Thank you so much Cyril!
> That being said, we don't have all modules shipped in the installer, and
> some other module might be available and used in the installed system
> (e.g. dedicated driver as opposed to fbdev during a graphical install on
> amd64), which can explain differences. The
Hi Cyril!
> Could you please guide me into reproducing this issue in QEMU? #987368
> had hints, but at least the openpower.xyz part no longer works (it's no
> longer resolving).
much simpler actually because in the current case, we won't emulate a
full baremetal PowerNV machine.
For example,
Thanks Cyril.
Another important detail ... I only get that behavior in qemu in
graphical mode.
On LPARs there is no issue. I didn't try on baremetal so far.
F.
On Tue, 21 Mar 2023 17:44:49 +0100 Cyril Brulebois wrote:
> Frédéric Bonnard (2023-03-17):
> > > It would be helpful to c
Ok found it...
> (nothing attached)
oops! .. not that much to display though (I also tried to remove the
"quiet" boot option, but it didn't change anything, it does not display
anything before getting in debian's init)
> > same happens with
> >
Package: installation-reports
Boot method: CD
Image version: http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso
Hi!
since debian-installer (20230217) uses kernel 6.1.0-5 in mini.iso, the kernel
hangs
before I have the installer menu (see attached .png) ; same happens with
Package: src:deal.ii
Version: 9.4.0-1
Control: tags -1 ftbfs
Control: tags -1 patch
--
Dear maintainer,
deal.ii fails to build atm on ppc64el on unstable. It actually fails at
link time.
Full log is here :
https://buildd.debian.org/status/fetch.php?pkg=deal.ii=ppc64el=9.4.0-1%2Bb1=1666717020=0
Package: src:powerpc-utils
Version: 1.3.9-1
Control: tags -1 ftbfs
Control: forwarded -1
https://github.com/ibm-power-utilities/powerpc-utils/issues/85
--
Dear maintainer,
powerpc-utils 1.3.9-1 fails to build atm with gcc-12.
I checked latest 1.3.10 and it's roughly the same.
I've opened an
Package: src:python-schema
Version: 0.6.7-4
--
Dear maintainer,
upstream python-schema introduced support for 'Literal' which the
package "organize" uses in its latest version and I'd like to update
"organize".
Would mind considering upgrading python-schema ?
Thanks a lot,
Regards,
F.
> FWIW, if you want to test - there is an MR open for updating Debian's
> rustc to 1.60 ;)
Awesome Fabian, that worked .. at least, on a current unstable schroot,
with squeekboard 1.18.0 (which failed just before in the very same schroot),
but with upgraded rustc .debs 1.60.0+dfsg1-1~exp1 .
Hi Sylvestre,
at first, I thought it may be a squeekboard coding issue too, but the fact that
the
same code breaks with rustc 1.59 and not 1.58 made me think of a
regression (be it squeekboard 1.17.1 or 1.18.0). Also, only rust
components where changed for this test : exact same gcc etc ..
If
Package: src:rustc
Version: 1.59.0+dfsg1-1
--
Dear maintainer,
squeekboard 1.18.0-1 package does not build on ppc64el, due to unknown symbols
at
link time :
https://buildd.debian.org/status/fetch.php?pkg=squeekboard=ppc64el=1.18.0-1=1654176130=0
---
error: linking with `cc` failed: exit
rent story, as it is enabled by default on ppc64el but not
+ on ppc64. So leaving it for now.
+Author: Frédéric Bonnard
+Forwarded: no
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -203,17 +203,6 @@
+
+ include(CheckCCo
Control: reassign -1 rocksdb
Hi,
this is actually an issue in latest rocksdb 7.2.2-3 that got compiled
with -mcpu=power9 -mtune=power9 which is not good in Debian, because
we want to be power8 compatible (Debian's gcc defaults).
(which is not the case in Ubuntu which optimize for Power9 and thus
Hi Paul,
sorry for the late reply.
As I said on debian-devel, I've not enough expertise nor hope on that
topic.
Switching to lua is the way I went a few times, instead on relying on
luajit.
F.
On Mon, 02 May 2022 07:55:50 +0200 Paul Gevers wrote:
> Hi,
>
> On 24-04-2022 12:00, Paul Gevers
Hi,
as I said, with gcc-9, mlton-20210117+dfsg-3 builds fine. Underlying
mlton to rebuilt it (Build-Depends-Arch) is mlton-20130715-3 .
Then, what I see, is that with
mlton-20210117+dfsg-3_built_with_gcc-9+mlton-20130715-3
installed as new Build-Depends-Arch instead of mlton-20130715-3,
Package: src:mlton
Version: 20210117+dfsg-3
Control: tags -1 ftbfs
--
Dear maintainer,
mlton fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=mlton=ppc64el=20210117%2Bdfsg-3=1642700806=0
I've not been able to dig much into that. What I noticed is that is does
build
Package: src:eigen3
Version: 3.4.0-2
Control: tags -1 + patch
--
Dear maintainer,
freecad fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=freecad=ppc64el=0.19.4%2Bdfsg1-1=1646410969=0
This bug is due to gcc failing in eigen3. Some related links :
Control: tags -1 + patch
Upstream 0.9.3 has patches.
F.
signature.asc
Description: PGP signature
Control: forwarded -1 https://github.com/stefanberger/libtpms/issues/298
With 0.10.0~dev1 it doesn't build too.
F.
signature.asc
Description: PGP signature
Hi,
debian/rules just need to fix the path for fpc unit files :
---
ifeq ($(DEB_HOST_GNU_CPU),powerpc64le)
DEB_HOST_GNU_CPU := powerpc64
endif
---
F.
signature.asc
Description: PGP signature
Package: src:vmg
Version: 3.7.1-5
Control: tags -1 ftbfs
--
Dear maintainer,
vmg fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=vmg=ppc64el=3.7.1-5=1604198887=0
Regards,
F.
signature.asc
Description: PGP signature
Package: src:fakeroot
Version: 1.26-1
Control: tags -1 ftbfs
--
Dear maintainer,
fakeroot fails to build on ppc64el since 1.26-1
https://buildd.debian.org/status/fetch.php?pkg=fakeroot=ppc64el=1.26-1=1630982822=0
Backtrace from the core file :
---
Core was generated by `chown -R daemon:sys 2 '.
Hi Steve,
awesome, couldn't wait to test it, so I built udpkg 1.20 from salsa and
integrated in latest debian-installer built to have a mini.iso to play
with.
I tried that iso 5-6 times on each of the 2 physical Power machines on
which I encountered the bug and it worked every single time.
From
Package: wnpp
Owner: Frédéric Bonnard
Severity: wishlist
* Package name: simplematch
Version : 1.3
Upstream Author : Thomas Feldmann
* URL : https://github.com/tfeldmann/simplematch
* License : Expat
Programming Lang: Python
Description : Minimal
Package: wnpp
Owner: Frédéric Bonnard
Severity: wishlist
* Package name: organize
Version : 1.10.1
Upstream Author : Thomas Feldmann
* URL : https://github.com/tfeldmann/organize
* License : Expat
Programming Lang: Python
Description : File management
Hi Cyril/all,
sorry that the process takes long, but that was the only way to
reproduce that bug (which I think may not be specific to ppc64el)
without having Power hardware (and a LPAR/HMC setup).
> Looking at that log, one sees two PIDs for main-menu (272 and 278),
> which could explain a very
On Fri, 28 May 2021 14:39:56 +0200, Cyril Brulebois wrote:
> Hi Frédéric,
>
> Frédéric Bonnard (2021-05-25):
> > Get that one too :
> > https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/skiboot.
ssue. Last components build may require a newer
skiboot.lid than the one coming in qemu package).
F.
On Mon, 24 May 2021 04:48:00 +0200, Cyril Brulebois wrote:
> Hi Frédéric,
>
> Frédéric Bonnard (2021-04-26):
> > Thanks for willing to investigate !
>
> Thanks for the de
Hi there,
I tried to bisect between 4.17.0 and 4.18.0 (4.19.0
didn't work either) and found the first offending commit
64ceb09e3297259b58a78b5d6486b1724070a4c9 that makes tracecompass fail
and playing with -DNO_gtk_1check_1button_1set_1inconsistent makes it
work. Soon after
whitespaces
+
+ [ Frédéric Bonnard ]
+ * Import upstream fix for make 4.3 use (Closes: #987636)
+
+ -- Frédéric Bonnard Tue, 27 Apr 2021 13:25:03 +0200
+
libcxl (1.7-1) unstable; urgency=medium
* Remove unused d/patches effectively
diff -Nru
libcxl-1.7/debian/patches/0001-Import-upstream-fix
-e (you'll get an error.. but this
steps seems necessary)
2. kexec -s vmlinux -i initrd.gz -e
- cross fingers ; if it doesn't fail, halt and rerun qemu...
I hope you get it as well!
F.
On Fri, 23 Apr 2021 22:48:33 +0200, Cyril Brulebois wrote:
> Hello Frédéric,
>
> Frédéric B
Package: installation-reports
Boot method: CD
Image version: http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso
Date: April 21st 2021
Machine: Power10 machine but got it on Power8 as well
This happens randomly when the installer menu starts, I get to the first
menu "Choose
and disable unported
+tests (Closes: #980628)
+
+ -- Frédéric Bonnard Wed, 07 Apr 2021 12:28:16 +0200
+
libsass-python (0.20.1-2) unstable; urgency=medium
* Avoid code download during doc build (Closes: #972140)
diff -Nru libsass-python-0.20.1/debian/rules libsass-python-0.20.1/debian/rules
-autoinst-4.6.1604525166.912dfbd/debian/changelog 2021-04-01
12:50:51.0 +0200
@@ -1,3 +1,10 @@
+os-autoinst (4.6.1604525166.912dfbd-0.3) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Stick to tests that upstream runs (Closes: #977990)
+
+ -- Frédéric Bonnard Thu, 01 Apr 2021 12:50
Hi,
sorry for the delay.
Initially I wanted to include all tests in the packaging as they just
didn't fail for me on ppc64el, amd64 and i386.
Having a look at the .spec file upstream, they skip some of the tests,
amongst them, the one we have an issue with.
---
# don't require qemu within OBS
#
s to be as per your patch, I am quite
> happy to apply that.
>
> Do you want me to run up a new release or would you prefer to use the
> patch on a Debian downstream release model ?
>
> Davo
>
> On 27/3/21 3:00 am, Frédéric Bonnard wrote:
>
>> Here is a patch proposal which fixes the build.
>> The patch header details the issue and the possible workaround.
>> Regards,
>>
>> F.
signature.asc
Description: PGP signature
Here is a patch proposal which fixes the build.
The patch header details the issue and the possible workaround.
Regards,
F.
--- a/buildit.bash
+++ b/buildit.bash
@@ -156,6 +156,9 @@
CPU="i386"
fi
TARGET="$CPU-$OS"
+if [ "$CPU" = "powerpc64le" ]; then
+CPU="powerpc64"
+fi
CheckFPC
Package: src:tomboy-ng
Version: 0.32-1
Control: tags -1 ftbfs
--
Dear maintainer,
tomboy fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=tomboy-ng=ppc64el=0.32-1=1612358331=0
Regards,
F.
signature.asc
Description: PGP signature
Control: severity -1 important
--
As explained upstream, the behaviour of the tests changed after
libsass's commit "fix how we count unicode characters" that
libsass_3.6.4+20201122-1 pulled.
But upstream's libsass-python doesn't not support non-release of
libsass and they wouldn't help on our
Hi,
indeed Paul, the test is flaky, probably a timing issue. I had already
changed some related parameter that made the tests pass reliably on
my i386 builder, but saw afterward that it still failed on debian's
builder and couldn't reproduce it :
Control: forwarded -1 https://github.com/sass/libsass-python/issues/331
--
Hi,
as build log shows, the very same version of libsass-python built
successfully some time ago (using libsass_3.6.4-4) :
https://buildd.debian.org/status/logs.php?pkg=libsass-python=amd64=sid
but with latest build dep
At the moment, buildd logs show that everything works fine on firefox
83.0-1 / rustc 1.47.0+dfsg1-1
https://buildd.debian.org/status/logs.php?pkg=firefox=83.0-1
I tried myself and it built fine too with current 1.48.0+dfsg1-1 rustc.
Regards,
F.
signature.asc
Description: PGP signature
Here is a patch based on this :
https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html
Tested on a power machine (where the build failed) and it seems to work.
F.
Description: Fix parallel build
This happened here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906
Package: wnpp
Owner: Frédéric Bonnard
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org
* Package name: libmojolicious-plugin-oauth2-perl
Version : 1.58
Upstream Author : Jan Henning Thorsen
* URL : https://metacpan.org
Package: wnpp
Owner: Frédéric Bonnard
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org
* Package name: libnet-dns-native-perl
Version : 0.22
Upstream Author : Oleg G
* URL : https://metacpan.org/release/Net-DNS-Native
Package: wnpp
Owner: Frédéric Bonnard
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org
* Package name: libcommonmark-perl
Version : 0.29
Upstream Author : Nick Wellnhofer
* URL : https://metacpan.org/release/CommonMark
On Wed, 23 Sep 2020 17:45:45 +0200, Frédéric Bonnard wrote:
> oh right, I didn't realize not all binary packages are built on "any". 2
> needs to be enabled (lcl-qt5-2.0 and lazarus-ide-qt5-2.0). And I tested
> and they build well on ppc64el.
> I'll also tested on
On Wed, 23 Sep 2020 15:01:55 +0200, Graham Inggs wrote:
> Hi Frédéric
>
> On Wed, 23 Sep 2020 at 10:47, Frédéric Bonnard wrote:
> > Debug info type's recommended setting seems to be dwarf anyway (32/64b).
> > So I've replaced -gs with -gw in components/chmhelp/lhelp/Makefi
in components/chmhelp/lhelp/Makefile.fpc.
It builds on amd64, i386 and ppc64el at least.
I'll send another merge request.
Thanks for letting me know!
F.
On Mon, 21 Sep 2020 11:10:30 +0200, Graham Inggs wrote:
> Hi Frédéric
>
> On Thu, 10 Sep 2020 at 11:27, Frédéric Bonnard wrote:
> >
Control: tags -1 patch
--
I'm no Free Pascal expert but having a look at the build on fedora which
work, I saw that they pass -gw to the build command that fails here in
Debian and that works on Fedora.
Which I tried and make it work :
/usr/bin/ppcppc64 -gs -gl -Sghi -O3 -dlclqt5 -Fu.
Package: src:lazarus
Version: 2.0.10+dfsg-2
Control: tags -1 ftbfs
--
Dear maintainer,
lazarus fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=lazarus=ppc64el=2.0.10%2Bdfsg-2=1597568160=0
Regards,
F.
signature.asc
Description: PGP signature
Package: src:arbtt
Version: 0.10.2-0.1
Control: tags -1 ftbfs
--
Dear maintainer,
arbtt fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=arbtt=ppc64el=0.10.2-0.1=1592498657=0
but trying on amd64, it failed the same way, the buildd log on amd64
being much older than the
Hi,
I wanted to check that FTBFS but it actually built, on different setup.
After a give back on ppc64el and s390x, everything went fine. Very few
changes between the failing and succeeding build. Same ghc, kernel.
For the record, linux-libc-dev, libgmpxx4ldbl, libgmp-dev, libkrb5support0,
Control: tags -1 patch
--
Dear maintainer,
upstream has a commit for that : which I imported and improved as well.
Here is a merge request for ardour packaging :
https://salsa.debian.org/multimedia-team/ardour/-/merge_requests/2
Regards,
F.
signature.asc
Description: PGP signature
Package: src:ardour
Version: 1:6.0.0~ds0-1
Control: tags -1 ftbfs
--
Dear maintainer,
ardour fails to build on ppc64el since 1:6.0.0~ds0-1 as shown here :
https://buildd.debian.org/status/logs.php?pkg=ardour
Regards,
F.
signature.asc
Description: PGP signature
Package: src:simde
Version:0.0.0.git.20200522-1
--
Dear maintainer,
since last version of simde, I noticed that bowtie2 fails on
ppc64el while it was not on a very similar version before but using
0.0.0.git.20200424-1 (I confirmed that by trying to rebuild bowtie2
2.4.1-4 which now
Package: src:tnftp
Version: 20151004-1
Control: tags -1 ftbfs patch
--
Dear maintainer,
tnftp fails to build on ppc64el ( probably the same issue on arm64,
riscv64 ) due to an outdated config.guess.
Here is a minimal patch that does the work.
Regards,
F.
diff -Nru tnftp-20151004/debian/rules
Hi Boyuan,
thanks for the NMU, no problem with the delay. There's a new upstream release,
but I won't package it right away. So all good!
F.
May 17, 2020 5:48 PM, "Boyuan Yang" wrote:
> Control: tags 960354 + patch
> Control: tags 960354 + pending
>
> Dear maintainer,
>
> I've prepared an
Sorry for the wrong link.
Merge request : https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4948
signature.asc
Description: PGP signature
, Frédéric Bonnard wrote:
> > > Here is a merge request for review :
> > > https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/13
> >
> > this is merged now, and I commented that I hope you could send it upstream..
>
> Thanks Timo!
> I sent a merge r
Control: tags -1 patch
--
Dear maintainer,
this issue is most probably due to char sign-ness .
The list of architectures needing char to be forced as signed because
by default they are unsigned (
https://wiki.debian.org/ArchitectureSpecificsMemo ) needs to be
extended.
See the attached debdiff.
> > Here is a merge request for review :
> > https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/13
>
> this is merged now, and I commented that I hope you could send it upstream..
Thanks Timo!
I sent a merge request to mesa a few hours ago. But one of the file I
patched is actually
Control: tags -1 patch
--
Here is a merge request for review :
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/13
Regards,
F.
pgphsIBUavl8n.pgp
Description: PGP signature
Control: tags -1 patch
--
Here is a merge request for review :
https://salsa.debian.org/med-team/spoa/-/merge_requests/1
Regards,
F.
pgpWvO7pZsIro.pgp
Description: PGP signature
Package: src:mesa
Version: 20.0.6-1
Control: tags -1 ftbfs
--
Dear maintainer,
mesa fails to build on ppc64el since 20.0.4-2 as shown here :
https://buildd.debian.org/status/fetch.php?pkg=mesa=ppc64el=20.0.6-1=1588668604=0
I've prepared a patch for review.
Regards,
F.
pgppFuVlSjAk3.pgp
Package: src:spoa
Version: 3.0.2-4
Control: tags -1 ftbfs
--
Dear maintainer,
spoa fails to build on ppc64el as shown here :
https://buildd.debian.org/status/fetch.php?pkg=spoa=ppc64el=3.0.2-4=1588509193=0
It looks like the recurrent issue being the collision between altivec
and std c++ types.
Package: src:last-align
Version: 1060-3
Control: tags -1 ftbfs
--
Dear maintainer,
last-align fails to build on ppc64el as shown here :
https://buildd.debian.org/status/fetch.php?pkg=last-align=ppc64el=1060-3=1587335358=0
It looks like the recurrent issue being the collision between altivec
and
Package: src:q2-cutadapt
Version: 2019.10.0-1
Control: tags -1 ftbfs
--
Dear maintainer,
trying to reproduce the ppc64el specific failure :
https://buildd.debian.org/status/fetch.php?pkg=q2-cutadapt=ppc64el=2019.10.0-1=1582306016=0
I actually found out that q2-cutadapt fails to build on
Hi Anthony
March 9, 2020 8:30 AM, "Anthony Fok" wrote:
> Control: severity -1 serious
> Control: tags -1 + ftbfs sid
> Control: found -1 0.18.0-1
>
> On Fri, 28 Feb 2020 17:38:13 +0100 Michael Fladischer
> wrote:
>
>> Source: libsass-python
>> Severity: wishlist
>>
>> -BEGIN PGP SIGNED
On Wed, 05 Feb 2020 14:35:53 -0600, Steve Robbins wrote:
> Thanks! Do you know why only ppc64el fails?
Hi Steve,
VSX is a POWER technology and opencv package enables VSX only on ppc64el :
https://sources.debian.org/src/opencv/4.2.0+dfsg-4/debian/rules/#L23
because of :
Package: src:digikam
Version: 4:6.4.0+dfsg-1
Control: tags -1 ftbfs patch
--
Dear maintainer,
latest 4:6.4.0+dfsg-1 fails to build on ppc64el here :
https://buildd.debian.org/status/fetch.php?pkg=digikam=ppc64el=4%3A6.4.0%2Bdfsg-1=1580716901=0
Opencv undefines vector, bool and pixel on purpose
Package: src:wp2latex
Version: 3.86-1
Control: tags -1 ftbfs patch
--
Dear maintainer,
latest 3.86-1 fails to build on multiple architectures with the
following error :
---
In file included from wp2latex.cc:29:
wp2latex.h:20:25: error: expected unqualified-id before string constant
20 |
Package: src:bpfcc
Version: 0.12.0-1
Control: tags -1 ftbfs patch
--
Dear maintainer,
latest 0.12.0-1 fails to build here :
https://buildd.debian.org/status/fetch.php?pkg=bpfcc=ppc64el=0.12.0-1=1580365148=0
upstream recently fixed the test :
Dear maintainer,
I submitted a merge request to fix that FTBFS :
https://salsa.debian.org/debian/os-autoinst/merge_requests/1
Can you have a look at it ?
Regards,
F.
pgpmaUxJMrahX.pgp
Description: PGP signature
The issue at the moment is probably in golang-github-remyoudompheng-bigfft :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948794.
F.
pgpc90UqaZLFQ.pgp
Description: PGP signature
Package: src:golang-github-remyoudompheng-bigfft
Version: 0.0~git20170806.52369c6-1
--
Dear maintainer,
rkt is failing to build on arm, mips and ppc64el because
golang-github-remyoudompheng-bigfft has missing support on those
architectures ( https://github.com/remyoudompheng/bigfft/issues/5 )
I
Package: wnpp
Severity: wishlist
Comskip is a commercial detector. It is a console application that reads a
mpeg or h.264 file and analyses the content based on a large amount of
configurable parameters. A gui is also provided.
After analysis it generates a file in various possible formats
Package: src:qd
Version: 2.3.22+dfsg.1-3
Control: tags -1 patch ftbfs
--
Hi,
after contacting the ppc64 toolchain team about bug #935289, especially
Pat Haugen, he said :
---
Basically the testcase is sensitive to
precision differences when FMA instructions are used (floating point
Package: src:openafs
Version: 1.8.5-1
--
Dear maintainer,
thanks for enabling ppc64el. It seems some more changes are needed for
openafs to build properly :
https://buildd.debian.org/status/fetch.php?pkg=openafs=ppc64el=1.8.5-1=1572239330=0
Here is a merge request that does the job here :
Package: src:vsearch
Version: 2.14.1-1
--
Dear maintainer,
vsearch compiles out of the box on ppc64el. Could it be possible that
you enable this architecture ?
Thanks.
Regards,
F.
pgpnOPWMzne_1.pgp
Description: PGP signature
Package: src:uswsusp
Version: 1.0+20120915-6.2
--
Dear maintainer,
I see that configure.ac mention ppc64 . Does that make sense on PowerMac
64b? Would it make sense en Power machines ? I'm not sure which
technology it relies on.
At least it compile on ppc64. It even compiled on ppc64el after
Package: src:e3
Version: 1:2.71-2
--
Dear maintainer,
is there any reason that e3 isn't built on more arches ?
I tried on ppc64el/ppc64 and it built out of the box.
Maybe "any" could be enabled ?
Regards,
F.
pgp56IfNB_Bsn.pgp
Description: PGP signature
Package: src:diamond-aligner
Version: 0.9.26+dfsg-1
--
Dear maintainer,
with some basic changes I could enable diamond-aligner to built on ppc64el.
It actually builds on powerpc, ppc64, i386 and I thought we could enable
it to build on "any". What do you think of that ?
Here is a merge request :
Package: src:crystalhd
Version: 1:0.0~git20110715.fdd2f19-13
--
Dear maintainer,
with some basic changes I could enable crystalhd to built on ppc64el.
Here is a merge request :
https://salsa.debian.org/multimedia-team/crystalhd/merge_requests/1
Thanks.
Regards,
F.
pgpdULCxKRJTt.pgp
Package: src:cnvkit
Version: 0.9.6-1
--
Dear maintainer,
is there any reason that cnvkit isn't built on ppc64el ?
Looks like it builds out of the box.
Regards,
F.
pgpBHz0tfsw_d.pgp
Description: PGP signature
Package: src:htslib
Version: 1.9-11
--
Dear maintainer,
is there any reason that htslib isn't built on i386 ?
Out of curiosity, I tried to build it and it actually worked.
Regards,
F.
pgpkZweNiDBMh.pgp
Description: PGP signature
Package: src:libssw
Version: 1.1-2
--
Dear maintainer,
with some basic changes I could enable libssw to built on ppc64el.
Here is a merge request :
https://salsa.debian.org/med-team/libssw/merge_requests/1
Thanks.
Regards,
F.
pgpS7yxtcRGz1.pgp
Description: PGP signature
Package: src:bwa
Version: 0.7.17-3
--
Dear maintainer,
with some basic changes I could enable bwa to built on ppc64el.
Here is a merge request :
https://salsa.debian.org/med-team/bwa/merge_requests/1
Thanks.
Regards,
F.
pgp6kVRRrhHYM.pgp
Description: PGP signature
Hi,
> I think the only reason is that I forgot to add it to debian/control after
> upstream merged the necessary bits :(
no worries.
> Thanks for the reminder; I should be able to include that in the next
> upload.
Thanks a lot Ben!
pgpviGOHeGh2J.pgp
Description: PGP signature
Package: src:bolt-lmm
Version: 2.3.4+dfsg-1
--
Dear maintainer,
with some basic changes I could enable bolt-lmm to built on i386 and
ppc64el. I ran example 2 and it seemed to do the job.
Here is a merge request :
https://salsa.debian.org/med-team/bolt-lmm/merge_requests/1
Thanks.
Regards,
F.
Control: tags -1 patch
--
Hi,
I submitted a merge request which enables ngs-sdk to build on ppc64* and
possibly others :
https://salsa.debian.org/med-team/ngs-sdk/merge_requests/1
Regards,
F.
pgpRFWhUMZx9T.pgp
Description: PGP signature
Package: src:bcal
Version: 2.1+git20190806.6c8d325-1
--
Dear maintainer,
is there any reason that bcal is not built on other architectures
(any/linux-any)?
I tested and it built well on ppc64/ppc64el.
Regards,
F.
pgpAEEO_1oMrY.pgp
Description: PGP signature
Hi,
I see 2.44.14 which previously built, does not built in the very same build
environment where 2.44.15 fails.
Looking at the differences and trying downgrading some build deps, I
found that replacing rustc 1.37 with 1.36 makes 2.44.14 and 2.44.15 build
again in that latest schroot.
Any idea
Package: src:libguytools2
Version: 2.0.5-3
--
Dear maintainer,
is there any reason that libguytools2 is not built on more architectures ?
I tested on ppc64/ppc64el and it built well, so at least those arches
could be added.
Regards,
F.
pgpsMk81_sY_Q.pgp
Description: PGP signature
Package: src:kgb
Version: 1.0b4+ds-14
--
Dear maintainer,
is there any reason that kgb is not built on more architectures ?
I tested on ppc64/ppc64el and it built well, so at least those arches
could be added.
Regards,
F.
pgplIUiOAIN2T.pgp
Description: PGP signature
Package: src:ibsim
Version: 0.7-2
--
Dear maintainer,
is there any reason that ibsim is not built on more architectures ?
I tested on ppc64/ppc64el and it built well, so at least those arches
could be added.
Regards,
F.
pgpCgrtKRZmqQ.pgp
Description: PGP signature
Dear maintainers,
do you have any plan to take that patch for ppc64el build ?
It would also fix the current FTBFS on ppc64.
Regards,
F.
pgpOJSrud57_3.pgp
Description: PGP signature
Package: src:purelibc
Version: 0.4.1-2
--
Dear maintainer,
is there any reason that purelibc isn't built on ppc64el ?
I tested on ppc64el and it built well.
Regards,
F.
pgpAw_gk4oE26.pgp
Description: PGP signature
Package: src:openafs
Version: 1.8.4~pre1-1
--
Dear maintainer,
is there any reason that openafs isn't built on ppc64el(maybe linux-any) ?
I tested on ppc64el and with minor modifications (arch verifications in
debian/sysname and debian/module/sysname), it built well.
Regards,
F.
1 - 100 of 215 matches
Mail list logo
