Your message dated Sun, 05 Aug 2007 11:08:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426291: emacs-lisp-intro: Upstream has removed invariant
sections
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for [EMAIL PROTECTED]:
> tag 428683 fixed-upstream
Bug#428683: problem with prolog-build-case-strings and occur
There were no tags set.
Tags added: fixed-upstream
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administ
tag 428683 fixed-upstream
thanks
Looks like this was fixed upstream:
;; Version 1.14:
[...]
;; o Condensed regular expressions for lower and upper case
;; characters (GNU Emacs seems to go over the regexp length limit
;; with the original form). My code on the matte
Package: prolog-el
Version: 1.12-2
debian/rules should use the binary-indep target since the package is
architecture-independent.
Thanks,
Matej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> # violates DFSG
> severity 395255 serious
Bug#395255: turkey includes jargs.jar without source
Severity set to `serious' from `normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
Your message dated Sun, 05 Aug 2007 11:50:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399660: fixed in libapache-mod-auth-mysql 4.3.9-4
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
lxdoom_1.4.4main-1_i386.changes uploaded successfully to localhost
along with the files:
lxdoom_1.4.4main-1.dsc
lxdoom_1.4.4main-1.diff.gz
lxdoom_1.4.4main-1_i386.deb
lxdoom-svga_1.4.4main-1_i386.deb
lxdoom-x11_1.4.4main-1_i386.deb
lxdoom-sndserv_1.4.4main-1_i386.deb
Greetings,
Accepted:
lxdoom-sndserv_1.4.4main-1_i386.deb
to pool/main/l/lxdoom/lxdoom-sndserv_1.4.4main-1_i386.deb
lxdoom-svga_1.4.4main-1_i386.deb
to pool/main/l/lxdoom/lxdoom-svga_1.4.4main-1_i386.deb
lxdoom-x11_1.4.4main-1_i386.deb
to pool/main/l/lxdoom/lxdoom-x11_1.4.4main-1_i386.deb
lxdoom_1.4.4ma
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:19:43 +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 t
Your message dated Sun, 05 Aug 2007 14:35:12 +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 t
Your message dated Sun, 05 Aug 2007 14:35:12 +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 t
Your message dated Sun, 05 Aug 2007 14:37:09 +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 t
Your message dated Sun, 05 Aug 2007 14:35:12 +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 t
Your message dated Sun, 05 Aug 2007 14:35:12 +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 t
Your message dated Sun, 05 Aug 2007 14:37:09 +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 t
Package: libcteco5
Severity: minor
Hi,
a very stupid question, but is libcteco5 indeed the right package
name for a Orga Eco 5000 smartcard reader driver? Another package from
the same source package is called ibcteco5000-dev.
Please note 50 000 vs. 5 000!
It's an old package but nobody
Jens Seidel <[EMAIL PROTECTED]> writes:
> a very stupid question, but is libcteco5 indeed the right package
> name for a Orga Eco 5000 smartcard reader driver? Another package from
> the same source package is called ibcteco5000-dev.
>
> Please note 50 000 vs. 5 000!
>
> It's an old package bu
Hi folks,
A new version of PAM (0.99.7.1-1) has been packaged and uploaded to
experimental. This is intended to replace 0.79-4. However, because
there have been quite a number of upstream changes, and all the
Debian-specific patches against the old one were painstakingly
re-diffed and updated by
libmail-srs-perl_0.31-4_amd64.changes uploaded successfully to localhost
along with the files:
libmail-srs-perl_0.31-4.dsc
libmail-srs-perl_0.31-4.diff.gz
libmail-srs-perl_0.31-4_all.deb
srs_0.31-4_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL P
Accepted:
libmail-srs-perl_0.31-4.diff.gz
to pool/main/libm/libmail-srs-perl/libmail-srs-perl_0.31-4.diff.gz
libmail-srs-perl_0.31-4.dsc
to pool/main/libm/libmail-srs-perl/libmail-srs-perl_0.31-4.dsc
libmail-srs-perl_0.31-4_all.deb
to pool/main/libm/libmail-srs-perl/libmail-srs-perl_0.31-4_a
bubblemon_2.0.5-3_amd64.changes uploaded successfully to localhost
along with the files:
bubblemon_2.0.5-3.dsc
bubblemon_2.0.5-3.diff.gz
bubblemon_2.0.5-3_amd64.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
Accepted:
bubblemon_2.0.5-3.diff.gz
to pool/main/b/bubblemon/bubblemon_2.0.5-3.diff.gz
bubblemon_2.0.5-3.dsc
to pool/main/b/bubblemon/bubblemon_2.0.5-3.dsc
bubblemon_2.0.5-3_amd64.deb
to pool/main/b/bubblemon/bubblemon_2.0.5-3_amd64.deb
Override entries for your package:
bubblemon_2.0.5-3.
Your message dated Sun, 05 Aug 2007 21:30:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line libapache-mod-auth-mysql: postrm script fails
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
blktool_4-4_amd64.changes uploaded successfully to localhost
along with the files:
blktool_4-4.dsc
blktool_4-4.diff.gz
blktool_4-4_amd64.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
Accepted:
blktool_4-4.diff.gz
to pool/main/b/blktool/blktool_4-4.diff.gz
blktool_4-4.dsc
to pool/main/b/blktool/blktool_4-4.dsc
blktool_4-4_amd64.deb
to pool/main/b/blktool/blktool_4-4_amd64.deb
Override entries for your package:
blktool_4-4.dsc - source admin
blktool_4-4_amd64.deb - optio
FYI: The status of the gringotts source package
in Debian's testing distribution has changed.
Previous version: 1.2.8+1.2.9pre1-14
Current version: 1.2.8+1.2.9pre1-15
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ fo
FYI: The status of the libgringotts source package
in Debian's testing distribution has changed.
Previous version: 1.2.1-10
Current version: 1.2.1-11
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more informatio
FYI: The status of the netdude source package
in Debian's testing distribution has changed.
Previous version: 0.3.3-2.2
Current version: (not in testing)
Hint: <http://ftp-master.debian.org/testing/hints/vorlon>
# 20070804; done 20070805
Bug #428947: netdude: FTBFS: /
FYI: The status of the plotmtv source package
in Debian's testing distribution has changed.
Previous version: 1.4.4t-9
Current version: 1.4.4t-10
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
Package: labrea
Version: 2.5-stable-2
Severity: minor
Hi,
The package description refers to hackers as denizens, I think this is
wrong and missleading and should be replaced with 'crackers'.
regards,
guillem
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
73 matches
Mail list logo
