On Tue, 2012-01-03 at 22:54 +, Adam D. Barratt wrote:
I had been planning on having a look at the situation for both armhf and
s390x over the period between Christmas and New Year, but for a variety
of reasons that never happened. It's still on my short-term to-do list;
it's not quite
On Sun, 2012-01-08 at 05:04 +, peter green wrote:
An initial push of packages to testing occurred with tonight's britney
run. There's a certain amount of uninstallability and loads of missing
packages still, but it's a start :)
I guess the next step is to try and get it to the
[dropped the non-existent debian-ftp@lists.d.o from CC]
On Fri, 2012-03-23 at 21:56 +, peter green wrote:
Afaict one of the key steps in getting an architecture to release status
is to deal with (prefferablly by fixing but I guess removing could also
be an option in some cases) any out
On Fri, 2012-03-23 at 22:46 +, peter green wrote:
Adam D. Barratt wrote:
On Fri, 2012-03-23 at 21:56 +, peter green wrote:
Afaict one of the key steps in getting an architecture to release status
is to deal with (prefferablly by fixing but I guess removing could also
Hi,
With the sound of the ever approaching freeze ringing loudly in our ears,
we're (somewhat belatedly) looking at finalising the list of release
architectures for the Wheezy release.
Comments on / additions and corrections to the content of
http://release.debian.org/wheezy/arch_qualify.html
Hi,
With the sound of the ever approaching freeze ringing loudly in our ears,
we're (somewhat belatedly) looking at finalising the list of release
architectures for the Wheezy release.
Comments on / additions and corrections to the content of
http://release.debian.org/wheezy/arch_qualify.html
On Thu, 2012-05-17 at 00:59 +0100, peter green wrote:
The statement that all but one armel buildd is at the same location disagrees
with
the debian machines database.
[...]
Metropolitan Area Network Darmstadt : arcadelt
DG-i: argento
They may still be physically located there, but:
Hi,
I've just committed a change to britney's configuration, removing all
special-casing of the armhf and s390x architectures. Both now have
release architecture status for wheezy.
So, what does this mean in practice?
- architecture-specific bugs affecting armhf or s390x may be
On Thu, 2012-07-19 at 20:09 +0100, Luke Kenneth Casson Leighton wrote:
On Thu, Jul 19, 2012 at 6:35 PM, Steve McIntyre st...@einval.com wrote:
Both armel and armhf are doing well, covering ~96% of the archive. We
[...]
(*1) and if someone _really_ wants a debug build of that particular
[non-debian lists dropped]
On Wed, 2013-06-05 at 20:46 +0100, Luke Kenneth Casson Leighton wrote:
what's the point of mentioning this?
well, the point is: the expectation of the linux kernel developers is
that Everyone Must Convert To DeviceTree.
[...]
thoughts and discussion appreciated.
tag 573712 + patch
thanks
On Tue, March 16, 2010 23:44, Martin Guy wrote:
On 3/16/10, Adam D. Barratt a...@adam-barratt.org.uk wrote:
gem fails to build on armel with assembler errors. From the build
log:
g++ -c-I/usr/include/lqt -fopenmp -I/usr/include/ImageMagick
-I/usr/include
Package: source-highlight
Version: 3.1.1-1
Severity: serious
X-Debbugs-Cc: debian-arm@lists.debian.org
Hi,
The past few uploads of source-highlight FTBFS on armel due to one of the
tests causing a segfault. I'm not sure whether this is an issue with the
package or the buildds, so have Cced the
On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote:
I'll make gcc-4.5 the default for (at least some) architectures within the
next
two weeks before more transitions start. GCC-4.5 is already used as the
default
compiler for almost any other distribution, so there shouldn't be many
On 2015-10-23 13:28, Thorsten Glaser wrote:
[...]
On Fri, 23 Oct 2015, Adam D. Barratt wrote:
[...]
It's also not quite that simple, even working things out by hand - see
#599128
for example.
Hm, I’m still under the impression that the +bN suffix to the Debian
version of the package
On 2015-10-23 12:02, Thorsten Glaser wrote:
On Fri, 23 Oct 2015, Adam D. Barratt wrote:
wanna-build does, yes, but at least the Release Team tend to use the
"wb"
wrapper tool which automatically works out the next free number on
each
architecture.
Ah, cool – so we have onl
On Fri, 2016-09-30 at 19:04 +, Niels Thykier wrote:
> As for "porter qualification"
> =
>
> We got burned during the Jessie release, where a person answered the
> roll call for sparc and we kept sparc as a release architecture for
> Jessie. However, we ended up
On Fri, 2018-06-29 at 10:20 +0100, Luke Kenneth Casson Leighton wrote:
[...]
> debian-riscv has been repeatedly asking for a single zero-impact
> line
> to be included in *one* file in *one* dpkg-related package which
> would
> allow riscv to stop being a NMU architecture and become part of
>
On Fri, 2018-06-29 at 11:44 +0100, Luke Kenneth Casson Leighton wrote:
[...]
> On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt
> wrote:
>
> > > what is the reason why that package is not moving forward?
> >
> > I assume you're referring to the dpkg upload t
On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
> > > * Rebuild the debian-installer images, pulling in updates from
> > > stretch-updates, leaving only armhf netboot targets broken.
> >
> > Expanding a bit: rebuilding
19 matches
Mail list logo
