Package: shinken Version: 2.0.3-3 Severity: serious Tags: patch User: debian...@lists.debian.org Usertags: piuparts
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, i.e.
the old packages from wheezy are kept installed rather than upgraded.
>From the attached log (scroll to the bottom...):
Starting 2
Investigating (0) shinken-common [ amd64 ] < none -> 2.0.3-3 > ( net )
Broken shinken-common:amd64 Breaks on shinken-core [ amd64 ] < 0.6.5-2 > (
net ) (< 1.4)
Considering shinken-core:amd64 5 as a solution to shinken-common:amd64 1
Holding Back shinken-common:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-mod-webui [ amd64 ] < none -> 1.0-1 > ( net )
Broken shinken-mod-webui:amd64 Depends on shinken-common [ amd64 ] < none ->
2.0.3-3 > ( net )
Considering shinken-common:amd64 1 as a solution to shinken-mod-webui:amd64 0
Holding Back shinken-mod-webui:amd64 rather than change shinken-common:amd64
Investigating (0) shinken-mod-pickle-retention-file-generic [ amd64 ] < none
-> 1.4.1-2 > ( net )
Broken shinken-mod-pickle-retention-file-generic:amd64 Depends on
shinken-common [ amd64 ] < none -> 2.0.3-3 > ( net )
Considering shinken-common:amd64 1 as a solution to
shinken-mod-pickle-retention-file-generic:amd64 0
Holding Back shinken-mod-pickle-retention-file-generic:amd64 rather than
change shinken-common:amd64
Investigating (0) shinken [ amd64 ] < 0.6.5-2 -> 2.0.3-3 > ( net )
Broken shinken:amd64 Depends on shinken-common [ amd64 ] < none -> 2.0.3-3 >
( net ) (= 2.0.3-3)
Considering shinken-common:amd64 1 as a solution to shinken:amd64 -1
Holding Back shinken:amd64 rather than change shinken-common:amd64
Try to Re-Instate (1) shinken:amd64
Done
The following NEW packages will be installed:
[...]
The following packages have been kept back:
shinken
The following packages will be upgraded:
[...]
The attached patch fixes this by readding an empty dummy shinken-core package.
Afterwards the problemresolver does this:
Starting 2
Investigating (0) shinken-poller [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-poller:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2 ->
2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-poller:amd64 -2
Removing shinken-poller:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-receiver [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-receiver:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2 ->
2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-receiver:amd64 -2
Removing shinken-receiver:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-broker [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-broker:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2 ->
2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-broker:amd64 -2
Removing shinken-broker:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-scheduler [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-scheduler:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2 ->
2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-scheduler:amd64 -2
Removing shinken-scheduler:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-reactionner [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-reactionner:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2
-> 2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-reactionner:amd64
-2
Removing shinken-reactionner:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-discovery [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-discovery:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2 ->
2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-discovery:amd64 -2
Removing shinken-discovery:amd64 rather than change shinken-core:amd64
Investigating (0) shinken-arbiter [ amd64 ] < 0.6.5-2 > ( net )
Broken shinken-arbiter:amd64 Depends on shinken-core [ amd64 ] < 0.6.5-2 ->
2.0.3-4 > ( net ) (= 0.6.5-2)
Considering shinken-core:amd64 7 as a solution to shinken-arbiter:amd64 -2
Removing shinken-arbiter:amd64 rather than change shinken-core:amd64
Done
The following packages will be REMOVED:
shinken-arbiter shinken-broker shinken-discovery shinken-poller
shinken-reactionner shinken-receiver shinken-scheduler
The following NEW packages will be installed:
[...]
The following packages will be upgraded:
[...]
cheers,
Andreas
shinken_2.0.3-3.log.gz
Description: application/gzip
diff -Nru shinken-2.0.3/debian/changelog shinken-2.0.3/debian/changelog
--- shinken-2.0.3/debian/changelog 2014-11-11 16:31:45.000000000 +0100
+++ shinken-2.0.3/debian/changelog 2015-01-28 16:45:43.000000000 +0100
@@ -1,3 +1,10 @@
+shinken (2.0.3-4) UNRELEASED; urgency=medium
+
+ * Reintroduce transitional shinken-core package for smooth upgrades from
+ wheezy. (Closes: #xxxxxx)
+
+ -- Andreas Beckmann <a...@debian.org> Wed, 28 Jan 2015 16:44:19 +0100
+
shinken (2.0.3-3) unstable; urgency=medium
[ Thibault Cohen ]
diff -Nru shinken-2.0.3/debian/control shinken-2.0.3/debian/control
--- shinken-2.0.3/debian/control 2014-11-11 16:31:45.000000000 +0100
+++ shinken-2.0.3/debian/control 2015-01-28 16:47:53.000000000 +0100
@@ -49,3 +49,9 @@
Shinken is a new, Nagios compatible monitoring tool, written in Python. The
main goal of Shinken is to allow users to have a fully flexible architecture
for their monitoring system that can easily scale to large environments.
+
+Package: shinken-core
+Architecture: all
+Depends: ${misc:Depends}
+Description: transitional dummy package to ensure smooth upgrades to wheezy
+ This empty package can be safely removed.
