Bug#985256:
Looks like a duplicate of this to me: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985631
Bug#1029485: RFS: runit/2.1.2-53 [RC] -- system-wide service supervision
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "runit": * Package name : runit Version : 2.1.2-53 Upstream contact : Gerrit Pape * URL : http://smarden.org/runit/ * License : CC0-1.0, BSD-3-clause, GPL-3+ * Vcs : https://salsa.debian.org/debian/runit Section : admin The source builds the following binary packages: runit - system-wide service supervision runit-run - service supervision (systemd and sysv integration) runit-systemd - transitional package for runit-systemd users getty-run - runscripts to supervise getty processes runit-init - system-wide service supervision (as init system) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/runit/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/runit/runit_2.1.2-53.dsc Git repo: https://salsa.debian.org/debian/runit/-/tree/next Changes since the last upload: runit (2.1.2-53) unstable; urgency=medium . * runit-init: - depends on mount [linux-any] (Closes: #1028181) - change architecture field to any, because of mount - recommends runit-services * runit: suggests runit-services * getty-run: - enable the serial getty-ttyS0 by default - make getty-ttyS0 device configurable - automatically set device for getty-ttyS0 from kernel `console=' command line (Closes: #1028270) * d/copyright: update copyright years * d/tests: update init-switch test Regards, Lorenzo
Bug#1029482: git-cola: New upstream version 4.1.0
Package: git-cola Version: 4.1.0-1 Severity: wishlist Dear Maintainer, git-cola has not been recently updated due to Breaking Changes in its Python build system (distutils deprecations, PEP-517/518). https://github.com/git-cola/git-cola/issues/1231#issuecomment-1136733246 I took at stab at updating the debian packaging and have made the updates available in this public repository: https://github.com/davvid/git-cola-debian/ The new packaging should get us over the 3.x -> 4.x breaking changes hurdle. https://github.com/davvid/git-cola-debian/commits/main The "debian: update packaging to 3.12.0-2" commit synced the repository with the latest version in debian, last packaged by g...@debian.org. The new commits (post the 3.12.0 import) got it to deal with issues in setuptools_scm and pip install --prefix=/usr. An interesting detail is that the updated packaging contains two workarounds for issues that affect Debian. Any project using setuptools_scm [1] or "pip install --prefix=/usr" [2] may be in a similar boat until the upstream issues are resolved. Hopefully these workarounds are acceptable for now. https://github.com/davvid/git-cola-debian/blob/main/debian/rules#L8 https://github.com/davvid/git-cola-debian/blob/main/debian/rules#L17 History: The git-cola-debian packaging repository is derived from the debian packaging originally hosted on aioth.debian.org: https://alioth-archive.debian.org/git/collab-maint/git-cola.git.tar.xz git-cola-debian's history is truncated. I did not have the sources for any of the intermediate versions from gcs that were being managed using quilt so there are no commits corresponding to them. I'm also the upstream for this package so I'd like to help keep the Debian packaging up to date. Thanks! -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/4 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 git-cola depends on: ii git [git-core] 1:2.39.0-1 ii libjs-jquery3.6.1+dfsg+~3.5.14-1 ii libjs-modernizr 2.6.2+ds1-5 ii libjs-underscore1.13.4~dfsg+~1.11.4-3 ii node-html5shiv 3.7.3+dfsg-5 ii python3 3.10.6-3+b1 ii python3-importlib-metadata 4.12.0-1 ii python3-pyqt5 5.15.7+dfsg-3+b3 ii python3-qtpy2.3.0-1 ii python3-send2trash 1.8.1~b0-2 Versions of packages git-cola recommends: ii gitk 1:2.39.0-1 ii tcl [tclsh] 8.6.11+1 ii xxdiff 1:5.1+git20220924+dfsg-1 git-cola suggests no packages. -- no debconf information
Bug#1017497: closed by Debian FTP Masters (reply to Jochen Sprickerhof ) (Bug#1017497: fixed in pnc 0.9.4-1)
Hi Paul, * Paul Wise [2023-01-23 08:46]: On Sun, 2023-01-22 at 14:09 +, Debian Bug Tracking System wrote: pnc (0.9.4-1) unstable; urgency=medium . [ Tzafrir Cohen ] * Include READMEs in docs dir (Closes: #1017497) I think this was closed by the wrong package? I filed it against pn not pnc. Sorry, I should have added more information. Upstream development of pn stalled and we are switching to the active pnc fork. Given that pn was never part of a release and the name is rather short and non explaining, I would just drop it. This also means that the executable is now named pnc. Cheers Jochen signature.asc Description: PGP signature
Bug#1029483: mmdebstrap: ld.so.cache unreproducible inside initrd for --mode=fakechroot
Package: mmdebstrap
Version: 1.3.1-2
Severity: minor
Tags: patch
Hi Johannes,
while this is not the cause for my funny ppc64el and s390x boot
failures, I think this is worth fixing anyhow, so here we go:
When --mode=chroot wraps ldconfig, it overwrites and -r argument. As it
happens mkinitramfs passes -r to ldconfig. When mmdebstrap's ldconfig
intercepts that, it overwrites that -r and the initramfs ends up missing
a ld.so.cache, which should be non-fatal, but is a difference anyhow.
I've tried fixing this and my final solution ended up with a ld.so.cache
(even though it still wouldn't boot, but that's another problem). Please
take this patch with a grain of salt.
Helmut
--- a/ldconfig.fakechroot
+++ b/ldconfig.fakechroot
@@ -106,10 +106,24 @@
for d in get_libdirs(chroot, [chroot / "etc" / "ld.so.conf"]):
make_relative(d)
+rootarg = chroot
+argv = sys.argv[1:]
+for arg in sys.argv[1:]:
+if arg == "-r":
+rootarg = None
+elif rootarg is None:
+argpath = Path(arg)
+if argpath.is_absolute():
+rootarg = chroot / argpath.relative_to("/")
+else:
+rootarg = Path.cwd() / argpath
+if rootarg is None:
+rootarg = chroot
+
# we add any additional arguments before "-r" such that any other "-r"
# option will be overwritten by the one we set
subprocess.check_call(
-[chroot / "sbin" / "ldconfig"] + sys.argv[1:] + ["-r", chroot]
+[chroot / "sbin" / "ldconfig"] + sys.argv[1:] + ["-r", rootarg]
)
Bug#919348: bring it in for Bookworm?
Hi! Would you be willing to reconsider for Bookworm? While you do have reservations about xfce4-screensaver, the question is not whether it's perfect, but how it fares against alternatives. And lightm-locker is so buggy it's outright useless for a good deal of users while reports for xfce4-screensaver are better. Thus even if not default, it'd be good to have it as an alternative -- at least installable. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄
Bug#1026200: Please package LilyPond 2.24.0 if possible
Anthony Fok writes: > Thank you so much for Cc'ing Rob regarding Guile-2.2. > > Rob, as you can see, there is a real need for Guile 2.2 for LilyPond > 2.24.0 (December 2022), this coming from LilyPond's Core Developer > Jonas Hahnfeld and "Factotum" and Jean Abou Samra. If it is OK with > you, Rob, I would be more than happy to adopt guile-2.2 and maintain > it for the entire lifetime of Debian 12 (bookworm), and hopefully by > Debian 13 (trixie), LilyPond will be ready for guile-3.0. :-)\ > Many thanks for your understanding! I'd be very hesitant to include Guile 2.2 in bookworm since I believe it's explicitly not supported upstream and hasn't had a single commit in over two years. If there's any chance LilyPond will support something newer in a reasonable time-frame, I might suggest just waiting, and then introducing the new version via backports. But I don't really understand the situation and constraints. That said, I won't oppose reintroducing 2.2, as long as I'm not responsible for it, and you're willing to herd all the cats to get it removed again as soon as possible. That was a good bit of work I'd prefer not to repeat. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#1029476: tuxguitar: arch-any build fails with current build system
On Sun, Jan 22, 2023 at 05:48:21PM -0800, tony mancill wrote: > Package: tuxguitar > Version: 1.5.6+dfsg1-3 > Severity: important > > The build system doesn't correctly build the arch-any packages when only > the arch specific targets are invoked. In the interest of getting the package into shape quickly for bullseye, I'm considering switching the arch-all packages to arch-any. This resolves the arch-any build issue until the upstream build system can be patched to work better with a separate arch-all and arch-any builds. The package has never been multi-arch. If any is opposed or would like to put up a patch, please speak up.
Bug#1021713: CalyxOS cannot be installed from Debian 11 since it has very old fastboot version
control: severity -1 wishlist src:android-platform-tools provides binary fastboot, and you can easily install version 29, which is even in bullseye backports. if you need version 30 or above, it's in experimental only.
Bug#1017497: closed by Debian FTP Masters (reply to Jochen Sprickerhof ) (Bug#1017497: fixed in pnc 0.9.4-1)
On Mon, 2023-01-23 at 06:58 +0100, Jochen Sprickerhof wrote: > Sorry, I should have added more information. Upstream development of pn > stalled and we are switching to the active pnc fork. > Given that pn was never part of a release and the name is rather short > and non explaining, I would just drop it. This also means that the > executable is now named pnc. I see, thanks for the explanation. Switching locally now. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1029480: python3-poetry should depend on python3-importlib-metadata (>= 3.6.0)
Package: python3-poetry Version: 1.3.2+dfsg-2 Having installed python3-poetry 1.3.2+dfsg-2 (from bookworm) and python3-importlib-metadata 1.6.0-2 (from bullseye), running poetry gives following error: $ poetry -v TypeError entry_points() got an unexpected keyword argument 'group' at /usr/lib/python3/dist-packages/poetry/plugins/plugin_manager.py:57 in get_plugin_entry_points 53│ self, env: Env | None = None 54│ ) -> list[metadata.EntryPoint]: 55│ return [ 56│ ep → 57│ for ep in metadata.entry_points(group=self._group) 58│ if self._is_plugin_candidate(ep, env) 59│ ] 60│ 61│ def add_plugin(self, plugin: Plugin) -> None: metadata.entry_point() has allowed arguments since 3.6.0; [1] so dependency should be added to the package metadata. [1] https://github.com/python/importlib_metadata/commit/8320adef797d5f14d9fff7b58ebc2a31a2a6a437
Bug#1023752: visidata: New upstream version: v2.10.2 (Oct 8, 2022)
Oh! Ty! What's your personal deadline so you have time to review? I will talk with the author, Saul. Nothing is coming up that is a dealbreaker for 2.11, so as far as I understand it that is the one we are going to go with. Either that or 2.10.2. On Sat, 21 Jan 2023 at 16:47, Martin wrote: > Hi, > > now is almost the last chance to get a current visidata into the next > Debian release. What's the state of the package? > > Cheers >
Bug#985631:
Seems to be a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985256
Bug#1029479: lintian: reject packages with debmake default description
Package: lintian Severity: wishlist X-Debbugs-CC: ftp-master yq was just accepted into Debian with a completely bogus description that is the default from the debmake automatic package generator. Please add a lintian tag and add it to the ftp-master auto-rejects. $ apt-cache show yq | grep-dctrl -s Description-en . Description-en: auto-generated package by debmake This Debian binary package was auto-generated by the debmake(1) command provided by the debmake package. $ dgrep -A5 'auto-generated' debmake /usr/lib/python3/dist-packages/debmake/control.py:desc = "auto-generated package by debmake" /usr/lib/python3/dist-packages/debmake/control.py-# /usr/lib/python3/dist-packages/debmake/control.py-if para["desc_long"].rstrip(): /usr/lib/python3/dist-packages/debmake/control.py-desc_long = para["desc_long"].rstrip() /usr/lib/python3/dist-packages/debmake/control.py-elif para["desc"].strip(): /usr/lib/python3/dist-packages/debmake/control.py-desc_long = " " + para["desc"].strip() -- /usr/lib/python3/dist-packages/debmake/para.py:help="pedantically check auto-generated files", /usr/lib/python3/dist-packages/debmake/para.py-) /usr/lib/python3/dist-packages/debmake/para.py-p.add_argument( /usr/lib/python3/dist-packages/debmake/para.py-"-T", /usr/lib/python3/dist-packages/debmake/para.py-"--tutorial", /usr/lib/python3/dist-packages/debmake/para.py-action="store_true", -- /usr/share/debmake/extra0desc_long/_long: This Debian binary package was auto-generated by the /usr/share/debmake/extra0desc_long/_long- debmake(1) command provided by the debmake package. -- /usr/share/debmake/extra0desc_long/_long_tutorial: This Debian binary package was auto-generated by the /usr/share/debmake/extra0desc_long/_long_tutorial- debmake(1) command provided by the debmake package. /usr/share/debmake/extra0desc_long/_long_tutorial- . /usr/share/debmake/extra0desc_long/_long_tutorial- = This comes from the unmodified template file = /usr/share/debmake/extra0desc_long/_long_tutorial- . /usr/share/debmake/extra0desc_long/_long_tutorial- Please edit this template file (debian/control) and other package files -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1029481: yq: unmodified incorrect package description from debmake template
Package: yq Version: 3.1.0-1 Severity: serious The current description of the yq package is rather bogus. It appears that the debmake template was not modified. $ apt-cache show yq | grep-dctrl -s Description-en . Description-en: auto-generated package by debmake This Debian binary package was auto-generated by the debmake(1) command provided by the debmake package. $ chronic apt source -qq yq $ head -n1 yq*/README* yq: Command-line YAML/XML/TOML processor - jq wrapper for YAML, XML, TOML documents $ dgrep -A5 'auto-generated' debmake /usr/lib/python3/dist-packages/debmake/control.py:desc = "auto-generated package by debmake" /usr/lib/python3/dist-packages/debmake/control.py-# /usr/lib/python3/dist-packages/debmake/control.py-if para["desc_long"].rstrip(): /usr/lib/python3/dist-packages/debmake/control.py-desc_long = para["desc_long"].rstrip() /usr/lib/python3/dist-packages/debmake/control.py-elif para["desc"].strip(): /usr/lib/python3/dist-packages/debmake/control.py-desc_long = " " + para["desc"].strip() -- /usr/lib/python3/dist-packages/debmake/para.py:help="pedantically check auto-generated files", /usr/lib/python3/dist-packages/debmake/para.py-) /usr/lib/python3/dist-packages/debmake/para.py-p.add_argument( /usr/lib/python3/dist-packages/debmake/para.py-"-T", /usr/lib/python3/dist-packages/debmake/para.py-"--tutorial", /usr/lib/python3/dist-packages/debmake/para.py-action="store_true", -- /usr/share/debmake/extra0desc_long/_long: This Debian binary package was auto-generated by the /usr/share/debmake/extra0desc_long/_long- debmake(1) command provided by the debmake package. -- /usr/share/debmake/extra0desc_long/_long_tutorial: This Debian binary package was auto-generated by the /usr/share/debmake/extra0desc_long/_long_tutorial- debmake(1) command provided by the debmake package. /usr/share/debmake/extra0desc_long/_long_tutorial- . /usr/share/debmake/extra0desc_long/_long_tutorial- = This comes from the unmodified template file = /usr/share/debmake/extra0desc_long/_long_tutorial- . /usr/share/debmake/extra0desc_long/_long_tutorial- Please edit this template file (debian/control) and other package files -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#989901: re: postfix: ipv6 CIDR not correct in mynetwork documentation
On Mon, 03 Jan 2022 14:32:45 -0500 Scott Kitterman wrote: > Proposed documentation changes will be included in postfix 3.7 when it is > released. 3.7 is in Unstable/Testing now, so this is resolved. Scott K signature.asc Description: This is a digitally signed message part.
Bug#960272: postfix: message_size_limit ignored if set to 0, and maximum is 2GiB
On Thu, 23 Dec 2021 22:25:32 -0500 Scott Kitterman wrote: > On Mon, 11 May 2020 13:40:28 +0200 Peter Keel wrote: > > Package: postfix > > Version: 3.4.10-0+deb10u1 > > Severity: wishlist > > Tags: upstream > > > > Hello > > > > Trying to set the postfix message_size_limit to 0 (educated guess > > for unlimited) will just have it use the compile-time-default of > > 1024. > > > > And then it turns out if you set it quite high, it will complain: > > fatal: bad numerical configuration: message_size_limit = 2147483648 > > > > Because the maximum is actually 2147483647 (one less than 2 GiB) > > Why would it have a maximum? > > It turns out that's LONG_MAX on a 32 bit machine. Upstream has updated the > documentation for Postfix 3.7 to explain this. I think for a limitation like > this a documentation update is the appropriate solution. We have 3.7 in Unstable/Testing now, so this has been addressed. Scott K signature.asc Description: This is a digitally signed message part.
Bug#1029484: linux: Enable Intel Uncore frequency control driver
Source: linux Version: 6.1.7-1 Severity: wishlist X-Debbugs-Cc: miguel.bernal.ma...@linux.intel.com, jair.de.jesus.gonzalez.plascen...@intel.com Dear Maintainer, Please enable the Intel Uncore frequency control driver. This driver allows control of uncore frequency limits on supported server platforms. # Intel Uncore frequency control driver CONFIG_INTEL_UNCORE_FREQ_CONTROL=m Some server users set limits on the uncore frequency using MSR 620H, while running latency sensitive workloads. This driver "the uncore frequency", controls RING/LLC (last-level cache) clocks. But MSR control is not always possible from the user space, so this driver provides a sysfs interface to set max and min frequency limits. This MSR 620H is a die scoped in multi-die system or package scoped in non multi-die systems. When this driver is loaded, a new directory is created under /sys/devices/system/cpu. For example on a two package Skylake server: $ cd /sys/devices/system/cpu/intel_uncore_frequency $ ls package_00_die_00 package_01_die_00 $ ls package_00_die_00 max_freq_khz min_freq_khz initial_max_freq_khz initial_min_freq_khz $ grep . * max_freq_khz:240 min_freq_khz:120 initial_max_freq_khz:240 initial_min_freq_khz:120 Here, initial_max_freq_khz and initial_min_freq_khz are read only attributes to show power up or initial values of max and min frequencies respectively. Other attributes are read-write, so that users can modify. A merge request was created at: https://salsa.debian.org/kernel-team/linux/-/merge_requests/645 Thanks, Miguel
Bug#1029234: lyx: Graphic problems editing a lyx file
OK. However I would like to point out that even the version flagged as bad works fine with the xfce desktop environment. Stefano On 22/01/23 20:04, Dr. Tobias Quathamer wrote: control: tag -1 unreproducible control: severity -1 important Am 20.01.23 um 15:21 schrieb Stefano Simonucci: I get the following messages: sudo apt build-dep lyx [sudo] password di stefano: Lettura elenco dei pacchetti... Fatto Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Alcuni pacchetti non possono essere installati. Questo può voler dire che è stata richiesta una situazione impossibile oppure, se si sta usando una distribuzione in sviluppo, che alcuni pacchetti richiesti non sono ancora stati creati o sono stati rimossi da Incoming. Le seguenti informazioni possono aiutare a risolvere la situazione: I seguenti pacchetti hanno dipendenze non soddisfatte: libboost-iostreams1.74-dev : Dipende: libboost1.74-dev (= 1.74.0-9) ma la versione 1.74.0-18.1 sta per essere installata Dipende: libboost-regex1.74-dev (= 1.74.0-9) ma la versione 1.74.0-18.1 sta per essere installata Dipende: libboost-iostreams1.74.0 (= 1.74.0-9) ma la versione 1.74.0-18.1 sta per essere installata libenchant-2-dev : Dipende: libenchant-2-2 (= 2.2.15-1) ma la versione 2.3.3-2 sta per essere installata Dipende: libglib2.0-dev ma non è installabile libmagic-dev : Dipende: libmagic1 (= 1:5.39-3) ma la versione 1:5.41-4 sta per essere installata libmythes-dev : Dipende: libmythes-1.2-0 (= 2:1.2.4-3+b1) ma la versione 2:1.2.5-1 sta per essere installata E: Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati. Maybe I must downgrade also these packages! Stefano Hi Stefano, unfortunately, I'm not able to reproduce the error you're seeing. Therefore, I'm downgrading the bug's severity to important, to avoid LyX being removed from the next Debian stable release. I suspect that the error you're experiencing comes from another package, which has to do with the graphic environment you're using. I have no idea, which package that might be, though. Sorry that I cannot provide any more useful ideas to narrow down this bug. Regards, Tobias
Bug#1027179: libde265: CVE-2022-43235 CVE-2022-43236 CVE-2022-43237 CVE-2022-43238 CVE-2022-43239 CVE-2022-43240 CVE-2022-43241 CVE-2022-43242 CVE-2022-43244 CVE-2022-43245 CVE-2022-43249 CVE-2022-432
Note: I've splitted the bugs as the NMU I'm currently preparing is only covering a subset of those CVEs, namely NOT those in #1029357 I've retitled the bugs accordingly, so that they reflect that.
Bug#1016963: Please test u-boot for dreamplug
On Sat, 2023-01-21 at 12:09 -0800, Vagrant Cascadian wrote: > On 2022-12-29, Ian Campbell wrote: > > On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: > > > dreamplug > > > > booting u-boot and Debian both from external mmc > > > > testing: 2022.04+dfsg-2+b1 "FDT and ATAGS support not compiled > > in" then resets and loops doing that > > unstable: 2022.10+dfsg-2 ok > > exp: 2023.01~rc4+dfsg-1 ok > > Any chance you could test 2023.01+dfsg-1 and/or 2023.01+dfsg-2 on the > dreamplug? Someone had problems with sheevaplug, which I think is a > fairly similar platform. Done, both versions worked fine on dreamplug. I also think dreamplug is a fairly similar platform to sheevaplug, but I have no personal experience of the latter. Ian.
Bug#1023472: Fix for double Window Manager in LXQt
... now sending to the bug, to show the full text ... The proposed patch is at Salsa: https://salsa.debian.org/installer-team/tasksel/-/merge_requests/23 By mentioning the sddm theme before sddm, it will prevent the default theme of sddm to be installed. Also in the MR: for some reason the theme was mentioned twice, it was probably intended to allow for other sddm themes. With kind regards, Roland Clobus PS: The old URL went stale, current openQA results can be seen here: 1) https://openqa.debian.net/group_overview/14 2) Select the most recent build that has '_sid_lxqt' 3) Look to 'walk-boot-options' 4) Select the red circle 5) At 'bootwalk_0' the Windows Manager selection window is shown (The current temporary deep link is https://openqa.debian.net/tests/116996#step/bootwalk_0/8) The ISO image can be downloaded from the tab 'Logs & Assets' OpenPGP_signature Description: OpenPGP digital signature
Bug#1028521: libopenscap8: openscap 1.2.16 not able to build ComplianceAsCode
Control: tags -1 + wontfix fixed-upstream buster Hi Marina On Thu, 12 Jan 2023 11:11:01 +0100 Marina Latini wrote: > Package: libopenscap8 > Version: 1.2.16-2+b2 > Severity: normal > > Dear Maintainer, > > I'm trying to build the scap-security-guide (ComplianceAsCode 0.1.64) on > Debian > 10. > https://github.com/ComplianceAsCode/content > > but currently the build is failing. > I'm am not able to reproduce this. With or without the patch, it generates the same files. Though without the patch, it clearly shows that openscap exits with a non-zero exit code, which isn't good, but the build still completes. I tested with these commands: cd build cmake ../ make ubuntu1604 > Note: I reported this issue also for Ubuntu as > https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/2002551 and > libopenscap8 provided in Debian 10 (2.1.16) is also affected. > > > The openscap versions 1.2.16 is missing the patch > https://github.com/OpenSCAP/openscap/commit/bbcbffcf6f901cb67ca5645307d170a32504a491.patch > provided via https://github.com/OpenSCAP/openscap/pull/1324 > > Without this patch openscap isn't able to build ComplianceAsCode > (https://github.com/ComplianceAsCode/content). > >* What led up to the situation? > > The PR https://github.com/OpenSCAP/openscap/pull/1324 was done after 1.2.16 > release and made available in openscap 1.2.18 and 1.3.1, so Debian 10 missed > it. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > The scap-security-guide uses openscap but, if the OVAL CVE/RPM data are not > available, the build fails. > > ComplianceAsCode on version 0.1.63 was building fine. > > This is one example of failure due to missing remote resources (but there are > more). > All xcddf generate fix with embedded remote resources fail. > > oscap xccdf generate fix --skip-valid --benchmark-id > xccdf_org.ssgproject.content_benchmark_UBUNTU-XENIAL --profile > xccdf_org.ssgproject.content_profile_anssi_np_nt28_restrictive --template > urn:xccdf:fix:script:sh ./ssg-ubuntu1604-ds.xml > > WARNING: Datastream component 'scap_org.open-scap_cref_-ubuntu-security-oval- > com.ubuntu.xenial.cve.oval.xml' points out to the remote > 'https://people.canonical.com/~ubuntu- > security/oval/com.ubuntu.xenial.cve.oval.xml'. Use '--fetch-remote-resources' > option to download it. > WARNING: Skipping 'https://people.canonical.com/~ubuntu- > security/oval/com.ubuntu.xenial.cve.oval.xml' file which is referenced from > datastream > OpenSCAP Error: Could not extract scap_org.open-scap_cref_ssg- > ubuntu1604-xccdf-1.2.xml with all dependencies from datastream. > [../../../src/DS/ds_sds_session.c:211] > > If the --fetch-remote-resources option is not provided, the resources pointed > by the components won't be downloaded. The provided patch allows the scan to > continue without remote components. > The result of rules which reference the missing remote resource will be > 'notchecked'. > >* What was the outcome of this action? > > The scap-security-guide uses openscap but, if the OVAL CVE/RPM data are not > available, the build will fail. > >* What outcome did you expect instead? > > If the --fetch-remote-resources option is not provided, the resources pointed > by the components won't be downloaded and the build should pass with remarks. I have marked this as 'wontfix', since buster has become LTS. If there is issues I have overlooked I can change this, but the final decision resides with the LTS team. I tested the proposed upstream patch, it is easily applied and will not create any regression. Regards, Håvard
Bug#1027919: RFS: dinit/0.16.0-1 -- [ITP] Service monitoring / "init" system
I send a new upload to mentors but seems like I do something "wrong". I think Debian BTS have a retitle system for bugs. No?
Bug#995966: epigrass: epirunner and epidash fail to run due to missing dash modules
Control: tags -1 pending Dash is packaged now but we also need https://github.com/Zsailer/nx_altair -- http://fam-tille.de
Bug#1026307: Fixed in 4:22.12.1-1
control: fixed -1 4:22.12.1-1
Bug#1014999: libde265: CVE-2020-21594 CVE-2020-21595 CVE-2020-21596 CVE-2020-21597 CVE-2020-21599 CVE-2020-21601 CVE-2020-21603 CVE-2020-21604 CVE-2020-21605 CVE-2020-21606
Bisect results. ONE CORRECTION: I can*not* reproduce CVE-2020-21601, this was an error yesterday. TL;DR: (Debian centric, see below if you want the commits) CVE-2020-21594 -- likely fixed in v1.0.3, or some regression made it reappear later. CVE-2020-21595 -- fixed in v1.0.9 CVE-2020-21596 -- STILL VULNERABLE CVE-2020-21597 -- fixed in v1.0.9 CVE-2020-21599 -- fixed in v1.0.9 CVE-2020-21601 -- fixed in v1.0.9 CVE-2020-21603 -- fixed in v1.0.9 CVE-2020-21604 -- fixed in v1.0.9 CVE-2020-21605 -- fixed in v1.0.9 CVE-2020-21606 -- fixed in v1.0.9 Later today, I will split the bug accordingly and set Debian fixed versions. I'll also amend d/changelog when preparing the NMU later. The poc is no longer triggering with the state in the master branch, as of today at commit c96962cf6a0259f1678e9a0e1566eb9b5516093a, I was bisecting to find when the poc started to no longer trigger. The test were commited on Debian unstable, gcc (Debian 12.2.0-14) 12.2. Methology: Starting point for all bisects were commit c43f2f8cd674bc7c78951b279ca0b1f883e1f276 (selected, as this is around the time where the CVEs were reported) ``` commit c43f2f8cd674bc7c78951b279ca0b1f883e1f276 (HEAD) Author: Dirk Farin Date: Thu Dec 19 11:04:40 2019 +0100 increase version number to v1.0.4 ``` Bisecting is done using, so that git will report the first "good" commit. ```# git bisect start --term-new=fixed --term-old=unfixed``` Bisecting is done using the CMake build system, using ```# cmake ../libde265 -DCMAKE_CXX_FLAGS="-fsanitize=address" -DCMAKE_BUILD_TYPE=Debug``` The pocs -- taken from the upstream issues (renamed for convience, so that the link to the CVE/issue is in the filename) The test was done with: ```./dec265/dec265 -q $POC``` CVE-2020-21594-issue233-libde265-put_epel_hv_fallback-heap_overflow.crash CVE-2020-21594-issue233-libde265-put_epel_hv_fallback-heap_overflow.crash2 Unfortunatly the code did not compile at the final bisect step, so the candidates for the first fixed commits are: ```git bisect fixed There are only 'skip'ped commits left to test. The first fixed commit could be any of: 39879b749bbad5b2abc2d56ddcb6488891e3a9a0 1df1dfe3180074724e8c7dedc789910a605934ad We cannot bisect more! ``` ``` git describe --contains 1df1dfe3180074724e8c7dedc789910a605934ad v1.0.3~15 git describe --contains 39879b749bbad5b2abc2d56ddcb6488891e3a9a0 v1.0.3~16 ``` So this seems to be fixed in v1.0.3. This result is strange, the commit 39879b7 is dated Mon Dec 4 16:22:57 2017 +0100 and the other is just ~30 minutes younger. Of course, there could be versions that have reintroduced a similar regression… CVE-2020-21595-issue239-libde265-mc_luma-heap_overflow.crash a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 is the first fixed commit ``` commit a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 Author: Dirk Farin Date: Tue Feb 23 15:11:09 2021 +0100 return error when PCM bits parameter exceeds pixel depth (#225) libde265/de265.cc | 2 ++ libde265/de265.h | 3 ++- libde265/sps.cc | 10 ++ 3 files changed, 14 insertions(+), 1 deletion(-) ``` ``` git describe --contains a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 v1.0.9~9 ``` CVE-2020-21597-issue238-mc_chroma-heap_overflow.crash f538254e4658ef5ea4e233c2185dcbfd165e8911 is the first fixed commit ``` commit f538254e4658ef5ea4e233c2185dcbfd165e8911 Author: Dirk Farin Date: Tue Apr 5 18:41:28 2022 +0200 fix streams where SPS image size changes without refreshing PPS (#299) libde265/decctx.cc | 9 + 1 file changed, 9 insertions(+) ``` ``` git describe --contains f538254e4658ef5ea4e233c2185dcbfd165e8911 v1.0.9~3^2~6 ``` CVE-2020-21599-issue235-libde265-de265_image__available_zscan-heap_overflow.crash a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 is the first fixed commit ``` commit a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 Author: Dirk Farin Date: Tue Feb 23 15:11:09 2021 +0100 return error when PCM bits parameter exceeds pixel depth (#225) libde265/de265.cc | 2 ++ libde265/de265.h | 3 ++- libde265/sps.cc | 10 ++ 3 files changed, 14 insertions(+), 1 deletion(-) ``` git describe --contains a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 v1.0.9~9 ``` CVE-2020-21603-put_qpel_0_0_fallback_16-heap_overflow.crash ``` a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 is the first fixed commit commit a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 Author: Dirk Farin Date: Tue Feb 23 15:11:09 2021 +0100 return error when PCM bits parameter exceeds pixel depth (#225) libde265/de265.cc | 2 ++ libde265/de265.h | 3 ++- libde265/sps.cc | 10 ++ 3 files changed, 14 insertions(+), 1 deletion(-) ``` ``` git describe --contains a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 v1.0.9~9 ``` CVE-2020-21604-issue231-mm_loadl_epi64-heap_overflow.crash a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 is the first fixed commit ``` commit
Bug#1026781: pkgconf: breaks adequate missing-pkgconfig-dependency check due to behaviour change in: pkg-config --exists --print-errors
On Wed, 21 Dec 2022 14:24:53 +0800 Paul Wise wrote: Package: pkgconf Severity: serious When a pkg doesn't have its dependencies satisfied, pkgconf --cflags etc all print an error message and return a failure exit code. Here’s a reproducer: $ docker run -it debian:unstable /bin/bash root@4f9e1cf385db:/# apt update > /dev/null WARNING: apt does not have a stable CLI interface. Use with caution in scripts. root@4f9e1cf385db:/# apt install -y --no-install-recommends libmpv-dev > /dev/null WARNING: apt does not have a stable CLI interface. Use with caution in scripts. debconf: delaying package configuration, since apt-utils is not installed root@4f9e1cf385db:/# apt install -y --no-install-recommends pkgconf > /dev/null WARNING: apt does not have a stable CLI interface. Use with caution in scripts. root@4f9e1cf385db:/# pkg-config --exists --print-errors mpv ; echo $? 0 root@4f9e1cf385db:/# pkg-config --cflags mpv ; echo $? -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/lua5.2 -I/usr/include/SDL2 -I/usr/include/uchardet -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -D_REENTRANT -I/usr/include/libdrm -I/usr/include/sixel -I/usr/include/spirv_cross 0 root@4f9e1cf385db:/# rm /usr/share/pkgconfig/wayland-protocols.pc root@4f9e1cf385db:/# pkg-config --exists --print-errors mpv ; echo $? 0 root@4f9e1cf385db:/# pkg-config --cflags mpv ; echo $? Package wayland-protocols was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-protocols.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-protocols', required by 'mpv', not found 1 root@4f9e1cf385db:/# -- -- Cheers, Andrej
Bug#1027506: Status of mozillavpn in Debian
Hello Richard, Have you been able to try again? Thanks Sylvestre Le 11/01/2023 à 09:43, Sylvestre Ledru a écrit : Are you sure it works in a pbuilder/chroot ? dget https://in.terlu.de/\~kreckel/mozillavpn/mozillavpn_2.12.0-1.dsc and building it fails with go: could not create module cache: mkdir /sbuild-nonexistent: permission denied (maybe an error above) Cheers S Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit : Could we just upgrade to version 1.12.0 for sid/bookworm, please? Right now, the mozillavpn package is slated for removal from bookworm. I would be very happy if we could avoid this. After some tinkering, I got v1.12.0 to work on sid/bookworm. Here's what it takes: 1) Create mozillavpn_2.12.0.orig.tar.gz a) download https://github.com/mozilla-mobile/mozilla-vpn-client/archive/refs/tags/v2.12.0.tar.gz b) unpack it (and discover that directories under 3rdparty/ subdir are empty) c) drop the contents of https://github.com/mozilla/glean/archive/refs/tags/v52.0.0.tar.gz into 3rdparty/glean/ d) drop the contents of https://github.com/WireGuard/wireguard-tools/archive/refs/heads/master.zip into 3rdparty/wireguard-tools/ 2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to debian/ directory: a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules (without it it FTBFS trying to run some tests and that is also in upstream's rules file) d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf debian/mozillavpn/etc/opt in debian/rules so purge won't remove /etc/opt/ since there's nothing in there anyway c) Add packages python3-click and python3-jinja2 to Build-Depnds in debian/control (without these, it FTBFS) d) remove libqt6* and qt6-qpa-plugins dependencies in debian/control (see #1026957). This builds for me on amd64. An alternative to step 1) above is of course to clone from https://github.com/mozilla-mobile/mozilla-vpn-client.git and then git submodule update --init. That only adds some stuff not needed for Debian into the orig.tar.gz. For the record, I've placed copies of the files at https://in.terlu.de/~kreckel/mozillavpn/. Also, debian-release should be contacted because of the build failure on mipsel and mpis64el. It makes little sense to insist on these architectures if upstream doesn't care. Please decide how to proceed and let me know if I can help in any way. -richard.
Bug#1029393: debian-installer: Missing glyph detection
Source: debian-installer Severity: minor Tags: l10n Hello maintainers of the Debian installer, As a follow-up on #101435, I've updated the script to detect more cases where glyphs are missing, but used in translations. The steps required to run the script are mentioned in the header of the script. If needed, I can provide the file 'collect' (the currently used translations of all udebs in Bookworm) Attached is also the output of the script, which lists the missing glyps With kind regards, Roland Clobus -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled E: Glyph: '' 173 is used in translations for language(s): da,tg, but not mentioned in any build/needed-chars/*.utf E: Glyph: '·' 183 is used in translations for language(s): ar,el,kab,ku,lt, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'Ĩ' 296 is used in translations for language(s): vi, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ĩ' 297 is used in translations for language(s): vi, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ɛ' 603 is used in translations for language(s): kab, but not mentioned in any build/needed-chars/*.utf E: Glyph: '́' 769 is used in translations for language(s): el,vi, but not mentioned in any build/needed-chars/*.utf E: Glyph: '̆' 774 is used in translations for language(s): bg, but not mentioned in any build/needed-chars/*.utf E: Glyph: '̉' 777 is used in translations for language(s): vi, but not mentioned in any build/needed-chars/*.utf E: Glyph: '־' 1470 is used in translations for language(s): he, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ו' 1493 is used in translations for language(s): he, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ע' 1506 is used in translations for language(s): he, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ף' 1507 is used in translations for language(s): he, but not mentioned in any build/needed-chars/*.utf E: Glyph: '׳' 1523 is used in translations for language(s): he, but not mentioned in any build/needed-chars/*.utf E: Glyph: '״' 1524 is used in translations for language(s): he, but not mentioned in any build/needed-chars/*.utf E: Glyph: '؛' 1563 is used in translations for language(s): ar,fa,ug, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ء' 1569 is used in translations for language(s): ar, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'آ' 1570 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'أ' 1571 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ؤ' 1572 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'إ' 1573 is used in translations for language(s): ar, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ة' 1577 is used in translations for language(s): ar, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ت' 1578 is used in translations for language(s): ar,fa,ug, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ث' 1579 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ح' 1581 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'خ' 1582 is used in translations for language(s): ar,fa,ug, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ذ' 1584 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ز' 1586 is used in translations for language(s): ar,fa,ug, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ص' 1589 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ض' 1590 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ط' 1591 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ظ' 1592 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ع' 1593 is used in translations for language(s): ar,fa, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'غ' 1594 is used in translations for language(s): ar,fa,ug, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ق' 1602 is used in translations for language(s): ar,fa,ug, but not mentioned in any build/needed-chars/*.utf E: Glyph: 'ن' 1606 is used in translations
Bug#1029394: dynamic-motd: piuparts error
Package: dynamic-motd Version: 0.04-1 Severity: serious https://piuparts.debian.org/sid/fail/dynamic-motd_0.04-1.log ... Selecting previously unselected package dynamic-motd. Preparing to unpack .../5-dynamic-motd_0.04-1_all.deb ... Unpacking dynamic-motd (0.04-1) ... Setting up media-types (8.0.0) ... Setting up libkeyutils1:amd64 (1.6.3-2) ... Setting up libtirpc-common (1.3.3+ds-1) ... Setting up libsqlite3-0:amd64 (3.40.1-1) ... Setting up libkrb5support0:amd64 (1.20.1-1) ... Setting up figlet (2.2.5-3+b1) ... update-alternatives: using /usr/bin/figlet-figlet to provide /usr/bin/figlet (figlet) in auto mode Setting up libncursesw6:amd64 (6.4-1) ... Setting up libk5crypto3:amd64 (1.20.1-1) ... Setting up libmpdec3:amd64 (2.5.1-2) ... Setting up libkrb5-3:amd64 (1.20.1-1) ... Setting up lsb-release (12.0-1) ... Setting up readline-common (8.2-1.3) ... Setting up libreadline8:amd64 (8.2-1.3) ... Setting up bc (1.07.1-3+b1) ... Setting up libgssapi-krb5-2:amd64 (1.20.1-1) ... Setting up libtirpc3:amd64 (1.3.3+ds-1) ... Setting up libnsl2:amd64 (1.3.0-2) ... Setting up libpython3.11-stdlib:amd64 (3.11.1-2) ... Setting up libpython3-stdlib:amd64 (3.11.1-1) ... Setting up python3.11 (3.11.1-2) ... Setting up python3 (3.11.1-1) ... [Errno 2] No such file or directory: '/etc/update-motd.d/sysinfo.py'error running python rtupdate hook dynamic-motd dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 ...
Bug#1029395: Our yad package is severely outdated
Package: yad Version: 0.40.0-1+b1 Hi, Debian Unstable proposes version 0.40.0-1+b1 of yad which is from 2019, while the real upstream version is 12.3, released on December 2022. Upstream moved their repository to github at: https://github.com/v1cont/yad Can you please provide an update for this package? Thanks in advance!
Bug#1029398: ben: "tracker --archs" is not honoured
Package: ben Version: 0.10.0 Severity: normal $ ben download --archs alpha --preferred-compression-format xz --mirror-binaries http://ftp.de.debian.org/debian-ports Downloading /tmp/Sources... Downloading /tmp/Packages_alpha... $ ben tracker --archs alpha -cd tracker Parsing /tmp/Sources... Parsing /tmp/Packages_amd64... Parsing /tmp/Packages_arm64... Parsing /tmp/Packages_armel... Parsing /tmp/Packages_armhf... Parsing /tmp/Packages_i386... Parsing /tmp/Packages_mips64el... Parsing /tmp/Packages_mipsel... Parsing /tmp/Packages_s390x... Parsing /tmp/Packages_ppc64el.. ...
Bug#1029400: libhtml-stripscripts-perl: CVE-2023-24038
Source: libhtml-stripscripts-perl Version: 1.06-3 Severity: important Tags: security upstream Forwarded: https://github.com/clintongormley/perl-html-stripscripts/issues/3 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.06-1 Hi, The following vulnerability was published for libhtml-stripscripts-perl. CVE-2023-24038[0]: | The HTML-StripScripts module through 1.06 for Perl allows | _hss_attval_style ReDoS because of catastrophic backtracking for HTML | content with certain style attributes. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-24038 https://www.cve.org/CVERecord?id=CVE-2023-24038 [1] https://github.com/clintongormley/perl-html-stripscripts/issues/3 Regards, Salvatore
Bug#999988: postfix: depends on obsolete pcre3 library
Dear maintainer, postfix package in unstable is now version 3.7. Could you change dependencies pcre3 to pcre2? Regards,
Bug#1028083: plasma-discover: Discover tray app crashes kded5, causing other system tray icons to vanish
Hello, this seems similar to the backtrace in bug #1026062. At least the "transactionListChanged" and the two lines above. It looks similar and may have the same root cause. I'd prefer to keep the bugs separate for now, though. It could be a different bug. FYI: My kded core dumps also contained something about a closed DBus connection in a different thread's stack trace. Perhaps this is related?
Bug#1029405: flightgear: crashes on receiving some real-time weather reports
Package: flightgear Version: 1:2020.3.16+dfsg-1+b2 Severity: important Forwarded: https://sourceforge.net/p/flightgear/codetickets/2765/ Tags: upstream fixed-upstream When real-time weather is enabled, some METAR strings received from the weather servers can cause fgfs to crash. A workaround is to disable real-time weather, an important feature of flightgear. This upstream commit fixes; it would be nice if it were backported before the freeze of bookworm. https://sourceforge.net/p/flightgear/flightgear/ci/86f82994bec00ecbe791b61530b229b22c7d51c8 Thank you! -- Ludovic Brenta.
Bug#1020913: looks like a temporary issue during ruby 3.1 transition
Control: fixed -1 2.2.0-1 likely caused by ruby-google-protobuf in experimental not being rebuilt with ruby 3.1. This built fine in buildd after ruby-google-protobuf was reuploaded to unstable.
Bug#1027198: einsteinpy: autopkgtest fail with numpy/1.24.1
Control: forwarded -1
https://github.com/einsteinpy/einsteinpy/commit/cffc0cacd053481e56
thanks
Dear Maintainer,
FTBFS is caused by two test failing with numpy 1.24
=== FAILURES ===
__ test_fractal_shows_figure ___
mock_stdout = <_io.StringIO object at 0x7fc084fb1d80>
mock_show =
@mock.patch.object(go.Figure, "show")
@mock.patch("sys.stdout", new_callable=StringIO)
def test_fractal_shows_figure(mock_stdout, mock_show):
> fig = fractal(divs=2, show=True)
einsteinpy/tests/test_plotting/test_fractal.py:12:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
einsteinpy/plotting/fractal.py:75: in fractal
go.Heatmap(z=_fractal_img(angle=step, dims=(400, 400)), showscale=False)
einsteinpy/plotting/fractal.py:40: in _fractal_img
_julia(A, c, zabs_max, i, j, dims, x_range, y_range, iter_max)
einsteinpy/plotting/fractal.py:20: in _julia
z = np.complex((i / width) * xwidth + xmin + 1j * ((j / height) * ywidth +
ymin))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
attr = 'complex'
def __getattr__(attr):
# Warn for expired attributes, and return a dummy function
# that always raises an exception.
import warnings
try:
msg = __expired_functions__[attr]
except KeyError:
pass
else:
warnings.warn(msg, DeprecationWarning, stacklevel=2)
def _expired(*args, **kwds):
raise RuntimeError(msg)
return _expired
# Emit warnings for deprecated attributes
try:
val, msg = __deprecated_attrs__[attr]
except KeyError:
pass
else:
warnings.warn(msg, DeprecationWarning, stacklevel=2)
return val
if attr in __future_scalars__:
# And future warnings for those that will change, but also give
# the AttributeError
warnings.warn(
f"In the future `np.{attr}` will be defined as the "
"corresponding NumPy scalar. (This may have returned Python "
"scalars in past versions.", FutureWarning, stacklevel=2)
# Importing Tester requires importing all of UnitTest which is not a
# cheap import Since it is mainly used in test suits, we lazy import it
# here to save on the order of 10 ms of import time for most users
#
# The previous way Tester was imported also had a side effect of adding
# the full `numpy.testing` namespace
if attr == 'testing':
import numpy.testing as testing
return testing
elif attr == 'Tester':
from .testing import Tester
return Tester
> raise AttributeError("module {!r} has no attribute "
"{!r}".format(__name__, attr))
E AttributeError: module 'numpy' has no attribute 'complex'
/usr/lib/python3/dist-packages/numpy/__init__.py:284: AttributeError
__ test_fractal_draws_figure ___
def test_fractal_draws_figure():
> fig = fractal(divs=2, show=False)
einsteinpy/tests/test_plotting/test_fractal.py:18:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
einsteinpy/plotting/fractal.py:75: in fractal
go.Heatmap(z=_fractal_img(angle=step, dims=(400, 400)), showscale=False)
einsteinpy/plotting/fractal.py:40: in _fractal_img
_julia(A, c, zabs_max, i, j, dims, x_range, y_range, iter_max)
einsteinpy/plotting/fractal.py:20: in _julia
z = np.complex((i / width) * xwidth + xmin + 1j * ((j / height) * ywidth +
ymin))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
attr = 'complex'
def __getattr__(attr):
# Warn for expired attributes, and return a dummy function
# that always raises an exception.
import warnings
try:
msg = __expired_functions__[attr]
except KeyError:
pass
else:
warnings.warn(msg, DeprecationWarning, stacklevel=2)
def _expired(*args, **kwds):
raise RuntimeError(msg)
return _expired
# Emit warnings for deprecated attributes
try:
val, msg = __deprecated_attrs__[attr]
except KeyError:
pass
else:
warnings.warn(msg, DeprecationWarning, stacklevel=2)
return val
if attr in __future_scalars__:
# And future warnings for those that will change, but also give
# the AttributeError
warnings.warn(
f"In the future `np.{attr}` will be defined as the "
"corresponding NumPy scalar. (This may have returned Python "
"scalars in past versions.", FutureWarning, stacklevel=2)
#
Bug#1004963: CVE-2020-21598 CVE-2020-21600 CVE-2020-21602
Control: tags -1 fixed 1.0.9-1 TL;DR: bisecting result. They are all fixed in the upstream 1.0.9 release, marking this as such. (I'll ammend d/changelog when I prepare my NMU. I'll keep bug open until the NMU is in the archives.) The poc is no longer triggering with the state in the master branch, as of today at commit c96962cf6a0259f1678e9a0e1566eb9b5516093a, I was bisecting to find when the poc started to no longer trigger. The test were commited on Debian unstable, gcc (Debian 12.2.0-14) 12.2. Methology: Starting point for all bisects were commit c43f2f8cd674bc7c78951b279ca0b1f883e1f276 (selected, as this is around the time where the CVEs were reported) ```c43f2f8cd674bc7c78951b279ca0b1f883e1f276 is the first fixed commit commit c43f2f8cd674bc7c78951b279ca0b1f883e1f276 (HEAD) Author: Dirk Farin Date: Thu Dec 19 11:04:40 2019 +0100 increase version number to v1.0.4 ``` Bisecting is done using, so that git will report the first "good" commit. ```# git bisect start --term-new=fixed --term-old=unfixed``` Bisecting is done using the CMake build system, using ```# cmake ../libde265 -DCMAKE_CXX_FLAGS="-fsanitize=address" -DCMAKE_BUILD_TYPE=Debug``` The pocs -- taken from the upstream issues (renamed for convience, so that the link to the CVE/issue is in the filename) The test was done with: ```./dec265/dec265 -q $POC``` CVE-2020-21598-issue237-libde265-ff_hevc_put_unweighted_pred_8_sse-heap_overflow.crash ``` f538254e4658ef5ea4e233c2185dcbfd165e8911 is the first fixed commit commit f538254e4658ef5ea4e233c2185dcbfd165e8911 Author: Dirk Farin Date: Tue Apr 5 18:41:28 2022 +0200 fix streams where SPS image size changes without refreshing PPS (#299) libde265/decctx.cc | 9 + 1 file changed, 9 insertions(+) git describe --contains 'f538254e4658ef5ea4e233c2185dcbfd165e8911' v1.0.9~3^2~6 ``` CVE-2020-21600-issue243-libde265-put_weighted_pred_avg_16_fallback-heap_overflow.crash a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 is the first fixed commit commit a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 Author: Dirk Farin Date: Tue Feb 23 15:11:09 2021 +0100 return error when PCM bits parameter exceeds pixel depth (#225) libde265/de265.cc | 2 ++ libde265/de265.h | 3 ++- libde265/sps.cc | 10 ++ 3 files changed, 14 insertions(+), 1 deletion(-) CVE-2020-21602-issue242-libde265-put_weighted_bipred_16_fallback-heap_overflow.crash a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 is the first fixed commit ``` commit a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25 Author: Dirk Farin Date: Tue Feb 23 15:11:09 2021 +0100 return error when PCM bits parameter exceeds pixel depth (#225) libde265/de265.cc | 2 ++ libde265/de265.h | 3 ++- libde265/sps.cc | 10 ++ 3 files changed, 14 insertions(+), 1 deletion(-) ``` git describe --contains 'a3f1c6a0dea2b0d4a531255ad06ed40cdb184d25' v1.0.9~9
Bug#1029389: nautilus: umount usb xfs with external log damages log
Package: nautilus Version: 3.38.2-1+deb11u1 Severity: normal Tags: upstream X-Debbugs-Cc: foren...@wi.rr.com I used the eject option for a usb drive with a xfs file system and external log. The drive wouldn't mount subsequently, and advised using xfs_repair. xfs_repair advised mounting the drive, and if that was not possible, to zero the log, losing all meta data, and possibly causing corruption. I could not mount the drive, so I zeroed the log with xfs_repair. Subsequently, thew drive could be mounted (NVMe drive inside usb enclosure). Experimenting, I tried using umount from the shell, and it properly unmounted the drive, which could then be mounted without issue. Granted this is currently a rare situation. But with the possibility of 4TB usb drives presently, and the advantages of the xfs for use with huge numbers of files (I use the drive in question to maintain the i386 and amd64 arches of the Debian mirror with ftpsync) and the advantages of external log feature, it might become more common. Thanks for all the help. -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 nautilus depends on: ii bubblewrap 0.4.1-3 ii desktop-file-utils 0.26-1 ii gsettings-desktop-schemas 3.38.0-2 ii gvfs1.46.2-1 ii libatk1.0-0 2.36.0-2 ii libc6 2.31-13+deb11u4 ii libcairo-gobject2 1.16.0-5 ii libcairo2 1.16.0-5 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1+deb11u1 ii libgexiv2-2 0.12.1-1 ii libglib2.0-02.66.8-1 ii libglib2.0-data 2.66.8-1 ii libgnome-autoar-0-0 0.2.4-3 ii libgnome-desktop-3-19 3.38.5-3 ii libgstreamer-plugins-base1.0-0 1.18.4-2 ii libgstreamer1.0-0 1.18.4-2.1 ii libgtk-3-0 3.24.24-4+deb11u2 ii libnautilus-extension1a 3.38.2-1+deb11u1 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libselinux1 3.1-3 ii libtracker-sparql-2.0-0 2.3.6-2 ii nautilus-data 3.38.2-1+deb11u1 ii shared-mime-info2.0-1 ii tracker 2.3.6-2 ii tracker-extract 2.3.5-2.1 ii tracker-miner-fs2.3.5-2.1 Versions of packages nautilus recommends: ii gnome-sushi 3.38.0-1 ii gvfs-backends 1.46.2-1 ii libgdk-pixbuf2.0-bin 2.42.2+dfsg-1+deb11u1 ii librsvg2-common 2.50.3+dfsg-1 Versions of packages nautilus suggests: ii eog 3.38.2-1 ii evince [pdf-viewer] 3.38.2-1 ii nautilus-extension-brasero 3.12.2-6 ii nautilus-sendto 3.8.6-3.1 ii totem 3.38.0-2 ii vlc [mp3-decoder] 3.0.17.4-0+deb11u1 ii xdg-user-dirs 0.17-2 -- no debconf information
Bug#1029391: munin-node: Please add cciss support to the smart_ plugin
Package: munin-node Version: 2.0.67-3 Severity: wishlist Hello I knew this exact same wish was in #488360 But I have new information to add to it. In that old bug report the user has SAS drives, and there are not that much information which SAS drives could report, so it was not a problem with the controller. I also have disks on a controller which are only available through cciss, but my disks are SATA disks which report fully normal data for SATA disks. So please add support for cciss for the smart_ plugin ... :-) Here is the output for example: (This is the output of my 4th disk, disks 1-3 (cciss,0 ... cciss,2) have errors so I only show disk 4 which has no errors.) smartctl /dev/sda -d cciss,3 -a smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-20-amd64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number:W1F7MF94 LU WWN Device Id: 5 000c50 06a73a16e Firmware Version: CC27 User Capacity:3.000.592.982.016 bytes [3,00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:7200 rpm Form Factor: 3.5 inches Device is:In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Sun Jan 22 11:31:13 2023 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART Status not supported: Incomplete response, ATA output registers missing SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:( 584) seconds. Offline data collection capabilities:(0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 322) minutes. Conveyance self-test routine recommended polling time:( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006Pre-fail Always - 183875504 3 Spin_Up_Time0x0003 094 094 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 60 5 Reallocated_Sector_Ct 0x0033 100 100 010Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 071 053 030Pre-fail Always - 43093110146 9 Power_On_Hours 0x0032 079 079 000Old_age Always - 18887 10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 21 183 Runtime_Bad_Block 0x0032 100 100 000Old_age Always - 0 184 End-to-End_Error0x0032 100 100 099Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000Old_age Always - 1 1 1 189 High_Fly_Writes 0x003a 097 097 000Old_age Always - 3 190
Bug#1029392: ITP: python-nx-altair -- draw NetworkX graphs with Altair in Python3
Package: wnpp Severity: wishlist Subject: ITP: python-nx-altair -- draw NetworkX graphs with Altair in Python3 Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: python-nx-altair Version : 0.1.6 Upstream Author : Zach Sailer * URL : https://altair-viz.github.io/ * License : MIT Programming Lang: Python Description : draw NetworkX graphs with Altair in Python3 nx_altair offers a similar draw API to NetworkX but returns Altair Charts instead. Remark: This package is maintained by Debian Python Team at https://salsa.debian.org/python-team/packages/python-nx-altair
Bug#1029399: ncurses-bin: tic crashes on very long tc/use clauses
Package: ncurses-bin Version: 6.4-1 Tags: security fixed-upstream Forwarded: https://lists.gnu.org/archive/html/bug-ncurses/2023-01/msg00035.html X-Debbugs-CC: t...@security.debian.org Running tic on the attached file triggers a stack buffer overflow: , | $ tic -I minimized-crash1 | "minimized-crash1", line 1, col 606, terminal '0': Very long string found. Missing separator? | "minimized-crash1", line 1, col 4098, terminal '0': Missing separator | *** buffer overflow detected ***: terminated | [1]485807 IOT instruction tic -I minimized-crash1 ` This has been reported upstream yesterday and was promptly addressed in this weekend's patchlevel. I intend to cherry-pick the patch for Bookworm, maybe it could also be included in a Bullseye point release if older versions are affected. The impact seems to be rather low, as the attacker needs to persuade the victim to run tic on crafted input, and thanks to the stack protection nothing worse than a crash should happen.
Bug#1029398: ben: "tracker --archs" is not honoured
Dear Adrian, Le 22/01/2023 à 12:33, Adrian Bunk a écrit : $ ben download --archs alpha --preferred-compression-format xz --mirror-binaries http://ftp.de.debian.org/debian-ports Downloading /tmp/Sources... Downloading /tmp/Packages_alpha... $ ben tracker --archs alpha -cd tracker Parsing /tmp/Sources... Parsing /tmp/Packages_amd64... Parsing /tmp/Packages_arm64... Parsing /tmp/Packages_armel... Parsing /tmp/Packages_armhf... Parsing /tmp/Packages_i386... Parsing /tmp/Packages_mips64el... Parsing /tmp/Packages_mipsel... Parsing /tmp/Packages_s390x... Parsing /tmp/Packages_ppc64el.. "ben tracker" indeed seems to ignore its "--archs" option... and probably most of the options common to all ben frontends! Actually, it takes its configuration from the so-called "global" configuration file. Did you specify one (I see you've specified "-cd tracker", does it refer to something you wrote yourself)? I'm afraid the default one is the Realase Team's one [1], which doesn't seem useful elsewhere... [1] /usr/share/doc/ben/examples/tracker/global.conf By writing a custom global.conf (see comments in [1]), I can make "ben tracker" work with debian-ports and only alpha... I see two approches to solving this bug: - make the command-line options override the configuration specified in global.conf - reject command-line options when they are read in global.conf What do you think? In all cases, you should be able to do what you want by providing a custom global.conf. Sorry for being hesitant, I am not familiar with this part of the codebase... Cheers, -- Stéphane
Bug#1029402: RFS: shaderc/2023.2-1 -- Library API for accessing glslc functionality
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "shaderc": * Package name : shaderc Version : 2023.2-1 Upstream contact : David Neto * URL : https://github.com/google/shaderc/ * License : BSD-3-clause, Apache-2.0 * Vcs : https://salsa.debian.org/debian/shaderc Section : libs The source builds the following binary packages: glslc - Command line compiler for GLSL/HLSL to SPIR-V libshaderc-dev - Library API for accessing glslc functionality - static libraries and headers libshaderc1 - Library API for accessing glslc functionality - shared libraries To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shaderc/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shaderc/shaderc_2023.2-1.dsc Changes since the last upload: shaderc (2023.2-1) unstable; urgency=medium . * New upstream release * Refresh patches (probably required by the raise of cmake required version) * Bump Standards-Version to 4.6.2: no change needed Regards, -- Philippe.
Bug#1029398: ben: "tracker --archs" is not honoured
On Sun, Jan 22, 2023 at 02:13:32PM +0100, Stéphane Glondu wrote: > Le 22/01/2023 à 13:48, Adrian Bunk a écrit : > > > I'm afraid the default one is the Realase > > > Team's one [1], which doesn't seem useful elsewhere... > > > > Usually they are pretty useful for me since usually I am just using this > > for sending new/changed trackers as MRs to the release team. > > Is your attempt to use "ben tracker" with debian-ports new? >... Yes. > > > I see two approches to solving this bug: > > > - make the command-line options override the configuration specified in > > > global.conf > > > - reject command-line options when they are read in global.conf > > > > > > What do you think? > > > ... > > > > The behaviour of "ben download" of having some sane defaults[1] > > or configuration file that can be overridden on the command line > > is IMHO pretty good, and I'd expect "ben tracker" to behave the > > same way. > > I'll see what I can do. Thanks! > > [2] https://salsa.debian.org/debian/ben/-/merge_requests/2 > > Sorry for taking so much time to merge such a trivial change, but I didn't > see the MR until now... There is so much noise in Salsa notifications that I > ended up ignoring them altogether. Ah thanks, that explains. > Cheers, cu Adrian
Bug#973990: reopen 973990
reopen 973990
Bug#1029168: fonts-urw-base35: Apache pdfbox cannot load fonts. Complains "Start marker missing"
On Sat, 21 Jan 2023, James Cloos wrote: > oh, and one way to convert the .t1 to traditional pfa or pfb is like this: > > t1disasm …/urw-base35/NimbusRoman-Bold.t1|t1asm -b -o NimbusRoman-Bold.pfb Except that this does not work for C059-Italic.t1 (see https://bugs.debian.org/1029289). On Sat, 21 Jan 2023, Fabian Greffrath wrote: > We must not forget the primary purpose of these fonts, and that is to > serve as the 35 base fonts for ghostscript! Thus, I consider it out of > question to modify the original T1 fonts in this package. > > What we may discuss about is to replace the "compatibility symlinks" in > /usr/share/fonts/X11/Type1 with actual converted PFB files. That would be an option. But X11 works for me with the symlinks without problems (it's only necessary that they are named .pfb not .t1). So from a "requirement" point of view it's only pdfbox, which fails on .pfb files without the binary segment headers (and t1utils, which fails with C059-Italic.t1, which can be repaired with my segmentheader generator script). > > doesn't handle C059-Italic.t1 correctly but generates a completely > > broken font file. > Does it work if you first convert to PFA format and from there to PFB > format? No, t1ascii C059-Italic.t1 | t1binary | t1disasm still has a binary blob (near definition of /uni0496). So t1utils are not able to handle C059-Italic.t1 at all (unless this font is patched with segment headers using my script before). I just compared the output of t1disasm of the original .t1 fonts and my patched fonts and noticed that the result is identical except C059-Italic.t1 and P052-italic.t1, which both have (unexpected) binary data in their disassembled output. I understand, that you do not want to modify the official urw-base35 .t1 fonts, since FreeType is able to handle them as they are, but from robustness principle view (https://en.wikipedia.org/wiki/Robustness_principle) "be conservative in what you send, be liberal in what you accept", it may be a good idea to "convert" the .t1 fonts to .pfb fonts by adding thes segment headers (and maybe rename them to .pfb), so all software (not only FreeType) is able to use them... Because there is other software, that doesn't support the fonts as they are: - X11 does not accept the .t1 suffix - pdfbox does not accept .t1 suffix and missing segment headers - t1utils fails on missing segment headers on C059-Italic.t1 and P052-italic.t1 So the current .t1 fonts are not really conservative... Greetings Roland
Bug#1028730: fixed in last upload and built on buildd
Control: fixed -1 1.7.0+dfsg-6
Bug#1017871: Please help to reproduce (Was: shiny-server: server-function don't run)
Hi Sebastian, thanks for your bug report and your attempt to track this down by replacing the sockjs files. Please note that neither Nilesh nor I are shiny-server users. Thus it would help if you could provide a possibly small example that helps us reproducing the problem. Kind regards Andreas. -- http://fam-tille.de
Bug#1029390: fontconfig-config: Frequently used sans, sans-serif and monospace changed from DejaVu to Noto without a warning
Package: fontconfig-config Version: 2.14.1-3 Severity: important X-Debbugs-Cc: gajdusek.p...@centrum.cz Dear Maintainer, In /usr/share/fontconfig/conf.avail/60-latin.conf the preferred font for sans, sans-serif and monospace has changed from DejaVu to Noto. This comes from upstream and the commit unfortunately lacks any reasoning: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/ad70d785974992c569b30108923875e5b5e9dc5e This results in font change in a lot of applications I am using. Please consider keeping the DejaVu as the preferred family or distribute a NEWS.Debian with the change described and instructions how to change the preferred fonts, e.g. by copying and modifying /etc/fonts/conf.d/60-latin.conf to $XDG_CONFIG_HOME/fontconfig/conf.d/ Thank you, Petr -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'testing'), (499, 'unstable'), (497, 'stable'), (496, 'oldstable'), (490, 'oldoldstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fontconfig-config depends on: ii debconf [debconf-2.0] 1.5.82 ii fonts-croscore 20201225-1 ii fonts-dejavu-core 2.37-2 ii fonts-freefont-otf 20120503-10 ii fonts-freefont-ttf 20120503-10 ii fonts-liberation 1:1.07.4-11 ii fonts-liberation2 2.1.5-1 ii fonts-texgyre 20180621-6 ii fonts-urw-base35 20200910-6 ii ttf-bitstream-vera 1.10-8.2 fontconfig-config recommends no packages. fontconfig-config suggests no packages. -- debconf information excluded
Bug#998388: openresolv: resolvconf fails if called from openvpn during system start with "kill: Operation not permitted"
Hi! Catched the same issue. I'm not using systemd service. Openvpn is started manually from shell as root. Script security is set to 2 to allow run everything. Multiple times openvpn restart connection and script executes well. But sometimes script exits with error code: ``` + : /var/run/avahi-daemon/pid + [ -s /var/run/avahi-daemon/pid ] + cat /var/run/avahi-daemon/pid + kill -HUP 935 /sbin/resolvconf: 31: kill: Operation not permitted + retval=1 ``` Source file is: `/lib/resolvconf/libc.d/avahi-daemon`
Bug#1029401: libde265: diff for NMU version 1.0.9-1.1
Package: libde265 Version: 1.0.9-1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for libde265 (versioned as 1.0.9-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru libde265-1.0.9/debian/changelog libde265-1.0.9/debian/changelog --- libde265-1.0.9/debian/changelog 2022-10-25 10:15:37.0 +0200 +++ libde265-1.0.9/debian/changelog 2023-01-22 13:19:20.0 +0100 @@ -1,7 +1,35 @@ +libde265 (1.0.9-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Apply patches to mitigate asan failures: +reject_reference_pics_from_different_sps.patch and +use_sps_from_the_image.patch. + * Combined, this two patches fixes: +- CVE-2022-43243, CVE-2022-43248, CVE-2022-43253 (Closes: #1025816) +- CVE-2022-43235, CVE-2022-43236, CVE-2022-43237, CVE-2022-43238, + CVE-2022-43239, CVE-2022-43240, CVE-2022-43241, CVE-2022-43242, + CVE-2022-43244, CVE-2022-43250, CVE-2022-43252 (Closes: #1027179) +- CVE-2022-47655 + * Additional patch recycle_sps_if_possible.patch to avoid over-rejecting +valid video streams due to reject_reference_pics_from_different_sps.patch. + * Modifying past changelog entries to indicate when vulnerabilities were +fixed: +- In 1.0.9-1, in total 11 CVE's. see #1004963 and #1014999 +- In 1.0.3-1, 1 CVE, see #1029396 + * drop unused Build-Depends: libjpeg-dev, libpng-dev and libxv-dev +(Closes: #981260) + + -- Tobias Frost Sun, 22 Jan 2023 13:19:20 +0100 + libde265 (1.0.9-1) unstable; urgency=medium * Add "Rules-Requires-Root: no". - * New upstream version 1.0.9 + * New upstream version 1.0.9. +Bisecting shows that this version fixed this CVES: + - CVE-2020-21598, CVE-2020-21600, CVE-2020-21602 (Closes: #1004963) + - CVE-2020-21595, CVE-2020-21597, CVE-2020-21599, CVE-2020-21601, + CVE-2020-21603, CVE-2020-21604, CVE-2020-21605, CVE-2020-21606 + (Closes: #1014999) * Remove patches now part of upstream release. * Bump "Standards-Version" to 4.6.1 * Add patch to provide "gl_VISIBILITY" macro. @@ -78,6 +106,7 @@ [ Joachim Bauch ] * Imported Upstream version 1.0.3 +This version fixes CVE-2020-21594. (Closes: #1029396) * Update patches for new upstream version. * Update symbols for new upstream version. * Update standards version and switch to debhelper 10. diff -Nru libde265-1.0.9/debian/control libde265-1.0.9/debian/control --- libde265-1.0.9/debian/control 2022-10-25 10:15:37.0 +0200 +++ libde265-1.0.9/debian/control 2023-01-22 13:04:40.0 +0100 @@ -7,14 +7,11 @@ Joachim Bauch Build-Depends: debhelper-compat (= 13), - libjpeg-dev, - libpng-dev, qtbase5-dev | libqt4-dev, libsdl-dev, libswscale-dev, libx11-dev, libxext-dev, - libxv-dev, pkg-config Rules-Requires-Root: no Standards-Version: 4.6.1 diff -Nru libde265-1.0.9/debian/.gitlab-ci.yml libde265-1.0.9/debian/.gitlab-ci.yml --- libde265-1.0.9/debian/.gitlab-ci.yml 1970-01-01 01:00:00.0 +0100 +++ libde265-1.0.9/debian/.gitlab-ci.yml 2023-01-21 18:01:58.0 +0100 @@ -0,0 +1,3 @@ +include: + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml + diff -Nru libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch --- libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch 1970-01-01 01:00:00.0 +0100 +++ libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch 2023-01-22 13:19:20.0 +0100 @@ -0,0 +1,340 @@ +Description: Don't update sps if they are only repeated +Origin: https://github.com/strukturag/libde265/pull/372 +From 51f07f132f29832e025a8b913b61cbd20257c5fc Mon Sep 17 00:00:00 2001 +From: Tobias Frost +Date: Fri, 13 Jan 2023 12:22:45 +0100 +Subject: [PATCH] Don't update sps if they are only repeated + +This is an attempt to improve the mitigations from #365 and #366 and picks up an idea I described at #345: + +> One way would be just to look at the pointers of the SPS (fast and easy, but +> may reject more than required), or investigate if the SPS used for the image +> generations are "compatible". + +This changes do exactly this: It (very conservativly) checks if the old and new sps have +identical information -- except the reference picture set, which I believe is supposed +to be updated by new sps'). If they are basically identical, the old sps will be +used instead of the new one, (of course, reference image set is updated from the new one) + +I'm using standalone operator== and helper functions to avoid changing ABI of the library; +if an ABI bump would be done, of course this should go to the respective classes. +--- + libde265/decctx.cc | 273 + + libde265/sps.cc| 6 + + 2 files changed, 279 insertions(+) + +diff --git a/libde265/decctx.cc b/libde265/decctx.cc +index 6701725f..b25d 100644 +--- a/libde265/decctx.cc
Bug#1029401: libde265: diff for NMU version 1.0.9-1.1
On 2023-01-22 13:30:00 +0100, Tobias Frost wrote: > Package: libde265 > Version: 1.0.9-1 > Severity: normal > Tags: patch pending > > > Dear maintainer, > > I've prepared an NMU for libde265 (versioned as 1.0.9-1.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks for working on the issue. Feel free to directly upload it to unstable / reschedule to DELAYED/0. Cheers > > Regards. > > diff -Nru libde265-1.0.9/debian/changelog libde265-1.0.9/debian/changelog > --- libde265-1.0.9/debian/changelog 2022-10-25 10:15:37.0 +0200 > +++ libde265-1.0.9/debian/changelog 2023-01-22 13:19:20.0 +0100 > @@ -1,7 +1,35 @@ > +libde265 (1.0.9-1.1) unstable; urgency=medium > + > + * Non-maintainer upload. > + * Apply patches to mitigate asan failures: > +reject_reference_pics_from_different_sps.patch and > +use_sps_from_the_image.patch. > + * Combined, this two patches fixes: > +- CVE-2022-43243, CVE-2022-43248, CVE-2022-43253 (Closes: #1025816) > +- CVE-2022-43235, CVE-2022-43236, CVE-2022-43237, CVE-2022-43238, > + CVE-2022-43239, CVE-2022-43240, CVE-2022-43241, CVE-2022-43242, > + CVE-2022-43244, CVE-2022-43250, CVE-2022-43252 (Closes: #1027179) > +- CVE-2022-47655 > + * Additional patch recycle_sps_if_possible.patch to avoid over-rejecting > +valid video streams due to > reject_reference_pics_from_different_sps.patch. > + * Modifying past changelog entries to indicate when vulnerabilities were > +fixed: > +- In 1.0.9-1, in total 11 CVE's. see #1004963 and #1014999 > +- In 1.0.3-1, 1 CVE, see #1029396 > + * drop unused Build-Depends: libjpeg-dev, libpng-dev and libxv-dev > +(Closes: #981260) > + > + -- Tobias Frost Sun, 22 Jan 2023 13:19:20 +0100 > + > libde265 (1.0.9-1) unstable; urgency=medium > >* Add "Rules-Requires-Root: no". > - * New upstream version 1.0.9 > + * New upstream version 1.0.9. > +Bisecting shows that this version fixed this CVES: > + - CVE-2020-21598, CVE-2020-21600, CVE-2020-21602 (Closes: #1004963) > + - CVE-2020-21595, CVE-2020-21597, CVE-2020-21599, CVE-2020-21601, > + CVE-2020-21603, CVE-2020-21604, CVE-2020-21605, CVE-2020-21606 > + (Closes: #1014999) >* Remove patches now part of upstream release. >* Bump "Standards-Version" to 4.6.1 >* Add patch to provide "gl_VISIBILITY" macro. > @@ -78,6 +106,7 @@ > >[ Joachim Bauch ] >* Imported Upstream version 1.0.3 > +This version fixes CVE-2020-21594. (Closes: #1029396) >* Update patches for new upstream version. >* Update symbols for new upstream version. >* Update standards version and switch to debhelper 10. > diff -Nru libde265-1.0.9/debian/control libde265-1.0.9/debian/control > --- libde265-1.0.9/debian/control 2022-10-25 10:15:37.0 +0200 > +++ libde265-1.0.9/debian/control 2023-01-22 13:04:40.0 +0100 > @@ -7,14 +7,11 @@ > Joachim Bauch > Build-Depends: > debhelper-compat (= 13), > - libjpeg-dev, > - libpng-dev, > qtbase5-dev | libqt4-dev, > libsdl-dev, > libswscale-dev, > libx11-dev, > libxext-dev, > - libxv-dev, > pkg-config > Rules-Requires-Root: no > Standards-Version: 4.6.1 > diff -Nru libde265-1.0.9/debian/.gitlab-ci.yml > libde265-1.0.9/debian/.gitlab-ci.yml > --- libde265-1.0.9/debian/.gitlab-ci.yml 1970-01-01 01:00:00.0 > +0100 > +++ libde265-1.0.9/debian/.gitlab-ci.yml 2023-01-21 18:01:58.0 > +0100 > @@ -0,0 +1,3 @@ > +include: > + - > https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml > + > diff -Nru libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch > libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch > --- libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch > 1970-01-01 01:00:00.0 +0100 > +++ libde265-1.0.9/debian/patches/recycle_sps_if_possible.patch > 2023-01-22 13:19:20.0 +0100 > @@ -0,0 +1,340 @@ > +Description: Don't update sps if they are only repeated > +Origin: https://github.com/strukturag/libde265/pull/372 > +From 51f07f132f29832e025a8b913b61cbd20257c5fc Mon Sep 17 00:00:00 2001 > +From: Tobias Frost > +Date: Fri, 13 Jan 2023 12:22:45 +0100 > +Subject: [PATCH] Don't update sps if they are only repeated > + > +This is an attempt to improve the mitigations from #365 and #366 and picks > up an idea I described at #345: > + > +> One way would be just to look at the pointers of the SPS (fast and easy, > but > +> may reject more than required), or investigate if the SPS used for the > image > +> generations are "compatible". > + > +This changes do exactly this: It (very conservativly) checks if the old and > new sps have > +identical information -- except the reference picture set, which I believe > is supposed > +to be updated by new sps'). If they are basically identical, the old sps > will be > +used instead of the new one, (of course, reference image set is
Bug#1029403: shorewall: fails to start with "Couldn't load match `iface':No such file or directory"
Package: shorewall
Version: 5.2.3.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
It seems Shorewall no longer works in Sid:
```
$ sudo shorewall start
Starting Shorewall
Initializing...
Setting up ARP filtering...
Setting up Route Filtering...
Setting up Martian Logging...
WARNING: Optional Interface wlp4s0 is not usable -- wlp not Started
Preparing iptables-restore input...
Running /sbin/iptables-restore --wait 60...
iptables-restore v1.8.9 (nf_tables): Couldn't load match `iface':No such file
or directory
Error occurred at line: 121
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
ERROR: iptables-restore Failed. Input is in
/var/lib/shorewall/.iptables-restore-input
Restoring Shorewall...
Initializing...
Setting up ARP filtering...
Setting up Route Filtering...
Setting up Martian Logging...
WARNING: Optional Interface wlp4s0 is not usable -- wlp not Started
iptables-restore v1.8.9 (nf_tables): Couldn't load match `iface':No such file
or directory
Error occurred at line: 118
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
done.
```
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages shorewall depends on:
ii bc 1.07.1-3+b1
ii debconf [debconf-2.0] 1.5.82
ii iproute2 6.1.0-1
ii iptables 1.8.9-2
ii perl 5.36.0-7
ii shorewall-core 5.2.3.4-1
ii sysvinit-utils [lsb-base] 3.06-2
Versions of packages shorewall recommends:
ii libnetfilter-cthelper0 1.0.1-1
Versions of packages shorewall suggests:
ii make 4.3-4.1
pn shorewall-doc
-- Configuration Files:
/etc/default/shorewall changed:
startup=0
OPTIONS=""
STARTOPTIONS="-f"
RESTARTOPTIONS=""
RELOADOPTIONS=""
STOPOPTIONS=""
INITLOG=/dev/null
SAFESTOP=1
/etc/shorewall/conntrack [Errno 13] Permission denied:
'/etc/shorewall/conntrack'
/etc/shorewall/params [Errno 13] Permission denied: '/etc/shorewall/params'
/etc/shorewall/shorewall.conf changed:
STARTUP_ENABLED=Yes
VERBOSITY=1
PAGER=
FIREWALL=
LOG_LEVEL="NFLOG"
BLACKLIST_LOG_LEVEL=
INVALID_LOG_LEVEL=
LOG_BACKEND=
LOG_MARTIANS=Yes
LOG_VERBOSITY=2
LOG_ZONE=Both
LOGALLNEW=
LOGFILE=/var/log/ulog/syslogemu.log
LOGFORMAT="%s %s "
LOGTAGONLY=No
LOGLIMIT="s:1/sec:10"
MACLIST_LOG_LEVEL="$LOG_LEVEL"
RELATED_LOG_LEVEL=
RPFILTER_LOG_LEVEL="NFLOG:rpfilter"
SFILTER_LOG_LEVEL="NFLOG:sfilter"
SMURF_LOG_LEVEL="NFLOG:smurf"
STARTUP_LOG=/var/log/shorewall-init.log
TCP_FLAGS_LOG_LEVEL="NFLOG:fcpflags"
UNTRACKED_LOG_LEVEL=
ARPTABLES=
CONFIG_PATH=":${CONFDIR}/shorewall:${SHAREDIR}/shorewall"
GEOIPDIR=/usr/share/xt_geoip/LE
IPTABLES=
IP=
IPSET=
LOCKFILE=
MODULESDIR=
NFACCT=
PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin"
PERL=/usr/bin/perl
RESTOREFILE=restore
SHOREWALL_SHELL=/bin/sh
SUBSYSLOCK=""
TC=
ACCEPT_DEFAULT="none"
BLACKLIST_DEFAULT="Broadcast(DROP),Multicast(DROP),dropNotSyn:$LOG_LEVEL,dropInvalid:$LOG_LEVEL,DropDNSrep:$LOG_LEVEL"
DROP_DEFAULT="Broadcast(DROP),Multicast(DROP)"
NFQUEUE_DEFAULT="none"
QUEUE_DEFAULT="none"
REJECT_DEFAULT="Broadcast(DROP),Multicast(DROP)"
RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
RSH_COMMAND='ssh ${root}@${system} ${command}'
ACCOUNTING=Yes
ACCOUNTING_TABLE=filter
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No
ADMINISABSENTMINDED=Yes
AUTOCOMMENT=Yes
AUTOHELPERS=No
AUTOMAKE=Yes
BALANCE_PROVIDERS=No
BASIC_FILTERS=No
BLACKLIST="NEW,INVALID,UNTRACKED"
CLAMPMSS=No
CLEAR_TC=Yes
COMPLETE=No
DEFER_DNS_RESOLUTION=Yes
DELETE_THEN_ADD=Yes
DETECT_DNAT_IPADDRS=No
DISABLE_IPV6=Yes
DOCKER=No
DONT_LOAD=
DYNAMIC_BLACKLIST=Yes
EXPAND_POLICIES=Yes
EXPORTMODULES=Yes
FASTACCEPT=No
FORWARD_CLEAR_MARK=
HELPERS=ftp
IGNOREUNKNOWNVARIABLES=No
IMPLICIT_CONTINUE=No
IPSET_WARNINGS=Yes
IP_FORWARDING=Keep
KEEP_RT_TABLES=No
MACLIST_TABLE=filter
MACLIST_TTL=
MANGLE_ENABLED=Yes
MARK_IN_FORWARD_CHAIN=No
MINIUPNPD=No
MULTICAST=No
MUTEX_TIMEOUT=60
NULL_ROUTE_RFC1918=No
OPTIMIZE=All
OPTIMIZE_ACCOUNTING=No
PERL_HASH_SEED=0
REJECT_ACTION=
RENAME_COMBINED=Yes
REQUIRE_INTERFACE=Yes
RESTART=restart
RESTORE_DEFAULT_ROUTE=Yes
RESTORE_ROUTEMARKS=Yes
RETAIN_ALIASES=No
ROUTE_FILTER=Yes
SAVE_ARPTABLES=No
SAVE_IPSETS=No
TC_ENABLED=Internal
TC_EXPERT=No
TC_PRIOMAP="2 3 3 3 2 3 1 1 2 2 2 2 2 2 2 2"
TRACK_PROVIDERS=Yes
TRACK_RULES=No
USE_DEFAULT_RT=Yes
USE_NFLOG_SIZE=No
USE_PHYSICAL_NAMES=No
USE_RT_NAMES=No
VERBOSE_MESSAGES=Yes
WARNOLDCAPVERSION=Yes
WORKAROUNDS=No
ZERO_MARKS=No
ZONE2ZONE=-
Bug#1029034: snack: includes non-free source
Hi Bastian, Thank you for the report! On Mon, Jan 16, 2023 at 9:33 PM Bastian Germann wrote: > > While the file part that is copied from formant.c is okay to be included in > Debian, the part from downsample.c is not. > Please repack the source package getting rid of the file. I don't think that I can remove this code without reimplementing its functionality somehow. So maybe it'd be better to drop the package from Debian. There are two packages that depend on tcl-snack: transcriber and wavesurfer. I guess they'd have to be removed from Debian as well. Cheers! -- Sergei Golovan
Bug#1029398: ben: "tracker --archs" is not honoured
On Sun, Jan 22, 2023 at 01:35:09PM +0100, Stéphane Glondu wrote: > Dear Adrian, > > Le 22/01/2023 à 12:33, Adrian Bunk a écrit : > > $ ben download --archs alpha --preferred-compression-format xz > > --mirror-binaries http://ftp.de.debian.org/debian-ports > > Downloading /tmp/Sources... > > Downloading /tmp/Packages_alpha... > > $ ben tracker --archs alpha -cd tracker > > Parsing /tmp/Sources... > > Parsing /tmp/Packages_amd64... > > Parsing /tmp/Packages_arm64... > > Parsing /tmp/Packages_armel... > > Parsing /tmp/Packages_armhf... > > Parsing /tmp/Packages_i386... > > Parsing /tmp/Packages_mips64el... > > Parsing /tmp/Packages_mipsel... > > Parsing /tmp/Packages_s390x... > > Parsing /tmp/Packages_ppc64el.. > > "ben tracker" indeed seems to ignore its "--archs" option... and probably > most of the options common to all ben frontends! Actually, it takes its > configuration from the so-called "global" configuration file. Did you > specify one (I see you've specified "-cd tracker", does it refer to > something you wrote yourself)? No, I have not created any configuration file (tracker/ just contains .ben files for testing/using trackers locally). > I'm afraid the default one is the Realase > Team's one [1], which doesn't seem useful elsewhere... Usually they are pretty useful for me since usually I am just using this for sending new/changed trackers as MRs to the release team. > [1] /usr/share/doc/ben/examples/tracker/global.conf > > By writing a custom global.conf (see comments in [1]), I can make "ben > tracker" work with debian-ports and only alpha... I ended up editing the defaults in lib/benl_base.ml and recompile ben, but that's just a short-term hack. > I see two approches to solving this bug: > - make the command-line options override the configuration specified in > global.conf > - reject command-line options when they are read in global.conf > > What do you think? >... The behaviour of "ben download" of having some sane defaults[1] or configuration file that can be overridden on the command line is IMHO pretty good, and I'd expect "ben tracker" to behave the same way. > Cheers, cu Adrian [1] but [2] would be a better compression default [2] https://salsa.debian.org/debian/ben/-/merge_requests/2
Bug#973990: Fixed in 3.11-1
On Tue, 10 Jan 2023 23:22:37 + Jeremy Sowden wrote: xtables-addons 3.9 did not support linux 5.9. The upgrade to 3.11 fixed But it's 3.23 on my machine: ``` $ LC_ALL=C apt policy xtables-addons-common xtables-addons-common: Installed: 3.23-1 Candidate: 3.23-1 Version table: *** 3.23-1 500 500 http://debian.mirror.vu.lt/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status ```
Bug#971068: linux-image-5.8.0-2-686-pae: Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation
Control: found -1 6.1.7-1 Can repro on the sid kernel, uname -a of Linux nabtop 6.1.0-2-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1 (2023-01-18) i686 GNU/Linux Log below. Backtrace is only trivially different. Best, наб -- >8 -- Jan 22 14:06:46 nabtop kernel: OOM killer disabled. Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000f] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb5aa1000-0xb5aa6fff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb5bba000-0xb5c0efff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb5d08000-0xb5f0efff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb5f18000-0xb5f1efff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb5f65000-0xb5f9efff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb5fe1000-0xb5ffefff] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Marking nosave pages: [mem 0xb600-0x] Jan 22 14:06:46 nabtop kernel: PM: hibernation: Basic memory bitmaps created Jan 22 14:06:46 nabtop kernel: PM: hibernation: Preallocating image memory Jan 22 14:06:46 nabtop kernel: PM: hibernation: Allocated 183519 pages for snapshot Jan 22 14:06:46 nabtop kernel: PM: hibernation: Allocated 734076 kbytes in 0.70 seconds (1048.68 MB/s) Jan 22 14:06:46 nabtop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 22 14:06:46 nabtop kernel: wifi1: deauthenticating from de:0d:17:ad:80:55 by local choice (Reason: 3=DEAUTH_LEAVING) Jan 22 14:06:46 nabtop kernel: ACPI: EC: interrupt blocked Jan 22 14:06:46 nabtop kernel: ACPI: PM: Preparing to enter system sleep state S4 Jan 22 14:06:46 nabtop kernel: ACPI: EC: event blocked Jan 22 14:06:46 nabtop kernel: ACPI: EC: EC stopped Jan 22 14:06:46 nabtop kernel: ACPI: PM: Saving platform NVS memory Jan 22 14:06:46 nabtop kernel: Disabling non-boot CPUs ... Jan 22 14:06:46 nabtop kernel: smpboot: CPU 1 is now offline Jan 22 14:06:46 nabtop kernel: PM: hibernation: Creating image: Jan 22 14:06:46 nabtop kernel: PM: hibernation: Need to copy 175700 pages Jan 22 14:06:46 nabtop kernel: PM: hibernation: Normal pages needed: 57765 + 1024, available pages: 167322 Jan 22 14:06:46 nabtop kernel: ACPI: PM: Restoring platform NVS memory Jan 22 14:06:46 nabtop kernel: ACPI: EC: EC started Jan 22 14:06:46 nabtop kernel: Enabling non-boot CPUs ... Jan 22 14:06:46 nabtop kernel: x86: Booting SMP configuration: Jan 22 14:06:46 nabtop kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 Jan 22 14:06:46 nabtop kernel: CPU1 is up Jan 22 14:06:46 nabtop kernel: ACPI: PM: Waking up from system sleep state S4 Jan 22 14:06:46 nabtop kernel: ACPI: EC: interrupt unblocked Jan 22 14:06:46 nabtop kernel: ACPI: EC: event unblocked Jan 22 14:06:46 nabtop kernel: usb usb1: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb2: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb4: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb3: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb6: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb7: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb8: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: usb usb5: root hub lost power or was reset Jan 22 14:06:46 nabtop kernel: sd 0:0:0:0: [sda] Starting disk Jan 22 14:06:46 nabtop kernel: iwlwifi :08:00.0: Radio type=0x1-0x2-0x0 Jan 22 14:06:46 nabtop kernel: iwlwifi :08:00.0: Radio type=0x1-0x2-0x0 Jan 22 14:06:46 nabtop kernel: [ cut here ] Jan 22 14:06:46 nabtop kernel: primary B assertion failure (expected off, current on) Jan 22 14:06:46 nabtop kernel: WARNING: CPU: 0 PID: 1038 at drivers/gpu/drm/i915/display/intel_display.c:476 assert_plane+0x9f/0xb0 [i915] Jan 22 14:06:46 nabtop kernel: Modules linked in: ghash_generic gf128mul gcm ccm algif_aead des_generic libdes ecb algif_skcipher bnep cmac md4 algif_hash af_alg binfmt_misc btusb btrtl btbcm btintel btmtk bluetooth jitterentropy_rng sha512_generic ctr drbg joydev ansi_cprng ecdh_generic ecc iwldvm mac80211 libarc4 iTCO_wdt intel_pmc_bxt snd_hda_codec_conexant iTCO_vendor_support uvcvideo watchdog snd_hda_codec_generic ledtrig_audio videobuf2_vmalloc videobuf2_memops i915 videobuf2_v4l2 nls_ascii snd_hda_intel iwlwifi videobuf2_common snd_intel_dspcfg drm_buddy snd_intel_sdw_acpi nls_cp437 videodev drm_display_helper snd_hda_codec snd_hda_core i2c_i801 cec vfat mc psmouse evdev wmi_bmof i2c_smbus snd_hwdep rc_core pcspkr cfg80211 sg ttm fat lpc_ich snd_pcm drm_kms_helper toshiba_acpi snd_timer industrialio snd sparse_keymap toshiba_bluetooth sky2 soundcore rfkill i2c_algo_bit
Bug#1028643: fontconfig
i can't downgrade - this is the only version available this fixed the color artifacts for me: remove /etc/fonts/conf.d/10-sub-pixel-rgb.conf
Bug#1029398: ben: "tracker --archs" is not honoured
Le 22/01/2023 à 13:48, Adrian Bunk a écrit : I'm afraid the default one is the Realase Team's one [1], which doesn't seem useful elsewhere... Usually they are pretty useful for me since usually I am just using this for sending new/changed trackers as MRs to the release team. Is your attempt to use "ben tracker" with debian-ports new? I am trying to understand why we get this bug report only now... I see two approches to solving this bug: - make the command-line options override the configuration specified in global.conf - reject command-line options when they are read in global.conf What do you think? ... The behaviour of "ben download" of having some sane defaults[1] or configuration file that can be overridden on the command line is IMHO pretty good, and I'd expect "ben tracker" to behave the same way. I'll see what I can do. [2] https://salsa.debian.org/debian/ben/-/merge_requests/2 Sorry for taking so much time to merge such a trivial change, but I didn't see the MR until now... There is so much noise in Salsa notifications that I ended up ignoring them altogether. Cheers, -- Stéphane
Bug#973990: Fixed in 3.11-1
I don't see errors in: `sudo apt install --reinstall xtables-addons-dkms`
Bug#1017619: nautilus-wipe: Fails to build with nautilus 43
Hi, FYI, Upstream has started work on that in a branch https://git.tuxfamily.org/wipetools/nautiluswipe.git/log/?h=nautilus-extension-4-wip. There are "alpha release" but I'm not sure this will be ready for bookworm. I can try to update it in experimental, though. Cheers, -- nodens
Bug#1029404: libncurses-dev: libncurses++w.a is not stripped on i386
Package: libncurses-dev Version: 6.3-2 Severity: normal Unfortunately libncurses++w.a is not stripped on i386 (and apparently on some other architecture[1], but I have not checked which one), because dh_strip skips it due to bug #875780[2]: , | $ perl -e 'print "@ARGV[0] not recognized as binary file\n" unless -B (@ARGV[0])' /usr/lib/i386-linux-gnu/libncurses++w.a | /usr/lib/i386-linux-gnu/libncurses++w.a not recognized as binary file ` This increases the installed size by some 500 kiB and also creates a reproducibility problem[3], because upstream (with good reasons) does not create deterministic archives, as mentioned in NEWS: , | 20151010 | + add workaround for breakage of POSIX makefiles by recent binutils | change. ` This problem has persisted at least since version 6.3-2 according to [3], and I was hoping that newer toolchains might stop exposing the dh_strip bug, but it seems we are stuck with it for Bookworm unless I find some workaround. Which is likely going to look quite ugly. :-( -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 1. https://udd.debian.org/lintian/?email1ncurses==html_error=on_warning=on_information=on_tag=unstripped-static-library#all 2. https://bugs.debian.org/875780 3. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/ncurses.html
Bug#973990: reassing 973990
reassing 973990 xtables-addons
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
Am 21.01.23 um 21:28 schrieb Otto Kekäläinen: Hi! I have been frantically trying to reproduce the issue you reported. It's trivial to reproduce: Have the versioned mariadb packages installed (say from unstable), then make an apt full-upgrade, which will install the new unversioned ones and forces the the versioned ones to be deinstalled. After that is done, purge the old, versioned packages. OpenPGP_signature Description: OpenPGP digital signature
Bug#1029398: ben: "tracker --archs" is not honoured
Le 22/01/2023 à 14:21, Adrian Bunk a écrit : I see two approches to solving this bug: - make the command-line options override the configuration specified in global.conf - reject command-line options when they are read in global.conf What do you think? ... The behaviour of "ben download" of having some sane defaults[1] or configuration file that can be overridden on the command line is IMHO pretty good, and I'd expect "ben tracker" to behave the same way. I'll see what I can do. Thanks! Actually, my initial understanding of what was happening was wrong. No default global.conf is read. I've pushed a tentative fix: https://salsa.debian.org/debian/ben/-/commit/7b882e6c090828babb677b258f1e64f287d631e8 Can you check that it does what you want? Cheers, -- Stéphane
Bug#1029408: rt-extension-assetautoname: autopkgtest failure
Source: rt-extension-assetautoname Version: 0.05-2 Severity: serious https://ci.debian.net/packages/r/rt-extension-assetautoname/unstable/amd64/ ... autopkgtest [12:08:48]: test autodep8-perl: /usr/share/pkg-perl-autopkgtest/runner runtime-deps autopkgtest [12:08:48]: test autodep8-perl: [--- # Failed test ' /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Looks like you failed 4 tests of 4. /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4 # Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 1 - /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully not ok 2 - /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output # Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) Tests: 4 Failed: 4) Failed tests: 1-4 Non-zero exit status: 4 Files=1, Tests=4, 0 wallclock secs ( 0.01 usr 0.00 sys + 0.07 cusr 0.01 csys = 0.09 CPU) Result: FAIL autopkgtest [12:08:49]: test autodep8-perl: ---] autopkgtest [12:08:49]: test autodep8-perl: - - - - - - - - - - results - - - - - - - - - - autodep8-perlFAIL non-zero exit status 1 autopkgtest [12:08:49]: test autodep8-perl: - - - - - - - - - - stderr - - - - - - - - - - # Failed test ' /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::AssetAutoName" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/AssetAutoName.pm in @INC (you may need to install the RT::Extension::AssetAutoName module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' #
Bug#1029409: RFS: quadrilateralcowboy/0~20160725-1 [ITP] -- first-person cyberpunk adventure game
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "quadrilateralcowboy": * Package name : quadrilateralcowboy Version : 0~20160725-1 Upstream contact : Brendon Chung * URL : https://www.blendogames.com/qc/ * License : GPL-3.0-with-additional-id-terms, Zlib, public-domain, SGI-B-1.1, RSA-MD, BSD-2-clause, Expat, MIT * Vcs : https://salsa.debian.org/jayaddison/quadrilateralcowboy/ Section : contrib/games The source builds the following binary packages: quadrilateralcowboy - first-person cyberpunk adventure game To access further information about this package, please visit the following URL: https://mentors.debian.net/package/quadrilateralcowboy/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/contrib/q/quadrilateralcowboy/quadrilateralcowboy_0~20160725-1.dsc Changes for the initial release: quadrilateralcowboy (0~20160725-1) UNRELEASED; urgency=medium . * Initial release. Closes: #1026277 Regards, James Addison
Bug#1029410: rt-extension-elapsedbusinesstime: autopkgtest failure
Source: rt-extension-elapsedbusinesstime Version: 0.05-1 Severity: serious https://ci.debian.net/packages/r/rt-extension-elapsedbusinesstime/unstable/amd64/ ... autopkgtest [12:10:28]: test autodep8-perl: /usr/share/pkg-perl-autopkgtest/runner runtime-deps autopkgtest [12:10:28]: test autodep8-perl: [--- # Failed test ' /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/ElapsedBusinessTime.pm in @INC (you may need to install the RT::Extension::ElapsedBusinessTime module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/ElapsedBusinessTime.pm in @INC (you may need to install the RT::Extension::ElapsedBusinessTime module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Looks like you failed 4 tests of 4. /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4 # Can't locate RT/Extension/ElapsedBusinessTime.pm in @INC (you may need to install the RT::Extension::ElapsedBusinessTime module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 1 - /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 exited successfully not ok 2 - /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 produced no (non-whitelisted) output # Can't locate RT/Extension/ElapsedBusinessTime.pm in @INC (you may need to install the RT::Extension::ElapsedBusinessTime module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 exited successfully not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 produced no (non-whitelisted) output Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) Tests: 4 Failed: 4) Failed tests: 1-4 Non-zero exit status: 4 Files=1, Tests=4, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.07 cusr 0.01 csys = 0.10 CPU) Result: FAIL ...
Bug#1029413: dracut: no-argument lsinitrd broken (says "the default image '' cannot be accessed!")
Package: dracut Version: 059-3 Severity: normal Dear Maintainer, -- >8 -- $ ls /boot/ config-5.5.0-1-amd64 gnumach initrd.img-5.5.0-1-amd64 System.map-5.5.0-1-amd64 vmlinuz-5.5.0-1-amd64 config-6.0.0-6-amd64 gnumach-1.8-486-dbg.gz initrd.img-6.0.0-6-amd64 System.map-6.0.0-6-amd64 vmlinuz-6.0.0-6-amd64 config-6.1.0-2-amd64 grubinitrd.img-6.1.0-2-amd64 System.map-6.1.0-2-amd64 vmlinuz-6.1.0-2-amd64 $ lsinitrd No specified and the default image '' cannot be accessed! Usage: lsinitrd [options] [ [ [ [...] ]]] Usage: lsinitrd [options] -k -h, --help print a help message and exit. -s, --size sort the contents of the initramfs by size. -m, --mod list modules. -f, --fileprint the contents of . --unpackunpack the initramfs, instead of displaying the contents. If optional filenames are given, will only unpack specified files, else the whole image will be unpacked. Won't unpack anything from early cpio part. --unpackearly unpack the early microcode part of the initramfs. Same as --unpack, but only unpack files from early cpio part. -v, --verbose unpack verbosely. -k, --kver inspect the initramfs of . -- >8 -- All those images were autogenerated; this works on bullseye. наб -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: amd64, i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/2 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 dracut depends on: ii dracut-core 059-3 dracut recommends no packages. Versions of packages dracut suggests: pn dracut-network -- no debconf information signature.asc Description: PGP signature
Bug#1027903: Co-maintainer access
Hi Jonathan! Thanks for packaging this one! Is it OK for you to move the Salsa repo to of kodi-game-libretro to https://salsa.debian.org/multimedia-team/kodi-media-center ? Then all Kodi stuff will be in one place :) If you dont want to move it, please grant me the co-maintainer access so I can keep the addon in sync with all others. Cheers! -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
Bug#1029415: linux-image-6.1.0-1-amd64: Macmini3,1(Late 2009) freezes few minutes after boot and login with Kernel Linux 6
Package: src:linux Version: 6.1.4-1 Severity: important Dear Maintainer, since Linux kernel 6 my Macmini3,1 started to freeze few minutes after boot and login (often I have time to open terminal emulator and run dmesg); I note that system freezes since can't move the mouse but also led on Caps key doesn't turn on. I'll try to upload a dmesg with Linux Kernel 6.1.6 that I've compiled since maybe with this one I have more time... -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Apple Inc. product_name: Macmini3,1 product_version: 1.0 chassis_vendor: Apple Inc. chassis_version: Mac-F22C86C8 bios_vendor: Apple Inc. bios_version: MM31.88Z.00AD.B00.0907171535 board_vendor: Apple Inc. board_name: Mac-F22C86C8 board_version: ** PCI devices: 00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a82] (rev b1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nForce2_smbus Kernel modules: i2c_nforce2, nv_tco 00:03.3 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a89] (rev b1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1) (prog-if 20 [EHCI]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:06.0 USB controller [0c03]: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1) (prog-if 10 [OHCI]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:06.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1) (prog-if 20 [EHCI]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:08.0 Audio device [0403]: NVIDIA Corporation MCP79 High Definition Audio [10de:0ac0] (rev b1) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Bridge [10de:0aab] (rev b1) (prog-if 01 [Subtractive decode]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn- Capabilities: 00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP79 Ethernet [10de:0ab0] (rev b1) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: forcedeth Kernel modules: forcedeth 00:0b.0 SATA controller [0106]: NVIDIA Corporation MCP79 AHCI Controller [10de:0ab9] (rev b1) (prog-if 01 [AHCI 1.0]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:10.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0aa0] (rev b1) (prog-if 00 [Normal decode]) Subsystem: NVIDIA Corporation MCP79 PCI Express Bridge [10de:] Control: I/O+ Mem+ BusMaster+
Bug#1029432: ITP: metaeuk -- sensitive, high-throughput gene discovery and annotation for metagenomics
Package: wnpp Severity: wishlist Owner: Sascha Steinbiss X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org * Package name: metaeuk Version : 6-a5d39d9 Upstream Author : Eli Levy Karin and co-authors * URL : https://github.com/soedinglab/metaeuk * License : GPL3 Programming Lang: C++ Description : sensitive, high-throughput gene discovery and annotation for metagenomics MetaEuk is a modular toolkit designed for large-scale gene discovery and annotation in eukaryotic metagenomic contigs. MetaEuk combines the fast and sensitive homology search capabilities of MMseqs2 with a dynamic programming procedure to recover optimal exons sets. It reduces redundancies in multiple discoveries of the same gene and resolves conflicting gene predictions on the same strand. This is packaged as a dependency of busco and will be maintained by the Debian Med team.
Bug#1029426: lnav: FTBFS in bookworm (undeclared build-dependency on tzdata)
Control: tags -1 + unreproducible help Hi Santiago, I cannot reproduce right now the FTBFS on a amd64 chroot. Can we exclude it was not a transiet issue? The build log contains suspicous premature EOF while running the tests. Might you try once to build it on your side? I will try next on a porterbox as well with another fresh chroot. Regards, Salvatore
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Package: src:feynmf Version: 1.08-13 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules build-indep dh_testdir mkdir -p "/<>/.texmf-var" /usr/bin/make MP=mpost MF=mf-nowin all manual.ps make[1]: Entering directory '/<>' latex feynmf.ins This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./feynmf.ins LaTeX2e <2022-06-01> patch level 5 L3 programming layer <2022-08-30> (/usr/share/texlive/texmf-dist/tex/latex/base/docstrip.tex Utility: `docstrip' v2.6a <2020-11-23> English documentation<2020-11-23> ** * This program converts documented macro-files into fast * * loadable files by stripping off (nearly) all comments! * ** * No Configuration file found, using default settings. * (./feynmf.ins Generating style file feynmf.sty for the feynmf package: Generating file(s) ./feynmf.sty Processing file feynmf.dtx (style) -> feynmf.sty File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating Metafont base feynmf.mf: Generating file(s) ./feynmf.mf Processing file feynmf.dtx (base) -> feynmf.mf File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating style file feynmp.sty for the MetaPost version: Generating file(s) ./feynmp.sty Processing file feynmf.dtx (style,mp) -> feynmp.sty File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating MetaPost base feynmp.mp: Generating file(s) ./feynmp.mp Processing file feynmf.dtx (base,mp) -> feynmp.mp File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating driver file for manual fmfman.drv: Generating file(s) ./fmfman.drv Processing file feynmf.dtx (driver,manual) -> fmfman.drv File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating alternate MetaPost driver file fmfmanps.drv: Generating file(s) ./fmfmanps.drv Processing file feynmf.dtx (driver,manual,mp) -> fmfmanps.drv File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating driver file for documentation feynmf.drv: Generating file(s) ./feynmf.drv Processing file feynmf.dtx (driver) -> feynmf.drv File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 Generating alternate MetaPost driver file feynmp.drv: Generating file(s) ./feynmp.drv Processing file feynmf.dtx (driver,mp) -> feynmp.drv File feynmf.dtx ended by \endinput. Lines processed: 7793 Comments removed: 5055 Comments passed: 19 Codelines passed: 2521 *** * * To finish the installation you have to move the files * * o feynmf.sty into a directory searched by TeX * o feynmf.mf into a directory searched by Metafont * o feynmp.sty into a directory searched by TeX * o feynmp.mp into a directory searched by MetaPost * * You can remove the latter two if you don't have * John Hobby's MetaPost system. Optionally you can copy the * files fmfman.dtx and fmfmanps.drv into a directory searched by * TeX, so that users can print a copy of the documentation. * *** ) Overall statistics: Files processed: 8 Lines processed: 62344 Comments removed: 40440 Comments passed: 152 Codelines passed: 20168 ) ) No pages of output. Transcript written on feynmf.log. pod2man --section 1 \ --release "FeynMF Version 1.08" \ --center "Contributed LaTeX Utilities" feynmf.pl > feynmf.1 latex --output-comment="" fmfmanps.drv This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./fmfmanps.drv LaTeX2e <2022-06-01> patch level 5 L3 programming layer <2022-08-30> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2021/10/04 v1.4n Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty) (/usr/share/texlive/texmf-dist/tex/latex/mflogo/mflogo.sty)
Bug#1029438: auctex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)
Package: src:auctex Version: 12.2-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep /bin/bash: line 1: git: command not found /bin/bash: line 1: git: command not found dh binary-indep --exclude .eperl --with tex dh_update_autotools_config -i -O--exclude=.eperl dh_autoreconf -i -O--exclude=.eperl configure.ac:38: warning: The macro `AC_FD_CC' is obsolete. configure.ac:38: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:26: EMACS_PATH_PREFIX is expanded from... aclocal.m4:36: EMACS_PROG_EMACS is expanded from... configure.ac:38: the top level configure.ac:40: warning: The macro `AC_FD_CC' is obsolete. configure.ac:40: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:100: EMACS_CHECK_VERSION is expanded from... configure.ac:40: the top level configure.ac:44: warning: The macro `AC_FD_CC' is obsolete. configure.ac:44: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:494: VALID_BUILD_DIR is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from... configure.ac:44: the top level configure.ac:44: warning: The macro `AC_FD_CC' is obsolete. configure.ac:44: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:494: VALID_BUILD_DIR is expanded from... lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from... configure.ac:44: the top level configure.ac:60: warning: The macro `AC_FD_CC' is obsolete. configure.ac:60: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:126: EMACS_EXAMINE_INSTALLATION_DIR is expanded from... aclocal.m4:160: EMACS_PATH_LISPDIR is expanded from... configure.ac:60: the top level configure.ac:102: warning: The macro `AC_FD_CC' is obsolete. configure.ac:102: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:102: the top level configure.ac:109: warning: The macro `AC_FD_CC' is obsolete. configure.ac:109: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:109: the top level configure.ac:112: warning: The macro `AC_FD_CC' is obsolete. configure.ac:112: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:112: the top level configure.ac:118: warning: The macro `AC_FD_CC' is obsolete. configure.ac:118: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:118: the top level configure.ac:131: warning: The macro `AC_FD_CC' is obsolete. configure.ac:131: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... configure.ac:131: the top level configure.ac:152: warning: The macro `AC_FD_CC' is obsolete. configure.ac:152: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:26: EMACS_PATH_PREFIX is expanded from... aclocal.m4:185: TEX_PATH_TEXMFDIR is expanded from... configure.ac:152: the top level configure.ac:152: warning: The macro `AC_FD_CC' is obsolete. configure.ac:152: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:126: EMACS_EXAMINE_INSTALLATION_DIR is expanded from... aclocal.m4:185: TEX_PATH_TEXMFDIR is expanded from... configure.ac:152: the top level configure.ac:157: warning: The macro `AC_FD_CC' is obsolete. configure.ac:157: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:157: the top level configure.ac:188: warning: The macro `AC_FD_CC' is obsolete. configure.ac:188: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13:
Bug#1029440: opm-common: FTBFS in bookworm (cc1plus: fatal error: [...]/builtin_pybind11.cpp: No such file or directory)
Package: src:opm-common Version: 2022.10+ds-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --with python3 dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DOPM_ENABLE_PYTHON=1 -DOPM_INSTALL_PYTHON=1 -DPYTHON_EXECUTABLE=/usr/bin/python3 -DOPM_INSTALL_COMPILED_PYTHON=OFF -DOPM_ENABLE_EMBEDDED_PYTHON=1 -DBUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_DOCDIR=share/doc/libopm-common -DPYTHON_INSTALL_PREFIX=lib/python3/dist-packages -DOPM_INSTALL_COMPILED_PYTHON=OFF -DUSE_RUNPATH=OFF -DWITH_NATIVE=OFF -DUSE_MPI=ON -DUSE_BASH_COMPLETIONS_DIR=ON -DOPM_BINARY_PACKAGE_VERSION=" lsb_release -r | sed "s/.*:\s*\([^\s]*\).*/\1/": 2022.10+ds-1" cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOPM_ENABLE_PYTHON=1 -DOPM_INSTALL_PYTHON=1 -DPYTHON_EXECUTABLE=/usr/bin/python3 -DOPM_INSTALL_COMPILED_PYTHON=OFF -DOPM_ENABLE_EMBEDDED_PYTHON=1 -DBUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_DOCDIR=share/doc/libopm-common -DPYTHON_INSTALL_PREFIX=lib/python3/dist-packages -DOPM_INSTALL_COMPILED_PYTHON=OFF -DUSE_RUNPATH=OFF -DWITH_NATIVE=OFF -DUSE_MPI=ON -DUSE_BASH_COMPLETIONS_DIR=ON "-DOPM_BINARY_PACKAGE_VERSION= lsb_release -r | sed s/.*:s*([^s]*).*/1/: 2022.10+ds-1" .. -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Deprecation Warning at cmake/Modules/OpmInit.cmake:26 (cmake_policy): The OLD behavior for policy CMP0026 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. Call Stack (most recent call first): CMakeLists.txt:58 (OpmSetPolicies) CMake Warning at cmake/Modules/Findopm-tests.cmake:26 (message): opm-tests not found - integration tests using opm-tests will be skipped. Call Stack (most recent call first): CMakeLists.txt:62 (include) -- Performing Test HAVE_C99 -- Performing Test HAVE_C99 - Success -- Found C99: -std=c99 -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found suitable version "1.74.0", minimum required is "1.44.0") found components: system unit_test_framework -- Performing Test HAVE_CJSON -- Performing Test HAVE_CJSON - Success -- Found cjson: /usr/include/cjson -- Found Python3: /usr/bin/python3 (found version "3.10.9") found components: Interpreter Development Development.Module Development.Embed -- Performing Test HAS_FLTO -- Performing Test HAS_FLTO - Success -- Found pybind11: /usr/include (found version "2.10.2") -- Performing Test HAVE_ATTRIBUTE_ALWAYS_INLINE -- Performing Test HAVE_ATTRIBUTE_ALWAYS_INLINE - Success -- Performing Test HAS_ATTRIBUTE_UNUSED -- Performing Test HAS_ATTRIBUTE_UNUSED - Success -- Performing Test HAS_ATTRIBUTE_DEPRECATED -- Performing Test HAS_ATTRIBUTE_DEPRECATED - Success -- Performing Test HAS_ATTRIBUTE_DEPRECATED_MSG -- Performing Test HAS_ATTRIBUTE_DEPRECATED_MSG - Success -- CMake version: 3.25.1 -- Linux distribution: Debian GNU/Linux bookworm/sid -- Target architecture: x86_64 -- Found Git: /usr/bin/git (found version "2.39.0") -- Source code repository: not found! -- GNU C++ compiler version: 12.2.0 -- Linker: ld 2.39.50.20221224 Processing opm_defaults opm-common -- Precompiled headers: disabled -- Build type: None -- Found OpenMP_C: -fopenmp (found version "4.5") -- Found OpenMP_CXX: -fopenmp (found version "4.5") -- Found OpenMP: TRUE (found version "4.5") -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE -- Checking to see if CXX compiler accepts flag -pthread -- Checking to see if CXX compiler accepts flag -pthread - yes -- Could NOT find CppCheck (missing: CPPCHECK_PROGRAM) -- Disabling clang-check as CMAKE_EXPORT_COMPILE_COMMANDS is
Bug#1027952: pcre2 causes crashes in link-grammar
On Sat, 07 Jan 2023 at 22:07:31 +, Matthew Vernon wrote: > I'm struggling a bit here; I wanted to try and bisect pcre2 upstream commits > to see where this bug might have been introduced (or get to the bottom of > what link-grammar's test is doing wrong, I see they've been troublesome in > the past cf #975696). I tried using AddressSanitizer to get more information, which might be helpful. I used a bookworm podman container for this, and for simplicity I'm using uid 0 in the container, but you could probably do the same in a Docker container, a VM or a chroot and as an unprivileged user. $ podman run -it --rm debian:bookworm-slim # apt install --no-install-recommends devscripts build-essential # echo "deb-src http://deb.debian.org/debian bookworm main" >> /etc/apt/sources.list # cd /root # apt update # apt source pcre2 link-grammar # echo "deb-src http://deb.debian.org/debian sid main" >> /etc/apt/sources.list # apt source pcre2 # apt build-dep pcre2 link-grammar # cd /root/pcre2-10.40 # debuild -eASAN_OPTIONS=detect_leaks=0 -eDEB_BUILD_OPTIONS="noopt sanitize=+address,+undefined" -us -uc -b # cd /root/pcre2-10.42 # debuild -eASAN_OPTIONS=detect_leaks=0 -eDEB_BUILD_OPTIONS="noopt sanitize=+address,+undefined" -us -uc -b # cd /root/link-grammar-5.11.0~dfsg # debuild -eASAN_OPTIONS=detect_leaks=0 -eDEB_BUILD_OPTIONS="noopt sanitize=+address,+undefined" -eLD_PRELOAD=libasan.so.8 -eLD_LIBRARY_PATH=/root/pcre2-10.40/debian/tmp/usr/lib/x86_64-linux-gnu -us -uc -b ... tests pass ... # debuild -eASAN_OPTIONS=detect_leaks=0 -eDEB_BUILD_OPTIONS="noopt sanitize=+address,+undefined" -eLD_PRELOAD=libasan.so.8 -eLD_LIBRARY_PATH=/root/pcre2-10.42/debian/tmp/usr/lib/x86_64-linux-gnu -us -uc -b ... tests fail ... (Note that the order of options to debuild is significant, debuild option -e must come before dpkg-buildpackage options like -us, -uc, -b.) With those steps, I get AddressSanitizer reporting a heap buffer overflow when the test tries to match a regular expression, and a similar error in the multi-java test. A roughly equivalent setup with the upstream libpcre also "works" (by which I mean, fails). AddressSanitizer output below. # apt install git # git clone https://github.com/PCRE2Project/pcre2 # cd /root/pcre2 # git checkout pcre2-10.42 # ./autogen.sh # ./configure CFLAGS="-fsanitize=address -fno-omit-frame-pointer -fsanitize=undefined" --prefix=/usr # make # ( cd /root/link-grammar-5.11.0~dfsg && debuild -eASAN_OPTIONS=detect_leaks=0 -eDEB_BUILD_OPTIONS="noopt sanitize=+address,+undefined" -eLD_PRELOAD=libasan.so.8 -eLD_LIBRARY_PATH=/root/pcre2/.libs -us -uc -b ) ... tests fail ... The same setup with pcre2-10.40 passes tests. The link-grammar build later fails when using the sanitizers, because it uses d-shlibs which is basically an anti-pattern (#902605), but that's enough to be able to bisect (in progress). smcv === link-grammar 5.11.0: tests/test-suite.log === # TOTAL: 5 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: multi-thread == = ==107299==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60e00708 at pc 0x7f8c46092bb4 bp 0x7f8c3cb87800 sp 0x7f8c3cb877f8 READ of size 1 at 0x60e00708 thread T10 #0 0x7f8c46092bb3 in match (/root/pcre2/.libs/libpcre2-8.so.0+0x492bb3) #1 0x7f8c460b4eac in pcre2_match_8 (/root/pcre2/.libs/libpcre2-8.so.0+0x4b4eac) #2 0x7f8c474930e3 in reg_match dict-common/regex-morph.c:219 #3 0x7f8c47494753 in match_regex dict-common/regex-morph.c:405 #4 0x7f8c475b2997 in regex_guess tokenize/tokenize.c:413 #5 0x7f8c475ca258 in separate_word tokenize/tokenize.c:2709 #6 0x7f8c475cdf73 in separate_sentence tokenize/tokenize.c:3116 #7 0x7f8c4745fc07 in sentence_split link-grammar/api.c:494 #8 0x55b9169165b8 in parse_one_sent tests/multi-thread.cc:34 #9 0x55b9169177e9 in parse_sents tests/multi-thread.cc:119 #10 0x55b9169209c2 in void std::__invoke_impl(std::__invoke_other, void (*&&)(Dictionary_s*, Parse_Options_s*, int, int), Dictionary_s*&&, Parse_Options_s*&&, int&&, int&&) /usr/include/c++/12/bits/invoke.h:61 #11 0x55b91692056f in std::__invoke_result::type std::__invoke(void (*&&)(Dictionary_s*, Parse_Options_s*, int, int), Dictionary_s*&&, Parse_Options_s*&&, int&&, int&&) /usr/include/c++/12/bits/invoke.h:96 #12 0x55b91691fffb in void std::thread::_Invoker >::_M_invoke<0ul, 1ul, 2ul, 3ul, 4ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul, 4ul>) /usr/include/c++/12/bits/std_thread.h:252 #13 0x55b91691fc59 in std::thread::_Invoker >::operator()() /usr/include/c++/12/bits/std_thread.h:259 #14 0x55b91691fc11 in std::thread::_State_impl > >::_M_run() /usr/include/c++/12/bits/std_thread.h:210 #15 0x7f8c46ed44a2
Bug#1029446: libghc-diagrams-dev: Depends: libghc-diagrams-core-dev (< 1.5) but 1.5.0.1-1+b1 is to be installed
Package: libghc-diagrams-dev Version: 1.4-5 Severity: serious Tags: bookworm sid The following packages have unmet dependencies: libghc-diagrams-dev : Depends: libghc-diagrams-core-dev (< 1.5) but 1.5.0.1-1+b1 is to be installed
Bug#1024012: Two other packages are now failing their debci tests on i386 (Was: Bug#1024012: [joshuaulrich/xts] Unit test failure when running on i386 (Issue #384))
According to tracker[1] there are now r-cran-bbmle[2] failing with
--- profbound.Rout.save_2023-01-22 11:28:41.154493354 +
+++ profbound.Rout_ 2023-01-22 11:28:41.158493203 +
@@ -40,6 +40,9 @@
+ method="L-BFGS-B")
>
> pp <- profile(fit2,prof.lower=-0.2)
+Warning message:
+In mle2(minuslogl = function (a = NULL, b = NULL) :
+ convergence failure: code=52 (ERROR: ABNORMAL_TERMINATION_IN_LNSRCH)
> stopifnot(min(subset(as.data.frame(pp),param=="b")$par.vals.b)==-0.2)
> ## note that b does go below -0.2 when profiling a ...
> options(old_opt)
and r-cran-rpf[3] failing with
══ Failed tests
── Failure ('test-fit.R:116'): fit w/ mcar ─
`stat` not equal to `Estat`.
1/20 mismatches
[5] 4.42 - 6.69 == -2.27
[ FAIL 1 | WARN 0 | SKIP 0 | PASS 381 ]
I have no idea what to do sensibly (except patching out the said tests).
Kind regards
Andreas.
[1] https://tracker.debian.org/pkg/r-base
[2]
https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-bbmle/30587711/log.gz
[3]
https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-rpf/30580781/log.gz
--
http://fam-tille.de
Bug#1029447: unmuting audio breaks video playing in browsers
Package: wireplumber Version: 0.4.13-1 Severity: grave If I replace pipewire-media-session with wireplumber then playing video in browsers (e.g. Youtube and other similar sites, or even just embedded tags) stutters and stops. Just pressing the mute button in the video player makes video work as usual, 100% reproducibile. I have reproduced this both with Firefox and Chrome. Installing again pipewire-media-session and rebooting fixed this. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 wireplumber depends on: ii init-system-helpers 1.65.2 ii libc6 2.36-8 ii libglib2.0-0 2.74.5-1 ii libpipewire-0.3-0 0.3.64-2 pn libwireplumber-0.4-0 ii pipewire 0.3.64-2 Versions of packages wireplumber recommends: pn pipewire-pulse Versions of packages wireplumber suggests: ii libspa-0.2-bluetooth 0.3.64-2 pn wireplumber-doc -- ciao, Marco signature.asc Description: PGP signature
Bug#1028721: khard: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpyt_g2chc', '--quiet', 'tom
Hi,
I tried to reproduce the issue, but the package just built fine. Maybe
it was a temporary issue with setuptools_scm? #1027947
On 2023-01-14 13:40+0100, Lucas Nussbaum wrote:
Source: khard
Version: 0.18.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
make[1]: Entering directory '/<>'
dh_auto_clean
I: pybuild base:240: python3.10 setup.py clean
/usr/lib/python3/dist-packages/setuptools/installer.py:27:
SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements
should be satisfied by a PEP 517 installer.
warnings.warn(
WARNING: The wheel package is not available.
/usr/bin/python3.10: No module named pip
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in
fetch_build_egg
subprocess.check_call(cmd)
File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpyt_g2chc',
'--quiet', 'tomli>=1.0.0']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/<>/setup.py", line 13, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 86, in setup
_install_setup_requires(attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 80, in
_install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 874, in
fetch_build_eggs
resolved_dists = pkg_resources.working_set.resolve(
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
dist = best[req.key] = env.best_match(
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1075, in
best_match
return self.obtain(req, installer)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1087, in
obtain
return installer(requirement)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 944, in
fetch_build_egg
return fetch_build_egg(self, req)
File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 84, in
fetch_build_egg
raise DistutilsError(str(e)) from e
distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpyt_g2chc',
'--quiet', 'tomli>=1.0.0']' returned non-zero exit status 1.
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
python3.10 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.10 3.11"
returned exit code 13
make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/01/13/khard_0.18.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--
Félix
signature.asc
Description: PGP signature
Bug#1029404: libncurses-dev: libncurses++w.a is not stripped on i386
On 2023-01-22 14:24 +0100, Sven Joachim wrote: > Package: libncurses-dev > Version: 6.3-2 > Severity: normal > > Unfortunately libncurses++w.a is not stripped on i386 (and apparently on > some other architecture[1], but I have not checked which one), because > dh_strip skips it due to bug #875780[2]: Looked up the archive now and found that the other architecture is mips64el, also with libncurses++w.a.
Bug#999988: postfix: depends on obsolete pcre3 library
On January 22, 2023 12:22:21 PM UTC, TOKORO Yuuki wrote: >Dear maintainer, > >postfix package in unstable is now version 3.7. >Could you change dependencies pcre3 to pcre2? I looked at this yesterday actually. At this point I'd like to see the issues with the current release in Unstable get resolved first. I don't want to get postfix entangled with it. Feel free to ping again once that's sorted. Scott K
Bug#1029411: rt-extension-mergeusers: autopkgtest failure
Source: rt-extension-mergeusers Version: 1.06-1 Severity: serious https://ci.debian.net/packages/r/rt-extension-mergeusers/unstable/amd64/ ... autopkgtest [12:12:08]: test autodep8-perl: /usr/share/pkg-perl-autopkgtest/runner runtime-deps autopkgtest [12:12:08]: test autodep8-perl: [--- # Failed test ' /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the RT::Extension::MergeUsers module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the RT::Extension::MergeUsers module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Looks like you failed 4 tests of 4. /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4 # Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the RT::Extension::MergeUsers module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 1 - /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully not ok 2 - /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output # Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the RT::Extension::MergeUsers module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) Tests: 4 Failed: 4) Failed tests: 1-4 Non-zero exit status: 4 Files=1, Tests=4, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.08 cusr 0.00 csys = 0.10 CPU) Result: FAIL autopkgtest [12:12:09]: test autodep8-perl: ---] autopkgtest [12:12:09]: test autodep8-perl: - - - - - - - - - - results - - - - - - - - - - autodep8-perlFAIL non-zero exit status 1 autopkgtest [12:12:09]: test autodep8-perl: - - - - - - - - - - stderr - - - - - - - - - - # Failed test ' /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the RT::Extension::MergeUsers module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Failed test 'env
Bug#1029412: rt-extension-resetpassword: autopkgtest failure
Source: rt-extension-resetpassword Version: 1.07-1 Severity: serious https://ci.debian.net/packages/r/rt-extension-resetpassword/unstable/amd64/ ... autopkgtest [12:13:07]: test autodep8-perl: [--- # Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install the RT::Extension::ResetPassword module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install the RT::Extension::ResetPassword module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Looks like you failed 4 tests of 4. /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4 # Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install the RT::Extension::ResetPassword module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 1 - /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully not ok 2 - /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output # Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install the RT::Extension::ResetPassword module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) Tests: 4 Failed: 4) Failed tests: 1-4 Non-zero exit status: 4 Files=1, Tests=4, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.11 cusr 0.01 csys = 0.14 CPU) Result: FAIL autopkgtest [12:13:08]: test autodep8-perl: ---] autopkgtest [12:13:08]: test autodep8-perl: - - - - - - - - - - results - - - - - - - - - - autodep8-perlFAIL non-zero exit status 1 autopkgtest [12:13:08]: test autodep8-perl: - - - - - - - - - - stderr - - - - - - - - - - # Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106. # Failed test ' /usr/bin/perl -w -M"RT::Extension::ResetPassword" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110. # Structures begin differing at: # $got->[0] = 'Can't locate RT/Extension/ResetPassword.pm in @INC (you may need to install the RT::Extension::ResetPassword module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). # ' # $expected->[0] = Does not exist # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w
Bug#971739: Sioyek not migrating to testing because of britney limitation/bug
Hi release managers, A few days ago sioyek was uploaded to unstable. It builds on all architectures where its dependencies are available according to buildd. However, its migration to testing is blocked because britney seems to think that sphinx:native is not satisfiable on any architecture. sphinx is a virtual package, provided by python3-sphinx. Its description says to "Build-depend on sphinx if your package uses /usr/bin/sphinx-* executables." The native architecture specifier is necessary to allow cross-building. This is bug #971739, I think, but I cannot find online what steps to take next. Should I switch the dependency to python3-sphinx:native? Or is this something that can be overridden someway? Thanks for your help in advance. -- Groet, Regards, Victor Westerhuis OpenPGP_signature Description: OpenPGP digital signature
Bug#1029352: netcfg: broken ifupdown support for ethernet interface
Similar Trouble here: A smoothly running Debian-Bookworm system here with ethernet eno1 managed by ifupdown, wlp1s0 is managed by NetworkManager. After today's bigger Update consisting of: qttranslations5-l10n:amd64 (5.15.7-2, 5.15.8-2), qtbase5-dev-tools:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5quickcontrols2-5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-shapes:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-layouts:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5core5a:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-window2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qt5-gtk-platformtheme:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), solaar:amd64 (1.1.8+dfsg-1, 1.1.8+dfsg-2), qml-module-qt-labs-settings:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), python3-pyqt5.qtopengl:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5charts5:amd64 (5.15.7-2, 5.15.8-2), libqt5qml5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), pyqt5-dev-tools:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5x11extras5:amd64 (5.15.7-2, 5.15.8-2), libmediastreamer12:amd64 (1:5.1.64+dfsg-3+b2, 1:5.1.64+dfsg-3+b3), qml-module-qtquick-controls2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5quickshapes5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qt-labs-platform:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5network5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-localstorage:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5dbus5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5multimedia5-plugins:amd64 (5.15.7-2, 5.15.8-2), python3-pyqt5:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5quick5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5test5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qtwayland5:amd64 (5.15.7-2, 5.15.8-2), libqt5waylandcompositor5:amd64 (5.15.7-2, 5.15.8-2), libqt5widgets5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), python3-scipy:amd64 (1.8.1-20, 1.8.1-21), qml-module-qtcharts:amd64 (5.15.7-2, 5.15.8-2), libqt5gui5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5multimediagsttools5:amd64 (5.15.7-2, 5.15.8-2), python3-jsonschema:amd64 (4.9.1-3, 4.10.3-1), libqt5multimedia5:amd64 (5.15.7-2, 5.15.8-2), libqt5printsupport5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), ifupdown:amd64 (0.8.39+b1, 0.8.40), libqt5xml5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5opengl5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), linphone-desktop:amd64 (4.4.10-2+b1, 4.4.10-2+b2), libqt5texttospeech5:amd64 (5.15.7-2, 5.15.8-2), xfonts-encodings:amd64 (1:1.0.4-2.1, 1:1.0.4-2.2), libqt5sql5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtgraphicaleffects:amd64 (5.15.7-2, 5.15.8-2), qml-module-qt-labs-folderlistmodel:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5svg5:amd64 (5.15.7-2, 5.15.8-2), libqt5multimediawidgets5:amd64 (5.15.7-2, 5.15.8-2), libqt5quicktemplates2-5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtqml-models2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-privatewidgets:amd64 (5.15.7-2, 5.15.8-2), qtspeech5-speechd-plugin:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtquick-controls:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtquick-templates2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5sql5-sqlite:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5qmlmodels5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), xfonts-scalable:amd64 (1:1.0.3-1.2, 1:1.0.3-1.3), xfce4-screenshooter:amd64 (1.10.2-1, 1.10.3-1), libqt5designer5:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtquick2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-dialogs:amd64 (5.15.7-2, 5.15.8-2), libqt5qmlworkerscript5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), python3-dbus.mainloop.pyqt5:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5waylandclient5:amd64 (5.15.7-2, 5.15.8-2), libqt5help5:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtqml:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qt5-gtk2-platformtheme:amd64 (5.0.0+git23.g335dbec-4+b6, 5.0.0+git23.g335dbec-4+b7) and subsequent reboot I did not get any network connection. systemctl restart networking brought my ethernet interface up again and all was fine. Applying Cyril's trick to substitute "allow-hotplug" by "auto" in /etc/network/interfaces resolved it for the moment.
Bug#1018811: Three new test issues preventing upload of patch (Was: pyfai: autopkgtest regression on armel and i386)
Hi Andreas,
Thanks for taking care of the packaging of pyFAI. I had a look at what
the logs and apparently you are packaging the version 0.21.3 ... while
I released the verison 2023.1 last week:
https://pypi.org/project/pyfai/
I just checked on the i386-debian sid chroot I have and none of the 3 test you
found were failing (they are skipped)... but there is another one failing:
==
FAIL: test (pyFAI.test.test_error_model.TestErrorModel.test)
--
Traceback (most recent call last):
File
"/tmp/pyFAI/build/lib/python3/dist-packages/pyFAI/test/test_error_model.py",
line 121, in test
self.assertGreaterEqual(cormap(ref.__getattribute__(array),
res.__getattribute__(array)), epsilon, f"array {array} matches for {k} vs
numpy")
AssertionError: 0 not greater than or equal to 0.002 : array
sum_normalization matches for ('poisson', 'opencl', 'integrate') vs numpy
I double checked and this failure is relative to the PoCL
implemantation used on my i386-chroot. If OpenCL is disabled for the
tests in debian, this test should pass OK.
Cheers,
Jerome
On Fri, 20 Jan 2023 22:20:57 +0100
Andreas Tille wrote:
> Hi Jerome,
>
> I've applied the suggested patch to relax the tests on 32 bit architectures.
> Unfortunately there are new test suite errors as you can see in Salsa CI[1]:
>
>
> ==
> FAIL: test_count_csr
> (pyFAI.test.test_histogram.TestHistogram2d.test_count_csr)
> Test that the pixel count and the total intensity is conserved
> --
> Traceback (most recent call last):
> File
> "/builds/science-team/pyfai/debian/output/source_dir/.pybuild/cpython3_3.11_pyfai/build/pyFAI/test/test_histogram.py",
> line 339, in test_count_csr
> self.assertTrue(delta == 0, msg="check all pixels were counted")
> AssertionError: False is not true : check all pixels were counted
> ==
> FAIL: test_numpy_vs_cython_vs_csr_2d
> (pyFAI.test.test_histogram.TestHistogram2d.test_numpy_vs_cython_vs_csr_2d)
> Compare numpy histogram with cython simple implementation
> --
> Traceback (most recent call last):
> File
> "/builds/science-team/pyfai/debian/output/source_dir/.pybuild/cpython3_3.11_pyfai/build/pyFAI/test/test_histogram.py",
> line 373, in test_numpy_vs_cython_vs_csr_2d
> self.assertTrue(delta_max <= self.err_max_cnt, "pixel count difference
> numpy/csr : max delta=%s" % delta_max)
> AssertionError: False is not true : pixel count difference numpy/csr : max
> delta=8.0
> ==
> FAIL: test_2d_nosplit (pyFAI.test.test_csr.TestCSR.test_2d_nosplit)
> --
> Traceback (most recent call last):
> File
> "/builds/science-team/pyfai/debian/output/source_dir/.pybuild/cpython3_3.11_pyfai/build/pyFAI/test/test_csr.py",
> line 195, in test_2d_nosplit
> self.assertLess(error.mean(), 1e-3, "img are almost the same")
> AssertionError: 244.15215998872887 not less than 0.001 : img are almost the
> same
> ==
>
> Any idea how to fix these?
>
> Kind regards
>Andreas.
>
>
> [1] https://salsa.debian.org/science-team/pyfai/-/jobs/3826387
>
> --
> http://fam-tille.de
Bug#1023472: Fix for double Window Manager in LXQt
tags 1023472 -patch
thanks
Hi,
Roland Clobus wrote (Sun, 22 Jan 2023 09:57:36 +0100):
> ... now sending to the bug, to show the full text ...
>
> The proposed patch is at Salsa:
> https://salsa.debian.org/installer-team/tasksel/-/merge_requests/23
>
> By mentioning the sddm theme before sddm, it will prevent the default
> theme of sddm to be installed.
> Also in the MR: for some reason the theme was mentioned twice, it was
> probably intended to allow for other sddm themes.
Your proposal
Depends: ${misc:Depends},
task-desktop,
+ # Mention the preferred theme before sddm, otherwise another theme will be
used
+ sddm-theme-debian-elarun | sddm-theme,
sddm,
- sddm-theme-debian-elarun | sddm-theme-debian-elarun,
lxqt,
will not work.
sddm-theme-debian-elarun itself recommends sddm, so installing
sddm-theme-debian-elarun will pull in sddm anyway, no matter what you do else.
And sddm pulls in most of the KDE environment, including kwin.
So I guess we will need to remove both, sddm-theme-debian-elarun and sddm,
from the list here, if we don't want kwin (and all the other KDE stuff).
Leaves us (or lxqt people, in CC) with the question, if some other theme package
is needed as a replacement from the above...
Holger
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#1029414: autopkgtest: please install a doc-base file
Package: autopkgtest Version: 5.27 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, could you please consider installing a doc-base file linking to the installed HTML documentation files like /usr/share/doc/autopkgtest/README.package-tests.html? This would make it possible to easily browse it with tools like dochelp. Thank you for your incredible work on autopkgtest! - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 autopkgtest depends on: ii apt-utils 2.5.4 ii libdpkg-perl1.21.18 ii procps 2:4.0.2-3 ii python3 3.10.6-3+b1 ii python3-debian 0.1.49 Versions of packages autopkgtest recommends: ii autodep8 0.28 ii fakeroot 1.29-1 Versions of packages autopkgtest suggests: pn docker.io pn fakemachine pn lxc pn lxd ii ovmf 2022.11-2 pn ovmf-ia32 pn podman ii python3-distro-info 1.3 pn qemu-efi-aarch64 pn qemu-efi-arm pn qemu-system ii qemu-utils 1:7.2+dfsg-1+b2 ii schroot 1.6.13-3+b1 ii util-linux 2.38.1-4 pn vmdb2 pn zerofree - -- no debconf information -BEGIN PGP SIGNATURE- iIoEARYIADIWIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCY81bGRQcYW5kcmVhQHBh cHBhY29kYS5pdAAKCRBKkgiiRVB3p8tuAP9nGSrmNG0PegY0GKCRv5g/sRBguVNj qT4CUcXMtDksBgD+NLMwKJETnwhS4HbtcBWNW4nenJtvHCZSPd7NBy0N7As= =zjIA -END PGP SIGNATURE-
Bug#1018811: Three new test issues preventing upload of patch (Was: pyfai: autopkgtest regression on armel and i386)
Am Sun, Jan 22, 2023 at 04:24:51PM +0100 schrieb Jerome Kieffer:
> I released the verison 2023.1 last week:
> https://pypi.org/project/pyfai/
>
> I just checked on the i386-debian sid chroot I have and none of the 3 test
> you found were failing (they are skipped)... but there is another one failing:
>
> ==
> FAIL: test (pyFAI.test.test_error_model.TestErrorModel.test)
> --
> Traceback (most recent call last):
> File
> "/tmp/pyFAI/build/lib/python3/dist-packages/pyFAI/test/test_error_model.py",
> line 121, in test
> self.assertGreaterEqual(cormap(ref.__getattribute__(array),
> res.__getattribute__(array)), epsilon, f"array {array} matches for {k} vs
> numpy")
> AssertionError: 0 not greater than or equal to 0.002 : array
> sum_normalization matches for ('poisson', 'opencl', 'integrate') vs numpy
>
> I double checked and this failure is relative to the PoCL
> implemantation used on my i386-chroot. If OpenCL is disabled for the
> tests in debian, this test should pass OK.
Thanks for commenting on this. Would you be able to push the needed changes
to Salsa (and preferably upload)?
Kind regards
Andreas.
--
http://fam-tille.de
Bug#1029417: gammu: FTBFS in bookworm (undeclared build-dependency on tzdata)
Package: src:gammu Version: 1.42.0-5 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-arch dh binary-arch --with sphinxdoc --buildsystem=cmake dh_update_autotools_config -a -O--buildsystem=cmake dh_autoreconf -a -O--buildsystem=cmake debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- \ -DINSTALL_LIBDATA_DIR=/usr/lib/x86_64-linux-gnu \ -DSYSTEMD_SERVICES_INSTALL_DIR=/usr/lib/systemd/system \ -DINSTALL_LSB_INIT=ON \ -DSYSTEMD_FOUND=ON \ -DWITH_SYSTEMD=ON cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DINSTALL_LIBDATA_DIR=/usr/lib/x86_64-linux-gnu -DSYSTEMD_SERVICES_INSTALL_DIR=/usr/lib/systemd/system -DINSTALL_LSB_INIT=ON -DSYSTEMD_FOUND=ON -DWITH_SYSTEMD=ON .. [...] test 468 Start 468: test_sql_time 468: Test command: /<>/obj-x86_64-linux-gnu/tests/atgen/test_sql_time 468: Working Directory: /<>/obj-x86_64-linux-gnu/tests/atgen 468: Test timeout computed to be: 1500 468: Test "tm.tm_hour == 13" failed! 468: test_fill_time_t_gmt 468: test_fill_time_t_dst 468/880 Test #468: test_sql_time ...***Failed 0.01 sec Test "tm.tm_hour == 13" failed! test_fill_time_t_gmt test_fill_time_t_dst [...] The following tests FAILED: 468 - test_sql_time (Failed) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2 make[1]: *** [debian/rules:21: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#1029419: golang-github-mattn-go-sqlite3: FTBFS in bookworm (undeclared build-dependency on tzdata)
Package: src:golang-github-mattn-go-sqlite3 Version: 1.14.15~ds1-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-arch dh binary-arch --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -a -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -a -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -a -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -a -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/mattn/go-sqlite3 github.com/mattn/go-sqlite3/upgrade internal/goarch internal/unsafeheader internal/abi internal/cpu internal/goexperiment internal/goos runtime/internal/atomic internal/bytealg runtime/internal/math runtime/internal/sys runtime/internal/syscall internal/race runtime sync/atomic internal/itoa math/bits math unicode/utf8 crypto/internal/subtle crypto/subtle unicode crypto/internal/boring/sig github.com/mattn/go-sqlite3/upgrade sync internal/reflectlite internal/testlog runtime/cgo errors internal/oserror syscall time io hash context strconv sort internal/syscall/unix internal/poll crypto reflect internal/syscall/execenv path io/fs os strings encoding/binary internal/fmtsort fmt crypto/cipher crypto/internal/boring crypto/sha1 crypto/sha256 crypto/sha512 database/sql/driver net/url database/sql github.com/mattn/go-sqlite3 dh_auto_test -a -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/mattn/go-sqlite3 github.com/mattn/go-sqlite3/upgrade === RUN TestBackupStepByStep --- PASS: TestBackupStepByStep (0.21s) === RUN TestBackupAllRemainingPages --- PASS: TestBackupAllRemainingPages (0.20s) === RUN TestBackupError --- PASS: TestBackupError (0.00s) === RUN TestCallbackArgCast --- PASS: TestCallbackArgCast (0.00s) === RUN TestCallbackConverters --- PASS: TestCallbackConverters (0.00s) === RUN TestCallbackReturnAny --- PASS: TestCallbackReturnAny (0.00s) === RUN TestSimpleError --- PASS: TestSimpleError (0.00s) === RUN TestCorruptDbErrors --- PASS: TestCorruptDbErrors (0.00s) === RUN TestSqlLogicErrors --- PASS: TestSqlLogicErrors (0.00s) === RUN TestExtendedErrorCodes_ForeignKey --- PASS: TestExtendedErrorCodes_ForeignKey (0.01s) === RUN TestExtendedErrorCodes_NotNull --- PASS: TestExtendedErrorCodes_NotNull (0.01s) === RUN TestExtendedErrorCodes_Unique --- PASS: TestExtendedErrorCodes_Unique (0.00s) === RUN TestError_SystemErrno --- PASS: TestError_SystemErrno (0.00s) === RUN TestCryptEncoders --- PASS: TestCryptEncoders (0.00s) === RUN TestBeginTxCancel --- PASS: TestBeginTxCancel (0.20s) === RUN TestStmtReadonly --- PASS: TestStmtReadonly (0.00s) === RUN TestNamedParams --- PASS: TestNamedParams (0.00s) === RUN TestShortTimeout --- PASS: TestShortTimeout (0.23s) === RUN TestExecContextCancel --- PASS: TestExecContextCancel (2.26s) === RUN TestQueryRowContextCancel --- PASS: TestQueryRowContextCancel (1.03s) === RUN TestQueryRowContextCancelParallel --- PASS: TestQueryRowContextCancelParallel (4.60s) === RUN TestExecCancel --- PASS: TestExecCancel (0.00s) === RUN TestOpenContext --- PASS: TestOpenContext (0.01s) === RUN TestFileCopyTruncate --- PASS: TestFileCopyTruncate (0.01s) === RUN TestExtensionsError --- PASS: TestExtensionsError (0.00s) === RUN TestLoadExtensionError --- PASS: TestLoadExtensionError (0.00s) === RUN TestFTS3 --- PASS: TestFTS3 (0.01s) === RUN TestFTS4 --- PASS: TestFTS4 (0.01s) === RUN TestOpen --- PASS: TestOpen (0.01s) === RUN TestOpenWithVFS --- PASS: TestOpenWithVFS (0.00s) === RUN TestOpenNoCreate --- PASS: TestOpenNoCreate (0.00s) === RUN TestReadonly --- PASS: TestReadonly (0.00s) === RUN TestForeignKeys --- PASS: TestForeignKeys (0.00s) === RUN TestRecursiveTriggers --- PASS: TestRecursiveTriggers (0.00s) === RUN TestClose --- PASS: TestClose (0.00s) === RUN TestInsert --- PASS: TestInsert (0.01s) === RUN TestUpsert --- PASS: TestUpsert (0.04s) === RUN TestUpdate --- PASS: TestUpdate (0.01s) === RUN TestDelete --- PASS: TestDelete (0.01s) === RUN TestBooleanRoundtrip --- PASS: TestBooleanRoundtrip (0.01s) === RUN TestTimestamp --- PASS: TestTimestamp (0.07s) === RUN TestBoolean --- PASS: TestBoolean (0.01s) === RUN TestFloat32 --- PASS: TestFloat32 (0.00s) === RUN TestNull --- PASS: TestNull (0.00s) === RUN TestTransaction --- PASS: TestTransaction (0.01s) === RUN TestWAL --- PASS: TestWAL (0.01s) === RUN TestTimezoneConversion sqlite3_test.go:952: Failed to create table: Invalid _loc: US/Central: unknown time zone US/Central --- FAIL: TestTimezoneConversion (0.04s) === RUN TestExecer --- PASS: TestExecer (0.01s) === RUN TestQueryer --- PASS: TestQueryer (0.00s) === RUN
Bug#1029421: Websocketd strips adds extraneous newlines in other direction from client to server, and strips out newlines in the other direction
Package: websocketd Version: 0.4.1-1+b5 In order to do some tests with web services, and eventually set up a tunnel for ssh, I used websocketd with a simple script. Here I noticed that the script's input and output are not faithfully received from/sent to the socket. Indeed, from client to server, extraneous newlines are added. Conversely, on data from server to client, newlines are stripped out. N.B., I *did* set both STDERR and STDOUT to autoflush. Hence, this cannot be used to tunnel arbitrary data via a web server. Thanks, Alain
Bug#1029431: ITP: pyequihash -- python bindings for libequihash: memory-hard Proof-of-Work with fast verification
Package: wnpp Severity: wishlist Owner: Joost van Baal-Ilić * Package name: pyequihash Version : 0.2 Upstream Author : Stefan Marsiske * URL : https://github.com/stef/equihash/python * License : GPLv3 Programming Lang: Python Description : python bindings for libequihash: memory-hard Proof-of-Work with fast verification Binary package name: python3-equihash Equihash implements the algorith as described in "Equihash: Asymmetric Proof-of-Work Based on the Generalized Birthday Problem" by Alex Biryukov and Dmitry Khovratovich, 2016, DOI:10.14722/ndss.2016.23108. This code, by Stefan Marsiske, is a fork of an ealier implementation by Khovratovich at https://github.com/khovratovich/equihash/ ; it provides a library, a C API and Python bindings. The cryptographic password storage SPHINX (pwdsphinx and libsphinx) depend upon equihash. . This package offers a Python wrapper for the C library and comes with functions equihash.solve(n, k, seed) and equihash.verify (n,k,seed,sol). See https://www.ctrlc.hu/~stef/blog/posts/sphinx.html and https://nlnet.nl/project/OpaqueSphinxServer/ for more background information. See e.g. https://core.ac.uk/download/pdf/31227294.pdf for a copy of the original article. The SPHINX project was funded through the NGI0 PET Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 825310. I intend to carry out this work within the Debian Python Team, at the yet to be created https://salsa.debian.org/python-team/packages/pyequihash . The libequihash package which is now in unstable ( see https://tracker.debian.org/pkg/libequihash ) currently holds the same python code. I'll upload a new version of this original libequihash package without the python wrapper code; it will no longer build python3-equihash. Packaging pyequihash from this pypi upstream sources is done in order to simplify the Debian packaging work (and by doing so fix some RC bugs). Bye, Joost
Bug#1028111: r-cran-clock: autopkgtest failure on 32bit
Control: severity -1 important The two failing tests were excluded for the three affected architectures. While the problem is not really fixed (and thus the bug remains open) the severity is lowered to "important" to enable testing migration. Kind regards Andreas. -- http://fam-tille.de
Bug#1029388: linux-image-6.1.0-2-amd64: system does not boot up when swap partion is a file
Control: severity -1 important Control: tags -1 + moreinfo On Sun, Jan 22, 2023 at 11:12:37AM +0100, magnus wrote: > Package: src:linux > Version: 6.1.7-1 > Severity: critical > Justification: breaks the whole system > X-Debbugs-Cc: magnus.ekd...@gmail.com > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > > apt dist-upgrade from an older version of debian unstable > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I got some errors (unfortunatly not saved) from upgrade process. I.e. the > script failed ***swap problem***, I assumed that meant the installation did > not > finish and the old kernel would boot up. > >* What was the outcome of this action? > > After bootup I got kenel panic. A working workaround was to: > > 1. boot into live debian (from the debian installer via usb) > 2. chroot into standard / > 3. comment out swapfile from /etc/fstab (from chroot) > 4. run apt upgrade again (this time it completed) > 5. reboot into standard / > >* What outcome did you expect instead? > > I expect that the kernel-package: > > 1: can handle if fstab conain an entry like: /swapfile swap swap defaults 0 0 > 2: if the kenel installation script breaks, I expect the old kenerl to boot > up. > If this is currently not technically possible I would expect a clear warning > that the system will be in a broken state if I reboot now. Can you please try to get the respecive installation errors still from the log files, you might get sucessful from /var/log/apt/term.log . There was a similar issue reported earlier this week, but was not found to be reproducible. So if you can get to this information that would be helpful. Regards, Salvatore
