The packages libisal, python-isal and fastp are no longer built on 32
bit. The packages were removed from the 32 release architectures:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098965
RM: libisal [armel armhf] -- ANAIS: 32 bit architectures dropped
https://bugs.debian.org/cgi-bin/bugrep
mån 2022-05-23 klockan 09:56 +0200 skrev John Paul Adrian Glaubitz:
> Hi Matthias!
>
> > On May 23, 2022, at 9:43 AM, Mattias Ellert
> > wrote:
> >
> > mån 2022-05-16 klockan 10:28 +0200 skrev John Paul Adrian
> > Glaubitz:
> > > Hi Matthias!
&g
mån 2022-05-16 klockan 10:28 +0200 skrev John Paul Adrian Glaubitz:
> Hi Matthias!
>
> On 5/16/22 10:24, Mattias Ellert wrote:
> > I have noticed that in addition to m68k and sh4, the builds also
> > fail
> > in the same way on the hppa host known as pasta, but when gi
Hi!
Now the openssl3 transition is underway, and many more of the globus
packages fail in the same way.
My original idea that it was failing due to doxygen using an input
filter, seems to be incorrect. Only 4 of the globus packages uses an
input filter, an many more of them are failing than those
Hi!
The globus-net-manager package failed to build from source on m64k and
sh4 during the python 3.10 transition. I tried giving the package back,
but the second attempt failed in the same way.
I did build the package successfully on the m68k porterbox
mitchy.debian.net, so I can not reproduce th
gsoap 2.8.60-2 failed to build on m68k:
https://buildd.debian.org/status/package.php?p=gsoap&suite=sid
According to the log it looks like the build got stuck during
documentation generation running doxygen. And then was killed due to
inactivity.
Is there some issue with doxygen on m68k that woul
mån 2016-07-25 klockan 20:50 +0200 skrev John Paul Adrian Glaubitz:
> On 07/23/2016 04:28 PM, Mattias Ellert wrote:
> >
> > >
> > > >
> > > > The qemu-m68k is approx 6 times faster than the aranym, but
> > > > three
> > >
lör 2016-07-23 klockan 10:34 +0200 skrev John Paul Adrian Glaubitz:
> On 07/23/2016 01:51 AM, Mattias Ellert wrote:
> >
> > The qemu-m68k is approx 6 times faster than the aranym, but three
> > of
> > the tests still take almost 1 hour to complete, which is more than
fre 2016-07-22 klockan 11:09 +0200 skrev John Paul Adrian Glaubitz:
> Hello Mattias!
>
> On 07/22/2016 10:56 AM, Mattias Ellert wrote:
> >
> > https://buildd.debian.org/status/logs.php?pkg=globus-ftp-client&arc
> > h=m68k
> >
> > There is nothing bro
Hi!
The m68k builds of the globus-ftp-client are failing:
https://buildd.debian.org/status/logs.php?pkg=globus-ftp-client&arch=m68k
There is nothing broken with the builds, except that they are a bit
slow.
The logs say "Build killed with signal TERM after 30 minutes of
inactivity" during the 4t
The build of globus-ftp-client on m68k failed due to a timeout:
"Build killed with signal TERM after 30 minutes of inactivity"
The 30 minute timeout is way to aggressive for this package. The
package builds OK for me in the aranym emulator, though the tests take
a long time to run. The whole buil
The build of globus-gram-protocol on m68k failed due to "qemu: fatal:
Illegal instruction" when doxygen is invoked. I can not reproduce this
failure in aranym. I would therefore like to request a give-back so
that the build can be tried again.
Mattias
signature.asc
Description: This is a
Hi!
The m68k builds for globus-io and globus-gss-assist have failed some
month ago, and no new attempt have been made. The builds work for me in
the aranym emulator, so if there is a problem with the packaging I
don't know how to debug it. Could the builds be tried again on the
buildds? If there w
13 matches
Mail list logo
