Hi,
On 2022-10-04 08:51, Aurelien Jarno wrote:
> Hi
>
> On 2022-09-25 13:43, Aurelien Jarno wrote:
> > > Running a quick diff against old procinfo reveals that "flags" has the
> > > following new entries now:
> > >
> > > tsc_deadline_timer ssbd ibrs ibpb stibp bmi1 bmi2 md_clear flush_l1d
> > >
Your message dated Wed, 05 Oct 2022 04:06:10 +
with message-id
and subject line Bug#1021288: fixed in josm-installer 0.0.2+svn18515
has caused the Debian Bug report #1021288,
regarding josm-installer: FTBFS with flake8 errors
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tags -1 pending
Bug #1021288 [src:josm-installer] josm-installer: FTBFS with flake8 errors
Added tag(s) pending.
--
1021288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 pending
Thanks for reporting this issue.
On 10/5/22 02:12, Andreas Beckmann wrote:
./josm-installer.py:38:7: E275 missing whitespace after keyword
./josm-installer.py:130:7: E275 missing whitespace after keyword
This is fixed in git and a new upload will follow shortly.
Source: josm-installer
Version: 0.0.1+svn18515
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
josm-installer recently started to FTBFS.
A previous rebuild on August 4 still succeeded.
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
Source: prody
Version: 2.2.0+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=prody=i386=2.2.0%2Bdfsg-1=1664908079=0
...
==
ERROR: testCompressed (prody.tests.proteins.test_wwpdb.TestFTP)
Source: unifrac-tools
Version: 1.1.1-1
Severity: serious
unifrac-tools seems to be an unintentional hijack of src:unifrac,
which is also maintained by Debian Med and RFA (#996921).
Package name differences:
- libssu-tools -> unifrac-tools
- python3-unifrac -> none
Processing commands for cont...@bugs.debian.org:
> forwarded 1020445 https://github.com/numba/numba/issues/8489
Bug #1020445 [src:numba] numba: autopkgtest regression on ppc64el: inf != 0.625
Set Bug forwarded-to-address to 'https://github.com/numba/numba/issues/8489'.
> thanks
Stopping
Source: simgrid
Version: 3.32-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=simgrid=mipsel=3.32-1=1664920617=0
...
-- Checking for modules
'ns3-core>=3.28;ns3-csma;ns3-point-to-point;ns3-internet;ns3-network;ns3-applications;ns3-wifi'
-- No package 'ns3-core'
Your message dated Tue, 04 Oct 2022 20:40:38 +
with message-id
and subject line Bug#1020306: fixed in neurodebian 0.41.1+nmu1
has caused the Debian Bug report #1020306,
regarding src:neurodebian: fails to migrate to testing for too long: uploader
built arch:all binaries
to be marked as done.
Hi,
On 2022-10-04 19:44, debian-bug-rep...@p0358.net wrote:
> > Is there an easy way to unbrick a system affected by the issue? such as
> > a kernel-line option or a configuration file in /etc? I don't see how I
> > can set a GLIBC_TUNABLES environment variable for the whole system.
>
> I was
Processing commands for cont...@bugs.debian.org:
> tags 1021270 + upstream
Bug #1021270 [src:libmodbus] libmodbus: CVE-2022-0367
Added tag(s) upstream.
> found 1021270 3.1.6-2
Bug #1021270 [src:libmodbus] libmodbus: CVE-2022-0367
Marked as found in versions libmodbus/3.1.6-2.
> forwarded 1021270
Processing commands for cont...@bugs.debian.org:
> found 1019303 2.4.2-3
Bug #1019303 [roger-router] librm0: library mismatch between roger-router and
librm0
Marked as found in versions roger-router/2.4.2-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> severity 1021271 grave
Bug #1021271 [src:strongswan] strongswan: CVE-2022-40617
Bug #1021277 [src:strongswan] strongswan: CVE-2022-40617
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> forcemerge 1021271 1021277
Bug #1021271 [src:strongswan] strongswan: CVE-2022-40617
Bug #1021277 [src:strongswan] strongswan: CVE-2022-40617
Severity set to 'important' from 'grave'
Marked as found in versions strongswan/5.9.1-1+deb11u2,
Source: pngcheck
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for pngcheck.
CVE-2020-35511[0]:
| A global buffer overflow was discovered in pngcheck function in
| pngcheck-2.4.0(5 patches applied) via a crafted png file.
Source: snort
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for snort.
These all lack details, but all boil down to the fact Snort needs
to be updated:
CVE-2020-3315[0]:
| Multiple Cisco products are affected by a
Source: strongswan
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for strongswan.
CVE-2022-40617[0]:
https://www.strongswan.org/blog/2022/10/03/strongswan-vulnerability-(cve-2022-40617).html
Patch:
Source: python-opcua
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for python-opcua.
CVE-2022-25304[0]:
| All versions of package opcua; all versions of package asyncua are
| vulnerable to Denial of Service (DoS) due to a
Source: nomad
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for nomad.
CVE-2021-37218[0]:
| HashiCorp Nomad and Nomad Enterprise Raft RPC layer allows non-server
| agents with a valid certificate signed by the same CA to
Source: libmodbus
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for libmodbus.
CVE-2022-0367[0]:
| A heap-based buffer overflow flaw was found in libmodbus in function
| modbus_reply() in src/modbus.c.
Your message dated Tue, 04 Oct 2022 17:26:26 +
with message-id
and subject line Bug#1021065: Removed package(s) from unstable
has caused the Debian Bug report #1017014,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> severity -1 important
Bug #1021256 [src:gtkmm4.0] gtkmm4: autopkgtest failure: Failed to locate
“gtk-logo.webm” in any source directory
Severity set to 'important' from 'serious'
--
1021256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021256
Debian Bug
Processing commands for cont...@bugs.debian.org:
> severity 1021264 important
Bug #1021264 [src:haskell-hdf5] haskell-hdf5 FTBFS in unregistered builds:
unknown RTS option: -N
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Control: severity -1 important
Since gtkmm4.0 is new to Debian, a broken autopkgtest isn't a
regression and doesn't block migration to Testing.
I've fixed the one line seen in the autopkgtest failure, but…
We need to either port the minimal gtkmm app to gtkmm4 or drop it and
just use the
Your message dated Tue, 04 Oct 2022 17:23:44 +
with message-id
and subject line Bug#1021202: Removed package(s) from unstable
has caused the Debian Bug report #983913,
regarding puppet-master,puppet-master-passenger: depends on unavailable
puppet-server
to be marked as done.
This means that
Your message dated Tue, 04 Oct 2022 17:23:44 +
with message-id
and subject line Bug#1021202: Removed package(s) from unstable
has caused the Debian Bug report #1009643,
regarding Puppet: Fails to work with Ruby 3.0
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Oct 2022 17:23:44 +
with message-id
and subject line Bug#1021202: Removed package(s) from unstable
has caused the Debian Bug report #1006231,
regarding puppet: FTBFS with ruby 3.0: fileutils.rb:865:in `install': wrong
number of arguments (given 3, expected 2)
Processing control commands:
> forwarded -1 https://github.com/libgit2/git2go/pull/929
Bug #1021265 [golang-github-libgit2-git2go] golang-github-libgit2-git2go ftbfs
with libgit2 1.5
Set Bug forwarded-to-address to 'https://github.com/libgit2/git2go/pull/929'.
--
1021265:
Hello,
Is there an easy way to unbrick a system affected by the issue? such as
a kernel-line option or a configuration file in /etc? I don't see how I
can set a GLIBC_TUNABLES environment variable for the whole system.
Samuel
Package: golang-github-libgit2-git2go
Version: 33.0.9-2
Severity: serious
Control: forwarded -1 https://github.com/libgit2/git2go/pull/929
This is also seen in autopkgtest failure
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/golang-github-libgit2-git2go/26651971/log.gz
Upstream
Source: haskell-hdf5
Version: 1.8.10-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=haskell-hdf5=1.8.10-1
...
Linking dist-ghc/build/hdf5-test/hdf5-test ...
touch build-ghc-stamp
perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
-E
Is there an easy way to unbrick a system affected by the issue? such as
a kernel-line option or a configuration file in /etc? I don't see how I
can set a GLIBC_TUNABLES environment variable for the whole system.
I was trying during my testing to set such option globally somehow, but
failed,
Comments inline below
On Mon, 26 Sep 2022 08:26:56 + Winnie Yue wrote:
> Package: ndctl
> Version: 71.1-1
> Severity: serious
>
> For Debian 11.5 32 bit, I got below info:
>
> apt-cache search ndctl
>
> libndctl-dev - Development files for libndctl
>
> libndctl6 - Utility library for
Your message dated Tue, 04 Oct 2022 16:51:53 +
with message-id
and subject line Bug#1010578: fixed in osmo-mgw 1.10.0+dfsg1-1
has caused the Debian Bug report #1010578,
regarding osmo-mgw: FTBFS if systemd is in build environment
to be marked as done.
This means that you claim that the
Source: ruby-stackprof
Version: 0.2.21-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=ruby-stackprof=0.2.21-1
...
Finished in 0.379613s, 79.0278 runs/s, 237.0833 assertions/s.
1) Failure:
StackProfTest#test_raw [/<>/test/test_stackprof.rb:153]:
Expected
severity 1020298 serious
severity 1019488 serious
severity 1020299 serious
thanks
cu
Adrian
Processing commands for cont...@bugs.debian.org:
> severity 1020298 serious
Bug #1020298 [src:eclipse-platform-runtime] eclipse-platform-runtime: wrong
information in the manifest files
Severity set to 'serious' from 'important'
> severity 1019488 serious
Bug #1019488 [src:bouncycastle]
Your message dated Tue, 04 Oct 2022 14:39:34 +
with message-id
and subject line Bug#1015334: fixed in ruby-stackprof 0.2.21-1
has caused the Debian Bug report #1015334,
regarding ruby-stackprof: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim
Your message dated Tue, 04 Oct 2022 14:39:34 +
with message-id
and subject line Bug#994456: fixed in ruby-stackprof 0.2.21-1
has caused the Debian Bug report #994456,
regarding ruby-stackprof: flaky autopkgtests
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Oct 2022 14:39:11 +
with message-id
and subject line Bug#1017630: fixed in r-cran-insight 0.18.4+dfsg-2
has caused the Debian Bug report #1017630,
regarding r-cran-insight: autopkgtest regression on i386: times out
to be marked as done.
This means that you claim
Your message dated Tue, 04 Oct 2022 14:34:14 +
with message-id
and subject line Bug#1020818: fixed in abi-dumper 1.2-2
has caused the Debian Bug report #1020818,
regarding abi-dumper: abi-dumper 1.2 doesn't work with today's binaries
to be marked as done.
This means that you claim that the
On Tue, Oct 04, 2022 at 03:37:36PM +0300, Adrian Bunk wrote:
> I cannot reproduce this, but I can NMU to build with -O1 everywhere.
Thank you very much. I have just closed by RM bug.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Dear maintainer,
I've prepared an NMU for uim (versioned as 1:1.8.8-9.2) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru uim-1.8.8/debian/changelog uim-1.8.8/debian/changelog
--- uim-1.8.8/debian/changelog 2022-06-26 17:40:31.0 +0300
Your message dated Tue, 04 Oct 2022 12:34:07 +
with message-id
and subject line Bug#1004285: fixed in davical 1.1.11-1
has caused the Debian Bug report #1004285,
regarding davical: problems after upgrade to php 8, calendar clients reports
"500"
to be marked as done.
This means that you
On Tue, Oct 04, 2022 at 11:28:27AM +0300, Dmitry Shachnev wrote:
> Hi Adrian!
>
> On Mon, Oct 03, 2022 at 07:48:08PM +0300, Adrian Bunk wrote:
> > The workaround below fixes the build.
> >
> > I looked through the backtrace in gdb, but debugging a Scheme
> > interpreter is outside of what I am
Processing commands for cont...@bugs.debian.org:
> reassign 1020779 libcereal-dev 1.3.2+dfsg-2
Bug #1020779 [src:slic3r-prusa] slic3r-prusa: FTBFS on 32-bit arches
Bug reassigned from package 'src:slic3r-prusa' to 'libcereal-dev'.
No longer marked as found in versions slic3r-prusa/2.5.0+dfsg-1.
reassign 1020779 libcereal-dev 1.3.2+dfsg-2
thanks
From the build log in [1], it looks like the build error is:
CMake Warning at cmake/modules/Findcereal.cmake:6 (find_package):
Could not find a configuration file for package "cereal" that is compatible
with requested version "".
The
Source: gtkmm4.0
Version: 4.8.0-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtkmm4.0/26657367/log.gz
...
autopkgtest [03:40:13]: test build: [---
+ mktemp -d
+ WORKDIR=/tmp/tmp.aaoH7slRso
+ trap rm -rf /tmp/tmp.aaoH7slRso 0 INT QUIT ABRT PIPE
Your message dated Tue, 04 Oct 2022 11:18:57 +
with message-id
and subject line Bug#1005449: fixed in awl 0.63-1
has caused the Debian Bug report #1005449,
regarding awl: FTBFS: TypeError: implode(): Argument #2 ($array) must be of
type ?array, string given - in tests/myCalendarTest.php:61
Processing control commands:
> tag -1 - unreproducible
Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing
/usr/lib/llvm-15/bin/mlir-tblgen
Removed tag(s) unreproducible.
> severity -1 serious
Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing
Your message dated Tue, 04 Oct 2022 09:49:07 +
with message-id
and subject line Bug#1021238: fixed in firmware-ast 20140808-6
has caused the Debian Bug report #1021238,
regarding firmware-ast: missing B-D: xxd
to be marked as done.
This means that you claim that the problem has been dealt
Hi Adrian!
On Mon, Oct 03, 2022 at 07:48:08PM +0300, Adrian Bunk wrote:
> The workaround below fixes the build.
>
> I looked through the backtrace in gdb, but debugging a Scheme
> interpreter is outside of what I am feeling comfortable doing.
Thank you for the patch. Can you go ahead and upload
Source: firmware-ast
Version: 20140808-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source
vim-common no longer depends on xxd, causing firmware-ast to FTBFS:
dh_auto_build
make -j3 "INSTALL=install --strip-program=true"
make[1]: Entering directory
Processing commands for cont...@bugs.debian.org:
> found 1020258 1:28.1+1-4
Bug #1020258 [emacs] emacs: elpa-*: fails to install: libgccjit.so: error:
error invoking gcc driver
Marked as found in versions emacs/1:28.1+1-4.
> tags 1007127 + sid bookworm experimental
Bug #1007127 {Done: Gürkan
Hi
On 2022-09-25 13:43, Aurelien Jarno wrote:
> > Running a quick diff against old procinfo reveals that "flags" has the
> > following new entries now:
> >
> > tsc_deadline_timer ssbd ibrs ibpb stibp bmi1 bmi2 md_clear flush_l1d
> >
> > > it looks like that the BMI2
> > > instructions support
Processing commands for cont...@bugs.debian.org:
> found 1020776 1:7.1+dfsg-2~bpo11+2
Bug #1020776 [qemu-system-data] qemu-system-data in bullseye-backports is too
old
There is no source info for the package 'qemu-system-data' at version
'1:7.1+dfsg-2~bpo11+2' with architecture ''
Unable to
57 matches
Mail list logo
