Bug#705210: unblock: mummy/1.0.3-3
On 2013-04-11 11:53, Mathieu Malaterre wrote:
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package mummy
As explained on 703332#23 I prepared a testing-proposed-update
package. debdiff attached.
unblock mummy/1.0.3-3
Thank you for the upload, although the convention is to submit your
debdiff first and seek permission to upload to tpu.
That matters because, in this case, something seems to have gone wrong
in your branching:
Base version: mummy_1.0.2-5 from testing
Target version: mummy_1.0.3-3 from testing-proposed-updates
+mummy (1.0.3-3) wheezy; urgency=low
+
+ * Fix ABI version. Closes: #703332
+
+ -- Mathieu Malaterre <malat@debian.org> Thu, 11 Apr 2013 09:58:20
+0000
+
+mummy (1.0.3-2) unstable; urgency=low
+
+ * Fix ABI version. Closes: #703332
+ + debian/libkitware-mummy-runtime1.0-cil.cligacpolicy
+
+ -- Mathieu Malaterre <malat@debian.org> Mon, 01 Apr 2013 09:33:20
+0200
+
+mummy (1.0.3-1) unstable; urgency=low
+
+ * New upstream
+ * Bump Std-Vers to 3.9.4, no changes needed
+ * Use dh(9) get hardening for free
+ * Refresh patches (use DEP3 when missing)
+
+ -- Mathieu Malaterre <malat@debian.org> Fri, 15 Mar 2013 14:31:05
+0100
Some of those are most definitely not suitable for Wheezy (I hope
they're obvious enough by now).
An upload to tpu is a cherry-pick of changes in unstable applied to the
package in *testing*, not just a manual upload of the unstable package
to tpu.
Please prepare a diff against the current package in Wheezy and submit
a revised debdiff for consideration. Please use version number
1.0.2-5+deb70u1 (the conventional format) as your previous upload has
now gone to the buildds and can't be revoked (also a good reason to ask
first).
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Reply to: