Processing control commands:
> severity -1 normal
Bug #975488 [src:lammps] lammps FTBFS: error: format not a string literal and
no format arguments
Severity set to 'normal' from 'serious'
--
975488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975488
Debian Bug Tracking System
Contact ow..
Control: severity -1 normal
Per reproducible builds [1], lammps starting building again around 2020-11-30.
The recent binNMU for Python 3.9 only was also successful.
[1] https://tests.reproducible-builds.org/debian/history/amd64/lammps.html
Processing commands for cont...@bugs.debian.org:
> tags 976218 + patch
Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of
check_ssl_cert
Ignoring request to alter tags of bug #976218 to the same tags previously set
> tags 976218 + pending
Bug #976218 [src:nagios-plugi
Hi Paul,
On Sun, Dec 6, 2020 at 9:27 PM Paul Gevers wrote:
> On Wed, 27 Mar 2019 19:47:52 + Matthias Klose wrote:
> > The package fails to build in a test rebuild on at least amd64 with
> > gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
> > severity of this report will be raised be
Control: tags 976218 + patch
Control: tags 976218 + pending
Dear maintainer,
to resolve this issue, I've prepared a NMU for nagios-plugins-contrib
(versioned as 27.20200511+1+nmu1), and uploaded it to DELAYED/5. Please
feel free to tell me if I should delay it longer.
Regards.
Christop
dif
Processing control commands:
> tags 976218 + patch
Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of
check_ssl_cert
Added tag(s) patch.
> tags 976218 + pending
Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of
check_ssl_cert
Added tag(s
Your message dated Mon, 07 Dec 2020 07:05:00 +
with message-id
and subject line Bug#976490: fixed in libsis-base-java
18.09~pre1+git20180928.45fbd31+dfsg-2
has caused the Debian Bug report #976490,
regarding libsis-base-java: FTBFS: Unable to delete file:
targets/unit-test-wd/ch.systemsx.cis
Processing commands for cont...@bugs.debian.org:
> fixed 976480 0.0.2+ds-2
Bug #976480 {Done: Andreas Tille } [src:xenium] xenium:
FTBFS: utils.hpp:80:4: error: #error "Unsupported compiler"
Marked as fixed in versions xenium/0.0.2+ds-2.
>
End of message, stopping processing here.
Please contact
Your message dated Mon, 07 Dec 2020 05:48:54 +
with message-id
and subject line Bug#976658: fixed in rust-debcargo 2.4.3-3
has caused the Debian Bug report #976658,
regarding debcargo is broken (and the autopkgtest didn't catch it).
to be marked as done.
This means that you claim that the pro
On Thu, Dec 03, 2020 at 01:27:51PM +0100, Michael Biebl wrote:
>
> Hm, so I applied this change and switched backed to dash, but now I get
>
> autopkgtest systemd --test-name=timedated -s -- lxc -s autopkgtest-sid
> ...
> disable NTP
> enable NTP
> Terminated
> autopkgtest [13:21:42]: test timedat
Processing control commands:
> tags 957533 + patch
Bug #957533 [src:menu-cache] menu-cache: ftbfs with GCC-10
Added tag(s) patch.
> tags 957533 + pending
Bug #957533 [src:menu-cache] menu-cache: ftbfs with GCC-10
Added tag(s) pending.
--
957533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Control: tags 957533 + patch
Control: tags 957533 + pending
Dear maintainer,
Mateusz Łukasik has prepared an NMU for menu-cache (versioned as
1.1.0-1.1) and I've uploaded it to DELAYED/2. Please feel free to
tell me if I should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at
Your message dated Sun, 06 Dec 2020 23:56:20 -0300
with message-id <98857780a3280a91f0d97b6bc33c7a1943d6b663.ca...@debian.org>
and subject line done
has caused the Debian Bug report #972722,
regarding pyvows: ftbfs with python 3.9
to be marked as done.
This means that you claim that the problem ha
Hello Maintainer:
Came across this as well and did some digging to find the cause. Found that
Python 3.9 removed the getiterator attribute and replaced it with iter.
To fix, in file "/usr/lib/python3/dist-packages/catfish_lib/Builder.py" at
line 87 changed this line:
ele_widgets = tree.getiter
Processing commands for cont...@bugs.debian.org:
> severity 976512 important
Bug #976512 [src:xtpcpp] xtpcpp: FTBFS: make[3]: *** No rule to make target
'/usr/lib/x86_64-linux-gnu/libalglib.so', needed by 'src/xtpcpp'. Stop.
Severity set to 'important' from 'serious'
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> severity 976514 important
Bug #976514 [src:tinyarray] tinyarray: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.8 3.9" --test-pytest
--test-args=../../../test_tinyarray.py returned exit code 13
Severity set to
Processing commands for cont...@bugs.debian.org:
> severity 976523 important
Bug #976523 [src:spades] spades: FTBFS: jemalloc_internal.h:292:6: error:
#error "No LG_QUANTUM definition for architecture; specify via CPPFLAGS"
Severity set to 'important' from 'serious'
> thanks
Stopping processing h
Processing commands for cont...@bugs.debian.org:
> severity 976581 important
Bug #976581 {Done: Sebastian Ramacher } [src:siconos]
siconos: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && make -j1 test
"ARGS=-E 'COLLECTION|python_test_lcp|dr_iso1'" ARGS\+=-j1 returned exit code 2
Severit
Processing commands for cont...@bugs.debian.org:
> severity 976479 important
Bug #976479 [src:scrappie] scrappie: FTBFS: scrappie_matrix.h:5:14: fatal
error: immintrin.h: No such file or directory
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
> severity 976497 important
Bug #976497 [src:python-parasail] python-parasail: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping pro
Processing commands for cont...@bugs.debian.org:
> severity 976553 important
Bug #976553 [src:mojoshader] mojoshader: FTBFS: segfaults
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976553: https://bugs.debian.org/cgi-bi
Processing commands for cont...@bugs.debian.org:
> severity 976478 important
Bug #976478 [src:libecpint] libecpint: FTBFS: dh_auto_test: error: cd
obj-aarch64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> severity 976557 important
Bug #976557 [src:kafs-client] kafs-client: FTBFS: cc: error: unrecognized
command-line option ‘-m64’
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance
Processing commands for cont...@bugs.debian.org:
> severity 976469 important
Bug #976469 [src:haskell-xml-html-qq] haskell-xml-html-qq: FTBFS: tests failed
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976469: https://b
Processing commands for cont...@bugs.debian.org:
> severity 976492 important
Bug #976492 {Done: Stephen Kitt } [src:bochs] bochs: FTBFS on
arm64: ld: cannot represent machine `i386'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assist
Processing commands for cont...@bugs.debian.org:
> severity 976524 important
Bug #976524 [src:bmtk] bmtk: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
P
Processing commands for cont...@bugs.debian.org:
> severity 976474 important
Bug #976474 [src:bcachefs-tools] bcachefs-tools: FTBFS:
include/linux/log2.h:281:27: error: ‘PAGE_SHIFT’ undeclared (first use in this
function); did you mean ‘PAGE_SIZE’?
Severity set to 'important' from 'serious'
> th
Processing commands for cont...@bugs.debian.org:
> severity 976494 important
Bug #976494 [src:blastem] blastem: FTBFS on arm64: z80_to_x86.c:634:21: error:
invalid operands to binary - (have ‘code_ptr’ {aka ‘unsigned int *’} and
‘uint8_t *’ {aka ‘unsigned char *’})
Severity set to 'important' fr
Processing commands for cont...@bugs.debian.org:
> forcemerge 953285 976484
Bug #953285 [src:rust-mach-o-sys] rust-mach-o-sys fails on architectures with
unsigned char
Bug #953285 [src:rust-mach-o-sys] rust-mach-o-sys fails on architectures with
unsigned char
Marked as found in versions rust-mac
It was quite disappointing to see (or not see) the GUI/WM stop working
after a causal system update (not upGrade).
I was able to get the system somewhat back to normal by using the
NOUVEAU driver instead of NVIDIA. BTW, even that was kind of tricking
because the Nvidia driver blacklisted Nouveau
Processing commands for cont...@bugs.debian.org:
> severity 976473 important
Bug #976473 [src:r-cran-s2] r-cran-s2: FTBFS:
../inst/include/s2/third_party/absl/base/internal/unaligned_access.h:289:8:
error: ‘uint64’ does not name a type; did you mean ‘uint64_t’?
Severity set to 'important' from '
Processing control commands:
> reopen -1
Bug #968730 {Done: Andreas Tille } [libnifti2] libnifti2:
libniftiio.so.2 not provided
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer mark
control: reopen -1
control: notifxed -1 3.0.1-1
Hello, how can three different binaries provide the very same old -dev library?
what happens now is that apt gets the old real cruft binary -dev package, and
not the virtual provided one
(because it seems to have higher priority).
So the rebuilds
Processing commands for cont...@bugs.debian.org:
> reassign 976687 src:python-escript 5.5-5
Bug #976687 [src:python3-escript] python3-escript: mixing incompatible
libpython and libboost_python
Warning: Unknown package 'src:python3-escript'
Bug reassigned from package 'src:python3-escript' to 'src
Processing control commands:
> affects -1 python3-escript python3-escript-mpi
Bug #976687 [src:python3-escript] python3-escript: mixing incompatible
libpython and libboost_python
Warning: Unknown package 'src:python3-escript'
Added indication that 976687 affects python3-escript and python3-escrip
Processing control commands:
> affects -1 glom libglom-1.30-0
Bug #976686 [src:glom] glom: mixing incompatible libpython and libboost_python
Added indication that 976686 affects glom and libglom-1.30-0
--
976686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976686
Debian Bug Tracking System
Source: python3-escript
Version: 5.5-5
Severity: serious
Tags: bookworm sid
Control: affects -1 python3-escript python3-escript-mpi
$ objdump -p /usr/lib/python3-escript/esys/dudley/dudleycpp.so | grep python
/usr/lib/python3-escript/esys/dudley/dudleycpp.so: file format elf64-x86-64
NEEDED
Source: glom
Version: 1.30.4-6.1
Severity: serious
Tags: bookworm sid
Control: affects -1 glom libglom-1.30-0
$ objdump -p /usr/bin/glom | grep python
NEEDED libpython3.9.so.1.0
NEEDED libboost_python38.so.1.71.0
$
This is now no longer a problem for bullseye,
but
On 05/12/20 at 13:47 +0100, Lucas Nussbaum wrote:
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Does this imply that it was also tested and failed in bullseye? The log
is marked unstable, and the test failures in it are #976620, which is
probably unstable-only.
Your message dated Sun, 06 Dec 2020 22:32:08 +
with message-id
and subject line Bug#974063: fixed in postgresql-11 11.10-0+deb10u1
has caused the Debian Bug report #974063,
regarding postgresql-13: FTBFS: timetz test failure
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> retitle 954270 kmc: hangs at high cores count
Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out
Changed Bug title to 'kmc: hangs at high cores count' from 'kmc: arm64
autopkgtest time out'.
> thanks
Stopping processing here.
Please contact m
debcargo (and cargo) is out of date in Debian and needs to be updated. We had
been blocked on the FTP binary-NEW policy but there is some progress in that
area.
Alternatively you could use collapse_features to begin to update it, but I
personally do not approve of it and haven't been spending t
Your message dated Sun, 06 Dec 2020 21:19:09 +
with message-id
and subject line Bug#975410: fixed in sieve-connect 0.90-1.1
has caused the Debian Bug report #975410,
regarding src:sieve-connect: fails to migrate to testing for too long:
maintainer built arch:all binary
to be marked as done.
On 2020-12-07 05:36:58 +0900, Norbert Preining wrote:
> Hi,
>
> thanks for the report, but that is really a porter/builder box problem:
>
> > | LLVM ERROR: out of memory
>
> Seems the machine couldn't deal with the required amount ( which is
> considerable from my experience).
>
> I don't know
Processing commands for cont...@bugs.debian.org:
> affects 976573 pandas
Bug #976573 [python3-xlrd] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Added indication that 976573 affects pandas
> retitle 976573 xlrd: AttributeEr
Processing commands for cont...@bugs.debian.org:
> tags 901952 bullseye-ignore
Bug #901952 [tar] xdelta: expected from file
(/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.
Please contact me if you need assist
Control: tag -1 + confirmed
Control: tag -1 - unreproducible
Hi Paul,
Paul Gevers, on 2020-12-06 20:54:43 +0100:
> It recently started to time out on amd64 too, but not always [1]. And
> when we added armhf, that timed out too. The failures on amd64 that I
> checked were all on ci-worker13, which
Processing control commands:
> tag -1 + confirmed
Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out
Added tag(s) confirmed.
> tag -1 - unreproducible
Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out
Removed tag(s) unreproducible.
--
954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?
Your message dated Sun, 06 Dec 2020 21:00:11 +
with message-id
and subject line Bug#973634: fixed in mpich 3.4~b1-1
has caused the Debian Bug report #973634,
regarding mpich: d/copyright does not mention vis.js
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Sun, 06 Dec 2020 21:00:11 +
with message-id
and subject line Bug#956289: fixed in mpich 3.4~b1-1
has caused the Debian Bug report #956289,
regarding Problems identified in debian/copyright
to be marked as done.
This means that you claim that the problem has been dealt with.
Can BTS #957468 be closed?
--
Brian T. Smith
System Fabric Works
Senior Principal Engineer
bsm...@systemfabricworks.com
GPG Key: 0xB3C2C7B73BA3CD7F
Processing commands for cont...@bugs.debian.org:
> reassign 974093 src:ruby-httparty 0.18.1-1
Bug #974093 {Done: =?utf-8?q?C=C3=A9dric_Boutillier?= }
[src:ruby-httparty, src:ruby-gitlab] ruby-httparty breaks ruby-gitlab
autopkgtest: Gitlab::Client.create_merge_request_discussion posts the correc
Processing commands for cont...@bugs.debian.org:
> # OOPS. assigned to the FIXED version...
> notfound 975188 0.3.2-1
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-native-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~
Hi,
On Fri, 6 Nov 2020 03:28:53 +0100 Guillem Jover wrote:
> On Tue, 2020-11-03 at 19:32:03 +0100, Moritz Muehlenhoff wrote:
> > argyll is filed for removal from the archive (#966416), but
> > colord-sensor-argyll
> > depends on it.
>
> The RC bugs filed against argyll have all been fixed now.
Processing commands for cont...@bugs.debian.org:
> block 975929 by 976629
Bug #975929 [check-manifest] python-logfury: autopkgtest tries to use pip to
download and install code from the internet
975929 was not blocked by any bugs.
975929 was not blocking any bugs.
Added blocking bug(s) of 975929:
Hi,
thanks for the report, but that is really a porter/builder box problem:
> | LLVM ERROR: out of memory
Seems the machine couldn't deal with the required amount ( which is
considerable from my experience).
I don't know what **we** can do here ...
Best
Norbert
--
PREINING Norbert
Dear VOIP-team,
On Wed, 27 Mar 2019 19:47:03 + Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be do
Processing commands for cont...@bugs.debian.org:
> reassign 975188 src:rust-foreign-types-0.3 0.3.2-1
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-native-tls] rust-native-tls: FTBFS: build-dependency not installable:
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Bug reassigned from
@jim_p Is it possible for you to avoid putting all system information
and Xorg logs in every message?
It makes the thread very difficult to follow on the online bug tracker.
I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it
won't be my very last kernel version.
Hi Anibal,
On Sun, 21 Jun 2020 22:34:58 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Do you intent to fix this in unstable soon too? The freeze is getting
close and we'd like to have this fixed in bullseye.
Paul
OpenPGP_signa
Dear Laszlo,
On Wed, 27 Mar 2019 19:47:52 + Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done
Processing control commands:
> severity -1 serious
Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out
Severity set to 'serious' from 'important'
--
954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 957007 + ftbfs
Bug #957007 [src:arpack] arpack: ftbfs with GCC-10
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957007
Debian Bu
Processing commands for cont...@bugs.debian.org:
> tags 976573 - bullseye
Bug #976573 [src:pandas] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Removed tag(s) bullseye.
> reassign 976573 python3-xlrd
Bug #976573 [src:pandas
Processing control commands:
> tags 976218 fixed-upstream
Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of
check_ssl_cert
Added tag(s) fixed-upstream.
--
976218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976218
Debian Bug Tracking System
Contact ow...@bugs
Control: tags 976218 fixed-upstream
Paul Gevers wrote...
> So, let's reassign appropriately.
This was fixed¹ in upstream release 1.119.0, and I'll start preparing a
NMU now.
FWIW, upstream is already at version 1.124.0 while Debian unstable is at
1.98.0.
Christoph
¹
https://github.com/ma
Hi,
On 06/12/20 at 18:39 +, Rebecca N. Palmer wrote:
> On 05/12/20 at 13:47 +0100, Lucas Nussbaum wrote:
> > Tags: bullseye sid ftbfs
> > Usertags: ftbfs-20201205 ftbfs-bullseye
>
> Does this imply that it was also tested and failed in bullseye? The log is
> marked unstable, and the test fai
Processing control commands:
> severity -1 serious
Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, AttributeError:
'ElementTree' object has no attribute 'getiterator'
Severity set to 'serious' from 'normal'
> affects -1 pandas
Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, At
Processing commands for cont...@bugs.debian.org:
> forcemerge 972689 901148
Bug #972689 [timidity] Sound output is only working randomly
Bug #918522 [timidity] No sound with PulseAudio when an NVidia GPU is installed.
Severity set to 'important' from 'critical'
Severity set to 'important' from 'cr
Control: forwarded -1
https://github.com/jeffdaily/parasail-python/issues/56
Forwarded the issue upstream, hopefully we will have a fix soonish with
arm64 becoming more popular.
Your message dated Sun, 06 Dec 2020 18:52:11 +
with message-id
and subject line Bug#975527: fixed in python-furl 2.1.0-2
has caused the Debian Bug report #975527,
regarding python-furl fails autopkg tests with Python 3.9
to be marked as done.
This means that you claim that the problem has bee
Processing commands for cont...@bugs.debian.org:
> forwarded 976537 https://github.com/astropy/specutils/issues/737
Bug #976537 [src:specutils] specutils: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Set Bug forwarded-to-address to
Hello!
On 12/6/20 7:38 PM, Nilesh Patra wrote:
> I've no clue of where to even start debugging this. Any help/hints are
> welcome and highly appreciated.
My suggestion would be to report this issue upstream [1].
Since ARM is going to be more popular in the future with Apple switching
their all
Processing control commands:
> tags -1 help
Bug #976497 [src:python-parasail] python-parasail: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Ignoring request to alter tags of bug #976497 to the same tags previously set
--
976497: https:
Control: tags -1 help
Hi Debian Arm team,
I've no clue of where to even start debugging this. Any help/hints are welcome
and highly appreciated.
Thanks and regards
Nilesh
On Sat, 5 Dec 2020 13:51:16 +0100 Lucas Nussbaum wrote:
> Source: python-parasail
> Version: 1.2.1-1
> Severity: serious
Processing control commands:
> tags -1 help
Bug #976497 [src:python-parasail] python-parasail: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) help.
--
976497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976497
Debian B
Control: tags -1 help
Hi Debian Arm team,
I've no clue of where to even start debugging this. Any help/hints are welcome
and highly appreciated.
Thanks and regards
Nilesh
On Sat, 5 Dec 2020 13:51:16 +0100 Lucas Nussbaum wrote:
> Source: python-parasail
> Version: 1.2.1-1
> Severity: serious
Your message dated Sun, 06 Dec 2020 18:07:10 +
with message-id
and subject line Bug#959858: fixed in snort 2.9.15.1-4
has caused the Debian Bug report #959858,
regarding snort-doc: missing Breaks+Replaces: snort (<< 2.9.15)
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 06 Dec 2020 18:04:08 +
with message-id
and subject line Bug#976310: fixed in gitlab 13.4.6-3
has caused the Debian Bug report #976310,
regarding node-compression-webpack-plugin: TypeError: (0 ,
_schemaUtils.validate) is not a function
to be marked as done.
This means
Package: debdelta
Version: 0.65
Followup-For: Bug #962203
X-Debbugs-Cc: calumlikesapple...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I have created an attached a patch. It is also availible as merge request !2
in the salsa repository.
- -- System Information:
Debian Release: b
On Sun, 06 Dec 2020 18:26:44 +0100, Torsten Paul wrote:
> On 06.12.20 02:37, gregor herrmann wrote:
> > Joel Ray Holveck has prepared an NMU for lib3mf (versioned as
> > 1.8.1+ds-3.1) and I've uploaded it to DELAYED/7. Please feel free to
> > tell me if I should delay it longer.
> Thanks, for the
Your message dated Sun, 06 Dec 2020 17:48:34 +
with message-id
and subject line Bug#976492: fixed in bochs 2.6.11+dfsg-4
has caused the Debian Bug report #976492,
regarding bochs: FTBFS on arm64: ld: cannot represent machine `i386'
to be marked as done.
This means that you claim that the prob
Your message dated Sun, 06 Dec 2020 17:35:49 +
with message-id
and subject line Bug#973026: fixed in python-executing 0.5.3-1
has caused the Debian Bug report #973026,
regarding python-executing's autopkg tests fail with python3.9
to be marked as done.
This means that you claim that the probl
Processing control commands:
> severity -1 grave
Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use
is_alive() instead
Severity set to 'grave' from 'normal'
--
962203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962203
Debian Bug Tracking System
Contact ow...@bugs.deb
Processing commands for cont...@bugs.debian.org:
> forwarded 976270 https://tickets.puppetlabs.com/browse/FORGE-575
Bug #976270 [ruby-puppet-forge] ruby-puppet-forge: autopkgtest/ftbfs with
ruby-faraday-middleware 1.x
Set Bug forwarded-to-address to
'https://tickets.puppetlabs.com/browse/FORGE-5
Hi!
On 06.12.20 02:37, gregor herrmann wrote:
> Joel Ray Holveck has prepared an NMU for lib3mf (versioned as
> 1.8.1+ds-3.1) and I've uploaded it to DELAYED/7. Please feel free to
> tell me if I should delay it longer.
Thanks, for the NMU, that's great. I appreciate the help as
I'm still stuck w
Processing commands for cont...@bugs.debian.org:
> title 976590 a unit test fails in arm64
Unknown command or malformed arguments to command.
> severity 976590 important
Bug #976590 [src:nova] nova: FTBFS: make[1]: pyversions: No such file or
directory
Severity set to 'important' from 'serious'
>
Hi,
There's multiple ways how this could be fixed, probably one should be to
disable the failing unit test if not running on amd64. I'll open an
issue upstream for this, and see how it goes. In the mean while (ie:
before I get an answer from upstream), I'll downgrade this bug to important.
Cheers
Your message dated Sun, 06 Dec 2020 16:55:21 +
with message-id
and subject line Bug#976542: fixed in python-biopython 1.78+dfsg-4
has caused the Debian Bug report #976542,
regarding python-biopython: FTBFS: AssertionError: 0 != 24
to be marked as done.
This means that you claim that the probl
Your message dated Sun, 06 Dec 2020 17:35:01 +0100
with message-id <3b78c0280ad367aae469ee8fd77fe5aed155c256.ca...@gmail.com>
and subject line Closing : fixed package migrated to testing
has caused the Debian Bug report #973017,
regarding python-django-import-export 's autopkg tests are failing wit
Your message dated Sun, 06 Dec 2020 16:23:07 +
with message-id
and subject line Bug#976567: fixed in libhmsbeagle 3.1.2+dfsg-9
has caused the Debian Bug report #976567,
regarding libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no
arguments to ‘malloc’ that depend on a template pa
Your message dated Sun, 6 Dec 2020 17:14:18 +0100
with message-id <20201206161418.gt31...@an3as.eu>
and subject line Bug was closed by upload of xenium (0.0.2+ds-2)
has caused the Debian Bug report #976480,
regarding xenium: FTBFS: utils.hpp:80:4: error: #error "Unsupported compiler"
to be marked a
Your message dated Sun, 06 Dec 2020 16:03:35 +
with message-id
and subject line Bug#976656: fixed in chemical-structures 2.2.dfsg.0-18
has caused the Debian Bug report #976656,
regarding chemical-structures-data: missing Breaks+Replaces:
chemical-structures (<< 2.2.dfsg.0-16)
to be marked as
Package: debcargo
Version: 2.4.3-2+bw
Severity: grave
After the recent binnmu of debcargo. debcargo update
(after deleting the cache) gives.
Updating crates.io index
Something failed: failed to fetch `https://github.com/rust-lang/crates.io-index`
Caused by:
invalid version 0 on git_pr
Your message dated Sun, 06 Dec 2020 15:50:07 +
with message-id
and subject line Bug#976506: fixed in conda-package-handling 1.7.2-2
has caused the Debian Bug report #976506,
regarding conda-package-handling: FTBFS on arm64: dh_auto_test: error: pybuild
--test --test-pytest -i python{version}
Control: reassign -1 src:python3-defaults
Control: severity -1 important
We're working around that for now by not byte-compiling the problematic file in
python3-joblib.
Processing control commands:
> reassign -1 src:python3-defaults
Bug #954403 [python3-minimal] joblib: configuration error installing
python3-joblib
Bug #975517 [python3-minimal] joblib fails to install with Python 3.9
Bug reassigned from package 'python3-minimal' to 'src:python3-defaults'.
Bug re
Your message dated Sun, 6 Dec 2020 16:22:06 +0100
with message-id <94dd95f5-3691-686c-87eb-aa64127e5...@redhat.com>
and subject line Re: python-icecream's autopkg tests ar failing with python3.9
has caused the Debian Bug report #973030,
regarding python-icecream's autopkg tests ar failing with pyth
Package: chemical-structures-data
Version: 2.2.dfsg.0-16
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries t
Processing control commands:
> severity -1 important
Bug #976366 [systemd] Upgrade to 247 broke keyboard input on Wayland session
Severity set to 'important' from 'critical'
> tags -1 unreproducible
Bug #976366 [systemd] Upgrade to 247 broke keyboard input on Wayland session
Added tag(s) unreprodu
1 - 100 of 128 matches
Mail list logo
