Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Time to finally finish off with GNOME 2.20 stabling. A list for each arch will be provided in a few hours, meanwhile I'm attaching my working (hopefully final) all arch list version for reference. All this of course depends on the gtk+-2.12 stabling bug and GNOME 2.20 stabling first pass bug being done before this.
Created an attachment (id=136476) [details] All arch working version of the targeted version list (for reference, arch specific lists will follow in subsequent comments)
- libpcre, and evolution is missing from list. - "make check" for evolution fails, The following files contain translations and are currently not in use. Please consider adding these to the POTFILES.in file, located in the po/ directory. evolution-addressbook.xml evolution-calendar.xml evolution-composer-entries.xml evolution-editor.xml evolution-event-editor.xml evolution-mail-global.xml evolution-mail-list.xml evolution-mail-message.xml evolution-mail-messagedisplay.xml evolution-memo-editor.xml evolution-memos.xml evolution-message-composer.xml evolution-signature-editor.xml evolution-subscribe.xml evolution-task-editor.xml evolution-tasks.xml evolution.xml If some of these files are left out on purpose then please add them to POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list of left out files has been written in the current directory. if [ -r missing -o -r notexist ]; then \ exit 1; \ fi make[1]: *** [check] Error 1 make[1]: Leaving directory `/var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po' make: *** [check-recursive] Error 1 * * ERROR: mail-client/evolution-2.12.1 failed.
(In reply to comment #2) > - libpcre, and evolution is missing from list. > > - "make check" for evolution fails, > > The following files contain translations and are currently not in use. Please > consider adding these to the POTFILES.in file, located in the po/ directory. > > evolution-addressbook.xml > evolution-calendar.xml > evolution-composer-entries.xml > evolution-editor.xml > evolution-event-editor.xml > evolution-mail-global.xml > evolution-mail-list.xml > evolution-mail-message.xml > evolution-mail-messagedisplay.xml > evolution-memo-editor.xml > evolution-memos.xml > evolution-message-composer.xml > evolution-signature-editor.xml > evolution-subscribe.xml > evolution-task-editor.xml > evolution-tasks.xml > evolution.xml > > If some of these files are left out on purpose then please add them to > POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list > of left out files has been written in the current directory. > if [ -r missing -o -r notexist ]; then \ > exit 1; \ > fi > make[1]: *** [check] Error 1 > make[1]: Leaving directory > `/var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po' > make: *** [check-recursive] Error 1 > * > * ERROR: mail-client/evolution-2.12.1 failed. > /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 102: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 103: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 104: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 105: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 106: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 107: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 108: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 109: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 110: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 111: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 112: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 113: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 114: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 115: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 116: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 117: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 118: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory
It's executing these echo lines from src_unpack before source is unpacked, sys-apps/portage-2.1.3.19. /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 117: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 118: /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: No such file or directory >>> Unpacking source... >>> Unpacking evolution-2.12.1.tar.bz2 to /var/tmp/portage/mail-client/evolution-2.12.1/work
(In reply to comment #4) > It's executing these echo lines from src_unpack before source is unpacked, > sys-apps/portage-2.1.3.19. > > /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 117: > /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: > No such file or directory > /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 118: > /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: > No such file or directory > >>> Unpacking source... > >>> Unpacking evolution-2.12.1.tar.bz2 to /var/tmp/portage/mail-client/evolution-2.12.1/work > Bah, sorry for bugspam but these echo lines are in (In reply to comment #4) > It's executing these echo lines from src_unpack before source is unpacked, > sys-apps/portage-2.1.3.19. > > /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 117: > /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: > No such file or directory > /usr/portage/mail-client/evolution/evolution-2.12.1.ebuild: line 118: > /var/tmp/portage/mail-client/evolution-2.12.1/work/evolution-2.12.1/po/POTFILES.in: > No such file or directory > >>> Unpacking source... > >>> Unpacking evolution-2.12.1.tar.bz2 to /var/tmp/portage/mail-client/evolution-2.12.1/work > Shrug, ignore me. http://sources.gentoo.org/viewcvs.py/gentoo-x86/mail-client/evolution/evolution-2.12.1.ebuild?r1=1.5&r2=1.6 It was fixed already.
Created an attachment (id=136555) [details] Final stabling list Best viewed in a plan text viewer/editor with tab size set to 4
Arches, please go ahead with GNOME-2.20 stabling as per attachment in comment #6. Assumes bugs #198845 and #199322 are done for your arch
x86 stable
alpha/ia64/sparc stable gnome should die :P
ppc stable; chasing the beagle and evo bugs now...
ppc64 stable. Although I ran into the following problem: while committing galago-daemon-0.5.1: DEPEND.bad 1 sys-apps/galago-daemon/galago-daemon-0.5.1.ebuild: ppc64(default-linux/ppc/ppc64/2006.1/64bit-userland) ['>=dev-libs/libgalago-0.5.2'] So I tried libgalago-0.5.2 first: PDEPEND.bad 1 dev-libs/libgalago/libgalago-0.5.2.ebuild: ppc64(default-linux/ppc/ppc64/2006.1/64bit-userland) ['>=sys-apps/galago-daemon-0.5.1'] Haven't seen this situation before. I committed both "at the same time": keywording one locally without commiting, commiting the other and then commiting the first one...
While syncing I just noted this, and I think it is strange... I hope I don't keep you guys busy for nothing, but...: + 26 Nov 2007; Markus Rothe <corsair@gentoo.org> scrollkeeper-9999.ebuild: + Stable on ppc64; bug #199740 was it really the intention to stable the cvs snapshot for this bug?
No, because it isn't a CVS snapshot. http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.20-upgrade.xml Changes chapter, section about Migration to rarian for explanation.
ohw, ok. Sorry for the noise. I'll add that version then.
If the GNOME bugzilla bug mentioned in bug #201276 is anything to go by, people have been testing/stabilising 2.20 against unstable packages (like python-2.5). Once that bug is fixed, maybe you want to readd those arches that stabilised 2.20 to this bug. Meanwhile, hppa can't go stable until this is fixed.
arm/sh done by Mike...what do you need s390 and m86k for, Gnome team?
(In reply to comment #16) > arm/sh done by Mike...what do you need s390 and m86k for, Gnome team? Exactly what is listed in the attachment with an entry in the s390 or m68k column. If I need to spell it out separately, then: s390: ===== app-text/rarian-0.6.0-r1 app-text/scrollkeeper-9999 dev-libs/libpcre-7.4 gnome-extra/gnome2-user-docs-2.20.1 m68k: ===== app-text/rarian-0.6.0-r1 app-text/scrollkeeper-9999 dev-libs/libpcre-7.4
Done also...man, I am tired about cleaning after vapier...anyway, all done after his arm/m68k/s390/sh stabilisation/keyword spree.
I'm sorry, but none of these arches are done. We need rarian and scrollkeeper-9999 keyworded and ultimately stabled to complete migration to rarian and be able to start thinking of how to get rid of scrollkeeper completely. arm and s390 also miss gnome-extra/gnome2-user-docs-2.20.1
With app-admin/sabayon now keyworded, I think HPPA is done.
From the attached list, arm/sh still have those to do (rekeywording mostly): app-text/scrollkeeper app-text/rarian gnome-extra/yelp media-video/totem gnome-extra/gnome-games-extra-data gnome-extra/gnome-utils
Hi, can this bug be closed?
this bug is deprecated by bug #214260. Closing.
