Hi.
It turned out that the problem was related to LVM partitions not being
"available" while "systemd" was trying to run "fsck" on them.
In maintenance mode, I just ran
# vgchange -a y theVolumeGroupName
and they were automatically detected, and mounted.
Then the boot sequence could proceed no
Package: upgrade-reports
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
I first ran
# aptitude safe-upgrade
which completed successfully.
["aptitude" automatically selected packages related to "console".]
I then installed the linu
Package: openjdk-6-jre
Version: 6b18-1.8.5-1
Severity: important
Hello.
I just wanted to mention that the bug is not limited to remote access. It is
triggered by any attempt to parse the decimal representation of the
problematic numbers. In particular, when such a representation appears in
source
Hi.
I must apologize for my previous post: I was using "reportbug" and it didn't
show the full history of the bug which I had selected (which led me to believe
that the original report hadn't been taken care of...).
[Nevertheless it's fairly misleading that "reportbug" doesn't provide the
full hi
Package: skencil
Version: 0.6.17-16
Followup-For: Bug #524554
Hi.
I see that no follow-up has been provided to the original report; is this
software still maintained in Debian?
Best,
Gilles
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstabl
Hi.
That was a quick reply; thanks!
[And it was too quick a report too (see below).]
> > --- Package information. ---
> > Depends (Version) | Installed
> > =-+-===
> > python (>= 2.4) | 2.4.4-6
>
> Is this version the default on your
Package: reportbug
Version: 3.43
Severity: critical
--- Please enter the report below this line. ---
Hi.
Trying to run the program:
$ reportbug
Traceback (most recent call last):
File "/usr/bin/reportbug", line 1823, in ?
main()
File "/usr/bin/reportbug", line 832, in main
lib_packa
7 matches
Mail list logo
