MantisBT - Doomseeker
View Issue Details
0003546Doomseeker[All Projects] Bugpublic2018-10-08 09:192018-10-13 18:59
WubTheCaptain 
Blzut3 
lowminoralways
closedfixed 
amd64Debian GNU/Linuxbuster/sid
1.1 
1.21.2 
0003546: DRD Team's Debian Package Repository: Lintian warning package-name-doesnt-match-sonames libwadseeker1
libwadseeker package from debian.drdteam.org should be called libwadseeker1, not libwadseeker. This would fix a Lintian "package-name-doesnt-match-sonames libwadseeker1".

More importantly, users may experience a conflict with Debian and my packaging efforts of 0003246 if both libwadseeker and libwadseeker1 would end up installed with library code under two different package names.
$ dpkg -l libwadseeker*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  libwadseeker   1.1          amd64        Mod fetching library for Doom.
This is just a heads up to you, Blzut3. I will be packaging Wadseeker as "libwadseeker1", matching the SONAME.

'https://lintian.debian.org/tags/package-name-doesnt-match-sonames.html [^]'
No tags attached.
related to 0003242closed Blzut3 libwadseeker: Doesn't distinguish version from ELF shared object filename, ABI cannot safely change 
related to 0003246acknowledged  Debian packaging 
Issue History
2018-10-08 09:19WubTheCaptainNew Issue
2018-10-08 09:19WubTheCaptainStatusnew => assigned
2018-10-08 09:19WubTheCaptainAssigned To => Blzut3
2018-10-08 09:22WubTheCaptainNote Added: 0020002
2018-10-08 09:23WubTheCaptainRelationship addedrelated to 0003242
2018-10-08 09:24WubTheCaptainNote Edited: 0020002bug_revision_view_page.php?bugnote_id=20002#r12179
2018-10-08 09:24WubTheCaptainRelationship addedrelated to 0003246
2018-10-08 09:25WubTheCaptainStatusassigned => new
2018-10-08 09:30WubTheCaptainNote Added: 0020003
2018-10-08 09:31WubTheCaptainNote Edited: 0020003bug_revision_view_page.php?bugnote_id=20003#r12181
2018-10-08 09:31WubTheCaptainNote Edited: 0020003bug_revision_view_page.php?bugnote_id=20003#r12182
2018-10-08 09:52WubTheCaptainNote Added: 0020004
2018-10-08 09:56WubTheCaptainNote Edited: 0020002bug_revision_view_page.php?bugnote_id=20002#r12183
2018-10-08 10:10WubTheCaptainStatusnew => assigned
2018-10-08 10:10WubTheCaptainSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=12185#r12185
2018-10-08 10:18WubTheCaptainPrioritynormal => low
2018-10-08 10:18WubTheCaptainStatusassigned => new
2018-10-08 10:22WubTheCaptainNote Added: 0020009
2018-10-08 10:29WubTheCaptainNote Deleted: 0020009
2018-10-08 21:04Blzut3Note Added: 0020036
2018-10-08 21:07Blzut3Note Edited: 0020036bug_revision_view_page.php?bugnote_id=20036#r12203
2018-10-08 22:05WubTheCaptainNote Added: 0020042
2018-10-08 22:05WubTheCaptainStatusnew => needs review
2018-10-08 23:42Blzut3Note Added: 0020046
2018-10-09 10:18WubTheCaptainNote Added: 0020048
2018-10-09 10:18WubTheCaptainStatusneeds review => resolved
2018-10-09 10:18WubTheCaptainResolutionopen => fixed
2018-10-09 10:18WubTheCaptainProduct Version1.2 => 1.1
2018-10-09 10:18WubTheCaptainFixed in Version => 1.2
2018-10-13 18:59WubTheCaptainStatusresolved => closed

Notes
(0020002)
WubTheCaptain   
2018-10-08 09:22   
(edited on: 2018-10-08 09:56)
My proposal: Make libwadseeker a transitional package to libwadseeker1 on debian.drdteam.org.

This takes a trivial modification to the Debian build files in the existing libwadseeker package at debian.drdteam.org to move it. Then you'd create another transitional package, which just depends on libwadseeker1?

(0020003)
WubTheCaptain   
2018-10-08 09:30   
(edited on: 2018-10-08 09:31)
Fyi: libwadseeker 1.1 is unaffected, because it has no SONAME at all. But we still face this issue in the future, irregardless.

(0020004)
WubTheCaptain   
2018-10-08 09:52   
Here's also some guidance on how to make a transitional package:

'https://wiki.debian.org/RenamingPackages [^]'
'https://wiki.debian.org/PackageTransition [^]'
(0020036)
Blzut3   
2018-10-08 21:04   
(edited on: 2018-10-08 21:07)
This is already taken care of behind the scenes.

You can run `make package` and then `../releasescripts/cpackpostprocess.sh` to get the 1.2 release format. (Requires CMake 3.11 or newer for best results.)

(0020042)
WubTheCaptain   
2018-10-08 22:05   
...more if-else-fi soup, yuck. I don't understand the CPack stuff anyway, and I certainly don't understand the script despite reading the description and simplistic bash language code.

Anyway, mind explaining to me if the transitional packaging issue has been resolved?
(0020046)
Blzut3   
2018-10-08 23:42   
I was going to manually create a transition package as you suggested. This is also a transition from me hand jamming files into a deb to using CPack, so this will just happen behind the scenes for the DRD Team repo.
(0020048)
WubTheCaptain   
2018-10-09 10:18   
Resolving as "fixed" for 1.1 in 1.2, but only because of CPack stuff changes (and well, SONAME). There's no good resolution to use here.