On Sat, 2013-11-23 at 15:19 +0100, Philipp Kern wrote:
Control: severity -1 important
On Fri, Nov 15, 2013 at 01:01:15PM +0100, Svante Signell wrote:
found 708430 2.00-20
thanks
Ping! Any ideas why nothing happens to this grave bug?
I disagree that it's grave. It's not broken for
Control: severity -1 important
On Fri, Nov 15, 2013 at 01:01:15PM +0100, Svante Signell wrote:
found 708430 2.00-20
thanks
Ping! Any ideas why nothing happens to this grave bug?
I disagree that it's grave. It's not broken for everybody. You copied
the binary to the fallback path to cope
On 2013-11-23 15:26, Svante Signell wrote:
On Sat, 2013-11-23 at 15:19 +0100, Philipp Kern wrote:
Control: severity -1 important
On Fri, Nov 15, 2013 at 01:01:15PM +0100, Svante Signell wrote:
found 708430 2.00-20
thanks
Ping! Any ideas why nothing happens to this grave bug?
I disagree
On Sat, 2013-11-23 at 16:33 +0100, Philipp Kern wrote:
On 2013-11-23 15:26, Svante Signell wrote:
On Sat, 2013-11-23 at 15:19 +0100, Philipp Kern wrote:
Control: severity -1 important
On Fri, Nov 15, 2013 at 01:01:15PM +0100, Svante Signell wrote:
found 708430 2.00-20
thanks
found 708430 2.00-20
thanks
Ping! Any ideas why nothing happens to this grave bug?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
found 708430 2.00-17
thanks
Since this bug report in not closed, I assume the problems remains. (I
have not installed -17 yet, due to the hassle to get a bootable
computer again)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
6 matches
Mail list logo