kmldonkey_2.0.5+kde4.3.3-4_source.changes ACCEPTED into unstable

2018-07-10 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 11 Jul 2018 07:51:54 +0200 Source: kmldonkey Binary: kmldonkey Architecture: source Version: 2.0.5+kde4.3.3-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Pino Toscano Descripti

Processing of kmldonkey_2.0.5+kde4.3.3-4_source.changes

2018-07-10 Thread Debian FTP Masters
kmldonkey_2.0.5+kde4.3.3-4_source.changes uploaded successfully to localhost along with the files: kmldonkey_2.0.5+kde4.3.3-4.dsc kmldonkey_2.0.5+kde4.3.3-4.debian.tar.bz2 kmldonkey_2.0.5+kde4.3.3-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.o

Bug#856948: marked as done (kmldonkey: Segfault starting)

2018-07-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Jul 2018 06:03:55 + with message-id and subject line Bug#856948: fixed in kmldonkey 2.0.5+kde4.3.3-4 has caused the Debian Bug report #856948, regarding kmldonkey: Segfault starting to be marked as done. This means that you claim that the problem has been dealt with

Processed: tagging 856948

2018-07-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 856948 = pending Bug #856948 [kmldonkey] kmldonkey: Segfault starting Added tag(s) pending; removed tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 856948: https://bugs.deb

mpdtoys is marked for autoremoval from testing

2018-07-10 Thread Debian testing autoremoval watch
mpdtoys 0.25 is marked for autoremoval from testing on 2018-07-16 It (build-)depends on packages with these RC bugs: 899571: libfishsound: Invalid maintainer address pkg-xiph-ma...@lists.alioth.debian.org

Bug#903476: bochs FTCBFS: multiple reasons

2018-07-10 Thread Helmut Grohne
Source: bochs Version: 2.6-6 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap bochs fails to cross build from source. There are a number of individual causes all rooted in the upstream build system. The attached patch fixes all of them. Let me go into detail: * The immediate f