Bug#866693: marked as done (nmu: jpy_0.8-5)
Your message dated Wed, 5 Jul 2017 00:44:00 +0200
with message-id <f436da59-2b8c-49be-64d9-abbcd79bfc96@debian.org>
and subject line Re: Bug#866693: nmu: jpy_0.8-5
has caused the Debian Bug report #866693,
regarding nmu: jpy_0.8-5
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.)
--
866693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866693
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: binnmu
nmu jpy_0.8-5 . ANY . unstable . -m "Rebuild with debhelper 10.6.1"
That package seems to be affected by #866572, too.
Does this need extra-depends on that debhelper version ?
Andreas
--- End Message ---
--- Begin Message ---
On 2017-07-04 21:49, Emilio Pozuelo Monfort wrote:
>> nmu jpy_0.8-5 . ANY . unstable . -m "Rebuild with debhelper 10.6.1"
>>
>> That package seems to be affected by #866572, too.
>
> Is it? Can point out why? I can't find any weird files on the amd64 or arm64
> python-jpy binaries.
That had a sourceful upload inbetween. There were file overwrite
conflicts in my piuparts instance.
Andreas
--- End Message ---
Reply to: