Package: wnpp
Severity: normal
python-daap is orphaned.
Maintaining a package requires time and skills. Please only adopt this
package if you are *sure* you will have enough time and attention to
work on it.
If you want to be the new maintainer, please see
Package: wnpp
Severity: normal
libipod is orphaned.
Maintaining a package requires time and skills. Please only adopt this
package if you are *sure* you will have enough time and attention to
work on it.
If you want to be the new maintainer, please see
Package: wnpp
Severity: normal
smarteiffel2 is orphaned.
Maintaining a package requires time and skills. Please only adopt this
package if you are *sure* you will have enough time and attention to
work on it.
If you want to be the new maintainer, please see
Searching for the name of a friend would bring a more diverse list perhaps
organised.
Anyone with a valid digital certificate for a website could generate a.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
smartcard |0.1.7-3 | source, alpha, amd64, arm, hppa, hurd-i386, i386,
ia64, m68k, mips, mipsel, powerpc, s390, sparc
Note that the package(s) have simply been removed from the tag
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
playground-plugin-xmms | 0.3-2 | alpha, amd64, arm, hppa, hurd-i386, i386,
ia64, m68k, mips, mipsel, powerpc, s390, sparc
playground-xmms | 0.3-2 | source
Note that the
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
playground | 0.3-2 | source, alpha, amd64, arm, hppa, i386, ia64, m68k,
mips, mipsel, powerpc, s390, sparc
playground-dev | 0.3-2 | all
Note that the package(s) have simply
I got some free time, so I fixed the bug I submitted.
The default settings when backgrounded were attempting
to input nonexistent input into the selection buffer
and thus cleared it. Please apply this simple patch
to the next version. Thanks.
diff -uN xsel-0.9.6/xsel.c xsel-0.9.6.fixed/xsel.c
Processing commands for [EMAIL PROTECTED]:
tags 453278 + patch
Bug#453278: CVE-2007-6110: XSS in htsearch
Tags were: security
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
I've prepared a patch/NMU using the patch I uploaded to fix this in Ubuntu.
--
William Grant
diff -u htdig-3.2.0b6/htsearch/Display.cc htdig-3.2.0b6/htsearch/Display.cc
--- htdig-3.2.0b6/htsearch/Display.cc
+++ htdig-3.2.0b6/htsearch/Display.cc
@@ -138,7 +138,7 @@
// Must temporarily
Your message dated Sat, 1 Dec 2007 10:10:54 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#453764: qa.debian.org: missing space
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
Hi,
I'd like to know whether it would be feasible to have a symlink from
e.g. [1] pointing to the latest run, so that we can fetch the diffs
directly without having to parse the summary page [2] to get the
timestamp or the links to the diffs.
1.
Hi :)
as discussed some minutes ago in the BOF I start the thread here now about the
MIA stuff in Debian.
One point was defining fixed intervals of pinging a maintainer and how we could
automate them, my proposal would be the following:
X-MIA-Summary: nice Then wait 30 days
On Sat, Dec 01, 2007, Mario Iseli wrote:
Hi :)
Hi!
X-MIA-Summary: nice Then wait 30 days
X-MIA-Summary: prod Then wait 30 days
X-MIA-Summary: last-warning Then wait 60 days
That makes 3 months. Isn't it a bit long?
Currently, I wait for nearly the same time after
Hi,
On Sat, Dec 01, 2007 at 12:44:05PM +0100, Cyril Brulebois wrote:
I'd like to know whether it would be feasible to have a symlink from
e.g. [1] pointing to the latest run, so that we can fetch the diffs
directly without having to parse the summary page [2] to get the
timestamp or the
On 01/12/2007, Ralf Treinen wrote:
No problem. You just need the symlink in the filesystem, right?
That's it, right.
Or do you also wish a html link on the generated html pages?
No thanks, I'll just use the static URL with latest/ to fetch the
updates of the history.xml file, then do some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-12-2007 12:28, Mohammed Adnène Trojette wrote:
On Sat, Dec 01, 2007, Mario Iseli wrote:
Hi :)
Hi!
X-MIA-Summary: nice Then wait 30 days
X-MIA-Summary: prod Then wait 30 days
X-MIA-Summary: last-warning Then wait 60
Your message dated Sat, 1 Dec 2007 17:30:10 -0600
with message-id [EMAIL PROTECTED]
and subject line DEHS: Error with a valid watch file
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 Sat, Dec 01, 2007, Felipe Augusto van de Wiel (faw) wrote:
X-MIA-Summary: niceThen wait 30 days
X-MIA-Summary: prodThen wait 30 days
X-MIA-Summary: last-warningThen wait 60 days
That makes 3 months. Isn't it a bit long?
AIUI, it makes
19 matches
Mail list logo
