Version in base suite: 3.2.0-1
Base version: libapache2-mod-rivet_3.2.0-1
Target version: libapache2-mod-rivet_3.2.1-1
Hi,
On Sat, 2021-11-13 at 20:03 +0000, Debian Queue Viewer wrote:
Version in base suite: 3.2.0-1
Base version: libapache2-mod-rivet_3.2.0-1
Target version: libapache2-mod-rivet_3.2.1-1
+libapache2-mod-rivet (3.2.1-1) stable; urgency=medium
+
+ * New upstream release.
+ * New rivet version addresses issue with multiple AM_AUTOMAKE_INIT
+ expansion (Closes: #998490).
+ * Correcting the name of the target directory where rivet library and
+ Tcl scripts are moved into (it still had the old 3.1 version name)
I'm assuming that you intended to upload this to unstable, not stable.
If targetting stable was actually intentional, then I'm afraid that you
need to fix the issue in unstable before we can consider accepting it
for stable.
On Sat, Nov 13, 2021 at 08:27:39PM +0000, Adam D. Barratt wrote:
Hi,
On Sat, 2021-11-13 at 20:03 +0000, Debian Queue Viewer wrote:
Version in base suite: 3.2.0-1
Base version: libapache2-mod-rivet_3.2.0-1
Target version: libapache2-mod-rivet_3.2.1-1
+libapache2-mod-rivet (3.2.1-1) stable; urgency=medium
+
+ * New upstream release.
+ * New rivet version addresses issue with multiple
AM_AUTOMAKE_INIT
+ expansion (Closes: #998490).
+ * Correcting the name of the target directory where rivet
library and
+ Tcl scripts are moved into (it still had the old 3.1 version
name)
I'm assuming that you intended to upload this to unstable, not
stable.
If targetting stable was actually intentional, then I'm afraid that
you
need to fix the issue in unstable before we can consider accepting
it
for stable.
Hello Adam,
yes that was intended to be uploaded to unstable, I missed the issue
and I screwed that up as the sponsor. Please remove the package from
the queue.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 234:47:05 |
Calls: | 6,624 |
Files: | 12,172 |
Messages: | 5,319,700 |