Bug#956666: logwatch: Homepage URL
Package: logwatch Version: 7.5.2-1 Severity: minor Tags: patch Dear Maintainer, Please update the logwatch Homepage URL to: https://sourceforge.net/projects/logwatch/ Patch below. Thank you! Daniel Lewart Urbana, Illinois --- debian/control.orig 2020-01-12 05:24:15.0 -0600 +++ debian/control 2020-04-14 00:00:00.0 -0500 @@ -4,7 +4,7 @@ Maintainer: Willi Mann Build-Depends: debhelper (>> 8.0.0~) Standards-Version: 4.4.1 -Homepage: http://www.logwatch.org/ +Homepage: https://sourceforge.net/projects/logwatch/ Vcs-Browser: https://salsa.debian.org/debian/logwatch Vcs-Git: https://salsa.debian.org/debian/logwatch.git
Bug#946572: closed by Debian FTP Masters (reply to Nicolas Boulenguez ) (Bug#946572: fixed in abcm2ps 8.14.7-0.1)
Control: reopen -1 On Mon, Apr 13, 2020 at 06:06:03PM +, Debian Bug Tracking System wrote: >* New upstream release closes: #946572. This is part of the solution, but without the parts in debian/rules, the fix is incomplete. Helmut
Bug#891136: ITP: tools-deps-alpha-clojure -- functional API for dependency management and classpath creation
Okay, latest version is now 0.8.677. Let's reevaluate what's required for packaging. `lein deps :tree` now says: [org.clojure/tools.deps.alpha "0.8.677"] ;; I'm going to ignore these for now [com.cognitect.aws/api "0.8.408"] [com.cognitect/http-client "0.1.101"] [org.eclipse.jetty/jetty-client "9.4.15.v20190215"] [org.eclipse.jetty/jetty-io "9.4.15.v20190215"] [org.eclipse.jetty/jetty-http "9.4.15.v20190215"] [org.eclipse.jetty/jetty-util "9.4.15.v20190215"] [commons-codec "1.13"] [org.clojure/core.async "0.5.527"] [org.clojure/tools.analyzer.jvm "0.7.2"] [org.clojure/core.memoize "0.5.9"] [org.clojure/core.cache "0.6.5"] [org.clojure/data.priority-map "0.0.7"] [org.clojure/tools.analyzer "0.6.9"] [org.clojure/tools.reader "1.0.0-beta4"] [org.ow2.asm/asm-all "4.2"] [org.clojure/data.json "0.2.7"] [org.clojure/tools.logging "0.5.0"] [com.cognitect.aws/endpoints "1.1.11.705"] [com.cognitect.aws/s3 "784.2.593.0"] ;; inside libatinject-jsr330-api-java [javax.inject "1"] ;; libmaven-resolver-java == 1.4.1 in sid [org.apache.maven.resolver/maven-resolver-api "1.4.1"] [org.apache.maven.resolver/maven-resolver-connector-basic "1.4.1"] [org.apache.maven.resolver/maven-resolver-impl "1.4.1"] [org.slf4j/slf4j-api "1.7.25"] [org.apache.maven.resolver/maven-resolver-spi "1.4.1"] [org.apache.maven.resolver/maven-resolver-transport-file "1.4.1"] [org.apache.maven.resolver/maven-resolver-transport-http "1.4.1"] [org.apache.httpcomponents/httpclient "4.5.6" :exclusions [[commons-logging]]] [org.apache.httpcomponents/httpcore "4.4.10"] [org.slf4j/jcl-over-slf4j "1.7.25" :scope "runtime"] [org.apache.maven.resolver/maven-resolver-util "1.4.1"] ;; libmaven3-core-java == 3.6.3 in sid [org.apache.maven/maven-core "3.6.3"] [com.google.inject/guice "4.2.1" :classifier "no_aop"] [aopalliance "1.0"] [com.google.guava/guava "25.1-android"] [com.google.code.findbugs/jsr305 "3.0.2"] [com.google.errorprone/error_prone_annotations "2.1.3"] [com.google.j2objc/j2objc-annotations "1.1"] [org.checkerframework/checker-compat-qual "2.0.0"] [org.codehaus.mojo/animal-sniffer-annotations "1.14"] [org.apache.commons/commons-lang3 "3.8.1"] [org.apache.maven.shared/maven-shared-utils "3.2.1"] [commons-io "2.5"] [org.apache.maven/maven-artifact "3.6.3"] [org.apache.maven/maven-builder-support "3.6.3"] [org.apache.maven/maven-plugin-api "3.6.3"] [org.apache.maven/maven-settings-builder "3.6.3"] [org.sonatype.plexus/plexus-sec-dispatcher "1.4"] [org.sonatype.plexus/plexus-cipher "1.4"] [org.apache.maven/maven-settings "3.6.3"] [org.codehaus.plexus/plexus-classworlds "2.6.0"] [org.codehaus.plexus/plexus-component-annotations "2.1.0" :exclusions [[junit]]] [org.eclipse.sisu/org.eclipse.sisu.inject "0.3.4"] [org.eclipse.sisu/org.eclipse.sisu.plexus "0.3.4"] [javax.enterprise/cdi-api "1.0" :exclusions [[javax.el/el-api] [org.jboss.ejb3/jboss-ejb3-api] [org.jboss.interceptor/jboss-interceptor-api]]] [javax.annotation/jsr250-api "1.0"] ;; in libmaven3-core-java == 3.6.3 in sid [org.apache.maven/maven-resolver-provider "3.6.3"] [org.apache.maven/maven-model-builder "3.6.3"] [org.codehaus.plexus/plexus-interpolation "1.25"] [org.apache.maven/maven-model "3.6.3"] [org.apache.maven/maven-repository-metadata "3.6.3"] [org.codehaus.plexus/plexus-utils "3.2.1"] ;; in libdata-xml-clojure > 0.0.8 in sid ;; there's an incompatibility with leiningen issue in upgrading [org.clojure/data.xml "0.2.0-alpha6"] [org.clojure/data.codec "0.1.0"] ;; in libtools-cli-clojure > 0.3.5 in sid [org.clojure/tools.cli "0.4.2"] ;; NOT in Debian, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905543 [org.clojure/tools.gitlibs "0.2.64"] [com.jcraft/jsch.agentproxy.connector-factory "0.0.9"] [com.jcraft/jsch.agentproxy.core "0.0.9"] [com.jcraft/jsch.agentproxy.pageant "0.0.9"] [com.jcraft/jsch.agentproxy.sshagent "0.0.9"] [com.jcraft/jsch.agentproxy.usocket-jna "0.0.9"] [net.java.dev.jna/jna-platform "4.1.0"] [net.java.dev.jna/jna "4.1.0"] [com.jcraft/jsch.agentproxy.usocket-nc "0.0.9"] [com.jcraft/jsch.agentproxy.jsch "0.0.9"] [org.eclipse.jgit "4.10.0.201712302008-r"] [com.googlecode.javaewah/JavaEWAH "1.1.6"] [com.jcraft/jsch "0.1.54"] So in summary, we need the following new packages: - [org.clojure/tools.gitlibs "0.2.64"] And the following upgrades: - [org.clojure/data.xml "0.2.0-alpha6"] - [org.clojure/tools.cli "0.4.2"] Again, I'm going to skip all the AWS stuff and consider it a "recommends" rather than a "depends". Previously, clojure-tools-gitlibs also needed version
Bug#956665: libdrm2: Update broke firefox WebGL
Package: libdrm2 Version: 2.4.101-1 Severity: normal Dear Maintainer, After updating libdrm2 from 2.4.100-4 to 2.4.101-1 WebGL stopped working on firefox (using esr from repos and tar from mozilla). After loading a WebGL sample from webglsamples.org the following is message is shown in the web console: Error: WebGL warning: : Failed to create WebGL context: WebGL creation failed: * tryNativeGL * Exhausted GL driver options. and in the terminal where firefox was launched: libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information Looks similar to #907698. Regards. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8), LANGUAGE=es_CL:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libdrm2 depends on: ii libc6 2.30-4 ii libdrm-common 2.4.101-1 libdrm2 recommends no packages. libdrm2 suggests no packages. -- no debconf information
Bug#956662: Acknowledgement (linphonec gives an error message referring to ortp.)
P.s. I should have included the transcript from the console. Linux 4.19.0-8-686-pae (joule.invalid) (pts/1) peter@joule:/home/peter$ linphonec 2020-04-13 21:06:02:568 ortp-error-Connection to the pulseaudio server failed Ready 2020-04-13 21:06:03:255 ortp-error-bctbx_file_open: Error open No such file or d irectory 2020-04-13 21:06:03:255 ortp-error-Error in the opening zrtp_cache_db_file((null )/.linphone-zidcache.tmp): unable to open database file. 2020-04-13 21:06:03:256 ortp-error-LIME/ZRTP cache migration failed(returned -40 0), start with a fresh cache, old one kept as backup in (null)/.linphone-zidcach e.bkp Warning: video is disabled in linphonec, use -V or -C or -D to enable. linphonec> 2020-04-13 21:06:04:265 ortp-error-bctbx_file_open: Error open No suc h file or directory linphonec> quit Terminating... -- https://en.wikibooks.org/wiki/Medical_Machines https://en.wikibooks.org/wiki/Oberon Tel: +1 604 670 0140Bcc: peter at easthope. ca
Bug#891141: ITP: clojure-cli -- upstream CLI entrypoints for Clojure
Latest upstream version is now 1.10.1.536 with a dependency on clojure.deps.alpha 0.8.677. signature.asc Description: PGP signature
Bug#956664: python-packaging: diff for NMU version 20.3-1.1
Package: python-packaging Version: 20.3-1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for python-packaging (versioned as 20.3-1.1). The diff is attached to this message. Please consider maintaining this package under DPMT Regards. diff -Nru python-packaging-20.3/debian/changelog python-packaging-20.3/debian/changelog --- python-packaging-20.3/debian/changelog 2020-03-23 04:44:10.0 -0400 +++ python-packaging-20.3/debian/changelog 2020-04-13 23:56:51.0 -0400 @@ -1,3 +1,10 @@ +python-packaging (20.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Dont run unittests for python2 binary, to reduce pytest rdeps + + -- Sandro Tosi Mon, 13 Apr 2020 23:56:51 -0400 + python-packaging (20.3-1) unstable; urgency=medium * New upstream version. diff -Nru python-packaging-20.3/debian/control python-packaging-20.3/debian/control --- python-packaging-20.3/debian/control 2020-02-18 11:29:15.0 -0500 +++ python-packaging-20.3/debian/control 2020-04-13 23:56:26.0 -0400 @@ -8,7 +8,7 @@ python-pretend, python3-pretend, pypy-pretend, python-pyparsing, python3-pyparsing, pypy-pyparsing, python-six, python3-six, pypy-six, - python-pytest, python3-pytest, + python3-pytest, python-setuptools, python3-setuptools, pypy-setuptools, Standards-Version: 4.5.0 Homepage: https://pypi.python.org/pypi/packaging diff -Nru python-packaging-20.3/debian/rules python-packaging-20.3/debian/rules --- python-packaging-20.3/debian/rules 2016-05-17 10:09:34.0 -0400 +++ python-packaging-20.3/debian/rules 2020-04-13 23:56:38.0 -0400 @@ -5,6 +5,7 @@ #export DH_VERBOSE=1 export PYBUILD_DISABLE_pypy=test +export PYBUILD_DISABLE_python2=test %: dh $@ --with python2,python3,pypy --buildsystem=pybuild
Bug#956147: gnome-shell-xrdesktop: Please update for GNOME 3.36 transition
Package: gnome-shell-xrdesktop Followup-For: Bug #956147 Hi Simon, Thanks for reporting this issue. I have rebased the package to 3.36.1-5 and will upload soon. I wonder would that be possible to include these xrdesktop patchset directly in gnome-shell package instead of gnome-shell-xrdesktop diverging? If you accept, I will join the team to keep the xrdesktop patchset update in gnome-shell package instead. And I believe this will shorter the time for transition each time. Best regards, -Andrew
Bug#956663: initramfs-tools-core: update-initramfs does not search all the firmware paths the kernel does
Package: initramfs-tools-core
Version: 0.133+deb10u1
Severity: normal
Tags: patch
Dear Maintainer,
* What led up to the situation?
I like to keep up with the official kernel releases. As a result the firmware
they wind up requiring is newer than what is available in firmware packages.
I'd like to install these from the git repo but also want to keep using
some firmware package from debian (cpu microcode patches for example).
* What exactly did you do (or not do) that was effective (or
ineffective)?
I placed the firmware from the git repo in /lib/firmware/updates/ which
the kernel searches before /lib/firmware.
* What was the outcome of this action?
Kernel can find them but update-initramfs cannot.
* What outcome did you expect instead?
update-initramfs look in all the places the kernel does and copies the files
as appropriate.
I have attached an initial patch that solves this. I am currently using the
resultng code and it is working fine for me.
The one thing the patch does not do is allow for a custom location that can
be provided to the kernel to search first.
This is because that's a little more complicated and requires a decision wrt
where to specify this location (ie the config file?).
I can do that work also if it'll help get the patch in.
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.3-local.20200409-123516 (SMP w/6 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages initramfs-tools-core depends on:
ii coreutils8.30-3
ii cpio 2.12+dfsg-9
ii e2fsprogs1.44.5-1+deb10u3
ii klibc-utils 2.0.6-1
ii kmod 26-1
ii udev 241-7~deb10u3
Versions of packages initramfs-tools-core recommends:
ii busybox 1:1.30.1-4
ii pigz 2.4-1
Versions of packages initramfs-tools-core suggests:
pn bash-completion
-- no debconf information
--- a/hook-functions2020-04-09 11:39:18.061168163 +1000
+++ b/hook-functions2020-04-09 11:51:05.621625010 +1000
@@ -53,7 +53,7 @@
# Add dependent modules + eventual firmware
manual_add_modules()
{
- local prefix kmod options firmware
+ local prefix kmod options firmware fwloc
if [ $# -eq 0 ]; then
return
@@ -76,15 +76,19 @@
# Add required firmware
for firmware in $(modinfo -k "${version}" -F firmware
"${kmod}"); do
- if [ -e "${DESTDIR}/lib/firmware/${firmware}" ] \
- || [ -e
"${DESTDIR}/lib/firmware/${version}/${firmware}" ]; then
+ if [ -e
"${DESTDIR}/lib/firmware/updates/${version}/${firmware}" ] \
+ || [ -e "${DESTDIR}/lib/firmware/updates/${firmware}" ]
\
+ || [ -e
"${DESTDIR}/lib/firmware/${version}/${firmware}" ] \
+ || [ -e "${DESTDIR}/lib/firmware/${firmware}" ]; then
continue
fi
# Only print warning for missing fw of loaded module
# or forced loaded module
- if [ ! -e "/lib/firmware/${firmware}" ] \
- && [ ! -e "/lib/firmware/${version}/${firmware}" ] ;
then
+ if [ ! -e
"/lib/firmware/updates/${version}/${firmware}" ] \
+ && [ ! -e "/lib/firmware/updates/${firmware}" ] \
+ && [ ! -e "/lib/firmware/${version}/${firmware}" ] \
+ && [ ! -e "/lib/firmware/${firmware}" ]; then
# Only warn about missing firmware if
# /proc/modules exists
if [ ! -e /proc/modules ] ; then
@@ -99,12 +103,15 @@
continue
fi
- if [ -e "/lib/firmware/${version}/${firmware}" ]; then
- copy_file firmware \
- "/lib/firmware/${version}/${firmware}"
- else
- copy_file firmware "/lib/firmware/${firmware}"
- fi
+ for fwloc in
"/lib/firmware/updates/${version}/${firmware}" \
+ "/lib/firmware/updates/${firmware}" \
+ "/lib/firmware/${version}/${firmware}" \
+ "/lib/firmware/${firmware}"; do
+ if [ -e "$fwloc" ]; then
+ copy_file firmware "$fwloc"
+ break
+
Bug#885433: access blocked to debian wiki
Dear Admin, Would you be able to unblock my statically assigned IP 119.15.103.114 please? I have been unable to read anything in the Debian wiki for many month and I am a recent user keen to learn , but have had to source my information from stack exchange and reddit, because your wiki is unavailable to me. regards, Ralph Holland
Bug#956661: /usr/sbin/update-initramfs: update-initramfs hangs forever when trying to update
Control: severity -1 important Control: tag -1 moreinfo unreproducible On Mon, 2020-04-13 at 20:54 -0400, Frank McCormick wrote: > Package: initramfs-tools > Version: 0.136 > Severity: grave > File: /usr/sbin/update-initramfs > Justification: renders package unusable > > Dear Maintainer, > > Not much to report. Update-initramfs hangs forever when trying to create a new > file or update a current one. > This happened after this afternoons update on Debian Sid. It's pretty much > useless > now. [...] initramfs-tools hasn't been changed for a while, so the bug is probably elsewhere. I tried to reproduce this on unstable, with all the same packages you have that include initramfs hooks, but update-initramfs completes in about 15 seconds. Please run this (as root) and send the output: mkinitramfs -v -o initrd.img Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#956662: linphonec gives an error message referring to ortp.
Package: linphone Version: 3.12.0-3 Severity: important Dear Maintainer, * What led up to the situation? Executed linphonec in a console. * What exactly did you do (or not do) that was effective (or ineffective)? Executing linphonec in a console was ineffective. * What was the outcome of this action? Failed to reach the linphonec prompt but linphone gave an error complaint referring to ortp. * What outcome did you expect instead? linphonec should give a prompt allowing dialing. -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-8-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linphone depends on: ii libatk1.0-0 2.30.0-2 ii libbctoolbox10.6.0-2+b2 ii libbelcard1 1.0.2-1 ii libbellesip0 1.6.3-5 ii libbzrtp01.0.6-3 ii libc62.28-10 ii libcairo21.16.0-4 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-0 2.24.32-3 ii libmediastreamer-base10 1:2.16.1-4+b1 ii libmediastreamer-voip10 1:2.16.1-4+b1 ii libnotify4 0.7.7-4 ii libortp131:1.0.2-1 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpangoft2-1.0-01.42.4-7~deb10u1 ii libpangoxft-1.0-01.42.4-7~deb10u1 ii libsqlite3-0 3.27.2-3 ii libstdc++6 8.3.0-6 ii libudev1 241-7~deb10u3 ii libxml2 2.9.4+dfsg1-7+b3 ii linphone-nogtk 3.12.0-3 ii zlib1g 1:1.2.11.dfsg-1 linphone recommends no packages. Versions of packages linphone suggests: ii yelp 3.31.90-1 -- no debconf information -- https://en.wikibooks.org/wiki/Medical_Machines https://en.wikibooks.org/wiki/Oberon Tel: +1 604 670 0140Bcc: peter at easthope. ca
Bug#953366: nvidia-kernel-dkms: module not loaded due lockdown
Dear maintainers, My problem is solved. It was happening because I did signed nvidia-kernel.ko as explained here in: https://wiki.debian.org/SecureBoot In the details, to automate the process for future nvidia-kernel-dmks update, I relied on this link: https://gist.github.com/dop3j0e/2a9e2dddca982c4f679552fc1ebb18df So, I generated my MOK key, rebooted my computer to enroll it, and created /etc/dkms/nvidia-current.conf containing: POST_BUILD=../../../../../../root/module-signing/dkms-sign-module Then, I installed optirun and nvidia-smi: apt install primus nvidia-smi ... rebuilt the nvidia module and apt reinstall nvidia-kernel-dkms ... and provided the passphrase of my MOK key (see dkms-sign-module) when prompted. After reboot, the nvidia module is now correctly loaded: (mando@aldur) (~) $ lsmod | grep nvidia nvidia_drm 53248 0 nvidia_modeset 1118208 1 nvidia_drm nvidia 20467712 19 nvidia_modeset ipmi_msghandler 65536 2 ipmi_devintf,nvidia drm_kms_helper 212992 2 nvidia_drm,i915 drm 548864 13 drm_kms_helper,nvidia_drm,i915 In the details, if I run: optirun glxgears ... and nvidia-smi in another terminal, I get: (mando@aldur) (~) $ nvidia-smi Tue Apr 14 03:58:29 2020 +-+ | NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: N/A | |---+--+--+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce MX150 On | :02:00.0 Off | N/A | | N/A 46C P0 N/A / N/A | 10MiB / 2002MiB | 4% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| | 0 2306 G /usr/lib/xorg/Xorg 7MiB | | 0 2310 G glxgears 2MiB | +-+ Best regards, you can close the bug mando
Bug#956341: qtcreator: Use litehtml
Hi! On Fri, 10 Apr 2020 at 03:06, Yangfl wrote: > > Package: qtcreator > Severity: wishlist > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947498 > Thanks a lot!!! I am curently quite busy, but I'll add it as soon as possible. Cheers, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#953860: how to reproduce
On Saturday, 11 April 2020 5:19:00 PM AEST Michael Biebl wrote:
> > type=AVC msg=audit(1586512443.135:71139): avc: granted { unlink } for
> > pid=293 comm="systemd-journal"
> > name="user-1001@165b61313e51499ab58ffd33d611e714--
> > .journal" dev="sdb2" ino=2093618
> > scontext=system_u:system_r:syslogd_t:s0
> > tcontext=system_u:object_r:systemd_journal_t:s0 tclass=file
> > type=AVC msg=audit(1586565837.001:94320): avc: granted { unlink } for
> > pid=293 comm="systemd-journal"
> > name="user-1001@165b61313e51499ab58ffd33d611e714--
> > .journal" dev="sdb2" ino=2095421
> > scontext=system_u:system_r:syslogd_t:s0
> > tcontext=system_u:object_r:systemd_journal_t:s0 tclass=file
>
> Is another user/process accessing the journal file at the time the
> delete happens?
Not through any deliberate user action. I'm the only user of the system and I
wasn't running any journalctl command. Does systemd do such stuff internally?
--
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/
Bug#956661: /usr/sbin/update-initramfs: update-initramfs hangs forever when trying to update
Package: initramfs-tools Version: 0.136 Severity: grave File: /usr/sbin/update-initramfs Justification: renders package unusable Dear Maintainer, Not much to report. Update-initramfs hangs forever when trying to create a new file or update a current one. This happened after this afternoons update on Debian Sid. It's pretty much useless now. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 54M Apr 8 09:23 /boot/initrd.img-5.4.0-4-amd64 -rw-r--r-- 1 root root 0 Apr 13 19:51 /boot/initrd.img-5.4.0-4-amd64.new -rw-r--r-- 2 root root 55M Apr 11 09:32 /boot/initrd.img-5.5.0-1-amd64 -rw-r--r-- 2 root root 55M Apr 11 09:32 /boot/initrd.img-5.5.0-1-amd64.dpkg-bak -rw-r--r-- 1 root root 0 Apr 13 19:40 /boot/initrd.img-5.5.0-1-amd64.new -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.5.0-1-amd64 root=UUID=9b4d766e-de76-49fc-9af2-c4fbf52b2c4a ro apparmor=0 -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by rfkill 28672 2 binfmt_misc24576 1 intel_powerclamp 20480 0 coretemp 20480 0 snd_hda_codec_hdmi 73728 1 kvm_intel 311296 0 snd_hda_codec_realtek 126976 1 snd_hda_codec_generic94208 1 snd_hda_codec_realtek ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek kvm 798720 1 kvm_intel snd_hda_intel 53248 2 irqbypass 16384 1 kvm joydev 28672 0 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 163840 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek pktcdvd49152 1 snd_hda_core 102400 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hwdep 16384 1 snd_hda_codec crct10dif_pclmul 16384 1 ghash_clmulni_intel16384 0 snd_pcm 131072 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 40960 1 snd_pcm aesni_intel 368640 0 crypto_simd16384 1 aesni_intel snd 106496 12 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm cryptd 24576 2 crypto_simd,ghash_clmulni_intel glue_helper16384 1 aesni_intel intel_cstate 16384 0 soundcore 16384 1 snd mei_wdt16384 0 intel_uncore 147456 0 mei_me 45056 1 iTCO_wdt 16384 0 mei 122880 3 mei_wdt,mei_me iTCO_vendor_support16384 1 iTCO_wdt watchdog 28672 2 iTCO_wdt,mei_wdt evdev 28672 7 serio_raw 20480 0 pcspkr 16384 0 acpi_cpufreq 28672 1 wmi_bmof 16384 0 vmwgfx364544 0 ttm 122880 1 vmwgfx fuse 139264 3 sg 36864 0 parport_pc 28672 0 ppdev 24576 0 lp 20480 0 sunrpc495616 1 parport61440 3 parport_pc,lp,ppdev ip_tables 32768 0 x_tables 53248 1 ip_tables autofs453248 2 ext4 765952 3 crc16 16384 1 ext4 mbcache16384 1 ext4 jbd2 135168 1 ext4 raid10 65536 0 raid456 176128 0 async_raid6_recov 24576 1 raid456 async_memcpy 20480 2 raid456,async_raid6_recov async_pq 20480 2 raid456,async_raid6_recov async_xor 20480 3 async_pq,raid456,async_raid6_recov async_tx 20480 5 async_pq,async_memcpy,async_xor,raid456,async_raid6_recov xor24576 1 async_xor raid6_pq 122880 3 async_pq,raid456,async_raid6_recov libcrc32c 16384 1 raid456 crc32c_generic 16384 0 raid1 49152 0 raid0 24576 0 multipath 20480 0 linear 20480 0 md_mod176128 6 raid1,raid10,raid0,linear,raid456,multipath hid_logitech_hidpp 45056 0 hid_logitech_dj28672 0 hid_generic16384 0 usbhid 65536 1 hid_logitech_dj hid 147456 4 usbhid,hid_generic,hid_logitech_dj,hid_logitech_hidpp uas32768 0 usb_storage81920 2 uas sr_mod 28672 1 sd_mod 57344 5 cdrom 73728 2 pktcdvd,sr_mod i915 2445312 3 ahci 40960 3 libahci45056 1 ahci libata290816 2 libahci,ahci ehci_pci 20480 0 ehci_hcd 98304 1 ehci_pci video 53248 1 i915 i2c_algo_bit 16384 1 i915 scsi_mod 253952 6 sd_mod,usb_storage,uas,libata,sg,sr_mod
Bug#947979: Please add a tracker for the enchant -> enchant-2 transition
On Thu, 12 Mar 2020 08:50:30 +0100 Paul Gevers wrote: > Hi Laurent, > > On 10-01-2020 21:09, Paul Gevers wrote: > > Slightly different from a regular transition: all involved > > packages need a source-full upload to switch and this can happen over a > > longer period. > > How is this faring. I haven't seen progress in a month to this > transition. Are all reverse dependencies aware now, there are only 4 > blocking bugs against this transition. Do you intend to finish this > before the freeze, we don't want be shipping two enchants with bullseye. Nothing much as moved on my side, I'll try to check if all rdeps have a bug open. But, looking at the tracker, I realized that there are false positive in it, the regex seems to match python3-enchant as well, which is definitely not intended Can somebody check? Thanks
Bug#956339: fixed in unattended-upgrades 2.3
On Mon, 2020-04-13 at 23:04 +, Balint Reczey wrote: >* Blacklist not trusted packages and ones with conffile prompts > instead of just pinning them once with NEVER_PIN which is can be cleared > later. (LP: #1871615) (Closes: #956339) I tested this with popularity-contest and I got the correct results. I'll file another bug if I see the other issue I mentioned again. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#956660: build-essential: The appropriate version gcc is not installed (and not available!)
Package: build-essential
Version: 12.8
Severity: important
Dear Maintainer,
I use a Debian Bullseye up-to-date. I try to install the latest Nvidia driver
as xserver-xorg-video-{nouveau,nvidia} does not work properly by using
NVIDIA-Linux-x86_64-440.82.run install script available on Nvidia website. I
use the standard current debian kernel:
(root@aldur) (~) # uname -a
Linux aldur 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64
GNU/Linux
(root@aldur) (~) # dpkg -l | grep linux-image
ii linux-image-5.4.0-4-amd64 5.4.19-1
amd64Linux 5.4 for 64-bit PCs (signed)
ii linux-image-amd64 5.4.19-1
amd64Linux for 64-bit PCs (meta-package)
I installed the packages needed to build the module:
apt install linux-headers-$(uname -r) dkms build-essential libglvnd-dev
pkg-config
When running NVIDIA-Linux-x86_64-440.82.run as root, the build fails and the
installer suggest me to look inside /var/lib/dkms/nvidia/440.82/build/make.log.
(root@aldur) (~) # cat /var/lib/dkms/nvidia/440.82/build/make.log
DKMS make.log for nvidia-440.82 for kernel 5.4.0-4-amd64 (x86_64)
Tue Apr 14 02:16:01 CEST 2020
make[1]: Entering directory '/usr/src/linux-headers-5.4.0-4-common'
make[2]: Entering directory '/usr/src/linux-headers-5.4.0-4-amd64'
Compiler version check failed:
The major and minor number of the compiler used to
compile the kernel:
gcc version 9.2.1 20200203 (Debian 9.2.1-28)
does not match the compiler used here:
cc (Debian 9.3.0-10) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
It is recommended to set the CC environment variable
to the compiler that was used to compile the kernel.
The compiler version check can be disabled by setting
the IGNORE_CC_MISMATCH environment variable to "1".
However, mixing compiler versions between the kernel
and kernel modules can result in subtle bugs that are
difficult to diagnose.
*** Failed CC version check. Bailing out! ***
make[3]: *** [/var/lib/dkms/nvidia/440.82/build/Kbuild:191:
cc_version_check] Error 1
make[3]: *** Waiting for unfinished jobs
make[2]: *** [/usr/src/linux-headers-5.4.0-4-common/Makefile:1665:
/var/lib/dkms/nvidia/440.82/build] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-5.4.0-4-amd64'
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-4-common'
make: *** [Makefile:81: modules] Error 2
Indeed, the version of gcc mismatches:
(root@aldur) (~) # cat /proc/version
Linux version 5.4.0-4-amd64 (debian-ker...@lists.debian.org) (gcc
version 9.2.1 20200203 (Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1 (2020-02-13)
(root@aldur) (~) # gcc --version
gcc (Debian 9.3.0-10) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
I tried to find the debian package providing gcc-9.2 on
http://ftp.fr.debian.org/debian/pool/main/g/gcc-9/ ... without success
Could you please either provide the appropriate compiler or provide a version
of linux-image using the current version of gcc-9 ?
Thanks !
Best regards
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages build-essential depends on:
ii dpkg-dev 1.19.7
ii g++ 4:9.2.1-3.1
ii gcc 4:9.2.1-3.1
ii libc6-dev [libc-dev] 2.30-4
ii make 4.2.1-1.2
build-essential recommends no packages.
build-essential suggests no packages.
-- no debconf information
Bug#956633: libpango-1.0-0: After upgrading from 1.42.4-8 to 1.44.7-3: Wrong font rendering in geany
Control: retitle -1 libpango-1.0-0: 1.44.7-3 regression: wrong font rendering in geany/hexchat: invisible underscores On Tue, 14 Apr 2020 08:20:29 +0800 Paul Wise: wrote: > I have a similar issue in hexchat and I get the invisible underscores. > I noticed that not all fonts are affected, in particular DejaVu Sans > Mono and Bitstream Vera Sans Mono are affected but Liberation Mono is > not affected. I noticed that it doesn't affect the pango-view tool. I also noticed that this is size dependent, 10pt works, 11pt doesn't. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#956633: libpango-1.0-0: After upgrading from 1.42.4-8 to 1.44.7-3: Wrong font rendering in geany
On Mon, 13 Apr 2020 21:24:25 +0200 Lukas Straub wrote: > After upgrading libpangocairo-1.0-0 and libpango-1.0-0 from 1.44.7-3 to > 1.42.4-8, fonts are rendered wrong in geany. It seems the cahracters are > too low, so for example underscores are invisible. I'll send some > screenshots by mail. I have a similar issue in hexchat and I get the invisible underscores. I noticed that not all fonts are affected, in particular DejaVu Sans Mono and Bitstream Vera Sans Mono are affected but Liberation Mono is not affected. I noticed that it doesn't affect the pango-view tool. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#956659: autopkgtest-build-qemu fails to create an image for qemu
Package: autopkgtest
Version: 5.12.1
Severity: important
Hello,
I'm no longer able to create an image for autopkgtest with
# autopkgtest-build-qemu unstable ./autopkgtest.img
Load spec file /tmp/tmp.r8ug3ZCECh
ERROR: No runner implements step with keys device, set
It seems to be because of this part of autopkgtest-build-qemu script,
that was added with commit adc0aa94 [1]
- set: flag
device: "{{ image }}"
The above error disappear if I remove that part from the script,
and the process goes ahead. Not sure if it's a bug in autopkgtest
or in vmbd2.
However, even with the autopkgtest-build-qemu script modified,
the creation of the image fails with another error
autopkgtest-build-qemu unstable ../autopkgtest.img
Load spec file /tmp/tmp.GYgpSOLAo0
Exec: ['qemu-img', 'create', '-f', 'raw', '../autopkgtest.img.raw', '25G']
Exec: ['parted', '-s', '../autopkgtest.img.raw', 'mklabel', 'gpt']
Exec: ['parted', '-m', '../autopkgtest.img.raw', 'print']
Exec: ['parted', '-s', '../autopkgtest.img.raw', 'mkpart', 'primary', 'ext2',
'0%', '5%']
Exec: ['parted', '-m', '../autopkgtest.img.raw', 'print']
Exec: ['parted', '-s', '../autopkgtest.img.raw', 'mkpart', 'primary', 'ext2',
'5%', '100%']
Exec: ['kpartx', '-asv', '../autopkgtest.img.raw']
remembering /dev/mapper/loop1p1 as boot
remembering /dev/mapper/loop1p2 as root
Exec: ['/sbin/mkfs', '-t', 'ext4', '/dev/mapper/loop1p2']
Exec: ['mount', '/dev/mapper/loop1p2', '/tmp/tmpmgw2bhok']
Exec: ['debootstrap', '--variant', '-', 'unstable', '/tmp/tmpmgw2bhok',
'http://deb.debian.org/debian']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', 'update']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', 'update']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', '-y', '--no-show-progress',
'install', 'eatmydata']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'eatmydata', 'apt-get', 'update']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'eatmydata', 'apt-get', '-y',
'--no-show-progress', 'install', 'linux-image-amd64', 'ifupdown']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', 'clean']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
Installing GRUB for BIOS
Exec: ['mount', '--bind', '/dev', '/tmp/tmpmgw2bhok/dev']
Exec: ['mount', '--bind', '/sys', '/tmp/tmpmgw2bhok/sys']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'apt-get', '-y', '--no-show-progress',
'install', 'grub-pc']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'grub-mkconfig', '-o',
'/boot/grub/grub.cfg']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', '-t', 'proc', 'proc',
'/proc']
Exec: ['chroot', '/tmp/tmpmgw2bhok', 'grub-install', '--target=i386-pc',
'--no-nvram', '--force-extra-removable', '--no-floppy', '--modules=part_msdos
part_gpt', '--grub-mkdevicemap=/boot/grub/device.map', '/dev/loop1']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
unmounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']
umount: /proc: not mounted.
ERROR: Command '['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc']' returned
non-zero exit status 32.
ERROR: CalledProcessError(32, ['chroot', '/tmp/tmpmgw2bhok', 'umount', '/proc'])
Something went wrong, cleaning up!
Exec: ['umount', '/tmp/tmpmgw2bhok/dev']
Exec: ['umount', '/tmp/tmpmgw2bhok/sys']
Exec: ['umount', '/tmp/tmpmgw2bhok']
Exec: ['kpartx', '-dsv', '../autopkgtest.img.raw']
and I'm not able to work around this; any ideas?
Regards,
Lorenzo
[1]
https://salsa.debian.org/ci-team/autopkgtest/-/commit/adc0aa941cd31c7ccb90f4ca030d6c15973af9f5
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked
Bug#956658: firmware-misc-nonfree: Missing firmware for i915 intel cards
Package: firmware-misc-nonfree Version: 20190717-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? My computer is an Asus UX433F which embeds a Nvidia and an Intel video card. I use a Debian Bullseye up-to-date. When I installed nvidia-driver, which returned the following results. Paramétrage de nvidia-driver (440.64-2) ... Traitement des actions différées (« triggers ») pour libc-bin (2.30-4) ... Traitement des actions différées (« triggers ») pour initramfs-tools (0.136) ... update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915 Traitement des actions différées (« triggers ») pour update-glx (1.1.0) ... Traitement des actions différées (« triggers ») pour glx-alternative-nvidia (1.1.0) ... update-alternatives: utilisation de « /usr/lib/nvidia » pour fournir « /usr/lib/glx » (glx) en mode automatique Traitement des actions différées (« triggers ») pour glx-alternative-mesa (1.1.0) ... Traitement des actions différées (« triggers ») pour systemd (245.4-3) ... Traitement des actions différées (« triggers ») pour libc-bin (2.30-4) ... Traitement des actions différées (« triggers ») pour initramfs-tools (0.136) ... update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915 * What outcome did you expect instead? The missing firmware should be available when installing the firmware-misc-nonfree package. Thanks Best regards *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-misc-nonfree depends on no packages. firmware-misc-nonfree recommends no packages. Versions of packages firmware-misc-nonfree suggests: ii initramfs-tools 0.136 -- no debconf information
Bug#956657: phonon4qt5-backend-vlc: Sound crashes after few seconds
Package: phonon4qt5-backend-vlc Version: 0.11.1-1 Severity: important Dear Maintainer, * What led up to the situation? I updated my Debian Buster. I tried to play a video on youtube through chromium. Few seconds after started the video, the sound crashed. * What exactly did you do (or not do) that was effective (or ineffective)? I installed phonon4qt5-backend-gstreamer and restarted my computer. * What was the outcome of this action? Switching to gstreamer circumvent my problem. * What outcome did you expect instead? It would be nice to have phonon working with vlc too. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages phonon4qt5-backend-vlc depends on: ii libc62.30-4 ii libphonon4qt5-4 4:4.11.1-3 ii libqt5core5a 5.12.5+dfsg-9 ii libqt5gui5 5.12.5+dfsg-9 ii libqt5widgets5 5.12.5+dfsg-9 ii libstdc++6 10-20200324-1 pn libvlc5 pn libvlccore9 pn vlc-plugin-base pn vlc-plugin-video-output phonon4qt5-backend-vlc recommends no packages. phonon4qt5-backend-vlc suggests no packages.
Bug#956656: gnome-shell-extension-system-monitor: Missing source file: gpu_usage.sh
Package: gnome-shell-extension-system-monitor Version: 38-2 Severity: normal Dear Maintainer, A source file is missing from the deb package: gpu_usage.sh is not copied over. This prevents the user from using the Gpu options. Perhaps adding a Suggests on glxinfo (for AMD cards) could help the user decide whether to install that as well. Best regards, Santiago -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-system-monitor depends on: ii gir1.2-clutter-1.0 1.26.4+dfsg-1 ii gir1.2-gtop-2.0 2.40.0-2 ii gnome-shell 3.36.1-5 gnome-shell-extension-system-monitor recommends no packages. gnome-shell-extension-system-monitor suggests no packages.
Bug#922222: Fwd: "A Brief History of Debian: Chapter 2 - Leadership" online page needs some update
Hi, Holger Wansing wrote: > > If noone objects, I will implement this solution then. > > In a first step, I have now added debian-history to 7doc as well. > Will see how it goes - fingers crossed... And now hamradio-maintguide and harden-doc added to 7doc. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#956171: gnome-shell-extension-system-monitor: please check compatibility with GNOME Shell 3.36.x
Dear maintainer, Please note that the necessary changes were committed to the upstream repository. Although no new version has been tagged yet, the code is in good shape as of today for 3.36. In order to keep the package installable in testing, a temporary `+git2020...` version could be uploaded. Best regards, Fran
Bug#956538: kde-config-fcitx5: cannot connect to fcitx via dbus error message
Hi Boyuan,
> some testing and examine its compatibility with native (GNOME) Wayland
> environment as well as its functionality to kill-and-{mimic,replace} ibus. As
Hmm, I am neither Gnome nor Wayland user ;-) I used to use Cinnamon and
now use my home compiled KDE/Plasma ;-)
Best
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#956655: nftables preinst / postrm depend on bash
Package: nftables Version: 0.9.0-2 Hello, Trying to install iptables in a container, nftables installation fails because preinst / postrm scripts use /bin/bash, which is not present in the container and not a dependency apt logs extract: Preparing to unpack .../08-nftables_0.9.0-2_amd64.deb ... dpkg (subprocess): unable to execute new nftables package pre-installation script (/var/lib/dpkg/tmp.ci/preinst): No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-LOgXvP/08-nftables_0.9.0-2_amd64.deb (--unpack): new nftables package pre-installation script subprocess returned error exit status 2 dpkg (subprocess): unable to execute new nftables package post-removal script (/var/lib/dpkg/tmp.ci/postrm): No such file or directory dpkg: error while cleaning up: new nftables package post-removal script subprocess returned error exit status 2 beginning of preinst: #!/bin/bash set -e dpkg-maintscript-helper rm_conffile \ /etc/nftables/bridge-filter \ 0.5+snapshot20151106-1 nftables -- "$@" Etienne
Bug#956538: kde-config-fcitx5: cannot connect to fcitx via dbus error message
在 2020-04-13星期一的 06:48 +0900，Norbert Preining写道：
> On Sun, 12 Apr 2020, Boyuan Yang wrote:
> > Are you using fcitx or fcitx5? They are completely different packages and
> > should not be mixed together.
>
> Ah .. uhmm ... sorry for the noise. Yes, with the correct version it
> works. Closing this bug.
>
> BTW, is fcitx5 prime for working with it? I am a happy user of fcitx
> since years (and was burned by ibus many times), and I'm happy doing
> some testing with fcitx5.
Looks like fcitx5 is still not ready for production use. There's still no
ABI/API compatibility guarantee. However, it would be great if you could do
some testing and examine its compatibility with native (GNOME) Wayland
environment as well as its functionality to kill-and-{mimic,replace} ibus. As
a GNOME-on-Xorg user, I personally haven't tested these areas at all so such
testing report would be interesting.
--
Regards,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#956625: texlive-luatex fails to install: running `luatex -ini -jobname=optex -progname=optex optex.ini
tags 956625 + pending thanks > ! Font \_tenrm=ec-lmr10 not loadable: metric data not found or bad. > > \_font > l.8 \_font > \_tenbf=ec-lmbx10 % boldface extended > ? > ! Emergency stop. > > \_font > l.8 \_font > \_tenbf=ec-lmbx10 % boldface extended > ! ==> Fatal error occurred, no output PDF file produced! > Transcript written on optex.log. Fixed in git. Thanks for the report. Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#956633: libpango-1.0-0: After upgrading from 1.42.4-8 to 1.44.7-3: Wrong font rendering in geany
On Mon, Apr 13, 2020, 3:27 PM Lukas Straub wrote: Package: libpango-1.0-0 Version: 1.44.7-3 Severity: normal Dear Maintainer, After upgrading libpangocairo-1.0-0 and libpango-1.0-0 from 1.44.7-3 to 1.42.4-8, fonts are rendered wrong in geany. It seems the cahracters are too low, so for example underscores are invisible. I'll send some screenshots by mail. The second screenshot is wrong. Those function names are supposed to have underscores. Thanks, Jeremy Bicha
Bug#956654: dh-python: man pybuild refers to http://deb.li/pybuild, points to an old page
Package: dh-python Version: 4.20200315 Severity: normal Hello, man pybuild refers to http://deb.li/pybuild which resolves to https://anonscm.debian.org/cgit/dh-python/dh-python.git/tree/pybuild.rst but that 404s now. Can you update the shortened url to the new doc location? Thanks, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-python depends on: ii python33.7.5-3 ii python3-distutils 3.8.0-1 dh-python recommends no packages. Versions of packages dh-python suggests: ii dpkg-dev 1.19.7 ii libdpkg-perl 1.19.7 -- no debconf information
Bug#956613: lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated
On Mon 2020-04-13 09:52:32 -0700, Felix Lechner wrote: > I do not see that tag when running lintian's development version > against balsa from unstable: there are separate issues with the appdata files in 2.5.9 (that have since been fixed upstream): https://gitlab.gnome.org/GNOME/balsa/-/merge_requests/22 so the issue only shows up in 2.6.0 (which just landed in unstable today) > Lintian should not complain, for a source package, about files not > shipped within it. Was the file perhaps included accidentally? ah, i might have gotten confused about the file name due to it being overwritten during the build. i do most of my packaging work from a gbp tree, and that tree has the generated files already pre-stripped (via an import-orig filter in debian/gbp.conf). Looks like upstream does in fact ship a copy of these generated files in the tarball, though, so i probably should mark them in debian/copyright anyway. I'm closing this ticket because it looks like i do need to mark the generated file in d/copyright anyway, which means there's a more obvious fix for me to do in this packaging. sorry for the noise! --dkg signature.asc Description: PGP signature
Bug#956653: python3-xapian-haystack: Broken compatibility with haystack on Debian Buster 10
Package: python3-xapian-haystack Version: 2.1.0-3 Severity: important Dear Maintainer, This is a follow-up of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951207 I configured xapian-haystack as the haystack backend of mailman3 on a Debian 10 system. When I try to index a mailing list, I get the error: [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): update() got an unexpected keyword argument 'commit' (pid 28083): update() got an unexpected keyword argument 'commit' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) TypeError: update() got an unexpected keyword argument 'commit' [...] If I apply the patch, the indexing works successfully. Please backport the change to stable-updates as well, otherwise the archiving feature of mailman is broken when using the efficient xapian backend. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (850, 'testing'), (800, 'unstable'), (750, 'experimental'), (750, 'stable'), (500, 'unstable-debug'), (500, 'stable-debug'), (500, 'oldstable-debug'), (500, 'buildd-unstable'), (500, 'oldstable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-xapian-haystack depends on: ii python3 3.8.2-2 pn python3-django-haystack ii python3-xapian 1.4.15-1+b1 python3-xapian-haystack recommends no packages. python3-xapian-haystack suggests no packages.
Bug#956652: svgtune: Should we remove this package?
Source: svgtune Severity: serious Version: 0.2.0-2 Tags: sid bullseye X-Debbugs-CC: y...@debian.org Dear package svgtune maintainer, A new upload of src:lxml was just made to drop package python-lxml from Sid. Since this is also the dependency of svgtune, package svgtune is now uninstallable in Sid (and Bullseye). Since there were no upload for svgtune since 2015 and that it upstream also had no activity since 2015, it might be reasonable for us to clean up the Debian repository and remove package svgtune from Sid/Bullseye. I will submit a removal request 21 days later (After May 04, 2020). If you are to migrate this package to python3 or have any other thoughts, please let me know *immediately* so that we could properly save this package in time. Thank you for your work in Debian and looking forward to your reply. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#956651: RM: backports.functools-lru-cache -- ROM; python2-only; backport of a python3.3 module; no rdeps
Package: ftp.debian.org Severity: normal
Bug#956650: awl: CVE-2020-11728 CVE-2020-11729
Source: awl Version: 0.60-1 Severity: important Tags: security upstream Two security vulnerabilities were found in the awl package: CVE-2020-11728 Session::__construct() allows use of the current time as a session key https://gitlab.com/davical-project/awl/-/issues/19 CVE-2020-11729 LSIDLogin() is insecure and can allow user impersonation https://gitlab.com/davical-project/awl/-/issues/18 All supported Debian releases are affected.
Bug#956639: [Pkg-utopia-maintainers] Bug#956639: Fails to start
Am 13.04.20 um 23:03 schrieb David Prévot: > Once removed the old file from /etc/NetworkManager/system-connections > that referenced the now non-existing file, the crash is the same, and > the syslog (besides the previous warning line not displayed anymore) is > identical. Ok, in that case, it would be good to gather a back trace and send this upstream to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/ signature.asc Description: OpenPGP digital signature
Bug#956605: texlive-bin: FTBFS on powerpc & sparc64
Am 13.04.2020 um 16:35 teilte Hilmar Preusse mit: Hi, > The build fails at least on powerpc & sparc64. Interestingly > it still worked when the -1 was uploaded to experimental. The > build fails b/c a header file is missing. > I tried to reproduce the issue using sbuild like this: sbuild --host=powerpc -d unstable --extra-repository='deb http://ftp.ports.debian.org/debian-ports/ sid main' --extra-repository-key=/usr/share/keyrings/debian-ports-archive-keyring.gpg texlive-bin For any reason some packages can't be installed into the sbuild chroot, although they are available in the porters archive. Not sure, what I'm doing wrong here. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-main-dummy:powerpc : Depends: libgd-dev:powerpc but it is not going to be installed Depends: libxaw7-dev:powerpc but it is not going to be installed Depends: texlive-binaries:powerpc E: Unable to correct problems, you have held broken packages. H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#956649: libgnutls30: Visiting some websites results in an "Unexpected TLS packet during handshake" error
Package: libgnutls30 Version: 3.6.7-4+deb10u3mhoran0 Severity: normal Dear Maintainer, This error is documented best in an upstream issue: https://gitlab.com/gnutls/gnutls/-/issues/841. In my experience this issue manifests in the liferea feed reader, and can be quite persistent. The issue is resolved in newer releases by the patch in https://gitlab.com/gnutls/gnutls/-/merge_requests/1087. I applied this patch to the version of libgnutls30 in buster and it resolves the issue for me. I'm hoping that either the patch above can be included in Debian buster, or a later release can be backported (3.6.13 from bullseye would be sufficient.) Thanks, Matt -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgnutls30 depends on: ii libc6 2.28-10 ii libgmp10 2:6.1.2+dfsg-4 ii libhogweed43.4.1-1 ii libidn2-0 2.0.5-1+deb10u1 ii libnettle6 3.4.1-1 ii libp11-kit00.23.15-2 ii libtasn1-6 4.13-3 ii libunistring2 0.9.10-1 libgnutls30 recommends no packages. Versions of packages libgnutls30 suggests: pn gnutls-bin -- no debconf information
Bug#956648: RFS: freecdb/0.76 [QA] -- creating and reading constant databases
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "freecdb"
* Package name: freecdb
Version : 0.76
Upstream Author : D. J. Bernstein
* URL :
* License :
* Vcs : https://salsa.debian.org/debian/freecdb
Section : utils
It builds those binary packages:
freecdb - creating and reading constant databases
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/freecdb
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/f/freecdb/freecdb_0.76.dsc
Changes since the last upload:
* QA upload.
* Mark source format as 3.0
* Update Standards-Version to 4.5.0
* Orphan the package. (See: #947698)
* Use debhelper-compat.
- Mark compat level to 12.
- Add dependency on ${misc:Depends}.
* simplify debian/rules.
- list files to install.
- list man pages.
- remove debian/implicit.
* Fix FTBFS with clang. (Closes: #757409)
- Thanks to Arthur Marble.
* Add Vcs link to salsa.
--
Regards
Sudip
Bug#946574: Add --conformable option to output all conformable units
We have added a --conformable option which displays the conformable units in a similar manner to using the "?" interactively. We will not support "?" in non-interactive units as suggested below. We also have decided that the suggested multi-conversion behavior is not useful enough to warrant addition to the core program. A script can be used to do this, with a pipe for efficiency if you're in a hurry, so something like this (once the --conformable option is released): #!/bin/sh if [ -z "$1" ] then echo Must supply argument to convert exit fi for unit in `./units --conformable $1 | cut -f 1 -d ' '` do echo "$1" echo $unit done | units --terse --verbose which produces the output below when run on 'coulomb': coulomb = 1 C coulomb = 1 CHARGE coulomb = 1 D_FLUX coulomb = 2.9979246e+09 Fr coulomb = 0.1 abC coulomb = 0.1 abcoul coulomb = 0.1 abcoulomb coulomb = 6.2415091e+18 atomiccharge coulomb = 1 coul coulomb = 1 coulomb coulomb = 0.9991 coulomb90 coulomb = 6.2415091e+18 e coulomb = 2.9979246e+09 esu coulomb = 1.036427e-05 faraday coulomb = 1.0363156e-05 faraday_chem coulomb = 1.0360343e-05 faraday_phys coulomb = 2.9979246e+09 franklin coulomb = 2.9979246e+09 stC coulomb = 2.9979246e+09 statC coulomb = 2.9979246e+09 statcoul coulomb = 2.9979246e+09 statcoulomb On Sat, Dec 21, 2019 at 04:00:47AM +0800, 積丹尼 Dan Jacobson wrote: > > "AM" == Adrian Mariano writes: > AM> So basically you're asking for a command line equivalent to the '?' > interactive command? > > Well, please first fix this > $ units FORCE \? > Unknown unit '?' > > so it works just like > > AM> You have: FORCE > AM> You want: ? > > Next, if we gave it > You have: cm > You have: 3.75cm > You have: m > > Then the > You want: ? > should be enhanced to give different output for each.
Bug#956646: harfbuzz: FTBFS on kfreebsd-amd64 - test suite fails
Source: harfbuzz Version: 2.6.4-1 Severity: important Dear Maintainer, the package fails in the test suite: FAIL: check-libstdc++.sh Checking that we are not linking to libstdc++ or libc++ in .libs/libharfbuzz.so libstdc++.so.6 => /usr/lib/x86_64-kfreebsd-gnu/libstdc++.so.6 (0x00080380) Ouch, linked to libstdc++ or libc++ Checking that we are not linking to libstdc++ or libc++ in .libs/libharfbuzz-gobject.so libstdc++.so.6 => /usr/lib/x86_64-kfreebsd-gnu/libstdc++.so.6 (0x00080440) Ouch, linked to libstdc++ or libc++ FAIL check-libstdc++.sh (exit status: 1) No clue why the test is needed and how to solve it. We recently uploaded texlive-bin to Debian unstable. Without solving this issue, it won't be available for this arch as the BD is now versioned. Hilmar -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 5.5.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#956647: debian-faq: get rid of xmlroff dependency
Package: debian-faq
Severity: wishlist
Tags: patch
Hi,
attached is a patch to get rid of the xmlroff build dependency.
Since switching from debiandoc to docbook, xmlroff is effectively of no use
anyway.
So long
Holger
--
Holger Wansing
PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
diff --git a/Makefile b/Makefile
index 3a07298..090b1c4 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
#
-# Makefile for the release notes, top-level
+# Makefile for the debian-faq (docbook format)
#
# comment out this line when the debian-faq should go into
@@ -38,13 +38,10 @@ ALL_LANGUAGES := $(LANGUAGES) $(DISABLED_LANGUAGES)
# (either original English or translators don't like .po)
DBK_LANGUAGES := en
PO_LANGUAGES := $(filter-out $(DBK_LANGUAGES), $(ALL_LANGUAGES))
-XMLROFF_LANGS=zh-cn
PO_FILES := $(wildcard */*.po)
# DISABLED_PDF are the languages we will not generate PDF versions for:
DISABLED_PDF=ja zh-cn
-# cairo backend of xmlroff 0.6.0 crashes on some languages (#492597)
-GPLIST=ja
LANGUAGES-publish := $(addsuffix -publish,$(LANGUAGES))
LANGUAGES-clean := $(addsuffix -clean,$(LANGUAGES))
@@ -83,8 +80,6 @@ DBLATEX=dblatex --backend=xetex --style=db2latex \
PROFILE=$(DOCBOOK_XSL)/profiling/profile.xsl
PREPROC=$(CURDIR)/preproc.xsl
DBLATEXXSL=$(CURDIR)/dblatex.xsl
-XMLROFF=xmlroff --backend cairo
-XMLROFF_GP=xmlroff --backend gp
FORMATS=html txt pdf
@@ -138,38 +133,16 @@ $(LINGUA)/$(LINGUA)/index.$(LINGUA).html: \
$(DBK2HTML) $(manual).$(LINGUA).xml
pdf:: $(LINGUA)/$(manual).$(LINGUA).pdf
-ifneq "$(filter $(XMLROFF_LANGS),$(LINGUA))" ""
-$(LINGUA)/$(manual).$(LINGUA).pdf: \
- $(LINGUA)/$(manual).$(LINGUA).fo
-$(LINGUA)/$(manual).$(LINGUA).fo: \
- $(LINGUA)/$(manual).$(LINGUA).xml fo.xsl
-else
$(LINGUA)/$(manual).$(LINGUA).pdf: \
$(LINGUA)/$(manual).$(LINGUA).xml
-endif
-
ifneq "$(filter $(DISABLED_PDF),$(LINGUA))" ""
cp nopdf.pdf $(LINGUA)/$(manual).$(LINGUA).pdf
else
-ifneq "$(filter $(XMLROFF_LANGS),$(LINGUA))" ""
-%.fo: %.xml xmlroff.xsl
- $(XP) xmlroff.xsl $< |$(XP) --output $@ fo.xsl -
-
-%.pdf: %.fo
- @test -n "`which xmlroff`" || { echo "ERROR: xmlroff not found. Please install the xmlroff package." ; false ; }
- USE_GP=`echo " $(GPLIST) " | grep " $$LINGUA "`; \
- if [ -n "$$USE_GP" ]; then \
- $(XMLROFF_GP) -o $@ $<; \
- else \
- $(XMLROFF) -o $@ $<; \
- fi
-else
%.pdf: %.xml
@test -n "`which dblatex`" || { echo "ERROR: dblatex not found. Please install the dblatex package." ; false ; }
export TEXINPUTS="$$(pwd)/$(@D):"; \
$(XP) $(DBLATEXXSL) $< | $(DBLATEX) --output=$@ -
endif
-endif
txt:: $(LINGUA)/$(manual).$(LINGUA).txt
$(LINGUA)/$(manual).$(LINGUA).txt: \
diff --git a/debian/changelog b/debian/changelog
index 9d243ff..af5469e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+debian-faq (10.1+nmu1) UNRELEASED; urgency=medium
+
+ * Get rid of Build-Depends-Indep: xmlroff (no more in effective use).
+
+ -- Holger Wansing Mon, 13 Apr 2020 23:04:27 +0200
+
debian-faq (10.1) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index 3402e84..f1f3f15 100644
--- a/debian/control
+++ b/debian/control
@@ -15,7 +15,6 @@ Build-Depends-Indep: dblatex ,
texlive-lang-all ,
texlive-xetex ,
w3m,
- xmlroff,
xsltproc
Standards-Version: 4.4.0
Rules-Requires-Root: no
Bug#937791: Blocked on reverse dependencies
On Sat, Feb 08, 2020 at 11:13:20AM -0800, Martin Kelly wrote: > On Sat, 8 Feb 2020 10:55:23 -0800 Martin Kelly > wrote: > > On 2/2/20 8:39 PM, Sandro Tosi wrote: > > > should we remove this package then? or do you want to generate a > > > python3-gmpy? > > > > > > > I didn't realize, but it looks like this package actually does support > > Python 3. I had assumed we would let this package die when Python 2 > > dies, since the package is dead upstream since 2013. However, looking at > > the popcon stats, the original python GMPY is still much more popular > > than than python GMPY2 (3543 vs 443). So I think it's worth keeping this > > package. > > > > I'm working on converting it over now and should be able to get it done > > in the next few weeks. > > > > Is it possible to remove the AUTORM tag until this is done, or should we > > let it get deleted and upload a new python3-gmpy package after that? > > > > Looking further, it seems that with current versions of Python 3 (I tested > with 3.7.3), the old GMPY 1.17 is no longer passing. When I run > test3/gmpy_test.py, I'm getting: > > $ python3 test3/gmpy_test.py > ... > 8 items had failures: >1 of 4 in gmpy_test_cvr >4 of 126 in gmpy_test_cvr.__test__.user_errors >1 of 1 in gmpy_test_dec >2 of 2 in gmpy_test_mpf >2 of 60 in gmpy_test_mpf.__test__.binio >2 of 2 in gmpy_test_mpq >2 of 4 in gmpy_test_mpz >7 of 25 in gmpy_test_rnd.__test__.rand > 1504 tests in 42 items. > 1483 passed and 21 failed. > ***Test Failed*** 21 failures. > > In contrast, the tests for GMPY 2 all succeed, so I think the author clearly > intended for tests to fully pass. Since this hasn't been maintained for 7 or > so years, I'm not too surprised. > > Given this, I think we should let this package be removed and consider > resurrecting it in the future if people ask for it and someone will step up > to maintain it. > > Sandro, is there anything more to do if I want to let this package be > removed, or do I just wait for the auto-removal? Martin, what are you referring here to with "removed"? Removal from testing or unstable? The former happened automatically in the mean time, the latter needs a bug using "reportbug ftp.debian.org" Cheers, Moritz
Bug#945271: python-ipcalc: Oprhaning package
On Fri, Nov 22, 2019 at 09:23:59AM +0100, Florian Pelgrim wrote: > Package: python-ipcalc > Version: 1.99.0-3.1 > Severity: important > > Hi community, > > I'm going to orphan this package. > > TL;DR I'm fine to have this package removed from the debian project. > IMHO it's dead and will not come back to life. > > sshfp is the only package having python-ipcalc as a dependency, but this > code has been touched last time 2015. So it is pure python2 and will > probably be also removed soon. sshfp has been removed in the mean time, so I've just filed an RM bug. Cheers, Moritz
Bug#956645: RM: python-ipcalc -- RoQA; Depends on Python 2, no reverse deps, orphaned
Package: ftp.debian.org Severity: normal Please remove python-ipcalc. It depends on Python 2, there are no reverse deps, it's orphaned and the former maintainer (CCed) suggested it's removal in #945271. Cheers, Moritz
Bug#956552: arno-iptables-firewall: 90-rpc.plugin causes arno to fail to start.
juri@ni:~/ImplicitCAD$ rpcinfo -p program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 111 udp 55732 rstatd 112 udp 55732 rstatd 113 udp 55732 rstatd 114 udp 55732 rstatd 115 udp 55732 rstatd 122 udp 32946 rusersd 123 udp 32946 rusersd 151 udp 33137 mountd 151 tcp 42829 mountd 152 udp 37118 mountd 152 tcp 54383 mountd 153 udp 60251 mountd 153 tcp 55123 mountd 133 tcp 2049 nfs 134 tcp 2049 nfs 1002273 tcp 2049 133 udp 2049 nfs 1002273 udp 2049 1000211 udp 41751 nlockmgr 1000213 udp 41751 nlockmgr 1000214 udp 41751 nlockmgr 1000211 tcp 46653 nlockmgr 1000213 tcp 46653 nlockmgr 1000214 tcp 46653 nlockmgr On Sun, Apr 12, 2020 at 11:00 PM Sven Geuer wrote: > Hi Julia, > > Thank you for filing this bug. > > In addition, could you please attach a sample output of 'rpcinfo -p' to > have the full picture of why this happens? > > Regards, > Sven >
Bug#956643: wireguard-tools: shipped without file:/etc/network/interfaces.d/wg0
Package: wireguard-tools Version: 1.0.20200319-1~bpo10+1 Severity: important Tags: a11y patch Dear Daniel, many thx for bringing wireguard-tools to Debian 10! While less so than for OpenVPN, configuring your WireGuard in 1.0.20200319 still costs me a lot of reading and thinking time that could be eased with pre-installed conffiles for which i am supplying the following suggestion to start with: # file:/etc/network/interfaces.d/wg0 # requiring file:/etc/network/interfaces to state # source /etc/network/interfaces.d/* # and allowing initial wg set wg0 private-key <(wg genkey) # 2020.04.14.©©-by-sa ro...@czyborra.com auto wg0 iface wg0 inet6 manual up ip link add wg0 type wireguard up wg setconf wg0 /etc/wireguard/wg0.conf downumask 077 && wg showconf wg0>/etc/wireguard/wg0.conf downip link del wg0 -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireguard-tools depends on: ii libc6 2.28-10 Versions of packages wireguard-tools recommends: ii iptables1.8.2-4 ii nftables0.9.0-2 ii wireguard-dkms 0.0.20200318-1~bpo10+1 wireguard-tools suggests no packages. -- no debconf information
Bug#936459: dvcs-autosync: Python2 removal in sid/bullseye
On Sat, Mar 28, 2020 at 07:30:12PM +0100, René Mayrhofer wrote: > Hi Moritz, > > The state on Github is unfortunately incomplete, as I got stuck in the > process of converting to Python 3. The problem is that the XMPP library > I used before hasn't been ported to Python 3 and I would either need to > change to a different XMPP support or to another protocol - considering > MQTT as a lightweight alternative. However, I haven't found time to > actually finish that part, and the current situation isn't helping. Ack, thanks for the update! Cheers, Moritz
Bug#956587: texlive-binaries: needs Breaks/Replaces on older texlive-extra-utils
Control: tags -1 + pending Am 13.04.2020 um 12:40 teilte Simon McVittie mit: Hi Simon, > In practice you can probably relax the version constraint to > (<< 2020.20200329) or even (<< 2020) if you know when the file involved > moved between packages, but using the full version as suggested above > is the safe/conservative option. > I used (<< 2020.20200329). Bug is solved in git, tag pending. H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#956644: RM: python-xmpp -- RoQA; Depends on Python 2, dead upstream, orphaned/unmaintained
Package: ftp.debian.org Severity: normal Please remove python-xmpp. It's dead upstream, depends on Python 2 and orphaned since 2017 without an adopter. There's one reverse dependency (dvcs-autosync), but it's being ported away from python-xmpp (936459) and it's RC-buggy and dropped from testing, so seem fair enough to not block the removal of python-xmpp with it. Cheers, Moritz
Bug#956639: [Pkg-utopia-maintainers] Bug#956639: Fails to start
Hi Michael, Thanks for the quick reply Le 13/04/2020 à 10:22, Michael Biebl a écrit : > Am 13.04.20 um 22:09 schrieb David Prévot: >> Package: network-manager >> Version: 1.23.90-1 […] >> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.4129] >> keyfile: 802-1x.ca-cert: certificat ou fichier clé « >> file:///home/taffit/ccc.cer » n'existe pas >> Apr 13 09:31:06 persil NetworkManager[1598787]: ** > > While I don't speak French (unfortunately), I think this means that one > of the connection profiles references a non-existent /home/taffit/ccc.cer > > Is that correct? Indeed. > Could you check if fixing/removing the (broken) connection makes the > keyfile plugin not crash? Once removed the old file from /etc/NetworkManager/system-connections that referenced the now non-existing file, the crash is the same, and the syslog (besides the previous warning line not displayed anymore) is identical. Regards David
Bug#697643: openntpd: Does not make large adjustments.
On Fri, 11 Nov 2016 17:48:45 -0300, Dererk wrote: > Usually from the standpoint of some servers that contain timestamp > operations embedded on them, like databases or things alike, enabling > -s could possible trigger data corruption, since from one instant to > the other time change backwards. This is also default behavior from > openntpd upstream. > > Personally I do have set -s on systems I know risks are not taken. Note that -s only makes large adjustments to the time on startup. In normal operation, this will occur only when the system boots, before any databases or other critical processes begin. I don't see that the upstream default is reasonable, especially when I see messages like the following in my system log: Apr 13 00:23:00 test64 ntpd[931]: adjusting local clock by 199.207333s Apr 13 00:25:39 test64 ntpd[931]: adjusting local clock by 199.127660s Apr 13 00:29:20 test64 ntpd[931]: adjusting local clock by 199.017683s Apr 13 00:30:25 test64 ntpd[931]: adjusting local clock by 198.985143s Apr 13 00:34:12 test64 ntpd[931]: adjusting local clock by 198.871842s Apr 13 00:37:22 test64 ntpd[931]: adjusting local clock by 198.776466s Apr 13 00:38:56 test64 ntpd[931]: adjusting local clock by 198.728357s Apr 13 00:40:36 test64 ntpd[931]: adjusting local clock by 198.679637s I would argue that the expectation for openntpd in Debian is to work as a drop-in replacement for ntp, and so should be configured to behave similarly, even if this differs from the upstream default. That is, presumably, why the config file lists four Debian NTP pool systems. If there are data-loss issues that arise with -s, then these should also arise with -g in ntp---and would have a much bigger impact there, as that package is many times more popular. Can -s be made the default in /etc/default/openntpd ? --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.
Bug#956642: RM: python-sptest -- RoQA; Depends on Python 2, dead upstream, unmaintained
Package: ftp.debian.org Severity: normal Please remove python-sptest. It depends on Python 2, is dead upstream (last commit from 2008) and there hasn't been a maintainer upload since 2008 either. Cheers, Moritz
Bug#941991: gnome-shell: crashes on startup (Wayland only) with "JS ERROR: TypeError: actor.get_meta_window(...) is null"
On Sun, Apr 12, 2020 at 7:57 AM Simon McVittie wrote: > On Tue, 08 Oct 2019 at 13:59:12 -0400, Zack Weinberg wrote: > > On my computer, after upgrading to gnome-shell 3.34, I consistently get a > > gnome-shell catastrophic failure about 10 seconds after logging in, but only > > when running under Wayland. > > Do you mean that you literally log in, wait for 10 seconds without doing > anything, and the shell crashes; or is there something else you do that > is or might be the trigger? I literally log in, wait 10 seconds without doing anything, and the shell crashes. > What GPU(s) do you have? If you have an NVIDIA device, are you using the > proprietary nvidia-graphics-drivers or the open source Mesa/Nouveau drivers? 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 740] Using the open source drivers. > Does this still happen in newer versions? > Do you have any GNOME Shell extensions enabled? Unfortunately, the affected computer is my office workstation and the building is closed to all personnel for the duration of the COVID-19 crisis. If it is possible to determine the answers to these questions somehow via ssh-ing into the box and typing commands, please tell me what to do; otherwise I will not be able to answer them anytime soon. Sorry. zw
Bug#956641: facter: diff for NMU 3.11.0-4.1
Source: facter
Version: 3.11.0-4
Severity: normal
Tags: patch
I just uploaded the attached diff as an NMU to unblock the Ruby
transition. Please apply it to your packaging vcs.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
diff --git a/debian/changelog b/debian/changelog
index 9f575b68..3c1bc8c6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+facter (3.11.0-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Add patch to not fail build when bundler is installed (Closes: #956300)
+ * Add a dependency on the minimal Ruby version needed (Closes: #956301)
+
+ -- Antonio Terceiro Mon, 13 Apr 2020 16:45:20 -0300
+
facter (3.11.0-4) unstable; urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index bb5757bd..9b6cdc87 100644
--- a/debian/control
+++ b/debian/control
@@ -36,7 +36,7 @@ Homepage: https://github.com/puppetlabs/facter
Package: facter
Architecture: any
-Depends: libfacter3.11.0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
+Depends: libfacter3.11.0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${ruby-interpreter:Depends}
Description: collect and display facts about the system
Facter is Puppet’s cross-platform system profiling library. It discovers and
reports per-node facts, which are collected by the Puppet agent and are made
diff --git a/debian/gen-ruby-dependency b/debian/gen-ruby-dependency
new file mode 100755
index ..bcfd2a84
--- /dev/null
+++ b/debian/gen-ruby-dependency
@@ -0,0 +1,9 @@
+#!/usr/bin/ruby
+
+require 'ruby_debian_dev'
+
+dependency = RubyDebianDev::RUBY_INTERPRETERS.map do |interp, data|
+ lib = data[:shared_library]
+ RubyDebianDev.min_ruby_dependency_for(lib)
+end.join(', ')
+puts "ruby-interpreter:Depends=#{dependency}"
diff --git a/debian/patches/0007-Don-t-run-rspec-via-bundler.patch b/debian/patches/0007-Don-t-run-rspec-via-bundler.patch
new file mode 100644
index ..31dc149b
--- /dev/null
+++ b/debian/patches/0007-Don-t-run-rspec-via-bundler.patch
@@ -0,0 +1,26 @@
+From: Antonio Terceiro
+Date: Thu, 9 Apr 2020 11:10:03 -0300
+Subject: Don't run rspec via bundler
+
+Closes: #956300
+---
+ CMakeLists.txt | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index ab7eb2e..4ca0392 100644
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -160,9 +160,9 @@ add_subdirectory(locales)
+ # Add test executables for unit testing
+ add_test(NAME "libfacter\\ tests" COMMAND libfacter_test)
+ if (RUBY_FOUND)
+-find_program(BUNDLER_PATH NAMES bundle.bat bundle)
+-if (BUNDLER_PATH)
+-add_test(NAME "libfacter\\ specs" COMMAND ${BUNDLER_PATH} exec rspec WORKING_DIRECTORY "${PROJECT_SOURCE_DIR}/lib")
++find_program(RSPEC_PATH NAMES rspec)
++if (RSPEC_PATH)
++add_test(NAME "libfacter\\ specs" COMMAND rspec WORKING_DIRECTORY "${PROJECT_SOURCE_DIR}/lib")
+ endif()
+ endif()
+ # Debian: disable the smoke tests, as the build environment lacks necessary
diff --git a/debian/patches/series b/debian/patches/series
index 8bae5647..9f3fef85 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@
0004-rapidjson-1.1-compat.patch
0005-fix-custom-facts-overriding-core.patch
0006-FACT-1916-fix-route-parsing-on-Linux.patch
+0007-Don-t-run-rspec-via-bundler.patch
diff --git a/debian/rules b/debian/rules
index 5de884da..fda516b0 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,3 +19,7 @@ override_dh_link:
/usr/lib/$(DEB_HOST_MULTIARCH)/libfacter.so.$(DEB_VERSION_UPSTREAM) \
"$${target}/libfacter.so"; \
done
+
+override_dh_gencontrol:
+ ./debian/gen-ruby-dependency >> debian/facter.substvars
+ dh_gencontrol
signature.asc
Description: PGP signature
Bug#956639: [Pkg-utopia-maintainers] Bug#956639: Fails to start
Am 13.04.20 um 22:09 schrieb David Prévot:
> Package: network-manager
> Version: 1.23.90-1
> Severity: important
>
> Hi,
>
> NetworkManager fails to start after the last update (reinstalling
> gir1.2-nm-1.0, libnm0, and network-manager from testing allowed me to
> use the WiFi again, I didn’t try to use wired network).
>
> Here is hopefully the relevant part of the syslog. I use a ThinkPad
> X220, please tell me if you need other information.
>
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3198]
> NetworkManager (version 1.23.90) is starting... (after a restart)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3200]
> Read config: /etc/NetworkManager/NetworkManager.conf (lib:
> no-mac-addr-change.conf)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3200]
> config: unknown key 'wifi.cloned-mac-address' in section
> [device-mac-addr-change-wifi] of file
> '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3200]
> config: unknown key 'ethernet.cloned-mac-address' in section
> [device-mac-addr-change-wifi] of file
> '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3247]
> bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
> Apr 13 09:31:06 persil systemd[1]: Started Network Manager.
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3315]
> manager[0x55a06db30040]: monitoring kernel firmware directory '/lib/firmware'.
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3319]
> monitoring ifupdown state file '/run/network/ifstate'.
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3354]
> hostname: hostname: using hostnamed
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3355]
> hostname: hostname changed from (none) to "persil"
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3359]
> dns-mgr[0x55a06db06240]: init: dns=default,systemd-resolved
> rc-manager=resolvconf
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3369]
> rfkill0: found Wi-Fi radio killswitch (at
> /sys/devices/pci:00/:00:1c.1/:03:00.0/ieee80211/phy0/rfkill0)
> (driver iwlwifi)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3396]
> manager[0x55a06db30040]: rfkill: Wi-Fi hardware radio set enabled
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3401]
> manager[0x55a06db30040]: rfkill: WWAN hardware radio set enabled
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3421]
> Loaded device plugin: NMWifiFactory
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-wifi.so)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3452]
> Loaded device plugin: NMBluezManager
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-bluetooth.so)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3470]
> Loaded device plugin: NMTeamFactory
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-team.so)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3483]
> Loaded device plugin: NMAtmManager
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-adsl.so)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3489]
> Loaded device plugin: NMWwanFactory
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-wwan.so)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3494]
> manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3497]
> manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3513]
> manager: Networking is enabled by state file
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3528]
> dhcp-init: Using DHCP client 'internal'
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3613]
> settings: Loaded settings plugin: ifupdown
> ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-settings-plugin-ifupdown.so")
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3618]
> settings: Loaded settings plugin: keyfile (internal)
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3621]
> ifupdown: management mode: unmanaged
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3624]
> ifupdown: interface-parser: parsing file /etc/network/interfaces
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3624]
> ifupdown: interface-parser: source line includes interfaces file(s)
> /etc/network/interfaces.d/*
> Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3625]
> ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
> Apr 13 09:31:06 persil
Bug#956495: htpdate install fails without directory /opt
Hi Joachim Trinkwitz, I tested it on my Debian (stable) and it really has a problem, but this bug was solved in testing. I will propose an s-p-u (stable-proposed-updates) and as soon as it is accepted you will be informed by the BTS. For now, if you wish, you can install htpdate from backports (apt install -t buster-backports htpdate). Thanks for reporting this Bug. Regards > Package: htpdate > Version: 1.2.0-3 > Severity: important > > Installation of htpdate fails on systems without directory /opt, because > of the directive 'InaccessibleDirectories=/boot /home /media /mnt /root > /opt /srv' in the systemd service file. The post-installation script > fails with the messages > htpdate.service: Failed to set up mount namespacing: No such file or directory > htpdate.service: Failed at step NAMESPACE spawning /usr/sbin/htpdate: No such > file or directory > > Obviously, a workaround is to create the directory /opt. -- ... ⢀⣴⠾⠻⢶⣦⠀ Thiago Andrade Marques ⣾⠁⢰⠒⠀⣿⡁ GPG: 4096R/F8CDB08B ⢿⡄⠘⠷⠚⠋⠀ GPG Fingerprint: 1D38 EE3C 624F 955C E1FA 3C85 5A30 3591 F8CD B08B ⠈⠳⣄
Bug#954628: pycallgraph: diff for NMU version 1.1.3-1.2
Control: tags 954628 + patch
Control: tags 954628 + pending
Dear maintainer,
I've prepared an NMU for pycallgraph (versioned as 1.1.3-1.2) and
uploaded it to DELAYED/6. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru pycallgraph-1.1.3/debian/changelog pycallgraph-1.1.3/debian/changelog
--- pycallgraph-1.1.3/debian/changelog 2020-03-12 13:18:59.0 +0200
+++ pycallgraph-1.1.3/debian/changelog 2020-04-13 22:59:48.0 +0300
@@ -1,3 +1,10 @@
+pycallgraph (1.1.3-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix the build with Python 3.8. (Closes: #954628)
+
+ -- Adrian Bunk Mon, 13 Apr 2020 22:59:48 +0300
+
pycallgraph (1.1.3-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru pycallgraph-1.1.3/debian/rules pycallgraph-1.1.3/debian/rules
--- pycallgraph-1.1.3/debian/rules 2020-03-12 13:18:59.0 +0200
+++ pycallgraph-1.1.3/debian/rules 2020-04-13 22:59:48.0 +0300
@@ -1,6 +1,6 @@
#!/usr/bin/make -f
-PYTHON3=$(shell py3versions -vr)
+PYTHON3=$(shell py3versions -d)
%:
dh $@ --with python3 --buildsystem=pybuild
@@ -9,8 +9,8 @@
dh_auto_install
# rename the module
- mv debian/python3-pycallgraph/usr/lib/python3.7/dist-packages/pycallgraph2 debian/python3-pycallgraph/usr/lib/python3.7/dist-packages/pycallgraph
- mv debian/python3-pycallgraph/usr/lib/python3.7/dist-packages/pycallgraph2-1.1.3.egg-info debian/python3-pycallgraph/usr/lib/python3.7/dist-packages/pycallgraph-1.1.3.egg-info
+ mv debian/python3-pycallgraph/usr/lib/${PYTHON3}/dist-packages/pycallgraph2 debian/python3-pycallgraph/usr/lib/${PYTHON3}/dist-packages/pycallgraph
+ mv debian/python3-pycallgraph/usr/lib/${PYTHON3}/dist-packages/pycallgraph2-1.1.3.egg-info debian/python3-pycallgraph/usr/lib/${PYTHON3}/dist-packages/pycallgraph-1.1.3.egg-info
# and make sure every module/script imports get renamed too
find debian/python3-pycallgraph/usr/ -type f -exec sed -i 's/pycallgraph2/pycallgraph/g' {} \;
Bug#956639: Fails to start
Package: network-manager
Version: 1.23.90-1
Severity: important
Hi,
NetworkManager fails to start after the last update (reinstalling
gir1.2-nm-1.0, libnm0, and network-manager from testing allowed me to
use the WiFi again, I didn’t try to use wired network).
Here is hopefully the relevant part of the syslog. I use a ThinkPad
X220, please tell me if you need other information.
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3198]
NetworkManager (version 1.23.90) is starting... (after a restart)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3200] Read
config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3200]
config: unknown key 'wifi.cloned-mac-address' in section
[device-mac-addr-change-wifi] of file
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3200]
config: unknown key 'ethernet.cloned-mac-address' in section
[device-mac-addr-change-wifi] of file
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3247]
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Apr 13 09:31:06 persil systemd[1]: Started Network Manager.
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3315]
manager[0x55a06db30040]: monitoring kernel firmware directory '/lib/firmware'.
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3319]
monitoring ifupdown state file '/run/network/ifstate'.
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3354]
hostname: hostname: using hostnamed
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3355]
hostname: hostname changed from (none) to "persil"
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3359]
dns-mgr[0x55a06db06240]: init: dns=default,systemd-resolved
rc-manager=resolvconf
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3369]
rfkill0: found Wi-Fi radio killswitch (at
/sys/devices/pci:00/:00:1c.1/:03:00.0/ieee80211/phy0/rfkill0)
(driver iwlwifi)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3396]
manager[0x55a06db30040]: rfkill: Wi-Fi hardware radio set enabled
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3401]
manager[0x55a06db30040]: rfkill: WWAN hardware radio set enabled
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3421]
Loaded device plugin: NMWifiFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-wifi.so)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3452]
Loaded device plugin: NMBluezManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-bluetooth.so)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3470]
Loaded device plugin: NMTeamFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-team.so)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3483]
Loaded device plugin: NMAtmManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-adsl.so)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3489]
Loaded device plugin: NMWwanFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-device-plugin-wwan.so)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3494]
manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3497]
manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3513]
manager: Networking is enabled by state file
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3528]
dhcp-init: Using DHCP client 'internal'
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3613]
settings: Loaded settings plugin: ifupdown
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.23.90/libnm-settings-plugin-ifupdown.so")
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3618]
settings: Loaded settings plugin: keyfile (internal)
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3621]
ifupdown: management mode: unmanaged
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3624]
ifupdown: interface-parser: parsing file /etc/network/interfaces
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3624]
ifupdown: interface-parser: source line includes interfaces file(s)
/etc/network/interfaces.d/*
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3625]
ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.3625]
ifupdown: interface-parser: finished parsing file /etc/network/interfaces
Apr 13 09:31:06 persil NetworkManager[1598787]: [1586806266.4129]
keyfile:
Bug#956637: trash-cli: fail to find trashed file outside home directory
Package: trash-cli
Version: 0.17.1.14-3
Severity: important
Dear Maintainer,
after upgrading package 0.17.1.14-2 -> 0.17.1.14-3, it fail to find trashed
file outside home directory.
Es:
user@pc:/media/disk$ touch test
user@pc:/media/disk$ trash-put test
user@pc:/media/disk$ trash-restore
No files trashed from current dir ('/media/disk')
and trash-list only show file trashed from home directory.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages trash-cli depends on:
ii python33.8.2-2
ii python3-pkg-resources 44.0.0-1
trash-cli recommends no packages.
trash-cli suggests no packages.
-- no debconf information
Bug#955775: ipython3 and entry_points
Hi, I think your report strange : using #!/usr/bin/env python as a shebang shouldn't really solve the issue : it points to Python 2 ! The Fedora script is interesting : I should have a look. Thanks! JP
Bug#956638: file-roller: CVE-2020-11736: do not follow external links when extracting files
Source: file-roller Version: 3.36.1-1 Severity: important Tags: security upstream fixed-upstream Hi, The following vulnerability was published for file-roller. CVE-2020-11736[0]: | fr-archive-libarchive.c in GNOME file-roller through 3.36.1 allows | Directory Traversal during extraction because it lacks a check of | whether a file's parent is a symlink to a directory outside of the | intended extraction location. 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-11736 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11736 [1] https://gitlab.gnome.org/GNOME/file-roller/-/commit/21dfcdbfe258984db89fb65243a1a888924e45a0 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#948789: [racket-dev] build failures for 7.5 on debian armhf
On Fri, Jan 17, 2020 at 06:52:11AM -0700, Matthew Flatt wrote:
> At Fri, 17 Jan 2020 09:43:15 -0400, David Bremner wrote:
> > Matthew Flatt writes:
> > > At Fri, 17 Jan 2020 08:31:22 -0400, David Bremner wrote:
> > >> => 0xb6ea3254 <+8>: stmdb sp!, {r4, r5, r6, r7, r8, r9, r10, r11,
> > >> lr}
> > >>0xb6ea3258 <+12>:add r3, pc
> > >
> > > That certainly looks like a valid ARM instruction. Maybe the processor
> > > is expecting Thumb instructions. What does `print $cpsr` report?
> >
> > (gdb) print $cpsr
> > $3 = 196656
>
> Since bit 5 is set, I think that means the processor was expecting
> Thumb instructions, which at least explains the error.
>
> To confirm that it's some bad jump or mismanagement of the mode by the
> Racket JIT, does changing "racket/src/lightning/arm/asm.h" to disable
> Thumb support allow the build to work?
I debugged this a bit, and reverting [1] makes 7.5 build.
The assembler code was taken from an ancient version of gmp,
and after a rewrite in 2009 (sic) the code in current gmp is
completely different.
Is there a reason why you cannot change to using an external
libgmp instead of local copies of gmp code?
cu
Adrian
[1]
https://github.com/racket/racket/commit/17bc6262938f3b29e7ec66d0e77eeb08807854cd
Bug#956579: Don't build-depend on udev and pass udevrulesdir to the at configure time instead
On Mon, Apr 13, 2020 at 11:15 AM Laurent Bigonville wrote: > ATM fuse3 package is not being build on kfreebsd-* as it build-depends > on udev. > > AFAICS, udev is only needed to detect the rules.d directory location, > this can be passed at build time instead using -Dudevrulesdir Might making that build dependency [linux-any] be better? That would keep the auto-detection intact on Linux. Of course, I don't expect the udev rules dir to change. Would fuse work correctly on kFreeBSD anyway? Does kFreeBSD has a fuse kernel module as well? I miss proper support of kFreeBSD in general. Seems neglected enough. :( > Please find a patch here that fixes this. Thanks, appreciated. Cheers, Laszlo/GCS
Bug#956597: temperature busted
Everything is working as it should. I think you want tempF(68) and tempC to get the result you expect. The notation degF means a temperature difference. See the manual for details. On Mon, Apr 13, 2020 at 07:49:51PM +0800, 積丹尼 Dan Jacobson wrote: > X-debbugs-Cc: adri...@gnu.org > Package: units > Version: 2.19-1 > > $ units 68degF degC > * 37.78 > / 0.026470588 > > Should be around 20. > > $ units degC > Definition: K = 1 K > > $ units degC degK > * 1 > / 1 > > What?!
Bug#956635: update libunistring symbols for non-glibc
Source: libunistring Version: 0.9.10-2 Tags: ftbfs patch User: helm...@debian.org Usertags: rebootstrap When building libunistring for musl-linux-any, I run into symbol issues. There are two notable issues: * libunistring_fseterr is missing. Since musl provides this function, gnulib does not supply a replacement and it goes missing. * libunistring_glthread_rwlock_init_for_glibc is missing. It is a glibc-specific symbol. Please consider applying the attached patch to mark these symbols as glibc-specific. Helmut diff --minimal -Nru libunistring-0.9.10/debian/changelog libunistring-0.9.10/debian/changelog --- libunistring-0.9.10/debian/changelog2019-07-11 19:15:05.0 +0200 +++ libunistring-0.9.10/debian/changelog2020-04-09 21:24:53.0 +0200 @@ -1,3 +1,10 @@ +libunistring (0.9.10-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update symbols for non-glibc. (Closes: #-1) + + -- Helmut Grohne Thu, 09 Apr 2020 21:24:53 +0200 + libunistring (0.9.10-2) unstable; urgency=medium * New patch debian/patches/0705-gcc-9.patch: diff --minimal -Nru libunistring-0.9.10/debian/libunistring2.symbols libunistring-0.9.10/debian/libunistring2.symbols --- libunistring-0.9.10/debian/libunistring2.symbols2018-07-08 23:15:23.0 +0200 +++ libunistring-0.9.10/debian/libunistring2.symbols2020-04-09 21:24:42.0 +0200 @@ -144,7 +144,7 @@ libunistring_c_tolower@Base 0.9.7 libunistring_c_toupper@Base 0.9.7 libunistring_freea@Base 0.9.7 - libunistring_fseterr@Base 0.9.7 +(arch=gnu-any-any)libunistring_fseterr@Base 0.9.7 libunistring_gl_locale_name@Base 0.9.7 libunistring_gl_locale_name_default@Base 0.9.7 libunistring_gl_locale_name_environ@Base 0.9.7 @@ -158,7 +158,7 @@ libunistring_gl_uninorm_decompose_merge_sort_inplace@Base 0.9.7 libunistring_glthread_once_singlethreaded@Base 0.9.7 libunistring_glthread_recursive_lock_init_multithreaded@Base 0.9.7 - libunistring_glthread_rwlock_init_for_glibc@Base 0.9.8 +(arch=gnu-any-any)libunistring_glthread_rwlock_init_for_glibc@Base 0.9.8 libunistring_hard_locale@Base 0.9.7 libunistring_iconveh_close@Base 0.9.7 libunistring_iconveh_open@Base 0.9.7
Bug#956636: libnet-ssh2-perl FTCBFS: uses a compile+run test
Source: libnet-ssh2-perl
Version: 0.71-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
libnet-ssh2-perl fails to cross build from source, because Makefile.PL
uses a compile + run test to detect the ssh2 library. Running an
executable is not necessary here and doing so breaks cross compilation.
Please consider using a link-only test, e.g. by applying the attached
patch.
Helmut
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -151,6 +151,7 @@ sub findlib {
for my $ldflags (@ldflags) {
if (eval {
assertlibs( %args,
+not_execute => 1,
libpath => $libpath,
incpath => $incpath,
ldflags => $ldflags);
Bug#956416: RFS: sipxtapi/3.3.0~test17-3.1 [NMU, RC] -- SIP stack, RTP media framework and codecs
Hi Tobi, On Mon, Apr 13, 2020 at 4:06 PM Tobias Frost wrote: > > Hi Sudip, > > As sipxtapi is de-facto unmaintained*, are you interested in adopting it? I usually don't like adopting package which I dont use, and I dont use this one. :( But I think it will be best to mark it as orphan and then I can update it and keep in a better shape than it is now :) otoh, if you want to remove it if there is no active maintainer then I guess I can take it up. -- Regards Sudip
Bug#956634: ITP: golang-github-pd0mz-go-maidenhead -- Maidenhead Locator system in Golang
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org Package: wnpp Severity: wishlist Owner: Taowa Munene-Tardif * Package name: golang-github-pd0mz-go-maidenhead Version : 0.0~git20170221.faa09c2-1 Upstream Author : pd0mz * URL : https://github.com/pd0mz/go-maidenhead * License : Expat Programming Lang: Go Description : Maidenhead Locator system in Golang Maidenhead Locator system in Golang For packaging pat (#877030) -- Taowa Munene-Tardif taowa.ca Montréal
Bug#956633: libpango-1.0-0: After upgrading from 1.42.4-8 to 1.44.7-3: Wrong font rendering in geany
Package: libpango-1.0-0 Version: 1.44.7-3 Severity: normal Dear Maintainer, After upgrading libpangocairo-1.0-0 and libpango-1.0-0 from 1.44.7-3 to 1.42.4-8, fonts are rendered wrong in geany. It seems the cahracters are too low, so for example underscores are invisible. I'll send some screenshots by mail. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpango-1.0-0 depends on: ii fontconfig 2.13.1-2+b1 ii libc6 2.30-4 ii libfribidi01.0.8-2 ii libglib2.0-0 2.64.1-1 ii libharfbuzz0b 2.6.4-1 ii libthai0 0.1.28-3 libpango-1.0-0 recommends no packages. libpango-1.0-0 suggests no packages. -- no debconf information
Bug#956632: ITP: python3-iniherit -- A ConfigParser subclass that allows inheritance.
Package: wnpp Severity: wishlist Owner: Henry-Nicolas Tourneur * Package name: python3-iniherit Version : 0.3.9 Upstream Author : Philip J Grabner, Cadit Health Inc * URL : https://pypi.org/project/iniherit/ * License : MIT Programming Lang: Python Description : A ConfigParser subclass that allows inheritance. Adds INI-file inheritance to ConfigParser. Note that although it effectively behaves very similarly to passing multiple files to ConfigParser’s read() method, that requires changing the code at that point. If that is not feasible, or the INI files should dictate inheritance themselves, then the iniherit package is a better alternative. Extra information on this packaging: - I wish to maintain this package together with DPMT - This library is a dependency for the authenticator gnome app which I would like to package as well once dependencies are resolved.
Bug#956135: Please close the current ticket : #956135
Hello, A new ticket is open for this problem : #956203 Please close the current ticket : #956135 Thank you Regards
Bug#956631: debconf-doc: error in debconf-devel(7) man page
Package: debconf-doc Version: 1.5.73 Severity: normal There appears to be an error in the debconf-devel(7) man page. In the 'ADVANCED PROGRAMMING WITH DEBCONF'/'Config file handling' section there's the following example: ... cp -a -f $CONFIGFILE $CONFIGFILE.tmp # If the admin deleted or commented some variables but then set # them via debconf, (re-)add them to the conffile. test -z "$FOO" || grep -Eq '^ *FOO=' $CONFIGFILE || \ echo "FOO=" >> $CONFIGFILE test -z "$BAR" || grep -Eq '^ *BAR=' $CONFIGFILE || \ echo "BAR=" >> $CONFIGFILE sed -e "s/^ *FOO=.*/FOO=\"$FOO\"/" \ -e "s/^ *BAR=.*/BAR=\"$BAR\"/" \ < $CONFIGFILE > $CONFIGFILE.tmp mv -f $CONFIGFILE.tmp $CONFIGFILE ... Note that in the second stanza it suggests writing to $CONFFILE, but then $CONFILE is overwritten by the last 'mv ...' line, so those changes will be overwritten. I think the tests just need to look at the temp file, not the main file, e.g.: ... cp -a -f $CONFIGFILE $CONFIGFILE.tmp # If the admin deleted or commented some variables but then set # them via debconf, (re-)add them to the conffile. test -z "$FOO" || grep -Eq '^ *FOO=' $CONFIGFILE.tmp || \ echo "FOO=" >> $CONFIGFILE.tmp test -z "$BAR" || grep -Eq '^ *BAR=' $CONFIGFILE.tmp || \ echo "BAR=" >> $CONFIGFILE.tmp sed -e "s/^ *FOO=.*/FOO=\"$FOO\"/" \ -e "s/^ *BAR=.*/BAR=\"$BAR\"/" \ < $CONFIGFILE > $CONFIGFILE.tmp mv -f $CONFIGFILE.tmp $CONFIGFILE ... Thanks. jamie. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (600, 'testing'), (500, 'stable'), (200, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled debconf-doc depends on no packages. debconf-doc recommends no packages. Versions of packages debconf-doc suggests: pn debian-policy -- no debconf information
Bug#956630: webcamoid: Please package the new version
Package: webcamoid Version: 8.6.1+dfsg-2.1 Severity: wishlist Tags: upstream Hello, There is a new version available: https://github.com/webcamoid/webcamoid/releases/tag/8.7.1 Please update. Thank you, Cord -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages webcamoid depends on: ii akqml 8.6.1+dfsg-2.1 ii libavkys8 8.6.1+dfsg-2.1 ii libc6 2.30-4 ii libgcc-s1 10-20200411-1 ii libqt5core5a5.12.5+dfsg-9 ii libqt5gui5 5.12.5+dfsg-9 ii libqt5network5 5.12.5+dfsg-9 ii libqt5qml5 5.12.5-5 ii libqt5quick55.12.5-5 ii libqt5widgets5 5.12.5+dfsg-9 ii libstdc++6 10-20200411-1 ii qml-module-qt-labs-folderlistmodel 5.12.5-5 ii qml-module-qt-labs-settings 5.12.5-5 ii qml-module-qtgraphicaleffects 5.12.5-2+b1 ii qml-module-qtqml-models25.12.5-5 ii qml-module-qtquick-controls 5.12.5-1+b1 ii qml-module-qtquick-controls25.12.5+dfsg-2+b1 ii qml-module-qtquick-dialogs 5.12.5-1+b1 ii qml-module-qtquick-extras 5.12.5-1+b1 ii qml-module-qtquick-privatewidgets 5.12.5-1+b1 ii qml-module-qtquick-templates2 5.12.5+dfsg-2+b1 ii webcamoid-data 8.6.1+dfsg-2.1 ii webcamoid-plugins 8.6.1+dfsg-2.1 webcamoid recommends no packages. webcamoid suggests no packages. -- no debconf information
Bug#951979: antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory
Package: antimony Version: 0.9.3-1+b1 Followup-For: Bug #951979 Dear Maintainer, Is it possible to update the package on the current Debian stable to fix this bug? Currently it won't start at all. For anyone who can't start antimony on the the current Debian stable (buster), this seems to make it work: $ ln -s /usr/lib/x86_64-linux-gnu/libboost_python37.so.1.67.0 /usr/lib/x86_64-linux-gnu/libboost_python36.so.1.67.0 Regards, LZY -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'testing') Architecture: amd64 (x86_64) Versions of packages antimony depends on: ii libboost-python1.67.0 1.67.0-13+deb10u1 ii libc6 2.28-10 ii libgcc11:8.3.0-6 ii libpng16-161.6.36-6 ii libpython3.7 3.7.3-2+deb10u1 ii libqt5concurrent5 5.11.3+dfsg1-1+deb10u3 ii libqt5core5a 5.11.3+dfsg1-1+deb10u3 ii libqt5gui5 5.11.3+dfsg1-1+deb10u3 ii libqt5network5 5.11.3+dfsg1-1+deb10u3 ii libqt5opengl5 5.11.3+dfsg1-1+deb10u3 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3 ii libstdc++6 8.3.0-6 ii python33.7.3-1 ii zlib1g 1:1.2.11.dfsg-1 antimony recommends no packages. antimony suggests no packages. -- no debconf information
Bug#956625: texlive-luatex fails to install: running `luatex -ini -jobname=optex -progname=optex optex.ini
Am 13.04.2020 um 20:08 teilte Dmitry Shachnev mit: Hi Dmitry, > The mentioned /tmp/fmtutil.zMbmF90b file is attached. > Relevant error message: Latin Modern fonts (EC) preloaded <2020-01-23> ! Font \_tenrm=ec-lmr10 not loadable: metric data not found or bad. \_font l.8 \_font \_tenbf=ec-lmbx10 % boldface extended ? ! Emergency stop. \_font l.8 \_font \_tenbf=ec-lmbx10 % boldface extended ! ==> Fatal error occurred, no output PDF file produced! Transcript written on optex.log. Does installing package lmodern solve your issue? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#956628: ITP: golang-github-microcosm-cc-bluemonday -- Go library for scrubbing user generated data of unapproved html
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org Package: wnpp Severity: wishlist Owner: Taowa Munene-Tardif * Package name: golang-github-microcosm-cc-bluemonday Version : 1.0.2 Upstream Author : Microcosm * URL : https://github.com/microcosm-cc/bluemonday * License : BSD-3-clause Programming Lang: Go Description : Go library for scrubbing user generated data of unapproved html Bluemonday takes untrusted user generated content as an input and returns HTML that has been sanitised against a whitelist of approved HTML elements and attributes. This can help prevent XSS attacks. Dependency of pat (#877030). -- Taowa Munene-Tardif taowa.ca Montréal
Bug#956629: src:sleef: fails to migrate to testing for too long: FTBFS on multiple archs
Source: sleef Version: 3.3.1-6 Severity: serious Control: close -1 3.4.1-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:sleef in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=sleef signature.asc Description: OpenPGP digital signature
Bug#899138: libopusfile-dev: move opusfile.pc to a multiarch location
Please consider applying the patch submitted by Helmut Grohne if there is nothing wrong with it, as it is a blocker for issue #935590, and this one is in turn preventing the co-installation of i386 and amd64 builds of libsdl2-mixer-2.0-0. If for some reason the provided patch can not be used in its current state, I would be happy to help in any way I can to work towards an acceptable patch. signature.asc Description: OpenPGP digital signature
Bug#956627: e4crypt: set_policy and add_key can both fail but return exit code 0
Package: e2fsprogs Version: 1.45.6-1 When e4crypt fails, it should return a non-zero exit code. here is add_key succeeding and then failing. note that $? is the first element in the prompt. This shows that the return code remains 0 even though "add_key" fails to add a new key. 0 dkg@alice:~$ /usr/sbin/e4crypt add_key Enter passphrase (echo disabled): Added key with descriptor [214ee2a37ebdd0bf] 0 dkg@alice:~$ /usr/sbin/e4crypt add_key Enter passphrase (echo disabled): Key with descriptor [214ee2a37ebdd0bf] already exists 0 dkg@alice:~$ Here is set_policy failing but still returning 0: 0 dkg@alice:~$ /usr/sbin/e4crypt set_policy 214ee2a37ebdd0bf foobar Error [File exists] setting policy. The key descriptor [214ee2a37ebdd0bf] may not match the existing encryption context for directory [foobar]. 0 dkg@alice:~$ Regards, --dkg signature.asc Description: PGP signature
Bug#956626: dhcpcanon systemd unit fails at boot due to missing debhelper apparmor integration
Package: dhcpcanon
Severity: normal
X-Debbugs-CC: whonix-de...@whonix.org
Debian buster dhcpcanon_0.8.5-2_all.deb debian/postinst lacks apparmor
integration which should be auto added by debhelper.
sudo aa-enforce /etc/apparmor.d/sbin.dhcpcanon
ERROR: Include file /etc/apparmor.d/local/sbin.dhcpcanon not found
Workaround:
sudo touch /etc/apparmor.d/local/sbin.dhcpcanon
For example /var/lib/dpkg/info/man-db.postinst has:
```
# Automatically added by dh_apparmor/2.13.2-7
if [ "$1" = "configure" ]; then
APP_PROFILE="/etc/apparmor.d/usr.bin.man"
if [ -f "$APP_PROFILE" ]; then
# Add the local/ include
LOCAL_APP_PROFILE="/etc/apparmor.d/local/usr.bin.man"
test -e "$LOCAL_APP_PROFILE" || {
mkdir -p `dirname "$LOCAL_APP_PROFILE"`
install --mode 644 /dev/null "$LOCAL_APP_PROFILE"
}
# Reload the profile, including any abstraction updates
if aa-enabled --quiet 2>/dev/null; then
apparmor_parser -r -T -W "$APP_PROFILE" || true
fi
fi
fi
# End automatically added section
```
Bug#944913: [Python-modules-team] Bug#944913: Bug#944913: Bug#944913: python3-sphinx: Please update to Sphinx 2.2.1
Hi Sandro! On Sun, Apr 12, 2020 at 02:43:49PM -0400, Sandro Tosi wrote: > > Ok, I will upload it tomorrow. > > Thanks! let me know if you need help with anything Unfortunately, today sphinx dependencies are uninstallable because of #956625. So if I upload sphinx now it will most probably FTBFS. I will wait until that bug is fixed. Maybe the current sphinx (1.8.5-9) migrates in the mean time. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
On Mon, 13 Apr 2020, Sebastian Ramacher wrote: This is caused by the ongoing effort to remove Python 3.7. casacore needs to be rebuilt against the new libboost-python1.67.0 version. But this build fails with: | -- Looking for python3 specific environment... | -- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7") | -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8.2") | -- Found Boost: /usr/include (found version "1.67.0") In the source dir, find python3/CMakeLists-older-cmake.txt, in there you'll find: # Detect the python properties set(Python_ADDITIONAL_VERSIONS 3.7 3.6 3.5 3.4) add 3.8 before 3.7, so that it now reads: # Detect the python properties set(Python_ADDITIONAL_VERSIONS 3.8 3.7 3.6 3.5 3.4) then, when I run fakeroot debian/rules build it detects and tries to use python3.8. Please, see if this is enough to get the package to compile correctly with the new boost libraries. Thanks again, bye Giacomo -- _ Giacomo Mulas _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180255 mob. : +39 329 6603810 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _
Bug#956625: texlive-luatex fails to install: running `luatex -ini -jobname=optex -progname=optex optex.ini
Package: texlive-luatex Version: 2020.20200329-2 Severity: grave Justification: fails to install on a clean system Dear Maintainer, When trying to run “apt install texlive-luatex” on a clean sid chroot, I get this error: Setting up texlive-luatex (2020.20200329-2) ... Processing triggers for libc-bin (2.30-4) ... Processing triggers for tex-common (6.13) ... Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... fmtutil failed. Output has been stored in /tmp/fmtutil.zMbmF90b Please include this file if you report a bug. dpkg: error processing package tex-common (--configure): installed tex-common package post-installation script subprocess returned error exit status 1 The mentioned /tmp/fmtutil.zMbmF90b file is attached. -- Dmitry Shachnev fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /usr/share/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: writing formats under /var/lib/texmf/web2c fmtutil [INFO]: --- remaking luahbtex with luahbtex fmtutil: running `luahbtex -ini -jobname=luahbtex -progname=luahbtex luatex.ini' ... This is LuaHBTeX, Version 1.12.0 (TeX Live 2020/Debian) (INITEX) restricted system commands enabled. (/usr/share/texlive/texmf-dist/tex/generic/tex-ini-files/luatex.ini (/usr/share/texlive/texmf-dist/tex/generic/tex-ini-files/luatexconfig.tex (/var/lib/texmf/tex/generic/config/pdftexconfig.tex)) (/usr/share/texlive/texmf-dist/tex/generic/config/luatexiniconfig.tex) (/usr/share/texlive/texmf-dist/tex/generic/unicode-data/load-unicode-data.tex load-unicode-data.tex v1.12 (2020-03-12) Reading Unicode data # UnicodeData-13.0.0.txt # Modified 2020-03-12 11:00:00 GMT [JAW] ) (/usr/share/texlive/texmf-dist/tex/luatex/hyph-utf8/etex.src (/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex Preloading the plain format: codes, registers, parameters, fonts, more fonts, macros, math definitions, output routines, hyphenation (/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex [skipping from \patterns to end-of-file...])) (/usr/share/texlive/texmf-dist/tex/plain/etex/etexdefs.lib Skipping module "grouptypes"; Loading module "interactionmodes"; Skipping module "nodetypes"; Skipping module "iftypes";) (/usr/share/texlive/texmf-dist/tex/generic/config/language.def (/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex)) Augmenting the Plain TeX definitions: \tracingall; Adding new e-TeX definitions: \eTeX, \loggingall, \tracingnone, register allocation; extended register allocation; Recycling: \addlanguage, \@nswer (not defined), \@sk, \b@dresponsetrue, \b@dresponsefalse, \ch@ckforyn, \mayber@cycle, \et@xabort, \et@xbuf, \et@xfmtsrc, \et@xfilehdr, \et@xinf, \et@xpatterns, \l@ngdefnfile, \n@xt, \p@rse (not defined), \pr@mpt (not defined), \pr@mptloop (not defined), \forcer@cycle, \usef@llback, \usef@llbacktrue, \usef@llbackfalse, Retaining: \et@xerr, \et@xinput, \et@xlibhdr, \et@xmsg, \et@xtoks, \et@xwarn, \et@xl@@d, \et@xl@ad, \et@xload, \et@xlang, \et@xhash, \eTeX, \etexhdrchk, \etexstatus, \module, \uselanguage, \r@tain, \r@cycle,)) Beginning to dump on file luahbtex.fmt (format=luahbtex 2020.4.13) 3354 strings using 10263 bytes 68807 memory locations dumped; current usage is 149&7700 1869 multiletter control sequences \font\nullfont=nullfont \font\tenrm=cmr10 \font\preloaded=cmr9 \font\preloaded=cmr8 \font\sevenrm=cmr7 \font\preloaded=cmr6 \font\fiverm=cmr5 \font\teni=cmmi10 \font\preloaded=cmmi9 \font\preloaded=cmmi8 \font\seveni=cmmi7 \font\preloaded=cmmi6 \font\fivei=cmmi5 \font\tensy=cmsy10 \font\preloaded=cmsy9 \font\preloaded=cmsy8 \font\sevensy=cmsy7 \font\preloaded=cmsy6 \font\fivesy=cmsy5 \font\tenex=cmex10 \font\preloaded=cmss10 \font\preloaded=cmssq8 \font\preloaded=cmssi10 \font\preloaded=cmssqi8 \font\tenbf=cmbx10 \font\preloaded=cmbx9 \font\preloaded=cmbx8 \font\sevenbf=cmbx7 \font\preloaded=cmbx6 \font\fivebf=cmbx5 \font\tentt=cmtt10 \font\preloaded=cmtt9 \font\preloaded=cmtt8 \font\preloaded=cmsltt10 \font\tensl=cmsl10 \font\preloaded=cmsl9 \font\preloaded=cmsl8 \font\tenit=cmti10 \font\preloaded=cmti9 \font\preloaded=cmti8 \font\preloaded=cmti7 \font\preloaded=cmu10 \font\preloaded=cmmib10 \font\preloaded=cmbsy10 \font\preloaded=cmcsc10 \font\preloaded=cmssbx10 \font\preloaded=cmdunh10 \font\preloaded=cmr7 at 14.51799pt \font\preloaded=cmtt10 at 14.4pt \font\preloaded=cmssbx10 at 14.4pt \font\preloaded=manfnt 50 preloaded fonts warning (pdf backend): no pages of output. Transcript written on luahbtex.log. fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/luahbtex/luahbtex.log fmtutil [INFO]: /var/lib/texmf/web2c/luahbtex/luahbtex.fmt installed. fmtutil [INFO]: --- remaking luatex with luatex fmtutil: running `luatex
Bug#939545: Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 4.19.0-5-amd64 (LTS)
Problem is solved with Powertop v.2.11 from testing and Kernel 5.4 from backports. Thank you very much for your work. The ticket can be considered as resolved. Powertop v.2.11 should be in backport, it works very fine !!! Regards. Philippe
Bug#956624: qemu: FTBFS on sparc64 due to libseccomp-dev dependency
Source: qemu Severity: normal User: debian-sp...@lists.debian.org Usertags: sparc64 Hello, Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any. Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was building successfully before: https://buildd.debian.org/status/logs.php?pkg=qemu=sparc64 Instead of enabling seccomp on linux-any, maybe it could be enabled on something like this: [!alpha !ia64 !m68k !sh4 !sparc64 !hurd-any !kfreebsd-any] Thanks, Tom
Bug#945245: Powertop v.2.8-1 + b2 => Update to Powertop v. 2.11 from testing
Hello Kanru, I saw your message a little late... I just made a clean installation and add the testing repertory. Unfortunately the result is the same, the hiss is still present in my headphones ;( But the installation is very stable for my. This is a perfect candidate to add it on backports repertory. After this, if I add the backports repertory and install the Kernel v. 5.4.0-0.bpo.4-amd64 after reboot => all is ok Powertop v. 2.11 with Kernel v. 5.4.0-0.bpo.4-amd64 solve the problem :) Now I have a new problem : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956203 If you have a Idea for solve this, I will be very grateful to you. Regards. Philippe
Bug#954268: enigmail: autopkgtest times out after 2h47 or 5h35 if keyserver can't be reached
Control: forwared 954268 https://admin.hostpoint.ch/pipermail/enigmail-users_enigmail.net/2020-April/005595.html On Thu 2020-03-19 14:57:57 +0100, Paul Gevers wrote: > The worker fleet of ci.d.n doesn't have the reliable network we would > wish for, but your package fails in an unpleasant way if a keyserver > can't be reached. Can you please detect the issue and fail more > gracefully, such that the test doesn't need to be killed by autopkgtest > after 2:47 hours idle time because of the autopkgtest timeout? > > Paul > > https://ci.debian.net/packages/e/enigmail/testing/arm64/ > > https://ci.debian.net/data/autopkgtest/testing/arm64/e/enigmail/4384388/log.gz > > 2020-02-26 17:05:54.370 [DEBUG] enigmailCommon.jsm: dispatchEvent f=resizeDlg > 2020-02-26 18:05:54.188 [DEBUG] keyRefreshService.jsm: Either no keyservers > exist or the protocols specified are invalid. Will recheck in an hour. > 2020-02-26 19:05:54.190 [DEBUG] keyRefreshService.jsm: Either no keyservers > exist or the protocols specified are invalid. Will recheck in an hour. Thanks for this report! I'm not sure how to fix this properly, since this is part of the upstream test suite :/ I've mentioned it to upstream to see whether they have any suggestions for how to deal with this more gracefully. --dkg signature.asc Description: PGP signature
Bug#956585: openjfx: FTBFS on all making openjfx uninstallable
Le 13/04/2020 à 19:34, Sebastiaan Couwenberg a écrit : > It looks like the changes in openjfx (11.0.7+0-2) won't be enough to fix > the FTBFS on mips* as well. I've noticed a segfault in the build log on mips64el. I have no idea how to address this, this sounds like a compiler bug. > Will openjfx & zeroc-ice be removed from those architectures to allow it > to migrate to testing if that's the case? I'll request the mips binaries to be removed if it still doesn't work. Emmanuel Bourg
Bug#956623: RM: ibniz -- RoQA; Depends on Python 2, dead upstream, unmaintained
Package: ftp.debian.org Severity: normal Please remove ibniz. It depends on Python 2, is dead upstream (last commit eight years ago) and the last (and only) upload was in 2013. Cheers, Moritz
Bug#956621: loganalyzer: New upstream version 4.1.10 available.
Package: src:loganalyzer Severity: wishlist Please package the new versions, Debian is almost 3 years behind upstream. -- tobi
Bug#956622: RM: drobo-utils -- RoQA; Depends on Python 2, dead upstream
Package: ftp.debian.org Severity: normal Please remove drobo-utils. It depends on Python 2 and https://github.com/petersilva/drobo-utils states: | Is it Still Supported ? | Not really. I no longer have any hardware to test with, so cannot | validate anything. I switched to QNAP instead, which was more | appropriate for my needs. The package is python2 and will never | be ported to python3 Cheers, Moritz
Bug#956585: openjfx: FTBFS on all making openjfx uninstallable
On 4/13/20 12:19 PM, Bas Couwenberg wrote: > The recent update to 11.0.7+0-1 fails to build and several architectures, > most importantly on all making the openjfx package uninstallable, and in > turn preventing the josm build in unstable: It looks like the changes in openjfx (11.0.7+0-2) won't be enough to fix the FTBFS on mips* as well. Will openjfx & zeroc-ice be removed from those architectures to allow it to migrate to testing if that's the case? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#956620: node-util: New upstream version 0.12.2 available.
Package: src:node-util Severity: wishlist Please package the new upstream version. Thanks!
Bug#956617: node-typedarray-to-buffer: New upstream version 3.1.5 available.
Package: src:node-typedarray-to-buffer Severity: wishlist Dear Maintainer, Please package version 3.1.5. Thanks!
Bug#956619: RFS: xtrx-dkms/0.0.1+git20190320.5ae3a3e-1 [ITP] -- XTRX PCI driver for linux
Package: sponsorship-requests Severity: wishlist Dear mentors, HAM Radio Team, I am looking for a sponsor for my package "xtrx-dkms" * Package name: xtrx-dkms Version : 0.0.1+git20190320.5ae3a3e-1 Upstream Author : Sergey Kostanbaev * URL : https://github.com/xtrx-sdr/xtrx_linux_pcie_drv * License : GPL-2.0+ * Vcs : https://salsa.debian.org/debian-hamradio-team/xtrx-dkms Section : kernel It builds those binary packages: xtrx-dkms - XTRX PCI driver for linux To access further information about this package, please visit the following URL: https://mentors.debian.net/package/xtrx-dkms Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/x/xtrx-dkms/xtrx-dkms_0.0.1+git20190320.5ae3a3e-1.dsc Changes since the last upload: * Initial release (Closes: #945156) Regards, -- Sepi Gair
Bug#956618: RM: diff-match-patch -- RoQA; unmaintained, lacking years behind upstream, no reverse dependencies
Package: ftp.debian.org Severity: normal As the title says, its probably better to RM it from Debian. -- tobi (spring cleaning)
