Re: Introducing a new maintainer of libtool

On 17 Jan 2024 18:43, Mike Frysinger wrote: > On 17 Jan 2024 16:09, Ileana Dumitrescu wrote: > > I'll need some time figuring out the release process, but otherwise I > > should be able to get an alpha release out soon. Mike has been helpful > > and has merged in many patches over the past few da

Re: Introducing a new maintainer of libtool

On 17 Jan 2024 16:09, Ileana Dumitrescu wrote: > I'll need some time figuring out the release process, but otherwise I > should be able to get an alpha release out soon. Mike has been helpful > and has merged in many patches over the past few days. there doesn't seem to be libtool-specific relea

Re: Introducing a new maintainer of libtool

On 17 Jan 2024 20:07, Ozkan Sezer wrote: > Please remember to check with debbugs.gnu.org: > https://debbugs.gnu.org/cgi/pkgreport.cgi?package=libtool;max-bugs=100;base-order=1;bug-rev=1 > > There are plenty of bugs in there. E.g.: we're always going to have a bug backlog. if there's something sp

Re: Introducing a new maintainer of libtool

On 17/01/2024 19:07, Ozkan Sezer wrote: Please remember to check with debbugs.gnu.org: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=libtool;max-bugs=100;base-order=1;bug-rev=1 There are plenty of bugs in there. E.g.: Yes, there's quite a lot that have piled up. I'll do my best to triage

Re: Introducing a new maintainer of libtool

On 2024-01-17 20:07:55 +0300, Ozkan Sezer wrote: > Please remember to check with debbugs.gnu.org: > https://debbugs.gnu.org/cgi/pkgreport.cgi?package=libtool;max-bugs=100;base-order=1;bug-rev=1 > > There are plenty of bugs in there. E.g.: > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253 >

Re: Introducing a new maintainer of libtool

Please remember to check with debbugs.gnu.org: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=libtool;max-bugs=100;base-order=1;bug-rev=1 There are plenty of bugs in there. E.g.: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45738 https://deb

[sr #110525] Typos caught by codespell

Follow-up Comment #3, sr#110525 (group libtool): feel free to send a patch to libtool-patches@ for it ___ Reply to this item at: ___ Message sent vi

Re: Introducing a new maintainer of libtool

On 17 Jan 2024 15:56, Simon Josefsson wrote: > Looking at that, it seems the bootstrap and bootstrap.conf scripts are > really old. seems like they're up-to-date to me. it's using the fork: https://github.com/gnulib-modules/bootstrap > Do we have any GitLab CI/CD testing for libtool? there is n

Re: Introducing a new maintainer of libtool

Ileana Dumitrescu writes: >> On 16/01/2024 22:59, Simon Josefsson wrote: >> If what's on git master passes self checks, I would package it and >> prepare an alpha release and announce that to pretesters mailing list. >> Assuming there is nothing in git master that really upsets you and needs >> t

Re: Introducing a new maintainer of libtool

> On 16/01/2024 22:59, Simon Josefsson wrote: If what's on git master passes self checks, I would package it and prepare an alpha release and announce that to pretesters mailing list. Assuming there is nothing in git master that really upsets you and needs to be backed out. Don't look at more

[sr #110525] Typos caught by codespell

Follow-up Comment #2, sr#110525 (group libtool): A residual typo in README.md: ./README.md:234: changsets ==> changesets ___ Reply to this item at: __