Bug#596291: offlineimap getting stuck when run with multiple threads/connections

2010-09-13 Thread Stephen Gran
Hi,

A couple of final notes.  I get this hang even when running with -1, and
I only get this hang when on the same LAN as the IMAP server.  When
fetching remotely, it's fine.  Again, this points to a timing dependant
bug that is only tickled when the sync isn't being slowed down by
latency or something else.

Sorry I'm not being more helpful.

Cheers,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature


Bug#596609: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

amavis-stats | 0.1.22+dfsg-2 | source, all

--- Reason ---
RoQA; orphaned
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596609

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5dt-0001q1...@franck.debian.org



Bug#596581: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

wmnetselect | 0.85-6 | source, alpha, amd64, armel, hppa, hurd-i386, i386, 
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, unused, dead upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596581

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5ek-0001uf...@franck.debian.org



Bug#596619: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  wmcb |  0.2-8 | source, alpha, amd64, armel, hppa, hurd-i386, i386, 
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596619

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5fg-0001xy...@franck.debian.org



Bug#596610: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  archzoom |0.5.1-4 | source, all

--- Reason ---
RoQA; orphaned, dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596610

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5go-0001c6...@franck.debian.org



Bug#596582: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 wmfsm |0.34-13 | source, alpha, amd64, hppa, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
 wmfsm | 0.34-13+b1 | armel, ia64

--- Reason ---
RoQA; orphaned, dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596582

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5hx-0001sc...@franck.debian.org



Bug#596620: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   view3ds |   1.0.0-11 | source, hurd-i386, kfreebsd-amd64, kfreebsd-i386
   view3ds | 1.0.0-11+b1 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, dead upstream, unused, obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596620

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5io-00022v...@franck.debian.org



Bug#596592: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 steam | 2.2.31-4.3 | source
 steam |   2.2.31-6 | source, all
 steam-lib | 2.2.31-4.3 | hurd-i386
 steam-lib |   2.2.31-6 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; outdated, orphaned
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596592

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5kw-0002ai...@franck.debian.org



Bug#583598: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   tepache |  1.1-9 | source, all

--- Reason ---
dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 583...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/583598

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5m7-0002hm...@franck.debian.org



Bug#596583: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  wmmemmon |1.0.1-7 | source, alpha, amd64, armel, hppa, hurd-i386, i386, 
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596583

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5kt-0002di...@franck.debian.org



Bug#596585: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   p2c | 1.21alpha2-4 | source, alpha, amd64, armel, hppa, hurd-i386, i386, 
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596585

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5mx-0002rg...@franck.debian.org



Bug#596615: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

librvm-dev | 1.16+debian-4 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
   librvm1 | 1.16+debian-4 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
   rvm | 1.16+debian-4 | source
   rvm-dbg | 1.16+debian-4 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
 rvm-tools | 1.16+debian-4 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596615

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5ni-0002gh...@franck.debian.org



Bug#596587: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

newpki-client | 2.0.0+rc1-6 | source, alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, dead upstream, buggy
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596587

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5nr-0002mg...@franck.debian.org



Bug#596589: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libnewpki-dev | 2.0.0+rc1-4 | hurd-i386
libnewpki-dev | 2.0.0+rc1-5 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
libnewpki2 | 2.0.0+rc1-4 | hurd-i386
libnewpki2 | 2.0.0+rc1-5 | alpha, amd64, armel, hppa, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
newpki-lib | 2.0.0+rc1-4 | source
newpki-lib | 2.0.0+rc1-5 | source

--- Reason ---
RoQA; dead upstream, orphaned, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596589

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5rj-0003tz...@franck.debian.org



Bug#596580: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   wmscope | 3.0-11 | source, alpha, amd64, armel, hppa, hurd-i386, i386, 
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; orphaned, dead upstream, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596580

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5sf-0003xw...@franck.debian.org



Bug#596579: Removed package(s) from unstable

2010-09-13 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 wmavgload |0.7.0-9 | source, alpha, amd64, armel, hppa, i386, ia64, mips, 
mipsel, powerpc, s390, sparc

--- Reason ---
RoQA; unused, orphaned, dead upstream, plenty of alternatives
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 596...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/596579

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ov5t5-0003bn...@franck.debian.org



Bug#482592: numlockx: no LED activated

2010-09-13 Thread yellowprotoss
Package: numlockx
Severity: normal

this issue is not present under the sarge or lenny version of linux.

A fix would be so great. best regards

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages numlockx depends on:
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libx11-6  2:1.3.3-3  X11 client-side library
ii  libxtst6  2:1.1.0-3  X11 Testing -- Record extension li

numlockx recommends no packages.

