[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924138: unblock: libnet-duo-perl/1.02-1



Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
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


Reply to: