Your message dated Thu, 28 Dec 2006 18:16:30 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:07:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:15:28 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:26:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Processing commands for [EMAIL PROTECTED]:
> reassign 404775 dwww
Bug#404775: iceweasel: upgrade fails from 2.0+dfsg-1 to 2.0.0.1+dfsg-1
Bug reassigned from package `iceweasel' to `dwww'.
> # patch is under way
> found 404775 1.10.0
Bug#404775: iceweasel: upgrade fails from 2.0+dfsg-1 to 2.0.0.1+
Your message dated Thu, 28 Dec 2006 18:15:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:27:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:29:09 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:25:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:29:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:30:58 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:15:28 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:13:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:24:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Amaya wrote (Fri 2006-Dec-22 17:04:41 +0100):
> Sven Dowideit wrote:
..
> > --- lib/TWiki.pm.orig 2006-10-25 02:16:05.0 +0200
> > +++ lib/TWiki.pm2006-12-21 16:52:23.0 +0100
> > @@ -720,6 +720,19 @@
> >
> > ASSERT($this->isa( 'TWiki')) if DEBUG;
> >
> > +# pre
Your message dated Thu, 28 Dec 2006 18:28:25 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:11:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:07:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:27:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:54:14 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:16:30 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:26:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:17:33 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:56:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:31:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:30:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:27:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:30:42 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:22:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:21:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:56:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 18:07:43 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:57:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 18:07:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:57:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
tags 404662 patch
thanks
Here's a patch for this bug, together with three other hunks that should
go into an NMU (restart apache properly, remove webserver configuration
snippet properly, and spanish debconf translation update).
I'm not going to NMU this myself, unless requested by the maintain
Your message dated Thu, 28 Dec 2006 18:08:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Processing commands for [EMAIL PROTECTED]:
> tags 404662 patch
Bug#404662: iceweasel: creates /usr/share/firefox symlink
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
Your message dated Thu, 28 Dec 2006 17:57:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:55:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:48:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:59:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:50:27 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 18:06:17 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:45:54 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:48:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:58:02 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:55:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:53:46 +0100
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:50:27 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 18:05:21 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:47:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:48:46 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 17:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line vpopmail removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to
Your message dated Thu, 28 Dec 2006 17:48:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen t
Your message dated Thu, 28 Dec 2006 11:40:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404631: missing files under /usr/share/doc/libtiff-tools/
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 28 Dec 2006 15:19:45 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391601: fixed in iputils 3:20020927-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is n
Processing commands for [EMAIL PROTECTED]:
> reassign 404828 libclanlib2
Bug#404828: clanbomber: unusable on sparc and powerpc (clanlib issue?)
Bug reassigned from package `clanbomber' to `libclanlib2'.
> severity 404828 important
Bug#404828: clanbomber: unusable on sparc and powerpc (clanlib iss
Processing commands for [EMAIL PROTECTED]:
> severity #403566 grave
Bug#403566: psad doesn't start because /usr/lib/psad doesn't exist
Severity set to `grave' from `normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
reassign 404828 libclanlib2
severity 404828 important
tag 404828 upstream confirmed
merge 404828 335886
thanks
Hi Frederic,
Frederic Daniel Luc Lehobey [2006-12-28 14:38 +0100]:
> On powerpc and sparc architectures where I have tried it, clanbomber
> takes 99% of CPU and does not display anything
On Thu, Dec 28, 2006 at 04:00:53AM -0800, Steve Langasek wrote:
> On Sat, Dec 23, 2006 at 08:03:29PM +0100, Andreas Barth wrote:
> > * Noah Meyerhans ([EMAIL PROTECTED]) [061218 19:41]:
> > > Our options would seem to be to revise the release notes
> > > to no longer suggest upgrading aptitude befo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andreas,
> The attached patch makes sure we don't mind about that anymore (though
> that is a bad patch, configure should have an option like
> --mtab=/etc/mtab or so).
The attached patch adds a configure option "--with-mnttab=". Maybe
it's a good
Hi,
Frederic Lehobey, le Thu 28 Dec 2006 14:57:02 +0100, a écrit :
> On Thu, Dec 28, 2006 at 12:37:53PM +0100, Samuel Thibault wrote:
>
> > For checking a bit more whether the bug is in pingus or clanlib/etc,
> > could you check other games that use it? (clanbomber and trophy)
>
> I have checked
* Andreas Barth ([EMAIL PROTECTED]) [061228 06:20]:
> * Andreas Barth ([EMAIL PROTECTED]) [061228 02:08]:
> > * Jochen Friedrich ([EMAIL PROTECTED]) [061228 10:58]:
> > > found 370132 5.2.3-6
> > > retitle 370132 snmpd segfaults upon first query [s390]
> > > thanks
> > >
> > > >>> I just tested 5.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andreas,
> Please allow me another remark - I think you should by way force
> configure to use sane values. Otherwise, you get errors like in
> http://buildd.debian.org/fetch.cgi?&pkg=net-snmp&ver=5.2.3-6&arch=powerpc&stamp=1166829254&file=log
> wi
* Andreas Barth ([EMAIL PROTECTED]) [061228 02:08]:
> * Jochen Friedrich ([EMAIL PROTECTED]) [061228 10:58]:
> > found 370132 5.2.3-6
> > retitle 370132 snmpd segfaults upon first query [s390]
> > thanks
> >
> > >>> I just tested 5.2.3-4 which doesn't expose this bug, cool!
> > >> Thanks for the r
On Thu, Dec 28, 2006 at 02:38:47PM +0100, Marco d'Itri wrote:
> Can you provide more info about this alleged bug?
What more information do you want ? I think you said this was in the camp of
upstream now ? And you asked me to contact them. Which admitelly i have not
yet done, but which i also beli
Hi,
Thanks for the hints.
On Thu, Dec 28, 2006 at 12:37:53PM +0100, Samuel Thibault wrote:
> For checking a bit more whether the bug is in pingus or clanlib/etc,
> could you check other games that use it? (clanbomber and trophy)
I have checked clanbomber on powerpc and sparc etch. It freezes in
Package: linux-image-2.6.18-3-sparc64
Version: 2.6.18-8
Severity: critical
Tags: patch
Justification: breaks unrelated software
Hi,
at first: if the severity may seem inflated feel free to adjust it.
Well start with the easy things: my hardware is an old Sun Ultra 5. I
added an USB 2.0 controll
Hi,
sorry that nobody contacted you for such a long time.
* jacob kuenzel ([EMAIL PROTECTED]) [061220 18:50]:
> I just did a fresh install from the stable netinst iso and then
> dist-upgraded to unstable. Now when I try to aptitude update or
> apt-get update, I get a crash:
does this error still
Package: clanbomber
Version: 1.05cdbs-5
Severity: grave
Justification: renders package unusable
Hi,
On powerpc and sparc architectures where I have tried it, clanbomber
takes 99% of CPU and does not display anything but a blackscreen (the
X window is frozen and not refreshed).
It is impossible t
Can you provide more info about this alleged bug?
If not then it should be downgraded or closed.
If you need more help with debugging you can find me on IRC.
--
ciao,
Marco
signature.asc
Description: Digital signature
You might want to read this regarding the license issue:
http://farragut.flameeyes.is-a-geek.org/articles/2006/12/20/lets-hear-the-communitys-voice-the-faad-2-5-licensing-issue
I also tried to contact ahead a few times in the past with absolutely no
answer. As you might've noticed I'm maintaining
Package: prboom
Version: 2:2.4.6-1
Severity: serious
Justification: Policy 2.1
It has been brought bto my attention that prboom's
prboom.wad contains sprites taken from the commercial ID
software game Wolfenstein 3D (the dog sprites, DOGS*) and
resources derived from copyright material taken from
Your message dated Thu, 28 Dec 2006 12:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404020: fixed in libuser 1:0.54.6-2.1.dfsg.1-1.2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Thu, 28 Dec 2006 12:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404020: fixed in libuser 1:0.54.6-2.1.dfsg.1-1.2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Package: gnome-control-center
Version: 1:2.16.2-2
Severity: serious
File: /usr/bin/gnome-mouse-properties
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
None of the mouse-related options seem to have any effect:
* Left-handed mouse
* Pointer Theme
* Locate Pointer
* Acceleration
* Sensitivit
Package: linux-2.6
Version: 2.6.18-3-amd64
Severity: grave
Justification: renders system unusable
I've just installed Debian Etch for amd64. The boot process sleep 2
times for about 5 minutes. My usb device doesn't work, they aren't
powered. My motherboard is an Asus A8V Deluxe. I've used a lot o
Hello,
Please find libuser-0.54.6-2.1.dfsg.1-1.2.diff as an attachment.
Aníbal Monsalve Salazar
--
http://v7w.com/anibal
interdiff -z -p1 ../libuser_0.54.6-2.1.dfsg.1-1.1.diff.gz
../libuser_0.54.6-2.1.dfsg.1-1.2.diff.gz
diff -u libuser-0.54.6-2.1.dfsg.1/debian/rules
libuser-0.54.6-2.1.dfsg.1/d
Closing, as the package has been removed from unstable (long overdue, too).
A slightly newer, although not completely updated, version of the book
is available at:
http://www.plope.com/Books/2_7Edition
(Also see: http://www.zope.org/Documentation/Books/ZopeBook/)
Note: the 2.7 book is also p
Hi,
For checking a bit more whether the bug is in pingus or clanlib/etc,
could you check other games that use it? (clanbomber and trophy)
Samuel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Dec 23, 2006 at 08:03:29PM +0100, Andreas Barth wrote:
> * Noah Meyerhans ([EMAIL PROTECTED]) [061218 19:41]:
> > Our options would seem to be to revise the release notes
> > to no longer suggest upgrading aptitude before dist-upgrade, or
> > including an initrd-tools package that doesn't c
Your message dated Thu, 28 Dec 2006 14:12:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line zope-book: FTBFS: SyntaxError: Invalid syntax. Assignment to
None.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Processing commands for [EMAIL PROTECTED]:
> severity 241931 grave
Bug#241931: pingus: Weird colors on powerpc arch (clanlib issue?)
Severity set to `grave' from `important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(ad
On Wed, Dec 27, 2006 at 10:32:37PM +0100, Andreas Barth wrote:
> * Marco Nenciarini ([EMAIL PROTECTED]) [061217 03:25]:
> > tags 403056 + pending
>
> When can we expect an upload of the next version of wengophone? Or
> should I just upload the fix as NMU for now?
>
I'm testing it just now.
Bye
Your message dated Thu, 28 Dec 2006 03:30:48 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404801: Kill -9 on gdb processs results in a kernel krash.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for [EMAIL PROTECTED]:
> tags 404775 -security
Bug#404775: iceweasel: upgrade fails from 2.0+dfsg-1 to 2.0.0.1+dfsg-1
There were no tags set.
Tags removed: security
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system admini
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 404377 normal
Bug#404377: Link tests are not allowed after GCC_NO_EXECUTABLES
Severity set to `normal' from `serious'
>
End of message, stopping processing here.
Please con
Your message dated Thu, 28 Dec 2006 03:01:37 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404634: copyright file missing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 28 Dec 2006 02:56:57 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404500: missing dependency against perl-modules (fixed in
sid)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Thu, 28 Dec 2006 02:55:26 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404484: gcompris: FTBFS on ia64 - needs build-dep on
libasound2-dev
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
101 - 200 of 228 matches
Mail list logo
