Processing of yorick_2.2.04+dfsg1-4_amd64.changes

yorick_2.2.04+dfsg1-4_amd64.changes uploaded successfully to localhost along with the files: yorick_2.2.04+dfsg1-4.dsc yorick_2.2.04+dfsg1-4.debian.tar.xz yorick-data_2.2.04+dfsg1-4_all.deb yorick-dbg_2.2.04+dfsg1-4_amd64.deb yorick-dev_2.2.04+dfsg1-4_amd64.deb

I would be grateful for your prompt reply.

Dear Good Friend, Compliment of the season, I am Mr.Abdel TRAORE, Director In charge of Auditing and accounting departmentof Bank Of Africa, BOA, I hope that you will not betray or expose this trustand confident that i am about to repose on you for the mutual benefit of ourboth families. I

pythia8_8.1.86-1.2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Dec 2015 13:08:49 +0100 Source: pythia8 Binary: pythia8-data libpythia8v5 libpythia8-dev libhepmcinterface8 libhepmcinterface8-dev pythia8-examples pythia8-root-interface pythia8-doc-html

Bug#800642: marked as done (pythia8 depends on obsolete package liblhapdf0)

Your message dated Mon, 28 Dec 2015 12:36:25 + with message-id and subject line Bug#800642: fixed in pythia8 8.1.86-1.2 has caused the Debian Bug report #800642, regarding pythia8 depends on obsolete package liblhapdf0 to be marked as done. This means

Bug#755535: marked as done (pythia8-data: Missing *.grid data files)

Your message dated Mon, 28 Dec 2015 12:36:25 + with message-id and subject line Bug#755535: fixed in pythia8 8.1.86-1.2 has caused the Debian Bug report #755535, regarding pythia8-data: Missing *.grid data files to be marked as done. This means that you

xmds REMOVED from testing

FYI: The status of the xmds source package in Debian's testing distribution has changed. Previous version: 1.6.6-7 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.

Bug#785605: marked as done (gummi: Clicking "Project" and then "Open Project" results in segfault.)

Your message dated Mon, 28 Dec 2015 18:18:57 + with message-id and subject line Bug#785605: fixed in gummi 0.6.5-7 has caused the Debian Bug report #785605, regarding gummi: Clicking "Project" and then "Open Project" results in segfault. to be marked as

gummi_0.6.5-7_multi.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Dec 2015 18:50:39 +0100 Source: gummi Binary: gummi Architecture: source Version: 0.6.5-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Bug#808791: marked as done (gummi: May ship in invalid directories after autoreconf)

Your message dated Mon, 28 Dec 2015 18:18:57 + with message-id and subject line Bug#808791: fixed in gummi 0.6.5-7 has caused the Debian Bug report #808791, regarding gummi: May ship in invalid directories after autoreconf to be marked as done. This means

Processed: Bug#785605 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 785605 pending Bug #785605 [gummi] gummi: Clicking "Project" and then "Open Project" results in segfault. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 785605:

depqbf 5.0-1 MIGRATED to testing

FYI: The status of the depqbf source package in Debian's testing distribution has changed. Previous version: 3.04-1 Current version: 5.0-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

Processed: Bug#808791 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 808791 pending Bug #808791 [gummi] gummi: May ship in invalid directories after autoreconf Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 808791:

compute 0.5-1 MIGRATED to testing

FYI: The status of the compute source package in Debian's testing distribution has changed. Previous version: 0.4-3 Current version: 0.5-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

Processing of yorick_2.2.04+dfsg1-4_amd64.changes

yorick_2.2.04+dfsg1-4_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: yorick_2.2.04+dfsg1-4.dsc yorick_2.2.04+dfsg1-4.debian.tar.xz yorick-data_2.2.04+dfsg1-4_all.deb yorick-dbg_2.2.04+dfsg1-4_amd64.deb yorick-dev_2.2.04+dfsg1-4_amd64.deb

yorick_2.2.04+dfsg1-4_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 28 Dec 2015 20:29:21 +0100 Source: yorick Binary: yorick yorick-dbg yorick-data yorick-dev yorick-mpy-mpich2 yorick-mpy-openmpi yorick-mpy-common yorick-doc yorick-full Architecture: source all amd64 Version:

Bug#808979: marked as done (yorick: FTBFS: )

Your message dated Mon, 28 Dec 2015 21:54:59 + with message-id and subject line Bug#808979: fixed in yorick 2.2.04+dfsg1-4 has caused the Debian Bug report #808979, regarding yorick: FTBFS: to be marked as done. This means that you claim that the problem

Processed: [bts-link] source package gummi

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gummi > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package gummi

# # bts-link upstream status pull for source package gummi # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #785605 (http://bugs.debian.org/785605) # Bug title: gummi: Clicking "Project" and then