Hi Mattia,
Quoting Mattia Rizzolo (2016-11-23 22:29:46)
> > Ok, so you're saying I don't need to force a higher libfolia version despite
> > the new so version? Will bug
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843053 still be fixed this
> > way?
>
> exactly, you don't need to force the new version. you only need to
> rebuild the package against the new soversion.
Right, that makes sense.
> > > for ucto:
> >
> > Ok, I reverted the changes, it's indeed a no-change upload then, no version
> > number change at all, is that valid?
>
> umh, no. I can't upload the same package/version, there need to be bump
> on the version of some kind. Just add a new changelog entry without
> doing anything else at all (that's also what binNMUs do
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu-binnmu)
Ok, as I suspected, I added a new changelog entry again. Does it look okay now?
Ciao,
--
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