Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard
Dear Maintainer, I confirm this issue. I experienced it with an AMD R7 240 graphics card[1] on a regular Debian Sid host running kernel 6.6.15. Booting with the previous kernel (6.6.13) did not change the situation but I confirm "Accel" "no", as suggested by Grégory, is a suitable workaround. The machine that experiences this issue idles most of the time, so let me know if I can do/provide anything that would help solving this. Cheers, -- Xavier G. [1] lspci: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340 / Radeon 520]
Bug#1029047: software-properties-qt: software-property-qt should depends on lazr
Package: software-properties-qt Version: 0.99.30-3 Severity: grave Justification: renders package unusable Dear Maintainer, When launching software-properties-qt, I get the following message : ❯ /usr/bin/software-properties-qt Traceback (most recent call last): File "/usr/bin/software-properties-qt", line 36, in from softwareproperties.qt.SoftwarePropertiesQt import SoftwarePropertiesQt File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 45, in from softwareproperties.SoftwareProperties import SoftwareProperties File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 62, in from softwareproperties.shortcuts import shortcut_handler File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 23, in from softwareproperties.ppa import PPAShortcutHandler File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, in from lazr.restfulclient.errors import (NotFound, BadRequest, Unauthorized) ModuleNotFoundError: No module named 'lazr' The package should include a runtime depends on python3-lazr.uri. Thanks, -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages software-properties-qt depends on: ii debconf-kde-helper 1.1.0-1 ii python3 3.11.1-1 ii python3-pyqt55.15.7+dfsg-3+b3 ii python3-software-properties 0.99.30-3 ii software-properties-common 0.99.30-3 software-properties-qt recommends no packages. Versions of packages software-properties-qt suggests: ii plasma-discover 5.26.5-2 -- no debconf information -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1028913: closed by Debian FTP Masters (reply to Emmanuel Arias ) (Bug#1028913: fixed in poetry 1.3.2+dfsg-2)
Hello, python3-pylev isn't a Build-Deb but à runtime dependencie Thank you so much Le 15 janv. à 01:39 Debian Bug Tracking System a écrit > This is an automatic notification regarding your Bug report > which was filed against the python3-poetry package: > > #1028913: python3-poetry: poetry commands depends on pylev (python3-pylev) > > It has been closed by Debian FTP Masters > (reply to Emmanuel Arias ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > (reply to Emmanuel Arias > ) by > replying to this email. > > > -- > 1028913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028913 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Sun, 15 Jan 2023 00:35:49 + > From: Debian FTP Masters > To: 1028913-cl...@bugs.debian.org > Subject: Bug#1028913: fixed in poetry 1.3.2+dfsg-2 > Reply-To: Emmanuel Arias > Message-Id: > [---=| Quote block shrunk by t-prot: 82 lines snipped |=---] > > python3-poetry suggests no packages. > > -- no debconf information > > -- > Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net > > Société Libre, Logiciel Libre http://www.april.org/adherer > Parinux, logiciel libre à Paris : http://www.parinux.org -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1028913: python3-poetry: poetry commands depends on pylev (python3-pylev)
Package: python3-poetry Version: 1.3.2+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, I've observed on Debian Sid that python3-pylev has to be removed when upgrading to python3.11. Alas, when trying to work with poetry, i got the following traceback : ❯ poetry new Traceback (most recent call last): File "/usr/bin/poetry", line 5, in from poetry.console.application import main File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 11, in from cleo.application import Application as BaseApplication File "/usr/lib/python3/dist-packages/cleo/application.py", line 12, in from cleo.commands.completions_command import CompletionsCommand File "/usr/lib/python3/dist-packages/cleo/commands/completions_command.py", line 10, in from cleo import helpers File "/usr/lib/python3/dist-packages/cleo/helpers.py", line 5, in from cleo.io.inputs.argument import Argument File "/usr/lib/python3/dist-packages/cleo/io/inputs/argument.py", line 5, in from cleo.exceptions import CleoLogicError File "/usr/lib/python3/dist-packages/cleo/exceptions/__init__.py", line 3, in from cleo._utils import find_similar_names File "/usr/lib/python3/dist-packages/cleo/_utils.py", line 8, in from pylev import levenshtein ModuleNotFoundError: No module named 'pylev' Poetry should depends on python3-pylev : if I install poetry in a Python virtualenv, every thing works as excpeted and it pulls pylev from pip ; if I install python3-pylev direct, poetry works fine. I've even tested on a fresh new debian:sid docker image. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-poetry depends on: ii python3 3.11.1-1 ii python3-cachecontrol0.12.12-2 ii python3-cleo2.0.1-3 ii python3-crashtest 0.4.1-1 ii python3-dulwich 0.20.50-1+b1 ii python3-filelock3.9.0-1 ii python3-html5lib1.1-3 ii python3-importlib-metadata 4.12.0-1 ii python3-jsonschema 4.9.1-3 ii python3-keyring 23.9.3-2 ii python3-lockfile1:0.12.2-2.2 ii python3-packaging 23.0-1 ii python3-pexpect 4.8.0-4 ii python3-pkginfo 1.8.2-2 ii python3-platformdirs2.6.0-1 ii python3-poetry-core 1.4.0-3 ii python3-requests2.28.1+dfsg-1 ii python3-requests-toolbelt 0.10.1-1 ii python3-shellingham 1.5.0-1 ii python3-tomli 2.0.1-2 ii python3-tomlkit 0.11.6-1 ii python3-urllib3 1.26.12-1 ii python3-virtualenv 20.17.1+ds-1 python3-poetry recommends no packages. python3-poetry suggests no packages. -- no debconf information -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#965454: chise-base: diff for NMU version 0.3.0-2.2
Control: tags 965454 + patch
Control: tags 965454 + pending
Dear maintainer,
I've prepared an NMU for chise-base (versioned as 0.3.0-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u chise-base-0.3.0/debian/changelog chise-base-0.3.0/debian/changelog
--- chise-base-0.3.0/debian/changelog
+++ chise-base-0.3.0/debian/changelog
@@ -1,3 +1,14 @@
+chise-base (0.3.0-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Using new DH level format. Consequently:
+ - debian/compat: removed.
+ - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+ - Closes: #965454
+
+ -- Guilherme de Paula Xavier Segundo Fri, 22 Apr 2022 13:29:50 -0300
+
chise-base (0.3.0-2.1) unstable; urgency=medium
* Non-maintainer upload.
reverted:
--- chise-base-0.3.0/debian/compat
+++ chise-base-0.3.0.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u chise-base-0.3.0/debian/control chise-base-0.3.0/debian/control
--- chise-base-0.3.0/debian/control
+++ chise-base-0.3.0/debian/control
@@ -2,7 +2,7 @@
Priority: optional
Section: devel
Maintainer: NIIBE Yutaka
-Build-Depends: debhelper (>= 5.0.0), libdb-dev (>= 4.8)
+Build-Depends: debhelper-compat (= 13), libdb-dev (>= 4.8)
Standards-Version: 3.8.4
Package: chise-db
diff -u chise-base-0.3.0/libchise/config.guess chise-base-0.3.0/libchise/config.guess
--- chise-base-0.3.0/libchise/config.guess
+++ chise-base-0.3.0/libchise/config.guess
@@ -1,14 +1,14 @@
#! /bin/sh
# Attempt to guess a canonical system name.
-# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-# 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
-# Free Software Foundation, Inc.
+# Copyright 1992-2022 Free Software Foundation, Inc.
-timestamp='2009-06-10'
+# shellcheck disable=SC2006,SC2268 # see below for rationale
+
+timestamp='2022-01-09'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful, but
@@ -17,26 +17,30 @@
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
-# 02110-1301, USA.
+# along with this program; if not, see <https://www.gnu.org/licenses/>.
#
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-
-# Originally written by Per Bothner .
-# Please send patches to . Submit a context
-# diff and a properly formatted ChangeLog entry.
+# the same distribution terms that you use for the rest of that
+# program. This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
#
-# This script attempts to guess a canonical system name similar to
-# config.sub. If it succeeds, it prints the system name on stdout, and
-# exits with 0. Otherwise, it exits with 1.
+# Originally written by Per Bothner; maintained since 2000 by Ben Elliston.
#
-# The plan is that this can be called by configure scripts if you
-# don't specify an explicit build system type.
+# You can get the latest version of this script from:
+# https://git.savannah.gnu.org/cgit/config.git/plain/config.guess
+#
+# Please send patches to .
+
+
+# The "shellcheck disable" line above the timestamp inhibits complaints
+# about features and limitations of the classic Bourne shell that were
+# superseded or lifted in POSIX. However, this script identifies a wide
+# variety of pre-POSIX systems that do not have POSIX shells at all, and
+# even some reasonably current systems (Solaris 10 as case-in-point) still
+# have a pre-POSIX /bin/sh.
+
me=`echo "$0" | sed -e 's,.*/,,'`
@@ -45,7 +49,7 @@
Output the configuration name of the system \`$me' is run on.
-Operation modes:
+Options:
-h, --help print this help, then exit
-t, --time-stamp print date of last modification, then exit
-v, --version print version number, then exit
@@ -56,8 +60,7 @@
GNU config.guess ($timestamp)
Originally written by Per Bothner.
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001,
-2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
+Copyright 1992-2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warr
Bug#965736: msp430mcu: diff for NMU version 20120406-2.2
Control: tags 965736 + patch Control: tags 965736 + pending Dear maintainer, I've prepared an NMU for msp430mcu (versioned as 20120406-2.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru msp430mcu-20120406/debian/changelog msp430mcu-20120406/debian/changelog --- msp430mcu-20120406/debian/changelog 2021-01-03 11:45:50.0 -0300 +++ msp430mcu-20120406/debian/changelog 2022-04-22 14:18:57.0 -0300 @@ -1,3 +1,14 @@ +msp430mcu (20120406-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965736 + + -- Guilherme de Paula Xavier Segundo Fri, 22 Apr 2022 14:18:57 -0300 + msp430mcu (20120406-2.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru msp430mcu-20120406/debian/compat msp430mcu-20120406/debian/compat --- msp430mcu-20120406/debian/compat 2012-05-10 12:16:44.0 -0300 +++ msp430mcu-20120406/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru msp430mcu-20120406/debian/control msp430mcu-20120406/debian/control --- msp430mcu-20120406/debian/control 2012-05-10 12:16:44.0 -0300 +++ msp430mcu-20120406/debian/control 2022-04-22 14:18:57.0 -0300 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Luca Bruno Standards-Version: 3.9.3 -Build-Depends: debhelper (>= 7) +Build-Depends: debhelper-compat (= 13) Package: msp430mcu Architecture: all
Bug#1010000: podman run panics with "assignment to entry in nil map"
Package: podman
Version: 3.4.7+ds1-2
Followup-For: Bug #101
Dear Maintainer,
Unfortunately, it seems upgrading from 3.4.7+ds1-1 to 3.4.7+ds1-2 does not
solve the issue reported by Norbert.
I tested as root user to avoid potential rootless-induced issues:
# dpkg -l podman
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---==
ii podman 3.4.7+ds1-2 amd64engine to run OCI-based containers
in Pods
# podman run alpine date
panic: assignment to entry in nil map
goroutine 1 [running]:
github.com/opencontainers/runtime-tools/generate.(*Generator).addEnv(...)
github.com/opencontainers/runtime-tools/generate/generate.go:532
github.com/opencontainers/runtime-tools/generate.(*Generator).AddProcessEnv(0xc00053da20,
{0x17edeb7, 0x8}, {0xc0004022c0, 0xc})
github.com/opencontainers/runtime-tools/generate/generate.go:508 +0x2ea
github.com/containers/podman/libpod.(*Container).generateSpec(0xc00031e790,
{0x1ad3150, 0xc000228d20})
github.com/containers/podman/libpod/container_internal_linux.go:648
+0x2965
github.com/containers/podman/libpod.(*Container).init(0xc00031e790, {0x1ad3150,
0xc000228d20}, 0x0)
github.com/containers/podman/libpod/container_internal.go:1098 +0x8e
github.com/containers/podman/libpod.(*Container).prepareToStart(0xc00031e790,
{0x1ad3150, 0xc000228d20}, 0xa8?)
github.com/containers/podman/libpod/container_internal.go:875 +0x345
github.com/containers/podman/libpod.(*Container).StartAndAttach(0xc00031e790,
{0x1ad3150?, 0xc000228d20?}, 0xc0006300c0, {0x17f5ed4, 0xd}, 0xc949c0,
0xb0?)
github.com/containers/podman/libpod/container_api.go:115 +0x145
github.com/containers/podman/pkg/domain/infra/abi/terminal.StartAttachCtr({0x1ad3150,
0xc000228d20}, 0xc00031e790, 0xc10018, 0xc10020, 0x0, {0x17f5ed4,
0xd}, 0x1, 0x1)
github.com/containers/podman/pkg/domain/infra/abi/terminal/terminal_linux.go:91
+0x546
github.com/containers/podman/pkg/domain/infra/abi.(*ContainerEngine).ContainerRun(0xc0001249f8,
{0x1ad3150, 0xc000228d20}, {{0x0, 0x0}, 0x0, {0x17f5ed4, 0xd}, 0xc10020,
0x0, ...})
github.com/containers/podman/pkg/domain/infra/abi/containers.go:957
+0x31e
github.com/containers/podman/cmd/podman/containers.run(0x25046a0?,
{0xc4ae60?, 0x2, 0x2})
github.com/containers/podman/cmd/podman/containers/run.go:194 +0x7e6
github.com/spf13/cobra.(*Command).execute(0x25046a0, {0xc3c0a0, 0x2, 0x2})
github.com/spf13/cobra/command.go:856 +0x67c
github.com/spf13/cobra.(*Command).ExecuteC(0x251b3a0)
github.com/spf13/cobra/command.go:974 +0x3b4
github.com/spf13/cobra.(*Command).Execute(...)
github.com/spf13/cobra/command.go:902
github.com/spf13/cobra.(*Command).ExecuteContext(...)
github.com/spf13/cobra/command.go:895
main.Execute()
github.com/containers/podman/cmd/podman/root.go:91 +0xc5
main.main()
github.com/containers/podman/cmd/podman/main.go:39 +0x74
Let me know if there is anything I can do to help on this matter.
Thanks for your work.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
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)
Versions of packages podman depends on:
ii conmon 2.0.25+ds1-1.1
ii containernetworking-plugins 1.1.0+ds1-1
ii crun 0.17+dfsg-1.1
ii golang-github-containers-common 0.44.5+ds1-1
ii libc62.33-7
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgpgme11 1.16.0-1.2
ii libseccomp2 2.5.4-1
ii runc 1.1.1+ds1-1
Versions of packages podman recommends:
ii buildah 1.23.1+ds1-2
pn catatonit | tini | dumb-init
ii fuse-overlayfs1.8.2-1
pn golang-github-containernetworking-plugin-dnsname
ii slirp4netns 1.0.1-2
ii uidmap1:4.11.1+dfsg1-2
Versions of packages podman suggests:
ii containers-storage 1.37.2+ds1-1
ii docker-compose 1.29.2-1
ii iptables1.8.7-1
-- no debconf information
Bug#965756: oneliner-el: diff for NMU version 0.3.6-9.2
Control: tags 965756 + patch Control: tags 965756 + pending Dear maintainer, I've prepared an NMU for oneliner-el (versioned as 0.3.6-9.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -u oneliner-el-0.3.6/debian/changelog oneliner-el-0.3.6/debian/changelog --- oneliner-el-0.3.6/debian/changelog +++ oneliner-el-0.3.6/debian/changelog @@ -1,3 +1,16 @@ +oneliner-el (0.3.6-9.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: +- debian/compat: removed. +- debian/control: changed from 'debhelper' to 'debhelper-compat' in + Build-Depends field and bumped level to 13. +- debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the + '-k' option is not supported since compat 12. +- Closes: #965756 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 11:01:29 -0300 + oneliner-el (0.3.6-9.1) unstable; urgency=medium * Non-maintainer upload. reverted: --- oneliner-el-0.3.6/debian/compat +++ oneliner-el-0.3.6.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u oneliner-el-0.3.6/debian/control oneliner-el-0.3.6/debian/control --- oneliner-el-0.3.6/debian/control +++ oneliner-el-0.3.6/debian/control @@ -1,6 +1,6 @@ Source: oneliner-el Section: editors -Build-Depends: debhelper (>= 5.0.0) +Build-Depends: debhelper-compat (= 13) Priority: optional Maintainer: OHURA Makoto Build-Depends-Indep: docbook-to-man, emacs, texinfo, po-debconf diff -u oneliner-el-0.3.6/debian/rules oneliner-el-0.3.6/debian/rules --- oneliner-el-0.3.6/debian/rules +++ oneliner-el-0.3.6/debian/rules @@ -68,7 +68,7 @@ install: build dh_testdir dh_testroot - dh_clean -k + dh_prep dh_installdirs # Add here commands to install the package into debian/oneliner-el.
Bug#965742: nagios-plugins-rabbitmq: diff for NMU version 1:1.2.0-2.4
Control: tags 965742 + patch Control: tags 965742 + pending Dear maintainer, I've prepared an NMU for nagios-plugins-rabbitmq (versioned as 1:1.2.0-2.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u nagios-plugins-rabbitmq-1.2.0/debian/changelog nagios-plugins-rabbitmq-1.2.0/debian/changelog --- nagios-plugins-rabbitmq-1.2.0/debian/changelog +++ nagios-plugins-rabbitmq-1.2.0/debian/changelog @@ -1,3 +1,14 @@ +nagios-plugins-rabbitmq (1:1.2.0-2.4) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965742 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 10:46:52 -0300 + nagios-plugins-rabbitmq (1:1.2.0-2.3) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. reverted: --- nagios-plugins-rabbitmq-1.2.0/debian/compat +++ nagios-plugins-rabbitmq-1.2.0.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u nagios-plugins-rabbitmq-1.2.0/debian/control nagios-plugins-rabbitmq-1.2.0/debian/control --- nagios-plugins-rabbitmq-1.2.0/debian/control +++ nagios-plugins-rabbitmq-1.2.0/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Cyril Bouthors Uploaders: Cyril Bouthors , Cyril Bouthors -Build-Depends: debhelper (>= 5), rsync, libmodule-build-perl +Build-Depends: debhelper-compat (= 13), rsync, libmodule-build-perl Standards-Version: 3.9.5 Package: nagios-plugins-rabbitmq
Bug#965738: mylvmbackup: diff for NMU version 0.15-1.2
Control: tags 965738 + patch Control: tags 965738 + pending Dear maintainer, I've prepared an NMU for mylvmbackup (versioned as 0.15-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru mylvmbackup-0.15/debian/changelog mylvmbackup-0.15/debian/changelog --- mylvmbackup-0.15/debian/changelog 2017-01-13 17:34:08.0 -0200 +++ mylvmbackup-0.15/debian/changelog 2022-04-21 10:42:15.0 -0300 @@ -1,3 +1,14 @@ +mylvmbackup (0.15-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: +- debian/compat: removed. +- debian/control: changed from 'debhelper' to 'debhelper-compat' in + Build-Depends field and bumped level to 13. +- Closes: #965738 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 10:42:15 -0300 + mylvmbackup (0.15-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru mylvmbackup-0.15/debian/compat mylvmbackup-0.15/debian/compat --- mylvmbackup-0.15/debian/compat 2014-05-22 14:26:26.0 -0300 +++ mylvmbackup-0.15/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru mylvmbackup-0.15/debian/control mylvmbackup-0.15/debian/control --- mylvmbackup-0.15/debian/control 2017-01-13 17:34:08.0 -0200 +++ mylvmbackup-0.15/debian/control 2022-04-21 10:42:15.0 -0300 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Debian MySQL Maintainers Uploaders: Norbert Tretkowski -Build-Depends: debhelper (>= 7.0.50), asciidoc (>= 8.2.0), xsltproc, docbook-xsl +Build-Depends: debhelper-compat (= 13), asciidoc (>= 8.2.0), xsltproc, docbook-xsl Standards-Version: 3.9.4 Homepage: http://lenzg.net/mylvmbackup/ Vcs-Browser: http://svn.debian.org/wsvn/pkg-mysql/mylvmbackup/
Bug#965733: mrb: diff for NMU version 0.3+nmu2
Control: tags 965733 + patch Control: tags 965733 + pending Dear maintainer, I've prepared an NMU for mrb (versioned as 0.3+nmu2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru mrb-0.3+nmu1/debian/changelog mrb-0.3+nmu2/debian/changelog --- mrb-0.3+nmu1/debian/changelog 2021-01-08 09:47:17.0 -0300 +++ mrb-0.3+nmu2/debian/changelog 2022-04-21 10:33:07.0 -0300 @@ -1,3 +1,14 @@ +mrb (0.3+nmu2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965733 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 10:33:07 -0300 + mrb (0.3+nmu1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru mrb-0.3+nmu1/debian/compat mrb-0.3+nmu2/debian/compat --- mrb-0.3+nmu1/debian/compat 2016-08-15 07:56:16.0 -0300 +++ mrb-0.3+nmu2/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru mrb-0.3+nmu1/debian/control mrb-0.3+nmu2/debian/control --- mrb-0.3+nmu1/debian/control 2016-08-15 07:56:16.0 -0300 +++ mrb-0.3+nmu2/debian/control 2022-04-21 10:33:07.0 -0300 @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Ron Lee -Build-Depends: debhelper (>= 5), perl +Build-Depends: debhelper-compat (= 13), perl Standards-Version: 3.9.8.0 Package: mrb
Bug#965460: cli-common: diff for NMU version 0.10+nmu1
Control: tags 965460 + patch Control: tags 965460 + pending Dear maintainer, I've prepared an NMU for cli-common (versioned as 0.10+nmu1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cli-common-0.10/debian/changelog cli-common-0.10+nmu1/debian/changelog --- cli-common-0.10/debian/changelog 2019-03-11 12:26:56.0 -0300 +++ cli-common-0.10+nmu1/debian/changelog 2022-04-21 09:30:10.0 -0300 @@ -1,3 +1,14 @@ +cli-common (0.10+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965460 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 09:30:10 -0300 + cli-common (0.10) unstable; urgency=medium * The Cambridge BSP ‘Let’s RM the world’ release. diff -Nru cli-common-0.10/debian/compat cli-common-0.10+nmu1/debian/compat --- cli-common-0.10/debian/compat 2019-03-11 12:26:56.0 -0300 +++ cli-common-0.10+nmu1/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 \ Nenhum caractere de nova linha no final do arquivo diff -Nru cli-common-0.10/debian/control cli-common-0.10+nmu1/debian/control --- cli-common-0.10/debian/control 2019-03-11 12:26:56.0 -0300 +++ cli-common-0.10+nmu1/debian/control 2022-04-21 09:30:10.0 -0300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Mono Group Uploaders: Mirco Bauer -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper-compat (= 13) Build-Depends-Indep: debiandoc-sgml, texlive-base-bin, texlive-base,
Bug#999034: squidtaild: diff for NMU version 2.1a6-6.2
Control: tags 999034 + patch Control: tags 999034 + pending Dear maintainer, I've prepared an NMU for squidtaild (versioned as 2.1a6-6.2) and uploaded it to DELAYED/22. Please feel free to tell me if I should delay it longer. Regards. diff -Nru squidtaild-2.1a6/debian/changelog squidtaild-2.1a6/debian/changelog --- squidtaild-2.1a6/debian/changelog 2021-01-05 09:18:12.0 -0300 +++ squidtaild-2.1a6/debian/changelog 2022-04-18 20:56:26.0 -0300 @@ -1,3 +1,11 @@ +squidtaild (2.1a6-6.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999034) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 20:56:26 -0300 + squidtaild (2.1a6-6.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. signature.asc Description: PGP signature
Bug#999018: xvier: diff for NMU version 1.0-7.7
Control: tags 999018 + patch Control: tags 999018 + pending Dear maintainer, I've prepared an NMU for xvier (versioned as 1.0-7.7) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u xvier-1.0/debian/changelog xvier-1.0/debian/changelog --- xvier-1.0/debian/changelog +++ xvier-1.0/debian/changelog @@ -1,3 +1,11 @@ +xvier (1.0-7.7) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999018) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 16:01:05 -0300 + xvier (1.0-7.6) unstable; urgency=medium * Non-maintainer upload.
Bug#965595: info2www: diff for NMU version 1.2.2.9-24.2
Control: tags 965595 + patch Control: tags 965595 + pending Dear maintainer, I've prepared an NMU for info2www (versioned as 1.2.2.9-24.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u info2www-1.2.2.9/debian/changelog info2www-1.2.2.9/debian/changelog --- info2www-1.2.2.9/debian/changelog +++ info2www-1.2.2.9/debian/changelog @@ -1,3 +1,10 @@ +info2www (1.2.2.9-24.2) unstable; urgency=medium + + * Non-maintainer upload. + * Bumped debhelper compat to 7. (Closes: #965595) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 14:10:25 -0300 + info2www (1.2.2.9-24.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team.
Bug#957892: ucarp: diff for NMU version 1.5.2-2.3
Hi, Sorry for my mistake, in the previous email sent by me the delay was 2 days and not 22. I had a problem with my keyboard.
Bug#965705: ltrace: diff for NMU version 0.7.3-6.2
Control: tags 965705 + patch Control: tags 965705 + pending Dear maintainer, I've prepared an NMU for ltrace (versioned as 0.7.3-6.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -Nru ltrace-0.7.3/debian/changelog ltrace-0.7.3/debian/changelog --- ltrace-0.7.3/debian/changelog 2018-08-20 03:09:32.0 -0300 +++ ltrace-0.7.3/debian/changelog 2022-03-30 20:48:13.0 -0300 @@ -1,3 +1,19 @@ +ltrace (0.7.3-6.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965705 + * Dropped CDBS in favor of the debhelper to allow the build system to use +DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs and autotools-dev from +Build-Depends field. + - debian/rules: changed from CDBS to DH. + + -- Guilherme de Paula Xavier Segundo Wed, 30 Mar 2022 20:48:13 -0300 + ltrace (0.7.3-6.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru ltrace-0.7.3/debian/control ltrace-0.7.3/debian/control --- ltrace-0.7.3/debian/control 2018-08-20 03:09:32.0 -0300 +++ ltrace-0.7.3/debian/control 2022-03-30 20:48:13.0 -0300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Juan Cespedes Standards-Version: 3.9.8 -Build-Depends: debhelper-compat (= 13), autotools-dev, libiberty-dev, libelf-dev, libselinux1-dev +Build-Depends: debhelper-compat (= 13), libiberty-dev, libelf-dev, libselinux1-dev Package: ltrace Architecture: alpha amd64 ia64 i386 mips mipsel powerpc powerpcspe ppc64 s390 s390x sparc diff -Nru ltrace-0.7.3/debian/rules ltrace-0.7.3/debian/rules --- ltrace-0.7.3/debian/rules 2018-08-20 03:09:32.0 -0300 +++ ltrace-0.7.3/debian/rules 2022-03-30 20:48:13.0 -0300 @@ -2,3 +2,11 @@ %: dh $@ + +override_dh_auto_configure: + dh_auto_configure -- --with-libunwind=no + +override_dh_install: + dh_install + rm -f debian/ltrace/usr/share/doc/ltrace/COPYING + rm -f debian/ltrace/usr/share/doc/ltrace/INSTALL
Bug#965560: gnome-icon-theme-yasis: diff for NMU version 0.4.2-1.2
Control: tags 965560 + patch Control: tags 965560 + pending Dear maintainer, I've prepared an NMU for gnome-icon-theme-yasis (versioned as 0.4.2-1.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -u gnome-icon-theme-yasis-0.4.2/debian/changelog gnome-icon-theme-yasis-0.4.2/debian/changelog --- gnome-icon-theme-yasis-0.4.2/debian/changelog +++ gnome-icon-theme-yasis-0.4.2/debian/changelog @@ -1,3 +1,19 @@ +gnome-icon-theme-yasis (0.4.2-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965560 + * Dropped CDBS in favor of the debhelper to allow the build system to use +DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs from Build-Depends +field. + - debian/rules: changed from CBDS to DH. + + -- Guilherme de Paula Xavier Segundo Wed, 30 Mar 2022 17:09:43 -0300 + gnome-icon-theme-yasis (0.4.2-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team.
Bug#965434: barada-pam: diff for NMU version 0.5-3.2
Control: tags 965434 + patch Control: tags 965434 + pending Dear maintainer, I've prepared an NMU for barada-pam (versioned as 0.5-3.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru barada-pam-0.5/debian/changelog barada-pam-0.5/debian/changelog --- barada-pam-0.5/debian/changelog 2012-05-31 14:55:25.0 -0300 +++ barada-pam-0.5/debian/changelog 2022-03-29 14:08:27.0 -0300 @@ -1,3 +1,14 @@ +barada-pam (0.5-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965434 + + -- Guilherme de Paula Xavier Segundo Tue, 29 Mar 2022 14:08:27 -0300 + barada-pam (0.5-3.1) unstable; urgency=low * Non-maintainer upload. diff -Nru barada-pam-0.5/debian/compat barada-pam-0.5/debian/compat --- barada-pam-0.5/debian/compat 2012-05-31 14:42:44.0 -0300 +++ barada-pam-0.5/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru barada-pam-0.5/debian/control barada-pam-0.5/debian/control --- barada-pam-0.5/debian/control 2012-05-31 14:42:44.0 -0300 +++ barada-pam-0.5/debian/control 2022-03-29 14:07:31.0 -0300 @@ -1,7 +1,7 @@ Source: barada-pam Priority: extra Maintainer: Andrew Pollock -Build-Depends: debhelper (>= 6.0.7~), autotools-dev, libboost-serialization-dev, libpam-dev, libssl-dev, libboost-filesystem-dev +Build-Depends: debhelper-compat (= 13), autotools-dev, libboost-serialization-dev, libpam-dev, libssl-dev, libboost-filesystem-dev Standards-Version: 3.9.2 Section: libs Homepage: http://barada.sourceforge.net/
Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken
Further investagations : activating pam_ssh.so via pam-auth-update insert the success=0 line in the /etc/pam.d/common-auth file Configuration seems to be declared in /usr/share/pam-configs/ssh-pwd (and I don't see any significative difference with ssh-server and ssh-client) -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken
The steps are : I've quickly reproduce the bug. You can follow these steps : 1. install debian stable in a vm 2. install libpam-ssh 3. upgrade it to debian sid Le 13 janv. à 10:06 Vincent-Xavier JUMEL a écrit > Hello, > > I've quickly reproduce the bug. You can follow these steps : > 1. install debian stable in a vm > 2. upgrade it to debian sid > > The mentionned line appears then in the /etc/pam.d/common-auth file > > Le 13 janv. à 00:18 Steve Langasek a écrit > > Control: tags -1 moreinfo unreproducible > > > > On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote: > > > Package: libpam-runtime > > > Version: 1.4.0-11 > > > Severity: critical > > > Justification: breaks the whole system > > > > > Dear Maintainer, > > > > > >* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all > > >with > > >``` > > >auth[success=0 default=ignore] pam_ssh.so use_first_pass > > >``` > > >* Login then failed > > >* I've modified "success=0" -> "success=1" to get back the login. > > > > So where does this 'success=0' come from? It doesn't come from > > /usr/share/pam-configs/ssh. Installing libpam-ssh in unstable does not > > result in a config containing this line. I'm not sure 'success=0' is valid, > > and if it is, it means 'on success, process the next module' so your bug > > report, by slicing your config file to only show the single pam_ssh line, > > does not show what happens afterward that actually fails the stack. > > > > -- > > Steve Langasek Give me a lever long enough and a Free OS > > Debian Developer to set it on, and I can move the world. > > Ubuntu Developer https://www.debian.org/ > > slanga...@ubuntu.com vor...@debian.org > > > > -- > Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net > > Société Libre, Logiciel Libre http://www.april.org/adherer > Parinux, logiciel libre à Paris : http://www.parinux.org -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken
Hello, I've quickly reproduce the bug. You can follow these steps : 1. install debian stable in a vm 2. upgrade it to debian sid The mentionned line appears then in the /etc/pam.d/common-auth file Le 13 janv. à 00:18 Steve Langasek a écrit > Control: tags -1 moreinfo unreproducible > > On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote: > > Package: libpam-runtime > > Version: 1.4.0-11 > > Severity: critical > > Justification: breaks the whole system > > > Dear Maintainer, > > > >* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all > >with > >``` > >auth[success=0 default=ignore] pam_ssh.so use_first_pass > >``` > >* Login then failed > >* I've modified "success=0" -> "success=1" to get back the login. > > So where does this 'success=0' come from? It doesn't come from > /usr/share/pam-configs/ssh. Installing libpam-ssh in unstable does not > result in a config containing this line. I'm not sure 'success=0' is valid, > and if it is, it means 'on success, process the next module' so your bug > report, by slicing your config file to only show the single pam_ssh line, > does not show what happens afterward that actually fails the stack. > > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer https://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken
Package: libpam-runtime Version: 1.4.0-11 Severity: critical Justification: breaks the whole system Dear Maintainer, * Upgrade to the unstable version of libpam-runtime_1.14.0_11_all with ``` auth[success=0 default=ignore] pam_ssh.so use_first_pass ``` * Login then failed * I've modified "success=0" -> "success=1" to get back the login. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500, 'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), (100, 'buster-backports'), (100, 'bullseye-fasttrack'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/4 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=fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpam-runtime depends on: ii debconf [debconf-2.0] 1.5.79 ii libpam-modules 1.4.0-11 libpam-runtime recommends no packages. libpam-runtime suggests no packages. -- debconf information: libpam-runtime/conflicts: libpam-runtime/override: false * libpam-runtime/profiles: passwdqc, unix, ssh-pwd, tmpdir, systemd libpam-runtime/no_profiles_chosen: libpam-runtime/title: -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1001643: Acknowledgement (sdaps: fails to setup a project with texlive-latex-extra/unstable (2021.2021127-1))
In the comment https://github.com/sdaps/sdaps/issues/ 238#issuecomment-993392198[1], sdaps author and maintener states that the package should not ship anymore these files > Yes. The package should add a dependency to the LaTeX class. And then stop > setting -- build-tex and --install-tex in debian/rules. > This was set earlier (in my own packages too), because TeXLive had a bug and > was missing a file. -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org [1] https://github.com/sdaps/sdaps/issues/238#issuecomment-993392198
Bug#1001643: Acknowledgement (sdaps: fails to setup a project with texlive-latex-extra/unstable (2021.2021127-1))
Bug reported upstream, since there a version mismatch between sdaps-class (1.9.10) and sdaps (1.9.9) I've filled a bug : https://github.com/sdaps/sdaps/issues/238 Meanwhile, Debian could version bump the package to 1.9.9 Le 13 déc. à 18:39 Debian Bug Tracking System a écrit > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1001643: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001643. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Edu Packaging Team > > If you wish to submit further information on this problem, please > send it to 1001...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1001643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001643 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#1001643: sdaps: fails to setup a project with texlive-latex-extra/unstable (2021.2021127-1)
Package: sdaps
Version: 1.9.8-0.1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I've sought to use sdaps instead of auto-multiple-choice, but, while
setting up the project, I've hit a bug :
Steps to reproduce
1. sdaps setup /tmp/projet /usr/share/doc/sdaps/examples/example.tex
Excepted output :
+ a generated pdf file
+ Question on the output
+ see https://sdaps.org/getting-started/setup/
Outcome :
+ questionnaire.pdf doesn't exist
+ sdaps setup fails
+ pdflatex questionnaire.tex fails
The main raison is that /usr/share/sdaps/tex/ and
/usr/share/texlive/texmf-dist/tex/latex/sdaps/ differs (I've attached a
diff).
If I copy files from /usr/share/texlive/texmf-dist/tex/latex/sdaps/ into
/tmp/projet and then run pdlfatex against questionnaire.tex, the
questionnaire.pdf is generated.
This bug may belongs to upstream.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500,
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500,
'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), (100,
'buster-backports'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sdaps depends on:
ii gir1.2-poppler-0.18 20.09.0-3.1
ii libc62.33-1
ii libcairo21.16.0-5
ii libglib2.0-0 2.70.2-1
ii libtiff5 4.3.0-2
ii python3 3.9.8-1
ii python3-cairo1.20.1-3
ii python3-gi 3.42.0-2+b1
ii python3-gi-cairo 3.42.0-2+b1
ii python3-opencv 4.5.4+dfsg-9+b1
ii python3-zbar 0.23.92-4
ii zbar-tools 0.23.92-4
Versions of packages sdaps recommends:
ii gir1.2-gtk-3.0 3.24.30-4
ii python3-pil8.4.0-1
ii python3-reportlab 3.6.2-1
ii texlive2021.20211127-1
ii texlive-latex-extra2021.20211127-1
ii texlive-latex-recommended 2021.20211127-1
ii texlive-plain-generic 2021.20211127-1
ii texlive-science2021.20211127-1
sdaps suggests no packages.
-- no debconf information
--
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net
Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org
--- /usr/share/sdaps/tex/
+++ /usr/share/texlive/texmf-dist/tex/latex/sdaps/
├── file list
│ @@ -1,14 +1,13 @@
│ sdapsarray.sty
│ sdapsbase.sty
│ sdapsclassic.cls
│ sdapscode128.tex
│ sdapslayout.sty
│ sdapspdf.sty
│ -sdapsreport.cls
│ translator-sdaps-dictionary-Brazilian.dict
│ translator-sdaps-dictionary-Dutch.dict
│ translator-sdaps-dictionary-English.dict
│ translator-sdaps-dictionary-Finnish.dict
│ translator-sdaps-dictionary-French.dict
│ translator-sdaps-dictionary-German.dict
│ translator-sdaps-dictionary-Italian.dict
├── stat {}
│ @@ -1,8 +1,8 @@
│
│Size: 4096 Blocks: 8 IO Block: 4096 directory
│ Links: 2
│ Access: (0755/drwxr-xr-x) Uid: (0/root) Gid: (0/root)
│
│ -Modify: 2020-11-24 10:10:36.384018304 +
│ +Modify: 2021-12-01 21:44:37.538686925 +
│ --- /usr/share/sdaps/tex/sdapsarray.sty
├── +++ /usr/share/texlive/texmf-dist/tex/latex/sdaps/sdapsarray.sty
│ @@ -582,19 +582,19 @@
│\dim_set:Nn \l_tmpa_dim { \linewidth - \coffin_wd:N \l_tmpa_coffin -
2\l_sdaps_sdapsarray_colsep_dim }
│\tl_gset:Nx \g_sdaps_array_local_data_new_tl { \dim_use:N \l_tmpa_dim }
│
│% TODO: The \hfil here is a hack to prevent a warning if the vbox is empty.
│% Unfortunately checking for an empty box does not work for some
reason.
│\dim_set:Nn \l_tmpb_dim { \box_ht:N #1 }
│\sdaps_if_rtl:TF {
│ -\hcoffin_set:Nn \l_tmpb_coffin { \hbox_to_wd:nn \l_tmpa_dim { \hfil
\vbox:n { \vbox_unpack_clear:N #1 } } \skip_horizontal:n {
\l_sdaps_sdapsarray_colsep_dim } }
│ +\hcoffin_set:Nn \l_tmpb_coffin { \hbox_to_wd:nn \l_tmpa_dim { \hfil
\vbox:n { \vbox_unpack_drop:N #1 } } \skip_horizontal:n {
\l_sdaps_sdapsarray_colsep_dim } }
│ \tl_set:Nn \l_tmpa_tl { l }
│ \tl_set:Nn \l_tmpb_tl { r }
│} {
│ -\hcoffin_set:Nn \l_tmpb_coffin { \skip_horizontal:n {
\l_sdaps_sdapsarray_colsep_dim } \hbox_to_wd:nn \l_tmpa_dim { \hfil \vbox:n {
\vbox_unpack_clear:N #1 } } }
│ +\hcoffin_set:Nn \l_tmpb_coffin { \skip_horizontal:n {
\l_sdaps_sdapsarray_colsep_dim } \hbox_to_wd:nn \l_tmpa_dim { \hfil \vbox:n {
\vbox_unpack_drop:N #1 } } }
│ \tl_set:Nn \l_tmpa_tl { r }
│ \tl_set:Nn \l_tmpb_tl { l }
│}
│\dim_set:Nn \l_tmpa_dim { \coffin_ht:N \l_tmpb_coffin }
│
│% If the first/last baseline differ then center the vbox, otherwise align
the
│% baseline with the cells
│ ├── stat
Bug#994391: Acknowledgement (vdirsyncer is unusable)
I've upgraded click-threading to 0.5.0 and vdirsyncer works again. Should I fill a bugreport against python3-click-threading ? Le 15 sept. à 14:09 Debian Bug Tracking System a écrit > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 994391: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994391. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Python Team > > If you wish to submit further information on this problem, please > send it to 994...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 994391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994391 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net Société Libre, Logiciel Libre http://www.april.org/adherer Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#994391: vdirsyncer is unusable
Package: vdirsyncer
Version: 0.16.8-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
See the attached console session transcript :
```sh
❯ vdirsyncer -vdebug sync
debug: Using 1 maximal workers.
error: Unknown error occurred: unmatched ')' (, line 1)
error: Use `-vdebug` to see the full traceback.
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line
30, in inner
debug: f(*a, **kw)
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line
145, in sync
debug: with wq.join():
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/utils.py", line
364, in join
debug: with ui_worker.patch_click():
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/click_threading/__init__.py",
line 144, in patch_click
debug: with patch_ui_functions(wrapper):
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/click_threading/monkey.py", line
50, in patch_ui_functions
debug: stub_f = eval('lambda {s}: {n}._real_click_fn({a})'
```
vdirsyncer sync should list the avalaible pairs to synchronise with and
proceed. Instead, an error is thrown.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500,
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500,
'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), (100,
'buster-backports'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vdirsyncer depends on:
ii init-system-helpers1.60
ii python33.9.2-3
ii python3-atomicwrites 1.4.0-2
ii python3-click 7.1.2-1
ii python3-click-log 0.2.1-2
ii python3-click-threading0.4.4-2
ii python3-requests 2.25.1+dfsg-2
ii python3-requests-toolbelt 0.9.1-1
vdirsyncer recommends no packages.
Versions of packages vdirsyncer suggests:
ii python3-requests-oauthlib 1.0.0-1.1
pn vdirsyncer-doc
-- no debconf information
--
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net
Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org
Bug#981678: [Pkg-javascript-devel] Bug#981678: node-babel-preset-env: Depends: node-babel-plugin-syntax-trailing-function-commas (>= 6.22.0) but it is not installable
ROM-RM already asked : #979457 Le 2 février 2021 20:55:41 GMT+01:00, Adrian Bunk a écrit : >Package: node-babel-preset-env >Version: 1.6.0-1 >Severity: serious >Tags: bullseye sid > >The following packages have unmet dependencies: > node-babel-preset-env : Depends: > node-babel-plugin-syntax-trailing-function-commas (>= 6.22.0) but it is not > installable > >-- >Pkg-javascript-devel mailing list >pkg-javascript-de...@alioth-lists.debian.net >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Bug#981474: marked as pending in node-rollup-plugin-terser
Control: tag -1 pending Hello, Bug #981474 in node-rollup-plugin-terser reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-terser/-/commit/e3df2a216bb82378d09c41244b115162f2d6b683 Increase test timeout Closes: #981474 (this message was generated automatically) -- Greetings https://bugs.debian.org/981474
Bug#981474: node-rollup-plugin-terser: test randomly fails due to timeout problems
Package: node-rollup-plugin-terser Version: 7.0.2-4 Severity: serious Tags: ftbfs Justification: Policy 2.1 https://ci.debian.net/packages/n/node-rollup-plugin-terser/testing/amd64/ shows that node-rollup-plugin-terser test randomly fails
Bug#981286: marked as pending in node-jest
Control: tag -1 pending Hello, Bug #981286 in node-jest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jest/-/commit/7296ac45a6aa1cdbc8067219f42d778defdc17ec Set Architecture to "any" Closes: #981286 (this message was generated automatically) -- Greetings https://bugs.debian.org/981286
Bug#981286: [Pkg-javascript-devel] Bug#981286: Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'
Control: reopen -1 Control: reassign -1 jest Le 30/01/2021 à 10:30, Xavier a écrit : > Le 30/01/2021 à 10:06, Xavier a écrit : >> Le 30/01/2021 à 10:02, Xavier a écrit : >>> Control: tags -1 + moreinfo >>> >>> Hi, >>> >>> debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, >>> armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox >>> (and node-iconv is listed in test dependencies). Could someone take a look ? >> >> An idea in node-jest: debian/rules modify jest to insert >> /usr/lib/"$(DEB_HOST_MULTIARCH)"/nodejs in search path so maybe jest >> should be "Architecture: any" instead of "architecture: all" ? > > jest seems not linked to this issue, error is reported by node itself This job shows that problem is not in iconv but in jest-resolve https://salsa.debian.org/js-team/node-mimic-response/-/jobs/1392937
Bug#981286: [Pkg-javascript-devel] Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'
Le 30/01/2021 à 10:06, Xavier a écrit : > Le 30/01/2021 à 10:02, Xavier a écrit : >> Control: tags -1 + moreinfo >> >> Hi, >> >> debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, >> armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox >> (and node-iconv is listed in test dependencies). Could someone take a look ? > > An idea in node-jest: debian/rules modify jest to insert > /usr/lib/"$(DEB_HOST_MULTIARCH)"/nodejs in search path so maybe jest > should be "Architecture: any" instead of "architecture: all" ? jest seems not linked to this issue, error is reported by node itself
Bug#981286: marked as pending in node-mimic-response
Control: tag -1 pending Hello, Bug #981286 in node-mimic-response reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-mimic-response/-/commit/e593e77ccabb1df12628eec65d44aaf7fe0d158d Add workaround for #981286 Closes: #981286 (this message was generated automatically) -- Greetings https://bugs.debian.org/981286
Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'
Le 30/01/2021 à 10:02, Xavier a écrit : > Control: tags -1 + moreinfo > > Hi, > > debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, > armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox > (and node-iconv is listed in test dependencies). Could someone take a look ? An idea in node-jest: debian/rules modify jest to insert /usr/lib/"$(DEB_HOST_MULTIARCH)"/nodejs in search path so maybe jest should be "Architecture: any" instead of "architecture: all" ?
Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'
Control: tags -1 + moreinfo Hi, debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox (and node-iconv is listed in test dependencies). Could someone take a look ?
Bug#970501: marked as pending in dojo
Control: tag -1 pending Hello, Bug #970501 in dojo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/dojo/-/commit/68e6a048b4c4386d0495e7faf11bd46bf0516604 Fix shrinksafe tests with newer rhino by setting JS version Closes: #970501 (this message was generated automatically) -- Greetings https://bugs.debian.org/970501
Bug#981296: [Pkg-javascript-devel] Bug#981296: node-ws: FTBFS: Error: Cannot find module '@types/node'
Control: tags -1 - moreinfo Control: tags -1 + experimental Control: reassign -1 nodejs Control: found -1 14.13.0~dfsg-1 Control: retitle -1 nodejs: missing ts definitions Control: notfound -1 12.20.1~dfsg-3 Le 29/01/2021 à 05:53, Xavier a écrit : > Control: tags -1 + moreinfo > > Le 28/01/2021 à 21:12, Andreas Beckmann a écrit : >> Source: node-ws >> Version: 7.4.1+~cs18.0.6-2 >> Severity: serious >> Tags: ftbfs >> Justification: fails to build from source (but built successfully in the >> past) >> >> Hi, >> >> node-ws/experimental recently started to FTBFS. An earlier build of the >> same version has succeeded, so this new failure is likely due some change >> in a (transitive) build dependency. The version in sid is not affected. >> >> debian/rules binary >> dh binary >>dh_update_autotools_config >>dh_autoreconf >>dh_auto_configure --buildsystem=nodejs >> mkdir node_modules >> ln -s /usr/share/nodejs/debug ./node_modules/ >> mkdir -p ./node_modules/\@types >> ln -s /usr/share/nodejs/\@types/debug ./node_modules/\@types/ >> ln -s /usr/share/nodejs/\@types/mocha ./node_modules/\@types/ >> internal/modules/cjs/loader.js:905 >> throw err; >> ^ >> >> Error: Cannot find module '@types/node' > > Hi, > > this is very strange: @types/node is provided by nodejs itself (since > 12.20), so I don't understand this issue (and I'm unable to reproduce > this issue of course). Sorry, I didn't see that it was related to experimental
Bug#981296: [Pkg-javascript-devel] Bug#981296: node-ws: FTBFS: Error: Cannot find module '@types/node'
Control: tags -1 + moreinfo Le 28/01/2021 à 21:12, Andreas Beckmann a écrit : > Source: node-ws > Version: 7.4.1+~cs18.0.6-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Hi, > > node-ws/experimental recently started to FTBFS. An earlier build of the > same version has succeeded, so this new failure is likely due some change > in a (transitive) build dependency. The version in sid is not affected. > > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > mkdir node_modules > ln -s /usr/share/nodejs/debug ./node_modules/ > mkdir -p ./node_modules/\@types > ln -s /usr/share/nodejs/\@types/debug ./node_modules/\@types/ > ln -s /usr/share/nodejs/\@types/mocha ./node_modules/\@types/ > internal/modules/cjs/loader.js:905 > throw err; > ^ > > Error: Cannot find module '@types/node' Hi, this is very strange: @types/node is provided by nodejs itself (since 12.20), so I don't understand this issue (and I'm unable to reproduce this issue of course).
Bug#980667: marked as pending in node-d3-transition
Control: tag -1 pending Hello, Bug #980667 in node-d3-transition reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-d3-transition/-/commit/206fce3cd0175557afa328422c78e194cb03f8da Disable short-timeout based test Closes: #980667 (this message was generated automatically) -- Greetings https://bugs.debian.org/980667
Bug#981286: marked as pending in node-mimic-response
Control: tag -1 pending Hello, Bug #981286 in node-mimic-response reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-mimic-response/-/commit/ec635c7501b1d4e8ab93aa1719c94c0ffa252a93 Add test dependency to node-iconv Closes: #981286 (this message was generated automatically) -- Greetings https://bugs.debian.org/981286
Bug#980657: eslint: FTBFS: test failed
Hi Jonas, could you take a look at this issue? Seems not a big bug, all tests passed except this one: > not ok 438 formatter:html when passing a single message with illegal characters should return a string in HTML format with 1 issue in 1 file > Check that message is correct: expected 'Unexpected "\' foo.' to equal 'Unexpected foo.' > AssertionError: Check that message is correct: expected 'Unexpected "\' foo.' to equal 'Unexpected foo.' > at checkContentRow (tests/lib/formatters/html.js:60:12) > at Context. (tests/lib/formatters/html.js:528:13) > at callFn (/usr/share/nodejs/mocha/lib/runnable.js:364:21) > at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5) > at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10) > at /usr/share/nodejs/mocha/lib/runner.js:801:12 > at next (/usr/share/nodejs/mocha/lib/runner.js:594:14) > at /usr/share/nodejs/mocha/lib/runner.js:604:7 > at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) > at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:572:5) > at processImmediate (internal/timers.js:461:21)
Bug#980928: npm: Installing any package gives "npm ERR! current.merge is not a function"
Control: tags -1 + pending Le 25/01/2021 à 10:35, Xavier a écrit : > Le 24/01/2021 à 15:52, Jan Kiszka a écrit : >> Package: npm >> Version: 7.4.0+ds-1~bpo10+2 >> Severity: grave >> Justification: renders package unusable >> >> Tried out via, e.g., "npm install serialport" inside a debian:buster-slim >> container. Happens with both "npm node-*" as well only the required >> node-packages takes from backports. > > npm was pushed to buster-backports without trying autopkgtest, which > confirms the bug. There is probably a missing minimal version of one > dependency, but I didn't found which one for now. Found: it requires node-ssri ≥ 8. I just pushed it to buster-backports but since it is new in it, we have to wait a little for its acceptance. Also I just pushed a new npm_7.4.3+ds-2 in Debian unstable with good requirements.
Bug#980928: [Pkg-javascript-devel] Bug#980928: npm: Installing any package gives "npm ERR! current.merge is not a function"
Le 24/01/2021 à 15:52, Jan Kiszka a écrit : > Package: npm > Version: 7.4.0+ds-1~bpo10+2 > Severity: grave > Justification: renders package unusable > > Tried out via, e.g., "npm install serialport" inside a debian:buster-slim > container. Happens with both "npm node-*" as well only the required > node-packages takes from backports. npm was pushed to buster-backports without trying autopkgtest, which confirms the bug. There is probably a missing minimal version of one dependency, but I didn't found which one for now.
Bug#980704: marked as pending in node-is-reference
Control: tag -1 pending Hello, Bug #980704 in node-is-reference reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-is-reference/-/commit/bcfe1a3b0cc85b20bf5432bba33e161a861c17f9 Build dependencies: replace deprecated node-typescript-types by node-types-estree Closes: #980704 (this message was generated automatically) -- Greetings https://bugs.debian.org/980704
Bug#980653: marked as pending in node-jquery-textcomplete
Control: tag -1 pending Hello, Bug #980653 in node-jquery-textcomplete reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jquery-textcomplete/-/commit/490f7a92c94c43974310f0881104db90d8a5fc4a Fix links Closes: #980653 (this message was generated automatically) -- Greetings https://bugs.debian.org/980653
Bug#980654: marked as pending in node-esprima
Control: tag -1 pending Hello, Bug #980654 in node-esprima reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-esprima/-/commit/1f0f028f2b372fc4188eac3959066276d24ad233 Update build dependency: replace deprecated node-typescript-types by node-types-estree (Closes: #980654, #979770) (this message was generated automatically) -- Greetings https://bugs.debian.org/980654
Bug#980652: marked as pending in select2.js
Control: tag -1 pending Hello, Bug #980652 in select2.js reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/select2.js/-/commit/2386b87029e3c158bfac2ae5fa4d823b898be480 Really fix node-select2.js links (Closes: #980652) (this message was generated automatically) -- Greetings https://bugs.debian.org/980652
Bug#980667: node-d3-transition: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Le 20/01/2021 à 21:46, Lucas Nussbaum a écrit : > Source: node-d3-transition > Version: 1.3.2-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20210120 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): >> make[1]: Entering directory '/<>' >> rollup -c >> >> src/index.js → dist/d3-transition.js... >> created dist/d3-transition.js in 143ms >> >> src/index.js → dist/d3-transition.min.js... >> created dist/d3-transition.min.js in 681ms >> make[1]: Leaving directory '/<>' >>dh_auto_test --buildsystem=nodejs >> mkdir -p node_modules >> ln -s ../. node_modules/d3-transition >> /bin/sh -ex debian/tests/pkg-js/test >> + tape test/**/*-test.js it's a timeout problem (very short in this test)
Bug#980679: marked as pending in node-uuid
Control: tag -1 pending Hello, Bug #980679 in node-uuid reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-uuid/-/commit/edf29c8211ecfbe6cabac6e884cc7223f55689f7 Add test dependency to node-json-stringify-safe Closes: #980679 (this message was generated automatically) -- Greetings https://bugs.debian.org/980679
Bug#980652: marked as pending in select2.js
Control: tag -1 pending Hello, Bug #980652 in select2.js reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/select2.js/-/commit/9ae8d25190f1a48a39d48ae2b4bf83edad39c232 Fix node-select2.js links Closes: #980652 (this message was generated automatically) -- Greetings https://bugs.debian.org/980652
Bug#980649: marked as pending in node-rollup-plugin-sourcemaps
Control: tag -1 pending Hello, Bug #980649 in node-rollup-plugin-sourcemaps reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-sourcemaps/-/commit/570cfda5c4b7d699dd0b00e18201214faeddf5da Add build dependency to node-jest-globals (Closes: #980649) * Replace deprecated build dependency to node-typescript-types by node-types-node (Closes: #979781) (this message was generated automatically) -- Greetings https://bugs.debian.org/980649
Bug#980665: marked as pending in twitter-bootstrap4
Control: tag -1 pending Hello, Bug #980665 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/twitter-bootstrap4/-/commit/6c056dcdb273b7c07886a0610461902dab763cd2 Fix build link to @rollup/plugin-babel Closes: #980665 (this message was generated automatically) -- Greetings https://bugs.debian.org/980665
Bug#980672: marked as pending in node-string-decoder
Control: tag -1 pending Hello, Bug #980672 in node-string-decoder reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-string-decoder/-/commit/cf598cc32d865c2025dc64a6b63dfc92f7ea22c2 Update babel7 patch Closes: #980672 (this message was generated automatically) -- Greetings https://bugs.debian.org/980672
Bug#980690: marked as pending in node-readable-stream
Control: tag -1 pending Hello, Bug #980690 in node-readable-stream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-readable-stream/-/commit/13ce86038479eda2493ff111013ed96ce503ef87 Fix test Closes: #980690 (this message was generated automatically) -- Greetings https://bugs.debian.org/980690
Bug#980702: marked as pending in node-nodemailer
Control: tag -1 pending Hello, Bug #980702 in node-nodemailer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-nodemailer/-/commit/787b67c9d639e0ff97fc8dcf754c2f5536a693fb Ignore cookie test Closes: #980702 (this message was generated automatically) -- Greetings https://bugs.debian.org/980702
Bug#980406: [Pkg-javascript-devel] Bug#980406: Bug#980406: This is confirmed as a bug in debian package
Le 19/01/2021 à 15:04, Pirate Praveen a écrit :
>
>
> On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
> wrote:
>> Control: severity -1 serious
>>
>> I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
>> issues. So this is a bug in node-xterm debian build.
>
> Trying to switch to rollup instead of browserify-lite, but tsc itself is
> failing now.
--- a/src/Terminal.ts
+++ b/src/Terminal.ts
@@ -1636,7 +1636,9 @@
*/
public log(text: string, data?: any): void {
if (!this.options.debug) return;
+// @ts-ignore
if (!this._context.console || !this._context.console.log) return;
+// @ts-ignore
this._context.console.log(text, data);
}
@@ -1645,7 +1647,9 @@
*/
public error(text: string, data?: any): void {
if (!this.options.debug) return;
+// @ts-ignore
if (!this._context.console || !this._context.console.error) return;
+// @ts-ignore
this._context.console.error(text, data);
}
--- a/src/renderer/ColorManager.test.ts
+++ b/src/renderer/ColorManager.test.ts
@@ -15,6 +15,7 @@
beforeEach(() => {
dom = new jsdom.JSDOM('');
+// @ts-ignore
window = dom.window;
document = window.document;
(window).HTMLCanvasElement.prototype.getContext = () => ({
Bug#980291: Bug#980294: libjs-jquery-flot: breaking API change
Le 19/01/2021 à 11:11, Jonas Smedegaard a écrit : > Quoting Xavier (2021-01-18 22:16:30) >> Le 18/01/2021 à 18:47, Pirate Praveen a écrit : >>> >>> On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro >>> wrote: >>>> But the fact is that all the other reverse dependencies that used >>>> any plugin now need to be changed accordingly. Otherwise we can >>>> just wait for their chart features to break in subtle ways in the >>>> face of users. >>> >>> Not specific to this bug, but in general, we need to be a lot more >>> careful and slow when updating node modules that also has libjs-* >>> since we don't really have automated tests for them. For, node only >>> parts we have tests most of the time, though not all packages have >>> tests. So we have to be generally slow down on any major version >>> update. >> >> Maintaining an unsupported version means taking the risk to be unable >> to backport a security fix during stable life and LTS (we already have >> many examples). > > Yes, and by letting a package into testing with no RC bugs filed, we > signal to consumers of the package that we take that risk. > > >> _Before freeze_, I prefer having updated libraries, take the risk to >> break sometime something, and patch reverse dependencies (with an >> upstream PR when useful): breaking a little testing/unstable is not a >> drama. > > Breaking a little in testing/unstable is generally expected, yes. > > Except close to freeze, where breakage _is_ a drama! > > The time of freeze is not the time to stop break things. > > The time of freeze is the time nothing can be broken. > > As a consequence, the closer to the freeze the more cautious we need to > be to avoid breaking things. Libraries can break things in consuming > libraries and applications as well, so need more caution, earlier. > >> But we are a team, if the team prefer to take the security risk, >> then OK, I'll stop updating any libjs-* package (and stop tearing my >> hair to patch obsolete packages when a CVE exists). > > Debian is making a release. Not the JavaScript team, and not you. > > Debian care *both* about security and breakage. > > Close to freeze, we shall not stop doing security assessments. Instead, > we shall involve the release team and the security team more in our > security assessments, by sharing release-concerning bugs with them, and > have them help decide how to deal with the dilemma of risking breakage > or tolerating security risks. > > First step in that is to _continue_ to file RC bugs. Then contact the > release team suggesting them how those bugs can be solved by them making > freeze exceptions, or alternatively having them make an exception for > that specific RC bug. > >> Anyway, we entered freeze, it's not time to update anything not >> needed, > > Not true: When entered freeze any larger update needs explicit accept > from the release team. Notes: * I'm not the author of the breakage, I did no source update on this package (just fixed node-uglify problem) * The breakage came before soft-freeze * I just tried to fix RC bug since nobody took care of it Bye
Bug#980291: marked as pending in flot
Control: tag -1 pending Hello, Bug #980291 in flot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/flot/-/commit/58ebdf9900c4545b73cd07c46854a670935c2c02 Fix breaking API change Closes: #980291 (this message was generated automatically) -- Greetings https://bugs.debian.org/980291
Bug#980291: [Pkg-javascript-devel] Bug#980291: Bug#980291: Bug#980294: libjs-jquery-flot: breaking API change
Le 18/01/2021 à 18:47, Pirate Praveen a écrit : > > On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro > wrote: >> But the fact is that all the other reverse dependencies that used any >> plugin now need to be changed accordingly. Otherwise we can just wait >> for their chart features to break in subtle ways in the face of users. > > Not specific to this bug, but in general, we need to be a lot more > careful and slow when updating node modules that also has libjs-* since > we don't really have automated tests for them. For, node only parts we > have tests most of the time, though not all packages have tests. So we > have to be generally slow down on any major version update. Maintaining an unsupported version means taking the risk to be unable to backport a security fix during stable life and LTS (we already have many examples). _Before freeze_, I prefer having updated libraries, take the risk to break sometime something, and patch reverse dependencies (with an upstream PR when useful): breaking a little testing/unstable is not a drama. But we are a team, if the team prefer to take the security risk, then OK, I'll stop updating any libjs-* package (and stop tearing my hair to patch obsolete packages when a CVE exists). For the rhythm, most of libjs/node-* packages were strongly outdated in Buster, the sustained pace of 2020 only partially made up for the accumulated delay and the related technical debt. Anyway, we entered freeze, it's not time to update anything not needed, except minor and tested updates, but I'm happy to have updated a lot of packages before freeze even if it has broken unstable sometime. I feel the [1] dashboard better now than before Buster release. [1]: https://udd.debian.org/dmd/?email1=pkg-javascript-devel%40lists.alioth.debian.org=html
Bug#980291: marked as pending in flot
Control: tag -1 pending Hello, Bug #980291 in flot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/flot/-/commit/05807a09b5ca7d4155f3adad8af795f2b06af77c Fix typo in previous patch Closes: #980291 (this message was generated automatically) -- Greetings https://bugs.debian.org/980291
Bug#980291: marked as pending in flot
Control: tag -1 pending Hello, Bug #980291 in flot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/flot/-/commit/b5108692905fb31a8639474d22bdd5a109aefbc6 Provide minified files and related maps Closes: #980291 (this message was generated automatically) -- Greetings https://bugs.debian.org/980291
Bug#980195: marked as pending in pkg-js-tools
Control: tag -1 pending Hello, Bug #980195 in pkg-js-tools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/pkg-js-tools/-/commit/d2739c95b6b1439c997dc3f657ff11c87ca21acd autopkgtest: fix regexp that parse debian/nodejs/ext* Closes: #980195 (this message was generated automatically) -- Greetings https://bugs.debian.org/980195
Bug#980195: ts-node: autopkgtest regression in testing: Cannot find name 'process'
Control: reassign -1 pkg-js-autopkgtest Control: affects -1 ts-node Le 15/01/2021 à 22:14, Paul Gevers a écrit : > Source: ts-node > Version: 9.1.1-4 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a very recent change in testing the autopkgtest of your package > started to fail. I copied some of the output at the bottom of this > report. 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 This is due to a Perl change: Now: $ cat debian/nodejs/extcopies|perl -pe 's/\s+.*$//' axiossemver@types/node@types/react Before: $ cat debian/nodejs/extcopies|perl -pe 's/\s+.*$//' axios semver @types/node @types/react I'm going to fix pkg-js-autopkgtest
Bug#980054: marked as pending in jquery-goodies
Control: tag -1 pending Hello, Bug #980054 in jquery-goodies reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/jquery-goodies/-/commit/8cd4da337babeb34eb840ccda1099ed5c2b2bc37 No more install libjs-jquery-mousewheel, provided by node-jquery-mousewheel Closes: #980054 (this message was generated automatically) -- Greetings https://bugs.debian.org/980054
Bug#980012: FTBFS: TypeError: Cannot read property 'register' of undefined
Package: coffeescript Version: 1.12.8~dfsg-4 Severity: serious coffeescript build seems broken. Logs: dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building coffeescript using existing ./coffeescript_1.12.8~dfsg.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building coffeescript in coffeescript_1.12.8~dfsg-5.debian.tar.xz dpkg-source: info: building coffeescript in coffeescript_1.12.8~dfsg-5.dsc debian/rules binary CDBS WARNING: copyright-check disabled - licensecheck is missing. test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p "." Scanning upstream source for new/changed copyright notices... set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive --copyright --deb-fmt --ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 -- * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints /bin/sh: 1: /usr/bin/licensecheck: not found 0 combinations of copyright and licensing found. No new copyright notices found - assuming no news is good news... touch debian/stamp-copyright-check mkdir -p "debian/upstream-cruft" cp -a "lib" "debian/upstream-cruft/lib"; touch debian/stamp-upstream-cruft mkdir -p docs/v1/browser-compiler chmod +x bin/cake bin/cake build bin/cake build bin/cake build:browser bin/cake test (node:2439631) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (node:2439631) [DEP0124] DeprecationWarning: REPLServer.rli is deprecated passed 856 tests in 1.66 seconds bin/cake test:browser /<>/Cakefile:450 CoffeeScript.register(); ^ TypeError: Cannot read property 'register' of undefined at runTests (/<>/Cakefile:450:18) at Object.action (/<>/Cakefile:562:19) at invoke (/<>/lib/coffee-script/cake.js:44:26) at Object.exports.run (/<>/lib/coffee-script/cake.js:70:20) at Object. (/<>/bin/cake:15:42) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) at internal/main/run_main_module.js:17:47
Bug#980009: marked as pending in node-js-yaml
Control: tag -1 pending Hello, Bug #980009 in node-js-yaml reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-js-yaml/-/commit/2b0a3b045dfd69c8eac3b038b643ca5433f4bd4d Increase test timeout Closes: #980009 (this message was generated automatically) -- Greetings https://bugs.debian.org/980009
Bug#979874: node-cross-spawn-async: Keep out of testing
Package: node-cross-spawn-async Version: 2.2.5-4 Severity: serious As node-cross-spawn, node-cross-spawn-async shoul d be kept out of Bullseye
Bug#975794: marked as pending in node-agent-base
Control: tag -1 pending Hello, Bug #975794 in node-agent-base reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-agent-base/-/commit/5a3c1d10828ca88ca5c275a65b8be87b81e38ed0 Fix typescript ≥ 4.1 regression Closes: #975794 (this message was generated automatically) -- Greetings https://bugs.debian.org/975794
Bug#956423: Bullseye freeze is coming soon
Hi all, Bullseye freeze is coming and we still have problems with node-request removal. In particular, node-jsdom is not easy to patch. I tried a patch (not approved by upstream) but it needs a lot of unavailable Node.js modules. Looking at the following list, it seems that only node-jsdom is important to update, others have no important reverse dependencies AFAIK, haven't they? List of problems (from dak): # Broken Depends: node-jsdom: node-jsdom node-jsonld: node-jsonld node-matrix-js-sdk: node-matrix-js-sdk node-millstone: node-millstone node-yarnpkg: yarnpkg # Broken Build-Depends: node-client-sessions: node-request node-jsdom: node-request node-matrix-js-sdk: node-request node-opencv: node-request node-request-promise-core: node-request node-yarnpkg: node-request (>= 2.88.1-5~)
Bug#978390: marked as pending in node-rollup-plugin-typescript
Control: tag -1 pending Hello, Bug #978390 in node-rollup-plugin-typescript reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-typescript/-/commit/98cd5110adaa35bade37af0939c2db3977142bc8 Fix regression due to typescript ≥ 4.1 Closes: #978390 (this message was generated automatically) -- Greetings https://bugs.debian.org/978390
Bug#979664: marked as pending in apache2
Control: tag -1 pending Hello, Bug #979664 in apache2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/apache-team/apache2/-/commit/ac6936d8a7058b01a147475a5f004c8de6388045 Disable temporary 3 subtests Closes: #979664 (this message was generated automatically) -- Greetings https://bugs.debian.org/979664
Bug#979693: [Pkg-javascript-devel] Bug#979693: typescript-types_20210110-1_sourceonly.changes ACCEPTED into unstable
Le 10/01/2021 à 11:05, Jonas Smedegaard a écrit : > Quoting Debian FTP Masters (2021-01-10 10:49:04) >> Changes: >> typescript-types (20210110-1) unstable; urgency=medium >> . >>* Team upload >>* Remove @types/node, provided by node 12.20.1~dfsg-1 (Closes: #979693) > > I am not convinced that above closes the bug: I think a Breaks is needed > in the nodejs package. > > - Jonas You were right but it took more time to build nodejs than typescript-types
Bug#979693: marked as pending in typescript-types
Control: tag -1 pending Hello, Bug #979693 in typescript-types reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/typescript-types/-/commit/0417c65b6d5e265ed982e2ae676a1b195495128d Remove @types/node, provided by node 12.20.1~dfsg-1 Closes: #979693 (this message was generated automatically) -- Greetings https://bugs.debian.org/979693
Bug#979693: marked as pending in nodejs
Control: tag -1 pending Hello, Bug #979693 in nodejs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/nodejs/-/commit/f66444eda7c14af092a686b6f13dc9c3acb74851 Indicate that it breaks node-typescript-types < 20210110~ Closes: #979693 (this message was generated automatically) -- Greetings https://bugs.debian.org/979693
Bug#979475: node-gyp-build: Keep out of testing
Package: node-gyp-build Severity: serious Justification: Policy 2.1 node-gyp-rebuild replaces `node-gyp rebuild` using pre-compiled binaries. This is useless in Debian. I did an error when packaging it, this package should be removed from Debian archive, shouldn't it?
Bug#979409: marked as pending in node-source-map
Control: tag -1 pending Hello, Bug #979409 in node-source-map reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-source-map/-/commit/5736ba840b945c5c83311c894a003b8b42510888 Fix link between node-source-map and libjs-source-map Closes: #979409 (this message was generated automatically) -- Greetings https://bugs.debian.org/979409
Bug#977960: marked as pending in node-jquery
Control: tag -1 pending Hello, Bug #977960 in node-jquery reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jquery/-/commit/00b1d48b8af231df2e207574aeea086e52ec2dcb Fix maintscript, thanks to Mattias Ellert Closes: #977960 (this message was generated automatically) -- Greetings https://bugs.debian.org/977960
Bug#979174: node-express-generator: Incompatible with current node-commander and node-mkdirp
Package: node-express-generator Version: 4.0.0-2 Severity: grave Tags: sid, ftbfs Justification: renders package unusable node-express-generator isn't compatible with current node-commander, neither node-mkdirp. As it has no reverse dependency, I suggest to remove it from Debian
Bug#978341: marked as pending in node-babel
Control: tag -1 pending Hello, Bug #978341 in node-babel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-babel/-/commit/ef792ae3156ad698fba901f8adfc834f3c9faa92 Build typescript definitions Closes: #978341 (this message was generated automatically) -- Greetings https://bugs.debian.org/978341
Bug#977960: [Pkg-javascript-devel] Bug#977960: dangling /usr/share/javascript/jquery/jquery.js symlink
Le 27/12/2020 à 19:04, Thorsten Glaser a écrit : > Package: node-jquery > Version: 3.5.1+dfsg+~3.5.5-3 > Followup-For: Bug #977960 > X-Debbugs-Cc: t...@mirbsd.de > > Even for the latest versions of these packages, adequate reports: > > node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js -> > ../../nodejs/jquery/dist/jquery.js > node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.min.js -> > ../../nodejs/jquery/dist/jquery.min.js > node-jquery: broken-symlink > /usr/share/nodejs/jquery/dist/jquery.min.js.brotli -> > ../../nodejs/jquery/dist/jquery.min.js.brotli > node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.min.js.gz -> > ../../nodejs/jquery/dist/jquery.min.js.gz > node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.min.map -> > ../../nodejs/jquery/dist/jquery.min.map > node-jquery: broken-symlink > /usr/share/nodejs/jquery/dist/jquery.min.map.brotli -> > ../../nodejs/jquery/dist/jquery.min.map.brotli > node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.min.map.gz > -> ../../nodejs/jquery/dist/jquery.min.map.gz > libjs-jquery: broken-symlink /usr/share/javascript/jquery/jquery.js -> > ../../nodejs/jquery/dist/jquery.js > libjs-jquery: broken-symlink /usr/share/javascript/jquery/jquery.min.js -> > ../../nodejs/jquery/dist/jquery.min.js > libjs-jquery: broken-symlink > /usr/share/javascript/jquery/jquery.min.js.brotli -> > ../../nodejs/jquery/dist/jquery.min.js.brotli > libjs-jquery: broken-symlink /usr/share/javascript/jquery/jquery.min.js.gz -> > ../../nodejs/jquery/dist/jquery.min.js.gz > libjs-jquery: broken-symlink /usr/share/javascript/jquery/jquery.min.map -> > ../../nodejs/jquery/dist/jquery.min.map > libjs-jquery: broken-symlink > /usr/share/javascript/jquery/jquery.min.map.brotli -> > ../../nodejs/jquery/dist/jquery.min.map.brotli > libjs-jquery: broken-symlink /usr/share/javascript/jquery/jquery.min.map.gz > -> ../../nodejs/jquery/dist/jquery.min.map.gz > > And indeed, these are circular: > > $ ls -la /usr/share/nodejs/jquery/dist /usr/share/javascript/jquery > lrwxrwxrwx 1 root root 29 May 6 2020 /usr/share/javascript/jquery -> > /usr/share/nodejs/jquery/dist > > /usr/share/nodejs/jquery/dist: > total 8 > drwxr-xr-x 2 root root 4096 Dec 27 18:57 . > drwxr-xr-x 3 root root 4096 Dec 27 18:57 .. > lrwxrwxrwx 1 root root 34 Dec 24 14:20 jquery.js -> > ../../nodejs/jquery/dist/jquery.js > lrwxrwxrwx 1 root root 38 Dec 24 14:20 jquery.min.js -> > ../../nodejs/jquery/dist/jquery.min.js > lrwxrwxrwx 1 root root 45 Dec 24 14:20 jquery.min.js.brotli -> > ../../nodejs/jquery/dist/jquery.min.js.brotli > lrwxrwxrwx 1 root root 41 Dec 24 14:20 jquery.min.js.gz -> > ../../nodejs/jquery/dist/jquery.min.js.gz > lrwxrwxrwx 1 root root 39 Dec 24 14:20 jquery.min.map -> > ../../nodejs/jquery/dist/jquery.min.map > lrwxrwxrwx 1 root root 46 Dec 24 14:20 jquery.min.map.brotli -> > ../../nodejs/jquery/dist/jquery.min.map.brotli > lrwxrwxrwx 1 root root 42 Dec 24 14:20 jquery.min.map.gz -> > ../../nodejs/jquery/dist/jquery.min.map.gz I'm still unable to reproduce this and didn't receive help from anyone, even if I'm not the author of this breakage. Anyway, I removed all links from libjs-jquery (3.5.1+dfsg+~3.5.5-4). If you consider that the bug is fixed, please close it, else let's wait for someone smarter than me to step in.
Bug#978341: [Pkg-javascript-devel] Bug#978341: Bug#978341: node-recast: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14, 11): error TS7016: Could not find a declaration file for module
Control: reassign -1 node-babel7 Control: reassign 978384 node-babel Control: forcemerge -1 978384 Control: retitle -1 @babel/types: missing lib/index.d.ts Control: affects -1 node-recast Control: affects -1 node-ast-typpes Le 27/12/2020 à 12:07, Xavier a écrit : > Le 26/12/2020 à 23:05, Lucas Nussbaum a écrit : >> Source: node-recast >> Version: 0.20.4-1 >> Severity: serious >> Justification: FTBFS on amd64 >> Tags: bullseye sid ftbfs >> Usertags: ftbfs-20201226 ftbfs-bullseye >> >> Hi, >> >> During a rebuild of all packages in sid, your package failed to build >> on amd64. >> >> Relevant part (hopefully): >>> make[1]: Entering directory '/<>' >>> mkdir -p node_modules/@types >>> for toto in esprima estree mocha node; do \ >>> cp -R /usr/share/nodejs/@types/$toto node_modules/@types/; \ >>> done >>> for toto in ast-types @babel esprima source-map tslib; do \ >>> cp -R /usr/share/nodejs/$toto node_modules/; \ >>> done >>> tsc >>> node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: >>> Could not find a declaration file for module '@babel/types'. >>> '/<>/node_modules/@babel/types/lib/index.js' implicitly has an >>> 'any' type. >>> Try `npm i --save-dev @types/babel__types` if it exists or add a new >>> declaration (.d.ts) file containing `declare module '@babel/types';` >>> node_modules/@babel/parser/typings/babel-parser.d.ts(22,11): error TS7016: >>> Could not find a declaration file for module '@babel/types'. >>> '/<>/node_modules/@babel/types/lib/index.js' implicitly has an >>> 'any' type. >>> Try `npm i --save-dev @types/babel__types` if it exists or add a new >>> declaration (.d.ts) file containing `declare module '@babel/types';` > > I fixed part of the problem using dh-sequence-nodejs, but it seems to > have a problem with @babel/types typescript definitions import but I > don't find where. Problem is in @babel/types: typescript definitions are missing
Bug#978341: [Pkg-javascript-devel] Bug#978341: node-recast: FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14, 11): error TS7016: Could not find a declaration file for module '@babel/type
Le 26/12/2020 à 23:05, Lucas Nussbaum a écrit : > Source: node-recast > Version: 0.20.4-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201226 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): >> make[1]: Entering directory '/<>' >> mkdir -p node_modules/@types >> for toto in esprima estree mocha node; do \ >> cp -R /usr/share/nodejs/@types/$toto node_modules/@types/; \ >> done >> for toto in ast-types @babel esprima source-map tslib; do \ >> cp -R /usr/share/nodejs/$toto node_modules/; \ >> done >> tsc >> node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016: >> Could not find a declaration file for module '@babel/types'. >> '/<>/node_modules/@babel/types/lib/index.js' implicitly has an >> 'any' type. >> Try `npm i --save-dev @types/babel__types` if it exists or add a new >> declaration (.d.ts) file containing `declare module '@babel/types';` >> node_modules/@babel/parser/typings/babel-parser.d.ts(22,11): error TS7016: >> Could not find a declaration file for module '@babel/types'. >> '/<>/node_modules/@babel/types/lib/index.js' implicitly has an >> 'any' type. >> Try `npm i --save-dev @types/babel__types` if it exists or add a new >> declaration (.d.ts) file containing `declare module '@babel/types';` I fixed part of the problem using dh-sequence-nodejs, but it seems to have a problem with @babel/types typescript definitions import but I don't find where.
Bug#978250: marked as pending in node-d3-queue
Control: tag -1 pending Hello, Bug #978250 in node-d3-queue reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-d3-queue/-/commit/49245aa882f2ba8d78be83a0fb94793a2cf80909 Remove unsupported uglifyjs option --preamble Closes: #978250 (this message was generated automatically) -- Greetings https://bugs.debian.org/978250
Bug#978309: [Pkg-javascript-devel] Bug#978309: node-cross-spawn-async: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Le 26/12/2020 à 22:54, Lucas Nussbaum a écrit : > Source: node-cross-spawn-async > Version: 2.2.5-4 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201226 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Hi, ROM-RM asked for this useless package.
Bug#978363: marked as pending in node-debug-fabulous
Control: tag -1 pending Hello, Bug #978363 in node-debug-fabulous reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-debug-fabulous/-/commit/58028c18458eaadbbcb9f60f44319613bbd1054a Add fix for node-hook-std ≥ 2 Closes: #978363 (this message was generated automatically) -- Greetings https://bugs.debian.org/978363
Bug#978303: marked as pending in node-clone-buffer
Control: tag -1 pending Hello, Bug #978303 in node-clone-buffer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-clone-buffer/-/commit/3cc051a2cb671400e0be67ce51ba4c72e4a8c9e6 Add test dependency to node-has Closes: #978303 (this message was generated automatically) -- Greetings https://bugs.debian.org/978303
Bug#978318: marked as pending in node-estree-walker
Control: tag -1 pending Hello, Bug #978318 in node-estree-walker reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-estree-walker/-/commit/32f48c7e9d5c5f6787eb07b56a61980e1fe973fe Fix test and autopkgtest Closes: #978318 (this message was generated automatically) -- Greetings https://bugs.debian.org/978318
Bug#978294: marked as pending in node-fast-levenshtein
Control: tag -1 pending Hello, Bug #978294 in node-fast-levenshtein reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-fast-levenshtein/-/commit/e9db1227f90ec7d4ae7f0adccfb18f679dd1c64a Add build dependency to node-lodash Closes: #978294 (this message was generated automatically) -- Greetings https://bugs.debian.org/978294
Bug#978300: marked as pending in node-fastcgi
Control: tag -1 pending Hello, Bug #978300 in node-fastcgi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-fastcgi/-/commit/a1f8b9b20bb72077070357e98d279790909c592e Add build dependency to node-lodash Closes: #978300 (this message was generated automatically) -- Greetings https://bugs.debian.org/978300
Bug#978298: marked as pending in node-glogg
Control: tag -1 pending Hello, Bug #978298 in node-glogg reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-glogg/-/commit/8296d7b61f524a2ba6ba8009cf32e64a5b0f18ee Add build dependency to node-has Closes: #978298 (this message was generated automatically) -- Greetings https://bugs.debian.org/978298
Bug#978319: marked as pending in node-gulp
Control: tag -1 pending Hello, Bug #978319 in node-gulp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-gulp/-/commit/e879be410b062cf33deb3f95b5c3af1dbe00529b Add missing build dependency to node-mkdirp Closes: #978319 (this message was generated automatically) -- Greetings https://bugs.debian.org/978319
Bug#978301: marked as pending in node-js-yaml
Control: tag -1 pending Hello, Bug #978301 in node-js-yaml reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-js-yaml/-/commit/d7145feeac137698d915e928f7cbb28ac418a8c0 Fix test for mocha 8 Closes: #978301 (this message was generated automatically) -- Greetings https://bugs.debian.org/978301
Bug#978317: marked as pending in node-json-stringify-safe
Control: tag -1 pending Hello, Bug #978317 in node-json-stringify-safe reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-json-stringify-safe/-/commit/5a68397c6ff05102e943ce625ca53411ea6bc90a Fix test for recent mocha Closes: #978317 (this message was generated automatically) -- Greetings https://bugs.debian.org/978317
Bug#978299: marked as pending in node-lie
Control: tag -1 pending Hello, Bug #978299 in node-lie reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-lie/-/commit/16dac0dd2a2e2e03868c07110704e10484788581 Fix test for mocha ≥ 8 Closes: #978299 (this message was generated automatically) -- Greetings https://bugs.debian.org/978299
Bug#978313: marked as pending in node-postgres
Control: tag -1 pending Hello, Bug #978313 in node-postgres reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-postgres/-/commit/c6f5ef03d03af87a048646d526c7c2277918dae0 Fix buffer-writer test for mocha ≥ 7 Closes: #978313 (this message was generated automatically) -- Greetings https://bugs.debian.org/978313
Bug#978321: marked as pending in node-vinyl
Control: tag -1 pending Hello, Bug #978321 in node-vinyl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-vinyl/-/commit/db78729353f33be1047854997b16151913c74d3c Add build dependency to node-has Closes: #978321 (this message was generated automatically) -- Greetings https://bugs.debian.org/978321
Bug#978373: marked as pending in node-deep-eql
Control: tag -1 pending Hello, Bug #978373 in node-deep-eql reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-deep-eql/-/commit/a1b7bfbcd9047a4d22a90a8781409649be2b29e6 Fix build Closes: #978373 (this message was generated automatically) -- Greetings https://bugs.debian.org/978373
Bug#978333: marked as pending in node-filesize
Control: tag -1 pending Hello, Bug #978333 in node-filesize reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-filesize/-/commit/d90d7b5ed8927857c144c5df96239aa3344cca40 Add build dependency to node-babel7 Closes: #978333 (this message was generated automatically) -- Greetings https://bugs.debian.org/978333
