Bug#965327: Lower severity of bash-completion-with-hashbang
Hi Vincent, > >> the shebang is harmless and I won't > >> patch or other upstream about a harmless shebang. > > > > As explained in this MR [2], we consider the hashbang an error. The > > snippets are not meant to be executed. The upstream for > > 'bash-completion' also does not use them. > > > > [2] https://salsa.debian.org/lintian/lintian/-/merge_requests/292 > > Again, I won't maintain a patch for such an "error". Hmm, I would agree this should not be a "W:" level tag, and could easily be convinced it should not even be "I:" either given that I wouldn't patch it out either or bother upstream with it. This might be another one of my controversial opinions too, but I find modelines as a solution beyond ugly. :) > Lintian is a very useful tool, but too many stuff is a warning while > this is a matter of opinion. I have given up on the "info" level > since a long time for similar reasons. I would like not to give up on > the "warning" level. (It is a shame to read you have given up on "I:" and it would be nice if Lintian earned back your trust. Now that it has a slightly simpler system of classification, could you file a wishlist bugs against what you feel are, or felt were, the worst offenders?) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#965378: distcc-pump fails to start due to incorrect include_server path
Package: distcc-pump Version: 3.3.2-10 Severity: important Dear Maintainer, The distcc-pump script fails to start properly due to not being able to find the include_server. More specifically, the hardcoded path to the server in /usr/bin/distcc-pump is: include_server='/usr/lib/distcc-pump/include_server/include_server.py' However, the distcc-pump package installs include_server.py to the following location: /usr/lib/distcc-pump/lib/python3.7/site-packages/include_server/include_server.py The result is the following error when starting distcc-pump: $ DISTCC_HOSTS="localhost,lzo,cpp" distcc-pump echo foo __Using distcc-pump from /usr/bin __Using 1 distcc server in pump mode /usr/bin/python3: can't open file '/usr/lib/distcc-pump/include_server/include_server.py': [Errno 2] No such file or directory __Expected a socket at '/tmp/distcc-pump.n4LiDO/socket' __Could not start distcc-pump include server Fixing the path in /usr/lib/distcc-pump resolves the issue: $ sed 's#pump/include_server#pump/lib/python3.7/site-packages/include_server#' \ /usr/bin/distcc-pump > /tmp/pump-fixed $ env DISTCC_LOCATION=/usr/bin DISTCC_HOSTS="localhost,lzo,cpp" \ sh /tmp/pump-fixed echo foo __Using distcc-pump from /usr/bin __Using 1 distcc server in pump mode foo __Shutting down distcc-pump include server This has been reported already to Ubuntu here: https://bugs.launchpad.net/ubuntu/+source/distcc/+bug/1835493 However, I thought it would be good to report here as well. Thank you for your time and help. If I can provide any other information that would be of use, please let me know. Best, Alex -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages distcc-pump depends on: ii distcc 3.3.2-10 ii libc62.28-10 ii python3 3.7.3-1 distcc-pump recommends no packages. distcc-pump suggests no packages. -- no debconf information
Bug#964793: qemu-system-x86 crash
Control: tag -1 + confirmed upstream I'm working on this. Reproduced, found the "messenger", now trying to find the root case. /mjt
Bug#954272: slurmd: SLURM not working with OpenMPI
On 20/07/2020 14:52, Lars Veldscholte wrote: Hi, I believe I have found a solution. I must confess that I still don't fully understand the difference between the various PMI APIs, and which ones are supported by OpenMPI, but I found that the recommended way is to use PMIx. However, PMIx was not working on my system even though libpmix2 is installed: # srun --mpi pmix ./a.out srun: error: (null) [0] /mpi_pmix.c:133 [init] mpi/pmix: ERROR: pmi/pmix: can not load PMIx library srun: error: Couldn't load specified plugin name for mpi/pmix: Plugin init() callback failed srun: error: cannot create mpi context for mpi/pmix srun: error: invalid MPI type 'pmix', --mpi=list for acceptable types Running `strace srun --mpi=pmix ./a.out` revealed that SLURM is looking for the pmix library at `/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so`, which does not exist, only `libpmix.so.2` exists. Which code is trying to load libpmix.so ? The compiled code should be loading libpmix.so.2 directly; the libpmix.so should only be needed at build-time. Perhaps the problem is that libpmix-dev is not installed at compile time. I can add it as a Dependency of libopenmpi-dev. Installing the package `libpmix-dev` installs this library (it symlinks it to the same file `libpmix.so.2` is symlinked to). Now, `srun --mpi=pmix ./a.out` is working! I'm not 100% sure, but I think that the package `libpmix2` should also install the file `libpmix.so`. The dev package shouldn't be required for that, right? Lars Regards Alastair -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.
Bug#965377: buster-pu: package libinput/1.12.6-2+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi Stable Release Managers,
libinput in buster is affected by the bug #952700 (fixed in unstable
already back when the new version was uploaded) and can be described
as:
libinput has an issue which was reported upstream in
https://gitlab.freedesktop.org/libinput/libinput/issues/291 and makes
external lenovo keyboard trackpoint and mouse buttons erroneously
suspended in yoga tablet mode. The pointing stick gets disabled on
tablet mode switch.
I was able to test the respective bug in the given combination.
Attached is the proposed debdiff for this update.
Regards,
Salvatore
diff -Nru libinput-1.12.6/debian/changelog libinput-1.12.6/debian/changelog
--- libinput-1.12.6/debian/changelog2019-03-31 03:42:45.0 +0200
+++ libinput-1.12.6/debian/changelog2020-02-27 21:27:20.0 +0100
@@ -1,3 +1,10 @@
+libinput (1.12.6-2+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * quirks: add trackpoint integration attribute (Closes: #952700)
+
+ -- Salvatore Bonaccorso Thu, 27 Feb 2020 21:27:20 +0100
+
libinput (1.12.6-2) unstable; urgency=medium
* Ship /usr/share/libinput in the udeb, since that's now needed by the
diff -Nru
libinput-1.12.6/debian/patches/quirks-add-trackpoint-integration-attribute.patch
libinput-1.12.6/debian/patches/quirks-add-trackpoint-integration-attribute.patch
---
libinput-1.12.6/debian/patches/quirks-add-trackpoint-integration-attribute.patch
1970-01-01 01:00:00.0 +0100
+++
libinput-1.12.6/debian/patches/quirks-add-trackpoint-integration-attribute.patch
2020-02-27 21:27:20.0 +0100
@@ -0,0 +1,224 @@
+From: Peter Hutterer
+Date: Tue, 28 May 2019 09:54:27 +1000
+Subject: quirks: add trackpoint integration attribute
+Origin:
https://gitlab.freedesktop.org/libinput/libinput/commit/6e60f8fb19cad03747b877dfcf587d9684dfc6f7
+Bug: https://gitlab.freedesktop.org/libinput/libinput/issues/291
+Bug-Debian: https://bugs.debian.org/952700
+
+Some versions [1] of the Lenovo ThinkPad Compact USB Keyboard with TrackPoint
USB
+have the pointing stick on an event node that has keys but is not a regular
+keyboard. Thus the stick falls through the cracks and gets disabled on tablet
+mode switch. Instead of adding more hacks let's do this properly: tag the
+pointing stick as external and have the code in place to deal with that.
+
+[1] This may be caused by recent kernel changes
+
+Fixes #291
+
+Signed-off-by: Peter Hutterer
+(cherry picked from commit 8dfe8c68eb9bde9eecc7de5665903d258df42272)
+---
+ doc/user/device-quirks.rst | 3 +++
+ quirks/50-system-lenovo.quirks | 9 -
+ src/evdev-fallback.c | 14 +-
+ src/evdev.c| 32
+ src/quirks.c | 8
+ src/quirks.h | 1 +
+ test/test-quirks.c | 34 ++
+ 7 files changed, 91 insertions(+), 10 deletions(-)
+
+--- a/doc/user/device-quirks.rst
b/doc/user/device-quirks.rst
+@@ -181,3 +181,6 @@ AttrEventCodeDisable=EV_ABS;BTN_STYLUS;E
+ Disables the evdev event type/code tuples on the device. Entries may be
+ a named event type, or a named event code, or a named event type with a
+ hexadecimal event code, separated by a single colon.
++AttrPointingStickIntegration=internal|external
++Indicates the integration of the pointing stick. This is a string enum.
++Only needed for external pointing sticks. These are rare.
+--- a/quirks/50-system-lenovo.quirks
b/quirks/50-system-lenovo.quirks
+@@ -59,13 +59,20 @@ MatchDMIModalias=dmi:*svnLENOVO:*:pvrThi
+ ModelLenovoT450Touchpad=1
+ AttrPalmPressureThreshold=150
+
+-[Lenovo ThinkPad Compact USB Keyboard with TrackPoint]
++[Lenovo ThinkPad Compact USB Keyboard with TrackPoint (keyboard)]
+ MatchUdevType=keyboard
+ MatchBus=usb
+ MatchVendor=0x17EF
+ MatchProduct=0x6047
+ AttrKeyboardIntegration=external
+
++[Lenovo ThinkPad Compact USB Keyboard with TrackPoint (trackpoint)]
++MatchUdevType=pointingstick
++MatchBus=usb
++MatchVendor=0x17EF
++MatchProduct=0x6047
++AttrPointingStickIntegration=external
++
+ # Lenovo Thinkpad Yoga (not the consumer versions) disables the keyboard
+ # mechanically. We must not disable the keyboard because some keys are
+ # still accessible on the screen and volume rocker.
+--- a/src/evdev-fallback.c
b/src/evdev-fallback.c
+@@ -1313,8 +1313,8 @@ fallback_tablet_mode_switch_event(uint64
+ }
+
+ static void
+-fallback_keyboard_pair_tablet_mode(struct evdev_device *keyboard,
+- struct evdev_device *tablet_mode_switch)
++fallback_pair_tablet_mode(struct evdev_device *keyboard,
++struct evdev_device *tablet_mode_switch)
+ {
+ struct fallback_dispatch *dispatch =
+ fallback_dispatch(keyboard->dispatch);
+@@ -1322,8 +1322,12 @@
Bug#965376: ITP: hyperspy -- interactive analysis of multidimensional datasets
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: hyperspy Version : 0.8.4 Upstream Author : Hyperspy Developers (https://github.com/hyperspy/hyperspy/contributors) * URL : https://hyperspy.org/ * License : GPL-3 Programming Lang: Python Description : interactive analysis of multidimensional datasets HyperSpy is an open source Python library for the interactive analysis of multidimensional datasets that can be described as multidimensional arrays of a given signal (for example, a 2D array of spectra, also known as a spectrum image). . HyperSpy makes it straightforward to apply analytical procedures that operate on an individual signal to multidimensional arrays, as well as providing easy access to analytical tools that exploit the multidimensionality of the dataset. . Its modular structure makes it easy to add features to analyze many different types of signals.
Bug#965375: Mention mirror status page
Package: mirrors https://www.debian.org/mirror/list says "Everything else you want to know about Debian mirrors: https://www.debian.org/mirror/.; OK, but that page doesn't mention status. Therefore please mention https://mirror-master.debian.org/status/mirror-status.html on https://www.debian.org/mirror/.
Bug#965373: ITP: lua-yajl -- Yet Another JSON Library bindings for Lua 5.1
Package: wnpp Severity: normal Owner: Matthias Urlichs * Package name: lua-yajl Version : 0.2 Upstream Author : Brian Maher * URL : https://github.com/brimworks/lua-yajl * License : MIT/X Programming Lang: C, Lua Description : Yet Another JSON Library bindings for Lua 5.1 This package is required for updating the "mudlet" package (Debian: 3.7, Upstream: 4.9.1).
Bug#965369: ripit: broken URL in Homepage header (and abandoned project?)
* Michael Prokop [2020-07-20 15:00 +0200]: > Package: ripit > Version: 4.0.0~beta20140508-1 > Severity: normal > > Hi, > > the Homepage header is outdated: > > | Homepage: http://www.suwald.com/ripit/news.php > > This domain seems to have been taken over by a domain grabber, which > was confirmed by > https://twitter.com/ripit_cli/status/949577216756797440 > > So the website now lives at http://www.ripit.pl/ripit/news.php > > (But overall the project seems to be abandoned? Might be worth > pinging upstream to clarify its state?) Well, I am in contact with upstream. We are working towards the new musicbrainz api which doesn't work atm and as well to switch from freedb to gnudb. It will take a few weeks till all is working, so please be patient. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891623 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963046 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965232 Elimar -- Never make anything simple and efficient when a way can be found to make it complex and wonderful ;-)
Bug#965372: ocaml-mccs: FTBFS in sid
Source: ocaml-mccs
Version: 1.1+11-1
Severity: serious
Hello, as said for extlib (Bug #965115), also this package is now failing in
dh_dwz since the new binutils.
This is a snip of the error log (the full one is attached)
dh_install
dh_ocamldoc
dh_installdocs
dh_installchangelogs
dh_perl
dh_link
dh_strip_nondeterminism
dh_compress
dh_fixperms
debian/rules override_dh_missing
make[1]: Entering directory '/build/ocaml-mccs-1.1+11'
dh_missing --fail-missing
make[1]: Leaving directory '/build/ocaml-mccs-1.1+11'
dh_dwz
dwz:
debian/libmccs-ocaml/usr/lib/ocaml/mccs/glpk/shared/mccs_hostglpk_shared.cmxs:
.debug_info section not present
dwz: debian/libmccs-ocaml/usr/lib/ocaml/mccs/mccs.cmxs: DWARF version 0
unhandled
dwz: Too few files for multifile optimization
dh_dwz: error: dwz
-mdebian/libmccs-ocaml/usr/lib/debug/.dwz/x86_64-linux-gnu/libmccs-ocaml.debug
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/libmccs-ocaml.debug --
debian/libmccs-ocaml/usr/lib/ocaml/mccs/glpk/shared/mccs_hostglpk_shared.cmxs
debian/libmccs-ocaml/usr/lib/ocaml/mccs/mccs.cmxs
debian/libmccs-ocaml/usr/lib/ocaml/stublibs/dllmccs_stubs.so returned exit code
1
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
I: copying local configuration
G.
[0;34mD: cmdline: build --distribution sid --buildresult
/home/locutus/pbuilder/sid_result --basetgz /home/locutus/pbuilder/sid-base.tgz
--logfile
/home/locutus/pbuilder/sid_result/ocaml-mccs_1.1+11-1build2_amd64.build
--mirror http://deb.debian.org/debian --debootstrapopts
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache
/home/locutus/pbuilder/aptcache/debian --components main contrib non-free
../ocaml-mccs_1.1+11-1build2.dsc[0m
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Mon Jul 20 15:42:10 CEST 2020[0m
[0mI: pbuilder-time-stamp: 1595252530[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz][0m
[0mI: copying local configuration[0m
[1;33mW: No local /etc/mailname to copy, relying on
/tmp/build/11462/etc/mailname to be correct[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [../ocaml-mccs_1.1+11-1build2.dsc][0m
[0mI: copying [../ocaml-mccs_1.1+11.orig.tar.xz][0m
[0mI: copying [../ocaml-mccs_1.1+11-1build2.debian.tar.xz][0m
[0mI: Extracting source[0m
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.UvKxUvGM/trustedkeys.kbx':
General error
gpgv: Signature made Thu Jul 16 10:50:34 2020 UTC
gpgv:using RSA key 92978A6E195E4921825F7FF0F34F09744E9F5DD9
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on
./ocaml-mccs_1.1+11-1build2.dsc
dpkg-source: info: extracting ocaml-mccs in ocaml-mccs-1.1+11
dpkg-source: info: unpacking ocaml-mccs_1.1+11.orig.tar.xz
dpkg-source: info: unpacking ocaml-mccs_1.1+11-1build2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-lp_solver.cpp-Fix-typos.patch
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 12)
-> Trying to add debhelper-compat=12
-> Loop detected, last APT error was: ==
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> =
-> (not adding to debhelper-compat=12)
-> Cannot install debhelper-compat=12; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> Considering debhelper to satisfy the dependency
-> Considering build-dep dh-ocaml
-> Trying to add dh-ocaml
-> Considering build-dep ocaml-nox (>= 4.3.0~)
-> Trying to add ocaml-nox
-> Considering build-dep ocaml-dune
-> Trying to add ocaml-dune
-> Considering build-dep libcudf-ocaml-dev
-> Trying to add libcudf-ocaml-dev
-> Considering build-dep libglpk-dev
-> Trying to add libglpk-dev
-> Installing debhelper dh-ocaml ocaml-nox ocaml-dune libcudf-ocaml-dev
libglpk-dev
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev
Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters
Anton Zinoviev left as an exercise for the reader: > On Mon, Jul 20, 2020 at 05:32:55AM -0400, Nick Black wrote: > What about these? > > . for U+2610 BALLOT BOX > v for U+2611 BALLOT BOX WITH CHECK > x for U+2612 BALLOT BOX WITH X If that's what you like, it's fine with me =]. So long as they're differentiated. I don't make use of the following, so they're not important to me, but it might be worthwhile to handle these: U+2BBD BALLOT BOX WITH LIGHT X U+2718 HEAVY BALLOT X U+2717 BALLOT X So far as I'm aware, there's no way to map non-BMP UTF8 (e.g. U+1F5F6 BALLOT BOLD SCRIPT X) into the console Unicode->font table, since it only accepts UCS-2 (fixed 16-bit). I'm interested in putting together the necessary kernel work to address this, but until then it's not a thing. Will this work be going upstream? I'm not clear on whether you're the upstream maintainer, or just Debian's. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
Bug#965209: ITP: php-gettext-languages -- gettext languages with plural rules
On Sat, 18 Jul 2020 21:55:09 +0800 Paul Wise wrote: > On Sat, 2020-07-18 at 07:13 -0400, James Valleroy wrote: > > > Sorry if the description wasn't clear. Upstream ships the CLDR data > > that they need in JSON format (and under Unicode license). > > https://github.com/php-gettext/Languages/tree/master/src/cldr-data > > So they ship a (generated) embedded data copy? > > https://wiki.debian.org/EmbeddedCopies > > Looks like they keep this up to date better than Debian does :( > > Do you know how they generate the JSON files from the upstream data? No, but I sent an email to the upstream maintainer to ask about it. > I wonder if the unicode-cldr-core maintainer would be willing to > generate the JSON files in that package or unicode-cldr-core-json. > > > "Generated" in the description actually refers to this runtime parsing. > > That language should probably get fixed, it is confusing. Here is my updated long description: Provides a language list for gettext based on Unicode CLDR data. The data can be accessed through the Gettext\Languages\Language class. An example script is provided at /usr/share/doc/php-gettext-languages/examples/export-plural-rules. signature.asc Description: OpenPGP digital signature
Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters
On Mon, Jul 20, 2020 at 05:32:55AM -0400, Nick Black wrote: > > To be more precise, U+2571 BOX DRAWINGS LIGHT DIAGONAL UPPER > RIGHT TO LOWER LEFT ought be getting mapped to U+002F SOLIDUS > aka '/', but is instead being mapped to U+0025 PERCENT SIGN aka > '%'. Thanks. On Mon, Jul 20, 2020 at 05:48:15AM -0400, Nick Black wrote: > While I've got you here, while the case isn't quite as clear-cut > for these two, I'd suggest mapping > > U+2612 BALLOT BOX WITH X -> U+0058 LATIN CAPITAL LETTER X > > and > > U+2610 BALLOT BOX -> U+002D HYPHEN-MINUS or, if you prefer, > U+004F LATIN CAPITAL LETTER O What about these? . for U+2610 BALLOT BOX v for U+2611 BALLOT BOX WITH CHECK x for U+2612 BALLOT BOX WITH X Anton Zinoviev
Bug#690210: multiple suite and debian-ports support in debootstrap
Le vendredi 20 avril à 00h 16mn 13s (+0200), Raphael Hertzog a écrit :
>
> IMO the special casing for ports.debian.org architectures should be
> handled in a dedicated wrapper. And maybe debootstrap needs new features
> to make this wrapper possible.
>
Hi,
It would be beneficial to add a new option to debootstrap
to postprocess downloaded package indices with an external
helper program.
This would allow to enforce the policy : 'debootstrap should install
the newest version of each package'
Please find below a first try to implement it. I would be thankful
for comments, advice or suggestions of improvement.
Regards,
JH Chatenet
diff -Naur a/debootstrap/debootstrap b/debootstrap/debootstrap
--- a/debootstrap/debootstrap 2020-03-13 03:03:08.0 +0100
+++ b/debootstrap/debootstrap 2020-07-20 11:08:15.531224245 +0200
@@ -46,6 +46,7 @@
CHECKCERTIF=""
PRIVATEKEY=""
CACHE_DIR=""
+PACKAGES_FILES_PROCESSOR=""
DEF_MIRROR="http://deb.debian.org/debian;
DEF_HTTPS_MIRROR="https://deb.debian.org/debian;
@@ -125,6 +126,10 @@
(requires --second-stage)
--extractor=TYPE override automatic .deb extractor selection
(supported: $EXTRACTORS_SUPPORTED)
+ --packages-files-processor=HELPER
+ specifies the path to an external helper program
+ to postprocess downloaded Packages files
+ (this may be beneficial in conjunction with
--extra-suites)
--debian-installer used for internal purposes by debian-installer
--private-key=file read the private key from file
--certificate=file use the client certificate stored in file (PEM)
@@ -323,6 +328,17 @@
fi
EXTRA_SUITES="$(echo "$EXTRA_SUITES" | tr , " ")"
;;
+ --packages-files-processor|--packages-files-processor=?*)
+ if [ "$1" = "--packages-files-processor" ] && [ -n "$2" ]; then
+ PACKAGES_FILES_PROCESSOR="$2"
+ shift 2
+ elif [ "$1" != "${1#--packages-files-processor=}" ]; then
+
PACKAGES_FILES_PROCESSOR="${1#--packages-files-processor=}"
+ shift 1
+ else
+error 1 NEEDARG "option requires an argument %s" "$1"
+ fi
+ ;;
--components|--components=?*)
if [ "$1" = "--components" ] && [ -n "$2" ]; then
USE_COMPONENTS="$2"
@@ -459,6 +475,9 @@
if [ -e "$DEBOOTSTRAP_DIR/extra-suites" ]; then
EXTRA_SUITES=$(cat "$DEBOOTSTRAP_DIR/extra-suites")
fi
+ if [ -e "$DEBOOTSTRAP_DIR/extra-suites-unprocessed" ]; then
+ extra_suites_unprocessed=$(cat
"$DEBOOTSTRAP_DIR/extra-suites-unprocessed")
+ fi
ARCH=$(cat "$DEBOOTSTRAP_DIR/arch")
USER_MIRROR=$(cat "$DEBOOTSTRAP_DIR/mirror")
if [ -e "$DEBOOTSTRAP_DIR/variant" ]; then
@@ -686,6 +705,8 @@
###
+packages_files_postprocess_initialize
+
if am_doing_phase finddebs; then
if [ "$FINDDEBS_NEEDS_INDICES" = "true" ] || \
[ "$RESOLVE_DEPS" = "true" ]; then
@@ -751,6 +772,8 @@
echo "$SUITE" >"$TARGET/debootstrap/suite"
[ "" = "$EXTRA_SUITES" ] ||
echo "$EXTRA_SUITES">"$TARGET/debootstrap/extra-suites"
+ [ "$EXTRA_SUITES" = "$extra_suites_unprocessed" ] ||
+ echo "$extra_suites_unprocessed"
>"$TARGET/debootstrap/extra-suites-unprocessed"
[ "" = "$VARIANT" ] ||
echo "$VARIANT" >"$TARGET/debootstrap/variant"
echo "$required">"$TARGET/debootstrap/required"
@@ -786,8 +809,10 @@
cp "$DEBOOTSTRAP_DIR"/scripts/*-common "$TARGET/debootstrap/"
echo "$ARCH">"$TARGET/debootstrap/arch"
echo "$SUITE" >"$TARGET/debootstrap/suite"
- [ "" = "$EXTRA_SUITES" ] ||
- echo "$EXTRA_SUITES"
>"$TARGET/debootstrap/extra-suites"
+ if [ -n "$EXTRA_SUITES" ]; then
+ echo "$EXTRA_SUITES" >"$TARGET/debootstrap/extra-suites"
+ echo "$extra_suites_unprocessed"
>"$TARGET/debootstrap/extra-suites-unprocessed"
+ fi
echo "$USER_MIRROR" >"$TARGET/debootstrap/mirror"
[ "" = "$VARIANT" ] ||
echo "$VARIANT" >"$TARGET/debootstrap/variant"
diff -Naur a/debootstrap/debootstrap.8 b/debootstrap/debootstrap.8
--- a/debootstrap/debootstrap.8 2020-03-09 06:21:13.0 +0100
+++ b/debootstrap/debootstrap.8 2020-07-20 11:20:58.187006051 +0200
@@ -63,6 +63,10 @@
.IP "\fB\-\-extra-suites=alpha,beta\fP"
Also use packages from the listed
Bug#965369: ripit: broken URL in Homepage header (and abandoned project?)
Package: ripit Version: 4.0.0~beta20140508-1 Severity: normal Hi, the Homepage header is outdated: | Homepage: http://www.suwald.com/ripit/news.php This domain seems to have been taken over by a domain grabber, which was confirmed by https://twitter.com/ripit_cli/status/949577216756797440 So the website now lives at http://www.ripit.pl/ripit/news.php (But overall the project seems to be abandoned? Might be worth pinging upstream to clarify its state?) regards -mika-
Bug#965368: rkhunter: fails to start
Package: rkhunter Version: 1.4.6-8 Severity: normal Dear Maintainer, rkhunter fails to start because it cannot find the fgrep/egrep utilities. The return message is as follows: $ rkhunter --check Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: /usr/bin/egrep Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: /usr/bin/fgrep while they are in the path: $ type egrep fgrep egrep is /bin/egrep fgrep is /bin/fgrep Thank you, Antonio
Bug#940413: syncthing: Please update to version 1.2.2
On Sun, Jul 19, 2020 at 10:57 PM Nicholas D Steeves wrote: > It seems to me that the most expedient path forward is to jump from > 1.2.x to 1.4.x. ACK? Right, it looks like we will have too. I was trying to avoid it at first because it is a lot of work. I suggest that we move slowly and try to find the lowest version that works for now. By the way I take notes here: - https://salsa.debian.org/go-team/packages/syncthing/-/blob/master/debian/README.Debian Cheers,
Bug#965367: qemu: no text (just unicode codepoint blocks) even for ASCII in compatmonitor0
Package: qemu-system-x86 Version: 1:5.0-10 Severity: normal X-Debbugs-Cc: t...@mirbsd.de Start qemu-system-i386 with no arguments, then select View → compatmonitor0 in the menu. This leads to illegible text, as attached. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5 ii libaio1 0.3.112-8 ii libbrlapi0.7 6.0+dfsg-6 ii libc6 2.31-1 ii libcacard01:2.7.0-1 ii libcapstone3 4.0.1+really+3.0.5-2 ii libepoxy0 1.5.4-1 ii libfdt1 1.6.0-1 ii libgbm1 20.1.2-1 ii libgcc-s1 10.1.0-6 ii libglib2.0-0 2.64.4-1 ii libgnutls30 3.6.14-2+b1 ii libibverbs1 29.0-1 ii libjpeg62-turbo 1:2.0.5-1 ii libnettle83.6-2 ii libnuma1 2.0.12-1+b1 ii libpixman-1-0 0.36.0-1 ii libpmem1 1.8-1 ii libpng16-16 1.6.37-2 ii librdmacm129.0-1 ii libsasl2-22.1.27+dfsg-2 ii libseccomp2 2.4.3-1+b1 ii libslirp0 4.3.1-1 ii libspice-server1 0.14.3-1 ii liburing1 0.6-3 ii libusb-1.0-0 2:1.0.23-2 ii libusbredirparser10.8.0-1+b1 ii libvdeplug2 2.3.2+r586-2.2+b1 ii libvirglrenderer1 0.8.2-3 ii libxendevicemodel14.11.4+24-gddaaccbbab-1 ii libxenevtchn1 4.11.4+24-gddaaccbbab-1 ii libxenforeignmemory1 4.11.4+24-gddaaccbbab-1 ii libxengnttab1 4.11.4+24-gddaaccbbab-1 ii libxenmisc4.114.11.4+24-gddaaccbbab-1 ii libxenstore3.04.11.4+24-gddaaccbbab-1 ii libxentoolcore1 4.11.4+24-gddaaccbbab-1 ii qemu-system-common1:5.0-10 ii qemu-system-data 1:5.0-10 ii seabios 1.13.0-1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages qemu-system-x86 recommends: pn ovmf ii qemu-system-gui 1:5.0-10 ii qemu-utils 1:5.0-10 Versions of packages qemu-system-x86 suggests: pn qemu-block-extra ii qemu-system-data [sgabios] 1:5.0-10 pn samba pn vde2 -- no debconf information
Bug#965077: MySQL database with "SQLAUthTypes Backend" doesn't work anymore in buster
Am 18.07.20 um 13:33 schrieb Hilmar Preuße: I applied your patch to 1.3.7rc4 code, I had to fix it; upstream changed variable names in [1]. The result is here [2]. I did not test the code and I have doubt, that it works as you expect. Would be nice, if you could test this. I don't plan to do another upload of 1.3.6 in unstable, as 1.3.7 will be released soon. Thanks a lot; I'm currently on vacation and will try it as soon as possible. Kind regards -- Andreas Trottmann CTO Werft22 AG T +41 56 210 91 32 F +41 56 210 91 34 M +41 79 229 88 55 andreas.trottm...@werft22.com Stadtbachstrasse 63 CH‑5400 Baden / Schweiz www.werft22.com
Bug#962863: r-cran-rdflib: autopkgtest regression
On Mon, 15 Jun 2020 11:17:24 +0200 Graham Inggs wrote: > Source: r-cran-rdflib > Version: 0.2.3+dfsg-1 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: regression > > Hi Maintainer > > Sometime in the last month, r-cran-rdflib started to fail its own > autopkgtests [1]. > There's a failing migration-reference/0 test in testing on 2020-05-22 > which was before the new r-base migrated. > > I've copied what I hope is the relevant part of the log below. I cannot seem to reproduce the error on my system (using a clean chroot). Logs: autopkgtest [17:46:54]: test pkg-r-autopkgtest: ---] autopkgtest [17:46:54]: test pkg-r-autopkgtest: - - - - - - - - - - results - - - - - - - - - - pkg-r-autopkgtest PASS autopkgtest [17:46:54]: summary run-unit-test PASS pkg-r-autopkgtest PASS In the test logs I observed that it _did_ pass on July 15 after it again started to fail yet again - weirdly enough. Log here[1] Is it randomly failing here, or is it error at my end? I'm not sure, please let me know. This is tagged for removal within a week now, and hence it'd be great if I can get a response. [1]: https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rdflib/6273992/log.gz Thanks and Regards, Nilesh signature.asc Description: OpenPGP digital signature
Bug#965366: ITP: pique -- software pipeline for performing genome wide association studies
Package: wnpp Severity: wishlist Subject: ITP: pique -- software pipeline for performing genome wide association studies Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: pique Version : 1.0 Upstream Author : A. J. Travis and A. Douglas * URL : https://github.com/tony-travis/PIQUE/ * License : GPL-3.0 Programming Lang: (C, C++, C#, Perl, Python, etc.) Description : software pipeline for performing genome wide association studies PIQUE is a software pipeline for performing genome wide association studies (GWAS). The main function of PIQUE is to provide ‘convenience’ wrappers that allow users to perform GWAS using the popular program EMMAX (Kang et al., 2010) without the need to be familiar with all of the software tools used to generate the required EMMAX input files. PIQUE will also perform a number of quality control steps prior to running EMMAX, ensuring that the various input data files are in the correct format. PIQUE proceeds in two main stages although there are multiple entry and exit points from which the pipeline can be run. The first stage consists of running the “pique-input” program, which can read genotype and phenotype information in several different formats and generates all the necessary input files required to run EMMAX. The second step in the pipeline uses the “pique-run” program to actually run EMMAX using the files generated by “pique-input” (or pre-existing user-supplied input files) to perform the GWAS and output the analysis summary files. Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/pique
Bug#964793: qemu-system-x86 crash
Hi, I experience exactly the same bevahiour after installing 1:3.1+dfsg-8+deb10u6 on Debian as Dom0 with Xen version 4.11.4+24-gddaaccbbab-1~deb10u1. No interessting output in any log files as far as I can tell. Downgrading the qemu-system-x86 packet to 1:3.1+dfsg-8+deb10u5 immediately fixes the problem. Thanks, Max -- Max Ried Heinrich-Heine-Universität Düsseldorf Institut für Informatik Systemadministration Gebäude 25.12, Raum 01.28 Universitätsstr. 1 40225 Düsseldorf Tel: +49 211 81 10715 smime.p7s Description: S/MIME Cryptographic Signature
Bug#965309: bzdiff not working with two compressed files
Control: tags -1 + confirmed pending El 19/07/20 a las 10:13, Joey Schulze escribió: > Package: bzip2 > Version: 1.0.6-9.2~deb10u1 > Severity: important > Tags: patch > > Moin, > > bzdiff does not work when comparing two bzip2 compressed files: > > finlandia!joey(tty6):/data> bzdiff options-18.bz2 options-19.bz2 > diff: extra operand '/tmp/bzdiff.6FPnOK9OHZ' > diff: Try 'diff --help' for more information. > > The problem has been introduced in buster and is still present in bullseye. > > The solution is to remove the quotes around options in diff execution > as show in the attached patch. > > Regards > > Joey Dear Joey, Thanks for reporting this. Patch applied in git, and I'll upload to unstable today or tomorrow. Cheers, -- Santiago signature.asc Description: PGP signature
Bug#965355: transition: ace
On Mon, Jul 20, 2020 at 09:34:41AM +0100, Sudip Mukherjee wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > Another transition for 'ace' please. > Small transition with only two affected packages: diagnostics, ivtools. > ivtools builds fine with ace 6.5.10+dfsg-1 version in experimental. > diagnostics already has a FTBFS (#964631) on it and so I could not verify > if there is any impact on it. fwiw, I have used a snapshot of '20200706T204334Z' (the last snapshot where diagnostics built successfully), installed ace/6.5.10+dfsg-1 and verified diagnostics still builds. Not an idea way to verify, but atleast now I know that new version of 'ace' will not create any new FTBFS with diagnostics. -- Regards Sudip
Bug#961016: podman: Error: error creating libpod runtime: default OCI runtime "crun" not found: invalid argument
Le 16/07/20 à 00:59, Dmitry Smirnov a écrit : On Thursday, 16 July 2020 5:41:43 AM AEST Emmanuel Kasper wrote: I think there is a problem in the Depends of podman: More likely there is a problem in Podman configuration. "io.podman.service" should be restarted to pick-up configuration changes. Well this is the default out of the box configuration just after installation, the configuration was not changed "runc" and "crun" can be used interchangeably.
Bug#965365: e1000e: Add support for Comet Lake
Control: tags -1 + patch Created merge request at https://salsa.debian.org/kernel-team/linux/-/merge_requests/257 .
Bug#964985: libpcap0.8: build with rpcap support (--enable-remote)
Hi, On Mon, Jul 13, 2020 at 11:03 PM Lukas Tribus wrote: > since libpcap 1.9, rpcap (remote-pcap) is supported [1] and can > be enabled at build by specifying --enable-remote or in cmake > -DENABLE_REMOTE=YES [2]. > > Please consider enabling this for libpcap 1.9. Thank you for the suggestion. Having rpcapd packaged for Debian and having remote capture support in libpcap could be useful in some situations, however I'm not sure that the code is supposed to be production-ready just yet. Guy, do you think it's generally safe to enable remote capture in Debian's packaged libpcap? Thanks,
Bug#965365: e1000e: Add support for Comet Lake
Source: linux
Version: 4.19.118-2
Severity: normal
X-Debbugs-Cc: bonac...@ee.ethz.ch
Hi
v4.19.y series lack support for Comet Lake in e1000e which was added
upstream in 5.5-rc1 with 914ee9c436cb ("e1000e: Add support for Comet
Lake").
Consequently buster kernel does not support
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (11)
I219-V [8086:0d4d]
Subsystem: ASUSTeK Computer Inc. Device [1043:8672]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Bug#965364: [createrepo] new upstream version 0.10.4 available
Package: createrepo Version: 0.10.3 Severity: normal --- Please enter the report below this line. --- 0.10.4 fixes in particular https://bugzilla.redhat.com/show_bug.cgi?id=1058975 Thanks!
Bug#962213: package ftbfs on arm64 and armhf
On Thu, 4 Jun 2020 17:24:54 +0200 Matthias Klose wrote: > The package ftbfs on arm64 and armhf, trying to link with -ldrm. Apparently > libdrm-dev is an implicit b-d for x86 targets, but used explicitly. Fixed by > b-d on libdrm-dev everywhere. Thanks for a very nice bug report! Submitted an update on mentors at https://mentors.debian.net/package/opencpn. We'll see if/when someone has time to review. I have not been able to test the arm builds, taking your word that lindrm-dev should fix it. --alec
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "opencpn" * Package name: opencpn Version : 5.2.0+dfsg-1 Upstream Author : Dave S. Register * URL : https://opencpn.org * License : GPL-2+ * Vcs : https://gitlab.com/leamas/opencpn Section : misc It builds those binary packages: opencpn - Open Source Chartplotter and Marine GPS Navigation Software opencpn-data - Open Source Chartplotter and Marine GPS Navigation Software (data) opencpn-plugins - Open Source Chartplotter and Marine GPS Navigation Software (transition) To access further information about this package see https://mentors.debian.net/package/opencpn Alternatively, one can download the package with dget: dget -x https://mentors.debian.net/debian/pool/main/o/opencpn/opencpn_5.2.0+dfsg-1.dsc Changes since the last upload: * New upstream release * Closes: #962213 * Update debian/copyright due to new upstream source layout. * Bump Standards-Version to 4.5.0, no changes. * Drop upstreamed patches. Regards, -- Alec Leamas
Bug#961582: wand: please make the build reproducible
Hi Håvard, > The reason I mentioned kernel variations is because when I tested the > new version (0.6.2) which includes your patch (not yet packaged in > Debian) reprotest still fails, and it fails when I use "$ reprotest > --variations=kernel ..." I cannot think why changing the kernel would make any difference to the difference in the document. It may be reproducible without this variation, it is not clear from your comment. However, please either upload with this patch, or provide some kind of (diffoscope?) output that I can see. Trying to guess at a distance is not very efficient (or fun). Thanks. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#965362: numpydoc: please make the build reproducible
Source: numpydoc Version: 1.1.0-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0] we noticed that numpydoc could not be built reproducibly. This is because it includes a junit-results.xml and .coverage file from the test run. (The latter file should have been detected by the package-contains-python-coverage-file Lintian tag FYI.) Patch attached. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk ` a/debian/rules 2020-07-20 11:14:23.254979286 +0100 --- b/debian/rules 2020-07-20 11:20:45.409510366 +0100 @@ -12,3 +12,8 @@ %: dh $@ --with python3 --buildsystem=pybuild + +override_dh_auto_install: + dh_auto_install + find debian -name .coverage -delete + find debian -name junit-results.xml -delete
Bug#889868: mtd-utils: please enable running unit tests
The changes are included in the current version. This issue can be closed.
Bug#965361: python-cooler: please make the build reproducible
Source: python-cooler Version: 0.8.8-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: umask filesystem X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0] we noticed that python-cooler could not be built reproducibly. This is because the /usr/share/doc/python3-cooler/tests.tar.xz file embedded the build user's user uid, gid and umask. It also was sorted based on the filesystem order. Patch attached. (Just an unrelated heads-up that this file is 30MB.) [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- a/debian/rules 2020-07-20 11:02:04.230747315 +0100 --- b/debian/rules 2020-07-20 11:08:55.124937866 +0100 @@ -9,4 +9,4 @@ override_dh_installexamples: dh_installexamples - cd debian/python3-$(PYBUILD_NAME)-examples/usr/share/doc/python3-$(PYBUILD_NAME) && tar caf tests.tar.xz tests && rm -rf tests + cd debian/python3-$(PYBUILD_NAME)-examples/usr/share/doc/python3-$(PYBUILD_NAME) && tar --create --owner=0 --group=0 --numeric-owner --sort=name --file tests.tar.xz tests && rm -rf tests
Bug#964738: Turns out this was an upstream bug
The issue should be fixed with https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1365 which is pushed to gnome-3-36 branch as well as master.
Bug#965191: libgdbm6: gdbm_reorganize() breaks later use in same process
DrNick on #kernelnewbies mentioned that on mmap() isn't cleaned up: 698118 14:52:47.634488 mmap(NULL, 16384, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0x7f0467ea2000 That seems to keep the fd open, and so the lock persists... So it's a libgdbm error.
Bug#965256: logilab-common: please make the build reproducible
forwarded 965256 https://www.logilab.org/ticket/10251578 thanks Hi Sandro, > would you mind forwarding this patch upstream (and eventually follow > up any change they may request)? thanks! Okay, I think I've managed to do this here: https://www.logilab.org/ticket/10251578 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#965360: apparmor-profiles: Please meke seperate packages for each apparmor profile
Package: apparmor-profiles Version: 2.13.4-3 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, currently when the apparmor-profiles package is installed, it installs several apparmor profile files. In this way users can have all or none of the profiles installed in their systems. Sometimes a user wants only a specific profile (or profiles) installed and doesn't really want the other profiles to be installed as well because: - he doesn't need the other profiles, - he has his own alternative profiles, which differ in rule sets, - the other profiles simply cause some issues with applications they confine. What do you think about another approach, which is to create separate packages containing individual apparmor profiles? For instance, there's the usr.sbin.dnsmasq file which is related to the dnsmasq package. In this case there could be a package named dnsmasq-apparmor-profile which would include the usr.sbin.dnsmasq file. If a user wanted to install dnsmasq and also wanted it to be confined by the default apparmor profile provided by Debian, he could also install dnsmasq-apparmor-profile, which wouldn't affect any other app functionality. Also, there are many profiles under /usr/share/apparmor/extra-profiles/ which aren't enabled, and probably no one uses them at all. If there was a package, for instance, postfix-apparmor-profile containing all the usr.lib.postfix* files installed under /etc/apparmor.d/ , I think more people would test the profiles, which would contribute to better development of the profiles themselves. Probably not all of the files included currently in the apparmor-profiles package can be separated in the way described above, but there are cases where this can be done, and I think it should be done. Tell me what do you think about this solution. -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQR1ZhNYxftXAnkWpwEy2ctjR5bMoQUCXxVrFAAKCRAy2ctjR5bM oUuSAP9vC0YwQpOCkhvml75GWrKVeWRNtxsLcDmG0G4qi/DhpQEA6Sqw0tiaYwve 1rgG46iE976oC6uVliwRSba/rkBEkAs= =5jJs -END PGP SIGNATURE-
Bug#965352: libopenmpi3: breaks tests in client programs
Package: libopenmpi3 Followup-For: Bug #965352 Build log for dolfin 2019.2.0~git20200218.027d9cc-12 indicates a problem with malloc in libucs.so, one of the new features (UCX) added in openmpi 4.0.4-2. Run C++ regression tests (MPI) Test project /<>/obj-x86_64-linux-gnu Start 2: demo_auto-adaptive-poisson_mpi Start 4: demo_bcs_mpi 1/49 Test #2: demo_auto-adaptive-poisson_mpi . Passed0.59 sec Start 6: demo_biharmonic_mpi 2/49 Test #4: demo_bcs_mpi ...***Failed1.75 sec malloc(): mismatching next->prev_size (unsorted) [x86-grnet-01:17654] *** Process received signal *** [x86-grnet-01:17654] Signal: Aborted (6) [x86-grnet-01:17654] Signal code: (-6) [x86-grnet-01:17654] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd30)[0x7f1882828d30] [x86-grnet-01:17654] [ 1] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7f1882828cb1] [x86-grnet-01:17654] [ 2] /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7f1882812537] [x86-grnet-01:17654] [ 3] /lib/x86_64-linux-gnu/libc.so.6(+0x7e738)[0x7f188286b738] [x86-grnet-01:17654] [ 4] /lib/x86_64-linux-gnu/libc.so.6(+0x85a2a)[0x7f1882872a2a] [x86-grnet-01:17654] [ 5] /lib/x86_64-linux-gnu/libc.so.6(+0x88e7c)[0x7f1882875e7c] [x86-grnet-01:17654] [ 6] /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x1a9)[0x7f1882877269] [x86-grnet-01:17654] [ 7] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_mpool_chunk_malloc+0xc)[0x7f187c969bfc] [x86-grnet-01:17654] [ 8] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_mpool_grow+0x60)[0x7f187c969980] [x86-grnet-01:17654] [ 9] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_mpool_get_grow+0x10)[0x7f187c969ba0] [x86-grnet-01:17654] [10] /usr/lib/x86_64-linux-gnu/libuct.so.0(+0x1b155)[0x7f187c930155] [x86-grnet-01:17654] [11] /usr/lib/x86_64-linux-gnu/libuct.so.0(+0x1a630)[0x7f187c92f630] [x86-grnet-01:17654] [12] /usr/lib/x86_64-linux-gnu/libuct.so.0(+0x1cd4e)[0x7f187c931d4e] [x86-grnet-01:17654] [13] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_event_set_wait+0xfd)[0x7f187c975bed] [x86-grnet-01:17654] [14] /usr/lib/x86_64-linux-gnu/libuct.so.0(uct_tcp_iface_progress+0x8f)[0x7f187c931e3f] [x86-grnet-01:17654] [15] /usr/lib/x86_64-linux-gnu/libucp.so.0(ucp_worker_progress+0x6a)[0x7f187cdf557a] [x86-grnet-01:17654] [16] /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pml_ucx.so(mca_pml_ucx_recv+0x118)[0x7f187ce6ae68] [x86-grnet-01:17654] [17] /usr/lib/x86_64-linux-gnu/libmpi.so.40(ompi_coll_base_scan_intra_linear+0x12b)[0x7f188205575b] [x86-grnet-01:17654] [18] /usr/lib/x86_64-linux-gnu/libmpi.so.40(MPI_Scan+0x128)[0x7f18820269b8] [x86-grnet-01:17654] [19] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin3MPI13global_offsetEP19ompi_communicator_tmb+0x4a)[0x7f1882ef790a] [x86-grnet-01:17654] [20] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin12GraphBuilder30compute_local_dual_graph_keyedILi3EEEiP19ompi_communicator_tRKN5boost11multi_arrayIlLm2ESaIlEEERKNS_8CellTypeERSt6vectorISD_ImSaImEESaISF_EERSD_ISt4pairISF_iESaISK_EE+0x1d4)[0x7f188300c994] [x86-grnet-01:17654] [21] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin12GraphBuilder24compute_local_dual_graphEP19ompi_communicator_tRKN5boost11multi_arrayIlLm2ESaIlEEERKNS_8CellTypeERSt6vectorISC_ImSaImEESaISE_EERSC_ISt4pairISE_iESaISJ_EE+0x2fa)[0x7f1883007eba] [x86-grnet-01:17654] [22] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin12GraphBuilder18compute_dual_graphEP19ompi_communicator_tRKN5boost11multi_arrayIlLm2ESaIlEEERKNS_8CellTypeElRSt6vectorISC_ImSaImEESaISE_EERSt3setIlSt4lessIlES5_E+0xf3)[0x7f1883008003] [x86-grnet-01:17654] [23] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin6SCOTCH17compute_partitionEP19ompi_communicator_tRSt6vectorIiSaIiEERSt3mapIlS5_St4lessIlESaISt4pairIKlS5_EEERKN5boost11multi_arrayIlLm2ESaIlEEERKS3_ImSaImEEllRKNS_8CellTypeE+0x99)[0x7f18830100e9] [x86-grnet-01:17654] [24] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin16MeshPartitioning15partition_cellsERKP19ompi_communicator_tRKNS_13LocalMeshDataENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIiSaIiEERSt3mapIlSG_St4lessIlESaISt4pairIKlSG_EEE+0x180)[0x7f18831f72e0] [x86-grnet-01:17654] [25] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin16MeshPartitioning22build_distributed_meshERNS_4MeshERKNS_13LocalMeshDataENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x403)[0x7f18831fec93] [x86-grnet-01:17654] [26] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin7XMLFile4readERNS_4MeshE+0x196)[0x7f188306] [x86-grnet-01:17654] [27] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin4MeshC1EP19ompi_communicator_tNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x2bb)[0x7f18831e700b] [x86-grnet-01:17654] [28] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin4MeshC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x4e)[0x7f18831e70de] [x86-grnet-01:17654] [29]
Bug#960824: restinio: Missing atomic library on several architectures
Upstream is trying to fix it, but unfortunately the first draft did not solve it completely. Hopefully soon. The current new version do not solve it, as far as I know. -- Happy hacking Petter Reinholdtsen
Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters
While I've got you here, while the case isn't quite as clear-cut for these two, I'd suggest mapping U+2612 BALLOT BOX WITH X -> U+0058 LATIN CAPITAL LETTER X and U+2610 BALLOT BOX -> U+002D HYPHEN-MINUS or, if you prefer, U+004F LATIN CAPITAL LETTER O Right now they render as the same missing glyph, which does nothing good for anybody =]. I add these two mappings on the fly in Notcurses for my multiselector widget. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters
Anton Zinoviev left as an exercise for the reader: I tested your Arabic-Fixed16 and Lat15-Terminus16, I'm pretty sure. First, I verified that the targeted UTF-8 was being rendered as the absent glyph, as expected. I then ran "setfont FONTFILE", and verified that the UTF-8 was properly being rendered as the base of its class. Except for one: the weird "big foreslash" is being mapped to a percent sign instead of a foreslash. Everything else looks correct, and seems a big improvement. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters
Nick Black left as an exercise for the reader: > I tested your Arabic-Fixed16 and Lat15-Terminus16, I'm pretty > sure. First, I verified that the targeted UTF-8 was being > rendered as the absent glyph, as expected. I then ran "setfont > FONTFILE", and verified that the UTF-8 was properly being > rendered as the base of its class. Except for one: the weird > "big foreslash" is being mapped to a percent sign instead of a > foreslash. Everything else looks correct, and seems a big > improvement. To be more precise, U+2571 BOX DRAWINGS LIGHT DIAGONAL UPPER RIGHT TO LOWER LEFT ought be getting mapped to U+002F SOLIDUS aka '/', but is instead being mapped to U+0025 PERCENT SIGN aka '%'. I believe you've mapped to font index 37 when you want font index 47. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
Bug#698267: fixed in mutt 1.14.5-1
On Wed, Jul 01, 2020 at 05:50:39PM +0900, Benjamin Poirier wrote: > This triggered a regression, I would say. > > When composing a new message, the realname configuration item is not > taken into account to create the "From" address. For example, in my > case, it appears as "From: benjamin.poir...@gmail.com". This is a > regression from package version 1.14.4-2 where it would appear as "From: > Benjamin Poirier ". Yes, I will fix it with an update between today and tomorrow.
Bug#965358: Please update Widelands package to Build 21
Control: notfound -1 1:21-0 Control: found -1 1:20-2 On Mon, 20 Jul 2020 at 09:49:13 +0100, Fòram na Gàidhlig wrote: > We have just released a new version of Widelands Thanks for reporting this. "The version in Debian is out of date" can be considered to be a bug in the version currently in Debian testing/unstable, which will be fixed by the first upload of version 1:21 or later. I'm adjusting the metadata of this bug report accordingly. (I don't play Widelands myself, so I'm not intending to work on packaging this new version - hopefully someone else in the games team will.) smcv
Bug#965359: lynis: Denial of service by user creating symlink to /, disk space exhaustion due to verbose logging
Package: lynis Version: 3.0.0-1 Severity: critical Tags: security Justification: breaks unrelated software X-Debbugs-Cc: witold.bary...@gmail.com, Debian Security Team root@debian:/var/log# grep lynis daemon.log | wc -l 21311825 root@debian:/var/log# grep lynis daemon.log.1 | wc -l 1986915 root@debian:/var/log# grep lynis syslog | wc -l 19082244 root@debian:/var/log# grep lynis syslog.1 | wc -l 2229585 root@debian:/var/log# ls -al | egrep 'syslog|daemon|lynis' -rw-r- 1 root adm 22056719829 Jul 20 09:01 daemon.log -rw-r- 1 root adm 2139363076 Jul 19 00:00 daemon.log.1 -rw-r- 1 root root1406036 Jul 20 08:57 lynis.log -rw-r- 1 root root 189897 Jul 20 08:57 lynis-report.dat -rw-r- 1 root adm 19752025179 Jul 20 09:01 syslog -rw-r- 1 root adm 2308186335 Jul 20 00:00 syslog.1 -rw-r- 1 root adm12446588 Jul 19 00:00 syslog.2.gz -rw-r- 1 root adm 3843198 Jul 18 00:00 syslog.3.gz -rw-r- 1 root adm 3957595 Jul 17 00:00 syslog.4.gz -rw-r- 1 root adm 651678 Jul 16 00:00 syslog.5.gz root@debian:/var/log# A sample: Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/bin/X11' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar/bin'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/dev/fd/3' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: '/lib/live/mount/overlay/rw/home/user/bar/dev/fd/4': No such file or directory Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/bar' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/Games/apex-legends/dosdevices/f:/debian' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar/home/user/Games/apex-legends/dosdevices/f:'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/Games/apex-legends/dosdevices/z:' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/.local/share/webkitgtk/databases/indexeddb/v0' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar/home/user/.local/share/webkitgtk/databases/indexeddb'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/lib' is part of the same file system loop as '/lib'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/proc/self/task/2755422/fd/3' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: '/lib/live/mount/overlay/rw/home/user/bar/proc/self/task/2755422/fd/4': No such file or directory Jul 19 00:12:00 localhost lynis[2755422]: find: '/lib/live/mount/overlay/rw/home/user/bar/proc/self/task/2755422/fdinfo/4': No such file or directory Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/proc/6/cwd' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. It consumed all 160GB of my disk space easily. All because `/home/user/bar -> /` symlink. Lynis should not emit 'File system loop detected' to logs. It is not a bug or error, similarly 'No such file or directory' should not be logged, it is not a bug or error, but normal occurance. Symlinks that do point back up, are normal, and shouldn't be logged, it is normal occurance. Multiple unrelated services got disrupted (including crashs), due to disk space exhaustion, missing logs from other software, and other software crashing with unsaved state (i.e. text editor, web browser, etc). Regards, Witold -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lynis depends on: ii e2fsprogs 1.45.6-1 Versions of packages
Bug#965358: Please update Widelands package to Build 21
Package: widelands Version: 1:21-0 Dear Debian team, We have just released a new version of Widelands - would you be willing to take care of the packaging for us? Source package: https://launchpad.net/widelands/build21/build21 Branch: https://github.com/widelands/widelands/tree/build-21 Ubuntu PPA for reference: https://code.launchpad.net/~widelands-dev/+recipe/widelands-b21 The following font dependencies were dropped due to lack of translators: * Sinhala (Sinhala, lklug) * Myanmar (mmrCensus) Thanks GunChleoc signature.asc Description: OpenPGP digital signature
Bug#925965: still exists in 5.7.6-1
Control: found -1 5.7.6-1 For me this issue still exists in kernel 5.7.0 so package version 5.7.6-1 Here the Error from dmesg: ``` [ 8811.591801] i915 :00:02.0: [drm] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set [ 9714.864832] i915 :00:02.0: [drm] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set [10315.440624] i915 :00:02.0: [drm] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set ``` Best regards Fritz
Bug#965357: RFS: libjs-material-design-lite/1.3.0+dfsg-1 [ITP] -- Material Design Lite (CSS, JS)
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libjs-material-design-lite" * Package name: libjs-material-design-lite Version : 1.3.0+dfsg-1 Upstream Author : https://getmdl.io/ * URL : https://github.com/google/material-design-lite * License : Apache-2.0 * Vcs : https://salsa.debian.org/fred1m-guest/libjs-material-design-lite Section : javascript It builds those binary packages: libjs-material-design-lite - Material Design Lite (CSS, JS) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libjs-material-design-lite Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libj/libjs-material-design-lite/libjs-material-design-lite_1.3.0+dfsg-1.dsc Changes since the last upload: * packaging: - libjs-material-design-lite upstream https://getmdl.io/ - is a dependency for searx-admin packaging, MDL is embedded into code base (closes: #964766) This package is a request to packaging of searx-admin (#944421) I am also looking for mentors that may be not far from: * https://wiki.debian.org/FreedomBox * https://wiki.debian.org/Javascript This may be the first contribution from a beginner, any kind of help will be welcomed! Regards, -- Fred Le Meur (fred1m)
Bug#965356: RFP: ProcMon -- Process monitor by Microsoft
Package: procmon Severity: wishlist Package name: ProcMon URL: https://github.com/microsoft/ProcMon-for-Linux/ License: MIT
Bug#965355: transition: ace
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, Another transition for 'ace' please. Small transition with only two affected packages: diagnostics, ivtools. ivtools builds fine with ace 6.5.10+dfsg-1 version in experimental. diagnostics already has a FTBFS (#964631) on it and so I could not verify if there is any impact on it. The autogenerated ben tracker looks good. Please consider 'ace' for transition. Thanks in advance. -- Regards Sudip
Bug#964078: Error during setup, bad file location
heh yeah, I meant it was paraview upstream that was forcing us to use the funny location. It's paraview that we (with you) have been getting to change. Debian has paraview 5.7.0 which is still looking in /usr/bin/plugins. We'll be able to clear it up in meshio-tools once paraview is upgraded. Drew On 2020-07-20 15:39, Nico Schlömer wrote: Upstream dev here. The location is ``` share/paraview-5.8/plugins ``` now, that's already for 4.0.16. Cheers, Nico On Mon, Jul 20, 2020 at 9:03 AM Drew Parsons wrote: Package: meshio-tools Followup-For: Bug #964078 Thanks for your report. Looks like the symlink might not be created in time for the installation scripts, will have to look into it. It is a funny location. Upstream was using it so. We're working with them to change it to a more appropriate location in /usr/lib or /usr/share. Drew
Bug#965354: bcolz: FTBFS with newer python3-numpydoc
Source: bcolz
Version: 1.2.1+ds2-5
Severity: serious
Justification: FTBFS
Hi,
bcolz FTBFS on amd64 with an updated version of python3-numpydoc.
Here is the tail of the build log. The error seems to originate
during the build of the documentation:
PYTHONPATH=/<>/.pybuild/cpython3_3.8_bcolz/build \
http_proxy='127.0.0.1:9' sphinx-build -N docs/
debian/bcolz-doc/usr/share/doc/bcolz-doc/html/
Running Sphinx v2.4.3
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 7 source files that are out of date
updating environment: [new config] 7 added, 0 changed, 0 removed
reading sources... [ 14%] defaults
reading sources... [ 28%] index
reading sources... [ 42%] install
reading sources... [ 57%] intro
reading sources... [ 71%] opt-tips
reading sources... [ 85%] reference
Exception occurred:
File "/usr/lib/python3/dist-packages/numpydoc/docscrape.py", line 324, in
_parse_see_also
raise ParseError("%s is not a item name" % line)
numpydoc.docscrape.ParseError: cparams.setdefaults() is not a item name in
"cparams(clevel=None, shuffle=None, cname=None, quantize=None)\n\nClass to host
parameters for compression and other filters.\n\nParameters\n--\nclevel
: int (0 <= clevel < 10)\nThe compression level.\nshuffle : int\nThe
shuffle filter to be activated. Allowed values are\nbcolz.NOSHUFFLE (0),
bcolz.SHUFFLE (1) and bcolz.BITSHUFFLE (2). The\ndefault is
bcolz.SHUFFLE.\ncname : string ('blosclz', 'lz4', 'lz4hc', 'snappy', 'zlib',
'zstd')\nSelect the compressor to use inside Blosc.\nquantize : int (number
of significant digits)\nQuantize data to improve (lossy) compression. Data
is quantized using\nnp.around(scale*data)/scale, where scale is 2**bits,
and bits is\ndetermined from the quantize value. For example, if
quantize=1, bits\nwill be 4. 0 means that the quantization is
disabled.\n\nIn case some of the parameters are not passed, they will be\nset
to a default (see `setdefaults()` method).\n\nSee
also\n\ncparams.setdefaults()"
The full traceback has been saved in /tmp/sphinx-err-ec7z35mu.log, if you want
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message
can be provided next time.
A bug report can be filed in the tracker at
. Thanks!
make[1]: Leaving directory '/<>'
make[1]: *** [debian/rules:22: override_dh_auto_install] Error 2
make: *** [debian/rules:17: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit
status 2
Bug#964078: Error during setup, bad file location
Upstream dev here. The location is ``` share/paraview-5.8/plugins ``` now, that's already for 4.0.16. Cheers, Nico On Mon, Jul 20, 2020 at 9:03 AM Drew Parsons wrote: > > Package: meshio-tools > Followup-For: Bug #964078 > > Thanks for your report. Looks like the symlink might not be created > in time for the installation scripts, will have to look into it. > > It is a funny location. Upstream was using it so. We're working with > them to change it to a more appropriate location in /usr/lib or > /usr/share. > > Drew >
Bug#965349: regression in dh_installchangelogs or dh_missing causes fatal error when installing upstream changelog from debian/tmp
Nicholas D Steeves: > Package: debhelper > Version: 13.2 > Severity: normal > > Steps to reproduce: > > override_dh_installchangelogs: > mkdir -p debian/tmp > generate-or-convert-changelog-here >> debian/tmp/changelog > dh_installchangelogs debian/tmp/changelog > > Result: > > dh_missing: warning: changelog exists in debian/tmp but is not installed > to anywhere > dh_missing: error: missing files, aborting > > Meanwhile the upstream changelog has been correction installed to each > of the debian/bin-pkg/u/s/doc/changelog.gz locations. Debhelper 12 > was definitely good, and I'm not sure if the regression was introduced > in 13, 13.1, or 13.2. > > f3ce4ba3a5e2f9515b0ebe1940aed81ce9a92c49 looks like a possible culprit, > but that's just a guess. > > Falling back to debhelper-compat 12 avoids triggering this bug. I > hope noting this fact makes it easier to track down, because it means > that the bug is in a branch specific to ≥ debhelper-compat 13. > > Regards, > Nicholas > Hi Nicholas, Thanks for filing the bug. I suspect that the reason that falling back to compat 12 works is because it downgrades the issue to a warning (compat 12 defaulting to --list-missing vs. compat 13 defaulting to --fail-missing). Can you confirm that finding? Because then it is probably just the new default and not a regression. Obviously, that still leaves finding a solution to the problem, but for starters lets confirm whether or not this is a regression. Thanks, ~Niels
Bug#964078: Error during setup, bad file location
Package: meshio-tools Followup-For: Bug #964078 Thanks for your report. Looks like the symlink might not be created in time for the installation scripts, will have to look into it. It is a funny location. Upstream was using it so. We're working with them to change it to a more appropriate location in /usr/lib or /usr/share. Drew
Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Source: node-babel7
Version: 7.10.5+~cs65.71.38-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=node-babel7=all=7.10.5%2B~cs65.71.38-2=1595148206=0
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f node_modules/@babel/code-frame
cd babel-plugin-dynamic-import-node && babeljs-7 src --out-dir lib
ReferenceError: /<>/babel-plugin-dynamic-import-node/src/index.js:
isArray is not defined
at /usr/share/nodejs/lodash/_baseOrderBy.js:24:7
at arrayMap (/usr/share/nodejs/lodash/_arrayMap.js:19:21)
at baseOrderBy (/usr/share/nodejs/lodash/_baseOrderBy.js:23:17)
at /usr/share/nodejs/lodash/sortBy.js:48:10
at apply (/usr/share/nodejs/lodash/_apply.js:18:25)
at /usr/share/nodejs/lodash/_overRest.js:35:12
at PluginPass.exit
(/usr/share/nodejs/@babel/core/lib/transformation/block-hoist-plugin.js:58:43)
at newFn (/usr/share/nodejs/@babel/traverse/lib/visitors.js:175:21)
at NodePath._call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:42:17) {
code: 'BABEL_TRANSFORM_ERROR'
}
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
