On 10/08/2022 19:32, Nilesh Patra wrote:
Hi,
Sorry to bother you over this again, but would you have any idea?
I'd be OK with a workaround if you don't have the bandwidth at the moment, but
this
seems to come from coffee related modifications only.
Hi,
not enough time this week, I'll try nex
Processing commands for cont...@bugs.debian.org:
> forwarded 1016972 https://bugs.php.net/bug.php?id=81723
Bug #1016972 [src:php8.1] php8.1: CVE-2022-31627
Set Bug forwarded-to-address to 'https://bugs.php.net/bug.php?id=81723'.
> thanks
Stopping processing here.
Please contact me if you need ass
Processing commands for cont...@bugs.debian.org:
> forwarded 1016978 https://github.com/FRRouting/frr/issues/11698
Bug #1016978 [src:frr] frr: CVE-2022-37035
Set Bug forwarded-to-address to 'https://github.com/FRRouting/frr/issues/11698'.
> thanks
Stopping processing here.
Please contact me if yo
Processing commands for cont...@bugs.debian.org:
> tags 1016971 + upstream
Bug #1016971 [src:fava] fava: CVE-2022-2514 CVE-2022-2523 CVE-2022-2589
Added tag(s) upstream.
> tags 1016972 + upstream
Bug #1016972 [src:php8.1] php8.1: CVE-2022-31627
Added tag(s) upstream.
> tags 1016974 + upstream
Bug
Your message dated Thu, 11 Aug 2022 00:48:59 +
with message-id
and subject line Bug#1016996: fixed in libnl3 3.7.0-0.2
has caused the Debian Bug report #1016996,
regarding libnl-3-200-udeb: uninstallable, depends on non-udeb sgml-base
to be marked as done.
This means that you claim that the p
Cyril Brulebois (2022-08-11):
> This breaks d-i builds, (at least) via libnl udebs picking up a
> dependency on sgml-base, which doesn't exist in a udeb context.
For completeness, I've just uploaded a workaround for src:libnl3 (see
https://bugs.debian.org/1016996 for details), so that particular
Package: libnl-3-200-udeb
Version: 3.7.0-0.1
Severity: grave
Tags: d-i patch
Justification: renders package unusable
X-Debbugs-Cc: Matthieu Baerts , Adam Borowski
, debian-b...@lists.debian.org
Hi Matthieu, hi Adam,
The set of packages you uploaded contains uninstallable udebs, as they
depend on
Your message dated Wed, 10 Aug 2022 22:49:16 +
with message-id
and subject line Bug#1016740: fixed in golang-github-cli-go-gh
0.0.3+git20220623.91ca4ef-2
has caused the Debian Bug report #1016740,
regarding golang-github-cli-go-gh: autopkgtest regression:
TestGQLClientDoWithContext/http_fail
Processing control commands:
> severity -1 serious
Bug #1015263 [debhelper] libidn2-0: Depends sgml-base
Severity set to 'serious' from 'normal'
--
1015263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #1016740 [src:golang-github-cli-go-gh] golang-github-cli-go-gh: autopkgtest
regression: TestGQLClientDoWithContext/http_fail_request_timed_out
Added tag(s) pending.
--
1016740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016740
Debian Bug
Control: tag -1 pending
Hello,
Bug #1016740 in golang-github-cli-go-gh 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:
https://salsa.debian.org/go-team/packages/golang-github-cli-go-gh/
Hi Adrian,
On Fri, 27 Aug 2021 13:32:22 +0300 Adrian Bunk wrote:
> Source: tootle
> Version: 1.0-alpha2-1
> Severity: serious
> Tags: ftbfs bookworm sid
> ...
> ../../src/Services/Network.vala:69.19-69.40: error: The name `get_phrase' does
not exist in the context of `Soup.Status' (libsoup-2.4)
Your message dated Thu, 11 Aug 2022 00:19:48 +0200
with message-id
<2b228a503f1ddaa163a5a70bf0d9f29904a0a05b.ca...@fortysixandtwo.eu>
and subject line Re: tootle FTBFS: error: The name `get_phrase' does not exist
in the context of `Soup.Status'
has caused the Debian Bug report #993088,
regarding
Your message dated Wed, 10 Aug 2022 21:55:10 +
with message-id
and subject line Bug#1016965: fixed in gitlab 15.1.4+ds1-1
has caused the Debian Bug report #1016965,
regarding gitlab upgrading to 15.1.3 fails with
ActiveRecord::DangerousAttributeError: gitlab_schema is defined by Active Record
Your message dated Wed, 10 Aug 2022 21:49:17 +
with message-id
and subject line Bug#1012898: fixed in assimp 5.2.4~ds0-1.1
has caused the Debian Bug report #1012898,
regarding assimp: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Wed, 10 Aug 2022 21:05:00 +
with message-id
and subject line Bug#1014003: fixed in iwyu 8.18-2
has caused the Debian Bug report #1014003,
regarding iwyu 0.18 requires clang-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Package: manpages-fr
Version: 4.15.0-3
Severity: grave
Justification: renders package unusable
manpages-fr 4.15.0-3 cannot be installed:
Unpacking manpages-fr (4.15.0-3) over (4.14.0-4) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-n3cIma/18-manpages-fr_4.15.0-3_all.deb (--unpack):
t
Hi,
On Sun, 10 Apr 2022 at 22:04, Moritz Mühlenhoff wrote:
>
> Revisiting this two years later; I really think k3d should be removed now?
> Nothing changed upstream and at this point it's uninstallable in unstable
> for many other libraries besides Python 2:
>
> -
> The follow
Processing commands for cont...@bugs.debian.org:
> severity 1016983 normal
Bug #1016983 [src:k3d] Should k3d be removed?
Severity set to 'normal' from 'serious'
> reassign 1016983 ftp.debian.org
Bug #1016983 [src:k3d] Should k3d be removed?
Bug reassigned from package 'src:k3d' to 'ftp.debian.org'
Hi Moritz,
On Wed, 10 Aug 2022 at 22:33, Moritz Muehlenhoff wrote:
>
> Source: k3d
> Version: 0.8.0.6-8
> Severity: serious
>
> Your package came up as a candidate for removal from Debian:
>
> - Python 2 will finally be removed in Bookworm and there's no
> upstream porting activity
> - Last uploa
Source: pd-py
Version: 0.2.2+git20170625.1.88fc77a-2
Severity: serious
Your package came up as a candidate for removal from Debian:
- Still depends on Python 2, which is finally being removed in Bookworm
- Last upload in 2018
If you disagree and want to continue to maintain this package,
please j
Source: nautilus-dropbox
Version: 2019.02.14-1
Severity: serious
Tags: bookworm sid
Forwarded: https://github.com/dropbox/nautilus-dropbox/issues/101
nautilus-dropbox doesn't build with nautilus 43. nautilus 43 has
switched to GTK4 and its API has received significant changes.
nautilus-dropbox wil
Source: k3d
Version: 0.8.0.6-8
Severity: serious
Your package came up as a candidate for removal from Debian:
- Python 2 will finally be removed in Bookworm and there's no
upstream porting activity
- Last upload four years ago
- Multiple other FTBFS issue
If you disagree and want to continue to
Processing control commands:
> forwarded -1 https://github.com/intel/media-driver/issues/1468
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error:
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has
type ‘uint64_t’
Set Bug forwarded-to-address
Control: forwarded -1 https://github.com/intel/media-driver/issues/1468
Control: tags -1 upstream
On 2022-08-10 21:13:47 +0100, Simon McVittie wrote:
> Control: tags -1 - patch
>
> On Wed, 10 Aug 2022 at 20:55:44 +0100, Simon McVittie wrote:
> > Yes, that seems to work.
>
> Sorry, no, that chang
Processing commands for cont...@bugs.debian.org:
> severity 1014933 important
Bug #1014933 [src:gnome-user-share] gnome-user-share: needs to be ported to gtk4
Severity set to 'important' from 'serious'
> retitle 1014933 gnome-user-share: Drop nautilus extension
Bug #1014933 [src:gnome-user-share]
Source: rails
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for rails.
CVE-2022-2[0]:
| A XSS Vulnerability in Action View tag helpers >= 5.2.0 and <
| 5.2.0 which would allow an attacker to inject content if able to
| con
Processing control commands:
> tags -1 - patch
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error:
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has
type ‘uint64_t’
Removed tag(s) patch.
--
1016953: https://bugs.debian.org/cgi-bin/bugrepo
Control: tags -1 - patch
On Wed, 10 Aug 2022 at 20:55:44 +0100, Simon McVittie wrote:
> Yes, that seems to work.
Sorry, no, that change is not sufficient. I also get:
In file included from
/<>/media_common/agnostic/common/os/mos_os.h:31,
from
/<>/media_driver/agnostic/common/o
Source: connman
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for connman.
CVE-2022-32292[0]:
| In ConnMan through 1.41, remote attackers able to send HTTP requests
| to the gweb component are able to exploit a heap-based b
Source: frr
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for frr.
CVE-2022-37035[0]:
| An issue was discovered in bgpd in FRRouting (FRR) 8.3. In
| bgp_notify_send_with_data() and bgp_process_packet() in bgp_packet.c,
| there
Source: sofia-sip
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for sofia-sip.
CVE-2022-31001[0]:
| Sofia-SIP is an open-source Session Initiation Protocol (SIP) User-
| Agent library. Prior to version 1.13.8, an attacker c
Source: php8.1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for php8.1.
It's specific to 8.1.x
CVE-2022-31627[0]:
| In PHP versions 8.1.x below 8.1.8, when fileinfo functions, such as
| finfo_buffer, due to incorrect patch a
Control: tags -1 + patch
On Wed, 10 Aug 2022 at 15:07:09 +0100, Simon McVittie wrote:
> The solution might be as simple as including or ,
> and using "%" PRIu64 instead of "%lu".
Yes, that seems to work.
smcv
From: Simon McVittie
Date: Wed, 10 Aug 2022 14:49:50 +0100
Subject: media_softlet
Processing control commands:
> tags -1 + patch
Bug #1016953 [src:intel-media-driver] intel-media-driver: FTBFS on i386: error:
format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has
type ‘uint64_t’
Added tag(s) patch.
--
1016953: https://bugs.debian.org/cgi-bin/bugreport
Your message dated Wed, 10 Aug 2022 18:49:27 +
with message-id
and subject line Bug#1013939: fixed in python-xarray 2022.06.0-2
has caused the Debian Bug report #1013939,
regarding python-xarray: autopkgtest regression: Left and right DataArray
objects are not close
to be marked as done.
Thi
Your message dated Wed, 10 Aug 2022 18:04:50 +
with message-id
and subject line Bug#1016574: fixed in adduser 3.126
has caused the Debian Bug report #1016574,
regarding adduser: dpkg conffile prompt for adduser.conf even though unmodified
to be marked as done.
This means that you claim that t
Processing commands for cont...@bugs.debian.org:
> tags 937085 + patch
Bug #937085 [src:mozilla-devscripts] mozilla-devscripts: Python2 removal in
sid/bullseye
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937085: https://bugs.debian.org/cgi
Hi,
Sorry to bother you over this again, but would you have any idea?
I'd be OK with a workaround if you don't have the bandwidth at the moment, but
this
seems to come from coffee related modifications only.
On Sun, 7 Aug 2022 11:42:45 +0530 Nilesh Patra wrote:
> On 8/7/22 11:04 AM, Yadd wrote:
Source: u-boot
Version: 2022.07+dfsg-1
Severity: serious
X-Debbugs-Cc: Vagrant Cascadian
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please consider testing and
reporting the status:
https://wiki.debian.org/U-boot/Status
live w
Control: severity 1012996 important
On 2022-07-22, Vagrant Cascadian wrote:
> Looks like mes 0.24 test suite failed with GCC-12?
>
> I have not yet tried to reproduce it myself, but this is a bigger issue
> now that GCC-12 is the default compiler in Debian.
Yup, definitely fails with gcc-12.
I'v
Processing control commands:
> severity 1012996 important
Bug #1012996 [src:mes] mes: ftbfs with GCC-12
Severity set to 'important' from 'serious'
--
1012996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: nautilus-python
Severity: serious
Version: 1.2.3-3.1
Forwarded: https://gitlab.gnome.org/GNOME/nautilus-python/-/merge_requests/9
nautilus-python doesn't work with nautilus 43. Sadly, nautilus-python
looks unmaintained upstream so it's unclear when this issue will be
resolved.
nautilus 43
Processing control commands:
> tags -1 fixed-upstream
Bug #1016224 [src:binutils-z80] binutils-z80: FTBFS: stdlib.h:134:10: error:
argument 1 is null but the corresponding size argument 3 value is [128,
9223372036854775807] [-Werror=nonnull]
Added tag(s) fixed-upstream.
--
1016224: https://bug
Control: tags -1 fixed-upstream
On Fri, Jul 29, 2022 at 06:20:14PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> > In function ‘mbstowcs’,
> > inlined from ‘read_symbol_name’ at read.c:1670:11:
> > /usr/include/x86_64-linux
Your message dated Wed, 10 Aug 2022 14:37:37 +
with message-id
and subject line Bug#1014488: fixed in scapy 2.4.4-5
has caused the Debian Bug report #1014488,
regarding scapy: flaky autopkgtest: No such file or directory: 'isotpsend'
to be marked as done.
This means that you claim that the pr
Source: intel-media-driver
Version: 22.5.1+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
intel-media-driver failed to build on i386, breaking multiarch
co-installation of amd64 and i386 driver libraries.
https://buildd.debian.
Your message dated Wed, 10 Aug 2022 15:30:26 +0200
with message-id
and subject line jekyll: FTBFS: ERROR: Test "ruby3.0" failed.
has caused the Debian Bug report #998499,
regarding jekyll: FTBFS: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim that the problem has b
Source: intel-compute-runtime
Version: 22.14.22890-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
intel-compute-runtime started to FTBFS when GCC 12 was made the default
compiler:
In file included from /usr/include/c++/12/string:50,
Your message dated Wed, 10 Aug 2022 13:53:17 +0200
with message-id <20220810115317.7snwni64u5mp3...@gpm.stappers.nl>
and subject line Avoiding removal from testing
has caused the Debian Bug report #1012999,
regarding msc-generator: ftbfs with GCC-12
to be marked as done.
This means that you claim
Processing control commands:
> notfound -1 8.1-2
Bug #1012999 [src:msc-generator] msc-generator: ftbfs with GCC-12
Ignoring request to alter found versions of bug #1012999 to the same values
previously set
--
1012999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012999
Debian Bug Tracking
Processing control commands:
> notfound -1 8.1-2
Bug #1012999 [src:msc-generator] msc-generator: ftbfs with GCC-12
Ignoring request to alter found versions of bug #1012999 to the same values
previously set
--
1012999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012999
Debian Bug Tracking
Control: notfound -1 8.1-2
Hi,
This e-mail is (an attempt) to prevent
that msc-generator gets removed from testing.
Originally was the bugreport serverity normal
and had the request "leave it to us".
Later became the serverity "serious"
The "leave it us" is still a good thing.
Yes, I appricia
Processing commands for cont...@bugs.debian.org:
> found 1010358 40.1+dfsg-1
Bug #1010358 [ugene] ugene: Fix for non-constant SIGSTKSZ
Marked as found in versions ugene/40.1+dfsg-1.
> severity 1010358 serious
Bug #1010358 [ugene] ugene: Fix for non-constant SIGSTKSZ
Severity set to 'serious' from
On Wed, 6 Jul 2022 21:42:22 +0200 Paul Gevers wrote:
>
> I looked at the results of the autopkgtest of you package on arm64
> because it was showing up as a regression for the upload of openssl.
> I noticed that the test regularly fails and I saw failures on other
> architectures too, even in s
Your message dated Wed, 10 Aug 2022 10:34:21 +
with message-id
and subject line Bug#1016540: fixed in wmanager 0.3.1-1
has caused the Debian Bug report #1016540,
regarding wmanager: FTBFS / autopkgtest regression with glibc 2.34
to be marked as done.
This means that you claim that the problem
On Wed, Aug 10, 2022 at 08:06:29AM +0200, Paul Gevers wrote:
> I looked at the results of the autopkgtest of you package because it was
> showing up on our page for long running tests on s390x. I noticed that the
> test always fails on s390x with an autopkgtest timeout. Your package
> regressed on
Your message dated Wed, 10 Aug 2022 09:09:55 +
with message-id
and subject line Bug#1016942: fixed in ptl 2.3.3-2
has caused the Debian Bug report #1016942,
regarding ptl: autopkgtest regression: ‘strlen’ was not declared in this scope
to be marked as done.
This means that you claim that the
Your message dated Wed, 10 Aug 2022 07:34:16 +
with message-id
and subject line Bug#1012943: fixed in herbstluftwm 0.9.5-2
has caused the Debian Bug report #1012943,
regarding herbstluftwm: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
On Wed, Aug 10, 2022 at 05:05:12PM +1000, Craig Small wrote:
> > Do you have capacity to prepare updates for bullseye?
> >
> Yes, see attached debdiff for review. It's just those two patches.
Looks good, thanks! Please upload to security-master.
Cheers,
Moritz
Source: ptl
Version: 2.3.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of ptl started to fail.
Paul
https://ci.debian.net/packages/p/ptl/
https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/
On Sun, 7 Aug 2022 at 23:29, Salvatore Bonaccorso wrote:
> Did you got confirmation from upstream back if those are the only two
> needed ones?
>
I got no message at all. However, these are the only two that mention the
people that found the bug and fixed it (two sets of people).
> Do you have
Source: phyml
Version: 3:3.3.20200621-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package because it was
showing up as a regression for the upload of glibc [0]. I noticed that
the test regularly fail
63 matches
Mail list logo
