Bug#1025455: libssh-dev: DSA support is disabled by default
Hello Vagrant, CC'ing the upstream maintainers, in case I speak nonsense here. Vagrant Cascadian [2022-12-04 16:45 -0800]: > In libssh 0.10.x versions, DSA support is deprecated and disabled by > default. This was indeed intended [1]. > This causes test suite failures when building guile-ssh which > tests support for DSA keys. > > The attached patch enables DSA support, as was supported in previous > versions. > -DEB_CMAKE_EXTRA_FLAGS := -DBUILD_STATIC_LIB=ON > -DLIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH) -DUNIT_TESTING=$(if $(filter > nocheck,$(DEB_BUILD_OPTIONS)),OFF,ON) -DWITH_GSSAPI=ON > +DEB_CMAKE_EXTRA_FLAGS := -DBUILD_STATIC_LIB=ON > -DLIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH) -DUNIT_TESTING=$(if $(filter > nocheck,$(DEB_BUILD_OPTIONS)),OFF,ON) -DWITH_GSSAPI=ON -DWITH_DSA=ON > If that is not an option in time for bookworm freeze, please let me know > ASAP so I can patch guile-ssh instead. If at all possible, I'd rather not enable it in the Debian package. DSA isn't an acceptable crypt algorithm any more, and I'd rather not support it for another Debian release. OpenSSH deprecated it two years ago [2], the Fedora package does not enable it either [3], and libssh upstream will remove it in the next major version. Can guile-ssh be built easily without DSA support? If so, that'd be great (and then let's reassign or just close this bug). Otherwise I can have a look and help you with disabling the DSA feature in guile. Thanks, Martin [1] https://www.libssh.org/2022/08/26/libssh-0-10-0/ [2] http://www.openssh.com/legacy.html [3] https://src.fedoraproject.org/rpms/libssh/blob/rawhide/f/libssh.spec#_74 signature.asc Description: PGP signature
Bug#671828: xmedcon: Cannot open file with YBR photometric interpretation
Hi, On Sun, Dec 4, 2022 at 10:29 AM Andreas Tille wrote: > could you confirm that this bug persists or whether we can close > this bug report. > 671828#15 > The graphical interface shows a black square in place of the > image. I guess not
Bug#617342: 32-bit multiframe image conversion ignores frames
Control: tags -1 confirmed upstream On Sun, Dec 4, 2022 at 10:28 AM Andreas Tille wrote: > could you confirm that this bug persists or whether we can close > this bug report. > 617342#86 > Unfortunately we don't have the resources right now to address problems that > primarily affect users outside of our own institution. I recommend trying the > excellent "dcm2nii" converter instead, to see if that works with your data. I guess not...
Bug#728569: Add PixelMed SCP
Hi, On Sun, Dec 4, 2022 at 10:30 AM Andreas Tille wrote: > I admit I have no idea how to solve this issue. Could you provide > some more information or close this bug if the problem does not > persist any more? dcmtk provides a DICOM SCP which is nicely setup for users. There is also a DICOM SCP in pixelmed which is not setup properly (top of my head).
Bug#749783: gdcm: Conflicting declarations of jpeg_memory_mgr may lead to invalid function calls
On Sun, Dec 4, 2022 at 11:21 AM Andreas Tille wrote: > > Hi, > > when checking old bug reports I'd like to verify whether this issue > persists. I admit I do not even understand the problem of this report > so I'd like to ask the reporter as well as upstream to provide some > input what should be done with this report. >From top of my head this is one of those -Wodr warnings in GCC. I'll have a look asap (jpeg 8 vs 12 vs 16 API).
Bug#1000104: inspircd: depends on obsolete pcre3 library
If you want to fix this on InspIRCd v3 there is a backported module in inspircd-contrib for PCRE2 which can be installed with `./modulemanager install m_regex_pcre2`. This module uses the same internal name so it can be used on the same network as a server using m_regex_pcre. Alternately, you can just ship a different regex backend instead. I'd personally recommend m_regex_stdlib as that requires no dependencies other than a C++11 compiler. ~ Sadie
Bug#982384: [Help] Bug 982384: Warnings profile count data file not found
Hi Nilesh, Am Sun, Dec 04, 2022 at 06:23:13PM -0500 schrieb Aaron M. Ucko: > Andreas Tille writes: > > > Could anybody comment on it / fix it? > > Per > https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fprofile-use: > > Before you can use this option, you must first generate profiling > information. See Instrumentation Options, for information about the > -fprofile-generate option. > > It may be simplest to drop the option, particularly if cross compilation > is otherwise possible. Since git blames you about last changes on the lines with the option in question could you please comment about this? Kind regards Andreas. -- http://fam-tille.de
Bug#991060: reopen for bullseye
Hi, Le 04/12/2022 à 20:51, Santiago Vila a écrit : Please, let us fix this for stable. I would gladly backport the fix from unstable but since the fix was included in a new upstream release I'm in doubt about what would have to be done and would definitely need help. Did you try the supplied patch? Cheers, -- Stéphane
Bug#891197: Please switch to pcre2
Hi Aaron, Am Sun, Dec 04, 2022 at 06:20:15PM -0500 schrieb Aaron M. Ucko: > Andreas Tille writes: > > > it would be great if you could use your upstream contact to convince > > them to switch to pcre2. > > Upstream explicitly passed on pcre2 a few years ago, but times have > changed; I've opened an internal ticket to revisit the question. Finally it seems to boil down to change four files of real code $ grep -Rl pcre | grep -v -e util/regexp -e cmake -e Manifest -e '\.txt' -e config -e pbxproj -e \.ini c++/src/util/xregexp/regexp.cpp c++/src/util/xregexp/regexp_template_tester.cpp c++/include/util/xregexp/regexp.hpp c++/include/util/xregexp/regexp_template_tester.hpp (if my rough estimation is not absolutely wrong.) Kind regards Andreas. -- http://fam-tille.de
Bug#1025424: beast-mcmc: please enable autopkgtest
Control: severity -1 wishlist Hi Andreas, On 2022-12-04 19:40, Andreas Tille wrote: Am Sun, Dec 04, 2022 at 03:34:44PM +0200 schrieb Andrius Merkys: I have recently worked on beast-mcmc and noticed it has an outline of a possible autopkgtest in debian/tests/run-unit-test, but debian/tests/control is missing. I have not tried running debian/tests/run-unit-test, but from its existence I assume the autopkgtest is left unfinished. Thanks for reminding me about this. I admit I do not really remember why I stopped with this. Currently I'm running into OpenCL error: CL_DEVICE_NOT_FOUND from file , line 122. I currently do not have any clue how to fix this. Here the code seems to be complaining about missing OpenCL hardware support, which will not be available on buildds and ci machines. Thus tests needing OpenCL have to be skipped. Hope this helps, Andrius
Bug#1024526: simbody: FTBFS on ppc64el, mips64el
Control: severity -1 important The upstream says this is a bug in optimization, but they do not have access to these architectures. For now I have RMed the binaries of ppc64el and mips64el, thus the package should be allowed to migrate to testing without them for the time being. Andrius
Bug#1012572: android-platform-frameworks-base: FTBFS with protobuf 3.20.1+
Hello Roger, On Fri, Jun 10, 2022 at 09:48:06PM +0900, Roger Shimizu wrote: > I tried your patch by installing protobuf in experimental > and confirmed it builds well, and all tests are also OK. > Will upload after protobuf 3.20 (or later) hits unstable. > Thanks for your support! You uploaded this patch to experimental, however I see no sign of v13 to be uploaded to unstable anytime soon. Can you please apply this same patch also in unstable? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1024515: Acknowledgement (mariadb-10.6: FTBFS on s390x: test main.order_by_innodb failed with type 'ref')
I did a re-run today and surprisingly it passed: main.order_by_innodb 'innodb'w2 [ pass ] 84 https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=s390x&ver=1%3A10.6.11-1&stamp=1670206361&raw=0 Maybe the issue is sporadic? But also the first day I saw this I re-ran the build and it did not pass, so could also be the test behaviour was dependant on some dependency that updated in the past week?
Bug#1025459: tigervnc: unmentioned config file
Source: tigervnc Version: 1.12.0+dfsg-5 Severity: minor Hey. tigervncserver(1) manpage mentions: /etc/tigervnc/vncserver-config-defaults ~/.vnc/tigervnc.conf /etc/tigervnc/vncserver-config-mandatory tigervncsession(8) manpage mentions: /etc/tigervnc/vncserver-config-defaults $HOME/.vnc/config /etc/tigervnc/vncserver-config-mandatory As far as I understand, all of them except for $HOME/.vnc/config are Debian addition, right? But $HOME/.vnc/config is still read (I guess in all cases)? Could you possibly add the respectively missing ($HOME/.vnc/config vs. ~/.vnc/tigervnc.conf) in the two manpages and also in which order the issing is loaded. It would further be nice if it could be emphasised in the manpage, that the Debian ones use Perl syntax, while the $HOME/.vnc/config uses key=value lines. Thanks, Chris.
Bug#1025458: tigervncserver: differing PID/log file format for unix/inet sockets
Source: tigervnc
Version: 1.12.0+dfsg-5
Severity: normal
Hey.
It seems that tigervncserver creates differen PID/log file names, depending
on whether it's listening on inet or unix sockets:
For UNIX sockets it uses:
kronecker.scientia.org:1.{log,pid}
with 1 being the display ID
For inet sockets:
kronecker.scientia.org:5901.{log,pid}
with 5091 being the port.
I think it would be much better if it would always use the display ID.
Thanks,
Chris.
Bug#1025457: tigervnc: allow to specify the PID file
Source: tigervnc Version: 1.12.0+dfsg-5 Severity: wishlist Hey. I have a use case here I start a VNC server via SSH as normal user and using systemd’s --user service manager. For that to work, systemd needs to know the PID file, which I thus need to know in the SSH command I'm executing on the remote side. It would be nice if I could tell tigervncserver exactly which file it should use, bacuse then I could e.g. even use a temp file created in the SSH command. Of course I could also hard code the hostname (which is used right now) in the SSH command, but that would make that one only useable for on remote host name in ssh_config. Thanks, Chris.
Bug#1025456: RM: flask-oidc -- RoM; inactive upstream; never migrated to testing
Package: ftp.debian.org Severity: normal Hello, I would like to request the removal of flask-oidc from unstable. The package is currently FTBFSing, and while it would be possible to patch it and make it build successfully again, I don't think it's worth the trouble: the package has never migrated to testing, and upstream has been inactive for 2 years now (the latest upstream release happened more than 5 years ago). This package is maintained with the Debian Python team, but I was the one who added it to Debian and there has been no other person interested in it ever since. --8<---cut here---start->8--- $ apt rdepends python3-flask-oidc python3-flask-oidc Reverse Depends: --8<---cut here---end--->8--- Thank you, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/ signature.asc Description: PGP signature
Bug#1002856: RFP: openrgb -- Control RGB devices
Hi there, I just had a quick look at the source code. The problem are the vendored headers in the dependencies/ folder. Per debian policy they need to be packaged themselves. I was just looking at this package as well and I was a bit confused by your comment. What exactly are you seeing in the dependencies folder that would require separate library packages? Could you also please point me to the policy that requires this? For openrgb this means at least seven new libraries. I see considerably more than seven directories in that folder so, again, I'm confused about what you're saying. Upstream provides *.debs in the meantime. Which is very convenient! It seems that packaging this into main (GPL2+) should be fairly straightforward unless I'm missing something. If I am missing something, I welcome the education from someone! :) -Olek OpenPGP_signature Description: OpenPGP digital signature
Bug#995670: Zig package status
Hi Bastian, * Bastian Germann [221204 09:02]: > > With the copyright in place I will sponsor it. Please notify me when you > think you have represented the applicable licenses completely and I will > review it. Many thanks for stepping forward for this. I started looking at the copyright again and have some questions. I'm not sure if the discussion should continue here in this bug report or if it is better to take it "offline" to be just with you as the potential sponsor. Thanks, Nick.
Bug#1025455: libssh-dev: DSA support is disabled by default
Source: libssh Version: 0.10.4-2 Severity: important Tags: patch X-Debbugs-Cc: Vagrant Cascadian Control: block 1020087 by -1 In libssh 0.10.x versions, DSA support is deprecated and disabled by default. This causes test suite failures when building guile-ssh which tests support for DSA keys. The attached patch enables DSA support, as was supported in previous versions. If that is not an option in time for bookworm freeze, please let me know ASAP so I can patch guile-ssh instead. Thanks for maintaining libssh! live well, vagrant From d3963761a4e2666187e4fb5281f5f45c9e8a106f Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Mon, 5 Dec 2022 00:19:05 + Subject: [PATCH] debian/rules: Enable DSA support. Upstream 0.10.x disables DSA support by default, and is likely to be deprecated in future versions. --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index fb55ca2..880aa59 100755 --- a/debian/rules +++ b/debian/rules @@ -1,6 +1,6 @@ #!/usr/bin/make -f -DEB_CMAKE_EXTRA_FLAGS := -DBUILD_STATIC_LIB=ON -DLIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH) -DUNIT_TESTING=$(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),OFF,ON) -DWITH_GSSAPI=ON +DEB_CMAKE_EXTRA_FLAGS := -DBUILD_STATIC_LIB=ON -DLIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH) -DUNIT_TESTING=$(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),OFF,ON) -DWITH_GSSAPI=ON -DWITH_DSA=ON export DEB_LDFLAGS_MAINT_APPEND = -Wl,-z,defs -Wl,-O1 export DEB_BUILD_MAINT_OPTIONS = hardening=+all -- 2.30.2 signature.asc Description: PGP signature
Bug#1025349: gdm3: should define the display-manager alias for start dependencies
Simon McVittie, le lun. 05 déc. 2022 00:15:01 +, a ecrit: > Upstream gdm3.service (or possibly gdm.service, I think we do some renaming > for historical reasons) has > > [Install] > Alias=display-manager.service > > so that `systemctl enable gdm3.service` will create a symlink > /etc/systemd/system/display-manager.service -> > /lib/systemd/system/gdm3.service. > This assumes that only one display manager can be enabled at a time, and > preferably only one *installed* at a time: if both gdm3 and lightdm try > to do that, if I understand correctly, the result will be unpredictable. > > In Debian, instead of gdm3.service having that, the debconf question > creates that symlink programmatically if and only if gdm3 is the selected > display manager (in particular, the symlink isn't created if you have > installed both gdm3 and lightdm, and chosen to use lightdm instead). > > If I understand correctly, any mechanism that makes the symlink exist > should be enough for "Before=display-manager.service" to do what you want > it to do. Please try it? Ah, indeed, that works, sorry for not having actually tried, because lightdm does have these two lines. But then, with this reasoning, lightdm is bogus by having these two lines? Samuel > systemd maintainers: Am I getting this right? > > smcv >
Bug#1025349: gdm3: should define the display-manager alias for start dependencies
On Sat, 03 Dec 2022 at 01:03:38 +0100, Samuel Thibault wrote: > If gdm happens to manage to start quicker than console-setup, > console-setup's setupcon call will fail. So we need a dependency between > the two, to make console-setup start "Before" display managers. This can > be set with > > Before=display-manager.service > > since display managers usually set this alias. But gdm3 apparently > explicitly removes this with the debian/patches/92_systemd_unit.patch > patch: > > * Don't install the display-manager.service alias, which is managed > jointly by all Debian display managers via a debconf question Upstream gdm3.service (or possibly gdm.service, I think we do some renaming for historical reasons) has [Install] Alias=display-manager.service so that `systemctl enable gdm3.service` will create a symlink /etc/systemd/system/display-manager.service -> /lib/systemd/system/gdm3.service. This assumes that only one display manager can be enabled at a time, and preferably only one *installed* at a time: if both gdm3 and lightdm try to do that, if I understand correctly, the result will be unpredictable. In Debian, instead of gdm3.service having that, the debconf question creates that symlink programmatically if and only if gdm3 is the selected display manager (in particular, the symlink isn't created if you have installed both gdm3 and lightdm, and chosen to use lightdm instead). If I understand correctly, any mechanism that makes the symlink exist should be enough for "Before=display-manager.service" to do what you want it to do. Please try it? systemd maintainers: Am I getting this right? smcv
Bug#1018326: celery: build-depends on python3-nose or uses it for autopkgtest
Hi, I checked the upstream source, and I found the upstream stopped using "nose" many years ago. Refer to this commit 29df527147514b3eab7fbc3dbf41ff181bf1dcd9 in the upstream repository https://github.com/celery/celery . Possible next step: Re-package the more recent upstream source to resolve this issue. - tai
Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
Hi Rafael,
latex is not able to compile a rsbtest-generated
file looking like the one I attach.
The problematic line is:
\usepackage[utf8x]{inputenc}
and there are two alternative fixes to be applied before autoreconf:
Patch suggestion 1:
sed 's/utf8x//g' -i rsbtest/rsbtest.cpp
Patch suggestion 2:
sed 's/..LATEX./false/g' -i rsbtest/Makefile.am
I suggest to use 1, and if you confirm it works, I'd also use
it upstream.
Is it effective?
Ciao,
Michele
On 20221204@22:45, Rafael Laboissière wrote:
> Control: forwarded -1 michelemart...@users.sourceforge.net
> Control: tags -1 unreproducible
>
> Hi Michele,
>
> There is a bug report filed against the librsb package (Bug#1016332 [1])
> that has severity level "serious". This is blocking the package entering
> testing and, therefore, librsb will be removed from the upcoming bookworm
> release, unless the bug is fixed. This means that octave-sparsersb would
> also be absent from the next Debian release if nothing is done.
>
> I cannot reproduce the bug and I am hereby tagging this bug report
> accordingly. Skimming over the full build log [2], I could not find the
> source of the problem. If you could take a look at this, it will be great.
>
> Best,
>
> Rafael
>
> [1] https://bugs.debian.org/1016332
> [2] http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log
>
> * Lucas Nussbaum [2022-07-29 20:37]:
>
> > Source: librsb
> > Version: 1.3.0.1+dfsg-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20220728 ftbfs-bookworm
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> >
> > [snip]
> >
> > The full build log is available from:
> > http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log
> >
> > All bugs filed during this archive rebuild are listed at:
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
> > or:
> > https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
> >
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> > contribute!
> >
> > If you reassign this bug to another package, please marking it as
> > 'affects'-ing this package. See
> > https://www.debian.org/Bugs/server-control#affects
> >
> > If you fail to reproduce this, please provide a build log and diff it
> > with mine so that we can identify if something relevant changed in the
> > meantime.
% for f in ; do epstopdf $f; done;
%%%
\documentclass[xcolor=dvipsnames]{beamer}
%rm *.pdf *.aux *.nav *.out *.dvi *.log *.snm *.toc -f && ls && latex slides.tex && pdflatex slides.tex && pdflatex slides.tex && evince slides.pdf
\usepackage{color}
\usepackage{sverb} % for verbinput
\usepackage{hyperref} % for url
\usepackage{epsfig}
\hypersetup{pdfpagemode=fullscreen}
\setbeamertemplate{footline}[page number] % no footline
\setbeamertemplate{footline}[text line{...}] % no footline
\setbeamertemplate{navigation symbols}{}
\usepackage[]{verbatim}
\usepackage[]{ulem}
\usepackage{graphicx}
\usepackage{ucs}
\usepackage[utf8x]{inputenc}
\usepackage{epstopdf}
\usepackage[]{comment}
\usepackage[]{color}
%\logo{\includegraphics[scale=0.20]{logo.png}}
\def\mytitle{librsb autotuning benchmark report\\
Linked to librsb-88e18cc
compiled by "gcc"
with flags "-g -O2 -ffile-prefix-map=/root/librsb=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c99"
supporting up to 128 threads
and hardcoded cache parameters ""
and OpenMP enabled.
Supported types: "double,float,float complex,double complex"
Not using C++ RSB implementation.
Not using C++ wrapper to librsb.
Not linked to the Intel MKL.
\_\_cplusplus: 201703
\_\_GNUC\_\_: 12
\_\_GNUC\_MINOR\_\_: 1
}%
\title{\mytitle}
%\author[{michele DOT martone AT lrz DOT de}]{Michele MARTONE}
%\institute{LRZ\\
%Garching bei Muenchen, Germany
%}
%
%\date[]{Place\\Date}%
%
\def\plotwidth{0.6}
\begin{document}
\section{Title Page}
\frame { \titlepage }
%%%
%%
%%%
Bug#1024055: Upload MariaDB 1:10.3.37-0+deb10u1 ?
Hi Emilio! I didn't get a reply to this, so asking again. On Sun, 20 Nov 2022 at 17:57, Otto Kekäläinen wrote: > > Hello Emilio! > > MariaDB 1:10.3.37-0+deb10u1 is ready for upload at > https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commits/buster > > Do you want to take care of the upload?
Bug#1025454: afl: Downloads software during build
Source: aflplusplus Version: 4.04c-1 Severity: serious Hi, On the buildds, we get: # -/usr/bin/make -C utils/plot_ui /usr/bin/make -C frida_mode make[3]: Entering directory '/<>/frida_mode' mkdir -p /<>/frida_mode/build/ mkdir -p /<>/frida_mode/build/frida/ wget -qO /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz "https://github.com/frida/frida/releases/download/15.2.1/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz"; || curl -L -o /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz "https://github.com/frida/frida/releases/download/15.2.1/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz"; /bin/sh: 1: wget: not found /bin/sh: 1: curl: not found make[3]: *** [GNUmakefile:313: /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz] Error 127 make[3]: Leaving directory '/<>/frida_mode' make[2]: [GNUmakefile:636: distrib] Error 2 (ignored) cd nyx_mode && ./build_nyx_support.sh = Nyx build script = [*] Performing basic sanity checks... [*] Making sure all Nyx is checked out ./build_nyx_support.sh: line 41: git: command not found make[2]: [GNUmakefile:637: distrib] Error 127 (ignored) cd qemu_mode && sh ./build_qemu_support.sh = QemuAFL build script = [*] Performing basic sanity checks... [+] All checks passed! [*] Making sure qemuafl is checked out [*] cloning qemuafl Trying to clone qemuafl (attempt 1/3) ./build_qemu_support.sh: 84: git: not found Trying to clone qemuafl (attempt 2/3) ./build_qemu_support.sh: 84: git: not found Trying to clone qemuafl (attempt 3/3) ./build_qemu_support.sh: 84: git: not found [-] Not checked out, please install git or check your internet connection. make[2]: [GNUmakefile:638: distrib] Error 1 (ignored) cd unicorn_mode && unset CFLAGS && sh ./build_unicorn_support.sh = UnicornAFL build script = [...] On machines that have more software installed, it will download various things and build them. It makes at least use of software like wget, curl, git, cargo. Packages in Debian should be build only from the source and not download more sources from internet. Kurt
Bug#982384: [Help] Bug 982384: Warnings profile count data file not found
Andreas Tille writes: > Could anybody comment on it / fix it? Per https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fprofile-use: Before you can use this option, you must first generate profiling information. See Instrumentation Options, for information about the -fprofile-generate option. It may be simplest to drop the option, particularly if cross compilation is otherwise possible. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#891197: Please switch to pcre2
Andreas Tille writes: > it would be great if you could use your upstream contact to convince > them to switch to pcre2. Upstream explicitly passed on pcre2 a few years ago, but times have changed; I've opened an internal ticket to revisit the question. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#1025453: Bug#1024093: The problem is still present in 0.3.61-1
On Sun, 2022-12-04 at 23:49 +0100, Dylan Aïssi wrote: > Le dim. 4 déc. 2022 à 23:28, James Bottomley > > So please restore the state of this bug report and open your own bug > report. I'm not really as expert in the bug control system as debian developers are supposed to be but I think I got this done. James
Bug#1025452: lintian: useless checks of debian/tests datafiles
Package: lintian Version: 2.115.3 Severity: important I'm working on new upstream version of upx-ucl. The package contains some *intentionally broken* ELF files inside debian/tests to check that for example upx does not crash on them. However for some reason lintan wants the data files to be perfectly correct binaries, with an accompanying source files. IMHO this is just ridiculous. Those files are in debian/tests anyway, what's the point of having such strict requirements on them? Anyway, some time ago I added overrides for those warnings, but now I can see that: - the overrides do no longer work, because lintian now requires names to be put inside square brackets; - some new checks were implemented to see if ELF file is correct, and the new checks display a bunch of additional warnings making it completely unreadable (and I do not think they can be overridden). Please just look at this lintian output of upx-ucl 3.96-3 package: Now running lintian --display-info --display-experimental --pedantic --color=always upx-ucl_3.96-3_amd64.changes ... upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 1]: [ 0] 00010102: 0001003e0002 405418 40 43 0 0 15762873573703680 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 9]: [ 4] 00ce: 00010102464c457f 4025b00d003e0002 35166de4b60f d84f21364027050f A 51577028 955743702 432376351040014592 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 11]: [ 5] 27080001: 213c84c840070f02 ec0ec27011c 2fb3cc074005 7b0b90641704e460 WAxMILTCo 9475801 2872516608 510523112357773942 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 15]: [ 8] 0400322e: 0302dd34cfba fff60303141f2006 5631d867221fc1ff 490437432c17f6f7 ox 2146830080 2207070372 1972876281791746561 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 19]: [10] 2f311b08: 086c21b017098f12 864219082f6247e5 17866c21b0865e62 a7021b086c212f29 AMLOGTop 1691277137 398596360 12089950241734945530 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 22]: [11] 5f55b086: f14d86421908bb17 17488fe56c21b086 745f20421b086198 2b02d0759b23b0 WAXMSLOGTCxxlExx 1814138935 2486117640 3417519580065700616 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 24]: [12] 17dd86c2: 01804219086c0b2f 8a1d42190864217 86373677841b0861 432f5b21b0864277 WAMSLGTxop 527180208 3944157743 6210289578152757356 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 26]: [13] 1bc3178d: 701738086c21902f 2f8c5f7b86c21b08 1748bf3d6c21b086 21039f0002a87272 AILGTxop 3076108358 1132526 4860816968149843738 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 29]: [14] 2fb31817: 17206c87272077ac 4d862689f100039 5fff0036de63efa8 746573006b68635f WAXMop 1718026210 1752397164 7382801058585599744 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 34]: [18] 5f6f6eb5: adbe103fc928f28c 64742666807a4b04 1b74845f6ec7756f 6e3eddf0a16d956d XxSIOTCop 1699376211 2037396843 8452239821877519578 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.pm line 569. upx-ucl_3.96-3.dsc (patched): Warning while running readelf ondebian/tests/data/907426-poc_free: Parse error in readelf section headers [row 36]: [19] 372f004f: bdb7bdb77e62bd6f 6567208368764a6d 7784009dba17c2b5 322738739d0cdd91 WxMILOTCxop 2826200169 3671557790 3259666543423467181 at /usr/share/lintian/bin/../lib/Lintian/Index/Elf.
Bug#1025265: lua-cjson: diff for NMU version 2.1.0+dfsg-2.2
Package: lua-cjson Followup-For: Bug #1025265 Hi, did you upload version 2.1.0+dfsg-2.2 yet ? If not, I can do a Team Upload. Also I've push your changes to salsa repository. Jérémy -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lua-cjson depends on: ii libc6 2.36-6 lua-cjson recommends no packages. lua-cjson suggests no packages. -- no debconf information
Bug#1024093: The problem is still present in 0.3.61-1
Le dim. 4 déc. 2022 à 23:28, James Bottomley a écrit : > > On Sun, 2022-12-04 at 22:42 +0100, Dylan Aïssi wrote: > > Le sam. 3 déc. 2022 à 15:45, James Bottomley > > a écrit : > > > > > > I just tested this out with the same results as previously reported > > > > > > > Do you mean you don't have sound at all using pipewire 0.3.61 in a > > QEMU VM? > > No, this is a physical system. The sound problems are only partial as > described at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024093#45 > Then your issue is absolutely not related to the initial issue of #1024093 that was about sound not working at all in a QEMU VM and that bug was fixed in pipewire/0.3.60-2. So please restore the state of this bug report and open your own bug report. Dylan
Bug#1025451: dgit: incorrectly tries to export patch queue without explicit --quilt=nofix
Package: dgit Version: 10.1 Hello, https://salsa.debian.org/emacsen-team/xref-el, reset master to 885455a. If you try to run dgit commands, it invokes git-debrebase to export a broken patch queue. The work around is to supply --quilt=nofix. -- Sean Whitton signature.asc Description: PGP signature
Bug#1024093: The problem is still present in 0.3.61-1
On Sun, 2022-12-04 at 22:42 +0100, Dylan Aïssi wrote: > Le sam. 3 déc. 2022 à 15:45, James Bottomley > a écrit : > > > > I just tested this out with the same results as previously reported > > > > Do you mean you don't have sound at all using pipewire 0.3.61 in a > QEMU VM? No, this is a physical system. The sound problems are only partial as described at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024093#45 James
Bug#1025450: python-gssapi: enable testing when packaging python-gssapi
Source: python-gssapi Version: 1.8.2-1 Severity: normal Dear Maintainer, The current debian package building process does not launch any testing when building python-gssapi. It will be great if the building process launches the corresponding upstream tests. FWIW: the upstream stopped using nosetests https://github.com/pythongssapi/python-gssapi/commit/5552513a47a636a4d956f76b498c6fa2e368cc98 and we have removed nose as debian package dependency (see BTS bug:#1018505) . However, the package building process still does not launch the corresponding upstream testing. -tai
Bug#1025427: pipewire: frequent crashes on x11 bell
Hi, Le dim. 4 déc. 2022 à 15:27, Adam Borowski a écrit : > > On a machine with no physical PC honker, I have the x11 bell enabled. > And that causes random but frequent crashes in pipewire: > Random crashes can happen when the module is loaded twice. And this module is loaded by default conf files since pipewire 0.3.60 see https://salsa.debian.org/utopia-team/pipewire/-/commit/45746784248c468622f0bd62597a3c5cc05e53b2 Do you load this module in another conf file? Best, Dylan
Bug#981600: nghttp2: missing build-dependency on tzdata
retitle 981600 nghttp2: missing build-depends on tzdata tags 981600 + patch severity 981600 serious thanks Helmut Grohne wrote: > An arch-only build (but not a full build) of nghttp2 seems to reliably > fail at test util_localtime_date: This happens because there is a missing build-dependency on tzdata. Arch-all builds work because python3-sphinx in Build-Depends-Indep depends on tzdata. The official buildds have tzdata in their chroots, but this is really wrong, because tzdata is not build-essential and should therefore not be installed on chroots being used to build packages (see Bug #837060). Trivial patch attached. Please make sure this is also fixed in bullseye as well, as packages in stable must build in stable. Thanks.--- a/debian/control +++ b/debian/control @@ -14,6 +14,7 @@ Build-Depends: debhelper (>= 13), libsystemd-dev, libxml2-dev, pkg-config, + tzdata, zlib1g-dev Build-Depends-Indep: python3-sphinx Standards-Version: 4.6.1
Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
Control: forwarded -1 michelemart...@users.sourceforge.net Control: tags -1 unreproducible Hi Michele, There is a bug report filed against the librsb package (Bug#1016332 [1]) that has severity level "serious". This is blocking the package entering testing and, therefore, librsb will be removed from the upcoming bookworm release, unless the bug is fixed. This means that octave-sparsersb would also be absent from the next Debian release if nothing is done. I cannot reproduce the bug and I am hereby tagging this bug report accordingly. Skimming over the full build log [2], I could not find the source of the problem. If you could take a look at this, it will be great. Best, Rafael [1] https://bugs.debian.org/1016332 [2] http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log * Lucas Nussbaum [2022-07-29 20:37]: Source: librsb Version: 1.3.0.1+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. [snip] The full build log is available from: http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1011552: ITP: python-exceptiongroup -- backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11
Hi Agathe, * Agathe Porte [2022-05-24 22:15]: * Package name: python-exceptiongroup Version : 1.0.0~rc7 Upstream Author : Alex Grönholm * URL : https://github.com/agronholm/exceptiongroup * License : MIT + PSFLv2 Programming Lang: Python Description : backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11 I was just going to ask about your progress on this package (because it is needed to update src:python-hypothesis), but then I saw that it is about to be uploaded to experimental. Thank you! Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1024093: The problem is still present in 0.3.61-1
Le sam. 3 déc. 2022 à 15:45, James Bottomley a écrit : > > I just tested this out with the same results as previously reported > Do you mean you don't have sound at all using pipewire 0.3.61 in a QEMU VM?
Bug#1025449: transition: capnproto
Control: tags -1 confirmed Control: forwarded -1 https://release.debian.org/transitions/html/auto-capnproto.html Hi tony On 2022-12-04 12:46:19 -0800, tony mancill wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > I am requesting a transition slot for capnproto [1]. The package upload > to experimental [2] created this auto-transition [3], which all looks > correct to me. capnproto 0.9.2 resolves a security vulnerability [4] > present in 0.9.1. Please go ahead Cheers > > Thank you! > tony > > [1] https://tracker.debian.org/pkg/capnproto > [2] > https://tracker.debian.org/news/1393214/accepted-capnproto-092-1-source-amd64-into-experimental/ > [3] https://release.debian.org/transitions/html/auto-capnproto.html > [4] https://security-tracker.debian.org/tracker/CVE-2022-46149 > > Ben file: > > title = "capnproto"; > is_affected = .depends ~ /\b(libcapnp\-0\.9\.1)\b/ | .depends ~ > /\b(libcapnp\-0\.9\.2)\b/; > is_good = .depends ~ /\b(libcapnp\-0\.9\.2)\b/; > is_bad = .depends ~ /\b(libcapnp\-0\.9\.1)\b/; -- Sebastian Ramacher
Bug#1024549: espeakup: crashes during speech synthesis installation, snd_pcm_area_copy assertion failed
Hello, I was about to try to investigate, but I cannot reproduce it with the daily image any more. It uses the new alsa-lib 1.2.8 upstream version, so perhaps the bug was just fixed, could you also give it a try? Samuel
Bug#1025449: transition: capnproto
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I am requesting a transition slot for capnproto [1]. The package upload to experimental [2] created this auto-transition [3], which all looks correct to me. capnproto 0.9.2 resolves a security vulnerability [4] present in 0.9.1. Thank you! tony [1] https://tracker.debian.org/pkg/capnproto [2] https://tracker.debian.org/news/1393214/accepted-capnproto-092-1-source-amd64-into-experimental/ [3] https://release.debian.org/transitions/html/auto-capnproto.html [4] https://security-tracker.debian.org/tracker/CVE-2022-46149 Ben file: title = "capnproto"; is_affected = .depends ~ /\b(libcapnp\-0\.9\.1)\b/ | .depends ~ /\b(libcapnp\-0\.9\.2)\b/; is_good = .depends ~ /\b(libcapnp\-0\.9\.2)\b/; is_bad = .depends ~ /\b(libcapnp\-0\.9\.1)\b/; signature.asc Description: PGP signature
Bug#1024791: libhsa-runtime64-1: libhsa-amd-aqlprofile64.so warning
Hi Cory, Cordell Bloor, on 2022-11-24: > LoadLib(libhsa-amd-aqlprofile64.so) failed: libhsa-amd-aqlprofile64.so: > cannot open shared object file: No such file or directory > > There is not actually anything wrong or unexpected with this file being > missing, so this warning is not appropriate. Indeed, this has been cluttering build logs, and at some point when things go wrong, they tend to produce red herrings. > I would suggest that the attempt to load the aqlprofile extension be > removed until there is an open-source package available. This can be > done by deleting some code in src/core/runtime/amd_gpu_agent.cpp: > > https://salsa.debian.org/rocm-team/rocr-runtime/-/blob/debian%2F5.2.3-1/src/core/runtime/amd_gpu_agent.cpp#L887-891 Thanks, thanks, thanks for the pointer! I give this a try. Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Helreid - Migrations signature.asc Description: PGP signature
Bug#1025448: google-android-installers: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: google-android-installers Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450 pt_BR.po.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#1025447: google-android-m2repository-installer: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: google-android-m2repository-installer Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450 pt_BR.po.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#1025446: php8.2: Please link against libatomic for "riscv64" arch
Source: php8.2 Severity: wishlist Tags: ftbfs patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: m...@debian.org, locutusofb...@debian.org, bba...@debian.org Hi, The package still in experimental builds with the changes attached, I built the package locally on this architecture, so please include it (or add an equivalent solution) in the next uploads, at least before moving to unstable. Thanks and cheers. -- Manuel A. Fernandez Montecelo diff -Nru php8.2-8.2.0~rc5/debian/changelog php8.2-8.2.0~rc5/debian/changelog --- php8.2-8.2.0~rc5/debian/changelog 2022-10-28 17:55:40.0 + +++ php8.2-8.2.0~rc5/debian/changelog 2022-12-04 09:18:27.0 + @@ -1,3 +1,10 @@ +php8.2 (8.2.0~rc5-1+0.riscv64.1) unreleased; urgency=medium + + * Non-maintainer upload. + * riscv64: fix linking against -latomic + + -- Manuel A. Fernandez Montecelo Sun, 04 Dec 2022 09:18:27 + + php8.2 (8.2.0~rc5-1) experimental; urgency=medium * New upstream version 8.2.0~rc5 diff -Nru php8.2-8.2.0~rc5/debian/rules php8.2-8.2.0~rc5/debian/rules --- php8.2-8.2.0~rc5/debian/rules 2022-10-28 17:55:40.0 + +++ php8.2-8.2.0~rc5/debian/rules 2022-12-04 09:18:27.0 + @@ -156,7 +156,12 @@ # Enable producing of debugging information DEB_CFLAGS_MAINT_APPEND += -g -DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed +# needs to link explicitly against libatomic on riscv64 +ifneq (,$(filter $(DEB_HOST_ARCH),riscv64)) +DEB_LDFLAGS_MAINT_APPEND += -latomic +endif + +DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed export DEB_CFLAGS_MAINT_APPEND export DEB_LDFLAGS_MAINT_APPEND
Bug#1024757: Editor: -key ignored
Hi! This is what I get when I run "openscad --debug=scintillaeditor": Pressing 3 times: scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP Pressing + 3 times: scintillaeditor: KeyPress - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyPress - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyPress - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyPress - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: SHIFT ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP Pressing (or any other letter) 3 times: scintillaeditor: KeyPress - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyPress - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyPress - modifiers: shift ctrl alt meta keypad GROUP scintillaeditor: KeyRelease - modifiers: shift ctrl alt meta keypad GROUP Sorry, I dont' have a nimpad on my keyboard, so I can't test that -key. Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Bug#1025445: google-android-sdk-docs-installer: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: google-android-sdk-docs-installer Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450 pt_BR.po.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#1025444: vdr-plugin-femon FTCBFS: misses compiler flags due to using the build architecture pkg-config
Source: vdr-plugin-femon Version: 2.4.0-5 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs vdr-plugin-femon fails to cross build from source, because it uses the build architecture pkg-config and thus misses out on relevant compiler flags. It has rather precise ideas on where to locate vdr.pc in order to support being vendored even though Debian doesn't vendor it. As such, changing the pkg-config invocation is probably not acceptable upstream. Instead, I propose forcing the Debian location of the .pc file. I'm attaching a patch for your convenience. Helmut diff --minimal -Nru vdr-plugin-femon-2.4.0/debian/changelog vdr-plugin-femon-2.4.0/debian/changelog --- vdr-plugin-femon-2.4.0/debian/changelog 2022-01-12 09:21:10.0 +0100 +++ vdr-plugin-femon-2.4.0/debian/changelog 2022-12-03 10:32:00.0 +0100 @@ -1,3 +1,10 @@ +vdr-plugin-femon (2.4.0-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Force correct location of vdr.pc. (Closes: #-1) + + -- Helmut Grohne Sat, 03 Dec 2022 10:32:00 +0100 + vdr-plugin-femon (2.4.0-5) unstable; urgency=medium * Fix debian/watch diff --minimal -Nru vdr-plugin-femon-2.4.0/debian/rules vdr-plugin-femon-2.4.0/debian/rules --- vdr-plugin-femon-2.4.0/debian/rules 2022-01-12 09:21:10.0 +0100 +++ vdr-plugin-femon-2.4.0/debian/rules 2022-12-03 10:31:56.0 +0100 @@ -3,6 +3,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +include /usr/share/dpkg/architecture.mk +export VDRDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig + %: dh $@ --with vdrplugin
Bug#1025443: aflplusplus: Missing lld-14 Build-Depends
Source: aflplusplus Version: 4.04c-1 Hi, The LTO mode is not build at runtime, the log shows: [+] llvm_mode detected llvm 10+, enabling neverZero implementation and c++14 [+] llvm_mode detected llvm 11+, enabling afl-lto LTO implementation GNUmakefile.llvm:229: ld.lld not found, cannot enable LTO mode This is because there is a missing Build-Depends on lld-14. The LTO mode is the recommended mode. Kurt
Bug#1025442: jruby,jruby-openssl: both ship /usr/share/jruby/lib/ruby/stdlib/*openssl*
Package: jruby,jruby-openssl Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 9.3.9.0+ds-1 Control: found -1 0.9.21-4 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../jruby-openssl_0.9.21-4_all.deb ... Unpacking jruby-openssl (0.9.21-4) ... dpkg: error processing archive /var/cache/apt/archives/jruby-openssl_0.9.21-4_all.deb (--unpack): trying to overwrite '/usr/share/jruby/lib/ruby/stdlib/jopenssl/load.rb', which is also in package jruby 9.3.9.0+ds-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/jruby-openssl_0.9.21-4_all.deb If jruby-openssl is obsolete, please RM it and add to jruby Breaks+Replaces: jruby-openssl and probably also a (versioned) Provides: jruby-openssl cheers, Andreas jruby=9.3.9.0+ds-1_jruby-openssl=0.9.21-4.log.gz Description: application/gzip
Bug#991060: reopen for bullseye
reopen 991060 found 991060 0.8.1-8 fixed 991060 0.9-1 thanks Hi. Please, let us fix this for stable. I would gladly backport the fix from unstable but since the fix was included in a new upstream release I'm in doubt about what would have to be done and would definitely need help. Thanks.
Bug#1023460: in debian/nslcd.config, guess_ldap_uri returns the IP address instead of the name of the server
* Arthur de Jong [221204 09:42]: > On Fri, 2022-11-04 at 11:00 -0400, Marvin Renich wrote: > > When nslcd is installed [...] guess_ldap_uri tries to find an > > appropriate ldap server using some heuristics. If it finds a host > > [...] it returns the IP address of the host rather than the name. > > The original reason for this was that if you use LDAP for host name > lookups having a host name in nslcd.conf causes problems. > > I think that is reasonably uncommon and agree that the host name would > make more sense to provide as a suggestion. This behaviour will be > changed in the next upload (uploads are not very frequent). > > Thanks, Thank you! ...Marvin
Bug#992010: pipewire: Cracking when playing sounds
Package: pipewire Version: 0.3.61-1 Severity: important Followup-For: Bug #992010 Forwarded: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2451 X-Debbugs-Cc: onit...@gmail.com This is almost certainly upstream issue https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2451 . According to the bug report, it was fixed in 0.3.58, but it's still present in Debian 0.3.63-1. Adding the allowed-rates option as described fixed it for me as well. Looks like the fix was either reverted, or the Debian package is still missing it? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-5-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire depends on: ii adduser 3.129 ii init-system-helpers 1.65.2 ii libpipewire-0.3-modules 0.3.61-1 ii pipewire-bin 0.3.61-1 pipewire recommends no packages. pipewire suggests no packages. -- no debconf information
Bug#1025441: sasl2-bind should depend or at least recommend libsasl2-modules
Package: sasl2-bin Version: 2.1.27+dfsg-2.1+deb11u1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Problem arose when installing my first bullseye brand new sendmail server(instead of upgrading from buster) Regardless of being well configured, sendmail didn´t offer any AUTH option (nor with or without starting tls). I checked all configurations several times and tried to debug. Sendmail log (with high loglevel) showed " AUTH warning: no mechanisms" and never connected to saslauth * What exactly did you do (or not do) that was effective (or ineffective)? Finally tried installing libsasl2-modules and then sendmail started to try to AUTH. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.5 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 'stable-security'), (400, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-19-amd64 (SMP w/4 CPU threads) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sasl2-bin depends on: ii db-util5.3.1+nmu1 ii debconf [debconf-2.0] 1.5.77 ii init-system-helpers1.60 ii libc6 2.31-13+deb11u5 ii libcrypt1 1:4.4.18-4 ii libdb5.3 5.3.28+dfsg1-0.8 ii libkrb5-3 1.18.3-6+deb11u3 ii libldap-2.4-2 2.4.57+dfsg-3+deb11u1 ii libpam0g 1.4.0-9+deb11u1 ii libsasl2-2 2.1.27+dfsg-2.1+deb11u1 ii libssl1.1 1.1.1n-0+deb11u3 ii lsb-base 11.1.0 sasl2-bin recommends no packages. sasl2-bin suggests no packages. -- Configuration Files: /etc/default/saslauthd changed: START=yes DESC="SASL Authentication Daemon" NAME="saslauthd" MECHANISMS="ldap" MECH_OPTIONS="" THREADS=5 OPTIONS="-c -m /var/run/saslauthd" -- debconf information: cyrus-sasl2/purge-sasldb2: false cyrus-sasl2/upgrade-sasldb2-backup-failed: cyrus-sasl2/backup-sasldb2: /var/backups/sasldb2.bak cyrus-sasl2/upgrade-sasldb2-failed:
Bug#1019270: cups-browsed: Query to /proc/sys/net/ipv6/conf/all/disable_ipv6 blocked by AppArmor, spamming syslog
Hi, On 04.12.22 18:53, Boyuan Yang wrote: Any update on this patch? I intend to do several bug fixing uploads for the debian-printing packages during my Christmas break. So please be patient a little bit longer. Thorsten
Bug#1025435: u-boot-menu: no way to specify unversioned FDT path if versioned default path is present
On Sonntag, 4. Dezember 2022 18:20:38 CET Jonas Smedegaard wrote:
> Quoting Nicolas Frattaroli (2022-12-04 18:03:30)
> > if I specify U_BOOT_FDT to be an absolute path, it won't be
> > used by u-boot-update if the default version FDT directory
> > exists.
> >
> > u-boot-update should check as the very first thing for FDT
> > line generation whether the path begin with an /, and if
> > it does, the file exists, and U_BOOT_FDT_DIR is either
> > default or empty (which gets set to default) make it use
> > the U_BOOT_FDT file as-is.
> >
> > This would allow for packages to provide supplemental device trees
> > without replacing the whole kernel.
>
> Thanks for reporting.
>
> Would it be possible for you to provide a draft proposed change as a
> unified diff file, and a (more concrete) example of how the change is
> useful?
>
> No need for a perfect patch - just helpful if you can provide something
> more concrete.
>
>
> Kind regards,
>
> - Jonas
>
>
Hello,
thank you for the quick response.
A more concrete example is this defaults file:
U_BOOT_FDT=/usr/lib/devicetrees-plebian-quartz64/rockchip/rk3566-soquartz-blade.dtb
U_BOOT_FDT_DIR=""
The expected output would be an fdt line in extlinux.conf with
fdt /usr/lib/devicetrees-plebian-quartz64/rockchip/rk3566-soquartz-blade.dtb
even if /usr/lib/linux-image-$KERNELVERSION exists.
The use-case for this is to provide a separate device trees package
on my Debian live image on my SBCs that contains device trees which
are modified from what Debian's kernel ships, or ones it doesn't
ship at all. Since device trees are forwards- and backwards
compatible, and the drivers I care about for the SoC have already
been mainlined for a while, I really only need to give it some
device trees.
The idea behind shipping Debian's kernel package rather than my own
is that I don't want my users to be left stranded with an out of
date kernel should I die in a tragic blimp accident.
Here's a (somewhat untested in this iteration) patch:
---
diff --git a/u-boot-update b/u-boot-update
index 69da211..e5ffb22 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -182,7 +182,10 @@ do
else
_INITRD=""
fi
- if [ -e "${_BOOT_PATH}${U_BOOT_FDT_DIR}${_VERSION}/${U_BOOT_FDT}" ] &&
[ -n "${U_BOOT_FDT}" ]
+ if [ -e ${U_BOOT_FDT} ] && [ -n "${U_BOOT_FDT}" ] && [ "/" = $(echo
"${U_BOOT_FDT}" | head -c1) ]
+ then
+ _FDT="fdt ${U_BOOT_FDT}"
+ elif [ -e "${_BOOT_PATH}${U_BOOT_FDT_DIR}${_VERSION}/${U_BOOT_FDT}" ]
&& [ -n "${U_BOOT_FDT}" ]
then
_FDT="fdt ${U_BOOT_FDT_DIR}${_VERSION}/${U_BOOT_FDT}"
elif [ -d "${_BOOT_PATH}${U_BOOT_FDT_DIR}${_VERSION}/" ]
Bug#1022122: node-minimatch 3.0.4+~3.0.3-1+deb11u1 flagged for acceptance
On 04/12/2022 19:11, Adam D. Barratt wrote: [...] Hi, no that's the reverse, I cleaned deb11u1 patch in deb11u2, see https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1022122;filename=node-minimatch_3.0.4%2B~3.0.3-1%2Bdeb11u1%2Bdeb11u2.debdiff;msg=42 (cumulative debdiff) Right, apparently I was confused by the (not entirely clear, at least to me) filenames. Regards, Adam Yes, sorry I introduced unneeded changes in deb11u1. deb11u2 cleans this and fixes node-glob regression
Bug#1025440: FTBFS: fails to compile with Java errors
Source: starjava-ttools Version: 3.4.7-2 Severity: serious Tags: ftbfs Dear Maintainer, starjava-ttools fails to build from source, see https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/starjava-ttools.html for detailed log output. The main errors seem to be com.sun.* imports. I've also seen the same build failure when the package got synced to Ubuntu (https://launchpad.net/ubuntu/+source/starjava-ttools/3.4.7-2/+build/24622556) as well as locally on my Sid system. Not sure what might have changed since the package got uploaded in the first place. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/3 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 -- mvh / best regards Hans Joachim Desserud http://desserud.org
Bug#1023710: jbigkit: diff for NMU version 2.1-6.1
Control: tags 1023710 + patch Control: tags 1023710 + pending Dear maintainer, I've prepared an NMU for jbigkit (versioned as 2.1-6.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru jbigkit-2.1/debian/changelog jbigkit-2.1/debian/changelog --- jbigkit-2.1/debian/changelog 2022-10-11 01:46:00.0 +0200 +++ jbigkit-2.1/debian/changelog 2022-12-04 19:16:16.0 +0100 @@ -1,3 +1,10 @@ +jbigkit (2.1-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix autopkgtest (Closes: #1023710) + + -- Jochen Sprickerhof Sun, 04 Dec 2022 19:16:16 +0100 + jbigkit (2.1-6) unstable; urgency=medium * Rehome JBIGKit packaging onto salsa.debian.org diff -Nru jbigkit-2.1/debian/tests/run-unit-test jbigkit-2.1/debian/tests/run-unit-test --- jbigkit-2.1/debian/tests/run-unit-test 2022-10-11 01:46:00.0 +0200 +++ jbigkit-2.1/debian/tests/run-unit-test 2022-12-04 19:12:00.0 +0100 @@ -1,4 +1,6 @@ #!/bin/sh +set -e + +cd debian/tests make -f unittests-Makefile -j1 test -exit $? signature.asc Description: PGP signature
Bug#1025439: maelstrom: Crashes on startup: couldn't create staging surface
Package: maelstrom Version: 3.0.7-4 Severity: important Dear Maintainer, Maelstrom crashes on startup with the following error message: $ maelstrom Fatal: Couldn't create staging surface: Parameter 'pitch' is invalid Originally reported in Ubuntu as https://bugs.launchpad.net/ubuntu/+source/maelstrom/+bug/1995534 but I am able to reproduce this on Debian Sid and it doesn't seem related to graphics card -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/3 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 maelstrom depends on: ii libc6 2.36-5 ii libgcc-s1 12.2.0-9 ii libsdl2-2.0-0 2.24.2+dfsg-1 ii libsdl2-net-2.0-0 2.2.0+dfsg-2 ii libstdc++6 12.2.0-9 maelstrom recommends no packages. maelstrom suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim Desserud http://desserud.org
Bug#1022122: node-minimatch 3.0.4+~3.0.3-1+deb11u1 flagged for acceptance
On Sun, 2022-12-04 at 19:07 +0100, Yadd wrote: > On 04/12/2022 19:03, Adam D. Barratt wrote: > > On Tue, 2022-11-29 at 11:14 +0100, Yadd wrote: > > > On 29/11/2022 10:56, Yadd wrote: > > > > On 28/11/2022 22:11, Paul Gevers wrote: > > > > > Hi Yadd, > > > > > > > > > > On Sat, 26 Nov 2022 13:01:22 + Adam D Barratt > > > > > wrote: > > > > > > The upload referenced by this bug report has been flagged > > > > > > for > > > > > > acceptance into the proposed-updates queue for Debian > > > > > > bullseye. > > > > > > > > > > > > Thanks for your contribution! > > > > > > > > > > > > Upload details > > > > > > == > > > > > > > > > > > > Package: node-minimatch > > > > > > Version: 3.0.4+~3.0.3-1+deb11u1 > > > > > > > > > > > > Explanation: improve protection against regular expression- > > > > > > based > > > > > > denial of service [CVE-2022-3517] > > > > > > > > > > The upload breaks [1] the autopkgtest of node-glob. Can you > > > > > have > > > > > a look? > > > > > > > [...] > > > > the problem is in this part of minimatch.js patch: > > > > > > > > @@ -280,7 +306,7 @@ > > > > if (pattern === '') return '' > > > > > > > > var re = '' > > > > - var hasMagic = !!options.nocase > > > > + var hasMagic = false > > > > var escaping = false > > > > // ? => one single character > > > > var patternListStack = [] > > > > > > > > We should apply this patch: > > > > https://github.com/isaacs/minimatch/commit/e4cd4346 > > > > > > > > I'm going to prepare a new upload > > > > > > Here is a new debdiff: > > >* this cleans CVE-2022-3517 patch (package*.json changes not > > > needed) > > >* this includes regressions fixes from 3.0.6 and 3.0.7 > > > > > > > If the huge package*.json changes aren't needed, then why are they > > included? Your stable -> deb11u2 diff contains a *lot* of noise > > with > > the changes to package-lock.json. > > > > Other than that, the patch does look like it's just the (still > > quite > > large) changes from upstream relating to the CVE, so please go > > ahead. > > > > Regards, > > Hi, > > no that's the reverse, I cleaned deb11u1 patch in deb11u2, see > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1022122;filename=node-minimatch_3.0.4%2B~3.0.3-1%2Bdeb11u1%2Bdeb11u2.debdiff;msg=42 > > (cumulative debdiff) > Right, apparently I was confused by the (not entirely clear, at least to me) filenames. Regards, Adam
Bug#1018360: funcparserlib: diff for NMU version 1.0.0-0.2
Control: tags -1 + patch Control: tags -1 + pending Dear maintainer, I've prepared an NMU for funcparserlib (versioned as 1.0.0-0.2). The diff is attached to this message. I have uploaded it to mentors, and require a sponsor to have it uploaded. Regards, Håvarddiff -Nru funcparserlib-1.0.0/debian/changelog funcparserlib-1.0.0/debian/changelog --- funcparserlib-1.0.0/debian/changelog2022-08-15 20:47:50.0 +0200 +++ funcparserlib-1.0.0/debian/changelog2022-12-04 18:40:13.0 +0100 @@ -1,3 +1,10 @@ +funcparserlib (1.0.0-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Remove python3-nose as BD. Closes: #1018360 + + -- Håvard F. Aasen Sun, 04 Dec 2022 18:40:13 +0100 + funcparserlib (1.0.0-0.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru funcparserlib-1.0.0/debian/control funcparserlib-1.0.0/debian/control --- funcparserlib-1.0.0/debian/control 2022-08-15 20:47:50.0 +0200 +++ funcparserlib-1.0.0/debian/control 2022-12-04 18:40:13.0 +0100 @@ -5,7 +5,6 @@ dh-python, python3-all, python3-setuptools, - python3-nose Standards-Version: 4.5.1 Section: python Homepage: https://github.com/vlasovskikh/funcparserlib diff -Nru funcparserlib-1.0.0/debian/rules funcparserlib-1.0.0/debian/rules --- funcparserlib-1.0.0/debian/rules2022-08-15 20:47:50.0 +0200 +++ funcparserlib-1.0.0/debian/rules2022-12-04 18:40:13.0 +0100 @@ -2,7 +2,6 @@ #export DH_VERBOSE=1 export PYBUILD_NAME=funcparserlib -export PYBUILD_TEST_NOSE=1 %: dh $@ --with python3 --buildsystem=pybuild
Bug#1019270: cups-browsed: Query to /proc/sys/net/ipv6/conf/all/disable_ipv6 blocked by AppArmor, spamming syslog
在 2022-12-04星期日的 19:06 +0100，Thorsten Alteholz写道： > Hi, > > On 04.12.22 18:53, Boyuan Yang wrote: > > Any update on this patch? > > I intend to do several bug fixing uploads for the debian-printing > packages during my Christmas break. So please be patient a little bit > longer. Great, Thanks! Best, Boyuan signature.asc Description: This is a digitally signed message part
Bug#1025438: RFS: funcparserlib/1.0.0-0.2 [NMU] -- Recursive descent parsing library for python3
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "funcparserlib": * Package name : funcparserlib Version : 1.0.0-0.2 Upstream contact : * URL : https://github.com/vlasovskikh/funcparserlib * License : Expat * Vcs : Section : python The source builds the following binary packages: python3-funcparserlib - Recursive descent parsing library for python3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/funcparserlib/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/f/funcparserlib/funcparserlib_1.0.0-0.2.dsc Changes since the last upload: funcparserlib (1.0.0-0.2) unstable; urgency=medium . * Non-maintainer upload. * Remove python3-nose as BD. Closes: #1018360 Regards, Håvard
Bug#1022122: node-minimatch 3.0.4+~3.0.3-1+deb11u1 flagged for acceptance
On 04/12/2022 19:03, Adam D. Barratt wrote: On Tue, 2022-11-29 at 11:14 +0100, Yadd wrote: On 29/11/2022 10:56, Yadd wrote: On 28/11/2022 22:11, Paul Gevers wrote: Hi Yadd, On Sat, 26 Nov 2022 13:01:22 + Adam D Barratt wrote: The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-minimatch Version: 3.0.4+~3.0.3-1+deb11u1 Explanation: improve protection against regular expression- based denial of service [CVE-2022-3517] The upload breaks [1] the autopkgtest of node-glob. Can you have a look? [...] the problem is in this part of minimatch.js patch: @@ -280,7 +306,7 @@ if (pattern === '') return '' var re = '' - var hasMagic = !!options.nocase + var hasMagic = false var escaping = false // ? => one single character var patternListStack = [] We should apply this patch: https://github.com/isaacs/minimatch/commit/e4cd4346 I'm going to prepare a new upload Here is a new debdiff: * this cleans CVE-2022-3517 patch (package*.json changes not needed) * this includes regressions fixes from 3.0.6 and 3.0.7 If the huge package*.json changes aren't needed, then why are they included? Your stable -> deb11u2 diff contains a *lot* of noise with the changes to package-lock.json. Other than that, the patch does look like it's just the (still quite large) changes from upstream relating to the CVE, so please go ahead. Regards, Hi, no that's the reverse, I cleaned deb11u1 patch in deb11u2, see https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1022122;filename=node-minimatch_3.0.4%2B~3.0.3-1%2Bdeb11u1%2Bdeb11u2.debdiff;msg=42 (cumulative debdiff) Cheers, Yadd
Bug#1022122: node-minimatch 3.0.4+~3.0.3-1+deb11u1 flagged for acceptance
On Tue, 2022-11-29 at 11:14 +0100, Yadd wrote: > On 29/11/2022 10:56, Yadd wrote: > > On 28/11/2022 22:11, Paul Gevers wrote: > > > Hi Yadd, > > > > > > On Sat, 26 Nov 2022 13:01:22 + Adam D Barratt > > > wrote: > > > > The upload referenced by this bug report has been flagged for > > > > acceptance into the proposed-updates queue for Debian bullseye. > > > > > > > > Thanks for your contribution! > > > > > > > > Upload details > > > > == > > > > > > > > Package: node-minimatch > > > > Version: 3.0.4+~3.0.3-1+deb11u1 > > > > > > > > Explanation: improve protection against regular expression- > > > > based > > > > denial of service [CVE-2022-3517] > > > > > > The upload breaks [1] the autopkgtest of node-glob. Can you have > > > a look? > > > [...] > > the problem is in this part of minimatch.js patch: > > > > @@ -280,7 +306,7 @@ > > if (pattern === '') return '' > > > > var re = '' > > - var hasMagic = !!options.nocase > > + var hasMagic = false > > var escaping = false > > // ? => one single character > > var patternListStack = [] > > > > We should apply this patch: > > https://github.com/isaacs/minimatch/commit/e4cd4346 > > > > I'm going to prepare a new upload > > Here is a new debdiff: > * this cleans CVE-2022-3517 patch (package*.json changes not > needed) > * this includes regressions fixes from 3.0.6 and 3.0.7 > If the huge package*.json changes aren't needed, then why are they included? Your stable -> deb11u2 diff contains a *lot* of noise with the changes to package-lock.json. Other than that, the patch does look like it's just the (still quite large) changes from upstream relating to the CVE, so please go ahead. Regards, Adam
Bug#1025340: xserver-xorg: Xorg segfaults at start-up in recent Debian Live images
On Fri, 02 Dec 2022 Philip Hands wrote> Debian Live images built in the last day seem not to be able to start X. > > It segfaults at start-up, thus: > > [20.784] (EE) Backtrace: > [20.785] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x564d21cafc59] > [20.787] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) > [0x7f5d44e5af90] > [20.788] (EE) unw_get_proc_name failed: no unwind info found [-10] > [20.788] (EE) 2: /lib64/ld-linux-x86-64.so.2 (?+0x0) [0x7f5d45a99029] > [20.788] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 > (_dl_catch_exception+0x7a) [0x7f5d44f6de9a] > [20.789] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_error+0x2f) > [0x7f5d44f6df4f] > [20.789] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (dlerror+0x297) > [0x7f5d44ea3dc7] > [20.790] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (dlclose+0x36) > [0x7f5d44ea3b26] > [20.820] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so > (nouveau_drm_screen_create+0x1d50f4) [0x7f5d4326bf44] > [20.821] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so > (nouveau_drm_screen_create+0x1d4340) [0x7f5d4326b190] > [20.821] (EE) unw_get_proc_name failed: no unwind info found [-10] > [20.821] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (?+0x0) > [0x7f5d4282e179] > [20.832] (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so > (__driDriverGetExtensions_d3d12+0x60ae16) [0x7f5d42e39156] > [20.832] (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so > (__driDriverGetExtensions_d3d12+0x60ad84) [0x7f5d42e390c4] > [20.832] (EE) 12: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so > (__driDriverGetExtensions_d3d12+0x6f4) [0x7f5d4282ea34] > [20.833] (EE) 13: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so > (__driDriverGetExtensions_d3d12+0xa175) [0x7f5d428384b5] > [20.833] (EE) unw_get_proc_name failed: no unwind info found [-10] > [20.833] (EE) 14: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) > [0x7f5d44b6fd77] > [20.833] (EE) unw_get_proc_name failed: no unwind info found [-10] > [20.833] (EE) 15: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) > [0x7f5d44b6eb7f] > [20.834] (EE) 16: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) > [0x564d21b41a24] > [20.834] (EE) 17: /usr/lib/xorg/Xorg (dri3_send_open_reply+0x10af) > [0x564d21c6da9f] > [20.838] (EE) 18: /usr/lib/xorg/Xorg (InitExtensions+0x89) > [0x564d21bad2a9] > [20.838] (EE) 19: /usr/lib/xorg/Xorg (InitFonts+0x1e8) [0x564d21b404e8] > [20.838] (EE) 20: /lib/x86_64-linux-gnu/libc.so.6 > (__libc_init_first+0x8a) [0x7f5d44e4618a] > [20.839] (EE) 21: /lib/x86_64-linux-gnu/libc.so.6 > (__libc_start_main+0x85) [0x7f5d44e46245] > [20.839] (EE) 22: /usr/lib/xorg/Xorg (_start+0x21) [0x564d21b29b61] > [20.839] (EE) > [20.839] (EE) Segmentation fault at address 0x337 > [20.839] (EE) > Fatal server error: > [20.839] (EE) Caught signal 11 (Segmentation fault). Server aborting > > Full log file is here: > > https://openqa.debian.net/tests/101031/logfile?filename=Xorg.0.log.txt > > I'm not sure what's causing this, hence the bug report against > xserver-xorg. > > libglx-mesa0 seems like it _might_ be worth a look Looks like it is this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025312
Bug#1025437: AW: Bug#1025437: Acknowledgement (version 4.0.0 does not run with the current wtforms)
I forgot the error message: ... File "/usr/lib/python3/dist-packages/flask_security/__init__.py", line 15, in from .core import Security, RoleMixin, UserMixin, AnonymousUser, current_user File "/usr/lib/python3/dist-packages/flask_security/core.py", line 34, in from .forms import ( File "/usr/lib/python3/dist-packages/flask_security/forms.py", line 30, in from wtforms.fields.html5 import EmailField ModuleNotFoundError: No module named 'wtforms.fields.html5'
Bug#1019270: cups-browsed: Query to /proc/sys/net/ipv6/conf/all/disable_ipv6 blocked by AppArmor, spamming syslog
X-Debbugs-CC: alteh...@debian.org till.kamppe...@gmail.com Hi, Any update on this patch? If allowed, I can offer a deferred NMU with this targeted bugfix. Thanks, Boyuan Yang On Sun, 30 Oct 2022 00:56:47 -0400 Boyuan Yang wrote: > Control: tags -1 +patch > X-Debbugs-CC: alteh...@debian.org till.kamppe...@gmail.com > > Dear Debian cups-filters maintainers, > > On Tue, 06 Sep 2022 13:08:34 -0400 Boyuan Yang wrote: > > Package: cups-browsed > > Version: 1.28.16-1 > > Severity: normal > > > > Dear Debian cups-filters packagers, > > > > On my current Debian/Sid system (as of Sep 2022), the syslog keeps > printing > > the following messages: > > > > kernel: audit: type=1400 audit(1662483939.030:193): apparmor="DENIED" > > operation="open" profile="/usr/sbin/cups-browsed" > > name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336 comm="cups- > browsed" > > requested_mask="r" denied_mask="r" fsuid=0 ouid=0 > > > > kernel: audit: type=1400 audit(1662483939.030:194): apparmor="DENIED" > > operation="open" profile="/usr/sbin/cups-browsed" > > name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336 comm="cups- > browsed" > > requested_mask="r" denied_mask="r" fsuid=0 ouid=0 > > > > audit[3336]: AVC apparmor="DENIED" operation="open" > profile="/usr/sbin/cups- > > browsed" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336 > > comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 > > > > audit[3336]: AVC apparmor="DENIED" operation="open" > profile="/usr/sbin/cups- > > browsed" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336 > > comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 > > > > > > > > These logs keeps spam my syslog. Please consider looking into it and > adjust > > AppArmor profile or cups-browsed program accordingly. > > Since cups-browsed only needs to read > /proc/sys/net/ipv6/conf/all/disable_ipv6 to determine whether ipv6 is > disabled, I believe this request should be allowed by AppArmor. > > As a result, I am attaching the following one-liner patch (see attachment). > Please consider applying it to avoid spamming syslog journal. > > > > --- a/debian/apparmor/usr.sbin.cups-browsed > +++ b/debian/apparmor/usr.sbin.cups-browsed > @@ -17,6 +17,9 @@ > /var/log/cups/* rw, > /tmp/** rw, > > + # Allow reading system ipv6 status > + /proc/sys/net/ipv6/conf/all/disable_ipv6 r, > + ># Courtesy to the Debian Edu team... >/etc/cups/cups-browsed-debian-edu.conf r, > signature.asc Description: This is a digitally signed message part
Bug#1025437: version 4.0.0 does not run with the current wtforms
Package: python3-flask-security Version: 4.0.0-1 Severity: important I think the current version of flask-security solves this problem. Sincerly Sebastian -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) 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 python3-flask-security depends on: ii python3 3.10.6-1 ii python3-email-validator 1.1.2-1 ii python3-flask2.0.3-1 ii python3-flask-login 0.6.2-1 ii python3-flask-mail 0.9.1+dfsg1-2 ii python3-flask-principal 0.4.0-4 ii python3-flaskext.wtf 1.0.1-2 ii python3-itsdangerous 2.1.2-3 ii python3-passlib 1.7.4-3 ii python3-speaklater 1.3-6 python3-flask-security recommends no packages. python3-flask-security suggests no packages. -- no debconf information
Bug#967669: opencfu: depends on deprecated GTK 2
Control: tags -1 upstream
Bug#1025424: beast-mcmc: please enable autopkgtest
Control: tags -1 help Hi Andrius, Am Sun, Dec 04, 2022 at 03:34:44PM +0200 schrieb Andrius Merkys: > I have recently worked on beast-mcmc and noticed it has an outline of a > possible autopkgtest in debian/tests/run-unit-test, but debian/tests/control > is missing. I have not tried running debian/tests/run-unit-test, but from > its existence I assume the autopkgtest is left unfinished. Thanks for reminding me about this. I admit I do not really remember why I stopped with this. Currently I'm running into OpenCL error: CL_DEVICE_NOT_FOUND from file , line 122. I currently do not have any clue how to fix this. Kind regards Andreas. -- http://fam-tille.de
Bug#1025436: lintian: Silence executable-stack-in-shared-library tag on mips*
Package: lintian Version: 2.115.3 Severity: important Hi! It seems that glibc forces an executable stack on MIPS architectures (see #1022787). On mipsel and mips64el architectures this is causing for all shared libraries the emission of the executable-stack-in-shared-library tag. As that report does not seem that it will be handled for bullseye, it would be nice if the tag could be silenced on these architectures, as there is nothing maintainers can really do about this, which is actually leading them into dead ends and incorrect fix attempts. Thanks, Guillem
Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4
forwarded 1012382 https://github.com/KIT-Telematics/pktanon/issues/8 tags 1012382 upstream thanks Hi, Your package has an autopkgtest, great. However, it fails on s390x. I have attached the relevant piece of the log [1]. I'd like to note that s390x is big-endian. Maybe the check for the version fails somehow? I assume that pktanon simply isn't portable enough to work on architectures not intended by upstream. I have opened an issue in upstream's GitHub [0] -- but as a previous one [1] regarding ARM issues remained unanswered I assume that portability to some exotic platforms is probably not a high priority. TBH I could live with that as well. Since pktanon does not seem to work reliably on that platform, I am going to remove s390x from the list of supported platforms to allow it to migrate to testing. Cheers Sascha [0] https://github.com/KIT-Telematics/pktanon/issues/8 [1] https://github.com/KIT-Telematics/pktanon/issues/7 OpenPGP_signature Description: OpenPGP digital signature
Bug#1025435: u-boot-menu: no way to specify unversioned FDT path if versioned default path is present
Quoting Nicolas Frattaroli (2022-12-04 18:03:30) > if I specify U_BOOT_FDT to be an absolute path, it won't be > used by u-boot-update if the default version FDT directory > exists. > > u-boot-update should check as the very first thing for FDT > line generation whether the path begin with an /, and if > it does, the file exists, and U_BOOT_FDT_DIR is either > default or empty (which gets set to default) make it use > the U_BOOT_FDT file as-is. > > This would allow for packages to provide supplemental device trees > without replacing the whole kernel. Thanks for reporting. Would it be possible for you to provide a draft proposed change as a unified diff file, and a (more concrete) example of how the change is useful? No need for a perfect patch - just helpful if you can provide something more concrete. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#848055: golang-github-go-chef-chef: diff for NMU version 0.0.1+git20161023.60.deb8c38-1.2
Control: tags 848055 + pending
Dear maintainer,
I've prepared an NMU for golang-github-go-chef-chef (versioned as
0.0.1+git20161023.60.deb8c38-1.2) and uploaded it to DELAYED/2.
Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog
--- golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog 2021-01-09 17:26:27.0 +0200
+++ golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog 2022-12-04 19:02:27.0 +0200
@@ -1,3 +1,10 @@
+golang-github-go-chef-chef (0.0.1+git20161023.60.deb8c38-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for intermittent test failures. (Closes: #848055)
+
+ -- Adrian Bunk Sun, 04 Dec 2022 19:02:27 +0200
+
golang-github-go-chef-chef (0.0.1+git20161023.60.deb8c38-1.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch
--- golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch 1970-01-01 02:00:00.0 +0200
+++ golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch 2022-12-04 19:02:27.0 +0200
@@ -0,0 +1,107 @@
+From b8a5b9cbb7b472eba5c1e2759aa6c288b8251de1 Mon Sep 17 00:00:00 2001
+From: markgibbons
+Date: Sat, 7 Dec 2019 07:10:13 -0800
+Subject: Fix the intermittent failures in the String tests
+
+diff --git a/client_test.go b/client_test.go
+index ad7aff7..7daeeaf 100644
+--- a/client_test.go
b/client_test.go
+@@ -40,15 +40,17 @@ func TestClientsService_List(t *testing.T) {
+ mux.HandleFunc("/clients", func(w http.ResponseWriter, r *http.Request) {
+ fmt.Fprintf(w, `{"client1": "http://localhost/clients/client1";, "client2": "http://localhost/clients/client2"}`)
+ })
+-
+ response, err := client.Clients.List()
+ if err != nil {
+ t.Errorf("Clients.List returned error: %v", err)
+ }
+
++ // The order printed by the String function is not defined
+ want := "client1 => http://localhost/clients/client1\nclient2 => http://localhost/clients/client2\n";
+- if response.String() != want {
+- t.Errorf("Clients.List returned:\n%+v\nwant:\n%+v\n", response.String(), want)
++ want2 := "client2 => http://localhost/clients/client2\nclient1 => http://localhost/clients/client1\n";
++ rstr := response.String()
++ if rstr != want && rstr != want2 {
++ t.Errorf("Clients.List returned:\n%+v\nwant:\n%+v\n", rstr, want)
+ }
+ }
+
+diff --git a/databag_test.go b/databag_test.go
+index 5ea7514..071fc4b 100644
+--- a/databag_test.go
b/databag_test.go
+@@ -157,8 +157,11 @@ func TestDataBagsService_UpdateItem(t *testing.T) {
+
+ func TestDataBagsService_DataBagListResultString(t *testing.T) {
+ e := &DataBagListResult{"bag1": "http://localhost/data/bag1";, "bag2": "http://localhost/data/bag2"}
++ // The output order is not guarenteed by the String function, check for either order
+ want := "bag1 => http://localhost/data/bag1\nbag2 => http://localhost/data/bag2\n";
+- if e.String() != want {
+- t.Errorf("DataBagListResult.String returned:\n%+v\nwant:\n%+v\n", e.String(), want)
++ want2 := "bag2 => http://localhost/data/bag2\nbag1 => http://localhost/data/bag1\n";
++ ebag := e.String()
++ if ebag != want && ebag != want2 {
++ t.Errorf("DataBagListResult.String returned:\n%+v\nwant:\n%+v\n", ebag, want)
+ }
+ }
+diff --git a/environment_test.go b/environment_test.go
+index 1bb7470..ff1b37a 100644
+--- a/environment_test.go
b/environment_test.go
+@@ -143,16 +143,19 @@ func TestEnvironmentsService_Put(t *testing.T) {
+
+ func TestEnvironmentsService_EnvironmentListResultString(t *testing.T) {
+ e := &EnvironmentResult{"_default": "https://api.opscode.com/organizations/org_name/environments/_default";, "webserver": "https://api.opscode.com/organizations/org_name/environments/webserver"}
++ estr := e.String()
+ want := "_default => https://api.opscode.com/organizations/org_name/environments/_default\nwebserver => https://api.opscode.com/organizations/org_name/environments/webserver\n";
+- if e.String() != want {
+- t.Errorf("EnvironmentResult.String returned:\n%+v\nwant:\n%+v\n", e.String(), want)
++ want2 := "webserver => https://api.opscode.com/organizations/org_name/environments/webserver\n_default => https://api.opscode.com/organizations/org_name/environments/_default\n";
++ if estr != want && estr != want2 {
++ t.Errorf("EnvironmentResult.String returned:\n%+v\nwant:\n%+v\n", estr, want)
+ }
+ }
+
+ func TestEnvironmentsService_EnvironmentCreateResultStrin
Bug#1025435: u-boot-menu: no way to specify unversioned FDT path if versioned default path is present
Package: u-boot-menu Version: 4.1.0 Severity: normal X-Debbugs-Cc: frattaroli.nico...@gmail.com Dear Maintainer, if I specify U_BOOT_FDT to be an absolute path, it won't be used by u-boot-update if the default version FDT directory exists. u-boot-update should check as the very first thing for FDT line generation whether the path begin with an /, and if it does, the file exists, and U_BOOT_FDT_DIR is either default or empty (which gets set to default) make it use the U_BOOT_FDT file as-is. This would allow for packages to provide supplemental device trees without replacing the whole kernel. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.1.0-rc7-plebian-g7ca751194ac4 (SMP w/4 CPU threads) 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 u-boot-menu depends on: ii linux-base 4.9 u-boot-menu recommends no packages. Versions of packages u-boot-menu suggests: pn flash-kernel -- Configuration Files: /etc/default/u-boot changed [not included] -- no debconf information
Bug#1025307: yosys mips64el build failure (fix)
Hi, I agree if you only read the C then the code looks fine, if a bit odd. However, having looked at the coredump with gdb it seems the compiler optomises the dereference out and passes back a pointer to the soon to be invalid stack address rather than the value. It only crashes with the stack protection on and I initially struggled to reproduce the issue as I was using the upstream compiler flags. It isn't even handling endianness conversions as it copies the bytes in the same order they come in. I think their idea was to support architectures where you can't access an 32-bit int at an odd address. I'll try you patch and report back. Cheers, Scott
Bug#779707: Errors when reading dicomdir file: "No images found" / "Loading: DICM Error reading file"
Control: tags -1 upstream Control: forwarded -1 Erik Nolf Hi Erik, there is a long standing bug report in the Debian bug tracking system. I'd like to bring this to your attention in case you see any chance to enhance xmedcon. Kind regards Andreas. -- http://fam-tille.de
Bug#1025434: python3-installer: sometimes not all files are installed in the wheel
Package: python3-installer Version: 0.5.1+dfsg1-3 Severity: important Control: affects -1 src:asdf-astropy Dear maintainer, The package asdf-astropy recently switched to use pyproject.toml, and now the installation is myteriously incomplete: The package consists of a number of subpackages: $ du asdf_astropy 8 asdf_astropy/io/tests 16 asdf_astropy/io 8 asdf_astropy/resources/schemas/table 8 asdf_astropy/resources/schemas/time [...] When building interactively (on the shell) in a sid environment, the build is often complete -- it seems to depend on the installed packages (when git is installed, it is complete; without git often not). When building with pbuilder, on Salsa [1], or on buildd [2], the package is however missing all subpackages: --8<- dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" module I: pybuild base:240: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /builds/debian-astro-team/asdf-astropy/debian/output/source_dir/.pybuild/cpython3_3.11 /usr/lib/python3/dist-packages/setuptools/config/pyprojecttoml.py:108: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. warnings.warn(msg, _BetaConfiguration) running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/asdf_astropy copying asdf_astropy/_version.py -> build/lib/asdf_astropy [... no asdf_astropy/io files here ...] * Building wheel... Successfully built asdf_astropy-0.3.0-py3-none-any.whl I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.11 with "installer" module --8<- On a discussion on the debian-python@l.d.o list, Scott Kitterman suggested [3] that this may be a bug in python3-installer; that's why the bug is filed here. Please re-assign if not. This problem currently prevents a successfull build for asdf-astropy. Best regards Ole [1] https://salsa.debian.org/debian-astro-team/asdf-astropy/-/jobs/3605729 [2] https://buildd.debian.org/status/fetch.php?pkg=asdf-astropy&arch=all&ver=0.3.0-1&stamp=1670016252&raw=0 [3] https://lists.debian.org/debian-python/2022/12/msg00036.html
Bug#1025239: dia: All letters in menus vanish after rescaling the image if some texts have been inserted [forwarded bug]
Control: forwarded -1 https://gitlab.gnome.org/GNOME/dia/-/issues/534 Hello, Thanks for the report. I reproduced the bug and forwarded the report upstream. Philippe.
Bug#779707: Closing due to no response from reporter (Was: Errors when reading dicomdir file: "No images found" / "Loading: DICM Error reading file")
Control: reassign -1 libmdc3 Hi Axel, Am Sun, Dec 04, 2022 at 04:42:16PM +0100 schrieb Axel Beckert: > JFTR: Well, yes, you asked, but that mail > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779707#33) > never reached me as I'm not subscribed to the bug report and you did > neither Cc me directly nor 79707-submit...@bugs.debian.org: Sorry about this. > ... > Not sure if some of the issues I ran into with the other paths I tried > today (crash on "amide dicomdir" and "Import File (Guess)") should be > a separate issue or not. At least usability is horrible in many ways: > popups to acknowledge, fixed window size, broken progress windows, > etc. But then again it still just doesn't seem to cope with videos in > DICOM data sets and I'm not sure which issues are just follow up > issues and which are separate issues. Thanks a lot for your effort in this issue. I've reassigned the issue to libmdc3 since the library has bumped soname meanwhile. I'll forward the issue to xmedcom upstream. Kind regards Andreas. -- http://fam-tille.de
Bug#1020531: dia: creating a text element kills all GUI fonts [tagging unreproducible]
Control: tags -1 unreproducible Hello, Since I didn’t manage to reproduce the bug, but it seems there is a bug anyway (the error message, and the fact you needed to remove the ~/.dia folder), I keep the bug open, but add the unreproducible tag. Philippe.
Bug#1024834: dia: Properties dialog is grapically currupted [bug forwarded]
Control: forwarded -1 https://gitlab.gnome.org/GNOME/dia/-/issues/533 Hello, Thanks for the report. I reproduced the bug and forwarded the report upstream. Philippe.
Bug#967514: gwyddion: depends on deprecated GTK 2
Am Sun, Dec 04, 2022 at 02:37:56PM +0100 schrieb David Nečas (Yeti): > At some point in medium-term horizon we plan to break everything and > switch to GTK+3. However, I expect it will be deprecated by then > everything in Debian will be expected to port to GTK+6, or quantum > wearables, or something. I highly estimate statements based on facts. Thank you Andreas. -- http://fam-tille.de
Bug#1025433: Copyright issue
Source: linuxcnc src/rtapi/procfs_macros.h incorrectly attributes copyright. The original file can be found here: http://svn.savannah.gnu.org/viewvc/rtai/magma/base/include/rtai_proc_fs.h?view=markup
Bug#779707: Closing due to no response from reporter (Was: Errors when reading dicomdir file: "No images found" / "Loading: DICM Error reading file")
Control: reopen 779707 Control: found 779707 1.0.6-1 Hi Andreas, On Sun, Dec 04, 2022 at 11:23:35AM +0100, Andreas Tille wrote: > I tried to do something to solve the issue in 2015 and asked the reporter > whether this was helpful. JFTR: Well, yes, you asked, but that mail (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779707#33) never reached me as I'm not subscribed to the bug report and you did neither Cc me directly nor 79707-submit...@bugs.debian.org: > From: Andreas Tille > To: 671...@bugs.debian.org, 779...@bugs.debian.org > Subject: Could you please verify the bug with latest upstream So that's the reason why you never got an answer. So I try to answer this now. Took a moment to remember, which file I tried to open with Amide back in 2015, but my reply to Gert (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779707#15) helped to remember it. If I now try to open that "dicomdir" file directly on the command line, it just crashes: $ amide dicomdir [1]11595 IOT instruction (core dumped) amide dicomdir If I try to import it via the menues "Import File (specify)" → "DICOM 3.0 via (X)MedCon" I still get a similar error message, although a tiny bit more informative as it now also mentions "libmdc": First "AMIDE WARNING" popup: Can't read file […]/dicomdir with libmdc/(X)MedCon. Second "AMIDE WARNING" popup: Could not import data sets from file […]/dicomdir I then tried "Import File (guess)" with the "dicomdir" file. This did something else and got me this "AMIDE WARNING" which shows that it at least got a bit farther: Couldn't find ImageOrientationPatient in file […]/86617/86625/83 The path "[…]" is the same as above, i.e. the directory the "dicomdir" file is. Maybe this bit of information helps: $ file -L 86617/86625/83 86617/86625/83: DICOM medical imaging data A second such popup says: Couldn't find ImagePositionPatient nor SliceLocation in file […]/86617/86625/83 It though did something. An empty (and focus grabbing) popup "Progress Dialog" appeared 6 times and the whole application seems to be rather unresponsive during that time (which is kinda ok-ish). It also threw tons of GTK errors in terminal where I started it. Didn't capture the output and it was far more than the terminal's history. But it seems to be a repitition of these few messages: (amide:11820): GLib-GObject-WARNING **: 15:47:26.266: invalid uninstantiatable type '(null)' in cast to 'GtkProgressBar' (amide:11820): Gtk-CRITICAL **: 15:47:26.266: IA__gtk_progress_bar_set_fraction: assertion 'GTK_IS_PROGRESS_BAR (pbar)' failed (amide:11820): GLib-GObject-WARNING **: 15:47:26.267: invalid uninstantiatable type '(null)' in cast to 'GtkProgressBar' (amide:11820): Gtk-CRITICAL **: 15:47:26.267: IA__gtk_progress_bar_set_fraction: assertion 'GTK_IS_PROGRESS_BAR (pbar)' failed (amide:11820): GLib-GObject-WARNING **: 15:47:27.239: invalid unclassed pointer in cast to 'GtkLabel' (amide:11820): Gtk-CRITICAL **: 15:47:27.239: IA__gtk_label_set_text: assertion 'GTK_IS_LABEL (label)' failed (amide:11820): Gtk-CRITICAL **: 15:47:27.239: IA__gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (amide:11820): GLib-GObject-WARNING **: 15:47:27.239: invalid uninstantiatable type '(null)' in cast to 'GtkProgressBar' (amide:11820): Gtk-CRITICAL **: 15:47:27.239: IA__gtk_progress_bar_set_fraction: assertion 'GTK_IS_PROGRESS_BAR (pbar)' failed (amide:11820): GLib-GObject-WARNING **: 15:47:27.239: invalid uninstantiatable type '(null)' in cast to 'GtkProgressBar' (amide:11820): Gtk-CRITICAL **: 15:47:27.239: IA__gtk_progress_bar_set_fraction: assertion 'GTK_IS_PROGRESS_BAR (pbar)' failed (The blank lines were output as well. So citing them as well. These errors are likely related to the empty, i.e. non-working "Progress Dialog".) Then another "AMIDE WARNING" popup appeared saying: Couldn't find ImageOrientationPatient in file […]/8651/8652/8659 And immediately after closing that one another one: Couldn't find ImagePositionPatient nor SliceLocation in file […]/8651/8652/8659 And immediately after closing that one another one: Couldn't find ImageOrientationPatient in file […]/8651/8652/86516 And immediately after closing that one another one: Couldn't find ImagePositionPatient nor SliceLocation in file […]/8651/8652/86516 The last empty Progress Dialog window closes and another empty Progress Dialog appears. Then I get the popup pair: Couldn't find ImageOrientationPatient in file […]/8651/8654/86511 Couldn't find ImagePositionPatient nor SliceLocation in file […]/8651/8654/86511 etc. pp. Then, after a while of more such popups with always other file names, a different "AMIDE WARNING" popup shows up (and now I really curse that widget library for not being able to copy and paste this error message *g* — even a screenshot would not have worked as the popup is fixed size and just has a
Bug#1023119: RFS: cruft-ng/0.9.47 with new dh-cruft binary package -- tool that help identify system files)
Hi again, Please review the current package. 0.9.49 https://mentors.debian.net/package/cruft-ng/ It's in a really good shape and can also be trivially backported to Bullseye. Greetings > Please upload a source package to mentors.debian.net or elsewhere > and I will review and upload the package including dh-cruft. > > -- > bye, > pabs
Bug#1025244: RM: mercantile -- ROM; Unmaintained
Control: tags -1 - moreinfo xyzservices (2022.9.0-2) no longer depends on mercantile. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1025297: virtualbox guest segfault with 22.3
I can confirm Xorg segmentation fault in virtualbox guest with accelleration 3D disabled. - [ 5.108] (EE) Backtrace: [ 5.111] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56088d48ec59] [ 5.111] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7fec1f05af90] [ 5.112] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 5.112] (EE) 2: /lib64/ld-linux-x86-64.so.2 (?+0x0) [0x7fec1fc50029] [ 5.112] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_exception+0x7a) [0x7fec1f16de9a] [ 5.112] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_error+0x2f) [0x7fec1f16df4f] [ 5.112] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (dlerror+0x297) [0x7fec1f0a3dc7] [ 5.113] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (dlclose+0x36) [0x7fec1f0a3b26] [ 5.117] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (nouveau_drm_screen_create+0x1d50f4) [0x7fec122e7f44] [ 5.117] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (nouveau_drm_screen_create+0x1d4340) [0x7fec122e7190] [ 5.117] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 5.118] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (?+0x0) [0x7fec118aa179] [ 5.119] (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x60ae16) [0x7fec11eb5156] [ 5.119] (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x60ad84) [0x7fec11eb50c4] [ 5.119] (EE) 12: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x6f4) [0x7fec118aaa34] [ 5.119] (EE) 13: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0xa175) [0x7fec118b44b5] [ 5.119] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 5.119] (EE) 14: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fec1ed26d77] [ 5.119] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 5.119] (EE) 15: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fec1ed25b7f] [ 5.119] (EE) 16: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x56088d320a24] [ 5.119] (EE) 17: /usr/lib/xorg/Xorg (dri3_send_open_reply+0x10af) [0x56088d44ca9f] [ 5.120] (EE) 18: /usr/lib/xorg/Xorg (InitExtensions+0x89) [0x56088d38c2a9] [ 5.120] (EE) 19: /usr/lib/xorg/Xorg (InitFonts+0x1e8) [0x56088d31f4e8] [ 5.120] (EE) 20: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7fec1f04618a] [ 5.120] (EE) 21: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7fec1f046245] [ 5.120] (EE) 22: /usr/lib/xorg/Xorg (_start+0x21) [0x56088d308b61] [ 5.120] (EE) [ 5.120] (EE) Segmentation fault at address 0x337 [ 5.120] (EE) Fatal server error: [ 5.120] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 5.120] (EE) [ 5.120] (EE) --- Downgrading to 22.2.4 solves. Best, Luca.
Bug#1025420: exim4: ${run} expansion fail
On 2022-12-04 Slavko wrote:
> Package: exim4
> Version: 4.96-9
> Hi,
> yesterday (3.12.2022) discussion on exim's ML shows bug in ${run}
> expansion, which fails if there is another expansion, eg (not very
> useful, but shows problem):
> exim -be '${run{/usr/bin/echo ${quote:aaa}}}'
> Failed: Expansion of "${quote:aaa" from command "/usr/bin/echo
> ${quote:aaa" in ${run} expansion failed: missing } at end of string
> (note missing "}" after quote...)
> It is already fixed, perhaps worth to include it, just in case that new
> version will not be released until next stable, see:
> https://github.com/Exim/exim/commit/44b6e099b76f403a55e77650821f8a69e9d2682e
Thanks for the heads-up. Sadly the fix from master does not apply
directly to 4.96 due to some rework ("Args count reduction in expansions
coding").
cu Andreas
Bug#1025432: LXD - suggestion to moving dnsmasq to recommended dependencie
Package: lxd Severity: wishlist Hello, Following the discussion[1] on the Go mailing list. Please find this bug for my suggestion to move the dnsmasq dependency to recommended. For users who do not need a network solution managed by LXD, we cannot install LXD without installing dnsmasq. I suggest to move dnsmasq to recommended. For me, this corresponds to what is mentioned in the paragraph "DEBIAN POLICY Recommends, Suggests, and Enhances fields"[2] from The Debian Administrator's Handbook Most of debian user (I think) will not change option about recommended packages and they are installed. Related to LXD, most of Debian user will install dnsmasq with LXD and for those who wish to not use it, we will be able to not install it. I tested to break (mv /usr/sbin/dnsmasq /usr/sbin/dnsmasq) dnsmasq to check if LXD will have issue. I didn't found issue. All seems good. I hope that other user will send their opinion Sylvain [1] - https://lists.debian.org/debian-go/2022/12/msg6.html [2] - https://debian-handbook.info/browse/stable/sect.package-meta-information.html
Bug#1015607: qemu: ftbfs with LTO (link time optimization) enabled
FWIW, qemu already enables LTO by default where appropriate, when available. So basically, optimize=+lto has no effect (besides this FTBFS issue). /mjt
Bug#1025431: libdvd-pkg: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: libdvd-pkg Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450 pt_BR.po.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#1025430: grub2-common: transition to fuse3
Package: grub-common Version: 2.06-5 Dear Maintainer, libfuse version 2 is in maintenance mode. Please consider to transiton to the actively developed version 3. See also https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1935659 with the applied patch https://github.com/OpenMandrivaAssociation/grub2/blob/eefc4320f00fec29868437a9e7b6cb53e03cfb34/0144-grub-mount-Add-support-for-libfuse3.patch
Bug#1025429: virtualbox-ext-pack: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: virtualbox-ext-pack Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450 pt_BR.po.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#1025046: additional information
Package: zfs-dkms Version: 2.1.5-1~bpo11+1 I confirm this issue, here what I tested on debian 11.5 as of today: - linux-image-amd64 (5.10.149) and zfsutils-linux (2.0.3) both from bullseye => dkms build ok - linux-image-amd64 from bullseye (5.10.149) and zfsutils-linux from bullseye-backports (2.1.5) => dkms build ok - linux-image-amd64 (6.0.3) from bullseye-backports and zfsutils-linux from bullseye-backports (2.1.5) => build fails with same error "shrinker" as reported
Bug#1023460: in debian/nslcd.config, guess_ldap_uri returns the IP address instead of the name of the server
On Fri, 2022-11-04 at 11:00 -0400, Marvin Renich wrote: > When nslcd is installed [...] guess_ldap_uri tries to find an > appropriate ldap server using some heuristics. If it finds a host > [...] it returns the IP address of the host rather than the name. The original reason for this was that if you use LDAP for host name lookups having a host name in nslcd.conf causes problems. I think that is reasonably uncommon and agree that the host name would make more sense to provide as a suggestion. This behaviour will be changed in the next upload (uploads are not very frequent). Thanks, -- -- arthur - adej...@debian.org - https://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
