Re: [gentoo-user] Re: Portage screwup
On Saturday 20 Apr 2013 03:04:30 Joseph wrote: On 04/20/13 01:13, Steven J. Long wrote: [snip] I am a holiday updater every second month or so; so at time to time I something get screw up and I got caught in between. I was looking blindly as I didn't really know what to look for. I turn out it was a problem with recent gtk+ package. Usually portage is very good at the package versions it offers and as long as you don't mix stable and testing trees too much you should have a working system most of the time. I just resync'ed and can see that app-text/poppler-0.22.2-r2 is stable: == ~ $ eix -l app-text/poppler [I] app-text/poppler Available versions: (0/35) 0.22.2-r2 [cairo cjk curl cxx debug doc +introspection +jpeg jpeg2k +lcms png qt4 tiff +utils] (0/36) ~ 0.22.3 [cairo cjk curl cxx debug doc +introspection +jpeg jpeg2k +lcms png qt4 tiff +utils] Installed versions: 0.22.2-r2(0/35)(10:09:38 03/23/13)(cairo cxx introspection jpeg lcms png qt4 tiff utils -cjk -curl -debug -doc -jpeg2k) Homepage:http://poppler.freedesktop.org/ Description: PDF rendering library based on the xpdf-3.0 code base == I do not know why want to revert to a previous version, but if you must then the advice about using an ebuild from attic is what you should follow. I'm not sure if building binary is a solution for me. Building a binary of already installed package(s) was offered as an option in case you want to revert to a previous version, *without* having to use a local overlay, or having to remerge an older version. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: Portage screwup
On Thu, Apr 18, 2013 at 02:34:42PM -0600, Joseph wrote: On 04/18/13 22:10, Michael Hampicke wrote: Am 18.04.2013 15:33, schrieb Joseph: What is going on with portage? All the older packages are being removed and and some of them are not even made stable. I've masked current one app-text/poppler-0.22.2-r2 but looking at the web-page this is not even stable poppler-0.22.3 is masked all across the previous version are all removed. All the packages that I recently try to roll back are gone, in most cases only one is available so there is no option to roll back. Am I missing something? If you want the option to rollback, you should use FEATURES=buildpkg[1] in general, and qpkg to make a binpkg from current system. qpkg is part of portage-utils, which is highly recommended. man q after you install it, and follow the instructions in einfo to get it to sync when portage does. The version of poppler that you have masked ( 0.22.2-r2 ) is stable. So it's not a portage screw up, the problem is more that you are trying to install outdated software. I'm not getting any were with this; looking blindly trying to install older versions hoping it might help.. Maybe it is time for me to move to another distro. Why do you want an older version? I don't understand why you have 0.22.2-r2 masked at all; it's in stable which means it's been tested by quite a few people already, and it is recommended that you upgrade. Just be sure to do a revdep-rebuild after you emerge -uD --changed-use world and depclean. As to attic stuff, as Neal said you need to copy ebuild and any needed files from the files subdir into a local overlay. You can read about how to do that at [2] but as I said, I don't think you should have stable poppler masked in the first place. Regards, steveL. [1] http://forums.gentoo.org/viewtopic-p-7165614.html#7165614 [2] http://forums.gentoo.org/viewtopic-p-4547366.html#4547366 -- #friendly-coders -- We're friendly, but we're not /that/ friendly ;-)
Re: [gentoo-user] Re: Portage screwup
On 04/20/13 01:13, Steven J. Long wrote: [snip] If you want the option to rollback, you should use FEATURES=buildpkg[1] in general, and qpkg to make a binpkg from current system. qpkg is part of portage-utils, which is highly recommended. man q after you install it, and follow the instructions in einfo to get it to sync when portage does. I am a holiday updater every second month or so; so at time to time I something get screw up and I got caught in between. I was looking blindly as I didn't really know what to look for. I turn out it was a problem with recent gtk+ package. I'm not sure if building binary is a solution for me. The version of poppler that you have masked ( 0.22.2-r2 ) is stable. So it's not a portage screw up, the problem is more that you are trying to install outdated software. I'm not getting any were with this; looking blindly trying to install older versions hoping it might help.. Maybe it is time for me to move to another distro. Why do you want an older version? I don't understand why you have 0.22.2-r2 masked at all; it's in stable which means it's been tested by quite a few people already, and it is recommended that you upgrade. Just be sure to do a revdep-rebuild after you emerge -uD --changed-use world and depclean. As to attic stuff, as Neal said you need to copy ebuild and any needed files from the files subdir into a local overlay. You can read about how to do that at [2] but as I said, I don't think you should have stable poppler masked in the first place. This atic stuff was explained to me on the forum in more details, I remember running overlay but it was long time ago so I had to have my memory refresh. First we need in make.conf PORTDIR_OVERLAY=/usr/local/portage Next we need to find the package from: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/?hideattic=0 Download the ebuild (and any extra/patches) and put in in path-to-overlay/category/packagename run full path name: ebuild path-to-overlay/category/packagename/.ebuild manifest It would be a good idea to have detailed instruction somewhere in Gentoo documentation. -- Joseph
