Bug#1041621: kindleclip: indirectly depends on unmaintained GTK 2
Simon McVittie dijo [Fri, Jul 21, 2023 at 02:53:29PM +0100]: > Package: kindleclip > Version: 0.6-1.1 > Severity: important > Tags: trixie sid > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: gtk2 oldlibs > Control: block 967733 by -1 > X-Debbugs-Cc: ruby-gn...@packages.debian.org > > kindleclip seems to be the only package in unstable that depends on > ruby-gtk2, a GTK 2 binding for Ruby. > (...) Thank you very much, Simon! I am the upstream author for kindleclip, but don't use it anymore, and don't have the needed hardware to use it anymore. I have filed a removal request against the package, to help allow ruby-gtk2 to be removed.
Bug#1042872: command-not-found doesn't understand deb822 format in sources.list.d
Package: command-not-found Version: 23.04.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, I have my own repository of packages I've created myself, and I sign them with GPG. This means that Debian needs to have my public key, which I've installed in /etc/apt/keyrings/rjmx.pub. Current practice, according to sources.list(5), is to refer to this in /etc/apt/sources.d/.sources. In my case, .sources is "rjmx.sources". Here's its contents: Types: deb deb-src URIs: https://www.rjmx.net/Debian Suites: local Components: main Signed-By: /etc/apt/keyrings/rjmx.pub This works fine for installing packages, and apt/aptitude etc have no problem with it. However, if I mistype a program to run, I get this: - - $ noprog WARNING:root:could not open file '/etc/apt/sources.list.d/rjmx.sources': Unable to parse section data noprog: command not found - - Thus it looks like command-not-found doesn't understand the deb822 format for files in sources.list. .Ron - -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.7.khufu (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages command-not-found depends on: ii apt-file 3.3 ii lsb-release 12.0-2 ii python3 3.11.4-5 ii python3-apt 2.6.0 command-not-found recommends no packages. Versions of packages command-not-found suggests: pn snapd - -- no debconf information -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmTJ5K4OHHJqbXhAcmpt eC5uZXQACgkQEvfoZbXi52GACBAAp+GODecOE2VzoB/Lz0N1FIPNfTJWatbhFaEs FR8DwdlJhSOQLxGQT8ThaxvgrY/0TGx4clad1FQU1lb3BomlRukdapu/31/t7V9H 3KwVgaxP4qtOf1fnNljGVe9rSIe+nRTKP3kNJPkujGV7fKZ562D/yTIiZIPfnSHc uGHuEtJH5kaltL0Pj7tzdBROhXZq5PIfTLM6PqJpPuIJotOA9OxDteq+N//kNrmd 06l//cmzsf8wWq+HfHtt5aBagEo3vHeFSu8NfJwlTG5IeMMVtvV5Ep4xqC+eMcys SsWWGTfPC0aK8Q7jxTOpJEcWZTv3wyEMRmZElMbFsTauH9xf3SNWzE9r5SP3xUvX 6TGjEOBTiP+3nZ7qQD/Mc6oOqx+LCFlhHmkXpmcrwn96iA5qlP+DHPF3zlGLB+26 ZxZ3OOlbByF0RA/I8A+jH6tAxYFKTbIbOqA73SnlWfzFD0m+1jK7vx8WaaTDRPCz RouUHQYX/bla9cbJs4/yr/gE/x0++Y/4l9RahOolJ1+6idAdonrpzkjYfkjp8GYV a8hjHuxKlfbKKUvX+voAWZ2xHyHKiqbFtzzdqFB/xx1VBckbQqYiuKLz+dem70Op CC1473JNxSR+VlOjnZBfcDvp0kvN13aFbb1Z1ow6Os57WPivBV9z6te3MGAmKit3 0Q1GIY4= =xBqX -END PGP SIGNATURE-
Bug#1042873: RM: kindleclip -- ROM; Package orphaned upstream; depends on unmantained GTK 2
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: kindlec...@packages.debian.org Control: affects -1 + src:kindleclip I am the upstream author for kindleclip. I wrote it over 10 years ago, and it continues to work -- but I no longer have a Kindle device (and they have added features that are not properly supported). Kindleclip is built using ruby-gtk2, which depends on GTK2, which has long been obsolete and will be finally removed. Please drop kindleclip from the archive, so that ruby-gtk2 can also be removed. Thank you! signature.asc Description: PGP signature
Bug#1042871: transition: simdjson
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: simdj...@packages.debian.org Control: affects -1 + src:simdjson Hi release team, The simdjson upstream has bumped the ABI version along with their new release. Thus the transition request. It has only two reverse dependencies in testing. src:vast is not in testing. All reverse dependencies compiles against the new version. Reverse-Build-Depends = * pcm [ok] * vast [skipped. not in testing] Reverse-Build-Depends-Arch == * cloudflare-ddns [ok] The automatic transition tracker is correct. Thank you! Ben file: title = "simdjson"; is_affected = .depends ~ "libsimdjson14" | .depends ~ "libsimdjson16"; is_good = .depends ~ "libsimdjson16"; is_bad = .depends ~ "libsimdjson14"; Thank you for using reportbug
Bug#1042870: repackaging doesn't seem to be necessary anymore
Package: src:bpfcc Version: 0.28.0-1 At least in the upstream tarball 0.28.0, the files which you try to remove don't exist anymore. So no repackaging is needed.
Bug#1036051: working riscv64 patch
here is a working patch: https://patches.ubuntu.com/b/bpfcc/bpfcc_0.26.0+ds-1ubuntu2.patch need to exclude the tools dir as done for other architectures, both in debian/rules and debian/control
Bug#975550: Any progress on CFSSL
With the bug raised some time ago I am wondering if there is any drive to get the cfssl package updated. Version 1.2 is rather old and does not offer support to restrict TLS ciphers etc.
Bug#1004256: Default Hash: usesHtml2552279=EM_DWP_223146888=44191126_DEFAULT_HASH=1Fh3Sy4iCY3LZcyIAstAHRi66WYn1vGXiMdAGLiO1XSei Pkgs aI nter me diate1: ethereum/eip-review-b
ethereum/eip-review-bot@3e9905fcb72cf81ae9ed732df429c28b17e155b1
usesHtml2552279=EM_DWP_223146888=44191126_DEFAULT_HASH=1Fh3Sy4iCY3LZcyIAstAHRi66WYn1vGXiMdAGLiO1XSei
Pkgs aI nter me diate1:
ethereum/eip-review-bot@3e9905fcb72cf81ae9ed732df429c28b17e155b1
continue-on-error: truewith: token: ${{ secrets.TOKEN }}
config: config/eip-editors.yml pr_number: ${{
steps.save-pr-number.outputs.pr }}
Bug#1029283:
Hi, I have used the attached patch to get the autopkgtests to pass. Best Regards, Vladimir. pywebdav_0.10.0-1ubuntu1.debdiff Description: Binary data
Bug#1042869: sniffles: Please update to newer version without python3-pep517 requirement
Source: sniffles Version: 2.0.7-1 Severity: important Currently sniffles build-depends on python3-pep517. This package has been replaced upstream by python3-pyproject-hooks, which is now in Debian. As a result, python3-pep517 will be removed soon. There appears to be a newer version of sniffles that does not use python3-pep517 (I did not check if the current version acutally requires it of the the build-depend is unneeded). Please upgrade to the newer version or otherwise remove the build-depends on python3-pep517. Once I file the rm bug for it, I'll increase this to serious, so please address it now. Thanks, Scott K
Bug#956181: zlib: provide minizip binary packages
Bastian Germann wrote:
> Mark has stated on https://github.com/madler/zlib/issues/742 that
> he will not be working on this.
I am willing to volunteer as zlib co-maintainer focusing solely on
minizip so that Mark need do no work related to it.
> Mark, are you aware that this has a patch already?
I updated the minizip patch to apply to zlib 1.2.13 (from previously
1.2.11), attached below. What do you think?
Best wishes,
Mike
diff -Nru zlib-1.2.13.dfsg/debian/changelog zlib-1.2.13.dfsg/debian/changelog
--- zlib-1.2.13.dfsg/debian/changelog 2022-11-05 12:24:46.0 +
+++ zlib-1.2.13.dfsg/debian/changelog 2023-08-02 01:30:53.0 +
@@ -1,3 +1,9 @@
+zlib (1:1.2.13.dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Build minizip packages.
+
+ -- Michael Gilbert Wed, 02 Aug 2023 01:30:53 +
+
zlib (1:1.2.13.dfsg-1) unstable; urgency=low
* New upstream release.
diff -Nru zlib-1.2.13.dfsg/debian/control zlib-1.2.13.dfsg/debian/control
--- zlib-1.2.13.dfsg/debian/control 2022-11-05 12:24:46.0 +
+++ zlib-1.2.13.dfsg/debian/control 2023-08-02 01:30:53.0 +
@@ -4,7 +4,7 @@
Maintainer: Mark Brown
Standards-Version: 4.6.1
Homepage: http://zlib.net/
-Build-Depends: debhelper (>= 13), gcc-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 sparc s390x mipsn32 mipsn32el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64 mips64el mips64r6 mips64r6el x32] , dpkg-dev (>= 1.16.1)
+Build-Depends: debhelper (>= 13), gcc-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 sparc s390x mipsn32 mipsn32el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64 mips64el mips64r6 mips64r6el x32] , dpkg-dev (>= 1.16.1), autoconf
Package: zlib1g
Architecture: any
@@ -118,3 +118,50 @@
This package should ONLY be used for building packages, users who do
not need to build packages should use multiarch to install the relevant
runtime.
+
+Package: minizip
+Section: utils
+Architecture: any
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+Replaces:
+ zlib-bin,
+Conflicts:
+ zlib-bin,
+Description: compression library - minizip tools
+ minizip is a minimalistic library that supports compressing, extracting,
+ viewing, and manipulating zip files.
+ .
+ This package includes the minizip and miniunzip tools.
+
+Package: libminizip1
+Architecture: any
+Multi-Arch: same
+Pre-Depends:
+ ${misc:Pre-Depends}
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+Description: compression library - minizip library
+ minizip is a minimalistic library that supports compressing, extracting,
+ viewing, and manipulating zip files.
+ .
+ This package includes the minizip library.
+
+Package: libminizip-dev
+Architecture: any
+Multi-Arch: same
+Section: libdevel
+Depends:
+ ${misc:Depends},
+ libminizip1 (= ${binary:Version})
+Replaces:
+ libkml-dev (<< 1.3.0~r864+git20150723-0fa2f22-1~),
+Breaks:
+ libkml-dev (<< 1.3.0~r864+git20150723-0fa2f22-1~),
+Description: compression library - minizip development files
+ minizip is a minimalistic library that supports compressing, extracting,
+ viewing, and manipulating zip files.
+ .
+ This package includes development support files for the minizip library.
diff -Nru zlib-1.2.13.dfsg/debian/libminizip-dev.install zlib-1.2.13.dfsg/debian/libminizip-dev.install
--- zlib-1.2.13.dfsg/debian/libminizip-dev.install 1970-01-01 00:00:00.0 +
+++ zlib-1.2.13.dfsg/debian/libminizip-dev.install 2023-08-02 01:29:43.0 +
@@ -0,0 +1,4 @@
+usr/include/minizip
+usr/lib/*/libminizip.a
+usr/lib/*/libminizip.so
+usr/lib/*/pkgconfig/minizip.pc
diff -Nru zlib-1.2.13.dfsg/debian/libminizip1.install zlib-1.2.13.dfsg/debian/libminizip1.install
--- zlib-1.2.13.dfsg/debian/libminizip1.install 1970-01-01 00:00:00.0 +
+++ zlib-1.2.13.dfsg/debian/libminizip1.install 2023-08-02 01:29:43.0 +
@@ -0,0 +1 @@
+usr/lib/*/libminizip.so.*
diff -Nru zlib-1.2.13.dfsg/debian/libminizip1.symbols zlib-1.2.13.dfsg/debian/libminizip1.symbols
--- zlib-1.2.13.dfsg/debian/libminizip1.symbols 1970-01-01 00:00:00.0 +
+++ zlib-1.2.13.dfsg/debian/libminizip1.symbols 2023-08-02 01:30:53.0 +
@@ -0,0 +1,62 @@
+libminizip.so.1 libminizip1
+ call_zopen64@Base 1.1
+ call_zseek64@Base 1.1
+ call_ztell64@Base 1.1
+ fill_fopen64_filefunc@Base 1.1
+ fill_fopen_filefunc@Base 1.1
+ fill_zlib_filefunc64_32_def_from_filefunc32@Base 1.1
+ unzClose@Base 1.1
+ unzCloseCurrentFile@Base 1.1
+ unzGetCurrentFileInfo64@Base 1.1
+ unzGetCurrentFileInfo@Base 1.1
+ unzGetCurrentFileZStreamPos64@Base 1.1
+ unzGetFilePos64@Base 1.1
+ unzGetFilePos@Base 1.1
+ unzGetGlobalComment@Base 1.1
+ unzGetGlobalInfo64@Base 1.1
+ unzGetGlobalInfo@Base 1.1
+ unzGetLocalExtrafield@Base 1.1
+ unzGetOffset64@Base 1.1
+ unzGetOffset@Base 1.1
+ unzGoToFilePos64@Base 1.1
+ unzGoToFilePos@Base 1.1
+ unzGoToFirstFile@Base 1.1
+ unzGoToNextFile@Base 1.1
+ unzLocateFile@Base 1.1
+ unzOpen2@Base 1.1
+ unzOpen2_64@Base 1.1
+ unzOpen64@Base 1.1
+ unzOpen@Base 1.1
+
Bug#1042868: kde-plasma-desktop: KDE Lockscreen Wakes Monitor up After It Is Turned Off via Escape Button and kscreen-doctor
Package: kde-plasma-desktop Version: 5:142 Severity: normal X-Debbugs-Cc: place4...@gmail.com Dear Maintainer, When the screen is locked, either via timeout or shortcut, I am unable to turn off the monitor. Seconds after pressing Escape, the lockscreen turns the monitor back on. I also tried to run a command that listens to the lock screen event, ``` kscreen-doctor -d off ``` but this too, cannot prevent the monitor from waking itself after it is turned off. Related posts: https://bugs.kde.org/show_bug.cgi?id=422455 https://bugs.kde.org/show_bug.cgi?id=462695 After reading the above posts, I think the problem might lie in the package `kidletime`, since this patch claims to fix the problem: https://bugs.kde.org/show_bug.cgi?id=462695#c40 https://src.fedoraproject.org/rpms/kf5-kidletime/c/2a096ad8d7e9ab9a838156021991d86e76971117?branch=rawhide -- System Information: Wayland session, Debian Bookworm, everything is up to date. Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kde-plasma-desktop depends on: ii kde-baseapps 4:22.12.3+5.142 ii plasma-desktop4:5.27.5-2 ii plasma-workspace 4:5.27.5-2 ii udisks2 2.9.4-4 ii upower0.99.20-2 Versions of packages kde-plasma-desktop recommends: ii kwin-x11 4:5.27.5-3 ii sddm 0.19.0-5 ii xserver-xorg 1:7.7+23 Versions of packages kde-plasma-desktop suggests: ii kdeconnect 22.12.3-1 -- no debconf information
Bug#1042867: debmirror: add option to URL-encode paths when fetching packages using http to support repos in AWS S3
Package: debmirror
Severity: normal
Dear Maintainer,
When using debmirror to mirror from a package repository hosted in an AWS
S3 bucket debmirror fails to fetch files containing characters that have a
plus sign ("+") as AWS S3 expects such fetches to use a URL-encoded path,
but debmirror does not do any URL-encoding.
Please add a command-line option that turns on URL-encoding when fetching
packages using http or https.
-- System Information:
Debian Release: 11.6
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-21-amd64 (SMP w/1 CPU thread)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages debmirror depends on:
ii bzip21.0.8-4
pn libdigest-md5-perl
pn libdigest-sha-perl
pn liblockfile-simple-perl
ii libwww-perl 6.52-1
ii perl [libnet-perl] 5.32.1-4+deb11u2
ii rsync3.2.3-4+deb11u1
ii xz-utils 5.2.5-2.1~deb11u1
Versions of packages debmirror recommends:
ii ed 1.17-1
ii gpgv 2.2.27-2+deb11u2
ii patch 2.7.6-7
Versions of packages debmirror suggests:
ii gnupg 2.2.27-2+deb11u2
Bug#1042856: man-db: man does not show any pages
>On Tue, Aug 01, 2023 at 11:15:22PM +0200, Francesco Potortì wrote:
>> man gives an error on any man page. For example:
>>
>> $ man -P cat wget
>> man: command exited with status 1: (cd /usr/share/man &&
>> /usr/libexec/man-db/zsoelim) | (cd /usr/share/man &&
>> /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd
>> /usr/share/man && preconv -e UTF-8) | (cd /usr/share/man && tbl) | (cd
>> /usr/share/man && nroff -mandoc -rLL=102n -rLT=102n -Tutf8)
>
>Can I have the output of "PIPELINE_DEBUG=1 man -P cat wget >/dev/null"
>to narrow things down a bit, please?
Here you are:
$ PIPELINE_DEBUG=1 man -P cat wget >/dev/null
Starting pipeline: zcat [input: {0, /usr/share/man/man1/wget.1.gz}, output:
{-1, NULL}]
Started "zcat", pid 3936106
Starting pipeline: (cd /usr/share/man && /usr/libexec/man-db/zsoelim) | (cd
/usr/share/man && /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t
UTF-8//IGNORE) | (cd /usr/share/man && preconv -e UTF-8) | (cd /usr/share/man
&& tbl) | (cd /usr/share/man && nroff -mandoc -rLL=102n -rLT=102n -Tutf8)
[input: {-1, NULL}, output: {-1, NULL}]
Started "/usr/libexec/man-db/zsoelim", pid 3936107
Started "/usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE", pid
3936108
Started "preconv", pid 3936109
Started "tbl", pid 3936110
Started "nroff", pid 3936111
Starting pipeline: col -b -p -x | sed -e '/^[[:space:]]*$/{ N;
/^[[:space:]]*\n[[:space:]]*$/D; }' [input: {-1, NULL}, output: {0, NULL}]
Started "col", pid 3936112
Started "sed -e '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'", pid
3936113
source pipeline 0 returned error or EOF
Starting pipeline: Starting pipeline: zcatzcat [input: {3, NULL}, output: {-1,
NULL}]
[input: {3, NULL}, output: {-1, NULL}]
Started "zcat", pid 3936114
Started "zcat", pid 3936115
Waiting for pipeline: zcat [input: {3, NULL}, output: {-1, NULL}]
Active processes (1):
"zcat" (3936115) -> -1
Active processes (1):
"zcat" (3936115) -> 0
Waiting for pipeline: zcat [input: {3, NULL}, output: {-1, NULL}]
Active processes (1):
"zcat" (3936114) -> -1
Active processes (1):
"zcat" (3936114) -> 0
troff: fatal error: cannot load 'DESC' description file for device 'utf8'
source pipeline 1 returned error or EOF
Waiting for pipeline: zcat [input: {0, /usr/share/man/man1/wget.1.gz}, output:
{-1, NULL}]
Active processes (1):
"zcat" (3936106) -> 0
Waiting for pipeline: (cd /usr/share/man && /usr/libexec/man-db/zsoelim) | (cd
/usr/share/man && /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t
UTF-8//IGNORE) | (cd /usr/share/man && preconv -e UTF-8) | (cd /usr/share/man
&& tbl) | (cd /usr/share/man && nroff -mandoc -rLL=102n -rLT=102n -Tutf8)
[input: {-1, NULL}, output: {-1, NULL}]
Active processes (5):
"/usr/libexec/man-db/zsoelim" (3936107) -> 0
"/usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE" (3936108)
-> 0
"preconv" (3936109) -> 0
"tbl" (3936110) -> -1
"nroff" (3936111) -> 256
Active processes (1):
"tbl" (3936110) -> -1
Active processes (1):
"tbl" (3936110) -> 13
Waiting for pipeline: col -b -p -x | sed -e '/^[[:space:]]*$/{ N;
/^[[:space:]]*\n[[:space:]]*$/D; }' [input: {-1, NULL}, output: {0, NULL}]
Active processes (2):
"col" (3936112) -> 0
"sed -e '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'" (3936113)
-> -1
Active processes (1):
"sed -e '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'" (3936113)
-> 0
man: command exited with status 1: (cd /usr/share/man &&
/usr/libexec/man-db/zsoelim) | (cd /usr/share/man &&
/usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd
/usr/share/man && preconv -e UTF-8) | (cd /usr/share/man && tbl) | (cd
/usr/share/man && nroff -mandoc -rLL=102n -rLT=102n -Tutf8)
--
Francesco Potortì (ricercatore)Mobile: +39.348.8283.107
ISTI - Area della ricerca CNR Skype: wnlabisti
via G. Moruzzi 1, I-56124 Pisa Web:http://fly.isti.cnr.it
(gate 20, 1st floor, room C71) ISPIN: https://ieee-jispin.org/
Bug#1030129: (no subject)
Can this bug be backported to stable?
Bug#1042856: man-db: man does not show any pages
On Tue, Aug 01, 2023 at 11:15:22PM +0200, Francesco Potortì wrote: > man gives an error on any man page. For example: > > $ man -P cat wget > man: command exited with status 1: (cd /usr/share/man && > /usr/libexec/man-db/zsoelim) | (cd /usr/share/man && > /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd > /usr/share/man && preconv -e UTF-8) | (cd /usr/share/man && tbl) | (cd > /usr/share/man && nroff -mandoc -rLL=102n -rLT=102n -Tutf8) Can I have the output of "PIPELINE_DEBUG=1 man -P cat wget >/dev/null" to narrow things down a bit, please? -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#1042753: nouveau: Screen remains black.
On Wednesday, 2 August 2023 00:23:16 CEST Olaf Skibbe wrote: > Finally I managed to compile the kernel via > > debian/bin/test-patches > ../0001-Revert-drm-nouveau-add-nv_encoder-pointer-check-for-.patch > ../0002-Revert-drm-nouveau-dp-check-for-NULL-nv_connector-na.patch > ../0003-Revert-drm-nouveau-don-t-detect-DSM-for-non-NVIDIA-d.patch > ../0004-Revert-nouveau-fix-client-work-fence-deletion-race.patch > > (apparently successfully, but it took several hours). Awesome \o/ Depending on the speed of the machine, it can indeed take several hours. > But now I am a little clueless: how do I install this kernel? Any hint? It should have produced one or more .deb files and you can install a .deb file like this: `apt install ./.deb` If you share the output of `ls -lh *.deb` (and/or `ls -lh ../*.deb`) then I can probably give you more precise instructions. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1042866: planner: Frequent segmentation faults
Package: planner Version: 0.14.91-2 Severity: important Dear Maintainer, (This seems to be a different segfault from #928029) planner seems to segfault randomly at different times after being used for a few seconds to a few minutes. This is one I managed to reproduce when trying to remove a resource I'd just added (it was an accident, I didn't mean to hit the delete icon but the one next to it to add another resource). However, I've seen others I haven't been able to reproduce reliably. To reproduce: -- start planner -- Select 'Resources' -- Add a resource, and insert its name -- hit the 'delete resource' icon Thread 1 "planner" received signal SIGSEGV, Segmentation fault. (gdb) bt #0 0x in () #1 0x77de93d8 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x77dfc407 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x77e02c97 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x77fa9a67 in mrp_project_remove_resource (project=0x557971d0, resource=0x55be4580) at ../libplanner/mrp-project.c:1414 #6 0x555775fe in resource_cmd_remove_do (cmd_base=0x55ad0b40) at ../src/planner-resource-view.c:861 #7 0x55585290 in cmd_manager_insert (manager=0x556d8b20, cmd=cmd@entry=0x55ad0b40, run_do=run_do@entry=1) at ../src/planner-cmd-manager.c:353 #8 0x5558536d in planner_cmd_manager_insert_and_do (manager=, cmd=cmd@entry=0x55ad0b40) at ../src/planner-cmd-manager.c:371 #9 0x55579ac1 in resource_cmd_remove (resource=0x55be4580, view=0x557ef680) at ../src/planner-resource-view.c:920 #10 resource_view_remove_resource_cb (action=, data=0x557ef680) at ../src/planner-resource-view.c:938 #11 0x77de93d8 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x77dfbede in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x77e02c97 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x77789b40 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #16 0x776f2e69 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #18 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x774d8650 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x774d68f0 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #25 0x77495a09 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #26 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #28 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #29 0x775adb06 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x77dec412 in g_cclosure_marshal_VOID__BOXEDv () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #31 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #32 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #33 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #34 0x775aabf3 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #35 0x775ac1f3 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #36 0x775af362 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #37 0x7757489d in gtk_event_controller_handle_event () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #38 0x7773d48d in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #39 0x7748f8c4 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #40 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #41 0x77e02392 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #42 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #43 0x7773eeb4 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #44 0x775f616e in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #45 0x775f7cee in gtk_main_do_event () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #46 0x77d08365 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 #47 0x77d5be72 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 #48 0x77e8c5e5 in
Bug#1042865: planner: Help user guide is missing from Debian package
Package: planner Version: 0.14.91-2 Severity: normal Dear Maintainer, After installing planner and planner-doc I expect that the 'Help' menu item 'User Guide' will pop up the user guide. Instead I get a 'File not found' page. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armhf, i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages planner depends on: ii gir1.2-gtk-2.0 2.24.33-2 ii libatk1.0-0 2.48.3-1 ii libc62.37-6 ii libcairo-gobject21.16.0-7 ii libcairo21.16.0-7 ii libgail-3-0 3.24.38-2 ii libgda-5.0-4 5.2.10-3 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.76.4-4 ii libgtk-3-0 3.24.38-2 ii libpango-1.0-0 1.50.14+ds-1 ii libpangocairo-1.0-0 1.50.14+ds-1 ii libxml2 2.9.14+dfsg-1.3 ii libxslt1.1 1.1.35-1 ii planner-data 0.14.91-2 ii python3-gi 3.44.1-2 ii shared-mime-info 2.2-1 Versions of packages planner recommends: ii planner-doc 0.14.91-2 planner suggests no packages. -- no debconf information --1690763229-eximdsn-1755513534--
Bug#1042709: qt6-base FTCBFS: doesn't build sqlbrowser
tag 1042709 pending thanks On Sun, 30 Jul 2023 at 16:43, Helmut Grohne wrote: > > Source: qt6-base > Version: 6.4.2+dfsg-17 > Tags: patch > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > > Hi, > > qt6-base fails to cross build again. This time, it misses building > sqlbrowser. While fixing it, I noticed that the variable we are passing > is deprecated and also update it. I'm attaching a patch for your > convenience. Thanks a lot for it! I just applied it to our master branch. I plan to push this as soon as the current version in unstable migrates to testing. > Should we also > s/QT_BUILD_TOOLS_WHEN_CROSSCOMPILING/QT_FORCE_BUILD_TOOLS/ across the > rest of the qt6 packaging? We should, although I think there are a handful of packages out of the whole 30 something submodules. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/
Bug#1042852: liblexical-failure-perl: FTBFS with Perl 5.38: test failures
Control: clone -1 -2 Control: reassign -2 perl Control: retitle -2 "perl: add Breaks: liblexical-failure-perl (<< 0.001000) Control: tags -2 - fixed-upstream ftbfs On Tue, 01 Aug 2023 22:59:59 +0300, Niko Tyni wrote: > It seems to be fixed upstream in 0.001000 according to the Changes file, > though the upstream bug is still open. > It would probably be prudent to add a Breaks entry on the perl side just > in case, so please file a bug about that when this issue is fixed. 0.001001-1 works with 5.38, uploaded to sid, cloning the bug for the Breaks on the perl side. 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
Bug#1042854: libcss-dom-perl: FTBFS with Perl 5.38: Old package separator "'" deprecated
On Tue, 01 Aug 2023 23:21:03 +0300, Niko Tyni wrote: > Source: libcss-dom-perl > Version: 0.17-2 > Severity: important > Tags: ftbfs sid trixie patch > Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=146661 > User: debian-p...@lists.debian.org > Usertags: perl-5.38-transition > > This package fails to build from source with Perl 5.38 (currently in > experimental.) > > There's a patch by Yves Orton in the upstream ticket. Which is technically incomplete, I ask for the actual diff in the RT ticket. 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
Bug#1042863: gnome-software: GNOME software broken icons in Debian 12 live image ( bookworm )
Package: gnome-software Version: 43.5-1 Severity: important X-Debbugs-Cc: sidto...@gmail.com Dear Maintainer, Boot Debian 12 live image and click "Software" app from the dock. Apps in the top carousel will have broken icon. Please refer to the following upstream issue for more information on the issue and the commits that fix the problem. https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2197 The broken icon is seen in: - debian-live-12.0.0-amd64-gnome - debian-live-12.1.0-amd64-gnome Thanks! -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-software depends on: ii appstream0.16.2-1 ii apt-config-icons 0.16.2-1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gnome-software-common43.5-1 ii gsettings-desktop-schemas44.0-2 ii libadwaita-1-0 1.3.3-2 ii libappstream40.16.2-1 ii libc62.37-6 ii libcairo21.16.0-7 ii libfwupd21.9.3-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.76.4-3 ii libgtk-4-1 4.10.4+ds-2 ii libgtk3-perl 0.038-3 ii libgudev-1.0-0 237-2 ii libjson-glib-1.0-0 1.6.6-1 ii libmalcontent-0-00.11.0-4 ii libpackagekit-glib2-18 1.2.6-5 ii libpango-1.0-0 1.50.14+ds-1 ii libpolkit-gobject-1-0122-4 ii libsoup-3.0-03.2.2-2 ii libxmlb2 0.3.10-2 ii packagekit 1.2.6-5 ii software-properties-gtk 0.99.30-4 Versions of packages gnome-software recommends: ii fwupd 1.9.3-1 Versions of packages gnome-software suggests: pn apt-config-icons-hidpi pn gnome-software-plugin-flatpak pn gnome-software-plugin-snap -- no debconf information
Bug#1042862: Xspice crashes on start
Package: xserver-xspice Version: 0.1.6-1 Severity: grave Justification: renders package unusable See #1038648. As I wrote there, 0.1.6-1 doesn't fix the problem, but this was ignored, so I'm sending a new bug report. The buggy patch is now upstream, but that doesn't make it correct. I've already explained how to fix it correctly.
Bug#1042753: nouveau: Screen remains black.
Finally I managed to compile the kernel via debian/bin/test-patches ../0001-Revert-drm-nouveau-add-nv_encoder-pointer-check-for-.patch ../0002-Revert-drm-nouveau-dp-check-for-NULL-nv_connector-na.patch ../0003-Revert-drm-nouveau-don-t-detect-DSM-for-non-NVIDIA-d.patch ../0004-Revert-nouveau-fix-client-work-fence-deletion-race.patch (apparently successfully, but it took several hours). But now I am a little clueless: how do I install this kernel? Any hint? Cheers, Olaf On Mon, 31 Jul 2023 at 22:42, Diederik de Haas wrote: On Monday, 31 July 2023 21:52:44 CEST Olaf Skibbe wrote: Yep, now we know it's a regression between 6.1.27-1 and 6.1.38-2. https://wiki.debian.org/DebianKernel/GitBisect describes the best way as it would identify the exact (upstream) commit which introduced the problem. If you can do that, great. I'd love to contribute here, but I am afraid this would be a bit beyond my capabilities. I now have only remote access to the computer in question (I have to ask somebody to verify whether the display is working) and I am not very experienced. Sorry. That's ok, I (kind of) expected that a `git bisect` would be too difficult. That's why I also described a simpler procedure which is specifically meant for people who aren't experienced. It will result in a new kernel being build, but all the complexity should be hidden for you. It probably sounds daunting/scary, but it shouldn't be. There is a subsequent step, but that is (far) more likely to succeed if we'd have more detailed data which the above procedure would provide. So it would be great if you could try it. If it turns out to be too difficult, don't worry about it :-) Cheers, Diederik
Bug#1042861: ITP: git-credential-azure -- A Git credential helper for Azure Repos
Package: wnpp Severity: wishlist Owner: M Hickford X-Debbugs-Cc: debian-de...@lists.debian.org, mirth.hickf...@gmail.com * Package name: git-credential-azure Version : 0.1.0 * URL : https://github.com/hickford/git-credential-azure * License : Apache2 Programming Lang: Go Description : A Git credential helper for Azure Repos git-credential-azure is a Git credential helper that authenticates to Azure Repos (dev.azure.com). Azure Repos is part of Azure DevOps.
Bug#1042527: [request-tracker-maintainers] Bug#1042527: request-tracker5: Include ckeditor minimified
tags 1042527 -ftbfs Hello Bastien Upstream does provide only a minified javascript in their release tarball, but Debian package includes the source of the ckeditor used within the third-party tarball http://deb.debian.org/debian/pool/main/r/request-tracker5/request-tracker5_5.0.3+dfsg.orig-third-party-source.tar.gz and minifies that source during the build process with the debian/build-final-ckeditor.sh script. There is more information on the history of this tarball on the bug with upstream https://rt.bestpractical.com/Ticket/Display.html?id=37009 Regards
Bug#1042860: firefox-esr: endlessly loops opening tabs for atom files when about:preferences has "Atom syndication feed" open in firefox
Package: firefox-esr Version: 102.13.0esr-1~deb11u1 Severity: normal X-Debbugs-Cc: echar...@vtluug.org Dear Maintainer, When attemting to open atom feeds (which firefox no longer can read, despite them being xml), the download prompt suggests opening the file in firefox. If you leave the box checked for "always open files of this type", firefox will open tabs endlessly, making it unusable, until you kill the application or delete the atom file. It does not result in excess memory usage, although it will pin firefox-esr cpu usage, thus the system will never recover itself, despite it appearing to be a fork bomb. This prompt changes the setting under about:preferences>Applications, s.t. "Atom Syndication feed" says "Use firefox web browser (Default)". As a mitigation, I have changed it to "save file". this prevents firefox from locking up or prompting the user to open the file in firefox. Ideally firefox would open atom and rss files as plain text and render them; I don't know why this is not the behaviour. But firefox should stop suggesting itself as the way to open atom files if it will do this. I suspect this is an upstream bug, but I don't have the resources to validate that at the moment. Apologies if this is a duplicate report. Thanks, echarlie -- Package-specific info: -- Addons package information -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-23-amd64 (SMP w/12 CPU threads) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox-esr depends on: ii debianutils 4.11.2 ii fontconfig 2.13.1-4.2 ii libasound2 1.2.4-1.1 ii libatk1.0-0 2.36.0-2 ii libc62.31-13+deb11u6 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.24-0+deb11u1 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libffi7 3.3-6 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1+deb11u1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1+deb11u1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4+deb11u3 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-1 ii libx11-6 2:1.7.2-1+deb11u1 ii libx11-xcb1 2:1.7.2-1+deb11u1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxrandr2 2:1.5.1-1 ii libxtst6 2:1.2.3-1 ii procps 2:3.3.17-5 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 Versions of packages firefox-esr recommends: ii libavcodec-extra58 [libavcodec58] 7:4.3.6-0+deb11u1 Versions of packages firefox-esr suggests: ii fonts-lmodern 2.004.5-6.1 ii fonts-stix [otf-stix] 1.1.1-4.1 ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.18.3-6+deb11u3 ii pulseaudio 14.2-2 -- no debconf information
Bug#1042842: network interface names wrong in domU (>10 interfaces)
Hello, the bug has been mentionned on #xen-devel, will keep you posted. Meanwhile, you may try to force the domU vif names with a letter, like : vif = [ 'mac=00:16:3e:fd:83:2f,bridge=lanbr,vifname=domu-a', 'mac=00:16:3e:fd:83:30,bridge=lanbr,vifname=domu-b', 'mac=00:16:3e:fd:83:31,bridge=lanbr,vifname=domu-c', ... ] Note it's just a workaround, and I've not tested it. I only guess letters would be sorted correctly. If you test this, can you report back please ? -- zithro / Cyril
Bug#1042859: cargo: Please upgrade to at least 0.67.0
Package: cargo Version: 0.66.0+ds1-1 Severity: normal 0.66 is the version of cargo that goes alongside rustc 1.65. 0.67 is the version of cargo that goes alongside rustc 1.66. Unstable and testing have rustc 1.66, so cargo should be updated to at least version 0.67. Mike
Bug#1042855: openjdk-8: Please consider using libjpeg-dev virtual package as dependency
Vladimir Petko dixit: >openjdk-8 382-ga-1 uses libjpeg-turbo62 as a dependency rather than >libjpeg-dev that it used before. No, for Ubuntu it uses libjpeg-turbo8-dev, so why… >The attached patch updates control and rules to select libjpeg-dev as a >dependency allowing Ubuntu sync. … oh, right, you don’t regenerate debian/control when you do a sync. >The attached patch was applied to achieve the following: > > * Use libjpeg-dev virtual package to solve dependency-wait (LP: >#2028973). No, virtual packages cannot be used as build dependencies, that violates Policy. Would be this okay for you: --- a/debian/rules +++ b/debian/rules @@ -689,7 +689,7 @@ ifeq ($(derivative),Ubuntu) else ifneq (,$(filter $(distrel),wheezy)) bd_syslibs += libjpeg8-dev, else - bd_syslibs += libjpeg62-turbo-dev, + bd_syslibs += libjpeg62-turbo-dev | libjpeg-dev, endif bd_syslibs += \ libgif-dev, This will be valid in Debian (virtual package *is* allowed as second alternative, because buildds only use the first) and works iff Ubuntu buildd also use the second alternative. bye, //mirabilos -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a clean repo │ fault (core dumped) if I rebase that now, it's really ugh │ wuahh
Bug#1042858: promod3: unable to install on arm64
Package: promod3 Version: 3.3.1+ds-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org $ apt-get install promod3 Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: promod3 : Depends: python3-ost but it is not installable Depends: python3-promod3 but it is not installable E: Unable to correct problems, you have held broken packages. Cheers -- Sebastian Ramacher
Bug#1042857: coinor-libcbc3.1: Fails to install, conflicts with coinor-libcbc3:amd64
Package: coinor-libcbc3.1 Version: 2.10.10+really2.10.10+ds1-2 Severity: serious Justification: Fails to install Hello, While upgrading testing today: Preparing to unpack .../coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb ... Unpacking coinor-libcbc3.1:amd64 (2.10.10+really2.10.10+ds1-2) ... dpkg: error processing archive /var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libCbc.so.3.10.10', which is also in package coinor-libcbc3:amd64 2.10.10+ds1-1 Errors were encountered while processing: /var/cache/apt/archives/coinor-libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb needrestart is being skipped since dpkg has failed I guess there should be some breaks+replace or some renaming? Samuel -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages coinor-libcbc3.1 depends on: ii coinor-libcgl1 0.60.3+repack1-4 ii coinor-libclp1 1.17.6-3 ii coinor-libcoinutils3v5 2.11.4+repack1-2 ii coinor-libosi1v50.108.6+repack1-2 ii libc6 2.37-6 ii libgcc-s1 13.1.0-6 ii libstdc++6 13.1.0-6 coinor-libcbc3.1 recommends no packages. coinor-libcbc3.1 suggests no packages.
Bug#1041076: dolphin-emu: diff for NMU version 5.0-19368+dfsg-2.1
Control: tags 1041076 + patch
Control: tags 1041076 + pending
Dear maintainer,
I've prepared an NMU for dolphin-emu (versioned as 5.0-19368+dfsg-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru dolphin-emu-5.0-19368+dfsg/debian/changelog dolphin-emu-5.0-19368+dfsg/debian/changelog
--- dolphin-emu-5.0-19368+dfsg/debian/changelog 2023-06-15 11:40:41.0 +0200
+++ dolphin-emu-5.0-19368+dfsg/debian/changelog 2023-08-01 22:59:04.0 +0200
@@ -1,3 +1,11 @@
+dolphin-emu (5.0-19368+dfsg-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Apply upstream patch to fix FTBFS with imgui 1.89.6
+(Closes: #1041076)
+
+ -- Sebastian Ramacher Tue, 01 Aug 2023 22:59:04 +0200
+
dolphin-emu (5.0-19368+dfsg-2) unstable; urgency=medium
* Update DOLPHIN_WC_DESCRIBE and DOLPHIN_WC_REVISION. *facepalm*
diff -Nru dolphin-emu-5.0-19368+dfsg/debian/patches/imgui_1.89.6.diff dolphin-emu-5.0-19368+dfsg/debian/patches/imgui_1.89.6.diff
--- dolphin-emu-5.0-19368+dfsg/debian/patches/imgui_1.89.6.diff 1970-01-01 01:00:00.0 +0100
+++ dolphin-emu-5.0-19368+dfsg/debian/patches/imgui_1.89.6.diff 2023-08-01 22:58:32.0 +0200
@@ -0,0 +1,98 @@
+--- a/Externals/implot/implot/implot.cpp
b/Externals/implot/implot/implot.cpp
+@@ -122,6 +122,7 @@
+
+ */
+
++#define IMGUI_DEFINE_MATH_OPERATORS
+ #include "implot.h"
+ #include "implot_internal.h"
+
+--- a/Externals/implot/implot/implot_internal.h
b/Externals/implot/implot/implot_internal.h
+@@ -31,10 +31,6 @@
+
+ #pragma once
+
+-#ifndef IMGUI_DEFINE_MATH_OPERATORS
+-#define IMGUI_DEFINE_MATH_OPERATORS
+-#endif
+-
+ #include
+ #include "imgui_internal.h"
+
+--- a/Externals/implot/implot/implot_items.cpp
b/Externals/implot/implot/implot_items.cpp
+@@ -22,6 +22,7 @@
+
+ // ImPlot v0.14
+
++#define IMGUI_DEFINE_MATH_OPERATORS
+ #include "implot.h"
+ #include "implot_internal.h"
+
+--- a/Source/Core/VideoCommon/OnScreenUI.cpp
b/Source/Core/VideoCommon/OnScreenUI.cpp
+@@ -349,35 +349,37 @@
+ }
+ void OnScreenUI::SetKeyMap(const DolphinKeyMap& key_map)
+ {
+- // Right now this is a 1:1 mapping. But might not be true later
+ static constexpr DolphinKeyMap dolphin_to_imgui_map = {
+ ImGuiKey_Tab, ImGuiKey_LeftArrow, ImGuiKey_RightArrow, ImGuiKey_UpArrow,
+ ImGuiKey_DownArrow, ImGuiKey_PageUp,ImGuiKey_PageDown, ImGuiKey_Home,
+ ImGuiKey_End, ImGuiKey_Insert,ImGuiKey_Delete, ImGuiKey_Backspace,
+- ImGuiKey_Space, ImGuiKey_Enter, ImGuiKey_Escape, ImGuiKey_KeyPadEnter,
++ ImGuiKey_Space, ImGuiKey_Enter, ImGuiKey_Escape, ImGuiKey_KeypadEnter,
+ ImGuiKey_A, ImGuiKey_C, ImGuiKey_V, ImGuiKey_X,
+ ImGuiKey_Y, ImGuiKey_Z,
+ };
+- static_assert(dolphin_to_imgui_map.size() == ImGuiKey_COUNT); // Fail if ImGui adds keys
+
+ auto lock = GetImGuiLock();
+
+ if (!ImGui::GetCurrentContext())
+ return;
+
++ m_dolphin_to_imgui_map.clear();
+ for (int dolphin_key = 0; dolphin_key <= static_cast(DolphinKey::Z); dolphin_key++)
+ {
+-int imgui_key = dolphin_to_imgui_map[DolphinKey(dolphin_key)];
++const int imgui_key = dolphin_to_imgui_map[DolphinKey(dolphin_key)];
+ if (imgui_key >= 0)
+- ImGui::GetIO().KeyMap[imgui_key] = (key_map[DolphinKey(dolphin_key)] & 0x1FF);
++{
++ const int mapped_key = key_map[DolphinKey(dolphin_key)];
++ m_dolphin_to_imgui_map[mapped_key & 0x1FF] = imgui_key;
++}
+ }
+ }
+
+ void OnScreenUI::SetKey(u32 key, bool is_down, const char* chars)
+ {
+ auto lock = GetImGuiLock();
+- if (key < std::size(ImGui::GetIO().KeysDown))
+-ImGui::GetIO().KeysDown[key] = is_down;
++ if (auto iter = m_dolphin_to_imgui_map.find(key); iter != m_dolphin_to_imgui_map.end())
++ImGui::GetIO().AddKeyEvent((ImGuiKey)iter->second, is_down);
+
+ if (chars)
+ ImGui::GetIO().AddInputCharactersUTF8(chars);
+--- a/Source/Core/VideoCommon/OnScreenUI.h
b/Source/Core/VideoCommon/OnScreenUI.h
+@@ -3,6 +3,7 @@
+
+ #pragma once
+
++#include
+ #include
+ #include
+ #include
+@@ -65,6 +66,7 @@
+ std::unique_ptr m_imgui_vertex_format;
+ std::vector> m_imgui_textures;
+ std::unique_ptr m_imgui_pipeline;
++ std::map m_dolphin_to_imgui_map;
+ std::mutex m_imgui_mutex;
+ u64 m_imgui_last_frame_time = 0;
+
diff -Nru dolphin-emu-5.0-19368+dfsg/debian/patches/series dolphin-emu-5.0-19368+dfsg/debian/patches/series
--- dolphin-emu-5.0-19368+dfsg/debian/patches/series 2023-06-14 14:26:33.0 +0200
+++ dolphin-emu-5.0-19368+dfsg/debian/patches/series 2023-08-01 22:58:26.0 +0200
@@ -5,3 +5,4 @@
gtest.patch
implot.patch
mgba_videosize.patch
+imgui_1.89.6.diff
Bug#1042856: man-db: man does not show any pages
Package: man-db Version: 2.11.2-3 Severity: important X-Debbugs-Cc: none, Francesco Potortì man gives an error on any man page. For example: $ man -P cat wget man: command exited with status 1: (cd /usr/share/man && /usr/libexec/man-db/zsoelim) | (cd /usr/share/man && /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd /usr/share/man && preconv -e UTF-8) | (cd /usr/share/man && tbl) | (cd /usr/share/man && nroff -mandoc -rLL=102n -rLT=102n -Tutf8) $ man -d -P cat wget ruid=1000, euid=1000 rgid=1000, egid=1000 >From the config file /etc/manpath.config: Mandatory mandir `/usr/man'. Mandatory mandir `/usr/share/man'. Mandatory mandir `/usr/local/share/man'. Path `/bin' mapped to mandir `/usr/share/man'. Path `/usr/bin' mapped to mandir `/usr/share/man'. Path `/sbin' mapped to mandir `/usr/share/man'. Path `/usr/sbin' mapped to mandir `/usr/share/man'. Path `/usr/local/bin' mapped to mandir `/usr/local/man'. Path `/usr/local/bin' mapped to mandir `/usr/local/share/man'. Path `/usr/local/sbin' mapped to mandir `/usr/local/man'. Path `/usr/local/sbin' mapped to mandir `/usr/local/share/man'. Path `/usr/X11R6/bin' mapped to mandir `/usr/X11R6/man'. Path `/usr/bin/X11' mapped to mandir `/usr/X11R6/man'. Path `/usr/games' mapped to mandir `/usr/share/man'. Path `/opt/bin' mapped to mandir `/opt/man'. Path `/opt/sbin' mapped to mandir `/opt/man'. Global mandir `/usr/man', catdir `/var/cache/man/fsstnd'. Global mandir `/usr/share/man', catdir `/var/cache/man'. Global mandir `/usr/local/man', catdir `/var/cache/man/oldlocal'. Global mandir `/usr/local/share/man', catdir `/var/cache/man/local'. Global mandir `/usr/X11R6/man', catdir `/var/cache/man/X11R6'. Global mandir `/opt/man', catdir `/var/cache/man/opt'. Global mandir `/snap/man', catdir `/var/cache/man/snap'. Added sections: `1', `n', `l', `8', `3', `0', `2', `3type', `3posix', `3pm', `3perl', `3am', `5', `4', `9', `6', `7'. is a tty using cat as pager path directory /home/pot/bin is not in the config file path directory /home/pot/.local/bin is not in the config file path directory /home/pot/bin is not in the config file path directory /home/pot/.local/bin is not in the config file path directory /usr/local/bin is in the config file adding /usr/local/man to manpath adding /usr/local/share/man to manpath path directory /usr/bin is in the config file adding /usr/share/man to manpath path directory /bin is in the config file path directory /usr/bin/X11 is in the config file warning: /usr/X11R6/man: No such file or directory path directory /snap/bin is not in the config file path directory /usr/games is in the config file adding mandatory man directories adding /usr/man to manpath add_nls_manpaths(): processing /usr/local/man:/usr/local/share/man:/usr/share/man:/usr/man checking for locale C.UTF-8 adding /usr/local/man to manpathlist adding /usr/share/man to manpathlist adding /usr/man to manpathlist final search path = /usr/local/man:/usr/share/man:/usr/man searching in /usr/local/man, section 1 trying section 1 with globbing Layout is GNU (1) update_directory_cache /usr/local/man: miss matching wildcard in /usr/local/man: man1* update_directory_cache /usr/local/man: hit matching wildcard in /usr/local/man: cat1* Failed to open /var/cache/man/oldlocal/index.db O_RDONLY searching in /usr/share/man, section 1 trying section 1 with globbing update_directory_cache /usr/share/man: miss matching wildcard in /usr/share/man: man1* matched: /usr/share/man/man1 update_directory_cache /usr/share/man/man1: miss matching wildcard in /usr/share/man/man1: wget.1* matched: /usr/share/man/man1/wget.1.gz ult_src: File /usr/share/man/man1/wget.1.gz in mantree /usr/share/man candidate: 0 0 wget /usr/share/man /usr/share/man/man1/wget.1.gz A wget 1 1 searching in /usr/man, section 1 trying section 1 with globbing update_directory_cache /usr/man: miss matching wildcard in /usr/man: man1* matched: /usr/man/man1 update_directory_cache /usr/man/man1: miss matching wildcard in /usr/man/man1: wget.1* update_directory_cache /usr/man: hit matching wildcard in /usr/man: cat1* Succeeded in opening /var/cache/man/fsstnd/index.db O_RDONLY searching in /usr/local/man, section n trying section n with globbing update_directory_cache /usr/local/man: hit matching wildcard in /usr/local/man: mann* update_directory_cache /usr/local/man: hit matching wildcard in /usr/local/man: catn* searching in /usr/share/man, section n trying section n with globbing update_directory_cache /usr/share/man: hit matching wildcard in /usr/share/man: mann* update_directory_cache /usr/share/man: hit matching wildcard in /usr/share/man: catn* Succeeded in opening /var/cache/man/index.db O_RDONLY found 2 names/extensions multi key lookup (Wget 1) multi key lookup (wget 1) searching in /usr/man, section n trying section n with globbing update_directory_cache /usr/man: hit matching wildcard in /usr/man: mann* update_directory_cache /usr/man:
Bug#1042855: openjdk-8: Please consider using libjpeg-dev virtual package as dependency
Package: openjdk-8 Version: openjdk-8 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu mantic ubuntu-patch X-Debbugs-Cc: vladimir.pe...@canonical.com Dear Maintainer, openjdk-8 382-ga-1 uses libjpeg-turbo62 as a dependency rather than libjpeg-dev that it used before. The attached patch updates control and rules to select libjpeg-dev as a dependency allowing Ubuntu sync. The attached patch was applied to achieve the following: * Use libjpeg-dev virtual package to solve dependency-wait (LP: #2028973). Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers lunar-updates APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), (100, 'lunar-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-25-generic (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru openjdk-8-8u382-ga/debian/control openjdk-8-8u382-ga/debian/control --- openjdk-8-8u382-ga/debian/control 2023-07-22 05:19:02.0 +1200 +++ openjdk-8-8u382-ga/debian/control 2023-07-29 07:37:27.0 +1200 @@ -9,7 +9,7 @@ xvfb, xauth, xfonts-base, libgl1-mesa-dri, xfwm4, x11-xkb-utils, dbus-x11, openjdk-8-jre-headless | default-jre-headless (>= 2:1.8), jtreg, libasmtools-java, testng, time, autoconf (>= 2.69), automake, ant, ant-optional, fastjar (>= 2:0.96-0ubuntu2), gcc-12, g++-12, libxtst-dev, libxi-dev, libxt-dev, libxaw7-dev, libxrender-dev, libcups2-dev, libasound2-dev, liblcms2-dev, libxinerama-dev, libkrb5-dev, xsltproc, libpcsclite-dev, libfreetype-dev, libgtk2.0-dev, libffi-dev, - zlib1g-dev, libattr1-dev, libpng-dev, libjpeg62-turbo-dev, libgif-dev, libpulse-dev (>= 0.9.12) [!alpha], systemtap-sdt-dev, + zlib1g-dev, libattr1-dev, libpng-dev, libjpeg-dev, libgif-dev, libpulse-dev (>= 0.9.12) [!alpha], systemtap-sdt-dev, libnss3-dev (>= 2:3.26), openjdk-8-jdk-headless , dpkg-dev (>= 1.17.14), Standards-Version: 4.6.2 Homepage: http://openjdk.java.net/ diff -Nru openjdk-8-8u382-ga/debian/rules openjdk-8-8u382-ga/debian/rules --- openjdk-8-8u382-ga/debian/rules 2023-07-22 05:19:02.0 +1200 +++ openjdk-8-8u382-ga/debian/rules 2023-07-29 07:37:27.0 +1200 @@ -684,12 +684,10 @@ else bd_syslibs += libpng-dev, endif -ifeq ($(derivative),Ubuntu) - bd_syslibs += libjpeg-turbo8-dev, -else ifneq (,$(filter $(distrel),wheezy)) +ifneq (,$(filter $(distrel),wheezy)) bd_syslibs += libjpeg8-dev, else - bd_syslibs += libjpeg62-turbo-dev, + bd_syslibs += libjpeg-dev, endif bd_syslibs += \ libgif-dev,
Bug#1037567: abseil: ftbfs with GCC-13
Hi, On 2023-06-26 12:55, Benjamin Barenblat wrote: > Control: fixed -1 20230125.3 > Control: forwarded -1 https://github.com/abseil/abseil-cpp/issues/1366 > Control: owner -1 ! > Control: tags -1 upstream fixed-upstream fixed-in-experimental > > This has been resolved in the 20230125 series, which is currently in > experimental and will be included in trixie after it transitions. What are your plans with this transition? This bug will soon block the riscv64 bootstrap in the official archive, and thus we would be interested by a relatively quick fix in unstable. Thanks Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net signature.asc Description: PGP signature
Bug#1042845: libembperl-perl: FTBFS with Perl 5.38: test failures
Hi Niko, Niko Tyni wrote: > This package fails to build from source with Perl 5.38 (currently in > experimental.) Thanks for the bug report. > I assume the diagnostics have changed again and it's just the tests that > need adjusting, but I haven't checked properly. Will look into it, but may take a while. >cat: test/tmp/httpd.pid: No such file or directory That one looks familiar, but IIRC was a red herring. 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
Bug#1041537: python3 platlib points again to /usr/local
On Fri, 21 Jul 2023 at 14:09, Jeremy Bícha wrote: > We have been working around this in several Debian packages by setting > this in debian/rules: > export DEB_PYTHON_INSTALL_LAYOUT = deb I'm confused. Why is this not set by default when building packages? FWICT this is a custom patch in Debian to make Python use deb paths.In this case Meson is doing exactly what you ask it to do, which is to use local paths because that environment variable is not set to `deb`.
Bug#1042854: libcss-dom-perl: FTBFS with Perl 5.38: Old package separator "'" deprecated
Source: libcss-dom-perl Version: 0.17-2 Severity: important Tags: ftbfs sid trixie patch Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=146661 User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) There's a patch by Yves Orton in the upstream ticket. http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/libcss-dom-perl_0.17-2/libcss-dom-perl_0.17-2_amd64-2023-07-06T13:44:23Z.build # Failed test 'no warnings for style belonging to element itself' # at t/css-dom.t line 34. # got: 'Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Style.pm line 174. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Style.pm line 175. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Style.pm line 176. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule.pm line 49. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 96. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 97. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 133. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 141. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 146. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 154. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 155. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 161. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 169. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 170. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 177. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Rule/Style.pm line 178. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Parser.pm line 372. # Old package separator "'" deprecated at /<>/blib/lib/CSS/DOM/Parser.pm line 416. # ' # expected: undef # Looks like you failed 1 test of 3. [...] Test Summary Report --- t/css-dom.t(Wstat: 256 (exited 1) Tests: 3 Failed: 1) Failed test: 3 Non-zero exit status: 1 Files=31, Tests=3203, 4 wallclock secs ( 0.33 usr 0.06 sys + 3.09 cusr 0.48 csys = 3.96 CPU) Result: FAIL -- Niko Tyni nt...@debian.org
Bug#1042848: bookworm-pu: package curl/7.88.1-10+deb12u2
Control: tag -1 confirmed On Tue, Aug 01, 2023 at 07:30:50PM +, John Scott wrote: > This upload is to address a regression in CURL, an undesirable change in > behavior as compared to Bullseye which works correctly. This upload contains > a cherry-picked fix that allows CURL to be built with OpenLDAP-specific code > instead of unmaintained fallback code as intended. Basically, the Autotools > build system only would fail to detect OpenLDAP properly (Debian uses > OpenLDAP). The fallback code, besides being unmaintained, has numerous > incidental issues. Pleaes go ahead. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1042853: docknot: FTBFS with Perl 5.38: t/spin/errors.t failure
Source: docknot Version: 7.01-1 Severity: important Tags: ftbfs sid trixie Forwarded: https://github.com/rra/docknot/issues/6 User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) This looks like just a test-only diagnostics change, but please file a bug against perl to add a Breaks entry if there's actual runtime breakage after all. http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/docknot_7.01-1/docknot_7.01-1_amd64-2023-07-06T13:37:26Z.build # Failed test 'errors are correct' # at t/spin/errors.t line 46. # got: 'errors.th:1: cannot find argument 2: Did not find opening bracket after prefix: "(?^:\G\s*)", detected at offset 2 # errors.th:3: invalid macro placeholder \2 (greater than 1) # errors.th:5: invalid macro argument count for \badcount # errors.th:9: unknown variable \=UNKNOWN # errors.th:11: unknown command or macro \unknown # errors.th:14: space in anchor "#foo bar" # errors.th:15: no package release information available # errors.th:16: no sitemap file found # errors.th:17: no package version information available # errors.th:17: cannot stat file nonexistent-file # ' # expected: 'errors.th:1: cannot find argument 2: Did not find opening bracket after prefix: "\s*", detected at offset 2 # errors.th:3: invalid macro placeholder \2 (greater than 1) # errors.th:5: invalid macro argument count for \badcount # errors.th:9: unknown variable \=UNKNOWN # errors.th:11: unknown command or macro \unknown # errors.th:14: space in anchor "#foo bar" # errors.th:15: no package release information available # errors.th:16: no sitemap file found # errors.th:17: no package version information available # errors.th:17: cannot stat file nonexistent-file # ' # Looks like you failed 1 test of 2. [...] Test Summary Report --- t/spin/errors.t (Wstat: 256 (exited 1) Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 1 Files=32, Tests=872, 24 wallclock secs ( 0.14 usr 0.05 sys + 20.32 cusr 2.82 csys = 23.33 CPU) Result: FAIL -- Niko Tyni nt...@debian.org
Bug#1042795: bookworm-pu: package mgba/0.10.1+dfsg-1+deb12u1
Control: tag -1 confirmed On Mon, Jul 31, 2023 at 04:26:12PM -0700, Ryan Tandy wrote: > I would like to update mgba in bookworm with the following changes. Both > bugs were introduced in mgba 0.10.0 and are thus regressions in > bookworm. The patches are cherry-picks from mgba 0.10.2. Please go ahead (your changelog should target bookworm). Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1042852: liblexical-failure-perl: FTBFS with Perl 5.38: test failures
Source: liblexical-failure-perl Version: 0.07-3 Severity: important Tags: ftbfs trixie sid fixed-upstream Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=148315 User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) It seems to be fixed upstream in 0.001000 according to the Changes file, though the upstream bug is still open. It's not clear to me if this is just a test diagnostics issue, or if the current version is actually broken with Perl 5.38. Most of the test failures are about deprecations warnings, but at least the t/aliased.t failure looks different. It would probably be prudent to add a Breaks entry on the perl side just in case, so please file a bug about that when this issue is fixed. http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/liblexical-failure-perl_0.07-3/liblexical-failure-perl_0.07-3_amd64-2023-07-06T13:46:41Z.build Test Summary Report --- t/aliased.t (Wstat: 256 (exited 1) Tests: 13 Failed: 1) Failed test: 3 Non-zero exit status: 1 t/inner_scalar.t(Wstat: 1536 (exited 6) Tests: 21 Failed: 11) Failed tests: 2-6, 16-21 Non-zero exit status: 6 Parse errors: Bad plan. You planned 15 tests but ran 21. t/simple.t (Wstat: 256 (exited 1) Tests: 14 Failed: 1) Failed test: 4 Non-zero exit status: 1 Files=9, Tests=59, 1 wallclock secs ( 0.05 usr 0.00 sys + 0.71 cusr 0.15 csys = 0.91 CPU) Result: FAIL -- Niko Tyni nt...@debian.org
Bug#1042851: sddm: Fails to terminate during shutdown/reboot (timeout)
Package: sddm Version: 0.19.0-5 Severity: normal X-Debbugs-Cc: dh463...@mailbox.org Dear Maintainer, * What led up to the situation? This happens sometimes upon shutdown/reboot while logged in (KDE Plasma). * What exactly did you do (or not do) that was effective (or ineffective)? Selected shutdown/reboot from menu. * What was the outcome of this action? SDDM fails to terminate and has to be killed. This causes a delay of the shutdown/reboot due to a timeout of 90s. * What outcome did you expect instead? SDDM should be terminated and no delay should occur. I attached the output of journalctl -rb -1. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sddm depends on: ii adduser 3.134 ii debconf [debconf-2.0] 1.5.82 ii libc6 2.36-9+deb12u1 ii libgcc-s1 12.2.0-14 ii libpam0g1.5.2-6 ii libqt5core5a5.15.8+dfsg-11 ii libqt5dbus5 5.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5network5 5.15.8+dfsg-11 ii libqt5qml5 5.15.8+dfsg-3 ii libqt5quick55.15.8+dfsg-3 ii libstdc++6 12.2.0-14 ii libsystemd0 252.12-1~deb12u1 ii libxcb-xkb1 1.15-1 ii libxcb1 1.15-1 ii qml-module-qtquick2 5.15.8+dfsg-3 ii x11-common 1:7.7+23 ii xauth 1:1.1.2-1 ii xserver-xorg [xserver] 1:7.7+23 Versions of packages sddm recommends: ii libpam-systemd 252.12-1~deb12u1 ii sddm-theme-breeze [sddm-theme] 4:5.27.5-2 ii sddm-theme-debian-breeze [sddm-theme] 4:5.27.5-2 Versions of packages sddm suggests: ii libpam-kwallet5 5.27.5-2 pn qtvirtualkeyboard-plugin -- debconf information: shared/default-x-display-manager: sddm sddm/daemon_name: /usr/bin/sddm Aug 01 20:56:53 laptop systemd-journald[383]: Journal stopped Aug 01 20:56:53 laptop systemd-shutdown[1]: Sending SIGTERM to remaining processes... Aug 01 20:56:53 laptop systemd-shutdown[1]: Syncing filesystems and block devices. Aug 01 20:56:53 laptop systemd-shutdown[1]: Watchdog running with a timeout of 10min. Aug 01 20:56:53 laptop systemd-shutdown[1]: Using hardware watchdog 'SP5100 TCO timer', version 0, device /dev/watchdog0 Aug 01 20:56:53 laptop kernel: watchdog: watchdog0: watchdog did not stop! Aug 01 20:56:53 laptop systemd[1]: Watchdog running with a timeout of 10min. Aug 01 20:56:53 laptop systemd[1]: Using hardware watchdog 'SP5100 TCO timer', version 0, device /dev/watchdog0 Aug 01 20:56:53 laptop systemd[1]: Shutting down. Aug 01 20:56:53 laptop systemd[1]: Reached target reboot.target - System Reboot. Aug 01 20:56:53 laptop systemd[1]: Finished systemd-reboot.service - System Reboot. Aug 01 20:56:53 laptop systemd[1]: systemd-reboot.service: Deactivated successfully. Aug 01 20:56:53 laptop systemd[1]: Reached target final.target - Late Shutdown Services. Aug 01 20:56:53 laptop systemd[1]: Reached target shutdown.target - System Shutdown. Aug 01 20:56:53 laptop systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems. Aug 01 20:56:53 laptop systemd[1]: systemd-remount-fs.service: Deactivated successfully. Aug 01 20:56:53 laptop systemd[1]: Stopped systemd-sysusers.service - Create System Users. Aug 01 20:56:53 laptop systemd[1]: systemd-sysusers.service: Deactivated successfully. Aug 01 20:56:53 laptop systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. Aug 01 20:56:53 laptop systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully. Aug 01 20:56:53 laptop systemd[1]: Stopped target local-fs-pre.target - Preparation for Local File Systems. Aug 01 20:56:53 laptop systemd[1]: Removed slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck. Aug 01 20:56:53 laptop systemd[1]: Stopped systemd-fsck@dev-disk-by\x2duuid-44b2bfdb\x2d5630\x2d4a0c\x2d81c0\x2dd47e60c4b034.service - File System Check on /dev/disk/by-uuid/44b2bfdb-5630-4a0c-81c0-d47e60c4b034. Aug 01 20:56:53 laptop systemd[1]: systemd-fsck@dev-disk-by\x2duuid-44b2bfdb\x2d5630\x2d4a0c\x2d81c0\x2dd47e60c4b034.service: Deactivated successfully. Aug 01 20:56:53 laptop systemd[1]: Reached target umount.target - Unmount All Filesystems. Aug 01 20:56:53 laptop systemd[1]: Unmounted home.mount - /home. Aug 01 20:56:53 laptop systemd[1]: home.mount: Deactivated successfully. Aug 01 20:56:53
Bug#1042730: bookworm-pu: package zfs-linux/2.1.12-1~deb12u1
Control: tag -1 moreinfo On Mon, Jul 31, 2023 at 03:53:23PM +0800, Aron Xu wrote: > zfs-linux in bookworm is affected by #1040183 which is considered an > important malfunction. Please cherry-pick a fix for this and propose a new debdiff; the upstream release contains too much else to be accepted. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1042050: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to `hidden_function'
On Wed, 26 Jul 2023 at 00:16, Lucas Nussbaum wrote: > Relevant part (hopefully): > > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main': > > ./b 52a78b9866/../test cases/failing build/2 hidden > > symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to > > `hidden_function' > > collect2: error: ld returned 1 exit status As before, that is not the real issue. It is this: --- ==796327==ERROR: LeakSanitizer: detected memory leaks Direct leak of 280 byte(s) in 2 object(s) allocated from: #0 0x7fcf1c99ef97 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:77 #1 0x7fcf1c77e2a5 in g_malloc0 (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x602a5) (BuildId: 3ca2ab24e2ecf8bb465ae4b321ee5d69412afd50) Indirect leak of 4172 byte(s) in 2 object(s) allocated from: #0 0x7fcf1c99f5bf in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69 #1 0x7fcf1c77e25d in g_malloc (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6025d) (BuildId: 3ca2ab24e2ecf8bb465ae4b321ee5d69412afd50) Indirect leak of 96 byte(s) in 1 object(s) allocated from: #0 0x7fcf1c99ef97 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:77 #1 0x7fcf1c77e2a5 in g_malloc0 (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x602a5) (BuildId: 3ca2ab24e2ecf8bb465ae4b321ee5d69412afd50) Indirect leak of 28 byte(s) in 1 object(s) allocated from: #0 0x7fcf1c99f5bf in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69 #1 0x7fcf1c394017 in __vasprintf_internal libio/vasprintf.c:116 #2 0x8876f375b14d25ff () SUMMARY: AddressSanitizer: 4576 byte(s) leaked in 6 allocation(s). -- This is actually a bug in gobject-introspection. It has already been fixed upstream. Dunno what the schedule is for getting that into a release and on to Debian.
Bug#1042850: libdatabase-dumptruck-perl: FTBFS with Perl 5.38: t/dumptruck.t failure
Source: libdatabase-dumptruck-perl
Version: 1.2-3
Severity: important
Tags: ftbfs trixie sid patch
Forwarded: https://github.com/lkundrak/perl-database-dumptruck/issues/2
User: debian-p...@lists.debian.org
Usertags: perl-5.38-transition
This package fails to build from source with Perl 5.38 (currently in
experimental.)
The upstream ticket points to a possible patch at
https://src.fedoraproject.org/rpms/perl-Database-DumpTruck/raw/20e8880e98b146200c20f379edd847b49f4aea0d
Build log at
http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/libdatabase-dumptruck-perl_1.2-3/libdatabase-dumptruck-perl_1.2-3_amd64-2023-07-06T13:44:51Z.build
dh_auto_test
/usr/bin/perl Build test --verbose 1
# Failed test 'Proper data was retrieved from the database'
# at t/dumptruck.t line 189.
# Structures begin differing at:
# $got->[0]{random}{yes} = 1
# $expected->[0]{random}{yes} = '1'
# Looks like you failed 1 test of 43.
[...]
Test Summary Report
---
t/dumptruck.t (Wstat: 256 (exited 1) Tests: 43 Failed: 1)
Failed test: 43
Non-zero exit status: 1
Files=2, Tests=44, 0 wallclock secs ( 0.01 usr 0.01 sys + 0.25 cusr 0.06
csys = 0.33 CPU)
Result: FAIL
--
Niko Tyni nt...@debian.org
Bug#1041142: closed by Diederik de Haas (Re: Debian's BTS is not for regular user questions)
On 01.08.23 21:08, AlMa wrote: This is a rather naive understanding of how logging is done in practice. The reality is that developers often don't know (and maybe can't know) just how severe an odd condition may be in practice. Unfortunately, neither do I. Though seemingly unrelated journal-visible issues are quite often indeed independent, sometimes unexpected interactions or common root causes occur. Perhaps, there should be a category for tentative errors and/or tentative warnings (i.e., with an unknown (or yet unknown) severity in practice). E.g., dereferencing a zero pointer, or division by zero, or garbled screen output, or the inability to read '/' as the root user, etc. are almost always errors (except when you test error-handling routes themselves; then a division by zero is not a bug but a must). If you say that it is unknown how severe a message such as “ACPI Warning: SystemIO range … conflicts with OpRegion … . lpc_ich: Resource conflict(s) found affecting gpio_ich” really is, it should not be a warning (especially, it should not warn the reader) but be a tentative warning (i.e., it might warn the reader in the future or under particular circumstances). The (new?) colors of the tentative errors and warnings should be clearly stated in the manpages of journalctl.
Bug#1042849: libmodule-reader-perl: FTBFS with Perl 5.38: t/memory.t failure
Source: libmodule-reader-perl Version: 0.003003-3 Severity: important Tags: ftbfs sid trixie Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=148979 User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/libmodule-reader-perl_0.003003-3/libmodule-reader-perl_0.003003-3_amd64-2023-07-06T13:48:09Z.build # Failed test 'regex fails the same as require' # at t/memory.t line 99. # got: 'Can't locate object method "INC" via package "Regexp"' # expected: 'Can't locate object method "INC", nor "INCDIR" nor string overload via package "Regexp" in object hook in @INC' # Failed test 'class without INC fails the same as require' # at t/memory.t line 99. # got: 'Can't locate object method "INC" via package "NonHook"' # expected: 'Can't locate object method "INC", nor "INCDIR" nor string overload via package "NonHook" in object hook in @INC' # Looks like you failed 2 tests of 18. t/memory.t .. ok 1 - correctly load module from sub @INC hook ok 2 - loads overridden module from sub @INC hook ok 3 - found => \%INC loads mod as it was required ok 4 - calculated file matches loaded filename ok 5 - hook returning an array ref is ignored ok 6 - hook returning a hash ref is ignored ok 7 - hash ref fails the same as require ok 8 - scalar ref fails the same as require not ok 9 - regex fails the same as require not ok 10 - class without INC fails the same as require ok 11 - class with INC hook works the same as require ok 12 - child class of INC hook works the same as require ok 13 - array ref without code fails the same as require ok 14 - array ref with string fails the same as require ok 15 - array ref with stringy main sub fails the same as require ok 16 - array ref with stringy fully qualified sub fails the same as require ok 17 - array ref with hash ref fails the same as require ok 18 - array ref with code fails the same as require 1..18 Dubious, test returned 2 (wstat 512, 0x200) Failed 2/18 subtests Test Summary Report --- t/memory.t(Wstat: 512 (exited 2) Tests: 18 Failed: 2) Failed tests: 9-10 Non-zero exit status: 2 Files=3, Tests=119, 1 wallclock secs ( 0.03 usr 0.02 sys + 0.24 cusr 0.06 csys = 0.35 CPU) Result: FAIL Failed 1/3 test programs. 2/119 subtests failed. make[1]: *** [Makefile:826: test_dynamic] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 make: *** [debian/rules:4: build] Error 25 -- Niko Tyni nt...@debian.org
Bug#1042848: bookworm-pu: package curl/7.88.1-10+deb12u2
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: c...@packages.debian.org, samuel...@debian.org Control: affects -1 + src:curl [ Reason ] This upload is to address a regression in CURL, an undesirable change in behavior as compared to Bullseye which works correctly. This upload contains a cherry-picked fix that allows CURL to be built with OpenLDAP-specific code instead of unmaintained fallback code as intended. Basically, the Autotools build system only would fail to detect OpenLDAP properly (Debian uses OpenLDAP). The fallback code, besides being unmaintained, has numerous incidental issues. [ Impact ] If this update isn't approved, then not only will advanced LDAP functionality not work, but fetching binary LDAP attributes will completely spoil CURL's output by injecting binary bytes into what's supposed to be a text file. This is the biggest fallout of using the unmaintained code. I don't think this issue is security-relevant, but it does make the LDAP functionality somewhat useless. The number of CURL LDAP users is hard to predict; LDAP is used frequently in internal-only business environments. [ Tests ] I manually tested the package against real-world LDAP servers; that's how I ran into the bug in the first place and noticed that it was a regression from the Bullseye behavior. Furthermore, I have added an autopkgtest validating that fetching binary attributes now works correctly. This test works by spinning up a real LDAP server and then using libcurl to fetch binary data from it. I verified that the autopkgtest fails without the upstream CURL patch, and passes with the CURL patch. [ Risks ] No libcurl code is touched; it's merely a change of a few lines so that the Autotools build system builds the OpenLDAP-using code. With the new autopkgtest especially, the risks are very small. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] The changes consist of updating the package changelog, adding the upstream CURL patch to the patch series, and then the biggest change is the new autopkgtest. (I chose to write it in C, so you could say it's rather verbose.) The OpenLDAP maintainers are aware of the new autopkgtest and do not have reservations. [ Other info ] I do not have uploading privileges and this is not an NMU; this upload was prepared with the assistance and supervision of DD Samuel Henrique who has been maintaining CURL lately. He will upload the package when this unblock request is approved. diff -Nru curl-7.88.1/debian/changelog curl-7.88.1/debian/changelog --- curl-7.88.1/debian/changelog 2023-07-23 17:43:52.0 -0400 +++ curl-7.88.1/debian/changelog 2023-07-25 08:11:34.0 -0400 @@ -1,3 +1,13 @@ +curl (7.88.1-10+deb12u2) bookworm; urgency=medium + + * Team upload. + * LDAP backend: correct the usage of OpenLDAP-specific functionality being +disabled with an upstream patch (Closes: #1041964) +This corrects the improper fetching of binary attributes. + * debian/tests: add a DEP-8 test that getting binary LDAP attributes works now + + -- John Scott Tue, 25 Jul 2023 08:11:34 -0400 + curl (7.88.1-10+deb12u1) bookworm-security; urgency=medium * Team upload. diff -Nru curl-7.88.1/debian/patches/series curl-7.88.1/debian/patches/series --- curl-7.88.1/debian/patches/series 2023-07-23 17:43:52.0 -0400 +++ curl-7.88.1/debian/patches/series 2023-07-25 08:11:34.0 -0400 @@ -31,3 +31,4 @@ # Used to generate packages for the other crypto libraries. 90_gnutls.patch 99_nss.patch +Use-OpenLDAP-specific-functionality.patch diff -Nru curl-7.88.1/debian/patches/Use-OpenLDAP-specific-functionality.patch curl-7.88.1/debian/patches/Use-OpenLDAP-specific-functionality.patch --- curl-7.88.1/debian/patches/Use-OpenLDAP-specific-functionality.patch 1969-12-31 19:00:00.0 -0500 +++ curl-7.88.1/debian/patches/Use-OpenLDAP-specific-functionality.patch 2023-07-25 08:11:34.0 -0400 @@ -0,0 +1,35 @@ +Description: Fix Autotools not enabling OpenLDAP-specific functionality + The non-OpenLDAP code paths are less tested, less featureful, less secure, + and omitted in the build system by accident. It has been discovered that this + also mitigates curl not being able to make LDIF output when attributes have + binary values. +Origin: upstream, https://github.com/curl/curl/commit/0ac6108856b9d500bc376d1d7e0b648d15499837.patch|commit:) +Bug: https://github.com/curl/curl/issues/11372 +Applied-Upstream: 8.2.0, https://github.com/curl/curl/commit/0ac6108856b9d500bc376d1d7e0b648d15499837 +Reviewed-By: John Scott +Last-Update: 2023-07-25 + +--- curl-7.88.1.orig/configure.ac curl-7.88.1/configure.ac +@@ -1663,16 +1663,19 @@ if test x$CURL_DISABLE_LDAP != x1 ; then + fi + + if test
Bug#1042847: libstring-license-perl: broken with Perl 5.38: syntax error near "class String::License::Naming::Custom :"
Package: libstring-license-perl Version: 0.0.2-1 Severity: important Tags: ftbfs trixie sid Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=148507 User: debian-p...@lists.debian.org Usertags: perl-5.38-transition Control: affects -1 licensecheck Some modules in this package report syntax errors with Perl 5.38 (currently in experimental.) This also makes the test suite fail, so the package fails to build from source. When this is fixed, please file a bug on the perl package to add a Breaks entry for earlier versions so that partial upgrades cannot end up with a broken combination. http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/libstring-license-perl_0.0.2-1/libstring-license-perl_0.0.2-1_amd64-2023-07-06T13:51:44Z.build dh_auto_test make -j4 test TEST_VERBOSE=1 make[1]: Entering directory '/<>' PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t syntax error at /<>/blib/lib/String/License/Naming/Custom.pm line 62, near "class String::License::Naming::Custom :" Execution of /<>/blib/lib/String/License/Naming/Custom.pm aborted due to compilation errors. Compilation failed in require at /<>/blib/lib/String/License.pm line 45. BEGIN failed--compilation aborted at /<>/blib/lib/String/License.pm line 45. Compilation failed in require at t/basic-lib-no-RE2.t line 7. BEGIN failed--compilation aborted at t/basic-lib-no-RE2.t line 7. [...] dh_auto_test make -j4 test TEST_VERBOSE=1 make[1]: Entering directory '/<>' PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t syntax error at /<>/blib/lib/String/License/Naming/Custom.pm line 62, near "class String::License::Naming::Custom :" Execution of /<>/blib/lib/String/License/Naming/Custom.pm aborted due to compilation errors. Compilation failed in require at /<>/blib/lib/String/License.pm line 45. BEGIN failed--compilation aborted at /<>/blib/lib/String/License.pm line 45. Compilation failed in require at t/basic-lib-no-RE2.t line 7. BEGIN failed--compilation aborted at t/basic-lib-no-RE2.t line 7. -- Niko Tyni nt...@debian.org
Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson
On 8/1/23 3:13 PM, Eli Schwartz wrote: > On Thu, 27 Jul 2023 15:43:26 +0100 Simon McVittie wrote: >> Is there a way this can be done, without making packages FTBFS if debhelper >> is backported to an older suite but Meson is not? -Dpython.bytecompile=-1 >> will cause `meson setup` to fail if Meson is an older version, and I'm not >> aware of a way to say "set this option if supported, ignore if not" without >> parsing `meson --version` and comparing it with a threshold. > > > Just tested, and adding this to a --native-file should work: > > ``` > [built-in options] > python.bytecompile = '-1' > ``` Sorry, no, this works for versions of meson that have the option, but setting unknown properties isn't ignored. Ignore me... -- Eli Schwartz
Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson
On Thu, 27 Jul 2023 15:43:26 +0100 Simon McVittie wrote: > Is there a way this can be done, without making packages FTBFS if debhelper > is backported to an older suite but Meson is not? -Dpython.bytecompile=-1 > will cause `meson setup` to fail if Meson is an older version, and I'm not > aware of a way to say "set this option if supported, ignore if not" without > parsing `meson --version` and comparing it with a threshold. Just tested, and adding this to a --native-file should work: ``` [built-in options] python.bytecompile = '-1' ``` -- Eli Schwartz
Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson
On Fri, 28 Jul 2023 13:41:14 +0300 Jussi Pakkanen wrote: > On Thu, 27 Jul 2023 at 17:45, Simon McVittie wrote: > > > As far as I'm aware, we never want to include .pyc in Debian packages, > > so I think debhelper's meson build system plugin should be turning this off > > as a standard setting for all Debian packages (similar to the way it > > sets --prefix=/usr as a standard setting for all Debian packages). > > > > Do the Meson maintainers agree? > > Obviously the defaults should do the correct thing. In fact until > yesterday that is what I thought the code does not do byte > compilation. We might even consider changing the default for this as I > would imagine all distros will hit the same issue. >From the original implementation, I discussed the topic: https://github.com/mesonbuild/meson/pull/11530#discussion_r1140204427 My conclusion was that all distros want bytecode, except for Debian, which doesn't want bytecode. There is one exception that does not want bytecode but instead of a lintian style "error if you have it" approach, they have a debhelper style "DTRT and automatically delete it" approach. I also made the following comment: """ I'm a bit surprised that debhelper doesn't help out your .deb by removing them for you, but whatever... It's theoretically possible to hardcode Debian yet again and skip this install script, but only if running inside a package build. Is there even a way to detect this? No idea. Not an enthusiastic topic anyway. """ -- Eli Schwartz
Bug#1042846: sdf: FTBFS with Perl 5.38: Old package separator "'" deprecated
Source: sdf Version: 2.001+1-8 Severity: important Tags: ftbfs trixie sid User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/sdf_2.001+1-8/sdf_2.001+1-8_amd64-2023-07-06T15:02:55Z.build dh_auto_test make -j4 test TEST_VERBOSE=1 make[1]: Entering directory '/<>' make[2]: Entering directory '/<>/bin' Manifying 1 pod document make[2]: Leaving directory '/<>/bin' make[2]: Entering directory '/<>/perllib' make[2]: Leaving directory '/<>/perllib' "/usr/bin/perl" t/TEST 1 Old package separator "'" deprecated at ../../blib/script/sdf line 607. Old package separator "'" deprecated at ../../blib/script/sdf line 608. Old package separator "'" deprecated at ../../blib/script/sdf line 608. Old package separator "'" deprecated at ../../blib/script/sdf line 609. Old package separator "'" deprecated at ../../blib/script/sdf line 610. Old package separator "'" deprecated at ../../blib/script/sdf line 610. [...] filter/table.t . 1..2 # table.sdf: output file ok ok 1 # table.sdf: log file FAILED not ok 2 Failed 1/2 subtests Test Summary Report --- general/expr.t (Wstat: 0 Tests: 2 Failed: 1) Failed test: 2 general/formats.t (Wstat: 0 Tests: 2 Failed: 1) Failed test: 2 [...] filter/table.t (Wstat: 0 Tests: 2 Failed: 1) Failed test: 2 Files=50, Tests=100, 15 wallclock secs ( 0.27 usr 0.19 sys + 4.88 cusr 0.99 csys = 6.33 CPU) Result: FAIL Failed 50/50 test programs. 50/100 subtests failed. make[1]: *** [Makefile:812: test] Error 255 -- Niko Tyni nt...@debian.org
Bug#1042845: libembperl-perl: FTBFS with Perl 5.38: test failures
Source: libembperl-perl Version: 2.5.0-17 Severity: important Tags: ftbfs sid trixie User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) I assume the diagnostics have changed again and it's just the tests that need adjusting, but I haven't checked properly. http://perl.debian.net/rebuild-logs/perl-5.38/libembperl-perl_2.5.0-17/libembperl-perl_2.5.0-17+b1_amd64-2023-07-21T10:56:05Z.build PERL_DL_NONLAZY=0 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl loading...ok Testing offline mode... #0 ascii... ok #1 pure.htm...ok #2 nooutput.htm...ok #3 nooutput.htm...ok #4 plain.htm... ok #5 plain.htm... ok #6 plain.htm... ok #7 plainblock.htm... ok #8 plainblock.htm... ok #15 error.htm... Expected 4 more error(s) in logfile Input: test/html/error.htm Output: test/tmp/out.htm Log: test/tmp/test.log Testparameter: errors = 6 condition = $] >= 5.01 version = 2 cgi = 0 repeat = 3 ERRORS detected! NOT all tests have been passed successfully cat: test/tmp/httpd.pid: No such file or directory make[1]: *** [Makefile:1462: test_dynamic] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 make: *** [debian/rules:19: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 -- Niko Tyni nt...@debian.org
Bug#1041142: closed by Diederik de Haas (Re: Debian's BTS is not for regular user questions)
This is a rather naive understanding of how logging is done in practice. The reality is that developers often don't know (and maybe can't know) just how severe an odd condition may be in practice. Unfortunately, neither do I. Though seemingly unrelated journal-visible issues are quite often indeed independent, sometimes unexpected interactions or common root causes occur. If there is still an actual problem on this machine (not just warning messages), please open *1* bug report that describes the actual problem and the log messages. If under *actual* you mean *user-disturbing* (“error, flaw or fault in the design, development, or operation of computer software that causes it to produce an incorrect or unexpected result, or to behave in unintended ways”, a definition from Wikipedia), I've got none for the kernel because the kernel is not visible (nor should it be visible) to users directly. The only (sometimes reproducible) full lock-up (SysRq doesn't seem to work) I saw myself, which might concern the kernel, happened when epiphany-browser loads Google maps directly or embedded into a different Web site; I plan to submit a bug report. As for other high-level problems which are already posted, there are at least two (and more are likely to come). One of them, already resolved recently (though the root cause is still unknown, the intermediate problem is gone) is #1041014. If I had to state the *actual* problem there, it would have been „the machine doesn't boot properly, the screen is black, the keyboard doesn't seem to respond“; such a description would've probably been considered *actual* but pretty useless to the maintainers. Even if it would have been useful to you, then only in the sense that a failure to start a graphical user interface should not prevent text logins from visibly showing up on Ctrl + Alt + F1 … Ctrl + Alt + F6 and that error codes (instead of "ERRNO" and "exit-code") from failed spawns by systemd should be printed. As another big problem on another machine, cf. #1040497. A next step in debugging this could be looking at how /run/gdm3/custom.conf is created, whether the logic in /lib/udev/rules.d/61-gdm.rules is correct, and whether using X.Org (in Debian 12) instead of Wayland (in Debian 11) is really justified on the particular machine (https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1403697 doesn't apply in my use case because the onboard graphics chip is usually not connected to a monitor in my setup, except if the monitor connected to the PCIe NVIDIA card happens to fail, which has not yet happened). If this issue involves the kernel at all, then probably the nouveau driver. The details of this issue are beyond my level of expertise, so I'm unsure how much I can really do myself. Gratefully, Alma
Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter
Hi, Steve and Len, Thank you for pointing this out. On Mon 2023-07-31 09.22.35, Lennart Sorensen wrote: On Sun, Jul 30, 2023 at 01:08:13PM +0100, Steve McIntyre wrote: I'm a little confused here... You say the machine is a Thinkpad X230, but the attached cpuinfo says you have an Atom CPU and the DMI data says it's an ASUSTeK Eee PC. What hardware are we actually looking at here please? It also says 4.15 kernel which is clearly not bookworm. I think the installation log was accidentally from a much earlier install on a different machine. The installation report must indeed be ancient, from an installation on an Eee ‘netbook’ some years ago, possibly Stretch or an even older release. My bug report relates to the situation after an upgrade from Bullseye on the Thinkpad X230: $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 36 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz CPU family: 6 Model: 58 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 Stepping:9 CPU(s) scaling MHz: 55% CPU max MHz: 3300. CPU min MHz: 1200. BogoMIPS:5188.29 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization: VT-x L1d cache: 64 KiB (2 instances) L1i cache: 64 KiB (2 instances) L2 cache:512 KiB (2 instances) L3 cache:3 MiB (1 instance) NUMA node(s):1 NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Mmio stale data: Unknown: No mitigations Vulnerability Retbleed: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2:Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds: Vulnerable: No microcode Vulnerability Tsx async abort: Not affected $ uname -a Linux bamboo 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux $ sudo lshw bamboo description: Notebook product: 23331U1 (LENOVO_MT_2333) vendor: LENOVO version: ThinkPad X230 serial: PK056K9 width: 64 bits capabilities: smbios-2.7 dmi-2.7 smp vsyscall32 configuration: administrator_password=disabled chassis=notebook family=ThinkPad X230 power-on_password=disabled sku=LENOVO_MT_2333 uuid=470dc001-5217-11cb-9533-a6ac2582edd3 *-core description: Motherboard product: 23331U1 vendor: LENOVO physical id: 0 version: Not Defined serial: 1ZSSK37N2VP slot: Not Available *-cpu description: CPU product: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 6.58.9 serial: None slot: CPU Socket - U3E1 size: 2019MHz capacity: 3300MHz width: 64 bits clock: 100MHz capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq
Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson
On Mon, 31 Jul 2023 at 21:21, Adrian Bunk wrote: > In this case Breaks would be required in both directions, otherwise a > build dependency on a new meson might result in using new meson and old > debhelper in backports. For reference we are currently discussing how to handle this. The original discussion is here: https://github.com/mesonbuild/meson/pull/11530#discussion_r1139247133
Bug#1042844: elinks: FTBFS with Perl 5.38: error: redefinition of ‘struct object’
Source: elinks
Version: 0.16.1.1-4
Severity: important
Tags: ftbfs sid trixie fixed-upstream
Forwarded: https://github.com/rkd77/elinks/pull/243
User: debian-p...@lists.debian.org
Usertags: perl-5.38-transition
This package fails to build from source with Perl 5.38 (currently in
experimental.)
http://perl.debian.net/rebuild-logs/perl-5.38/elinks_0.16.1.1-4/elinks_0.16.1.1-4+b1_amd64-2023-07-01T14:49:32Z.build
FAILED: src/elinks.p/scripting_perl_core.c.o
cc -Isrc/elinks.p -Isrc -I../src -I. -I.. -I/usr/include/p11-kit-1
-I/usr/include/lua5.3 -I/usr/local/include
-I/usr/lib/x86_64-linux-gnu/perl/5.38/CORE -fdiagnostics-color=always -Wall
-Winvalid-pch '-DGETTEXT_PACKAGE="elinks"' '-DBUILD_ID=""' -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -isystem /usr/include/mit-krb5
-Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -fno-strict-aliasing
-Wno-address -Wno-builtin-declaration-mismatch -Wc++-compat -MD -MQ
src/elinks.p/scripting_perl_core.c.o -MF src/elinks.p/scripting_perl_core.c.o.d
-o src/elinks.p/scripting_perl_core.c.o -c ../src/scripting/perl/core.c
In file included from /usr/lib/x86_64-linux-gnu/perl/5.38/CORE/perl.h:4530,
from ../src/scripting/perl/core.h:6,
from ../src/scripting/perl/core.c:16:
/usr/lib/x86_64-linux-gnu/perl/5.38/CORE/sv.h:285:8: error: redefinition of
‘struct object’
285 | struct object {
|^~
In file included from ../src/config/options.h:4,
from ../src/intl/libintl.h:4,
from ../src/scripting/perl/core.c:13:
../src/main/object.h:14:8: note: originally defined here
14 | struct object {
|^~
This seems to be fixed upstream with the PR at
https://github.com/rkd77/elinks/pull/243
--
Niko Tyni nt...@debian.org
Bug#1042843: libimage-sane-perl: FTBFS with Perl 5.38: given is deprecated
Source: libimage-sane-perl Version: 5-1 Severity: important Tags: ftbfs sid trixie upstream patch Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=148487 User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package fails to build from source with Perl 5.38 (currently in experimental.) http://perl.debian.net/rebuild-logs/perl-5.38/libimage-sane-perl_5-1/libimage-sane-perl_5-1+b4_amd64-2023-06-29T01:43:33Z.build # Failed test '--device=test --test 2>&1' # at t/81_scanimage-perl.t line 41. # got: 'scanimage: scanning image of size 157x196 pixels at 8 bits/pixel [...] # ' # expected: 'given is deprecated at examples/scanimage line 125. # when is deprecated at examples/scanimage line 126. [...] Test Summary Report --- t/81_scanimage-perl.t (Wstat: 1280 (exited 5) Tests: 6 Failed: 5) Failed tests: 2-6 Non-zero exit status: 5 Files=11, Tests=341, 7 wallclock secs ( 0.05 usr 0.01 sys + 1.18 cusr 0.30 csys = 1.54 CPU) Result: FAIL There's a patch by Petr Písař in the upstream ticket. -- Niko Tyni nt...@debian.org
Bug#764252: librocket: changing from ITP to RFP
On Sun, 27 Dec 2015 13:17:00 +0100 Lucas Nussbaum wrote: > retitle 764252 RFP: librocket -- User interface middleware package based HTML and CSS > noowner 764252 > tag 764252 - pending > thanks > > Hi, > > A long time ago, you expressed interest in packaging librocket. Unfortunately, > it seems that it did not happen. In Debian, we try not to keep ITP bugs open > for a too long time, as it might cause other prospective maintainers to > refrain from packaging the software. > > This is an automatic email to change the status of librocket from ITP > (Intent to Package) to RFP (Request for Package), because this bug hasn't seen > any activity during the last 12 months. > > If you are still interested in packaging librocket, please send a mail to > with: > > retitle 764252 ITP: librocket -- User interface middleware package based HTML and CSS > owner 764252 ! > thanks > > It is also a good idea to document your progress on this ITP from time to > time, by mailing <764...@bugs.debian.org>. If you need guidance on how to > package this software, please reply to this email, and/or contact the > debian-ment...@lists.debian.org mailing list. > > Thank you for your interest in Debian, > -- > Lucas, for the QA team > > Oi boa tarde
Bug#1042842: network interface names wrong in domU (>10 interfaces)
Package: xen-utils-4.17 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are sorted primarily by the leftmost digit. so for 11 interfaces we will end up with: vifX.0 <> eth0 vifX.1 <> eth1 vifX.10 <> eth2 vifX.2 <> eth3 vifX.3 <> eth4 This was observed with linux-kernel versions 5.10.179-3 and 6.1.38-2 (all combinations of domU and dom0) and xen 4.17.1+2-gb773c48e36-1. You can find a config snippet and "xl network-list" + "ip a" command output demonstrating the issue below. Booting the host with Xen 4.14.5+94-ge49571868d-1 restored the expected behaviour. Looking for relevant changes i found commit fce6999 [0] which changes the way libxl__device_list works, but i'm not sure that's the cause of this issue. Thanks for your help, Valentin [0] http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=fce6999 Sample vif configuration (ascending MACs): vif = [ 'mac=00:16:3e:fd:83:2f,bridge=lanbr', 'mac=00:16:3e:fd:83:30,bridge=lanbr', 'mac=00:16:3e:fd:83:31,bridge=lanbr', 'mac=00:16:3e:fd:83:32,bridge=lanbr', 'mac=00:16:3e:fd:83:33,bridge=lanbr', 'mac=00:16:3e:fd:83:34,bridge=lanbr', 'mac=00:16:3e:fd:83:35,bridge=lanbr', 'mac=00:16:3e:fd:83:36,bridge=lanbr', 'mac=00:16:3e:fd:83:37,bridge=lanbr', 'mac=00:16:3e:fd:83:38,bridge=lanbr', 'mac=00:16:3e:fd:83:39,bridge=lanbr', ] dom0# xl network-list 3 Idx BE Mac Addr. handle state evt-ch tx-/rx-ring-ref BE-path 0 0 00:16:3e:fd:83:2f 0 4 -1-1/-1 /local/domain/0/backend/vif/3/0 1 0 00:16:3e:fd:83:30 1 4 -1-1/-1 /local/domain/0/backend/vif/3/1 10 0 00:16:3e:fd:83:3910 4 -1-1/-1 /local/domain/0/backend/vif/3/10 2 0 00:16:3e:fd:83:31 2 4 -1-1/-1 /local/domain/0/backend/vif/3/2 3 0 00:16:3e:fd:83:32 3 4 -1-1/-1 /local/domain/0/backend/vif/3/3 4 0 00:16:3e:fd:83:33 4 4 -1-1/-1 /local/domain/0/backend/vif/3/4 5 0 00:16:3e:fd:83:34 5 4 -1-1/-1 /local/domain/0/backend/vif/3/5 6 0 00:16:3e:fd:83:35 6 4 -1-1/-1 /local/domain/0/backend/vif/3/6 7 0 00:16:3e:fd:83:36 7 4 -1-1/-1 /local/domain/0/backend/vif/3/7 8 0 00:16:3e:fd:83:37 8 4 -1-1/-1 /local/domain/0/backend/vif/3/8 9 0 00:16:3e:fd:83:38 9 4 -1-1/-1 /local/domain/0/backend/vif/3/9 domU# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:16:3e:fd:83:2f brd ff:ff:ff:ff:ff:ff inet X.X.X.X/16 brd X.X.X.X scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fefd:832f/64 scope link valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:30 brd ff:ff:ff:ff:ff:ff 4: eth2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:39 brd ff:ff:ff:ff:ff:ff 5: eth3: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:31 brd ff:ff:ff:ff:ff:ff 6: eth4: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:32 brd ff:ff:ff:ff:ff:ff 7: eth5: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:33 brd ff:ff:ff:ff:ff:ff 8: eth6: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:34 brd ff:ff:ff:ff:ff:ff 9: eth7: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:35 brd ff:ff:ff:ff:ff:ff 10: eth8: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:36 brd ff:ff:ff:ff:ff:ff 11: eth9: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:37 brd ff:ff:ff:ff:ff:ff 12: eth10: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:16:3e:fd:83:38 brd ff:ff:ff:ff:ff:ff
Bug#1039536: closed by Julien Cristau (Re: Bug#1039536: mirror submission for mirror.nasutek.com)
Hello, Fixed the issue with the mirror not updating, seems to be odd it wasnt executing in cron. Tho how do I get the trace file to set the Maintainer value? - Original Message - From: "Debian Bug Tracking System" To: "Michael Manley" Sent: Monday, July 31, 2023 8:36:03 AM Subject: Bug#1039536 closed by Julien Cristau (Re: Bug#1039536: mirror submission for mirror.nasutek.com) This is an automatic notification regarding your Bug report which was filed against the mirrors package: #1039536: mirror submission for mirror.nasutek.com It has been closed by Julien Cristau . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Julien Cristau by replying to this email. -- 1039536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042819: spirv-llvm-translator-14, 15, 16, please mark some symbols as optional
On Tue, 1 Aug 2023 15:05:39 +0200 Andreas Beckmann wrote: On 01/08/2023 13.26, Gianfranco Costamagna wrote: > Hello, thanks for marking such 6 symbols as optional, for some reasons > in Ubuntu (lto?) they don't appear... Perfect timing, I'm just in the process of updating the symbols files for gcc-13 builds ;-) > - (arch=armel > riscv64)_ZTISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIvELN9__gnu_cxx12_Lock_policyE1EE@Base 13 c++filt decodes that to typeinfo for std::_Sp_counted_ptr_inplace >, std::allocator, (__gnu_cxx::_Lock_policy)1> (The others are "typeinfo name" and "vtable" for that symbol.) Why does pkg-kde-tools not mark them as optional automatically? At least for me this looks like a case of templinst ... Should we file a bug? I've just uploaded spirv-llvm-translator-14 with your patch applied, how long does it take until this appears and gets built in Ubuntu and we can see whether that change was sufficient? Don't know, I'm not a huge user of pkg-kde-tools... I never went into such deep details... https://launchpad.net/ubuntu/+source/spirv-llvm-translator-14/14.0.0-8 (I'll retry failed builds, I'm also in the process of building llvm-toolchain-14 and some archs will need some more days to finish) G. Andreas OpenPGP_signature Description: OpenPGP digital signature
Bug#1042671:
Hi Nicholas, thanks for your quick response and your proposal. I will give it a try in the next days and report back as soon as possible. Regards, Lutz
Bug#1042438: bisection results
# first bad commit: [1c4dfadb4611ef511816dfdfbdb37d7d100b5a4b] ArmPkg/CpuDxe: Implement EFI memory attributes protocol Reverting that from latest upstream seems to make the problem go away. But the reason is not clear to me. This commit registers a protocol, but it doesn't appear to use that protocol on its own. I wonder if the AlmaLinux bootloader stack is trying to use it?
Bug#1042463: Severity RC?
I would say this is an RC issue, as packages are automatically rejected when they shouldn't. qt6-webengine as an example. signature.asc Description: This is a digitally signed message part.
Bug#1041792: httpie
First of all package can't modify files in users' home directories which makes this bug unfixable without patching upstream somehow. Any volounteers with patch disabling version check completely? regards Bartosz Fenski
Bug#1041142: closed by Diederik de Haas (Re: Debian's BTS is not for regular user questions)
On Tue, 2023-08-01 at 02:49 +0200, AlMa wrote: > On 01.08.23 01:12, Debian Bug Tracking System wrote: > > You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile > > Precision M6700 ... and not once did you say what actual problem you > > experienced?!? > > That's wrong. > Before I posted some (not all) of the bug reports, the Dell laptop > stopped booting properly rather early; the root cause is still unknown > (though an intermediate cause is finally resolved now, the bug report is > already closed). It took me a bit to get a working console, a mouse and > network going so as to simply be able to start debugging. Some other > machines I manage had (and still have) other, less severe symptoms, > e.g., Wayland and programs depending on Wayland (e.g., “foot”) failing > to start after Debian upgrade. > > If your computer doesn't boot properly, you go one by one through every > suspicious message you find. The fact that some messages are shown as > warnings and others as errors is clearly meant to warn whoever reads > them (i.e., the admin) and make him/her concerned. By the definition of > the terms “warning” and “error”! This is a rather naive understanding of how logging is done in practice. The reality is that developers often don't know (and maybe can't know) just how severe an odd condition may be in practice. > If these messages shouldn't make the > admin concerned, well, then the journalctl shouldn't show these messages > as warnings (AFAIK, yellow) and errors (red according to `man > journalctl`). Please don't try to unload on me because of this mess; > I'm just an admin, and not even a developer. > > Therefore, please restore the bug reports you closed. I agree with Diederik's closing these bug reports. We as kernel maintainers have limited time and resources for investigating bugs, and we are certainly not able to provide individual support for users and administrators. Investigating warning messages one by one is not a priority at all. If there is still an actual problem on this machine (not just warning messages), please open *1* bug report that describes the actual problem and the log messages. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part
Bug#1042841: RM: insighttoolkit4 -- RoQA; Superseded by insighttoolkit5
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: insighttoolk...@packages.debian.org Control: affects -1 + src:insighttoolkit4 Please remove insighttoolkit4 from the archive per #1024343.
Bug#1042840: xorg: Dell E6230 missing xorg.conf after Debian 12 upgrade
Package: xorg Version: 1:7.7+23 Severity: important Dear Maintainer, Upgrade from Debian 11 desktop with little customisation. Debian 11 was up to date - standard changes to sources.list - apt update - apt upgrade After installing all new packages and rebooting, no GUI at all X server not running missing xorg.conf NOTE that running X -configure gave "error 2", though little (I can see) in log to indicate such an issue. I assume the error prevented the new conf from being used -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 4 -rw-r--r-- 1 root root 3306 Aug 1 17:27 xorg.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 6.1.0-10-686-pae (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) Xorg X server log files on system: -- -rw-r--r-- 1 root root 18997 Aug 1 16:35 /var/log/Xorg.1.log -rw-r--r-- 1 root root 23608 Aug 1 2023 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 7.456] (--) Log file renamed from "/var/log/Xorg.pid-846.log" to "/var/log/Xorg.0.log" [ 7.460] X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 [ 7.461] Current Operating System: Linux Dell-E6230 6.1.0-10-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) i686 [ 7.461] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-686-pae root=UUID=5e413918-d712-477d-b7a4-83660e15b2d2 ro quiet [ 7.461] xorg-server 2:21.1.7-3 (https://www.debian.org/support) [ 7.461] Current version of pixman: 0.42.2 [ 7.461]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 7.461] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 7.461] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 1 17:53:57 2023 [ 7.464] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 7.464] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 7.469] (==) ServerLayout "X.org Configured" [ 7.469] (**) |-->Screen "Screen0" (0) [ 7.469] (**) | |-->Monitor "Monitor0" [ 7.469] (**) | |-->Device "Card0" [ 7.469] (**) |-->Input Device "Mouse0" [ 7.469] (**) |-->Input Device "Keyboard0" [ 7.469] (==) Automatically adding devices [ 7.469] (==) Automatically enabling devices [ 7.469] (==) Automatically adding GPU devices [ 7.469] (==) Automatically binding GPU devices [ 7.469] (==) Max clients allowed: 256, resource mask: 0x1f [ 7.473] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 7.473]Entry deleted from font path. [ 7.479] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 7.479]Entry deleted from font path. [ 7.479] (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 7.479] (**) ModulePath set to "/usr/lib/xorg/modules" [ 7.479] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 7.479] (WW) Disabling Mouse0 [ 7.479] (WW) Disabling Keyboard0 [ 7.479] (II) Loader magic: 0x7027a0 [ 7.479] (II) Module ABI versions: [ 7.479]X.Org ANSI C Emulation: 0.4 [ 7.479]X.Org Video Driver: 25.2 [ 7.479]X.Org XInput driver : 24.4 [ 7.479]X.Org Server Extension : 10.0 [ 7.480] (++) using VT number 7 [ 7.480] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 7.483] (II) xfree86: Adding drm device (/dev/dri/card0) [ 7.483] (II) Platform probe for /sys/devices/pci:00/:00:02.0/drm/card0 [ 7.497] (--) PCI:*(0@0:2:0) 8086:0166:1028:0532 rev 9, Mem @ 0xf640/4194304, 0xe000/268435456, I/O @ 0xf000/64, BIOS @
Bug#1032647: Keeping 525.105.17-1 for bookworm?
On 26/05/2023 20.04, julienbenja...@free.fr wrote: Since Debian 12 entered in full freeze, I guess this issue will stay open for the entirety of Bookwork lifetime? Nope, bookworm will see new driver releases (usually fixing CVEs). Bookworm now has 525.125.06-1~deb12u1 - does this fix the issue? At some point we will be updating bookworm to the 535 series which is a new LTSB branch and supported for the lifetime of bookworm. But that is not yet in sid or even experimental. Andreas
Bug#1042827: priv-wrapper?
Hi I have finished packaging cwrap's priv-wrapper: https://salsa.debian.org/jas/priv-wrapper/ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042827 Would you be interested in co-maintaining priv-wrapper in the SSSD group? I noticed that SSSD maintains some of the other cwrap projects: https://tracker.debian.org/pkg/nss-wrapper https://tracker.debian.org/pkg/pam-wrapper https://tracker.debian.org/pkg/uid-wrapper I'm happy to maintain priv-wrapper in the sssd-group, and help improve packaging of other SSSD packages (e.g, upload new releases), if you grant me access to the Salsa gitlab group. /Simon signature.asc Description: PGP signature
Bug#1042839: xserver-xorg-video-radeon: modprobe radeon reboots the machine randomly then the usb mouse does not work on Xorg on restart
Package: xserver-xorg-video-radeon Version: 1:19.1.0-3~bpo11+1 Severity: important Dear Maintainer, When Debian starts, it reboots randomly at the moment when the radeon module is enabled. This occurs 3 times of 4 on normal boot mode and about 1 time of 3 on maintenance boot mode. Then the USB mouse does not work on Xorg. When the boot works fine and modprobe radeon is well enabled, all works fine. When I run the BIOS settings page in graphics mode and with the mouse, the BIOS works fine, then if I reboots, all work fine always. If I run Linux Mint from a USB key and then I reboots on Debian, all works fine always. A compilation of xserver-xorg-video-radeon to backport from 1:19.1.0-2 to the 1:19.1.0-3 release does not fix the issue. Expected: the system should not reboot when the radeon was enabled. Note: These bottom logs are done when the system works fine. Regards. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 10 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Mar 23 11:25 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7480D] [1002:9993] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 4 -rw-r--r-- 1 root root 97 Nov 28 2020 50-dimensions-af.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 6.1.0-0.deb11.9-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1~bpo11+1 (2023-04-23) Xorg X server log files on system: -- -rw-r--r-- 1 root root 33355 Nov 2 2020 /var/log/Xorg.2.log -rw-r--r-- 1 alain alain 33480 Jul 22 09:52 /home/alain/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 alain alain 46097 Jul 30 16:42 /home/alain/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 32602 Aug 1 15:59 /var/log/Xorg.1.log -rw-r--r-- 1 root root 37674 Aug 1 17:35 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [29.663] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [29.663] Build Operating System: linux Debian [29.663] Current Operating System: Linux chro 6.1.0-0.deb11.9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1~bpo11+1 (2023-04-23) x86_64 [29.663] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-0.deb11.9-amd64 root=UUID=5ebf0513-8146-4896-b3bc-9a9923f0cf81 ro quiet [29.663] Build Date: 23 March 2023 10:25:56AM [29.663] xorg-server 2:1.20.11-1+deb11u6 (https://www.debian.org/support) [29.663] Current version of pixman: 0.40.0 [29.663]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [29.663] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [29.664] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 1 17:34:59 2023 [29.824] (==) Using config directory: "/etc/X11/xorg.conf.d" [29.824] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [30.110] (==) No Layout section. Using the first Screen section. [30.110] (==) No screen section available. Using defaults. [30.110] (**) |-->Screen "Default Screen Section" (0) [30.110] (**) | |-->Monitor "" [30.121] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [30.121] (==) Automatically adding devices [30.121] (==) Automatically enabling devices [30.121] (==) Automatically adding GPU devices [30.121] (==) Max clients allowed: 256, resource mask: 0x1f [30.366] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [30.367]Entry deleted from font path. [30.381] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [30.381] (==) ModulePath set to "/usr/lib/xorg/modules" [30.381] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [30.381] (II) Loader magic: 0x559b53570e40 [30.381] (II) Module ABI versions: [30.381]X.Org ANSI C Emulation: 0.4 [30.381]X.Org Video Driver: 24.1 [30.381]X.Org XInput driver : 24.1 [30.381]X.Org Server Extension : 10.0 [30.382] (++)
Bug#1042838: selinux-basics: selinux-config-enforcing should explicitely set mode of /etc/selinux/config
Package: selinux-basics Version: 0.5.8 Severity: important Tags: patch /etc/selinux/config needs to be world-readable so user space object managers running as non-root can find the SELINUXTYPE, otherwise they default to targeted which is the source of error messages about /etc/selinux/targeted/contexts being unavailable. In some situations this can prevent a graphical login. As a combination of a umask such as 027 and running the script as-is will cause things to break unexpectedly (including systemd processes run for the user) this might be worth an update to bookworm. The fix is to add the following line to the end of the file: chmod 644 $CONF -- System Information: Debian Release: 12.1 Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages selinux-basics depends on: ii checkpolicy 3.4-1+b2 ii perl 5.36.0-7 ii policycoreutils 3.4-1 ii python3 3.11.2-1+b1 ii selinux-utils3.4-1+b6 Versions of packages selinux-basics recommends: ii policycoreutils-python-utils 3.4-1 ii selinux-policy-default2:2.20230710-1 ii setools 4.4.1-2 Versions of packages selinux-basics suggests: pn logcheck pn syslog-summary -- debconf-show failed
Bug#1040730: khronos-opencl-clhpp: autopkgtest failure due to new CMake deprecation warning
Hi, On Sun, 09 Jul 2023 23:03:05 +0200 roehl...@debian.org wrote: your package khronos-opencl-clhpp will soon experience autopkgtest failures because the new CMake release 3.27 will issue a deprecation warning on stderr if cmake_minimum_required() asks for compatibility with CMake 3.4 or older. I have uploaded an NMU to DELAYED/5 now (see attached diff). Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ diff --git a/debian/changelog b/debian/changelog index 4890a5a..975b170 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +khronos-opencl-clhpp (3.0~2023.04.17-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Bump cmake_minimum_required() in autopkgtest (Closes: #1040730) + + -- Timo Röhling Tue, 01 Aug 2023 18:04:04 +0200 + khronos-opencl-clhpp (3.0~2023.04.17-1) unstable; urgency=medium * New upstream release. diff --git a/debian/tests/upstream-testsuite b/debian/tests/upstream-testsuite index f6786ed..501bfb0 100644 --- a/debian/tests/upstream-testsuite +++ b/debian/tests/upstream-testsuite @@ -5,6 +5,14 @@ srcdir=$(pwd) cp -a . $AUTOPKGTEST_TMP cd $AUTOPKGTEST_TMP +# Temporary fix for #1040730 +sed -i -e '1 s/VERSION [^)]*/VERSION 3.13/' \ + CMakeLists.txt \ + examples/CMakeLists.txt \ + tests/strip_defines.cmake \ + tests/pkgconfig/bare/CMakeLists.txt \ + tests/pkgconfig/sdk/CMakeLists.txt +# End of temporary fix mkdir build cd build cmake -DOPENCL_LIB_DIR=/usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH) -DCMOCK_DIR=../cmock -DUNITY_DIR=../unity .. signature.asc Description: PGP signature
Bug#1042713: wireplumber: High cpu usage
El 2023-08-01 11:22 PYT, Dylan Aïssi escribió: > Do you have pipewire-libcamera installed? If yes, can you remove it? "pipewire-libcamera" doesn't appear anywhere under /var/log/apt so I think it's never been installed. > Can you provide log from pipewire and wireplumber as explained here [1]? I'm attaching the result of $ journalctl --user-unit=pipewire --user-unit=wireplumber \ --user-unit=pipewire-pulse --since="2023-07-29" \ --until="2023-07-30" > log1.txt which I think includes the result of my first boot into debian 12, soon followed by my killing wireplumber. Hope that helps. > Best regards, > Dylan Thanks for replying, I'll try to supply more if needed. -- Nick Asunción 12:03 PYT ► 30.7°C ◆ cielo claro ◆ 22Km/h NNE ◆ 40% HR Jul 29 10:45:59 argon systemd[1380]: Stopping Multimedia Service... Jul 29 10:45:59 argon pipewire-media-session[1419]: error id:0 seq:164 res:-32 (Broken pipe): connection error Jul 29 10:45:59 argon systemd[1380]: pipewire.service: Succeeded. Jul 29 10:45:59 argon systemd[1380]: Stopped Multimedia Service. Jul 29 10:45:59 argon systemd[1380]: pipewire.service: Consumed 40.688s CPU time. -- Boot 1fda9ee2cfc54a14bbab068213dac2d7 -- Jul 29 10:46:53 argon systemd[1422]: Started pipewire.service - PipeWire Multimedia Service. Jul 29 10:46:53 argon systemd[1422]: Started wireplumber.service - Multimedia Service Session Manager. Jul 29 10:46:53 argon systemd[1422]: Started pipewire-pulse.service - PipeWire PulseAudio. Jul 29 10:46:53 argon pipewire[1438]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? Jul 29 10:46:53 argon pipewire-pulse[1440]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? Jul 29 10:46:53 argon pipewire-pulse[1440]: mod.rt: found session bus but no portal Jul 29 10:46:53 argon pipewire[1438]: mod.rt: found session bus but no portal Jul 29 10:46:53 argon wireplumber[1439]: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? Jul 29 10:46:53 argon wireplumber[1439]: found session bus but no portal Jul 29 10:46:54 argon wireplumber[1439]: Failed to set scheduler settings: Operation not permitted Jul 29 10:46:54 argon wireplumber[1439]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed? Jul 29 10:46:54 argon wireplumber[1439]: PipeWire's libcamera SPA missing or broken. libcamera not supported. Jul 29 10:46:54 argon wireplumber[1439]: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed? Jul 29 10:46:54 argon wireplumber[1439]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported. Jul 29 10:46:54 argon wireplumber[1439]: Object activation aborted: proxy destroyed Jul 29 10:46:54 argon wireplumber[1439]: failed to activate item: Object activation aborted: proxy destroyed Jul 29 10:53:05 argon wireplumber[1439]: stopped by signal: Terminated Jul 29 10:53:05 argon wireplumber[1439]: disconnected from pipewire Jul 29 10:53:05 argon systemd[1422]: wireplumber.service: Consumed 5min 6.906s CPU time.
Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)
Using -x instead of -m when verifying gives "interesting" output: $ signify-openbsd -Vz -p s3ql-5.0.pub -x signed.gz untrusted comment: verify with s3ql-5.0.pub RWSKPEtoJRYfrolP1xcoVCAxdIGvBp+I600+z5r4Ckcknx45J4pGrYvhlrWn6WTtwom7mTyjT7epM/oQyhfn/UbuKTR7pjN+0g0= date=2023-08-01T16:10:04Z key=s3ql-5.0.sec algorithm=SHA512/256 blocksize=65536 05b894ec8534324eda46e2c71b2e9cd8c3e6f89432d222d06949076bc5236998 Ke2~⏎ This terminates with exit code 0... but somehow I'm not convinced that signify did the right thing here. Best, -Nikolaus
Bug#1042789: rust-futures-macro: Please update to v0.3.28
Control: affects -1 rust-futures-util rust-futures-executor rust-futures Quoting Jonas Smedegaard (2023-08-01 00:10:08) > Source: rust-futures-macro > Version: 0.3.21-1 > Severity: normal > Tags: upstream > > Please update to (at least) newer upstream release v0.3.28. This is now blocking build of rust-futures-util rust-futures-executor rust-futures. Just mentioning because it seems this was missed when updating a slew of other future* crates. Thanks, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1035026: singularity-container: CVE-2023-30549
Hi Nilesh, On Tue, Aug 01, 2023 at 09:33:16PM +0530, Nilesh Patra wrote: > On Tue, Aug 01, 2023 at 05:10:10PM +0200, Salvatore Bonaccorso wrote: > > On Tue, Aug 01, 2023 at 07:57:22PM +0530, Nilesh Patra wrote: > > > I asked this upstream[1] and upstream thinks that this is actually an > > > issue with the kernel filesystem itself, and this is not a singularity > > > issue per se. They even have a blogpost about the same giving more > > > details on the CVE. I suppose there's nothing I can do as a package > > > maintainer to act upon the bug. > > > > > > I've also CC'ed David (upstream) to this mail, to keep them in the loop > > > as well. > > > > > > What do you think? > > > > Okay I see there is disagreement on the Apptainer project on Sylabs on > > this and understand the reasoning outlined in the response blogpost. I > > will mark the CVE entry as unimportant and add a rationale for it, in > > particular because for the suites where singularity-container is > > available, the known CVE-2022-1184 is patched. > > Thank you! > > > The Apptainer rationale > > is as explained though more broad and not referring only to this known > > CVE. > > > > Given that, I'm fine if you close the bugreport following the upstream > > response to their view on CVE-2023-30549. > > > > What you could do as packager, once this configuration option in a new > > security-container is available to put it in reference with > > CVE-2023-30549, maybe. > > I think this was introduced in version 3.11.2 as per the changelog > mention > > > https://github.com/sylabs/singularity/blob/main/CHANGELOG.md#3112-2023-04-27 > > However, I had already uploaded 3.11.4 to unstable before I saw this bug > report, sorry about that. I'll mention this in the bookworm-fasttrack upload > in that case. Ah perfect. I ammended the entry again and considering the issue fixed from our persective with 3.11.4+ds1-1 plus a reference to the upstrema changelog entry. > > > > Note: If I do not hear from you in a week, I'll close this bug report. > > > > Quite tight pressure given there is as well general > > I wanted to upload this to bookworm before next week. To my surprise, > there are actually users consuming this package from there, so I just > wanted to make it a little quick :) Was all not that serious, but wanted to put away some time pressure from me on the decision making. All good. > > summer vacation times ;-) > > There are _currently_ no summer vacation times in the part of the world I > live in. > It was infact, raining quite heavily since past few days, so I didn't > realise the vac stuff for you :-) Ah right :) Regards, Salvatore
Bug#1042823: Cannot log into SLBackup web frontend with sshd default configuration
On Tue, Aug 01, 2023 at 02:52:38PM +0200, Guido Berhoerster wrote: > The Debian openssh-server disables login as root using a password by > default. As noted in the DebianEdu documentation this must be > changed manually for the SLBackup web frontend to work: > > > Note: the site will only work if you temporarily allow SSH root login on > > the backup server, which is the main server (tjener.intern) by default. > > I'm wondering whether we should allow password-based logins from > localhost by default? E.g. through a drop in file > /etc/ssh/sshd_config.d/debia-edu.conf: can't we teach slbackup to work with ssh-key authentication? it's 2023. > Match Address 127.0.0.1,10.0.2.2 10.0.2.2 is not localhost. :) -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ We live in a world where teenagers get more and more desperate trying to convince adults to behave like grown ups. signature.asc Description: PGP signature
Bug#1035026: singularity-container: CVE-2023-30549
On Tue, Aug 01, 2023 at 05:10:10PM +0200, Salvatore Bonaccorso wrote: > On Tue, Aug 01, 2023 at 07:57:22PM +0530, Nilesh Patra wrote: > > I asked this upstream[1] and upstream thinks that this is actually an > > issue with the kernel filesystem itself, and this is not a singularity > > issue per se. They even have a blogpost about the same giving more > > details on the CVE. I suppose there's nothing I can do as a package > > maintainer to act upon the bug. > > > > I've also CC'ed David (upstream) to this mail, to keep them in the loop > > as well. > > > > What do you think? > > Okay I see there is disagreement on the Apptainer project on Sylabs on > this and understand the reasoning outlined in the response blogpost. I > will mark the CVE entry as unimportant and add a rationale for it, in > particular because for the suites where singularity-container is > available, the known CVE-2022-1184 is patched. Thank you! > The Apptainer rationale > is as explained though more broad and not referring only to this known > CVE. > > Given that, I'm fine if you close the bugreport following the upstream > response to their view on CVE-2023-30549. > > What you could do as packager, once this configuration option in a new > security-container is available to put it in reference with > CVE-2023-30549, maybe. I think this was introduced in version 3.11.2 as per the changelog mention https://github.com/sylabs/singularity/blob/main/CHANGELOG.md#3112-2023-04-27 However, I had already uploaded 3.11.4 to unstable before I saw this bug report, sorry about that. I'll mention this in the bookworm-fasttrack upload in that case. > > Note: If I do not hear from you in a week, I'll close this bug report. > > Quite tight pressure given there is as well general I wanted to upload this to bookworm before next week. To my surprise, there are actually users consuming this package from there, so I just wanted to make it a little quick :) > summer vacation times ;-) There are _currently_ no summer vacation times in the part of the world I live in. It was infact, raining quite heavily since past few days, so I didn't realise the vac stuff for you :-) Best, Nilesh signature.asc Description: PGP signature
Bug#1042837: signify-openbsd: Embedding signature in gz header does not work
Package: signify-openbsd Version: 31-3 Severity: normal Dear Maintainer, I believe this should work, but it does not: $ signify-openbsd -Sz -s signify/s3ql-5.0.sec -m dist/s3ql-5.1.0.tar.gz -x out.gz $ signify-openbsd -Vz -m out.gz -p signify-s3ql-5.0.pub signify-openbsd: can't open out.gz.sig for reading: No such file or directory Am I holding this wrong? -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages signify-openbsd depends on: ii libbsd0 0.11.7-2 ii libc62.36-9+deb12u1 signify-openbsd recommends no packages. Versions of packages signify-openbsd suggests: pn signify-openbsd-keys -- no debconf information
Bug#1042065: ltrace: [p]{read,write}[v]() handling, common *64() functions in modern glibc, [fl]seek[o]()/ftell[o](); requisite [u]llong; 20x speed optimisation in default config; format %b+bin() lens
Control: retitle -1 ltrace: [p]{read,write}[v]() handling, common *64()
functions in modern glibc, [fl]seek[o]()/ftell[o](); requisite [u]llong; 20x
speed optimisation in default config; format %b+bin() lens and %w[f]32x;
splice/c_f_r/sendfile[64] formatting; useful __errno_location
Attaching two patches that turn
splice(3, 0x7ffca660acd8, 1, 0)
= -1
copy_file_range(3, 0x7ffca660acd8, 1, 0)
= -1
sendfile64(1, 3, 0x7ffca660acd8, 0x40)
= -1
pread64(3
error: maximum array length seems negative
, "", 65536, -65536)
= -1
__errno_location()
= 0x7f5347bb86c0
__errno_location()
= 0x7f5347bb86c0
strerror(22)
= "Invalid argument"
fprintf(0x7f5347d8e680, "%s: %s: %s\n", "out/cmd/tail", "5M", "Invalid
argument") = 35
close(3)
= 0
__cxa_finalize(0x561787e1efd8)
=
+++ exited (status 1) +++
into
splice(3, -65536, 1, nil, 4194304, 0b101)
= -1
copy_file_range(3, -65536, 1, nil, 4194304, 0)
= -1
sendfile64(1, 3, -65536, 4194304)
= -1
pread64(3
error: maximum array length seems negative
, "", 65536, -65536)
= -1
__errno_location()
= 22
__errno_location()
= 22
strerror(22)
= "Invalid argument"
fprintf(0x7f2b0401c680, "%s: %s: %s\n", "out/cmd/tail", "5M", "Invalid
argument") = 35
close(3)
= 0
__cxa_finalize(0x55ba48e1cfd8)
=
+++ exited (status 1) +++
From: =?utf-8?b?0L3QsNCx?=
Date: Tue, 1 Aug 2023 17:09:11 +0200
Subject: Add splice()/copy_file_range()/sendfile[64]()
Before:
splice(3, 0x7ffd4b66f348, 1, 0)= -1
copy_file_range(3, 0x7ffd772bbf28, 1, 0) = -1
sendfile64(1, 3, 0x7ffd772bbf28, 0x40) = -1
pread64(3
error: maximum array length seems negative
, "", 65536, -65536) = -1
After:
splice(3, -65536, 1, nil, 4194304, 0b101) = -1
copy_file_range(3, -65536, 1, nil, 4194304, 0) = -1
sendfile64(1, 3, -65536, 4194304) = -1
pread64(3
error: maximum array length seems negative
, "", 65536, -65536) = -1
---
etc/ltrace.conf | 6 ++
1 file changed, 6 insertions(+)
diff --git a/etc/ltrace.conf b/etc/ltrace.conf
index 855d373..db914cb 100644
--- a/etc/ltrace.conf
+++ b/etc/ltrace.conf
@@ -60,6 +60,12 @@ int open(string,hex(int),octal); ; WARNING: 3rd argument may not be there
int open64(string,hex(int),octal); ; WARNING: 3rd argument may not be there
int openat(openat_fd,string,hex(int),octal); ; WARNING: 4th argument may not be there
int openat64(openat_fd,string,hex(int),octal); ; WARNING: 4th argument may not be there
+long splice(int,llong*,int,llong*,ulong,bin(uint))
+; unistd.h
+long copy_file_range(int,llong*,int,llong*,ulong,bin(uint))
+; sys/sendfile.h
+long sendfile(int,int,long*,ulong)
+long sendfile64(int,int,llong*,ulong)
; fnmatch.h
int fnmatch(string, string, int);
From: =?utf-8?b?0L3QsNCx?=
Date: Tue, 1 Aug 2023 17:30:15 +0200
Subject: __errno_location() returns an int*, not addr
This means that before:
__errno_location() = 0x7f2707f256c0
__errno_location() = 0x7f2707f256c0
__errno_location() = 0x7f2707f256c0
After:
__errno_location() = 0
__errno_location() = 22
__errno_location() = 22
And this __errno_location() is made useful
---
etc/ltrace.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/etc/ltrace.conf b/etc/ltrace.conf
index db914cb..3d4f5cd 100644
--- a/etc/ltrace.conf
+++ b/etc/ltrace.conf
@@ -52,7 +52,7 @@ addr dlsym(addr, string);
int dlclose(addr);
; errno.h
-addr __errno_location();
+int* __errno_location();
;
Bug#1034358: libvncclient1: license conflict with libsasl2
Control: severity -1 important The RSA-MD license is gone from cyrus-sasl's binaries now, so derivative works can ignore it. For BSD-3-Clause-Attribution, the incompatibility case is not as strong, so I am lowering the severity.
Bug#1042836: tomcat9: tomcat user has non-existent home directory /var/lib/tomcat
Source: tomcat9 Version: 9.0.70-2 Severity: normal Hi, in #926338 the home directory for the tomcat user has been set (from /) to /var/lib/tomcat, however this directory is not created during install. As the home directory is indeed needed in some cases as described in #926338, it would be nice to have it automatically created. Having a non-existant home directory, still leaves a non-working setup these cases after installation and is least slightly confusing. Best wishes Matthias P.S.: There is also a bug report for Ubuntu mentioning the missing home directory as well as the missing write permissions to that directory in the unt file: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/2000593 -- System Information: Debian Release: 12.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1032001: RM: bzrtools -- RoQA; transitional package since bullseye
Control: reassign -1 ftp.debian.org On Sun, 26 Feb 2023 13:16:07 +0100 Bastian Germann wrote:> The bzrtools package can be removed because it was a transitional package for one release. Please reassign to ftp.debian.org if you agree. This also goes for the bzr-* packages. bzrtools has been a transitional package for two releases now. Please remove it.
Bug#1042713: wireplumber: High cpu usage
Le lun. 31 juil. 2023 à 00:21, Nick a écrit : > > On rebooting, a process called wireplumber consumes most of the cpu. > Sound does work. If I kill the process, cpu usage falls, my fan stops > spinning and I no longer have sound. I have to kill wireplumber on > each reboot (or let it try to fry my cpu). Do you have pipewire-libcamera installed? If yes, can you remove it? Can you provide log from pipewire and wireplumber as explained here [1]? Best regards, Dylan [1] https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#general
Bug#995838: [htcondor-debian] Bug#995838: Bug#995838: Should condor be removed?
Hi Tim, I see you imported 10.3 into Debian. Please let me know if I can help you. Thanks, Bastian On Fri, 2 Dec 2022 09:03:27 -0600 Tim Theisen wrote: Hello Bastian, I am working on this. Twice I had everything building and ready for upload and then something changed on sid. First change, moving to openssl 3 caused condor to FTBFS. Then migration to cgroups v2 caused condor to FTBFS. Right now I have it building. However, some change is causing the install step to not place files in the proper directories. Perhaps, something to do with usrmerge or some change in the build tools. Still working on that one. ...Tim On 11/30/22 11:05, Bastian Germann wrote: > X-Debbugs-Cc: andr...@an3as.eu > > Any news on condor? Upstream has released the announced version but > the Debian package has only advanced in git.
Bug#1035026: singularity-container: CVE-2023-30549
Hi On Tue, Aug 01, 2023 at 07:57:22PM +0530, Nilesh Patra wrote: > Hi Salvatore, > > On Thu, 27 Apr 2023 22:06:36 +0200 Salvatore Bonaccorso > wrote: > > Source: singularity-container > > Version: 3.11.0+ds1-1 > > Severity: important > > Tags: security upstream > > The following vulnerability was published for singularity-container. > > The issue originally reference for apptainer is affecting in same way > > singularity. > > > > CVE-2023-30549[0]: > > ... > > I asked this upstream[1] and upstream thinks that this is actually an > issue with the kernel filesystem itself, and this is not a singularity > issue per se. They even have a blogpost about the same giving more > details on the CVE. I suppose there's nothing I can do as a package > maintainer to act upon the bug. > > I've also CC'ed David (upstream) to this mail, to keep them in the loop > as well. > > What do you think? Okay I see there is disagreement on the Apptainer project on Sylabs on this and understand the reasoning outlined in the response blogpost. I will mark the CVE entry as unimportant and add a rationale for it, in particular because for the suites where singularity-container is available, the known CVE-2022-1184 is patched. The Apptainer rationale is as explained though more broad and not referring only to this known CVE. Given that, I'm fine if you close the bugreport following the upstream response to their view on CVE-2023-30549. What you could do as packager, once this configuration option in a new security-container is available to put it in reference with CVE-2023-30549, maybe. > Note: If I do not hear from you in a week, I'll close this bug report. Quite tight pressure given there is as well general summer vacation times ;-) Regards, Salvatore
Bug#1042835: rust-rkyv-derive: Please update to v0.7.41
Source: rust-rkyv-derive Version: 0.7.39-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to (at least) newer upstream release v0.7.41. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTJHnkACgkQLHwxRsGg ASFNyA//UWqNzf5bnoPoheaqVdtivEfT9CLJJ5R0iJZ1uz+WTtoaBrwIJQcK9u11 mpZcH5aoovraESSvzM5BkCT3PSZk9ss9t8kTAqvNpCIvV1MRZwrZMYsKCy3yuWOy P+01JLXoV7a7l1SzvXnsi+2kLY58tCrR7yfM6ErSL9VPCRxYBLYCJfoQFb+3kRb+ smj5tijKV2g8IBXNFozgsJgWepozK+UIty5r8i0NRb8jFJ2fYBC54ulXHAz+SdnX zTu5RpL+0ZZ7JHUKE/ZD9AQAZbdGSx/OqbCtMYx80i03wD/6Zm2KF9v3F5jNZMxu kicPm/RBdkqmluEObNNfhGa8Np2w/viCWrd/I4q8HWzFwNIZ9ILvfh4pKps/378S ezMl+WLiGkSxWgaYIWP+DNjnwZG4d/OyufvHQ8M88Ocy2yObEONEe5us482V9a0m YJwG5yaWCFcbd3WuQ0UO2Eh+3BUNIGGm7QoOWS6mIg8xPT/RZ/buckT8BepMWtDz W+d8Qvn9GnWOy5Y4Fd9wPNcb7HDJizkxonWtCQg0Ljzm+f2o2IpoptSKDASCWi5R BaJDHMXFoF0JSUjB/SOsdRj+AMGay6cMn6Mvi+Ru+Psm/y9sa35gWW6tHl5LIsYN 0aoQ4vjspJQKvdZBZNumtedDhTG4ne8nWH9gnNsRkgf17q27lQI= =++Dt -END PGP SIGNATURE-
Bug#1042834: rust-rkyv: Please update to v0.7.42
Source: rust-rkyv Version: 0.7.39-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to (at least) newer upstream release v0.7.42. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTJHiwACgkQLHwxRsGg ASHQbQ/+MPKFTPVjLQTDlrhXxHM6A+2AmbylTNMRSeF5auMCKo3bVBLYSY5ruOaC gj10iNZcEIJUT9etcL/wxVlKPNh5T1ukyQaFFdsPNFf8D1xouiJF92/cUpIFUEBg 8MAgAW2L/F2FcZiktkx9TfPDnc5GQ5aP59nZN6nKNEUcmvkDqzdzo1Y71pKQzWOd c2iXZ3KL+epxty9WOAiV74FPX90M7qS55lJn9Ihss17Rq/JZH1zc6/f4CZSsZJos PU3TcJpnq7hlNrcYV7zeCjkXRKUN+nO29e+lcOgLPZOiMjP9TcbXXTotSgQsCESx yNVUHObNfDOUZCGVDVBkeGHQEkWqwSTK3c1MddoMjFtR5ThOhqXJvPpRVcotvenA SaDQStBRu97HfrZ0PADx1axaG4FynERO1EzwSi83JOAve4sz2iPXaZO1XQHzjW0b C85Z7S3vG4oYXDOAcYHeJ/tpBf9lqCrrQVOB4VNmREvj7Nrhrc/mnIsGXBdLnQRq 04I+yB0Sap72RUiIg5Ii0757MUyKxnO8LBV9w3CQW4oLNvV3+t2TZ9OWEiSP9/if zibbiqBKynK1k5M7uDRnaWYvtSBlYP1ZpANegRWwp9ZiVVVIxPIfjyHaJwsGlkoj ROXrhmpjzf2swdV/PVoUNBM/0YsvrKdP+vauT3f7VlX2uiljbJY= =MSjc -END PGP SIGNATURE-
Bug#1041141: kernel: pmd_set_huge: Cannot satisfy [mem 0x…-0x…] with a huge-page mapping due to MTRR override.
On 01.08.23 10:50, Diederik de Haas wrote: On Tuesday, 1 August 2023 02:53:19 CEST AlMa wrote: and my own educated guess: Disable the ASPEED device and see what happens Any hint on how to do it on the linux command line in grub? Please read http://www.catb.org/esr/faqs/smart-questions.html The "Before You Ask" section lists (among others) the following: 2. Try to find an answer by searching the Web. 3. Try to find an answer by reading the manual. You said you're managing several hardware devices, so I would also expect (and the device manual will undoubtedly tell you) that the most logical place to disable build-in hardware would be the BIOS ... Probably a bad idea. This would prevent seeing anything right from the beginning in case the monitor connected to the NVIDIA graphic cards stops showing stuff for whatever reason. After the 7 item list, that document says the following: "When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time." So please read and apply the document I linked above. I won't be wasting my time on your issues though. Don't upbraid me for no good reason; better rail at the bugs themselves. I don't see folks really retypesetting all the Web search queries they run. If I would have exposed some of the research I did, I would have run the risk of introducing typos while retypesetting; nobody is immune against errors of all kinds. Anyway, I don't expose folks to potentially useless material. Having said that, I kindly ask for understanding that, responding to your ranting and raving, I won't be wasting my time on replying to psychological issues you apparently have.
Bug#1038405: Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74
On 31 July 2023 at 23:13, Adrian Bunk wrote: | On Mon, Jun 19, 2023 at 04:37:22PM +0300, Adrian Bunk wrote: | > On Tue, Jun 13, 2023 at 03:30:18PM -0500, Dirk Eddelbuettel wrote: | > > | > > On 13 June 2023 at 13:15, Steve Langasek wrote: | > > | Control: reassign -1 r-cran-rstan r-cran-bh | > > | Control: found -1 r-cran-rstan/2.21.8-1 | > > | | > > | Unfortunately, at least in Ubuntu it appears the r-cran-rstan build still | > > | exhausts the 32-bit memory space even with boost 1.81. | > > | | > > | https://launchpad.net/ubuntu/+source/r-cran-rstan/2.21.8-1/+build/26010118 | > > | > > :-/ | > > | > > Not sure that it is fair to point at BH / Boost though. Anyway. | > > | > > CRAN no longer checks / compiles 32 bit so upstream may not care, but they | > > are a good team (if busy). You could ping Ben, he is at | > >Benjamin K Goodrich | > >... | > | > The patch below to r-base fixes the build of r-cran-rstan/i386 for me. | > | > This will reduce debug info in the R ecosystem on 32bit to what is | > required for backtraces, but I assume realistically R on 32bit is | > anyway only sparsely used these days. | > | > > Dirk | > | > cu | > Adrian | > | > --- debian/rules.old2023-06-18 19:45:14.437261923 + | > +++ debian/rules2023-06-18 19:51:30.097179612 + | > @@ -90,6 +90,11 @@ | > export DEB_CFLAGS_MAINT_APPEND = -ffloat-store | > endif | > | > +## fewer debug info on 32bit to workaround 2-4 GB address space limitation | > +ifeq ($(DEB_HOST_ARCH_BITS), 32) | > +export DEB_CFLAGS_MAINT_APPEND += -g1 | > +endif | > + | >... | | These two entries ended up in the opposite order in the upload, and the | -ffloat-store one did not have a += making the -g1 change a nop on i386. | | Please apply also the patch below. | | cu | Adrian | | --- debian/rules.old 2023-07-26 07:56:06.872438302 + | +++ debian/rules 2023-07-26 07:56:27.340457680 + | @@ -92,7 +92,7 @@ | | ## Adrian Bunk 20 Jan 2023 workaround excess precision of x87 | ifneq (,$(filter $(DEB_HOST_ARCH), i386)) | -export DEB_CFLAGS_MAINT_APPEND = -ffloat-store | +export DEB_CFLAGS_MAINT_APPEND += -ffloat-store | endif | | ## edd 31 Mar 2014 Flim! Thanks for catching that, that's what I get for manually patching. Will fix now. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1036110: qemu-system-*: license conflict with libsasl2
Control: severity -1 important On Mon, 15 May 2023 21:17:15 +0300 Michael Tokarev wrote: Also for the RSA-MD license (which has stronger attribution clause), the 4 files in cyrus-sasl which are covered by it should just be deleted and replaced with equivalent implementations which is done by everyone else. This was done in the latest cyrus-sasl2 package version. As RSA-MD was the strong offender and the case is not as clear cut for BSD-3-Clause-Attribution, I am lowering the severity.
Bug#1036113: libpurple0: license conflict with libsasl2
Control: severity -1 important On Sun, 23 Jul 2023 22:42:26 +0200 Evangelos Ribeiro Tzaras wrote: Fyi: that issue has now been closed with https://github.com/cyrusimap/cyrus-sasl/pull/770 The backport to Debian was done. I am no longer considering this a serious issue as the clearly GPL-incompatible RSA-MD is gone from cyrus-sasl2's binaries with the latest version.
Bug#1042833: rust-nom: Please update to v7.1.3
Source: rust-nom Version: 7.1.1-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to (at least) newer upstream release v7.1.3. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTJG2YACgkQLHwxRsGg ASGR5Q//TctaUZy6KxZMqOSC/QUXHsmW5IjpohEEu0RoxUCt6VZhr5cTvotDCf+o KQXmnLC0JmiR2kBlorwdpHY03mL+rzTSR7rP6SzFWoeK/ps5WIAb1VyGhj1ETS5e elGxUgWxaszgcXj71wde6K3fvhuCv4lIVRJg6NdNCzMIFrrcTkVxHEj0nHaMX3P5 DXbOu6rS2vObO51Jwf4B8Ve267dvKMBhd/y4Y8iIbZlTe+rqHkXdnK8D/hMxBGaK 0QQqoxc0Ht19Y30KyMkNbSEnYqUmJGa9RfsmwvNIPdMAoONtV2fSTD5goxfQeyAi 4TtW4B4CmbRb61UcdeKFitW75uVDk6MNp4a1D90qfXpbx9PpJmdBLP+bmdQKmRwi dUbiTEeDjlN5i5JMOXY5NWJPI/m/qBLHhZZbCX2TrJLtBh+epJyNgGJb/ckJRii9 fS589/3nELFj49FLTwFQkEkUKXjfteRieIrOArDNjawWX08M3cbe4WrzmfLSSpCQ bPo2DdLMmbUHmQVyMuK/kvZEKvo3ZXIhm/jvusjORJp7tWFfdAgCMxcJs/w/HVQz O/LbMHm6r4i5+7IhSLqmy6/8Vj577e/yTaRcD3aTWddNIU3Cu7CHahCcYo0cdS7U nez6meovMNaT2UXN96Xm1OOAy7jbUe4JVtv9YAnvrOyCy4jCsC8= =o4R8 -END PGP SIGNATURE-
Bug#1042832: rust-enumset: Please update to v1.1.2
Source: rust-enumset Version: 1.0.12-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to (at least) newer upstream release v1.1.2. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTJGmAACgkQLHwxRsGg ASHjfQ/+N0KvWeXFc6LZT8+Xzr/V6kFMjAMovIGLqjb9hkOx7ukwNuSme6uqAjd+ dOxpBsXrkKXCb+8NEQsvarpy96TkyWr+YcDM/3eqnnGLzH/0dHgOLn//FLyX0Xvs /veT/uP/TcZ2PwQxVjGLNGuJPKn5KoaRZsJDtP2hBcKZvT5qGZiIqkMZEB/L7leE mPGM+/NuzmtSj7HTpIEGvxKtbReHxvD1h+SVXar4wdZhVCKnNQofRxt6mYgYP4i6 FjWM65eaYoi753lPR9pacnrqgV3k+9i3Wqusg09psAWJWsWZRQpEkPzrnRexNEZj a+zc1lLaA8IKNKFaLLTBYqOMnvflJP/2KBf2c6J0E2h9XM3SSQ/UOBgEVnCcwgOz 5tSFh8pf6sD0muj4IyU/b+MGse3h9mSAXUTVWImIj5qTYvFNoFcXkyUImE8AuEE3 wVq/kpEWRxepNbqBUgzBnT59plC1JwZRZ+TU+QKSiwPaV5oeMxZVw8oQxj/BgVit K32hh4dtP2NuAgx+lbaDt3L9eu9F5i8J2buI4eSdlCvvnkkcUHOigGN2/AD260m+ bZir7R2GgEWwYfb6GfO2C54jozuKiUMo6jkGKlZyNlMrYiCAAgZchxkmRA0gpf1+ cEMKnhGOB7R+dUCfuZKH2hjbf9iurDavw7dpCt6Ext/aI1E0A8U= =19Rv -END PGP SIGNATURE-
