>> >>> until today our Release files included 3 Hashes for all their entries:
>> >>> MD5SUM, SHA1, SHA256. I just modified the code to no longer include
>> >>> MD5SUM in *all* newly generated Release files.
>> >> When will that affect Release files for stable? Next point release?
>> >> Because that unfortunatly completly breaks debmirror..
>> > It did suddenly change for squeeze-updates without consultation with the
>> > suite admins. I expect that this is reverted.
>> Good laugh that is.
> In any case, it would seem logical for squeeze and squeeze-updates to
> use the same set of hashes, imho; similarly the -proposed-updates
> suites. Each of the "sister" suites would generally be expected to be
> consumed (for want of a better word) by the tools in the corresponding
> (old)stable suite.
Sure, and thats a reason I happily follow. Instead of that useless we
had before. :)
Done.
--
bye, Joerg
<aj> vorlon: would it be less subtle if we replaced red, green and
yellow with black, white and a shade of grey?
<vorlon> aj: "and this is what a necrotic port looks like"?
<aj> vorlon: the arch qualification table, halloween edition?
<aj> vorlon: "i heard a faint pinging, and went to the firewall and what
greeted my eyes? AN m68k RISED FROM THE GRAVE!!!"
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877hctt6z6....@gkar.ganneff.de
