Processed: bug 1022211 is forwarded to https://github.com/ietf-tools/xml2rfc/issues/921

[Debian Bug Tracking System]

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

> forwarded 1022211 https://github.com/ietf-tools/xml2rfc/issues/921
Bug #1022211 [xml2rfc] xml2rfc: Test failures with Weasyprint 57.0
Set Bug forwarded-to-address to 
'https://github.com/ietf-tools/xml2rfc/issues/921'.
> thanks
Stopping processing here.

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

Bug#1022211: xml2rfc: Test failures with Weasyprint 57.0

[Scott Kitterman]

Package: xml2rfc
Version: 3.13.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Using FTBFS as it's the closest thing we have to an autopkgtest
regression severity.  xml2rfc autopkgtest fails in Unstable with
Weasyprint 57.0:

==
ERROR: setUpClass (__main__.PdfWriterTests)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.48kx6p_4/downtmp/build.obL/src/xxx/test.py", line 
495, in setUpClass
cls.elements_pdfxml = xmldoc(None, bytes=elements_pdfdoc)
  File "/usr/lib/python3/dist-packages/xml2rfc/walkpdf.py", line 96, in xmldoc
return lxml.etree.fromstring(text)
  File "src/lxml/etree.pyx", line 3254, in lxml.etree.fromstring
  File "src/lxml/parser.pxi", line 1913, in lxml.etree._parseMemoryDocument
  File "src/lxml/parser.pxi", line 1793, in lxml.etree._parseDoc
  File "src/lxml/parser.pxi", line 1082, in 
lxml.etree._BaseParser._parseUnicodeDoc
  File "src/lxml/parser.pxi", line 615, in 
lxml.etree._ParserContext._handleParseResultDoc
  File "src/lxml/parser.pxi", line 725, in lxml.etree._handleParseResult
  File "src/lxml/parser.pxi", line 654, in lxml.etree._raiseParseError
  File "", line 14199
lxml.etree.XMLSyntaxError: PCDATA invalid Char value 23, line 14199, column 11

--
Ran 42 tests in 21.851s

FAILED (errors=1)

https://ci.debian.net/data/autopkgtest/testing/amd64/x/xml2rfc/27394437/log.gz

Upstream is apparently aware since (I discovered after uploading
Weasyprint) they have recently pinned the Weasyprint dependency to
<57.0.

I did file an issue upstream:

https://github.com/ietf-tools/xml2rfc/issues/921

Scott K

Bug#1018754: telegram-cli: Outdated app that is no longer supported

[Ying-Chun Liu (PaulLiu)]

Hi Axel,

Neither szqdong nor kenorb-contrib is working.
I've tried both.

1. Purge libtgl*, telegram-cli, libtl-parser*, tl-parser.
2. git clone --recursive 
3. ./configure; make
4. ./bin/telegram-cli

And both of them are not working. So I think we might need to really 
look into what causes the failure.


Yours,
Paul

On 2022/10/21 17:05, Axel Beckert wrote:

Hi,

aexlfow...@web.de wrote:

when I start the program it asks for my phone number. When I give it it
says following:
  *** 1661844939.688455 Notification API_64BIT_LOGIN_APP_OUTDATED_39:
You are using an outdated app that is no longer supported. To access
your messages, please update your app to the latest version.

[…]

I don't think it will be fixed,


The original developer clearly seems to have stalled working on it:

https://github.com/vysheng/tg says last commit was on Mar 23, 2016.

But there seem at least two very active forks:

* https://github.com/szqdong/tg
* https://github.com/kenorb-contrib/tg

Last commit in both is from 2022 Jul 26. (It's the same commit of
kenorb — not kenorb-contrib — in both cases.)

I'm though not sure which of these would be better to base the package
on in the future.

Bastian Germann wrote:

Setting appropriate severity. The application is not usable.


Thanks!

Regards, Axel


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021898: marked as done (sfepy: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 22:27:38 +
with message-id 
and subject line Bug#1021898: fixed in sfepy 2021.4-3
has caused the Debian Bug report #1021898,
regarding sfepy: FTBFS: distutils.errors.DistutilsSetupError: each element of 
'ext_modules' option must be an Extension instance or 2-tuple
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.)


-- 
1021898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sfepy
Version: 2021.4-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sfepy=amd64=2021.4-1%2Bb1=1665944538=0

Traceback (most recent call last):
  File "/<>/setup.py", line 252, in 
setup_package()
  File "/<>/setup.py", line 230, in setup_package
