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

Bug#687630: marked as done (unblock: arpack/3.1.1-2.1)

Your message dated Fri, 14 Sep 2012 13:04:46 +0100
with message-id <9d79a18ff8b2788dea4725a9520da79b@mail.adsl.funky-badger.org>
and subject line Re: Bug#687630: unblock: arpack/3.1.1-2.1
has caused the Debian Bug report #687630,
regarding unblock: arpack/3.1.1-2.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 owner@bugs.debian.org
immediately.)


-- 
687630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687630
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package arpack

The only change is the addition of
  Breaks: octave3.2
to libarpack2. This fixes some upgrade paths as noticed and verified in
piuparts.
octave3.2 is an obsolete package that is removed during the upgrade, but
apt may choose a bad timing causing a trigger failure (actually a dpkg
bug, but probably can't be fixed for wheezy).

Andreas

unblock arpack/3.1.1-2.1

diffstat for arpack-3.1.1 arpack-3.1.1

 changelog |   13 +++++++++++++
 control   |    1 +
 2 files changed, 14 insertions(+)

diff -Nru arpack-3.1.1/debian/changelog arpack-3.1.1/debian/changelog
--- arpack-3.1.1/debian/changelog	2012-06-14 10:45:35.000000000 +0200
+++ arpack-3.1.1/debian/changelog	2012-09-13 21:01:02.000000000 +0200
@@ -1,3 +1,16 @@
+arpack (3.1.1-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * libarpack2: add Breaks: octave3.2  (Closes: #684773)
+    This fixes some upgrade paths by removing the obsolete octave3.2 (and its
+    triggers) a bit earlier.  dpkg may run trigger processing of a package
+    even if its dependencies are not satisfied.  The octave3.2 triggers may
+    be run in such a state and will fail, aborting the upgrade, even if
+    octave3.2 would be removed later anyway.
+    This is a dpkg bug, but probably won't be fixed for wheezy (see #678848).
+
+ -- Andreas Beckmann <debian@abeckmann.de>  Thu, 13 Sep 2012 21:01:02 +0200
+
 arpack (3.1.1-2) unstable; urgency=low
 
   * Update the symbol files. Thanks to Nobuhiro Iwamatsu (Closes: #666038)
diff -Nru arpack-3.1.1/debian/control arpack-3.1.1/debian/control
--- arpack-3.1.1/debian/control	2012-04-05 09:53:57.000000000 +0200
+++ arpack-3.1.1/debian/control	2012-09-13 21:01:54.000000000 +0200
@@ -18,6 +18,7 @@
 Depends: ${shlibs:Depends}, ${misc:Depends}, libparpack2
 Replaces: arpack2
 Conflicts: arpack2
+Breaks: octave3.2
 Description: Fortran77 subroutines to solve large scale eigenvalue problems
  ARPACK software is capable of solving large scale symmetric,
  nonsymmetric, and generalized eigenproblems from significant

--- End Message ---
--- Begin Message --- 
On 14.09.2012 12:57, Andreas Beckmann wrote:

Please unblock package arpack

The only change is the addition of
  Breaks: octave3.2
to libarpack2. This fixes some upgrade paths as noticed and verified in 
piuparts.
octave3.2 is an obsolete package that is removed during the upgrade, but apt may choose a bad timing causing a trigger failure (actually a dpkg 
bug, but probably can't be fixed for wheezy).


Unblocked; thanks.

Regards,

Adam

--- End Message ---
Reply to: