Bug#854040: marked as done (unblock: iptables/1.6.1)
Your message dated Mon, 20 Feb 2017 19:39:00 +0000
with message-id <63f200a4-d91b-7d77-c3a3-0c4d1a3dc32d@thykier.net>
and subject line Re: Bug#854040: unblock: iptables/1.6.1
has caused the Debian Bug report #854040,
regarding unblock: iptables/1.6.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
854040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854040
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Dear release team,
thanks for your awesome work with Debian. I really appreciate it.
In debian stretch/sid, we currently have iptables 1.6.0+snapshot20161117-5.
Upstream has released iptables 1.6.1, but by the time of the upstream release
I had no time to upload to unstable due to our freeze and the 10 days
testing migration delay.
I, hereby, ask for permission to upload iptables 1.6.1 to unstable targeting
debian stretch.
This request is previous to any effort by my side to package this new
upstream release, so I have no debdiff or the like.
However, I have counted that our package is ~17 commits behind the upstream
code.
There are no hidden interests in this request. Please, decide according
to your needs and the needs of Stretch.
--- End Message ---
--- Begin Message ---
Arturo Borrero Gonzalez:
> Control: tags -1 - moreinfo
>
> On 3 February 2017 at 20:13, Niels Thykier <niels@thykier.net> wrote:
>>
>> Without any additional information, it is hard for us to review this
>> request. The easiest for us is if you attach a source debdiff between
>> testing and unstable plus the change log to the request.
>>
>
> I'm afraid the resulting debdiff resulted in something bigger than I
> expected at first.
>
> Anyway, find it attached.
>
> The cmd used to generate the debdiff was:
>
> % debdiff iptables_1.6.0+snapshot20161117-5.dsc iptables_1.6.1-1.dsc |
> filterdiff -i *.c -i *.patch -i *changelog -i *control > debdiff.diff
>
> The package has not been uploaded to unstable.
>
Hi Arturo,
Thanks for the diff.
I have tried to review it twice now on different occasions and I will
prefer leaving this for buster.
Thanks,
~Niels
--- End Message ---
Reply to: