Your message dated Wed, 15 Mar 2023 07:03:34 +0100
with message-id
and subject line Accepted libosip2 5.3.0-2.1 (source) into unstable
has caused the Debian Bug report #1021662,
regarding libosip2: CVE-2022-41550
to be marked as done.
This means that you claim that the problem has been dealt with
Processing commands for cont...@bugs.debian.org:
> tags 915072 + ftbfs
Bug #915072 [src:keysafe] keysafe: build-depends on many no longer available
libghc-*-dev versions
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915072: https://bugs.debi
Hi,
I am removing myself from the uploaders field/maintenance of tiledb-py. Feel
free to update it once tiledb is ready for migration. The repository
lives at python team namespace.
--
Best,
Nilesh
signature.asc
Description: PGP signature
Package: igdiscover
Version: 0.11-4
Severity: serious
Usertags: ftbfs-bookworm
Dear Maintainer,
igdiscover vendors just a /usr/bin/igdiscover with is supposed to be
nothing more than just a wrapper. The actual code is missing from the
binary package (i.e. the python files) effectively making igdi
Your message dated Wed, 15 Mar 2023 01:21:56 +
with message-id
and subject line Bug#1032893: Removed package(s) from unstable
has caused the Debian Bug report #997744,
regarding pt-websocket: FTBFS: go install: version is required when current
directory is not in a module
to be marked as done
Your message dated Wed, 15 Mar 2023 01:19:46 +
with message-id
and subject line Bug#1028349: Removed package(s) from unstable
has caused the Debian Bug report #1020055,
regarding tnetstring3: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.10 returned exit code 13
to be mar
Processing control commands:
> fixed -1 5.3.0-2.1
Bug #1021662 [src:libosip2] libosip2: CVE-2022-41550
The source 'libosip2' and version '5.3.0-2.1' do not appear to match any binary
packages
Marked as fixed in versions libosip2/5.3.0-2.1.
--
1021662: https://bugs.debian.org/cgi-bin/bugreport.c
Control: fixed -1 5.3.0-2.1
I have just uploaded a NMU to fix this. debdiff attached.diff -Nru libosip2-5.3.0/debian/changelog libosip2-5.3.0/debian/changelog
--- libosip2-5.3.0/debian/changelog 2022-03-08 23:51:47.0 +0100
+++ libosip2-5.3.0/debian/changelog 2023-03-15 01:04:10.00
Dear maintainers,
the patch for fenix-plugins in my last e-mail was missing a line
(copy'n'paste mistake). Sorry! Please find the updated patch attached
to this e-mail.
With this patch, I was able to successfully build fenix-plugins for armhf.
Best regards,
Thomas Uhle
04-update-configure
Package: tzdata-legacy
Version: 2022g-7exp1
Severity: serious
There was an error installing your package:
,
| Unpacking tzdata-legacy (2022g-7exp1) ...
| dpkg: error processing archive
/var/cache/apt/archives/tzdata-legacy_2022g-7exp1_all.deb (--unpack):
| trying to overwrite '/usr/share/zo
Your message dated Tue, 14 Mar 2023 21:19:49 +
with message-id
and subject line Bug#1032538: fixed in emacs 1:28.2+1-13
has caused the Debian Bug report #1032538,
regarding emacs: CVE-2023-27985 CVE-2023-27986
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Tue, 14 Mar 2023 14:04:19 -0700
with message-id <873567yrho@athena.silentflame.com>
and subject line Re: Bug#1031888: emacs-nox: bullseye-security update fails to
install on mips64el
has caused the Debian Bug report #1031888,
regarding emacs-nox: bullseye-security update fai
Processing control commands:
> severity -1 important
Bug #1032468 [file-roller] file-roller: does not work - no error messages
except on stderr (org.freedesktop.DBus.Error.ServiceUnknown)
Severity set to 'important' from 'grave'
> tags -1 + moreinfo unreproducible
Bug #1032468 [file-roller] file-
Control: severity -1 important
Control: tags -1 + moreinfo unreproducible
On Tue, 07 Mar 2023 at 17:00:57 +0100, Vincent Lefevre wrote:
> Justification: renders package unusable
It is not the case that file-roller is unusable. There must be something
specific to the system where you reproduced th
Source: gobject-introspection
Version: 1.76.0-1
Severity: serious
Tags: trixie sid experimental ftbfs
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/458
gobject-introspection fails to build in experimental on several Debian
release architectures. See the upstre
Your message dated Tue, 14 Mar 2023 16:19:18 +
with message-id
and subject line Bug#1032929: fixed in nginx 1.22.1-9
has caused the Debian Bug report #1032929,
regarding nginx-common: missing Breaks+Replaces: nginx (<< 1.22.1-8)
to be marked as done.
This means that you claim that the problem
Processing control commands:
> severity -1 wishlist
Bug #1032937 [systemd-resolved] systemd-resolved: Overwriting /etc/resolv.conf
with link to /run/systemd/resolve/stub-resolv.conf breaks install in chroot
Severity set to 'wishlist' from 'serious'
> tags -1 wontfix
Bug #1032937 [systemd-resolved
Control: severity -1 wishlist
Control: tags -1 wontfix
On Tue, 14 Mar 2023 15:05:20 +0100 Bastian Blank
wrote:
> Control: severity -1 serious
>
> Let's make this RC, as it breaks updates.
>
> The systemd-resolved package modifies a global config file
> /etc/resolv.conf. This breaks any name re
Processing control commands:
> block -1 by 1031909
Bug #960727 [python3-distutils] errors during upgrade
960727 was not blocked by any bugs.
960727 was not blocking any bugs.
Added blocking bug(s) of 960727: 1031909
--
960727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960727
Debian Bug T
Processing control commands:
> severity -1 serious
Bug #1032937 [systemd-resolved] systemd-resolved: Overwriting /etc/resolv.conf
with link to /run/systemd/resolve/stub-resolv.conf breaks install in chroot
Severity set to 'serious' from 'important'
--
1032937: https://bugs.debian.org/cgi-bin/bu
Processing commands for cont...@bugs.debian.org:
> fixed 1009035 0.4.0-1
Bug #1009035 [src:ruby-asciidoctor-include-ext] ruby-asciidoctor-include-ext:
CVE-2022-24803 - Command Injection vulnerability
Marked as fixed in versions ruby-asciidoctor-include-ext/0.4.0-1.
> thanks
Stopping processing he
Your message dated Tue, 14 Mar 2023 12:04:14 +
with message-id
and subject line Bug#1031965: fixed in pyodc 1.1.4-1
has caused the Debian Bug report #1031965,
regarding python3-pyodc-docs is empty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> reopen -1
Bug #1016903 {Done: Matthias Klose } [g++-12] tree-vectorize:
Wrong code at O2 level (-fno-tree-vectorize is working)
'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 th
Control: reopen -1
> the upstream fix went into 12.2.0-2.
Would be so kind as to demonstrate how ?
Here is what I see on my side:
% ssh barriere.debian.org
% sessionid=$(schroot -b -c sid_i386-dchroot)
% dd-schroot-cmd -c $sessionid apt-get update
% dd-schroot-cmd -c $sessionid apt-get upgrade
Processing control commands:
> severity -1 normal
Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new
pocl
Severity set to 'normal' from 'serious'
--
1031414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031414
Debian Bug Tracking System
Contact ow...@bugs.debian.
Followup-For: Bug #1031414
Control: severity -1 normal
This should have been addressed in pyopencl.
Andreas
Source: pynest2d
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
pynest2d/experimental started to FTBFS after some (transitive)
build-dependency has been upgraded. Most likely this is caused by cmake
3.25 (the last
Version: 12.2.0-2
the upstream fix went into 12.2.0-2. If the problem persists, then there's
probably another issue. Please file a separate issue, after testing both gcc-12
and gcc-13 from experimental.
Your message dated Tue, 14 Mar 2023 10:47:07 +0100
with message-id
and subject line closing again
has caused the Debian Bug report #1016903,
regarding tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is
working)
to be marked as done.
This means that you claim that the problem has been
Package: nginx-common
Version: 1.22.1-8
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 to overwrite other
Your message dated Tue, 14 Mar 2023 07:04:05 +
with message-id
and subject line Bug#1032517: fixed in nginx 1.22.1-8
has caused the Debian Bug report #1032517,
regarding nginx settings deleted on upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If
31 matches
Mail list logo
