Bug#614517: Info received (Bug#614517: Packaging of libgit2
Hey Bálint,
Bálint Réczey <balint@balintreczey.hu> writes:
>>> Why does the absence of 1.0 version prevent the upload to unstable?
>>> There has been many 0.xx releases and the package can be blocked from
>>> migration to testing if it is really not ready for being released as
>>> part of Debian.
>>> I would like to upload a package depending on libgit2, thus i would
>>> like to see libgit2
>>> in unstable. :-)
>> I don't know too much about blocking things from testing but I believe
>> this is not recommended practice. The problem is that the API is
> Filing a blocker RC bug is widely used when the package is not considered
> to be ready or useful as part of the stable distributuion:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=414385
>> changing in backwards incompatible ways with every version change. So
>> the reason it's in experimental is because it is a more appropriate
>> place for a package that is undergoing these kinds of changes. You will
>> still able to access the package from the experimental repository and
>> any packages that depend will probably need to be uploaded to
>> experimental. I would also recommend adding a dependency on the
>> specific version i.e. 0.16 because there are already symbol renames in
>> master that will break compatibility.
> In case of young libraries it is normal, IMO it could be part of stable.
I don't think using a blocker RC bug is really justified in this case.
For a start this library is not actually in Debian yet, so it is not
going to break any other packages. By putting it in unstable there is
an implicit agreement that the package will progress to testing. By
putting the library in experimental it's much clearer what the current
state of the library is, which is that every version will likely break
all client libraries and there will be no bug fix releases. The library
is young, and I think putting the library into unstable it will be
misrepresenting the actual state of the library.
You will still be able to upload your package, but you will need to
upload it to experimental.
Cheers,
Russell
Reply to: