[arch-dev-public] iso release? libtool signoffs
>Hi >Life changed here recently, new full time job starts, marrying and >such stuff. >Feel free to update any of my adopted packages, or just orphan them >that someone else can take care of them. > >Cya guys, >greetings >tpowa Is some way this might be the result of the past discussions... Anyway, what about our iso release? tpowa didn't want to have libtool moved before the release. Because I don't expect another new ISO based on his work in the next days I want to push libtool and related packages to core/extra. I know not all devs have checked their packages for rebuilds or just not replied. All known libtool issues have been fixed. I expect more from hidden depends after a move to core but that wouldn't change if we keep libtool longer in testing. opinions? can i get signoffs for libtool 2.2-2? -Andy
Re: [arch-dev-public] iso release? libtool signoffs
On Wed, Mar 26, 2008 at 11:23 AM, Andreas Radke <[EMAIL PROTECTED]> wrote: > Anyway, what about our iso release? tpowa didn't want to have libtool > moved before the release. Because I don't expect another new ISO based > on his work in the next days I want to push libtool and related > packages to core/extra. I know not all devs have checked their packages > for rebuilds or just not replied. All known libtool issues have been > fixed. I expect more from hidden depends after a move to core but that > wouldn't change if we keep libtool longer in testing. > > opinions? can i get signoffs for libtool 2.2-2? This sounds acceptable to me. If all the major libtool related issues have been run into, then I'm cool with it. I will give you a signoff tonight when I make sure I'm fully up to date and everything is running fine. Anyone else?
Re: [arch-dev-public] iso release? libtool signoffs
On Wed, 26 Mar 2008 14:56:20 -0500 "Aaron Griffin" <[EMAIL PROTECTED]> wrote: > On Wed, Mar 26, 2008 at 11:23 AM, Andreas Radke <[EMAIL PROTECTED]> > wrote: > > Anyway, what about our iso release? tpowa didn't want to have > > libtool moved before the release. Because I don't expect another > > new ISO based on his work in the next days I want to push libtool > > and related packages to core/extra. I know not all devs have > > checked their packages for rebuilds or just not replied. All known > > libtool issues have been fixed. I expect more from hidden depends > > after a move to core but that wouldn't change if we keep libtool > > longer in testing. > > > > opinions? can i get signoffs for libtool 2.2-2? > > This sounds acceptable to me. If all the major libtool related issues > have been run into, then I'm cool with it. > > I will give you a signoff tonight when I make sure I'm fully up to > date and everything is running fine. > > Anyone else? Signoff from me, see no problems on my programs here. Maybe we find some more issues after the moving...but I think the most dependencies are rebuilt.
Re: [arch-dev-public] iso release? libtool signoffs
On Wed, 2008-03-26 at 14:56 -0500, Aaron Griffin wrote: > On Wed, Mar 26, 2008 at 11:23 AM, Andreas Radke <[EMAIL PROTECTED]> wrote: > > Anyway, what about our iso release? tpowa didn't want to have libtool > > moved before the release. Because I don't expect another new ISO based > > on his work in the next days I want to push libtool and related > > packages to core/extra. I know not all devs have checked their packages > > for rebuilds or just not replied. All known libtool issues have been > > fixed. I expect more from hidden depends after a move to core but that > > wouldn't change if we keep libtool longer in testing. > > > > opinions? can i get signoffs for libtool 2.2-2? > > This sounds acceptable to me. If all the major libtool related issues > have been run into, then I'm cool with it. > > I will give you a signoff tonight when I make sure I'm fully up to > date and everything is running fine. > > Anyone else? Only issues I have seen is some packages that come with outdated libtool included as symlinks that try to run the old libtool commands through the new libtool. This causes libtool to parse commands completely wrong, resulting in random X processes being fired when building some packages. I've seen several of these packages during gnome 2.22 packaging. A libtoolize --force --copy, followed by the required aclocal, autoconf, automake steps fixes this issue. I don't see the above as an issue with libtool, but as an issue with the sources that distribute libtool as symlinks. In case something fails to build, re-libtoolizing is your friend.
Re: [arch-dev-public] iso release? libtool signoffs
Am Mittwoch, 26. März 2008 17:23:20 schrieb Andreas Radke: > opinions? can i get signoffs for libtool 2.2-2? I am fine with moving in the new libtool. But would it be possible to synchronize this with the postgres bump? (php depends on both; new apache is needed with new php..) -- archlinux.de
Re: [arch-dev-public] iso release? libtool signoffs
I don't know who just moved libtool, but I have to say: REALLY GREAT WORK. Just move libtool and forget all packages that depend on it and have been rebuilt for testing. The whole libtool thing annoyed me anyway: There was never a TODO list created, it was just built, put into testing and left alone. Could we please be more careful about not breaking our system? signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] iso release? libtool signoffs
On Fri, Mar 28, 2008 at 11:05 AM, Thomas Bächler <[EMAIL PROTECTED]> wrote: > I don't know who just moved libtool, but I have to say: REALLY GREAT > WORK. Just move libtool and forget all packages that depend on it and > have been rebuilt for testing. > > The whole libtool thing annoyed me anyway: There was never a TODO list > created, it was just built, put into testing and left alone. > > Could we please be more careful about not breaking our system? So only libtool was moved? Ugh...
Re: [arch-dev-public] iso release? libtool signoffs
Aaron Griffin schrieb: On Fri, Mar 28, 2008 at 11:05 AM, Thomas Bächler <[EMAIL PROTECTED]> wrote: I don't know who just moved libtool, but I have to say: REALLY GREAT WORK. Just move libtool and forget all packages that depend on it and have been rebuilt for testing. The whole libtool thing annoyed me anyway: There was never a TODO list created, it was just built, put into testing and left alone. Could we please be more careful about not breaking our system? So only libtool was moved? Ugh... I sent that mail too early. Only one package was forgotten as far as I can see and it was fixed before I even noticed. It still annoys me. signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] iso release? libtool signoffs
On Fri, 28 Mar 2008 17:41:19 +0100 Thomas Bächler <[EMAIL PROTECTED]> wrote: > Aaron Griffin schrieb: > > On Fri, Mar 28, 2008 at 11:05 AM, Thomas Bächler > > <[EMAIL PROTECTED]> wrote: > >> I don't know who just moved libtool, but I have to say: REALLY > >> GREAT WORK. Just move libtool and forget all packages that depend > >> on it and have been rebuilt for testing. > >> > >> The whole libtool thing annoyed me anyway: There was never a TODO > >> list created, it was just built, put into testing and left alone. > >> > >> Could we please be more careful about not breaking our system? > > > > So only libtool was moved? Ugh... > > I sent that mail too early. Only one package was forgotten as far as > I can see and it was fixed before I even noticed. It still annoys me. > I really don't understand your bother. There was a list at the ML. OK, it wasn't a TODO list in our dev wiki, but is this really sad? I don't think so. As you recognized already all packages were moved, just one was forgotten. So, it was a (nearly) smooth moving. Daniel
