The reason is that I distribute many stable and unstable packages through 2 PPA <https://gitlab.com/jean-christophe-manciot/ppa> channels. I would be rather strange to publish an unstable release without its preceding stable version Also, in the case of aptitude, I try to publish only stable versions because it's too much work to publish all unstable releases of all packages.
On Thu, Jan 26, 2017 at 5:52 PM, Axel Beckert <a...@debian.org> wrote: > Hi, > > jean-christophe manciot wrote: > > Do you mean by "build from the HEAD" that the bug has been fixed after > > 0.8.5 tag on the master branch? > > Yes. > > > In which case the unstable commit would be more stable than the > > stable tag commit. > > Speaking of git history, yes. It's not meant to happen, but it happens > occasionally. > > As mentioned before, the patch has been applied in the published > Debian package as used by Debian, Ubuntu and other derivatives. > > > I suggest to tag a new stable version when all this is stabilized. > > I must admit, I'm suprised that anyone uses aptitude from Git and does > not use Git HEAD then (like us developers). > > Regards, Axel > -- > ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ > : :' : | Debian Developer, ftp.ch.debian.org Admin > `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 > `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE > -- Jean-Christophe
