Hi Julien,

On 13 May 2020 at 15:25, Julien Cristau wrote:
| Hi Dirk,
| 
| On Wed, May 13, 2020 at 08:05:19 -0500, Dirk Eddelbuettel wrote:
| 
| > 
| > Hi Julien,
| > 
| > On 13 May 2020 at 14:43, Julien Cristau wrote:
| > | Package: libgsl25
| > | Version: 2.6+dfsg-2
| > | Severity: minor
| > | 
| > | libgsl25 has the following relationships:
| > | 
| > | Replaces: gsl, libgsl0 (<= 1.9-4), libgsl0ldbl (<= 1.16+dfsg-4)
| > | Conflicts: gsl, libgsl0, libgsl0ldbl
| > | 
| > | However it does not actually replace or conflict with any of these
| > | (neither did libgsl23) as far as I can tell.  Possibly since libgslcblas
| > | was moved to a separate package?
| > 
| > Possible. Some of these may be old. Do you think I should just remove them
| > now?  (GSL barely moves. This was an upstream release from late last summer
| > than lingered in experimental because I failed to trigger a transition [my
| > fault]).
| > 
| > If we knew what a good fix was I could make a quick upload. Suggestions
| > welcome :)
| > 
| I believe they date back to the days of libgsl.so.0, where the package
| was renamed but the SONAME stayed the same, a couple of times?  Since

I think it is worse in the sense that libgsl DOES have sonames but
libgslcblas from the same source package DOES NOT:

edd@rob:~/deb/gsl(master)$ pkg-config --libs gsl
-lgsl -lgslcblas -lm
edd@rob:~/deb/gsl(master)$ ls -l /usr/lib/x86_64-linux-gnu/libgsl*
-rw-r--r-- 1 root root 5135700 Nov 26  2018 /usr/lib/x86_64-linux-gnu/libgsl.a
-rw-r--r-- 1 root root  473986 Nov 26  2018 
/usr/lib/x86_64-linux-gnu/libgslcblas.a
lrwxrwxrwx 1 root root      20 Nov 26  2018 
/usr/lib/x86_64-linux-gnu/libgslcblas.so -> libgslcblas.so.0.0.0
lrwxrwxrwx 1 root root      20 Nov 26  2018 
/usr/lib/x86_64-linux-gnu/libgslcblas.so.0 -> libgslcblas.so.0.0.0
-rw-r--r-- 1 root root  260064 Nov 26  2018 
/usr/lib/x86_64-linux-gnu/libgslcblas.so.0.0.0
lrwxrwxrwx 1 root root      16 Nov 26  2018 /usr/lib/x86_64-linux-gnu/libgsl.so 
-> libgsl.so.23.1.0
lrwxrwxrwx 1 root root      16 Nov 26  2018 
/usr/lib/x86_64-linux-gnu/libgsl.so.23 -> libgsl.so.23.1.0
-rw-r--r-- 1 root root 2590704 Nov 26  2018 
/usr/lib/x86_64-linux-gnu/libgsl.so.23.1.0
edd@rob:~/deb/gsl(master)$

(From my Ubuntu 19.10 box so one release behind, but that _never_
changed. gslcblas always was 0.0.0.

| the current package no longer shares filenames with those old ones I
| think they can just be removed.  It's quite possible this still applies

I am not having my best day today. What exactly do you suggest by "they can
just be removed"?  Can you make it more explicit?

| to libgslcblas.so.0 though, in which case the libgslcblas0 package
| should probably keep its own Conflicts/Replaces.
| 
| > (And did you mean 'harmful' or 'harmless'?  What 'harm' is being done? Do
| > upgrades balk? A clean install just worked in Docker...)
| > 
| That was my mistake, I initially thought this is what caused the
| non-co-installability with libgsl23, but it's actually harmless, I
| retitled the bug to clarify.  Sorry for any confusion.

No worries, that is how I read it.

Thanks for all the help,  Dirk
 
| Cheers,
| Julien

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to