Your message dated Fri, 12 Apr 2013 10:49:33 +0200
with message-id
<CA+7wUsw=zCDO5+T6bY9oNYauecjFqid=jmfy5svhr0dnbfm...@mail.gmail.com>
and subject line
has caused the Debian Bug report #705210,
regarding unblock: mummy/1.0.3-3
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.)
--
705210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705210
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 mummy
As explained on 703332#23 I prepared a testing-proposed-update package. debdiff
attached.
unblock mummy/1.0.3-3
-- System Information:
Debian Release: 6.0.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru mummy-1.0.3/debian/changelog mummy-1.0.3/debian/changelog
--- mummy-1.0.3/debian/changelog 2013-04-01 09:34:42.000000000 +0200
+++ mummy-1.0.3/debian/changelog 2013-04-11 11:59:20.000000000 +0200
@@ -1,3 +1,9 @@
+mummy (1.0.3-3) wheezy; urgency=low
+
+ * Fix ABI version. Closes: #703332
+
+ -- Mathieu Malaterre <[email protected]> Thu, 11 Apr 2013 09:58:20 +0000
+
mummy (1.0.3-2) unstable; urgency=low
* Fix ABI version. Closes: #703332
--- End Message ---
--- Begin Message ---
found 703332 1.0.3-1
thanks
After discussion on debian-cli, here is what we think:
10:41 <directhex> 1) wheezy has 1.0.2
10:41 <directhex> 2) sid has 1.0.3
10:41 <directhex> 3) packages built against 1.0.3 cannot work against 1.0.2
10:42 <directhex> 4) packages built against 1.0.2 cannot work against
1.0.3 unless you add the proposed cligacpolicy
10:42 <directhex> (which would remap version 1.0.2.599 to 1.0.3.599
when a lib tries to load version 1.0.2.599)
10:44 <directhex> 5) if libactiviz.net-cil in wheezy on every
architecture, and libvtkgdcm-cil in wheezy on every architecture
specifically consume version 1.0.2 only, then there is no wheezy RC
bug to fix
10:44 <directhex> 6) if there are any cases where the version in
wheezy expects 1.0.3, those should be binNMU'd
10:45 <malat> both libactiviz.net-cil and libvtkgdcm-cil in wheezy are
against 1.0.2
hence closing 705210
--- End Message ---
