Hi,
On Samstag, 8. Dezember 2012, intrigeri wrote:
this bug is reproduced by a Jenkins job nicely setup by Holger:
* general information:
http://jenkins.debian.net/job/chroot-test_squeeze_install_gnome_upgrade_to
_wheezy/ * last try:
Hi,
this bug is reproduced by a Jenkins job nicely setup by Holger:
* general information:
http://jenkins.debian.net/job/chroot-test_squeeze_install_gnome_upgrade_to_wheezy/
* last try:
http://jenkins.debian.net/job/chroot-test_squeeze_install_gnome_upgrade_to_wheezy/74/consoleFull
Hi,
I've had this problem several times past weekends trying to install
Wheezy from a fresh Squeeze installation.
The concrete steps to reproduce the problem are:
1) Install Squeeze
2) Change your /etc/apt/sources.list from squeeze to wheezy
3) # apt-get update
4) # apt-get upgrade
5) #
2011/10/18 Michael Biebl bi...@debian.org:
upping the severity a bit as I think apt should be able to upgrade a default
GNOME installation.
Is the transition completed already?
(And what is a default GNOME? Every package from task 'gnome'
installed or package 'gnome' installed or
On Tue, Oct 18, 2011 at 03:52:33AM +0200, Michael Biebl wrote:
severity 645713 important
thanks
upping the severity a bit as I think apt should be able to upgrade a default
GNOME installation.
To testing, yes; but I don't think upgrading default installations of
stable to unstable is
severity 645713 important
thanks
upping the severity a bit as I think apt should be able to upgrade a default
GNOME installation.
Seems I also forgot to attach the dist-upgrade log...
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed
6 matches
Mail list logo
