On Fri, Jun 22, 2012 at 12:29:48AM -0400, Yaroslav Halchenko wrote:
I was thinking about a bit more automated way... ideally (in the long
run) even that FTBFS (e.g. due to failed tests or some other arch
specific quirks) would forbid automatic migration to wheezy etc --
kinda full blown
Stefano Zacchiroli z...@debian.org writes:
On Fri, Jun 22, 2012 at 12:29:48AM -0400, Yaroslav Halchenko wrote:
I was thinking about a bit more automated way... ideally (in the long
run) even that FTBFS (e.g. due to failed tests or some other arch
specific quirks) would forbid automatic
Hi,
On 22/06/12 at 09:37 +0200, Stefano Zacchiroli wrote:
On Fri, Jun 22, 2012 at 12:29:48AM -0400, Yaroslav Halchenko wrote:
I was thinking about a bit more automated way... ideally (in the long
run) even that FTBFS (e.g. due to failed tests or some other arch
specific quirks) would
On 22/06/12 at 10:56 +0200, Goswin von Brederlow wrote:
Are archive wide rebuilds done on anythiong but i386/amd64?
A long time ago, I played with archive rebuilds inside qemu for mips or
mipsel. It is probably doable, but needs someone to do the work.
Lucas
--
To UNSUBSCRIBE, email to
On Fri, 22 Jun 2012, Goswin von Brederlow wrote:
I was thinking about a bit more automated way... ideally (in the long
run) even that FTBFS (e.g. due to failed tests or some other arch
specific quirks) would forbid automatic migration to wheezy etc --
kinda full blown benefits from the
Yaroslav Halchenko deb...@onerussian.com writes:
On Fri, 22 Jun 2012, Goswin von Brederlow wrote:
archive-wide rebuilds of arch:all packages as we routinely do rebuilds
of arch:any packages.
(Cc:-ing Lucas, for his great work on QA rebuilds.)
Are archive wide rebuilds done on anythiong
On 22/06/12 19:23, Goswin von Brederlow wrote:
Yaroslav Halchenko deb...@onerussian.com writes:
On Fri, 22 Jun 2012, Goswin von Brederlow wrote:
archive-wide rebuilds of arch:all packages as we routinely do rebuilds
of arch:any packages.
(Cc:-ing Lucas, for his great work on QA rebuilds.)
I wonder if we have a way to achieve that.
I package a few Python modules and enable build-time testing in them for
at least some QA. Some of the packages, although being pure Python
(thus architecture all), deal with data I/O thus prone to bugs related
to alignment/endianness etc.
On Thu, Jun 21, 2012 at 01:21:00PM -0400, Yaroslav Halchenko wrote:
I wonder if we have a way to achieve that.
I think this is best handled with autopkgtest. See recent efforts to
set up Debian infrastructure to use it.
--
I wrote a book: http://gtdfh.branchable.com/
signature.asc
On Fri, Jun 22, 2012 at 1:21 AM, Yaroslav Halchenko wrote:
I package a few Python modules and enable build-time testing in them for
at least some QA. Some of the packages, although being pure Python
(thus architecture all), deal with data I/O thus prone to bugs related
to
On Fri, 22 Jun 2012, Paul Wise wrote:
I package a few Python modules and enable build-time testing in them for
at least some QA. Some of the packages, although being pure Python
(thus architecture all), deal with data I/O thus prone to bugs related
to alignment/endianness etc.
11 matches
Mail list logo