On Wed, Mar 22, 2017 at 5:19 AM, Samuel Henrique <samuel...@gmail.com> wrote: >> How about building a dummy package from iptraf-ng? > Yeah, that's a much better solution! > > NEW iptraf package containing iptraf-ng and iptraf-ng upgraded to a dummy > package depending on iptraf. > > I was going to ask permission to help you two in the iptraf/iptraf-ng > packaging while getting the package under the pkg-security team some days > before the freeze, but then i thought it would be better to discuss this > after Stretch's release. > > I see that iptraf-ng is on collab-main, i can work there with your > permission and prepare this today (on the next 8 hours). > iptraf will need another upload and its packaging is not on git, so i should > prepare a NMU and put it on mentors (i'm not really sure if a NMU applies on > this case, but my changelog entry can be signed and changed by any of you, > either way). >
I've made a new upload of iptraf-ng providing a transitional dummy package, and updated the Git repo. If you need further changes, please feel free to make changes and upload. > Then we will need to ask for a freeze-unblock of iptraf and iptraf-ng, which > should be accepted without trouble considering the case. > > Of course, that is if you don't prefer to do it yourself, please feel free > to ask for help on any stage. > > Thanks for the quick reply :) > > Samuel Henrique <samueloph> > > 2017-03-21 10:02 GMT-03:00 Aron Xu <a...@debian.org>: >> >> On Tue, Mar 21, 2017 at 3:43 PM, Frederic Peters <fpet...@debian.org> >> wrote: >> > Hi Samuel, >> > >> >> Also, i can help with the fix, given the maintainers permission to do >> >> so. >> > >> > Of course I am totally fine with this. >> > >> >> How about building a dummy package from iptraf-ng? >> >> Aron > >
