Your message dated Sat, 17 Dec 2022 07:49:06 +
with message-id
and subject line Bug#1025024: fixed in python-boto 2.49.0-4.1
has caused the Debian Bug report #1025024,
regarding python-boto: (autopkgtest) needs update for python3.11: Cannot spec a
Mock object
to be marked as done.
This means
Your message dated Sat, 17 Dec 2022 07:34:02 +
with message-id
and subject line Bug#1023290: fixed in golang-raven-go 0.2.0+ds2-1
has caused the Debian Bug report #1023290,
regarding golang-raven-go: Include outdated copy of CA bundles
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1023290 [src:golang-raven-go] golang-raven-go: Include outdated copy of CA
bundles
Added tag(s) pending.
--
1023290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: tag -1 pending
Hello,
Bug #1023290 in golang-raven-go 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-raven-go/-/commit/797ae7a
Processing control commands:
> tags 1026155 + patch
Bug #1026155 [python3-trio] python3-trio: MultiError implementation conflicts
with BaseExceptionGroup backport in Python 3.10
Added tag(s) patch.
> tags 1026155 + pending
Bug #1026155 [python3-trio] python3-trio: MultiError implementation confli
Hi,
On Sun, 8 May 2022 20:59:08 -0300 Antonio Terceiro
wrote:
The ruby-bootsnap test suite hangs forever on ppc64el. This has been
reported upstream at the link above, and happens on both the version in
testing and the one in unstable.
There have been several successful builds since this bug
Processing control commands:
> found -1 12.2.0-10
Bug #1026245 [gm2-12-doc,gm2-13-doc] gm2-12-doc,gm2-13-doc: ships unversioned
/usr/share/info/gm2.info.gz
There is no source info for the package 'gm2-13-doc' at version '12.2.0-10'
with architecture ''
Marked as found in versions gcc-12/12.2.0-1
Package: gm2-12-doc,gm2-13-doc
Severity: serious
Control: found -1 12.2.0-10
Control: found -1 13-20221214-1
Hi,
there is a file conflict between gm2-12-doc and gm2-13-doc:
Preparing to unpack .../gm2-13-doc_13-20221214-1_all.deb ...
Unpacking gm2-13-doc (13-20221214-1) ...
dpkg: error pro
Processing control commands:
> reassign -1 python3-openssl
Bug #1026241 [python3-cryptography] [python3-cryptography] new version breaks
deluge
Bug reassigned from package 'python3-cryptography' to 'python3-openssl'.
No longer marked as found in versions python-cryptography/38.0.4-1.
Ignoring req
Downgrading python3-cryptography from 38.0.4-1 to 3.4.8-2 is a
temporary workaround.
Package: deluge
Version: 2.0.3-3.2
Severity: grave
Worked yesterday, now won't start.
Loading in a terminal reveals the following output:
Traceback (most recent call last):
File "/usr/bin/deluge", line 33, in
sys.exit(load_entry_point('deluge==2.0.3', 'gui_scripts', 'deluge')())
File "/
Processing control commands:
> block 1026137 by 1026139
Bug #1026137 [src:gobgp] gobgp: switch B-D to
golang-github-golang-protobuf-1-5-dev
1026137 was not blocked by any bugs.
1026137 was not blocking any bugs.
Added blocking bug(s) of 1026137: 1026139
--
1026137: https://bugs.debian.org/cgi-b
Control: block 1026137 by 1026139
Updating the B-D to golang-github-golang-protobuf-1-5-dev conflicts
with golang-github-golang-protobuf-1-3-dev that is pulled in by the
version of golang-google-grpc-dev in experimental or one of its
dependencies. Once that's resolved it should be pretty straigh
If the i915 dri driver is present gnome-shell is using the DRM platform
(not the Wayland platform?) with this driver.
If i915 is not present gnome-shell uses the DRM platform with the
kms_swrast-driver!
I did not see this with the lsof-command, because the name of the
"zink"-driver was
shown whic
Your message dated Fri, 16 Dec 2022 21:34:31 +
with message-id
and subject line Bug#1023765: fixed in ruby-asciidoctor-pdf 2.3.4-1
has caused the Debian Bug report #1023765,
regarding ruby-asciidoctor-pdf: autopkgtest needs update for new version of
ruby-prawn-icon: Could not find 'prawn-icon
Your message dated Fri, 16 Dec 2022 19:23:19 +
with message-id
and subject line Bug#1025202: fixed in gscan2pdf 2.13.1-1
has caused the Debian Bug report #1025202,
regarding gscan2pdf: autopkgtest regression: Can't open
scanners/Brother_DCP-7025
to be marked as done.
This means that you clai
This would violate POLA and break, among other things already noted, things
like fingerd, which wants to run with least-privilege but still access
.plan and .project files.
Security is a process and requires conscious thought by an administrator,
and default permissions on home directories are no
Package: efibootguard
Version: 0.12-2
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 p
Processing commands for cont...@bugs.debian.org:
> forwarded 1026088 https://github.com/linux-rdma/rdma-core/pull/1285
Bug #1026088 [src:rdma-core] rdma-core: add mips64* to COHERENT_DMA_ARCHS
Set Bug forwarded-to-address to
'https://github.com/linux-rdma/rdma-core/pull/1285'.
> thanks
Stopping p
* Sébastien Villemot [2022-12-16 16:26]:
In the current system, in which the BLAS and LAPACK implementation are
decided through the alternatives system, it’s not possible to solve the
problem through versioned provides. Because even if the dependency on
the versioned provides is satisfied, this
Processing control commands:
> found -1 1.0.5-3
Bug #999724 {Done: Mohammed Bilal }
[src:ruby-omniauth-salesforce] ruby-omniauth-salesforce: FTBFS with
ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in
activate_de
Followup-For: Bug #999724
Control: found -1 1.0.5-3
The version in sid now fails with
Could not find 'omniauth' (~> 1.0) - did find: [omniauth-2.1.0]
and the version in experimental fails with
Could not find 'omniauth-oauth2' (~> 1.7.1) - did find:
[omniauth-oauth2-1.8.0]
Andreas
Package: vagrant
Version: 2.2.19+dfsg-2
Severity: serious
Hi!
Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable
in Debian sid. I assume this will require packaging a new upstream
release to support the new virtualbox version 7.0.x series.
Thanks,
Guillem
Your message dated Fri, 16 Dec 2022 16:49:58 +
with message-id
and subject line Bug#1023341: fixed in khal 1:0.10.5-1
has caused the Debian Bug report #1023341,
regarding Fails to add any event due to too new python3-tzlocal
to be marked as done.
This means that you claim that the problem has
Source: golang-github-google-cel-spec
Version: 0.5.1-1
Severity: serious
golang-github-google-cel-spec/experimental has a
B-D: golang-goprotobuf-dev (>= 1.4.3~)
which is no longer available but has been superseded by
golang-github-golang-protobuf-1-5-dev.
Andreas
Processing control commands:
> forcemerge 1025838 -1
Bug #1025838 {Done: Pierre Gruet } [src:libreflectasm-java]
libreflectasm-java: build-depends on dropped package
Bug #1025838 {Done: Pierre Gruet } [src:libreflectasm-java]
libreflectasm-java: build-depends on dropped package
Added tag(s) ftbf
Control: forcemerge 1025838 -1
Hello,
This is the same as #1025838, which version 1.11.9+dfsg-3 properly closes.
Best,
--
Pierre
OpenPGP_signature
Description: OpenPGP digital signature
Source: golang-google-genproto
Version: 0.0~git20210726.e7812ac-1~exp0
Severity: serious
golang-google-genproto/experimental has a
B-D: golang-goprotobuf-dev (>= 1.4.1~)
which is no longer available but has been superseded by
golang-github-golang-protobuf-1-5-dev.
Andreas
Source: rust-sequoia-octopus-librnp
Version: 1.4.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
rust-sequoia-octopus-librnp/experimental has a no longer satisfiable
Build-Depends: librust-libgit2-sys-0.12+default-dev
librust-libgit2-sys-dev now provides (among o
Processing commands for cont...@bugs.debian.org:
> fixed 1013129 4.18.0-1
Bug #1013129 {Done: Yves-Alexis Perez } [src:exo] exo:
CVE-2022-32278
Marked as fixed in versions exo/4.18.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013129: https://bugs.debian.
Le vendredi 16 décembre 2022 à 13:47 +0100, Jochen Sprickerhof a
écrit :
> Hi Sébastien,
>
> * Sébastien Villemot [2022-12-16 10:30]:
> > Le jeudi 15 décembre 2022 à 21:16 +0100, Paul Gevers a écrit :
> > > On 13-12-2022 21:59, Sébastien Villemot wrote:
> > > > The problem is that atlas needs to
Your message dated Fri, 16 Dec 2022 15:20:40 +
with message-id
and subject line Bug#1026216: fixed in pkgconf 1.8.0-12
has caused the Debian Bug report #1026216,
regarding pkg-conf: breaking build with latest m4 fixes
to be marked as done.
This means that you claim that the problem has been d
Hi,
On Fri, 16 Dec 2022, at 15:12, Gianfranco Costamagna wrote:
> Source: pkgconf
> Version: 1.8.0-11
> Severity: serious
> Forwarded: https://github.com/pkgconf/pkgconf/issues/260
>
> Hello, after the change in
> https://github.com/pkgconf/pkgconf/commit/8d9d3de6eb8f0ffdbb859fce79cff89038e513c4
On Fri, Dec 16, 2022 at 04:14:56PM +0300, Michael Tokarev wrote:
> On Fri, 16 Dec 2022 11:50:18 + debian user wrote:
> > Package: login
> > Version: 1:4.13+dfsg1-1
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> > X-Debbugs-Cc: r...@localhost.lan, Debian Security
Source: pkgconf
Version: 1.8.0-11
Severity: serious
Forwarded: https://github.com/pkgconf/pkgconf/issues/260
Hello, after the change in
https://github.com/pkgconf/pkgconf/commit/8d9d3de6eb8f0ffdbb859fce79cff89038e513c4
The pkg-config automake module is broken if the pkg-config is called with
m
Processing commands for cont...@bugs.debian.org:
> tags 1024313 + fixed
Bug #1024313 {Done: Dima Kogan } [src:amgcl] amgcl: b-d on
python3-all-dev, but not built for all supported Python3 versions
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Fri, 16 Dec 2022 11:50:18 + debian user wrote:
Package: login
Version: 1:4.13+dfsg1-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: r...@localhost.lan, Debian Security Team
Dear Maintainer,
please uncomment the line in /etc/login.defs that currently sa
Processing commands for cont...@bugs.debian.org:
> block 937049 with 1026215
Bug #937049 [src:mini-buildd] mini-buildd: Python2 removal in sid/bullseye
937049 was not blocked by any bugs.
937049 was blocking: 936296 937579 937580 937684 937691 937695 937870 938065
938068 938168 938234 938235 9385
Hi Sébastien,
* Sébastien Villemot [2022-12-16 10:30]:
Le jeudi 15 décembre 2022 à 21:16 +0100, Paul Gevers a écrit :
On 13-12-2022 21:59, Sébastien Villemot wrote:
> The problem is that atlas needs to be recompiled against lapack 3.11.0.
> Which has been done in atlas 3.10.3-13. But atlas its
Package: login
Version: 1:4.13+dfsg1-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: r...@localhost.lan, Debian Security Team
Dear Maintainer,
please uncomment the line in /etc/login.defs that currently says:
#HOME_MODE 0700
to say:
HOME_MODE 0700
Your message dated Fri, 16 Dec 2022 11:35:33 +
with message-id
and subject line Bug#1025121: fixed in python-stack-data 0.6.2-1
has caused the Debian Bug report #1025121,
regarding python-stack-data: (autopkgtest) needs update for python3.11:
AssertionError
to be marked as done.
This means t
Processing commands for cont...@bugs.debian.org:
> affects 1026207 - src:pytest
Bug #1026207 [src:python-ase] python-ase: autopkgtest regression because test
functions return values
Removed indication that 1026207 affects src:pytest
> affects 1026209 - src:pytest
Bug #1026209 [python3-pytest-asyn
Processing control commands:
> affects -1 src:pytest
Bug #1026210 [src:scipy] scipy: autopkgtest regression due to invalid test
function returns
Added indication that 1026210 affects src:pytest
--
1026210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026210
Debian Bug Tracking System
Cont
Source: scipy
Version: 1.8.1-14
Severity: serious
Control: affects -1 src:pytest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainers,
the autopkgtest of your package started failing because some of the
tests return values. This has always been incorrect (tests are expected
to assert
Processing control commands:
> affects -1 src:pytest
Bug #1026207 [src:python-ase] python-ase: autopkgtest regression because test
functions return values
Added indication that 1026207 affects src:pytest
--
1026207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026207
Debian Bug Tracking S
Source: python-ase
Version: 3.22.1-2
Severity: serious
Control: affects -1 src:pytest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainers,
the autopkgtest of your package started failing because some of the
tests return values. This has always been incorrect (tests are expected
to a
Package: g++-13
Version: 13-20221214-1
Severity: serious
Hi Matthias,
thanks for pushing gcc-13 into experimental already. That leaves plenty
of time to work on it. I've located a quite fundamental problem with it
already:
$ cat test.c++
#include
$ g++-13 -c test.c++
In file included from /usr/
Your message dated Fri, 16 Dec 2022 09:49:06 +
with message-id
and subject line Bug#1024913: fixed in flask-restful 0.3.9-5
has caused the Debian Bug report #1024913,
regarding flask-restful: (autopkgtest) needs update for python3.11: Address
already in use
to be marked as done.
This means t
Hi Paul,
Le jeudi 15 décembre 2022 à 21:16 +0100, Paul Gevers a écrit :
> On 13-12-2022 21:59, Sébastien Villemot wrote:
> > The problem is that atlas needs to be recompiled against lapack 3.11.0.
> > Which has been done in atlas 3.10.3-13. But atlas itself cannot migrate
> > to testing because of
Processing commands for cont...@bugs.debian.org:
> tags 1026057 + help
Bug #1026057 [src:swi-prolog] swi-prolog: autopkgtest regression on armel armhf
and i386: Segmentation fault
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026057: https:/
Hi Paul,
Чт 15 дек 2022 @ 21:10 Paul Gevers :
> On 14-12-2022 10:15, Debian Bug Tracking System wrote:
>> * rebuild against new swi-prolog (Closes: #1026056)
>
> I can't but feel a bit uneasy by this "solution". Apparently it's not
> properly tracked by dependencies, so it doesn't show up on
On 15/12/2022 20:38, Mihai Moldovan wrote:
[Resent to the bug tracker as well]
* On 12/15/22 19:15, Emilio Pozuelo Monfort wrote:
I'm not sure I understand what the problem is. The patches are in
debian/patches/ and are applied during build using quilt.
Oh this is about the xorg-server-source
52 matches
Mail list logo
