Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[Mike Gilbert]

On Tue, Sep 12, 2017 at 12:57 PM,   wrote:
> On 09/12 04:52, Andreas K. Huettel wrote:
>> > I masked =sys-libs/glibc-2.25-r4.
>> >
>> > And now I remember why I did this: It gave a compilation error:
>> > (As some other packages) it has problems with my texinfo installation
>> > as it seems.
>> >
>>
>> bug number?
>>
>>
>> --
>> Andreas K. Hüttel
>> dilfri...@gentoo.org
>> Gentoo Linux developer (council, perl, libreoffice)
>>
>
> Hi Andreas,
>
> hrrrmmmno the problem is on my side...somewhere.
> It is not considered a Gentoo-bug...
>
>

Here are the previous ml threads on this topic.

https://archives.gentoo.org/gentoo-user/message/143c7501eedc377a72a98cdf5a1b4280

https://archives.gentoo.org/gentoo-user/message/e25e368978d10615346bd18a8b3740e8

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[tuxic]

On 09/12 04:52, Andreas K. Huettel wrote:
> > I masked =sys-libs/glibc-2.25-r4.
> > 
> > And now I remember why I did this: It gave a compilation error:
> > (As some other packages) it has problems with my texinfo installation
> > as it seems.
> > 
> 
> bug number?
> 
> 
> -- 
> Andreas K. Hüttel
> dilfri...@gentoo.org
> Gentoo Linux developer (council, perl, libreoffice)
> 

Hi Andreas,

hrrrmmmno the problem is on my side...somewhere.
It is not considered a Gentoo-bug...


Cheers
Meino

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[tuxic]

On 09/12 04:50, Andreas K. Huettel wrote:
> Am Dienstag, 12. September 2017, 05:43:59 CEST schrieb tu...@posteo.de:
> > Hi,
> > 
> > got a problem this morning:
> > >>> Verifying ebuild manifests
> > >>> Running pre-merge checks for sys-libs/glibc-2.24-r4
> > 
> >  * Sanity check to keep you from breaking your system:
> >  *  Downgrading glibc is not supported and a sure way to destruction
> 
> ... because I accidentally removed 2.24-r4 instead of 2.24-r3. 
> 
> Got fixed a few hours later as soon as someone filed a bug. 
> (I wanted to keep the last 2.24 revision.)
> 
> --> so, file bugs! :)
> 
> That said, 2.24 won't go stable; the current stable candidate is 2.25-r5. 
> 
> -- 
> Andreas K. Hüttel
> dilfri...@gentoo.org
> Gentoo Linux developer (council, perl, libreoffice)
> 

Hi Andreas,

...and it was also a configuration bug on my side (see my last
posting).

Do you know how to solve this long lasting texinfo problem on my side?

Cheers
Meino

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[Andreas K. Huettel]

> I masked =sys-libs/glibc-2.25-r4.
> 
> And now I remember why I did this: It gave a compilation error:
> (As some other packages) it has problems with my texinfo installation
> as it seems.
> 

bug number?


-- 
Andreas K. Hüttel
dilfri...@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[Andreas K. Huettel]

Am Dienstag, 12. September 2017, 05:43:59 CEST schrieb tu...@posteo.de:
> Hi,
> 
> got a problem this morning:
> >>> Verifying ebuild manifests
> >>> Running pre-merge checks for sys-libs/glibc-2.24-r4
> 
>  * Sanity check to keep you from breaking your system:
>  *  Downgrading glibc is not supported and a sure way to destruction

... because I accidentally removed 2.24-r4 instead of 2.24-r3. 

Got fixed a few hours later as soon as someone filed a bug. 
(I wanted to keep the last 2.24 revision.)

--> so, file bugs! :)

That said, 2.24 won't go stable; the current stable candidate is 2.25-r5. 

-- 
Andreas K. Hüttel
dilfri...@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[tuxic]

Hi,

WRONG! :) :) :)

I did something different, but it was the same amount of "wrong".

I masked =sys-libs/glibc-2.25-r4.

And now I remember why I did this: It gave a compilation error:
(As some other packages) it has problems with my texinfo installation
as it seems.

As suggested I run perl-cleaner, I checked my environment for
suspicious entrie...but looks fine (at least for me).

I really wnat to get rid of this damn texinfo problem and I 
desperately aksing for help, since I didn't found the problem myself.

But before bombarding the mailinglist with TONS of logs I would like
to ask, what logging to post first?

Cheers and thanks for the support in advance!
Meino





