Processed: Re: Bug#920714: lombok: Build-Depends on openjdk-8-jdk which will no be in buster
Processing control commands: > severity -1 wishlist Bug #920714 [src:lombok] lombok: Build-Depends on openjdk-8-jdk which will no be in buster Severity set to 'wishlist' from 'serious' -- 920714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920714: lombok: Build-Depends on openjdk-8-jdk which will no be in buster
Control: severity -1 wishlist Hi Andreas, Actually lombok is the exception that is forcing us to ship (but not support) openjdk-8-jdk in Buster. It's a build time only dependency, lombok works with OpenJDK 11 at runtime. Emmanuel Bourg
Bug#891670: pymssql FTBFS with freetds-dev 1.00.82-2
I've been busy, sorry - feel free to team upload/NMU it but I'm hoping to get to it this weekend. -- Geoffrey Thomas (via mobile) geo...@ldpreload.com > On Jan 28, 2019, at 08:56, Raphael Hertzog wrote: > > Hi, > >> On Sun, 24 Jun 2018, Geoffrey Thomas wrote: >> Upstream is being slow to put out a new release, there's some blocker >> involving the new freetds. I asked if that was resolved yet: >> >> https://github.com/pymssql/pymssql/issues/528 >> >> At some point (probably in a month or two, honestly...) I'll cherry-pick the >> relevant patches if there's no release, but I'd prefer to see upstream be >> confident about the new freetds version. > > There's a new upstream release available. We need this package > updated for Python 3.7 for Kali so we will look into this if nobody > else is quicker. > > 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/
Processed: lombok: Build-Depends on openjdk-8-jdk which will no be in buster
Processing control commands: > block 920037 with -1 Bug #920037 [src:openjdk-8] Don't include in buster 920037 was not blocked by any bugs. 920037 was not blocking any bugs. Added blocking bug(s) of 920037: 920714 -- 920037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920037 920714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920714: lombok: Build-Depends on openjdk-8-jdk which will no be in buster
Source: lombok Version: 1.16.22-6 Severity: serious Control: block 920037 with -1 Hi, your package still Build-Depends on openjdk-8-jdk which will not be part of buster. Andreas
Processed: Bug #919876 in java-string-similarity marked as pending
Processing control commands: > tag -1 pending Bug #919876 [src:java-string-similarity] javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module Added tag(s) pending. -- 919876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919876: Bug #919876 in java-string-similarity marked as pending
Control: tag -1 pending Hello, Bug #919876 in java-string-similarity reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/java-string-similarity/commit/4df88af8bf54218a265c9ab0460e69bc7703c40c Drop -java-doc package to address FTBFS (Closes: #919876) (this message was generated automatically) -- Greetings https://bugs.debian.org/919876
Bug#920188: Bug #920188 in twitter-bootstrap4 marked as pending
Control: tag -1 pending Hello, Bug #920188 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/twitter-bootstrap4/commit/48afc3bfd09dbc5139827805f9cb7655ad375002 Add libjs-popper.js in dependencies Closes: #920188 (this message was generated automatically) -- Greetings https://bugs.debian.org/920188
Processed: Bug #920188 in twitter-bootstrap4 marked as pending
Processing control commands: > tag -1 pending Bug #920188 [libjs-bootstrap4] broken: required library Popper.js missing Ignoring request to alter tags of bug #920188 to the same tags previously set -- 920188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920712: r-cran-repr: autopkgtest regression
Source: r-cran-repr
Version: 0.19.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has
been failing its autopkgtests [1] with the following error:
> test_check('repr')
-- 1. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_arra
`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 4 string mismatches >
-- 2. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_arra
`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 5 string mismatches >
== testthat results
===
OK: 128 SKIPPED: 5 FAILED: 2
1. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_array_manipulation.r#229)
2. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_array_manipulation.r#251)
Error: testthat unit tests failed
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-repr/unstable/amd64/
Bug#920711: r-cran-repr: autopkgtest regression
Source: r-cran-repr
Version: 0.19.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has
been failing its autopkgtests [1] with the following error:
> test_check('repr')
-- 1. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_arra
`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 4 string mismatches >
-- 2. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_arra
`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 5 string mismatches >
== testthat results
===
OK: 128 SKIPPED: 5 FAILED: 2
1. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_array_manipulation.r#229)
2. Failure: ellip_limit_arr preserves rownames when limiting rows
(@test_array_manipulation.r#251)
Error: testthat unit tests failed
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-repr/unstable/amd64/
Bug#920709: distcc: fails to upgrade from 'testing': causes dpkg trigger loop
Hi Guillem, do you have any recommendations for this trigger loop? I think at this point it is already dpkg 1.19.4 that is running (dpkg is being upgraded during the same run). On 2019-01-28 14:32, Christian Marillat wrote: > On 28 janv. 2019 14:17, Andreas Beckmann wrote: > >> Package: distcc >> Version: 3.3.2-7 >> Severity: serious >> User: debian...@lists.debian.org >> Usertags: piuparts >> >> Hi, >> >> during a test with piuparts I noticed your package fails to upgrade from >> 'testing'. >> It installed fine in 'testing', then the upgrade to 'sid' fails. >> >> >From the attached log (scroll to the bottom...): >> >> dpkg: dependency problems prevent processing triggers for distcc: >>distcc depends on python3; however: >> Package python3 is not configured yet. > > How to fix this issue ? > > A pre-depends on python3 is the solution ? > > Christian Andreas
Bug#891670: pymssql FTBFS with freetds-dev 1.00.82-2
Hi, On Sun, 24 Jun 2018, Geoffrey Thomas wrote: > Upstream is being slow to put out a new release, there's some blocker > involving the new freetds. I asked if that was resolved yet: > > https://github.com/pymssql/pymssql/issues/528 > > At some point (probably in a month or two, honestly...) I'll cherry-pick the > relevant patches if there's no release, but I'd prefer to see upstream be > confident about the new freetds version. There's a new upstream release available. We need this package updated for Python 3.7 for Kali so we will look into this if nobody else is quicker. 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#907997: marked as done (emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2)
Your message dated Mon, 28 Jan 2019 14:53:33 +0100 with message-id <3fbe04a7-64ec-05db-ee9d-5e0e3b7a7...@debian.org> and subject line Re: Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 has caused the Debian Bug report #907997, regarding emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emacs-lucid Severity: serious Version: 1:25.2+1-11 Hi Rob, I'm sorry, but the Breaks/Replaces headers still seem incomplete. I just experienced the following upgrade failure when I wanted to switch from emacs25 to emacs-lucid on a Raspberry Pi running Buster/Testing arm64: Preparing to unpack .../emacs_1%3a25.2+1-11_all.deb ... Unpacking emacs (1:25.2+1-11) over (47.0) ... Selecting previously unselected package emacs-lucid. Preparing to unpack .../emacs-lucid_1%3a25.2+1-11_arm64.deb ... Unpacking emacs-lucid (1:25.2+1-11) ... dpkg: error processing archive /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-11_arm64.deb (--unpack): trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-11_arm64.deb […] E: Sub-process /usr/bin/dpkg returned an error code (1) Processing triggers for mime-support (3.61) ... dpkg: dependency problems prevent configuration of emacs: emacs depends on emacs-gtk (>= 1:25) | emacs-lucid (>= 1:25) | emacs-nox (>= 1:25); however: Package emacs-gtk is not installed. Package emacs-lucid is not installed. Package emacs-nox is not installed. dpkg: error processing package emacs (--configure): dependency problems - leaving unconfigured […] The package currently has: Replaces: emacs-gtk, emacs-lucid (<< 1:25), emacs-nox But it should have (at least): Replaces: emacs-gtk, emacs-nox, emacs25, emacs25-lucid, emacs25-nox (I don't see why a package should have a Replaces header against an earlier, identically named version of itself, so I dropped the "emacs-lucid (<< 1:25)" part. Feel free to keep it though as it shouldn't do any harm there.) Having the same packages listed in Conflicts should be probably done, too. So please also replace Conflicts: emacs-gtk, emacs-nox with Conflicts: emacs-gtk, emacs-nox, emacs25, emacs25-lucid, emacs25-nox The same also needs to be done for emacs-gtk and emacs-nox with the according package being removed from the above examples and emacs-lucid added instead. --- End Message --- --- Begin Message --- On Sun, 13 Jan 2019 14:01:00 -0600 Rob Browning wrote: > I think this bug may now be "fixed" by the switch of the emacs package > to upstream 26.1, which should avoid including any of the conflicting > paths. I haven't seen anything related in my piuparts upgrade tests, so this seems to be really "fixed", thus closing. Andreas--- End Message ---
Processed: Re: emacs-common: copyright file missing after upgrade of emacs-nox from stretch
Processing control commands: > tag -1 pending Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file missing after upgrade of emacs-nox from stretch Added tag(s) pending. > tag 875430 pending Bug #875430 [emacs25] emacs25: please add Breaks: edb (<< 1.32) Added tag(s) pending. > tag 910925 pending Bug #910925 [emacs25] emacs25: add Breaks: egg Added tag(s) pending. > tag 690771 pending Bug #690771 [src:emacs] please add Vcs-* headers to the control file Added tag(s) pending. > tag 918646 pending Bug #918646 [src:emacs] emacs: FTBFS (failing tests) Added tag(s) pending. -- 690771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690771 875430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875430 910925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910925 911616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911616 918646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch
Followup-For: Bug #911616 Control: tag -1 pending Control: tag 875430 pending Control: tag 910925 pending Control: tag 690771 pending Control: tag 918646 pending Hi Rob, this issue is cuasing a lot of upgrade failures in piuparts. I've prepared a NMU of the emacs package fixing this and some more issues and uploaded to DELAYED/5. Please let me know if I should delay it longer. It fixes all the RC issues and some more trivial ones, I also did some further packaging cleanup to reduce the amount of issues reported by lintian. I'll probably followup with another upload adding some more transitional packages (#916758). You can find all the changes in the master branch of https://salsa.debian.org/anbe/deb-emacs (I'll push the tag once the package has been accepted into unstable). Note that your repository does not contain any branches for emacs 26.1, there are only the tags, so I started my work from the latest tag. Once you settled the branch issue, the Vcs-Git URL should get a " -b some/branch" appended. Andreas
Bug#920709: distcc: fails to upgrade from 'testing': causes dpkg trigger loop
On 28 janv. 2019 14:17, Andreas Beckmann wrote: > Package: distcc > Version: 3.3.2-7 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails. > >>From the attached log (scroll to the bottom...): > > dpkg: dependency problems prevent processing triggers for distcc: >distcc depends on python3; however: > Package python3 is not configured yet. How to fix this issue ? A pre-depends on python3 is the solution ? Christian
Processed: severity of 907754 is important
Processing commands for cont...@bugs.debian.org: > severity 907754 important Bug #907754 [src:webdis] webdis: FTBFS on i386, mips64el Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 907754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907754: webdis: FTBFS on i386, mips64el
On Sat, 1 Sep 2018 14:46:57 +0200 Mattia Rizzolo wrote: > Source: webdis > Version: 0.1.4+dfsg-1 > Severity: serious > > Dear maintainer, > > the package FTBFS on the buildds on i386 and mips64el: It since built on i386 and the mips64el binary has been removed, so downgrading to important. Scott K
Bug#920709: distcc: fails to upgrade from 'testing': causes dpkg trigger loop
Package: distcc Version: 3.3.2-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): dpkg: dependency problems prevent processing triggers for distcc: distcc depends on python3; however: Package python3 is not configured yet. dpkg: error processing package distcc (--configure): dependency problems - leaving triggers unprocessed [...] dpkg: dependency problems prevent processing triggers for distcc: distcc depends on python3; however: Package python3 is not configured yet. dpkg: error processing package distcc (--configure): dependency problems - leaving triggers unprocessed dpkg: too many errors, stopping Errors were encountered while processing: distcc distcc distcc distcc [...] distcc distcc distcc distcc Processing was halted because there were too many errors. cheers, Andreas distcc_3.3.2-7.log.gz Description: application/gzip
Bug#785990: distcc: deprecation of python-support
Control: tag -1 - experimental Control: close -1 There is no longer an outdated version in experimental. Andreas
Processed: Re: distcc: deprecation of python-support
Processing control commands: > tag -1 - experimental Bug #785990 [src:distcc] distcc: deprecation of python-support Removed tag(s) experimental. > close -1 Bug #785990 [src:distcc] distcc: deprecation of python-support Marked Bug as done -- 785990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920705: python-jupyter-sphinx-theme: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-jupyter-sphinx-theme Version: 0.0.6+ds1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: stretch -> sid For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 1m12.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-jupyter-sphinx-theme/changelog.Debian.gz (python-jupyter-sphinx-theme) != /usr/share/doc/jupyter-sphinx-theme-common/changelog.Debian.gz (jupyter-sphinx-theme-common) /usr/share/doc/python-jupyter-sphinx-theme -> jupyter-sphinx-theme-common /usr/share/doc/python-jupyter-sphinx-theme/copyright (python-jupyter-sphinx-theme) != /usr/share/doc/jupyter-sphinx-theme-common/copyright (jupyter-sphinx-theme-common) /usr/share/doc/python-jupyter-sphinx-theme -> jupyter-sphinx-theme-common cheers, Andreas
Processed: Re: Fails to build for non-current kernel version
Processing control commands: > affects -1 + xtables-addons-dkms Bug #917905 [xtables-addons-source] Fails to build for non-current kernel version Added indication that 917905 affects xtables-addons-dkms > severity -1 serious Bug #917905 [xtables-addons-source] Fails to build for non-current kernel version Severity set to 'serious' from 'important' -- 917905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920018: marked as done (Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory)
Your message dated Mon, 28 Jan 2019 12:51:45 + with message-id and subject line Bug#920018: fixed in systemd 240-5 has caused the Debian Bug report #920018, regarding Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 240-4 Severity: important Hi! Since systemd_240-4 journald seems to either leak memory or something strange is going on with my system. Soon after boot or journald restart, I get messages like this in my kernel log: [...] [31317.206261] systemd-journald[341]: Failed to write entry (29 items, 682 bytes), ignoring: Cannot allocate memory [31330.715806] systemd-journald[341]: Failed to write entry (21 items, 547 bytes), ignoring: Cannot allocate memory [31330.756475] systemd-journald[341]: Failed to write entry (21 items, 549 bytes), ignoring: Cannot allocate memory [31330.756946] systemd-journald[341]: Failed to write entry (21 items, 633 bytes), ignoring: Cannot allocate memory [31330.757454] systemd-journald[341]: Failed to write entry (21 items, 629 bytes), ignoring: Cannot allocate memory [31331.070486] systemd-journald[341]: Failed to write entry (22 items, 577 bytes), ignoring: Cannot allocate memory [31331.070625] systemd-journald[341]: Failed to write entry (22 items, 564 bytes), ignoring: Cannot allocate memory [31331.103742] systemd-journald[341]: Failed to write entry (22 items, 581 bytes), ignoring: Cannot allocate memory [31331.103878] systemd-journald[341]: Failed to write entry (22 items, 548 bytes), ignoring: Cannot allocate memory [31331.104589] systemd-journald[341]: Failed to write entry (22 items, 562 bytes), ignoring: Cannot allocate memory [31334.787786] systemd-journald[341]: Failed to write entry (24 items, 611 bytes), ignoring: Cannot allocate memory [31335.992491] systemd-journald[341]: Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory [...] Also the committed memory size as recored by munin (see attached image) spikes quickly. You can clearly spot in the graph, when I upgraded to systemd_240-4. You can also see the times where I manually restarted journald. (Yes, this system is a bit small for all the services running on it, hence the swap usage.) I now have downgraded to systemd_240-3 which resolves this issue for me. Other systems of mine show the same, but because they have more RAM, the problem is not as visible (yet). Grüße, Sven. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.13.2-3 ii libaudit11:2.8.4-2 ii libblkid12.33.1-0.1 ii libc62.28-5 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.6-1 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.5-2 ii libgpg-error01.33-3 ii libidn11 1.33-2.2 ii libip4tc01.8.2-3 ii libkmod2 25-2 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.2-1.3 ii libmount12.33.1-0.1 ii libpam0g 1.1.8-4 ii libseccomp2 2.3.3-3 ii libselinux1 2.8-1+b1 ii libsystemd0 240-4 ii mount2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus1.12.12-1 ii libpam-systemd 240-4 Versions of packages systemd suggests: ii policykit-10.105-25 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.132 ii udev 240-4 -- Configuration Files: /etc/systemd/journald.conf changed: [Journal] Storage=persistent ForwardToConsole=yes TTYPath=/dev/tty12 /etc/systemd/logind.conf changed: [Login] KillUserProcesses=no /etc/systemd/system.conf changed: [Manager] RuntimeWatchdogSec=60 -- debconf-show failed --- End Message --- --- Begin Message --- Source: systemd Source-Version: 240-5 We believe
Bug#919390: marked as done (udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules)
Your message dated Mon, 28 Jan 2019 12:51:45 +
with message-id
and subject line Bug#919390: fixed in systemd 240-5
has caused the Debian Bug report #919390,
regarding udev: network interface gets ID_NET_NAME even when NAME has been set
by /etc/udev/rules.d/70-persistent-net.rules
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 240-2
Severity: normal
Hi,
when updating from an older udev version I have noticed that my ethernet
interface got renamed to autogenerated (ID_NET_NAME) name even though I
have /etc/udev/rules.d/70-persistent-net.rules to rename it based on
the mac address as follows:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="28:f1:0e:31:04:16", KERNEL=="eth*", NAME="lan0"
The kernel log says that this gets applied:
[3.563937] e1000e :00:1f.6 lan0: renamed from eth0
[...]
[4.043437] e1000e :00:1f.6 enp0s31f6: renamed from lan0
Downgrading to 232-25+deb9u7 or adding net.ifnames=0 to kernel cmd line
makes the problem go away.
Let me know if you need an additional information.
Thanks!
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.0.0-rc1-1-g3bd6e94bec12 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(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 libacl1 2.2.52-3+b1
ii libblkid12.33.1-0.1
ii libc62.28-2
ii libkmod2 25-2
ii libselinux1 2.8-1+b1
ii libudev1 240-2
ii lsb-base 10.2018112800
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/title/upgrade:
udev/sysfs_deprecated_incompatibility:
udev/reboot_needed:
udev/new_kernel_needed: false
--
Michal Hocko
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-5
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Jan 2019 21:33:07 +
Source: systemd
Architecture: source
Version: 240-5
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
Changed-By: Martin Pitt
Closes: 919390 920018
Changes:
systemd (240-5) unstable; urgency=medium
.
[ Felipe Sateler ]
* Revert interface renaming changes. (Closes: #919390)
.
[ Martin Pitt ]
* process-util: Fix memory leak (Closes: #920018)
Checksums-Sha1:
7ca4cf0e5237140b58f79cbd085aefd8d149ccf4 4898 systemd_240-5.dsc
10bd8179fbecdd2e1042dfa0bb3ff7af3b2c542e 165928 systemd_240-5.debian.tar.xz
35957a2ecd9e3d91ab8e2e24e2578302ede86cba 5785 systemd_240-5_source.buildinfo
Checksums-Sha256:
dfd3171ad9a140feaff6719abcd7586e3f4d46e5e5f048c3b04aa8504a8c94d8 4898
systemd_240-5.dsc
85022f13fd97467d10760917ac190f5f2960cf03b2349eed02b84dc3128dcb59 165928
systemd_240-5.debian.tar.xz
8236986f70863b5b8b79adb74a7d1ff789b2df0b3adaa22be11742e4468c0215 5785
systemd_240-5_source.buildinfo
Files:
02768a90ec1bc4eb87b61b7c149f1e54 4898 admin optional systemd_240-5.dsc
3349beba2d35cdbd1e3b4c0601b6bda5 165928 admin optional
systemd_240-5.debian.tar.xz
7d4c1fe5c542be96eeb55ea405d66b24 5785 admin optional
systemd_240-5_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#920704: python3.6: keep out of testing
Source: python3.6 Severity: serious We want to ship buster with python3.7 as the only python3 version. This bug shall prevent python3.6 from re-entering testing. Emilio
Bug#920547: Crashes every few hours
On Sun, 27 Jan 2019 15:10:39 -0500 Chris Manougian wrote: > Hi Toni. I have an XPS 15 9570, which, I think, is basically the same > machine, except yours uses an NVIDIA Quadro vs my GeForce GTX 1050Ti as a > 2nd graphics card. > > A lot of problems with that secondary graphics card and linux. Are you > attempting to use it via Bumblebee? > > See this thread (and links within the thread) - BIOS related: > https://bugzilla.redhat.com/show_bug.cgi?id=1610727 > > I did my best to disable the NVIDIA card: > https://wiki.archlinux.org/index.php/Dell_XPS_15_9570 > > One of my more recent "important" gnome-logs file is: > > 03:16:35 kernel: ath10k_pci :3b:00.0: firmware: failed to load > ath10k/cal-pci-:3b:00.0.bin (-2) > 03:16:35 kernel: firmware_class: See https://wiki.debian.org/Firmware for > information about missing firmware > 03:16:35 kernel: ath10k_pci :3b:00.0: firmware: failed to load > ath10k/pre-cal-pci-:3b:00.0.bin (-2) > 03:16:34 kernel: iTCO_wdt iTCO_wdt: can't request region for resource [mem > 0x00c5fffc-0x00c5] > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS10._PLD], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS10._UPC], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS09._PLD], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS08._PLD], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating Hi, If it may help (I'm on testing w/ 4.9.12) this bug seems to be NVidia-specific. Never encountered such things on my laptop which has an AMD GPU with the FOSS driver. Reference is Dell Latitude e6540. Rgds,
Bug#919763: adios: armhf FTBFS when built on arm64
Hi Alastair, On Mon, Jan 28, 2019 at 09:50:30AM +, Alastair McKinstry wrote: >Hi > >Yes, thanka for this patch. I'm reluctant to consider that binaries built on >armhf failing on arm64 is an _RC Bug_, but its definitely undesirable. It's not *yet* RC, but it's going to go that way soon. Our plan is to switch to building for armel and armhf using arm64 machines before too long, which would reliably break all packages with bugs like this. -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back
Bug#920700: python3-adios: fails to upgrade from 'testing': update-alternatives: error: alternative python-py37-adios-x86_64-linux-gnu can't be master: it is a slave of python-py36-adios-x86_64-linux-
Package: python3-adios Version: 1.13.1-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): Setting up python3-adios (1.13.1-14) ... update-alternatives: error: alternative python-py37-adios-x86_64-linux-gnu can't be master: it is a slave of python-py36-adios-x86_64-linux-gnu dpkg: error processing package python3-adios (--configure): installed python3-adios package post-installation script subprocess returned error exit status 2 Processing triggers for libc-bin (2.28-5) ... Errors were encountered while processing: python3-adios cheers, Andreas python3-adios_1.13.1-14.log.gz Description: application/gzip
Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'
[2019-01-23 12:41] Jonathan Nieder > Dmitry Bogatov wrote: > >> Jonathan Nieder wrote: > > >>> + * git-daemon-run: pre-create supervise directory so that postinst > >>> +can start the service (thx Celejar and Dmitry Bogatov; closes: > >>> +#919296). > [...] > > Wierd. It should work. /etc/sv/git-daemon/supervise is not dangling, is > > it? Tell me which git commit I should build and test, in effort to help > > debugging? > > It's not dangling. > > I tested with the debian-sid branch, with the patch in the message I > sent applied on top. That said: > > [...] > > It is my fault. I dropped /var/lib/supervise directory in runit=2.1.2-4, > > which was expected by git-daemon-run. > > > > Today runit packaging underwent quite a rework, and packages, providing > > runscripts are encouraged to use dh_runit(1). It manages creation of > > apporiate directories and symbolic links. If you have any issues, do not > > hezitate to ask -- runit is my top priority. > > Thanks, these are two good starting points. I'll take a look at the > 2.1.2-4 changes and into whether it's simple to use dh_runit. Hopefully > the latter will take care of everything. :) As promised, I applied patch over debian-sid branch and rebuilt package. It worked out-of-box, except on on postinst, it output warning about missing 'supervision/control', originating from this line: sv -v term git-daemon || : but it is harmless. You observe another, more buggy behaviour, don't you? -- Note, that I send and fetch email in batch, once every 24 hours. If matter is urgent, try https://t.me/kaction --
Processed: Bug #916286 in traverso marked as pending
Processing control commands: > tag -1 pending Bug #916286 [src:traverso] traverso: baseline violation on i386 Added tag(s) pending. -- 916286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916286: Bug #916286 in traverso marked as pending
Control: tag -1 pending Hello, Bug #916286 in traverso reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/traverso/commit/4c1f132b778c3f9197f66de5fd374c1913f2d948 d/rules: fix baseline CPU instructions violation Closes: #916286 Signed-off-by: Dmitry Eremin-Solenikov (this message was generated automatically) -- Greetings https://bugs.debian.org/916286
Bug#920662: marked as done (orthanc-mysql: uses $(DEB_VERSION) as SOVERSION)
Your message dated Mon, 28 Jan 2019 12:21:27 + with message-id and subject line Bug#920662: fixed in orthanc-mysql 2.0-2 has caused the Debian Bug report #920662, regarding orthanc-mysql: uses $(DEB_VERSION) as SOVERSION to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: orthanc-mysql Version: 1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, $ lintian orthanc-mysql_1.1-1+b1_amd64.deb W: orthanc-mysql: package-name-doesnt-match-sonames libOrthancMySQLIndex1.1-1+b1 libOrthancMySQLStorage1.1-1+b1 E: orthanc-mysql: ldconfig-symlink-missing-for-shlib usr/lib/libOrthancMySQLIndex.so.1.1-1+b1 usr/lib/libOrthancMySQLIndex.so.1.1-1 libOrthancMySQLIndex.so.1.1-1+b1 E: orthanc-mysql: ldconfig-symlink-missing-for-shlib usr/lib/libOrthancMySQLStorage.so.1.1-1+b1 usr/lib/libOrthancMySQLStorage.so.1.1-1 libOrthancMySQLStorage.so.1.1-1+b1 This is also reproducible with 2.0-1. Using $(DEB_VERSION) in the SONAME of the library is, well, insane. Since the library has a strange naming that makes it nearly impossible to be used as a regular shared library (and it seems to used rather as a plugin loaded via the .so extension, no no version weirdness involved), the question arises "why is it in/usr/lib nevertheless?" Andreas --- End Message --- --- Begin Message --- Source: orthanc-mysql Source-Version: 2.0-2 We believe that the bug you reported is fixed in the latest version of orthanc-mysql, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc-mysql package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 11:55:02 +0100 Source: orthanc-mysql Binary: orthanc-mysql orthanc-mysql-dbgsym Architecture: source amd64 Version: 2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Description: orthanc-mysql - Plugins to use MySQL or MariaDB as a database back-end to Orthanc Closes: 920662 Changes: orthanc-mysql (2.0-2) unstable; urgency=medium . * Removed $(DEB_VERSION) from SOVERSION. Closes: #920662 Checksums-Sha1: 6f783663a4befbf859e3defe41284f4982217e63 2168 orthanc-mysql_2.0-2.dsc 11ead7ff07ce3da9e35200f9e819adb180b777b9 1422764 orthanc-mysql_2.0-2.debian.tar.xz bf892d069b84cb51484469f5b15afc7e2e618656 14885808 orthanc-mysql-dbgsym_2.0-2_amd64.deb 8a5f5abef5e6150a813904e21931d652fc91fc23 13181 orthanc-mysql_2.0-2_amd64.buildinfo 8aaf03cec84e07516d217bdd324a8c88d1eaf33f 373140 orthanc-mysql_2.0-2_amd64.deb Checksums-Sha256: 7a602d7125fb0d0b30beffed59dc57223097b2a55da1d300e74ebb0c497a4fc0 2168 orthanc-mysql_2.0-2.dsc 9a5d7bdf632c192513032ffa93f6e3864337ab43a689e323ebeb523d99598778 1422764 orthanc-mysql_2.0-2.debian.tar.xz d334f15507fd57d1ce3aea31b3138072c9a804ea80f700e3efea0c2a3cb7fe84 14885808 orthanc-mysql-dbgsym_2.0-2_amd64.deb d0f5b789849a361bdf0ca063dc5e4b84313cd018f7eb30c0b40bb5f415ad75ad 13181 orthanc-mysql_2.0-2_amd64.buildinfo d26da053ab2e50ab621bfaeca0f1ef911590a96515a3e95c71d42e98a1e01b69 373140 orthanc-mysql_2.0-2_amd64.deb Files: b6ec9673f4cadf6438a9eb8167c15ee5 2168 science optional orthanc-mysql_2.0-2.dsc f87e94ad351055e35fca26965bf96c0f 1422764 science optional orthanc-mysql_2.0-2.debian.tar.xz 7d19afb3a343a13dd54a1888979cafe8 14885808 debug optional orthanc-mysql-dbgsym_2.0-2_amd64.deb 4990591bf83272c873d60c2c77134654 13181 science optional orthanc-mysql_2.0-2_amd64.buildinfo 39eeaa867c97a13d151cdb049c96a3e5 373140 science optional orthanc-mysql_2.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAlxO7hkUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw10gcA/9GMtAdv82CpAtJ2C/Exg7A7JuKhk2
Processed: Re: Bug#919962: Errors caused by not installing Recommend packages
Processing control commands: > severity -1 normal Bug #919962 [goaccess] Errors caused by not installing Recommend packages Severity set to 'normal' from 'serious' > retitle -1 goaccess: absence of optional packages looks like an error, but > it's not Bug #919962 [goaccess] Errors caused by not installing Recommend packages Changed Bug title to 'goaccess: absence of optional packages looks like an error, but it's not' from 'Errors caused by not installing Recommend packages'. -- 919962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919962: Errors caused by not installing Recommend packages
Control: severity -1 normal Control: retitle -1 goaccess: absence of optional packages looks like an error, but it's not On Sun, Jan 20, 2019 at 03:57:22PM +0800, 積丹尼 Dan Jacobson wrote: > X-Debbugs-Cc: goacc...@prosoftcorp.com > Package: goaccess > Version: 1:1.2-4 > > Versions of packages goaccess recommends: > pn geoip-database > pn geoip-database-extra > > Well one gets the > Error Opening file /usr/share/GeoIP/GeoIP.dat > each time one uses the command. > > So please either require the packages, or remove the error. Note that although the message seems scary, that is a warning and not a fatal error, so Recommends: is correct. I will keep this bug open to track making the message that is displayed more clear. signature.asc Description: PGP signature
Bug#920695: knot-resolver: uninstallable and FTBFS in stretch-backports
Source: knot-resolver Version: 2.3.0-3~bpo9+1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libkres7 Hi, libkres7/stretch-backports depends on unavailable libdnssec5, libknot7. Trying to rebuild it fails with In file included from /build/knot-resolver-2.3.0/lib/resolve.h:24:0, from /build/knot-resolver-2.3.0/lib/cache/impl.h:32, from lib/cache/entry_list.c:21: /build/knot-resolver-2.3.0/lib/cookies/lru_cache.h:24:39: fatal error: libknot/rrtype/opt-cookie.h: No such file or directory #include You should probably update the backport to the current version in buster. Andreas
Processed: Re: Bug#920681: atropy ftbfs with numpy 1.16
Processing control commands: > tags -1 moreinfo Bug #920681 [src:astropy] atropy ftbfs with numpy 1.16 Added tag(s) moreinfo. -- 920681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920681: atropy ftbfs with numpy 1.16
Control: tags -1 moreinfo Hi Matthias, could you point me to a complete build log? 3.1.1-1 compiled fine with numpy_1.16.0~rc2, and I just successfully tried with numpy 1.16.0. The failure you mentioned happened in 3.1 and was the main reason for upstream to make a 3.1.1 release. Best Ole
Bug#905254: marked as done (libphp-phpmailer: Please update to version 6.x)
Your message dated Mon, 28 Jan 2019 11:19:49 + with message-id and subject line Bug#905254: fixed in libphp-phpmailer 6.0.6-0.1 has caused the Debian Bug report #905254, regarding libphp-phpmailer: Please update to version 6.x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 905254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libphp-phpmailer Version: 5.2.14+dfsg-2.3 Severity: wishlist Hello, libphp-phpmailer seems out of date, current version is 6.0.5. Could you update it ? Cheers, Xavier -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (600, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libphp-phpmailer depends on: pn php-common libphp-phpmailer recommends no packages. Versions of packages libphp-phpmailer suggests: pn php-league-oauth2-client pn php-league-oauth2-google ii postfix [mail-transport-agent] 3.3.0-1+b1 --- End Message --- --- Begin Message --- Source: libphp-phpmailer Source-Version: 6.0.6-0.1 We believe that the bug you reported is fixed in the latest version of libphp-phpmailer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated libphp-phpmailer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Jan 2019 09:30:40 +0100 Source: libphp-phpmailer Binary: libphp-phpmailer Architecture: source Version: 6.0.6-0.1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: Paul Gevers Description: libphp-phpmailer - full featured email transfer class for PHP Closes: 905254 Changes: libphp-phpmailer (6.0.6-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release (Closes: #905254) * Drop patches, applied upstream Checksums-Sha1: 6e69a1dc9adc39bd8ae5ba7691116905025f73e3 1695 libphp-phpmailer_6.0.6-0.1.dsc a3e4fe23731adde20696bd64f303e45a400dd6e0 90407 libphp-phpmailer_6.0.6.orig.tar.gz 3ba327aa4a95bbe0ea2e20d57defd5a358dd129c 5300 libphp-phpmailer_6.0.6-0.1.debian.tar.xz Checksums-Sha256: 14bd8e461879d7c727b07337913d092c53ea15aebf45551f68874930c19f1b45 1695 libphp-phpmailer_6.0.6-0.1.dsc 3cf1f9a2ef06809040cb8b532e3de95d483cb10f25f722548f6a73a0d134666c 90407 libphp-phpmailer_6.0.6.orig.tar.gz d909e6fb31309e29aa13fa33807195ca5ef89b10b80e31855e735114e9ed21ff 5300 libphp-phpmailer_6.0.6-0.1.debian.tar.xz Files: 545553c64eb4bcd24fa6fbdf44efe48e 1695 php optional libphp-phpmailer_6.0.6-0.1.dsc ebfe6eb9d16ca2ff3d599924459f2630 90407 php optional libphp-phpmailer_6.0.6.orig.tar.gz b81269e743f4cafaf1b77c62324ae8ae 5300 php optional libphp-phpmailer_6.0.6-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlw7CfwACgkQnFyZ6wW9 dQor0AgAl4rlEhwzRtHVEqmVAoUqedAoBwzF9vrGD6dmD053/I2n283A3E3qUS3f uVfz3lUkKAJEoYrNHQibOqfNqVAKtrct4kpOhWkXswyWvImwb3ctF4T3iXJvg1bg ieKOd541nIgJ1ZTxYC3HSUqlQW3PxUaoIZQ0oLftYUW4qxSCwlYu7de9XwwVzjp6 Yb60HJCyrK7ShjHGcuaAuWniDxn5EiU9OsDjBZs1SgdkKOmKzNupB5mVcSuey+yX YN4XDX7mFMBMC9cXoPO8C1ziYOo1nx+4r0vNaq0tENzHjYNoTITzEbMg+R1JRGfO n0ahU9k4aAvxavqzxOVcW3Vi/JI18w== =W92x -END PGP SIGNATURE End Message ---
Bug#920683: Cannot import gdbm module
Le 28/01/19 à 11:55, Matthias Klose a écrit : On 28.01.19 11:48, Laurent Bigonville wrote: Package: python3-gdbm Version: 3.7.2-3 Severity: grave Hi, It seems that the gdbm module cannot be imported in python 3 import gdbm Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'gdbm' there is none ... python3-gdbm: /usr/lib/python3.7/lib-dynload/_gdbm.cpython-37m-x86_64-linux-gnu.so ?
Bug#901952: usability bug
I agree that the issue of older versions not unpacking things made by newer versions is not an important bug. I added that as an FYI. I do think this bug qualifies as RC even though there is a workaround. The workaround is non-trivial and requires Debian Developers to research the issue for a process that is normally entirely transparent. Tools like pristine-tar become much less valuable if they introduce their own restrictions to the packaging process. It changes "use pristine-tar, and things will work better" into "use pristine-tar and you'll have to learn some new workarounds, but it'll probably save you time".
Bug#920683: marked as done (Cannot import gdbm module)
Your message dated Mon, 28 Jan 2019 11:55:28 +0100 with message-id <29610ccc-2e4e-33a3-485b-e8e4b6f81...@debian.org> and subject line Re: Bug#920683: Cannot import gdbm module has caused the Debian Bug report #920683, regarding Cannot import gdbm module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-gdbm Version: 3.7.2-3 Severity: grave Hi, It seems that the gdbm module cannot be imported in python 3 >>> import gdbm Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'gdbm' 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) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-gdbm depends on: ii libc6 2.28-5 ii libgdbm6 1.18.1-2 ii python3 3.7.2-1 python3-gdbm recommends no packages. Versions of packages python3-gdbm suggests: pn python3-gdbm-dbg --- End Message --- --- Begin Message --- On 28.01.19 11:48, Laurent Bigonville wrote: > Package: python3-gdbm > Version: 3.7.2-3 > Severity: grave > > Hi, > > It seems that the gdbm module cannot be imported in python 3 > import gdbm > Traceback (most recent call last): > File "", line 1, in > ModuleNotFoundError: No module named 'gdbm' there is none ...--- End Message ---
Bug#910064: marked as done (androguard : Depends: python3-asn1crypto but it is not installable)
Your message dated Mon, 28 Jan 2019 11:48:43 +0100 with message-id <58f2c979-be53-df6a-6d2b-51cf1555d...@eds.org> and subject line python3-asn1crypto is in stretch-backports has caused the Debian Bug report #910064, regarding androguard : Depends: python3-asn1crypto but it is not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 910064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: androguard Version: 3.2.1-1~bpo9+1 Severity: serious Dear Maintainer, androguard from stretch-backports is not installable: holger@profitbricks-build7-amd64:~$ sudo apt update Hit:1 http://security.debian.org stretch/updates InRelease Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease Hit:4 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease Hit:5 http://cdn-fastly.deb.debian.org/debian stretch Release Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. holger@profitbricks-build7-amd64:~$ apt list --upgradable Listing... Done androguard/stretch-backports 3.2.1-1~bpo9+1 amd64 [upgradable from: 3.1.0~rc2-1~bpo9+1] N: There are 2 additional versions. Please use the '-a' switch to see them. holger@profitbricks-build7-amd64:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. holger@profitbricks-build7-amd64:~$ sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. holger@profitbricks-build7-amd64:~$ sudo apt install androguard Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: androguard : Depends: python3-asn1crypto but it is not installable E: Unable to correct problems, you have held broken packages. holger@profitbricks-build7-amd64:~$ cat /etc/apt/sources.list | grep -v \# deb http://deb.debian.org/debian/ stretch main contrib non-free deb http://deb.debian.org/debian/ stretch-updates main contrib non-free deb http://security.debian.org/ stretch/updates main contrib non-free deb http://deb.debian.org/debian/ stretch-backports main contrib non-free holger@profitbricks-build7-amd64:~$ -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature --- End Message --- --- Begin Message --- I forgot to close this bug, python3-asn1crypto is in stretch-backports now: https://packages.debian.org/stretch-backports/python3-asn1crypto signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#920683: Cannot import gdbm module
Package: python3-gdbm Version: 3.7.2-3 Severity: grave Hi, It seems that the gdbm module cannot be imported in python 3 >>> import gdbm Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'gdbm' 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) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-gdbm depends on: ii libc6 2.28-5 ii libgdbm6 1.18.1-2 ii python3 3.7.2-1 python3-gdbm recommends no packages. Versions of packages python3-gdbm suggests: pn python3-gdbm-dbg
Bug#920681: atropy ftbfs with numpy 1.16
Package: src:astropy Version: 3.1.1-1 Severity: serious Tags: sid buster atropy ftbfs with numpy 1.16 at least there are deprecation warnings popping up ... > 'a.item() instead', DeprecationWarning, stacklevel=1) E DeprecationWarning: np.asscalar(a) is deprecated since NumPy v1.16, use a.item() instead /usr/lib/python3/dist-packages/numpy/lib/type_check.py:546: DeprecationWarning == 23 failed, 11633 passed, 358 skipped, 66 xfailed in 640.43 seconds ==
Bug#919763: marked as done (adios: armhf FTBFS when built on arm64)
Your message dated Mon, 28 Jan 2019 10:19:34 + with message-id and subject line Bug#919763: fixed in adios 1.13.1-15 has caused the Debian Bug report #919763, regarding adios: armhf FTBFS when built on arm64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adios Version: 1.13.1-11 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=adios=armhf ... make check-TESTS make[5]: Entering directory '/<>/build-mpich/tests/test_src' make[6]: Entering directory '/<>/build-mpich/tests/test_src' PASS: copy_subvolume PASS: test_strutil PASS: text_to_pairstruct PASS: trim_spaces PASS: group_free_test PASS: transforms_specparse ../../../config/test-driver: line 107: 15948 Bus error "$@" > $log_file 2>&1 ../../../config/test-driver: line 107: 15949 Bus error "$@" > $log_file 2>&1 FAIL: read_points_2d FAIL: array_attribute PASS: selection_api ../../../config/test-driver: line 107: 15944 Bus error "$@" > $log_file 2>&1 FAIL: query_minmax ../../../config/test-driver: line 107: 15950 Bus error "$@" > $log_file 2>&1 FAIL: read_points_3d PASS: points_1DtoND PASS: hashtest = adios 1.13.1: tests/test_src/test-suite.log = # TOTAL: 14 # PASS: 9 # SKIP: 0 # XFAIL: 0 # FAIL: 5 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: query_minmax == Running query_minmax [rank=000, line 196]: Write step 0 to query_minmax.bp [rank=000, line 200]: groupsize calculated = 48 [rank=000, line 202]: groupsize calculated = 448 [rank=000, line 205]: groupsize 448, totalsize 1844 [rank=000, line 237]: Write time for step 0 was 0.000 seconds [rank=000, line 196]: Write step 1 to query_minmax.bp FAIL query_minmax (exit status: 135) FAIL: read_points_2d Running read_points [rank=000, line 221]: Write step 0 to read_points_2d.bp [rank=000, line 264]: Write time for step 0 was 0.000 seconds [rank=000, line 221]: Write step 1 to read_points_2d.bp FAIL read_points_2d (exit status: 135) FAIL: read_points_3d Running read_points [rank=000, line 238]: Write step 0 to read_points_3d.bp [rank=000, line 274]: Write time for step 0 was 0.001 seconds [rank=000, line 238]: Write step 1 to read_points_3d.bp FAIL read_points_3d (exit status: 135) FAIL: array_attribute = FAIL array_attribute (exit status: 135) FAIL: array_attribute = FAIL array_attribute (exit status: 135) Testsuite summary for adios 1.13.1 # TOTAL: 14 # PASS: 9 # SKIP: 0 # XFAIL: 0 # FAIL: 5 # XPASS: 0 # ERROR: 0 See tests/test_src/test-suite.log make[6]: *** [Makefile:1343: test-suite.log] Error 1 These are likely alignment problems. Backtrace of array_attribute: #0 0x00b6ac76 in bp_parse_vars (fh=fh@entry=0x14dc940) at ../../src/core/bp_utils.c:1585 #1 0x00b6bc1e in bp_open (fname=, comm=comm@entry=1, fh=fh@entry=0x14dc940) at ../../src/core/bp_utils.c:384 #2 0x00b780ae in open_stream (timeout_sec=, comm=1, fname=, fp=0x14ddfb0) at ../../src/read/read_bp.c:1685 #3 adios_read_bp_open (fname=, comm=1, lock_mode=, timeout_sec=) at ../../src/read/read_bp.c:1713 #4 0x00b6d76e in common_read_open (fname=0xbbe394 "array_attribute.bp", method=ADIOS_READ_METHOD_BP, comm=1, lock_mode=ADIOS_LOCKMODE_NONE, timeout_sec=0) at ../../src/core/common_read.c:424 #5 0x00b50698 in read_attrs () at ../../../tests/test_src/array_attribute.c:267 #6 0x00b4ff1c in main (argc=, argv=) at ../../../tests/test_src/array_attribute.c:115 --- End Message --- --- Begin Message --- Source: adios Source-Version: 1.13.1-15 We believe that the bug you reported is fixed in the latest version of adios, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian
Bug#920678: closing 920678
close 920678 10.15.0~dfsg-10 thanks This is canonically true that 10.15.0~dfsg-10 fixes this bug.
Processed: closing 920678
Processing commands for cont...@bugs.debian.org: > close 920678 10.15.0~dfsg-10 Bug #920678 [src:nodejs] nodejs: FTBFS in Buster Marked as fixed in versions nodejs/10.15.0~dfsg-10. Bug #920678 [src:nodejs] nodejs: FTBFS in Buster Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 920678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's
> Building Tutorial to download and build wpa_supplicant with the changes you
> linked. One exception, I use wpa_supplicant through NetworkManager and could
> not work out where I needed to create a wpa_supplicant.conf, so I changed the
> one line in config.c to:
>
> { INT(no_oper_classes_ie), 1 },
>
> which I'm hoping makes the default "on" instead of "off." Sadly doesn't
> appear to have made a difference, although it didn't make anything worse
> either.
>
> Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my
> desktop this morning and had the same problems with a Qualcomm Atheros AR9462
> Wireless Adapter.
Forwarding Different55’s message from the Debian bug here:
Sure thing! Sadly doesn't seem to make a difference. I've included
another log, this time starting from the time wpa_supplicant was
brought back up to a little bit after I got the popup that the
connection had failed.
Thanks,
Diff
--
Cheers,
Andrej
Jan 27 21:31:57 Empanada systemd[1]: Started WPA supplicant.
Jan 27 21:31:57 Empanada wpa_supplicant[10450]: Successfully initialized wpa_supplicant
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.3679] manager: NetworkManager state is now DISCONNECTED
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6609] sup-iface: failed to remove network: The name :1.742 was not provided by any .service files
Jan 27 21:31:57 Empanada systemd[20774]: Stopping gnome-user-share WebDAV server...
Jan 27 21:31:57 Empanada gsd-sharing[20946]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
Jan 27 21:31:57 Empanada dbus-daemon[570]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=582 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6901] supplicant: wpa_supplicant running
Jan 27 21:31:57 Empanada NetworkManager[582]: [1548646317.6902] device (wls8): supplicant interface state: init -> starting
Jan 27 21:31:57 Empanada systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 27 21:31:57 Empanada systemd[20774]: Stopping Rygel DLNA/UPnP server...
Jan 27 21:31:57 Empanada systemd[20774]: rygel.service: Succeeded.
Jan 27 21:31:57 Empanada systemd[20774]: Stopped Rygel DLNA/UPnP server.
Jan 27 21:31:58 Empanada dbus-daemon[570]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 27 21:31:58 Empanada systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1466] sup-iface[0x55eefa7fecf0,wls8]: supports 5 scan SSIDs
Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1489] device (wls8): supplicant interface state: starting -> ready
Jan 27 21:31:58 Empanada NetworkManager[582]: [1548646318.1490] device (wls8): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 27 21:31:58 Empanada kernel: IPv6: ADDRCONF(NETDEV_UP): wls8: link is not ready
Jan 27 21:31:58 Empanada dbus-daemon[570]: [system] Reloaded configuration
Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:1 'down' [wls8]: new request (1 scripts)
Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:1 'down' [wls8]: start running ordered scripts...
Jan 27 21:31:58 Empanada nm-dispatcher[10462]: req:2 'connectivity-change': new request (1 scripts)
Jan 27 21:31:58 Empanada systemd[20774]: gnome-user-share-webdav.service: Succeeded.
Jan 27 21:31:58 Empanada systemd[20774]: Stopped gnome-user-share WebDAV server.
Jan 27 21:31:59 Empanada nm-dispatcher[10462]: req:2 'connectivity-change': start running ordered scripts...
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: Failed to construct signal
Jan 27 21:32:01 Empanada wpa_supplicant[10450]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed
Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7146] policy: auto-activating connection 'Depeche Modem' (f5750ddc-91b1-4ec7-8ec8-bb7847056796)
Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7158] device (wls8): Activation: starting connection 'Depeche Modem' (f5750ddc-91b1-4ec7-8ec8-bb7847056796)
Jan 27 21:32:01 Empanada NetworkManager[582]: [1548646321.7160] device (wls8): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 27 21:32:01
Bug#919763: adios: armhf FTBFS when built on arm64
Hi Yes, thanka for this patch. I'm reluctant to consider that binaries built on armhf failing on arm64 is an _RC Bug_, but its definitely undesirable. I'll forward the patch to upstream, and let them optimize it better. regards Alastair On 25/01/2019 18:02, Steve Langasek wrote: Package: adios Followup-For: Bug #919763 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Hi Alastair, I'm reopening this bug report because I see that you have closed it by disabling the testsuite. This is a wrong fix for the issue given that the tests are correctly identifying CPU incompatibility in the code. This only results in willingly shipping binaries that will not work on more recent ARM CPUs (and even older CPUs, when using a kernel in a particular mode). If you as maintainer don't want to support adios across the range of CPUs that the Debian armhf port is expected to work on, then it would be better to remove the adios binaries for this architecture instead. (And btw, this issue would also affect sparc64 as an architecture, not only armhf, due to similar alignment constraints.) However, I've just prepared a patch that fixes the unaligned access problems in adios's code. Would you consider applying this as a solution instead? It could stand to be improved - in particular, for cases where we are byteswapping, the code currently writes the variable twice where this could be optimized to be a single write. But I presume the byteswap case is only of interest on big-endian architectures, so not of great concern on modern targets. Thanks for considering, -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.
Bug#920678: [Pkg-javascript-devel] Bug#920678: nodejs: FTBFS in Buster
Le lun. 28 janv. 2019 à 10:42, Ritesh Raj Sarraf a écrit : > Source: nodejs > Version: 8.11.2~dfsg > Severity: serious > Justification: fails to build from source (but built successfully in the > past) > > Dear Maintainer, > > I have been trying to build package nodejs from Buster but it fails to > build. Below is a build failure snippet and the full build log is > attached to this bug report. > > The version in Sid, 10.15.0~dfsg, is building proper. It would really > help if you could confirm the version of nodejs that is intended to be > part of Debian Buster. > It's awaiting migration to testing and that might happen any day now. Jérémy
Bug#920536: Bug #920536 in lintian marked as pending
Control: tag -1 pending Hello, Bug #920536 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/lintian/lintian/commit/73fa0875a285cc1f1eead787e5dd5e29488ad7ba Fix FTBFS by avoiding "self" false-positives when checking for file-references-package-build-path in the Lintian test suite. (Closes: #920536) (this message was generated automatically) -- Greetings https://bugs.debian.org/920536
Processed: Bug #920536 in lintian marked as pending
Processing control commands: > tag -1 pending Bug #920536 [src:lintian] lintian: fails to build because of test failure Added tag(s) pending. -- 920536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920674: rainloop: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/rainloop/rainloop.nginx.conf
Package: rainloop Version: 1.11.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: "Packages must not require the existence of any files in /usr/share/doc/ in order to function." https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. >From the attached log (scroll to the bottom...): Selecting previously unselected package rainloop. (Reading database ... (Reading database ... 9276 files and directories currently installed.) Preparing to unpack .../rainloop_1.11.1-2_all.deb ... Unpacking rainloop (1.11.1-2) ... Setting up rainloop (1.11.1-2) ... cp: cannot stat '/usr/share/doc/rainloop/rainloop.nginx.conf': No such file or directory dpkg: error processing package rainloop (--configure): installed rainloop package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: rainloop Cheers, Andreas rainloop_1.11.1-2.log.gz Description: application/gzip
Bug#919058: My findings
Hi, On Monday, 28 January 2019, Lars Skovlund wrote: > Hmm, moving the files out of the original directory structure and trying from > there works. > This gets weirder and weirder. Indeed, indeed. Thanks for digging into this. Mike -- Sent from my Sailfish device
Bug#920672: marked as done (netdata: Incomplete debian/copyright?)
Your message dated Mon, 28 Jan 2019 09:30:47 +0100 with message-id <1548664247.3149642.1645029560.44b17...@webmail.messagingengine.com> and subject line has caused the Debian Bug report #920672, regarding netdata: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netdata Version: 1.11.1+dfsg-5 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Daniel Baumann , ftpmas...@debian.org Hi, I just ACCEPTed netdata from NEW but noticed it was missing attribution in debian/copyright for at least a bunch of embedded code copies under collectors/python.d.plugin and Alon Bar-Le This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Duplicate of #920671.--- End Message ---
Processed: severity of 920639 is grave
Processing commands for cont...@bugs.debian.org: > severity 920639 grave Bug #920639 [solfege] solfege: Does not start Severity set to 'grave' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 920639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920672: netdata: Incomplete debian/copyright?
Source: netdata Version: 1.11.1+dfsg-5 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Daniel Baumann , ftpmas...@debian.org Hi, I just ACCEPTed netdata from NEW but noticed it was missing attribution in debian/copyright for at least a bunch of embedded code copies under collectors/python.d.plugin and Alon Bar-Le This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#920671: netdata: Incomplete debian/copyright?
Source: netdata Version: 1.11.1+dfsg-5 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Daniel Baumann , ftpmas...@debian.org Hi, I just ACCEPTed netdata from NEW but noticed it was missing attribution in debian/copyright for at least a bunch of embedded code copies under collectors/python.d.plugin, Alon Bar-Lev, etc. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: severity of 920639 is serious
Processing commands for cont...@bugs.debian.org: > severity 920639 serious Bug #920639 [solfege] solfege: Does not start Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 920639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904111: clamav-daemon causing deadlocks/blocking I/O
On Mon, 19 Nov 2018 16:42:35 -0800 Adam Lambert wrote: > Ah, so I think you may have the winner. I set my temp directory to be > something other than /tmp, and turned ClamAV back on, and it's been running > for about an hour now with no obvious ill effects. I will report back if > something else crops up, but I think this may solve it. > > Thank you! > > On Mon, Nov 19, 2018 at 2:31 PM Sebastian Andrzej Siewior > wrote: > > > On 2018-11-19 21:01:07 [+0100], To Adam Lambert wrote: > > > On 2018-11-12 10:17:32 [-0800], Adam Lambert wrote: > > > > I believe I already supplied all that way back when I opened up this > > bug > > > > report. But for reference, here it is again: > > > > > > I tried it back then with no luck. Thanks for the info. I will try to > > > reproduce this asap and get back to you. > > > > Okay. It triggers. This > > > > OnAccessIncludePath /tmp > > > > seems to be the root of all evil. Removing this option or adding > > > > TemporaryDirectory /var/tmp/ > > > > seems to make it go away. So I *think* the problem is that clamav makes > > temporary files during scanning which in turn it tries to scan and > > blocks itself. > > Can you acknowledge the behaviour? Now that there's a clear work-around, I don't think this is critical. I'll downgrade to important. Scott K
Processed: severity of 904111 is important
Processing commands for cont...@bugs.debian.org: > severity 904111 important Bug #904111 [clamav-daemon] clamav-daemon causing deadlocks/blocking I/O. Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 904111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
