[gentoo-amd64] Re: printing has stopped

[Duncan <1i5t5.duncan@cox.net>]

Beso <givemesugarr@gmail.com> posted
d257c3560712081230x513a700foc530b9f0a40d5a0@mail.gmail.com, excerpted
below, on  Sat, 08 Dec 2007 20:30:43 +0000:

> 2007/12/8, David Abbott <abbottdavid@bellsouth.net>:
>>
>>
>>
>> This may help;
>> https://forums.gentoo.org/viewtopic-t-448550.html
> 
> 
> this is the expat-2 upgrade thread. i don't really see how this could
> help.... if it's only the revdep issue you just need to remove the
> .revdep* files from /root/ and run revdep again (or run revdep-rebuild
> -i, thus i don't know if the portage version - i'm using paludis -
> support -i, which stands for --ignore, option).

Portage's revdep-rebuild does indeed support -i.

However, that's not the issue in this case.  Note that the affected 
rebuilds are 32-bit, thus not rebuilds at all, but simply remerging pre-
built binaries.  One can "rebuild" them all day and it's not going to 
help, because it's the same binaries that are remerged each time, 
binaries that remain linked to an old/stale 32-bit expat library that's 
apparently no longer there either.

Find the 32-bit binary that continues to link to the old 32-bit expat 
library, and try remerging both it and the compat package that should 
contain the missing library (probably the same one containing the new 
version) manually.  It's possible that revdep-rebuild is only remerging 
one and it's a remerge of the other that's necessary.  If that doesn't 
work, then it's time to see if there's already a bug filed on it, and 
file one if not.  (Or just decide 32-bit isn't worth the hassle anyway, 
and switch to a no-multilib profile, unmerging all the 32-bit stuff, my 
solution as I don't/can't merge proprietaryware anyway, and most of the 
freedomware stuff is long since 64-bit ported, OR decide that it's worth 
/really/ supporting, and do the 32-bit chroot thing, after which you can 
do a real rebuild in the chroot, assuming it's not some stupid 
proprietaryware causing the trouble.)

However, while it's possible that'll fix the printing issue if there's 
some mixup between 32-bit and 64-bit, it's unlikely to in the normal 
case, unless it's a 32-bit app you are trying to print from, since 64-bit 
shouldn't be trying to load the 32-bit stuff anyway -- it should ignore 
it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list