Bug#931761: python3-jsonschema: Wrong import order
Package: python3-jsonschema Version: 2.6.0-4 Severity: important jsonschema.compat has try: from collections import MutableMapping, Sequence # noqa except ImportError: from collections.abc import MutableMapping, Sequence # noqa instead of try: from collections.abc import MutableMapping, Sequence # noqa except ImportError: from collections import MutableMapping, Sequence # noqa This unnecessarily triggers a DeprecationWarning, which prevents code using this package from testing cleanly. The current version (3.0.1) fixes this. Please back-port for Buster. -- System Information: Debian Release: 9.9 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-jsonschema depends on: ii python33.7.3-1 ii python3-pkg-resources 40.8.0-1 python3-jsonschema recommends no packages. Versions of packages python3-jsonschema suggests: pn python-jsonschema-doc -- no debconf information
Bug#931759: ITP: r-cran-insight -- GNU R easy access to model information for various model objects
Package: wnpp Severity: wishlist Subject: ITP: r-cran-insight -- GNU R easy access to model information for various model objects Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: r-cran-insight Version : 0.4.0 Upstream Author : Daniel Lüdecke, * URL : https://cran.r-project.org/package=insight * License : GPL-3 Programming Lang: GNU R Description : GNU R easy access to model information for various model objects A tool to provide an easy, intuitive and consistent access to information contained in various R models, like model formulas, model terms, information about random effects, data that was used to fit the model or data from response variables. 'insight' mainly revolves around two types of functions: Functions that find (the names of) information, starting with 'find_', and functions that get the underlying data, starting with 'get_'. The package has a consistent syntax and works with many different model objects, where otherwise functions to access these information are missing. Remark: This package is maintained by Debian R Packages Maintainers at https://salsa.debian.org/r-pkg-team/r-cran-insight
Bug#931760: doesn't pull perl-openssl-defaults in debootstrap
Package: libnet-ssleay-perl Version: 1.85-2+b1 Severity: minor Dear Maintainer, when I use debootstrap with a package that depends on libnet-ssleay-perl, the debootstap fails: 1 [22/5006]mh@salida:~ $ sudo debootstrap --arch=amd64 --variant=minbase --include=libnet-ssleay-perl sid blubb http://debian.debian.zugschlus.de/debian I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 0146DC6D4A0B2914BDED34DB648ACFD622F3D138) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://debian.debian.zugschlus.de/debian... I: Retrieving libacl1 2.2.53-4 I: Validating libacl1 2.2.53-4 I: Retrieving adduser 3.118 I: Validating adduser 3.118 I: Retrieving apt 1.8.2 I: Validating apt 1.8.2 I: Configuring libgdbm-compat4:amd64... I: Configuring libperl5.28:amd64... I: Configuring perl... I: Configuring libc-bin... W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /home/mh/blubb/debootstrap/debootstrap.log for details (possibly the package libnet-ssleay-perl is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /home/mh/blubb/debootstrap/debootstrap.log for details (possibly the package libnet-ssleay-perl is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /home/mh/blubb/debootstrap/debootstrap.log for details (possibly the package libnet-ssleay-perl is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /home/mh/blubb/debootstrap/debootstrap.log for details (possibly the package libnet-ssleay-perl is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /home/mh/blubb/debootstrap/debootstrap.log for details (possibly the package libnet-ssleay-perl is at fault) 1 [23/5007]mh@salida:~ $ relevant parts of the log: Preparing to unpack .../libgdbm-compat4_1.18.1-4_amd64.deb ... Unpacking libgdbm-compat4:amd64 (1.18.1-4) ... Preparing to unpack .../libgdbm6_1.18.1-4_amd64.deb ... Unpacking libgdbm6:amd64 (1.18.1-4) ... Preparing to unpack .../libnet-ssleay-perl_1.85-3_amd64.deb ... Unpacking libnet-ssleay-perl (1.85-3) ... Preparing to unpack .../libssl1.1_1.1.1c-1_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1c-1) ... Preparing to unpack .../libperl5.28_5.28.1-6_amd64.deb ... Unpacking libperl5.28:amd64 (5.28.1-6) ... Preparing to unpack .../perl_5.28.1-6_amd64.deb ... Unpacking perl (5.28.1-6) ... Preparing to unpack .../perl-modules-5.28_5.28.1-6_all.deb ... Unpacking perl-modules-5.28 (5.28.1-6) ... Processing triggers for libc-bin (2.28-10) ... dpkg: dependency problems prevent configuration of libnet-ssleay-perl: libnet-ssleay-perl depends on perl-openssl-abi-1.1; however: Package perl-openssl-abi-1.1 is not installed. dpkg: error processing package libnet-ssleay-perl (--configure): dependency problems - leaving unconfigured Setting up perl-modules-5.28 (5.28.1-6) ... Setting up libssl1.1:amd64 (1.1.1c-1) ... Setting up libgdbm6:amd64 (1.18.1-4) ... Setting up libgdbm-compat4:amd64 (1.18.1-4) ... Setting up libperl5.28:amd64 (5.28.1-6) ... Setting up perl (5.28.1-6) ... perl-openssl-abi-1.1 is provided by perl-openssl-defaults, which your package depends on. Both debootstrapping without libnet-ssleay-perl and explicitly also including perl-openssl-defaults work just fine. This might be a bug in debootstrap, not properly handling the virtual provides of perl-openssl-defaults. Please reassign if your analysis has the same result. Greetings Marc -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.15-zgws1 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libnet-ssleay-perl depends on: ii libc6 2.28-10 ii libssl1.1 1.1.1c-1 ii perl 5.28.1-6 ii perl-openssl-defaults [perl-openssl-abi-1.1] 3 pn perlapi-5.28.0 libnet-ssleay-perl recommends no packages. libnet-ssleay-perl suggests no packages. -- no debconf information
Bug#931758: mirror submission for repo.jztkft.hu
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: repo.jztkft.hu Type: leaf Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Gabor Birincsik Country: HU Hungary Location: Budapest Comment: repo.jztkft.hu/debian Trace Url: http://repo.jztkft.hu/debian/project/trace/ Trace Url: http://repo.jztkft.hu/debian/project/trace/ftp-master.debian.org Trace Url: http://repo.jztkft.hu/debian/project/trace/repo.jztkft.hu
Bug#931757: FTBFS: firefox 68.0-1 on buster/i386
Package: firefox Version: 68.0-1 Severity: normal Hi, I'm building firefox 68.0-1 on buster/i386 with nss and nspr backported from sid. While it builds fine on amd64, it fails on i386: ---snip--- [...] Compiling gkrust v0.1.0 (/build/firefox-68.0-1/toolkit/library/rust) Running `CARGO_PKG_REPOSITORY= CARGO_PRIMARY_PACKAGE=1 CARGO_PKG_VERSION=0.1.0 CARGO_PKG_AUTHORS='nob...@mozilla.org' CARGO_MANIFEST_DIR=/build/firefox-68.0-1/toolkit/library/rust CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_DESCRIPTION='Rust code for libxul' CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_HOMEPAGE= LD_LIBRARY_PATH='/build/firefox-68.0-1/build-browser/release/deps:/usr/lib' CARGO_PKG_VERSION_PRE= CARGO=/usr/bin/cargo CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_NAME=gkrust /usr/bin/rustc --crate-name gkrust toolkit/library/rust/lib.rs --color always --crate-type staticlib --emit=dep-info,link -C opt-level=2 -C panic=abort -C codegen-units=1 -C lto --cfg 'feature="bindgen"' --cfg 'feature="cubeb-remoting"' --cfg 'feature="cubeb_pulse_rust"' --cfg 'feature="gecko_profiler"' --cfg 'feature="gkrust-shared"' --cfg 'feature="moz_memory"' --cfg 'feature="moz_places"' --cfg 'feature="quantum_render"' --cfg 'feature="servo"' -C metadata=6f96f008c952a2a0 -C extra-filename=-6f96f008c952a2a0 --out-dir /build/firefox-68.0-1/build-browser/i686-unknown-linux-gnu/release/deps --target i686-unknown-linux-gnu -C linker=/build/firefox-68.0-1/build/cargo-linker -L dependency=/build/firefox-68.0-1/build-browser/i686-unknown-linux-gnu/release/deps -L dependency=/build/firefox-68.0-1/build-browser/release/deps --extern gkrust_shared=/build/firefox-68.0-1/build-browser/i686-unknown-linux-gnu/release/deps/libgkrust_shared-5c52925ca959de1c.rlib --extern mozilla_central_workspace_hack=/build/firefox-68.0-1/build-browser/i686-unknown-linux-gnu/release/deps/libmozilla_central_workspace_hack-50a3f0598d8b252a.rlib -C opt-level=2 --cap-lints warn -L native=/build/firefox-68.0-1/build-browser/i686-unknown-linux-gnu/release/build/lmdb-rkv-sys-057ba1a0785cc5e3/out` Finished release [optimized] target(s) in 12m 54s /build/firefox-68.0-1/build-browser/_virtualenvs/init/bin/python -m mozbuild.action.check_binary --target --networking /build/firefox-68.0-1/build-browser/i686-unknown-linux-gnu/release/libgkrust.a make[5]: Leaving directory '/build/firefox-68.0-1/build-browser/toolkit/library/rust' make[4]: Leaving directory '/build/firefox-68.0-1/build-browser' make[3]: *** [/build/firefox-68.0-1/config/recurse.mk:34: compile] Error 2 make[3]: Leaving directory '/build/firefox-68.0-1/build-browser' make[2]: *** [/build/firefox-68.0-1/config/rules.mk:413: default] Error 2 make[2]: Leaving directory '/build/firefox-68.0-1/build-browser' dh_auto_build: cd build-browser && make -j88 LD_LIBS=-Wl,--no-gc-sections _LEAKTEST_FILES=leaktest.py returned exit code 2 make[1]: *** [debian/rules:241: stamps/build-browser] Error 2 make[1]: Leaving directory '/build/firefox-68.0-1' make: *** [debian/rules:342: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 build@debian:~$ ---snap--- Regards, Daniel
Bug#931756: bindgraph stop action fails
Package: bindgraph Version: 0.2a-6 Severity: serious Tags: patch Hello, the sysv init script for bindgraph fails on the stop action with the message start-stop-daemon: matching only on non-root pidfile /var/run/servergraph/bindgraph.pid is insecure Relevant other bugs are 923421, 921016, and 921557. What works for me is adding -u daemon to the start-stop-daemon call on line 63. Bye, Joerg signature.asc Description: PGP signature
Bug#931753: DefaultDependencies=no ignores PrivateTmp=yes, but honors its implied RequiresMountsFor=
Trent W. Buck wrote: > But I also noticed that "systemd-analyze security" says that PrivateTmp=yes > will be ignored: > > # SYSTEMD_PAGER='grep apply' systemd-analyze security procps.service > PrivateTmp= Service > runs in special boot phase, option does not apply > ProtectHome=Service > runs in special boot phase, option does not apply > ProtectSystem= Service > runs in special boot phase, option does not apply > RootDirectory=/RootImage= Service > runs in special boot phase, option does not apply > RemoveIPC= Service > runs as root, option does not apply > > If systemd ignores PrivateTmp=yes when DefaultDependencies=no, then > systemd SHOULD ignore the implied RequiresMountsFor= (and knock-on > Requires=var-tmp.mount) when DefaultDependencies=no. My earlier analysis is clearly incorrect, because systemd-resolved.service systemd-timesyncd.service both use both DefaultDependencies=no and PrivateTmp=yes, and as a result cannot start until after var-tmp.mount is done (even if /var/tmp is stored on a remote NFS server whose name must be DNS-resolved --- oops!) "systemd-analyze security systemd-resolved" claims for that PrivateTmp= "does not apply", though it clearly does.
Bug#931755: ITP: python-b2-sdk -- Python library to access B2 cloud storage.
Package: wnpp Severity: wishlist Owner: Ondrej Koblizek * Package name: python-b2-sdk Version : 1.0.0 Upstream Author : Backblaze, Inc. * URL : https://github.com/Backblaze/b2-sdk-python * License : MIT Programming Lang: Python Description : Python library to access B2 cloud storage. This repository contains a client library and a few handy utilities for easy access to all of the capabilities of B2 Cloud Storage. This package is a new dependency of the next version of package backblaze-b2. I plan maintain it in DPMT.
Bug#878487: checkinstall bug
Thanks for reporting this and providing a patch! I just uploaded checkinstall 1.6.2-5 which includes your patch. Unfortunately this didn’t make it into buster but once this fixed version migrates to testing I will upload it to buster-backports. Thanks! Stephen
Bug#931750: telegram-desktop: Packace uninstallable due to alleged lack of dependency
It happens because you've installed some packages from the experimental repository where Telegram Desktop was built against Qt 5.11.3. Now you have to downgrade version of libqt5core5a. Install it from stable repo, for example. Also I would recommend you to decrease priority of the experimental repository.
Bug#931670: apt uses yellow for warnings
Control: merge 844298 -1 Am 09.07.2019 um 15:58 schrieb David Kalnischkies: > Control: reassign dpkg 1.19.7 > > On Tue, Jul 09, 2019 at 01:52:05AM -0400, Lady Aleena wrote: >> While I was running apt autoremove, I saw a warning. I did not know it was a >> warning at first because I could not read the bright yellow text. I use a >> terminal emulator with a white background. Bright yellow is the only color >> that causes problems on a white background. > > The warning is produced by dpkg – apt just tells dpkg to color its output > by default – so I am reassigning to dpkg for them to deal with it. This has been noticed before in #844298, BTW. > Still, thanks for the report & I hope something can be done about this. > I intend to follow as apt might color more of its output someday and > would eventually run into the same problems then. Cheers, Sven
Bug#931754: qa.debian.org: pass --debian to blhc
package: qa.debian.org severity: normal The blhc results on the build log scanner pages at qa.debian.org indicate that most packages have missing pie flags now that gcc injects it automatically on most archs. Please use the new --debian flag, which was added to account for this [0]. Best wishes, Mike [0] http://bugs.debian.org/845339
Bug#931753: DefaultDependencies=no ignores PrivateTmp=yes, but honors its implied RequiresMountsFor=
Package: systemd Version: 241-5 Severity: minor After discovering "systemd-analyze security", I went around adding systemd-level confinement to units, e.g. remove modprobe privileges from all units that don't modprobe. I noticed that adding PrivateTmp=yes to keyboard-setup.service and systemd-udev-settle.service caused ordering cycles. This is because 1. they want to run BEFORE zfs-mount, but 2. PrivateTmp=yes implies RequiresMountsFor=/tmp /var/tmp, so they ALSO want to run AFTER zfs-mount. So OK, the obvious answer is "don't do that, then" - remove PrivateTmp=yes. But I also noticed that "systemd-analyze security" says that PrivateTmp=yes will be ignored: # SYSTEMD_PAGER='grep apply' systemd-analyze security procps.service PrivateTmp= Service runs in special boot phase, option does not apply ProtectHome=Service runs in special boot phase, option does not apply ProtectSystem= Service runs in special boot phase, option does not apply RootDirectory=/RootImage= Service runs in special boot phase, option does not apply RemoveIPC= Service runs as root, option does not apply If systemd ignores PrivateTmp=yes when DefaultDependencies=no, then systemd SHOULD ignore the implied RequiresMountsFor= (and knock-on Requires=var-tmp.mount) when DefaultDependencies=no. I realize this is probably a huge pain to fix. Probably the implicit options are added at read time, but the "ignore conflicting options" is done much later, at which time it's impossible to know if Requires=var-tmp.mount was added explicitly or implicitly. Possibly an easy mitigation is just to log a warning like: WARNING: procps.service has both DefaultDependencies=no and PrivateTmp=yes; this won't do what you want! There are already similar warnings for similar dumb mistakes: systemd[1]: /etc/systemd/system/charybdis.service:7: Unknown lvalue 'StartExec' in section 'Service', ignoring systemd[1]: charybdis.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing. PS: DynamicUser=yes implies PrivateTmp=yes, so I think it should also be "does not apply" for "special boot phase". PPS: I ran into this on a system with ZFS, but it should be reproducible anywhere that has a dedicated /var/tmp mount in /etc/fstab.
Bug#931752: linux-image-4.19.0-5-amd64: USB-C to HDMI doesn't work. CONFIG_TYPEC_DP_ALTMODE is not set
Package: src:linux Version: 4.19.37-5 Severity: wishlist Tags: newcomer USB-C to HDMI doesn't work with the pre-compiled kernel. I have done a decent amount of research in regards to getting this to work. I think this may be related to the fact that the following is not set. ~ $ cat /boot/config-4.19.0-5-amd64 |grep TYPEC_DP_ALTMODE # CONFIG_TYPEC_DP_ALTMODE is not set With more and more laptops starting to use usb-c it would be nice if the pre- compiled kernel was compiled to use this as a module. Links that may be of some use: https://lore.kernel.org/patchwork/patch/954390/ https://cateee.net/lkddb/web-lkddb/TYPEC_DP_ALTMODE.html Thanks! -slick -- Package-specific info: ** Version: Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-5 (2019-06-19) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-amd64 root=/dev/mapper/work01--vg-root ro quiet ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: LENOVO product_name: 20KHCTO1WW product_version: ThinkPad X1 Carbon 6th chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N23ET52W (1.27 ) board_vendor: LENOVO board_name: 20KHCTO1WW board_version: SDK0J40697 WIN ** Loaded modules: ctr ccm fuse sd_mod sg btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc hid_generic videobuf2_memops videobuf2_v4l2 videobuf2_common usbhid videodev drbg hid ansi_cprng media ecdh_generic nf_conntrack_netlink xfrm_user xfrm_algo devlink br_netfilter bridge stp llc aufs(OE) overlay uas usb_storage scsi_mod nft_chain_nat_ipv4 ipt_MASQUERADE nf_nat_ipv4 nf_nat xt_addrtype nf_log_ipv4 nf_log_common nft_limit nft_counter xt_LOG xt_limit xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nft_compat nf_tables nfnetlink arc4 binfmt_misc iTCO_wdt iTCO_vendor_support mei_wdt snd_soc_skl iwlmvm intel_rapl x86_pkg_temp_thermal snd_soc_skl_ipc intel_powerclamp mac80211 snd_soc_sst_ipc coretemp joydev snd_soc_sst_dsp snd_hda_codec_hdmi snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_generic snd_soc_acpi kvm_intel snd_soc_core snd_compress kvm irqbypass snd_hda_intel idma64 crct10dif_pclmul wmi_bmof crc32_pclmul iwlwifi snd_hda_codec xhci_pci ghash_clmulni_intel thinkpad_acpi snd_hda_core xhci_hcd intel_cstate cfg80211 snd_hwdep intel_uncore snd_pcm usbcore mei_me snd_timer nvram ucsi_acpi snd e1000e pcspkr mei intel_lpss_pci rfkill intel_rapl_perf intel_lpss i2c_i801 typec_ucsi processor_thermal_device int3403_thermal usb_common soundcore int340x_thermal_zone intel_pch_thermal battery intel_soc_dts_iosf tpm_crb ac typec tpm_tis tpm_tis_core tpm int3400_thermal acpi_thermal_rel rng_core acpi_pad pcc_cpufreq ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher af_alg dm_crypt dm_mod i915 crc32c_intel i2c_algo_bit drm_kms_helper aesni_intel drm nvme psmouse aes_x86_64 crypto_simd cryptd glue_helper nvme_core serio_raw thermal wmi evdev video button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:225c] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:225c] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [17aa:225c] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
Bug#931751: plymouth: Spinner theme won't properly display "watermark.png"
Package: plymouth Version: 0.9.4-1.1 Severity: normal Dear Maintainer, I copied "/usr/share/plymouth/debian-logo.png" to "/usr/share/plymouth/themes/spinner/watermark.png" and expected the image to show up in the middle of the screen. However, I instead saw the image on the far right of the screen, which I found ugly and unappealing. I recently switched from Arch after using it for a few days (too unstable) and the same bug occured on Arch, albeit with a different image, but this means it's an upstream bug. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plymouth depends on: ii init-system-helpers 1.56+nmu1 ii initramfs-tools 0.133 ii libc62.28-10 ii libdrm2 2.4.97-1 ii libplymouth4 0.9.4-1.1 ii lsb-base 10.2019051400 ii systemd 241-5 ii udev 241-5 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 10.0.2 ii plymouth-themes 0.9.4-1.1 -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=spinner -- no debconf information
Bug#931750: telegram-desktop: Packace uninstallable due to alleged lack of dependency
Package: telegram-desktop
Severity: grave
Justification: renders package unusable
I am unable to install this package.
For some reason it got uninstalled on Saturday after Buster's release and when
I try to install it, apt claims that it depends on qtbase-abi-5-11-3.
As the maintainer certaily knows, that's a metapackage that is provided by
libqt5core5a, which *is* installed on my system.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (900, 'stable'), (800, 'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8), LANGUAGE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to
en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages telegram-desktop depends on:
ii libavcodec58 7:4.1.3-1
ii libavformat58 7:4.1.3-1
ii libavutil567:4.1.3-1
ii libc6 2.28-10
ii libgcc11:9.1.0-7
ii libglib2.0-0 2.61.1-1
ii liblzma5 5.2.4-1
ii libminizip11.1-8+b1
ii libopenal1 1:1.19.1-1
ii libopus0 1.3-1
ii libqt5core5a 5.12.4+dfsg-4
ii libqt5dbus55.12.4+dfsg-4
ii libqt5gui5 5.12.4+dfsg-4
ii libqt5network5 5.12.4+dfsg-4
ii libqt5widgets5 5.12.4+dfsg-4
ii libssl1.1 1.1.1c-1
ii libstdc++6 9.1.0-7
ii libswresample3 7:4.1.3-1
ii libswscale57:4.1.3-1
ii libx11-6 2:1.6.7-1
ii libxxhash0 0.7.0-1
ii qt5-image-formats-plugins 5.12.4-1
pn qtbase-abi-5-11-3
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages telegram-desktop recommends:
ii fonts-open-sans 1.11-1
*** /home/fmneto/temp.txt
magi: /home/fmneto#> sudo apt install telegram-desktop
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
telegram-desktop : Depends: qtbase-abi-5-11-3
E: Unable to correct problems, you have held broken packages.
magi: /home/fmneto#> sudo aptitude install telegram-desktop
The following NEW packages will be installed:
telegram-desktop{b}
0 packages upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 16.8 MB of archives. After unpacking 44.4 MB will be used.
The following packages have unmet dependencies:
telegram-desktop : Depends: qtbase-abi-5-11-3 which is a virtual package,
provided by:
- libqt5core5a (5.11.3+dfsg1-1), but 5.12.4+dfsg-4
is installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) telegram-desktop [Not Installed]
Accept this solution? [Y/n/q/?]
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
magi: /home/fmneto#> sudo apt install libqt5core5a
Reading package lists... Done
Building dependency tree
Reading state information... Done
libqt5core5a is already the newest version (5.12.4+dfsg-4).
libqt5core5a set to manually installed.
Bug#931685: bash-completion: completion disables usage of environment variables
Control: merge 922657 931685 Control: stop On Tue, 09 Jul 2019 11:39:47 +0200 Michael Becker wrote: > > with an existing directory $HOME/devel > ls $HOME/dev > completes to > ls \$HOME/devel/ This has the same root cause of bug https://bugs.debian.org/922657, i.e.: in _quote_readline_by_ref, the backslash gets added by: printf -v $2 %q "$1" This has been reported upstream as https://github.com/scop/bash-completion/issues/290 I'm merging the bug reports. Thanks, Gabriel
Bug#931671: vokoscreen: I don't see the screen just the cursor
I've solved the issue : I've deleted my ./config directory... I'm sorry for disturbing. Thanks again Best regards Charles Le 10/07/2019 à 02:05, Eriberto a écrit : > Em ter, 9 de jul de 2019 às 20:41, Charles BLANC ROLIN > escreveu: >> Since I've upgraded from Stretch to Buster, I know some bugs with Gnome, >> so it's spossible to the problem come from that... > Thanks! > > I use KDE. Can you test in a fresh install using openbox? > > Cheers, > > Eriberto signature.asc Description: OpenPGP digital signature
Bug#931647: Acknowledgement (movim deb package does not save URL edits during installation; later dpkg-reconfigure works OK)
Exploring this issue further, it's looking like a possible race condition. If one downloads the movim debian package, and installs it with "dpkg -i", the user is prompted for their debconf selections, and then the file (/etc/default/movim) is pushed out incorporating user choices -- the ideal situation. However, if one installs movim using "apt-get install", the configuration file gets pushed out, then the user is prompted for their selections, which then get lost (as default values are read in from the configuration file pushed out). One can observe this behaviour if they keep a copy of /etc/default/movim (possibly seeded with an alternate value) and put it in place before installing movim. One potential fix might be to alter "debian/movim.config" to check debconf if the user has set a debconf value for movim/public_url , rather than just reading a value from the configuration file (which may be the default one pushed out by the package). There may be a better way to work around this potential race condition that I'm not familiar with. regards, donfede On Mon, Jul 08, 2019 at 06:54:04PM +, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 931647: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931647. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian XMPP Maintainers > > If you wish to submit further information on this problem, please > send it to 931...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 931647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931647 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- I choose information and knowledge over profit.
Bug#931749: [pkg-cryptsetup-devel] Bug#931749: cryptsetup: "no longer required" on encrypted system!
Control: reassign -1 deborphan Control: severity -1 wishlist Control: retitle -1 Removing dummy packages should marks dependencies as manually installed Hi, On Wed, 10 Jul 2019 at 00:01:00 +0100, Conrad J.C. Hughes (for Debian package stuff) wrote: > So this is probably a buster upgrade issue, but not sure where to report it.. > > After upgrading to buster, deborphan --guess-dummy (seemingly correctly) > identified cryptsetup as a transitional dummy package, suitable for removal. > However after removing cryptsetup, apt now tells me all the time that > cryptsetup-bin, cryptsetup-initramfs and cryptsetup-run "were automatically > installed and are no longer required". But my system's LUKS1-on-LVM-RAID-1.. > Running "apt autoremove" at this point would surely cause chaos? Sounds like a feature request for deborphan, reassigning and retitling accordingly. cryptsetup.NEWS reads cryptsetup (2:2.0.3-1) unstable; urgency=medium With this version, cryptsetup has been split into cryptsetup-run (init script) and cryptsetup-initramfs (initramfs integration). 'cryptsetup' is now a transitional dummy package depending on cryptsetup-run and cryptsetup-initramfs. -- Guilhem Moulin Wed, 16 May 2018 23:39:20 +0200 So if you remove the transition package you'll also need to `apt mark manual` the dependencies. I guess deborphan could do that automatically? For what it's worth in your case marking ‘cryptsetup-initramfs’ only as manually installed should be enough, because the package depends on ‘cryptsetup-run’. On a system where the initramfs integration is not needed, one could instead remove ‘cryptsetup-initramfs’ and mark ‘cryptsetup-run’ as manually installed. Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#931671: vokoscreen: I don't see the screen just the cursor
Em ter, 9 de jul de 2019 às 20:41, Charles BLANC ROLIN escreveu: > > Since I've upgraded from Stretch to Buster, I know some bugs with Gnome, > so it's spossible to the problem come from that... Thanks! I use KDE. Can you test in a fresh install using openbox? Cheers, Eriberto
Bug#931749: cryptsetup: "no longer required" on encrypted system!
Package: cryptsetup Version: 2:2.1.0-5 Severity: normal Dear Maintainer, So this is probably a buster upgrade issue, but not sure where to report it.. After upgrading to buster, deborphan --guess-dummy (seemingly correctly) identified cryptsetup as a transitional dummy package, suitable for removal. However after removing cryptsetup, apt now tells me all the time that cryptsetup-bin, cryptsetup-initramfs and cryptsetup-run "were automatically installed and are no longer required". But my system's LUKS1-on-LVM-RAID-1.. Running "apt autoremove" at this point would surely cause chaos? Conrad -- Package-specific info: -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup depends on: ii cryptsetup-initramfs 2:2.1.0-5 ii cryptsetup-run2:2.1.0-5 cryptsetup recommends no packages. cryptsetup suggests no packages. -- debconf information: cryptsetup/prerm_active_mappings: true
Bug#931671: vokoscreen: I don't see the screen just the cursor
Hi, Thanks for your answer and your great job ! Since I've upgraded from Stretch to Buster, I know some bugs with Gnome, so it's spossible to the problem come from that... Best regards, Charles Le 09/07/2019 à 20:04, Eriberto Mota a écrit : > Control: tags 931671 moreinfo unreproducible > > Em ter, 9 de jul de 2019 às 03:15, Charles BLANC ROLIN > escreveu: >> Dear Maintainer, >> >> When I capture, I don't see the screen on the video, only the cursor. > Hi Charles, > > Thanks for your report. I can't reproduce it in vokoscreen 2.5.0-2 > over Debian 10. > > Can you execute '$ rm ~/.config/vokoscreen' and try again? If not > working, can you try over a fresh install? I think it is a specific > problem in your system, not vokoscreen. > > Regards, > > Eriberto signature.asc Description: OpenPGP digital signature
Bug#931748: Please add audit support to log installation/update of a package
Package: dpkg Version: 1.19.7 Severity: wishlist Usertags: audit Hi, It would be nice if dpkg was logging audit events when packages are installed/updated/removed/... The type of the message is AUDIT_SOFTWARE_UPDATE, the content is not documented, AFAICS, the messages look something like: op=install sw="ntpdate-4.2.6p5-25.el7_3.2.x86_64" sw_type=rpm key_enforce=0 gpg_res=0 root_dir="/" rpm is already doing that, and the code is available at https://github.com/rpm-software-management/rpm/blob/master/plugins/audit.c Kind regards, Laurent Bigonville -- Package-specific info: System tainted due to merged-usr-via-symlinks. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-9.1 ii libc62.28-10 ii liblzma5 5.2.4-1 ii libselinux1 2.9-2 ii tar 1.30+dfsg-6 ii zlib1g 1:1.2.11.dfsg-1 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt1.8.2 pn debsig-verify -- no debconf information
Bug#931746: neomutt: /etc/neomuttrc tries to source /usr/lib/neomutt/source-neomuttrc.d which is not existing
Package: neomutt
Version: 20180716+dfsg.1-1.1
Severity: normal
Starting neomutt I see
sh: 1: /usr/lib/neomutt/source-neomuttrc.d: not found
becasue /etc/neomuttrc contains
source /usr/lib/neomutt/source-neomuttrc.d|
but this directory is not shipped
Thanks
-- Package-specific info:
NeoMutt 20180716
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.
System: Linux 5.1.15 (x86_64)
ncurses: ncurses 6.1.20181013 (compiled with 6.1.20181013)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet
Compiler:
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.3.0-7'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.3.0 (Debian 8.3.0-7)
Configure options: --build=x86_64-linux-gnu --prefix=/usr
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man}
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules {--libdir=${prefix}/lib/x86_64-linux-gnu}
{--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode
--disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec
--with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls --gss
--idn --mixmaster --sasl --tokyocabinet
Compilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/neomutt-uNPuRY/neomutt-20180716+dfsg.1=.
-fstack-protector-strong -Wformat -Werror=format-security -std=c99
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include
-I/usr/include/lua5.3 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5
Default options:
+attach_headers_color +compose_to_sender +compress +cond_date +debug
+encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color
+initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop
+progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar
+skip_quoted +smtp +status_color +timeout +tls_sni +trash
Compile options:
+bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens +getaddrinfo
+gnutls +gpgme +gss +hcache -homespool +idn -locales_hack +lua +meta
+mixmaster +nls +notmuch -openssl +pgp +sasl +smime +start_color
+sun_attachment +typeahead
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"
To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.1.15 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages neomutt depends on:
ii libc6 2.28-10
ii libcom-err2 1.45.2-1
ii libgnutls30 3.6.8-2
ii libgpgme111.12.0-6
ii libgssapi-krb5-2 1.17-4
ii libidn11 1.33-2.2
ii libk5crypto3 1.17-4
ii libkrb5-3 1.17-4
ii liblua5.3-0 5.3.3-1.1
ii libncursesw6 6.1+20181013-2
ii libnotmuch5 0.28.4-1
ii libsasl2-22.1.27+dfsg-1
ii libtinfo6 6.1+20181013-2
ii libtokyocabinet9 1.4.48-12
Versions of packages neomutt recommends:
ii libsasl2-modules 2.1.27+dfsg-1
ii locales 2.28-10
ii mime-support 3.62
Versions of packages neomutt suggests:
ii aspell 0.60.7~20110707-6
ii
Bug#931747: gnome-terminal: Window dimensions tooltip missing when resizing under Wayland
Package: gnome-terminal Version: 3.30.2-2 Severity: normal Dear Maintainer, Buster upgrade issue: when resizing gnome-terminal windows under Wayland, there's no window dimensions tooltip. Logging in under Classic Gnome, the tooltip's there. Bug reported elsewhere too: https://bugzilla.redhat.com/show_bug.cgi?id=1306260 Best, Conrad -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gnome-terminal-data 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libdconf1 0.30.1-2 ii libglib2.0-0 2.58.3-2 ii libgtk-3-03.24.5-1 ii libpango-1.0-01.42.4-6 ii libuuid1 2.33.1-0.1 ii libvte-2.91-0 0.54.2-2 ii libx11-6 2:1.6.7-1 Versions of packages gnome-terminal recommends: ii gvfs 1.38.1-5 ii nautilus-extension-gnome-terminal 3.30.2-2 ii yelp 3.31.90-1 gnome-terminal suggests no packages. -- no debconf information
Bug#931745: dovecot-core: mkcert.sh instructions are not debian-ready
Package: dovecot-core
Version: 1:2.3.4.1-5
Severity: minor
Dear Maintainer,
This is an easy one just for clarity of instructions:)
After last upgrade, I found that I need to redo my self-signed certificates.
I was able to accomplish
this by adapting instructions in the comments of conf.d/10-master.conf that
pointed to doc/mkcert.sh. In Debian
that file is actually /share/dovecot/mkcert.sh. Furthermore, in that file,
CERTDIR and KEYDIR, should be
/etc/dovecot/private rather than its current value.
Otherwise it works flawlessly. Thanks!
Patricio
-- Package-specific info:
dovecot configuration
-
# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 ()
# OS: Linux 4.9.0-8-amd64 x86_64 Debian 10.0
# Hostname: wasabi.das.uchile.cl
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_privileged_group = mail
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
protocols = " imap"
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
ssl = required
ssl_cert =
ii dovecot-imapd 1:2.3.4.1-5
pn dovecot-ldap
pn dovecot-lmtpd
pn dovecot-lucene
pn dovecot-managesieved
pn dovecot-mysql
pn dovecot-pgsql
pn dovecot-pop3d
pn dovecot-sieve
pn dovecot-solr
pn dovecot-sqlite
pn dovecot-submissiond
ii ntp 1:4.2.8p12+dfsg-4
Versions of packages dovecot-core is related to:
ii dovecot-core [dovecot-common] 1:2.3.4.1-5
pn dovecot-dev
pn dovecot-gssapi
ii dovecot-imapd 1:2.3.4.1-5
pn dovecot-ldap
pn dovecot-lmtpd
pn dovecot-managesieved
pn dovecot-mysql
pn dovecot-pgsql
pn dovecot-pop3d
pn dovecot-sieve
pn dovecot-sqlite
-- no debconf information
Bug#931744: gnome-terminal: "Show bold text in bright colours" has no effect
Package: gnome-terminal Version: 3.30.2-2 Severity: normal Dear Maintainer, Buster upgrade issue: after upgrading to buster I find bold text barely noticeable. I'm pretty sure that prior to upgrade it was highlighted with a brighter colour. I can see a "Show bold text in bright colours" checkbox in my colour scheme, and it's checked, but turning it on and off has no effect (unlike, say, checking the "Highlight colour" box, which has an instant effect). Holds true for six of the schemes I've tried (including "colours from system theme" checkbox), Solarized Dark being my "usual". Best, Conrad -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gnome-terminal-data 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libdconf1 0.30.1-2 ii libglib2.0-0 2.58.3-2 ii libgtk-3-03.24.5-1 ii libpango-1.0-01.42.4-6 ii libuuid1 2.33.1-0.1 ii libvte-2.91-0 0.54.2-2 ii libx11-6 2:1.6.7-1 Versions of packages gnome-terminal recommends: ii gvfs 1.38.1-5 ii nautilus-extension-gnome-terminal 3.30.2-2 ii yelp 3.31.90-1 gnome-terminal suggests no packages. -- no debconf information
Bug#929675: mojolicious: HTTPS / SSL / TLS is broken
On Wed, 3 Jul 2019 09:49:14 +0100 Nick Morrott wrote: > On Sun, 23 Jun 2019 at 01:58, Nick Morrott wrote: > > > > > Upstream tried to help, but seems to be out of ideas: > > > > > > https://groups.google.com/forum/#!topic/mojolicious/gjz-0uvUDLk > > > > I have posted an update to that thread (currently held for > > moderation). I have also created an upstream PR [2] which provides a > > TLS 1.2-compliant keypair: > > > > [2] https://github.com/mojolicious/mojo/pull/1371 > > Upstream have now created a new TLS keypair which will be included in > the next Mojolicious release. > > My current plan is to review the update and upload a new 8.12 build > targetting the first Debian "buster" point release which includes the > updated keypair. Thank you! Celejar
Bug#931743: developers-reference: Improve documentation for stable updates (5.5.1)
Package: developers-reference Version: 3.4.25 Severity: normal It would be helpful if chapter 5.5.1 would include more information, especially either explicitly the update criteria that can be found in the message below or a link/reference leading there. https://lists.debian.org/debian-devel-announce/2018/04/msg7.html (linked from https://release.debian.org ) Making these criteria more accessible would probably also reduce the workload of the release-team. Regards, Carsten
Bug#931742: Package new version of Rapid Photo Downloader
Package: rapid-photo-downloader Version: 0.9.13-1 Severity: important Version 0.9.15 is released, with several important bug fixes compared to 0.9.13. Translations are also updated. As an additional step, please note these important packaging changes compared to the current Debian package are -- Add as required packages: gir1.2-glib-2.0 gir1.2-gstreamer-1.0 libgphoto2-6 libraw-bin python3-tenacity Remove these packages (they are not used): ffmpegthumbnailer python3-dbus Thank you. Best, Damon Lynch -- http://www.damonlynch.net
Bug#931278: bzip2: Fix for CVE-2019-12900 breaks uncompressing some lbzip2 files
On Tue, 2019-07-09 at 22:06 +0200, Salvatore Bonaccorso wrote: > The patch seems to have evolved to > https://sourceware.org/ml/bzip2-devel/2019-q3/msg7.html. Were > there any more issues found? Should downstream distros who picked up > the CVE-2019-12900 safely include this patch? Yes. It was just committed upstream: https://sourceware.org/git/?p=bzip2.git;a=commit;h=b07b105d1b66e32760095e3602261738443b9e13 No other issues were found. But some time was spend creating and integrating a new testsuite: https://sourceware.org/git/bzip2-tests.git with the buildbot: https://builder.wildebeest.org/buildbot/#/builders?tags=bzip2 To make sure we didn't overlook any other issues. We are now looking at better integration with some fuzzers to catch any other issues. Expect a 1.0.8 release soon (days, not weeks) with the patch and some other small fixes. Cheers, Mark
Bug#931581: Acknowledgement (tiger: purging tiger package fails in postrm because /var/log/tiger is removed before somehow)
I use the following patch in a PPA package at
https://launchpad.net/~dominik-stadler/+archive/ubuntu/ppa/+packages to
make it work for me
--- tiger-3.2.4~rc1.orig/debian/postrm
+++ tiger-3.2.4~rc1/debian/postrm
@@ -11,9 +11,8 @@
purge)
for dir in /var/log/tiger/ /var/lib/tiger/work /var/lib/tiger/
/var/run/tiger/
do
- [ -d "$dir" ] && {
- find "$dir" -type d -o -exec rm -f {} \;
- find "$dir" -type d -exec rmdir {} \;
+ [ -d "$dir" ] && {
+ rm -rf "$dir"
}
done
# Do we have any tigerXX files under /var/log/? if so we should remove
On Sun, Jul 7, 2019 at 10:45 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 931581:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931581.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> Javier Fernández-Sanguino Peña
>
> If you wish to submit further information on this problem, please
> send it to 931...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 931581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931581
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
Bug#880497: pytimechart: diff for NMU version 1.0.0~rc1-3.3
Package: pytimechart
Version: 1.0.0~rc1-3.2
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for pytimechart (versioned as 1.0.0~rc1-3.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru pytimechart-1.0.0~rc1/debian/changelog pytimechart-1.0.0~rc1/debian/changelog
--- pytimechart-1.0.0~rc1/debian/changelog 2015-03-26 02:25:04.0 -0300
+++ pytimechart-1.0.0~rc1/debian/changelog 2019-07-09 16:15:49.0 -0300
@@ -1,3 +1,11 @@
+pytimechart (1.0.0~rc1-3.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing dependencies: python-fonttools, python-kiwisolver.
+Thanks to Antonio Ospite . (Closes #880497)
+
+ -- William Grzybowski Tue, 09 Jul 2019 16:15:49 -0300
+
pytimechart (1.0.0~rc1-3.2) unstable; urgency=low
* Non-maintainer upload with maintainer's permission.
diff -Nru pytimechart-1.0.0~rc1/debian/control pytimechart-1.0.0~rc1/debian/control
--- pytimechart-1.0.0~rc1/debian/control 2015-03-26 02:24:05.0 -0300
+++ pytimechart-1.0.0~rc1/debian/control 2019-07-09 16:06:11.0 -0300
@@ -13,7 +13,8 @@
Package: pytimechart
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
- python-enthoughtbase, python-chaco, python-wxgtk3.0, python-gtk2
+ python-enthoughtbase, python-chaco, python-wxgtk3.0, python-gtk2,
+ python-fonttools, python-kiwisolver
XB-Python-Version: ${python:Versions}
Description: GUI Viewer for Linux kernel traces
PyTimechart provides explorability and overall visualization of Linux
signature.asc
Description: This is a digitally signed message part
Bug#930917: [Pkg-javascript-devel] Bug#930917: Bug#930917: Bug#930917: Include import test like require test when package.json#module is present
Le 09/07/2019 à 21:22, Xavier a écrit :
> Le 09/07/2019 à 11:27, Pirate Praveen a écrit :
>>
>>
>> On 2019, ജൂലൈ 9 2:12:43 PM IST, Xavier wrote:
>>> Hello,
>>>
>>> pkg-js-autopkgtest launches 2 tests:
>>> - a `node -e 'require("package")'
>>> - upstream tests on installed files
>>>
>>> is it enough ?
>>
>> For packages that only provide commonjs/umd modules, that should be enough.
>>
>> For packages that also provide ES module, we should test they are installed
>> properly. This can be confirmed if package.json has a "module" field or not.
>>
>> We could write a ES6 js file with import * from "package" and run rollup on
>> it as node does not natively support import yet.
>>
>> es-module-test.js:
>>
>> import * from "package"
>>
>> Then run,
>>
>> rollup es-module-test.js -f umd -o bundle.js
>>
>> Or possibly,
>> es-module-test.mjs:
>> import * from "package"
>>
>> node --experimental-modules es-module-test.js
>>
>> Note: not tested the code
>
> OK, `import foo from "d3-dsv"` works fine.
> Do I have to launch this test every time a "module" exists in package.json ?
>
> Cheers,
> Xavier
Pushed to experimental, let's test it !
Bug#931632: lintian: Testsuite hangs in/around "debian/test-out/tags/checks/version-substvars/legacy-etcfiles"
Felix, > Please take a look at the following commit. It solved a similar issue > in two other tests. Perhaps you find it helpful. Thanks for the link and it's likely the "fix" but it really explain why it failed previously for me and doesn't for you... (Will rebuild and report this evening most likely...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#931741: pytimechart: diff for NMU version 1.0.0~rc1-3.3
Package: pytimechart
Version: 1.0.0~rc1-3.2
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for pytimechart (versioned as 1.0.0~rc1-3.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru pytimechart-1.0.0~rc1/debian/changelog pytimechart-1.0.0~rc1/debian/changelog
--- pytimechart-1.0.0~rc1/debian/changelog 2015-03-26 02:25:04.0 -0300
+++ pytimechart-1.0.0~rc1/debian/changelog 2019-07-09 16:15:49.0 -0300
@@ -1,3 +1,11 @@
+pytimechart (1.0.0~rc1-3.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing dependencies: python-fonttools, python-kiwisolver.
+Thanks to Antonio Ospite . (Closes #880497)
+
+ -- William Grzybowski Tue, 09 Jul 2019 16:15:49 -0300
+
pytimechart (1.0.0~rc1-3.2) unstable; urgency=low
* Non-maintainer upload with maintainer's permission.
diff -Nru pytimechart-1.0.0~rc1/debian/control pytimechart-1.0.0~rc1/debian/control
--- pytimechart-1.0.0~rc1/debian/control 2015-03-26 02:24:05.0 -0300
+++ pytimechart-1.0.0~rc1/debian/control 2019-07-09 16:06:11.0 -0300
@@ -13,7 +13,8 @@
Package: pytimechart
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
- python-enthoughtbase, python-chaco, python-wxgtk3.0, python-gtk2
+ python-enthoughtbase, python-chaco, python-wxgtk3.0, python-gtk2,
+ python-fonttools, python-kiwisolver
XB-Python-Version: ${python:Versions}
Description: GUI Viewer for Linux kernel traces
PyTimechart provides explorability and overall visualization of Linux
signature.asc
Description: This is a digitally signed message part
Bug#931632: lintian: Testsuite hangs in/around "debian/test-out/tags/checks/version-substvars/legacy-etcfiles"
Also, should this bug be retitled?
Bug#931740: imagemagick: CVE-2019-13454
Source: imagemagick Version: 8:6.9.10.23+dfsg-2.1 Severity: important Tags: security upstream Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1629 Hi, The following vulnerability was published for imagemagick. CVE-2019-13454[0]: | ImageMagick 7.0.8-54 Q16 allows Division by Zero in | RemoveDuplicateLayers in MagickCore/layer.c. 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-2019-13454 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13454 [1] https://github.com/ImageMagick/ImageMagick/issues/1629 [2] https://github.com/ImageMagick/ImageMagick6/commit/4f31d78716ac94c85c244efcea368fea202e2ed4 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#931739: quassel-core: key too small error after upgrade to buster
Package: quassel-core Version: 1:0.13.1-1 Severity: normal Dear Maintainer, After upgrading to buster and restarting quassel-core whenever a client attempts to connect it fails and the log shows: Socket error 21: Error loading local certificate, error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (700, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages quassel-core depends on: ii adduser3.118 ii libc6 2.28-10 ii libgcc11:8.3.0-6 ii libqca-qt5-2 2.1.3-2 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5script5 5.11.3+dfsg-3 ii libqt5sql5 5.11.3+dfsg1-1 ii libqt5sql5-sqlite 5.11.3+dfsg1-1 ii libstdc++6 8.3.0-6 ii lsb-base 10.2019051400 ii openssl1.1.1c-1 ii zlib1g 1:1.2.11.dfsg-1 quassel-core recommends no packages. Versions of packages quassel-core suggests: ii libqt5sql5-psql 5.11.3+dfsg1-1 -- no debconf information
Bug#931632: lintian: Testsuite hangs in/around "debian/test-out/tags/checks/version-substvars/legacy-etcfiles"
Please take a look at the following commit. It solved a similar issue in two other tests. Perhaps you find it helpful. https://salsa.debian.org/lintian/lintian/commit/d1d7acdb7ee124b6f59def18e5cfae9cd7e3592d On Tue, Jul 9, 2019 at 12:59 PM Chris Lamb wrote: > Hi Felix, > > > Also, can this bug be reassigned or closed? > > I'm a bit lost. Reassigned? Or closed? Did you mean to send this to > this particular bug? > > I mean, I am still in the process of debugging this (actual) issue as > per your instructions here: > > https://bugs.debian.org/931632#40 > > (Update soon...) > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org chris-lamb.co.uk >`- >
Bug#931278: bzip2: Fix for CVE-2019-12900 breaks uncompressing some lbzip2 files
Hi Mark, On Tue, Jul 02, 2019 at 10:10:21PM +0200, Salvatore Bonaccorso wrote: > Hey Mark! > > On Mon, Jul 01, 2019 at 12:33:06AM +0200, Mark Wielaard wrote: > > Hi Salvatore, > > > > On Sun, 2019-06-30 at 19:28 +0200, Salvatore Bonaccorso wrote: > > > Testing and feedback appreciated. > > > > > > it is not very helpfull I think, because I do not have a good testing > > > corpus. What I did is to apply the patch on top of our current > > > 1.0.6-9.1 (which has the issue after fixing CVE-2019-12900), and > > > tested it with the problematic file from > > > > > https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-package-31-1-0 > > > . > > > > > > But apart from that I do not have at them moment better feedback :( > > > > That is already great feedback thanks. > > > > But you are right that it would be good to have a better testing > > corpus. It isn't much, but I have setup an initial bzip2 test suite: > > https://sourceware.org/git/?p=bzip2-tests.git;a=summary > > > > It is a little bare bones right now, but the README will hopefully help > > to see how to run it on some other collection of .bz2 files. > > > > It does already contain a testcase that still fails with the proposed > > patch. It is a really odd corner case, but since we accepted it in the > > past, we should really make sure it works in the future too. > > > > I'll discuss an alternative patch upstream. > > Thanks. For context here in the bug, the alternative apporach patch is > posted at https://sourceware.org/ml/bzip2-devel/2019-q2/msg00035.html > . The patch seems to have evolved to https://sourceware.org/ml/bzip2-devel/2019-q3/msg7.html. Were there any more issues found? Should downstream distros who picked up the CVE-2019-12900 safely include this patch? Regards, Salvatore
Bug#931738: ITP: libkainjow-mustache -- Mustache text templates for modern C++
Package: wnpp Severity: wishlist Owner: Kunal Mehta * Package name: libkainjow-mustache Version : 3.2.1 Upstream Author : Kevin Wojniak * URL : https://github.com/kainjow/Mustache * License : BSL-1.0 Programming Lang: C++ Description : Mustache text templates for modern C++ A header-only Mustache template implementation for C++11, with no additional dependencies. This is a new dependency for the latest version of libkiwix, replacing the unmaintained ctpp2 library.
Bug#931632: lintian: Testsuite hangs in/around "debian/test-out/tags/checks/version-substvars/legacy-etcfiles"
Hi Felix, > Also, can this bug be reassigned or closed? I'm a bit lost. Reassigned? Or closed? Did you mean to send this to this particular bug? I mean, I am still in the process of debugging this (actual) issue as per your instructions here: https://bugs.debian.org/931632#40 (Update soon...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#929729: lintian: \n in filenames cause "md5sum: ...: No such file or directory"
Hi Felix, > The index files seem to be inspired by the 't' option in tar. My sense > is that we need more encoding rather than less to preserve the meaning > of whitespace, and especially newlines, in those files. Sure thing. I guess unless we moved these to a "NUL"-terminated format but that's going to be a little too annoying in Perl and non-intuitive to boot. > > adjust all the consumer/producers of that data to reflect that? The > > current situation as I understand it is that some assume the former, > > some the latter. > > I believe there is only one of each. Please let me know if you found others. [..] > which uses the subroutine 'dequote_name' from here: Sounds about right. But just to add: when I was looking at this issue before I tried using exactly this routine in the producers & consumers and IIRC this actually caused further breakage. YMMV. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#931636: doesnt bring up virtio interface link with kernel 5.2
Am 09.07.19 um 21:41 schrieb Marc Haber: > On Tue, Jul 09, 2019 at 07:16:07PM +0200, Michael Biebl wrote: >> Can you test those patches to verify that they fix your issue? > > Even an unpatched systemd 241-6 fails building in my sid build chroot: > > 433/514 test-bus-watch-bind FAIL 0.03 s (killed by > signal 6 SIGABRT) > 333/514 test-fd-utilFAIL 0.03 s (killed by > signal 6 SIGABRT) > 331/514 test-fs-utilFAIL 0.03 s (killed by > signal 6 SIGABRT) > > Any special reason for that? The build machine has 8 Gig of RAM and 10 > Gig of disk free. No idea why it fails on your particular system. You'd probably have to debug that on-site. Or you can skip the test-suite via the "nocheck" build flag. dpkg-buildpackage -Pnocheck or export DEB_BUILD_OPTIONS=nocheck -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#931737: kdepim-runtime: Imap session login cancelled
Package: kdepim-runtime Version: 4:18.08.3-4 Severity: normal Dear Maintainer, With Debian Buster akonadi does not work anymore with aruba imap server, goes in a loop "idle/connection established" without downloading anything. In .xsession-errors file there are infinite occurrences of : org.kde.pim.kimap: Connection to server lost 9 org.kde.pim.imapresource: Session login cancelled -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdepim-runtime depends on: ii akonadi-server 4:18.08.3-5 ii kio 5.54.1-1 ii kio-ldap 18.08.3-1 ii libc62.28-10 ii libgcc1 1:8.3.0-6 ii libkf5akonadiagentbase5 4:18.08.3-5 ii libkf5akonadicalendar5abi1 4:18.08.3-1 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-5 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadinotes5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-5 ii libkf5alarmcalendar5abi1 4:18.08.3-2 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5identitymanagement518.08.3-2 ii libkf5imap5 18.08.3-1 ii libkf5itemmodels55.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kdelibs4support5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5mailtransport5 18.08.3-2 ii libkf5mailtransportakonadi5 18.08.3-2 ii libkf5mbox5 18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libkolabxml1v5 1.1.6-4 ii libkpimgapicalendar5 18.08.3-2 ii libkpimgapicontacts5 18.08.3-2 ii libkpimgapicore5abi1 18.08.3-2 ii libkpimgapitasks518.08.3-2 ii libkpimkdav5abi2 18.08.3-2 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5texttospeech5 5.11.3-3 ii libqt5webenginecore5 5.11.3+dfsg-2+b1 ii libqt5webenginewidgets5 5.11.3+dfsg-2+b1 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5xml5 5.11.3+dfsg1-1 ii libsasl2-2 2.1.27+dfsg-1 ii libsasl2-modules-kdexoauth2 18.08.3-2 ii libstdc++6 8.3.0-6 kdepim-runtime recommends no packages. kdepim-runtime suggests no packages. -- no debconf information
Bug#931636: doesnt bring up virtio interface link with kernel 5.2
On Tue, Jul 09, 2019 at 07:16:07PM +0200, Michael Biebl wrote: > Can you test those patches to verify that they fix your issue? Even an unpatched systemd 241-6 fails building in my sid build chroot: 433/514 test-bus-watch-bind FAIL 0.03 s (killed by signal 6 SIGABRT) 333/514 test-fd-utilFAIL 0.03 s (killed by signal 6 SIGABRT) 331/514 test-fs-utilFAIL 0.03 s (killed by signal 6 SIGABRT) Any special reason for that? The build machine has 8 Gig of RAM and 10 Gig of disk free. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#931736: h5py: FTBFS against HDF5 1.10.5
Source: h5py Version: 2.9.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, During a rebuild against HDF5 1.10.5 currently in experimental, h5py FTBFS with: set -e; for DIR in $(find .pybuild -name build | grep -v _dbg_); do \ cd $DIR; PYTHONPATH=. python$(echo $DIR | sed -e 's@.*cpython._\(.*\)_h5py.*@\1@g') \ -c "from sys import exit; import h5py; exit(0) if h5py.run_tests().wasSuccessful() else exit(1)"; \ cd ../../..; done ...E...xxs/build/h5py-V5ZcPx/h5py-2.9.0/.pybuild/cpython3_3.7_h5py/build/h5py/_hl/files.py:258: H5pyDeprecationWarning: File.fid has been deprecated. Use File.id instead. "Use File.id instead.", H5pyDeprecationWarning) ...s..ss...ss.xx.x..x.. == ERROR: test_track_order (h5py.tests.old.test_attrs.TestTrackOrder) - -- Traceback (most recent call last): File "/build/h5py-V5ZcPx/h5py-2.9.0/.pybuild/cpython3_3.7_h5py/build/h5py/tests/old/test_attrs.py", line 180, in test_track_order attrs = self.fill_attrs(track_order=True) # creation order File "/build/h5py-V5ZcPx/h5py-2.9.0/.pybuild/cpython3_3.7_h5py/build/h5py/tests/old/test_attrs.py", line 174, in fill_attrs attrs[str(i)] = i File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper File "/build/h5py-V5ZcPx/h5py-2.9.0/.pybuild/cpython3_3.7_h5py/build/h5py/_hl/attrs.py", line 95, in __setitem__ self.create(name, data=value, dtype=base.guess_dtype(value)) File "/build/h5py-V5ZcPx/h5py-2.9.0/.pybuild/cpython3_3.7_h5py/build/h5py/_hl/attrs.py", line 210, in create h5a.rename(self._id, self._e(tempname), self._e(name)) File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper File "h5py/h5a.pyx", line 118, in h5py.h5a.rename RuntimeError: Can't rename attribute (record is already in B-tree) - -- Ran 509 tests in 1.117s FAILED (errors=1, skipped=14, expected failures=6) Thanks, _g. -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl0k7QoACgkQ7+hsbH/+ z4PPRAf6A5KCbfbFgHQK0+9WVbl1RX0Kb0xk0LLlfWVzV66vKOZ0Sq9q0hnci9Wv hFPAfA0IMfKVYyzUJfcXyXEEruR+mKRCvgs1UQKLlfVsvlWPt3lOZW9k51GY0x7+ 9a6DN+6JxJznSf+wTBz9dtIetlTarbG6D817xqQlcVMVRYMN5KID0MTDtfsDo2V4 E2mUX7enp1CbZsgkU0nVjtKGltxBal5sShYyszlIO3yNC34hwVT4wxQiMDDvppY8 rLRsUUd+fOxgkzqJEflAFdtqVxL65SVXbH6wMwY/Tu6jahwy4ipVXV1M6rB9Ko6i pC6k59uTMXrfAA2rbvn/scX7oMnVqw== =M+OC -END PGP SIGNATURE-
Bug#931735: photoprint: Unable to install photoprint in debian 10 and Testing
Package: photoprint Version: 0.4.2-1.11 Severity: important Dear Maintainer, I tried to install https://packages.debian.org/jessie/photoprint (jessie and sid packages) but I was unable to do it. Could you provide a compilation or instructions to compile this app into a Debian testing or Debian 10 branch. This is a nice app and very useful. It is a pitty not being able to use it. Thanks a lot! -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-20.2-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), LANGUAGE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#930917: [Pkg-javascript-devel] Bug#930917: Bug#930917: Include import test like require test when package.json#module is present
Le 09/07/2019 à 11:27, Pirate Praveen a écrit :
>
>
> On 2019, ജൂലൈ 9 2:12:43 PM IST, Xavier wrote:
>> Hello,
>>
>> pkg-js-autopkgtest launches 2 tests:
>> - a `node -e 'require("package")'
>> - upstream tests on installed files
>>
>> is it enough ?
>
> For packages that only provide commonjs/umd modules, that should be enough.
>
> For packages that also provide ES module, we should test they are installed
> properly. This can be confirmed if package.json has a "module" field or not.
>
> We could write a ES6 js file with import * from "package" and run rollup on
> it as node does not natively support import yet.
>
> es-module-test.js:
>
> import * from "package"
>
> Then run,
>
> rollup es-module-test.js -f umd -o bundle.js
>
> Or possibly,
> es-module-test.mjs:
> import * from "package"
>
> node --experimental-modules es-module-test.js
>
> Note: not tested the code
OK, `import foo from "d3-dsv"` works fine.
Do I have to launch this test every time a "module" exists in package.json ?
Cheers,
Xavier
Bug#931734: samba-common-bin.postinst fails when role is ad-dc and ldb backend is used
Package: samba-common-bin Version: 2:4.9.11+dfsg-1 Severity: normal Dear Maintainer, * What led up to the situation? upgrade from stretch to buster * What exactly did you do (or not do) that was effective (or ineffective)? diverted testparm and replaced it with script that called "samba-tool testparm" the postinst checks for role of samba _after_ a plain testparm call which fails because it is not supposed to be used on ad-dc https://bugzilla.samba.org/show_bug?id=12629#c7 (last comment) this diff should fix the problem: --- samba-common-bin.postinst 2019-07-08 09:56:36.0 +0200 +++ samba-common-bin.postinst.fixed 2019-07-09 21:11:49.284682976 +0200 @@ -2,15 +2,15 @@ set -e -echo "Checking smb.conf with testparm" -testparm -d1 --suppress-prompt > /dev/null -echo "Done" - SERVER_ROLE=`samba-tool testparm --parameter-name="server role" 2>/dev/null | tail -1` if [ "$SERVER_ROLE" = "active directory domain controller" ]; then echo "Checking smb.conf with samba-tool" samba-tool testparm -d1 --suppress-prompt > /dev/null echo "Done" +else +echo "Checking smb.conf with testparm" +testparm -d1 --suppress-prompt > /dev/null +echo "Done" fi * What was the outcome of this action? configuration of samba packages failed. * What outcome did you expect instead? samba packages configured and installed ok -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_FORCED_RMMOD Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba-common-bin depends on: ii libbsd00.9.1-2 ii libc6 2.28-10 ii libldap-2.4-2 2.4.47+dfsg-3 ii libncurses66.1+20181013-2 ii libpopt0 1.16-12 ii libreadline8 8.0-2 ii libtalloc2 2.1.14-2 ii libtdb11.3.16-2+b1 ii libtevent0 0.9.37-1 ii libtinfo6 6.1+20181013-2 ii libwbclient0 2:4.9.11+dfsg-1 ii python 2.7.16-1 ii python-samba 2:4.9.11+dfsg-1 ii python2.7 2.7.16-2 ii samba-common 2:4.9.11+dfsg-1 ii samba-libs 2:4.9.11+dfsg-1 Versions of packages samba-common-bin recommends: ii samba-dsdb-modules 2:4.9.11+dfsg-1 Versions of packages samba-common-bin suggests: pn heimdal-clients -- no debconf information
Bug#931730: libfile-stripnondeterminism-perl: build dependency cycle with libsub-identify-perl
Hi Niko, > the recently added libmonkey-patch-perl dependency in > libfile-stripnondeterminism-perl has unfortunately resulted in a build > dependency cycle […] > I see this new dependency was introduced for normalizing zip archives > (#858431) by changing the Archive::Zip behaviour on the fly. Is this > fixable on the Archive::Zip side? I guess in theory but if I recall the details correctly, I don't /think/ this was going to be a trivial patch to Archive::Zip and my Perl-fu is/was a bit weak. Would pkg-perl apply and upload a patch anyway? Here's a link to my long comment given that I just dug it up for my own benefit: https://salsa.debian.org/reproducible-builds/strip-nondeterminism/commit/f40f555085eeb086bfd4ee1fca1012550790a12d#40676c4ac877689b2966fdabb71ac3686de48aeb_227_224 ... although I would concede that this doesn't speak to the plausibility of the aforementioned patch. > Alternatively, would it be possible to weaken the cycle somehow, for > instance by making this dependency optional and having the packages that > actually need it declare an explicit build dependency ? Would adding a restriction be of use to you? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#931733: rsyslog-doc: please upload 8.1905.0 to unstable
Package: rsyslog-doc Version: 8.1901.0-1 Severity: normal This is just a friendly reminder that you probably want to upload rsyslog-doc 8.1905.0 to unstable so that it matches the rsyslog version there. Thanks for maintaining rsyslog! -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsyslog-doc depends on: ii libjs-sphinxdoc 1.8.4-1 rsyslog-doc recommends no packages. Versions of packages rsyslog-doc suggests: ii chromium [www-browser] 75.0.3770.90-1 ii doc-base 0.10.8 ii elinks [www-browser] 0.13~20190125-3 ii firefox-esr [www-browser] 60.7.2esr-1 ii lynx [www-browser] 2.9.0dev.1-2 ii w3m [www-browser] 0.5.3-37 -- no debconf information
Bug#800968: get all TLS / certificate stuff into a dedicated section or appendix
Please have a look at https://salsa.debian.org/hertzog/debian-handbook/issues/12#note_94829
Bug#931718: [Aptitude-devel] Bug#931718: new packages list forgets about old packages
Control: tag -1 - moreinfo unreproducible + confirmed Hi Matus, Matus UHLAR - fantomas wrote: > On 09.07.19 18:05, Axel Beckert wrote: > > I assume you did not exit aptitude inbetween, right > > I did. What I did was: Ok, exiting aptitude inbetween is what I usually do, too. > 2. change sources.list to point to buster archive. > > # rm sources.list; ln -s sources.list.buster sources.list I don't think that using a symlink instead of editing the file makes a difference. > 3. run aptitude, see only installed packages marked as obsolete: > > --- Obsolete and Locally Created Packages (3978) [...] > 4. run 'u'pdate packages list, see no old packages, but all uninstalled as > new: Gotcha! Doing this in two instead of one step is is the relevant difference and cause for this issue. I usually use "aptitude -u" instead here, which updates the package lists before calculating any view and then there's no problem either. (Also speeds things up as the view needs to be built only once. :-) So as soon as you generate a new view with all packages obsolete, it's clear that afterwards, all other packages are new. I suspect that this is caused by some subtle change in how libapt sees its cache if the sources.list has been modified after the last package list update". Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#931732: downloaded Relase file URLs only given when debugging is active
Package: mini-buildd Version: 1.0.41 Severity: minor Hi, when some archive signing keys have changed, mini-buildd just says "GnuPG authorization failed" without giving any information about the reasons to fail. When I start the daemon with --foreground --verbose --verbose --debug=exception,http,webapp, the log tells me which actual files were downloaded. I then can download those myself (since mini-buildd removes them immediately after failing the check) and manually run gpgv on it, giving the keys that the Release file was signed with. And finally, I can download the missing keys. Is it really necessary that mini-buildd verifies _all_ signatures on Release files? I don't know too much about that, but wouldn't it be enough to have one verified signature for the Release file to be genuine? Any why does it need to be so hard to find out what's going wrong? Wouldn't it be possible to emit something like "release file http://path.to.release.file/debian/dists/stretch/Release signed with untrusted key 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC" without having to hike up the debug level, maybe even in the web interface? Greetings Marc -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.1.16-zgsrv20080 (SMP w/6 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mini-buildd depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.72 ii debootstrap1.0.114 ii devscripts 2.19.5 ii dirmngr2.2.13-2 ii dpkg-dev 1.19.7 ii gnupg 2.2.13-2 ii libjs-jquery 3.3.1~dfsg-3 ii libjs-sphinxdoc1.8.4-1 ii lintian2.15.0 ii lsb-base 10.2019051400 ii mini-buildd-common 1.0.41 ii python 2.7.16-1 ii python-cherrypy3 8.9.1-2 ii python-daemon 2.2.3-1 ii python-mini-buildd 1.0.41 ii python-pyftpdlib 1.5.4-1 ii reprepro 5.3.0-1 ii sbuild 0.78.1-2 ii schroot1.6.10-6+b1 ii sudo 1.8.27-1 Versions of packages mini-buildd recommends: ii python-apt 1.8.4 Versions of packages mini-buildd suggests: pn binfmt-support pn btrfs-progs ii debian-archive-keyring 2019.1 ii haveged 1.9.1-7 ii lvm22.03.02-3 pn qemu-user-static pn ubuntu-keyring -- Configuration Files: /etc/default/mini-buildd changed [not included] /etc/schroot/setup.d/15mini-buildd-workarounds changed [not included] /etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied: '/etc/sudoers.d/mini-buildd-sudoers' -- debconf information excluded
Bug#931636: doesnt bring up virtio interface link with kernel 5.2
On Tue, 2019-07-09 at 19:16 +0200, Michael Biebl wrote: > Am 09.07.19 um 18:44 schrieb Marc Haber: > > https://bugzilla.kernel.org/show_bug.cgi?id=204099 > > https://bugzilla.kernel.org/show_bug.cgi?id=203769 > > > > identify the kernel commit that broke things, > > See also > https://lore.kernel.org/netdev/58ac6ec1-9255-0e51-981a-195c2b1ac...@mellanox.com/T/ > > but people think this is > > actually a systemd issue: > > > > https://github.com/systemd/systemd/issues/12784 > > I'm not an expert on this matter, so I can't say if networkd is buggy > here and if the changed kernel behaviour is ok. Would appreciate Ben's > input on this. I don't really understand the detail of what's changed, but the kernel has a strict policy of not breaking user-space (with rare exceptions being made for security fixes). So even if this is a bug in systemd-networkd, the kernel should end up with a workaround for it. Ben. > > (with patch) > > Can you test those patches to verify that they fix your issue? > > > Will I have to live with a patched systemd again during the buster > > cycle, or would that one warrant a systemd update in buster? > > Depends on whether those patches can be sanely backported to v241 or if > they are too invasive. In the end they have to be acked by the SRM. > > Michael > > -- Ben Hutchings The Peter principle: In a hierarchy, every employee tends to rise to their level of incompetence. signature.asc Description: This is a digitally signed message part
Bug#931671: vokoscreen: I don't see the screen just the cursor
Control: tags 931671 moreinfo unreproducible Em ter, 9 de jul de 2019 às 03:15, Charles BLANC ROLIN escreveu: > Dear Maintainer, > > When I capture, I don't see the screen on the video, only the cursor. Hi Charles, Thanks for your report. I can't reproduce it in vokoscreen 2.5.0-2 over Debian 10. Can you execute '$ rm ~/.config/vokoscreen' and try again? If not working, can you try over a fresh install? I think it is a specific problem in your system, not vokoscreen. Regards, Eriberto
Bug#931718: [Aptitude-devel] Bug#931718: new packages list forgets about old packages
Matus UHLAR - fantomas wrote: I am trying to look which packages are new in buster that were not in stretch. I am using aptitude since it't great tool for browsing packages. until now it was easy: do 'f'orget new packages in aptitude change sources.list to point to new release do 'u'pdate packages list On 09.07.19 18:05, Axel Beckert wrote: I assume you did not exit aptitude inbetween, right I did. What I did was: 0. start with sources.list pointing to stretch archive: lrwxrwxrwx 1 root root20 Jul 9 19:21 sources.list -> sources.list.stretch -rw-r--r-- 1 root root 444 Jul 8 18:27 sources.list.buster -rw-r--r-- 1 root root 450 Nov 1 2018 sources.list.stretch 1. run aptitude to see available packages. Optionally use 'f' to forget new packages. quit aptitude --- Installed Packages (3970) --- Not Installed Packages (74188) --- Obsolete and Locally Created Packages (8) --- Virtual Packages (11400) --- Tasks (235) 2. change sources.list to point to buster archive. # rm sources.list; ln -s sources.list.buster sources.list # ls -ld sources.list* lrwxrwxrwx 1 root root 19 Jul 9 19:23 sources.list -> sources.list.buster -rw-r--r-- 1 root root 444 Jul 8 18:27 sources.list.buster -rw-r--r-- 1 root root 450 Nov 1 2018 sources.list.stretch 3. run aptitude, see only installed packages marked as obsolete: --- Obsolete and Locally Created Packages (3978) --- Virtual Packages (570) --- Tasks (2) 4. run 'u'pdate packages list, see no old packages, but all uninstalled as new: --- Security Updates (1) --- Upgradable Packages (3099) --- New Packages (82647) --- Installed Packages (442) --- Obsolete and Locally Created Packages (436) --- Virtual Packages (28449) --- Tasks (235) but now, when I do this, aptitude seems to forget all info about packages previously available. So every package is listed under "New Packages"? I can't reproduce this. every package that is not installed is shown as new. I just did the following inside an uptodate Stretch pbuilder chroot: * Start "aptitude" [...] * Press Ctrl-Z * Edit /etc/apt/sources.list and change any occurrence of "stretch" to "buster". * Called "fg" to get aptitude into the foreground again. * Pressed "u" in aptitude's TUI. I haven't tried changing sources.list while aptitude is running. Now aptitude shows me this view: --- Actions Undo Package Resolver Search Options Views Help C-T: Menu ?: Help q: Quit u: Update g: Preview/Download/Install/Remove Pkgs aptitude 0.8.7 @ c6 --- Upgradable Packages (111) --- New Packages (13184) --- Installed Packages (2) --- Not Installed Packages (43508) --- Obsolete and Locally Created Packages (15) --- Virtual Packages (14460) I can confirm this works. Just as the "apt update" hack, I consider this a hack too. as I said before, the jessie version of aptitude worked as described even when I quit aptitude in between. I usually change packages list, run 'u'pdate and then browse/upgrade packages. I didn't see the need (nor I had an idea) of changing sources.list while aptitude is running. Maybe you can post even more verbose steps how to reproduce this. Otherwise I have no idea what could be different with your setup to cause such a different behaviour. I hope I have described it thoroughly enough. Thanks for the hint. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Depression is merely anger without enthusiasm.
Bug#893009: Debdiff to fix icu pkgdata crash on Stretch
Hi Laszlo,
Attached is a debdiff to fix the icu pkgdata crash on Stretch. Can this
please be applied in the next point release? It would be really helpful
to have it fixed.
Thanks,
Scottdiff -Nru icu-57.1/debian/changelog icu-57.1/debian/changelog
--- icu-57.1/debian/changelog 2018-03-14 14:28:38.0 -0400
+++ icu-57.1/debian/changelog 2019-05-30 18:53:23.0 -0400
@@ -1,3 +1,9 @@
+icu (57.1-6+deb9u3) stretch; urgency=medium
+
+ * Apply upstream fix for pkgdata crash (Closes: #893009)
+
+ -- Scott Talbert Thu, 30 May 2019 18:53:23 -0400
+
icu (57.1-6+deb9u2) stretch-security; urgency=high
* Backport upstream security fix for CVE-2017-15422: Persian calendar
diff -Nru icu-57.1/debian/patches/0fd799f7eead9e29fa1dd81f8a119b5fbc88ec36.patch icu-57.1/debian/patches/0fd799f7eead9e29fa1dd81f8a119b5fbc88ec36.patch
--- icu-57.1/debian/patches/0fd799f7eead9e29fa1dd81f8a119b5fbc88ec36.patch 1969-12-31 19:00:00.0 -0500
+++ icu-57.1/debian/patches/0fd799f7eead9e29fa1dd81f8a119b5fbc88ec36.patch 2019-05-30 18:53:23.0 -0400
@@ -0,0 +1,66 @@
+From 0fd799f7eead9e29fa1dd81f8a119b5fbc88ec36 Mon Sep 17 00:00:00 2001
+From: Michael Ow
+Date: Fri, 20 May 2016 20:00:53 +
+Subject: [PATCH] ICU-12531 Add null check for closeFunction
+
+X-SVN-Rev: 38757
+---
+ icu4c/source/common/unicode/localpointer.h | 13 +
+ 1 file changed, 5 insertions(+), 8 deletions(-)
+
+diff --git a/icu4c/source/common/unicode/localpointer.h b/icu4c/source/common/unicode/localpointer.h
+index 35e37765c23..c86429359da 100644
+--- icu4c/source/common/unicode/localpointer.h
icu4c/source/common/unicode/localpointer.h
+@@ -485,9 +485,6 @@ class LocalArray : public LocalPointerBase {
+ * like LocalPointer except that this subclass will use the closeFunction
+ * rather than the C++ delete operator.
+ *
+- * Requirement: The closeFunction must tolerate a NULL pointer.
+- * (We could add a NULL check here but it is normally redundant.)
+- *
+ * Usage example:
+ * \code
+ * LocalUCaseMapPointer csm(ucasemap_open(localeID, options, ));
+@@ -512,12 +509,12 @@ class LocalArray : public LocalPointerBase {
+ : LocalPointerBase(src.ptr) { \
+ src.ptr=NULL; \
+ } \
+-~LocalPointerClassName() { closeFunction(ptr); } \
++~LocalPointerClassName() { if (ptr != NULL) { closeFunction(ptr); } } \
+ LocalPointerClassName =(LocalPointerClassName &) U_NOEXCEPT { \
+ return moveFrom(src); \
+ } \
+ LocalPointerClassName (LocalPointerClassName ) U_NOEXCEPT { \
+-closeFunction(ptr); \
++if (ptr != NULL) { closeFunction(ptr); } \
+ LocalPointerBase::ptr=src.ptr; \
+ src.ptr=NULL; \
+ return *this; \
+@@ -531,7 +528,7 @@ class LocalArray : public LocalPointerBase {
+ p1.swap(p2); \
+ } \
+ void adoptInstead(Type *p) { \
+-closeFunction(ptr); \
++if (ptr != NULL) { closeFunction(ptr); } \
+ ptr=p; \
+ } \
+ }
+@@ -544,7 +541,7 @@ class LocalArray : public LocalPointerBase {
+ explicit LocalPointerClassName(Type *p=NULL) : LocalPointerBase(p) {} \
+ ~LocalPointerClassName() { closeFunction(ptr); } \
+ LocalPointerClassName (LocalPointerClassName ) U_NOEXCEPT { \
+-closeFunction(ptr); \
++if (ptr != NULL) { closeFunction(ptr); } \
+ LocalPointerBase::ptr=src.ptr; \
+ src.ptr=NULL; \
+ return *this; \
+@@ -558,7 +555,7 @@ class LocalArray : public LocalPointerBase {
+ p1.swap(p2); \
+ } \
+ void adoptInstead(Type *p) { \
+-closeFunction(ptr); \
++if (ptr != NULL) { closeFunction(ptr); } \
+ ptr=p; \
+ } \
+ }
diff -Nru icu-57.1/debian/patches/series icu-57.1/debian/patches/series
--- icu-57.1/debian/patches/series 2018-03-14 14:28:38.0 -0400
+++ icu-57.1/debian/patches/series 2019-05-30 18:53:23.0 -0400
@@ -12,3 +12,4 @@
CVE-2017-7867_CVE-2017-7868.patch
CVE-2017-14952.patch
CVE-2017-15422.patch
+0fd799f7eead9e29fa1dd81f8a119b5fbc88ec36.patch
Bug#931731: perl: autopkgtest to check for Perl related build cycles in the archive
Package: perl Version: 5.28.1-6 Severity: wishlist Filing #931730, it occurred to me that we could flag perlapi-* related build dependency cycles automatically by having an autopkgtest check in src:perl that looks for them. This would block any such build dependency cycles from reaching testing and highlight the issue for maintainers. While we noticed the build cycle early this time because we've been running Perl 5.30 test rebuilds continuously, with other timing it might take up to a year before anybody notices. The code we currently use for calculating the rebuild order is at https://salsa.debian.org/perl-team/scripts/tree/master/perl-transitions and could probably be simplified to just alert on build dependency cycles. -- Niko Tyni nt...@debian.org
Bug#931636: doesnt bring up virtio interface link with kernel 5.2
Am 09.07.19 um 18:44 schrieb Marc Haber: > https://bugzilla.kernel.org/show_bug.cgi?id=204099 > https://bugzilla.kernel.org/show_bug.cgi?id=203769 > > identify the kernel commit that broke things, See also https://lore.kernel.org/netdev/58ac6ec1-9255-0e51-981a-195c2b1ac...@mellanox.com/T/ but people think this is > actually a systemd issue: > > https://github.com/systemd/systemd/issues/12784 I'm not an expert on this matter, so I can't say if networkd is buggy here and if the changed kernel behaviour is ok. Would appreciate Ben's input on this. > (with patch) Can you test those patches to verify that they fix your issue? > Will I have to live with a patched systemd again during the buster > cycle, or would that one warrant a systemd update in buster? Depends on whether those patches can be sanely backported to v241 or if they are too invasive. In the end they have to be acked by the SRM. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#931728: variety: privacy breach in variety
Control: forwarded -1 https://github.com/varietywalls/variety/issues/198 Hi Damyan, I've copied this upstream, thanks for spotting this. Best, James On 2019-07-09 9:43 a.m., Damyan Ivanov wrote: > Package: variety > Version: 0.7.1-2 > Severity: important > Tags: upstream > > Hi, > > Thank you for packaging variety. It is a very nice program and does its work > smoothly. > > Sadly, it contains code which attempts to load "options" from a remove server > without user's consent. See [1] and [2]. > > [1] > https://sources.debian.org/src/variety/0.7.1-2/variety/VarietyWindow.py/?hl=81#L609 > [2] > https://sources.debian.org/src/variety/0.7.1-2/variety/VarietyWindow.py/?hl=81#L932 > > I'll prepare a merge request that removes the start of the background thread > which does the fetch. Variety works just fine without it. > > > Thanks for considering, > Damyan > > -- System Information: > Debian Release: 10.0 > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), > (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE > Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), > LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages variety depends on: > ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 > ii gir1.2-gexiv2-0.10 0.10.9-1 > ii gir1.2-glib-2.0 1.58.3-2 > ii gir1.2-gtk-3.0 3.24.5-1 > ii gir1.2-notify-0.70.7.7-4 > ii gir1.2-pango-1.0 1.42.4-6 > ii imagemagick 8:6.9.10.23+dfsg-2.1 > ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1 > ii python3 3.7.3-1 > ii python3-bs4 4.7.1-1 > ii python3-cairo1.16.2-1+b1 > ii python3-configobj5.0.6-3 > ii python3-dbus 1.2.8-3 > ii python3-gi 3.30.4-1 > ii python3-gi-cairo 3.30.4-1 > ii python3-lxml 4.3.3-2 > ii python3-pil 5.4.1-2 > ii python3-pkg-resources41.0.1-1 > ii python3-requests 2.21.0-1 > > Versions of packages variety recommends: > ii gir1.2-appindicator3-0.1 0.4.92-7 > ii python3-httplib2 0.11.3-2 > > Versions of packages variety suggests: > pn feh | nitrogen > ii gnome-shell-extension-appindicator 22-1 > > -- no debconf information > signature.asc Description: OpenPGP digital signature
Bug#908964: evince: reports "! SyncTeX Error : No file?" at startup
Hello, this bug is really annoying ! In fact, this issue is a texlive-bin issue: the message comes form libsynctex: https://gitlab.gnome.org/GNOME/evince/commit/678410e81d0c889f4db4e995ca451ed62b8a2eee Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature
Bug#931728: privacy breach in variety
Control: tag -1 patch Merge request adding a quilt patch that removes the start of the background thread that fetches the options: https://salsa.debian.org/jlu-guest/variety/merge_requests/2
Bug#900554: fixed in gcc-8 8.3.0-19
Version: 8.3.0-19 now fixed.
Bug#931730: libfile-stripnondeterminism-perl: build dependency cycle with libsub-identify-perl
Package: libfile-stripnondeterminism-perl Version: 1.2.0-2 Severity: serious User: debian-p...@lists.debian.org Usertags: perl-5.30-transition X-Debbugs-Cc: debhel...@packages.debian.org, debian-p...@lists.debian.org Hi, the recently added libmonkey-patch-perl dependency in libfile-stripnondeterminism-perl has unfortunately resulted in a build dependency cycle: libsub-identify-perl Build-Depends: debhelper debhelper Depends: dh-strip-nondeterminism dh-strip-nondeterminism Depends: libfile-stripnondeterminism-perl libfile-stripnondeterminism-perl Depends: libmonkey-patch-perl libmonkey-patch-perl Depends: libsuper-perl libsuper-perl Depends: libsub-identify-perl This is a problem for Perl major version transitions because libsub-identify-perl is arch:any and needs to be rebuilt against the new Perl, but its build dependencies will now be uninstallable until it is rebuilt. We need to break the cycle. I see this new dependency was introduced for normalizing zip archives (#858431) by changing the Archive::Zip behaviour on the fly. Is this fixable on the Archive::Zip side? Alternatively, would it be possible to weaken the cycle somehow, for instance by making this dependency optional and having the packages that actually need it declare an explicit build dependency ? Thanks for considering, -- Niko Tyni nt...@debian.org
Bug#914511: Please enable the "virtio-rng" driver in "cloud" kernels
Workaround: have the hypervisor expose the 'rdrand' CPU feature to the VM (but this is in the hands of the hypervisor's provider, not the VM user)
Bug#931729: apt-mirror: [SSUse of uninitialized value $lines{"Files:"} in split at /usr/bin/apt-mirror line 829
Package: apt-mirror
Version: 0.5.4-1
Severity: normal
Dear Maintainer,
Begin time: Tue Jul 9 17:56:00 2019
[1]... [0]...
End time: Tue Jul 9 17:56:00 2019
Processing indexes: [SSUse of uninitialized value $lines{"Files:"} in
split at /usr/bin/apt-mirror line 829, line 1.
Use of uninitialized value $lines{"Files:"} in split at
/usr/bin/apt-mirror line 829, line 2.
Use of uninitialized value $lines{"Files:"} in split at
/usr/bin/apt-mirror line 829, line 3.
Use of uninitialized value $lines{"Files:"} in split at
/usr/bin/apt-mirror line 829, line 4.
SSSPP]
0 bytes will be downloaded into archive.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt-mirror depends on:
ii adduser 3.118
ii perl 5.28.1-6
ii wget 1.20.1-1.1
pt-mirror recommends no packages.
apt-mirror suggests no packages.
-- Configuration Files:
/etc/apt/mirror.list changed:
set base_path/repository/debian
set nthreads1
set _tilde 0
deb-amd64 http://ftp.de.debian.org/debian buster main contrib non-free
deb-i386 http://ftp.de.debian.org/debian buster main contrib non-free
deb-src http://ftp.de.debian.org/debian buster main contrib non-free
deb-amd64 http://security.debian.org/debian-security buster/updates main
contrib non-free
deb-i386 http://security.debian.org/debian-security buster/updates main
contrib non-free
deb-src http://security.debian.org/debian-security buster/updates main
contrib non-free
deb-amd64 http://ftp.de.debian.org/debian buster-updates main contrib
non-free
deb-i386 http://ftp.de.debian.org/debian buster-updates main contrib
non-free
deb-src http://ftp.de.debian.org/debian buster-updates main contrib non-free
deb-amd64 http://ftp.de.debian.org/debian stretch main contrib non-free
deb-i386 http://ftp.de.debian.org/debian stretch main contrib non-free
deb-src http://ftp.de.debian.org/debian stretch main contrib non-free
deb-amd64 http://security.debian.org/debian-security stretch/updates
main contrib non-free
deb-i386 http://security.debian.org/debian-security stretch/updates main
contrib non-free
deb-src http://security.debian.org/debian-security stretch/updates main
contrib non-free
deb-amd64 http://ftp.de.debian.org/debian stretch-updates main contrib
non-free
deb-i386 http://ftp.de.debian.org/debian stretch-updates main contrib
non-free
deb-src http://ftp.de.debian.org/debian stretch-updates main contrib
non-free
deb-amd64 http://ftp.de.debian.org/debian stretch-backports main contrib
non-free
deb-i386 http://ftp.de.debian.org/debian stretch-backports main contrib
non-free
deb-src http://ftp.de.debian.org/debian stretch-backports main contrib
non-free
deb-amd64 http://ftp.de.debian.org/debian jessie main contrib non-free
deb-i386 http://ftp.de.debian.org/debian jessie main contrib non-free
deb-src http://ftp.de.debian.org/debian jessie main contrib non-free
deb-amd64 http://security.debian.org/debian-security jessie/updates main
contrib non-free
deb-i386 http://security.debian.org/debian-security jessie/updates main
contrib non-free
deb-src http://security.debian.org/debian-security jessie/updates main
contrib non-free
clean http://ftp.de.debian.org/debian
clean http://security.debian.org/debian
/etc/cron.d/apt-mirror changed:
4 * * * * root/usr/bin/apt-mirror | logger -t "apt-mirror"
-- no debconf information
Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")
On Tue, Jul 9, 2019 at 15:55:02 +0200, Christoph Berg wrote: > Re: David Kalnischkies 2019-07-09 <20190709133107.gvib2ibj6w36j447@crossbow> > > A Release file can declare that it will "soon" change its the value of > > a field to foo and apt clients can notify users about this so > > Fwiw, I think this is seriously overengineered. We can't really test > it, and there's high chances the feature will break (itself or > something else) more than it might fix in practise. > Definitely agreed. I think overall what you're trying to do here (the whole "notify the user they're out of date" thing) does not belong in apt. IMO it belongs in higher level tools that are going to heavily depend on the use case and so there's not really a good generic answer you can come up with at the lowest (apt) level. Cheers, Julien
Bug#931728: variety: privacy breach in variety
Package: variety Version: 0.7.1-2 Severity: important Tags: upstream Hi, Thank you for packaging variety. It is a very nice program and does its work smoothly. Sadly, it contains code which attempts to load "options" from a remove server without user's consent. See [1] and [2]. [1] https://sources.debian.org/src/variety/0.7.1-2/variety/VarietyWindow.py/?hl=81#L609 [2] https://sources.debian.org/src/variety/0.7.1-2/variety/VarietyWindow.py/?hl=81#L932 I'll prepare a merge request that removes the start of the background thread which does the fetch. Variety works just fine without it. Thanks for considering, Damyan -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages variety depends on: ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 ii gir1.2-gexiv2-0.10 0.10.9-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-notify-0.70.7.7-4 ii gir1.2-pango-1.0 1.42.4-6 ii imagemagick 8:6.9.10.23+dfsg-2.1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1 ii python3 3.7.3-1 ii python3-bs4 4.7.1-1 ii python3-cairo1.16.2-1+b1 ii python3-configobj5.0.6-3 ii python3-dbus 1.2.8-3 ii python3-gi 3.30.4-1 ii python3-gi-cairo 3.30.4-1 ii python3-lxml 4.3.3-2 ii python3-pil 5.4.1-2 ii python3-pkg-resources41.0.1-1 ii python3-requests 2.21.0-1 Versions of packages variety recommends: ii gir1.2-appindicator3-0.1 0.4.92-7 ii python3-httplib2 0.11.3-2 Versions of packages variety suggests: pn feh | nitrogen ii gnome-shell-extension-appindicator 22-1 -- no debconf information
Bug#931669: ephoto doesn't even start up
Control: severity -1 normal Hi Michael, I bet there's no rendering engine package installed. You can check with: dpkg -l libevas1-engines*. If so, installing libevas1-engines-x should fix the issue. Currently, ephoto Depends on libevas1, which Recommends libevas1-engines*. That can't be tightened to Depends without creating a circular dependency (libevas1-engines* Depends on libevas1). If apt's config disables recommends, it'll leave you in this situation. I've been trying to avoid making all EFL packages depend on the engines, but maybe it's time to give that up. You're the second person to run into this. Thanks, Ross On Mon, Jul 08, 2019 at 10:57:39PM -0500, Michael Meier wrote: > Package: ephoto > Version: 1.5-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I've just installed ephoto to try it out. I didn't get very far. It doesn't > even start up. If I try to start it up on the console, that's what it tells > me: > > ERR<26189>:ecore_evas lib/elementary/efl_ui_win.c:5300 > _elm_win_finalize_internal() Cannot create window. > ## Copy & Paste the below (until EOF) into a terminal, then hit Enter > > eina_btlog << EOF > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71dcc0c 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71dd901 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71decd3 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b84c6a 0x7f5ce690 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b870c1 0x7f5ce690 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d127a7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8750c 0x7f5ce690 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d127a7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d0f8e4 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8742b 0x7f5ce690 > /usr/bin/ephoto 0x563c68457604 0x563c6843b000 > /usr/bin/ephoto 0x563c68444b7f 0x563c6843b000 > /usr/bin/ephoto 0x563c684448dc 0x563c6843b000 > /lib/x86_64-linux-gnu/libc.so.6 0x7f5ce641e09b 0x7f5ce63fa000 > /usr/bin/ephoto 0x563c6844491a 0x563c6843b000 > EOF > > ERR<26189>:eo lib/eo/eo.c:993 _efl_add_internal_end() Object of class > 'Efl.Ui.Win_Legacy' - Not all of the object constructors have been executed. > ## Copy & Paste the below (until EOF) into a terminal, then hit Enter > > eina_btlog << EOF > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71dcc0c 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71dd901 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71decd3 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d0f9bc 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8742b 0x7f5ce690 > /usr/bin/ephoto 0x563c68457604 0x563c6843b000 > /usr/bin/ephoto 0x563c68444b7f 0x563c6843b000 > /usr/bin/ephoto 0x563c684448dc 0x563c6843b000 > /lib/x86_64-linux-gnu/libc.so.6 0x7f5ce641e09b 0x7f5ce63fa000 > /usr/bin/ephoto 0x563c6844491a 0x563c6843b000 > EOF > > ERR<26189>:evas_main lib/evas/canvas/evas_object_smart.c:718 > _efl_canvas_group_efl_object_destructor() efl_canvas_group_del() was not > called > on this object: 0x40007457 (Efl.Ui.Win_Legacy) > ## Copy & Paste the below (until EOF) into a terminal, then hit Enter > > eina_btlog << EOF > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71dcc0c 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71dd901 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7f5ce71decd3 0x7f5ce71b3000 > /usr/lib/x86_64-linux-gnu/libevas.so.1 0x7f5ce6f9c2c8 0x7f5ce6f02000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b7025c 0x7f5ce690 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6be29a4 0x7f5ce690 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b82d9b 0x7f5ce690 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d0fcec 0x7f5ce6d01000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8742b 0x7f5ce690 > /usr/bin/ephoto 0x563c68457604 0x563c6843b000 > /usr/bin/ephoto 0x563c68444b7f 0x563c6843b000 > /usr/bin/ephoto 0x563c684448dc 0x563c6843b000 > /lib/x86_64-linux-gnu/libc.so.6 0x7f5ce641e09b 0x7f5ce63fa000 > /usr/bin/ephoto 0x563c6844491a 0x563c6843b000 > EOF > > 1 rmm@RMMbook ~ % ERR<26198>:efreet_desktop lib/efreet/efreet_desktop.c:986 > efreet_desktop_generic_fields_parse() no Name or _Name fields in file > '/home/rmm/.local/share/applications/_home_rmm_local_eclipse_jee-2018-12_eclipse_.desktop' > ## Copy & Paste the
Bug#931727: cups-bsd: typo in German error message in lpq command
Package: cups-bsd Version: 2.2.10-6 Severity: minor Dear Maintainer, * What led up to the situation? Invoking the lpq command without installed printer * What was the outcome of this action? message "lpq: Fehler - kein voreingestellted Druckziel verfügbar." This is the German translation of "lpq: Error - no default destination available." * What outcome did you expect instead? message "lpq: Fehler - kein voreingestelltes Druckziel verfügbar." There should be an "s" instead of a "d" at the end of "voreingestelltes" Bye, Thorsten -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cups-bsd depends on: ii cups-client2.2.10-6 ii cups-common2.2.10-6 ii debconf [debconf-2.0] 1.5.72 ii libc6 2.28-10 ii libcups2 2.2.10-6 cups-bsd recommends no packages. Versions of packages cups-bsd suggests: ii cups2.2.10-6 pn inetutils-inetd | inet-superserver ii update-inetd4.50 -- debconf information: cups-bsd/setuplpd: false
Bug#931636: doesnt bring up virtio interface link with kernel 5.2
Am 09.07.19 um 17:48 schrieb Marc Haber: > On Mon, Jul 08, 2019 at 04:41:00PM +0200, Marc Haber wrote: >> I will attach straces of a working and a non-working case once the bug >> number is known. If you need additional information, I will help. > > Here are the straces. .prelink is an invocation without manually setting > the link to up, .postlink is the same after a manual ip link set dev > ens3 up > > Can I somehow tell networkd to be more verbose? systemctl edit systemd-networkd <- [Service] Environment=SYSTEMD_LOG_LEVEL=debug --> systemctl restart systemd-networkd journalctl -u systemd-networkd -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#931636: doesnt bring up virtio interface link with kernel 5.2
https://bugzilla.kernel.org/show_bug.cgi?id=204099 https://bugzilla.kernel.org/show_bug.cgi?id=203769 identify the kernel commit that broke things, but people think this is actually a systemd issue: https://github.com/systemd/systemd/issues/12784 (with patch) Will I have to live with a patched systemd again during the buster cycle, or would that one warrant a systemd update in buster? Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#708976: close 708976
On Tue, 2019-07-09 at 18:10 +0200, Nicolas Boulenguez wrote: > This bug is probably fixed, and the original reporter seems unreachable. My apologies, I must have missed your previous message. I can confirm that on my system a program linked against libffado run as a normal user prints: Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns That seems reasonable to me. I agree with closing the issue. Thanks! Kevin
Bug#931726: xdg-desktop-portal: Intermittent test failure: tests/test-doc-portal.c:695:test_add_named: assertion failed (error == NULL): Can't open .../add-named-1 (g-file-error-quark, 23)
Package: xdg-desktop-portal Version: 1.4.2-1 Severity: important Tags: help xdg-desktop-portal's build-time tests intermittently fail with an error like this: PASS: test-doc-portal 4 /db/create_docs Bail out! xdg-desktop-portal:ERROR:tests/test-doc-portal.c:695:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-UNS23Z/doc/c8891209/add-named-1 (g-file-error-quark, 23) This seems to be quite reproducible on salsa.debian.org CI (maybe 50% of runs, each of which builds x-d-p three times due to reprotest). I can reproduce it on my laptop, but only by building x-d-p 1000 times in a loop. It isn't clear why this happens, and the way the desktop portal gets started by GTestDBus during testing results in its log messages being lost, so it's hard to debug. smcv
Bug#915246: Bug#931536: aptitude update fails to cope with changed release info
On Sun, Jul 07, 2019 at 03:54:04PM +0200, Axel Beckert wrote:
> I hope that Manuel (CCc'ed) can provide a fix which we then can also
> apply to aptitude in Buster in the first minor update which is
> expected in about a month.
It was two years ago, so my memory was spotty, but now that I am looking
into extending the reporting let me add some implementation hints:
(Note that this is against apt/master which has some API changes, but in
that case that means ABI-compat classes where folded into another, so
backports should be rather trivial – adding virtual methods is ABI
breaking, so in buster the class to derive from has the creative name
pkgAcquireStatus2 as it is itself derived from pkgAcquireStatus)
libapt has a pkgAcquireStatus class which gained a new virtual method:
ReleaseInfoChanges – kinda similar to the existing MediaChange. aptitude
subclasses this a few times, just pick the right one I guess.
See apt{,-get}s implementation:
https://salsa.debian.org/apt-team/apt/blob/master/apt-private/acqprogress.cc#L334
I guess you want to work directly with the parameter
std::vector & rather than do the trickery to
make "proper" apt error messages out of it and then print them directly
by wrap-calling the default implementation I did there – aka it is
probably simpler for you.
See the doc for the struct in the method in the header:
https://salsa.debian.org/apt-team/apt/blob/master/apt-pkg/acquire.h#L797
And the code generating the messages you can reuse via the struct:
https://salsa.debian.org/apt-team/apt/blob/master/apt-pkg/acquire-item.cc#L1806
If I could make a wish I would suggest featuring the messages which
don't need confirmation (in apt N: lines) not too prominently – as in
don't make them a popup dialog with an OK button (while the other type
is a popup dialog with yes and no buttons).
I can't speak for aptitude folks and I am not too good with aptitude
code, but if I would be that might be a good bug for tagging +newcomer.
Happy to help in case there are {lib,}apt questions in any case – although
I have insane reply delays currently.
Best regards
David "breaking the world one feature at a time" Kalnischkies
signature.asc
Description: PGP signature
Bug#931722: [Pkg-utopia-maintainers] Bug#931722: Firewalld fails when startig and when reloading rules
Control: reassign -1 iptables Hi Am 09.07.19 um 17:52 schrieb Ramón García: > Package: firewalld > Version: 0.6.3-5 > > When one runs firewall-cmd --reload, and when firewalld starts, the > following error appears > > > 2019-07-09 17:02:15 ERROR: '/usr/sbin/iptables-restore -w -n' failed: > iptables-restore v1.8.2 (nf_tables): > line 4: RULE_REPLACE failed (No such file or directory): rule in chain INPUT > line 4: RULE_REPLACE failed (No such file or directory): rule in chain OUTPUT > > > Fix: > > The cause of the bug is that iptables restore fails when both -F and > -Z are applied in the same table (see > https://bugzilla.redhat.com/show_bug.cgi?id=1664829 ) > > In file /usr/lib/python3/dist-packages/firewall/core/ipXtables.py > remove the flag -Z > > > --- /usr/lib/python3/dist-packages/firewall/core/ipXtables.py.orig > 2019-07-09 17:37:33.915510550 +0200 > +++ /usr/lib/python3/dist-packages/firewall/core/ipXtables.py > 2019-07-09 17:02:09.251902978 +0200 > @@ -551,7 +551,8 @@ > # Flush firewall rules: -F > # Delete firewall chains: -X > # Set counter to zero: -Z > -for flag in [ "-F", "-X", "-Z" ]: > +#for flag in [ "-F", "-X", "-Z" ]: > +for flag in [ "-F", "-X" ]: > rules.append(["-t", table, flag]) > return rules The upstream bug report mentions that this is a iptables issue/regression, most likely caused by the switch to nft. So reassigning accordingly. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#931725: ftp.debian.org: RM: ufraw -- ROM; upstream gone, possible security issues
Package: ftp.debian.org Severity: normal Please remove ufraw. It seems to be abandoned upstream (no release for 4 years, source code in Sourceforge CVS which is now read-only), and may have security issues (libraw, which contains similar code, has had multiple security patches applied, and I've tried to port over some of the patches, but some may have been missed due to divergences in the code. There are also #878732, #878733, #906559, #907467, and #915254 which are potential security issues). Reverse dependencies: - geeqie (recommends ufraw-batch, suggests ufraw) - education-desktop-other (recommends gimp-ufraw) - multimedia-photography (recommends gimp-ufraw) - multimedia-graphics (recommends gimp-ufraw) - imagemagick-6.q16(hdri) (suggests ufraw-batch) I have previously contacted the maintainers of those packages telling them that I was planning on RM-ROM-ing ufraw. Alternatives exist for processing camera RAW files. Thanks
Bug#931723: stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2019b
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've uploaded libdatetime-timezone-perl/1:2.09-1+2019b to stretch,
incorporating the Olson db 2019b release, as usual as a quilt patch
which only touches the Perl modules with the timezone information.
Manually stripped down debdiff attached.
Relevant changes this time are:
- - Palestine: the change in March 2019 was fixed (off-by-one day)
- - Brazil will stay in standard time, i.e. the switch to DST in Autumn
2019 is cancelled.
As there is no urgency this doesn't necessarily have to go through
- -updates IMO, depending on when the next point release is. But of
course I leave that to your discretion.
Thanks in advance,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl0kvMxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYQdxAAwk0dp+2pxA6xs2QUZvOR+pQtE/RFIzhiOTnK1OKzQza5E1efNe0vlAnC
CkI/uN8crMIocipTmXlwgqO1OBCfeBvGhOL9DrkT2XEu3IE4bEQYUCcHul4b+raw
H2hebUgE63JeQ7NxtxIKSG7+ACKi4eu2Jjp/0ua+PlEnzxhnc7VfdyfZ2eqz+MZs
T/X7wsaGeVB7CZTjYWPUfMk9xg0Ds1I3GWI+/YLbhs0U7LT4DvKMqeJi4LC3m5oL
e1PrhWx7e49arBrrXMp5KyQRB5LJlqSHTMiGYsl/WAQT9IxwXv3F+hn8e1ygVnZ+
BnhfRnP1NDr+51QZ5gCN3gvz+O3i3yXBTho53lzbHmt1omiIoGz+oFStf/KQcwWh
YXg6pQDV98l97v6eTVVE1X9w/JQoFYWiV9WiserJ8sKW/v7X0GklAfix574URASI
dIga3EiibiN509CYd/2iiNJR5Gu2z1DucT2JQQT8iPL3JqfQzvpH0wVKE7OHmBxC
ZELD9XmF9mw59dBEFAKNuTjRHNd9HbeSDqJpI5piw7q2VMpmQpRlvb80kW34TuiH
Gd23LL39M4SDCrnJ+OqgtSfEP8NydiSKXUYJ+lqi0PINiyt7OypuYcmuzOCWIh6K
5IL9xVS6/tGZBL8DPqM2J8/E3rZANThL1wI+XK5pEb4nSg+pwR0=
=tQqK
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.09/debian/changelog
libdatetime-timezone-perl-2.09/debian/changelog
--- libdatetime-timezone-perl-2.09/debian/changelog 2019-03-26
18:22:03.0 +0100
+++ libdatetime-timezone-perl-2.09/debian/changelog 2019-07-09
17:45:44.0 +0200
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.09-1+2019b) stretch; urgency=medium
+
+ * Update to Olson database version 2019b.
+This update contains contemporary changes for Brazil and Palestine.
+
+ -- gregor herrmann Tue, 09 Jul 2019 17:45:44 +0200
+
libdatetime-timezone-perl (1:2.09-1+2019a) stretch; urgency=medium
* Update to Olson database version 2019a.
diff -Nru libdatetime-timezone-perl-2.09/debian/patches/olson-2019b
libdatetime-timezone-perl-2.09/debian/patches/olson-2019b
--- libdatetime-timezone-perl-2.09/debian/patches/olson-2019b 1970-01-01
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.09/debian/patches/olson-2019b 2019-07-09
17:45:44.0 +0200
@@ -0,0 +1,13505 @@
+Description: Update to Olson DB 2019b
+Origin: vendor
+Author: gregor herrmann
+Last-Update: 2019-07-07
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+
+ #
+-# Generated from debian/tzdata/africa. Olson data version 2019a
++# Generated from debian/tzdata/africa. Olson data version 2019b
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,7 +43,7 @@
+ ],
+ ];
+
+-sub olson_version {'2019a'}
++sub olson_version {'2019b'}
+
+ sub has_dst_changes {0}
+
+--- a/lib/DateTime/TimeZone/America/Sao_Paulo.pm
b/lib/DateTime/TimeZone/America/Sao_Paulo.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+
+ #
+-# Generated from debian/tzdata/southamerica. Olson data version 2019a
++# Generated from debian/tzdata/southamerica. Olson data version 2019b
+ #
+ # Do not edit this file directly.
+ #
+@@ -853,451 +853,25 @@
+ ],
+ [
+ 63686052000, #utc_start 2019-02-17 02:00:00 (Sun)
+-63708433200, # utc_end 2019-11-03 03:00:00 (Sun)
++DateTime::TimeZone::INFINITY, # utc_end
+ 63686041200, # local_start 2019-02-16 23:00:00 (Sat)
+-63708422400, #local_end 2019-11-03 00:00:00 (Sun)
+--10800,
+-0,
+-'-03',
+-],
+-[
+-63708433200, #utc_start 2019-11-03 03:00:00 (Sun)
+-63717501600, # utc_end 2020-02-16 02:00:00 (Sun)
+-63708426000, # local_start 2019-11-03 01:00:00 (Sun)
+-63717494400, #local_end 2020-02-16 00:00:00 (Sun)
+--7200,
+-1,
+-'-02',
+-],
+-[
+-63717501600, #utc_start 2020-02-16 02:00:00 (Sun)
+-63739882800, # utc_end 2020-11-01 03:00:00 (Sun)
+-63717490800, # local_start 2020-02-15 23:00:00 (Sat)
+-63739872000, #local_end 2020-11-01 00:00:00 (Sun)
+--10800,
+-0,
+-'-03',
+-],
+-[
+-63739882800, #utc_start 2020-11-01 03:00:00 (Sun)
+-63749556000, # utc_end 2021-02-21 02:00:00 (Sun)
+-63739875600, # local_start 2020-11-01 01:00:00 (Sun)
+-63749548800, #local_end 2021-02-21 00:00:00 (Sun)
+--7200,
+-1,
+-'-02',
+-],
+-[
+-63749556000, #utc_start 2021-02-21 02:00:00 (Sun)
+-63771937200, #
Bug#931724: buster-pu: package libdatetime-timezone-perl/1:2.23-1+2019b
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've uploaded libdatetime-timezone-perl/1:2.23-1+2019b to buster,
incorporating the Olson db 2019b release, as usual as a quilt patch
which only touches the Perl modules with the timezone information.
Manually stripped down debdiff attached.
Relevant changes this time are:
- - Palestine: the change in March 2019 was fixed (off-by-one day)
- - Brazil will stay in standard time, i.e. the switch to DST in Autumn
2019 is cancelled.
As there is no urgency this doesn't necessarily have to go through
- -updates IMO, depending on when the next point release is. But of
course I leave that to your discretion.
Thanks in advance,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl0kvM5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYCBBAAtGQESBo2Rn8LHZhtvdcI/ExD8zPWasY0slIeJCLSkThr7L658f6JRkW5
4s2gJYUPIx5nBmOIzHxFZ6hRZc0r7hmRPuTtr9djQlw4DKPEYMKaNjvYtpIpd8B8
wRETgpGkmrqwfiUMuWEvmC/n6+5Isluuk9W771hcXhKxMh0elYZRL68D6WLFtA7H
fMfuhJZEOmSs5RjnwN/+S9v8aFoPvH+DHG9OGyyblYLpEL0XX/cs2V2J9LfLV6qA
WafpO4Dqihq8n11nhTPGylaL5fUKGuE8GosFespm9NxMe/WyQAb36+6HcvJRuUOK
kiMsSNkXjA8gFB2H+n5ifNqN402wYGx3f/NJ7mi8fXzbfD9fR5mBaxdKuIhx8COI
7QtfiWv0FE90ooIpluNLeOkN7v1tGSPgrbfu2ovxLGeNVLWeXUD2P5shnPO9QRyy
biIujH6/GBzVciNNRNsAWaJuC1fvNhxX3w6z8zuWKJDaZK0zC7N9xvLaxBCLdpQx
k+wHXoSEDeNFcshEKl5/QY4xTV+qFHTISFkqMrr2wit8kwngMRiB1nIoQw8THiEL
2zOuxiuh3IWHR/7y6SviNIIoJxRyWPFO0BXuVuzrpxa56vBp5k6GkI2Jkg/LsKuq
3Yw7tMrNa0qDvgWy5SQaCCY87z8kndxsHLvtZTYCwtoMbl76s64=
=SuRo
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.23/debian/changelog
libdatetime-timezone-perl-2.23/debian/changelog
--- libdatetime-timezone-perl-2.23/debian/changelog 2019-03-26
18:05:11.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/changelog 2019-07-09
17:51:51.0 +0200
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.23-1+2019b) buster; urgency=medium
+
+ * Update to Olson database version 2019b.
+This update contains contemporary changes for Brazil and Palestine.
+
+ -- gregor herrmann Tue, 09 Jul 2019 17:51:51 +0200
+
libdatetime-timezone-perl (1:2.23-1+2019a) unstable; urgency=medium
* Update to Olson database version 2019a.
diff -Nru libdatetime-timezone-perl-2.23/debian/patches/olson-2019b
libdatetime-timezone-perl-2.23/debian/patches/olson-2019b
--- libdatetime-timezone-perl-2.23/debian/patches/olson-2019b 1970-01-01
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/patches/olson-2019b 2019-07-09
17:51:51.0 +0200
@@ -0,0 +1,13401 @@
+Description: Update to Olson DB 2019b
+Origin: vendor
+Author: gregor herrmann
+Last-Update: 2019-07-07
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+
+ #
+-# Generated from debian/tzdata/africa. Olson data version 2019a
++# Generated from debian/tzdata/africa. Olson data version 2019b
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,7 +43,7 @@
+ ],
+ ];
+
+-sub olson_version {'2019a'}
++sub olson_version {'2019b'}
+
+ sub has_dst_changes {0}
+
+--- a/lib/DateTime/TimeZone/America/Sao_Paulo.pm
b/lib/DateTime/TimeZone/America/Sao_Paulo.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+
+ #
+-# Generated from debian/tzdata/southamerica. Olson data version 2019a
++# Generated from debian/tzdata/southamerica. Olson data version 2019b
+ #
+ # Do not edit this file directly.
+ #
+@@ -853,451 +853,25 @@
+ ],
+ [
+ 63686052000, #utc_start 2019-02-17 02:00:00 (Sun)
+-63708433200, # utc_end 2019-11-03 03:00:00 (Sun)
++DateTime::TimeZone::INFINITY, # utc_end
+ 63686041200, # local_start 2019-02-16 23:00:00 (Sat)
+-63708422400, #local_end 2019-11-03 00:00:00 (Sun)
+--10800,
+-0,
+-'-03',
+-],
+-[
+-63708433200, #utc_start 2019-11-03 03:00:00 (Sun)
+-63717501600, # utc_end 2020-02-16 02:00:00 (Sun)
+-63708426000, # local_start 2019-11-03 01:00:00 (Sun)
+-63717494400, #local_end 2020-02-16 00:00:00 (Sun)
+--7200,
+-1,
+-'-02',
+-],
+-[
+-63717501600, #utc_start 2020-02-16 02:00:00 (Sun)
+-63739882800, # utc_end 2020-11-01 03:00:00 (Sun)
+-63717490800, # local_start 2020-02-15 23:00:00 (Sat)
+-63739872000, #local_end 2020-11-01 00:00:00 (Sun)
+--10800,
+-0,
+-'-03',
+-],
+-[
+-63739882800, #utc_start 2020-11-01 03:00:00 (Sun)
+-63749556000, # utc_end 2021-02-21 02:00:00 (Sun)
+-63739875600, # local_start 2020-11-01 01:00:00 (Sun)
+-63749548800, #local_end 2021-02-21 00:00:00 (Sun)
+--7200,
+-1,
+-'-02',
+-],
+-[
+-63749556000, #utc_start 2021-02-21 02:00:00 (Sun)
+-63771937200, #
Bug#931718: [Aptitude-devel] Bug#931718: new packages list forgets about old packages
Control: tag -1 + moreinfo unreproducible Hi Matus, thanks for the bug report. Matus UHLAR - fantomas wrote: > I am trying to look which packages are new in buster that were not in > stretch. I am using aptitude since it't great tool for browsing packages. > > until now it was easy: > > do 'f'orget new packages in aptitude > change sources.list to point to new release > do 'u'pdate packages list I assume you did not exit aptitude inbetween, right > but now, when I do this, aptitude seems to forget all info about packages > previously available. So every package is listed under "New Packages"? I can't reproduce this. I just did the following inside an uptodate Stretch pbuilder chroot: * Start "aptitude" It shows this view: --- Actions Undo Package Resolver Search Options Views Help C-T: Menu ?: Help q: Quit u: Update g: Preview/Download/Install/Remove Pkgs aptitude 0.8.7 @ c6 --- Installed Packages (128) --- Not Installed Packages (50663) --- Virtual Packages (5897) These packages are currently installed on your computer. ▒ ▒ This group contains 128 packages. ▒ --- * Press Ctrl-Z * Edit /etc/apt/sources.list and change any occurrence of "stretch" to "buster". * Called "fg" to get aptitude into the foreground again. * Pressed "u" in aptitude's TUI. Now aptitude shows me this view: --- Actions Undo Package Resolver Search Options Views Help C-T: Menu ?: Help q: Quit u: Update g: Preview/Download/Install/Remove Pkgs aptitude 0.8.7 @ c6 --- Upgradable Packages (111) --- New Packages (13184) --- Installed Packages (2) --- Not Installed Packages (43508) --- Obsolete and Locally Created Packages (15) --- Virtual Packages (14460) A newer version of these packages is available. ▒ ▒ This group contains 111 packages. ▒ --- Which is more or less what I would expect: * 13184 new binary packages (You should get the same number on amd64 unless you also have contrib/non-free or third-party repos enabled.) * 111 of the 128 installed packages of the minimal chroot are updatable. * 2 are unchanged between stretch and buster. * 15 are no more in buster. Maybe you can post even more verbose steps how to reproduce this. Otherwise I have no idea what could be different with your setup to cause such a different behaviour. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#929506: gbrowse FTBFS: tests fail
Hi Carnë, On Tue, Jul 09, 2019 at 04:53:31PM +0100, Carnë Draug wrote: > On Tue, 9 Jul 2019 at 10:33, Andreas Tille wrote: > > > > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gbrowse_2.56+dfsg-4.rbuild.log.gz > > I have checked the output from that link and it's getting a lot of > "Can't locate Bio/DB/SeqFeature/Store.pm in @INC (you may need to > install the Bio::DB::SeqFeature::Store module)" and another for > Bio::DB::GFF. > > These module used to be part of the BioPerl distribution but has been > moved out to their own distribution, both of which have already been > released. > > Their distributions are: > > Bio-DB-SeqFeature [1,2] > Bio-DB-GFF [3,4] > > [1] https://github.com/bioperl/Bio-DB-SeqFeature/ > [2] https://metacpan.org/release/Bio-DB-SeqFeature > [3] https://github.com/bioperl/Bio-DB-GFF/ > [4] https://metacpan.org/release/Bio-DB-GFF Thanks for analysing this issue. Do you volunteer to create these packages? Kind regards Andreas. -- http://fam-tille.de
Bug#929506: gbrowse FTBFS: tests fail
On Tue, 9 Jul 2019 at 10:33, Andreas Tille wrote: > > Hi Carnė, > > I have not checked but I could imagine that this issue is somehow > connected to the the new upstream version of bioperl. Since you > intended to to restructure the bioperl packages I think this is a good > point in time. Since you are way more involved in bioperl than I I'd be > more than happy if you do this fully according to your own opinion. > Please let me know if you need any help. > [...] > This is also observed by reproducible builds using pbuilder: > > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gbrowse_2.56+dfsg-4.rbuild.log.gz I have checked the output from that link and it's getting a lot of "Can't locate Bio/DB/SeqFeature/Store.pm in @INC (you may need to install the Bio::DB::SeqFeature::Store module)" and another for Bio::DB::GFF. These module used to be part of the BioPerl distribution but has been moved out to their own distribution, both of which have already been released. Their distributions are: Bio-DB-SeqFeature [1,2] Bio-DB-GFF [3,4] [1] https://github.com/bioperl/Bio-DB-SeqFeature/ [2] https://metacpan.org/release/Bio-DB-SeqFeature [3] https://github.com/bioperl/Bio-DB-GFF/ [4] https://metacpan.org/release/Bio-DB-GFF
Bug#931722: Firewalld fails when startig and when reloading rules
Package: firewalld Version: 0.6.3-5 When one runs firewall-cmd --reload, and when firewalld starts, the following error appears 2019-07-09 17:02:15 ERROR: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.8.2 (nf_tables): line 4: RULE_REPLACE failed (No such file or directory): rule in chain INPUT line 4: RULE_REPLACE failed (No such file or directory): rule in chain OUTPUT Fix: The cause of the bug is that iptables restore fails when both -F and -Z are applied in the same table (see https://bugzilla.redhat.com/show_bug.cgi?id=1664829 ) In file /usr/lib/python3/dist-packages/firewall/core/ipXtables.py remove the flag -Z --- /usr/lib/python3/dist-packages/firewall/core/ipXtables.py.orig 2019-07-09 17:37:33.915510550 +0200 +++ /usr/lib/python3/dist-packages/firewall/core/ipXtables.py 2019-07-09 17:02:09.251902978 +0200 @@ -551,7 +551,8 @@ # Flush firewall rules: -F # Delete firewall chains: -X # Set counter to zero: -Z -for flag in [ "-F", "-X", "-Z" ]: +#for flag in [ "-F", "-X", "-Z" ]: +for flag in [ "-F", "-X" ]: rules.append(["-t", table, flag]) return rules
Bug#931659: transition: rm python2
On 09.07.19 00:31, Scott Kitterman wrote: > Ben file: > > title = "python-defaults"; > is_affected = .depends ~ > /python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg/ > | .depends ~ "''"; > is_good = .depends ~ "''"; > is_bad = .depends ~ > /python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg/; this is missing all cases where python2 is only used for the build, and doesn't end up in any python/python2 dependency. So realistically, check for python and python2 in B-D's as well.
Bug#931715: please update to 0.6.4
Sean Whitton wrote: > Looks like it's not in Stackage LTS yet. I see you wrote the patch. > Would it be enough to backport it to what's currently in sid? Patch backport attached. -- see shy jo diff -ur haskell-http-client-0.5.13.1.orig/Network/HTTP/Client/Headers.hs haskell-http-client-0.5.13.1/Network/HTTP/Client/Headers.hs --- haskell-http-client-0.5.13.1.orig/Network/HTTP/Client/Headers.hs 2018-04-09 09:40:11.0 -0400 +++ haskell-http-client-0.5.13.1/Network/HTTP/Client/Headers.hs 2019-07-09 11:37:17.499256981 -0400 @@ -84,13 +84,20 @@ if S.null line then return $ front [] else do -header <- parseHeader line -parseHeaders (count + 1) $ front . (header:) +mheader <- parseHeader line +case mheader of +Just header -> +parseHeaders (count + 1) $ front . (header:) +Nothing -> +-- Unparseable header line; rather than throwing +-- an exception, ignore it for robustness. +parseHeaders count front -parseHeader :: S.ByteString -> IO Header +parseHeader :: S.ByteString -> IO (Maybe Header) parseHeader bs = do let (key, bs2) = S.break (== charColon) bs -when (S.null bs2) $ throwHttp $ InvalidHeader bs -return (CI.mk $! strip key, strip $! S.drop 1 bs2) +if S.null bs2 +then return Nothing +else return (Just (CI.mk $! strip key, strip $! S.drop 1 bs2)) strip = S.dropWhile (== charSpace) . fst . S.spanEnd (== charSpace) signature.asc Description: PGP signature
Bug#931721: firewalld fails at startup when it runs iptables-restore/ip6tables-restore
Package: firawalld Version: 0.6.3-5 When one runs firewall-cmd --reload, and when firewalld starts, the following error appears 2019-07-09 17:02:15 ERROR: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.8.2 (nf_tables): line 4: RULE_REPLACE failed (No such file or directory): rule in chain INPUT line 4: RULE_REPLACE failed (No such file or directory): rule in chain OUTPUT Fix: The cause of the bug is that iptables restore fails when both -F and -Z are applied in the same table (see https://bugzilla.redhat.com/show_bug.cgi?id=1664829 ) In file /usr/lib/python3/dist-packages/firewall/core/ipXtables.py
Bug#931720: firewalld: after run any firewall rule changing command, and then reload it, error messages are displayed.
Package: firewalld Version: 0.6.3-5 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After add new rules to firewalld, and then reload it, error messages are displayed and firewalld mulfunction. * What exactly did you do (or not do) that was effective (or ineffective)? I run the following commands in super user mode: firewall-cmd --zone=public --permanent --add-service=ssh firewall-cmd --zone=public --permanent --add-service=http firewall-cmd --zone=public --permanent --add-service=https firewall-cmd --zone=public --permanent --add-icmp-block=echo-request firewall-cmd --reload * What was the outcome of this action? Error messages show up as follows: Error: COMMAND_FAILED: '/usr/sbin/ip6tables-restore -w -n' failed: ip6tables-restore v1.8.2 (nf_tables): line 4: RULE_REPLACE failed (No such file or directory): rule in chain OUTPUT After that, I run command 'firewall-cmd --list-all', error message 'Error: INVALID_ZONE' is seem. * What outcome did you expect instead? New firewall rules can be added, and firewalld functions normally. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8), LANGUAGE=en_HK:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firewalld depends on: ii dbus 1.12.16-1 ii gir1.2-glib-2.0 1.58.3-2 ii init-system-helpers 1.56+nmu1 ii iptables 1.8.2-4 ii policykit-1 0.105-25 ii python3 3.7.3-1 ii python3-dbus 1.2.8-3 ii python3-gi 3.30.4-1 ii python3-slip-dbus0.6.5-2 Versions of packages firewalld recommends: ii ipset 6.38-1.2 firewalld suggests no packages. -- no debconf information
Bug#931710: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass
On Tue, 09 Jul 2019 at 14:47:04 +, Luke Flinders wrote: > cat /etc/crypttab > sda5_crypt UUID=ec7880bc-c758-4681-8e94-b21f13752b48 none luks,discard Is there an entry for ‘sda5_crypt’ in the initramfs' ‘/cryptroot/crypttab’? And, is ‘/scripts/local-top/cryptroot’ running by the time you start `cryptroot-unlock`? I don't see anything relevant in our diff between 2:2.0.6-1 and 2:2.1.0-5. Could you please start the script with `sh -x cryptroot-unlock` (also in the initramfs shell) and share the trace? -- Guilhem. signature.asc Description: PGP signature
Bug#931719: 40-systemd: line 11: 1: unbound variable when sourcing /lib/lsb/init-functions with $1 unset
Package: systemd
Version: 241-5
Severity: normal
Tags: patch
Dear Maintainer,
After upgrading to Debian 10 we noticed a slightly different behaviour
in /lib/lsb/init-functions.d/40-systemd which caused one of our scripts
to break and which also causes some /etc/init.d files like /etc/init.d/mysql
to no longer to display their help text when calling them without a parameter.
The root cause are accesses to the $1 and $2 variables without checking
if they are defined beforehand. When running code using "set -u", this
causes the above mentioned error.
I've outlined this very simple fix which bypasses all further tests if
$1 and so on are undefined.
$ diff -C 9 40-systemd.orig 40-systemd
*** 40-systemd.orig 2019-05-24 22:58:59.0 +0200
--- 40-systemd 2019-07-09 16:40:39.642678140 +0200
***
*** 1,18
--- 1,21
# -*-Shell-script-*-
# /lib/lsb/init-functions
_use_systemctl=0
if [ -d /run/systemd/system ]; then
if [ -n "${__init_d_script_name:-}" ]; then # scripts run
with new init-d-script
executable="$__init_d_script_name"
argument="$1"
+ elif [ $# -eq 0 ] ; then
+ executable="$0"
+ argument=""
elif [ "${0##*/}" = "init-d-script" ] ||
[ "${0##*/}" = "${1##*/}" ]; then # scripts run with
old init-d-script
executable="$1"
argument="$2"
else # plain old scripts
executable="$0"
argument="$1"
fi
-- Package-specific info:
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-4
ii libapparmor1 2.13.2-10
ii libaudit11:2.8.4-3
ii libblkid12.33.1-0.1
ii libc62.28-10
ii libcap2 1:2.25-2
ii libcryptsetup12 2:2.1.0-5
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.7-4
ii libgpg-error01.35-1
ii libidn11 1.33-2.2
ii libip4tc01.8.2-4
ii libkmod2 26-1
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.4-1
ii libmount12.33.1-0.1
ii libpam0g 1.3.1-5
ii libseccomp2 2.3.3-4
ii libselinux1 2.8-1+b1
ii libsystemd0 241-5
ii mount2.33.1-0.1
ii util-linux 2.33.1-0.1
Versions of packages systemd recommends:
ii dbus1.12.16-1
ii libpam-systemd 241-5
Versions of packages systemd suggests:
ii policykit-10.105-25
pn systemd-container
Versions of packages systemd is related to:
pn dracut
ii initramfs-tools 0.133
ii udev 241-5
-- no debconf information
Bug#931711: [notificati...@github.com: Re: [mad-lab/transit] Please port to Python3 (#20)]
Control: tags -1 pending - Forwarded message from ioerger - Date: Tue, 09 Jul 2019 06:43:05 -0700 From: ioerger To: mad-lab/transit Cc: Andreas Tille , Author Subject: Re: [mad-lab/transit] Please port to Python3 (#20) Transit has already been ported to Python3 internally, and will be available in Transit release 3.0, which is imminent.
Bug#931718: new packages list forgets about old packages
Package: aptitude Version: 0.8.7-1 I am trying to look which packages are new in buster that were not in stretch. I am using aptitude since it't great tool for browsing packages. until now it was easy: do 'f'orget new packages in aptitude change sources.list to point to new release do 'u'pdate packages list ... voila but now, when I do this, aptitude seems to forget all info about packages previously available. This was not an issue in jessie (0.6.11-1+b1) and previous versions. when I have tried to run "apt update" after changing sources.list, and run aptitude, the expected (former) behaviour was encountered. (even when I furtger 'u'pdated in aptitude). the pkgstates contained differencies between releases: # diff -u /tmp/pkgstates.old /tmp/pkgstates.apt-update @@ -47,13 +40,6 @@ Dselect-State: 0 Remove-Reason: 0 -Package: libcollada2gltfconvert-dev -Architecture: i386 -Unseen: no -State: 3 -Dselect-State: 0 -Remove-Reason: 0 - Package: python3-doc8 Architecture: i386 Unseen: no @@ -117,6 +103,13 @@ Dselect-State: 0 Remove-Reason: 0 +Package: python-libthumbor +Architecture: i386 +Unseen: yes +State: 3 +Dselect-State: 0 +Remove-Reason: 0 + Package: globus-xioperf Architecture: i386 Unseen: no When I rolled back and did update inside of aptitude, all packages in pkgstates were changed to: --- /tmp/pkgstates.apt-update 2019-07-09 16:31:37.079852823 +0200 +++ /var/lib/aptitude/pkgstates 2019-07-09 16:37:57.671178453 +0200 @@ -1,104 +1,104 @@ Package: libdatrie-doc Architecture: i386 -Unseen: no +Unseen: yes State: 3 Dselect-State: 0 Remove-Reason: 0 Package: libfstrcmp0-dbg Architecture: i386 -Unseen: no +Unseen: yes State: 3 Dselect-State: 0 Remove-Reason: 0 etc. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. "One World. One Web. One Program." - Microsoft promotional advertisement "Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler
Bug#931576: RFS: blackbox-themes/0.6
On Sun, 7 Jul 2019 21:46:16 +0200 Adam Borowski wrote: > On Sun, Jul 07, 2019 at 10:38:07PM +0300, Juhani Numminen wrote: > > I am looking for a sponsor for my package "blackbox-themes" which > > I have orphaned (#931569). I don't have much interest in blackbox or its > > themes > > these days. > > > > Additionally, I took the chance to convert the old-style packaging to dh. > > You're not following our standards! The custom is to leave the package > neglected for a decade without saying a word -- putting in effort to do such > overhaul at the very end is inappropriate. :þ Ah, then I must thank you for letting such a standards violation slip ;) Juhani
Bug#931710: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass
Hi Guilhem, Yes it is being run from an initramfs shell, sorry for leaving that out. Requested information is as follows; cat /etc/crypttab sda5_crypt UUID=ec7880bc-c758-4681-8e94-b21f13752b48 none luks,discard cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/kali--vg-root / ext4errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=5264b2eb-3b0c-4b82-896b-c44b1dd5bae6 /boot ext2defaults 0 2 /dev/mapper/kali--vg-swap_1 noneswapsw 0 0 Kind regards, Luke Flinders -Original Message- From: Guilhem Moulin Sent: 09 July 2019 15:39 To: Luke Flinders ; 931...@bugs.debian.org Subject: Re: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass Control: reassign -1 cryptsetup-initramfs 2:2.1.0 Control: tag -1 moreinfo Hi, On Tue, 09 Jul 2019 at 13:00:52 +, Luke Flinders wrote: > Error message is; > Error: Timeout reached while waiting for askpass > > Command run is; > cryptroot-unlock Are you running `cryptroot-unlock` from an initramfs shell? Could you please share your partitioning information (/etc/crypttab and /etc/fstab)? The message suggests that there is no cryptsetup (askpass) prompt running at this time, so I'd like to see how the device stack unfolds at initramfs stage. > The contents of this email message and any attachments are intended > solely for the addressee(s) and may contain confidential and/or > privileged information and may be legally protected from disclosure. Just for the record, this bug tracker is public :-) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931710 https://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/2019-July/008324.html Cheers, -- Guilhem.
Bug#931565: RFS: pentobi/17.1-1
On Sun, 7 Jul 2019 21:41:32 +0200 Adam Borowski wrote: > Looks good, uploaded! Thank you! > One nit: > . > [0707/213841.195824:WARNING:stack_trace_posix.cc(699)] Failed to open file: > /home/kilobyte/#5424019 (deleted) > Error: No such file or directory > ` > but with no apparent problems, just a message. Just a cosmetic problem – until proven otherwise :) I might be able to investigate it further at a later date. Juhani
Bug#931714: node-request-promise: autopkgtest fails
Control: severity -1 grave Le 09/07/2019 à 16:16, Xavier Guimard a écrit : > Package: node-request-promise > Version: 4.2.4-1 > Severity: important > > Both autopkgtest tests fail with the following message: > > 8< > autopkgtest [16:10:50]: test require: [--- > > ### > ### The "request" library is not installed automatically anymore. > ### But is a dependency of "request-promise". > ### Please install it with: > ### npm install request --save > ### > > /usr/share/nodejs/request-promise/lib/rp.js:23 > throw err; > ^ > > Error: Cannot find module 'request' > at Function.Module._resolveFilename > (internal/modules/cjs/loader.js:581:15) > at Function.Module._load (internal/modules/cjs/loader.js:507:25) > at Module.require (internal/modules/cjs/loader.js:637:17) > at require (internal/modules/cjs/helpers.js:22:18) > at /usr/share/nodejs/request-promise/lib/rp.js:11:16 > at module.exports (/usr/lib/nodejs/stealthy-require/lib/index.js:62:23) > at Object. (/usr/share/nodejs/request-promise/lib/rp.js:10:19) > at Module._compile (internal/modules/cjs/loader.js:689:30) > at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10) > at Module.load (internal/modules/cjs/loader.js:599:32) > at tryModuleLoad (internal/modules/cjs/loader.js:538:12) > at Function.Module._load (internal/modules/cjs/loader.js:530:3) > at Module.require (internal/modules/cjs/loader.js:637:17) > at require (internal/modules/cjs/helpers.js:22:18) > at [eval]:1:1 > at Script.runInThisContext (vm.js:96:20) > at Object.runInThisContext (vm.js:303:38) > at Object. ([eval]-wrapper:6:22) > at Module._compile (internal/modules/cjs/loader.js:689:30) > at evalScript (internal/bootstrap/node.js:587:27) > at startup (internal/bootstrap/node.js:265:9) > at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3) > >8 > > Please fix it Upgrading severity since package seems unusable (fails with a simple "require")
Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer
Package: amarok Version: 2.9.0-1+b1 Followup-For: Bug #921194 Dear maintainer. The amarok builds just fine as per the steps outlined in https://wiki.debian.org/BuildingTutorial#Rebuild_without_changes No source changes are necessary. I guess the only thing needed is the actual libmariadb* dep version bump. It would be *really* great to have amarok back :) Roman.
