Út 25. červen 2013, 16:54:21 CEST Jonas Smedegaard <d...@jones.dk> napsal(a):
> Changes to compiler flags is something that may cause surprises. > That's the reason each and every package need to deal with that, > instead of enforcing flags centrally. I therefore find it a too > risky change for a stable update I got your point. It also clarifies my statement that the fix is unintrusive not being true and that it shouldn't go to p-u. I doubt it should go even to backports.d.o, because if I understand b.d.o., it is designed to contain backported packages that should continuously track newer versions in testing. I am not interested in having newest cdbs (or most of other software). I will ask on the backports list if somebody needs it, and if so, I will backport it and try to track testing, that I think is required by b.d.o. Otherwise I will keep it private and change the version to be lesser than the eventual next updates/proposed-updates upload so I won't miss fixes. Lintian will inform me if I accidentally loose the backported version anyway. Please consider the bug as resolved from my side, maybe it should stay open to track wheezy and be tagged wontfix? Thanks for the discussion and you patience and feel free to make what you want with this bug as you obviously have deeper insight than me. Thanks, Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
