Bug#953525: snowball: Please make autopkgtests cross-test-friendly
Package: snowball
Version: 0+svn585-1.1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Hi Stefano,
In Ubuntu, we are in the process of moving the i386 architecture to a
compatibility-only layer on amd64, and therefore we are also moving our
autopkgtest infrastructure to test i386 binaries in a cross-environment.
This requires changes to some tests so that they are cross-aware and can do
the right thing.
The snowball tests currently fail in this environment, because one test is a
build test that does not invoke the toolchain in a cross-aware manner. I've
verified that the attached patch lets the tests successfully build (and run)
i386 tests on an amd64 host.
Note that upstream autopkgtest doesn't currently set DEB_HOST_ARCH so this
is a complete no-op in Debian for the moment. Support for cross-testing in
autopkgtest is currently awaiting review at
https://salsa.debian.org/ci-team/autopkgtest/merge_requests/69 and once
landed, will still have no effect unless autopkgtest is invoked with a '-a'
option. So this change should be safe to land in your package despite this
not being upstream in autopkgtest.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru snowball-0+svn585/debian/tests/compilation
snowball-0+svn585/debian/tests/compilation
--- snowball-0+svn585/debian/tests/compilation 2019-09-13 19:06:36.0
-0700
+++ snowball-0+svn585/debian/tests/compilation 2020-03-09 22:24:51.0
-0700
@@ -3,6 +3,12 @@
cd "$AUTOPKGTEST_TMP"
+if [ -n "${DEB_HOST_GNU_TYPE:-}" ]; then
+CROSS_COMPILE="$DEB_HOST_GNU_TYPE-"
+else
+CROSS_COMPILE=
+fi
+
cat > test.c << EOF
#include
#include
@@ -27,8 +33,8 @@
}
EOF
-gcc -o test test.c -l stemmer
+${CROSS_COMPILE}gcc -o test test.c -l stemmer
./test
-gcc -o test test.c -static -l stemmer
+${CROSS_COMPILE}gcc -o test test.c -static -l stemmer
./test
Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again
Hi Daniel, On Mon, Mar 09, 2020 at 12:42:48PM -0400, Daniel Kahn Gillmor wrote: > > gpgme1.0 only uses the most recent Python version, so we don't have to > > port <=3.7 here. > > What do you mean by this? > https://packages.debian.org/sid/amd64/python3-gpg/filelist includes > modules for python 3.7 and 3.8. Do you think it doesn't or shouldn't for > some reason? I'm a little puzzled as to why my patch made it cross build. Your observation seems entirely correct. In any case, I don't think that we will release bullseye with Python 3.7. So even if the patch means that gpgme cross builds python3-gpg without support for 3.7, I think that's a reasonable compromise when comparing maintenance cost vs. features. I suppose that the majority of cross build users would want the C library and not the Python bindings. Once 3.7 is removed, the issue "heals" itself, so I suggest not spending time on it. Does that work for you? If Python continues to be annoying, I'd propose the addition of a profile to reduce the scope of cross builds. Helmut
Bug#953524: RM: cajun -- ROM; Unfinished, unmaintained and orphaned package
Package: ftp.debian.org Severity: normal Hi, cajun seems: * unfinished: only a libcajun-dev is published without any libcajunX * unmaintained upstream: last commit 6 years ago * orphaned: MIA Then I think it is safe to remove this from Debian archive. This packaged is tagged as maintained by JS Team, however it is not related to JavaScript (JSON for C++). Cheers, Xavier $ dak rm -Rn cajun Will remove the following packages from unstable: cajun |2.0.3-2 | source libcajun-dev |2.0.3-2 | all Maintainer: Debian Javascript Maintainers --- Reason --- -- Checking reverse dependencies... No dependency problem found.
Bug#953449: [Pkg-javascript-devel] Bug#953449: Bug#953449: Updating the cajun Uploaders list
Le 09/03/2020 à 22:47, Mattia Rizzolo a écrit : > On Mon, Mar 09, 2020 at 10:18:13PM +0100, Xavier wrote: >> this package looks unfinished (libcajun-dev without binary), and not >> related to JS world. Also it looks unused (see below). Then I think it >> should be removed from Debian archive > > Please go ahead and ask for its removal it then :) > >> $ dakrn cajun > > 'r*n*' ? Sorry, local alias for ssh y...@mirror.ftp-master.debian.org dak rm -Rn cajun
Bug#953523: ITP: filetype.py -- Small module to infer binary file types via signature
Based on the module name and Python policy, the binary package name should be python3-filetype. That appears to be available. I'd suggest using that as the source package name too to make your life easier. Scott K
Bug#865266: upstream bug
tags 865266 +upstream thanks + checking for automake-1.11 >= 1.11 ... You must have automake-1.11 installed to compile Warzone2100. Download the appropriate package for your distribution, or get the source tarball at ftp://ftp.gnu.org/pub/gnu/automake/ dh_autoreconf: error: ./autogen.sh returned exit code 1 It doesn't work with newer automake and upstream specifically wrote it that way. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/
Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'
Package: python3-vtkplotter Followup-For: Bug #953235 Dodgy libgomp.so. See https://github.com/pytorch/pytorch/issues/2575
Bug#953523: ITP: filetype.py -- Small module to infer binary file types via signature
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho * Package name: filetype.py Version : 1.0.5 Upstream Author : Tomás Aparicio * URL : https://github.com/h2non/filetype.py * License : MIT Programming Lang: Python 3 Description : Small module to infer binary file types via signature Small and dependency free Python module to infer file type and MIME type checking the magic numbers signature of a file or buffer (aka file pattern). . This is a Python port from filetype Go package. . Features: - Simple and friendly API. - Supports a wide range of file types. - Provides file extension and MIME type inference. - File discovery by extension or MIME type. - File discovery by kind (image, video, audio...). - Pluggable: add new custom type matchers. - Fast, even processing large files. - Only first 261 bytes representing the max file header is required, so you can just pass a list of bytes. - Dependency free (just Python code, no C extensions, no libmagic bindings). - Cross-platform file recognition. . Currently, the following patterns are recognised: - Image: bmp, cr2, gif, heic, ico, jpg, jpx, jxr, png, psd, tif, webp. - Video: avi, flv, m4v, mkv, mov, mp4, mpg, webm, wmv. - Audio: amr, flac, m4a, mid, mp3, ogg, wav. - Archive: Z, ar, bz2, cab, crx, deb, eot, epub, exe, gz, lz, nes, pdf, ps, rar, rtf, sqlite, swf, tar, xz, zip, 7z. - Font: otf, ttf, woff, woff2.
Bug#953479: mopidy: Please move fonts-lato dependency to the recommended section
On 10.03.2020 00:39, Stein Magnus Jodal wrote: reassign 953479 sphinx-rtd-theme thanks On Mon, Mar 09, 2020 at 11:26:22PM +0200, Горбешко Богдан wrote: the fonts-lato is a pretty bloated dependency (more than 10 MB of disk space). It was mandatory for the ruby2.5 package when it just released, but then was moved to recommended. Please do the same. I don't think that using a fallback font will affect user experience in any significant way (only maybe if mopidy uses some Lato-specific font features). Hi! Mopidy does not depend on fonts-lato directly, only via Suggests on mopidy-doc, which Depends on sphinx-rtd-theme-common, which again Depends on fonts-lato. Thus, there is nothing that can be easily done with this from the perspective of src:mopidy. Reassigning to src:sphinx-rtd-theme. -- Stein Magnus Jodal Hmm, yes; though the reason is not the suggested mopidy-doc package, but the python3-pykka dependency, which started to depend on sphinx-rtd-theme-common. The latter is used by a lot of packages, so then I'm less sure that this change will have that minimal impact.
Bug#953522: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
Package: src:linux Version: 5.4.19-1 No idea where to report this. # update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
Bug#953521: meshlab: fails to run, it show libmeshlab-common.so: cannot open shared object file
Package: meshlab Version: 2020.02+git200217-1 Severity: normal -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-rc5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages meshlab depends on: ii lib3ds-1-3 1.3.0-9+b1 ii libc6 2.29-10 ii libgcc-s1 10-20200222-1 ii libgl1 1.3.1-1 ii libglew2.1 2.1.0-4+b1 ii libglu1-mesa [libglu1] 9.0.1-1 ii libgmp102:6.2.0+dfsg-4 ii libgomp110-20200222-1 ii libmuparser2v5 2.2.6.1+dfsg-1 ii libopenctm1 1.0.3+dfsg1-2.1 ii libqhull7 2015.2-4 ii libqt5core5a5.12.5+dfsg-9 ii libqt5gui5 5.12.5+dfsg-9 ii libqt5network5 5.12.5+dfsg-9 ii libqt5opengl5 5.12.5+dfsg-9 ii libqt5script5 5.12.5+dfsg-2 ii libqt5widgets5 5.12.5+dfsg-9 ii libqt5xml5 5.12.5+dfsg-9 ii libqt5xmlpatterns5 5.12.5-1 ii libstdc++6 10-20200222-1 Versions of packages meshlab recommends: ii chemical-mime-data 0.1.94-7 meshlab suggests no packages. -- no debconf information meshlab: error while loading shared libraries: libmeshlab-common.so: cannot open shared object file: No such file or directory ldd /usr/bin/meshlab libmeshlab-common.so => not found
Bug#953520: Build obs-studio for more architectures
Package: obs-studio Version: 24.0.6+dfsg1-1 Hi obs-studio maintainers: obs-studio upstream had introduced SIMDE [1] in version 25, and it's now RC. So now obs is nolonger tied on amd64. I had confirmed that it can be built on mips64el and arm64 [2], [3]. Please consider build it for more architectures when updating it. Btw: Is it possible to make it as a part of buster-backport? Thanks. [1]: https://github.com/obsproject/obs-studio/pull/2069 [2]: https://github.com/obsproject/obs-studio/pull/2341 [3]: https://github.com/obsproject/obs-studio/pull/2467
Bug#953519: liblapacke: undefined symbol in /usr/lib/x86_64-linux-gnu/liblapacke.so
Package: liblapacke Version: 3.9.0-1 Severity: normal Tags: a11y -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-rc5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages liblapacke depends on: ii libatlas3-base [liblapack.so.3]3.10.3-9 ii libblas3 [libblas.so.3]3.9.0-1 ii libc6 2.29-10 ii liblapack3 [liblapack.so.3]3.9.0-1 ii libopenblas0-pthread [liblapack.so.3] 0.3.8+ds-1 ii libtmglib3 3.9.0-1 liblapacke recommends no packages. liblapacke suggests no packages. -- no debconf information ldd -r /usr/lib/x86_64-linux-gnu/liblapacke.so marco@thinkPad linux-vdso.so.1 (0x7ffc44fd6000) libblas.so.3 => /lib/x86_64-linux-gnu/libblas.so.3 (0x7f4aa076a000) libtmglib.so.3 => /lib/x86_64-linux-gnu/libtmglib.so.3 (0x7f4aa0706000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4aa0546000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4aa0541000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4aa03fc000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f4aa03e2000) /lib64/ld-linux-x86-64.so.2 (0x7f4aa10b9000) undefined symbol: cgesvdq_ (/usr/lib/x86_64-linux-gnu/liblapacke.so) undefined symbol: dgesvdq_ (/usr/lib/x86_64-linux-gnu/liblapacke.so) undefined symbol: sgesvdq_ (/usr/lib/x86_64-linux-gnu/liblapacke.so) undefined symbol: zgesvdq_ (/usr/lib/x86_64-linux-gnu/liblapacke.so)
Bug#953518: ./doc/quickstartguide.html
I've attached the file that can't be converted to PDF on the build servers. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ quickstartguide.html.xz Description: application/xz
Bug#946996: wireguard-tools: 'wg-quick down' segfaults
On Mon, 09 Mar 2020 17:22:57 -0400 Daniel Kahn Gillmor wrote: > On Mon 2020-02-03 13:20:22 -0500, Celejar wrote: > > Okay, now I've gotten it. I've uninstalled nftables and put in the > > debug line, and I get this (with 1.0.20200121-2): > > > > ~# ifdown wg0 > > [#] ip -4 rule delete table 51820 > > [#] ip -4 rule delete table main suppress_prefixlength 0 > > [#] ip link delete dev wg0 > > [#] resolvconf -d tun.wg0 -f > > RESTORING: *filter > > COMMIT > > *nat > > COMMIT > > *mangle > > -D PREROUTING -p udp -m comment --comment "wg-quick(8) rule for wg0" -j > > CONNMARK --restore-mark --nfmask 0x --ctmask 0x > > -D POSTROUTING -p udp -m mark --mark 0xca6c -m comment --comment > > "wg-quick(8) rule for wg0" -j CONNMARK --save-mark --nfmask 0x > > --ctmask 0x > > COMMIT > > *raw > > COMMIT > > [#] iptables-restore -n > > /usr/bin/wg-quick: line 29: 2284068 Segmentation fault "$@" > > > OK, so it looks to me like the problem comes when feeding this set of > commands into iptables-restore. > > But hm, i'm still having trouble replicating the segfault. > > Is this still happening for you? Yes (with 1.0.20200206-2) > Can you send the output of these two commands? > > dpkg -l iptables wireguard ~$ dpkg -l iptables wireguard Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description ++ +-==-==-- ii iptables 1.8.4-3amd64administration tools for packet filtering and NAT ii wireguard 1.0.20200206-2 all fast, modern, secure kernel VPN tunnel (metapackage) > dpkg -S $(readlink -f $(which iptables-restore)) ~# dpkg -S $(readlink -f $(which iptables-restore)) iptables: /usr/sbin/xtables-nft-multi > That might help us narrow down the cause of the segfault. > > Sorry for how long this is taking to debug! Hey, wireguard itself seems entirely functional here - I'm just trying to do my tiny bit to help Debian! Thank you for all your work on this and Debian in general (and your privacy work). Celejar
Bug#953518: wkhtmltopdf: crash on alpha and ppc64
Package: wkhtmltopdf Version: 0.12.5-1+b2 Severity: normal https://buildd.debian.org/status/package.php?p=warzone2100 In the above build log you can see that warzone2100 doesn't build on alpha and ppc64 due to a wkhtmltopdf SEGV. There probably isn't anyone who wants to run warzone2100 on alpha, but there are some nice ppc64 workstations that would run it well. I'll update this bug report with the HTML file in question.
Bug#953517: Updating the node-util Uploaders list
Source: node-util Version: 0.10.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953514: Updating the loganalyzer Uploaders list
Source: loganalyzer Version: 4.1.5+dfsg-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953509: Updating the node-is-typedarray Uploaders list
Source: node-is-typedarray Version: 1.0.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953515: Updating the node-bowser Uploaders list
Source: node-bowser Version: 0.7.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953513: Updating the node-sdp-transform Uploaders list
Source: node-sdp-transform Version: 1.4.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953510: Updating the ganglia-nagios-bridge Uploaders list
Source: ganglia-nagios-bridge Version: 1.2.1-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953511: Updating the jquery-i18n-properties Uploaders list
Source: jquery-i18n-properties Version: 1.1.0-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953508: Updating the node-websocket Uploaders list
Source: node-websocket Version: 1.0.28-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953512: Updating the node-merge Uploaders list
Source: node-merge Version: 1.2.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953516: Updating the pegjs Uploaders list
Source: pegjs Version: 0.7.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953507: Updating the node-typedarray-to-buffer Uploaders list
Source: node-typedarray-to-buffer Version: 3.0.3-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953506: RFS: click-man/0.3.0-1 [ITP] -- Generate man pages for click based CLI applications - command (Python 3)
Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "click-man" * Package name: click-man Version : 0.3.0-1 Upstream Author : Timo Furrer * URL : https://github.com/click-contrib/click-man * License : Expat * Vcs : https://salsa.debian.org/rpavlik-guest/click-man Section : devel It builds those binary packages: python3-click-man - Generate man pages for click based CLI applications (Python 3) click-man - Generate man pages for click based CLI applications - command (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/click-man Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/click-man/click-man_0.3.0-1.dsc Changes since the last upload: * Initial Release. (Closes: #924099) Regards, Ryan A. Pavlik signature.asc Description: OpenPGP digital signature
Bug#953497: Updating the loganalyzer Uploaders list
Source: loganalyzer Version: 4.1.5+dfsg-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953501: Updating the node-sdp-transform Uploaders list
Source: node-sdp-transform Version: 1.4.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953498: Updating the node-bowser Uploaders list
Source: node-bowser Version: 0.7.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953503: Updating the node-util Uploaders list
Source: node-util Version: 0.10.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953499: Updating the node-is-typedarray Uploaders list
Source: node-is-typedarray Version: 1.0.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953502: Updating the node-typedarray-to-buffer Uploaders list
Source: node-typedarray-to-buffer Version: 3.0.3-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953504: Updating the node-websocket Uploaders list
Source: node-websocket Version: 1.0.28-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953496: Updating the jquery-i18n-properties Uploaders list
Source: jquery-i18n-properties Version: 1.1.0-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953505: Updating the pegjs Uploaders list
Source: pegjs Version: 0.7.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953500: Updating the node-merge Uploaders list
Source: node-merge Version: 1.2.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953495: Updating the ganglia-nagios-bridge Uploaders list
Source: ganglia-nagios-bridge Version: 1.2.1-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953032: Internal error: Could not resolve keysym XF86FullScreen
Glad somebody found the cause, because it could quickly fill up disks with logged error messages.
Bug#937277: NMU on the way
On Fri, 6 Mar 2020 19:33:19 +0200 Adrian Bunk wrote: > On Fri, Aug 30, 2019 at 03:00:10PM +, Debian Bug Tracking System wrote: > >... > > Architecture: source all > >... > >* Switch to python3 (thanks to Sandro Tosi for the patch) > > (Closes: > #935476, #937277) > > >... > > Thanks for fixing this in unstable. > > Could you make a source-only upload to allow testing migration? This is now blocking psycopg2 migration to Testing, so I'm going to upload an NMU to get it to migrate. Diff attached. Scott Kdiff -Nru pg-activity-1.5.0/debian/changelog pg-activity-1.5.0/debian/changelog --- pg-activity-1.5.0/debian/changelog 2019-08-29 04:04:54.0 -0400 +++ pg-activity-1.5.0/debian/changelog 2020-03-09 19:39:30.0 -0400 @@ -1,3 +1,10 @@ +pg-activity (1.5.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * No change source upload to allow fixes for #937277 to make it to Testing + + -- Scott Kitterman Mon, 09 Mar 2020 19:39:30 -0400 + pg-activity (1.5.0-1) unstable; urgency=medium * New upstream release signature.asc Description: This is a digitally signed message part.
Bug#953493: Add "Year 2038-OK certified version" statement to man page
Package: e2fsprogs Version: 1.45.5-2 File: /usr/share/man/man8/mke2fs.8.gz Please add to the mke2fs man page: ** This version of mke2fs is guaranteed to make filesystems that support timestamps *beyond* 2038. ** (The user will be looking for "2038" in the man page. Please be sure he finds something. Thanks.) "You can use it in full confidence that you will not get such kernel warnings upon mounting. No matter what the physical device the filesystem will be created on, no matter what version of Linux you are using." "The previous unfortunate behavior will never happen again, we promise." "You can verify which of your filesystems will still cause problems, even without needing to mount each one. Use e.g., # xyze2fs /dev/sdj6|grep xyz to find out."
Bug#953494: Document 2038 migration method
Package: e2fsprogs Version: 1.45.5-2 Idea: make a new file /usr/share/doc/e2fsprogs/Year2038warnings that would say: If you get ext4 filesystem being mounted at ... supports timestamps until 2038 (0x7fff) warnings, here is what to do. As there is no way to simply "tune" the old filesystem, we must copy the files to a new filesystem, and then make the UUID numbers the same (for those people who mention them in their fstabs and don't want to have to change them on each machine they use.) # mke2fs.ext4 /dev/somewhere # mount /mnt /dev/somewhere # cp -a /old/filesystem /mnt # umount /old/filesystem # [then some commands that makes the UUID numbers etc. disk label, on the new filesystem # just like the ones on the old filesystem, so we don't have to change # our fstabs etc.] # [then some command that changes the UUID number etc. of the old filesystem, # so it doesn't conflict with the new filesystem. For the weeks we still # will keep it around just in case.]
Bug#945172: firmware: failed to load rtw88/rtw8822b_fw.bin (workaround - correction)
The last line of "modprobe rtw8822b_fw.bin" was supposed to say "modprobe rtwpci". Sorry about that.
Bug#953492: RM: weupnp -- ROM; Not used, low popcon
Package: ftp.debian.org Severity: normal Hi, please remove the weupnp package, this package isn't used and has a low popcon. This was a jitsi dependency left over after its removal in 2017. Thank you, Emmanuel Bourg
Bug#940848: nfs-utils:CVE-2019-3689: root-owned files stored in insecure /var/lib/nfs
Upstream commit: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=fee2cc29e888f2ced6a76990923aef19d326dc0e
Bug#953491: zfs-auto-snapshot: Can't snapshot when com.sun:auto-snapshot is set to false
Package: zfs-auto-snapshot Version: 1.2.4-2 Hi, The manpage documents that you can set com.sun:auto-snapshot to false to disable the auto snapshot, and that you can use --default-exclude to reverse that behaviour. But --default-exclude doesn't seem to have any effect. When running: # zfs-auto-snapshot --syslog --label=daily --keep=60 --default-exclude // I just get: @zfs-auto-snap_daily-2020-03-09-2242, 0 created, 0 destroyed, 0 warnings. And I don't have any snapshot. I think it would also be useful if the --default-exclude wasn't needed in case don't use "//" but give the name directly. But giving the name directly, with or without --default-exclude also doesn't create a new snapshot. Kurt
Bug#953490: RM: jmxetric -- ROM; Not used, low popcon
Package: ftp.debian.org Severity: normal Hi, please remove the jmxetric package, this package isn't used, has a low popcon, and the project is dead upstream. Better and actively maintained alternatives like jmxtrans could be packaged as a replacement. Thank you, Emmanuel Bourg
Bug#953479: mopidy: Please move fonts-lato dependency to the recommended section
reassign 953479 sphinx-rtd-theme thanks On Mon, Mar 09, 2020 at 11:26:22PM +0200, Горбешко Богдан wrote: > the fonts-lato is a pretty bloated dependency (more than 10 MB of disk > space). > It was mandatory for the ruby2.5 package when it just released, but then was > moved to recommended. Please do the same. I don't think that using a > fallback > font will affect user experience in any significant way (only maybe if > mopidy > uses some Lato-specific font features). Hi! Mopidy does not depend on fonts-lato directly, only via Suggests on mopidy-doc, which Depends on sphinx-rtd-theme-common, which again Depends on fonts-lato. Thus, there is nothing that can be easily done with this from the perspective of src:mopidy. Reassigning to src:sphinx-rtd-theme. -- Stein Magnus Jodal signature.asc Description: PGP signature
Bug#953486: xow: binaries for non-free not auto-built
Hello Ivo, > If the binaries can be auto-built, the package should be whitelisted, as > described in > https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd This has been done already, I sent the email asking for the whitelisting yesterday and at this point I'm just waiting for it. Regards, -- Samuel Henrique
Bug#953488: powder: binaries for non-free not auto-built
package: src:powder version: 118+dfsg1-3 severity: serious tags: ftbfs Hi, The latest upload of powder to unstable has no binaries. The buildds are not building it, because it is in non-free. If the binaries can be auto-built, the package should be whitelisted, as described in https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd If not, a binary upload must be done (note that binary maintainer uploads for sources in contrib and non-free are allowed to migrate to testing). Cheers, Ivo
Bug#953489: php-horde-text-filter-jsmin: binaries for non-free not auto-built
package: src:php-horde-text-filter-jsmin version: 1.0.2-6 severity: serious tags: ftbfs Hi, The latest upload of php-horde-text-filter-jsmin to unstable has no binaries. The buildds are not building it, because it is in non-free. If the binaries can be auto-built, the package should be whitelisted, as described in https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd If not, a binary upload must be done (note that binary maintainer uploads for sources in contrib and non-free are allowed to migrate to testing). Cheers, Ivo
Bug#953486: xow: binaries for non-free not auto-built
package: src:xow version: 0.3-3 severity: serious tags: ftbfs Hi, The latest upload of xow to unstable has no binaries. The buildds are not building it, because it is in non-free. If the binaries can be auto-built, the package should be whitelisted, as described in https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd If not, a binary upload must be done (note that binary maintainer uploads for sources in contrib and non-free are allowed to migrate to testing). Cheers, Ivo
Bug#953487: runescape: binaries for non-free not auto-built
package: src:runescape version: 0.6-2 severity: serious tags: ftbfs Hi, The latest upload of runescape to unstable has no binaries. The buildds are not building it, because it is in non-free. If the binaries can be auto-built, the package should be whitelisted, as described in https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd If not, a binary upload must be done (note that binary maintainer uploads for sources in contrib and non-free are allowed to migrate to testing). Cheers, Ivo
Bug#953485: amiwm: binaries for non-free not auto-built
package: src:amiwm version: 0.21pl2-2 severity: serious tags: ftbfs Hi, The latest upload of amiwm to unstable has no binaries. The buildds are not building it, because it is in non-free. If the binaries can be auto-built, the package should be whitelisted, as described in https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd If not, a binary upload must be done (note that binary maintainer uploads for sources in contrib and non-free are allowed to migrate to testing). Cheers, Ivo
Bug#953483: RM: mercurial-server -- RoQA; Depends on Python 2, dead upstream, unmaintained
Package: ftp.debian.org Severity: normal Please remove mercurial-server. It depends on Python 2, is dead upstream and the last maintainer upload was in 2012. It even seems as it the package which ended up in Buster is broken (946667) Cheers, Moritz
Bug#951387: Please accept https://salsa.debian.org/installer-team/console-setup/merge_requests/3
Hi! On 3/9/20 10:33 PM, Nicholas D Steeves wrote: >> Hi, why such simple patch isn't accepted - 3 weeks already passed... >> > > Don't feel bad! Here's one I've been waiting three years for (tested > with custom install media in a VM): > > > https://salsa.debian.org/installer-team/partman-btrfs/-/merge_requests/1/commits I can have a look tomorrow. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#938567: starpy: diff for NMU version 1.0.1.0.git.20151124-2.1
Dear maintainer,
attached the debdiff for my NMU for starpy (versioned as
1.0.1.0.git.20151124-2.1)
Cheers,
Moritz
diff -Nru starpy-1.0.1.0.git.20151124/debian/changelog starpy-1.0.1.0.git.20151124/debian/changelog
--- starpy-1.0.1.0.git.20151124/debian/changelog 2017-08-01 22:59:50.0 +0200
+++ starpy-1.0.1.0.git.20151124/debian/changelog 2020-03-09 22:40:05.0 +0100
@@ -1,3 +1,10 @@
+starpy (1.0.1.0.git.20151124-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Cherrypick upstream commit to fix Python 3 compat (Closes: #938567)
+
+ -- Moritz Muehlenhoff Mon, 09 Mar 2020 22:40:05 +0100
+
starpy (1.0.1.0.git.20151124-2) unstable; urgency=medium
* Depend on python-setuptools (Closes: #867672)
diff -Nru starpy-1.0.1.0.git.20151124/debian/control starpy-1.0.1.0.git.20151124/debian/control
--- starpy-1.0.1.0.git.20151124/debian/control 2017-08-01 22:45:45.0 +0200
+++ starpy-1.0.1.0.git.20151124/debian/control 2020-03-09 22:40:05.0 +0100
@@ -5,19 +5,19 @@
# Add Paul Belanger as an uploaded, for now.
Uploaders: Tzafrir Cohen , Paul Belanger
Build-Depends: debhelper (>= 10),
- python,
+ python3,
dh-python,
- python-setuptools,
- python-twisted-core
+ python3-setuptools,
+ python3-twisted
X-Python-Version: >= 2.4
Standards-Version: 3.9.8
Homepage: https://github.com/asterisk/starpy
Vcs-Git: https://anonscm.debian.org/cgit/pkg-voip/starpy.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-voip/starpy.git
-Package: python-starpy
+Package: python3-starpy
Architecture: all
-Depends: python-twisted-core, ${misc:Depends}, ${python:Depends}
+Depends: python3-twisted, ${misc:Depends}, ${python3:Depends}
Recommends: asterisk
Description: Asterisk (AMI) protocols for Twisted Python
A Twisted Python protocol that provides access to the Asterisk PBX's Manager
diff -Nru starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch
--- starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch 1970-01-01 01:00:00.0 +0100
+++ starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch 2020-03-09 22:38:37.0 +0100
@@ -0,0 +1,267 @@
+From 7e43a8bafddd9e746dadf3ed4ec28fc79542dc25 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Rodrigo=20Ram=C3=ADrez=20Norambuena?=
+Date: Sat, 1 Oct 2016 14:24:14 -0300
+Subject: [PATCH] Add support code for Python 3
+
+Change-Id: I9ccd5a15be6e4129a5e0ce0bf1a5a4ff26998bac
+---
+ starpy/fastagi.py | 19 ++-
+ starpy/manager.py | 44 +---
+ tox.ini | 2 +-
+ 3 files changed, 40 insertions(+), 25 deletions(-)
+
+diff --git a/starpy/fastagi.py b/starpy/fastagi.py
+index 7a9b32e..7e26284 100644
+--- a/starpy/fastagi.py
b/starpy/fastagi.py
+@@ -127,7 +127,7 @@ def lineReceived(self, line):
+ try:
+ key, value = line.split(':', 1)
+ value = value[1:].rstrip('\n').rstrip('\r')
+-except ValueError, err:
++except ValueError as err:
+ log.error("""Invalid variable line: %r""", line)
+ else:
+ self.variables[key.lower()] = value
+@@ -135,7 +135,7 @@ def lineReceived(self, line):
+ else:
+ try:
+ df = self.pendingMessages.pop(0)
+-except IndexError, err:
++except IndexError as err:
+ log.warn("Line received without pending deferred: %r", line)
+ else:
+ if line.startswith('200'):
+@@ -148,7 +148,7 @@ def lineReceived(self, line):
+ try:
+ errCode, line = line.split(' ', 1)
+ errCode = int(errCode)
+-except ValueError, err:
++except ValueError as err:
+ errCode = 500
+ df.errback(error.AGICommandFailure(errCode, line))
+
+@@ -166,7 +166,7 @@ def checkFailure(self, result, failure='-1'):
+ # result code may have trailing information...
+ try:
+ resultInt, line = result.split(' ', 1)
+-except ValueError, err:
++except ValueError as err:
+ resultInt = result
+ if resultInt.strip() == failure:
+ raise error.AGICommandFailure(FAILURE_CODE, result)
+@@ -176,7 +176,7 @@ def resultAsInt(self, result):
+ """(Internal) Convert result to an integer value"""
+ try:
+ return int(result.strip())
+-except ValueError, err:
++except ValueError as err:
+ raise error.AGICommandFailure(FAILURE_CODE, result)
+
+ def secondResultItem(self, result):
+@@ -188,7 +188,7 @@ def resultPlusTimeoutFlag(self, resultLine):
+ try:
+ digits, timeout = resultLine.split(' ', 1)
+ return digits.strip(), True
+-
Bug#953449: [Pkg-javascript-devel] Bug#953449: Bug#953449: Updating the cajun Uploaders list
On Mon, Mar 09, 2020 at 10:18:13PM +0100, Xavier wrote: > this package looks unfinished (libcajun-dev without binary), and not > related to JS world. Also it looks unused (see below). Then I think it > should be removed from Debian archive Please go ahead and ask for its removal it then :) > $ dakrn cajun 'r*n*' ? -- 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#951387: Please accept https://salsa.debian.org/installer-team/console-setup/merge_requests/3
Mantas Baltix writes: > Tags: patch > > Hi, why such simple patch isn't accepted - 3 weeks already passed... > Don't feel bad! Here's one I've been waiting three years for (tested with custom install media in a VM): https://salsa.debian.org/installer-team/partman-btrfs/-/merge_requests/1/commits Cheers, Nicholas signature.asc Description: PGP signature
Bug#953482: RM: txwinrm -- RoQA; Depends on Python 2
Package: ftp.debian.org Severity: normal Please remove txwinrm. It depends on Python 2 and there's no sign of a port (acked by the maintainer in #938736) Cheers, Moritz
Bug#938736: txwinrm: Python2 removal in sid/bullseye
On Mon, Mar 09, 2020 at 09:02:29PM +, Christopher Hoskin wrote: > Dear Moritz, > > Yes - that seems sensible. There's no sign of an upstream Python 3 version. Thanks, I've just filed a removal bug. Cheers, Moritz
Bug#953449: [Pkg-javascript-devel] Bug#953449: Updating the cajun Uploaders list
Le 09/03/2020 à 21:00, Pierre-Elliott Bécue a écrit : > Source: cajun > Version: 2.0.3-2 > Severity: minor > User: m...@qa.debian.org > Usertags: mia-teammaint > > Daniel Pocock is not a member of the Project anymore (see > https://bugs.debian.org/953378#12) > > We are tracking their status in the MIA team and would like to ask you > to remove them from the Uploaders list of the package so we can close > that part of the file. > > (If the person is listed as Maintainer, what we are asking is to please > step in as a new maintainer.) > > Thanks. Hi, this package looks unfinished (libcajun-dev without binary), and not related to JS world. Also it looks unused (see below). Then I think it should be removed from Debian archive $ dakrn cajun Will remove the following packages from unstable: cajun |2.0.3-2 | source libcajun-dev |2.0.3-2 | all Maintainer: Debian Javascript Maintainers --- Reason --- -- Checking reverse dependencies... No dependency problem found.
Bug#953481: dmaths: Sources are no more available from upstream
Source: dmaths Severity: serious Justification: Policy 2.3 Hello, While visiting the upstream website [1], I saw a financial contribution has to be paid in order to be able to download dmaths. This violates 2.3 in the Debian policy. No link for downloading the source can be found on the website. I tried to reach upstream several weeks ago to confirm, but got no answer. For those reasons, I think the package should be removed from Debian. Best, Pierre [1] http://www.dmaths.org
Bug#953480: RM: jsmpp -- ROM; Not used, low popcon
Package: ftp.debian.org Severity: normal Hi, Please remove the jsmpp package, this package isn't used, has a low popcon and has never been upgraded since its initial upload 5 years ago. Thank you, Emmanuel Bourg
Bug#950836: [pkg-gnupg-maint] Bug#950836: Bug#950836: gpg-agent: generator 90gpg-agent and user with no home crontask generate annoying logs
On Fri 2020-03-06 09:09:11 +0100, Laurent Wafflard wrote:
> Yes it would be better !
> With the Q stderr redirect, some logs are not catched by the logcheck
> rules of gpg-agent, we added locally:
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ systemd\[[[:digit:]]+\]:
> Listening on GnuPG cryptographic agent and passphrase cache \(access for
> web browsers\)\.$
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ systemd\[[[:digit:]]+\]:
> Closed GnuPG cryptographic agent and passphrase cache \(access for web
> browsers\)\.$
Please propose new logcheck patterns in a separate bug report, ideally
with a patch, or perhaps as a separate file! your e-mail program
appears to line-wrap this stuff, and regexps aren't very useful if
they've been mangled.
> but it would become useless if gpgconf will be executed only for users
> with existent home.
I don't want to predicate running gpgconf on whether the homedir exists,
because it's not clear to me that this is a specific requirement.
the canonical upstream way to query the gpg suite's configuration is
gpgconf, and i'm trying to use the canonical upstream interfaces rather
than crafting novel ones that i (or someone else) will then have to
maintain.
That said, i agree that the spurious warnings don't seem relevant.
Rather, the environment generator shouldn't try to claim that gpg-agent
should be the active ssh-agent socket if it knows that gpg-agent is
somehow broken.
So i've wrapped the test in question in a "gpgconf --check-programs"
command instead. Please follow up here (feel free to reopen the bug
report) if this doesn't solve the problem for you.
Regards,
--dkg
signature.asc
Description: PGP signature
Bug#933713: libgpg-error-dev: make package fit for cross development
On Sat 2020-03-07 16:17:36 +0100, Francois Gouget wrote:
> On Wed, 12 Feb 2020, Daniel Kahn Gillmor wrote:
>
>> On Tue 2020-01-28 13:01:04 +0100, Francois Gouget wrote:
> [...]
>> > So I think it is reasonable to stop shipping gpg-error-config, just like
>> > FreeType stopped shipping freetype-config to become multiarch-compatible.
>>
>> I agree that upstream's preferred configuration mechanism
>> (gpg-error-config) is not well-suited for the modern multiarch world.
>
> But is gpg-error-config upstream's _preferred_ configuration mechanism
> or merely the legacy one?
I haven't been able to get a read on that, but i note that GnuPG itself
(made by the same people) appears to be using gpg-error-config. See
m4/gpg-error.m4 in the GnuPG sources. They use the idiosyncratic
--with-libgpg-error-prefix= as an argument for doing cross-builds.
> I did not try. But any package that depends on a multiarch-incompatible
> xxx-config script is broken imho.
>
> Now an alternative to removing gpg-error-config is to make it
> compatible with multiarch. The only differences between the two copies
> are:
>
> -libdir=${prefix}/lib/x86_64-linux-gnu
> +libdir=${prefix}/lib/i386-linux-gnu
> ...
> - output="$output -L${prefix}/lib/x86_64-linux-gnu -lgpg-error"
> + output="$output -L${prefix}/lib/i386-linux-gnu -lgpg-error"
>
> The -L option is not needed on Debian so it might as well be omitted.
>
>
> - host) echo "x86_64-pc-linux-gnu" ;;
> + host) echo "i686-pc-linux-gnu" ;;
> ...
> -echo "x86_64-pc-linux-gnu"
> +echo "i686-pc-linux-gnu"
>
> This one is the real problem. Maybe it can be derived from some other
> source. Or maybe removing support for host would have less impact than
> removing gpg-error-config entirely.
I agree with you that these things are not aligned with modern
multi-arch packaging, and are problematic today.
> Wine normally uses GnuTLS. But GnuTLS is missing support for ECDH public
> key encryption. From the patch that triggered this:
This is a mystifying claim. GnuTLS has supported ECDHE for ages. It
just supports it for TLS sessions.
Maybe you're saying that it doesn't offer the cryptographic primitive
for non-ephemeral ECDH encryption. But that's reasonable, because
modern TLS doesn't do encryption to static keys. GnuTLS is not a
generic crypto platform, and it doesn't claim to be. It claims to be a
solid TLS implementation with a sensible API (which it is!)
> https://www.winehq.org/pipermail/wine-devel/2020-January/157434.html
This seems to be talking about wanting to do something other than TLS.
It's not clear why wine would want to adopt libgcrypt if they're already
using GnuTLS, which uses nettle for its cryptographic toolkit. Why pull
in another reverse dependency?
> For now this patchset is on hold to not add a new dependency to Wine.
Wine should just use nettle directly instead of growing a dependency on
gcrypt.
--dkg
signature.asc
Description: PGP signature
Bug#952797: gpgme1.0 FTCBFS: python3.8 changed interface again
On Sat 2020-02-29 14:06:11 +0100, Helmut Grohne wrote: > gpgme1.0 fails to cross build from source, because with python3.8 the > interface was changed again. I do see that this is frustrating as it has > already resulted in a native ftbfs on gpgme1.0. However, I'm not the > Python maintainer and even Matthias' attempts at filing this issue > upstream was unsuccessful thus far. As far as I understand the current > situation, the "m" is dropped for good and not about to come back > anytime soon. So hope is that this is a one-time migration. Could you > just adapt it with your next maintainer upload? sure, i'll make that change today. it's frustrating, but i'll just keep playing catchup. Thus is the sisyphean nature of software maintenance. > gpgme1.0 only uses the most recent Python version, so we don't have to > port <=3.7 here. What do you mean by this? https://packages.debian.org/sid/amd64/python3-gpg/filelist includes modules for python 3.7 and 3.8. Do you think it doesn't or shouldn't for some reason? --dkg signature.asc Description: PGP signature
Bug#946996: wireguard-tools: 'wg-quick down' segfaults
On Mon 2020-02-03 13:20:22 -0500, Celejar wrote: > Okay, now I've gotten it. I've uninstalled nftables and put in the > debug line, and I get this (with 1.0.20200121-2): > > ~# ifdown wg0 > [#] ip -4 rule delete table 51820 > [#] ip -4 rule delete table main suppress_prefixlength 0 > [#] ip link delete dev wg0 > [#] resolvconf -d tun.wg0 -f > RESTORING: *filter > COMMIT > *nat > COMMIT > *mangle > -D PREROUTING -p udp -m comment --comment "wg-quick(8) rule for wg0" -j > CONNMARK --restore-mark --nfmask 0x --ctmask 0x > -D POSTROUTING -p udp -m mark --mark 0xca6c -m comment --comment "wg-quick(8) > rule for wg0" -j CONNMARK --save-mark --nfmask 0x --ctmask 0x > COMMIT > *raw > COMMIT > [#] iptables-restore -n > /usr/bin/wg-quick: line 29: 2284068 Segmentation fault "$@" OK, so it looks to me like the problem comes when feeding this set of commands into iptables-restore. But hm, i'm still having trouble replicating the segfault. Is this still happening for you? Can you send the output of these two commands? dpkg -l iptables wireguard dpkg -S $(readlink -f $(which iptables-restore)) That might help us narrow down the cause of the segfault. Sorry for how long this is taking to debug! --dkg signature.asc Description: PGP signature
Bug#953479: mopidy: Please move fonts-lato dependency to the recommended section
Package: mopidy Version: 3.0.1-2 Severity: wishlist Dear Maintainer, the fonts-lato is a pretty bloated dependency (more than 10 MB of disk space). It was mandatory for the ruby2.5 package when it just released, but then was moved to recommended. Please do the same. I don't think that using a fallback font will affect user experience in any significant way (only maybe if mopidy uses some Lato-specific font features). -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8), LANGUAGE=ru_UA:ru (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mopidy depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.73 ii gir1.2-gst-plugins-base-1.0 1.16.2-2 ii gir1.2-gstreamer-1.0 1.16.2-2 ii gstreamer1.0-plugins-good 1.16.2-2 ii gstreamer1.0-plugins-ugly 1.16.2-2 ii lsb-base 11.1.0 ii python-gst-1.0 1.16.2-1 ii python-pkg-resources 44.0.0-1 ii python-pykka 1.2.1-4 ii python-requests 2.22.0-2 ii python-tornado 6.0.3+really5.1.1-2 ii python2 2.7.17-2 Versions of packages mopidy recommends: ii gstreamer1.0-alsa 1.16.2-2 ii gstreamer1.0-pulseaudio 1.16.2-2 ii gstreamer1.0-tools 1.16.2-2 Versions of packages mopidy suggests: pn mopidy-doc -- Configuration Files: /etc/mopidy/mopidy.conf [Errno 13] Отказано в доступе: '/etc/mopidy/mopidy.conf' -- debconf information: mopidy/daemon: false
Bug#953477: netkit-telnet: CVE-2020-10188
Source: netkit-telnet Version: 0.17-41.2 Severity: important Tags: security upstream Control: clone -1 -2 Control: reassign -2 src:netkit-telnet-ssl 0.17.41+0.2-3.2 Control: retitle -2 netkit-telnet-ssl: CVE-2020-10188 Control: found -1 0.17-41 Control: found -2 0.17.41+0.2-3 Hi, The following vulnerability was published for netkit-telnet and netkit-telnet-ssl, filling this for starting tracking the issue. Any more insights into it? CVE-2020-10188[0]: | utility.c in telnetd in netkit telnet through 0.17 allows remote | attackers to execute arbitrary code via short writes or urgent data, | because of a buffer overflow involving the netclear and nextitem | functions. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-10188 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10188 [1] https://appgateresearch.blogspot.com/2020/02/bravestarr-fedora-31-netkit-telnetd_28.html Regards, Salvatore
Bug#950177: source-highlight: FTBFS: make test fails
Control: severity -1 serious Control: tags -1 + patch On Thursday, March 05 2020, I wrote: > On Wednesday, January 29 2020, Boyuan Yang wrote: > >> Dear source-highlight maintainer, >> >> Currently source-highlight would FTBFS due to errors when running "make test" >> after build: >> >> https://buildd.debian.org/status/fetch.php?pkg=source-highlight=arm64=3.1.9-1=1579812231=0 >> >> There are differences between the expected output value and the real value. >> Please investigate into it. > > I took some time to investigate this on amdahl.d.o, and I am not able to > reproduce this failure. I left "make check" running in a loop for > several minutes, and all of the runs successfully passed without a > problem. > > I'm almost sure this was a failure caused by either a non-deterministic > test, or by some broken dependency that got fixed later. I'm therefore > taking the liberty to downgrade the severity of this bug to normal, as > well as retitling it to remove the FTBFS part. Feel free to revert > these changes if you disagree. I stand corrected. The bug has not been fixed, and it's now impacting the latest build even on amd64: https://buildd.debian.org/status/fetch.php?pkg=source-highlight=amd64=3.1.9-1.1=1583753021=0 I *think* I understand why the problem is manifesting. The issue here is that 'make check' is parallelized, which may cause a race condition due to buffering, redirections and file-writing commands. It's a mess. I can trigger a testsuite error when I locally run 'make check -j6', but the error doesn't happen on 'make check -j1'. For this reason, I'm proposing the patch below, which disables parallelization on dh_auto_test. I am not 100% sure of this analysis, though. But since I can't spend much more time on this, I think it's worth a try. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ diff -Nru source-highlight-3.1.9/debian/changelog source-highlight-3.1.9/debian/changelog --- source-highlight-3.1.9/debian/changelog 2020-03-02 05:16:32.0 -0500 +++ source-highlight-3.1.9/debian/changelog 2020-03-09 17:07:08.0 -0400 @@ -1,3 +1,12 @@ +source-highlight (3.1.9-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Disable parallelization when running 'dh_auto_test'. +This is necessary due to racy conditions in the way the testsuite +is run. (Closes: #950177) + + -- Sergio Durigan Junior Mon, 09 Mar 2020 17:07:08 -0400 + source-highlight (3.1.9-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru source-highlight-3.1.9/debian/rules source-highlight-3.1.9/debian/rules --- source-highlight-3.1.9/debian/rules 2020-03-02 05:16:32.0 -0500 +++ source-highlight-3.1.9/debian/rules 2020-03-09 17:06:51.0 -0400 @@ -18,3 +18,6 @@ mv $(DESTDIR)/usr/bin/source-highlight-esc.sh $(DESTDIR)/usr/share/source-highlight/ dh_install rm $(DESTDIR)/usr/lib/$(DEB_TARGET_MULTIARCH)/libsource-highlight.la + +override_dh_auto_test: + dh_auto_test --no-parallel signature.asc Description: PGP signature
Bug#938736: txwinrm: Python2 removal in sid/bullseye
Dear Moritz, Yes - that seems sensible. There's no sign of an upstream Python 3 version. Thanks. Christopher On Mon, 9 Mar 2020 at 18:35, Moritz Mühlenhoff wrote: > > On Fri, Aug 30, 2019 at 07:57:05AM +, Matthias Klose wrote: > > Package: src:txwinrm > > Version: 1.3.3-1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > Hi Christopher, > there was no followup from upstream on > https://github.com/zenoss/txwinrm/issues/191 > for > five months, shall we remove txwinrm? > > Cheers, > Moritz
Bug#916972: ITP: domoticz-plugin-zigate -- Domoticz plugin for the Zigate.fr Zigbee transceiver
Control: retitle -1 domoticz-plugin-zigate -- Domoticz plugin for the Zigate.fr Zigbee transceiver control: noowner -1 Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12), therefore cannot own this ITP anymore. -- tobi (for the MIA team) signature.asc Description: PGP signature
Bug#837662: ITP: homer-ui -- HOMER / SIPCapture node web UI
Control: retitle -1 RFP: homer-ui -- HOMER / SIPCapture node web UI control: noowner -1 Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12), therefore cannot ownthis ITP anymore. -- tobi (for the MIA team) signature.asc Description: This is a digitally signed message part
Bug#951386: uscan: fails to downloads from a “dumb” HTTP git repository
Control: tags -1 + moreinfo Hi, I'm unable to reproduce this bug: $ uscan -v --force-download uscan info: uscan (version 2.20.2) See uscan(1) for help uscan info: Scan watch files in . uscan info: Check debian/watch and debian/changelog in . uscan info: package="xe" version="0.11-4" (as seen in debian/changelog) uscan info: package="xe" version="0.11" (no epoch/revision) uscan info: ./debian/changelog sets package="xe" version="0.11" uscan info: Found upstream signing keyring: debian/upstream/signing-key.asc uscan info: Process watch file at: debian/watch package = xe version = 0.11 pkg_dir = . uscan info: opts: mode=git, pgpmode=gittag uscan info: line: https://github.com/leahneukirchen/xe.git refs/tags/v(\d\S+) uscan info: Parsing mode=git uscan info: Parsing pgpmode=gittag uscan info: line: https://github.com/leahneukirchen/xe.git refs/tags/v(\d\S+) uscan info: Last orig.tar.* tarball version (from debian/changelog): 0.11 uscan info: Last orig.tar.* tarball version (dversionmangled): 0.11 uscan info: Execute: git ls-remote https://github.com/leahneukirchen/xe.git uscan info: Found the following matching refs: refs/tags/v0.11 (0.11) refs/tags/v0.10 (0.10) refs/tags/v0.9 (0.9) refs/tags/v0.8 (0.8) refs/tags/v0.7.0 (0.7.0) refs/tags/v0.6.1 (0.6.1) refs/tags/v0.6 (0.6) refs/tags/v0.5 (0.5) refs/tags/v0.4 (0.4) refs/tags/v0.3 (0.3) refs/tags/v0.2 (0.2) refs/tags/v0.1 (0.1) HEAD () refs/heads/master () refs/pull/1/head () refs/pull/1/merge () refs/pull/2/head () refs/pull/3/head () refs/pull/3/merge () refs/pull/4/head () refs/pull/4/merge () refs/pull/5/head () refs/pull/5/merge () uscan info: Looking at $base = https://github.com/leahneukirchen/xe.git with $filepattern = refs/tags/v(\d\S+) found $newfile = refs/tags/v0.11 $newversion = 0.11 $lastversion = 0.11 uscan info: Upstream URL(+tag) to download is identified as https://github.com/leahneukirchen/xe.git refs/tags/v0.11 uscan info: Filename (filenamemangled) for downloaded file: xe-0.11.tar.xz uscan info: Newest version of xe on remote site is 0.11, local version is 0.11 uscan info:=> Package is up to date for from https://github.com/leahneukirchen/xe.git refs/tags/v0.11 uscan info:=> Forcing download as requested uscan info: Downloading upstream package: xe-0.11.tar.xz Clonage dans le dépôt nu '../xe-temporary.3071220.git' remote: Enumerating objects: 18, done. remote: Counting objects: 100% (18/18), done. remote: Compressing objects: 100% (18/18), done. remote: Total 18 (delta 0), reused 12 (delta 0), pack-reused 0 Dépaquetage des objets: 100% (18/18), 17.82 Kio | 912.00 Kio/s, fait. uscan info: Successfully downloaded package: xe-0.11.tar.xz gpgv: Signature faite le dim. 05 nov. 2017 21:03:23 CET gpgv:avec la clef RSA C9C0E3814184EAFF gpgv: Impossible de vérifier la signature : Pas de clef publique uscan die: OpenPGP signature did not verify. at /usr/share/perl5/Devscripts/Uscan/Output.pm line 58.
Bug#952126: emacs-bind-map: FTBFS caused by elpa-undo-tree 0.7.1
Hi Lev, Lev Lamberov writes: > Hi Nicholas and David, > > Пн 24 фев 2020 @ 12:27 Nicholas D Steeves : > >> Lev Lamberov writes: >> >>> Hmmm, looks like the bug is caused by undo-tree, since when >>> elpa-undo-tree 0.6.4-3 is installed tests are passed correctly. >>> Moreover, when new upstream version of undo-tree is used (0.7.4, not >>> currently in Debian) tests also are passed correctly. >> >> Lev, thank you for working to find, and finding the cause! Sorry, I >> share the blame for this regression because I sponsored the upload of >> 0.7.1. How urgently would you like a fix? I'd like to give David some >> time to prepare the new undo-tree release, but can prepare it myself if >> too much time passes. BTW, are undo-trees tests flaky or could you >> enable autopkgtests for it at this time? > > In fact, this was not that urgent. Anyway, thank you both for your work > and kindness! There's no one to blame simply because it is up to > impossible to check a package against all possible regressions > (especially given that dependency chain becomes way too long pretty > quickly). > Thank you Lev, that's kind :-) On the upside, autopkgtests give us an edge over MELPA Stable! Sorry for not noticing emacs-bind-map already had them enabled. IIRC the dep chain for this package is now covered, so our early-warning system should be functional. 'wish we had untruncated backtraces... > Thanks again! I'm closing this bug (it also motivated me to update > packaging of emacs-bind-map, which should have been done at some point). > Wonderful! By the way, whenever I see a lot of packaging updates on our mailing list it also motivates me to work on my packages :-D Take care, Nicholas signature.asc Description: PGP signature
Bug#953032: Internal error: Could not resolve keysym XF86FullScreen
On 9.3.2020 21.41, Thorsten Glaser wrote: > Package: x11-xkb-utils > Version: 7.7+5 > Followup-For: Bug #953032 > Control: retitle -1 xkbcomp: Internal error: Could not resolve keysym > XF86FullScreen > > The high keycode errors went away, but this one still happens. The reason, as I see it, is because this is missing from xorgproto but there was a 4mo old merge-request on upstream gitlab which I've now merged, so until there's a new release made it could be patched and then libx11 built against that version.. -- t
Bug#953476: Updating the ganglia-modules-linux Uploaders list
Source: ganglia-modules-linux Version: 1.3.6-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Bug#953378: enough conflict, BS
‐‐‐ Original Message ‐‐‐ On Monday, March 9, 2020 7:54 PM, Geert Stappers wrote: > On Mon, Mar 09, 2020 at 07:09:41PM +, Melanie Frost wrote: > > > Dear Sam > > Dear All, > > > From an outsider perspective, this doesn't look like something that > > belongs in the bug system. I don't know your point of view but it > > looks spiteful. > > The volunteer was elected as a community representative and he's been > > hounded ever since. It looks like he asked people to stop these games, > > he resigned and he was still chased. > > Making up reasons and stories to justify this retrospectively doesn't > > wash with me. Nobody ever presented any evidence of wrongdoing before, > > you can't just make it up now and declare it to be true because you > > are the leader. > > Please think about removing these records of vendettas from Debian. > > You always talk about healing but there is no healing when these records > > are persisted in all the Debian tools, you are making Debian a target > > and setting the standard for future confrontation. > > Melanie > > That does not compute: An outsider worried about "this". > > In other words: The bullshit has been seen. > > Request: Leave this crap as manure. Debian can be better than this, really
Bug#952547: chromium: freezes for a couple of seconds, about once or twice a minute
I can confirm this with Qubes OS when Debian is used as the template VM. Chromium (80.0.3987.116-1) which is in testing fixes the issue. Hope it's scheduled to go to stable soon.
Bug#953397: evil-el: please update to 1.14.0, testing2sid is currently failing
David Krauser writes: > Hi Nicholas, > > On Sunday, March 8, 2020 11:07 PM, Nicholas D Steeves > wrote: >> Would you please package 1.14.0? I am of course happy to review your >> work and sponsor the upload. > > 1.14.+ is not yet tagged or released upstream. I'll ping the upstream > maintainers about the status of this release. > Ah, now I see what happened; it looks like they forgot to push the tag: https://github.com/emacs-evil/evil/commit/4dc63903d9688e2ce838a220b0e24d8f14a64c12 Regards, Nicholas P.S. I generally won't nag you about new upstream versions, and the reason for this exception is the piuparts failure, which is RC (release critical bug) if it's not a transient failure. eg: byte-compilation when installing the package should not fail. Stable22sid is also now failing, and someone on the Release Team will eventually file an RC bug, or upgrade the priority of this one. P.P.S. I didn't tag this bug as serious because I couldn't reproduce the failure on amd64 for stable2sid nor stable2testing2sid, so I wonder if it's an armhf thing...nonetheless, an official release arch thing. signature.asc Description: PGP signature
Bug#953475: RM: python-netsyslog -- ROM; python2-only; no rdeps in testing; unmaintained
Package: ftp.debian.org Severity: normal
Bug#953378: enough conflict
> "Melanie" == Melanie Frost writes: Melanie> The volunteer was elected as a community representative and Melanie> he's been hounded ever since. It looks like he asked Melanie> people to stop these games, he resigned and he was still Melanie> chased. The issue is that Daniel is still chasing us. In this specific instance, I responded because Daniel filed an ITP. If Daniel resigned and stopped interacting with the Debian community, we would be a lot happier, and I would not have chosen to respond this way. The primary issue from Debian's side is that Debian has asked someone to leave--to stop interacting. And yet they are still interacting by doing things like filing ITPs. We are not chasing anyone. We are responding and reacting to being chased on websites like debian.community, in our own BTS, and in other fora. We are responding to being chased by having messages bcc'd to large numbers of our contributors even after we have banned someone from posting to our lists. In some cases, this has been done by Daniel. In other cases this has been done by people using anonymous accounts using techniques that are very similar to techniques described on a website run by Daniel. We reject these forms of interaction. If it were not for these forms of interaction, we would be much less vocal/much less interested in making public statements. --Sam
Bug#909716: Request for sponsoring changes in idba
Hi Andreas, On Sun, Mar 8, 2020 at 12:54 PM Andreas Tille wrote: > Hi Pranav, > I hope you are happy with your result. > Thank you, they went quite well. May be adding some binary package idba-extra (or some better name you > might find) to ship these additional tools that might be not needed in > every day use but might be helpful anyway for some use case - for > instance testing the package. > > > Also, would it be possible to have some programs available only during > > testing, but not in the finall installation? Then we could run sim_reads > > that way and avoid all the static data. > > Yes, for instance in an extra binary package. While we could even run > autopkgtest inside a compiled source tree I personally prefer to ship > every tool inside some binary Debian package to enable users reproducing > the test results on their installation. > Yes, this makes sense. I have added another package called idba-extra. > Than you do > > git mv debian/install debian/idba.install > git mv debian/manpages debian/idba.manpages > > (which is strictly speaking redundant since by default debian/install > and debian/manpages are affecting the first binary package - but I > consider this better) and create a > > $EDITOR debian/idba-extra.install > > package listing all tools you want to install into this package. > One small problem I ran into: There was no debian/install file originally, so I couldn't figure out how it is that these files are being copied. Is it something to do with make install? I've added debian/idba.install and debian/idba-extra.install, and everything works as expected. Although, the following warnings are generated during testing. dh_missing: warning: usr/bin/idba_tran exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/validate_blat_parallel exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/validate_blat exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/idba_ud exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/scan.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/idba_hybrid exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/run-unittest.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/bin/idba exists in debian/tmp but is not installed to anywhere Please check debian/*.install and see if these are right. I have also changed the test files now. Only a few necessary files are included, and the rest are generated during testing. Let me know if I missed anything, otherwise please review and sponsor these changes. > Hope this short intro is helpful. > It was very helpful, indeed. I have a few more queries, though. I was trying to find more information about the structure of packages and I found these two guides: https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf https://www.debian.org/doc/manuals/maint-guide/dother.en.html Are these okay, or would you recommend some other resource? Also, now that we have included some new programs in the idba-extra package, how can I generate man pages for them? I noticed that it is the debian/*.1 files that correspond to manpages, and are generated using help2man. But as far as I understand, help2man needs the executable, which is produced only inside the testing chroot. So, do I run help2man inside the chroot, or is there another way? And does anything else need to be done, when a new package is added? Please reply whenever it is convenient for you. Regards, Pranav ᐧ
Bug#953473: Updating the homer-api Uploaders list
Source: homer-api Version: 5.0.6+dfsg2-3.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953464: Updating the libphonenumber Uploaders list
Source: libphonenumber Version: 7.1.0-5 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- 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#953465: Updating the captagent Uploaders list
Source: captagent Version: 6.1.0.20-3.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- 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#953472: Updating the ganglia-web Uploaders list
Source: ganglia-web Version: 3.6.1-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953467: Updating the qpid-proton Uploaders list
Source: qpid-proton Version: 0.22.0-3.3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953469: Updating the node-inherits Uploaders list
Source: node-inherits Version: 2.0.4-1 2.0.3-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953466: Updating the coturn Uploaders list
Source: coturn Version: 4.5.1.1-1.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- 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#953471: Updating the ganglia Uploaders list
Source: ganglia Version: 3.6.0-7 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953462: Updating the flactag Uploaders list
Source: flactag Version: 2.0.4-5 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- 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#953463: Updating the jsmpp Uploaders list
Source: jsmpp Version: 2.1.2-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953470: Updating the radcli Uploaders list
Source: radcli Version: 1.2.6-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953468: Updating the node-debug Uploaders list
Source: node-debug Version: 4.1.1-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953460: Updating the syslog-nagios-bridge Uploaders list
Source: syslog-nagios-bridge Version: 1.0.3-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- 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#953459: procps: Non-source-only upload in the latest revision
Source: procps Version: 2:3.3.16-3 Severity: important X-Debbugs-CC: csm...@debian.org Dear procps maintainer, Unfortunately the last upload of procps was not a source-only upload. As a result, this version will not migrate to Testing. This is also blocking the ongoing auto-procps transition from being completed. Please consider requesting an binNMU for arch:amd64 or make another source- only upload. Thanks! -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#953458: Updating the sipxtapi Uploaders list
Source: sipxtapi Version: 3.3.0~test17-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- 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
