Processing of c2html_0.9.6-3_amd64.changes

-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p5m9c-0007ze...@franck.debian.org

Processing of c2html_0.9.6-3_amd64.changes

-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p5m7i-0007cf...@kassia.debian.org

Processing of epos_2.5.37-9_i386.changes

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p5ohg-0003ir...@franck.debian.org

Processing of epos_2.5.37-9_i386.changes

-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p5ogp-0002r2...@ravel.debian.org

Processing of proofgeneral_3.7-4_i386.changes

-4_all.deb Greetings, Your Debian queue daemon (running on host franck.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/e1p5

Processing of proofgeneral_3.7-4_i386.changes

proofgeneral-doc_3.7-4_all.deb Greetings, Your Debian queue daemon (running on host ravel.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.o

Processing of seyon_2.20c-31_i386.changes

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p5ot9-0007bz...@franck.debian.org

Processing of seyon_2.20c-31_i386.changes

-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p5orc-0005or...@ravel.debian.org

Processing of flashybrid_0.16_i386.changes

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p53ij-0007ok...@franck.debian.org

Processing of flashybrid_0.16_i386.changes

-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p53gx-0001mc...@ravel.debian.org

Processing of mnogosearch_3.3.8-3_i386.changes

debian.org Archive: http://lists.debian.org/e1p53ds-0006ci...@franck.debian.org

Processing of mnogosearch_3.3.8-3_i386.changes

ct listmas...@lists.debian.org Archive: http://lists.debian.org/e1p53c2-00014d...@ravel.debian.org

Processing of lib3ds_1.3.0-5_i386.changes

, 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/e1p4zo1-0007xe...@franck.debian.org

Processing of isdnutils_3.9.20060704+dfsg.2-2_multi.changes

-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p4uzs-0001zm...@franck.debian.org

Processing of isdnutils_3.9.20060704+dfsg.2-1_multi.changes

-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p4eok-0008w8...@franck.debian.org

Processing of magyarispell_0.99.4-2_amd64.changes

) -- 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/e1p4jfi-0007qi...@franck.debian.org

Processing of numlockx_1.2-1_amd64.changes

, 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/e1p2lew-0001xk...@franck.debian.org

Processing of numlockx_1.2-1_amd64.changes

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/e1p2leu-00079d...@ravel.debian.org

acorn-fdisk_3.0.6-7_m68k.changes ACCEPTED

of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p2am9-df...@debian-ports.org

Processing of acorn-fdisk_3.0.6-7_i386.changes

-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p27f4-00020v...@franck.debian.org

Processing of palo_1.18_hppa.changes

a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p1yxd-0008ke...@franck.debian.org

Processing of qtparted_0.4.5-9_mipsel.changes

-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p0whw-0007nm...@franck.debian.org

Processing of qtparted_0.4.5-8_mipsel.changes

-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p0uu7-yx...@franck.debian.org

mock_1.0.8-3_amd64.changes ACCEPTED into unstable

devel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- 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.o

Processing of mock_1.0.8-3_amd64.changes

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ox3r3-0008q3...@franck.debian.org

mock_1.0.8-2_amd64.changes ACCEPTED into unstable

devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 597164 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Arc

Processing of mock_1.0.8-2_amd64.changes

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ox1qf-0005lw...@franck.debian.org

pympd_0.07-2_i386.changes ACCEPTED into unstable

Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 594129 Thank you for your contribution to Debian. -- 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.

yafray_0.0.9+dfsg-5_amd64.changes ACCEPTED into unstable

;. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1owzb0-hz...@franck.debian.org

Processing of yafray_0.0.9+dfsg-5_amd64.changes

-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1owyxs-0008le...@franck.debian.org

glfer_0.4.2-1_i386.changes ACCEPTED into unstable

of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1owlq8-00067k...@franck.debian.org

Processing of glfer_0.4.2-1_i386.changes

debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1owlfw-0005zy...@franck.debian.org

Bug#596759: Removed package(s) from unstable

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

Bug#596568: Removed package(s) from unstable

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

Bug#596758: Removed package(s) from unstable

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

Bug#596748: Removed package(s) from unstable

(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

Bug#596757: Removed package(s) from unstable

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

Bug#596766: Removed package(s) from unstable

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

Bug#596756: Removed package(s) from unstable

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

Bug#596621: Removed package(s) from unstable

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

Bug#596754: Removed package(s) from unstable

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

Bug#597009: Removed package(s) from unstable

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

Bug#596752: Removed package(s) from unstable

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

Bug#597008: Removed package(s) from unstable

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

Processing of pympd_0.07-2_i386.changes

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ovycl-6o...@franck.debian.org

Bug#596579: Removed package(s) from unstable

(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

Bug#596580: Removed package(s) from unstable

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

Bug#596589: Removed package(s) from unstable

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

Bug#596587: Removed package(s) from unstable

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

Bug#596615: Removed package(s) from unstable

) 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

Bug#596585: Removed package(s) from unstable

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

Bug#596583: Removed package(s) from unstable

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

Bug#583598: Removed package(s) from unstable

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

Bug#596592: Removed package(s) from unstable

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

Bug#596620: Removed package(s) from unstable

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

Bug#596582: Removed package(s) from unstable

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

Bug#596610: Removed package(s) from unstable

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

Bug#596619: Removed package(s) from unstable

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

Bug#596581: Removed package(s) from unstable

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

Bug#596609: Removed package(s) from unstable

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

Bug#596551: Removed package(s) from unstable

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

Bug#596550: Removed package(s) from unstable

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

Bug#596543: Removed package(s) from unstable

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

Bug#596553: Removed package(s) from unstable

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

Bug#596552: Removed package(s) from unstable

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

Bug#596534: Removed package(s) from unstable

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

Bug#596506: Removed package(s) from unstable

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

Bug#596533: Removed package(s) from unstable

; 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

Bug#477485: Removed package(s) from unstable

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

Bug#596532: Removed package(s) from unstable

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

Bug#596531: Removed package(s) from unstable

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

Bug#486860: Removed package(s) from unstable

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

Bug#596524: Removed package(s) from unstable

) 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

Bug#596535: Removed package(s) from unstable

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

isdnutils_3.9.20060704+dfsg.1-3_amd64.changes ACCEPTED

...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ou0up-0001as...@franck.debian.org

Processing of isdnutils_3.9.20060704+dfsg.1-3_amd64.changes

, 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/e1ou0mt-by...@franck.debian.org

Bug#596273: Removed package(s) from unstable

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

Bug#596272: Removed package(s) from unstable

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

Bug#596271: Removed package(s) from unstable

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

Bug#596114: Removed package(s) from unstable

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

Bug#596158: Removed package(s) from unstable

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

Bug#596157: Removed package(s) from unstable

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

Bug#596147: Removed package(s) from unstable

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

Bug#583597: Removed package(s) from unstable

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

Bug#596118: Removed package(s) from unstable

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

Bug#596146: Removed package(s) from unstable

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

Bug#593163: Removed package(s) from unstable

). 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

Bug#596145: Removed package(s) from unstable

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

Bug#596154: Removed package(s) from unstable

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

Bug#596116: Removed package(s) from unstable

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

Bug#595393: Removed package(s) from unstable

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

Bug#596115: Removed package(s) from unstable

. 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

Bug#595990: Removed package(s) from unstable

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

Bug#595989: Removed package(s) from unstable

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

Bug#595994: Removed package(s) from unstable

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

Bug#595988: Removed package(s) from unstable

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

Bug#595993: Removed package(s) from unstable

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

Bug#595987: Removed package(s) from unstable

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

Bug#595992: Removed package(s) from unstable

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

Bug#595997: Removed package(s) from unstable

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

  1   2   3   4   5   6   7   8   9   10   >