| View previous topic :: View next topic |
| Author |
Message |
tabanus
l33t
Joined: 11 Jun 2004
Posts: 638
Location: UK
|
 Posted: Tue Sep 10, 2013 5:08 pm Post subject: Portage 2.2 stabilised released! WTF? |
 |
|
OK, so after humpty-million rc-candidates, portage-2.2.1 has been stabilised. I had to rub my eyes to make sure I wasn't mis-reading it.
Now, I've not been following the testing branch at all, so have no clue what differences this brings. Any chance of a news item or an announcement in the forums? Can someone summarise what's changed?
Presumably one thing that's changed is overlay handling because I got this error message:
| Code: | !!! Repository 'x-local' is missing masters attribute in '/usr/portage/local/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
WARNING: One or more repositories have missing repo_name entries:
/usr/portage/local/profiles/repo_name
NOTE: Each repo_name entry should be a plain text file containing a
unique name for the repository on the first line.
|
Thanks
_________________
Things you might say if you never took Physics: "I'm overweight even though I don't overeat." - Neil deGrasse Tyson |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Tue Sep 10, 2013 5:34 pm Post subject: |
|
|
Now, on the other hand I have been following portage-2.2 for years, so I have no idea what features were integrated in 2.1.x already (I understand there were a lot). 
One thing's for sure, hell must be freezing cold right now. |
|
| Back to top |
|
|
Annagul
Apprentice
Joined: 05 Dec 2004
Posts: 156
Location: San Fernando, Cádiz (Spain)
|
| Posted: Tue Sep 10, 2013 7:03 pm Post subject: |
|
|
Another surprised user here.
Is there an official announce, or a news item (accessible via "eselect news"), or a doc where users can read the new features?
Thanks devs for this very long waited release!
_________________
Sapere aude |
|
| Back to top |
|
|
Simba7
l33t
Joined: 22 Jan 2007
Posts: 706
Location: Billings, MT, USA
|
| Posted: Tue Sep 10, 2013 7:52 pm Post subject: |
|
|
I'm having a problem with the 2.2.x series with my MBL (PowerPC-464)
| Code: | >>> Emerging (4 of 39) sys-libs/zlib-1.2.8-r1
* zlib-1.2.8.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking zlib-1.2.8.tar.gz to /var/tmp/portage/sys-libs/zlib-1.2.8-r1/work
>>> Source unpacked in /var/tmp/portage/sys-libs/zlib-1.2.8-r1/work
>>> Preparing source in /var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8 ...
* Will copy sources from /var/tmp/portage/sys-libs/zlib-1.2.8-r1/work/zlib-1.2.8
Unable to handle kernel paging request for data at address 0x015b2cfc
Faulting instruction address: 0xc02727d4
Oops: Kernel access of bad area, sig: 11 [#1]
PowerPC 44x Platform
Modules linked in:
NIP: c02727d4 LR: c0270ed8 CTR: 00000000
REGS: c827bcd0 TRAP: 0300 Not tainted (2.6.32.11-svn70860)
MSR: 00029000 <EE,ME,CE> CR: 88828422 XER: 00000000
DEAR: 015b2cfc, ESR: 00000000
TASK = c829f370[12235] 'ebuild.sh' THREAD: c827a000
GPR00: c0270ed8 c827bd80 c829f370 c827bddc c0bceec0 c072a2a8 00000001 00000000
GPR08: 00000000 015b2cf4 c0730000 c8012998 88828422 100c2d74 00000000 00000000
GPR16: c827be7c fffffff4 c0770000 c827be60 c827be58 00000000 c827be68 000001b6
GPR24: 00010241 00000022 c0bceec0 00001180 c0bceec0 00000000 c827bddc 00000000
NIP [c02727d4] trustee_perm+0x2c/0x264
LR [c0270ed8] trustees_inode_permission+0x250/0x430
Call Trace:
[c827bd80] [c072a2a8] 0xc072a2a8 (unreliable)
[c827bdd0] [c0270ed8] trustees_inode_permission+0x250/0x430
[c827be10] [c026ec68] security_inode_permission+0x30/0x48
[c827be20] [c009c848] inode_permission+0xb8/0xe0
[c827be30] [c009e154] may_open+0xb0/0x1c4
[c827be50] [c00a05f8] do_filp_open+0x1a4/0x8e0
[c827bf10] [c00918e8] do_sys_open+0x64/0x130
[c827bf40] [c000e184] ret_from_syscall+0x0/0x3c
Instruction dump:
4bffff54 9421ffb0 7c0802a6 7d800026 bec10028 90010054 91810024 3d40c073
81630000 80aaa2a8 812b0014 7c9c2378 <83c90008> 7cda3378 93c10008 57c0653e
---[ end trace 6cf1ab24749b1ff4 ]---
/usr/lib/portage/bin/ebuild.sh: line 719: 12235 Segmentation fault ( if [[ -n ${PORTAGE_PIPE_FD} ]]; then
eval "exec ${PORTAGE_PIPE_FD}>&-"; unset PORTAGE_PIPE_FD;
fi; __ebuild_main ${EBUILD_SH_ARGS}; exit 0 )
* The ebuild phase 'prepare' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
>>> Failed to emerge sys-libs/zlib-1.2.8-r1, Log file: |
This only happens after I emerge portage-2.2.x. Every package that I emerge afterwards does this. It works fine with 2.1.12.1. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21591
|
| Posted: Tue Sep 10, 2013 10:25 pm Post subject: |
|
|
| That type of kernel paging error message indicates a kernel bug. The new Portage may exercise the code path to trigger it, but the basic problem is in the kernel. It looks like a 2.6.32.11 kernel, so you should upgrade. |
|
| Back to top |
|
|
EasterParade
l33t
Joined: 26 Jul 2003
Posts: 938
|
| Posted: Wed Sep 11, 2013 8:29 am Post subject: |
|
|
| Quote: | OK, so after humpty-million rc-candidates, portage-2.2.1 has been stabilised. I had to rub my eyes to make sure I wasn't mis-reading it.
Now, I've not been following the testing branch at all, so have no clue what differences this brings. Any chance of a news item or an announcement in the forums? Can someone summarise what's changed?
Presumably one thing that's changed is overlay handling because I got this error message:
Code:
!!! Repository 'x-local' is missing masters attribute in '/usr/portage/local/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
WARNING: One or more repositories have missing repo_name entries:
/usr/portage/local/profiles/repo_name
NOTE: Each repo_name entry should be a plain text file containing a
unique name for the repository on the first line.
Thanks |
Yea  |
|
| Back to top |
|
|
Simba7
l33t
Joined: 22 Jan 2007
Posts: 706
Location: Billings, MT, USA
|
| Posted: Wed Sep 11, 2013 3:31 pm Post subject: |
|
|
| Hu wrote: | | That type of kernel paging error message indicates a kernel bug. The new Portage may exercise the code path to trigger it, but the basic problem is in the kernel. It looks like a 2.6.32.11 kernel, so you should upgrade. |
Love to.. except the device in question requires the 2.6.32.x branch, so the highest I can go is 2.6.32.61. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Wed Sep 11, 2013 6:52 pm Post subject: Re: Portage 2.2 stabilised released! WTF? |
|
|
| tabanus wrote: | | Can someone summarise what's changed? |
Essentially only two features: Sets are now available, and FEATURES=preserve-lib is now default. Both (with appropriate references) is described in /usr/share/doc/portage-2.2.1/NEWS*
| Quote: | | Presumably one thing that's changed is overlay handling |
Actually: no. "repo_names" was supported and recommended since ages; the only change is that portage now prints a warning if it is still not used. The warning says exactly what to do: Give your local overlay a name in the way described in the warning.
| Quote: | | ]!!! Repository 'x-local' is missing masters attribute in '/usr/portage/local/metadata/layout.conf' |
This is a very recent change in portage-2.2 which is just a few days old. However, again the message says exactly what to do to avoid it. Just follow this instruction unless you use a different distribution than gentoo. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Wed Sep 11, 2013 6:56 pm Post subject: |
|
|
| Simba7 wrote: | | Love to.. except the device in question requires the 2.6.32.x branch, so the highest I can go is 2.6.32.61. |
It might be that the bug is triggered by FEATURES="userfetch userspriv usersandbox usersync sandbox" which AFAIK are now all the default and perhaps have not be the default previously. Thus explicitly disabling these features (or at least the one which triggers the kernel bug) might be a workaround (though it would be of course safer to use these features). |
|
| Back to top |
|
|
huuan
Apprentice
Joined: 19 Feb 2007
Posts: 265
Location: California
|
| Posted: Wed Sep 11, 2013 8:38 pm Post subject: |
|
|
| Annagul wrote: | Another surprised user here.
Is there an official announce, or a news item (accessible via "eselect news"), or a doc where users can read the new features?
Thanks devs for this very long waited release! |
One more surprised user here:
| Code: | # emerge -a nano
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility |
Usually there's a news item about stuff like this... |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21591
|
| Posted: Wed Sep 11, 2013 8:51 pm Post subject: |
|
|
| Simba7 wrote: | | Hu wrote: | | That type of kernel paging error message indicates a kernel bug. The new Portage may exercise the code path to trigger it, but the basic problem is in the kernel. It looks like a 2.6.32.11 kernel, so you should upgrade. |
Love to.. except the device in question requires the 2.6.32.x branch, so the highest I can go is 2.6.32.61. |
Kernel 2.6.32.61 would still be 50 releases newer than the one you appear to be running. If you cannot upgrade to a modern mainline kernel, please at least try to upgrade to the latest stable kernel on the major version you are stuck on. |
|
| Back to top |
|
|
Naib
Watchman
Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy
|
| Posted: Wed Sep 11, 2013 9:40 pm Post subject: |
|
|
I remember when it was rc# and then the hardlimit of 99 release candidates within portage was hit so it became alpha#
to be fair wtf could you call it a rc and have 99 release of them each one with significant changes from the last
need a facepalm emote
_________________
| Quote: | | Removed by Chiitoo |
|
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Wed Sep 11, 2013 9:42 pm Post subject: |
|
|
| huuan wrote: | | Usually there's a news item about stuff like this... |
But then the message is completely harmless and crystal clear, isn't it?
| Naib wrote: | | to be fair wtf could you call it a rc and have 99 release of them each one with significant changes from the last |
to be fair there never was one alpha-grade showstopper hit, so it was pretty safe all the while. |
|
| Back to top |
|
|
huuan
Apprentice
Joined: 19 Feb 2007
Posts: 265
Location: California
|
| Posted: Wed Sep 11, 2013 9:54 pm Post subject: |
|
|
| genstorm wrote: | | huuan wrote: | | Usually there's a news item about stuff like this... |
But then the message is completely harmless and crystal clear, isn't it?
| Naib wrote: | | to be fair wtf could you call it a rc and have 99 release of them each one with significant changes from the last |
to be fair there never was one alpha-grade showstopper hit, so it was pretty safe all the while. |
What would have been completely harmless is for the portage upgrade to have done that in its stride, then we would not even be discussing this. Leverage.  |
|
| Back to top |
|
|
Simba7
l33t
Joined: 22 Jan 2007
Posts: 706
Location: Billings, MT, USA
|
| Posted: Thu Sep 12, 2013 3:06 am Post subject: |
|
|
| Hu wrote: | | Kernel 2.6.32.61 would still be 50 releases newer than the one you appear to be running. If you cannot upgrade to a modern mainline kernel, please at least try to upgrade to the latest stable kernel on the major version you are stuck on. |
I am. The problem is I'm compiling this on a WD MyBook Live 3TB, which is running an old version of Debian (Wheezy). I was able to find a replacement kernel (2.6.32.60), and the problem still exists. I currently repartitioned the entire drive and am currently compiling Gentoo on it. So far, I'm having a couple issues.. but I'm ironing them out.
I am curious if anyone tested portage-2.2 on a ppc4xx architecture. |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9521
Location: beyond the rim
|
| Posted: Thu Sep 12, 2013 7:36 am Post subject: |
|
|
| Naib wrote: | I remember when it was rc# and then the hardlimit of 99 release candidates within portage was hit so it became alpha#
to be fair wtf could you call it a rc and have 99 release of them each one with significant changes from the last |
There is no such limit. |
|
| Back to top |
|
|
|
Portage & Programming
