Bug#904018: gcc-8: FTBFS on x32: hangs in the testsuite (zombie child)
I think the problem may be that code to use libcurl is compiled into libphobos (std.net.curl) and tests for it are executed which do not correctly handle its absence. Neither libgphobos-8-dev nor libgphobos76 appear to depend on, recommend or suggest libcurl4 and it does not appear in the build logs; 'curl' is suggested but not installed. In the absence of correct libcurl libraries, these tests were known to time out: https://issues.dlang.org/show_bug.cgi?id=18519 In doing so there might be a deadlock. The issue was raised initially on FreeBSD and Windows, but Iain Buclaw says there that it occurs on "Linux64 with MODEL=32" (although this may be a lack of regular x86 32-bit libraries on a amd64 system). This was meant to be fixed by a patch in March 2018, however it appears to have been ineffective: https://github.com/dlang/phobos/commit/35e9807bbec392658ecdc8b4ed93d1f6c02f2845 Iain committed further patches to resolve this in January (now in dmd v2.085.1): https://github.com/dlang/phobos/commit/1dcb92aade1c82c356e964c1ca15c51e7de8bf76 https://github.com/dlang/phobos/commit/d36b28c3fc90919a2a3a98249ad2d65393e28507 I'm not sure if this would go automatically into a 8.4, or maybe it can be cherry-picked? I've no knowledge of D and other patches here (or elsewhere?) may also be relevant: https://github.com/dlang/phobos/commit/c6bd6743254584e292f82cbcbac644d1705d14b0 https://github.com/dlang/phobos/commit/8d51519f3f11a5f9b538cd690521b61e9fbbf5df https://github.com/dlang/phobos/commits/master/std/net/curl.d in general Just noticed this failure popping up regularly in the x32 build logs and thought I'd have a look, since I'm hoping to build a home server on it shortly. Best regards, -- Laurence "GreenReaper" Parry http://www.greenreaper.co.uk/
Bug#897146: androgui: traceback and crash (SIGABRT) with no file open and menu item View -> Resources
Control: tags -1 + fixed-upstream On Sun, 29 Apr 2018 10:44:03 +0800 Paul Wise wrote: > When I start androgui without opening any files and immediate choose > the View -> Resources menu item, it gives a Python traceback and crash: I note that the two crashes have apparently been fixed upstream: https://github.com/androguard/androguard/issues/484 https://github.com/androguard/androguard/releases/tag/v3.3.4 https://github.com/androguard/androguard/releases/tag/v3.3.5 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#926979: munin: autopkgtest compatibility for systemd-only derivatives
Package: munin Version: 2.0.47-1 Severity: minor Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Dear maintainers, In Ubuntu, after merging munin 2.04.7-1, autopkgtests were failing because they depended on being able to install the sysvinit-core package, which Ubuntu does not include: [...] autopkgtest [20:35:14]: test master-sysvinit-cron: [--- Installing sysvinit-core... Reading package lists... Building dependency tree... Reading state information... Package sysvinit-core is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: systemd-sysv autopkgtest [20:35:15]: test master-sysvinit-cron: ---] master-sysvinit-cron FAIL non-zero exit status 100 [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/m/munin/20190412_204534_b9ff8@/log.gz) It seems to me this could be sidestepped by having the test declare a dependency on sysvinit-core instead of installing it as part of the test, and also using Restrictions: skip-not-installable. This at least makes the tests pass in Ubuntu, but you may or may not want the autopkgtests to be skipped if the test deps become transiently uninstallable in Debian. Regards, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru munin-2.0.47/debian/tests/control munin-2.0.47/debian/tests/control --- munin-2.0.47/debian/tests/control 2019-04-12 21:30:45.0 -0700 +++ munin-2.0.47/debian/tests/control 2019-04-12 21:42:55.0 -0700 @@ -21,8 +21,8 @@ # sysvinit-core Tests: master-sysvinit-cron, master-sysvinit-cgi -Depends: munin, munin-node, daemontools, apache2, curl, file, libcgi-fast-perl, sharness -Restrictions: needs-root, breaks-testbed, isolation-machine, needs-reboot +Depends: munin, munin-node, daemontools, apache2, curl, file, libcgi-fast-perl, sharness, sysvinit-core +Restrictions: needs-root, breaks-testbed, isolation-machine, needs-reboot, skip-not-installable # Tests for munin-node: @@ -40,8 +40,8 @@ # sysvinit-core Tests: node-sysvinit -Depends: munin-node, netcat-openbsd, net-tools, sharness -Restrictions: needs-root, breaks-testbed, isolation-machine, needs-reboot +Depends: munin-node, netcat-openbsd, net-tools, sharness, sysvinit-core +Restrictions: needs-root, breaks-testbed, isolation-machine, needs-reboot, skip-not-installable # verify that all binary packages can be installed at the same time (without conflicts)
Bug#926978: ITP: biobambam2 -- tools for early stage alignment file processing
Package: wnpp Severity: wishlist Subject: ITP: biobambam2 -- tools for early stage alignment file processing Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: biobambam2 Version : 2.0.95 Upstream Author : German Tischler * URL : https://gitlab.com/german.tischler/biobambam2 * License : GPL-3+ Programming Lang: C++ Description : tools for early stage alignment file processing This package contains some tools for processing BAM files including . bamsormadup: parallel sorting and duplicate marking bamcollate2: reads BAM and writes BAM reordered such that alignment or collated by query name bammarkduplicates: reads BAM and writes BAM with duplicate alignments marked using the BAM flags field bammaskflags: reads BAM and writes BAM while masking (removing) bits from the flags column bamrecompress: reads BAM and writes BAM with a defined compression setting. This tool is capable of multi-threading. bamsort: reads BAM and writes BAM resorted by coordinates or query name bamtofastq:reads BAM and writes FastQ; output can be collated or uncollated by query name Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/biobambam2
Bug#888988: Bug hits me often (or make base64 configurable)
Hello Nis, On Tue, Feb 12, 2019 at 11:46:59PM +0100, Nis Martensen wrote: > Your mail should probably not have gone to debian bug #853915 > (python-debianbts retrieving undecoded text), but to #888988 (reportbug > sending in base64). Sorry, taking the right bug in CC now. > Anyway some comments below. > > On 9 Jan 2019 Helge Kreutzmann wrote: > > I'm often hit by this bug, as I have several Debian instances where no > > e-mail > > conection is available. So I save the report of reportbug, transfer > > the file to another machine and then I need to massage the e-mail to > > get it accepted (currently removing all but the base64 part, running > > "base64 -d " on the remaining part and inserting the output back into > > the original mail. I'm probably going to skript it soon. > > > > So it would be very helpful for me if either temporarily stored > > e-mails of reportbug are not stored in base64 format at all or at > > least configurable, so that I can always see the contents after "mutt > > -H reportbug …". > > In my tests mutt was able to deal with these base64-encoded files just > fine, no manual conversion was needed. I've tested with mutt both in > stable and unstable. You seem to describe that it does not work for you? Yes. I was an older mutt, but I can do tests with a more recent one, maybe this bug is fixed. > One (other) way to automate the conversion from base64 to 8bit is the > "reformime" tool from the maildrop package: > $ reformime -u < /tmp/reportbug- > should output the text in readable form. Yes, thanks for the pointer, this works nicely. > > Since all e-mails sent by mutt at least arrived in the BTS without > > problems I do not see the point of encoding e-mails in base64 at all. > > (But there may be use cases, so makeing this configurable would > > probably be the best option). > > reportbug is using python's email package for setting up its messages. > reportbug does not actually want to deal with such encoding issues, but > wants to rely on the email package for making the proper decisions. > Making this configurable is not a desirable step from reportbug's > perspective, as it would make the code more complex for no significant gain. I see. > > Having the BTS accept the base64 encoded e-mails is suboptimal, as I > > can no longer read the e-mails in mutt and sometimes I notice things > > just before sending, prompting me to update the report in mutt. > > I suspect that the BTS may already be able to deal with base64-encoded > mail bodies, because not everybody who sends control messages to the BTS > uses a mailer where they can control the content transfer encoding. But > I haven't checked. I'm planning to run a few tests to check this soon. Thanks. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#926977: munin: Missing test dep on net-tools
Package: munin Version: 2.0.47-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Dear maintainers, After merging munin 2.0.47-1 into Ubuntu, the node-systemd autopkgtest was failing on armhf because of a mismatch in the list of plugins being exposed: [...] test_cmp expected_plugins all_without_network_interfaces --- expected_plugins2019-04-12 22:53:26.048623301 + +++ all_without_network_interfaces 2019-04-12 22:53:26.040623244 + @@ -8,7 +8,6 @@ irqstats load memory -netstat open_files open_inodes proc_pri not ok 1 - request list of configured plugins [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/armhf/m/munin/20190412_225957_3819c@/log.gz) The reason for this is that the netstat plugin checks whether the netstat command is present at registration time, and the netstat command is not guaranteed to be installed on the testbed because nothing depends on net-tools. The attached patch fixes the test failure by adding a test dependency on net-tools. Perhaps it would also make sense for munin-plugins-core to Recommend: net-tools, I don't know. Please consider applying this patch in Debian. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru munin-2.0.47/debian/tests/control munin-2.0.47/debian/tests/control --- munin-2.0.47/debian/tests/control 2019-02-28 06:50:43.0 -0800 +++ munin-2.0.47/debian/tests/control 2019-04-12 21:30:45.0 -0700 @@ -35,12 +35,12 @@ # systemd Tests: node-systemd -Depends: munin-node, netcat-openbsd, sharness +Depends: munin-node, netcat-openbsd, net-tools, sharness Restrictions: needs-root, breaks-testbed, isolation-container # sysvinit-core Tests: node-sysvinit -Depends: munin-node, netcat-openbsd, sharness +Depends: munin-node, netcat-openbsd, net-tools, sharness Restrictions: needs-root, breaks-testbed, isolation-machine, needs-reboot
Bug#926975: Additinal reports.
Dear maintainers, This old (2010) TOSHIBA laptop, upgraded from Stretch, seems OK. * Sound is fine. * logcheck with my own rules works. It sends summary mails and I can read them by Mozilla Thunderbird. Wi-Fi seems odd; even I use the physical toggle switch and make it Off, GNOME setting panel shows nearby SSIDs. Maybe this is TOSHIBA laptop's hardware issue. I turned Off the Wi-Fi on GNOME setting panel, it seems no problem. Regard.
Bug#925411: Count me as happy user of make-kpkg
Hello, I'm quite "suprised" by todays dist-upgrade. I use make-kpkg (with some wrapper scripts) since I switched to Debian around 2000. I just build 5.0.7 last Sunday. So this is a bad suprise this late in the development cycle. I did not have a chance to read all details of all bugs/links in this bug report (I'm in a bit of rush at the moment). Hopefully the replacement works as flawlessly as make-kpkg did. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#910104: Re: [LLNL/hypre] tests regularly hang (#44)
On 2019-04-13 04:37, Paul Gevers wrote: Has there been any progress on this issue? This issue is blocking full utilization of the test in the Debian infrastructure. The next Debian release is near. A fix would be very welcome. On 2019-04-13 04:59, ulrikeyang wrote: I don't know what's causing your problem, since there isn't enough info provided, however we have a new release, so you could try that. hypre's repo is now on https://github.com/hypre-space/hypre . [1] https://github.com/LLNL/hypre/issues/44#issuecomment-482721207 I've cherry-picked race-condition fixes from hypre 2.16.0, https://github.com/hypre-space/hypre/commit/b99fe7719c56073ea77d5c5400ef35229bf6b3ab https://github.com/hypre-space/hypre/commit/97cd175d5470dc81fa47e84f85e4afd2db3ef483 97cd175 also had memory fixes (BigInt) which did not apply cleanly. So I've removed those parts of the patch (in debian patch fix_race_condition_97cd175.patch) I've uploaded the 2 patches as hypre 2.15.1-5 They build and pass tests. We'll need to run a barrage of tests to see if they fixing the intermittent test failures. If it doesn't help, the next option is to take the full transition to hypre 2.16.0. Drew
Bug#926909: libblis-openmp-dev: blis needs to provide blas shlib dependency files
Hi Drew, Thanks for the report! I didn't even notice that... I think this will fix the bug, after updating symbols for all architectures likewise and refreshing the symbol lists: https://salsa.debian.org/science-team/blis/commit/ca29b285093acc602b891a993fa38a33f79a
Bug#926976: [pre-a] unblock: blis/0.5.1-13
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I'd like to apply for unblocking package blis in advance. (explain the reason for the unblock here) I'm going to fix this bug (the severity is actually important): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926909 BLIS is one of the two fastest free-software BLAS implementations, and sometimes it's even faster than MKL... which means a lot to scientific computing users. So I'm eager to fix this problem for Buster for sake of package quality. I plan to first upload (= 0.5.1-12) with this tiny patch, abusing buildd to refresh symbol lists for all architectures: https://salsa.debian.org/science-team/blis/commit/ca29b285093acc602b891a993fa38a33f79a Then I'll upload (= 0.5.1-13) with collected symbol patches. The packaging detail for the BLAS/LAPACK family is a bit complex. Each BLIS variant (there are 6 variants in total) binary package ships two shared objects, one of them is used as libblis.so.2 registered as an alternative to libblis.so.2-, and another is libblas.so.3 stored in its subdirectory, registered as an alternative to libblas.so.3-. The current (= 0.5.1-11) version in testing/sid doesn't provide a dependency template for libblas.so.3, and that appears to be problematic as a drop-in replacement for libblas-dev. See the aforementioned bug. The proposed patch should be able to fix that. Is this (quality improvement) change acceptable to Buster? (include/attach the debdiff against the package in testing) unblock blis/0.5.1-13 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-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
Bug#926968: diaspora-common: fails to federate with other diaspora servers
On Sat, 13 Apr 2019 03:22:35 +0530 Ambady Anand S
wrote:
> Package: diaspora-common
> Version: 0.7.6.1
> Severity: normal
>
> Dear Maintainer,
>
>Diaspora fails to federate with other diaspora servers a.k.a pods.
>
>Diaspora needs a configuration file for sidekiq named schedule.yml
>without which federation will not work. This file is supposed to be
>autogenerated by an initializer ruby script called
>sidekiq_scheduled.rb but it is failing to do so because of
>insufficient file system permissions. This could be solved by making
>the directory ${diaspora_home}/config owned by ${diaspora_user}.
See
https://salsa.debian.org/ruby-team/diaspora-installer/blob/master/debian/diaspora-common.links#L7
We should install this as a symbolic link in /etc/diaspora pointing to
/var/lib/diaspora where diaspora user has write access.
> With best regards,
> Ambady Anand S
>
>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#926974: Followup
I noticed that this crash only happens when transmitting while in "Stretch" image mode, which appears to be the default when loading the attached image for TX. If I set the mode to "Fit" or "Crop," the transmission completes without crash. -- ⛵ - 🏴☠️
Bug#926975: installation-reports: Grub install and/or update is okay, amd64, LVM-over-LUKS on a SSD.
Package: installation-reports Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: tester@busterlp To: Debian Bug Tracking System Subject: installation-reports: Grub install and/or update is okay, amd64, LVM-over-LUKS on a SSD. Bcc: tester@busterlp Package: installation-reports Severity: normal Dear Maintainer, This time, I upgraded my laptop Stretch into Buster, and found Grub bug report at "reportbug installation-reports". Rewrite the sources.list, apt update -> upgrade -> dist-upgrade. As far as I tested, GRUB seems OK. * LVM-over-LUKS, discard options, fstrim works. * update-grub is OK. (I swapped original HDD into Sandisk SATA SSD) This laptop is almost test purpose machine. I create this report on that, submitting from my main machine. -- Package-specific info: Boot method: upgrade from Stretch Image version: N/A Date: 2019-04-13 Machine: TOSHIBA TX-66 Partitions: FilesystemType 1K-blocksUsed Available Use% Mounted on udev devtmpfs 1900784 0 1900784 0% /dev tmpfs tmpfs 3835806300377280 2% /run /dev/mapper/main-rootfs ext4 3776568 568224 2996788 16% / /dev/mapper/main-usr ext4 7622824 1372828 5843060 20% /usr tmpfs tmpfs 1917880 120 1917760 1% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 1917880 0 1917880 0% /sys/fs/cgroup /dev/sda1 ext4474712 79413366269 18% /boot tmpfs tmpfs 1917880 124 1917756 1% /tmp /dev/mapper/main-var ext4 3776568 18268 3546744 1% /var /dev/mapper/main-home ext4 30626664 123048 28924816 1% /home /dev/mapper/main-varlog ext4 1886280 31604 1740808 2% /var/log /dev/mapper/main-varlib ext4 1886280 680344 1092068 39% /var/lib /dev/mapper/main-usrshare ext4 15311208 1920456 12593264 14% /usr/share /dev/mapper/main-varcache ext4 1886280 82088 1690324 5% /var/cache /dev/mapper/main-vartmp ext4 3776568 15312 3549700 1% /var/tmp /dev/mapper/main-varspool ext4 18862805772 1766640 1% /var/spool /dev/mapper/main-varmail ext4 18862805712 1766700 1% /var/mail tmpfs tmpfs 383576 0383576 0% /run/user/0 tmpfs tmpfs 3835766044377532 2% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: It seems upgrading from Stretch had no problem. GNOME, Firefox ESR, LibreOffice, works fine under some of my AppArmor enforce mode profiles; though I need some tweaks by aa-logprof. On the other hand, unused old WiFi module had trouble. * rtl8192se: printing error on all tty periodically. rmmod it solve that error prints. Perhaps I should blacklist it. note: On this laptop, there is a WiFi On/Off physical toggle switch, and I keep it Off always. Maybe that is the cause. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="9 (stretch) - installer build 20170615+deb9u5" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux busterlp 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series
Bug#922733: Bumped to serious
This is a show stopper bug for any package that uses the functionality. Bumping to serious. Scott K
Bug#926973: unblock: ddskk/16.2-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock the ddskk package (priority: optional) to fix the important bug #926861. See also the attached debdiff. (Note: non-UTF-8 files are changed, so use the nkf package to see the decoded characters, e.g. `nkf *.debdiff | less`) changelog: > ddskk (16.2-7) unstable; urgency=medium > > * New patch 020_reiwa.patch to not fail when 令和元年 (2019/5-) > (closes: #926861) > > -- Tatsuya Kinoshita Fri, 12 Apr 2019 21:18:06 +0900 unblock ddskk/16.2-7 Thanks, -- Tatsuya Kinoshita ddskk.debdiff Description: Binary data pgpw68QoYeKfj.pgp Description: PGP signature
Bug#926972: unblock: skkdic/20190217-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock the skkdic package (priority: optional) to fix the important bugs #926862, #926863. See also the attached debdiff. (Note: non-UTF-8 files are changed, so use the nkf package to see the decoded characters, e.g. `nkf *.debdiff | less`) changelog: > skkdic (20190217-2) unstable; urgency=medium > > * New patch 010_reiwa.patch to add Japan's new era 令和 (Reiwa) > (closes: #926862, #926863) > > -- Tatsuya Kinoshita Thu, 11 Apr 2019 21:52:37 +0900 unblock skkdic/20190217-2 Thanks, -- Tatsuya Kinoshita skkdic.debdiff Description: Binary data pgp43atrTjPqU.pgp Description: PGP signature
Bug#916372: pastebinit: multiple deprecation warnings under Python 3.7
Dear Maintainer, I have uploaded an NMU for this using Antonio's patches to DELAYED/5. Let me know if you would like me to delay it further. Thanks. -- Simon Quigley tsimo...@debian.org tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature
Bug#711853: Bug# 711853: insserv
> I just ran a quick test and can confirm that if I have an existing > link to a service, for example /etc/rc5.d/S05bluetooth, then running > the command "insserv bluetooth" will attempt to remove the old > symlink and replace it with one that conforms to the LSB headers. In > my case, removing the original link and creating > /etc/rc5.d/S04bluetooth. > > Now, as to whether this should be considered a bug or a desired > effect is open to debate. On the one hand it is understandable > people might not want insserv to overwrite their changes. On the > other hand, in my case insserv is fixing a mistake in my symlinks, > and adjusting them to match their LSB headers. > > My thought on this is if someone wants to improve their start-up > routine it makes more sense for them to edit their script's LSB > header and re-run insserv rather than editing links by hand. I've always assumed that: - the rcX.d links are only meant to be changed by running "insserv" (directly or via update-rc.d) - the dependencies of "/etc/init.d/foo" should be changed via "/etc/insserv/overrides/foo"
Bug#926970: follow up
exact error message: profanity: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by profanity) 0x9A84C39E7DDC5A4F.asc Description: application/pgp-keys
Bug#926970: profanity: Profanity tries to use libcurl3 which isn't included in the repository.
Package: profanity Version: 0.6.0-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to start profanity * What exactly did you do (or not do) that was effective (or ineffective)? I tried to uninstall and reinstall the package, same thing with libcurl. * What was the outcome of this action? Nothing changed. * What outcome did you expect instead? I wanted Profanity to start *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages profanity depends on: ii libassuan0 2.5.2-1 ii libatk1.0-0 2.30.0-2 ii libc62.28-8 ii libcairo21.16.0-4 ii libcurl3-gnutls 7.64.0-2 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-1 ii libgpg-error01.35-1 ii libgpgme11 1.12.0-6 ii libgtk2.0-0 2.24.32-3 ii libncursesw6 6.1+20181013-2 ii libnotify4 0.7.7-4 ii libotr5 4.1.1-3 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpangoft2-1.0-01.42.4-6 ii libpython3.7 3.7.3~rc1-1 ii libreadline7 7.0-5 ii libstrophe0 0.9.2-2 ii libtinfo66.1+20181013-2 ii libx11-6 2:1.6.7-1 ii libxss1 1:1.2.3-1 profanity recommends no packages. profanity suggests no packages. -- no debconf information
Bug#887733: Should this bug be closed?
This bug is still open but has been marked as fixed in the versions currently in testing/unstable and stable. It also has been fixed in oldstable-security. Should it be closed or is there any reason to still keep it open? signature.asc Description: This is a digitally signed message part.
Bug#926969: libapt-pkg: SetSignedBy can attempt to access index -1 in an array
Package: libapt-pkg5.0
Version: 1.4.9
Severity: normal
Tags: patch
Dear Maintainer,
In troubleshooting of another problem I found an invalid memory access testing
with ASAN. Attached is a patch to ensure this does not happen.
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-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 libapt-pkg5.0 depends on:
ii libbz2-1.0 1.0.6-8.1
ii libc6 2.24-11+deb9u3
ii libgcc1 1:6.3.0-18+deb9u1
ii liblz4-10.0~r131-2+b1
ii liblzma55.2.2-1.2+b1
ii libstdc++6 6.3.0-18+deb9u1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages libapt-pkg5.0 recommends:
ii apt 1.4.9
libapt-pkg5.0 suggests no packages.
-- no debconf information
commit 706e8fe6cb93323e6b03c662aaced03a36db3574
Author: Sam Bingner
Date: Thu Apr 11 13:31:14 2019 -1000
Don't access invalid string indexes
diff --git a/apt-pkg/deb/debmetaindex.cc b/apt-pkg/deb/debmetaindex.cc
index f25906fba..610965024 100644
--- a/apt-pkg/deb/debmetaindex.cc
+++ b/apt-pkg/deb/debmetaindex.cc
@@ -682,13 +682,13 @@ bool debReleaseIndex::SetSignedBy(std::string const
&pSignedBy)
SignedBy = os.str();
}
// Normalize the string: Remove trailing commas
- while (SignedBy[SignedBy.size() - 1] == ',')
+ while (SignedBy.size() > 0 && SignedBy[SignedBy.size() - 1] == ',')
SignedBy.resize(SignedBy.size() - 1);
}
else {
// Only compare normalized strings
auto pSignedByView = APT::StringView(pSignedBy);
- while (pSignedByView[pSignedByView.size() - 1] == ',')
+ while (pSignedByView.size() > 0 && pSignedByView[pSignedByView.size() -
1] == ',')
pSignedByView = pSignedByView.substr(0, pSignedByView.size() - 1);
if (pSignedByView != SignedBy)
return _error->Error(_("Conflicting values set for option %s regarding
source %s %s: %s != %s"), "Signed-By", URI.c_str(), Dist.c_str(),
SignedBy.c_str(), pSignedByView.to_string().c_str());
Bug#926968: diaspora-common: fails to federate with other diaspora servers
Package: diaspora-common
Version: 0.7.6.1
Severity: normal
Dear Maintainer,
Diaspora fails to federate with other diaspora servers a.k.a pods.
Diaspora needs a configuration file for sidekiq named schedule.yml
without which federation will not work. This file is supposed to be
autogenerated by an initializer ruby script called
sidekiq_scheduled.rb but it is failing to do so because of
insufficient file system permissions. This could be solved by making
the directory ${diaspora_home}/config owned by ${diaspora_user}.
With best regards,
Ambady Anand S
Bug#926794: linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config
Hello Ben, as this does not have any direct impact on any other components I think it can be enabled independently. This is because the first write to the console bounds it to the FB and the output behavior works as usual. On other hand, I definitely agree with you that other components has to be updated as well in order to be possible to fully use this feature. At least, the screen must be captured prior the display driver is loaded and the Systemd runs the console initialization in order to be possible to restore the vendor logo displayed by EFI shell after mentioned tasks. Also, components such as Plymouth should be updated in order to be possible to use the “UEFI” theme. Unfortunately, the list of components can be more wide and I can’t even imagine the foll set of them. I asked to enable it independently because it currently prevents us from customization of the boot process while the standard Debian Kernel build is in use. We can do it only in case we recompile the Kernel on our own. It is not optimal for the productional environments. Regards, Frantisek > On 12 Apr 2019, at 22:17, Ben Hutchings wrote: > > On Wed, 10 Apr 2019 15:58:07 +0200 Frantisek Novak < > novak.franti...@atlas.cz> wrote: >> Package: linux-image-4.19.0.0-bpo.4-amd64 >> Version: linux-image-4.19.0-0-bpo.4-amd64 >> Severity: wishlist >> >> Dear Maintainer, >> >> please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel > configuration to prevent clearing of the framebuffer when the console > starts during the boot. > > I tried it a few months back and I don't think we should do this in the > kernel in isolation. We would also need to make the boot loader silent > by default, and we might need to update themes as well. > > If you want this to happen, please propose those changes in the other > packages after the buster release. > > Ben. > > -- > Ben Hutchings > Hoare's Law of Large Problems: > Inside every large problem is a small problem struggling to get out. > >
Bug#922654: debian-policy: Section 9.1.2 points to a wrong FHS section?
Hello, On Thu 11 Apr 2019 at 02:37PM +00, Linda Lapinlampi wrote: > On Thu, Apr 11, 2019 at 02:35:26PM +, Linda Lapinlampi wrote: >> Just fyi: The debian/changelog file references section 9.11 incorrectly >> for UNRELEASED 4.3.0.4 version; the section should be 9.1.1. The commit >> has it correct. > > Actually, I think I was meant to say 9.1.2 for the changelog. Fixed, thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#926936: udev: systemd-udevd PID file name produces false positive with rkhunter for XORDDOS malware
Control: reassign -1 rkhunter Am 12.04.19 um 14:53 schrieb Andrew J. Buehler: > It is possible to whitelist this filename in rkhunter's configuration > settings, > but doing so does - however mildly - increase the likelihood that if this > malware does get a foothold on the system, rkhunter will not detect it. Thus, > a > way to remove this false positive from the udev side would be preferable. Fwiw, this only affects sysvinit systems and I'm not convinced the udev package should work around rkhunter limitations. Clearly this is a false-positive of rkhunter and should be fixed there. I'll reassign this to rkhunter. -- 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#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
reopen 924829
kthxbye
caffe still doesn't build with unstable's texlive-extra, a quick tail:
Package longtable Warning: Column widths have changed
(longtable)in table 5.5 on input line 97.
! Improper \prevdepth.
\tabu@verticalspacing ...tempdimc \the \prevdepth
\@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
?
! Emergency stop.
\tabu@verticalspacing ...tempdimc \the \prevdepth
\@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
A full log can be found at:
https://people.debian.org/~adconrad/caffe_1.0.0+git20180821.99bd997-2build2_amd64.build
... Adam
Bug#926920: Additinal reports
Dear maintainers, * LibreOffice AppArmor profiles needs some more rules, by aa-logprof check. w/ or w/o that tuning, LibreOffice seems and works normally. * ibus-mozc Japanese Input seems fine. I can compose Japanese article with it, by LibreOffice Writer. At Stretch, Tools and Properties are sometimes unavailable; though I can not reproduce them and have no idea what is wrong. * sshd works. * PAM su restriction, securetty works. I setup them to restrict direct tty root login only; no sudo. * HDMI connected speakers does not play sounds. GNOME setting panels' speaker tests does not work, too. (GeForce 1030 -> HDMI -> LCD w/ speakers) I have no idea about these problems survey, If you have any idea what I should check and/or attempt, please give me your idea or some instruction. I'm testing on dedicated machine. I almost can do anything including HW configurations. Regards.
Bug#925399: zim: Window dialog become oversized for long paths
Control: forwarded -1 https://github.com/zim-desktop-wiki/zim-desktop-wiki/issues/786 On Mon, 08 Apr 2019, Emmanuel Chantréau wrote: > The complet path (which zim try to print in one line) is : Thanks for the details, I forwarded your bug report to the upstream developer. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Bug#926967: Don't recommend irqbalance (was: Re: Handling irqbalance in virtual environments)
Package: src:linux Version: 4.19.28-2 Severity: important On Fri, Apr 12, 2019 at 09:10:32PM +0100, Ben Hutchings wrote: > On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote: > > It turns out we got again problems with irqbalance. > > > > It was added as recommends of the main image in 3.16, as it was reported > > that older kernels move all interrupts to CPU 0 without help.[1] > > > > In the meantime the kernel can do balancing on it's own. In 4.9, I've > > seen it working with aacraid, each queue gets hard pinned to it's own > > CPU from 0 to $NRCPUS. In 4.19 I've seen the same working properly with > > virtio-net. > > > > With 4.19, even on real hardware, where interrupts have an affinity for > > all cpus, each interrupt is actually delivered to different cpu. > > > > Random example for this, it even selects only one thread of each core: > > > > > 26:0000 92000 IR-PCI-MSI 3670017-edge > > > eno1-TxRx-0 > > > 27:00000 16700 IR-PCI-MSI 3670018-edge > > > eno1-TxRx-1 > > > 28:000000 4670 IR-PCI-MSI 3670019-edge > > > eno1-TxRx-2 > > > 29:0000000 454 IR-PCI-MSI 3670020-edge > > > eno1-TxRx-3 > > > > Now irqbalance comes to re-do the existing pinning, and the result is not > > longer correct but $RANDOM for the hard queue-to-cpu case of virtio. > > Then let's drop the recommendation. Okay. Regards, Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9
Bug#926292: manpages-dev: memfd_create needs sys/mman.h, not sys/memfd.h
tags fixed-upstream thanks This error was fixed in the latest upstream version, which was released a few weeks ago. On Wed, 3 Apr 2019 at 04:42, Marc Lehmann wrote: > > Package: manpages-dev > Version: 4.16-1 > Severity: minor > > Dear Maintainer, > > the manpage for memfd_create documents: > >#include > > but as far as I can tell, this heade rnever existed and trhere are not > plans to bring it into existance. > > Instead, the header to use is: > >#include > > And it requires _GNU_SOURCE or equivalent. > > -- System Information: > Debian Release: 9.8 > APT prefers stable > APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, > 'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, > 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, x32 > > Kernel: Linux 4.19.27-041927-generic (SMP w/8 CPU cores) > Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX > (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages manpages-dev depends on: > ii manpages 4.16-1 > > manpages-dev recommends no packages. > > Versions of packages manpages-dev suggests: > ii konqueror [man-browser] 4:16.08.3-1 > ii man-db [man-browser] 2.7.6.1-2 > > -- no debconf information > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Bug#926966: RFA: vim-lastplace -- Vim script to reopen files at your last edit position
Package: wnpp Severity: normal I request an adopter for the vim-lastplace package. The package description is: Intelligently reopen files at your last edit position. By default git, svn, and mercurial commit messages are ignored because you probably want to type a new message and not re-edit the previous one. Maintaining this package is not much work. It is a small package with only one vim addon that does not change much.
Bug#924591: e2fsprogs?
I quickly checked the versions of e2fsprogs used by Android vs what it is in buster. It seems that buster is as new as the Android version. So either this specific feature was added via a Google patch or it was not enabled in the Debian build of e2fsprogs. Do you have any more information on the specific missing features?
Bug#926965: RFA: jugglinglab -- Application for creating and animating juggling patterns
Package: wnpp Severity: normal I request an adopter for the jugglinglab package. It's a Java application for visualization of juggling patterns. It is near to no work, because it is not developed actively anymore. No one has filed a bug against that package so far. The package description is: Juggling Lab is an application written in Java for creating and animating juggling patterns. . Its main goals are to help people learn juggling patterns, and to assist in inventing new ones. . It generates and animates synchronous and asynchronous siteswaps and also multiplex siteswaps. Hand and body movement can be adjusted. . Part of the program is its siteswap generator, which allows one to generate
Bug#926964: ITP: libmaus2 -- collection of data structures and algorithms for biobambam
Package: wnpp Severity: wishlist Subject: ITP: libmaus2 -- collection of data structures and algorithms for biobambam Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: libmaus2 Version : 2.0.611 Upstream Author : German Tischler * URL : https://gitlab.com/german.tischler/libmaus2 * License : GPL-3+ Programming Lang: C Description : collection of data structures and algorithms for biobambam Libmaus2 is a collection of data structures and algorithms. It contains . * I/O classes (single byte and UTF-8) * bitio classes (input, output and various forms of bit level manipulation) * text indexing classes (suffix and LCP array, fulltext and minute (FM), ...) * BAM sequence alignment files input/output (simple and collating) . and many lower level support classes. Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/libmaus2
Bug#926963: gpac: CVE-2019-11221: buffer-overflow issue in gf_import_message() in media_import.c
Source: gpac Version: 0.5.2-426-gc5ad4e4+dfsg5-4.1 Severity: important Tags: security upstream Forwarded: https://github.com/gpac/gpac/issues/1203 Control: found -1 0.5.2-426-gc5ad4e4+dfsg5-3+deb9u1 Control: found -1 0.5.2-426-gc5ad4e4+dfsg5-3 Hi, The following vulnerability was published for gpac. CVE-2019-11221[0]: | GPAC 0.7.1 has a buffer overflow issue in gf_import_message() in | media_import.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-11221 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11221 [1] https://github.com/gpac/gpac/issues/1203 [2] https://github.com/gpac/gpac/commit/f4616202e5578e65746cf7e7ceeba63bee1b094b Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#926794: linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config
On Wed, 10 Apr 2019 15:58:07 +0200 Frantisek Novak < novak.franti...@atlas.cz> wrote: > Package: linux-image-4.19.0.0-bpo.4-amd64 > Version: linux-image-4.19.0-0-bpo.4-amd64 > Severity: wishlist > > Dear Maintainer, > > please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel configuration to prevent clearing of the framebuffer when the console starts during the boot. I tried it a few months back and I don't think we should do this in the kernel in isolation. We would also need to make the boot loader silent by default, and we might need to update themes as well. If you want this to happen, please propose those changes in the other packages after the buster release. Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Bug#926961: gpac: CVE-2019-11222: Buffer-overflow in gf_bin128_parse
Source: gpac Version: 0.5.2-426-gc5ad4e4+dfsg5-4.1 Severity: important Tags: security upstream Hi, The following vulnerability was published for gpac. CVE-2019-11222[0]: | gf_bin128_parse in utils/os_divers.c in GPAC 0.7.1 has a buffer | overflow issue for the crypt feature when encountering a | crafted_drm_file.xml file. 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-11222 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11222 [1] https://github.com/gpac/gpac/commit/f36525c5beafb78959c3a07d6622c9028de348da [2] https://github.com/gpac/gpac/issues/1204 [3] https://github.com/gpac/gpac/issues/1205 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#926962: Fwd: NOTICE: mail delivery status.
Package: lists.debian.org Severity: normal lists.debian.org stopped accepting attachements, see below: - Forwarded message from mailer-daemon@213.239.213.133 - > Date: Fri, 12 Apr 2019 22:10:08 +0200 > From: mailer-daemon@213.239.213.133 > To: deb...@helgefjell.de > Subject: NOTICE: mail delivery status. > > > This is a delivery status notification from > static.213-239-213-133.clients.your-server.de, > running the Courier mail server, version 0.73.1. > > The original message was received on Fri, 12 Apr 2019 22:10:05 +0200 > from localhost (localhost [127.0.0.1]) > > --- > >UNDELIVERABLE MAIL > > Your message to the following recipients cannot be delivered: > > : > bendel.debian.org [82.195.75.100]: > >>> DATA > <<< 550 5.7.1 No attachments allowed > > --- > > If your message was also sent to additional recipients, their delivery > status is not included in this report. You may or may not receive > other delivery status notifications for additional recipients. > > The original message follows as a separate attachment. > > Reporting-MTA: dns; static.213-239-213-133.clients.your-server.de > Arrival-Date: Fri, 12 Apr 2019 22:10:05 +0200 > Received-From-MTA: dns; localhost (localhost [127.0.0.1]) > > Final-Recipient: rfc822; debian-l10n-ger...@lists.debian.org > Action: failed > Status: 5.0.0 > Remote-MTA: dns; bendel.debian.org [82.195.75.100] > Diagnostic-Code: smtp; 550 5.7.1 No attachments allowed > Date: Fri, 12 Apr 2019 22:10:05 +0200 > From: Helge Kreutzmann > To: debian-l10n-ger...@lists.debian.org > Subject: [RFR] man://manpages-de/systemd.exec.5.po (Teil 1/23) > User-Agent: Mutt/1.5.23 (2014-03-12) > > Moin, > die Handbuchseiten von Systemd wurden übersetzt. > > Ich wäre Euch dankbar, wenn Ihr mir konstruktive Rückmeldungen zu dem > ersten Teil der angehängten Seite (30 Zeichenketten) geben könntet. > > Vielen Dank & Grüße > > Helge > > -- > Dr. Helge Kreutzmann deb...@helgefjell.de >Dipl.-Phys. http://www.helgefjell.de/debian.php > 64bit GNU powered gpg signed mail preferred >Help keep free software "libre": http://www.ffii.de/ > # German translation of manpages > # This file is distributed under the same license as the manpages-de package. > # Copyright © of this file: > # Helge Kreutzmann , 2018-2019. > msgid "" > msgstr "" > "Project-Id-Version: manpages-de\n" > "POT-Creation-Date: 2019-02-28 13:12+01:00\n" > "PO-Revision-Date: 2019-04-12 19:12+0200\n" > "Last-Translator: Helge Kreutzmann \n" > "Language-Team: German \n" > "Language: de\n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=UTF-8\n" > "Content-Transfer-Encoding: 8bit\n" > "Plural-Forms: nplurals=2; plural=(n != 1);\n" > > #. type: TH > #: archlinux debian-unstable > #, no-wrap > msgid "SYSTEMD\\&.EXEC" > msgstr "SYSTEMD\\&.EXEC" > > #. type: TH > #: archlinux debian-unstable > #, no-wrap > msgid "systemd 241" > msgstr "systemd 241" > > #. type: TH > #: archlinux debian-unstable > #, no-wrap > msgid "systemd.exec" > msgstr "systemd.exec" > > #. - > #. * MAIN CONTENT STARTS HERE * > #. - > #. type: SH > #: archlinux debian-unstable > #, no-wrap > msgid "NAME" > msgstr "BEZEICHNUNG" > > #. type: Plain text > #: archlinux debian-unstable > msgid "systemd.exec - Execution environment configuration" > msgstr "systemd.exec - Konfiguration der Ausführungsumgebung" > > #. type: SH > #: archlinux debian-unstable > #, no-wrap > msgid "SYNOPSIS" > msgstr "ÜBERSICHT" > > #. type: Plain text > #: archlinux debian-unstable > msgid "" > "I\\&.service, I\\&.socket, I\\&.mount, I\\&." > "swap" > msgstr "" > "I\\&.service, I\\&.socket, I\\&.mount, I" > "\\&.swap" > > #. type: SH > #: archlinux debian-unstable > #, no-wrap > msgid "DESCRIPTION" > msgstr "BESCHREIBUNG" > > #. type: Plain text > #: archlinux debian-unstable > msgid "" > "Unit configuration files for services, sockets, mount points, and swap " > "devices share a subset of configuration options which define the execution " > "environment of spawned processes\\&." > msgstr "" > "Unit-Konfigurationsdateien für Dienste, Sockets, Einhängepunkte und " > "Auslagerungsgeräte nutzen eine Teilmenge der Konfigurationsoptionen, die die > " > "Ausführungsumgebung von gestarteten Prozessen definieren\\&." > > #. type: Plain text > #: archlinux debian-unstable > msgid "" > "This man page lists the configuration options shared by these four unit > types" > "\\&. See B(5) for the common options of all unit " > "configuration files, and B(5), B(5), " > "B(5), and B(5) for more information on the " > "specific unit configuration files\\
Bug#926960: cjet: autopkgtest times out since 2019-04-07
Source: cjet Version: 0.8.9-7 X-Debbugs-CC: debian...@lists.debian.org Severity: important User: debian...@lists.debian.org Usertags: timeout regression Dear maintainers, Since 2019-04-07 the autopkgtest of your package started to fail because it times out (after 2:47h) on ci.debian.net in both unstable and testing. Unfortunately, this most likely isn't caused by any of your direct (test) dependencies, otherwise the integration with our migration software should have caught it. If the content of our log is correct, the following files may hint at the culprit: https://ci.debian.net/data/packages/unstable/amd64/c/cjet/2214069.log https://ci.debian.net/data/packages/testing/amd64/c/cjet/2226265.log Can you please investigate the situation? Don't hesitate to ask for help from the Debian CI team (in X-Debbugs-CC) if you need help solving this issue. If the situation doesn't change in a week or two I may blacklist this package on the ci.debian.net infrastructure. If that happens I will remove the blacklist once this bug is fixed. If needed, please ping me to try any uploads you make that should fix the issue if you are unsure and don't want to close this bug until verified. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/c/cjet/2226265/log.gz autopkgtest [12:38:01]: test printer-driver-cjet: [--- * Driver foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Canon-LBP-4U-cjet.ppd - Create test printer: done. - Print test job with /usr/share/cups/data/standard.pdf:
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 10.04.19 um 19:43 schrieb Bernhard Übelacker:
> Control: reassign 921266 libbellesip0 1.6.3-4
> Control: affects 921266 linphone
> Control: tags 921266 + upstream patch
> (gdb) list provider.c:1032,1050
> 1032
> 1033static void
> authorization_context_fill_from_auth(authorization_context_t*
> auth_context,belle_sip_header_www_authenticate_t*
> authenticate,belle_sip_uri_t *from_uri) {
> 1034
> authorization_context_set_realm(auth_context,belle_sip_header_www_authenticate_get_realm(authenticate));
> 1035 > if (auth_context->nonce &&
> strcmp(belle_sip_header_www_authenticate_get_nonce(authenticate),auth_context->nonce)!=0)
> {
> 1036/*new nonce, resetting nounce_count*/
> 1037auth_context->nonce_count=0;
> 1038}
>
Thanks for your help Bernhard!
I am prepared to test your patch as soon as I get a binary of the
patched lib.
I just got aware of another detail regarding Telekom/t-online:
Some time ago (1 - 2 years) the internet access has been switched to so
called "BNG" (broadband network gateway). With that the authentication
no longer needs a password, it is tied to "the pair of wires" = the
physical port on the DSL access multiplexer.
So a password is actually obsolete, every string or even none as a
password does allow registration. The only parameter needed is the phone
number which should be registered (I got 4). I tested with twinkle (in
Buster and Stretch) and linphone 3.6.1 in Stretch.
Kind regards,
Alf
Bug#926959: xsane: Missing Name and Comment to pt_BR
Source: xsane Severity: minor Tags: l10n Missing Name and comment on xsane.desktop to pt_BR -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#926419: abiword: When logged in with wayland session you can not see what you type with out having to scroll screen.
I am using wayland and I also getting the exact same problem with no text appearing until the screen is resized in some way.
Bug#920455: followup on bash process substitution and wait
Control: forwarded 920455 https://lists.gnu.org/archive/html/bug-bash/2019-04/msg00076.html https://bugs.debian.org/920455 is being discussed with upstream over on the bug-b...@gnu.org mailing list. --dkg signature.asc Description: PGP signature
Bug#926958: VU#871675: Authentication bypass in EAP-PWD
Package: src:freeradius Severity: important Tags: security 3.0.19 has been released adressing some issues in EAP-PWD. The VU# linked in the original advisory is not (yet?) accessible and I haven't found a CVE for it. Since FreeRADIUS is orphaned I'll look at doing an NMU when I find some time, but likely not before early next week. https://freeradius.org/security/ 2019.04.10Authentication bypass in EAP-PWD The EAP-PWD module is vulnerable to multiple issues, including authentication bypass. This module is not enabled in the default configuration. Administrators must manually enable it for their server to be vulnerable. Version 3.0.0 through 3.0.18 are are affected. The EAP-PWD module is vulnerable to side-channel and cache-based attacks. The issue is discussed in more in Hostap 2019-2. The attack requires the attacker to be able to run a program on the target device. This is not commonly the case on an authentication server (EAP server), so the most likely target for this would be a client device using EAP-PWD. It is not clear at this time if the attack is possible between multiple virtual machines on the same hardware. Other issues with EAP-PWD were found earlier, and patched in Hostap. The FreeRADIUS team was not notified of these attacks until recently. We have now patched FreeRADIUS to address these issues. Additional issues were found by Mathy Vanhoef as part of a deep investigation into EAP-PWD. He also supplied patches to address the issues. His report is included below. This issue is recorded in VU#871675 We have released version 3.0.19 to address these issues.
Bug#926957: RM: plainbox-provider-resource-generic -- ROM; no longer maintained as a deb
Package: ftp.debian.org Severity: normal checkbox upstream has moved to develop checkbox as a snap only. This packaging is now obsolete and dead and should be removed from the Debian archive. This bug report is filed by me, with consent from the checkbox team. Regards, Dimitri.
Bug#926956: RM: plainbox-provider-checkbox -- ROM; no longer maintained as a deb
Package: ftp.debian.org Severity: normal checkbox upstream has moved to develop checkbox as a snap only. This packaging is now obsolete and dead and should be removed from the Debian archive. This bug report is filed by me, with consent from the checkbox team. Regards, Dimitri.
Bug#926955: RM: plainbox -- ROM; no longer maintained as a deb
Package: ftp.debian.org Severity: normal checkbox upstream has moved to develop checkbox as a snap only. This packaging is now obsolete and dead and should be removed from the Debian archive. This bug report is filed by me, with consent from the checkbox team. Regards, Dimitri.
Bug#926954: RM: checkbox-support -- ROM; no longer maintained as a deb
Package: ftp.debian.org Severity: normal checkbox upstream has moved to develop checkbox as a snap only. This packaging is now obsolete and dead and should be removed from the Debian archive. This bug report is filed by me, with consent from the checkbox team. Regards, Dimitri.
Bug#926953: RM: checkbox-ng -- ROM; no longer maintained as a deb
Package: ftp.debian.org Severity: normal checkbox upstream has moved to develop checkbox as a snap only. This packaging is now obsolete and dead and should be removed from the Debian archive. This bug report is filed by me, with consent from the checkbox team. Regards, Dimitri.
Bug#926306: RFS: socklog/2.1.0-9
[2019-04-10 23:48] Mathieu Mirmont > > part 1 text/plain 434 > On Wed, Apr 10, 2019 at 08:20:30AM +, Dmitry Bogatov wrote: > > You can repack it as new upstream version. New version would be > > something like `2.1.0+repack-1'. Do not forget add clarification into > > Debian.source. > > I've updated the package and uploaded to mentors: > > https://mentors.debian.net/package/socklog > https://mentors.debian.net/debian/pool/main/s/socklog/socklog_2.1.0+repack-1.dsc Lintian (2.11.0) warnings: W: socklog: missing-versioned-depends-on-init-system-helpers postinst:152 "update-rc.d defaults-disabled" needs i nit-system-helpers >= 1.50 W: socklog: missing-versioned-depends-on-init-system-helpers postinst:165 "update-rc.d defaults-disabled" needs i nit-system-helpers >= 1.50 W: socklog: missing-versioned-depends-on-init-system-helpers postinst:178 "update-rc.d defaults-disabled" needs i nit-system-helpers >= 1.50 Oh, and extremely minor notice: in `debian/control' you align fields with tabs. It does not look pretty, if tabstop is not 8. What about expand(1)? -- Note, that I send and fetch email in batch, once every 24 hours. If matter is urgent, try https://t.me/kaction --
Bug#926952: sa-exim: Unbuildable/uninstallable in sid
Package: sa-exim Version: 4.2.1-16 Severity: serious Control: block -1 by 879687 Hello, with exim4/4.92-5 I have dropped support for sa-exim: The dlopen localscan patch in exim4 has been nonfunctional in unstable for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1 unstable/26 Dec and buster/03 Jan). The issue only popped up end of March on the upstream user support ML. At this time I opened a tracking bug in exim #925982 and looked at sa-exim. It is dead upstream since 2006 and buggy: * https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html * #879687 (This might be same issue, I just do not know. Chunking is enabled by (upstream) default.) At this point we (exim4) decided that this was a good time to finally drop the dlopen localscan patch. We did that and adopted exim accordingly: - improve the example/docs for content-scanning in exim without sa-exim - drop the abovementioned patch and the virtual Provides for exim4-localscanapi-2.0 and also drop the exim-dev package (only needed for sa-exim). Exim now also Conflicts with sa-exim. However, what I did *not* do was consult you before I did this. I am sorry for that. It is still possible to reinstate exim-dev and try to fix exim to make sa-exim work again. But imho only if sa-exim is fixed in the first place and is tested and found to be working with current exim. What are your thoughts on this? TIA, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
Bug#926306: RFS: socklog/2.1.0-9
[2019-04-10 12:46] Mathieu Mirmont > > Are you sure you need "Depends: runit"? Maybe it is just me, but I > > thought that `socklog' is just an implementation of `syslog'. If > > so, hard dependency on bin:runit is quite heavyweight. > > It heavily relies on runsv and svlogd, that's how it splits files by > syslog service name. Essentially socklog is a data collector for svlogd. > > The alternative would be to re-implement runsv and svlogd by redirecting > the output of socklog to a file and using logrotate, but clearly that > would be a hack, it's not how it's meant to be run, and it would have > the risk of losing messages when logrotate kicks in. > > The dependency on runit is less risky than that. Also the dependency is > on runit alone, not on any of the runit-* packages that call runsvdir, > so it's quite lite. I see. Fine. -- Note, that I send and fetch email in batch, once every 24 hours. If matter is urgent, try https://t.me/kaction --
Bug#926951: ITP: python3-git-archive-all -- Archive repository with all its submodules
Package: wnpp Owner: Mark A. Hershberger Severity: wishlist Package name: python3-git-archive-all Version : 1.19.4 Upstream Author : Ilya Kulakov URL or Web page : https://github.com/Kentzo/git-archive-all License : MIT Description : Archive repository with all its submodules
Bug#926950: courier-imap-ssl: Courier IMAP and POP SSL packages have opposite cache files
Package: courier-imap-ssl Version: 4.18.1+0.78.0-2 Severity: minor Dear Maintainer, the packages courier-imap-ssl and courier-pop-ssl have configuration files with opposite cache files. courier-imap-ssl has this: TLS_CACHEFILE=/var/lib/courier/couriersslpop3cache courier-pop-ssl has this: TLS_CACHEFILE=/var/lib/courier/couriersslimapcache I assume these should be the opposite. Of course they don't affect operations so therefore low priority. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 4.15.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15), LANGUAGE=en_US:en (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages courier-imap-ssl depends on: ii courier-imap 5.0.6+1.0.6-1 courier-imap-ssl recommends no packages. courier-imap-ssl suggests no packages. -- Configuration Files: /etc/logcheck/ignore.d.server/courier-imap-ssl [Errno 13] Permission denied: '/etc/logcheck/ignore.d.server/courier-imap-ssl' /etc/logcheck/violations.ignore.d/courier-imap-ssl [Errno 13] Permission denied: '/etc/logcheck/violations.ignore.d/courier-imap-ssl' -- no debconf information
Bug#926878: unblock: exim4/4.92-5
On 2019-04-11 Paul Gevers wrote: > Control: tags -1 moreinfo > Hi Andreas, > On 11-04-2019 19:51, Andreas Metzler wrote: >> The second notable change is related to sa-exim. Exim in Debian was >> patched to allow dlopening a localscan() module. The single consumer of >> this patch in Debian is sa-exim. (The patch also originates there.) >> The patch in Debian has been nonfunctional in unstable for quite some >> time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1 unstable/26 Dec and >> buster/03 Jan). The issue only popped up end of March on the upstream >> user support ML. >> Looking at the state of sa-exim (dead upstream since 2006 and buggy: >> https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html >> #879687) we have decided stop patching exim, which resulted in 4.92-5, >> which >> - improves the example/docs for content-scanning in exim without sa-exim >> - drops the abovementioned patch and the virtual Provides for >> exim4-localscanapi-2.0 and also drops the exim-dev packages (only >> needed for sa-exim). Exim now also Conflicts with sa-exim. > I am probably missing something, but as far as I see it, your packages > can't migrate to testing/buster because it would make sa-exim > uninstallable. uninstallable and unbuildable. > If I am right, please coordinate with the maintainer of > sa-exim (in CC). At least at this moment they should agree that it is > alright to remove sa-exim from buster. I am not seeing any serious bugs > reported against sa-exim so they may not be aware of the issue. I had X-Debbugs-Cc'ed sa-exim@pdo on this report. I will also open a rc bug suggesting sa-exim removal to hash this out properly. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#925276: cron: Maximum crontab limit applied needlessly to system crontabs
Hi all, We just discovered the change of the 1000 lines limit, because we have some big crontab that are now broken. Our servers run multiple MySQL instances, that each runs many databases, the contab contains one line per database to dump once a day, so we have up to 4500 lines of legit command for a user. We tried to find a way to make it works, but we didn't found a secure one. (We don't want those cron jobs to be run by root) Currently we have downgraded the cron package to keep our prod working. The idea of the configurable limit in /etc/default/cron sounds very interesting to me (Maybe two different config for root ones and userland ones ?), it could allow the sysadmin to adapt the value for each use case. Did you have the time to take a look at it yet ? Or could you consider to raise the limit up to 5000 ? (I don't really see if a limit set to this value still protect from CVE-2019-9705 as it probably depends of the amount of memory available on the server) Any way, thank you all for the work on Debian project (even if this patch doesn't really fit my needs :D ) That's the first time i reply on a debian bug, so, sorry if didn't follow some "rules"... Maxime Feron OVH - DevOps databases
Bug#926949: LDAP connection fails due to missing depends on gnutls-bin
Package: debian-edu-config Version: 2.10.64 Severity: important While testing Debian Edu Buster installation scenarios I noticed that gnutls-cli is missing in case a system with profile 'Minimal' is installed. Establishing a secured connection to LDAP on the main server fails in this case. Just installing the gnutls-bin package solves the problem. Adding a depends on gnutls-bin will ensure all systems to be installed correctly, regardless which profile is used. Wolfgang signature.asc Description: PGP signature
Bug#918531: RFP: trx -- realtime audio over IP
This package installs "tx" and "rx" executables, but these names are already taken: $ apt-file search -x '/bin/[tr]x$' lrzsz: /usr/bin/rx transifex-client: /usr/bin/tx The prospective packager should talk to upstream about renaming the executables. -- Jakub Wilk
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
notfound 926932 4.050-2 thanks It works if I try in a machine with more RAM. Explanation: Since I'm poor but want to test as many packages as I can with the money I spend on virtual machines, I try to keep track of the memory required for each package by monitoring Committed_AS in /proc/meminfo during the build. That way I can build small packages with small machines (which are cheaper) and big packages with big machines. This procedure works most of the time, but not always. When it does not work I have an "override" to force more memory even if the historical data indicate that it does not need as much. Thanks a lot and sorry for the false positive.
Bug#912365: More info
Hi Carlos, Thanks for your bug report. Unfortunately I can't seem to reproduce this issue. I tried grepping for 'stop' in the foremost code but nothing matches, so I don't even know what part of the code you are hitting. Can you provide a test file that I can run foremost with, so I can hit the same issue? Thanks, Rul signature.asc Description: PGP signature
Bug#926933: fetch-ldap-cert fails against LDAP cert on jessie tjener
> Then run 'service fetch-ldap-certrestart'. typo, should rather be: 'service fetch-ldap-cert restart'. Wolfgang signature.asc Description: PGP signature
Bug#926933: fetch-ldap-cert fails against LDAP cert on jessie tjener
Moin Mike, On Fri, Apr 12, 2019 at 11:52:25AM +, Mike Gabriel wrote: > I just tested a Debian Edu 10 installation against a Debian Edu 8 TJENER. > The LDAP certificate on the jessie TJENER had been created wrongly (subject: > CN=localhost, issuer: CN=localhost). Maybe the SSL/TLS related changes would best be dealt with providing a jessie-pu/debian-edu-config package. (And maye for stretch-pu as well just in case someone installs a Buster workstation against a Stretch main server.) As a workaround copy these files from the Jessie main-server to the Buster workstation: (1) /etc/init.d/fetch-ldap-cert (2) /usr/bin/ldap-server-getcert (3) /etc/ldap/ldap.conf Then run 'service fetch-ldap-certrestart'. It should get this 8/10 combination working. Same should apply to a 9/10 combination. Please test. Wolfgang signature.asc Description: PGP signature
Bug#926948: unblock: tracker/2.1.8-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package tracker
This fixes crash bug #926946 that I filed, although we don't have an
existing report of it / steps to reproduce, so you might not consider
this really RC. Up to you.
unblock tracker/2.1.8-2
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
diff -Nru tracker-2.1.8/debian/changelog tracker-2.1.8/debian/changelog
--- tracker-2.1.8/debian/changelog 2019-02-21 01:26:33.0 +
+++ tracker-2.1.8/debian/changelog 2019-04-12 16:20:46.0 +0100
@@ -1,3 +1,10 @@
+tracker (2.1.8-2) unstable; urgency=medium
+
+ * gbp.conf: Update debian-branch for buster
+ * Cherry-pick upstream patch to fix crash (Closes: #926946)
+
+ -- Iain Lane Fri, 12 Apr 2019 16:20:46 +0100
+
tracker (2.1.8-1) unstable; urgency=medium
* New upstream release
diff -Nru tracker-2.1.8/debian/control tracker-2.1.8/debian/control
--- tracker-2.1.8/debian/control2019-02-21 01:26:33.0 +
+++ tracker-2.1.8/debian/control2019-04-12 16:20:46.0 +0100
@@ -6,7 +6,7 @@
Section: utils
Priority: optional
Maintainer: Debian GNOME Maintainers
-Uploaders: Iain Lane , Jeremy Bicha , Tim
Lunn
+Uploaders: Jeremy Bicha , Michael Biebl ,
Tim Lunn
Build-Depends: debhelper (>= 11),
gnome-common,
pkg-config,
diff -Nru tracker-2.1.8/debian/gbp.conf tracker-2.1.8/debian/gbp.conf
--- tracker-2.1.8/debian/gbp.conf 2019-02-21 01:26:33.0 +
+++ tracker-2.1.8/debian/gbp.conf 2019-04-12 16:20:46.0 +0100
@@ -1,6 +1,6 @@
[DEFAULT]
pristine-tar = True
-debian-branch = debian/master
+debian-branch = debian/buster
upstream-branch = upstream/latest
upstream-vcs-tag = %(version)s
diff -Nru tracker-2.1.8/debian/patches/series
tracker-2.1.8/debian/patches/series
--- tracker-2.1.8/debian/patches/series 2019-02-21 01:26:33.0 +
+++ tracker-2.1.8/debian/patches/series 2019-04-12 16:20:46.0 +0100
@@ -5,3 +5,4 @@
libtracker-miners-common-Make-g_error-a-soft-error.patch
build-Restore-right-soversion-to-libraries.patch
functional-tests-Require-Bash-for-test-runner.patch
+tracker-miner-Fix-cancellation-of-g_file_enumerator_next_.patch
diff -Nru
tracker-2.1.8/debian/patches/tracker-miner-Fix-cancellation-of-g_file_enumerator_next_.patch
tracker-2.1.8/debian/patches/tracker-miner-Fix-cancellation-of-g_file_enumerator_next_.patch
---
tracker-2.1.8/debian/patches/tracker-miner-Fix-cancellation-of-g_file_enumerator_next_.patch
1970-01-01 01:00:00.0 +0100
+++
tracker-2.1.8/debian/patches/tracker-miner-Fix-cancellation-of-g_file_enumerator_next_.patch
2019-04-12 16:20:46.0 +0100
@@ -0,0 +1,43 @@
+From: Andrea Azzarone
+Date: Mon, 1 Apr 2019 16:52:15 +0100
+Subject: tracker-miner: Fix cancellation of
+ g_file_enumerator_next_files_async
+
+The async op is not owner of the user data, so it may be actually gone in the
+GAsyncReadyCallback. Ensure we only use it on success or on other errors than
+cancelled.
+
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926946
+Bug-Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1822629
+Bug-Upstream: https://gitlab.gnome.org/GNOME/tracker/issues/86
+Origin: upstream, commit:465b8031d0a73ac775952c07d0374206746a8a46
+Applied-Upstream: 2.2.2
+---
+ src/libtracker-miner/tracker-crawler.c | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/src/libtracker-miner/tracker-crawler.c
b/src/libtracker-miner/tracker-crawler.c
+index 93b1ab1..4031d86 100644
+--- a/src/libtracker-miner/tracker-crawler.c
b/src/libtracker-miner/tracker-crawler.c
+@@ -899,7 +899,7 @@ enumerate_next_cb (GObject *object,
+ {
+ DataProviderData *dpd;
+ GList *info;
+- GError *error = NULL;
++ g_autoptr(GError) error = NULL;
+
+ info = g_file_enumerator_next_files_finish (G_FILE_ENUMERATOR (object),
result, &error);
+ dpd = user_data;
+@@ -918,9 +918,9 @@ enumerate_next_cb (GObject *object,
+ g_warning ("Could not enumerate next item in
container / directory '%s', %s",
+ uri, error ? error->message : "no
error given");
+ g_free (uri);
++ } else {
++ return;
+ }
+-
+- g_clear_error (&error);
+ } else {
+ /* Done enumerating, start processing what we got ... */
+ data_provider_data_add (dpd);
Bug#926947: d-i.debian.org: Setting the 'd-i network-console/password password' preseed variable doesn't change password of 'installer' user
Package: d-i.debian.org Severity: important Tags: d-i I'm trying to install Debian 10 with preseed configuration. A password of an 'installer' user was set like this: d-i anna/choose_modules string network-console d-i network-console/password password password d-i network-console/password-again password password This configuration worked well with the previous Debian releases, however looks like the latest Debian Buster ignores the password from configuration and leaves it as empty in /etc/shadow The content of /etc/shadow : installer::1:0:9:7::: Preseed configuration was taken from this source: https://d-i.debian.org/manual/example-preseed.txt -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=C.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
Bug#926946: tracker-miner-fs SIGSEGV in process_func_start()
Package: src:tracker Version: 2.1.8-1 Severity: serious Tags: patch upstream fixed-upstream Hi, Just filing so I have a bug reference for the unblock. In Ubuntu's error tracker we noticed reports of a crash in tracker-miner that looks like this: #0 0x7f1a2c1db676 in process_func_start (crawler=0x0) at tracker-crawler.c:713 No locals. #1 0x7f1a2c1db9d0 in enumerate_next_cb (object=, result=, user_data=0x7f19ec0886f0) at tracker-crawler.c:930 dpd = 0x7f19ec0886f0 info = error = 0x0 #2 0x7f1a2c030df6 in next_async_callback_wrapper (source_object=0x55d54803ccd0, res=0x55d547f2e1b0, user_data=0x7f19ec0886f0) at ../../../gio/gfileenumerator.c:305 enumerator = 0x55d54803ccd0 #3 0x7f1a2c070059 in g_task_return_now (task=0x55d547f2e1b0) at ../../../gio/gtask.c:1209 No locals. #4 0x7f1a2c070099 in complete_in_idle_cb (task=0x55d547f2e1b0) at ../../../gio/gtask.c:1223 No locals. #5 0x7f1a2be98958 in ?? () No symbol table info available. #6 0x7ffecede7820 in ?? () No symbol table info available. #7 0x7f1a in ?? () No symbol table info available. #8 0x in ?? () No symbol table info available. Andrea Azzarone from the Canonical team fixed this upstream[0]. I'm proposing to include the fix in buster, and I'm uploading to unstable now to hopefully achieve this. These are automated reports and I don't have steps to reproduce I'm afraid. You can see from frame #0 that process_func_start() is passed NULL. The fix avoids calling this if the operation has been cancelled, in which case data_provider_end() will be called, which frees the data. That's how we get NULL there. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] [0] https://gitlab.gnome.org/GNOME/tracker/merge_requests/86
Bug#926945: autopkgtest - autopkgtest-build-qemu on ppc64el
Package: autopkgtest Version: 5.10 Severity: important Tag: autopkgtest qemu patch buster vmdb2 Usertags: ppc64el While using debci, create-tesbed command for backends/qemu launches autopkgtest-build-qemu unstable /var/lib/debci/qemu/unstable-ppc64el.img http://deb.debian.org/debian *ppc64el* backends/qemu/customize.sh 1) it fails with E: Unable to locate package /*linux-image-ppc64el*/ the proper name should be linux-image-powerpc64le, so on line 123 I would add the following entry for architecture ppc64el /* (ppc64el)*//* *//* kernel=linux-image-powerpc64le*//* *//* ;;*/ 2) Then it calls vmdb2 with an entry: grub: bios which calls /usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py which wants to install package grub_package = 'grub-pc' for grub_target = 'i386-pc' problem is that grub-pc package doesn't exist on ppc64el at least*2 solutions there *- either in autopkgtest-build-qemu conditionally sending the grub: option and install what's needed in customize.sh script either modify vmdb2 to use grub2 package and target=powerpc-ieee1275 _NOTE:_ because grub-install doesn't install on /dev/loop0 - send a message : grub-install: error: the chosen partition is not a PReP partition I was successfull doing /grub-install ... /dev/sda1 but image is not bootable because slash not found - Not a bootable device !/ /A bit stuck right now ! / Thanks for your help Regards -- Thierry Fauck @ fr.ibm.com
Bug#926944: ITP: atropos -- NGS read trimming tool that is specific, sensitive, and speedy
Package: wnpp
Severity: wishlist
Subject: ITP: atropos -- NGS read trimming tool that is specific, sensitive,
and speedy
Package: wnpp
Owner: Andreas Tille
Severity: wishlist
* Package name: atropos
Version : 1.1.21
Upstream Author : Marcel Martin
* URL : https://github.com/jdidion/atropos
* License : Expat
Programming Lang: Python
Description : NGS read trimming tool that is specific, sensitive, and
speedy
Atropos is tool for specific, sensitive, and speedy trimming of NGS
reads. It is a fork of the venerable Cutadapt read trimmer, with the
primary improvements being:
.
1. Multi-threading support, including an extremely fast "parallel
write" mode.
2. Implementation of a new insert alignment-based trimming algorithm
for paired-end reads that is substantially more sensitive and
specific than the original Cutadapt adapter alignment-based
algorithm. This algorithm can also correct mismatches between the
overlapping portions of the reads.
3. Options for trimming specific types of data (miRNA, bisulfite-seq).
4. A new command ('detect') that will detect adapter sequences and
other potential contaminants.
5. A new command ('error') that will estimate the sequencing error
rate, which helps to select the appropriate adapter- and quality-
trimming parameter values.
6. A new command ('qc') that generates read statistics similar to
FastQC. The trim command can also compute read statistics both
before and after trimming (using the '--stats' option).
7. Improved summary reports, including support for serialization
formats (JSON, YAML, pickle), support for user-defined templates
(via the optional Jinja2 dependency), and integration with MultiQC.
8. The ability to merge overlapping reads (this is experimental and
the functionality is limited).
9. The ability to write the summary report and log messages to
separate files.
10. The ability to read SAM/BAM files and read/write interleaved
FASTQ files.
11. Direct trimming of reads from an SRA accession.
12. A progress bar, and other minor usability enhancements.
Remark: This package is maintained by Debian Med Packaging Team at
https://salsa.debian.org/med-team/atropos
Bug#926930: joblib: FTBFS (test_nested_parallelism_limit does not always work)
TL;DR summary:
interesting... in my case reliably fails locally on python 3.6 and 3.7 but not
2.7 even with fresh release of 0.13.0
reported upstream https://github.com/joblib/joblib/issues/870
Thanks for the patch -- I will xfail it in 0.13.0-1 with this, upload to
unstable, and then upload 0.13.2-1 with it to experimental
Some notes collected:
1. I think it is the same issue as
https://github.com/joblib/joblib/issues/758 which was addressed upstream in
commit f58e833df6802bbc2120a9eb2c608a8c35dbc099
Author: Olivier Grisel
Date: Mon Aug 27 11:34:30 2018 +0200
Fix a bug in nesting level computation with
FallbackToBackend(SequentialBackend()) (#759)
which is
$> git describe --contains f58e833df6802bbc2120a9eb2c608a8c35dbc099
0.12.3~5
so might have been regression in
Version: 0.13.0-1
where (on upstream)
taskset -c 0 python -m pytest -v -k test_nested_parallelism_limit
passes just ok, so probably not a straight regression.
2. Could trigger "reliably" for the second (python 3.7) test run while
passing for 2.7
with change
$> git diff
diff --git a/debian/rules b/debian/rules
index 0ede50a..dd4d8ef 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,7 @@ override_dh_auto_test: ${PYVERS:%=python-test%}
${PY3VERS:%=python-test%}
python-test%:
ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
- PYTHONPATH=$(CURDIR) python$* /usr/bin/py.test -s -v joblib;
+ PYTHONPATH=$(CURDIR) python$* /usr/bin/py.test -s -v -k
test_nested_parallelism_limit joblib;
else
: # Skip unittests due to nocheck
endif
and running
taskset -c 0 fakeroot debian/rules binary
> Note: I've checked and this failure may be reproduced easily on any
> system by doing "taskset -c 0 dpkg-buildpackage", but if for whatever
> reason you need a single-CPU system to test, please contact me
> privately and I will gladly provide one.
> Thanks.
> --- a/joblib/test/test_parallel.py
> +++ b/joblib/test/test_parallel.py
> @@ -1429,6 +1429,7 @@ def _recursive_backend_info(limit=3, **kwargs):
> return this_level + results[0]
> +@pytest.mark.xfail
> @with_multiprocessing
> @parametrize('backend', ['loky', 'threading'])
> def test_nested_parallelism_limit(backend):
Cheers,
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Bug#926943: python3-rtslib-fb: package doesn't ship service unit or init script
Package: python3-rtslib-fb Version: 2.1.66-2 Severity: important Dear Maintainer, I've also posted about this at debian-openst...@lists.debian.org because I'm not 100% sure it is a bug, but after a day my message is not in the list archives so I'm not sure it was actually received (there are no messages in the archive for 2019 at all). The issue I'm experiencing is that after a reboot, all targetcli configuration is gone despite there being a file with the saved desired state under /etc/rtslib-fb-target/saveconfig.json Investigating further with dpkg, targetcli-fb and python3-rtslib-fb seem not to provide any kind of service unit files or init scripts. After issuing targetctl restore manually, the desired state is restored. Am I missing something here? Is this intentional? The man page for targetcli explicitly states that distributions should ship service files to restore configuration after a reboot. I've also noticed that this package does ship with rtslib-fb-targetctl.service on debian stretch. So I'm inclined to believe this is a bug, after all. Versions (running debian buster/unstable): # dpkg -l | egrep 'rtslib|target' ii python-rtslib-fb-doc 2.1.66-2 ii python3-rtslib-fb2.1.66-2 ii targetcli-fb 2.1.48-2 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/32 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 /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-rtslib-fb depends on: ii python3 3.7.2-1 ii python3-pyudev 0.21.0-1 ii python3-six 1.12.0-1 python3-rtslib-fb recommends no packages. Versions of packages python3-rtslib-fb suggests: ii python-rtslib-fb-doc 2.1.66-2 -- no debconf information
Bug#926942: ifupdown.sh: --may-exist missing for OVSBond
Package: openvswitch-switch Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-11 Severity: important Tags: patch upstream Dear Maintainer, The --may-exist option is missing for the invocation of ovs_vsctl when creating an OVSBond fake interface. This results in an error (upon booting for example, in case the interface is already brought up due to an entry in OVS database) that makes the networking service fail. I have submitted a patch upstream to https://github.com/openvswitch/ovs which was merged with commit acd9a7fae16a6b3d76646ef65e4c26c4b8cd4816. Would you consider including this patch with a future release of this package? Thank you. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/32 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 /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages openvswitch-switch depends on: ii kmod26-1 ii lsb-base10.2019031300 ii netbase 5.6 ii openvswitch-common 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-11 ii procps 2:3.3.15-2 ii python 2.7.16-1 ii uuid-runtime2.33.1-0.1 openvswitch-switch recommends no packages. openvswitch-switch suggests no packages. -- no debconf information
Bug#865967: backport to stretch
Is it possible to back port this fix to debian stretch, stretch backports? As far as I can tell, this package simply won't work in Debian Stretch if you are using the postgres backend (maybe it works with other backends, not entirely sure). Thanks for your work packaging it! jamie signature.asc Description: OpenPGP digital signature
Bug#926941: backuppc: Web GUI does not work, error client denied by server configuration
Package: backuppc Version: 3.3.2-2 Severity: normal Dear Maintainer, Freshly installed BackupPC on this Buster host. Could not connect with browser to http://hostname/backuppc. Error in /var/log/apache/error.log: [Fri Apr 12 15:30:50.876517 2019] [authz_core:error] [pid 786:tid 139650751440640] [client 192.168.42.114:52654] AH01630: client denied by server configuration: /usr/share/backuppc/cgi-bin/ [Fri Apr 12 16:16:18.087116 2019] [authz_core:error] [pid 786:tid 139650509231872] [client 192.168.42.114:52718] AH01630: client denied by server configuration: /usr/share/backuppc/cgi-bin/ [Fri Apr 12 16:17:10.254008 2019] [authz_core:error] [pid 790:tid 139650643515136] [client 192.168.42.114:52732] AH01630: client denied by server configuration: /usr/share/backuppc/cgi-bin/index.cgi [Fri Apr 12 16:17:17.668545 2019] [authz_core:error] [pid 786:tid 139650593158912] [client 192.168.42.114:52734] AH01630: client denied by server configuration: /usr/share/backuppc/cgi-bin/ Fixed this by adding to /etc/backuppc/apache.conf require valid-user after AuthName "BackupPC Admin" Now it works. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.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 backuppc depends on: ii adduser 3.118 ii apache2 [httpd] 2.4.38-3 ii apache2-utils2.4.38-3 ii bzip21.0.6-9 ii debconf [debconf-2.0]1.5.71 ii exim4-daemon-light [mail-transport-agent]4.92-2 ii iputils-ping 3:20180629-2 ii libarchive-zip-perl 1.64-1 ii libc62.28-8 ii libcgi-pm-perl 4.40-1 pn libdigest-md5-perl pn libio-compress-perl | libcompress-zlib-perl ii libsocket6-perl 0.29-1+b1 ii libtime-parsedate-perl 2015.103-3 ii libwww-perl 6.36-1 ii lsb-base 10.2019031300 ii perl 5.28.1-6 ii ucf 3.0038+nmu1 Versions of packages backuppc recommends: ii libfile-rsyncp-perl 0.74-2.1+b5 ii libio-dirent-perl0.05-1+b7 ii openssh-client [ssh-client] 1:7.9p1-9 ii rrdtool 1.7.1-1 ii rsync3.1.3-6 ii samba-common-bin 2:4.9.5+dfsg-3 ii smbclient2:4.9.5+dfsg-3 Versions of packages backuppc suggests: pn certbot | acme-tiny | acmetool | dehydrated | lacme | lecm | lego pn par2 pn w3m | www-browser -- Configuration Files: /etc/backuppc/apache.conf changed: Alias /backuppc /usr/share/backuppc/cgi-bin/ AllowOverride None # Uncomment the line below to ensure that nobody can sniff important # info from network traffic during editing of the BackupPC config or # when browsing/restoring backups. # Requires that you have your webserver set up for SSL (https) access. #SSLRequireSSL Options ExecCGI FollowSymlinks AddHandler cgi-script .cgi DirectoryIndex index.cgi AuthUserFile /etc/backuppc/htpasswd AuthType basic AuthName "BackupPC admin" require valid-user # Comment out this line once you have setup HTTPS and uncommented SSLRequireSSL Require local # This line ensures that only authenticated users may access your backups Require valid-user /etc/backuppc/hosts changed: hostdhcpusermoreUsers # <--- do not edit this line localhost 0 backuppc localhost 0 backuppc peli0 backuppc -- debconf information: * backuppc/configuration-note: backuppc/restart-webserver: true * backuppc/reconfigure-webserver: apache2 -- Tapio Lehtonen tapio.lehto...@iki.fi http://www.iki.fi/tapio.lehtonen signature.asc Description: PGP signature
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
severity 926932 important thanks Sorry, didn't spot the out of memory message. I'm making this not RC for now. I'd like to investigate this a little bit more on my side. Thanks a lot.
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
On Fri, 12 Apr 2019 11:51:53 +, Santiago Vila wrote: > I tried to build this package in buster but it failed: > Out of memory! > Out of memory! > # Looks like your test exited with 1 just after 25. > t/40server_prepare.t > 1..31 > ok 1 - connecting > ok 2 - making slate clean > ok 3 - creating table > ok 4 - loading data > ok 5 > ok 6 > ok 7 - binding parameter > ok 8 - fetching data > ok 9 > ok 10 > ok 11 - cleaning up > ok 12 - making slate clean > ok 13 - creating test table > ok 14 > ok 15 - binding int > ok 16 - binding smallint > ok 17 - binding tinyint > ok 18 - binding bigint > ok 19 - inserting data > ok 20 > ok 21 - cleaning up > ok 22 - making slate clean > ok 23 - creating test table > ok 24 > ok 25 - insert t3 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 6/31 subtests > Out of memory! > Out of memory! > # Looks like your test exited with 1 just after 16. > t/40server_prepare_crash.t .. > 1..39 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok 16 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 23/39 subtests > Out of memory! > Out of memory! > # Tests were run but no plan was declared and done_testing() was not seen. > # Looks like your test exited with 1 just after 106. > t/50chopblanks.t > ok 1 - drop table if exists dbd_mysql_t50chopblanks > ok 2 - create table dbd_mysql_t50chopblanks > ok 3 > ok 4 > ok 5 - insert into dbd_mysql_t50chopblanks values (1 , '', '', '', '', '', > '', '', '', '') > ok 6 - select c_varchar, c_text, c_tinytext, c_mediumtext, c_longtext, > b_blob, b_tinyblob, b_mediumblob, b_longblob from dbd_mysql_t50chopblanks > where id = 1 > ok 7 > ok 8 - NoChopBlanks: c_varchar should not have blanks chopped > ok 9 - NoChopBlanks: c_text should not have blanks chopped > ok 10 - NoChopBlanks: c_tinytext should not have blanks chopped > ok 11 - NoChopBlanks: c_mediumtext should not have blanks chopped > ok 12 - NoChopBlanks: c_longtext should not have blanks chopped > ok 13 - NoChopBlanks: b_blob should not have blanks chopped > ok 14 - NoChopBlanks: b_tinyblob should not have blanks chopped > ok 15 - NoChopBlanks: b_mediumblob should not have blanks chopped > ok 16 - NoChopBlanks: b_longblob should not have blanks chopped > ok 17 > ok 18 > ok 19 - ChopBlanks: c_varchar should have blanks chopped > ok 20 - ChopBlanks: c_text should have blanks chopped > ok 21 - ChopBlanks: c_tinytext should have blanks chopped > ok 22 - ChopBlanks: c_mediumtext should have blanks chopped > ok 23 - ChopBlanks: c_longtext should have blanks chopped > ok 24 - ChopBlanks: b_blob should not have blanks chopped > ok 25 - ChopBlanks: b_tinyblob should not have blanks chopped > ok 26 - ChopBlanks: b_mediumblob should not have blanks chopped > ok 27 - ChopBlanks: b_longblob should not have blanks chopped > ok 28 - insert into dbd_mysql_t50chopblanks values (2 , ' ', ' ', ' ', ' ', ' > ', ' ', ' ', ' ', ' ') > ok 29 - select c_varchar, c_text, c_tinytext, c_mediumtext, c_longtext, > b_blob, b_tinyblob, b_mediumblob, b_longblob from dbd_mysql_t50chopblanks > where id = 2 > ok 30 > ok 31 - NoChopBlanks: c_varchar should not have blanks chopped > ok 32 - NoChopBlanks: c_text should not have blanks chopped > ok 33 - NoChopBlanks: c_tinytext should not have blanks chopped > ok 34 - NoChopBlanks: c_mediumtext should not have blanks chopped > ok 35 - NoChopBlanks: c_longtext should not have blanks chopped > ok 36 - NoChopBlanks: b_blob should not have blanks chopped > ok 37 - NoChopBlanks: b_tinyblob should not have blanks chopped > ok 38 - NoChopBlanks: b_mediumblob should not have blanks chopped > ok 39 - NoChopBlanks: b_longblob should not have blanks chopped > ok 40 > ok 41 > ok 42 - ChopBlanks: c_varchar should have blanks chopped > ok 43 - ChopBlanks: c_text should have blanks chopped > ok 44 - ChopBlanks: c_tinytext should have blanks chopped > ok 45 - ChopBlanks: c_mediumtext should have blanks chopped > ok 46 - ChopBlanks: c_longtext should have blanks chopped > ok 47 - ChopBlanks: b_blob should not have blanks chopped > ok 48 - ChopBlanks: b_tinyblob should not have blanks chopped > ok 49 - ChopBlanks: b_mediumblob should not have blanks chopped > ok 50 - ChopBlanks: b_longblob should not have blanks chopped > ok 51 - insert into dbd_mysql_t50chopblanks values (3 , ' a b c ', ' a b c ', > ' a b c ', ' a b c ', ' a b c ', ' a b c ', ' a b c ', ' a b c ', ' a b c ') > ok 52 - select c_varchar, c_text, c_tinytext, c_mediumtext, c_longtext, > b_blob, b_tinyblob, b_mediumblob, b_longblob from dbd_mysql_t50chopblanks > where id = 3 > ok 53 > ok 54 - NoChopBlanks: c_varchar should not have blanks chopped > ok 55 - NoChopBlanks: c_text should not have blanks chopped > ok 56 - NoChopBlanks: c_tinytext should not have blanks chopped > ok 57 - NoChopBlanks: c_mediumtext should not have blanks chopped > ok 58 - NoChopBlanks: c_longtext should not have bla
Bug#880659: [stunnel4] still random segfaults - kernel reports illegal instruction
Hi, i am still seeing regular illegal instruction crashes in stunnel4 - Setup hasnt changed from 2017. Version is 3:5.39-2 It doesnt look trustworthy when a crypto application which is public internet facing regularly crashes with illegal instruction. [Sun Mar 24 23:41:01 2019] traps: stunnel4[22548] trap invalid opcode ip:7fdf2a82fc43 sp:7fdf29483af8 error:0 [Sun Mar 24 23:41:01 2019] in libpthread-2.24.so[7fdf2a823000+18000] [Sat Mar 30 23:53:23 2019] traps: stunnel4[20823] trap invalid opcode ip:7f113cc66c43 sp:7f113b8baa98 error:0 [Sat Mar 30 23:53:23 2019] in libpthread-2.24.so[7f113cc5a000+18000] [Sun Mar 31 06:30:01 2019] traps: stunnel4[32449] trap invalid opcode ip:7fe43fda7c43 sp:7fe43e9fba68 error:0 [Sun Mar 31 06:30:01 2019] in libpthread-2.24.so[7fe43fd9b000+18000] [Wed Apr 10 21:45:50 2019] traps: stunnel4[13859] trap invalid opcode ip:7f2381e09c43 sp:7f2380a5db38 error:0 [Wed Apr 10 21:45:50 2019] in libpthread-2.24.so[7f2381dfd000+18000] Flo -- Florian Lohoff f...@zz.de UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away signature.asc Description: PGP signature
Bug#926940: unblock: watson/1.6.0-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package watson[0]
Version 1.6.0-6 fixes one Build-Depends and one upstream
test. It is a good fix for reproducibility[1]. The package
is "13 days old (2 needed)"
[0] - https://tracker.debian.org/pkg/watson
[1] - https://tests.reproducible-builds.org/debian/rb-pkg/watson.html
The fix in watson/tests/test_watson.py file is:
-@pytest.mark.datafiles(
-TEST_FIXTURE_DIR / 'frames-with-conflict',
-)
-def test_merge_report(watson, datafiles):
+#@pytest.mark.datafiles(
+#TEST_FIXTURE_DIR / 'frames-with-conflict',
+#)
+def test_merge_report(watson): # , datafiles):
# Get report
watson.frames.add('foo', 4000, 4015, id='1', updated_at=4015)
watson.frames.add('bar', 4020, 4045, id='2', updated_at=4045)
conflicting, merging = watson.merge_report(
-str(datafiles) + '/frames-with-conflict')
+TEST_FIXTURE_DIR + '/frames-with-conflict')
Attached you will find the 'debdiff watson_1.6.0-5.dsc watson_1.6.0-6.dsc'
compressed file.
Regards,
Herbert
watson_deb_revision_5_to_6.debdiff.gz
Description: application/gzip
Bug#926939: z3: Please move the package as team maintained with a VCS
Source: z3 Severity: wishlist Hello It would be great to move z3 debian packaging under a repo and make it team maintained. pkg-llvm could be a place as it is used by llvm/clang upstream (not yet in debian). https://salsa.debian.org/pkg-llvm-team I can take care of the move if you want. Sylvestre -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'buildd-unstable'), (500, 'stable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/28 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#926938: reboot hangs, hung task, ohci_urb_dequeue
Package: src:linux Version: 4.9.144-3.1 I have two machines in the Xen Project CI lab which fail to reboot using the stock stretch kernel. They both hang, printing a message like the one belwo to their serial console. The appearance of a new usb device during kernel reboot is rather odd. Full logs http://logs.test-lab.xenproject.org/osstest/logs/134652/test-amd64-amd64-xl-multivcpu/info.html http://logs.test-lab.xenproject.org/osstest/logs/134652/test-amd64-amd64-xl-multivcpu/serial-joubertin0.log http://logs.test-lab.xenproject.org/osstest/logs/134651/test-xtf-amd64-amd64-1/info.html http://logs.test-lab.xenproject.org/osstest/logs/134651/test-xtf-amd64-amd64-1/serial-merlot1.log Look at or near the end of each serial log. The "client 0x55dcddf30100 connected" messages are a result of my CI system deciding that the host isn't going reboot, and making connections to the serial concentrator to try to collect debug information. BTW, my Citrix email address has an often-malfunctioning spamfilter. Sadly I have not been able to get corporiate IT to fix it. Please CC ijack...@chiark.greenend.org.uk (especially if you get bounces). If ijackson@chiark bounces, talk to postmaster@chiark and I will fix my personal spamfilter so it lets you through. Sorry for any inconvenience. If you would like me to test any workaround or something, please let me know. Thanks, Ian. Apr 12 01:23:40.224056 Unmounting local filesystems...done. Apr 12 01:23:40.224074 [ 523.410355] EXT4-fs (dm-1): re-mounted. Opts: (null) Apr 12 01:23:40.260056 Will now restart. Apr 12 01:23:40.464036 [ 526.126589] kvm: exiting hardware virtualization Apr 12 01:23:42.976057 [ 599.629542] usb 3-2: new full-speed USB device number 2 using ohci-pci Apr 12 01:24:56.488055 [ 741.973018] INFO: task kworker/0:2:370 blocked for more than 120 seconds. Apr 12 01:27:18.840086 [ 741.980517] Not tainted 4.9.0-8-amd64 #1 Debian 4.9.144-3.1 Apr 12 01:27:18.840111 [ 741.988437] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 12 01:27:18.852090 [ 741.997540] kworker/0:2 D0 370 2 0x Apr 12 01:27:18.864081 [ 742.004100] Workqueue: usb_hub_wq hub_event [usbcore] Apr 12 01:27:18.864102 [ 742.009689] 9d7431996580 9d7231d68100 9d7237c18980 Apr 12 01:27:18.876085 [ 742.017972] 9d722ac85080 c2a742443ba0 be2144b9 c03241c2 Apr 12 01:27:18.876110 [ 742.026553] 00ff9d723244d600 9d7237c18980 c02a40b0 9d7231d68100 Apr 12 01:27:18.888092 [ 742.035477] Call Trace: Apr 12 01:27:18.888109 [ 742.038273] [] ? __schedule+0x239/0x6f0 Apr 12 01:27:18.900084 [ 742.044656] [] ? ohci_urb_dequeue+0x72/0xa0 [ohci_hcd] Apr 12 01:27:18.912078 [ 742.052929] [] ? schedule+0x32/0x80 Apr 12 01:27:18.912100 [ 742.058956] [] ? usb_kill_urb+0x86/0xc0 [usbcore] Apr 12 01:27:18.924088 [ 742.066682] [] ? prepare_to_wait_event+0xf0/0xf0 Apr 12 01:27:18.924110 [ 742.074339] [] ? usb_start_wait_urb+0xe2/0x170 [usbcore] Apr 12 01:27:18.936094 [ 742.082688] [] ? usb_control_msg+0xdd/0x140 [usbcore] Apr 12 01:27:18.948080 [ 742.090724] [] ? hub_port_init+0x323/0xbd0 [usbcore] Apr 12 01:27:18.960073 [ 742.098831] [] ? usb_alloc_dev+0x1e2/0x300 [usbcore] Apr 12 01:27:18.960098 [ 742.106802] [] ? hub_event+0xb5d/0x15c0 [usbcore] Apr 12 01:27:18.972083 [ 742.114258] [] ? process_one_work+0x18a/0x430 Apr 12 01:27:18.972106 [ 742.121552] [] ? worker_thread+0x4d/0x490 Apr 12 01:27:18.984084 [ 742.128767] [] ? process_one_work+0x430/0x430 Apr 12 01:27:18.996072 [ 742.136056] [] ? kthread+0xd9/0xf0 Apr 12 01:27:18.996093 [ 742.142505] [] ? kthread_park+0x60/0x60 Apr 12 01:27:19.008069 [ 742.149159] [] ? ret_from_fork+0x44/0x70 Apr 12 01:27:19.008091 [ 864.055852] INFO: task kworker/0:2:370 blocked for more than 120 seconds. Apr 12 01:29:20.920082 [ 864.063321] Not tainted 4.9.0-8-amd64 #1 Debian 4.9.144-3.1 Apr 12 01:29:20.932081 [ 864.071672] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 12 01:29:20.944079 [ 864.080284] kworker/0:2 D0 370 2 0x Apr 12 01:29:20.944100 [ 864.087479] Workqueue: usb_hub_wq hub_event [usbcore] Apr 12 01:29:20.956081 [ 864.093070] 9d7431996580 9d7231d68100 9d7237c18980 Apr 12 01:29:20.968086 [ 864.102238] 9d722ac85080 c2a742443ba0 be2144b9 c03241c2 Apr 12 01:29:20.968110 [ 864.112078] 00ff9d723244d600 9d7237c18980 c02a40b0 9d7231d68100 Apr 12 01:29:20.980083 [ 864.121397] Call Trace: Apr 12 01:29:20.980100 [ 864.124094] [] ? __schedule+0x239/0x6f0 Apr 12 01:29:20.992082 [ 864.131348] [] ? ohci_urb_dequeue+0x72/0xa0 [ohci_hcd] Apr 12 01:29:21.004079 [ 864.139310] [] ? schedule+0x32/0x80 Apr 12 01:29:21.004099 [ 864.145826] [] ? usb_kill_urb+0x86/0xc0 [usbcore] Apr 12 01:29:21.016080 [ 864.153651] [] ? prepare_to_wait_ev
Bug#926475: ITP: dlt-viewer -- Viewer for GENIVI DLT traces
I would gladly help in maintaining/uploading that. I've tried making a package of it, but I am getting some compilation issues and my knowledge of that build process is not good enough to fix them on my own. -- Best regards, Aigars Mahinovsmailto:aigar...@debian.org #--# | .''`.Debian GNU/Linux (http://www.debian.org)| | : :' : Latvian Open Source Assoc. (http://www.laka.lv) | | `. `'Linux Administration and Free Software Consulting | | `- (http://www.aiteki.com) | #--#
Bug#926937: unblock: tdbcmysql/1.1.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package tdbcmysql
tdbcmysql version blocks mariadb-10.3 transition because depends on a no more
built version of libmariadbclient
diff -Nru tdbcmysql-1.1.0/debian/changelog tdbcmysql-1.1.0/debian/changelog
--- tdbcmysql-1.1.0/debian/changelog2018-10-20 12:38:45.0 +0200
+++ tdbcmysql-1.1.0/debian/changelog2019-04-11 12:36:26.0 +0200
@@ -1,3 +1,10 @@
+tdbcmysql (1.1.0-2) unstable; urgency=medium
+
+ * Add libmariadb3 to the dependencies list, and load it during [package
+require] if it's available (closes: #926628).
+
+ -- Massimo Manghi Thu, 11 Apr 2019 12:36:26 +0200
+
tdbcmysql (1.1.0-1) unstable; urgency=medium
* New upstream release
diff -Nru tdbcmysql-1.1.0/debian/control tdbcmysql-1.1.0/debian/control
--- tdbcmysql-1.1.0/debian/control 2018-10-20 12:38:45.0 +0200
+++ tdbcmysql-1.1.0/debian/control 2019-04-11 12:34:23.0 +0200
@@ -2,14 +2,14 @@
Section: libs
Priority: optional
Maintainer: Massimo Manghi
-Build-Depends: debhelper (>=9), tcl8.6-dev, tcl8.6-tdbc (>=1.0.5~),
libmariadbclient18 | libmysqlclient18 | libmysqlclient20
+Build-Depends: debhelper (>=9), tcl8.6-dev, tcl8.6-tdbc (>=1.0.5~),
libmariadb3 | libmariadbclient18 | libmysqlclient18 | libmysqlclient20
Standards-Version: 4.2.1
Rules-Requires-Root: binary-targets
Homepage: http://core.tcl.tk/tdbcmysql
Package: tcl8.6-tdbc-mysql
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, tcl8.6, tcl8.6-tdbc (>=1.0.5),
libmariadbclient18 | libmysqlclient18 | libmysqlclient20
+Depends: ${shlibs:Depends}, ${misc:Depends}, tcl8.6, tcl8.6-tdbc (>=1.0.5),
libmariadb3 | libmariadbclient18 | libmysqlclient18 | libmysqlclient20
Description: Tcl Database Connectivity
Tdbc is an interface standard for SQL databases and connectivity that aims to
make it easy to write portable and secure Tcl scripts that access SQL
diff -Nru tdbcmysql-1.1.0/debian/patches/mariadb-client-support
tdbcmysql-1.1.0/debian/patches/mariadb-client-support
--- tdbcmysql-1.1.0/debian/patches/mariadb-client-support 2018-10-20
12:38:45.0 +0200
+++ tdbcmysql-1.1.0/debian/patches/mariadb-client-support 2019-04-11
12:34:23.0 +0200
@@ -10,12 +10,20 @@
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/generic/mysqlStubInit.c
+++ b/generic/mysqlStubInit.c
-@@ -37,7 +37,7 @@
+@@ -37,14 +37,14 @@
static const char *const mysqlStubLibNames[] = {
/* @LIBNAMES@: DO NOT EDIT THESE NAMES */
-"mysqlclient_r", "mysqlclient", "mysql", NULL
-+"mysqlclient_r", "mysqlclient", "mysql", "mariadbclient", NULL
++"mysqlclient_r", "mysqlclient", "mysql", "mariadb", "mariadbclient", NULL
/* @END@ */
};
+ /* ABI Version numbers of the MySQL API that we can cope with */
+
+ static const char mysqlSuffixes[][4] = {
+-"", ".20", ".18", ".17", ".16", ".15"
++"", ".20", ".18", ".17", ".16", ".15", ".3"
+ };
+
+ /* Names of the functions that we need from MySQL */
diff -Nru tdbcmysql-1.1.0/debian/patches/series
tdbcmysql-1.1.0/debian/patches/series
--- tdbcmysql-1.1.0/debian/patches/series 2018-10-20 12:38:45.0
+0200
+++ tdbcmysql-1.1.0/debian/patches/series 2019-04-11 12:34:23.0
+0200
@@ -1,3 +1,3 @@
-mariadb-client-support
addlibmysqlclient20
numeric-expression-expected
+mariadb-client-support
unblock tdbcmysql/1.1.0-2
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (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
Bug#926936: udev: systemd-udevd PID file name produces false positive with rkhunter for XORDDOS malware
Package: udev Version: 241-3 Severity: minor Dear Maintainer, On some of my systems, I use the package 'rkhunter', which seeks to detect (via daily cron job) and report on (via E-mail to the primary local user) the presence of possible rootkits on the system. For some time now, I have been getting daily mails from rkhunter with the following message: Warning: Checking for possible rootkit files and directories [ Warning ] Found file '/var/run/udev.pid'. Possible rootkit: xorddos component which appear to be false-positive reports about a possible infection by the XORDDOS malware. Searching online seems to indicate that this PID-file name is also (quite legitimately) used by systemd-udevd, which indeed is running on the system where these reports have been appearing. These false positives havve been mentioned online by a few other people, including an inquiry in the rkhunter forums as to whether this is really a false positive, and a discussion in some gentoo context. It has also been filed in Devuan against eudev (https://bugs.devuan.org/cgi/bugreport.cgi?bug=292), where the suggestion is to fix the false positive by naming the PID file 'eudev.pid' instead, although I have not found any previous reports about it in Debian. The dates of these discussions seem to indicate that the false positive seems to have first started manifesting in February of 2019. The solution of using 'eudev.pid' is obviously not suitable for udev itself, but a name like 'udevd.pid' or 'systemd-udevd.pid' seems like it might achieve the same goal. It is possible to whitelist this filename in rkhunter's configuration settings, but doing so does - however mildly - increase the likelihood that if this malware does get a foothold on the system, rkhunter will not detect it. Thus, a way to remove this false positive from the udev side would be preferable. This malware, and its use of this filename, seems to date back at least to 2015. I do not know when systemd-udevd came to be included in the (Debian) standard udev setup, or when it started to use this filename, but it seems possible to me that the malware may actually have gotten there first. I would like to request that a change be made so that the genuine, legitimate systemd-udevd process does not use the same PID-file name as has historically been used by this malware, and therefore this false positive does not occur. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_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 /bin/dash Init: sysvinit (via /sbin/init) Versions of packages udev depends on: ii adduser 3.118 ii dpkg 1.19.6 ii libacl1 2.2.53-4 ii libblkid12.33.1-0.1 ii libc62.28-8 ii libkmod2 26-1 ii libselinux1 2.8-1+b1 ii libudev1 241-3 ii lsb-base 10.2019031300 ii util-linux 2.33.1-0.1 udev recommends no packages. udev suggests no packages. Versions of packages udev is related to: pn systemd -- debconf information: udev/new_kernel_needed: false udev/title/upgrade: udev/sysfs_deprecated_incompatibility: udev/reboot_needed: P: /devices/LNXSYSTM:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00 E: SUBSYSTEM=acpi E: MODALIAS=acpi:LNXSYSTM: E: USEC_INITIALIZED=22890814 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation P: /devices/LNXSYSTM:00/LNXCPU:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00 E: SUBSYSTEM=acpi E: MODALIAS=acpi:LNXCPU: E: USEC_INITIALIZED=22913013 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation P: /devices/LNXSYSTM:00/LNXCPU:01 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01 E: SUBSYSTEM=acpi E: MODALIAS=acpi:LNXCPU: E: USEC_INITIALIZED=23127948 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation P: /devices/LNXSYSTM:00/LNXCPU:02 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02 E: SUBSYSTEM=acpi E: MODALIAS=acpi:LNXCPU: E: USEC_INITIALIZED=23128420 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation P: /devices/LNXSYSTM:00/LNXCPU:03 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03 E: SUBSYSTEM=acpi E: MODALIAS=acpi:LNXCPU: E: USEC_INITIALIZED=23127945 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation P: /devices/LNXSYSTM:00/LNXPWRBN:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00 E: SUBSYSTEM=acpi E: DRIVER=button E: MODALIAS=acpi:LNXPWRBN: E: USEC_INITIALIZED=23128553 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 E: SUBSYSTEM=input E: PRODUCT=19/0/1/0 E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PROP=0 E: EV=3 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: USEC_INITIALIZED=26171813 E:
Bug#926876: unblock: chiark-utils/6.0.4
Control: tags -1 - moreinfo
Niels Thykier writes ("Re: Bug#926876: unblock: chiark-utils/6.0.4"):
> Please go ahead with the upload and remove the moreinfo tag when it is
> ready to be unblocked.
Done, and the buildds have finished. Thanks.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#926935: arpack: FTBFS (does not honor parallel=n in DEB_BUILD_OPTIONS)
Package: src:arpack Version: 3.7.0-1 Severity: serious Tags: ftbfs patch Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:12: installing 'build-aux/compile' configure.ac:17: installing 'build-aux/config.guess' [... snipped ...] make[4]: Leaving directory '/<>/PARPACK/SRC/MPI' Making check in . make[4]: Entering directory '/<>/PARPACK' make[4]: Nothing to be done for 'check-am'. make[4]: Leaving directory '/<>/PARPACK' Making check in TESTS/MPI make[4]: Entering directory '/<>/PARPACK/TESTS/MPI' make issue46 make[5]: Entering directory '/<>/PARPACK/TESTS/MPI' mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o issue46.o issue46.f /bin/bash ../../../libtool --tag=F77 --mode=link mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wl,-z,relro -o issue46 issue46.o ../../../PARPACK/SRC/MPI/libparpack.la -llapack -lblas libtool: link: mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wl,-z -Wl,relro -o .libs/issue46 issue46.o ../../../PARPACK/SRC/MPI/.libs/libparpack.so -llapack -lblas make[5]: Leaving directory '/<>/PARPACK/TESTS/MPI' make check-TESTS make[5]: Entering directory '/<>/PARPACK/TESTS/MPI' make[6]: Entering directory '/<>/PARPACK/TESTS/MPI' FAIL: issue46 Testsuite summary for ARPACK-NG 3.7.0 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See PARPACK/TESTS/MPI/test-suite.log Please report to https://github.com/opencollab/arpack-ng/issues/ make[6]: *** [Makefile:830: test-suite.log] Error 1 make[6]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[5]: *** [Makefile:938: check-TESTS] Error 2 make[5]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[4]: *** [Makefile:1026: check-am] Error 2 make[4]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[3]: *** [Makefile:387: check-recursive] Error 1 make[3]: Leaving directory '/<>/PARPACK' make[2]: *** [Makefile:509: check-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 This used to work ok in all my autobuilders in version 3.5.0+real-2, but it started to fail in some of them in version 3.6.3-1. I've put a bunch of build logs here: https://people.debian.org/~sanvila/build-logs/arpack/ The problem seems to be that the Makefiles wrongly assume that the system has at least 2 CPUs, which may or may not be the case. A simple solution that seems to work is to set 'LOG_FLAGS = -n 1' in both PARPACK/EXAMPLES/MPI/Makefile.am and PARPACK/TESTS/MPI/Makefile.am, but it would be even better to honor parallel=n setting in DEB_BUILD_OPTIONS when there is one, as in the patch below. I did not find a simple way to reproduce this in any system. The usual recipe is to try "taskset -c 0 dpkg-buildpackage" but this does not seem to work here, so if you need a test machine to reproduce the failure please contact me privately and I will gladly provide one. Thanks. --- a/PARPACK/EXAMPLES/MPI/Makefile.am +++ b/PARPACK/EXAMPLES/MPI/Makefile.am @@ -12,7 +12,7 @@ check_PROGRAMS = $(SNDRV) $(DNDRV) $(SSDRV) $(DSDRV) $(CNDRV) $(ZNDRV) # Run MPI tests with "mpirun -n 2" LOG_COMPILER = mpirun -LOG_FLAGS = -n 2 +LOG_FLAGS = -n $(NUMJOBS) TESTS = $(check_PROGRAMS) --- a/PARPACK/TESTS/MPI/Makefile.am +++ b/PARPACK/TESTS/MPI/Makefile.am @@ -3,7 +3,7 @@ LDADD = $(top_builddir)/PARPACK/SRC/MPI/libparpack$(LIBSUFFIX).la $(LAPACK_LIBS) # Run MPI tests with "mpirun -n 2" LOG_COMPILER = mpirun -LOG_FLAGS = -n 2 +LOG_FLAGS = -n $(NUMJOBS) SISS = issue46 --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,12 @@ %: dh $@ +export NUMJOBS = $(shell nproc) + +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) +endif + override_dh_auto_configure: # Enforce generic BLAS (to avoid tying to ATLAS
Bug#926934: flash-kernel: /sbin/installkernel fails when flash-kernel is installed
Package: flash-kernel
Version: 3.98pureos+librem5.2~1175.gbpd159a8
Severity: normal
Dear Maintainer,
The /sbin/installkernel script fails when flash-kernel is installed:
$ sudo make install
arch/arm64/Makefile:40: LSE atomics not supported by binutils
arch/arm64/Makefile:48: Detected assembler with broken .inst; disassembly will
be unreliable
/bin/bash ./arch/arm64/boot/install.sh 4.18.11-00448-ge4cb08275a83 \
arch/arm64/boot/Image System.map "/boot"
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
4.18.11-00448-ge4cb08275a83 /boot/vmlinuz-4.18.11-00448-ge4cb08275a83
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
4.18.11-00448-ge4cb08275a83 /boot/vmlinuz-4.18.11-00448-ge4cb08275a83
update-initramfs: Generating /boot/initrd.img-4.18.11-00448-ge4cb08275a83
Using DTB: librem5-evk.dtb
Couldn't find DTB librem5-evk.dtb in
/usr/lib/linux-image-4.18.11-00448-ge4cb08275a83 or /etc/flash-kernel/dtbs
Installing into /boot/dtbs/4.18.11-00448-ge4cb08275a83/./librem5-evk.dtb
cp: cannot stat '': No such file or directory
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
make[1]: *** [arch/arm64/boot/Makefile:40: install] Error 1
make: *** [arch/arm64/Makefile:127: install] Error 2
When run from "make install" in a kernel directory, the last thing
installkernel does is call run-parts on /etc/kernel/postinst.d:
run-parts --verbose --exit-on-error --arg="$ver"
--arg="$dir/$img_dest-$ver" \
/etc/kernel/postinst.d
The postinst.d script for initramfs-tools executes update-initramfs
which in turn calls run-parts on /etc/initramfs/post-update.d:
run-parts --arg=${version} --arg=${initramfs} \
/etc/initramfs/post-update.d/
The flash-kernel package installs a hook script in
/etc/initramfs/post-update.d which executes flash-kernel. The
flash-kernel script then tries to install the kernel's .dtb files,
assuming the hook script is being run during the installation of a
kernel package. The expected .dtb files are not present and so the
execution fails causing installkernel to error out.
There is a conflict: installkernel assumes the /etc/kernel/postinst.d
hook scripts can be run outside of a kernel package installation but
flash-kernel's /etc/initramfs/post-update.d hook script assumes that
it will only be run during a kernel package installation.
Regards,
Bob Ham
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 4.18.11-gee84b30c (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default
locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages flash-kernel depends on:
ii debconf [debconf-2.0] 1.5.71
ii devio 1.2-1.2+b1
ii initramfs-tools0.133
ii linux-base 4.5
ii mtd-utils 1:2.0.1-1
ii ucf3.0038+nmu1
Versions of packages flash-kernel recommends:
ii u-boot-tools 2019.01+dfsg-3
flash-kernel suggests no packages.
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
flash-kernel/linux_cmdline: quiet
Bug#926933: fetch-ldap-cert fails against LDAP cert on jessie tjener
Package: debian-edu-config Version: 2.10.64 Severity: important I just tested a Debian Edu 10 installation against a Debian Edu 8 TJENER. The LDAP certificate on the jessie TJENER had been created wrongly (subject: CN=localhost, issuer: CN=localhost). The new gnutls-cli implemenation in fetch-ldap-cert now chokes on that with this error: ``` gnutls-cli --x509cafile /etc/ssl/certs/debian-edu-bundle.crt --save-cert=/etc/ssl/certs/debian-edu-server.crt.new ldap.intern [...] Status: The certificate is NOT trusted. The certificate issuer is unknown. The name in the certificate does not match the expected. ``` This probably needs to be addressed by documentation. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpbptasUuwv0.pgp Description: Digitale PGP-Signatur
Bug#926932: libdbd-mysql-perl: FTBFS (autobuilder hangs)
Package: src:libdbd-mysql-perl
Version: 4.050-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with perl_dbi
dh_update_autotools_config -a
dh_autoreconf -a
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
LC_ALL=C.UTF-8 dh_auto_configure
perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2"
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
-Wl,-z,now"
PLEASE NOTE:
For 'make test' to run properly, you must ensure that the
database user 'buildd' can connect to your MySQL server
and has the proper privileges that these tests require such
as 'drop table', 'create table', 'drop procedure', 'create procedure'
as well as others.
mysql> grant all privileges on test.* to 'buildd'@'localhost' identified by
's3kr1t';
You can also optionally set the user to run 'make test' with:
perl Makefile.PL --testuser=username
mysql_config: unrecognized option '--embedded'
I will use the following settings for compiling and testing:
cflags(mysql_config) = -I/usr/include/mariadb
-I/usr/include/mariadb/mysql
embedded (guessed ) =
ldflags (guessed ) =
libs (mysql_config) = -L/usr/lib/x86_64-linux-gnu/ -lmariadb -lz
-ldl -lm -lpthread -lgnutls
mysql_config (guessed ) = mysql_config
nocatchstderr (default ) = 0
nofoundrows (default ) = 0
nossl (default ) = 0
testdb(default ) = test
testhost (default ) =
testpassword (default ) =
testport (default ) =
testsocket(default ) =
testuser (guessed ) = buildd
To change these settings, see 'perl Makefile.PL --help' and
'perldoc DBD::mysql::INSTALL'.
Checking if libs are available for compiling...
Looks good.
Checking if your kit is complete...
Looks good
Using DBI 1.642 (for perl 5.028001 on x86_64-linux-gnu-thread-multi) installed
in /usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/
Generating a Unix-style Makefile
Writing Makefile for DBD::mysql
Writing MYMETA.yml and MYMETA.json
make[1]: Leaving directory '/<>'
dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
cp lib/DBD/mysql/GetInfo.pm blib/lib/DBD/mysql/GetInfo.pm
cp lib/DBD/mysql.pm blib/lib/DBD/mysql.pm
cp lib/DBD/mysql/INSTALL.pod blib/lib/DBD/mysql/INSTALL.pod
cp lib/Bundle/DBD/mysql.pm blib/lib/Bundle/DBD/mysql.pm
Running Mkbootstrap for mysql ()
chmod 644 "mysql.bs"
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- mysql.bs
blib/arch/auto/DBD/mysql/mysql.bs 644
x86_64-linux-gnu-gcc -c -I/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -DDBD_MYSQL_WITH_SSL -g
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"4.050\"
-DXS_VERSION=\"4.050\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.28/CORE"
dbdimp.c
In file included from /usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/DBIXS.h:38,
from dbdimp.h:20,
from dbdimp.c:15:
/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/dbipport.h:4471: warning:
"WIDEST_UTYPE" redefined
# define WIDEST_UTYPE U64TYPE
In file included from /usr/lib/x86_64-linux-gnu/perl/5.28/CORE/perl.h:2465,
from /usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/DBIXS.h:23,
from dbdimp.h:20,
from dbdimp.c:15:
/usr/lib/x86_64-linux-gnu/perl/5.28/CORE/handy.h:1064: note: this is the
location of the previous definition
# define WIDEST_UTYPE U64
dbdimp.c: In function 'mysql_st_prepare':
dbdimp.c:3207:24: warning: assignment to 'my_bool *' {aka 'char *'} from
incompatible pointer type '_Bool *' [-Wincompatible-pointer-types]
bind->is_null= (_Bool*) &(fbind->is_null);
^
"/usr/bin/perl" -p -e "s/~DRIVER~/mysql/g"
/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI/Driver.xst > mysql.xsi
"/usr/bin/perl" "/usr/share/perl/5.28/ExtUtils/xsubpp" -typemap
'/usr/share/perl/5.28/ExtUtils/typemap' mysql.xs > mysql.xsc
Warning: duplicate function definition 'do' detected in mysql.xs, line 247
Warning: duplicate function definition 'rows' detected in mysql.xs, line 683
mv mysql.xsc mysql.c
x86_64-linux-gnu-gcc -c -I/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/DBI
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -DDBD_MYSQL_WITH_SSL -g
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe
-I/usr/local/include -D_LARG
Bug#926931: unblock: golang-github-go-debos-fakemachine/0.0~git20181105.9316584-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package golang-github-go-debos-fakemachine
Fixes release critical bug which causes package to be unusable
diff -Nru
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog
--- golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog
2018-11-09 10:15:18.0 +0100
+++ golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog
2019-04-12 11:53:04.0 +0200
@@ -1,3 +1,10 @@
+golang-github-go-debos-fakemachine (0.0~git20181105.9316584-2) unstable;
urgency=medium
+
+ * fakemachine: execution fails due to missing shared lib
+(Closes: #924392)
+
+ -- Héctor Orón Martínez Fri, 12 Apr 2019 11:53:04 +0200
+
golang-github-go-debos-fakemachine (0.0~git20181105.9316584-1) unstable;
urgency=medium
* New upstream version 0.0~git20181105.9316584
diff -Nru
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
---
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
1970-01-01 01:00:00.0 +0100
+++
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
2019-04-12 11:47:40.0 +0200
@@ -0,0 +1,25 @@
+From: Sjoerd Simons
+Date: Tue, 5 Mar 2019 10:17:57 +0100
+Subject: Add libresolve.so.2 in the initramfs
+
+busybox in buster depends on libresolve.so.2 so copy it to the
+initramfs; Potentially in future fakemachine should move to
+busybox-static
+
+Signed-off-by: Sjoerd Simons
+---
+ machine.go | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/machine.go b/machine.go
+index 4a9bd83..021ee67 100644
+--- a/machine.go
b/machine.go
+@@ -457,6 +457,7 @@ func (m *Machine) startup(command string, extracontent
[][2]string) (int, error)
+ if mergedUsrSystem() {
+ prefix = "/usr"
+ }
++ w.CopyFile(prefix + "/lib/x86_64-linux-gnu/libresolv.so.2")
+ w.CopyFile(prefix + "/lib/x86_64-linux-gnu/libc.so.6")
+ w.CopyFile(prefix + "/bin/busybox")
+
diff -Nru
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
---
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
1970-01-01 01:00:00.0 +0100
+++
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
2019-04-12 11:47:40.0 +0200
@@ -0,0 +1 @@
+0001-Add-libresolve.so.2-in-the-initramfs.patch
unblock golang-github-go-debos-fakemachine/0.0~git20181105.9316584-2
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf
Kernel: Linux 4.19.0-4-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8),
LANGUAGE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#923476: webkit2gtk: FTBFS when built with parallel=1
On Wed, Apr 10, 2019 at 09:22:33AM +0200, Santiago Vila wrote: > close 923476 2.24.1-1 > retitle 923476 webkit2gtk: FTBFS when built with parallel=1 (No rule to make > target 'JavaScriptCore-4.0.gir', needed by 'WebKit2-4.0.gir') > thanks > > (Note: The retitle merely adds a snippet from the build log to the title set > by Alberto) > > This works ok in the single-cpu systems I've tested, therefore I'm > closing this with the version in unstable. Here's the unblock request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926929 Berto
Bug#926930: joblib: FTBFS (test_nested_parallelism_limit does not always work)
Package: src:joblib
Version: 0.13.0-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=python_distutils --with=python2,python3
dh_update_autotools_config -i -O--buildsystem=python_distutils
dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
dh_auto_build -i -O--buildsystem=python_distutils
dh_auto_build: Please use the third-party "pybuild" build system instead of
python-distutils
dh_auto_build: This feature will be removed in compat 12.
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
[... snipped ...]
joblib/test/test_testing.py::test_check_subprocess_call PASSED
joblib/test/test_testing.py::test_check_subprocess_call_non_matching_regex
PASSED
joblib/test/test_testing.py::test_check_subprocess_call_wrong_command PASSED
joblib/test/test_testing.py::test_check_subprocess_call_non_zero_return_code
PASSED
joblib/test/test_testing.py::test_check_subprocess_call_timeout
/<>/joblib/testing.py:50: UserWarning: Timeout running
['/usr/bin/python2.7', '-c', 'import time\nimport sys\nprint("before sleep on
stdout")\nsys.stdout.flush()\nsys.stderr.write("before sleep on
stderr")\nsys.stderr.flush()\ntime.sleep(1.1)\nprint("process should have be
killed before")\nsys.stdout.flush()']
warnings.warn("Timeout running {}".format(cmd))
PASSED
joblib/test/data/create_numpy_pickle.py::joblib.test.data.create_numpy_pickle.get_joblib_version
PASSED
=== FAILURES ===
_ test_nested_parallelism_limit[loky] __
backend = 'loky'
@with_multiprocessing
@parametrize('backend', ['loky', 'threading'])
def test_nested_parallelism_limit(backend):
with parallel_backend(backend, n_jobs=2):
backend_types_and_levels = _recursive_backend_info()
if cpu_count() == 1:
second_level_backend_type = 'SequentialBackend'
max_level = 1
else:
second_level_backend_type = 'ThreadingBackend'
max_level = 2
top_level_backend_type = backend.title() + 'Backend'
expected_types_and_levels = [
(top_level_backend_type, 0),
(second_level_backend_type, 1),
('SequentialBackend', max_level),
('SequentialBackend', max_level)
]
> assert backend_types_and_levels == expected_types_and_levels
E AssertionError: assert [('LokyBacken...lBackend', 2)] ==
[('LokyBackend...lBackend', 1)]
E At index 1 diff: ('ThreadingBackend', 1) != ('SequentialBackend', 1)
E Full diff:
E [('LokyBackend', 0),
E - ('ThreadingBackend', 1),
E - ('SequentialBackend', 2),
E ?^
E + ('SequentialBackend', 1),...
E
E ...Full output truncated (7 lines hidden), use '-vv' to show
joblib/test/test_parallel.py:1452: AssertionError
___ test_nested_parallelism_limit[threading] ___
backend = 'threading'
@with_multiprocessing
@parametrize('backend', ['loky', 'threading'])
def test_nested_parallelism_limit(backend):
with parallel_backend(backend, n_jobs=2):
backend_types_and_levels = _recursive_backend_info()
if cpu_count() == 1:
second_level_backend_type = 'SequentialBackend'
max_level = 1
else:
second_level_backend_type = 'ThreadingBackend'
max_level = 2
top_level_backend_type = backend.title() + 'Backend'
expected_types_and_levels = [
(top_level_backend_type, 0),
(second_level_backend_type, 1),
('SequentialBackend', max_level),
('SequentialBackend', max_level)
]
> assert backend_types_and_levels == expected_types_and_levels
E AssertionError: assert [('ThreadingB...lBackend', 2)] ==
[('ThreadingBa...lBackend', 1)]
E At index 1 diff: ('ThreadingBackend', 1) != ('SequentialBackend', 1)
E Full diff:
E [('ThreadingBackend', 0),
E - ('ThreadingBackend', 1),
E - ('SequentialBackend', 2),
E ?^
E + ('SequentialBackend', 1),...
E
E ...Full output truncated (7 lines hidden), use '-vv' to show
joblib/test/test_parallel.py:1452: AssertionError
== 2 failed, 1099 passed, 19 skipped in 70.93 seconds ==
[INFO:MainProcess:Dummy-463] process shutting down
[DEBUG:MainProcess:Dummy-463] running all "atexit" finalizers with priority >= 0
[DEBUG:MainP
Bug#926651: Acknowledgement (unblock: nodejs/10.15.2~dfsg-2)
Ping ? Also i forgot to mention (though it's written in the diff of the changelog): Closes #919588 nodejs: FTBFS randomly Jérémy
Bug#926920: About nvidia-driver and nouveau
Dear maintainers, GDM, GNOME, nvidia-driver and nouveau seems fine now, but ordinal ttys resolutions were decreased. After all, I, root@buster# apt remove --purge nvidia-driver root@buster# reboot -n root@buster# nano /etc/apt/sources.list (remove contrib and non-free) root@buster# apt update root@buster# apt install xserver-xorg-video-nouveau # re-install root@buster# apt autoremove --purge root@buster# reboot -n and GDM, GNOME are fine. Mozilla Firefox plays youtube video both in window and fullscreen. no sound, though. I connect GeForce 1030 and LCD by HDMI cable. With that, Stretch was fine. Perhaps I should clean install by the next buster netinst, without contrib and non-free, again. I will report something went wrong after that. Sorry for junky reports. Thank you, all the maintainers. Regards.
Bug#926929: unblock: webkit2gtk/2.24.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package webkit2gtk Upstream published the 2.24 stable branch recently and 2.22 is no longer maintained. We want to offer webkit2gtk security updates in buster and for that we will collaborate with the Debian security team, so we'd like to have the most up-to-date stable release in the distribution. The 2.24 branch contains fixes for the following security bugs: CVE-2019-6251 CVE-2019-8506 CVE-2019-8524 CVE-2019-8535 CVE-2019-8536 CVE-2019-8544 CVE-2019-8551 CVE-2019-8558 CVE-2019-8559 CVE-2019-8563 CVE-2019-11070 See the latest WebKitGTK security advisory for more details: https://webkitgtk.org/security/WSA-2019-0002.html Updating to 2.24.1 also fixes the following Debian bug: https://bugs.debian.org/923476 unblock webkit2gtk/2.24.1-1 -- System Information: Debian Release: 9.8 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#926928: fetchmail: Server CommonName mismatch
Package: fetchmail Version: 6.4.0~beta4-3 Severity: grave Justification: renders package unusable Dear Maintainer, I use ferchmail for a while and I have seen in syslog that fetchmail returns errors: fetchmail: Loaded OpenSSL library 0x1010102f newer than headers 0x1010101f, trying to continue. fetchmail: SSL verify callback depth 0: preverify_ok == 0, err = 62, Hostname mismatch fetchmail: Server certificate: fetchmail: Issuer Organization: DigiCert Inc fetchmail: Issuer CommonName: RapidSSL RSA CA 2018 fetchmail: Subject CommonName: *.nerim.net fetchmail: Subject Alternative Name: *.nerim.net fetchmail: Subject Alternative Name: nerim.net fetchmail: Server CommonName mismatch: *.nerim.net != pop.nerim.fr fetchmail: pop.nerim.fr key fingerprint: D8:9B:28:28:4C:DF:07:5E:BC:87:6C:11:7C:A1:8E:BE fetchmail: Server certificate verification error: Hostname mismatch fetchmail: OpenSSL reported: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed fetchmail: pop.nerim.fr: upgrade to TLS failed. and, of course, fetchmail stops transaction. I haven't find a solution to fix this issue. Best regards, JB -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.8.6.1 ii libc6 2.28-8 ii libcom-err2 1.44.5-1 ii libgssapi-krb5-2 1.17-2 ii libk5crypto3 1.17-2 ii libkrb5-3 1.17-2 ii libssl1.1 1.1.1b-1 ii lsb-base 10.2019031300 Versions of packages fetchmail recommends: ii ca-certificates 20190110 Versions of packages fetchmail suggests: pn fetchmailconf pn resolvconf ii sendmail-bin [mail-transport-agent] 8.15.2-12 -- Configuration Files: /etc/default/fetchmail [Errno 13] Permission non accordée: '/etc/default/fetchmail' /etc/init.d/fetchmail changed [not included] -- no debconf information
Bug#926920: More additional reports
Dear maintainers, I almost forgot to write about /var/mail. If I separate it on debian installer, the owner and permission was not correct. Exim cannot send mails. So, root@buster# ls -ld /var/mail drwxrwxr-x 3 root root ... root@buster# chown root:mail /var/mail root@buster# chmod 2775 /var/mail root@buster# ls -ld /var/mail drwxrwsr-x 3 root mail ... And now, I confirmed Mozilla Thunderbird receives logcheck summay mails.
Bug#926927: Please add iptables.service and ip6tables.service symlinks
Package: iptables-persistent Version: 1.0.12 Severity: normal Tags: patch Hi, In other distributions, (mainly RH/Fedora) their equivalant package (iptables-services) is installing systemd iptables.service and ip6tables.service files. Some other services (like firewalld) are using these in their own .service file as dependency or conflict Would be nice if iptables-persistent was adding symlinks so other services doesn't need to be modified Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru iptables-persistent-1.0.12/debian/ipset-persistent.lintian-overrides iptables-persistent-1.0.12bigon1/debian/ipset-persistent.lintian-overrides --- iptables-persistent-1.0.12/debian/ipset-persistent.lintian-overrides 1970-01-01 01:00:00.0 +0100 +++ iptables-persistent-1.0.12bigon1/debian/ipset-persistent.lintian-overrides 2019-04-12 12:11:09.0 +0200 @@ -0,0 +1,3 @@ +# netfilter-persistent.service is installed in the netfilter-persistent package +# and this package directly depends on it +ipset-persistent: service-file-is-not-a-file lib/systemd/system/ipset.service diff -Nru iptables-persistent-1.0.12/debian/iptables-persistent.lintian-overrides iptables-persistent-1.0.12bigon1/debian/iptables-persistent.lintian-overrides --- iptables-persistent-1.0.12/debian/iptables-persistent.lintian-overrides 1970-01-01 01:00:00.0 +0100 +++ iptables-persistent-1.0.12bigon1/debian/iptables-persistent.lintian-overrides 2019-04-12 12:11:09.0 +0200 @@ -0,0 +1,4 @@ +# netfilter-persistent.service is installed in the netfilter-persistent package +# and this package directly depends on it +iptables-persistent: service-file-is-not-a-file lib/systemd/system/ip6tables.service +iptables-persistent: service-file-is-not-a-file lib/systemd/system/iptables.service diff -Nru iptables-persistent-1.0.12/debian/rules iptables-persistent-1.0.12bigon1/debian/rules --- iptables-persistent-1.0.12/debian/rules 2019-03-27 07:34:28.0 +0100 +++ iptables-persistent-1.0.12bigon1/debian/rules 2019-04-12 12:11:09.0 +0200 @@ -2,3 +2,11 @@ %: dh $@ + +override_dh_installsystemd: + # install the symlinks before calling dh_installsystemd, using a .links + # file will not work as dh_link is called later in the sequence + dh_link -pipset-persistent lib/systemd/system/netfilter-persistent.service lib/systemd/system/ipset.service + dh_link -piptables-persistent lib/systemd/system/netfilter-persistent.service lib/systemd/system/iptables.service + dh_link -piptables-persistent lib/systemd/system/netfilter-persistent.service lib/systemd/system/ip6tables.service + dh_installsystemd
Bug#926920: Additional status report
Dear maintainers, * bzr shared repository seems okay, and qbzr qdiff works. THIS IS GREAT. Please do not remove qdiff feature. It's nice. * byobu had screen size problem, but after some reboots it seems okay on CLI. I have no idea to reproduce the problem, both on GUI and CLI. * GDM, GNOME, are still slow, and GNOME system monitor shows almost 100% CPU usage; it drops CLI tty. "ps auf" says gnome-shell process %CPU around 30 on the GNOME terminal, and CLI ttys. However, response on CLI is okay. * lm-sensors seems okay. All core temp around 30 degree Celsius. (I installed a large heat pipe and 3 chassis coolers) * syslog shows multiple errors. It's 185KB. If it is okay to send it, I will attach it as .tar.gz or .xz. Here is an error summary. - Firmware Bug: TSC_DEADLINE disabled by errata. It says "please update microcode to version 0x52 or later. - nouveau: firmware failed to load nvidia/gp108/gr/sw_nonctx.bin (-2) Maybe this is the cause of GDM and gnome-shell CPU wasting. Maybe. I only using main, no contrib, no non-free section, now. I will try it later; though "only main" is my favorite, free Debian. - nouveau: DRM: failed to create kernel channel, -22 - Multiple gnome-session-binary warnings, apps killed by signal 15. - gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop. * smartd and nvme smart-log seems well. They read SMART info from both SATA SSD and M.2 NVMe. Regards.
Bug#926924: blockdev: ignore cache options for empty CDROM drives
Hi,
there is the patchfile.
Regards
Sascha
From aa21b1603562dd765c1d149600902fe63e8212b2 Mon Sep 17 00:00:00 2001
From: Sascha Girrulat
Date: Thu, 4 Apr 2019 14:08:57 +0200
Subject: [PATCH 1/2] Add upstream patch to fixup the empty cdrom handling with
e.g. cloudstack
This patch is exported from upstream. To apply this patch needed to
change some lines around 568 to support the current debian version of the
qemu source.
---
...cache-options-for-empty-CDROM-drives.patch | 89 +++
debian/patches/series | 1 +
2 files changed, 90 insertions(+)
create mode 100644 debian/patches/blockdev-ignore-cache-options-for-empty-CDROM-drives.patch
diff --git a/debian/patches/blockdev-ignore-cache-options-for-empty-CDROM-drives.patch b/debian/patches/blockdev-ignore-cache-options-for-empty-CDROM-drives.patch
new file mode 100644
index 00..2957051d90
--- /dev/null
+++ b/debian/patches/blockdev-ignore-cache-options-for-empty-CDROM-drives.patch
@@ -0,0 +1,89 @@
+From: John Snow
+Date: Fri, 16 Sep 2016 22:06:28 +0200
+Subject: blockdev: ignore cache options for empty CDROM drives
+
+RH-Author: John Snow
+Message-id: <1474063588-6370-2-git-send-email-js...@redhat.com>
+Patchwork-id: 72377
+O-Subject: [RHEV-7.3 qemu-kvm-rhev PATCH 1/1] blockdev: ignore cache options for empty CDROM drives
+Bugzilla: 1342999
+RH-Acked-by: Max Reitz
+RH-Acked-by: Kevin Wolf
+RH-Acked-by: Stefan Hajnoczi
+
+BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1342999
+Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11768839
+Upstream: N/A
+
+In qemu-kvm-rhev-2.3.0, QEMU will accept cache options for empty CDROM
+devices, but silently ignore them as they will be overwritten when the
+next CDROM is inserted.
+
+Libvirt and VMM are capable of generating XML configurations which
+attempt to specify these cache options to QEMU, though they don't have
+any effect.
+
+Upstream, a refactoring of cache option mechanisms means that we have
+started rejecting invalid configurations where cache options are supplied
+without any target to actually apply them to.
+
+This means that there are combinations of QEMU and libvirt that will fail
+to start a VM if a user selects a cache option.
+
+This patch is a downstream-only workaround until libvirt can stop
+supplying cache settings for empty CDROMs and/or until libvirt can take
+advantage of the new QMP tray/medium manipulation mechanisms that will
+allow proper cache specification for removable media.
+
+Signed-off-by: John Snow
+Signed-off-by: Miroslav Rezanina
+---
+ blockdev.c | 28 +++-
+ 1 file changed, 27 insertions(+), 1 deletion(-)
+
+diff --git a/blockdev.c b/blockdev.c
+index 81f95d9..200aae3 100644
+--- a/blockdev.c
b/blockdev.c
+@@ -461,6 +461,32 @@ static void extract_common_blockdev_options(QemuOpts *opts, int *bdrv_flags,
+ }
+ }
+
++/**
++ * libvirt expects to be able to pass cache options for CDROM drives without
++ * inserted media. Historically, QEMU eventually ignores these cache options as
++ * they are lost when media is inserted. Recently, QEMU started rejecting these
++ * configurations. Libvirt however still generates such configurations.
++ *
++ * To prevent QEMU from being unable to start, pretend there are no options
++ * present if the only options present are cache options for the BDS.
++ */
++static bool __redhat_com_has_bs_opts(QDict *bs_opts)
++{
++size_t n, s;
++s = qdict_size(bs_opts);
++
++if (s == 0) {
++return false;
++} else if (s > 2) {
++return true;
++}
++
++n = qdict_haskey(bs_opts, BDRV_OPT_CACHE_DIRECT);
++n += qdict_haskey(bs_opts, BDRV_OPT_CACHE_NO_FLUSH);
++
++return s != n;
++}
++
+ /* Takes the ownership of bs_opts */
+ static BlockBackend *blockdev_init(const char *file, QDict *bs_opts,
+Error **errp)
+@@ -568,7 +594,7 @@ static BlockBackend *blockdev_init(const char *file, QDict *bs_opts,
+ read_only = qemu_opt_get_bool(opts, BDRV_OPT_READ_ONLY, false);
+
+ /* init */
+-if ((!file || !*file) && !qdict_size(bs_opts)) {
++if ((!file || !*file) && !__redhat_com_has_bs_opts(bs_opts)) {
+ BlockBackendRootState *blk_rs;
+
+ blk = blk_new(0, BLK_PERM_ALL);
diff --git a/debian/patches/series b/debian/patches/series
index e179f79b6d..3bf3893ad8 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -9,3 +9,4 @@ slirp-check-data-length-while-emulating-ident-function-CVE-2019-6778.patch
i2c-ddc-fix-oob-read-CVE-2019-3812.patch
slirp-check-sscanf-result-when-emulating-ident-CVE-2019-9824.patch
device_tree-don-t-use-load_image-CVE-2018-20815.patch
+blockdev-ignore-cache-options-for-empty-CDROM-drives.patch
--
2.20.1
signature.asc
Description: OpenPGP digital signature
Bug#926919: PLEASE CLOSE THIS; RE-RE-SUBMIT ACK as Bug#926920
Dear maintainers, I re-re-submit due to my confusion around the name of "installation-report" package and the BTS entry name "installation-reports". I apologize about these. Regards.
