Installed debian-cd 2.1.90-1 (all source)
Installed:
debian-cd_2.1.90-1.tar.gz
to dists/potato/contrib/source/admin/debian-cd_2.1.90-1.tar.gz
debian-cd_2.1.90-1.dsc
to dists/potato/contrib/source/admin/debian-cd_2.1.90-1.dsc
debian-cd_2.1.90-1_all.deb
to dists/potato/contrib/binary-all/admin/debian-cd_2.1.90-1.deb
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Thu, 29 Jul 1999 18:26:09 +0200
Source: debian-cd
Binary: debian-cd
Architecture: source all
Version: 2.1.90-1
Distribution: unstable
Urgency: low
Maintainer: Raphael Hertzog <hertzog@debian.org>
Description:
debian-cd - Tools for building (Official) Debian CD set
Closes: 17540 24418 24708 25195 25210 25710 27758 31044 36109 36110 36111 36112 36113 36114 36115 36116 36228 38402
Changes:
debian-cd (2.1.90-1) unstable; urgency=low
.
* Moved to contrib because of the unzip and lha dependencies.
* Corrected the boot-m68k script (bvme600 -> bvme6000).
* YACS 0.5 :
* ----------
* tools/add_dirs: don't create section subdirectories for non-US.
* tools/*: full slink compliance. Should build slink disk even with
non-US. Thanks to the help of Filip Van Raemdonck <mechanix@dma.be>.
* Makefile: added an upgrade target called when building
official_images. It will call tools/$CODENAME/upgrade.sh if possible.
Created this upgrade.sh file for slink.
* YACS can/should generate complete slink images with this release.
Please test. In particular for non-i386 CD images. I want to check
if the scripts to make CD bootables are (still) working.
* tools/apt-selection: removed some bashisms.
* Many data has been splitted by codename. This is to allow
us to build slink and potato CD without much troubles.
* Updated the master file for potato. Added the old one for slink.
* Status file is now automatically generated when a provided one
is not available (data/$CODENAME/status.$ARCH).
* build.sh build_all.sh: convenience scripts to build CD images.
* YACS 0.4 :
* ----------
* New status file for potato i386.
* When including packages listed in the status file check that they
exist before.
* Call dpkg-scansources for generating Sources.gz file on the source
CD. And depends on dpkg-dev (>= 1.4.1.6) to be sure that we have it.
* Add dependency to libdigest-md5-perl.
* list2cds: try to select all suggested/recommended packages not only from
packages explicitely selectionned but also from packages listed
in dependencies.
* list2cds: many little checks added, now generates a log.list2cds
file (in the temp dir).
* YACS 0.3 :
* ----------
* This version has herited nothing from the previous debian-cd
package only the changelog has been added.
* It can now build sources CD.
* This package does now replace slink_cd and the old debian-cd.
I'll close the bugs (after checking that the new debian-cd behaves
correctly with the bug report situation) affected to those packages.
* The Packages.cd files are generated correctly (the same way than
slink_cd did).
* Added the good dependencies. Closes: #25710, #36109, #27758
* Some bugs are no more applicable. Closes: #24708, #25195, #31044, #24418
Closes: #36115, #36228
* No source URL in copyright file since this is a Debian native
package. Closes: #36111
* Full GPL isn't included. Closes: #36113
* Missing newlines added. Closes: #36114
* The README is a good documentation for building CD. Closes: #17540
* Added the support for hooks. Closes: #36112
* Added a link index.html -> install.html. Closes: #38402
* Files are better placed. Closes: #36110
* Rebuilding the Contents file is of no use. And if you really need
it, you can do it yourself with the hook system. Closes: #36116
* Internationalization is a boot-floppies problem. Closes: #25210
* Tried miniunz but it lacks important feature like -L ... still
uses unzip. And recommends it.
Files:
ce2e7c8b9b9d9a1ebf0fc1ae8661a1a3 608 contrib/admin extra debian-cd_2.1.90-1.dsc
9854263f5d7c2ea000c6990f58d05bb9 290160 contrib/admin extra debian-cd_2.1.90-1.tar.gz
250f8ad7c213cea78cbc121673676424 308576 contrib/admin extra debian-cd_2.1.90-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iQCVAwUBOAhW7trM2c0MTKvxAQFmjAQAmpF8/4g7oqxZnPe860hSgngpR/D37qgU
pe1pdLSxSZ68du+joU+cHGxOTx+Lm04lHHLOT7XX9G1mZHYI0ishKOau5dT06ZLL
gGw16tkCv4vB6Q8CdABJF0mUB2l6AsFjgAysVsoyenkdYhrcNpVetlWMdu9B1MLE
m8biqDDuXDo=
=Oq/f
-----END PGP SIGNATURE-----
Reply to: