Hi!
After you solved bug #646620 (the defunct apt-get issue) I upgraded some of
my stable machines suffering from that bug to unattended-upgrades 0.76 and I
started getting mails of packages that could not be upgraded. I though on
opening a new bug, but I believe it is the same issue as this bug (#645382)
and sounds to me that #625847 is also a dupplicate or at least quite similar
issue.
I'll descrive what I'm seeing: the two machines sending these mails are
stable machines to which I have upgraded some packages to testing or
unstable ones by hand and which have APT::Default-Release set to "stable".
On these machines the packages that were upgraded by me do have newer
versions on unstable and unstable is listed on their sources, thus, the
packages should be upgradable if we were to pull them from unstable, but for
dependency reasons they are not unless we go to unstable on other libs or
packages which are from stable.
This is the mail I'm getting from one of them:
----
Unattended upgrade returned: None
Packages that are upgraded:
Packages with upgradable origin but kept back:
roundcube roundcube-core roundcube-plugins
Unattended-upgrades log:
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Debian,n=squeeze',
'o=Debian,n=squeeze,l=Debian-Security']
package 'roundcube' upgradable but fails to be marked for upgrade (E:Unable
to correct problems, you have held broken packages.)
package 'roundcube-core' upgradable but fails to be marked for upgrade
(E:Unable to correct problems, you have held broken packages.)
package 'roundcube-plugins' upgradable but fails to be marked for upgrade
(E:Unable to correct problems, you have held broken packages.)
Packages that are upgraded:
----
I thought that maybe listing the packages in question as blacklisted would
help skip the message but still does the same, this is the log
unattended-upgrades shows now on the other machine after blacklisting the
reported packages:
2012-03-21 09:32:02,056 INFO Initial blacklisted packages: amule-common
amule-daemon asterisk asterisk-config asterisk-modules libwxbase2.8-0
2012-03-21 09:32:02,058 INFO Starting unattended upgrades script
2012-03-21 09:32:02,060 INFO Allowed origins are: ['o=Debian,n=squeeze',
'o=Debian,n=squeeze,l=Debian-Security']
2012-03-21 09:32:14,223 WARNING package 'amule-daemon' upgradable but fails to
be marked for upgrade (E:Unable to correct problems, you have held broken
packages.)
2012-03-21 09:32:18,472 WARNING package 'asterisk' upgradable but fails to be
marked for upgrade (E:Unable to correct problems, you have held broken
packages.)
2012-03-21 09:32:27,112 WARNING package 'asterisk-modules' upgradable but fails
to be marked for upgrade (E:Unable to correct problems, you have held broken
packages.)
2012-03-21 09:32:33,139 WARNING package 'libwxbase2.8-0' upgradable but fails
to be marked for upgrade (E:Unable to correct problems, you have held broken
packages.)
2012-03-21 09:32:41,680 INFO Packages that are upgraded:
The stable version of unattended-upgrades with the very same packages didn't
send any mail and its logs for this last machine were:
2012-03-09 06:37:10,097 INFO Initial blacklisted packages:
2012-03-09 06:37:10,103 INFO Starting unattended upgrades script
2012-03-09 06:37:10,104 INFO Allowed origins are: ["('Debian', 'stable')",
"('Debian', 'squeeze-security')"]
2012-03-09 06:37:17,592 INFO No packages found that can be upgraded unattended
I believe that sending mails when something from your allowed origins fails
to be upgraded is good, but on this case the packages don't have any newer
versions on my allowed origins, they do have them on unstable, which is not
allowed, thus it shouldn't even try to upgrade them (this is how the old
version behaved). Do you think that I should open a new bug for this or on
which of these two I commented should we continue discussing this one?
If the logs and my explanations are not enough just let me know what I
should provide.
Regards...
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