On 09/12 07:32, Franz Fellner wrote:
> My guess: You have glibc-2.24-r4 and one of the 2.25 with revision <-r4
> listed WITH EXACT VERSION AND REVISiON in your package.accept_keywords. The
> recent glibc-cleanp remove those 2.25 revisions and only left 2.25-r4 and
> 2.24-r4 Leaving you with the downgrade as only option to get the most
> recent available version.
> 
> 2017-09-12 9:17 GMT+02:00 Alan McKinnon :
> 
> > On 12/09/2017 05:43, tu...@posteo.de wrote:
> > > Hi,
> > >
> > > got a problem this morning:
> > >
> >  Verifying ebuild manifests
> >  Running pre-merge checks for sys-libs/glibc-2.24-r4
> > >  * Sanity check to keep you from breaking your system:
> > >  *  Downgrading glibc is not supported and a sure way to destruction
> > >  * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase):
> > >  *   aborting to save your system
> > >  *
> > >  * Call stack:
> > >  *ebuild.sh, line 115:  Called pkg_pretend
> > >  *ebuild.sh, line 348:  Called
> > toolchain-glibc_pkg_pretend
> > >  *   toolchain-glibc.eclass, line 507:  Called die
> > >  * The specific snippet of code:
> > >  *die "aborting to save your system"
> > >  *
> > >  * If you need support, post the output of `emerge --info
> > '=sys-libs/glibc-2.24-r4::gentoo'`,
> > >  * the complete build log and the output of `emerge -pqv
> > '=sys-libs/glibc-2.24-r4::gentoo'`.
> > >  * The complete build log is located at '/var/tmp/portage/sys-libs/
> > glibc-2.24-r4/temp/build.log'.
> > >  * The ebuild environment file is located at '/var/tmp/portage/sys-libs/
> > glibc-2.24-r4/temp/die.env'.
> > >  * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir'
> > >  * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24'
> >  Running pre-merge checks for media-sound/pulseaudio-11.0
> > >  * Determining the location of the kernel source code
> > >  * Found kernel source directory:
> > >  * /usr/src/linux
> > >  * Found sources for kernel version:
> > >  * 4.13.1-RT
> > >  * Checking for suitable kernel configuration options...
> > >  [ ok ]
> > >  * A preallocated buffer-size of 2048 (kB) or higher is recommended for
> > the HD-audio driver!
> > >  * CONFIG_SND_HDA_PREALLOC_SIZE=64
> > >
> > > I would interpret this as:
> >
> > Looks to me like you are assuming the glibc maintainer has more
> > knowledge of the future that he/she actually has.
> >
> > >
> > > In the past emerge had updated glibc to a higher version as it want it
> > > to install now and prevented the latter becayse it would be downgrade,
> > > which in turn would render my box useless.
> >
> > No, not useless. It's a safety check for just in case. And now you must
> > bypass the checks
> >
> > >
> > > But why updateing to higher version in the first step
> >
> > Because you had a valid ebuild in the tree that said to do it ?
> > >
> > or attempting
> > > to downgrade now?
> >
> > Because now you don't have that valid ebuild anymore?
> >
> >
> > >
> > > And finally...ANy update is blocked for now it seems...how can I get
> > > out of this?
> >
> > Why is glibc wanting to downgrade? What is your current version?
> >
> > both of these versions are in the tree: (~)2.24-r4^s (~)2.25-r4^s
> > so there is at least 1 glibc higher than what portage wants to downgrade
> > to.
> >
> > You need to find out why 2.25-r4 is not being used. Usual tools, e.g.:
> >
> > grep -r glibc /etc/portage
> > and any other methods you prefer
> >
> > As a last resort if the ebuld maintainer screwed up, you can bypass the
> > safety check. Edit ${PORTDIR}/eclass/toolchain-glibc.eclass and comment
> > out the check in
> > toolchain-glibc_pkg_pretend()
> >
> > This is unlikely to destroy the system. Cause a problem - maybe. Destroy
> > it? No. The wording of the safety check is hugely over-dramatic to
> > discourage people from downgrading willy-nilly without thinking
> >
> > --
> > Alan McKinnon
> > alan.mckin...@gmail.com
> >
> >
> >

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[Franz Fellner]

My guess: You have glibc-2.24-r4 and one of the 2.25 with revision <-r4
listed WITH EXACT VERSION AND REVISiON in your package.accept_keywords. The
recent glibc-cleanp remove those 2.25 revisions and only left 2.25-r4 and
2.24-r4 Leaving you with the downgrade as only option to get the most
recent available version.

2017-09-12 9:17 GMT+02:00 Alan McKinnon :

> On 12/09/2017 05:43, tu...@posteo.de wrote:
> > Hi,
> >
> > got a problem this morning:
> >
>  Verifying ebuild manifests
>  Running pre-merge checks for sys-libs/glibc-2.24-r4
> >  * Sanity check to keep you from breaking your system:
> >  *  Downgrading glibc is not supported and a sure way to destruction
> >  * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase):
> >  *   aborting to save your system
> >  *
> >  * Call stack:
> >  *ebuild.sh, line 115:  Called pkg_pretend
> >  *ebuild.sh, line 348:  Called
> toolchain-glibc_pkg_pretend
> >  *   toolchain-glibc.eclass, line 507:  Called die
> >  * The specific snippet of code:
> >  *die "aborting to save your system"
> >  *
> >  * If you need support, post the output of `emerge --info
> '=sys-libs/glibc-2.24-r4::gentoo'`,
> >  * the complete build log and the output of `emerge -pqv
> '=sys-libs/glibc-2.24-r4::gentoo'`.
> >  * The complete build log is located at '/var/tmp/portage/sys-libs/
> glibc-2.24-r4/temp/build.log'.
> >  * The ebuild environment file is located at '/var/tmp/portage/sys-libs/
> glibc-2.24-r4/temp/die.env'.
> >  * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir'
> >  * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24'
>  Running pre-merge checks for media-sound/pulseaudio-11.0
> >  * Determining the location of the kernel source code
> >  * Found kernel source directory:
> >  * /usr/src/linux
> >  * Found sources for kernel version:
> >  * 4.13.1-RT
> >  * Checking for suitable kernel configuration options...
> >  [ ok ]
> >  * A preallocated buffer-size of 2048 (kB) or higher is recommended for
> the HD-audio driver!
> >  * CONFIG_SND_HDA_PREALLOC_SIZE=64
> >
> > I would interpret this as:
>
> Looks to me like you are assuming the glibc maintainer has more
> knowledge of the future that he/she actually has.
>
> >
> > In the past emerge had updated glibc to a higher version as it want it
> > to install now and prevented the latter becayse it would be downgrade,
> > which in turn would render my box useless.
>
> No, not useless. It's a safety check for just in case. And now you must
> bypass the checks
>
> >
> > But why updateing to higher version in the first step
>
> Because you had a valid ebuild in the tree that said to do it ?
> >
> or attempting
> > to downgrade now?
>
> Because now you don't have that valid ebuild anymore?
>
>
> >
> > And finally...ANy update is blocked for now it seems...how can I get
> > out of this?
>
> Why is glibc wanting to downgrade? What is your current version?
>
> both of these versions are in the tree: (~)2.24-r4^s (~)2.25-r4^s
> so there is at least 1 glibc higher than what portage wants to downgrade
> to.
>
> You need to find out why 2.25-r4 is not being used. Usual tools, e.g.:
>
> grep -r glibc /etc/portage
> and any other methods you prefer
>
> As a last resort if the ebuld maintainer screwed up, you can bypass the
> safety check. Edit ${PORTDIR}/eclass/toolchain-glibc.eclass and comment
> out the check in
> toolchain-glibc_pkg_pretend()
>
> This is unlikely to destroy the system. Cause a problem - maybe. Destroy
> it? No. The wording of the safety check is hugely over-dramatic to
> discourage people from downgrading willy-nilly without thinking
>
> --
> Alan McKinnon
> alan.mckin...@gmail.com
>
>
>

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[Alan McKinnon]

On 12/09/2017 05:43, tu...@posteo.de wrote:
> Hi,
> 
> got a problem this morning:
> 
 Verifying ebuild manifests
 Running pre-merge checks for sys-libs/glibc-2.24-r4
>  * Sanity check to keep you from breaking your system:
>  *  Downgrading glibc is not supported and a sure way to destruction
>  * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase):
>  *   aborting to save your system
>  * 
>  * Call stack:
>  *ebuild.sh, line 115:  Called pkg_pretend
>  *ebuild.sh, line 348:  Called toolchain-glibc_pkg_pretend
>  *   toolchain-glibc.eclass, line 507:  Called die
>  * The specific snippet of code:
>  *die "aborting to save your system"
>  * 
>  * If you need support, post the output of `emerge --info 
> '=sys-libs/glibc-2.24-r4::gentoo'`,
>  * the complete build log and the output of `emerge -pqv 
> '=sys-libs/glibc-2.24-r4::gentoo'`.
>  * The complete build log is located at 
> '/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/build.log'.
>  * The ebuild environment file is located at 
> '/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/die.env'.
>  * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir'
>  * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24'
 Running pre-merge checks for media-sound/pulseaudio-11.0
>  * Determining the location of the kernel source code
>  * Found kernel source directory:
>  * /usr/src/linux
>  * Found sources for kernel version:
>  * 4.13.1-RT
>  * Checking for suitable kernel configuration options...
>  [ ok ]
>  * A preallocated buffer-size of 2048 (kB) or higher is recommended for the 
> HD-audio driver!
>  * CONFIG_SND_HDA_PREALLOC_SIZE=64
> 
> I would interpret this as:

Looks to me like you are assuming the glibc maintainer has more
knowledge of the future that he/she actually has.

> 
> In the past emerge had updated glibc to a higher version as it want it
> to install now and prevented the latter becayse it would be downgrade,
> which in turn would render my box useless.

No, not useless. It's a safety check for just in case. And now you must
bypass the checks

> 
> But why updateing to higher version in the first step

Because you had a valid ebuild in the tree that said to do it ?
>
or attempting
> to downgrade now?

Because now you don't have that valid ebuild anymore?


> 
> And finally...ANy update is blocked for now it seems...how can I get
> out of this?

Why is glibc wanting to downgrade? What is your current version?

both of these versions are in the tree: (~)2.24-r4^s (~)2.25-r4^s
so there is at least 1 glibc higher than what portage wants to downgrade to.

You need to find out why 2.25-r4 is not being used. Usual tools, e.g.:

grep -r glibc /etc/portage
and any other methods you prefer

As a last resort if the ebuld maintainer screwed up, you can bypass the
safety check. Edit ${PORTDIR}/eclass/toolchain-glibc.eclass and comment
out the check in
toolchain-glibc_pkg_pretend()

This is unlikely to destroy the system. Cause a problem - maybe. Destroy
it? No. The wording of the safety check is hugely over-dramatic to
discourage people from downgrading willy-nilly without thinking

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[Dale]

tu...@posteo.de wrote:
> Hi,
>
> got a problem this morning:
>
 Verifying ebuild manifests
 Running pre-merge checks for sys-libs/glibc-2.24-r4
>  * Sanity check to keep you from breaking your system:
>  *  Downgrading glibc is not supported and a sure way to destruction
>  * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase):
>  *   aborting to save your system
>  * 
>  * Call stack:
>  *ebuild.sh, line 115:  Called pkg_pretend
>  *ebuild.sh, line 348:  Called toolchain-glibc_pkg_pretend
>  *   toolchain-glibc.eclass, line 507:  Called die
>  * The specific snippet of code:
>  *die "aborting to save your system"
>  * 
>  * If you need support, post the output of `emerge --info 
> '=sys-libs/glibc-2.24-r4::gentoo'`,
>  * the complete build log and the output of `emerge -pqv 
> '=sys-libs/glibc-2.24-r4::gentoo'`.
>  * The complete build log is located at 
> '/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/build.log'.
>  * The ebuild environment file is located at 
> '/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/die.env'.
>  * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir'
>  * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24'
 Running pre-merge checks for media-sound/pulseaudio-11.0
>  * Determining the location of the kernel source code
>  * Found kernel source directory:
>  * /usr/src/linux
>  * Found sources for kernel version:
>  * 4.13.1-RT
>  * Checking for suitable kernel configuration options...
>  [ ok ]
>  * A preallocated buffer-size of 2048 (kB) or higher is recommended for the 
> HD-audio driver!
>  * CONFIG_SND_HDA_PREALLOC_SIZE=64
>
> I would interpret this as:
>
> In the past emerge had updated glibc to a higher version as it want it
> to install now and prevented the latter becayse it would be downgrade,
> which in turn would render my box useless.
>
> But why updateing to higher version in the first stepor attempting
> to downgrade now?
>
> And finally...ANy update is blocked for now it seems...how can I get
> out of this?
>
> Thanks a lot in advance for any help!
> Cheers
> Meino
>

I would start by adding -t to the emerge command.  That should show what
is pulling in the older glibc.  Hopefully, that will shine a light on
the why it wants to downgrade. 

May be a good idea to post that info here as well.  May help others with
a answer since it should provide more info. 

Dale

:-)  :-) 

[gentoo-user] Downgrading glibc prevented by emerge/portage...but why initiated?

[tuxic]

Hi,

got a problem this morning:

