Wouter Verhelst (2013-12-02):
> It will revert to throwaway chroots the minute LVM gets unbroken in
> stable.
What's the bug report for the issue you're mentioning?
In the meanwhile, I think tarball-based chroots are an alternative as
far as sbuild/schroot are concerned.
How are the other power
Hello,
2013/12/2 Cyril Brulebois :
> Wouter Verhelst (2013-12-02):
>> It will revert to throwaway chroots the minute LVM gets unbroken in
>> stable.
> What's the bug report for the issue you're mentioning?
[..]
< zumbi> waldi: are there plans to fix lvm2 snapshot in stable?
(#659762) - I was wo
On 30/11/13 17:56, Jakub Wilk wrote:
> * Niels Thykier , 2013-11-28, 21:04:
>> Starting today, all non-key packages with RC bugs in Jessie for more than 15
>> days will be considered for auto-removal, even if they have reverse
>> dependencies. This also means that the removal of these packages will
>> Wouter Verhelst (2013-12-02):
>>> It will revert to throwaway chroots the minute LVM gets unbroken in
>>> stable.
>FWIW, ARM buildds are quite fine on stable LVM snaphots.
Hrm, ARM is little-endian, right?
LVM snapshots are apparently (according to the buildd
maintainers who run that) unstab
Cyril Brulebois writes ("Re: Release sprint results - team changes, auto-rm and
arch status"):
> Wouter Verhelst (2013-12-02):
> > It will revert to throwaway chroots the minute LVM gets unbroken in
> > stable.
>
> What's the bug report for the issue you're mentioning?
Someone has already menti
On Mon, Dec 2, 2013 at 08:30:45 +0100, Wouter Verhelst wrote:
> Op 28-11-13 21:04, Niels Thykier schreef:
> > It has also come to our attention that a few buildds do not use
> > throw-away chroots. This sometimes results in unclean builds and we
> > have therefore decided to only consider archite
Am 01.12.2013 21:03, schrieb Lucas Nussbaum:
> that fictious goals such as "gcc 4.9 by default in jessie" or "GNOME
> 3.14 in jessie" would totally be in the realm of the release team, but
> are already covered in the delegation.
a) please use real fictious goals.
b) the choice of compiler versi
On Mon, Dec 02, 2013 at 08:22:50AM +0100, Tollef Fog Heen wrote:
> ]] Aurelien Jarno
>
> > Also note that the latest batches of the Loongson-2F CPUs have the bug
> > fixed.
>
> That doesn't help us when the MIPS porters seem to be unable to get us
> any reasonable machine with the bug fixed, eve
Am 02.12.2013 08:03, schrieb Lucas Nussbaum:
> On 01/12/13 at 23:32 +0100, Joerg Jaspert wrote:
>>
I would presumably put something like:
* Release Team members decide on the release goals for stable releases
>>> I think that a delegation would need to be a bit more specific in
>>> defini
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-bioc-altcdfenvs
Version : 2.24.0-1
Upstream Author : Laurent Gautier
* URL :
http://www.bioconductor.org/packages/release/bioc/html/altcdfenvs.html
* License : Artistic-2.0
Programming
On 2013-12-02 08:30, Wouter Verhelst wrote:
Op 28-11-13 21:04, Niels Thykier schreef:
It has also come to our attention that a few buildds do not use
throw-away chroots. This sometimes results in unclean builds and we
have therefore decided to only consider architectures which use
throw-away chr
Package: wnpp
Severity: wishlist
Owner: David Prévot
Control: block 718585 by -1
* Package name: php-jama
Version : 0~2
Upstream Author : Paul Meagher
* URL : http://www.phpmath.com/build02/JAMA/docs/
* License : BSD
Programming Lang: PHP
Description :
Hi.
As Aron says, the Loongson 3A boards may offer us some solution here, for
mipsel anyhow, and maybe that offers us a mid-term solution for mips(be)
whilst I work on other hardware options.
The Loongson 3A CPU patches are 'in flight' over at linux-mips.org I
believe. We will be testing the stab
>> - There are project-wide changes to be done and someone needs to take a
>>decision to do them to adjust some of our common rules to make them
>>easier to do. Lets name them "technical project goals"
>> - There are project-wide changes to be done that should be done in time
>>for
Package: wnpp
Severity: wishlist
Owner: Piotr Roszatycki
* Package name: libplack-app-proxy-perl
Version : 0.29
Upstream Author : Lee Aylward
* URL : https://metacpan.org/release/Plack-App-Proxy
* License : GPL-1+ or Artistic
Programming Lang: Perl
Descrip
Hi all,
am I wrong or among the supporters of the concept of release goals, there are
no members of the release team themselves ? If yes, then it may be more
fruitful to explore alternatives.
The Debian Enhancement Proposals (DEP) have an advantage, as they provide a way
to record whether a give
Package: wnpp
Severity: wishlist
Owner: Scott Howard
* Package name: jssc
Version : 2.6.0
Upstream Author : scream3r@gmail.com
* URL : http://code.google.com/p/java-simple-serial-connector/
* License : LGPL-3+
Programming Lang: Java
Description : Li
Hello,
2013/12/2 Graham Whaley :
> If this works out, my intention is to purchase three 3A motherboards to
> donate for mipsel use (2x buildd, 1x porter I'd expect?). Then *maybe* we
> could move one of the BCM91250 Swarm boards over from mipsel to mips(be)
> whilst I work on some other BE optio
Hi,
On Tue, Dec 03, 2013 at 12:43:36AM +0100, Hector Oron wrote:
> 5.2 Setup arm64 debian-ports
>
>
> ⁃ arm64 setup as new bootstrapping port
> ⁃ manual builds could be uploaded but possible lack of space
> ⁃ 9 more packages needed for a minimal bootstrap
I hav
Hector Oron wrote:
[snip]
> 5.1 Enable buildd support
> ─
>
> ⁃ Fast model system (initial bootstrapping only)
> ⁃ QEMU support (bootstrapping to the point of a buildd image &
> recompile it all again)
> ⁃ Real hardware accessible to Debian (?)
> ⁃ Qt issues m
On Tue, Dec 3, 2013 at 7:43 AM, Hector Oron wrote:
> 12 Flashable image generation
> ═
>
> 12.1 Discussion on supporting pre-installed images
> ──
>
> ⁃ Just fix DI to work on the expected platforms.
> ⁃ Document ways
21 matches
Mail list logo
