Re: New libtool maintainer

[Ozkan Sezer]

On 2/8/22, Roumen Petrov  wrote:
> As result is expected Debian to be flooded with defects.
>
>> Some of the outstanding bugs with existing patches :
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38305
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21137
>> (and its dups at 22895, 31900, and 36762)
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21503
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22373
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46559
>>
>> Some of the outstanding bugs without any suggested patches:
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45738
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53479
>
> If those bugs are not Debian specific someone could look at them.

They have nothing to do with debian.

--
O.S.

Re: New libtool maintainer

[Roumen Petrov]

Ozkan Sezer wrote:

On 2/8/22, Julien ÉLIE  wrote:

Hi Alex,


Feel free to reach out if you have pending patches/issues you want to
"bump", ideas for improvements, general advice for a new GNU maintainer
- and above all if you'd like to lend a hand toward getting `libtool' up
and running again.

Many thanks for your work on Libtool!

I believe a good start would be to integrate suggestions and patches
from the issue tracker

https://savannah.gnu.org/patch/?group=libtool

and maybe also some patches Debian (and other distributions) have added
over the years to the last 2.4.6 release.  For instance:

https://sources.debian.org/patches/libtool/2.4.6-15/


We must be very careful with Debian patches!
Only Debian distributes version (valid for 1.4 and 2*) that cannot pass libtool 
regression tests.
As result is expected Debian to be flooded with defects.


Some of the outstanding bugs with existing patches :
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38305
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21137
(and its dups at 22895, 31900, and 36762)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21503
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22373
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46559

Some of the outstanding bugs without any suggested patches:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45738
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53479


If those bugs are not Debian specific someone could look at them.

Libtool projects must not care for defects that shows Debian libtool brokenness.


Regards,
Roumen Petrov

Re: New libtool maintainer

[Ozkan Sezer]

On 2/8/22, Julien ÉLIE  wrote:
> Hi Alex,
>
>> Feel free to reach out if you have pending patches/issues you want to
>> "bump", ideas for improvements, general advice for a new GNU maintainer
>> - and above all if you'd like to lend a hand toward getting `libtool' up
>> and running again.
>
> Many thanks for your work on Libtool!
>
> I believe a good start would be to integrate suggestions and patches
> from the issue tracker
>
>https://savannah.gnu.org/patch/?group=libtool
>
> and maybe also some patches Debian (and other distributions) have added
> over the years to the last 2.4.6 release.  For instance:
>
>https://sources.debian.org/patches/libtool/2.4.6-15/

Some of the outstanding bugs with existing patches :
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38305
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21137
   (and its dups at 22895, 31900, and 36762)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21503
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22373
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46559

Some of the outstanding bugs without any suggested patches:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45738
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53479

Re: New libtool maintainer

[Julien ÉLIE]

Hi Alex,

Feel free to reach out if you have pending patches/issues you want to 
"bump", ideas for improvements, general advice for a new GNU maintainer 
- and above all if you'd like to lend a hand toward getting `libtool' up 
and running again.


Many thanks for your work on Libtool!

I believe a good start would be to integrate suggestions and patches 
from the issue tracker


  https://savannah.gnu.org/patch/?group=libtool

and maybe also some patches Debian (and other distributions) have added 
over the years to the last 2.4.6 release.  For instance:


  https://sources.debian.org/patches/libtool/2.4.6-15/


Personaly, I would of course "bump" one of the patch I provided to make 
--preserve-dup-deps work again:

  https://savannah.gnu.org/patch/?

But I wouldn't mind if that's not your top priority (I perfectly 
understand that).


And thanks again,

--
Julien ÉLIE

« J'oubliais qu'Assurancetourix a une nouvelle corde à sa harpe ! »
  (Astérix)

Re: New libtool maintainer

[Richard Purdie]