setup(name='sfepy',
  File "/usr/lib/python3/dist-packages/numpy/distutils/core.py", line 169, in 
setup
return old_setup(**new_attr)
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
973, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
992, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build.py", line 
61, in run
old_build.run(self)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", 
line 132, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 319, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
992, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build_src.py", 
line 144, in run
self.build_sources()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build_src.py", 
line 158, in build_sources
self.check_extensions_list(self.extensions)
  File "/usr/lib/python3.10/distutils/command/build_ext.py", line 362, in 
check_extensions_list
raise DistutilsSetupError(
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit 
code 13


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: sfepy
Source-Version: 2021.4-3
Done: Anton Gladky 

We believe that the bug you reported is fixed in the latest version of
sfepy, 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.
Anton Gladky  (supplier of updated sfepy 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, 21 Oct 2022 23:36:32 +0200
Source: sfepy
Architecture: source
Version: 2021.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 1021898
Changes:
 sfepy (2021.4-3) unstable; urgency=medium
 .
   * [5b62353] Fix FTBFS due to the import module order. (Closes: #1021898)
Checksums-Sha1:
 354684416524cd422a63a9de8ffbac38967e0977 2468 sfepy_2021.4-3.dsc
 a9e4cdc8b71b8afb50e23d098e154e556e22730a 7080 sfepy_2021.4-3.debian.tar.xz
 6ab07c56be3b570e584a1bbcb02a42fee39464c4 14039 sfepy_2021.4-3_source.buildinfo
Checksums-Sha256:
 e70e5a0cd62b145c33db3cf0f9bbdbbea0b98d267f523b8ce7d6f8ee79e04f2a 

Bug#1022204: FTBFS because nimgrep needs libpcre3

[Sergio Durigan Junior]

On Friday, October 21 2022, I wrote:

> I will soon attach a patch to fix the problem.

Here it is.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff --git a/debian/changelog b/debian/changelog
index f8dd0ad79..8654f42cb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+nim (1.6.8-2) UNRELEASED; urgency=medium
+
+  * d/control: Add libpcre3 to B-D and to nim's Dependency list.
+(Closes: #1022204)
+
+ -- Sergio Durigan Junior   Fri, 21 Oct 2022 16:58:30 
-0400
+
 nim (1.6.8-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/control b/debian/control
index cf9ea3932..16d606696 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,8 @@ Maintainer: Federico Ceratto 
 Build-Depends: debhelper-compat (= 13),
  help2man (>= 1.46.4),
  libssl-dev,
- libssl1.1
+ libssl1.1,
+ libpcre3,
 Standards-Version: 4.6.1
 Homepage: https://nim-lang.org/
 Vcs-Git: https://salsa.debian.org/debian/nim.git
@@ -16,7 +17,8 @@ Package: nim
 Architecture: alpha amd64 arm64 armel armhf hppa hurd-i386 i386 ia64 m68k mips 
mips64el mipsel powerpc powerpcspe ppc64 ppc64el riscv64 sh4 sparc64 x32
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- libssl1.1
+ libssl1.1,
+ libpcre3,
 Suggests: nim-doc
 Recommends: build-essential,
  gcc,


signature.asc
Description: PGP signature

Processed: patch

[Debian Bug Tracking System]

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

> tags 1022204 + patch
Bug #1022204 [src:nim] FTBFS because nimgrep needs libpcre3
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1000922: upgrading llvmlite to llvm-13

[Diane Trout]

Hi,

I found a pull request that starts the process of upgrading llvmlite to
llvm-12 or -13.
https://github.com/numba/llvmlite/pull/802

I modified it to work with our llvmlite 0.39.1 package and was able to
build llvmlite and have it's tests pass on x86 64.

The llvmlite upstream developers are concerned about releasing it
because in their experience they have various compile errors on unusual
architectures.

Though I'm having those with the llvm-11 version too, so who knows.

I was thinking that releasing it to Debian's buildd would help upstream
see which architectures are having problems with the migration to llvm-
13

I've been trying to build and run numba's tests, it's been a bit
difficult to tell what's failures are new because of building against
llvm-13 and which are because there's some failures due to the
autopkgtest environment being different from what upstream expects.

I think there's only a couple of test failures out of the about 20 I'm
trying to fix that are due to the llvm-13 update.

Since there's already some numba test failures with ppc64el and amdel
even with the llvm-11 version of llvmlite, I feel like releasing the -
13 version of llvmlite isn't going to make things any worse for numba.

So should we uploading a version of llvmlite with the -13 compatibility
patch?

They both fell out of testing, and it'd be really bad for the
scientific python ecosystem if we don't get numba shipped in bullseye.

Diane
From 1d928ebcd59b23b5050234a2bf71f9be7f5f6bd1 Mon Sep 17 00:00:00 2001
From: Richard Barnes 
Date: Wed, 1 Dec 2021 10:29:08 -0700
Subject: [PATCH] Enable LLVM-12 and LLVM-13

---
 ffi/build.py   |  5 ++---
 ffi/targets.cpp|  2 ++
 llvmlite/tests/test_binding.py | 19 ---
 3 files changed, 20 insertions(+), 6 deletions(-)

--- a/ffi/build.py
+++ b/ffi/build.py
@@ -163,9 +163,8 @@
 print(msg)
 print(warning + '\n')
 else:
-
-if not out.startswith('11'):
-msg = ("Building llvmlite requires LLVM 11.x.x, got "
+if not (out.startswith('11') or out.startswith('12') or out.startswith('13')):
+msg = ("Building llvmlite requires LLVM 11-13.x.x, got "
"{!r}. Be sure to set LLVM_CONFIG to the right executable "
"path.\nRead the documentation at "
"http://llvmlite.pydata.org/ for more information about "
--- a/ffi/targets.cpp
+++ b/ffi/targets.cpp
@@ -204,7 +204,9 @@
 rm = Reloc::DynamicNoPIC;
 
 TargetOptions opt;
+#if LLVM_VERSION_MAJOR < 12
 opt.PrintMachineCode = PrintMC;
+#endif
 opt.MCOptions.ABIName = ABIName;
 
 bool jit = JIT;
--- a/llvmlite/tests/test_binding.py
+++ b/llvmlite/tests/test_binding.py
@@ -18,6 +18,16 @@
 from llvmlite.tests import TestCase
 
 
+def clean_string_whitespace(x: str) -> str:
+# Remove trailing whitespace from the end of each line
+x = re.sub(r"\s+$", "", x, flags=re.MULTILINE)
+# Remove intermediate blank lines
+x = re.sub(r"\n\s*\n", r"\n", x, flags=re.MULTILINE)
+# Remove extraneous whitespace from the beginning and end of the string
+x = x.strip()
+return x
+
+
 # arvm7l needs extra ABI symbols to link successfully
 if platform.machine() == 'armv7l':
 llvm.load_library_permanently('libgcc_s.so.1')
@@ -555,7 +565,10 @@
 bd = ir.IRBuilder(fn.append_basic_block(name="<>!*''#"))
 bd.ret(ir.Constant(ir.IntType(32), 12345))
 asm = str(mod)
-self.assertEqual(asm, asm_nonalphanum_blocklabel)
+self.assertEqual(
+clean_string_whitespace(asm),
+clean_string_whitespace(asm_nonalphanum_blocklabel)
+)
 
 def test_global_context(self):
 gcontext1 = llvm.context.get_global_context()
@@ -640,7 +653,7 @@
 def test_version(self):
 major, minor, patch = llvm.llvm_version_info
 # one of these can be valid
-valid = [(11,)]
+valid = [(11,), (12,), (13,)]
 self.assertIn((major,), valid)
 self.assertIn(patch, range(10))
 
--- a/ffi/passmanagers.cpp
+++ b/ffi/passmanagers.cpp
@@ -17,9 +17,6 @@
 #include "llvm-c/Transforms/IPO.h"
 #include "llvm-c/Transforms/Scalar.h"
 #include "llvm/IR/LegacyPassManager.h"
-#if LLVM_VERSION_MAJOR > 11
-#include "llvm/IR/RemarkStreamer.h"
-#endif
 #include "llvm/IR/LLVMRemarkStreamer.h"
 #include "llvm/Remarks/RemarkStreamer.h"
 #include "llvm/Transforms/IPO.h"


signature.asc
Description: This is a digitally signed message part

Bug#1022204: FTBFS because nimgrep needs libpcre3

[Sergio Durigan Junior]

Source: nim
Version: 1.6.8-1
Severity: serious

Hi,

One of the reasons nim is currently FTBFSing is because the nimgrep
program attempts to load libpcre.so.3 but fails.  The package needs to
explicitly depend on libpcre3.

I will soon attach a patch to fix the problem.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1022200: cpan: cannot check signatures

[Vincent Lefevre]

On 2022-10-21 22:28:14 +0200, Vincent Lefevre wrote:
> It is no longer possible to install modules from CPAN because
> signatures can no longer be checked. There was no such issue
> with 5.34. This is a major regression; in particular, the
> locally installed modules need to be reinstalled after the
> upgrade.

As a workaround, one can run "gpg --recv-keys E247329948EA8380",
then all the modules can be installed. But I suppose that the key
should be loaded by default as before.

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

Processed (with 1 error): Re: Bug#1022174: Acknowledgement (linux-image-6.0.0-1-amd64: nvidia 470 modul builds successfully, but does not get loaded on boot -> no X)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 nvidia-graphics-drivers-tesla-470 470.141.03-2
Bug #1022174 [src:nvidia-graphics-drivers-tesla-470] linux-image-6.0.0-1-amd64: 
nvidia 470 modul builds successfully, but does not get loaded on boot -> no X
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-470' to 
'nvidia-graphics-drivers-tesla-470'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-470/470.141.03-2.
Ignoring request to alter fixed versions of bug #1022174 to the same values 
previously set
Bug #1022174 [nvidia-graphics-drivers-tesla-470] linux-image-6.0.0-1-amd64: 
nvidia 470 modul builds successfully, but does not get loaded on boot -> no X
There is no source info for the package 'nvidia-graphics-drivers-tesla-470' at 
version '470.141.03-2' with architecture ''
Unable to make a source version for version '470.141.03-2'
Marked as found in versions 470.141.03-2.
> severity -1 normal
Bug #1022174 [nvidia-graphics-drivers-tesla-470] linux-image-6.0.0-1-amd64: 
nvidia 470 modul builds successfully, but does not get loaded on boot -> no X
Severity set to 'normal' from 'grave'
> merge -1 1021974
Bug #1022174 [nvidia-graphics-drivers-tesla-470] linux-image-6.0.0-1-amd64: 
nvidia 470 modul builds successfully, but does not get loaded on boot -> no X
Unable to merge bugs because:
package of #1021974 is 'nvidia-tesla-470-driver' not 
'nvidia-graphics-drivers-tesla-470'
Failed to merge 1022174: Did not alter merged bugs.


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

Bug#1022174: Acknowledgement (linux-image-6.0.0-1-amd64: nvidia 470 modul builds successfully, but does not get loaded on boot -> no X)

[Diederik de Haas]

Control: reassign -1 nvidia-graphics-drivers-tesla-470 470.141.03-2
Control: severity -1 normal
Control: merge -1 1021974

On Friday, 21 October 2022 22:13:35 CEST mh wrote:
> 2> /var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/nv-acpi.c:270:43:
> 2> error: ‘struct acpi_device’ has no member named ‘children’
> 2> /var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/nv-acpi.c:273:50:
> 2> error: ‘struct acpi_device’ has no member named ‘node’; did you mean
> 2> ‘fwnode’?
> 2>
> /usr/src/linux-headers-6.0.0-1-common/include/linux/compiler_types.h:295:27
> : 2> error: expression in static assertion is not an integer

Sounds like https://bugs.debian.org/1021974 (doesn't work with kernel 6.0), 
thus reassigning and merging accordingly

signature.asc
Description: This is a digitally signed message part.

Bug#1022200: cpan: cannot check signatures

[Vincent Lefevre]

Package: perl
Version: 5.36.0-4
Severity: grave
Justification: renders package unusable

It is no longer possible to install modules from CPAN because
signatures can no longer be checked. There was no such issue
with 5.34. This is a major regression; in particular, the
locally installed modules need to be reinstalled after the
upgrade.

Example:

Fetching with HTTP::Tiny:
https://cpan.org/modules/03modlist.data.gz
Reading '/home/vinc17/.cpan/sources/modules/03modlist.data.gz'
DONE
Writing /home/vinc17/.cpan/Metadata
Running install for module 'ReadDir'
Fetching with HTTP::Tiny:
https://cpan.org/authors/id/S/SA/SAMV/ReadDir-0.03.tar.gz
CPAN: Digest::SHA loaded ok (v6.02)
Fetching with HTTP::Tiny:
https://cpan.org/authors/id/S/SA/SAMV/CHECKSUMS
CPAN: Module::Signature loaded ok (v0.88)
gpg: Signature made 2021-11-21T22:42:22 CET
gpg:using RSA key B6A1739063760CCA
gpg: Can't check signature: No public key

Signature for file /home/vinc17/.cpan/sources/authors/id/S/SA/SAMV/CHECKSUMS 
could not be verified for an unknown reason. Distribution id = 
S/SA/SAMV/ReadDir-0.03.tar.gz
CPAN_USERID  SAMV (Sam Vilain )
CALLED_FOR   ReadDir
CHECKSUM_STATUS 
CONTAINSMODS ReadDir
UPLOAD_DATE  2004-06-25
incommandcolor 1
localfile
/home/vinc17/.cpan/sources/authors/id/S/SA/SAMV/ReadDir-0.03.tar.gz
mandatory1
negative_prefs_cache 0
prefsHASH(0x55c2dfe1e9f8)
reqtype  c

Module::Signature verification returned value 0E0

The manual says for this case: Cannot verify the
OpenPGP signature, maybe due to the lack of a network connection to
the key server, or if neither gnupg nor Crypt::OpenPGP exists on the
system. You probably want to analyse the situation and if you cannot
fix it you will have to decide whether you want to stop this session
or you want to turn off signature verification. The latter would be
done with the command 'o conf init check_sigs'

Signature for S/SA/SAMV/CHECKSUMS could not be verified for an unknown reason. 
Distribution id = S/SA/SAMV/ReadDir-0.03.tar.gz

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages perl depends on:
ii  dpkg   1.21.9+b1
ii  libperl5.365.36.0-4
ii  perl-base  5.36.0-4
ii  perl-modules-5.36  5.36.0-4

Versions of packages perl recommends:
ii  netbase  6.4

Versions of packages perl suggests:
pn  libtap-harness-archive-perl  
ii  libterm-readline-perl-perl   1.0303-2.1
ii  make 4.3-4.1
ii  perl-doc 5.36.0-4

-- no debconf information

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

Processed: reassign 1022174 to src:nvidia-graphics-drivers-tesla-470

[Debian Bug Tracking System]

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

> reassign 1022174 src:nvidia-graphics-drivers-tesla-470 470.141.03-2
Bug #1022174 [src:linux] linux-image-6.0.0-1-amd64: nvidia 470 modul builds 
successfully, but does not get loaded on boot -> no X
Bug reassigned from package 'src:linux' to 
'src:nvidia-graphics-drivers-tesla-470'.
No longer marked as found in versions linux/6.0.2-1.
Ignoring request to alter fixed versions of bug #1022174 to the same values 
previously set
Bug #1022174 [src:nvidia-graphics-drivers-tesla-470] linux-image-6.0.0-1-amd64: 
nvidia 470 modul builds successfully, but does not get loaded on boot -> no X
Marked as found in versions nvidia-graphics-drivers-tesla-470/470.141.03-2.
> thanks
Stopping processing here.

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

Bug#1022174: Acknowledgement (linux-image-6.0.0-1-amd64: nvidia 470 modul builds successfully, but does not get loaded on boot -> no X)

[mh]

Addidional Info 
(Error while building modul after installen new kernel version
linux-image-6.0.0-1-amd64 amd64 6.0.2-1+b1 this evening)

Still no working Module:
on boot first error: Failed to start Load Kernel Modules


Building module:
Cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j2 modules
KERNEL_UNAME=6.0.0-1-amd64..(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.0.0-1-amd64
(x86_64) Consult
/var/lib/dkms/nvidia-tesla-470/470.141.03/build/make.log for more
information.

*



$ cat /var/lib/dkms/nvidia-tesla-470/470.141.03/build/make.log | grep
error

NV_CONFTEST_CFLAGS=-O2 -D__KERNEL__ -DKBUILD_BASENAME="#conftest87977"
-DKBUILD_MODNAME="#conftest87977" -nostdinc -isystem
/usr/lib/gcc/x86_64-linux-gnu/12/include
-I/lib/modules/6.0.0-1-amd64/source/arch/x86/include/asm/mach-default
-I/lib/modules/6.0.0-1-amd64/source/include/asm-x86/mach-default
-I/lib/modules/6.0.0-1-amd64/build/include2
-I/lib/modules/6.0.0-1-amd64/build/include -include
/lib/modules/6.0.0-1-amd64/build/include/generated/autoconf.h
-I/lib/modules/6.0.0-1-amd64/source/arch/x86/include
-I/lib/modules/6.0.0-1-amd64/source/arch/x86/include/uapi
-I/lib/modules/6.0.0-1-amd64/build/arch/x86/include/generated
-I/lib/modules/6.0.0-1-amd64/build/arch/x86/include/generated/uapi
-I/lib/modules/6.0.0-1-amd64/source/include
-I/lib/modules/6.0.0-1-amd64/source/include/uapi
-I/lib/modules/6.0.0-1-amd64/source/include/xen
-I/lib/modules/6.0.0-1-amd64/build/include/generated/uapi -mfentry
-DCC_USING_FENTRY
-I/var/lib/dkms/nvidia-tesla-470/470.141.03/build/common/inc
-I/var/lib/dkms/nvidia-tesla-470/470.141.03/build -Wall -MD
-Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE
-DNVRM -DNV_VERSION_STRING=\"470.141.03\" -Wno-unused-function
-Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel
-DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0
-DNV_KERNEL_INTERFACE_LAYER -fno-pie -Wall -Wundef -Wno-trigraphs
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE
-Wno-format-security -std=gnu11 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
-mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1
-mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3
-mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel
-Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register
-mindirect-branch-cs-prefix -mfunction-return=thunk-extern
-fno-jump-tables -mharden-sls=all -fno-delete-null-pointer-checks
-Wno-frame-address -Wno-format-truncation -Wno-format-overflow
-Wno-address-of-packed-member -O2 -fno-allow-store-data-races
-Wframe-larger-than=2048 -fstack-protector-strong -Wno-array-bounds
-Wimplicit-fallthrough=5 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer
-ftrivial-auto-var-init=zero -fno-stack-clash-protection -pg
-mrecord-mcount -mfentry -DCC_USING_FENTRY
-Wdeclaration-after-statement -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow
-Wno-restrict -Wno-maybe-uninitialized -Wno-alloc-size-larger-than
-fno-strict-overflow -fno-stack-check -fconserve-stack
-Wno-packed-not-aligned -g KBUILD_CFLAGS=-Wall -Wundef
-Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -fshort-wchar -fno-PIE
-Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Wno-format-security -std=gnu11 -mno-sse -mno-mmx
-mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern
-mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fno-delete-null-pointer-checks -Wno-frame-address
-Wno-format-truncation -Wno-format-overflow
-Wno-address-of-packed-member -O2 -fno-allow-store-data-races
-Wframe-larger-than=2048 -fstack-protector-strong -Wno-array-bounds
-Wimplicit-fallthrough=5 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer
-ftrivial-auto-var-init=zero  -fno-stack-clash-protection -pg
-mrecord-mcount -mfentry -DCC_USING_FENTRY
-Wdeclaration-after-statement -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow
-Wno-restrict -Wno-maybe-uninitialized -Wno-alloc-size-larger-than
-fno-strict-overflow -fno-stack-check -fconserve-stack
-Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wno-packed-not-aligned -g gcc-12
-Wp,-MMD,/var/lib/dkms/nvidia-tesla-470/470.141.03/build/nvidia/.nv.o.d
-nostdinc -I/usr/src/linux-headers-6.0.0-1-common/arch/x86/include
-I./arch/x86/include/generated
-I/usr/src/linux-headers-6.0.0-1-common/include -I./include

Bug#1022042: linux-image-5.10.0-19-amd64: amd computers with integrated graphics (ryzen 5 3400G) don't boot with this kernel version

[George Ramos]

Package: src:linux
Version: 5.10.149-1
Followup-For: Bug #1022042
X-Debbugs-Cc: m...@duck.com

Dear Maintainer,

I just updated to the new kernel linux-image-5.10.0-19-amd64 (ver 5.10.149-1)
And when the system was trying to boot(but never did), I just got this
messages:

[14.020140] [drm:drm_atomic_helper_wait_for_flip_done [drm_dkms_helper]]
*ERROR* [CRTC:62:crtc-0] flip_done timed out
[24.260069] [drm:drm_atomic_helper_wait_for_flip_done [drm_dkms_helper]]
*ERROR* [CRTC:65:crtc-1] flip_done timed out
[34.500079] [drm:drm_atomic_helper_wait_for_dependencies [drm_dkms_helper]]
*ERROR* [CRTC:62:crtc-0] flip_done timed out
[44.740026] [drm:drm_atomic_helper_wait_for_dependencies [drm_dkms_helper]]
*ERROR* [CRTC:62:crtc-1] flip_done timed out
[54.980073] [drm:drm_atomic_helper_wait_for_dependencies [drm_dkms_helper]]
*ERROR* [PLANE:48:plane-2] flip_done timed out
[65.220054] [drm:drm_atomic_helper_wait_for_dependencies [drm_dkms_helper]]
*ERROR* [PLANE:52:plane-3] flip_done timed out
[75.460064] [drm:drm_atomic_helper_wait_for_flip_done [drm_dkms_helper]]
*ERROR* [CRTC:62:crtc-0] flip_done timed out
[85.700050] [drm:drm_atomic_helper_wait_for_flip_done [drm_dkms_helper]]
*ERROR* [CRTC:65:crtc-1] flip_done timed out
/dev/nvme0n1p2: clean, 354739/1831424 files, 4384360/7324160 blocks

I restarted the system twice later but got nothing more than a black screen.

I backed off to the previous kernel linux-image-5.10.0-17-amd64 (5.10.136-1)

The system boots again with no issues, I'll keep using this kernel version
(linux-image-5.10.0-17-amd64) until a new one
gets released and try it.

Thanks for your great work.




-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: BIOSTAR Group
product_name: A32M2
product_version: 
chassis_vendor: BIOSTAR Group
chassis_version: 
bios_vendor: American Megatrends Inc.
bios_version: 5.14
board_vendor: BIOSTAR Group
board_name: A32M2
board_version: 

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Root Complex [1022:15d0]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 
[1022:15d0]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe 
GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Internal PCIe GPP Bridge 0 to Bus B [1022:15dc] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: Biostar Microtech Int'l Corp FCH SMBus Controller [1565:370b]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device 

Bug#1020436: marked as done (giac FTBFS with PARI 2.15.0)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 19:49:39 +
with message-id 
and subject line Bug#1020436: fixed in giac 1.9.0.21+dfsg2-1
has caused the Debian Bug report #1020436,
regarding giac FTBFS with PARI 2.15.0
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.)


-- 
1020436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giac
Version: 1.9.0.19+dfsg2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=giac=1.9.0.19%2Bdfsg2-1%2Bb1

...
pari.cc: At global scope:
pari.cc:752:17: error: typedef ‘giac::PFGEN’ is initialized (use ‘decltype’ 
instead)
  752 |   typedef GEN (*PFGEN)(ANYARG);
  | ^
pari.cc:752:24: error: ‘ANYARG’ was not declared in this scope
  752 |   typedef GEN (*PFGEN)(ANYARG);
  |^~
pari.cc: In function ‘giac::gen giac::in_pari(const gen&, const context*)’:
pari.cc:829:26: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  829 |   argvec[k]= (GEN) v[j].val;
  |  ^~
pari.cc:847:33: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  847 |   argvec[k]=(long int*)(pos -1);
  | ^~~
pari.cc:855:31: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  855 | argvec[k]=(long int*) v[j].val;
  |   ^~~~
pari.cc:883:23: error: ‘PFGEN’ was not declared in this scope; did you mean 
‘GEN’?
  883 |   res = ((PFGEN)call)(_ARGS_);
  |   ^
  |   GEN
pari.cc:883:29: error: expected ‘)’ before ‘call’
  883 |   res = ((PFGEN)call)(_ARGS_);
  | ~   ^~~~
  | )
pari.cc:887:27: error: expected primary-expression before ‘int’
  887 |   m = (long)((int (*)(ANYARG))call)(_ARGS_);
  |   ^~~
pari.cc:887:27: error: expected ‘)’ before ‘int’
  887 |   m = (long)((int (*)(ANYARG))call)(_ARGS_);
  |  ~^~~
  |   )
pari.cc:887:56: error: expected ‘)’ before ‘;’ token
  887 |   m = (long)((int (*)(ANYARG))call)(_ARGS_);
  | ~  ^
  |)
pari.cc:891:21: error: expected primary-expression before ‘long’
  891 |   m = ((long (*)(ANYARG))call)(_ARGS_);
  | ^~~~
pari.cc:891:21: error: expected ‘)’ before ‘long’
  891 |   m = ((long (*)(ANYARG))call)(_ARGS_);
  |~^~~~
  | )
pari.cc:891:51: error: expected ‘)’ before ‘;’ token
  891 |   m = ((long (*)(ANYARG))call)(_ARGS_);
  |   ~   ^
  |   )
pari.cc:895:17: error: expected primary-expression before ‘void’
  895 |   ((void (*)(ANYARG))call)(_ARGS_);
  | ^~~~
pari.cc:895:17: error: expected ‘)’ before ‘void’
  895 |   ((void (*)(ANYARG))call)(_ARGS_);
  |~^~~~
  | )
pari.cc:895:47: error: expected ‘)’ before ‘;’ token
  895 |   ((void (*)(ANYARG))call)(_ARGS_);
  |   ~   ^
  |   )
make[3]: *** [Makefile:993: pari.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: giac
Source-Version: 1.9.0.21+dfsg2-1
Done: Ileana Dumitrescu 

We believe that the bug you reported is fixed in the latest version of
giac, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ileana Dumitrescu  (supplier of updated giac 
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#1016658: marked as done (kalgebra: fails to start: assertion failed)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 19:26:54 +
with message-id 
and subject line Bug#1016658: fixed in z3 4.8.12-3
has caused the Debian Bug report #1016658,
regarding kalgebra: fails to start: assertion failed
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.)


-- 
1016658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kalgebra
Version: 4:20.12.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: karogyoker2+deb...@gmail.com

Dear Maintainer,

I use Debian Edu 11.4 Standard install for i386 on an Athlon XP.
When I try to start kalgebra from Terminal, this is what I get:

(kalgebra:3838): Gtk-CRITICAL **: 14:28:36.532: 
_gtk_css_ease_value_new_cubic_bezier: assertion 'x1 <= 1.0' failed

(kalgebra:3838): Gtk-CRITICAL **: 14:28:36.534: _gtk_css_array_value_new: 
assertion 'content != NULL' failed
**
Gtk:ERROR:../../../../gtk/gtkcssstylepropertyimpl.c:87:gtk_css_style_property_register:
 assertion failed: (initial_value != NULL)
Bail out! 
Gtk:ERROR:../../../../gtk/gtkcssstylepropertyimpl.c:87:gtk_css_style_property_register:
 assertion failed: (initial_value != NULL)
Aborted


-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-16-686-pae (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kalgebra depends on:
ii  kalgebra-common  4:20.12.1-1
ii  kio  5.78.0-5
ii  libanalitza8 4:20.12.0-2
ii  libanalitzagui8  4:20.12.0-2
ii  libanalitzaplot8 4:20.12.0-2
ii  libanalitzawidgets8  4:20.12.0-2
ii  libc62.31-13+deb11u3
ii  libkf5configcore55.78.0-4
ii  libkf5configwidgets5 5.78.0-2
ii  libkf5coreaddons55.78.0-4
ii  libkf5i18n5  5.78.0-2
ii  libkf5kiocore5   5.78.0-5
ii  libkf5widgetsaddons5 5.78.0-2
ii  libkf5xmlgui55.78.0-2
ii  libqt5core5a 5.15.2+dfsg-9
ii  libqt5gui5   5.15.2+dfsg-9
ii  libqt5webenginewidgets5  5.15.2+dfsg-3
ii  libqt5widgets5   5.15.2+dfsg-9
ii  libreadline8 8.1-1
ii  libstdc++6   10.2.1-6

kalgebra recommends no packages.

kalgebra suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: z3
Source-Version: 4.8.12-3
Done: Karo Gyoker 

We believe that the bug you reported is fixed in the latest version of
z3, 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 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Karo Gyoker  (supplier of updated z3 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: Fri, 21 Oct 2022 19:24:40 +0200
Source: z3
Architecture: source
Version: 4.8.12-3
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Karo Gyoker 
Closes: 1016658 1020516 1020802 1021926
Changes:
 z3 (4.8.12-3) unstable; urgency=medium
 .
   * Do not use SSE2 unconditionally on i386
 (Closes: #1020802, #1020516, #1016658, #1021926)
Checksums-Sha1:
 43831183587607081a47be1fe2a54cfce70e81bd 2630 z3_4.8.12-3.dsc
 2f37f8566b2bfeeeac62d228e86a62becd48dad1 10308 z3_4.8.12-3.debian.tar.xz
 a01f0e6c10e5fa3f3ee0967a854ce77521ded596 13280 z3_4.8.12-3_amd64.buildinfo
Checksums-Sha256:
 bae3d63f0c8168d91935dafc7f77d24cfe27a17557018d184fc371a1bf9b0275 2630 
z3_4.8.12-3.dsc
 1eb8b62a1194956a0049d4ab121bd088a727499dd69d4d7dc0f4e6c09affec3e 10308 
z3_4.8.12-3.debian.tar.xz
 0fdb6927d4a72dde54d84e20b42e432c5ddf36caf43f2912d8898977be139b44 13280 
z3_4.8.12-3_amd64.buildinfo
Files:
 75cba8dd8da47e6d5a37d20d7c523b18 2630 science optional z3_4.8.12-3.dsc
 f45db163406f1154f020a50ddc9e622f 10308 science optional 
z3_4.8.12-3.debian.tar.xz
 3848cd121e018bda08b02e6de4407042 13280 science optional 
z3_4.8.12-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1022196: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-relational-schemas
Version: 0.1.8.0-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022195: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-relational-record
Version: 0.2.2.0-5
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022194: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-relational-query-hdbc
Version: 0.7.2.0-2
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022192: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-relational-query
Version: 0.12.3.0-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022191: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-persistable-types-hdbc-pg
Version: 0.0.3.5-2
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1019347: marked as done (Backups end up mostly empty when location.patterns is used and /root/.borgmatic exists)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 18:04:01 +
with message-id 
and subject line Bug#1019347: fixed in borgmatic 1.7.4-0.1
has caused the Debian Bug report #1019347,
regarding Backups end up mostly empty when location.patterns is used and 
/root/.borgmatic exists
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.)


-- 
1019347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgmatic
Version: 1.5.12-2
Severity: grave
Tags: upstream fixed-upstream
Forwarded: 
https://projects.torsion.org/borgmatic-collective/borgmatic/issues/574
Control: found -1 1.6.3-1

Hi,

Recently I reported the bug mentioned above upstream, which causes
most data to be silently excluded from backups if /root/.borgmatic
exists. Since details of the bug are already available in the upstream
bug report, I will omit them here for brevity.

Since the issue has already been fixed upstream, this bug is only
meant to track the issue in Debian.

I've set the severity to grave, because the bug causes borgmatic to
produce effectively empty backups, while the user may believe to have
secure backups, which qualifies as data loss to me. Feel free to lower
the severity to normal if you disagree.

Regards
Sven

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (102, 
'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages borgmatic depends on:
ii  borgbackup 1.2.1-2
ii  python33.10.6-1
ii  python3-colorama   0.4.5-2
ii  python3-jsonschema 4.6.0-3
ii  python3-pkg-resources  59.6.0-1.2
ii  python3-requests   2.27.1+dfsg-1
ii  python3-ruamel.yaml0.17.16-1

borgmatic recommends no packages.

borgmatic suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: borgmatic
Source-Version: 1.7.4-0.1
Done: Sven Bartscher 

We believe that the bug you reported is fixed in the latest version of
borgmatic, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sven Bartscher  (supplier of updated borgmatic 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: Sun, 16 Oct 2022 18:00:20 +0200
Source: borgmatic
Architecture: source
Version: 1.7.4-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Borg Collective 
Changed-By: Sven Bartscher 
Closes: 1019347
Changes:
 borgmatic (1.7.4-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 1.7.4 (Closes: #1019347)
Checksums-Sha1:
 b026410c696bbffb6427cfe4231a83f3cc4eafc9 2394 borgmatic_1.7.4-0.1.dsc
 79ac653462a232a38cc83e47ab8ccf763445d994 328302 borgmatic_1.7.4.orig.tar.gz
 9927ffbb3bbb472fd6c7bebfb147ba4f74c9889b 5280 borgmatic_1.7.4-0.1.debian.tar.xz
Checksums-Sha256:
 5c6118f0d711fc6cd033c98869ba86633b973248c8fd53e4edb2ecf687edfef3 2394 
borgmatic_1.7.4-0.1.dsc
 f0c59e9efe0accebfa7914b075e8ebe02912dd98692f7f1d60b91720fb9f0bd2 328302 
borgmatic_1.7.4.orig.tar.gz
 40ec06ffbc6d350a356a58ebcde2ef78d96f7c26cd1fa84dafd8a98a530edf71 5280 
borgmatic_1.7.4-0.1.debian.tar.xz
Files:
 17daf59afd7fe56b8d378b273dcda11a 2394 utils optional borgmatic_1.7.4-0.1.dsc
 926e91b218e668a0b672c7e007419bef 328302 utils optional 
borgmatic_1.7.4.orig.tar.gz
 83c9f9a3b313f859c2b91c54d9c2bd37 5280 utils optional 
borgmatic_1.7.4-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEE9eLej9CS02N0etaYrrJTIyFwKMIFAmNMQGcWHGtyaXR6ZWZp
dHpAZGViaWFuLm9yZwAKCRCuslMjIXAowj3rEADLXxLKp58G0zNlKYqm/PNl7EcN

Bug#1022190: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-persistable-record
Version: 0.6.0.5-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022189: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-product-isomorphic
Version: 0.0.3.3-2
Severity: serious

I intend to remove this package:

  * The current version is incompatible with GHC 9.0 and FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1022188: debugpy: FTBFS due to either "Timed out..." or "Address already in use"

[Sergio Durigan Junior]

Source: debugpy
Version: 1.6.3+ds-1
Severity: serious

Hi,

debugpy is currently FTBFSing:

--8<---cut here---start->8---
=== short test summary info 
FAILED 
tests/debugpy/test_run.py::test_custom_python_args[program-python-custompy,-O-None-launch(console=internalConsole)]
FAILED 
tests/debugpy/test_run.py::test_custom_python_args[program-pythonPath-custompy,-O-None-launch(console=internalConsole)]
FAILED 
tests/debugpy/test_run.py::test_custom_python_args[program-python-custompy,-O--B-launch(console=integratedTerminal)]
FAILED 
tests/debugpy/test_run.py::test_custom_python_args[program-pythonPath-custompy,-O-None-launch(console=externalTerminal)]
--8<---cut here---end--->8---

The long summary is too big to post here, but you can see the full log
at:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debugpy.html

I think the gist of what's going on is the following excerpt:

--8<---cut here---start->8---
E+00015.109: /handling #2 request "attach" from Client[1]/
 Traceback (most recent call last):
   File 
"/<>/.pybuild/cpython3_3.10_debugpy/build/debugpy/adapter/../../debugpy/common/messaging.py",
 line 1015, in __init__
 raise self
 debugpy.common.messaging.MessageHandlingError: Timed out waiting 
for debug server to connect.
--8<---cut here---end--->8---

Interestingly, when I sbuild the package locally I get a somewhat
different error:

--8<---cut here---start->8---
E+0.008: Error listening for incoming Client connections on 127.0.0.1:5684:
 
 Traceback (most recent call last):
   File 
"/<>/.pybuild/cpython3_3.10_debugpy/build/debugpy/../debugpy/adapter/../../debugpy/common/sockets.py",
 line 93, in serve
 listener = create_server(host, port, backlog, timeout)
   File 
"/<>/.pybuild/cpython3_3.10_debugpy/build/debugpy/../debugpy/adapter/../../debugpy/common/sockets.py",
 line 24, in create_server
 server.bind((host, port))
 OSError: [Errno 98] Address already in use
--8<---cut here---end--->8---

I found a few upstream bugs that contain either the "Timed out waiting
for debug server to connect" or the "Address already in use" messages,
but I haven't investigated further TBH.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#937234: trying to remove python2.7 from bookworm

[Mike Gabriel]

Hi Nilesh,

On  Fr 21 Okt 2022 16:13:37 CEST, Nilesh Patra wrote:


On Fri, 16 Sep 2022 22:50:29 +0200 Paul Gevers  wrote:

Hi Mike,

On Mon, 15 Aug 2022 13:54:27 + Mike Gabriel
 wrote:
> in another project context I have a freelancer working on pam-python
> Py3 transition. Will pick up the threads this week (I returned freshly
> from VAC yesterday).

One month went by, is there any progress to report?


. and it is two months now, w/ nothing happening on this bug reoport.
Mike, do you intend to get working on it?


yes, I do. I'll have it +/- next on my list.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp34VjT7eKSf.pgp
Description: Digitale PGP-Signatur

Bug#1020436: giac failed tests with new pari

[Ileana Dumitrescu]

Hi Tobias,

> are you aware of the bug
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020436

> Bill posted a suggestion how to fix this test there yesterday.

Yes I saw the bug and initial comments by Bill but thanks for letting me know 
about Bill's latest comments.

I applied the patch from sagemath (define-anyarg.patch) and built giac 
1.9.0.21+dfsg2 in my pbuilder environment and was able to reproduce the 
chk_fhan4 seg fault from above. I added an additional patch 
(increase-pari-size.patch) to export PARI_SIZE=2048000 in chk_fhan4 as in 
Gonzalo Tornaria's comment here: https://trac.sagemath.org/ticket/34583. This 
allowed the build to complete without error on my pbuilder environment and I 
committed the changes to salsa. Please feel free to test and upload if the 
updates look good.

IleanaFrom 2238c88dbb3ea8eacd7b3d8f071cd8a977c47e98 Mon Sep 17 00:00:00 2001
From: Ileana Dumitrescu 
Date: Fri, 21 Oct 2022 16:41:42 +0300
Subject: [PATCH] define anyarg

---
 src/pari.cc | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/src/pari.cc b/src/pari.cc
index 76ce8e1..8d5b22b 100644
--- a/src/pari.cc
+++ b/src/pari.cc
@@ -39,6 +39,12 @@ using namespace std;
 #endif
 
 #ifdef HAVE_LIBPARI
+// ANYARG disappeared from PARI 2.15.0
+#ifdef __cplusplus
+# define ANYARG ...
+#else
+# define ANYARG
+#endif
 
 #ifdef HAVE_PTHREAD_H
 #include 
-- 
2.37.2

From f32439947309f276d963234c827c1e8918bb808c Mon Sep 17 00:00:00 2001
From: Ileana Dumitrescu 
Date: Fri, 21 Oct 2022 17:10:36 +0300
Subject: [PATCH] increase pari size

---
 check/chk_fhan4 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/check/chk_fhan4 b/check/chk_fhan4
index 5d1e1e8..29429d3 100755
--- a/check/chk_fhan4
+++ b/check/chk_fhan4
@@ -1,4 +1,5 @@
 #! /bin/sh
 unset LANG
+export PARI_SIZE=2048000
 ../src/icas TP04-sol.cas > TP04.tst
 diff TP04.tst TP04-sol.cas.out1
-- 
2.37.2

Bug#1009684: marked as done (openmw: FTBFS with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 17:35:41 +0200
with message-id 
and subject line Re: openmw: FTBFS with glibc 2.34
has caused the Debian Bug report #1009684,
regarding openmw: FTBFS with glibc 2.34
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.)


-- 
1009684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmw
Version: 0.47.0-1
Severity: important
Tags: ftbfs fixed-upstream

Hi Maintainer

Your package FTBFS once glibc is upgraded to 2.34 due to MINSIGSTKSZ
and SIGSTKSZ no longer being defined as constants.

This was already fixed upstream [1].

Regards
Graham


[1] 
https://gitlab.com/OpenMW/openmw/-/commit/98a7d90ee258ceef9c70b0b2955d0458ec46f048
--- End Message ---
--- Begin Message ---

Version: 0.47.0-2--- End Message ---

Bug#1022124: libdbd-oracle-perl needs binaries uploaded for the perl 5.36 transitions

[Adrian Bunk]

On Fri, Oct 21, 2022 at 02:38:56PM +0200, Alex Muntada wrote:
> Hi Adrian,
> 
> > libdbd-oracle-perl cannot be built on the buildds,
> > and it needs binaries uploaded for the perl 5.36 transition.
> 
> Please, don't hesitate to remove libdbd-oracle-perl from testing
> for the perl 5.36 transition to proceed. I'll try to have those
> binaries by next week, but I don't want to stall the transition.

I am not a member of the release team, but your statement on
status/schedule is appreciated.

> Cheers!
> Alex

cu
Adrian

Bug#1022102: marked as done (rust-linux-raw-sys: invalid Uploaders field: missing name)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 15:06:01 +
with message-id 
and subject line Bug#1022102: fixed in rust-linux-raw-sys 0.0.46-2
has caused the Debian Bug report #1022102,
regarding rust-linux-raw-sys: invalid Uploaders field: missing 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.)


-- 
1022102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-linux-raw-sys
Version: 0.0.46-1
Severity: serious
Usertags: uploaders

rust-linux-raw-sys 0.0.46-1 introduced an invalid Uploaders field,
that is missing the name for the uploader .

   $ apt-cache showsrc rust-linux-raw-sys | grep -E '^$|^Version|^Uploaders'
   Version: 0.0.46-1
   Uploaders: 

According to Debian policy 5.6.3 the Uploaders field must include both
names and email addresses:

   List of the names and email addresses of co-maintainers of the
   package, if any.
 
   https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders

This is causing the DDPO and BLS cron jobs to send error mails,
please fix it as soon as possible.

   Subject: Cron  nice -15 flock -n /srv/qa.debian.org/lock/ddpo 
/srv/qa.debian.org/data/cronjobs/ddpo

   Uploader without name: rust-linux-raw-sys  at 
../extract_archive.pl line 122.
   Use of uninitialized value in concatenation (.) or string at 
../extract_archive.pl line 201.

   Cron  nice -15 flock -n /srv/qa.debian.org/lock/bls 
/srv/qa.debian.org/data/cronjobs/bls
   
   Cannot parse uploader «
   » from package ('rust-linux-raw-sys', 0, 1, 0, 0)

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: rust-linux-raw-sys
Source-Version: 0.0.46-2
Done: John Goerzen 

We believe that the bug you reported is fixed in the latest version of
rust-linux-raw-sys, 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.
John Goerzen  (supplier of updated rust-linux-raw-sys 
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, 21 Oct 2022 14:45:22 +
Source: rust-linux-raw-sys
Architecture: source
Version: 0.0.46-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: John Goerzen 
Closes: 1022102
Changes:
 rust-linux-raw-sys (0.0.46-2) unstable; urgency=medium
 .
   * Correct uploaders: line.  Closes: #1022102.
Checksums-Sha1:
 77d3a014f51c739b1813850b19db836a51256b87 2672 rust-linux-raw-sys_0.0.46-2.dsc
 4f753ac678c4fa5c2d133ece3becacfdc96f8870 3972 
rust-linux-raw-sys_0.0.46-2.debian.tar.xz
 ead9ba02ed0807473b5664bd7c2b3c15846a8c82 7069 
rust-linux-raw-sys_0.0.46-2_source.buildinfo
Checksums-Sha256:
 3cd13c31b97c72a75d7f5733419900281fa741cbfe78817ab7311dc844c5f43c 2672 
rust-linux-raw-sys_0.0.46-2.dsc
 64fa507220e489668a70e976c582d581b9688cb1c76f7d065861fe23dd0ec882 3972 
rust-linux-raw-sys_0.0.46-2.debian.tar.xz
 744c0aa8eb12b43e116afada90ba49144baaa9a0956133318a0294576e59ce91 7069 
rust-linux-raw-sys_0.0.46-2_source.buildinfo
Files:
 3ce3a749ce8862ac0ab750d089841172 2672 rust optional 
rust-linux-raw-sys_0.0.46-2.dsc
 92bc1afba265341e2b8183a14da142c5 3972 rust optional 
rust-linux-raw-sys_0.0.46-2.debian.tar.xz
 c5875fa3e5749e6a8169dda5f76fb5ed 7069 rust optional 
rust-linux-raw-sys_0.0.46-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJ217d7abdWx8toZp3Sn4hEKDntMFAmNSsL8ACgkQ3Sn4hEKD

Bug#1020989: trafficserver: failed to load plugin

[Jean Baptiste Favre]

Hello,
Thanks for your report.
After a quick look, I couldn't find any easy solution to this issue.
Will have a deeper as soon as possible.

Best,
Jean Baptiste


On 9/30/22 09:05, YunQiang Su wrote:

Package: trafficserver
Version: 9.1.3+ds-2
Severity: grave

Since ATS 9, it tries to load plugins to /run/trafficserver, and then load them,
and it asks for the plugins to have execution permission.

While the /run filesystem on Debian is mounted with noexec option.





OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022025: two reverts required, submitted to stable review list

[Dan Coleman]

On Fri, 21 Oct 2022 13:51:48 + Dan Coleman  wrote:
 > Thanks for sending them! No need for the binary packages, I mostly just want 
 > to see if I can successfully apply patches and get a working kernel.

The patches work! I booted into the new kernel just fine.

Bug#937234: trying to remove python2.7 from bookworm

[Nilesh Patra]

On Fri, 16 Sep 2022 22:50:29 +0200 Paul Gevers  wrote:
> Hi Mike,
> 
> On Mon, 15 Aug 2022 13:54:27 + Mike Gabriel 
>  wrote:
> > in another project context I have a freelancer working on pam-python  
> > Py3 transition. Will pick up the threads this week (I returned freshly  
> > from VAC yesterday).
> 
> One month went by, is there any progress to report?

. and it is two months now, w/ nothing happening on this bug reoport.
Mike, do you intend to get working on it?

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Processed: severity of 1022182 is normal

[Debian Bug Tracking System]

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

> severity 1022182 normal
Bug #1022182 [src:prads] prads: FTBFS on riscv64 (undefined reference to 
`_res_opcodes')
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1022025: two reverts required, submitted to stable review list

[Dan Coleman]

Thanks for sending them! No need for the binary packages, I mostly just want to 
see if I can successfully apply patches and get a working kernel.

On 10/21/22 08:42 AM, Salvatore Bonaccorso wrote:
> Hi,
>
> On Fri, Oct 21, 2022 at 12:55:09PM +, Dan Coleman wrote:
>> Hey,
>>
>>   > On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote:
>>
>>   > > So there are two patches who need to be reverted:
>>   > >
>>   > > 
>> https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/
>>   > > 
>> https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/
>>
>>
>> How do I apply these patches to see if they work for me? Thus far in
>> this bug, I've just seen .patch files.
> Here are those as patches.
>
> If you trust unsigned binary packages build I would put somehwere I
> can provide you those with those two applied. But again, after testing
> make sure you reinstall the meta package and go back to the -18
> version.
>
> Regards,
> Salvatore

Bug#1022182: prads: FTBFS on riscv64 (undefined reference to `_res_opcodes')

[Eric Long]

Source: prads
Version: 0.3.3-7
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: i...@hack3r.moe

Dear maintainer,

prads failed to build on riscv64 due to undefined reference to `_res_opcodes',
which somehow not existent on riscv64 but on other platforms:

```
cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -DCONFDIR='"/etc/prads/"' -D__USE_GNU -o 
shm-client shm-client.o -Wl,-z,relro -lpcap -lpcre -lresolv
/usr/bin/ld: dump_dns.o: in function `dump_dns':
./src/dump_dns.c:135: undefined reference to `_res_opcodes'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:88: prads] Error 1
```

Full buildd log: 
https://buildd.debian.org/status/fetch.php?pkg=prads=riscv64=0.3.3-7=1634546939=0

After some searching I found this related to libresolv. Using existing shim code
for FreeBSD I am able to fix FTBFS, which is included in the attached
patch.

If more help is needed, please let me know.

Cheers,
Eric
--- prads-0.3.3.orig/src/dump_dns.c
+++ prads-0.3.3/src/dump_dns.c
@@ -98,7 +98,7 @@ void printchars(char buf[NS_MAXDNAME], u
(cp) += INT32SZ; \
 } while (0)

-#ifdef __FreeBSD__
+#if defined(__FreeBSD__) || defined(__riscv)
 const char *_res_opcodes[] = {
 "QUERY",
 "IQUERY",

Bug#1022025: two reverts required, submitted to stable review list

[Salvatore Bonaccorso]

Hi,

On Fri, Oct 21, 2022 at 12:55:09PM +, Dan Coleman wrote:
> Hey,
> 
>  > On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote:
> 
>  > > So there are two patches who need to be reverted:
>  > >
>  > > 
> https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/
>  > > 
> https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/
> 
> 
> How do I apply these patches to see if they work for me? Thus far in
> this bug, I've just seen .patch files.

Here are those as patches.

If you trust unsigned binary packages build I would put somehwere I
can provide you those with those two applied. But again, after testing
make sure you reinstall the meta package and go back to the -18
version.

Regards,
Salvatore
From: Alex Deucher 
Date: Thu, 20 Oct 2022 11:38:56 -0400
Subject: Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code
 for vega"
Origin: https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/
Bug-Debian: https://bugs.debian.org/1022025

This reverts commit 9f55f36f749a7608eeef57d7d72991a9bd557341.

This patch was backported incorrectly when Sasha backported it and
the patch that caused the regression that this patch set fixed
was reverted in commit 412b844143e3 ("Revert "PCI/portdrv: Don't disable AER reporting in get_port_device_capability()"").
This isn't necessary and causes a regression so drop it.

Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Cc: Shuah Khan 
Cc: Sasha Levin 
Signed-off-by: Alex Deucher 
Cc: # 5.10
Tested-By: Diederik de Haas 
---
 drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c |  5 -
 drivers/gpu/drm/amd/amdgpu/soc15.c | 25 +
 2 files changed, 25 insertions(+), 5 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c b/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
index a1a8e026b9fa..1f2e2460e121 100644
--- a/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
@@ -1475,11 +1475,6 @@ static int sdma_v4_0_start(struct amdgpu_device *adev)
 		WREG32_SDMA(i, mmSDMA0_CNTL, temp);
 
 		if (!amdgpu_sriov_vf(adev)) {
-			ring = >sdma.instance[i].ring;
-			adev->nbio.funcs->sdma_doorbell_range(adev, i,
-ring->use_doorbell, ring->doorbell_index,
-adev->doorbell_index.sdma_doorbell_range);
-
 			/* unhalt engine */
 			temp = RREG32_SDMA(i, mmSDMA0_F32_CNTL);
 			temp = REG_SET_FIELD(temp, SDMA0_F32_CNTL, HALT, 0);
diff --git a/drivers/gpu/drm/amd/amdgpu/soc15.c b/drivers/gpu/drm/amd/amdgpu/soc15.c
index abd649285a22..7212b9900e0a 100644
--- a/drivers/gpu/drm/amd/amdgpu/soc15.c
+++ b/drivers/gpu/drm/amd/amdgpu/soc15.c
@@ -1332,6 +1332,25 @@ static int soc15_common_sw_fini(void *handle)
 	return 0;
 }
 
+static void soc15_doorbell_range_init(struct amdgpu_device *adev)
+{
+	int i;
+	struct amdgpu_ring *ring;
+
+	/* sdma/ih doorbell range are programed by hypervisor */
+	if (!amdgpu_sriov_vf(adev)) {
+		for (i = 0; i < adev->sdma.num_instances; i++) {
+			ring = >sdma.instance[i].ring;
+			adev->nbio.funcs->sdma_doorbell_range(adev, i,
+ring->use_doorbell, ring->doorbell_index,
+adev->doorbell_index.sdma_doorbell_range);
+		}
+
+		adev->nbio.funcs->ih_doorbell_range(adev, adev->irq.ih.use_doorbell,
+		adev->irq.ih.doorbell_index);
+	}
+}
+
 static int soc15_common_hw_init(void *handle)
 {
 	struct amdgpu_device *adev = (struct amdgpu_device *)handle;
@@ -1351,6 +1370,12 @@ static int soc15_common_hw_init(void *handle)
 
 	/* enable the doorbell aperture */
 	soc15_enable_doorbell_aperture(adev, true);
+	/* HW doorbell routing policy: doorbell writing not
+	 * in SDMA/IH/MM/ACV range will be routed to CP. So
+	 * we need to init SDMA/IH/MM/ACV doorbell range prior
+	 * to CP ip block init and ring test.
+	 */
+	soc15_doorbell_range_init(adev);
 
 	return 0;
 }
-- 
2.37.2

From: Alex Deucher 
Date: Thu, 20 Oct 2022 11:38:57 -0400
Subject: Revert "drm/amdgpu: make sure to init common IP before gmc"
Origin: https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/
Bug-Debian: https://bugs.debian.org/1022025

This reverts commit 7b0db849ea030a70b8fb9c9afec67c81f955482e.

The patches that this patch depends on were not backported properly
and the patch that caused the regression that this patch set fixed
was reverted in commit 412b844143e3 ("Revert "PCI/portdrv: Don't disable AER reporting in get_port_device_capability()"").
This isn't necessary and causes a regression so drop it.

Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Cc: Shuah Khan 
Cc: Sasha Levin 
Signed-off-by: Alex Deucher 
Cc: # 5.10
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 14 +++---
 1 file changed, 3 insertions(+), 11 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index 881045e600af..bde0496d2f15 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ 

Bug#1020043: pillow: FTBFS: ModuleNotFoundError: No module named 'PIL'

[Nilesh Patra]

I have NMU'd and put the pakcage to the DELAY queue with 7-day delay.
Let me know if I should cancel it or reduce the delay.

On Thu, 13 Oct 2022 17:58:54 +0530 Nilesh Patra  wrote:
> diff --git a/debian/rules b/debian/rules
> index 68e9a8c..96cc5ca 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -23,7 +23,7 @@ build-indep: build build-doc-stamp
>  build: build-stamp
>  
>  build-doc-stamp: build
> -   -PYTHONPATH=$(CURDIR)/$(wildcard build/lib.*-$(PY3VER)) $(MAKE) -C 
> docs html
> +   -PYTHONPATH=$(CURDIR)/$(wildcard build/lib.*) $(MAKE) -C docs html
> touch $@
>  
>  build-stamp: $(PY3VERS:%=build-stamp-python%) 
> $(PY3VERS:%=check-stamp-python%)

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1020446: marked as done (gdisk: FTBFS with popt 1.19+dfsg-1~exp1)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 13:34:14 +
with message-id 
and subject line Bug#1020446: fixed in gdisk 1.0.9-2.1
has caused the Debian Bug report #1020446,
regarding gdisk: FTBFS with popt 1.19+dfsg-1~exp1
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.)


-- 
1020446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdisk
Severity: important
Tags: ftbfs

Hi,

gdisk FTBFS and has a failing autopkgtest with popt 1.19+dfsg-1~exp1
from experimental. Build log and log from autopkgtest is attached.

This was reported upstream a while ago [1], and a partial fix was
applied [2]. This was later found insufficient and a new fix has been
proposed [3], as of this mail, the patch has not been merged.
FWIW, Fedora is using this patch [4].

Regards,
Håvard


[1] https://sourceforge.net/p/gptfdisk/mailman/message/37640877/
[2] 
https://sourceforge.net/p/gptfdisk/code/ci/5d5e76d369a412bfb3d2cebb5fc0a7509cef878d/
[3] https://sourceforge.net/p/gptfdisk/code/merge-requests/28/
[4] 
https://src.fedoraproject.org/fork/pmatilai/rpms/gdisk/raw/71100f6fd84dd21f1346917e4fa84a2eccdb70c3/f/gdisk-1.0.9-poptmisuse.patchautopkgtest [17:43:32]: starting date: 2022-09-20
autopkgtest [17:43:32]: version 5.25
autopkgtest [17:43:32]: host ci-worker01; command line: /usr/bin/autopkgtest --no-built-binaries '--setup-commands=echo '"'"'gdisk unstable/amd64'"'"' > /var/tmp/debci.pkg 2>&1 || true' '--setup-commands=echo '"'"'Acquire::Retries "10";'"'"' > /etc/apt/apt.conf.d/75retry 2>&1 || true' --user debci --apt-upgrade --add-apt-release=experimental --pin-packages=experimental=src:popt --output-dir /tmp/debci-worker-26264295-p2XpCgn6gv/autopkgtest-incoming/unstable/amd64/g/gdisk/26264295 gdisk -- lxc --sudo --name ci-263-5ce3cb6a autopkgtest-unstable-amd64
autopkgtest [17:43:36]:  test bed setup
Get:1 http://deb.debian.org/debian experimental InRelease [97.5 kB]
Get:2 http://deb.debian.org/debian experimental/contrib Sources [1,820 B]
Get:3 http://deb.debian.org/debian experimental/non-free Sources [2,512 B]
Get:4 http://deb.debian.org/debian experimental/main Sources [447 kB]
Get:5 http://deb.debian.org/debian experimental/non-free amd64 Packages [7,388 B]
Get:6 http://deb.debian.org/debian experimental/contrib amd64 Packages [6,056 B]
Get:7 http://deb.debian.org/debian experimental/main amd64 Packages [402 kB]
Fetched 964 kB in 1s (1,200 kB/s)
Reading package lists...
Get:1 http://deb.debian.org/debian unstable InRelease [158 kB]
Get:2 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Hit:3 http://deb.debian.org/debian experimental InRelease
Get:4 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:5 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:6 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:8 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:9 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:10 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:11 http://deb.debian.org/debian-debug unstable-debug/non-free Sources.diff/Index [63.3 kB]
Get:12 http://deb.debian.org/debian-debug unstable-debug/non-free amd64 Packages.diff/Index [63.3 kB]
Get:13 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:14 http://deb.debian.org/debian unstable/main Sources T-2022-09-20-1646.49-F-2022-09-20-1106.00.pdiff [22.7 kB]
Get:15 http://deb.debian.org/debian unstable/non-free Sources T-2022-09-20-1646.49-F-2022-09-20-1646.49.pdiff [31 B]
Get:16 http://deb.debian.org/debian unstable/contrib Sources T-2022-09-20-1646.49-F-2022-09-20-1646.49.pdiff [31 B]
Get:17 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-09-20-1646.49-F-2022-09-20-1106.00.pdiff [36.2 kB]
Get:18 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2022-09-20-1106.00-F-2022-09-20-1106.00.pdiff [5,854 B]
Get:14 http://deb.debian.org/debian unstable/main Sources T-2022-09-20-1646.49-F-2022-09-20-1106.00.pdiff [22.7 kB]
Get:16 http://deb.debian.org/debian unstable/contrib Sources T-2022-09-20-1646.49-F-2022-09-20-1646.49.pdiff [31 B]
Get:15 http://deb.debian.org/debian unstable/non-free Sources T-2022-09-20-1646.49-F-2022-09-20-1646.49.pdiff [31 B]
Get:17 http://deb.debian.org/debian unstable/main amd64 Packages 

Bug#1019606: marked as done (roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: YAML.load_file config_file)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 13:19:28 +
with message-id 
and subject line Bug#1019606: fixed in roodi 5.0.0-5
has caused the Debian Bug report #1019606,
regarding roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 
Failure/Error: YAML.load_file config_file
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.)


-- 
1019606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: roodi
Version: 5.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild roodi with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>  Failure/Error: YAML.load_file config_file
> 
>  Psych::DisallowedClass:
>Tried to load unspecified class: Regexp
>  # (eval):2:in `regexp'
>  # ./lib/roodi/core/runner.rb:135:in `load_config'
>  # ./lib/roodi/core/runner.rb:126:in `load_checks'
>  # ./lib/roodi/core/runner.rb:72:in `check'
>  # ./lib/roodi/core/runner.rb:81:in `check_content'
>  # ./spec/roodi/core/runner_spec.rb:52:in `block (4 levels) in  (required)>'
> 
> Deprecation Warnings:
> 
> Using `should_not` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/roodi/checks/abc_metric_method_check_spec.rb:12:in 
> `verify_content_score'.
> 
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly 
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
> enable `:should` instead. Called from 
> /<>/spec/roodi/core/runner_spec.rb:58:in `block (3 levels) in 
> '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 2 deprecation warnings total
> 
> Finished in 0.09081 seconds (files took 0.39761 seconds to load)
> 115 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/roodi/core/runner_spec.rb:7 # Roodi::Core::Runner running 
> against a file adds an error if file is not valid ruby
> rspec ./spec/roodi/core/runner_spec.rb:17 # Roodi::Core::Runner running 
> against a file checks that one file
> rspec ./spec/roodi/core/runner_spec.rb:24 # Roodi::Core::Runner running 
> against a directory checks all files in that directory recursively
> rspec ./spec/roodi/core/runner_spec.rb:31 # Roodi::Core::Runner running 
> without specifying files or directory checks all files in that directory 
> recursively
> rspec ./spec/roodi/core/runner_spec.rb:43 # Roodi::Core::Runner configuration 
> given a custom config file uses check from it
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> spec/roodi/checks/abc_metric_method_check_spec.rb 
> spec/roodi/checks/assignment_in_conditional_check_spec.rb 
> spec/roodi/checks/case_missing_else_check_spec.rb 
> spec/roodi/checks/class_line_count_check_spec.rb 
> spec/roodi/checks/class_name_check_spec.rb 
> spec/roodi/checks/class_variable_check_spec.rb 
> spec/roodi/checks/control_coupling_check_spec.rb 
> spec/roodi/checks/core_method_override_check_spec.rb 
> spec/roodi/checks/cyclomatic_complexity_block_check_spec.rb 
> spec/roodi/checks/cyclomatic_complexity_method_check_spec.rb 
> spec/roodi/checks/empty_rescue_body_check_spec.rb 
> spec/roodi/checks/for_loop_check_spec.rb 
> spec/roodi/checks/method_line_count_check_spec.rb 
> spec/roodi/checks/method_name_check_spec.rb 
> spec/roodi/checks/module_line_count_check_spec.rb 
> spec/roodi/checks/module_name_check_spec.rb 
> spec/roodi/checks/npath_complexity_method_check_spec.rb 
> spec/roodi/checks/parameter_number_check_spec.rb 
> spec/roodi/core/runner_spec.rb spec/roodi_task_spec.rb failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/roodi/roodi_5.0.0-4+rebuild1663007308_amd64-2022-09-12T18:28:29Z.build

To reproduce this, you need ruby-all-dev >= 1:3.0+2.  Depending on when you
read this, this might mean installing 

Processed: bug 1022169 is forwarded to https://github.com/llvm/llvm-project/issues/57521

[Debian Bug Tracking System]

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

> forwarded 1022169 https://github.com/llvm/llvm-project/issues/57521
Bug #1022169 [src:llvm-toolchain-15] llvm-toolchain-15: FTBFS on mips*el: 
static assertion failed: struct_kernel_stat_sz == sizeof(stat)
Ignoring request to change the forwarded-to-address of bug#1022169 to the same 
value
> thanks
Stopping processing here.

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

Bug#1022042: Similar problem with Radeon R7 360

[Andreas Wirooks]

I am running Debian 11 with linux-image-5.10.0-19-amd64 and can confirm a similar problem with an AMD Radeon R7 360 on an Intel X58 board with Intel Xeon W3530 CPU and classic BIOS.

 


Kernel parameters are radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.gpu_recovery=1

 

Nothing is logged and screen is black. No error messages at all. Works flawless with linux-image-5.10.0-18-amd64.

 

Kind regards,

Andreas

Bug#1022025: two reverts required, submitted to stable review list

[Dan Coleman]

Hey,

 > On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote:

 > > So there are two patches who need to be reverted:
 > >
 > > https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/
 > > https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/


How do I apply these patches to see if they work for me? Thus far in this bug, 
I've just seen .patch files.

Bug#1019724: Processed: tagging 1019724

[Santiago Ruano Rincón]

Control: tags -1 + pending

El 20/10/22 a las 17:58, Adrian Bunk escribió:
> On Thu, Oct 20, 2022 at 04:17:18PM +0200, Santiago Ruano Rincón wrote:
> > El 20/10/22 a las 11:30, Debian Bug Tracking System escribió:
> > > Processing commands for cont...@bugs.debian.org:
> > > 
> > > > tags 1019724 + ftbfs
> > > Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure
> > > Added tag(s) ftbfs.
> > 
> > Could you please clarify why it FTBFS? The warnings are present during
> > the build process, but I can build grep on a clean environment.
> 
> It makes another package FTBFS, with the affects and the ftbfs tag this 
> bug is displayed at
>   https://buildd.debian.org/status/package.php?p=kbuild

I am kind of surprised kbuild fails to build *now*. Lucas has run an
archive rebuild and he didn't report any package failing to build.

Please note this warning comes from an erroneous search pattern, and is
that pattern that should be fixed. In this case, grep has fixed its
behaviour.
Anyway, I am planing to apply the attached patch to temporarily disable
the warning by default.

Cheers,

 -- Santiago
Description: Temporarily disable the stray \ warnings. While the related
  patters are wrong, these warnings are causing trouble in Debian package
  builds and autopkgtests.
  This patch should be removed after coordination with the rest of the project
  to remove the erroneous patterns.
  Setting the DEBIAN_GREP_ENABLE_STRAY_BACKSLASH_WARN environement variable
  restores the upstream beahviour, enabling the warning.
Author: Santiago Ruano Rincón 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019724

Index: grep/lib/dfa.c
===
--- grep.orig/lib/dfa.c
+++ grep/lib/dfa.c
@@ -1547,7 +1547,10 @@ lex (struct dfa *dfa)
   if (!backslash)
 goto normal_char;
 stray_backslash:
-  if (dfa->syntax.dfaopts & DFA_STRAY_BACKSLASH_WARN)
+  char const *userevalwarn;
+  userevalwarn = getenv ("DEBIAN_GREP_ENABLE_STRAY_BACKSLASH_WARN");
+  if ((dfa->syntax.dfaopts & DFA_STRAY_BACKSLASH_WARN) &&
+  !(userevalwarn == NULL || *userevalwarn == '\0'))
 {
   char const *msg;
   char msgbuf[100];


signature.asc
Description: PGP signature

Processed: Re: Bug#1019724: Processed: tagging 1019724

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure
Added tag(s) pending.

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

Bug#1014137: marked as done (src:cpu-x: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 12:50:33 +
with message-id 
and subject line Bug#1014137: fixed in cpu-x 4.5.0-1
has caused the Debian Bug report #1014137,
regarding src:cpu-x: invalid maintainer address
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.)


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

Source: cpu-x
Version: 4.3.1-1
Tags: sid
Severity: serious
X-Debbugs-Cc: Mike Gabriel 

The maintainer address for cpu-x is invalid, see below.

Ansgar

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   martin.wimpr...@ubuntu.com
>     host mx.ubuntu.com [185.125.188.73]
>     SMTP error from remote mail server after RCPT 
> TO::
>     550 5.1.1 : Recipient address rejected:
>     User unknown in relay recipient table

Reporting-MTA: dns; mitropoulos.debian.org

Action: failed
Final-Recipient: rfc822;martin.wimpress@ubuntu.com
Status: 5.0.0
Remote-MTA: dns; mx.ubuntu.com
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in relay recipient table
--- End Message ---
--- Begin Message ---
Source: cpu-x
Source-Version: 4.5.0-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
cpu-x, 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.
Mike Gabriel  (supplier of updated cpu-x 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: Fri, 21 Oct 2022 10:01:16 +0200
Source: cpu-x
Architecture: source
Version: 4.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Wimpress 
Changed-By: Mike Gabriel 
Closes: 1014137 1020740
Changes:
 cpu-x (4.5.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - (This rebuilds the package against current libcpi). (Closes: #1020740).
   * debian/control:
 + Update Martin's mail address in Maintainer: field. (Closes: #1014137).
 + Bump versioned B-D on libcpuid to (>= 0.6.0).
   * debian/copyright:
 + Update auto-generated copyright.in file.
 + Update copyright attributions.
   * debian/patches:
 + Add 1001_typo-fix.patch
 + Mark 200*_*.patch files as Debian-specific.
Checksums-Sha1:
 804be1d4c00b8ea4e2aafe01ba2637083f309cdb 2105 cpu-x_4.5.0-1.dsc
 9dea1b3a44d300b69c723e9fe829ef1929d1238c 1924637 cpu-x_4.5.0.orig.tar.gz
 685d19bc6e1be3d6150de7905a94a8b212b7e68b 8828 cpu-x_4.5.0-1.debian.tar.xz
 27e9a861e261c42cb7ce490fbe52d0a5b12e8987 15153 cpu-x_4.5.0-1_source.buildinfo
Checksums-Sha256:
 8f3028e5edf7dcde8d8e7486dd9ac516c5231b98ddb82bc8a00e2ffdd80b9710 2105 
cpu-x_4.5.0-1.dsc
 1273b1c16da73e2a4e3f3e13139fb39e5c61bc1d54d7d1b05704ea0ff4001037 1924637 
cpu-x_4.5.0.orig.tar.gz
 abd6736e117f83088dd43711aef435ac95dd498e778a500d5d5fba9b38211009 8828 
cpu-x_4.5.0-1.debian.tar.xz
 3ac331a36ee987ee58a72ea24625ada80c95d5984311cec08567c02ff94f2e73 15153 
cpu-x_4.5.0-1_source.buildinfo
Files:
 a7a0e95424db2647af7d86838243ad0d 2105 x11 optional cpu-x_4.5.0-1.dsc
 7359562af95a97f66789a91d594e867e 1924637 x11 optional cpu-x_4.5.0.orig.tar.gz
 bf6164e03741be974f9a55b8ffcf5473 8828 x11 optional cpu-x_4.5.0-1.debian.tar.xz
 8338381aeaa8700bc504a61e04dad66c 15153 x11 optional 
cpu-x_4.5.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmNSi90VHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxVi8P/j3obGQglcqJJjagl4b4V49RC64D
LtqVAe+sc6RCBff5dvlpMlCqwCdX/4DxY3KkskhZhZzYDrf0nJa6PK1YceePubyk
AdWcLrr4+bbUgMqrjkWXs54La3Q5uZeX+YMexYk6Dxowl/DuQ/W+uOyLGgtldT7U
3SkzuIWU67OML7zMUl3xsItN/DCFNCMy9z12kZg2ucFX1UBfze6+pEz7G3/RGf4b
pSlUqZ4Z8iC/W3VH2ZhX507sp52i8sys/4qQAvb32oDsiKZDIiChLLpdrIHnt6Du
Jmy9cLEKXvUy2E0MqFA944Fg4DKJzJ3RzXce4hCiAo34hPrRBkE3+cQ3F5uwVo4J
Guig7uFTG4sjRjaU5JAyL0HwQs70Vwak1dbAS3w2vQy6lbcgCcuWmTSVxhFbltO7
xfbUD+zgPOhIqxrHwhfiuNHGPmcxOT4J7YW2tuPbwaoUwtfVzxkzxboAGjiHjhlZ
gFOh2NO4pLpsw+jvJtlRLN5mJtrSVQT654+dlr5uxNNxGqHxBpCbQwUylz6Sf3LH

Bug#1022174: linux-image-6.0.0-1-amd64: nvidia 470 modul builds successfully, but does not get loaded on boot -> no X

[Michael Hatzold]

Package: src:linux
Version: 6.0.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Installing linux-image 6.0.0.1 (may not be the *exact* nam, but you'll figure 
it out

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
The nvidia470 module seems to be build (?), no error message

On reeboot with the newwly installed kernel there are red *Failed* messages. 
The first one stating:

*Failed*  start load Kernel modules (or the like)

The boot continues with some more *Failed* messages

   * What outcome did you expect instead?

all neccessary modules, including a working nvidia 470 modul should be loaded


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


BTW:
I am writing this report on a terminal (i.e. no X -> ctrl-Alt_F2)
reportbug asks *repeatedly* for sudo PW (for the kernel log) (I don't want to 
use 'sudo' which is not configured for that reason)
I am sure most people will give up writing a bug report at this point.

Apart from this:
I hope the internal reportbug-email works (which it didn't in recent times) 
because I don't know - being here now outside of X - how to forward it to my 
email client. 


-- Package-specific info:
** Version:
Linux version 6.0.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-5) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.2-1 (2022-10-16)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.0.0-1-amd64 
root=UUID=655268bd-541f-4863-a960-951dc0cdcb46 ro quiet systemd.show_status=1

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: wortmann
product_name: G31M-ES2L
product_version: 
chassis_vendor: Gigabyte Technology Co., Ltd.
chassis_version: 
bios_vendor: Award Software International, Inc.
bios_version: F9h WG
board_vendor: Gigabyte Technology Co., Ltd.
board_name: G31M-S2L
board_version: x.x

** Loaded modules:
bnep
8021q
garp
stp
mrp
llc
qrtr
cpufreq_ondemand
cpufreq_powersave
cpufreq_userspace
iptable_nat
cpufreq_conservative
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
iptable_mangle
iptable_filter
bluetooth
jitterentropy_rng
sha512_ssse3
sha512_generic
ctr
drbg
ansi_cprng
ecdh_generic
rfkill
ecc
sunrpc
binfmt_misc
rc_hauppauge
em28xx_rc
rc_core
si2157
si2168
i2c_mux
em28xx_dvb
dvb_core
em28xx
tveeprom
videodev
mc
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
snd_hda_codec_hdmi
iTCO_wdt
coretemp
intel_pmc_bxt
snd_emu10k1
iTCO_vendor_support
snd_hda_intel
watchdog
snd_util_mem
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_hda_codec
snd_ac97_codec
pcspkr
serio_raw
ac97_bus
snd_hda_core
snd_rawmidi
snd_seq_device
snd_hwdep
evdev
snd_pcm_oss
snd_mixer_oss
snd_pcm
emu10k1_gp
gameport
snd_timer
snd
soundcore
acpi_cpufreq
rng_core
sg
loop
drivetemp
parport_pc
ppdev
lp
drm
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
btrfs
blake2b_generic
zstd_compress
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
hid_generic
usbhid
hid
sd_mod
t10_pi
crc64_rocksoft
crc64
crc_t10dif
crct10dif_generic
crct10dif_common
ata_generic
ata_piix
libata
scsi_mod
i2c_i801
i2c_smbus
scsi_common
r8169
lpc_ich
ehci_pci
realtek
uhci_hcd
ehci_hcd
usbcore
mdio_devres
libphy
usb_common
floppy
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0] (rev 10)
Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express DRAM 
Controller [1458:5000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI 
Express Root Port [8086:29c1] (rev 10) (prog-if 00 [Normal decode])
Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express PCI 
Express Root Port [1458:5000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 01)
Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD (Realtek ALC887) 
[1458:a002]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: 

Bug#1022124: libdbd-oracle-perl needs binaries uploaded for the perl 5.36 transitions

[Alex Muntada]

Hi Adrian,

> libdbd-oracle-perl cannot be built on the buildds,
> and it needs binaries uploaded for the perl 5.36 transition.

Please, don't hesitate to remove libdbd-oracle-perl from testing
for the perl 5.36 transition to proceed. I'll try to have those
binaries by next week, but I don't want to stall the transition.

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#984057: marked as done (infinipath-psm: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 12:20:02 +
with message-id 
and subject line Bug#984057: fixed in infinipath-psm 3.3+20.604758e7-6.2
has caused the Debian Bug report #984057,
regarding infinipath-psm: ftbfs with GCC-11
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.)


-- 
984057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:infinipath-psm
Version: 3.3+20.604758e7-6.1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/infinipath-psm_3.3+20.604758e7-6.1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  |^~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:51: ptl_rcvthread.o] Error 1
make[3]: Leaving directory '/<>/ptl_ips'
make[3]: Entering directory '/<>/ptl_am'
cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fcommon   -Wall -Werror  -fpic -fPIC 
-D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall -Werror  -fpic 
-fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  -DPSM_USE_SYS_UUID  -DNVALGRIND 
-I. -I/<>/include -I/<>/mpspawn 
-I/<>/include/linux-x86_64  -I/<>  -c am_reqrep.c -o 
am_reqrep.o
cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fcommon   -Wall -Werror  -fpic -fPIC 
-D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall -Werror  -fpic 
-fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  -DPSM_USE_SYS_UUID  -DNVALGRIND 
-I. -I/<>/include -I/<>/mpspawn 
-I/<>/include/linux-x86_64  -I/<>  -c 
am_reqrep_shmem.c -o am_reqrep_shmem.o
In file included from /<>/include/ipath_intf.h:51,
 from /<>/include/ipath_user.h:60,
 from /<>/psm_user.h:45,
 from am_reqrep_shmem.c:40:
am_reqrep_shmem.c: In function ‘amsh_ep_connreq_wrap’:
/<>/include/linux-x86_64/sysdep.h:109:5: error: array subscript 
‘struct xchg_dummy[0]’ is partly outside array bounds of ‘psmi_spinlock_t[1]’ 
{aka ‘ips_atomic_t[1]’} [-Werror=array-bounds]
  109 | asm volatile(LOCK_PREFIX "cmpxchgl %1,%2"
  | ^~~
In file included from am_reqrep_shmem.c:40:
/<>/psm_user.h:103:20: note: while referencing ‘psmi_progress_lock’
  103 |   psmi_spinlock_t  psmi_progress_lock;
  |^~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:41: am_reqrep_shmem.o] Error 1
make[3]: Leaving directory '/<>/ptl_am'
make[3]: Entering directory '/<>/libuuid'
cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fcommon   -Wall -Werror  -fpic -fPIC 
-D_GNU_SOURCE -funwind-tables   -O3 -g3   -DNVALGRIND   -Wall -Werror  -fpic 
-fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  -DPSM_USE_SYS_UUID  -DNVALGRIND 
-DPSM_UUID=1 -Wno-unused-function -I. -I/<>/include 
-I/<>/mpspawn -I/<>/include/linux-x86_64  
-I/<> -I/libuuid -c psm_uuid.c -o psm_uuid.o
make[3]: Leaving directory '/<>/libuuid'
make[3]: Entering directory '/<>/ipath'
cc   -Wall   -fpic -fPIC -D_GNU_SOURCE -funwind-tables   -O3 -g3  
-DPSM_USE_SYS_UUID -D_GNU_SOURCE -I. -I/<>/include 

Bug#1022158: marked as done (libdata-uuid-libuuid-perl is empty)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 12:20:14 +
with message-id 
and subject line Bug#1022158: fixed in libdata-uuid-libuuid-perl 0.05-5
has caused the Debian Bug report #1022158,
regarding libdata-uuid-libuuid-perl is empty
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.)


-- 
1022158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdata-uuid-libuuid-perl
Version: 0.05-4
Severity: serious

$ dpkg -L libdata-uuid-libuuid-perl
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libdata-uuid-libuuid-perl
/usr/share/doc/libdata-uuid-libuuid-perl/changelog.Debian.amd64.gz
/usr/share/doc/libdata-uuid-libuuid-perl/changelog.Debian.gz
/usr/share/doc/libdata-uuid-libuuid-perl/changelog.gz
/usr/share/doc/libdata-uuid-libuuid-perl/copyright
$
--- End Message ---
--- Begin Message ---
Source: libdata-uuid-libuuid-perl
Source-Version: 0.05-5
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libdata-uuid-libuuid-perl, 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.
gregor herrmann  (supplier of updated 
libdata-uuid-libuuid-perl 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, 21 Oct 2022 13:59:29 +0200
Source: libdata-uuid-libuuid-perl
Architecture: source
Version: 0.05-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1022158
Changes:
 libdata-uuid-libuuid-perl (0.05-5) unstable; urgency=medium
 .
   * Team upload.
   * Simplify alternative test dependency.
   * Declare compliance with Debian Policy 4.6.1.
   * Set Rules-Requires-Root: no.
   * Enable all hardening flags.
   * Annotate test-only build dependencies with .
   * Add patch from CPAN RT to fix compilation with gcc-12.
 Thanks to Adrian Bunk for the bug report. (Closes: #1022158)
   * Add patch to make the build abort if the check for uuid fails.
 Otherwise we end up with an empty package (cf. #1022158).
Checksums-Sha1:
 0f205e4616d0608484df34d9e60634f42c85b445 2538 
libdata-uuid-libuuid-perl_0.05-5.dsc
 8a0dee19e2b21ccbf63310077cd0fd2726d7b3b7 4544 
libdata-uuid-libuuid-perl_0.05-5.debian.tar.xz
Checksums-Sha256:
 c488faf22c60b71b18b8c4977c77a91c874139ecad29185217ed1a8a29dfb09c 2538 
libdata-uuid-libuuid-perl_0.05-5.dsc
 20029e0331d4a36af71fc7b45b8db844e86e4232bc5c909f42b3e26e10611508 4544 
libdata-uuid-libuuid-perl_0.05-5.debian.tar.xz
Files:
 0557733e3e79ae2c35cef9d4d33822da 2538 perl optional 
libdata-uuid-libuuid-perl_0.05-5.dsc
 dc9dd11bdbfdf40ac69e52104e8f605f 4544 perl optional 
libdata-uuid-libuuid-perl_0.05-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNSimVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYmIhAAgh6Vh4X6JLyJ4Yj7eRJrlyCdK9fDk2MHRno/R+B1H3vycFBSEZEs1+2t
cAGAQpCjEBY9UdknGzFXFjGAt1cqPkf+dVtJ6hTQpyPFBF7xDXqJRa9HFj/vs5NV
uxGGFZ0zydzBoFukl4gEf6kzOsdhw4qo3IYU6O00fwtf8ZHf0g2Q05j11O/VX0H/
VjJpulnTJvVc7ibrmNQBFgIWcG1rgbiygpLdeiIrZ627lJbMwTOIR9tA27xsDIQs
TE9S+bjPENcaqLL4hzsgBXAR2YpKLxg2/S7MGv4KB66WjLssYDnjT9fgNbdP1zsN
VdZFxkah4IN7uACO+kmlfEOfKqS01SHtY6qWxYdvSPT2XcGbVHHW8gZXt7mPEPzD
Uljb/NYctzYWttgbuzECDDvBeDr4vGp43+n9CE6B21BQQ6veK1feCt9upGs17WE9
IP6WrYPfLQuUef+dF1YBvqxYsHkrkPUKv4vX+4I9k8LjIeFZxFPAJ6v8rB0XtZ1h
Sf6BBcTMOtrsZjXKsWa50FII5U3KWWV6Gp3NSLsesyQ/JoAuClvGbILtDKO0yAaG
/SnzOIpmY84V/dlgm5aT+w3o88ozBiHDd3JnAR9uVAbII5MTaDijgbW73xrSdz/n
4drIdMedAarL8V/7YpxrJ8ENvmluQQoQqPnUNiN68sL2kRJTSEM=
=97Yc
-END PGP SIGNATURE End Message ---

Bug#1020081: marked as done (aft: FTBFS: make: *** [debian/rules:47: binary-indep] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2022 12:18:58 +
with message-id 
and subject line Bug#1020081: fixed in aft 2:5.098-6
has caused the Debian Bug report #1020081,
regarding aft: FTBFS: make: *** [debian/rules:47: binary-indep] Error 25
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.)


-- 
1020081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aft
Version: 2:5.098-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> test -z "/<>/debian/aft/usr/bin" || mkdir -p -- . 
> "/<>/debian/aft/usr/bin"
>  /usr/bin/install -c 'aft' '/<>/debian/aft/usr/bin/aft'
> test -z "/<>/debian/aft/usr/share/doc/aft/backends" || mkdir -p 
> -- . "/<>/debian/aft/usr/share/doc/aft/backends"
>  /usr/bin/install -c -m 644 'aft-dbarticle.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-dbarticle.dat'
>  /usr/bin/install -c -m 644 'aft-bn-html.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-bn-html.dat'
>  /usr/bin/install -c -m 644 'aft-html.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-html.dat'
>  /usr/bin/install -c -m 644 'aft-lout.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-lout.dat'
>  /usr/bin/install -c -m 644 'aft-loutbook.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-loutbook.dat'
>  /usr/bin/install -c -m 644 'aft-loutreport.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-loutreport.dat'
>  /usr/bin/install -c -m 644 'aft-rtf.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-rtf.dat'
>  /usr/bin/install -c -m 644 'aft-tex.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-tex.dat'
>  /usr/bin/install -c -m 644 'aft-xhtml.dat' 
> '/<>/debian/aft/usr/share/doc/aft/backends/aft-xhtml.dat'
> test -z "/<>/debian/aft/usr/share/doc/aft" || mkdir -p -- . 
> "/<>/debian/aft/usr/share/doc/aft"
>  /usr/bin/install -c -m 644 'aft2rtf-doc.rtf' 
> '/<>/debian/aft/usr/share/doc/aft/aft2rtf-doc.rtf'
>  /usr/bin/install -c -m 644 'aft-refman.html' 
> '/<>/debian/aft/usr/share/doc/aft/aft-refman.html'
>  /usr/bin/install -c -m 644 'aft.gif' 
> '/<>/debian/aft/usr/share/doc/aft/aft.gif'
>  /usr/bin/install -c -m 644 'aft.jpg' 
> '/<>/debian/aft/usr/share/doc/aft/aft.jpg'
>  /usr/bin/install -c -m 644 'aft.eps' 
> '/<>/debian/aft/usr/share/doc/aft/aft.eps'
>  /usr/bin/install -c -m 644 'ChangeLog.aft' 
> '/<>/debian/aft/usr/share/doc/aft/ChangeLog.aft'
> test -z "/<>/debian/aft/usr/share/doc/aft/examples" || mkdir -p 
> -- . "/<>/debian/aft/usr/share/doc/aft/examples"
>  /usr/bin/install -c -m 644 'aft.aft' 
> '/<>/debian/aft/usr/share/doc/aft/examples/aft.aft'
>  /usr/bin/install -c -m 644 'aft-refman.aft' 
> '/<>/debian/aft/usr/share/doc/aft/examples/aft-refman.aft'
>  /usr/bin/install -c -m 644 'aft2rtf-doc.aft' 
> '/<>/debian/aft/usr/share/doc/aft/examples/aft2rtf-doc.aft'
> test -z "/<>/debian/aft/usr/share/aft" || mkdir -p -- . 
> "/<>/debian/aft/usr/share/aft"
>  /usr/bin/install -c -m 644 'aft.pl' 
> '/<>/debian/aft/usr/share/aft/aft.pl'
>  /usr/bin/install -c -m 644 'aft-dbarticle.pm' 
> '/<>/debian/aft/usr/share/aft/aft-dbarticle.pm'
>  /usr/bin/install -c -m 644 'aft-bn-html.pm' 
> '/<>/debian/aft/usr/share/aft/aft-bn-html.pm'
>  /usr/bin/install -c -m 644 'aft-html.pm' 
> '/<>/debian/aft/usr/share/aft/aft-html.pm'
>  /usr/bin/install -c -m 644 'aft-lout.pm' 
> '/<>/debian/aft/usr/share/aft/aft-lout.pm'
>  /usr/bin/install -c -m 644 'aft-loutbook.pm' 
> '/<>/debian/aft/usr/share/aft/aft-loutbook.pm'
>  /usr/bin/install -c -m 644 'aft-loutreport.pm' 
> '/<>/debian/aft/usr/share/aft/aft-loutreport.pm'
>  /usr/bin/install -c -m 644 'aft-rtf.pm' 
> '/<>/debian/aft/usr/share/aft/aft-rtf.pm'
>  /usr/bin/install -c -m 644 'aft-tex.pm' 
> '/<>/debian/aft/usr/share/aft/aft-tex.pm'
>  /usr/bin/install -c -m 644 'aft-xhtml.pm' 
> '/<>/debian/aft/usr/share/aft/aft-xhtml.pm'
>  /usr/bin/install -c -m 644 'AFT.pm' 
> '/<>/debian/aft/usr/share/aft/AFT.pm'
> test -z "/<>/debian/aft/usr/share/aft" || mkdir -p -- . 
> "/<>/debian/aft/usr/share/aft"
>  /usr/bin/install -c 'compile.pl' 
> '/<>/debian/aft/usr/share/aft/compile.pl'
>  /usr/bin/install -c 'postrtf.pl' 
> '/<>/debian/aft/usr/share/aft/postrtf.pl'
>  /usr/bin/install -c 'launch_ie.pl' 
> '/<>/debian/aft/usr/share/aft/launch_ie.pl'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving 

Processed: Bug#1022158 marked as pending in libdata-uuid-libuuid-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022158 [libdata-uuid-libuuid-perl] libdata-uuid-libuuid-perl is empty
Ignoring request to alter tags of bug #1022158 to the same tags previously set

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

Bug#1022158: marked as pending in libdata-uuid-libuuid-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #1022158 in libdata-uuid-libuuid-perl 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/perl-team/modules/packages/libdata-uuid-libuuid-perl/-/commit/b5618c37603309d223b3ecae91c27064ba305cb9


Add patch from CPAN RT to fix compilation with gcc-12.

Thanks: Adrian Bunk for the bug report.
Closes: #1022158


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022158

Bug#1021737: lava: CVE-2022-42902

[Antonio Terceiro]

On Wed, Oct 19, 2022 at 09:57:34PM +0200, Moritz Muehlenhoff wrote:
> On Tue, Oct 18, 2022 at 06:09:42PM -0300, Antonio Terceiro wrote:
> > Hi,
> > 
> > On Thu, Oct 13, 2022 at 09:13:18PM +0200, Moritz Mühlenhoff wrote:
> > > Source: lava
> > > X-Debbugs-CC: t...@security.debian.org
> > > Severity: grave
> > > Tags: security
> > > 
> > > Hi,
> > > 
> > > The following vulnerability was published for lava.
> > > 
> > > CVE-2022-42902[0]:
> > > | In Linaro Automated Validation Architecture (LAVA) before 2022.10,
> > > | there is dynamic code execution in lava_server/lavatable.py. Due to
> > > | improper input sanitization, an anonymous user can force the lava-
> > > | server-gunicorn service to execute user-provided code on the server.
> > > 
> > > https://git.lavasoftware.org/lava/lava/-/merge_requests/1834
> > > https://git.lavasoftware.org/lava/lava/-/commit/e66b74cd6c175ff8826b8f3431740963be228b52?merge_request_iid=1834
> > > 
> > > If you fix the vulnerability please also make sure to include the
> > > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> > > 
> > > For further information see:
> > > 
> > > [0] https://security-tracker.debian.org/tracker/CVE-2022-42902
> > > https://www.cve.org/CVERecord?id=CVE-2022-42902
> > > 
> > > Please adjust the affected versions in the BTS as needed.
> > 
> > I have uploaded a fix version to unstable (latest upstream), and I would
> > like to upload the attached debdiff to -security. That package builds
> > cleanly and passes its autopkgtest on bullseye. Let me know.
> 
> Ack, we can fix this via a DSA. The debdiff looks fine content-wise,
> but the deb111u1 version is slightly off by 100 Debian releases ;-)
> 
> So please change to +deb11u1 and upload to security-master.

Heh, my mistake.

Just uploaded.


signature.asc
Description: PGP signature

Processed: Re: Bug#1022158: libdata-uuid-libuuid-perl is empty

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=62115
Bug #1022158 [libdata-uuid-libuuid-perl] libdata-uuid-libuuid-perl is empty
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=62115'.
> tag -1 + patch pending
Bug #1022158 [libdata-uuid-libuuid-perl] libdata-uuid-libuuid-perl is empty
Added tag(s) patch and pending.

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

Bug#1022158: libdata-uuid-libuuid-perl is empty

[gregor herrmann]

Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=62115
Control: tag -1 + patch pending

On Fri, 21 Oct 2022 10:37:06 +0300, Adrian Bunk wrote:

> Package: libdata-uuid-libuuid-perl
> Version: 0.05-4
> Severity: serious
> 
> $ dpkg -L libdata-uuid-libuuid-perl
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/libdata-uuid-libuuid-perl
> /usr/share/doc/libdata-uuid-libuuid-perl/changelog.Debian.amd64.gz
> /usr/share/doc/libdata-uuid-libuuid-perl/changelog.Debian.gz
> /usr/share/doc/libdata-uuid-libuuid-perl/changelog.gz
> /usr/share/doc/libdata-uuid-libuuid-perl/copyright
> $

From the build log, both at
https://buildd.debian.org/status/fetch.php?pkg=libdata-uuid-libuuid-perl=amd64=0.05-4%2Bb1=1666258243=0
and locally:

   dh_auto_configure
/usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-ffile-prefix-map=/build/libdata-uuid-libuuid-perl-0.05=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 
-ffile-prefix-map=/build/libdata-uuid-libuuid-perl-0.05=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now"
Checking if your kit is complete...
Looks good
trying x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64  -o /dev/null hdr_check.h
Generating a Unix-style Makefile
Writing Makefile for Data::UUID::LibUUID
Writing MYMETA.yml and MYMETA.json
hdr_check.h:2: fatal error: cannot write PCH file: required memory segment 
unavailable
compilation terminated.

*** ERROR:  seems to be missing ***
please install libuuid from e2fsprogs (available as uuid-dev on debian)


https://rt.cpan.org/Public/Bug/Display.html?id=62115
contains a patch from Mageia for gcc-12 …

… and it works


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1022169 https://github.com/llvm/llvm-project/issues/57521
Bug #1022169 [src:llvm-toolchain-15] llvm-toolchain-15: FTBFS on mips*el: 
static assertion failed: struct_kernel_stat_sz == sizeof(stat)
Set Bug forwarded-to-address to 
'https://github.com/llvm/llvm-project/issues/57521'.
> thanks
Stopping processing here.

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

Bug#1022169: llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat)

[Sylvestre Ledru]

Le 21/10/2022 à 13:32, Simon McVittie a écrit :

Source: llvm-toolchain-15
Version: 1:15.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source, making mesa unbuildable
User: debian-m...@lists.debian.org
Usertags: mipsel mips64el
X-Debbugs-Cc: debian-m...@lists.debian.org, m...@packages.debian.org
Control: affects -1 + src:mesa

Quoting from mips64el buildd logs, but mipsel has a similar failure:


/<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_linux.cpp:67:1:
 error: static assertion failed due to requirement 'struct_kernel_stat_sz == sizeof(stat)':
COMPILER_CHECK(struct_kernel_stat_sz == sizeof(struct stat));

Strictly speaking this is not a regression because llvm-toolchain-15 was
never built successfully on mips*el, but I think it should be treated as
RC anyway, because older llvm-toolchain-* were buildable on mips*el (and
mesa is already using llvm-toolchain-15, making it a key package).


I reported it early sept:

https://github.com/llvm/llvm-project/issues/57521

S

Bug#1022169: llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat)

[Simon McVittie]

Source: llvm-toolchain-15
Version: 1:15.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source, making mesa unbuildable
User: debian-m...@lists.debian.org
Usertags: mipsel mips64el
X-Debbugs-Cc: debian-m...@lists.debian.org, m...@packages.debian.org
Control: affects -1 + src:mesa

Quoting from mips64el buildd logs, but mipsel has a similar failure:

> /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_linux.cpp:67:1:
>  error: static assertion failed due to requirement 'struct_kernel_stat_sz == 
> sizeof(stat)':
> COMPILER_CHECK(struct_kernel_stat_sz == sizeof(struct stat));

Strictly speaking this is not a regression because llvm-toolchain-15 was
never built successfully on mips*el, but I think it should be treated as
RC anyway, because older llvm-toolchain-* were buildable on mips*el (and
mesa is already using llvm-toolchain-15, making it a key package).

smcv

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

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

Processed: llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:mesa
Bug #1022169 [src:llvm-toolchain-15] llvm-toolchain-15: FTBFS on mips*el: 
static assertion failed: struct_kernel_stat_sz == sizeof(stat)
Added indication that 1022169 affects src:mesa

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

Bug#1004154: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC

[TJ]

On Sat, 12 Feb 2022 08:21:55 + Felix Leimbach  wrote:

I noticed that vgamem_mb was still low (32 MB).
So I changed to this (slightly wasteful) command-line and am now running the 
latest kernel (5.15.0-3-amd64):

-vga none -device 
qxl-vga,ram_size_mb=256,vgamem_mb=256,vram_size_mb=256,vram64_size_mb=256,max_outputs=1

Will report back if that helps.


Did the vgamem_mb change fix the issue?

This bug is currently keeping the package out of bookworm and, if it was 
a user-specific issue, ought to be closed and the package reintroduced 
to bookworm.


I'm currently doing a full-upgrade bullseye to bookworm and this removal 
is a blocker for VMs.


OpenPGP_0xEFEC37A429CD6080.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1005899: mplayer: should not release with bookworm

[fabian]

Am 21.10.2022 12:36, schrieb Tj:

I require mencoder specifically to handle some old legacy format
conversion where I found ffmpeg fails despite many attempts to work
around the issues with various command-line options.


Ever considered reporting these issues to the ffmpeg project?

 - Fabian

Bug#1005899: mplayer: should not release with bookworm

[Tj]

On Wed, 16 Mar 2022 20:09:59 +0100 Diederik de Haas 
 wrote:

On 16 Feb 2022 23:25:00 +0100 Sebastian Ramacher  wrote:
> Source: mplayer
> Version: 2:1.4+ds1-3
> Severity: serious
> Tags: sid bookworm
> 
> I think we should not include mplayer in bookworm. 
> mpv is a worthy replacement for mplayer.


I just found this report whilst doing a buster > bookworm full-upgrade.

I have both mplayer and mencoder installed and both were listed for removal.

I require mencoder specifically to handle some old legacy format 
conversion where I found ffmpeg fails despite many attempts to work 
around the issues with various command-line options.


Specifically RealMedia multi-stream formats originally recorded in the 
1999-2004 time-frame.

Processed: reassign 1022062 to src:linux, forcibly merging 1022025 1022062

[Debian Bug Tracking System]

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

> reassign 1022062 src:linux
Bug #1022062 [linux-image-5.10.0-19-amd64] regression on amdgpu: drm_kms_helper 
"flip_done timed out" messages during boot and console freeze
Bug #1022147 [linux-image-5.10.0-19-amd64] regression on amdgpu: drm_kms_helper 
"flip_done timed out" messages during boot and console freeze
Bug reassigned from package 'linux-image-5.10.0-19-amd64' to 'src:linux'.
Bug reassigned from package 'linux-image-5.10.0-19-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #1022062 to the same values 
previously set
Ignoring request to alter found versions of bug #1022147 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1022062 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1022147 to the same values 
previously set
> forcemerge 1022025 1022062
Bug #1022025 [src:linux] Can't enable amdgpu driver in 
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails 
to boot on machines with AMD integrated graphics
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Bug #1022070 [src:linux] Booting semi-hangs with 
'drm_atomic_helper_wait_for_flip_done' errors and alike
Bug #1022062 [src:linux] regression on amdgpu: drm_kms_helper "flip_done timed 
out" messages during boot and console freeze
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/drm/amd/-/issues/2216'.
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/drm/amd/-/issues/2216'.
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Removed indication that 1022062 affects linux-image-5.10.0-19-rt-amd64
Removed indication that 1022147 affects linux-image-5.10.0-19-rt-amd64
Marked as found in versions linux/5.10.149-1.
Marked as found in versions linux/5.10.149-1.
Added tag(s) pending, patch, moreinfo, and upstream.
Added tag(s) pending, patch, upstream, and moreinfo.
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails 
to boot on machines with AMD integrated graphics
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Bug #1022070 [src:linux] Booting semi-hangs with 
'drm_atomic_helper_wait_for_flip_done' errors and alike
Bug #1022147 [src:linux] regression on amdgpu: drm_kms_helper "flip_done timed 
out" messages during boot and console freeze
Merged 1022025 1022042 1022051 1022062 1022070 1022147
> thanks
Stopping processing here.

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

Bug#1018754: telegram-cli: Outdated app that is no longer supported

[Axel Beckert]

Hi,

aexlfow...@web.de wrote:
> when I start the program it asks for my phone number. When I give it it
> says following:
>  *** 1661844939.688455 Notification API_64BIT_LOGIN_APP_OUTDATED_39:
> You are using an outdated app that is no longer supported. To access
> your messages, please update your app to the latest version.
[…]
> I don't think it will be fixed,

The original developer clearly seems to have stalled working on it:

https://github.com/vysheng/tg says last commit was on Mar 23, 2016.

But there seem at least two very active forks:

* https://github.com/szqdong/tg
* https://github.com/kenorb-contrib/tg

Last commit in both is from 2022 Jul 26. (It's the same commit of
kenorb — not kenorb-contrib — in both cases.)

I'm though not sure which of these would be better to base the package
on in the future.

Bastian Germann wrote:
> Setting appropriate severity. The application is not usable.

Thanks!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: tagging 1004805

[Debian Bug Tracking System]

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

> # 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1004805;filename=ffmpeg-5-ed86b39.patch;msg=14
> tags 1004805 + patch
Bug #1004805 [src:xmms2] xmms2: FTBFS with ffmpeg 5.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1022025: Upstream Reports

[Christoph Zechner]

On Thu, 20 Oct 2022 18:36:21 +0200 Diederik de Haas 
 wrote:

On Thursday, 20 October 2022 17:36:33 CEST Christoph Zechner wrote:
> I hope this helps, if there's something additional I could contribute,
> please let me know!

It's probably best to participate in the upstream issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2216

Thank you for the pointer, I submitted my information there as well.


On Thu, 20 Oct 2022 22:10:27 +0200 Salvatore Bonaccorso 
 wrote:> Hi all,

>
> On Thu, Oct 20, 2022 at 07:41:51PM +, Doublychargedhiggs wrote:
> > Did the same as Dan, i.e built the kernel (apt-get install source) 
with the upstream proposed patch

> > 0001-drm-amdgpu-fix-sdma-doorbell-init-ordering-on-APUs.patch
> > using the mentioned test-patches script. The kernel really builds, 
is even installable, but then hangs

> > as before at boot, as Dan reported before.
> >
> > However, i'm even less experienced kernel builder than Dan (my 1st 
kernel build ever)...

>
> So there are two patches who need to be reverted:
>
> 
https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/
> 
https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/

>
> Salvatore

Perfect, thank you, this solved the issue on my machine (Ryzen 7 PRO 
4750U) as well.


Best regards
Christoph Zechner

Bug#1022158: libdata-uuid-libuuid-perl is empty

[Adrian Bunk]

Package: libdata-uuid-libuuid-perl
Version: 0.05-4
Severity: serious

$ dpkg -L libdata-uuid-libuuid-perl
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libdata-uuid-libuuid-perl
/usr/share/doc/libdata-uuid-libuuid-perl/changelog.Debian.amd64.gz
/usr/share/doc/libdata-uuid-libuuid-perl/changelog.Debian.gz
/usr/share/doc/libdata-uuid-libuuid-perl/changelog.gz
/usr/share/doc/libdata-uuid-libuuid-perl/copyright
$

Bug#1022149: ktimetracker total data loss

[David Jarvie]

This looks of it could be the same issue as bug 1021938, which is due to a 
regression in libical version 3.0.15.
--
David Jarvie
KAlarm author, KDE developer

Bug#1022025: two reverts required, submitted to stable review list

[Doublychargedhiggs]

Confirmed, the two patches work for me too (AMD Ryzen Embedded V1605B with 
Radeon Vega Gfx). 
Kernel rebuilt and now boots like a charm and works without further issues. 
Thanks to all of you!!

Processed: limit source to linux, tagging 1022025

[Debian Bug Tracking System]

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

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 1022025 + pending
Bug #1022025 [src:linux] Can't enable amdgpu driver in 
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails 
to boot on machines with AMD integrated graphics
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Bug #1022070 [src:linux] Booting semi-hangs with 
'drm_atomic_helper_wait_for_flip_done' errors and alike
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.
-- 
1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025
1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042
1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051
1022070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems