Control: tag -1 fixed-upstream pending
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/115
Hello Lucas,
Lucas Nussbaum [2020-12-26 22:57 +0100]:
> > Bail out! ERROR:../tests/test-umockdev.c:1135:t_testbed_usb_lsusb:
> > assertion failed (exit_status == 0): (256 == 0)
I
On 2020-12-26 23:15 +0100, Axel Beckert wrote:
> Sven Joachim wrote:
>> > Looks like a missing dependency on libxxhash-dev on a first glance.
>> >
>> > Will check if that helps. (And I wonder where that one got lost.)
>>
>> It did not get lost, rather I suppose that the latest apt upload
>>
For the record, I reinstalled the machine in question with Ubuntu
18.04 a few days ago, and upgraded it since to 20.04, and the
problem was not present there.
This make me suspect this issue is fixed in kernel 5.4.0
and possible earlier versions.
I am unable to test with a Debian kernel. :(
--
Hello Helmut,
Helmut Grohne [2020-12-26 17:39 +0100]:
> given the prolonged silence on these bugs, I've uploaded a NMU with
> delay 10 fixing both and adding a Multi-Arch stanza. All of the changes
> seem quite safe to me. I've performed local test builds for various
> configurations (nocheck,
Am Samstag, dem 26.12.2020 um 13:35 +0100 schrieb Martin:
> On 2020-12-26 06:02, Bruno Kleinert wrote:
> > when I enter gajim's settings window (keyboard shortcut Ctrl+P), go to tab
> > 'Audio/Video' and check and uncheck the 'Live preview" checkbox, gajim
> > reproducibly crashes. Selecting
Hi,
On 24/12/20 at 17:16 +0100, Michael Banck wrote:
> Package: libopenmpi3
> Version: 3.1.3-11
> Severity: serious
>
> Even with the fixed libpmix2_4.0.0~rc1-2, I am getting runtime failures
> trying to run MPI programs, e.g. the nwchem autopkgtests all fail like
> this:
A simple way to
I too face this issue on Debian testing with pulseaudio 13.0-5 installed.
$ lspci | fgrep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition
Audio Controller (rev 30)
I believe it’s a reasonable assumption that the kernel matches the Debian
release. If anybody is running with old kernel or disables getrandom I would
say they are on their own - also other stuff will break, not only apache2.
Ondrej
--
Ondřej Surý (He/Him)
> On 27. 12. 2020, at 0:24, Stefan
Source: chasquid
Version: 1.3-1
Severity: serious
Control: close -1 1.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 961814
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync
Source: picolibc
Version: 1.4.6-1
Severity: serious
Control: close -1 1.4.7-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing
Source: golang-gopkg-lxc-go-lxc.v2
Version: 0.0+git20190625.f4822c6-1
Severity: serious
Control: close -1 0.0+git20201012.d1943fb-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now
Source: pipemeter
Version: 1.1.3-1
Severity: serious
Control: close -1 1.1.4-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 972958
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
On 12/27/20 12:13 AM, Aurelien Jarno wrote:
> On 2020-12-26 08:05, Sebastiaan Couwenberg wrote:
>> On 12/25/20 11:17 PM, Logan Rosen wrote:
>>> libhdf4 currently FTBFS on riscv64. William Grant applied a patch in
>>> Ubuntu to add support for the architecture.
>>>
>>> Thanks for considering the
forwarded -1 https://github.com/henrydcase/nobs/issues/37
from upstream:
> only x86-64 and aarch64 is currently supported. why would you need i386
> exactly?
So currently maybe we can only build for amd64 and arm64.
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
reassign 978236 src:insighttoolkit4
found 978236 insighttoolkit4/4.13.3withdata-dfsg1-3
affects 978236 src:otb
thanks
On 12/26/20 10:40 PM, Lucas Nussbaum wrote:
>> The following packages have unmet dependencies:
>> libinsighttoolkit4-dev : Depends: libnifti-dev
This is not an issue in otb, but
Hi,
Axel Beckert wrote:
> I intent to maintain this package under the umbrella of the Debian
> Emacsen Team (X-Debbugs-CC'ed). Until I get Salsa write access to their
> repos, I published my work temporarily at
> https://salsa.debian.org/abe/elpa-ligature
The repo has been moved to
Quoting Jonas Smedegaard (2020-04-18 19:02:15)
> UglifyJS 2 is dead upstream (no code commit since June 2017).
>
> These packages will *not* be part of Bullseye:
>
> src:uglifyjs
> libjs-uglify
> node-uglify
>
> Projects now using UglifyJS 2 can either upgrade to UglifyJS 3 or
> migrate to
Package: emacs-gtk
Version: 1:27.1+1-3
Severity: wishlist
Tags: patch fixed-upstream
Control: affects -1 elpa-ligature
Dear Rob,
I'm currently packaging ligature.el from
https://github.com/mickeynp/ligature.el at
https://salsa.debian.org/emacsen-team/elpa-ligature
According to
Hi Cédric,
On Sun, Dec 27, 2020 at 2:57 AM Cédric Boutillier wrote:
> I've just created a merge request on salsa
> https://salsa.debian.org/debian/libgit2/-/merge_requests/3
> with a proposition.
> This adds an extra libgit2-fixtures binary package, shipping the
> examples under tests/resources
A few observations.
1) The commit
https://github.com/rollup/plugins/commit/1459cf0ab5e5eb7beee46f52bc4dbbb88d3e4335#diff-c68d63c5e10e04a850c0ea8abd479dbb77c794b3aadecf91483dcf3df96156df
which prevents exceptions from being silently ignored maybe the reason
why this is starting to err.
2)
X-Debbugs-CC: p...@debian.org
On Wed, 23 Dec 2020 23:51:57 +0100 Pino Toscano
wrote:
> reassign 977988 src:kimageannotator
> forcemerge 977649 977988
> thanks
>
> In data mercoledì 23 dicembre 2020 22:26:13 CET, Dominik George ha
scritto:
> > Package: kde-spectacle
> > Version: 20.12.0-1
> >
Version 8.1.0 of android-libboringssl is also broken; ref bug report #933865 -
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933865.
Control: reassign -1 libalure1
Control: forcemerge 960707 -1
Control: tag -1 + confirmed
Control: affects -1 + bucklespring
Hi,
jan de kruyf wrote in June 2020:
> Error loading libfluidsynth.so.1: libfluidsynth.so.1: cannot open shared
> object
> file: No such file or directory
Just ran into
So, on your system where:
- xfonts-100dpi is not installed
- gsfonts-x11 is installed
- xterm uses Helvetica with: -fn
'-*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1'
What do you get from:
find /usr -name '*helvB18*'
find /usr -name fonts.dir | xargs grep -i 'helvetica-bold-r-.*180'
Control: severity -1 important
在 2020-12-26星期六的 18:48 -0500，Boyuan Yang写道：
> Source: ibus-libpinyin
> Version: 1.12.0-2
> Severity: serious
> Tags: ftbfs sid
>
> As shown on
> https://buildd.debian.org/status/package.php?p=ibus-libpinyin ,
> currently ibus-libpinyin FTBFS on armel armhf and
* Shengjing Zhu:
> dep is deprecated by upstream. The upstream repo is now read-only.
> Users should have migrated to Go modules.
I agree. Not because I think that the Go Modules concept is generally
more sensible, but because it has caused the go-dep project to stop.
> I was thinking just to
Source: libcommoncpp2
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Two man pages shipped in libcommoncpp2-doc include names based on the
build path:
Source: libcommoncpp2
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath usrmerge shell
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The included file /usr/share/doc/libcommoncpp2-dev/examples/Makefile.gz
various paths dependent on the
Ilkka Virta writes:
> On Fri, Nov 13, 2020 at 2:06 AM Simon Josefsson via OATH Toolkit general
> discussions wrote:
>
>> Thank you for the patch -- this makes sense. I'm not fond of the name
>> 'args-from-files' though. How about this behaviour: if the supplied
>> strings for KEY and/or OTP
Package: usbguard
Version: 0.7.8+ds-2
Severity: normal
Hello,
Currently the postinst script calls "usbguard add-user" to allow the
plugdev group.
This seems redundent to me as plugdev is already listed in the
usbguard-daemon.conf file.
Please stop calling this and rely on the
Package: whipper
Version: 0.9.0-4
Severity: important
X-Debbugs-Cc: age.bo...@protonmail.com
Dear Maintainer,
* What led up to the situation?
After a new/clean install of whipper, it's primary function, ripping a cd, does
not work, resulting in an error instead.
* What exactly did you do
Dear Alerto,
Thanks for your notification. I am sad to hear that the plugin support
will be removed.
The plugin is our company's in house program to provide a way to
communicate between C/C++ and JavaScript, makes it possible for the
connected primitive hardware to play some roles in the
Package: usbguard
Version: 0.7.4+ds-1
Severity: important
Hello,
Curently, the postinstall script of the package is generating a default
policy that allows all USB devices conntected at the time of the
installation.
The problem is that there is no guarantee that the user has all the
needed USB
Control: clone -1 -2
Control: retitle -2 RM: mozjs52 -- ROM; superseded by mozjs78, no reverse
dependencies remain
Control: severity -2 normal
Control: reassign -2 ftp.debian.org
On Sat, 26 Dec 2020 at 23:46:48 +0100, Aurelien Jarno wrote:
> I confirm that nothing else is using this package
this is basically resolved by the fact that unstable is on 3.x
Package: wnpp
Severity: wishlist
* Package name: jolokia
Version : 1.6.2
Upstream Author : Roland Huß
* URL : https://github.com/rhuss/jolokia
* License : Apache-2.0
Programming Lang: Java
Description : a fresh way to access JMX MBeans remotely using
Package: libtrapperkeeper-metrics-clojure
Version: 1.3.1-1
Severity: wishlist
At the moment, libtrapperkeeper-metrics-clojure patches out Jolokia
entirely, as it's not in the archive.
It would be nice to remove that patch and add support for it, as v1
endpoints are being deprecated.
--
Steven Robbins writes:
> On Saturday, December 26, 2020 12:50:58 A.M. CST Keith Packard wrote:
>
>> I've tagged version '1.0' of this repository and created some (not
>> finished) debian packaging for it. This version has imported the mille
>> sources from 'upstream' which include copyright
Santiago Vila, le dim. 27 déc. 2020 00:59:23 +0100, a ecrit:
> On Sun, Dec 27, 2020 at 12:29:01AM +0100, Samuel Thibault wrote:
> > Lucas Nussbaum, le sam. 26 déc. 2020 22:52:15 +0100, a ecrit:
> > > > INTLTOOL_EXTRACT="/usr/bin/intltool-extract"
> > > > XGETTEXT="/usr/bin/xgettext" srcdir=.
On Sun, Dec 27, 2020 at 12:29:01AM +0100, Samuel Thibault wrote:
> Hello gettext maintainers,
>
> Lucas Nussbaum, le sam. 26 déc. 2020 22:52:15 +0100, a ecrit:
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> > >
On 2020-12-27 00:04, Simon McVittie wrote:
> On Sun, 27 Dec 2020 at 00:45:43 +0100, Aurelien Jarno wrote:
> > Looking at the licenses, both RFC included in the tarball are definitely
> > non-free
>
> According to the replies to #894158, d/copyright contains permission to
> distribute those RFCs
On 2020-12-27 00:45, Aurelien Jarno wrote:
> clone 894158 -1
> retitle -1 libogg contains RFC released under a non-free license
> severity -1 serious
> thanks
>
> On 2018-03-27 11:09, Simon McVittie wrote:
> > If the RFCs are false-positives and they are actually Free Software,
> > please add
On Sun, 27 Dec 2020 at 00:45:43 +0100, Aurelien Jarno wrote:
> Looking at the licenses, both RFC included in the tarball are definitely
> non-free
According to the replies to #894158, d/copyright contains permission to
distribute those RFCs under DFSG licenses, if I'm reading correctly. I
would
Ciao Francesco,
Francesco Poli wrote:
> >* Add hard dependency on virtual package notification-daemon.
> > + Mention in README.Debian that not all notification-daemon
> >implementations start up automatically upon user login.
> > + Closes: #974949
>
> Thank you Axel! :-)
Source: ibus-libpinyin
Version: 1.12.0-2
Severity: serious
Tags: ftbfs sid
As shown on
https://buildd.debian.org/status/package.php?p=ibus-libpinyin ,
currently ibus-libpinyin FTBFS on armel armhf and mipsel due to errors
around Lua in tests:
Package: ftp.debian.org
Severity: normal
Hi,
As subject says, please drop mochikit from unstable, as it is no
longer used anywhere in Debian.
Cheers,
--
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com
signature.asc
Description: This is a digitally signed
clone 894158 -1
retitle -1 libogg contains RFC released under a non-free license
severity -1 serious
thanks
On 2018-03-27 11:09, Simon McVittie wrote:
> If the RFCs are false-positives and they are actually Free Software,
> please add Lintian overrides to document this for future contributors. If
Am 26.12.2020 um 23:08 teilte Lucas Nussbaum mit:
Source: proftpd-mod-dnsbl
Version: 0.1.5-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64
forwarded 978369 https://github.com/apertium/apertium-eo-ca/issues/2
thanks
Fixed in upstream.
-- Tino Didriksen
Hello gettext maintainers,
Lucas Nussbaum, le sam. 26 déc. 2020 22:52:15 +0100, a ecrit:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> > INTLTOOL_EXTRACT="/usr/bin/intltool-extract" XGETTEXT="/usr/bin/xgettext"
> > srcdir=. /usr/bin/intltool-update
forwarded 978359 https://github.com/apertium/apertium-br-fr/issues/4
thanks
Fixed in upstream.
-- Tino Didriksen
reassign 978045 libapr1
found 978045 1.7.0-1
thanks
Am 25.12.20 um 03:18 schrieb David W:
You can see that the associated call/failure is happening inside APR
here, on
line 216:
https://svn.apache.org/viewvc/apr/apr/trunk/misc/unix/rand.c?revision=1832691=markup#l216
Hi,
Axel Beckert wrote:
> dpkg: error processing archive
> /tmp/apt-dpkg-install-hDYr38/054-libudunits2-0_2.2.28-1_amd64.deb (--unpack):
> trying to overwrite '/usr/share/xml/udunits/udunits2-accepted.xml', which is
> also in package libudunits2-data 2.2.28-1
[...]
> Seems as if either that
Samuel Thibault, le dim. 27 déc. 2020 00:13:55 +0100, a ecrit:
> FTR, the file that poses problem is Testing/gtest/test/gtest_unittest.cc
> This is not something that contains anything to be translated, we'd need
> some option to just ignore Testing/ entirely.
More precisely, it is line
On 2020-12-26 08:05, Sebastiaan Couwenberg wrote:
> Control: tags -1 pending
>
> On 12/25/20 11:17 PM, Logan Rosen wrote:
> > libhdf4 currently FTBFS on riscv64. William Grant applied a patch in
> > Ubuntu to add support for the architecture.
> >
> > Thanks for considering the patch.
>
> Thanks
FTR, the file that poses problem is Testing/gtest/test/gtest_unittest.cc
This is not something that contains anything to be translated, we'd need
some option to just ignore Testing/ entirely.
Samuel
Package: reportbug
Version: 7.9.0
Severity: wishlist
Sometimes when I am on a bug page I want to file another bug, but
against the source package, so I copy-paste src:foo but then reportbug
doesn't accept that on the command-line.
Similarly when I want to report a bug against a source package, I
Package: libudunits2-0
Version: 2.2.28-1
Severity: serious
Hi,
upgrading libudunits2-0 from 2.2.26-5+b1 to 2.2.28-1 fails for me as
follows:
Preparing to unpack .../054-libudunits2-0_2.2.28-1_amd64.deb ...
Unpacking libudunits2-0 (2.2.28-1) over (2.2.26-5+b1) ...
dpkg: error processing archive
la 26. jouluk. 2020 klo 21.30 Rick Thomas (rbtho...@rcthomas.org) kirjoitti:
>
> Package: upgrade-system
> Version: 1.7.3.1
> Severity: normal
>
> --- Please enter the report below this line. ---
>
> The package "deluge" is manually (i.e. not "auto") installed on my
> system. I use it daily. But
Package: sympa
Version: 6.2.40~dfsg-1+deb10u1
Severity: normal
Dear Maintainer,
I've tried to upgrade sympa, and lead to debocnf error because i've mounted a
filesystem
for 'arc' subdir:
root@mail:~# df -h
File system Dim. Usati Dispon. Uso% Montato su
/dev/loop1 2,9G 1,9G904M
Package: python3-ruffus
Version: 2.8.4-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:sga
sga cannot be cross built, because its dependency on python3-ruffus is
not satisfiable. In general, Architecture: all packages can never
satisfy
Package: wnpp
Severity: wishlist
X-Debbugs-CC: sk...@debian.org
* Package name: cygwin
* URL : http://cygwin.com
* License : LGPL
Programming Lang: C, C++
Description : library and headers providing POSIX functionality on Windows
As an alternative to MinGW, Cygwin is
On 2020-11-08 22:06, Bryan Quigley wrote:
> This package is brought in by cinnamon through cjs.
>
> The cinnamon upstream project has been ported to mozjs78 in
> https://github.com/linuxmint/cinnamon/pull/9624
>
> And the switchover is included in an unreleased version in salsa -
>
Simon Josefsson writes ("Re: Bug#839278: oathtool: has no secure way to provide
a key"):
> I have pushed Ian's patch, but I dropped his newly introduced
> command-line parameter and instead allowed for KEY and OTP parameters to
> be - to mean stdin or @filename like you suggested Ilkka.
Thanks.
Re: Peter Felecan
> Package: cura
> Version: 4.5.0-1
> Severity: important
>
> Dear maintainers,
>
> I have a very annoying behavior since a long time but only recently I
> understood the origin of the problem. By the way, it's similar to the
> bug report #951033 "cura: UI not usable in 4.4.1"
Source: epm
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
The file /usr/bin/epm contains an embedded build path:
Package: gdb-source
Version: 10.1-1.5
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gdb-source now only contains the following:
/usr/share/doc/gdb-source/NEWS.Debian.gz
/usr/share/doc/gdb-source/changelog.Debian.gz
/usr/share/doc/gdb-source/changelog.gz
Source: node-rollup-plugin-typescript
Version: 6.0.0+~1.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Hi Sven,
Sven Joachim wrote:
> > Looks like a missing dependency on libxxhash-dev on a first glance.
> >
> > Will check if that helps. (And I wonder where that one got lost.)
>
> It did not get lost, rather I suppose that the latest apt upload
> introduced this new include without adding a
Source: malcontent
Version: 0.10.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: easyh10
Version: 1.5-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: xdemorse
Version: 3.6.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> DC-Build-Header: xdemorse 3.6.
Source: runawk
Version: 1.6.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: elpa
Version: 2019.11.001-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]: Entering direct
Source: node-ast-types
Version: 0.14.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: macopix
Version: 3.4.0+dfsg.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: phpmyadmin
Version: 4:4.9.7+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: google-recaptcha
Version: 1.2.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: ssl-utils-clojure
Version: 3.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: zhcon
Version: 1:0.2.6-17
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: php-gettext
Version: 1.0.12-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: apertium-eo-fr
Version: 0.9.0~r57551-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Enter
Source: paexec
Version: 1.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: gkdebconf
Version: 2.1.0
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: sundials
Version: 4.1.0+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: node-deep-eql
Version: 4.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: ap-utils
Version: 1.5-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: gnokii
Version: 0.6.30+dfsg-1.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: lgeneral
Version: 1.4.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: apertium-eo-ca
Version: 1:0.9.1~r60655-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Enter
Source: ibus-anthy
Version: 1.5.11-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: libmaa
Version: 1.4.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpack
Source: xracer
Version: 0.96.9.1-10
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: fonts-inter
Version: 3.15+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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: transmission-remote-gtk
Version: 1.4.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Enter
Source: python-whoosh
Version: 2.7.4+git6-g9134ad92-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: apertium-ukr
Version: 0.1.0~r82563-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: node-debug-fabulous
Version: 1.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: node-eslint-plugin-node
Version: 11.1.0~ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: hg-git
Version: 0.9.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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
1 - 100 of 403 matches
Mail list logo
