Bug#949348: #949348: libnet: example Makefile includes build paths and binary paths
Hi.
I am curious if you're still maintaining "libnet" in Debian, and if you
saw the bug I reported last year:
https://bugs.debian.org/949348
I am sending this message to your email directly in case there is some
technical difficulty relaying messages from the debian bug tracking
system...
Thanks!
live well,
vagrant
On 2021-01-01, Vagrant Cascadian wrote:
> On 2020-01-19, Vagrant Cascadian wrote:
>> I'd suggest simply removing the Makefile, as it is not functional, or
>> alternately, sanitizing with the attached patch to debian/rules.
>
> Patch attached which removes the Makefile instead, which should fix both
> the usrmerge and build path bugs than the previous patches.
>
> I would like to see this land in bullseye if possible, would you
> consider uploading soon, or be amenable to an NMU?
>
>
> live well,
> vagrant
> From d8e38005ce5c084e33212c399968410661fcb07f Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian
> Date: Fri, 1 Jan 2021 21:32:55 +
> Subject: [PATCH] Remove example Makefile. (Closes: #949348, #949346)
>
> The example Makefile embeds build paths that are not likely to be
> present on the end-user system, and possibly binary paths that may be
> different on a usrmerge system, thus requiring the end-user to
> regenerate the file from Makefile.in or Makefile.am anyway.
> ---
> debian/rules | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/debian/rules b/debian/rules
> index 578a6af..b73692b 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -14,3 +14,6 @@ CFLAGS += -Wno-uninitialized -Wno-unused-but-set-variable
> DEB_INSTALL_CHANGELOGS_libnet1 := doc/CHANGELOG
> DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
>
> +binary-install/libnet1-doc::
> + # Remove example Makefile which embeds build paths and binary paths
> + rm -f
> $(CURDIR)/debian/libnet1-doc/usr/share/doc/libnet1-doc/html/Makefile
> --
> 2.30.0
signature.asc
Description: PGP signature
Bug#979398: reportbug: mnemosyne package should probably have python3-gtts as a dependency
Package: mnemosyne Version: 2.7.3+ds1-1 Severity: minor Running the mnemosyne command (when the mnemosyne package is installed, but the python3-gtts package is not) on one of the installations I tested this situation on gives the following output.: Warning: Could not import OpenGL. Might cause a black screen on some Linux distributions. Try installing python3-opengl in that case. Log body: An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 277, in mnemosyne.initialise(data_dir=data_dir, filename=filename, File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 400, in initialise self.register_components() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 465, in register_components importlib.import_module(module_name), class_name) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist- packages/mnemosyne/libmnemosyne/pronouncers/google_pronouncer.py", line 5, in from gtts import gTTS ModuleNotFoundError: No module named 'gtts' An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 277, in mnemosyne.initialise(data_dir=data_dir, filename=filename, File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 400, in initialise self.register_components() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 465, in register_components importlib.import_module(module_name), class_name) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist- packages/mnemosyne/libmnemosyne/pronouncers/google_pronouncer.py", line 5, in from gtts import gTTS ModuleNotFoundError: No module named 'gtts' An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 277, in mnemosyne.initialise(data_dir=data_dir, filename=filename, File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 400, in initialise self.register_components() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 465, in register_components importlib.import_module(module_name), class_name) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist- packages/mnemosyne/libmnemosyne/pronouncers/google_pronouncer.py", line 5, in from gtts import gTTS ModuleNotFoundError: No module named 'gtts' After installing the python3-gtts package, the mnemosyne command launches the Mnemosyne program as intended. I was able to produce this on two separate installations. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mnemosyne depends on: ii libjs-sphinxdoc 3.4.1-1 ii libqt5sql5-sqlite 5.15.2+dfsg-2 ii python3 3.9.1-1 ii python3-cheroot 8.5.1+ds1-1 ii python3-cherrypy3 8.9.1-7 ii python3-matplotlib 3.3.2-2+b1 ii python3-pil 8.0.1-1+b1 ii python3-pyqt5 5.15.2+dfsg-1+b1 ii python3-pyqt5.qtsql 5.15.2+dfsg-1+b1 ii python3-pyqt5.qtwebchannel 5.15.2+dfsg-1+b1 ii python3-pyqt5.qtwebengine 5.15.2-1 ii python3-webob 1:1.8.6-1.1 mnemosyne recommends no packages. mnemosyne suggests no packages. -- no debconf information
Bug#979399: RFS: mrboom/5.2+ds-1 -- 8 player Bomberman
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mrboom": * Package name: mrboom Version : 5.2+ds-1 Upstream Author : Remdy Software * URL : http://mrboom.mumblecore.org/ * License : GPL-3+, Zlib, MIT * Vcs : https://salsa.debian.org/games-team/mrboom Section : games It builds those binary packages: mrboom - 8 player Bomberman To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mrboom/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mrboom/mrboom_5.2+ds-1.dsc Changes since the last upload: mrboom (5.2+ds-1) unstable; urgency=medium . * New upstream version. * d/watch: - drop template part. - added filemangle for repacking. * d/copyright: - updated match. - added Files-Excluded field. Regards, -- Gürkan Myczko
Bug#979400: ITP: drs -- DRS4 Evaluation Board software
Package: wnpp Severity: wishlist Owner: Gürkan Myczko X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: drs Version : 5.0.5 Upstream Author : Stefan Ritt * URL : https://www.psi.ch/en/drs/software-download * License : GPL-3-only Description : DRS4 Evaluation Board software The DRS4 chip is a full custom Integrated Circuit developed at PSI, Switzerland. It contains a switched capacitor array (SCA) with 1024 cells, capable of digitizing eight analog signals with high speed (6 GSPS) and high accuracy (11.5 bit SNR) on a single chip. This web site contains the chip documentation and software (firmware, drivers, applications) needed in order to work with the chip or the chip evaluation board. . This is software that is only useful if you also get the hardware for it. You can already play with it, find it at the usual place (sid.e.c or mentors.d.n)
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
On 5.1.2021 9.29, Жохов Александр wrote: Good afternoon, sorry for the bad english. Faced a similar problem. Catalina ca logs 2021-01-05 01:07:32 [main] WARNING: Failed to scan [file:/usr/share/java/el-api-3.0.jar] from classloader hierarchy java.io.IOException: > Caused by: java.nio.file.NoSuchFileException: /usr/share/java/el-api-3.0.jar Figure out which jar is trying to search that and we'd at least get rid of this error. dogtag 10.10.2-1 at least should use the correct el-api from tomcat9 now, but there's probably some other package which still doesn't. Syslog Jan 5 01:08:09 srv-freeipa01 ns-slapd[4070]: [05/Jan/2021:01:08:09.503254206 +0300] - ERR - ipalockout_getpolicy - [file ipa_lockout.c, line 294]: Failed to retrieve entry "cn=global_policy,cn=DOMAIN.LOCAL,cn=kerberos,dc=domain,dc=linux": 32 Jan 5 01:08:09 srv-freeipa01 certmonger[5797]: 2021-01-05 01:08:09 [5797] Running enrollment/cadata helper "/usr/lib/certmonger/dogtag-ipa-renew-agent-submit". Jan 5 01:08:09 srv-freeipa01 ns-slapd[4070]: [05/Jan/2021:01:08:09.506826816 +0300] - ERR - ipalockout_getpolicy - [file ipa_lockout.c, line 294]: Failed to retrieve entry "cn=global_policy,cn= DOMAIN.LOCAL,cn=kerberos,dc=domain,dc=linux": 32 Jan 5 01:08:09 srv-freeipa01 certmonger[5792]: Error opening "/etc/apache2/nssdb/pwdfile.txt": No such file or directory. That certdb isn't used anymore, so I don't know how you got that. -- t
Bug#975747: this is actually fixed
Control: fixed -1 1:10.0.0+r36-1 Control: fixed -1 1:10.0.0+r36-2 Control: fixed -1 1:10.0.0+r36-3 Control: fixed -1 1:10.0.0+r36-4
Bug#977912: This is due to aapt's linking error.
Control: reassign -1 aapt Control: merge 977023 977912 This is due to aapt's linking error. The fdroidserver tests rely on aapt.
Bug#950626: dcut: Detect which queue commands will be rejected by server, before writing them
Control: severity -1 wishlist Control: retitle -1 dcut: Detect which queue commands will be rejected by server, before writing them Control: tags -1 + moreinfo Control: outlook -1 0 The channel to upload commands to the server has no way for those errors to come back to the ‘dcut’ program as it runs. Is this something the uploading program can detect, without connection to the server? How, exactly? On 04-Feb-2020, Ben Finney wrote: > Control: tags -1 + moreinfo > > On 04-Feb-2020, Mark Brown wrote: > > I would expect that dcut would detect any errors that will not be > > being reported by ftp-master. > > My understanding is that the channel to upload commands to the > server has no way for those errors to come back to the ‘dcut’ > program as it runs. Is this something the uploading program can > detect? As described, this is not an error in ‘dcut’ operation so I'm adjusting severity to show this is a hoped-for feature. I'm setting the outlook on this report to invite feedback if someone can specify exactly what behaviour would implement this feature. -- \ “If sharing a thing in no way diminishes it, it is not rightly | `\ owned if it is not shared.” —Augustine of Hippo (354–430 CE) | _o__) | Ben Finney signature.asc Description: PGP signature
Bug#867280: dput: mentors.debian.net should allow UNRELEASED packages
Control: tags -1 - patch + moreinfo On 05-Jul-2017, Tom Fitzhenry wrote: > mentors.debian.net allows UNRELEASED packages[0], but the mentors.debian.net > block in /etc/dput.cf does not allow UNRELEASED packages. For the mentors.debian.net queue, it seems best to strictly limit the target distributions to only those that are correct for that queue. Would this be appropriate: allowed_distributions = (UNRELEASED|experimental|unstable) -- \“I have a microwave fireplace in my house. The other night I | `\ laid down in front of the fire for the evening in two minutes.” | _o__) —Steven Wright | Ben Finney signature.asc Description: PGP signature
Bug#979371: nis should depend on libnss-nis
tags 979371 + pending severity 979371 minor quit libnss-nis should be a Recommends for current nis or prospectively for ypbind-mt. On Tue, Jan 05, 2021 at 10:05:35PM +0100, Thomas Lange wrote: Package: nis Version: 3.17.1-9+b1 In bullseye the nis function of libc was moved to a new package, called libnss-nis. I think the nis package should depend or recommend libnss-nis. -- regards Thomas -- Francesco P. Lovergine
Bug#977701: gitlab: Missing assets, breaking some functionalities
>Unfortunately updating css-loader and postcss did not fix this issue :( Can I somehow help to untangle this issue? Are there any workarounds maybe? Best, Maximilian
Bug#971429: simde: autopkgtest failure on armhf
Control: reopen -1 Hi Maintainer The autopkgtests of simde 0.7.0-2 still fail on armhf in what looks to me to be the same way. Regards Graham
Bug#977701: gitlab: Missing assets, breaking some functionalities
On Wed, Jan 6, 2021 at 10:24 am, Maximilian Stein wrote: >Unfortunately updating css-loader and postcss did not fix this issue :( Can I somehow help to untangle this issue? Are there any workarounds maybe? One things I can think of is to get gitlab-rake gitlab:assets:compile working (we run only part of it in rake-tasks.sh, I'm not sure if the steps we don't run is causing the issues). Another possibility is to include gitaly-git2go binary in the gitaly package. gitaly now seems to be using its own version of git2go for merges. Best, Maximilian
Bug#979401: dh_auto_test: would be good to check for "nocheck" in DEB_BUILD_PROFILES as well
Package: debhelper Version: 13.3.1 Severity: wishlist With the increasing prevalence of DEB_BUILD_PROFILES, it would seem to make sense for dh_auto_test to skip any tests if "nocheck" appears in either DEB_BUILD_OPTIONS or DEB_BUILD_PROFILES. Otherwise, it is very easy to end up with a situation where a package fails to build if DEB_BUILD_PROFILES=nocheck but DEB_BUILD_OPTIONS is empty. To guard against this is every package by conditionally overriding dh_auto_make is silly; it would be much better to do it centrally. Best wishes, Julian
Bug#979402: libiddawc0.9: should link json and gnutls
Package: libiddawc0.9 Version: 0.9.7-1 Severity: normal X-Debbugs-Cc: sramac...@debian.org During the build of iddawc, dpkg-shlibdeps produces the following warnings: | dpkg-shlibdeps: warning: symbol json_object_iter_next used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_object_iter used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_loads used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_deep_copy used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_string used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_array_size used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_object used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_object_set_new used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol gnutls_fingerprint used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: symbol json_pack used by debian/libiddawc0.9/usr/lib/x86_64-linux-gnu/libiddawc.so.0.9.7 found in none of the libraries | dpkg-shlibdeps: warning: 11 other similar warnings have been skipped (use -v to see them all) Please ensure that libiddawc0.9 is linked with all shared libraries it requires to function properly. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#979403: skopeo: Error loading trust policy: open /etc/containers/policy.json: no such file or directory
Package: skopeo Version: 1.2.0+dfsg1-2 Severity: important Dear Maintainer, I noticed that if skopeo is installed without buildah, a simple command such as: skopeo copy docker://busybox oci:busybox fails with: FATA[] Error loading trust policy: open /etc/containers/policy.json: no such file or directory as mentioned here: https://github.com/containers/skopeo/issues/181 this can be worked around by executing skopeo with a command-line option: skopeo --insecure-policy copy docker://busybox oci:busybox But /etc/containers/policy.json is installed by buildah, should skopeo recommend buildah ? Or should /etc/containers/policy.json be installed by a new package from which both skopeo and buildah depend ? Thanks, Paolo -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages skopeo depends on: ii libc6 2.31-6 ii libdevmapper1.02.1 2:1.02.173-1 ii libgpgme11 1.14.0-1+b2 skopeo recommends no packages. skopeo suggests no packages. -- no debconf information
Bug#933940: lxqt-policykit: Messagebox for auth info is modal, which is user-unfriendly
Package: lxqt-policykit Version: 0.14.1-1 Followup-For: Bug #933940 Hi Jörg, Thanks for reporting this and provide solution. However this is an upstream issue. Please open an issue in upstream instead. I think they will be glad to see your merge request on github. Best regards, -Andrew
Bug#933939: lxqt-policykit: With two-factor auth the password is displayed in cleartext
Package: lxqt-policykit Version: 0.14.1-1 Followup-For: Bug #933939 Hi Jörg, Thanks for reporting this and provide solution. However this is an upstream issue. Please open an issue in upstream instead. I think they will be glad to see your merge request on github. Best regards, -Andrew
Bug#950782: closed by Debian FTP Masters (reply to Kartik Mistry ) (Bug#950782: fixed in recoll 1.28.3-1)
Dear Kartik and xiscu, On Wed, 06 Jan 2021 08:18:05 +, "Debian Bug Tracking System" wrote: > Changes: > recoll (1.28.3-1) unstable; urgency=low > . >* New upstream release. >* debian/control: > + Suggest python3-lz4 (Closes: #950782) ^^^ Shouldn't it better suggest python3-py7zr instead of python3-lz4 as xiscu pointed out in the e-mail? (Many thanks to xiscu for spotting the solution!) (Highlighted in Recoll's release notes: "Use py7zr in preference to pylzma for 7z archive indexing") Thanks a lot for working on the bug report, too! Best regards, Marcus pgpOowvRtzW82.pgp Description: OpenPGP digital signature
Bug#979350: Confirmation of G++/GCC bug on gentoo
The described compiler bug is reproducible on gentoo [0] (gcc-10.2.0-r5, that is patchlevel 6). So it is not a debian - specific bug [0] https://github.com/Return-To-The-Roots/s25client/issues/1327#issuecomment-755180727
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
Hello. >> 2021-01-05 01:07:32 [main] WARNING: Failed to scan >> [file:/usr/share/java/el-api-3.0.jar] from classloader hierarchy >> java.io.IOException: >> >> Caused by: java.nio.file.NoSuchFileException: >> /usr/share/java/el-api-3.0.jar >Figure out which jar is trying to search that and we'd at least get rid > of this error. dogtag 10.10.2-1 at least should use the correct el-api from > tomcat9 now, but there's probably some other package which still doesn't. There was no el-api-3.0.jar on my system for some reason I'm install libel-api-java. And also I installed libjemalloc2 and created a link ln -s /usr/lib/x86_64-linux-gnu/ /usr/lib/x86_64-linux-gnu/dirsrv/lib, because in the log I saw a message about the absence of the /usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2 Now in the log / var / lib / pki / pki-tomcat / ca / logs / debug I see an error 2021-01-06 12:18:33 [http-nio-8080-exec-15] WARNING: Certificate request deferred: defer request 2021-01-06 12:18:33 [http-nio-8080-exec-15] INFO: Updating certificate request 2021-01-06 12:18:34 [https-jsse-nio-8443-exec-3] INFO: Getting SSL client certificate. 2021-01-06 12:18:34 [https-jsse-nio-8443-exec-3] SEVERE: ReviewReqServlet: You did not provide a valid certificate for this operation You did not provide a valid certificate for this operation at com.netscape.cms.servlet.base.CMSServlet.getSSLClientCertificate(CMSServlet.java:843) at com.netscape.cms.servlet.base.CMSServlet.getSSLClientCertificate(CMSServlet.java:825) at com.netscape.cms.servlet.base.CMSServlet.authenticate(CMSServlet.java:1685) at com.netscape.cms.servlet.base.CMSServlet.authenticate(CMSServlet.java:1627) at com.netscape.cms.servlet.profile.ProfileReviewServlet.process(ProfileReviewServlet.java:120) at com.netscape.cms.servlet.base.CMSServlet.service(CMSServlet.java:494) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542)
Bug#979404: ITP: sass-stylesheets-neat -- lightweight and flexible Sass grid
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: sass-stylesheets-neat Version : 4.0.0 Upstream Author : thoughtbot, inc. * URL : https://neat.bourbon.io/ * License : Expat Programming Lang: Sass Description : lightweight and flexible Sass grid Neat is a lightweight and flexible Sass grid, which works well together with Bourbon and Bitters. . NB! The Neat project is no longer maintained; for new projects you are encouraged to instead use native CSS features like Grid and Flexbox. . Bourbon is a library of Sass mixins and functions that are designed to make you a more efficient style sheet author. . Sass makes CSS fun again. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. . Sass can be encoded in either of two formats - SASS and SCSS. These mixins are provided in SCSS format. This package will be maintained in the Sass team. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/1i+cACgkQLHwxRsGg ASGm7A//ReD9y6roQuebr+931VJfwGtBk2MPtOZvmdBpfOaYYQ6I0uoTTvEJmnCc hqmHYwlcg9k1apq5FvkxegEdmRojd+MXxtrNCuP1b5t5GrQkQaatnzwFPNKLI4cZ 6mH9YbV7n7PzJ1Wb4bDvXguuMuCJQK6LvHwFlWu6cplY7b0qRcEPk92l84VyFfjP Ihq6J0veLcJR8sDlIrbw9NXKOneXkakdL4oJD8jUYFCtpCoNQ3Nvv/M7XRoI8Juk /wWIQ+7p7Kmx6esupn/UGOuFAIVZI6SK4LvbCRMhObIR1Vi+umAMONco1gkUQME4 kJ2U9gPDyVKdeMbvayWK842awcK9MXkFtYAu9J13+Txu8ve4baEaKnpapLUoaLfz IzNjUOaG1CaLqiiNmAdB6Ab8lj0ooYFOzPDoG961E7hIpkB23YrIxb7QEMZfDVJK ZQC3r5YERi83TtSZSzRcXCS/JcYOIX+crcnBSTrew1OmxViBtB6clMf93zpjaCRV KljbIqSBXFIerI2ZrAdv8CZuza61wr7IrQi+Y/E6B0Nei5PCfc+gQm/N1+FsDNzj zumcFoppX2+cmQwYgFQrDIITjxUVAVqZv9c4i/vDa6O15uxe1Qyuyew/LJl3Q1Ch QRYVyaWdFFcKrBoATDGXwGM6FNybe8BamCrVRon4kzao1BGbDo4= =jyQv -END PGP SIGNATURE-
Bug#979405: emscripten: FTBFS: Fatal: globalBase must be set
Source: emscripten Version: 2.0.9~dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, emscripten/experimental FTBFS with [...] PATH="/build/emscripten-2.0.9~dfsg:$PATH" EM_CACHE="/build/emscripten-2.0.9~dfsg/debian/em_cache" emcc tests/hello_world.c shared:INFO: (Emscripten: Running sanity checks) cache:INFO: generating system library: libc.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libcompiler_rt.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libcompiler_rt.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libc++-noexcept.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc++-noexcept.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libc++abi-noexcept.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc++abi-noexcept.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libdlmalloc.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libdlmalloc.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libpthread_stub.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libpthread_stub.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libc_rt_wasm.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc_rt_wasm.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libsockets.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libsockets.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system asset: generated_struct_info.json... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/generated_struct_info.json" for subsequent builds) Fatal: globalBase must be set emcc: error: '/usr/bin/wasm-emscripten-finalize --detect-features --minimize-wasm-changes --dyncalls-i64 /tmp/tmplzjtvhxu.wasm -o /tmp/tmplzjtvhxu.wasm' failed (1) FAIL: Compilation failed!: ['emcc', '-D_GNU_SOURCE', '-o', '/tmp/tmplzjtvhxu.js', '/tmp/tmprdy33uqc.c', '-O0', '--memory-init-file', '0', '-Werror', '-Wno-format', '-s', 'BOOTSTRAPPING_STRUCT_INFO=1', '-s', 'WARN_ON_UNDEFINED_SYMBOLS=0', '-s', 'STRICT=1', '-s', 'SINGLE_FILE=1', '-Wno-error=version-check', '-Wno-deprecated'] make[1]: *** [debian/rules:260: override_dh_auto_test] Error 1 make[1]: Leaving directory '/build/emscripten-2.0.9~dfsg' make: *** [debian/rules:244: binary] Error 2 Andreas emscripten_2.0.9~dfsg-1.log.gz Description: application/gzip
Bug#979406: lilypond-doc: missing Breaks+Replaces: lilypond-doc-html (<< 2.21)
Package: lilypond-doc Version: 2.21.82-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../lilypond-doc_2.21.82-1~exp1_all.deb ... Unpacking lilypond-doc (2.21.82-1~exp1) over (2.20.0-4) ... dpkg: error processing archive /var/cache/apt/archives/lilypond-doc_2.21.82-1~exp1_all.deb (--unpack): trying to overwrite '/usr/share/doc/lilypond/html/Documentation/00/lily-02e0a159.png', which is also in package lilypond-doc-html 2.20.0-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/lilypond-doc_2.21.82-1~exp1_all.deb According to this changelog entry * Adjust debian/lilypond-doc.install and debian/rules so that the PNG files stay with lilypond-doc package the .png files seem to have been moved intentionally from -doc-html to -doc cheers, Andreas lilypond-doc-html=2.20.0-4_lilypond-doc=2.21.82-1~exp1.log.gz Description: application/gzip
Bug#979367: kodi: segfault when shutting down
> Another thing that bothers me is that you mix dmo and official Debian > repository. yes these are leftovers... I now purged all dmo packages and reinstalled them from debian testing/sid. > > Can you please backup your Kodi profile and reinstall Kodi with only > dependencies from official Debian archive? Should an apt purge --autoremove && apt install do the same? However, on my cleaned system the segfault persists. I also tried to change the locale from de_AT.UTF8 to en_US.UTF8 but it does not matter. Sebastian
Bug#864082: fontconfig: please make the cache files reproducible
Dear maintainers, On Sun, 13 Sep 2020 08:13:06 - "Chris Lamb" wrote: > Friendly ping on this? I'd like to send another ping about this. This bug is affecting my package mmdebstrap so I'd love to see it fixed. Thanks! cheers, josch signature.asc Description: signature
Bug#979367: kodi: segfault when shutting down
Hi Sebastian, > yes these are leftovers... I now purged all dmo packages and reinstalled them > from debian testing/sid. Great, thanks! > Should an apt purge --autoremove && apt install do the same? Yes, it should: apt --purge autoremove kodi* && apt install kodi > However, on my cleaned system the segfault persists. > I also tried to change the locale from de_AT.UTF8 to en_US.UTF8 but it does > not > matter. I will build kodi against testing/amd64 today with a patch introducing null checks in the PythonLanguageHook and send you the link to the resulting deb file. In the meantime, can you please upload the corefile? I want to check if pointer to PyDict is null or not. If it is nulled, then it is a deference bug but if it is non-null then we encountered an UaF. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 6 січня 2021 р. 10:36:56 UTC, Sebastian Bachmann написав(-ла): >> Another thing that bothers me is that you mix dmo and official Debian >> repository. > >yes these are leftovers... I now purged all dmo packages and reinstalled them >from debian testing/sid. > >> >> Can you please backup your Kodi profile and reinstall Kodi with only >> dependencies from official Debian archive? > >Should an apt purge --autoremove && apt install do the same? > >However, on my cleaned system the segfault persists. >I also tried to change the locale from de_AT.UTF8 to en_US.UTF8 but it does not >matter. > >Sebastian
Bug#979366: openvswitch-common: openswitch-common uninstallable on non-amd64
Contro: found -1 2.13.0+dfsg1-15 On Tue, 05 Jan 2021 21:48:58 + Debian FTP Masters wrote: > We believe that the bug you reported is fixed in the latest version of > openvswitch, which is due to be installed in the Debian FTP archive. > openvswitch (2.13.0+dfsg1-15) unstable; urgency=medium > . >* Fix installing OVS alternatives on non-amd64 arch (Closes: #979366). I’m afraid it’s not working since dpkg-architecture is in dpkg-dev: root@9cecd1b74b8f:/# apt update Get:1 http://deb.debian.org/debian unstable InRelease [153 kB] Get:2 http://deb.debian.org/debian unstable/main amd64 Packages [8565 kB] Fetched 8718 kB in 2s (4485 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 43 packages can be upgraded. Run 'apt list --upgradable' to see them. root@9cecd1b74b8f:/# apt policy openvswitch-common openvswitch-common: Installed: (none) Candidate: 2.13.0+dfsg1-15 Version table: 2.13.0+dfsg1-15 500 500 http://deb.debian.org/debian unstable/main amd64 Packages root@9cecd1b74b8f:/# apt policy dpkg-dev dpkg-dev: Installed: (none) Candidate: 1.20.5 Version table: 1.20.5 500 500 http://deb.debian.org/debian unstable/main amd64 Packages root@9cecd1b74b8f:/# apt install openvswitch-common Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: bzip2 ca-certificates file krb5-locales libevent-2.1-7 libexpat1 libgdbm-compat4 libgdbm6 libgpm2 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmagic-mgc libmagic1 libncursesw6 libnsl2 libperl5.32 libpython3-stdlib libpython3.9-minimal libpython3.9-stdlib libreadline8 libsqlite3-0 libssl1.1 libtinfo6 libtirpc-common libtirpc3 libunbound8 mailcap media-types mime-support netbase openssl perl perl-base perl-modules-5.32 python3 python3-minimal python3-six python3.9 python3.9-minimal readline-common xz-utils Suggested packages: bzip2-doc gdbm-l10n gpm krb5-doc krb5-user sensible-utils ethtool perl-doc libterm-readline-gnu-perl | libterm-readline-perl-perl make libtap-harness-archive-perl python3-doc python3-tk python3-venv python3.9-venv python3.9-doc binutils binfmt-support readline-doc The following NEW packages will be installed: bzip2 ca-certificates file krb5-locales libevent-2.1-7 libexpat1 libgdbm-compat4 libgdbm6 libgpm2 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmagic-mgc libmagic1 libncursesw6 libnsl2 libperl5.32 libpython3-stdlib libpython3.9-minimal libpython3.9-stdlib libreadline8 libsqlite3-0 libssl1.1 libtirpc-common libtirpc3 libunbound8 mailcap media-types mime-support netbase openssl openvswitch-common perl perl-modules-5.32 python3 python3-minimal python3-six python3.9 python3.9-minimal readline-common xz-utils The following packages will be upgraded: libtinfo6 perl-base 2 upgraded, 43 newly installed, 0 to remove and 41 not upgraded. Need to get 22.5 MB of archives. After this operation, 94.2 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://deb.debian.org/debian unstable/main amd64 perl-base amd64 5.32.0-6 [1627 kB] Get:2 http://deb.debian.org/debian unstable/main amd64 perl-modules-5.32 all 5.32.0-6 [2820 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 libgdbm6 amd64 1.18.1-5.1 [64.4 kB] Get:4 http://deb.debian.org/debian unstable/main amd64 libgdbm-compat4 amd64 1.18.1-5.1 [44.4 kB] Get:5 http://deb.debian.org/debian unstable/main amd64 libperl5.32 amd64 5.32.0-6 [4105 kB] Get:6 http://deb.debian.org/debian unstable/main amd64 perl amd64 5.32.0-6 [293 kB] Get:7 http://deb.debian.org/debian unstable/main amd64 libssl1.1 amd64 1.1.1i-1 [1551 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 libpython3.9-minimal amd64 3.9.1-1 [799 kB] Get:9 http://deb.debian.org/debian unstable/main amd64 libexpat1 amd64 2.2.10-1 [96.9 kB] Get:10 http://deb.debian.org/debian unstable/main amd64 python3.9-minimal amd64 3.9.1-1 [1954 kB] Get:11 http://deb.debian.org/debian unstable/main amd64 python3-minimal amd64 3.9.1-1 [37.8 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 media-types all 1.1.0 [19.0 kB] Get:13 http://deb.debian.org/debian unstable/main amd64 mailcap all 3.68 [31.6 kB] Get:14 http://deb.debian.org/debian unstable/main amd64 mime-support all 3.66 [10.9 kB] Get:15 http://deb.debian.org/debian unstable/main amd64 libtinfo6 amd64 6.2+20201114-2 [341 kB] Get:16 http://deb.debian.org/debian unstable/main amd64 libncursesw6 amd64 6.2+20201114-2 [132 kB] Get:17 http://deb.debian.org/debian unstable/main amd64 libkrb5support0 amd64 1.18.3-4 [65.1 kB] Get:18 http://deb.debian.org/debian unstable/main amd64 libk5crypto3 amd64 1.18.3-4 [113 kB] Get:19 http://deb.debian.org/debian unstable/main amd64 libkeyutils1 amd64 1.6.1-2 [15.4 kB] Get:20 http://deb.debian.org/debian unstable/main amd64 libkrb5-3 amd64 1.18.3-4 [362 kB] Get:21 http://deb.debian.org/de
Bug#979407: amd64-microcode: Amd64 microcode is not being loaded by the kernel from early initramfs.
Package: amd64-microcode Version: 3.20191218.1 Severity: normal On boot, the cpus are reported as having the following microcode version by the kernel: microcode: CPU0: patch_level=0x0800820c But this is not the latest version of the microcode, which is 0x800820d & if I trigger a microcode load from the shell with echo 1 > /sys/devices/system/cpu/microcode/reload after booting then the microcode is updated to that newer version. I have checked & the initramfs does contain an uncompressed cpio archive containing the microcode file kernel/x86/microcode/AuthenticAMD.bin as expected. So either the kernel is not seeing this, or for some reason it does not contain the latest microcode version, despite that latest version being the one loaded from /lib/firmware/amd64-microcode when triggered post-boot. It would be nice to sort this out! Any suggestons as to where to start? cheers, Phil Armstrong -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled amd64-microcode depends on no packages. Versions of packages amd64-microcode recommends: ii initramfs-tools 0.139 amd64-microcode suggests no packages. -- no debconf information
Bug#971309: ansible: diff for NMU version 2.9.16+dfsg-1.1
Control: tags 971309 + patch
Control: tags 971309 + pending
Dear maintainer,
I've prepared an NMU for ansible (versioned as 2.9.16+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru ansible-2.9.16+dfsg/debian/changelog ansible-2.9.16+dfsg/debian/changelog
--- ansible-2.9.16+dfsg/debian/changelog 2020-12-16 20:27:46.0 +0100
+++ ansible-2.9.16+dfsg/debian/changelog 2021-01-06 11:56:22.0 +0100
@@ -1,3 +1,11 @@
+ansible (2.9.16+dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: Replace python3-crypto with python3-cryptography (Closes:
+#971309). The cryptography based backend is the default crypto backend.
+
+ -- Sebastian Ramacher Wed, 06 Jan 2021 11:56:22 +0100
+
ansible (2.9.16+dfsg-1) unstable; urgency=medium
* New upstream release
diff -Nru ansible-2.9.16+dfsg/debian/control ansible-2.9.16+dfsg/debian/control
--- ansible-2.9.16+dfsg/debian/control 2020-09-09 13:35:17.0 +0200
+++ ansible-2.9.16+dfsg/debian/control 2021-01-06 11:55:12.0 +0100
@@ -6,7 +6,7 @@
Build-Depends: debhelper (>= 12~),
dh-python,
python3-all,
- python3-crypto,
+ python3-cryptography,
python3-docutils,
python3-jinja2,
python3-nose,
@@ -29,7 +29,7 @@
Depends: ${misc:Depends},
${python3:Depends},
openssh-client | python3-paramiko (>= 2.6.0),
- python3-crypto,
+ python3-cryptography,
python3-distutils,
python3-dnspython,
python3-httplib2,
@@ -37,7 +37,6 @@
python3-netaddr,
python3-yaml
Recommends: python3-argcomplete,
-python3-cryptography,
python3-jmespath,
python3-kerberos,
python3-libcloud,
signature.asc
Description: PGP signature
Bug#979408: qpdfview: Cannot create annotation
Package: qpdfview Version: 0.4.18-4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I opened a djvu file * What exactly did you do (or not do) that was effective (or ineffective)? According to the documentation, either ctrl-a and then dragging a box or ctrl whilst dragging a box should present an option to create either an annotation or highlight the region. * What was the outcome of this action? This option never appears. * What outcome did you expect instead? I expected to be able to create an annotation. *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qpdfview depends on: ii hicolor-icon-theme 0.17-2 ii libc62.31-6 ii libcups2 2.3.3op1-3 ii libgcc-s110.2.1-3 ii libqt5concurrent55.15.2+dfsg-2 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus5 5.15.2+dfsg-2 ii libqt5gui5 5.15.2+dfsg-2 ii libqt5printsupport5 5.15.2+dfsg-2 ii libqt5sql5 5.15.2+dfsg-2 ii libqt5sql5-sqlite5.15.2+dfsg-2 ii libqt5svg5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libstdc++6 10.2.1-3 ii libsynctex2 2020.20200327.54578-5 ii qpdfview-pdf-poppler-plugin 0.4.18-4 Versions of packages qpdfview recommends: ii qpdfview-djvu-plugin 0.4.18-4 ii qpdfview-ps-plugin 0.4.18-4 ii qpdfview-translations 0.4.18-4 qpdfview suggests no packages. -- no debconf information
Bug#978733: Runs env both inside and outside the chroot for the same variables
Hi, Quoting Josh Triplett (2020-12-31 01:56:47) > mmdebstrap appears to be running commands like the following: > > env --unset=APT_CONFIG --unset=TMPDIR /usr/sbin/chroot /path/to/targetdir env > --unset=TMPDIR dpkg --install > > Running env both inside and outside of the chroot seems unnecessary. > chroot will not set TMPDIR, so the internal invocation of env can be > dropped; it would be nice to not count on "env" existing inside the > chroot. funnily, I was investigating this situation already last december but then didn't change anything because I didn't see a way to have a working chroot without coreutils or busybox. Thus, I didn't make the change. Do you have a scenario where the chroot actually doesn't have env? Thanks! cheers, josch signature.asc Description: signature
Bug#979367: kodi: segfault when shutting down
Hi! On Wed, Jan 06, 2021 at 10:49:34AM +, Vasyl Gello wrote: > I will build kodi against testing/amd64 today with a patch introducing null > checks in the PythonLanguageHook > and send you the link to the resulting deb file. In the meantime, can you > please upload the corefile? I want to check > if pointer to PyDict is null or not. If it is nulled, then it is a deference > bug but if it is non-null then we encountered an UaF. Great, thank you! I set `ulimit -S -c unlimited` and pressed shutdown. I can see that a core file is generated in /home/kodi but as soon as the kodi crashlog is written, the core file is removed. Do I need to enable something so that the core file is not deleted? I ran `find / -name core` but there seems to be no core file anywhere... It looks like that kodi is eating the file, see /usr/bin/kodi line 113. Is there a method to keep the core file (or is the only way to comment out the rm?) Sebastian
Bug#979408: qpdfview: Cannot create annotation
This seems to only affect djvu documents. With PDFs, it works as advertised. OpenPGP_signature Description: OpenPGP digital signature
Bug#926242: [rb-general] Bug#926242: jenkins.debian.org: Please test reproducibility status of Debian Installer images
Chris Lamb wrote: > > I've made an initial step of taking my patch from: > > > > https://bugs.debian.org/926242#127 > > > > … and submitting it as a MR on salsa here: > > > > > > https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/13 Alas, this didn't seem to land in the Bullseye Alpha 3 release of d-i. Are we in time to merge it into the next alpha/beta, perhaps? :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#979367: kodi: segfault when shutting down
Hi! > Great, thank you! > I set `ulimit -S -c unlimited` and pressed shutdown. I can see that a core > file > is generated in /home/kodi but as soon as the kodi crashlog is written, the > core > file is removed. Do I need to enable something so that the core file is not > deleted? I ran `find / -name core` but there seems to be no core file > anywhere... > It looks like that kodi is eating the file, see /usr/bin/kodi line 113. > Is there a method to keep the core file (or is the only way to comment out the > rm?) Either to comment out that line or exploit a race condition: while [ ! -f /home/kodi/core.copy ]; do cp /home/kodi/core* /home/kodi/core.copy; done -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
Bug#979367: kodi: segfault when shutting down
On 2021-01-06 11:36:56 +0100, Sebastian Bachmann wrote: > > Another thing that bothers me is that you mix dmo and official Debian > > repository. > > yes these are leftovers... I now purged all dmo packages and reinstalled them > from debian testing/sid. > > > > > Can you please backup your Kodi profile and reinstall Kodi with only > > dependencies from official Debian archive? > > Should an apt purge --autoremove && apt install do the same? If you have other packages depending on ffmpeg or other libraries used by kodi, this won't help. Check https://wiki.debian.org/DebianMultimedia/FAQ on how to find all packages installed from DMO and then you'll need to reinstall them with the correct version. Cheers > > However, on my cleaned system the segfault persists. > I also tried to change the locale from de_AT.UTF8 to en_US.UTF8 but it does > not > matter. > > Sebastian > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#979369: libsdl2 FTBFS with DEB_BUILD_OPTIONS=nocheck
Pushed on git! thanks G.
Bug#975822: pyramid-jinja2: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13
Control: tags -1 patch fixed-upstream This is fixed with: https://github.com/horazont/aioxmpp/commit/5e375400a05b1cbec8b2459838ced2cdf57394b0 https://github.com/horazont/aioxmpp/commit/5e530636df162d8371d286b8fdaf284f4dd83f35 cu Adrian
Bug#979367: kodi: segfault when shutting down
On Wed, Jan 06, 2021 at 12:25:33PM +0100, Sebastian Ramacher wrote: > If you have other packages depending on ffmpeg or other libraries used > by kodi, this won't help. Check > https://wiki.debian.org/DebianMultimedia/FAQ on how to find all packages > installed from DMO and then you'll need to reinstall them with the > correct version. yes, I purged all -dmo packages from the system and reinstalled from debian testing/sid again. Sebastian
Bug#975822: pyramid-jinja2: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13
Control: tags -1 - patch fixed-upstream Sorry, this was the wrong bug number. On Wed, Jan 06, 2021 at 01:51:47PM +0200, Adrian Bunk wrote: > Control: tags -1 patch fixed-upstream > > This is fixed with: > https://github.com/horazont/aioxmpp/commit/5e375400a05b1cbec8b2459838ced2cdf57394b0 > https://github.com/horazont/aioxmpp/commit/5e530636df162d8371d286b8fdaf284f4dd83f35
Bug#975801: python-aioxmpp: FTBFS: TypeError: 'Lock' object is not iterable
Control: tags -1 patch fixed-upstream Fixed with: https://github.com/horazont/aioxmpp/commit/5e375400a05b1cbec8b2459838ced2cdf57394b0 https://github.com/horazont/aioxmpp/commit/5e530636df162d8371d286b8fdaf284f4dd83f35 cu Adrian
Bug#978722: nmu: nheko_0.7.2-3
On Wed, 30 Dec 2020 22:35:13 +0100 Sebastian Ramacher wrote: > This needs an upload of spdlog first. See #978471. Looks like that has happened now. Is there anything else blocking this?
Bug#213733: Bug#118023: nis: upgrade breaks postinst and service restart
I recently adopted NIS and trying to deal with old bugs. Note that nis package is going to be completely revamped with systemd use and split of the package, but this issue (and the merged 118023) seems still of interest. First of all, *current* ypbind is not able to bind automagically to a local ypserv if the loopback address is not set in /etc/yp.conf. I suspect that this issue would not be an issue at all if ypbind would connect an external server via -broadcast or its ip. Note that in order to use broadcast even in buster+ now it is mandatory using -r option in rpcbind, which is not the default. Current nis package still shows exactly this behavior at its first installation on a new box. But *now* the postinst does not fail at all, the ypbind goes in background and timeouts when broadcast fails, but it runs forever with RPC timeouts. This is the result of fresh install on buster: Setting up libtirpc3:amd64 (1.1.4-0.4) ... Setting up rpcbind (1.2.5-0.3+deb10u1) ... Created symlink /etc/systemd/system/multi-user.target.wants/rpcbind.service → /lib/systemd/system/rpcbind.service. Created symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket → /lib/systemd/system/rpcbind.socket. Setting up nis (3.17.1-3+b1) ... Progress: [ 90%] [#..] [... some minutes after ... ] Setting up nis (3.17.1-3+b1) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10) ... Processing triggers for systemd (241-7~deb10u5) ... So, the postinst now apparently is not failing at all even if syslog reports: Jan 6 10:22:30 buster nis[1039]: Setting NIS domainname to: localdomain. Jan 6 10:23:24 buster ypbind[1051]: broadcast: RPC: Timed out. Jan 6 10:24:18 buster ypbind[1051]: broadcast: RPC: Timed out. Jan 6 10:25:12 buster ypbind[1051]: broadcast: RPC: Timed out. Jan 6 10:25:26 buster nis[1039]: Starting NIS services: ypbindbinding to YP server...failed (backgrounded). Jan 6 10:25:26 buster nis[1039]: . Jan 6 10:25:26 buster systemd[1]: Started LSB: Start NIS client and server daemons.. Jan 6 10:25:27 buster systemd[1]: Reloading. Jan 6 10:26:06 buster ypbind[1051]: broadcast: RPC: Timed out. Jan 6 10:27:00 buster ypbind[1051]: broadcast: RPC: Timed out. Jan 6 10:27:54 buster ypbind[1051]: broadcast: RPC: Timed out. ... and the ypbind timeouts forever. Note that this is expect because the empty /etc/yp.conf triggered the -broadcast: root 1051 1 0 10:22 ?00:00:00 /usr/sbin/ypbind -broadcast and there is no server available in my test. Now, let's add a server by changing /etc/default/nis and restarting the services. /etc/init.d/nis restart [... hangs again because of ypbind, then after some minutes: ] [ ok ] Restarting nis (via systemctl): nis.service. At this point a /usr/lib/yp/ypinit -m can be issued and it works. Now again a restart of ypbind is due and again it hangs because of the missing ypserver spec in /etc/yp.conf, and a broadcast never answered. Of course, I could simply add 127.0.0.1 to /etc/yp.conf and restart. But let's pretend it was able to magically understand that it should talk with the local server and reboot. Well, nothing chaged, still RPC timeouts. Now, this report apparently says that stopping and restarting ypbind after the upgrade was be able to work even with an empty /etc/yp.conf before nis 3.9 Unfortunately this is not more the case, at least in the last 17 years or so, as shown in #118023: $ sudo ypbind No NIS server and no -broadcast option specified. Add a NIS server to the /etc/yp.conf configuration file, or start ypbind with the -broadcast option. Therefore, on the basis of this trials I will go to close this bug because it is unfortunately the way ypbind works and so basically a configuration issue. Also, the postinst does not fail for the issues with ypbind configurations at least from jessie and nis 3.17-33, which expose the same behavior. I'll leave this bug open at least until next package release. -cheers Francesco On Fri, Aug 14, 2009 at 01:24:07PM +1000, Ben Finney wrote: package nis found 213733 3.17-27 tags 213733 - moreinfo found 118023 3.17-27 tags 118023 - moreinfo thanks On 02-Oct-2003, Paul Schulz wrote: Upgrade NIS in testing distribution and NIS fails to restart. The usual messages is reported. Starting NIS services: ypbind [binding to YP server .. backgrounded] NIS can be stopped and restarted several times with the same result. (It was running previously without a problem.) I have exactly the same problem on upgrading to version 3.17-27, with this output: = $ sudo /etc/init.d/nis restart Stopping NIS services: ypbind ypserv ypppasswdd ypxfrd. Starting NIS services: ypserv yppasswdd ypxfrd ypbindbinding to YP server..
Bug#979409: node-source-map: Missing dependency on libjs-source-map
Package: node-source-map Version: 0.7.0++dfsg2+really.0.6.1-5 Severity: serious Tags: ftbfs Control: affects -1 src:node-recast https://buildd.debian.org/status/fetch.php?pkg=node-recast&arch=all&ver=0.20.4-2&stamp=1609934485&raw=0 ... dh_auto_configure --buildsystem=nodejs -i mkdir node_modules cp -rL /usr/share/nodejs/ast-types ./node_modules/ mkdir -p ./node_modules/\@babel cp -rL /usr/share/nodejs/\@babel/parser ./node_modules/\@babel mkdir -p ./node_modules/\@babel cp -rL /usr/share/nodejs/\@babel/types ./node_modules/\@babel cp -rL /usr/share/nodejs/source-map ./node_modules/ cp: cannot stat '/usr/share/nodejs/source-map/dist/source-map.debug.js': No such file or directory cp: cannot stat '/usr/share/nodejs/source-map/dist/source-map.debug.min.js': No such file or directory cp: cannot stat '/usr/share/nodejs/source-map/dist/source-map.js': No such file or directory cp: cannot stat '/usr/share/nodejs/source-map/dist/source-map.min.js.map': No such file or directory dh_auto_configure: error: cp -rL /usr/share/nodejs/source-map ./node_modules/ returned exit code 1 make: *** [debian/rules:4: binary-indep] Error 25 These are now dangling symlinks in node-source-map.
Bug#977088: closed by Debian FTP Masters (reply to Andrej Shadura ) (Bug#977088: fixed in python-h2 4.0.0-2)
Control: reopen -1 On Mon, Jan 04, 2021 at 09:09:10AM +, Debian Bug Tracking System wrote: >... > python-h2 (4.0.0-2) unstable; urgency=medium > . >* Use "not" with -k, not "-" for pytest 6 compatibility > (Closes: #977088). >... Something went wrong: https://buildd.debian.org/status/fetch.php?pkg=python-h2&arch=all&ver=4.0.0-2&stamp=1609934542&raw=0 cu Adrian
Bug#978232: Standalone orage
On Tue, Jan 05, 2021 at 05:23:24PM +0100, Slavko wrote: > Hi, > > i rebuild package locally and i can confirm, that it works as i > assumed. There are needed more tweaks, i will summarize them here to > save some time: > [...] > After i install new package, XFCE's panel can be upgraded and orage can > be run in background (in systray). Thanks Slavko! That worked perfectly. Orage is also imcompatible with the current xfce4-panel, and will block an upgrade without this fix. xfce4-panel is now built on gtk3 rather than gtk2, and so the panel plugin cannot even be built. Orage is also abandoned upstream - the repository has been removed. Best wishes, Julian
Bug#979392: RFS: libfilezilla/0.26.0-1 [Team] -- build high-performing platform-independent programs (runtime lib)
On Wed, Jan 06, 2021 at 04:15:28AM +, Philip Wyett wrote: > * Package name: libfilezilla >Version : 0.26.0-1 > > It builds those binary packages: > > libfilezilla0 - build high-performing platform-independent programs > (runtime lib) > libfilezilla-dev - build high-performing platform-independent > programs (development) The soname has changed, you'd need to rename the runtime package to libfilezilla1. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ] ⣾⠁⢠⠒⠀⣿⡁ # beware of races ⢿⡄⠘⠷⠚⠋⠀ all: pillage burn ⠈⠳⣄ `
Bug#979410: lemon: Mention installed lemon.html in lemon.1
Package: lemon Severity: minor Dear Maintainer, I think it is useful to mention the installed documentation in form of lemon.html in the manual page. I don't feel strongly about the description of lemon.html, so feel free to change if you have a better idea. While doing that I also improved the markup of e-mail addresses using the Mt macro and fixed a few complaints from mandoc -Tlint lemon.1 Thanks! -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lemon depends on: ii libc6 2.28-10 lemon recommends no packages. lemon suggests no packages. diff -ur sqlite3-3.27.2/debian/lemon.1 sqlite3-3.27.2_new/debian/lemon.1 --- sqlite3-3.27.2/debian/lemon.1 2010-03-13 17:47:58.0 +0100 +++ sqlite3-3.27.2_new/debian/lemon.1 2021-01-06 13:23:05.095872794 +0100 @@ -1,4 +1,4 @@ -.Dd 2002-10-04 +.Dd January 6, 2021 .Dt LEMON 1 .Os "Debian GNU/Linux" .\" Manual page created by Guus Sliepen @@ -13,14 +13,14 @@ .Nm is an LALR(1) parser generator for C or C++. It does the same job as bison and yacc. -But +But .Nm is not another bison or yacc clone. It uses a different grammar syntax which is designed to reduce the number of coding errors. .Nm also uses a more sophisticated parsing engine that is faster than yacc and bison and which is both reentrant and thread-safe. -Furthermore, +Furthermore, .Nm implements features that can be used to eliminate resource leaks, making is suitable for use in long-running programs such as graphical user interfaces or embedded controllers. @@ -52,12 +52,14 @@ Driver template for the .Nm parser generator. +.It Pa /usr/share/doc/lemon/lemon.html +Syntax description and additional information. .El -.Sh AUTHOR +.Sh AUTHORS .Nm has been written by -.An D. Richard Hipp Aq d...@hwaci.com . +.An D. Richard Hipp Aq Mt d...@hwaci.com . .Pp This manual page was written by -.An Guus Sliepen Aq g...@debian.org +.An Guus Sliepen Aq Mt g...@debian.org for the Debian GNU/Linux system.
Bug#979411: resize2fs: no percentage completion bars displayed with -p
Package: e2fsprogs Version: 1.44.5-1+deb10u3 Severity: normal Tags: upstream Dear Maintainer, According to the man page the -p option should print out "percentage completion bars", though this was not done on a recent operation (offline shrink). Kind regards, Andrei -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 3.18.0-12-ARCH (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), LANGUAGE=ro_RO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages e2fsprogs depends on: ii libblkid12.33.1-0.1 ii libc62.28-10 ii libcom-err2 1.44.5-1+deb10u3 ii libext2fs2 1.44.5-1+deb10u3 ii libss2 1.44.5-1+deb10u3 ii libuuid1 2.33.1-0.1 Versions of packages e2fsprogs recommends: pn e2fsprogs-l10n Versions of packages e2fsprogs suggests: pn e2fsck-static pn fuse2fs pn gpart ii parted 3.2-25 -- no debconf information
Bug#979412: pinentry: "--lc-type" in manapges is typo for "--lc-ctype"
Source: pinentry Severity: minor Tags: patch X-Debbugs-Cc: kas...@rollingapple.net Dear Maintainer, The manpages for pinentry commands say that the commands accept "--lc-type" options, but the correct option name is "--lc-ctype". The same typo is fixed in the info in the upstream commit 971962116fba3769d8260b5016f93c6f9ebf083f. https://git.gnupg.org/cgi-bin/gitweb.cgi?p=pinentry.git;a=commit;h=971962116fba3769d8260b5016f93c6f9ebf083f -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled >From c7514f8849174fecc479833cc078cf7b6f323a87 Mon Sep 17 00:00:00 2001 From: Kasumi Hanazuki Date: Wed, 6 Jan 2021 12:20:53 + Subject: [PATCH] Fix typo in manpages --- debian/pinentry-curses.1 | 2 +- debian/pinentry-fltk.1 | 2 +- debian/pinentry-gnome3.1 | 2 +- debian/pinentry-gtk-2.1 | 2 +- debian/pinentry-qt.1 | 2 +- debian/pinentry-tty.1| 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/debian/pinentry-curses.1 b/debian/pinentry-curses.1 index 69d24f7..876fa02 100644 --- a/debian/pinentry-curses.1 +++ b/debian/pinentry-curses.1 @@ -50,7 +50,7 @@ you have other means to connect to the machine to kill Use window ID \fIN\fR as the parent window for positioning the window. Note, that this is not fully supported by all flavors of \fBpinentry\fR. .TP -\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-type\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR +\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-ctype\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR These options are used to pass localization information to \fBpinentry-curses\fR. They are required because \fBpinentry-curses\fR is usually called by diff --git a/debian/pinentry-fltk.1 b/debian/pinentry-fltk.1 index 1078e19..17cec2a 100644 --- a/debian/pinentry-fltk.1 +++ b/debian/pinentry-fltk.1 @@ -48,7 +48,7 @@ you have other means to connect to the machine to kill Use window ID \fIN\fR as the parent window for positioning the window. Note, that this is not fully supported by all flavors of \fBpinentry\fR. .TP -\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-type\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR +\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-ctype\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR These options are used to pass localization information to \fBpinentry-fltk\fR. They are required because \fBpinentry-fltk\fR is usually called by diff --git a/debian/pinentry-gnome3.1 b/debian/pinentry-gnome3.1 index d99d99e..389afff 100644 --- a/debian/pinentry-gnome3.1 +++ b/debian/pinentry-gnome3.1 @@ -48,7 +48,7 @@ you have other means to connect to the machine to kill Use window ID \fIN\fR as the parent window for positioning the window. Note, that this is not fully supported by all flavors of \fBpinentry\fR. .TP -\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-type\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR +\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-ctype\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR These options are used to pass localization information to \fBpinentry-gnome3\fR. They are required because \fBpinentry-gnome3\fR is usually called by diff --git a/debian/pinentry-gtk-2.1 b/debian/pinentry-gtk-2.1 index 180be04..d108811 100644 --- a/debian/pinentry-gtk-2.1 +++ b/debian/pinentry-gtk-2.1 @@ -48,7 +48,7 @@ you have other means to connect to the machine to kill Use window ID \fIN\fR as the parent window for positioning the window. Note, that this is not fully supported by all flavors of \fBpinentry\fR. .TP -\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-type\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR +\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-ctype\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR These options are used to pass localization information to \fBpinentry-gtk-2\fR. They are required because \fBpinentry-gtk-2\fR is usually called by diff --git a/debian/pinentry-qt.1 b/debian/pinentry-qt.1 index 61c23a0..1047399 100644 --- a/debian/pinentry-qt.1 +++ b/debian/pinentry-qt.1 @@ -48,7 +48,7 @@ you have other means to connect to the machine to kill Use window ID \fIN\fR as the parent window for positioning the window. Note, that this is not fully supported by all flavors of \fBpinentry\fR. .TP -\fB--display\fR \fISTRING\fR,
Bug#979408: qpdfview: Cannot create annotation
Hi Jeff, > This seems to only affect djvu documents. With PDFs, it works as advertised. Yes, annotations are a PDF thingy. That you can view djvu with qpdfview is just an "added gadget", but not all functionality is available. Can we close this report, or is there anything else you want to see? Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#979108: memtool: 64 bit memory reads may be split on 32 bit systems
Control: found -1 2016.10.0-1
Control: fixed -1 2018.03.0-1
On Tue, Jan 05, 2021 at 09:42:35PM +0100, Uwe Kleine-König wrote:
> On 1/2/21 8:34 PM, Gergely Peli wrote:
> > Package: memtool
> > Severity: normal
> > Tags: upstream patch
> >
> > Hello,
> >
> > I tried memtool on a 32 bit ARM system, and the supposedly 64 bit reads
> > with the "-q" option are done by 2 separate 32 bit "ldr" instructions.
> > Adding a volatile qualifier to the pointers accessing the memory could
> > convince gcc to generate a single "ldrd" instruction instead, which uses
> > a 64 bit memory transfer. See below a proposed patch. Adding volatile to all
> > 4 cases may be an overkill, but can't hurt. Cheers,
> >
> > Gergely Peli
> >
> >
> >
> > --- memtool-2016.10.0.orig/memtool.c
> > +++ memtool-2016.10.0/memtool.c
> > @@ -152,24 +152,24 @@ static int memory_display(const void *ad
> > for (i = 0; i < linebytes; i += width) {
> > if (width == 8) {
> > uint64_t res;
> > - res = (*uqp++ = *((uint64_t *)addr));
> > + res = (*uqp++ = *((volatile uint64_t
> > *)addr));
>
> In this code location it doesn't matter if two ldrs instead of a single ldrd
> is used. This is only the code printing the data from the buffer that holds
> the read data. If memtools behaves wrong the problem is likely in mmap_read.
In a private followup conversation it became obvious that there is
indeed a culprit but only in oldstable with version 2016.10.0-1 where
memory_display operates directly on the mmap'd memory.
With changes introduced in 2018.03.0 the problem is gone. (It's not
entirely clear why though, maybe there is also some luck involved
because the compiler behaviour changed and we might need some volatiles
in mmap_read (and mmap_write) for correctness). Anyhow, I checked
memtool 2018.03.0 on armhf and there a 64 bit read (vldr.64, not ldrd)
is used. So I marked 2018.03.0-1 as fixed.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König|
Industrial Linux Solutions | https://www.pengutronix.de/ |
signature.asc
Description: PGP signature
Bug#979415: dkimproxy: file conflict with libmsdw-smtp-perl
Package: dkimproxy Version: 1.4.1-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. dkimproxy ships a copy of usr/share/perl5/MSDW/SMTP/Client.pm usr/share/perl5/MSDW/SMTP/Server.pm which are also in libmsdw-smtp-perl. libmsdw-smtp-perl has Breaks: dkimproxy (<= 1.4.1-3) which is *NOT* a correct solution. >From the attached log (scroll to the bottom...): Preparing to unpack .../dkimproxy_1.4.1-3.1_all.deb ... Unpacking dkimproxy (1.4.1-3.1) ... dpkg: error processing archive /var/cache/apt/archives/dkimproxy_1.4.1-3.1_all.deb (--unpack): trying to overwrite '/usr/share/perl5/MSDW/SMTP/Client.pm', which is also in package libmsdw-smtp-perl 1.2-1 Errors were encountered while processing: /var/cache/apt/archives/dkimproxy_1.4.1-3.1_all.deb cheers, Andreas libmsdw-smtp-perl=1.2-1_dkimproxy=1.4.1-3.1.log.gz Description: application/gzip
Bug#979408: qpdfview: Cannot create annotation
Hi Norbert, On 06/01/2021 13:42, Norbert Preining wrote: Yes, annotations are a PDF thingy. That you can view djvu with qpdfview is just an "added gadget", but not all functionality is available. DjVu documents support annotations, too. So perhaps we can turn this into two reports: * at present, the user should get some feedback that qpdfview cannot create annotations in djvu * a wishlist bug that the functionality be added. Regards Jeff OpenPGP_signature Description: OpenPGP digital signature
Bug#979414: zfs-zed: please improve package long description
Package: zfs-zed Version: 0.8.6-1 Severity: minor Dear Maintainer, In addition to the common description for all ZFS packages the description only mentions: This package provides the OpenZFS Event Daemon (zed). For people that are unfamiliar with ZFS it is unclear what this Event Daemon does and why a ZFS user would want this installed. The package is also recommended by zfsutils-linux, so it should be installed in all by unusual configurations. As far as I understand from zed(8), the description could be improved by adding something like: [...] which can be used to monitor events from ZFS (zevents) and trigger various actions (ZEDLETs) in response. Some info on why most ZFS users should have this installed would also be very good (or it should be demoted to a Suggests of zfsutils-linux instead). Kind regards, Andrei -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 3.18.0-12-ARCH (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), LANGUAGE=ro_RO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#979416: Wrong test to determine "if systemd-resolved is running"
Package: ppp Version: 2.4.8-1+2 File: /etc/ppp/ip-up.d/usepeerdns In /etc/ppp/ip-up.d/usepeerdns we see: # exit if systemd-resolved is running [ -x /usr/bin/systemd-resolve ] && \ /usr/bin/systemd-resolve --status >/dev/null && exit 0 However this is the wrong test to see "if systemd-resolved is running". Proof: # systemctl start systemd-resolved # systemctl status systemd-resolved|grep running Active: active (running) since Wed 2021-01-06 19:05:09 CST; 12s ago # systemctl stop systemd-resolved # systemctl status systemd-resolved|grep running # systemctl status systemd-resolved|grep Active Active: inactive (dead) since Wed 2021-01-06 19:05:35 CST; 20s ago The current test in /etc/ppp/ip-up.d/usepeerdns will give TRUE even "if systemd-resolved is NOT running": # systemctl start systemd-resolved # /usr/bin/systemd-resolve --status >/dev/null && echo TRUE TRUE # systemctl stop systemd-resolved # /usr/bin/systemd-resolve --status >/dev/null && echo TRUE TRUE Probing further, # systemctl disable systemd-resolved Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service. Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service. # /usr/bin/systemd-resolve --status >/dev/null && echo TRUE TRUE # systemctl --now disable systemd-resolved # /usr/bin/systemd-resolve --status >/dev/null && echo TRUE Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found. OK, we finally got it to not return TRUE, in fact due to a bug (it can't find a file, so bombs early,) which I will report to them... OK, now let us research what the documented exit value of /usr/bin/systemd-resolve is. # man systemd-resolve No manual entry for systemd-resolve # systemd-resolve --help | grep man See the resolvectl(1) man page for details. Ah, it turns out /usr/bin/systemd-resolve lrwxrwxrwx 1 root 10 01-03 00:06 systemd-resolve -> resolvectl is a symlink all along. Anyway the resolvectl man page doesn't mention anything about exit statuses. So maybe one needs a junky line like: # systemctl status systemd-resolved|grep Active|grep -q running && echo TRUE to test if something is running. I didn't explore further. All I know is the current test used in usepeerdns is wrong. (I did look in /run and did find some stuff, but it doesn't seem affected by my tests) Wait! I found the correct test for you: $ man systemctl is-active PATTERN... Check whether any of the specified units are active (i.e. running). Returns an exit code 0 if at least one is active, or non-zero otherwise. Unless --quiet is specified, this will also print the current unit state to standard output. # systemctl stop systemd-resolved # systemctl --quiet is-active systemd-resolved && echo TRUE # systemctl start systemd-resolved # systemctl --quiet is-active systemd-resolved && echo TRUE TRUE
Bug#979417: systemd-resolved --status not prepared for missing files
Package: systemd Version: 247.2-4 Severity: minor File: /usr/bin/systemd-resolve /usr/bin/systemd-resolve --status expects to always find files that in fact may not be there and are not errors and should not cause the program to bomb out early. # systemctl enable --now systemd-resolved Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /lib/systemd/system/systemd-resolved.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service. # /usr/bin/systemd-resolve --status | wc 11 33 481 # systemctl --now disable systemd-resolved Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service. Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service. # /usr/bin/systemd-resolve --status | wc Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found. 0 0 0
Bug#979418: nmu: kwave_20.12.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: Debian Qt/KDE Maintainers nmu kwave_20.12.0-1 . ANY . unstable . -m "Rebuild on buildds so it can migrate to testing." -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#979250: cinnamon-core: Why does cinnamon-core depend on xorg?
I did some other minimal install tests with debian and ubuntu. Replacing xorg dep. in cinnamon-core with xserver-xorg on debian is still working also without recommends but it don't install a terminal (that was one of xorg deps); I think that can be considered "a must" I'll solve it moving terminal dep. from cinnamon-desktop-environment to cinnnamon-core. On ubuntu instead is not working but is not an issue related to cinnamon-core packages, is lightdm package on ubuntu that is different from debian one and have greeter as recommmends instead dep. and without one installed lightdm fails to start.
Bug#979419: nfs-ganesha build depends on the removed dh-systemd transitional package
Source: nfs-ganesha Version: 3.3-1 Severity: serious Tags: ftbfs The transitional dh-systemd package is no longer built by debhelper. It is still as cruft package in unstable, but already removed from testing.
Bug#972425: mlpack FTBFS fixed in version 3.4.2-1 ?
Good day, I tried to reproduce the FTBFS of mlpack on my end, and the build went through. Then, I spotted the following entry in the mlpack changelog: * Do not allow doxygen warnings to break the build By chance, isn't it time to close #972425, as fixed in version 3.4.2-1 ? Best wishes, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#979420: nautilus-kdeconnect: missing Breaks+Replaces: kdeconnect (<< 20.12)
Package: nautilus-kdeconnect Version: 20.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../nautilus-kdeconnect_20.12.0-3_all.deb ... Unpacking nautilus-kdeconnect (20.12.0-3) ... dpkg: error processing archive /var/cache/apt/archives/nautilus-kdeconnect_20.12.0-3_all.deb (--unpack): trying to overwrite '/usr/share/nautilus-python/extensions/kdeconnect-share.py', which is also in package kdeconnect 20.08.3-1 Errors were encountered while processing: /var/cache/apt/archives/nautilus-kdeconnect_20.12.0-3_all.deb cheers, Andreas kdeconnect=20.08.3-1_nautilus-kdeconnect=20.12.0-3.log.gz Description: application/gzip
Bug#978742: mmtarfilter: Slow performance with many path exclusions
Hi, Quoting Josh Triplett (2020-12-31 22:04:49) > On Wed, Dec 30, 2020 at 10:38:58PM -0800, Josh Triplett wrote: > > With a large number of path exclusions specified (around 500), > > mmtarfilter starts to become a noticeable performance bottleneck. while I'm amazed, that my software is being used in exotic setups I'm scared to ask in which scenario you ended up using 500 path exclusions. :D > > It looks like mmtarfilter checks each file linearly against each filter > > using fnmatch. > > > > Python's fnmatch implementation works by translating shell patterns into > > regular expressions. Python also provides a function to do that translation > > separate from fnmatch. One fairly simple optimization would be to walk the > > list of patterns *once*, take each series of consecutive exclude or include > > filters, turn each one into a regex, join all the regexes in each group > > together using (?:...)|(?:...) , and compile the resulting regexes once. > > That should provide a substantial performance improvement. > > Turns out there's a much simpler explanation with a simpler fix. fnmatch has > a 256-entry LRU cache for the translated regular expressions. Once there are > more than 256 path filters, the cache stops working entirely, and every shell > pattern gets re-translated and re-compiled on every invocation of fnmatch. > > I wrote the attached patch for mmtarfilter to address this. On an invocation > of mmdebstrap with around 500 path filters, this saves more than a minute. Thanks! It's applied upstream: https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/5a7dbc10c74167c8f0105f5803b81317cf676f42 signature.asc Description: signature
Bug#979421: problem installing for lighttpd: /usr/bin/php-cgi: No such file or directory
Package: phpmyadmin Version: 4:4.9.7+dfsg1-1 Severity: normal I am running Debian testing. I made a fresh install of lighttpd and did not change its configuration or enable any modules. Then I installed phpmyadmin and asked it to configure automatically for lighttpd. This caused lighttpd to be unable to start. I checked the log and found this message: Jan 06 08:44:06 saturn lighttpd[339062]: /usr/bin/php-cgi: No such file or directory Jan 06 08:44:06 saturn systemd[1]: lighttpd.service: Main process exited, code=exited, status=255/EXCEPTION I think that this is because the postinst script in the phpmyadmin package enables the lighttpd fastcgi-php module: lighty-enable-mod phpmyadmin auth fastcgi fastcgi-php But this module needs to have /usr/bin/php-cgi available, and phpmyadmin doesn't depend on the php-cgi package. Note, though, that the description for the php-cgi package says this: "Note that MOST users probably want the php-fpm package that provide FastCGI support." So I think that, rather than phpmyadmin adding a dependency on php-cgi, it would be better for phpmyadmin to add a dependency on php-fpm and enable the fastcgi-php-fpm module in its postinst. Let me know if I can provide any further information. Thank you, James Dietrich
Bug#978742: mmtarfilter: Slow performance with many path exclusions
Hi, Quoting Jonas Smedegaard (2020-12-31 07:51:42) > Quoting Josh Triplett (2020-12-31 07:38:58) > > With a large number of path exclusions specified (around 500), > > mmtarfilter starts to become a noticeable performance bottleneck. > > > > It looks like mmtarfilter checks each file linearly against each filter > > using fnmatch. > > > > Python's fnmatch implementation works by translating shell patterns into > > regular > > expressions. Python also provides a function to do that translation > > separate from fnmatch. One fairly simple optimization would be to walk the > > list of > > patterns *once*, take each series of consecutive exclude or include > > filters, turn each one into a regex, join all the regexes in > > each group together using (?:...)|(?:...) , and compile the resulting > > regexes once. That should provide a substantial performance improvement. > > Alternatively, if a rewrite in Perl is preferred, there's > libarchive-tar-wrapper-perl which does not slurp the whole tarball into > memory (noticing the comment in current script), and libregexp-assemble-perl > to fuse regexes together. yes, a rewrite is preferred, but it should not bloat mmdebstraps dependencies more. Ideally, mmdebstrap should be able to run on a very minimal system (so that you can run mmdebstrap inside mmdebstrap) thus I would also love to kick Python from its dependencies. So if a rewrite happens, then it should probably be written in C. Since libarchive doesn't work, it should probably copypaste the tar handling code from dpkg. Thanks! cheers, josch signature.asc Description: signature
Bug#979422: minicom does not consider port busy if lockfile isn't readable (existence isn't enough)
Package: minicom Version: 2.7.1-1+b1 Severity: normal When minicom checks for a lockfile (e.g. /var/lock/LCK..modem0), it only considers lockfiles that are readable (by the current user). If the lockfile isn't readable, minicom will proceed as if the lockfile didn't exist, causing a collision with the application already accessing the port/device. Expected behavior would be that minicom considers the port/device busy if it finds a lockfile, regardless of whether it is readable or not. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minicom depends on: ii libc6 2.28-10 ii libtinfo6 6.1+20181013-2+deb10u2 Versions of packages minicom recommends: ii lrzsz 0.12.21-10 minicom suggests no packages. -- no debconf information
Bug#893924: python3-distutils: Please describe road map/recommendations for users of distutils
The current CPython plan is to deprecate distutils in 3.10 and 3.11, and then remove it in 3.12. https://www.python.org/dev/peps/pep-0632/
Bug#979412: [pkg-gnupg-maint] Bug#979412: pinentry: "--lc-type" in manapges is typo for "--lc-ctype"
FWIW, that was fixed 11 years ago in upstream (commit 971962116fba3769d8260b5016f93c6f9ebf083f) -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
Bug#965964: Update on Geant4
Small update regarding Geant4: Geant4 10.7.0 got released in December, which is basically lintian clean so far (thanks to upstream for fixing all that). However, Geant4 10.7.0 won't make it into Bullseye (or even Sid for that matter), because there is a major problem: it segfaults. I tried it on 3 different setups, one running Ubuntu 20.10, and it justs segfaults every time one starts a run. I don't know why (yet), I *think* it might be due to the introduction of PTL & TBB, but I haven't debugged it yet. PTL is a library which should heavily increase performance, but it is really new and upstream has stabilized just yet. I hope the next major Geant4 release (i. e. 10.8.0) uses the just released upstream PTL 1.0.0, so we can use that. For anyone interested, my current plan is to package PTL and wait for the next minor Geant4 version (10.7.1) before trying to debugging it. If you want to help, you can try to find out why it segfaults (requires to start a run, you can take any included example). Regards, Stephan
Bug#978024: regression: 4.11.1 broke dose3 on bytecode arches
Control: reassign -1 dose3 Hello, Le 24/12/2020 à 17:37, Johannes 'josch' Schauer a écrit : > my package botch FTBFS on armel, mips64el and mipsel: > > https://buildd.debian.org/status/package.php?p=botch > > The reason is, that when calling dose-deb-coinstall it fails with "unknown > option --verbose". Upon further investigation, it turns out, that the dose3 > source package builds invalid binaries on armel, mips64el and mipsel. > You can reproduce the problem by building dose3 on a mipsel porter box > with: > > $ apt-get source dose3 --build > > You then end up with the following identical working binaries: > > dose3-5.0.1/_build/applications/deb-coinstall.byte > dose3-5.0.1/debian/tmp/usr/bin/dose-deb-coinstall > > But surprisingly, this one is different and also doesn't work as > expected: > > $ dose3-5.0.1/debian/dose-extra/usr/bin/dose-deb-coinstall --help > unknown option --help > > Funnily, the other non-working binaries, have the exact same md5sum: > > $ find dose3-5.0.1/ -type f -print0 | xargs -0 md5sum | grep > 0261218e050b5c5c7ee1988fd1d4e5da > 0261218e050b5c5c7ee1988fd1d4e5da > dose3-5.0.1/debian/dose-extra/usr/bin/dose-deb-coinstall > 0261218e050b5c5c7ee1988fd1d4e5da > dose3-5.0.1/debian/dose-extra/usr/bin/dose-ceve > 0261218e050b5c5c7ee1988fd1d4e5da > dose3-5.0.1/debian/dose-distcheck/usr/bin/dose-distcheck > > I don't understand how this problem or what makes these three different from > the other utilities built by the dose3 source package or how the error is only > introduced when moving the binaries from debian/tmp to debian/dose-*. I can reproduce the problem in an amd64 chroot by first removing /usr/bin/ocamlopt* and /usr/lib/ocaml/dynlink.cmx* (nice trick to reproduce a fast bytecode environment). My suspicion was stripped custom bytecode executables... and this is indeed the case. In Debian OCaml < 4.11, there was a Debian-specific patch that made stripping custom bytecode executables possible. In (upstream) OCaml 4.11, the feature was added, under a new command-line option (-output-complete-exe). In Debian, I patched OCaml so that the new feature is triggered with -custom... only if a specific environment variable (OCAML_CUSTOM_USE_OUTPUT_COMPLETE_EXE) is set. This variable is set by /usr/share/ocaml/ocamlvars.mk, included by the debian/rules of most packages... but not the one of dose3. This is why this issue happens only with dose3. > Maybe you have an idea of how to proceed? Possible fixes are: 1. do not strip dose3 executables 2. include /usr/share/ocaml/ocamlvars.mk in dose3's debian/rules 3. directly use -output-complete-exe instead of -custom 4. do not use -custom nor -output-complete-exe at all I tried 2 (which is actually 3) and it does not work because -output-complete-exe is incompatible with -a, and -a and -custom are used together somewhere in dose3 build system. 1 should be easy to implement (empty override of dh_strip) and upload, if urgent. I am currently looking into 4. Cheers, -- Stéphane
Bug#979423: fail2ban: Dovecot's submission default logging errors are not handled
Package: fail2ban
Version: 0.10.2-2.1
Severity: normal
Tags: patch
X-Debbugs-Cc: fpoul...@metrodore.fr
Dear Maintainer,
I am using Dovecot's submission system, which is not the more famous way
of using dovecot.
It appears that the fail2ban's dovecot filter doesn't handle
submission's logging format (fail2ban and dovecot, released with buster).
The latter looks like:
janv. 06 14:53:12 mx1 dovecot[21994]: submission-login: Remote closed
connection (auth failed, 1 attempts in 7 secs): ...
Rather than:
Jan 5 16:43:55 mx1 dovecot: imap-login: Disconnected (auth failed, 3 attempts
in 14 secs): ...
I locally fixed it by trivially altering the fail2ban dovecot filter:
diff --git a/fail2ban/filter.d/dovecot.conf b/fail2ban/filter.d/dovecot.conf
index 2019a16..71df301 100644
--- a/fail2ban/filter.d/dovecot.conf
+++ b/fail2ban/filter.d/dovecot.conf
@@ -10,10 +10,10 @@ before = common.conf
_auth_worker = (?:dovecot: )?auth(?:-worker)?
_daemon = (?:dovecot(?:-auth)?|auth)
-prefregex = ^%(__prefix_line)s(?:%(_auth_worker)s(?:\([^\)]+\))?:
)?(?:%(__pam_auth)s(?:\(dovecot:auth\))?: |(?:pop3|imap)-login: )?(?:Info:
)?.+$
+prefregex = ^%(__prefix_line)s(?:%(_auth_worker)s(?:\([^\)]+\))?:
)?(?:%(__pam_auth)s(?:\(dovecot:auth\))?: |(?:pop3|imap|submission)-login:
)?(?:Info: )?.+$
failregex = ^authentication failure; logname=\S* uid=\S* euid=\S* tty=dovecot
ruser=\S* rhost=(?:\s+user=\S*)?\s*$
-^(?:Aborted login|Disconnected)(?::(?: [^ \(]+)+)? \((?:auth
failed, \d+ attempts(?: in \d+ secs)?|tried to use (?:disabled|disallowed) \S+
auth)\):(?: user=<[^>]*>,)?(?: method=\S+,)? rip=(?:[^>]*(?:,
session=<\S+>)?)\s*$
+^(?:Aborted login|Disconnected|Remote closed connection)(?::(?: [^
\(]+)+)? \((?:auth failed, \d+ attempts(?: in \d+ secs)?|tried to use
(?:disabled|disallowed) \S+ auth)\):(?: user=<[^>]*>,)?(?: method=\S+,)?
rip=(?:[^>]*(?:, session=<\S+>)?)\s*$
^pam\(\S+,(?:,\S*)?\): pam_authenticate\(\) failed: (?:User
not known to the underlying authentication module: \d+ Time\(s\)|Authentication
failure \(password mismatch\?\)|Permission denied)\s*$
^[a-z\-]{3,15}\(\S*,(?:,\S*)?\): (?:unknown user|invalid
credentials)\s*$
>
Best regards.
François
-- System Information:
Debian Release: buster
Bug#977701: gitlab: Missing assets, breaking some functionalities
So, I got the asset compilation running, but I had to workaround some issues,
including broken symlinks to js
libs:_
cd /usr/share/gitlab
# move locale.static elsewhere
mv app/assets/javascripts/locale.static .
mv app/assets/javascripts/locale/index.js{,.bak}
ln -s /usr/share/gitlab/locale.static/index.js
app/assets/javascripts/locale/index.js
# remove broken symlinks
mkdir /root/vendor_assets_javascripts
cd vendor/assets/javascripts/
mv -t /root/vendor_assets_javascripts chart-lib.min.js clipboard.js
fuzzaldrin-plus.js g.bar-min.js g.raphael-min.js jquery.nicescroll.min.js
cd -
# create hash file
touch assets-hash.txt
chown git:git assets-hash.txt
# provide webpack
ln -s /usr/bin/webpack node_modules/.bin/webpack
# compile all assets
gitlab-rake gitlab:assets:compile_
However, this unfortunately didn't resolve the issues.
Best,
Maximilian
Bug#978024: regression: 4.11.1 broke dose3 on bytecode arches
Hi, Quoting Stéphane Glondu (2021-01-06 16:02:05) > Le 24/12/2020 à 17:37, Johannes 'josch' Schauer a écrit : > > my package botch FTBFS on armel, mips64el and mipsel: > > > > https://buildd.debian.org/status/package.php?p=botch > > > > The reason is, that when calling dose-deb-coinstall it fails with "unknown > > option --verbose". Upon further investigation, it turns out, that the dose3 > > source package builds invalid binaries on armel, mips64el and mipsel. > > You can reproduce the problem by building dose3 on a mipsel porter box > > with: > > > > $ apt-get source dose3 --build > > > > You then end up with the following identical working binaries: > > > > dose3-5.0.1/_build/applications/deb-coinstall.byte > > dose3-5.0.1/debian/tmp/usr/bin/dose-deb-coinstall > > > > But surprisingly, this one is different and also doesn't work as > > expected: > > > > $ dose3-5.0.1/debian/dose-extra/usr/bin/dose-deb-coinstall --help > > unknown option --help > > > > Funnily, the other non-working binaries, have the exact same md5sum: > > > > $ find dose3-5.0.1/ -type f -print0 | xargs -0 md5sum | grep > > 0261218e050b5c5c7ee1988fd1d4e5da > > 0261218e050b5c5c7ee1988fd1d4e5da > > dose3-5.0.1/debian/dose-extra/usr/bin/dose-deb-coinstall > > 0261218e050b5c5c7ee1988fd1d4e5da > > dose3-5.0.1/debian/dose-extra/usr/bin/dose-ceve > > 0261218e050b5c5c7ee1988fd1d4e5da > > dose3-5.0.1/debian/dose-distcheck/usr/bin/dose-distcheck > > > > I don't understand how this problem or what makes these three different from > > the other utilities built by the dose3 source package or how the error is > > only > > introduced when moving the binaries from debian/tmp to debian/dose-*. > > I can reproduce the problem in an amd64 chroot by first removing > /usr/bin/ocamlopt* and /usr/lib/ocaml/dynlink.cmx* (nice trick to > reproduce a fast bytecode environment). > > My suspicion was stripped custom bytecode executables... and this is > indeed the case. > > In Debian OCaml < 4.11, there was a Debian-specific patch that made > stripping custom bytecode executables possible. In (upstream) OCaml > 4.11, the feature was added, under a new command-line option > (-output-complete-exe). In Debian, I patched OCaml so that the new > feature is triggered with -custom... only if a specific environment > variable (OCAML_CUSTOM_USE_OUTPUT_COMPLETE_EXE) is set. This variable is > set by /usr/share/ocaml/ocamlvars.mk, included by the debian/rules of > most packages... but not the one of dose3. This is why this issue > happens only with dose3. > > > Maybe you have an idea of how to proceed? > > Possible fixes are: > > 1. do not strip dose3 executables > 2. include /usr/share/ocaml/ocamlvars.mk in dose3's debian/rules > 3. directly use -output-complete-exe instead of -custom > 4. do not use -custom nor -output-complete-exe at all > > I tried 2 (which is actually 3) and it does not work because > -output-complete-exe is incompatible with -a, and -a and -custom are > used together somewhere in dose3 build system. > > 1 should be easy to implement (empty override of dh_strip) and upload, > if urgent. > > I am currently looking into 4. awesome, thank you for your input! We are currently changing the buildsystem of dose3 to dune, so the problem might even become moot (I didn't try yet). But in case it doesn't I now know what to try out. :) Since this is not a src:ocaml bug, feel free to close this. Also, why I am in contact with you, could you also comment on https://salsa.debian.org/ocaml-team/camlbz2/-/commit/2fb669b0ae4a37417ac32bcbeca0055173b4d8bd#note_209628 Thanks! cheers, josch signature.asc Description: signature
Bug#979424: ITP: sass-stylesheets-typey -- framework for working with typography in sass
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: sass-stylesheets-typey Version : 1.1.2 Upstream Author : Jack Taranto * URL : https://github.com/jptaranto/typey * License : Expat Programming Lang: Sass Description : framework for working with typography in sass Typey is a complete Sass framework for working with typography on the web. . * Takes px unit sizes in source and resolves to pt/rem/em/... in CSS * Handles typefaces as single units * Flexibly applies case, letter-spacing, or other advanced typesetting * Supports line-height based on vertical rhythm or ratio * Includes a set of base font stacks . Sass makes CSS fun again. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. . Sass can be encoded in either of two formats - SASS and SCSS. These mixins are provided in SCSS format. This package will be maintained in the Sass team. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/11zoACgkQLHwxRsGg ASGCaA//VHHTqdBjEyAavHPEqc9/kQu4E4qKiepUdD0bnfrcjU38NCS1eJKwF1Fb bAxo9lIOammLN5kP53GqLqrrSeR2wdNMzi8wpaOvA866H13TlXXC+4pOweORXXiK tc/icRyhdwX8+B2aToZrbzr7lk5ahn2ijm/qIs1Ko/U0oT5mu5kwvl3wh5MOQTSO U81w+YddCDpcbnlgxU1BZxAwLBGGleHf6zDEh/S/X//TpmdtBisFwW0Yl0glpI9s gXY7ZYMpGowCQ7+jDoolJAmDBEjLM6lvOeclXbyvd8JykZIKYZ6jQytxen+rHO2G BbtJAQDE4SGKlLurDTr2sf9koCSOpNkxTLkj9j/XBdhXeKL1hhsIFt2UrnyQlH4R LZKdV38b8wKF0SV4ermi7RUmVJ3siO89QHzS6rHDD49MtX+rvJeCoY4s4zzCBNcb bXSCEykEyturpUb6Di88WhB6xUx/vXJ5tH5Je+CkM5hhRANd+HeJNhROXscirh5z h5IOs2JdgqJqq2FfsTKiFjDKfsuF/UZrsmGUeM9jDJWNEFuEEfjU2N4E+Z9sYXTh ZWS3Q662VSQiPfLwldFqHrcS98t+BfIIflQdTDZgpHhRhUviXtb7lAFKSmdbuvyl BQc54TkHrIv6crpEHN4ermhd652p5Rcol0NOPdPxUgl7pDYHdI4= =r35+ -END PGP SIGNATURE-
Bug#979425: ITP: sass-stylesheets-gutenberg -- mixins for Sass for print-optimized styling
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: sass-stylesheets-gutenberg Version : 1.1.2 Upstream Author : Fabien Salathe * URL : https://github.com/BafS/Gutenberg * License : Expat Programming Lang: Sass Description : mixins for Sass for print-optimized styling Gutenberg.css provides Sass mixins for use with print media. . Sass makes CSS fun again. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. . Sass can be encoded in either of two formats - SASS and SCSS. These mixins are provided in SCSS format. This package will be maintained in the Sass team. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/1244ACgkQLHwxRsGg ASH1FA/+O5nQPADt+R6Co3suzpHiJ2taKvj21YnDORCecWBPlODln7d/ehUdl7lQ AjcP1nifzD8+Pf4IthxepIK6gMBSAnXFLT3PEvf4pPkwL/sQq6vokFLIjyCZEWiu KhElN8LM+8RKk2+VXJeBOHeoBerVYoR7hy1djjRloM/03OTU1KNV05bcTiZoWhLj /+8ZzdU5z1+2tlTrqRxEiMWK4pdPXCquPLDm2EaXSog0CZ4IFyf/7QmsoDd01rI7 RBuJOfs+uS+/o2zduuxxAt8Ne+8CGFQ0DLXe4uGkAU781HFOZkwxKY+H/sYRBUDM 3HyAoZ2mF655+inJoTQxZ+pVWtf2cXZiaE/IucbfKEYS2B90v3U4gSQUwyKJQKnE Thq48KtFK9QJliVYCIuph4d3vM/dJi/L4HW5vk4onnTIWQzdQxGk/1XK0G6yxhpo 6e/tAcF/LfPqb1iXReXd/kzhhh8hzXhSmdo1EHNjhbev+PV5lAfEqRJxF73cghxp 67JHUPOoLy24lxxznAQHOjVswypwQ6oe20idT0g0Zs03pLJzbfkrhWPWVCCyz7cj zvBUUOZ9NcL+svHDCqYTo0Qa0GLAuAfPx16XWBSNsFGwypc+VhE1aVqK5K2bBl6s hyDQbbR1stjRt57nCQVkA7BRrpuatff9X/lV3KTboz/YCsuNnQQ= =NJnD -END PGP SIGNATURE-
Bug#979426: missing linux-headers-amd64 prevents running dkms when kernel is updated in debian/contrib-testing64
Package: cloud.debian.org Severity: normal While upgrading the current debian/current-testing64 (half of 2020) under virtualbox provider: [...] /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 5.9.0-5-amd64:Error! Your kernel headers for kernel 5.9.0-5-amd64 cannot be found. Please install the linux-headers-5.9.0-5-amd64 package, or use the --kernelsourcedir option to tell DKMS where it's located [...] That's due to 5.6 -> 5.9 migration and missing of linux-headers-amd64 package apparently. -- System Information: Debian Release: 10.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#979427: src:libnet-ipaddress-perl: invalid maintainer address
Source: libnet-ipaddress-perl Version: 1.10-3 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Cyril Bouthors , Cyril Bouthors , Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Wed, 06 Jan 2021 15:53:01 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: cy...@debian-packaging.com Unrouteable address Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;cyril@debian-packaging.com Status: 5.0.0
Bug#979428: src:cvsdelta: invalid maintainer address
Source: cvsdelta Version: 1.7.0-6 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address (forwarded to from the maintainer's @d.o address) is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Tue, 05 Jan 2021 22:33:56 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: deb...@salix.org retry timeout exceeded Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;debian@salix.org Status: 5.0.0
Bug#979423: fixed upstream
It has been recently fixed upstream : https://github.com/fail2ban/fail2ban/commit/595ee7ed74a111b0ff15e2284fb4d05599df253a#diff-6525036f260a65a64215e1dacd52fed67bb8f9b330834c11238315997573e1bc -- François Poulain
Bug#979420: nautilus-kdeconnect: missing Breaks+Replaces: kdeconnect (<< 20.12)
Le 06/01/2021 à 14:53, Andreas Beckmann a écrit : Hi, Dear Andreas, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces Thank you for your bug report. It’s now fixed and uploaded. Happy hacking ! -- Aurélien
Bug#963444: [PATCH] Make lambdas use Guava's Java 8 (JRE) flavor
Debian only package Guava's Java 8+ (JRE) flavor in libguava-java,
not the Android flavor. The "Predicate" class of the JRE flavor
extends "java.util.function.Predicate", so the lambdas need to override
both the "apply()" and "test()" methods.
Find attached a patch to adopt the lambdas accordingly, to work with the
JRE flavor.
-- Lukas
Description: Make lambdas use Guava's Java 8 (JRE) flavor
Debian and Ubuntu only package Guava's Java 8+ (JRE) flavor in libguava-java,
not the Android flavor. The "Predicate" class of the JRE flavor extends
"java.util.function.Predicate", so the lambdas need to override both the
"apply()" and "test()" methods.
Author: Lukas Märdian
Bug: https://github.com/w3c/epubcheck/pull/833#issuecomment-367052775
Bug-Debian: https://bugs.debian.org/963444
Forwarded: https://bugs.debian.org/963444
Last-Update: 2021-01-06
--- epubcheck-4.2.4.orig/src/main/java/com/adobe/epubcheck/ocf/OCFChecker.java
+++ epubcheck-4.2.4/src/main/java/com/adobe/epubcheck/ocf/OCFChecker.java
@@ -359,6 +359,11 @@ public class OCFChecker
|| (validationVersion == EPUBVersion.VERSION_3
&& ((OPFHandler30) opfHandler).getLinkedResources().hasPath(entry));
}
+ @Override
+ public boolean test(OPFHandler opfHandler)
+ {
+return apply(opfHandler);
+ }
}).isPresent())
{
report.message(MessageId.OPF_003, EPUBLocation.create(ocf.getName()), entry);
--- epubcheck-4.2.4.orig/src/main/java/com/adobe/epubcheck/opf/MetadataSet.java
+++ epubcheck-4.2.4/src/main/java/com/adobe/epubcheck/opf/MetadataSet.java
@@ -237,6 +237,11 @@ public final class MetadataSet
{
return tryFind(meta.getRefiners(), property, value).isPresent();
}
+ @Override
+ public boolean test(Metadata meta)
+ {
+return apply(meta);
+ }
});
}
@@ -274,6 +279,11 @@ public final class MetadataSet
return property.equals(meta.getProperty())
&& (!value.isPresent() || value.get().equals(meta.getValue()));
}
+ @Override
+ public boolean test(Metadata meta)
+ {
+return apply(meta);
+ }
});
}
--- epubcheck-4.2.4.orig/src/main/java/com/adobe/epubcheck/opf/OPFChecker30.java
+++ epubcheck-4.2.4/src/main/java/com/adobe/epubcheck/opf/OPFChecker30.java
@@ -337,6 +337,11 @@ public class OPFChecker30 extends OPFChe
{
return item.get().getPath().equals(dict.getLocation().get().getPath());
}
+@Override
+public boolean test(Feature dict)
+{
+ return apply(dict);
+}
}).isPresent();
}
}
--- epubcheck-4.2.4.orig/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java
+++ epubcheck-4.2.4/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java
@@ -270,6 +270,11 @@ public final class ValidationContext
{
return input.properties.contains(property);
}
+@Override
+public boolean test(ValidationContext input)
+{
+ return apply(input);
+}
};
}
@@ -286,6 +291,11 @@ public final class ValidationContext
{
return input.pubTypes.contains(type);
}
+@Override
+public boolean test(ValidationContext input)
+{
+ return apply(input);
+}
};
}
@@ -302,6 +312,11 @@ public final class ValidationContext
{
return input.mimeType.equals(mimetype);
}
+@Override
+public boolean test(ValidationContext input)
+{
+ return apply(input);
+}
};
}
@@ -318,6 +333,11 @@ public final class ValidationContext
{
return input.path.equals(path);
}
+@Override
+public boolean test(ValidationContext input)
+{
+ return apply(input);
+}
};
}
@@ -334,6 +354,11 @@ public final class ValidationContext
{
return input.profile.equals(profile);
}
+@Override
+public boolean test(ValidationContext input)
+{
+ return apply(input);
+}
};
}
@@ -350,6 +375,11 @@ public final class ValidationContext
{
return input.version.equals(version);
}
+@Override
+public boolean test(ValidationContext input)
+{
+ return apply(input);
+}
};
}
--- epubcheck-4.2.4.orig/src/main/java/org/idpf/epubcheck/util/css/CssParser.java
+++ epubcheck-4.2.4/src/main/java/org/idpf/epubcheck/util/css/CssParser.java
@@ -705,6 +705,10 @@ public final class CssParser
checkNotNull(cc);
return cc.type != CssConstruct.Type.ATRULE; //TODO;
}
+ public boolean test(CssConstruct cc)
+ {
Bug#979430: RM: user-manager -- ROM; dropped upstream
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: Debian/Kubuntu Qt/KDE Maintainers Dear FTP Masters, user-manager has been dropped upstream in favor of a KCM configuration module integrated into Plasma’s systemsettings. As such it’s not maintained or useful anymore and should be removed from the archive. Thanks, -- Aurélien
Bug#979413: ITP: ptl -- parallel tasking library
Package: wnpp Severity: wishlist Owner: Stephan Lachnit * Package name: ptl Version : 1.0.0 * URL : https://github.com/jrmadsen/PTl/ * License : MIT Programming Lang: C++ Description : parallel tasking library Dependency of Geant4. Will maintain in the Science team. Regards, Stephan
Bug#976113: RFS Review for Hydrogen
Hi Ross, Sorry for the delay, so tired and busy here! Ross Gammon writes: > Please note, I was not able to do a test installation to check hydrogen > is working. I hope you can confirm that. > I can confirm it works for everything I use it for, but unfortunately I don't have any midi gear to test midi-related functionality. > Blocking upload: > 1. The package fails to build twice in a row (I used the --twice option > in pdebuild). It appears some translation files are not being cleaned > after the first build. > Thank you for spotting this. I've activated a build hook to catch cases like this in the future. Fixed, and fixed an assumption I had made about the translations. > Minor things: > 1. We could enable Salsa CI by adding a debian/salsa-ci.yml file. We could, but I don't think Hydrogen's test is significant enough to make it worthwhile to spin up an instance every time someone pushes to the repo (cost of resources, and cost of carbon footprint). > 2. I think the copyright-hints & check files can be removed as they were > used by cdbs? Done, queued for the source-only -2 upload > 3. The github issues page could be added to the upstream metadata > file. Is this user facing? I have been specifically omitting this from my packages, because I worry that it will make it more convenient for the user to click and report upstream, despite "Don't file bugs upstream" (https://www.debian.org/Bugs/Reporting). > 4. I am not sure what is going on with the icon. There is a lot going on > in d/rules and also a patch. This is probably something that should be > sorted out upstream. As a minimum we should probably forward our patch > upstream or tag the patch as "Forwarded: not-needed" if it is not an > upstream issue. I note that in Ubuntu, they install an svg into the > pixmaps folder. Yeah, it's confusing to me too, and yes, ought to be solved upstream. The png (erroneously named as a bmp) is used internally for something, and I'm not sure using the svg in that context would succeed, but it seems like it ought to be. The SVGs we install are: usr/share/hydrogen/data/img/gray/h2-icon.svg usr/share/hydrogen/data/img/gray/icon.svg usr/share/hydrogen/data/img/gray/warning.svg usr/share/icons/hicolor/scalable/apps/org.hydrogenmusic.Hydrogen.svg > 5. Patch 2001 should probably be tagged as "Forwarded: not-needed" as it > seems Debian specific. Done. Queued for -2. > 6. I see that even with all hardening options enabled in d/rules, we > still get the "hardening no fortify" lintian error. Are there some flags > not being passed to the build system? Possibly. I will investigate and plan to solve this for -2. > 7. I see the large number of commits to add library packages and upload > pre-release versions has resulted in some churn in the changelog. I > think some entries can be removed now that we have agreed to upload a > simpler structure and because it is a proper release (e.g. disabling the > documentation)? > I believe I cut the bin:lib-pkg ones, but I see I missed the docs ones. Fixed. > Suggestions/Considerations: > 1. It is worth taking a look at the version of hydrogen uploaded in > Ubuntu by Erich Eickmeyer. By adding ladspa-sdk and libtar as build > dependencies (and a patch), it appears that the hydrogen builds with > extra options. I considered enabling new features, but chose to change the package as little as possible, because we're so late in the bullseye cycle. I'm of course open to enabling them if someone else will thoroughly test the features. > Erich also switched the jack dependency to jack2. When building with libjack-dev, debhelper should indirectly generate a dependency on libjack-jackd2-0 | libjack-0.125. My rational for not switching is that I'm aware of users of older Firewire interfaces who prefer (or need) jack and not jack2. I also asked #debian-multimedia for confirmation that sticking with jack was consistent with team policy and received a firm statement to not switch to building against jack2-dev. > 2. I see we have added a lintian override for the desktop and appdata > files not being in the same package as the executable. Is there a reason > for not just installing the desktop/appdata files with the executable > instead of in -data? > If I remember correctly this was one of the previous maintainers' decisions, and I think it had to with putting everything is arch:all into the -data package--personally I think that's a reasonable design decision. bin:hydrogen Depends on bin:hydrogen-data, and bin:hydrogen-data Recommends bin:hydrogen, so they'll almost always both be installed. Do you know if appdata files should always go in the same package as the executable? Thanks again for taking the time to review and sponsor! Nicholas signature.asc Description: PGP signature
Bug#890994: nis: ypbind started when the computer start without network
severity 890994 wishlist tags 890994 + wontfix quit As explained by Mark, NIS is not tought for supporting intermittently connected clients. Also, in the next releases nis services will use systemd units and that would be used to switch off ypbind if the client is not connected to a netẇork. For that purpose, it will be enough: systemctl enable systemd-networkd.service systemd-networkd-wait-online.service And then add After=systemd-networkd-wait-online.service Wants=systemd-networkd-wait-online.service to the (future) ypbind.service. That should work even with DHCP. But it solves only partially the issue and not in general. What if you connect to another network? What if you are multi-homed? What if the NIS client is a laptop hosted in multiple variable networks, with more than one domain? NIS is simply not tought for this use cases, it is an old beast of the 80s. The simplest thing to do is using ad hoc scripts to on/off the service on the basis of local needs, it is simply not possible supporting all possible settings. On Wed, Feb 21, 2018 at 01:04:33PM +0100, adrien moulin wrote: Package: nis Version: 3.17.1-1+b1 Severity: normal Dear Maintainer, On stretch when i start without network, the computer is very slow to launch the graphical interface and when i try to login on tty console there are important latency. After research the origin of the problem, i found that /etc/nsswitch.conf tried to bind nis because ypbind is launch but without network it can't do it. It seems there are no timeout on this. I usually use laptop with nis client, on Jessie the nis.service do not start when the network cable was out but on Stretch it start with or without network cable. (on the laptop there are a new installation of debian not a distupgrade) The solution i have found is not very nice, i had in /etc/init.d/nis when the process is backgrouned a killall ypbind. I hope there are an other solution with systemd but i can't find out for now. -- Francesco P. Lovergine
Bug#979431: resolvconf: Unconditional use of systemctl
Package: resolvconf Version: 1.86 Severity: normal Hi! This package makes unconditional use of systemctl in at least the /etc/dhcp/dhclient-enter-hooks.d/resolvconf script, which on a sysvinit system then shows the following message: ,--- /sbin/dhclient-script: 19: /etc/dhcp/dhclient-enter-hooks.d/resolvconf: systemctl: not found `--- Thanks, Guillem
Bug#979432: ruby-rack FTBFS on IPV6-only buildds
Source: ruby-rack Version: 2.1.1-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ruby-rack&arch=all ... ┌──┐ │ Run tests for ruby2.7 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/<>/debian/ruby-rack/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<>/debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 -S rake -f debian/ruby-tests.rake /usr/bin/ruby2.7 -I"lib:test" "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" "test/spec_chunked.rb" "test/spec_common_logger.rb" "test/spec_conditional_get.rb" "test/spec_config.rb" "test/spec_content_length.rb" "test/spec_content_type.rb" "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" "test/spec_multipart.rb" "test/spec_null_logger.rb" "test/spec_recursive.rb" "test/spec_request.rb" "test/spec_response.rb" "test/spec_rewindable_input.rb" "test/spec_runtime.rb" "test/spec_sendfile.rb" "test/spec_server.rb" "test/spec_session_abstract_id.rb" "test/spec_session_abstract_session_hash.rb" "test/spec_session_cookie.rb" "test/spec_session_pool.rb" "test/spec_show_exceptions.rb" "test/spec_show_status.rb" "test/spec_static.rb" "test/spec_tempfile_reaper.rb" "test/spec_thin.rb" "test/spec_urlmap.rb" "test/spec_utils.rb" "test/spec_version.rb" "test/spec_webrick.rb" "test/gemloader.rb" Cannot load minitest-sprint >= 0 Run options: --seed 3819 # Running: S.S..S#>/test/spec_thin.rb:17 run> terminated with exception (report_on_exception is true): /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no acceptor (port is in use or requires root privileges) (RuntimeError) from /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_server' from /usr/lib/ruby/vendor_ruby/thin/backends/tcp_server.rb:16:in `connect' from /usr/lib/ruby/vendor_ruby/thin/backends/base.rb:63:in `block in start' from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run_machine' from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run' from /usr/lib/ruby/vendor_ruby/thin/backends/base.rb:73:in `start' from /usr/lib/ruby/vendor_ruby/thin/server.rb:162:in `start' from /<>/lib/rack/handler/thin.rb:24:in `run' from /<>/test/spec_thin.rb:18:in `block (3 levels) in ' E#>/test/spec_thin.rb:17 run> terminated with exception (report_on_exception is true): ... 1040 runs, 3730 assertions, 0 failures, 8 errors, 3 skips You have skipped tests. Run with --verbose for details. rake aborted! Command failed with status (1): [ruby -I"lib:test" "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" "test/spec_chunked.rb" "test/spec_common_logger.rb" "test/spec_conditional_get.rb" "test/spec_config.rb" "test/spec_content_length.rb" "test/spec_content_type.rb" "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" "test/spec_multipart.rb" "test/spec_null_logger.rb" "test/spec_recursive.rb" "test/spec_request.rb" "test/spec_response.rb" "test/spec_rewindable_input.rb" "test/spec_runtime.rb" "test/
Bug#979434: zfsutils-linux: fails to install if zfs module is not loaded
Package: zfsutils-linux Version: 0.8.6-1 Severity: normal X-Debbugs-Cc: andreimpope...@gmail.com Dear Maintainer, During install the package tries to start nfs-share.service, which fails in case the zfs module is not loaded, for whatever reason[1]. As far as I can tell the start of nfs-share.service is due to WantedBy=zfs.target which is started in postinst. A quick fix could be to add a condition like for zfs-mount.service, etc. ConditionPathIsDirectory=/sys/module/zfs [1] For some reason when installing the buster-backports package on buster the postinst of zfsutils-linux is run before attempting to build the zfs module, so this bug is always triggered if installing the package by itself (even though dkms-zfs is also installed in the dame run, due to the Recommends). Kind regards, Andrei -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.9.0-5-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.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 zfsutils-linux depends on: ii libblkid12.36.1-4 ii libc62.31-9 ii libnvpair1linux 0.8.6-1 ii libuuid1 2.36.1-4 ii libuutil1linux 0.8.6-1 ii libzfs2linux 0.8.6-1 ii libzpool2linux 0.8.6-1 ii python3 3.9.1-1 Versions of packages zfsutils-linux recommends: ii lsb-base11.1.0 ii zfs-dkms [zfs-modules] 0.8.6-1 pn zfs-zed Versions of packages zfsutils-linux suggests: ii nfs-kernel-server 1:1.3.4-4 pn samba-common-bin pn zfs-initramfs | zfs-dracut -- Configuration Files: /etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs' -- no debconf information
Bug#947534: mp3splt: diff for NMU version 2.6.2+20170630-3.1
Control: tags 947534 + patch
Control: tags 947534 + pending
Control: tags 957561 + patch
Control: tags 957561 + pending
Dear maintainer,
I've prepared an NMU for mp3splt (versioned as 2.6.2+20170630-3.1) and
will upload it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
kind regards, Andreas
diff -Nru mp3splt-2.6.2+20170630/debian/changelog mp3splt-2.6.2+20170630/debian/changelog
--- mp3splt-2.6.2+20170630/debian/changelog 2021-01-06 18:29:47.0 +0100
+++ mp3splt-2.6.2+20170630/debian/changelog 2021-01-06 17:59:57.0 +0100
@@ -1,3 +1,16 @@
+mp3splt (2.6.2+20170630-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use 3.0 (quilt) format, extract
+10_Properly-zero-initialise-the-ogg-and-vorbis-state-st.patch from diff.
+ * 20_mp3splt-gtk-0.9.2-fno-common.patch from Getoo: Fix gcc 10 build error.
+Closes: #957561
+ * Drop b-d on gnome-doc-utils, configure with --disable-gnome.
+Closes: #947534
+ * Add missing b-d on libdbus-glib-1-dev.
+
+ -- Andreas Metzler Wed, 06 Jan 2021 17:59:57 +0100
+
mp3splt (2.6.2+20170630-3) unstable; urgency=medium
* Drop support for things that are deprecated and/or unmaintained in GNOME:
diff -Nru mp3splt-2.6.2+20170630/debian/control mp3splt-2.6.2+20170630/debian/control
--- mp3splt-2.6.2+20170630/debian/control 2021-01-06 18:29:47.0 +0100
+++ mp3splt-2.6.2+20170630/debian/control 2021-01-06 17:59:02.0 +0100
@@ -2,11 +2,11 @@
Section: sound
Priority: optional
Maintainer: Ron Lee
-Build-Depends: debhelper (>= 7.0.15),
+Build-Depends: debhelper (>= 7.0.15), libdbus-glib-1-dev,
libogg-dev, libvorbis-dev, libflac-dev, libmad0-dev,
libid3tag0-dev, libltdl3-dev, libpcre3-dev, libgtk-3-dev,
libgstreamer1.0-dev, libgstreamer-plugins-base1.0-dev,
- audacious-dev, libaudclient-dev, gnome-doc-utils,
+ audacious-dev, libaudclient-dev,
doxygen, graphviz
Standards-Version: 4.1.3.0
Homepage: http://mp3splt.sourceforge.net/
diff -Nru mp3splt-2.6.2+20170630/debian/patches/10_Properly-zero-initialise-the-ogg-and-vorbis-state-st.patch mp3splt-2.6.2+20170630/debian/patches/10_Properly-zero-initialise-the-ogg-and-vorbis-state-st.patch
--- mp3splt-2.6.2+20170630/debian/patches/10_Properly-zero-initialise-the-ogg-and-vorbis-state-st.patch 1970-01-01 01:00:00.0 +0100
+++ mp3splt-2.6.2+20170630/debian/patches/10_Properly-zero-initialise-the-ogg-and-vorbis-state-st.patch 2021-01-06 17:59:57.0 +0100
@@ -0,0 +1,65 @@
+From 18f018cd774cb931116ce06a520dc0c5f9443932 Mon Sep 17 00:00:00 2001
+From: Ron
+Date: Wed, 27 Sep 2017 03:36:51 +0930
+Subject: [PATCH] Properly zero initialise the ogg and vorbis state structs
+
+This prevents things from exploding in flames if an error occurs and the
+code tries to unwind before the codec and container initialiser functions
+can all be called. It fixes the second issue indicated in CVE-2017-11333,
+which isn't the fault of libvorbis, it's caused by us passing junk data
+to vorbis_block_clear() when an invalid file is detected and we bail out
+before vorbis_block_init() gets called.
+
+Ideally, we should simplify all of this and get rid of most of the malloc
+farm there by embedding the needed structs in splt_ogg_state (instead of
+pointers to them), then just do a single malloc and memset for the whole
+lot - but that would be a much more intrusive change, so for now just
+ensure the allocated memory is all safely zeroed in the simplest manner.
+---
+ libmp3splt/plugins/ogg.c | 10 ++
+ 1 file changed, 10 insertions(+)
+
+diff --git a/libmp3splt/plugins/ogg.c b/libmp3splt/plugins/ogg.c
+index 50cc495..57745f1 100644
+--- a/libmp3splt/plugins/ogg.c
b/libmp3splt/plugins/ogg.c
+@@ -212,26 +212,36 @@ static splt_ogg_state *splt_ogg_v_new(int *error)
+ goto error;
+ }
+ memset(oggstate, 0, sizeof(splt_ogg_state));
++
+ if ((oggstate->sync_in = malloc(sizeof(ogg_sync_state)))==NULL)
+ {
+ goto error;
+ }
++ memset(oggstate->sync_in, 0, sizeof(ogg_sync_state));
++
+ if ((oggstate->stream_in = malloc(sizeof(ogg_stream_state)))==NULL)
+ {
+ goto error;
+ }
++ memset(oggstate->stream_in, 0, sizeof(ogg_stream_state));
++
+ if ((oggstate->vd = malloc(sizeof(vorbis_dsp_state)))==NULL)
+ {
+ goto error;
+ }
++ memset(oggstate->vd, 0, sizeof(vorbis_dsp_state));
++
+ if ((oggstate->vi = malloc(sizeof(vorbis_info)))==NULL)
+ {
+ goto error;
+ }
++ memset(oggstate->vi, 0, sizeof(vorbis_info));
++
+ if ((oggstate->vb = malloc(sizeof(vorbis_block)))==NULL)
+ {
+ goto error;
+ }
++ memset(oggstate->vb, 0, sizeof(vorbis_block));
+
+ if ((oggstate->headers = malloc(sizeof(splt_v_packet) * TOTAL_HEADER_PACKETS))==NULL)
+ {
+--
+2.29.2
+
diff -Nru mp3splt-2.6.2+20170630/debian/patches/20_mp3splt-gtk-0.9.2-fno-common.patch mp3splt-2.6.2+20170630/debian/patches/20_mp3splt-gtk-0.9.2-fno-common.patch
--- mp3splt
Bug#979435: src:archmbox: invalid maintainer address
Source: archmbox Version: 4.10.0-2 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Wed, 06 Jan 2021 16:48:51 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: stral...@email.it host mx.email.it [212.97.34.36] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;straluna@email.it Status: 5.0.0 Remote-MTA: dns; mx.email.it Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table
Bug#979436: resolvconf: Missing cleanup for obsolete dnscache conffile
Package: resolvconf Version: 1.86 Severity: normal Hi! This package used to ship the /etc/resolvconf/update.d/dnscache conffile, which stopped being shipped in version 1.75, but the conffile was never cleaned up in the maintainer scripts, so it is left behind in the system and marked as obsolete in the dpkg database. Thanks, Guillem
Bug#979355: src:sphinx-rtd-theme: embeds several Sass libraries that should be packaged separately
Control: block -1 by 979404 Hi again Jonas! On Tue, Jan 05, 2021 at 09:01:40PM +0100, Jonas Smedegaard wrote: > > Yes, it cannot use the newer release because Wyrm is incompatible with > > it: > > > > https://github.com/snide/wyrm/issues/12 > > That one concretely seems easy fixable - but that's easy to say, I know > :-) I just noticed that you already packaged all three dependencies and uploaded them to NEW. Thanks a lot for that — when you suggested me to file RFPs I definitely did not expect such speed :) Now, you say that it will be easy to port Wyrm to new Bourbon. Actually the current construction is quite fragile because of inter-dependencies: not only Wyrm needs to be switched to new Bourbon or Neat, but also sphinx-rtd-theme itself at the same time. My knowledge of SCSS is minimal so I can only say that patches are welcome. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#979437: zfsutils-linux: please install zpool and zfs binaries in [/usr]/bin instead of /sbin
Package: zfsutils-linux Version: 0.8.6-1 Severity: wishlist X-Debbugs-Cc: andreimpope...@gmail.com Hello, Various 'zpool' and 'zfs' sub-commands seem to work fine also for regular users (e.g. 'zpool status' and zpool/zfs 'get', list', etc.) It would be nice to have them in the user's default path though (same as e.g. systemctl), probably in /usr/bin (due to the merged /usr transition). Kind regards, Andrei -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.9.0-5-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.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 zfsutils-linux depends on: ii libblkid12.36.1-4 ii libc62.31-9 ii libnvpair1linux 0.8.6-1 ii libuuid1 2.36.1-4 ii libuutil1linux 0.8.6-1 ii libzfs2linux 0.8.6-1 ii libzpool2linux 0.8.6-1 ii python3 3.9.1-1 Versions of packages zfsutils-linux recommends: ii lsb-base11.1.0 ii zfs-dkms [zfs-modules] 0.8.6-1 pn zfs-zed Versions of packages zfsutils-linux suggests: ii nfs-kernel-server 1:1.3.4-4 pn samba-common-bin pn zfs-initramfs | zfs-dracut -- Configuration Files: /etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs' -- no debconf information
Bug#979312: vokoscreen-ng: Segmentation fault when screenAdded
severity 979312 important retitle 979312 vokoscreen-ng: Segmentation fault when install qt5dxcb-plugin forwarded 979312 https://github.com/vkohaupt/vokoscreenNG/issues/129 thanks The bug is really from vokoscreen-ng and has already been forwarded to the upstream. As it does not affect the entire functioning of the program, I down the severity to important. Thanks. -- ... ⢀⣴⠾⠻⢶⣦⠀ Thiago Andrade Marques ⣾⠁⢰⠒⠀⣿⡁ GPG: 4096R/F8CDB08B ⢿⡄⠘⠷⠚⠋⠀ GPG Fingerprint: 1D38 EE3C 624F 955C E1FA 3C85 5A30 3591 F8CD B08B ⠈⠳⣄
Bug#979429: RFS: node-gulp-tsb/4.0.5-1 [ITP] -- node-gulp-tsb
Control: reassign -1 sponsorship-requests On Mi, 06 ian 21, 16:17:38, VIVEK K J wrote: > Package: node-gulp-tsb > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "node-gulp-tsb": > > * Package name : node-gulp-tsb > Version : 4.0.5-1 > Upstream Author : Johannes Rieken > * URL : https://github.com/jrieken/gulp-tsb > * License : Expat > * Vcs : https://salsa.debian.org/vivekkj/node-gulp-tsb > Section : Javascript > > It builds those binary packages: > > node-gulp-tsb > > To access further information about this package, please visit the following > URL: > > https://www.npmjs.com/package/gulp-tsb > > This is a part of HedgeDoc packaging[1] > > Regards, > > Vivek K J > > [1] - https://wiki.debian.org/Javascript/Nodejs/Tasks/HedgeDoc Reassigning to correct (pseudo-)package. Kind regards, Andrei -- Looking after bugs assigned to unknown or inexistent packages signature.asc Description: PGP signature
Bug#971309: ansible: diff for NMU version 2.9.16+dfsg-1.1
Hi Sebastian, thanks, I acknowledge the NMU. I'm in the process of packaging ansible 2.10.x which will already contain the fix. So feel free to consider this bug closed. Regards, Lee On Wed, 6 Jan 2021 12:07:18 +0100 Sebastian Ramacher wrote: > Control: tags 971309 + patch > Control: tags 971309 + pending > > Dear maintainer, > > I've prepared an NMU for ansible (versioned as 2.9.16+dfsg-1.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. > > Cheers > -- > Sebastian Ramacher
Bug#979378: [Pkg-utopia-maintainers] Bug#979378: network-manager should drop unused Build-Depends
Hi Helmut, thanks a lot for the patch Am 05.01.21 um 22:56 schrieb Helmut Grohne: Source: network-manager Version: 1.28.0-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap network-manager has a number of Build-Depends and is involved in dependency cycles relevant to architecture bootstrap. Instead of looking into such cycles, a simpler measure is looking into entirely unused Build-Depends. As it happens, network-manager has those. According to debian/changelog, libyaml-perl was added to build the documentation. At this point nothing in the source mentions it in any way. I think it can be safely dropped. I guess libyaml-perl and perl can be dropped safely. The NEWS file kindly explains that since version 1.24, libpolkit-agent-1-dev and libpolkit-gobject-1-dev are no longer needed. While meson.build and configure.ac still check for polkit-agent, they're completely unused otherwise and network-manager now interacts with polkit via dbus and its own abstraction only. libpolkit-gobject-1-dev is no longer needed and can be dropped safely. libpolkit-agent-1-dev is still used to get the polkit package prefix: POLKIT_PACKAGE_PREFIX=`$PKG_CONFIG --variable=prefix polkit-agent-1` which is later used in clients/common/nm-polkit-listener.c:POLKIT_PACKAGE_PREFIX "/lib/polkit-1/polkit-agent-helper-1", There is a hard-coded fallback, but I'd rather keep the libpolkit-agent-1-dev Build-Depends. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#979438: gnome-passwordsafe: many SyntaxError messages during installation
Package: gnome-passwordsafe Version: 4.1-1 Severity: normal Hi, Here they are: # apt install gnome-passwordsafe Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: gnome-passwordsafe 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 366 kB of archives. After this operation, 1 298 kB of additional disk space will be used. Get:1 https://deb.debian.org/debian sid/main amd64 gnome-passwordsafe all 4.1-1 [366 kB] Fetched 366 kB in 0s (942 kB/s) Selecting previously unselected package gnome-passwordsafe. (Reading database ... 401455 files and directories currently installed.) Preparing to unpack .../gnome-passwordsafe_4.1-1_all.deb ... Unpacking gnome-passwordsafe (4.1-1) ... Setting up gnome-passwordsafe (4.1-1) ... Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/color_widget.py: File "/usr/lib/python3/dist- packages/passwordsafe/color_widget.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/custom_keypress_handler.py: File "/usr/lib/python3/dist-packages/passwordsafe/custom_keypress_handler.py" , line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/database_settings_dialog.py: File "/usr/lib/python3/dist-packages/passwordsafe/database_settings_dialog.p y", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/entry_page.py: File "/usr/lib/python3/dist- packages/passwordsafe/entry_page.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/entry_row.py: File "/usr/lib/python3/dist- packages/passwordsafe/entry_row.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/group_row.py: File "/usr/lib/python3/dist- packages/passwordsafe/group_row.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/notes_dialog.py: File "/usr/lib/python3/dist- packages/passwordsafe/notes_dialog.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/password_entry_row.py: File "/usr/lib/python3/dist- packages/passwordsafe/password_entry_row.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/password_generator_popover.py: File "/usr/lib/python3/dist-packages/passwordsafe/password_generator_popov er.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/properties_dialog.py: File "/usr/lib/python3/dist- packages/passwordsafe/properties_dialog.py", line 3 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/references_dialog.py: File "/usr/lib/python3/dist- packages/passwordsafe/references_dialog.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist-packages/passwordsafe/search.py: File "/usr/lib/python3/dist-packages/passwordsafe/search.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/selection_ui.py: File "/usr/lib/python3/dist- packages/passwordsafe/selection_ui.py", line 2 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined Failed to byte-compile /usr/lib/python3/dist- packages/passwordsafe/unlocked_database.py: File "/usr/lib/python3/dist- packages/passwordsafe/unlocked_database.py", line 3 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Sh
Bug#979439: hunspell-it: Italian spell check cannot recognize simple words
Package: hunspell-it Version: 1:7.1.0~rc1-1 Severity: normal X-Debbugs-Cc: livm...@hotmail.com Dear Maintainer, the Italian spell check is broken and cannot recognize common words like "di" or "è" and other terms with apostrophe or accent. It is possible to notice the problem simply copying the text of the Universal Declaration of Human Rights in Italian and trying a spell check on it. It will highlight in applications like LibreOffice or Gedit some part of the text even if it is right. Normally I should expect no mistake in the Declaration. If I try to use aspell-it in Gedit, the terms are correctly checked. Also the AppImage version of LibreOffice is not affected. My Debian version is Bullseye freshly updated. Thank you in advance, Best Regards -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/12 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 hunspell-it depends on: ii dictionaries-common 1.28.3 hunspell-it recommends no packages. Versions of packages hunspell-it suggests: ii hunspell1.7.0-3 ii libreoffice-writer 1:7.1.0~rc1-1 -- no debconf information