Versions of packages numlockx suggests:
pn  x-display-manager  (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100913152947.27583.38856.report...@debian05.rp614v4



libjackasyn 0.11-5 MIGRATED to testing

2010-09-13 Thread Debian testing watch
FYI: The status of the libjackasyn source package
in Debian's testing distribution has changed.

  Previous version: 0.11-2
  Current version:  0.11-5

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3u-0007zb...@franck.debian.org



dict-misc REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the dict-misc source package
in Debian's testing distribution has changed.

  Previous version: 1.5A-2
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3t-0007y3...@franck.debian.org



adesklets REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the adesklets source package
in Debian's testing distribution has changed.

  Previous version: 0.6.1-5
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3t-0007xr...@franck.debian.org



latex.service REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the latex.service source package
in Debian's testing distribution has changed.

  Previous version: 0.1-5
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3u-0007z5...@franck.debian.org



kbiff 3.9-1 MIGRATED to testing

2010-09-13 Thread Debian testing watch
FYI: The status of the kbiff source package
in Debian's testing distribution has changed.

  Previous version: 3.8-1.1
  Current version:  3.9-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3u-0007yn...@franck.debian.org



psh REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the psh source package
in Debian's testing distribution has changed.

  Previous version: 1.8-9
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3u-0007zv...@franck.debian.org



ude REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the ude source package
in Debian's testing distribution has changed.

  Previous version: 0.2.9b-5
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3v-0007zr...@franck.debian.org



yabasic REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the yabasic source package
in Debian's testing distribution has changed.

  Previous version: 2.763-5
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3v-0007at...@franck.debian.org



xbsql REMOVED from testing

2010-09-13 Thread Debian testing watch
FYI: The status of the xbsql source package
in Debian's testing distribution has changed.

  Previous version: 0.11-8
  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. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ovc3v-0007ah...@franck.debian.org



Bug#596291: offlineimap getting stuck when run with multiple threads/connections

2010-09-13 Thread Stephen Gran
This one time, at band camp, Stephen Gran said:
> I have so far been unable to reproduce this when running offlineimap
> under strace, which suggests a timing dependant bug (kind of as
> suspected, but still not all that helpful, I realize).  The earlier
> strace (and the strace I see when attaching after it hangs) does suggest
> that a lock is not being releaesed somewhere, but I can't immediately
> see anything obviously wrong with the logic in the code.

Trying to run with -d thread under python2.6 gets me a recursion
exceeded exception, but I did manage to capture a lockup under 2.5:

Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .start(): starting thread
Copy message 2200 from packaging.clamav: .__bootstrap(): thread started
Copy message 2200 from packaging.clamav:
   Copy message 2200 IMAP[packaging.clamav] -> Maildir[packaging.clamav], 
LocalStatus[packaging.clamav]
Copy message 2200 from packaging.clamav: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0
Copy message 2200 from packaging.clamav: .release: success, value=1
Copy message 2200 from packaging.clamav: , 1)>.notify(): notifying 1 waiter
Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it
Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .release: success, value=1
Folder sync Lobefin[packaging.clamav]: , 0)>.notify(): no waiters
Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0
Copy message 2200 from packaging.clamav: .release: success, value=1
Copy message 2200 from packaging.clamav: , 1)>.notify(): notifying 1 waiter
Copy message 2200 from packaging.clamav: .__bootstrap(): normal return
Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it
Copy message 2200 from packaging.clamav: , 0)>.notify(): no waiters
Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .start(): starting thread
Copy message 2201 from packaging.clamav: .__bootstrap(): thread started
Copy message 2201 from packaging.clamav:
   Copy message 2201 IMAP[packaging.clamav] -> Maildir[packaging.clamav], 
LocalStatus[packaging.clamav]
Copy message 2201 from packaging.clamav: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0
Copy message 2201 from packaging.clamav: .release: success, value=1
Copy message 2201 from packaging.clamav: , 1)>.notify(): notifying 1 waiter
Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it
Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .release: success, value=1
Folder sync Lobefin[packaging.clamav]: , 0)>.notify(): no waiters
Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0
Copy message 2201 from packaging.clamav: .release: success, value=1
Copy message 2201 from packaging.clamav: , 1)>.notify(): notifying 1 waiter
Copy message 2201 from packaging.clamav: .__bootstrap(): normal return
Folder sync Lobefin[packaging.clamav]: , 0)>.wait(): got it
Copy message 2201 from packaging.clamav: , 0)>.notify(): no waiters
Folder sync Lobefin[packaging.clamav]: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .start(): starting thread
Copy message 2202 from packaging.clamav: .__bootstrap(): thread started
Copy message 2202 from packaging.clamav:
   Copy message 2202 IMAP[packaging.clamav] -> Maildir[packaging.clamav], 
LocalStatus[packaging.clamav]
Copy message 2202 from packaging.clamav: .acquire: success, value=0
Folder sync Lobefin[packaging.clamav]: .acquire(1): blocked waiting, value=0

And there it hangs.
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -



--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100913220506.ga30...@varinia.lobefin.net



Queres vir assistir a um treino do Real Madrid

2010-09-13 Thread Mourinho
 - This mail is a HTML mail. Not all elements could be shown in plain text 
mode. -

Real Madrid
Veja a versão
online
!
Caso não deseje voltar a receber campanhas publicitárias neste endereço de 
e-mail,
por favor
remova
o seu endereço