[gentoo-user] Re: Emerging glib-2.60.6 failed
David Haller: >You seem to be missing the 32bit part of dev-libs/libffi. I.e. >ABI_X86="32 64". Right. Next time I will do a 'grep fatal' on the build.log. Thanks. :) Hartmut
Re: [gentoo-user] Re: Emerging glib-2.60.6 failed
Hello, On Sun, 08 Sep 2019, Hartmut Figge wrote: >(Nuno Silva): > >>http://www.triffids.de/pub/gentoo/glib-2.60.6/build.log.txt gives me >>HTTP 403 (Forbidden). > >Fixed. Have to investigate how that could have happened. You seem to be missing the 32bit part of dev-libs/libffi. I.e. ABI_X86="32 64". HTH, -dnh -- Och yes. I used to have a brain once. If anyone sees it, please ask it to come back, I miss it sometimes. -- Frossie
Re: [gentoo-user] KDE machine -> Shutdown icons gone walkabout
On 20/8/19 2:21 am, Andrew Lowe wrote: Hi all, I recently, last week or so, did some updating of my KDE desktop and when I went to select "Shutdown" off the menu bar thingy, no icons for "Logout", "Shutdown" & "Some Other Thing" appeared as they used to. I in turn had to open up a shell, su and then "shutdown -t now" to bring the machine down. Have I missed something somewhere as to why I no longer get the icons? Has something been broken down into smaller bits and I now have to emerge something else to get the icons back? Thoughts greatly appreciated, Andrew A bit of a wait and a few more emerges and it appears to have fixed itself. Cause - unknown!!! Thanks for the replies, Andrew
[gentoo-user] Re: packages going stable after sources become unavailable
On 2019-09-08, Rich Freeman wrote: > On Sun, Sep 8, 2019 at 11:38 AM Grant Edwards > wrote: >> >> This seems to happen regularly with Imagemagick. Version 7.0.8.60 >> just went stable today, yet it can't be built because version 7.0.8.60 >> sources can no longer be downloaded. >> >> Am I doing something wrong? >> >> Shouldn't there be a requirement that an ebuild actually be >> _buildable_ from scratch when it goes stable? >> > > Do you have a working Gentoo distfile mirror in your make.conf? Doh! Apparently, both of the mirrors I have configured are broken: GENTOO_MIRRORS="http://lug.mtu.edu/gentoo/ http://cosmos.illinois.edu/pub/gentoo/; The first one is out-of-date and doesn't contain the the last few versions of ImageMagick. The second is just plain AWOL. I've updated make.conf with a couple mirrors that I've manually verified, and now my update is building as expected. I guess I need to add verifying mirrors are present and correct to the list of normal maintainence activities. -- Grant
Re: [gentoo-user] packages going stable after sources become unavailable
On Sun, Sep 8, 2019 at 11:38 AM Grant Edwards wrote: > > This seems to happen regularly with Imagemagick. Version 7.0.8.60 > just went stable today, yet it can't be built because version 7.0.8.60 > sources can no longer be downloaded. > > Am I doing something wrong? > > Shouldn't there be a requirement that an ebuild actually be > _buildable_ from scratch when it goes stable? > Do you have a working Gentoo distfile mirror in your make.conf? imagemagic has a mirror:// SRC_URI. That means there is no upstream distfile available, and Gentoo is distributing its own file via the mirrors (this is actually frowned upon these days though I'm not sure if it is banned offhand - I just avoid doing it this way). Usually the better practice is to host the file somewhere (such as the Gentoo webserver), and it will be mirrored anyway. These mirror:// files are manually injected into the mirror system by developers, and then they stick around as long as some ebuild references them, and then they just go poof without a trace (which means users with older repos can have issues). There has been talk about more robust solutions for these files (especially patches/etc), but nothing has happened. If your system isn't configured with a working Gentoo distfile mirror then for most packages you're probably downloading everything from upstream, but these mirror:// URIs have no sources other than the mirrors so if you don't have a working mirror config it simply won't fetch at all. In general anything in the tree should be fetchable. If that isn't the case it should be quickly spotted and fixed/removed, and it is always a valid bug, assuming it isn't just a local issue on your system. I wouldn't file a bug for this issue - I suspect QA would have already if it wanted to make it a strict policy. This sort of thing is trivially detected with a tinderbox or repoman if desired. -- Rich
[gentoo-user] packages going stable after sources become unavailable
I've noticed on several occasions in the past few months that by the time some packages are marked stable, the version is old enough that sources are no longer available -- so the emerge fails because sources can no longer be downloaded. If I'm lucky I may have a copy of the sources on another machine. If I'm not lucky, I just wait until the next time a new version goes stable and hope that it's not been obsoleted. This seems to happen regularly with Imagemagick. Version 7.0.8.60 just went stable today, yet it can't be built because version 7.0.8.60 sources can no longer be downloaded. Am I doing something wrong? Shouldn't there be a requirement that an ebuild actually be _buildable_ from scratch when it goes stable? -- Grant
[gentoo-user] Re: Emerging glib-2.60.6 failed
Hartmut Figge: >(Nuno Silva): >>http://www.triffids.de/pub/gentoo/glib-2.60.6/build.log.txt gives me >>HTTP 403 (Forbidden). > >Fixed. Have to investigate how that could have happened. /var/tmp/portage/dev-libs/glib-2.60.6/temp/build.log has the permissions -rw-rw. My only change was to append .txt as convenience. Hartmut
[gentoo-user] Re: Emerging glib-2.60.6 failed
(Nuno Silva): >http://www.triffids.de/pub/gentoo/glib-2.60.6/build.log.txt gives me >HTTP 403 (Forbidden). Fixed. Have to investigate how that could have happened. Hartmut
[gentoo-user] Re: Emerging glib-2.60.6 failed
On 2019-09-08, Hartmut Figge wrote: > my latest update 'emerge -q -uDN @world' failed at glib-2.60.6. > Continuing with --skipfirst succeeded. Today, after a new 'emerge > --sync', 'emerge -q -uDN @system' still failed with the same error. > > My Gentoo is mostly stable. The relevant info can be found at > http://www.triffids.de/pub/gentoo/glib-2.60.6/ http://www.triffids.de/pub/gentoo/glib-2.60.6/build.log.txt gives me HTTP 403 (Forbidden). -- Nuno Silva
[gentoo-user] Emerging glib-2.60.6 failed
Greetings, my latest update 'emerge -q -uDN @world' failed at glib-2.60.6. Continuing with --skipfirst succeeded. Today, after a new 'emerge --sync', 'emerge -q -uDN @system' still failed with the same error. My Gentoo is mostly stable. The relevant info can be found at http://www.triffids.de/pub/gentoo/glib-2.60.6/ What to do? If more info is needed I will upload it to the above location. Hartmut
