Bug#956946: sprai FTCBFS: does not pass cross tools to make
Source: sprai Version: 0.9.9.23+dfsg1-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs sprai fails to cross build from source, because it does not pass cross tools to make. dh thinks that this is an autoconf project, so dh_auto_build doesn't do it for you, but configure is something entirely different and therefore skipped by debian/rules. A better solution is to tell dh what kind of buildsystem it is dealing with and doing so makes sprai cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru sprai-0.9.9.23+dfsg1/debian/changelog sprai-0.9.9.23+dfsg1/debian/changelog --- sprai-0.9.9.23+dfsg1/debian/changelog 2020-04-15 17:01:52.0 +0200 +++ sprai-0.9.9.23+dfsg1/debian/changelog 2020-04-17 07:11:31.0 +0200 @@ -1,3 +1,10 @@ +sprai (0.9.9.23+dfsg1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: use the makefile buildsystem. (Closes: #-1) + + -- Helmut Grohne Fri, 17 Apr 2020 07:11:31 +0200 + sprai (0.9.9.23+dfsg1-1) unstable; urgency=medium [ Adrian Bunk ] diff --minimal -Nru sprai-0.9.9.23+dfsg1/debian/rules sprai-0.9.9.23+dfsg1/debian/rules --- sprai-0.9.9.23+dfsg1/debian/rules 2020-04-15 17:01:52.0 +0200 +++ sprai-0.9.9.23+dfsg1/debian/rules 2020-04-17 07:11:29.0 +0200 @@ -4,10 +4,7 @@ include /usr/share/dpkg/buildflags.mk %: - dh $@ - -override_dh_auto_configure: - echo Skip + dh $@ --buildsystem=makefile override_dh_install: mkdir -p $(CURDIR)/debian/sprai/usr/lib/sprai
Bug#956945: trinculo FTCBFS: uses the build architecture compiler
Source: trinculo Version: 0.96+dfsg-2 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs trinculo fails to cross build from source, because it uses the build architecture compiler as a make default. The simplest way of fixing that - using dpkg's buildtools.mk - makes trinculo cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru trinculo-0.96+dfsg/debian/changelog trinculo-0.96+dfsg/debian/changelog --- trinculo-0.96+dfsg/debian/changelog 2020-04-10 07:43:12.0 +0200 +++ trinculo-0.96+dfsg/debian/changelog 2020-04-17 07:15:24.0 +0200 @@ -1,3 +1,10 @@ +trinculo (0.96+dfsg-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dpkg's buildtools.mk set up CXX. (Closes: #-1) + + -- Helmut Grohne Fri, 17 Apr 2020 07:15:24 +0200 + trinculo (0.96+dfsg-2) unstable; urgency=medium * Rules-Requires-Root: no (routine-update) diff --minimal -Nru trinculo-0.96+dfsg/debian/rules trinculo-0.96+dfsg/debian/rules --- trinculo-0.96+dfsg/debian/rules 2020-04-10 07:43:12.0 +0200 +++ trinculo-0.96+dfsg/debian/rules 2020-04-17 07:15:22.0 +0200 @@ -2,6 +2,8 @@ # DH_VERBOSE := 1 +-include /usr/share/dpkg/buildtools.mk + # for hardening you might like to uncomment this: export DEB_BUILD_MAINT_OPTIONS=hardening=+all
Bug#956944: pd-creb FTCBFS: uses the build architecture compiler
Source: pd-creb Version: 0.9.2+darcs20151027-3 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs pd-creb fails to cross build from source, because it uses the build architecture compiler as a make default. A typical autotools project should be using the compiler detected by configure instead. In case of C++, the configure script doesn't even attempt to detect it. The attached patch fixes all of that. Please consider applying it. Helmut --- pd-creb-0.9.2+darcs20151027.orig/Makefile.config.in +++ pd-creb-0.9.2+darcs20151027/Makefile.config.in @@ -1,3 +1,5 @@ +CC = @CC@ +CXX = @CXX@ PD_INCLUDE_DIR = @PD_INCLUDE_DIR@ LIBNAME = @LIBNAME@ LIBFLAGS = @LIBFLAGS@ $(EXTRA_LDFLAGS) --- pd-creb-0.9.2+darcs20151027.orig/configure.ac +++ pd-creb-0.9.2+darcs20151027/configure.ac @@ -1,5 +1,6 @@ AC_INIT(modules/setup.c) AC_PROG_CC +AC_PROG_CXX AC_HEADER_STDC
Bug#956943: Subject: fzf: binary package contains golang source code
Package: fzf Version: 0.20.0-1 Severity: normal Dear Maintainer, * What led up to the situation? Inspecting contents of the package * What was the outcome of this action? Sources of fzf application were found in a binary package * What outcome did you expect instead? Sources should not be present in a binary package -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/6 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) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#956942: parcimonie reports a Gdk-Critical bit in my .xsession-errors file
Package: parcimonie Version: 0.11.0-2 Severity: normal Dear Maintainer, Got the following in my .xsession-errors - (parcimonie-applet:9438): Gdk-CRITICAL **: 07:46:21.767: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed Please fix the same. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-debug'), (100, 'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages parcimonie depends on: ii dirmngr 2.2.20-1 ii gnupg 2.2.20-1 ii libclone-perl 0.43-2 ii libconfig-general-perl 2.63-1 ii libfile-homedir-perl1.004-1 ii libfile-which-perl 1.23-1 ii libgnupg-interface-perl 0.52-11 ii libipc-system-simple-perl 1.30-1 ii liblist-moreutils-perl 0.416-1+b5 ii libmoo-perl 2.004000-1 ii libmoox-late-perl 0.016-1 ii libmoox-options-perl4.103-3 ii libmoox-strictconstructor-perl 0.011-1 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl 0.108-1 ii libtime-duration-parse-perl 0.15-1 ii libtry-tiny-perl0.30-1 ii libtype-tiny-perl 1.010001-1 ii libtypes-path-tiny-perl 0.006-1 ii perl5.30.0-9 Versions of packages parcimonie recommends: ii libglib-perl3:1.329.2-1 ii libgtk3-perl0.037-1 ii liblocale-gettext-perl 1.07-4 ii libnet-dbus-glib-perl 0.33.0-3+b2 ii libnet-dbus-perl1.2.0-1 ii libpango-perl 1.227-3+b2 ii libtime-duration-perl 1.21-1 ii tor 0.4.2.7-1 parcimonie suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
Bug#956941: .xsession-errors log show caja emitting a gtk-warning as failed to register client
Package: caja Version: 1.24.0-1 Severity: normal Dear Maintainer, Got the following, was browsing my .xsession-errors file. This is a new session, so unless mate is running some old configuration somewhere, which I would investigate if that is the matter, although you would have to help me. I did come across this in .xsession-errors file - (caja:9423): Gtk-WARNING **: 07:45:37.360: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client Please let me know if any more info. is needed. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-debug'), (100, 'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages caja depends on: ii caja-common 1.24.0-1 ii desktop-file-utils0.24-1 ii gvfs 1.44.1-1 ii libatk1.0-0 2.36.0-2 ii libc6 2.30-4 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libcaja-extension11.24.0-1 ii libexempi82.5.1-1 ii libexif12 0.6.21-6 ii libgail-3-0 3.24.18-1 ii libgdk-pixbuf2.0-02.40.0+dfsg-4 ii libglib2.0-0 2.64.1-1 ii libglib2.0-bin2.64.1-1 ii libglib2.0-data 2.64.1-1 ii libgtk-3-03.24.18-1 ii libice6 2:1.0.9-2 ii libmate-desktop-2-17 1.24.0-2 ii libnotify40.7.9-1 ii libpango-1.0-01.44.7-3 ii libpangocairo-1.0-0 1.44.7-3 ii libselinux1 3.0-1+b1 ii libsm62:1.2.3-1 ii libx11-6 2:1.6.9-2 ii libxml2 2.9.10+dfsg-4 ii mate-desktop 1.24.0-2 ii shared-mime-info 1.15-1 Versions of packages caja recommends: ii gvfs-backends 1.44.1-1 Versions of packages caja suggests: ii engrampa1.24.0-2 ii gstreamer1.0-tools 1.16.2-2 ii meld3.20.2-1 -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
Bug#956940: EC2 images should install compatibility symlinks for NVME drives
Package: cloud.debian.org Severity: wishlist As documented at https://opensource.creativecommons.org/blog/entries/2020-04-03-nvmee-on-debian-on-aws/ and https://lists.debian.org/debian-cloud/2020/04/msg00015.html, it would be helpful if we install meaningful /dev/xvd* or /dev/sd* symlinks mapping the EC2 API's block device mapping to the corresponding NVME device.
Bug#954042: ssl bug 954042
Note that next inxi, 3.0.39, will force ssl verification by default for Tiny::HTTP, just to get this issue closed. This change is now in pinxi if you want to test it. the --no-ssl flag will operate as expected for Tiny::HTTP, to some degree at least.
Bug#954965: /etc/ssh/ssh_config: ssh_config: Include custom config files at the end, so they can overwrite the default settings
Package: openssh-server Version: 1:8.2p1-4 Followup-For: Bug #954965 Just wanted to chime in to say that 1. I can confirm that the config works as intended, 2. The debug output is really quite confusing in this regard: ``` debug3: /etc/ssh/sshd_config.d/no-xforwarding.conf:1 setting X11Forwarding no […] debug3: /etc/ssh/sshd_config:91 setting X11Forwarding yes ``` This clearly suggests that X11Forwarding is being turned on again. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-rc5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openssh-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.73 ii dpkg 1.19.7 ii libaudit1 1:2.8.5-3+b1 ii libc6 2.30-4 ii libcom-err21.45.6-1 ii libcrypt1 1:4.4.16-1 ii libgssapi-krb5-2 1.17-7 ii libkrb5-3 1.17-7 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libselinux13.0-1+b3 ii libssl1.1 1.1.1f-1 ii libsystemd0245.4-4 ii libwrap0 7.6.q-30 ii lsb-base 11.1.0 ii openssh-client 1:8.2p1-4 ii openssh-sftp-server1:8.2p1-4 ii procps 2:3.3.16-4 ii runit-helper 2.8.15 ii ucf3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages openssh-server recommends: ii libpam-systemd [logind] 245.4-4 pn ncurses-term ii xauth1:1.0.10-1 Versions of packages openssh-server suggests: pn molly-guard pn monkeysphere ii ssh-askpass 1:1.2.4.1-10+b1 pn ufw -- debconf information excluded -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#956939: ITP: timekpr-next -- Keep control of computer usage
Package: wnpp Severity: wishlist Owner: Anthony Fok -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: timekpr-next Version : 0.2.13 Upstream Author : Eduards Bezverhijs * URL : http://launchpad.net/timekpr-next/ * License : GPL-3 Programming Lang: Python Description : Keep control of computer usage Timekpr-nExT is a program that tracks and controls the computer usage of your user accounts. You can limit their daily usage based on a timed access duration and configure periods of day when they can or cannot log in. . Any bugs should be reported to our bug tracker: https://bugs.launchpad.net/timekpr-next/+bugs Reason for packaging: Being a parent of several young kids, now especially stuck at home due to the Covid-19 pandemic, I have been searching for quite some time some kind of parental control software to limit their screen time in Linux. Today, I was lucky to come across this wiki entry: https://wiki.archlinux.org/index.php/Parental_control where Timekpr-nExT is the first on the list. Timekpr-nExT is also featured in the following November 2019 article: https://www.linuxuprising.com/2019/11/timekpr-next-is-linux-parental-control.html Timekpr-nExT has been living as an Ubuntu PPA for some years thanks to upstream author who also maintains the Debian packaging, and end user Sim asks for to have it officially packaged for Debian to get "massive exposure in BOTH Debian AND Ubuntu communities": https://answers.launchpad.net/timekpr-next/+question/685282 Sim also further points out that: I was looking for years for an effective program that can limit the time kids spend on computer. And there is absolutely nothing like this within 59000 current Debian packages. I'm sure thousands of teachers/parents worldwide are desperately looking for something like this. Arguing with children each time you want them to stop using computer is too exhausting... and I admit I am in the same boat myself, so here we are! :-) Since this is a Python 3 application, I intend to maintain it within the Python Applications Packaging Team. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl6ZEp8ACgkQ6iUAtBLF ms+AGhAAh2BPpuqXzjyzpf8iWz1f/Ki4k+f1co87In6vd+njeSGSQmwbvqSMqrSn 2hCjGeqRUHp7IqEkoPdZZV/6/N9aIhr8PlM9uZC8CF+E3QWw9KkWpLj+h8P25PkC 6AM9dZdxgZKaYkQaSX2y58VDfWIC9jMOJYaH9dBmv/k5l4RVU+YZqmJxU6xVxza1 dAj6v52dusbyF2f6WR6EiGUs81XWiesQmR+GDeiSPGcn4fH4k0DeK24yWiJDQAWi jqBTYrpRhSpQBna5kpSgeXh3m/08RD8x901iBtHjoTfE5pHYI4DYWhZ3Dh5LGMVP hqmjqlID3FlGXHpiFDtd82vvQNMM41UYJVsp5cVrBAu8nLdRpL6mLIEcvgLrZRdq kh+r4V2S6N9JvhjFvvIewEBS1JW1hXXh34MuF3ztm0ahm3j9xOF8hexTayn36TnA 5Y6swgamDp3U5Zt/tkaFbbrvvKENONGU/0wokK8hy0pqalcNsCMSiGx2wVbcR6z3 THeGfYUXBb1mOdP5eS+1Y4j4YfnuG/LdrIYQFBgAk5T0Fdemy7yYu45lBFPSeh4I F9kjlMpPIkC3ocBHjg9bgil/2eSSQeIEYL/hzujiSUAFKwsD9lT0kcGM30wum7da XM1fdZFtEos0AU9XzhB0HxmuXZVE/WQla4rVVkYAneLXHcPG1pQ= =VQXf -END PGP SIGNATURE-
Bug#954004: Info received (Bug#954004: systemd-udevd: do_page_fault() type=15 address=0x00000005)
The attached file provides debug info regarding the page fault generated by systemd-udevd. The fault appears to occur in builtin_net_setup_link. The faulting instruction comes from line 64 in ../src/basic/string-util.h. As noted, version 244.3-1 does not fault. Later versions do. Hope this helps. Regards, Dave Anglin -- John David Anglin dave.ang...@bell.net Page fault occurs in page 0. Apr 16 21:24:30 atlas kernel: do_page_fault() command='systemd-udevd' type=15 address=0x0005 in systemd-udevd[4109c000+9f000] Apr 16 21:24:30 atlas kernel: trap #15: Data TLB miss fault Apr 16 21:24:30 atlas kernel: CPU: 1 PID: 1152 Comm: systemd-udevd Not tainted 4.14.176+ #1 Apr 16 21:24:30 atlas kernel: Hardware name: 9000/785/C8000 Apr 16 21:24:30 atlas kernel: task: 00412e148ac0 task.stack: 00412e1b4000 Apr 16 21:24:30 atlas kernel: Apr 16 21:24:30 atlas kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI Apr 16 21:24:30 atlas kernel: PSW: 01001110 Not tainted Apr 16 21:24:30 atlas kernel: r00-03 00ff0004fe0f 000f 410f9093 411c9368 Apr 16 21:24:30 atlas kernel: r04-07 4114b000 f8f1740c Apr 16 21:24:30 atlas kernel: r08-11 411a19a8 41153840 411541b0 f8f1742c Apr 16 21:24:30 atlas kernel: r12-15 4115a980 f8f17448 f8f17440 f8f1754c Apr 16 21:24:30 atlas kernel: r16-19 f8f17348 41134a30 f8f17444 4114b000 Apr 16 21:24:30 atlas kernel: r20-23 0056 f8b0f1ba 001b Apr 16 21:24:30 atlas kernel: r24-27 41131648 001e 0005 4114b000 Apr 16 21:24:30 atlas kernel: r28-31 fffe 000f f8f17580 410c9223 Apr 16 21:24:30 atlas kernel: sr00-03 0007b800 0007b800 Apr 16 21:24:30 atlas kernel: sr04-07 0007b800 0007b800 0007b800 0007b800 Apr 16 21:24:30 atlas kernel: Apr 16 21:24:30 atlas kernel: VZOUICununcqcqcqcqcqcrmunTDVZOUI Apr 16 21:24:30 atlas kernel: FPSR: Apr 16 21:24:30 atlas kernel: FPER1: Apr 16 21:24:30 atlas kernel: fr00-03 Apr 16 21:24:30 atlas kernel: fr04-07 Apr 16 21:24:30 atlas kernel: fr08-11 Apr 16 21:24:30 atlas kernel: fr12-15 Apr 16 21:24:30 atlas kernel: fr16-19 Apr 16 21:24:30 atlas kernel: fr20-23 00e0 01e0 Apr 16 21:24:30 atlas kernel: fr24-27 Apr 16 21:24:30 atlas kernel: fr28-31 Apr 16 21:24:30 atlas kernel: Apr 16 21:24:30 atlas kernel: IASQ: 0007b800 0007b800 IAOQ: 410f8dc3 410f8dc7 Apr 16 21:24:30 atlas kernel: IIR: 0f40101cISR: 0007b800 IOR: 0005 Apr 16 21:24:30 atlas kernel: CPU:1 CR30: 00412e1b4000 CR31: 17fcfcfa83419f83 Apr 16 21:24:30 atlas kernel: ORIG_R28: Apr 16 21:24:30 atlas kernel: IAOQ[0]: 410f8dc3 Apr 16 21:24:30 atlas kernel: IAOQ[1]: 410f8dc7 Apr 16 21:24:30 atlas kernel: RP(r2): 410f9093 Instruction at IAOQ[0] matches fault instruction in IIR. Register r26 contains page fault address 5. (gdb) disass 0x410f8dc0-16,0x410f8dc0+16 Dump of assembler code from 0x410f8db0 to 0x410f8dd0: 0x410f8db0 :copy r3,r26 0x410f8db4 :copy r4,r19 0x410f8db8 :ldw 0(r7),r26 0x410f8dbc :cmpib,=,n 0,r26,0x410f8df0 0x410f8dc0 :ldb 0(r26),ret0 0x410f8dc4 :cmpiclr,<> 0,ret0,r0 0x410f8dc8 :b,l,n 0x410f8df0 :b,l 0x410f3808,rp End of assembler dump. 20: 0f 40 10 1c ldb 0(r26),ret0 24: 93 80 30 00 cmpiclr,<> 0,ret0,r0 (gdb) break *0x410f8dc0 Breakpoint 1 at 0x410f8dc0: file ../src/basic/string-util.h, line 64.
Bug#956268: (no subject)
Control: reopen 956268 Thank-you for taking the time to address this issue. Although your changes to d/copyright may accurately reflect the source package for 1.22.2, this bug was filed against 1.25.0. This version of the package has not received an update to d/copyright. Unfortunately, (assuming correctness in 1.22.2) the same d/copyright will not correctly represent the 1.25.0 source package.
Bug#956889: Acknowledgement (buster-pu: package zfs-linux/0.7.12-2+deb10u2)
Control: close -1 This bug is duplicated with #956889. When sending this mail for the first time my mutt crashed somehow. Hence the duplicated submission. On Thu, Apr 16, 2020 at 11:27:04AM +, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 956889: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956889. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Release Team > > If you wish to submit further information on this problem, please > send it to 956...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 956889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956889 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
Bug#956938: RFP: irccat -- cat to IRC
Package: wnpp Severity: wishlist * Package name: irccat Version : 0.4.5 Upstream Author : Russ Garrett https://github.com/ru * URL : https://github.com/irccloud/irccat * License : GPL-3 Programming Lang: Golang Description : cat to IRC irccat lets you easily send events to IRC channels from scripts and other applications. Supports input on: * TCP * HTTP * Prometheus alert manager * Grafana alerting The bot can also respond to events on IRC to run arbitrary commands. This is similar to KGB-bot and irker, but is much simpler to talk with and configure.$
Bug#837346: Info received ()
Vào 10:09 PM, T.7, 11 Th4, 2020 Debian Bug Tracking System < ow...@bugs.debian.org> đã viết: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Apache Maintainers > > If you wish to submit further information on this problem, please > send it to 837...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 837346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837346 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#929417: debconf: Readline frontend should check that stdin is a tty (to fix Docker build freezes)
On Thu, Apr 16, 2020 at 04:56:58PM -0700, Tianon Gravi wrote: > As a bit of added versioning information, this affects Debian Stretch > (1.5.61) and newer, but Debian Jessie (1.5.56+deb8u1) is unaffected > (and over in Ubuntu land, Xenial is unaffected at 1.5.58ubuntu2, but > Bionic at 1.5.66ubuntu1 and newer *is* affected). Actually, scratch that -- Jessie is also affected. I was testing with "tzdata" and it worked in Jessie, but testing with the example Anders provided of "keyboard-configuration" I was able to reproduce even on Jessie. Going back to Squeeze, I was no longer able to reproduce: | ... | Setting up keyboard-configuration (1.68+squeeze2) ... | debconf: unable to initialize frontend: Dialog | debconf: (TERM is not set, so the dialog frontend is not usable.) | debconf: falling back to frontend: Readline | debconf: unable to initialize frontend: Readline | debconf: (This frontend requires a controlling tty.) | debconf: falling back to frontend: Teletype | Configuring keyboard-configuration | -- | | Please select the layout matching the keyboard for this machine. | | 1. USA | 2. USA - Alternative international (former us_intl) | 3. USA - Cherokee | 4. USA - Classic Dvorak | 5. USA - Colemak | 6. USA - Dvorak | 7. USA - Dvorak international | 8. USA - Group toggle on multiply/divide key | 9. USA - International (AltGr dead keys) | 10. USA - International (with dead keys) | 11. USA - Left handed Dvorak | 12. USA - Macintosh | 13. USA - Programmer Dvorak | 14. USA - Right handed Dvorak | 15. USA - Russian phonetic | 16. USA - With EuroSign on 5 | 17. Other | | Keyboard layout: | Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111. | Use of uninitialized value $val in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 83, line 5. | Use of uninitialized value $val in concatenation (.) or string at /usr/share/perl5/Debconf/Format/822.pm line 84, line 5. | Setting up libgdbm3 (1.8.3-9) ... | ... ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
Bug#929417: debconf: Readline frontend should check that stdin is a tty (to fix Docker build freezes)
On Wed, 22 May 2019 23:36:43 -0400 (EDT) Anders Kaseorg wrote:
> When building a Debian- or Ubuntu-based Docker container, installing
> perl (so that Term::Readline is available) and a package that asks a
> Debconf question causes the build to freeze with an interactive readline
> prompt that cannot be answered:
> ...
> Docker builds are noninteractive, of course, and stdin is connected to
> /dev/null. What seems to have happened here is that apt created a pty and
> connected stdout and stderr to it, but left stdin connected to /dev/null.
> The Readline frontend checked that there’s a controlling tty (there is),
> but failed to check that stdin is a tty (it’s not). So it proceeded to
> wait for input from a tty that will never provide it.
>
> (Obviously one can set DEBIAN_FRONTEND=noninteractive as a workaround, but
> that shouldn’t be necessary, and is in fact discouraged:
> https://docs.docker.com/engine/faq/#why-is-debian_frontendnoninteractive-discouraged-in-dockerfiles
>
> because it’s often set in ways that persist for longer than intended.)
Friendly ping? :)
Would it be helpful if someone were to make the attached patch into a
Merge Request on Salsa for easier review?
As a bit of added versioning information, this affects Debian Stretch
(1.5.61) and newer, but Debian Jessie (1.5.56+deb8u1) is unaffected
(and over in Ubuntu land, Xenial is unaffected at 1.5.58ubuntu2, but
Bionic at 1.5.66ubuntu1 and newer *is* affected).
I'm not sure what changed this behavior between Jessie and Stretch
(possibly something outside the debconf package?), but the relevant
debdiff for debconf is relatively small (~400 lines if one excludes
translation updates), so I've attached that here in case it's helpful.
♥,
- Tianon
4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
diff -Nru --exclude '*.po' --exclude '*.pot'
debconf-1.5.56+deb8u1/bash_completion debconf-1.5.61/bash_completion
--- debconf-1.5.56+deb8u1/bash_completion 2017-06-16 15:22:02.0
-0700
+++ debconf-1.5.61/bash_completion 2015-11-07 19:17:02.0 -0800
@@ -1,4 +1,4 @@
-have debconf-show &&
+_have debconf-show &&
_debconf_show()
{
local cur
diff -Nru --exclude '*.po' --exclude '*.pot'
debconf-1.5.56+deb8u1/Debconf/Config.pm debconf-1.5.61/Debconf/Config.pm
--- debconf-1.5.56+deb8u1/Debconf/Config.pm 2017-06-16 15:22:02.0
-0700
+++ debconf-1.5.61/Debconf/Config.pm2015-07-12 10:35:31.0 -0700
@@ -59,7 +59,7 @@
my $text=shift;
my $hash=shift;
- $text =~ s/\${([^}]+)}/$ENV{$1}/eg;
+ $text =~ s/\$\{([^}]+)\}/$ENV{$1}/eg;
my %ret;
my $i;
diff -Nru --exclude '*.po' --exclude '*.pot'
debconf-1.5.56+deb8u1/Debconf/Element/Editor/Multiselect.pm
debconf-1.5.61/Debconf/Element/Editor/Multiselect.pm
--- debconf-1.5.56+deb8u1/Debconf/Element/Editor/Multiselect.pm 2017-06-16
15:22:02.0 -0700
+++ debconf-1.5.61/Debconf/Element/Editor/Multiselect.pm2015-11-07
18:11:17.0 -0800
@@ -13,7 +13,7 @@
=head1 DESCRIPTION
-Presents a list of choices to be selected amoung. Multiple selection is
+Presents a list of choices to be selected among. Multiple selection is
allowed.
=head1 METHODS
diff -Nru --exclude '*.po' --exclude '*.pot'
debconf-1.5.56+deb8u1/Debconf/Element/Editor/Select.pm
debconf-1.5.61/Debconf/Element/Editor/Select.pm
--- debconf-1.5.56+deb8u1/Debconf/Element/Editor/Select.pm 2017-06-16
15:22:02.0 -0700
+++ debconf-1.5.61/Debconf/Element/Editor/Select.pm 2015-11-07
18:11:19.0 -0800
@@ -13,7 +13,7 @@
=head1 DESCRIPTION
-Presents a list of choices to be selected amoung.
+Presents a list of choices to be selected among.
=head2 METHODS
diff -Nru --exclude '*.po' --exclude '*.pot'
debconf-1.5.56+deb8u1/Debconf/Element/Teletype/Boolean.pm
debconf-1.5.61/Debconf/Element/Teletype/Boolean.pm
--- debconf-1.5.56+deb8u1/Debconf/Element/Teletype/Boolean.pm 2017-06-16
15:22:02.0 -0700
+++ debconf-1.5.61/Debconf/Element/Teletype/Boolean.pm 2015-11-07
18:36:34.0 -0800
@@ -40,6 +40,13 @@
$default=$n;
}
+ # If this is not terse mode, we want to print out choices. Since we
+ # only have two choices, though, we use a compact display format.
+ my $description=$this->question->description;
+ if (Debconf::Config->terse eq 'false') {
+ $description.=" [$y/$n]";
+ }
+
my $value='';
while (1) {
@@ -47,7 +54,7 @@
$_=$this->frontend->prompt(
default => $default,
completions => [$y, $n],
- prompt => $this->question->description,
+ prompt => $description,
question => $this->question,
);
return unless defined $_;
diff -Nru --exclude '*.po' --exclude '*.pot'
debconf-1.5.56+deb8u1/Debconf/FrontEnd/Readline.pm
Bug#951761: buster-pu: package opam/2.0.3-1+deb10u1
control: retitle -1 buster-pu: package opam/2.0.3-1+deb10u1 thanks hi, On Fri, Feb 21, 2020 at 11:56:15AM +0100, Stéphane Glondu wrote: > It has been brought to my attention that opam doesn't work in buster > out of the box. This has been tracked in [1] (fixed in testing) and > [2]. See in particular comments starting at [3]. [...] > I've attached the proposed changes. I would like to apply them in a > buster update. I can confirm that those changes worked for me and enabled me to use opam on buster. Without them, following https://mirage.io/wiki/install does not work, with a patched opam it does. IMO #908203 (which is fixed by opam/2.0.3-1+deb10u1) should have severity 'important'. Please allow opam/2.0.3-1+deb10u1 into the next buster pointrelease. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#941199: Upstream has valid debian packaging
On Mon, 2 Mar 2020 12:44:42 +0100 Christian Ehrhardt wrote: > Hi, > since [1] seems to have valid packaging content and I've had a few users > reporting to use that for a while and it works well. Therefore I wanted to > ask what this might be missing - just someone who does the dput or was > there more going on in the background that is missing here? > Dear Laurent Bigonville and Christian Ehrhardt, I would like to package this one. Best regards, Seunghun
Bug#956893: wireguard-dkms-1.0.20200413-2 not build on Kernel 5.5.0-1
Control: affects 956893 + dkms On Thu 2020-04-16 14:27:57 +0200, Holger Schröder wrote: > Loading new wireguard-1.0.20200413 DKMS files... > Building for 5.5.0-1-amd64 > Building initial module for 5.5.0-1-amd64 > Error! The > /var/lib/dkms/wireguard/1.0.20200413/5.5.0-1-amd64/x86_64/dkms.conf > for module wireguard includes a BUILD_EXCLUSIVE directive which > does not match this kernel/arch. This indicates that it should not be built. > Skipped. Yep -- this is deliberate. building wireguard isn't necessary because 5.5.0-1 already ships with wireguard.ko! If you read /var/lib/dkms/wireguard/1.0.20200413/5.5.0-1-amd64/x86_64/dkms.conf (mentioned in the verbose dkms message above) you'll see that we have a special carveout there to accomodate for this nice backport. (see also #956241) The "Error!" message is unfortunate, because it's not actually an error at all. But that comes from dkms, and it's not something we can change directly in the wireguard-dkms package. I'm closing this bug report because everything is working as intended. you should even be able to use wireguard with your new 5.5.0-1 kernel without the wireguard-dkms package at all! If I'm misunderstanding this and you're actually having problems with wireguard on 5.5.0-1, feel free to reopen this report and give me more detail about the problem. Regards, --dkg signature.asc Description: PGP signature
Bug#956937: flatpak: "flatpak enter" dose not work
Package: flatpak Version: 1.2.5-0+deb10u1 Severity: important Dear Maintainer, * What led up to the situation? I tried flatpak today for the first time, installed an app and wanted to get a shell in its content to make some system settings (dark gtk theme), read manpage, found out about enter command, tried it but failed * What exactly did you do (or not do) that was effective (or ineffective)? -- === First Term == $ flatpak run org.midori_browser.Midori Note that the directories '/var/lib/flatpak/exports/share' '/home/user/.local/share/flatpak/exports/share' are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by Flatpak may not appear on your desktop until the session is restarted. == 2nd Term == $ flatpak enter org.midori_browser.Midori bash Note that the directories '/var/lib/flatpak/exports/share' '/home/user/.local/share/flatpak/exports/share' are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by Flatpak may not appear on your desktop until the session is restarted. Not running as root, may be unable to enter namespace error: No such pid org.midori_browser.Midori $ sudo flatpak enter org.midori_browser.Midori bash [sudo] password for user: error: org.midori_browser.Midori is neither a pid nor an application or instance ID $ ps auxf | grep -B 10 -A 10 -i midori [...] user 17920 0.0 0.0 11500 3580 pts/29 R+ 00:51 0:00 | \_ ps auxf user 17921 0.0 0.0 6412 884 pts/29 S+ 00:51 0:00 | \_ grep -B 10 -A 10 -i midori user 15787 0.0 0.0 8588 5012 pts/30 Ss 00:49 0:00 \_ bash root 16359 0.0 0.0 5192 972 pts/30 S+ 00:50 0:00 \_ bwrap --args 36 midori user 16370 0.0 0.0 5456 900 pts/30 S+ 00:50 0:00 \_ bwrap --args 36 midori user 16372 1.0 0.6 85894808 83064 pts/30 Sl+ 00:50 0:00 \_ midori user 16381 0.2 0.3 85989832 47784 pts/30 SLl+ 00:50 0:00 \_ /usr/libexec/webkit2gtk-4.0/WebKitNetworkProcess 3 21 user 16417 1.0 0.7 85787012 91116 pts/30 SLl+ 00:50 0:00 \_ /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 9 29 user 27055 0.0 0.2 482388 34200 ?Sl Apr01 2:00 mate-terminal user 27079 0.0 0.0 8580 1668 pts/5Ss+ Apr01 0:00 \_ bash user 20692 0.0 0.0 8712 1760 pts/6Ss+ Apr01 0:00 \_ bash user 24193 0.0 0.0 8580 1692 pts/7Ss+ Apr02 0:00 \_ bash user 32225 0.0 0.0 8580 1568 pts/9Ss Apr07 0:00 \_ bash [...] $ flatpak enter 16372 Note that the directories '/var/lib/flatpak/exports/share' '/home/user/.local/share/flatpak/exports/share' are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by Flatpak may not appear on your desktop until the session is restarted. error: INSTANCE and COMMAND must be specified See 'flatpak enter --help' $ flatpak enter 16372 bash Note that the directories '/var/lib/flatpak/exports/share' '/home/user/.local/share/flatpak/exports/share' are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by Flatpak may not appear on your desktop until the session is restarted. Not running as root, may be unable to enter namespace error: 16372 is neither a pid nor an application or instance ID $ flatpak enter 16359 bash Note that the directories '/var/lib/flatpak/exports/share' '/home/user/.local/share/flatpak/exports/share' are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by Flatpak may not appear on your desktop until the session is restarted. Not running as root, may be unable to enter namespace error: No such pid 16359 $ sudo flatpak enter 16359 bash error: 16359 is neither a pid nor an application or instance ID $ -- * What was the outcome of this action? to get some shell within that context * What outcome did you expect instead? error message with false statements (pid exist but it says it dose nto) thanks in advance Tim -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flatpak depends on: ii bubblewrap 0.3.1-4 ii libappstream-glib8 0.7.14-1 ii libarchive13 3.3.3-4+deb10u1 ii libc6 2.28-10 ii libdconf1 0.30.1-2 ii
Bug#956001: debdiff available
tags 956001 + pending thanks > I have a patch/debdiff ready for you. Thanks for the patch, included in the git repo! 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#956936: libvirt-daemon: clients unable to connect to libvirt: CheckAuthorization: Action org.libvirt.unix.manage is not registered
Package: libvirt-daemon Version: 6.0.0-6 Severity: important Hello, I've been unable to use libvirt for a while and I haven't yet found a workaround or a fix.. This started happening the last time I ran package upgrades. However, since I don't run them very often I'm not sure with which versions of packages it started happening. If it seems relevant to do so, I can test rolling back to older packages to figure out when things started to break down. I've been using libvirt with qemu-kvm for a while. my user is part of the libvirt and kvm groups so I should have access to the local unix sockets. however when I try and connect to libvirt on localhost (either with vagrant-libvirt or with virt-manager) I get an error message that also appears in the service's log as: Apr 16 17:51:47 meevyl libvirtd[544743]: error from service: CheckAuthorization: Action org.libvirt.unix.manage is not registered Apr 16 17:51:47 meevyl libvirtd[544743]: End of file while reading data: Input/output error >From what I could vaguely understand, the first line seems to be related to polkit but I don't quite understand how this thing is supposed to be working. I do have polkit installed and runing: $ dpkg -l | grep polkit ii gir1.2-polkit-1.0 0.105-26 amd64GObject introspection data for PolicyKit ii libpolkit-agent-1-0:amd64 0.105-26 amd64PolicyKit Authentication Agent API ii libpolkit-gobject-1-0:amd64 0.105-26 amd64PolicyKit Authorization API $ ps aux|grep polkit root 544473 0.0 0.0 235204 10120 ?Ssl 17:49 0:00 /usr/lib/policykit-1/polkitd --no-debug gabster 545750 0.0 0.0 8744 844 pts/8S+ 18:29 0:00 grep --color=auto polkit -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8), LANGUAGE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvirt-daemon depends on: ii libblkid1 2.34-0.1 ii libc6 2.30-4 ii libcap-ng0 0.7.9-2.1+b2 ii libdbus-1-3 1.12.16-2 ii libdevmapper1.02.1 2:1.02.167-1+b1 ii libfuse22.9.9-3 ii libgcc-s1 10-20200411-1 ii libglib2.0-02.64.2-1 ii libnetcf1 1:0.2.8-1+b3 ii libparted2 3.3-4 ii libpcap0.8 1.9.1-3 ii libpciaccess0 0.14-1 ii libselinux1 3.0-1+b3 ii libudev1245.4-4 ii libvirt-daemon-driver-qemu 6.0.0-6 ii libvirt06.0.0-6 ii libxml2 2.9.10+dfsg-5 Versions of packages libvirt-daemon recommends: ii libvirt-daemon-driver-lxc 6.0.0-6 ii libvirt-daemon-driver-vbox 6.0.0-6 ii libvirt-daemon-driver-xen 6.0.0-6 ii libxml2-utils 2.9.10+dfsg-5 ii netcat-openbsd 1.206-1 ii qemu1:4.2-6 ii qemu-kvm1:4.2-6 Versions of packages libvirt-daemon suggests: pn libvirt-daemon-driver-storage-gluster pn libvirt-daemon-driver-storage-rbd pn libvirt-daemon-driver-storage-zfs pn libvirt-daemon-system pn numad -- no debconf information
Bug#956935: RFS: grok-jpeg2000/5.1.0-0 -- development files for Grok, a JPEG 2000 image library
Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "grok-jpeg2000" Grok is one of only two actively developed open source JPEG 2000 codecs. * Package name : grok-jpeg2000 Version : 5.1.0-0 Upstream Author : boxe...@gmail.com * URL : https://github.com/GrokImageCompression/grok * License : [fill in] * Vcs : https://github.com/GrokImageCompression/grok Section : libs It builds those binary packages: grok-jpeg2000-10-dev - development files for Grok, a JPEG 2000 image library grok-jpeg2000-10 - JPEG 2000 image compression/decompression library grok-jpeg2000-tools - command-line tools using the JPEG 2000 library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/grok-jpeg2000 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/grok-jpeg2000/grok-jpeg2000_5.1.0-0.dsc Changes since the last upload: * Initial release Many Thanks! Aaron Boxer
Bug#956928: tex-common: Fails to install on hppa - missing engine luajithbtex
> Fixed on github, tag pending. Thanks for the report! Thanks Hilmar, feel free to upload, that was the necessary change. I have also bumped the dep in texlive-nonbin to 6.14 so that we are sure the correct version is installed. 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#956928: tex-common: Fails to install on hppa - missing engine luajithbtex
Control: tags -1 + pending Am 16.04.2020 um 21:55 teilte John David Anglin mit: > Install fails as follows: > > Setting up tex-common (6.13) ... > Running mktexlsr. This may take some time... done. > Running mtxrun --generate. This may take some time... done. > 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.WljFgC6Y > 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 > Fixed on github, tag pending. Thanks for the report! Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#948407: Please re-test
Hey Gio, seems like this was fixed upstream in Calamares 3.2.18, could you test again with the latest version? thanks, Jonathan
Bug#955245: ibus-unikey: diff for NMU version 0.7.0~beta1-0.1
Control: tags -1 +pending +patch Dear maintainer, I've prepared an NMU for ibus-unikey (versioned as 0.7.0~beta1-0.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. The full debdiff would be too large to attach. If you have any doubts with the upload, please let me know. Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#956934: RM: python-prowlpy -- RoQA; Depends on Python 2, dead upstream
Package: ftp.debian.org Severity: normal Please remove python-prowlpy. It depends on Python 2, is dead upstream (last commit nine years ago) and there are no remaining rdeps. Cheers, Moritz
Bug#956933: tpm2-tools: Invalid Maintainer Email Address
Package: tpm2-tools Version: 4.1.1-1 Severity: serious Justification: Policy 3.3 Policy requires a valid maintainer email address. Please see below: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: mathieu.trudel-lapie...@canonical.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table To: mathieu.trudel-lapie...@canonical.com From: Debian FTP Masters Subject: Processing of tpm2-tools_4.2-1_source.changes Date: Thu, 16 Apr 2020 21:00:10 + X-Debian: DAK X-DAK: DAK Precedence: bulk Auto-Submitted: auto-generated X-Debian-Package: tpm2-tools Message-Id: Scott K
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
On Thu, 16 Apr 2020 11:30:01 -0500 "Julio C. Ortega" wrote: > I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 > solved the problem. You can also force the next version of gnome-shell from unstable. sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. > Julio C. Ortega Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpoNNqPZcVvR.pgp Description: PGP signature
Bug#956932: buster-pu: package nvidia-graphics-drivers-legacy-390xx/390.132-3~deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to update the non-free nvidia-graphics-drivers-legacy-390xx in buster from 390.116-1 to 390.132-3~deb10u1. There are a few upstream fixes but no known CVE fixes. The majority of the changes are packaging related ... because the packaging is mainly generated (since we build 4 source packages from it in sid nowadays) and I'd like to keep it in sync to be able to propagate fixes through it without running into a merge nightmare at some point. Most changes were triggered by adding support for the separately packaged Tesla drivers - a huge textual diff (e.g. renaming of variables and substvars from "legacy" to the more generic "variant") without causing differences in the generated binaries. All packaging changes are backports from sid and should be documented in the changelog. (Some documentation changes may not be documented.) Some of these changes were already included in previous point releases when we updated nvidia-graphics-drivers-legacy-340xx for its EoL state. With these changes I hope to cover most changes to be backported through the bullseye release cycle and further updates will only include new upstream releases (with CVE fixes?) without significant packaging updates. This is a rebuild of the sid package for buster with no additional changes. As always for nvidia-graphics-drivers, the attached patch is a git diff of debian/ excluding the blobs (*.run). In case it would help your review, I could also provide (like in #956913): * a binary debdiff of 390.116-1 in buster against 390.116-1 rebuilt with the proposed packaging updates * a split source debdiff of debian/control for the actual changes without reordering and the reordering part Thanks for considering this series of non-trivial pu requests. Andreas ngd-390.132-3~deb10u1.diff.xz Description: application/xz
Bug#956910: Bug fixes with packages from unstable
Install the next version of gnome-shell from unstable: sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpgFTeNEF7SN.pgp Description: PGP signature
Bug#956931: autopkgtest: Build profiles support for autopkgtest
Package: autopkgtest Version: 5.12.2~6.gbp89ad39 Severity: wishlist Dear Maintainer, with the latest and greatest changes in dpkg, I think it would be nice if autopkgtest followed suit. Particularly, it would be advantageous to support running and building tests in autopkgtest under build profiles (esp. nodoc!). This would allow for smaller test footprint, less packages to pull (ie. you don't need texlive on the testbed), and faster building of the packages. I prepared a patch implementing such a change here: https://salsa.debian.org/jpalecek-guest/autopkgtest/-/commit/6275da59305d6e836cb3558f9f442479eb24fc95 The patch is functional, albeit incomplete due to missing documentation. The real issue is the control file format. In my patch, I use an extra stanza to specify build profiles, like this: >>> Build-Profiles: nodoc Tests: run-some-tests <<< I chose this format, because adding the specification to some of the tests would be IMHO misleading: the build profile applies to all of the tests indiscriminately, not to any particular one. Also, I chose to apply them to all @builddep@ dependencies as well. However, there is a problem about this: it makes the control file format non-backwards-compatible. Particularly, dpkg needs to be patched or it will croak on packages with such d/t/control. Maybe, some artificial Tests: line like Tests: * could be added? That would make the change backwards compatible. Dpkg still needs to be patched, but the change would be rather minimal. What do you think about this proposal? Please comment here or on salsa. I'm also CC-ing the dpkg developers, since it concerns them. Regards Jiri Palecek -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 5.5.0-rc5-686-pae (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages autopkgtest depends on: ii apt-utils 2.0.1 ii libdpkg-perl1.20.0+nmu2~1.gbpcd9614 ii procps 2:3.3.16-4 ii python3 3.8.2-2 ii python3-debian 0.1.36 Versions of packages autopkgtest recommends: pn autodep8 Versions of packages autopkgtest suggests: pn lxc pn lxd pn ovmf pn qemu-efi-aarch64 pn qemu-efi-arm pn qemu-system ii qemu-utils1:4.2-2 ii schroot 1.6.10-9 pn vmdb2 -- no debconf information
Bug#956894: upgrade-reports: display of gnome login screen failed /gnome crashes after applying dist-upgrade on 16th of April 2020
Thank you! I'll continue to apply upgrades within the next days then. Dennis On Thu, 16 Apr 2020 16:10:54 0100 Simon McVittie s...@debian.org (mailto:s...@debian.org)> wrote: Control: reassign -1 libgnome-desktop-3-18 Control: affects -1 gnome gnome-shell gdm3 Control: tags -1 = bullseye On Thu, 16 Apr 2020 at 15:56:33 0200, Bill Allombert wrote: > On Thu, Apr 16, 2020 at 02:30:46PM 0200, Dennis wrote: > >Can not register existing type 'GnomeBGSlideShow' This is caused by the ongoing library transition from libgnome-desktop-3-18 to libgnome-desktop-3-19 (#954422), which should sort itself out soon when all packages involved have been rebuilt with a consistent version. I'll merge the various duplicate bugs when new ones stop arriving. smcv
Bug#927255: powerpc-utils is uninstallable
Control: severity -1 normal Hi! Lowering the severity as this affects powerpc and ppc64 only [1], so no release architectures. On the other hand, I have uploaded pmac-utils to unreleased for powerpc and ppc64. On the other hand, it looks like that the package seems orphaned, so I will try to adopt it, update it to the latest version and possibly figure out whether pmac-utils is still required or not. Thanks, Adrian > [1] https://sources.debian.org/src/powerpc-utils/1.3.2-1.1/debian/control/#L13 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#956693: spyder: depends on python3.7
X-Debbugs-CC: debian-scie...@lists.debian.org To debian-science folks, I will be uploading another source-only upload with minimal changes in order to complete this Python3.8 transition. There are work about spyder 4.0 in Salsa experimental branch as well; I will keep it there as-is hoping someone could finish the packaging work. -- Best, Boyuan Yang On Tue, 14 Apr 2020 14:15:39 +0200 Graham Inggs wrote: > Source: spyder > Version: 3.3.6+dfsg1-4 > Severity: serious > Tags: bullseye sid > > The binary package spyder has a dependency on python3.7 [1]. > Since this is an arch:all package, it cannot be binNMU'd. > Please make a source-only upload so that it picks up a dependency on > python3.8 instead. signature.asc Description: This is a digitally signed message part
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
On Thu, 16 Apr 2020 11:30:01 -0500 "Julio C. Ortega" wrote: > I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 > solved the problem. You can also force the next version of gnome-shell from unstable. sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. > Julio C. Ortega Jean-Marc
Bug#956858: firmware-b43-installer.postinst returns with error
Package: firmware-b43-installer
Version: 1:019-5
Followup-For: Bug #956858
Yes, I can confirm that I get the same error message in German.
I translated it, which was probably not so clever after all.
I'm quite sure that the problem is actually with the German locale.
Line 64 in firmware-b43-installer.postinst reads
xargs -r -0 -a "${catalog}" dpkg-query -S 2>&1 1>/dev/null | sed -es',[^/]\+,,'
| xargs -r rm --
With German locale, the dpkg-query command returns
dpkg-query: Kein Pfad gefunden, der auf Muster
/lib/firmware/b43/lp0initvals14.fw passt
dpkg-query: Kein Pfad gefunden, der auf Muster
/lib/firmware/b43/lcn0bsinitvals25.fw passt
[and so on...]
Thus, the sed parsing returns something else than expected (the trailing
'passt' is not removed from the output of dpkg-query).
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firmware-b43-installer depends on:
ii b43-fwcutter 1:019-5
ii bzip21.0.8-2
ii ca-certificates 20190110
ii wget 1.20.3-1+b2
firmware-b43-installer recommends no packages.
firmware-b43-installer suggests no packages.
-- no debconf information
Bug#956930: RM: python-shelltoolbox -- RoQA; Depends on Python 2, dead upstream, unmaintained
Package: ftp.debian.org Severity: normal Please remove python-shelltoolbox. It depends on Python 2, is dead upstream (last commit in 2012), there are no reverse deps and the last maintainer upload was in 2012. Cheers, Moritz
Bug#956929: stretch-pu: package nvidia-graphics-drivers/390.132-1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to update the non-free nvidia-graphics-drivers in stretch from 390.116-1 to 390.132-1. There are a few upstream fixes but no known CVE fixes. The majority of the changes are packaging related ... because the packaging is mainly generated (since we build 4 source packages from it in sid nowadays) and I'd like to keep it in sync to be able to propagate fixes through it without running into a merge nightmare at some point. Most changes were triggered by adding support for the separately packaged Tesla drivers - a huge textual diff (e.g. renaming of variables and substvars from "legacy" to the more generic "variant") without causing differences in the generated binaries. All packaging changes are backports from sid and should be documented in the changelog. (Some documentation changes may not be documented.) Some of these changes were already included in previous point releases when we updated nvidia-graphics-drivers-legacy-340xx for its EoL state. With these changes I hope to cover most changes to be backported through the bullseye release cycle and further updates will only include new upstream releases (with CVE fixes?) without significant packaging updates. The proposed package is very similar to src:nvidia-graphics-drivers-legacy-390xx in sid/bullseye. As always for nvidia-graphics-drivers, the attached patch is a git diff of debian/ excluding the blobs (*.run). In case it would help your review, I could also provide (like in #956913): * a binary debdiff of 390.116-1 in stretch against 390.116-1 rebuilt with the proposed packaging updates * a split source debdiff of debian/control for the actual changes without reordering and the reordering part Andreas ngd-390.132-1.stretch.diff.xz Description: application/xz
Bug#937806: python-halberd: Python2 removal in sid/bullseye
On Wed, Sep 04, 2019 at 11:16:28AM +, Gianfranco Costamagna wrote: > control: forwared -1 https://github.com/jmbr/halberd/issues/2 Upstream seems dead, let's remove? Cheers, Moritz
Bug#956926: twinkle-console: First launch fails
On 2020-04-16 21:26, onal...@rhizogen.es.eu.org wrote: > Package: twinkle-console > Version: 1:1.10.1+dfsg-4 > Severity: important > > Dear Maintainer, > > twinkle-console fails to launch with the following message: > > Critical: Cannot open file for reading: /home/$USER/.twinkle/twinkle.cfg > > Here is the content of /home/$USER/.twinkle : > > drwx-- 2 $USER users 4096 Apr 16 21:05 tmp > -rw--- 1 $USER users0 Apr 16 21:05 twinkle.lck > -rw-r--r-- 1 $USER users 412 Apr 16 21:09 twinkle.log > -rw-r--r-- 1 $USER users 412 Apr 16 21:05 twinkle.log.old > > Regards, > More information : It happens with the version in testing and unstable too. However, on systems where twinkle (the graphical client) has been installed and used already, twinkle-console seems to launch properly, even if there is no home/$USER/.twinkle/twinkle.cfg file. Here is what I have on a system where the graphical twinkle client has been used before twinkle-console : ls -l .twinkle/ total 216 -rw-r--r-- 1 ac ac 2472 avril 16 13:31 u...@domain.cfg -rw-r--r-- 1 ac ac 2515 avril 16 12:59 u...@domain.cfg~ -rw-r--r-- 1 ac ac536 avril 16 16:06 gui_state.ini drwx-- 2 ac ac 4096 août 15 2019 tmp -rw-r--r-- 1 ac ac 2359 avril 16 15:59 twinkle.ch -rw--- 1 ac ac275 avril 16 14:58 twinkle.history -rw--- 1 ac ac 0 août 15 2019 twinkle.lck -rw-r--r-- 1 ac ac 116916 avril 16 16:06 twinkle.log -rw-r--r-- 1 ac ac 46128 avril 16 14:58 twinkle.log.old -rw-r--r-- 1 ac ac 1446 avril 16 16:06 twinkle.sys -rw-r--r-- 1 ac ac 1446 avril 16 14:58 twinkle.sys~ When I try to add something on the command line : $ twinkle-console --help Critical: Cannot open file for reading: /home/onalyrg/.twinkle/--help BTW twinkle-console has no manpage and no help either apparently. When I create the file : $ touch .twinkle/twinkle.cfg twinkle-console launches properly (with error messages because no account has been defined yet) Regards, --
Bug#956928: tex-common: Fails to install on hppa - missing engine luajithbtex
Package: tex-common Version: 6.13 Severity: normal Dear Maintainer, Install fails as follows: Setting up tex-common (6.13) ... Running mktexlsr. This may take some time... done. Running mtxrun --generate. This may take some time... done. 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.WljFgC6Y 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 We have in /tmp/fmtutil.WljFgC6Y: fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/texsis.log fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/texsis.fmt installed. fmtutil [ERROR]: not building luajithbtex due to missing engine: luajithbtex fmtutil [INFO]: disabled formats: 1 fmtutil [INFO]: successfully rebuilt formats: 35 fmtutil [INFO]: not available formats: 1 fmtutil [INFO]: failed to build: 1 (luajithbtex/luajithbtex) fmtutil [INFO]: total formats: 38 fmtutil [INFO]: exiting with status 1 On hppa, luajithbtex is not in texlive-binaries. Regards, Dave Anglin -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 4.14.175+ (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tex-common depends on: ii dpkg 1.19.7 ii ucf 3.0038+nmu1 tex-common recommends no packages. Versions of packages tex-common suggests: ii debhelper 13 Versions of packages texlive-base depends on: ii debconf [debconf-2.0] 1.5.73 ii libpaper-utils 1.1.28 ii sensible-utils 0.0.12+nmu1 ii texlive-binaries 2020.20200327.54578-3 ii ucf3.0038+nmu1 ii xdg-utils 1.1.3-2 Versions of packages texlive-base recommends: ii lmodern 2.004.5-6 Versions of packages texlive-base suggests: ii ghostscript [postscript-viewer] 9.52~dfsg-1 ii gv [postscript-viewer]1:3.7.4-2 pn perl-tk pn xzdec ii zathura-pdf-poppler [pdf-viewer] 0.3.0-1 Versions of packages texlive-binaries depends on: ii dpkg1.19.7 ii install-info6.7.0.dfsg.2-5 ii libc6 2.30-4 ii libcairo2 1.16.0-4 ii libfontconfig1 2.13.1-3 ii libfreetype62.10.1-2 ii libgcc-s4 10-20200411-1 ii libgmp102:6.2.0+dfsg-4 ii libgraphite2-3 1.3.14-1 ii libharfbuzz0b 2.6.4-1 ii libice6 2:1.0.9-2 ii libicu6363.2-3 ii libkpathsea62020.20200327.54578-3 ii libmpfr64.0.2-1 ii libpaper1 1.1.28 ii libpixman-1-0 0.36.0-1 ii libpng16-16 1.6.37-2 ii libptexenc1 2020.20200327.54578-3 ii libsm6 2:1.2.3-1 ii libstdc++6 10-20200411-1 ii libsynctex2 2020.20200327.54578-3 ii libteckit0 2.5.8+ds2-5 ii libtexlua53 2020.20200327.54578-3 ii libx11-62:1.6.9-2 ii libxaw7 2:1.0.13-1+b2 ii libxext62:1.3.3-1+b2 ii libxi6 2:1.7.9-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii libxt6 1:1.1.5-1 ii libzzip-0-130.13.62-3.2 ii perl5.30.0-9 ii t1utils 1.41-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages texlive-binaries recommends: ii dvisvgm 2.9.1-1 ii texlive-base 2020.20200329-3 -- debconf information: texlive-base/texconfig_ignorant: tex-common/check_texmf_wrong: texlive-base/binary_chooser: pdftex, dvips, dvipdfmx, xdvi tex-common/check_texmf_missing:
Bug#956927: wav2cdr: Regression in arm64 CI: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
Package: wav2cdr Version: 2.3.4-3 Severity: important The new and first CI test[1] for wav2cdr fails in arm64[2]. Consequently, the revision 2.3.4-3 will not migrate to testing. [1] https://salsa.debian.org/debian/wav2cdr/-/blob/debian/master/debian/tests/control [2] https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz The significative output is: autopkgtest [19:42:07]: test command1: wav2cdr -V | grep Version autopkgtest [19:42:07]: test command1: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. autopkgtest [19:42:07]: test command1: ---] autopkgtest [19:42:07]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 1 autopkgtest [19:42:07]: test command1: - - - - - - - - - - stderr - - - - - - - - - - wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. [...] autopkgtest [19:42:16]: test command2: wav2cdr --help | grep describes autopkgtest [19:42:16]: test command2: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. autopkgtest [19:42:16]: test command2: ---] autopkgtest [19:42:16]: test command2: - - - - - - - - - - results - - - - - - - - - - command2 FAIL non-zero exit status 1 autopkgtest [19:42:17]: test command2: - - - - - - - - - - stderr - - - - - - - - - - wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. [...] autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3 autopkgtest [19:42:21]: test command3: [--- wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. bash: line 1: 837 Aborted bash -ec 'wav2cdr debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a /tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout) autopkgtest [19:42:21]: test command3: ---] autopkgtest [19:42:21]: test command3: - - - - - - - - - - results - - - - - - - - - - command3 FAIL non-zero exit status 134 autopkgtest [19:42:22]: test command3: - - - - - - - - - - stderr - - - - - - - - - - wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed. autopkgtest [19:42:22]: summary command1 FAIL non-zero exit status 1 command2 FAIL non-zero exit status 1 command3 FAIL non-zero exit status 134 Eriberto
Bug#956069: dask: Please skip network-requiring tests in autopkgtest
Hi, On Mon, 6 Apr 2020 23:34:59 +0200 Christian Kastner wrote: > In a recent CI-test [1], dask failed on arm64 because one of the tests > required network access, but this wasn't available on the particular CI > host. > > Please exclude these tests for now. This can be done with the attached > patch, which excludes those all tests which are marked as 'network' > (admittedly, I didn't test it, but only because of its simplicity). > > There's more discussion, including the background on this, and how > this issue might be solved in future, here [2]. I just uploaded a new version of autopkgtest. It gained a new restriction that should be added to tests that require internet access beyond the apt archive. Please add the needs-internet restriction to those tests, if you intent to keep the network tests in. Paul
Bug#956926: twinkle-console: First launch fails
Package: twinkle-console Version: 1:1.10.1+dfsg-4 Severity: important Dear Maintainer, twinkle-console fails to launch with the following message: Critical: Cannot open file for reading: /home/$USER/.twinkle/twinkle.cfg Here is the content of /home/$USER/.twinkle : drwx-- 2 $USER users 4096 Apr 16 21:05 tmp -rw--- 1 $USER users0 Apr 16 21:05 twinkle.lck -rw-r--r-- 1 $USER users 412 Apr 16 21:09 twinkle.log -rw-r--r-- 1 $USER users 412 Apr 16 21:05 twinkle.log.old Regards, -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (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: sysvinit (via /sbin/init) Versions of packages twinkle-console depends on: ii libasound2 1.1.8-1 ii libc6 2.28-10 ii libccrtp2v5 2.0.9-2.3 ii libgcc1 1:8.3.0-6 ii libgsm1 1.0.18-2 ii libmagic1 1:5.35-4+deb10u1 ii libreadline77.0-5 ii libsndfile1 1.0.28-6 ii libspeex1 1.2~rc1.2-1+b2 ii libspeexdsp11.2~rc1.2-1+b2 ii libstdc++6 8.3.0-6 ii libucommon8 7.0.0-16 ii libxml2 2.9.4+dfsg1-7+b3 ii twinkle-common 1:1.10.1+dfsg-4 Versions of packages twinkle-console recommends: pn twinkle twinkle-console suggests no packages. -- no debconf information
Bug#906072: Ogon packages available (Linux RDP Server)
Hi Marcel, On Do 16 Apr 2020 19:33:51 CEST, marcel wrote: Hi, I just wanted to let you know about ab packaged version of ogon (https://github.com/ogon-project (https://github.com/ogon-project), a linux Remote Desktop Protocol (RDP) server implementation). https://launchpad.net/~linux-ng/+archive/ubuntu/ogon (https://launchpad.net/~linux-ng/+archive/ubuntu/ogon) Maybe this can make it into Debian and helps to get ogon usable for a wider public. Bye, Marcel very cool. I will take a look when time allows it. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpofA2R7t0RK.pgp Description: Digitale PGP-Signatur
Bug#956925: dpkg: dpkg-source: should fail before-build if patches can't be applied fully in v3-quilt
Package: dpkg
Version: 1.20.0+nmu2~1.gbpcd9614
Severity: normal
Tags: patch
Dear Maintainer,
while building some of my packages, I noticed they were built without
patches applied. Further investigation in the code showed that it was
caused by dpkg-source --before-build carrying on silently if the first
patch could't be applied, eg. when the series was partially applied, or
the patch itself was somehow defective. It seems this behaviour was a
legacy from package format 2 and IMHO is totally unneeded with quilt. I
therefore suggest to apply this patch, which I've used for several
months now without problems. It relegates the issue of deciding when to
apply patches to quilt.
Regards
Jiri Palecek
From f489217e511c4ed5c78d63fcc7688a630b73bc67 Mon Sep 17 00:00:00 2001
From: =?iso8859-2?q?Ji=F8=ED=20Pale=E8ek?=
Date: Sun, 27 Oct 2019 18:55:06 +0100
Subject: [PATCH] Don't pass before-build stage when first patch doesn't apply
with format V3-quilt
When the first patch doesn't apply, dpkg-source --before-build
silently continues. This behaviour is meant to allow it to continue
when the patch series has been applied, however, it also makes it
very prone to breakage. Particularly, if your first patch is applied
but the rest isn't (eg. has been applied upstream), or if it is
defective, you are going to get a package built with Debian patches
silently ignored. Quilt will safely apply all the patches, even if
some of them are already applied, and fail correctly when the patches
are defective. V2 doesn't offer any such functionality, so IMHO the
cleanest behaviour is to rely on quilt and fail if patches according
to its bookkeeping should be applied but can't.
---
scripts/Dpkg/Source/Package/V3/Quilt.pm | 4
1 file changed, 4 deletions(-)
diff --git a/scripts/Dpkg/Source/Package/V3/Quilt.pm b/scripts/Dpkg/Source/Package/V3/Quilt.pm
index 45237d26a..25c5aab1b 100644
--- a/scripts/Dpkg/Source/Package/V3/Quilt.pm
+++ b/scripts/Dpkg/Source/Package/V3/Quilt.pm
@@ -235,10 +235,6 @@ sub check_patches_applied {
my $next = $quilt->next();
return if not defined $next;
-my $first_patch = File::Spec->catfile($dir, 'debian', 'patches', $next);
-my $patch_obj = Dpkg::Source::Patch->new(filename => $first_patch);
-return unless $patch_obj->check_apply($dir, fatal_dupes => 1);
-
$self->apply_patches($dir, usage => 'preparation', verbose => 1);
}
--
2.25.1
-- Package-specific info:
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 5.5.0-rc5-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.8-2
ii libc62.30-4
ii liblzma5 5.2.4-1+b1
ii libselinux1 3.0-1+b1
ii tar 1.30+dfsg-6
ii zlib1g 1:1.2.11.dfsg-2
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt2.0.1
pn debsig-verify
-- no debconf information
Bug#956014: new upstream LTS version
Le lundi 06 avril 2020 à 08:43:52+0200, Harald Dunkel a écrit : > Package: lxc > Version: 1:3.1.0+really3.0.4-2 > > Upstream announced new LTS versions for LXC, LXCFS and LXD, see > https://lists.linuxcontainers.org/pipermail/lxc-users/2020-April/015198.html > > Do you think it would be possible to upgrade the lxc and lxcfs packages > for sid? I would be glad to help. > > > Regards Dear Harald, Thanks for your bug report and your offer for help! I intend to package LXC 4 soon, and I'd be glad to have some testers! I was considering the idea to package it in experimental first, would it be fine with you? Cheers! -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Bug#956923: u-boot-sdunxi: A64-Olinuxino(-eMMC) no USB
Source: u-boot Version: 2020.04+dfsg-1 Severity: normal Tags: upstream Hi, USB is not working on my Olimex A64-Olinuxino-1Ge4GW Rev. D, no matter if I use the u-boot variant with or without eMMC (but that's no surprise). I attached boot logs with and without attached USB key. In both cases one gets an "EHCI failed to shut down host controller." while loading the kernels fdt. The error message with attached USB key is: scanning bus usb@1c1b400 for devices... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) USB device not accepting new address (error=20) After booting Linux there is still no USB available, bat that's a different bug report I guess ;-). I attached the dmesg log anyway. Best, Philip -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (600, 'testing'), (550, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled U-Boot SPL 2020.04+dfsg-1 (Apr 15 2020 - 00:24:39 +) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug): NOTICE: BL31: Built : 15:34:34, Apr 10 2020 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x4090fd0, model: Olimex A64-Olinuxino-eMMC INFO:ARM GICv2 driver initialized INFO:Configuring SPC Controller NOTICE: BL31: PMIC: Detected AXP803 on RSB. INFO:PMIC: AXP803: Enabling DRIVEVBUS INFO:PMIC: AXP803: dcdc1 voltage: 3.300V INFO:PMIC: AXP803: dcdc5 voltage: 1.360V INFO:PMIC: AXP803: dcdc6 voltage: 1.100V INFO:PMIC: AXP803: dldo1 voltage: 3.300V INFO:BL31: Platform setup done INFO:BL31: Initializing runtime services INFO:BL31: cortex_a53: CPU workaround for 843419 was applied INFO:BL31: cortex_a53: CPU workaround for 855873 was applied INFO:BL31: Preparing for EL3 exit to normal world INFO:Entry point address = 0x4a00 INFO:SPSR = 0x3c9 U-Boot 2020.04+dfsg-1 (Apr 15 2020 - 00:24:39 +) Allwinner Technology CPU: Allwinner A64 (SUN50I) Model: Olimex A64-Olinuxino-eMMC DRAM: 1 GiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c1' mmc@1c0f000: 0, mmc@1c1: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In:serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c3 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) USB device not accepting new address (error=20) 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3012 bytes read in 3 ms (980.5 KiB/s) ## Executing script at 4fc0 U-boot loaded from SD Boot script loaded from mmc 175 bytes read in 2 ms (85 KiB/s) 24201 bytes read in 8 ms (2.9 MiB/s) 29057066 bytes read in 1247 ms (22.2 MiB/s) 21069680 bytes read in 905 ms (22.2 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe0 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size:29057002 Bytes = 27.7 MiB Load Address: Entry Point: Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa0 Booting using the fdt blob at 0x4fa0 EHCI failed to shut down host controller. Loading Ramdisk to 4844a000, end 49ea ... OK Loading Device Tree to 483db000, end 48449fff ... OK Starting kernel ... U-Boot SPL 2020.04+dfsg-1 (Apr 15 2020 - 00:24:39 +) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug): NOTICE: BL31: Built : 15:34:34, Apr 10 2020 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x4090fd0, model: Olimex A64-Olinuxino-eMMC INFO:ARM GICv2 driver initialized INFO:Configuring SPC Controller NOTICE: BL31: PMIC: Detected AXP803 on RSB. INFO:PMIC: AXP803: Enabling DRIVEVBUS INFO:PMIC: AXP803: dcdc1 voltage: 3.300V INFO:PMIC: AXP803: dcdc5
Bug#956924: cups didn't work anymore after upgrading to 2.3.1
Package: cups Version: 2.2.10-6+deb10u2 Severity: important Dear Maintainer, thank you for maintaining cups! * What led up to the situation? i've upgraded from stable to testing * What exactly did you do (or not do) that was effective (or ineffective)? there was a set of package upgrades i suspect. the error manifested in the cups error log. especially "Filter Failed", and HTTP_STATE_WAITING Closing for error 32 (Broken pipe) * What was the outcome of this action? i couldn't print, untill i reversed the whole printing subsystem to stable. i suspect, the problem is the missing ippserver binary, and i will report to cups-ipp-utils. * What outcome did you expect instead? i would be happy has my wife continue to use the printer and not bug me to fix it. thank you in advance for any fix, alex -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (1001, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 5.5.0-1-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/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups depends on: ii cups-client2.2.10-6+deb10u2 ii cups-common2.3.1-11 ii cups-core-drivers 2.2.10-6+deb10u2 ii cups-daemon2.2.10-6+deb10u2 ii cups-filters 1.21.6-5 ii cups-ppdc 2.2.10-6+deb10u2 ii cups-server-common 2.3.1-11 ii debconf [debconf-2.0] 1.5.73 ii ghostscript9.27~dfsg-2+deb10u3 ii libavahi-client3 0.7-5 ii libavahi-common3 0.7-5 ii libc6 2.30-4 ii libcups2 2.2.10-6+deb10u2 pn libcupsimage2 ii libgcc-s1 [libgcc1]10-20200324-1 ii libgcc11:10-20200324-1 ii libstdc++6 10-20200324-1 ii libusb-1.0-0 2:1.0.23-2 ii poppler-utils 0.71.0-6 ii procps 2:3.3.16-4 Versions of packages cups recommends: ii avahi-daemon 0.7-5 ii colord 1.4.4-2 ii cups-filters [ghostscript-cups] 1.21.6-5 pn printer-driver-gutenprint Versions of packages cups suggests: ii cups-bsd 2.2.10-6+deb10u2 ii foomatic-db-compressed-ppds [foomatic-db] 20200401-1 pn hplip ii printer-driver-cups-pdf [cups-pdf] 3.0.1-6 pn printer-driver-hpcups ii smbclient 2:4.11.5+dfsg-1+b1 ii udev 245.4-3 -- debconf information: * cupsys/backend: lpd, socket, usb, snmp, dnssd * cupsys/raw-print: true
Bug#956922: ITP: fsverity -- Userspace utilities for fs-verity
Package: wnpp Severity: wishlist Owner: Romain Perier * Package name: fsverity Version : 1.0 Upstream Author : Eric Biggers * URL : https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git * License : GPL Programming Lang: C Description : Userspace utilities for fs-verity This is fsverity, a userspace utility for fs-verity. fs-verity is a Linux kernel feature that does transparent on-demand integrity/authenticity verification of the contents of read-only files, using a hidden Merkle tree (hash tree) associated with the file. The mechanism is similar to dm-verity, but implemented at the file level rather than at the block device level. The fsverity utility allows you to set up fs-verity protected files. This package will be helpful for handling the fsverity feature on a file from userspace. I want to maintain this package. As DM, I need someone for the initial upload. Packaging is currently hosted here https://salsa.debian.org/rperier-guest/fsverity, and will be developed at https://salsa.debian.org/debian/fsverity
Bug#956919: patch
>From 2d81d6435c73e573779e5162755fbae4ab5ff036 Mon Sep 17 00:00:00 2001
From: dann frazier
Date: Thu, 16 Apr 2020 12:44:23 -0600
Subject: [PATCH] Add support for new AMD SMCA bank types. Closes: #956919.
---
debian/changelog | 7 +
...-support-for-new-AMD-SMCA-bank-types.patch | 212 ++
.../rasdaemon-rename-CPU_NAPLES-cputype.patch | 71 ++
debian/patches/series | 2 +
4 files changed, 292 insertions(+)
create mode 100644 debian/patches/rasdaemon-add-support-for-new-AMD-SMCA-bank-types.patch
create mode 100644 debian/patches/rasdaemon-rename-CPU_NAPLES-cputype.patch
diff --git a/debian/changelog b/debian/changelog
index 21fb2b1..2f5c217 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+rasdaemon (0.6.5-2) UNRELEASED; urgency=medium
+
+ * Use CPU feature flag instead of family to detect AMD SMCA support.
+ * Add support for new AMD SMCA bank types. Closes: #956919
+
+ -- dann frazier Thu, 16 Apr 2020 12:43:23 -0600
+
rasdaemon (0.6.5-1) unstable; urgency=medium
* Update to latest upstream
diff --git a/debian/patches/rasdaemon-add-support-for-new-AMD-SMCA-bank-types.patch b/debian/patches/rasdaemon-add-support-for-new-AMD-SMCA-bank-types.patch
new file mode 100644
index 000..3fd2ee5
--- /dev/null
+++ b/debian/patches/rasdaemon-add-support-for-new-AMD-SMCA-bank-types.patch
@@ -0,0 +1,212 @@
+From 8704a85d8dc3483423ec2934fee8132f85f8fdb6 Mon Sep 17 00:00:00 2001
+From: "Brian WoodsGhannam, Yazen"
+Date: Fri, 1 Nov 2019 15:48:14 +0100
+Subject: [PATCH] rasdaemon: add support for new AMD SMCA bank types
+
+Going forward, the Scalable Machine Check Architecture (SMCA) has some
+updated and additional bank types which show up in Zen2. The differing
+bank types include: CS_V2, PSP_V2, SMU_V2, MP5, NBIO, and PCIE. The V2
+bank types replace the original bank types but have unique HWID/MCAtype
+IDs from the originals so there's no conflicts between different
+versions or other bank types. All of the differing bank types have new
+MCE descriptions which have been added as well.
+
+CC: "mchehab+sams...@kernel.org" , "Namburu, Chandu-babu" # Thread-Topic: [PATCH 2/2] rasdaemon: add support for new AMD SMCA bank types
+Signed-off-by: Brian Woods
+Signed-off-by: Yazen Ghannam
+Cc: Chandu-babu Namburu
+Signed-off-by: Mauro Carvalho Chehab
+---
+ mce-amd-smca.c | 112 +
+ 1 file changed, 112 insertions(+)
+
+diff --git a/mce-amd-smca.c b/mce-amd-smca.c
+index 6c3e8a5..114e786 100644
+--- a/mce-amd-smca.c
b/mce-amd-smca.c
+@@ -49,11 +49,17 @@ enum smca_bank_types {
+ SMCA_FP,/* Floating Point */
+ SMCA_L3_CACHE, /* L3 Cache */
+ SMCA_CS,/* Coherent Slave */
++ SMCA_CS_V2, /* Coherent Slave V2 */
+ SMCA_PIE, /* Power, Interrupts, etc. */
+ SMCA_UMC, /* Unified Memory Controller */
+ SMCA_PB,/* Parameter Block */
+ SMCA_PSP, /* Platform Security Processor */
++ SMCA_PSP_V2,/* Platform Security Processor V2 */
+ SMCA_SMU, /* System Management Unit */
++ SMCA_SMU_V2,/* System Management Unit V2 */
++ SMCA_MP5, /* Microprocessor 5 Unit */
++ SMCA_NBIO, /* Northbridge IO Unit */
++ SMCA_PCIE, /* PCI Express Unit */
+ N_SMCA_BANK_TYPES
+ };
+
+@@ -165,6 +171,23 @@ static const char * const smca_cs_mce_desc[] = {
+ "Atomic request parity",
+ "ECC error on probe filter access",
+ };
++/* Coherent Slave Unit V2 */
++static const char * const smca_cs2_mce_desc[] = {
++ "Illegal Request",
++ "Address Violation",
++ "Security Violation",
++ "Illegal Response",
++ "Unexpected Response",
++ "Request or Probe Parity Error",
++ "Read Response Parity Error",
++ "Atomic Request Parity Error",
++ "SDP read response had no match in the CS queue",
++ "Probe Filter Protocol Error",
++ "Probe Filter ECC Error",
++ "SDP read response had an unexpected RETRY error",
++ "Counter overflow error",
++ "Counter underflow error",
++};
+ /* Power, Interrupt, etc.. */
+ static const char * const smca_pie_mce_desc[] = {
+ "HW assert",
+@@ -189,10 +212,75 @@ static const char * const smca_pb_mce_desc[] = {
+ static const char * const smca_psp_mce_desc[] = {
+ "PSP RAM ECC or parity error",
+ };
++/* Platform Security Processor V2 */
++static const char * const smca_psp2_mce_desc[] = {
++ "High SRAM ECC or parity error",
++ "Low SRAM ECC or parity error",
++ "Instruction Cache Bank 0 ECC or parity error",
++ "Instruction Cache Bank 1 ECC or parity error",
++ "Instruction Tag Ram 0 parity error",
++ "Instruction Tag Ram 1 parity error",
++ "Data Cache Bank 0 ECC or parity error",
++ "Data Cache Bank 1 ECC or parity error",
++ "Data Cache Bank 2 ECC or parity error",
++ "Data Cache Bank 3 ECC or parity error",
++ "Data Tag Bank 0 parity error",
++ "Data Tag Bank 1 parity error",
++ "Data Tag Bank 2 parity error",
++ "Data Tag Bank 3 parity error",
++ "Dirty Data Ram parity error",
++ "TLB Bank 0 parity error",
Bug#956912: ITP: golang-github-davecgh-go-spew -- Implements a deep pretty printer for Go data structures to aid in debugging
On Fri, Apr 17, 2020 at 12:37 AM Manas Kashyap wrote: > * Package name: golang-github-davecgh-go-spew It has been packaged. https://tracker.debian.org/pkg/golang-github-davecgh-go-spew -- Shengjing Zhu
Bug#123468: [Bug c/6906] warn about asserts with side effects
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6906
felix changed:
What|Removed |Added
CC||felix.von.s at posteo dot de
--- Comment #9 from felix ---
I have just realised that __builtin_pure_p is already expressible:
#define __builtin_pure_p(expr) \
(__builtin_object_size(((void)(expr), ""), 2))
If (expr) is free of side effects, this is the same as
__builtin_object_size("", 2), which is 1. Otherwise, the expression returns 0.
This is documented behaviour, by the way. The documentation for
__builtin_object_size at
states:
> __builtin_object_size never evaluates its arguments for side effects.
> If there are any side effects in them, it returns (size_t) -1 for
> type 0 or 1 and (size_t) 0 for type 2 or 3.
Experimentation reveals __attribute__((pure)) is enough for
__builtin_object_size to consider a function free of side effects.
--
You are receiving this mail because:
You reported the bug.
Bug#956918: RFS: libutempter/1.1.6-6 -- privileged helper for utmp/wtmp updates (development)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libutempter" * Package name: libutempter Version : 1.1.6-6 Upstream Author : Dmitry V. Levin * URL : http://git.altlinux.org/people/ldv/packages/?p=libutempter.git * License : LGPL-2.1 * Vcs : https://salsa.debian.org/cgzones-guest/libutempter Section : libs It builds those binary packages: libutempter-dev - privileged helper for utmp/wtmp updates (development) libutempter0 - privileged helper for utmp/wtmp updates (runtime) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libutempter Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libu/libutempter/libutempter_1.1.6-6.dsc Changes since the last upload: * d/patches: silence all intentional omits of copying null-character Should fix FTBFS on kfreebsd Best regards, Christian Göttsche
Bug#956920: djangorestframework-api-key: invalid copyright claim in debian/patches/Fix_mkdocs_yml
Source: djangorestframework-api-key Version: 2.0.0-1 X-Debbugs-CC: utka...@debian.org Hello, During review in NEW, I noticed that mkdocs.yml says copyright: © 2018-present Florimond Manca but this is not a valid copyright claim because copyright is, conceptually, something time-limited. Please ask upstream to replace "present" with the year in which the file was most recently modified. -- Sean Whitton signature.asc Description: PGP signature
Bug#956921: subversion: Debian patch last-changed-date-charset has an error leak
Source: subversion
Version: 1.13.0-3
Severity: normal
Tags: patch
Good morning James,
One of the Debian patches has a error leak:
[[[
--- debian/patches/last-changed-date-charset
+++ debian/patches/last-changed-date-charset
@@ -24,7 +24,7 @@ index c8c3018..b69f90a 100644
+ {
+ char *date_keyword;
+ char *date_utf8 = svn_time_to_human_cstring (date, pool);
-+ svn_utf_cstring_from_utf8(_keyword, date_utf8, pool);
++ SVN_ERR(svn_utf_cstring_from_utf8(_keyword, date_utf8,
pool));
+ svn_stringbuf_appendcstr(value, date_keyword);
+}
break;
]]]
Cheers,
Daniel
Bug#956919: please add support for new AMD SMCA bank types
Package: rasdaemon Version: 0.6.5-1 Severity: normal Tags: patch Upstream has merged patches to add support for new AMD SMCA bank types. I've tested the following backport on a Rome system (will submit a salsa PR as well). -- System Information: Debian Release: bullseye/sid 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 5.5.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND 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 rasdaemon depends on: ii libc62.30-4 ii libdbd-sqlite3-perl 1.64-1+b1 ii libsqlite3-0 3.31.1-5 ii perl 5.30.0-9 ii sqlite3 3.31.1-5 rasdaemon recommends no packages. rasdaemon suggests no packages. -- no debconf information
Bug#946572: abcm2ps: diff for NMU version 8.14.7-0.2
Control: tags 946572 + patch Control: tags 946572 + pending Dear maintainer, I've prepared an NMU for abcm2ps (versioned as 8.14.7-0.2) and uploaded it to DELAYED/15. Please feel free to tell me if I should delay it longer. Regards. diff -Nru abcm2ps-8.14.7/debian/changelog abcm2ps-8.14.7/debian/changelog --- abcm2ps-8.14.7/debian/changelog 2020-03-29 18:51:47.0 +0200 +++ abcm2ps-8.14.7/debian/changelog 2020-04-16 18:40:04.0 +0200 @@ -1,3 +1,11 @@ +abcm2ps (8.14.7-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Pass cross tools CC and PKG_CONFIG to ./configure. Closes: #946572. +I have only applied the upstream part of the fix by Helmut Grohne. + + -- Nicolas Boulenguez Thu, 16 Apr 2020 18:40:04 +0200 + abcm2ps (8.14.7-0.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru abcm2ps-8.14.7/debian/rules abcm2ps-8.14.7/debian/rules --- abcm2ps-8.14.7/debian/rules 2020-03-29 18:45:49.0 +0200 +++ abcm2ps-8.14.7/debian/rules 2020-04-16 18:40:04.0 +0200 @@ -2,6 +2,7 @@ DEB_BUILD_MAINT_OPTIONS := hardening=+all DEB_CFLAGS_MAINT_APPEND := -Wall +include /usr/share/dpkg/buildtools.mk include /usr/share/dpkg/buildflags.mk %: @@ -10,4 +11,4 @@ .PHONY: override_dh_auto_configure override_dh_auto_configure: dh_auto_configure -- \ - $(foreach v,CFLAGS CPPFLAGS LDFLAGS,'--$(v)=$($(v))') + $(foreach v,CC PKG_CONFIG CFLAGS CPPFLAGS LDFLAGS,'--$(v)=$($(v))')
Bug#956916: Update libiscsi to 1.19.0
Package: libiscsi Please update libiscsi to 1.19.0. Changelog: https://github.com/sahlberg/libiscsi/blob/4db1e0a46329c27ad05baf6223fca27aeebbef74/packaging/RPM/libiscsi.spec.in#L112 Sun Jul 14 2019: 1.19.0 * iSER improvements * Add support to enable/disable digests via URL arguments * Add XCOPY support to examples/dd * Add support for EXTENDED_COPY and RECEIVE_COPY_RESULTS * Performance improvements for reading from the socket. * Test improvements
Bug#956329: patch
tags 956329 + patch thanks Here's the obvious patch, tested with both remove & purge cases. diff -urpN rasdaemon-0.6.5.orig/debian/rasdaemon.postrm rasdaemon-0.6.5/debian/rasdaemon.postrm --- rasdaemon-0.6.5.orig/debian/rasdaemon.postrm 1969-12-31 17:00:00.0 -0700 +++ rasdaemon-0.6.5/debian/rasdaemon.postrm 2020-04-16 12:16:19.898085730 -0600 @@ -0,0 +1,40 @@ +#!/bin/sh +# postrm script for rasdaemon +# +# see: dh_installdeb(1) + +set -e + +# summary of how this script can be called: +#* `remove' +#* `purge' +#* `upgrade' +#* `failed-upgrade' +#* `abort-install' +#* `abort-install' +#* `abort-upgrade' +#* `disappear' +# +# for details, see https://www.debian.org/doc/debian-policy/ or +# the debian-policy package + + +case "$1" in +purge) + rm -f /var/lib/rasdaemon/ras-mc_event.db +;; +remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) +;; + +*) +echo "postrm called with unknown argument \`$1'" >&2 +exit 1 +;; +esac + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0
Bug#951500: libqt5gui5: crash in QTextEngine after disconnect from the session manager
Hi Jiri, and sorry for the late reply! On Mon, Feb 17, 2020 at 03:09:57PM +0100, Jiri Palecek wrote: > Dear Maintainer, > > after my session manager (ksmserver) probably died, other applications > began crashing as well. Kopete crashed during its closing sequence in > QTextEngine::shapeTextWithHarfbuzzNG. The backtrace is: I looked at the stacktrace, and I could not find any similar bug on Qt bug tracker or anywhere. The affected code also hasn't changed, so presumably Qt 5.15 is still affected. Do you know a way to reliably reproduce this bug? If yes, maybe you can report it upstream to bugreports.qt.io? -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#955812: gedit-latex-plugin does not work anymore
Dear Pietro, I can confirm it works. Many thanks for your help!
Bug#956915: RFS: apngasm/2.91-2 [QA] -- assemble APNG animation from PNG/TGA image sequence
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "apngasm" * Package name: apngasm Version : 2.91-2 Upstream Author : Max Stepin * URL : https://sourceforge.net/projects/apngasm * License : Zlib * Vcs : https://salsa.debian.org/debian/apngasm Section : graphics It builds those binary packages: apngasm - assemble APNG animation from PNG/TGA image sequence To access further information about this package, please visit the following URL: https://mentors.debian.net/package/apngasm Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/apngasm/apngasm_2.91-2.dsc Changes since the last upload: * QA upload. . [ Debian Janitor ] * Use correct machine-readable copyright file URI. * Use secure URI in debian/watch. * Update standards version to 4.4.1, no changes needed. * Set upstream metadata fields: Archive, Bug-Database. . [ Sudip Mukherjee ] * Update Standards-Version to 4.5.0 * Add Rules-Requires-Root: no. -- Regards Sudip
Bug#906072: Ogon packages available (Linux RDP Server)
Hi, I just wanted to let you know about ab packaged version of ogon (https://github.com/ogon-project (https://github.com/ogon-project), a linux Remote Desktop Protocol (RDP) server implementation). https://launchpad.net/~linux-ng/+archive/ubuntu/ogon (https://launchpad.net/~linux-ng/+archive/ubuntu/ogon) Maybe this can make it into Debian and helps to get ogon usable for a wider public. Bye, Marcel
Bug#885433: wiki.debian.org: Access to wiki.debian.org is blocked with 403 Forbidden
Hi, My address also seems to have been blacklisted: 90.120.212.217 I would be really grateful if it could be unblocked. Regards.
Bug#956914: pyee: please upgrade package to upstream 6.0.0 or newer
Source: pyee Version: 3.0.3-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This package is virtually unchanged for 2.5 years, despite upstream having issued 4 major releases since then. Recent releases of janus need python-aiortc for its testsuite, and transitively needs at least version 6.0.0 of python-pyee. Please therefore upgrade to at least version 6.0.0. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6YlEkACgkQLHwxRsGg ASG9/hAAkz3yFAFTZmWaGDp3E+7cihpNqXA54NdKPF0z/TbL6JkXb6qRbPhgadPt KVMfZh/F4K6M7eT9WQI2HZyEEuhYfXFqPKCRQXFGeQVfNP1cY+ZIGgOpJVdpuwcb rr8Z70q3mFsPGXm0FKq9g9eAfi9CaRx4MwiJmZy7JSi1K6W1Hp9QBVHl+dm5qp+I pOb9tfnEx92UhnvubV5CZnK2kzijE8GFAFZ1pqpk1R+LHtAldLoGl27t2iCklx25 Ho6uyWyRYldef29Z3YmLdTfPy/FxqxE4//+AGJcMdWWGISlPQRxfQiQ0ReVgT6Q3 PWJ21oVZC7/nHIsfXeKZGhELfwRJMcJ5teIj/dGMjq3wsahDi440wmJrVhemts5R +0nEeBJTV6hmllur+qf4/WkQu7WYXoOk07cgaz7OmkkASMN3V3GUFe07v3Ny0nZ5 Y2TjRC5ODy7JD4fDCLVdaejnXzAIo6+VlVMp4RFn02YCxb2PeKO8LJC2WD3+w5hC W1dHWnHzExwf8sdPUZEUk56V9KbFGRGbhAhg4G0D/T0YNSGXGN9fOMSnVLuLaegG L+j7FGYNn3t8da8hvqnz9HIf0zBKzStwp4riu8WuixETuVR349XPiur7Baw3jOp4 KJx/MavB8ykYslqG5BHStKnZtkQjvrpvnaprBPAUiMa06Ld/J3o= =8OEI -END PGP SIGNATURE-
Bug#956913: buster-pu: package nvidia-graphics-drivers/418.113-1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to update the non-free nvidia-graphics-drivers in buster from 418.74-1 to 418.113-1. There are a few upstream fixes but no known CVE fixes. The majority of the changes are packaging related ... because the packaging is mainly generated (since we build 4 source packages from it in sid nowadays) and I'd like to keep it in sync to be able to propagate fixes through it without running into a merge nightmare at some point. Most changes were triggered by adding support for the separately packaged Tesla drivers - a huge textual diff (e.g. renaming of variables and substvars from "legacy" to the more generic "variant") without causing differences in the generated binaries. All packaging changes are backports from sid and should be documented in the changelog. (Some documentation changes may not be documented.) Some of these changes were already included in previous point releases when we updated nvidia-graphics-drivers-legacy-340xx for its EoL state. I'd like to include one further change to sync the packaging to sid: shuffling the packages in debian/control from a historically grown order to a more logical grouping. I've omitted this in the proposed debdiff, since it destroys readability of the changes to debian/control. Please see the separate diff that only shuffles the generated d/control (something similar will get applied to d/control.in, too). With these changes I hope to cover most changes to be backported through the bullseye release cycle and further updates will only include new upstream releases (with CVE fixes?) without significant packaging updates. To show the impact on generated binary packages, I'm including a binary debdiff from all+amd64 for 418.74-1 (currently in buster) rebuilt with the proposed changes. (To avoid the version change noise when debdiffing 418.74-1 to 418.113-1.) The proposed package is very similar to src:nvidia-graphics-drivers-tesla-418 in sid and buster-backports. I've excluded all changes that would build packages for ppc64el. I've also excluded a patch for Linux 5.5 support that is a) not needed for buster and b) I'm not confident that it has seen enough testing. (These changes are available via nvidia-graphics-drivers in buster-backports.) I'll propose similar updates for nvidia-graphics-drivers in stretch and nvidia-graphics-drivers-legacy-390xx in buster, but no more changes for EoL-ed nvidia-graphics-drivers-legacy-340xx. Andreas ngd-418.113-1.buster.diff.xz Description: application/xz ngd-418.113-1.shuffle-control.diff.xz Description: application/xz ngd-418.113-1.binary.418.74-1.debdiff.xz Description: application/xz
Bug#886512: broadcom-sta-dkms: /bin/sh: 1: [: Illegal number:
control: tags -1 +patch +pending
Bug#886512: broadcom-sta-dkms: /bin/sh: 1: [: Illegal number:
control: tags +patch +pending finally I found what's the problem, and here is enclosed the patch. -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 From: Roger Shimizu Date: Fri, 17 Apr 2020 00:08:34 +0900 Subject: Parse KERNELRELEASE into VERSION, PATCHLEVEL, and SUBLEVEL This fixes build error message: /bin/sh: 1: [: Illegal number: /bin/sh: 1: [: Illegal number: Wireless Extension is the only possible API for this kernel version Using Wireless Extension API Closes: #886512 --- amd64/Makefile | 4 i386/Makefile | 4 2 files changed, 8 insertions(+) diff --git a/amd64/Makefile b/amd64/Makefile index 994a146..ed16dfc 100644 --- a/amd64/Makefile +++ b/amd64/Makefile @@ -20,6 +20,10 @@ ifneq ($(KERNELRELEASE),) + VERSION := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\1/') + PATCHLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\2/') + SUBLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\3/') + LINUXVER_GOODFOR_CFG80211:=$(strip $(shell \ if [ "$(VERSION)" -ge "2" -a "$(PATCHLEVEL)" -ge "6" -a "$(SUBLEVEL)" -ge "32" -o "$(VERSION)" -ge "3" ]; then \ echo TRUE; \ diff --git a/i386/Makefile b/i386/Makefile index a323a0d..ec947d9 100644 --- a/i386/Makefile +++ b/i386/Makefile @@ -20,6 +20,10 @@ ifneq ($(KERNELRELEASE),) + VERSION := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\1/') + PATCHLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\2/') + SUBLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\3/') + LINUXVER_GOODFOR_CFG80211:=$(strip $(shell \ if [ "$(VERSION)" -ge "2" -a "$(PATCHLEVEL)" -ge "6" -a "$(SUBLEVEL)" -ge "32" -o "$(VERSION)" -ge "3" ]; then \ echo TRUE; \
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 solved the problem. -- Julio C. Ortega
Bug#956912: ITP: golang-github-davecgh-go-spew -- Implements a deep pretty printer for Go data structures to aid in debugging
Package: wnpp Severity: wishlist Owner: Manas Kashyap * Package name: golang-github-davecgh-go-spew Version : 1.1.1-1 Upstream Author : Dave Collins * URL : https://github.com/davecgh/go-spew * License : ISC Programming Lang: Go Description : Implements a deep pretty printer for Go data structures to aid in debugging Go-spew implements a deep pretty printer for Go data structures to aid in debugging. . A comprehensive suite of tests with 100% test coverage is provided to ensure proper functionality. . It is a dependency of gitlab-shell
Bug#956911: ITP: mercantile -- Spherical mercator coordinate and tile utilities for web mercator XYZ tiles
Package: wnpp Severity: wishlist Owner: Joachim Langenbach -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: mercantile Version : 1.1.3 Upstream Author : Sean Gillies * URL : https://github.com/mapbox/mercantile * License : BSD-3-clause Programming Lang: Python Description : Spherical mercator coordinate and tile utilities for web mercator XYZ tiles Spherical mercator coordinate and tile utilities Documentation: http://mercantile.readthedocs.io/en/latest/ The mercantile module provides ``ul(xtile, ytile, zoom)`` and ``bounds(xtile, ytile, zoom)`` functions that respectively return the upper left corner and bounding longitudes and latitudes for XYZ tiles, a ``xy(lng, lat)`` function that returns spherical mercator x and y coordinates, a ``tile(lng, lat, zoom)`` function that returns the tile containing a given point, and quadkey conversion functions ``quadkey(xtile, ytile, zoom)`` and ``quadkey_to_tile(quadkey)`` for translating between quadkey and tile coordinates. Also in mercantile are functions to traverse the tile stack. Named tuples are used to represent tiles, coordinates, and bounding boxes. I use this library in my project and find it very useful to transform between XYZ coordinates and latitude / longitude coordinates. So I think, many other users find it useful also. I would be very happy to find a sponsor uploading this package. I already packaged it and will upload it to debian mentors referencing this Bug report in the changelog. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE7rN7YxAGj/5T5nRYORUhb9eUwC4FAl6Yg0AACgkQORUhb9eU wC4rCg//Tox9AcInyvrH7qG/kle+uxYGFkPxqDYcTfTxuJSzu4UsPFAW8tKczjOl W/YDbV9vuPJsXCy/q+MuQS2vfzTgxBl9GMXjgbjxkN5l/JXxrNUEQZoT5+XG3rDM 1Z4IyqvLCJFZdYNeleGccl9a1jUabrFUS445jamEWaTJqoqOTGzkUWSDwBaBAzcJ csBq95YAj4g17u/W9N6EzKKECGJ018pTxtK+5LVN2m4GqAUGa20Um89fbv5KdYZz 30h876gWSftSyK68Ed+by7w0dg7rj7xtO7BAMMUj44dglYo9cBNRFZTi46e80trl 2TNT6d7sLSr1IkOk5y6Wrszx3jf2a7Yp3BfHTkerD4HAnSIEsIN+T1j1tC1hvsxc pmxNem89jdu8ppD231OoTjeD++2vrfLM/kGTIuQyHlBxHhEUMsny49enRl2BUgc2 J+/N7/1H2GneR4hBEUu/a5EsTGEQ4YwmqqeyUNLKZHYbt0x0oL5uosMeLps6mUCo srnREO0p0YkjfKj4khCWYYlkzGeeI40D1OcY9mPCcPRJAh9NG4fXyjGGXF5ADCOz rpyoY2HdiGa81Igcfte6Jr7/3we29rjVwR1Gd5bV9VdQYyJeTsSpeJs10HReQjrA lu0ds2TxjEEY08VWlWfXGd++wHa1NDv6Qhkog5mkc4eqpSl0Fi8= =KgAA -END PGP SIGNATURE-
Bug#955812: gedit-latex-plugin does not work anymore
Il giorno dom, 12/04/2020 alle 18.12 +0200, Maurizio Quadrio ha scritto: > > [...] > if BENCHMARK: t = time.clock() > AttributeError: module 'time' has no attribute 'clock' This (and the other AttributeError that followed) should be fixed by https://gitlab.gnome.org/GNOME/gedit-latex/-/commit/0cf04556eeb3f35084051d5ec98c345432a838fe ... but you might need to also apply https://gitlab.gnome.org/GNOME/gedit-latex/-/commit/959755c21d9909dafdd639455a1e621063b9c633 Then the plugin should work again. I plan to create a release and the new Debian package in the next days. Pietro
Bug#956858: firmware-b43-installer.postinst returns with error
Package: firmware-b43-installer Version: 1:019-5 Followup-For: Bug #956858 Dear Maintainer, Same here. I want to add that there complete error message is: rm: das Entfernen von '/lib/firmware/b43/n16bsinitvals30.fw' ist nicht möglich: Datei oder Verzeichnis nicht gefunden rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden which is repeated about 30 times. The first part seems to refer to an old version which can't be found. The second part seams to indicate a scripting error: 'passt' is german for "(sth) fits". This doesn't seam to be the name of a file, but part of a describing text. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.4-towo.1-siduction-amd64 (SMP w/2 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firmware-b43-installer depends on: ii b43-fwcutter 1:019-5 ii bzip21.0.8-2 ii ca-certificates 20190110 ii wget 1.20.3-1+b2 firmware-b43-installer recommends no packages. firmware-b43-installer suggests no packages. -- no debconf information
Bug#956885: The same happened to me
I installed lightdm and could login into openbox, I had openbox previously installed. Disabling Wayland in /etc/gdm3/daemon.conf didn't work, in fact it was worse because could not open another terminal with Control+Alt+F2. I had to enter recovery mode to enable Wayland again. Regards, Alvaro
Bug#956530: Increasing severity
Control: severity -1 serious Hi! This is considered a serious bug, so increasing the severity. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration
Am 16.04.20 um 17:18 schrieb Bernhard Schmidt: Am 16.04.20 um 17:11 schrieb sauro...@gmx.de: Hi, Well at least i thought that this would let me on Squeeze, but i was wrong Could you please rephrase your question? BTW, Squeeze is Debian 6 and out of LTS since 2016. I assume you mean Stretch aka Debian 9? Bernhard Yes Stretch was what i meant, sorry. I don´t have any further questions, at the beginning i was thinking that this bug prevent me from upgrading to Buster, but in fact it has nothing to do with it. Nevertheless i think when you upgrade from 9 to 10 the "sites-available" folder disappears on any machine which causes freeradius to not start. Best regards!
Bug#955432: gnome-shell-xrdesktop: FTBFS: dh_missing: warning: usr/share/bash-completion/completions/gnome-extensions exists in debian/tmp but is not installed to anywhere
Package: gnome-shell-xrdesktop Followup-For: Bug #955432 I have prepared version 3.36.1-1 in NEW which includes the commit already. Let's see if it builds on buildd. Best regards, -Andrew
Bug#956907: RFS: ace/6.5.8+dfsg-1 [RC] -- makefile, project, and workspace creator
Control: tags -1 moreinfo Hi Sudip, here's a review, no specific order: - it seems that there is an ABI bump in the libraries (as packages get renamed and so on…). Please target "experimental" for this upload, as this will trigger an transistion [1] and also needs to clear "NEW". - d/copyright needs some years updated. Bonus points for converting it to dep5 (its almost already dep5, so likely quickly converted) [1] https://wiki.debian.org/Teams/ReleaseTeam/Transitions - you should probably close #878198; I see the change but it is not mentioned in the changelog. - you should probably also close #954252 (at least the bts says it is fixed by the new upstream version) Regarding the symbols: Be aware that symbols are tricky for C++ code, especially for different architectures… Lets see and wait how it turns out, but do not hesitate to undo that if you feel it becomes a burden. -- tobi
Bug#740601: blat_35-1_amd64.changes REJECTED
rejecting for now and waiting for updated license from upstream ... === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration
Am 16.04.20 um 17:11 schrieb sauro...@gmx.de: Hi, > Well at least i thought that this would let me on Squeeze, but i was wrong Could you please rephrase your question? BTW, Squeeze is Debian 6 and out of LTS since 2016. I assume you mean Stretch aka Debian 9? Bernhard
Bug#956910: gnome-shell: System hangs with GnomeDesktop:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Control: reassign -1 libgnome-desktop-3-18 Control: affects -1 + gnome-shell gnome gdm3 On Thu, 16 Apr 2020 at 16:54:25 +0200, Gert van de Kraats wrote: > After today's upgrade the system hangs with > > GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: > assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)). This is a known transitional problem during the upgrade from GNOME Shell and gnome-desktop3 3.34.x to 3.36.x. It will be resolved when the transition finishes (probably sometime in the next 1 to 2 days), but there is nothing that the maintainers of individual packages can do about it right now. Either hold/downgrade related packages to the versions that depend on libgnome-desktop-3-18 for now, or upgrade selected packages to their versions from unstable so that everything depends on libgnome-desktop-3-19. smcv
Bug#956894: upgrade-reports: display of gnome login screen failed /gnome crashes after applying dist-upgrade on 16th of April 2020
Control: reassign -1 libgnome-desktop-3-18 Control: affects -1 + gnome gnome-shell gdm3 Control: tags -1 = bullseye On Thu, 16 Apr 2020 at 15:56:33 +0200, Bill Allombert wrote: > On Thu, Apr 16, 2020 at 02:30:46PM +0200, Dennis wrote: > >Can not register existing type 'GnomeBGSlideShow' This is caused by the ongoing library transition from libgnome-desktop-3-18 to libgnome-desktop-3-19 (#954422), which should sort itself out soon when all packages involved have been rebuilt with a consistent version. I'll merge the various duplicate bugs when new ones stop arriving. smcv
Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration
Well at least i thought that this would let me on Squeeze, but i was wrong. I´ve did the upgrade to Buster today now on two machines, both with the following result. After upgrading freeradius wouldn´t start, so i looked into it and found out that somehow the folder: /etc/freeradius/3.0/sites-available was gone after the upgrade. Actually that caused the software to not start. I did a fresh Buster installation then, copied the folder and files to my old machines, changed the owner of the folder to "freerad" and now it´s up and running again. Im not really qualified i think to answer your question and though as you can read im not an Freeradius expert. Thanks for your input!
Bug#956908: scilab: Fail to run: null pointer
Package: scilab Version: 6.1.0+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, scilab crash at start: Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Could not access to the Main Scilab Class: Exception in thread "main" java.lang.ExceptionInInitializerError at org.scilab.modules.localization.Messages.gettext(Unknown Source) at org.scilab.modules.commons.xml.XConfiguration.(Unknown Source) at org.scilab.modules.core.Scilab.(Unknown Source) Caused by: java.lang.NullPointerException at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2646) at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:830) at java.base/java.lang.System.loadLibrary(System.java:1870) at org.scilab.modules.localization.MessagesJNI.(Unknown Source) ... 3 more Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available). Bastien -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-rt-amd64 (SMP w/4 CPU cores; PREEMPT) 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 /bin/dash Init: systemd (via
Bug#956909: ITP: golang-github-cilium-ebpf -- eBPF Library for Go
Package: wnpp Severity: wishlist Owner: Shengjing Zhu * Package name: golang-github-cilium-ebpf Version : 0.0~git20200413.48fb86d-1 Upstream Author : Cilium * URL : https://github.com/cilium/ebpf * License : Expat Programming Lang: Go Description : eBPF Library for Go eBPF is a pure Go library that provides utilities for loading, compiling, and debugging eBPF programs. It has minimal external dependencies and is intended to be used in long running processes.
Bug#956910: gnome-shell: System hangs with GnomeDesktop:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Package: gnome-shell Version: 3.34.4-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After today's upgrade the system hangs with GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)). This happens with and without wayland. The gnome-shell errors about OpenGL and glamor and keymap are normal. Apr 16 10:43:21 debian gnome-shell[838]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs Apr 16 10:43:21 debian gnome-shell[838]: Failed to find schema: org.gnome.settings-daemon.plugins.xsettings Apr 16 10:43:23 debian gnome-shell[838]: can't load /usr/lib/i386-linux-gnu/spa/support/libspa-support.so: /usr/lib/i386-linux-gnu/spa/support/libspa-support.so: cannot open shared object file: No such file or directory Apr 16 10:43:24 debian gnome-shell[910]: Require OpenGL version 2.1 or later. Apr 16 10:43:24 debian gnome-shell[910]: Failed to initialize glamor Apr 16 10:43:24 debian gnome-shell[910]: Failed to initialize glamor, falling back to sw Apr 16 10:43:24 debian snapd[468]: daemon.go:539: gracefully waiting for running hooks Apr 16 10:43:24 debian snapd[468]: daemon.go:541: done waiting for running hooks Apr 16 10:43:24 debian snapd[468]: daemon stop requested to wait for socket activation Apr 16 10:43:24 debian systemd[1]: snapd.service: Succeeded. Apr 16 10:43:27 debian dbus-daemon[753]: [session uid=117 pid=753] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.3' (uid=117 pid=749 comm="/usr/libexec/tracker-extract ") Apr 16 10:43:27 debian systemd[648]: Starting Virtual filesystem metadata service... Apr 16 10:43:27 debian dbus-daemon[753]: [session uid=117 pid=753] Successfully activated service 'org.gtk.vfs.Metadata' Apr 16 10:43:27 debian systemd[648]: Started Virtual filesystem metadata service. Apr 16 10:43:28 debian gnome-shell[922]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 16 10:43:28 debian gnome-shell[922]: > Internal error: Could not resolve keysym XF86FullScreen Apr 16 10:43:28 debian gnome-shell[922]: Errors from xkbcomp are not fatal to the X server Apr 16 10:43:28 debian dbus-daemon[753]: [session uid=117 pid=753] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.24' (uid=117 pid=838 comm="/usr/bin/gnome-shell ") Apr 16 10:43:28 debian systemd[648]: Starting Accessibility services bus... Apr 16 10:43:28 debian dbus-daemon[753]: [session uid=117 pid=753] Successfully activated service 'org.a11y.Bus' Apr 16 10:43:28 debian systemd[648]: Started Accessibility services bus. Apr 16 10:43:34 debian gnome-shell[838]: cannot register existing type 'GnomeBGSlideShow' Apr 16 10:43:34 debian gnome-shell[838]: cannot add private field to invalid (non-instantiatable) type '' Apr 16 10:43:34 debian gnome-shell[838]: ** Apr 16 10:43:34 debian gnome-shell[838]: GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)) Apr 16 10:43:34 debian gnome-shell[838]: Bail out! GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)) Apr 16 10:43:34 debian gnome-shell[838]: == Stack trace for context 0x1c70be0 == Apr 16 10:43:34 debian gnome-shell[838]: #0 1f66cf8 i resource:///org/gnome/shell/ui/background.js:636 (abfb7a10 @ 47) Apr 16 10:43:34 debian gnome-shell[838]: #1 1f66c80 i resource:///org/gnome/shell/ui/background.js:177 (abfb2d30 @ 316) Apr 16 10:43:34 debian gnome-shell[838]: #2 1f66c18 i resource:///org/gnome/shell/ui/background.js:444 (abfb7560 @ 70) Apr 16 10:43:34 debian gnome-shell[838]: #3 1f66bb0 i resource:///org/gnome/shell/ui/background.js:479 (abfb76a0 @ 58) Apr 16 10:43:34 debian gnome-shell[838]: #4 1f66b48 i resource:///org/gnome/shell/ui/background.js:494 (abfb76f0 @ 106) Apr 16 10:43:34 debian gnome-shell[838]: #5 1f66ac0 i resource:///org/gnome/shell/ui/background.js:261 (abfb2f10 @ 501) Apr 16 10:43:34 debian gnome-shell[838]: #6 1f66a38 i resource:///org/gnome/shell/ui/background.js:590 (abfb78d0 @ 426) Apr 16 10:43:34 debian gnome-shell[838]: #7 1f669c8 i resource:///org/gnome/shell/ui/background.js:751 (abfb7ce0 @ 39) Apr 16 10:43:34 debian gnome-shell[838]: #8 1f66948 i resource:///org/gnome/shell/ui/background.js:687 (abfb7b00 @ 269) Apr 16 10:43:34 debian gnome-shell[838]: #9 1f668c0 i resource:///org/gnome/shell/ui/screenShield.js:601 (abbf4880 @ 191) Apr 16 10:43:34 debian gnome-shell[838]: #10 1f66850 i resource:///org/gnome/shell/ui/screenShield.js:619 (abbf48d0 @ 181) Apr 16 10:43:34 debian gnome-shell[838]: #11 1f667b8 i resource:///org/gnome/shell/ui/screenShield.js:467 (abbf45b0 @
Bug#956894: work-around
Same issue. work-around: Boot into recovery mode, install alternative Desktop Environment and Display Manager E.g.: apt install lxde-core select alternative Display Manager when asked, reboot, select alternative Desktop Environment in greeter and login Best regards, Peter
Bug#956890: buster-pu: package zfs-linux/0.7.12-2+deb10u2
Control: tags -1 + moreinfo Control: tags 956889 + moreinfo On Thu, 2020-04-16 at 11:26 +, Mo Zhou wrote: > (please explain the reason for this update here) > > We need to cherry-pick two patches in order to fix a deadlock issue > for zfs > https://github.com/openzfs/zfs/commit/98bb45e27ae80145a6ce028df90fccdb23f8901d > https://github.com/openzfs/zfs/commit/01937958ce85b1cd8942dbaf9a3f9768c5b02a0a > > And the two patches have to be used in conjunction with a patch for > src:spl-linux > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932251 > (I'm uploading shortly) I'm afraid I'm slightly confused here. You've filed two copies of this bug, with slightly different content. Neither of them has a proposed diff attached, and they both claim to be requesting updates for the "zfs-linux" package, but the upload you've made is for the "spl-linux" package, for which there appears to be no p-u bug. Please could you clarify? Regards, Adam
Bug#931930: Workaround ? [Re: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin]
I follow testing, and I have the same problem : charpent@zen-book-flip:~/Kernel-SOS/firmware-nonfree-20190717/i915$ dpkg -l "*firmware*" | grep ii| sed -re "s/[ \t]+/ /g" | cut -d " " -f 2 | xargs sudo apt-get install --reinstall -y [ Snip... ] Traitement des actions différées (« triggers ») pour initramfs-tools (0.136) ... update-initramfs: Generating /boot/initrd.img-5.5.0-1-amd64 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.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/skl_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 Does someone has a workaround ? The Debian source package doesn't have the right version of the files. BTW, do the maintainer(s) have acknowledged the problem ? -- Emmanuel Charpentier
Bug#956907: RFS: ace/6.5.8+dfsg-1 [RC] -- makefile, project, and workspace creator
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "ace" * Package name: ace Version : 6.5.8+dfsg-1 Upstream Author : Douglas C. Schmidt * URL : https://www.dre.vanderbilt.edu/~schmidt/ACE.html * License : * Vcs : https://salsa.debian.org/debian/ace Section : devel It builds those binary packages: mpc-ace - makefile, project, and workspace creator libace-6.5.8 - C++ network programming framework libace-dev - C++ network programming framework - development files libace-doc - C++ network programming framework - documentation libace-ssl-6.5.8 - ACE secure socket layer library libace-ssl-dev - ACE secure socket layer library - development files libace-rmcast-6.5.8 - ACE reliable multicast library libace-rmcast-dev - ACE reliable multicast library - development files libace-tmcast-6.5.8 - ACE transactional multicast library libace-tmcast-dev - ACE transactional multicast library - development files libace-htbp-6.5.8 - ACE protocol over HTTP tunneling library libace-htbp-dev - ACE protocol over HTTP tunneling library - development files libace-inet-6.5.8 - ACE Inet protocol library libace-inet-dev - ACE Inet protocol library - development files libace-inet-ssl-6.5.8 - ACE SSL-enabled Inet protocol library libace-inet-ssl-dev - ACE SSL-enabled Inet protocol library - development files ace-gperf - ACE perfect hash function generator libacexml-6.5.8 - ACE SAX based XML parsing library libacexml-dev - ACE SAX based XML parsing library - development files libace-xml-utils-6.5.8 - ACE XML utility classes and methods libace-xml-utils-dev - ACE XML utility classes and methods - development files libkokyu-6.5.8 - ACE scheduling and dispatching library libkokyu-dev - ACE scheduling and dispatching library - development files libace-xtreactor-6.5.8 - ACE-GUI reactor integration for Xt libace-xtreactor-dev - ACE-GUI reactor integration for Xt - development files libace-tkreactor-6.5.8 - ACE-GUI reactor integration for Tk libace-tkreactor-dev - ACE-GUI reactor integration for Tk - development files libace-flreactor-6.5.8 - ACE-GUI reactor integration for FLTK libace-flreactor-dev - ACE-GUI reactor integration for FLTK - development files libace-foxreactor-6.5.8 - ACE-GUI reactor integration for FOX libace-foxreactor-dev - ACE-GUI reactor integration for FOX - development files ace-netsvcs - ACE network service implementations libnetsvcs-6.5.8 - ACE network service implementations - libraries libnetsvcs-dev - ACE network service implementations - development files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ace Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/ace/ace_6.5.8+dfsg-1.dsc Changes since the last upload: * Team upload. * Update to upstream v6.5.8 - Remove old patches applied upstream. - Use debian/* from upstream. * Update Standards-Version to 4.5.0 * Use debhelper-compat. - Update compat level to 12. * Update debian/rules. - Remove --list-missing. - Add -g for debug symbols. - Stop modifying flags directly. - Install shared library in multiarch location. - Remove LD_LIBRARY_PATH. * Add symbols files. * Update doc-base location. * Remove lintian overrides. - for symbols. - for debhelper. * Update maintainer to valid team email. (Closes: #899440) * Update Vcs link to salsa. Note: 1. Has been tested with ratt. 2. One of the uploader - "Thomas Girard" is not replying to mails, and Johny (the other uploader) is from upstream and has asked me to do the update as he is not aware of Debian process. 3. Upstream repo provides the debian/* files. The changes I did for this update has been merged upstream to ease the process for next upstream release. -- Regards Sudip
Bug#956906: ITP: golang-gopkg-gorp.v1 -- Go Relational Persistence - an ORM-ish library for Go
Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org * Package name : golang-gopkg-gorp.v1 Version : 1.7.2-1 Upstream Author : * URL : https://github.com/go-gorp/gorp * License : Expat Programming Lang: Go Description : Go Relational Persistence - an ORM-ish library for Go This is a build dependnecy of gitaly.
Bug#956896: Bug fixes with packages from unstable
Hi, You were right. Just installing gnome-shell and it's dependencies from unstable fixed this issue. Feel free to close the bug as it'll get fixed once the new version migrates to testing. Thanks for helping me.
Bug#956903: clang-tidy-6.0: Depends on cruft package python-yaml
Hello Le 16/04/2020 à 15:35, Scott Kitterman a écrit : Package: clang-tidy-6.0 Version: 1:6.0.1-14 Severity: serious The clang-tidy-6.0 package depends on python-yaml, which is now NBS and will be removed from Testing at some point. I understand that llvm 6.0 is sticking around to support ghc, but is clang-tidy needed for that? If that binary could be dropped it would help with moving the python2-rm transition forward. afaik, ghc only needs llvm. All the other packages could be removed. However, not planning to spend time on this myself. llvm-toolchain-6 should be just removed... Cheers, Sylvestre
Bug#956894: upgrade-reports: display of gnome login screen failed /gnome crashes after applying dist-upgrade on 16th of April 2020
reassign gnome-shell quit On Thu, Apr 16, 2020 at 02:30:46PM +0200, Dennis wrote: > Package: upgrade-reports > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >Since today's dist-upgrade Gnome does not start to lock screen and crashes > before. Graphical error message is displayed. > >* What exactly did you do (or not do) that was effective (or > ineffective)? >Checked journalctl /usr/bin/gnome-shell(-session) logs for gnome realted > issues: Since the update I see a assertion failed for > "gnome_bg_slide_show_set_property" in "gnome-bg-slide_show.c:83" >g_once_init_leave: assertion: 'result!=0' failed >Can not register existing type 'GnomeBGSlideShow' > >* What was the outcome of this action? >I have not taken any action yet as I currently don't exactly know why this > issue occures > >* What outcome did you expect instead? > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), > LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled
Bug#956905: Cyrus SASL: please make NTLMv2 the default
Package: libsasl2-modules
Version: 2.1.27+dfsg-1+deb10u1
Severity: wishlist
Tags: patch
The NTLM plugin defaults to the less-secure v1 of the protocol, does not
support a way for clients to override this default (this is tracked upstream
as https://github.com/cyrusimap/cyrus-sasl/issues/574), and will not even
attempt v2 if v1 fails (e.g., due to it being disabled server-side).
As a workaround until a better fix is available, I've applied the attached
patch (which is a variation on the proof of concept at
https://access.redhat.com/solutions/4253821). Since in this day and age
it makes more sense to prefer NTLMv2 (if NTLM is to be used at all),
I'm submitting it for the maintainers' consideration.
Default to ntlm_v2=yes.
See https://github.com/cyrusimap/cyrus-sasl/issues/574 and
https://bugzilla.redhat.com/show_bug.cgi?id=1722159
We definitely should prefer NTLMv2 over v1.
--- a/plugins/ntlm.c
+++ b/plugins/ntlm.c
@@ -1993,7 +1993,7 @@
unsigned char hash[NTLM_HASH_LENGTH];
unsigned char resp[NTLM_RESP_LENGTH], *lm_resp = NULL, *nt_resp = NULL;
int result;
-const char *sendv2;
+const char *sendv2 = NULL;
if (!serverin || serverinlen < NTLM_TYPE2_MINSIZE ||
memcmp(serverin, NTLM_SIGNATURE, sizeof(NTLM_SIGNATURE)) ||
@@ -2065,7 +2065,7 @@
/* should we send a NTLMv2 response? */
params->utils->getopt(params->utils->getopt_context,
"NTLM", "ntlm_v2", , NULL);
-if (sendv2 &&
+if (!sendv2 ||
(sendv2[0] == '1' || sendv2[0] == 'y' ||
(sendv2[0] == 'o' && sendv2[1] == 'n') || sendv2[0] == 't')) {
Bug#956904: vokoscreen-ng: upstream provides a new .desktop file
Package: vokoscreen-ng Severity: minor The upstream is providing a new .desktop file in src/applications/. Eriberto
