We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
lsnipes |0.9.4-7 | source, alpha, amd64, armel, hppa, i386, ia64, mips,
mipsel, powerpc, s390, sparc
--- Reason ---
RoQA; orphaned, dead upstream, u
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
workman | 1.3.4-29 | source, alpha, armel, hppa, i386, mips, mipsel,
powerpc, s390, sparc
--- Reason ---
RoQA; orphaned, unused, dead upstream, altern
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
hindent |1.1.2-8 | source, all
--- Reason ---
RoQA; obsolete, unmaintained, dead upstream, orphaned for a long time
-
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
wmmaiload |2.3.0-1 | source, alpha, amd64, armel, hppa, hurd-i386, i386,
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
--- Reason --
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
u++ |5.3.0-2 | source, amd64, i386, ia64
u++-doc |5.3.0-2 | all
--- Reason ---
RoQA; unused, orphaned, dead upstream
-
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
bake | 1.0-14 | source, all
--- Reason ---
dead upstream, unused, no reverse deps
--
Note that the pa
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
wmbinclock | 0.5-5 | source, alpha, amd64, armel, hppa, hurd-i386, i386,
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
--- Reason --
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
wmblob |1.0.3-3 | source, alpha, amd64, hppa, hurd-i386, i386,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
wmblob | 1.0.3-3+b1 | armel, ia64
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
anymeal | 0.30-9 | source, alpha, amd64, armel, hppa, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
--- Reason ---
R
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
wmmisc | 1.1-5 | source, alpha, amd64, armel, hppa, hurd-i386, i386,
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
--- Reason --
FYI: The status of the tkmixer source package
in Debian's testing distribution has changed.
Previous version: 1.0-19
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint files.
FYI: The status of the transcriber source package
in Debian's testing distribution has changed.
Previous version: 1.5.1.1-4
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the nstx source package
in Debian's testing distribution has changed.
Previous version: 1.1-beta6-6
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint file
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #254966,
regarding nstx should pass through dns queries to a real dns server
to be marked as done.
This means that y
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #259339,
regarding nstx: return value of malloc() is never checked anywhere
to be marked as done.
This means that yo
Your message dated
with message-id <20100909203456.4772.94194.mass-bugs-cl...@merkel.debian.org>
and subject line tkmixer removed from Debian unstable
has caused the Debian Bug report #274636,
regarding tkmixer: channel Digital1 causes white noise
to be marked as done.
This means that you claim t
Your message dated
with message-id <20100909203525.4772.44963.mass-bugs-cl...@merkel.debian.org>
and subject line transcriber removed from Debian unstable
has caused the Debian Bug report #291482,
regarding transcriber: feature request: slow down sound like Audacity's "change
tempo"
to be marked
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #307772,
regarding nstx: Fail to parse some DNS responses
to be marked as done.
This means that you claim that the p
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #317786,
regarding nstx: init script doesn't report daemon start failure
to be marked as done.
This means that you c
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #393339,
regarding segfault in nstxd
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #398356,
regarding provide a way to name the interface
to be marked as done.
This means that you claim that the prob
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #428529,
regarding Starting nstx at arbitary times
to be marked as done.
This means that you claim that the problem
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #467216,
regarding nstxcd fails with IPv6 DNS resolver
to be marked as done.
This means that you claim that the prob
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #468446,
regarding Memleaks in nstxcd
to be marked as done.
This means that you claim that the problem has been deal
Your message dated
with message-id <20100909203456.4772.94194.mass-bugs-cl...@merkel.debian.org>
and subject line tkmixer removed from Debian unstable
has caused the Debian Bug report #477800,
regarding tkmixer: Doesn't run (can't open /dev/mixer)
to be marked as done.
This means that you claim t
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #515309,
regarding nstx: init restart action not equivalent to stop+start and fails
miserably
to be marked as done.
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #550401,
regarding return value of write ignored in nstx_tuntap.c
to be marked as done.
This means that you claim th
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #553297,
regarding nstx: Uses non-standard '_' in domain names
to be marked as done.
This means that you claim that
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #553299,
regarding nstx: Does not support cross-endianness
to be marked as done.
This means that you claim that the
Your message dated
with message-id <20100909203528.4772.62981.mass-bugs-cl...@merkel.debian.org>
and subject line nstx removed from Debian unstable
has caused the Debian Bug report #589328,
regarding Short write in nstx_tuntap.c
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> tags 475727 + confirmed
Bug #475727 [offlineimap] offlineimap: Aborts if the server refuses to store a
message
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
475727: http://bugs.debian.or
I think that I found one way to reproduce this in a way that would
serve for debugging purposes:
With a gmail account, if you are trying to upload to the gmail servers
an "e-mail" that is a chat of theirs, then they will refuse the upload
(tested also with mutt and icedove). The most informative m
Hi.
Or should I say "ping"?
Unfortunately, it seems that offlineimap is very sensitive to many
situations and dies quite frequently. I suspect that, aside from the
"die always", it may also be under some deadlock situations (or would
that be the "new" python 2.6 that is in sid)?
Apart from dying
Package: offlineimap
Severity: important
As I reported in another bug (about offlineimap dying too easily under
many circumstances), attached is what I see when I strace one of the
running threads of offlineimap when it is run with 10 connections to
initially mirror my gmail account to a local mai
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
varkon |1.18B-1 | source, alpha, amd64, hppa, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
varkon-programmer-manual |1.18B-1 | all
v
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
open.app | 0.1+20061029-3 | source
open.app | 0.1+20061029-3+b1 | kfreebsd-amd64, kfreebsd-i386
open.app | 0.1+20061029-3+b2 | hurd-i386
open.app | 0.1+20061029-3+b3 | alpha, amd64,
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
tkpaint |1.5.4-7 | source, all
--- Reason ---
RoQA; orphaned, unused, dead upstream, alternatives exist
-
37 matches
Mail list logo
