Processing of sendmail_8.14.8-1_amd64.changes

2014-10-03 Thread Debian FTP Masters
sendmail_8.14.8-1_amd64.changes uploaded successfully to localhost along with the files: sendmail-bin_8.14.8-1_amd64.deb rmail_8.14.8-1_amd64.deb sensible-mda_8.14.8-1_amd64.deb libmilter1.0.1_8.14.8-1_amd64.deb libmilter1.0.1-dbg_8.14.8-1_amd64.deb libmilter-dev_8.14.8-1_amd64.deb se

sendmail_8.14.8-1_amd64.changes ACCEPTED into experimental

2014-10-03 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 03 Oct 2014 14:48:33 +0200 Source: sendmail Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter1.0.1-dbg libmilter-dev sendmail-doc sendmail sendmail-base sendmail-cf Architecture: source amd64 all Ve

Bug#618570: marked as done (sendmail-cf/feature/block_bad_helo.m4 doesn't handle IPv6:::1)

2014-10-03 Thread Debian Bug Tracking System
Your message dated Fri, 03 Oct 2014 13:19:45 + with message-id and subject line Bug#618570: fixed in sendmail 8.14.8-1 has caused the Debian Bug report #618570, regarding sendmail-cf/feature/block_bad_helo.m4 doesn't handle IPv6:::1 to be marked as done. This means that you claim that the pro

Processing of cruft_0.9.17_amd64.changes

2014-10-03 Thread Debian FTP Masters
cruft_0.9.17_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: cruft_0.9.17_amd64.deb cruft_0.9.17.dsc cruft_0.9.17.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ.

Processing of cruft_0.9.17_amd64.changes

2014-10-03 Thread Debian FTP Masters
cruft_0.9.17_amd64.changes uploaded successfully to localhost along with the files: cruft_0.9.17_amd64.deb cruft_0.9.17.dsc cruft_0.9.17.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.deb

cruft_0.9.17_amd64.changes ACCEPTED into unstable

2014-10-03 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Oct 2014 14:53:47 +0200 Source: cruft Binary: cruft Architecture: source amd64 Version: 0.9.17 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Marcin Owsiany Description: cruft

Bug#763602: reportbug, mirage and pyrenamer not starting

2014-10-03 Thread ghpy
Package: reportbug Version: 6.5.1 Package: mirage Version: 0.9.5.1-3 Package: pyrenamer Version: 0.6.0-1.1 Apart from reportbug (#762612 merged with 758619) and mirage (#763602) I also get the same error message when trying to start pyrenamer. Judging from the time the problem arose first and

Bug#763928: tvtime: Crash when scanning for new channels

2014-10-03 Thread User
Package: tvtime Version: 1.0.2-12.1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome

Bug#80459: apt-move is using worng architecture

2014-10-03 Thread Peter Keel
> There's no way around this unless apt-get starts supporting cross-arch > downloads. Well it does, if your system is multiarch. I just tried to apt-move my amd64 and i386 packages, and lo and behold, it only moves amd64 ones. Actually, the code looks as if it only expects one architecture at mo