Tollef Fog Heen <[EMAIL PROTECTED]> writes:
> * Steve Langasek
>
> | Er. You're going to hold NMUers responsible for the general crappy
> | state of a package before they got to it?
>
> No, but a package might be broken in other subtle ways because of the
> NMU, like broken build-environment. If you upload a package which
> doesn't work (even though the only thing you did was to change a
> translation), then it's your responsibility to fix that breakage.
If you break it you fix it.
But broken build-environment is a bug of the ftp maintainance
scripts. The problems are known and completly avoidable.
Packages entering sid should be checked for uninstallability (caused by
depends on outdated libs) and a rebuild should probabily triggered in
some sane way (i.e. wait for the arch to get uptodate on the failed
lib and then rebuild against that).
Also source-only uploads spring to mind. We know the autobuilders do a
fine job of having a reasonable build-environment. We know uploaders
overall don't (everyone who does don't be angry).
What doesn't get caught is packages being rebuild with a newer
toolschain or newer libs then they where ready for, but then the
source is broken given the current sid even if the old binary was
fine. Better catch that before something gets released by breaking the
package.
MfG
Goswin
