2.1.5 github releases deb upgrade from 2.1.4 changes package name from liquidsoap to liquidsoap-fb688f6

[mailinglists35]

on debian/ubuntu is not expected for packages to change names between updates. perhaps this is a mistake?

$ dpkg -l liquidsoap
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  liquidsoap     1:2.1.4-ubuntu-jammy-1 amd64        audio and video streaming language

$ sudo eatmydata apt install ./liquidsoap-fb688f6_2.1.5-ubuntu-jammy-1_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'liquidsoap-fb688f6' instead of './liquidsoap-fb688f6_2.1.5-ubuntu-jammy-1_amd64.deb'
Suggested packages:
  awscli
The following packages will be REMOVED:
  liquidsoap
The following NEW packages will be installed:
  liquidsoap-fb688f6
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B/10.4 MB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

[toots]

This is by design. The problem is that rolling releases are tracked using git commit sha and those are not ordered numbers that can be used for release. Thus, the packages are named using the github commit sha and conflict with each other.

Other than the naming, there shouldn't be any issue with the content and etc.

[mailinglists35]

the problem is not the file name, but the package naming. this is the first time in 15 years of using debian/ubuntu that I observe this policy, when an upgrade changes the package name. you can still do rolling releases and keep the package name.