Your message dated Wed, 20 Jan 2021 07:48:48 +
with message-id
and subject line Bug#980526: fixed in maven 3.6.3-3
has caused the Debian Bug report #980526,
regarding maven: Update to maven 3.6.3-2 drops dependency to
libcommons-cli-java, renders package unusable
to be marked as done.
This
Processing control commands:
> tag -1 pending
Bug #980526 [maven] maven: Update to maven 3.6.3-2 drops dependency to
libcommons-cli-java, renders package unusable
Added tag(s) pending.
--
980526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980526
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #980526 in maven reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: maven
Version: 3.6.3-2
Severity: grave
Justification: renders package unusable
Hi there,
first of all thanks a lot for all the work of maintaining the maven package in
debian.
The last update to maven 3.6.3-2 in unstable dropped the dependency to
libcommons-cli-java,
whichs renders
On 2021-01-18, Vagrant Cascadian wrote:
> both rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot with
> 2021.01 (and rockpro64-rk3399 may have issues with 2020.10 as well).
Both platforms initialize USB from "preboot", but somehow this triggers
a boot failure.
This can be worked around by
Yes, and this is partly my fault. I've prepared a version of this
patch [1] and forwarding it to upstream [2]. [1] Also includes
some other fixes that should get in, but weren't worth delaying
the upload for. (But this certainly is!)
/sbin is the correct place for this, right?
Antonio
[1]
Processing control commands:
> severity -1 important
Bug #980464 [zfs-dracut] zfs-dracut: dracut+ZFS-on-root systems rendered
unbootable
Severity set to 'important' from 'critical'
--
980464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980464
Debian Bug Tracking System
Contact
Control: severity -1 important
Lowering the severity to unblock the migration, as migration is
currently the first priority for us due to the huge diff between
0.8.6 and 2.0.1, given the stable freeze schedule.
I will fix it and upload 2.0.1-3 immediately after migration.
It is easy to apply
Package: libmkl-interface-dev
Version: 2020.3.279-1
Severity: serious
Justification: packaging issue
X-Debbugs-Cc: witold.bary...@gmail.com
Dear Maintainer,
root@debian:~# apt dist-upgrade --purge
Reading package lists... Done
Building dependency tree
Reading state information... Done
Processing commands for cont...@bugs.debian.org:
> affects 979041 - dolfin mshr pysph dolfinx
Bug #979041 [libopenmpi3] libopempi3: aborts python code due to libfabric
fork() issues
Removed indication that 979041 affects dolfin, mshr, pysph, and dolfinx
> affects 979041 + src:dolfin src:mshr
Processing control commands:
> tags -1 patch
Bug #957116 [src:cyclades-serial-client] cyclades-serial-client: ftbfs with
GCC-10
Added tag(s) patch.
--
957116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* Fix FTBFS with GCC 10 due to multiple definitions.
Thanks for considering the patch.
Logan
diff -Nru cyclades-serial-client-0.93ubuntu2/inc/dev.h
cyclades-serial-client-0.93ubuntu3/inc/dev.h
Source: dump1090-mutability
Version: 1.15~20180310.4a16df3+dfsg-6
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Hi,
dump1090-mutability FTBFS with
Package: dvi2ps
Version: 5.1j-1.3
Followup-For: Bug #957157
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Mark variable as extern to fix FTBFS
Processing control commands:
> tags -1 patch
Bug #957157 [src:dvi2ps] dvi2ps: ftbfs with GCC-10
Added tag(s) patch.
--
957157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: efax-gtk
Version: 3.2.8-2.1
Followup-For: Bug #957165
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10: Cherrypick/adapt upstream Git commit to
Processing control commands:
> tags -1 patch
Bug #957165 [src:efax-gtk] efax-gtk: ftbfs with GCC-10
Added tag(s) patch.
--
957165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> forwarded 980498 bug-gu...@gnu.org
Bug #980498 [src:guile-3.0] guile-3.0 FTBFS on amd64: check-guile fails
Set Bug forwarded-to-address to 'bug-gu...@gnu.org'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
forwarded 980498 bug-gu...@gnu.org
thanks
Helmut Grohne writes:
> guile-3.0 failed to build from source on the buildd on amd64. It is hard
> to pin down the actual failure. It happens during unit tests.
> https://buildd.debian.org/status/fetch.php?pkg=guile-3.0=amd64=3.0.5-1=1610521112=0
> is
Package: redshift
Version: 1.12-4
Followup-For: Bug #892275
X-Debbugs-Cc: witold.bary...@gmail.com
I believe it was working before. Now it fails for me too on log in with a
dialog showing it can't connect to geoclue.
user@debian:~$ systemctl --user status redshift
● redshift.service - Redshift
FWIW, I gave the patch a review and it seems sane to me. I also looked
at the package in unstable and confirmed that zgenhostid is being
installed to /sbin, not /bin.
--
Richard
Processing commands for cont...@bugs.debian.org:
> tags 948876 - ftbfs
Bug #948876 [fontforge] fontforge: Segmentation fault, making kodi FTBFS
Bug #948977 [fontforge] fontforge: Segmentation fault, making kodi FTBFS
Removed tag(s) ftbfs.
Removed tag(s) ftbfs.
> thanks
Stopping processing here.
Processing control commands:
> found -1 20110425
Bug #922981 [ca-certificates-java] ca-certificates-java:
"update-ca-certificates -f" doesn't update "/etc/ssl/certs/java/cacerts"
Marked as found in versions ca-certificates-java/20110425.
> severity -1 serious
Bug #922981 [ca-certificates-java]
Your message dated Tue, 19 Jan 2021 23:17:59 +
with message-id
and subject line Bug#972246: fixed in numba 0.52.0-1
has caused the Debian Bug report #972246,
regarding numba ftbfs in unstable with python3.9 as supported python3 version
to be marked as done.
This means that you claim that the
Your message dated Tue, 19 Jan 2021 23:05:18 +
with message-id
and subject line Bug#971095: fixed in derivations 0.57.20210107-2
has caused the Debian Bug report #971095,
regarding derivations: FTBFS: PDF.cc:141:63: error: no matching function for
call to ‘Catalog::findPage(const int&, const
Processing control commands:
> tags 957797 + patch
Bug #957797 [src:simh] simh: ftbfs with GCC-10
Added tag(s) patch.
> tags 957797 + pending
Bug #957797 [src:simh] simh: ftbfs with GCC-10
Added tag(s) pending.
--
957797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957797
Debian Bug
Control: tags 957797 + patch
Control: tags 957797 + pending
--
Dear maintainer,
I've prepared an NMU for simh (versioned as 3.8.1-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -u simh-3.8.1/debian/changelog
Processing commands for cont...@bugs.debian.org:
> close 978251
Bug #978251 [src:ruby-mysql2] ruby-mysql2: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978251:
Processing control commands:
> tags -1 + patch
Bug #980473 [python3-potr] ModuleNotFoundError: No module named 'Crypto'
Added tag(s) patch.
--
980473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
On 2021-01-20 01:52:54 +1100, Konomi Kitten wrote:
> Package: python3-otr
> Version: python3-potr
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: konomikit...@gmail.com
>
> Trying to import potr throws the following error:
>
> $ python3
>
Your message dated Tue, 19 Jan 2021 21:04:34 +
with message-id
and subject line Bug#979270: fixed in python-rfc6555 0.0~git20190913.1a181b4-3
has caused the Debian Bug report #979270,
regarding python-rfc6555: Requires network access during build
to be marked as done.
This means that you
Processing control commands:
> close -1 2.0.2+dfsg-1
Bug #980501 [src:r-cran-projpred] src:r-cran-projpred: fails to migrate to
testing for too long: Build-Depends not available on armel
Marked as fixed in versions r-cran-projpred/2.0.2+dfsg-1.
Bug #980501 [src:r-cran-projpred]
Source: r-cran-projpred
Version: 1.1.6-1
Severity: serious
Control: close -1 2.0.2+dfsg-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
I suggest you request removal of r-cran-projpred on armel, the package
doesn't build.
As recently
Processing commands for cont...@bugs.debian.org:
> tags 979439 + upstream
Bug #979439 {Done: Rene Engelhard } [hunspell-it] hunspell-it:
Italian spell check cannot recognize simple words
Added tag(s) upstream.
> forwarded 979439 https://bugs.documentfoundation.org/show_bug.cgi?id=139193
Bug
Your message dated Tue, 19 Jan 2021 20:38:24 +
with message-id
and subject line Bug#973789: fixed in parsinsert 1.04-10
has caused the Debian Bug report #973789,
regarding src:parsinsert: fails to migrate to testing for too long: FTBFS on
armel, armhf, mips64el and ppc64el
to be marked as
Hello,
I was looking through Debian release-critical bugs and saw this report
that no one had followed up on. Evolution 3.38.2 is working for me and
I was wondering if you were still having trouble.
Also I see you had stable and experimental in your sources list and I
think that's likely to lead
Source: guile-3.0
Version: 3.0.5-1
Severity: serious
Tags: ftbfs
guile-3.0 failed to build from source on the buildd on amd64. It is hard
to pin down the actual failure. It happens during unit tests.
https://buildd.debian.org/status/fetch.php?pkg=guile-3.0=amd64=3.0.5-1=1610521112=0
is a link to
Processing control commands:
> tags -1 pending
Bug #976929 [src:parsinsert] parsinsert: FTBFS on ppc64el: incorrect result
Added tag(s) pending.
--
976929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 pending
Hi David,
Following up on parsinsert failing to build from source on POWER
64 bits little endian on Debian Testing, I found out that
reducing the compiler optimization level to -O1 allows the test
suite to pass.
The affected configuration is Debian 11 at Testing stage,
Processing control commands:
> severity -1 important
Bug #972334 [src:llvm-toolchain-11] llvm-toolchain-11: autopkgtest failure on
i386: integration-test-suite-test FAIL non-zero exit status 2
Bug #975906 [src:llvm-toolchain-11] llvm-toolchain-11: autopkgtest segfaults on
armhf and fails on
control: severity -1 important
On Mon, 16 Nov 2020 21:56:27 +0100 Sebastian Ramacher
wrote:
> On 2020-11-14 23:16:15 +0100, Sylvestre Ledru wrote:
> > severity 972334 normal
> >
> > thanks
> >
> > Hello
> >
> > As this isn't a new regression (it didn't work before), I am lowering the
> >
Processing control commands:
> severity -1 important
Bug #979495 [src:llvm-toolchain-11] clang_delta (creduce, cvise) segfaults when
built with LLVM 11
Severity set to 'important' from 'serious'
> found -1 1:11.0.0-5
Bug #979495 [src:llvm-toolchain-11] clang_delta (creduce, cvise) segfaults when
control: severity -1 important
control: found -1 1:11.0.0-5
On Thu, 7 Jan 2021 12:02:43 +0100 Matthias Klose wrote:
> Package: src:llvm-toolchain-11
> Version: 1:11.0.1-1
> Severity: serious
> Tags: sid bullseye
> Forwarded: https://bugs.llvm.org/show_bug.cgi?id=48682
>
> First seen at
Processing commands for cont...@bugs.debian.org:
> tags 978675 + sid bullseye
Bug #978675 {Done: Holger Levsen }
[libsys-hostname-long-perl] libsys-hostname-long-perl: FTBFS, tests fail
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
I know that ubuntu "masquerades" snap installations as having come via
apt. I don't see that on bullseye though.
I have installed "lxd" (which is not packaged as a .deb) via snapd.
root@piserver:~# dpkg-query --list lxd
dpkg-query: no packages found matching lxd
root@piserver:~#
Processing control commands:
> reopen -1
Bug #980406 {Done: Pirate Praveen } [node-xterm]
node-xterm: likely broken build - JSON.parse: unexpected character at line 1
column 1 of the JSON data Resource
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions
Control: reopen -1
Control: severity -1 important
Control: tags -1 help
On Tue, Jan 19, 2021 at 6:54 pm, Debian Bug Tracking System
wrote:
Your message dated Tue, 19 Jan 2021 18:50:13 +
with message-id
and subject line Bug#980406: fixed in node-xterm 3.8.1+~cs0.9.0-1
has caused the
Your message dated Tue, 19 Jan 2021 18:50:13 +
with message-id
and subject line Bug#980406: fixed in node-xterm 3.8.1+~cs0.9.0-1
has caused the Debian Bug report #980406,
regarding node-xterm: likely broken build - JSON.parse: unexpected character at
line 1 column 1 of the JSON data Resource
Your message dated Tue, 19 Jan 2021 18:50:13 +
with message-id
and subject line Bug#954678: fixed in node-xterm 3.8.1+~cs0.9.0-1
has caused the Debian Bug report #954678,
regarding node-xterm: FTBFS: src/renderer/ColorManager.test.ts(12,18): error
TS2694: Namespace
Source: wine-development
Version: 5.5-9
Severity: serious
Hello, your package FBTFS in sid...
missing build on arm64
missing build on armel
missing build on armhf
can you please have a look?
thanks
G.
Processing commands for cont...@bugs.debian.org:
> tags 958117 + pending
Bug #958117 [src:uglifyjs] uglifyjs: dead code: keep away from bullseye
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958117:
Processing control commands:
> Severity -1 important
Bug #980025 [nextcloud-desktop] nextcloud-desktop: Nextcloud-desktop starts but
window doesn't display properly and disappears in GNOME
Severity set to 'important' from 'grave'
> reassign -1 gnome-shell
Bug #980025 [nextcloud-desktop]
Control: Severity -1 important
Control: reassign -1 gnome-shell
Control: affects -1 nextcloud-desktop
This sounds not like the fault of nextcloud-desktop and I cannot reproduce it
under a KDE environment. that's why lowering the severity and forward to
gnome-shell.
It also may makes sense to
Your message dated Tue, 19 Jan 2021 16:48:46 +
with message-id
and subject line Bug#980437: fixed in dqlite 1.6.0-2
has caused the Debian Bug report #980437,
regarding libdqlite-dev: missing dependency on libsqlite3-dev
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> close 971123 0.15-1
Bug #971123 [src:kxd] kxd: FTBFS: dh_auto_test: error: make -j4 test returned
exit code 2
Marked as fixed in versions kxd/0.15-1.
Bug #971123 [src:kxd] kxd: FTBFS: dh_auto_test: error: make -j4 test returned
exit code 2
Your message dated Tue, 19 Jan 2021 17:42:31 +0100
with message-id <86fd3262523a87ae6b27edbc398533be78d72122.ca...@debian.org>
and subject line Re: Bug#943396: FTBFS on armhf: testsuite segfault
has caused the Debian Bug report #943396,
regarding FTBFS on armhf: testsuite segfault
to be marked as
On Tue, Jan 19, 2021 at 5:06 pm, Xavier wrote:
Le 19/01/2021 à 15:04, Pirate Praveen a écrit :
On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
wrote:
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without
any
issues. So this is a bug in
Your message dated Tue, 19 Jan 2021 16:33:48 +
with message-id
and subject line Bug#980475: fixed in libnet-traceroute-perl 1.15-2
has caused the Debian Bug report #980475,
regarding libnet-traceroute-perl: FTBFS depending on network configuration
to be marked as done.
This means that you
Your message dated Tue, 19 Jan 2021 16:33:48 +
with message-id
and subject line Bug#980475: fixed in libnet-traceroute-perl 1.15-2
has caused the Debian Bug report #980475,
regarding libnet-traceroute-perl FTBFS on IPV6-only buildds
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> forwarded 980481 https://github.com/dap/XML-Stream/issues/25
Bug #980481 [src:libxml-stream-perl] libxml-stream-perl FTBFS on IPV6-only
buildds
Bug #692311 [src:libxml-stream-perl] FTBFS if non-local network communication
is forbidden
Set Bug
Processing commands for cont...@bugs.debian.org:
> tags 977086 + ftbfs
Bug #977086 [src:python-dugong] python-dugong FTBFS with pytest 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977086:
Processing commands for cont...@bugs.debian.org:
> tags 977091 + ftbfs
Bug #977091 [src:python-pymeasure] python-pymeasure FTBFS with pytest 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977091:
Processing commands for cont...@bugs.debian.org:
> reassign 980481 src:libxml-stream-perl 1.23-1
Bug #980481 [src:libxml-stream-perl] libxml-stream-perl FTBFS on IPV6-only
buildds
Ignoring request to reassign bug #980481 to the same package
Bug #980481 [src:libxml-stream-perl] libxml-stream-perl
Processing control commands:
> tag -1 pending
Bug #980475 [src:libnet-traceroute-perl] libnet-traceroute-perl FTBFS on
IPV6-only buildds
Bug #849933 [src:libnet-traceroute-perl] libnet-traceroute-perl: FTBFS
depending on network configuration
Added tag(s) pending.
Added tag(s) pending.
--
Control: tag -1 pending
Hello,
Bug #980475 in libnet-traceroute-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le 19/01/2021 à 15:04, Pirate Praveen a écrit :
>
>
> On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
> wrote:
>> Control: severity -1 serious
>>
>> I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
>> issues. So this is a bug in node-xterm debian build.
>
> Trying to switch
Package: chromium
Version: 87.0.4280.141-0.1~deb10u1
Severity: serious
Tags: buster
Dear Maintainer,
I upgraded chromium on Debian stable (buster) from
83.0.4103.116-1~deb10u3 to 87.0.4280.141-0.1~deb10u1.
After this upgrade chromium becomes completely unusable to me, which
means, that the
Source: libxml-stream-perl
Version: 1.24-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libxml-stream-perl=all=1.24-3.1=1610929660=0
...
Cannot resolve x86-conova-01: at /<>/blib/lib/XML/Stream.pm line
208.
# Looks like your test exited with 255 before it could
Your message dated Tue, 19 Jan 2021 16:03:40 +
with message-id
and subject line Bug#980470: fixed in jsxgraph 1.3.5+dfsg1-8
has caused the Debian Bug report #980470,
regarding jsxgraph FTBFS: /usr/bin/uglifyjs: not found
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 19 Jan 2021 16:04:07 +
with message-id
and subject line Bug#977915: fixed in r-cran-arsenal 3.5.0-3
has caused the Debian Bug report #977915,
regarding r-cran-arsenal: autopkgtest failure on several architectures
to be marked as done.
This means that you claim that
Your message dated Tue, 19 Jan 2021 15:48:21 +
with message-id
and subject line Bug#980469: fixed in almond 0.3.3+dfsg-6
has caused the Debian Bug report #980469,
regarding almond FTBFS: uglifyjs: No such file or directory
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> reassign 980475 src:libnet-traceroute-perl 1.15-1
Bug #980475 [src:libnet-traceroute-perl] libnet-traceroute-perl FTBFS on
IPV6-only buildds
Ignoring request to reassign bug #980475 to the same package
Bug #980475 [src:libnet-traceroute-perl]
Processing control commands:
> reassign -1 python3-potr 1.0.2-3
Bug #980473 [python3-otr] ModuleNotFoundError: No module named 'Crypto'
Warning: Unknown package 'python3-otr'
Bug reassigned from package 'python3-otr' to 'python3-potr'.
No longer marked as found in versions python3-potr.
Ignoring
Control: reassign -1 python3-potr 1.0.2-3
Reassigned because I typoed the package name.
Output of apt policy python3-potr:
python3-potr:
Installed: 1.0.2-3
Candidate: 1.0.2-3
Version table:
*** 1.0.2-3 500
500 https://deb.debian.org/debian unstable/main amd64 Packages
500
Source: libnet-traceroute-perl
Version: 1.15-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libnet-traceroute-perl=all=1.15-1.1=1610929613=0
...
not ok 9 - Hop 4 has 3 queries # TODO Unknowns aren't quite right yet
# Failed (TODO) test 'Hop 4 has 3 queries'
#
Package: python3-otr
Version: python3-potr
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: konomikit...@gmail.com
Trying to import potr throws the following error:
$ python3
Python 3.9.1+ (default, Jan 10 2021, 15:42:50)
[GCC 10.2.1 20201224] on linux
Type "help",
Source: almond
Version: 0.3.3+dfsg-5
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=almond=all=0.3.3%2Bdfsg-5=1610721789=0
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
uglifyjs -o almond.min.js almond.js
make[1]: uglifyjs: No such file or
Source: jsxgraph
Version: 1.3.5+dfsg1-7
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=jsxgraph=all=1.3.5%2Bdfsg1-7=1610723955=0
...
cp build/bin/jsxgraphcore.min.js distrib/jsxgraphcore.js
mkdir -p build/bin/readers
{ cat COPYRIGHT; /usr/bin/uglifyjs
On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
wrote:
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
issues. So this is a bug in node-xterm debian build.
Trying to switch to rollup instead of browserify-lite, but tsc itself
is failing
Your message dated Tue, 19 Jan 2021 13:23:43 +
with message-id
and subject line Bug#980238: fixed in ucx 1.10.0~rc1-5
has caused the Debian Bug report #980238,
regarding do not depend on the non-public binutils ABI
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 19 Jan 2021 11:49:34 +
with message-id
and subject line Bug#978352: fixed in gftl 1.3.0+is-really-1.2.7-1
has caused the Debian Bug report #978352,
regarding gftl-shared: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu
&& cmake -DCMAKE_INSTALL_PREFIX=/usr
Quoting Xavier (2021-01-19 11:56:33)
[ quotes seemingly not directly related snipped ]
> Notes:
> * I'm not the author of the breakage, I did no source update on this
>package (just fixed node-uglify problem)
> * The breakage came before soft-freeze
> * I just tried to fix RC bug since
On 2021-01-19 14:15, Pirate Praveen wrote:
> It is not about breaking as such, but breaking without coordination and
> planning that is the problem. We have a release team and transition process
> for a reason. I don't think uploading breaking changes without giving
> adequate notice and
Le 19/01/2021 à 11:11, Jonas Smedegaard a écrit :
> Quoting Xavier (2021-01-18 22:16:30)
>> Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
>>>
>>> On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro
>>> wrote:
But the fact is that all the other reverse dependencies that used
any plugin
Your message dated Tue, 19 Jan 2021 10:48:29 +
with message-id
and subject line Bug#962596: fixed in ca-certificates 20210119
has caused the Debian Bug report #962596,
regarding ca-certificates: Removal of GeoTrust Global CA requires investigation
to be marked as done.
This means that you
Your message dated Tue, 19 Jan 2021 10:48:29 +
with message-id
and subject line Bug#942915: fixed in ca-certificates 20210119
has caused the Debian Bug report #942915,
regarding ca-certificates: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> retitle 979670 nvidia-graphics-drivers: CVE-2021-1052, CVE-2021-1053,
> CVE-2021-1056
Bug #979670 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052,
CVE‑2021‑1053, CVE‑2021‑1056
Changed Bug title to
Your message dated Tue, 19 Jan 2021 10:33:31 +
with message-id
and subject line Bug#980438: fixed in bpftrace 0.11.3-5
has caused the Debian Bug report #980438,
regarding do not depend on the non-public binutils ABI
to be marked as done.
This means that you claim that the problem has been
On Mon, Jan 18, 2021 at 12:36PM, Sudip Mukherjee wrote:
> Thanks. And I will also like to have your advice on the question of a
> transitional package for offlineimap3.
> I am in confusion about that.
>
> 1. If we dont have a transitional package then users of offlineimap
> will see it not
Processing control commands:
> tag -1 pending
Bug #954352 {Done: picca } [python3-silx] pymca: Missing
dependency "python3-scipy", probably in "python3-silx"
Added tag(s) pending.
--
954352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954352
Debian Bug Tracking System
Contact
Followup-For: Bug #954352
Control: tag -1 pending
buster-pu: https://bugs.debian.org/980453
Andreas
Processing control commands:
> forcemerge 964537 949570
Bug #964537 [src:dropwatch] dropwatch should not depend on the shared binutils
libraries
Bug #949570 [src:dropwatch] dropwatch should not use the private binutils
shared libraries
Severity set to 'serious' from 'important'
Marked as found
Quoting Xavier (2021-01-18 22:16:30)
> Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
> >
> > On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro
> > wrote:
> >> But the fact is that all the other reverse dependencies that used
> >> any plugin now need to be changed accordingly. Otherwise we
Your message dated Tue, 19 Jan 2021 11:07:40 +0100
with message-id <99542aec-7f70-d0ed-ce15-ab7643c84...@debian.org>
and subject line Re: racon: FTBFS: fatal error: bioparser/bioparser.hpp: No
such file or directory
has caused the Debian Bug report #979727,
regarding racon: FTBFS: fatal error:
❦ 19 janvier 2021 10:57 +01, Vincent Bernat:
>> bpftrace should not depend on the non-public binutils ABI. This always
>> generated
>> an upper dependency on libbinutils. If you think it's worth having this
>> dependency, please statically link with libbinutils and record the the
>> version
❦ 19 janvier 2021 08:33 +01, Matthias Klose:
> bpftrace should not depend on the non-public binutils ABI. This always
> generated
> an upper dependency on libbinutils. If you think it's worth having this
> dependency, please statically link with libbinutils and record the the version
> used in
Control: severity -1 important
Control: tags -1 +stretch
Le vendredi 30 octobre 2020 à 16:10:09+0100, Ludwig Gramberg a écrit :
> when lxc-net and netfilter/iptables-persistent are installed the start-up
> script
> in lxc-net uses iptables-commands while iptables-restore is used by
>
Processing control commands:
> severity -1 important
Bug #973439 [lxc] lxc-net conflicts with iptables-persistent on boot
Severity set to 'important' from 'grave'
> tags -1 +stretch
Bug #973439 [lxc] lxc-net conflicts with iptables-persistent on boot
Added tag(s) stretch.
--
973439:
Your message dated Tue, 19 Jan 2021 09:33:47 +
with message-id
and subject line Bug#956766: fixed in gcin 2.9.0+dfsg1-2
has caused the Debian Bug report #956766,
regarding gcin: Build-Depends (unnecessarily?) on deprecated libappindicator
to be marked as done.
This means that you claim that
Your message dated Tue, 19 Jan 2021 09:33:47 +
with message-id
and subject line Bug#921005: fixed in gcin 2.9.0+dfsg1-2
has caused the Debian Bug report #921005,
regarding Missing manual dependency for package gcin on libappindicator3-1
to be marked as done.
This means that you claim that
1 - 100 of 116 matches
Mail list logo
