This is a good reason to forbid source-only uploads, but there is another,
which actually leverages what we do now, and the idea of not using the
maintainer-provided binary packages in order to have better determinism on
the build:
[...]
Sounds like a great idea, yes.
If ftpmasters don't
[Joey Hess]
File sizes won't 100% stable unfortunatly but the rest should be.
Well, depending on how often I upgrade, vs. how often the buildd does
(and for that matter, how long my package sits in a queue before it is
built), there can be dependency changes due to build-depends shlibs /
On Sun, 13 Feb 2011, brian m. carlson wrote:
On Sun, Feb 13, 2011 at 06:00:11PM +, Lars Wirzenius wrote:
That's something I don't understand. If I upload a broken package, why
should it be the buildd admin's job to deal with it? Should not I get
notified of the error, and told to fix
Henrique de Moraes Holschuh wrote:
1. Instead of discarding upon upload the maintainer-provided binary uploads,
we should first retain some interesting metadata[1] about it, and then
discard.
* Packages that outright FTBFS won't get uploaded
2. Autobuild all binary packages
Henrique de Moraes Holschuh wrote:
This is a good reason to forbid source-only uploads, but there is another,
which actually leverages what we do now, and the idea of not using the
maintainer-provided binary packages in order to have better determinism on
the build:
[...]
Sounds like a great
5 matches
Mail list logo
