1 |
Hi, |
2 |
|
3 |
WRONG! :) :) :) |
4 |
|
5 |
I did something different, but it was the same amount of "wrong". |
6 |
|
7 |
I masked =sys-libs/glibc-2.25-r4. |
8 |
|
9 |
And now I remember why I did this: It gave a compilation error: |
10 |
(As some other packages) it has problems with my texinfo installation |
11 |
as it seems. |
12 |
|
13 |
As suggested I run perl-cleaner, I checked my environment for |
14 |
suspicious entrie...but looks fine (at least for me). |
15 |
|
16 |
I really wnat to get rid of this damn texinfo problem and I |
17 |
desperately aksing for help, since I didn't found the problem myself. |
18 |
|
19 |
But before bombarding the mailinglist with TONS of logs I would like |
20 |
to ask, what logging to post first? |
21 |
|
22 |
Cheers and thanks for the support in advance! |
23 |
Meino |
24 |
|
25 |
|
26 |
|
27 |
|
28 |
|
29 |
On 09/12 07:32, Franz Fellner wrote: |
30 |
> My guess: You have glibc-2.24-r4 and one of the 2.25 with revision <-r4 |
31 |
> listed WITH EXACT VERSION AND REVISiON in your package.accept_keywords. The |
32 |
> recent glibc-cleanp remove those 2.25 revisions and only left 2.25-r4 and |
33 |
> 2.24-r4 Leaving you with the downgrade as only option to get the most |
34 |
> recent available version. |
35 |
> |
36 |
> 2017-09-12 9:17 GMT+02:00 Alan McKinnon <alan.mckinnon@×××××.com>: |
37 |
> |
38 |
> > On 12/09/2017 05:43, tuxic@××××××.de wrote: |
39 |
> > > Hi, |
40 |
> > > |
41 |
> > > got a problem this morning: |
42 |
> > > |
43 |
> > >>>> Verifying ebuild manifests |
44 |
> > >>>> Running pre-merge checks for sys-libs/glibc-2.24-r4 |
45 |
> > > * Sanity check to keep you from breaking your system: |
46 |
> > > * Downgrading glibc is not supported and a sure way to destruction |
47 |
> > > * ERROR: sys-libs/glibc-2.24-r4::gentoo failed (pretend phase): |
48 |
> > > * aborting to save your system |
49 |
> > > * |
50 |
> > > * Call stack: |
51 |
> > > * ebuild.sh, line 115: Called pkg_pretend |
52 |
> > > * ebuild.sh, line 348: Called |
53 |
> > toolchain-glibc_pkg_pretend |
54 |
> > > * toolchain-glibc.eclass, line 507: Called die |
55 |
> > > * The specific snippet of code: |
56 |
> > > * die "aborting to save your system" |
57 |
> > > * |
58 |
> > > * If you need support, post the output of `emerge --info |
59 |
> > '=sys-libs/glibc-2.24-r4::gentoo'`, |
60 |
> > > * the complete build log and the output of `emerge -pqv |
61 |
> > '=sys-libs/glibc-2.24-r4::gentoo'`. |
62 |
> > > * The complete build log is located at '/var/tmp/portage/sys-libs/ |
63 |
> > glibc-2.24-r4/temp/build.log'. |
64 |
> > > * The ebuild environment file is located at '/var/tmp/portage/sys-libs/ |
65 |
> > glibc-2.24-r4/temp/die.env'. |
66 |
> > > * Working directory: '/var/tmp/portage/sys-libs/glibc-2.24-r4/homedir' |
67 |
> > > * S: '/var/tmp/portage/sys-libs/glibc-2.24-r4/work/glibc-2.24' |
68 |
> > >>>> Running pre-merge checks for media-sound/pulseaudio-11.0 |
69 |
> > > * Determining the location of the kernel source code |
70 |
> > > * Found kernel source directory: |
71 |
> > > * /usr/src/linux |
72 |
> > > * Found sources for kernel version: |
73 |
> > > * 4.13.1-RT |
74 |
> > > * Checking for suitable kernel configuration options... |
75 |
> > > [ ok ] |
76 |
> > > * A preallocated buffer-size of 2048 (kB) or higher is recommended for |
77 |
> > the HD-audio driver! |
78 |
> > > * CONFIG_SND_HDA_PREALLOC_SIZE=64 |
79 |
> > > |
80 |
> > > I would interpret this as: |
81 |
> > |
82 |
> > Looks to me like you are assuming the glibc maintainer has more |
83 |
> > knowledge of the future that he/she actually has. |
84 |
> > |
85 |
> > > |
86 |
> > > In the past emerge had updated glibc to a higher version as it want it |
87 |
> > > to install now and prevented the latter becayse it would be downgrade, |
88 |
> > > which in turn would render my box useless. |
89 |
> > |
90 |
> > No, not useless. It's a safety check for just in case. And now you must |
91 |
> > bypass the checks |
92 |
> > |
93 |
> > > |
94 |
> > > But why updateing to higher version in the first step |
95 |
> > |
96 |
> > Because you had a valid ebuild in the tree that said to do it ? |
97 |
> > > |
98 |
> > ....or attempting |
99 |
> > > to downgrade now? |
100 |
> > |
101 |
> > Because now you don't have that valid ebuild anymore? |
102 |
> > |
103 |
> > |
104 |
> > > |
105 |
> > > And finally...ANy update is blocked for now it seems...how can I get |
106 |
> > > out of this? |
107 |
> > |
108 |
> > Why is glibc wanting to downgrade? What is your current version? |
109 |
> > |
110 |
> > both of these versions are in the tree: (~)2.24-r4^s (~)2.25-r4^s |
111 |
> > so there is at least 1 glibc higher than what portage wants to downgrade |
112 |
> > to. |
113 |
> > |
114 |
> > You need to find out why 2.25-r4 is not being used. Usual tools, e.g.: |
115 |
> > |
116 |
> > grep -r glibc /etc/portage |
117 |
> > and any other methods you prefer |
118 |
> > |
119 |
> > As a last resort if the ebuld maintainer screwed up, you can bypass the |
120 |
> > safety check. Edit ${PORTDIR}/eclass/toolchain-glibc.eclass and comment |
121 |
> > out the check in |
122 |
> > toolchain-glibc_pkg_pretend() |
123 |
> > |
124 |
> > This is unlikely to destroy the system. Cause a problem - maybe. Destroy |
125 |
> > it? No. The wording of the safety check is hugely over-dramatic to |
126 |
> > discourage people from downgrading willy-nilly without thinking |
127 |
> > |
128 |
> > -- |
129 |
> > Alan McKinnon |
130 |
> > alan.mckinnon@×××××.com |
131 |
> > |
132 |
> > |
133 |
> > |