+++ /dev/null
-*.pyc
-Packages
-Sources
-neve-files
+++ /dev/null
-manpage.*
-*.1
+++ /dev/null
-alicia - make microchanges or microqueries of the overrides
-alyson - syncs the ISC-style configuration file with the SQL DB
-amber - 'installer' wrapper for security team
-andrea - looks for fixable descrepancies between stable and unstable
-ashley - display the contents of a .katie file
-billie - split a pool/ftp-site/whatever by architecture groups
-catherine - poolifies packages; i.e. moves them from legacy dists/ locations into the pool
-charisma - generates Maintainers files used by e.g. the Debian BTS
-cindy - override cruft checker
-claire - generates compatability symlink tree for legacy dists/ locations [obsolete]
-denise - outputs the override tables to text files
-emilie - syncs fingerprint and uid tables with a Debian LDAP DB
-fernanda - checker script for new packages in incoming
-halle - removes obsolete .changes files from proposed-updates
-heidi - manipulates suite tags; i.e. removes/adds packages from any given suite
-helena - produces a report on NEW and BYHAND packages
-jenna - generates lists of files in suites which are then fed to apt-ftparchive
-jennifer - processes packages in incoming
-jeri - basic dependency checking for proposed-updates
-julia - Sync PostgreSQL users with (LDAP-generated) passwd file
-katie - common code used by lisa, jennifer, kelly and others
-kelly - installs packages into the pool
-lauren - manually reject packages from proposed-updates
-lisa - processes NEW and BYHAND packages
-madison - shows which suites a package is in
-melanie - removes packages from suites
-natalie - manpiulates/list override entries
-neve - populates the SQL database
-nina - split queue/done into a date-based directory structure
-rene - check for obsolete or duplicated packages
-rose - initial setup of an archive
-rosamund - check for users with no packages in the archive
-rhona - cleans unused/superseded packages out of the pool and the database
-saffron - stats pr0n generator
-shania - cleans cruft from incoming
-tea - various sanity checks of the database and archive
-ziyi - creates Release files
-
-With apologies to Alicia Silverstone, Alyson Hannigan, Amber Benson,
- Andrea Corr, Ashley Judd, Catherine Zeta Jones, Charisma Carpenter,
- Cindy Crawford, Claire Forlani, Denise Richards, Emilie de Ravin,
- Fernanda Tavares, Halle Berry, Heidi Klum, Helena Christensen, Jenna
- Elfman, Jennifer Lopez, Jeri Ryan, Julia Roberts, Katie Holmes, Kelly
- Brook, Lauren Lee Smith, Lisa Falkner, Madison Michele, Melanie Sykes,
- Natalie Portman, Neve Campbell, Nina Garbiras, Rene Russo, Rosamund Pike, Rose
- McGowan, Rhona Mitra, Saffron Burrows, Shania Twain, Tea Leoni and
- Ziyi Zhang.
-
- In Use Elsewhere
- ================
-
-Christina (Aguilera) [lene]
-Emily (Mortimer) [lene]
-Lene (Nystrom) [lene]
-Lonneke (Engel) [lene]
-Louise (Nurding) [lene]
-
-Britney (Spears) [aj]
-
-Michelle (Yeoh) [joey]
-Courtney (Cox) [neuro]
-Sandra (Bullock) [neuro]
-
-Linda (Evangelista) [python lintian]
-Jane (Fonda) [linda over the entire archive]
-Lucy (Lawless) [files from jane -> html]
-
-Kate (Hudson, Beckinsale, Winslet) [kde text editor]
-
-Amanda (Peet) [Backup software]
-
-Canonical Names
----------------
-
-Anastacia
-Bridget (Hall)
-Geri (Haliwell)
-Kari (Wuhrer)
-Heather (Graham)
-Hilarie (Burton)
-Lorraine (Van Wyk)
-Poppy (Montgomery)
-Teri (Hatcher)
-
- Possible Future Candidates
- ==========================
-
-Alessandra (Ambrosia)
-Alyssa (Milliano)
-Amy (Brenneman)
-Angelina (Jolie)
-Bethany (Joy Lenz)
-Billie (Piper)
-Cameron (Diaz)
-Carly (Pope)
-Carrie (Ann Moss)
-Charlize (Theron)
-Daniela (Pestova)
-Dannii (Minogue)
-Dido
-Donna (Air)
-Elisabeth (Shue)
-Elisha (Cuthbert)
-Eliza (Dushku)
-Estella (Warren)
-Emma (Caulfield)
-Famke (Janssen)
-Gail (Porter)
-Gillian (Anderson)
-Gina (Gershon)
-Gwyneth (Paltrow)
-Holly (Marie Combs)
-Janel (Moloney)
-Jessica (Alba, Biel)
-Jewel (Kilcher)
-Jill (Hennessy)
-Josie (Maran)
-Katherine (Heigl)
-Kim (Smith)
-Kirsten (Dunst)
-Kristin (Kreuk)
-Kylie (Minogue)
-Laetitia (Casta)
-Lana (Parrilla)
-Liv (Tyler)
-Marcia (Cross)
-Mariska (Hargitay)
-Michelle (Hunziker)
-Mira (Sorvino)
-Monica (Belluci)
-Naima (Belkhiati)
-Nicole (Appleton)
-Rebecca (Romijn-Stamos)
-Reese (Witherspoon)
-Salma (Hayek)
-Sarah (Whatmore)
-Shannen (Doherty)
-Shiri (Appleby)
-Sophia (Bush)
-Sophie (Marceau)
-Stephanie (March)
-Suzanne (Cryer)
-Tara (Reid)
-Tasha (Tilberg)
-Tiffani (Amber Thiesen)
-Tricia (Helfer)
-Uma (Thurman)
-Veronica (Varekova)
-Virginie (Leoyden)
-Yamila (Diaz)
+++ /dev/null
-[ This was some notes to myself that I made while removing potato; I
- kept it because it turned out to be a far more traumatic experience
- than was necesary. Hopefully rhona will be fixed by the time I need
- to do this again which would obsolete most of the complex SQL
- crap. (JT) ]
-
-
- Potato Removal Plan
- -------------------
-
-o Create potato copy on archive.debian.org
-o poolize any not-just-potato files with monica.
-o force-remove any just-potato files (i.e. by setting last used to 3 weeks ago and run rhona)
-o remove any files (dists/potato) (NB: not pool symlinks!)
-o remove oldstable etc. from the db and config files
-
-********************************************************************************
-DROP TABLE moo;
-
-SELECT f.id INTO TEMP moo FROM files f, binaries b, bin_associations ba
- WHERE ba.suite IN (2, 3) AND ba.bin = b.id AND f.id = b.file
-EXCEPT
-SELECT f.id FROM files f, binaries b, bin_associations ba
- WHERE ba.suite NOT IN (2, 3) AND ba.bin = b.id AND f.id = b.file;
-
-CREATE INDEX moo_index on moo (id);
-VACUUM; VACUUM ANALYZE;
-
-EXPLAIN UPDATE files set last_used = '2003/09/03'
- WHERE EXISTS (
- SELECT id FROM moo WHERE files.id = moo.id);
-
-DELeditmeETE FROM bin_associations WHERE suite IN (2, 3);
-
-[ run rhona ]
-
-****************************************
-
-DROP TABLE moo;
-
-SELECT f.id INTO TEMP moo FROM files f, source s, src_associations sa, dsc_files df
- WHERE sa.suite IN (2, 3) AND sa.source = s.id AND df.source = s.id AND df.file = f.id
- AND NOT EXISTS (SELECT b.id FROM binaries b WHERE b.source = s.id)
-EXCEPT
-SELECT f.id FROM files f, source s, src_associations sa, dsc_files df
- WHERE sa.suite NOT IN (2, 3) AND sa.source = s.id AND df.source = s.id AND df.file = f.id;
-
-CREATE INDEX moo_index on moo (id);
-VACUUM; VACUUM ANALYZE;
-
-EXPLAIN UPDATE files set last_used = '2003/09/03'
- WHERE EXISTS (
- SELECT id FROM moo WHERE files.id = moo.id);
-
-DELeditmeETE FROM src_associations WHERE suite IN (2, 3);
-
-[ run rhona ]
-
-********************************************************************************
-
-[Code for catherine (poolize); to go after the move of the file]
-# Create symlink
-src = utils.clean_symlink(destination, legacy_filename, Cnf["Dir::Root"]);
-if verbose:
- print "Symlinking: %s -> %s" % (legacy_filename, src);
-if not no_action:
- os.symlink(src, legacy_filename);
-
-
-[Query for catherine]
-SELECT l.path, f.filename, f.id as files_id, c.name as component
- FROM files f, binaries b, bin_associations ba, location l, component c
- WHERE ba.suite NOT IN (2, 3) AND f.filename ~ '^potato'
- AND ba.bin = b.id AND f.id = b.file AND l.id = f.location
- AND c.id = l.component
-UNION
-SELECT DISTINCT ON (f.filename) l.path, f.filename, f.id as files_id, c.name as component
- FROM files f, source s, src_associations sa, dsc_files df,
- location l, component c
- WHERE sa.suite NOT IN (2, 3) AND f.filename ~ '^potato'
- AND sa.source = s.id AND df.source = s.id AND f.id = df.file
- AND l.id = f.location AND c.id = l.component;
-Currently used substitutions in katie:
-======================================
+Currently used substitutions in dak
+===================================
Global
------
o __BCC__ [*]
o __BUG_SERVER__
o __DISTRO__
- o __KATIE_ADDRESS__
+ o __DAK_ADDRESS__
Per package
-----------
Misc
----
+
o __ANNOUNCE_LIST_ADDRESS__
o __BUG_NUMBER__
o __CONTROL_MESSAGE__
+++ /dev/null
-From: __ALICIA_ADDRESS__
-To: __BUG_NUMBER__-close@__BUG_SERVER__
-__CC__
-__BCC__
-Subject: Bug#__BUG_NUMBER__: fixed
-
-We believe that the bug you reported is now fixed; the following
-changes were made to the overrides...
-
-__SUMMARY__
-
-Thank you for reporting the bug, which will now be closed. If you
-have further comments please address them to __BUG_NUMBER__@__BUG_SERVER__.
-
-This message was generated automatically; if you believe that there is
-a problem with it please contact the archive administrators by mailing
-__ADMIN_ADDRESS__.
-
-__DISTRO__ distribution maintenance software
-pp.
-__WHOAMI__ (the ftpmaster behind the curtain)
+++ /dev/null
-From: __KATIE_ADDRESS__
-To: __WHOAMI__ <katie@security.debian.org>
-__BCC__
-Subject: Template Advisory __ADVISORY__
-
-------------------------------------------------------------------------
-Debian Security Advisory __ADVISORY__ security@debian.org
-http://www.debian.org/security/ __WHOAMI__
-__DATE__
-------------------------------------------------------------------------
-
-Package : __PACKAGE__
-Vulnerability : XXX
-Problem type : local/remote XXX
-Debian-specific: XXX
-CVE Id(s) : XXX
-CERT advisory : XXX
-BugTraq ID : XXX
-Debian Bug : XXX
-
-...
-
-[single issue]
-For the stable distribution (woody), this problem has been fixed in version XXX
-
-For the old stable distribution (potato), this problem has been fixed in
-version XXX
-
-[multiple issues]
-For the stable distribution (woody), these problems have been fixed in version
-XXX
-
-For the old stable distribution (potato), these problems have been fixed in
-version XXX
-
-
-We recommend that you upgrade your __PACKAGE__ package.
-
-Upgrade instructions
---------------------
-
-wget url
- will fetch the file for you
-dpkg -i file.deb
- will install the referenced file.
-
-If you are using the apt-get package manager, use the line for
-sources.list as given below:
-
-apt-get update
- will update the internal database
-apt-get upgrade
- will install corrected packages
-
-You may use an automated update by adding the resources from the
-footer to the proper configuration.
-
-__ADVISORY_TEXT__
-
-
- These files will probably be moved into the stable distribution on
- its next update.
-
----------------------------------------------------------------------------------
-For apt-get: deb http://security.debian.org/ stable/updates main
-For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
-Mailing list: debian-security-announce@lists.debian.org
-Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
+++ /dev/null
-From: __KATIE_ADDRESS__
-To: __MAINTAINER_TO__
-__BCC__
-Precedence: bulk
-Subject: __CHANGES_FILENAME__ ACCEPTED__SUITE__
-
-__REJECT_MESSAGE__
-Accepted:
-__SUMMARY__
-
-Thank you for your contribution to __DISTRO__.
+++ /dev/null
-From: __MAINTAINER_FROM__
-To: __ANNOUNCE_LIST_ADDRESS__
-__BCC__
-Subject: Accepted __SOURCE__ __VERSION__ (__ARCHITECTURE__)
-
-__FILE_CONTENTS__
-
-Accepted:
-__SHORT_SUMMARY__
+++ /dev/null
-From: __MAINTAINER_FROM__
-To: __BUG_NUMBER__-close@__BUG_SERVER__
-__BCC__
-Subject: Bug#__BUG_NUMBER__: fixed in __SOURCE__ __VERSION__
-
-Source: __SOURCE__
-Source-Version: __VERSION__
-
-We believe that the bug you reported is fixed in the latest version of
-__SOURCE__, which is due to be installed in the __DISTRO__ FTP archive:
-
-__SHORT_SUMMARY__
-__STABLE_WARNING__
-
-A summary of the changes between this version and the previous one is
-attached.
-
-Thank you for reporting the bug, which will now be closed. If you
-have further comments please address them to __BUG_NUMBER__@__BUG_SERVER__,
-and the maintainer will reopen the bug report if appropriate.
-
-__DISTRO__ distribution maintenance software
-pp.
-__MAINTAINER__ (supplier of updated __SOURCE__ package)
-
-(This message was generated automatically at their request; if you
-believe that there is a problem with it please contact the archive
-administrators by mailing __ADMIN_ADDRESS__)
-
-
-__FILE_CONTENTS__
+++ /dev/null
-From: __MAINTAINER_FROM__
-To: control@__BUG_SERVER__
-Cc: __MAINTAINER_TO__
-__BCC__
-Subject: Fixed in upload of __SOURCE__ __VERSION__ to experimental
-
-__CONTROL_MESSAGE__
-quit
-
-This message was generated automatically in response to an
-upload to the experimental distribution. The .changes file follows.
-
-__FILE_CONTENTS__
+++ /dev/null
-From: __MAINTAINER_FROM__
-To: control@__BUG_SERVER__
-Cc: __MAINTAINER_TO__
-__BCC__
-Subject: Fixed in NMU of __SOURCE__ __VERSION__
-
-__CONTROL_MESSAGE__
-quit
-
-This message was generated automatically in response to a
-non-maintainer upload. The .changes file follows.
-
-__FILE_CONTENTS__
+++ /dev/null
-From: __KATIE_ADDRESS__
-To: __MAINTAINER_TO__
-__BCC__
-Precedence: bulk
-Subject: __CHANGES_FILENAME__ is NEW
-
-__SUMMARY__
-
-Your package contains new components which requires manual editing of
-the override file. It is ok otherwise, so please be patient. New
-packages are usually added to the override file about once a week.
-
-You may have gotten the distribution wrong. You'll get warnings above
-if files already exist in other distributions.
+++ /dev/null
-From: __KATIE_ADDRESS__
-To: __MAINTAINER_TO__
-__BCC__
-Precedence: junk
-Subject: __SOURCE__ override disparity
-
-There are disparities between your recently accepted upload and the
-override file for the following file(s):
-
-__SUMMARY__
-Either the package or the override file is incorrect. If you think
-the override is correct and the package wrong please fix the package
-so that this disparity is fixed in the next upload. If you feel the
-override is incorrect then please reply to this mail and explain why.
-
-[NB: this is an automatically generated mail; if you replied to one
-like it before and have not received a response yet, please ignore
-this mail. Your reply needs to be processed by a human and will be in
-due course, but until then the installer will send these automated
-mails; sorry.]
-
---
-__DISTRO__ distribution maintenance software
-
-(This message was generated automatically; if you believe that there
-is a problem with it please contact the archive administrators by
-mailing __ADMIN_ADDRESS__)
+++ /dev/null
-From: __REJECTOR_ADDRESS__
-To: __MAINTAINER_TO__
-__BCC__
-__CC__
-Precedence: bulk
-Subject: __CHANGES_FILENAME__ REJECTED
-
-__MANUAL_REJECT_MESSAGE__
-__REJECT_MESSAGE__
-
-===
-
-If you don't understand why your files were rejected, or if the
-override file requires editing, reply to this email.
+++ /dev/null
-From: __KATIE_ADDRESS__
-To: __MAINTAINER_TO__
-__BCC__
-Precedence: bulk
-Subject: __CHANGES_FILENAME__ INSTALLED__SUITE__
-
-__REJECT_MESSAGE__
-Installing:
-__SUMMARY__
-
-Thank you for your contribution to __DISTRO__.
+++ /dev/null
-From: __REJECTOR_ADDRESS__
-To: __MAINTAINER_TO__
-__CC__
-__BCC__
-Subject: __CHANGES_FILENAME__ UNACCEPT
-
-__REJECT_MESSAGE__
-
-===
-
-Despite being ACCEPTed, this package failed the database sanity checks
-at the time of install. This should only happen rarely and in
-corner-cases (a binary upload of a package which has since been
-melanie'd for example), so no code to do the necessary unaccept
-actions has been written. These actions (e.g. bug reopening,
-announcement rescinding, etc.) will have to be done by hand. Also,
-the files have been left in the accepted directory; please deal with
-them as well.
+++ /dev/null
-From: __KATIE_ADDRESS__
-To: __MAINTAINER_TO__
-__CC__
-__BCC__
-Precedence: bulk
-Subject: __CHANGES_FILENAME__ REJECTED from proposed-updates
-
-Your package was rejected by an ftp master on behalf of
-__STABLE_REJECTOR__, if you have any questions or
-comments regarding this rejection, please address them to him as we
-can't help you.
-
-The reason given for rejection was:
-
-__MANUAL_REJECT_MESSAGE__
-
-Please see:
-
- __MORE_INFO_URL__
-
-for more details.
-
-===
-
-Your rejected .changes files is in queue/REJECT/; the other files
-have been removed from proposed-updates and will be auto-cleaned as
-normal.
+++ /dev/null
-From: Ben Collins <bxa@ftp-master.debian.org>
-To: crypt@bxa.doc.gov
-Cc: bxa@ftp-master.debian.org
-__BCC__
-Precedence: junk
-Subject: Addition to __DISTRO__ Source Code
-
- Department of Commerce
- Bureau of Export Administration
- Office of Strategic Trade and Foreign Policy Controls
- 14th Street and Pennsylvania Ave., N.W.
- Room 2705
- Washington, DC 20230
-
-Re: Unrestricted Encryption Source Code Notification
-Commodity: Addition to Debian Source Code
-
-Dear Sir/Madam,
-
- Pursuant to paragraph (e)(1) of Part 740.13 of the U.S. Export
-Administration Regulations ("EAR", 15 CFR Part 730 et seq.), we are
-providing this written notification of the Internet location of the
-unrestricted, publicly available Source Code of a package being added
-to the Debian Source Code. Debian Source Code is a free operating
-system developed by a group of individuals, coordinated by the
-non-profit Software in the Public Interest. This notification serves
-as a notification of an addition of new software to the Debian
-archive. Previous notifications have covered the archive as a whole
-and other software added in the past. This archive is updated from
-time to time, but its location is constant. Therefore this
-notification serves as a one-time notification for subsequent updates
-that may occur in the future to the software covered by this
-notification. Such updates may add or enhance cryptographic
-functionality of the Debian operating system. The Internet location
-for the Debian Source Code is: http://ftp.debian.org/debian/
-
-This site is mirrored to a number of other sites located outside the
-United States.
-
-The following software is being added to the Debian archive:
-
-----------------------------------------------------------------------
-__BINARY_DESCRIPTIONS__
-----------------------------------------------------------------------
-
-If you have any questions, please email me at bxa@ftp-master.debian.org,
-or call me on (804) 695-9730.
-
- Sincerely,
- Ben Collins
- Debian Developer
+++ /dev/null
-From: __FROM_ADDRESS__
-To: __MAINTAINER_TO__
-__CC__
-Subject: Comments regarding __CHANGES_FILENAME__
-
-__PROD_MESSAGE__
-
+++ /dev/null
-From: __MELANIE_ADDRESS__
-To: __BUG_NUMBER__-close@__BUG_SERVER__
-__CC__
-__BCC__
-Subject: Bug#__BUG_NUMBER__: fixed
-
-We believe that the bug you reported is now fixed; the following
-package(s) have been removed from __SUITE_LIST__:
-
-__SUMMARY__
-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 (__MASTER_ARCHIVE__) and will not propagate to any
-mirrors (__PRIMARY_MIRROR__ included) until the next cron.daily run at the
-earliest.
-
-Packages are never 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.
-
-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 __BUG_NUMBER__@__BUG_SERVER__.
-
-This message was generated automatically; if you believe that there is
-a problem with it please contact the archive administrators by mailing
-__ADMIN_ADDRESS__.
-
-__DISTRO__ distribution maintenance software
-pp.
-__WHOAMI__ (the ftpmaster behind the curtain)
--- /dev/null
+From: __OVERRIDE_ADDRESS__
+To: __BUG_NUMBER__-close@__BUG_SERVER__
+__CC__
+__BCC__
+Subject: Bug#__BUG_NUMBER__: fixed
+
+We believe that the bug you reported is now fixed; the following
+changes were made to the overrides...
+
+__SUMMARY__
+
+Thank you for reporting the bug, which will now be closed. If you
+have further comments please address them to __BUG_NUMBER__@__BUG_SERVER__.
+
+This message was generated automatically; if you believe that there is
+a problem with it please contact the archive administrators by mailing
+__ADMIN_ADDRESS__.
+
+__DISTRO__ distribution maintenance software
+pp.
+__WHOAMI__ (the ftpmaster behind the curtain)
--- /dev/null
+From: __DAK_ADDRESS__
+To: __MAINTAINER_TO__
+__BCC__
+Precedence: bulk
+Subject: __CHANGES_FILENAME__ INSTALLED__SUITE__
+
+__REJECT_MESSAGE__
+Installing:
+__SUMMARY__
+
+Thank you for your contribution to __DISTRO__.
--- /dev/null
+From: __REJECTOR_ADDRESS__
+To: __MAINTAINER_TO__
+__CC__
+__BCC__
+Subject: __CHANGES_FILENAME__ UNACCEPT
+
+__REJECT_MESSAGE__
+
+===
+
+Despite being ACCEPTed, this package failed the database sanity checks
+at the time of install. This should only happen rarely and in
+corner-cases (a binary upload of a package which has since been
+'dak rm'-d for example), so no code to do the necessary unaccept
+actions has been written. These actions (e.g. bug reopening,
+announcement rescinding, etc.) will have to be done by hand. Also,
+the files have been left in the accepted directory; please deal with
+them as well.
--- /dev/null
+From: Ben Collins <bxa@ftp-master.debian.org>
+To: crypt@bxa.doc.gov
+Cc: bxa@ftp-master.debian.org
+__BCC__
+Precedence: junk
+Subject: Addition to __DISTRO__ Source Code
+
+ Department of Commerce
+ Bureau of Export Administration
+ Office of Strategic Trade and Foreign Policy Controls
+ 14th Street and Pennsylvania Ave., N.W.
+ Room 2705
+ Washington, DC 20230
+
+Re: Unrestricted Encryption Source Code Notification
+Commodity: Addition to Debian Source Code
+
+Dear Sir/Madam,
+
+ Pursuant to paragraph (e)(1) of Part 740.13 of the U.S. Export
+Administration Regulations ("EAR", 15 CFR Part 730 et seq.), we are
+providing this written notification of the Internet location of the
+unrestricted, publicly available Source Code of a package being added
+to the Debian Source Code. Debian Source Code is a free operating
+system developed by a group of individuals, coordinated by the
+non-profit Software in the Public Interest. This notification serves
+as a notification of an addition of new software to the Debian
+archive. Previous notifications have covered the archive as a whole
+and other software added in the past. This archive is updated from
+time to time, but its location is constant. Therefore this
+notification serves as a one-time notification for subsequent updates
+that may occur in the future to the software covered by this
+notification. Such updates may add or enhance cryptographic
+functionality of the Debian operating system. The Internet location
+for the Debian Source Code is: http://ftp.debian.org/debian/
+
+This site is mirrored to a number of other sites located outside the
+United States.
+
+The following software is being added to the Debian archive:
+
+----------------------------------------------------------------------
+__BINARY_DESCRIPTIONS__
+----------------------------------------------------------------------
+
+If you have any questions, please email me at bxa@ftp-master.debian.org,
+or call me on (804) 695-9730.
+
+ Sincerely,
+ Ben Collins
+ Debian Developer
--- /dev/null
+From: __FROM_ADDRESS__
+To: __MAINTAINER_TO__
+__CC__
+Subject: Comments regarding __CHANGES_FILENAME__
+
+__PROD_MESSAGE__
+
--- /dev/null
+From: __DAK_ADDRESS__
+To: __MAINTAINER_TO__
+__BCC__
+Precedence: bulk
+Subject: __CHANGES_FILENAME__ ACCEPTED__SUITE__
+
+__REJECT_MESSAGE__
+Accepted:
+__SUMMARY__
+
+Thank you for your contribution to __DISTRO__.
--- /dev/null
+From: __MAINTAINER_FROM__
+To: __ANNOUNCE_LIST_ADDRESS__
+__BCC__
+Subject: Accepted __SOURCE__ __VERSION__ (__ARCHITECTURE__)
+
+__FILE_CONTENTS__
+
+Accepted:
+__SHORT_SUMMARY__
--- /dev/null
+From: __MAINTAINER_FROM__
+To: __BUG_NUMBER__-close@__BUG_SERVER__
+__BCC__
+Subject: Bug#__BUG_NUMBER__: fixed in __SOURCE__ __VERSION__
+
+Source: __SOURCE__
+Source-Version: __VERSION__
+
+We believe that the bug you reported is fixed in the latest version of
+__SOURCE__, which is due to be installed in the __DISTRO__ FTP archive:
+
+__SHORT_SUMMARY__
+__STABLE_WARNING__
+
+A summary of the changes between this version and the previous one is
+attached.
+
+Thank you for reporting the bug, which will now be closed. If you
+have further comments please address them to __BUG_NUMBER__@__BUG_SERVER__,
+and the maintainer will reopen the bug report if appropriate.
+
+__DISTRO__ distribution maintenance software
+pp.
+__MAINTAINER__ (supplier of updated __SOURCE__ package)
+
+(This message was generated automatically at their request; if you
+believe that there is a problem with it please contact the archive
+administrators by mailing __ADMIN_ADDRESS__)
+
+
+__FILE_CONTENTS__
--- /dev/null
+From: __MAINTAINER_FROM__
+To: control@__BUG_SERVER__
+Cc: __MAINTAINER_TO__
+__BCC__
+Subject: Fixed in upload of __SOURCE__ __VERSION__ to experimental
+
+__CONTROL_MESSAGE__
+quit
+
+This message was generated automatically in response to an
+upload to the experimental distribution. The .changes file follows.
+
+__FILE_CONTENTS__
--- /dev/null
+From: __MAINTAINER_FROM__
+To: control@__BUG_SERVER__
+Cc: __MAINTAINER_TO__
+__BCC__
+Subject: Fixed in NMU of __SOURCE__ __VERSION__
+
+__CONTROL_MESSAGE__
+quit
+
+This message was generated automatically in response to a
+non-maintainer upload. The .changes file follows.
+
+__FILE_CONTENTS__
--- /dev/null
+From: __DAK_ADDRESS__
+To: __MAINTAINER_TO__
+__BCC__
+Precedence: bulk
+Subject: __CHANGES_FILENAME__ is NEW
+
+__SUMMARY__
+
+Your package contains new components which requires manual editing of
+the override file. It is ok otherwise, so please be patient. New
+packages are usually added to the override file about once a week.
+
+You may have gotten the distribution wrong. You'll get warnings above
+if files already exist in other distributions.
--- /dev/null
+From: __DAK_ADDRESS__
+To: __MAINTAINER_TO__
+__BCC__
+Precedence: junk
+Subject: __SOURCE__ override disparity
+
+There are disparities between your recently accepted upload and the
+override file for the following file(s):
+
+__SUMMARY__
+Either the package or the override file is incorrect. If you think
+the override is correct and the package wrong please fix the package
+so that this disparity is fixed in the next upload. If you feel the
+override is incorrect then please reply to this mail and explain why.
+
+[NB: this is an automatically generated mail; if you replied to one
+like it before and have not received a response yet, please ignore
+this mail. Your reply needs to be processed by a human and will be in
+due course, but until then the installer will send these automated
+mails; sorry.]
+
+--
+__DISTRO__ distribution maintenance software
+
+(This message was generated automatically; if you believe that there
+is a problem with it please contact the archive administrators by
+mailing __ADMIN_ADDRESS__)
--- /dev/null
+From: __REJECTOR_ADDRESS__
+To: __MAINTAINER_TO__
+__BCC__
+__CC__
+Precedence: bulk
+Subject: __CHANGES_FILENAME__ REJECTED
+
+__MANUAL_REJECT_MESSAGE__
+__REJECT_MESSAGE__
+
+===
+
+If you don't understand why your files were rejected, or if the
+override file requires editing, reply to this email.
--- /dev/null
+From: __DAK_ADDRESS__
+To: __MAINTAINER_TO__
+__CC__
+__BCC__
+Precedence: bulk
+Subject: __CHANGES_FILENAME__ REJECTED from proposed-updates
+
+Your package was rejected by an ftp master on behalf of
+__STABLE_REJECTOR__, if you have any questions or
+comments regarding this rejection, please address them to him as we
+can't help you.
+
+The reason given for rejection was:
+
+__MANUAL_REJECT_MESSAGE__
+
+Please see:
+
+ __MORE_INFO_URL__
+
+for more details.
+
+===
+
+Your rejected .changes files is in queue/REJECT/; the other files
+have been removed from proposed-updates and will be auto-cleaned as
+normal.
--- /dev/null
+From: __RM_ADDRESS__
+To: __BUG_NUMBER__-close@__BUG_SERVER__
+__CC__
+__BCC__
+Subject: Bug#__BUG_NUMBER__: fixed
+
+We believe that the bug you reported is now fixed; the following
+package(s) have been removed from __SUITE_LIST__:
+
+__SUMMARY__
+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 (__MASTER_ARCHIVE__) and will not propagate to any
+mirrors (__PRIMARY_MIRROR__ included) until the next cron.daily run at the
+earliest.
+
+Packages are never 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.
+
+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 __BUG_NUMBER__@__BUG_SERVER__.
+
+This message was generated automatically; if you believe that there is
+a problem with it please contact the archive administrators by mailing
+__ADMIN_ADDRESS__.
+
+__DISTRO__ distribution maintenance software
+pp.
+__WHOAMI__ (the ftpmaster behind the curtain)
--- /dev/null
+From: __DAK_ADDRESS__
+To: __WHOAMI__ <dak@security.debian.org>
+__BCC__
+Subject: Template Advisory __ADVISORY__
+
+------------------------------------------------------------------------
+Debian Security Advisory __ADVISORY__ security@debian.org
+http://www.debian.org/security/ __WHOAMI__
+__DATE__
+------------------------------------------------------------------------
+
+Package : __PACKAGE__
+Vulnerability : XXX
+Problem type : local/remote XXX
+Debian-specific: XXX
+CVE Id(s) : XXX
+CERT advisory : XXX
+BugTraq ID : XXX
+Debian Bug : XXX
+
+...
+
+[single issue]
+For the stable distribution (woody), this problem has been fixed in version XXX
+
+For the old stable distribution (potato), this problem has been fixed in
+version XXX
+
+[multiple issues]
+For the stable distribution (woody), these problems have been fixed in version
+XXX
+
+For the old stable distribution (potato), these problems have been fixed in
+version XXX
+
+
+We recommend that you upgrade your __PACKAGE__ package.
+
+Upgrade instructions
+--------------------
+
+wget url
+ will fetch the file for you
+dpkg -i file.deb
+ will install the referenced file.
+
+If you are using the apt-get package manager, use the line for
+sources.list as given below:
+
+apt-get update
+ will update the internal database
+apt-get upgrade
+ will install corrected packages
+
+You may use an automated update by adding the resources from the
+footer to the proper configuration.
+
+__ADVISORY_TEXT__
+
+
+ These files will probably be moved into the stable distribution on
+ its next update.
+
+---------------------------------------------------------------------------------
+For apt-get: deb http://security.debian.org/ stable/updates main
+For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
+Mailing list: debian-security-announce@lists.debian.org
+Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
projects / dak.git / commitdiff