Bug#1077193: O: bucklespring -- Nostalgia bucklespring keyboard sound
Package: wnpp Severity: normal I am orphaning bucklespring, as I don't use it anymore and have no proper ways of testing with legacy environments. signature.asc Description: PGP signature
Bug#919265: Orphan xloadimage
Control: retitle -1 O: xloadimage -- Graphics file viewer under X11 I am orphaning this package. I have not used it for several years. signature.asc Description: PGP signature
Bug#1072469: shc: FTBFS: build-depends on ash which does no longer exist
Hi, I also noticed the reverse build dependency of shc on ash in Ubuntu (see: https://bugs.launchpad.net/debian/+source/shc/+bug/2073141). > The trivial fix is to build-depend on dash instead, as in the attached patch. Even though this technically works, test/ttest.sh fails the build, because of failing test cases for /bin/ash, which is to be expected when it no longer gets installed. I submitted a fix for - Debian (https://salsa.debian.org/debian/shc/-/merge_requests/3) and - Upstream (https://github.com/neurobin/shc/pull/167) Best regards, Dominik P.S.: This is the first time that I use the Debian BTS E-Mail interface. Feel free to educate me if I did something wrong.
Bug#1074630: xrayutilities: fails tests with matplotlib 3.8
I believe I fixed this upstream some time ago:
https://github.com/dkriegner/xrayutilities/commit/8da8fd0fda2a54a23d5e65b6d043f6f808cb06ff
Likely you can patch that in debian easily.
On Tue, Jul 2, 2024 at 12:39 PM Drew Parsons wrote:
> Source: xrayutilities
> Version: 1.7.4-1
> Severity: normal
>
> xrayutilities is failing tests with matplotlib 3.8 from experimental
>
> 470s _ TestExampleScripts.test_simpack_powdermodel
> __
> 470s
> 470s self = testMethod=test_simpack_powdermodel>
> 470s
> 470s def test(self):
> 470s with tempfile.TemporaryFile(mode='w') as fid:
> 470s env = os.environ.copy()
> 470s env['MPLBACKEND'] = 'agg'
> 470s cmd = [sys.executable, scriptname]
> 470s > subprocess.run(cmd, env=env, cwd=scriptdir, stdout=fid,
> 470scheck=True)
> 470s
> 470s tests/test_examples.py:78:
> 470s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _ _
> 470s
> 470s input = None, capture_output = False, timeout = None, check = True
> 470s popenargs = (['/usr/bin/python3.11', 'simpack_powdermodel.py'],)
> 470s kwargs = {'cwd':
> '/tmp/autopkgtest-lxc.jsvdm1mu/downtmp/autopkgtest_tmp/tests/../examples',
> 'env': {'ADTTMP':
> '/tmp/autopkgtest...topkgtest-lxc.jsvdm1mu/downtmp/autopkgtest_tmp', ...},
> 'stdout': <_io.TextIOWrapper name=12 mode='w' encoding='UTF-8'>}
> 470s process = 'simpack_powdermodel.py']>
> 470s stdout = None, stderr = None, retcode = 1
> 470s
> 470s def run(*popenargs,
> 470s input=None, capture_output=False, timeout=None,
> check=False, **kwargs):
> 470s """Run command with arguments and return a CompletedProcess
> instance.
> 470s
> 470s The returned instance will have attributes args, returncode,
> stdout and
> 470s stderr. By default, stdout and stderr are not captured, and
> those attributes
> 470s will be None. Pass stdout=PIPE and/or stderr=PIPE in order to
> capture them,
> 470s or pass capture_output=True to capture both.
> 470s
> 470s If check is True and the exit code was non-zero, it raises a
> 470s CalledProcessError. The CalledProcessError object will have
> the return code
> 470s in the returncode attribute, and output & stderr attributes
> if those streams
> 470s were captured.
> 470s
> 470s If timeout is given, and the process takes too long, a
> TimeoutExpired
> 470s exception will be raised.
> 470s
> 470s There is an optional argument "input", allowing you to
> 470s pass bytes or a string to the subprocess's stdin. If you use
> this argument
> 470s you may not also use the Popen constructor's "stdin"
> argument, as
> 470s it will be used internally.
> 470s
> 470s By default, all communication is in bytes, and therefore any
> "input" should
> 470s be bytes, and the stdout and stderr will be bytes. If in text
> mode, any
> 470s "input" should be a string, and stdout and stderr will be
> strings decoded
> 470s according to locale encoding, or by "encoding" if set. Text
> mode is
> 470s triggered by setting any of text, encoding, errors or
> universal_newlines.
> 470s
> 470s The other arguments are the same as for the Popen constructor.
> 470s """
> 470s if input is not None:
> 470s if kwargs.get('stdin') is not None:
> 470s raise ValueError('stdin and input arguments may not
> both be used.')
> 470s kwargs['stdin'] = PIPE
> 470s
> 470s if capture_output:
> 470s if kwargs.get('stdout') is not None or
> kwargs.get('stderr') is not None:
> 470s raise ValueError('stdout and stderr arguments may not
> be used '
> 470s 'with capture_output.')
> 470s kwargs['stdout'] = PIPE
> 470s kwargs['stderr'] = PIPE
> 470s
> 470s with Popen(*popenargs, **kwargs) as process:
> 470s try:
> 470s stdout, stderr = process.communicate(input,
> timeout=timeout)
> 470s except TimeoutExpired as exc:
> 470s process.kill()
> 470s if _mswindows:
> 470s # Windows accumulates the output in a single
> blocking
> 470s # read() call run on child threads, with the
> timeout
> 470s # being done in a join() on those threads.
> communicate()
> 470s # _after_ kill() is required to collect that and
> add it
> 470s # to the exception.
> 470s exc.stdout, exc.stderr = process.communicate()
> 470s else:
> 470s # POSIX _communicate already populated the output
> so
> 470s # far into the TimeoutExpired exception.
> 470s process.wait()
> 470s raise
> 470s
Bug#1071084: Updated patch
A slightly adjusted patch which uses one more newline:
--- /usr/update-locale 2024-05-13 23:42:46.584127893 +0200
+++ /usr/sbin/update-locale 2024-05-14 11:18:56.086121879 +0200
@@ -88,7 +88,7 @@
{
# Check that this locale does exist
my $charset = `LANG= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE=
LC_MEASUREMENT= LC_IDENTIFICATION= LC_ALL= $env locale charmap 2>&1`;
- die "*** $progname: Error: invalid locale settings: $env\n"
+ die "*** $progname: Error: invalid locale settings:
$env\n\n--\n$charset--\n"
if ($charset =~ m/Cannot set/);
# If LANGUAGE is set, its first value must be compatible with
LC_MESSAGES
if (defined $arg{LANGUAGE})
Bug#1071084: locales: update-locale hides error information when invoking 'locale charmap'
Package: locales
Version: 2.38-10
Severity: normal
Tags: newcomer, patch
The perl script update-local internally invokes 'locale charmap' to perform
additional checks.
However if this call fails for some reason, update-locale always only prints
"Error: invalid locale settings: LANG=" which can be very misleading when
the root-cause is actually different.
I.e. sample output of "sudo /usr/sbin/update-locale LANG=de_AT.UTF-8" on Debian
Trixie:
*** update-locale: Error: invalid locale settings: LANG=de_AT.UTF-8
After applying the following patch:
==
--- /usr/update-locale 2024-05-13 23:42:46.584127893 +0200
+++ /usr/sbin/update-locale 2024-05-13 23:40:25.160121142 +0200
@@ -88,7 +88,7 @@
{
# Check that this locale does exist
my $charset = `LANG= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE=
LC_MEASUREMENT= LC_IDENTIFICATION= LC_ALL= $env locale charmap 2>&1`;
- die "*** $progname: Error: invalid locale settings: $env\n"
+ die "*** $progname: Error: invalid locale settings:
$env\n\n--$charset--\n"
if ($charset =~ m/Cannot set/);
# If LANGUAGE is set, its first value must be compatible with
LC_MESSAGES
if (defined $arg{LANGUAGE})
==
The output contains the actual information why the call to "locale chaarmap"
failed, thus making it possible to investigate why the call actually failed:
===
*** update-locale: Error: invalid locale settings: LANG=de_AT.UTF-8
--locale: Cannot set LC_CTYPE to default locale: No such file or
directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968
--
===
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages locales depends on:
ii debconf [debconf-2.0] 1.5.86
ii libc-bin 2.38-10
ii libc-l10n 2.38-10
locales recommends no packages.
locales suggests no packages.
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "de_AT.UTF-8",
LC_MONETARY = "de_AT.UTF-8",
LC_CTYPE = "C.UTF-8",
LC_ADDRESS = "de_AT.UTF-8",
LC_TELEPHONE = "de_AT.UTF-8",
LC_NAME = "de_AT.UTF-8",
LC_MEASUREMENT = "de_AT.UTF-8",
LC_IDENTIFICATION = "de_AT.UTF-8",
LC_NUMERIC = "de_AT.UTF-8",
LC_PAPER = "de_AT.UTF-8",
LANG = "de_AT.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locales/locales_to_be_generated:
locales/default_environment_locale: None
Bug#1060235: Information about report to upstream
For the lack of reaction, I also reported the error to the upstream maintainers: https://github.com/WayneD/rsync/issues/577
Bug#1063368: kate: Shift-key not working
Hello, On 07/02/2024 00:50, Patrick Franz wrote: Hej, Am Dienstag, 6. Februar 2024, 22:10:47 CET schrieb Dominik: Package: kate Version: 4:22.12.3-1 Severity: important Dear Maintainer, The shift key has no effect when writing (e.g. Shift+a results in 'a' instead of 'A'). Some general observations about the probelm itself: - Caps lock works. - Shift hotkeys work (e.g. Shift+Left in order to mark the character left of the cursor). - Alt Gr has the same problem (I changed my keybooard layout to german and Alt Gr+q prints 'q' instead of '@'). - Some other applications have the same issue (e.g. kwrite, vlc, texstudio, wireshark). I think all my Qt-applications do, but Qt might also be unrelated. Other applications such as xfce4-terminal or firefox work flawlessly. With "distrobox" I created a container for debian stable (like mine) and debian testing, and the problem occurs only in the "stable" conteiner. Therefore, I don't think it's some configuration error of mine. Also, this suggests that the bug has been fixed in more recent package versions. However, those are not available yet for stable via apt upgrade. stable: image: quay.io/toolbx-images/archlinux-toolbox:latest Qt-Version (kate): 5.15.8 kate-Version: 22.12.3 testing: image: docker.io/library/debian:testing Qt-Version (kate): 5.15.10 kate-Version: 23.08.1 I'm slightly confused about which system you are actually running and how you do that (natively or in a container). Because your "Debian stable" seems to be some Arch container. I have a native desktop system which I upgraded from Debian 11 to 12 bookworm a couple of days ago. Something during the upgrade-process must've broken it. I use distrobox only for testing/comparison purposes. The quay.io link was a Debian container from the Archlinux repo, but even with the container docker (docker.io/library/debian:stable-backports) this issue persists. Also, I cannot reproduce the issue on Debian Stable and I don't remember this ever being an issue. Since using a newer package fixes the problem it has to be a bug - which only appears in combination with my system configuration. Unfortunately, I don't know which parts of my configuration might trigger this bug or how to make the bug reproducible on other systems. I've tried everything I know in trying to narrow the problem down, so if you have any suggestions/questions I'd be happy to try/answer them. Dominik
Bug#1063368: kate: Shift-key not working
Package: kate Version: 4:22.12.3-1 Severity: important Dear Maintainer, The shift key has no effect when writing (e.g. Shift+a results in 'a' instead of 'A'). Some general observations about the probelm itself: - Caps lock works. - Shift hotkeys work (e.g. Shift+Left in order to mark the character left of the cursor). - Alt Gr has the same problem (I changed my keybooard layout to german and Alt Gr+q prints 'q' instead of '@'). - Some other applications have the same issue (e.g. kwrite, vlc, texstudio, wireshark). I think all my Qt-applications do, but Qt might also be unrelated. Other applications such as xfce4-terminal or firefox work flawlessly. With "distrobox" I created a container for debian stable (like mine) and debian testing, and the problem occurs only in the "stable" conteiner. Therefore, I don't think it's some configuration error of mine. Also, this suggests that the bug has been fixed in more recent package versions. However, those are not available yet for stable via apt upgrade. stable: image: quay.io/toolbx-images/archlinux-toolbox:latest Qt-Version (kate): 5.15.8 kate-Version: 22.12.3 testing: image: docker.io/library/debian:testing Qt-Version (kate): 5.15.10 kate-Version: 23.08.1 Sorry if I made any errors in posting this bug report, as it appears to be fixed in more recent kate versions. I dont know anything about the inner working or policies of debian. -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-17-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.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 kate depends on: ii kate5-data 4:22.12.3-1 ii kio 5.103.0-1 ii ktexteditor-katepart 5.103.0-1.1 ii libc62.36-9+deb12u4 ii libkf5activities55.103.0-1 ii libkf5bookmarks5 5.103.0-1 ii libkf5completion55.103.0-1 ii libkf5configcore55.103.0-2 ii libkf5configgui5 5.103.0-2 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons55.103.0-1 ii libkf5crash5 5.103.0-1 ii libkf5dbusaddons55.103.0-1 ii libkf5guiaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libkf5iconthemes55.103.0-1 ii libkf5jobwidgets55.103.0-1 ii libkf5kiocore5 5.103.0-1 ii libkf5kiofilewidgets55.103.0-1 ii libkf5kiogui55.103.0-1 ii libkf5kiowidgets55.103.0-1 ii libkf5newstuff5 5.103.0-1 ii libkf5newstuffcore5 5.103.0-1 ii libkf5newstuffwidgets5 5.103.0-1 ii libkf5parts5 5.103.0-1 ii libkf5service-bin5.103.0-1 ii libkf5service5 5.103.0-1 ii libkf5syntaxhighlighting55.103.0-3 ii libkf5texteditor55.103.0-1.1 ii libkf5textwidgets5 5.103.0-1 ii libkf5wallet-bin 5.103.0-1 ii libkf5wallet55.103.0-1 ii libkf5widgetsaddons5 5.103.0-1 ii libkf5windowsystem5 5.103.0-1 ii libkf5xmlgui55.103.0-1 ii libkuserfeedbackcore11.2.0-2 ii libkuserfeedbackwidgets1 1.2.0-2 ii libqt5concurrent55.15.8+dfsg-11 ii libqt5core5a 5.15.8+dfsg-11 ii libqt5dbus5 5.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5network5 5.15.8+dfsg-11 ii libqt5sql5 5.15.8+dfsg-11 ii libqt5widgets5 5.15.8+dfsg-11 ii libqt5xml5 5.15.8+dfsg-11 ii libstdc++6 12.2.0-14 ii plasma-framework 5.103.0-1+deb12u1 ii qml-module-org-kde-kquickcontrolsaddons 5.103.0-1 ii qml-module-qtquick-layouts 5.15.8+dfsg-3 ii qml-module-qtquick2 5.15.8+dfsg-3 Versions of packages kate recommends: ii sonnet-plugins 5.103.0-1 Versions of packages kate suggests: pn darcs pn exuberant-ctags ii git
Bug#1060913: Re: Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys
Hi, > Here I am not a member of DebianEdu team and told if am not a member > of one team there is no reason to do team upload. > Ideally, I should contact the team to join in or tell team I am going > to fix ftbfs issue. Whether the maintainer is a team doesn't matter here (it just means I am not responsible alone for the lack of updates on the package, haha ;)). In general, you always contact the maintainer for every upload before doing an NMU, through the address from the package meta-data or by sending your changes to the BTS into the bug you are fixing. > But I got no response from there(not DebianEdu > team) in the past. Can you point me to message IDs where you requested changes to be uploaded? Ideally, you should just send the changes to the BTS bug you are fixing, and tag it "patch". -nik signature.asc Description: PGP signature
Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys
Hi, is there a reason why you are not working with the packaging team, and doing NMUs without contacting the team beforehand? -nik
Bug#1060235: rsync: --ignore-existing and --size-only have no effect when combined with -t
Package: rsync Version: 3.2.7-1 Severity: normal Dear Maintainer, Excected outcome: I wanted to preserve the time of modification for files that did not exist on target, but do not change files that already exist, even if the modification times differ. Attempted action: I thought that rsync with -t and --ignore-existing would be a perfect fit for that; their summary taken from rsync --help: --times, -t preserve modification times --ignore-existing skip updating files that exist on receiver Actual result: I compared the output of two commands: rsync -rlv --dry-run dir1 dir2 and rsync -rlv --ignore-existing --dry-run dir1 dir2 print the same 3 files, which indeed do not exist on the target. However, rsync -rlvt --dry-run dir1 dir2 and rsync -rlvt --ignore-existing --dry-run dir1 dir2 print a few hundred files. Most of them, with the exception of the mentioned 3, exist in dir2. It seems that --ignore-existing takes no effect when combined with -t: the number of lines returned is the same in both cases. Case of --size-only: I expanded the above combination with --size-only (--help: skip files that match in size), which in my opinion should be sufficient for my use-case on its own, but it didn't help either. Summary: Apparently combining the -t option with --ignore-exisitng or --size-only renders the latter useless. Assuming the best case, their --help strings are inprecise enough that their wrong behaviour is assumed. -- System Information: Debian Release: 12.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-17-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 rsync depends on: ii init-system-helpers1.65.2 ii libacl12.3.1-3 ii libc6 2.36-9+deb12u3 ii liblz4-1 1.9.4-1 ii libpopt0 1.19+dfsg-1 ii libssl33.0.11-1~deb12u2 ii libxxhash0 0.8.1-1 ii libzstd1 1.5.4+dfsg2-5 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-4 ii zlib1g 1:1.2.13.dfsg-1 rsync recommends no packages. Versions of packages rsync suggests: ii openssh-client 1:9.2p1-2+deb12u2 ii openssh-server 1:9.2p1-2+deb12u2 ii python3 3.11.2-1+b1 pn python3-braceexpand -- no debconf information
Bug#1060218: xmobar: cannot run with Wireless plugin
Package: xmobar Version: 0.46-2 Severity: normal Dear Maintainer, After removing libiw-dev dependency (#1058738) xmobar fails to run with Wireless plugin in the config file. Best regards, Dominik -- System Information: Debian Release: trixie/sid APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.9-amd64 (SMP w/12 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xmobar depends on: ii libasound2 1.2.10-3 ii libc62.37-13 ii libcairo21.18.0-1 ii libffi8 3.4.4-2 ii libglib2.0-0 2.78.3-1 ii libgmp10 2:6.3.0+dfsg-2 ii libharfbuzz0b8.0.1-1 ii libpango-1.0-0 1.51.0+ds-3 ii libpangocairo-1.0-0 1.51.0+ds-3 ii libpng16-16 1.6.40-3 ii libx11-6 2:1.8.7-1 ii libxext6 2:1.3.4-1+b1 ii libxft2 2.3.6-1 ii libxinerama1 2:1.1.4-3 ii libxpm4 1:3.5.17-1 ii libxrandr2 2:1.5.2-2+b1 ii libxrender1 1:0.9.10-1.1 ii libxss1 1:1.2.3-1 ii zlib1g 1:1.3.dfsg-3 xmobar recommends no packages. Versions of packages xmobar suggests: ii xmonad 0.17.2-1+b1 -- no debconf information
Bug#1050621: blends-dev: Support conflicts and breaks relations in meta-packages
Package: blends-dev Version: 0.7.5 Severity: wishlist As discussed in [1], I would like to request addition of Conflicts and Breaks relationships in tasks meta-package descriptions. I ahve already started to scan the sources of blends-dev and to implement the basics for the feature in [2], which works as I want it. However, there are a few missing parts: * Packages in Conflicts or Breaks on some meta-package, but not in Requires, Recommends, Suggests or Ignore on others should be added to Avoid * The generated web pages should probably get a section for listed Conflcits and Breaks Happy to receive advice on these two or any other missing parts. [1] https://lists.debian.org/debian-blends/2023/08/msg0.html [2] https://salsa.debian.org/blends-team/blends/-/merge_requests/14
Bug#1049328: Reverting nested groups feature in Debian's GOsa²
Hi, > However, group nesting is not a feature that can be used with posixGroup > objectClass based LDAP objects (as the objectClass / schema does not support > group nesting). I really have a huge question mark about what upstream's > intention for this feature was/is... It is not a feature, but definitely possible using dynlist (we did this at Teckids before abandonning LDAP): https://www.openldap.org/faq/data/cache/1209.html Maybe GOSa expects something like that to be in place? -nik
Bug#1042906: ansible: please package new upstream version 8.x
Source: ansible Version: 7.3.0+dfsg-1 Severity: wishlist Hi Lee, Ansible upstream is currently at 8.2. In order to not having to resort to pip install, an update of Debian's ansible package would be much appreciated. Cheers, Nik
Bug#1042772: O: pam-krb5-migrate -- PAM module for migrating to Heimdal Kerberos
Package: wnpp Severity: normal X-Debbugs-Cc: pam-krb5-migr...@packages.debian.org Control: affects -1 + src:pam-krb5-migrate -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I intend to orphan the pam-krb5-migrate package. The package description is: A stackable authentication module that takes a username and password from an earlier module in the stack and attempts to transparently add the user to a Kerberos realm using the Kerberos 5 kadmin service. The module can be used to ease the administrative burdens of migrating a large installed userbase from pre-existing authentication methods to a Kerberos-based setup. . This package allows updating the database of a remote Heimdal server. As I do not rely on Kerberos anymore myself, it is hard for me to spot issues with the module. -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCZMfyMDEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3YK9AP9Ks4Mh9kFp1TVf6EtRoxYD eNWJysTXIBE6+IU56kKrwQD/Y1K6xwWEA3riziSm/KqDqhqn5XU0Q51rug0C18Ji dQA= =GqUh -END PGP SIGNATURE-
Bug#1042771: O: gnome-pass-search-provider -- GNOME Shell search provider for the pass password manager
Package: wnpp Severity: normal X-Debbugs-Cc: gnome-pass-search-provi...@packages.debian.org Control: affects -1 + src:gnome-pass-search-provider -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I intend to orphan the gnome-pass-search-provider package. The package description is: This GNOME search provider integrates the pass utility into GNOME Shell. It can search password entries and copy passwords as well as arbitrary fields (username, pin, etc.) from the GNOME Shell search frontend. It also supports the OTP extension (from the pass-extension-otp package). As I do not use GNOME anymore, it is hard for me to spot when this package needs love. -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCZMfw5TEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3UN9AP9PXGhSdhTD39EVf5gpO3lR x0ofjMVWBxqpImNE5Ue9dwD/SgNMGaikq0hVrAwmgPAyYI5yRI/qkrO8+yYP5+mh wAM= =IYSE -END PGP SIGNATURE-
Bug#1040003: jackd: add pipewire-jack to dependency alternativees
Package: jackd Version: 5+nmu1 Severity: wishlist The pipewire-jack package provides a JACKd implementation based on PipeWire, which I am using on my audio recording workstation. Other packages depend on jackd if they need a JACK daemon to talk to (e.g. qjackctl), and that pulls in jackd2 currently, which I do not need. Please allow pipewire-pulse to satisfy the dependency on a JACKd implementation. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jackd depends on: pn jackd2 | jackd1 jackd recommends no packages. jackd suggests no packages.
Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files
> Ok, how about: "the whole project, minus naturesha...@debian.org who > appears to be unfamiliar with the concept of hyperboles, is moving > toward git and Salsa". Better? No. Your "hyperbole" very much read as "Come on, minority who cares about the mail workflow, you're weird anachronists, get onto the Salsa train already!" So that's what I am criticizing. -nik signature.asc Description: PGP signature
Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files
> The whole project is moving toward git and Salsa Sorry for the noise, but as you are clearly misattributing this to me (I am part of the project, so "the whole project" includes me): I am not, and do not want to, move bugs and patches to Git and Salsa. I consider it a huge advantage of Debian that I can contribute limitless with something as barrierfree as an e-mail. If you voice your opinion, please do not impose it on me. Thanks! -nik
Bug#1035108: ITP: rdflib-sqlalchemy -- RDFLib store using SQLAlchemy dbapi as back-end
Package: wnpp Severity: wishlist Owner: Dominik George X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rdflib-sqlalchemy Version : 0.5.4 Upstream Contact: Mark Watts * URL : https://github.com/RDFLib/rdflib-sqlalchemy * License : BSD-3-clause Programming Lang: Python Description : RDFLib store using SQLAlchemy dbapi as back-end RDFlib-SQLAlchemy is a formula-aware store for RDFlib that uses SQLAlchemy to persist triples in relational databases. I will maintain the package under the Debian Python Team. -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCZE15njEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3UpmAP4nttkSjVJbdmIU0ECtjWju Z00zP7ebS3KHBCGyww0XLgEA+lIczQMdcGq7n9TOKRryhAhQ8hRwdWj7uc8cCQ5R jQ8= =tzxJ -END PGP SIGNATURE-
Bug#1035100: Unrelated political statement in main UI
Package: thonny Version: 4.0.1-1 Severity: important Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thonny now has a Ukraine flag in its main UI, linking to a GitHub page about the Russian invasion. This is problematic for two reasons: * Thonny is used for education, and education should, inherently, be free of political views, if not related to the subject of the course * GitHub invades on user privacy, and the main UI should not drop users into a browser leading to a privacy-invading web platform (The second point is even worse for the Python Tutor linked from the menu, which is a shitload of tracking and advertising; will be reported separately.) The Ukraine button should be removed (even though I personally agree with the linked content. This issue is a blocker for using Thonny for its original purpose, and the context of the target group of its packaging team. Cheers, NIk - -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=C.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 thonny depends on: ii mypy 1.0.1-1 ii pylint 2.16.2-2 ii python33.11.2-1+b1 ii python3-asttokens 2.2.1-1 ii python3-docutils 0.19+dfsg-6 ii python3-jedi 0.18.2-1 ii python3-mypy 1.0.1-1 ii python3-pip23.0.1+dfsg-1 ii python3-pkg-resources 66.1.1-1 ii python3-send2trash 1.8.1~b0-2 ii python3-serial 3.5-1.1 ii python3-tk 3.11.2-2 ii python3-venv 3.11.2-1+b1 ii python3-wheel 0.38.4-2 Versions of packages thonny recommends: ii xsel1.2.0+git9bfc13d.20180109-4 ii zenity 3.44.0-1 Versions of packages thonny suggests: ii python3-distro 1.8.0-1 - -- no debconf information -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCZE1EjzEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3W4iAQCDRLgBVM6VDoiHrs1KOhmb CItExlVFSHIILuWryqqZFAD9EHQLnjEttKONGgDJw84mhOnmxUn9yqh11AlSlH2l eQk= =tOF6 -END PGP SIGNATURE-
Bug#973883: comment
I see the same issue about invalid permissions of /var/log/apt-cacher-ng when installing the latest package on bookworm. I installed it multiple times on this VM before without this issue, not sure why it started to fail in this way now. Somehow the /var/log/apt-cacher-ng directory has owner = "root", no manual intervention was done as far as I am aware. When apt-cacher-ng package is installed it fails with the error about permission on /var/log/apt-cacher-ng folder. Could it be some sort of regression via some other package which adjusts permission of files in /var/log? apt-cacher-ng does not seem to have had any release lately so no regression there. Could either the installation of the package perform a check and fix or the systemd service could adjust access rights during startup to make apt-cacher-ng more robust against such invalid permissions?
Bug#1033436: retitle
retitle 1033436 Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.3:test
Bug#1033407: duplicate bugs
merge 1033407 1032989 -- These two bug-reports sound very similar, #1032989 has a lot of investigation already.
Bug#1032468: More info needed
Works as expected on a fresh installation of bookworm. Can you provide the output of the following command dpkg --list | grep dbus P.S. Regarding "First, any recommended application is expected to work without any issue" => This sounds a bit strange when you are actually using a totally free operating system built by volunteers! Please consider how much you can "expect" or "request" here. Better to spend time yourself to improve Debian. If you think the application or X-Windows itself should do things differently, you are welcome to provide improvements and patches to the upstream projects!
Bug#1032019: python3.11: deadlock on interpreter shutdown waiting for threads
Package: python3.11 Version: 3.11.2-4 Severity: important Tags: upstream fixed-upstream Forwarded: https://github.com/python/cpython/issues/102126 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Python 3.11.2 introduced a deadlock on interpreter shutdown when using threads, causing quite a few libraries and tools to hang on exit. https://github.com/python/cpython/issues/102126 Fixed upstream; reporting here to track for bookworm. - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3.11 depends on: ii libpython3.11-stdlib 3.11.1-2 ii media-types 9.0.0 ii mime-support 3.66 ii python3.11-minimal3.11.1-2 python3.11 recommends no packages. Versions of packages python3.11 suggests: ii binutils 2.40-2 pn python3.11-doc ii python3.11-venv 3.11.1-2 - -- no debconf information -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCY/uJxjEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3Qr9AQC6ZJlTqYQ02kLfhD2oblIV 2yPkIEDk5Mbqu2pTG/eCbAD+MGLRKuibJkB6EFwcP7O8C6NgV00iGcKxGqzBp/ok IAg= =JbNH -END PGP SIGNATURE-
Bug#1028713: Comment
A stacktrace from the segmentation fault looks like follows.
It triggers consistently for me with the following steps in a source-tree
fakeroot debian/rules binary
cd sample_data/
/tmp/salmon-1.9.0+ds1/obj-x86_64-linux-gnu/src/salmon index -t
transcripts.fasta -i sample_salmon_quasi_index
#0 0x77495993 in __GI__IO_fwrite (buf=0x7fffc978, size=1,
count=82,
fp=0x76060400) at ./libio/iofwrite.c:37
#1 0x5560f55d in spdlog::details::file_helper::write
(this=0x7607f980,
msg=...) at ./include/spdlog/details/../sinks/../details/file_helper.h:90
#2 0x556299dd in
spdlog::sinks::simple_file_sink::_sink_it
(msg=...,
this=0x7607f970) at ./include/spdlog/details/../sinks/file_sinks.h:45
#3 spdlog::sinks::base_sink::log
(this=0x7607f970,
msg=...) at ./include/spdlog/sinks/base_sink.h:37
#4 0x55618aa3 in spdlog::logger::_sink_it
(this=0x76025810, msg=...)
at /usr/include/c++/12/bits/shared_ptr_base.h:1665
#5 0x55a8ae19 in spdlog::logger::log (fmt=0x55cd7f0b
"mphf size = {} MB", lvl=spdlog::level::info, this=0x76025810) at
./external/pufferfish/include/spdlog/details/logger_impl.h:74
#6 spdlog::logger::info (arg1=, fmt=0x55cd7f0b
"mphf size = {} MB", this=0x76025810) at
./external/pufferfish/include/spdlog/details/logger_impl.h:145
#7 pufferfishIndex (indexOpts=...) at
./external/pufferfish/src/PufferfishIndexer.cpp:660
#8 0x556636ae in SalmonIndex::buildPuffIndex_ (idxOpt=...,
indexDir=...,
this=0x7603e280) at ./include/SalmonIndex.hpp:111
#9 SalmonIndex::build (idxOpt=..., indexDir=..., this=0x7603e280) at
./include/SalmonIndex.hpp:76
#10 salmonIndex (argc=, argv=) at
./src/BuildSalmonIndex.cpp:247
#11 0x555fe510 in std::function
>&)>::operator()(int, char const**, std::unique_ptr >&) const (__args#2=std::unique_ptr = {...},
__args#1=, __args#0=, this=0x7604e1a8) at
/usr/include/c++/12/bits/std_function.h:591
#12 main (argc=, argv=0x7fffe028) at ./src/Salmon.cpp:267
Bug#1027305: Bug-Investigation
It seems the module does not yet support Python newer than 3.7 (3.9 in the latest version on Github), see https://github.com/ilius/pyglossary/tree/master/pyglossary/plugin_lib Copying the folder pyglossary/plugin_lib/py37 to py310 and py311 fixes this build-error for me.
Bug#1029076: [pkg-uWSGI-devel] Bug#1029076: Bug#1029076: closed by Jonas Smedegaard (reply to 1029...@bugs.debian.org) (Re: Bug#1029076: uwsgi-plugin-python3: built against non-defaul
> Since this issue only emerges during transitions (and possibly for > downstream derivative distros supporting multiple concurrent Python > versions in their final user-exposed distro releases), this issue is not > considered urgent to fix, and is not planned to do before this upcoming > freeze. So, what about Python 3.11 most likely not going to be the default Python in bookworm? Using your choice of words, bookworm is currently in a transition, and will probably be released with this transition ongoing. So, as I take it, your plan is to live with the issue, even though this means uWSGI's Python 3 support will not be properly usable for third-party applications for a full stable release lifetime? signature.asc Description: PGP signature
Bug#1029076: [pkg-uWSGI-devel] Bug#1029076: closed by Jonas Smedegaard (reply to 1029...@bugs.debian.org) (Re: Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.
Jonas, > If you want me to not share my views here, then I shall stop waste my > time on that. I cannot see where I said, or implied, that I do not want you to share your views here. > If you want to be understood, then I suggest you try elaborate, taking > the views shared by your opponent into account, instead of simply > insisting that what you said initially is the truth and adequate for > understanding your truth. So, how about trying to read my elaborate mail instead of complaining about my style? As often when interacting with you, I have a very strong feeling of rejection, because your biggest interest seems to be educating others on how to interact with you. From my point of view, I do not want you to do anything in particular, I simply want a working Linux distribution with as few bugs as possible, and I always try to assume that this goal is shared among all Debian Developers. -nik signature.asc Description: PGP signature
Bug#991462: Please update etcd to 3.5.5
Hi Thomas, Shengjing, et al, I am currently investigating if, and how, we could get etcd 3.5.7 into Debian bookworm. It is already very short before the freeze, but yet… let's at least discuss it. It looks like Shengjing is working on the package, but recently uploaded 3.4.23. Shengjing, can you provide an update on your plans for bookworm? The Git repository has a version 3.5.5 which according to the changelog should have been uploaded to experimental, where I cannot find it. Thomas, do you remember where this version went? COncerning the reverse dependencies of golang-etcd-server-dev, are there any known incompatibilities that would prevent a move to etcd 3.5.5? Kind regards, Nik signature.asc Description: PGP signature
Bug#1029076: [pkg-uWSGI-devel] Bug#1029076: closed by Jonas Smedegaard (reply to 1029...@bugs.debian.org) (Re: Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.
Hi Jonas, > Please describe what exactly fails, to aid in understanding what we are > talking about and aid in testing. So, consider the following example of how to use uWSGI (it is actually the msot common and basic example, so I would expect you to test it): 1. Create a virtual environment: python3 -m venv /srv/fooenv 2. Install whatever WSGI app you like into the venv → note that at this point, all packages isntalled into the venv will be versioned for python3.10 in testing! 3. Configure a uWSGI app to use the environment (by setting virtualenv = /srv/fooenv and referring to a script exposing a WSGI app there) 4. Start uWSGI → note that at this point, all imports from packages in the venv fail, because the WSGI script is run using Python 3.11 while the venv uses Python 3.10, which is the default Python) -nik signature.asc Description: PGP signature
Bug#1029076: closed by Jonas Smedegaard (reply to 1029...@bugs.debian.org) (Re: Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.11 / should always build agains
> Seems to me you are looking at a policy for Python modules. Yes, as I said. And also as I said, I still think it applies here. -nik signature.asc Description: PGP signature
Bug#1029076: closed by Jonas Smedegaard (reply to 1029...@bugs.debian.org) (Re: Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.11 / should always build agains
I'd say what the Python policy says for modules also applies here: https://www.debian.org/doc/packaging-manuals/python-policy/index.html#dependencies Specificically, dependencies on versioned Python runtime packages are forbidden. As I see it, uwsgi-plugin-python3 needs to build a versioned package against all supported Python versions, and build a meta-package depending on the current default Python version. A less elaborate fix would be adding a dependency on python3 (>= 3.11~), which would prevent migration to testing before the default Python in testing being changed.
Bug#1029076: closed by Jonas Smedegaard (reply to 1029...@bugs.debian.org) (Re: [pkg-uWSGI-devel] Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.11 / should a
Control: reopen -1 > Sorry, but I fail to see any problem here. > > uwsgi _does_ build against the default Python. Yes, but the default Python it builds against in unstable is not necessarily the default Python in testing. Right now, it is built against Python 3.11, while the default Python in testing is 3.10. Hence, it does not work in testing (have you actually tried that after my bug report?).
Bug#1026725: Comment
The next minor version 20.2.0 has this test removed as part of removing support for Python2 and 3.5, see commit https://github.com/hynek/structlog/commit/f65309d4f66fbd44c09288a485107d725c3da1d4#diff-673441c4b6dbee451d8130f1e9bb48f3dbc44d5d3acf1c21d52d0904002342d5 So it might be justified to simply remove or disable this test until the next version-upgrade is done for the package.
Bug#1029077: debian-edu-config: leaks first user password in Debconf answers
Source: debian-edu-config Version: 2.12.25 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 It was discovered that the password for the first user (GOSa); and root user if using the Debian Edu installer, is not cleared from the Debconf answers database. It is also therefore available unencrypted in the system memory on tjener, at least after the first ever debconf run. The database is generally not world-readable, and regular users cannot access arbitrary system memory, so this is not a critical security bug. I still propose to clear the password from the Debconf database "as soon as possible", as per the Debconf Programmer's Tutorial [1]: You should consider clearing that value out of the database as soon as is possible. - -nik [1] http://www.fifi.org/doc/debconf-doc/tutorial.html#AEN34 -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCY8ahVDEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3aIyAQCOlYlZt6REMchQ9DSak5JD 5PmdwnD89Uc0K4U+feDu4QD6A8WwWgnV7ov3VJ0wupphIVopqGcnIxJrZH8LnYaW cAY= =Vrqx -END PGP SIGNATURE-
Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.11 / should always build against the defalt Python in testing
Package: uwsgi-plugin-python3 Version: 2.0.21-3+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: debian-pyt...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Currently, the uWSGI Python 3 plugin is built against Python 3.11, and depends on libpython3.11. This is, to some extent, fine, as Python 3.11 is already in Debian. However, Python 3.10 is still the default Python in bookworm, and as it stands this will not change [1]. In practice, this means that without changing the interpreter and manually ensuring that the Python 3.11 environment is fully available, apps run through uWSGI do not work. So, the uWSGI plugin should in general always build against the default Python IMHO. - -nik [1] https://lists.debian.org/debian-python/2023/01/msg00010.html - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uwsgi-plugin-python3 depends on: ii libc6 2.36-8 ii libpython3.11 3.11.1-2 ii uwsgi-core 2.0.21-3+b1 uwsgi-plugin-python3 recommends no packages. Versions of packages uwsgi-plugin-python3 suggests: pn python3-uwsgidecorators - -- no debconf information -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCY8aedTEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3ZDoAQCYW8oE4ZgiBKkgo1lge2Az 7/qTIXGHgKAAF5kmuGTB5QD+NiuAOboj6I6ZvxRZF4o1D3vXCBr1HkqYz+piZMQO Fgc= =Y+XX -END PGP SIGNATURE-
Bug#1026827: xrdp: initially xrdp worked ok, but later it broke, and the problem was /etc/xrdp/startwm.sh that changed
Control: tags -1 + moreinfo Control: severity -1 normal Hi, > Severity: critical > Justification: breaks the whole system I doubt that very much. Are you sure that the whole system stopped working because you could not start a session in xrdp? As in, no login on the tty possible, the kernel crashing, boot failed, or the like? >* What led up to the situation? What did yo udo *before* the file was renamed? I am pretty certain that this is not something the package did. How is the syste mmanaged? Did the change happen in correlation with a package update? -nik signature.asc Description: PGP signature
Bug#1023680: ITP: django-jsonstore -- Expose JSONField data as a virtual django model fields
Hi, > * License : GPL-3 Please mind that this library is licensed under AGPL. Therefore, we deem it unfit for release in a free software product, and will replace it in AlekSIS. -nik
Bug#1019455: laminard: WebUI of laminar fails because newer incompatible version of Chart.js is included
Package: laminard Version: 1.1-1+b2 Severity: grave Justification: renders package unusable laminar currently uses Chart.js 2.7.2 (also in newer version 1.2 and on latest master) Debian packaging replaces this with the version packaged in Debian, which is 3.9.x curently, the bookworm-package of laminar seems to actually include 3.7.1. Version 2 and 3 of Chart.js are not compatible and thus the WebUI of laminar cannot be used at all! The JavaScript error in Browser-console is "Chart.scaleService is undefined". See https://github.com/ohwgiles/laminar/issues/175 for the related upstream report. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages laminard depends on: ii init-system-helpers 1.64 ii libc62.34-7 ii libcapnp-0.9.1 0.9.1-4+b1 ii libgcc-s112.2.0-1 ii libsqlite3-0 3.39.3-1 ii libstdc++6 12.2.0-1 ii sysuser-helper 1.3.7+really1.4.1 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages laminard recommends: ii daemon 0.8-1 laminard suggests no packages. -- Configuration Files: /etc/laminar.conf changed [not included] -- no debconf information
Bug#1017540: Clarification
The .iso is for the latest debian bullseye, taken from https://cdimage.debian.org/debian-cd/current/i386/iso-dvd/
Bug#1017540: cdimage.debian.org: i386 DVD 1 iso fails to install - md5 file integrity
Package: cdimage.debian.org Severity: normal Tags: ftbfs a11y X-Debbugs-Cc: domin...@organworks.com Dear Maintainer, Attempting an install of .i386 DVD 1 through USB stick, the Install process stops shortly after searching for installation files, bringing up a read error. Running the md5 integrity check will eventually find an error with some file on the system, though the specific file varies on installation attempts. Thus it is not possible to install the .iso. This is despite correct sha256sum checks. A netinst iso is available and works fine, as a temporary workaround.
Bug#1016730: ITP: netbird -- VPN management platform built on top of WireGuard
Package: wnpp Severity: wishlist Owner: Dominik George X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: netbird Version : 0.8.5 Upstream Author : * URL : https://netbird.io/ * License : BSD-3-clause Programming Lang: Go Description : VPN management platform built on top of WireGuard NetBird is an open-source VPN management platform built on top of WireGuard® making it easy to create secure private networks for your organization or home. It requires zero configuration effort leaving behind the hassle of opening ports, complex firewall rules, VPN gateways, and so forth. NetBird creates an overlay peer-to-peer network connecting machines automatically regardless of their location (home, office, datacenter, container, cloud or edge environments) unifying virtual private network management experience. I intend to maintain netbird inside the Go packaging team. -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCYu5UAzEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3X/lAP9wV67BD4AD0G9CDKjzkJyx HFObmtNenmFGmk2C8bNy4wD/cxm+p6/Iq/xaKKxiw9J9goMPsO4o7qQCNC431FZr 3wY= =pDtN -END PGP SIGNATURE-
Bug#1003856: fatal rendering error
Hi Ralph, I cannot reproduce it. Could you provide more information about your Perl installation? best, dominik GPG: 0xB28A0AB9F13EFD61 signature.asc Description: PGP signature
Bug#1014908: ITP: gender-guesser -- Guess the gender from first name
Hi, what practical use, except for direct discriminatory attempts against non-binaries and probably even many cis people, does such a package have? -nik
Bug#1010593: fai-server - fai-diskimage must call losetup -P
Package: fai-server Version: 5.10.3 Followup-For: Bug #1010593 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I can confirm this issue. I cannot find any hints on why and when the behaviour changed, but I had to add -P to losetup today as well to get fai-diskimage back to a working state. - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fai-server depends on: ii debootstrap 1.0.126+nmu1 ii e2fsprogs1.46.5-2 ii fai-client 5.10.3 ii xz-utils 5.2.5-2.1 Versions of packages fai-server recommends: ii dosfstools4.2-1 pn isc-dhcp-server ii libproc-daemon-perl 0.23-2 ii mtools4.0.33-1+really4.0.32-1 ii nfs-kernel-server 1:2.6.1-2 ii openbsd-inetd [inet-superserver] 0.20160825-5 ii openssh-client1:9.0p1-1+b1 ii openssh-server1:9.0p1-1+b1 ii tftpd-hpa 5.2+20150808-1.2 Versions of packages fai-server suggests: ii binutils 2.38.50.20220615-4 pn debmirror ii fai-setup-storage 5.10.3 pn grub2 ii perl-tk1:804.036-1 ii qemu-utils 1:7.0+dfsg-7 pn reprepro ii squashfs-tools 1:4.5.1-1 ii xorriso1.5.4-2 - -- no debconf information -BEGIN PGP SIGNATURE- iL8EARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCYrIvNzEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3evkAPioiwmA7CCgwL9BbOuwLVsc LrRa+9QZnAsGPdxmbdm5AQDunHEtldkdrsRREbixA8yAhH62axYxuKpVJxJKePO4 Dw== =sqlb -END PGP SIGNATURE-
Bug#1011642: fai-client: softupdate should unmount tmpfs on /var/lib/fai
Package: fai-client Version: 5.10.3 Severity: normal When using a remote configspace (using FAI_CONFIG_SRC=https://…/foo.tar.xz), fai softupdate mounts a tmpfs on /var/lib/fai (thanks forthat behaviour, that is really helpful!). This mount is never cleaned up, neither after a successful run nor after a failed run. Even worse, on the next fai softupdate, another tmpfs is mounted at the same location, slowly accumulatiing squillions of mounts on /var/lib/fai… -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/1 CPU thread) Locale: LANG=en_US.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages fai-client depends on: ii debconf-utils1.5.77 ii file 1:5.39-3 ii iproute2 5.10.0-4 ii libapt-pkg-perl 0.1.39 ii libfile-lchown-perl 0.02-2+b7 ii perl 5.32.1-4+deb11u2 ii procps 2:3.3.17-5 Versions of packages fai-client recommends: ii fdisk 2.36.1-8+deb11u1 pn libgraph-perl ii util-linux 2.36.1-8+deb11u1 Versions of packages fai-client suggests: pn logtail -- Configuration Files: /etc/fai/fai.conf changed [not included] -- no debconf information
Bug#1011387: ITP: inkscape-silhouette -- An extension to drive Silhouette vinyl cutters (e.g. Cameo, Portrait series) from within inkscape
Package: wnpp Severity: wishlist Owner: Dominik George X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: inkscape-silhouette Version : 1.25 Upstream Author : Fab Lab Region Nuernberg e. V. * URL : https://github.com/fablabnbg/inkscape-silhouette * License : GPL-2.0+ Programming Lang: Python Description : An extension to drive Silhouette vinyl cutters (e.g. Cameo, Portrait series) from within inkscape inkscape-silhoute is an extension to drive a Silhoutte Cameo and similar plotter devices from within Inkscape. It is 100% pure Python, and works on top of the libusb backend. The folloiwing devices are supported: Silhouette Portrait Silhouette Portrait 2 (working confirmed) Silhouette Portrait 3 Silhouette Cameo Silhouette Cameo 2 Silhouette Cameo 3 Silhouette Cameo 4 Silhouette Cameo 4 Pro Silhouette Curio (partial success confirmed in #36) Craft Robo CC200-20 Craft Robo CC300-20 Silhouette SD 1 Silhouette SD 2 I intend to maintain the package withing the Debian Multimedia Packaing team. -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCYoj8hzEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3XQtAQDAvFmiq7DlhRHnE1sp3vqs k/oarTee00VEqQiXaO98BQD/aFer8iH+x+adpQFYdxReIc8T4idZhv67v5M3arwW DwQ= =99Q0 -END PGP SIGNATURE-
Bug#1010670: libgoogle-gson-java: CVE-2022-25647 Deserialization of Untrusted Data via the writeReplace method
Hi, > Thank you for uploading to old-old-stable [1]. Are you interested in > doing the same for old-stable and stable? (If not, I plan to. I'm > asking only to avoid duplication of effort.) I was actually planning to ask you whether I shall handle that. So if you want, I will take that up as well. Cheers, Nik
Bug#1008772: xrdp: Please integrate NMUs and gitlab MR
Hi, > I have just uploaded an NMU prepared by a Kali contributor (in the NM > queue). Please find the relevant "git am" patches attached. (The two > patches by Arnaud are also in https://salsa.debian.org/arnaudr/xrdp) > > It fixes CVE-2022-23613 and nothing else. Thanks a lot! > I noticed that you have open MR on Gitlab that it would be good to handle. > There's a former NMU that was never acked and that doesn't appear in > debian/changelog. > > https://salsa.debian.org/debian-remote-team/xrdp/-/merge_requests Yep, I am clearly behind on my maintenance work… I am resolving all of that with the next upload based on the current upstream version 0.9.19. -nik signature.asc Description: PGP signature
Bug#940398: RFA: golang-github-nats-io-go-nats
Hi, On Sun, Sep 15, 2019 at 06:38:01PM -0400, Alexandre Viau wrote: > I'd like to find new maintainers for some of my packages because I have > had less time for Debian. I'd like to focus the small amount of time > that I have for Debian on other things. > > For now, I intend to do my best to keep maintaining this package. > However, I will probably retitle this bug with the 'O:' prefix at some > point, indicating that I have orphaned it. > > Feel free to upload a new version of the package and remove me from the > uploaders in debian/control. On Mon, Jun 22, 2020 at 01:53:45PM +0200, Badreddin Aboubakr wrote: > I would like to take the maintainership for the NATS packages. I am currently working on packaging nextcloud-spreed-signaling, which depends on NATS. It seems the pckage has by now been renamed to nats.go and has go.mod support. SO I would package the new package in the Go packaging team under the new name, and then file a removal request for this package. Any objections? Cheers, Nik signature.asc Description: PGP signature
Bug#1001224: amavisd-new: Amavis database corrupted infrequently - Suicide in child_init_hook: BDB can't connect db env
Package: amavisd-new Version: 1:2.11.1-5 Severity: important Dear Maintainer, after upgrading to bullseye, I see a database corruption every few days, rendering amavis unusable until the database is built up again. To recover from the error, something like this is needed: service amavis stop mv /var/lib/amavis/db /var/lib/amavis/db~ mkdir /var/lib/amavis/db chown amavis:amavis /var/lib/amavis/db chmod o-rx /var/lib/amavis/db service amavis start Unfortunatelly, I'm not able to tell the exact trigger for the database corruption. Maybe it is related to the system being somewhat memory limited, which sometimes leads to swapping and slow processing times. In one thread, switching to a redis database is recommended: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214218 The logs look for examlple like this: Dec 6 13:35:53 emailserver amavis[1559665]: (1559665-02-7) (!!)TROUBLE in check_mail, but must continue (1): update_snmp FAILED: update_snmp_variables: BDB S db_cursor: BDB0061 PANIC: Das Argument ist ungültig, . at (eval 91) l ine 107. Dec 6 13:35:53 emailserver amavis[1559664]: (1559664-03-2) (!!)TROUBLE in check_mail, but must continue (1): update_snmp FAILED: update_snmp_variables: BDB S c_get: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 140. Dec 6 13:35:53 emailserver amavis[1559665]: (1559665-02-7) (!!)TROUBLE in process_request: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 220. Dec 6 13:35:53 emailserver amavis[1559665]: (1559665-02-7) (!)Requesting process rundown after fatal error Dec 6 13:35:53 emailserver amavis[1559664]: (1559664-03-2) (!!)TROUBLE in process_request: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 220. Dec 6 13:35:53 emailserver amavis[1559664]: (1559664-03-2) (!)Requesting process rundown after fatal error Dec 6 13:35:54 emailserver amavis[1559665]: (1559665-02-7) (!)TempDir removal: tempdir is to be PRESERVED: /var/lib/amavis/tmp/amavis-20211206T132604-1559665-foq2xpsA Dec 6 13:35:56 emailserver amavisd-new[1559665]: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 220. Dec 6 13:35:56 emailserver amavis[1559665]: (1559665-02-7) (!)_DIE: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 220. Dec 6 13:35:56 emailserver amavisd-new[1559664]: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 220. Dec 6 13:35:56 emailserver amavis[1559665]: (1559665-02-7) (!)Amavis::END: DB unregistering failed: Dec 6 13:35:56 emailserver amavis[1559664]: (1559664-03-2) (!)TempDir removal: tempdir is to be PRESERVED: /var/lib/amavis/tmp/amavis-20211206T132604-1559664-xiTb_xfl Dec 6 13:35:56 emailserver amavis[1559664]: (1559664-03-2) (!)_DIE: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 91) line 220. Dec 6 13:35:57 emailserver amavis[1559664]: (1559664-03-2) (!)Amavis::END: DB unregistering failed: Dec 6 13:36:47 emailserver amavis[1559785]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. Dec 6 13:36:47 emailserver amavisd-new[1559785]: Suicide in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. Dec 6 13:36:48 emailserver amavisd-new[1559786]: Suicide in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. Dec 6 13:36:48 emailserver amavis[1559786]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. Dec 6 13:36:48 emailserver amavis[1559785]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. Dec 6 13:36:48 emailserver amavis[1559786]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. Dec 6 13:42:40 emailserver amavis[1559809]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/lib/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 91) line 338. These TROUBLE / _DIE messages continue until the database is
Bug#999519: xrayutilities: diff for NMU version 1.7.1-2.1
Dear Debian team, I think the patch can be used like this. I'll also release a new upstream version with this patch hopefully today. kind regards Dominik On Tue, Nov 23, 2021 at 2:48 AM Stefano Rivera wrote: > Control: tags 999519 + patch > Control: tags 999519 + pending > > Dear maintainer, > > I've prepared an NMU for xrayutilities (versioned as 1.7.1-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. > > Also filed as: > https://salsa.debian.org/science-team/python-xrayutilities/-/merge_requests/1 > > Regards, > > SR >
Bug#998388: Acknowledgement (openresolv: resolvconf fails if called from openvpn during system start with "kill: Operation not permitted")
I just checked. Giving the permission for kill CAP_KILL in /lib/systemd/system/openvpn-client@.service resolves the problem. But besides kill there are other ways to see if a process exists e.g. ps -o pid= -p However, by replaing the relevant line in /sbin/resolvconf still resulted in the error message. Regards Dominik
Bug#998388: openresolv: resolvconf fails if called from openvpn during system start with "kill: Operation not permitted"
Package: openresolv Version: 3.12.0-1 Severity: normal X-Debbugs-Cc: dr896...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade from debian 10 to debian 11 resolvconf is called during startup from an openvpn service, but fails with the message openvpn[4511]: /sbin/resolvconf: 31: kill: Operation not permitted openvpn[4020]: WARNING: Failed running command (--up/--down): external program exited with error status: 1 openvpn[4020]: Exiting due to fatal error Thus, the openvpn connection is not started. restarting the service with openvpn-client@example will bring up openvpn It seems, that this is related to the capabilities of openvpn, when run as a service https://forums.openvpn.net/viewtopic.php?f=4=24993=14319b7b38867b271a0cb1ac09c994ea=20 the only line in resolvconf that uses kill is line 874 if $have_pid && ! kill -0 "$pid"; then * What exactly did you do (or not do) that was effective (or ineffective)? booting the system, where openvpn-client@example has been enabled as service * What was the outcome of this action? openvpn is not started because of the failure in resolvconf * What outcome did you expect instead? working openvpn connection *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) 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 -- no debconf information
Bug#947771: unbound: cannot restart daemon under sysvinit-core when apparmor is enforced
Followup-For: Bug #947771 Package: unbound Version: 1.13.1-1 On Thu, 28 Jan 2021 02:19:05 +0800 Gedalya wrote: --- unbound.init 2020-12-24 00:34:24.0 + +++ /etc/init.d/unbound 2021-01-27 18:15:25.663526469 + @@ -42,7 +42,7 @@ stop) log_daemon_msg "Stopping $DESC" "$NAME" - if start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE --name $NAME --retry 5; then + if start-stop-daemon --stop --quiet --oknodo --remove-pidfile --pidfile $PIDFILE --name $NAME --retry 5; then $HELPER resolvconf_stop $HELPER chroot_teardown log_end_msg 0 @@ -53,7 +53,7 @@ restart|force-reload) log_daemon_msg "Restarting $DESC" "$NAME" - start-stop-daemon --stop --quiet --pidfile $PIDFILE --name $NAME --retry 5 + start-stop-daemon --stop --quiet --remove-pidfile --pidfile $PIDFILE --name $NAME --retry 5 $HELPER resolvconf_stop if start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE --name $NAME --startas $DAEMON -- $DAEMON_OPTS; then $HELPER chroot_setup This works perfectly and should be accepted.
Bug#995958: ITP: aleksis-core -- Free School Information System (Core)
Package: wnpp Severity: wishlist Owner: Dominik George X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: aleksis-core Version : 2.0 Upstream Author : The AlekSIS Team * URL : https://aleksis.org/ * License : EUPL-1.2 Programming Lang: Python Description : Free School Information System (Core) AlekSIS is a web-based school information system (SIS) which can be used to manage and/or publish organisational subjects of educational institutions. . AlekSIS is a platform based on Django, that provides central funstions and data structures that can be used by apps that are developed and provided seperately. The AlekSIS team also maintains a set of official apps which make AlekSIS a fully-featured software solutions for the information management needs of schools. . By design, the platform can be used by schools to write their own apps for specific needs they face, also in coding classes. Students are empowered to create real-world applications that bring direct value to their environment. The package shall be maintained within the Debian Edu Packaging Team, which intends to ship it with the Debian Edu Pure Blend as management console. -BEGIN PGP SIGNATURE- iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCYWDL/DEaaHR0cHM6Ly93 d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3XskAP4m42U+GZlTQI0rN2P/p+5z 2xR38ENk6OOUM6eNSiTpRwD/dKU6WmXb4LCKbOdg4xWne5FoozOeNjUp9ibI1OpO Ugs= =ON11 -END PGP SIGNATURE-
Bug#995893: python3-django-uwsgi-ng: should install .egg-info alias for django-uwsgi
Package: python3-django-uwsgi-ng Version: 1.1.2-1 Severity: important Tags: newcomer The new django-uwsgi-ng package is a drop-in replacement for django-uwsgi, and some dependent packages using it might rely on it being findable as django-uwsgi through pkg_resources as well. Thus, the .egg-info directory should be duplicated, to ensure the package can be found under the old name in Python.
Bug#995874: tipp10: The Configuration directory includes an advertisement
Package: tipp10 Version: 2.1.0-5 Severity: normal X-Debbugs-Cc: domi...@unix-ag.org Dear Maintainer, 1. Tipp10 10 Crashes on first start, because of missing config file. 2. After killing the tipp10 process you can start the application, but you have now an advertisement to "~/.config/Tom Thielicke IT Solutions$" in your home, what is against the debian rules. -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tipp10 depends on: ii libc62.31-13 ii libgcc-s110.2.1-6 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5multimedia55.15.2-3 ii libqt5printsupport5 5.15.2+dfsg-9 ii libqt5sql5 5.15.2+dfsg-9 ii libqt5sql5-sqlite5.15.2+dfsg-9 ii libqt5widgets5 5.15.2+dfsg-9 ii libstdc++6 10.2.1-6 tipp10 recommends no packages. tipp10 suggests no packages.
Bug#995840: ITP: golang-github-vmware-vmw-ovflib --
Package: wnpp Severity: wishlist Owner: Dominik George * Package name: golang-github-vmware-vmw-ovflib Version : 0.0~git20200204.53a0e9f-1 Upstream Author : VMware, Inc. * URL : https://github.com/vmware/vmw-ovflib * License : Apache-2.0 Programming Lang: Go Description : parse OVF (open Virtualization Format) data in Go Needed for ignition.
Bug#972409: spdx-licenses diff for #972409
> Sorry, I never had the impression that you meant for our conversation to > be kept secret - only that you found it a more convenient platform. Aren't you the person signing all their mail with explicit consent? Considering that, I find it hard to believe that you don't know the concept of explicit consent to publication of written words. I would welcome it very much if we could get back to technical discussions and, if asked a simple question via a Medium you officially promote on your website, you give a simple answer in the future. I don't think that that is too much to ask for in a setting where everyone donates their free time and not want to waste time writing full blown mails to everyone and there dog for a quick question no one will care about later. While you are technically correct on this issue, I consider it socially inadequate to not point me to the issue you knew of very well when you had the chance. Maybe if we can agree that there are more helpful ways to interact right from the start, we could find a way forward in the other bug report -nik
Bug#972409: spdx-licenses diff for #972409
Hi Jonas, > For the record this conversation began in a Matrix chatroom like this: Thanks for sharing conversations I did not consent to make public to a public forum. I will seek legal advice on that. For the record: * I asked on Matrix to get a quick "Go" or "Stop", no more, no less. You refused to give me a quick answer, which would have been helpful, instead of asking me to waste time on a far more elaborate means of communication for a quick question no one else cares about * I did ask the same question by mail after you refused to give a simple answer. You chose not to respond to that either. A quick "Stop, you will need to fix the other bug first" would have been helpful, instead of waiting until I wasted hours of work on your package Now, never mind, I will not waste more time on your package. I will just make a new package for my needs, and if anyone asks why we need two, I will point them to this conversation. Thanks for being such a pedantic^Wvery helpful fellow contributor! -nik
Bug#972409: spdx-licenses diff for #972409
> Sorry, but I consider the NMU as drafted useless since it does not > account for release-critical bug#975120. Thanks for your kind words. As can be seen by the fact that we are communicating in this bug report, my question for feedback is about this bug, not some other bugs. Looking at the Maintainer field of the package, it also seems this is **your** package. If it is a requirement to solve all issues with your package to get a single bug fixed, then sorry, I find that unacceptable. If "useless" is everything you have to say about the work of a contributor, then please reconsider your involvement in a community of developers. Are you able to provide feedback concerning the questions at hand, on top of judging the work I do because you ignored it for several years? Thanks, Nik
Bug#972409: spdx-licenses diff for #972409
Hi, the attached diff to the dbeian/ directory adds the RDF/Turtle, RDF/XML, and JSON formatted files to the package. The package is not ready to upload yet, because I need to align d/copyright with the new upstream verison. Please note that in order to keep the file list in d/install maintainable, I chose to change from explicitly listing each file there to installing the full directories. The intention of listing the single files was to not install any license texts missing in d/copyright, which IMHO is wrong because d/copyright is about the source package, rather than the binary package. So I removed the general wildcard from d/copyright, so that now we can rely on lintian reporting missing files: W: spdx-licenses source: file-without-copyright-information debian/copyright text/389-exception.txt W: spdx-licenses source: file-without-copyright-information debian/copyright text/AAL.txt W: spdx-licenses source: file-without-copyright-information debian/copyright text/ANTLR-PD-fallback.txt W: spdx-licenses source: file-without-copyright-information debian/copyright text/ANTLR-PD.txt […] Before I get down to updating d/copyright (quite a few additions upstream…), I ask the maintainer to approve of the changes to how the package is built. -nik diff -Npru spdx-licenses-3.8+dfsg/debian/README.Debian spdx-licenses-3.14+dfsg/debian/README.Debian --- spdx-licenses-3.8+dfsg/debian/README.Debian 1970-01-01 01:00:00.0 +0100 +++ spdx-licenses-3.14+dfsg/debian/README.Debian 2021-10-05 13:50:46.395165638 +0200 @@ -0,0 +1,5 @@ +The Debian version of the JSON format files has the detailsUrl field +changed to point to the relative paths within the Debian package. The +original values are linking to https://spdx.org/licenses/*.json. + + -- Dominik George , Tue, 5 Oct 2021 13:50:46 +0200 diff -Npru spdx-licenses-3.8+dfsg/debian/changelog spdx-licenses-3.14+dfsg/debian/changelog --- spdx-licenses-3.8+dfsg/debian/changelog 2021-04-07 09:12:25.0 +0200 +++ spdx-licenses-3.14+dfsg/debian/changelog 2021-10-05 14:18:31.688460612 +0200 @@ -1,3 +1,19 @@ +spdx-licenses (3.14+dfsg-0.1) unstable; urgency=medium + + * Non-maintainer upload. + * Include JSON and RDF formats. (Closes: #972409) ++ Rework d/install and d/copyright to ease tracking of + license files; i.e. install by glob, and remove wildcard + from d/copyright to make lintian complain on new files + instead of tracking each file in d/install. ++ Add README.Debian describing differences in the data + files in Debian. ++ Build-Depend on jq and xml-twig-tools to rebuild compiled + license files for JSON and RDF formats. + * Align d/watch with new GitHub tag URLs. + + -- Dominik George Tue, 05 Oct 2021 13:29:29 +0200 + spdx-licenses (3.8+dfsg-3) unstable; urgency=medium * friendly takeover; diff -Npru spdx-licenses-3.8+dfsg/debian/control spdx-licenses-3.14+dfsg/debian/control --- spdx-licenses-3.8+dfsg/debian/control 2021-04-07 09:09:38.0 +0200 +++ spdx-licenses-3.14+dfsg/debian/control 2021-10-05 14:15:23.946432016 +0200 @@ -2,7 +2,10 @@ Source: spdx-licenses Section: doc Priority: optional Maintainer: Jonas Smedegaard -Build-Depends: debhelper-compat (= 12) +Build-Depends: + debhelper-compat (= 12), + jq, + xml-twig-tools Standards-Version: 4.5.0 Vcs-Browser: https://github.com/Debian/spdx-licenses Vcs-Git: https://github.com/Debian/spdx-licenses.git @@ -18,4 +21,7 @@ Description: Collection of license data and provided by SPDX Workgroup, a Linux Foundaition Project. This package makes most of these license texts available to Debian systems. . + In addition to the license texts, the collection data ist supplied in + JSON and RDF formats. + . Note: License texts have NOT been evaluated against DFSG. diff -Npru spdx-licenses-3.8+dfsg/debian/copyright spdx-licenses-3.14+dfsg/debian/copyright --- spdx-licenses-3.8+dfsg/debian/copyright 2020-12-05 03:33:11.0 +0100 +++ spdx-licenses-3.14+dfsg/debian/copyright 2021-10-05 14:03:05.842506105 +0200 @@ -2,87 +2,99 @@ Format: https://www.debian.org/doc/packa Upstream-Name: license-list-data Upstream-Contact: https://github.com/spdx/license-list-data/issues Source: https://github.com/spdx/license-list-data -Files-Excluded: website template html json jsonld rd* - -Files: * +Files-Excluded: website template html jsonld rdfa rdfnt + rdfturtle/licenses.turtle + rdfxml/licenses.rdf + +Files: CONTRIBUTING.md + README.md + accessingLicenses.md + licenses.md + json/exceptions.json + json/licenses.json Copyright: 2020 SPDX Workgroup 2016 Gary O'Neall License: CC-BY-3.0 Files: debian/* Copyright: 2020 Michael Lustfield + 2021 Dominik George License: CC-BY-3.0 -Files: text/0BSD.txt +Files: json/exceptions/* +License: none +Comment: Used in combination with licenses + +Files: */0BSD.* Copyright: 2006 Rob Landley License: none -Files: text/Abstyles.txt +Files: */Abstyles.* Copyright: 1991, 1992 Hans-Hermann
Bug#995767: ITP: golang-github-pin-tftp -- TFTP server and client library for Golang
Package: wnpp Severity: wishlist Owner: Dominik George * Package name: golang-github-pin-tftp Version : 2.2.0-1 Upstream Author : Dmitri Popov * URL : https://github.com/pin/tftp * License : Expat Programming Lang: Go Description : TFTP server and client library for Golang TFTP server and client library for Golang . Implements: * RFC 1350 (https://tools.ietf.org/html/rfc1350) - The TFTP Protocol (Revision 2) * RFC 2347 (https://tools.ietf.org/html/rfc2347) - TFTP Option Extension * RFC 2348 (https://tools.ietf.org/html/rfc2348) - TFTP Blocksize Option . Partially implements (tsize server side only): * RFC 2349 (https://tools.ietf.org/html/rfc2349) - TFTP Timeout Interval and Transfer Size Options . Set of features is sufficient for PXE boot support. Needed for the ignition package.
Bug#995766: ITP: golang-github-vincent-petithory-dataurl -- Data URL Schemes in Golang
Package: wnpp Severity: wishlist Owner: Dominik George * Package name: golang-github-vincent-petithory-dataurl Version : 0.0~git20191104.d1553a7-1 Upstream Author : Vincent Petithory * URL : https://github.com/vincent-petithory/dataurl * License : Expat Programming Lang: Go Description : Data URL Schemes in Golang This package parses and generates Data URL Schemes for the Go language, according to RFC 2397 (http://tools.ietf.org/html/rfc2397). . Data URLs are small chunks of data commonly used in browsers to display inline data, typically like small images, or when you use the FileReader API of the browser. Needed for the ignition package.
Bug#995765: ITP: golang-github-coreos-vcontext -- A library for validating json and yaml configs in Go
Package: wnpp Severity: wishlist Owner: Dominik George * Package name: golang-github-coreos-vcontext Version : 0.0~git20210903.c22998b-1 Upstream Author : CoreOS * URL : https://github.com/coreos/vcontext * License : Apache-2.0 Programming Lang: Go Description : A library for validating json and yaml configs in Go vcontext: Validation with context vcontext is a library supporting validation of config files parsed from yaml or json with support for giving context as to where errors occur. Needed for the ignition package.
Bug#995764: ITP: ignition -- First boot installer and configuration tool
Package: wnpp Severity: wishlist Owner: Dominik George * Package name: ignition Version : 2.12.0-1 Upstream Author : CoreOS * URL : https://github.com/coreos/ignition * License : Apache-2.0 Programming Lang: Go Description : First boot installer and configuration tool Ignition is the utility used by Fedora CoreOS and RHEL CoreOS to manipulate disks during the initramfs. This includes partitioning disks, formatting partitions, writing files (regular files, systemd units, etc.), and configuring users. On first boot, Ignition reads its configuration from a source of truth (remote URL, network metadata service, hypervisor bridge, etc.) and applies the configuration. Usage Odds are good that you don't want to invoke Ignition directly. In fact, it isn't even present in the root filesystem. Take a look at the Getting Started Guide (docs/getting-started.md) for details on providing Ignition with a runtime configuration.
Bug#995763: ITP: golang-github-coreos-go-json -- Modified version of go's encoding/json library which allows decoding to a Node struct with offset information
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-coreos-go-json
Version : 0.0~git20200220.5ae6071-1
Upstream Author : CoreOS
* URL : https://github.com/coreos/go-json
* License : TODO
Programming Lang: Go
Description : Modified version of go's encoding/json library which allows
decoding to a Node struct with offset information
This is a fork of go's encoding/json library. It adds the a third target for
unmarshalling, json.Node.
Unmarshalling to a Node behaves similarilarly to unmarshalling to an
interface{}, except it also records
the offsets for the start and end of the value that was unmarshalled and, if
the value was part of a json
object, it also records the offsets of the start and end of the object's key.
The Value field of the Node
will be unmarshalled to the same types as if it were an interface{}, except in
the case of arrays and
objects. In those case it will be unmarshalled to a []Node or map[string]Node
instead []interface{} or
map[string]interface{} for arrays and objects, respectively.
(Maybe) needed for ignition, but clarifying upstream whether this fork is
really still needed.
Bug#995762: ITP: golang-github-vmware-vmw-guestinfo --
Package: wnpp Severity: wishlist Owner: Dominik George * Package name: golang-github-vmware-vmw-guestinfo Version : 0.0~git20200218.687661b-1 Upstream Author : VMware * URL : https://github.com/vmware/vmw-guestinfo * License : Apache-2.0 Programming Lang: Go Description : provides access to the guestinfo variables exposed to a VMware virtual machine. Needed for the ignition package.
Bug#995758: ITS: move to the Python Packaging Team
Source: pyrhon-requests-oauthlib Version: 1.3.0+ds-0.1 Severity: important X-Debbugs-Cc: Simon Fondrie-Teitler , Debian Python Team Hi, I would like to salvage this package, and doing so, move it under team maintenance by the Python Packaging Team. Reasons for salvaging eligibility: * The last upload by the maintainer was in June 2018, more than three years ago * An NMU from September 2019 went unacknowledged for two years * Upstream versions were pending for more than three years * The package was broken by the upload of python-oauthlib 3.0.0 in September 2019, which would have been fixed by a new upstream version of python-requests-oauthlib I will move the package to the Python Packaging Team starting in 21 days, as per the Salvaging policy, keeping the original maintainer as Uploader. Cheers, Nik
Bug#995702: TypeError: Cannot read property 'prefix_exceptions' of undefined
Control: reassign -1 node-caniuse-lite 1.0.30001224+dfsg-2 Control: retitle -1 Broken exports in index.js Control: affects -1 node-autoprefixer Control: tags -1 + upstream fixed-upstream Control: forwarded -1 https://github.com/browserslist/caniuse-lite/issues/70 > Proposal: > > 1. Add a patch to node-autoprefixer to use the old API > 2. Add a version constraint to the node-caniuse-lite dependency in > node-autoprefixer (<< 1.0.30001226~) > 3. Report a bug against node-caniuse-lite to update to the current > upstream version, with a gentle hint on what will break if updated > 4. Once updated, drop the patch, and remove the version constraint Actually, all rdepends seem to use another import mechanism, which was not broken. Thus, reassigning to node-caniuse-lite to get it updated. -nik signature.asc Description: PGP signature
Bug#995702: TypeError: Cannot read property 'prefix_exceptions' of undefined
> - let autoprefixerData = { browsers: agents, prefixes: dataPrefixes }
> + let autoprefixerData = { browsers: agents.agents, prefixes: dataPrefixes }
It's
https://github.com/browserslist/caniuse-lite/commit/fde289588b2ccb129ba3d1552134be2c78fee8b7
So, this happened with a recent update of node-autoprefixer, because
the new autoprefixer relies on the new API of caniuse-lite.
caniuse-lite should, and will at some point, be updated in Debian as
well. However, this will break node-browserslist, because that relies
on the old API. Oh the joy!
Proposal:
1. Add a patch to node-autoprefixer to use the old API
2. Add a version constraint to the node-caniuse-lite dependency in
node-autoprefixer (<< 1.0.30001226~)
3. Report a bug against node-caniuse-lite to update to the current
upstream version, with a gentle hint on what will break if updated
4. Once updated, drop the patch, and remove the version constraint
@ JavaScript team, shall I proceed with that?
-nik
signature.asc
Description: PGP signature
Bug#995702: TypeError: Cannot read property 'prefix_exceptions' of undefined
Package: node-autoprefixer
Version: 10.3.1.0+dfsg1+~cs14.6.19-1
Severity: grave
Justification: renders package unusable
autoprefixer currently does not work because it handles the agents
imported from caniuse-lite wrongly:
/usr/share/nodejs/autoprefixer/lib/browsers.js:64
let prefix = data.prefix_exceptions && data.prefix_exceptions[version]
^
TypeError: Cannot read property 'prefix_exceptions' of undefined
at Browsers.prefix (/usr/share/nodejs/autoprefixer/lib/browsers.js:64:23)
at /usr/share/nodejs/autoprefixer/lib/prefixes.js:193:54
at Array.map ()
at Prefixes.select (/usr/share/nodejs/autoprefixer/lib/prefixes.js:193:31)
at new Prefixes (/usr/share/nodejs/autoprefixer/lib/prefixes.js:133:53)
at loadPrefixes
(/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:111:22)
at Object.prepare
(/usr/share/nodejs/autoprefixer/lib/autoprefixer.js:121:22)
at /usr/share/nodejs/postcss/lib/lazy-result.js:133:39
at Array.map ()
at new LazyResult (/usr/share/nodejs/postcss/lib/lazy-result.js:131:43)
The problem comes from /usr/share/nodejs/autoprefixer/lib/autoprefixer.js:
let { agents } = require('caniuse-lite')
The object loaded here contains another object called agents. For me, changing
line 10
fixes the issue:
- let autoprefixerData = { browsers: agents, prefixes: dataPrefixes }
+ let autoprefixerData = { browsers: agents.agents, prefixes: dataPrefixes }
I have no idea how this problem came to be, and how to properly fix it. Might be
an incompatibility between the versions of autoprefixer and canisue-lite?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8),
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages node-autoprefixer depends on:
ii node-browserslist 4.17.0+~cs5.6.76-1
ii node-caniuse-lite 1.0.30001224+dfsg-2
ii node-normalize-range 0.1.2-2
ii node-postcss [node-colorette] 8.2.1+~cs5.3.23-8
ii node-postcss-value-parser 4.1.0-2
ii nodejs 12.22.5~dfsg-5
node-autoprefixer recommends no packages.
node-autoprefixer suggests no packages.
-- no debconf information
Bug#995417: bug is RC
Control: severity -1 grave This is actually an RC bug as the requests-oauthlib version currently in Debian does not work with the oauthlib version currently in Debian. signature.asc Description: PGP signature
Bug#995417: python-requests-oauthlib: please update to current upstream version 1.3.0
Source: python-requests-oauthlib Version: 1.0.0-1.1 Severity: wishlist Please update this package to the current upstream version. I would also like to suggest moving this to team maintenance under the Python Packaging team. Thanks, Nik -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#995398: RM: midori -- ROM; upstream made software unusable
Package: ftp.debian.org Severity: normal As reported in #977263, the upstream of midori decided that it could be a great idea to write a web browser in JavaScript running in a browser (i.e. use Electron to run a browser). I follow the proposal in the aforementioned bug report and ask to remove Midori from the unstable distribution.
Bug#995363: python-jwcrypto: do not drop egg-info
Source: python-jwcrypto Version: 1.0.0-1 Severity: important Trying to build a package depending on python3-jwcrypto, I discovered that you explicitly drop the egg-info file from the package. Please do not do that, as it breaks Python's pkg_resources and related when discovering distributions.
Bug#994983: clamav-daemon: Postinst script assumes /var/lib/clamav/ to be writable, which is not always the case
Package: clamav-daemon Version: 0.103.3+dfsg-0+deb10u1 Severity: normal Tags: patch Dear Maintainer, in order to limit network bandwith and harddisk capacity, we use a setup with shared virus patterns. For this, the directory /var/lib/clamav is shared by multiple systems, only the master system (responsible for pattern update) having write access. This breaks the post-install process: clamav-daemon (0.103.3+dfsg-0+deb10u1) wird eingerichtet ... /var/lib/dpkg/info/clamav-daemon.postinst: 464: /var/lib/dpkg/info/clamav-daemon.postinst: cannot create /var/lib/clamav/clamav.conf: Permission denied dpkg: Fehler beim Bearbeiten des Paketes clamav-daemon (--configure): »installiertes clamav-daemon-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück Fehler traten auf beim Bearbeiten von: clamav-daemon Which we can fix by modifying /var/lib/dpkg/info/clamav-daemon.postinst sudo patch --forward /var/lib/dpkg/info/clamav-daemon.postinst << EOF --- /tmp/clamav-daemon.postinst 2021-05-21 12:53:07.386753639 +0200 +++ /tmp/clamav-daemon.postinst.new 2021-05-21 12:53:48.410539251 +0200 @@ -264,11 +264,11 @@ configure) # The DEB*FILE files are used temporarily during the update of the CLAMAV* files. - DEBCONFFILE=/var/lib/clamav/clamav.conf + DEBCONFFILE=/tmp/clamav.conf CLAMAVCONF=/etc/clamav/clamd.conf - DEBROTATEFILE=/var/lib/clamav/clamdrotate.debconf + DEBROTATEFILE=/tmp/clamdrotate.debconf CLAMAVROTATEFILE=/etc/logrotate.d/clamav-daemon - DEBSYSTEMDCLAMDCONF=/var/lib/clamav/extend.conf + DEBSYSTEMDCLAMDCONF=/tmp/extend.conf CLAMAVSYSTEMDCLAMDONF=/etc/systemd/system/clamav-daemon.service.d/extend.conf # Update the configuration file EOF sudo apt -y install --fix-broken Please consider not to use /var/lib/clamav/ as temporary location to generate configuration files. -- Package-specific info: --- configuration --- Checking configuration files in /etc/clamav Config file: clamd.conf --- AlertExceedsMax disabled PreludeEnable disabled PreludeAnalyzerName = "ClamAV" LogFile = "/var/log/clamav/clamav.log" LogFileUnlock disabled LogFileMaxSize = "4294967295" LogTime = "yes" LogClean disabled LogSyslog disabled LogFacility = "LOG_LOCAL6" LogVerbose disabled LogRotate = "yes" ExtendedDetectionInfo = "yes" PidFile disabled TemporaryDirectory disabled DatabaseDirectory = "/var/lib/clamav" OfficialDatabaseOnly disabled LocalSocket = "/var/run/clamav/clamd.ctl" LocalSocketGroup = "clamav" LocalSocketMode = "666" FixStaleSocket = "yes" TCPSocket disabled TCPAddr disabled MaxConnectionQueueLength = "15" StreamMaxLength = "26214400" StreamMinPort = "1024" StreamMaxPort = "2048" MaxThreads = "12" ReadTimeout = "180" CommandReadTimeout = "30" SendBufTimeout = "200" MaxQueue = "100" IdleTimeout = "30" ExcludePath = "/initrd.img", "/vmlinuz" MaxDirectoryRecursion = "25" FollowDirectorySymlinks disabled FollowFileSymlinks disabled CrossFilesystems = "yes" SelfCheck = "3600" ConcurrentDatabaseReload = "yes" DisableCache disabled VirusEvent disabled ExitOnOOM disabled AllowAllMatchScan = "yes" Foreground disabled Debug disabled LeaveTemporaryFiles disabled User = "clamav" Bytecode = "yes" BytecodeSecurity = "TrustSigned" BytecodeTimeout = "6" BytecodeUnsigned disabled BytecodeMode = "Auto" DetectPUA disabled ExcludePUA disabled IncludePUA disabled ScanPE = "yes" ScanELF = "yes" ScanMail = "yes" ScanPartialMessages disabled PhishingSignatures = "yes" PhishingScanURLs = "yes" HeuristicAlerts = "yes" HeuristicScanPrecedence disabled StructuredDataDetection disabled StructuredMinCreditCardCount = "3" StructuredMinSSNCount = "3" StructuredSSNFormatNormal = "yes" StructuredSSNFormatStripped disabled ScanHTML = "yes" ScanOLE2 = "yes" AlertBrokenExecutables disabled AlertBrokenMedia disabled AlertEncrypted disabled StructuredCCOnly disabled AlertEncryptedArchive disabled AlertEncryptedDoc disabled AlertOLE2Macros disabled AlertPhishingSSLMismatch disabled AlertPhishingCloak disabled AlertPartitionIntersection disabled ScanPDF = "yes" ScanSWF = "yes" ScanXMLDOCS = "yes" ScanHWP3 = "yes" ScanArchive = "yes" ForceToDisk disabled MaxScanTime = "12" MaxScanSize = "104857600" MaxFileSize = "26214400" MaxRecursion = "16" MaxFiles = "1" MaxEmbeddedPE = "10485760" MaxHTMLNormalize = "10485760" MaxHTMLNoTags = "2097152" MaxScriptNormalize = "5242880" MaxZipTypeRcg = "1048576" MaxPartitions = "50" MaxIconsPE = "100" MaxRecHWP3 = "16" PCREMatchLimit = "1" PCRERecMatchLimit = "5000" PCREMaxFileSize = "26214400" OnAccessMountPath disabled OnAccessIncludePath disabled OnAccessExcludePath disabled OnAccessExcludeRootUID disabled OnAccessExcludeUID disabled OnAccessExcludeUname disabled OnAccessMaxFileSize = "5242880" OnAccessDisableDDD disabled OnAccessPrevention disabled OnAccessExtraScanning disabled OnAccessCurlTimeout = "5000" OnAccessMaxThreads = "5" OnAccessRetryAttempts disabled OnAccessDenyOnError disabled DevACOnly disabled DevACDepth
Bug#993988: debian-edu-config: consider to drop diskless workstation support as default for Main-Server+LTSP-Server profile
Hi, > Like reported in #993935, a local admin might install additional > packages on a combined server causing potential leakage of sensible data > in the SquashFS image file for diskless workstations. > > It would be quite easy to drop the diskless workstation support (done by > default at first boot of a combined server), only provide thin client > support on the combined server and leave the (site specific) setup for > diskless ws to the local admin. (The manual should then contain hints > how to do this.) I take it that by "drop support", you mean "not install by default"? Diskless workstations are one (probably the) Unique Selling Point of Debian Edu, so I would like to make very clear that dropping support for it in general would be problematic. -nik -- Dominik George (1. Vorstandsvorsitzender, pädagogischer Leiter) Teckids e.V. — Digitale Freiheit mit Jugend und Bildung https://www.teckids.org/ signature.asc Description: PGP signature
Bug#993935: debian-edu-ltsp-install: Netboot image exposes private data and crypto keys
Package: debian-edu-config Version: 2.11.56 Severity: critical Tags: security Justification: root security hole X-Debbugs-Cc: Debian Security Team The LTSP netboot image produced by debian-edu-ltsp-install includes full copies of files that should never leave the Debian Edu main server, if run on a so-called "combined server" (a system using the Main Server and Terminal Server profiles, as done in small installations). Among these files are full copies of, among others: - /var/lib/ldap, containing the full, unencrypted LDAP database with all private information on all users, password hashes, and Kerberos keys - /etc/krb5-kdc, containing information on decrypting Kerberos data in the LDAP database - /etc/gosa, containing the (encrypted) LDAP manager credentials, plus the key to decrypt it Any user with access to the local terminal server network can acquire the netboot image, unauthenticated, and extract the listed information from it. The issue is caused by the new LTSP system using the LTSP PnP system now in all cases, thus packing the entire mai nserver filesystem in squashfs image. The debian-edu-ltsp-install script produces a list of files to exclude from the image, which is not sufficient, most probably because it was tailored to the use case where the image is produced from a dedicated Terminal Server instead of a combined server. IMHO, the use case of the combined server cannot be fixed. The new LTSP system de facto disallows any use of a combiend server – even if we make a very carefully curated list of excluded files, any administrator would have to take care to add their own excludes for just about any file they place on the main server that was not palced there by the Debian Edu software. In fact, the whole new LTSP system seems unfit to be used on any server that is not limited to producing LTSP images, and supporting netbooting them. For now, the issue should be mitigated by carefully adding all relevant paths that are known to exist only on the main server to the exclude list, but I do not think that is a viable fix in the long term.
Bug#991920: Acknowledgement (please demote pkg-config to Recommends)
On Thu, Aug 05, 2021 at 10:21:30PM +0200, Michael Banck wrote: > I've run "dracut --no-kernel" in a minimal lxc container, once with > pkg-config and once without and then diffoscope'd the two generated > initrds. Most of what diffoscope complains about are timestamp > differences in directories and symlinks which I don't know how to get > rid of, but there's some changes in etc/conf.d/systemd.conf that I have > attached. Not sure whether those are problematic? Given that /usr/lib is the canonical path for these directories, and /lib happens to be a symlink there, this should not be a problem. If Thomas consents, I would make the change in experimental as well and we will see how it works out. I do not see any reason not to demote pkg-config. Cheers, Nik -- Dominik George Berater PostgreSQL / Datenbanken Telefon: +49 2166 9901-192 Telefax: +49 2166 9901-100 E-Mail: dominik.geo...@credativ.de PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 https://www.credativ.de/ credativ GmbH, HRB Mönchengladbach 12080 USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Sascha Heuer, Geoff Richardson, Peter Lilley Unser Umgang mit personenbezogenen Daten unterliegt folgenden Bestimmungen: https://www.credativ.de/datenschutz
Bug#991918: dracut: new upstream version 055
Source: dracut
Version: 051
Severity: minor
Tags: patch
Hi Thomas, et al,
the attached debdiff updates the debian/ directory to work with
upstream version 055.
Thanks to Andre Russ for preparing the patch updates; thanks to
credativ for sponsoring Debian work!
Thomas, if you are ok, I would upload to experimental.
Cheers,
Nik
diff -Nru dracut-051/debian/changelog dracut-055/debian/changelog
--- dracut-051/debian/changelog 2020-12-15 16:23:33.0 +0100
+++ dracut-055/debian/changelog 2021-08-05 13:31:22.0 +0200
@@ -1,3 +1,20 @@
+dracut (055-1) UNRELEASED; urgency=medium
+
+ [ Dominik George ]
+ * Team upload.
+ * New upstream version
+
+ [ Andre Russ ]
+ * Refresh patches for dracut 055
++ systemd needs more users in Debian
++ crc32c patch was applied upstream
++ several minor changes
+ * Update installed files
++ Several docs were moved upstream
++ mkinitrd was removed
+
+ -- Dominik George Thu, 05 Aug 2021 13:31:22 +0200
+
dracut (051-1) unstable; urgency=low
* new upstream version
diff -Nru dracut-051/debian/dracut-core.docs dracut-055/debian/dracut-core.docs
--- dracut-051/debian/dracut-core.docs 2020-12-15 15:29:17.0 +0100
+++ dracut-055/debian/dracut-core.docs 2021-08-05 13:31:22.0 +0200
@@ -1,10 +1,8 @@
AUTHORS
-HACKING
-NEWS
+docs/HACKING.md
+NEWS.md
README.md
-README.cross
-README.generic
-README.kernel
-README.modules
-TODO
+docs/README.cross
+docs/README.generic
+docs/README.kernel
dracut.html
diff -Nru dracut-051/debian/dracut-core.install
dracut-055/debian/dracut-core.install
--- dracut-051/debian/dracut-core.install 2020-12-15 15:29:17.0
+0100
+++ dracut-055/debian/dracut-core.install 2021-08-05 13:31:22.0
+0200
@@ -1,6 +1,5 @@
usr/bin/dracut
usr/bin/dracut-catimages
-usr/bin/mkinitrd
usr/bin/lsinitrd
usr/lib/dracut/dracut-functions
usr/lib/dracut/dracut-functions.sh
@@ -19,7 +18,6 @@
debian/90overlay-root usr/lib/dracut/modules.d
modules.d/00dash usr/lib/dracut/modules.d
modules.d/00bash usr/lib/dracut/modules.d
-modules.d/00bootchart usr/lib/dracut/modules.d
modules.d/00systemdusr/lib/dracut/modules.d
modules.d/01fips usr/lib/dracut/modules.d
modules.d/01systemd-initrd usr/lib/dracut/modules.d
diff -Nru dracut-051/debian/dracut-core.manpages
dracut-055/debian/dracut-core.manpages
--- dracut-051/debian/dracut-core.manpages 2020-12-15 15:29:17.0
+0100
+++ dracut-055/debian/dracut-core.manpages 2021-08-05 13:31:22.0
+0200
@@ -1,9 +1,8 @@
-dracut.8
-dracut.conf.5
-dracut.modules.7
-dracut.bootup.7
-dracut.cmdline.7
-dracut-catimages.8
-lsinitrd.1
-mkinitrd.8
+man/dracut.8
+man/dracut.conf.5
+man/dracut.modules.7
+man/dracut.bootup.7
+man/dracut.cmdline.7
+man/dracut-catimages.8
+man/lsinitrd.1
debian/tmp/usr/share/man/man8/*
diff -Nru dracut-051/debian/dracut-network.install
dracut-055/debian/dracut-network.install
--- dracut-051/debian/dracut-network.install2020-12-15 15:29:17.0
+0100
+++ dracut-055/debian/dracut-network.install2021-08-05 13:31:22.0
+0200
@@ -1,5 +1,5 @@
debian/etc/11-ifcfg.conf etc/dracut.conf.d
-modules.d/02systemd-networkd usr/lib/dracut/modules.d
+modules.d/01systemd-networkd usr/lib/dracut/modules.d
modules.d/35network-manager usr/lib/dracut/modules.d
modules.d/35network-legacy usr/lib/dracut/modules.d
modules.d/40networkusr/lib/dracut/modules.d
diff -Nru dracut-051/debian/patches/crc32c dracut-055/debian/patches/crc32c
--- dracut-051/debian/patches/crc32c2020-12-15 15:29:17.0 +0100
+++ dracut-055/debian/patches/crc32c1970-01-01 01:00:00.0 +0100
@@ -1,11 +0,0 @@
a/modules.d/99fs-lib/module-setup.sh
-+++ b/modules.d/99fs-lib/module-setup.sh
-@@ -38,7 +38,7 @@
- include_fs_helper_modules() {
- local dev=$1 fs=$2
- case "$fs" in
--xfs|btrfs|ext4)
-+xfs|btrfs|ext4|ext3)
- instmods crc32c
- ;;
- f2fs)
diff -Nru dracut-051/debian/patches/dev-shm-mount
dracut-055/debian/patches/dev-shm-mount
--- dracut-051/debian/patches/dev-shm-mount 2020-12-15 15:29:17.0
+0100
+++ dracut-055/debian/patches/dev-shm-mount 2021-08-05 13:31:22.0
+0200
@@ -1,14 +1,14 @@
--- a/modules.d/99base/init.sh
+++ b/modules.d/99base/init.sh
-@@ -57,11 +57,6 @@
- mount -t devpts -o gid=5,mode=620,noexec,nosuid devpts /dev/pts >/dev/null
+@@ -55,11 +55,6 @@
+ mount -t devpts -o gid=5,mode=620,noexec,nosuid devpts /dev/pts >
/dev/null
fi
-if ! ismounted /dev/shm; then
--mkdir -m 0755 /dev/shm
--mount -t tmpfs -o mode=1777,noexec,nosuid,nodev,strictatime tmpfs
/dev/shm >/dev/null
+-mkdir -m 0755 -p /dev/shm
+-mount -t tmpfs -o mode=1777,noexec,nosuid,nodev,strictatime tmpfs
/dev/shm > /dev/null
-fi
-
if ! ismounted /run; then
- mkdir -m 0755 /newrun
+ mkdir -m 0755 -p /newrun
Bug#990518: apt: 'apt install ./.deb' segfaults if a malformed .list file exists
Package: apt
Version: 2.2.4
Severity: normal
Dear Maintainer,
having a single malformed .list file lets 'apt install ./.deb'
segfault
e.g. having 'foo' in /etc/apt/sources.list.d/test.list
maybe related to #792088, #977041 though the stack traces are different
stacktrace:
---
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
pkgSourceList::GetVolatileFiles (this=this@entry=0x0) at
../apt-pkg/sourcelist.cc:532
532return VolatileFiles;
#0 pkgSourceList::GetVolatileFiles (this=this@entry=0x0) at
../apt-pkg/sourcelist.cc:532
#1 0x77f75a35 in AddIfVolatile (SL=0x0, VolatileCmdL=std::vector of
length 0, capacity 0, Add=0x77f77f20 >&)>,
I=0x7fffedaf "./test.deb", pseudoArch="") at
../apt-private/private-install.cc:760
#2 0x77f76e5f in operator() (I=, __closure=) at ../apt-private/private-install.cc:803
#3 __gnu_cxx::__ops::_Iter_pred&),
const string&):: >::operator()
(__it=0x55576b58, this=) at
/usr/include/c++/10/bits/predefined_ops.h:316
#4 std::__find_if&), const
string&):: > > (__pred=..., __last=,
__first=0x55576b58) at /usr/include/c++/10/bits/stl_algobase.h:1954
#5 std::__find_if&), const
string&):: > > (__pred=..., __last=,
__first=) at /usr/include/c++/10/bits/stl_algobase.h:1974
#6 std::__remove_if&), const
string&):: > > (__pred=..., __last=,
__first=) at /usr/include/c++/10/bits/stl_algo.h:836
#7 std::remove_if&),
const string&):: > (__pred=..., __last=,
__first=) at /usr/include/c++/10/bits/stl_algo.h:914
#8 GetPseudoPackages (SL=0x0, CmdL=..., Add=0x77f77f20
>&)>, pseudoArch="") at
../apt-private/private-install.cc:802
#9 0x77f7d818 in DoInstall (CmdL=...) at include/apt-pkg/cachefile.h:76
#10 0x77e28667 in CommandLine::DispatchArg
(this=this@entry=0x7fffe9e0, Map=,
NoMatch=NoMatch@entry=true) at ../apt-pkg/contrib/cmndline.cc:369
#11 0x77f6a0d3 in DispatchCommandLine (CmdL=..., Cmds=std::vector of
length 31, capacity 32 = {...}) at ../apt-private/private-cmndline.cc:586
#12 0x6296 in main (argc=3, argv=0x7fffeb48) at
../cmdline/apt.cc:120
#0 pkgSourceList::GetVolatileFiles (this=this@entry=0x0) at
../apt-pkg/sourcelist.cc:532
No locals.
#1 0x77f75a35 in AddIfVolatile (SL=0x0, VolatileCmdL=std::vector of
length 0, capacity 0, Add=0x77f77f20 >&)>,
I=0x7fffedaf "./test.deb", pseudoArch="") at
../apt-private/private-install.cc:760
pkg = {name =
"\220\017XUUU\000\000\000QZUUU\000\000\000\000\000\000\000\000\000\000\240\017XUUU\000\000p\321^UUU\000\000\b\000\000\000\000\000\000\000BASE_URI\000y\000\000\000\000\000\000p\377WUUU\000\000\063\000\000\000\000\000\000\000\063\000\000\000\000\000\000\000\220\tXUUU\000\000p\000\000\000\000\000\000\000\321\000\000\000\000\000\000\000\060\326_UUU\000\000\240\374\266\367\377\177\000\000\000\000\000\000\000\000\000\000\020\345\\UUU\000\000\060\333\\UUU",
'\000' ,
"P\000\000\000\000\000\000\000\200\000\000\000\000\000\000\000
\235WUUU\000\000"..., arch = , release = '\000' ,
"`\357WUUU\000\000`\357WUUU\000\000\000\000\000\000\000\000\000\000\003\000\000\000\000\000\000\000\240\357WUUU\000\000\341\000\000\000\000\000\000\000P\347WUUU\000\000\020\240\000\000\300\355WUUU",
'\000' , "\001", '\000' , "\001", '\000'
..., index = 93824992407024}
#2 0x77f76e5f in operator() (I=, __closure=) at ../apt-private/private-install.cc:803
SL =
VolatileCmdL =
Add =
pseudoArch =
#3 __gnu_cxx::__ops::_Iter_pred&),
const string&):: >::operator()
(__it=0x55576b58, this=) at
/usr/include/c++/10/bits/predefined_ops.h:316
No locals.
#4 std::__find_if&), const
string&):: > > (__pred=..., __last=,
__first=0x55576b58) at /usr/include/c++/10/bits/stl_algobase.h:1954
__trip_count =
__trip_count =
#5 std::__find_if&), const
string&):: > > (__pred=..., __last=,
__first=) at /usr/include/c++/10/bits/stl_algobase.h:1974
No locals.
#6 std::__remove_if&), const
string&):: > > (__pred=..., __last=,
__first=) at /usr/include/c++/10/bits/stl_algo.h:836
__result =
__result =
#7 std::remove_if&),
const string&):: > (__pred=..., __last=,
__first=) at /usr/include/c++/10/bits/stl_algo.h:914
No locals.
#8 GetPseudoPackages (SL=0x0, CmdL=..., Add=0x77f77f20
>&)>, pseudoArch="") at
../apt-private/private-install.cc:802
VolatileCmdL = std::vector of length 0, capacity 0
#9 0x77f7d818 in DoInstall (CmdL=...) at include/apt-pkg/cachefile.h:76
Cache = { = {_vptr.pkgCacheFile = 0x77fbfd90 , d = 0x55576b10, ExternOwner = false, Map = 0x0, Cache =
0x0, DCache = 0x0, SrcList = 0x0, Policy = 0x0}, UniverseList = std::vector of
length 0, capacity 0}
VolatileCmdL = std::vector of length 0, capacity 0
verset = std::map with 0 elements
UnknownPackages = std::set
Bug#937234: pam-python: Python2 removal in sid/bullseye
Hi, > I wonder what the state of this issue is. > > I looked at the code and somehow it has a few hints on (at least > partial?) Python 3 compatibility. > > Russell, can you give me a short update on how far this got? Can we > somehow get to the goal of making this fully work with Python 3? Maybe > even for bullseye… Never mind, I just realised that pam-python is licensed under AGPL and is thus not suitable for Debian Edu IMHO. @Mike, @Petter: Did you realise that pam-python is AGPL? It means that we cannot provide terminal servers or netbooting in Debian Edu without placing a prominent link to pam-python's sources on the desktop… @Russell: Can you please relicence pam-python under a less insane licence? If the latter fails, we should either rewrite such a module under a less restrictie licence, or rewrite libpam-mklocaluser in C or Rust, or get rid of the need for libpam-mklocaluser (probably by using sssd). Looking forward to everyone's thoughts, Nik
Bug#937234: pam-python: Python2 removal in sid/bullseye
Hi, I wonder what the state of this issue is. I looked at the code and somehow it has a few hints on (at least partial?) Python 3 compatibility. Russell, can you give me a short update on how far this got? Can we somehow get to the goal of making this fully work with Python 3? Maybe even for bullseye… It seems I completely missed that Python 2 is still in bullseye, and spent the last few hours writing a new PAM module in Python, and used Python 3 features all over the place with the assumption that Python 2 is gone, then I found that libpam-python is linked against libpython2.7. If there is some kind of to-do list with open points to make it use Python 3, I will see whether I can help. It would be very sad if I had to backport my module to Python 2 for bullseye… Cheers, Nik signature.asc Description: PGP signature
Bug#956118: pianobar FTCBFS: uses the build architecture pkg-config
Hello Helmut, I just came across your patch and applied it upstream as commit 4b45e043aa6371edc2808bb52f6c86910fa0ea47. Cheers, Lars
Bug#971842: [Pkg-clamav-devel] Bug#971842: clamav-daemon erroneously reports "Failed with result 'timeout'" when stopped
Dear Sebastian, sorry for the late reply most likely, the daemon is swapped out. We are talking about a memory restricted system with the obligation to run daily scans on the file system. It seems that running clamdscan with the daemon is still faster while scanning the major part of the file system, compared to running clamscan, even if the daemon uses some swap space. Obviously, this setup is not optimal. I looked into running clamdscan against a service on a different system in the same network, but this seems not to be supported out of the box. Would it hurt to increase the timeout or make it adjustable? Dominik Am Mi., 20. Jan. 2021 um 08:05 Uhr schrieb Dominik Reusser < dr896...@gmail.com>: > > > Dear Sebastian, > > most likely, the daemon is swapped out. We are talking about a memory > restricted system with the obligation to run daily scans on the file > system. It seems that running clamdscan with the daemon is still faster > while scanning the major part of the file system, compared to running > clamscan, even if the daemon uses some swap space. > > Obviously, this setup is not optimal. I looked into running clamdscan > against a service on a different system in the same network, but this seems > not to be supported out of the box. > > Would it hurt to increase the timeout or make it adjustable? > > Dominik > > >
Bug#980287: ITP: python-telethon -- asyncio Python 3 MTProto library
Package: wnpp Severity: wishlist Owner: Dominik George X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-telethon Version : 1.19.0 Upstream Author : Lonami Exo * URL : https://github.com/LonamiWebs/Telethon * License : MIT Programming Lang: Python Description : asyncio Python 3 MTProto library Telethon is an asyncio Python 3 MTProto library to interact with Telegram's API as a user or through a bot account (bot API alternative). It is needed for the matrix-telegram bridge, and I intend to maintain it within the Python packaging team. -BEGIN PGP SIGNATURE- iQJ+BAEBCgBoFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAmAEGhIxGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxgcbmF0dXJl c2hhZG93QGRlYmlhbi5vcmcACgkQt5o8FqDE8paEMBAAtXnCL6kJDvDSgcIEDG30 53Vaaa2e9DpI56u/cLyvc31gAw+33ooyIDiR9qxhVpsN50DpqQc7UYqEEImSj8Ik 9RjnsUhr/ZSE+R+D5mIvnVW779xMlHepBfxrV+1giKvdI8ufG94eOHCjEq80CgfF J9RgqR6/bg2ocExmTGN76y43QZL/FpZyfnM4dvS6s5wBIb31ZdhikL6FxuafJOeY vB+cm0aeIKaEK2IXoqi/upoZIZPqLgXtD1NMnMhYeye3bjy2Srcw3eL8paM9m3Nr l5IWRkF9F0d8IGR7i53BJj9KWhREurqF4bbmkdgTWNnBdaoUbQTV4gJ+Aov0uQCB XwOB8W+7fqPm4VRQt/rj30sGunQgPe2CGTNuJvRss/BnTWkw8NIpbOk/ms+X+Mld xjBzvksnNZ3xVfA0odzgdg8yUpHMEvBLudisgQq363uimJe8almTFkseysBsBvA+ +Raz8vvvphAFbKHC2KHDVeHHnphCdvfyRhY3QcsebhXOnwtrump+nVAORLyYfJqn J+ii90otMjPbUHVIonRng4yxfZC2etJxIjwOXs/0gqKlTUd04Ul+b0AJbcc+DScY 17i2qgVDBztMB7eKcnzI86PwA7HntQHnH/wwjDg+ZTh2h6EOwdPPeqE1WjV2TGcH sFnaMAcGlRKFGV2MGHGx63I= =E9Tb -END PGP SIGNATURE-
Bug#980286: RFP: signald -- A daemon that facilitates communication via Signal Private Messenger
Package: wnpp Severity: wishlist X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: signald Version : 0.11.1 Upstream Author : Finn Herzfeld * URL : https://gitlab.com/signald/signald * License : GPL Programming Lang: Java Description : A daemon that facilitates communication via Signal Private Messenger signald is needed for mautrix-signal, the Matrix to Signal bridge, which I intend to package. -BEGIN PGP SIGNATURE- iQJ+BAEBCgBoFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAmAEF4cxGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxgcbmF0dXJl c2hhZG93QGRlYmlhbi5vcmcACgkQt5o8FqDE8pbOtQ//VIIw3d2WuiClPHthWPsE hhKA4Y+Za9YBHuUZGdRjMwjxABovM+xyZxVTnUPiEGGQQKWfctne7NqQnzfsqXrh 2l1i6ZS8HHcyuouRHjjw2NVRsVDxu9cCwsEPcEtKgVxCb3e5Ktn6+YwwwBeMjNZk HFUb3qL8DD220gin8SZgK0YDxUg3VV1YWCkHbm4iTZ5Esh1j1ioYuQOYu0JScUW4 l6HVvydPWV+H2Ab+dqvkiFIsd0pS2RgyZ3bDdpG2SL++XN4F7edznqB1YR1V85w/ 9L4Aq0l6P7j/m7yMUdp5nJsWq2EcDNK4SrXqR9ISiYM4aedlhomXC2lqVDqIcqf8 begby2PeC3fOmy2GyD4JbxjDfs29+qW6krs2OPvsMzN4jpoi2mlAaSQoruxXdPXG jv75XuoJtxV6MX/ijGoZADcriZKHkwvD2eUFOmnJsH9AoIxgTk6LDHDJ557XQwY5 N8ywcBkXxCPQ2Lia9WzmE6WQJrZ6fc78rkiGEMGqMYWKICyJZGudYBGuA/kc5IFI nzomrjMn//BDY2Mwxtmj7vao5vvmzrt2gw19KkIlCmdv+xgzlPZmgzq7zOgYGoO3 J+BodntYvL8aauvY8gtXKcu3wEKmtolK8ZeuEm5cDUoptf08R88IFm2QsxmzQeau 7y7eiirgCrNzO0YL97oyhaI= =RA69 -END PGP SIGNATURE-
Bug#978201: Add link to upstream patch/commit
The necessary fix seems to be at https://github.com/crossbario/autobahn-cpp/commit/eac22bd61117ac18b5efee3c6da16a97835055de, applying this fixes building the package.
Bug#977988: /usr/bin/spectacle: does not start (libkImageAnnotator.so.0.3.2 not found)
Package: kde-spectacle Version: 20.12.0-1 Severity: grave File: /usr/bin/spectacle Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After a recent update, spectacle stoppede working, and errors out on start with: spectacle: error while loading shared libraries: libkImageAnnotator.so.0.3.2: cannot open shared object file: No such file or directory Maybe it needs a binNMU? - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kde-spectacle depends on: ii kio5.77.0-2 ii libc6 2.31-6 ii libkf5configcore5 5.77.0-2 ii libkf5configgui5 5.77.0-2 ii libkf5configwidgets5 5.77.0-2 ii libkf5coreaddons5 5.77.0-2 ii libkf5dbusaddons5 5.77.0-2 ii libkf5globalaccel-bin 5.77.0-2 ii libkf5globalaccel5 5.77.0-2 ii libkf5i18n55.77.0-2 ii libkf5kiocore5 5.77.0-2 ii libkf5kiogui5 5.77.0-2 ii libkf5kiowidgets5 5.77.0-2 ii libkf5kipi32.0.0 4:20.08.0-1 ii libkf5newstuff55.77.0-3 ii libkf5notifications5 5.77.0-2 ii libkf5purpose-bin 5.77.0-2 ii libkf5purpose5 5.77.0-2 ii libkf5service-bin 5.77.0-2 ii libkf5service5 5.77.0-2 ii libkf5waylandclient5 4:5.77.0-2 ii libkf5widgetsaddons5 5.77.0-4 ii libkf5windowsystem55.77.0-2 ii libkf5xmlgui5 5.77.0-2 ii libkimageannotator00.4.0-1 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus55.15.2+dfsg-2 ii libqt5gui5 5.15.2+dfsg-2 ii libqt5printsupport55.15.2+dfsg-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libqt5x11extras5 5.15.2-2 ii libstdc++6 10.2.1-1 ii libxcb-cursor0 0.1.1-4 ii libxcb-image0 0.4.0-1+b3 ii libxcb-util1 0.4.0-1+b1 ii libxcb-xfixes0 1.14-2 ii libxcb11.14-2 ii qdbus-qt5 5.15.2-3 kde-spectacle recommends no packages. kde-spectacle suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJ+BAEBCgBoFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl/jtdYxGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxgcbmF0dXJl c2hhZG93QGRlYmlhbi5vcmcACgkQt5o8FqDE8pavGQ/+LbBxRuQdz7GeHZabCmTo GlYBc/60XxcqG7y1SIJdkuxPKoLz5TJrG+87Qy2U6O701g+CIgWCEUhrGWjnXuEC E2uRQj66m2R9UbIz7s4mgEV9fxfZVZwwQafEH1RXXuvWkSbaslVQuNTbgC1P5zaw C5YFNtiLuN3BAlJSa3lAi0hZUnD5+KcTzxWYKNKq2fCKd8Wex/tAd+YAeD623htS OR/CwklxtUrtPPCapMPWBhMzk5dvWpunD4A7j1WF3nptkKA2nk+Jio1qbbqUwlW/ ha/p6LByqwT9CRI4JAyFxwy62nOP1pVfraaOrB9/7fxABJmxsS0wNNUL0Hxsx5we NSO80AqM34JwRp5ho7f4ZKn9jviAIr7UvInUo46Ng3RjX8hRRw04Y/R43lv+vYQD aq2gts5t+MQB2HwM+p+4Qz/6Vn+xwkQSh4reQixIo2UoSjNsyMc0GstDzdB8ZHyc ulyFA0FEvz4AoJiSDCRuJ6tgVXqP4EI2DkdDck4H31bt7WZwYOV5MJzX93U9QXyd pt0Q8Aav4ya+A3lfRjwAvCPpDqH8PgiT5XLLF/rUB2W7z50MNO3LonJKz2UGxtgu TvzHNDPosEx0BnbX5Li0u8OgRHizttC23IbR9hld4A0o8C/iz07IbMSP8nqED6CT gNlsZMEbF2LYl9GutLcbq44= =KbJh -END PGP SIGNATURE-
Bug#976234: RM: jerry -- ROM; outdated and not maintained
Package: ftp.debian.org Severity: normal Source: jerry Version: 3.1.0-1 Outdated (version 3.1.0) and no longer maintained. Has build errors (cf. bug #974583). Latest version 4.0 uses Java and several maven-dependencies, for which no debian packages exist. For me as the maintainer, this is a too complex task. thanks - Dominik
Bug#974989: [Freedombox-pkg-team] Bug#974989: freedombox: firstboot wizard fails in connection setup (KeyError: 'box_name')
Tags: -1 + l10n > > The first boot wizard got as far as setting up the connection, and > > when asked how my router is set up, I chose I do not want to set it up > > right now. That caused the following exception: > > Just to rule out one cause of error. Did you select a langauge? > Perhaps one of the languages have a bug in a format string? Yep, forcing my browser to prioritise English fixes it. In other words, the nb_NO locale is broken. Thanks for the pointer! -nik
Bug#974989: [Freedombox-pkg-team] Bug#974989: freedombox: firstboot wizard fails in connection setup (KeyError: 'box_name')
Hi, > > The first boot wizard got as far as setting up the connection, and > > when asked how my router is set up, I chose I do not want to set it up > > right now. That caused the following exception: > > Just to rule out one cause of error. Did you select a langauge? > Perhaps one of the languages have a bug in a format string? Not actively — it might use my browser language, which is a language that shouldn't come as a surpris eto you however ;). Will check. -nik
Bug#974989: freedombox: firstboot wizard fails in connection setup (KeyError: 'box_name')
Package: freedombox Version: 20.18 Severity: normal I installed the freedombox package on a pretty much vanilla Debian installation. The first boot wizard got as far as setting up the connection, and when asked how my router is set up, I chose I do not want to set it up right now. That caused the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 145, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 143, in _get_response response = response.render() File "/usr/lib/python3/dist-packages/django/template/response.py", line 106, in render self.content = self.rendered_content File "/usr/lib/python3/dist-packages/django/template/response.py", line 83, in rendered_content content = template.render(context, self._request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 171, in render return self._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 987, in render output = self.filter_expression.resolve(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 698, in resolve new_obj = func(obj, *arg_vals) File "/usr/lib/python3/dist-packages/bootstrapform/templatetags/bootstrap.py", line 14, in bootstrap return render(element, markup_classes) File "/usr/lib/python3/dist-packages/bootstrapform/templatetags/bootstrap.py", line 85, in render return template.render(context) File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 171, in render return self._render(context)
Bug#973310: RM: osmalchemy -- ROM; Abandoned upstream, no rdeps
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I am both upstream an maintainer of OSMAlchemy, and OSMAlchemy never got any traction and was only used in one project (which now uses other mechanisms). I therefore request removal. - -nik -BEGIN PGP SIGNATURE- iQJ+BAEBCgBoFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl+ZmHQxGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxgcbmF0dXJl c2hhZG93QGRlYmlhbi5vcmcACgkQt5o8FqDE8pZIaQ/9Fg/ef1/LZXuQ44W08l5F jCi4C/jzvVdb/v4MsaTfEX+uiBvqMq+mx55ylAQ+d+kPuNznRGvY6lY+hMy5UUHH E7DgZZ3pjmoDWS0N06uqzVdyepg7hv5oYKFf0yHsQ/NbXYTRYj98QZRx5grfxXoF rJ1R5GV+O3+/rEO6Ps4XK8px+HUJL8FdU9FM5UN0mBTH5lGJSuRU7dApHAk8M0ma r/F8Odn36BF4ia4iQXZbFL/e9u5IENhKNIiMYW79YJ9uTHDpPZXQaZI29YGJaq+Y HiJihncX5d3urNkRsxcArV60CwfUpq0w8aciFnEGdubp3Ru8zWzy6Z3jDm0AEMqp shgTfQuLLfpRwJQ2wG49CWQjQYhvs/ycqrCj5qAyW88K9rSDrjOgcRE3L9te0EEg dr+MdKixzYTiX99y9noHJUsqbzD91r8rkhDWu2fzpFlm1JeH+qpM5D9eUEarOBbB 0CHircKr6j111eKK/kNYQdfvT765c3GQTGY5qi1nvoHF/sRXS+RNkzgqM/vkSF0T qlIM/ae/Y3yiFxZWzoQfF5wdWDAuN1h+QFVDFNCa1LLUiImODwVmF+TNBKF/7w8l sU5x2eQTIrAT6IaLErhrnPMlVk1Yo9xudtxRjHqxVaLctU6Fnia7sSwhmnVG0Lbx oAm1EbLcxdwOoYATOnv4Uz0= =bdVe -END PGP SIGNATURE-
