libtool-2.4.7 removed as a "duplicate"?

  • Done
  • quality assurance status badge
Details
3 participants
  • Michael Ford
  • Ludovic Courtès
  • Marius Bakke
Owner
unassigned
Submitted by
Michael Ford
Severity
normal
M
M
Michael Ford wrote on 23 Aug 2022 16:42
(address . bug-guix@gnu.org)
CAFyhPjV8G=nQbt2czJ2T11XjuH6WCYtnu4th0iuUadzbV9g13Q@mail.gmail.com
In commit 5b6b731c7d8ecbae0ead1600b4cd2f70c66d51ca, the libtool-2.4.7
package was removed as a "duplicate". The commit message doesn't explain at
all why libtool 2.4.7 was being removed, or what it was a duplicate of? As
of latest master, libtool is still version 2.4.6.

Thanks.
Attachment: file
L
L
Ludovic Courtès wrote on 1 Sep 2022 15:02
(name . Michael Ford)(address . fanquake@gmail.com)
87a67j459e.fsf@gnu.org
Hi,

Michael Ford <fanquake@gmail.com> skribis:

Toggle quote (5 lines)
> In commit 5b6b731c7d8ecbae0ead1600b4cd2f70c66d51ca, the libtool-2.4.7
> package was removed as a "duplicate". The commit message doesn't explain at
> all why libtool 2.4.7 was being removed, or what it was a duplicate of? As
> of latest master, libtool is still version 2.4.6.

Indeed, I think this commit was intended for ‘core-updates’, where
‘libtool’ *is* 2.4.7, and not for ‘master’.

I’m reverting it on ‘master’. Marius, we’ll have to make sure not to
reintroduce it on the next merge into ‘core-updates’.

Thanks,
Ludo’.
Closed
M
M
Marius Bakke wrote on 1 Sep 2022 16:35
(address . 57356-done@debbugs.gnu.org)
87tu5rb1sr.fsf@gnu.org
Ludovic Courtès <ludo@gnu.org> skriver:

Toggle quote (15 lines)
> Hi,
>
> Michael Ford <fanquake@gmail.com> skribis:
>
>> In commit 5b6b731c7d8ecbae0ead1600b4cd2f70c66d51ca, the libtool-2.4.7
>> package was removed as a "duplicate". The commit message doesn't explain at
>> all why libtool 2.4.7 was being removed, or what it was a duplicate of? As
>> of latest master, libtool is still version 2.4.6.
>
> Indeed, I think this commit was intended for ‘core-updates’, where
> ‘libtool’ *is* 2.4.7, and not for ‘master’.
>
> I’m reverting it on ‘master’. Marius, we’ll have to make sure not to
> reintroduce it on the next merge into ‘core-updates’.

Whoops, sorry for the misunderstanding, and thanks for fixing me! :-)
-----BEGIN PGP SIGNATURE-----

iIUEARYKAC0WIQRNTknu3zbaMQ2ddzTocYulkRQQdwUCYxDDJQ8cbWFyaXVzQGdu
dS5vcmcACgkQ6HGLpZEUEHfk5gEAt5iWbbI9DKgXF43gnit1f0SbrEsyX/o4lY0k
R9rd3lQBAOmL5Ja4NV3nzBNC0RWPAyB/7gYtLZCS2w2uTOZAEz0B
=/YYs
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 57356@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 57356
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch