Processing commands for [EMAIL PROTECTED]:
tag 366574 + fixed
Bug#366574: libnora-ruby: Please stop building ruby1.6 modules
Tags were: patch
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Hi Ben,
Ben Hay [2006-08-03 19:19 +1000]:
pmount gives the error Error: this program needs to be installed suid
root even though /usr/bin/pmount is suid root.
That's certainly very strange. Do you happen to have /usr mounted
'nosuid' or something like that? What is the output of
ls -l
On Friday 04 August 2006 00:41, sean finney wrote:
hey jan,
On Thu, Aug 03, 2006 at 12:33:34PM +0200, Jan Wagner wrote:
Package: nagios-plugins-standard
Version: 1.4.3-1
Severity: serious
the attached patch should fix the problem and be applied to debian/rules.
i don't believe this
Package: gcj-4.0
Version: 4.0.3-2
Severity: serious
Hello,
There was a problem while autobuilding your package:
Automatic build of gcj-4.0_4.0.3-2 on avidan by sbuild/i386 0.49
Build started at 20060804-0551
Package: gdome2-xslt
Version: 0.0.7-4
Severity: serious
Hello,
There was a problem while autobuilding your package:
Automatic build of gdome2-xslt_0.0.7-4 on avidan by sbuild/i386 0.49
Build started at 20060804-0609
Processing commands for [EMAIL PROTECTED]:
reassign 381399 postgresql-common 58
Bug#381399: Subject: postgresql: postgresql can't be installed
Bug reassigned from package `postgresql' to `postgresql-common'.
merge 381399 381394
Bug#381394: postgresql-common fails to install at useradd command
reassign 381394 passwd 4.0.18-1
tag 381394 confirmed
thanks
Hi,
luke [2006-08-03 23:15 -0400]:
When trying to install postgresql-common (a dependency of the server
package) I get an error when the user postgres is created:
Setting up postgresql-common (58) ...
useradd: invalid numeric
Processing commands for [EMAIL PROTECTED]:
reassign 381394 passwd 4.0.18-1
Bug#381394: postgresql-common fails to install at useradd command
Bug#381399: Subject: postgresql: postgresql can't be installed
Bug reassigned from package `postgresql-common' to `passwd'.
tag 381394 confirmed
Hi
I have seen this as well, but don't this mean that this bug is really in gcc,
as it complains about one of the files that are included. I thought that
the gcc team was aware of it...
It only happen on that architecture.
Regards,
// Ola
On Thu, Aug 03, 2006 at 10:37:26AM -0600, [EMAIL
Martin Pitt wrote:
Hi Ben,
Ben Hay [2006-08-03 19:19 +1000]:
pmount gives the error "Error: this program needs to be installed suid
root" even though /usr/bin/pmount is suid root.
That's certainly very strange. Do you happen to have /usr mounted
'nosuid' or something
at 20060804-0551
**
Checking available source versions...
Fetching source files...
Reading package lists...
Building dependency tree...
Need to get 33.6MB of source archives.
Get:1 http://ftp.fr.debian.org sid/main gcj-4.0
Package: passwd
Version: 1:4.0.18-1
Severity: serious
When I try to bootstrap sid, useradd fails because it does not accept
group names passed to -g:
P: Configuring package exim4-config
D: Updating exim4-config to status 3
O: hostname:
O: Host name lookup failure
O:
O: hostname:
O: Host
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/06, Josselin Mouette [EMAIL PROTECTED] wrote:
The pango-libthai package relies on pango-querymodules, but it doesn't
depend on libpango1.0-common. Currently, this package is pulled by
chance because of a circular dependency with
On Fri, Aug 04, 2006 at 08:19:24AM +0200, Jan Wagner wrote:
I recognised the problem first with 1.4.3. Dont know if earlier packages are
effected. 1.4.3.0cvs.20060707-2 has the check_ldaps symlink in basic and
standard, so sarge and etch are definetly effected.
assuming you mean sid and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/06, Theppitak Karoonboonyanan [EMAIL PROTECTED] wrote:
However, I don't quite understand about the circular
dependency problem. Could you give more info?
Umm.. I have also replaced the hard-coded dependencies
with ${shlibs:Depends},
Processing commands for [EMAIL PROTECTED]:
merge 381394 381408
Bug#381394: postgresql-common fails to install at useradd command
Bug#381408: useradd's -g option doesn't handle group names
Bug#381399: Subject: postgresql: postgresql can't be installed
Merged 381394 381399 381408.
--
Stopping
tag 381394 patch
thanks
The attached patch should fix this problem by adding support for
passing group names to useradd's -g option.
--
Matt
--- src/useradd.c.orig 2006-08-04 00:55:19.0 -0700
+++ src/useradd.c 2006-08-04 00:58:07.0 -0700
@@ -206,11 +206,9 @@
char
Processing commands for [EMAIL PROTECTED]:
tag 381394 patch
Bug#381394: postgresql-common fails to install at useradd command
Tags were: confirmed
Bug#381399: Subject: postgresql: postgresql can't be installed
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need
Hi there
This problem is consistently causing issues for me and numerous other people..
I don't really have much to add to this bug request, other than to consider
this a vote for please look at this if you have some time - it'd be much
appreciated.
I know you guys have hundreds of other things
Your message dated Fri, 4 Aug 2006 10:25:16 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#381264: Error: this program needs to be installed suid root
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
On Fri, Aug 04, 2006 at 12:01:35AM +0200, Arjan Oosting wrote:
tag 380132 patch
thanks
I have prepared a patch which solves the FTBFS. The patch is attached.
Greetings Arjan
Thanks Arjan, but I already uploaded a fix for this bug (Looks
like its in unstable as I write).
cheers,
--
sam
Processing commands for [EMAIL PROTECTED]:
tags 381405 + wontfix
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
There were no tags set.
Tags added: wontfix
tags 381405 + pending
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
Tags were: wontfix
Tags
reopen 381405
thanks
On Fri, Aug 04, 2006 at 09:44:47AM +0200, Matthias Klose wrote:
this package is scheduled for removal.
Please, close bugs when the package is actually removed, not before.
--
Julien Danjou
.''`. Debian Developer
: :' : http://julien.danjou.info
`. `'
Processing commands for [EMAIL PROTECTED]:
reopen 381405
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
Bug reopened, originator not changed.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Processing commands for [EMAIL PROTECTED]:
severity 381405 serious
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
Severity set to `serious' from `wishlist'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Hi,
this was tagged pending already some time ago, and fixed since, but only
in experimental.
Is a fix for testing expected soon?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Le vendredi 04 août 2006 à 15:03 +0700, Theppitak Karoonboonyanan a
écrit :
However, I don't quite understand about the circular
dependency problem. Could you give more info?
Currently, there is a circular dependency between libpango1.0-0 and
libpango1.0-common. This is why by chance your
Processing commands for [EMAIL PROTECTED]:
severity 368967 serious
Bug#368967: RM: gcj-4.0 -- RoM; old gcj packages, replaced by gcj-4.1
Severity set to `serious' from `normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Your message dated Fri, 04 Aug 2006 03:02:54 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381098: fixed in ocp 0.1.10rc6-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
Em Thu, 3 Aug 2006 17:31:26 +0200
David Weinehall [EMAIL PROTECTED] escreveu:
On Wed, Aug 02, 2006 at 11:18:41PM -0300, Gustavo Noronha Silva wrote:
So it seems that this version works =)
Great =D, let me upload then!
--
Gustavo Noronha Silva [EMAIL PROTECTED]
http://people.debian.org/~kov/
Package: cupsys
Version: 1.2.2-1
Severity: grave
Justification: renders package unusable
While trying to add a printer, the dialog never presents a device
selection, it stays empty. This way, I am not able to add any printer.
The folder backend was missing first and I copied it in from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/06, Josselin Mouette [EMAIL PROTECTED] wrote:
Le vendredi 04 août 2006 à 15:03 +0700, Theppitak Karoonboonyanan a
écrit :
However, I don't quite understand about the circular
dependency problem. Could you give more info?
Currently, there
Processing commands for [EMAIL PROTECTED]:
reopen 381404
Bug#381404: proftpd: fails to install (useradd bug?)
Bug reopened, originator not changed.
reassign 381404 passwd
Bug#381404: proftpd: fails to install (useradd bug?)
Bug reassigned from package `proftpd' to `passwd'.
severity 381404
Your message dated Fri, 04 Aug 2006 04:32:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381248: fixed in libsdl1.2 1.2.11-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 message dated Fri, 04 Aug 2006 05:02:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#379359: fixed in kiwi 1.9.8-7
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
Kapil Hari Paranjape [EMAIL PROTECTED] wrote:
I think I understand what you are saying:
The problem is that changes in the Linux interface force you to ask
Linux users to install the program setuid in order to be sure to test
all the possible difficulties that may arise when writing a
Hi,
finally, there was the things answered by the release-team about the
future of oot-modules in etch I wanted to know.
So, I can prepare new ipw* oot-module packages next week.
Regards,
Daniel
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL
Your message dated Fri, 4 Aug 2006 14:54:10 +0200
with message-id [EMAIL PROTECTED]
and subject line duplicate 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 your responsibility to
Processing commands for [EMAIL PROTECTED]:
severity 381348 serious
Bug#381348: cpio build glitch breaks Unicode char handling
Severity set to `serious' from `important'
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
severity 381428 important
thanks
At Fri, 04 Aug 2006 13:25:37 +0200,
root wrote:
Package: cupsys
Version: 1.2.2-1
Severity: grave
Justification: renders package unusable
While trying to add a printer, the dialog never presents a device
selection, it stays empty. This way, I am not able to
Processing commands for [EMAIL PROTECTED]:
severity 381428 important
Bug#381428: cupsys: Device dialog does not how any entry
Severity set to `important' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Your message dated Fri, 4 Aug 2006 15:47:06 +0200
with message-id [EMAIL PROTECTED]
and subject line Close #295736
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
hello Manoj and vorlon!
rechecking the issues that were reported on #358397 and #362064
1) fails to install on read-only /boot
this is correct and not yet checked, boot is assumed rw.
we currently fail to check that, but non standard setup.
2) overwriting yaird generated image
only happened in
Package: postgresql-common
Version: 58
Severity: grave
Justification: renders package unusable
I'm unable to install postgresql-8.1. The whole system is a fresh
install, the base system from etch netinstall beta 2 and then a complete
upgrade to sid. This isn't an update of installed postgresql
Hello,
On Mon, Jul 31, 2006 at 09:30:35AM +0530, Kapil Hari Paranjape wrote:
tags 349674 upstream
thanks
Hello,
As reported in Debian bug #349674 which can be seen at
http://bugs.debian.org/349674
Unison has problems when the file system is removed from under it.
For
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
package libpam-smbpass libsmbclient libsmbclient-dev python-samba samba
samba-common samba-dbg samba-doc samba-doc-pdf smbclient smbfs swat winbind
Ignoring bugs not assigned to:
reassign 381406 libgdome2-cpp-smart-dev
thanks
On Fri, Aug 04, 2006 at 08:45:02AM +0200, Julien Danjou wrote:
package: gdome2-xslt
version: 0.0.7-4
severity: serious
hello,
There was a problem while autobuilding your package:
snip
g++ -g -Wall -O2 -o .libs/test main.o -lz -lm
Package: adonthell
Version: 0.3.4.cvs.20050813-2.1+b1
Severity: grave
Justification: renders package unusable
Hello,
$ /usr/games/adonthell wastesedge
Segmentation fault
Segfault a the end of the sound during the splash screen.
$ strace /usr/games/adonthell wastesedge
munmap(0xa760a000,
severity 369448 important
stop
can you still reproduce your bug with newest 2.6.17 image from unstable?
if yes please post your /etc/kernel-img.conf
also did you read the following follow up to your bug report:
On Wed, 07 Jun 2006, Manoj Srivastava wrote:
Hi,
Looking at the logs,
Tags 381122 + patch
Thanks
The attached patch replace the $RANDOM and let bash internal functions
using external commands in coreutils.
--- debian/cron.daily 2006-06-16 11:05:37.0 -0300
+++ debian/rata.daily 2006-08-04 11:17:18.0 -0300
@@ -1,9 +1,9 @@
#!/bin/sh
RANGE=3600
Processing commands for [EMAIL PROTECTED]:
Tags 381122 + patch
Bug#381122: Bashism in /etc/cron.daily/apticron
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, Debian
Processing commands for [EMAIL PROTECTED]:
reassign 381406 libgdome2-cpp-smart-dev
Bug#381406: gdome2-xslt: FTBFS: ld: cannot find -lz
Bug reassigned from package `gdome2-xslt' to `libgdome2-cpp-smart-dev'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
severity 330214 important
Bug#330214: kernel-image-2.6.8-2-686: kernel panic when using QUEUE target with
iptables
Severity set to `important' from `critical'
End of message,
Processing commands for [EMAIL PROTECTED]:
severity 369448 important
Bug#369448: [powerpc] failure in pre-inst script, package fails to install
Severity set to `important' from `grave'
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
reassign 381448 passwd
severity 381448 serious
tags 381448 confirmed patch
merge 381448 381394
thanks
Hi Fidel,
Fidel Ramos [2006-08-04 16:12 +0200]:
adduser: `/usr/sbin/useradd -d /var/lib/postgresql -g postgres -s /bin/bash
-u 106 postgres'
Already known as #381394 and a handful of
Processing commands for [EMAIL PROTECTED]:
reassign 381448 passwd
Bug#381448: postgresql-common postinst error blocks postgresql-8.1 installation
Bug reassigned from package `postgresql-common' to `passwd'.
severity 381448 serious
Bug#381448: postgresql-common postinst error blocks
Your message dated Fri, 04 Aug 2006 09:17:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#373926: fixed in nagios-plugins 1.4.3.0cvs.20060707-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
Package: acl2
Version: 3.0.1-1
Severity: serious
Hi,
Your package is failing to build on amd64 with the following
error:
HARD ACL2 ERROR in RECORD-ERROR: An attempt was made to treat NIL
as a record of type REWRITE-RULE.
ACL2 Error in CERTIFY-BOOK: Evaluation aborted. See :DOC wet for
how
Package: initramfs-tools
Version: 0.73
Severity: grave
Justification: makes the package unsuitable for release in maintainer's opinion
After upgrading from testing (0.69b) to unstable (0.73), resuming from
hibernation no longer works -- it just boots as normal. Downgrading
fixes the issue.
--
On Wed, 2 Aug 2006 21:37, Brian M. Carlson said:
I am inclined to say that this is grave, but since gnupg tends to do
memory allocation before it drops privileges, you might find that this
The allocation problem, which is overflow like
malloc(numbercontrolledbyuser+20), can only happen after
Package: aptitude
Version: 0.4.2-1
Severity: serious
Hello,
There was a problem while autobuilding your package:
Automatic build of aptitude_0.4.2-1 on avidan by sbuild/i386 0.49
Build started at 20060804-1937
Processing commands for [EMAIL PROTECTED]:
tag 381390 + fixed
Bug#381390: pyrite-publisher: can't open file '/usr/lib/python/compileall.py'
There were no tags set.
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Package: adolc
Version: 1.10.1-1
Severity: serious
Hello,
There was a problem while autobuilding your package:
Automatic build of adolc_1.10.1-1 on avidan by sbuild/i386 0.49
Build started at 20060804-2031
On Thu, Aug 03, 2006 at 10:40:09PM -0300, Margarita Manterola wrote:
Hi!
I've been working with a couple of friends (Damián Viano and Martín
Ferrari), in trying to fix this bug. We've built perl in an hppa machine
and use that build to test the following things.
This line:
./perl
Package: ivmanVersion: 0.6.12-3Severity: graveJustification: renders package unusableThe package ivman don't install, ocurring the error "invoke-rc.d:initscript ivman, action "start" failed."Try to run command line ivman after that, but the command "ps aux | grepivman" don't return any ivman job
retitle 381483 adolc: FTBFS: gawkism/bashism
tag 381483 patch
thanks
--- adolc-1.10.1.orig/debian/rules
+++ adolc-1.10.1/debian/rules
@@ -65,8 +65,8 @@
DESTDIR=`pwd`/debian/tmp bindir=/usr/bin/adolc/additional
mkdir --parents
Processing commands for [EMAIL PROTECTED]:
retitle 381483 adolc: FTBFS: gawkism/bashism
Bug#381483: adolc: FTBFS: awk: not an option: --file=debian/move-READMEs.awk
Changed Bug title.
tag 381483 patch
Bug#381483: adolc: FTBFS: gawkism/bashism
There were no tags set.
Tags added: patch
thanks
I'm sorry, is this *not* a fails to build in standard Debian build
environment problem. This is a fails to build in non-standard
environment in which awk is mawk instead of gawk issue.
If it were the former, I the severity of serious would be
reasonable, and I would upload a fix immediately.
Processing commands for [EMAIL PROTECTED]:
severity 381483 wishlist
Bug#381483: adolc: FTBFS: gawkism/bashism
Severity set to `wishlist' from `serious'
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Processing commands for [EMAIL PROTECTED]:
tag 379265 + fixed
Bug#379265: FTBFS: needs an update for new ghc6
Tags were: patch
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Processing commands for [EMAIL PROTECTED]:
tag 258174 + fixed
Bug#258174: db3(GNU/k*BSD): FTBFS: out of date libtool scripts
Tags were: patch
Tags added: fixed
tag 357526 + fixed
Bug#357526: db3-doc: doc package is not DFSG-free
There were no tags set.
Tags added: fixed
quit
Stopping
Your message dated Fri, 04 Aug 2006 13:47:24 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#364262: fixed in debian-edu 0.805
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: avarice
Version: 2.4-2
Severity: grave
Tags: patch
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
avarice is linked with the shared version of libbfd, but the
binutils-dev says :
Note that building Debian packages which depend on the shared libbfd
hello
the problem is that start-stop-daemon can't start the server if the old
(shutting down) process is still running since it just allows one
instance
a simple solution is to copy the start section in the initscript and
rename it to force-start, change the --pidfile $PIDFILE to --pidfile
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381394: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381408: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381394: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381399: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381448: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381408: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381408: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381448: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381394: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381408: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381404: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381404: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381448: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381394: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381408: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381394: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381399: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381399: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381404: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381399: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381399: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381404: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381448: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381404: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381448: fixed in shadow 1:4.0.18.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
Your message dated Fri, 04 Aug 2006 15:47:22 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#375053: fixed in gnupg2 1.9.20-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
1 - 100 of 108 matches
Mail list logo
