On Wed, Jan 03, 2007 at 11:49:51AM +0100, Marco d'Itri wrote:
> Are there other drivers in this situation?
hey Marco,
Mark Salyzyn's reply on LKML suggests that this problem maybe more
widespread and possibly difficult audit on the kernel side. Could
we do something like change the default block/
On Thu, Jan 04, 2007 at 02:36:36AM +0100, Caspar Bothmer <[EMAIL PROTECTED]>
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mike Hommey wrote:
> | And what happens if you try this again?
>
> I haven't tried yet.
>
> If there is a need for it I would do further testing. Please tel
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 405510 important
Bug#405510: Build process sets the eog-$VER directory perms to 777
Severity set to `important' from `grave'
>
End of message, stopping processing here.
Ple
Package: eog
Version: 2.16.2-1
Severity: grave
Tags: security
Justification: user security hole
This is a user security hole only on systems where the package is
built. Sorry if this doesn't qualify it for the grave severity.
The build process of eog sets the perms of the entire eog-$VERSION
subd
On Thursday 04 January 2007 10:19, Yitzchak Gale wrote:
> > digikam 0.9.0 (final) is currently available in the experimental
> > distribution. I would suggest that you both upgrade to 0.9.0 and advise
> > if this issue is still a problem
>
> Is there a version of digikamimageplugins that
> can be u
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 405506 important
Bug#405506: aptitude cannot parse package file
Severity set to `important' from `grave'
> # corrupted database, no one else reporting this - fs problem?
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
| And what happens if you try this again?
I haven't tried yet.
If there is a need for it I would do further testing. Please tell me
specifically, what kind of information you want me to provide.
caspar
-BEGIN PGP SIGNATURE-
Package: aptitude
Version: 0.4.4-1
Severity: grave
aptitude goes dead shortly after etch installed; entire etch
installation appears useless.
I was unable to use aptitude to determine version number; I installed
version number obtained by reading the filename
aptitude_0.4.4-1_i386.deb on pool
Your message dated Thu, 04 Jan 2007 01:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393387: fixed in libgcgi 0.9.5.dfsg-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 case it is n
severity 405354 important
severity 405363 important
thanks, bot
Given the clarification provided at
http://www.ietf.org/ietf/IPR/RSA-MD-all , and after discussion with
vorlon on irc, I am downgrading these to important (I actually believe
they are not problems at all, but I will let the respective
Processing commands for [EMAIL PROTECTED]:
> severity 405354 important
Bug#405354: inn2: contains non-free files
Severity set to `important' from `serious'
> severity 405363 important
Bug#405363: openswan: contains non-free files
Severity set to `important' from `serious'
> thanks, bot
Unknown c
Processing commands for [EMAIL PROTECTED]:
> tags 403346 + pending
Bug#403346: installation-report: Creates mails that are way too big and never
make the list
There were no tags set.
Tags added: pending
> tags 405102 + pending
Bug#405102: installation-report: Include info on which PCI device is
severity 382252 important
thanks
On Wed, Jan 03, 2007 at 01:04:37PM +0100, Pierre Habouzit wrote:
> # sorry pal but mishandling *.pyc files is a policy violation.
> severity 382252 serious
> thanks
> > > $ ls -l /usr/lib/python*/site-packages/mercurial/
> > [.. lots of *.pyc ..]
> > > Can you
Processing commands for [EMAIL PROTECTED]:
> severity 382252 important
Bug#382252: ImportError: No module named bdiff
Severity set to `important' from `serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
This one time, at band camp, Jason Cutting said:
> How does one install gzip 1.3.9-2 while apt is broken?
wget, ar, and tar. Although you may have to do the uncompression on
another machine.
--
-
| ,''`.
On Wed, 2007-01-03 at 13:10 -0800, Jason Cutting wrote:
> How does one install gzip 1.3.9-2 while apt is broken?
The phrase "while apt is broken" doesn't really convey much useful
information, so I'm not at all sure what problem you're trying to
overcome.
Generally, you can download a specific .d
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> # bogus severity justification, who runs vlc as root? :P
> severity 405425 grave
Bug#405425: FrSIRT/ADV-2007-0026: vlc: "cdio_log_handler()" and
"vcd_log_handler()" Format String Vul
digikam 0.9.0 (final) is currently available in the experimental
distribution. I would suggest that you both upgrade to 0.9.0 and advise
if this issue is still a problem
Is there a version of digikamimageplugins that
can be used with digikam 0.9.0 and libexiv2-0.12?
Thanks,
Yitz
--
To UNSUBSC
Package: twinkle
Version: 1:0.9-5
Followup-For: Bug #402509
Twinkle also freezes when receiving a call with this message:
twinkle: ERROR: Server sent error -1: Received invalid XML
markup: unexpected character at 2:2
Hope it helps because it's a great SIP softphone, perhaps the best for
Linux.
Your message dated Wed, 03 Jan 2007 21:53:14 +
with message-id <[EMAIL PROTECTED]>
and subject line mouse & other prefs work again
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 res
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401266: fixed in iceape 1.0.7-1
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 you
Package: pd-flext-dev
Version: 0.5.0g-1
Severity: grave
Justification: renders package unusable
It is impossible to use flext to build pd external as there are not using
Makefile to compile but the flext build.sh script.
When I invoke the supplied script :
$ LANG=C flext-build.sh
sh: /usr/lib/f
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401265: fixed in iceape 1.0.7-1
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 you
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401266: fixed in iceape 1.0.7-1
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 you
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400341: fixed in iceape 1.0.7-1
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 you
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400341: fixed in iceape 1.0.7-1
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 you
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401372: fixed in iceape 1.0.7-1
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 you
Your message dated Wed, 03 Jan 2007 22:17:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401372: fixed in iceape 1.0.7-1
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 you
Processing commands for [EMAIL PROTECTED]:
> severity 405472 normal
Bug#405472: openmpi-bin: mpif77 and mpif90 incorrect default include file
search path
Severity set to `normal' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking syste
severity 405472 normal
thanks
On Wed, 03, Jan, 2007 at 10:28:59PM +0200, Juha Jäykkä spoke thus..
> All fortran programs calling MPI_* need to include mpif.h, but
>
> ~/gl> mpif77 -DHAVE_CONFIG_H -I. -I. -I.. -I../include -O3
> -finline-limit=1 -march=i686 -march=x86-64 -funroll-loops -m
These files seem to be concerned:
acroread
doom
doom3
firefox
lxdoom
mozilla-firefox
mozilla-thunderbird
quake4
realplayer
thunderbird
ubuntu
ut2004
vmware
Regards,
Gonéri
pgpN67P0L6Bnf.pgp
Description: PGP signature
Yikes, apologies. That mail was meant to be postponed, not sent; I
*haven't* clarified this with the RMs yet and am im the process of
checking with them. I feel very stupid now.
Mark
--
Mark Hymers
"I never make predictions. I never have and I never will."
Tony Blair
signature.asc
De
How does one install gzip 1.3.9-2 while apt is broken?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Wed, 03 Jan 2007 21:17:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397074: fixed in stun 0.96.dfsg-3
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 y
Your message dated Wed, 03 Jan 2007 21:17:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397074: fixed in stun 0.96.dfsg-3
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 y
Your message dated Wed, 03 Jan 2007 21:17:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401569: fixed in democracyplayer 0.9.2.1-2.1
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
Your message dated Wed, 03 Jan 2007 21:17:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388037: fixed in stun 0.96.dfsg-3
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 y
Your message dated Wed, 03 Jan 2007 21:17:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388037: fixed in stun 0.96.dfsg-3
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 y
Package: lukemftp
Severity: serious
lukemftp has been renamed upstream to tnftp. tnftp is already packaged
in Debian, so there seems to be no need to maintain an obsolete lukemftp
package as well.
I have asked the release managers to remove this package from etch, but
they suggested that I open
Package: openmpi-bin
Version: 1.1-2.3
Severity: grave
Justification: renders package unusable
All fortran programs calling MPI_* need to include mpif.h, but
~/gl> mpif77 -DHAVE_CONFIG_H -I. -I. -I.. -I../include -O3
-finline-limit=1 -march=i686 -march=x86-64 -funroll-loops -mfpmath=sse
Processing commands for [EMAIL PROTECTED]:
> submitter 354355 Jean Charles Delepine <[EMAIL PROTECTED]>
Bug#354355: New debian sympa package
Changed Bug submitter from 4.1.5-8 to Jean Charles Delepine <[EMAIL PROTECTED]>.
(By the way, that Bug is currently marked as done.)
> found 354355 4.1.5-8
Your message dated Wed, 03 Jan 2007 19:47:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#298932: fixed in scorched3d 40.1d.dfsg-1
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 i
Your message dated Wed, 03 Jan 2007 19:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403542: fixed in mutagen 1.8-1.1
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 yo
At Wed, 3 Jan 2007 20:14:42 +0100,
Martin Michlmayr <[EMAIL PROTECTED]> wrote:
>
> * Clemens Fruhwirth <[EMAIL PROTECTED]> [2007-01-03 17:59]:
> > After a bit of debugging on Gordon's slug, I found out that we have
> > some kind of read race/read corruption when reading the encrypted
> > master ke
* Clemens Fruhwirth <[EMAIL PROTECTED]> [2007-01-03 20:32]:
> > I just applied the two patches from that thread and successfully ran
> > 'cryptsetup luksClose' on ARM.
>
> "cryptsetup luksClose" is just an alias for "cryptsetup remove". This
> should never fail. What's with luksOpen after the patc
* Clemens Fruhwirth <[EMAIL PROTECTED]> [2007-01-03 17:59]:
> After a bit of debugging on Gordon's slug, I found out that we have
> some kind of read race/read corruption when reading the encrypted
> master key from a key slot.
...
> As far as I understand page caching comes after dm-crypt, so mayb
Your message dated Wed, 3 Jan 2007 20:23: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 th
Your message dated Wed, 3 Jan 2007 20:22:38 +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 th
Your message dated Wed, 3 Jan 2007 20:16: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 th
The last package is broken in such a way that installing in on a fresh
system gets the package into a state wher eit cannot install or be
removed...
This patch lets you _upgrade_ to this version then everything is fixed
and works!
I am not a DD so cannot NMU this.
I have only tested installing a
Your message dated Wed, 3 Jan 2007 20:16: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 th
Your message dated Wed, 3 Jan 2007 20:17: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 th
Your message dated Wed, 3 Jan 2007 20:10: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 th
Hello,
Quoting Alex Owen <[EMAIL PROTECTED]>:
Patrice, please update this bug if it still does not work for you.
With the patch I cannot recreate your original problem.
As promised, I re-did the tests and the patch *does* work correctly.
The multi-page problem I had in my earlier testing wa
Package: ktrack
Version: 0.3.0-alpha1-8.1
I can confirm this also. Here is the output of what appears to be a
relevant section of the strace:
32153 open("/usr/lib/i486-linux-gnu/i686/cmov/hamlib-dummy", O_RDONLY) = -1
ENOENT (No such file or directory)
32153 stat64("/usr/lib/i486-linux-gnu/i
Your message dated Wed, 03 Jan 2007 19:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#405206: fixed in gnome-terminal 2.16.1-3
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 i
Your message dated Wed, 3 Jan 2007 20:09: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 th
Your message dated Wed, 03 Jan 2007 19:02:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382252: fixed in mercurial 0.9.1-1+etch1
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 i
Your message dated Wed, 3 Jan 2007 20:11:35 +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 th
Your message dated Wed, 03 Jan 2007 17:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404756: fixed in libxklavier 3.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 case it is now
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> reopen 354355 4.1.5-8
Bug#354355: New debian sympa package
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reo
The ips driver, indirectly via Firmware as it spoofs it's own inquiry
data, reports the Removable bit set in the inquiry response for the
arrays. The dpt_i2o driver similarly has the firmware constructing the
bit set. Some of the Array Bridges and external RAID boxes do the same
thing. I think the
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> reassign 404756 libxklavier11 3.1-1
Bug#404756: gnome-control-center: "Error activating XKB configuration" when
logging on
Bug reassigned from package `gnome-control-center' to `libx
Processing commands for [EMAIL PROTECTED]:
> found 405425 0.8.1.svn20050314-1sarge1
Bug#405425: FrSIRT/ADV-2007-0026: vlc: "cdio_log_handler()" and
"vcd_log_handler()" Format String Vulnerabilities
Bug marked as found in version 0.8.1.svn20050314-1sarge1.
> thanks
Stopping processing here.
Plea
At Tue, 2 Jan 2007 19:04:41 +0100,
Martin Michlmayr <[EMAIL PROTECTED]> wrote:
>
> * Clemens Fruhwirth <[EMAIL PROTECTED]> [2007-01-02 18:00]:
> > Does luksDump report the same things on both architecture?
>
> Yes.
After a bit of debugging on Gordon's slug, I found out that we have
some kind of
Janusz Krzysztofik wrote:
>
> Maybe vino does not provide libwrap with valid server socket data, like
> in the case of tcpdmatch without server address specified? Maybe other
> applications don't do as well? If this is the case, I think libwrap must
> be patched for security.
That is why I filed
Jamin W. Collins napisał(a):
... With the
existing libwrap0 package in testing/unstable connections to vino are
allowed from any location (not just connections from localhost).
Maybe vino does not provide libwrap with valid server socket data, like
in the case of tcpdmatch without server addr
(lkml readers: this concerns a security issue reported to debian by a
user of udev/aacraid. udev gives the aacraid devices the floppy group
because it reports block devices as 'removable'. See
http://bugs.debian.org/404927 for the entire thread).
On Wed, Jan 03, 2007 at 11:49:51AM +0100, Marco d'I
The postinst for the lilo package used to offer to run lilo. Because
it didn't, my colo system had a broken bootloader halfway through my
own upgrade from woody to sarge. I normally run lilo myself anyway
just to be sure but the system crashed due to a kernel bug triggered
by another part of the
Package: wengophone
Version: 2.0.0~rc5-svn8108-3
Severity: grave
I've told to some persons to test the wengophone package included in
testing, and i've received a very bad result.
No one of them was using it without varius segfault and random weird
things, so i think wengophone isn't releasable
Processing commands for [EMAIL PROTECTED]:
> tags 405111 security confirmed fixed-upstream pending
Bug#405111: miredo: Spoofing vulnerability
Tags were: fixed-upstream pending
Tags added: security, confirmed, fixed-upstream, pending
> tags 405412 security confirmed fixed-upstream pending
Bug#4054
On Fri, 2006-12-29 at 15:01 +0100, Martin Michlmayr wrote:
> Yes, I agree. I'm CCing the linux-mm list in hope that someone can
> review your patch. In the meantime, I've asked the Debian LSB folks to
> verify that your patch fixes the LSB problem.
I am running the complete lsb-runtime-test suit
Your message dated Thu, 4 Jan 2007 01:10:34 +1100
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-kde-extras] Bug#405386: digikam: moving items loses tag
and rating data in 0.9.0-beta3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem ha
Package: vlc
Version: 0.8.6-svn20061012.debian-1
Severity: critical
Tags: security
Justification: root security hole
Description:
Multiple vulnerabilities have been identified in VideoLAN VLC, which could be
exploited by attackers to take complete control of an affected system. These
issues
are
Hello,
Could qemu be used to emulate a 64bit system for debuging this problem?
Regards
Alex Owen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wednesday 03 January 2007 23:56, Yitzchak Gale wrote:
> Mark Purcell wrote:
> > ...we are going to... revert digikam in etch to 0.8.2 due to a
> > library transition for libexiv2...
> > digikam 0.9.0 (final) is currently available in the experimental
> > distribution. I would suggest that you bo
Your message dated Wed, 03 Jan 2007 13:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382252: fixed in mercurial 0.9.3-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 case it is now
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 379113 grave
Bug#379113: python-soappy: fpconst failure on 64 Bit
Severity set to `grave' from `important'
>
End of message, stopping processing here.
Please contact me if
Wouter Cloetens a écrit :
> On Wed, Jan 03, 2007 at 01:04:37PM +0100, Pierre Habouzit wrote:
>> To Wouter: to resolve your problem, just rm -rf
>> /usr/lib/python*/site-packages/mercurial. You can do that safely,
>> that'll solve your problem.
>
> Success! Many thanks!
You need to remove /usr/lib
Josselin Mouette wrote:
> mdiff.py does "import bdiff" which looks for bdiff.so in the same
> directory. On your system, mdiff.py is is
> in /var/lib/python-support/python2.4/mercurial/ which is the correct
> place for packages handled by python-support, while on the user's system
> it is in /usr/l
Mark Purcell wrote:
...we are going to... revert digikam in etch to 0.8.2 due to a
library transition for libexiv2...
digikam 0.9.0 (final) is currently available in the experimental distribution.
I would suggest that you both upgrade to 0.9.0 and advise if this issue is
still a problem.
Where
On Wed, Jan 03, 2007 at 01:04:37PM +0100, Pierre Habouzit wrote:
> To Wouter: to resolve your problem, just rm -rf
> /usr/lib/python*/site-packages/mercurial. You can do that safely,
> that'll solve your problem.
Success! Many thanks!
signature.asc
Description: Digital signature
Processing commands for [EMAIL PROTECTED]:
> # sorry pal but mishandling *.pyc files is a policy violation.
> severity 382252 serious
Bug#382252: ImportError: No module named bdiff
Severity set to `serious' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance
Janusz Krzysztofik wrote:
I believe my patch is safe because for the old behaviour (process name) it
only removes error provoking condition on request->server-:sim being set,
introduced by port numbrer patch, and does not change anything else. This
condition is only applicable in case of port n
Your message dated Wed, 3 Jan 2007 11:56:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line woody only
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
On Wed, Jan 03, 2007 at 12:14:23PM +0100, Mike Hommey wrote:
> On Tue, Jan 02, 2007 at 11:03:58AM -0200, Fabiano Manoel de Andrade <[EMAIL
> PROTECTED]> wrote:
> > The totem-mozila version was 2.16.4-2. /usr/lib/firefox was a symbolic
> > link to iceweasel directory.
> > Fabiano.
> This whole
On Wed, Jan 03, 2007 at 03:22:37AM -0800, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> To my eye, I think it would be much better to drop the /usr/lib/firefox
> symlink. I wholly expect that people will want to install third-party
> firefox packages, maybe even alongside the iceweasel package, and
On Wednesday 03 January 2007 20:47, Yitzchak Gale wrote:
> As a heavy users of digicam (actually my kids, not me,
> anyway...), we would lose a LOT more data from digicam
> being removed from etch than from this bug.
Unfortunately we are going to have to revert digikam in etch to 0.8.2 due to a
l
On Sat, Dec 16, 2006 at 12:36:14PM +0100, Caspar Bothmer <[EMAIL PROTECTED]>
wrote:
> So I have this picture:
>
> 1. I got two mails, the friend's mail some months ago, the spam message
> some days ago. The spam message was marked spam on arrival.
>
> 2. The friend's mail stayed in my normal in
Your message dated Wed, 3 Jan 2007 11:52:03 +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 th
Your message dated Wed, 3 Jan 2007 11:45:48 +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 th
* "Sergei Golovan"
| On 1/3/07, Stephen Gran <[EMAIL PROTECTED]> wrote:
| > Yes, many do. It's also not immediately clear to me that this is under
| > a non-free license. I agree that it could be better worded, but that's
| > not quite the same thing.
|
| Kenneth Lundin has pointed me (in erla
Your message dated Wed, 3 Jan 2007 11:51: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 th
On Tue, Jan 02, 2007 at 11:03:58AM -0200, Fabiano Manoel de Andrade <[EMAIL
PROTECTED]> wrote:
> The totem-mozila version was 2.16.4-2. /usr/lib/firefox was a symbolic
> link to iceweasel directory.
> Fabiano.
This whole issue might be related to the fact that /usr/lib/firefox is a
symlink to
On Jan 03, dann frazier <[EMAIL PROTECTED]> wrote:
> Can you elaborate on what you believe the kernel is doing
> incorrectly? My first guess would be the setting of the removable
> flag, but aacraid claims to be setting this to prevent partition table
> caching - do you believe that to be an inco
Your message dated Wed, 3 Jan 2007 11:51:42 +0100
with message-id <[EMAIL PROTECTED]>
and subject line woody only
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
Processing commands for [EMAIL PROTECTED]:
> reassign 310939 installation-reports
Bug#310939: installation: mismatch between install kernel and initial boot
kernel
Warning: Unknown package 'installation'
Bug reassigned from package `installation' to `installation-reports'.
> reassign 341135 inst
Your message dated Wed, 3 Jan 2007 11:47:23 +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 th
Your message dated Wed, 3 Jan 2007 11:46:47 +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 th
Processing commands for [EMAIL PROTECTED]:
> severity 405360 important
Bug#405360: erlang: contains non-free files
Severity set to `important' from `serious'
> retitle 405360 erlang: license of RSA derived sources should be documented
Bug#405360: erlang: contains non-free files
Changed Bug title.
1 - 100 of 119 matches
Mail list logo
