Bug#985948: marked as done (libubootenv-tool: Debug lines from fw_printenv break RAUC)
Your message dated Tue, 06 Apr 2021 02:17:59 + with message-id and subject line Bug#985948: fixed in libubootenv 0.3-2 has caused the Debian Bug report #985948, regarding libubootenv-tool: Debug lines from fw_printenv break RAUC to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libubootenv-tool Version: 0.3-1 Severity: grave Hello, there are compatibility problems with RAUC and the libubootenv-tool package. RAUC requires the fw_setenv and fw_printenv utilites to interact with the u-boot-environment. After Installing the libubootenv-tool package to get fw_printenv and fw_setenv, RAUC didnt work properly. i.e.: $ rauc status ... === Bootloader === Activated: (null) ((null)) <-- should look like "Activated: rootfs.0 (A) ... The reason for this is that RAUC is not able to parse the output of fw_printenv with the added debug message "Environment OK, copy 0": $ fw_printenv BOOT_ORDER Environment OK, copy 0 BOOT_ORDER=B A After building a fw_printenv that doesnt print the Debug Mesaage the Rauc worked properly again. (I looked into the source code of libubootenv and saw that passing the NDEBUG compiler flag supresses the Debugging Messages: https://salsa.debian.org/debian/libubootenv/-/blob/master/src/uboot_env.c#L946) i.e: $ fw_printenv BOOT_ORDER BOOT_ORDER=B A $ rauc status ... === Bootloader === Activated: rootfs.1 (B) ... Perhaps it is desirable that libubootenv-tool provides output similiar to the native u-boot envtools to support compability, by building it in downstream with the NDEBUG compiler flag. Paul Jena -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.14.184-rt84-stable-16216-gdf370847d809 (SMP w/4 CPU threads; PR> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libubootenv-tool depends on: ii libc6 2.31-9 ii libubootenv0.1 0.3-1 ii zlib1g 1:1.2.11.dfsg-2 libubootenv-tool recommends no packages. libubootenv-tool suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libubootenv Source-Version: 0.3-2 Done: Nobuhiro Iwamatsu We believe that the bug you reported is fixed in the latest version of libubootenv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated libubootenv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 06 Apr 2021 09:45:58 +0900 Source: libubootenv Architecture: source Version: 0.3-2 Distribution: unstable Urgency: medium Maintainer: Nobuhiro Iwamatsu Changed-By: Nobuhiro Iwamatsu Closes: 969026 969216 985948 Changes: libubootenv (0.3-2) unstable; urgency=medium . [ Dave Jones ] * Added symbols for libubootenv0.1 (Closes: #969216) . [ Bastian Germann ] * Compile with NDEBUG set (Closes: #985948) * Let libubootenv-dev depend on zlib1g-dev (Closes: #969026) Checksums-Sha1: f04ebd1304ccd146838a13f4ec295ee20e599ef5 2126 libubootenv_0.3-2.dsc fc57373219f6be5a0c0bc670e2ca49a915198290 4348 libubootenv_0.3-2.debian.tar.xz ad4a4c6459e7acfa3236ad9ead7390b3a14e5ac3 9416 libubootenv_0.3-2_amd64.buildinfo Checksums-Sha256: 43229c7c3f77e54a65da805f54a34dcb58fcb3a235509d58887c8a645534b2d5 2126 libubootenv_0.3-2.dsc 9b08b97d8e9fe05fa5f73b1803520c4a4f969c3b30d1c9a8cee4f11491690314 4348 libubootenv_0.3-2.debian.tar.xz 4c95303789d5ccd15fce4045be0f40c85cca54e3070c4d18535b50734e2f 9416 libubootenv_0.3-2_amd64.buildinfo Files: 3170990f7c0d3611adf5d4e571f793a1 2126 utils optional libubootenv_0.3-2.dsc 8f4dab44943347d91c80d712a6238711 4348 utils optional libubootenv_0.3-2.debian.tar.xz 52c62a2ef2bbae307127be1f997125e6 9416 utils optional libubootenv_0.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXmKe5SMh
Bug#892275: Redshift under xfce4
Hi, chipping in with my experience under xfce4. First, I'm using a manual config file with lat./long. information, so I can't comment on the geoclue part of the conversation. However, I had problems when trying to manually kill redshift, because systemd would restart the service, ending up with my screen getting progressively more red.. To summarize, my current solution is to deactivate the systemd service and use xfce4 specific session startup along with a manual config file. Hope this helps someone.
Processed: not RC in lsb-release
Processing commands for cont...@bugs.debian.org: > severity 986408 normal Bug #986408 [lsb-release] ValueError: could not convert string to float: '6.06 LTS' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 986408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986408: mali-midgard-dkms: Fail to install/build
On 2021-04-05 14:32 +0200, Christian Marillat wrote: > Package: mali-midgard-dkms > Version: 16.0+pristine-4 > Severity: serious > > Dear Maintainer, > > This package fail to install/build with : Hmm. I meant to remove this package as the state of the free drivers (panfrost) is such that there is no real point debian maintaining this free wrapper for the non-free driver any longer (and certainly not for a whole stable cycle). Looks like I failed to get round to filing a remove bug. I'll do that if it's not too late. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#986436: node-tldjs: modifies shipped files: /usr/lib/nodejs/tldjs/rules.json
Package: node-tldjs Version: 2.3.1-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 0m48.9s ERROR: FAIL: debsums reports modifications inside the chroot: /usr/lib/nodejs/tldjs/rules.json The shipped file has -rw-r--r-- 1 root root 146771 Apr 1 2018 /usr/lib/nodejs/tldjs/rules.json while the file found after the uprade has -rw-r--r-- 1 root root 160230 Apr 5 21:53 /usr/lib/nodejs/tldjs/rules.json This only seems to happen if --install-recommends is enabled. cheers, Andreas node-tldjs_2.3.1-1.1.log.gz Description: application/gzip
Bug#986434: kmail FTBFS: /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libKF5MailCommon.so.5.15.3.abi2: undefined reference to `MessageCore::MailingList::MailingList()@ABI_5_1'
Source: kmail Version: 4:20.08.3-1 Severity: serious Tags: ftbfs kmail fails to build from source in unstable on amd64. It runs into a pile of linker errors while linking the kmail executable. Example: | /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libKF5MailCommon.so.5.15.3.abi2: undefined reference to `MessageCore::MailingList::MailingList()@ABI_5_1' Maybe libkf5mailcommon5abi2 is underlinked? Please reassign the bug if necessary. Seems to be a fairly recent issue as reproducible.d.n didn't run into it on 2021-03-24. I don't see what could have caused this. Should be trivially reproducible though. Helmut
Bug#986429: marked as done (nettle: FTBFS on arm{el,hf}: missing symbols)
Your message dated Mon, 05 Apr 2021 22:44:15 +0200
with message-id <4226550.zzfL3KEAxe@johansson>
and subject line Re: Bug#986429: nettle: FTBFS on arm{el,hf}: missing symbols
has caused the Debian Bug report #986429,
regarding nettle: FTBFS on arm{el,hf}: missing symbols
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nettle
Version: 3.7.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
--- debian/libnettle8.symbols (libnettle8_3.7.2-2_armel)
+++ dpkg-gensymbolsJpEqc7 2021-04-05 18:28:14.466650127 +
@@ -35,8 +35,8 @@
(arch=ppc64 ppc64el)_nettle_chacha_4core@NETTLE_INTERNAL_8_3 3.7.2
_nettle_chacha_core@NETTLE_INTERNAL_8_3 3.7.2
(arch=ppc64 ppc64el)_nettle_chacha_core_altivec@NETTLE_INTERNAL_8_3 3.7.2
- (arch=armel armhf ppc64 ppc64el)_nettle_chacha_core_c@NETTLE_INTERNAL_8_3
3.7.2
- (arch=armel armhf)_nettle_chacha_core_neon@NETTLE_INTERNAL_8_3 3.7.2
+#MISSING: 3.7.2-2# (arch=armel armhf ppc64
ppc64el)_nettle_chacha_core_c@NETTLE_INTERNAL_8_3 3.7.2
+#MISSING: 3.7.2-2# (arch=armel
armhf)_nettle_chacha_core_neon@NETTLE_INTERNAL_8_3 3.7.2
(arch=armel armhf ppc64
ppc64el)_nettle_chacha_crypt32_1core@NETTLE_INTERNAL_8_3 3.7.2
(arch=armel armhf)_nettle_chacha_crypt32_3core@NETTLE_INTERNAL_8_3 3.7.2
(arch=ppc64 ppc64el)_nettle_chacha_crypt32_4core@NETTLE_INTERNAL_8_3 3.7.2
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:4: binary-arch] Error 25
See
https://buildd.debian.org/status/fetch.php?pkg=nettle&arch=armel&ver=3.7.2-2&stamp=1617647308&raw=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.7.2-3
Thanks; I noticed and I think I already had uploaded a new version.
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Bug#986256: marked as done (simka: flaky amd64 autopkgtest: regularly times out after 2:47 h)
Your message dated Mon, 05 Apr 2021 20:20:33 + with message-id and subject line Bug#986256: fixed in simka 1.5.3-3 has caused the Debian Bug report #986256, regarding simka: flaky amd64 autopkgtest: regularly times out after 2:47 h to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: simka Version: 1.5.3-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), Your package has an autopkgtest, great. However, I looked into the history of your autopkgtest [1] and I noticed version 1.5.3-2 fails regularly on amd64, while sporadically a rerun passes. I copied some of the output at the bottom of this report. It hits the autopkgtest time out after 2hours and 47 minutes. Successful runs pass in less than a minute. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Paul [1] https://ci.debian.net/packages/s/simka/testing/amd64/ https://ci.debian.net/data/autopkgtest/testing/amd64/s/simka/11355132/log.gz Computing stats... Stats Reads Total:8470M0G Min:980M0G Max:4020M0G Average:1690M0G Kmers Distinct Kmers (before merging):146700M0G Distinct Kmers (after merging):81230M0G Shared distinct Kmers:43220M0G Kmers:501300M0G Mean k-mer coverage: 2.66341 Output dir: ./simka_results/ *** Test: PASSED Command used: /usr/bin/simka -in ../example/simka_input.txt -out ./simka_results/ -out-tmp ./simka_temp_output Command for visualizing results: python ../scripts/visualization/run-visualization.py -in ./simka_results/ -out ./simka_results/ -pca -heatmap -tree Command for visualizing results with metadata annotations: python ../scripts/visualization/run-visualization.py -in ./simka_results/ -out ./simka_results/ -pca -heatmap -tree -metadata-in ../example/dataset_metadata.csv -metadata-variable VARIABLE_1 autopkgtest [07:42:20]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/build.NZn/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.zk5p_5wg/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=48; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod +x /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/build.NZn/src/debian/tests/run-unit-test; touch /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stdout /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stderr; /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/build.NZn/src/debian/tests/run-unit-test 2> >(tee -a /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.zk5p_5wg/downtmp/run-unit-test-stdout);" (kind: test) autopkgtest [07:42:20]: test run-unit-test: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: simka Source-Version: 1.5.3-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of simka, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 986.
Processed: Re: Bug#953947: debci: arm64 autopkgtest regularly times out
Processing control commands: > severity -1 serious Bug #953947 [src:debci] debci: arm64 autopkgtest regularly times out Severity set to 'serious' from 'normal' > retitle -1 debci: autopkgtest regularly times out Bug #953947 [src:debci] debci: arm64 autopkgtest regularly times out Changed Bug title to 'debci: autopkgtest regularly times out' from 'debci: arm64 autopkgtest regularly times out'. -- 953947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986256: [RFS] simka: test failure common denominator ci-worker13
Control: forwarded -1 https://github.com/GATB/simka/issues/20 Nilesh Patra, on 2021-04-06 01:00:04 +0530: > On 4/6/21 12:29 AM, Étienne Mollier wrote: > > Hi Paul, Hi Nilesh, > > feel also free to grant dm rights if you feel > > appropriate. > Done Thanks Nilesh, forwarded upstream and uploaded! :) Kind Regards, -- É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
Processed: Re: [RFS] simka: test failure common denominator ci-worker13
Processing control commands: > forwarded -1 https://github.com/GATB/simka/issues/20 Bug #986256 [src:simka] simka: flaky amd64 autopkgtest: regularly times out after 2:47 h Set Bug forwarded-to-address to 'https://github.com/GATB/simka/issues/20'. -- 986256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#892275: redshift: Unable to connect to GeoClue
Control: reassign -1 redshift 1.11-1 Control: retitle -1 redshift shouldn't start itself via systemd Hi, On Thu, 4 Feb 2021 14:29:55 +0100 Laurent Bigonville wrote: > IMVHO, you should remove the redshift systemd file and let redshift > start via de xdg autostart mechanism. The geoclue agent should then be > started before redshift as I think it start the process using the > alphabetical order. So, I think reassigning back to redshift makes most sense after this assessment (which makes sense to me, albeit being non-expert). Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: redshift: Unable to connect to GeoClue
Processing control commands: > reassign -1 redshift 1.11-1 Bug #892275 [geoclue-2.0] redshift: Unable to connect to GeoClue. Bug reassigned from package 'geoclue-2.0' to 'redshift'. Ignoring request to alter found versions of bug #892275 to the same values previously set Ignoring request to alter fixed versions of bug #892275 to the same values previously set Bug #892275 [redshift] redshift: Unable to connect to GeoClue. Marked as found in versions redshift/1.11-1. > retitle -1 redshift shouldn't start itself via systemd Bug #892275 [redshift] redshift: Unable to connect to GeoClue. Changed Bug title to 'redshift shouldn't start itself via systemd' from 'redshift: Unable to connect to GeoClue.'. -- 892275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986256: [RFS] simka: test failure common denominator ci-worker13
On 4/6/21 12:29 AM, Étienne Mollier wrote: > Hi Paul, Hi Nilesh, > feel also free to grant dm rights if you feel > appropriate. Done signature.asc Description: OpenPGP digital signature
Bug#986429: nettle: FTBFS on arm{el,hf}: missing symbols
Source: nettle Version: 3.7.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org --- debian/libnettle8.symbols (libnettle8_3.7.2-2_armel) +++ dpkg-gensymbolsJpEqc7 2021-04-05 18:28:14.466650127 + @@ -35,8 +35,8 @@ (arch=ppc64 ppc64el)_nettle_chacha_4core@NETTLE_INTERNAL_8_3 3.7.2 _nettle_chacha_core@NETTLE_INTERNAL_8_3 3.7.2 (arch=ppc64 ppc64el)_nettle_chacha_core_altivec@NETTLE_INTERNAL_8_3 3.7.2 - (arch=armel armhf ppc64 ppc64el)_nettle_chacha_core_c@NETTLE_INTERNAL_8_3 3.7.2 - (arch=armel armhf)_nettle_chacha_core_neon@NETTLE_INTERNAL_8_3 3.7.2 +#MISSING: 3.7.2-2# (arch=armel armhf ppc64 ppc64el)_nettle_chacha_core_c@NETTLE_INTERNAL_8_3 3.7.2 +#MISSING: 3.7.2-2# (arch=armel armhf)_nettle_chacha_core_neon@NETTLE_INTERNAL_8_3 3.7.2 (arch=armel armhf ppc64 ppc64el)_nettle_chacha_crypt32_1core@NETTLE_INTERNAL_8_3 3.7.2 (arch=armel armhf)_nettle_chacha_crypt32_3core@NETTLE_INTERNAL_8_3 3.7.2 (arch=ppc64 ppc64el)_nettle_chacha_crypt32_4core@NETTLE_INTERNAL_8_3 3.7.2 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:4: binary-arch] Error 25 See https://buildd.debian.org/status/fetch.php?pkg=nettle&arch=armel&ver=3.7.2-2&stamp=1617647308&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#986256: [RFS] simka: test failure common denominator ci-worker13
Hi Paul, Hi Nilesh, when looking up that issue today, I noticed on the CI web page[1], that all tests were failing on one given host, which is ci-worker13. I would thus suspect, that the failure is triggered by some hardware specific configuration: maybe core count (ci-worker13 reports builds with 48 parallel jobs), memory size, or something more exotic. [1]: https://ci.debian.net/packages/s/simka/testing/amd64/ Looking then further, I think I'm on a good trail on the high cores count hypothesis. I can reproduce some severe slowdowns using qemu with 48 cpus overcommit, or even less. Actually I could bissect clunky execution speed of the test case past 8 cpu cores allocated. As far as I can tell, passing CI runs only occurred on 2 cpu cores count machines, so they seem consistent with my own observations. I brought a change on simka run-unit-test on Salsa[2], to cap the execution of simka to 8 cores in the context of the test and address the issue. simka 1.5.3-3 is available for review, and possibly upload, feel also free to grant dm rights if you feel appropriate. Note that CI pipeline is on hold, but I expect the blhc test to fail due to missing compilation flags; other CI tests did seem to pass on my end. [2]: https://salsa.debian.org/med-team/simka/ Hopefully the slowdown is specific to the test case, but this might need to be brought upstream. Thanks for having caught it! Kind Regards, -- É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#986427: psgml: causes emacs-gtk to fail to upgrade from buster to bullseye
Package: psgml Version: 1.4.0-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. This problem was observed by first performing 'apt-get upgrade' (which upgrades psgml) followed by 'apt-get dist-upgrade' (which upgrades emacs-gtk). It does not happen if only 'apt-get dist-upgrade' is executed, i.e. both packages are upgraded in one run. --install-recommends was disabled during all these tests From the attached log (scroll to the bottom...): [... during apt-get upgrade ...] Preparing to unpack .../78-psgml_1.4.0-11_all.deb ... Remove psgml for emacs remove/psgml: Ignoring emacsen flavor emacs. Remove psgml for emacs remove/psgml: Ignoring emacsen flavor emacs. Unpacking psgml (1.4.0-11) over (1.4.0-7) ... [...] Setting up psgml (1.4.0-11) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install psgml for emacs install/psgml: Byte-compiling for emacs...Loading /etc/emacs/site-start.d/00debian.el (source)... In toplevel form: psgml.el:719:26:Warning: (lambda (foo) ...) quoted with ' rather than with #' In sgml-mode: psgml.el:1225:52:Warning: assignment to free variable `which-func-format' In sgml-set-buffer-multibyte: psgml-parse.el:365:16:Warning: assignment to free variable `mc-flag' In sgml-set-active-dtd-indicator: psgml-parse.el:2898:47:Warning: assignment to free variable `which-func-mode' In sgml-kill-markup: psgml-edit.el:247:4:Warning: value returned from (/= 0 (skip-chars-forward " ")) is unused psgml-edit.el:247:4:Warning: value returned from (= 0 (skip-chars-forward " ")) is unused psgml-edit.el:247:4:Warning: value returned from (= (skip-chars-forward " ") 0) is unused In sgml-edit-external-entity: psgml-edit.el:1975:62:Warning: Use `with-current-buffer' rather than save-excursion+set-buffer psgml-edit.el:1977:24:Warning: `process-kill-without-query' is an obsolete function (as of 22.1); use `process-query-on-exit-flag' or `set-process-query-on-exit-flag'. In sgml-append-to-help-buffer: psgml-edit.el:2177:36:Warning: Use `with-current-buffer' rather than save-excursion+set-buffer In sgml-show-structure: psgml-edit.el:2412:6:Warning: Use `with-current-buffer' rather than save-excursion+set-buffer In end of data: psgml-edit.el:2475:1:Warning: the function `string-to-int' is not known to be defined. In sgml-parse-entity-type: psgml-dtd.el:646:8:Warning: value returned from (/= 0 (skip-chars-forward " ")) is unused psgml-dtd.el:646:8:Warning: value returned from (= 0 (skip-chars-forward " ")) is unused psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward " ") 0) is unused psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward " ") 0) is unused psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward " ") 0) is unused In sgml-write-dtd: psgml-dtd.el:1010:9:Warning: assignment to free variable `file-type' In end of data: psgml-dtd.el:1016:1:Warning: the function `string-to-int' is not known to be defined. Done compiling WARNING: tempfile is deprecated; consider using mktemp instead. Creating config file /etc/emacs/site-start.d/50psgml-init.el with new version done. [... during subsequent apt-get dist-upgrade ...] Preparing to unpack .../02-emacs-gtk_1%3a27.1+1-3_amd64.deb ... Remove psgml for emacs remove/psgml: Removing for emacs... done. Remove emacsen-common for emacs emacsen-common: Handling removal of emacsen flavor emacs Unpacking emacs-gtk (1:27.1+1-3) over (1:26.1+1-3.2+deb10u2) ... [...] Setting up emacs-gtk (1:27.1+1-3) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install psgml for emacs install/psgml: Byte-compiling for emacs...cp: cannot stat 'Makefile-el': No such file or directory ERROR: install script from psgml package failed dpkg: error processing package emacs-gtk (--configure): installed emacs-gtk package post-installation script subprocess returned error exit status 1 Setting up librsvg2-common:amd64 (2.50.3+dfsg-1) ... Setting up systemd-timesyncd (247.3-3) ... Created symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service. Setting up systemd (247.3-3) ... Installing new version of config file /etc/systemd/journald.conf ... Installing new version of config file /etc/systemd/logind.conf ... Installing new version of config file /etc/systemd/networkd.conf ... Installing new version of config file /etc/systemd/resolved.conf ... Installing new version of config file /etc/systemd/system.conf ... Installing new version o
Processed: Re: Bug#986408: mali-midgard-dkms: Fail to install/build
Processing commands for cont...@bugs.debian.org: > reassign 986408 lsb-release Bug #986408 [lsb-release] ValueError: could not convert string to float: '6.06 LTS' Ignoring request to reassign bug #986408 to the same package > tags 986408 patch Bug #986408 [lsb-release] ValueError: could not convert string to float: '6.06 LTS' Ignoring request to alter tags of bug #986408 to the same tags previously set > retitle 986408 ValueError: could not convert string to float: '6.06 LTS' Bug #986408 [lsb-release] ValueError: could not convert string to float: '6.06 LTS' Ignoring request to change the title of bug#986408 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 986408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#986408: mali-midgard-dkms: Fail to install/build
Processing commands for cont...@bugs.debian.org: > reassign 986408 lsb-release Bug #986408 [mali-midgard-dkms] mali-midgard-dkms: Fail to install/build Bug reassigned from package 'mali-midgard-dkms' to 'lsb-release'. No longer marked as found in versions mali-midgard/16.0+pristine-4. Ignoring request to alter fixed versions of bug #986408 to the same values previously set > tags 986408 patch Bug #986408 [lsb-release] mali-midgard-dkms: Fail to install/build Added tag(s) patch. > retitle 986408 ValueError: could not convert string to float: '6.06 LTS' Bug #986408 [lsb-release] mali-midgard-dkms: Fail to install/build Changed Bug title to 'ValueError: could not convert string to float: '6.06 LTS'' from 'mali-midgard-dkms: Fail to install/build'. > thanks Stopping processing here. Please contact me if you need assistance. -- 986408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986408: mali-midgard-dkms: Fail to install/build
On 05 avril 2021 17:28, Chris Hofstaedtler wrote: > Hello Christian, Hello Chris, [...] >> RELEASES_ORDER.sort(key=lambda n: float(n[0])) >> File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in >> RELEASES_ORDER.sort(key=lambda n: float(n[0])) >> ValueError: could not convert string to float: '6.06 LTS' > > Please try running this, and see if that also fails: > > lsb_release -s -i > > I think your system configuration confuses lsb_release. If so, > please reassign to lsb-release. Yes this is a bug in lsb-release. I'll reassign to lsb-release. Otherwise mali-midgard-dkms fail to build with latest 5.10 kernel. Christian
Bug#986161: fixed in droopy 0.20160830-4
Hi, On Sat, Apr 03, 2021 at 02:17:47PM +, Debian FTP Masters wrote: > Binary: droopy > Architecture: source all Please note that you uploaded binaries. If you want the fix to (potentially) migrate to testing, you'll need to do a new source-only upload (and file an unblock request after that). Cheers, Ivo
Bug#978334: marked as done (php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage())
Your message dated Mon, 05 Apr 2021 16:48:22 + with message-id and subject line Bug#978334: fixed in phpdox 0.12.0-5 has caused the Debian Bug report #978334, regarding php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-finder-facade Version: 1.2.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > phpab \ > --template debian/autoload.php.in \ > --output src/autoload.php \ > src > phpab %development% - Copyright (C) 2009 - 2020 by Arne Blankerts and > Contributors > > Scanning directory src > > Autoload file src/autoload.php generated. > > cd debian && phpdox > phpDox 0.12.0-dev - Copyright (C) 2010 - 2020 by Arne Blankerts and > Contributors > > [26.12.2020 - 18:42:54] Using config file './phpdox.xml' > [26.12.2020 - 18:42:54] Registered collector backend 'parser' > [26.12.2020 - 18:42:54] Registered enricher 'build' > [26.12.2020 - 18:42:54] Registered enricher 'git' > [26.12.2020 - 18:42:54] Registered enricher 'checkstyle' > [26.12.2020 - 18:42:54] Registered enricher 'phpcs' > [26.12.2020 - 18:42:54] Registered enricher 'pmd' > [26.12.2020 - 18:42:54] Registered enricher 'phpunit' > [26.12.2020 - 18:42:54] Registered enricher 'phploc' > [26.12.2020 - 18:42:54] Registered output engine 'xml' > [26.12.2020 - 18:42:54] Registered output engine 'html' > [26.12.2020 - 18:42:54] Starting to process project 'FinderFacade' > [26.12.2020 - 18:42:54] Starting collector > [26.12.2020 - 18:42:54] Scanning directory '../src' for files to process > > ..[2] > > [26.12.2020 - 18:42:54] Saving results to directory 'phpdox' > [26.12.2020 - 18:42:54] Resolving inheritance > > [26.12.2020 - 18:42:54] '/usr/bin/dependencies/php/index.xml' not found - > skipping dependency > ..[2] > > [26.12.2020 - 18:42:54] Collector process completed > > [26.12.2020 - 18:42:54] Starting generator > [26.12.2020 - 18:42:54] Loading enrichers > [26.12.2020 - 18:42:54] Enricher Build Information initialized successfully > [26.12.2020 - 18:42:54] Starting event loop. > > . [33] > > [26.12.2020 - 18:42:54] Generator process completed > [26.12.2020 - 18:42:54] Processing project 'FinderFacade' completed. > > > > > Oups... phpDox encountered a problem and has terminated! > > It most likely means you've found a bug, so please file a report for this > and paste the following details and the stacktrace (if given) along: > > PHP Version: 7.4.11 (Linux) > PHPDox Version: 0.12.0-dev > Exception: Error (Code: 0) > Location: /usr/share/php/TheSeer/phpDox/logger/ShellProgressLogger.php (Line > 91) > > Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() > > #0 /usr/bin/phpdox(51): TheSeer\phpDox\CLI->run() > > > > make[1]: *** [debian/rules:7: override_dh_auto_build] Error 5 The full build log is available from: http://qa-logs.debian.net/2020/12/26/php-finder-facade_1.2.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: phpdox Source-Version: 0.12.0-5 Done: David Prévot We believe that the bug you reported is fixed in the latest version of phpdox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 978...@bugs.debian.org, and
Processed: retitle 986422 to Does not work with current DHCP servers
Processing commands for cont...@bugs.debian.org: > retitle 986422 Does not work with current DHCP servers Bug #986422 [autodns-dhcp] RM: autodns-dhcp -- ROM; Old package not working with current dhcp servers. Changed Bug title to 'Does not work with current DHCP servers' from 'RM: autodns-dhcp -- ROM; Old package not working with current dhcp servers.'. > thanks Stopping processing here. Please contact me if you need assistance. -- 986422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 985708, reassign -1 to autodns-dhcp, severity of -1 is grave
Processing commands for cont...@bugs.debian.org: > clone 985708 -1 Bug #985708 [ftp.debian.org] RM: autodns-dhcp -- ROM; Old package not working with current dhcp servers. Bug 985708 cloned as bug 986422 > reassign -1 autodns-dhcp Bug #986422 [ftp.debian.org] RM: autodns-dhcp -- ROM; Old package not working with current dhcp servers. Bug reassigned from package 'ftp.debian.org' to 'autodns-dhcp'. Ignoring request to alter found versions of bug #986422 to the same values previously set Ignoring request to alter fixed versions of bug #986422 to the same values previously set > severity -1 grave Bug #986422 [autodns-dhcp] RM: autodns-dhcp -- ROM; Old package not working with current dhcp servers. Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 985708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985708 986422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986408: mali-midgard-dkms: Fail to install/build
Hello Christian, * Christian Marillat [210405 15:26]: > This package fail to install/build with : > > $ sudo apt-get dist-upgrade > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] > Setting up mali-midgard-dkms (16.0+pristine-4) ... > Building for 5.10.0-5-arm64 > Traceback (most recent call last): > File "/usr/bin/lsb_release", line 95, in > main() > File "/usr/bin/lsb_release", line 59, in main > distinfo = lsb_release.get_distro_information() > File "/usr/lib/python3/dist-packages/lsb_release.py", line 356, in > get_distro_information > distinfo = guess_debian_release() > File "/usr/lib/python3/dist-packages/lsb_release.py", line 246, in > guess_debian_release > get_distro_info(distinfo['ID']) > File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in > get_distro_info > RELEASES_ORDER.sort(key=lambda n: float(n[0])) > File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in > RELEASES_ORDER.sort(key=lambda n: float(n[0])) > ValueError: could not convert string to float: '6.06 LTS' Please try running this, and see if that also fails: lsb_release -s -i I think your system configuration confuses lsb_release. If so, please reassign to lsb-release. Best, Chris
Processed: limit source to phpdox, tagging 978334
Processing commands for cont...@bugs.debian.org: > limit source phpdox Limiting to bugs with field 'source' containing at least one of 'phpdox' Limit currently set to 'source':'phpdox' > tags 978334 + pending Bug #978334 [phpdox] php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage() Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 978334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sphinxsearch: Still maintained (same version since stretch)?
Processing commands for cont...@bugs.debian.org: > severity 939763 serious Bug #939763 [src:sphinxsearch] sphinxsearch: Still maintained (same version since stretch)? Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 939763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986171: marked as done (underscore: CVE-2021-23358)
Your message dated Mon, 05 Apr 2021 13:32:33 + with message-id and subject line Bug#986171: fixed in underscore 1.9.1~dfsg-1+deb10u1 has caused the Debian Bug report #986171, regarding underscore: CVE-2021-23358 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: underscore Version: 1.9.1~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team ,y...@debian.org Hi, The following vulnerability was published for underscore. CVE-2021-23358[0]: | The package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 | and before 1.12.1 are vulnerable to Arbitrary Code Execution via the | template function, particularly when a variable property is passed as | an argument as it is not sanitized. [1] provides a POC to verify the issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-23358 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358 [1] https://snyk.io/vuln/SNYK-JS-UNDERSCORE-1080984 Regards, Salvatore --- End Message --- --- Begin Message --- Source: underscore Source-Version: 1.9.1~dfsg-1+deb10u1 Done: Yadd We believe that the bug you reported is fixed in the latest version of underscore, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated underscore package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 30 Mar 2021 22:54:09 +0200 Source: underscore Binary: libjs-underscore node-underscore Architecture: source all Version: 1.9.1~dfsg-1+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Javascript Maintainers Changed-By: Yadd Description: libjs-underscore - JavaScript's functional programming helper library node-underscore - JavaScript's functional programming helper library - NodeJS Closes: 986171 Changes: underscore (1.9.1~dfsg-1+deb10u1) buster-security; urgency=high . * Team upload * Fix arbitrary code execution (Closes: #986171) Checksums-Sha1: 14c53f6b548c8eed71a8c7b2767a93680feba49a 2152 underscore_1.9.1~dfsg-1+deb10u1.dsc 49afe4a08ef6de8faee938c153ec68b436a49bda 138080 underscore_1.9.1~dfsg.orig.tar.xz 9346893b3388aea67b5d8089a2e5f9b93b979e66 9076 underscore_1.9.1~dfsg-1+deb10u1.debian.tar.xz 2fd0a642957d214ba1aacba7c273805c0508e654 99968 libjs-underscore_1.9.1~dfsg-1+deb10u1_all.deb 3bda2ec92f31ef2c78197db58953834112ff9e33 7676 node-underscore_1.9.1~dfsg-1+deb10u1_all.deb ddb4fe3baea4c7974209793b0627407b85f3f439 6562 underscore_1.9.1~dfsg-1+deb10u1_amd64.buildinfo Checksums-Sha256: d679f4ff436f310d3930c024179ae49def4a367a7d83616aee5dec57b68914e8 2152 underscore_1.9.1~dfsg-1+deb10u1.dsc 26832038e5282c0bde14d5cbe511a42053b5f440e1670f99ba67224a4fd45702 138080 underscore_1.9.1~dfsg.orig.tar.xz 7b16380d4b23af32743a9870279eb43d90ef26837b581bd97f3038a16ffdc410 9076 underscore_1.9.1~dfsg-1+deb10u1.debian.tar.xz 8e7868ddef6d344c915914551a1b0a4edf7b47371eddb1f4ce01ed308e27d864 99968 libjs-underscore_1.9.1~dfsg-1+deb10u1_all.deb eb05cf4f104cb4df35e14816dfab0818978653562e54e4d1c33dbef22c97dd65 7676 node-underscore_1.9.1~dfsg-1+deb10u1_all.deb 2ed6d8e7e193984633b3460eed2427485568fdd0cd21c85f0a8a20882f48aee4 6562 underscore_1.9.1~dfsg-1+deb10u1_amd64.buildinfo Files: 45721395b5abb8a2bd66ecaa733a43e7 2152 web optional underscore_1.9.1~dfsg-1+deb10u1.dsc b16d89fde3b10643b57c331653f8d2b3 138080 web optional underscore_1.9.1~dfsg.orig.tar.xz 17ac85447191a9d1c562740834853edd 9076 web optional underscore_1.9.1~dfsg-1+deb10u1.debian.tar.xz 36c739b0f88393890ece3419dc0e2a7d 99968 web optional libjs-underscore_1.9.1~dfsg-1+deb10u1_all.deb 57b6d7856ae1ba87646fea8068b22c65 7676 web optional node-underscore_1.9.1~dfsg-1+deb10u1_all.deb d2f18887b5d4a6ec6a73a8099b97b5ae 6562 web o
Bug#985962: marked as done (spamassassin: CVE-2020-1946: arbitrary code execution via malicious rule configuration files)
Your message dated Mon, 05 Apr 2021 13:32:30 + with message-id and subject line Bug#985962: fixed in spamassassin 3.4.2-1+deb10u3 has caused the Debian Bug report #985962, regarding spamassassin: CVE-2020-1946: arbitrary code execution via malicious rule configuration files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spamassassin Version: 3.4.2-1+deb10u2 Severity: grave Tags: security patch upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team CVE-2020-1946 Quoting from https://www.openwall.com/lists/oss-security/2021/03/24/3 : In Apache SpamAssassin before 3.4.5, malicious rule configuration (.cf) files can be configured to run system commands without any output or errors. With this, exploits can be injected in a number of scenarios. In addition to upgrading to SA version 3.4.5, users should only use update channels or 3rd party .cf files from trusted places. The fix was silently added to the 3.4 branch prior to 3.4.5~pre1 being packaged for Debian, so it is already present in unstable and bullseye. Buster remains exposed. noah --- End Message --- --- Begin Message --- Source: spamassassin Source-Version: 3.4.2-1+deb10u3 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of spamassassin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated spamassassin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Mar 2021 15:04:43 -0700 Source: spamassassin Architecture: source Version: 3.4.2-1+deb10u3 Distribution: buster-security Urgency: high Maintainer: Noah Meyerhans Changed-By: Noah Meyerhans Closes: 985962 Changes: spamassassin (3.4.2-1+deb10u3) buster-security; urgency=high . * Import upstream fix for CVE-2020-1946: arbitrary code execution via malicious rule files. (Closes: #985962) Checksums-Sha1: 3cae443ea77627ded2fe2fa2be8cd2383092aa6e 2469 spamassassin_3.4.2-1+deb10u3.dsc add571a6b29bbd87b0ecb70e76be3c3bcae3fb67 65548 spamassassin_3.4.2-1+deb10u3.debian.tar.xz a3e7eeb637a33fc7b62dcc63ffd3d58a2f471392 5521 spamassassin_3.4.2-1+deb10u3_source.buildinfo Checksums-Sha256: 8bcb63eceefb8aeb398668ac675b297a0033ff142af542a42a1e2b3ed309f606 2469 spamassassin_3.4.2-1+deb10u3.dsc 9337aa963f531fffd297ebc2488f18ba705279ef39a3a79de8ab88e9d66161f4 65548 spamassassin_3.4.2-1+deb10u3.debian.tar.xz 1ae506c93329fa216f89a1b8c542cafbf31df2be544f6c7c190cbb1df8d93ba1 5521 spamassassin_3.4.2-1+deb10u3_source.buildinfo Files: 63c2eb11bf17b3dcbc5b3e578588918b 2469 mail optional spamassassin_3.4.2-1+deb10u3.dsc 398fe0a1e688bfacc2c5052c4fca00b4 65548 mail optional spamassassin_3.4.2-1+deb10u3.debian.tar.xz 6dc1a8a705e13ff33c275b99463771d4 5521 mail optional spamassassin_3.4.2-1+deb10u3_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE65xaF5r2LDCTz+zyV68+Bn2yWDMFAmBehAkRHG5vYWhtQGRl Ymlhbi5vcmcACgkQV68+Bn2yWDOUAA/+K3gBVjQkXXPAeVI3IHFcRSvc2w84oFxY ouQc9uz4Xo6sWPf695t2i5PISChYSZItylku69viGriRt8oRuN9aYXHJjGIIbbKj Z17jxgZsyXWVluIuYRIHPQNcKJ8UKiQHhe1sTVOMoXr7kgQcgbWYfZ58/eSRXlrt f3HVWVOy2KEj6qxwEcLs25z7ot6DyJkw1KHAA0cZ2QVeMYh/u7dzFEpkrBr9I2Zl elp4lIV8vLO70mx1rWl4MVbyxtsNlJQowIKTrG2PEv7PrWAyF1HsUYq71J1av4kd AsW32LIrIqjV0lHT5vxtkoIQt486BL2puuah/28RceC62XD1LoBuam6olvJPx8a2 F+3bq3xBxHxlGx7kyw66syjKqnUYbpB6iMgBjVG+AbP9rSmULzJ5IS4/n8AnmFhu 3rs1b5ZFtTo+4pcqRaujat1LaTiovOTbm2aGDKj7yjZWl8BEmJk4nnK/RfLuTMt7 WAhmGYG6GJNjZCK4bSe1p2TU6KCCj9aHUqGJ+9LYP3M9dg0cpqwzDiWlhko2Nr4J NxuPBXkuAkoXbtkH5CHfzLUz6b6AwDcaSkti3wxQIm2gDlw7plOTD4Daboa2VvvF wyQMu2le6jIICtD5dcBRMv7x6wlz5cJfa4nOi5OudhU0BekCeo3nxuKW+vVID/5k vg/rMPl5Uwo= =F5Ru -END PGP SIGNATURE End Message ---
Bug#985936: marked as done (ldb: CVE-2020-27840)
Your message dated Mon, 05 Apr 2021 13:32:14 + with message-id and subject line Bug#985936: fixed in ldb 2:1.5.1+really1.4.6-3+deb10u1 has caused the Debian Bug report #985936, regarding ldb: CVE-2020-27840 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldb Version: 2:2.2.0-3 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugzilla.samba.org/show_bug.cgi?id=14595 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ldb. CVE-2020-27840[0]: | Heap corruption via crafted DN strings If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-27840 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27840 [1] https://bugzilla.samba.org/show_bug.cgi?id=14595 [2] https://www.samba.org/samba/security/CVE-2020-27840.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ldb Source-Version: 2:1.5.1+really1.4.6-3+deb10u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of ldb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ldb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Mar 2021 10:35:25 +0200 Source: ldb Architecture: source Version: 2:1.5.1+really1.4.6-3+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Samba Maintainers Changed-By: Salvatore Bonaccorso Closes: 985935 985936 Changes: ldb (2:1.5.1+really1.4.6-3+deb10u1) buster-security; urgency=high . * Non-maintainer upload by the Security Team. * lib ldb: Check if ldb_lock_backend_callback called twice (CVE-2020-10730) * ldb_dn: avoid head corruption in ldb_dn_explode (CVE-2020-27840) (Closes: #985936) * ldb/attrib_handlers casefold: stay in bounds (CVE-2021-20277) (Closes: #985935) Checksums-Sha1: d4be8ebbe6058a671962ea9d7541db0f37c00fe0 2735 ldb_1.5.1+really1.4.6-3+deb10u1.dsc 7563ec51c1621c8b72a579c5550ef2cce8edd8ab 1431798 ldb_1.5.1+really1.4.6.orig.tar.gz 33374bb929ad70faa0bf8a060de29c29ba4c4263 21232 ldb_1.5.1+really1.4.6-3+deb10u1.debian.tar.xz Checksums-Sha256: b4571fafe2adce13583526ab34cfae7f5188e2ab5a39db53d5d72e75663703f9 2735 ldb_1.5.1+really1.4.6-3+deb10u1.dsc a7d008244d95ae8afbff9a843cd3282e92f71d3748e0fd93e3d1b81bd5985983 1431798 ldb_1.5.1+really1.4.6.orig.tar.gz 23ebc07f65f0f8371f5962adb13477616fc16e454a1e9242a545b5e5127e3e16 21232 ldb_1.5.1+really1.4.6-3+deb10u1.debian.tar.xz Files: 4b2cb3a48bb5fbc15fc93690e7216203 2735 devel optional ldb_1.5.1+really1.4.6-3+deb10u1.dsc 3951773a4fed1b3ae27af24972c2ac50 1431798 devel optional ldb_1.5.1+really1.4.6.orig.tar.gz e1fb8be8ebd5268da447e7a65845d28c 21232 devel optional ldb_1.5.1+really1.4.6-3+deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmBgUrBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89ELR8P/0TU5wWptYuOheMEVnJ94eNx+d8Klydu d4ijTcifA4fJL0ExGb69dRPpduiAPuJ/Y1RamKqLlxq5iG+7DYHoUD145mUrFD4o zdUSDpo9/fv1hn2GyOCI/Fm5il5JkDUG7s95PVGRTtABqKbXhItFTll9d9Az5Mu+ jbSpjQ70tsgO2CNPSB+pkpRbmtftn8KFT94k/9v0l1eF64QymfWKkS921D2bwpOV BpdfrWNuEBCnNrusvLC4MkT2dhpd6VQreU83fSjXZul6TgcgZTyqnFJGKU6d0SDn z2fBIO+lwCpSrWe47+cwnnkEJAUoOjDZSX0C0ZCRmdLj76E8mJTwxNMwsIjVTaWv HS+EWt1x/boCDASW10tdJuQQ8ebRJ+wX/Aguh8xl3mIdOD2HtuNS1JdUTSnh6M+2 W9c/VVYXcvtTDaqUteUq4T/5t/ZGQk6ElMKPN71Ug1U9o5lAiQHVWA7EZNcbEQyN R9KMjby6AqUK4BGiJc23HY+Oh5DltV5ja2NtgvUFhfR54JJDs6zyjaUkrqFj5570 Pk9Vum4JaJF9MqnQowojsKm4Igxb81oAp2K8m+NANA3g/hKQs7pCdIu+vWDE226d uU4l9F966c/9L5pnR8nBV+cASZ
Bug#985935: marked as done (ldb: CVE-2021-20277)
Your message dated Mon, 05 Apr 2021 13:32:14 + with message-id and subject line Bug#985935: fixed in ldb 2:1.5.1+really1.4.6-3+deb10u1 has caused the Debian Bug report #985935, regarding ldb: CVE-2021-20277 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldb Version: 2:2.2.0-3 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugzilla.samba.org/show_bug.cgi?id=14655 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ldb. CVE-2021-20277[0]: | Out of bounds read in AD DC LDAP server If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-20277 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20277 [1] https://bugzilla.samba.org/show_bug.cgi?id=14655 [2] https://www.samba.org/samba/security/CVE-2021-20277.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ldb Source-Version: 2:1.5.1+really1.4.6-3+deb10u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of ldb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ldb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Mar 2021 10:35:25 +0200 Source: ldb Architecture: source Version: 2:1.5.1+really1.4.6-3+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Samba Maintainers Changed-By: Salvatore Bonaccorso Closes: 985935 985936 Changes: ldb (2:1.5.1+really1.4.6-3+deb10u1) buster-security; urgency=high . * Non-maintainer upload by the Security Team. * lib ldb: Check if ldb_lock_backend_callback called twice (CVE-2020-10730) * ldb_dn: avoid head corruption in ldb_dn_explode (CVE-2020-27840) (Closes: #985936) * ldb/attrib_handlers casefold: stay in bounds (CVE-2021-20277) (Closes: #985935) Checksums-Sha1: d4be8ebbe6058a671962ea9d7541db0f37c00fe0 2735 ldb_1.5.1+really1.4.6-3+deb10u1.dsc 7563ec51c1621c8b72a579c5550ef2cce8edd8ab 1431798 ldb_1.5.1+really1.4.6.orig.tar.gz 33374bb929ad70faa0bf8a060de29c29ba4c4263 21232 ldb_1.5.1+really1.4.6-3+deb10u1.debian.tar.xz Checksums-Sha256: b4571fafe2adce13583526ab34cfae7f5188e2ab5a39db53d5d72e75663703f9 2735 ldb_1.5.1+really1.4.6-3+deb10u1.dsc a7d008244d95ae8afbff9a843cd3282e92f71d3748e0fd93e3d1b81bd5985983 1431798 ldb_1.5.1+really1.4.6.orig.tar.gz 23ebc07f65f0f8371f5962adb13477616fc16e454a1e9242a545b5e5127e3e16 21232 ldb_1.5.1+really1.4.6-3+deb10u1.debian.tar.xz Files: 4b2cb3a48bb5fbc15fc93690e7216203 2735 devel optional ldb_1.5.1+really1.4.6-3+deb10u1.dsc 3951773a4fed1b3ae27af24972c2ac50 1431798 devel optional ldb_1.5.1+really1.4.6.orig.tar.gz e1fb8be8ebd5268da447e7a65845d28c 21232 devel optional ldb_1.5.1+really1.4.6-3+deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmBgUrBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89ELR8P/0TU5wWptYuOheMEVnJ94eNx+d8Klydu d4ijTcifA4fJL0ExGb69dRPpduiAPuJ/Y1RamKqLlxq5iG+7DYHoUD145mUrFD4o zdUSDpo9/fv1hn2GyOCI/Fm5il5JkDUG7s95PVGRTtABqKbXhItFTll9d9Az5Mu+ jbSpjQ70tsgO2CNPSB+pkpRbmtftn8KFT94k/9v0l1eF64QymfWKkS921D2bwpOV BpdfrWNuEBCnNrusvLC4MkT2dhpd6VQreU83fSjXZul6TgcgZTyqnFJGKU6d0SDn z2fBIO+lwCpSrWe47+cwnnkEJAUoOjDZSX0C0ZCRmdLj76E8mJTwxNMwsIjVTaWv HS+EWt1x/boCDASW10tdJuQQ8ebRJ+wX/Aguh8xl3mIdOD2HtuNS1JdUTSnh6M+2 W9c/VVYXcvtTDaqUteUq4T/5t/ZGQk6ElMKPN71Ug1U9o5lAiQHVWA7EZNcbEQyN R9KMjby6AqUK4BGiJc23HY+Oh5DltV5ja2NtgvUFhfR54JJDs6zyjaUkrqFj5570 Pk9Vum4JaJF9MqnQowojsKm4Igxb81oAp2K8m+NANA3g/hKQs7pCdIu+vWDE226d uU4l9F966c/9L5pnR8nBV+cAS
Bug#985358: pitivi: A/V out of sync in rendered videos
On Sat, Mar 20, 2021 at 10:43:05AM +0200, Sebastian Dröge wrote: > On Tue, 2021-03-16 at 13:39 -0300, Antonio Terceiro wrote: > > As a user, I don't even know about all the stuff that could be better; > pitivi worked ok for me as an amateur video editor. It just failed at > the end of the process, rendering the video. So from my PoV, the > version in bullseye is fine once this is fixed. > > Of course the latest and greatest if always better, but that's > incompatible with a stable release. We just have to cut it at some > point. > > While that's true, in this case I'm mostly concerned about all the > bugfixes that happened in the meantime. > > In any case, would you be interested in helping maintaining this > package? I don't have much time for that these days. I already maintain quite a few packages, I'm not sure I will be able to. Thanks for fixing this! signature.asc Description: PGP signature
Bug#986408: mali-midgard-dkms: Fail to install/build
Package: mali-midgard-dkms Version: 16.0+pristine-4 Severity: serious Dear Maintainer, This package fail to install/build with : $ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up mali-midgard-dkms (16.0+pristine-4) ... Building for 5.10.0-5-arm64 Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 356, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 246, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS' /usr/lib/dkms/common.postinst: 236: [: =: unexpected operator Building for architecture arm64 This package appears to be a binaries-only package you will not be able to build against kernel 5.10.0-5-arm64 since the package source was not provided Removing old mali-midgard-16.0 DKMS files... -- Deleting module version: 16.0 completely from the DKMS tree. -- Done. Loading new mali-midgard-16.0 DKMS files... Building for 5.10.0-5-arm64 Building initial module for 5.10.0-5-arm64 Error! Bad return status for module build on kernel: 5.10.0-5-arm64 (aarch64) Consult /var/lib/dkms/mali-midgard/16.0/build/make.log for more information. dpkg: error processing package mali-midgard-dkms (--configure): installed mali-midgard-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: mali-midgard-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) Christian -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-5-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mali-midgard-dkms depends on: ii dkms 2.8.4-3 mali-midgard-dkms recommends no packages. mali-midgard-dkms suggests no packages. -- no debconf information
Bug#986306: marked as done (FTBFS: certificate in testdata has expired)
Your message dated Mon, 05 Apr 2021 11:48:31 + with message-id and subject line Bug#986306: fixed in golang-github-docker-go-connections 0.4.0-3 has caused the Debian Bug report #986306, regarding FTBFS: certificate in testdata has expired to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-docker-go-connections Version: 0.4.0-2 Severity: serious X-Debbugs-Cc: z...@debian.org === RUN TestConfigServerExclusiveRootPools config_test.go:241: Unable to verify certificate 1: x509: certificate has expired or is not yet valid: current time 2021-04-02T18:04:40Z is after 2021-03-17T16:40:46Z --- FAIL: TestConfigServerExclusiveRootPools (0.00s) === RUN TestConfigClientExclusiveRootPools config_test.go:595: Unable to verify certificate 1: x509: certificate has expired or is not yet valid: current time 2021-04-02T18:04:40Z is after 2021-03-17T16:40:46Z --- FAIL: TestConfigClientExclusiveRootPools (0.00s) --- End Message --- --- Begin Message --- Source: golang-github-docker-go-connections Source-Version: 0.4.0-3 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of golang-github-docker-go-connections, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated golang-github-docker-go-connections package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Apr 2021 19:39:50 +0800 Source: golang-github-docker-go-connections Architecture: source Version: 0.4.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 986306 Changes: golang-github-docker-go-connections (0.4.0-3) unstable; urgency=medium . * Team upload. * Update Section to golang * Update maintainer address to team+pkg...@tracker.debian.org * Add Rules-Requires-Root * Drop unused dependency golang-github-opencontainers-runc-dev * Update Standards-Version to 4.5.1 (no changes) * Update uscan watch file to version 4 * Add patch to skip tests which use expiered certificate (Closes: #986306) Checksums-Sha1: 5b8cd9f157ddfc52bb26c25b9631eb1f8570180c 1889 golang-github-docker-go-connections_0.4.0-3.dsc 5ec680864821d333d1d1fa07fcf0ef89e505cf50 3580 golang-github-docker-go-connections_0.4.0-3.debian.tar.xz b75fdbb2ebe33e69cede0ff626a3b5963f1d674d 6176 golang-github-docker-go-connections_0.4.0-3_amd64.buildinfo Checksums-Sha256: 4f6e562e733417ba240f2515cdc36fcb01b61090ea758a2089e5d53fac0aaffa 1889 golang-github-docker-go-connections_0.4.0-3.dsc f62f694e1e3efb88cf37cf48a36a17697ea7ac4f21d96a7a3d69373e2ceb9b26 3580 golang-github-docker-go-connections_0.4.0-3.debian.tar.xz a32a4222b59c1b2a480689fd19fc05eb58b7c4940a6733321e640a6fcbd52072 6176 golang-github-docker-go-connections_0.4.0-3_amd64.buildinfo Files: 9ab2f81219ab04a0f90339400bc3c5da 1889 golang optional golang-github-docker-go-connections_0.4.0-3.dsc 952f0c3a72a9b44f840e068fe7196192 3580 golang optional golang-github-docker-go-connections_0.4.0-3.debian.tar.xz 6a49d37ce6c40fd7468b2a92d502d310 6176 golang optional golang-github-docker-go-connections_0.4.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCYGr4ahAcemhzakBkZWJp YW4ub3JnAAoJEMSFSjgY4LAWuyYA/RQfhaI0tRHoj7P8Tan9fHaItEtGx5tAYUnb qP5aERgsAPoDsDYqwj0WHN4Av+Q9o+xeYwnTi7grb6h8kYP4E7RoCA== =HMRL -END PGP SIGNATURE End Message ---
Bug#986403: marked as done (Compression doesn't work)
Your message dated Mon, 05 Apr 2021 10:36:50 + with message-id and subject line Bug#986403: fixed in libfits-java 1.15.2-2 has caused the Debian Bug report #986403, regarding Compression doesn't work to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfits-java Version: 1.15.2-1 Severity: serious Control: affects -1 skyview The library fails to handle compressed files, due to missing resources in the Jar file. This causes skyview to fail completely (since skyview uses compressed files). The jar needs additionally the "META-INF/resources", which are in "src/main/resources". --- End Message --- --- Begin Message --- Source: libfits-java Source-Version: 1.15.2-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of libfits-java, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated libfits-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Apr 2021 12:10:07 +0200 Source: libfits-java Architecture: source Version: 1.15.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Ole Streicher Closes: 986403 Changes: libfits-java (1.15.2-2) unstable; urgency=medium . * Team upload. * Add resources files to jar (Closes: #986403) Checksums-Sha1: aebf6f562038a3111573c1ddcc126d341ffbe4f4 2219 libfits-java_1.15.2-2.dsc 11026845030de58918eca8a63a331c6caa1ea3e8 4832 libfits-java_1.15.2-2.debian.tar.xz Checksums-Sha256: 87328701ced889484ebceac539bb21c871a8d0190e9b485724652c8b5e3fb234 2219 libfits-java_1.15.2-2.dsc 4bc084196f53502e41c29b956f71394d74068c7ee83e4b22eae75e59e508607b 4832 libfits-java_1.15.2-2.debian.tar.xz Files: 5861636dc8a6dcf999ac9b33ca86b8ae 2219 java optional libfits-java_1.15.2-2.dsc ff3b767f2e4d7be4eeb5d38caee6ab75 4832 java optional libfits-java_1.15.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmBq4ocACgkQcRWv0HcQ 3PdQng/9FZNMMHl1xyzLc6mK/1GIMI2psnuXbBaoGYy4cuwwSU7MGTo7ddPGpApG MLvJ0ZURCKtS9LUFjob/mSjamjeYRE10V7W0VHvcUZIXB6n60oISzFchH8cbavvN uQNO4Qw5h91r/Fe8a4znmhnPaTX9Err650S4+we8D/LI3HvrNPKXBuZmdAaAKNAS XvMOSUfC59BOrTnZ2a0VAZIclu4FTdMxPW093dr11PuCJH/c3ghHu19cET7Hmb8Z QxoxHnWW7Isnm8TPuSF8hJDhi5M0pBIARsItTgTYv4lsc+GMqOeeRwCsPXiwmp8h AzSv30d7uwssSkjN8+A+J+C3mnZaolXjrNSVYN9/0sjnFbJ9yLlhzOU/bOeGAF8e J4Wvq17335P1fN6yg6LeXqBnDqkyylq5L64Rj9YQaWcRAElMKG1mo4+Z/On27c85 VmQMW7Ngy2m6Z4gubZzD261CdTVyLMxzrqnavQteA0LCPUWlio51Dd1hdm0Eu7LK ckHCv8dnALEIIRQFofwUuWk5kvBI2x1BVKtxqHIXB25pMyShi+jnlIpg5Ccbk4yx i/B6ZyY91iyi8kpd2yV5FaPN6/uvfHuAXEmXiJx/4YL5HMiq8KzVp9LF4PfLHiBU xvWVOUOmk6E0HX1aabIXj29VuaOv8CVrbvv9sYdp1U3W2VYryR8= =rj1g -END PGP SIGNATURE End Message ---
Bug#986392: marked as done (skyview fails to start)
Your message dated Mon, 05 Apr 2021 10:22:37 + with message-id and subject line Bug#986392: fixed in skyview 3.5.5+repack-2 has caused the Debian Bug report #986392, regarding skyview fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: skyview Version: 3.5.5+repack-1 Severity: normal Dear Maintainer, Skyviews fails to start with the following errors: skyview Unable to find settings. Continuing with defaults. SkyView version is -1.0 Error reading usage file:java.lang.NullPointerException Unable to instantiate dynamic class null in package skyview.survey: null java.lang.NullPointerException at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:315) at skyview.util.Utilities.newInstance(Utilities.java:474) at skyview.executive.Imager.usage(Imager.java:405) at skyview.executive.Imager.main(Imager.java:268) Error creating SurveyFinder: null BR -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages skyview depends on: ii default-jre-headless 2:1.11-72 ii jarwrapper0.78 ii skyview-java 3.5.5+repack-1 skyview recommends no packages. skyview suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: skyview Source-Version: 3.5.5+repack-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of skyview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated skyview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Apr 2021 12:00:20 +0200 Source: skyview Architecture: source Version: 3.5.5+repack-2 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 986392 Changes: skyview (3.5.5+repack-2) unstable; urgency=medium . * Include default settings file and intro in skyview jar (Closes: #986392) Checksums-Sha1: 0eb20a7c05024b93fea081fafbde7c74e24b1099 2209 skyview_3.5.5+repack-2.dsc d00690cca07724db324455c09d178393ef239ea2 7152 skyview_3.5.5+repack-2.debian.tar.xz Checksums-Sha256: a44bea8d4402c22cb36adf16346401ed660b3de7eb1985a053851e14c539a7f6 2209 skyview_3.5.5+repack-2.dsc b47604946bfc47770fc44dfd7d4ac789ad9b81b78ff023193e6c8ca0eb360e8b 7152 skyview_3.5.5+repack-2.debian.tar.xz Files: ebf652db1f52ea227e09f337a42ac509 2209 java optional skyview_3.5.5+repack-2.dsc 1dcf1f9fa91c0fd19739ee5fd84e6a66 7152 java optional skyview_3.5.5+repack-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmBq4QUACgkQcRWv0HcQ 3PcvfQ/8C0yfEngIyfkGXGOhq+o80yyw18mTiAnar4zxYvUljSVN4AzGI3eiThoG qmQrhqn/Y5aixRHijIVp9pPtMqCY2AQjDvmT0OTfHjUVoFX8VoBeb3WZzT2HTKrX I1x1lxaYkuZuZPrwt2DXGqiMriZtqcnya2PxvlArf+l1KnaCopgFIhsY/fR5yuUg 1MrQsN9GhrJNd8Tn+cSuADwHiQOA1EFbUbajiLlWws/V38jyOmD5HABlLjOuAEMS tjz6vepXjJ1ksObzeRaFquDrSpxfPnEdsLTlIOl0kgFL99f2onwc9Batqjdxi6v5 PmHzRDQFHyxO2jt8A1gJwuctx0VB0p+KL8a/XBgIm4AE7+galbDaN+7TrkKBBMvt 4yMFp+94j35LkGWieWcS0gDL1Y8ggm+0zHLGWnc2eYMH0SKt9NM7arFSZKEy1uum CoaVLMeFRBA8DDQGE4v+mTsJSWK2TOeS6rW0RfixWcEP4HAhVo312SsLXfBFUYgF tPWbBEXLHnMbbaMOLGrP2AsnDkNmM7AMSY5vpbgQw2f2Vz9ulsRDWNsCgnCKAECj JoGSIY0F1qEkttIVqFmwf/afXkHuH5dMjucCPyUKQ7/+6m+GSTbRHOVLKJBt2wBY Jhk0Dw6D7n44xe6R/YduAXUjLXM3EQQIm2W9C+fvoVSZKrOd7DE= =p6O2 -END PGP SIGNATURE End Message ---
Bug#986403: Compression doesn't work
Package: libfits-java Version: 1.15.2-1 Severity: serious Control: affects -1 skyview The library fails to handle compressed files, due to missing resources in the Jar file. This causes skyview to fail completely (since skyview uses compressed files). The jar needs additionally the "META-INF/resources", which are in "src/main/resources".
Processed: Compression doesn't work
Processing control commands: > affects -1 skyview Bug #986403 [libfits-java] Compression doesn't work Added indication that 986403 affects skyview -- 986403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Raising severity for skyview bug
Processing commands for cont...@bugs.debian.org: > severity 986392 serious Bug #986392 [skyview] skyview fails to start Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 986392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984579: marked as done (libgstreamer1.0-dev: leaves diversions after upgrade from buster)
Your message dated Mon, 05 Apr 2021 09:49:24 + with message-id and subject line Bug#984579: fixed in gstreamer1.0 1.18.3-2 has caused the Debian Bug report #984579, regarding libgstreamer1.0-dev: leaves diversions after upgrade from buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgstreamer1.0-dev Version: 1.18.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove some diversions after upgrading from buster to bullseye and removing the package afterwards. >From the attached log (scroll to the bottom...): 0m47.6s ERROR: FAIL: Installed diversions (dpkg-divert) not removed by purge: diversion of /usr/share/man/man1/dh_gstscancodecs.1.gz to /usr/share/man/man1/dh_gstscancodecs.1.gz-gst0.10 by libgstreamer1.0-dev diversion of /usr/bin/dh_gstscancodecs to /usr/bin/dh_gstscancodecs-gst0.10 by libgstreamer1.0-dev The version in bullseye no longer uses diversions, therefore it should clean up the old diversions in its postinst: if [ "$1" = "configure" ] && dpkg --compare-versions "$2" lt-nl "1.18.3-2~" ; then dpkg-divert --package libgstreamer1.0-dev --rename --remove /usr/bin/dh_gstscancodecs dpkg-divert --package libgstreamer1.0-dev --rename --remove /usr/share/man/man1/dh_gstscancodecs.1.gz fi cheers, Andreas libgstreamer1.0-dev_1.18.3-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gstreamer1.0 Source-Version: 1.18.3-2 Done: Sebastian Dröge We believe that the bug you reported is fixed in the latest version of gstreamer1.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge (supplier of updated gstreamer1.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Apr 2021 11:39:20 +0300 Source: gstreamer1.0 Architecture: source Version: 1.18.3-2 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages Changed-By: Sebastian Dröge Closes: 981203 984579 Changes: gstreamer1.0 (1.18.3-2) unstable; urgency=medium . [ Helmut Grohne ] * Annotate Build-Depends libgmp-dev and libgsl-dev (Closes: #981203). . [ Andreas Beckmann ] * Remove obsolete diversions on upgrades from buster (Closes: #984579). . [ Sebastian Dröge ] * Upload to unstable. Checksums-Sha1: 6a262e7a85126082f8a927e3d53b01272e734349 3008 gstreamer1.0_1.18.3-2.dsc 9daaf26def895882af1510e5e530f76bc19fda98 2701612 gstreamer1.0_1.18.3.orig.tar.xz 3f1e4ba9a10831bc307d9081b02fce29c97780f4 44080 gstreamer1.0_1.18.3-2.debian.tar.xz 5654663efd996182b5a7a3759b654eca55f1 9925 gstreamer1.0_1.18.3-2_amd64.buildinfo Checksums-Sha256: c4003aa844f80db62b072ba2b57007d72fb9515340395837da65a0c99ce9da8a 3008 gstreamer1.0_1.18.3-2.dsc 0c2e09e18f2df69a99b5cb3bd53c597b3cc2e35cf6c98043bb86a66f3d312100 2701612 gstreamer1.0_1.18.3.orig.tar.xz ffa4d57886aee32c6f33ff5711d0a150ccbd756ab631e1df8f7ba6df8a7b 44080 gstreamer1.0_1.18.3-2.debian.tar.xz ace8307f560d7e1ac5ffc1b08f88930d148239c42586cd87732d7baa95d60e24 9925 gstreamer1.0_1.18.3-2_amd64.buildinfo Files: c94ea5828df5544589ee16b471b67dfd 3008 libs optional gstreamer1.0_1.18.3-2.dsc eb126bc230ba7cc7db9e1d1fc0b4f40d 2701612 libs optional gstreamer1.0_1.18.3.orig.tar.xz a0a9cb6d61e6a650bdbf1e1755130a90 44080 libs optional gstreamer1.0_1.18.3-2.debian.tar.xz cb6f4fa9fec0222df1859aed8931f9a9 9925 libs optional gstreamer1.0_1.18.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEEf0vHzDygb5cza7/rBmjMFIbC17UFAmBq2GJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDdG NEJDN0NDM0NBMDZGOTczMzZCQkZFQjA2NjhDQzE0ODZDMkQ3QjUSHHNsb21vQGNv YXhpb24ubmV0AAoJEAZozBSGwte11zAP/0hvVGzwQlvlxnjqQi2VVzg8HgX/e8se NKaBuk9P7tcJ9ukKum19JP8rCrKlKhh8aaA45fIj0OuqVT3zZJzsYttxowkjA6sU OD3gqGoyBugfkGDl1Vde77d7EkkZsdKIG/FteXw725JtmgaMx90NhHtlsN2Ex5U5 OMlAlr5ZlEw
Bug#985358: marked as done (pitivi: A/V out of sync in rendered videos)
Your message dated Mon, 05 Apr 2021 08:15:05 + with message-id and subject line Bug#985358: fixed in pitivi 2020.09.2-3 has caused the Debian Bug report #985358, regarding pitivi: A/V out of sync in rendered videos to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pitivi Version: 2020.09.2-2 Severity: grave Tags: upstream patch Justification: renders package unusable Forwarded: https://gitlab.gnome.org/GNOME/pitivi/-/issues/2498 Dear Maintainer, The version of pitivi in bullseye is affected by the bug listed above: rendered videos have A/V out of sync by a few seconds, while they sound just find in the preview. I'm attaching the upstream patch that fixed the issue, already backported to the current Debian package. I rebuilt pitivi locally with this patch, and confirmed that it does fix the issue. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pitivi depends on: ii gir1.2-gdkpixbuf-2.02.42.2+dfsg-1 ii gir1.2-ges-1.0 1.18.3-1 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gst-plugins-bad-1.0 1.18.3-1+b1 ii gir1.2-gst-plugins-base-1.0 1.18.3-1 ii gir1.2-gstreamer-1.01.18.3-1 ii gir1.2-gtk-3.0 3.24.24-3 ii gir1.2-pango-1.01.46.2-3 ii gir1.2-peas-1.0 1.28.0-2+b1 pn gstreamer1.0-audiosink ii gstreamer1.0-gl [gstreamer1.0-videosink]1.18.3-1 ii gstreamer1.0-gtk3 [gstreamer1.0-videosink] 1.18.3-1 ii gstreamer1.0-plugins-bad [gstreamer1.0-videosink] 1.18.3-1+b1 ii gstreamer1.0-plugins-base 1.18.3-1 ii gstreamer1.0-plugins-good [gstreamer1.0-videosink] 1.18.3-1 ii gstreamer1.0-x [gstreamer1.0-videosink] 1.18.3-1 ii libc6 2.31-9 ii libcairo2 1.16.0-5 ii libglib2.0-02.66.7-2 ii libgstreamer1.0-0 1.18.3-1 ii libpython3.93.9.2-1 ii python3 3.9.2-2 ii python3-cairo 1.16.2-4+b2 ii python3-dbus1.2.16-5 ii python3-ges-1.0 1.18.3-1 ii python3-gi 3.38.0-2 ii python3-gi-cairo3.38.0-2 ii python3-gst-1.0 1.18.3-1 ii python3-matplotlib 3.3.4-1 ii python3-numpy 1:1.19.5-1 ii python3-xdg 0.27-2 ii python3.9 3.9.2-1 pitivi recommends no packages. Versions of packages pitivi suggests: pn frei0r-plugins ii gir1.2-gnomedesktop-3.03.38.4-1 pn gir1.2-gsound-1.0 ii gir1.2-notify-0.7 0.7.9-3 ii gstreamer1.0-libav 1.18.3-1 ii gstreamer1.0-plugins-ugly 1.18.3-1 -- no debconf information From: Thibault Saunier Date: Mon, 11 Jan 2021 17:50:26 -0300 Subject: pipeline: Avoid committing the timeline while rendering This can cause weird behavior and in particular it can lead to de-synchronized audio/video streams. Fixes https://gitlab.gnome.org/GNOME/pitivi/-/issues/2498 --- pitivi/editorperspective.py | 3 +++ pitivi/utils/pipeline.py| 8 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/pitivi/editorperspective.py b/pitivi/editorperspective.py index a25450c..49cbf61 100644 --- a/pitivi/editorperspective.py +++ b/pitivi/editorperspective.py @@ -128,6 +128,9 @@ class EditorPerspective(Perspective, Loggable):
Processed: Re: openjdk-11-jre-dcevm is marked for autoremoval from testing
Processing commands for cont...@bugs.debian.org: > severity 984725 important Bug #984725 [openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: incompatible with newest openjdk-11-jre 11.0.11+4-1 Severity set to 'important' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 984725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
