Discussion:
Processed: transition: coinmp
(too old to reply)
Debian Bug Tracking System
2024-11-19 05:40:01 UTC
Permalink
affects -1 + src:coinmp
Bug #1087818 [release.debian.org] transition: coinmp
Added indication that 1087818 affects src:coinmp
--
1087818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087818
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2024-11-20 09:00:02 UTC
Permalink
tags -1 confirmed
Bug #1087818 [release.debian.org] transition: coinmp
Added tag(s) confirmed.
--
1087818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087818
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Rene Engelhard
2024-11-20 21:30:01 UTC
Permalink
Hi,
 coinmp (1.8.4+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Upload to unstable to start the library transition
Just that it is questionable whether one needed one at all as other distros apparently still get a .so.1 out of 1.8.4.

However they did that.... I wonder whether something is fishy here...


That's why I didn't upload it (yet) to sid.. If you asked me I would have said that.


Ah, well. Now we have that transition...


Regards,


Rene
Rene Engelhard
2024-11-20 23:30:01 UTC
Permalink
Hi,
Post by Rene Engelhard
Hi,
 coinmp (1.8.4+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Upload to unstable to start the library transition
Just that it is questionable whether one needed one at all as other distros apparently still get a .so.1 out of 1.8.4.
However they did that.... I wonder whether something is fishy here...
That's why I didn't upload it (yet) to sid.. If you asked me I would have said that.
Oh, and because of the "autoreconf fails" issue which I *temporarily* (implied by "for now"
in "remoremove autotools-dev usage (for now)" in 1.8.4-1) worked around by not using
autotools-dev.

This then was changed to dh 10 without autoreconf in 1.8.4+dfsg-1 back in 2020.
As long as this was in experimental, that was OK, but for unstable a non-working autoreconf is bad.
What if we ever need to change it for architecture stuff?

Maybe the person who did all uploads so far (and this package was introduced by me initially solely
for libreoffice, and has no other r-dep) should have been asked...

Regards,


Rene
Rene Engelhard
2024-11-21 07:30:01 UTC
Permalink
Hi,
Post by Rene Engelhard
Hi,
Post by Rene Engelhard
Hi,
 coinmp (1.8.4+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Upload to unstable to start the library transition
Just that it is questionable whether one needed one at all as other distros apparently still get a .so.1 out of 1.8.4.
However they did that.... I wonder whether something is fishy here...
That's why I didn't upload it (yet) to sid.. If you asked me I would have said that.
If I understand correctly, you think better coordination would have been useful there. Sorry for not doing so, next time I will.
And that one needs to find out why other distros happily still get a so.1 out of this. I fear so.0 is somehow wrong.


And we become the only distro having this is not ideal(tm)
Sorry, I am not sure to get the problem. Skipping autoreconf has been a current practice for coinor packages for many years, see coinor-cbc, coinor-cgl, coinor-osi, ... for instance. And this has not revealed to be problematic.
Hrrm.
Post by Rene Engelhard
Maybe the person who did all uploads so far (and this package was introduced by me initially solely
for libreoffice, and has no other r-dep) should have been asked...
I admit this. Still, we had the upload of 1.8.4+dfsg-1 by Andreas in experimental,
which I noticed back then, but it just cleaned up packaging, does some questionable things IMHO, but otherwise OK. But that doesn't say anything about experimental->unstable
no open bug about the packaging,
What bug should that be? The changelog and that the SONAME goes backwards whereas other distros don't have that (easily lookable by looking at them) is enough warning signs, IMHO to not just upload..
I commit to monitor the transition and fix things if problems show up, which I don't expect.
I would expect so :)


Still, by pesonal opinion is that we should only upload this until we know why the SONAME changed and whether we really want it and this upload reverted.

Your and the other Science people opinion might differ, but...


Regards,


Rene
Rene Engelhard
2024-11-21 07:40:01 UTC
Permalink
Hi,
[...] that the SONAME goes backwards whereas other distros don't have that (easily lookable by looking at them)
e.g.

https://src.fedoraproject.org/rpms/coin-or-CoinMP/blob/rawhide/f/coin-or-CoinMP.spec#_76
https://archlinux.org/packages/extra/x86_64/coin-or-mp/

Regards,


Rene
Debian Bug Tracking System
2025-01-07 10:50:01 UTC
Permalink
Your message dated Tue, 7 Jan 2025 09:40:58 -0100
with message-id <***@mail.gmail.com>
and subject line Re: Bug#1087818: transition: coinmp
has caused the Debian Bug report #1087818,
regarding transition: coinmp
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
1087818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087818
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...