Your message dated Tue, 03 Feb 2015 17:37:30 +0100 with message-id <54d0f94a.4000...@debian.org> and subject line Re: Bug#776477: tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades has caused the Debian Bug report #776477, regarding tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades 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 ow...@bugs.debian.org immediately.) -- 776477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: tomcat7 Version: 7.0.56-1 Severity: serious Tags: patch User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + solr-tomcat Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. Even after the upgrade it is not possible to install solr-tomcat again (without removing tomcat6 manually). >From the attached log (scroll to the bottom...): [ wheezy# apt-get distupgrade ] Starting 2 Investigating (0) libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] < 6.0.35-6+deb7u1 -> 6.0.41-2 > ( java ) Considering libtomcat6-java:amd64 2 as a solution to libtomcat7-java:amd64 0 Holding Back libtomcat7-java:amd64 rather than change libtomcat6-java:amd64 Investigating (0) tomcat7-common [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken tomcat7-common:amd64 Depends on libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) (>= 7.0.56-1) Considering libtomcat7-java:amd64 0 as a solution to tomcat7-common:amd64 0 Holding Back tomcat7-common:amd64 rather than change libtomcat7-java:amd64 Investigating (1) tomcat7 [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken tomcat7:amd64 Depends on tomcat7-common [ amd64 ] < none -> 7.0.56-1 > ( java ) (>= 7.0.56-1) Considering tomcat7-common:amd64 0 as a solution to tomcat7:amd64 1 Holding Back tomcat7:amd64 rather than change tomcat7-common:amd64 Investigating (2) solr-tomcat [ amd64 ] < 3.6.0+dfsg-1+deb7u1 -> 3.6.2+dfsg-5 > ( java ) Broken solr-tomcat:amd64 Depends on tomcat7 [ amd64 ] < none -> 7.0.56-1 > ( java ) Considering tomcat7:amd64 1 as a solution to solr-tomcat:amd64 2 Removing solr-tomcat:amd64 rather than change tomcat7:amd64 Done The following packages will be REMOVED: solr-tomcat Removing the package to be tested is not optimal, but sometimes unavoidable. So let's reinstall afterwards. [ jessie# apt-get install solr-tomcat ] Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) tomcat6-common [ amd64 ] < 6.0.41-2 > ( java ) Broken tomcat6-common:amd64 Depends on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) (>= 6.0.41-2) Considering libtomcat6-java:amd64 -1 as a solution to tomcat6-common:amd64 1 Added libtomcat6-java:amd64 to the remove list Fixing tomcat6-common:amd64 via keep of libtomcat6-java:amd64 Investigating (0) libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) Considering libtomcat6-java:amd64 -1 as a solution to libtomcat7-java:amd64 0 Added libtomcat6-java:amd64 to the remove list Fixing libtomcat7-java:amd64 via remove of libtomcat6-java:amd64 Investigating (1) tomcat6-common [ amd64 ] < 6.0.41-2 > ( java ) Broken tomcat6-common:amd64 Depends on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) (>= 6.0.41-2) Considering libtomcat6-java:amd64 -1 as a solution to tomcat6-common:amd64 1 Added libtomcat6-java:amd64 to the remove list Fixing tomcat6-common:amd64 via keep of libtomcat6-java:amd64 Investigating (1) libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) Considering libtomcat6-java:amd64 -1 as a solution to libtomcat7-java:amd64 0 Added libtomcat6-java:amd64 to the remove list Fixing libtomcat7-java:amd64 via remove of libtomcat6-java:amd64 Investigating (2) tomcat6-common [ amd64 ] < 6.0.41-2 > ( java ) Broken tomcat6-common:amd64 Depends on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) (>= 6.0.41-2) Considering libtomcat6-java:amd64 -1 as a solution to tomcat6-common:amd64 1 Added libtomcat6-java:amd64 to the remove list Fixing tomcat6-common:amd64 via keep of libtomcat6-java:amd64 Investigating (2) libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) Considering libtomcat6-java:amd64 1 as a solution to libtomcat7-java:amd64 0 Holding Back libtomcat7-java:amd64 rather than change libtomcat6-java:amd64 Investigating (2) tomcat7-common [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken tomcat7-common:amd64 Depends on libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) (>= 7.0.56-1) Considering libtomcat7-java:amd64 0 as a solution to tomcat7-common:amd64 0 Holding Back tomcat7-common:amd64 rather than change libtomcat7-java:amd64 Investigating (3) tomcat7 [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken tomcat7:amd64 Depends on tomcat7-common [ amd64 ] < none -> 7.0.56-1 > ( java ) (>= 7.0.56-1) Considering tomcat7-common:amd64 0 as a solution to tomcat7:amd64 0 Holding Back tomcat7:amd64 rather than change tomcat7-common:amd64 Investigating (4) solr-tomcat [ amd64 ] < none -> 3.6.2+dfsg-5 > ( java ) Broken solr-tomcat:amd64 Depends on tomcat7 [ amd64 ] < none -> 7.0.56-1 > ( java ) Considering tomcat7:amd64 0 as a solution to solr-tomcat:amd64 10001 Re-Instated libtomcat7-java:amd64 Re-Instated tomcat7-common:amd64 Re-Instated tomcat7:amd64 Investigating (4) libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] < 6.0.41-2 > ( java ) Considering libtomcat6-java:amd64 1 as a solution to libtomcat7-java:amd64 0 Holding Back libtomcat7-java:amd64 rather than change libtomcat6-java:amd64 Investigating (4) tomcat7-common [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken tomcat7-common:amd64 Depends on libtomcat7-java [ amd64 ] < none -> 7.0.56-1 > ( java ) (>= 7.0.56-1) Considering libtomcat7-java:amd64 0 as a solution to tomcat7-common:amd64 0 Holding Back tomcat7-common:amd64 rather than change libtomcat7-java:amd64 Investigating (5) tomcat7 [ amd64 ] < none -> 7.0.56-1 > ( java ) Broken tomcat7:amd64 Depends on tomcat7-common [ amd64 ] < none -> 7.0.56-1 > ( java ) (>= 7.0.56-1) Considering tomcat7-common:amd64 0 as a solution to tomcat7:amd64 0 Holding Back tomcat7:amd64 rather than change tomcat7-common:amd64 Investigating (6) solr-tomcat [ amd64 ] < none -> 3.6.2+dfsg-5 > ( java ) Broken solr-tomcat:amd64 Depends on tomcat7 [ amd64 ] < none -> 7.0.56-1 > ( java ) Considering tomcat7:amd64 0 as a solution to solr-tomcat:amd64 10001 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: solr-tomcat : Depends: tomcat7 but it is not going to be installed E: Unable to correct problems, you have held broken packages. The attached patch adds Package: libtomcat7-java Conflicts: tomcat6, tomcat6-common This at least fixes the installation of solr-tomcat in jessie since this will ensure the removal of tomcat6. It does not prevent to (temporary) removal of solr-tomcat during the distupgrade to jessie. That would require Breaks: tomcat6, tomcat6-common, libtomcat6-java in a (possibly unrelated) package with sufficiently high score. The upgrade situation might clear up if the tomcat6, tomcat6-common binary packages get removed from jessie (src:tomcat6 in sid only build some java libraries, but no longer tomcat6 etc). But as long as tomcat6 is installed and a valid install candidate, apt-get gives "install tomcat7 instead" a too low score. cheers, Andreasdiff --git a/debian/changelog b/debian/changelog index 6bb4dc3..55b6dfa 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +tomcat7 (7.0.56-2) UNRELEASED; urgency=medium + + * libtomcat7-java: Add Conflicts: tomcat6, tomcat6-common to fix some + upgrade paths that involve switching from tomcat6 to tomcat7. + (Closes: #xxxxxx) + + -- Andreas Beckmann <a...@debian.org> Wed, 28 Jan 2015 01:45:09 +0100 + tomcat7 (7.0.56-1) unstable; urgency=medium * New upstream release diff --git a/debian/control b/debian/control index 94617b5..ab193d2 100644 --- a/debian/control +++ b/debian/control @@ -80,7 +80,7 @@ Depends: libecj-java, libcommons-pool-java, libcommons-dbcp-java, libservlet3.0-java (>= ${source:Version}), ${misc:Depends} -Conflicts: libtomcat6-java +Conflicts: tomcat6, tomcat6-common, libtomcat6-java Suggests: tomcat7 (>= ${source:Version}) Description: Servlet and JSP engine -- core libraries Apache Tomcat implements the Java Servlet and the JavaServer Pages (JSP)
t7.0.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---On 2015-01-28 14:29, Emmanuel Bourg wrote: > tomcat6 is going to be removed from Jessie but the update hasn't > migrated yet (see #770769). src:tomcat6 will only build > libservlet2.5-java. Will that solve this upgrade issue? now that it migrated, tomcat6 removal has smoothened this upgrade path, thus closing. Andreas
--- End Message ---
