Bug#818366: synaptic: fails to start under Wayland
Hi Paul, Paul Gevers wrote: > I am going to raise my question again, if synaptic can't be run on the > default desktop in the default login mode, isn't the average user better > of if we don't ship synaptic with buster? Huh? What kind of logic is that? So any X program which doesn't run under Wayland but does work under X should not be shipped at all? WTF? Of course with these issues, it doesn't make sense to install Synaptic by default. But it's still useful for anyone who doesn't use Wayland, which is AFAIK anyone who has no properly accelerated GPU. And besides: Isn't GNOME/Wayland only on x86 architectures the default, but on any other architecture XFCE (with X I assume) is the default desktop because GNOME doesn't properly work on them? Following the same logic, shouldn't we stop shipping GNOME? Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#924762: further information
The problem occurs also with the current kernel linux-image-4.19.0-4-amd64.
Bug#924762: emacs: commandline with extended characters kills the X server
Package: emacs Version: 1:26.1+1-3.2 Severity: grave Tags: upstream Dear Maintainer, the command "emacs FILENAME", with extended characters in FILENAME, causes the X-server to crash immediately. xdm.log contains: Sun Mar 17 01:43:04 2019 xdm info (pid 7547): sourcing /etc/X11/xdm/Xreset XIO: fatal IO error 4 (Interrupted system call) on X server ":0" after 19 requests (13 known processed) with 0 events remaining. (II) Server terminated successfully (0). Closing log file. To reproduce, type "emacs $(echo -e \\xE4)" in an X-terminal. This does not happen in the console. Also, if emacs --daemon is running," emacsclient -c FILENAME" works fine. I put Severity:grave, because of the potential data loss. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.0.2-00092-ge9de71fc75e3 (SMP w/4 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages emacs depends on: ii emacs-gtk 1:26.1+1-3.2 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#923238: marked as done (libmarc-charset-perl: needs a rebuild on 32bit architectures?)
Your message dated Sun, 17 Mar 2019 00:34:02 + with message-id and subject line Bug#923238: fixed in libmarc-charset-perl 1.35-3 has caused the Debian Bug report #923238, regarding libmarc-charset-perl: needs a rebuild on 32bit architectures? 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.) -- 923238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmarc-charset-perl Version: 1.35-2 Severity: serious Hello, for some reasons the package testsuite started to fail in Ubuntu for this package and xml-perl reverse-dependency, only on armhf and i386. This happened when the new gdbm has been uploaded and rebuilds issued. I traced down the problem to some differences in the march8/utf8 Table generation, I don't know how serious it is, but the testsuite seems completely broken on armhf and i386 at least, and utf8 cjk conversion seems to return wrong values. This is the reason for me opening this bug as "serious". you can see the reports here https://autopkgtest.ubuntu.com/packages/libmarc-xml-perl and https://autopkgtest.ubuntu.com/packages/libmarc-charset-perl perl t/cjk.t 1..1 no mapping found for [0x61] at position 0 in a $1!u`!** z g0=ASCII_DEFAULT g1=EXTENDED_LATIN at /usr/share/perl5/MARC/Charset.pm line 308. not ok 1 - cjk # Failed test 'cjk' # at t/cjk.t line 17. Wide character in print at /usr/share/perl/5.28/Test2/Formatter/TAP.pm line 113. # got: 'a 埇 z' # expected: undef # Looks like you failed 1 test of 1. after a no-change rebuild of the package, and installing it, the test goes passing ok: perl t/cjk.t 1..1 ok 1 - cjk I'm not sure if a no-change rebuild fixes also libmarc-xml-perl and fixes all the test failures, this is something I'm checking right now (but I suppose it will) G. --- End Message --- --- Begin Message --- Source: libmarc-charset-perl Source-Version: 1.35-3 We believe that the bug you reported is fixed in the latest version of libmarc-charset-perl, 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libmarc-charset-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 17 Mar 2019 01:13:44 CET Source: libmarc-charset-perl Binary: Architecture: source Version: 1.35-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Description: Closes: 923238 Changes: libmarc-charset-perl (1.35-3) unstable; urgency=medium . [ gregor herrmann ] * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. * Remove Nathan Handler from Uploaders. Thanks for your work! . [ Alex Muntada ] * Remove inactive pkg-perl members from Uploaders. . [ Salvatore Bonaccorso ] * Update Vcs-* headers for switch to salsa.debian.org . [ intrigeri ] * Declare that debian/rules does not need root. * Declare compliance with Policy 4.1.5. . [ gregor herrmann ] * Add empty debian/tests/pkg-perl/syntax-skip to activate more syntax.t tests. . [ Niko Tyni ] * Depend and Build-Depend on Perl versions that guarantee database binary compatibility with libgdbm6. (Closes: #923238) Checksums-Sha256: 31da1f542b6532e061da29ad906ab0f4c9898192e0a5a07dd5ccac6012f3f863 2367 libmarc-charset-perl_1.35-3.dsc c89bdc1b391cafb45b6c26ea7364a773c0d426c1d60e64e3f677d36902ffa68e 4816 libmarc-charset-perl_1.35-3.debian.tar.xz 5d9fbbb727684e857b1743773415d7102a0b0d5e85f22728c05bc4da6c3c484d 5738 libmarc-charset-perl_1.35-3_sourceonly.buildinfo Checksums-Sha1: 63e819a5f63ff85b8d3c8d44c5141cba59e1caf2 2367 libmarc-charset-perl_1.35-3.dsc ebde371b4331f49ec57ed3c88bf7c05e66a76d22 4816 libmarc-charset-perl_1.35-3.debian.tar.xz 4b2aac03155102d926a08d51350775b6b4188d72 5738 libmarc-charset-perl_1.35-3_sourceonly.buildinfo Files: 9689c9aaca6cdf08d5e0618126ee79fc 2367 perl optional libmarc-charset-perl_1.35-3.dsc af8c4cd5b9a60e15f5779072a108c176 4816 perl optional libmarc-charset-perl_1.35-3.debian.tar.xz
Bug#924755: gnome-user-docs: fails to clean after build: execvp: /bin/bash: Argument list too long
On Sat, Mar 16, 2019 at 6:40 PM Andreas Beckmann wrote: > Version: 3.32.0-1 > Severity: serious > Justification: fails to build from source I question the severity you have assigned to this issue. As I assume you're aware, by marking the bug as "serious, version 3.32.0-1", you will prevent newer versions from reaching Testing once we finally start pushing GNOME 3.32 stuff to Unstable. I question if there is anywhere in policy that says a package has to build twice in a row. That's obviously not needed for the official buildds. And I question whether this issue is new in 3.32. I suggest we downgrade this issue to "important". I recommend that you also report this issue to GNOME. I have ported gnome-user-docs to meson a good while ago, but it hasn't been accepted yet because the GNOME doc websites don't handle cmake & meson modules well yet. There's a good chance switching to meson would fix this issue. Thanks, Jeremy Bicha
Bug#924756: libg3d: fails to clean after build
Source: libg3d Version: 0.0.8-27 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, libg3d/experimental fails to build twice in a row because cleaning after the first (and successful) build fails: fakeroot debian/rules clean dh clean --without autoreconf debian/rules override_dh_auto_clean make[1]: Entering directory '/build/libg3d-0.0.8' rm -rf "/build/libg3d-0.0.8/build" make[1]: Leaving directory '/build/libg3d-0.0.8' dh_clean dh_clean: mv debian/.debhelper/bucket/files/19c12bb2ca19e68724c2854ed0512469518df19b0710cc2011a5ca540810979c.tmp build/config/config.guess: No such file or directory make: *** [debian/rules:20: clean] Error 2 Andreas libg3d_0.0.8-27_twice.log.gz Description: application/gzip
Bug#924206: marked as done (rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`))
Your message dated Sat, 16 Mar 2019 22:20:19 +
with message-id
and subject line Bug#924206: fixed in rust-opener 0.3.2-1
has caused the Debian Bug report #924206,
regarding rust-opener: FTBFS (method `name` is not a member of trait
`failure::Fail`)
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.)
--
924206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rust-opener
Version: 0.3.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --buildsystem cargo
dh_update_autotools_config -a -O--buildsystem=cargo
dh_autoreconf -a -O--buildsystem=cargo
dh_auto_configure -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel: ['parallel=1'] [] ['-j1']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<>/debian/cargo_registry/
dh_auto_build -a -O--buildsystem=cargo
dh_auto_test -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel: ['parallel=1'] [] ['-j1']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j1',
'--target', 'x86_64-unknown-linux-gnu'],) {}
Compiling proc-macro2 v0.4.27
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/proc-macro2-0.4.27/build.rs --color
never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
'feature="default"' --cfg 'feature="proc-macro"' -C metadata=4386f0ca6bd23fd4
-C extra-filename=-4386f0ca6bd23fd4 --out-dir
/<>/target/debug/build/proc-macro2-4386f0ca6bd23fd4 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling unicode-xid v0.1.0
Running `rustc --crate-name unicode_xid
/<>/debian/cargo_registry/unicode-xid-0.1.0/src/lib.rs --color
never --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg
'feature="default"' -C metadata=d0685fa25ab49bda -C
extra-filename=-d0685fa25ab49bda --out-dir /<>/target/debug/deps
-L dependency=/<>/target/debug/deps --cap-lints warn`
Compiling libc v0.2.48
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/libc-0.2.48/build.rs --color never
--crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=c9e8a1016dba7752 -C extra-filename=-c9e8a1016dba7752 --out-dir
/<>/target/debug/build/libc-c9e8a1016dba7752 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling backtrace-sys v0.1.28
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/backtrace-sys-0.1.28/build.rs --color
never --crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=752798b597b87583 -C extra-filename=-752798b597b87583 --out-dir
/<>/target/debug/build/backtrace-sys-752798b597b87583 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling autocfg v0.1.1
Running `rustc --crate-name autocfg
/<>/debian/cargo_registry/autocfg-0.1.1/src/lib.rs --color never
--crate-type lib --emit=dep-info,link -C debuginfo=2 -C
metadata=ff9a63bf38561cff -C extra-filename=-ff9a63bf38561cff --out-dir
/<>/target/debug/deps -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling failure_derive v0.1.5
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/failure_derive-0.1.5/build.rs --color
never --crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=4b7e5641c6406b41 -C extra-filename=-4b7e5641c6406b41 --out-dir
/<>/target/debug/build/failure_derive-4b7e5641c6406b41 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling rustc-demangle v0.1.13
Running `rustc --crate-name rustc_demangle
/<>/debian/cargo_registry/rustc-demangle-0.1.13/src/lib.rs --color
never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
metadata=0be214a18526b2cc -C extra-filename=-0be214a18526b2cc --out-dir
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -L
dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
dependency=/<>/target/debug/deps --cap-lints warn -C debuginfo=2
--cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
--remap-path-prefix /<>=/usr/share/cargo/registry/opener-0.3.0`
Compiling cfg-if v0.1.6
Bug#924206: marked as done (rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`))
Your message dated Sat, 16 Mar 2019 21:32:00 +
with message-id
and subject line Re: Bug#924206: rust-opener: FTBFS (method `name` is not a
member of trait `failure::Fail`)
has caused the Debian Bug report #924206,
regarding rust-opener: FTBFS (method `name` is not a member of trait
`failure::Fail`)
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.)
--
924206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rust-opener
Version: 0.3.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --buildsystem cargo
dh_update_autotools_config -a -O--buildsystem=cargo
dh_autoreconf -a -O--buildsystem=cargo
dh_auto_configure -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel: ['parallel=1'] [] ['-j1']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<>/debian/cargo_registry/
dh_auto_build -a -O--buildsystem=cargo
dh_auto_test -a -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel: ['parallel=1'] [] ['-j1']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j1',
'--target', 'x86_64-unknown-linux-gnu'],) {}
Compiling proc-macro2 v0.4.27
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/proc-macro2-0.4.27/build.rs --color
never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
'feature="default"' --cfg 'feature="proc-macro"' -C metadata=4386f0ca6bd23fd4
-C extra-filename=-4386f0ca6bd23fd4 --out-dir
/<>/target/debug/build/proc-macro2-4386f0ca6bd23fd4 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling unicode-xid v0.1.0
Running `rustc --crate-name unicode_xid
/<>/debian/cargo_registry/unicode-xid-0.1.0/src/lib.rs --color
never --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg
'feature="default"' -C metadata=d0685fa25ab49bda -C
extra-filename=-d0685fa25ab49bda --out-dir /<>/target/debug/deps
-L dependency=/<>/target/debug/deps --cap-lints warn`
Compiling libc v0.2.48
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/libc-0.2.48/build.rs --color never
--crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=c9e8a1016dba7752 -C extra-filename=-c9e8a1016dba7752 --out-dir
/<>/target/debug/build/libc-c9e8a1016dba7752 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling backtrace-sys v0.1.28
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/backtrace-sys-0.1.28/build.rs --color
never --crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=752798b597b87583 -C extra-filename=-752798b597b87583 --out-dir
/<>/target/debug/build/backtrace-sys-752798b597b87583 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling autocfg v0.1.1
Running `rustc --crate-name autocfg
/<>/debian/cargo_registry/autocfg-0.1.1/src/lib.rs --color never
--crate-type lib --emit=dep-info,link -C debuginfo=2 -C
metadata=ff9a63bf38561cff -C extra-filename=-ff9a63bf38561cff --out-dir
/<>/target/debug/deps -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling failure_derive v0.1.5
Running `rustc --crate-name build_script_build
/<>/debian/cargo_registry/failure_derive-0.1.5/build.rs --color
never --crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=4b7e5641c6406b41 -C extra-filename=-4b7e5641c6406b41 --out-dir
/<>/target/debug/build/failure_derive-4b7e5641c6406b41 -L
dependency=/<>/target/debug/deps --cap-lints warn`
Compiling rustc-demangle v0.1.13
Running `rustc --crate-name rustc_demangle
/<>/debian/cargo_registry/rustc-demangle-0.1.13/src/lib.rs --color
never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
metadata=0be214a18526b2cc -C extra-filename=-0be214a18526b2cc --out-dir
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -L
dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
dependency=/<>/target/debug/deps --cap-lints warn -C debuginfo=2
--cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
--remap-path-prefix
Bug#838903: A note about switching to the new "Command" applet
FTR, I added a little note that might help anyone wanting to switch to the "Command" applet from command-runner-applet: https://github.com/porridge/command-runner-applet/blob/master/README#L15-L18
Processed: Unarchiving to add a note
Processing commands for cont...@bugs.debian.org:
> unarchive 838903
Bug #838903 {Done: Debian FTP Masters }
[command-runner-applet] command-runner-applet: Incompatible with upcoming
gnome-panel 3.22
Unarchived Bug 838903
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
838903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#740893: ‘libjs-jquery-hotkeys’ 0.2.0 works with ‘python-coverage’
Hi, On Wed, 13 Mar 2019 12:44:37 +1100 Ben Finney wrote: > On 10-Oct-2018, Thomas Goirand wrote: > > I've prepared an update of this package to the version available at: > > https://github.com/jeresig/jquery.hotkeys > > > > Can you please try? > > Testing this manually, I find that the “0.2.0” version you've prepared > means that it works for the dependency in ‘python-coverage’ for > hotkeys support. > > Are there more checks you would like to be done? Please be aware that one of the reverse-dependencies of libjs-jquery-hotkeys is cacti, which uses the tzuryby version upstream. I haven't investigated, but I expect that replacing libjs-jquery-hotkeys with the jeresig version is going to break cacti. If I understand this bug properly, I think Debian could/should have two versions of libjs-jquery-hotkeys, one for each upstream. If that is correct, than it is too late in the release cycle to fix this issue if we keep in mind that it is already 5 years old and present in stable releases. Paul signature.asc Description: OpenPGP digital signature
Processed: found 924346 in 1.5.3-2+deb8u3, fixed 924346 in 1.5.3-2+deb8u4, fixed 924346 in 1.6.0-4+deb9u2
Processing commands for cont...@bugs.debian.org:
> found 924346 1.5.3-2+deb8u3
Bug #924346 {Done: Ferenc Wágner } [src:xmltooling]
xmltooling: CVE-2019-9628: XML parser class fails to trap exceptions on
malformed XML declaration
Marked as found in versions xmltooling/1.5.3-2+deb8u3.
> fixed 924346 1.5.3-2+deb8u4
Bug #924346 {Done: Ferenc Wágner } [src:xmltooling]
xmltooling: CVE-2019-9628: XML parser class fails to trap exceptions on
malformed XML declaration
The source 'xmltooling' and version '1.5.3-2+deb8u4' do not appear to match any
binary packages
Marked as fixed in versions xmltooling/1.5.3-2+deb8u4.
> fixed 924346 1.6.0-4+deb9u2
Bug #924346 {Done: Ferenc Wágner } [src:xmltooling]
xmltooling: CVE-2019-9628: XML parser class fails to trap exceptions on
malformed XML declaration
Marked as fixed in versions xmltooling/1.6.0-4+deb9u2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
924346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module
Control: severity -1 minor Try switching to legacy-390xx, or removing bbswitch and using the kernel's power management, with these laptops it's always a dice roll on what will actually work On Sat, 2019-03-16 at 14:19 -0400, Danfun360 wrote: > The graphics card in my laptop is an Nvidia Geforce GTX 1050. > > On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi m> > wrote: > > > What Nvidia card does your laptop have? > > > > On Sat, 16 Mar 2019, 03:42 Daniel O. > > > > Package: bumblebee-nvidia > > > Version: 3.2.1-20 > > > Severity: grave > > > Justification: renders package unusable > > > > > > Dear Maintainer, I write this bug report because this > > > bumblebee/bumblebeed > > > doesn't work as it should. > > > > > > * What led up to the situation? Bumblebee used to work > > > correctly when > > > the > > > nvidia driver was at 390. A few days ago it was upgraded to 410. > > > At the > > > time I > > > was running Debian Buster (testing as of this writing). That's > > > where > > > things > > > started to get problematic. It appears that the nvidia module > > > couldn't be > > > unloaded or something. bbswitch reported as "ON" without optirun, > > > and as > > > the > > > nvidia drivers were considered in use, I was unable to unbind the > > > nvidia > > > driver > > > for VGA Passthrough as I had been doing before. > > > * What exactly did you do (or not do) that was effective (or > > > ineffective)? I uninstalled every bumblebee and nvidia > > > package. I > > > then > > > reinstalled everything. No luck. I then uninstalled everything > > > and went > > > for the > > > legacy 390 package. Unfortunately there were problems with that: > > > nvidia-cuba- > > > toolkit and nvidia-cuba-dev require the latest nvidia driver > > > installed. > > > On top > > > of that, bumblebee refused to see the legacy 390 drivers as a glx > > > alternative. > > > I uninstalled all the nvidia stuff again, switched to Debian Sid, > > > and > > > installed > > > the latest nvidia drivers again (they were slightly more up to > > > date on > > > Sid than > > > in Buster). Still no change. > > > * What was the outcome of this action? Bumblebee should be > > > able to > > > blacklist > > > the nvidia driver and isolate it from the operating system in > > > such a way > > > that > > > the system would run on the integrated GPU and run the discrete > > > GPU for > > > applications when called for. > > > * What outcome did you expect instead? The nvidia driver is > > > not > > > blacklisted, > > > and the discrete GPU is in control. > > > > > > On a different note, I tried posting a bug report upstream. It > > > has some > > > information this report might not have (vice versa is definitely > > > the case, > > > unfortunately). It can be found at https://github.com/Bumblebee- > > > Project/Bumblebee/issues/1023 > > > > > > > > > > > > -- System Information: > > > Debian Release: buster/sid > > > APT prefers unstable > > > APT policy: (500, 'unstable') > > > 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 > > > > > > Versions of packages bumblebee-nvidia depends on: > > > ii bumblebee 3.2.1-20 > > > ii glx-alternative-nvidia 0.9.1 > > > ii nvidia-driver 410.104-1 > > > ii nvidia-kernel-dkms 410.104-1 > > > > > > bumblebee-nvidia recommends no packages. > > > > > > bumblebee-nvidia suggests no packages. > > > > > > -- no debconf information > > > > > > ___ > > > pkg-nvidia-devel mailing list > > > pkg-nvidia-de...@alioth-lists.debian.net > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvid > > > ia-devel > > > > -- Kind regards, Luca Boccassi
Processed: Re: Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module
Processing control commands: > severity -1 minor Bug #924704 [bumblebee-nvidia] bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module Severity set to 'minor' from 'grave' -- 924704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)
Please do not remove this package, the first CI builds (MinGW cross builds) already break (GNU Wget / Wget2). Well, it's already gone from buster... please add it back or provide a another way to convert charsets within cross-compiled Windows executables. Regards, Tim signature.asc Description: OpenPGP digital signature
Bug#924747: ruby-doorkeeper-openid-connect: CVE-2019-9837
Source: ruby-doorkeeper-openid-connect Version: 1.5.2-1 Severity: grave Tags: security upstream Forwarded: https://github.com/doorkeeper-gem/doorkeeper-openid_connect/issues/61 Hi, The following vulnerability was published for ruby-doorkeeper-openid-connect. CVE-2019-9837[0]: | Doorkeeper::OpenidConnect (aka the OpenID Connect extension for | Doorkeeper) 1.4.x and 1.5.x before 1.5.4 has an open redirect via the | redirect_uri field in an OAuth authorization request (that results in | an error response) with the 'openid' scope and a prompt=none value. | This allows phishing attacks against the authorization flow. 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-9837 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9837 [1] https://github.com/doorkeeper-gem/doorkeeper-openid_connect/issues/61 [2] https://github.com/doorkeeper-gem/doorkeeper-openid_connect/pull/66 Regards, Salvatore
Bug#924744: cockpit: fails to clean after build: find: './dist': No such file or directory
Source: cockpit Version: 189-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, cockpit/experimental fails to build twice in a row because the clean target fails after the package was build successfully: fakeroot debian/rules clean dh clean dh_auto_clean make -j3 distclean make[1]: Entering directory '/build/cockpit-189' test -z "cockpit-bridge" || rm -f cockpit-bridge test -z "test-server" || rm -f test-server test -z "doc/man/cockpit-bridge.1 doc/man/cockpit.1 doc/man/cockpit-desktop.1 doc/man/cockpit-ws.8 doc/man/cockpit.conf.5 doc/man/pam_ssh_add.8 doc/man/remotectl.8 valgrind-suppressions dist/apps/stamp dist/das test -z " cockpit-askpass cockpit-stub cockpit-pcp cockpit-ssh cockpit-ws cockpit-session" || rm -f cockpit-askpass cockpit-stub cockpit-pcp cockpit-ssh cockpit-ws cockpit-session find . -name '*.gc??' -delete test -z "libcockpit-stub.a libcockpit-bridge.a libcockpit-pcp.a libcockpit-common.a libwebsocket.a libcockpit-ssh.a libcockpit-ws.a libretest.a libpam_ssh_add.a" || rm -f libcockpit-stub.a libcockpit-bridge.a li test -z "test-paths test-rules test-pipe-channel test-packages test-peer test-dbus-meta test-fs test-metrics test-connect test-stream test-httpstream test-setup test-websocketstream test-process test-bridge test-r test -z "remotectl" || rm -f remotectl rm -f *.o rm -f src/bridge/*.o rm -f src/common/*.o rm -f src/pam-ssh-add/*.o rm -f src/retest/*.o rm -f src/ssh/*.o test -z "pkg/users/test-list-public-keys.log dist/base1/test-base64.log dist/base1/test-utf8.log dist/base1/test-events.log dist/base1/test-chan.log dist/base1/test-dbus.log dist/base1/test-dbus-address.log dist/b rm -f src/websocket/*.o rm -f src/ws/*.o rm -f *.tab.c test -z "pkg/users/test-list-public-keys.trs dist/base1/test-base64.trs dist/base1/test-utf8.trs dist/base1/test-events.trs dist/base1/test-chan.trs dist/base1/test-dbus.trs dist/base1/test-dbus-address.trs dist/b test -z "doc/guide/version" || rm -f doc/guide/version test . = "." || test -z "" || rm -f rm -f src/bridge/.deps/.dirstamp test -z "test-suite.log" || rm -f test-suite.log rm -f src/bridge/.dirstamp find . -name '*.pyc' -delete rm -f src/common/.deps/.dirstamp rm -f config.h stamp-h1 rm -f src/common/.dirstamp rm -rf dist/ rm -f src/pam-ssh-add/.deps/.dirstamp rm -f src/pam-ssh-add/.dirstamp rm -f src/retest/.deps/.dirstamp rm -f src/retest/.dirstamp rm -f src/ssh/.deps/.dirstamp rm -f src/ssh/.dirstamp rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags rm -f src/websocket/.deps/.dirstamp rm -f cscope.out cscope.in.out cscope.po.out cscope.files rm -f src/websocket/.dirstamp rm -f src/ws/.deps/.dirstamp rm -f src/ws/.dirstamp test -z "./Makefile node_modules cockpit-cache-*.tar.xz " || rm -f ./Makefile node_modules cockpit-cache-*.tar.xz rm: cannot remove 'node_modules': Is a directory make[1]: [Makefile:8857: distclean-generic] Error 1 (ignored) find: './dist': No such file or directory make[1]: *** [Makefile:9446: clean-local] Error 1 make[1]: Leaving directory '/build/cockpit-189' dh_auto_clean: make -j3 distclean returned exit code 2 make: *** [debian/rules:18: clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 The dist directory tree has been deleted a few statements earlier ... Andreas cockpit_189-1_twice.log.gz Description: application/gzip
Processed: tagging 917708, reassign 878770 to src:mono, fixed 878770 in 5.16.0.220+dfsg3-1 ..., affects 916567 ...
Processing commands for cont...@bugs.debian.org:
> tags 917708 + experimental
Bug #917708 {Done: Jeremy Bicha }
[src:gnome-settings-daemon] gnome-settings-daemon: FTBFS: dh_auto_test: cd
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned
exit code 1
Added tag(s) experimental.
> reassign 878770 src:mono 4.6.2.7+dfsg-1
Bug #878770 {Done: Jo Shields } [mono-dmcs] please drop
transitional package mono-dmcs
Bug reassigned from package 'mono-dmcs' to 'src:mono'.
No longer marked as found in versions mono/4.6.2.7+dfsg-1.
No longer marked as fixed in versions mono/5.16.0.220+dfsg3-1.
Bug #878770 {Done: Jo Shields } [src:mono] please drop
transitional package mono-dmcs
Marked as found in versions mono/4.6.2.7+dfsg-1.
> fixed 878770 5.16.0.220+dfsg3-1
Bug #878770 {Done: Jo Shields } [src:mono] please drop
transitional package mono-dmcs
Marked as fixed in versions mono/5.16.0.220+dfsg3-1.
> reassign 916567 src:golang-github-juju-utils
Bug #916567 {Done: Alexandre Viau }
[golang-github-juju-testing-dev] golang-github-juju-testing-dev: depends on the
removed golang-github-juju-utils-dev
Bug reassigned from package 'golang-github-juju-testing-dev' to
'src:golang-github-juju-utils'.
No longer marked as found in versions
golang-github-juju-testing/0.0~git20170608.2fe0e88-3.
No longer marked as fixed in versions
golang-github-juju-utils/0.0~git20171220.f38c0b0-5.
> fixed 916567 0.0~git20171220.f38c0b0-5
Bug #916567 {Done: Alexandre Viau }
[src:golang-github-juju-utils] golang-github-juju-testing-dev: depends on the
removed golang-github-juju-utils-dev
Marked as fixed in versions golang-github-juju-utils/0.0~git20171220.f38c0b0-5.
> affects 916567 + golang-github-juju-testing-dev
Bug #916567 {Done: Alexandre Viau }
[src:golang-github-juju-utils] golang-github-juju-testing-dev: depends on the
removed golang-github-juju-utils-dev
Added indication that 916567 affects golang-github-juju-testing-dev
> reassign 917004 src:emacs-non-dfsg
Bug #917004 {Done: Rob Browning } [emacs] emacs: Emacs
26 lacks its manual
Bug #918528 {Done: Rob Browning } [emacs] Suggesting
non-existent package emacs-common-non-dfsg
Bug reassigned from package 'emacs' to 'src:emacs-non-dfsg'.
Bug reassigned from package 'emacs' to 'src:emacs-non-dfsg'.
No longer marked as found in versions emacs/1:26.1+1-2.
No longer marked as found in versions emacs/1:26.1+1-2.
No longer marked as fixed in versions emacs-non-dfsg/1:26.1+1-1.
No longer marked as fixed in versions emacs-non-dfsg/1:26.1+1-1.
> fixed 917004 1:26.1+1-1
Bug #917004 {Done: Rob Browning } [src:emacs-non-dfsg]
emacs: Emacs 26 lacks its manual
Bug #918528 {Done: Rob Browning } [src:emacs-non-dfsg]
Suggesting non-existent package emacs-common-non-dfsg
Marked as fixed in versions emacs-non-dfsg/1:26.1+1-1.
Marked as fixed in versions emacs-non-dfsg/1:26.1+1-1.
> reassign 916147 src:rng-tools-debian
Bug #916147 {Done: Thorsten Glaser } [src:rng-tools] rng-tools:
replaced with inferior version
Bug reassigned from package 'src:rng-tools' to 'src:rng-tools-debian'.
No longer marked as found in versions rng-tools/5-1.
No longer marked as fixed in versions rng-tools-debian/2-unofficial-mt.14-2.
> fixed 916147 2-unofficial-mt.14-2
Bug #916147 {Done: Thorsten Glaser } [src:rng-tools-debian]
rng-tools: replaced with inferior version
Marked as fixed in versions rng-tools-debian/2-unofficial-mt.14-2.
> affects 916147 + src:rng-tool
Bug #916147 {Done: Thorsten Glaser } [src:rng-tools-debian]
rng-tools: replaced with inferior version
Added indication that 916147 affects src:rng-tool
> reassign 908632 firmware-amd-graphics
Bug #908632 {Done: Ben Hutchings } [src:linux] amdgpu
uses wrong firmware paths for SI/CIK
Bug reassigned from package 'src:linux' to 'firmware-amd-graphics'.
No longer marked as found in versions linux/4.19~rc3-1~exp1.
No longer marked as fixed in versions firmware-nonfree/20190114-1.
> fixed 908632 20190114-1
Bug #908632 {Done: Ben Hutchings }
[firmware-amd-graphics] amdgpu uses wrong firmware paths for SI/CIK
Marked as fixed in versions firmware-nonfree/20190114-1.
> notfound 685295 2.00-7
Bug #685295 {Done: Bernhard Übelacker } [grub-ieee1275]
grub crashes with invalid memory access
No longer marked as found in versions grub2/2.00-7.
> notfixed 910863 1:6.1.4~
Bug #910863 {Done: Samuel Thibault } [libreoffice]
LibreOffice no longer providing formatting information to Orca when "Orca
MOdifier Key + f" is used
There is no source info for the package 'libreoffice' at version '1:6.1.4~'
with architecture ''
Unable to make a source version for version '1:6.1.4~'
No longer marked as fixed in versions 1:6.1.4~.
> fixed 910863 1:6.1.4-1
Bug #910863 {Done: Samuel Thibault } [libreoffice]
LibreOffice no longer providing formatting information to Orca when "Orca
MOdifier Key + f" is used
Marked as fixed in versions libreoffice/1:6.1.4-1.
> reassign 584924 src:webpy 1:0.34-2
Bug #584924 {Done: deba...@debian.org (W. Martin Borgert)}
Bug#924734: marked as done (libbpp-seq-omics: FTBFS (dh_makeshlibs fails))
Your message dated Sat, 16 Mar 2019 18:34:35 + with message-id and subject line Bug#924734: fixed in libbpp-seq-omics 2.4.1-3 has caused the Debian Bug report #924734, regarding libbpp-seq-omics: FTBFS (dh_makeshlibs fails) 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.) -- 924734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq-omics Version: 2.4.1-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 dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. -- The CXX compiler identification is GNU 8.3.0 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- bpp-core 4.1.0 found: [... snipped ...] _ZTv0_n24_N3bpp13BasicSequenceD0Ev@Base 2.4.1 @@ -1134,7 +1150,9 @@ _ZTv0_n48_N3bpp25SimpleMafStatisticsResult8setValueERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 2.4.1 _ZTv0_n48_N3bpp36CsvStatisticsOutputIterationListener14iterationStopsEv@Base 2.4.1 _ZTv0_n48_NK3bpp12EdSymbolList11getAlphabetEv@Base 2.4.1 + _ZTv0_n48_NK3bpp12SequenceMask11isRemovableEv@Base 2.4.1-2 _ZTv0_n48_NK3bpp15SequenceQuality11isRemovableEv@Base 2.4.1 + _ZTv0_n48_NK3bpp20AbstractCoreSequence7getNameB5cxx11Ev@Base 2.4.1-2 _ZTv0_n48_NK3bpp21AbstractMafStatistics9getResultEv@Base 2.4.1 _ZTv0_n48_NK3bpp22SequenceWithAnnotation7getNameB5cxx11Ev@Base 2.4.1 _ZTv0_n48_NK3bpp25AbstractSequenceContainer11getAlphabetEv@Base 2.4.1 @@ -1144,6 +1162,7 @@ _ZTv0_n56_N3bpp16GtfFeatureReader17getFeaturesOfTypeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 _ZTv0_n56_N3bpp17SiteMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 _ZTv0_n56_N3bpp19AbstractMafIterator20addIterationListenerEPNS_17IterationListenerE@Base 2.4.1 + _ZTv0_n56_N3bpp20AbstractCoreSequence7setNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1-2 _ZTv0_n56_N3bpp21BedGraphFeatureReader17getFeaturesOfTypeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 _ZTv0_n56_N3bpp22SequenceWithAnnotation7setNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 _ZTv0_n56_N3bpp25PolymorphismMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 @@ -1153,6 +1172,7 @@ _ZTv0_n56_N3bpp34SiteFrequencySpectrumMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 _ZTv0_n56_N3bpp37FourSpeciesPatternCountsMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 _ZTv0_n56_NK3bpp12EdSymbolList4sizeEv@Base 2.4.1 + _ZTv0_n56_NK3bpp12SequenceMask8isSharedEv@Base 2.4.1-2 _ZTv0_n56_NK3bpp15BasicSymbolList4sizeEv@Base 2.4.1 _ZTv0_n56_NK3bpp15SequenceQuality8isSharedEv@Base 2.4.1 _ZTv0_n64_N3bpp16GffFeatureReader21getFeaturesOfSequenceERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 @@ -1160,12 +1180,14 @@ _ZTv0_n64_N3bpp21BedGraphFeatureReader21getFeaturesOfSequenceERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 _ZTv0_n64_N3bpp22SequenceWithAnnotation10setContentERKSt6vectorIiSaIiEE@Base 2.4.1 _ZTv0_n64_NK3bpp17SiteMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 + _ZTv0_n64_NK3bpp20AbstractCoreSequence11getCommentsB5cxx11Ev@Base 2.4.1-2 _ZTv0_n64_NK3bpp22SequenceWithAnnotation11getCommentsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp25PolymorphismMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp28CharacterCountsMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp30SequenceDiversityMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp34SiteFrequencySpectrumMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp37FourSpeciesPatternCountsMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 +
Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module
The graphics card in my laptop is an Nvidia Geforce GTX 1050. On Sat, Mar 16, 2019 at 7:20 AM Luca Boccassi wrote: > What Nvidia card does your laptop have? > > On Sat, 16 Mar 2019, 03:42 Daniel O. >> Package: bumblebee-nvidia >> Version: 3.2.1-20 >> Severity: grave >> Justification: renders package unusable >> >> Dear Maintainer, I write this bug report because this bumblebee/bumblebeed >> doesn't work as it should. >> >>* What led up to the situation? Bumblebee used to work correctly when >> the >> nvidia driver was at 390. A few days ago it was upgraded to 410. At the >> time I >> was running Debian Buster (testing as of this writing). That's where >> things >> started to get problematic. It appears that the nvidia module couldn't be >> unloaded or something. bbswitch reported as "ON" without optirun, and as >> the >> nvidia drivers were considered in use, I was unable to unbind the nvidia >> driver >> for VGA Passthrough as I had been doing before. >>* What exactly did you do (or not do) that was effective (or >> ineffective)? I uninstalled every bumblebee and nvidia package. I >> then >> reinstalled everything. No luck. I then uninstalled everything and went >> for the >> legacy 390 package. Unfortunately there were problems with that: >> nvidia-cuba- >> toolkit and nvidia-cuba-dev require the latest nvidia driver installed. >> On top >> of that, bumblebee refused to see the legacy 390 drivers as a glx >> alternative. >> I uninstalled all the nvidia stuff again, switched to Debian Sid, and >> installed >> the latest nvidia drivers again (they were slightly more up to date on >> Sid than >> in Buster). Still no change. >>* What was the outcome of this action? Bumblebee should be able to >> blacklist >> the nvidia driver and isolate it from the operating system in such a way >> that >> the system would run on the integrated GPU and run the discrete GPU for >> applications when called for. >>* What outcome did you expect instead? The nvidia driver is not >> blacklisted, >> and the discrete GPU is in control. >> >> On a different note, I tried posting a bug report upstream. It has some >> information this report might not have (vice versa is definitely the case, >> unfortunately). It can be found at https://github.com/Bumblebee- >> Project/Bumblebee/issues/1023 >> >> >> >> -- System Information: >> Debian Release: buster/sid >> APT prefers unstable >> APT policy: (500, 'unstable') >> 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 >> >> Versions of packages bumblebee-nvidia depends on: >> ii bumblebee 3.2.1-20 >> ii glx-alternative-nvidia 0.9.1 >> ii nvidia-driver 410.104-1 >> ii nvidia-kernel-dkms 410.104-1 >> >> bumblebee-nvidia recommends no packages. >> >> bumblebee-nvidia suggests no packages. >> >> -- no debconf information >> >> ___ >> pkg-nvidia-devel mailing list >> pkg-nvidia-de...@alioth-lists.debian.net >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel > >
Bug#924327: marked as done (directfb FTBFS for armel,armhf: error: implicit declaration of function 'makedev')
Your message dated Sat, 16 Mar 2019 17:19:13 + with message-id and subject line Bug#924327: fixed in directfb 1.7.7-9 has caused the Debian Bug report #924327, regarding directfb FTBFS for armel,armhf: error: implicit declaration of function 'makedev' 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.) -- 924327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: directfb Version: 1.7.7-8 Severity: serious Tags: ftbfs User: helm...@debian.org Usertags: rebootstrap directfb has build failures. A cross build for armel fails: http://crossqa.subdivi.de/build/directfb_1.7.7-8_armel_20190223000250.log | /bin/bash ../../libtool --tag=CC --mode=compile arm-linux-gnueabi-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../../lib -I../../include -I../../lib -I../../src -I../../systems -I./kernel-module/include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-strict-aliasing -Werror-implicit-function-declaration -O3 -g2 -ffast-math -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -std=gnu99 -Werror-implicit-function-declaration -c -o davinci_c64x.lo davinci_c64x.c | libtool: compile: arm-linux-gnueabi-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../../lib -I../../include -I../../lib -I../../src -I../../systems -I./kernel-module/include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-strict-aliasing -Werror-implicit-function-declaration -O3 -g2 -ffast-math -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -std=gnu99 -Werror-implicit-function-declaration -c davinci_c64x.c -fPIC -DPIC -o .libs/davinci_c64x.o | davinci_c64x.c: In function 'davinci_c64x_open': | davinci_c64x.c:1902:42: error: implicit declaration of function 'makedev' [-Werror=implicit-function-declaration] | mknod( C64X_DEVICE, 0666 | S_IFCHR, makedev( 400, 0 ) ); | ^~~ | cc1: some warnings being treated as errors It is very likely that this failure is a native failure as well. A native build for armhf fails in the same way: https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/directfb_1.7.7-8.rbuild.log.gz | davinci_c64x.c: In function 'davinci_c64x_open': | davinci_c64x.c:1902:42: error: implicit declaration of function 'makedev' [-Werror=implicit-function-declaration] | mknod( C64X_DEVICE, 0666 | S_IFCHR, makedev( 400, 0 ) ); | ^~~ So directfb presently fails to build on armhf and fails to cross build for armel in the very same way. Most likely it FTBFS on two release architectures. Helmut --- End Message --- --- Begin Message --- Source: directfb Source-Version: 1.7.7-9 We believe that the bug you reported is fixed in the latest version of directfb, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated directfb 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: Sat, 16 Mar 2019 17:29:57 +0100 Source: directfb Architecture: source Version: 1.7.7-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 924327 Changes: directfb (1.7.7-9) unstable; urgency=medium . * QA upload. * Add missing #include to ensure makedev() is defined. (Closes: #924327) Checksums-Sha1: 0690afd7cf2926dfdab15d70efa9f5b45f4a88a3 2817 directfb_1.7.7-9.dsc 9bbf5db8082fa6588ff31c88aabc2fbf900ae289 25640 directfb_1.7.7-9.debian.tar.xz 2c3aca9a4d087fefcbdd58a873d32f873b364d41 7893 directfb_1.7.7-9_source.buildinfo Checksums-Sha256: db30febca0377aa90c41344b4fb70bc55624ddd0e69ad81a3bd144adeb9146fb 2817 directfb_1.7.7-9.dsc 0b1b6d2303b49c4e91acc41cb60d37816369bc2531393aafb4859bb7b0aa08d4 25640 directfb_1.7.7-9.debian.tar.xz 6553e00d91b732125646e2d81ca1835d62911e644eda9eb2c3602fc6a005d146 7893
Bug#924047: marked as done (FTBFS: package don't build successful after new GCC version)
Your message dated Sat, 16 Mar 2019 18:13:37 +0100 with message-id <20190316171337.ga9...@x260.cruise.homelinux.net> and subject line Re: Bug#924047: FTBFS: package don't build successful after new GCC version has caused the Debian Bug report #924047, regarding FTBFS: package don't build successful after new GCC version 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.) -- 924047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:systemc Version: 2.3.3-1 Severity: grave Hello Ahmed, the systemc package is currently failing to build from source basically related due a newer GCC version and changed symbols introduced by the newer GCC. I've fixed the reason of the FTBFS by modifying and adopting the symbols file so the package is building again on all RC platforms. I've pushed the adopted symbols file to Salsa after I've tested the builds. If you can also have a look on a update of Standards-Version to 4.3.0 and prepare a new changelog entry I can offer a sponsored upload. I see no problem with a later unblock request so the updated package can go into the Buster release. Regards Carsten -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 2.3.3-2 Just close this report as it was fixed by the uploaded version. Regards Carsten--- End Message ---
Bug#924719: marked as done (perl: Break libmarc-charset-perl (<< 1.35-3))
Your message dated Sat, 16 Mar 2019 17:05:01 + with message-id and subject line Bug#924719: fixed in perl 5.28.1-5 has caused the Debian Bug report #924719, regarding perl: Break libmarc-charset-perl (<< 1.35-3) 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.) -- 924719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmarc-charset-perl Version: 1.35-2 Severity: serious Hello, for some reasons the package testsuite started to fail in Ubuntu for this package and xml-perl reverse-dependency, only on armhf and i386. This happened when the new gdbm has been uploaded and rebuilds issued. I traced down the problem to some differences in the march8/utf8 Table generation, I don't know how serious it is, but the testsuite seems completely broken on armhf and i386 at least, and utf8 cjk conversion seems to return wrong values. This is the reason for me opening this bug as "serious". you can see the reports here https://autopkgtest.ubuntu.com/packages/libmarc-xml-perl and https://autopkgtest.ubuntu.com/packages/libmarc-charset-perl perl t/cjk.t 1..1 no mapping found for [0x61] at position 0 in a $1!u`!** z g0=ASCII_DEFAULT g1=EXTENDED_LATIN at /usr/share/perl5/MARC/Charset.pm line 308. not ok 1 - cjk # Failed test 'cjk' # at t/cjk.t line 17. Wide character in print at /usr/share/perl/5.28/Test2/Formatter/TAP.pm line 113. # got: 'a 埇 z' # expected: undef # Looks like you failed 1 test of 1. after a no-change rebuild of the package, and installing it, the test goes passing ok: perl t/cjk.t 1..1 ok 1 - cjk I'm not sure if a no-change rebuild fixes also libmarc-xml-perl and fixes all the test failures, this is something I'm checking right now (but I suppose it will) G. --- End Message --- --- Begin Message --- Source: perl Source-Version: 5.28.1-5 We believe that the bug you reported is fixed in the latest version of perl, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni (supplier of updated perl 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: Sat, 16 Mar 2019 16:02:28 +0200 Source: perl Architecture: source Version: 5.28.1-5 Distribution: unstable Urgency: medium Maintainer: Niko Tyni Changed-By: Niko Tyni Closes: 922609 923409 924506 924517 924719 Changes: perl (5.28.1-5) unstable; urgency=medium . * Patch perlbug to use "editor" as the default editor. (Closes: #922609) * Add a Breaks entry for older versions of libdist-inkt-perl. (Closes: #924506) * Add a README.Debian note about overriding the default perldoc formatter. (See: #917530) * Include arch-specific data for NDBM and GDBM autopkgtests. (Closes: #923409) * Break older versions of libmarc-charset-perl, broken by libgdbm changes. (Closes: #924719) + Build-Depend on a current libgdbm-dev to guarantee compatibility with the new LFS-enabled database binary format. * Fix crashing POSIX::mblen(). (Closes: #924517) Checksums-Sha1: fa391d5f89041ce590022bae8c4f01896fc984d8 2835 perl_5.28.1-5.dsc c77f47040e72c4230c6acdf28b05f1f57f47e5e2 178628 perl_5.28.1-5.debian.tar.xz 5cc8af047aac0b5b3fb259e55c41fa1ae839e4db 4678 perl_5.28.1-5_source.buildinfo Checksums-Sha256: a0fa371a5563da70cb671f67662e8e69c799c70904a64f67820c27defc1bc8dd 2835 perl_5.28.1-5.dsc d5ac8e9177d400efffc963a806746ba68127882375f7966ffa6156fc673fd550 178628 perl_5.28.1-5.debian.tar.xz 6312ac6bfdbd77ebcd318a14e7ac87257fb7d3f095b3aec74662381da860e823 4678 perl_5.28.1-5_source.buildinfo Files: 9f6f18fcd33473de5910650fdb32fa9e 2835 perl standard perl_5.28.1-5.dsc f79065a3666e66e8797f39dce578614d 178628 perl standard perl_5.28.1-5.debian.tar.xz 6ee40a8bf5a6cbb94f2c0df838bfd902 4678 perl standard perl_5.28.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlyNHusRHG50eW5pQGRl Ymlhbi5vcmcACgkQLsD/s7cwGx/6/w//RpkUSsA1doSS033QVHDq6KlYDks7BWf1 W0gbEVu3OSIfx9XsGm/F9CYS8LJ7gNEKlwW4F4Poj7EZ7ke1W040R6D16HYjEHrj
Bug#923238: libmarc-charset-perl: needs a rebuild on 32bit architectures?
On Sat, Mar 16, 2019 at 12:29:07PM +0200, Niko Tyni wrote: > > > This will cause temporary uninstallability of libmarc-charset-perl in > > > sid so the uploads should be coordinated a bit. I guess I can do both > > > if needed. > > > > Thanks. > > (If it helps I can also upload libmarc-charset-perl but maybe the > > coordination effort is higher than if you just go ahead :)) > > Yeah, thanks. I'll try to handle this myself. Just uploaded perl_5.28.1-5 and pushed the planned libmarc-charset-perl changes to salsa. Will upload libmarc-charset-perl later when the new perl is built and available on the mirrors. Fine by me if someone else beats me to it. -- Niko
Processed: Bug #923238 in libmarc-charset-perl marked as pending
Processing control commands: > tag -1 pending Bug #923238 [libmarc-charset-perl] libmarc-charset-perl: needs a rebuild on 32bit architectures? Added tag(s) pending. -- 923238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923238: Bug #923238 in libmarc-charset-perl marked as pending
Control: tag -1 pending Hello, Bug #923238 in libmarc-charset-perl 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/perl-team/modules/packages/libmarc-charset-perl/commit/afdc8a315314b69124a18a3af16cdc45b7e6c43c Depend on Perl versions that guarantee database bincompat with libgdbm6 We could do with just "the version of the first sourceful Perl upload after the libgdbm6 transition", but that's somewhat fragile, so perl_5.28.1-5 declared an explicit build dependency on newer libgdbm-dev to guarantee libgdbm6 compatibility. Closes: #923238 (this message was generated automatically) -- Greetings https://bugs.debian.org/923238
Bug#924719: Bug #924719 in perl marked as pending
Control: tag -1 pending Hello, Bug #924719 in perl 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/perl-team/interpreter/perl/commit/7ffa05fcb0ebe9525c7ceae6fa51fa790abb5f53 Break older versions of libmarc-charset-perl, broken by libgdbm changes We Build-Depend on a new libgdbm-dev version to guarantee that the resulting binary packages will be compatible with LFS-enabled GDBM databases as generated by new libgdbm versions. This will need a coordinated upload of libmarc-charset-perl with dependencies on the newer perl. Closes: #924719 (this message was generated automatically) -- Greetings https://bugs.debian.org/924719
Processed: Bug #924719 in perl marked as pending
Processing control commands: > tag -1 pending Bug #924719 [perl] perl: Break libmarc-charset-perl (<< 1.35-3) Added tag(s) pending. -- 924719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924666: marked as done ([hostapd] [buster] not possible to start and to uninstall : /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found)
Your message dated Sat, 16 Mar 2019 16:34:32 + with message-id and subject line Bug#924666: fixed in wpa 2:2.7+git20190128+0c1e29f-3 has caused the Debian Bug report #924666, regarding [hostapd] [buster] not possible to start and to uninstall : /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found 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.) -- 924666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hostapd Version: 2:2.7+git20190128+0c1e29f-2 Dear maintaniers, On Debian Buster, it seems not possible to uninstall hostapd package afterinstallation. Furthermore, i can not launch daemon. My current configuration before installing hostapd is : (with sysvinit, not systemd !) ansible@vm-buster-x86-amd64-100:~$ pstree -anp init,1 |-dhclient,603 -4 -v -i -pf /run/dhclient.eth-admin.pid -lf /var/lib/dhcp/dhclient.eth-admin.leases -I -df... |-dhclient,685 -4 -v -i -pf /run/dhclient.eth-srv.pid -lf /var/lib/dhcp/dhclient.eth-srv.leases -I -df ... |-dhclient,768 -4 -v -i -pf /run/dhclient.eth-user.pid -lf /var/lib/dhcp/dhclient.eth-user.leases -I -df ... |-cron,1197 |-dbus-daemon,1206 --system |-getty,1476 115200 console |-getty,1477 38400 tty2 |-getty,1478 38400 tty3 |-getty,1479 38400 tty4 |-syslog-ng,12916 | `-(syslog-ng,13835) |-syslog-ng,12939 | `-syslog-ng,12940 -p /var/run/syslog-ng.pid --no-caps `-sshd,16299 `-sshd,10843 `-sshd,10849 `-bash,10850 `-pstree,13836 -anp ansible@vm-buster-x86-amd64-100:~$ cat /etc/debian_version buster/sid ansible@vm-buster-x86-amd64-100:~$ cat /etc/apt/sources.list.d/debian_apt_v_10_buster_* |grep -v "#" deb http://ftp.debian.org/debian/ buster main contrib non-free deb http://ftp.debian.org/debian/ sid main contrib non-free deb http://ftp.debian.org/debian/ stretch main contrib non-free deb http://ftp.debian.org/debian/ unstable main contrib non-free ansible@vm-buster-x86-amd64-100:~$ cat /etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#" Package: * Pin: release a=buster Pin-Priority: 900 Package: * Pin: release a=stretch Pin-Priority: 400 Package: * Pin-Priority: -1 Package: * Pin: release a=unstable Pin-Priority: -1 Package: dhcpcd5 Pin: release * Pin-Priority: -1 Package: *systemd* Pin: release * Pin-Priority: -1 ansible@vm-buster-x86-amd64-100:~$ sudo apt update && sudo apt upgrade ansible@vm-buster-x86-amd64-100:~$ dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ansible@vm-buster-x86-amd64-100:~$ sudo apt install hostapd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnl-route-3-200 The following NEW packages will be installed: hostapd libnl-route-3-200 0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. Need to get 939 kB of archives. After this operation, 2637 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ftp.debian.org/debian buster/main amd64 libnl-route-3-200 amd64 3.4.0-1 [162 kB] Get:2 http://ftp.debian.org/debian buster/main amd64 hostapd amd64 2:2.7+git20190128+0c1e29f-2 [777 kB] Fetched 939 kB in 1s (1280 kB/s) Selecting previously unselected package libnl-route-3-200:amd64. (Reading database ... 130986 files and directories currently installed.) Preparing to unpack .../libnl-route-3-200_3.4.0-1_amd64.deb ... Unpacking libnl-route-3-200:amd64 (3.4.0-1) ... Selecting previously unselected package hostapd. Preparing to unpack .../hostapd_2%3a2.7+git20190128+0c1e29f-2_amd64.deb ... Unpacking hostapd (2:2.7+git20190128+0c1e29f-2) ... Setting up libnl-route-3-200:amd64 (3.4.0-1) ... Setting up hostapd (2:2.7+git20190128+0c1e29f-2) ... /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-8) ... ansible@vm-buster-x86-amd64-100:~$ Which is very fine But... ansible@vm-buster-x86-amd64-100:~$ sudo apt remove --purge
Bug#924734: libbpp-seq-omics: FTBFS (dh_makeshlibs fails)
Package: src:libbpp-seq-omics Version: 2.4.1-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 dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. -- The CXX compiler identification is GNU 8.3.0 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- bpp-core 4.1.0 found: [... snipped ...] _ZTv0_n24_N3bpp13BasicSequenceD0Ev@Base 2.4.1 @@ -1134,7 +1150,9 @@ _ZTv0_n48_N3bpp25SimpleMafStatisticsResult8setValueERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 2.4.1 _ZTv0_n48_N3bpp36CsvStatisticsOutputIterationListener14iterationStopsEv@Base 2.4.1 _ZTv0_n48_NK3bpp12EdSymbolList11getAlphabetEv@Base 2.4.1 + _ZTv0_n48_NK3bpp12SequenceMask11isRemovableEv@Base 2.4.1-2 _ZTv0_n48_NK3bpp15SequenceQuality11isRemovableEv@Base 2.4.1 + _ZTv0_n48_NK3bpp20AbstractCoreSequence7getNameB5cxx11Ev@Base 2.4.1-2 _ZTv0_n48_NK3bpp21AbstractMafStatistics9getResultEv@Base 2.4.1 _ZTv0_n48_NK3bpp22SequenceWithAnnotation7getNameB5cxx11Ev@Base 2.4.1 _ZTv0_n48_NK3bpp25AbstractSequenceContainer11getAlphabetEv@Base 2.4.1 @@ -1144,6 +1162,7 @@ _ZTv0_n56_N3bpp16GtfFeatureReader17getFeaturesOfTypeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 _ZTv0_n56_N3bpp17SiteMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 _ZTv0_n56_N3bpp19AbstractMafIterator20addIterationListenerEPNS_17IterationListenerE@Base 2.4.1 + _ZTv0_n56_N3bpp20AbstractCoreSequence7setNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1-2 _ZTv0_n56_N3bpp21BedGraphFeatureReader17getFeaturesOfTypeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 _ZTv0_n56_N3bpp22SequenceWithAnnotation7setNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 _ZTv0_n56_N3bpp25PolymorphismMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 @@ -1153,6 +1172,7 @@ _ZTv0_n56_N3bpp34SiteFrequencySpectrumMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 _ZTv0_n56_N3bpp37FourSpeciesPatternCountsMafStatistics7computeERKNS_8MafBlockE@Base 2.4.1 _ZTv0_n56_NK3bpp12EdSymbolList4sizeEv@Base 2.4.1 + _ZTv0_n56_NK3bpp12SequenceMask8isSharedEv@Base 2.4.1-2 _ZTv0_n56_NK3bpp15BasicSymbolList4sizeEv@Base 2.4.1 _ZTv0_n56_NK3bpp15SequenceQuality8isSharedEv@Base 2.4.1 _ZTv0_n64_N3bpp16GffFeatureReader21getFeaturesOfSequenceERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 @@ -1160,12 +1180,14 @@ _ZTv0_n64_N3bpp21BedGraphFeatureReader21getFeaturesOfSequenceERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_18SequenceFeatureSetE@Base 2.4.1 _ZTv0_n64_N3bpp22SequenceWithAnnotation10setContentERKSt6vectorIiSaIiEE@Base 2.4.1 _ZTv0_n64_NK3bpp17SiteMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 + _ZTv0_n64_NK3bpp20AbstractCoreSequence11getCommentsB5cxx11Ev@Base 2.4.1-2 _ZTv0_n64_NK3bpp22SequenceWithAnnotation11getCommentsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp25PolymorphismMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp28CharacterCountsMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp30SequenceDiversityMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp34SiteFrequencySpectrumMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 _ZTv0_n64_NK3bpp37FourSpeciesPatternCountsMafStatistics16getSupportedTagsB5cxx11Ev@Base 2.4.1 + _ZTv0_n72_N3bpp20AbstractCoreSequence11setCommentsERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1-2 _ZTv0_n72_N3bpp22SequenceWithAnnotation10setContentERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1 _ZTv0_n72_N3bpp22SequenceWithAnnotation11setCommentsERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1 _ZTv0_n72_NK3bpp5Fastq12nextSequenceERSiRNS_8SequenceE@Base 2.4.1 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:10: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant
Bug#919793: prospector won't run at all
found 919793 0.12.7-2.1
thanks
prospector is still completely unusable in latest package, but with
different errors.
Without pyroma installed:
Traceback (most recent call last):
File "/usr/bin/prospector", line 11, in
load_entry_point('prospector==0.12.7', 'console_scripts',
'console_script')()
File "/usr/share/prospector/prospector/run.py", line 165, in main
prospector.execute()
File "/usr/share/prospector/prospector/run.py", line 53, in execute
for tool in self.config.get_tools(found_files):
File "/usr/share/prospector/prospector/config/__init__.py", line 45,
in get_tools
config_result = tool.configure(self, found_files)
File "/usr/share/prospector/prospector/tools/pylint/__init__.py",
line 172, in configure
linter.reset_options()
File "/usr/share/prospector/prospector/tools/pylint/linter.py", line
30, in reset_options
OptionsManagerMixIn.__init__(self, usage=PyLinter.__doc__, quiet=True)
TypeError: __init__() got an unexpected keyword argument 'quiet'
And with pyroma installed:
Traceback (most recent call last):
File "/usr/bin/prospector", line 11, in
load_entry_point('prospector==0.12.7', 'console_scripts',
'console_script')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
489, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2793, in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2411, in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2417, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/share/prospector/prospector/run.py", line 8, in
from prospector import blender, postfilter, tools
File "/usr/share/prospector/prospector/tools/__init__.py", line 48,
in
'pyroma': _optional_tool('pyroma'),
File "/usr/share/prospector/prospector/tools/__init__.py", line 29,
in _optional_tool
tool_package = __import__(package_name, fromlist=[tool_class_name])
File "/usr/share/prospector/prospector/tools/pyroma/__init__.py",
line 27, in
ratings.PEP386Version: 'PYR04',
AttributeError: module 'pyroma.ratings' has no attribute 'PEP386Version'
Processed: Re: Bug#919793: prospector won't run at all
Processing commands for cont...@bugs.debian.org: > found 919793 0.12.7-2.1 Bug #919793 [prospector] prospector won't run at all Marked as found in versions prospector/0.12.7-2.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 919793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924733: pyqwt3d: FTBFS (SIP failed to generate the C++ code)
Package: src:pyqwt3d
Version: 0.1.8-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh_testdir
export QTDIR=/usr/share/qt5
set -e ;\
for py in 3.7 ; do \
mkdir -p build/py$py-qt5; \
cp -Rl `ls . |grep -v build|grep -v debian` build/py$py-qt5; \
(cd build/py$py-qt5/configure;\
python$py configure-qt5.py -5 -I /usr/include/qwtplot3d
--extra-libs=qwtplot3d-qt5 -D GL2PS_HAVE_ZLIB); \
done
sip: Deprecation warning: ../sip/OpenGL_Qt5_Module.sip:31: %Module version
number should be specified using the 'version' argument
sip: Deprecation warning: ../sip/Qwt3D_Qt5_Module.sip:31: %Module version
number should be specified using the 'version' argument
sip: ../sip/types.sip:5: syntax error
Command line options:
{'debug': False,
'disable_numarray': False,
'disable_numeric': False,
'disable_numpy': False,
'excluded_features': [],
'extra_cflags': [],
'extra_cxxflags': [],
'extra_defines': ['GL2PS_HAVE_ZLIB'],
'extra_include_dirs': ['/usr/include/qwtplot3d'],
'extra_lflags': [],
'extra_lib_dirs': [],
'extra_libs': ['qwtplot3d-qt5'],
'jobs': '',
'module_install_path': '',
'modules': [],
'qt': 5,
'qwtplot3d_sources': '',
'sip_include_dirs': ['-I ../sip'],
'subdirs': [],
'timelines': [],
'trace': '',
'zlib_sources': ''}
Found SIP-4.19.14.
Found 'posix' operating system:
3.7.2+ (default, Feb 27 2019, 15:41:59)
[GCC 8.2.0]
Found NumPy-1.16.1.
Setup the OpenGL package build.
-n sip -t WS_X11 -t Qt_5_11_3
sip invokation:
('/usr/bin/sip -I /usr/share/sip/PyQt5 -n sip -t WS_X11 -t Qt_5_11_3 -b '
'tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -c tmp-OpenGL_Qt5 '
'../sip/OpenGL_Qt5_Module.sip')
Copy tmp-OpenGL_Qt5/sipOpenGLcmodule.cpp -> OpenGL_Qt5/sipOpenGLcmodule.cpp.
Copy tmp-OpenGL_Qt5/sipAPIOpenGL.h -> OpenGL_Qt5/sipAPIOpenGL.h.
Copy tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -> OpenGL_Qt5/OpenGL_Qt5.sbf.
3 file(s) lazily copied.
Setup the Qwt3D package build.
Extended options:
{'debug': False,
'disable_numarray': False,
'disable_numeric': False,
'disable_numpy': False,
'excluded_features': ['-x HAS_QT3 -x HAS_QT4'],
'extra_cflags': [],
'extra_cxxflags': [],
'extra_defines': ['GL2PS_HAVE_ZLIB', 'HAS_NUMPY'],
'extra_include_dirs': ['/usr/include/qwtplot3d',
'/usr/include/python3.7m',
'/usr/lib/python3/dist-packages/numpy/core/include',
'/usr/include/x86_64-linux-gnu/qt5/Qt',
'/usr/include/x86_64-linux-gnu/qt5/QtCore',
'/usr/include/x86_64-linux-gnu/qt5/QtGui',
'/usr/include/x86_64-linux-gnu/qt5/QtWidgets',
'/usr/include/x86_64-linux-gnu/qt5/QtOpenGL',
'/usr/include/x86_64-linux-gnu/qt5'],
'extra_lflags': [],
'extra_lib_dirs': [],
'extra_libs': ['qwtplot3d-qt5'],
'jobs': '',
'module_install_path': '/usr/lib/python3.7/dist-packages/PyQt5/Qwt3D',
'modules': [],
'opengl': 'OpenGL_Qt5',
'qt': 5,
'qwt3d': 'Qwt3D_Qt5',
'qwtplot3d_sources': '',
'sip_include_dirs': ['-I ../sip'],
'subdirs': ['Qwt3D_Qt5', 'OpenGL_Qt5'],
'timelines': [],
'trace': '',
'zlib_sources': ''}
sip invokation:
('/usr/bin/sip -I /usr/share/sip/PyQt5 -n sip -t WS_X11 -t Qt_5_11_3 -b '
'tmp-Qwt3D_Qt5/qwt3d.sbf -c tmp-Qwt3D_Qt5 -I ../sip -x HAS_QT3 -x HAS_QT4 '
'../sip/Qwt3D_Qt5_Module.sip')
SIP failed to generate the C++ code.
make: *** [debian/rules:25: configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyqwt3d.html
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Processed: Re: Bug#919793: prospector won't run at all
Processing commands for cont...@bugs.debian.org: > severity 919793 serious Bug #919793 [prospector] prospector won't run at all Severity set to 'serious' from 'important' > # due to errors package is completely worthless > End of message, stopping processing here. Please contact me if you need assistance. -- 919793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: patch
Processing control commands: > tags -1 + patch Bug #866421 [src:comix] comix: depends on obsolete python-imaging (replace with python3-pil or python-pil) Added tag(s) patch. -- 866421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866421: patch
Control: tags -1 + patch
I fixed the problem by changing Imaging to PIL. See attached patch.
--- comix-4.0.4/debian/changelog2016-02-24 14:16:57.0 +0100
+++ comix-4.0.4/debian/changelog2018-09-28 19:07:08.0 +0200
@@ -1,3 +1,10 @@
+comix (4.0.4-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * added patch import PIL rather than Imaging (Closes: #866421)
+
+ --Fri, 28 Sep 2018 19:07:08 +0200
+
comix (4.0.4-3) unstable; urgency=low
* Didn't really add unar support, remove suggestion.
--- comix-4.0.4/debian/control 2016-02-24 13:45:55.0 +0100
+++ comix-4.0.4/debian/control 2018-09-28 19:07:08.0 +0200
@@ -8,7 +8,7 @@
Package: comix
Architecture: all
-Depends: ${misc:Depends}, python (>= 2.4), python-gtk2 (>= 2.12),
python-imaging (>= 1.1.5)
+Depends: ${misc:Depends}, python (>= 2.4), python-gtk2 (>= 2.12), python-pil
(>= 1.1.5)
Recommends: mcomix
Suggests: unrar-free | unrar, python (>=2.5)|python-sqllite2
Description: GTK Comic Book Viewer
--- comix-4.0.4/debian/patches/866421-python-imaging-removal.patch
1970-01-01 01:00:00.0 +0100
+++ comix-4.0.4/debian/patches/866421-python-imaging-removal.patch
2018-09-28 19:07:08.0 +0200
@@ -0,0 +1,144 @@
+Description: remove python-imaging dependency
+
+
+Author: Thomas Walz
+Bug-Debian: https://bugs.debian.org/866421
+
+Last-Update: 2018-09-28
+
+Index: comix-4.0.4/install.py
+===
+--- comix-4.0.4.orig/install.py
comix-4.0.4/install.py
+@@ -240,14 +240,14 @@ def check_dependencies():
+ print '!!! PyGTK Not found'
+ required_found = False
+ try:
+-import Image
+-assert Image.VERSION >= '1.1.5'
++import PIL
++assert PIL.VERSION >= '1.1.5'
+ print 'Python Imaging Library ... OK'
+ except ImportError:
+ print '!!! Python Imaging Library ... Not found'
+ required_found = False
+ except AssertionError:
+-print '!!! Python Imaging Library ... version', Image.VERSION,
++print '!!! Python Imaging Library ... version', PIL.VERSION,
+ print 'found'
+ print '!!! Python Imaging Library 1.1.5 or higher is required'
+ required_found = False
+Index: comix-4.0.4/src/comix.py
+===
+--- comix-4.0.4.orig/src/comix.py
comix-4.0.4/src/comix.py
+@@ -49,7 +49,7 @@ except ImportError:
+ sys.exit(1)
+
+ try:
+-import Image
++import PIL as Image
+ assert Image.VERSION >= '1.1.5'
+ except AssertionError:
+ print "You don't have the required version of the Python Imaging",
+Index: comix-4.0.4/src/histogram.py
+===
+--- comix-4.0.4.orig/src/histogram.py
comix-4.0.4/src/histogram.py
+@@ -1,9 +1,9 @@
+ """histogram.py - Draw histograms (RGB) from pixbufs."""
+
+ import gtk
+-import Image
+-import ImageDraw
+-import ImageOps
++from PIL import Image
++from PIL import ImageDraw
++from PIL import ImageOps
+
+ import image
+
+Index: comix-4.0.4/src/image.py
+===
+--- comix-4.0.4.orig/src/image.py
comix-4.0.4/src/image.py
+@@ -1,10 +1,10 @@
+ """image.py - Various image manipulations."""
+
+ import gtk
+-import Image
+-import ImageEnhance
+-import ImageOps
+-import ImageStat
++from PIL import Image
++from PIL import ImageEnhance
++from PIL import ImageOps
++from PIL import ImageStat
+
+ from preferences import prefs
+
+@@ -169,7 +169,7 @@ def get_most_common_edge_colour(pixbuf):
+
+ def pil_to_pixbuf(image):
+ """Return a pixbuf created from the PIL ."""
+-imagestr = image.tostring()
++imagestr = image.tobytes()
+ IS_RGBA = image.mode == 'RGBA'
+ return gtk.gdk.pixbuf_new_from_data(imagestr, gtk.gdk.COLORSPACE_RGB,
+ IS_RGBA, 8, image.size[0], image.size[1],
+Index: comix-4.0.4/src/library.py
+===
+--- comix-4.0.4.orig/src/library.py
comix-4.0.4/src/library.py
+@@ -8,8 +8,8 @@ from xml.sax.saxutils import escape as x
+ import gtk
+ import gobject
+ import pango
+-import Image
+-import ImageDraw
++import PIL as Image
++from PIL import ImageDraw
+
+ import archive
+ import encoding
+Index: comix-4.0.4/src/thumbbar.py
+===
+--- comix-4.0.4.orig/src/thumbbar.py
comix-4.0.4/src/thumbbar.py
+@@ -4,8 +4,8 @@ import urllib
+
+ import gtk
+ import gobject
+-import Image
+-import ImageDraw
++from PIL import Image
++from PIL import ImageDraw
+
+ import image
+ from preferences import prefs
+Index: comix-4.0.4/src/thumbnail.py
+===
+--- comix-4.0.4.orig/src/thumbnail.py
comix-4.0.4/src/thumbnail.py
Bug#924731: phamm: CVE-2018-20806: Reflected XSS in Phamm login page
Source: phamm Version: 0.6.5-1 Severity: grave Tags: security upstream Forwarded: https://github.com/lota/phamm/issues/24 Hi, The following vulnerability was published for phamm. CVE-2018-20806[0]: | Phamm (aka PHP LDAP Virtual Hosting Manager) 0.6.8 allows XSS via the | login page (the /public/main.php action parameter). 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-2018-20806 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20806 [1] https://github.com/lota/phamm/issues/24 Regards, Salvatore
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 867682 +patch Bug #867682 [squid-deb-proxy-client] squid-deb-proxy-client: breaks apt operation if removed and system upgraded to stretch Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 867682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923891: have the same problem
Thx Soren Stoutner for the workaround! I'm waiting to for resolution of this major bug! Dragos
Bug#924727: check-mk: build-depends on no longer available g++-6
Source: check-mk Version: 1.4.0p9-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, check-mk/experimental cannot be built any more since it build-depends on an ancient no longer available g++ version. Andreas
Bug#924666: invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
On Sat, 16 Mar 2019 at 12:33, Jean-Marc LACROIX wrote: > Hi, > > According to previous tests, due to a serious bug in the > post-installation scripts, it is no longer possible to reinstall or > remove any type of package. The system is then definitely unusable. hostapd from buster Pre-Depends on init-system-helpers >= 1.54 which supports the required option. > Many thanks To William Bonnet for his support on Debian systems I don’t know who William Bonnet is. -- Cheers, Andrej
Bug#918389: marked as done (ruby-attr-encrypted FTBFS with rails 5.2.0)
Your message dated Sat, 16 Mar 2019 12:49:04 + with message-id and subject line Bug#918389: fixed in ruby-attr-encrypted 3.1.0-2 has caused the Debian Bug report #918389, regarding ruby-attr-encrypted FTBFS with rails 5.2.0 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.) -- 918389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-attr-encrypted Version: 3.1.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-attr-encrypted.html ... 1) Failure: ActiveRecordTest#test_attribute_was_works_when_options_for_old_encrypted_value_are_different_than_options_for_new_encrypted_value [/build/1st/ruby-attr-encrypted-3.1.0/test/active_record_test.rb:215]: Expected: "password" Actual: nil 2) Failure: ActiveRecordTest#test_should_create_was_predicate [/build/1st/ruby-attr-encrypted-3.1.0/test/active_record_test.rb:194]: Expected: "t...@example.com" Actual: nil 147 runs, 262 assertions, 2 failures, 0 errors, 0 skips rake aborted! Command failed with status (1): [ruby -w -I"test" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/active_record_test.rb" "test/attr_encrypted_test.rb" "test/compatibility_test.rb" "test/legacy_active_record_test.rb" "test/legacy_attr_encrypted_test.rb" "test/legacy_compatibility_test.rb" "test/legacy_sequel_test.rb" "test/sequel_test.rb" -v] Tasks: TOP => default (See full trace by running task with --trace) ERROR: Test "ruby2.5" failed. Exiting. dh_auto_install: dh_ruby --install /build/1st/ruby-attr-encrypted-3.1.0/debian/ruby-attr-encrypted returned exit code 1 make: *** [debian/rules:8: binary] Error 1 --- End Message --- --- Begin Message --- Source: ruby-attr-encrypted Source-Version: 3.1.0-2 We believe that the bug you reported is fixed in the latest version of ruby-attr-encrypted, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-attr-encrypted 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: Sat, 16 Mar 2019 16:50:36 +0530 Source: ruby-attr-encrypted Binary: ruby-attr-encrypted Architecture: source Version: 3.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Description: ruby-attr-encrypted - Encrypt and decrypt attributes Closes: 918389 Changes: ruby-attr-encrypted (3.1.0-2) unstable; urgency=medium . * Fix test failure with upstream patch (Closes: #918389) * Bump Standards-Version to 4.3.0 (no changes needed) Checksums-Sha1: 5c2597062a31bc39120414c7103e1a32f4f7ee04 2202 ruby-attr-encrypted_3.1.0-2.dsc 7e2d50eb7bb7c4d240393b7902dee70049d31036 4344 ruby-attr-encrypted_3.1.0-2.debian.tar.xz 8c91a776d85f479288d138af15ced768dcf26136 12376 ruby-attr-encrypted_3.1.0-2_source.buildinfo Checksums-Sha256: 56a565bf7fa106d6c06838e76f086834829c0285c0921757605a9c219746324a 2202 ruby-attr-encrypted_3.1.0-2.dsc 7867a6d733eb431f005a2304f0d8ac1c7f356ddbe0055911496f8ba3d026ba75 4344 ruby-attr-encrypted_3.1.0-2.debian.tar.xz 806e0d9d43ffe76b7704f83287a36d160a6e6c9a0b4ad984eb42a873c6d7488a 12376 ruby-attr-encrypted_3.1.0-2_source.buildinfo Files: ab90c1c9629a88c46db923c4a802d327 2202 ruby optional ruby-attr-encrypted_3.1.0-2.dsc 1ec484a417f99167e7193186e252cc79 4344 ruby optional ruby-attr-encrypted_3.1.0-2.debian.tar.xz 248e8666a401278c2cb58818e58ab1f0 12376 ruby optional ruby-attr-encrypted_3.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAlyM72oACgkQC3aSB2Km t4Wr0w/9E+fRHqw7kcC5Sv4/aP/UbUb7bGt7lZ0DdSSNUSn9wEtJoAM15TMbbTuW +Z+V2waX+KkXLLvzYBlcesM8eAhsYNH8ZoNJldnHpR3bqVUcMrgOwuca6xtb6y8K gL488nzcK1eMeEyIXocy6AOw3to5UEowyKAtd9r5eq/kt4nFi6z0Sp5foO24zlx4 hV0xCfm6IFZp6WXVWzd4SqfjuzLMw7P2P7ucDQkXuupiTMrMsWRiWOSuaVi2jziP 5EXtejsZI5MRkdeb06O8jOEQTiQXsQQj35P+N3OV4dnw420hcKVfsK0+Dnoi9Ajx NJRc/bAYNxchPwT/cRJq22omLXOOJM6bwkDITaSeG8Vjq0CItRSUXSiTIj2exnrx
Processed: Re: google-android-ndk-installer: Superseded by google-android-installers?
Processing control commands:
> reassign -1 src:google-android-installers 1472023576
Bug #849390 {Done: Helge Kreutzmann }
[src:google-android-ndk-installer] google-android-ndk-installer: Superseded by
google-android-installers?
Bug reassigned from package 'src:google-android-ndk-installer' to
'src:google-android-installers'.
No longer marked as found in versions google-android-ndk-installer/13b.
No longer marked as fixed in versions google-android-installers/1472023576+nmu2.
Bug #849390 {Done: Helge Kreutzmann }
[src:google-android-installers] google-android-ndk-installer: Superseded by
google-android-installers?
Marked as found in versions google-android-installers/1472023576.
> fixed -1 1472023576+nmu2
Bug #849390 {Done: Helge Kreutzmann }
[src:google-android-installers] google-android-ndk-installer: Superseded by
google-android-installers?
Marked as fixed in versions google-android-installers/1472023576+nmu2.
> retitle -1 src:google-android-installers: google-android-ndk-installer is now
> built from a separate source package
Bug #849390 {Done: Helge Kreutzmann }
[src:google-android-installers] google-android-ndk-installer: Superseded by
google-android-installers?
Changed Bug title to 'src:google-android-installers:
google-android-ndk-installer is now built from a separate source package' from
'google-android-ndk-installer: Superseded by google-android-installers?'.
> tag -1 sid buster
Bug #849390 {Done: Helge Kreutzmann }
[src:google-android-installers] src:google-android-installers:
google-android-ndk-installer is now built from a separate source package
Added tag(s) buster and sid.
--
849390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: google-android-installers: FTBFS in stretch/i386
Processing control commands: > close -1 1472023576+nmu2 Bug #924725 [src:google-android-installers] google-android-installers: FTBFS in stretch/i386 Marked as fixed in versions google-android-installers/1472023576+nmu2. Bug #924725 [src:google-android-installers] google-android-installers: FTBFS in stretch/i386 Marked Bug as done -- 924725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#849390: google-android-ndk-installer: Superseded by google-android-installers?
Followup-For: Bug #849390 Control: reassign -1 src:google-android-installers 1472023576 Control: fixed -1 1472023576+nmu2 Control: retitle -1 src:google-android-installers: google-android-ndk-installer is now built from a separate source package Control: tag -1 sid buster This was resolved by removal of the binary package from src:google-android-installers. google-android-ndk-installer | 12.b+1| stable/contrib | amd64 google-android-ndk-installer | 13b | unstable/contrib | source, amd64 Andreas
Bug#924725: google-android-installers: FTBFS in stretch/i386
Source: google-android-installers Version: 1472023576 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: close -1 1472023576+nmu2 Hi, google-android-installers/stretch now FTBFS in stretch/i386: fakeroot debian/rules binary dh binary create-stamp debian/debhelper-build-stamp dh_testroot dh_prep dh_installdirs dh_auto_install dh_install dh_installdocs dh_installchangelogs dh_installdebconf dh_lintian dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_strip dh_makeshlibs dh_shlibdeps dh_installdeb debian/rules override_dh_gencontrol make[1]: Entering directory '/build/google-android-installers-1472023576' dh_gencontrol -- -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-24-installer -- -v24+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-23-installer -- -v23+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-22-installer -- -v22+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-21-installer -- -v21+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-20-installer -- -v20+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-19-installer -- -v19+r04 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-18-installer -- -v18+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-17-installer -- -v17+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-16-installer -- -v16+r05 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-15-installer -- -v15+r05 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-14-installer -- -v14+r04 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-13-installer -- -v13+r01 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-12-installer -- -v12+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-11-installer -- -v11+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-10-installer -- -v10+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-9-installer -- -v9+r02 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-8-installer -- -v8+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-7-installer -- -v7+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-6-installer -- -v6+r01 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-5-installer -- -v5+r01 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-4-installer -- -v4+r03 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-3-installer -- -v3+r04 -Tdebian/substvars dh_gencontrol -pgoogle-android-platform-2-installer -- -v2+r1 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-24-installer -- -v24.0.2 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-23-installer -- -v23.0.3 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-22-installer -- -v22.0.1 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-21-installer -- -v21.1.2 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-20-installer -- -v20.0.0 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-19-installer -- -v19.0.3 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-18-installer -- -v18.1.1 -Tdebian/substvars dh_gencontrol -pgoogle-android-build-tools-17-installer -- -v17.0.0 -Tdebian/substvars dh_gencontrol -pgoogle-android-ndk-installer -- -v12.b+1 -Tdebian/substvars dpkg-gencontrol: error: current host architecture 'i386' does not appear in package's architecture list (amd64) dh_gencontrol: dpkg-gencontrol -pgoogle-android-ndk-installer -ldebian/changelog -Tdebian/google-android-ndk-installer.substvars -Pdebian/google-android-ndk-installer -v12.b+1 -Tdebian/substvars returned exit code 255 debian/rules:40: recipe for target 'override_dh_gencontrol' failed make[1]: *** [override_dh_gencontrol] Error 2 make[1]: Leaving directory '/build/google-android-installers-1472023576' debian/rules:37: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 dpkg-gencontrol seems to have gotten more strict compared to the time when this package was built successfully in 2016. This was fixed automatically at the point this source stopped building the google-android-ndk-installer package. Andreas google-android-installers_1472023576.log.gz Description: application/gzip
Bug#924321: marked as done (python-openflow: please stop buildd-depending on py3.6)
Your message dated Sat, 16 Mar 2019 12:19:11 + with message-id and subject line Bug#924321: fixed in python-openflow 2017.2b1+dfsg-2.1 has caused the Debian Bug report #924321, regarding python-openflow: please stop buildd-depending on py3.6 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.) -- 924321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-openflow Version: Severity: serious Control: block 924018 by -1 Dear maintainer, your package block the removal python 3.6. Please stop build-depending on it, and in general please always prefer to build-depend only on the unversioned python variants (which you already do, mostly interestingly…). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: python-openflow Source-Version: 2017.2b1+dfsg-2.1 We believe that the bug you reported is fixed in the latest version of python-openflow, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python-openflow 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: Sat, 16 Mar 2019 12:49:28 +0100 Source: python-openflow Architecture: source Version: 2017.2b1+dfsg-2.1 Distribution: unstable Urgency: medium Maintainer: Paulo Henrique de Lima Santana (phls) Changed-By: Matthias Klose Closes: 924321 Changes: python-openflow (2017.2b1+dfsg-2.1) unstable; urgency=medium . * Non-maintainer upload. * Remove python3.6 build dependency. Closes: #924321. Checksums-Sha1: 313fa081d923a0876ed23ca9848409db2e57d08d 1942 python-openflow_2017.2b1+dfsg-2.1.dsc 2e191501377406d3f1e152a3d59e5a532ca75562 4576 python-openflow_2017.2b1+dfsg-2.1.debian.tar.xz cdd525815a9e200772d7aec20b0713ba447891fc 6054 python-openflow_2017.2b1+dfsg-2.1_source.buildinfo Checksums-Sha256: a3c82cbd77d9915103f31cc9202efed8c898d844fd7b5921b9017335f062337e 1942 python-openflow_2017.2b1+dfsg-2.1.dsc efb2d4b1e4f52d1d5c283e68b535f776a55f9d6e1ba53aa9070ce1910d6974cc 4576 python-openflow_2017.2b1+dfsg-2.1.debian.tar.xz c95213b3266abc336f8f2971a653ca248a6abf60deee51175fab18ed0c396130 6054 python-openflow_2017.2b1+dfsg-2.1_source.buildinfo Files: 39384f28c14ea9eda8f1dba08671b87b 1942 python optional python-openflow_2017.2b1+dfsg-2.1.dsc 04f8bf3584bc84ae1cffec07c88eff8d 4576 python optional python-openflow_2017.2b1+dfsg-2.1.debian.tar.xz 2736ac39d73fa1743af133cdc490f611 6054 python optional python-openflow_2017.2b1+dfsg-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlyM5BwQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9SflD/9bJybRIioLoFc96WuK6UKWoYrr1RQIshfw gwcHI6G6Zs2x5i2RwEVqvwNuzy2XKx/jaMxgsx/jYR6eeeA/qJxgU/RiixTdVy9/ 91uO03TWP4V8EM1JtF5pyHekOUMDn54AMJUaYZGUKZcjnRz99nOJzDRJP/Yih2rT 2bJbO5HyWINxMaNIiJOhp7ZbzzopaajbUd0MID0HygOSp9ZkokIHjahYpLtP9Dqa Mrecv01kC3EUJk+WXr9Zog0TD1Hd5P3AGOzEFNYrux0KoBASsK/htASmFkjOLdKb vhM4M/4L87FiUYbUpHVG11SZx3pFx5TMdm944pEeJXSFjx70TYPgDvOSCJlGac29 1XqKbCNq+oRqfWw8kvwf8drkI2Vfat+FB1Lr77IpBQL6bEJAb9nLVldVoCLynl+J HJ1IDeKakYvHMvbdTbs5/xr8CSopAC4Aoe8cZxU/ZuKZyZTxy1A4a9CAG66kglKc GrO1tJEGVO/M4kRVeNthPc3BbHZFPJ9IC4PtVvClaULo+huohJlhhrYmtOSBIwCl wheiX2m+ho9IhhvrE+S6KfcrVyNwDR9/duDfquY/Jk+n9zd2bGn+JgH0LB3fSkqS g7yuPN5oKBQfvjlw3wolIe6/cw7M8RZoUX6HaardWKX0FBRpo6Zsz+UAl7odUPPa QvhxwUElEQ== =W3Hb -END PGP SIGNATURE End Message ---
Bug#924321: python-openflow: please stop buildd-depending on py3.6
now NMUed. This was the last package preventing the removal of python3.6 in unstable.
Bug#924397: corekeeper: insecure use of world-writable /var/crash
* Paul Wise , 2019-03-15, 08:59: As a data point, apport creates /var/crash as world-writable in postinst: Does apport use a core dump handler? Yes. If so it shouldn't need a world writable directory since the core dump handler runs as root. Apparmor saves dumps directly in /var/crash (bad idea...), so the sticky bit is needed so that the user can delete their own core dumps. I've filed #924692 and #924693 so far, but there's probably more. -- Jakub Wilk
Bug#924666: invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
Hi, According to previous tests, due to a serious bug in the post-installation scripts, it is no longer possible to reinstall or remove any type of package. The system is then definitely unusable. Thanks in advance to apply following patch To reproduce : step 1: no hostapd on the system ansible@srv-authenticator-100:~$ dpkg -l |grep hostapd ansible@srv-authenticator-100:~$ step 2: install buster release ansible@srv-authenticator-100:~$ sudo apt -t buster install hostapd Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: hostapd 0 upgraded, 1 newly installed, 0 to remove and 303 not upgraded. Need to get 0 B/777 kB of archives. After this operation, 2081 kB of additional disk space will be used. Selecting previously unselected package hostapd. (Reading database ... 23028 files and directories currently installed.) Preparing to unpack .../hostapd_2%3a2.7+git20190128+0c1e29f-2_amd64.deb ... Unpacking hostapd (2:2.7+git20190128+0c1e29f-2) ... Setting up hostapd (2:2.7+git20190128+0c1e29f-2) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error processing package hostapd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db (2.7.6.1-2) ... Errors were encountered while processing: hostapd E: Sub-process /usr/bin/dpkg returned an error code (1) ansible@srv-authenticator-100:~$ step 3: As system is broken, be sure to verify that system is unusable ansible@srv-authenticator-100:~$ sudo dpkg --purge --force-all hostapd (Reading database ... 23054 files and directories currently installed.) Removing hostapd (2:2.7+git20190128+0c1e29f-2) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error processing package hostapd (--purge): subprocess installed pre-removal script returned error exit status 1 invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: hostapd ansible@srv-authenticator-100:~$ step 4: search invalid parameter ansible@srv-authenticator-100:~$ egrep -e '-skip-systemd-native' /var/lib/dpkg/info/hostapd.* /var/lib/dpkg/info/hostapd.postinst:invoke-rc.d --skip-systemd-native hostapd $_dh_action || exit 1 /var/lib/dpkg/info/hostapd.prerm: invoke-rc.d --skip-systemd-native hostapd stop || exit 1 step 5 : patch Debian scripts . sudo sed -i -e 's/--skip-systemd-native//g' /var/lib/dpkg/info/hostapd.* step 6 : As system is broken, be sure to verify that system is usable now ansible@srv-authenticator-100:~$ sudo apt remove --purge hostapd -y Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: hostapd* 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 2081 kB disk space will be freed. (Reading database ... 23054 files and directories currently installed.) Removing hostapd (2:2.7+git20190128+0c1e29f-2) ... /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found Processing triggers for man-db (2.7.6.1-2) ... (Reading database ... 23032 files and directories currently installed.) Purging configuration files for hostapd (2:2.7+git20190128+0c1e29f-2) ... dpkg: warning: while removing hostapd, directory '/etc/hostapd' not empty so not removed ansible@srv-authenticator-100:~$ Many thanks To William Bonnet for his support on Debian systems Best regards
Bug#924704: bumblebee-nvidia: nvidia-driver 410 doesn't appear to allow the unloading of the nvidia module
What Nvidia card does your laptop have? On Sat, 16 Mar 2019, 03:42 Daniel O. Package: bumblebee-nvidia > Version: 3.2.1-20 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, I write this bug report because this bumblebee/bumblebeed > doesn't work as it should. > >* What led up to the situation? Bumblebee used to work correctly when > the > nvidia driver was at 390. A few days ago it was upgraded to 410. At the > time I > was running Debian Buster (testing as of this writing). That's where things > started to get problematic. It appears that the nvidia module couldn't be > unloaded or something. bbswitch reported as "ON" without optirun, and as > the > nvidia drivers were considered in use, I was unable to unbind the nvidia > driver > for VGA Passthrough as I had been doing before. >* What exactly did you do (or not do) that was effective (or > ineffective)? I uninstalled every bumblebee and nvidia package. I then > reinstalled everything. No luck. I then uninstalled everything and went > for the > legacy 390 package. Unfortunately there were problems with that: > nvidia-cuba- > toolkit and nvidia-cuba-dev require the latest nvidia driver installed. On > top > of that, bumblebee refused to see the legacy 390 drivers as a glx > alternative. > I uninstalled all the nvidia stuff again, switched to Debian Sid, and > installed > the latest nvidia drivers again (they were slightly more up to date on Sid > than > in Buster). Still no change. >* What was the outcome of this action? Bumblebee should be able to > blacklist > the nvidia driver and isolate it from the operating system in such a way > that > the system would run on the integrated GPU and run the discrete GPU for > applications when called for. >* What outcome did you expect instead? The nvidia driver is not > blacklisted, > and the discrete GPU is in control. > > On a different note, I tried posting a bug report upstream. It has some > information this report might not have (vice versa is definitely the case, > unfortunately). It can be found at https://github.com/Bumblebee- > Project/Bumblebee/issues/1023 > > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable') > 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 > > Versions of packages bumblebee-nvidia depends on: > ii bumblebee 3.2.1-20 > ii glx-alternative-nvidia 0.9.1 > ii nvidia-driver 410.104-1 > ii nvidia-kernel-dkms 410.104-1 > > bumblebee-nvidia recommends no packages. > > bumblebee-nvidia suggests no packages. > > -- no debconf information > > ___ > pkg-nvidia-devel mailing list > pkg-nvidia-de...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel
Bug#873200: marked as done (/usr/bin/llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined
Your message dated Sat, 16 Mar 2019 11:19:16 + with message-id and subject line Bug#866354: fixed in gcc-8 8.3.0-3 has caused the Debian Bug report #866354, regarding /usr/bin/llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference 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.) -- 866354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: llvm-4.0-dev Version: 1:4.0.1-1 Severity: serious Justification: Breaks compilation of dependent packages on a release architecture Hi, This error seems to occur on armel only. Affected is the package aspectc++, which FTBFS because of this bug. Please see the buildlog at https://buildd.debian.org/status/fetch.php?pkg=aspectc%2B%2B=armel=1%3A2.2%2Bgit20170823-1=1503642904=0 The relevant part reads like this: [...] /usr/bin/make -s -C AspectC++ cleanall FRONTEND=Clang LLVMCONF=/usr/bin/llvm-config-4.0 /usr/bin/llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference config/clang.mk:12: *** UNSUPPORTED Clang version '' used -- try 'make -C config clang LLVMCONF='. Stop. debian/rules:85: recipe for target 'clean' failed make: *** [clean] Error 2 Thanks for looking into this! Reinhard --- End Message --- --- Begin Message --- Source: gcc-8 Source-Version: 8.3.0-3 We believe that the bug you reported is fixed in the latest version of gcc-8, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-8 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: Sat, 16 Mar 2019 11:41:45 +0100 Source: gcc-8 Architecture: source Version: 8.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 866354 Changes: gcc-8 (8.3.0-3) unstable; urgency=medium . * Update to SVN 20190316 (r269720) from the gcc-8-branch. - Fix PR tree-optimization/89505, PR target/89517 (AArch64), PR bootstrap/89539, PR debug/88878, PR debug/89514, PR tree-optimization/89536, PR target/88100 (PPC), PR target/89397 (x86), PR target/89361 (S390), PR c++/89212, PR fortran/89077, PR fortran/77583, PR fortran/89174, PR fortran/87689, PR fortran/84387, PR fortran/89516, PR fortran/89492, PR fortran/89266, PR fortran/88326, PR libfortran/89020, PR target/88530 (AArch64), PR target/88530 (AArch64), PR ipa/88235, PR c++/88820, PR c++/88869, PR c++/88419, PR c++/88690, PR c++/87921, PR c++/89381, PR c++/89576, PR c++/89422, PR c++/87513, PR c++/88183, PR c++/89585, PR fortran/71544, PR fortran/87734, PR fortran/71203, PR fortran/72714, PR middle-end/89572, PR target/85860, PR middle-end/89677, PR middle-end/89497, PR tree-optimization/89296, PR tree-optimization/89664, PR rtl-optimization/89588, PR lto/88147, PR target/86952 (x86), PR lto/88147, PR fortran/87673, PR c++/89383, PR lto/87525, PR other/89712, PR testsuite/85368. * Backport libgo patches for the Hurd from the trunk (Svante Signell). * Add some more breaks to libstdc++6. Closes: #866354. Checksums-Sha1: 289eef74f89e06705557422c66f9d43dfe25a251 32433 gcc-8_8.3.0-3.dsc b3430f476c16fc8607c508da13121a091fc9ef57 684830 gcc-8_8.3.0-3.diff.gz bcc2d9f108f3c764da3fe17695af8c690b0dabb6 10310 gcc-8_8.3.0-3_source.buildinfo Checksums-Sha256: 0c737e3b3d6169a43177b10568a035990d555b59312408710c40a7fe1b576085 32433 gcc-8_8.3.0-3.dsc c1241b56a675f0112ae4d8db87abdef7c5707fe1048ca11849d8e886aec91e80 684830 gcc-8_8.3.0-3.diff.gz 688bb43186adc2da03eb1b7040588cdbb3594e1b78762fee616f7a76a5a609a7 10310 gcc-8_8.3.0-3_source.buildinfo Files: 08f6674230675de176106b40f31a21c1 32433 devel optional gcc-8_8.3.0-3.dsc
Bug#866354: marked as done (armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6)
Your message dated Sat, 16 Mar 2019 11:19:16 + with message-id and subject line Bug#866354: fixed in gcc-8 8.3.0-3 has caused the Debian Bug report #866354, regarding armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 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.) -- 866354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++6 Version: 7.1.0-7 Severity: serious Control: affects -1 src:mesa mesa FTBFS on armel due to: https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=17.1.3-2=1498610882=0 ... llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference ... My first guess would be that the #727621 fix might be missing or broken in GCC 7. --- End Message --- --- Begin Message --- Source: gcc-8 Source-Version: 8.3.0-3 We believe that the bug you reported is fixed in the latest version of gcc-8, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-8 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: Sat, 16 Mar 2019 11:41:45 +0100 Source: gcc-8 Architecture: source Version: 8.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 866354 Changes: gcc-8 (8.3.0-3) unstable; urgency=medium . * Update to SVN 20190316 (r269720) from the gcc-8-branch. - Fix PR tree-optimization/89505, PR target/89517 (AArch64), PR bootstrap/89539, PR debug/88878, PR debug/89514, PR tree-optimization/89536, PR target/88100 (PPC), PR target/89397 (x86), PR target/89361 (S390), PR c++/89212, PR fortran/89077, PR fortran/77583, PR fortran/89174, PR fortran/87689, PR fortran/84387, PR fortran/89516, PR fortran/89492, PR fortran/89266, PR fortran/88326, PR libfortran/89020, PR target/88530 (AArch64), PR target/88530 (AArch64), PR ipa/88235, PR c++/88820, PR c++/88869, PR c++/88419, PR c++/88690, PR c++/87921, PR c++/89381, PR c++/89576, PR c++/89422, PR c++/87513, PR c++/88183, PR c++/89585, PR fortran/71544, PR fortran/87734, PR fortran/71203, PR fortran/72714, PR middle-end/89572, PR target/85860, PR middle-end/89677, PR middle-end/89497, PR tree-optimization/89296, PR tree-optimization/89664, PR rtl-optimization/89588, PR lto/88147, PR target/86952 (x86), PR lto/88147, PR fortran/87673, PR c++/89383, PR lto/87525, PR other/89712, PR testsuite/85368. * Backport libgo patches for the Hurd from the trunk (Svante Signell). * Add some more breaks to libstdc++6. Closes: #866354. Checksums-Sha1: 289eef74f89e06705557422c66f9d43dfe25a251 32433 gcc-8_8.3.0-3.dsc b3430f476c16fc8607c508da13121a091fc9ef57 684830 gcc-8_8.3.0-3.diff.gz bcc2d9f108f3c764da3fe17695af8c690b0dabb6 10310 gcc-8_8.3.0-3_source.buildinfo Checksums-Sha256: 0c737e3b3d6169a43177b10568a035990d555b59312408710c40a7fe1b576085 32433 gcc-8_8.3.0-3.dsc c1241b56a675f0112ae4d8db87abdef7c5707fe1048ca11849d8e886aec91e80 684830 gcc-8_8.3.0-3.diff.gz 688bb43186adc2da03eb1b7040588cdbb3594e1b78762fee616f7a76a5a609a7 10310 gcc-8_8.3.0-3_source.buildinfo Files
Processed: bug 918389 is forwarded to https://github.com/attr-encrypted/attr_encrypted/pull/337
Processing commands for cont...@bugs.debian.org: > forwarded 918389 https://github.com/attr-encrypted/attr_encrypted/pull/337 Bug #918389 [src:ruby-attr-encrypted] ruby-attr-encrypted FTBFS with rails 5.2.0 Set Bug forwarded-to-address to 'https://github.com/attr-encrypted/attr_encrypted/pull/337'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924230: marked as done (jekyll: Could not load bundler)
Your message dated Sat, 16 Mar 2019 11:04:14 + with message-id and subject line Bug#924230: fixed in jekyll 3.8.3+dfsg-4 has caused the Debian Bug report #924230, regarding jekyll: Could not load bundler 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.) -- 924230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jekyll Version: 3.8.3+dfsg-3.1 Severity: grave Justification: renders package unusable Dear Maintainer, On Debian buster/sid. Creating a fresh site gives me a warning related to bundler. $ jekyll new mysite Could not load Bundler. Bundle install skipped. New jekyll site installed in /home/username/mysite. The site seems to be created as the directory and the main files of the site are present but I can't run a local server. $ cd mysite $ jekyll serve Traceback (most recent call last): 3: from /usr/bin/jekyll:9:in `' 2: from /usr/lib/ruby/vendor_ruby/jekyll/plugin_manager.rb:48:in `require_from_bundler' 1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- bundler (LoadError) Maybe bundler is missing? -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jekyll depends on: ii ruby1:2.5.1 ii ruby-addressable2.5.2-1 ii ruby-classifier-reborn 2.2.0-1 ii ruby-colorator 1.1.0-1 ii ruby-em-websocket 0.5.1-2 ii ruby-i18n 1.5.3-1 ii ruby-jekyll-coffeescript1.0.1-2 ii ruby-jekyll-feed0.3.1-1 ii ruby-jekyll-gist1.5.0-1 ii ruby-jekyll-paginate1.1.0-1 ii ruby-jekyll-sass-converter 1.5.2-1 ii ruby-jekyll-watch 2.0.0-1 ii ruby-kramdown 1.17.0-1 ii ruby-launchy-shim 2.3.0.1 ii ruby-liquid 4.0.1-1 ii ruby-mercenary 0.3.6-1 ii ruby-mime-types 3.2.2-1 ii ruby-pathutil 0.16.1-1 ii ruby-pygments.rb1.2.0-2 ii ruby-rdiscount 2.1.8-1+b5 ii ruby-redcarpet 3.4.0-4+b1 ii ruby-rouge 3.3.0-1 ii ruby-safe-yaml 1.0.4-2 ii ruby-toml 0.2.0-3 ii xdg-utils 1.1.3-1 Versions of packages jekyll recommends: pn ruby-mysql ii ruby-sequel 5.15.0-1 pn ruby-sequel-pg jekyll suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: jekyll Source-Version: 3.8.3+dfsg-4 We believe that the bug you reported is fixed in the latest version of jekyll, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Youhei SASAKI (supplier of updated jekyll 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: Sat, 16 Mar 2019 19:33:25 +0900 Source: jekyll Binary: jekyll Architecture: source all Version: 3.8.3+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Youhei SASAKI Description: jekyll - Simple, blog aware, static site generator Closes: 924230 Changes: jekyll (3.8.3+dfsg-4) unstable; urgency=medium . * d/control: Add bundler to Depends (Closes: #924230) Checksums-Sha1: 972d2417c1508d9565d4fdf433282dfeb0193a2e 2682 jekyll_3.8.3+dfsg-4.dsc 49ac89a3d7ab10e57ee7028d21aa23e4eabfaf11 837722 jekyll_3.8.3+dfsg.orig.tar.gz 9d44006f9386b6995e5853ba7d316ffbd81b 30528 jekyll_3.8.3+dfsg-4.debian.tar.xz 6ef137cc4e54f89de60bd288c9e7fcd0dfd2e309 99640 jekyll_3.8.3+dfsg-4_all.deb ab047a00b826d2dcbc943ea1f2a56b352f136763 23809 jekyll_3.8.3+dfsg-4_amd64.buildinfo Checksums-Sha256:
Processed: Bug #924230 in jekyll marked as pending
Processing control commands: > tag -1 pending Bug #924230 [jekyll] jekyll: Could not load bundler Added tag(s) pending. -- 924230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924230: Bug #924230 in jekyll marked as pending
Control: tag -1 pending Hello, Bug #924230 in jekyll 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/ruby-team/jekyll/commit/ed44f79c44372d18cab0780912f1f46a3cdc1f7b d/control: Add bundler to Depends (Closes: #924230) Signed-off-by: Youhei SASAKI (this message was generated automatically) -- Greetings https://bugs.debian.org/924230
Bug#924235: marked as done (tdiary-mode: fails to upgrade from 'stretch': http.el:36:1:Error: Cannot open load file: No such file or directory, pces)
Your message dated Sat, 16 Mar 2019 10:34:35 + with message-id and subject line Bug#924235: fixed in tdiary-contrib 5.0.11-2 has caused the Debian Bug report #924235, regarding tdiary-mode: fails to upgrade from 'stretch': http.el:36:1:Error: Cannot open load file: No such file or directory, pces 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.) -- 924235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tdiary-mode Version: 5.0.11-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): Setting up emacs-gtk (1:26.1+1-3.2) ... update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs (emacs) in auto mode update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) in auto mode Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install psgml for emacs install/psgml: Ignoring emacsen flavor emacs. Install tdiary-mode for emacs install/tdiary-mode-20170123.2324: Handling install of emacsen flavor emacs install/tdiary-mode-20170123.2324: byte-compiling for emacs In toplevel form: http.el:36:1:Error: Cannot open load file: No such file or directory, pces In toplevel form: tdiary-mode.el:74:1:Error: Cannot open load file: No such file or directory, pces ERROR: install script from tdiary-mode package failed dpkg: error processing package emacs-gtk (--configure): installed emacs-gtk package post-installation script subprocess returned error exit status 1 cheers, Andreas tdiary-mode_5.0.11-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: tdiary-contrib Source-Version: 5.0.11-2 We believe that the bug you reported is fixed in the latest version of tdiary-contrib, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Youhei SASAKI (supplier of updated tdiary-contrib 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: Sat, 16 Mar 2019 18:43:42 +0900 Source: tdiary-contrib Binary: tdiary-contrib tdiary-mode Architecture: source all Version: 5.0.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Youhei SASAKI Description: tdiary-contrib - Plugins of tDiary to add functionalities tdiary-mode - tDiary editing mode for Emacsen Closes: 924235 Changes: tdiary-contrib (5.0.11-2) unstable; urgency=medium . * Drop apel depends from tdiary-mode: (Closes: #924235) - The "apel" in Debian is not under dh-elpa's umbrella. So just import needed macro/function and drop depends of apel. Checksums-Sha1: 70f1eb2578fe831166a280d35c3f729bf9c7c8cd 2165 tdiary-contrib_5.0.11-2.dsc 6bd3d852ad4e872021ee50fefc4cc3f88452ec9d 371468 tdiary-contrib_5.0.11.orig.tar.gz 5e03cddf35c7aa1b88b19b99e3c9a2846195c1a7 52620 tdiary-contrib_5.0.11-2.debian.tar.xz 66aa0492a7a6e43be765e66560ee7dfe61843ad2 245188 tdiary-contrib_5.0.11-2_all.deb 118b4477fadbc6cca65232622bacd74cf5953165 14351 tdiary-contrib_5.0.11-2_amd64.buildinfo e1868af1dfb0ef0278ab5bbeb3fc85d11e172cf4 19676 tdiary-mode_5.0.11-2_all.deb Checksums-Sha256: 31dd2ca8e73bf82499ae2718d2ca27f948d9ff53930831653428174bb8fdb89c 2165 tdiary-contrib_5.0.11-2.dsc 4dd647afb64f7a925fc99a47837b2f5d463ff269bb560962883cf1152929a5bc 371468 tdiary-contrib_5.0.11.orig.tar.gz 8859cbe2c67624f27ea7531c9510ffbc6014e2c93cb0bda544084d4f810e6632 52620 tdiary-contrib_5.0.11-2.debian.tar.xz e2ed3a349e558a84e94c04a8cd80ab3a9c07a622e80c5f3d0ad51f3f0c8f2fe6 245188 tdiary-contrib_5.0.11-2_all.deb c4e6c9214e183dc9ab9b40f6f0ba5f1bac5c1d6478cf2b91c2e2f5f0bfacabc4 14351 tdiary-contrib_5.0.11-2_amd64.buildinfo c99b1265c903b4fe3158b8c3a5ae76bfef798d814e8043425441a0a5c856e35f 19676 tdiary-mode_5.0.11-2_all.deb Files:
Processed: Re: Bug#923238: libmarc-charset-perl: needs a rebuild on 32bit architectures?
Processing control commands: > clone -1 -2 Bug #923238 [libmarc-charset-perl] libmarc-charset-perl: needs a rebuild on 32bit architectures? Bug 923238 cloned as bug 924719 924719 was blocked by: 923609 924719 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #924719 to the same blocks previously set > retitle -2 perl: Break libmarc-charset-perl (<< 1.35-3) Bug #924719 [libmarc-charset-perl] libmarc-charset-perl: needs a rebuild on 32bit architectures? Changed Bug title to 'perl: Break libmarc-charset-perl (<< 1.35-3)' from 'libmarc-charset-perl: needs a rebuild on 32bit architectures?'. > reassign -2 perl 5.28.1-4 Bug #924719 [libmarc-charset-perl] perl: Break libmarc-charset-perl (<< 1.35-3) Bug reassigned from package 'libmarc-charset-perl' to 'perl'. No longer marked as found in versions libmarc-charset-perl/1.35-2. Ignoring request to alter fixed versions of bug #924719 to the same values previously set Bug #924719 [perl] perl: Break libmarc-charset-perl (<< 1.35-3) Marked as found in versions perl/5.28.1-4. -- 923238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923238 924719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923238: libmarc-charset-perl: needs a rebuild on 32bit architectures?
Control: clone -1 -2 Control: retitle -2 perl: Break libmarc-charset-perl (<< 1.35-3) Control: reassign -2 perl 5.28.1-4 On Wed, Mar 13, 2019 at 10:49:29PM +0100, gregor herrmann wrote: > On Wed, 13 Mar 2019 20:24:59 +0200, Niko Tyni wrote: > > > - have perl_5.28.1-5 Build-Depend on libgdbm-dev (>= 1.18-3) > > [any gdbm version built with LFS support would do, but 1.18-3 > >fixed other binary compat issues so pick that for safety] > > - have perl_5.28.1-5 Break libmarc-charset-perl (<< 1.35-3) > > - have libmarc-charset-perl_1.35-3 Build-Depend and Depend on > > perl (>= perl_5.28.1-5) > > Sounds right. Thanks. Cloning and reassigning. > > This will cause temporary uninstallability of libmarc-charset-perl in > > sid so the uploads should be coordinated a bit. I guess I can do both > > if needed. > > Thanks. > (If it helps I can also upload libmarc-charset-perl but maybe the > coordination effort is higher than if you just go ahead :)) Yeah, thanks. I'll try to handle this myself. -- Niko
Bug#924583: razor2 servers
I have the same issue. related Ubuntu Bug: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5557337.html pgpQcjgBt8sst.pgp Description: Digitale Signatur von OpenPGP
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
FTR: https://bugzilla.redhat.com/show_bug.cgi?id=1566464
Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and
Hi, On Sat, 16 Mar 2019 09:37:04 +0100 Andreas Beckmann wrote: > Does this conffile-to-symlink transition work cleanly on upgrades? i.e. > does dpkg "forget" about the conffile? > I'd expect that you may need dpkg-maintscript_helper rm_conffile and > create the symlink manually in the postinst ... Yes, it is. I've tested it with sudo piuparts --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database \ --warn-on-leftovers-after-purge --mirror 'http://debian-mirror.sakura.ne.jp/debian/ main' \ --arch amd64 -b /home/henrich/tmp/buster.tgz -d testing -d sid \ squid-deb-proxy-client_0.8.14+nmu2_all.deb and local machine. -- Hideki Yamane
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
Package: libc6-dev Version: 2.28-8 Severity: serious Hi, The crypt.3 manpage, state that _XOPEN_SOURCE should be define for crypt() to be available. But it looks that it's currently the opposite, if _XOPEN_SOURCE is defined, the function cannot be found. This actually looks like a regression compared to stretch. Regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-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 Versions of packages manpages-dev depends on: ii manpages 4.16-1 manpages-dev recommends no packages. Versions of packages manpages-dev suggests: ii man-db [man-browser] 2.8.5-2 -- no debconf information
Bug#921767: CVE-2018-12029
Hi,
On Fri, Feb 08, 2019 at 10:50:41PM +0100, Moritz Muehlenhoff wrote:
> Source: passenger
> Severity: grave
> Tags: security
>
> This was assigned CVE-2018-12029:
> https://blog.phusion.nl/2018/06/12/passenger-5-3-2-various-security-fixes/
> https://github.com/phusion/passenger/commit/207870f5b7f5cc240587ab0977d6046782ae1d86
I think this issue should be lowered to minor or normal as it to fix
the issue specifically in the nginx module, which AFAICS is not build
in the Debian build.
Do I miss something?
I have a NMU for the current two passenger issues, which still
includes the changes for CVE-2018-12029.
Regards,
Salvatore
diff -Nru passenger-5.0.30/debian/changelog passenger-5.0.30/debian/changelog
--- passenger-5.0.30/debian/changelog 2016-08-21 19:24:14.0 +0200
+++ passenger-5.0.30/debian/changelog 2019-03-16 08:54:26.0 +0100
@@ -1,3 +1,13 @@
+passenger (5.0.30-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * arbitrary file read via REVISION symlink (CVE-2017-16355)
+(Closes: #884463)
+ * Fix privilege escalation in the Nginx module (CVE-2018-12029)
+(Closes: #921767)
+
+ -- Salvatore Bonaccorso Sat, 16 Mar 2019 08:54:26 +0100
+
passenger (5.0.30-1) unstable; urgency=medium
* New upstream release.
diff -Nru passenger-5.0.30/debian/patches/CVE-2017-16355.patch
passenger-5.0.30/debian/patches/CVE-2017-16355.patch
--- passenger-5.0.30/debian/patches/CVE-2017-16355.patch1970-01-01
01:00:00.0 +0100
+++ passenger-5.0.30/debian/patches/CVE-2017-16355.patch2019-03-16
08:48:13.0 +0100
@@ -0,0 +1,73 @@
+From: "Daniel Knoppel (Phusion)"
+Date: Wed, 11 Oct 2017 15:55:07 +0200
+Subject: arbitrary file read via REVISION symlink
+Origin:
https://github.com/phusion/passenger/commit/4043718264095cde6623c2cbe8c644541036d7bf,
+
https://github.com/phusion/passenger/commit/947af424330f5d5f5006860b2f0140bbba153e42
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2017-16355
+Bug-Debian: https://bugs.debian.org/884463
+
+[carnil: false is actually a defined macro, but the key part of the fix is the
emoval of the call to inferApplicationInfo() to adress the issue.
+---
+ src/agent/Core/SpawningKit/Spawner.h | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+--- a/src/agent/Core/SpawningKit/Spawner.h
b/src/agent/Core/SpawningKit/Spawner.h
+@@ -719,7 +719,6 @@ protected:
+ prepareChroot(info, options);
+ info.userSwitching = prepareUserSwitching(options);
+ prepareSwitchingWorkingDirectory(info, options);
+- inferApplicationInfo(info);
+ return info;
+ }
+
+@@ -773,49 +772,6 @@ protected:
+ assert(info.appRootPathsInsideChroot.back() ==
info.appRootInsideChroot);
+ }
+
+- void inferApplicationInfo(SpawnPreparationInfo ) const {
+- info.codeRevision = readFromRevisionFile(info);
+- if (info.codeRevision.empty()) {
+- info.codeRevision =
inferCodeRevisionFromCapistranoSymlink(info);
+- }
+- }
+-
+- string readFromRevisionFile(const SpawnPreparationInfo ) const {
+- string filename = info.appRoot + "/REVISION";
+- try {
+- if (fileExists(filename)) {
+- return strip(readAll(filename));
+- }
+- } catch (const SystemException ) {
+- P_WARN("Cannot access " << filename << ": " <<
e.what());
+- }
+- return string();
+- }
+-
+- string inferCodeRevisionFromCapistranoSymlink(const
SpawnPreparationInfo ) const {
+- if (extractBaseName(info.appRoot) == "current") {
+- char buf[PATH_MAX + 1];
+- ssize_t ret;
+-
+- do {
+- ret = readlink(info.appRoot.c_str(), buf,
PATH_MAX);
+- } while (ret == -1 && errno == EINTR);
+- if (ret == -1) {
+- if (errno == EINVAL) {
+- return string();
+- } else {
+- int e = errno;
+- P_WARN("Cannot read symlink " <<
info.appRoot << ": " << strerror(e));
+- }
+- }
+-
+- buf[ret] = '\0';
+- return extractBaseName(buf);
+- } else {
+- return string();
+- }
+- }
+-
+ bool shouldLoadShellEnvvars(const Options , const
SpawnPreparationInfo ) const {
+ if (options.loadShellEnvvars) {
+ string shellName =
extractBaseName(preparation.userSwitching.shell);
diff -Nru
passenger-5.0.30/debian/patches/Fix-privilege-escalation-in-the-Nginx-module.patch
Bug#884463: passenger: CVE-2017-16355: arbitrary file read
Control: tags -1 + patch
Attaching proposed debdiff for NMU, but I'm awaiting confirmation in
#921767 to see if I miss something about the nginx module.
Regards,
Salvatore
diff -Nru passenger-5.0.30/debian/changelog passenger-5.0.30/debian/changelog
--- passenger-5.0.30/debian/changelog 2016-08-21 19:24:14.0 +0200
+++ passenger-5.0.30/debian/changelog 2019-03-16 08:54:26.0 +0100
@@ -1,3 +1,13 @@
+passenger (5.0.30-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * arbitrary file read via REVISION symlink (CVE-2017-16355)
+(Closes: #884463)
+ * Fix privilege escalation in the Nginx module (CVE-2018-12029)
+(Closes: #921767)
+
+ -- Salvatore Bonaccorso Sat, 16 Mar 2019 08:54:26 +0100
+
passenger (5.0.30-1) unstable; urgency=medium
* New upstream release.
diff -Nru passenger-5.0.30/debian/patches/CVE-2017-16355.patch
passenger-5.0.30/debian/patches/CVE-2017-16355.patch
--- passenger-5.0.30/debian/patches/CVE-2017-16355.patch1970-01-01
01:00:00.0 +0100
+++ passenger-5.0.30/debian/patches/CVE-2017-16355.patch2019-03-16
08:48:13.0 +0100
@@ -0,0 +1,73 @@
+From: "Daniel Knoppel (Phusion)"
+Date: Wed, 11 Oct 2017 15:55:07 +0200
+Subject: arbitrary file read via REVISION symlink
+Origin:
https://github.com/phusion/passenger/commit/4043718264095cde6623c2cbe8c644541036d7bf,
+
https://github.com/phusion/passenger/commit/947af424330f5d5f5006860b2f0140bbba153e42
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2017-16355
+Bug-Debian: https://bugs.debian.org/884463
+
+[carnil: false is actually a defined macro, but the key part of the fix is the
emoval of the call to inferApplicationInfo() to adress the issue.
+---
+ src/agent/Core/SpawningKit/Spawner.h | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+--- a/src/agent/Core/SpawningKit/Spawner.h
b/src/agent/Core/SpawningKit/Spawner.h
+@@ -719,7 +719,6 @@ protected:
+ prepareChroot(info, options);
+ info.userSwitching = prepareUserSwitching(options);
+ prepareSwitchingWorkingDirectory(info, options);
+- inferApplicationInfo(info);
+ return info;
+ }
+
+@@ -773,49 +772,6 @@ protected:
+ assert(info.appRootPathsInsideChroot.back() ==
info.appRootInsideChroot);
+ }
+
+- void inferApplicationInfo(SpawnPreparationInfo ) const {
+- info.codeRevision = readFromRevisionFile(info);
+- if (info.codeRevision.empty()) {
+- info.codeRevision =
inferCodeRevisionFromCapistranoSymlink(info);
+- }
+- }
+-
+- string readFromRevisionFile(const SpawnPreparationInfo ) const {
+- string filename = info.appRoot + "/REVISION";
+- try {
+- if (fileExists(filename)) {
+- return strip(readAll(filename));
+- }
+- } catch (const SystemException ) {
+- P_WARN("Cannot access " << filename << ": " <<
e.what());
+- }
+- return string();
+- }
+-
+- string inferCodeRevisionFromCapistranoSymlink(const
SpawnPreparationInfo ) const {
+- if (extractBaseName(info.appRoot) == "current") {
+- char buf[PATH_MAX + 1];
+- ssize_t ret;
+-
+- do {
+- ret = readlink(info.appRoot.c_str(), buf,
PATH_MAX);
+- } while (ret == -1 && errno == EINTR);
+- if (ret == -1) {
+- if (errno == EINVAL) {
+- return string();
+- } else {
+- int e = errno;
+- P_WARN("Cannot read symlink " <<
info.appRoot << ": " << strerror(e));
+- }
+- }
+-
+- buf[ret] = '\0';
+- return extractBaseName(buf);
+- } else {
+- return string();
+- }
+- }
+-
+ bool shouldLoadShellEnvvars(const Options , const
SpawnPreparationInfo ) const {
+ if (options.loadShellEnvvars) {
+ string shellName =
extractBaseName(preparation.userSwitching.shell);
diff -Nru
passenger-5.0.30/debian/patches/Fix-privilege-escalation-in-the-Nginx-module.patch
passenger-5.0.30/debian/patches/Fix-privilege-escalation-in-the-Nginx-module.patch
---
passenger-5.0.30/debian/patches/Fix-privilege-escalation-in-the-Nginx-module.patch
1970-01-01 01:00:00.0 +0100
+++
passenger-5.0.30/debian/patches/Fix-privilege-escalation-in-the-Nginx-module.patch
2019-03-16 08:51:30.0 +0100
@@ -0,0 +1,52 @@
+From: Camden Narzt
+Date: Mon, 14 May 2018 08:34:12 -0600
+Subject: Fix privilege escalation in the Nginx module
Processed: Re: Bug#884463: passenger: CVE-2017-16355: arbitrary file read
Processing control commands: > tags -1 + patch Bug #884463 [src:passenger] passenger: CVE-2017-16355: arbitrary file read Ignoring request to alter tags of bug #884463 to the same tags previously set -- 884463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and
On 2019-03-16 07:58, Hideki Yamane wrote: > How about moving 30autoproxy to /usr/share and create symlink under > /etc/apt/apt.conf.d to it? Here's a patch, works well after package > removal and piuparts clean one. Does this conffile-to-symlink transition work cleanly on upgrades? i.e. does dpkg "forget" about the conffile? I'd expect that you may need dpkg-maintscript_helper rm_conffile and create the symlink manually in the postinst ... Andreas
Bug#923804: marked as done (golang-github-ncw-swift: FTBFS randomly (TestWatchdogReaderOnSlowNetwork fails))
Your message dated Sat, 16 Mar 2019 08:35:46 + with message-id and subject line Bug#923804: fixed in golang-github-ncw-swift 0.0~git20180327.b2a7479-2 has caused the Debian Bug report #923804, regarding golang-github-ncw-swift: FTBFS randomly (TestWatchdogReaderOnSlowNetwork fails) 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.) -- 923804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-ncw-swift Version: 0.0~git20180327.b2a7479-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/<>/golang-github-ncw-swift-0.0\~git20180327.b2a7479/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/<>/golang-github-ncw-swift-0.0\~git20180327.b2a7479/obj-x86_64-linux-gnu/src\" -v -p 2 github.com/ncw/swift github.com/ncw/swift/rs github.com/ncw/swift/swifttest errors internal/cpu internal/race runtime/internal/atomic runtime/internal/sys internal/bytealg sync/atomic unicode runtime unicode/utf8 crypto/subtle math math/bits strconv crypto/internal/subtle internal/testlog encoding unicode/utf16 container/list crypto/rc4 vendor/golang_org/x/crypto/cryptobyte/asn1 vendor/golang_org/x/net/dns/dnsmessage internal/nettrace runtime/cgo vendor/golang_org/x/crypto/curve25519 sync io syscall bytes bufio hash crypto/hmac crypto crypto/md5 crypto/cipher internal/syscall/unix reflect crypto/aes time internal/poll os encoding/binary fmt math/rand strings crypto/sha1 math/big encoding/hex encoding/base64 sort encoding/json crypto/rand path/filepath mime io/ioutil compress/flate hash/crc32 context crypto/des compress/gzip crypto/elliptic crypto/internal/randutil crypto/sha512 encoding/asn1 crypto/rsa crypto/sha256 crypto/ecdsa crypto/dsa crypto/x509/pkix encoding/pem vendor/golang_org/x/crypto/cryptobyte internal/singleflight net net/url vendor/golang_org/x/crypto/internal/chacha20 vendor/golang_org/x/crypto/poly1305 vendor/golang_org/x/crypto/chacha20poly1305 vendor/golang_org/x/text/transform log vendor/golang_org/x/text/unicode/bidi vendor/golang_org/x/text/secure/bidirule vendor/golang_org/x/text/unicode/norm vendor/golang_org/x/net/idna vendor/golang_org/x/net/http2/hpack mime/quotedprintable net/http/internal path flag regexp/syntax crypto/x509 net/textproto vendor/golang_org/x/net/http/httpguts vendor/golang_org/x/net/http/httpproxy mime/multipart regexp crypto/tls runtime/debug runtime/trace testing net/http/httptrace net/http net/http/httptest github.com/ncw/swift github.com/ncw/swift/swifttest github.com/ncw/swift/rs debian/rules override_dh_auto_test make[1]: Entering directory '/<>' # some tests want to hit a remote API and spin up remote resources ($$) so skip them DH_GOLANG_EXCLUDES='github.com/ncw/swift/rs' dh_auto_test cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 github.com/ncw/swift github.com/ncw/swift/swifttest Waiting for server to start .. Started === RUN TestHeadersToMetadata --- PASS: TestHeadersToMetadata (0.00s) === RUN TestHeadersToAccountMetadata --- PASS: TestHeadersToAccountMetadata (0.00s) === RUN TestHeadersToContainerMetadata --- PASS: TestHeadersToContainerMetadata (0.00s) === RUN TestHeadersToObjectMetadata --- PASS: TestHeadersToObjectMetadata (0.00s) === RUN TestMetadataToHeaders --- PASS: TestMetadataToHeaders (0.00s) === RUN TestMetadataToAccountHeaders --- PASS: TestMetadataToAccountHeaders (0.00s) === RUN TestMetadataToContainerHeaders --- PASS: TestMetadataToContainerHeaders (0.00s) === RUN TestMetadataToObjectHeaders --- PASS: TestMetadataToObjectHeaders (0.00s) === RUN TestNsToFloatString --- PASS: TestNsToFloatString (0.00s) === RUN TestFloatStringToNs --- PASS: TestFloatStringToNs (0.00s) === RUN TestGetModTime --- PASS: TestGetModTime (0.00s) === RUN TestSetModTime --- PASS: TestSetModTime (0.00s) === RUN TestInternalError --- PASS: TestInternalError (0.00s) === RUN TestInternalCheckClose --- PASS: TestInternalCheckClose (0.00s) === RUN TestInternalParseHeaders --- PASS: TestInternalParseHeaders (0.00s) === RUN TestInternalReadHeaders --- PASS:
Bug#924651: Bug #924651 in pyqwt5 marked as pending
Control: tag -1 pending Hello, Bug #924651 in pyqwt5 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/python-team/modules/pyqwt5/commit/a4d076817bd8d142a38f276fade7213d260c6548 Add patch to fix build error (Closes: #924651) (this message was generated automatically) -- Greetings https://bugs.debian.org/924651
Processed: Bug #924651 in pyqwt5 marked as pending
Processing control commands: > tag -1 pending Bug #924651 [src:pyqwt5] pyqwt5: FTBFS (An internal error occured. Please report all the output) Added tag(s) pending. -- 924651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923804: Bug #923804 in golang-github-ncw-swift marked as pending
Control: tag -1 pending Hello, Bug #923804 in golang-github-ncw-swift 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/go-team/packages/golang-github-ncw-swift/commit/c795e6789156ecb51ebad0cea66c6249e9e9b9a0 Add patch to fix unreliable test (Closes: #923804) + Fix TestWatchdogReaderOnSlowNetwork (this message was generated automatically) -- Greetings https://bugs.debian.org/923804
Processed: Bug #923804 in golang-github-ncw-swift marked as pending
Processing control commands: > tag -1 pending Bug #923804 [src:golang-github-ncw-swift] golang-github-ncw-swift: FTBFS randomly (TestWatchdogReaderOnSlowNetwork fails) Added tag(s) pending. -- 923804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924666: [hostapd] [buster on stretch] invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
Hi, I am trying to install on Debian buster hostapd release on stretch target This job was ok in december 2018, but now, it seems there is one regression in the package, because : ansible@srv-authenticator-100:~$ sudo apt install -t buster hostapd Reading package lists... Done Building dependency tree Reading state information... Done hostapd is already the newest version (2:2.7+git20190128+0c1e29f-2). 0 upgraded, 0 newly installed, 0 to remove and 303 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up hostapd (2:2.7+git20190128+0c1e29f-2) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error processing package hostapd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: hostapd E: Sub-process /usr/bin/dpkg returned an error code (1) ansible@srv-authenticator-100:~$ My environment is : ansible@srv-authenticator-100:~$ pstree -an init |-logsave -s /var/log/fsck/checkfs fsck -M -A -a |-dhclient -4 -v -pf /run/dhclient.eth-admin.pid -lf /var/lib/dhcp/dhclient.eth-admin.leases -I -df /var/lib/dhcp/dhclient6.eth-admin.leases eth-admin |-dhclient -4 -v -pf /run/dhclient.eth-srv.pid -lf /var/lib/dhcp/dhclient.eth-srv.leases -I -df /var/lib/dhcp/dhclient6.eth-srv.leases eth-srv |-dhclient -4 -v -pf /run/dhclient.eth-user.pid -lf /var/lib/dhcp/dhclient.eth-user.leases -I -df /var/lib/dhcp/dhclient6.eth-user.leases eth-user |-dhclient -4 -v -pf /run/dhclient.eth-wifi.pid -lf /var/lib/dhcp/dhclient.eth-wifi.leases -I -df /var/lib/dhcp/dhclient6.eth-wifi.leases eth-wifi |-syslog-ng | `-syslog-ng -p /var/run/syslog-ng.pid --no-caps |-cron |-sshd | `-sshd | `-sshd | `-bash | `-pstree -an |-getty 115200 console |-getty 38400 tty2 |-getty 38400 tty3 `-getty 38400 tty4 Thanks in advance for your help
Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and
system upgraded to stretch Message-Id: <20190316155830.288514652de850440de12...@iijmio-mail.jp> In-Reply-To: <1540574...@msgid.manchmal.in-ulm.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt" This is a multi-part message in MIME format. --Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit control: tags -1 +patch Hi, On Fri, 26 Oct 2018 19:27:05 +0200 Christoph Biedl wrote: > So the only solution I can think of was to either move > apt-avahi-discover to /etc/ (not quite good style), or to create a small > wrapper script in /etc/ that just does the check as above - not the best > thing as well, but should do the trick. > > Did I miss something? How about moving 30autoproxy to /usr/share and create symlink under /etc/apt/apt.conf.d to it? Here's a patch, works well after package removal and piuparts clean one. -- Hideki Yamane --Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt Content-Type: text/x-diff; name="bug867682.patch" Content-Disposition: attachment; filename="bug867682.patch" Content-Transfer-Encoding: 7bit diff -Nru squid-deb-proxy-0.8.14+nmu1/Makefile squid-deb-proxy-0.8.14+nmu2/Makefile --- squid-deb-proxy-0.8.14+nmu1/Makefile2018-08-16 03:25:06.0 +0900 +++ squid-deb-proxy-0.8.14+nmu2/Makefile2019-03-16 15:30:32.0 +0900 @@ -19,4 +19,4 @@ install -m 644 mirror-dstdomain.acl $(DESTDIR)/etc/squid-deb-proxy/ # client install -m 755 apt-avahi-discover $(DESTDIR)/usr/share/squid-deb-proxy-client/ - install -m 644 30autoproxy $(DESTDIR)/etc/apt/apt.conf.d + install -m 644 30autoproxy $(DESTDIR)/usr/share/squid-deb-proxy-client/ diff -Nru squid-deb-proxy-0.8.14+nmu1/debian/changelog squid-deb-proxy-0.8.14+nmu2/debian/changelog --- squid-deb-proxy-0.8.14+nmu1/debian/changelog2018-08-16 03:25:06.0 +0900 +++ squid-deb-proxy-0.8.14+nmu2/debian/changelog2019-03-16 15:30:32.0 +0900 @@ -1,3 +1,12 @@ +squid-deb-proxy (0.8.14+nmu2) unstable; urgency=medium + + * Non-maintainer upload. + * move /etc/apt/conf.d/30autoproxy to under /usr/share/squid-deb-proxy-client +and make symlink to it, to avoid package fetch failure after removed its +package (Closes: #867682) + + -- Hideki Yamane Sat, 16 Mar 2019 15:30:32 +0900 + squid-deb-proxy (0.8.14+nmu1) unstable; urgency=medium * Non-maintainer upload with maintainer consent diff -Nru squid-deb-proxy-0.8.14+nmu1/debian/squid-deb-proxy-client.links squid-deb-proxy-0.8.14+nmu2/debian/squid-deb-proxy-client.links --- squid-deb-proxy-0.8.14+nmu1/debian/squid-deb-proxy-client.links 1970-01-01 09:00:00.0 +0900 +++ squid-deb-proxy-0.8.14+nmu2/debian/squid-deb-proxy-client.links 2019-03-16 15:30:32.0 +0900 @@ -0,0 +1 @@ +usr/share/squid-deb-proxy-client/30autoproxy etc/apt/apt.conf.d/30autoproxy --Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt--
Processed: severity of 924692 is serious
Processing commands for cont...@bugs.debian.org: > severity 924692 serious Bug #924692 [apport] apport: /var/crash/.lock created insecurely Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 924692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 924692 is grave, severity of 924693 is grave
Processing commands for cont...@bugs.debian.org: > severity 924692 grave Bug #924692 [apport] apport: /var/crash/.lock created insecurely Severity set to 'grave' from 'serious' > severity 924693 grave Bug #924693 [apport] apport: /var/crash/.lock is world-writable Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 924692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924692 924693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
