On Mon, 01 Dec 2003, christophe barbe wrote:
> Before mass bug-filling, it would be necessary to make it mandatory
> which unfortunately is not the case right now afaik.
Deployment plan for md5sums everywhere:
1. List packages that do not have a md5sum included.
For every package in the list:
2. Download the thing, an add a dh_md5sum OR whatever is more in tune with
the package build system (lots of packages do not use dh_*)
2a. TEST IT. REALLY.
2b. Use interdiff or something like that to make sure the only change
you made was the md5sum thing, and no errors crept in the diff.
3. Send patch to BTS
4. Wait 1 month
After that one month:
For every package that the maintainer did not fix the md5sum thing himself:
1. Upload NMU to biggest delay possible, send email to maintainer,
and NMU patch to BTS
After the dust settles:
Propose policy changes. Since well over 90% of the packages should have
md5sums now, it will probably be accepted.
I am *MOST DEFINATELY NOT* going to do anything like the above. I am just
pointing out what people who _do_ care enough should do to get things fixed.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