>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-libs/glibc-2.24-r4
 * Sanity check to keep you from breaking your system:
 *  Downgrading glibc is not supported and a sure way to destruction
 * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase):
 *   aborting to save your system
 * 
 * Call stack:
 *ebuild.sh, line 115:  Called pkg_pretend
 *ebuild.sh, line 348:  Called toolchain-glibc_pkg_pretend
 *   toolchain-glibc.eclass, line 507:  Called die
 * The specific snippet of code:
 *  die "aborting to save your system"
 * 
 * If you need support, post the output of `emerge --info 
'=sys-libs/glibc-2.24-r4::gentoo'`,
 * the complete build log and the output of `emerge -pqv 
'=sys-libs/glibc-2.24-r4::gentoo'`.
 * The complete build log is located at 
'/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/build.log'.
 * The ebuild environment file is located at 
'/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir'
 * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24'
>>> Running pre-merge checks for media-sound/pulseaudio-11.0
 * Determining the location of the kernel source code
 * Found kernel source directory:
 * /usr/src/linux
 * Found sources for kernel version:
 * 4.13.1-RT
 * Checking for suitable kernel configuration options...
 [ ok ]
 * A preallocated buffer-size of 2048 (kB) or higher is recommended for the 
HD-audio driver!
 * CONFIG_SND_HDA_PREALLOC_SIZE=64

I would interpret this as:

In the past emerge had updated glibc to a higher version as it want it
to install now and prevented the latter becayse it would be downgrade,
which in turn would render my box useless.

But why updateing to higher version in the first stepor attempting
to downgrade now?

And finally...ANy update is blocked for now it seems...how can I get
out of this?

Thanks a lot in advance for any help!
Cheers
Meino

Re: [gentoo-user] downgrading glibc

[Raffaele Belardi]

On Fri, 2017-08-18 at 16:25 +0200, Nils Freydank wrote:
> Hi Raffaele,
> 
> Am Freitag, 18. August 2017, 09:00:52 CEST schrieb Raffaele Belardi:
> > […]
> > Downgrading the system to glibc to 2.23-r3 means trouble?
> 
> yes, you would crush your system. Therefore the even the ebuild
> prohibits it 
> (you can enforce it, but you really shouldn’t).
> 
> You can a) brick you system: https://forums.gentoo.org/viewtopic-t-84
> 5000.html
> or b) create a chroot with a blank system (new stage 3), emerge your
> package, 
> create a binpkg, install that on the host and hope it works.
> 

Message loud and clear, better search for a different solution or wait
for a fix!

thanks,

raffaele

Re: [gentoo-user] downgrading glibc

[Nils Freydank]

Hi Raffaele,

Am Freitag, 18. August 2017, 09:00:52 CEST schrieb Raffaele Belardi:
> […]
> Downgrading the system to glibc to 2.23-r3 means trouble?
yes, you would crush your system. Therefore the even the ebuild prohibits it 
(you can enforce it, but you really shouldn’t).

You can a) brick you system: https://forums.gentoo.org/viewtopic-t-845000.html
or b) create a chroot with a blank system (new stage 3), emerge your package, 
create a binpkg, install that on the host and hope it works.

Good luck! :-)


-- 
GPG fingerprint: '00EF D31F 1B60 D5DB ADB8  31C1 C0EC E696 0E54 475B'
Nils Freydank

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] downgrading glibc

[Raffaele Belardi]

I hava a build problem upgrading Mythtv to 0.28.1-r1 [1] on an ~amd64
system. The problem is related to a glibc API change [2] introduced in
glibc-2.24 and still present in glibc-2.25. So I'm thinking to try the
build with an older glibc version.

Downgrading the system to glibc to 2.23-r3 means trouble?
If not, an emerge @preserved-rebuild after the downgrade will be
sufficient to not break the rest of the system?
I suppose a quickpkg of the whole world before the downgrade would be a
good idea, just in case...

thanks,

raffaele


[1] https://bugs.gentoo.org/show_bug.cgi?id=604430
[2] https://bugs.gentoo.org/show_bug.cgi?id=575232

[gentoo-user] Downgrading glibc

[7v5w7go9ub0o]

I went through the gcc upgrade and discovered that ssp no longer works  
(suppose it was documented somewhere - but I missed it)


So I'm trying to reverse the upgrade process (this time using using a  
hardened profile) and glibc won't allow me to downgrade.


How do I get around this, please?

I've considered hacking the script/size/md5 tests, but would prefer to do  
it the proper way.


TIA
--
gentoo-user@gentoo.org mailing list