Hi Mattia,
I have completed the update process to fix bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843053, as discussed.
Package libfolia has a new soname now (new upstream). Packages ucto and frog have been updated
accordingly to depend on it (no new upstream). The three packages are ready for upload now.
Grazie in anticipo,
--
Maarten van Gompel
Centre for Language Studies
Radboud Universiteit Nijmegen
proycon@anaproy.nl
http://proycon.anaproy.nl
http://github.com/proycon
GnuPG key: 0x1A31555C
XMPP: proycon@anaproy.nl Matrix: @proycon:anaproy.nl
Telegram: proycon IRC: proycon (freenode)
Twitter: https://twitter.com/proycon
Bitcoin: 1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd
Quoting Maarten van Gompel (2016-11-13 18:54:27)
> Hi Mattia,
>
> Quoting Mattia Rizzolo (2016-11-13 12:53:25)
> > > Ok, so let me try to get this straight, I've never done this before:
> >
> > don't they say "there is a first time for everyone"? ;)
>
> Right ;)
>
> > [reflowing the points]
> > > * First, don't we have a problem now the transition freeze deadline has passed then?
> > > * Considering the only packages relying on libfolia, both in debian but also in
> > > general, are our own (ucto & frog), can't I just
> > > release the new libfolia package along with a new ucto and frog package that
> > > depend on it and forego on any transitions? (also considering the freeze).
> >
> > In theory, yes.
> > In practise it's fine, the release team don't particularly care for very
> > small transitions like this, expecially if we take care of the rdeps
> > ourself (in this case, just uploading a new version of them).
> > You can also read from the transition freeze announcement email¹ how
> > they are banning "transitions that involve a large number of packages",
> > this surely isn't.
> >
> > The tricky part of being so near to the freeze is that we're doomed if
> > ftpmasters take too much time to process the new package, but these days
> > the risk is pretty low.
> >
> > > * We bump the soname version in libfolia upstream to 5.0.0 (was: 4.0.0) [I'm not sure
> > > what the versioning scheme/convention here is and don't really like that we're in such
> > > high numbers already compared to the actual software version]
> >
> > I don't know your version scheme at all. Just be aware that the SONAME
> > of a library is not tangled with the version of the library (but people
> > expect ABI breakages only at major versions bumps, so…)
>
> Right, I spoke to Joost van Baalen-Ilić today and he also confirmed the differing
> versioning schemes were no problem.
>
> > > * We release upstream and update the debian package
> > > * I bump the libfolia4 package to libfolia5 (and adapt libfolia5.install accordingly )
> > > and make libfolia-dev depend on libfolia5 instead of libfolia4
> > [ * upload ucto and from to have them build against the new library ]
> >
> > yes.
> >
> > > * I add a symbols file to libfolia with dpkg-gensymbols to make things easier for the future
> >
> > this may be hard, and/or require some more studying, so I suggest you
> > defer this and not tangle with the stuff above (but please look into it)
>
> Okay, that sounds like smart advice indeed.
>
> > > Does this sound right?
> >
> > yes.
>
> Ok! Thank you very much, that sounds promising then, I'll talk with my upstream
> colleague and we'll get working on it asap, since frog and ucto are flagged for
> removal no; I assume we have a few days to fix it. I'm expecting to have it
> ready this week.
>
> In the meantime, I'll send out another sponsor request for another new package,
> if you want to pick that up too I'd be happy, if I'm not over-stressing you
> already :)
>
> > I want to link you this KDE doc about ABI stability in C++
> > https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B
> > maybe read it before releasing the new upstream, and take the occasion
> > to do all those changes that you want to do and you know that break the
> > ABI ;)
>
> Good tip, that is indeed some useful reading.
>
> Grazie,
>
> --
>
> Maarten van Gompel
> Centre for Language Studies
> Radboud Universiteit Nijmegen
>
> proycon@anaproy.nl
> http://proycon.anaproy.nl
> http://github.com/proycon
>
> GnuPG key: 0x1A31555C
> XMPP: proycon@anaproy.nl Matrix: @proycon:anaproy.nl
> Telegram: proycon IRC: proycon (freenode)
> Twitter: https://twitter.com/proycon
> Bitcoin: 1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd
Attachment:
signature.asc
Description: signature