Re: yum, %post errors, mock failures
Jack Neely <[email protected]>
| Newsgroups | gmane.linux.rpm.yum |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Apr 29, 2009 at 05:26:57PM -0400, James Antill wrote: > Seth Vidal <[email protected]> writes: > > > On Wed, 29 Apr 2009, Jack Neely wrote: > > > >> Folks, > >> > >> I'm running into the funness that documented here: > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=433579 > >> > >> and discussed on the CentOS list: > >> > >> http://lists.centos.org/pipermail/centos/2009-April/074912.html > >> > >> In building a chroot, pam is installed before coreutils causing its > >> %post script to fail, yum to report an error code to mock, and mock > >> refusing to continue with the build. In fact, my case exactly matches > >> the CentOS thread just in RHEL 5.3. > >> > >> I hesitate to patch and push a custom pam package because of a > >> backwards dependency loop. Would anyone know how to jiggle yum or mock > >> just enough to ignore or get the loop in the right order for my build > >> machines? > >> > >> This is yum 3.2.19. > > > > grab yum from f11 and rebuild it - or ask nicely geppetto on irc about > > another pkg. > > Latest 3.2.22 still fails, IIRC there were two fixes for post > scripts. One was in yum, to make certain errors actually fail the > transaction and/or produce real error codes, and another was in rpm to > make %post scripts not be in that category. > There's probably no good fix here. > Don't you love build system failures? What would be the correct way to fix the pam package? I've seen a trick or two to jiggle it in front of coreutils by adding a file based dep...but that's just asking for this to come up again. Other comments I've seen are to ||: some of the %post bits. Jack -- Jack Neely <[email protected]> Linux Czar, OIT Campus Linux Services Office of Information Technology, NC State University GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89