Bug#956877: marked as done (release-notes: Upgrade from XFS removes mount option "barrier|nobarrier")
Your message dated Sun, 14 Mar 2021 07:52:47 +0100 with message-id <878957ec-c025-ceb8-1954-a7169609e...@debian.org> and subject line Re: Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier" has caused the Debian Bug report #956877, regarding release-notes: Upgrade from XFS removes mount option "barrier|nobarrier" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 956877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release-notes Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** While doing an upgrade from Stretch to Buster on a Laptop with XFS Filesystem in use. After the upgrade the laptop doesn't boot into the system because of the removed "barrier|nobarrier" mount option for XFS in version 4.19. I think this issue should be mentioned in the "5. Issues to be aware of for buster" part of the release-notes in Buster. -- System Information: Debian Release: 9.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-0.bpo.6-amd64 (SMP w/32 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.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) -- Benedikt Tuchen | https://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner --- End Message --- --- Begin Message --- Hi On 14-03-2021 06:52, Justin B Rye wrote: > Make that > presence of either keyword and remove it. XFS will fail to start > ^ ^ > And I'm not sure about "start"... maybe it should be swapped around to > "Partitions using these options will fail to mount". Thanks, applied. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#826168: marked as done (support bitcoin exchange rates)
Your message dated Sat, 13 Mar 2021 23:21:03 + with message-id <20210313232103.ga18...@mithrandir.lan.emorrp1.name> and subject line Fw: Mark 826168 as fixed in experimental/2.2.1-1 has caused the Debian Bug report #826168, regarding support bitcoin exchange rates to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 826168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qalculate Version: 0.9.7-6 Severity: wishlist I use qalculate for everything! It's great. Unfortunately, it doesn't support converting to and from the bitcoin currency. This is because the central european bank exchange rates do not support the currency (yet?): http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml could it be possible to also support bitcoins there, maybe through another data source? -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-0.bpo.2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qalculate depends on: ii qalculate-gtk 0.9.7-6 qalculate recommends no packages. qalculate suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- > # according to upstream[1], this was added in version 2.2.0 > fixed 826168 2.2.1-1 > thanks > > [1]: https://github.com/Qalculate/qalculate-gtk/releases/tag/v2.2.0 signature.asc Description: PGP signature --- End Message ---
Bug#597855: marked as done (..bad ~/.qalculate/eurofxref-daily.xml, no recovery hints found)
Your message dated Sat, 13 Mar 2021 22:55:02 + with message-id <20210313225502.ga32...@mithrandir.lan.emorrp1.name> and subject line closing, cannot reproduce has caused the Debian Bug report #597855, regarding ..bad ~/.qalculate/eurofxref-daily.xml, no recovery hints found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 597855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qalc Version: 0.9.7-4 Severity: normal ...qalc, wget etc works behind a proxy server and needs a "unset http_proxy&&" prefix which I forgot and which had qalc whine about not getting the new rates (from wget). ...so I got tired of these: arnt@a45:/tmp $ qalc 2+2 /home/arnt/.qalculate/eurofxref-daily.xml:1: parser error : Document is empty ^ /home/arnt/.qalculate/eurofxref-daily.xml:1: parser error : Start tag expected, '<' not found ^ /home/arnt/.qalculate/eurofxref-daily.xml:1: parser error : Document is empty ^ /home/arnt/.qalculate/eurofxref-daily.xml:1: parser error : Start tag expected, '<' not found ^ 2 + 2 = 4 ...docs and Google are silent on ~/.qalculate/eurofxref-daily.xml, fooling around, I found a _bad_ "workaound": arnt@a45:/tmp $ cat /home/arnt/.qalculate/definitions/units.xml >/home/arnt/.qalculate/eurofxref-daily.xml arnt@a45:/tmp $ qalc 2+2 2 + 2 = 4 arnt@a45:/tmp $ arnt@a45:/tmp $ ll -R /home/arnt/.qalculate/ /home/arnt/.qalculate/: total 40 drwx-- 3 arnt arnt 4096 2004-10-27 00:12 definitions -rw-r--r-- 1 arnt arnt 51 2010-09-23 13:17 eurofxref-daily.xml -rw-r--r-- 1 arnt arnt 1132 2010-09-23 13:17 qalc.cfg -rw--- 1 arnt arnt 1096 2010-09-23 13:15 qalc.history -rw-r--r-- 1 arnt arnt 5321 2010-09-23 13:17 qalculate-gtk.cfg -rw-r--r-- 1 arnt arnt 8423 2010-07-11 13:49 qalculate-kde.cfg drwx-- 2 arnt arnt 4096 2006-11-15 21:52 tmp /home/arnt/.qalculate/definitions: total 20 drwx-- 2 arnt arnt 4096 2004-10-27 00:12 datasets -rw-r--r-- 1 arnt arnt 51 2010-09-23 13:15 datasets.xml -rw-r--r-- 1 arnt arnt 51 2010-09-23 13:15 functions.xml -rw-r--r-- 1 arnt arnt 51 2010-09-23 13:15 units.xml -rw-r--r-- 1 arnt arnt 51 2010-09-23 13:15 variables.xml /home/arnt/.qalculate/definitions/datasets: total 0 /home/arnt/.qalculate/tmp: total 4 -rw-r--r-- 1 arnt arnt 232 2006-11-15 21:52 divline.png arnt@a45:/tmp $ -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.35-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qalc depends on: ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libcln6 1.3.1-2 Class Library for Numbers (C++) ii libgcc1 1:4.5-20100321-1 GCC support library ii libglib2.0-02.24.2-1 The GLib library of C routines ii libncurses5 5.7+20100313-3 shared libraries for terminal hand ii libqalculate5 0.9.7-4 Powerful and easy to use desktop c ii libreadline66.1-3GNU readline and history libraries ii libstdc++6 4.5-20100321-1 The GNU Standard C++ Library v3 ii libxml2 2.7.7.dfsg-4 GNOME XML library Versions of packages qalc recommends: ii libgnomevfs2-common 1:2.24.3-1 GNOME Virtual File System (common ii wget 1.12-2.1 retrieves files from the web qalc suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- A decade later and I cannot reproduce an http_proxy error on current buster. Presumed fixed by first upload of 2.2.1-1, I don't believe keeping this open with moreinfo is going to achieve anything. signature.asc Description: PGP signature --- End Message ---
Bug#984542: marked as done (psgml: fails to upgrade from 'buster': install: 'psgml-api.elc' and '/usr/share/emacs/site-lisp/psgml/psgml-api.elc' are the same file)
Your message dated Sat, 13 Mar 2021 22:48:40 + with message-id and subject line Bug#984542: fixed in psgml 1.4.0-10 has caused the Debian Bug report #984542, regarding psgml: fails to upgrade from 'buster': install: 'psgml-api.elc' and '/usr/share/emacs/site-lisp/psgml/psgml-api.elc' are the same file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: psgml Version: 1.4.0-9 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. >From the attached log (scroll to the bottom...): Setting up psgml (1.4.0-9) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install psgml for emacs install/psgml: Byte-compiling for emacs...Loading /etc/emacs/site-start.d/00debian.el (source)... In toplevel form: psgml.el:60:30:Warning: Package cl is deprecated psgml.el:719:26:Warning: (lambda (foo) ...) quoted with ' rather than with #' In sgml-mode: psgml.el:1225:52:Warning: assignment to free variable `which-func-format' In sgml-set-buffer-multibyte: psgml-parse.el:365:16:Warning: assignment to free variable `mc-flag' In sgml-set-active-dtd-indicator: psgml-parse.el:2898:47:Warning: assignment to free variable `which-func-mode' In sgml-kill-markup: psgml-edit.el:247:4:Warning: value returned from (/= 0 (skip-chars-forward " ")) is unused psgml-edit.el:247:4:Warning: value returned from (= 0 (skip-chars-forward " ")) is unused psgml-edit.el:247:4:Warning: value returned from (= (skip-chars-forward " ") 0) is unused In sgml-edit-external-entity: psgml-edit.el:1975:62:Warning: Use `with-current-buffer' rather than save-excursion+set-buffer In sgml-append-to-help-buffer: psgml-edit.el:2177:36:Warning: Use `with-current-buffer' rather than save-excursion+set-buffer In sgml-show-structure: psgml-edit.el:2412:6:Warning: Use `with-current-buffer' rather than save-excursion+set-buffer In end of data: psgml-edit.el:2475:1:Warning: the following functions are not known to be defined: string-to-int, process-kill-without-query In sgml-parse-entity-type: psgml-dtd.el:646:8:Warning: value returned from (/= 0 (skip-chars-forward " ")) is unused psgml-dtd.el:646:8:Warning: value returned from (= 0 (skip-chars-forward " ")) is unused psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward " ") 0) is unused psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward " ") 0) is unused psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward " ") 0) is unused In sgml-write-dtd: psgml-dtd.el:1010:9:Warning: assignment to free variable `file-type' In end of data: psgml-dtd.el:1016:1:Warning: the function `string-to-int' is not known to be defined. Done compiling install: 'psgml-api.elc' and '/usr/share/emacs/site-lisp/psgml/psgml-api.elc' are the same file ERROR: install script from psgml package failed dpkg: error processing package psgml (--configure): installed psgml package post-installation script subprocess returned error exit status 1 Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1) ... Errors were encountered while processing: psgml cheers, Andreas psgml_1.4.0-9.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: psgml Source-Version: 1.4.0-10 Done: Neil Roeth We believe that the bug you reported is fixed in the latest version of psgml, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Roeth (supplier of updated psgml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 17:28:23 -0500 Source: psgml
Bug#452498: marked as done (qalculate-kde: Broken conversion from Celsius to Kelvin if temperature is multiplied by Boltzmann's constant)
Your message dated Sat, 13 Mar 2021 22:37:29 + with message-id <20210313223729.ga29...@mithrandir.lan.emorrp1.name> and subject line Re: libqalculate: boltzmann * celsius has caused the Debian Bug report #452498, regarding qalculate-kde: Broken conversion from Celsius to Kelvin if temperature is multiplied by Boltzmann's constant to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 452498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qalculate-kde Version: 0.9.4-2 Severity: normal Calculating boltzmann * (20 °C) yields ≈ 2.7613E-22 J + 273.15 K I expect it should yield ≈ 4.0474E-21 J which is equal to boltzmann * ( (20 + 273.15) K ) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qalculate-kde depends on: ii gnuplot 4.2.2-1 A command-line driven interactive ii kdelibs4c2a 4:3.5.8.dfsg.1-3 core libraries and binaries for al ii libacl1 2.2.45-1 Access control list shared library ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libattr11:2.4.39-1 Extended attribute shared library ii libaudio2 1.9-3Network Audio System - shared libr ii libc6 2.6.1-6 GNU C Library: Shared libraries ii libcln4 1.1.13-2 Class Library for Numbers (C++) ii libfam0 2.7.0-13 Client library to control the FAM ii libfontconfig1 2.4.2-1.2generic font configuration library ii libfreetype62.3.5-1+b1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.2-3GCC support library ii libglib2.0-02.14.1-5 The GLib library of C routines ii libgmp3c2 2:4.2.2+dfsg-1 Multiprecision arithmetic library ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libidn111.1-1GNU libidn library, implementation ii libjpeg62 6b-14The Independent JPEG Group's JPEG ii libpng12-0 1.2.15~beta5-3 PNG library - runtime ii libqalculate3 0.9.4-5 Powerful and easy to use desktop c ii libqt3-mt 3:3.3.7-9Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxcursor1 1:1.1.9-1X cursor management library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxi6 2:1.1.3-1X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxml2 2.6.30.dfsg-2GNOME XML library ii libxrandr2 2:1.2.2-1X11 RandR extension library ii libxrender1 1:0.9.4-1X Rendering Extension client libra ii libxt6 1:1.0.5-3X11 toolkit intrinsics library ii qalc0.9.4-5 Powerful and easy to use command l ii zlib1g 1:1.2.3.3.dfsg-6 compression library - runtime qalculate-kde recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Control: fixed 452498 2.2.1-1 thanks Wording added was already in place for v1.0.0a, which wasn't packaged. signature.asc Description: PGP signature --- End Message ---
Bug#579491: marked as done (error: quo is zero)
Your message dated Sat, 13 Mar 2021 22:04:55 + with message-id <20210313220455.ga21...@mithrandir.lan.emorrp1.name> and subject line Re: error: quo is zero has caused the Debian Bug report #579491, regarding error: quo is zero to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 579491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qalc Version: 0.9.7-1 Severity: normal qalc requested that I report a bug. $ qalc "log(tan((pi/4)+(x*pi)/360))*6371000=0" error: quo is zero: sin(rad(0.0087266463x + 0.78539816)) + -1 * cos(rad(0.0087266463x + 0.78539816)). This is a bug. Please report it. (log(tan(((pi / 4) + ((x * pi) / 360)) * radian), e) * 6371000) = 0 = approx. cos((0.0087266463x + 0.78539816) rad) != 0 and sin((0.0087266463x + 0.78539816) rad) - cos((0.0087266463x + 0.78539816) rad) = 0 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (750, 'stable'), (700, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32+78 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qalc depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcln6 1.3.1-2Class Library for Numbers (C++) ii libgcc1 1:4.4.2-9 GCC support library ii libglib2.0-0 2.24.0-1 The GLib library of C routines ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii libqalculate5 0.9.7-1Powerful and easy to use desktop c ii libreadline6 6.1-1 GNU readline and history libraries ii libstdc++64.4.2-9The GNU Standard C++ Library v3 ii libxml2 2.7.7.dfsg-2 GNOME XML library Versions of packages qalc recommends: ii libgnomevfs2-common 1:2.24.2-2 GNOME Virtual File System (common ii wget 1.12-2 retrieves files from the web qalc suggests no packages. -- no debconf information signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Control: fixed -1 3.3.0-1 thanks 2019-07-04 * Improved handling of interval arithmetics for cubic equations https://github.com/Qalculate/libqalculate/commit/1e0aad01c409a12696def26eab3263dd4d41f801 signature.asc Description: PGP signature --- End Message ---
Bug#984881: marked as done (libnvidia-ml-dev: missing libnvidia-ml.so in library search path?)
Your message dated Sat, 13 Mar 2021 22:03:43 + with message-id and subject line Bug#984881: fixed in nvidia-graphics-drivers-legacy-390xx 390.141-3 has caused the Debian Bug report #984881, regarding libnvidia-ml-dev: missing libnvidia-ml.so in library search path? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnvidia-ml-dev Version: 11.2.67~11.2.1-2 Severity: important Hello, While trying to build a program that uses nvml, I am getting: $ gcc transfers.c -o transfers -lnvidia-ml /usr/bin/ld: cannot find -lnvidia-ml collect2: error: ld returned 1 exit status indeed libnvidia-ml-dev doesn't provide a libnvidia-ml.so link in /usr/lib/x86_64-linux-gnu Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnvidia-ml-dev depends on: ii libnvidia-ml1 [libnvidia-ml.so.1] 460.39-1 libnvidia-ml-dev recommends no packages. libnvidia-ml-dev suggests no packages. -- no debconf information -- Samuel il y a 10 catégories de personnes dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-legacy-390xx Source-Version: 390.141-3 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-legacy-390xx, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-legacy-390xx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 22:39:29 +0100 Source: nvidia-graphics-drivers-legacy-390xx Architecture: source Version: 390.141-3 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 984881 Changes: nvidia-graphics-drivers-legacy-390xx (390.141-3) unstable; urgency=medium . * nvidia-legacy-390xx-alternative: Add libnvidia-ml.so slave alternative if libnvidia-ml-dev is installed (460.56-2). (Closes: #984881) Checksums-Sha1: 8bfdbf2ec1ff1d2251bcf6003072f61ba4a52649 7598 nvidia-graphics-drivers-legacy-390xx_390.141-3.dsc aeeb3d7d007d20ff84fde701d84e9f7c16b657d1 175536 nvidia-graphics-drivers-legacy-390xx_390.141-3.debian.tar.xz 10b277cd2fca05e6ecb5150ec9b48fdf610e9e74 7869 nvidia-graphics-drivers-legacy-390xx_390.141-3_source.buildinfo Checksums-Sha256: b0f1472527249933475f486423cc31249f8fd079b8562a0c8050a42105094301 7598 nvidia-graphics-drivers-legacy-390xx_390.141-3.dsc b01198929288f4b55cd869d076ea1c61c6ad5ab06c9478ebbd595ffc9d810cc1 175536 nvidia-graphics-drivers-legacy-390xx_390.141-3.debian.tar.xz 28c37616c9dd0e695534c41780bca116817468c71de2626b9eeed374604eed8b 7869 nvidia-graphics-drivers-legacy-390xx_390.141-3_source.buildinfo Files: 34fb91947241693cdee8315412c0b473 7598 non-free/libs optional nvidia-graphics-drivers-legacy-390xx_390.141-3.dsc 73c017b56db3a612c77bf8cbe9097d59 175536 non-free/libs optional nvidia-graphics-drivers-legacy-390xx_390.141-3.debian.tar.xz b63fdd406295b1e5a3d9a089f354e0b5 7869 non-free/libs optional nvidia-graphics-drivers-legacy-390xx_390.141-3_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#868817: marked as done (release-notes: Example emulate3buttons snippet should include option "scrollmethod" "none")
Your message dated Sat, 13 Mar 2021 22:48:10 +0100 with message-id <09596f35-fc42-a9f6-06a1-ff9e2d5c6...@debian.org> and subject line release notes bug for EOL Debian release has caused the Debian Bug report #868817, regarding release-notes: Example emulate3buttons snippet should include option "scrollmethod" "none" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release-notes Severity: normal Hi, Section 5.3.3. of the release notes (about the transition from evdev to libinput) has an example of how to get the old emulate3buttons behaviour (i.e. use click both buttons as middle-button). It should also mention, though, that libinput is likely to leave middle-button and drag as scroll up and down (because the default scroll method is button, and the default button is 2). This means people who just wanted a middle button will get the confusing behaviour that their "middle" button clicks OK, but they can't click and drag with it. I think this should either be documented, or the snippet adjusted to add: Option "ScrollMethod" "none" Thanks, Matthew -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Dear reporter, Thanks for taking the time long ago to submit your release notes bug. I'm closing these reports now because the Debian releases they were reported against have reached their end-of-life (some long ago). Unfortunately it's possible that the report I'm now closing may still have relevant information for the current release (bullseye). If you believe that's the case, don't hesitate to reopen the bug, retitle it and provide further information and it will be seen during the current freeze period of Debian. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#984881: marked as done (libnvidia-ml-dev: missing libnvidia-ml.so in library search path?)
Your message dated Sat, 13 Mar 2021 21:49:15 + with message-id and subject line Bug#984881: fixed in nvidia-graphics-drivers-tesla-460 460.32.03-3 has caused the Debian Bug report #984881, regarding libnvidia-ml-dev: missing libnvidia-ml.so in library search path? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnvidia-ml-dev Version: 11.2.67~11.2.1-2 Severity: important Hello, While trying to build a program that uses nvml, I am getting: $ gcc transfers.c -o transfers -lnvidia-ml /usr/bin/ld: cannot find -lnvidia-ml collect2: error: ld returned 1 exit status indeed libnvidia-ml-dev doesn't provide a libnvidia-ml.so link in /usr/lib/x86_64-linux-gnu Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnvidia-ml-dev depends on: ii libnvidia-ml1 [libnvidia-ml.so.1] 460.39-1 libnvidia-ml-dev recommends no packages. libnvidia-ml-dev suggests no packages. -- no debconf information -- Samuel il y a 10 catégories de personnes dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-460 Source-Version: 460.32.03-3 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-460, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-460 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 21:31:33 +0100 Source: nvidia-graphics-drivers-tesla-460 Architecture: source Version: 460.32.03-3 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 984881 Changes: nvidia-graphics-drivers-tesla-460 (460.32.03-3) unstable; urgency=medium . * Switch to dh-sequence-dkms (460.56-1). * Simplify dh_dkms usage (460.56-1). * nvidia-tesla-460-alternative: Add libnvidia-ml.so slave alternative if libnvidia-ml-dev is installed (460.56-2). (Closes: #984881) Checksums-Sha1: 817c53a09ffe0f8852b9e966222b0211a1777b21 7498 nvidia-graphics-drivers-tesla-460_460.32.03-3.dsc cfee79146eaf8f7643db5568362432aef4b223f2 199308 nvidia-graphics-drivers-tesla-460_460.32.03-3.debian.tar.xz 13924bd48102f8fbd43ab011a0bee15937976c8f 7885 nvidia-graphics-drivers-tesla-460_460.32.03-3_source.buildinfo Checksums-Sha256: 710d3ba80a736390133c0443b4911abfb25d3c39cfb8f9c357acea308954e8d1 7498 nvidia-graphics-drivers-tesla-460_460.32.03-3.dsc 6e650e28f0fa512daede5d3699b6f58a0f0227fdfd79ed21bc6e738c60ecab5b 199308 nvidia-graphics-drivers-tesla-460_460.32.03-3.debian.tar.xz 8502699e1f0249adb98c407224db79f32efef37f2477b557162cc74cc011d179 7885 nvidia-graphics-drivers-tesla-460_460.32.03-3_source.buildinfo Files: c563d0c4f7985febc2bb49c6a3ca5c95 7498 non-free/libs optional nvidia-graphics-drivers-tesla-460_460.32.03-3.dsc a5508430720b54a919b29e66828c6c44 199308 non-free/libs optional nvidia-graphics-drivers-tesla-460_460.32.03-3.debian.tar.xz 27bace0a45faee753503eda524fcb290 7885 non-free/libs optional nvidia-graphics-drivers-tesla-460_460.32.03-3_source.buildinfo -BEGIN PGP
Bug#865120: marked as done (release-notes: document i386/amd64 kernel changes for jessie->stretch)
Your message dated Sat, 13 Mar 2021 22:48:10 +0100 with message-id <09596f35-fc42-a9f6-06a1-ff9e2d5c6...@debian.org> and subject line release notes bug for EOL Debian release has caused the Debian Bug report #865120, regarding release-notes: document i386/amd64 kernel changes for jessie->stretch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 865120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release-notes Severity: important With Stretch, amd64 flavour kernels are no longer supplied within the i386 Debian architecture (i.e. for a 64 bit kernel with a 32 bit userspace). The release notes should document that these kernel packages are no longer offered so that users don't accidentally run unsupported kernels indefinitely (hence severity:important). The upgrade path is to enable amd64 as a foreign architecture and then install the relevant amd64 kernel image. A 0th draft at some wording for §4.6/4.6.1: Users of the i386 port are advised that the amd64 flavour of kernel is no longer included within the i386 port but that these kernels should instead be installed directly from the amd64 port using the ability for apt and dpkg to install foreign architecture packages (known as multiarch). - check if running i386 userspace with amd64 kernel: `dpkg --print-architure` is i386, and `uname -r` ends in amd64 - add amd64 as foreign architecture `dpkg --add-architecture amd64; apt-get update` - (install the appropriate kernel metapackage as described already) cheers Stuart --- End Message --- --- Begin Message --- Dear reporter, Thanks for taking the time long ago to submit your release notes bug. I'm closing these reports now because the Debian releases they were reported against have reached their end-of-life (some long ago). Unfortunately it's possible that the report I'm now closing may still have relevant information for the current release (bullseye). If you believe that's the case, don't hesitate to reopen the bug, retitle it and provide further information and it will be seen during the current freeze period of Debian. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#864307: marked as done (release-notes: Document openssh regression)
Your message dated Sat, 13 Mar 2021 22:48:10 +0100
with message-id <09596f35-fc42-a9f6-06a1-ff9e2d5c6...@debian.org>
and subject line release notes bug for EOL Debian release
has caused the Debian Bug report #864307,
regarding release-notes: Document openssh regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
864307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock openssh 1:7.4p1-11, which contains a one-line patch for
compression statistics. This fell through the cracks, but is apparently
a significant issue for some users tracking data transfers. It was a
regression in OpenSSH 6.8 (i.e. since jessie).
diff -Nru openssh-7.4p1/debian/.git-dpm openssh-7.4p1/debian/.git-dpm
--- openssh-7.4p1/debian/.git-dpm 2017-03-30 11:18:22.0 +0100
+++ openssh-7.4p1/debian/.git-dpm 2017-06-06 15:02:30.0 +0100
@@ -1,6 +1,6 @@
# see git-dpm(1) from git-dpm package
-904bc482ad87648a2c799c441dc6a8449f24e15a
-904bc482ad87648a2c799c441dc6a8449f24e15a
+a93e5207256eff3a51db335c5a12b3ad2291f686
+a93e5207256eff3a51db335c5a12b3ad2291f686
971a7653746a6972b907dfe0ce139c06e4a6f482
971a7653746a6972b907dfe0ce139c06e4a6f482
openssh_7.4p1.orig.tar.gz
diff -Nru openssh-7.4p1/debian/changelog openssh-7.4p1/debian/changelog
--- openssh-7.4p1/debian/changelog 2017-03-30 11:19:04.0 +0100
+++ openssh-7.4p1/debian/changelog 2017-06-06 15:03:48.0 +0100
@@ -1,3 +1,10 @@
+openssh (1:7.4p1-11) unstable; urgency=medium
+
+ * Fix incoming compression statistics (thanks, Russell Coker; closes:
+#797964).
+
+ -- Colin Watson Tue, 06 Jun 2017 15:03:48 +0100
+
openssh (1:7.4p1-10) unstable; urgency=medium
* Move privilege separation directory and PID file from /var/run/ to /run/
diff -Nru
openssh-7.4p1/debian/patches/fix-incoming-compression-statistics.patch
openssh-7.4p1/debian/patches/fix-incoming-compression-statistics.patch
--- openssh-7.4p1/debian/patches/fix-incoming-compression-statistics.patch
1970-01-01 01:00:00.0 +0100
+++ openssh-7.4p1/debian/patches/fix-incoming-compression-statistics.patch
2017-06-06 15:02:30.0 +0100
@@ -0,0 +1,27 @@
+From a93e5207256eff3a51db335c5a12b3ad2291f686 Mon Sep 17 00:00:00 2001
+From: Russell Coker
+Date: Tue, 6 Jun 2017 15:00:20 +0100
+Subject: Fix incoming compression statistics
+
+Bug-Debian: https://bugs.debian.org/797964
+Forwarded:
https://lists.mindrot.org/pipermail/openssh-unix-dev/2017-June/036077.html
+Last-Update: 2017-06-06
+
+Patch-Name: fix-incoming-compression-statistics.patch
+---
+ packet.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/packet.c b/packet.c
+index ad1f6b49..afcde6f3 100644
+--- a/packet.c
b/packet.c
+@@ -587,7 +587,7 @@ ssh_packet_close(struct ssh *ssh)
+ deflateEnd(stream);
+ }
+ if (state->compression_in_started) {
+- z_streamp stream = >compression_out_stream;
++ z_streamp stream = >compression_in_stream;
+ debug("compress incoming: "
+ "raw data %llu, compressed %llu, factor %.2f",
+ (unsigned long long)stream->total_out,
diff -Nru openssh-7.4p1/debian/patches/series
openssh-7.4p1/debian/patches/series
--- openssh-7.4p1/debian/patches/series 2017-03-30 11:18:21.0 +0100
+++ openssh-7.4p1/debian/patches/series 2017-06-06 15:02:30.0 +0100
@@ -34,3 +34,4 @@
ssh-keyscan-hash-port.patch
ssh-keygen-null-deref.patch
unbreak-unix-forwarding-for-root.patch
+fix-incoming-compression-statistics.patch
unblock openssh/1:7.4p1-11
Thanks,
--
Colin Watson [cjwat...@debian.org]
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Dear reporter,
Thanks for taking the time long ago to submit your release notes bug.
I'm closing these reports now because the Debian releases they were
reported against have reached their end-of-life (some long ago).
Unfortunately it's possible that the report I'm now closing may still
have relevant information for the current release (bullseye). If you
believe that's the case, don't hesitate to reopen the bug, retitle it
and provide further information and it will be seen during the current
freeze period of Debian.
Paul
OpenPGP_signature
Description:
Bug#864160: marked as done (Release notes should document how to compile 3rd party software against OpenSSL)
Your message dated Sat, 13 Mar 2021 22:48:10 +0100 with message-id <09596f35-fc42-a9f6-06a1-ff9e2d5c6...@debian.org> and subject line release notes bug for EOL Debian release has caused the Debian Bug report #864160, regarding Release notes should document how to compile 3rd party software against OpenSSL to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 864160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release-notes Severity: normal With both OpenSSL 1.0.2 and 1.1 included in stretch, the release notes should document which to choose for compiling 3rd party software. In most cases either will work, but in some circumstances compiling against the wrong OpenSSL version will result in a crashing application (if some library used uses the other OpenSSL version and incompatible data is passed from one OpenSSL version to the other). It was decided to not force the correct OpenSSL version through libssl1.0-dev/libssl-dev dependencies. For packages included in stretch choosing the correct OpenSSL version was implemented through a review by Kurt half a year ago and RC bugs forcing affected software to use the correct version. For stretch users compiling 3rd party software this should be properly documented. One consumer of this information should be stretch-backports, whenever a package uses libssl1.0-dev in stretch but libssl-dev in buster the information is required whether compiling with libssl-dev in stretch-backports is safe. --- End Message --- --- Begin Message --- Dear reporter, Thanks for taking the time long ago to submit your release notes bug. I'm closing these reports now because the Debian releases they were reported against have reached their end-of-life (some long ago). Unfortunately it's possible that the report I'm now closing may still have relevant information for the current release (bullseye). If you believe that's the case, don't hesitate to reopen the bug, retitle it and provide further information and it will be seen during the current freeze period of Debian. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#828746: marked as done (hwclock: RTC to wrong offset after reboot)
Your message dated Sat, 13 Mar 2021 22:48:10 +0100 with message-id <09596f35-fc42-a9f6-06a1-ff9e2d5c6...@debian.org> and subject line release notes bug for EOL Debian release has caused the Debian Bug report #828746, regarding hwclock: RTC to wrong offset after reboot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 828746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: util-linux Version: 2.28-5 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Whenever rebooting this host, the RTC time is 3 hours ahead of what it should be. This wasn't the case when using whatever is currently in Debian/stable. - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'stable') Architecture: i386 (i586) Kernel: Linux 4.6.0-1-686 (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages util-linux depends on: ii libblkid1 2.28-5 ii libc6 2.22-11 ii libfdisk1 2.28-5 ii libmount1 2.28-5 ii libncursesw5 6.0+20160319-1 ii libpam0g 1.1.8-3.3 ii libselinux12.5-3 ii libsmartcols1 2.28-5 ii libsystemd0230-2 ii libtinfo5 6.0+20160319-1 ii libudev1 230-2 ii libuuid1 2.28-5 ii zlib1g 1:1.2.8.dfsg-2+b1 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 4.0-2 ii kbd 2.0.3-2 pn util-linux-locales - -- Configuration Files: /etc/default/hwclock changed: HWCLOCKACCESS=yes - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJXcRxGAAoJEK4fgnfEtNe2nN8P/RGiTyAgVpJAE9do7KqZ5sLd CkiL20w9UdFPFw5YQ8gvCqOFFyCLm5rQH6zoUT5qZsKui2BwOwyZ6FQe8YUVlIKk o87SITuJXa8bTeXXp9OFy1UwcWkaBHLCOmlzJ4SVLr8dLTLjWBpmyJO62hdjqYC3 dR01ykPE8zgcSA5sGASzb/JJyQlWu2woBISRiTTkV+yXW+x3uNhnzsH9WgPiy1Q4 F+aPzsZDNiEpY+aLB22101g20DpaNl/kNpydN0WJCHuulwrFDPBic6j0c+zFDUrV ZdAdmzYP2henhQPGcAMaB222RHmY2gVC/gxh0C6JhCMBpHon3XcMdf5H49cvklBT 03HzHAuRl2irf3HNJ/ykZ3HFUrvK16etJAS3Jvi0RrXv4ED1elRwGnEGi5ubJ3wV rUyZeln6e7DuUqaYFtazIqKS2JjiqOtOeOkfC5vh5B6LSPyxgvUQqtOKkSmGTrcn Xvna1pMugKo+Xma+lXQ5ivN76N+A97qVIn8Z7iaxJIBeF6TlEG9MQZYp2FhWkHU0 bsZ0/YFp/0W20XJY514YPtF8a1l+/aKG5G7RBmVy9z+quH6PkQ/cT+1k5n0hw7Sp +rUJ9mmWJytSC5lyrJbF+UmjDmWV2NGVCD4OmRJyudLX6LhOOruqZIbpVBfEFv/8 QSvO3jqyHWwbk35qzbwN =53CV -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Dear reporter, Thanks for taking the time long ago to submit your release notes bug. I'm closing these reports now because the Debian releases they were reported against have reached their end-of-life (some long ago). Unfortunately it's possible that the report I'm now closing may still have relevant information for the current release (bullseye). If you believe that's the case, don't hesitate to reopen the bug, retitle it and provide further information and it will be seen during the current freeze period of Debian. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#423456: marked as done (every orkut message is marked as spam (numeric localpart))
Your message dated Sat, 13 Mar 2021 22:44:09 +0100 with message-id and subject line Re: Bug#423456: every orkut message is marked as spam (numeric localpart) has caused the Debian Bug report #423456, regarding every orkut message is marked as spam (numeric localpart) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 423456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: spamassassin Version: 3.1.7-2 Severity: normal Apparently these "numeric From" checks are very similar and so are easylu triggered together, with the effect of marking the message as spam. X-Spam-Status: Yes, score=6.5 required=5.0 tests=AWL,FROM_ALL_NUMS, FROM_LOCAL_HEX,FROM_STARTS_WITH_NUMS autolearn=no version=3.1.7-deb X-Spam-Report: * 1.8 FROM_STARTS_WITH_NUMS From: starts with many numbers * 2.2 FROM_LOCAL_HEX From: localpart has long hexadecimal * sequence * 2.3 FROM_ALL_NUMS From numeric address (except US/Canada * phones) * 0.1 AWL AWL: From: address is in the auto white-list ... From: orkut <3504732672376623...@mail.orkut.com> -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21 (SMP w/2 CPU cores) Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages spamassassin depends on: ii libarchive-tar-perl 1.30-2 Archive::Tar - manipulate tar file ii libdigest-sha1-perl 2.11-2 NIST SHA-1 message digest algorith ii libhtml-parser-perl 3.56-1 A collection of modules that parse ii libsocket6-perl 0.19-1 Perl extensions for IPv6 ii libwww-perl 5.805-1WWW client/server library for Perl ii perl 5.8.8-7Larry Wall's Practical Extraction Versions of packages spamassassin recommends: pn libmail-spf-query-perl (no description available) ii libnet-dns-perl 0.59-1 Perform DNS queries from a Perl sc ii perl [libmime-base64-perl]5.8.8-7Larry Wall's Practical Extraction pn spamc (no description available) -- no debconf information -- ciao, Marco --- End Message --- --- Begin Message --- Version: 3.4.4-1 This has been fixed at some point in the past. -- ciao, Marco signature.asc Description: PGP signature --- End Message ---
Bug#985154: marked as done (gegl: autopkgtest regression: Package 'gegl-0.4' requires 'babl >= 0.1.84' but version of babl is 0.1.82)
Your message dated Sat, 13 Mar 2021 21:18:34 + with message-id and subject line Bug#985154: fixed in gegl 1:0.4.28-2 has caused the Debian Bug report #985154, regarding gegl: autopkgtest regression: Package 'gegl-0.4' requires 'babl >= 0.1.84' but version of babl is 0.1.82 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gegl Version: 1:0.4.28-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of gegl the autopkgtest of gegl fails in testing when that autopkgtest is run with the binary packages of gegl from unstable. It passes when run with only packages from testing. In tabular form: passfail gegl from testing1:0.4.28-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Reading the changelog, I noticed that the Build-Depends on babl was bumped appropriately, but it seems that *versioned* dependency is missing in other places. This missing is also causing regressions in other reverse dependencies [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gegl https://ci.debian.net/data/autopkgtest/testing/amd64/g/gegl/11037943/log.gz autopkgtest [03:10:42]: test libgegl-dev: [--- + mktemp -d + WORKDIR=/tmp/tmp.SF6Nw0UrQI + export XDG_RUNTIME_DIR=/tmp/tmp.SF6Nw0UrQI + trap rm -rf "$WORKDIR" 0 INT QUIT ABRT PIPE TERM + cd /tmp/tmp.SF6Nw0UrQI + [ -n ] + CROSS_COMPILE= + cat + pkg-config --cflags --libs gegl-0.4 Package 'gegl-0.4' requires 'babl >= 0.1.84' but version of babl is 0.1.82 + gcc -o gegl-0.4-test gegl-0.4.c gegl-0.4.c:1:10: fatal error: gegl.h: No such file or directory 1 | #include | ^~~~ compilation terminated. + rm -rf /tmp/tmp.SF6Nw0UrQI autopkgtest [03:10:43]: test libgegl-dev: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gegl Source-Version: 1:0.4.28-2 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of gegl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gegl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 15:53:15 -0500 Source: gegl Built-For-Profiles: noudeb Architecture: source Version: 1:0.4.28-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 985154 Changes: gegl (1:0.4.28-2) unstable; urgency=medium . * debian/control.in: Use epoch for babl dependency (Closes: #985154) . gegl (1:0.4.28-1) unstable; urgency=medium . * New upstream release * debian/control.in: Bump minimum babl to 0.1.84 * debiabn/control.in: Bump minimum meson to 0.54.0 * debian/control.in: Build-Depend on libmaxflow-dev Checksums-Sha1: dab00f96f18252e72efda2df4e9b9bf2fac3995c 3061 gegl_0.4.28-2.dsc 2fc58442b2035d4e3f6a0d51ccab048ad69fce07 23780 gegl_0.4.28-2.debian.tar.xz 1cf26cd79b2aa9c39c8778af9fe4ae42ba29f291 12494 gegl_0.4.28-2_source.buildinfo Checksums-Sha256: f5e3e0e8db252522c324c065865012b3e121348e5d3844ab95fd039ea2137050 3061 gegl_0.4.28-2.dsc bf11b37d9c154124fc123420dacbee244a92264cc9877b37895a6899e0ebf9f4 23780 gegl_0.4.28-2.debian.tar.xz bc480441c17566006fbebbf333c0081d25a5bb295bb6b899354eda495d37c77d 12494 gegl_0.4.28-2_source.buildinfo Files: 756bb938a6b84b6151ba3f7d931bbd84 3061 devel optional gegl_0.4.28-2.dsc 0361a51d906d77dfe710a25ad07d067d 23780 devel optional gegl_0.4.28-2.debian.tar.xz 7e28f269115c27f02b3c0920d1e73921 12494 devel optional
Bug#702010: marked as done (gtkglext: uses pangox which is going away)
Your message dated Sat, 13 Mar 2021 19:03:49 + with message-id and subject line Bug#702010: fixed in gtkglext 1.2.0-10~exp1 has caused the Debian Bug report #702010, regarding gtkglext: uses pangox which is going away to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 702010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtkglext Version: 1.2.0-3 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pangox Hi, gtkglext uses pangox, which is going away. Ideally gtkglext would stop using it entirely, though I'm not sure if that's feasible without breaking the ABI. There's a commit upstream removing the use of pangox[1], but it also removes public APIs, so we can't use that. Thanks, Emilio [1] http://git.gnome.org/browse/gtkglext/commit/?id=df7a7b35b80b395d7ba411c7f727970a46fb0588 --- End Message --- --- Begin Message --- Source: gtkglext Source-Version: 1.2.0-10~exp1 Done: Gert Wollny We believe that the bug you reported is fixed in the latest version of gtkglext, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gert Wollny (supplier of updated gtkglext package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 17:29:28 +0100 Source: gtkglext Architecture: source Version: 1.2.0-10~exp1 Distribution: unstable Urgency: medium Maintainer: Gert Wollny Changed-By: Gert Wollny Closes: 702010 Changes: gtkglext (1.2.0-10~exp1) unstable; urgency=medium . * d/control: don't depend on pangox Closes: #702010 Checksums-Sha1: 501ec242df75d9f7ecf53616b9b7db16d222cfb2 2124 gtkglext_1.2.0-10~exp1.dsc 25d6ecbba0185cdfdfa7b239f16965a6fd2e8d54 8304 gtkglext_1.2.0-10~exp1.debian.tar.xz b318e65fed8e6f875a0928b128e199cb8938e45d 13135 gtkglext_1.2.0-10~exp1_source.buildinfo Checksums-Sha256: 6bebbfe49387d008421270a94b141a41128fe0b825a31abc93e7a25427aee454 2124 gtkglext_1.2.0-10~exp1.dsc da8104a03023c84c8616d4177975cc5d5cde15ba3d469b631823b23aac23c526 8304 gtkglext_1.2.0-10~exp1.debian.tar.xz 583a949eba81f16646fcc504f04ea493ff19e81059623e2e698d0c3fd2b0f3a6 13135 gtkglext_1.2.0-10~exp1_source.buildinfo Files: 424d1d86b03ddd28f53653b31f6efb78 2124 oldlibs optional gtkglext_1.2.0-10~exp1.dsc f18e73f79ec94bf75906e7f27423f123 8304 oldlibs optional gtkglext_1.2.0-10~exp1.debian.tar.xz 0bf7fa8105e17e93fc995b4cd1f9456e 13135 oldlibs optional gtkglext_1.2.0-10~exp1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAmBNCWYACgkQl/LU/KCf ME6PAw//eu6JxBFGCeHhttxf9xK2co9O8H6r0M1lVLpZHyoUBz57sAFVMaSJA+S2 PgPWF5wA6ooToZFS/7sr4Cyfsvay8MapJzdjB7S02oSJeReu44rnYYjiMr74ScT5 ISehrSj2NulgDvvojfJ5HoH93ZWSRyjwS/+E4JvXlD/VYJuE8zCTZd73MMYFt9HR OvNCJ0Gj7sh5cZ3y7moEsv7KBUZ3+fnqGq4wumv98Ahxj9p9AY/SAfSeHj4DiHXz s9pZDbRbNkl+tvWatXSjh+8Dsc2nuezBpg6g9iA6+MU4JMG4mF2YKGfIZU3yQPPk YI4FyD53kbTEziJ/fr6lGf/l0xSicQpvDemWrXNKzSYhQMWGBhOl5tcfH6AqFDZo YWOcEkoqd9a8iMuoLxS718jKbg6muqVGTYWAKz6oHLG1Va/+JMLfvVdVEXMuKr0c d8i2c1FYl8/lmzYir9nq/NCwP8XVvf5uTr50Mjw92/IqI6CARDr644w/ICcBA10e yvAh92pnKskW8Iqiy66H1LRsRMAM6sw/wQvkPASQUYH0wKYLlH2q0zFN02exQ6YR dNT5mCZ4gI8nQeuyB35sPMUDGoTRrMdUHwcwW20zilbL2MnmNRxeLHwyrKa2Ps7U brnjeKsKbqrNXubTBOULmYcik0fHrwzv3Lsk3S7FQviFBmyCsFI= =wBB2 -END PGP SIGNATURE End Message ---
Bug#984983: marked as done (python3-networkmanager: crashes on unknown device types (eg. wifi p2p) in >=bullseye)
Your message dated Sat, 13 Mar 2021 18:50:14 +
with message-id
and subject line Bug#984983: fixed in python-networkmanager 2.2-1
has caused the Debian Bug report #984983,
regarding python3-networkmanager: crashes on unknown device types (eg. wifi
p2p) in >=bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
984983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-networkmanager
Version: 2.1-2
Severity: serious
Justification: Incompatibility with bullseye NM causes crashes enumerating
devices etc.
Dear Maintainer,
I'm experiencing python3-networkmanager crashing with a simple test
program like this:
$ cat /tmp/test.py
#!/usr/bin/python3
import NetworkManager
for dev in NetworkManager.NetworkManager.Devices:
if dev.DeviceType == NetworkManager.NM_DEVICE_TYPE_WIFI:
print(dev)
print("Program finished")
$ python3 /tmp/test.py
Traceback (most recent call last):
File "/tmp/test.py", line 6, in
for dev in NetworkManager.NetworkManager.Devices:
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 174, in get_func
return fixups.to_python(klass, 'Get', name, data, attrib['type'])
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 555, in
to_python
val = fixups.base_to_python(val)
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 612, in
base_to_python
return [fixups.base_to_python(x) for x in val]
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 612, in
return [fixups.base_to_python(x) for x in val]
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 625, in
base_to_python
return globals()[classname](val)
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 353, in __new__
klass = device_class(obj.Get('org.freedesktop.NetworkManager.Device',
'DeviceType', dbus_interface='org.freedesktop.DBus.Properties'))
File "/usr/lib/python3/dist-packages/NetworkManager.py", line 373, in
device_class
return {
KeyError: dbus.UInt32(30, variant_level=1)
The reason appears to be that NM in bullseye supports and returns a
(disconnected=30) wifi p2p interface on my device.
Here's some info from the affected system:
$ nmcli d
DEVICE TYPE STATE CONNECTION
wlan0 wifi connected FOOBAR
p2p-dev-wlan0 wifi-p2p disconnected --
lo loopback unmanaged --
The mere existance of p2p-dev-wlan0 causes the crash and the needed constant
values in python3-networkmanager was added in new upstream release 2.2.
FWIW the problem is also reproducible on a buster system with a partial
update to NM (and deps) from bullseye. The p2p feature is thus not a new
kernel feature or similar, simply new info exposed by NM.
As mentioned, this is fixed in upstream release 2.2.
I've also filed a pre-approval request to update to 2.2 during freeze,
see Bug#984925
Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: python-networkmanager
Source-Version: 2.2-1
Done: Andreas Henriksson
We believe that the bug you reported is fixed in the latest version of
python-networkmanager, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 984...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Henriksson (supplier of updated
python-networkmanager package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 13 Mar 2021 19:29:10 +0100
Source: python-networkmanager
Architecture: source
Version: 2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Henriksson
Closes: 984983
Changes:
python-networkmanager (2.2-1) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Andreas Henriksson ]
* New upstream release.
Bug#965935: marked as done (configure_networking() should wait for specified interface)
Your message dated Sat, 13 Mar 2021 18:49:40 + with message-id and subject line Bug#965935: fixed in initramfs-tools 0.140 has caused the Debian Bug report #965935, regarding configure_networking() should wait for specified interface to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools-core Version: 0.137 Severity: normal Tags: patch configure_networking() will do a `udevadm settle` before trying to configure an interface. However it is possible for a NIC to appear after the event queue has settled. This is pretty reproducible with a USB NIC I have. There doesn't appear to be a good way to wait for all devices that were connected at boot time to become available - `udevadm settle` is just the closest thing we have. However, in the case that the user has told us which interface they expect to be used in the initramfs, we can just wait for it specifically. As a bonus, this should shave off some time on systems where the NIC is available before the udev event queue has emptied. I've a patch to do this, which I'll submit as an MR in salsa. Note: This should help out with the following issue in clevis, which provides a mechanism for unlocking a LUKS root device from the initramfs by communicating with a tang server: https://github.com/latchset/clevis/issues/145 -- 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.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools-core depends on: ii coreutils8.32-3 ii cpio 2.13+dfsg-3 ii e2fsprogs1.45.6-1 ii klibc-utils 2.0.7-1 ii kmod 27+20200310-2 ii logsave 1.45.6-1 ii udev 245.6-3 Versions of packages initramfs-tools-core recommends: ii busybox 1:1.30.1-5 ii pigz 2.4-1+b1 Versions of packages initramfs-tools-core suggests: ii bash-completion 1:2.10-1 -- Configuration Files: /etc/initramfs-tools/initramfs.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.140 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated initramfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 19:13:18 +0100 Source: initramfs-tools Architecture: source Version: 0.140 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Bastian Blank Closes: 965935 Changes: initramfs-tools (0.140) unstable; urgency=medium . [ Norbert Lange ] * mkinitramfs: use temporary file for uncompressed cpio . [ Michael Prokop ] * mkinitramfs: report actually requested compress util if it's not present . [ Ben Hutchings ] * init: Mount /dev without the noexec option . [ dann frazier ] * configure_networking(): Wait for specified network device (Closes: #965935) . [ Bastian Blank ] * Include all PCI controller modules * Include all reset controller modules Checksums-Sha1: ca9b2b7c1bcd523e6b0d01610a8ffc1f9469d3c9 1599 initramfs-tools_0.140.dsc 503b9ba5619bbb5fc1fefc54148b438517306a2f 95044 initramfs-tools_0.140.tar.xz 98067441d1545346eb097dbc0e8065c3bee85dfd 5816 initramfs-tools_0.140_source.buildinfo Checksums-Sha256: 5537ff004f5e7fc9be4790a3248664806fa1ae4e5fe05ea47df821be8953aef4 1599 initramfs-tools_0.140.dsc 17ec1b0e5e1c6f8254f2184be780e50c8274f71cdf482e5c46d50f955370685f 95044
Bug#968519: marked as done (configure_networking(): race condition with RockPro64: calls ipconfig before NIC is detected)
Your message dated Sat, 13 Mar 2021 18:49:40 + with message-id and subject line Bug#965935: fixed in initramfs-tools 0.140 has caused the Debian Bug report #965935, regarding configure_networking(): race condition with RockPro64: calls ipconfig before NIC is detected to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dropbear-initramfs Version: 2020.80-1 Severity: important Dear Maintainer, About four times out of five, dropbear fails to launch at boot on the RockPro64 single-board computer. When it fails, I see this message repeated several times, scattered between various other messages on the serial console: ipconfig: no devices to configure Finally, this message appears: /scripts/init-premount/dropbear: .: line 279: can't open '/run/net-*.conf': No such file or directory The system then proceeds to the luks unlock prompt at the serial console only, with dropbear not running, so the boot process will not continue unless I connect a serial console and enter the password that way. I have tried adding all my ethernet-related driver modules to /etc/initramfs-tools/modules and rebuilding initramfs, but it didn't help. I have tried using ip= kernel command line arguments for a static address instead of DHCP, but that didn't help either. However, editing /usr/share/initramfs-tools/scripts/init-premount/dropbear does get it working. Making that script wait for a /run/net-*.conf file to appear before it calls configure_networking appears to be a solution. Even just sleeping for a few seconds before the configure_networking call seems to work, though I don't know how consistently. Based on this workaround and the fact that the aforementioned error messages are interleaved with other boot messages, it looks to me like dropbear's init-premount script is being run in parallel with driver and network setup, and often executing before the rk3399's onboard ethernet has a chance to finish initializing. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.7.0-2-arm64 (SMP w/6 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dropbear-initramfs depends on: ii busybox 1:1.30.1-5 ii dropbear-bin 2020.80-1 ii initramfs-tools 0.137 ii udev 246-2 Versions of packages dropbear-initramfs recommends: ii cryptsetup-initramfs 2:2.3.3-1 dropbear-initramfs suggests no packages. -- Configuration Files: /etc/dropbear-initramfs/config changed: DROPBEAR_OPTIONS="-p 222" -- no debconf information --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.140 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated initramfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 19:13:18 +0100 Source: initramfs-tools Architecture: source Version: 0.140 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Bastian Blank Closes: 965935 Changes: initramfs-tools (0.140) unstable; urgency=medium . [ Norbert Lange ] * mkinitramfs: use temporary file for uncompressed cpio . [ Michael Prokop ] * mkinitramfs: report actually requested compress util if it's not present . [ Ben Hutchings ] * init: Mount /dev without the noexec option . [ dann frazier ] * configure_networking(): Wait for specified network device (Closes: #965935) . [ Bastian Blank ] * Include all PCI controller modules * Include all reset controller modules Checksums-Sha1: ca9b2b7c1bcd523e6b0d01610a8ffc1f9469d3c9 1599
Bug#934743: marked as done (python-networkmanager: org.freedesktop.DBus.Error.ServiceUnknown if NetworkManager service restarts)
Your message dated Sat, 13 Mar 2021 19:40:16 +0100 with message-id <20210313184016.6d7muxjbpazdy...@fatal.se> and subject line Re: python-networkmanager: org.freedesktop.DBus.Error.ServiceUnknown if NetworkManager service restarts has caused the Debian Bug report #934743, regarding python-networkmanager: org.freedesktop.DBus.Error.ServiceUnknown if NetworkManager service restarts to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 934743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-networkmanager Version: 2.1-2 Tags: patch Forwarded: https://github.com/seveas/python-networkmanager/issues/66 If NetworkManager service restarts, it gets a new dbus unix process id. The python-networkmanager remains with the old id. since this process doesn't exist any more, a org.freedesktop.DBus.Error.ServiceUnknown exception is thrown. The parameter follow_name_owner_changes can be used in get_object() calls to prevent this. diff --git a/NetworkManager.py b/NetworkManager.py index 3d137fe..00f0729 100644 --- a/NetworkManager.py +++ b/NetworkManager.py @@ -258,7 +258,7 @@ def __eq__(self, other): @property def proxy(self): if not self._proxy: -self._proxy = dbus.SystemBus().get_object(self.dbus_service, self.object_path) +self._proxy = dbus.SystemBus().get_object(self.dbus_service, self.object_path, follow_name_owner_changes=True) self._proxy.created = time.time() elif self._proxy.created < self.last_disconnect: if self.is_transient: https://github.com/anrodlo/python-networkmanager/commit/88f1b0e4531f80e17af3ffe00b5816800ebb4c1a.diff --- End Message --- --- Begin Message --- Version: 2.2-1 Sorry I forgot to list this bug as closed in the debian/changelog entry I just uploaded. Manually closing this now since the fix should be included in the version I just uploaded. Regards, Andreas Henriksson--- End Message ---
Bug#601228: marked as done (open dialog crashes in dirs with more than 63 subdirs)
Your message dated Sat, 13 Mar 2021 19:07:28 +0100 with message-id <20210313180728.gy356...@zedat.fu-berlin.de> and subject line Re: Bug#600477: Bad LessTiff call? has caused the Debian Bug report #600477, regarding open dialog crashes in dirs with more than 63 subdirs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 600477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- X-debbugs-Cc: der...@glyphandcog.com Package: xpdf Version: 3.02-11 Right click and then choose "Open", or "Open in another window", $ *** glibc detected *** xpdf: malloc(): memory corruption (fast): 0x09f5a048 *** === Backtrace: = /lib/i686/cmov/libc.so.6(+0x6b281)[0xb71c8281] /lib/i686/cmov/libc.so.6(+0x6e400)[0xb71cb400] /lib/i686/cmov/libc.so.6(__libc_malloc+0x5c)[0xb71ccc8c]... Happens in various PDF files, every time. Happens if I have a ~/.xpdfrc file or not. Also right click, type ESC, then left click. Segmentation fault. --- End Message --- --- Begin Message --- > When this bug was reported, xpdf was being linked with Lesstif rather > than OpenMotif, so it might have been a Lesstif problem. Either way, I > think it's safe to close this bug now. ACK, closing.--- End Message ---
Bug#600477: marked as done (open dialog crashes in dirs with more than 63 subdirs)
Your message dated Sat, 13 Mar 2021 19:07:28 +0100 with message-id <20210313180728.gy356...@zedat.fu-berlin.de> and subject line Re: Bug#600477: Bad LessTiff call? has caused the Debian Bug report #600477, regarding open dialog crashes in dirs with more than 63 subdirs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 600477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.02-11 Severity: normal If I try to load a pdf file by first clicking on 'open' or 'open in a new window' xpdf crashes. However, if in a termial I do this by typing xpdf foo.pdf, then the pdf file is opened. Now that a file is openned, if I try 'open in a new window' or 'save as' it crashes. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xpdf depends on: ii lesstif2 1:0.95.2-1 OSF/Motif 2.1 implementation relea ii libc6 2.11.2-5 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-8 GCC support library ii libpoppler5 0.12.4-1.1 PDF rendering library ii libstdc++64.4.4-8The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-3 X11 client-side library ii libxt61:1.0.7-1 X11 toolkit intrinsics library Versions of packages xpdf recommends: ii gsfonts-x11 0.21 Make Ghostscript fonts available t ii poppler-data 0.4.3-1Encoding data for the poppler PDF ii poppler-utils 0.12.4-1.1 PDF utilitites (based on libpopple xpdf suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- > When this bug was reported, xpdf was being linked with Lesstif rather > than OpenMotif, so it might have been a Lesstif problem. Either way, I > think it's safe to close this bug now. ACK, closing.--- End Message ---
Bug#505932: marked as done (xpdf: needs to support selectable checkboxes)
Your message dated Sat, 13 Mar 2021 19:06:28 +0100 with message-id <20210313180628.qalw65r5p3h3o6qz@begin> and subject line Re: Bug#505932: xpdf: Check boxes to not get ticked has caused the Debian Bug report #505932, regarding xpdf: needs to support selectable checkboxes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 505932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf-reader Version: 3.02-1.4 Severity: normal Hello, wget www.irs.gov/pub/irs-pdf/fw9.pdf evince fw9.pdf then tick some boxes, fill some fields, save. Reopen with evince, both fields and check boxes are filled as appropriate. Reopen with xpdf, fields get filled, but check boxes do not get ticked. Samuel -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xpdf depends on: ii xpdf-common 3.02-1.4 Portable Document Format (PDF) sui ii xpdf-reader 3.02-1.4 Portable Document Format (PDF) sui ii xpdf-utils3.02-1.4 Portable Document Format (PDF) sui xpdf recommends no packages. xpdf suggests no packages. Versions of packages xpdf-reader depends on: ii gsfonts 1:8.11+urwcyr1.0.7~pre44-3 Fonts for the Ghostscript interpre ii lesstif2 1:0.95.0-2.1 OSF/Motif 2.1 implementation relea ii libc6 2.7-15 GNU C Library: Shared libraries ii libfreetype6 2.3.7-2FreeType 2 font engine, shared lib ii libgcc1 1:4.3.2-1 GCC support library ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libpaper1 1.1.23+nmu1library for handling paper charact ii libsm62:1.0.3-2 X11 Session Management library ii libstdc++64.3.2-1The GNU Standard C++ Library v3 ii libt1-5 5.1.2-3Type 1 font rasterizer library - r ii libx11-6 2:1.1.5-2 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxp61:1.0.0.xsf1-2 X Printing Extension (Xprint) clie ii libxpm4 1:3.5.7-1 X11 pixmap library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xpdf-common 3.02-1.4 Portable Document Format (PDF) sui -- no debconf information -- Samuel Battery 1: charging, 90%, charging at zero rate - will never fully charge. -+- acpi - et pourtant, ca monte -+- --- End Message --- --- Begin Message --- Version: 3.04+git20210103-3 Hello, Florian Schlichting, le sam. 13 mars 2021 18:34:54 +0100, a ecrit: > > wget www.irs.gov/pub/irs-pdf/fw9.pdf > > evince fw9.pdf > > > > then tick some boxes, fill some fields, save. Reopen with evince, both > > fields and check boxes are filled as appropriate. Reopen with xpdf, > > fields get filled, but check boxes do not get ticked. > > I think this has worked for some time, and in my testing today I see > both fields filled in and boxes checked, just like they were in evince. > > Do you agree this bug can be closed? With the current version it seems to be working fine indeed. Samuel--- End Message ---
Bug#985140: marked as done (gobgpd: bash-completion script attempts to source missing file)
Your message dated Sat, 13 Mar 2021 18:03:42 + with message-id and subject line Bug#985140: fixed in gobgp 2.25.0-1 has caused the Debian Bug report #985140, regarding gobgpd: bash-completion script attempts to source missing file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gobgpd Version: 2.18.0-1+b2 Severity: normal Dear Maintainer, gobgp installs a bash-completion script at /usr/share/bash-completion/completions/gobgp which starts with: . `dirname $BASH_SOURCE`/gobgp-static-completion.bash . `dirname $BASH_SOURCE`/gobgp-dynamic-completion.bash Since these files do not exist, it causes the script not to function. Presumably these should be changed to: . `dirname $BASH_SOURCE`/gobgp-static . `dirname $BASH_SOURCE`/gobgp-dynamic To match the files installed by in the gobgp package. Thanks, Kevin --- End Message --- --- Begin Message --- Source: gobgp Source-Version: 2.25.0-1 Done: Vincent Bernat We believe that the bug you reported is fixed in the latest version of gobgp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Bernat (supplier of updated gobgp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 17:57:01 +0100 Source: gobgp Architecture: source Version: 2.25.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Vincent Bernat Closes: 985140 Changes: gobgp (2.25.0-1) unstable; urgency=medium . * New upstream release. * d/lintian-overrides: remove * d/bash-completions: do not rename helper completion scripts (Closes: #985140) Checksums-Sha1: d95412d95616081f752bfbb34983718bf2a7d581 2678 gobgp_2.25.0-1.dsc d605bad0374b747db8b19fba4ed9b2ac82b2250a 865504 gobgp_2.25.0.orig.tar.xz e1bc5194d874b281027bfae876b4484ade4d99c1 3632 gobgp_2.25.0-1.debian.tar.xz 9d7e79a7d64a9a2ee7b0034eb1b1df6ccc1da491 9902 gobgp_2.25.0-1_amd64.buildinfo Checksums-Sha256: 288caee14075e4a97ae629225d16cf226c080445bd31cbd2d4c1608e3689e3f2 2678 gobgp_2.25.0-1.dsc ed54676a39c0817bfacbfad804b9dfe3ef95416d6d13dcbbc4d3aaa3d12c31f5 865504 gobgp_2.25.0.orig.tar.xz 44749cf51d9b1cb063251f47e07af722c950e62ddca12c90c874f143e200d764 3632 gobgp_2.25.0-1.debian.tar.xz 7d08ff30d6a5247428ab62be153829309a07b878650721401df80b4e68b56284 9902 gobgp_2.25.0-1_amd64.buildinfo Files: a2287f1b36487fe55c15f8ea2b944250 2678 net optional gobgp_2.25.0-1.dsc 4e2196353a9a7ac0180399e921b8ae13 865504 net optional gobgp_2.25.0.orig.tar.xz 984d44137afa7d93f48a1de0fb090e7b 3632 net optional gobgp_2.25.0-1.debian.tar.xz c005fef5dd3877f9c12eb9a87d81fa70 9902 net optional gobgp_2.25.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmBM8t4SHGJlcm5hdEBk ZWJpYW4ub3JnAAoJEJWkL+g1NSX5EooP/03vJBSyqQ03h1cwhcTnLmhsbU0LCDig mp9ZpHK2nsLXfa0r7ozpj969eaku9So2K2GD1eSts/cHIiOMCBNVORQUOAIccxjf Rltn2/MDXlm4TXOVfDvK8GNl5O5n/Fo782m/LVyd8Pv4FNodV+VP6oovuU4QiCqV ycaSQLuaRaDjpiC1tvrGBDftrC/fcLU3RT7i4vSKlNgtu4muz4lcr79CdRH8RfW3 B+5YPG7GgEI74xqrghYNd6YT0DmQSroGl8jpVtqy0LEUtIJcnE42h5o9DpxxFIoN QKi3CFA3QO7PTMgPHEGBL6Ia0vLsngLLqB70BD3md+/nEk1KS6X1FNlKElu7EA0L HcuHKEvkhJIKczps73o2E8zAZOLWDTUTe2J7+S5QKWS8wdStBiwjjV93XZpuOSGC 37tMKEV4jcZ+/tKK4Ge7414Bu8FzScgg9czau5ZLtMwCD7O6icDHTx+xE5yonmQg P8W0sczhCPaUGNgL70e+AalWXHpm8yP56dZ8h+Rza7O7HqQh5BmVjwFkyNubK3EX KTzkHMPX3gGYBPf0cKgHg5Q2NwsWMdRtCfIyR/d4/JytNgRhglrU6G1EEP79A758 yKWqdAbLK7vxFUyGfppttYi576tueMqbjLz+sz3TA+wQUrizE5aW+7/f43z1JIia ZWIoBScQ8BXL =dTdF -END PGP SIGNATURE End Message ---
Bug#984881: marked as done (libnvidia-ml-dev: missing libnvidia-ml.so in library search path?)
Your message dated Sat, 13 Mar 2021 18:04:15 + with message-id and subject line Bug#984881: fixed in nvidia-graphics-drivers-tesla-450 450.102.04-2 has caused the Debian Bug report #984881, regarding libnvidia-ml-dev: missing libnvidia-ml.so in library search path? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnvidia-ml-dev Version: 11.2.67~11.2.1-2 Severity: important Hello, While trying to build a program that uses nvml, I am getting: $ gcc transfers.c -o transfers -lnvidia-ml /usr/bin/ld: cannot find -lnvidia-ml collect2: error: ld returned 1 exit status indeed libnvidia-ml-dev doesn't provide a libnvidia-ml.so link in /usr/lib/x86_64-linux-gnu Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnvidia-ml-dev depends on: ii libnvidia-ml1 [libnvidia-ml.so.1] 460.39-1 libnvidia-ml-dev recommends no packages. libnvidia-ml-dev suggests no packages. -- no debconf information -- Samuel il y a 10 catégories de personnes dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-450 Source-Version: 450.102.04-2 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-450, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-450 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 18:43:15 +0100 Source: nvidia-graphics-drivers-tesla-450 Architecture: source Version: 450.102.04-2 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 984881 Changes: nvidia-graphics-drivers-tesla-450 (450.102.04-2) unstable; urgency=medium . * Switch to dh-sequence-dkms (460.56-1). * Simplify dh_dkms usage (460.56-1). * nvidia-tesla-450-alternative: Add libnvidia-ml.so slave alternative if libnvidia-ml-dev is installed (460.56-2). (Closes: #984881) Checksums-Sha1: dbddf8bd12aa4883b60ca35087212f120de7315d 7511 nvidia-graphics-drivers-tesla-450_450.102.04-2.dsc bff0b7e8a8c7ba9ff67fe6b15787342189fe5d08 196308 nvidia-graphics-drivers-tesla-450_450.102.04-2.debian.tar.xz 9152188e04509679cca30347eeb7ecc35e2b074b 7890 nvidia-graphics-drivers-tesla-450_450.102.04-2_source.buildinfo Checksums-Sha256: 4dfa66cc94784a59fdf0fec9520405bf2142880e032fad92e2eb16ebcbe56845 7511 nvidia-graphics-drivers-tesla-450_450.102.04-2.dsc 1b9045a48c8c578ea0c06e222874b6ea4a30debbdb73a7d9ed2b4916f78952a1 196308 nvidia-graphics-drivers-tesla-450_450.102.04-2.debian.tar.xz 1a697593ea223d6302c35949bfc127ae5670a1ef1c6bd2248eb50c3264aa16cb 7890 nvidia-graphics-drivers-tesla-450_450.102.04-2_source.buildinfo Files: 4c3108a15860728dccfa09bba74440c2 7511 non-free/libs optional nvidia-graphics-drivers-tesla-450_450.102.04-2.dsc 6a05851e830da9a8b2f8af792b715120 196308 non-free/libs optional nvidia-graphics-drivers-tesla-450_450.102.04-2.debian.tar.xz eda7f0ed997143bb91d417855b2d0d00 7890 non-free/libs optional nvidia-graphics-drivers-tesla-450_450.102.04-2_source.buildinfo -BEGIN
Bug#384449: marked as done (reading files from stdin)
Your message dated Sat, 13 Mar 2021 18:24:38 +0100 with message-id <20210313172438.gv356...@zedat.fu-berlin.de> and subject line Re: Bug#95574: use of stdin/stdout has caused the Debian Bug report #95574, regarding reading files from stdin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 95574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf-reader Version: 3.01-9 Severity: wishlist I wish I could do generate-pdf-command | xpdf - gv allows it... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages xpdf-reader depends on: ii gsfonts 8.14+v8.11+urw-0.2 Fonts for the Ghostscript interpre ii lesstif2 1:0.94.4-2 OSF/Motif 2.1 implementation relea ii libc6 2.3.6.ds1-2GNU C Library: Shared libraries ii libfreetype6 2.2.1-2FreeType 2 font engine, shared lib ii libgcc1 1:4.1.1-11 GCC support library ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library ii libpaper1 1.1.19 Library for handling paper charact ii libsm61:1.0.0-4 X11 Session Management library ii libstdc++64.1.1-11 The GNU Standard C++ Library v3 ii libt1-5 5.1.0-2Type 1 font rasterizer library - r ii libx11-6 2:1.0.0-8 X11 client-side library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxp61:1.0.0.xsf1-1 X Printing Extension (Xprint) clie ii libxpm4 1:3.5.4.2-3X11 pixmap library ii libxt61:1.0.0-5 X11 toolkit intrinsics library ii xpdf-common 3.01-9 Portable Document Format (PDF) sui ii zlib1g1:1.2.3-13 compression library - runtime xpdf-reader recommends no packages. -- no debconf information -- .''`. martin f. krafft : :' :proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP) --- End Message --- --- Begin Message --- Hi, I see that poppler utils like pdftotext and pdftops have gained the ability to work with stdin/stdout, while xpdf itself has learned to deal with compressed files like report.pdf.gz or plans.pdf.bz2 through its wrapper. I think the features requested in this bug are all present now, so I'm closing this bug (after almost two decades!). Florian--- End Message ---
Bug#198385: marked as done (xpdf should be able to read pdf's from STDIN)
Your message dated Sat, 13 Mar 2021 18:24:38 +0100 with message-id <20210313172438.gv356...@zedat.fu-berlin.de> and subject line Re: Bug#95574: use of stdin/stdout has caused the Debian Bug report #95574, regarding xpdf should be able to read pdf's from STDIN to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 95574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 2.02-2 Severity: wishlist Currently, cat foo.pdf |xpdf -; fails with Error: Couldn't open file '-' It would be useful if xpdf could handle reading a pdf from standard input, instead of relying on temp files to handle this functionality. Don Armstrong -- [Panama, 1989. The U.S. government called it "Operation Just Cause".] I think they misspelled this. Shouldn't it be "Operation Just 'Cause"? -- TekPolitik http://slashdot.org/comments.pl?sid=59669=5664907 http://www.donarmstrong.com http://www.anylevel.com http://rzlab.ucr.edu pgpP5DJbE__MG.pgp Description: PGP signature --- End Message --- --- Begin Message --- Hi, I see that poppler utils like pdftotext and pdftops have gained the ability to work with stdin/stdout, while xpdf itself has learned to deal with compressed files like report.pdf.gz or plans.pdf.bz2 through its wrapper. I think the features requested in this bug are all present now, so I'm closing this bug (after almost two decades!). Florian--- End Message ---
Bug#95574: marked as done (use of stdin/stdout)
Your message dated Sat, 13 Mar 2021 18:24:38 +0100 with message-id <20210313172438.gv356...@zedat.fu-berlin.de> and subject line Re: Bug#95574: use of stdin/stdout has caused the Debian Bug report #95574, regarding use of stdin/stdout to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 95574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 0.92-3 Severity: wishlist It would be nice if the xpdf tools supported the Unixy style of using stdin and stdout streams when the filenames are not presented on the command line. I'm so used to expecting to be able to do things such as: $ zcat foo.pdf.gz | xpdf & $ bzip2 -dc plans.pdf.bz2 | pdftops -upw s3cr3t | lpr -Pcolor $ zcat report.pdf.gz | pdftotext | chef | mail -s Report boss --- End Message --- --- Begin Message --- Hi, I see that poppler utils like pdftotext and pdftops have gained the ability to work with stdin/stdout, while xpdf itself has learned to deal with compressed files like report.pdf.gz or plans.pdf.bz2 through its wrapper. I think the features requested in this bug are all present now, so I'm closing this bug (after almost two decades!). Florian--- End Message ---
Bug#979364: marked as done (nodejs: CVE-2020-8265 CVE-2020-8287)
Your message dated Sat, 13 Mar 2021 17:17:13 + with message-id and subject line Bug#979364: fixed in nodejs 10.23.1~dfsg-1~deb10u1 has caused the Debian Bug report #979364, regarding nodejs: CVE-2020-8265 CVE-2020-8287 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs Version: 12.19.0~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 10.21.0~dfsg-1~deb10u1 Control: found -1 14.13.0~dfsg-1 Hi, The following vulnerabilities were published for nodejs. CVE-2020-8265[0]: | nodejs: use-after-free in TLSWrap CVE-2020-8287[1]: | nodejs: HTTP Request Smuggling If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-8265 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8265 [1] https://security-tracker.debian.org/tracker/CVE-2020-8287 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8287 Regards, Salvatore --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 10.23.1~dfsg-1~deb10u1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Jan 2021 21:29:29 +0100 Source: nodejs Binary: libnode-dev libnode64 libnode64-dbgsym nodejs nodejs-dbgsym nodejs-doc Architecture: source amd64 all Version: 10.23.1~dfsg-1~deb10u1 Distribution: buster-security Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode64 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 979364 Changes: nodejs (10.23.1~dfsg-1~deb10u1) buster-security; urgency=medium . * New upstream version 10.23.1~dfsg. Closes: #979364. Fixed vulnerabilities: + CVE-2020-8265: use-after-free in TLSWrap (High) + CVE-2020-8287: HTTP Request Smuggling (Low) . nodejs (10.22.1~dfsg-1~deb10u1) buster-security; urgency=medium . * New upstream version 10.22.1~dfsg Vulnerabilities fixed: + CVE-2020-8252 fs.realpath.native on may cause buffer overflow (Medium) Checksums-Sha1: abf256a46e9975d98d6675dbae4f728e5eaec0b7 3057 nodejs_10.23.1~dfsg-1~deb10u1.dsc 31b0c0cc7be9a973d354cb43efb5e3f91dd2f34b 16553968 nodejs_10.23.1~dfsg.orig.tar.xz efff795990e36ee433bb706fa16098013c1c142a 100244 nodejs_10.23.1~dfsg-1~deb10u1.debian.tar.xz 4a9dbdc83127243e666abd1b47a87831d1e80fe2 396644 libnode-dev_10.23.1~dfsg-1~deb10u1_amd64.deb db2dd1f422f6869474260f78607f0f37bdd8e787 298944812 libnode64-dbgsym_10.23.1~dfsg-1~deb10u1_amd64.deb 1c63a5369133d32894dbda0120c7a4005a84da7a 5619152 libnode64_10.23.1~dfsg-1~deb10u1_amd64.deb 195c95c60d0302be6b2d5c2a73a96738c0370f38 12964 nodejs-dbgsym_10.23.1~dfsg-1~deb10u1_amd64.deb 51a20dfa3cdaeefd4359c16388de5a962ecdc3fc 973588 nodejs-doc_10.23.1~dfsg-1~deb10u1_all.deb 1ea6fa4c6b647f099897aa25519233a2af979cc7 9262 nodejs_10.23.1~dfsg-1~deb10u1_amd64.buildinfo fc5d10170f3d1bd65950ab70cdef3b93ed1d89dd 87236 nodejs_10.23.1~dfsg-1~deb10u1_amd64.deb Checksums-Sha256: 765dfaa8d9b048ec90608b7917d7492738e8c0e885a1cb560baadac740307581 3057 nodejs_10.23.1~dfsg-1~deb10u1.dsc 0754ead9c34820f5a0bbecd9fd33d28e86ef0e497d3cec4374282c958d956a34 16553968 nodejs_10.23.1~dfsg.orig.tar.xz 453942508fb7b94f8a42d3a1a6389e9f32a4f7d55d8ba0d80609d62370e31872 100244 nodejs_10.23.1~dfsg-1~deb10u1.debian.tar.xz 1d7100e204ef3c2b9bc2cd2e9b7e4d235f2a3bcbac38f470dec010767b54c80e
Bug#984595: marked as done (buster-pu: package samba/2:4.9.5+dfsg-5)
Your message dated Sat, 13 Mar 2021 17:12:31 + with message-id <70e3af961623ecd9008e4dd08f6b51d49dee6c1c.ca...@adam-barratt.org.uk> and subject line Re: Bug#984595: buster-pu: package samba/2:4.9.5+dfsg-5 has caused the Debian Bug report #984595, regarding buster-pu: package samba/2:4.9.5+dfsg-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: mat...@debian.org, math.par...@gmail.com Dear colleagues, Please accept the proposed update of samba in buster / buster-security after the fix closing #984486 gets merged by Mathieu and uploaded to stable queue. [ Reason ] I encountered the missing header include within libsmbclient-dev trying to do a no-change rebuild of ffmpeg 4.3.2 for buster-backports. The problem has been reported to Samba upstream by Gentoo maintainers two years ago there: https://bugs.gentoo.org/666548 and the only contribution I made in re this bug is adapting the patch for Debian's samba source tree: https://salsa.debian.org/samba-team/samba/-/merge_requests/51 [ Impact ] ffmpeg >= 4.3.1-8 will FTBFS due to re-added libsmbclient build-dependency [ Tests ] Build passes, built package from my unofficial Kodi from Debian repo is tested by me & other (several dozen) users. [ Risks ] The risk is low because: * It is a header-only change * It has been accepted by upstream 2 years ago * I confirmed ffmpeg builds fine with modified samba package * Quite many unofficial repo users [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] One patch added, debian/patches/fix-timeval.patch that includes into source3/include/libsmbclient.h [ Other info ] Debdiff will be added after MR gets merged. --- End Message --- --- Begin Message --- On Fri, 2021-03-05 at 18:53 +0100, Sebastian Ramacher wrote: > On 2021-03-05 16:51:44 +, Vasyl Gello wrote: > > Hi Sebastian! > > > > > FWIW, the relevant version for buster-backports is ffmpeg > > > 7:4.3.2-0+deb11u1 which does not require libsmbclient-dev. So the > > > bug in > > > samba does not prevent backports of ffmpeg > > > > Strange, I have noticed that 7:4.3.2-0+deb11u1 sits in > > debian/bullseye branch of ffmpeg, but not in debian/master. > > What is more strange, 'gbp pull --all' does not populate new > > branches so there is no way to distinguish from CLI > > if the new Git branch was cut. > > > > Anyway, I think it is nice to have a fixed samba in buster. Or you > > are not planning to enable smbclient within ffmpeg > > for bullseye at all? > > It's too late to introduce new binary packages in bullseye. The > changes > in debian/master are already for bookworm. That's why I have branched > of > debian/bullseye before the experimental uploads. smbclient in ffmpeg > won't happen for bullseye. That sounds like there's no practical issue with the package in buster, and therefore no need for an update. Regards, Adam--- End Message ---
Bug#984665: marked as done (CVE-2021-25900)
Your message dated Sat, 13 Mar 2021 16:48:43 + with message-id and subject line Bug#984665: fixed in rust-smallvec 1.4.2-2 has caused the Debian Bug report #984665, regarding CVE-2021-25900 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-smallvec Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team https://rustsec.org/advisories/RUSTSEC-2021-0003.html https://github.com/servo/rust-smallvec/issues/252 Cheers, Moritz --- End Message --- --- Begin Message --- Source: rust-smallvec Source-Version: 1.4.2-2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-smallvec, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-smallvec package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Mar 2021 16:28:35 + Source: rust-smallvec Architecture: source Version: 1.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 984665 Changes: rust-smallvec (1.4.2-2) unstable; urgency=medium . * Team upload. * Package smallvec 1.4.2 from crates.io using debcargo 2.4.3 * Apply upstream patch to fix overflow in insert_many ( Closes: 984665 ) Checksums-Sha1: b176930122b5038f18a2692c9c13d1a8ec0eebc8 2288 rust-smallvec_1.4.2-2.dsc 3faa893899858c9ddf77842424b0b11241c0d892 4676 rust-smallvec_1.4.2-2.debian.tar.xz 54b3d9a3c6623d15a8bd8c503368a411de548cd4 7005 rust-smallvec_1.4.2-2_source.buildinfo Checksums-Sha256: e216bc72df7cee0b8b32b147161320360a2bd6ae0203c8cb2d45ad621af5ec66 2288 rust-smallvec_1.4.2-2.dsc 8a47b4aefed9d17dfe1f2894bfa671ec5f746ab2dce911b7af7470e226bc9757 4676 rust-smallvec_1.4.2-2.debian.tar.xz 04857fe24f49dfea4231bb22a438e2804335a33d03a8ebfec75246ca62591662 7005 rust-smallvec_1.4.2-2_source.buildinfo Files: 42e5313231c2f0ba8df73631fd75c8a2 2288 rust optional rust-smallvec_1.4.2-2.dsc 5c3672232527790cdac15307c6920cfa 4676 rust optional rust-smallvec_1.4.2-2.debian.tar.xz 37b524b07f03bfd435d650c532c81481 7005 rust optional rust-smallvec_1.4.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmBM6OUUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xsh+g//Ze5hxThaaXt7vLYSzj1I13VKhtWT En3SzglXZExqTZqDqyBvu8W1QoevUvKs9S9bhkSJwE2mFQ/3kGNG3M1yLyGPQgxh x2jRh7z04Jyo1E0vyZTXyHC54LbvsczgMnyba51on6IseUcx9Cuo+4qzwoDBmIlh oKDb153qZiJ+zC0LeBdh3z+Wh8lYUWiPm8arjMhs3JA+6wfI/GsjIgd/COin6/au PoI9gDda8XybF7uygOGc0pqLGw57p9rPbjJUimJoUmGTfR86siuk2yezF0hODdvv kPKCdT8d/yDjcGkcIWVlyTdjAA4naLTUwqd2wnqO43qnab6789kzZ5G78ejrKfxW NLZVigtb2xG/yt7SbzBVYMUrINznO96KIv/+PzuDNjPF7f5LqUQOrsnXq7SE/38v oFKEx4FuEa6M3OyrzEmcagDtv3A/NXATdPXFdNgYvExsgiwUXp2/KgwX5vQHboFF tQ+/3o6ZleRbQx/eewiqfW96ABSTxZ44ThM6IOsKV+w/bzFYyjTI22MyK8Kqg9qy hB/1YkHLR3zchpjsCJFB6erLTqIwvCqrUq7E82uZEoUPzn1CU/unxItaP6bPM2Xt acEqCwhEKhuSOhCnH2CipCCY/wRzOpayWq6P2ABwX1VUyIen2P8HQnF+7orbrsNC 2b9iIDuMdqjw1Ac= =PxzF -END PGP SIGNATURE End Message ---
Bug#984529: marked as done (rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1))
Your message dated Sat, 13 Mar 2021 11:19:38 -0500 with message-id <70f6d8092aa60e6adfe45785eee643887c4608bd.ca...@debian.org> and subject line Re: rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1) has caused the Debian Bug report #984529, regarding rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rheolef Version: 7.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../51-rheolef_7.1-3_amd64.deb ... Unpacking rheolef (7.1-3) over (7.0-2+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-qDgNC1/51-rheolef_7.1-3_amd64.deb (--unpack): trying to overwrite '/usr/bin/rheolef-config', which is also in package librheolef-dev 7.0-2+b1 Preparing to unpack .../52-librheolef-dev_7.1-3_amd64.deb ... Unpacking librheolef-dev (7.1-3) over (7.0-2+b1) ... cheers, Andreas rheolef_7.1-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 7.1-5 On Fri, 12 Mar 2021 11:20:17 +0100 Andreas Beckmann wrote: > Followup-For: Bug #984529 > Control: found -1 7.1-4 > > Hi, > > rheolef has Breaks+Replaces against rheolef-dev, a package that never > existed. You want librheolef-dev there ;-) I believe this is fixed in the recent 7.1-5. The latest autopkgtest has also passed. I will file an unblock request soon. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#977702: marked as done (firmware-brcm80211: brcmfmac43455 on RPi4 causes hostapd to fail silently)
Your message dated Sat, 13 Mar 2021 17:08:19 +0100 with message-id and subject line Re: firmware-brcm80211: brcmfmac43455 on RPi4 causes hostapd to fail silently has caused the Debian Bug report #977702, regarding firmware-brcm80211: brcmfmac43455 on RPi4 causes hostapd to fail silently to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-brcm80211 Version: 20200918-1~bop10+1 Severity: normal Dear Maintainer, Steps to reproduce: 1. flash latest tested Raspberry Pi 4 image and boot 2. update all packages 3. install hostapd 4. configure the onboard wlan device as an 802.11n AP Expected results: AP works Actual results: hostapd claims the AP is enabled, but it's actually not Work-around: 1. apt purge firmware-brcm80211 2. cp /lib/firmware/brcm/brcmfmac43455.* from a current stable Raspbian install - this appears to work even despite the fact that Raspbian is 32-bit - the driver still throws a warning about a missing brcmfmac43455-sdio.raspberrypi,4-model-b.txt file, but this file is not included with stable Raspbian, and its absence doesn't appear to cause any problems beyond the warning The brcmfmac43455 firmware in firmware-brcm80211 appears to be much older than what Raspbian stable is currently shipping -- System Information: Debian Release: 10.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: arm64 (aarch64) Kernel: Linux 5.9.0-0.bpo.2-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.133+deb10u1 --- End Message --- --- Begin Message --- Version: 20210208-4 Thanks latest upstream version in unstable is known to work with hostapd. (attention current -3 testing version is known to *not* work on RPi4) if the original issues are still reproducible with 20210208-4, please let us know together with relevant hostapd.conf. thank you. -- maks signature.asc Description: PGP signature --- End Message ---
Bug#983688: marked as done (tasksel-data: gnome-flashback-desktop task in Japanese environment should pull task-japanese-gnome-desktop)
Your message dated Sat, 13 Mar 2021 16:03:25 + with message-id and subject line Bug#983688: fixed in tasksel 3.65 has caused the Debian Bug report #983688, regarding tasksel-data: gnome-flashback-desktop task in Japanese environment should pull task-japanese-gnome-desktop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tasksel-data Version: 3.64 Severity: important Tags: bullseye l10n patch Dear Maintainer, The GNOME Flashback desktop is similar to the original GNOME desktop. For Japanese users, when the GNOME Flashback desktop is installed, it is expected to also install the task-japanese-gnome-desktop package. The attached patch adds "japanese-gnome-flashback-desktop" Task which behaves just like "japanese-gnome-desktop" Task for "gnome-flashback-desktop" Task, which installs the task-japanese-gnome-desktop package. Note that this patch does NOT add a new binary package, but just adds a new Task. Thanks in advance, -- YOSHINO Yoshihito -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/1 CPU thread) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tasksel-data depends on: ii tasksel 3.64 Versions of packages tasksel-data recommends: ii laptop-detect 0.16 tasksel-data suggests no packages. -- no debconf information --- tasksel-3.64/tasks/japanese-gnome-flashback-desktop 1970-01-01 09:00:00.0 +0900 +++ tasksel-3.64/tasks/japanese-gnome-flashback-desktop 2021-02-28 17:37:14.982899811 +0900 @@ -0,0 +1,5 @@ +Task: japanese-gnome-flashback-desktop +Enhances: gnome-flashback-desktop, japanese-desktop +Section: l10n +Key: + task-japanese-gnome-desktop --- End Message --- --- Begin Message --- Source: tasksel Source-Version: 3.65 Done: Holger Wansing We believe that the bug you reported is fixed in the latest version of tasksel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of updated tasksel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 16:26:46 +0100 Source: tasksel Architecture: source Version: 3.65 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Closes: 982043 982175 983074 983688 Changes: tasksel (3.65) unstable; urgency=medium . * Team upload. . [ HIGUCHI Daisuke ] * tasksel-japanese-desktop: prefer uim-mozc over uim-anthy (Closes: #982175) . [ Holger Wansing ] * Re-add manpages-it to task-italian task (package is again available in unstable/testing). Closes: #982043. * Add manpages translations from newly introduced manpages-l10n package (manpages-pt-br, manpages-nl, manpages-mk, manpages-ro, manpages-es) to the respective language tasks (see #982043). * Re-add synaptic to gnome desktop tasks. Closes: #983074 * Remove scim-qt-immodule from task-chinese-t-kde-desktop, since it's no longer in the archive. . [ YOSHINO Yoshihito ] * Let gnome-flashback-desktop task in Japanese pull task-japanese-gnome-desktop. Closes: #983688 Checksums-Sha1: d9f25ba3157627be6161e93f23d06baf6b9f2434 17065 tasksel_3.65.dsc 737abaa72a5614e85cf0d46c8acc563ce9957066 295340 tasksel_3.65.tar.xz 08d061992cd0a8635035fc097302be3515521237 65609 tasksel_3.65_amd64.buildinfo Checksums-Sha256: abac42b83b151bbdfe690922db46423c2d14f7f0c44fbc63b836487e56b45926 17065 tasksel_3.65.dsc 9d5daaa26ac608085dce740fc63c5793c2e26b78f1a33224fea9dd7b81dcd395 295340 tasksel_3.65.tar.xz bec4a37a32a9560dc61b84468d836d23b3e099cd119b71f66dab51a4731c0545 65609 tasksel_3.65_amd64.buildinfo Files: 75eaccad5b334093d1bd92746ccfe90f 17065 tasks optional tasksel_3.65.dsc 48902b77ae76405ef1b11c8733394a66
Bug#982175: marked as done (task-japanese-desktop: should explicitly prefer mozc over anthy)
Your message dated Sat, 13 Mar 2021 16:03:25 + with message-id and subject line Bug#982175: fixed in tasksel 3.65 has caused the Debian Bug report #982175, regarding task-japanese-desktop: should explicitly prefer mozc over anthy to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: task-japanese-desktop Version: 3.63 Tags: bullseye patch Priority: important Dear Maintainer, Most Japanese users prefer "mozc" over "anthy" among several Japanese input method engines. Because mozc is supported upstream in limited architectures (x86 and arm related only) anthy has been used as a fall-back. However, the recent bullseye debian installer does not configure the system as expected. When the buster (or earlier) debian installer installs japanese-desktop task it configures (runs postinst maintainer scripts of) the uim-* input method packages in the following order: uim-anthy uim-mozc buster dpkg.log: 2021-01-31 12:47:57 install uim-anthy:all <なし> 1:1.8.8-4+deb10u3 2021-01-31 12:47:57 status half-installed uim-anthy:all 1:1.8.8-4+deb10u3 2021-01-31 12:47:57 status unpacked uim-anthy:all 1:1.8.8-4+deb10u3 (snip) 2021-01-31 12:51:44 install uim-mozc:amd64 <なし> 2.23.2815.102+dfsg-4 2021-01-31 12:51:44 status half-installed uim-mozc:amd64 2.23.2815.102+dfsg-4 2021-01-31 12:51:44 status unpacked uim-mozc:amd64 2.23.2815.102+dfsg-4 (snip) 2021-01-31 12:53:58 configure uim-anthy:all 1:1.8.8-4+deb10u3 <なし> 2021-01-31 12:53:58 status unpacked uim-anthy:all 1:1.8.8-4+deb10u3 2021-01-31 12:53:58 status half-configured uim-anthy:all 1:1.8.8-4+deb10u3 2021-01-31 12:53:58 status installed uim-anthy:all 1:1.8.8-4+deb10u3 (snip) 2021-01-31 12:54:04 configure uim-mozc:amd64 2.23.2815.102+dfsg-4 <なし> 2021-01-31 12:54:04 status unpacked uim-mozc:amd64 2.23.2815.102+dfsg-4 2021-01-31 12:54:04 status half-configured uim-mozc:amd64 2.23.2815.102+dfsg-4 2021-01-31 12:54:04 status installed uim-mozc:amd64 2.23.2815.102+dfsg-4 which makes uim input method framework configured in the desirable preference ordering, because the uim-* input method packages are structured as LIFO: last configured package is preferred first. However, the recent bullseye debian installer (perhaps recent apt or dpkg algorithm) has been changed for some reason. It configures the uim-* input method packages in the following order: uim-mozc uim-anthy bullseye dpkg.log: 2021-01-31 10:55:44 install uim-anthy:all 1:1.8.8-7 2021-01-31 10:55:44 status half-installed uim-anthy:all 1:1.8.8-7 2021-01-31 10:55:44 status unpacked uim-anthy:all 1:1.8.8-7 (snip) 2021-01-31 10:58:47 install uim-mozc:amd64 2.26.4220.100+dfsg-2 2021-01-31 10:58:47 status half-installed uim-mozc:amd64 2.26.4220.100+dfsg-2 2021-01-31 10:58:47 status unpacked uim-mozc:amd64 2.26.4220.100+dfsg-2 (snip) 2021-01-31 11:00:36 configure uim-mozc:amd64 2.26.4220.100+dfsg-2 2021-01-31 11:00:36 status unpacked uim-mozc:amd64 2.26.4220.100+dfsg-2 2021-01-31 11:00:36 status half-configured uim-mozc:amd64 2.26.4220.100+dfsg-2 2021-01-31 11:00:36 status installed uim-mozc:amd64 2.26.4220.100+dfsg-2 (snip) 2021-01-31 11:00:38 configure uim-anthy:all 1:1.8.8-7 2021-01-31 11:00:38 status unpacked uim-anthy:all 1:1.8.8-7 2021-01-31 11:00:38 status half-configured uim-anthy:all 1:1.8.8-7 2021-01-31 11:00:38 status installed uim-anthy:all 1:1.8.8-7 Since depending on the dpkg configuration order is inherently fragile, it should be avoided. It should be better to adjust the dependency field in the task package. The attached patch should fix this problem. Thanks in advance, -- YOSHINO Yoshihito --- tasksel-3.63/debian/control 2020-12-21 01:58:07.0 +0900 +++ tasksel-3.63/debian/control 2021-02-07 16:06:00.487409455 +0900 @@ -1410,8 +1410,7 @@ fonts-vlgothic, fonts-ipafont, uim, - uim-anthy, - uim-mozc, + uim-mozc | uim-anthy, mozc-utils-gui, anthy, libreoffice-l10n-ja, --- End Message --- --- Begin Message --- Source: tasksel Source-Version: 3.65 Done: Holger Wansing We believe that the bug you reported is fixed in the latest version of tasksel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of
Bug#982043: marked as done (tasksel: please re-add manpages-it to 'task-italian' task, when available in unstable)
Your message dated Sat, 13 Mar 2021 16:03:25 + with message-id and subject line Bug#982043: fixed in tasksel 3.65 has caused the Debian Bug report #982043, regarding tasksel: please re-add manpages-it to 'task-italian' task, when available in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tasksel Severity: wishlist Tags: l10n Hi, manpages-it has been remove from tasksel's depends, since package was kicked out of unstable (see #982035 and #979034). It should be re-added to unstable some day though, so filing this bug as a reminder to reinstate the corresponding dependency. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 --- End Message --- --- Begin Message --- Source: tasksel Source-Version: 3.65 Done: Holger Wansing We believe that the bug you reported is fixed in the latest version of tasksel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of updated tasksel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 16:26:46 +0100 Source: tasksel Architecture: source Version: 3.65 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Closes: 982043 982175 983074 983688 Changes: tasksel (3.65) unstable; urgency=medium . * Team upload. . [ HIGUCHI Daisuke ] * tasksel-japanese-desktop: prefer uim-mozc over uim-anthy (Closes: #982175) . [ Holger Wansing ] * Re-add manpages-it to task-italian task (package is again available in unstable/testing). Closes: #982043. * Add manpages translations from newly introduced manpages-l10n package (manpages-pt-br, manpages-nl, manpages-mk, manpages-ro, manpages-es) to the respective language tasks (see #982043). * Re-add synaptic to gnome desktop tasks. Closes: #983074 * Remove scim-qt-immodule from task-chinese-t-kde-desktop, since it's no longer in the archive. . [ YOSHINO Yoshihito ] * Let gnome-flashback-desktop task in Japanese pull task-japanese-gnome-desktop. Closes: #983688 Checksums-Sha1: d9f25ba3157627be6161e93f23d06baf6b9f2434 17065 tasksel_3.65.dsc 737abaa72a5614e85cf0d46c8acc563ce9957066 295340 tasksel_3.65.tar.xz 08d061992cd0a8635035fc097302be3515521237 65609 tasksel_3.65_amd64.buildinfo Checksums-Sha256: abac42b83b151bbdfe690922db46423c2d14f7f0c44fbc63b836487e56b45926 17065 tasksel_3.65.dsc 9d5daaa26ac608085dce740fc63c5793c2e26b78f1a33224fea9dd7b81dcd395 295340 tasksel_3.65.tar.xz bec4a37a32a9560dc61b84468d836d23b3e099cd119b71f66dab51a4731c0545 65609 tasksel_3.65_amd64.buildinfo Files: 75eaccad5b334093d1bd92746ccfe90f 17065 tasks optional tasksel_3.65.dsc 48902b77ae76405ef1b11c8733394a66 295340 tasks optional tasksel_3.65.tar.xz 1b9414df676a35c3b9890ceb47deb8ee 65609 tasks optional tasksel_3.65_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmBM3OoVHGh3YW5zaW5n QG1haWxib3gub3JnAAoJEFnxh8oVbrB2C6EP/ApHj6lw1+NhAwCCnZsv0LMB39qK Vhbp2YPnhaTHtFh7AyRNRQKcDRCgb3GrchGO0YKV774PPBNSR7G9rN/R8lAK7lR/ veB+BSGxVMiMF7wsNx2D5hkQcj6WaEYcNOpO0lgyr+RmN5/ENtK7dzaOFqL0LS7l DCavbGOPWjJOzx1+munYX3Smb7UOmYf3IgUgKEeAK8sO+X2pRaZ9kkOyBYaOn/pu EUui9NTJEjHdFAs5EbnTXgBDEkM1CLoF8uWPMbnr4m5ZuJZ5yYqIiheaX1p2I5RL qylYxex5vhqISBJ6yQkN9NneX8OIkThCCbdsGXMZ+8t16HOG5yHUaW+dwaJrESSY RNsQZfPZ3MvCCP4jhbuG0XzpwtYJ6KQFshLH3QFe2Fmird3R0wZSHJnvWeCn1Bmr vRzBqliGELgypRmB+pdxvTmnn4cPTxfiaUkmZloz38lcFxsI9aGPe1a8YpFzx1Wh IrbC2alJq8Yf7ZB1VJSt5GsYyp43PZdFFW14P1CjXu9FfoE1AVzbfsQNWAYlJkem vsKaaBjp5TXlEKEb625x6mT0WV/MS63oa3zeQEl+fYFrMPla5iCaVC1FxgEW8Isp 1qJiUrUg0oBvdhlswf1y0s3zyBI1/E6NiEpjLX36suAimBnlvL5W9oRfHKHjLFRq S+3G570SnVxBzbMn =0A4V -END PGP SIGNATURE End Message ---
Bug#983074: marked as done (task-gnome-desktop: Please consider recommending synaptic again)
Your message dated Sat, 13 Mar 2021 16:03:25 + with message-id and subject line Bug#983074: fixed in tasksel 3.65 has caused the Debian Bug report #983074, regarding task-gnome-desktop: Please consider recommending synaptic again to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: task-gnome-desktop Version: 3.63 Severity: normal Tags: d-i Hello maintainers of task-gnome-desktop, Synaptic used to be recommended by task-gnome-desktop (and other task-*-desktop), until it was removed from Buster (#889897), due to it not functionning correctly under Wayland. Under GNOME, users have been left with gnome-software to install packages, but gnome-software only shows packages shipping AppStream metadata, thus most packages don't show up there, such as mat2, nautilus-wipe, sm and many more. Installing packages not available in gnome-software nowadays requires the use of a terminal, or gnome-packagekit, which is also not installed by default. Gnome-packagekit does the job and has a prettier interface, but its developpment is much slower than synaptic's (regarding commits in the last 2 years). Shipping synaptic by default in Debian Bullseye with GNOME, XFCE, LXDE, Mate and Cinnamon would be a great (re)improvement in user experience, giving users more control without the need of mastering terminal usage. Thank you very much, gagz --- End Message --- --- Begin Message --- Source: tasksel Source-Version: 3.65 Done: Holger Wansing We believe that the bug you reported is fixed in the latest version of tasksel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of updated tasksel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 16:26:46 +0100 Source: tasksel Architecture: source Version: 3.65 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Closes: 982043 982175 983074 983688 Changes: tasksel (3.65) unstable; urgency=medium . * Team upload. . [ HIGUCHI Daisuke ] * tasksel-japanese-desktop: prefer uim-mozc over uim-anthy (Closes: #982175) . [ Holger Wansing ] * Re-add manpages-it to task-italian task (package is again available in unstable/testing). Closes: #982043. * Add manpages translations from newly introduced manpages-l10n package (manpages-pt-br, manpages-nl, manpages-mk, manpages-ro, manpages-es) to the respective language tasks (see #982043). * Re-add synaptic to gnome desktop tasks. Closes: #983074 * Remove scim-qt-immodule from task-chinese-t-kde-desktop, since it's no longer in the archive. . [ YOSHINO Yoshihito ] * Let gnome-flashback-desktop task in Japanese pull task-japanese-gnome-desktop. Closes: #983688 Checksums-Sha1: d9f25ba3157627be6161e93f23d06baf6b9f2434 17065 tasksel_3.65.dsc 737abaa72a5614e85cf0d46c8acc563ce9957066 295340 tasksel_3.65.tar.xz 08d061992cd0a8635035fc097302be3515521237 65609 tasksel_3.65_amd64.buildinfo Checksums-Sha256: abac42b83b151bbdfe690922db46423c2d14f7f0c44fbc63b836487e56b45926 17065 tasksel_3.65.dsc 9d5daaa26ac608085dce740fc63c5793c2e26b78f1a33224fea9dd7b81dcd395 295340 tasksel_3.65.tar.xz bec4a37a32a9560dc61b84468d836d23b3e099cd119b71f66dab51a4731c0545 65609 tasksel_3.65_amd64.buildinfo Files: 75eaccad5b334093d1bd92746ccfe90f 17065 tasks optional tasksel_3.65.dsc 48902b77ae76405ef1b11c8733394a66 295340 tasks optional tasksel_3.65.tar.xz 1b9414df676a35c3b9890ceb47deb8ee 65609 tasks optional tasksel_3.65_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmBM3OoVHGh3YW5zaW5n QG1haWxib3gub3JnAAoJEFnxh8oVbrB2C6EP/ApHj6lw1+NhAwCCnZsv0LMB39qK Vhbp2YPnhaTHtFh7AyRNRQKcDRCgb3GrchGO0YKV774PPBNSR7G9rN/R8lAK7lR/ veB+BSGxVMiMF7wsNx2D5hkQcj6WaEYcNOpO0lgyr+RmN5/ENtK7dzaOFqL0LS7l DCavbGOPWjJOzx1+munYX3Smb7UOmYf3IgUgKEeAK8sO+X2pRaZ9kkOyBYaOn/pu
Bug#984489: marked as done (firmware-brcm80211: newer versions fail to load on raspberry pi 4b with "brcmf_sdio_htclk: HT Avail timeout")
Your message dated Sat, 13 Mar 2021 15:34:02 + with message-id and subject line Bug#984489: fixed in firmware-nonfree 20210208-4 has caused the Debian Bug report #984489, regarding firmware-brcm80211: newer versions fail to load on raspberry pi 4b with "brcmf_sdio_htclk: HT Avail timeout" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-brcm80211 Version: 20210208-3 Severity: important The version of firmware-brcm80211 in bullseye (specifically 20201218-3) works fine on my Rasperry Pi 4 board. However, the version in sid does not. Specifically, the brcmfmac kernel driver fails to load with some clock errors. Here's snippets from boot dmesg: [0.00] Linux version 5.10.0-3-arm64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.13-1 (2021-02-06) [0.00] Machine model: Raspberry Pi 4 Model B Rev 1.1 [...] [ 10.308867] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 10.318818] usbcore: registered new interface driver brcmfmac [ 10.322875] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4]) [ 10.335422] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops [vc4]) [ 10.343356] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4]) [ 10.350443] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 10.358185] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 10.365828] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 10.373704] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 10.376815] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.bin [ 10.384437] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 [ 10.398479] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt [...] [ 11.462064] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 [...] [ 12.471809] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 You can specifically see that the driver times out after one second with that error message, then times out again with the error and gives up. No wlan0 is available. There are some pretty major firmware updates between those two versions, and they are generally Good. However, there's also some minor updates to the raspi4 board file /lib//firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt If we revert the line "boardflags3=0x48200100" in that file back to what was in the 20201218-3 version (so it would instead be "boardflags3=0x44200100"), and then reboot, the driver now loads: [ 13.342844] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 13.353195] usbcore: registered new interface driver brcmfmac [ 13.465495] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.bin [ 13.472403] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 13.488397] hub 1-1:1.0: 4 ports detected [ 13.488428] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 13.500413] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt [ 13.673868] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 13.812345] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd [ 13.856502] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.clm_blob [ 13.869572] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Sep 18 2020 02:27:58 version 7.45.221 (3a6d3a0 CY) FWID 01-bbd9282b [...] [ 23.951744] br0: port 2(wlan0) entered blocking state [ 23.953859] br0: port 2(wlan0) entered disabled state [ 23.956221] device wlan0 entered promiscuous mode [ 23.961230] br0: port 3(wlan1) entered blocking state [ 23.963358] br0: port 3(wlan1) entered disabled state [ 23.966488] device wlan1 entered promiscuous mode [ 29.417766] br0: port 2(wlan0) entered blocking state [ 29.419853] br0: port 2(wlan0) entered forwarding state I'm not sure if the driver needs fixing, or if the boardflags need fixing, but the boardflags thing seems to be a functional workaround for users hitting this issue. Thanks to Steev Klimaszewski for helping me figure out the workaround. --- End Message --- --- Begin Message
Bug#982579: marked as done (Failed to load firmware brcmfmac43430-sdio at BananaPi M2)
Your message dated Sat, 13 Mar 2021 15:34:02 + with message-id and subject line Bug#982579: fixed in firmware-nonfree 20210208-4 has caused the Debian Bug report #982579, regarding Failed to load firmware brcmfmac43430-sdio at BananaPi M2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-brcm80211 Version: 20201218-3 Hello, At my BananaPi M2 Ultra, loading firmware failed: > [ 10.514530] brcmfmac mmc2:0001:1: firmware: direct-loading firmware > brcm/brcmfmac43430-sdio.bin > [ 10.514732] brcmfmac mmc2:0001:1: firmware: failed to load > brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt ( > -2) > [ 10.525149] firmware_class: See https://wiki.debian.org/Firmware for > information about missing firmware > [ 10.534664] brcmfmac mmc2:0001:1: Direct firmware load for > brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt f > ailed with error -2 > [ 10.551207] brcmfmac mmc2:0001:1: firmware: failed to load > brcm/brcmfmac43430-sdio.txt (-2) > [ 10.559692] brcmfmac mmc2:0001:1: Direct firmware load for > brcm/brcmfmac43430-sdio.txt failed with error -2 > Please add the corresponding firmware. Best regards and thank you for the great support. Bernhard signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: firmware-nonfree Source-Version: 20210208-4 Done: maximilian attems We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 13:23:22 +0100 Source: firmware-nonfree Binary: firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc firmware-qlogic firmware-realtek firmware-samsung firmware-siano firmware-ti-connectivity Architecture: source all Version: 20210208-4 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: maximilian attems Description: firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards firmware-cavium - Binary firmware for Cavium Ethernet adapters firmware-intel-sound - Binary firmware for Intel sound DSPs firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (metapack firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel (metapack firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netronome - Binary firmware for Netronome network adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qcom-media - Binary firmware for Qualcomm graphics/video (dummy package) firmware-qcom-soc - Binary firmware for Qualcomm SoCs firmware-qlogic - Binary firmware for QLogic HBAs firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters firmware-samsung
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 981283 minor Bug #981283 [nsd] Should the daemon started at postinst? Severity set to 'minor' from 'normal' > close 981283 Bug #981283 [nsd] Should the daemon started at postinst? Marked Bug as done > severity 938987 minor Bug #938987 [nsd] Overly restrictive CapabilityBoundingSet Severity set to 'minor' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 938987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938987 981283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 664219
Processing commands for cont...@bugs.debian.org: > close 664219 2.3.1-1 Bug #664219 [l2tpns] Squeeze l2tpns, network latency and high CPU Utilization Marked as fixed in versions l2tpns/2.3.1-1. Bug #664219 [l2tpns] Squeeze l2tpns, network latency and high CPU Utilization Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 664219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 462369
Processing commands for cont...@bugs.debian.org: > close 462369 2.3.1-1 Bug #462369 [l2tpns] l2tpns: Configuration option 'bind_address' documentation is misleading Marked as fixed in versions l2tpns/2.3.1-1. Bug #462369 [l2tpns] l2tpns: Configuration option 'bind_address' documentation is misleading Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 462369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985136: marked as done (unblock: gnome-passwordsafe/5.0-2)
Your message dated Sat, 13 Mar 2021 14:31:59 +
with message-id
and subject line unblock gnome-passwordsafe
has caused the Debian Bug report #985136,
regarding unblock: gnome-passwordsafe/5.0-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
985136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gnome-passwordsafe
[ Reason ]
Fix a bug that prevents the icon of the application from being displayed
when the software is running in a Wayland session.
[ Impact ]
Wayland won't show the icon of gnome-passwordsafe while it is running
(in the taskbar).
[ Tests ]
This issue is fixed with a one line patch provided by upstream.
Manual tests of the newer version show the bug is fixed.
[ Risks ]
Code change is trivial and very limited. I consider the risk to be low.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
unblock gnome-passwordsafe/5.0-2
diff -Nru gnome-passwordsafe-5.0/debian/changelog
gnome-passwordsafe-5.0/debian/changelog
--- gnome-passwordsafe-5.0/debian/changelog 2021-02-07 21:03:23.0
+
+++ gnome-passwordsafe-5.0/debian/changelog 2021-03-10 16:46:52.0
+
@@ -1,3 +1,10 @@
+gnome-passwordsafe (5.0-2) unstable; urgency=medium
+
+ * d/patches: add 001_fix-app-name
+Display the app icon correctly in Wayland environments
+
+ -- Henry-Nicolas Tourneur Wed, 10 Mar 2021 16:46:52 +
+
gnome-passwordsafe (5.0-1) unstable; urgency=medium
* New upstream version 5.0
diff -Nru gnome-passwordsafe-5.0/debian/patches/001_fix-app-name.patch
gnome-passwordsafe-5.0/debian/patches/001_fix-app-name.patch
--- gnome-passwordsafe-5.0/debian/patches/001_fix-app-name.patch
1970-01-01 00:00:00.0 +
+++ gnome-passwordsafe-5.0/debian/patches/001_fix-app-name.patch
2021-03-10 16:46:52.0 +
@@ -0,0 +1,19 @@
+Author: David Heidelberg
+Forwarded: https://gitlab.gnome.org/World/PasswordSafe/-/merge_requests/487
+Description: set prgname to application_id
+ This fixes issue with the icon inside Wayland environment.
+ Wayland expect that prgname matches application_id, otherwise refuse to
+ show the icon.
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/passwordsafe/application.py
b/passwordsafe/application.py
+@@ -43,7 +43,7 @@ class Application(Gtk.Application):
+ def do_startup(self): # pylint: disable=arguments-differ
+ Gtk.Application.do_startup(self)
+ GLib.set_application_name('Password Safe')
+-GLib.set_prgname("Password Safe")
++GLib.set_prgname(self.application_id)
+
+ Handy.init()
+ self.connect("open", self.file_open_handler)
diff -Nru gnome-passwordsafe-5.0/debian/patches/series
gnome-passwordsafe-5.0/debian/patches/series
--- gnome-passwordsafe-5.0/debian/patches/series2021-02-07
21:03:23.0 +
+++ gnome-passwordsafe-5.0/debian/patches/series2021-03-10
16:40:16.0 +
@@ -1 +1,2 @@
+001_fix-app-name.patch
000_fix-mime-path.patch
--- End Message ---
--- Begin Message ---
Unblocked gnome-passwordsafe.--- End Message ---
Processed: closing 928842
Processing commands for cont...@bugs.debian.org: > close 928842 2.3.3-1 Bug #928842 [src:l2tpns] l2tpns FTCBFS: does not pass cross tools to make Bug #977569 [src:l2tpns] l2tpns FTCBFS: uses the build architecture compiler Marked as fixed in versions l2tpns/2.3.3-1. Marked as fixed in versions l2tpns/2.3.3-1. Bug #928842 [src:l2tpns] l2tpns FTCBFS: does not pass cross tools to make Bug #977569 [src:l2tpns] l2tpns FTCBFS: uses the build architecture compiler Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 928842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928842 977569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929214: marked as done (Add key package for cloud images)
Your message dated Sat, 13 Mar 2021 15:30:39 +0100 with message-id <20210313143037.ga27...@debian.org> and subject line Re: Bug#929214: release.debian.org - Add package constraint for cloud images has caused the Debian Bug report #929214, regarding Add key package for cloud images to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 929214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Hi release team To make your and our work easier, we would like to ask you to add a package constraint for all the packages included into the official Debianm cloud images. >From what I read, the easiest way for you would be to specify a single package as constraint, a package that depends on all the other binary package we explicitely include in the images. I intend to add one binary package per architecture we currently build images for: amd64, arm64 and ppc64el. The dependencies will be arch dependent and auto-generated from our own list. The package would look like this: | Package: debian-cloud-images-packages | Architecture: amd64 | Depends: apparmor, awscli, chrony, cloud-init, cloud-initramfs-growroot, google-compute-engine, grub-cloud-amd64, grub-pc, libpam-systemd, linux-image-amd64, linux-image-cloud-amd64, openssh-server, python, python-boto, python3-boto, sudo, unattended-upgrades, waagent Please acknowledge that such a package would be okay for using as constraint. After that I'll upload that change. Regards, Bastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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) --- End Message --- --- Begin Message --- Hi Bastian, On Fri, Mar 12, 2021 at 08:14:58AM +0100, Bastian Blank wrote: > > > Please acknowledge that such a package would be okay for using as > > > constraint. After that I'll upload that change. > > If you create such a package, having a binary per architecture as you > > describe, should do what you want. It can be added to the list as soon as it > > is in testing. > > The binary package is in testing since some time. Please add it to the > key packages list. Added. FYI this currently adds the following packages as key packages: awscli chrony cloud-init cloud-initramfs-tools cloud-utils debian-cloud-images fai google-compute-image-packages grub-cloud ifenslave libcloud libextutils-cchecker-perl libfile-lchown-perl liblinux-lvm-perl python-bcdoc python-boto python-httpretty python-lockfile python-marshmallow python-rednose python-sure python-termstyle vlan Cheers, Ivo--- End Message ---
Bug#985134: marked as done (nginx: please provide nginx-dev package for packaging 3rd party module)
Your message dated Sat, 13 Mar 2021 22:47:39 +0900 with message-id <20210313224739.0f2ccff371b408d287759...@xdump.org> and subject line nginx: please provide nginx-dev package for packaging 3rd party module has caused the Debian Bug report #985134, regarding nginx: please provide nginx-dev package for packaging 3rd party module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nginx Version: 1.18.0-6 Severity: wishlist X-Debbugs-Cc: ken...@xdump.org The problem: It is hard to package nginx 3rd party modules because nginx package does not ship configure scripts. Actual: No configure and auto/* conf/* src/* for building nginx 3rd party modules. Expected: * package nginx-dev. * nginx-dev package provides: /usr/share/nginx/configure /usr/share/nginx/auto/* /usr/share/nginx/conf/* /usr/share/nginx/src/* Then, 3rd party module can use these files in debian/rules. ./configure --add-dynamic-module=$(CURDIR) ... -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: sh4, powerpc, m68k Kernel: Linux 5.10.0-4-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nginx depends on: ii nginx-core 1.18.0-6+b1 ii nginx-full 1.18.0-6 nginx recommends no packages. nginx suggests no packages. --- End Message --- --- Begin Message --- duplicated.--- End Message ---
Bug#858270: marked as done (xpdf: debian's xpdf fails to render text in graphics while upstream version works)
Your message dated Sat, 13 Mar 2021 15:01:32 +0100 with message-id <20210313140132.gr356...@zedat.fu-berlin.de> and subject line Re: Bug#858270: closed by Florian Schlichting (Bug#850163: fixed in xpdf 3.04-6) has caused the Debian Bug report #858270, regarding xpdf: debian's xpdf fails to render text in graphics while upstream version works to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.04-4 Severity: normal Hi, The pdf file [1] does not render properly with the debian version of xpdf. This is not the only file I have experienced this. I stumble over such an issue every couple of months. Debians's xpdf prints lots of errors like this: Syntax Error (28001): No font in show Syntax Error: Unknown font tag 'R35' Syntax Error (28391): No font in show/space Syntax Error: Unknown font tag 'R31' Syntax Error (29447): No font in show/space Syntax Error (29542): No font in show/space Syntax Error: Unknown font tag 'R35' At the same time, xpdf compiled from the upstream sources works fine. Attila Kinali [1] http://time.kinali.ch/a_flexible_5ps_bin_width_timing_core_for_next_generation_high_energy_physics_time_to_digital_converter_applications-2012-perktold_christiansen-06226156.pdf -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xpdf depends on: ii libc6 2.24-9 ii libgcc1 1:6.3.0-6 ii libpoppler64 0.48.0-2 ii libstdc++66.3.0-6 ii libx11-6 2:1.6.4-3 ii libxm42.3.4-13 ii libxt61:1.1.5-1 Versions of packages xpdf recommends: ii cups-bsd 2.2.1-8 ii gsfonts-x110.24 ii poppler-data 0.4.7-8 ii poppler-utils 0.48.0-2 xpdf suggests no packages. -- Configuration Files: /etc/xpdf/xpdfrc changed: psFile "|xpp" urlCommand "sensible-browser '%s'" unbind down any unbind right any unbind up any unbind left any bind down window scrollDown(16) bind right window scrollRight(16) bind up window scrollUp(16) bind left window scrollLeft(16) bind down fullScreen nextPage bind right fullScreen nextPage bind up fullScreen prevPage bind left fullScreen prevPage include /etc/xpdf/includes -- no debconf information --- End Message --- --- Begin Message --- Control: fixed 858270 3.04+git20210103-3 >> This bug is still present, the same as reported. Whatever libpopler does >> with the fonts, it does it wrong. > > can you please make available a PDF file exhibiting the bug you talk > about? The link that you provided in your initial bug report results in > a "403 Forbidden". Today the link worked, and I could confirm that there are no error messages and no obvious font rendering issues with xpdf version 3.04+git20210103-3, so I'm again closing this bug. Florian--- End Message ---
Bug#762000: marked as done (xpdf: Missing glyphs, "Syntax Error: Missing language pack for 'Adobe-GB1' mapping")
Your message dated Sat, 13 Mar 2021 15:01:32 +0100 with message-id <20210313140132.gr356...@zedat.fu-berlin.de> and subject line Re: Bug#858270: closed by Florian Schlichting (Bug#850163: fixed in xpdf 3.04-6) has caused the Debian Bug report #858270, regarding xpdf: Missing glyphs, "Syntax Error: Missing language pack for 'Adobe-GB1' mapping" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.03-17+b1 Severity: normal Hi, In some PDF documents, typically datasheets, I've noticed that sequences like °C and °F don't display as anything. The same datasheet displays fine in evince. An example is attached (bad.pdf). The first line says "Absolute Maximum Ratings at Ta=25°C" in evince, but the °C is missing in xpdf. Xpdf outputs a bunch of errors beginning with "Syntax Error: Missing language pack for 'Adobe-GB1' mapping" when displaying the page. I think the °C is a different font. pdffonts shows: $ pdffonts bad.pdf name type encoding emb sub uni object ID - --- --- --- - SimSun CID TrueType Identity-H no no no 5 0 Verdana TrueType WinAnsi no no no 8 0 Verdana-BoldItalic TrueType WinAnsi no no no 10 0 Jim Debian Release: jessie/sid APT prefers testing APT policy: (250, 'testing'), (200, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xpdf depends on: ii libc6 2.19-10 ii libgcc1 1:4.9.1-12 ii libpoppler46 0.26.4-1 ii libstdc++64.9.1-12 ii libx11-6 2:1.6.2-3 ii libxm42.3.4-5 ii libxt61:1.1.4-1 Versions of packages xpdf recommends: ii cups-bsd 1.7.5-1 ii gsfonts-x110.22 ii poppler-data 0.4.7-1 ii poppler-utils 0.26.4-1 xpdf suggests no packages. -- no debconf information bad.pdf Description: Adobe PDF document --- End Message --- --- Begin Message --- Control: fixed 858270 3.04+git20210103-3 >> This bug is still present, the same as reported. Whatever libpopler does >> with the fonts, it does it wrong. > > can you please make available a PDF file exhibiting the bug you talk > about? The link that you provided in your initial bug report results in > a "403 Forbidden". Today the link worked, and I could confirm that there are no error messages and no obvious font rendering issues with xpdf version 3.04+git20210103-3, so I'm again closing this bug. Florian--- End Message ---
Bug#850163: marked as done (xpdf fails to render Japanese text with various pdf files)
Your message dated Sat, 13 Mar 2021 15:01:32 +0100 with message-id <20210313140132.gr356...@zedat.fu-berlin.de> and subject line Re: Bug#858270: closed by Florian Schlichting (Bug#850163: fixed in xpdf 3.04-6) has caused the Debian Bug report #858270, regarding xpdf fails to render Japanese text with various pdf files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.04-3 xpdf often fails to render pdf documents using Japanese fonts. This issue exists on Jessie, Stretch and the latest Sid. xpdf-i on Wheezy worked well as expected. Here's the procedure how to reproduce: > wget http://gum.debian.or.jp/2012/download/debian-gum-presentation.nojima.pdf .. > xpdf debian-gum-presentation.nojima.pdf Syntax Error: Missing language pack for 'Adobe-Japan1' mapping Syntax Error: Missing language pack for 'Adobe-Japan1' mapping Syntax Error: Unknown font tag 'F3' Syntax Error (4879): No font in show/space Syntax Error: Unknown font tag 'F3' Syntax Error (4917): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (4972): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5005): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5058): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5074): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5088): No font in show/space Syntax Error: Missing language pack for 'Adobe-Japan1' mapping Syntax Error: Missing language pack for 'Adobe-Japan1' mapping Syntax Error: Unknown font tag 'F3' Syntax Error (4879): No font in show/space Syntax Error: Unknown font tag 'F3' Syntax Error (4917): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (4972): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5005): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5058): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5074): No font in show/space Syntax Error: Unknown font tag 'F5' Syntax Error (5088): No font in show/space --- End Message --- --- Begin Message --- Control: fixed 858270 3.04+git20210103-3 >> This bug is still present, the same as reported. Whatever libpopler does >> with the fonts, it does it wrong. > > can you please make available a PDF file exhibiting the bug you talk > about? The link that you provided in your initial bug report results in > a "403 Forbidden". Today the link worked, and I could confirm that there are no error messages and no obvious font rendering issues with xpdf version 3.04+git20210103-3, so I'm again closing this bug. Florian--- End Message ---
Bug#985062: marked as done (unblock: lxc-templates/3.0.4-5)
Your message dated Sat, 13 Mar 2021 13:37:16 +
with message-id
and subject line unblock lxc-templates
has caused the Debian Bug report #985062,
regarding unblock: lxc-templates/3.0.4-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
985062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Please unblock package lxc-templates from unstable to testing.
lxc-templates 3.0.4-5, which has just been accepted in unstable, fixes 3 bugs
that will be beneficial for the stability of the package in bullseye. I should
clearly state that none of these bugs are release critical.
The first bug is to add a Suggest to qemu-user-static.
The second is to add a missing Recommend that made lxc-debian template not
working since a patch I made in October.
The third and last is to fix some errors in some templates that could lead to
catastrophic rm in case of sigint spawned while installing a container for some
distributions (arch, centos, ...). It contains the patch 0004, which is the
reason this debdiff has some lines
Please don't hesitate if you need more intel.
Here is the debdiff:
diff -Nru lxc-templates-3.0.4/debian/changelog
lxc-templates-3.0.4/debian/changelog
--- lxc-templates-3.0.4/debian/changelog2020-10-17 22:42:34.0
+0200
+++ lxc-templates-3.0.4/debian/changelog2021-03-12 11:53:24.0
+0100
@@ -1,3 +1,18 @@
+lxc-templates (3.0.4-5) unstable; urgency=medium
+
+ [ Gianfranco Costamagna ]
+ * d/control:
+- Add Suggests: qemu-user-static (Closes: #973345)
+
+ [ Pierre-Elliott Bécue ]
+ * d/control:
+- Add distro-info to the Recommends of lxc-templates (Closes: #974569)
+- Bump Standards-Version to 4.5.1
+ * d/p/0004: fix path variable in some templates to avoid catastrophic rm
+(Closes: #839843)
+
+ -- Pierre-Elliott Bécue Fri, 12 Mar 2021 11:53:24 +0100
+
lxc-templates (3.0.4-4) unstable; urgency=medium
* d/patches/0002: Update lxc.debian template to document alternatives to the
diff -Nru lxc-templates-3.0.4/debian/control lxc-templates-3.0.4/debian/control
--- lxc-templates-3.0.4/debian/control 2020-10-17 22:42:34.0 +0200
+++ lxc-templates-3.0.4/debian/control 2021-03-12 11:53:22.0 +0100
@@ -4,7 +4,7 @@
Maintainer: pkg-lxc
Uploaders: Pierre-Elliott Bécue
Build-Depends: debhelper-compat (= 13)
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
Homepage: https://linuxcontainers.org/
Vcs-Git: https://salsa.debian.org/lxc-team/lxc-templates.git
Vcs-Browser: https://salsa.debian.org/lxc-team/lxc-templates
@@ -17,11 +17,13 @@
busybox-static,
cloud-image-utils | cloud-utils,
debootstrap | cdebootstrap,
+distro-info,
mmdebstrap,
openssl,
rsync,
uuid-runtime,
xz-utils
+Suggests: qemu-user-static
Description: Linux Containers userspace tools (templates)
Containers are insulated areas inside a system, which have their own namespace
for filesystem, network, PID, IPC, CPU and memory allocation and which can be
diff -Nru
lxc-templates-3.0.4/debian/patches/0004-Fixes-path-variable-in-some-templates.patch
lxc-templates-3.0.4/debian/patches/0004-Fixes-path-variable-in-some-templates.patch
---
lxc-templates-3.0.4/debian/patches/0004-Fixes-path-variable-in-some-templates.patch
1970-01-01 01:00:00.0 +0100
+++
lxc-templates-3.0.4/debian/patches/0004-Fixes-path-variable-in-some-templates.patch
2021-03-12 11:50:28.0 +0100
@@ -0,0 +1,180 @@
+From: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
+Date: Fri, 12 Mar 2021 11:50:00 +0100
+Subject: Fixes path variable in some templates
+
+The behaviour of the path variable is somewhat inconsistent with a
+relevant way of generating containers. path now points to a directory,
+where ${path}/${name} will be created and handle the new container's
+config/rootfs
+---
+ templates/lxc-archlinux.in | 8 +---
+ templates/lxc-centos.in| 6 --
+ templates/lxc-fedora-legacy.in | 8 +---
+ templates/lxc-fedora.in| 8 +---
+ templates/lxc-pld.in | 7 +--
+ templates/lxc-voidlinux.in | 8 +++-
+ 6 files changed, 31 insertions(+), 14 deletions(-)
+
+diff --git a/templates/lxc-archlinux.in b/templates/lxc-archlinux.in
+index f8d4ba0..afa2f11 100644
+--- a/templates/lxc-archlinux.in
b/templates/lxc-archlinux.in
+@@ -206,8
Bug#984468: marked as done (Unblock selected KDE Apps 20.12.3)
Your message dated Sat, 13 Mar 2021 14:28:22 +0100
with message-id <20210313132820.ga26...@debian.org>
and subject line Re: Bug#984468: Pre-approval for uploading KDE Apps 20.12.3
has caused the Debian Bug report #984468,
regarding Unblock selected KDE Apps 20.12.3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
984468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: Debian Qt/KDE Maintainers
Dear Release Team,
KDE Apps 20.12.3 will be released tomorrow and a preliminary
changelog is available at [1].
I’d like to get a pre-aproval for uploading the packages listed below as
they will not have migrated to testing before the hard freeze.
I’m listing the change log first then the code diffs, excluding
translation updates and version changes in xml metadata files.
Juk has a couple of trivial packaging changes pending and other packages
would be uploaded as is with just the new upstream version.
Feel free to ask for the changes in any other form if it makes the review
easier for you.
[1] https://phabricator.kde.org/P672
Thanks,
--
Aurélien
== change log ==
elisa-player
- fix sort by duration to not use string sort
gwenview
- Switch from QGLWidget to QOpenGLWidget
- Use Quality level when saving JPEG images
juk
- filerenamer: Prevent creating track name folders
kdeconnect-kde
- Don't escape notification title text
konsole
- Delete client builder before d-pointer of KXMLGUIClient is killed
=== kpmcore ===
- Fix out of bounds read when parsing fstab.
- Add initial support for dosfstools 4.2.
krdc
- Fix low quality connections
- VNC: accept the wheel event
- Unpress modifiers on focusOutEvent in VncView
marble
- Fix GeoNames web service URL, is now api.geonames.org (#432598)
- Provide BUILD_TOUCH option to force install of touch variant
okular
- presentation: Show better the status of the "playing" button
- pdf: Fix InPlace text annotations being loaded as linked
palapeli
- Make the cache work
kde-spectacle
- Fix compression quality range
===
== diffs ==
===
elisa-player
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 10078c21..17f34229 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -7,7 +7,7 @@ cmake_minimum_required(VERSION 3.8)
# KDE Applications version, managed by release script.
set(RELEASE_SERVICE_VERSION_MAJOR "20")
set(RELEASE_SERVICE_VERSION_MINOR "12")
-set(RELEASE_SERVICE_VERSION_MICRO "2")
+set(RELEASE_SERVICE_VERSION_MICRO "3")
set(RELEASE_SERVICE_VERSION
"${RELEASE_SERVICE_VERSION_MAJOR}.${RELEASE_SERVICE_VERSION_MINOR}.${RELEASE_SERVICE_VERSION_MICRO}")
project(elisa
diff --git a/src/models/datamodel.cpp b/src/models/datamodel.cpp
index 69d71397..7559c0e5 100644
--- a/src/models/datamodel.cpp
+++ b/src/models/datamodel.cpp
@@ -87,7 +87,7 @@ QHash DataModel::roleNames() const
roles[static_cast(DataTypes::ColumnsRoles::AlbumRole)] = "album";
roles[static_cast(DataTypes::ColumnsRoles::AlbumArtistRole)] =
"albumArtist";
-roles[static_cast(DataTypes::ColumnsRoles::DurationRole)] =
"duration";
+roles[static_cast(DataTypes::ColumnsRoles::StringDurationRole)] =
"duration";
roles[static_cast(DataTypes::ColumnsRoles::TrackNumberRole)] =
"trackNumber";
roles[static_cast(DataTypes::ColumnsRoles::DiscNumberRole)] =
"discNumber";
roles[static_cast(DataTypes::ColumnsRoles::RatingRole)] = "rating";
@@ -156,7 +156,7 @@ QVariant DataModel::data(const QModelIndex , int
role) const
break;
}
break;
-case DataTypes::ColumnsRoles::DurationRole:
+case DataTypes::ColumnsRoles::StringDurationRole:
{
switch (d->mModelType)
{
gwenview
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 25adb69b..c34f4108 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -3,7 +3,7 @@ cmake_minimum_required (VERSION 3.0 FATAL_ERROR)
# KDE Application Version, managed by release script
set (RELEASE_SERVICE_VERSION_MAJOR "20")
set (RELEASE_SERVICE_VERSION_MINOR "12")
-set (RELEASE_SERVICE_VERSION_MICRO "1")
+set (RELEASE_SERVICE_VERSION_MICRO "3")
set (RELEASE_SERVICE_VERSION
"${RELEASE_SERVICE_VERSION_MAJOR}.${RELEASE_SERVICE_VERSION_MINOR}.${RELEASE_SERVICE_VERSION_MICRO}")
project(gwenview VERSION ${RELEASE_SERVICE_VERSION})
@@ -51,7 +51,7 @@ else()
set(GWENVIEW_SEMANTICINFO_BACKEND_BALOO
Bug#984645: marked as done (unblock: refpolicy/2:2.20210203-4)
Your message dated Sat, 13 Mar 2021 13:18:17 + with message-id and subject line unblock refpolicy has caused the Debian Bug report #984645, regarding unblock: refpolicy/2:2.20210203-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package refpolicy [ Reason ] This new version has lots of changes that will make the experience more pleasant for users. It specifically allows some of the recent features in systemd, chromium/chrome, and KDE. It allows gpg with pinentry to be run from user_t (the confined user). It allows some extra access that mailman3 requires. It also allows newaliases to run with Postfix. [ Impact ] If this isn't in Bullseye then the SE Linux experience for users will be a little more annoying. Things won't work out of the box as expected without it and local customisations to resolve the issues won't be of as high quality as the ones I developed. Also without this version there will be audit messages that will be confusing and annoying. [ Tests ] For the programs subject to the policy in question, they were run repeatedly with the new policy, VMs running them were rebooted, and the results were inspected to see if they operated correctly and didn't give unwanted audit messages. [ Risks ] Most changes are granting new access, not access that is unexpected given the context, and not access that is likely to be part of a vulnerability chain. These have low possibility of causing any problem. The change for the newaliases command is more complex, but being unable to run newaliases is a serious issue so it's worth doing. The worst case might be some domain being unable to send mail from a script. But in all the test cases it worked. [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing unblock refpolicy/2:2.20210203-4 diff -Nru refpolicy-2.20210203/debian/changelog refpolicy-2.20210203/debian/changelog --- refpolicy-2.20210203/debian/changelog 2021-02-23 16:57:40.0 +1100 +++ refpolicy-2.20210203/debian/changelog 2021-03-05 21:11:58.0 +1100 @@ -1,3 +1,35 @@ +refpolicy (2:2.20210203-4) unstable; urgency=medium + + * Allow ntpd_t to get the status of generic systemd units + * Allow kernel_t self:perf_event cpu. + * Allow chromium to watch network manager runtime dirs (for resolv.conf) +Allow chromium to run naclhelper with nnp_transition +Allow chromium to watch root dirs +Allow chromium to read/write unix sockets from the calling domain + * Make Postgresql use postgresql_tmpfs_t for tmpfs files and make +mon_local_test_t and systemd_logind_t not have getattr access to tmpfs +files audited. + * Allow systemd_user_runtime_dir_t to unlink device nodes of type +user_tmp_t, they probably should not exist, so it's in the hacks patch. + * Allow the acngtool to read random and urandom devices and search fs sysctls + * Add wm_write_xdg_data tunable to allow user_wm_t etc to write xdg data. + * Allow chromium to watch gnome_xdg_config_t dirs + * Label pinentry programs as gpg_agent_exec_t and allow gpg_agent_t to exec +them + * Create new admin_mail_t domain so that newaliases can work with Postfix + * Added a transition rule so that vipw/vigr gives the right context for +/etc/passwd and /etc/group + * Allow acngtool_t to read /proc/sys/kernel/random/uuid + * Allow unconfined domains lockdown confidentiality and integrity access + * Allow netutils_t netlink_generic_socket access for tcpdump + * Allow smbcontrol to create a sock_file in a samba run dir + * Allow mailman_queue_t to bind to all unreserved TCP ports + * Allow systemd_coredump_t to mmap all executables and to have cap_userns +sys_ptrace access. dontaudit systemd_coredump_t capability net_admin + * Allow mailman_queue_t to connect to port 443 + + -- Russell Coker Fri, 05 Mar 2021 21:11:58 +1100 + refpolicy (2:2.20210203-3) unstable; urgency=medium * Add policy for blkmapd which is part of nfs service (included in upstream) diff -Nru refpolicy-2.20210203/debian/patches/0002-strict refpolicy-2.20210203/debian/patches/0002-strict --- refpolicy-2.20210203/debian/patches/0002-strict 2021-02-17 13:40:42.0 +1100 +++
Bug#984642: marked as done (unblock: policycoreutils/3.1-3)
Your message dated Sat, 13 Mar 2021 13:16:41 +
with message-id
and subject line unblock policycoreutils
has caused the Debian Bug report #984642,
regarding unblock: policycoreutils/3.1-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
984642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package policycoreutils
(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)
[ Reason ]
This version fixes bug #983447 which is grave and risks kicking the package
out of Bullseye. It also closes bug #922448 and avoids trying to relabel
non-persistent filesystems on reboot.
[ Impact ]
All SE Linux packages get removed from Debian I guess, catastrophic for all
SE Linux users in Debian.
[ Tests ]
Manual test is to create an empty file /.autorelabel and reboot the system
and verify that it causes a relabel, then create a file /.autorelabel with
the contents "-F" and verify that it works.
[ Risks ]
The changed code is pretty simple, and in day to day usage it isn't even
used. It's only used for corner cases of an initial installation.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
[ Other info ]
(Anything else the release team should know.)
unblock policycoreutils/3.1-3
Here is the debdiff:
diff -Nru policycoreutils-3.1/debian/changelog
policycoreutils-3.1/debian/changelog
--- policycoreutils-3.1/debian/changelog2021-02-11 02:46:48.0
+1100
+++ policycoreutils-3.1/debian/changelog2021-03-05 20:45:24.0
+1100
@@ -1,3 +1,16 @@
+policycoreutils (3.1-3) unstable; urgency=medium
+
+ * Remove needless quotes around $FORCE variable in
+/lib/systemd/selinux-autorelabel to avoid shell error on empty file
+Closes: #983447
+ * Add check for noautorelabel command line option to prevent relabeling
+Closes: #922448
+ * Make fixfiles avoid trying to relabel tmpfs and other non-permanent
+filesystems
+Closes: #984567
+
+ -- Russell Coker Fri, 05 Mar 2021 20:45:24 +1100
+
policycoreutils (3.1-2) unstable; urgency=medium
[ Laurent Bigonville ]
diff -Nru policycoreutils-3.1/debian/local/selinux-autorelabel
policycoreutils-3.1/debian/local/selinux-autorelabel
--- policycoreutils-3.1/debian/local/selinux-autorelabel2021-02-11
02:46:48.0 +1100
+++ policycoreutils-3.1/debian/local/selinux-autorelabel2021-03-05
20:32:47.0 +1100
@@ -29,7 +29,7 @@
FORCE=$(cat /.autorelabel)
[ -x "/sbin/quotaoff" ] && /sbin/quotaoff -aug
- /sbin/fixfiles "$FORCE" restore
+ /sbin/fixfiles $FORCE restore
fi
rm -f /.autorelabel
[ -x /usr/lib/dracut/dracut-initramfs-restore ] &&
/usr/lib/dracut/dracut-initramfs-restore
diff -Nru policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh
policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh
--- policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh
2021-02-11 02:46:48.0 +1100
+++ policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh
2021-03-05 20:05:29.0 +1100
@@ -21,6 +21,9 @@
}
if selinuxenabled; then
+if grep -sqE "\bnoautorelabel\b" /proc/cmdline; then
+exit 0
+fi
if test -f /.autorelabel; then
set_target
elif grep -sqE "\bautorelabel\b" /proc/cmdline; then
diff -Nru policycoreutils-3.1/debian/patches/fixfiles-remove-extras
policycoreutils-3.1/debian/patches/fixfiles-remove-extras
--- policycoreutils-3.1/debian/patches/fixfiles-remove-extras 1970-01-01
10:00:00.0 +1000
+++ policycoreutils-3.1/debian/patches/fixfiles-remove-extras 2021-03-05
20:37:08.0 +1100
@@ -0,0 +1,13 @@
+Index: policycoreutils-3.1/scripts/fixfiles
+===
+--- policycoreutils-3.1.orig/scripts/fixfiles
policycoreutils-3.1/scripts/fixfiles
+@@ -45,7 +45,7 @@ FS="`cat /proc/self/mounts | sort | uniq
+ for i in $FS; do
+ if [ `useseclabel` -ge 0 ]
+ then
+- grep " $i " /proc/self/mounts | awk '{print $4}' | egrep
--silent '(^|,)seclabel(,|$)' && echo $i
++ grep " $i " /proc/self/mounts | egrep -v "(tmpfs)|(
/sys)|(^devpts)|(^hugetlbfs)|(^mqueue)" |
Bug#985132: marked as done (unblock: tipa/tipa_1.3-21)
Your message dated Sat, 13 Mar 2021 14:10:15 +0100
with message-id <20210313131014.ga26...@debian.org>
and subject line Re: unblock: tipa/tipa_1.3-21
has caused the Debian Bug report #985132,
regarding unblock: tipa/tipa_1.3-21
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
985132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package tipa
[ Reason ]
In the last upload I fixed the most issues regarding the Debian
packaging itself.
[ Impact ]
Not releasing the package results in a heavily outdated Debian package from
the view of the packaging. This makes it harder to adapt the package to new
systems.
[ Tests ]
Only the Debian packaging was changed. Mostly I addressed the issues
reported by lintian. The following tests result in a more clean package.
[ Risks ]
There was no code change in the upstream code, hence no risk for the
end user. The only visible change is: the tipa doc files (from
tipa-doc) now sit in /usr/share/doc/tipa according to new standard.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
unblock tipa/tipa_1.3-21
diff -Nru tipa-1.3/debian/changelog tipa-1.3/debian/changelog
--- tipa-1.3/debian/changelog 2014-10-10 01:49:13.0 +0200
+++ tipa-1.3/debian/changelog 2021-03-12 00:19:38.0 +0100
@@ -1,3 +1,18 @@
+tipa (2:1.3-21) unstable; urgency=medium
+
+ * Add me to Uploaders, fix Vcs URLs to salsa.
+ * Replace http -> https in docs, where possible.
+ * tipa-doc now ships pdf files in /usr/share/doc/tipa .
+ * tipa suggests tipa-doc
+ * Mark tipa-doc & xfonts-tipa as "Multi-Arch: foreign"
+ * Lintian:
+- priority-extra-is-replaced-by-priority-optional
+- debhelper compat 13
+- Standards version bumped to 4.5.1
+- older-debian-watch-file-standard 3
+
+ -- Hilmar Preusse Fri, 12 Mar 2021 00:19:38 +0100
+
tipa (2:1.3-20) unstable; urgency=medium
* fix location of documentation links to /usr/share/texmf/doc
diff -Nru tipa-1.3/debian/compat tipa-1.3/debian/compat
--- tipa-1.3/debian/compat 2014-10-10 01:28:46.0 +0200
+++ tipa-1.3/debian/compat 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-8
diff -Nru tipa-1.3/debian/control tipa-1.3/debian/control
--- tipa-1.3/debian/control 2014-10-10 01:47:30.0 +0200
+++ tipa-1.3/debian/control 2021-03-12 00:15:05.0 +0100
@@ -2,20 +2,24 @@
Section: tex
Priority: optional
Maintainer: Debian TeX maintainers
-Uploaders: Daniele Tricoli , Norbert Preining
-Standards-Version: 3.9.6
-Build-Depends: debhelper (>= 8.1.0~)
+Uploaders: Daniele Tricoli ,
+ Norbert Preining ,
+ Hilmar Preusse
+Standards-Version: 4.5.1
+Build-Depends: debhelper-compat (= 13)
Build-Depends-Indep: tex-common (>= 3), texlive-latex-recommended,
texlive-fonts-recommended, ghostscript, sharutils
-Vcs-Svn: svn://svn.debian.org/svn/debian-tex/tipa/trunk
-Vcs-Browser: http://svn.debian.org/wsvn/debian-tex/tipa/trunk/
-Homepage: http://www.ctan.org/tex-archive/fonts/tipa/
+Rules-Requires-Root: no
+Vcs-Git: https://salsa.debian.org/tex-team/tipa.git
+Vcs-Browser: https://salsa.debian.org/tex-team/tipa
+Homepage: https://www.ctan.org/tex-archive/fonts/tipa/
Package: tipa
Architecture: all
Depends: texlive-latex-base, texlive-base-bin, ${misc:Depends}
Conflicts: tipa-type1
Replaces: tipa-type1
+Suggests: tipa-doc
Description: system for processing phonetic symbols in LaTeX
TIPA is a system for processing IPA (International Phonetic
Alphabet) symbols in LaTeX written by Fukui Rei. TIPA stands for
@@ -43,8 +47,8 @@
xfonts-tipa package).
Package: xfonts-tipa
-Priority: extra
Architecture: all
+Multi-Arch: foreign
Section: fonts
Pre-Depends: ${misc:Pre-Depends}
Depends: tipa (= ${source:Version}), ${misc:Depends}
@@ -60,9 +64,9 @@
http://www.sil.org/computing/fonts/encore-ipa.html).
Package: tipa-doc
-Priority: extra
Depends: ${misc:Depends}
Architecture: all
+Multi-Arch: foreign
Section: doc
Description: documentation for the TIPA LaTeX font
TIPA is a system for processing IPA (International Phonetic
diff -Nru tipa-1.3/debian/copyright tipa-1.3/debian/copyright
--- tipa-1.3/debian/copyright 2014-10-10 01:48:30.0 +0200
+++ tipa-1.3/debian/copyright 2021-03-11 00:26:57.0 +0100
@@ -1,17 +1,10 @@
-Format:
Bug#985128: marked as done (unblock: texlive-bin/2020.20200327.54578-7)
Your message dated Sat, 13 Mar 2021 12:58:46 +
with message-id
and subject line unblock texlive-bin
has caused the Debian Bug report #985128,
regarding unblock: texlive-bin/2020.20200327.54578-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
985128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-tex-ma...@lists.debian.org
Please unblock package texlive-bin
[ Reason ]
Several fixes for shell escape exploits recently reported on the
private TeX Live security list have been fixed.
(No CVE or bug numbers are available)
[ Impact ]
TeX programs (like (la)tex, pdf(la)tex, lua(la)tex etc have a
"restricted" mode for calling external programs, where only a
specific set of vetted for programs are allowed.
Without these fixes it will be rather easy to call arbitrary programs
from tex/luatex/etc even when those programs run in restricted mode
(which is the default setup).
Another fix that is in this patch is for xdvi which didn't quote '&'
before passing it to the shell to start a program, which again allowed
for arbitrary program execution.
[ Tests ]
All exploits have been tested before and after the fix. On request I
will send the exploit code.
[ Risks ]
One fix that has been done is that in restricted mode, luatex does not
allow putenv (change of environment variables) anymore, because this
would allow PATH changes, and thus circumvention of restricted mode
setting.
Some packages might use putenv (lua) on purpose and good way, which
might be broken when run in restricted mode, although we (that is
upstream TeX Live as well as the Debian team) are not aware of any.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
I made them and backported them
[X] attach debdiff against the package in testing
I attach the three patches added to the patch
queue in debian/patches. All other changes are
just changelog entry and one patch renaming
for consistency. All the code changes are attached.
unblock texlive-bin/2020.20200327.54578-7
Norbert
--
PREINING Norbert https://www.preining.info
Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
---
texk/web2c/lib/texmfmp.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
--- a/texk/web2c/lib/texmfmp.c
+++ b/texk/web2c/lib/texmfmp.c
@@ -606,8 +606,18 @@ runsystem (const char *cmd)
if (allow == 1)
status = system (cmd);
- else if (allow == 2)
+ else if (allow == 2) {
+/*
+ command including a character '|' is not allowed in
+ restricted mode for security.
+*/
+size_t k;
+for (k = 0; k < strlen (safecmd); k++) {
+ if (safecmd[k] == '|')
+return 0;
+}
status = system (safecmd);
+ }
/* Not really meaningful, but we have to manage the return value of system.
*/
if (status != 0)
---
texk/web2c/luatexdir/lua/luatex-core.c | 626
+-
texk/web2c/luatexdir/lua/luatex-core.lua|3
texk/web2c/luatexdir/luafontloader/fontforge/fontforge/splinefont.c | 10
3 files changed, 326 insertions(+), 313 deletions(-)
--- a/texk/web2c/luatexdir/lua/luatex-core.lua
+++ b/texk/web2c/luatexdir/lua/luatex-core.lua
@@ -198,6 +198,9 @@ if saferoption == 1 or shellescape ~= 1
package.searchers[4] = nil
package.searchers[3] = nil
+if os.setenv then
+os.setenv = function(...) end
+end
ffi = require('ffi')
if ffi then
--- a/texk/web2c/luatexdir/luafontloader/fontforge/fontforge/splinefont.c
+++ b/texk/web2c/luatexdir/luafontloader/fontforge/fontforge/splinefont.c
@@ -246,6 +246,12 @@ char *Decompress(char *name, int compres
char buf[1500];
char *tmpfile;
+if ( strchr(name,'$') || strchr(name,'!') || strchr(name,'*') ||
strchr(name,'?')
+|| strchr(name,'[') || strchr(name,'[') || strchr(name,']') ||
strchr(name,']')
+|| strchr(name,';') || strchr(name,'&') || strchr(name,'>') ||
strchr(name,'<')
+|| strchr(name,'`') || strchr(name,'"') || strchr(name,'|') ||
strchr(name,'\'')
+|| strchr(name,'\\'))
+return( NULL );
if ( dir==NULL ) dir = P_tmpdir;
tmpfile = galloc(strlen(dir)+strlen(GFileNameTail(name))+2);
Bug#985125: marked as done (ibus-anthy is not available on GNOME: 1.5.11-2 -> 1.5.12-1 upgrade)
Your message dated Sat, 13 Mar 2021 21:11:51 +0900
with message-id
and subject line Re: Bug#985125: ibus-anthy is not available on GNOME: 1.5.11-2
-> 1.5.12-1 upgrade
has caused the Debian Bug report #985125,
regarding ibus-anthy is not available on GNOME: 1.5.11-2 -> 1.5.12-1 upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
985125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibus-anthy
Version: 1.5.12-1
Severity: important
X-Debbugs-Cc: YOSHINO Yoshihito
>From yeasterday's upgrade 1.5.11-2 -> 1.5.12-1, anthy is not usable on
GNOME/ibus.
This happened just when I was going to check https://bugs.debian.org/983695
I don't see anthy in GNOME Setting dialogue.
I think some data file is missing.
$ debdiff ibus-anthy_1.5.11-2_amd64.deb ibus-anthy_1.5.12-1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/lib/x86_64-linux-gnu/libanthygobject-1.0.so.5.0.512
-rw-r--r-- root/root /usr/share/locale/de/LC_MESSAGES/ibus-anthy.mo
-rw-r--r-- root/root /usr/share/locale/hu/LC_MESSAGES/ibus-anthy.mo
-rw-r--r-- root/root /usr/share/locale/pt_PT/LC_MESSAGES/ibus-anthy.mo
-rw-r--r-- root/root /usr/share/locale/tr/LC_MESSAGES/ibus-anthy.mo
lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/libanthygobject-1.0.so.5 ->
libanthygobject-1.0.so.5.0.512
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/lib/x86_64-linux-gnu/libanthygobject-1.0.so.5.0.511
lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/libanthygobject-1.0.so.5 ->
libanthygobject-1.0.so.5.0.511
Control files: lines which differ (wdiff format)
Installed-Size: [-8723-] {+8783+}
Version: [-1.5.11-2-] {+1.5.12-1+}
So far, it looks OK. Intriguing
But something caused this missing dialog and missing IM (I can still use
ibus-mozc for Japanese).
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ibus-anthy depends on:
ii anthy1:0.4-2
ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2
ii ibus 1.5.23-2
ii libanthy11:0.4-2
ii libc62.31-9
ii libglib2.0-0 2.66.7-1
ii python3 3.9.2-2
ibus-anthy recommends no packages.
ibus-anthy suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hmm... Now I see anthy in SEtting menu. (Maybe because I rebooted, or
I was seeing something odd) I have anthy back.
Odd. But let me close it.
On Sat, 2021-03-13 at 18:28 +0900, YOSHINO Yoshihito wrote:
> Package: ibus-anthy
> Followup-For: Bug #985125
>
> Not reproducible on my side ...
>
> $ sudo apt-get dist-upgrade
> $ sudo apt-get install ibus-mozc
> $ sudo dpkg -i /var/cache/apt/archives/ibus-anthy_1.5.11-2_amd64.deb
> $ sudo reboot
> Then I manually added "日本語 (Anthy)" to an input source in GNOME
> Settings, and anthy is available on the GNOME top bar.
> $ sudo apt-get dist-upgrade
> which upgrades ibus-anthy to 1.5.12-1
> $ sudo reboot
> Then anthy is still available. Attached a screenshot of GNOME
> Settings.
> Note that the current dconf value is
> $ dconf read /org/gnome/desktop/input-sources/sources
> [('ibus', 'mozc-jp'), ('xkb', 'jp'), ('ibus', 'anthy')]
> $
>
> Regards,
> --
> YOSHINO Yoshihito
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing-security
> APT policy: (500, 'testing-security'), (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-4-amd64 (SMP w/1 CPU thread)
> Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
> LANGUAGE not set
>
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages ibus-anthy depends on:
> ii anthy 1:0.4-2
> ii
Bug#985090: marked as done (CVE-2020-35711)
Your message dated Sat, 13 Mar 2021 11:48:25 + with message-id and subject line Bug#985090: fixed in rust-arc-swap 0.4.8-1 has caused the Debian Bug report #985090, regarding CVE-2020-35711 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-arc-swap Severity: important Tags: security X-Debbugs-Cc: Debian Security Team CVE-2020-35711 https://github.com/vorner/arc-swap/issues/45 https://rustsec.org/advisories/RUSTSEC-2020-0091.html --- End Message --- --- Begin Message --- Source: rust-arc-swap Source-Version: 0.4.8-1 Done: Wolfgang Silbermayr We believe that the bug you reported is fixed in the latest version of rust-arc-swap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wolfgang Silbermayr (supplier of updated rust-arc-swap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 12:24:41 +0100 Source: rust-arc-swap Architecture: source Version: 0.4.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Wolfgang Silbermayr Closes: 985090 Changes: rust-arc-swap (0.4.8-1) unstable; urgency=medium . * Package arc-swap 0.4.8 from crates.io using debcargo 2.4.3 Closes: #985090 Checksums-Sha1: d03a613ebec0d605bf4bfc44d742eb5d65db6d05 2370 rust-arc-swap_0.4.8-1.dsc 66c18486fc295337aca6fb91410882b8dd541421 48254 rust-arc-swap_0.4.8.orig.tar.gz 6c902d2beeb07b9f0dcfbe75cd41e41f616eb50d 2876 rust-arc-swap_0.4.8-1.debian.tar.xz 132d7eb20c0f3f19fb9fc4cb78219a15da8bb185 7509 rust-arc-swap_0.4.8-1_source.buildinfo Checksums-Sha256: 9ee4d4d5a678dcf736fd847ec52f02b1795d58cf3158ac24c57ac1a9cee513c5 2370 rust-arc-swap_0.4.8-1.dsc dabe5a181f83789739c194cbe5a897dde195078fac08568d09221fd6137a7ba8 48254 rust-arc-swap_0.4.8.orig.tar.gz e242159a32b9984e17893a23344205e23aecaee38cb996e28105c9eaacdd7ffd 2876 rust-arc-swap_0.4.8-1.debian.tar.xz e4a99fe518afff1b1dd261ea5d4ab8406e3205b73c8b7b4bf744ef3a7e9ec1ec 7509 rust-arc-swap_0.4.8-1_source.buildinfo Files: 40b30fbcd9bfba35e94fad2be05ed3ae 2370 rust optional rust-arc-swap_0.4.8-1.dsc a5477b618cf3f7e1d9b7febd4b93ca56 48254 rust optional rust-arc-swap_0.4.8.orig.tar.gz 8f581b9eb2c16a48d3490ea7bd1e6015 2876 rust optional rust-arc-swap_0.4.8-1.debian.tar.xz b4130d30d3af6431085ca2f28b44a8ad 7509 rust optional rust-arc-swap_0.4.8-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEEz66yQIxXO1E0pjrO1bHTe2DcM9MFAmBMoQgXHHdvbGZnYW5n QHNpbGJlcm1heXIuYXQACgkQ1bHTe2DcM9MvnQ//UjxYVMHwmn8d75j78X6j1U+0 y9IjxbCPqkeMhx6MG5EUB/sQC2iNBOs6nWG8ifNlkPi5N4frlzyVV7nVB64D3JmQ xTCSOmIsNGcQdlQ7jqW0MvQblJUTriiaL5JFcKJEt+Rdfq3yQH8s1s6m0rA0VnW9 6qMKk+Ujpgck42D3l22VnqVtmNvxPS473Y8H6rW54+yoJkzjFKS2SsQYVxnhx9mZ 9stJMk6rZL5Q8uAJrKDYR2G9c/+DvzaKI75MiCEYsyHUqcjDKdBKmeUxeDmCt0FS Z863vQFLjYbx8jVa5gQHRzvS02ScuX+n/l8Ub75LpqJBObs0y+T4Ka7ohwSHQ3op BVv4iNoB75htUUAzMtMWjYY8D7C/fN0L6TnH4ccSxLFv2cfiyVKg7L1W600xQiR3 NMJIXKJ6IqmIvmsUJ1UTRHIKIDli+YEghLNtFbOpNTH2XiVmolhe/RtfAD+AoULb exSgbD8Kig8KBboBtT6l1sKYA9wNgMtmX6J/zIGwueJOtZ94z7MJYy7qeX0OXs+T op2FBKAE+/ujZg21vX78+o9MnbFfkqOXTjWOWIx5o8jJKaTLmkrJR/UMY5eTrl4L 6bXCTsDFzW7hfdfVOEQk4XlyUYMfThbsqOBJ1Axc0KVFORb2prH2iyY8vF56CHWK K2j9D+ZG6vb4VDsR8aA= =X5Z+ -END PGP SIGNATURE End Message ---
Bug#984940: marked as done (CVE-2021-28041)
Your message dated Sat, 13 Mar 2021 10:18:28 + with message-id and subject line Bug#984940: fixed in openssh 1:8.4p1-5 has caused the Debian Bug report #984940, regarding CVE-2021-28041 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openssh Severity: important Tags: security X-Debbugs-Cc: Debian Security Team Hi, The following vulnerability was published for openssh. CVE-2021-28041[0]: | ssh-agent in OpenSSH before 8.5 has a double free that may be relevant | in a few less-common scenarios, such as unconstrained agent-socket | access on a legacy operating system, or the forwarding of an agent to | an attacker-controlled host. Buster is not affected. Isolated patch at: https://github.com/openssh/openssh-portable/commit/e04fd6dde16de1cdc5a4d9946397ff60d96568db Cheers, Moritz --- End Message --- --- Begin Message --- Source: openssh Source-Version: 1:8.4p1-5 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of openssh, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated openssh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 09:59:40 + Source: openssh Architecture: source Version: 1:8.4p1-5 Distribution: unstable Urgency: high Maintainer: Debian OpenSSH Maintainers Changed-By: Colin Watson Closes: 984940 Changes: openssh (1:8.4p1-5) unstable; urgency=high . * CVE-2021-28041: Fix double free in ssh-agent(1) (closes: #984940). Checksums-Sha1: 1bbcf852400b5c78dbb42216906749fdc257dac6 3353 openssh_8.4p1-5.dsc 8422023273c7bb8bca46d5f14c7a18effc9cbe2d 179108 openssh_8.4p1-5.debian.tar.xz Checksums-Sha256: 77f230be1493a1037ab9b1555709f597563759115f40b189605da9f1817c0138 3353 openssh_8.4p1-5.dsc 9f38375592c9903fd64a1e69f42452ddad7e7c35c561ea7b8befbf45870b1a53 179108 openssh_8.4p1-5.debian.tar.xz Files: 01355d3d331293cb3739fb10ab7cc6b9 3353 net standard openssh_8.4p1-5.dsc 584914153d290009cf68f3258cc8dec3 179108 net standard openssh_8.4p1-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmBMjTgACgkQOTWH2X2G UAs8ow/+K4Yql3/txS7i+KEbgK2N2CCL1S+lgvc3TeD+jOiEFHoFEXTRkAywoGtr YpPLDZheIDhWtJ6AY5QSK8YzMFRqy0K+WGQwbuBq1pD+a/zhLhzUM4cp9HMzYHVQ vqLO3yIdxpUj7idP9i2u5V2Yztn0qmSUOZLDSwgDO4UXvnyBNswpu+vVzKhJtFhx fCupF484PBqA0Hi1Kw/+dQ8N3ocdvbul458A9hSEqlEl5gRJjeUybY2t+EvTRwg1 9PXsZ2nwnviIASI74J4zm5YuZGrNX23wrc0M6F+2x26VnA/ClD4oH/AEdIxh1faz yKzhDyj7u1qjKo8kHbDK06hoIc44bti92n1jr/e8NOKkBpajS3BrbazXI3uRAEej kHEfdLdKwNezj258rVPMQEyVRo2e82B+dGij3l60RPeeTS0D0TJ94A2kCsTXtRdG vpRFtcHphP01cJFV3PzmvlXfOZ19jVw/6KcdC1vYNS3Fo0v6ajIxmjU9w7W3BRrG iwiZGtJkGtHg0Oia8YgWo3h4U3+3toikKAWUEZI36AHGAZSFCe8eHPBZrP+w2h1L HGhCYNvVCj0lyYUmPvN0tlN5LAWvUtOdxq/ZureOVOe5oVODObh0Sf5Z5Xhn7SBm M33eVWXR9V8/kz82jxI6SOqym72gWEuU7dfcRCjijbNB1+2kdWY= =hwEK -END PGP SIGNATURE End Message ---
Bug#984863: marked as done (samba: new upstream bugfix release 4.13.5 for bullseye)
Your message dated Sat, 13 Mar 2021 09:04:49 + with message-id and subject line Bug#984863: fixed in samba 2:4.13.5+dfsg-1 has caused the Debian Bug report #984863, regarding samba: new upstream bugfix release 4.13.5 for bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: samba Version: 2:4.13.4+dfsg-1 Severity: wishlist There is new upstream bugfix release 4.13.5 out. This includes fixes for two bugs that my workplace has been experiencing and has had to patch within our rebuild of the Debian samba package. These are the last two patches that we had for our rebuild of the bullseye package. We would very much like to no longer need to rebuild samba, so it would be great if samba 4.13.5 could enter Debian and reach Debian bullseye. https://bugzilla.samba.org/show_bug.cgi?id=13992 https://bugzilla.samba.org/show_bug.cgi?id=12505 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: samba Source-Version: 2:4.13.5+dfsg-1 Done: Mathieu Parent We believe that the bug you reported is fixed in the latest version of samba, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Parent (supplier of updated samba package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 08:31:27 +0100 Source: samba Architecture: source Version: 2:4.13.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Samba Maintainers Changed-By: Mathieu Parent Closes: 984863 Changes: samba (2:4.13.5+dfsg-1) unstable; urgency=medium . * New upstream version (Closes: #984863) Checksums-Sha1: 8ffc732b51e004547ca16cfd3166b630e7e494a1 4349 samba_4.13.5+dfsg-1.dsc a6ee880b0069561162219f98b59d27cc385afeaf 11687056 samba_4.13.5+dfsg.orig.tar.xz 68f714d9ff382b3bf5a5809c8ae7ee938f41cc49 247360 samba_4.13.5+dfsg-1.debian.tar.xz 8220199a9130c16ab482106e807f5800a76ae748 7173 samba_4.13.5+dfsg-1_source.buildinfo Checksums-Sha256: 59e5e1a64eec12d8e48ad3800ab2724428f51948702c64b206f45fa3d9df9a7e 4349 samba_4.13.5+dfsg-1.dsc 7b7177d32df67fda6ee79778d65ceaa276843eeae4d4b758ed5ee4a9f265b2de 11687056 samba_4.13.5+dfsg.orig.tar.xz 0ab033be5c7dff75c0016d43cf1378b44c72c53915e265ea933cb7d7fb32effd 247360 samba_4.13.5+dfsg-1.debian.tar.xz c09bcaf2942cec43896cd9f471a5a37fcc6765a466494d34f0c09c430403e186 7173 samba_4.13.5+dfsg-1_source.buildinfo Files: 6aeaf8f5cd1fdc9d6d2fedb78238d9fd 4349 net optional samba_4.13.5+dfsg-1.dsc 995e11642b7feee3c0228130921ac5b4 11687056 net optional samba_4.13.5+dfsg.orig.tar.xz d8d2240033aa722478e43032b290b035 247360 net optional samba_4.13.5+dfsg-1.debian.tar.xz 60b1206705597f40b77f87e11f5e9b9a 7173 net optional samba_4.13.5+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEqqWLhC6ILPQU4Lqxp8cqHHgrjD8FAmBMfSUTHHNhdGhpZXVA ZGViaWFuLm9yZwAKCRCnxyoceCuMP1upEADjTTYU/LSwBinJ3j8GuqsCKdgbTPW1 3Ez5/JP5oCIvVbPgMmCcAUaamS+3e6k51/w9feGkkOHCCyzZlw7FMNZS64GO7Ten cM6p/BohlCGQd7+q1NHmaJChmY5ca5NRI4coXkG8cHtVPtkT3M9ZwGeuXrWR7YAt b5iJ/Dnid2S2MhK/vH4Ip3FAzkUtOiWl/EvRXrW/s5ItHOd8Jcuoazfg56c7rroj 35GflZ9fxsvP24GGpn32l2o58NMrQyPgDHoMacTeD8aBLQrC+ymIWTbNLQ8M/Ai6 01obUc9atyECozIco1aPhqQgPoLj4iFg1v2VtKwCPbdwGTz0x5Md8t1PtBlb47A7 7UOWZB2HiytIQd0tqW5HusQKYpferH7XlNc7duGnE8pJrv4X4tjUjFXis78Oa+mD h5ZvfbohPQ8W7T3AOimKN1u0i15vdPohHlB6Bn9MqBlPFsQBtZtBY5KY8IWmpv6P 3EDUVzcJtX6xnde8tWcz4/FznZEgCFNxukDbdfpnMbCTnwcboGaZUseNfMkBxd7s ktKimi0kFbnxYsLPzqQRsbAS7BhaKRB9WUJpTY+fjHS4d9xImfYU7GfIbMMtQU4f JjseK7pm0vXStUTRnrX5rTCImSQm/LHAWG4T32iu71VcN8o5nI1mLZodh19RZ4BQ 2ywh+sm0AkeGkw== =r9qv -END PGP SIGNATURE End Message ---
Bug#984838: marked as done (libboost1.74-dev: depends on libstdc++-dev provided by multiple packages)
Your message dated Sat, 13 Mar 2021 08:48:44 +
with message-id
and subject line Bug#984838: fixed in boost1.74 1.74.0-9
has caused the Debian Bug report #984838,
regarding libboost1.74-dev: depends on libstdc++-dev provided by multiple
packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
984838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost1.74-dev
Version: 1.74.0-8
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
libstdc++-dev is not a good virtual package to depend upon, since it is
provided by multiple packages:
bullseye# apt-get install libstdc++-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package libstdc++-dev is a virtual package provided by:
libstdc++-9-dev 9.3.0-22
libstdc++-10-dev 10.2.1-6
You should explicitly select one to install.
E: Package 'libstdc++-dev' has no installation candidate
If apt has to choose, it may select the wrong one:
bullseye# apt-get install libboost1.74-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libstdc++-9-dev
Suggested packages:
libboost1.74-doc libboost-atomic1.74-dev libboost-chrono1.74-dev
libboost-container1.74-dev libboost-context1.74-dev libboost-contract1.74-dev
libboost-coroutine1.74-dev libboost-date-time1.74-dev
libboost-exception1.74-dev libboost-fiber1.74-dev
libboost-filesystem1.74-dev libboost-graph1.74-dev
libboost-graph-parallel1.74-dev libboost-iostreams1.74-dev
libboost-locale1.74-dev libboost-log1.74-dev libboost-math1.74-dev
libboost-mpi1.74-dev libboost-mpi-python1.74-dev libboost-numpy1.74-dev
libboost-program-options1.74-dev libboost-python1.74-dev
libboost-random1.74-dev libboost-regex1.74-dev libboost-serialization1.74-dev
libboost-stacktrace1.74-dev libboost-system1.74-dev libboost-test1.74-dev
libboost-thread1.74-dev libboost-timer1.74-dev
libboost-type-erasure1.74-dev libboost-wave1.74-dev libboost1.74-tools-dev
libmpfrc++-dev libntl-dev libboost-nowide1.74-dev libstdc++-9-doc
The following NEW packages will be installed:
libboost1.74-dev libstdc++-9-dev
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/11.2 MB of archives.
After this operation, 159 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
But worse, on upgrades from buster to bullseye libstdc++-8-dev would
have to be removed and libstdc++-10-dev would have to be installed to
perform a clean upgrade, but I've found with piuparts a few upgrade
paths where apt prefers to keep libstdc++-8-dev installed since it
provides libstdc++-dev. That causes the upgrade to fail, since apt
cannot find a valid upgrade path at al in these cases.
The attached patch exchanges this dependency to
Upgrading to the packages with this patch applied fixes all the issues I
observed. I also tried a
Depends: libstdc++-10-dev | libstdc++-dev
but that leaves us with the failure I initially observed
Andreas
diff -Nru boost1.74-1.74.0/debian/changelog boost1.74-1.74.0/debian/changelog
--- boost1.74-1.74.0/debian/changelog 2021-01-23 20:00:18.0 +0100
+++ boost1.74-1.74.0/debian/changelog 2021-03-08 16:18:55.0 +0100
@@ -1,3 +1,13 @@
+boost1.74 (1.74.0-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * libboost1.74-dev: Smoothen upgrades from buster by depending on
+libstdc++-${gxx:major}-dev using the build-time version of g++ instead of
+the virtual libstdc++-dev provided by multiple packages.
+(Closes: #xx)
+
+ -- Andreas Beckmann Mon, 08 Mar 2021 16:18:55 +0100
+
boost1.74 (1.74.0-8) unstable; urgency=medium
* [85a2610] Fix compilation warnings. (Closes: #980497)
diff -Nru boost1.74-1.74.0/debian/control boost1.74-1.74.0/debian/control
--- boost1.74-1.74.0/debian/control 2021-01-23 19:37:38.0 +0100
+++ boost1.74-1.74.0/debian/control 2021-03-08 16:18:55.0 +0100
@@ -24,7 +24,7 @@
Architecture: any
Multi-Arch: same
Section: libdevel
-Depends: ${misc:Depends}, ${shlibs:Depends}, libstdc++-dev
+Depends: ${misc:Depends}, ${shlibs:Depends}, libstdc++-${gxx:major}-dev
Suggests: libboost1.74-doc,
libboost-atomic1.74-dev,
libboost-chrono1.74-dev,
diff -Nru boost1.74-1.74.0/debian/rules boost1.74-1.74.0/debian/rules
--- boost1.74-1.74.0/debian/rules 2020-12-25 23:26:58.0 +0100
+++ boost1.74-1.74.0/debian/rules
Bug#985110: marked as done (node-url-parse: CVE-2021-27515)
Your message dated Sat, 13 Mar 2021 08:19:14 + with message-id and subject line Bug#985110: fixed in node-url-parse 1.5.1-1 has caused the Debian Bug report #985110, regarding node-url-parse: CVE-2021-27515 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-url-parse Version: 1.4.7+repack-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-url-parse. CVE-2021-27515[0]: | url-parse before 1.5.0 mishandles certain uses of backslash such as | http:\/ and interprets the URI as a relative path. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-27515 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515 [1] https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0 Regards, Salvatore --- End Message --- --- Begin Message --- Source: node-url-parse Source-Version: 1.5.1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-url-parse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-url-parse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 08:55:57 +0100 Source: node-url-parse Architecture: source Version: 1.5.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 985110 Changes: node-url-parse (1.5.1-1) unstable; urgency=medium . * Team upload * New upstream version 1.5.1 (Closes: #985110, CVE-2021-27515) Checksums-Sha1: 41ecc286f6d90b1dd1cf1612b43a55133e54b233 2551 node-url-parse_1.5.1-1.dsc fba49d90f834951cb000a674efee3d6f20968329 2028 node-url-parse_1.5.1.orig-types-url-parse.tar.gz b8328c86ecc8d86cf2f40806a2f9285dbbaa1094 15752 node-url-parse_1.5.1.orig.tar.gz e9729616413c186f1132c05e9819e8e0d223daf2 4120 node-url-parse_1.5.1-1.debian.tar.xz Checksums-Sha256: 7fbb638e124745465fa3f7b9d89a879697e16f54a4bfceab0bf91659bf84b6c7 2551 node-url-parse_1.5.1-1.dsc aacd8bb80991adce84b6305b2f64d1644f16ac47376a095895417647b03e 2028 node-url-parse_1.5.1.orig-types-url-parse.tar.gz a06e817a6da716b87be010e04c20b03ce184749da94124377706c5acf637e75b 15752 node-url-parse_1.5.1.orig.tar.gz 06a4602e903e90f456f17bf3950905af6cd80e608d9e82cd4db391753d3ced26 4120 node-url-parse_1.5.1-1.debian.tar.xz Files: 6d221fbe04a72c81597aac560562a7dc 2551 javascript optional node-url-parse_1.5.1-1.dsc 782204fc24278d978e12ef488becc87e 2028 javascript optional node-url-parse_1.5.1.orig-types-url-parse.tar.gz 9ac71a05eb039ce09af472d1748e05ac 15752 javascript optional node-url-parse_1.5.1.orig.tar.gz 9eb7b501f9679fbacfe4cdb17b628d15 4120 javascript optional node-url-parse_1.5.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmBMcHcACgkQ9tdMp8mZ 7uloKg//W2SiSFbfj7XjA+oRpDgteFUf58/JUPkuyIM4YWLSmNWJ0DYEtDAR59cw blv86dUx9pVmJnyEiC+DcUrYMFmZOFRG32tonbFdrNPuWOiKbIUBzXIaIYBEw36b VEdEABzt34Vl6+wy6/1LplQAtiTEyAridOHmvdiUtYaOIvWfGOH+nUjfBekIn/Kw J/De96OzfZ5j1rnalkIOlpVExKCiHe+DgUaIdhD+JYoOcIN3E+RZhVFvpDcCdUaB 6xoSQedLdVAb4BuI5+0kPmaAmhKZDhUUYAX460FquAGFRYNBfjGB8iEG132i3igD M6pMZk1AtDvW2dNYpAvdOC0DC/nG+xTYq+s1ijU4msg+jlINRTWlPmQhLTysSUDu jTxfPsZ3XNZumCsYhaMlPA0mqZMx0F0xVhxfBh/JHtoKoIrkPBYOe/4+xQN9u0Pt DbrpNw9O7+fgQLkfbadEoAfqcTLL6rlF9h//cpmbKIPTUMOGqHDdJ2wRJLApHy5C LDTHPJKdIcoXXnZPzaaUBBB+uu+jVz/bPLmLISD1jbAx3vivczJ2iqzXtSStKUP0 rQ3dbIBvdXzJN+Utet8kCIVe1aCaDJDHPVYLmJCSH0HemNjVEAOnoFdYbkFECNFZ mZWQYvDLR1qHeUI11NQX5x+IhifuhL/dqLcfHnsH9oz6ZrgnUnI= =c9hT -END PGP SIGNATURE End Message ---
Bug#985109: marked as done (node-prismjs: CVE-2021-23341)
Your message dated Sat, 13 Mar 2021 08:19:07 + with message-id and subject line Bug#985109: fixed in node-prismjs 1.23.0+dfsg-1 has caused the Debian Bug report #985109, regarding node-prismjs: CVE-2021-23341 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-prismjs Version: 1.11.0+dfsg-4 Severity: important Tags: security upstream Forwarded: https://github.com/PrismJS/prism/issues/2583 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-prismjs. CVE-2021-23341[0]: | The package prismjs before 1.23.0 are vulnerable to Regular Expression | Denial of Service (ReDoS) via the prism-asciidoc, prism-rest, prism- | tap and prism-eiffel components. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-23341 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23341 [1] https://github.com/PrismJS/prism/issues/2583 Regards, Salvatore --- End Message --- --- Begin Message --- Source: node-prismjs Source-Version: 1.23.0+dfsg-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-prismjs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-prismjs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Mar 2021 08:52:25 +0100 Source: node-prismjs Architecture: source Version: 1.23.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 985109 Changes: node-prismjs (1.23.0+dfsg-1) unstable; urgency=medium . * Team upload . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Yadd ] * Add "Rules-Requires-Root: no" * Bump debhelper compatibility level to 13 * Declare compliance with policy 4.5.1 * Modernize debian/watch * Use dh-sequence-nodejs * New upstream version 1.23.0+dfsg (Closes: 985109, CVE-2021-23341) Checksums-Sha1: a97975d69d350a6a2c769fbc5ba8a96e214a0c30 2119 node-prismjs_1.23.0+dfsg-1.dsc 96635061c6e716d327772a979f05f0fcc281af68 1996764 node-prismjs_1.23.0+dfsg.orig.tar.xz cb7df3fdfc23025dda68330825799db70ed689ea 3744 node-prismjs_1.23.0+dfsg-1.debian.tar.xz Checksums-Sha256: 257d6372afe76707d22f71c7ea5312bd2e98a06d0efa97e4170f6489b11a1ff8 2119 node-prismjs_1.23.0+dfsg-1.dsc 493c99f34c8ca116d58adc16ef39cf77f1d912004f5faf649a61a8c424ae7b1c 1996764 node-prismjs_1.23.0+dfsg.orig.tar.xz 326cdfc4f77d8bf64dd09e8b62aa0bf4e425505bc22d107554b729dea69f265d 3744 node-prismjs_1.23.0+dfsg-1.debian.tar.xz Files: 0edf83aea03b6dd1c60618fa3a504932 2119 javascript optional node-prismjs_1.23.0+dfsg-1.dsc 0470807e4396fce031f81eb1f97e933e 1996764 javascript optional node-prismjs_1.23.0+dfsg.orig.tar.xz 506581d29a45c7602379a27edafe8621 3744 javascript optional node-prismjs_1.23.0+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmBMb54ACgkQ9tdMp8mZ 7ulvKw//YMxgHUneZ3N1r//n+HGbu63xVqtoB3RaMwF4SLuiENniDzV7GBnuVirE FceZ+MhIT8MkHQjq+aAn87M1CQ5DNLNJVD4i2utVBjExAmN62kesGndUY6QsXdwL V9n90QhgsARR3e62gDQnwbS9j8r3a5obGhz1dHdTK+zOcbNCkXY7yHKlgVrw7kJw JhUlUsl7awBeZKJ+FR/bsC2XT601s1UtG5KDBlzQYhgBzCwM5sVbxuAuv69e8Rfz 2xVvLOyLMwTp989R+RzIz85ML6PMGEcowmL+CNQ7vc6iSCuRBON+evGhQYAO+FXf bBBn/i69bwAXM6W0PGY4auZYZUKkGCnnH4XsfmAYVO2y/M47Or1Ksd64XaCP4GTD KkKSI1gwK5TtSEM/XCQRM8aCyo7Sy33ZtzLFD4LwbAN1xUJFuoqq0JNv6vZ64FWT gGVbWRmT1wrpf+nh59ZnzWaq87JdX5Ins1g7aQqZ1DQ6QC9/y150NFI6OZvzRezK 6ucpGfqWn/oPHxZcy3xZfECkz0pEkchfUaOsESNuAg9Xmh7tgL1zR23v3mtOIRsE lHafawmG1L4rufMKK5w1P7P0TDQ7paZlOfx89GE2G75UTonVvtE4q7afePSgZrft LK7/nAHjRr8ggwUawTdDjUEmWme3Rger2EUcQvHypKYxZmw+W+4= =YSyO -END PGP SIGNATURE End Message ---
Bug#659544: marked as done (Using \pause in a TikZ picture makes footer disappear on all but last slide)
Your message dated Sat, 13 Mar 2021 09:08:50 +0100
with message-id <73f7f271-682f-d7b0-61de-17e614c8e...@web.de>
and subject line Re: Bug#659544: Using \pause in a TikZ picture makes footer
disappear on all but last slide
has caused the Debian Bug report #659544,
regarding Using \pause in a TikZ picture makes footer disappear on all but last
slide
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
659544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: latex-beamer
Version: 3.10-1
Severity: normal
When using a theme with a footer, if I create a slide which uses \pause
within a TikZ picture to create an incrementally overlaid diagram, the
footer will disappear on all but the last sub-slide. This doesn't
happen when using \pause outside of a TikZ picture, nor does it happen
when using full overlay specifications in a TikZ picture.
I've attached a minimal test case.
- Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages latex-beamer depends on:
ii latex-xcolor2.11-1
ii pgf 2.10-1
ii texlive-latex-base 2009-15
latex-beamer recommends no packages.
latex-beamer suggests no packages.
-- no debconf information
\documentclass{beamer}
\usepackage{tikz}
\usetheme{Madrid}
\beamertemplatenavigationsymbolsempty
\title{The case of the missing footer}
\subtitle{A minimal test case}
\author{Josh Triplett}
\date{February 11, 2012}
\begin{document}
\maketitle
\begin{frame}{Overlays with overlay specifications}
\begin{itemize}
\item<1-> Footer appears as expected
\item<2-> On both pages
\end{itemize}
\end{frame}
\begin{frame}{Overlays with pause}
\begin{itemize}
\item Footer appears as expected
\pause
\item On both pages
\end{itemize}
\end{frame}
\begin{frame}{Overlays in TikZ with overlay specifications on node}
\begin{tikzpicture}
\node<1-> at (0,0) {Footer appears as expected};
\node<2-> at (0,-1) {On both pages};
\end{tikzpicture}
\end{frame}
\begin{frame}{Overlays in TikZ with overlay specifications around node}
\begin{tikzpicture}
\visible<1->{\node at (0,0) {Footer appears as expected};}
\visible<2->{\node at (0,-1) {On both pages};}
\end{tikzpicture}
\end{frame}
\begin{frame}{Overlays in TikZ with pause}
\begin{tikzpicture}
\node at (0,0) {No footer on this page};
\pause
\node at (0,-1) {Only on this page};
\end{tikzpicture}
\end{frame}
\end{document}--- End Message ---
--- Begin Message ---
Am 03.08.2019 um 13:06 teilte Hilmar Preuße mit:
Am 07.05.2014 um 21:06 teilte Hilmar Preusse mit:
On 12.02.12 Josh Triplett (j...@joshtriplett.org) wrote:
When using a theme with a footer, if I create a slide which uses
\pause within a TikZ picture to create an incrementally overlaid
diagram, the footer will disappear on all but the last sub-slide.
This doesn't happen when using \pause outside of a TikZ picture,
nor does it happen when using full overlay specifications in a TikZ
picture.
Seems to be known in upstream:
https://bitbucket.org/rivanvx/beamer/issue/278/tikz-overlay-breaks-footer
Could you test the fix for that issue:
https://bitbucket.org/rivanvx/beamer/commits/f6bd5e3805daadedb29ee5a976a5c30a4efe3e35/raw/
New URL: https://github.com/josephwright/beamer/issues/278
The issue has been closed in 2016, hence I'd assume that the fix has
made it into Debian. Could you confirm that the issue is solved?
No reaction foom customer for > 1,5 years and issue probably solved.
Closing.
Hilmar
--
sigfault
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
