teTeX-3.0 for sarge: The official backports collection
No, this is not the announcment of its availability.
Rather, it is a list of things that should be done before we can
announce it:
- enhance the code in the "sarge" target in debian/rules that changes
the changelog:
* It should also add entries to the changelog (from some file in the
debian/sarge/ subdirectory),
* and it should be possible to use a binary-only-NMU version number:
Currently one can compile and use teTeX-3.0 on sarge out of the box,
but one cannot use tetex-bin compiled on sid because of libgcc1,
soon because of the c++ transition.
- Write a web page about it, which should give some information about
how we promise to care about these backports: Quite well (because I am
going to use them on my own machine), but still we might get to the
point were we aren't able to do this, especially with respect to
security support.
- Optionally, prepare a package in which all binaries are replaced by a
script saying "because of problems providing security updates, this
package is no longer functional. Please install a package from the
Debian archive proper".
- Write (or rather, google for) a script that automates as good as
possible the upload to the archive on people.debian.org, including
signed Release files. This is because I assume that sooner or later
people will start using backports of apt and friends with the
signature support built in, and as it is now you have to either
completely disable the signature check mechanism, or not use unsigned
archives at all - there is no by-sources.list-line exclusion of the
necessity to sign packages.
The last point need not be done before we can announce.
Critical remarks and additions, but especially volunteers welcome!
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: