Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.4
> tags 422585 lenny sid
Bug#422585: FTBFS: Numeric/arrayobject.h: No such file or directory
There were no tags set.
Tags added: lenny, sid
> tags 426012 sid
Bug#426012: python-scipy: c
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.4
> tags 424449 lenny sid
Bug#424449: spfmilter - FTBFS: spfmilter.c:1261: undefined reference to
`smfi_getpriv'
Tags were: confirmed
Tags added: lenny, sid
> tags 428997 lenny sid
Bug#
On Wed, Jun 27, 2007 at 12:03:20PM -0500, Gunnar Wolf wrote:
> ...I reproduced it - the problem is that $rsvg->loadImage with a
> svg.gz triggers a segfault, and all the tests from that point on don't
> get executed at all. Just to illustrate, from the source tree, just
> after the build died (hen
Package: incron
Version: 0.5.5-1
Severity: serious
hi,
while doing a archive wide piuparts run your package failed to install
due to a missing dependency on adduser:
Setting up incron (0.5.5-1) ...
/var/lib/dpkg/info/incron.postinst: line 10: addgroup: command not found
dpkg: error process
Package: icecc
Version: 0.8.0-1
Severity: serious
Tags: etch-ignore
Usertags: postrm-depends-nonessential
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
> Removing
Package: armagetronad-dedicated
Version: 0.2.8.2.1-4
Severity: serious
Usertags: postrm-depends-nonessential
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
Removing
Package: greylistd
Version: 0.8.3.5
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
R
Package: nbd-server
Version: 1:2.9.4-1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable during postrm:
Re
Package: freewnn-cserver
Version: 1.1.0+1.1.1-a021-1.1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable
Package: boxbackup-client
Version: 0.10+chrismerge+r1706-1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable
Package: diogenes
Version: 0.9.20-1.1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable during postrm:
Rem
Package: localepurge
Version: 0.5.9
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable during postrm:
Remov
Package: boxbackup-server
Version: 0.10+chrismerge+r1706-1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable
Package: flyspray
Version: 0.9.8-12
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable during postrm:
Remov
Package: nagios-common
Version: 2:1.4-3.1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable during postrm:
Package: python-poker-network
Version: 1.0.37-1.1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of ucf beeing unavailable during po
Package: freewnn-jserver
Version: 1.1.0+1.1.1-a021-1.1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable
Package: crywrap
Version: 0.2.1-4.2
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
P
Your message dated Tue, 3 Jul 2007 10:19:28 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423962: tcm: FTBFS: /usr/include/X11/VendorP.h:87: error:
previous declaration of 'VendorShellClassRec vendorShellClassRec' with 'C++'
linkage
has caused the attached Bug report to be marked
Package: uw-imapd
Version: 7:2002edebian1-13.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: postrm-depends-nonessential
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of update-inetd beeing unavailable dur
Package: gnats
Version: 4.1.0-0.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: postrm-depends-nonessential
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of update-inetd beeing unavailable during postrm:
Package: ipopd
Version: 7:2002edebian1-13.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: postrm-depends-nonessential
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of update-inetd beeing unavailable during
Package: opendb
Version: 0.81p20-1.1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of wwwconfig-common beeing unavailable during po
Package: memlockd
Version: 0.03
Severity: serious
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on install
because of adduser beeing unavailable during postrm:
Setting up memlockd (0.03) ...
/var/lib/dpkg/info/memlockd.post
Package: munge
Version: 0.5.8-4
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
Purgi
Package: lyskom-server
Version: 2.1.2-6
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
Package: tinyerp-server
Version: 4.0.3-1
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of adduser beeing unavailable during postrm:
Processing commands for [EMAIL PROTECTED]:
> severity 431104 serious
Bug#431104: libgsf-1-114: Bug in libgsf : segfault.
Severity set to `serious' from `important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
Your message dated Tue, 03 Jul 2007 09:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431532: fixed in tinyerp-server 4.0.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
Your message dated Tue, 03 Jul 2007 09:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431481: fixed in git-core 1:1.5.2.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 n
Processing commands for [EMAIL PROTECTED]:
> notfound 430785 +1.6.dfsg.1-4
Bug#430785: CVE-2007-2798: kadmind vulnerable to buffer overflow
Bug marked as not found in version +1.6.dfsg.1-4.
(By the way, this Bug is currently marked as done.)
> notfound 430785 +1.4.4-7etch1
Bug#430785: CVE-2007-27
Package: tct
Version: 1.11-6.3
Severity: serious
Redistribution and use in source and binary forms are permitted
provided that this entire copyright notice is duplicated in all such
copies.
Doesn't say anywhere that modification is permitted.
Since there are a few package
Thanks for the information, bug will be solved in the next release.
--
Gennaro Oliva
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 03 Jul 2007 11:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431519: fixed in boxbackup 0.10+really0.10-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 Tue, 03 Jul 2007 11:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431518: fixed in boxbackup 0.10+really0.10-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
Processing commands for [EMAIL PROTECTED]:
> package cryptcat
Ignoring bugs not assigned to: cryptcat
> tags 431010 lenny sid
Bug#431010: cryptcat: segfault in listen mode
There were no tags set.
Tags added: lenny, sid
> thanks
Stopping processing here.
Please contact me if you need assistance.
Actually, just rewrote it. I also added a useful feature the original
doesn't have (--status).
--
Robert Millan
/*
* timeout.c -- run commands with a specified timeout
* Copyright (C) 2007 Robert Millan <[EMAIL PROTECTED]>
*
* GRUB is free software; you can redistribute it and/or modify
Hi,
> Doesn't say anywhere that modification is permitted.
>
> Since there are a few packages that depend on timeout, and this program is
> in fact very small, I'd gladly provide a rewrite if needed.
>
> secvpn,timeout
> podracer,timeout
> netatalk,timeout
> gnokii,timeout
Actually for an
Hi,
> > I noticed that the sweep problem is caused by libasound2 error.
> > What's the status of libasound2 update?
>
> Waiting for upload [1]
>
> Elimar
>
> [1]
> http://svn.debian.org/wsvn/pkg-alsa/trunk/alsa-lib/debian/changelog?op=file&rev=0&sc=1
>
I thought we're kind of trying to get t
Your message dated Tue, 03 Jul 2007 12:47:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431510: fixed in incron 0.5.5-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 you
Processing commands for [EMAIL PROTECTED]:
> severity 427806 serious
Bug#427806: referencer: Uninstallable in unstable (needs poppler
patch/recompile)
Severity set to `serious' from `important'
> --
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Your message dated Tue, 3 Jul 2007 16:08:29 +0200
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 Tue, 3 Jul 2007 16:10:51 +0200
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 Tue, 3 Jul 2007 16:08:00 +0200
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 Tue, 3 Jul 2007 16:08:48 +0200
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 Tue, 3 Jul 2007 16:10:51 +0200
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 Tue, 3 Jul 2007 16:11:47 +0200
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 Tue, 3 Jul 2007 16:21:51 +0200
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 Tue, 3 Jul 2007 16:17:50 +0200
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 Tue, 3 Jul 2007 16:17:18 +0200
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 Tue, 3 Jul 2007 16:26:50 +0200
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 Tue, 3 Jul 2007 16:22:20 +0200
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 Tue, 3 Jul 2007 16:16:32 +0200
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 Tue, 3 Jul 2007 16:16:50 +0200
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 Tue, 3 Jul 2007 16:26:50 +0200
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 Tue, 3 Jul 2007 16:16:50 +0200
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 Tue, 3 Jul 2007 16:25:48 +0200
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 Tue, 3 Jul 2007 16:23:53 +0200
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 Tue, 3 Jul 2007 16:17:50 +0200
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 Tue, 3 Jul 2007 16:17:18 +0200
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 Tue, 3 Jul 2007 16:17:18 +0200
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 Tue, 3 Jul 2007 16:29:42 +0200
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 Tue, 3 Jul 2007 16:18:14 +0200
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 Tue, 3 Jul 2007 16:15:55 +0200
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 Tue, 3 Jul 2007 16:29:42 +0200
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 Tue, 3 Jul 2007 16:25:48 +0200
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 Tue, 03 Jul 2007 16:30:37 +0200
with message-id <[EMAIL PROTECTED]>
and subject line evolution has long been ported to the pilot-link 0.12 API
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 Tue, 03 Jul 2007 06:51:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in experimental version.
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 Tue, 3 Jul 2007 16:26:50 +0200
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 Tue, 03 Jul 2007 06:51:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in experimental version.
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 Tue, 3 Jul 2007 16:29:42 +0200
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 Tue, 3 Jul 2007 16:29:42 +0200
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 Tue, 3 Jul 2007 16:29:22 +0200
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 Tue, 03 Jul 2007 06:51:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in experimental version.
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 Tue, 3 Jul 2007 16:26:50 +0200
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 Tue, 3 Jul 2007 16:29:42 +0200
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 Tue, 3 Jul 2007 16:15:55 +0200
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]:
> reassign 417656 evolution-data-server
Bug#417656: evolution: Crashes when run
Bug reassigned from package `evolution' to `evolution-data-server'.
> found 417656 evolution-data-server/1.8.2-2
Bug#417656: evolution: Crashes when run
Bug marked as found i
reassign 417656 evolution-data-server
found 417656 evolution-data-server/1.8.2-2
close 417656 1.8.2-3
thanks
Heya,
The versioning information for this bug was broken, so I'm fixing it
now :)
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
134: Benutzerfreundlichkeit
Der Benutzer ha
Hi,
I uploaded an NMU of your package.
Please see this as help to get the package into a releaseable condition again.
Please find the used diff below.
Cheers,
Andi
diff -u abiword-2.4.6/debian/changelog abiword-2.4.6/debian/changelog
--- abiword-2.4.6/debian/changelog
+++ abiword-2.4.6/debian
Your message dated Tue, 03 Jul 2007 15:02:56 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#425066: fixed in abiword 2.4.6-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 it is now
Package: openoffice.org
Version: 2.2.1-4
Severity: critical
Justification: breaks unrelated software
soffice
*** glibc detected *** /usr/lib/openoffice/program/soffice.bin: double free or
corruption (out): 0x08585ba0 ***
=== Backtrace: =
/lib/libc.so.6[0xb6cc0b74]
/lib/libc.so.6(cfr
tag 422395 patch
thanks
On Sat, May 05, 2007 at 05:35:59PM +0200, Lucas Nussbaum wrote:
> Package: lilypond
> Version: 2.8.7-3
> Severity: serious
> Justification: FTBFS on i386, very likely to fail everywhere else
> User: [EMAIL PROTECTED]
> Usertags: builddep-tetex-ftbfs
>
> Hi,
>
> During a r
Processing commands for [EMAIL PROTECTED]:
> tag 422395 patch
Bug#422395: lilypond: FTBFS: ! I can't find file `lcircle10'.
Tags were: sid lenny
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
On Mon, Jul 02, 2007 at 10:00:53PM -0700, Nathaniel Smith <[EMAIL PROTECTED]>
was heard to say:
> On Sun, Jul 01, 2007 at 06:12:11PM -0700, Daniel Burrows wrote:
> > Does installing the version in experimental fix the problem for you?
>
> Yes, the aptitude in experimental (0.4.4-5~2, which appe
severity 431572 important
thanks
Michael Ott wrote:
> Package: openoffice.org
> Version: 2.2.1-4
> Severity: critical
> Justification: breaks unrelated software
Suure. Which unrelated software? OpenOffice.org breaking itself? This is
ridiculous. Neither does it fullfill the "breaks the whole syst
Processing commands for [EMAIL PROTECTED]:
> tags 431090 + upstream
Bug#431090: libnetaddr-ip-perl: Includes non-free RFC documentation
There were no tags set.
Tags added: upstream
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administra
Your message dated Tue, 3 Jul 2007 17:33:36 +0200
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
tags 431090 + upstream
thanks
Reported as upstream bug #27941 in the CPAN RT:
http://rt.cpan.org/Ticket/Display.html?id=27941
Damyan Ivanov dijo [Mon, Jul 02, 2007 at 11:35:10AM +0300]:
> > This package's orig.tar.gz includes NetAddr-IP-4.007/docs/rfc1884.txt,
> > which is non-free
>
> Isn't th
Your message dated Tue, 3 Jul 2007 17:35:42 +0200
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 Tue, 3 Jul 2007 17:36:20 +0200
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 431572 important
Bug#431572: openoffice.org: Ooo crashed when i try to sort a sheet
Severity set to `important' from `critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
Your message dated Tue, 3 Jul 2007 17:36:20 +0200
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 Tue, 3 Jul 2007 17:36:20 +0200
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 Tue, 3 Jul 2007 17:36:20 +0200
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 Tue, 3 Jul 2007 17:36:20 +0200
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
Package: myspell-de-at
Version: 20051113-9
Severity: grave
Justification: renders package unusable
debian:/home/wickey# aptitude install myspell-de-at
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut... Fertig
Lese erweiterte Statusinformationen
Initialisiere Paketstatus...
Package: gnarwl
Version: 3.3-8.2
Severity: serious
hi,
while running archive wide piuparts tests your package failed on install
because of a missing dependency on ed:
Setting up gnarwl (3.3-8.2) ...
/var/lib/dpkg/info/gnarwl.postinst: line 22: ed: command not found
dpkg: error processing g
Your message dated Tue, 03 Jul 2007 16:02:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431090: fixed in libnetaddr-ip-perl 4.007+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 c
Package: iiimf-client-gtk
Version: 12.3.91-5
Severity: serious
Usertags: postrm-depends-nonessential
User: [EMAIL PROTECTED]
Justification: Policy violation, see section 7.2
hi,
while running archive wide piuparts tests your package failed on purge
because of /usr/sbin/update-gtk-immodules beein
1 - 100 of 146 matches
Mail list logo
