El 31/5/24 a las 13:21, Drew Parsons escribió:
Source: adios4dolfinx
Followup-For: Bug #1071722
Santiago, could you try running with
export OMPI_MCA_rmaps_base_oversubscribe=true
added to the top of debian/rules?
That seems to work.
And also it works again on single-cpu systems
(where it
Package: src:python-peachpy
Version: 0.0~git20211013.257881e-1.1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules
In such bug I proposed to run mpi with true and skip
the tests if it fails.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057556#34
Maybe a similar idea would work here as well.
We can try that. As you suggested in the other bug, it might be quirk of
openmpi we're facing.
openmpi
El 25/5/24 a las 16:42, Drew Parsons escribió:
Source: adios4dolfinx
Followup-For: Bug #1071722
Control: tags -1 ftbfs
adios4dolfinx is building cleanly in reproducibility builds.
Perhaps the problem was a temporary glitch on your test system?
No, this is unlikely to be a temporary glitch:
Package: src:tpot
Version: 0.11.7+dfsg-5
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with
Package: src:spyder-memory-profiler
Version: 0.2.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
Package: src:qiskit-ibmq-provider
Version: 0.4.6-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:pyfftw
Version: 0.13.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with
Package: src:adios4dolfinx
Version: 0.8.1.post0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:intel-mkl
Version: 2020.4.304-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
El 14/5/24 a las 7:15, Antonio Valentino escribió:
On Sat, 11 May 2024 21:46:59 +0200 Santiago Vila wrote:
E error: unknown target CPU 'generic'
I'm sorry but I have no clue about this issue.
Looking at the log It seems that the CPU is not recognized.
Yes, that's what it seems
owner 1070950 sanv...@debian.org
thanks
El 12/5/24 a las 8:36, Santiago Vila escribió:
Another option is that I simply change NPROCS to 1 as you point out,
verify that it works, including machines with a single cpu, and do the
proposed-updates upload (but in this case the mystery of mpi would
[ adding 1070...@bugs.debian.org to the loop ]
El 12/5/24 a las 7:42, Antonio Valentino escribió:
Dear Santiago,
Il 11/05/24 21:55, Debian Bug Tracking System ha scritto:
Processing control commands:
close -1 1.0~b1-5
Bug #1070950 [src:pysph] pysph: FTBFS in bullseye
Marked as fixed in
Package: src:ros-vcstools
Version: 0.1.42-3
Severity: serious
Control: close -1 0.1.42-7
Tags: ftbfs bullseye
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
Package: src:pysph
Version: 1.0~b0~20191115.gite3d5e10-4
Severity: serious
Control: close -1 1.0~b1-5
Tags: ftbfs bullseye
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
Package: src:compyle
Version: 0.7-2
Severity: serious
Control: close -1 0.8.1-4
Tags: ftbfs bullseye
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules
Package: src:zarr
Version: 2.17.2+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
El 3/12/23 a las 19:00, Daniel Gröber escribió:
Hi Lucas,
On Thu, Oct 26, 2023 at 09:45:53AM +0200, Lucas Nussbaum wrote:
As an additional data point, I can still reproduce this.
I cannot provide the buildinfo, as sbuild outputs it at the end of
successful builds.
Doh! Didn't think of that.
/debian/changelog 2023-12-13 18:40:00.0 +0100
@@ -1,3 +1,11 @@
+pyzoltan (1.0.1-2+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * debian/rules: Set NPROC to 1 so that the package may be
+built on systems with a single core. Closes: #1055625.
+
+ -- Santiago Vila Wed, 13
-12 21:30:00.0
+0100
@@ -1,3 +1,10 @@
+vlfeat (0.9.21+dfsg0-6+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * Apply patch by Dennis Filder to fix build error. Closes: #991066.
+
+ -- Santiago Vila Tue, 12 Dec 2023 21:30:00 +0100
+
vlfeat (0.9.21+dfsg0-6) unstable; urgency
# Also happens in bullseye
found 1055625 1.0.1-2
tags 1055625 + bullseye
owner 1055625 !
thanks
This happens even when using r6a.large instances from AWS,
which have 2 vCPUs. I'll try to fix this for bullseye.
Thanks.
--
debian-science-maintainers mailing list
Package: src:ycm-cmake-modules
Version: 0.13.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:python-escript
Version: 5.6-5
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build -v
Package: src:lmfit-py
Version: 1.2.2-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
to 1 so that the package may be
+built on systems with a single core. Closes: #1055625.
+
+ -- Santiago Vila Sun, 12 Nov 2023 23:25:00 +0100
+
pyzoltan (1.0.1-5) unstable; urgency=medium
* Standards version bumped to 4.6.1 (non changes).
diff -Nru pyzoltan-1.0.1/debian/rules pyzoltan
tags 1055625 + patch
thanks
Ok, thanks to the fact that the package is reproducible, I've just
checked that the package builds the same regardless of NPROCS
being set to 1 or 2 in debian/rules.
Therefore, we can build it using NPROCS = 1 for everybody,
and nothing is lost. As I said before,
Package: src:pyzoltan
Version: 1.0.1-5
Severity: important
Tags: ftbfs
Dear maintainer:
During a mass-rebuild of all packages in bookworm, this
package failed to build in this way:
[...]
raise RuntimeError(msg)
E RuntimeError: test geometric_partitioner.py failed with
Hi. Just FYI: After the upload, the package is currently
BD-Uninstallable on hurd-amd64:
https://buildd.debian.org/status/package.php?p=mpi-defaults=sid
(I guess this should be fixed somewhere else).
Thanks.
--
debian-science-maintainers mailing list
owner 1050845 !
owner 1055458 !
thanks
El 6/11/23 a las 20:13, Samuel Thibault escribió:
AIUI the debian/control part is auto-generated.
Oh, I see. There is a control.in and a control (mandated by policy),
and dpkg-buildpackage aborts if control is not ok.
I use a similar trick in base-files
Version: 1:0.3.7-11
Hi. Since stretch is no longer supported, I'm closing
my own bug using buster version.
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
El 26/9/23 a las 16:50, Daniel Gröber escribió:
Hi Lucas,
On Tue, Sep 26, 2023 at 03:43:28PM +0200, Lucas Nussbaum wrote:
Source: yosys
Version: 0.33-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
The full build log
El 28/2/23 a las 12:53, Andrius Merkys escribió:
On a related note, is trying network access to localhost RC?
It's ok if you try to connect to a service started by the build process
itself (please downgrade again if my severity change was wrong).
This is the exact wording in policy:
For
severity 1016958 serious
thanks
Hello. Merely trying network access is already considered RC,
so this should really be serious.
(I would be willing to test a fix if somebody proposes one).
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
Package: src:armci-mpi
Version: 0.3.1~beta-6
Severity: important
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-arch
dh
Package: src:taurus-pyqtgraph
Version: 0.5.9-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh
Package: src:sardana
Version: 3.0.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-indep
dh build-indep
El 28/1/23 a las 11:49, Markus Blatt escribió:
How should we proceed. Is there a possibility to do the builds on other
machines with
more RAM?
I have just enabled 8GB of swap in the test machine I gave you. If you believe
it's lack of RAM,
please show me where the "out of memory" happens in
El 27/1/23 a las 23:48, Graham Inggs escribió:
Control: severity -1 important
Hi Markus, Santiago
As opm-common is no longer in bookworm, this bug is currently unreproducible.
When I wrote "bookworm" I meant "bookworm and above".
Should I change the title so that you don't interpret it
Package: src:opm-common
Version: 2022.10+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-indep
dh
severity 1027208 important
thanks
Hi. I think this is what you really meant.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
On Mon, Sep 09, 2019 at 09:37:20AM +0200, Graham Inggs wrote:
> Hi Santiago
>
> Did you try rebuilding with:
>
> DEB_BUILD_OPTIONS=nocheck
>
> as suggested in #932795 [1] ?
That's not the type of QA I'm doing. I'm trying to keep Debian buster
free of FTBFS bugs like this one, and naturally me
reopen 907829
found 907829 1.1-5
fixed 907829 2.2-1
thanks
Hi.
Could we please fix this in buster as well?
(for some future point release)
I'm still doing QA on buster and it's a real pain to find packages
which FTBFS. Please let me know if you need/require/welcome help
for this.
Thanks.
Hi.
Package: src:mpi4py
Version: 3.0.2-12
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep
Greetings.
I can reproduce this bug, and I've put a bunch of failed build logs here:
https://people.debian.org/~sanvila/build-logs/hkl/
The bug happens "randomly", but in a very particular way: always in some
instances and never in the others.
I believe this may be some sort of Makefile bug
On Tue, 2 Oct 2018, Adrian Bunk wrote:
> Everyone else uses the common-sense approach of using CPU-strong
> machines for CPU-intensive tasks like package building, if you
> have made different practical experiences I'd be interested in
> seeing the bills.
On Fri, May 10, 2019 at 03:37:51PM +0200, Andreas Beckmann wrote:
> The bug is now again in the bts-is-confused state: found+fixed in the
> same version (which is treated as not-fixed and wont-be-archived). My
> intention was to close it as invalid (found with version, fixed without
> version) +
Version: 2.6~20180302-1
On Sun, May 05, 2019 at 09:41:21AM +0100, Rebecca N. Palmer wrote:
> Control: tags -1 moreinfo
>
> It works for me, in both sid and buster cowbuilder chroots.
Same here, just tried in both buster and sid, using sbuild.
So, I'm closing the bug.
[ Ansgar: If you still can
On Wed, Apr 24, 2019 at 04:47:16PM +0200, Sylvestre Ledru wrote:
> Le 24/04/2019 à 16:45, Santiago Vila a écrit :
> > On Wed, Apr 24, 2019 at 04:24:59PM +0200, ghisv...@gmail.com wrote:
> > > Anyone objecting on applying Santiago's patch to src:arpack to fix the
> > >
On Wed, Apr 24, 2019 at 04:24:59PM +0200, ghisv...@gmail.com wrote:
> Anyone objecting on applying Santiago's patch to src:arpack to fix the
> occasionnal FTBFS on single-core builders?
>
> If not, then I am happy to prepare a release.
Thanks a lot.
One minor clarification: The failure happens
Package: src:gmsh
Version: 4.1.3+ds1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=cmake
I said:
[ lots of things ]
Ok, sorry, I didn't want to sound confrontational. Just FYI: The
reason this issue makes me to be upset is the discussion that took
place here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907829
[ Since you applied buster-ignore here, you might want to apply
Hi. I forgot: The fact that you decided to use buster-ignore here
means that it's still ok to use "serious" for these kind of bugs?
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
On Sat, 13 Apr 2019, Ivo De Decker wrote:
> # buildds have at least 2 CPU cores
However, this is still a FTBFS bug in a release architecture (amd64).
We are a free software distribution. We don't agree that the end user
*must* be able to rebuild the package?
For the record: I can build 99.99%
Package: src:arpack
Version: 3.7.0-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
Package: src:dune-pdelab
Version: 2.6~20180302-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep --parallel
> Still there seems to be an issue with your specific build environment,
> and of course this is a bug (but maybe not an RC one, since you are the
> first to report such a build failure after many years). Could you give
> more details about the hardware you are using?
I'm currently using Scaleway
Package: src:openblas
Version: 0.3.5+ds-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-arch
dh binary-arch
Package: src:lammps
Version: 0~20181211.gitad1b1897d+dfsg1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
severity 922946 serious
thanks
On Fri, 22 Feb 2019, Andrej Shadura wrote:
> The Roboto upstream no longer provides hinted fonts, so
> fonts-roboto-hinted is now a transitional package providing symlinks to
> the unhinted fonts. Please modify your package to use the unhinted fonts
> instead.
The
Package: src:hydroffice.bag
Version: 0.2.15-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with
Package: src:pyfr
Version: 1.5.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3,sphinxdoc
Package: src:lmfit-py
Version: 0.9.11+dfsg-1
Severity: serious
Tags: ftbfs patch
Hello Andreas et al.
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with
Package: src:morse-simulator
Version: 1.4-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
dh_update_autotools_config
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --builddirectory=_build
Package: src:sketch
Version: 1:0.3.7-10
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:bliss
Version: 0.73-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf
Package: src:ask
Version: 1.1.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2
Package: src:gfsview
Version: 20121130+dfsg-5
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with autoreconf
found 917500 3.8.0+repack1-3
thanks
Hi. Sorry for the reopening but this does not seem fixed.
I can still reproduce the error in our test machine (using sbuild)
and it also fails (with a different error) in reproducible-builds:
Small update: I've given Anton Gladky access to a machine where this
seems to happen all the time. (While we are at it: Anybody reading
this willing to debug the problem in the test machine, please contact
me privately and I will gladly give you access as well).
It is interesting to see that this
Package: src:harp
Version: 1.5+data-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch --with python3
Package: src:schroedinger-coordgenlibs
Version: 1.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
Package: src:liggghts
Version: 3.8.0+repack1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:schroedinger-maeparser
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package but it failed:
[...]
debian/rules build-arch
dh build-arch
Package: src:coda
Version: 2.18.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package but it failed:
[...]
config.status: executing depfiles commands
config.status: error: in `/<>':
> building != running
>
> And I am getting really annoyed of your double standard regarding
> build requirements.
We have to put things in perspective before claiming double-standards.
> If a package cannot be built on a single-core machine with 256 MB RAM
> due to the number of CPUs, you
On Sun, Sep 30, 2018 at 06:22:23PM +0300, Adrian Bunk wrote:
> Noone is talking about no longer supporting running Debian on
> single-core systems.
Well, you are talking about dropping (or lowering) support for
building Debian on single-core systems.
But we are not a proprietary software
On Sun, Sep 30, 2018 at 04:32:17PM +0300, Adrian Bunk wrote:
> On Sun, Sep 30, 2018 at 03:10:23PM +0200, Santiago Vila wrote:
> >...
> > In my opinion, you are so much fixated on the idea that "does not fail
> > on the buildds" is the "same" as &quo
On Fri, 7 Sep 2018, Adrian Bunk wrote:
> On Fri, Sep 07, 2018 at 02:45:31PM +0200, Santiago Vila wrote:
> >...
> > And I put a very simple example: Imagine that all our amd64
> > autobuilders are Intel and there is a package which FTBFS on AMD.
> >
> >
Package: src:lua-torch-image
Version: 0~20170420-g5aa1881-6
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
On Fri, Sep 07, 2018 at 10:46:36AM +0300, Adrian Bunk wrote:
> On Thu, Sep 06, 2018 at 10:46:07PM +0200, Santiago Vila wrote:
>
> > You will have noticed that we usually report FTBFS bugs when a package
> > fails to build in any "correctly" configured autobuilder, we
reassign 907920 gmsh
thanks
On Tue, Sep 04, 2018 at 07:57:55AM +0200, Nico Schlömer wrote:
> Package: hello
> Version: 3.0.6+dfsg1-3
>
>
> When building some meshes, I'm getting
> ```
> Error : Petsc is required (we do need complex in discreteFace::crossField())
> ```
> followed a double free
On Mon, Sep 03, 2018 at 01:03:27PM +0300, Adrian Bunk wrote:
> On Mon, Sep 03, 2018 at 01:22:47AM +0200, Santiago Vila wrote:
> >...
> > This single-CPU thing has been discussed before and the bugs have
> > never stopped being serious:
> >
> > https://list
On Mon, Sep 03, 2018 at 09:23:54AM +0200, Graham Inggs wrote:
> Hi Santiago
>
> On 2 September 2018 at 19:21, Santiago Vila wrote:
> > My guess is that this is a bug in p4est but it's triggered by a build
> > depends
> > which changed behaviour somewhere between 2017
On Mon, Sep 03, 2018 at 01:33:30AM +0300, Adrian Bunk wrote:
> On Sun, Sep 02, 2018 at 11:19:04PM +0200, Santiago Vila wrote:
> > This is not an architecture-specific bug which only happens on
> > unreleased architectures.
> >
> > Instead, this happened to me o
Package: src:p4est
Version: 1.1-5
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
Package: src:orocos-kdl
Version: 1.4.0-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster and sid but it failed:
[...]
debian/rules binary-arch
dh binary-arch
retitle 830739 mpi-testsuite: FTBFS randomly because Makefile errors are not
trapped properly
retitle 907158 mpi-testsuite: FTBFS randomly because Makefile errors are not
trapped properly
forcemerge 830739 907158
severity 830739 serious
thanks
--
debian-science-maintainers mailing list
On Sun, 10 Jul 2016, Aaron M. Ucko wrote:
> Source: mpi-testsuite
> Version: 3.2+dfsg-1
> Severity: important
> Justification: fails to build from source
>
> Builds of mpi-testsuite on kFreeBSD and the Hurd have been failing:
>
> config.status: executing default-4 commands
> for i in `find
On Sun, Aug 26, 2018 at 12:24:35AM +0300, Adrian Bunk wrote:
> Control: severity -1 important
>
> On Fri, Aug 24, 2018 at 11:03:54AM +, Santiago Vila wrote:
> >...
> > for i in `find . -name "testlist" | grep -v ^
Package: src:mpi-testsuite
Version: 3.2+dfsg-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
Package: src:cb2bib
Version: 1.9.7-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --parallel
Package: src:librecad
Version: 2.1.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:newmat
Version: 1.10.4-6
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
QUILT_PATCHES=debian/patches \
Package: src:python-admesh
Version: 0.98.8-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with python2,python3
Package: src:lua-torch-torch7
Version: 0~20170926-g89ede3b-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
Package: src:lmfit-py
Version: 0.9.7+dfsg-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with
Package: src:jeuclid
Version: 3.1.9-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
test -x debian/rules
mkdir -p "."
if [ -d
Package: src:freefem
Version: 3.5.8-6
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
1 - 100 of 106 matches
Mail list logo
