Hi,
I made a fresh install of debian squeeze just after its release and
dutifully installed the updates suggested by the package manager
whenever necessary.
1) This morning, I did the same (what the package manager calls a safe
update, no packages where removed or installed) but in between
I made a fresh install of debian squeeze just after its release and
dutifully installed the updates suggested by the package manager
whenever necessary.
What's the content of your sources.list?
2) The only thing that worked was switching between x (ctrl+alt+f7) and
the terminal
On 2011-05-12 12:53 +0200, Jochen Schulz wrote:
udevd[58]: error: runtime directory '/run/udev' not writable, for
now falling back to '/dev/.udev'
That looks like you are actually running testing or unstable.
FWIW, the error message has not been present in udev versions before
168, and that
Eccles, David wrote:
From: Simon Hoerder [mailto:si...@hoerder.net]
1) This morning, I did the same (what the package manager calls a safe
update, no packages where removed or installed) but in between the
update crashed the system.
...
udevd[58]: error: runtime directory '/run/udev' not
Sorry, meant to send it to the list, not just to Jochen.
Jochen Schulz wrote:
I made a fresh install of debian squeeze just after its release and
dutifully installed the updates suggested by the package manager
whenever necessary.
What's the content of your sources.list?
deb
From: Simon Hoerder [mailto:si...@hoerder.net]
1) This morning, I did the same (what the package manager calls a safe
update, no packages where removed or installed) but in between the
update crashed the system.
...
udevd[58]: error: runtime directory '/run/udev' not writable, for now
Simon Hoerder:
deb http://ftp.de.debian.org/debian sid main contrib
That line points to unstable, aka sid. Sid is the permanent alias for
the unstable distribution, unlike the rolling aliases for testing and
stable.
Assuming Sven is correct:
B) Am I correct that the easiest way to return to
Jochen Schulz wrote:
[...]
Since you still have a bootable operating system, you may try the hint
at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450#36.
After taking a second look at Sven's link after lunch I discovered
similar hints there as well. These hints helped to some degree -
Simon Hoerder:
Is there an easy way to remove all unstable packages?
No, at least no easy way I could come up with. You could use aptitude
search to identify installed packages from unstable, remove them and
reinstall them from squeeze. But since you apparently already have libc
from unstable,
On Thu, May 12, 2011 at 6:26 PM, Jochen Schulz m...@well-adjusted.de wrote:
Simon Hoerder:
Is there an easy way to remove all unstable packages?
No, at least no easy way I could come up with. You could use aptitude
search to identify installed packages from unstable, remove them and
Javier Barroso:
So, why not, simply wait one month without upgrading, remove sid from
your sources.list (and keep only wheezy), and then aptitude update;
aptitude safe-upgrade; aptitude full-upgrade ?
Because the OP would still run some kind of more or less mixed
wheezy/sid system even
12/05/2011 14:59, Simon Hoerder wrote:
Jochen Schulz wrote:
[...]
Since you still have a bootable operating system, you may try the hint
at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450#36.
After taking a second look at Sven's link after lunch I discovered
similar hints there as
On Thu, May 12, 2011 at 8:35 PM, Jochen Schulz m...@well-adjusted.de wrote:
Javier Barroso:
So, why not, simply wait one month without upgrading, remove sid from
your sources.list (and keep only wheezy), and then aptitude update;
aptitude safe-upgrade; aptitude full-upgrade ?
Because the OP
Javier Barroso (javibarr...@gmail.com on 2011-05-12 19:11 +0200):
Other possible solution would be pinning all packages from sid to
their current version (upgrading glibc with the bug, of course), and
removing sid from sources.list, and again wait, but this time you
could upgrade your system.
14 matches
Mail list logo
