It still exists in Debian Sid with 1.3.9-2.
Entpacke Ersatz für gzip ...
Richte gzip ein (1.3.9-2) ...
install-info(/usr/share/info/gzip.info): Warnung, ignoriere verwirrenden
Eintrag INFO-DIR-ENTRY in Datei.
Kein »START-INFO-DIR-ENTRY« und kein »This file documents«.
install-info(/usr/share/i
Your message dated Fri, 22 Dec 2006 02:42:35 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Current package doesn't have this bug
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
On Thu, Dec 21, 2006 at 05:29:47PM +0100, Jochen Friedrich wrote:
> My *guess* is that the buildd server for s390 has no /etc/mtab or /etc/mtab
> might be a symlink.
> So maybe a fix could be to use -e instead of -f in the above test case.
> However, i'll ask this
> on [EMAIL PROTECTED]
I believ
On Fri, Dec 22, 2006 at 01:53:15AM +0100, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061204 13:00]:
> > On Mon, Dec 04, 2006 at 07:50:37PM +0100, Mike Hommey <[EMAIL PROTECTED]>
> > wrote:
> > > On Mon, Dec 04, 2006 at 01:25:26PM -0500, Aaron M. Ucko <[EMAIL
>
Am Freitag, den 22.12.2006, 00:31 +0100 schrieb Santiago Vila:
> On Thu, 21 Dec 2006, Daniel Leidert wrote:
>
> > Hi,
> >
> > A question. Isn't it possible to solve this issue by a
> >
> > m4_ifdef(
> > [AM_PROG_MKDIR_P],
> > [AM_PROG_MKDIR_P],// automake >= 1.8
> > [...old solutio
Package: kdepim
Version: 4:3.5.5.dfsg.1-4
Severity: serious
Justification: no longer builds from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
~/Temp/src/temp/kdepim-3.5.5.dfsg.1$ dpkg-buildpackage -b -rfakeroot
make[1]: Entering directory `/home/first/Temp/src/temp/kdepim-3.5.5.dfsg
Package: gzip
Version: 1.3.9-1
Followup-For: Bug #403998
I can confirm this bug. despite what packages.debian.org says, version
1.3.9-1 is coming down the pipe at debian.midco.net. Interestingly
though, apt-cache policy shows version 1.3.9-1 already installed.
menawhile aptitude is trying to inst
I mis-read the bug reports. I'm sorry for the extra noise.
A
signature.asc
Description: Digital signature
Processing commands for [EMAIL PROTECTED]:
> reopen 401791
Bug#401791: wodim upgrade breaks xcdroast
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
> reassign 401791 wodim
Bug#401791: wodim
this is a double submission of 404103, so I'm closing this bug report
now.
Aren't libcurl3-gnutls and libcurl3 different packages? If so, then
this is not a double.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: euro-support
Version: 0.37
Severity: grave
I've missed to adapt this package to the latest glibc's changes (which
introduced /etc/default/locale) and most of its work is already done by
localization-config.
Thus, I would like this package to be removed from etch (but not sid) until
suc
Hi,
On Mon, 2006-12-18 at 19:19:30 +0100, Aurelien Jarno wrote:
> Well this has been removed, and now the linker and the dynamic loader
> both know about /emul/ia32-linux/[usr/]lib, just as they now /lib64 and
> /usr/lib64 on 32-bit platforms.
>
> I guess dpkg-shlibdeps have to know about those p
Package: kernel
Severity: critical
Justification: causes serious data loss
Hi everybody.
I'm currently (together with others) investigating in a severe data
corruption problem that at least many users might suffer from.
A short description, when you validate lots of GBs over and over with
md5sum
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 404103 wishlist
Bug#404103: unnecessary depends on ca-certificates
Severity set to `wishlist' from `critical'
>
End of message, stopping processing here.
Please contact me
Hi Yann,
I maintain google-perftools.
Yann Dirson wrote:
TAU has been using this name since quite a long time, and a number of
3rd-party tools and user scripts probably rely on that name. Since the
Google tool is quite young (not at 1.0 yet at least), it is probably
still possible for them to
Package: sun-java5
Version: 1.5.0-08-1.1
Severity: serious
Tags: security
Hi,
from your changelog of 1.5.0-10-1:
* New upstream release. Closes: #393153.
- CVE-2006-2426 is fixed. Closes: #384734.
- CVE-2006-5201 is fixed. Closes: #393042
These fixes are not part of the package in te
reopen 337779
thanks
That this is now documented in lilo does not mean it should not be
documented in the RN too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Mike Hommey ([EMAIL PROTECTED]) [061204 13:00]:
> On Mon, Dec 04, 2006 at 07:50:37PM +0100, Mike Hommey <[EMAIL PROTECTED]>
> wrote:
> > On Mon, Dec 04, 2006 at 01:25:26PM -0500, Aaron M. Ucko <[EMAIL PROTECTED]>
> > wrote:
> > > Mike Hommey <[EMAIL PROTECTED]> writes:
> > >
> > > > So, I fixe
Processing commands for [EMAIL PROTECTED]:
> reopen 337779
Bug#337779: release-notes do not suggest re-running lilo
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
> thanks
Stopping processi
Package: linux-image-2.6.18-3-amd64
Version: 2.6.18-7
Severity: grave
Justification: hardware overheating hazard; requires periodic reboots
(This is not the same bug as #400488 (upstream #7122))
This bug affects several amd64 notebooks from HP, notably the nx6125
and the nx6325; there may be othe
Package: migemo
Version: 0.40-7
Severity: serious
Justification: dependency error
Migemo seems to call 'ruby' command, which is included in the
package 'ruby'. So, it needs to change to call 'ruby1.8' or to
require the ruby package, I think.
Without the 'ruby' package, Migemo warns:
[(file-erro
On Thu, Dec 21, 2006 at 05:24:34PM -0600, Gunnar Wolf wrote:
> Luis Rodrigo Gallardo Cruz dijo [Thu, Dec 21, 2006 at 11:55:38AM -0600]:
> > Gunnar seems to have been a little sleepy yesterday. For his patch to
> > work you also need to manually create debian/compat with the single
> > line:
> >
>
Package: sympa
Version: 5.2.3-0.7
Severity: grave
Tags: patch
Justification: causes non-serious data loss
wwsympa and soap can cause database corruption if running while database
upgrade :
http://listes.cru.fr/sympa/arc/sympa-users/2006-12/msg00058.html
With newer sympa versions, including 5.2.3
Processing commands for [EMAIL PROTECTED]:
> reassign 403645 libattr1
Bug#403645: libattr1: kdeinit fails to start
Bug reassigned from package `libattr1' to `libattr1'.
> found 403645 2.4.35-1
Bug#403645: libattr1: kdeinit fails to start
Bug marked as found in version 2.4.35-1.
> close 403645 1:
Luis Rodrigo Gallardo Cruz dijo [Thu, Dec 21, 2006 at 11:55:38AM -0600]:
> Gunnar seems to have been a little sleepy yesterday. For his patch to
> work you also need to manually create debian/compat with the single
> line:
>
> --snip--
> 4
> --snap--
Umgh... It is included in the pending NMU, bla
Your message dated Fri, 22 Dec 2006 01:40:58 +0100
with message-id <[EMAIL PROTECTED]>
and subject line double submission
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 t
Your message dated Fri, 22 Dec 2006 00:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#245826: fixed in t-gnus 6.17.2.00-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 n
Your message dated Fri, 22 Dec 2006 00:02:14 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403287: fixed in planet 2.0-6
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, 21 Dec 2006 23:17:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403223: fixed in marble 0.2-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 your
On Thu, 21 Dec 2006, Daniel Leidert wrote:
> Hi,
>
> A question. Isn't it possible to solve this issue by a
>
> m4_ifdef(
> [AM_PROG_MKDIR_P],
> [AM_PROG_MKDIR_P],// automake >= 1.8
> [...old solution...] // automake <= 1.7
> )
>
> Maybe you could forward this to upstream.
I
Jochen Friedrich a écrit :
> Hi Aurelien,
>
>> using the libc6-dbg package, I have seen that the getmntent() function
>> is called with a NULL pointer. This may be due to the fact that on s390
>> there is in the build log:
>> checking for mount table location... unknown
>>
>> whereas on architec
Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
> Jon Marler <[EMAIL PROTECTED]> (21/12/2006):
> > Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
> > > Note also that once this is fixed, you should update the description of
> > > the qmail-src package.
> >
> > I am not exactly sure what pbuilder is doing
Your message dated Thu, 21 Dec 2006 23:17:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402331: fixed in qmail 1.03-42
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, 21 Dec 2006 23:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403992: fixed in childsplay-alphabet-sounds-ru 0.4.2-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
Your message dated Thu, 21 Dec 2006 23:17:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403992: fixed in childsplay-alphabet-sounds-sv 0.4.2-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
Your message dated Thu, 21 Dec 2006 22:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403841: fixed in hat 2.05+rerolled-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 no
On Thu, Dec 21, 2006 at 08:01:07AM +0100, Michael Ablassmeier wrote:
> both libgoogle-perftools0 and tau ship usr/bin/pprof but do not conflict or
> add
> a diversion, thus fail to be installed on the same environment:
The tools are quite different, so an alternative is not a solution.
Using a c
Processing commands for [EMAIL PROTECTED]:
> tags 403287 + pending
Bug#403287: planet: install same files as drscheme, but doesn't conflict
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adminis
[not cc'ed to debian-release and exiv2]
On Thursday, 21. December 2006 16:46, Marc 'HE' Brockschmidt wrote:
[...]
> From what I can see, this is fine. bugs.d.o doesn't report anything
> unusual, but I would love to know if #393505 and #396249 are fixed in
> 2:0.8.2-2.
FWIW: a quick try of an aliot
Hi Ryan,
We would like to find out why latest version of emacs21 (21.4+1-2) failed to
build
on mipsel.
21.4+1-1 used to build fine and no change related to the C code nor autoconf
files has been made in 21.4+1-2.
Since we don't have a clean sid chroot on vaughan (the only developer mipsel
machi
Le jeudi 21 décembre 2006 21:34, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > Rob, are you taking care of this, or should I?
>
> Please do, if you have the time.
I will only available till next Saturday so I guess someone will have to
take care of it if both of us are
Matija Nalis said on Thu, Dec 21, 2006 at 09:35:08PM +0100:
> both have been fixed promptly in upstream.
Ok I'm happy that they are now indeed fixed. I really like debian users
as they give feedback ;-)
> > I might send you a patch to try against mindi-2.20-1. Would you be able
> > to test it?
Steve Langasek wrote:
On Sun, Dec 17, 2006 at 01:29:31PM +0200, Mohammed Sameer wrote:
I don't know if it makes a difference, but I'm quite sure I didn't have
this problem on another unstable machine. The machine which is having
the problem was recently installed from scratch; the other machi
severity 404105 important
thanks
Am Donnerstag, 21. Dezember 2006 20:29 schrieb Stefan Fritsch:
> Package: openoffice.org
> Version: 2.0.4.dfsg.2-1
> Severity: grave
> Tags: security
> Justification: user security hole
>
>
> openoffice.org crashes when loading the exploit from [1]. There is
> i
Your message dated Thu, 21 Dec 2006 23:17:04 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404130: ieee80211 package doesn't work with amd64
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
Jon Marler <[EMAIL PROTECTED]> (21/12/2006):
> Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
> > Note also that once this is fixed, you should update the description of
> > the qmail-src package.
>
> I am not exactly sure what pbuilder is doing here, but I don't get the same
> behavior when executin
Processing commands for [EMAIL PROTECTED]:
> severity 404105 important
Bug#404105: CVE-2006-6628: Integer overflow in OpenOffice.org
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(ad
Your message dated Thu, 21 Dec 2006 21:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397412: fixed in wmaker 0.92.0-6.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
Your message dated Thu, 21 Dec 2006 15:41:17 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402331: FTBFS: "unable to find user alias"
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
Package: ieee80211
Version: 1.1.14-1
Severity: grave
This is not installable or buildable on the amd64.
Because of this users on amd64 running ipw3945 and other chips experience
kernel panics and have systems that freeze frequently.
Your message dated Thu, 21 Dec 2006 21:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400923: fixed in multi-gnome-terminal 1.6.2-13
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 cas
Your message dated Thu, 21 Dec 2006 20:47:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337779: fixed in lilo 1:22.7.3-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
On Thu, Dec 21, 2006 at 10:12:29PM +0100, Ludovic Rousseau wrote:
> It looks like pcscd does not want to die.
...or that it dies across suspend/resume, without rm-ing the pid file. It
is my understanding that if the daemon is not there when stop runs, it should
simply nuke the pid file.
> We will
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> tags 403223 confirmed
Bug#403223: marble_0.2-1(sparc/experimental): FTBFS: unrecognized command line
option "-msse"
There were no tags set.
Tags added: confirmed
> tags 403223 pendi
Le 21.12.2006, à 12:24:13, Steinar H. Gunderson a écrit:
> Sorry, this still does not work (I missed the close message, so I assumed it
> was still open, I guess):
>
> fugl:~/nmu> sudo /etc/init.d/pcscd restart
>
> Stopping PCSC Lite resource manager: pcs
On Sun, Dec 17, 2006 at 01:29:31PM +0200, Mohammed Sameer wrote:
> > I don't know if it makes a difference, but I'm quite sure I didn't have
> > this problem on another unstable machine. The machine which is having
> > the problem was recently installed from scratch; the other machine had
> >
reopen 402331
found 402331 1.03-41
thanks
Jon Marler <[EMAIL PROTECTED]> (20/12/2006):
> Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
>
> My previous emails have gone unanswered, but I have uploaded a new
> release that should fix this issue. Look in the upload queue for -41,
> or wait for when q
Jérôme Marant <[EMAIL PROTECTED]> writes:
> Rob, are you taking care of this, or should I?
Please do, if you have the time.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Processing commands for [EMAIL PROTECTED]:
> reopen 402331
Bug#402331: FTBFS: "unable to find user alias"
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
> found 402331 1.03-41
Bug#402331: F
On Thu, Dec 21, 2006 at 10:38:35PM +1100, Andree Leidenfrost wrote:
> Looking at the mailing list thread it looks like the patch listed in
> both the mailing list thread and in trac ticket 100 is the same and did
> not work because you wrote in the mailinglist thread in response to the
> patch:
>
Le samedi 16 décembre 2006 21:09, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > Shall we contact Ryan?
>
> Sounds like a good idea. Though I suppose there's another difference
> between vaughan and the buildd. On vaughan I wasn't building from a
> clean chroot.
Rob,
Your message dated Thu, 21 Dec 2006 19:47:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403165: fixed in gnome-menus 2.16.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 n
Package: linux-patch-bootsplash
Version: 2.6.18-1
Severity: serious
Justification: FTBFS
It appears that in order build boot splash, you must select the VESA
driver. However, the VESA driver is not available on powerpc (and I
presume other x86 platforms).
-- System Information:
Debian Release: 4
Hello,
I have done some test running pstops against the current packaed
version and a version patched with str2111.patch.
I tested with the attached 3 page ps file "test.ps"
and ran the attached script "test.sh"
My diffs or the resultinf ps files show that no JCL/PJL whatever it is
is genereted.
Op di, 19-12-2006 te 18:14 -0600, schreef JP Sugarbroad:
> []
> % hat-trail z
> hat-trail: attempt to read beyond end of file
> hat-trail: offset = 0x300, filesize = 0x28b6
> hat-trail: errno = 0 (Success)
> Architecture: amd64 (x86_64)
This seems to be architecture specific bug. On i386 hat-
Package: check
Version: 0.9.4-2
Severity: grave
Tags: patch
Justification: renders package unusable
check uses "i" in the loop test macro, which breaks every use that uses
"i" locally. since "i" is the most ommon loop variable in C, it will
break in almost any case.
cu robert
-- System Informat
According to http://secunia.com/advisories/23024, there are more
security issues in chectpasswd.
It should be removed from Debian if no fix is expected.
Cheers,
Stefan
pgpRBWv3mJa6I.pgp
Description: PGP signature
Hi Michael,
Yes, known bug and on my list to fix *soon*. If only there were 30
hour days. ;-)
Thanks.
Cheers,
Paul.
> Package: axyl
> Version: 2.1.11
> Severity: serious
>
> hi,
>
> axyl fails to install if /etc/apache is missing:
>
> Setting up axyl (2.1.12) ...
> mkdir: created directo
Your message dated Thu, 21 Dec 2006 19:25:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402886: icedove has become highly unstable - 2 to 3 hangs
per day
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Tue, Dec 19, 2006 at 11:32:30AM -0700, Bdale Garbee wrote:
> On Tue, 2006-12-19 at 15:46 +, Alex Owen wrote:
>
> > This patch should fix the problem. I guess the opotions are to aply
> > this patch to 1.16 or package 1.16.1. I guess applying the patch is
> > the better option if we wnat to
Package: libcurl3
Version: 7.15.5-1
Severity: critical
Tags: security
Given that trustworthiness of certificate authorities is not evaluated,
no package should depend on ca-certificates. To do so forces the user
to trust everything in ca-certificates.
I suggest setting this Depends to Recomm
Package: openoffice.org
Version: 2.0.4.dfsg.2-1
Severity: grave
Tags: security
Justification: user security hole
openoffice.org crashes when loading the exploit from [1]. There is inconclusive
information whether this may be used to execute arbitrary code [2,3]. If this is
a mere DoS you may of c
Package: libcurl3-gnutls
Version: 7.15.5-1
Severity: critical
Tags: security
Given that trustworthiness of certificate authorities is not evaluated,
no package should depend on ca-certificates. To do so forces the user
to trust everything in ca-certificates.
I suggest setting this Depends to
Your message dated Thu, 21 Dec 2006 18:02:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379628: fixed in linux-ntfs 1.13.1-5
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 no
Hi,
A question. Isn't it possible to solve this issue by a
m4_ifdef(
[AM_PROG_MKDIR_P],
[AM_PROG_MKDIR_P],// automake >= 1.8
[...old solution...] // automake <= 1.7
)
Maybe you could forward this to upstream.
Regards, Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
Bdale Garbee <[EMAIL PROTECTED]> writes:
> On Tue, 2006-12-19 at 15:46 +, Alex Owen wrote:
>> This patch should fix the problem. I guess the opotions are to aply
>> this patch to 1.16 or package 1.16.1. I guess applying the patch is
>> the better option if we wnat to fix this for etch.
> It's n
"Mark Purcell" <[EMAIL PROTECTED]> writes:
> Given the discussion has died down.
>
> I am proposing to release digikam[imageplugins] 0.8.2 to unstable in the
> next couple of days to overcome the lack of an libexiv2 transition.
From what I can see, this is fine. bugs.d.o doesn't report anything
un
Jochen Friedrich a écrit :
> Hi Aurelien,
>
>> using the libc6-dbg package, I have seen that the getmntent() function
>> is called with a NULL pointer. This may be due to the fact that on s390
>> there is in the build log:
>> checking for mount table location... unknown
>>
>> whereas on architec
Your message dated Thu, 21 Dec 2006 16:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404048: fixed in gzip 1.3.9-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 your
Hi Aurelien,
> using the libc6-dbg package, I have seen that the getmntent() function
> is called with a NULL pointer. This may be due to the fact that on s390
> there is in the build log:
> checking for mount table location... unknown
>
> whereas on architecture there is:
> checking for moun
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 400627 serious
Bug#400627: apache2 refuse to start when kolab-webadmin is installed
Severity set to `serious' from `important'
>
End of message, stopping processing here.
P
Aurelien Jarno a écrit :
> Program received signal SIGSEGV, Segmentation fault.
> 0x77c20e60 in getmntent_r () from /lib/tls/libc.so.6
> (gdb)
> (gdb) bt
> #0 0x77c20e60 in getmntent_r () from /lib/tls/libc.so.6
> #1 0x77c20738 in getmntent () from /lib/tls/libc.so.6
> #2 0x77e9f196 in init_disk
Gunnar seems to have been a little sleepy yesterday. For his patch to
work you also need to manually create debian/compat with the single
line:
--snip--
4
--snap--
--
Rodrigo Gallardo
GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28
signature.asc
Description: Digital signatu
Your message dated Thu, 21 Dec 2006 10:01:43 -0700 (MST)
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 1.3.9-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 your responsibil
Your message dated Thu, 21 Dec 2006 10:01:43 -0700 (MST)
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 1.3.9-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 your responsibil
Your message dated Thu, 21 Dec 2006 10:01:43 -0700 (MST)
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 1.3.9-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 your responsibil
Jochen Friedrich a écrit :
> tags 370132 + help moreinfo
> thanks
>
> Hi Aurelien,
>
>>> snmpd no longer works on ia64. It dies when receiving first query.
>
>> I have got the same exact problem on s390. Given that this bug renders
>
> I tested this in a chroot on merulo and raptor by running s
tags 404048 patch
thanks
Hi,
here's a simple patch that fixes this problem:
diff -Nur gzip-1.3.9.old/doc/gzip.texi gzip-1.3.9/doc/gzip.texi
--- gzip-1.3.9.old/doc/gzip.texi2006-12-08 19:45:37.0 +0100
+++ gzip-1.3.9/doc/gzip.texi2006-12-21 15:04:50.0 +0100
@@ -28,14 +2
Re: Romain Beauxis 2006-12-21 <[EMAIL PROTECTED]>
> gnome-peercast ships a static library file libpeercast.a.
>
> This is bad for the following reasons:
> * It conflicts with libpeercast0-dev and hence trigered bug #404000
> * No package should be built against gnome-peercast unless it states in
>
Your message dated Thu, 21 Dec 2006 14:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403952: fixed in rlwrap 0.24-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 your
Processing commands for [EMAIL PROTECTED]:
> tags 404048 patch
Bug#404048: unstable, gzip, apt-get dist-upgrade - error
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,
On Thursday 21 December 2006 02:46, Steve Langasek wrote:
> You could argue that the package is "unfit for release" (=> sev:
> serious), but then I don't see how that's consistent with asking for an
> etch-ignore tag. If it's ignorable for etch, I don't see why it
> wouldn't also be ignorable for
Your message dated Thu, 21 Dec 2006 14:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403952: fixed in rlwrap 0.28-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 your
Processing commands for [EMAIL PROTECTED]:
> #as discussed in the IRC channel.
> retitle 403776 kdm: Theme option doesn't work
Bug#403776: kdm seems to violate FHS
Changed Bug title.
> severity 403776 normal
Bug#403776: kdm: Theme option doesn't work
Severity set to `normal' from `serious'
> tha
Your message dated Thu, 21 Dec 2006 13:17:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403091: fixed in haskell-uulib 0.9.2-6
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
Marco d'Itri wrote:
> On Dec 19, Joey Hess <[EMAIL PROTECTED]> wrote:
>
> > The whole check for lo being up based on /etc/network/run/ifstate seems
> > less than ideal; it could instead check whether the actual interface is
> > up, that seems less likely to have false positivies.
> Looks like a go
Your message dated Thu, 21 Dec 2006 12:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404054: fixed in elfutils 0.123-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
Hi Mark,
On St, 2006-12-13 at 10:08 -0800, Mark Symonds wrote:
> Possible DoS attack in the wild? I wouldn't think so but it's been the same
> thing on four different servers in a week... I'm going to post to some lug
> mailing lists later today to see if anyone else is seeing this.
Did you
Processing commands for [EMAIL PROTECTED]:
> severity 404055 important
Bug#404055: file conflict between libasm-dev and libelfsh0-dev
Severity set to `important' from `serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On 12/21/06, Jochen Friedrich <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> Package: snmpd
> Version: 5.2.2-3
> Severity: important
>
> snmpd no longer works on ia64. It dies when receiving first query.
> Here's a sample testcase, running "snmpwalk" from another
1 - 100 of 169 matches
Mail list logo
