Bug#903683: libvpf.so: undefined symbols: needs -lm
Control: tags -1 pending Hi Paul, Thanks for reporting this issue, it's been fixed in git but a new upload to unstable won't follow shortly. Probably at the next policy update or otherwise before the buster freeze. Kind Regards, Bas signature.asc Description: OpenPGP digital signature
Bug#903683: libvpf.so: undefined symbols: needs -lm
Package: libogdi3.2 Version: 3.2.1+ds-3 Severity: minor File: /usr/lib/libvpf.so.3.2 User: debian...@lists.debian.org Usertags: undefined-symbol adequate libvpf.so needs to link with -lm, see the output of adequate, symtree and objdump below. I detected this on amd64 but the Debian build log scanner also detected dpkg-buildpackage complaining about it on other architectures, see the w3m/getbuildlog output below. I filed this bug at severity minor since everything currently in Debian that uses libogdi3.2 (GDAL) seems to also use libm.so. This bug report brought to you by adequate: http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/ https://piuparts.debian.org/sid/undefined_symbol_inadequate_issue.html https://piuparts.debian.org/sid/pass/libogdi3.2_3.2.1+ds-3.log $ adequate libogdi3.2 libogdi3.2: undefined-symbol /usr/lib/libvpf.so.3.2 => sincos libogdi3.2: undefined-symbol /usr/lib/libvpf.so.3.2 => acos libogdi3.2: undefined-symbol /usr/lib/libvpf.so.3.2 => cos $ man adequate | grep -A6 undefined-symbol undefined-symbol The symbol has not been found in the libraries linked with the binary. Either the binary either needs to be linked with an additional shared library, or the dependency on the shared library package that provides this symbol is too weak. References: Debian Policy §3.5, §8.6, §10.2. $ lddtree /usr/lib/libvpf.so.3.2 libvpf.so.3.2 => /usr/lib/libvpf.so.3.2 (interpreter => none) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 $ symtree /usr/lib/libvpf.so.3.2 /usr/lib/libvpf.so.3.2 libc.so.6 => __stpcpy_chk,strcpy,__printf_chk,exit,readdir,fopen,strncmp,strrchr,closedir,ftell,strncpy,puts,__stack_chk_fail,realloc,abort,memchr,strspn,rewind,strtod,strtol,feof,fgetc,calloc,strlen,tmpfile,memset,fseek,memcmp,__fprintf_chk,memcpy,memcpy,fclose,malloc,strcasecmp,opendir,getenv,stderr,strncasecmp,__fxstat,fileno,fwrite,fread,__memcpy_chk,strchr,iconv,qsort,iconv_open,__ctype_toupper_loc,__strcpy_chk,__ctype_tolower_loc,__cxa_finalize,__sprintf_chk,memmove,access,__strcat_chk,strcmp,free WEAK => _ITM_deregisterTMCloneTable,__gmon_start__,_ITM_registerTMCloneTable UNRESOLVED => sincos,acos,cos $ objdump -T /lib/x86_64-linux-gnu/libm.so.6 | grep -E " ($(symtree /usr/lib/libvpf.so.3.2 | sed -n 's/UNRESOLVED => //p' | tr , '|'))$" e910 w DF .text 0042 GLIBC_2.2.5 acos 00037470 w iD .text 0047 GLIBC_2.2.5 cos 0003cf10 w DF .text 4fc2 GLIBC_2.2.5 sincos $ w3m -dump https://qa.debian.org/bls/packages/o/ogdi-dfsg.html | grep -A2 symbol • W shlibs-symbol-not-found (alpha, arm64, armel, armhf, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, m68k, mips, mips64el, mipsel, powerpc, powerpcspe, ppc64, ppc64el, riscv64, s390x, sh4, sparc64, x32) $ w3m -dump https://qa.debian.org/bls/bytag/W-shlibs-symbol-not-found.html | grep -A12 description description The build logs contains a like like dpkg-shlibdeps: warning: symbol NAME used by BINARY found in none of the libraries. Possible reasons: • A library not linked with a library needed. While this can sometimes make sense in order to allow the using binary to decide which of multiple available implementations to use, it means that dependency information might be incorrect, optimisations like prelinking might fail and stuff like that. $ chronic getbuildlog ogdi-dfsg last $ grep 'dpkg-shlibdeps: warning: symbol .* used by .* found in none of the libraries' *.log ogdi-dfsg_3.2.1+ds-3_alpha.log:dpkg-shlibdeps: warning: symbol ceil used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_alpha.log:dpkg-shlibdeps: warning: symbol acos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_alpha.log:dpkg-shlibdeps: warning: symbol sincos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_alpha.log:dpkg-shlibdeps: warning: symbol cos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_arm64.log:dpkg-shlibdeps: warning: symbol sincos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_arm64.log:dpkg-shlibdeps: warning: symbol cos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_arm64.log:dpkg-shlibdeps: warning: symbol acos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_armel.log:dpkg-shlibdeps: warning: symbol ceil used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries ogdi-dfsg_3.2.1+ds-3_armel.log:dpkg-shlibdeps: warning: symbol acos used by debian/libogdi3.2/usr/lib/libvpf.so.3.2 found in none of the libraries
Bug#903682: piuparts.debian.org: aggregate results for all suites on per-source-package pages
Package: piuparts.debian.org Severity: wishlist Currently the piuparts website has pages per source package per install/upgrade target. It would be nice to have per source package pages that aggregate all of the results for a source package. This could be used as a location for the Debian package tracker links sidebar to link to. The URLs for this could be something like this: https://piuparts.debian.org/source/s/somepkg.html -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#903270: RFS: sharness/1.0.0-1 [ITP] shell library for running tests
Hello Sergio, Am Thu, 12 Jul 2018 21:11:50 -0400 schrieb Sergio Durigan Junior : > [..] > Hm, it seems you removed an important line, [..] stumbling upon my own feet :( > 1) Since this is the first release of the package, a d/changelog with an > entry like: > [..] > would have been enough. Good to know - thank you. > 2) A word about git tags. I noticed you only have the "debian/1.0.0-1" > tag, but no "upstream/1.0.0" tag in your git repo. git-buildpackage > should have created that for you; it's worth checking to see if you > didn't forget to push. gbp ist still quite new to me ... I tagged the upstream release now. > Also, we usually don't create the "debian/xyz" tags until the package > has been uploaded and accepted into the archives. Good to know! > Hm, alright. The "aggregate-results.sh" may be useful to some users; it > provides a way to display the results in a nicer way, right? Indeed, the code looks like that. But I also expected it to adjust its exit code in case of errors. Thus it feels like a tool just for humans and not for testing. We will see, how upstream responds ... > Maybe you could install it under /usr/share/doc/sharness/contrib/, since it's > not an example script, but doesn't seem *that* important to justify polluting > the PATH. What do you think? That sounds good. I suggested this location in the discussion with upstream: https://github.com/chriscool/sharness/issues/78#issuecomment-404706089 Now I install this file via dh_install in the above location. But dh_install seems to remove the executable flag from the file (as the target path indicates a documentation file, I guess). Do you think, this is acceptable? Or would an "override_dh_auto_install" target be justified for a chown operation? I uploaded another source package for another round ... Thank you! Cheers, Lars
Bug#903647: ITP: wmmisc -- dockapp that monitors your system
On Thu, Jul 12, 2018 at 10:31 PM, Doug Torrance wrote: > wmmisc was removed in Debian in 2010. However, it was recently adopted > upstream and a new version released. Please note the extra steps required when reintroducing packages: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs -- bye, pabs https://wiki.debian.org/PaulWise
Bug#903655: libopenmpi-dev: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version
On Thu, 12 Jul 2018 22:35:04 +0800 Drew Parsons wrote: > > and petsc tests fail, reporting: Never mind petsc, a simpler test will do: $ mpirun -np 2 date [grendel:03595] mca_base_component_repository_open: unable to open mca_pmix_pmix2x: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version (ignored) [grendel:03595] [[29810,0],0] ORTE_ERROR_LOG: Not found in file ess_hnp_module.c at line 325
Bug#903288: change of the upstream bug report
Control: tags -1 - fixed-upstream Control: notforwarded -1 Control: forwarded -1 https://github.com/systemd/systemd/issues/2809 Update the upstream forwarded URI so that bts-link does the right thing. Ryutaroh
Bug#903011: two related bugs at the upstream
Control: tags -1 + upstream Control: found -1 239-5 I confirm that this bug 903011 still exists in 239-5. Two other bugs reported at the upstream https://github.com/systemd/systemd/issues/9502 https://github.com/systemd/systemd/issues/9578 probably have the same cause because the same workaround https://github.com/systemd/systemd/issues/9512#issuecomment-404270548 prevents all of them. Ryutaroh
Bug#665314: php-elisp: xemacs setups
Control: tag -1 + wontfix Hi Kevin, On Tue, Jun 26, 2012 at 08:24:23AM +1000, Kevin Ryde wrote: > Ola Lundqvist writes: > > > > Do you mean that the below code should replace > > /usr/lib/emacsen-common/packages/install/php-elisp > > Yep. > > The symlink bit I mentioned is now emacsen-common policy, > /usr/share/doc/emacsen-common/debian-emacs-policy.gz section 5 part E. > In /usr/lib/emacsen-common/packages/install/php-elisp "cp" becomes > "ln -s" and don't "rm *.el" (but do remove path.el). lua-mode is a > single-elfile package which does that, as an example to consult or copy > :). I hope you're not yet getting tired of these emails ;-) The Debian Emacsen team is adopting php-elisp, and will be converting the package to use dh-elpa. Consequently, xemacs support for this package will be dropped, as dh-elpa does not support xemacs. Kind regards, Nicholas signature.asc Description: PGP signature
Bug#903270: RFS: sharness/1.0.0-1 [ITP] shell library for running tests
On Thursday, July 12 2018, Lars Kruse wrote: > Hello Sergio, Hey Lars, > thank you for reviewing my packaging attempt! No problem. Thank you for packaging for Debian :-). > Am Wed, 11 Jul 2018 23:21:05 -0400 > schrieb Sergio Durigan Junior : > >> [..] >> 1) On d/copyright, you don't list the files under the "debian/" >> directory. These should be listed, and you should be the author. I >> recommend choosing the same license as upstream, just to make things >> simpler. >> >> 2) On d/control, Standards-Version should now be 4.1.5. >> >> 3) Better safe than sorry: on d/control, the Vcs-* fields should point >> to your salsa.d.o repo. > > Done (1-3). > > >> 4) On d/rules, you can remove the "override_dh_auto_install" target if >> you're not using it. > > Done. > I am a bit embarrassed, that I overlooked that cruft ... No need to be embarassed. That's why we do reviews :-). Hm, it seems you removed an important line, the one that was exporting the HOME variable. It's needed because the Makefile uses it to determine the install location. Also, some things I forgot to mention in my first review: 1) Since this is the first release of the package, a d/changelog with an entry like: sharness (1.0.0-1) unstable; urgency=medium * Initial release. (Closes: #902730). -- Lars Kruse Fri, 13 Jul 2018 00:47:01 +0200 would have been enough. But this is just to save you time; I definitely don't complain about extensive changelogs! 2) A word about git tags. I noticed you only have the "debian/1.0.0-1" tag, but no "upstream/1.0.0" tag in your git repo. git-buildpackage should have created that for you; it's worth checking to see if you didn't forget to push. Also, we usually don't create the "debian/xyz" tags until the package has been uploaded and accepted into the archives. This is because the "debian/xyz" tag is meant to indicate when a successful release of the package was made. > My recent upload contains another change besides the ones above: for now I > removed the helper script "aggregate-results.sh". > I started a discussion with upstream in order to decide whether that file > needs > to be included at all (https://github.com/chriscool/sharness/issues/78). Hm, alright. The "aggregate-results.sh" may be useful to some users; it provides a way to display the results in a nicer way, right? I understand the concerns you raised in the ticket, and don't have an immediate answer. Maybe you could install it under /usr/share/doc/sharness/contrib/, since it's not an example script, but doesn't seem *that* important to justify polluting the PATH. What do you think? >> Otherwise, the package looks good to me. Let me know when you address >> these issues and I'll be happy to upload it. > > Thank you for your kind offer! > I just uploaded my updated source package: > https://mentors.debian.net/debian/pool/main/s/sharness/sharness_1.0.0-1.dsc Thanks. I'll wait until you fix the issue with d/rules (readding the HOME variable), and then upload the package. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#889042: lintian: Do not use dot as a separator in build profile names
Control: tags -1 patch
Fix works on 2.5.50.4. This patch is for 2.5.92.Bug-Debian: https://bugs.debian.org/889042
Index: lintian-2.5.92/checks/control-file.desc
===
--- lintian-2.5.92.orig/checks/control-file.desc
+++ lintian-2.5.92/checks/control-file.desc
@@ -285,7 +285,7 @@ Info: The restriction formula in Build-P
"noudeb",
"stage1",
"stage2"
- and "pkg.srcpkg.anything".
+ and "pkg/srcpkg/anything".
Ref: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
Tag: multiline-architecture-field
Index: lintian-2.5.92/checks/control-file.pm
===
--- lintian-2.5.92.orig/checks/control-file.pm
+++ lintian-2.5.92/checks/control-file.pm
@@ -364,7 +364,7 @@ sub run {
tag 'invalid-profile-name-in-build-profiles-field',
$profile, $bin
unless $KNOWN_BUILD_PROFILES->known($profile)
- or $profile =~ /^pkg\.[a-z0-9][a-z0-9+.-]+\../;
+ or $profile =~ /^pkg\/[a-z0-9][a-z0-9+.-]+\/./;
}
}
}
Index: lintian-2.5.92/checks/fields.desc
===
--- lintian-2.5.92.orig/checks/fields.desc
+++ lintian-2.5.92/checks/fields.desc
@@ -669,7 +669,7 @@ Info: The restriction formula in the sou
"noudeb",
"stage1",
"stage2"
- and "pkg.srcpkg.anything".
+ and "pkg/srcpkg/anything".
Ref: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
Tag: build-depends-on-build-essential-package-without-using-version
Index: lintian-2.5.92/checks/fields.pm
===
--- lintian-2.5.92.orig/checks/fields.pm
+++ lintian-2.5.92/checks/fields.pm
@@ -1097,7 +1097,7 @@ sub run {
tag 'invalid-profile-name-in-source-relation',
"$prof [$field: $part_d_orig]"
unless $KNOWN_BUILD_PROFILES->known($prof)
- or $prof =~ /^pkg\.[a-z0-9][a-z0-9+.-]+\../;
+ or $prof =~ /^pkg\/[a-z0-9][a-z0-9+.-]+\/./;
}
}
Index: lintian-2.5.92/t/tests/fields-build-profiles-general/debian/debian/control.in
===
--- lintian-2.5.92.orig/t/tests/fields-build-profiles-general/debian/debian/control.in
+++ lintian-2.5.92/t/tests/fields-build-profiles-general/debian/debian/control.in
@@ -5,7 +5,7 @@ Maintainer: {$author}
Standards-Version: {$standards_version}
Build-Depends: {$build_depends},
big , bpfail1 ,
- bpcomplicated
+ bpcomplicated
Rules-Requires-Root: no
Package: {$source}-wrong-syntax
@@ -23,7 +23,7 @@ Description: {$description} (wrong synta
Package: {$source}-unknown-profile
Architecture: {$architecture}
Depends: $\{shlibs:Depends\}, $\{misc:Depends\}
-Build-Profiles:
+Build-Profiles:
Description: {$description} (unknown profile)
Check for unknown profile names
.
smime.p7s
Description: S/MIME cryptographic signature
Bug#903681: psf-unifont: Should not Depend on bdf2psf
Package: psf-unifont Version: 1:11.0.01-1 Severity: minor While this package clearly needs to Build-Depend on bdf2psf, I fail to see a clear reason for it to Depend on it. The font is perfectly usable without bdf2psf. Thanks, Jacob -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages psf-unifont depends on: ii bdf2psf 1.184 psf-unifont recommends no packages. Versions of packages psf-unifont suggests: ii ttf-unifont 1:11.0.01-1 -- no debconf information
Bug#886506: busybox: wrongly compiled with -mpreferred-stack-boundary=2 on i386
Control: severity -1 important Lowering severity because this stopped causing a crash after #887327 was fixed. Ben. -- Ben Hutchings Man invented language to satisfy his deep need to complain. - Lily Tomlin signature.asc Description: This is a digitally signed message part
Bug#903270: RFS: sharness/1.0.0-1 [ITP] shell library for running tests
Hello Sergio, thank you for reviewing my packaging attempt! Am Wed, 11 Jul 2018 23:21:05 -0400 schrieb Sergio Durigan Junior : > [..] > 1) On d/copyright, you don't list the files under the "debian/" > directory. These should be listed, and you should be the author. I > recommend choosing the same license as upstream, just to make things > simpler. > > 2) On d/control, Standards-Version should now be 4.1.5. > > 3) Better safe than sorry: on d/control, the Vcs-* fields should point > to your salsa.d.o repo. Done (1-3). > 4) On d/rules, you can remove the "override_dh_auto_install" target if > you're not using it. Done. I am a bit embarrassed, that I overlooked that cruft ... My recent upload contains another change besides the ones above: for now I removed the helper script "aggregate-results.sh". I started a discussion with upstream in order to decide whether that file needs to be included at all (https://github.com/chriscool/sharness/issues/78). > Otherwise, the package looks good to me. Let me know when you address > these issues and I'll be happy to upload it. Thank you for your kind offer! I just uploaded my updated source package: https://mentors.debian.net/debian/pool/main/s/sharness/sharness_1.0.0-1.dsc Cheers, Lars
Bug#868785: Fixes for excessive memory usage
Control: affects -1 isenkram Leaving a note on the symptomatic package bug list . . .
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
Ian Jackson writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu [and
1 more messages]"):
> This is now implemented in 5.9+exp1, just uploaded to Debian
> experimental. Can you give it a try in Ubuntu please ?
This trips what seems to be a bug in adt-virt-lxc; see #903680
and https://ci.debian.net/packages/d/dgit/unstable/amd64/.
5.9+exp3 (just uploaded) has what I think is the fix.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#868785: Fixes for excessive memory usage
Control: reassign -1 appstream Control: tags -1 patch upstream Control: forwarded -1 https://github.com/ximion/appstream/pull/193 I was also seeing isenkramd occupying huge and growing amounts of memory, increasing by several megabytes with each time a device was plugged in (in my case, when my monitor was turned on and its USB hub attached devices came back). I tracked this down to a leak in the appstream library, for which I submitted a patch upstream that's now been merged. We're just waiting on a new release of that and an upload to Debian, and this will be fixed.
Bug#903680: failure when test artifacts in $AUTOPKGTEST_ARTIFACTS not world-readable
Package: autopkgtest Version: 5.4.1 In https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dgit/597262/log.gz we see this autopkgtest [20:02:10]: test gitworktree: - - - - - - - - - - results - - - - - - - - - - gitworktree PASS cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/dd.gpg' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/dm.gpg' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/dm.txt' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/pubring.gpg' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/random_seed' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/secring.gpg' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/trustdb.gpg' for reading: Permission denied cp: cannot open '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/dgit-test-global-lock' for reading: Permission denied cp: cannot access '/tmp/autopkgtest-lxc.jx44mw5k/downtmp/gitworktree-artifacts/gnupg/private-keys-v1.d': Permission denied tar: ./example/.git: Cannot open: File exists tar: Exiting with failure status due to previous errors : failure: copyup destination failed, status 2 autopkgtest [20:02:12]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe I think this is probably a bug in the lxc virt provider but I'm not sure. The failure occurs with the test suite from dgit 5.9+exp1, which copies some non-world-readable files into $AUTOPKGTEST_ARTIFACTS. I will add an appropriate chmod a+r. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#903165: On boot squid.service starts but doesn't work
I've CCed NetworkManager maintainers: since here /etc/resolv.conf is a symlink created by NetworkManager, perhaps they can provide some advice. Regarding the opening message, I've workarounded the problem overriding the squid service like this: # systemctl edit squid.service --- [Unit] After=network-online.target --- But that didn't work with my PC at work (see message #30), for which the override had no effect. Perhaps there the problem has different origin: I have to investigate better on this. Cesare.
Bug#903679: /build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm]
Package: src:linux Version: 4.16.16-2 Severity: important Problem occurs with vmlinuz-4.16.0-2-amd64 No problem in vmlinuz-4.15.0-3-amd64 Problem occurs if user puts xrandr --output LVDS-1 --mode 1024x576 in his ~/.xsession file. Problem doesn't occur if user just invokes xrandr --output LVDS-1 --mode 1024x576 from the command line in an xterm. Problem is vblank wait timed out on crtc 0 [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:37:pipe A] flip_done timed out WARNING: CPU: 0 PID: 671 at /build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm] Using video=SVIDEO-1:d doesn't help. Anyway the computer must be rebooted and the line taken out of .xsession to be usable. vblank wait timed out on crtc 0 WARNING: CPU: 1 PID: 671 at /build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wa Modules linked in: arc4 brcmsmac intel_rapl cordic brcmutil x86_pkg_temp_thermal b43 intel_powerclamp cm irqbypass btintel bluetooth crct10dif_pclmul crc32_pclmul drbg ghash_clmulni_intel cfg80211 ssb pc tel_cstate iTCO_wdt videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 ecdh_generic videobuf2_common i b_ms media memstick intel_rapl_perf snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic j nd_hwdep snd_pcm ideapad_laptop i915 snd_timer pcspkr mei_me mei evdev serio_raw snd sg drm_kms_helpe lpc_ich video ac drm button battery i2c_algo_bit ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd gl _usb_sdmmc mmc_core rtsx_usb sr_mod cdrom sd_mod uas usb_storage ahci libahci crc32c_intel psmouse i2 d xhci_hcd alx mdio usbcore usb_common thermal CPU: 1 PID: 671 Comm: Xorg Tainted: GW4.16.0-1-amd64 #1 Debian 4.16.5-1 Hardware name: LENOVO 20150/Product Name, BIOS 5ECN40WW(V3.06) 10/22/2012 RIP: 0010:drm_wait_one_vblank+0x16e/0x180 [drm] RSP: 0018:a86701313800 EFLAGS: 00010286 RAX: RBX: 91aa25a5 RCX: RDX: RSI: 0002 RDI: 0202 RBP: R08: R09: 001f R10: a867013136b8 R11: R12: R13: 337f R14: 91aa20b8c808 R15: 91aa25a5 FS: 7fbd8b29da40() GS:91aa2f24() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55d2787f99cc CR3: 0001a4450001 CR4: 000606e0 Call Trace: ? finish_wait+0x80/0x80 ironlake_crtc_enable+0x4bb/0xcd0 [i915] intel_update_crtc+0x39/0x90 [i915] intel_update_crtcs+0x47/0x60 [i915] intel_atomic_commit_tail+0x1dd/0xd30 [i915] intel_atomic_commit+0x21f/0x2d0 [i915] restore_fbdev_mode_atomic+0x1ac/0x210 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x45/0x90 [drm_kms_helper] drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper] intel_fbdev_set_par+0x16/0x60 [i915] ? __update_load_avg_se.isra.35+0x1b6/0x1c0 fb_set_var+0x179/0x3e0 ? update_load_avg+0x563/0x6c0 ? __cgroup_account_cputime+0x24/0x30 ? account_entity_enqueue+0xc5/0xf0 ? __update_load_avg_se.isra.35+0x1b6/0x1c0 ? __update_load_avg_se.isra.35+0x1b6/0x1c0 fbcon_blank+0x26f/0x320 do_unblank_screen+0xb3/0x1a0 complete_change_console+0x54/0xd0 vt_ioctl+0x695/0x1120 ? _copy_to_user+0x22/0x30 ? drm_ioctl+0x2ee/0x380 [drm] tty_ioctl+0xef/0x890 ? __handle_mm_fault+0xa27/0x1220 do_vfs_ioctl+0xa4/0x630 ? handle_mm_fault+0xdc/0x210 SyS_ioctl+0x74/0x80 do_syscall_64+0x6c/0x130 entry_SYSCALL_64_after_hwframe+0x3d/0xa2 RIP: 0033:0x7fbd8c79c097 RSP: 002b:7ffce45db298 EFLAGS: 3246 ORIG_RAX: 0010 RAX: ffda RBX: 55ccf3743650 RCX: 7fbd8c79c097 RDX: 0001 RSI: 5605 RDI: 000d RBP: 55ccf374358c R08: R09: 0001 R10: 0093 R11: 3246 R12: 0001 R13: 0008 R14: 55ccf3743640 R15: 55ccf3743588 Code: 2d ff ff ff e8 d4 b7 b6 ec 48 89 e6 4c 89 f7 e8 99 f3 ba ec 45 85 e4 0f 85 0a ff ff ff 89 ee 48 c7 c7 58 aa 52 c0 e8 22 b5 b6 ec <0f> 0b e9 f5 fe ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 66 66 66
Bug#903678: resize vs. xrandr
Package: xterm Version: 333-1 Severity: wishlist File: /usr/share/man/man1/resize.1.gz Man resize does not mention what to do in the case one does in a running xterm: $ seq 222 $ xrandr --output LVDS-1 --mode 1024x576 $ # mention the correct resize recipe here, so that $ seq 222 # will show 222 at the bottom of the screen too, just like the first time, even thought now there are less rows.
Bug#903677: RFS: wolfssl/3.15.3+dfsg-1 [RC] [NEW] -- wolfSSL encryption library
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "wolfssl" Package name: wolfssl Version : 3.15.3+dfsg-1 Upstream Author : wolfSSL Inc. URL : https://www.wolfssl.com/products/wolfssl/ License : GPL-2+ and others Section : libs * This shared library release has a new major number, and will require a trip through the NEW queue. It builds those binary packages: libwolfssl18 - wolfSSL encryption library libwolfssl-dev - Development files for the wolfSSL encryption library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wolfssl Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wolfssl/wolfssl_3.15.3+dfsg-1.dsc Changes since the last upload: * New upstream release * Fixes "return of the hidden number problem" CVE-2018-12436 (Closes: #901627) * Major number is now 18 * Updated shared object symbols * Debug symbol migration complete; code deleted * Shipping examples for C library * Removed doxygen-generated files from source tarball * Removed non-existing 'm4/wolfssl_darwin_clang.m4' from copyright * Updated upstream home page in control * Switched to secure URI for copyright format * Fixed spelling in patch header * Set Standards-Version: 4.1.5 * Set compat to 11 * Set Build-Depends: debhelper (>= 11) Regards, Felix Lechner
Bug#903303: Acknowledgement (fireqos: Fireqos fails to start on boot)
First, to the bug report context I add that my network is managed by NetworkManager and I use a wifi network (so slower to come up than a cable network). Since on one occasion the service started ok on boot, with my basic systemd knowledge I analyzed the fireqos.service and I think the problem is the lack of something that tells the service to start only after some conditions are met. I don't know exactly what are those conditions but at least the networks to which fireqos rules are referred should be up. I've experimented that overriding the fireqos service (systemctl edit fireqos.service) with the following lines, worked for me: --- [Unit] After=network-online.target --- I'm sure it's suboptimal, but I tried "After=network.target" and it didn't suffice. Cesare.
Bug#903676: patch
Attached is a simple dep8 smoketest, which basically makes sure that ipmitool doesn't e.g. segfault on startup. diff -urpN ipmitool-1.8.18.orig/debian/tests/control ipmitool-1.8.18/debian/tests/control --- ipmitool-1.8.18.orig/debian/tests/control 1969-12-31 17:00:00.0 -0700 +++ ipmitool-1.8.18/debian/tests/control 2018-07-12 14:45:27.460597784 -0600 @@ -0,0 +1,3 @@ +# smoke test +Test-Command: ipmitool -V +Depends: ipmitool
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Andrey Rahmatullin wrote: On Thu, Jul 12, 2018 at 10:16:36AM -0500, Kent West wrote: > > ... once I learned that the fix had been uploaded to stable, > To unstable (the only place where it was broken). D'oh! I mean "unstable". > But if I'm understanding this error, for some months (years?), I've been > > pulling VirtualBox from virtualbox.org > No, the extension pack can be installed on the Debian Virtualbox > separately and I don't think it's installed by default even with the > official package. > > instead of from Debian, and whilst > > doing that, had configured my VMs with USB support. And my fix should > just > > be to disable the USB support in my VMs > The fix should be to upgrade the extension pack after you upgraded > virtualbox itself... Good to know. Thanks! -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Bug#903676: add a dep8 smoketest
Package: ipmitool Version: 1.8.18-5+b1 Severity: minor Tags: patch Please add dep8 testing. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ipmitool depends on: ii libc6 2.27-4 ii libfreeipmi17 1.5.7-2 ii libncurses66.1+20180210-4 ii libreadline7 7.0-5 ii libssl1.1 1.1.0h-4 ii libtinfo6 6.1+20180210-4 ii lsb-base 9.20170808 Versions of packages ipmitool recommends: ii openipmi 2.0.25-2 ipmitool suggests no packages. -- debconf-show failed
Bug#903627: ocrmypdf: contains workaround for old version of python3-ruffus which should not be used with current python3-ruffus
I backported the fixes related to python3-ruffus 2.7, python 3.7 support, and a few other minor changes from 7.0.0. I released it just now as 6.2.2, so that should take care of it. Let me know if there are any further issues. On Thu, 12 Jul 2018 at 01:03 Sean Whitton wrote: > Package: ocrmypdf > Version: 6.2.0-1 > Severity: serious > Tags: ftbfs > X-debbugs-cc: j...@purplerock.ca > > OCRmyPDF contains a workaround for a bug in python3-ruffus <=2.6.3 that > upstream reports should not be used with python3-ruffus >=2.7 (see > changelog entry for 4.1.2-1 upload). > > python3-ruffus 2.7 was just uploaded to Debian, so ocrmypdf is now > buggy, and indeed unbuildable. > > The current upstream release of OCRmyPDF, 7.0.0, will not be reaching > Debian unstable for some time: a new dependency, pikepdf, will target > experimental. So ideally we would patch the workaround out of OCRmyPDF > 6.2.0. CCing upstream to request advice on how to do this. > > -- > Sean Whitton >
Bug#885812: pk-update-icon: Depends on libunique
On Fri, 29 Dec 2017 21:32:30 -0500 Jeremy Bicha wrote: > As announced [1], we do not intend to release Debian 10 "Buster" with > the old libgnome (and related) libraries. These libraries have been > deprecated and unmaintained for several years. > > Your package depends and or build-depends on libunique. > > Please port your package to GTK3 and related maintained libraries. > Otherwise, please consider requesting that your package be removed from > Debian to help us complete this goal. > > [1] https://lists.debian.org/debian-devel/2017/10/msg00299.html pk-update-icon is no longer under development, however I've written a (much improved) replacement called package-update-indicator[1] which is based on GTK3 and newer glib. It just needs to be packaged for Debian. (I am the upstream author of both projects.) [1] https://code.guido-berhoerster.org/projects/package-update-indicator/ -- Guido Berhoerster
Bug#903669: lintian -- false positive on using-first-person-in-description
Hi Chris, On Thu, 12 Jul 2018, Chris Lamb wrote: The description of pyicloud contains the name of a software called "Find My iPhone". I think this is a case for an override rather than a change in Lintian as it will never be able to reliably know that this is a false positive without aintaining a list of project names like "Find My iPhone." aren't there lists for other lintian tags as well? For example where Rouge is the correct spelling that should not be replaced by Rogue, as mentioned in #891794? What do you think? I am always happy to see no output from lintian, so I would slightly prefer the solution with a list. But I also don't mind to add an override. It is your call :-). Thorsten
Bug#898725: Patch for "FTBFS when built with dpkg-buildpackage -A"
Hi, I have attached a patch which fixes building with "dpkg-buildpackage -A". Best regards, Ruben commit 30d8612136cc132d5134e8b6c51123bf14efd6d8 Author: Ruben Undheim Date: Thu Jul 12 20:00:09 2018 + Patch for dpkg-buildpackage -A build failure diff --git a/debian/changelog b/debian/changelog index 9834f0d..105a86b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +flex (2.6.4-6.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * debian/rules: +- Fix build with "dpkg-buildpackage -A" by checking if directory exists + first (Closes: #898725) + + -- Ruben Undheim Thu, 12 Jul 2018 20:02:32 + + flex (2.6.4-6.1) unstable; urgency=medium * Non-maintainer upload. diff --git a/debian/rules b/debian/rules index e676497..f8ee94e 100755 --- a/debian/rules +++ b/debian/rules @@ -73,7 +73,9 @@ override_dh_install: rm -f debian/flex/usr/share/doc/flex/flex.pdf test ! -f debian/flex/usr/share/doc/flex/COPYING || \ rm -f debian/flex/usr/share/doc/flex/COPYING - find debian/flex/usr/share/locale -type d -empty -delete + if [ -d debian/flex/usr/share/locale ] ; then \ + find debian/flex/usr/share/locale -type d -empty -delete ; \ + fi dh_link
Bug#903675: hyperscan/5.0.0-1 appears to break suricata/1:4.0.4-1 autopktest: suricata fails to install
Source: hyperscan, suricata Version: hyperscan/5.0.0-1 Version: suricata/1:4.0.4-1 User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of hyperscan the autopkgtest of suricata started to fail in unstable and testing. I have copied the error below. The new version of hyperscan prevents suricata to be installed. Currently this regression is delaying the migration of hyperscan to testing by 13 days. Could you please investigate the situation and determine which package needs to fix something, and assign appropriately? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/s/suricata/594512/log.gz Setting up suricata (1:4.0.4-1) ... Job for suricata.service failed because the control process exited with error code. See "systemctl status suricata.service" and "journalctl -xe" for details. invoke-rc.d: initscript suricata, action "start" failed. ● suricata.service - Suricata IDS/IDP daemon Loaded: loaded (/lib/systemd/system/suricata.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2018-07-12 04:39:04 UTC; 6ms ago Docs: man:suricata(8) man:suricatasc(8) https://suricata-ids.org/docs/ Process: 3273 ExecStart=/usr/bin/suricata -D --af-packet -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid (code=exited, status=127) dpkg: error processing package suricata (--configure): installed suricata package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on suricata; however: Package suricata is not configured yet. dpkg: error processing package autopkgtest-satdep (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of suricata-oinkmaster: suricata-oinkmaster depends on suricata (>= 1:4.0.4-1); however: Package suricata is not configured yet. dpkg: error processing package suricata-oinkmaster (--configure): dependency problems - leaving unconfigured signature.asc Description: OpenPGP digital signature
Bug#903671: autopkgtest excuses in tracker should also link to the packages
On Thu, Jul 12, 2018 at 09:11:19PM +0200, Paul Gevers wrote: > Hi Adrian, Hi Paul, > On 12-07-18 20:48, Adrian Bunk wrote: > > Example: > > https://tracker.debian.org/pkg/python3-defaults > > > > Lines like: > > autopkgtest for aodh/6.0.0-7: amd64: Regression ♻ > > > > The "amd64" and "Regression" are already links (to ci.debian.org). > > > > It would be useful if the package name "aodh" would also become > > a link pointing at https://tracker.debian.org/pkg/aodh since > > this is the central place for finding related information like > > bugs or buildd logs. > > I like the idea, but there are more consumers of the excuses. So what > makes tracker special? The links for ci.debian.net (Not ci.debian.org) > are justified because that is where the tests run. >... what makes tracker special is that it is the place for getting all information about a package on one page. > Paul cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#903674: mailman: CVE-2018-13796: (yet) unspecified vulnerability in mailman
Source: mailman Version: 1:2.1.23-1 Severity: important Tags: security upstream Hi, The following vulnerability was published for mailman, details are not yet published. The 2.1.28 release along with details will be on 23th July 2018. CVE-2018-13796[0]: | Unspecified vulnerability in Mailman before 2.1.28 has unknown impact | and attack vectors. 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-13796 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13796 [1] https://mail.python.org/pipermail/mailman-users/2018-July/083536.html [2] https://mail.python.org/pipermail/mailman-users/2018-July/083537.html Regards, Salvatore
Bug#903672: r-cran-etm: autopkgtest regression
Source: r-cran-etm Version: 1.0.3-1 User: debian...@lists.debian.org Usertags: regression Hi R Package Team Since the upload of 1.0.3-1, r-cran-etm has been failing its own autopkgtest [1] with the following error: +Error: The following tests require the 'kmi' package +In addition: Warning message: +In library(package, lib.loc = lib.loc, character.only = TRUE, logical.return = TRUE, : + there is no package called 'kmi' +Execution halted autopkgtest [04:46:42]: test run-unit-test: ---] autopkgtest [04:46:42]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1 Regards Graham [1] https://ci.debian.net/packages/r/r-cran-etm/unstable/amd64/
Bug#903673: sddm-theme-breeze: selected background image ignored
Package: sddm-theme-breeze Version: 4:5.13.2-1 Severity: normal Dear Maintainer, the control for the sddm-theme-breeze allows to specify a background image. I specified an image. But it is ignored when the system is restarted. Best regards Heinrich Schuchardt -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armhf Kernel: Linux 4.16.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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sddm-theme-breeze depends on: ii plasma-framework 5.47.0-1 ii plasma-workspace 4:5.13.2-1 Versions of packages sddm-theme-breeze recommends: ii sddm 0.17.0-1 sddm-theme-breeze suggests no packages. -- no debconf information
Bug#903671: autopkgtest excuses in tracker should also link to the packages
Hi Adrian, On 12-07-18 20:48, Adrian Bunk wrote: > Example: > https://tracker.debian.org/pkg/python3-defaults > > Lines like: > autopkgtest for aodh/6.0.0-7: amd64: Regression ♻ > > The "amd64" and "Regression" are already links (to ci.debian.org). > > It would be useful if the package name "aodh" would also become > a link pointing at https://tracker.debian.org/pkg/aodh since > this is the central place for finding related information like > bugs or buildd logs. I like the idea, but there are more consumers of the excuses. So what makes tracker special? The links for ci.debian.net (Not ci.debian.org) are justified because that is where the tests run. RT, what do you think? Paul signature.asc Description: OpenPGP digital signature
Bug#903669: lintian -- false positive on using-first-person-in-description
tags 903669 + moreinfo thanks Hi Thorsten, > The description of pyicloud contains the name of a software called "Find > My iPhone". I think this is a case for an override rather than a change in Lintian as it will never be able to reliably know that this is a false positive without aintaining a list of project names like "Find My iPhone." What do you think? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#903671: autopkgtest excuses in tracker should also link to the packages
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: britney Example: https://tracker.debian.org/pkg/python3-defaults Lines like: autopkgtest for aodh/6.0.0-7: amd64: Regression ♻ The "amd64" and "Regression" are already links (to ci.debian.org). It would be useful if the package name "aodh" would also become a link pointing at https://tracker.debian.org/pkg/aodh since this is the central place for finding related information like bugs or buildd logs.
Bug#903625: ITP: pikepdf -- python library for reading and writing PDFs, powered by qpdf
Thanks for making me aware of this. I didn't know about pikepdf. That's really exciting -- I've always wanted to be able to use qpdf from Python. I will contact pikepdf's author. On Thu, Jul 12, 2018 at 3:18 AM Sean Whitton wrote: > Package: wnpp > Severity: wishlist > Owner: Sean Whitton > > * Package name: pikepdf > Version : 0.2.2 > Upstream Author : James R. Barlow > * URL : https://github.com/pikepdf/pikepdf > * License : MPL-2.0 > Programming Lang: Python & C++ > Description : python library for reading and writing PDFs, powered > by qpdf > > This is a new dependency of the latest upstream release of OCRmyPDF. > > I intend to maintain it under the Debian Python Modules Team umbrella. > > After discussion with upstream, I plan to upload to experimental, > because the library's API is not yet stable. Upstream expects it to > have stabilised in time to upload to unstable in time for the buster > freeze. > > -- > Sean Whitton >
Bug#903641: initramfs-tools-core: 'keymap' scripts don't preserve numlock state
Control: severity -1 wishlist Control: reassign -1 initramfs-tools-core Control: retitle -1 initramfs-tools-core: 'keymap' scripts don't preserve numlock state On Thu, 12 Jul 2018 at 19:46:02 +0200, Pascal Vibet - ADACIS wrote: > Le 12/07/2018 à 15:48, Guilhem Moulin a écrit : >> Why only in cryptopensc and not in cryptroot? Also /usr/bin/setleds >> comes from the ‘kbd’ package which cryptsetup-initramfs doesn't depend >> on (it's only a Recommends, not a hard Depends), so `copy_exec` needs to >> wrapped to check for the program's existence. > > Because i don't test with cryptroot. You are, it's the hook that copies the cryptsetup binaries to the initramfs… And /scripts/local-top/cryptroot is run whenever you have encrypted devices that need to be unlocked at initramfs stage (whether or not some of these devices are using ‘keyscript=decrypt_opensct’). > For package depends or Recommends, the > /usr/share/initramfs-tools/hooks/cryptopensc script need > 'dpkg-architecture' program to work and it is in 'dpkg-dev' package||. No need, it's enough to check whether ‘/usr/bin/setleds’ exists, like we're doing for ‘/usr/bin/gpg’ and some other binaries. That being said I don't think restoring the numlock state is the job of cryptsetup's initramfs hook & boot scripts, just like it's not its job to install the right keyboard layout. I'm therefore reassigning this to ‘initramfs-tools-core’, which is the package shipping the keymap hook. > But you are right, 'setleds' is not the goods choice to keep numlock state. > I will search a better program. An option would be to store the state when generating the initramfs image, but that doesn't seem to be exactly what you want. With full disk encryption I don't know where else to store the state at shutdown stage. -- Guilhem. signature.asc Description: PGP signature
Bug#903670: RFS: pius/2.2.6-1 -- Tools to help before and after key-signing parties
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pius" Package name: pius Version : 2.2.6-1 Upstream Author : Phil Dibowitz URL : http://www.phildev.net/pius/ License : GPL-2 Section : utils It builds those binary packages: pius - Tools to help before and after key-signing parties To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pius Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pius/pius_2.2.6-1.dsc Changes since the last upload: * New upstream release (Closes: #873741) * Set Build-Depends: and Depends: to python3 and friends (Closes: #902328) * Removed X-Python-Version: * Set Depends: gnupg (>= 2) (Closes: #864431) * Switched to upstream manpages (submitted from Debian) * Set Vcs-Browser: https://salsa.debian.org/lechner-guest/pius * Set Vcs-Git: https://salsa.debian.org/lechner-guest/pius.git * Switched to secure URI in copyright * Set Priority: optional (from extra) * Set Build-Depends: debhelper (>= 11) * Set compat to 11 * Set Standards-Version: 4.1.5 Regards, Felix Lechner
Bug#903669: lintian -- false positive on using-first-person-in-description
Package: lintian Version: 2.5.84 Severity: normal The description of pyicloud contains the name of a software called "Find My iPhone". So in this case "My" is not a using-first-person-in-description ... Thorsten
Bug#903668: RFS: enchive/3.4-3 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "enchive" * Package name: enchive Version : 3.4-3 Upstream Author : Christopher Wellons * URL : https://github.com/skeeto/enchive * License : Unlicense Section : utils It builds those binary packages: enchive- long-term archive encryption tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/enchive Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/e/enchive/enchive_3.4-3.dsc Or from Salsa using this command: gbp clone https://salsa.debian.org/zebmccorkle-guest/enchive.git More information about hello can be obtained from https://github.com/skeeto/enchive and https://nullprogram.com/blog/2017/03/12/. -- Zebulon McCorkle zebmccor...@asymptote.club | https://keybase.io/zebMcCorkle 803A 0F47 82AD DDEA 46BE 055F F8F9 DB8C 1A54 6398 | | __/ __ Asymptote Club /(bad ASCII graph by yours truly) | | signature.asc Description: PGP signature
Bug#903664: An assertion failed on Amule
> I pressed the download botton and I got an error message: > ASSERT INFO: > ../src/unix/sockunix.cpp(143): assert "m_fd != INVALID_SOCKET" failed in > OnReadWaiting(): invalid socket ready for reading? > > BACKTRACE: > [1] wxOnAssert(char const*, int, char const*, char const*, char const*) > [2] g_main_context_dispatch > [3] g_main_loop_run > [4] gtk_main > [5] wxGUIEventLoop::DoRun() > [6] wxEventLoopBase::Run() > [7] wxAppConsoleBase::MainLoop() > [8] wxEntry(int&, wchar_t**) > [9] __libc_start_main please follow https://salsa.debian.org/debian/amule/blob/master/debian/bug-presubj and report the information as requested, as-is the report is not helpful to understand what caused it - thanks! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#903667: [clawsker] Silently aborts on startup
Package: clawsker Version: 1.1.1-1 Severity: normal Tags: patch Clawsker silently aborts on start up when called from KDE's application menu. When started from command line the following is printed to console before quitting; The encoding pragma is no longer supported at /usr/local/bin/clawsker line 7. BEGIN failed--compilation aborted at /usr/local/bin/clawsker line 7. Error is simple to correct (found by internet search) Replace use encoding 'utf8'; with use utf8; at line 7 of clawsker I've applied the change and clawsker now works as expected here. --- System information. --- Architecture: Kernel: Linux 4.16.0-2-amd64 Debian Release: buster/sid 500 testing www.deb-multimedia.org 500 testing deb.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== perl:any | libgtk2-perl (>= 1.140) | 2:1.24992-1+b1 liblocale-gettext-perl (>= 1.05) | 1.07-3+b3 Recommends (Version) | Installed =-+-=== claws-mail| Package's Suggests field is empty. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Who's a sucker now? Edward The Bear - The Damned
Bug#903666: cod-tools: missing dependencies
Source: cod-tools Control: found -1 2.2+dfsg-1 Control: owner -1 ! Hello, cod-tools depends on libdate-calc-perl, what is obvious from autopkgtest log [1]. By the way, failed autopkgtest is not recognized as failed. From build logs [2] is evident that some b-depends are also missing. However, these b-dependencies are not essential, only required for after build tests. Best, Andrius [1] https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cod-tools/596842/log.gz [2] for example https://buildd.debian.org/status/fetch.php?pkg=cod-tools=arm64=2.2%2Bdfsg-1=1531408717=0
Bug#894476: #894476: Solved from the Qt side. (rcc: please honour SOURCE_DATE_EPOCH)
On Wednesday, July 11, 2018 10:08:23 PM CEST Vagrant Cascadian wrote: > Ideally QT_RCC_SOURCE_DATE_OVERRIDE would get set based on > SOURCE_DATE_EPOCH, otherwise build tools have an arbitrary growing No. As explained, we need to look at each individual package to check if the timestamp is actually used for anything. It can be. It probably is. I think a better fix might be to specifically mark in the rcc file if the dates are important or not. But it requires involvement upstream. (Or maybe if the rcc file is autogenerated or not). I don't think it is a problem for non- autogenerated rcc files. /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth
Hi, Le 12/07/2018 à 15:48, Guilhem Moulin a écrit : Why only in cryptopensc and not in cryptroot? Also /usr/bin/setleds comes from the ‘kbd’ package which cryptsetup-initramfs doesn't depend on (it's only a Recommends, not a hard Depends), so `copy_exec` needs to wrapped to check for the program's existence. Because i don't test with cryptroot. For package depends or Recommends, the /usr/share/initramfs-tools/hooks/cryptopensc script need 'dpkg-architecture' program to work and it is in 'dpkg-dev' package||. But you are right, 'setleds' is not the goods choice to keep numlock state. I will search a better program. Regards Le 12/07/2018 à 15:48, Guilhem Moulin a écrit : Control: severity -1 minor Hi, On Thu, 12 Jul 2018 at 15:02:20 +0200, Pascal Vibet - ADACIS wrote: So, i apply modifications like this: in /usr/share/initramfs-tools/hooks/cryptopensc: […] in /usr/share/initramfs-tools/scripts/local-top/cryptopensc: Why only in cryptopensc and not in cryptroot? Also /usr/bin/setleds comes from the ‘kbd’ package which cryptsetup-initramfs doesn't depend on (it's only a Recommends, not a hard Depends), so `copy_exec` needs to wrapped to check for the program's existence. INITTY=/dev/tty[1-8] for tty in $INITTY ; do setleds -D +num < $tty done Does that really *preserve* the numlock state? I'm not familiar with setleds(1), but according to the manpage it *sets* numlock and changes the default settings. Cheers,
Bug#903665: boost1.62: bali-phy FTBFS on ppc64*
Package: src:boost1.62 Version: 1.62.0+dfsg-6 Severity: normal Tags: patch pending Dear maintainer, I see that bali-phy 3.2+dfsg-1 fails to build on ppc64* architectures : https://buildd.debian.org/status/fetch.php?pkg=bali-phy=ppc64el=3.2%2Bdfsg-1=1530003294=0 I saw this recent bug opened upstream boost that include a fix submitted to boost people and that seems to make bali-phy compile : https://svn.boost.org/trac10/ticket/13531#no2 Regards. F. pgppeUnWyEYwc.pgp Description: PGP signature pgp4W0NfV71w2.pgp Description: PGP signature
Bug#903664: An assertion failed on Amule
Package: amule Version: 1:2.3.2-1+b2 Severity: minor Dear Maintainer, I pressed the download botton and I got an error message: ASSERT INFO: ../src/unix/sockunix.cpp(143): assert "m_fd != INVALID_SOCKET" failed in OnReadWaiting(): invalid socket ready for reading? BACKTRACE: [1] wxOnAssert(char const*, int, char const*, char const*, char const*) [2] g_main_context_dispatch [3] g_main_loop_run [4] gtk_main [5] wxGUIEventLoop::DoRun() [6] wxEventLoopBase::Run() [7] wxAppConsoleBase::MainLoop() [8] wxEntry(int&, wchar_t**) [9] __libc_start_main -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages amule depends on: ii amule-common 1:2.3.2-1 ii libboost-system1.62.0 1.62.0+dfsg-4 ii libc6 2.24-11+deb9u3 ii libcrypto++6 5.6.4-7 ii libgcc11:6.3.0-18+deb9u1 ii libgeoip1 1.6.9-4 ii libstdc++6 6.3.0-18+deb9u1 ii libupnp6 1:1.6.19+git20160116-1.2 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii libwxgtk3.0-0v53.0.2+dfsg-4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages amule recommends: ii amule-utils 1:2.3.2-1+b2 ii unzip6.0-21 Versions of packages amule suggests: pn amule-utils-gui -- no debconf information
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
On Thursday, July 12 2018, Mario Frasca wrote: > I've not been able to satisfy all packaging requirements, and gave up. > > so I wish to close this issue, there is no candidate package any more. You can send an e-mail to 898773-cl...@bugs.debian.org. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#894476: #894476: Solved from the Qt side. (rcc: please honour SOURCE_DATE_EPOCH)
> That's sadly something we can only "fix" by making packages have the right
> value set. As per Qt policy the environment variable needs to be prefixed
> with QT, so no chance of directly using SOURCE_DATE_EPOCH.
I added a downstream patch to a test-version [1] in openSUSE with
+static const quint64 sourceDate2 = 1000 *
qgetenv("SOURCE_DATE_EPOCH").toULongLong();
+if (sourceDate2 != 0)
+lastmod = sourceDate2;
but somehow this did not help (e.g. with bitcoin's
bitcoin-0.16.1/src/qt/qrc_bitcoin_locale.cpp going into the bitcoin-qt
binary).
So maybe the patch is not the correct solution... or there are more
similar issues somewhere else in rcc.
[1]
https://build.opensuse.org/package/view_file/home:bmwiedemann:reproducible:test/libqt5-qtbase/reproducibletime.patch
Bug#903663: python3-numpy: Should not depend on python3.7
Package: python3-numpy Version: 1:1.14.5-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Since python3.7 is currently uninstallable, packages should not depend on it. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#903662: nfs-ganesha-config.service ExecStart points to incorrect path
Package: nfs-ganesha Version: 2.6.0-2~bpo9+1 Severity: normal Dear Maintainer, After installing this package I noticed it failed to start with the following error in /var/syslog: nfs-ganesha-config.service: Failed at step EXEC spawning /usr/lib/ganesha/nfs-ganesha-config.sh: No such file or directory The package places this file at /usr/lib/nfs-ganesha-config.sh, which does not match the ExecStart location (/usr/lib/ganesha/nfs-ganesha-config.sh) in the included systemd service file. After pointing ExecStart to /usr/lib/nfs-ganesha-config.sh, nfs-ganesha starts without issues. Thanks, -Steve -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-ganesha depends on: ii daemon 0.6.4-1+b2 ii dbus 1.10.26-0+deb9u1 ii init-system-helpers 1.48 ii libblkid12.29.2-1+deb9u1 ii libc62.24-11+deb9u3 ii libcap2 1:2.25-1 ii libcomerr2 1.43.4-2 ii libdbus-1-3 1.10.26-0+deb9u1 ii libgssapi-krb5-2 1.15-1+deb9u1 ii libk5crypto3 1.15-1+deb9u1 ii libkrb5-31.15-1+deb9u1 ii libnfsidmap2 0.25-5.1 ii libntirpc1.6 1.6.1-1~bpo9+1 ii libuuid1 2.29.2-1+deb9u1 ii libwbclient0 2:4.5.12+dfsg-2+deb9u2 ii nfs-common 1:1.3.4-2.1 ii rpcbind 0.2.3-0.6 Versions of packages nfs-ganesha recommends: pn nfs-ganesha-ceph pn nfs-ganesha-gluster pn nfs-ganesha-gpfs pn nfs-ganesha-mem pn nfs-ganesha-mount-9p pn nfs-ganesha-nullfs pn nfs-ganesha-proxy ii nfs-ganesha-vfs 2.6.0-2~bpo9+1 pn nfs-ganesha-xfs nfs-ganesha suggests no packages. -- Configuration Files: /etc/ganesha/ganesha.conf changed [not included] -- no debconf information
Bug#903661: [cfdisk]: Assertion `end > start' failed. Aborted
Package: util-linux Version: 2.29.2-1+deb9u1 Severity: normal Dear Maintainer, when trying to use cfdisk to view the partitions on a USB thumb drive with an image of a ChromeOS recovery disk on it ( specifically chromeos_10176.76.0_terra_recovery_stable-channel_mp-v2.bin ) instead of cfdisk running, cfdisk merely prints out cfdisk: libfdisk/src/table.c:409: new_freespace: Assertion `end > start' failed. Aborted and does not run any further. fdisk can load this disk - fdisk /dev/sdb , p gives: Disk /dev/sdb: 3.8 GiB, 4048551936 bytes, 7907328 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: FADF1998-E292-1A43-975C-0BF190FDC25F Device Start End Sectors Size Type /dev/sdb1 4415488 4435967 20480 10M Microsoft basic data /dev/sdb220480 53247 32768 16M ChromeOS kernel /dev/sdb3 319488 4415487 40960002G ChromeOS root fs /dev/sdb453248 86015 32768 16M ChromeOS kernel /dev/sdb5 315392 31948740962M ChromeOS root fs /dev/sdb616448 16448 1 512B ChromeOS kernel /dev/sdb716449 16449 1 512B ChromeOS root fs /dev/sdb886016 118783 32768 16M Microsoft basic data /dev/sdb916450 16450 1 512B ChromeOS reserved /dev/sdb10 16451 16451 1 512B ChromeOS reserved /dev/sdb11 64 16447 163848M unknown /dev/sdb12 249856 315391 65536 32M EFI System Partition table entries are not in disk order. Command (m for help): lsusb gives Bus 005 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive While it's plausible that ChromeOS has made some kind of mangled filesystem, or even that the disk itself has bad sectors(??) ...in both cases cfdisk should behave differently 1) if the disk is bad, it should say as much 2) if it's ChromeOS's filesystem which is not written properly, it should load a screen much like fdisk does anyway, or present the option to do something about the situation(format?) -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages util-linux depends on: ii libblkid1 2.29.2-1+deb9u1 ii libc6 2.24-11+deb9u3 ii libfdisk1 2.29.2-1+deb9u1 ii libmount1 2.29.2-1+deb9u1 ii libncursesw5 6.0+20161126-1+deb9u2 ii libpam0g 1.1.8-3.6 ii libselinux12.6-3+b3 ii libsmartcols1 2.29.2-1+deb9u1 ii libsystemd0232-25+deb9u3 ii libtinfo5 6.0+20161126-1+deb9u2 ii libudev1 232-25+deb9u3 ii libuuid1 2.29.2-1+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 util-linux recommends no packages. Versions of packages util-linux suggests: pn dosfstools ii kbd 2.0.3-2+b1 ii util-linux-locales 2.29.2-1+deb9u1 -- no debconf information
Bug#903660: ITP: enchive -- long-term archive encryption tool
Package: wnpp Severity: wishlist Owner: zebmccorkle * Package name: enchive Version : 3.4 Upstream Author : Christopher Wellons * URL : https://github.com/skeeto/enchive * License : Unlicense Programming Lang: C Description : long-term archive encryption tool Enchive is a tool to encrypt files to yourself for long-term archival. It's a focused, simple alternative to more complex solutions such as GnuPG or encrypted filesystems. Files are secured with ChaCha20, Curve25519, and HMAC-SHA256. I will need a sponsor to upload this package. Will be uploaded to mentors and Salsa when I get my ITP number.
Bug#903656: stretch-pu: package publicsuffix/20180523.2326-0+deb9u1
On Thu 2018-07-12 11:25:58 -0400, d...@fifthhorseman.net wrote: > Package: release.debian.org > Severity: normal > Tags: stretch > User: release.debian@packages.debian.org > Usertags: pu > Control: affects -1 publicsuffix > > Please consider an update to publicsuffix in debian stretch. > > This package reflects the state of the network, and keeping it current > is useful for all the packages that depend on it. > > The debdiff from the previous version in stretch is not attached because it > was being rejected as spam. > > This proposed release is also available at the > "publicsuffix_debian/20180523.2326-0+deb9u1" tag on the "debian/stretch" > branch at > the git repo for publicsuffix packaging: > > https://salsa.debian.org/debian/publicsuffix > > Please followup on this ticket to confirm whether I should upload this > revision to stretch. I've tried multiple times now to attach the debdiff to this bug report, and it continues to be rejected as spam by bugs.debian.org with this message: <903...@bugs.debian.org>: host buxtehude.debian.org[209.87.16.39] said: 550 malware detected: Sanesecurity.Jurlbl.db3039.UNOFFICIAL: message rejected (in reply to end of DATA command) Since that's failing, i'll just post it publicly on the web. You can retrieve the debdiff at: https://dkg.fifthhorseman.net/publicsuffix_20180218.2049-0+deb9u1_20180523.2326-0+deb9u1.debdiff.gz It has a sha256sum of: 8cbafa1ef6fac079f3a32ba88c5fd1bb4bb43335feb4ff3e16fdfbd3df7a069f Apologies for the inconvenience. --dkg signature.asc Description: PGP signature
Bug#903500: New upstream version?
Hi Thomas, On Wed, 11 Jul 2018 15:31:03 +0200, Thomas Goirand wrote : > I usually upload new versions of rtslib-fb together with new versions of > OpenStack, ie every 6 months. This is due for the end of this month. So > please do upload the new version to Experimental first, and then it will > go to unstable with everything else once OpenStack is released later > this summer. I can't upload a new version of rtslib-fb to Experimental because I am not a Debian developer. So you or another Debian maintainer / developer would have to do that. With best regards, -- Christophe Vu-Brugier
Bug#903659: OpenBLAS 0.3.1 gives incorrect SVD result
Package: libopenblas-base Version: 0.3.1+ds-1 Severity: serious https://github.com/JuliaLang/julia/pull/28002 https://github.com/JuliaLang/julia/issues/27960 https://github.com/xianyi/OpenBLAS/issues/1666
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Actually, if you had virtualbox-ext-pack installed, you just need to install back/reinstall/upgrade it. -- WBR, wRAR signature.asc Description: PGP signature
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On Thu, Jul 12, 2018 at 10:16:36AM -0500, Kent West wrote: > > Note! This error could also mean that an incompatible version of the > > 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND). > While VirtualBox was broken this week, I had tried various things ( > snapshot.debian.org, virtualbox.org, etc), but once I learned that the fix > had been uploaded to stable, To unstable (the only place where it was broken). > But if I'm understanding this error, for some months (years?), I've been > pulling VirtualBox from virtualbox.org No, the extension pack can be installed on the Debian Virtualbox separately and I don't think it's installed by default even with the official package. > instead of from Debian, and whilst > doing that, had configured my VMs with USB support. And my fix should just > be to disable the USB support in my VMs The fix should be to upgrade the extension pack after you upgraded virtualbox itself... -- WBR, wRAR signature.asc Description: PGP signature
Bug#903658: ITP: eclipse-platform-ui -- User interface and help components of the Eclipse IDE
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg * Package name: eclipse-platform-ui Version : 4.7.3 Upstream Author : Eclipse Foundation, Inc. * URL : https://www.eclipse.org/eclipse/platform-ui/ * License : EPL-1.0 Programming Lang: Java Description : User interface and help components of the Eclipse IDE The Eclipse Platform UI project is responsible for the runtime, user interface and help components of Eclipse. Platform UI provides the basic building blocks to create the Eclipse IDE and other Eclipse based applications called Rich Client Platform (RCP). The Eclipse IDE is just one instance of an RCP application, but it demonstrates the power and extensibility achievable by RCP applications. This package will be maintained by the Java Team. It's required to update the Eclipse ecosystem in Debian and complete the transition to Java 11.
Bug#903657: debootstrap checks for existence of wget on --second-stage, breaking --foreign bootstraps
Package: debootstrap Version: 1.0.95ubuntu0.1 Severity: important Dear Maintainer, QEMU's build system has support for debootstrap using binfmt_misc and QEMU's linux-user emulation. Since commit 9a6ebf628 this is broken as it checks for the presence of wget which isn't available in the second-stage environment. If the user is doing a --second-stage it shouldn't matter that wget is missing as all the packages have already been downloaded on the host system. For reference the wrapper script is: https://git.qemu.org/?p=qemu.git;a=blob;f=tests/docker/dockerfiles/debian-bootstrap.pre;h=56e1aa7a21418437b5b0fbaf473a8686338d9014;hb=cee35138b59c6d6b0808c5fa644e3f063832860f And you should be able to debootstrap on QEMU's master with a line like: make docker-binfmt-image-debian-ubuntu-xenial-arm64 DEB_ARCH=arm64 \ DEB_TYPE=xenial DEB_URL=http://ports.ubuntu.com EXECUTABLE=./aarch64-linux-user/qemu-aarch64~ There is also a bug in QEMU's own script which means it always falls back to the SCM version of debootstrap, but that is mine to fix ;-) -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, armhf Kernel: Linux 4.15.0-24-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.19.4-1ubuntu2.1 Versions of packages debootstrap recommends: ii gnupg 2.2.4-1ubuntu1.1 ii ubuntu-keyring 2018.02.28 Versions of packages debootstrap suggests: pn ubuntu-archive-keyring -- no debconf information
Bug#900936: (No Subject)
>I filled a bug upstream because the source of the problem is that the agent is >started while geoclue is not running. In what file does one put the fix in the link you provided? I'd like to fix this manually...
Bug#903656: stretch-pu: package publicsuffix/20180523.2326-0+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Control: affects -1 publicsuffix Please consider an update to publicsuffix in debian stretch. This package reflects the state of the network, and keeping it current is useful for all the packages that depend on it. The debdiff from the previous version in stretch is not attached because it was being rejected as spam. This proposed release is also available at the "publicsuffix_debian/20180523.2326-0+deb9u1" tag on the "debian/stretch" branch at the git repo for publicsuffix packaging: https://salsa.debian.org/debian/publicsuffix Please followup on this ticket to confirm whether I should upload this revision to stretch.
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On Thu, Jul 12, 2018 at 10:08:06AM -0500, Kent West wrote: > I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a new > version of VirtualBox. > > When I try to start a virtual machine, I get a new error: > > > Implementation of the USB 2.0 controller not found! > > Because the USB 2.0 controller state is part of the saved VM state, the VM > cannot be started. To fix this problem, either install the > 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM > settings. > > Note! This error could also mean that an incompatible version of the > 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND). Update the extension pack. -- WBR, wRAR signature.asc Description: PGP signature
Bug#903655: libopenmpi-dev: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version
Package: libopenmpi-dev Version: 3.1.1.real-2 Severity: grave Justification: renders package unusable Did something get missed in 3.1.1.real-2? It still depends on libpmix2 (e.g. /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix2x.so), and petsc tests fail, reporting: cd src/snes/examples/tutorials >/dev/null; /usr/bin/make --no-print-directory PETSC_ARCH=x86_64-linux-gnu-real-debug PETSC_DIR=/home/drew/projects/petsc/build/petsc testex19 Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process See http://www.mcs.anl.gov/petsc/documentation/faq.html [grendel:25623] mca_base_component_repository_open: unable to open mca_pmix_pmix2x: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version (ignored) [grendel:25623] [[7790,0],0] ORTE_ERROR_LOG: Not found in file ess_hnp_module.c at line 325 -- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): opal_pmix_base_select failed --> Returned value Not found (-13) instead of ORTE_SUCCESS -- -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libopenmpi-dev depends on: ii libc62.27-4 ii libevent-2.1-6 2.1.8-stable-4 ii libevent-pthreads-2.1-6 2.1.8-stable-4 ii libhwloc-dev 1.11.10-2 ii libhwloc51.11.10-2 ii libibverbs-dev 19.0-1 ii libopenmpi3 3.1.1.real-2 ii openmpi-bin 3.1.1.real-2 ii openmpi-common 3.1.1.real-2 libopenmpi-dev recommends no packages. Versions of packages libopenmpi-dev suggests: pn openmpi-doc -- no debconf information
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On Thu, Jul 12, 2018 at 10:08 AM, Kent West wrote:
> I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a new
> version of VirtualBox.
>
> When I try to start a virtual machine, I get a new error:
>
>
> Implementation of the USB 2.0 controller not found!
>
> Because the USB 2.0 controller state is part of the saved VM state, the VM
> cannot be started. To fix this problem, either install the
> 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the
> VM settings.
>
> Note! This error could also mean that an incompatible version of the
> 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
>
> Result Code:
>
> NS_ERROR_FAILURE (0x80004005)
>
> Component:
>
> ConsoleWrap
>
> Interface:
>
> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>
>
>
While VirtualBox was broken this week, I had tried various things (
snapshot.debian.org, virtualbox.org, etc), but once I learned that the fix
had been uploaded to stable, I made sure my sources.list was "clean" of
anything non-Debian, but didn't think to look in my sources.list.d
directory for additional "add-ons". I found that I did have a virtualbox
file in that directory, which I have since removed.
But if I'm understanding this error, for some months (years?), I've been
pulling VirtualBox from virtualbox.org instead of from Debian, and whilst
doing that, had configured my VMs with USB support. And my fix should just
be to disable the USB support in my VMs, but those options are grayed
(because my VMs are in a saved state, maybe?). Once I get this figured out,
I suspect VirtualBox will work. I'll let you know.
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Got it!
I had to "Discard" the saved state, and then I could turn off the USB
support (actually just lowered it to USB 1.0), and now my VMs work!
Yea! You did great! Thanks!
On Thu, Jul 12, 2018 at 10:16 AM, Kent West wrote:
>
>
> On Thu, Jul 12, 2018 at 10:08 AM, Kent West wrote:
>
>> I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a
>> new version of VirtualBox.
>>
>> When I try to start a virtual machine, I get a new error:
>>
>>
>> Implementation of the USB 2.0 controller not found!
>>
>> Because the USB 2.0 controller state is part of the saved VM state, the
>> VM cannot be started. To fix this problem, either install the
>> 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the
>> VM settings.
>>
>> Note! This error could also mean that an incompatible version of the
>> 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
>>
>> Result Code:
>>
>> NS_ERROR_FAILURE (0x80004005)
>>
>> Component:
>>
>> ConsoleWrap
>>
>> Interface:
>>
>> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>>
>>
>>
> While VirtualBox was broken this week, I had tried various things (
> snapshot.debian.org, virtualbox.org, etc), but once I learned that the
> fix had been uploaded to stable, I made sure my sources.list was "clean" of
> anything non-Debian, but didn't think to look in my sources.list.d
> directory for additional "add-ons". I found that I did have a virtualbox
> file in that directory, which I have since removed.
>
> But if I'm understanding this error, for some months (years?), I've been
> pulling VirtualBox from virtualbox.org instead of from Debian, and whilst
> doing that, had configured my VMs with USB support. And my fix should just
> be to disable the USB support in my VMs, but those options are grayed
> (because my VMs are in a saved state, maybe?). Once I get this figured out,
> I suspect VirtualBox will work. I'll let you know.
>
> --
> Kent West<")))><
> Westing Peacefully - http://kentwest.blogspot.com
>
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
Bug#903654: tor: Tor doesn't start because of AppArmor
Package: tor Version: 0.2.9.15-1 Severity: normal Dear Maintainer, I installed Tor on my machine and haven't made any change to its config yet, as far as I know. But when I start it, AppArmor seems to stop it right at the start. More specifically, I get: # /etc/init.d/tor stop [ ok ] Stopping tor (via systemctl): tor.service. # /etc/init.d/tor start [ ok ] Starting tor (via systemctl): tor.service. # /etc/init.d/tor status tor.service - Anonymizing overlay network for TCP (multi-instance-master) Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled) Active: active (exited) since Thu 2018-07-12 11:03:03 EDT; 2min 39s ago Process: 6842 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 6842 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CPU: 0 CGroup: /system.slice/tor.service Jul 12 11:03:03 faina systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)... Jul 12 11:03:03 faina systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master). # and `journalctl -f` on the "start" part gives me: Jul 12 11:03:03 faina systemd[1]: Starting Anonymizing overlay network for TCP... Jul 12 11:03:03 faina systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master). Jul 12 11:03:04 faina tor[6862]: Jul 12 11:03:04.973 [notice] Tor 0.2.9.15 (git-2dc1a1a2abab5403) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0f and Zlib 1.2.8. Jul 12 11:03:04 faina tor[6862]: Jul 12 11:03:04.974 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 12 11:03:04 faina tor[6862]: Jul 12 11:03:04.974 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Jul 12 11:03:04 faina tor[6862]: Jul 12 11:03:04.974 [notice] Read configuration file "/etc/tor/torrc". Jul 12 11:03:05 faina tor[6862]: Configuration was valid Jul 12 11:03:05 faina audit[6873]: AVC apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 profile="unconfined" name="system_tor" pid=6873 comm="(tor)" Jul 12 11:03:05 faina kernel: audit: type=1400 audit(1531407785.239:26): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 profile="unconfined" name="system_tor" pid=6873 comm="(tor)" Jul 12 11:03:05 faina systemd[6873]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Jul 12 11:03:05 faina systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Jul 12 11:03:05 faina systemd[1]: Failed to start Anonymizing overlay network for TCP. Jul 12 11:03:05 faina systemd[1]: tor@default.service: Unit entered failed state. Jul 12 11:03:05 faina systemd[1]: tor@default.service: Failed with result 'exit-code'. Jul 12 11:03:05 faina systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Jul 12 11:03:05 faina systemd[1]: Stopped Anonymizing overlay network for TCP. repeated 5 times. I do see some tor-related file in /etc, tho: # find /etc/apparmor* -name '*tor*' /etc/apparmor.d/abstractions/tor /etc/apparmor.d/local/system_tor /etc/apparmor.d/system_tor # What am I doing wrong? Stefan -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (50, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.15.0-rc2+ (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tor depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libc62.24-11+deb9u3 ii libevent-2.0-5 2.0.21-stable-3 ii libgcc1 1:6.3.0-18+deb9u1 ii libssl1.11.1.0f-3+deb9u2 ii libsystemd0 232-25+deb9u2 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages tor recommends: ii logrotate3.11.0-0.1 pn tor-geoipdb pn torsocks Versions of packages tor suggests: pn apparmor-utils pn mixmaster pn obfs4proxy pn obfsproxy ii socat1.7.3.1-2+deb9u1 pn tor-arm pn torbrowser-launcher -- no debconf information
Bug#903653: ITP: eclipse-platform-text -- Basic building blocks for text and text editors within Eclipse
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg * Package name: eclipse-platform-text Version : 4.7.3 Upstream Author : Eclipse Foundation, Inc. * URL : http://www.eclipse.org/eclipse/platform-text/ * License : EPL-1.0 Programming Lang: Java Description : Basic building blocks for text and text editors within Eclipse Eclipse Platform Text is part of the Platform UI project and provides the basic building blocks for text and text editors within Eclipse and contributes the Eclipse default text editor. It consists of five parts: * The text infrastructure provides facilities for text manipulation, position management, and change notification. * JFace Text provides UI components for editing and presenting text. It offers support for rule based styling, content completion, formatting, model reconciling, hover help, and vertical rulers. * The text editor framework provides the abstract implementation of an Eclipse text editor. * The File Buffers plug-in which introduces text file buffers for shared access to the content of a text file in form of an IDocument and and associated IAnnotationModel. * A concrete editor implementation: the Eclipse default text editor. This package will be maintained by the Java Team. It's required to update the Eclipse ecosystem in Debian and complete the transition to Java 11.
Bug#903652: puredata-core: alsamidi not working
Package: puredata-core Version: 0.48.1-5 Severity: normal Dear Maintainer, it seems that alsamidi OUT stopped working. e.g. sending notes via [noteout] only works "a couple of times", then starts to stutter and eventually stops. i can reproduce this locally (both with dpkg-buildpackage and gbp-buildpackage builds). however, compiling the sources manually, seems to fix the problem. doing a bit of bisecting, it seems that the problem starts to appear after applying both the safe-sprintf.patch *and* the remove_unimplemented_extern.patch. without the remove_unimplemented_extern.patch, there is no problem. i have no idea. fgamdsr IOhannes -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages puredata-core depends on: ii libasound21.1.6-1 ii libc6 2.27-4 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii libportaudio2 19.6.0-1 Versions of packages puredata-core recommends: ii puredata-gui 0.48.1-5 puredata-core suggests no packages. -- no debconf information
Bug#903651: ITP: ros-urdf -- parser for urdf
Package: wnpp Severity: wishlist Owner: Johannes 'josch' Schauer * Package name: ros-urdf Version : 1.13.1 Upstream Author : Willow Garage, Inc., University of Tokyo * URL : https://github.com/ros/urdf * License : BSD-3-clause Programming Lang: C++ Description : parser for urdf Upstream of the existing Debian package src:ros-robot-model split the project into four individual projects. The maintainers of src:ros-robot-model want to follow this split and remove src:ros-robot-model in favour of four new source packages which will track each of the new projects, respectively. This ITP is for the new source package src:ros-urdf.
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a new
version of VirtualBox.
When I try to start a virtual machine, I get a new error:
Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM
cannot be started. To fix this problem, either install the
'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM
settings.
Note! This error could also mean that an incompatible version of the
'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
Bug#903649: ITP: ros-collada-urdf -- convert collada files to urdf
Package: wnpp Severity: wishlist Owner: Johannes 'josch' Schauer * Package name: ros-collada-urdf Version : 1.12.12 Upstream Author : Willow Garage, Inc., University of Tokyo * URL : https://github.com/ros/collada_urdf * License : BSD-3-clause Programming Lang: C++ Description : convert collada files to urdf Upstream of the existing Debian package src:ros-robot-model split the project into four individual projects. The maintainers of src:ros-robot-model want to follow this split and remove src:ros-robot-model in favour of four new source packages which will track each of the new projects, respectively. This ITP is for the new source package src:ros-collada-urdf.
Bug#903648: ITP: ros-joint-state-publisher -- publishing joint state messages for a robot described with urdf
Package: wnpp Severity: wishlist Owner: Johannes 'josch' Schauer * Package name: ros-joint-state-publisher Version : 1.12.13 Upstream Author : Willow Garage, Inc., University of Tokyo * URL : https://github.com/ros/joint_state_publisher * License : BSD-3-clause Programming Lang: Python Description : publishing joint state messages for a robot described with urdf Upstream of the existing Debian package src:ros-robot-model split the project into four individual projects. The maintainers of src:ros-robot-model want to follow this split and remove src:ros-robot-model in favour of four new source packages which will track each of the new projects, respectively. This ITP is for the new source package src:ros-joint-state-publisher.
Bug#903650: ITP: ros-kdl-parser -- converts urdf to kdl
Package: wnpp Severity: wishlist Owner: Johannes 'josch' Schauer * Package name: ros-kdl-parser Version : 1.13.0 Upstream Author : Willow Garage, Inc., University of Tokyo * URL : https://github.com/ros/kdl_parser * License : BSD-3-clause Programming Lang: C++ Description : converts urdf to kdl Upstream of the existing Debian package src:ros-robot-model split the project into four individual projects. The maintainers of src:ros-robot-model want to follow this split and remove src:ros-robot-model in favour of four new source packages which will track each of the new projects, respectively. This ITP is for the new source package src:ros-kdl-parser.
Bug#903644: Acknowledgement (O: bauble -- biodiversity collection manager software application)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898954 python-fibra is the extra dependency in bauble-1.0 since bauble-0.9.7 it is also the software I tried to package for Debian, and where I gave up.
Bug#812159: closed by Kartik Mistry (Bug#812159: fixed in aria2 1.34.0-2)
almost two years for a neeeded library! puff at this steps debian will goes very blurry Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2018-07-12 10:15 GMT-04:00 Debian Bug Tracking System : > This is an automatic notification regarding your Bug report > which was filed against the aria2 package: > > #812159: please enable new featured libaria2 > > It has been closed by Kartik Mistry . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Kartik Mistry < > kar...@debian.org> by > replying to this email. > > > -- > 812159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812159 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Mensaje reenviado -- > From: Kartik Mistry > To: 812159-cl...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 12 Jul 2018 14:10:45 + > Subject: Bug#812159: fixed in aria2 1.34.0-2 > Source: aria2 > Source-Version: 1.34.0-2 > > We believe that the bug you reported is fixed in the latest version of > aria2, 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 812...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Kartik Mistry (supplier of updated aria2 package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 1.8 > Date: Tue, 10 Jul 2018 09:19:46 +0530 > Source: aria2 > Binary: aria2 libaria2-0 libaria2-0-dev > Architecture: source amd64 > Version: 1.34.0-2 > Distribution: unstable > Urgency: low > Maintainer: Patrick Ruckstuhl > Changed-By: Kartik Mistry > Description: > aria2 - High speed download utility > libaria2-0 - C++ library interface to aria2 > libaria2-0-dev - High speed download utility (Development files) > Closes: 812159 > Changes: > aria2 (1.34.0-2) unstable; urgency=low > . >* debian/rules: > + Enable libaria2 library (Closes: #812159) >* debian/control: > + New binaries: libaria2-0, libaria2-0-dev. > + Updated Standards-Version to 4.1.5 >* Added debian/*.install files. > Checksums-Sha1: > 79061e88bd40effe468fd3e8495cd11d3868bade 2150 aria2_1.34.0-2.dsc > 9a56f64a0b41662deee5f8a791890d6e661aba1f 5852 > aria2_1.34.0-2.debian.tar.xz > 84d24cf4c22e5d5651f2836b7c01629fdf451de6 47480 > aria2-dbgsym_1.34.0-2_amd64.deb > 2eb88b1f2328066cbb19573787dfb8374ab95035 8304 > aria2_1.34.0-2_amd64.buildinfo > 5d5df4ae69b839474760481f47f14216f6a5e74b 361460 aria2_1.34.0-2_amd64.deb > 304af2cabb59e4dd6cad9f1643f9100ab9ec194d 29320088 > libaria2-0-dbgsym_1.34.0-2_amd64.deb > 55416918e4e3113cec9ce17425ebb01d421b6cfd 15976 > libaria2-0-dev_1.34.0-2_amd64.deb > 389d55449d08cc9df6f902f41f60fc460f9643ae 1075856 > libaria2-0_1.34.0-2_amd64.deb > Checksums-Sha256: > 67ec44d3286140e11f5d5ba78c48cc0376476a984439da92deb2b4b92bc2e0fb 2150 > aria2_1.34.0-2.dsc > 0af4d63953dfbe7bd4d8a0287a0042dd369df01b0f6de527da5da42b03e7b4f7 5852 > aria2_1.34.0-2.debian.tar.xz > 30e78e1efb48015868e395e67ace9b12e05dc2f0da1c051a62fdd82e2e23155e 47480 > aria2-dbgsym_1.34.0-2_amd64.deb > a65fba070ac898228bb5d57b7e850c55cfd361a70d8f9bbaa00c7fbce72a2214 8304 > aria2_1.34.0-2_amd64.buildinfo > d9ec42d7cb0b29f0f40cbb48b50624e4b4db01cce023e7899b08505ba6cb0574 361460 > aria2_1.34.0-2_amd64.deb > 45405eebffb5cd53802f3015b23f933c82e112f2f5e0a0e608ed4685721cdf84 > 29320088 libaria2-0-dbgsym_1.34.0-2_amd64.deb > c6e84f2f9a03f8cf1be88b93097a5819d62b75e17dd74bcd1abacc2eaa6a61f9 15976 > libaria2-0-dev_1.34.0-2_amd64.deb > 610f6727f19bb56a2b0fb8e874aa1e8da147ee57d016bf403c9f76ef5421ab21 1075856 > libaria2-0_1.34.0-2_amd64.deb > Files: > cd79cf19c9f05034e1e4da40a9307aff 2150 net optional aria2_1.34.0-2.dsc > be67ae0b7a7f72580ddf717982ba07b0 5852 net optional > aria2_1.34.0-2.debian.tar.xz > 2ca876b1372025b93885881403ca4015 47480 debug optional > aria2-dbgsym_1.34.0-2_amd64.deb > c2366f31c58880939a3004a371678fcf 8304 net optional > aria2_1.34.0-2_amd64.buildinfo > 353556a7884beea55f89536a6fc37e92 361460 net optional > aria2_1.34.0-2_amd64.deb > bb4e481326a986e06641bd1f2dd90dfc 29320088 debug optional > libaria2-0-dbgsym_1.34.0-2_amd64.deb > cc9dd4a951aabec059bb45bb5cafa47c 15976 libdevel optional > libaria2-0-dev_1.34.0-2_amd64.deb > 711dbbcf247b2a589bacb4c5bdd6dd4b 1075856 libs optional > libaria2-0_1.34.0-2_amd64.deb > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAltEPGoACgkQAsHT8ng6 >
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
I've not been able to satisfy all packaging requirements, and gave up. so I wish to close this issue, there is no candidate package any more.
Bug#903647: ITP: wmmisc -- dockapp that monitors your system
Package: wnpp Severity: wishlist Owner: Doug Torrance * Package name: wmmisc Version : 1.2 Upstream Author : Window Maker Team * URL : https://www.dockapps.net/wmmisc * License : GPL Programming Lang: C Description : dockapp that monitors your system wmmisc is a simple dockapp that monitors the following: the amount of users logged in, the total number of processes, the number of running (or 'alive') processes, the total number of forks and the system load average. wmmisc was removed in Debian in 2010. However, it was recently adopted upstream and a new version released. I plan to package wmmisc under the umbrella of the Debian Window Maker Team.
Bug#903646: libwinpr2-2: remmina crashing on reconnect
Package: libwinpr2-2 Version: 2.0.0~git20180411.1.7a7b1802+dfsg1-2 Severity: normal Hello Remote maintainers, lately remmina keeps crashing when the connection needs to be reconnected. I don't think this is a bug with remmina, but libwinpr2. It happens on RDP sessions with Windows Server 2012 and 2016, here is a backtrace I collected. Please tell me if I can supply more details! Regards Markus Core was generated by `remmina'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fee1b5303c5 in InterlockedIncrement () from /usr/lib/x86_64-linux-gnu/libwinpr2.so.2 [Current thread is 1 (Thread 0x7fee0b99f700 (LWP 27333))] (gdb) bt #0 0x7fee1b5303c5 in InterlockedIncrement () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2 #1 0x7fee1b521e32 in EnterCriticalSection () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2 #2 0x7fee1b53fe50 in MessageQueue_Dispatch () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2 #3 0x7fee1b53ffa7 in MessageQueue_Post () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2 #4 0x7fee1b8308de in drdynvc_virtual_channel_event_disconnected (drdynvc=0x7fedfc0031a0) at ./channels/drdynvc/client/drdynvc_main.c:1407 #5 0x7fee1b8308de in drdynvc_virtual_channel_init_event_ex (lpUserParam=0x7fedfc0031a0, pInitHandle=, event=3, pData=, dataLength=) at ./channels/drdynvc/client/drdynvc_main.c:1547 #6 0x7fee1bb1bf51 in freerdp_channels_disconnect (channels=channels@entry=0x56286c2223d0, instance=0x56286c0c17c0) at ./libfreerdp/core/client.c:642 #7 0x7fee1bb249ae in rdp_client_reconnect (rdp=0x56286c0c5790) at ./libfreerdp/core/connection.c:399 #8 0x7fee1bb18ce0 in freerdp_reconnect (instance=) at ./libfreerdp/core/freerdp.c:518 #9 0x7fee1bdf2114 in rf_auto_reconnect (rfi=0x56286c0c5000) at ./plugins/rdp/rdp_plugin.c:278 #10 0x7fee1bdf33b0 in remmina_rdp_main_loop (gp=0x56286be61b40) at ./plugins/rdp/rdp_plugin.c:626 #11 0x7fee1bdf33b0 in remmina_rdp_main (gp=gp@entry=0x56286be61b40) at ./plugins/rdp/rdp_plugin.c:1106 #12 0x7fee1bdf377a in remmina_rdp_main_thread (data=0x56286be61b40) at ./plugins/rdp/rdp_plugin.c:1122 #13 0x7fee314a15aa in start_thread (arg=0x7fee0b99f700) at pthread_create.c:463 #14 0x7fee2f38dcbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwinpr2-2 depends on: ii libc62.27-3 ii libssl1.11.1.0h-4 ii libsystemd0 239-5 libwinpr2-2 recommends no packages. Versions of packages libwinpr2-2 suggests: pn freerdp2-x11 -- no debconf information -- mar...@lazyfrosch.de http://www.lazyfrosch.de signature.asc Description: OpenPGP digital signature
Bug#903557: systemd-journal-upload manpages are in the wrong package
Hi Michael, On Thu, Jul 12, 2018 at 6:11 AM Michael Biebl wrote: > > Am 11.07.2018 um 11:54 schrieb Julian Calaby: > > > The manpages for systemd-journal-upload and systemd-journal-upload.service > > are > > shipped in the systemd package instead of the systemd-journal-remote where > > the > > files and binaries they document are shipped. > > Thanks for your bug report Thanks for your quick response > /usr/share/man/man8/systemd-journal-remote.socket.8.gz > /usr/share/man/man8/systemd-journal-upload.8.gz > /usr/share/man/man8/systemd-journal-remote.service.8.gz > /usr/share/man/man8/systemd-journal-upload.service.8.gz > > I think those man pages all belong into systemd-journal-remote. > Did I miss any? No, I believe that is all of them. $ dpkg-query -S journal-remote systemd-journal-remote: /lib/systemd/system/systemd-journal-remote.socket systemd-journal-remote: /usr/share/man/man5/journal-remote.conf.d.5.gz systemd-journal-remote: /lib/systemd/system/systemd-journal-remote.service systemd: /usr/share/man/man8/systemd-journal-remote.socket.8.gz systemd-journal-remote: /usr/share/doc/systemd-journal-remote/copyright systemd-journal-remote: /usr/share/man/man8/systemd-journal-remote.8.gz systemd: /usr/share/man/man8/systemd-journal-remote.service.8.gz systemd-journal-remote: /usr/share/man/man5/journal-remote.conf.5.gz systemd-journal-remote: /usr/share/doc/systemd-journal-remote/changelog.Debian.gz systemd-journal-remote: /usr/share/doc/systemd-journal-remote systemd-journal-remote: /etc/systemd/journal-remote.conf systemd-journal-remote: /lib/systemd/systemd-journal-remote $ dpkg-query -S journal-upload systemd: /usr/share/man/man8/systemd-journal-upload.service.8.gz systemd-journal-remote: /lib/systemd/systemd-journal-upload systemd-journal-remote: /lib/systemd/system/systemd-journal-upload.service systemd-journal-remote: /usr/share/man/man5/journal-upload.conf.d.5.gz systemd-journal-remote: /usr/share/man/man5/journal-upload.conf.5.gz systemd: /usr/share/man/man8/systemd-journal-upload.8.gz systemd-journal-remote: /etc/systemd/journal-upload.conf $ dpkg-query -S journal-gateway systemd-journal-remote: /usr/share/man/man8/systemd-journal-gatewayd.8.gz systemd-journal-remote: /usr/share/man/man8/systemd-journal-gatewayd.socket.8.gz systemd-journal-remote: /lib/systemd/systemd-journal-gatewayd systemd-journal-remote: /lib/systemd/system/systemd-journal-gatewayd.socket systemd-journal-remote: /usr/share/man/man8/systemd-journal-gatewayd.service.8.gz systemd-journal-remote: /lib/systemd/system/systemd-journal-gatewayd.service Thanks, -- Julian Calaby Email: julian.cal...@gmail.com Profile: http://www.google.com/profiles/julian.calaby/
Bug#903645: ITP: eclipse-platform-resources -- Fundamental model underlying the IDE portion of the Eclipse Platform
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg * Package name: eclipse-platform-resources Version : 4.7.3 Upstream Author : Eclipse Foundation, Inc. * URL : http://wiki.eclipse.org/Resources * License : EPL-1.0 Programming Lang: Java Description : Fundamental model underlying the IDE portion of the Eclipse Platform The Eclipse Platform Resources component provides the fundamental model underlying the IDE portion of the Eclipse Platform. This includes the central concepts of resources (projects, folders, and files), builders, natures, resource change listeners, etc. The resources component contains no GUI, and can be run in a completely headless Eclipse application. This package will be maintained by the Java Team. It's required to update the Eclipse ecosystem in Debian and complete the transition to Java 11.
Bug#903644: O: bauble -- biodiversity collection manager software application
Package: wnpp Severity: normal I intend to orphan the bauble package. The package description is: Bauble is a software application to help you manage a collection of botanical specimens. It is intended to be used by botanic gardens, herbaria, arboreta, etc. to manage their collection information. It is a open, free, cross-platform alternative to BG-Base and similar software. I have been in contact with the current maintainer, who wrote: You can take the maintainer responsibility of the package. I neglected it to much. At beginning (for 1.0) it was because dependencies were not in Debian, but than it exited from my radar. So feel free to be the maintainer. I started by trying to package fibra, the new dependency of bauble 1.0, and got lost in the fine details, so I give up packaging and go back focusing on development. thank you all, MF
Bug#903640: Done the work
Please, feel welcome to update the package. Thx for the work. Ghe Rivero On Thu, Jul 12, 2018 at 2:36 PM Thomas Goirand wrote: > Hi Gue, > > I've done most of the work. It's available here: > https://salsa.debian.org/openstack-team/third-party/lshw > > The package is still quite dusty and would need some refresh. > > Do you currently have time to work on this, or can I just upload? > > Cheers, > > Thomas Goirand (zigo) > -- Pinky: "Gee, Brain, what do you want to do tonight?" The Brain: "The same thing we do every night, Pinky—try to take over the world!" GPG Key: BC52FA6F GPG fingerprint: 1904 7374 5A88 BF8D FFE8 44A0 DD0B A251 BC52 FA6F
Bug#849974: openmpi: not enough slots available
On Thu, 19 Jan 2017 14:49:24 +0200 Graham Inggs wrote: > Alternatively, add the '--oversubscribe' option to the mpirun command > line, i.e.: > > mpirun --map-by socket:OVERSUBSCRIBE -np 4 python -c "print 'hello'" Here you meant mpirun --oversubscribe -np 4 python -c "print 'hello'" But the ability to oversubscribe doesn't explain the bug here. Why does openmpi think only 2 slots are available when in fact 4 processors are available? Drew
Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth
Control: severity -1 minor Hi, On Thu, 12 Jul 2018 at 15:02:20 +0200, Pascal Vibet - ADACIS wrote: > So, i apply modifications like this: > in /usr/share/initramfs-tools/hooks/cryptopensc: > […] > in /usr/share/initramfs-tools/scripts/local-top/cryptopensc: Why only in cryptopensc and not in cryptroot? Also /usr/bin/setleds comes from the ‘kbd’ package which cryptsetup-initramfs doesn't depend on (it's only a Recommends, not a hard Depends), so `copy_exec` needs to wrapped to check for the program's existence. >> INITTY=/dev/tty[1-8] >> for tty in $INITTY ; do >> setleds -D +num < $tty >> done Does that really *preserve* the numlock state? I'm not familiar with setleds(1), but according to the manpage it *sets* numlock and changes the default settings. Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#883276: avahi-browse: terminates with NXDOMAIN
same here
Bug#903643: ITP: baconqrcode -- QR Code Generator for PHP
Package: wnpp Severity: wishlist Owner: Joost van Baal-Ilić * Package name: baconqrcode Version : 2.0.0 Upstream Author : Ben "DASPRiD" Scholzen * URL : https://github.com/Bacon/BaconQrCode * License : BSD-2-clause Programming Lang: PHP Description : QR Code Generator for PHP BaconQrCode is a port of QR code portion of the ZXing library. It currently only features the encoder part, but could later receive the decoder part as well. vpn-user-portal ( https://github.com/eduvpn/vpn-user-portal ) depends upon php-bacon-qr-code . The vpn-user-portal package is part of the Let's Connect! VPN software suite. See https://bugs.debian.org/901499 and https://bugs.debian.org/901502 for other ITPs for Let's Connect!/eduVPN ( https://github.com/eduvpn/eduvpn-debian). I'll request to package this software in the PHP PEAR and Composer group at https://salsa.debian.org/php-team/pear . Bye, Joost signature.asc Description: Digital signature
Bug#903640: Done the work
Hi Gue, I've done most of the work. It's available here: https://salsa.debian.org/openstack-team/third-party/lshw The package is still quite dusty and would need some refresh. Do you currently have time to work on this, or can I just upload? Cheers, Thomas Goirand (zigo)
Bug#903642: elinks: debsums aborts when elinks + elinks-data are installed
Package: elinks Version: 0.12~pre6-13 Severity: important Dear Maintainer, Running debsums on updated sid install fails with the following error: # debsums -s debsums: Error: symlink loop detected in path 'usr/share/doc/elinks/changelog.Debian.gz'. Please file a bug again elinks. The cause of this error is unclear, as the only symling visible in given path is sane: $ ls -ld /usr/share/doc/elinks* lrwxrwxrwx 1 root root 26 août 1 2015 /usr/share/doc/elinks -> /usr/share/doc/elinks-data drwxr-xr-x 3 root root 4096 déc. 1 2017 /usr/share/doc/elinks-data And sure enough, traversal works just fine for ls: $ ls -l /usr/share/doc/elinks*/ /usr/share/doc/elinks/: total 56 -rw-r--r-- 1 root root 7720 oct. 28 2012 AUTHORS.gz -rw-r--r-- 1 root root 13083 nov. 12 2017 changelog.Debian.gz -rw-r--r-- 1 root root 468 oct. 28 2012 changelog.gz -rw-r--r-- 1 root root 6255 juin 27 2014 copyright drwxr-xr-x 6 root root 4096 déc. 1 2017 examples -rw-r--r-- 1 root root 2595 oct. 28 2012 README -rw-r--r-- 1 root root 1925 nov. 21 2013 README.Debian -rw-r--r-- 1 root root 793 oct. 28 2012 THANKS -rw-r--r-- 1 root root 464 oct. 28 2012 TODO /usr/share/doc/elinks-data/: total 56 -rw-r--r-- 1 root root 7720 oct. 28 2012 AUTHORS.gz -rw-r--r-- 1 root root 13083 nov. 12 2017 changelog.Debian.gz -rw-r--r-- 1 root root 468 oct. 28 2012 changelog.gz -rw-r--r-- 1 root root 6255 juin 27 2014 copyright drwxr-xr-x 6 root root 4096 déc. 1 2017 examples -rw-r--r-- 1 root root 2595 oct. 28 2012 README -rw-r--r-- 1 root root 1925 nov. 21 2013 README.Debian -rw-r--r-- 1 root root 793 oct. 28 2012 THANKS -rw-r--r-- 1 root root 464 oct. 28 2012 TODO I picked "important" severity as, while it does not affect elinks per se, it prevents debsums from running at all (impossible to get past that point without uninstalling elinks). Maybe this bug should be reported against debusms instead ? Regards, Vincent Pellerier -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, powerpc Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages elinks depends on: ii debconf [debconf-2.0] 1.5.67 ii elinks-data0.12~pre6-13 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.27-4 pn libcomerr2 ii libexpat1 2.2.5-3 ii libfsplib0 0.11-2 ii libgnutls303.5.18-1 ii libgpm21.20.7-5 ii libgssapi-krb5-2 1.16-2 ii libidn11 1.33-2.2 ii libk5crypto3 1.16-2 ii libkrb5-3 1.16-2 ii liblua5.1-05.1.5-8.1+b2 ii libperl5.265.26.2-6 ii libtre50.8.0-6 ii zlib1g 1:1.2.11.dfsg-1 elinks recommends no packages. Versions of packages elinks suggests: pn elinks-doc -- no debconf information -- debsums errors found: debsums: Error: symlink loop detected in path 'usr/share/doc/elinks/changelog.Debian.gz'. Please file a bug again elinks.
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Works for me also. Thank you. -Roy On 07/12/2018 07:30 AM, Christian Marillat wrote: On 12 juil. 2018 11:14, Volker Christian wrote: I can confirm that the virtual machines start again with this fix! Works for me too with 32 and 64 bits guests. Thank you very much! Me too. Christian
Bug#100808: Business Partnership Request
Hello, I am seeking your consent for a prospective and risk free business collaboration, Contact my private email for more details. Email: h@outlook.com Thanks,
Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth
Package: cryptsetup-initramfs Version: 2:2.0.2-1ubuntu1 Dear Maintainers, i propose you my fix to this problem. I'm using smartcard to decrypt luks disk, i'm using decrypt_opensc script in /etc/crypttab. I want to preserve numlock state during cryptdisk boot password prompt. I found this article: https://superuser.com/questions/1062979/preserve-numlock-state-during-cryptdisk-boot-password-prompt-in-plymouth So, i apply modifications like this: in /usr/share/initramfs-tools/hooks/cryptopensc: 65a66 > copy_exec /usr/bin/setleds in /usr/share/initramfs-tools/scripts/local-top/cryptopensc: 36a37,45 > > if [ ! -x /usr/bin/setleds ] ; then > exit 0 > fi > > INITTY=/dev/tty[1-8] > for tty in $INITTY ; do > setleds -D +num < $tty > done I apply modifications: update-initramfs -u -k all So i can use my numlock in boot password prompt for my smartcard. Cheers,
Bug#903574: Error 2304 in GDM login page when i use smartcard to decrypt disk and to login into Gnome Session
Hi, My fault. You are right, it's '‘$!’ not ‘$?’. Cheers, 2018-07-11 17:58 GMT+02:00 Guilhem Moulin : > Control: reassign -1 cryptsetup-initramfs > Control: retitle -1 opensc: can't use smartcard after pivot_root because > pcscd isn't killed at local-bottom stage > Control: tag -1 pending > > Hi, > > On Wed, 11 Jul 2018 at 15:05:47 +0200, Pascal Vibet - ADACIS wrote: > > In /usr/share/initramfs-tools/scripts/local-top/cryptopensc, PSCSD > process is start and go in background. But the PID is not store, so i fix > it with: > > 36a37 > >> echo $? > /var/run/pcscd.pid > > I assume you meant ‘$!’ not ‘$?’ here [0]. Thanks for the patch, I > just applied it with minor modifications: > > https://salsa.debian.org/cryptsetup-team/cryptsetup/commit/ > 8190cb3bc8a4bb4205abc5f66376a2586896e6df > > Cheers, > -- > Guilhem. > > [0] http://pubs.opengroup.org/onlinepubs/9699919799/ > utilities/V3_chap02.html#tag_18_05_02 >
Bug#903640: Please package new version B.02.18.85
Package: lshw Version: 02.18-0.1 Severity: important Dear maintainer, It looks like upstream for lshw is quite dead, however, there's a fork available in here: https://github.com/lyonel/lshw What I found horrible with lshw, is that its json output is completely broken. Just try to make jq parse it, and you'll see what I mean. The good news is that this fork has a repaired version of it, and the json output looks better now. It's still not fully working, but at least it does when requesting a specific class of hardware (which is what I currently need). For example, this works with the version on Github, when it doesn't with the current Sid version: ./src/lshw -class network 2>/dev/null -json | jq . Please get this new version in Debian. Cheers, Thomas Goirand (zigo)
Bug#903441: dgit: autopkgtest failures in Ubuntu [and 1 more messages]
Ian Jackson writes ("Re: Bug#903598: devscripts: dch -r [something]"):
> Mattia Rizzolo writes ("Re: Bug#903598: devscripts: dch -r [something]"):
> > Ton of things use '' (i.e. empty string). Including debchange's
> > testsuite :3
>
> Well, that's helpful information, indeed. I will do the same :-).
This is now implemented in 5.9+exp1, just uploaded to Debian
experimental. Can you give it a try in Ubuntu please ?
I have also made use of AUTOPKGTEST_ARTIFACTS and I would like to know
if this output is too large.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#898823: does not work for cryptopro test servers
Package: libengine-gost-openssl1.1 Version: 1.1.0.1-1 Followup-For: Bug #898823 Hello Wartan, Any progress on this bug? If the issue is within OpenSSL itself most probably we should reassign the bug to OpenSSL package and provide them necessary patches to be applied. -- With best wishes Dmitry -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libengine-gost-openssl1.1 depends on: ii libc6 2.27-3 ii libssl1.1 1.1.0h-4 libengine-gost-openssl1.1 recommends no packages. libengine-gost-openssl1.1 suggests no packages. -- no debconf information
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On 12 juil. 2018 11:14, Volker Christian wrote: > I can confirm that the virtual machines start again with this fix! Works for me too with 32 and 64 bits guests. > Thank you very much! Me too. Christian
