On Thu, May 7, 2015, at 19:23, Sergio Durigan Junior wrote: > On Thursday, May 07 2015, Frederic Peters wrote: > >> Also, ReceitaNet is often updated, it went from version 4 (tax report of ... > >> This can cause operational issues if rnetclient makes it to Debian > >> stable, since the program must be working perfectly during the tax > >> submission window. ... > > This makes it an appropriate candidate for jessie-updates. > > That is actually a pretty good solution! I am still learning the terms > and the whole process here, but jessie-updates, according to: > > <https://www.debian.org/News/2011/20110215> > (thanks to Cascardo for providing the link) > > would indeed be the ideal place for rnetclient, according to this > criterion: > > - Packages that need to be current to be useful (e.g. clamav).
I am well versed with stable-updates, I upload to it several times per year due to intel-microcode. Unless there is previous arrangement with the stable release managers, an upload to stable-proposed-updates it is not always going to be fast enough for this. "keep current" doesn't mean "rush into stable every time", after all. IMHO, it would be far better to have someone maintain the debian packaging of this stuff upstream, in a "apt-gettable" repository that can be added to sources.list. Such a repository, although unofficial, could be both Debian and Ubuntu-friendly, and target also the LTS branches of Debian and Ubuntu. This side-steps all the issues I raised. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique de Moraes Holschuh <h...@debian.org> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1431041125.3326982.264217493.12bca...@webmail.messagingengine.com
