On Wed, Jan 20, 2021 at 08:14:45PM -0500, Daniel Kahn Gillmor wrote:
> Package: rust-sequoia-sqv
> Version: 1.0.0-1
>
> Looks like the autopkgtests are not being run for rust-sequoia-sqv (or
> for sq-keyring-linter or sqop). I think this is because some rust
> packages needed specifically for
On 20/01/21 at 23:05 +, Simon McVittie wrote:
> On Wed, 20 Jan 2021 at 22:01:14 +0100, Lucas Nussbaum wrote:
> > > dpkg-source -b .
>
> Are you deliberately rebuilding the source package? That seems unusual
> for testing whether packages FTBFS...
Yes, it's not that much additional effort
On Thu, Jan 21, 2021 at 12:50 PM Sébastien Delafond wrote:
> I'm not expecting upstream to fix it either, but it'd feel more
> comfortable to close this bug on our side while still linking to an
> existing upstream issue.
Of course. Here it is: https://github.com/samwoods1/in-parallel/issues/8
Package: dput-ng
Version: 1.31
Severity: wishlist
Tags: patch
Dear Maintainer(s),
this adds a new method "ftps" following RFC 4217 with ftplib.FTP_TLS (py
standard library).
Patch is in this salsa merge request:
https://salsa.debian.org/debian/dput-ng/-/merge_requests/14
Thanks for
Hi,
In that case what does it take to become a maintainer for this package?
Are there any docs on how the build process works?
Regards,Patrick
On Wed, 20 Jan 2021 18:00:45 +0100 Salvatore Bonaccorso <
car...@debian.org> wrote:> Hi,> > On Mon, Jan 11, 2021 at 05:23:50PM
+0100, Michel Le Bihan
On 21/01 12:46, Utkarsh Gupta wrote:
> I can create an issue in the original fork. However, just know that
> this library is *not* being maintained at all. So there won't be much
> help from anywhere.
I'm not expecting upstream to fix it either, but it'd feel more
comfortable to close this bug on
Hi Sébastien,
On Thu, Jan 21, 2021 at 12:42 PM Sébastien Delafond wrote:
> > Aah, okay. So I ran sbuild + autopkgtest 10 times, all passed for me.
> > But when I ran these tests locally with rake, it failed for me exactly
> > like the report just for the first time. And then passed all 9 times
>
Package: arc-theme
Version: 20201013-1
On 21/01 12:31, Utkarsh Gupta wrote:
> Aah, okay. So I ran sbuild + autopkgtest 10 times, all passed for me.
> But when I ran these tests locally with rake, it failed for me exactly
> like the report just for the first time. And then passed all 9 times
> afterward.
I haven't been able to
Package: ukui-panel
Version: 3.0.3-1
Severity: wishlist
User: aure...@debian.org
Usertags: libsensors-dev-transition
Dear maintainer,
ukui-panel build-depends on libsensors4-dev, the development package
from lm-sensors. For historical reasons the development package is
versioned. Following the
Package: indicator-sensors
Version: 1.2-1
Severity: wishlist
User: aure...@debian.org
Usertags: libsensors-dev-transition
Dear maintainer,
ukui-panel build-depends on libsensors4-dev, the development package
from lm-sensors. For historical reasons the development package is
versioned. Following
Package: htop
Version: 3.0.3-2
Severity: wishlist
User: aure...@debian.org
Usertags: libsensors-dev-transition
Dear maintainer,
ukui-panel build-depends on libsensors4-dev, the development package
from lm-sensors. For historical reasons the development package is
versioned. Following the
Hi,
If I make the change, will you upload it for me?
Thank you for reporting.
--
Cheers,
Leandro Cunha
Debian Contributor and developer.
Hi Sébastien,
On Thu, Jan 21, 2021 at 11:51 AM Utkarsh Gupta wrote:
> I've started to look into it already but I wasn't able to reproduce
> it. All tests pass for me + autopkgtest (which is what I fixed last
> time). So I am not sure what's going wrong here.
Aah, okay. So I ran sbuild +
Hi Sébastien,
On Thu, Jan 21, 2021 at 11:37 AM Sébastien Delafond wrote:
> since you took care of the last upload, do you also plan to fix this
> FTBFS? If not, please let me know and I'll look into it.
I've started to look into it already but I wasn't able to reproduce
it. All tests pass for
Package: linux-source-5.9
Version: 5.9.15-1~bpo10+1
Severity: important
Tags: upstream
Dear Maintainer,
5.9.15 crashes regularly with memory/paging related messages, like this:
=
Jan 15 17:25:09 host kernel: [125426.427889] BUG: unable to handle page fault
for address: 2500
Jan
Hi Utkarsh,
since you took care of the last upload, do you also plan to fix this
FTBFS? If not, please let me know and I'll look into it.
Cheers,
--
Seb
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "grap":
* Package name: grap
Version : 1.46-1
Upstream Author : Ted Faber
* URL : https://www.lunabase.org/~faber/Vault/software/grap/
* License :
Hi,
On Wed, Jan 20, 2021 at 10:23:30PM +, Thomas Habets wrote:
> libcheck made a breaking change.
> Patch for arping to make it build:
> https://github.com/ThomasHabets/arping/commit/e0773bc26ae14d4a19825023307d1496d7c7d0f1
>
> I aim to release 2.22 tomorrow with this change.
> But there are
Hi Diane,
On Wed, Jan 20, 2021 at 04:12:13PM -0800, Diane Trout wrote:
>
> While waiting for numba test cases on the super slow armhf architecture
> to run I got the pynndescent autopkgtests to run (by replacing the
> contents of run-unit-tests) and pushed them to the main packaging
>
Control: reassign -1 firmware-nonfree
Control: retitle -1 firmware: missing txt file for brcm/brcmfmac43340-sdio.bin
Dave Dyer wrote:
> At 05:40 AM 1/18/2021, Holger Wansing wrote:
> >> 3) in my particular case, the driver is brcm/brcmfmac43340-sdio.bin, which
> >> *also* requires a text file,
Seems all it needs is:
sudo systemctl enable gpm
Does that need to be added to the packaging?
Package: gpm
Version: 1.20.7-7
The gpm service does not automatically start on boot.
$ systemctl status gpm
● gpm.service - Console Mouse manager
Loaded: loaded (/lib/systemd/system/gpm.service; disabled; vendor preset:
enabled)
Active: inactive (dead)
Docs: man:gpm(8)
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/04-gcc_10.patch: Fix FTBFS with GCC 10 by adjusting some variables.
Thanks for considering the patch.
Logan
diff -Nru bristol-0.60.11/debian/patches/04-gcc_10.patch
On 1/21/21 4:00 AM, Evangelos Ribeiro Tzaras wrote:
Hi,
On 1/20/21 9:25 PM, Lucas Nussbaum wrote:
Source: chatty
Version: 0.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid
Hi Vagrant,
Do you know which version is the last version that works in this case?
The firmware is from eMMC and it's wired for USB to affect the boot
process.
Thanks,
- Kever
On 2021/1/21 上午8:08, Vagrant Cascadian wrote:
It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc_10: Mark variables as extern to fix FTBFS with GCC 10.
Thanks for considering the patch.
Logan
diff -Nru cde-0.1+git9-g551e54d/debian/patches/gcc_10
Hi,
On 1/20/21 9:25 PM, Lucas Nussbaum wrote:
Source: chatty
Version: 0.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
thanks for your
This can be closed completely as there is now a Flatpak for this software.
Chris
On 1/19/21 6:09 PM, Diederik de Haas wrote:
# journalctl -kaf --no-hostname | grep -w 'apparmor="DENIED"'
jan 20 00:45:32 kernel: audit: type=1400 audit(1611099932.689:41):
apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd"
name="/etc/ssl/openssl.cnf" pid=43157 comm="ntpd"
On Wed, Jan 20, 2021 at 11:03 PM Chris wrote:
> This can be closed completely as there is now a Flatpak for this software.
Please see the documentation about how to close Debian bugs:
https://www.debian.org/Bugs/Developer#closing
PS: Flatpak is quite different and IMO not a substitute for a
I have a suspicion, which is that this is due to the Lutris Runtime missing.
Did you have an internet connection when you launched it the first time?
I'll try it on a live image tomorrow as well.
Regards
Stephan
Package: python3-pylev
Severity: minor
python3-pylev has an off-putting package description, please remove the
phrase "that's not freaking GPL'd" from the long description.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Control: tags -1 + fixed-upstream
Self-compiled 5.10.9 does not show this reported symptom,
and I assume this is fixed-upstream. Ryutaroh
On Wed, 20 Jan 2021 21:48:37 +0100, Lucas Nussbaum said:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This was due to the new libquotient package erroneously creating a
libqmatrixclient-dev binary package. The latest libquotient package
does not do this,
Package: memlockd
Version: 1.2.1
Severity: normal
Usertags: warnings
I get an update-rc.d warning when upgrading memlockd:
...
Preparing to unpack .../memlockd_1.2.1_amd64.deb ...
Unpacking memlockd (1.2.1) over (1.2+b1) ...
Setting up memlockd (1.2.1) ...
update-rc.d: warning:
Control: fixed -1 5.10.5-1
I verified that linux-image-arm64 5.10.5-1 at least boots on
my raspi 4B 8GB model.
On the other hand, vc4.ko gives completely garbled screen to my 4K HDMI
display, and disable_fw_kms_setup=1 does not help unlike
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977642
Hi!
Since your last report of a crash, there's been six new releases:
five in the 0.1.* version series, and now one 4.16.0-1. As the
new version claims a stable release, is there still a reason to
keep xfce4-screensaver out of Bullseye?
I've been using it happily all the time, with no borkage to
I've never used gnutls-cli before, and I'm not at all sure what
openconnect is doing internally to match that behaviour, but it appears
that I can reproduce w/ -cli
$ gnutls-cli ""
Processed 126 CA certificate(s).
Resolving ':443'...
Connecting to ':443'...
- Certificate type: X.509
- Got a
On Wed, 2021-01-20 at 19:26 +0100, Paul Gevers wrote:
> Passing packages that are still shown are those where an update
> happened since the successful run, so they are more or less
> "pending". I realize that probably nobody realizes this.
It is very non-obvious from the output, I'd suggest
On Wed, 20 Jan 2021 21:42:22 +0100, Lucas Nussbaum said:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This version of nheko was just rebuilt 18 days ago as a binNMU.
https://buildd.debian.org/status/fetch.php?pkg=nheko=amd64=0.7.2-3%2Bb1=1609589163=0
That
Package: rust-sequoia-sqv
Version: 1.0.0-1
Looks like the autopkgtests are not being run for rust-sequoia-sqv (or
for sq-keyring-linter or sqop). I think this is because some rust
packages needed specifically for testing are not available in the
archive.
We should add them to the archive so
On Wed, 2021-01-20 at 10:48 +0100, Andreas Tille wrote:
> I've fixed this in Git for the new upstream version. Unfortunately
> this
> new version needs python-pynndescent (ITP #980537) but I need some
> help
> with the test suite there.
>
While waiting for numba test cases on the super slow
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "filezilla":
* Package name: filezilla
Version : 3.52.2-2
Upstream Author : Tim Kosse
* URL : https://filezilla-project.org/
* License : CC0-1.0,
Yes. brcm/brcmfmac43340-sdio.bin is not currently part of the package
either, and I think there's no logic to copy .txt files even if they
are present.
At 04:39 PM 1/20/2021, Holger Wansing wrote:
>Control: reassign -1 firmware-nonfree
>Control: retitle -1 firmware: missing txt file for
I appreciate your detailed explanation, era. Thank you.
On 1/19/21 10:07 PM, era wrote:
The following is based on my -- possibly limited -- understanding based on
reading through the bug reports around this.
On Wed, Jan 20, 2021, at 05:56, Deb-user wrote:
Thank you for your reply. Yes, the
It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
is started. It hangs indefinitely at:
## Flattened Device Tree blob at 01f0
Booting using the fdt blob at 0x1f0
I have observed this also using 2020.10 on rockpro64-rk3399, though on
pinebook-pro-rk3399 usb
On Wed, 2021-01-20 at 14:46 -0800, Noah Meyerhans wrote:
> On Wed, Jan 20, 2021 at 11:39:16PM +0100, Vincent Blut wrote:
> > > We could do that. However, in the past (earlier in this bug,
> > > even) it's
> > > been pointed out that other packages should not be responsible
> > > for
> > > setting
On Wed, 20 Jan 2021 at 22:01:14 +0100, Lucas Nussbaum wrote:
> > dpkg-source -b .
Are you deliberately rebuilding the source package? That seems unusual
for testing whether packages FTBFS...
> > dpkg-source: info: local changes detected, the modified files are:
> >
On Wed, 20 Jan 2021 at 21:30:37 +0100, Lucas Nussbaum wrote:
> >35 | static_assert(SDL_CONTROLLER_BUTTON_MAX - 1 ==
> > SDL_CONTROLLER_BUTTON_DPAD_RIGHT, "non continous name");
I think this is caused by SDL 2.0.14 adding support for more controller
buttons, and supertuxkart assuming that
Le 2021-01-20 14:46, Noah Meyerhans a écrit :
> On Wed, Jan 20, 2021 at 11:39:16PM +0100, Vincent Blut wrote:
> > > We could do that. However, in the past (earlier in this bug, even) it's
> > > been pointed out that other packages should not be responsible for
> > > setting kernel policies, so
I would also like to see a package for Newlib sources. For my case I'm
investigating packaging a cross toolchain to build free firmware (carl9170),
which uses the SH-2 ISA and requires Newlib.
If that is to be built by a new Debian source package instead of this one,
then a newlib-source
Source: graphicsmagick
Version: 1.4+really1.3.36+hg16442-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
graphicsmagick participates in a number of dependency cycles relevant to
architecture bootstrap. Rather than looking into this difficult problem,
I looked into easily droppable
On Wed, Jan 20, 2021 at 11:39:16PM +0100, Vincent Blut wrote:
> > We could do that. However, in the past (earlier in this bug, even) it's
> > been pointed out that other packages should not be responsible for
> > setting kernel policies, so changes like this should be the
> > responsibility of
Source: python-apt
Version: 2.1.7
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
python-apt participates in a number of dependency cycles relevant to
architecture bootstrap. Rather than work on such a difficult problem, I
looked into easily droppable dependencies. It turns out that a
Source: libreadonly-perl
Version: 2.050-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:enblend-enfuse src:krb5-strength src:krb5-sync
src:lbcd src:libafs-pag-perl src:libapache2-mod-perl2 src:libdevel-cover-perl
On Wed, 20 Jan 2021 21:33:41 +0100 Lucas Nussbaum wrote:
> Source: racon
> Version: 1.4.20-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210120 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid
Package: ftp.debian.org
Severity: normal
Hi,
I'm failing my duties on this package, so it's probably time that it goes
away from Debian. Also, see $subject: upstream has become non-responsive.
There's also many alternative solutions that people are using with Postfix
these days (which wasn't
Le 2021-01-20 13:58, Noah Meyerhans a écrit :
> On Wed, Jan 20, 2021 at 10:22:16PM +0100, Vincent Blut wrote:
> > My proposal would differ from yours though in that it would not touch the
> > kernel
> > configuration but would instead consist in patching procps to provide a
> > configuration file
Control: block -1 by 980153
The package starjava-table was recently updated; however it now has a
split-off (source) package starjava-tjoin (ITP #980153). To fix the
FTBFS, starjava-tjoin needs to be accepted, and the updated
starjava-ttools resp. starjava-topcat packages must be uploaded
libcheck made a breaking change.
Patch for arping to make it build:
https://github.com/ThomasHabets/arping/commit/e0773bc26ae14d4a19825023307d1496d7c7d0f1
I aim to release 2.22 tomorrow with this change.
But there are no changes between 2.21 and 2.22, so you can just patch in
the commit, if you
Control: tags -1 + patch
A proposed patch is at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/309
Source: kazocsaba-imageviewer
Version: 1.2.3-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=kazocsaba-imageviewer=all=1.2.3-2=1611094937=0
...
---
Exception in thread "main" java.lang.NoClassDefFoundError:
Control: block -1 by 980153
The package starjava-table was recently updated; however it now has a
split-off (source) package starjava-tjoin (ITP #980153). To fix the
FTBFS, starjava-tjoin needs to be accepted, and the updated
starjava-ttools resp. starjava-topcat packages must be uploaded
Hi,
* Sebastian Ramacher [2021-01-20 22:20]:
On 2021-01-19 00:05:36 +0100, László Böszörményi wrote:
On Mon, Jan 18, 2021 at 10:24 PM Laurent Bigonville wrote:
> Several packages FTBFS since 3.12.4
>
> The autopkgtest catched ignition-msgs and ignition-transport, see
>
Sorry not sorry~HM King MBS
--
Sent from King Philps' NETWORKS & MORE 77
Package: wnpp
Severity: wishlist
Owner: Anton Gladky
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: luma.core
Version : 2.2.0
Upstream Author : Richard Hull and contributors
* URL : https://github.com/rm-hull/luma.core/
* License : MIT
On Wed, Jan 20, 2021 at 10:22:16PM +0100, Vincent Blut wrote:
> My proposal would differ from yours though in that it would not touch the
> kernel
> configuration but would instead consist in patching procps to provide a
> configuration file (let's say default_qdisc.conf) to set the value of the
On Sun, Jan 17, 2021 at 10:29:44PM -0300, Ivan Baldo wrote:
> I think we want the mq qdisc to distribute the load between cores, to
> support very high speed network cards or too slow CPUs.
Yep, you're right. Though it's not about CPU cores, but about tx queues
on the NIC hardware.
>
Hi,
On Wed, Jan 20, 2021 at 09:25:15PM +0100, Lucas Nussbaum wrote:
> Source: arping
> Version: 2.21-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210120 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all
On Wed, Jan 20, 2021 at 10:31:54AM -0800, Kevin J. McCarthy wrote:
> On Tue, Jan 19, 2021 at 08:47:01PM +0100, Antonio Radici wrote:
> > Thanks for the patch, I will upgrade to the latest upstream version by
> > Sunday
> > this week
>
> Antonio, if it helps, I can try to get a 2.0.5 release out
On 2021-01-20 12:58, Lucas Nussbaum wrote:
Source: leiningen-clojure
Version: 2.9.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant
Control: clone -1 -2 -3
Control: reassign -2 src:ignition-msgs 5.1.0+dfsg-6
Control: retitle -2 tighten dependencies on libprotobuf-dev
Control: reassign -3 src:ignition-transport 8.0.0+dfsg-3
Control: retitle -3 tighten dependencies on libprotobuf-dev
On 2021-01-19 00:05:36 +0100, László
Hi Noah,
Le 2021-01-07 16:12, Noah Meyerhans a écrit :
> On Thu, Apr 23, 2020 at 03:34:06PM -0700, Matt Taggart wrote:
> > #890343 was originally opened against systemd asking to install the upstream
> > systemd sysctl.d/50-default.conf file that sets:
> >
> > net.core.default_qdisc = fq_codel
>
On 2021-01-03 16:23, Peter Rohrer wrote:
> Package: usbutils
> Version: 1:010-3
> Severity: minor
>
> Dear Maintainer,
>
> I recently figured out that updating the usb.ids database does not have any
> effect on lsusb, and I realizied that the manpage does no longer refer to the
> usb.ids file.
>
Source: node-jest
Version: 26.6.3+repack+~cs61.38.35-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upcoming package mediasoup needs jest-tobetype for its testsuite.
Please consider embedding jest-tobetype with jest.
Severity raised due to the benefits for the upcoming
Source: golang-github-dvsekhvalnov-jose2go
Version: 1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> deb
On 2021-01-20 09:42, Boyuan Yang wrote:
> According to https://tracker.debian.org/pkg/libqmi , the latest upload
> of package libqmi was not a source-only upload.
That was accidental. Thanks for noticing!
Source: gpaw
Version: 20.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: dolfin
Version: 2019.2.0~git20200629.946dbd3+lfs-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: mpi4py
Version: 3.0.3-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: trapperkeeper-scheduler-clojure
Version: 1.1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: golang-github-cznic-ql
Version: 1.0.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules bu
Source: grcompiler
Version: 5.2-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: golang-github-cznic-strutil
Version: 0.0~git20150430.0.1eb03e3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: node-is-reference
Version: 1.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: node-nodemailer
Version: 6.4.17-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: borgmatic
Version: 1.5.12-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: golang-github-cznic-sortutil
Version: 0.0~git20150617.0.4c73428-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: ceres-solver
Version: 1.14.0-13
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering direct
Source: sfepy
Version: 2019.4-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering direct
Source: tellico
Version: 3.3.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<
Source: dask
Version: 2.11.0+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules bin
Source: felix-latin
Version: 2.0-11.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering direct
Source: gnome-software
Version: 3.38.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: seaborn
Version: 0.10.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: ldc
Version: 1:1.24.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering direct
Source: checkstyle
Version: 8.34-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: seqan
Version: 1.4.2+dfsg-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering direct
Source: liblist-objects-withutils-perl
Version: 2.028003-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
1 - 100 of 318 matches
Mail list logo
