On Tue, Apr 8, 2008 at 11:08 AM, Thomas Bächler <[EMAIL PROTECTED]> wrote: > Aaron Griffin schrieb: > > > > On Tue, Apr 8, 2008 at 3:48 AM, Simo Leone <[EMAIL PROTECTED]> wrote: > > > > > Hey guys, do *NOT* try these out quite yet. Removing packages from a db > > > results in a segfault that leaves it on the web db, which will quickly > > > desync it and make a mess. > > > http://bugs.archlinux.org/task/10114 > > > > > > > Bah, how often do we remove packages anyway. It's still fine for > > upgrades - the "do *NOT*" warning is jumping the gun. > > I will fix this when I get a chance. > > Everytime we remove something from testing to move it to core/extra. Due to > the signoff rule, that happens a lot.
I just meant that the previous email sounded like a "Everyone panic!" email... but it's really not a huge deal. I may have just fixed it anyway. > > > /usr/bin/communitypkg is merely a symlink to /usr/bin/extrapkg, and > > > extrapkg has the svn commit lines instead of the CVS lines needed for > > > community. I'm not sure if this is "bug worthy", but I opened a bug > > > in community packages so TU's have a reference: > > > > > > http://bugs.archlinux.org/task/10118 > > > > > > To all TU's, either downgrade or don't upgrade devtools until this can > > > be fixed. I mean, you could always use "cvs commit". > > > > > > > Good catch. I didn't even pick up on that one. Now the kicker - how > > quickly can I/we get the community daemon converted vs putting out a > > new devtools package? Which way should we go? > > > > Instead of a symlink, use the old (CVS-)extrapkg as communitypkg. That will > effectively fix communitypkg, so you can take your time to convert > community. As I understand you, no work has been done on that yet. Hmm, that's probably be the path of least resistance - Jason, opinions?
