Re: Package libburn-1.4.2.pl01.tar.gz as 1.4.2-2 or as 1.4.2.pl01-1 ?
Hi,
>thanks for the answers to my previous question about Multi-Arch.
>Incidentially the next packaging of libburn will happen soon,
>because of an embarrassing bug in its command line frontend cdrskin.
>
>This leads me to my next first-time situation:
>
>There is now upstream
>libburn-1.4.2.pl01.tar.gz
>which replaces
>libburn-1.4.2.tar.gz
>Despite the tarball name it unpacks to ./libburn-1.4.2/.
>
this isn't an issue.
(well, you might want to ask upstream to call it 1.4.2.1 maybe?)
>The effective difference is a single line of source code (plus
>some logging and online documentation files).
>The binary package which actually bears the bug is cdrskin_1.4.2-1.
>
mmm ok, so a sort of shared library issue.
>>Am i right that in this case all packages from libburn_1.4.2-1.dsc
>shall be rebuilt ?
>
I don't get the question, the library has to be rebuilt? yes, I presume so.
All the packages using the library needs a rebuild?
it depends on the change, if it is ABI/API safe, you don't need it, if the change
breaks ABI yes, you need to change soname and rebuild the affected packages.
e.g. adding a field to a struct, or changing a size of a variable used from outside
is an ABI break, and packages doing e.g. sizeof will need a rebuild to understand
the new size (and avoiding a segfault)
>Shall i keep the name scheme by packaging 1.4.2-2 from the buggy
>libburn-1.4.2.tar.gz with a debian/patch file ?
>
>Or shall i package 1.4.2.pl01-1 without patch ?
>At the last such occasion, more than 4 years ago, George Danchev
>packaged 1.1.0.pl01-1.
you can do both, since debian already had a pl01 version you can just upload the new
tarball.
the pro is:
- you have the latest upstream version (uscan and PTS will point to the latest release)
- you have less patches
the con is:
- a new sourceful upload needs time and machine time, people will need to upgrade their package
and so on.
But I think you need to reupload the package anyway, so I would go for the first option.
Moreover having an 1.4.2 with patches that makes it look exactly a 1.4.2.pl01 is somewhat difficult
from the end user point of view.
(I would expect users asking "why can't we have the latest version, hey it was buggy! and you answering
"it is, I just hidden the fix into a quilt patch file")
just before taking a decision, please use dpkg --compare-versions to see if the version is effectively
later than the already in the archive one.
>Have a nice day :)
you too!
HTH
Gianfranco
Reply to: