| 1 |
On 12/09/2017 05:43, tuxic@××××××.de wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> got a problem this morning: |
| 5 |
> |
| 6 |
>>>> Verifying ebuild manifests |
| 7 |
>>>> Running pre-merge checks for sys-libs/glibc-2.24-r4 |
| 8 |
> * Sanity check to keep you from breaking your system: |
| 9 |
> * Downgrading glibc is not supported and a sure way to destruction |
| 10 |
> * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase): |
| 11 |
> * aborting to save your system |
| 12 |
> * |
| 13 |
> * Call stack: |
| 14 |
> * ebuild.sh, line 115: Called pkg_pretend |
| 15 |
> * ebuild.sh, line 348: Called toolchain-glibc_pkg_pretend |
| 16 |
> * toolchain-glibc.eclass, line 507: Called die |
| 17 |
> * The specific snippet of code: |
| 18 |
> * die "aborting to save your system" |
| 19 |
> * |
| 20 |
> * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r4::gentoo'`, |
| 21 |
> * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r4::gentoo'`. |
| 22 |
> * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/build.log'. |
| 23 |
> * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.24-r4/temp/die.env'. |
| 24 |
> * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir' |
| 25 |
> * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24' |
| 26 |
>>>> Running pre-merge checks for media-sound/pulseaudio-11.0 |
| 27 |
> * Determining the location of the kernel source code |
| 28 |
> * Found kernel source directory: |
| 29 |
> * /usr/src/linux |
| 30 |
> * Found sources for kernel version: |
| 31 |
> * 4.13.1-RT |
| 32 |
> * Checking for suitable kernel configuration options... |
| 33 |
> [ ok ] |
| 34 |
> * A preallocated buffer-size of 2048 (kB) or higher is recommended for the HD-audio driver! |
| 35 |
> * CONFIG_SND_HDA_PREALLOC_SIZE=64 |
| 36 |
> |
| 37 |
> I would interpret this as: |
| 38 |
|
| 39 |
Looks to me like you are assuming the glibc maintainer has more |
| 40 |
knowledge of the future that he/she actually has. |
| 41 |
|
| 42 |
> |
| 43 |
> In the past emerge had updated glibc to a higher version as it want it |
| 44 |
> to install now and prevented the latter becayse it would be downgrade, |
| 45 |
> which in turn would render my box useless. |
| 46 |
|
| 47 |
No, not useless. It's a safety check for just in case. And now you must |
| 48 |
bypass the checks |
| 49 |
|
| 50 |
> |
| 51 |
> But why updateing to higher version in the first step |
| 52 |
|
| 53 |
Because you had a valid ebuild in the tree that said to do it ? |
| 54 |
> |
| 55 |
....or attempting |
| 56 |
> to downgrade now? |
| 57 |
|
| 58 |
Because now you don't have that valid ebuild anymore? |
| 59 |
|
| 60 |
|
| 61 |
> |
| 62 |
> And finally...ANy update is blocked for now it seems...how can I get |
| 63 |
> out of this? |
| 64 |
|
| 65 |
Why is glibc wanting to downgrade? What is your current version? |
| 66 |
|
| 67 |
both of these versions are in the tree: (~)2.24-r4^s (~)2.25-r4^s |
| 68 |
so there is at least 1 glibc higher than what portage wants to downgrade to. |
| 69 |
|
| 70 |
You need to find out why 2.25-r4 is not being used. Usual tools, e.g.: |
| 71 |
|
| 72 |
grep -r glibc /etc/portage |
| 73 |
and any other methods you prefer |
| 74 |
|
| 75 |
As a last resort if the ebuld maintainer screwed up, you can bypass the |
| 76 |
safety check. Edit ${PORTDIR}/eclass/toolchain-glibc.eclass and comment |
| 77 |
out the check in |
| 78 |
toolchain-glibc_pkg_pretend() |
| 79 |
|
| 80 |
This is unlikely to destroy the system. Cause a problem - maybe. Destroy |
| 81 |
it? No. The wording of the safety check is hugely over-dramatic to |
| 82 |
discourage people from downgrading willy-nilly without thinking |
| 83 |
|
| 84 |
-- |
| 85 |
Alan McKinnon |
| 86 |
alan.mckinnon@×××××.com |
Archives