Hello, 2013/6/5 Cyril Brulebois <k...@debian.org>: > Martin Michlmayr <t...@cyrius.com> (04/06/2013):
>> I just received several bug reports about this issue and decided to >> investigate. > Many thanks! +1 > Maybe we should also perform a .db check at build time, so that any > new such items would be spotted early? The following shell snippet > seems to do the trick, and could be added to debian/rules, causing > non-zero exit in case there are some hits? > > $ for i in Optional Required; do ok=$(grep -c ^$i-Packages db/all.db); > all=$(grep -i -c ^$i-Packages db/all.db); if [ $ok != $all ]; then echo > "Wrong case for $((all-ok)) $i-Packages fields in db/all.db"; fi; done > Wrong case for 12 Required-Packages fields in db/all.db > > Feel free to add that to master if you like it, and upload the > resulting package to unstable. I can take care of preparing the wheezy > branch and the wheezy pu bug report. Thanks, I think it is not bad idea to add such extra-check. I'll look into adding it to master. Thanks as well for handling wheezy upload. Regards, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caodfweh65s4s00pgltr2__gnw4x_fx64cmoasrs0kfdlsm6...@mail.gmail.com
