Your message dated Sun, 10 Mar 2019 11:32:40 +0000
with message-id <[email protected]>
and subject line Re: Bug#924138: unblock: libnet-duo-perl/1.02-1
has caused the Debian Bug report #924138,
regarding unblock: libnet-duo-perl/1.02-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 [email protected]
immediately.)
--
924138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924138
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
This is an unblock request for a package I've not yet uploaded, since I
wanted to get your guidance on how you'd prefer to get this update.
On March 15th, the Duo API is changing to require pagination be used for
a couple of the API calls implemented by libnet-duo-perl. I want to get
the fix for that into the next stable release, since it otherwise breaks
part of the module. (Bug is #924127.)
There's a new upstream release (1.02) that fixes this as the only code
changes (which also requires a fair bit of work on the test suite), but
also includes various documentation changes. I've prepared a regular
packaging of that new upstream release, including such things as bumping
the debhelper compat level and the standards version. However, I know
we're pretty late in the release cycle.
Would you rather that I:
* Upload 1.02-1 to unstable and have you unblock that for propagation to
testing as a regular package update? This is a leaf package, so I'm
pretty confident that this should be safe, but it has extraneous changes
compared to only fixing this bug.
* Upload 1.02-1 to experimental and prepare a more limited update for
unstable that only backports the relevant upstream change? This will
still require changes to the test suite, so it's not a super-tiny change,
and will still include all the code changes in 1.02-1 (just not the
documentation and packaging changes).
If you have no strong preference, I'd prefer the first since it's simpler,
but I wanted to ask before uploading the package to unstable so that I
didn't lock unstable into the new upstream version and packaging.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Sat, Mar 09, 2019 at 04:23:54PM -0800, Russ Allbery wrote:
> Now uploaded and in unstable, so it should be ready to unblock (unless I
> misunderstood and you meant after the package had aged as well).
Nope - it just has to be in the archive so the version number and contents
are guaranteed. Unblocked - thanks.
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
--- End Message ---