On Sun, 2021-11-21 at 13:14 -0600, Alex Ameen wrote:
> I just took a look at those. Good catches on the typos, I probably would 
> not have noticed them just reading the script myself. Same thing with 
> the M4 `[]' quoting issue ( classic pitfall ). I'll get these merged ASAP.
> 
> For the non-Linux patches I can merge them, but I don't have personally 
> have OSX, powerpc, or Solaris boxes, and while I do have a Windows 
> partition I don't currently have it set up to run these kinds of tests. 
> Nonetheless I can merge these - if you have access to any of those 
> platforms let me know if you would be open to running `make check' and 
> posting the logs so I can sanity check the new behavior.
> 
> Thank you so much for bringing these to my attention. There's a long 
> list of old patches and mailing list archives and as a practical matter 
> it's hard to know which of them are still relevant - so I appreciate 
> your help.

I did recently post the better bits of the OpenEmbedded/Yocto Project patchset
for libtool:

https://lists.gnu.org/archive/html/libtool-patches/2021-10/msg00012.html

Those are at up to date and in regular use in OE/YP which is widely used for
cross compiling for Linux/mingw and others. We tend to find sysroot and cross
compile issues in particular and we also find reproducibility and parallel make
race issues.

If you have any questions or concerns on any of those I'm happy to try and help.

Cheers,

Richard

Re: New libtool maintainer

[Alex Ameen]

That would be a huge help. Thanks for the tip, I'm filling out the 
account request stuff now. :)


On 11/21/21 2:04 PM, Russ Allbery wrote:

Alex Ameen  writes:


For the non-Linux patches I can merge them, but I don't have personally
have OSX, powerpc, or Solaris boxes, and while I do have a Windows
partition I don't currently have it set up to run these kinds of
tests. Nonetheless I can merge these - if you have access to any of
those platforms let me know if you would be open to running `make check'
and posting the logs so I can sanity check the new behavior.

For testing INN builds on non-Linux, non-x86 platforms, we use the GCC
Compile farm project:

 https://gcc.gnu.org/wiki/CompileFarm

I am certain they would be happy to give you access as Libtool maintainer.

Re: New libtool maintainer

[Russ Allbery]

Alex Ameen  writes:

> For the non-Linux patches I can merge them, but I don't have personally
> have OSX, powerpc, or Solaris boxes, and while I do have a Windows
> partition I don't currently have it set up to run these kinds of
> tests. Nonetheless I can merge these - if you have access to any of
> those platforms let me know if you would be open to running `make check'
> and posting the logs so I can sanity check the new behavior.

For testing INN builds on non-Linux, non-x86 platforms, we use the GCC
Compile farm project:

https://gcc.gnu.org/wiki/CompileFarm

I am certain they would be happy to give you access as Libtool maintainer.

-- 
Russ Allbery (ea...@eyrie.org) 

Re: New libtool maintainer

[Alex Ameen]

I just took a look at those. Good catches on the typos, I probably would 
not have noticed them just reading the script myself. Same thing with 
the M4 `[]' quoting issue ( classic pitfall ). I'll get these merged ASAP.


For the non-Linux patches I can merge them, but I don't have personally 
have OSX, powerpc, or Solaris boxes, and while I do have a Windows 
partition I don't currently have it set up to run these kinds of tests. 
Nonetheless I can merge these - if you have access to any of those 
platforms let me know if you would be open to running `make check' and 
posting the logs so I can sanity check the new behavior.


Thank you so much for bringing these to my attention. There's a long 
list of old patches and mailing list archives and as a practical matter 
it's hard to know which of them are still relevant - so I appreciate 
your help.



On 11/20/21 2:56 AM, Ozkan Sezer wrote:

On 10/27/21, Alex Ameen  wrote:

Howdy!

This is Alex Ameen reporting in from Austin, Texas. I'm a long time GNU
and `autotools' user who specializes in ELF linking and loading. I'm
writing you today to introduce myself and announce that I was recently
approved as the new maintainer of `libtool'!

I'm excited to bring some updates to the tool and want to thank everyone
for their patience while I work my through the pending patch/bug lists
and get familiar with some of the maintenance infrastructure.

In the near future I look forward to extending `libtool' support for
modern ELF shared objects, and improved integration with the rest of
`autotools'. I'll share a more detailed roadmap after I've worked my
through the pending tasks in the mailing lists.

