Bug#1016002: polymake: VISUAL fails when browser is already started
Package: polymake Version: 4.3-4 Severity: normal Dear Maintainer. If I run polymake 'simplex(3)->VISUAL;' and the browser is already running and uses the existing instance to display the graph, a file not found error is displayed instead of the graph. This is the case on chromium and epiphany. Firefox is not affected since it starts a new browser instance. An easy fix for debian might be to not delete the temporary files that are displayed. -- System Information: Debian Release: 11.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages polymake depends on: ii libbliss2 0.73-5 ii libc6 2.33-7 ii libcdd0d094l-2 ii libeantic0 0.1.8+ds-1 ii libflint-2.6.3 2.6.3-3 ii libgcc-s1 11.2.0-2 ii libgmp102:6.2.1+dfsg1-1 ii libgomp111.2.0-2 ii libmpfr64.1.0-3 ii libnormaliz33.8.9+ds-0.1 ii libpolymake-dev-common 4.3-4 ii libppl141:1.2-8.1 ii libstdc++6 11.2.0-2 ii ninja-build 1.10.1-1 ii polymake-common 4.3-4 Versions of packages polymake recommends: ii chromium 103.0.5060.134-1~deb11u1 ii gfan 0.6.2-4 ii graphviz 2.42.2-5 ii xdg-utils 1.1.3-4.1 Versions of packages polymake suggests: pn povray ii texlive-latex-extra 2020.20210202-3 ii texlive-pictures 2020.20210202-3
Bug#1016001: rust-capstone: please add support for riscv64
Source: rust-capstone
Version: 0.7.0-3
Severity: wishlist
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear rust-capstone Maintainer,
The rust-capstone package can be built on riscv64 arch with
the patch attached, so could you please add riscv64 arch as
a build target? thanks.
--
Regards,
--
Bo YU
diff -Nru rust-capstone-0.7.0/debian/control rust-capstone-0.7.0/debian/control
--- rust-capstone-0.7.0/debian/control 2021-10-15 02:33:33.0 +0800
+++ rust-capstone-0.7.0/debian/control 2021-10-15 02:33:33.0 +0800
@@ -17,7 +17,7 @@
Rules-Requires-Root: no
Package: librust-capstone-dev
-Architecture: amd64 arm64
+Architecture: amd64 arm64 riscv64
Multi-Arch: same
Depends:
${misc:Depends},
signature.asc
Description: PGP signature
Bug#984921: rust-libsqlite3-sys: depends on multiple unavailable packages
Version: 0.25.0-1 On Wed 2021-03-10 10:43:38 +0100, Andreas Beckmann wrote: > the binary packages built from src:rust-libsqlite3-sys depend on several no > longer available packages, e.g. > > The following packages have unmet dependencies: >librust-libsqlite3-sys+bindgen-dev : Depends: > librust-bindgen-0.50+default-dev but it is not installable This has been resolved with rust-libsqlite3-sys 0.25.0-1, as it now Depends: librust-bindgen-0.60+runtime-dev, which is in both testing and unstable. --dkg signature.asc Description: PGP signature
Bug#1015999: emacs: tags-query-replace doesn't start from beginning of already-loaded files
Package: emacs Version: 1:27.1+1-3.1 Severity: normal Dear Maintainer, Doing a tags-query-replace that operates on files that are already opened in buffers doesn't start searching at the beginning of the file/buffer (as it has done for years). (It seems to start at each buffer's point instead.) (This makes is really difficult to do a series of tags-query-replace commands on a set of files--one has to do something like deleting all the buffers so a subsequent tags-query-replace command processes the whole of each file.) * Create a TAGS file listing a file. * Begin a tags-query-replace that will find something in the file. (You don't need to replace anything.) * Begin a second tags-query-replace that should find something that is in the buffer _before_ the last match you went to in the previous step. Note how tags-query-replace does not find that something, bu only finds matches _after_ that previous match. -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_DIE 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 emacs depends on: ii emacs-gtk 1:27.1+1-3.1 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#1015028: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/celery/celery/commit/b260860988469ef8ad74f2d4225839c2fa91d590 Control: retitle -1 celery: FTBFS: test failures due to billiard upgrade: ImportError: cannot import name 'buf_t' from 'billiard.compat' On Sat, 16 Jul 2022 15:41:55 +0200 Lucas Nussbaum wrote: > > > from billiard.compat import buf_t, isblocking, setblocking > > E ImportError: cannot import name 'buf_t' from 'billiard.compat' > > (/usr/lib/python3/dist-packages/billiard/compat.py) This issue was caused by the update of python3-billiard to 4.0.0-1 and is fixed in celery upstream alpha version v5.3.0a1. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1006472: Upload to unstable?
Il 24/07/2022 22:12, Roland Clobus ha scritto: Hello maintainer of nemo, would you consider to upload this fix to unstable? It is currently only in experimental. I've found this issue, because it makes the Cinnamon live image non-reproducible. See https://wiki.debian.org/ReproducibleInstalls/LiveImages. With kind regards, Roland Clobus Hi, nemo and major of cinnamon 5.4 components are in experimental due many bugs still present related to big changes, upstreamsolved a lot of problems with the latest versions which i uploaded to experimental and tried a bit in the last few days but didn't have much time for in-depth testing. I think however that within a few weeks with the next bugfixes they will be good enough to be able to migrate them to unstable. Is it a problem to wait up to a few more weeks or I should upload this change to unstable faster? OpenPGP_signature Description: OpenPGP digital signature
Bug#965765: pacparser: diff for NMU version 1.3.6-1.3
Control: tags 965765 + patch Control: tags 965765 + pending Dear maintainer, I've prepared an NMU for pacparser (versioned as 1.3.6-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru pacparser-1.3.6/debian/changelog pacparser-1.3.6/debian/changelog --- pacparser-1.3.6/debian/changelog 2020-03-02 07:22:40.0 +0200 +++ pacparser-1.3.6/debian/changelog 2022-07-25 00:20:17.0 +0300 @@ -1,3 +1,10 @@ +pacparser (1.3.6-1.3) unstable; urgency=low + + * Non-maintainer upload. + * debian/compat: 5 -> 7. (Closes: #965765) + + -- Adrian Bunk Mon, 25 Jul 2022 00:20:17 +0300 + pacparser (1.3.6-1.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru pacparser-1.3.6/debian/compat pacparser-1.3.6/debian/compat --- pacparser-1.3.6/debian/compat 2015-09-04 23:06:41.0 +0300 +++ pacparser-1.3.6/debian/compat 2022-07-25 00:20:17.0 +0300 @@ -1 +1 @@ -5 +7
Bug#1015993: RM: jsonnet [mips64el mipsel s390x] -- NBS; No longer built on these architectures
Package: ftp.debian.org Severity: normal jsonnet (0.18.0+ds-2) unstable; urgency=medium ... * Allow only specific architectures as build targets -- Fukui Daichi Sat, 02 Jul 2022 13:23:19 +
Bug#1003397:
Hi Daichi,
I reviewed your package.
First, This is emedded with C4CORE.
Do you have any plans to package this?
https://github.com/biojppm/c4core
debain/control:
development package is required., because this is a library.
debian/patches:
Currently, this package does not have any patches. so this can delete.
Best regards,
Nobuhiro
2022年7月20日(水) 23:09 Daichi Fukui :
>
> Hello Iwamatsu-san,
>
> I have drafted a source package of rapidyaml and put it onto my private
> repository in salsa:
>
> https://salsa.debian.org/dfukui/rapidyaml/-/tree/debian/0.4.1-1
>
> When you have time, can you review the source package and help me upload it
> to the archive?
>
> Best regards,
> Fukui
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
Bug#1015565: opencc: ftbfs with LTO (link time optimization) enabled
The first step of a fix taken via version 1.1.4+ds1-2. Waiting for a build-attempt on ppc64el before updating the symbols file with the buildd logs.
Bug#1015994: python3-csound depends on python3.9 that will be removed
Package: python3-csound Version: 1:6.17.0~dfsg-3 Severity: serious python3-csound depends on python3.9 that will be removed. A no-change source upload would fix this, but override_dh_python3 forcing a versioned dependency looks bogus and should be dropped.
Bug#1015995: gpgme1.0 FTBFS with 3.10 as only supported Python3 version
Source: gpgme1.0 Version: 1.17.1-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gpgme1.0=1.17.1-4%2Bb1 ... Making check in tests make[5]: Entering directory '/<>/build/lang/python/tests' make all-am make[6]: Entering directory '/<>/build/lang/python/tests' make[6]: Nothing to be done for 'all-am'. make[6]: Leaving directory '/<>/build/lang/python/tests' GNUPGHOME=/<>/build/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../../.. srcdir=../../../../lang/python/tests LD_LIBRARY_PATH="../../../src/.libs:" ../../../../lang/python/tests/run-tests.py \ --interpreters="/usr/bin/python3.10 " --srcdir=../../../../lang/python/tests \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-edit.py t-keylist.py t-keylist-from-data.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py t-quick-key-creation.py t-quick-subkey-creation.py t-quick-key-manipulation.py t-quick-key-signing.py final.py /bin/bash: line 1: ../../../../lang/python/tests/run-tests.py: Permission denied make[5]: *** [Makefile:621: xcheck] Error 126
Bug#1015756: lynx: segfault when setting 'default colors' to 'OFF'
On Wed, Jul 20, 2022 at 06:37:18PM -0400, Thomas Dickey wrote: > On Wed, Jul 20, 2022 at 06:27:34PM -0400, Thomas Dickey wrote: > > On Wed, Jul 20, 2022 at 06:01:01PM -0400, Thomas Dickey wrote: > > > On Wed, Jul 20, 2022 at 05:50:48PM +0200, Cédric Hannotier wrote: > > > > Package: lynx > > > > Version: 2.9.0dev.10-1 > > > > Severity: normal > > > > > > > > Dear Maintainer, > > > > > > > > Seems that toggling off the "default colors" in the option menu > > > > crashes lynx (segfault). > > > > > > > > Steps: > > > > - $ lynx > > > > - Press o > > > > - navigate to "Default colors (!)" > > > > - switch from "ON_" (default) to "OFF" > > > > - navigate to "Accept Changes" and press enter > > > > > > > > Disabling it using the command-line option > > > > (lynx -default_colors) seems to work. > > > > However, toggling it ON, then OFF makes it segfault. > > > > > > thanks (I can reproduce this, will investigate) > > > > The issue that I can reproduce is in ncurses. > > (my traceback is longer than that given in the bug report) > > > Will reassign & resolve it there. > > The apparent problem is from this change: > > 20211106 > + fix a memory-leak in del_curterm (prompted by discussion with Bram > Moolenaar, cf: 20210821). > > Lynx uses delscreen (in libncurses*) when resetting curses, > which calls del_curterm (in libtinfo*). > > Few programs do this, so it's taken a while to notice. There was more than one problem, all older than the indicated change. That just happened to move things around to make the problems noticeable. In the diffstat: ncurses/base/lib_set_term.c |8 +-- ncurses/tinfo/lib_setup.c |4 +-- ncurses/tinfo/lib_tputs.c |9 ncurses/trace/lib_trace.c | 22 +++- ncurses/tty/tty_update.c | 16 ++- The changes in "tinfo" and "tty" are relevant. The core dump is fixed by the change in tty_update.c, while the other changes are things that would be a problem at another time. (The change to lib_set_term.c is just to be more certain, and the trace change doesn't affect Debian). However, there's still a less-visible issue in lynx source (seen with valgrind), which is fixed in v2-9-0dev_10i seen here https://github.com/ThomasDickey/lynx-snapshots/commit/76e3af60e119146f4da21a008af1ff752c61136f Since that didn't cause the core-dump which I can reproduce, it's just fyi - will be in dev.11 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1015996: coreutils: chcon -v always says "changing security context" even when it doesn't?
Package: coreutils
Version: 8.32-4+b1
Severity: minor
Dear Maintainer,
chcon doesn't setfilecon() when the current context is already the one
requested, mirroring chgrp.
Observe, however chgrp -v:
$ chgrp -v users fips180-2withchangenotice.pdf fips180-3_final.pdf
group of 'fips180-2withchangenotice.pdf' retained as users
changed group of 'fips180-3_final.pdf' from nabijaczleweli to users
as contrasted with chcon -v:
# ls -Z /mnt/*_t | cat
unconfined_u:object_r:tmp_t:s0 /mnt/tmp_t
unconfined_u:object_r:unlabeled_t:s0 /mnt/unlabeled_t
# chcon -v -t tmp_t /mnt/*_t
changing security context of '/mnt/tmp_t'
changing security context of '/mnt/unlabeled_t'
A re-run confirms this is a lie:
# strace chcon -v -t tmp_t /mnt/*_t 2>&1 | grep xattr
getxattr("/mnt/tmp_t", "security.selinux", "unconfined_u:object_r:tmp_t:s0",
255) = 31
getxattr("/mnt/unlabeled_t", "security.selinux",
"unconfined_u:object_r:unlabeled_"..., 255) = 37
setxattr("/mnt/unlabeled_t", "security.selinux",
"unconfined_u:object_r:tmp_t:s0", 31, 0) = 0
Best,
наб
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-16-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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
Versions of packages coreutils depends on:
ii libacl1 2.2.53-10
ii libattr1 1:2.4.48-6
ii libc62.31-13+deb11u3
ii libgmp10 2:6.2.1+dfsg-1+deb11u1
ii libselinux1 3.1-3
coreutils recommends no packages.
coreutils suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
Bug#1015782: live-build: Replace a few more values in the splash SVG
[Roland Clobus] > Of the 5 additional variables, only 3 are used in your SVG image > (LB_ISO_APPLICATION, LB_ISO_PUBLISHER, LB_LINUX_PACKAGES). > Do you mind if I will add only these three? Any is better than none. :) Is there a reason not to make all 5 variables available for SVG artists? > I've looked a little deeper into the repository. > Perhaps the following questions should be redirected to a mailing list > instead of drifting off-topic from this bug report: > > The file in patches/binary_syslinux is rather different from the version > in git (https://salsa.debian.org/live-team/live-build). Have you tried > using live-build from bookworm (which is currently at 1:20220505 or > better yet, the latest version from git? (By setting LIVE_BUILD, see > https://wiki.debian.org/ReproducibleInstalls/LiveImages) > > Your repository is called https://github.com/LinuxCNC/buster-live-build, > which refers to buster, which is currently oldstable. Will you be aiming > for bookworm? (You could use a single repository live-build-config, with > several branches) > > The image for Grub (used for UEFI boot) is the default image. Is that > intentional? I have similar question regarding the setup, and have no idea what the answer to them are. I recently decided to have a look at the live build to bring it up to bookworm, and discovered one needed patch that I decided to submit to you. I am working on a patch set for bookworm, but it is not yet ready. > PS: In the README.md you could add a first step: > lb config --config https://github.com/LinuxCNC/buster-live-build Ah, thanks. :) -- Happy hacking Petter Reinholdtsen
Bug#1015971: ITP: pamixer -- pulseaudio command line mixer
On Sun, 2022-07-24 at 18:26 +0200, Tzafrir Cohen wrote: > pamixer is like amixer but for pulseaudio. pulsemixer is already available in Debian, do we need pamixer? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1015997: monit: useless mail about link down after reload
Package: monit Version: 1:5.32.0-1+b1 Severity: minor I've received a mail Link down Service eth0 Date:Mon, 25 Jul 2022 00:00:01 Action: alert Host:zira Description: link down Your faithful employee, Monit I have check network eth0 with interface eth0 if changed link capacity then alert but the link has been down (no cable plugged in) for several days. So there's no change, and I shouldn't have received any mail. Monit was automatically reloaded at midnight (I don't know why, and that's probably useless). -- Package-specific info: Monit config file /etc/monit/monitrc is *NOT* readable by reportbug. Please, consider to rerun reportbug as root and *carefully* examine reportbug's output (e.g., monitrc content), before sending it out. Contents of /etc/monit/ directory: /etc/monit: total 36 drwxr-xr-x 2 root root 4096 2022-06-12 03:06:28 conf-available drwxr-xr-x 2 root root 4096 2015-12-05 21:19:30 conf-enabled drwxr-xr-x 2 root root 4096 2020-01-04 22:11:10 conf.d -rw--- 1 root root 13578 2021-08-27 03:29:15 monitrc drwxr-xr-x 2 root root 4096 2022-03-13 02:56:43 monitrc.d drwxr-xr-x 2 root root 4096 2022-06-12 03:06:28 templates /etc/monit/conf-available: total 60 -rw-r--r-- 1 root root 481 2015-12-05 21:13:49 acpid -rw-r--r-- 1 root root 640 2015-12-05 21:13:49 apache2 -rw-r--r-- 1 root root 455 2015-12-05 21:13:49 at -rw-r--r-- 1 root root 691 2015-12-05 21:13:49 cron -rw-r--r-- 1 root root 602 2015-12-05 21:13:49 mdadm -rw-r--r-- 1 root root 669 2015-12-05 21:13:49 memcached -rw-r--r-- 1 root root 703 2015-12-05 21:13:49 mysql -rw-r--r-- 1 root root 521 2015-12-05 21:13:49 nginx -rw-r--r-- 1 root root 471 2015-12-05 21:13:49 openntpd -rw-r--r-- 1 root root 1200 2020-07-31 13:12:44 openssh-server -rw-r--r-- 1 root root 683 2015-12-05 21:13:49 pdns-recursor -rw-r--r-- 1 root root 1426 2018-12-21 09:32:54 postfix -rw-r--r-- 1 root root 869 2016-03-22 16:43:44 rsyslog -rw-r--r-- 1 root root 501 2015-12-05 21:13:49 smartmontools -rw-r--r-- 1 root root 306 2016-02-04 15:03:50 snmpd /etc/monit/conf-enabled: total 0 /etc/monit/conf.d: total 4 -rw-r--r-- 1 root root 357 2020-01-04 22:11:10 eth0 /etc/monit/monitrc.d: total 64 -rw-r--r-- 1 root root 481 2015-06-09 15:52:48 acpid -rw-r--r-- 1 root root 640 2015-06-09 15:52:48 apache2 -rw-r--r-- 1 root root 455 2015-06-09 15:52:48 at -rw-r--r-- 1 root root 691 2015-06-09 15:52:48 cron -rw-r--r-- 1 root root 403 2016-12-09 15:37:54 fail2ban -rw-r--r-- 1 root root 602 2015-06-09 15:52:48 mdadm -rw-r--r-- 1 root root 669 2015-06-09 15:52:48 memcached -rw-r--r-- 1 root root 703 2015-06-09 15:52:48 mysql -rw-r--r-- 1 root root 521 2015-06-09 15:52:48 nginx -rw-r--r-- 1 root root 471 2015-06-09 15:52:48 openntpd -rw-r--r-- 1 root root 950 2015-06-09 15:52:48 openssh-server -rw-r--r-- 1 root root 683 2015-06-09 15:52:48 pdns-recursor -rw-r--r-- 1 root root 1421 2015-06-09 15:52:48 postfix -rw-r--r-- 1 root root 867 2015-06-09 15:52:48 rsyslog -rw-r--r-- 1 root root 501 2015-06-09 15:52:48 smartmontools -rw-r--r-- 1 root root 310 2015-06-09 15:52:48 snmpd /etc/monit/templates: total 12 -rw-r--r-- 1 root root 164 2015-06-09 15:52:48 rootbin -rw-r--r-- 1 root root 160 2015-06-09 15:52:48 rootrc -rw-r--r-- 1 root root 164 2015-06-09 15:52:48 rootstrict -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages monit depends on: ii init-system-helpers 1.64 ii libc62.33-7 ii libcrypt11:4.4.28-2 ii libpam0g 1.4.0-13 ii libssl3 3.0.4-2 ii lsb-base 11.2 ii zlib1g 1:1.2.11.dfsg-4 monit recommends no packages. Versions of packages monit suggests: ii postfix [mail-transport-agent] 3.6.4-1+b3 pn sysvinit-core -- Configuration Files: /etc/monit/monitrc [Errno 13] Permission
Bug#1015998: boost1.74: shlibs don't generate *-py310 dependencies with Python 3.10
Source: boost1.74
Version: 1.74.0-16.1
Severity: serious
override_dh_makeshlibs:
dh_makeshlibs -plibboost-regex$(SOVERSION) -V '$(regexicuabi)'
dh_makeshlibs --remaining-packages
sed -i -r 's/^(libboost_python([0-9]{2}) \S+ (\S+).*)$$/\1, \3-py\2/'
debian/libboost-python$(SOVERSION)/DEBIAN/shlibs
sed -i -r 's/^(libboost_mpi_python([0-9]{2}) \S+ (\S+).*)$$/\1,
\3-py\2/' debian/libboost-mpi-python$(SOVERSION)/DEBIAN/shlibs
ifeq ($(BUILD_NUMPY), yes)
sed -i -r 's/^(libboost_numpy([0-9]{2}) \S+ (\S+).*)$$/\1, \3-py\2/'
debian/libboost-numpy$(SOVERSION)/DEBIAN/shlibs
endif
These {2} should be {3} to work with Python 3.10.
Bug#1015565: opencc: ftbfs with LTO (link time optimization) enabled
On 2022-07-24 23:56, Gunnar Hjalmarsson wrote: The first step of a fix taken via version 1.1.4+ds1-2. Waiting for a build-attempt on ppc64el before updating the symbols file with the buildd logs. Second thoughts: It builds fine on ppc64el in an Ubuntu PPA, without any complaints from dpkg-gensymbols, so I'm going to assume it will be fine on Debian too and upload 1.1.4+ds1-3 without access to any ppc64el log from the previous upload.
Bug#1015925: libcwidget-dev: causes aptitude FTBFS due to missing #include
Package: libcwidget-dev Version: 0.5.18-5 Severity: serious File: /usr/include/cwidget/generic/threads/threads.h The threads.h file in libcwidget-dev uses various pthread_* functions but does not #include , which means that aptitude and any other application using that header but not #include will FTBFS because the pthread_* functions are not able to be found. This bug appears to have been exposed by the change from GCC 11 to 12 in Debian unstable, since aptitude does not FTBFS in Debian bookworm. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcwidget-dev depends on: ii libcwidget40.5.18-5 ii libncurses-dev [libncursesw5-dev] 6.3+20220423-2 pn libsigc++-2.0-dev ii pkg-config 0.29.2-1 libcwidget-dev recommends no packages. Versions of packages libcwidget-dev suggests: pn libcwidget-doc -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1015926: ITP: persalys -- GUI for uncertainty treatment and variabilities management
Package: wnpp Severity: wishlist Owner: Pierre Gruet User: debian-scie...@lists.debian.org Usertags: field..science X-Debbugs-Cc: debian-de...@lists.debian.org, debian-scie...@lists.debian.org * Package name: persalys Version : 12.0.1 Upstream Author : Airbus-EDF-Phimeca * URL : https://persalys.fr/ * License : LGPL-3+ Programming Lang: C++ Description : GUI for uncertainty treatment and variabilities management Persalys is a graphical user interface for OpenTURNS, dedicated to the treatment of uncertainty and the management of variabilities. The software is a tool between the computer simulation, probabilistic analyses and the data sciences. The interface is available in French or in English. Persalys allows one to: - create mathematical models: analytical, coupling with an external model (finite elements, ...), FMU; - analyse the variability of one's parameters thanks to many methods and visualisation tools; - statistically analyse one's measuring data, infer probability distributions or create metamodels. I am an user of Persalys. I plan to maintain in in the Debian-science team.
Bug#1014796: Intel Unknown processors, Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz
tags 1014796 + pending thanks Hello Xiao, thanks, added. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1015927: pypi2deb: template d/control includes unnecessary Testsuite line
Package: pypi2deb Version: 3.20220721 Severity: normal As far as I know, the control file line: Testsuite: autopkgtest-pkg-python is no longer necessary, so could be removed from the template control file. But if I'm wrong, then sorry for the noise and please close this. (It may be that it will be needed for the future automated autopkgtest for Python packages.) Best wishes, Julian
Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version
[CC += libc-alpha] Hi glibc developers, On 7/24/22 14:24, Aurelien Jarno wrote: Hi, On 2022-07-24 12:39, Alejandro Colomar (man-pages) wrote: Hi Aurelien, On 7/23/22 11:43, Aurelien Jarno wrote: Hi, On 2022-07-19 21:55, Alejandro Colomar wrote: Package: libc6-dev Version: 2.33-8 Severity: normal X-Debbugs-Cc: alx.manpa...@gmail.com Hi, We had a discussion in NGINX Unit about if we should use __NR_xxx or SYS_xxx syscall numbers. As maintainer of the Linux man-pages, I suggested that we should use the libc macros (SYS_xxx), since they are compatible with other non-Linux systems, and also because they are the documented way for user space. However, there was some concern that someone might be running a new kernel with an old glibc, and that __NR_xxx symbols might be available but not SYS_xxx in that case. Yes that sounds good. Since the (included through ) header is generated automatically from the kernel headers at glibc build time, Debian should make sure that the latest available kernel headers are used, so building the latest Sid glibc package should be done on a system with also the latest kernel available in Sid, to have a complete SYS_xxx list. This is basically what is done, the buildd chroots are updated twice a week, so in the worst case glibc is build against a kernel headers package that is 4 days old. Is it? I have kernel 5.18, but my bits/syscalls.h still says it was generated from kernel 5.10 (that's a long time ago). I have the latest Sid packages for both the kernel and glibc. Yes, this is definitely the case, glibc 2.33-8 has been built against linux-libc-dev 5.18.5-1. What is wrong is "header is generated automatically from the kernel headers at glibc build time". They are generated by upstream at release time, not at build time. Is there an easy way to regenerate that header to get the tatest syscalls? Maybe a command could be supplied so that users (or at least distributors) have it easy to regenerate them? Maybe it already exists but it's not widely known? Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
Bug#1015957: ITP: junit5-system-exit
Package: wnpp Severity: wishlist Owner: Jérôme Charaoui Package name : junit5-system-exit Version : 1.1.2 Upstream author : Todd Ginsberg URL : https://github.com/tginsberg/junit5-system-exit License : Expat Programming Lang : Java Description : JUnit5 Extension to help write tests that call System.exit() This JUnit 5 Extension helps you write tests for code that calls System.exit(). Starting with JUnit 5, @Rules, @ClassRules, and Runners were replaced by the Extension concept. This package is a dependency for PGPainless (ITP #1005300). Thanks, -- Jerome
Bug#887035: cron: Patch by Greek adapted for cron 3.0pl1-137
Hi Georges, first off: this patch is completely irrelevant IMHO. We should not be discussing it. What's relevant is [1]. On Sun, 24 Jul 2022, Georges Khaznadar wrote: two remarks: 1) most of Greek's patches which you adapted is about making cron installable without the package syslog. That is what it claims but not what it does AFAICS. What it does is adapt the `log_it` function so that it takes a `priority` parameter. But again. This patch is irrelevant. [1] is relevant IMO. Were are the parts about "log-to-stdout-when-in-foreground"? It's at [2]. But it's irrelevant. [1] is relevant. I see that one patch modifies debian/patches/series, mentioning the file log-to-stdout-when-in-foreground, but that file is provided nowhere by the set of patches. Again see [2]. But it's irrelevant. [1] is relevant. By the way, do you know who is "Greek"? No She or he did not reply to questions which I submitted about Bug#887014 ... It's been 4 years since this bug has been filed so "Greek" might have moved on since. Is "Greek" a pseudonyme of yours? No 2) I shall not patch cron 3.0pl1-137. You can do it if you want, for your own usage, of course. If I modify debian's cron package, I must do it in the testing distribution, so please propose patches targetting at least cron 3.0pl1-147. Then, if the modification you are wishing is accepted in debian/testing, I can create a backport to use in debian/bullseye later, for example a release such as cron 3.0pl1-149~bpo11+1, to be published in bullseye-backports. Ack. However I do not want that patch to be included because as I said as far as I can see it does *not* activate output to STDOUT, contrary to what the origianl message by "Greek" claims. That patch is irrelevant, I have only posted it in case somebody is interested in using it. But I am *not* interested in it. I am interested in [1] only. Thanks! *t [1] - enable debugging logs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887035#15/ [2] - debian/patches: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=887035;filename=log-to-stdout-when-in-foreground;msg=25 Best regards, Georges. Tomas Pospisek a écrit : Package: cron Version: 3.0pl1-137 Followup-For: Bug #887035 X-Debbugs-Cc: Georges Khaznadar If anybody wants to use Greek's patch (see [1] and [2]) then I'm attaching my version of it adapted to cron 3.0pl1-137 (the version in Debian bullseye). It comes in two parts: one is the patch and one is cron-3.0pl1/debian/patches/log-to-stdout-when-in-foreground to satisfy the Debian build infrastructure. Use the patch like this to build a new, patched cron package: apt-get source cron sudo apt-get build-dep cron patch -p0 < cron-syslog-fix-and-foreground-stdout.for-new-cron.debianized.patch cp log-to-stdout-when-in-foreground cron-3.0pl1/debian/patches cd cron-3.0pl1 && dpkg-buildpackage -rfakeroot *t [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887035#5 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=887035;filename=cron-syslog-fix-and-foreground-stdout.patch;msg=5 -- Package-specific info: --- EDITOR: --- /usr/bin/editor: /usr/bin/vim.gtk3 --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 43568 Feb 22 2021 /usr/bin/crontab --- /var/spool/cron: drwxr-xr-x 3 root root 4096 Apr 10 2021 /var/spool/cron --- /var/spool/cron/crontabs: drwx-wx--T 2 root crontab 4096 Feb 22 2021 /var/spool/cron/crontabs --- /etc/cron.d: drwxr-xr-x 2 root root 4096 Jul 22 15:03 /etc/cron.d --- /etc/cron.daily: drwxr-xr-x 2 root root 4096 Jul 11 09:33 /etc/cron.daily --- /etc/cron.hourly: drwxr-xr-x 2 root root 4096 Apr 10 2021 /etc/cron.hourly --- /etc/cron.monthly: drwxr-xr-x 2 root root 4096 Apr 10 2021 /etc/cron.monthly --- /etc/cron.weekly: drwxr-xr-x 2 root root 4096 Apr 10 2021 /etc/cron.weekly -- System Information: Debian Release: 11.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/8 CPU threads) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cron depends on: ii adduser 3.118 ii debianutils 4.11.2 ii init-system-helpers 1.60 ii libc62.31-13+deb11u3 ii libpam-runtime 1.4.0-9+deb11u1 ii libpam0g 1.4.0-9+deb11u1 ii libselinux1 3.1-3 ii lsb-base 11.1.0 ii sensible-utils 0.0.14 Versions of packages cron recommends: ii msmtp-mta [mail-transport-agent] 1.8.11-2.1 Versions of packages cron suggests: ii anacron2.3-30 pn checksecurity ii logrotate 3.18.0-2+deb11u1 Versions of packages cron is related to: pn libnss-ldap pn libnss-ldapd pn libpam-ldap pn libpam-mount
Bug#1015958: haskell-http-client FTBFS on IPV6-only buildds
Source: haskell-http-client
Version: 0.7.11-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=haskell-http-client=i386=0.7.11-1=1658667307=0
...
Failures:
test-nonet/Network/HTTP/ClientSpec.hs:241:18:
1) Network.HTTP.Client.Client withResponseHistory and redirect
uncaught exception: IOException of type InvalidArgument
threadWait: invalid argument (Bad file descriptor)
To rerun use: --match "/Network.HTTP.Client/Client/withResponseHistory and
redirect/"
Randomized with seed 1906044238
Finished in 2.0400 seconds
82 examples, 1 failure
Test suite spec-nonet: FAIL
Test suite logged to: dist-ghc/test/http-client-0.7.11-spec-nonet.log
1 of 2 test suites (1 of 2 test cases) passed.
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"test", "--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"test", "--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 678
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:165: check-ghc-stamp] Error 25
Bug#1015911: git patch
>From 14804dd48e2bbcd662a7127ef55ba803f685c6e2 Mon Sep 17 00:00:00 2001
From: Peter Sagi
Date: Sun, 24 Jul 2022 09:57:24 +
Subject: [PATCH] Fix the misaligned printed image for smaller paper-sizes on
LaserJet 1100. Closes: #1015911.
---
Normalize.cpp | 3 ++-
Normalize.h | 2 +-
base/models.py | 3 ++-
data/models/models.dat | 6 +++---
prnt/drv/hpcups.drv.in.template | 16 +++-
prnt/hpcups/Encapsulator.cpp| 16
6 files changed, 31 insertions(+), 15 deletions(-)
diff --git a/Normalize.cpp b/Normalize.cpp
index afbd356..65df257 100644
--- a/Normalize.cpp
+++ b/Normalize.cpp
@@ -119,7 +119,8 @@ string TECH_SUBCLASSES[MAX_SUB_CLASS] = {
"Mono_Duplex",
"AutoDuplex",
"K10",
-"CuHdIPH"
+"CuHdIPH",
+"CenterAligned"
};
/** string array of shortening replacements */
diff --git a/Normalize.h b/Normalize.h
index 0839174..fe5cb67 100644
--- a/Normalize.h
+++ b/Normalize.h
@@ -6,7 +6,7 @@
#define MAX_TECH_CLASS_PDL 67
#define MAX_TECH_CLASS 77
#define MAX_FAMILY_CLASS 54
-#define MAX_SUB_CLASS 32
+#define MAX_SUB_CLASS 33
#define COLOR "Color"
diff --git a/base/models.py b/base/models.py
index 46c44e4..5776831 100644
--- a/base/models.py
+++ b/base/models.py
@@ -272,7 +272,8 @@ TECH_SUBCLASSES = [
"Mono_Duplex",
"AutoDuplex",
"K10",
-"CuHdIPH"
+"CuHdIPH",
+"CenterAligned"
]
TECH_SUBCLASSES.sort()
diff --git a/data/models/models.dat b/data/models/models.dat
index 113cf26..fc3ef33 100644
--- a/data/models/models.dat
+++ b/data/models/models.dat
@@ -18504,7 +18504,7 @@ support-type=2
support-ver=0.9.5
tech-class=LJMono
family-class=LJ-Class6
-tech-subclass=Normal
+tech-subclass=CenterAligned
tech-type=3
usb-pid=0
usb-vid=3f0
@@ -18587,7 +18587,7 @@ support-type=2
support-ver=0.9.5
tech-class=LJMono
family-class=LJ-Class6
-tech-subclass=Normal
+tech-subclass=CenterAligned
tech-type=3
usb-pid=0
usb-vid=3f0
@@ -18830,7 +18830,7 @@ support-type=2
support-ver=0.9.5
tech-class=LJMono
family-class=LJ-Class6
-tech-subclass=Normal
+tech-subclass=CenterAligned
tech-type=3
usb-pid=0
usb-vid=3f0
diff --git a/prnt/drv/hpcups.drv.in.template b/prnt/drv/hpcups.drv.in.template
index 9dddc2b..351e966 100644
--- a/prnt/drv/hpcups.drv.in.template
+++ b/prnt/drv/hpcups.drv.in.template
@@ -13730,6 +13730,12 @@ Group "RLT/HP Real Life Technologies"
Choice "Draft/Draft (Economy)" "<>setpagedevice"
Choice "Best/Best" "<>setpagedevice"
+ /* Dummy option to handle the center-aligned paper guide feature of the
+ LaserJet 1100 family */
+ Option "PaperAlignment/Paper Alignment" PickOne AnySetup 10.0
+ *Choice "Left" ""
+ Choice "Center" "<>setpagedevice"
+
// Duplexer is optional...
Installable "OptionDuplex/Duplexer Installed"
@@ -13805,11 +13811,19 @@ Group "RLT/HP Real Life Technologies"
MinSize 1in 4in
MaxSize 8.5in 14in
-// <%LJMono:Normal%>
{
+ UIConstraints "*PaperAlignment Center *MediaType"
+ // <%LJMono:Normal%>
+}
+{
+ UIConstraints "*PaperAlignment Center *MediaType"
UIConstraints "*OutputMode Best *MediaType"
// <%LJMono:300dpiOnly%>
}
+{
+ UIConstraints "*PaperAlignment Left *MediaType"
+ // <%LJMono:CenterAligned%>
+}
} // End Supported media sizes.
{
diff --git a/prnt/hpcups/Encapsulator.cpp b/prnt/hpcups/Encapsulator.cpp
index e661f4a..9e78033 100644
--- a/prnt/hpcups/Encapsulator.cpp
+++ b/prnt/hpcups/Encapsulator.cpp
@@ -255,6 +255,14 @@ void Encapsulator::sendJobHeader()
addToHeader((const BYTE *) szStr, 20);
}
+top_margin = m_pMA->printable_start_y - ((m_pJA->mech_offset * m_pQA->actual_vertical_resolution)/1000);
+int left_margin = 0;
+if (m_pJA->integer_values[1] > 0)
+{
+left_margin = ((m_pJA->integer_values[1] * m_pQA->horizontal_resolution) / 100 - m_pMA->printable_width) / 2;
+}
+addToHeader("\x1b*p%dx%dY", left_margin, top_margin);
+
const BYTE *pgrafMode = grafMode2;
if (m_pJA->color_mode == 0)
{
@@ -266,14 +274,6 @@ void Encapsulator::sendJobHeader()
addToHeader((const BYTE *) pgrafMode, 5);
addToHeader((const BYTE *) seedSame, sizeof(seedSame));
-top_margin = m_pMA->printable_start_y - ((m_pJA->mech_offset * m_pQA->actual_vertical_resolution)/1000);
-int left_margin = 0;
-if (m_pJA->integer_values[1] > 0)
-{
-left_margin = ((m_pJA->integer_values[1] * m_pQA->horizontal_resolution) / 100 - m_pMA->printable_width) / 2;
-}
-addToHeader("\x1b*p%dx%dY", left_margin, top_margin);
-
return;
}
--
2.36.1
Bug#1015792: [Pkg-openssl-devel] Bug#1015792: openssl: Explicitly use libatomic on ARC/NIOS2/SPARC
control: notfound -1 1.1.1f-1ubuntu2.12 control: found -1 3.0.4-2 On 2022-07-21 12:25:51 [+0200], Alexey Brodkin wrote: > Package: openssl > Version: 1.1.1f-1ubuntu2.12 Please use Debian's verions, not Ubunut's. This will only be addressed in unstable as it does not affect stable/oldstable in any way. > openssl fails to build on 32-bit architectures such as ARC, NIOS2 & SPARC > due to the fact that 64-bit atomisc are not natively supported. … > And for the record, "linux-latomic" is already used for the rest > of 32-bit architectures. So nothing new here. Not all of them. I guess that NIOS is used by Synopsys. I hope you tested Sparc/ARC on recent toolchains. I *think* Sparc is dead and the world does Sparc64 if at all. There are still other 32bit architecures with -latomic such as s390, avr32 or hppa. The latter builds regulary so that looks fine. The other two don't show on buildd.d.o so I can't tell. Sebastian
Bug#962715: Incompatible API versions: encoded with [1,17,5,4] but attempted to decode with [1,20]
Just to note that this issue has appeared again. pandoc-sidenote version 0.22.1.0-1+b1 is built against pandoc-types version [1,22,2], but the versions of pandoc available are built against lower versions ([1,21] for the version in experimental, [1,20] for the version in unstable). Perhaps a simple solution for this problem would be to merge the two packages (bundle pandoc-sidenote together with pandoc)?
Bug#1015966: ci.debian.net: Please enable KVM support on all x86 runners
Package: debci Severity: wishlist Dear Maintainer, In order to test behavior at early boot stage we have autopkgtests in src:cryptsetup (resp. src:dropbear) that launch a virtual machine and mock user interaction through the serial console (resp. SSH) to unlock the disks and check that boot eventually yields a login prompt. (These autopkgtests don't use ‘Restrictions: isolation-machine’; they launch QEMU themselves and interact with the guest at early boot stage.) This appears to work rather well and is reasonably fast on x86 thanks to hardware virtualization support. AFAICT the debci runners don't expose /dev/kvm, but the device can be created in the autopkgtest with `mknod /dev/kvm c 10 232` before calling QEMU. However not all amd64 runners seem to support KVM in the first place: ci-worker13 (which fortunately seem to pick most jobs) does support it but AFAICT neither do ci-worker02 nor ci-worker05. This means that depending on the runners the tests are more likely to timeout and fail. (Moreover we'd like to test multiple layouts to check for past regressions, and without KVM it gets very slow.) Presumably all amd64 hosts actually do have KVM support but don't always advertise the capability to the runner. Would it be possible to enable KVM support on all x86 runners? Alternatively, is there a mechanism to exclude specific runners for a given source package? Also please consider pre-creating /dev/kvm on runners with KVM support (this is normally taken care of by udev but can be done manually), that way we can drop the ‘Restrictions: needs-root’ on our autopkgtests :-) Thanks for maintaining debci! -- Guilhem. signature.asc Description: PGP signature
Bug#1015967: RFS: psocksxx/1.1.1-3 -- psocksxx is a C++ wrapper for POSIX sockets
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "psocksxx": Package name: psocksxx Version : 1.1.1-3 Upstream Author : [fill in name and email of upstream] URL : https://nukedzn.github.io/psocksxx License : LGPL-3+ Vcs : https://jff.email/cgit/psocksxx.git/ Section : libs The source builds the following binary packages: libpsocksxx0 - psocksxx is a C++ wrapper for POSIX sockets libpsocksxx-dev - psocksxx is a C++ wrapper for POSIX sockets (development files) libpsocksxx-doc - psocksxx is a C++ wrapper for POSIX sockets (documentation) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/psocksxx/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/psocksxx/psocksxx_1.1.1-3.dsc or from git https://jff.email/cgit/psocksxx.git/?h=release%2Fdebian%2F1.1.1-3 Changes since the last upload: psocksxx (1.1.1-3) unstable; urgency=medium . * Disable Link time optimization (Closes: #1015593): - debian/rules: Add optimize=-lto to DEB_BUILD_MAINT_OPTIONS. * Declare compliance with Debian Policy 4.6.1.0 (No changes needed). * To build new files remove symbols files (Closes: #1014158). * debian/copyright: - Add year 2022 to myself. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1015968: RFS: xbase64/3.1.2-14 -- xbase compatible C++ class library
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xbase64":
Package name: xbase64
Version : 3.1.2-14
Upstream Author : [fill in name and email of upstream]
URL : http://sourceforge.net/projects/xdb/
License : LGPL-2.1+, GPL-2+
Vcs : https://jff.email/cgit/xbase64.git
Section : libs
The source builds the following binary packages:
libxbase64-1 - xbase compatible C++ class library (shared libraries)
libxbase64-dev - xbase compatible C++ class library (development
files)
libxbase64-bin - xbase compatible C++ class library (utilities)
libxbase64-doc - xbase compatible C++ class library (documentation)
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/xbase64/
Alternatively, you can download the package with 'dget' using this
command:
dget -x
https://mentors.debian.net/debian/pool/main/x/xbase64/xbase64_3.1.2-14.dsc
or from
git https://jff.email/cgit/xbase64.git/?h=release%2Fdebian%2F3.1.2-14
Changes since the last upload:
xbase64 (3.1.2-14) unstable; urgency=medium
.
* Migrate to debhelper-compat 13:
- debian/control: Add debhelper-compat (= 13).
- Remove debian/compat.
- Add usr/bin/xbase64-config into new debian/not-installed.
- Add usr/lib/${DEB_HOST_MULTIARCH}/libxbase64.la to
debian/libxbase64-bin.install.
* Declare compliance with Debian Policy 4.6.1.0 (No changes needed).
* debian/copyright:
- Add year 2022 to myself.
* Disable Link time optimization (Closes: #1015707):
- debian/rules: Add optimize=-lto to DEB_BUILD_MAINT_OPTIONS.
* debian/control: Add Rules-Requires-Root: no.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
git: https://jff.email/cgit/
Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst
My wish list:
- Please send me a picture from the nature at your home.
signature.asc
Description: This is a digitally signed message part
Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
On 24 juil. 2022 09:39, Andy wrote: > Hi Christian Hi Andy, Cc to the BTS. > I have come across a bug in the deb-multimedia package kodi-data. The > debian maintainer of firewalld recommended to file a bug with debian- > multimedia. I'll fix that. But why firewalld install services for packages not installed ? firewalld services must be managed as systemd does. Christian
Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
On 24 juil. 2022 09:39, Andy wrote: > Hi Christian Hi again, > I have come across a bug in the deb-multimedia package kodi-data. The > debian maintainer of firewalld recommended to file a bug with debian- > multimedia. firewalld will remove these files. https://github.com/firewalld/firewalld/pull/552 Christian
Bug#1015085: texworks-manual: FTBFS: make[4]: *** [Makefile:66: index.ind] Error 1
Hi Hilmar, On 22/07/22 at 14:55 +0200, Hilmar Preuße wrote: > Am 21.07.2022 um 00:20 teilte Hilmar Preuße mit: > > Am 16.07.2022 um 15:56 teilte Lucas Nussbaum mit: > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > > on amd64. > > > > > For now there is an MWE, which compiles fine using LaTeX but can't be > > processed using htlatex (that's what we try to do). I'll try to contact > > TeX people soon: > > > > I got a heads up from "Michal Hoftich", so I'll start packaging next round > of texlive-base, -lang, -extra in the hope to solve the issue. > > https://tex.stackexchange.com/questions/651631/htlatex-fails-to-convert-file > > @Lucas: are there more packages affected using htlatex? No, only that one Lucas
Bug#1015786: marked as pending in neovim
> Control: tag -1 pending Thanks. I also think your fix is most reasonable choice. Osamu
Bug#1012096: RFS: tractor/3.14-1 [ITP] -- Setup an onion routing proxy
I changed the watch from pypi.debian.net to the upstream git repository. I rebased the salsa to use the new version 3.14 and built the new deb file with `gbp buildpackage` and put it in mentors. I also changed the copyright file to use GPL-3+. Is everything right there? Danial Behzadi
Bug#1015964: logrotate.conf: olddir may extend tilde to HOME directory
Package: logrotate Version: 3.18.0-2+deb11u1 Severity: wishlist Tags: upstream Dear Maintainer, thanks for your work. olddir may expand tilde (~) to the HOME directory of the current user as entries do. Note that this looks as an inconsistency: entries expand ~ (tilde) while oldir's do not. Best wishes, Jerome -- Package-specific info: Contents of /etc/logrotate.d total 84 -rw-r--r-- 1 root root 120 Apr 19 2019 alternatives -rw-r--r-- 1 root root 173 Mar 14 2013 apt -rw-r--r-- 1 root root 79 Nov 7 2012 aptitude -rw-r--r-- 1 root root 378 Jan 10 2014 backupsync -rw-r--r-- 1 root root 130 Aug 29 2018 btmp -rw-r--r-- 1 root root 593 Aug 22 2015 chrony -rw-r--r-- 1 root root 181 Jun 9 2015 cups-daemon -rw-r--r-- 1 root root 319 Jan 10 2014 ddns -rw-r--r-- 1 root root 112 Apr 19 2019 dpkg -rw-r--r-- 1 root root 128 May 4 2021 exim4-base -rw-r--r-- 1 root root 108 May 4 2021 exim4-paniclog -rw-r--r-- 1 root root 716 Jul 12 2019 fetchmail -rw-r--r-- 1 root root 406 Jul 28 2014 firehol -rw-r--r-- 1 root root 119 Aug 27 2014 gapd -rw-r--r-- 1 root root 363 Aug 24 2021 hdak -rw-r--r-- 1 root root 157 Jan 16 2012 pm-utils -rw-r--r-- 1 root root 374 Feb 17 2021 rsyslog drwxr-xr-x 2 root root 4096 Jul 12 2019 scripts -rw-r--r-- 1 root root 401 Jul 2 2018 ulogd2 -rw-r--r-- 1 root root 58 Apr 17 2017 wdm -rw-r--r-- 1 root root 145 Feb 19 2018 wtmp -- System Information: Debian Release: Bullseye* APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages logrotate depends on: ii anacron 2.3-30 ii cron [cron-daemon] 3.0pl1-137 ii libacl1 2.2.53-10 ii libc6 2.31-13+deb11u3 ii libpopt01.18-2 ii libselinux1 3.1-3 Versions of packages logrotate recommends: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-2 logrotate suggests no packages. -- no debconf information
Bug#1015965: libgit2: missing SSH support
Source: libgit2 Version: 1.4.3+dfsg.1-1 Severity: important Tags: patch X-Debbugs-Cc: f.gruenbich...@proxmox.com Hi! libgit2 1.3 was built with SSH support enabled (by default). upstream switched the default with 1.4, it would be appreciated if it could be explicitly enabled (again) for the Debian build. cargo transitively depends on and links with libgit2 (via librust-git2-dev -> librust-libgit2-sys-dev) and requires SSH support, and the newest cargo version (that I am currently packaging ;)) requires libgit2 1.4.x. I opened an MR on salsa and tested my cargo update with the resulting binary packages: https://salsa.debian.org/debian/libgit2/-/merge_requests/5 Thanks in advance for your consideration (and work on libgit2!). Fabian -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/16 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
Bug#1015971: ITP: pamixer -- pulseaudio command line mixer
Package: wnpp Severity: wishlist Owner: Tzafrir Cohen X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: pamixer Version : 1.6 Upstream Author : Clément Démoulins * URL : https://github.com/cdemoulins/pamixer * License : GPL-3+ Programming Lang: C++ Description : pulseaudio command line mixer pamixer is like amixer but for pulseaudio. It can control the volume levels of the sinks. It is used by the SXMO mobile phone interface, an ITP to follow shortly. It will be packaged in the debian namespace on Salsa: https://salsa.debian.org/debian/pamixer
Bug#1012895: aptitude: ftbfs with GCC-12
Control: tags -1 + patch On Thu, 16 Jun 2022 12:07:38 + Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The > severity of this report will be raised before the bookworm release. I tried to build aptitude, found it fails due to cwidget bug #1015925. I tried to look at this failure, which also happens after fixing that. I don't know enough C++ but seems that the operator<< function in the test_parsers.cc file taking std::optional as a parameter is not being found by GCC 12 even though it should be found. The g++ output was verbose but the clang++ output was very clear. The issue is that the operator<< functions are not declared before the call site, so forward declarations before HelperMacros.h are needed: #include template std::ostream <<(std::ostream , const std::optional o); template std::ostream <<(std::ostream , const std::vector v); #include I'm not sure how to contribute this change to the package because this should be a native package but isn't and has debian/patches/ but also an upstream master branch that seems to be unused. I suggest merging the contents of debian/patches/ to the upstream master branch and then cherry-picking the FTBFS patches to a new minor release branch instead of using debian/patches/. I've filed two merge requests with two different approaches, one is a commit for the master branch and one a patch for the debian-sid branch. https://salsa.debian.org/apt-team/aptitude/-/merge_requests/14 https://salsa.debian.org/apt-team/aptitude/-/merge_requests/13 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1015929: python3-fast-histogram: Installation of the C extension might be incorrect
Package: python3-fast-histogram Version: 0.11-1 Severity: serious Package: python3-fast-histogram Version: 0.9-2+b1 /usr/lib/python3/dist-packages/fast_histogram/_histogram_core.cpython-310-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/fast_histogram/_histogram_core.cpython-39-x86_64-linux-gnu.so Package: python3-fast-histogram Version: 0.11-1+b1 /usr/lib/python3/dist-packages/fast_histogram/_histogram_core.abi3.so
Bug#1014306: crun - seriously out of date
On Fri, 22 Jul 2022 15:43:56 +0200 Faidon Liambotis wrote: > On Sun, Jul 03, 2022 at 09:20:37PM +0200, Bastian Blank wrote: > > crun was not uploaded since before the release of Debian 11. It is now > > seriously out of date and even fails hard as root, see #1012053. > > I built 1.4.5 using the existing Debian packaging and with no changes > other than dropping all d/patches as they are now merged upstream. The > package is fully functional with my testing. > > 1.5 was released 2 days ago as well, but I haven't tried to build that > yet. > > Dmitry, are you still working on this package? I noticed that it's under > the debian group in Salsa -- would you be OK if someone else made an > upload? CC'ing @Dmitry explicitly in case that helps. @Faidon, I suppose it would be fine to NMU and put it into DELAYED/10 atleast till we have time for an ACK. This is triggering a bunch of auto-rm and hence it is prudent. Do consider doing so if you agree. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1015934: Acknowledgement of maintainer-only report (vim-airline: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
diffstat for vim-airline-0.11 vim-airline-0.11
control |4 +-
install |3 -
postinst | 22
preinst | 24 --
prerm| 22
vim-airline.neovim-addon |1
vim-airline.vim-addon|1
vim-airline.yaml | 80 ---
8 files changed, 5 insertions(+), 152 deletions(-)
diff -Nru vim-airline-0.11/debian/control vim-airline-0.11/debian/control
--- vim-airline-0.11/debian/control 2019-11-12 12:11:59.0 +0300
+++ vim-airline-0.11/debian/control 2019-11-12 12:11:59.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Jonathan Carter
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), dh-sequence-vim-addon
Standards-Version: 4.4.1
Homepage: https://github.com/vim-airline/vim-airline
Vcs-Git: https://salsa.debian.org/vim-team/vim-airline.git
@@ -10,7 +10,7 @@
Package: vim-airline
Architecture: all
-Depends: ${misc:Depends}, vim, vim-addon-manager
+Depends: ${misc:Depends}, ${vim-addon:Depends}
Recommends: vim-airline-themes
Suggests: fonts-powerline
Description: Lean & mean status/tabline for vim that's light as air
diff -Nru vim-airline-0.11/debian/install vim-airline-0.11/debian/install
--- vim-airline-0.11/debian/install 2018-12-18 02:13:01.0 +0300
+++ vim-airline-0.11/debian/install 2019-11-12 12:11:59.0 +0300
@@ -1,2 +1 @@
-autoload doc plugin t usr/share/vim/addons
-debian/vim-airline.yaml usr/share/vim/registry
+autoload doc plugin t usr/share/vim-airline
diff -Nru vim-airline-0.11/debian/postinst vim-airline-0.11/debian/postinst
--- vim-airline-0.11/debian/postinst2018-12-18 02:13:01.0 +0300
+++ vim-airline-0.11/debian/postinst1970-01-01 03:00:00.0 +0300
@@ -1,22 +0,0 @@
-#! /bin/bash
-# postinst script for vim-airline
-
-set -e
-
-case "$1" in
-configure)
-vim-addon-manager -w install airline
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-airline-0.11/debian/preinst vim-airline-0.11/debian/preinst
--- vim-airline-0.11/debian/preinst 2018-12-18 02:13:01.0 +0300
+++ vim-airline-0.11/debian/preinst 1970-01-01 03:00:00.0 +0300
@@ -1,24 +0,0 @@
-#!/bin/sh
-# preinst script for vim-airline
-
-set -e
-
-case "$1" in
-install|upgrade)
-if [ "$(vim-addons status | grep airline | awk '{print $3}')" =
"installed" ] ; then
-vim-addon-manager -w remove airline
-fi
-;;
-
-abort-upgrade)
-;;
-
-*)
-echo "preinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-airline-0.11/debian/prerm vim-airline-0.11/debian/prerm
--- vim-airline-0.11/debian/prerm 2018-12-18 02:13:01.0 +0300
+++ vim-airline-0.11/debian/prerm 1970-01-01 03:00:00.0 +0300
@@ -1,22 +0,0 @@
-#!/bin/sh
-# prerm script for vim-airline
-
-set -e
-
-case "$1" in
-remove|upgrade|deconfigure)
-vim-addon-manager -w remove airline
-;;
-
-failed-upgrade)
-;;
-
-*)
-echo "prerm called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-airline-0.11/debian/vim-airline.neovim-addon
vim-airline-0.11/debian/vim-airline.neovim-addon
--- vim-airline-0.11/debian/vim-airline.neovim-addon1970-01-01
03:00:00.0 +0300
+++ vim-airline-0.11/debian/vim-airline.neovim-addon2019-11-12
12:11:59.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-airline airline
diff -Nru vim-airline-0.11/debian/vim-airline.vim-addon
vim-airline-0.11/debian/vim-airline.vim-addon
--- vim-airline-0.11/debian/vim-airline.vim-addon 1970-01-01
03:00:00.0 +0300
+++ vim-airline-0.11/debian/vim-airline.vim-addon 2019-11-12
12:11:59.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-airline airline
diff -Nru vim-airline-0.11/debian/vim-airline.yaml
vim-airline-0.11/debian/vim-airline.yaml
--- vim-airline-0.11/debian/vim-airline.yaml2019-11-12 12:11:59.0
+0300
+++ vim-airline-0.11/debian/vim-airline.yaml1970-01-01 03:00:00.0
+0300
@@ -1,80 +0,0 @@
-addon: airline
-description: "Lean & mean status/tabline for vim that's light as air"
-files:
- - plugin/airline.vim
- - doc/airline.txt
- - autoload/airline.vim
- - autoload/airline/extensions/tabline/formatters/default.vim
- - autoload/airline/extensions/tabline/formatters/unique_tail.vim
- -
autoload/airline/extensions/tabline/formatters/unique_tail_improved.vim
- - autoload/airline/extensions/tabline/formatters/tabnr.vim
- -
Bug#1015941: Acknowledgement of maintainer-only report (vim-fugitive: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
The README.Debian file mentioned vim-addons, and I removed the file. As far as
I can see, vim-fugitive was activated automatically in the postinst script.
diffstat for vim-fugitive-3.4 vim-fugitive-3.4
README.Debian | 19 ---
control |4 ++--
vim-fugitive.install | 13 ++---
vim-fugitive.neovim-addon |1 +
vim-fugitive.postinst | 41 -
vim-fugitive.preinst | 38 --
vim-fugitive.prerm| 39 ---
vim-fugitive.vim-addon|1 +
vim-fugitive.yaml | 11 ---
9 files changed, 10 insertions(+), 157 deletions(-)
diff -Nru vim-fugitive-3.4/debian/control vim-fugitive-3.4/debian/control
--- vim-fugitive-3.4/debian/control 2021-10-06 19:42:53.0 +0300
+++ vim-fugitive-3.4/debian/control 2021-10-06 19:42:53.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Andrea Capriotti
-Build-Depends: debhelper-compat (= 13)
+Build-Depends: debhelper-compat (= 13), dh-sequence-vim-addon
Standards-Version: 4.6.0
Rules-Requires-Root: no
Homepage: https://github.com/tpope/vim-fugitive
@@ -11,7 +11,7 @@
Package: vim-fugitive
Architecture: all
-Depends: vim, vim-addon-manager, ${misc:Depends}
+Depends: ${misc:Depends}, ${vim-addon:Depends}
Description: Vim plugin to work with Git
vim-fugitive is a wrapper for Vim that complements the command
line interface to Git. The plugin provides an interactive status
diff -Nru vim-fugitive-3.4/debian/README.Debian vim-fugitive-3.4/debian/README.Debian
--- vim-fugitive-3.4/debian/README.Debian 2014-01-28 20:14:50.0 +0400
+++ vim-fugitive-3.4/debian/README.Debian 1970-01-01 03:00:00.0 +0300
@@ -1,19 +0,0 @@
-vim-fugitive for Debian
-Enabling the addons
-===
-
-This package provides a "fugitive" addon for the vim text editor.
-It is not enabled by default. To enable it for you only, run:
-
-$ vim-addons install fugitive
-
-Similarly, to enable it for all users of this system just
-execute (as root):
-
-# vim-addons -w install fugitive
-
-vim-addons is provided by the vim-addon-manager package, have a look at its
-manpage for more information.
-
- -- Andrea Capriotti Tue, 28 Jan 2014 14:08:36 +0100
diff -Nru vim-fugitive-3.4/debian/vim-fugitive.install vim-fugitive-3.4/debian/vim-fugitive.install
--- vim-fugitive-3.4/debian/vim-fugitive.install 2021-10-06 19:42:53.0 +0300
+++ vim-fugitive-3.4/debian/vim-fugitive.install 2021-10-06 19:42:53.0 +0300
@@ -1,7 +1,6 @@
-autoload/ usr/share/vim/addons
-ftdetect/ usr/share/vim/addons
-ftplugin/ usr/share/vim/addons
-plugin/ usr/share/vim/addons
-syntax/usr/share/vim/addons
-doc/usr/share/vim/addons
-debian/vim-fugitive.yamlusr/share/vim/registry
+autoload usr/share/vim-fugitive
+doc usr/share/vim-fugitive
+ftdetect usr/share/vim-fugitive
+ftplugin usr/share/vim-fugitive
+plugin usr/share/vim-fugitive
+syntax usr/share/vim-fugitive
diff -Nru vim-fugitive-3.4/debian/vim-fugitive.neovim-addon vim-fugitive-3.4/debian/vim-fugitive.neovim-addon
--- vim-fugitive-3.4/debian/vim-fugitive.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-fugitive-3.4/debian/vim-fugitive.neovim-addon 2021-10-06 19:42:53.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-fugitive fugitive
diff -Nru vim-fugitive-3.4/debian/vim-fugitive.postinst vim-fugitive-3.4/debian/vim-fugitive.postinst
--- vim-fugitive-3.4/debian/vim-fugitive.postinst 2014-06-27 16:34:54.0 +0400
+++ vim-fugitive-3.4/debian/vim-fugitive.postinst 1970-01-01 03:00:00.0 +0300
@@ -1,41 +0,0 @@
-#! /bin/bash
-# postinst script for vim-fugitive
-#
-# see: dh_installdeb(1)
-
-set -e
-
-
-# summary of how this script can be called:
-# * `configure'
-# * `abort-upgrade'
-# * `abort-remove' `in-favour'
-#
-# * `abort-deconfigure' `in-favour'
-# `removing'
-#
-#
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
-configure)
-vim-addon-manager -w install fugitive
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-fugitive-3.4/debian/vim-fugitive.preinst vim-fugitive-3.4/debian/vim-fugitive.preinst
--- vim-fugitive-3.4/debian/vim-fugitive.preinst 2014-06-27 16:35:43.0 +0400
+++ vim-fugitive-3.4/debian/vim-fugitive.preinst 1970-01-01 03:00:00.0 +0300
@@ -1,38 +0,0 @@
-#!/bin/sh
-#
Bug#1015953: netatalk: Please remove hard dependencies on Systemd and alloe compatibility with SysVrc
Package: netatalk Version: 3.1.12~ds-8 Severity: wishlist Netatalk requires Systemd to be installed (and thus automatically be active). Debian Bullyeye still supports SysVrc. Please (re-)enable compatibility with SysVrc, and remove any hard dependencies on any particular Init System. Most traditional server tasks (including Samba) do not impose this dependency. -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/2 CPU threads) 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/bash Init: sysvinit (via /sbin/init) Versions of packages netatalk depends on: ii init-system-helpers 1.60 ii libacl1 2.2.53-10 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libc62.31-13+deb11u3 ii libcrack22.9.6-3.4 ii libcrypt11:4.4.18-4 ii libdb5.3 5.3.28+dfsg1-0.8 pn libdbus-glib-1-2 ii libevent-2.1-7 2.1.12-stable-1 ii libgcrypt20 1.8.7-6 ii libglib2.0-0 2.66.8-1 ii libgssapi-krb5-2 1.18.3-6+deb11u1 ii libkrb5-31.18.3-6+deb11u1 ii libldap-2.4-22.4.57+dfsg-3+deb11u1 ii libmariadb3 1:10.5.15-0+deb11u1 ii libpam-modules 1.4.0-9+deb11u1 ii libpam0g 1.4.0-9+deb11u1 ii libssl1.11.1.1n-0+deb11u3 ii libtalloc2 2.3.1-2+b1 ii libtdb1 1.4.3-1+b1 pn libtracker-sparql-2.0-0 ii libwrap0 7.6.q-31 ii lsb-base 11.1.0 ii netbase 6.3 ii perl 5.32.1-4+deb11u2 Versions of packages netatalk recommends: pn avahi-daemon ii cracklib-runtime 2.9.6-3.4 pn dbus ii lsof 4.93.2+dfsg-1.1 ii procps2:3.3.17-5 ii python3 3.9.2-3 pn python3-dbus pn tracker Versions of packages netatalk suggests: ii quota 4.06-1
Bug#989085: ITP: gamescope -- micro-compositor for games
Update: packaging is now available at https://salsa.debian.org/games-team/gamescope. Almost done, I will probably upload it next week :) Cheers, Stephan
Bug#884829: Still present in Debian 11
Hi, I can confirm this bug still exists in xserver-xorg-core 2:1.20.11-1+deb11u1; I have been suffering from it ever since I upgraded from Debian 10 to Debian 11 a few months ago. The memory usage of Xorg process keeps growing until eventually the laptop becomes unresponsive and OOM killer starts reaping random processes and everything comes crashing down. In my case, I tracked the problem mainly to xfdesktop4 and xfce4-panel (leaking about 5 MB per hour when the machine is idle). Only when I kill both of them the increase in memory consumption stops, although the already consumed memory is not released. Using the machine makes the rate of leaking worse, so clearly there are many other sources that can trigger the leak. I can also confirm that if I install audacious and play it with the visualization on, the leak increases to about 57 MB per hour, so the problem I experience is very likely the same one as reported here. I'm really happy to finally learn I'm not crazy and someone else noticed the issue as well (although I did not expect it to go all the way back to 2017). Is there anything I can do to help move this along? Should I try testing the patch? Or open a bug report upstream? Thanks, Martin
Bug#953046: Wrongly picks AZERTY layout when alternative Canadian layout is present.
Dear Gunnar and Nobuhiro,
it took me some time to debug the issue further, but here are some
new information that I hope you will find useful:
In finally found that the AZERTY layout is imposed by the Japanese
input system when the language I chose in Gnome is French from France,
and switching it to French from Canada or of course English restores
the QWERTY layout.
So it looks like the problem did not have to do with the presence of
the alternative canadian keyboard layout.
I inspected my locales when using the different variants of French
and the most prominent change is LANG, with either fr_FR or fr_CA.
So maybe ibus or Mozc hardcode the input layout to AZERTY through
a guess based on the fr_FR locale, assuming that all French speakers
from France type on AZERTY keyboards ?
Le Sun, Mar 21, 2021 at 03:05:38PM +0100, Gunnar Hjalmarsson a écrit :
>
> Can you please run these terminal commands:
>
> gsettings get org.gnome.desktop.input-sources sources
[('ibus', 'mozc-jp'), ('xkb', 'jp'), ('xkb', 'ca+multix')]
> gsettings get org.freedesktop.ibus.general use-system-keyboard-layout
false
> cat /etc/default/keyboard
XKBLAYOUT=jp,ca
XKBVARIANT=,multix
BACKSPACE=guess
And also:
cat /etc/default/locale
LANG=fr_CA.UTF-8
Have a nice day,
--
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from work, https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1015937: Acknowledgement of maintainer-only report (vim-airline-themes: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
diffstat for vim-airline-themes-0+git.20210713-97cf3e6 vim-airline-themes-0+git.20210713-97cf3e6
control |4
install |3
postinst| 22 ---
preinst | 24
prerm | 22 ---
vim-airline-themes.neovim-addon |1
vim-airline-themes.vim-addon|1
vim-airline-themes.yaml | 238
8 files changed, 5 insertions(+), 310 deletions(-)
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/control vim-airline-themes-0+git.20210713-97cf3e6/debian/control
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/control 2022-03-18 13:09:46.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/control 2022-03-18 13:09:46.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Jonathan Carter
-Build-Depends: debhelper-compat (= 13)
+Build-Depends: debhelper-compat (= 13), dh-sequence-vim-addon
Standards-Version: 4.6.0
Homepage: https://github.com/vim-airline/vim-airline-themes
Vcs-Git: https://salsa.debian.org/vim-team/vim-airline-themes.git
@@ -11,7 +11,7 @@
Package: vim-airline-themes
Architecture: all
-Depends: ${misc:Depends}, vim, vim-addon-manager, vim-airline
+Depends: vim-airline, ${misc:Depends}, ${vim-addon:Depends}
Description: official theme collection for vim-airline
Official collection of themes for vim-airline.
.
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/install vim-airline-themes-0+git.20210713-97cf3e6/debian/install
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/install 2022-03-18 13:09:46.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/install 2022-03-18 13:09:46.0 +0300
@@ -1,2 +1 @@
-autoload plugin usr/share/vim/addons
-debian/vim-airline-themes.yaml usr/share/vim/registry
+autoload plugin usr/share/vim-airline
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/postinst vim-airline-themes-0+git.20210713-97cf3e6/debian/postinst
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/postinst 2017-07-12 13:16:40.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/postinst 1970-01-01 03:00:00.0 +0300
@@ -1,22 +0,0 @@
-#! /bin/bash
-# postinst script for vim-airline
-
-set -e
-
-case "$1" in
-configure)
-vim-addon-manager -w install airline-themes
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/preinst vim-airline-themes-0+git.20210713-97cf3e6/debian/preinst
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/preinst 2017-07-12 13:16:58.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/preinst 1970-01-01 03:00:00.0 +0300
@@ -1,24 +0,0 @@
-#!/bin/sh
-# preinst script for vim-airline
-
-set -e
-
-case "$1" in
-install|upgrade)
-if [ "$(vim-addons status | grep airline-themes | awk '{print $3}')" = "installed" ] ; then
-vim-addon-manager -w remove airline-themes
-fi
-;;
-
-abort-upgrade)
-;;
-
-*)
-echo "preinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/prerm vim-airline-themes-0+git.20210713-97cf3e6/debian/prerm
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/prerm 2017-07-12 13:17:07.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/prerm 1970-01-01 03:00:00.0 +0300
@@ -1,22 +0,0 @@
-#!/bin/sh
-# prerm script for vim-airline
-
-set -e
-
-case "$1" in
-remove|upgrade|deconfigure)
-vim-addon-manager -w remove airline-themes
-;;
-
-failed-upgrade)
-;;
-
-*)
-echo "prerm called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.neovim-addon vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.neovim-addon
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.neovim-addon 2022-03-18 13:09:46.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-airline airline-themes
diff -Nru vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.vim-addon vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.vim-addon
--- vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.vim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-airline-themes-0+git.20210713-97cf3e6/debian/vim-airline-themes.vim-addon 2022-03-18 13:09:46.0 +0300
@@ -0,0 +1 @@
Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version
Hi, On 2022-07-24 12:39, Alejandro Colomar (man-pages) wrote: > Hi Aurelien, > > On 7/23/22 11:43, Aurelien Jarno wrote: > > Hi, > > > > On 2022-07-19 21:55, Alejandro Colomar wrote: > > > Package: libc6-dev > > > Version: 2.33-8 > > > Severity: normal > > > X-Debbugs-Cc: alx.manpa...@gmail.com > > > > > > > > > Hi, > > > > > > We had a discussion in NGINX Unit about if we should use __NR_xxx > > > or SYS_xxx syscall numbers. As maintainer of the Linux man-pages, > > > I suggested that we should use the libc macros (SYS_xxx), since > > > they are compatible with other non-Linux systems, and also because > > > they are the documented way for user space. However, there was > > > some concern that someone might be running a new kernel with an > > > old glibc, and that __NR_xxx symbols might be available but not > > > SYS_xxx in that case. > > > > Yes that sounds good. > > > > > Since the (included through ) > > > header is generated automatically from the kernel headers at glibc > > > build time, Debian should make sure that the latest available > > > kernel headers are used, so building the latest Sid glibc package > > > should be done on a system with also the latest kernel available > > > in Sid, to have a complete SYS_xxx list. > > > > This is basically what is done, the buildd chroots are updated twice a > > week, so in the worst case glibc is build against a kernel headers > > package that is 4 days old. > > Is it? I have kernel 5.18, but my bits/syscalls.h still says it was > generated from kernel 5.10 (that's a long time ago). I have the latest Sid > packages for both the kernel and glibc. Yes, this is definitely the case, glibc 2.33-8 has been built against linux-libc-dev 5.18.5-1. What is wrong is "header is generated automatically from the kernel headers at glibc build time". They are generated by upstream at release time, not at build time. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#997862: wireplumber: Bluetooth is not supported, breaking audio of existing systems
On 2021-10-26 12:21:20 [+0200], Vincent Lefevre wrote: > On 2021-10-26 12:00:34 +0200, Dylan Aïssi wrote: > > Wireplumber needs the libspa-0.2-bluetooth package to support > > bluetooth. I guess it was missing from your system. > > libspa-0.2-bluetooth is only a plugin, wireplumber can work without > > it. This is why it is not a dependency. > > OK, but then, this should be announced in a NEWS.Debian file > (perhaps pipewire's), since this package has to be installed > manually by the user in the upgrade. > > Ideally, it should be installed automatically for a user who > upgrades from pulseaudio with bluetooth support (note that > this is an automatic upgrade with the new version of pipewire, > not a switch by the user). I would have appreciated this information as well. I hoped that it will either fix by itself or a NEWS.Debian pointer appears. It took me quite some time to figure that out… Sebastian
Bug#964184: [Pkg-openssl-devel] Bug#964184: openssl: gsconnect does not work after update openssl
On 2020-07-03 11:37:39 [+0200], Michael Ott wrote:
> Dear Maintainer,
>
> After update openssl gsconnect does not longer work
>
> I already create a bug report on gsconnect
> https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/886#
>
> ~# cat /var/log/syslog | grep gsconnect
> Jul 3 11:31:57 k-c13 gjs[3863]: JS ERROR: TypeError:
> /[a-zA-Z0-9:]{59}/.exec(...) is
> null#012value@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/protocol/__init__.js:69:57#012get
>
> encryption_info@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/device.js:195:58#012_get@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:185:26#012_exportProperties/<@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:218:30#012@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js:1132:17
> Jul 3 11:31:57 k-c13 gjs[3863]: JS ERROR: TypeError:
> /[a-zA-Z0-9:]{59}/.exec(...) is
> null#012value@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/protocol/__init__.js:69:57#012get
>
> encryption_info@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/device.js:202:15#012_get@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:185:26#012_exportProperties/<@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:218:30#012@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js:1132:17
> Jul 3 11:31:57 k-c13 gjs[3863]: JS ERROR: TypeError:
> /[a-zA-Z0-9:]{59}/.exec(...) is
> null#012value@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/protocol/__init__.js:69:57#012get
>
> encryption_info@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/device.js:195:58#012_get@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:185:26#012_exportProperties/<@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:218:30#012@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js:1132:17
> Jul 3 11:31:57 k-c13 gjs[3863]: JS ERROR: TypeError:
> /[a-zA-Z0-9:]{59}/.exec(...) is
> null#012value@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/protocol/__init__.js:69:57#012get
>
> encryption_info@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/device.js:202:15#012_get@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:185:26#012_exportProperties/<@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/utils/dbus.js:218:30#012@/srv/home/michael/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js:1132:17
Is this still relevant given that the transition completed?
Sebastian
Bug#1014675: Announced fixed upstream in 102.0.3
Apparently fixed upstream. May we have a hint on 102.0.3 arrival. I know it is vacation period but... Regards, --eric
Bug#1015930: lists.debian.org: Please create debian-livecoding
Package: lists.debian.org Severity: wishlist Dear Maintainer, I would like to ask the creation of a new mailing list with the following details. ** Name ** debian-livecoding ** Rationale ** I want this list to start discussing topics related to Live Coding (for art, music, sound and visuals) inside Debian community. ** Short description ** Discussion on Live Coding for art, music, sound and visuals in Debian ** Long description ** Discussion on Live Coding tools, techniques, events, conferences, packaging and artwork creation. The main goal of this mailing list is to explore and experiment Live Coding tools on Debian, collaborate with others Debian-teams on packaging live-coding-related languages, libraries and tools, and also organize, promote and spread events on those topics among Debian community. Debian Live Coding team page: https://wiki.debian.org/Teams/LiveCoding ** Category ** Miscellaneous Debian ** Subscription Policy ** open ** Post Policy ** open ** Web Archive ** open Thanks, -- Joenio M. Costa
Bug#1015931: chromium: Chromium clutters the filesystem with crash reports
Package: chromium Version: 103.0.5060.134-1~deb11u1 Severity: normal Dear Maintainer, Chromium clutters the filesystem with pending crash reports. Every time I click + to open a new tab, 2 more crash reports are added. The browser continues to function and there's no noticeable change in behavior from the end-user's perspective. $ ls -ltr ~/.config/chromium/Crash\ Reports/pending -rw--- 1 x x 32 Jul 2 18:06 c28e2342-2517-4804-8a2a-cf0b11f85123.meta -rw--- 1 x x 53824 Jul 2 18:06 c28e2342-2517-4804-8a2a-cf0b11f85123.dmp -rw--- 1 x x 32 Jul 2 18:08 62eea42e-4b55-452d-aad5-431fc9aa7373.meta -rw--- 1 x x 47488 Jul 2 18:08 62eea42e-4b55-452d-aad5-431fc9aa7373.dmp -rw--- 1 x x 32 Jul 2 18:08 bd30b77c-271b-49c5-b9c5-356ae171ebed.meta -rw--- 1 x x 53824 Jul 2 18:08 bd30b77c-271b-49c5-b9c5-356ae171ebed.dmp -rw--- 1 x x 32 Jul 2 19:19 4f515fee-d6cc-4259-a88d-28edf6afe15f.meta -rw--- 1 x x 47456 Jul 2 19:19 4f515fee-d6cc-4259-a88d-28edf6afe15f.dmp -rw--- 1 x x 32 Jul 2 19:21 5735f453-8116-4353-9afe-7eccffc7f3ba.meta -rw--- 1 x x 47488 Jul 2 19:21 5735f453-8116-4353-9afe-7eccffc7f3ba.dmp ... -rw--- 1 x x 32 Jul 24 12:51 3a1f60b5-e747-41d5-81aa-08fe826b5d89.meta -rw--- 1 x x 59632 Jul 24 12:51 3a1f60b5-e747-41d5-81aa-08fe826b5d89.dmp -rw--- 1 x x 32 Jul 24 12:53 eac3404f-4eb6-47d4-a5bc-bbede45625c8.meta -rw--- 1 x x 53296 Jul 24 12:53 eac3404f-4eb6-47d4-a5bc-bbede45625c8.dmp -rw--- 1 x x 32 Jul 24 12:53 beff6e3e-ec3b-4ec1-9a74-956d4f4310a2.meta -rw--- 1 x x 53296 Jul 24 12:53 beff6e3e-ec3b-4ec1-9a74-956d4f4310a2.dmp -rw--- 1 x x 32 Jul 24 12:58 a4ed0a35-9b50-414f-b46a-86035ce5c5cf.meta -rw--- 1 x x 59632 Jul 24 12:58 a4ed0a35-9b50-414f-b46a-86035ce5c5cf.dmp -rw--- 1 x x 32 Jul 24 12:58 7485959c-1a55-49d1-b0ab-34fe69752340.meta -rw--- 1 x x 53296 Jul 24 12:58 7485959c-1a55-49d1-b0ab-34fe69752340.dmp $ strings ~/.config/chromium/Crash\ Reports/pending/7485959c-1a55-49d1-b0ab-34fe69752340.dmp ... *** stack smashing detected ***: terminated $ ls -ltr ~/.config/chromium/Crash\ Reports/pending | wc 5093 45830 440471 $ du -c ~/.config/chromium/Crash\ Reports/pending 157M/home/x/.config/chromium/Crash Reports/pending 157Mtotal -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common103.0.5060.134-1~deb11u1 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-02.36.0-2 ii libatomic1 10.2.1-6 ii libatspi2.0-0 2.38.0-4 ii libc6 2.31-13+deb11u3 ii libcairo2 1.16.0-5 ii libcups2 2.3.3op2-3+deb11u2 ii libdbus-1-31.12.20-2 ii libdrm22.4.104-1 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat1 2.2.10-2+deb11u3 ii libflac8 1.3.3-2+deb11u1 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1+deb11u1 ii libgbm120.3.5-1 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4+deb11u2 ii libjpeg62-turbo1:2.0.6-4 ii libjsoncpp24 1.9.4-4 ii liblcms2-2 2.12~rc1-2 ii libminizip11.1-8+b1 ii libnspr4 2:4.29-1 ii libnss32:3.61-1+deb11u2 ii libopenjp2-7 2.4.0-3 ii libopus0 1.3.1-0.1 ii libpango-1.0-0
Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version
Hi Aurelien, On 7/23/22 11:43, Aurelien Jarno wrote: Hi, On 2022-07-19 21:55, Alejandro Colomar wrote: Package: libc6-dev Version: 2.33-8 Severity: normal X-Debbugs-Cc: alx.manpa...@gmail.com Hi, We had a discussion in NGINX Unit about if we should use __NR_xxx or SYS_xxx syscall numbers. As maintainer of the Linux man-pages, I suggested that we should use the libc macros (SYS_xxx), since they are compatible with other non-Linux systems, and also because they are the documented way for user space. However, there was some concern that someone might be running a new kernel with an old glibc, and that __NR_xxx symbols might be available but not SYS_xxx in that case. Yes that sounds good. Since the (included through ) header is generated automatically from the kernel headers at glibc build time, Debian should make sure that the latest available kernel headers are used, so building the latest Sid glibc package should be done on a system with also the latest kernel available in Sid, to have a complete SYS_xxx list. This is basically what is done, the buildd chroots are updated twice a week, so in the worst case glibc is build against a kernel headers package that is 4 days old. Is it? I have kernel 5.18, but my bits/syscalls.h still says it was generated from kernel 5.10 (that's a long time ago). I have the latest Sid packages for both the kernel and glibc. Cheers, Alex Regards Aurelien -- Alejandro Colomar Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
Bug#1015932: src:inkscape: fails to migrate to testing for too long: ftbfs on arm64, ppc64el, s390x
Source: inkscape Version: 1.1.2-3 Severity: serious Control: close -1 1.2.1+ds-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1012496 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:inkscape has been trying to migrate for 62 days [2]. Hence, I am filing this bug. Your package fails to build from source as reported in bug #1012496. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=inkscape OpenPGP_signature Description: OpenPGP digital signature
Bug#887035: cron: Patch by Greek adapted for cron 3.0pl1-137
Hi Tomas,
two remarks:
1) most of Greek's patches which you adapted is about making cron
installable without the package syslog. Were are the parts about
"log-to-stdout-when-in-foreground"? I see that one patch modifies
debian/patches/series, mentioning the file
log-to-stdout-when-in-foreground, but that file is provided nowhere
by the set of patches. By the way, do you know who is "Greek"? She or
he did not reply to questions which I submitted about Bug#887014 ...
Is "Greek" a pseudonyme of yours?
2) I shall not patch cron 3.0pl1-137. You can do it if you want,
for your own usage, of course. If I modify debian's cron package, I
must do it in the testing distribution, so please propose patches
targetting at least cron 3.0pl1-147. Then, if the modification you
are wishing is accepted in debian/testing, I can create a backport to
use in debian/bullseye later, for example a release such as cron
3.0pl1-149~bpo11+1, to be published in bullseye-backports.
Best regards, Georges.
Tomas Pospisek a écrit :
> Package: cron
> Version: 3.0pl1-137
> Followup-For: Bug #887035
> X-Debbugs-Cc: Georges Khaznadar
>
> If anybody wants to use Greek's patch (see [1] and [2]) then I'm attaching my
> version of it adapted to cron 3.0pl1-137 (the version in Debian bullseye).
>
> It comes in two parts: one is the patch and one is
> cron-3.0pl1/debian/patches/log-to-stdout-when-in-foreground to satisfy
> the Debian build infrastructure.
>
> Use the patch like this to build a new, patched cron package:
>
> apt-get source cron
> sudo apt-get build-dep cron
> patch -p0 <
> cron-syslog-fix-and-foreground-stdout.for-new-cron.debianized.patch
> cp log-to-stdout-when-in-foreground cron-3.0pl1/debian/patches
> cd cron-3.0pl1 && dpkg-buildpackage -rfakeroot
>
> *t
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887035#5
> [2]
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=887035;filename=cron-syslog-fix-and-foreground-stdout.patch;msg=5
>
>
>
> -- Package-specific info:
> --- EDITOR:
>
>
> --- /usr/bin/editor:
> /usr/bin/vim.gtk3
>
> --- /usr/bin/crontab:
> -rwxr-sr-x 1 root crontab 43568 Feb 22 2021 /usr/bin/crontab
>
> --- /var/spool/cron:
> drwxr-xr-x 3 root root 4096 Apr 10 2021 /var/spool/cron
>
> --- /var/spool/cron/crontabs:
> drwx-wx--T 2 root crontab 4096 Feb 22 2021 /var/spool/cron/crontabs
>
> --- /etc/cron.d:
> drwxr-xr-x 2 root root 4096 Jul 22 15:03 /etc/cron.d
>
> --- /etc/cron.daily:
> drwxr-xr-x 2 root root 4096 Jul 11 09:33 /etc/cron.daily
>
> --- /etc/cron.hourly:
> drwxr-xr-x 2 root root 4096 Apr 10 2021 /etc/cron.hourly
>
> --- /etc/cron.monthly:
> drwxr-xr-x 2 root root 4096 Apr 10 2021 /etc/cron.monthly
>
> --- /etc/cron.weekly:
> drwxr-xr-x 2 root root 4096 Apr 10 2021 /etc/cron.weekly
>
>
> -- System Information:
> Debian Release: 11.4
> APT prefers stable-security
> APT policy: (500, 'stable-security'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-16-amd64 (SMP w/8 CPU threads)
> Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_CH:de
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages cron depends on:
> ii adduser 3.118
> ii debianutils 4.11.2
> ii init-system-helpers 1.60
> ii libc62.31-13+deb11u3
> ii libpam-runtime 1.4.0-9+deb11u1
> ii libpam0g 1.4.0-9+deb11u1
> ii libselinux1 3.1-3
> ii lsb-base 11.1.0
> ii sensible-utils 0.0.14
>
> Versions of packages cron recommends:
> ii msmtp-mta [mail-transport-agent] 1.8.11-2.1
>
> Versions of packages cron suggests:
> ii anacron2.3-30
> pn checksecurity
> ii logrotate 3.18.0-2+deb11u1
>
> Versions of packages cron is related to:
> pn libnss-ldap
> pn libnss-ldapd
> pn libpam-ldap
> pn libpam-mount
> pn nis
> pn nscd
>
> -- no debconf information
> diff -u -r orig/cron-3.0pl1/cron.c cron-3.0pl1/cron.c
> --- orig/cron-3.0pl1/cron.c 2022-07-19 12:18:36.0 +0200
> +++ cron-3.0pl1/cron.c2022-07-19 14:24:39.0 +0200
> @@ -122,12 +122,12 @@
> } else if (!stay_foreground) {
> switch (fork()) {
> case -1:
> - log_it("CRON",getpid(),"DEATH","can't fork");
> + log_it(LOG_ERR, "CRON",getpid(),"DEATH","can't fork");
> exit(0);
> break;
> case 0:
> /* child process */
> - log_it("CRON",getpid(),"STARTUP","fork ok");
> + log_it(LOG_INFO, "CRON",getpid(),"STARTUP","fork ok");
> (void) setsid();
> freopen("/dev/null", "r", stdin);
> freopen("/dev/null",
Bug#1015935: Acknowledgement of maintainer-only report (vim-addon-mw-utils: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
diffstat for vim-addon-mw-utils-0.2 vim-addon-mw-utils-0.2
control |4 +--
vim-addon-mw-utils.dirs |1
vim-addon-mw-utils.install |5 +---
vim-addon-mw-utils.neovim-addon |1
vim-addon-mw-utils.postinst | 41
vim-addon-mw-utils.preinst | 38 -
vim-addon-mw-utils.prerm| 39 --
vim-addon-mw-utils.vim-addon|1
vim-addon-mw-utils.yaml | 15 --
9 files changed, 6 insertions(+), 139 deletions(-)
diff -Nru vim-addon-mw-utils-0.2/debian/control vim-addon-mw-utils-0.2/debian/control
--- vim-addon-mw-utils-0.2/debian/control 2020-01-13 00:01:36.0 +0300
+++ vim-addon-mw-utils-0.2/debian/control 2020-01-31 01:22:14.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Andrea Capriotti
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), dh-sequence-vim-addon
Standards-Version: 4.4.1
Homepage: https://github.com/MarcWeber/vim-addon-mw-utils
Vcs-Git: https://salsa.debian.org/debian/vim-addon-mw-utils.git
@@ -10,6 +10,6 @@
Package: vim-addon-mw-utils
Architecture: all
-Depends: vim, vim-addon-manager, ${misc:Depends}
+Depends: ${misc:Depends}, ${vim-addon:Depends}
Description: Vim funcref library
A vim library to interpret a file by function and cache file automatically.
diff -Nru vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.dirs vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.dirs
--- vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.dirs 2014-12-20 18:38:56.0 +0300
+++ vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.dirs 1970-01-01 03:00:00.0 +0300
@@ -1 +0,0 @@
-var/lib/vim/addons/autoload/
diff -Nru vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.install vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.install
--- vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.install 2014-06-16 16:59:49.0 +0400
+++ vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.install 2020-01-31 01:22:14.0 +0300
@@ -1,3 +1,2 @@
-doc/ usr/share/vim/addons
-autoload/usr/share/vim/addons
-debian/vim-addon-mw-utils.yaml usr/share/vim/registry
+autoload usr/share/vim-addon-mw-utils
+doc usr/share/vim-addon-mw-utils
diff -Nru vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.neovim-addon vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.neovim-addon
--- vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.neovim-addon 2020-01-31 01:22:14.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-addon-mw-utils
diff -Nru vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.postinst vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.postinst
--- vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.postinst 2014-06-25 12:31:20.0 +0400
+++ vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.postinst 1970-01-01 03:00:00.0 +0300
@@ -1,41 +0,0 @@
-#! /bin/bash
-# postinst script for vim-addon-mw-utils
-#
-# see: dh_installdeb(1)
-
-set -e
-
-
-# summary of how this script can be called:
-# * `configure'
-# * `abort-upgrade'
-# * `abort-remove' `in-favour'
-#
-# * `abort-deconfigure' `in-favour'
-# `removing'
-#
-#
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
-configure)
-vim-addon-manager -w install addon-mw-utils
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.preinst vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.preinst
--- vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.preinst 2014-06-25 12:31:33.0 +0400
+++ vim-addon-mw-utils-0.2/debian/vim-addon-mw-utils.preinst 1970-01-01 03:00:00.0 +0300
@@ -1,38 +0,0 @@
-#!/bin/sh
-# preinst script for vim-addon-mw-utils
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#* `install'
-#* `install'
-#* `upgrade'
-#* `abort-upgrade'
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-install|upgrade)
-if [ "$(vim-addons status | grep addon-mw-utils | awk '{print $3}')" = "installed" ] ; then
-vim-addon-manager -w remove addon-mw-utils
-fi
-;;
-
-abort-upgrade)
-;;
-
-*)
-echo "preinst called with unknown argument \`$1'" >&2
-
Bug#1015947: Acknowledgement of maintainer-only report (vim-snipmate: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
The README.Debian file mentioned vim-addons, and I removed the file. As far as
I can see, vim-snipmate was activated automatically in the postinst script.
diffstat for vim-snipmate-0.87 vim-snipmate-0.87
README.Debian | 19 ---
control |4 ++--
vim-snipmate.install | 13 ++---
vim-snipmate.neovim-addon |1 +
vim-snipmate.postinst | 41 -
vim-snipmate.preinst | 38 --
vim-snipmate.prerm| 39 ---
vim-snipmate.vim-addon|1 +
vim-snipmate.yaml | 15 ---
9 files changed, 10 insertions(+), 161 deletions(-)
diff -Nru vim-snipmate-0.87/debian/control vim-snipmate-0.87/debian/control
--- vim-snipmate-0.87/debian/control 2020-03-18 04:32:11.0 +0300
+++ vim-snipmate-0.87/debian/control 2020-03-18 05:20:04.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Andrea Capriotti
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), dh-sequence-vim-addon
Standards-Version: 4.5.0
Homepage: https://github.com/msanders/snipmate.vim
Vcs-Git: https://salsa.debian.org/debian/vim-snipmate.git
@@ -10,7 +10,7 @@
Package: vim-snipmate
Architecture: all
-Depends: vim, vim-addon-manager, vim-tlib, vim-addon-mw-utils, ${misc:Depends}
+Depends: vim-addon-mw-utils, vim-tlib, ${misc:Depends}, ${vim-addon:Depends}
Suggests: vim-snippets
Description: Vim script that implements some of TextMate's snippets features.
SnipMate.vim aims to be an unobtrusive, concise vim script that implements
diff -Nru vim-snipmate-0.87/debian/README.Debian vim-snipmate-0.87/debian/README.Debian
--- vim-snipmate-0.87/debian/README.Debian 2020-03-18 04:30:27.0 +0300
+++ vim-snipmate-0.87/debian/README.Debian 1970-01-01 03:00:00.0 +0300
@@ -1,19 +0,0 @@
-vim-snipmate for Debian
-Enabling the addons
-===
-
-This package provides a "snipmate" addon for the vim text editor.
-It is not enabled by default. To enable it for you only, run:
-
-$ vim-addons install snipmate
-
-Similarly, to enable it for all users of this system just
-execute (as root):
-
-# vim-addons -w install snipmate
-
-vim-addons is provided by the vim-addon-manager package, have a look at its
-manpage for more information.
-
- -- Andrea Capriotti Mon, 27 Jan 2014 17:33:04 +0100
diff -Nru vim-snipmate-0.87/debian/vim-snipmate.install vim-snipmate-0.87/debian/vim-snipmate.install
--- vim-snipmate-0.87/debian/vim-snipmate.install 2020-03-18 04:30:27.0 +0300
+++ vim-snipmate-0.87/debian/vim-snipmate.install 2020-03-18 05:20:04.0 +0300
@@ -1,7 +1,6 @@
-after/usr/share/vim/addons
-doc/ usr/share/vim/addons
-ftplugin/ usr/share/vim/addons
-plugin/ usr/share/vim/addons
-autoload/ usr/share/vim/addons
-syntax/ usr/share/vim/addons
-debian/vim-snipmate.yaml usr/share/vim/registry
+afterusr/share/vim-snipmate
+autoload usr/share/vim-snipmate
+doc usr/share/vim-snipmate
+ftplugin usr/share/vim-snipmate
+plugin usr/share/vim-snipmate
+syntax usr/share/vim-snipmate
diff -Nru vim-snipmate-0.87/debian/vim-snipmate.neovim-addon vim-snipmate-0.87/debian/vim-snipmate.neovim-addon
--- vim-snipmate-0.87/debian/vim-snipmate.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-snipmate-0.87/debian/vim-snipmate.neovim-addon 2020-03-18 05:20:04.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-snipmate snipmate
diff -Nru vim-snipmate-0.87/debian/vim-snipmate.postinst vim-snipmate-0.87/debian/vim-snipmate.postinst
--- vim-snipmate-0.87/debian/vim-snipmate.postinst 2020-03-18 04:30:27.0 +0300
+++ vim-snipmate-0.87/debian/vim-snipmate.postinst 1970-01-01 03:00:00.0 +0300
@@ -1,41 +0,0 @@
-#! /bin/bash
-# postinst script for vim-snipmate
-#
-# see: dh_installdeb(1)
-
-set -e
-
-
-# summary of how this script can be called:
-# * `configure'
-# * `abort-upgrade'
-# * `abort-remove' `in-favour'
-#
-# * `abort-deconfigure' `in-favour'
-# `removing'
-#
-#
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
-configure)
-vim-addon-manager -w install snipmate
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-snipmate-0.87/debian/vim-snipmate.preinst vim-snipmate-0.87/debian/vim-snipmate.preinst
---
Bug#1015948: Acknowledgement of maintainer-only report (vim-snippets: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
diffstat for vim-snippets-1.0.0 vim-snippets-1.0.0
control |4 -
vim-snippets.install | 11 +--
vim-snippets.neovim-addon |1
vim-snippets.postinst | 41 -
vim-snippets.preinst | 38
vim-snippets.prerm| 39
vim-snippets.vim-addon|1
vim-snippets.yaml | 139 --
8 files changed, 9 insertions(+), 265 deletions(-)
diff -Nru vim-snippets-1.0.0/debian/control vim-snippets-1.0.0/debian/control
--- vim-snippets-1.0.0/debian/control 2020-03-18 04:39:51.0 +0300
+++ vim-snippets-1.0.0/debian/control 2020-03-18 05:15:17.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Andrea Capriotti
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), dh-sequence-vim-addon
Standards-Version: 4.5.0
Homepage: https://github.com/honza/vim-snippets
Vcs-Git: https://salsa.debian.org/debian/vim-snippets.git
@@ -10,7 +10,7 @@
Package: vim-snippets
Architecture: all
-Depends: vim, vim-addon-manager, ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends}, ${vim-addon:Depends}
Breaks: vim-snipmate (<< 0.87)
Description: Snippets files for various programming languages.
This repository contains many different snippets files for various programming
diff -Nru vim-snippets-1.0.0/debian/vim-snippets.install vim-snippets-1.0.0/debian/vim-snippets.install
--- vim-snippets-1.0.0/debian/vim-snippets.install 2020-03-18 04:38:31.0 +0300
+++ vim-snippets-1.0.0/debian/vim-snippets.install 2020-03-18 05:15:17.0 +0300
@@ -1,6 +1,5 @@
-autoload/ usr/share/vim/addons
-plugin/ usr/share/vim/addons
-pythonx/ usr/share/vim/addons
-snippets/ usr/share/vim/addons
-UltiSnips/usr/share/vim/addons
-debian/vim-snippets.yaml usr/share/vim/registry
+autoload usr/share/vim-snippets
+pluginusr/share/vim-snippets
+pythonx usr/share/vim-snippets
+snippets usr/share/vim-snippets
+UltiSnips usr/share/vim-snippets
diff -Nru vim-snippets-1.0.0/debian/vim-snippets.neovim-addon vim-snippets-1.0.0/debian/vim-snippets.neovim-addon
--- vim-snippets-1.0.0/debian/vim-snippets.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-snippets-1.0.0/debian/vim-snippets.neovim-addon 2020-03-18 05:15:17.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-snippets snippets
diff -Nru vim-snippets-1.0.0/debian/vim-snippets.postinst vim-snippets-1.0.0/debian/vim-snippets.postinst
--- vim-snippets-1.0.0/debian/vim-snippets.postinst 2020-03-18 04:38:31.0 +0300
+++ vim-snippets-1.0.0/debian/vim-snippets.postinst 1970-01-01 03:00:00.0 +0300
@@ -1,41 +0,0 @@
-#! /bin/bash
-# postinst script for vim-snippets
-#
-# see: dh_installdeb(1)
-
-set -e
-
-
-# summary of how this script can be called:
-# * `configure'
-# * `abort-upgrade'
-# * `abort-remove' `in-favour'
-#
-# * `abort-deconfigure' `in-favour'
-# `removing'
-#
-#
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
-configure)
-vim-addon-manager -w install snippets
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-snippets-1.0.0/debian/vim-snippets.preinst vim-snippets-1.0.0/debian/vim-snippets.preinst
--- vim-snippets-1.0.0/debian/vim-snippets.preinst 2020-03-18 04:38:31.0 +0300
+++ vim-snippets-1.0.0/debian/vim-snippets.preinst 1970-01-01 03:00:00.0 +0300
@@ -1,38 +0,0 @@
-#!/bin/sh
-# preinst script for vim-snippets
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#* `install'
-#* `install'
-#* `upgrade'
-#* `abort-upgrade'
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-install|upgrade)
-if [ "$(vim-addons status | grep snippets | awk '{print $3}')" = "installed" ] ; then
-vim-addon-manager -w remove snippets
-fi
-;;
-
-abort-upgrade)
-;;
-
-*)
-echo "preinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-snippets-1.0.0/debian/vim-snippets.prerm vim-snippets-1.0.0/debian/vim-snippets.prerm
--- vim-snippets-1.0.0/debian/vim-snippets.prerm 2020-03-18 04:38:31.0 +0300
+++ vim-snippets-1.0.0/debian/vim-snippets.prerm
Bug#1015952: Acknowledgement of maintainer-only report (vim-tlib: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
diffstat for vim-tlib-1.27 vim-tlib-1.27
control |4 +-
rules |2 -
vim-tlib.dirs |2 -
vim-tlib.install | 19 +--
vim-tlib.neovim-addon |1
vim-tlib.postinst | 41 -
vim-tlib.prerm| 39 ---
vim-tlib.vim-addon|1
vim-tlib.yaml | 82 --
9 files changed, 14 insertions(+), 177 deletions(-)
diff -Nru vim-tlib-1.27/debian/control vim-tlib-1.27/debian/control
--- vim-tlib-1.27/debian/control 2020-01-31 02:08:01.0 +0300
+++ vim-tlib-1.27/debian/control 2020-06-25 14:56:10.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Andrea Capriotti
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), dh-sequence-vim-addon
Standards-Version: 4.5.0
Homepage: http://www.vim.org/scripts/script.php?script_id=1863
Vcs-Git: https://salsa.debian.org/debian/vim-tlib.git
@@ -10,7 +10,7 @@
Package: vim-tlib
Architecture: all
-Depends: vim, vim-addon-manager, ${misc:Depends}
+Depends: ${misc:Depends}, ${vim-addon:Depends}
Description: Some vim utility functions
This library provides some utility functions. There isn't much need to
install it unless another plugin requires you to do so.
diff -Nru vim-tlib-1.27/debian/rules vim-tlib-1.27/debian/rules
--- vim-tlib-1.27/debian/rules 2020-01-12 23:13:29.0 +0300
+++ vim-tlib-1.27/debian/rules 2020-06-25 14:56:10.0 +0300
@@ -8,4 +8,4 @@
dh $@
override_dh_fixperms:
dh_fixperms
- find debian/vim-tlib/usr/share/vim/addons/ -type f -exec chmod 644 {} \;
+ find debian/vim-tlib/usr/share/vim-tlib -type f -exec chmod 644 {} +
diff -Nru vim-tlib-1.27/debian/vim-tlib.dirs vim-tlib-1.27/debian/vim-tlib.dirs
--- vim-tlib-1.27/debian/vim-tlib.dirs 2020-01-12 23:13:29.0 +0300
+++ vim-tlib-1.27/debian/vim-tlib.dirs 1970-01-01 03:00:00.0 +0300
@@ -1,2 +0,0 @@
-var/lib/vim/addons/samples/
-var/lib/vim/addons/macro/
diff -Nru vim-tlib-1.27/debian/vim-tlib.install vim-tlib-1.27/debian/vim-tlib.install
--- vim-tlib-1.27/debian/vim-tlib.install 2020-06-25 14:56:03.0 +0300
+++ vim-tlib-1.27/debian/vim-tlib.install 2020-06-25 14:56:10.0 +0300
@@ -1,10 +1,9 @@
-doc/tlib.txt usr/share/vim/addons/doc
-etc/ usr/share/vim/addons
-macros/ usr/share/vim/addons
-plugin/ usr/share/vim/addons
-test/ usr/share/vim/addons
-spec/ usr/share/vim/addons
-samples/ usr/share/vim/addons
-scripts/ usr/share/vim/addons
-autoload/ usr/share/vim/addons
-debian/vim-tlib.yaml usr/share/vim/registry
+autoload usr/share/vim-tlib
+doc usr/share/vim-tlib
+etc usr/share/vim-tlib
+macros usr/share/vim-tlib
+plugin usr/share/vim-tlib
+samples usr/share/vim-tlib
+scripts usr/share/vim-tlib
+spec usr/share/vim-tlib
+test usr/share/vim-tlib
diff -Nru vim-tlib-1.27/debian/vim-tlib.neovim-addon vim-tlib-1.27/debian/vim-tlib.neovim-addon
--- vim-tlib-1.27/debian/vim-tlib.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-tlib-1.27/debian/vim-tlib.neovim-addon 2020-06-25 14:56:10.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-tlib tlib
diff -Nru vim-tlib-1.27/debian/vim-tlib.postinst vim-tlib-1.27/debian/vim-tlib.postinst
--- vim-tlib-1.27/debian/vim-tlib.postinst 2020-01-12 23:13:29.0 +0300
+++ vim-tlib-1.27/debian/vim-tlib.postinst 1970-01-01 03:00:00.0 +0300
@@ -1,41 +0,0 @@
-#! /bin/bash
-# postinst script for vim-tlib
-#
-# see: dh_installdeb(1)
-
-set -e
-
-
-# summary of how this script can be called:
-# * `configure'
-# * `abort-upgrade'
-# * `abort-remove' `in-favour'
-#
-# * `abort-deconfigure' `in-favour'
-# `removing'
-#
-#
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
-configure)
-vim-addon-manager -w install tlib
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-tlib-1.27/debian/vim-tlib.prerm vim-tlib-1.27/debian/vim-tlib.prerm
--- vim-tlib-1.27/debian/vim-tlib.prerm 2020-01-12 23:13:29.0 +0300
+++ vim-tlib-1.27/debian/vim-tlib.prerm 1970-01-01 03:00:00.0 +0300
@@ -1,39 +0,0 @@
-#!/bin/sh
-# prerm script for vim-tlib
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#* `remove'
-#* `upgrade'
-#* `failed-upgrade'
-#*
Bug#1015950: Acknowledgement of maintainer-only report (vim-tabular: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1))
Control: tag -1 patch
Hi! I have a debdiff fixing this.
The README.Debian file mentioned vim-addons, and I removed the file. As far as
I can see, vim-tabular was activated automatically in the postinst script.
diffstat for vim-tabular-1.0 vim-tabular-1.0
README.Debian| 19 ---
control |4 ++--
vim-tabular.install |9 -
vim-tabular.neovim-addon |1 +
vim-tabular.postinst | 41 -
vim-tabular.preinst | 38 --
vim-tabular.prerm| 39 ---
vim-tabular.vim-addon|1 +
vim-tabular.yaml |8
9 files changed, 8 insertions(+), 152 deletions(-)
diff -Nru vim-tabular-1.0/debian/control vim-tabular-1.0/debian/control
--- vim-tabular-1.0/debian/control 2020-03-18 04:53:16.0 +0300
+++ vim-tabular-1.0/debian/control 2020-03-18 05:09:15.0 +0300
@@ -2,7 +2,7 @@
Section: editors
Priority: optional
Maintainer: Andrea Capriotti
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 12), dh-sequence-vim-addon
Standards-Version: 4.5.0
Homepage: https://github.com/godlygeek/tabular
Vcs-Git: https://salsa.debian.org/debian/vim-tabular.git
@@ -10,7 +10,7 @@
Package: vim-tabular
Architecture: all
-Depends: vim, vim-addon-manager, ${misc:Depends}
+Depends: ${misc:Depends}, ${vim-addon:Depends}
Description: Vim script for text filtering and alignment
Sometimes, it's useful to line up text. Naturally, it's nicer to have the
computer do this for you, since aligning things by hand quickly becomes
diff -Nru vim-tabular-1.0/debian/README.Debian vim-tabular-1.0/debian/README.Debian
--- vim-tabular-1.0/debian/README.Debian 2020-03-18 04:52:22.0 +0300
+++ vim-tabular-1.0/debian/README.Debian 1970-01-01 03:00:00.0 +0300
@@ -1,19 +0,0 @@
-vim-tabular for Debian
---
-Enabling the addons
-===
-
-This package provides a "tabular" addon for the vim text editor.
-It is not enabled by default. To enable it for you only, run:
-
-$ vim-addons install tabular
-
-Similarly, to enable it for all users of this system just
-execute (as root):
-
-# vim-addons -w install tabular
-
-vim-addons is provided by the vim-addon-manager package, have a look at its
-manpage for more information.
-
- -- Andrea Capriotti Mon, 27 Jan 2014 15:56:06 +0100
diff -Nru vim-tabular-1.0/debian/vim-tabular.install vim-tabular-1.0/debian/vim-tabular.install
--- vim-tabular-1.0/debian/vim-tabular.install 2020-03-18 04:52:22.0 +0300
+++ vim-tabular-1.0/debian/vim-tabular.install 2020-03-18 05:09:15.0 +0300
@@ -1,5 +1,4 @@
-doc/ usr/share/vim/addons
-plugin/ usr/share/vim/addons
-autoload/ usr/share/vim/addons
-after/usr/share/vim/addons
-debian/vim-tabular.yaml usr/share/vim/registry
+afterusr/share/vim-tabular
+autoload usr/share/vim-tabular
+doc usr/share/vim-tabular
+plugin usr/share/vim-tabular
diff -Nru vim-tabular-1.0/debian/vim-tabular.neovim-addon vim-tabular-1.0/debian/vim-tabular.neovim-addon
--- vim-tabular-1.0/debian/vim-tabular.neovim-addon 1970-01-01 03:00:00.0 +0300
+++ vim-tabular-1.0/debian/vim-tabular.neovim-addon 2020-03-18 05:09:15.0 +0300
@@ -0,0 +1 @@
+usr/share/vim-tabular tabular
diff -Nru vim-tabular-1.0/debian/vim-tabular.postinst vim-tabular-1.0/debian/vim-tabular.postinst
--- vim-tabular-1.0/debian/vim-tabular.postinst 2020-03-18 04:52:22.0 +0300
+++ vim-tabular-1.0/debian/vim-tabular.postinst 1970-01-01 03:00:00.0 +0300
@@ -1,41 +0,0 @@
-#! /bin/bash
-# postinst script for vim-tabular
-#
-# see: dh_installdeb(1)
-
-set -e
-
-
-# summary of how this script can be called:
-# * `configure'
-# * `abort-upgrade'
-# * `abort-remove' `in-favour'
-#
-# * `abort-deconfigure' `in-favour'
-# `removing'
-#
-#
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
-configure)
-vim-addon-manager -w install tabular
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru vim-tabular-1.0/debian/vim-tabular.preinst vim-tabular-1.0/debian/vim-tabular.preinst
--- vim-tabular-1.0/debian/vim-tabular.preinst 2020-03-18 04:52:22.0 +0300
+++ vim-tabular-1.0/debian/vim-tabular.preinst 1970-01-01 03:00:00.0 +0300
@@ -1,38 +0,0 @@
-#!/bin/sh
-# preinst script for vim-tabular
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#* `install'
-#*
Bug#1015954: unmkinitramfs and lsinitramfs don't dereference symlinks consistently
Package: initramfs-tools-core Version: 0.142 Severity: normal Tags: patch File: /usr/bin/unmkinitramfs Dear Maintainer, With the default COMPRESS=zstd lsmkinitramfs fails on unsplit /initrd.img: $ lsmkinitramfs /initrd.img cpio: premature end of archive $ unmkinitramfs /initrd.img /tmp/initramfs cpio: premature end of archive This is because zstd(1) refuses to operate on symlinks without `-f`: $ zstd -t /initrd.img Warning : /initrd.img is a symbolic link, ignoring (This is with an unsplit initramfs, so xcpio() processes the input file directly.) That behavior seems to be specific to zstd(1), at least unmkinitramfs(8) does seem work with COMPRESS=gzip, bzip2, lz4, lzma, lzop, xz. All these utilities do process standard input though, so a simple fix (attached) is to merely redirect it. Thanks for maintaining initramfs-tools! -- Guilhem. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools-core depends on: ii coreutils8.32-4.1 ii cpio 2.13+dfsg-7 ii e2fsprogs1.46.5-2 ii klibc-utils 2.0.10-4 ii kmod 30+20220630-2 ii logsave 1.46.5-2 ii udev 251.3-1 Versions of packages initramfs-tools-core recommends: ii busybox 1:1.35.0-1 ii zstd 1.5.2+dfsg-1 Versions of packages initramfs-tools-core suggests: ii bash-completion 1:2.11-6 -- Configuration Files: /etc/initramfs-tools/initramfs.conf changed [not included] -- no debconf information --- a/unmkinitramfs +++ b/unmkinitramfs @@ -29,18 +29,18 @@ dir="$2" shift 2 - if gzip -t "$archive" >/dev/null 2>&1 ; then - gzip -c -d "$archive" - elif zstd -q -c -t "$archive" >/dev/null 2>&1 ; then - zstd -q -c -d "$archive" - elif xzcat -t "$archive" >/dev/null 2>&1 ; then - xzcat "$archive" + if gzip -t < "$archive" >/dev/null 2>&1 ; then + gzip -c -d < "$archive" + elif zstd -q -c -t < "$archive" >/dev/null 2>&1 ; then + zstd -q -c -d < "$archive" + elif xzcat -t < "$archive" >/dev/null 2>&1 ; then + xzcat < "$archive" elif lz4cat -t < "$archive" >/dev/null 2>&1 ; then - lz4cat "$archive" - elif bzip2 -t "$archive" >/dev/null 2>&1 ; then - bzip2 -c -d "$archive" - elif lzop -t "$archive" >/dev/null 2>&1 ; then - lzop -c -d "$archive" + lz4cat < "$archive" + elif bzip2 -t < "$archive" >/dev/null 2>&1 ; then + bzip2 -c -d < "$archive" + elif lzop -t < "$archive" >/dev/null 2>&1 ; then + lzop -c -d < "$archive" # Ignoring other data, which may be garbage at the end of the file fi | ( if [ -n "$dir" ]; then signature.asc Description: PGP signature
Bug#1011138: Workaround for bug #1011138
On 2022-05-20 19:16:06 [+0200], Bernhard Schmidt wrote: > On 19/05/22 01:35 PM, Hopea Jonne wrote: > > > Uninstalling libssl-dev helped, for some reason libssl-dev also ships with > > a > > libssl.so binary which may or may not be of same version as other ones. > > I don't think this is the reason, libssl-dev does not ship the .so > binary, instead it ships a symlink to the libraries provided by libssl3 > > $ dpkg-deb -c libssl-dev_3.0.3-4_amd64.deb | grep .so > lrwxrwxrwx root/root 0 2022-05-16 23:20 > ./usr/lib/x86_64-linux-gnu/libcrypto.so -> libcrypto.so.3 > lrwxrwxrwx root/root 0 2022-05-16 23:20 > ./usr/lib/x86_64-linux-gnu/libssl.so -> libssl.so.3 > > However, your bugreport might still point to another problem in > libssl-dev, thus reassigning. > > Is it possible that you have a partially upgraded system (libssl-dev > from OpenSSL 1.1, but kmail linked to OpenSSL 3.0)? Now that I am back, what is the status here? Did this resolve by itself as part of the transition or is still relevant? > Bernhard Sebastian
Bug#1015889: [Pkg-utopia-maintainers] Bug#1015889: high CPU load for avahi-daemon on Bullseye
Am 24.07.22 um 06:15 schrieb Harald Dunkel: 0.8-6 builds fine on Bullse More importantly: Does it fix the high CPU load in your case? OpenPGP_signature Description: OpenPGP digital signature
Bug#1015955: liblemon-dev: pkg-config --libs response is wrong
Package: liblemon-dev Version: 1.3.1+dfsg-4 Severity: normal X-Debbugs-Cc: yorg...@gmail.com Dear Maintainer, Trying to use pkg-config with the Lemon library for a project of mine, I noticed that the response using the --libs option is "-lemon", which leads to build failure (of my project). I think the response should be "-llemon" instead (i.e. an "l" character is missing). I browsed the dfsg-5 version and found that the problem most likely still exists in the "lemon/lemon.pc.in" source file. I do not consider it a major problem, since one can always apply a fix in their build procedure, but I thought you might want to make a correction for a future version. Thank you for your maintenance efforts! yorgath -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages liblemon-dev depends on: ii liblemon1.3.1 1.3.1+dfsg-4 liblemon-dev recommends no packages. liblemon-dev suggests no packages. -- no debconf information
Bug#1015886: [Pkg-utopia-maintainers] Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
Control: reopen -1 Control: severity -1 important Control: clone -1 -2 Control: reassign -2 kodi Control: retitle -2 please ship firewalld service files Control: block -1 by -2 Am 24.07.22 um 08:12 schrieb Christian Marillat: > But why firewalld install services for packages not installed ? > > firewalld services must be managed as systemd does. firewalld uses a hybrid approach. As you can see, it provides a lot of service definitions in /usr/lib/firewalld/services out of the box. But individual packages can those ship service definitions as well. I think firewalld upstream actually prefers if those service definitions are shipped by the respective packages themselves. Am 24.07.22 um 08:57 schrieb Christian Marillat: On 24 juil. 2022 09:39, Andy wrote: I have come across a bug in the deb-multimedia package kodi-data. The debian maintainer of firewalld recommended to file a bug with debian- multimedia. firewalld will remove these files. https://github.com/firewalld/firewalld/pull/552 The official debian kodi package does not ship those files. Looking closer, I found https://salsa.debian.org/multimedia-team/kodi-media-center/kodi/-/blob/master/debian/not-installed#L1 debian/not-installed:# firewalld is present only on RHEL / CentOS debian/not-installed:usr/lib/firewalld/services/kodi-jsonrpc.xml debian/not-installed:usr/lib/firewalld/services/kodi-http.xml debian/not-installed:usr/lib/firewalld/services/kodi-eventserver.xml This is apparently an outdated remark. I can remove the kodi service files from firewalld and upload as 1.2.0-2 but I'd like the Debian kodi package to take over and ship those files first before. Dear kodi maintainers: Please ship the above firewalld service files in either kodi or kodi-data and add a versioned Breaks: firewalld (<< 1.2.0-2) Replaces: firewalld (<< 1.2.0-2) Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
On Sun, 24 Jul 2022 14:22:24 +0200 Michael Biebl wrote: [...] > But individual packages can those ship service definitions as well. I > think firewalld upstream actually prefers if those service definitions > are shipped by the respective packages themselves. Nice to know. :) [...] > I can remove the kodi service files from firewalld and upload as 1.2.0-2 > but I'd like the Debian kodi package to take over and ship those files > first before. For the record : Kodi FTBFS with ffmpeg 5 and has been removed from testing. Kodi upstream will never fix this issue and I think Debian too. Christian
Bug#1015973: Should xdeb be removed?
Source: xdeb Version: 0.6.7 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - No upload since five years If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015974: Should gnat-gps be removed?
Source: gnat-gps Version: 19.2-3 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1013924: coreutils: runcon -c getfscon()s program verbatim but execve()s it; trojan moment?
On 27/06/2022 19:13, Pádraig Brady wrote:
On 27/06/2022 16:04, наб wrote:
Package: coreutils
Version: 8.32-4+b1
Severity: normal
Dear Maintainer,
The strace for runcon -c true true (after a > true) contains
getxattr("true", "security.selinux", "unconfined_u:object_r:user_tmp_t",
255) = 36
execve("/usr/local/sbin/true", ["true", "true"]) = -1 ENOENT
execve("/usr/local/bin/true", ["true", "true"]) = -1 ENOENT
execve("/sbin/true", ["true", "true"]) = -1 ENOENT
execve("/bin/true", ["true", "true"]) = 0
This corresponds to getfscon("true"), execvp("true", ["true", NULL]).
(of course, this also errors if ./true doesn't exist).
So, uh: is this intentional? It certainly feels wrong? All invocations
take a PATH executable except this one which takes a PATH executable
that must *also* be a valid file? And also invites a trivial trojan
because the precomputed transition is to the file in the cwd, but the
program executed lives somewhere in PATH? Should -c just execv()
instead? Am I misunderstanding the usefulness of this?
Best,
наб
This is a fair point.
I.e. the following patch would be more correct operation.
I'll propose this upstream.
Now existing scripts would need to pass absolute paths to `runcon -c`
to work in the first place, so I don't know how much of a security
issue this is in practice.
thanks,
Pádraig
iff --git a/src/runcon.c b/src/runcon.c
index c4227c784..d85411c79 100644
--- a/src/runcon.c
+++ b/src/runcon.c
@@ -255,7 +255,7 @@ main (int argc, char **argv)
if (cur_context != NULL)
freecon (cur_context);
- execvp (argv[optind], argv + optind);
+ (compute_trans ? execv : execvp) (argv[optind], argv + optind);
int exit_status = errno == ENOENT ? EXIT_ENOENT : EXIT_CANNOT_INVOKE;
error (0, errno, "%s", quote (argv[optind]));
Pushed the attached upstream.
thanks,
Pádraig
From 96c149941357186abcbd8da914544a7867cab01e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?P=C3=A1draig=20Brady?=
Date: Sun, 24 Jul 2022 18:46:10 +0100
Subject: [PATCH] runcon: ensure --compute runs the file it inspects
* src/runcon.c (main): With -c avoid searching the path
to ensure the file specified to --compute is executed.
* tests/misc/runcon-compute.sh: Add a new test.
* tests/local.mk: Reference the new test.
* NEWS: Mention the bug fix.
Reported in https://bugs.debian.org/1013924
---
NEWS | 4
src/runcon.c | 2 +-
tests/local.mk | 1 +
tests/misc/runcon-compute.sh | 28
4 files changed, 34 insertions(+), 1 deletion(-)
create mode 100755 tests/misc/runcon-compute.sh
diff --git a/NEWS b/NEWS
index 816025255..b5b8990f8 100644
--- a/NEWS
+++ b/NEWS
@@ -10,6 +10,10 @@ GNU coreutils NEWS-*- outline -*-
'mv --backup=simple f d/' no longer mistakenly backs up d/f to f~.
[bug introduced in coreutils-9.1]
+ runcon --compute no longer looks up the specified command in the $PATH
+ so that there is no mismatch between the inspected and executed file.
+ [bug introduced when runcon was introduced in coreutils-6.9.90]
+
'sort -g' no longer infloops when given multiple NaNs on platforms
like x86_64 where 'long double' has padding bits in memory.
Although the fix alters sort -g's NaN ordering, that ordering has
diff --git a/src/runcon.c b/src/runcon.c
index c4227c784..d85411c79 100644
--- a/src/runcon.c
+++ b/src/runcon.c
@@ -255,7 +255,7 @@ main (int argc, char **argv)
if (cur_context != NULL)
freecon (cur_context);
- execvp (argv[optind], argv + optind);
+ (compute_trans ? execv : execvp) (argv[optind], argv + optind);
int exit_status = errno == ENOENT ? EXIT_ENOENT : EXIT_CANNOT_INVOKE;
error (0, errno, "%s", quote (argv[optind]));
diff --git a/tests/local.mk b/tests/local.mk
index 0f7778619..0496c2873 100644
--- a/tests/local.mk
+++ b/tests/local.mk
@@ -351,6 +351,7 @@ all_tests = \
tests/misc/readlink-fp-loop.sh \
tests/misc/readlink-root.sh \
tests/misc/realpath.sh \
+ tests/misc/runcon-compute.sh \
tests/misc/runcon-no-reorder.sh \
tests/misc/sha1sum.pl\
tests/misc/sha1sum-vec.pl \
diff --git a/tests/misc/runcon-compute.sh b/tests/misc/runcon-compute.sh
new file mode 100755
index 0..1c4e0c060
--- /dev/null
+++ b/tests/misc/runcon-compute.sh
@@ -0,0 +1,28 @@
+#!/bin/sh
+# Ensure that runcon -c uses absolute file names
+
+# Copyright (C) 2022 Free Software Foundation, Inc.
+
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+
+#
Bug#1015977: Should vland be removed?
Source: vland Version: 0.8-1 Severity: serious Your package came up as a candidate for removal from Debian, it's one of the few remaining packages still depending on Python 2 and there're no visible upstream activity to port it to vland? If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015978: Should falcon be removed?
Source: falcon Version: 1.8.8-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Dropped from testing in 2018 - Last upload in 2017 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015980: Should pd-aubio be removed?
Source: pd-aubio Version: 0.4-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2014 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015981: Should grokmirror be removed?
Source: grokmirror Version: 1.0.0-1.1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last maintainer upload in 2016 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1009281: [Debichem-devel] Bug#1009281: Bug#1009281: Should cinfony be removed?
Am Mon, Apr 11, 2022 at 09:21:25AM +0200 schrieb Michael Banck: > Hi, > > On Mon, Apr 11, 2022 at 08:38:21AM +0300, Andrius Merkys wrote: > > Hi, > > > > On 2022-04-11 01:35, Moritz Muehlenhoff wrote: > > > Source: cinfony > > > Version: 1.2-4 > > > Severity: serious > > > > > > Your package came up as a candidate for removal from Debian: > > > > > > - Still depends on Python 2 and thus removed from testing since 2019 > > > - Dead upstream > > > - No reverse dependencies > > > > Incidentally, I was the last to upload this package. Since 2019 there > > were no uploads, due to aforementioned reasons. I have contemplated > > filing for RM ever since, but did not get to it. I think it is fine to > > remove. If Python 3 port ever happens, we can reintroduce the package then. > > I contacted the author and asked him about it - it seems the master > branch on Github has python3 support, but I didn't look very closely. Did you get any reply? Otherwise let's go ahead with the removal. Cheers, Moritz
Bug#1015984: vim: CVE-2022-1942 CVE-2022-1968 CVE-2022-2000 CVE-2022-2124 CVE-2022-2125 CVE-2022-2126 CVE-2022-2129 CVE-2022-2285 CVE-2022-2288 CVE-2022-2304 CVE-2022-2207 CVE-2022-1616 CVE-2022-1619
Source: vim X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for vim. CVE-2022-1942[0]: | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/67ca4d3b-9175-43c1-925c-72a7091bc071 https://github.com/vim/vim/commit/71223e2db87c2bf3b09aecb46266b56cda26191d (v8.2.5043) CVE-2022-1968[1]: | Use After Free in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/949090e5-f4ea-4edf-bd79-cd98f0498a5b https://github.com/vim/vim/commit/409510c588b1eec1ae33511ae97a21eb8e110895 (v8.2.5050) CVE-2022-2000[2]: | Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/f61a64e2-d163-461b-a77e-46ab38e021f0 https://github.com/vim/vim/commit/44a3f3353e0407e9fffee138125a6927d1c9e7e5 (v8.2.5063) CVE-2022-2124[3]: | Buffer Over-read in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/8e9e056d-f733-4540-98b6-414bf36e0b42 https://github.com/vim/vim/commit/2f074f4685897ab7212e25931eeeb0212292829f (v8.2.5120) CVE-2022-2125[4]: | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/17dab24d-beec-464d-9a72-5b6b11283705 https://github.com/vim/vim/commit/0e8e938d497260dd57be67b4966cb27a5f72376f (v8.2.5122) CVE-2022-2126[5]: | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/8d196d9b-3d10-41d2-9f70-8ef0d08c946e https://github.com/vim/vim/commit/156d3911952d73b03d7420dc3540215247db0fe8 (v8.2.5123) CVE-2022-2129[6]: | Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/3aaf06e7-9ae1-454d-b8ca-8709c98e5352 https://github.com/vim/vim/commit/d6211a52ab9f53b82f884561ed43d2fe4d24ff7d (v8.2.5126) CVE-2022-2285[7]: | Integer Overflow or Wraparound in GitHub repository vim/vim prior to | 9.0. https://huntr.dev/bounties/64574b28-1779-458d-a221-06c434042736/ https://github.com/vim/vim/commit/27efc62f5d86afcb2ecb7565587fe8dea4b036fe (v9.0.0018) CVE-2022-2288[8]: | Out-of-bounds Write in GitHub repository vim/vim prior to 9.0. https://huntr.dev/bounties/a71bdcb7-4e9b-4650-ab6a-fe8e3e9852ad/ https://github.com/vim/vim/commit/c6fdb15d423df22e1776844811d082322475e48a (v9.0.0025) CVE-2022-2304[9]: | Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0. https://huntr.dev/bounties/eb7402f3-025a-402f-97a7-c38700d9548a/ https://github.com/vim/vim/commit/54e5fed6d27b747ff152cdb6edfb72ff60e70939 (v9.0.0035) CVE-2022-2207[10]: | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/05bc6051-4dc3-483b-ae56-cf23346b97b9 https://github.com/vim/vim/commit/0971c7a4e537ea120a6bb2195960be8d0815e97b (v8.2.5162) CVE-2022-1616[11]: | Use after free in append_command in GitHub repository vim/vim prior to | 8.2.4895. This vulnerability is capable of crashing software, Bypass | Protection Mechanism, Modify Memory, and possible remote execution https://huntr.dev/bounties/40f1d75f-fb2f-4281-b585-a41017f217e2 https://github.com/vim/vim/commit/d88934406c5375d88f8f1b65331c9f0cab68cc6c (v8.2.4895) CVE-2022-1619[12]: | Heap-based Buffer Overflow in function cmdline_erase_chars in GitHub | repository vim/vim prior to 8.2.4899. This vulnerabilities are capable | of crashing software, modify memory, and possible remote execution https://huntr.dev/bounties/b3200483-624e-4c76-a070-e246f62a7450 https://github.com/vim/vim/commit/ef02f16609ff0a26ffc6e20263523424980898fe (v8.2.4899) CVE-2022-1621[13]: | Heap buffer overflow in vim_strncpy find_word in GitHub repository | vim/vim prior to 8.2.4919. This vulnerability is capable of crashing | software, Bypass Protection Mechanism, Modify Memory, and possible | remote execution https://huntr.dev/bounties/520ce714-bfd2-4646-9458-f52cd22bb2fb https://github.com/vim/vim/commit/7c824682d2028432ee082703ef0ab399867a089b (v8.2.4919) CVE-2022-1720[14]: | Buffer Over-read in function grab_file_name in GitHub repository | vim/vim prior to 8.2.4956. This vulnerability is capable of crashing | the software, memory modification, and possible remote execution. https://huntr.dev/bounties/5ccfb386-7eb9-46e5-98e5-243ea4b358a8 https://github.com/vim/vim/commit/395bd1f6d3edc9f7edb5d1f2d7deaf5a9e3ab93c (v8.2.4956) CVE-2022-1785[15]: | Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.4977. https://huntr.dev/bounties/8c969cba-eef2-4943-b44a-4e3089599109 https://github.com/vim/vim/commit/e2bd8600b873d2cd1f9d667c28cba8b1dba18839 (v8.2.4977) CVE-2022-1851[16]: | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/f8af901a-9a46-440d-942a-8f815b59394d https://github.com/vim/vim/commit/78d52883e10d71f23ab72a3d8b9733b00da8c9ad (v8.2.5013) CVE-2022-1897[17]: | Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. https://huntr.dev/bounties/82c12151-c283-40cf-aa05-2e39efa89118
Bug#1015985: perl: CVE-2020-16156
Source: perl X-Debbugs-CC: t...@security.debian.org Severity: normal Tags: security Hi, The following vulnerability was published for perl. CVE-2020-16156[0]: | CPAN 2.28 allows Signature Verification Bypass. https://blog.hackeriet.no/cpan-signature-verification-vulnerabilities/ http://blogs.perl.org/users/neilb/2021/11/addressing-cpan-vulnerabilities-related-to-checksums.html https://bugzilla.redhat.com/show_bug.cgi?id=2035273 Patches: https://github.com/andk/cpanpm/commit/b27c51adf0fda25dee84cb72cb2b1bf7d832148c (2.29) https://github.com/andk/cpanpm/commit/bcbf6d608e48d25306ecfd273118b4d6ba1c5df6 (2.29) https://github.com/andk/cpanpm/commit/46fe910becd5746adca92e18660567c9e8d37eb5 (2.29) https://github.com/andk/cpanpm/commit/7f9e5e8c52f535c1c13e177595a5ef4710c72058 (2.29) https://github.com/andk/cpanpm/commit/c03257dbebccd4deeff1987d5efd98113643f717 (2.29) https://github.com/andk/cpanpm/commit/7d4d5e32bcd9b75f7bf70a395938a48ca4a06d25 (2.33-TRIAL) https://github.com/andk/cpanpm/commit/89b13baf1d46e4fb10023af30ef305efec4fd603 (2.33-TRIAL) 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-2020-16156 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16156 Please adjust the affected versions in the BTS as needed.
Bug#1006472: Upload to unstable?
Hello maintainer of nemo, would you consider to upload this fix to unstable? It is currently only in experimental. I've found this issue, because it makes the Cinnamon live image non-reproducible. See https://wiki.debian.org/ReproducibleInstalls/LiveImages. With kind regards, Roland Clobus OpenPGP_signature Description: OpenPGP digital signature
Bug#953046: Wrongly picks AZERTY layout when alternative Canadian layout is present.
As regards a solution which survives a package update, the latest
ibus-mozc version in the Debian archive creates this file:
$ cat ~/.config/mozc/ibus_config.textproto
engines {
name : "mozc-jp"
longname : "Mozc"
layout : "default"
}
So to specify a layout you can now do:
layout : "ca"
layout_variant : "multix"
or just
layout : "jp"
Bug#1015972: k3b: CD fails to burn, even with correct permissions
Package: k3b Version: 20.12.2-1 Severity: important Dear Maintainer, I have an optical disc reader/burner and needed to burn an Audio CD, so I opened K3b, created a new Audio CD project, and hit "Burn". It took awhile to burn, and in the middle of it I get an error message: Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. Insufficient permissions for cdrdao executable: /bin/cdrdao K3b uses cdrdao to actually write CDs. This actually made my CD-R a coaster, as it seems that some part of the disc was already written, but no audio is playable after testing it in VLC. I later installed xfburn, interted a new CD-R and it burned the CD without issue. Because I still wanted to use K3b, I ran the command usermod -aG operator alex as root and restarted K3b. I was greeted to another error: Insufficient permissions for cdrecord executable: /bin/wodim K3b uses cdrecord to actually write CDs. Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. Insufficient permissions for cdrdao executable: /bin/cdrdao K3b uses cdrdao to actually write CDs. Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. Insufficient permissions for growisofs executable: /bin/growisofs K3b uses growisofs to actually write DVDs. Without growisofs you will not be able to write DVDs. Make sure to install at least version 5.10. Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. I logged out and logged back in, but still got the error. Then I ran the groups command. Here is the output: alex@galago-pro:~$ groups alex dialout cdrom floppy sudo audio dip operator video plugdev kvm netdev bluetooth lpadmin scanner libvirt wireshark It seems like I am a member of all the proper user groups (audio, video, cdrom, operator). After talking to some of the members of the #debian IRC channel, some helpful folks linked me to #983861 and https://salsa.debian.org/qt-kde-team/kde/k3b/-/blob/master/debian/README.Debian and I also found #401057. Looks like k3b is falsely requiring the operator group instead of cdrom, but even when you add your user to operator and cdrom, K3b still errors out, asking the user for operator permissions. And the README file says to run dpkg-statoverride --add root cdrom 04710 /usr/bin/wodim if I am still getting permission issues, so I ran that, and just to be safe, I rebooted my system and opened K3b. Upon opening, I didn't get an error message. Assuming that the command worked, I attempted to burn another CD-R and... it did the exact same thing as when I did it the first time... that makes two coasters. It seems like there is a problem with this package and the way it accepts permissions. Can anyone try it on their own system to confirm that the bug is reproducable? Thanks, Alex Relis -- Package-specific info: Device was not specified. Trying to find an appropriate drive... Detected CD-R drive: /dev/cdrw Using /dev/cdrom of unknown capabilities Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identification : 'BD-RE BP60NB10 ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages k3b depends on: ii cdparanoia 3.10.2+debian-13.1 ii cdrdao 1:1.2.4-2 ii genisoimage9:1.1.11-3.2 ii k3b-data 20.12.2-1 ii kio5.78.0-5 ii libc6 2.31-13+deb11u3 ii libk3b720.12.2-1 ii libkf5archive5 5.78.0-2 ii libkf5authcore55.78.0-2 ii libkf5bookmarks5 5.78.0-2 ii libkf5cddb54:20.12.0-1 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5i18n55.78.0-2 ii
Bug#1015975: Should python-neuroshare be removed?
Source: python-neuroshare Version: 0.9.2-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2014 - Dead upstream (last commits from 2016) If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015976: Should vmm be removed?
Source: vmm Version: 0.6.2-2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2017, removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015979: Should python-unshare be removed?
Source: python-unshare Version: 0.2-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2016 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1015982: jqueryui: CVE-2022-31160
Source: jqueryui X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for jqueryui. CVE-2022-31160[0]: | jQuery UI is a curated set of user interface interactions, effects, | widgets, and themes built on top of jQuery. Versions prior to 1.13.2 | are potentially vulnerable to cross-site scripting. Initializing a | checkboxradio widget on an input enclosed within a label makes that | parent label contents considered as the input label. Calling | `.checkboxradio( "refresh" )` on such a widget and the initial HTML | contained encoded HTML entities will make them erroneously get | decoded. This can lead to potentially executing JavaScript code. The | bug has been patched in jQuery UI 1.13.2. To remediate the issue, | someone who can change the initial HTML can wrap all the non-input | contents of the `label` in a `span`. https://github.com/jquery/jquery-ui/security/advisories/GHSA-h6gj-6jjq-h8g9 https://github.com/jquery/jquery-ui/commit/8cc5bae1caa1fcf96bf5862c5646c787020ba3f9 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-31160 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31160 Please adjust the affected versions in the BTS as needed.
Bug#1015983: undertow: CVE-2021-3859
Source: undertow X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for undertow. CVE-2021-3859[0]: https://bugzilla.redhat.com/show_bug.cgi?id=2010378 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-2021-3859 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3859 Please adjust the affected versions in the BTS as needed.
Bug#1015986: guacamole-client: CVE-2021-41767 CVE-2021-43999 CVE-2020-11997
Source: guacamole-client X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for guacamole-client. CVE-2021-41767[0]: | Apache Guacamole 1.3.0 and older may incorrectly include a private | tunnel identifier in the non-private details of some REST responses. | This may allow an authenticated user who already has permission to | access a particular connection to read from or interact with another | user's active use of that same connection. https://www.openwall.com/lists/oss-security/2022/01/11/6 CVE-2021-43999[1]: | Apache Guacamole 1.2.0 and 1.3.0 do not properly validate responses | received from a SAML identity provider. If SAML support is enabled, | this may allow a malicious user to assume the identity of another | Guacamole user. https://www.openwall.com/lists/oss-security/2022/01/11/7 CVE-2020-11997[2]: | Apache Guacamole 1.2.0 and earlier do not consistently restrict access | to connection history based on user visibility. If multiple users | share access to the same connection, those users may be able to see | which other users have accessed that connection, as well as the IP | addresses from which that connection was accessed, even if those users | do not otherwise have permission to see other users. https://lists.apache.org/thread.html/r1a9ae9d1608c9f846875c4191cd738f95543d1be06b52dc1320e8117%40%3Cannounce.guacamole.apache.org%3E https://issues.apache.org/jira/browse/GUACAMOLE-1123 https://github.com/apache/guacamole-client/pulls?q=is%3Apr+guacamole-1123+is%3Aclosed https://github.com/glyptodon/guacamole-client/pull/453 https://enterprise.glyptodon.com/doc/latest/cve-2020-11997-inconsistent-restriction-of-connection-history-visibility-31424710.html https://enterprise.glyptodon.com/doc/1.x/changelog-950368.html#id-.Changelogv1.x-1.14 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-41767 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41767 [1] https://security-tracker.debian.org/tracker/CVE-2021-43999 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43999 [2] https://security-tracker.debian.org/tracker/CVE-2020-11997 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11997 Please adjust the affected versions in the BTS as needed.
Bug#1015782: live-build: Replace a few more values in the splash SVG
Hello Petter, On 21/07/2022 08:36, Petter Reinholdtsen wrote: > The LinuxCNC live build provide a splash SVG with a few more strings > that are replaced at build time. ... > It would be great if these strings could be inserted by the official > live-build scripts, so the project did not have to use a patched > binary_syslinux. Of the 5 additional variables, only 3 are used in your SVG image (LB_ISO_APPLICATION, LB_ISO_PUBLISHER, LB_LINUX_PACKAGES). Do you mind if I will add only these three? xorriso does not recommend changing LB_ISO_PREPARER, so I would rather leave that one out. I've looked a little deeper into the repository. Perhaps the following questions should be redirected to a mailing list instead of drifting off-topic from this bug report: The file in patches/binary_syslinux is rather different from the version in git (https://salsa.debian.org/live-team/live-build). Have you tried using live-build from bookworm (which is currently at 1:20220505 or better yet, the latest version from git? (By setting LIVE_BUILD, see https://wiki.debian.org/ReproducibleInstalls/LiveImages) Your repository is called https://github.com/LinuxCNC/buster-live-build, which refers to buster, which is currently oldstable. Will you be aiming for bookworm? (You could use a single repository live-build-config, with several branches) The image for Grub (used for UEFI boot) is the default image. Is that intentional? With kind regards, Roland Clobus PS: In the README.md you could add a first step: lb config --config https://github.com/LinuxCNC/buster-live-build OpenPGP_signature Description: OpenPGP digital signature
Bug#1015987: cme does not allow package private build profile names
Package: libconfig-model-dpkg-perl Version: 2.161 Severity: normal File: /usr/share/perl5/Config/Model/models/Dpkg/Control/Binary.pl -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 According to the BuildProfileSpec[0], it is allowed to use private build profiles of the form `pkg.$sourcepackage.$anything` where "$anything must match the following regex [a-z0-9-]+". cme/libconfig-model-dpkg-perl do not recognise these, because it uses the regex "(?:\\s+)*". Regards, Victor Westerhuis [0]: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en_US:en:nl_NL:nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libconfig-model-dpkg-perl depends on: ii debhelper 13.8 ii libapt-pkg-perl0.1.40+b1 ii libarray-intspan-perl 2.004-2 ii libconfig-model-backend-yaml-perl 2.134-1 ii libconfig-model-perl 2.150-1 ii libdata-compare-perl 1.27-2 ii libexporter-lite-perl 0.09-1 ii liblog-log4perl-perl 1.55-1 ii libmouse-perl 2.5.10-1+b2 ii libparse-debcontrol-perl 2.005-5 ii libparse-recdescent-perl 1.967015+dfsg-3 ii libsoftware-licensemoreutils-perl 1.009-1 ii libsort-versions-perl 1.62-2 ii libtext-autoformat-perl1.75-1 ii libtext-levenshtein-damerau-perl 0.41-2 ii libtoml-tiny-perl 0.15-1 ii liburi-perl5.12-1 ii libwww-perl6.67-1 ii libyaml-libyaml-perl 0.83+ds-1+b1 ii licensecheck 3.3.0-1 ii lintian2.115.2 ii perl [libmodule-corelist-perl] 5.34.0-5 Versions of packages libconfig-model-dpkg-perl recommends: ii libconfig-model-tkui-perl 1.375-1 libconfig-model-dpkg-perl suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmLdoqwTHHZpY3RvckB3 ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+3mND/405+Zfs/cPHuqrcdUB2XQLJ1CKCfTl Rug5Jlyo4ShIWdV/CbxJk7BLZ5l9Tv+zGERGxddeqHqkV9NyIJ41ENiGYaPPv1zm TT1UcLr9ZxlJK13vBDV/mTZ3W7qvhIv9RJFg78nK0u/siP/ubDE5XDBKzVJRLPNX ddpFPUsXFVKCY3WTEG6S34LS9VzFEBGHyIeU7nO2Gpo4np6gehSJ4Vz/w7F/x2Kx aA89wIjuY5hrv0GWiPaFTjpfxW1YrKwpL01Q+/Rz6yHGNOAFpUkxmzTc7oSwdxfH izCUlmbpDewmG+//AYtNM+noRJgxZqrKlir3VoeclidGsn41ldV3YsfPCKj+OPrh Ki6fdVlDPMzIvGjKojCbBSzgFXh6z2ZAhNBdMa1PIScgnzbkxEb+1bXOB4iVb+Sl JNgyHHLjh+8r6WAdJQW/VjF/9yE1TPSOWV5YvYIZO5HjYmH1F+owBg0/bvm9giAd BIXPFbBD5PGxLcc1ua47P6P9w75oMS4vDTJyhp4SMDweVi2VygTBzk/LtxsnPUkt sedO9Npd81j/aA+H652KbUe+IreUvlJuuL9lqN+N5hlGlQiq1lCbDujDX+pPfZoz 6xYtEX3FMf81RQ1QUDmRh2IV74JsCcKe90KlH3TKA00FIZNASgAUlND6OPmdoaNp 8GuB5S4uYL+eow== =0N+v -END PGP SIGNATURE-
Bug#1015978: Should falcon be removed?
Hi Moritz, thanks for bringing this up. I agree that falcon your point is perfectly valid. On the other hand we have a new upstream version in Git which now depends from Python3 and is a promising candidate to fix the Python3 bug. Unfortunately the package does not build[1] which is probably a gcc issue. If someone would volunteer to fix this issue we might be able to keep the package. If there is no response in say two weeks we should probably remove it since it becomes obvious that there is no interest in this package. Kind regards Andreas. [1] https://salsa.debian.org/med-team/falcon/-/jobs/3033927 Am Sun, Jul 24, 2022 at 08:13:58PM +0200 schrieb Moritz Muehlenhoff: > Source: falcon > Version: 1.8.8-1 > Severity: serious > > Your package came up as a candidate for removal from Debian: > - Still depends on Python 2 > - Dropped from testing in 2018 > - Last upload in 2017 > > If you disagree and want to continue to maintain this package, > please just close this bug (and fix the open issues). > > If you agree with the removal, please reassign to ftp.debian.org > by sending the following commands to cont...@bugs.debian.org: > > -- > severity $BUGNUM normal > reassign $BUGNUM ftp.debian.org > retitle $BUGNUM RM: -- RoM; > thx > -- > > Otherwise I'll move forward and request it's removal in a month. > > Cheers, > Moritz > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > -- http://fam-tille.de
Bug#953046: Wrongly picks AZERTY layout when alternative Canadian layout is present.
On 2022-07-24 11:42, Charles Plessy wrote:
gsettings get org.gnome.desktop.input-sources sources
[('ibus', 'mozc-jp'), ('xkb', 'jp'), ('xkb', 'ca+multix')]
I don't understand from where it gets AZERTY, but I may have a solution.
ibus-mozc 2.23.2815.102+dfsg-4, which you at least used when reporting
the issue, installs the /usr/share/ibus/component/mozc.xml file with
this line:
default
I changed that on my own machine to:
ca
multix
and it seemed to work. Optionally you can just change it to:
jp
Can you please test those suggestions and let us know if it makes a
difference for you.
--
Gunnar
Bug#1015990: libgetdataFTBFS with Python 3.10 as only supported Python3 version
Source: libgetdata Version: 0.11.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=libgetdata=0.11.0-3%2Bb1 ... dh_install -a install -d debian/.debhelper/generated/libgetdata-doc install -d debian/libgetdata-dev//usr/include cp --reflink=auto -a debian/tmp/usr/include/getdata debian/tmp/usr/include/getdata.f debian/tmp/usr/include/getdata.h debian/libgetdata-dev//usr/include/ install -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.a debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.a debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/ install -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.so debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata/ install -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/getdata.pc debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig/ install -d debian/.debhelper/generated/libgetdata-dev install -d debian/libgetdata8//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8 debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8.1.0 debian/libgetdata8//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libgetdata8 install -d debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7 debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7.1.0 debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libgetdata\+\+7 install -d debian/libfgetdata6//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6 debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6.1.0 debian/libfgetdata6//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libfgetdata6 install -d debian/libf95getdata7//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7 debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7.1.0 debian/libf95getdata7//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libf95getdata7 install -d debian/libgetdata-tools//usr/bin cp --reflink=auto -a debian/tmp/usr/bin/checkdirfile debian/tmp/usr/bin/dirfile2ascii debian/libgetdata-tools//usr/bin/ install -d debian/libgetdata-tools//usr/share/man/man1 cp --reflink=auto -a debian/tmp/usr/share/man/man1/checkdirfile.1 debian/tmp/usr/share/man/man1/dirfile2ascii.1 debian/libgetdata-tools//usr/share/man/man1/ dh_install: warning: Cannot find (any matches for) "usr/lib/python3*/site-packages/pygetdata*so" (tried in ., debian/tmp) dh_install: warning: python3-pygetdata missing files: usr/lib/python3*/site-packages/pygetdata*so dh_install: error: missing files, aborting install -d debian/.debhelper/generated/libgetdata-tools install -d debian/.debhelper/generated/python3-pygetdata install -d debian/.debhelper/generated/libgetdata-perl make: *** [debian/rules:28: binary-arch] Error 25
Bug#1015991: xscreensaver: quick power-off does not work if power management is disabled
Package: xscreensaver Version: 6.02+dfsg1-2 Severity: normal The 'Quick Power-off in Blank Only Mode' option has no effect if the 'Display Power Management' option is not enabled. This is presumably because xscreensaver does not run DPMSEnable() before DPMSForceLevel(). -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xscreensaver depends on: ii init-system-helpers 1.64 ii libatk1.0-0 2.38.0-1 ii libc62.33-8 ii libcrypt11:4.4.28-2 ii libglib2.0-0 2.72.3-1 ii libgtk2.0-0 2.24.33-2 ii libpam0g 1.4.0-13 ii libpango-1.0-0 1.50.7+ds-1 ii libsystemd0 251.2-7 ii libx11-6 2:1.7.5-1 ii libxext6 2:1.3.4-1 ii libxft2 2.3.4-1 ii libxi6 2:1.8-1 ii libxinerama1 2:1.1.4-3 ii libxml2 2.9.14+dfsg-1+b1 ii libxrandr2 2:1.5.2-2+b1 ii libxt6 1:1.2.1-1 ii libxxf86vm1 1:1.1.4-1+b2 ii xscreensaver-data6.02+dfsg1-2 Versions of packages xscreensaver recommends: pn gsfonts-x11 | xfonts-100dpi ii libjpeg-turbo-progs 1:2.1.2-1 ii perl 5.34.0-5 ii wamerican [wordlist] 2020.12.07-2 ii wfrench [wordlist] 1.2.6-1 ii wpolish [wordlist] 20220301-1 Versions of packages xscreensaver suggests: ii chromium [www-browser] 103.0.5060.134-1 ii firefox [www-browser]102.0.1-3 ii fortune-mod [fortune]1:1.99.1-7.1 pn gdm3 | kdm-gdmcompat ii lynx [www-browser] 2.9.0dev.10-1 pn qcam | streamer pn xdaliclock pn xfishtank ii xscreensaver-data-extra 6.02+dfsg1-2 ii xscreensaver-gl 6.02+dfsg1-2 ii xscreensaver-gl-extra6.02+dfsg1-2 -- no debconf information
Bug#1015992: python-jpype FTBFS with 3.10 as only supported Python3 version
Source: python-jpype Version: 1.4.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-jpype=1.4.0-1%2Bb1 ... debian/rules override_jh_installlibs make[1]: Entering directory '/<>' jh_installlibs rm /<>/debian/python3-jpype/usr/lib/python3/dist-packages/org.jpype.jar rm /<>/debian/python3-jpype/usr/lib/python3.10/dist-packages/org.jpype.jar rm: cannot remove '/<>/debian/python3-jpype/usr/lib/python3.10/dist-packages/org.jpype.jar': No such file or directory make[1]: *** [debian/rules:17: override_jh_installlibs] Error 1
