Processed: tagging 1025121, tagging 1025030

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1025121 + pending
Bug #1025121 [src:python-stack-data] python-stack-data: (autopkgtest) needs 
update for python3.11: AssertionError
Added tag(s) pending.
> tags 1025030 + pending
Bug #1025030 [src:python-executing] python-executing: (autopkgtest) needs 
update for python3.11: RuntimeError
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1025030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025030
1025121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: python-boto: diff for NMU version 2.49.0-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1025024 + patch
Bug #1025024 [src:python-boto] python-boto: (autopkgtest) needs update for 
python3.11: Cannot spec a Mock object
Added tag(s) patch.
> tags 1025024 + pending
Bug #1025024 [src:python-boto] python-boto: (autopkgtest) needs update for 
python3.11: Cannot spec a Mock object
Added tag(s) pending.

-- 
1025024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025024: python-boto: diff for NMU version 2.49.0-4.1

[Jochen Sprickerhof]

Control: tags 1025024 + patch
Control: tags 1025024 + pending

Dear maintainer,

I've prepared an NMU for python-boto (versioned as 2.49.0-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-boto-2.49.0/debian/changelog python-boto-2.49.0/debian/changelog
--- python-boto-2.49.0/debian/changelog	2021-12-19 16:45:16.0 +0100
+++ python-boto-2.49.0/debian/changelog	2022-12-15 07:50:01.0 +0100
@@ -1,3 +1,10 @@
+python-boto (2.49.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix autopkgtests (Closes: #1025024)
+
+ -- Jochen Sprickerhof   Thu, 15 Dec 2022 07:50:01 +0100
+
 python-boto (2.49.0-4) unstable; urgency=medium
 
   * Add patch to fix importing from collections (Closes: #1001395).
diff -Nru python-boto-2.49.0/debian/patches/0005-Don-t-mock-list-subclass.patch python-boto-2.49.0/debian/patches/0005-Don-t-mock-list-subclass.patch
--- python-boto-2.49.0/debian/patches/0005-Don-t-mock-list-subclass.patch	1970-01-01 01:00:00.0 +0100
+++ python-boto-2.49.0/debian/patches/0005-Don-t-mock-list-subclass.patch	2022-12-15 07:45:17.0 +0100
@@ -0,0 +1,21 @@
+From: Jochen Sprickerhof 
+Date: Thu, 15 Dec 2022 07:44:54 +0100
+Subject: Don't mock list subclass
+
+---
+ tests/unit/ec2/test_volume.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/tests/unit/ec2/test_volume.py b/tests/unit/ec2/test_volume.py
+index 81d7f55..d4d8e4f 100644
+--- a/tests/unit/ec2/test_volume.py
 b/tests/unit/ec2/test_volume.py
+@@ -55,7 +55,7 @@ class VolumeTests(unittest.TestCase):
+ @mock.patch("boto.resultset.ResultSet")
+ def test_startElement_with_name_tagSet_calls_ResultSet(self, ResultSet, startElement):
+ startElement.return_value = None
+-result_set = mock.Mock(ResultSet([("item", Tag)]))
++result_set = ResultSet([("item", Tag)])
+ volume = Volume()
+ volume.tags = result_set
+ retval = volume.startElement("tagSet", None, None)
diff -Nru python-boto-2.49.0/debian/patches/series python-boto-2.49.0/debian/patches/series
--- python-boto-2.49.0/debian/patches/series	2021-12-19 16:45:16.0 +0100
+++ python-boto-2.49.0/debian/patches/series	2022-12-15 07:45:17.0 +0100
@@ -2,3 +2,4 @@
 Use-python-six-from-Debian-instead-of-vendored-copy.patch
 bug-953970_python3.8-compat.patch
 fix-importing-from-collections.patch
+0005-Don-t-mock-list-subclass.patch


signature.asc
Description: PGP signature

Bug#1026125: debhelper: makes packages fail with Operation not permitted

[Helmut Grohne]

Package: debhelper
Version: 13.11.2
Severity: grave
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:desmume src:libpappsomspp src:libstatgrab src:libzstd 
src:minitube src:netgen-lvs src:psmisc src:quvi src:rinetd src:tor src:xz-utils 
src:wdiff

Hi Niels,

I'm pretty sure this upload is bad now although I cannot yet pin why.
Affected packages started FTBFSing and the symptom looks like this:

|dh_auto_configure
| install -m0755 -o 0 -g 0 -d 
/<>/libzstd-1.5.2\+dfsg/debian/.debhelper/generated/_source/home
| install: cannot change owner and permissions of 
‘/<>/debian/.debhelper/generated/_source/home’: Operation not 
permitted
| dh_auto_configure: error: install -m0755 -o 0 -g 0 -d 
/<>/libzstd-1.5.2\+dfsg/debian/.debhelper/generated/_source/home 
returned exit code 1
| make: *** [debian/rules:16: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Processed: debhelper: makes packages fail with Operation not permitted

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:desmume src:libpappsomspp src:libstatgrab src:libzstd 
> src:minitube src:netgen-lvs src:psmisc src:quvi src:rinetd src:tor 
> src:xz-utils src:wdiff
Bug #1026125 [debhelper] debhelper: makes packages fail with Operation not 
permitted
Added indication that 1026125 affects src:desmume, src:libpappsomspp, 
src:libstatgrab, src:libzstd, src:minitube, src:netgen-lvs, src:psmisc, 
src:quvi, src:rinetd, src:tor, src:xz-utils, and src:wdiff

-- 
1026125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026124: haskell-githash ftbfs

[Steve Langasek]

Source: haskell-githash
Version: 0.1.6.2-1
Severity: serious
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar

Hi Clint,

The haskell-githash package fails to build from source in unstable with
testsuite failures:

[...]
Failures:

  test/RepoWithASubmoduleSpec.hs:21:13: 
  1) RepoWithASubmodule.getGitInfo it makes sensible git info for a both the 
parent and the child module
   uncaught exception: IOException of type OtherError
   readCreateProcess: git "submodule" "add" "/tmp/with-submodule1520181/2" 
"2" (exit 128): failed

  To rerun use: --match "/RepoWithASubmodule/getGitInfo/it makes sensible git 
info for a both the parent and the child module/"

  test/RepoWithASubmoduleSpec.hs:38:13: 
  2) RepoWithASubmodule.getGitRoot it gets the expected git root for a both the 
parent and the child module
   uncaught exception: IOException of type OtherError
   readCreateProcess: git "submodule" "add" "/tmp/with-submodule1520181/2" 
"2" (exit 128): failed

  To rerun use: --match "/RepoWithASubmodule/getGitRoot/it gets the expected 
git root for a both the parent and the child module/"

Randomized with seed 773553922

Finished in 0.2952 seconds
7 examples, 2 failures
[...]

This was noticed in Ubuntu when rebuilding for the ghc 9.0.2 transition, but
it is also reproducible in unstable.

  
https://launchpad.net/ubuntu/+source/haskell-githash/0.1.6.2-1build2/+build/24927578


Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1026094: marked as done (prometheus-ipmi-exporter: autopkgtest/build fails due to API change in prometheus exporter-toolkit)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2022 04:35:34 +
with message-id 
and subject line Bug#1026094: fixed in prometheus-ipmi-exporter 1.6.1-2
has caused the Debian Bug report #1026094,
regarding prometheus-ipmi-exporter: autopkgtest/build fails due to API change 
in prometheus exporter-toolkit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-ipmi-exporter
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Dear Maintainer,

Recent API changes in the github.com/prometheus/exporter-toolkit/web
package, which are included in golang-github-prometheus-exporter-toolkit
0.8.2-1, cause the autopkgtest (and re-build) to fail.

This can be fixed by an upstream commit that adapts to the new API.

Thanks,
Nick
diff -Nru 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
--- 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
  1969-12-31 19:00:00.0 -0500
+++ 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
  2022-12-13 15:51:36.0 -0500
@@ -0,0 +1,33 @@
+Description: Fix build with golang-github-prometheus-exporter-toolkit 0.8.2
+Origin: upstream, 
https://github.com/prometheus-community/ipmi_exporter/commit/e8989cfdf79bebb2e3d84e43f65a7fc027ee7bba.patch
+Bug-Ubuntu: https://launchpad.net/bugs/1999574
+Last-Update: 2022-12-13
+---
+--- a/main.go
 b/main.go
+@@ -41,11 +41,7 @@
+   "freeipmi.path",
+   "Path to FreeIPMI executables.",
+   ).Default("/usr/sbin").String()
+-  listenAddress = kingpin.Flag(
+-  "web.listen-address",
+-  "Address to listen on for web interface and telemetry.",
+-  ).Default(":9290").String()
+-  webConfig = webflag.AddFlags(kingpin.CommandLine)
++  webConfig = webflag.AddFlags(kingpin.CommandLine, ":9290")
+ 
+   sc = {
+   C: {},
+@@ -169,10 +165,8 @@
+ `))
+   })
+ 
+-  level.Info(logger).Log("msg", "Listening on", "address", *listenAddress)
+-
+-  srv := {Addr: *listenAddress}
+-  if err := web.ListenAndServe(srv, *webConfig, logger); err != nil {
++  srv := {}
++  if err := web.ListenAndServe(srv, webConfig, logger); err != nil {
+   level.Error(logger).Log("msg", "HTTP listener stopped", 
"error", err)
+   os.Exit(1)
+   }
diff -Nru prometheus-ipmi-exporter-1.6.1/debian/patches/series 
prometheus-ipmi-exporter-1.6.1/debian/patches/series
--- prometheus-ipmi-exporter-1.6.1/debian/patches/series2022-06-22 
07:19:56.0 -0400
+++ prometheus-ipmi-exporter-1.6.1/debian/patches/series2022-12-13 
15:23:10.0 -0500
@@ -1 +1,2 @@
 01-debian-defaults.patch
+02-fix-build-with-new-exporter-toolkit.patch
--- End Message ---
--- Begin Message ---
Source: prometheus-ipmi-exporter
Source-Version: 1.6.1-2
Done: Daniel Swarbrick 

We believe that the bug you reported is fixed in the latest version of
prometheus-ipmi-exporter, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Swarbrick  (supplier of updated 
prometheus-ipmi-exporter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Dec 2022 04:09:48 +
Source: prometheus-ipmi-exporter
Architecture: source
Version: 1.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Daniel Swarbrick 
Closes: 1026094
Changes:
 prometheus-ipmi-exporter (1.6.1-2) unstable; urgency=medium
 .
   [ Daniel Swarbrick ]
   * Bump minimum required golang-github-prometheus-exporter-toolkit-dev
 version to 0.8.0
   * d/control: replace golang-go with golang-any
 .
   [ Nick 

Processed: closing 1025982

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1025982 0.3.3-8
Bug #1025982 [src:python-mitogen] python-mitogen: autopkgtest needs update for 
new version of ansible-core
Marked as fixed in versions python-mitogen/0.3.3-8.
Bug #1025982 [src:python-mitogen] python-mitogen: autopkgtest needs update for 
new version of ansible-core
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1025982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025982: closing 1025982

[Unit 193]

close 1025982 0.3.3-8
thanks

We believe that the bug you reported is fixed in the latest version of
python-mitogen, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Tue, 13 Dec 2022 21:43:51 -0500
Source: python-mitogen
Architecture: source
Version: 0.3.3-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Unit 193 
Changes:
 python-mitogen (0.3.3-8) unstable; urgency=medium
 .
   * Team upload.
   * d/p/ansible-6, d/control: Bump max ansible to 2.14/7.
Checksums-Sha1:
 b928b64dba03bcd6ebfcc51d2f988c5188131565 2371 python-mitogen_0.3.3-8.dsc
 5fd4c0d68fbaaac9a53188a25d215d8fd1cbaa2a 1260897 
python-mitogen_0.3.3.orig.tar.gz
 83b55242b10dccee7cfa1e8e9ba82dde622b1121 12008 
python-mitogen_0.3.3-8.debian.tar.xz
 844a2b744400792cb95665685fd0602e18ba23b2 6897 
python-mitogen_0.3.3-8_amd64.buildinfo
Checksums-Sha256:
 3b71240060e665652c3d8c301b83a1fb44d5293573cecd768f9e11df416f8669 2371 
python-mitogen_0.3.3-8.dsc
 41d2c540a64ca4706f9413e6807c8d5d401918788ae7428d8273c80bb61ca216 1260897 
python-mitogen_0.3.3.orig.tar.gz
 21aa1719e3b80ccd2af944b6469d9abf8e764c666b060ca6be84ab2adda3e322 12008 
python-mitogen_0.3.3-8.debian.tar.xz
 2671f1c8a383d16d45d05dcc98397ab25d1eb40755e84db96f88cfa997305d99 6897 
python-mitogen_0.3.3-8_amd64.buildinfo
Files:
 fbb8286c43bfda33bb758cafc3ecc7f4 2371 python optional 
python-mitogen_0.3.3-8.dsc
 0b15434520c5064784984336b6464f87 1260897 python optional 
python-mitogen_0.3.3.orig.tar.gz
 6cf4cd212face4232b7eedc57676d2b5 12008 python optional 
python-mitogen_0.3.3-8.debian.tar.xz
 c583cd552ca7f5e30a265c106463fc03 6897 python optional 
python-mitogen_0.3.3-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmOZOw0ACgkQUAHhsJqj
dEtdgg/+Owb9nl8HHnlP+ONDDf4Zj/roOwhLDTjNkS/VvvDLfMqv0fBH4FgaVQcu
946I2I4jie6FXB7yWyr4+I6aOSuzKrg/kNkAegVLIWhFNbL1bVEFikd2VW0zCjZ9
FP0I1ERIXj/Hgc7vmiwkBAxauf3V3jbEqPiUbxuDatZxjf/YCwdJkDItcvfeWWAa
cv/ttY0I7PBN/nxeP1uMExgBDG+5UHWt+tLaszB5zfJNvXcyXSoVnccQpsGO0E9Y
4CSrHeuoO6SnRsoLM+H0GBt7omrpbEg18BIskoWk9Z+csmlTBc1eyVpkrMzmS2uw
9CiacNbVnxxXjqpxRv9tOh066Lr9vO6I9iPWvYN+Kt7mAopup525dUpEVwd6vl6K
C6EpP831gN6C85/tLygyGPRz2r5oZr8b/kSbZwr5VC0bFOa/FSuSIYIfdnDwSaoz
Eytie3c91FiVQDG6t2/5G+m7tedZSFQGb9Hz7KrBxISOrqFxrAtKGzfAoBiRrG2S
+aY0PD0fppdQNqrjXVNcNuJhW9dB3vFlhPLaZngGHZ86tSaQB+5cHb0Mo83d/e/s
Rpnn23zZEM36nOZfLN0jQjlYXxaARedcQaabxR9CQmWwYGOj/NAwpuAdNQG8NAKc
vE/qBsChnHftOqhvE7wiPbzndFYlISLBw8YpK41IIP9TETgIh1k=
=LHsU
-END PGP SIGNATURE-

Bug#1024483: marked as done (geany-plugins: FTBFS against libgpgme-dev >= 1.18.0-2)

[Debian Bug Tracking System]

Your message dated Thu, 15 Dec 2022 04:04:48 +
with message-id 
and subject line Bug#1024483: fixed in geany-plugins 1.38+dfsg-2
has caused the Debian Bug report #1024483,
regarding geany-plugins: FTBFS against libgpgme-dev >= 1.18.0-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1024483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geany-plugins
Version: 1.38+dfsg-1.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

geany-plugins ships an outdated version of gpgme.m4 which cannot handle
the transition from gpgme-config to gpgrt-config. Deleting the outdated
copy lets the build succeed.

cu Andreas
--- geany-plugins-1.38+dfsg.orig/Makefile.am
+++ geany-plugins-1.38+dfsg/Makefile.am
@@ -1,4 +1,4 @@
-ACLOCAL_AMFLAGS = -I build/cache -I build -I build/bundled -I geanypy/m4 --install
+ACLOCAL_AMFLAGS = -I build/cache -I build -I geanypy/m4 --install
 AM_DISTCHECK_CONFIGURE_FLAGS = --with-geany-libdir='$${libdir}'
 
 SUBDIRS = po
--- geany-plugins-1.38+dfsg.orig/build/bundled/gpgme.m4
+++ /dev/null
@@ -1,307 +0,0 @@
-# gpgme.m4 - autoconf macro to detect GPGME.
-# Copyright (C) 2002, 2003, 2004 g10 Code GmbH
-#
-# This file is free software; as a special exception the author gives
-# unlimited permission to copy and/or distribute it, with or without
-# modifications, as long as this notice is preserved.
-#
-# This file is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
-# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-
-AC_DEFUN([_AM_PATH_GPGME_CONFIG],
-[ AC_ARG_WITH(gpgme-prefix,
-AC_HELP_STRING([--with-gpgme-prefix=PFX],
-   [prefix where GPGME is installed (optional)]),
- gpgme_config_prefix="$withval", gpgme_config_prefix="")
-  if test "x$gpgme_config_prefix" != x ; then
-  GPGME_CONFIG="$gpgme_config_prefix/bin/gpgme-config"
-  fi
-  AC_PATH_PROG(GPGME_CONFIG, gpgme-config, no)
-
-  if test "$GPGME_CONFIG" != "no" ; then
-gpgme_version=`$GPGME_CONFIG --version`
-  fi
-  gpgme_version_major=`echo $gpgme_version | \
-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
-  gpgme_version_minor=`echo $gpgme_version | \
-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
-  gpgme_version_micro=`echo $gpgme_version | \
-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
-])
-
-dnl AM_PATH_GPGME([MINIMUM-VERSION,
-dnl   [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
-dnl Test for libgpgme and define GPGME_CFLAGS and GPGME_LIBS.
-dnl
-AC_DEFUN([AM_PATH_GPGME],
-[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl
-  tmp=ifelse([$1], ,1:0.4.2,$1)
-  if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
- req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
- min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
-  else
- req_gpgme_api=0
- min_gpgme_version="$tmp"
-  fi
-
-  AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version)
-  ok=no
-  if test "$GPGME_CONFIG" != "no" ; then
-req_major=`echo $min_gpgme_version | \
-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
-req_minor=`echo $min_gpgme_version | \
-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
-req_micro=`echo $min_gpgme_version | \
-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
-if test "$gpgme_version_major" -gt "$req_major"; then
-ok=yes
-else 
-if test "$gpgme_version_major" -eq "$req_major"; then
-if test "$gpgme_version_minor" -gt "$req_minor"; then
-   ok=yes
-else
-   if test "$gpgme_version_minor" -eq "$req_minor"; then
-   if test "$gpgme_version_micro" -ge "$req_micro"; then
- ok=yes
-   fi
-   fi
-fi
-fi
-fi
-  fi
-  if test $ok = yes; then
- # If we have a recent GPGME, we should also check that the
- # API is compatible.
- if test "$req_gpgme_api" -gt 0 ; then
-tmp=`$GPGME_CONFIG --api-version 2>/dev/null || echo 0`
-if test "$tmp" -gt 0 ; then
-   if test "$req_gpgme_api" -ne "$tmp" ; then
- ok=no
-   fi
-fi
- fi
-  fi
-  if test $ok = yes; then
-

Processed: tagging 1026072

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1026072 + pending
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Bug #1026105 [firefox] firefox: XPCOMGlueLoad error for file 
/usr/lib/firefox/libnssutil3.so
Bug #1026111 [firefox] Failed to start due to missing 
/usr/lib/firefox/libnssutil3.so
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
1026105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026105
1026111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026117: golang-gogoprotobuf: FTBFS on all and ppc64el: test failures

[Cyril Brulebois]

Source: golang-gogoprotobuf
Version: 1.3.2-2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: Jelmer Vernooij 

Hi Jelmer,

Your golang-gogoprotobuf upload FTBFSes on both all and ppc64el:
  https://buildd.debian.org/status/package.php?p=golang-gogoprotobuf


As usual, all is built on amd64 (x86-csail-02.debian.org this time), and
the failure looks like this:

=== RUN   TestStdTypesGoString
stdtypespb_test.go:611: 1:39: expected operand, found '<' (and 1 more 
errors)
--- FAIL: TestStdTypesGoString (0.00s)

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=golang-gogoprotobuf=all=1.3.2-2=1671022557=0


The ppc6el failure looks similar:

=== RUN   TestStdTypesGoString
stdtypespb_test.go:611: 1:39: expected operand, found '<' (and 1 more 
errors)
--- FAIL: TestStdTypesGoString (0.00s)

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=golang-gogoprotobuf=ppc64el=1.3.2-2=1671025321=0


I've spotted this regression while working on crowdsec (#1011665), since
golang-github-docker-docker-dev couldn't be installed in cowbuilder.

I suppose at least all of its reverse build dependencies are broken at
the moment, but I didn't perform any extra checks:

crowdsec
gitlab-ci-multi-runner
golang-github-containerd-stargz-snapshotter
golang-github-containers-buildah
golang-github-containers-common
golang-github-containers-image
golang-github-containers-psgo
golang-github-containers-storage
golang-github-fsouza-go-dockerclient
golang-github-openshift-imagebuilder
golang-github-optiopay-kafka
golang-github-samalba-dockerclient
golang-github-tonistiigi-fsutil
golang-oras-oras-go
libpod
nomad
nomad-driver-lxc
nomad-driver-podman
oci-seccomp-bpf-hook
prometheus
prometheus-postfix-exporter
singularity-container
skeema
skopeo


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#1025943: marked as done (dolphin: copy/move files: only the first item is copied to the clipboard)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 22:05:04 +
with message-id 
and subject line Bug#1025943: fixed in dolphin 4:22.12.0-2
has caused the Debian Bug report #1025943,
regarding dolphin: copy/move files: only the first item is copied to the 
clipboard
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dolphin
Version: 4:22.12.0-1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com

Dear Maintainer,

there is a kde bug that makes it problematic to copy/move files, see link
https://bugs.kde.org/show_bug.cgi?id=462928

I went back to the previous version 4:22.08.1-1

Perhaps it would be to return to the previous version also in the repositories
and update this package only when the problem is solved.

Thanks,
Antonio



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-12.1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dolphin depends on:
ii  baloo-kf5 5.100.0-1
ii  kinit 5.100.0-1
ii  kio   5.100.0-2
ii  libc6 2.36-6
hi  libdolphinvcs54:22.08.1-1
ii  libkf5activities5 5.100.0-1
ii  libkf5baloo5  5.100.0-1
ii  libkf5baloowidgets5   4:22.12.0-2
ii  libkf5bookmarks5  5.100.0-1
ii  libkf5codecs5 5.100.0-1
ii  libkf5completion5 5.100.0-1
ii  libkf5configcore5 5.100.1-1
ii  libkf5configgui5  5.100.1-1
ii  libkf5configwidgets5  5.100.0-1
ii  libkf5coreaddons5 5.100.0-1
ii  libkf5crash5  5.100.0-1
ii  libkf5dbusaddons5 5.100.0-1
ii  libkf5filemetadata3   5.100.0-1
ii  libkf5i18n5   5.100.0-1
ii  libkf5iconthemes5 5.100.0-1
ii  libkf5itemviews5  5.100.0-1
ii  libkf5jobwidgets5 5.100.0-1
ii  libkf5kcmutils5   5.100.0-1
ii  libkf5kiocore55.100.0-2
ii  libkf5kiofilewidgets5 5.100.0-2
ii  libkf5kiogui5 5.100.0-2
ii  libkf5kiowidgets5 5.100.0-2
ii  libkf5newstuff5   5.100.0-1
ii  libkf5newstuffwidgets55.100.0-1
ii  libkf5notifications5  5.100.0-1
ii  libkf5parts5  5.100.0-1
ii  libkf5service-bin 5.100.0-1
ii  libkf5service55.100.0-1
ii  libkf5solid5  5.100.0-1
ii  libkf5textwidgets55.100.0-1
ii  libkf5widgetsaddons5  5.100.0-2
ii  libkf5windowsystem5   5.100.0-1
ii  libkf5xmlgui5 5.100.0-1
ii  libkuserfeedbackcore1 1.2.0-2
ii  libkuserfeedbackwidgets1  1.2.0-2
ii  libpackagekitqt5-11.1.0-1
ii  libphonon4qt5-4   4:4.11.1-4
ii  libqt5core5a  5.15.6+dfsg-5
ii  libqt5dbus5   5.15.6+dfsg-5
ii  libqt5gui55.15.6+dfsg-5
ii  libqt5widgets55.15.6+dfsg-5
ii  libqt5xml55.15.6+dfsg-5
ii  libstdc++612.2.0-10
ii  phonon4qt54:4.11.1-4

Versions of packages dolphin recommends:
ii  ffmpegthumbs  4:22.12.0-2
ii  kdegraphics-thumbnailers  4:22.12.0-1
ii  kimageformat-plugins  5.100.0-1
ii  kio-extras4:22.12.0-2

Versions of packages dolphin suggests:
ii  dolphin-plugins  4:22.12.0-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/dolphin (from dolphin package)
--- End Message ---
--- Begin Message ---
Source: dolphin
Source-Version: 4:22.12.0-2
Done: Aurélien COUDERC 

We believe that the bug you reported is fixed in the latest version of
dolphin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurélien COUDERC  (supplier of updated dolphin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please 

Processed: forcibly merging 1026072 1026111

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1026072 1026111
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Bug #1026105 [firefox] firefox: XPCOMGlueLoad error for file 
/usr/lib/firefox/libnssutil3.so
Bug #1026111 [firefox] Failed to start due to missing 
/usr/lib/firefox/libnssutil3.so
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1805371'.
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Bug #1026105 [firefox] firefox: XPCOMGlueLoad error for file 
/usr/lib/firefox/libnssutil3.so
Merged 1026072 1026073 1026077 1026105 1026111
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
1026105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026105
1026111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025021: closing 1025021

[Jochen Sprickerhof]

close 1025021 1.3.7-9
thanks

Processed: forcibly merging 1026072 1026105

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1026072 1026105
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Bug #1026105 [firefox] firefox: XPCOMGlueLoad error for file 
/usr/lib/firefox/libnssutil3.so
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1805371'.
Severity set to 'grave' from 'important'
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Merged 1026072 1026073 1026077 1026105
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
1026105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1025021

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1025021 1.3.7-9
Bug #1025021 [python3-nose] python-bayespy: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Marked as fixed in versions nose/1.3.7-9.
Bug #1025021 [python3-nose] python-bayespy: (autopkgtest) needs update for 
python3.11: module 'inspect' has no attribute 'getargspec'
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1025021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1026072 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1805371

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1026072 https://bugzilla.mozilla.org/show_bug.cgi?id=1805371
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1805371'.
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1805371'.
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1805371'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026111: Failed to start due to missing /usr/lib/firefox/libnssutil3.so

[Klaus Ethgen]

Package: firefox
Version: 108.0-1
Severity: grave

When I try to start the most current firefox, I get the following error:
~> firefox
XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so:
/usr/lib/firefox/libnssutil3.so: cannot open shared object file: No such file 
or directory
Couldn't load XPCOM.

libnss3 is installed and has libnssutil3.so in
/usr/lib/x86_64-linux-gnu/libnssutil3.so.

When I try to symlink that so file, I get the same error for libnss3.so,
libsmime3.so, libssl3.so (where I stopped, trying)


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.13.1-4.5
ii  libasound2   1.2.8-1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-6
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1devuan1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.3-1
ii  libgtk-3-0   3.24.35-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.85-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libstdc++6   12.2.0-10
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:4.0.2-2devuan1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec59  10:5.1.2-dmo2

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-1
pn  pulseaudio 

-- Configuration Files:
/etc/firefox/firefox.js changed [not included]

-- no debconf information

-- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


signature.asc
Description: PGP signature

Processed: forcibly merging 1026072 1026077

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1026072 1026077
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Merged 1026072 1026073 1026077
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 1026072 1026073

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1026072 1026073
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Merged 1026072 1026073 1026077
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026110: xournal: FTBFS: Makefile:263: *** missing separator. Stop.

[Aurelien Jarno]

Package: xournal
Version: 1:0.4.8.2016-7+b1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer(s),

Your package fails to build with:

|dh_auto_build
|   make -j8
| make[1]: Entering directory '/build/1st/xournal-0.4.8.2016'
| Makefile:263: *** missing separator.  Stop.
| make[1]: Leaving directory '/build/1st/xournal-0.4.8.2016'
| dh_auto_build: error: make -j8 returned exit code 2
| make: *** [debian/rules:6: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

The full build log is available from:
  
https://buildd.debian.org/status/fetch.php?pkg=xournal=riscv64=1%3A0.4.8.2016-7%2Bb2=1671008048=0
  
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/xournal_0.4.8.2016-7.rbuild.log.gz

Regards
Aurelien

Bug#1025026: marked as done (python-bytecode: (autopkgtest) needs update for python3.11: invalid operation name)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 21:21:43 +
with message-id 
and subject line Bug#1025026: fixed in python-bytecode 0.14.0-1
has caused the Debian Bug report #1025026,
regarding python-bytecode: (autopkgtest) needs update for python3.11: invalid 
operation name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: python-bytecode
Version: 0.13.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
python-bytecode fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
python-bytecodefrom testing0.13.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-bytecode/28728884/log.gz

=== FAILURES 
===
_ BytecodeTests.test_empty_dup 
_


self = <[AttributeError("'Instr' object has no attribute '_arg'") raised 
in repr()] Instr object at 0x7fcc47774e00>

name = 'DUP_TOP', arg = , lineno = None

def _set(self, name, arg, lineno):
if not isinstance(name, str):
raise TypeError("operation name must be a str")
try:

  opcode = _opcode.opmap[name]

E   KeyError: 'DUP_TOP'

/usr/lib/python3/dist-packages/bytecode/instr.py:233: KeyError

During handling of the above exception, another exception occurred:

self = 

def test_empty_dup(self):
code = Bytecode()
code.first_lineno = 1

  code.extend([Instr("DUP_TOP")])


tests/test_bytecode.py:426: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/bytecode/instr.py:171: in __init__

self._set(name, arg, lineno)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
self = <[AttributeError("'Instr' object has no attribute '_arg'") raised 
in repr()] Instr object at 0x7fcc47774e00>

name = 'DUP_TOP', arg = , lineno = None

def _set(self, name, arg, lineno):
if not isinstance(name, str):
raise TypeError("operation name must be a str")
try:
opcode = _opcode.opmap[name]
except KeyError:

  raise ValueError("invalid operation name")

E   ValueError: invalid operation name

/usr/lib/python3/dist-packages/bytecode/instr.py:235: ValueError
_ BytecodeTests.test_for_iter_stack_effect_computation 
_


self = <[AttributeError("'Instr' object has no attribute '_arg'") raised 
in repr()] Instr object at 0x7fcc47774ea0>
name = 'JUMP_ABSOLUTE', arg = 0x7fcc4797afe0>

lineno = None

def _set(self, name, arg, lineno):
if not isinstance(name, str):
raise TypeError("operation name must be a str")
try:

  opcode = _opcode.opmap[name]

E   KeyError: 'JUMP_ABSOLUTE'

/usr/lib/python3/dist-packages/bytecode/instr.py:233: KeyError

During handling of the above exception, another exception occurred:

self = testMethod=test_for_iter_stack_effect_computation>


def test_for_iter_stack_effect_computation(self):
with self.subTest():
code = Bytecode()
code.first_lineno = 1
lab1 = Label()
lab2 = Label()
code.extend(
[
lab1,
Instr("FOR_ITER", lab2),
Instr("STORE_FAST", "i"),

  

Bug#1021675: marked as done (ariba: autopkgtest regression and ftbfs with samtools 1.16)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 21:19:12 +
with message-id 
and subject line Bug#1022508: fixed in ariba 2.14.6+ds-4
has caused the Debian Bug report #1022508,
regarding ariba: autopkgtest regression and ftbfs with samtools 1.16
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1022508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ariba
Version: 2.14.6+ds-3
Severity: serious
Tags: ftbfs upstream help
Justification: fails to build from source (but built successfully in the past)

Greetings,

Following the upgrade of htslib, samtools and bcftools from
versions 1.13 to 1.16, ariba hits autopkgtest regressions which
are preventing migration of python-pysam to testing.  The test
failures are also present during the build time test suite,
causing the package to fail to build from source.

I attempted to begin wrapping up a patch fixing/working around
the problem which looks to be caused by the migration of mpileup
functionalities from samtools to bcftools, but the test suite
then chokes on non-matching command output, for which I don't
know whether the new results are sound and simply need
adjustments, or if errors could have been left over.  Temporary
patch is below for reference, but is not sufficient on his own
to fix the failure:

---8<--8<--8<--8<---
--- a/ariba/samtools_variants.py
+++ b/ariba/samtools_variants.py
@@ -1,6 +1,7 @@
 import os
 import sys
 import pysam
+import pysam.bcftools
 import pyfastaq
 import vcfcall_ariba
 
@@ -36,13 +37,11 @@
 
 tmp_vcf = self.vcf_file + '.tmp'
 with open(tmp_vcf, 'w') as f:
-print(pysam.mpileup(
+print(pysam.bcftools.mpileup(
 '-t', 'INFO/AD,INFO/ADF,INFO/ADR',
 '-L', '',
 '-A',
 '-f', self.ref_fa,
-'-u',
-'-v',
 self.bam,
 ), end='', file=f)
 
---8<--8<--8<--8<---

I already provided upstream with my findings on their issue
tracker[1] in a related entry, but I don't know for sure how
much active they are these days.  This note in debbugs is mostly
to document the issue for Med team members before they spend too
much time debugging this issue in parallel (and also seeking
help if possible).

[1]: https://github.com/sanger-pathogens/ariba/issues/327

Have a nice day,  :)
Étienne.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.
On air: Gazpacho - Valerie's Friend


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ariba
Source-Version: 2.14.6+ds-4
Done: Étienne Mollier 

We believe that the bug you reported is fixed in the latest version of
ariba, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated ariba package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 21:34:16 +0100
Source: ariba
Architecture: source
Version: 2.14.6+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1021675 1022508
Changes:
 ariba (2.14.6+ds-4) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Fix watch file
   * Standards-Version: 4.6.1 (routine-update)
   * Add salsa-ci file (routine-update)
 .
   [ Étienne Mollier ]
   * mpileup-1.16.patch: add; fix mpileup calls since htslib 1.16.
 (Closes: #1021675, #1022508)
   * 

Bug#1021675: marked as done (ariba: autopkgtest regression and ftbfs with samtools 1.16)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 21:19:12 +
with message-id 
and subject line Bug#1021675: fixed in ariba 2.14.6+ds-4
has caused the Debian Bug report #1021675,
regarding ariba: autopkgtest regression and ftbfs with samtools 1.16
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1021675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ariba
Version: 2.14.6+ds-3
Severity: serious
Tags: ftbfs upstream help
Justification: fails to build from source (but built successfully in the past)

Greetings,

Following the upgrade of htslib, samtools and bcftools from
versions 1.13 to 1.16, ariba hits autopkgtest regressions which
are preventing migration of python-pysam to testing.  The test
failures are also present during the build time test suite,
causing the package to fail to build from source.

I attempted to begin wrapping up a patch fixing/working around
the problem which looks to be caused by the migration of mpileup
functionalities from samtools to bcftools, but the test suite
then chokes on non-matching command output, for which I don't
know whether the new results are sound and simply need
adjustments, or if errors could have been left over.  Temporary
patch is below for reference, but is not sufficient on his own
to fix the failure:

---8<--8<--8<--8<---
--- a/ariba/samtools_variants.py
+++ b/ariba/samtools_variants.py
@@ -1,6 +1,7 @@
 import os
 import sys
 import pysam
+import pysam.bcftools
 import pyfastaq
 import vcfcall_ariba
 
@@ -36,13 +37,11 @@
 
 tmp_vcf = self.vcf_file + '.tmp'
 with open(tmp_vcf, 'w') as f:
-print(pysam.mpileup(
+print(pysam.bcftools.mpileup(
 '-t', 'INFO/AD,INFO/ADF,INFO/ADR',
 '-L', '',
 '-A',
 '-f', self.ref_fa,
-'-u',
-'-v',
 self.bam,
 ), end='', file=f)
 
---8<--8<--8<--8<---

I already provided upstream with my findings on their issue
tracker[1] in a related entry, but I don't know for sure how
much active they are these days.  This note in debbugs is mostly
to document the issue for Med team members before they spend too
much time debugging this issue in parallel (and also seeking
help if possible).

[1]: https://github.com/sanger-pathogens/ariba/issues/327

Have a nice day,  :)
Étienne.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.
On air: Gazpacho - Valerie's Friend


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ariba
Source-Version: 2.14.6+ds-4
Done: Étienne Mollier 

We believe that the bug you reported is fixed in the latest version of
ariba, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated ariba package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 21:34:16 +0100
Source: ariba
Architecture: source
Version: 2.14.6+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1021675 1022508
Changes:
 ariba (2.14.6+ds-4) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Fix watch file
   * Standards-Version: 4.6.1 (routine-update)
   * Add salsa-ci file (routine-update)
 .
   [ Étienne Mollier ]
   * mpileup-1.16.patch: add; fix mpileup calls since htslib 1.16.
 (Closes: #1021675, #1022508)
   * 

Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard

[Aurélien COUDERC]

Le lundi 12 décembre 2022 12:01:16 CET, vous avez écrit :
> Control: severity -1 serious
> 
> Le lundi 12 décembre 2022, 11:45:56 CET antonio a écrit :
> > Dear Maintainer,
> 
> Dear Antonio,
> 
> > there is a kde bug that makes it problematic to copy/move files, see link
> > https://bugs.kde.org/show_bug.cgi?id=462928
> > 
> > I went back to the previous version 4:22.08.1-1
> 
> thank you for your bug report.
> 
> I’m keeping 22.12.0 in unstable, but raising the severity of this bug report 
> so the new version doesn’t migrate to testing.

FYI I just uploaded 4:22.12.0-2 including the upstream-revert of the commit 
that broke this.


Happy hacking,
--
Aurélien

Bug#1026072: Fix for the bug

[Vincent Lefevre]

On 2022-12-14 19:57:38 +0100, Richard B. Kreckel wrote:
> I am having it too and downgrading to 107.0.1-1 fixes the problem.
> 
> It seems like someone was seeing something similar before and reported it
> here  but the bug
> got closed?

Because it was reported against firefox 107.0-1, which has no issues.
This one was apparently due to an issue introduced by the user, who
added a /usr/lib/firefox/libssl3.so file (not provided by the firefox
package). BTW, all those who added symbolic links to make FF 108 work
should remove them before upgrading the firefox package, otherwise
there is a risk to have the same kind of issue.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#999719: marked as done (ruby-omniauth-multipassword: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 21:04:57 +
with message-id 
and subject line Bug#999719: fixed in ruby-omniauth-multipassword 2.0.0~rc1-2
has caused the Debian Bug report #999719,
regarding ruby-omniauth-multipassword: FTBFS with ruby-omniauth 2.0.x: ERROR: 
Test "ruby2.7" failed:  NoMethodError:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
999719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-multipassword
Version: 0.4.2-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-multipassword was found to fail to build in that 
situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot. I would expect a new upstream version to
work against the latest ruby-omniauth just fine.

Relevant part (hopefully):
>  NoMethodError:
>undefined method `[]' for nil:NilClass
>  # ./spec/omniauth/strategy/multi_password_spec.rb:32:in `block (4 
> levels) in '
>  # 
> /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in
>  `call!'
>  # 
> /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in
>  `call'
>  # 
> /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/test/phony_session.rb:11:in
>  `call'
>  # ./spec/omniauth/strategy/multi_password_spec.rb:37:in `block (2 
> levels) in '
> 
> Finished in 0.03768 seconds (files took 0.14531 seconds to load)
> 11 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/omniauth/multipassword/base_spec.rb:61 # 
> OmniAuth::MultiPassword::Base single strategy shows login FORM
> rspec ./spec/omniauth/strategy/multi_password_spec.rb:36 # 
> OmniAuth::Strategies::MultiPassword shows login FORM
> 
> Randomized with seed 13795
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 


The full build log is available at
https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-multipassword.log


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-omniauth-multipassword
Source-Version: 2.0.0~rc1-2
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
ruby-omniauth-multipassword, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated 
ruby-omniauth-multipassword package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Dec 2022 17:36:27 -0300
Source: ruby-omniauth-multipassword
Architecture: source
Version: 2.0.0~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Kanashiro 
Closes: 999719
Changes:
 ruby-omniauth-multipassword (2.0.0~rc1-2) unstable; urgency=medium
 .
   * Team upload.
   * No-change upload to unstable.
 .
 ruby-omniauth-multipassword (2.0.0~rc1-1) experimental; urgency=medium
 .
   * Team Upload.
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Run wrap-and-sort on packaging files
   * Use new default gem2deb Rakefile to run the tests
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Bump debhelper from old 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update Vcs-* headers from URL redirect.
   * Use canonical URL in Vcs-Git.
   * 

Bug#1014968: marked as done (mruby: CVE-2021-46020 CVE-2022-0240 CVE-2022-0481 CVE-2022-0890 CVE-2022-1071 CVE-2022-1427 CVE-2022-1201)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 20:55:03 +
with message-id 
and subject line Bug#1014968: fixed in mruby 3.1.0-1
has caused the Debian Bug report #1014968,
regarding mruby: CVE-2021-46020 CVE-2022-0240 CVE-2022-0481 CVE-2022-0890 
CVE-2022-1071 CVE-2022-1427 CVE-2022-1201
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1014968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mruby
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for mruby.

CVE-2021-46020[0]:
| An untrusted pointer dereference in mrb_vm_exec() of mruby v3.0.0 can
| lead to a segmentation fault or application crash.

https://github.com/mruby/mruby/issues/5613
https://github.com/mruby/mruby/commit/a137ef12f981b517f1e6b64e39edc7ac15d7e1eb
https://github.com/mruby/mruby/commit/d3b7601af96c9e0eeba4c89359289661c755a74a

CVE-2022-0240[1]:
| mruby is vulnerable to NULL Pointer Dereference

https://huntr.dev/bounties/5857eced-aad9-417d-864e-0bdf17226cbb/
https://github.com/mruby/mruby/commit/31fa3304049fc406a201a72293cce140f0557dca

CVE-2022-0481[2]:
| NULL Pointer Dereference in Homebrew mruby prior to 3.2.

https://huntr.dev/bounties/54725c8c-87f4-41b6-878c-01d8e0ee7027
https://github.com/mruby/mruby/commit/ae3c99767a27f5c6c584162e2adc6a5d0eb2c54e

CVE-2022-0890[3]:
| NULL Pointer Dereference in GitHub repository mruby/mruby prior to
| 3.2.

https://huntr.dev/bounties/68e09ec1-6cc7-48b8-981d-30f478c70276/
https://github.com/mruby/mruby/commit/da48e7dbb20024c198493b8724adae1b842083aa

CVE-2022-1071[4]:
| User after free in mrb_vm_exec in GitHub repository mruby/mruby prior
| to 3.2.

https://huntr.dev/bounties/6597ece9-07af-415b-809b-919ce0a17cf3
https://github.com/mruby/mruby/commit/aaa28a508903041dd7399d4159a8ace9766b022f

CVE-2022-1427[5]:
| Out-of-bounds Read in mrb_obj_is_kind_of in in GitHub repository
| mruby/mruby prior to 3.2. # Impact: Possible arbitrary code execution
| if being exploited.

https://huntr.dev/bounties/23b6f0a9-64f5-421e-a55f-b5b7a671f301
https://github.com/mruby/mruby/commit/a4d97934d51cb88954cc49161dc1d151f64afb6b

CVE-2022-1201[6]:
| NULL Pointer Dereference in mrb_vm_exec with super in GitHub
| repository mruby/mruby prior to 3.2. This vulnerability is capable of
| making the mruby interpreter crash, thus affecting the availability of
| the system.

https://huntr.dev/bounties/6f930add-c9d8-4870-ae56-d4bd8354703b
https://github.com/mruby/mruby/commit/00acae117da1b45b318dc36531a7b0021b8097ae

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-46020
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46020
[1] https://security-tracker.debian.org/tracker/CVE-2022-0240
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0240
[2] https://security-tracker.debian.org/tracker/CVE-2022-0481
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0481
[3] https://security-tracker.debian.org/tracker/CVE-2022-0890
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0890
[4] https://security-tracker.debian.org/tracker/CVE-2022-1071
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1071
[5] https://security-tracker.debian.org/tracker/CVE-2022-1427
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1427
[6] https://security-tracker.debian.org/tracker/CVE-2022-1201
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1201

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: mruby
Source-Version: 3.1.0-1
Done: Nobuhiro Iwamatsu 

We believe that the bug you reported is fixed in the latest version of
mruby, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated mruby package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8

Bug#999720: marked as done (ruby-omniauth-oauth: 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_

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 20:56:19 +
with message-id 
and subject line Bug#999720: fixed in ruby-omniauth-oauth 1.2.0-2
has caused the Debian Bug report #999720,
regarding ruby-omniauth-oauth: 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_dependencies': Could not find 'omniauth' (~> 1.0) 
among 78 total gem(s) (Gem::MissingSpecError)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
999720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-oauth
Version: 1.1.0-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-oauth was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot. I would expect a new upstream version to
work against the latest ruby-omniauth just fine.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all/specifications/omniauth-oauth-1.1.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> addressable (2.8.0)
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> crack (0.4.4)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> docile (1.1.5)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashdiff (1.0.1)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 

Bug#1003649: marked as done (php-horde-argv: (autopkgtest) needs update for php8.1: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 20:55:18 +
with message-id 
and subject line Bug#1003649: fixed in php-horde-argv 2.1.0-8
has caused the Debian Bug report #1003649,
regarding php-horde-argv: (autopkgtest) needs update for php8.1: deprecation 
warnings on stderr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1003649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: php-horde-argv
Version: 2.1.0-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-argv fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing92
php-horde-argv from testing2.1.0-7
versioned deps from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs my be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php8.1 transition, it needs to be resolved one 
way or the other.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] https://bugs.debian.org/976811
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-argv/18254588/log.gz

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/BoolTest.php

   Class name was 'Horde_Argv_BoolTest', expected 'BoolTest'
Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackCheckAbbrevTest.php
   Class name was 'Horde_Argv_CallbackCheckAbbrevTest', 
expected 'CallbackCheckAbbrevTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackExtraArgsTest.php
   Class name was 'Horde_Argv_CallbackExtraArgsTest', 
expected 'CallbackExtraArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackManyArgsTest.php
   Class name was 'Horde_Argv_CallbackManyArgsTest', 
expected 'CallbackManyArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackMeddleArgsTest.php
   Class name was 'Horde_Argv_CallbackMeddleArgsTest', 
expected 'CallbackMeddleArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackTest.php
   Class name was 'Horde_Argv_CallbackTest', expected 
'CallbackTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackVarArgsTest.php
   Class name was 'Horde_Argv_CallbackVarArgsTest', 
expected 'CallbackVarArgsTest'

Warning:   Test case class not matching filename is deprecated

Bug#1025732: marked as done (src:genimage: fails to migrate to testing for too long: FTBFS (testsuite fails) on 32 bits systems)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 20:51:20 +
with message-id 
and subject line Bug#1025732: fixed in genimage 16-2
has caused the Debian Bug report #1025732,
regarding src:genimage: fails to migrate to testing for too long: FTBFS 
(testsuite fails) on 32 bits systems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: genimage
Version: 15-3
Severity: serious
Control: close -1 16-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:genimage has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on the 32 bit architectures where it built successfully in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=genimage



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: genimage
Source-Version: 16-2
Done: Sudip Mukherjee 

We believe that the bug you reported is fixed in the latest version of
genimage, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated genimage 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 19:36:11 +
Source: genimage
Architecture: source
Version: 16-2
Distribution: unstable
Urgency: medium
Maintainer: Sudip Mukherjee 
Changed-By: Sudip Mukherjee 
Closes: 1025732
Changes:
 genimage (16-2) unstable; urgency=medium
 .
   * Add upstream patches fixing ext.test. (Closes: #1025732)
Checksums-Sha1:
 e9f7332de5181d4b0e3de9f112e11313dbfc80ab 2013 genimage_16-2.dsc
 3e9456d8b3d5e53bd8f3d18af6abb3db53d67d2a 5060 genimage_16-2.debian.tar.xz
 d940f9ed34903a1fe2c6956b30b948f6e2e59cb6 6611 genimage_16-2_amd64.buildinfo
Checksums-Sha256:
 1a0209720a4db401dce7a74512740d74c5792ebad8f2e9cb8804008924b990ad 2013 
genimage_16-2.dsc
 d005316b05ca7126a4aef222976c73def9892e30c7bf6418cbde0c6032476bb4 5060 
genimage_16-2.debian.tar.xz
 6df85e462feb8b4af7168b0797b7832fa8e3e9a0a6e4497f72e4632ed7e04fbd 6611 
genimage_16-2_amd64.buildinfo
Files:
 fb000e5ade29fc8b3dfee40f4e3b6f86 2013 utils optional genimage_16-2.dsc
 c0a3b476735ed81c62f7b8aa084b0f2c 5060 utils optional 
genimage_16-2.debian.tar.xz
 63623c03d94e5aeda543b7eeeb80e48b 6611 utils optional 
genimage_16-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmOaJj0ACgkQR5mjUUbR
KzVZ1g/+PHkYo8lDrs9Gve6mQsvSSCvrZWUXYnDVFznCSos3vj/HkbSkBJEEJ8xg
bdVL4TRcvVmYV9vCT4VB8dKVMSHTAWBb/B+EhYvzGcgYyfG6euIjIi9PsrqsOE1e
zYiwfZ20ZX4RjrTC/rT86dxZuyAJZ7nrNUkbYr72LQ1CCNdCkBEf7UJgXAIGXovB
2rO35rRqZpFbqqk/ZHy1i/3IV1yurDPPJuIp9JaN+T8ROoAx3xu2wFIIRoxfeMX0

Bug#1026005: cumin FTBFS: Tries to use $HOME

[Antoine Beaupré]

Hi all,

So cumin is failing to build in Debian because it does some nasty things
during build (namely using $HOME, because of that setup.py develop --user).

I have a beginning of a fix for this in the bugfix-1026005 branch on
salsa. The problem now is that it fails on *other* parts of the test
suite, which wasn't failing before. I suspect it might be because the
code layout is different, but I can't figure out how or why...

Riccardo, Moritz, any ideas on how this could be fixed?

Here's the failing build log:

anarcat@angela:cumin$ dpkg-buildpackage 
dpkg-buildpackage: info: source package cumin
dpkg-buildpackage: info: source version 4.1.1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Antoine Beaupré 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-import-version-number-from-setuptools_scm.patch
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.10 setup.py clean 
running clean
removing '/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build' (and 
everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.10' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: warning: upstream signing key but no upstream tarball signature
dpkg-source: info: building cumin using existing ./cumin_4.1.1.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building cumin in cumin_4.1.1-3.debian.tar.xz
dpkg-source: info: building cumin in cumin_4.1.1-3.dsc
 debian/rules build
dh build --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:240: python3.10 setup.py config 
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build 
running build
running build_py
creating /home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
copying cumin/transport.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
copying cumin/color.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
copying cumin/cli.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
copying cumin/__init__.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
copying cumin/grammar.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
copying cumin/query.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin
creating 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/backends
copying cumin/backends/direct.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/backends
copying cumin/backends/openstack.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/backends
copying cumin/backends/puppetdb.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/backends
copying cumin/backends/knownhosts.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/backends
copying cumin/backends/__init__.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/backends
creating 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/transports
copying cumin/transports/clustershell.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/transports
copying cumin/transports/__init__.py -> 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build/cumin/transports
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:240: cd 
/home/anarcat/dist/cumin/.pybuild/cpython3_3.10_cumin/build; python3.10 -m 
pytest /home/anarcat/dist/cumin/cumin/tests/unit
 test 
session starts 

platform linux -- Python 3.10.8, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /home/anarcat/dist/cumin, configfile: pytest.ini
plugins: arraydiff-0.5.0, betamax-0.8.1, astropy-header-0.2.2, 
remotedata-0.3.3, requests-mock-1.9.3, hypothesis-6.36.0, openfiles-0.5.0, 
mock-3.8.2, astropy-0.10.0, cov-4.0.0, doctestplus-0.12.1, 
filter-subpackage-0.1.1
collected 416 items 


../../../cumin/tests/unit/test_backends.py .
  [  0%]
../../../cumin/tests/unit/test_cli.py ..
 

Bug#1026107: ruby-asciidoctor-pdf: depends on deprecated ruby-safe-yaml

[Antonio Terceiro]

Package: ruby-asciidoctor-pdf
Version: 1.6.2-1
Severity: serious
Tags: upstream
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Dear Maintainer,

Working to get ruby3.1 as the default Ruby version it was noticed that
ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most
upstreams have dropped their dependencies on it; I checked and that is
also the case for asciidoctor-pdf: v2.3.4 no longer depends on
safe_yaml.

ruby-safe-yaml will soon be removed from testing due to this,
ruby-asciidoctor-pdf needs to drop its dependency on it.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 
'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ruby-asciidoctor-pdf depends on:
ii  ruby  1:3.1~1
ii  ruby-asciidoctor  2.0.17-1
ii  ruby-concurrent   1.1.6+dfsg-5
pn  ruby-prawn
pn  ruby-prawn-icon   
pn  ruby-prawn-svg
pn  ruby-prawn-table  
ii  ruby-safe-yaml1.0.5-2
pn  ruby-treetop  

ruby-asciidoctor-pdf recommends no packages.

Versions of packages ruby-asciidoctor-pdf suggests:
ii  ruby-rouge  3.30.0-2


signature.asc
Description: PGP signature

Processed: Bug#1003649 marked as pending in php-horde-argv

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003649 [src:php-horde-argv] php-horde-argv: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Added tag(s) pending.

-- 
1003649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1003649: marked as pending in php-horde-argv

[Anton Gladky]

Control: tag -1 pending

Hello,

Bug #1003649 in php-horde-argv 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/horde-team/php-horde-argv/-/commit/1a6dde08c44d5a075389a66e46a90c86ee6c40e1


Fix autopkgtests. (Closes: #1003649)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003649

Processed: found 1026048 in 5.0.2-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1026048 5.0.2-2
Bug #1026048 [src:redmine] redmine: CVE-2022-44030 CVE-2022-44637 CVE-2022-44031
Marked as found in versions redmine/5.0.2-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1024785: marked as done (supysonic: (autopkgtest) needs update for python3.11: DecompileError: Unsupported operation)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 19:36:23 +
with message-id 
and subject line Bug#1024785: fixed in supysonic 0.7.2+ds-2
has caused the Debian Bug report #1024785,
regarding supysonic: (autopkgtest) needs update for python3.11: DecompileError: 
Unsupported operation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1024785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: supysonic
Version: 0.7.2+ds-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
supysonic fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
supysonic  from testing0.7.2+ds-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/armel/s/supysonic/28609595/log.gz

==
ERROR: test_get_album_list 
(tests.api.test_album_songs.AlbumSongsTestCase.test_get_album_list)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.umijt0w4/downtmp/autopkgtest_tmp/tests/api/test_album_songs.py", 
line 61, in test_get_album_list

self._make_request("getAlbumList", {"type": "kraken"}, error=0)
  File 
"/tmp/autopkgtest-lxc.umijt0w4/downtmp/autopkgtest_tmp/tests/api/apitestbase.py", 
line 74, in _make_request

rg = self.client.get(uri, query_string=args)
 ^^^
  File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 1129, in get
return self.open(*args, **kw)
   ^^
  File "/usr/lib/python3/dist-packages/flask/testing.py", line 235, in open
return super().open(
   ^
  File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 1074, in 
open

response = self.run_wsgi_app(request.environ, buffered=buffered)
   ^
  File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 945, in 
run_wsgi_app

rv = run_wsgi_app(self.application, environ, buffered=buffered)
 ^^
  File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 1231, in 
run_wsgi_app

app_rv = app(environ, start_response)
 
  File "/usr/lib/python3/dist-packages/flask/app.py", line 2091, in 
__call__

return self.wsgi_app(environ, start_response)
   ^^
  File "/usr/lib/python3/dist-packages/pony/utils/utils.py", line 35, 
in pony_wrapper

return caller(func, *args, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 519, in 
new_func

result = func(*args, **kwargs)
 ^
  File "/usr/lib/python3/dist-packages/flask/app.py", line 2076, in 
wsgi_app

response = self.handle_exception(e)
   
  File "/usr/lib/python3/dist-packages/flask/app.py", line 2073, in 
wsgi_app

response = self.full_dispatch_request()
   
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1518, in 
full_dispatch_request

rv = self.handle_user_exception(e)
 ^
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1516, in 
full_dispatch_request

rv = self.dispatch_request()
 ^^^
  File 

Bug#1026103: aflplusplus: FTBFS on s390x

[Kurt Roeckx]

Source: aflplusplus
Version: 4.04c-2
Severity: serious

Hi,

Your package is failing to build on s390x:
[*] Compiling afl++ for OS Linux on ARCH s390x
./test/unittests/unit_maybe_alloc
[==] Running 6 test(s).
[ RUN  ] test_pow2
[   OK ] test_pow2
[ RUN  ] test_null_allocs
[   OK ] test_null_allocs
[ RUN  ] test_nonpow2_size
[   OK ] test_nonpow2_size
[ RUN  ] test_zero_size
[   OK ] test_zero_size
[ RUN  ] test_unchanged_size
[   OK ] test_unchanged_size
[ RUN  ] test_grow_multiple
[   OK ] test_grow_multiple
[==] 6 test(s) run.
[  PASSED  ] 6 test(s).
./test/unittests/unit_preallocable
[==] Running 2 test(s).
[ RUN  ] test_alloc_free
[   OK ] test_alloc_free
[ RUN  ] test_prealloc_overflow
[   OK ] test_prealloc_overflow
[==] 2 test(s) run.
[  PASSED  ] 2 test(s).
./test/unittests/unit_list
[==] Running 3 test(s).
[ RUN  ] test_contains
[   OK ] test_contains
[ RUN  ] test_foreach
[   OK ] test_foreach
[ RUN  ] test_long_list
[   OK ] test_long_list
[==] 3 test(s) run.
[  PASSED  ] 3 test(s).
./test/unittests/unit_rand
[==] Running 2 test(s).
[ RUN  ] test_rand_0
[   OK ] test_rand_0
[ RUN  ] test_rand_below
[   OK ] test_rand_below
[==] 2 test(s) run.
[  PASSED  ] 2 test(s).
./test/unittests/unit_hash
[==] Running 1 test(s).
[ RUN  ] test_hash
[   OK ] test_hash
[==] 1 test(s) run.
[  PASSED  ] 1 test(s).
make[3]: Leaving directory '/<>'
␛[1;90m[*] 10 test cases completed.␛[0m
␛[1;93m[-] not all test cases were executed
␛[0;31m[!] failure in tests :-(␛[0m
make[2]: *** [GNUmakefile:343: tests] Error 1

It's not at all clear why it says: "failure in tests". All the test seem
to pass. Other architectures also have the "not all test cases were
executed" message.

I've tried to build it again on the buildds, but it failed the same way.


Kurt

Bug#1004784: aiscm: FTBFS with ffmpeg 5.0

[Bastian Germann]

Am 14.12.22 um 16:51 schrieb Jan Wedekind:

No, I didn't manage to fix it. Is it possible to remove the package?


Yes. But if you do not want to maintain it anymore, orphaning would usually the 
step that maintainers take.

Processed (with 5 errors): Re: Bug#1025025: ImportError: cannot import name 'Application' from 'cleo'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1025025
Bug #1025025 [python3-poetry] ImportError: cannot import name 'Application' 
from 'cleo'
Marked Bug as done
> I've used debian:bookworm Docker image.
Unknown command or malformed arguments to command.
> I rechecked it now, and problem seems to be solved:
Unknown command or malformed arguments to command.
> docker run  --rm -ti debian:bookworm
Unknown command or malformed arguments to command.
> # apt update && apt install -y python3-poetry
> # /usr/bin/poetry config virtualenvs.create false
> #
> Thank you very much for help.
Unknown command or malformed arguments to command.
> On 12/14/22 19:49, Emmanuel Arias wrote:
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
1025025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025025: ImportError: cannot import name 'Application' from 'cleo'

[George Shuklin]

close 1025025

I've used debian:bookworm Docker image.

I rechecked it now, and problem seems to be solved:

docker run  --rm -ti debian:bookworm

# apt update && apt install -y python3-poetry
# /usr/bin/poetry config virtualenvs.create false
#

Thank you very much for help.

On 12/14/22 19:49, Emmanuel Arias wrote:


Hi George,

Thanks for the report.

I assume that you are in testing. Please can you try again? 
python-cleo was migrated to testing

yesterday [0]

[0] 
https://tracker.debian.org/news/1398131/python-cleo-100a5-3-migrated-to-testing/


Please, let me know.

Cheers,
Emmanuel

On Fri, Dec 9, 2022 at 2:21 PM George Shuklin 
 wrote:


Unfortunately, 1.2.2+dfsg-1didn't fixed the problem:

dpkg -l|grep poetr
ii  python3-poetry  1.2.2+dfsg-1

/usr/bin/poetry config virtualenvs.create false
Traceback (most recent call last):
   File "/usr/bin/poetry", line 5, in 
 from poetry.console.application import main
   File
"/usr/lib/python3/dist-packages/poetry/console/application.py",
line 13, in 
 from cleo.events.console_events import COMMAND
ModuleNotFoundError: No module named 'cleo.events'

Processed: Bug#1024785 marked as pending in supysonic

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1024785 [src:supysonic] supysonic: (autopkgtest) needs update for 
python3.11: DecompileError: Unsupported operation
Added tag(s) pending.

-- 
1024785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1024785: marked as pending in supysonic

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #1024785 in supysonic 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/python-team/packages/supysonic/-/commit/0a4e6dde6fce76482a1dc8b6af8c5c88beec4c21


d/control: add versionned dependency on python3-pony. (Closes: #1024785)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024785

Bug#1026072: Fix for the bug

[Richard B. Kreckel]

I am having it too and downgrading to 107.0.1-1 fixes the problem.

It seems like someone was seeing something similar before and reported 
it here  but 
the bug got closed?


  -richy.
--
Richard B. Kreckel

Processed: Bug#1024812 marked as pending in ponyorm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1024812 [src:ponyorm] ponyorm FTBFS with Python 3.11 as supported version
Added tag(s) pending.

-- 
1024812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1024812: marked as pending in ponyorm

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #1024812 in ponyorm 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/python-team/packages/ponyorm/-/commit/e4a6d7985bdc2d06023bf111d8755cd2bccca87b


d/patches: add 0003 to fix Python 3.11 compatibility. (Closes: #1024812)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024812

Bug#1026097: lua-curl: there are no OPT_* constants in the module

[Aleksey]

Package: lua-curl
Version: 0.3.0-10
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After I updated from version 0.3.0-9.2, any call to the setopt function
began to fail with the error "Expecting a CURLoption value, got nil".
A little investigation showed that the module is missing any OPT_*
constants. Perhaps, not only these. For instance, in this code:

print(require("curl").OPT_URL)

I expect to get 10002, but get nil. Replacing the constants with their
numeric values doen't solve the problem either. Rollback to version
0.3.0-9.2 solves the problem.

I dug a little deeper into the package sources and I think that the
package was built with an empty curopt.h, which is mentioned here:
https://sources.debian.org/src/lua-curl/0.3.0-10/lua-curl.c/#L148

Regards, Aleksey A.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lua-curl depends on:
ii  libc62.36-6
ii  libcurl3-gnutls  7.86.0-2

lua-curl recommends no packages.

lua-curl suggests no packages.

-- no debconf information

Bug#1025025: ImportError: cannot import name 'Application' from 'cleo'

[Emmanuel Arias]

Hi George,

Thanks for the report.

I assume that you are in testing. Please can you try again? python-cleo was
migrated to testing
yesterday [0]

[0]
https://tracker.debian.org/news/1398131/python-cleo-100a5-3-migrated-to-testing/

Please, let me know.

Cheers,
Emmanuel

On Fri, Dec 9, 2022 at 2:21 PM George Shuklin 
wrote:

> Unfortunately, 1.2.2+dfsg-1didn't fixed the problem:
>
> dpkg -l|grep poetr
> ii  python3-poetry  1.2.2+dfsg-1
>
> /usr/bin/poetry config virtualenvs.create false
> Traceback (most recent call last):
>File "/usr/bin/poetry", line 5, in 
>  from poetry.console.application import main
>File "/usr/lib/python3/dist-packages/poetry/console/application.py",
> line 13, in 
>  from cleo.events.console_events import COMMAND
> ModuleNotFoundError: No module named 'cleo.events'
>
>

Bug#1026094: prometheus-ipmi-exporter: autopkgtest/build fails due to API change in prometheus exporter-toolkit

[Nick Rosbrook]

Package: prometheus-ipmi-exporter
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Dear Maintainer,

Recent API changes in the github.com/prometheus/exporter-toolkit/web
package, which are included in golang-github-prometheus-exporter-toolkit
0.8.2-1, cause the autopkgtest (and re-build) to fail.

This can be fixed by an upstream commit that adapts to the new API.

Thanks,
Nick
diff -Nru 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
--- 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
  1969-12-31 19:00:00.0 -0500
+++ 
prometheus-ipmi-exporter-1.6.1/debian/patches/02-fix-build-with-new-exporter-toolkit.patch
  2022-12-13 15:51:36.0 -0500
@@ -0,0 +1,33 @@
+Description: Fix build with golang-github-prometheus-exporter-toolkit 0.8.2
+Origin: upstream, 
https://github.com/prometheus-community/ipmi_exporter/commit/e8989cfdf79bebb2e3d84e43f65a7fc027ee7bba.patch
+Bug-Ubuntu: https://launchpad.net/bugs/1999574
+Last-Update: 2022-12-13
+---
+--- a/main.go
 b/main.go
+@@ -41,11 +41,7 @@
+   "freeipmi.path",
+   "Path to FreeIPMI executables.",
+   ).Default("/usr/sbin").String()
+-  listenAddress = kingpin.Flag(
+-  "web.listen-address",
+-  "Address to listen on for web interface and telemetry.",
+-  ).Default(":9290").String()
+-  webConfig = webflag.AddFlags(kingpin.CommandLine)
++  webConfig = webflag.AddFlags(kingpin.CommandLine, ":9290")
+ 
+   sc = {
+   C: {},
+@@ -169,10 +165,8 @@
+ `))
+   })
+ 
+-  level.Info(logger).Log("msg", "Listening on", "address", *listenAddress)
+-
+-  srv := {Addr: *listenAddress}
+-  if err := web.ListenAndServe(srv, *webConfig, logger); err != nil {
++  srv := {}
++  if err := web.ListenAndServe(srv, webConfig, logger); err != nil {
+   level.Error(logger).Log("msg", "HTTP listener stopped", 
"error", err)
+   os.Exit(1)
+   }
diff -Nru prometheus-ipmi-exporter-1.6.1/debian/patches/series 
prometheus-ipmi-exporter-1.6.1/debian/patches/series
--- prometheus-ipmi-exporter-1.6.1/debian/patches/series2022-06-22 
07:19:56.0 -0400
+++ prometheus-ipmi-exporter-1.6.1/debian/patches/series2022-12-13 
15:23:10.0 -0500
@@ -1 +1,2 @@
 01-debian-defaults.patch
+02-fix-build-with-new-exporter-toolkit.patch

Bug#1021991: marked as done (mumax3: does not use nvcc during build)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 17:08:23 +
with message-id 
and subject line Bug#1021991: fixed in mumax3 3.10-6
has caused the Debian Bug report #1021991,
regarding mumax3: does not use nvcc during build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1021991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mumax3
Version: 3.10-4
Severity: serious

Hi,

mumax3 has a build dependency on nvidia-cuda-toolkit, but does not call
nvcc during build to compile the .cu files. I don't think that is intended.

Please make the following additional packaging changes w.r.t. cuda:
* Use Build-Depends: nvidia-cuda-toolkit-gcc instead of nvidia-cuda-toolkit
  That results in a deterministic nvcc+gcc combination using the default
  cuda compatible GCC version as defined in src:nvidia-cuda-toolkit.
  It also provides the /usr/bin/cuda-{gcc,g++} symlinks.
* In case you need to set a host compiler for 'nvcc -ccbin  ...'
  (because e.g. your package build system picks an cuda-incompatible gcc
  version by default (i.e. /usr/bin/gcc aka gcc-12)), please use
  cuda-g++ (or cuda-gcc) and do not hardcode any version.

Andreas
--- End Message ---
--- Begin Message ---
Source: mumax3
Source-Version: 3.10-6
Done: Roland Mas 

We believe that the bug you reported is fixed in the latest version of
mumax3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roland Mas  (supplier of updated mumax3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 17:28:43 +0100
Source: mumax3
Architecture: source
Version: 3.10-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Roland Mas 
Closes: 1021991
Changes:
 mumax3 (3.10-6) unstable; urgency=medium
 .
   * Rebuild cuda2go wrappers from source during build to fix "does not use
 nvcc during build", thanks to Andreas Beckmann (Closes: #1021991).
Checksums-Sha1:
 9ef12dd49ed9b3c1d90d20637af4ed9dc06e2447 2011 mumax3_3.10-6.dsc
 a84b722bfa40f47ee1180bb0ee3a85d6a3bcea66 12672 mumax3_3.10-6.debian.tar.xz
 4829ee3e4bd825398cc382811477228ce2cd8a77 8676 mumax3_3.10-6_amd64.buildinfo
Checksums-Sha256:
 776f00e1350218e0e0416dafcec0387371106a1769773f65e8889e617916423b 2011 
mumax3_3.10-6.dsc
 b8a1214336e54bcda89495853ccb5f02ed985e7478ea6a3ba4ed1e20bdbb7d00 12672 
mumax3_3.10-6.debian.tar.xz
 7a98780ab721385638d027b6fd446568ae63cfdb4f2450fd8b1276aa39a83871 8676 
mumax3_3.10-6_amd64.buildinfo
Files:
 fe6162191ffa6a79933e2a4f9148632e 2011 contrib/science optional 
mumax3_3.10-6.dsc
 8e3f2c48c054f218636e863b6c8a54bc 12672 contrib/science optional 
mumax3_3.10-6.debian.tar.xz
 85fd73a7624fcee474c16054d1fa29e0 8676 contrib/science optional 
mumax3_3.10-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmOZ+koACgkQ0w3s0lmT
IvwMkw//dOU5c/b41dfWcOWYHDbXp3E9xqy7EUT3rkYMzSbx6zMULTmfb9cBF5lj
LTnFeMXm+IHU7qOOoaIcn1W5c4OSMpUsJfuaLkLHDWJ/Hfa43wnKhgXdWVYLhrb5
Ax+UIQK5MlLKJ6w4TD/vN0Ws/L/TA+ItFXY8Qws1F3gRGhk8Ke2WzJ6skbBeJMku
+CAskiE576eZjU6tyXlCLtoipjy9l3D7A6hO6y4HIazuIAJOQdOL7QDTxWUSMi8W
kutDRGuf3YM0A0WDHdkG986xXL0AoTGiz4egf14g15MTEf6SqqldLaXA7/O76bem
Jsjnv7CjIujqvkTwOZz/a6OJY1Mpv6YEJEP/q7Q6gf4Aln2uSy98LxrMXs6hLLnf
nkOHr8Nc7HhX1e6ZCdLOTucwvHeR27QGF+bm3PseaQl9Q2II3BB4g28Pnx6MRduz
DGO9hcxfBmKAj07xp+Nbf5EAI+bwIjD74pqk5v+DRg29IfKiHSUdHCXbM73Na5Dy
TRbg4v9XXdeZ5x2FYded5wqRTrY6lv7aRKH6Y2kzVklxXxWbWtbC8NyQRYugBE0Z
5fLQZwWKtdJvibQ4V7ykn/7d7f4SoN8vnFQYPIbEikzumIjp7kdRBBI4tRXMqxuG
Cb6r5osqhO/JCaw9imOVnExs8QAQNjCHz9/8zSaYGo1TqhYGBK0=
=p0TQ
-END PGP SIGNATURE End Message ---

Bug#1024860: marked as done (circuits: (autopkgtest) needs update for python3.11: cannot import name 'getargspec' from 'inspect')

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 16:49:42 +
with message-id 
and subject line Bug#1024860: fixed in circuits 3.2.2-1
has caused the Debian Bug report #1024860,
regarding circuits: (autopkgtest) needs update for python3.11: cannot import 
name 'getargspec' from 'inspect'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1024860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: circuits
Version: 3.1.0+ds1-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
circuits fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
circuits   from testing3.1.0+ds1-3
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/c/circuits/28706378/log.gz

Testing with python3.11:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/circuits/__init__.py", line 22, 
in 

from .core import Event
  File "/usr/lib/python3/dist-packages/circuits/core/__init__.py", line 
12, in 

from .bridge import Bridge
  File "/usr/lib/python3/dist-packages/circuits/core/bridge.py", line 
23, in 

from .handlers import handler
  File "/usr/lib/python3/dist-packages/circuits/core/handlers.py", line 
9, in 

from inspect import getargspec
ImportError: cannot import name 'getargspec' from 'inspect' 
(/usr/lib/python3.11/inspect.py)

autopkgtest [14:13:56]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: circuits
Source-Version: 3.2.2-1
Done: Daniele Tricoli 

We believe that the bug you reported is fixed in the latest version of
circuits, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniele Tricoli  (supplier of updated circuits package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 17:15:09 +0100
Source: circuits
Architecture: source
Version: 3.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Daniele Tricoli 
Closes: 1024860
Changes:
 circuits (3.2.2-1) unstable; urgency=medium
 .
   * New upstream version 3.2.2 (Closes: #1024860)
   * Watch the upstream github instead of the PyPI tarball.
   * Refresh patches.
   * debian/control
 - Add python3-setuptools-scm to Build-Depends.
 - Update Homepage field.
 - Bump Standards-Version to 4.6.1.0, no changes needed.
   * debian/copyright
 - Don't esclude built docs since they are not included anymore
 - Update copyright years.
 - Use my debian.org address.
Checksums-Sha1:
 0098f032967cf5ed9dbab2d9fecfe83d454d4f25 2146 circuits_3.2.2-1.dsc
 e07bbd7840b07d03c947f77a722faf0ef02987c2 425478 circuits_3.2.2.orig.tar.gz
 431fdc73d565e4d03905f17b311a371c5949f501 9848 circuits_3.2.2-1.debian.tar.xz
 f09e4c97070d207a3ddfc9d5ea1eb9146fdd7f8b 8398 circuits_3.2.2-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#1004784: aiscm: FTBFS with ffmpeg 5.0

[Jan Wedekind]

No, I didn't manage to fix it. Is it possible to remove the package?

On 13 December 2022 23:48:42 GMT, Bastian Germann  wrote:
>Is this fixed with 0.24.2? If so, please update the package.
>
>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Processed: tagging 1026083

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1026083 + upstream
Bug #1026083 {Done: Hans-Christoph Steiner } [ruby-loofah] 
Security: XSS bug in Loofah
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025872: installing greetd immediately reboots and prevents any logins

[duck]

Quack,

On 2022-12-11 09:20, Johannes Schauer Marin Rodrigues wrote:


 1. do not start the greetd service by default installing a package
should not result into logging out the currently active user


I only tested greetd in the console after having started my previous 
login manager and did not hit this problem but that's indeed an 
unpleasant behavior.
I had a quick look at lightdm and gdm3 and I don't see anything 
preventing them from doing the same thing.
Not starting is an option but I'd like to look around a little bit more 
before making a decision.



 2. provide a sensible default. Using $SHELL makes no sense when the
default shell of the user running greetd is /usr/sbin/nologin. 
Maybe

replace $SHELL with /bin/bash?


I tested agreety but did not check it again before the upload.
I'll try it with dash first, maybe we do not need a dependency on bash.

Thanks for the report, I hope to have this sorted out soon.
Regards.
\_o<

--
Marc Dequènes

Bug#1026072: Fix for the bug

[Michael Rasmussen]

Running the commands below solves the problem until a new package is
available for install:

sudo ln -s /usr/lib/x86_64-linux-gnu/libnssutil3.so /usr/lib/firefox/
sudo ln -s /usr/lib/x86_64-linux-gnu/libnss3.so /usr/lib/firefox/
sudo ln -s /usr/lib/x86_64-linux-gnu/libsmime3.so /usr/lib/firefox/
sudo ln -s /usr/lib/x86_64-linux-gnu/libssl3.so /usr/lib/firefox/


-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
https://pgp.key-server.io/pks/lookup?search=0xD3C9A00E
mir  datanom  net
https://pgp.key-server.io/pks/lookup?search=0xE501F51C
mir  miras  org
https://pgp.key-server.io/pks/lookup?search=0xE3E80917
--

'During times of universal deceit, telling the truth becomes a
revolutionary act.' -George Orwell

/usr/games/fortune -es says:
I just had my entire INTESTINAL TRACT coated with TEFLON!


pgprBG4YZOvJS.pgp
Description: OpenPGP digital signature

Bug#1017197: marked as done (haskell-pandoc-citeproc: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev (< 1.6), libghc-pandoc-dev (< 2.11), libghc-pandoc-types-dev (< 1.22))

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 15:46:38 +
with message-id 
and subject line Bug#997972: Removed package(s) from unstable
has caused the Debian Bug report #1017197,
regarding haskell-pandoc-citeproc: FTBFS: unsatisfiable build-dependencies: 
libghc-aeson-dev (< 1.6), libghc-pandoc-dev (< 2.11), libghc-pandoc-types-dev 
(< 1.22)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-pandoc-citeproc
Version: 0.17.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-hsyaml-dev (>= 0.2), libghc-hsyaml-dev 
> (<< 0.3), libghc-hsyaml-prof, libghc-hsyaml-aeson-dev (>= 0.2), 
> libghc-hsyaml-aeson-dev (<< 0.3), libghc-hsyaml-aeson-prof, libghc-aeson-dev 
> (>= 0.7), libghc-aeson-dev (<< 1.6), libghc-aeson-prof, 
> libghc-base-compat-dev (>= 0.9), libghc-base-compat-prof, 
> libghc-data-default-dev, libghc-data-default-prof, libghc-hs-bibutils-dev (>= 
> 6.4), libghc-hs-bibutils-prof, libghc-network-dev (<< 3.2), 
> libghc-network-prof, libghc-old-locale-dev, libghc-old-locale-prof, 
> libghc-pandoc-dev (>= 2.8), libghc-pandoc-dev (<< 2.11), libghc-pandoc-prof, 
> libghc-pandoc-types-dev (>= 1.20), libghc-pandoc-types-dev (<< 1.22), 
> libghc-pandoc-types-prof, libghc-setenv-dev (<< 0.2), libghc-setenv-dev (>= 
> 0.1), libghc-setenv-prof, libghc-split-dev, libghc-split-prof, 
> libghc-syb-dev, libghc-syb-prof, libghc-tagsoup-dev, libghc-tagsoup-prof, 
> libghc-temporary-dev (>= 1.1), libghc-text-icu-dev, libghc-text-icu-prof, 
> libghc-unordered-containers-dev (<< 0.3), libghc-unordered-containers-dev (>= 
> 0.2), libghc-unordered-containers-prof, libghc-vector-dev (>= 0.10), 
> libghc-vector-prof, libghc-xml-conduit-dev (>= 1.2), libghc-xml-conduit-dev 
> (<< 1.10), libghc-xml-conduit-prof, libghc-yaml-dev (>= 0.11), 
> libghc-yaml-prof, libghc-aeson-pretty-dev (>= 0.8), libghc-aeson-pretty-prof, 
> libghc-attoparsec-dev, libghc-attoparsec-prof, libghc-libyaml-dev, 
> libghc-libyaml-prof, libghc-safe-dev, libghc-safe-prof, build-essential, 
> fakeroot, ghc-doc, libghc-hsyaml-doc, libghc-hsyaml-aeson-doc, 
> libghc-aeson-doc, libghc-base-compat-doc, libghc-data-default-doc, 
> libghc-hs-bibutils-doc, libghc-network-doc, libghc-old-locale-doc, 
> libghc-pandoc-doc, libghc-pandoc-types-doc, libghc-setenv-doc, 
> libghc-split-doc, libghc-syb-doc, libghc-tagsoup-doc, libghc-text-icu-doc, 
> libghc-unordered-containers-doc, libghc-vector-doc, libghc-xml-conduit-doc, 
> libghc-yaml-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-hsyaml-dev (>= 0.2), libghc-hsyaml-dev 
> (<< 0.3), libghc-hsyaml-prof, libghc-hsyaml-aeson-dev (>= 0.2), 
> libghc-hsyaml-aeson-dev (<< 0.3), libghc-hsyaml-aeson-prof, libghc-aeson-dev 
> (>= 0.7), libghc-aeson-dev (<< 1.6), libghc-aeson-prof, 
> libghc-base-compat-dev (>= 0.9), libghc-base-compat-prof, 
> libghc-data-default-dev, libghc-data-default-prof, libghc-hs-bibutils-dev (>= 
> 6.4), libghc-hs-bibutils-prof, libghc-network-dev (<< 3.2), 
> libghc-network-prof, libghc-old-locale-dev, libghc-old-locale-prof, 
> libghc-pandoc-dev (>= 2.8), libghc-pandoc-dev (<< 2.11), libghc-pandoc-prof, 
> libghc-pandoc-types-dev (>= 1.20), libghc-pandoc-types-dev (<< 1.22), 
> libghc-pandoc-types-prof, libghc-setenv-dev (<< 0.2), libghc-setenv-dev (>= 
> 0.1), libghc-setenv-prof, libghc-split-dev, libghc-split-prof, 
> libghc-syb-dev, libghc-syb-prof, libghc-tagsoup-dev, libghc-tagsoup-prof, 
> libghc-temporary-dev (>= 1.1), libghc-text-icu-dev, libghc-text-icu-prof, 
> libghc-unordered-containers-dev (<< 0.3), libghc-unordered-containers-dev (>= 
> 0.2), libghc-unordered-containers-prof, libghc-vector-dev (>= 0.10), 
> libghc-vector-prof, libghc-xml-conduit-dev (>= 1.2), libghc-xml-conduit-dev 
> (<< 1.10), libghc-xml-conduit-prof, libghc-yaml-dev (>= 0.11), 
> libghc-yaml-prof, 

Bug#1022794: marked as done (libghc-highlighting-kate-doc: depends on non-existing haddock-interface-35)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 15:46:06 +
with message-id 
and subject line Bug#963737: Removed package(s) from unstable
has caused the Debian Bug report #1022794,
regarding libghc-highlighting-kate-doc: depends on non-existing 
haddock-interface-35
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1022794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-highlighting-kate-doc
Version: 0.6.4-6
Severity: serious

Hi,

libghc-highlighting-kate-doc depends on haddock-interface-35 which does
not exist in the archive.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.6.4-6+rm

Dear submitter,

as the package highlighting-kate has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/963737

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1026088: rdma-core: add mips64* to COHERENT_DMA_ARCHS

[YunQiang Su]

Yunqiang Su  于2022年12月14日周三 23:24写道：
>
> On Wed, 14 Dec 2022 22:47:53 +0800 YunQiang Su  wrote:
> > Source: rdma-core
> > Version: 33.2-1
> > Severity: serious
> > Tags: ftbfs
> >
> > Can you help to add the fellow 4 ports
> > mips64 mips64el mips64r6 mips64r6el
>
> mips mipsel mipsr6 mipsr6el
> are also needed.
>
> > to the list of
> > COHERENT_DMA_ARCHS
> > in debian/rules ?
> >
>
> Backport this patch can fix FTBFS on mipsel.
>
https://github.com/linux-rdma/rdma-core/commit/90a5793ec9a6b9462712d36d466042fa979249a9

> > --
> > YunQiang Su
> >
> >



-- 
YunQiang Su

Bug#1026088: rdma-core: add mips64* to COHERENT_DMA_ARCHS

[Yunqiang Su]

On Wed, 14 Dec 2022 22:47:53 +0800 YunQiang Su  wrote:
> Source: rdma-core
> Version: 33.2-1
> Severity: serious
> Tags: ftbfs
> 
> Can you help to add the fellow 4 ports
> mips64 mips64el mips64r6 mips64r6el

mips mipsel mipsr6 mipsr6el
are also needed.

> to the list of
> COHERENT_DMA_ARCHS
> in debian/rules ?
> 

Backport this patch can fix FTBFS on mipsel.

> -- 
> YunQiang Su
> 
> 

Bug#1026088: rdma-core: add mips64* to COHERENT_DMA_ARCHS

[YunQiang Su]

Source: rdma-core
Version: 33.2-1
Severity: serious
Tags: ftbfs

Can you help to add the fellow 4 ports
mips64 mips64el mips64r6 mips64r6el
to the list of
COHERENT_DMA_ARCHS
in debian/rules ?

-- 
YunQiang Su

Bug#1020527:

[Andreas Hasenack]

Hi,

any particular reason for not adopting the upstream patch, which fixes
the problem properly? Disabling the compiler/build flags that tripped
the error could have other consequences.

Bug#1025869: Acknowledgement (tigervnc-scraping-server: Under bookworm server fails to start. Gives error in Wrapper.pm)

[Mark]

Additional info:

TigerVNC says that this is an issue with Debian script, not an upstream issue 
with them.

https://github.com/TigerVNC/tigervnc/issues/1560#issuecomment-1351443752

Processed: notfixed 235576 in 1.9.1, fixed 235576 in 1.9.1-1, notfixed 216195 in 1.9.1, fixed 216195 in 1.9.1-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfixed 235576 1.9.1
Bug #235576 {Done: Paolo Greppi } [doxygen] doxygen: 
Fails to recognize class template members with changed parameter names
There is no source info for the package 'doxygen' at version '1.9.1' with 
architecture ''
Unable to make a source version for version '1.9.1'
No longer marked as fixed in versions 1.9.1.
> fixed 235576 1.9.1-1
Bug #235576 {Done: Paolo Greppi } [doxygen] doxygen: 
Fails to recognize class template members with changed parameter names
Marked as fixed in versions doxygen/1.9.1-1.
> notfixed 216195 1.9.1
Bug #216195 {Done: Paolo Greppi } [doxygen] doxygen: 
complaining about static functions being documented elsewhere
There is no source info for the package 'doxygen' at version '1.9.1' with 
architecture ''
Unable to make a source version for version '1.9.1'
No longer marked as fixed in versions 1.9.1.
> fixed 216195 1.9.1-1
Bug #216195 {Done: Paolo Greppi } [doxygen] doxygen: 
complaining about static functions being documented elsewhere
Marked as fixed in versions doxygen/1.9.1-1.
> tags 936393 - bullseye + bookworm
Bug #936393 {Done: Philippe SWARTVAGHER } [src:dia] dia: 
Python2 removal in sid/bullseye
Removed tag(s) bullseye.
Bug #936393 {Done: Philippe SWARTVAGHER } [src:dia] dia: 
Python2 removal in sid/bullseye
Added tag(s) bookworm.
> notfixed 743886 1.9.1
Bug #743886 {Done: Paolo Greppi } [doxygen] doxygen: 
Generates invalid LaTeX from structure with anonymous union
There is no source info for the package 'doxygen' at version '1.9.1' with 
architecture ''
Unable to make a source version for version '1.9.1'
No longer marked as fixed in versions 1.9.1.
> fixed 743886 1.9.1-1
Bug #743886 {Done: Paolo Greppi } [doxygen] doxygen: 
Generates invalid LaTeX from structure with anonymous union
Marked as fixed in versions doxygen/1.9.1-1.
> notfixed 869998 1.8.13
Bug #869998 {Done: Paolo Greppi } [doxygen] Jessie to 
Stretch regression of # support in Markdown links
There is no source info for the package 'doxygen' at version '1.8.13' with 
architecture ''
Unable to make a source version for version '1.8.13'
No longer marked as fixed in versions 1.8.13.
> fixed 869998 1.8.13-10
Bug #869998 {Done: Paolo Greppi } [doxygen] Jessie to 
Stretch regression of # support in Markdown links
Marked as fixed in versions doxygen/1.8.13-10.
> tags 945623 - bullseye
Bug #945623 {Done: Hugh McMaster } [src:cfengine3] 
cfengine3: Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 936765 - bullseye
Bug #936765 {Done: Chris Hofstaedtler } [src:jinja2] jinja2: 
Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 936994 - bullseye
Bug #936994 {Done: Bastian Germann } [src:markupsafe] 
markupsafe: Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 885800 - buster bullseye
Bug #885800 {Done: Philippe SWARTVAGHER } [src:dia] dia: 
Don't Build-Depend on libart
Removed tag(s) bullseye and buster.
> tags 943303 - bullseye
Bug #943303 {Done: Sebastian Ramacher } [src:yasm] yasm: 
Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 936908 - bullseye
Bug #936908 {Done: Boyuan Yang } [src:libpyzy] libpyzy: 
Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
216195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216195
235576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=235576
743886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743886
869998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869998
885800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885800
936393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936393
936765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936765
936908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936908
936994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936994
943303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943303
945623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026083: marked as done (Security: XSS bug in Loofah)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 13:42:59 +
with message-id 
and subject line Bug#1026083: fixed in ruby-loofah 2.19.1-1
has caused the Debian Bug report #1026083,
regarding Security: XSS bug in Loofah
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ruby-loofah
Version: 2.19.0-1
Severity: serious

control: affects -1 ruby-loofah/2.1.0
control: affects -1 ruby-loofah/2.7.0+dfsg-1
control: tags -1 fixed-upstream security help

An XSS issue has been discovered in Loofah:
https://github.com/flavorjones/loofah/security/advisories/GHSA-228g-948r-83gx

It is fixed in the upstream release v2.19.1.
--- End Message ---
--- Begin Message ---
Source: ruby-loofah
Source-Version: 2.19.1-1
Done: Hans-Christoph Steiner 

We believe that the bug you reported is fixed in the latest version of
ruby-loofah, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated ruby-loofah package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Dec 2022 13:36:17 +0100
Source: ruby-loofah
Architecture: source
Version: 2.19.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Hans-Christoph Steiner 
Closes: 1026083
Changes:
 ruby-loofah (2.19.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 2.19.1 (Closes: #1026083) (CVE-2022-23515)
Checksums-Sha1:
 e73f996106e40474cc50a57256d47f78ddef327a 1823 ruby-loofah_2.19.1-1.dsc
 f8677409dac451de4cb4dac81eab10b79c2ae8f0 24572 ruby-loofah_2.19.1.orig.tar.xz
 747a10958b8a3a730466df95430c8170d5e4155a 4088 
ruby-loofah_2.19.1-1.debian.tar.xz
 96a6f1bf02a7314cd1a1d0c09dec0fb6ebc1aeaf 12665 
ruby-loofah_2.19.1-1_source.buildinfo
Checksums-Sha256:
 86aa6fe5cf1249b2a1f4d13d1fbe10468a3e183e8fca3d0ab1888310d00f380e 1823 
ruby-loofah_2.19.1-1.dsc
 f80bcbddde17c5c6cbe4eb262e8336c75a236f6b71525cde3b5f52ea2eb7b2e7 24572 
ruby-loofah_2.19.1.orig.tar.xz
 81f859d725cb4b37ab28f6c67cc8200eb418067f9200715d5d0780cd12b40160 4088 
ruby-loofah_2.19.1-1.debian.tar.xz
 a838fdaa5c39badea9989dbcc1fef558b387c681d8b518096571df454cc8aefc 12665 
ruby-loofah_2.19.1-1_source.buildinfo
Files:
 2cd021a617e17004a18e8ad247c02dfe 1823 ruby optional ruby-loofah_2.19.1-1.dsc
 e90fdf270ff57fc75bca5f20f56c99e8 24572 ruby optional 
ruby-loofah_2.19.1.orig.tar.xz
 b3bca4e6af235aa44ed127cfb6a5e1ac 4088 ruby optional 
ruby-loofah_2.19.1-1.debian.tar.xz
 2f079fd122311fe5b64847e7024dd141 12665 ruby optional 
ruby-loofah_2.19.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAmOZxOQACgkQPhd4F7ob
m/rUYwf/YO8S4Ojw3+XL0+m9xl25k3eetpD5UkD3DbNELd4sxcTwMcsTO5gVn1wq
Tt7a0URwbqzqn0rFwJEJeyTPgAOU3GKcNkKkMbOsfQ8T0pO7XywkWlhs1YKX/Id/
Z+q9bSxfHzgaKNX6k2YyJup7pYb3YqAwdHFo5iiULvmz+TJ1vDyj9F5dxmBUqyZr
xG7JWvOlOXAl61JXeVnIFT8BSi/jodFri6e/D//dT2vdS3XC31azhynPvNoWNGeo
Q2ZIrNJQgNUxu1ryHWo2oF72B6rUqLQ42JlehyVhkRRLLjBNVrh/TcyXFliqrh4i
IbjFkkPD7eBF74UqipYPOjNcip02Fw==
=13Zh
-END PGP SIGNATURE End Message ---

Bug#1026071: marked as done (xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 14:38:51 +0100
with message-id 
and subject line [ftpmas...@ftp-master.debian.org: Accepted xorg-server 
2:21.1.5-1 (source) into unstable]
has caused the Debian Bug report #1026071,
regarding xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 
CVE-2022-46342 CVE-2022-46343 CVE-2022-46344
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg-server
Version: 2:21.1.4-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for xorg-server.

CVE-2022-4283[0]:
| xkb: reset the radio_groups pointer to NULL after freeing it

CVE-2022-46340[1]:
| Xtest: disallow GenericEvents in XTestSwapFakeInput

CVE-2022-46341[2]:
| Xi: disallow passive grabs with a detail > 255

CVE-2022-46342[3]:
| Xext: free the XvRTVideoNotify when turning off from the same client

CVE-2022-46343[4]:
| Xext: free the screen saver resource when replacing it

CVE-2022-46344[5]:
| Xi: avoid integer truncation in length check of ProcXIChangeProperty

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-4283
https://www.cve.org/CVERecord?id=CVE-2022-4283
[1] https://security-tracker.debian.org/tracker/CVE-2022-46340
https://www.cve.org/CVERecord?id=CVE-2022-46340
[2] https://security-tracker.debian.org/tracker/CVE-2022-46341
https://www.cve.org/CVERecord?id=CVE-2022-46341
[3] https://security-tracker.debian.org/tracker/CVE-2022-46342
https://www.cve.org/CVERecord?id=CVE-2022-46342
[4] https://security-tracker.debian.org/tracker/CVE-2022-46343
https://www.cve.org/CVERecord?id=CVE-2022-46343
[5] https://security-tracker.debian.org/tracker/CVE-2022-46344
https://www.cve.org/CVERecord?id=CVE-2022-46344
[6] https://lists.x.org/archives/xorg-announce/2022-December/003302.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xorg-server
Source-Version: 2:21.1.5-1

- Forwarded message from Debian FTP Masters 
 -

From: Debian FTP Masters 
Resent-From: debian-devel-chan...@lists.debian.org
Reply-To: debian-de...@lists.debian.org
Date: Wed, 14 Dec 2022 10:10:32 +
To: debian-devel-chan...@lists.debian.org
Subject: Accepted xorg-server 2:21.1.5-1 (source) into unstable
Message-Id: 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 11:10:24 +0200
Source: xorg-server
Built-For-Profiles: noudeb
Architecture: source
Version: 2:21.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Changes:
 xorg-server (2:21.1.5-1) unstable; urgency=medium
 .
   * New upstream release.
 - CVE-2022-46340, CVE-2022-46341, CVE-2022-46342, CVE-2022-46343,
   CVE-2022-46344, CVE-2022-46283
   * Add signing-key from Peter Hutterer.
Checksums-Sha1:
 9879f8698e606006d3c860870a54a11d2bad59ac 4207 xorg-server_21.1.5-1.dsc
 c5efdc5696815a8925e371b5237223f60c920568 8917627 xorg-server_21.1.5.orig.tar.gz
 e54e3660bcd95539a17841075f330a3a05a6a9bf 195 xorg-server_21.1.5.orig.tar.gz.asc
 a4e0502f05552a701fce55f8dcd23547f39ce122 169209 xorg-server_21.1.5-1.diff.gz
 e6d3bdb6bcbe24fd0d7531191dbf7086d40ba95f 10540 
xorg-server_21.1.5-1_source.buildinfo
Checksums-Sha256:
 40b27446f4a6c6d54b734a199f9f94f37d6b66092635d2ac018180e0678800ae 4207 
xorg-server_21.1.5-1.dsc
 5e391867bfe44ce766a8c748e7563dc9678c229af72b5f94e221a92b1b04b7a1 8917627 
xorg-server_21.1.5.orig.tar.gz
 e677f4436820c0863c2fb1043a498f81d9f6cfea808ced5bf5921686238cc1bb 195 
xorg-server_21.1.5.orig.tar.gz.asc
 735c73342e8a3b9b9b722837cf783a0bcf368aaf8b5f844a3f11c19bedb3b258 169209 
xorg-server_21.1.5-1.diff.gz
 90d9e9e338b615d58d48446e532dd7a5c175aa73207872ac51fbce9627cf8f03 10540 
xorg-server_21.1.5-1_source.buildinfo
Files:
 9b01577aea185661100ab83359d82492 4207 x11 optional xorg-server_21.1.5-1.dsc
 8afa3a9cb1cbe3101183eedc9773243f 8917627 x11 optional 
xorg-server_21.1.5.orig.tar.gz
 428b0a04ac6dd4ce330fcefe018f16cb 195 x11 optional 
xorg-server_21.1.5.orig.tar.gz.asc
 748b63932c6fc2c8637c3402f933d7a9 169209 x11 optional 
xorg-server_21.1.5-1.diff.gz
 c073e5207fd1a10192f148863a1b965a 10540 x11 optional 
xorg-server_21.1.5-1_source.buildinfo

Bug#1026071: xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344

[Salvatore Bonaccorso]

Hi Timo,

On Wed, Dec 14, 2022 at 12:01:53PM +0200, Timo Aaltonen wrote:
> Salvatore Bonaccorso kirjoitti 14.12.2022 klo 11.42:
> > > 
> > > btw, there's a typo in one of the CVE's, it's -46283 not -4283:
> > > 
> > > https://lists.x.org/archives/xorg-announce/2022-December/003302.html
> > > 
> > > the typo is also on the git commit but I fixed it on d/changelog
> > 
> > Should already be correct in above listing and security-tracker. But
> > right the final advisory upstream still has the typo.
> 
> Hmm so the announce mail was wrong and it's actually -4283?? These aren't
> public so I wasn't able to check, my bad..

Yes the 4-digit one is the correct one. Unfortunately the typo
apparently did still propagated to the official announce even it was
noticied before.

Regards,
Salvatore

Processed: tags

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> usertag 1026083 CVE-2022-23515
User is h...@eds.org
There were no usertags set.
Usertags are now: CVE-2022-23515.
> found 1026083 ruby-loofah/2.1.0
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
The source ruby-loofah and version 2.1.0 do not appear to match any binary 
packages
Marked as found in versions ruby-loofah/2.1.0.
> found 1026083 ruby-loofah/2.7.0+dfsg-1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Marked as found in versions ruby-loofah/2.7.0+dfsg-1.
> found 1026083 ruby-loofah/2.2.2-1~bpo9+1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Marked as found in versions ruby-loofah/2.2.2-1~bpo9+1.
> found 1026083 ruby-loofah/2.2.3-1+deb10u1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Marked as found in versions ruby-loofah/2.2.3-1+deb10u1.
> found 1026083 ruby-loofah/2.4.0+dfsg-1~bpo10+1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Marked as found in versions ruby-loofah/2.4.0+dfsg-1~bpo10+1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1026083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1026064  RM: haskell-blogliterately -- RoQA; RC-buggy; not released 
> since stretch; blocks 2 other removals
Bug #1026064 [src:haskell-blogliterately] RM: haskell-blogliterately -- RoQA; 
not released since stretch; blocks 2 other removals
Changed Bug title to 'RM: haskell-blogliterately -- RoQA; RC-buggy; not 
released since stretch; blocks 2 other removals' from 'RM: 
haskell-blogliterately -- RoQA; not released since stretch; blocks 2 other 
removals'.
> reassign 1026064 ftp.debian.org
Bug #1026064 [src:haskell-blogliterately] RM: haskell-blogliterately -- RoQA; 
RC-buggy; not released since stretch; blocks 2 other removals
Bug reassigned from package 'src:haskell-blogliterately' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1026064 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1026064 to the same values 
previously set
> retitle 963737 RM: highlighting-kate -- RoQA; RC-buggy; upstream deprecated; 
> alternatives exist
Bug #963737 [src:highlighting-kate] highlighting-kate: Removal notice: 
Deprecated
Changed Bug title to 'RM: highlighting-kate -- RoQA; RC-buggy; upstream 
deprecated; alternatives exist' from 'highlighting-kate: Removal notice: 
Deprecated'.
> reassign 963737 ftp.debian.org
Bug #963737 [src:highlighting-kate] RM: highlighting-kate -- RoQA; RC-buggy; 
upstream deprecated; alternatives exist
Bug reassigned from package 'src:highlighting-kate' to 'ftp.debian.org'.
No longer marked as found in versions highlighting-kate/0.6.4-5.
Ignoring request to alter fixed versions of bug #963737 to the same values 
previously set
> severity 963737 normal
Bug #963737 [ftp.debian.org] RM: highlighting-kate -- RoQA; RC-buggy; upstream 
deprecated; alternatives exist
Severity set to 'normal' from 'grave'
> tags 963737 - bookworm bullseye sid
Bug #963737 [ftp.debian.org] RM: highlighting-kate -- RoQA; RC-buggy; upstream 
deprecated; alternatives exist
Removed tag(s) sid, bookworm, and bullseye.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1026064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026064
963737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1026083 ruby-loofah/2.2.2-1~bpo9+1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Added indication that 1026083 affects ruby-loofah/2.2.2-1~bpo9+1
> affects 1026083 ruby-loofah/2.2.3-1+deb10u1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Added indication that 1026083 affects ruby-loofah/2.2.3-1+deb10u1
> affects 1026083 ruby-loofah/2.4.0+dfsg-1~bpo10+1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Added indication that 1026083 affects ruby-loofah/2.4.0+dfsg-1~bpo10+1
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1026083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tags

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1026083 ruby-loofah/2.1.0
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Added indication that 1026083 affects ruby-loofah/2.1.0
> affects 1026083 ruby-loofah/2.7.0+dfsg-1
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Added indication that 1026083 affects ruby-loofah/2.7.0+dfsg-1
> tags 1026083 fixed-upstream security help
Bug #1026083 [ruby-loofah] Security: XSS bug in Loofah
Added tag(s) fixed-upstream, help, and security.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1026083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1011540: marked as done (burp: autopkgtest regression with openssl 3)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 13:21:21 +0100
with message-id 
and subject line Re: burp: autopkgtest regression with openssl 3
has caused the Debian Bug report #1011540,
regarding burp: autopkgtest regression with openssl 3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1011540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: burp
Version: 2.4.0-3
Severity: serious
Tags: sid bookworm

burp's autopkgtest fail with openssl 3:

make[2]: Entering directory 
'/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src'
FAIL: runner

Testsuite summary for Burp 2.4.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to https://github.com/grke/burp/issues

make[2]: *** [Makefile:8640: test-suite.log] Error 1
make[2]: Leaving directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src'
make[1]: *** [Makefile:8748: check-TESTS] Error 2
make[1]: Leaving directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src'
make: *** [Makefile:8959: check-am] Error 2
autopkgtest [09:14:37]: test burp-unit-test: ---]


See
https://ci.debian.net/data/autopkgtest/testing/amd64/b/burp/22058117/log.gz

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

I've update burp to branch 3.*which fix the problem with openssl.

autopkgtest now is ok: https://ci.debian.net/packages/b/burp/

Thanks--- End Message ---

Bug#1026083: Security: XSS bug in Loofah

[Hans-Christoph Steiner]

Package: ruby-loofah
Version: 2.19.0-1
Severity: serious

control: affects -1 ruby-loofah/2.1.0
control: affects -1 ruby-loofah/2.7.0+dfsg-1
control: tags -1 fixed-upstream security help

An XSS issue has been discovered in Loofah:
https://github.com/flavorjones/loofah/security/advisories/GHSA-228g-948r-83gx

It is fixed in the upstream release v2.19.1.

Processed: Re: Bug#1025827: slic3r-prusa: FTBFS on armel mipsel powerpc riscv64 sh4 m68k

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025827 [src:slic3r-prusa] slic3r-prusa: FTBFS on armel mipsel powerpc 
riscv64 sh4 m68k
Severity set to 'serious' from 'important'

-- 
1025827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026068: marked as done (efibootguard: build fails if tests are disabled)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 11:35:41 +
with message-id 
and subject line Bug#1026068: fixed in efibootguard 0.12-2
has caused the Debian Bug report #1026068,
regarding efibootguard: build fails if tests are disabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: efibootguard
Version: 0.12-1
Severity: serious
tags: patch

Hello, it looks like you are using dh_auto_test to create manpages used during 
dh_auto_install target.
This is a bad thing to do, because if the user overrides the testsuite the 
build will fail.

The correct approach is to probably override dh auto build to create manpages 
(or even dh_auto_install)

and keep auto_test disabled, if you intend to do so.


The proposed patch is:
diff -Nru efibootguard-0.12/debian/changelog efibootguard-0.12/debian/changelog
--- efibootguard-0.12/debian/changelog  2022-09-01 08:50:34.0 +
+++ efibootguard-0.12/debian/changelog  2022-12-14 08:23:29.0 +
@@ -1,3 +1,10 @@
+efibootguard (0.12-1.1) unstable; urgency=medium
+
+  * Don't create manpages on test target, otherwise build
+fails if nocheck=true (Closes: #-1)
+
+ -- Gianfranco Costamagna   Wed, 14 Dec 2022 
09:23:29 +0100
+
 efibootguard (0.12-1) unstable; urgency=medium
 
   * Initial release (Closes: #1001214)

diff -Nru efibootguard-0.12/debian/rules efibootguard-0.12/debian/rules
--- efibootguard-0.12/debian/rules  2022-09-01 08:50:34.0 +
+++ efibootguard-0.12/debian/rules  2022-12-14 08:23:27.0 +
@@ -9,6 +9,9 @@
 
 # do not run the tests until fff is available in Debian

 override_dh_auto_test:
+
+override_dh_auto_build:
+   dh_auto_build
help2man -N -o bg_setenv.1   -n bg_setenv   ./bg_setenv
help2man -N -o bg_printenv.1 -n bg_printenv ./bg_printenv
help2man -N -o bg_gen_unified_kernel.1 
--version-string=v$(DEB_VERSION_UPSTREAM) tools/bg_gen_unified_kernel


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: efibootguard
Source-Version: 0.12-2
Done: Gylstorff Quirin 

We believe that the bug you reported is fixed in the latest version of
efibootguard, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gylstorff Quirin  (supplier of updated 
efibootguard package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Dec 2022 10:01:25 +0100
Source: efibootguard
Architecture: source
Version: 0.12-2
Distribution: unstable
Urgency: medium
Maintainer: Quirin Gylstorff 
Changed-By: Gylstorff Quirin 
Closes: 1026068
Changes:
 efibootguard (0.12-2) unstable; urgency=medium
 .
 * d/*.install: reorder content
 .
   [ Felix Moessbauer ]
 * fix lintian warning useless-whatis-entry
 * add multi-arch support to the package (Closes: #1026068)
Checksums-Sha1:
 fb7c0dab0b4ab7b10aea87cc6e37c060b9918948 1939 efibootguard_0.12-2.dsc
 3b655f470f9391d0ffa69887f829dbfd8e83cc1a 4504 efibootguard_0.12-2.debian.tar.xz
 28d29cb8f0caf4e5658de4bac1785f2c1f1709e9 5986 
efibootguard_0.12-2_source.buildinfo
Checksums-Sha256:
 2394f0b40bd14989a7e680fe8c8a6ce2cf7473a80c5b5fecb150d9712bd7f9ce 1939 
efibootguard_0.12-2.dsc
 b84e76ba848335b569ed0902101c5d3cce0a9ead90a71fd4f4a7dc27db2464aa 4504 
efibootguard_0.12-2.debian.tar.xz
 e1f1d42db81ba4350db5247b71c94722c72704fea0441becf238d00bdb98734f 5986 
efibootguard_0.12-2_source.buildinfo
Files:
 a98512e1e8e6194afe678e4b469ba756 1939 admin optional efibootguard_0.12-2.dsc
 9f300d69df242142bd0d35d8128dc015 4504 admin optional 
efibootguard_0.12-2.debian.tar.xz
 053d61da9b83f30823bcbdf1df434b95 5986 admin optional 
efibootguard_0.12-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOZqboQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOutC/9B0d2QBBqmXszONMTd2rQ3QYV70gHIe5wT
eTs0bQbsyXPeM7IsTL80nf0InW4KrGULEfwqlDFcRkNbL0sj9Qg025RC+H1nr3LR
e2s4uFR2L4ZnRRwJoyj/2bh9YHVeKWSisXuMY6htNrT6ROmFhBCZpUHmU8gh4Wxl

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 1026072 1026073 1026077
Bug #1026072 [firefox] firefox: fails to start (cannot load libnssutil3.so)
Bug #1026073 [firefox] firefox: failure at launch due to ldd problem
Bug #1026077 [firefox] firefox 108.0 fails to start
Merged 1026072 1026073 1026077
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026072
1026073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026073
1026077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972146: marked as done (/usr/share/applications/mono-runtime-common.desktop: should not handle MIME type by executing arbitrary code)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 10:54:34 +
with message-id 
and subject line Bug#972146: fixed in mono 6.8.0.105+dfsg-3.3
has caused the Debian Bug report #972146,
regarding /usr/share/applications/mono-runtime-common.desktop: should not 
handle MIME type by executing arbitrary code
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mono-runtime-common
Version: 6.8.0.105+dfsg-3
Severity: important
File: /usr/share/applications/mono-runtime-common.desktop
Tags: security
X-Debbugs-Cc: Debian Security Team 

/usr/share/applications/mono-runtime-common.desktop and
/usr/share/applications/mono-runtime-terminal.desktop are registered
as freedesktop.org MIME handlers for the application/x-ms-dos-executable
MIME type. They run the executable under mono(1) without any further
prompting. This means that doing normal "open a document" actions
will result in arbitrary code execution with normal user privileges:

- follow a web link to a downloadable file and accept the browser's
  offer to open it (mitigation: the user is prompted, and major
  browsers might special-case application/x-ms-dos-executable as
  particularly dangerous)
- follow a file:/// link in a non-web format that allows links, such
  as PDF
- open an email attachment
- xdg-desktop-portal forwarding an "open file" action from a Flatpak
  app (mitigation: this one involves user action to confirm which
  app should be used to open the file)

I don't think this is *necessarily* a security vulnerability, as such
(everything is doing what it is designed to do), but in 2020 it seems
deeply inadvisable. In particular, web browsers, email clients, and
sandboxed app frameworks like Flatpak and Snap, which are not generally
aware of the specifics of particular MIME types, have little choice but
to assume that opening a file is not normally arbitrary code execution.

The analogous MIME handling in Wine was removed in 2013
().

I would expect that Mono would either not handle
application/x-ms-dos-executable, or handle it with an application
that shows a "this is probably dangerous, are you sure?" prompt
first (like Wine used to do). I would personally prefer it
to not handle application/x-ms-dos-executable at all, due to
.

This was brought to my attention by a commit in GNOME's evince PDF
viewer which removes its "launch action" feature (part of the PDF spec,
but in practice mostly used by Windows malware) as a form of security
hardening. See 
(I'm preparing an upload with the change referenced there), which uses
mono in its proof-of-concept.

Mitigation: GNOME users will find that org.gnome.FileRoller.desktop is a
preferred handler for application/x-ms-dos-executable. It isn't clear to
me how useful this really is (opening an executable as a zip-like archive
with "filenames" like .text and .bss seems more like a proof-of-concept
than something people would genuinely use) but at least it's harmless.
MATE's equivalent (fork?) of file-roller, engrampa, does the same.

Another mitigation: I was surprised to find that gnome-games-app also
associates itself with application/x-ms-dos-executable, alongside lots
of ROM formats (presumably so it can offer to run them in a sandbox
environment with Dosbox). This is hopefully OK, because gnome-games-app
hopefully has a lot more prompting and sandboxing than a general-purpose
program interpreter.

smcv
--- End Message ---
--- Begin Message ---
Source: mono
Source-Version: 6.8.0.105+dfsg-3.3
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
mono, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated mono package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 14:33:03 +0100
Source: mono
Architecture: source

Bug#1026077: firefox 108.0 fails to start

[Dimitris T.]

Package: firefox
Version: 108.0-1
Severity: grave
Justification: renders package unusable

hey, 

after upgrading to firefox 108.0-1, firefox no longer starts.

console error :

$ firefox 
XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so:
/usr/lib/firefox/libnssutil3.so: cannot open shared object file: No such file 
or directory
Couldn't load XPCOM.

i think this has something to do with dependentlibs.list... : 

(firefox 108) cat /usr/lib/firefox/dependentlibs.list
libmozsandbox.so
liblgpllibs.so
libmozsqlite3.so
libmozgtk.so
libmozwayland.so
libnssutil3.so
libnss3.so
libsmime3.so
libssl3.so
libxul.so


after downgrading to firefox 107.0.1-1 from yesterdays snapshots.debian.org, 
firefox works agains as expected..
(firefox 107) cat /usr/lib/firefox/dependentlibs.list 
libmozsandbox.so
liblgpllibs.so
libmozsqlite3.so
libmozgtk.so
libmozwayland.so
libxul.so



thanks in advance,
d



-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages firefox depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.13.1-4.5
ii  libasound2   1.2.8-1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-6
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1devuan1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.3-1
ii  libgtk-3-0   3.24.35-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.85-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libstdc++6   12.2.0-10
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:4.0.2-2devuan1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec58  7:4.4.2-1+b3
ii  libavcodec59  7:5.1.2-1

Versions of packages firefox suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-1
pn  pulseaudio 

-- no debconf information

Bug#1024632: [Pkg-erlang-devel] Bug#1024632: Bug#1024632: Bug#1024632: erlang: CVE-2022-37026 Client Authentication Bypass

[Sergei Golovan]

Hi!

On Mon, Dec 12, 2022 at 5:27 PM Sergei Golovan  wrote:
>
> Hi Salvatore,
>
> On Fri, Dec 9, 2022 at 12:15 AM Salvatore Bonaccorso  
> wrote:
> >
> > The upcoming point release for 11.6 is scheduled for 17th with
> > uploading window closing the upcoming weekend. If we are confident
> > enough about potential regressions, can you make sure the fix land in
> > the next bullseye point release?
>
> Unfortunately, I've found a few regressions in the Erlang test suite,
> and I couldn't fix them myself yet. I'll try my best to do that
> tonight and tomorrow, but I'm afraid I'd suggest postponing uploading
> patched Erlang to stable.

I couldn't fix these regressions in the test suite, but it appears
that they are present
in the latest released Erlang 23 version (23.3.4.18) as well.
Therefore, I'm uploading the
fix to stable.

Cheers!
-- 
Sergei Golovan

Bug#1026071: xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344

[Timo Aaltonen]

Salvatore Bonaccorso kirjoitti 14.12.2022 klo 11.42:


btw, there's a typo in one of the CVE's, it's -46283 not -4283:

https://lists.x.org/archives/xorg-announce/2022-December/003302.html

the typo is also on the git commit but I fixed it on d/changelog


Should already be correct in above listing and security-tracker. But
right the final advisory upstream still has the typo.


Hmm so the announce mail was wrong and it's actually -4283?? These 
aren't public so I wasn't able to check, my bad..


--
t

Bug#1026072: Workaround

[Fiona Klute]

The bug affects a few more libraries. I found that creating symlinks for
all of them in /usr/lib/firefox/ is a workaround:

/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so

Bug#1026073: firefox: failure at launch due to ldd problem

[Grégory Mounié]

Package: firefox
Version: 108.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Firefox looks for some standard libraries (libnss3, libnssutil3, libsmime3,
libssl3) in /usr/lib/firefox

Launching firefox fails with (here when missing libsmime3):

XPCOMGlueLoad error for file /usr/lib/firefox/libsmime3.so:
/usr/lib/firefox/libsmime3.so: cannot open shared object file: No such file or
directory
Couldn't load XPCOM.

Workaround: add symbolic link one after the other in /usr/lib/firefox to
relevant /usr/lib/x86_64-linux-gnu/

cd /usr/lib/firefox
ln -s /usr/lib/x86_64-linux-gnu/libssl3.so .



-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.13.1-4.5
ii  libasound2   1.2.8-1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-6
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.4-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.3-1
ii  libgtk-3-0   3.24.35-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.85-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libstdc++6   12.2.0-10
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:4.0.2-2
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec-extra59 [libavcodec59]  7:5.1.2-1
ii  libavcodec58   7:4.4.2-1+b3

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-1
pn  pulseaudio 

-- no debconf information

Bug#1026072: firefox: fails to start (cannot load libnssutil3.so)

[Vincent Lefevre]

On 2022-12-14 10:26:39 +0100, Martin Dickopp wrote:
> When starting firefox, it displays the following message and exits 
> immediately with exit code 255:
> 
> XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so:
> /usr/lib/firefox/libnssutil3.so: cannot open shared object file: No such file 
> or directory
> Couldn't load XPCOM.

Same problem here.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1026071: xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344

[Salvatore Bonaccorso]

hi Timo,

On Wed, Dec 14, 2022 at 11:28:39AM +0200, Timo Aaltonen wrote:
> Salvatore Bonaccorso kirjoitti 14.12.2022 klo 11.19:
> > Source: xorg-server
> > Version: 2:21.1.4-3
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > 
> > 
> > Hi,
> > 
> > The following vulnerabilities were published for xorg-server.
> > 
> > CVE-2022-4283[0]:
> > | xkb: reset the radio_groups pointer to NULL after freeing it
> > 
> > CVE-2022-46340[1]:
> > | Xtest: disallow GenericEvents in XTestSwapFakeInput
> > 
> > CVE-2022-46341[2]:
> > | Xi: disallow passive grabs with a detail > 255
> > 
> > CVE-2022-46342[3]:
> > | Xext: free the XvRTVideoNotify when turning off from the same client
> > 
> > CVE-2022-46343[4]:
> > | Xext: free the screen saver resource when replacing it
> > 
> > CVE-2022-46344[5]:
> > | Xi: avoid integer truncation in length check of ProcXIChangeProperty
> > 
> > If you fix the vulnerabilities please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
> > 
> > For further information see:
> > 
> > [0] https://security-tracker.debian.org/tracker/CVE-2022-4283
> >  https://www.cve.org/CVERecord?id=CVE-2022-4283
> > [1] https://security-tracker.debian.org/tracker/CVE-2022-46340
> >  https://www.cve.org/CVERecord?id=CVE-2022-46340
> > [2] https://security-tracker.debian.org/tracker/CVE-2022-46341
> >  https://www.cve.org/CVERecord?id=CVE-2022-46341
> > [3] https://security-tracker.debian.org/tracker/CVE-2022-46342
> >  https://www.cve.org/CVERecord?id=CVE-2022-46342
> > [4] https://security-tracker.debian.org/tracker/CVE-2022-46343
> >  https://www.cve.org/CVERecord?id=CVE-2022-46343
> > [5] https://security-tracker.debian.org/tracker/CVE-2022-46344
> >  https://www.cve.org/CVERecord?id=CVE-2022-46344
> > [6] https://lists.x.org/archives/xorg-announce/2022-December/003302.html
> > 
> > Please adjust the affected versions in the BTS as needed.
> > 
> > Regards,
> > Salvatore
> > 
> 
> I've uploaded 21.1.5-1 ~20min ago :) All of these were referenced in the
> changelog.

hehe, thanks. I guess we had a race with filling the bug and the
upload. Thanks.
> 
> btw, there's a typo in one of the CVE's, it's -46283 not -4283:
> 
> https://lists.x.org/archives/xorg-announce/2022-December/003302.html
> 
> the typo is also on the git commit but I fixed it on d/changelog

Should already be correct in above listing and security-tracker. But
right the final advisory upstream still has the typo.

Regards,
Salvatore

Processed: mono: diff for NMU version 6.8.0.105+dfsg-3.3

[Debian Bug Tracking System]

Processing control commands:

> tags 972146 + patch
Bug #972146 [mono-runtime-common] 
/usr/share/applications/mono-runtime-common.desktop: should not handle MIME 
type by executing arbitrary code
Added tag(s) patch.

-- 
972146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972146: mono: diff for NMU version 6.8.0.105+dfsg-3.3

[Salvatore Bonaccorso]

Control: tags 972146 + patch


Dear maintainer,

I've prepared an NMU for mono (versioned as 6.8.0.105+dfsg-3.3). The diff
is attached to this message.

Regards,
Salvatore
diff -Nru mono-6.8.0.105+dfsg/debian/changelog mono-6.8.0.105+dfsg/debian/changelog
--- mono-6.8.0.105+dfsg/debian/changelog	2021-06-29 22:33:21.0 +0200
+++ mono-6.8.0.105+dfsg/debian/changelog	2022-12-09 14:33:03.0 +0100
@@ -1,3 +1,11 @@
+mono (6.8.0.105+dfsg-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Revert "Added desktop file for mono with and without a terminal window"
+(Closes: #972146)
+
+ -- Salvatore Bonaccorso   Fri, 09 Dec 2022 14:33:03 +0100
+
 mono (6.8.0.105+dfsg-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mono-6.8.0.105+dfsg/debian/mono-runtime-common.desktop mono-6.8.0.105+dfsg/debian/mono-runtime-common.desktop
--- mono-6.8.0.105+dfsg/debian/mono-runtime-common.desktop	2021-06-29 22:33:21.0 +0200
+++ mono-6.8.0.105+dfsg/debian/mono-runtime-common.desktop	1970-01-01 01:00:00.0 +0100
@@ -1,8 +0,0 @@
-[Desktop Entry]
-Name=Mono Runtime
-Exec=mono
-Terminal=false
-Type=Application
-Icon=mono-runtime-common
-MimeType=application/x-ms-dos-executable;
-NoDisplay=true
diff -Nru mono-6.8.0.105+dfsg/debian/mono-runtime-common.install mono-6.8.0.105+dfsg/debian/mono-runtime-common.install
--- mono-6.8.0.105+dfsg/debian/mono-runtime-common.install	2021-06-29 22:33:21.0 +0200
+++ mono-6.8.0.105+dfsg/debian/mono-runtime-common.install	2022-12-09 14:32:09.0 +0100
@@ -8,6 +8,3 @@
 /usr/lib/libMonoSupportW.so
 /usr/lib/libmono-native.so*
 /usr/bin/mono-hang-watchdog
-debian/mono-runtime-common.png /usr/share/pixmaps
-debian/mono-runtime-common.desktop /usr/share/applications
-debian/mono-runtime-terminal.desktop /usr/share/applications
Binary files /tmp/ocGH346p1X/mono-6.8.0.105+dfsg/debian/mono-runtime-common.png and /tmp/3QjcTjDqMs/mono-6.8.0.105+dfsg/debian/mono-runtime-common.png differ
diff -Nru mono-6.8.0.105+dfsg/debian/mono-runtime-terminal.desktop mono-6.8.0.105+dfsg/debian/mono-runtime-terminal.desktop
--- mono-6.8.0.105+dfsg/debian/mono-runtime-terminal.desktop	2021-06-29 22:33:21.0 +0200
+++ mono-6.8.0.105+dfsg/debian/mono-runtime-terminal.desktop	1970-01-01 01:00:00.0 +0100
@@ -1,8 +0,0 @@
-[Desktop Entry]
-Name=Mono Runtime (Terminal)
-Exec=mono
-Terminal=true
-Type=Application
-Icon=mono-runtime-common
-MimeType=application/x-ms-dos-executable;
-NoDisplay=true

Bug#1026071: xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344

[Timo Aaltonen]

Salvatore Bonaccorso kirjoitti 14.12.2022 klo 11.19:

Source: xorg-server
Version: 2:21.1.4-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for xorg-server.

CVE-2022-4283[0]:
| xkb: reset the radio_groups pointer to NULL after freeing it

CVE-2022-46340[1]:
| Xtest: disallow GenericEvents in XTestSwapFakeInput

CVE-2022-46341[2]:
| Xi: disallow passive grabs with a detail > 255

CVE-2022-46342[3]:
| Xext: free the XvRTVideoNotify when turning off from the same client

CVE-2022-46343[4]:
| Xext: free the screen saver resource when replacing it

CVE-2022-46344[5]:
| Xi: avoid integer truncation in length check of ProcXIChangeProperty

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-4283
 https://www.cve.org/CVERecord?id=CVE-2022-4283
[1] https://security-tracker.debian.org/tracker/CVE-2022-46340
 https://www.cve.org/CVERecord?id=CVE-2022-46340
[2] https://security-tracker.debian.org/tracker/CVE-2022-46341
 https://www.cve.org/CVERecord?id=CVE-2022-46341
[3] https://security-tracker.debian.org/tracker/CVE-2022-46342
 https://www.cve.org/CVERecord?id=CVE-2022-46342
[4] https://security-tracker.debian.org/tracker/CVE-2022-46343
 https://www.cve.org/CVERecord?id=CVE-2022-46343
[5] https://security-tracker.debian.org/tracker/CVE-2022-46344
 https://www.cve.org/CVERecord?id=CVE-2022-46344
[6] https://lists.x.org/archives/xorg-announce/2022-December/003302.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



I've uploaded 21.1.5-1 ~20min ago :) All of these were referenced in the 
changelog.


btw, there's a typo in one of the CVE's, it's -46283 not -4283:

https://lists.x.org/archives/xorg-announce/2022-December/003302.html

the typo is also on the git commit but I fixed it on d/changelog


--
t

Bug#1026072: firefox: fails to start (cannot load libnssutil3.so)

[Martin Dickopp]

Package: firefox
Version: 108.0-1
Severity: grave
Justification: renders package unusable

When starting firefox, it displays the following message and exits immediately 
with exit code 255:

XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so:
/usr/lib/firefox/libnssutil3.so: cannot open shared object file: No such file 
or directory
Couldn't load XPCOM.

-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.13.1-4.5
ii  libasound2   1.2.8-1
ii  libatk1.0-0  2.46.0-4
ii  libc62.36-6
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.4-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.2-1
ii  libgtk-3-0   3.24.35-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.85-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libstdc++6   12.2.0-9
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:3.3.17-7.1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec-extra58 [libavcodec58]  7:4.4.2-1+b3
ii  libavcodec59   7:5.1.2-1

Versions of packages firefox suggests:
pn  fonts-lmodern  
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-1
ii  pulseaudio 16.1+dfsg1-2+b1

-- no debconf information

Bug#1026071: xorg-server: CVE-2022-4283 CVE-2022-46340 CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344

[Salvatore Bonaccorso]

Source: xorg-server
Version: 2:21.1.4-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for xorg-server.

CVE-2022-4283[0]:
| xkb: reset the radio_groups pointer to NULL after freeing it

CVE-2022-46340[1]:
| Xtest: disallow GenericEvents in XTestSwapFakeInput

CVE-2022-46341[2]:
| Xi: disallow passive grabs with a detail > 255

CVE-2022-46342[3]:
| Xext: free the XvRTVideoNotify when turning off from the same client

CVE-2022-46343[4]:
| Xext: free the screen saver resource when replacing it

CVE-2022-46344[5]:
| Xi: avoid integer truncation in length check of ProcXIChangeProperty

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-4283
https://www.cve.org/CVERecord?id=CVE-2022-4283
[1] https://security-tracker.debian.org/tracker/CVE-2022-46340
https://www.cve.org/CVERecord?id=CVE-2022-46340
[2] https://security-tracker.debian.org/tracker/CVE-2022-46341
https://www.cve.org/CVERecord?id=CVE-2022-46341
[3] https://security-tracker.debian.org/tracker/CVE-2022-46342
https://www.cve.org/CVERecord?id=CVE-2022-46342
[4] https://security-tracker.debian.org/tracker/CVE-2022-46343
https://www.cve.org/CVERecord?id=CVE-2022-46343
[5] https://security-tracker.debian.org/tracker/CVE-2022-46344
https://www.cve.org/CVERecord?id=CVE-2022-46344
[6] https://lists.x.org/archives/xorg-announce/2022-December/003302.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1026068: efibootguard: build fails if tests are disabled

[Gylstorff Quirin]

Thanks for the reporting,

as efibootguard uses the fff test framework which is not available the 
intention was to disable all test. This should fix it:


-# do not run the tests until fff is available in Debian
-override_dh_auto_test:
+override_dh_auto_build:
+   dh_auto_build
help2man -N -o bg_setenv.1   -n bg_setenv   ./bg_setenv
help2man -N -o bg_printenv.1 -n bg_printenv ./bg_printenv
 	help2man -N -o bg_gen_unified_kernel.1 
--version-string=v$(DEB_VERSION_UPSTREAM) tools/bg_gen_unified_kernel

+
+# do not run the tests until fff is available in Debian
+override_dh_auto_test:
+   true


Quirin

On 12/14/22 09:26, Gianfranco Costamagna wrote:

Source: efibootguard
Version: 0.12-1
Severity: serious
tags: patch

Hello, it looks like you are using dh_auto_test to create manpages used 
during dh_auto_install target.
This is a bad thing to do, because if the user overrides the testsuite 
the build will fail.


The correct approach is to probably override dh auto build to create 
manpages (or even dh_auto_install)


and keep auto_test disabled, if you intend to do so.


The proposed patch is:
diff -Nru efibootguard-0.12/debian/changelog 
efibootguard-0.12/debian/changelog
--- efibootguard-0.12/debian/changelog    2022-09-01 08:50:34.0 
+
+++ efibootguard-0.12/debian/changelog    2022-12-14 08:23:29.0 
+

@@ -1,3 +1,10 @@
+efibootguard (0.12-1.1) unstable; urgency=medium
+
+  * Don't create manpages on test target, otherwise build
+    fails if nocheck=true (Closes: #-1)
+
+ -- Gianfranco Costamagna   Wed, 14 Dec 2022 
09:23:29 +0100

+
  efibootguard (0.12-1) unstable; urgency=medium

    * Initial release (Closes: #1001214)
diff -Nru efibootguard-0.12/debian/rules efibootguard-0.12/debian/rules
--- efibootguard-0.12/debian/rules    2022-09-01 08:50:34.0 +
+++ efibootguard-0.12/debian/rules    2022-12-14 08:23:27.0 +
@@ -9,6 +9,9 @@

  # do not run the tests until fff is available in Debian
  override_dh_auto_test:
+
+override_dh_auto_build:
+    dh_auto_build
  help2man -N -o bg_setenv.1   -n bg_setenv   ./bg_setenv
  help2man -N -o bg_printenv.1 -n bg_printenv ./bg_printenv
  help2man -N -o bg_gen_unified_kernel.1 
--version-string=v$(DEB_VERSION_UPSTREAM) tools/bg_gen_unified_kernel

Bug#1026056: marked as done (swi-prolog breaks logol autopkgtest: Program exited with wrong status code)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 09:11:27 +
with message-id 
and subject line Bug#1026056: fixed in logol 1.7.9+dfsg-6
has caused the Debian Bug report #1026056,
regarding swi-prolog breaks logol autopkgtest: Program exited with wrong status 
code
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: swi-prolog, logol
Control: found -1 swi-prolog/9.0.2+dfsg-1
Control: found -1 logol/1.7.9+dfsg-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of swi-prolog the autopkgtest of logol fails in 
testing when that autopkgtest is run with the binary packages of 
swi-prolog from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
swi-prolog from testing9.0.2+dfsg-1
logol  from testing1.7.9+dfsg-5
all others from testingfrom testing

I copied some of the output at the bottom of this report. The issue 
*looks* similar to bug 1022253, but now on all architectures.


Currently this regression is blocking the migration of swi-prolog to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=swi-prolog

https://ci.debian.net/data/autopkgtest/testing/amd64/l/logol/29303003/log.gz

calling logol with parameters -g 1799.logol -s 1799.fasta -dna
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /var/log/logol/logol.log (Permission denied)
at java.base/java.io.FileOutputStream.open0(Native Method)
at java.base/java.io.FileOutputStream.open(FileOutputStream.java:293)
at java.base/java.io.FileOutputStream.(FileOutputStream.java:235)
at java.base/java.io.FileOutputStream.(FileOutputStream.java:155)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
	at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
	at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
	at 
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
	at 
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
	at 
org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672)
	at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516)
	at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
	at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)

at org.apache.log4j.LogManager.(LogManager.java:127)
at org.apache.log4j.Logger.getLogger(Logger.java:117)
at org.irisa.genouest.logol.Logol.(Unknown Source)
For help, use option -h
INFO org.irisa.genouest.logol.Logol  - Using configuration file: 
/usr/share/logol/prolog/logol.properties

INFO org.irisa.genouest.logol.Logol  - option g called with 1799.logol
INFO org.irisa.genouest.logol.Logol  - option s called with 1799.fasta
INFO org.irisa.genouest.logol.Logol  - No maximum solutions defined, 
using defaults

INFO org.irisa.genouest.logol.Logol  - option dna called
INFO org.irisa.genouest.logol.Logol  - Start analyse to create grammar 
analyser

Executing prolog for pre-analyse
java.io.FileNotFoundException: 
/tmp/1799.logol.38da5a9d-c2ac-4a7d-8eb3-8c05b42f5c04.pre.res (No such 
file or directory)

at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(FileInputStream.java:216)
at java.base/java.io.FileInputStream.(FileInputStream.java:157)
at java.base/java.io.FileReader.(FileReader.java:75)
at org.irisa.genouest.logol.Logol.loadVariables2Postpone(Unknown Source)
at org.irisa.genouest.logol.Logol.generatePreAnalysis(Unknown Source)
at org.irisa.genouest.logol.Logol.analyse(Unknown Source)
at org.irisa.genouest.logol.Logol.execute(Unknown 

Bug#1026069: Cannot find symbols during build

[martin f krafft]

Package: scrcpy
Version: 1.24-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Running `apt build-dep scrcpy` and `fakeroot debian/rules binary` 
results in plenty of unresolvable symbols.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages scrcpy depends on:
ii  libavcodec59   7:5.1.2-1
ii  libavdevice59  7:5.1.2-1
ii  libavformat59  7:5.1.2-1
ii  libavutil577:5.1.2-1
ii  libc6  2.36-6
ii  libsdl2-2.0-0  2.26.0+dfsg-1
ii  libusb-1.0-0   2:1.0.26-1
ii  scrcpy-server  1.24-1

Versions of packages scrcpy recommends:
ii  adb  1:29.0.6-21

scrcpy suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems

Bug#1003432: marked as done (php-wmerrors: Incompatible with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Wed, 14 Dec 2022 08:46:05 +
with message-id 
and subject line Bug#1003432: fixed in php-wmerrors 2.0.0~git20221212.631dedd-1
has caused the Debian Bug report #1003432,
regarding php-wmerrors: Incompatible with PHP 8.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1003432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-wmerrors
Version: 2.0.0~git20190628.183ef7d-3
Severity: serious
Tags: ftbfs upstream
Justification: ftbfs
X-Debbugs-Cc: lego...@debian.org

wmerrors is currently incompatible with PHP 8.1.

https://phabricator.wikimedia.org/T298421 tracks this upstream and I'm
working on a patch there.


-- System Information:
Debian Release: 11.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.156-1.fc25.qubes.x86_64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php-wmerrors depends on:
ii  libc62.31-13+deb11u2
pn  php | php-cli
ii  php-common   2:76
ii  php7.4-cli [phpapi-20190902] 7.4.25-1+deb11u1
ii  php7.4-phpdbg [phpapi-20190902]  7.4.25-1+deb11u1

php-wmerrors recommends no packages.

php-wmerrors suggests no packages.
--- End Message ---
--- Begin Message ---
Source: php-wmerrors
Source-Version: 2.0.0~git20221212.631dedd-1
Done: Kunal Mehta 

We believe that the bug you reported is fixed in the latest version of
php-wmerrors, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated php-wmerrors package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Dec 2022 02:53:34 -0500
Source: php-wmerrors
Architecture: source
Version: 2.0.0~git20221212.631dedd-1
Distribution: unstable
Urgency: medium
Maintainer: MediaWiki packaging team 
Changed-By: Kunal Mehta 
Closes: 1003432
Changes:
 php-wmerrors (2.0.0~git20221212.631dedd-1) unstable; urgency=medium
 .
   * New upstream version 2.0.0~git20221212.631dedd
   * Add PHP 8.0+ support (Closes: #1003432)
Checksums-Sha1:
 dab169c5f950415f37a2d61e3f045993bc8d5c04 2199 
php-wmerrors_2.0.0~git20221212.631dedd-1.dsc
 5a330124fd2c6b3a2c8e1007eebaf6ed3f8c84e9 9528 
php-wmerrors_2.0.0~git20221212.631dedd.orig.tar.xz
 ee3b6827fab3198be01cdc42a578a66456b3b921 2568 
php-wmerrors_2.0.0~git20221212.631dedd-1.debian.tar.xz
 6fcade5877d64c1f57669a4a30127472f6e11882 7347 
php-wmerrors_2.0.0~git20221212.631dedd-1_amd64.buildinfo
Checksums-Sha256:
 42cb06f90613906c157b379e1b144a7b1b708e29bee1ebd67d643b5fd2f22914 2199 
php-wmerrors_2.0.0~git20221212.631dedd-1.dsc
 e89528d874fc3555d865d70379562e1ac24f1302d6cb48c0eec50aca2f3d676b 9528 
php-wmerrors_2.0.0~git20221212.631dedd.orig.tar.xz
 19dd3c87f619b1c8bcf118805f898d4febfaf888642b867c5cfd6fc12fff0284 2568 
php-wmerrors_2.0.0~git20221212.631dedd-1.debian.tar.xz
 ae250c523b4cb1930562a9315f11e5a90c0877cbf65e7a5526b58b47f2e467a5 7347 
php-wmerrors_2.0.0~git20221212.631dedd-1_amd64.buildinfo
Files:
 41a825c60f8bafe8a9e38bf271d114ad 2199 php optional 
php-wmerrors_2.0.0~git20221212.631dedd-1.dsc
 a95cf0f86cf0cea8bb9f0886f4d3ff77 9528 php optional 
php-wmerrors_2.0.0~git20221212.631dedd.orig.tar.xz
 806c9da60b0bcf5853894d68bedd9e2a 2568 php optional 
php-wmerrors_2.0.0~git20221212.631dedd-1.debian.tar.xz
 96caf0ffc25dbdd58b6f8bcece633c5d 7347 php optional 
php-wmerrors_2.0.0~git20221212.631dedd-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmOZgmUTHGxlZ29rdG1A
cmlzZXVwLm5ldAAKCRDxBfgQGwUmm/9lD/97n5fL8Y9vAkvBHxIefscBHxq4+MH+
9QHcHi9BM69gbdImz8fIXFv77dzGnsbDGGULcFWvT1xoLPfTBzWyPLY25VEVcenL
Rd/m/l+ZBTykuUR9Sb6NmWZjVzj7tgBolukRPqIaJ/bOVcH2HuIpIwX0Q1fDjicD
+c4o+Y6dy3Nn9JOoeXhMAZ5gYbxk7ewp51x8vYeqm4OWGkzahaZuKMKwCHUldOR1

Bug#1026056: swi-prolog breaks logol autopkgtest: Program exited with wrong status code

[olivier sallou]

after investigation, logol does not find anymore libswipl.so.8, need
version providing .so.9

compiled program link to .so.x versions, forcing package recompilation

Le mar. 13 déc. 2022 à 22:03, Paul Gevers  a écrit :

> Source: swi-prolog, logol
> Control: found -1 swi-prolog/9.0.2+dfsg-1
> Control: found -1 logol/1.7.9+dfsg-5
> Severity: serious
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
>
> Dear maintainer(s),
>
> With a recent upload of swi-prolog the autopkgtest of logol fails in
> testing when that autopkgtest is run with the binary packages of
> swi-prolog from unstable. It passes when run with only packages from
> testing. In tabular form:
>
> passfail
> swi-prolog from testing9.0.2+dfsg-1
> logol  from testing1.7.9+dfsg-5
> all others from testingfrom testing
>
> I copied some of the output at the bottom of this report. The issue
> *looks* similar to bug 1022253, but now on all architectures.
>
> Currently this regression is blocking the migration of swi-prolog to
> testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the right package?
>
> More information about this bug and the reason for filing it can be found
> on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=swi-prolog
>
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/logol/29303003/log.gz
>
> calling logol with parameters -g 1799.logol -s 1799.fasta -dna
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /var/log/logol/logol.log (Permission denied)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io
> .FileOutputStream.open(FileOutputStream.java:293)
> at java.base/java.io
> .FileOutputStream.(FileOutputStream.java:235)
> at java.base/java.io
> .FileOutputStream.(FileOutputStream.java:155)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at
>
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
> at
>
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> at
>
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> at
>
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
>
> org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672)
> at
>
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516)
> at
>
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
>
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> at org.apache.log4j.LogManager.(LogManager.java:127)
> at org.apache.log4j.Logger.getLogger(Logger.java:117)
> at org.irisa.genouest.logol.Logol.(Unknown Source)
> For help, use option -h
> INFO org.irisa.genouest.logol.Logol  - Using configuration file:
> /usr/share/logol/prolog/logol.properties
> INFO org.irisa.genouest.logol.Logol  - option g called with 1799.logol
> INFO org.irisa.genouest.logol.Logol  - option s called with 1799.fasta
> INFO org.irisa.genouest.logol.Logol  - No maximum solutions defined,
> using defaults
> INFO org.irisa.genouest.logol.Logol  - option dna called
> INFO org.irisa.genouest.logol.Logol  - Start analyse to create grammar
> analyser
> Executing prolog for pre-analyse
> java.io.FileNotFoundException:
> /tmp/1799.logol.38da5a9d-c2ac-4a7d-8eb3-8c05b42f5c04.pre.res (No such
> file or directory)
> at java.base/java.io.FileInputStream.open0(Native Method)
> at java.base/java.io
> .FileInputStream.open(FileInputStream.java:216)
> at java.base/java.io
> .FileInputStream.(FileInputStream.java:157)
> at java.base/java.io.FileReader.(FileReader.java:75)
> at org.irisa.genouest.logol.Logol.loadVariables2Postpone(Unknown
> Source)
> at org.irisa.genouest.logol.Logol.generatePreAnalysis(Unknown
> Source)
> at org.irisa.genouest.logol.Logol.analyse(Unknown Source)
> at org.irisa.genouest.logol.Logol.execute(Unknown Source)
> at org.irisa.genouest.logol.Logol.main(Unknown Source)
> INFO org.irisa.genouest.logol.Logol  - Analyse in progress..
> WARN org.irisa.genouest.logol.SequenceAnalyser  - Path to suffix search
> tool is not set in system environment. Will try to execute directly but
> may fail if not in PATH of current user
> Exception in thread "main" 

Bug#1026068: efibootguard: build fails if tests are disabled

[Gianfranco Costamagna]

Source: efibootguard
Version: 0.12-1
Severity: serious
tags: patch

Hello, it looks like you are using dh_auto_test to create manpages used during 
dh_auto_install target.
This is a bad thing to do, because if the user overrides the testsuite the 
build will fail.

The correct approach is to probably override dh auto build to create manpages 
(or even dh_auto_install)

and keep auto_test disabled, if you intend to do so.


The proposed patch is:
diff -Nru efibootguard-0.12/debian/changelog efibootguard-0.12/debian/changelog
--- efibootguard-0.12/debian/changelog  2022-09-01 08:50:34.0 +
+++ efibootguard-0.12/debian/changelog  2022-12-14 08:23:29.0 +
@@ -1,3 +1,10 @@
+efibootguard (0.12-1.1) unstable; urgency=medium
+
+  * Don't create manpages on test target, otherwise build
+fails if nocheck=true (Closes: #-1)
+
+ -- Gianfranco Costamagna   Wed, 14 Dec 2022 
09:23:29 +0100
+
 efibootguard (0.12-1) unstable; urgency=medium
 
   * Initial release (Closes: #1001214)

diff -Nru efibootguard-0.12/debian/rules efibootguard-0.12/debian/rules
--- efibootguard-0.12/debian/rules  2022-09-01 08:50:34.0 +
+++ efibootguard-0.12/debian/rules  2022-12-14 08:23:27.0 +
@@ -9,6 +9,9 @@
 
 # do not run the tests until fff is available in Debian

 override_dh_auto_test:
+
+override_dh_auto_build:
+   dh_auto_build
help2man -N -o bg_setenv.1   -n bg_setenv   ./bg_setenv
help2man -N -o bg_printenv.1 -n bg_printenv ./bg_printenv
help2man -N -o bg_gen_unified_kernel.1 
--version-string=v$(DEB_VERSION_UPSTREAM) tools/bg_gen_unified_kernel


OpenPGP_signature
Description: OpenPGP digital signature