I want to express my appreciation for all of the `autotools' and
`libtool' maintainers/contributors before me. I understand that
`libtool' is an important piece of infrastructure for a number of
important pieces of software, and I aim to treat modifications and
extensions appropriately with that responsibility in mind ( don't worry
I'm not going to break legacy behavior with reckless abandon haha ).

Feel free to reach out if you have pending patches/issues you want to
"bump", ideas for improvements, general advice for a new GNU maintainer
- and above all if you'd like to lend a hand toward getting `libtool' up
and running again.

Thank you for your time,

-Alex Ameen

It would be nice if the patches for the following long-standing
bugs were applied:


https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21137 (also reported
 duplicately as 22895, 31900 and 36762)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22373
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38305
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46559
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44605 (also see 44684)

And maybe this?
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41837

--
O.S.

Re: New libtool maintainer

[Ozkan Sezer]

On 10/27/21, Alex Ameen  wrote:
> Howdy!
>
> This is Alex Ameen reporting in from Austin, Texas. I'm a long time GNU
> and `autotools' user who specializes in ELF linking and loading. I'm
> writing you today to introduce myself and announce that I was recently
> approved as the new maintainer of `libtool'!
>
> I'm excited to bring some updates to the tool and want to thank everyone
> for their patience while I work my through the pending patch/bug lists
> and get familiar with some of the maintenance infrastructure.
>
> In the near future I look forward to extending `libtool' support for
> modern ELF shared objects, and improved integration with the rest of
> `autotools'. I'll share a more detailed roadmap after I've worked my
> through the pending tasks in the mailing lists.
>
> I want to express my appreciation for all of the `autotools' and
> `libtool' maintainers/contributors before me. I understand that
> `libtool' is an important piece of infrastructure for a number of
> important pieces of software, and I aim to treat modifications and
> extensions appropriately with that responsibility in mind ( don't worry
> I'm not going to break legacy behavior with reckless abandon haha ).
>
> Feel free to reach out if you have pending patches/issues you want to
> "bump", ideas for improvements, general advice for a new GNU maintainer
> - and above all if you'd like to lend a hand toward getting `libtool' up
> and running again.
>
> Thank you for your time,
>
> -Alex Ameen

It would be nice if the patches for the following long-standing
bugs were applied:


https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21137 (also reported
duplicately as 22895, 31900 and 36762)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22373
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38305
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46559
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44605 (also see 44684)

And maybe this?
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41837

--
O.S.

Re: New libtool maintainer

[Pavel Raiskup]

Hello Alex!

On Wednesday, October 27, 2021 4:44:00 AM CEST Alex Ameen wrote:
> Howdy!
> 
> This is Alex Ameen reporting in from Austin, Texas. I'm a long time GNU 
> and `autotools' user who specializes in ELF linking and loading. I'm 
> writing you today to introduce myself and announce that I was recently 
> approved as the new maintainer of `libtool'!
> 
> I'm excited to bring some updates to the tool and want to thank everyone 
> for their patience while I work my through the pending patch/bug lists 
> and get familiar with some of the maintenance infrastructure.
> 
> In the near future I look forward to extending `libtool' support for 
> modern ELF shared objects, and improved integration with the rest of 
> `autotools'. I'll share a more detailed roadmap after I've worked my 
> through the pending tasks in the mailing lists.
> 
> I want to express my appreciation for all of the `autotools' and 
> `libtool' maintainers/contributors before me. I understand that 
> `libtool' is an important piece of infrastructure for a number of 
> important pieces of software, and I aim to treat modifications and 
> extensions appropriately with that responsibility in mind ( don't worry 
> I'm not going to break legacy behavior with reckless abandon haha ).
> 
> Feel free to reach out if you have pending patches/issues you want to 
> "bump", ideas for improvements, general advice for a new GNU maintainer 
> - and above all if you'd like to lend a hand toward getting `libtool' up 
> and running again.
> 
> Thank you for your time,

Thank you for the good news!

I'd happy to help, with my limited time, as much as I can.  Especially if we
could get a Libtool release out soon (that would be awesome).

I wish you happy on-boarding, and success in your maintenance path!
Pavel

> -Alex Ameen
> 
> 
>