Your message dated Thu, 06 Nov 2014 07:27:34 +0000
with message-id <[email protected]>
and subject line Re: Bug#768215: unblock: owfs/2.9p8-4
has caused the Debian Bug report #768215,
regarding unblock: owfs/2.9p8-4
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 [email protected]
immediately.)
--
768215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768215
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
Please unblock package owfs
Hi,
I uploaded a new version of owfs (2.9p7) in unstable on 2014-10-17.
Talking with upstream, he tells me there is a important bug, so I uploaded
the new upstream version (2.9p8) that fixes it on 2014-10-20.
And here, I missed the fact that 2.9p8 introduced a problem on FreeBSD
until 2014-10-25 (a FreeBSD porter signaled the problem to me). And it took me
3 days (until 2014-10-27) to correctly fix it. And, of course, I missed the
deadline by one day :-(
I would be very pleased if you accept to unblock this package whereas the
reason is not correct according to the freeze policy (ie, I know I ask you to
overule the policy, not to apply it).
I do not add the debdiff here because it is really important (the current
version in testing is 2.9p5-1.1, ie several upstream releases before)
A few remarks:
* owfs has a RC bug : #768115
It is only missing a Breaks/Replaces relation. But, as this bugs is already
present in the current testing version (2.9p5-1.1), I'm waiting for your
decision here to know if I must prepare the fix on top of 2.9p5-1.1 or
2.9p8-4 (probably with an epoch to go through unstable)
* going back to the current testing version will reopen the important bug
#765371 but this bug will be easy to fix
* even if owfs produces library packages, this is a leaf package: to my
knowledge (and apt-cache rdepends results), no other packages depend nor
build-depend on this one.
Regards,
Vincent
unblock owfs/2.9p8-4
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armel
mipsel
Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On 2014-11-06 1:07, Vincent Danjean wrote:
I uploaded a new version of owfs (2.9p7) in unstable on 2014-10-17.
Talking with upstream, he tells me there is a important bug, so I
uploaded
the new upstream version (2.9p8) that fixes it on 2014-10-20.
And here, I missed the fact that 2.9p8 introduced a problem on
FreeBSD
until 2014-10-25 (a FreeBSD porter signaled the problem to me). And it
took me
3 days (until 2014-10-27) to correctly fix it. And, of course, I missed
the
deadline by one day :-(
Actually, you managed to just make it by being lucky with dinstall
timings:
owfs | 2.9p8-4 | testing | source, all
Regards,
Adam
--- End Message ---
