Bug#927333: node-postcss-reporter: depends on non-existent node-log-symbols
Package: node-postcss-reporter Version: 5.0.0-1 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco The node-postcss-reporter package is uninstallable because it depends on a non-existent node-log-symbols package. $ sudo apt install node-postcss-reporter Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: node-postcss-reporter : Depends: node-log-symbols (>= 2.0.0) but it is not installable E: Unable to correct problems, you have held broken packages. $ -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#926917: marked as done (openjdk-13-doc: ships usr/share/doc/openjdk-12-jre-headless/api/jquery/*)
Your message dated Thu, 18 Apr 2019 05:08:09 + with message-id and subject line Bug#926917: fixed in openjdk-13 13~17-1 has caused the Debian Bug report #926917, regarding openjdk-13-doc: ships usr/share/doc/openjdk-12-jre-headless/api/jquery/* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-13-doc Version: 13~12-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. Looks like a hardcoded package name/path somewhere ... >From the attached log (scroll to the bottom...): Preparing to unpack .../openjdk-13-doc_13~12-1_all.deb ... Unpacking openjdk-13-doc (13~12-1) ... dpkg: error processing archive /var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/openjdk-12-jre-headless/api/jquery/external/jquery/jquery.js', which is also in package openjdk-12-doc 12.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb This is the list of clashing files: usr/share/doc/openjdk-12-jre-headless/api/jquery/external/jquery/jquery.js usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-3.3.1.js usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.css usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.js usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.min.css usr/share/doc/openjdk-12-jre-headless/api/jquery/jquery-ui.min.js cheers, Andreas openjdk-12-doc=12.0.0-3_openjdk-13-doc=13~12-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openjdk-13 Source-Version: 13~17-1 We believe that the bug you reported is fixed in the latest version of openjdk-13, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-13 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: Thu, 18 Apr 2019 06:33:56 +0200 Source: openjdk-13 Architecture: source Version: 13~17-1 Distribution: experimental Urgency: medium Maintainer: OpenJDK Team Changed-By: Matthias Klose Closes: 926845 926917 Changes: openjdk-13 (13~17-1) experimental; urgency=medium . [ Matthias Klose ] * Build the alternate zero VM using the just built hotspot VM. * Remove the icedtea-sound/pulseaudio build support. * Remove some xulrunner build bits. * Annotate the bootstrap dependency with :native. * Fix installation of the -doc package. Closes: #926845, #926917. . [ Tiago Stürmer Daitx ] * Install swing.properties into /conf instead of /lib. Checksums-Sha1: 4222901dba6fe2e6651cf9b94a3888d4bf518336 4644 openjdk-13_13~17-1.dsc 17abad06ff98254cf8a11c19c6e851c994cbc47e 68633036 openjdk-13_13~17.orig.tar.xz 5fb5b639b14909acba27a1b493c3bea72edc4936 165020 openjdk-13_13~17-1.debian.tar.xz dd41f8d03632f0b553e393e5a126949fd7871861 17312 openjdk-13_13~17-1_source.buildinfo Checksums-Sha256: 4dbecce8627e46c336b70d72e33e463ba46b26d159ff2e2dea211abec0161592 4644 openjdk-13_13~17-1.dsc 6bfedb954060252645617c4f0d93889ea81c597795b9c0971dc72eafaafe7823 68633036 openjdk-13_13~17.orig.tar.xz d6beec43b769af1a5ec2fcea5eab738e49b153b7f5a4faad53c84a3bffb55d64 165020 openjdk-13_13~17-1.debian.tar.xz 24623d6affe1ae53bc3934aa7a591a0b7305eb3dd9f255cd102e5cff22dc3a9a 17312 openjdk-13_13~17-1_source.buildinfo Files: dfa197833ef0557a012946538c23abe3 4644 java optional openjdk-13_13~17-1.dsc 3efbf96e661669998fd93fe214f8f31e 68633036 java optional openjdk-13_13~17.orig.tar.xz de64847d17cdba6bffd3014beb7a18f3 165020 java optional openjdk-13_13~17-1.debian.tar.xz 377b6e70933acd7013a0bf6fc9d49e6c 17312 java optional openjdk-13_13~17-1_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#926845: marked as done (openjdk-13-doc: conflicts with openjdk-12-doc)
Your message dated Thu, 18 Apr 2019 05:08:08 + with message-id and subject line Bug#926845: fixed in openjdk-13 13~17-1 has caused the Debian Bug report #926845, regarding openjdk-13-doc: conflicts with openjdk-12-doc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-13-doc Severity: grave Justification: renders package unusable --8<---cut here---start->8--- Unpacking openjdk-13-doc (13~12-1) ... dpkg: error processing archive /var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/openjdk-12-jre-headless/api/jquery/external/jquery/jquery.js', which is also in package openjdk-12-doc 12.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --8<---cut here---end--->8--- -- System Information: Debian Release: buster/sid APT prefers stable APT policy: (900, 'stable'), (190, 'testing'), (180, 'unstable'), (170, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openjdk-13-doc depends on: ii libjs-jquery 3.3.1~dfsg-1 ii libjs-jquery-ui 1.12.1+dfsg-5 openjdk-13-doc recommends no packages. Versions of packages openjdk-13-doc suggests: ii openjdk-13-jdk 13~12-1 --- End Message --- --- Begin Message --- Source: openjdk-13 Source-Version: 13~17-1 We believe that the bug you reported is fixed in the latest version of openjdk-13, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-13 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: Thu, 18 Apr 2019 06:33:56 +0200 Source: openjdk-13 Architecture: source Version: 13~17-1 Distribution: experimental Urgency: medium Maintainer: OpenJDK Team Changed-By: Matthias Klose Closes: 926845 926917 Changes: openjdk-13 (13~17-1) experimental; urgency=medium . [ Matthias Klose ] * Build the alternate zero VM using the just built hotspot VM. * Remove the icedtea-sound/pulseaudio build support. * Remove some xulrunner build bits. * Annotate the bootstrap dependency with :native. * Fix installation of the -doc package. Closes: #926845, #926917. . [ Tiago Stürmer Daitx ] * Install swing.properties into /conf instead of /lib. Checksums-Sha1: 4222901dba6fe2e6651cf9b94a3888d4bf518336 4644 openjdk-13_13~17-1.dsc 17abad06ff98254cf8a11c19c6e851c994cbc47e 68633036 openjdk-13_13~17.orig.tar.xz 5fb5b639b14909acba27a1b493c3bea72edc4936 165020 openjdk-13_13~17-1.debian.tar.xz dd41f8d03632f0b553e393e5a126949fd7871861 17312 openjdk-13_13~17-1_source.buildinfo Checksums-Sha256: 4dbecce8627e46c336b70d72e33e463ba46b26d159ff2e2dea211abec0161592 4644 openjdk-13_13~17-1.dsc 6bfedb954060252645617c4f0d93889ea81c597795b9c0971dc72eafaafe7823 68633036 openjdk-13_13~17.orig.tar.xz d6beec43b769af1a5ec2fcea5eab738e49b153b7f5a4faad53c84a3bffb55d64 165020 openjdk-13_13~17-1.debian.tar.xz 24623d6affe1ae53bc3934aa7a591a0b7305eb3dd9f255cd102e5cff22dc3a9a 17312 openjdk-13_13~17-1_source.buildinfo Files: dfa197833ef0557a012946538c23abe3 4644 java optional openjdk-13_13~17-1.dsc 3efbf96e661669998fd93fe214f8f31e 68633036 java optional openjdk-13_13~17.orig.tar.xz de64847d17cdba6bffd3014beb7a18f3 165020 java optional openjdk-13_13~17-1.debian.tar.xz 377b6e70933acd7013a0bf6fc9d49e6c 17312 java optional openjdk-13_13~17-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAly3/80QHGRva29AdWJ1
Bug#900912: marked as done (openjdk-11: Accessibility does not get loaded)
Your message dated Thu, 18 Apr 2019 03:22:30 + with message-id and subject line Bug#900912: fixed in openjdk-11 11.0.3+7-2 has caused the Debian Bug report #900912, regarding openjdk-11: Accessibility does not get loaded to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 900912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjdk-10 Version: 10.0.1+10-4 Severity: important Tags: a11y Hello, Like with openjdk-9, accessibility does not work in the openjdk-10 packages, the libatk-wrapper and java-atk-wrapper do not get loaded. See Bug#822642 for my researches at the time, I gues things haven't improved since then. I have pasted it for conveniency: “ In previous versions there were symlinks for java-atk-wrapper.jar and libatk-wrapper.so in /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext but with openjdk-9 this directory seems to be disabled. I see that it's where the class gets loaded from with openjdk-8: -verbose:class show: [Loaded org.GNOME.Accessibility.AtkWrapper from file:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/java-atk-wrapper.jar] and removing that file brings Exception in thread "main" java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:807) at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:886) at java.awt.Window.getToolkit(Window.java:1362) I tried to look for the equivalent code in openjdk-9, but I don't see where the binary is supposed to be: in openjdk-8, it was in rt.jar, but I can't find this in openjdk-9. The source code of getDefaultToolkit seems to be the same, except that it also checks for running headless. Perhaps that's the test that fails? ” I guess openjdk-8 will be phased out in Buster, so this is a really important issue: people needing accessibility will not be able to use java applications at all any more if openjdk-10 does not properly load accessibility support. Samuel -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: openjdk-11 Source-Version: 11.0.3+7-2 We believe that the bug you reported is fixed in the latest version of openjdk-11, 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 900...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-11 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: Thu, 18 Apr 2019 04:54:26 +0200 Source: openjdk-11 Architecture: source Version: 11.0.3+7-2 Distribution: unstable Urgency: high Maintainer: OpenJDK Team Changed-By: Matthias Klose Closes: 900912 Changes: openjdk-11 (11.0.3+7-2) unstable; urgency=medium . * Fix 8210739: Calling JSpinner's setFont with null throws NullPointerException. * Fix 8210483: AssertionError in DeferredAttr at setOverloadKind caused by JDK-8203679. . openjdk-11 (11.0.3+7-1) unstable; urgency=high . * OpenJDK 11.0.3+7 build. - Security fixes: - S8211936, CVE-2019-2602: Better String parsing. - S8218453, CVE-2019-2684: More dynamic RMI interactions. - S8219066, CVE-2019-2698: Fuzzing TrueType fonts: setCurrGlyphID(). * Support using the Java ATK wrapper (Samuel Thibault). Closes: #900912. - patches/jaw-classpath.diff: Fix finding the Java ATK wrapper. - patches/jaw-optional.diff: Make failing to load the Java ATK wrapper non-fatal. Checksums-Sha1:
Bug#927307: libgraphicsmagick breaks gnudatalanguage
Control: tags -1 +confirmed
On Wed, Apr 17, 2019 at 10:00 PM Bob Friesenhahn
wrote:
> On Wed, 17 Apr 2019, Ole Streicher wrote:
> > gdl: magick/semaphore.c:606: LockSemaphoreInfo:
> > Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed.
> > Aborted
>
> A stack trace would be very useful in order to diagnose the cause.
> Unfortunately, the assertion does not reveal which semaphore is
> involved.
Simply invoking gdl also produce:
gdl: magick/semaphore.c:606: LockSemaphoreInfo: Assertion
`semaphore_info != (SemaphoreInfo *) NULL' failed.
Aborted
strace didn't reveal too much things (not for me at least). The gdb
backtrace says:
#0 0x7335b8bb in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:50
set =
{__val = {0, 93824992798416, 0, 140737274038087,
4222451712, 93824992798416, 93824992798517, 93824992798416,
93824992798416, 93824992798525, 93824992798716, 93824992798416,
93824992798716, 0, 0, 0}}
pid =
tid =
#1 0x73346535 in __GI_abort () at abort.c:79
save_stage = 1
act =
{__sigaction_handler = {sa_handler = 0x55578090,
sa_sigaction = 0x55578090}, sa_mask = {__val = {0, 303,
93824992798416, 0, 0, 0, 21474836480, 140737488349736,
140737488349584, 140737275153072, 140737275137760, 0,
7985314115815763968, 140737275122618, 0, 140737275137760}}, sa_flags =
-161122104, sa_restorer = 0x76657940}
sigs = {__val = {32, 0 }}
#2 0x7334640f in __assert_fail_base
(fmt=0x734a8ee0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=0x76657940 "semaphore_info != (SemaphoreInfo *) NULL",
file=0x766578c8 "magick/semaphore.c", line=606,
function=) at assert.c:92
str = 0x55578090 ""
total = 4096
#3 0x733540f2 in __GI___assert_fail
(assertion=0x76657940 "semaphore_info != (SemaphoreInfo *)
NULL", file=0x766578c8 "magick/semaphore.c", line=606,
function=0x766579c0 "LockSemaphoreInfo") at assert.c:101
#4 0x7651802d in LockSemaphoreInfo ()
at /usr/lib/libGraphicsMagick-Q16.so.3
#5 0x76514e59 in GetMagickResourceLimit ()
at /usr/lib/libGraphicsMagick-Q16.so.3
#6 0x764f1719 in GetCacheInfo ()
at /usr/lib/libGraphicsMagick-Q16.so.3
#7 0x764d4081 in AllocateImage ()
at /usr/lib/libGraphicsMagick-Q16.so.3
#8 0x763eacf5 in Magick::ImageRef::ImageRef() (this=0x555d9740)
at Magick++/lib/ImageRef.cpp:49
#9 0x763e155c in Magick::Image::Image()
(this=0x77f9fc60 ) at Magick++/lib/Image.cpp:278
#10 0x773fb1d0 in ()
at /usr/lib/x86_64-linux-gnu/libgnudatalanguage.so.0
#11 0x77fe430a in call_init
(l=, argc=argc@entry=1,
argv=argv@entry=0x7fffec58, env=env@entry=0x7fffec68) at
dl-init.c:72
j =
jm =
addrs =
init_array =
#12 0x77fe4406 in call_init
(env=0x7fffec68, argv=0x7fffec58, argc=1, l=)
at dl-init.c:30
preinit_array =
preinit_array_size =
i = 1
#13 0x77fe4406 in _dl_init
(main_map=0x77ffe190, argc=1, argv=0x7fffec58, env=0x7fffec68)
at dl-init.c:119
preinit_array =
preinit_array_size =
i = 1
#14 0x77fd60ca in _dl_start_user () at /lib64/ld-linux-x86-64.so.2
#15 0x0001 in ()
#16 0x7fffee4c in ()
#17 0x in ()
Sorry for my brevity, it's almost morning here. Should rest before my
working hours. But I hope this helps something.
Regards,
Laszlo/GCS
Processed: Re: Bug#927307: libgraphicsmagick breaks gnudatalanguage
Processing control commands: > tags -1 +confirmed Bug #927307 [libgraphicsmagick-q16-3] libgraphicsmagick breaks gnudatalanguage Added tag(s) confirmed. -- 927307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921688: saw this
This is still happening, the legitimate public servers may not work with electrum 3.3, but there are dozens of rogue servers that do and that are exploiting this bug. -- see shy jo signature.asc Description: PGP signature
Bug#927314: rust-ascii depends on obsolete version of librust-quickcheck-dev
Package: librust-ascii+quickcheck-dev Version: 0.9.1-1 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco The rust-ascii package in unstable depends on an obsolete version of librust-quickcheck-dev: $ sudo apt install librust-ascii+quickcheck-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: librust-ascii+quickcheck-dev : Depends: librust-quickcheck-0.6+default-dev but it is not installable E: Unable to correct problems, you have held broken packages. $ librust-quickcheck+default-dev is at version 0.7 in testing and version 0.8 in unstable, and neither provide the 0.6 that this depends on. rust-ascii needs to be updated for a current rust-quickcheck. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#917501: meson: does not build ok when built with eatmydata + overlayfs
severity 917501 normal retitle 917501 meson: does not build ok when built with eatmydata + overlayfs thanks [ Cc:ing all the parties who tried to help ] I'm really sorry. My apologies. I usually build with eatmydata and overlayfs, as it speeds the build a lot, and I forgot to try without those addons for this package. After I stopped using eatmydata, the package built ok for me. My mistake was to assume that because it failed for me and it failed in reproducible-builds, it would fail in the usual sense, but a failure which only happens when using eatmydata is not a "real" failure. I suspect that this fails in reproducible-builds because they use eatmydata as well, but I don't know how to check this. Thanks and sorry again.
Processed: Re: Bug#917501: meson: does not build ok when built with eatmydata + overlayfs
Processing commands for cont...@bugs.debian.org: > severity 917501 normal Bug #917501 [src:meson] meson: FTBFS (failing tests) Severity set to 'normal' from 'serious' > retitle 917501 meson: does not build ok when built with eatmydata + overlayfs Bug #917501 [src:meson] meson: FTBFS (failing tests) Changed Bug title to 'meson: does not build ok when built with eatmydata + overlayfs' from 'meson: FTBFS (failing tests)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 917501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927310: libvirt-daemon: LXC container shut down, e.g., virsh -c lxc:// shutdown , is ignored
Package: libvirt-daemon Version: 5.0.0-2 Severity: grave Tags: patch Justification: renders package unusable Dear maintainer, LXC container shut down is ignore. Amongst others, this will induce a hang on host shut down as the libvirt daemon waits 3 minutes per active container for shut down. Relevant patches from upstram are >From 64eca3d5e30030147383bc63eba77e723563d4e2 Mon Sep 17 00:00:00 2001 From: Michal Privoznik Date: Fri, 25 Jan 2019 12:37:53 +0100 Subject: [PATCH 1/2] virinitctl: Expose fifo paths and allow caller to chose one So far the virInitctlSetRunLevel() is fully automatic. It finds the correct fifo to use to talk to the init and it will set the desired runlevel. Well, callers (so far there is just one) will need to inspect the fifo a bit just before the runlevel is set. Therefore, expose the internal list of fifos and also allow caller to explicitly use one. Signed-off-by: Michal Privoznik Reviewed-by: Erik Skultety >From 94fce255461ad6bf0366dd4428921d7d41ba1a8f Mon Sep 17 00:00:00 2001 From: Michal Privoznik Date: Fri, 25 Jan 2019 12:42:54 +0100 Subject: [PATCH 2/2] lxc: Don't reboot host on virDomainReboot If the container is really a simple one (init is just bash and the whole root is passed through) then virDomainReboot and virDomainShutdown will talk to the actual init within the host. Therefore, 'virsh shutdown $dom' will result in shutting down the host. True, at that point the container is shut down too but looks a bit harsh to me. The solution is to check if the init inside the container is or is not the same as the init running on the host. Signed-off-by: Michal Privoznik Reviewed-by: Erik Skultety >From 14b6a1854fb4c02c5fb2f51679f8ff099f28f53c Mon Sep 17 00:00:00 2001 From: Maxim Kozin Date: Wed, 6 Mar 2019 21:39:11 +0300 Subject: [PATCH] lxc: Try harder to stop/reboot containers If shutting down a container via setting the runlevel fails, the control jumps right onto endjob label and doesn't even try sending the signal. If flags allow it, we should try both methods. Signed-off-by: Maxim Kozin Signed-off-by: Michal Privoznik -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libvirt-daemon depends on: ii libacl1 2.2.53-4 ii libapparmor12.13.2-10 ii libaudit1 1:2.8.4-2 ii libavahi-client30.7-4+b1 ii libavahi-common30.7-4+b1 ii libblkid1 2.33.1-0.1 ii libc6 2.28-8 ii libcap-ng0 0.7.9-2 ii libcurl3-gnutls 7.64.0-2 ii libdbus-1-3 1.12.12-1 ii libdevmapper1.02.1 2:1.02.155-2 ii libfuse22.9.9-1 ii libgcc1 1:8.3.0-6 ii libgnutls30 3.6.6-2 ii libnetcf1 1:0.2.8-1+b2 ii libnl-3-200 3.4.0-1 ii libnl-route-3-200 3.4.0-1 ii libnuma12.0.12-1 ii libparted2 3.2-24 ii libpcap0.8 1.8.1-6 ii libpciaccess0 0.14-1 ii libsasl2-2 2.1.27+dfsg-1 ii libselinux1 2.8-1+b1 ii libssh2-1 1.8.0-2.1 ii libudev1241-3 hi libvirt05.0.0-2 ii libxenmisc4.11 4.11.1+26-g87f51bf366-3 ii libxenstore3.0 4.11.1+26-g87f51bf366-3 ii libxentoollog1 4.11.1+26-g87f51bf366-3 ii libxml2 2.9.4+dfsg1-7+b3 ii libyajl22.1.0-3 Versions of packages libvirt-daemon recommends: ii libxml2-utils 2.9.4+dfsg1-7+b3 ii netcat-openbsd 1.195-2 ii qemu-kvm1:3.1+dfsg-7 Versions of packages libvirt-daemon suggests: pn libvirt-daemon-driver-storage-gluster pn libvirt-daemon-driver-storage-rbd pn libvirt-daemon-driver-storage-zfs hi libvirt-daemon-system 5.0.0-2 ii numad 0.5+20150602-5 -- no debconf information >From 64eca3d5e30030147383bc63eba77e723563d4e2 Mon Sep 17 00:00:00 2001 From: Michal Privoznik Date: Fri, 25 Jan 2019 12:37:53 +0100 Subject: [PATCH 1/2] virinitctl: Expose fifo paths and allow caller to chose one So far the virInitctlSetRunLevel() is fully automatic. It finds the correct fifo to use to talk to the init and it will set the desired runlevel. Well, callers (so far there is just one) will need to inspect the fifo a bit just before the runlevel is set. Therefore, expose the internal list of fifos and also allow caller to explicitly use one. Signed-off-by: Michal Privoznik Reviewed-by: Erik Skultety --- src/libvirt_private.syms | 1 + src/lxc/lxc_driver.c | 2 +- src/util/virinitctl.c| 67 ++-- src/util/virinitctl.h| 6 +++- 4 files changed, 50 insertions(+), 26 deletions(-) Index: libvirt/src/libvirt_private.syms
Processed: tagging 883872
Processing commands for cont...@bugs.debian.org: > tags 883872 + patch Bug #883872 [src:bitlbee] bitlbee: Extremely incomplete d/copyright Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 883872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926928: closing 926928
close 926928 thanks Maybe a coincidence with the provider changing their certificate. Glad to hear it's fixed, so closing. Cheers Jochen
Processed: closing 926928
Processing commands for cont...@bugs.debian.org: > close 926928 Bug #926928 [fetchmail] fetchmail: Server CommonName mismatch Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 926928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927307: libgraphicsmagick breaks gnudatalanguage
On Wed, 17 Apr 2019, Ole Streicher wrote: gdl: magick/semaphore.c:606: LockSemaphoreInfo: Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed. Aborted A stack trace would be very useful in order to diagnose the cause. Unfortunately, the assertion does not reveal which semaphore is involved. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
Bug#927308: mysql-5.7: Security fixes from the April 2019 CPU
Source: mysql-5.7 Version: 5.7.25-1 Severity: grave Tags: security upstream Hi See https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html#AppendixMSQL for a list of CVEs affecting src:mysql-5.7. Regards, Salvatore
Bug#905772: libvirtd upgrade broken stretch->buster
When I marked the bug RC, I thought it was happening all the time; I then went to reproduce yet again in a controlled environment to be more in a position to test a fix. That's when I discovered things are more complex. Obviously if this is a fringe situation, then it shouldn't be RC.
Bug#905772: libvirtd upgrade broken stretch->buster
Hi, On Wed, Apr 17, 2019 at 02:47:41PM -0400, Sam Hartman wrote: > but I haven't been able to reproduce on a clean install. > It's frustrating: on my machines where I really want the upgrade to be > smoothe this bit me, but on all my toy tests, it didn't happen. > What I think may be necessary is for virtlogd to be active. > So it may be necessary to actually get libvirtd running and actually > running a VM to use the socket before the issue comes up. That's possible. > Alternatively, it's possible some other change has fixed this in the > last month. We did not change anything in that area so it's likely hidden (e.g. only happening when running a VM) - I'll check that. > I'll certainly say that a month ago ran into this on two different VM > servers. That's an important data point. Thanks -- Guido
Bug#926784: firehol: Please document usage of iptables-legacy
Hi, just a follow up from today. On host, where I was debuging firehol behaviour on iptables-nft vs. iptables- legacy (before reporting bug) , I got strange behavior after upgrading to 3.1.6+ds-8. It was caused by my manual change of iptables alternatives -legacy one. Sequence was like this: install firehol 3.1.6+ds-7 setup firewall (loaded do nft tables) do some debuging to find out that you need -legacy update-alternatives to iptables-legacy load firewall again (this time, it loads to legacy iptables) upgrade to firehol 3.1.6+ds-8, keep iptables alternatives to -legacy Now you have two "identical" firewalls ;) - first was loaded with old version of firehol to nft, second is loaded to legacy tables. Now change config of firehol, open new port to be accessible, reload firehol and test it. It's not accessible, iptables keep logging dropped packet. Try to allow all access, try to stop firehol - port is still not accessible. List your firewall using iptables -L You see empty ruleset with policy=ACCEPT in all chains. Go crazy ;) Try to list iptables-nft -L AHA - here is your firewall blocking your access. (it also warns you, that there are some rules in legacy tables) Reboot I think, users are safe to upgrade from -7 to -8 , unless they did manual override of iptables alternatives. Libor
Bug#927307: libgraphicsmagick breaks gnudatalanguage
Package: libgraphicsmagick-q16-3 Version: 1.4~hg15968-1 Severity: serious Control: affects -1 gnudatalanguage gdl-coyote gdl-mpfit gdl-astrolib The latest upload of graphicsmagick to unstable breaks the CI test of gnudatalanguage and all GDL packages, and also causes an FTBFS for these packages. CI failure is catched in https://ci.debian.net/data/autopkgtest/unstable/amd64/g/gnudatalanguage/2250913/log.gz with the overall error gdl: magick/semaphore.c:606: LockSemaphoreInfo: Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed. Aborted This is an assertion within graphicsmagick. It is a regression and worked well with 1.4~hg15916-2. Best regards Ole
Processed: libgraphicsmagick breaks gnudatalanguage
Processing control commands: > affects -1 gnudatalanguage gdl-coyote gdl-mpfit gdl-astrolib Bug #927307 [libgraphicsmagick-q16-3] libgraphicsmagick breaks gnudatalanguage Added indication that 927307 affects gnudatalanguage, gdl-coyote, gdl-mpfit, and gdl-astrolib -- 927307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905772: libvirtd upgrade broken stretch->buster
> "Guido" == Guido Günther writes: Guido> Hi, Guido> On Mon, Apr 15, 2019 at 02:38:27PM -0400, Sam Hartman wrote: >> control: severity -1 serious >> >> justification: libvirtd upgrades from stretch to buster break >> causing apt to fail and requiring the admin to get the systemd >> units into a consistent state before things can continue >> >> >> Unfortunately based on discussion so far this is a complex bug to >> fix. Ubuntu's solution is to drop the sysv scripts and to drop >> Also= lines in some of the units. Guido> Did you reproduce this bug on a stretch->buster upgrade? Guido> Cause I just did that and didn't encounter any errors. I've run into this on two active server upgrades--servers that were running VMs, but I haven't been able to reproduce on a clean install. It's frustrating: on my machines where I really want the upgrade to be smoothe this bit me, but on all my toy tests, it didn't happen. What I think may be necessary is for virtlogd to be active. So it may be necessary to actually get libvirtd running and actually running a VM to use the socket before the issue comes up. Alternatively, it's possible some other change has fixed this in the last month. I'll certainly say that a month ago ran into this on two different VM servers.
Bug#910964: marked as done (libprotobuf17 needs Breaks: libprotobuf10)
Your message dated Wed, 17 Apr 2019 18:34:17 + with message-id and subject line Bug#910964: fixed in protobuf 3.6.1.3-2 has caused the Debian Bug report #910964, regarding libprotobuf17 needs Breaks: libprotobuf10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 910964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libprotobuf17 Version: 3.6.1-2 Severity: serious Control: affects -1 src:cura-engine https://buildd.debian.org/status/package.php?p=cura-engine=sid ... Running tests... /usr/bin/ctest --force-new-ctest-process -j4 Test project /<>/obj-x86_64-linux-gnu Start 1: SpaceFillingTreeFillTest Start 2: SparseGridTest Start 3: IntPointTest Start 4: LinearAlg2DTest 1/8 Test #1: SpaceFillingTreeFillTest .***Exception: Child aborted 0.02 sec [libprotobuf FATAL google/protobuf/stubs/common.cc:79] This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) terminate called after throwing an instance of 'google::protobuf::FatalException' what(): This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) Start 5: PolygonUtilsTest 2/8 Test #2: SparseGridTest ...***Exception: Child aborted 0.03 sec [libprotobuf FATAL google/protobuf/stubs/common.cc:79] This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) terminate called after throwing an instance of 'google::protobuf::FatalException' what(): This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) Start 6: PolygonTest 3/8 Test #3: IntPointTest .***Exception: Child aborted 0.03 sec [libprotobuf FATAL google/protobuf/stubs/common.cc:79] This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) terminate called after throwing an instance of 'google::protobuf::FatalException' what(): This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) Start 7: StringTest 4/8 Test #4: LinearAlg2DTest ..***Exception: Child aborted 0.02 sec [libprotobuf FATAL google/protobuf/stubs/common.cc:79] This program was compiled against version 3.0.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.6.1). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".) terminate called after throwing an instance of 'google::protobuf::FatalException'
Bug#905772: libvirtd upgrade broken stretch->buster
Hi, On Mon, Apr 15, 2019 at 02:38:27PM -0400, Sam Hartman wrote: > control: severity -1 serious > > justification: libvirtd upgrades from stretch to buster break causing > apt to fail and requiring the admin to get the systemd units into a > consistent state before things can continue > > > Unfortunately based on discussion so far this is a complex bug to fix. > Ubuntu's solution is to drop the sysv scripts and to drop Also= lines > in some of the units. Did you reproduce this bug on a stretch->buster upgrade? Cause I just did that and didn't encounter any errors. Cheers, -- Guido
Bug#921232: marked as done (mono: Internal compiler error building libsbml on s390x)
Your message dated Wed, 17 Apr 2019 17:58:13 + with message-id and subject line Bug#921232: fixed in mono 5.18.0.240+dfsg-3 has caused the Debian Bug report #921232, regarding mono: Internal compiler error building libsbml on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mono-mcs Version: 5.18.0.240+dfsg-2 Severity: serious Control: affects -1 src:libsbml https://buildd.debian.org/status/fetch.php?pkg=libsbml=s390x=5.17.2%2Bdfsg-3=1548889326=0 ... [ 98%] Build csharp files Creating: libsbmlcsP.dll csharp-files/FbcModelPlugin.cs(119,3): error CS0589: Internal compiler error during parsingSystem.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length at System.String.Substring (System.Int32 startIndex, System.Int32 length) [0x0003a] in :0 at System.String.SplitKeepEmptyEntries (System.ReadOnlySpan`1[T] sepList, System.ReadOnlySpan`1[T] lengthList, System.Int32 defaultLength, System.Int32 count) [0x00049] in :0 at System.String.SplitInternal (System.ReadOnlySpan`1[T] separators, System.Int32 count, System.StringSplitOptions options) [0x000d1] in :0 at System.String.Split (System.Char separator, System.StringSplitOptions options) [0x9] in :0 at Mono.CSharp.Tokenizer.update_formatted_doc_comment (System.Int32 current_comment_start) [0x0002a] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.Tokenizer.xtoken () [0x00b1c] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.Tokenizer.token () [0x0] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.CSharpParser.yyparse (Mono.CSharp.yyParser.yyInput yyLex) [0x0010f] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.CSharpParser.parse () [0x0002e] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 csharp-files/ListOfMembers.cs(120,3): error CS0589: Internal compiler error during parsingSystem.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length at System.String.Substring (System.Int32 startIndex, System.Int32 length) [0x0003a] in :0 at System.String.SplitKeepEmptyEntries (System.ReadOnlySpan`1[T] sepList, System.ReadOnlySpan`1[T] lengthList, System.Int32 defaultLength, System.Int32 count) [0x00049] in :0 at System.String.SplitInternal (System.ReadOnlySpan`1[T] separators, System.Int32 count, System.StringSplitOptions options) [0x000d1] in :0 at System.String.Split (System.Char separator, System.StringSplitOptions options) [0x9] in :0 at Mono.CSharp.Tokenizer.update_formatted_doc_comment (System.Int32 current_comment_start) [0x0002a] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.Tokenizer.xtoken () [0x00b1c] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.Tokenizer.token () [0x0] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.CSharpParser.yyparse (Mono.CSharp.yyParser.yyInput yyLex) [0x0010f] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.CSharpParser.parse () [0x0002e] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 csharp-files/Parameter.cs(126,3): error CS0589: Internal compiler error during parsingSystem.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length at System.String.Substring (System.Int32 startIndex, System.Int32 length) [0x0003a] in :0 at System.String.SplitKeepEmptyEntries (System.ReadOnlySpan`1[T] sepList, System.ReadOnlySpan`1[T] lengthList, System.Int32 defaultLength, System.Int32 count) [0x00049] in :0 at System.String.SplitInternal (System.ReadOnlySpan`1[T] separators, System.Int32 count, System.StringSplitOptions options) [0x000d1] in :0 at System.String.Split (System.Char separator, System.StringSplitOptions options) [0x9] in :0 at Mono.CSharp.Tokenizer.update_formatted_doc_comment (System.Int32 current_comment_start) [0x0002a] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.Tokenizer.xtoken () [0x00b1c] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.Tokenizer.token () [0x0] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.CSharpParser.yyparse (Mono.CSharp.yyParser.yyInput yyLex) [0x0010f] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 at Mono.CSharp.CSharpParser.parse () [0x0002e] in <5ee4ea6b36fa4cf3b3000934ce92985a>:0 csharp-files/SBMLDocument.cs(1221,5): error CS0589: Internal compiler error during parsingSystem.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length at
Bug#926935: tagging 926935
I said: [ lots of things ] Ok, sorry, I didn't want to sound confrontational. Just FYI: The reason this issue makes me to be upset is the discussion that took place here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907829 [ Since you applied buster-ignore here, you might want to apply buster-ignore to such bug as well instead of downgrading as Adrian did. In fact, maybe it would be good news to have it serious and buster-ignore ]. Thanks.
Bug#927295: marked as done (depends on non-available version of grub-common)
Your message dated Wed, 17 Apr 2019 18:53:39 +0100 with message-id <20190417175339.dhdyjewgpxbdr...@riva.ucam.org> and subject line Re: Bug#927295: depends on non-available version of grub-common has caused the Debian Bug report #927295, regarding depends on non-available version of grub-common to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 927295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grub-efi-amd64-bin Version: 1+2.02+dfsg1+16 Severity: serious grub-efi-amd64-bin depends on grub-common_2.02+dfsg1-16 but only grub-common_2.02+dfsg1-17 is available in the archive. Regards, Michael -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-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 grub-efi-amd64-signed depends on: ii grub-common 2.02+dfsg1-16 Versions of packages grub-efi-amd64-signed recommends: pn shim-signed grub-efi-amd64-signed suggests no packages. Versions of packages grub-efi-amd64-bin depends on: ii grub-common 2.02+dfsg1-16 grub-efi-amd64-bin recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- On Wed, Apr 17, 2019 at 04:25:55PM +0200, Michael Biebl wrote: > Package: grub-efi-amd64-bin > Version: 1+2.02+dfsg1+16 That's a version of grub-efi-amd64-signed, not grub-efi-amd64-bin. > grub-efi-amd64-bin depends on grub-common_2.02+dfsg1-16 but only > grub-common_2.02+dfsg1-17 is available in the archive. grub-efi-amd64-signed is a separate source package. Its builds will catch up; and the point of the strict dependency is to make sure they stay in sync in testing, so we don't need an RC bug to avoid that. https://buildd.debian.org/status/package.php?pkg=grub-efi-amd64-signed Thanks, -- Colin Watson [cjwat...@debian.org]--- End Message ---
Processed: retitle 905772 to virtlogd dependency loop causing upgrade failures
Processing commands for cont...@bugs.debian.org: > retitle 905772 virtlogd dependency loop causing upgrade failures Bug #905772 [libvirt] virtlogd dependency loop causing upgrade failures Ignoring request to change the title of bug#905772 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 905772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 905772 to virtlogd dependency loop causing upgrade failures
Processing commands for cont...@bugs.debian.org: > retitle 905772 virtlogd dependency loop causing upgrade failures Bug #905772 [libvirt] virtlogd dependency loop cuaing upgrade failures Changed Bug title to 'virtlogd dependency loop causing upgrade failures' from 'virtlogd dependency loop cuaing upgrade failures'. > thanks Stopping processing here. Please contact me if you need assistance. -- 905772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926935: tagging 926935
Hi. I forgot: The fact that you decided to use buster-ignore here means that it's still ok to use "serious" for these kind of bugs? Thanks.
Bug#926935: tagging 926935
On Sat, 13 Apr 2019, Ivo De Decker wrote: > # buildds have at least 2 CPU cores However, this is still a FTBFS bug in a release architecture (amd64). We are a free software distribution. We don't agree that the end user *must* be able to rebuild the package? For the record: I can build 99.99% of Debian with a single CPU, and only a handful of packages FTBFS with a single CPU. Not 10 and not 100, only a handful. Since VPS providers have small machines where building packages is still cheaper, there is no clear benefit in "deprecating" building in single-CPU machines. So: Could I know please when exactly this started not to be RC, if that's the case? Please state exact date and how many bugs had to be downgraded after the decision was made (AFAIK, this has never happened). Thanks.
Bug#926872: evolution: Spaces in mail view disappeared with recent updates
在 2019-04-17三的 10:55 +，Niels Thykier写道： > Control: tags -1 moreinfo unreproducible > > Hi Boyuan Yang, > > Dominique provided the following message to your bug. However, I am > sure if you have seen it (you were not listed as an explicit CC and the > BTS does not CC submitters by default). > > On Wed, 17 Apr 2019 10:06:22 +0200 Dominique Dumont wrote: > > On Thu, 11 Apr 2019 11:22:46 -0400 Boyuan Yang wrote: > > > A screenshot is provided with the email here. I'm not sure if it can be > > > reproduced by you, but at least this issues appears on all my machines > > > running Debian Sid. > > > > I'm using evolution 3.30.5-1 and cannot reproduce this bug. > > > > Could you check that the mail source does contain the missing white spaces > > ? > > > > Could you reproduce this bug with different font settings ? I found that this will happen when I set the default font to be Noto Sans CJK SC with arbitary font weight. By resetting the font to default, the email viewer would recover back to normal however the composer is always missing spaces no matter how I set up the fonts. It's really a headache if this issue is related to fonts. I'm sending mail copy to debian-fonts list to see if anyone could help. -- Thanks, Boyuan Yang
Bug#926737: marked as done (Possible memory leak after upgrading from 16.1.1 to 16.2.1)
Your message dated Wed, 17 Apr 2019 18:44:22 +0200 with message-id <55b1659a-ab89-b49b-9a83-178a9ed15...@debian.org> and subject line Re: Bug#926737: Possible memory leak after upgrading from 16.1.1 to 16.2.1 has caused the Debian Bug report #926737, regarding Possible memory leak after upgrading from 16.1.1 to 16.2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asterisk Version: 1:16.2.1~dfsg-1 Severity: serious Hi, I intend to look at this myself, but I'm short on time right now. Filing this bug so I don't forget (and maybe someone else can look at it). After having upgraded one of my test systems from 16.1.1 to 16.2.1 shows the Asterisk process being constantly growing until the machine finally runs out of memory. 2019-04-04 16:55:33 upgrade asterisk:amd64 1:16.1.1~dfsg-1 1:16.2.1~dfsg-1 This was a dist-upgrade in a sid container, so it might be something else triggering it, but it is definitely the Asterisk process leaking memory. asterisk 10485 0.3 26.8 964940 271656 ? Ssl Apr08 5:23 /usr/sbin/asterisk -g -f -p -U asterisk Directly after a fresh restart asterisk 11171 15.8 8.0 759704 80928 ?Ssl 19:45 0:03 /usr/sbin/asterisk -g -f -p -U asterisk I'll do some more tests and will followup on this bug. Bernhard --- End Message --- --- Begin Message --- I cannot reproduce this anymore. I have identified two misconfigurations that might have lead to this, as chan_pjsip is known to leak memory in some error handling paths. a) I have a buster container without network namespace on a Stretch host. Asterisk is installed on both. Due to a local misconfiguration the stretch host instance was started as well and the containerized Asterisk could not bind to the source port, permanently logging [2019-04-17 16:41:00] ERROR[14824] res_pjsip.c: Unable to retrieve PJSIP transport 'transport-udp' b) At the same time a libssl1.1 update overwrote (with my consent of course) /etc/ssl/openssl.cnf with the default SECLEVEL=2. I have two upstream peers that run a too small dh key, making Asterisk log SSL SSL_ERROR_SSL (Handshake): Level: 0 err: <337260938> len: 0 every 30 seconds. However, I have reinstated both errors and could not get Asterisk to leak any memory. Hence I'm closing this for now.--- End Message ---
Bug#909750: applications tries to write to /usr/* directories via libfontconfig1
* Niels Thykier [190413 18:28]: > Vincas Dargis: > > On 2019-04-13 12:50, Niels Thykier wrote: > >> What is the status of this bug? AFAICT, we have *some* fixes from > >> upstream but Chris's mail implies that the bug is not completely fixed. > > > > This bug disappeared from my logs long time ago, at least haven't seen > > any application reproducing it so far. > > Interestingly, Chris (just Cc'ed) claims to have reproduced it about a > week ago with libfontconfig1:amd64 using strace and to my knowledge > libfontconfig1 hasn't changed for months in sid/buster. > > @Chris: Just to confirm: Do you still see the issue? I've given this another try, and can hopefully shed some light: In a local X session with fluxbox, I don't see the EACCESS in strace. In an ssh session with X11 forwarding to an XQuartz server, I still get the EACCESS. Couldn't try with a remote Xorg server though, maybe someone else can verify this. Chris
Processed: affects 927245
Processing commands for cont...@bugs.debian.org: > affects 927245 - jtb Bug #927245 [src:caveconverter] caveconverter: obsolete d/javabuild points to non-existant directory Removed indication that 927245 affects jtb > thanks Stopping processing here. Please contact me if you need assistance. -- 927245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927243: marked as done (jtb: Obsolete and unused jh_build + d/javabuild references non-existant dir causing FTBFS)
Your message dated Wed, 17 Apr 2019 14:33:50 + with message-id and subject line Bug#927243: fixed in jtb 1.4.12-2 has caused the Debian Bug report #927243, regarding jtb: Obsolete and unused jh_build + d/javabuild references non-existant dir causing FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 927243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jtb Version: 1.4.12-1.1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper dh_update_autotools_config -i dh_auto_configure -i jh_linkjars -i dh_auto_build -i ant -Duser.name debian Buildfile: /<>/build.xml echo_jtb_props: [echo] jtb_proj_dir=/<> [echo] jtb_last_version=1.4.11 [echo] jtb_curr_version=1.4.12 [echo] jtb_bs_jar=/<>/lib/jtb132.jar [echo] jtblv=/<>/lib/jtb-1.4.11.jar [echo] jtb_last_jar=/<>/lib/jtb-1.4.11.jar [echo] jtb_new_jar=/<>/lib/new_jtb-1.4.12.jar [echo] jtb_prev_jar=/<>/lib/jtb-1.4.12.jar [echo] jtb_ok_jar=/<>/lib/jtb-1.4.12.jar echo_javacc_props: [echo] javacc_imp_dir=/usr/share/maven-repo/net/java/dev/javacc/javacc/debian [echo] javacc_ok_jar=/usr/share/maven-repo/net/java/dev/javacc/javacc/debian/javacc-debian.jar [echo] javacc_main=org.javacc.parser.Main echo_all_props: clean_javacc_gen_files: clean_jtb_gen_files: clean_all_gen_files: process_jtbgram.jtb: [java] JTB version 1.4.12 [java] JTB: Reading jtb input file /<>/src/EDU/purdue/jtb/jtbgram.jtb... [java] JTB: jtb input file parsed successfully. [java] JTB: jj output file "/<>/src/EDU/purdue/jtb/jtb.out.jj" generated. [java] JTB: base node class files generated into directory "/<>/src/EDU/purdue/jtb/syntaxtree". [java] JTB: 134 syntax tree node class files generated into directory "/<>/src/EDU/purdue/jtb/syntaxtree". [java] [java] JTB: Visitor interface "IRetArguVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor interface "IVoidVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor interface "IRetVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor interface "IVoidArguVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor class "DepthFirstRetArguVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor class "DepthFirstRetVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor class "DepthFirstVoidArguVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] JTB: Visitor class "DepthFirstVoidVisitor.java" generated into directory "/<>/src/EDU/purdue/jtb/visitor". [java] process_jtb.out.jj: [java] Java Compiler Compiler Version 5.0 (Parser Generator) [java] (type "javacc" with no arguments for help) [java] Reading from file /<>/src/EDU/purdue/jtb/jtb.out.jj . . . [java] Warning: Line 119, Column 1: Command line setting of "OUTPUT_DIRECTORY" modifies option value in file. [java] File "TokenMgrError.java" does not exist. Will create one. [java] File "ParseException.java" does not exist. Will create one. [java] File "Token.java" does not exist. Will create one. [java] File "JavaCharStream.java" does not exist. Will create one. [java] Parser generated with 0 errors and 1 warnings. copy_specific_token_for_jtb: [copy] Copying 1 file to /<>/src/EDU/purdue/jtb/parser generate_all: generate_all+compile_java: compile_java: [javac] Compiling 234 source files to /<>/bin [javac] warning: [options] bootstrap class path not set in conjunction with -source 7 [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 1 warning build_new_jtb_jar: check_jtb_jar: make_new_jtb_jar: [jar] Building jar: /<>/lib/new_jtb-1.4.12.jar test_process_jtbgram.jtb: [java] JTB version 1.4.12 [java] JTB: Reading jtb input file /<>/src/EDU/purdue/jtb/jtbgram.jtb... [java] java.lang.NullPointerException [java] at EDU.purdue.jtb.parser.JTBToolkit.makeNodeToken(JTBParser.java:12271) [java]
Bug#926885: marked as done (lighttpd: CVE-2019-11072)
Your message dated Wed, 17 Apr 2019 14:33:59 + with message-id and subject line Bug#926885: fixed in lighttpd 1.4.53-4 has caused the Debian Bug report #926885, regarding lighttpd: CVE-2019-11072 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lighttpd Version: 1.4.53-3 Severity: grave Tags: security upstream Forwarded: https://redmine.lighttpd.net/issues/2945 Hi, The following vulnerability was published for lighttpd. CVE-2019-11072[0]: | lighttpd before 1.4.54 has a signed integer overflow, which might | allow remote attackers to cause a denial of service (application | crash) or possibly have unspecified other impact via a malicious HTTP | GET request, as demonstrated by mishandling of /%2F? in | burl_normalize_2F_to_slash_fix in burl.c. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-11072 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11072 [1] https://redmine.lighttpd.net/issues/2945 [2] https://github.com/lighttpd/lighttpd1.4/commit/32120d5b8b3203fc21ccb9eafb0eaf824bb59354 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: lighttpd Source-Version: 1.4.53-4 We believe that the bug you reported is fixed in the latest version of lighttpd, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Glenn Strauss (supplier of updated lighttpd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Apr 2019 00:00:00 -0400 Source: lighttpd Architecture: source Version: 1.4.53-4 Distribution: unstable Urgency: high Maintainer: Debian QA Group Changed-By: Glenn Strauss Closes: 926885 Changes: lighttpd (1.4.53-4) unstable; urgency=high . * QA upload. * fix mixed use of srv->split_vals array (regression) * mod_magnet:fix invalid script return-type crash * fix assertion with server.error-handler * mod_wstunnel:fix wstunnel.ping-interval for big-endian architectures * fix abort in server.http-parseopts with url-path-2f-decode enabled CVE-2019-11072 (closes: #926885) Checksums-Sha1: b609f87fcac5281e0dea93b72ba74b9db2fe0a24 3879 lighttpd_1.4.53-4.dsc b79ba0fa89ad031f0fe979a2bd6d0667390459b7 44060 lighttpd_1.4.53-4.debian.tar.xz 5b34212f522882d440645fc8636cd8d68265e282 16638 lighttpd_1.4.53-4_amd64.buildinfo Checksums-Sha256: d496e9a6879a70451402d8a19f0396e781dc00fc902c9bf0b567c6c8b6b63257 3879 lighttpd_1.4.53-4.dsc b11b1ff4831671cc67da207009d5cb9dac71fea5b17ac10144a980cb5903dcc4 44060 lighttpd_1.4.53-4.debian.tar.xz c70fdd421bf1240ca925390e01c9cd14a4c121dfab3d4c6a215175fabdcb1eb0 16638 lighttpd_1.4.53-4_amd64.buildinfo Files: f0d901e9c6b3d9ab91179b4d54567aa4 3879 httpd optional lighttpd_1.4.53-4.dsc f0b909359a42999d57044af80513cc39 44060 httpd optional lighttpd_1.4.53-4.debian.tar.xz ebed16c45ec61b788fb19f1696944831 16638 httpd optional lighttpd_1.4.53-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAly3KT8ACgkQLRqqzyRE REKqlQ//URCooawWK1Z5e1/RRYLF8DBPyahxrI2DEJG83Xp9ikdVy1+0KAGfdTOC yOJY9trdRuek7liGr4mKu+fIeF4Mj12eoz9QV6678A4VuegdgRiPWGbWN6Nc3xlV jP2Z9j+RVBXU59v3SdAYTDeUBindqk7P5qGl8YtLS0Asub4cGVX1MmmI2sv/Lk/A ihdQvXFeaN8VnbF/0Um5cnzEL3gh+Z/oEo6YnGxn6FVUG/ZJ6vFAvUwkLOuIIvkO Qh4JeJ5c0ujJHYa6b7zQIRobQBsUVWh3K6AZ6plVqE10YdSt+3yG2/Cgmc5YfqdC MVmzkGe6UdNKHua09YEFkSbmIynfHIVwUJytylv0pryl4TTKv1ZKnJeO5a9Mw9Vq UuffUZEwLwtwnevYyu8ycp7IVip7lor04JmQFUa6vqpW2MdS9OEEeRtRDWjWlGdM yAhMKHvz2PAMUROnpztgLHDvtSHv8WYsCuo5dk92FCq9amgG3gwtvsxvhPGge9k3 owIhbeblxtopj8geyQtk0G714+Olrpq77ZjlszE1HHATH2hMIziXPy6haieJxZ3Q uJnpmRW1AX4ovWM4g2jxo0K0wyyflMG4YMX0jken0XTiA+pkF+QQQPlEAm+i32nf Pt5cQxrt/m5+ncC8iZ/beTPdNPYQWXM3/Yt1zDP77pY9GuUaWZk= =ZGri -END PGP SIGNATURE End Message ---
Bug#927295: depends on non-available version of grub-common
Package: grub-efi-amd64-bin Version: 1+2.02+dfsg1+16 Severity: serious grub-efi-amd64-bin depends on grub-common_2.02+dfsg1-16 but only grub-common_2.02+dfsg1-17 is available in the archive. Regards, Michael -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-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 grub-efi-amd64-signed depends on: ii grub-common 2.02+dfsg1-16 Versions of packages grub-efi-amd64-signed recommends: pn shim-signed grub-efi-amd64-signed suggests no packages. Versions of packages grub-efi-amd64-bin depends on: ii grub-common 2.02+dfsg1-16 grub-efi-amd64-bin recommends no packages. -- no debconf information
Bug#927292: libqb: Breaks applications not running as root (for example pacemaker-based AKA cib)
Source: libqb Version: 1.0.4-1 Severity: grave Tags: upstream Justification: renders package unusable Forwarded: https://github.com/ClusterLabs/libqb/issues/338 IPC connection setup is aborted if the application is unable to chown() the temporary communication directory under /dev/shm to the credentials of the client. This can happen if the application isn't running as root, but isn't necessarily fatal if the client has appropriate privileges.
Bug#927142: cyrus-imapd: Cyrus 3 segfaults when attempting to deliver mail via lmtp
Hello, once again a small update: 1) I was able to trace our vacation issues to a problem on our end. This won't be relevant to Debian. 2) The squatter issue I referred to earlier is odd and reproducible, but probably an upstream issue: busternt.kim.mein-iserv.de ~ # /usr/sbin/cyrus squatter -u kim.brodowski cyrus/squatter[17830]: indexing mailboxes cyrus/squatter[17830]: indexing mailbox user/kim.brodowski... cyrus/squatter[17830]: indexing mailbox user/kim.brodowski/Drafts... cyrus/squatter[17830]: indexing mailbox user/kim.brodowski/Junk... cyrus/squatter[17830]: indexing mailbox user/kim.brodowski/Sent... cyrus/squatter[17830]: indexing mailbox user/kim.brodowski/Trash... cyrus/squatter[17830]: done indexing mailboxes busternt.kim.mein-iserv.de ~ # /usr/sbin/cyrus squatter user/kim.brodowski/Sent cyrus/squatter[19346]: indexing mailboxes cyrus/squatter[19346]: indexing mailbox user/kim.brodowski/Sent... cyrus/squatter[19346]: done indexing mailboxes busternt.kim.mein-iserv.de ~ # /usr/sbin/cyrus squatter user/kim^brodowski fatal error: Internal error: assertion failed: lib/cyrusdb_twoskip.c: 2339: keylen Compared to Stretch: stable.iserv.eu /etc # /usr/sbin/cyrus squatter user/kim.brodowski -v Indexing mailbox user/kim.brodowski... Indexed 401 messages (7007950 bytes) into 942379 index bytes in 0 seconds stable.iserv.eu /etc # /usr/sbin/cyrus squatter user/kim^brodowski -v Indexing mailbox user/kim.brodowski... Indexed 401 messages (7007950 bytes) into 942379 index bytes in 0 seconds Depending on how squatter is called it'll crash. This is relevant to us because of a different bug that'll cause squatter to fail creating it's index on i386 systems when user mailboxes are too big and the squat file exceeds 2 147 483 647 bytes. As a workaround - so that at the very least some folders can be searched - we call squatter for each folder individually. Since there is a workaround by replacing the ^ character with the . character in squatter calls this isn't a major issue right now. -- Kind regards, Kim-Alexander Brodowski IServ GmbH Bültenweg 73 38106 Braunschweig Telefon: +49 531 22 43 666-0 Mobil: +49 152 55 17 55 16 Fax: +49 531 22 43 666-9 E-Mail:kim.brodow...@iserv.eu Internet: https://iserv.eu USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822 Geschäftsführer: Benjamin Heindl, Martin Hüppe, Jörg Ludwig
Bug#925546: How to reproduce?
Hi, Hilko Bengen: > I can get rid of the issues by backporting a number of commits from > github.com/nsf/gocode and will submnit an updated package for > stretch-proposed-updates. Thanks for investigating. > Are you able to build .deb packages from source or should I provide a > binary package for you to test? I can build from source. Joonas
Bug#818366: synaptic: fails to start under Wayland
Great thank you
Bug#926928: fetchmail: Server CommonName mismatch
Thanks for your answer. I have replaced pop.nerim.fr by pop.nerim.net and it works as expected. This configuration worked fine with pop.nerim.fr for a very long time until last upgrade of feetchmail. Best regards, JB
Processed: Re: Bug#926215: dune-pdelab: FTBFS with gcc 8.3
Processing control commands: > reassign -1 src:dune-pdelab 2.6~20180302-1 Bug #926215 [src:dune-istl] dune-pdelab: FTBFS with gcc 8.3 Bug reassigned from package 'src:dune-istl' to 'src:dune-pdelab'. No longer marked as found in versions dune-istl/2.6.0-2. Ignoring request to alter fixed versions of bug #926215 to the same values previously set Bug #926215 [src:dune-pdelab] dune-pdelab: FTBFS with gcc 8.3 Marked as found in versions dune-pdelab/2.6~20180302-1. > retitle -1 dune-pdelab: testpk fails with assertion failure Bug #926215 [src:dune-pdelab] dune-pdelab: FTBFS with gcc 8.3 Changed Bug title to 'dune-pdelab: testpk fails with assertion failure' from 'dune-pdelab: FTBFS with gcc 8.3'. -- 926215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926215: dune-pdelab: FTBFS with gcc 8.3
Control: reassign -1 src:dune-pdelab 2.6~20180302-1 Control: retitle -1 dune-pdelab: testpk fails with assertion failure On Mon, 2019-04-08 at 08:42 +0200, Ansgar Burchardt wrote: > This is a bug in dune-istl, though I'm not quite sure I understand > what > is exactly wrong. Renaming the template argument from `T` to `T1` in > the definition of `prolongateVector` makes the problem go away, but the > name of template arguments shouldn't really matter? > > There is also a template argument `T` in the generic version of the > `Transfer` class... Maybe that results in the confusion in some way? That problem went away with a GCC update, but there is still a problem with a test in dune-pdelab that now fails... Not sure yet if the problem is in dune-grid or dune-pdelab for that one, reassigning to dune-pdelab for now: +--- | check_mesh: checking mesh 'DUNE AlbertaGrid' | checking done; no error detected | AlbertaGrid< 2, 2 > created from macro grid file '/<>/dune/pdelab/test/grids/ldomain.al'. | GridParameterBlock: Parameter 'refinementedge' not specified, defaulting to 'ARBITRARY'. | testpk: /build/dune-grid-yp9bpw/dune-grid-2.6.0/dune/grid/albertagrid/elementinfo.hh:488: bool Dune::Alberta::ElementInfo::isLeaf() const [with int dim = 2]: Assertion `!(*this) == false' failed. +--- Ansgar
Bug#925546: How to reproduce?
Joonas, I can get rid of the issues by backporting a number of commits from github.com/nsf/gocode and will submnit an updated package for stretch-proposed-updates. Are you able to build .deb packages from source or should I provide a binary package for you to test? Cheers, -Hilko
Processed: Re: evolution: Spaces in mail view disappeared with recent updates
Processing control commands: > tags -1 moreinfo unreproducible Bug #926872 [evolution] evolution: Spaces in mail view disappeared with recent updates Added tag(s) moreinfo and unreproducible. -- 926872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926872: evolution: Spaces in mail view disappeared with recent updates
Control: tags -1 moreinfo unreproducible Hi Boyuan Yang, Dominique provided the following message to your bug. However, I am sure if you have seen it (you were not listed as an explicit CC and the BTS does not CC submitters by default). On Wed, 17 Apr 2019 10:06:22 +0200 Dominique Dumont wrote: > On Thu, 11 Apr 2019 11:22:46 -0400 Boyuan Yang wrote: > > A screenshot is provided with the email here. I'm not sure if it can be > > reproduced by you, but at least this issues appears on all my machines > > running Debian Sid. > > I'm using evolution 3.30.5-1 and cannot reproduce this bug. > > Could you check that the mail source does contain the missing white spaces ? > > Could you reproduce this bug with different font settings ? > > All the best > > Thanks, ~Niels
Processed: Re: Bug#927142: cyrus-imapd: Cyrus 3 segfaults when attempting to deliver mail via lmtp
Processing control commands: > severity -1 serious Bug #927142 [cyrus-imapd] cyrus-imapd: Cyrus 3 segfaults when attempting to deliver mail via lmtp Severity set to 'serious' from 'important' -- 927142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 927243 to src:jtb ...
Processing commands for cont...@bugs.debian.org: > reassign 927243 src:jtb Bug #927243 [javahelper] jh_build: Regression in handling directories in d/javabuild Bug reassigned from package 'javahelper' to 'src:jtb'. Ignoring request to alter found versions of bug #927243 to the same values previously set Ignoring request to alter fixed versions of bug #927243 to the same values previously set > retitle 927243 jtb: Obsolete and unused jh_build + d/javabuild references > non-existant dir causing FTBFS Bug #927243 [src:jtb] jh_build: Regression in handling directories in d/javabuild Changed Bug title to 'jtb: Obsolete and unused jh_build + d/javabuild references non-existant dir causing FTBFS' from 'jh_build: Regression in handling directories in d/javabuild'. > thanks Stopping processing here. Please contact me if you need assistance. -- 927243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925483: tilda: does not start (segfault) (under Wayland)
Hi, Upstream has a workaround for this crash at [1], you might want to use it as a patch. Also this report can be probably merged with [2]. [1] https://github.com/lanoxx/tilda/commit/daa64f579b4d544cb7da614612f1d35c461b43be [2] https://bugs.debian.org/904309
Processed: unmerging 927245, reassign 927245 to src:caveconverter ...
Processing commands for cont...@bugs.debian.org: > unmerge 927245 Bug #927245 [javahelper] caveconverter: FTBFS (jh_build: Cannot find "caveconverter") Bug #927243 [javahelper] jh_build: Regression in handling directories in d/javabuild Disconnected #927245 from all other report(s). > reassign 927245 src:caveconverter Bug #927245 [javahelper] caveconverter: FTBFS (jh_build: Cannot find "caveconverter") Bug reassigned from package 'javahelper' to 'src:caveconverter'. Ignoring request to alter found versions of bug #927245 to the same values previously set Ignoring request to alter fixed versions of bug #927245 to the same values previously set > retitle 927245 caveconverter: obsolete d/javabuild points to non-existant > directory Bug #927245 [src:caveconverter] caveconverter: FTBFS (jh_build: Cannot find "caveconverter") Changed Bug title to 'caveconverter: obsolete d/javabuild points to non-existant directory' from 'caveconverter: FTBFS (jh_build: Cannot find "caveconverter")'. > thanks Stopping processing here. Please contact me if you need assistance. -- 927243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927243 927245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927275: gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot
Package: gnome-shell Version: 3.30.2-3 Severity: serious Device: Thinkpad L390 Debian Version: Buster with latest updates After a fresh install, arranging all monitors in gnome-settings and saving the changes the setup works on both sides (office and home) with two same dockingstations (Thinkpad Thunderbolt 3 Dock Gen 2) and different monitor settings at each side. All monitors are placed correctly and the internal screen is off, as it was defined in gnome settings before, see attached monitors.xml But after disconnecting the dockingstation, suspend the laptop and change the location, wake it up and connecting to the other dock, the settings are not applied again, just the default display arrangement (all three in one row, from left to right). Even a reboot, or another suspend while beeing connected to the dockingstation is not solving it. There is no way to get the correct saved options applied again which have been working before. It seems gnome-shell is not reading in the monitors.xml where the correct settings are applied and stored for each side after a suspend or even a reboot. Any idea what is causing this issue and what could be a workaround for now to trigger a manual reading of the monitors.xml so that it can be applied manually as a temporary fix? best regards Christian Höffer monitors.xml Description: XML document
Bug#927244: marked as done (mina: FTBFS (Unknown option: source 1.7 -target 1.7))
Your message dated Wed, 17 Apr 2019 08:34:24 + with message-id and subject line Bug#927244: fixed in mina 1.1.7.dfsg-13 has caused the Debian Bug report #927244, regarding mina: FTBFS (Unknown option: source 1.7 -target 1.7) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 927244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mina Version: 1.1.7.dfsg-12 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper dh_update_autotools_config -i dh_autoreconf -i jh_linkjars -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>' # Build the packages ( CLASSPATH=/usr/share/java/slf4j-api.jar jh_build -J -o"-source 1.7 -target 1.7" mina-core.jar core/src/main/java/ ) Unknown option: source 1.7 -target 1.7 jh_build: unknown option or error during option parsing; aborting make[1]: *** [debian/rules:43: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:39: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mina.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: mina Source-Version: 1.1.7.dfsg-13 We believe that the bug you reported is fixed in the latest version of mina, 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 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated mina package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Apr 2019 09:56:32 +0200 Source: mina Architecture: source Version: 1.1.7.dfsg-13 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 889352 927244 Changes: mina (1.1.7.dfsg-13) unstable; urgency=medium . * Team upload. * Fixed the build failure with javahelper 0.72 (Closes: #927244) * Removed Damien Raude-Morvan from the uploaders (Closes: #889352) * Use salsa.debian.org Vcs-* URLs Checksums-Sha1: cfac90082116ecd1d03c702f9f8731edb2b3354e 2097 mina_1.1.7.dfsg-13.dsc b5f040988bc2d24e17167478d0d477c67c4dec52 4764 mina_1.1.7.dfsg-13.debian.tar.xz 2f1f7ff0c2ee839ec2cabc4eaba84641db23a051 12847 mina_1.1.7.dfsg-13_source.buildinfo Checksums-Sha256: 3962d4cf018e7ff6a3bc5f27efa5563cff1c32f7ebc96d6034972234976ff4dd 2097 mina_1.1.7.dfsg-13.dsc 4468c73d39ac6bcc5fdc968b8bf698b0cfda5ebe9af4935fac5eeb7a44a91b00 4764 mina_1.1.7.dfsg-13.debian.tar.xz 770edabb1154825e2a589e47af32efd8bd8e66913fd0461a0c86e02e31ad5a4f 12847 mina_1.1.7.dfsg-13_source.buildinfo Files: 2039d44f51175265ae8f776eb39fbd83 2097 java optional mina_1.1.7.dfsg-13.dsc ddad1d51b29d5f1f76515eb79f42ff5c 4764 java optional mina_1.1.7.dfsg-13.debian.tar.xz 1aafd238837e1c6bd2cd5b13b6203c96 12847 java optional mina_1.1.7.dfsg-13_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAly23OYSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsg0gQAJIiwQy6mo6GsNd6UMbb2CGJmbA/fetf vTWb3cVO7D/CPBtLk8xzluOc4NoSrTlz3HIuu8hwK+bVkPHaydKyzHyS9cTCm2f8 jlRGu1dYGK4DyhhYYsnt/sUlWhuR8KoRr5DZ4mdeKuSSidD698xNCSY9znZjNnWX qNyxvbJwGGB5qIiD5NSDbQpX91z+7WF2yBXt3yr2hyJ0mDBpEXaB2aINJhG08/hp LUy797NCfNdBKma2fHgjqeSsBZPvrFPiq235ibHdCRIdYuDfg+Ng2qD9yk1xlVfz NKnGIk3IgqaFep9HVQXSaGfcinFCg3i+5NDZ/MosydtGQTyWisos1L0hR5h7D49W OZmgG6tcUzWICFb04qT4zry3O1JZHwHHyQFq1CoFp807KjHmSbrGLdCptyFZuPzy FCZzDE/+7Rh8h7C9dQtq4mYoCKs+Lshg7ooVuSMKjEivB8ITJNszyMmeTh+FexQY 5TOQqVg3JdTF7Lxi5W817f8qehbsPRhVAErzABXFBkXfmsn3z3+LE566BFC6WlLl
Bug#926872: evolution: Spaces in mail view disappeared with recent updates
On Thu, 11 Apr 2019 11:22:46 -0400 Boyuan Yang wrote: > A screenshot is provided with the email here. I'm not sure if it can be > reproduced by you, but at least this issues appears on all my machines > running Debian Sid. I'm using evolution 3.30.5-1 and cannot reproduce this bug. Could you check that the mail source does contain the missing white spaces ? Could you reproduce this bug with different font settings ? All the best
Processed: Bug #927244 in mina marked as pending
Processing control commands: > tag -1 pending Bug #927244 [src:mina] mina: FTBFS (Unknown option: source 1.7 -target 1.7) Added tag(s) pending. -- 927244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927244: Bug #927244 in mina marked as pending
Control: tag -1 pending Hello, Bug #927244 in mina reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/mina/commit/3cf6af5c1f789d8b84c08239e37d22e76bf96381 Fixed the build failure with javahelper 0.72 (Closes: #927244) (this message was generated automatically) -- Greetings https://bugs.debian.org/927244
Bug#857208: marked as done (socklog: building with -A doesn't put the changelog in usr/share/doc/socklog-run/changelog.Debian.gz)
Your message dated Wed, 17 Apr 2019 07:52:42 + with message-id and subject line Bug#857208: fixed in socklog 2.1.0+repack-1 has caused the Debian Bug report #857208, regarding socklog: building with -A doesn't put the changelog in usr/share/doc/socklog-run/changelog.Debian.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 857208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: socklog Version: 2.1.0-8 Severity: serious building binary-indep with dpkg-buildpackage -A leads to changelog.Debian to be renamed to just changelog, as this code in debian/implicit does the wrong thing: @sh -cx 'install -m0644 debian/changelog \ debian/$*/usr/share/doc/$*/changelog.Debian' @test ! -r changelog || \ sh -cx 'install -m0644 changelog debian/$*/usr/share/doc/$*/' @test -r debian/$*/usr/share/doc/$*/changelog || \ sh -cx 'mv debian/$*/usr/share/doc/$*/changelog.Debian \ debian/$*/usr/share/doc/$*/changelog' I couldn't completely get what was going on and why this is not happening during a full or arch-dep build, and I refuse to wrap my mind around that make for more than 2 minutes. In any case, this could easily be fixed by shipping that tarball unpacked properly, and switching to debhelper….. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: socklog Source-Version: 2.1.0+repack-1 We believe that the bug you reported is fixed in the latest version of socklog, 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 857...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Mirmont (supplier of updated socklog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Apr 2019 00:24:26 +0200 Source: socklog Architecture: source Version: 2.1.0+repack-1 Distribution: experimental Urgency: medium Maintainer: Mathieu Mirmont Changed-By: Mathieu Mirmont Closes: 668718 834089 857208 907092 Changes: socklog (2.1.0+repack-1) experimental; urgency=medium . * uscan: add watch file and repack.sh script * New upstream version 2.1.0+repack * Convert the package to debhelper (Closes: #857208) * patch: socklog-conf(8): refer to update-service(8) * patch: tryto.c: don't fail if the final try succeeds * socklog-run: migrate to dh-runit (Closes: #668718, #834089) * Merge socklog and socklog-run * source/lintian-overrides: no https upstream * doc-base: register the html documentation * copyright: convert to DEP-5 format * gitlab-ci.yml: add GitLab CI file * patch: Makefile: bypass the chkshsgr test in CI * Add sysv init scripts * control: update the Vcs fields * control: new maintainer (Closes: #907092) Checksums-Sha1: 702e73ba0ddfe1650e0bb9e201e0f60085ba203f 1974 socklog_2.1.0+repack-1.dsc dafd279c26942a8f34184aeec3f3780db3788a3d 59796 socklog_2.1.0+repack.orig.tar.gz dd6550d95979983e131967fa9b71277110708226 10080 socklog_2.1.0+repack-1.debian.tar.xz 26d10ea1bb6d4d59e672f2a989e556911096225e 5214 socklog_2.1.0+repack-1_source.buildinfo Checksums-Sha256: 0a7833514825931a6bc54fdcc6a3105c3e956aec6a27719fe2201f7f5b1ba779 1974 socklog_2.1.0+repack-1.dsc 80c0b73e6409b06748026dd3d26276fea29b78b1bd145a748e4a4c04cdf769f7 59796 socklog_2.1.0+repack.orig.tar.gz bb61ca3e50807f062372a6f9eb0da126c1c02a615a07c2bc98c5d145f5ba1713 10080 socklog_2.1.0+repack-1.debian.tar.xz 0a35fa8e9834d730526b92b3b98f56d2ac3e16c0b4aea80242889dee927c9e08 5214 socklog_2.1.0+repack-1_source.buildinfo Files: 63d65fa3cc08e887907590ea54724711 1974 admin optional socklog_2.1.0+repack-1.dsc 936848fc4531da3882ace2b9309fbac2 59796 admin optional socklog_2.1.0+repack.orig.tar.gz
Bug#834089: marked as done (runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory)
Your message dated Wed, 17 Apr 2019 07:52:42 + with message-id and subject line Bug#834089: fixed in socklog 2.1.0+repack-1 has caused the Debian Bug report #834089, regarding runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 834089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: runit Version: 2.1.2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package bcron-run. (Reading database ... (Reading database ... 6995 files and directories currently installed.) Preparing to unpack .../bcron-run_0.10-3_all.deb ... Unpacking bcron-run (0.10-3) ... Setting up bcron-run (0.10-3) ... Installing new version of config file /etc/crontab ... Adding system user `cron' (UID 151) ... Adding new group `cron' (GID 152) ... Adding new user `cron' (UID 151) with group `cron' ... Not creating home directory `/var/spool/cron'. Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory Adding system user `cronlog' (UID 152) ... Adding new user `cronlog' (UID 152) with group `nogroup' ... Not creating home directory `/nonexistent'. ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory dpkg: error processing package bcron-run (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: bcron-run Similar problems were seen in different *-run packages. cheers, Andreas bcron-run_0.10-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: socklog Source-Version: 2.1.0+repack-1 We believe that the bug you reported is fixed in the latest version of socklog, 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 834...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Mirmont (supplier of updated socklog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Apr 2019 00:24:26 +0200 Source: socklog Architecture: source Version: 2.1.0+repack-1 Distribution: experimental Urgency: medium Maintainer: Mathieu Mirmont Changed-By: Mathieu Mirmont Closes: 668718 834089 857208 907092 Changes: socklog (2.1.0+repack-1) experimental; urgency=medium . * uscan: add watch file and repack.sh script * New upstream version 2.1.0+repack * Convert the package to debhelper (Closes: #857208) * patch: socklog-conf(8): refer to update-service(8) * patch: tryto.c: don't fail if the final try succeeds * socklog-run: migrate to dh-runit (Closes: #668718, #834089) * Merge socklog and socklog-run * source/lintian-overrides: no https upstream * doc-base: register the html documentation * copyright: convert to DEP-5 format * gitlab-ci.yml: add GitLab CI file * patch: Makefile: bypass the chkshsgr test in CI * Add sysv init scripts * control: update the Vcs fields * control: new maintainer (Closes: #907092) Checksums-Sha1: 702e73ba0ddfe1650e0bb9e201e0f60085ba203f 1974 socklog_2.1.0+repack-1.dsc dafd279c26942a8f34184aeec3f3780db3788a3d 59796 socklog_2.1.0+repack.orig.tar.gz dd6550d95979983e131967fa9b71277110708226 10080 socklog_2.1.0+repack-1.debian.tar.xz 26d10ea1bb6d4d59e672f2a989e556911096225e 5214 socklog_2.1.0+repack-1_source.buildinfo Checksums-Sha256: 0a7833514825931a6bc54fdcc6a3105c3e956aec6a27719fe2201f7f5b1ba779 1974 socklog_2.1.0+repack-1.dsc 80c0b73e6409b06748026dd3d26276fea29b78b1bd145a748e4a4c04cdf769f7 59796 socklog_2.1.0+repack.orig.tar.gz bb61ca3e50807f062372a6f9eb0da126c1c02a615a07c2bc98c5d145f5ba1713 10080 socklog_2.1.0+repack-1.debian.tar.xz
Bug#926392: licensecheck chokes on long lines
On Thu, 04 Apr 2019 18:13:43 +0200 Jonas Smedegaard wrote:
> control: tag -1 confirmed
>
> Quoting Sandro Mani (2019-04-04 13:36:28)
> > $ wget
> > https://files.pythonhosted.org/packages/source/x/xonsh/xonsh-0.8.12.tar.gz
> > $ tar xf xonsh-0.8.12.tar.gz
> > $ licensecheck xonsh-0.8.12/xonsh/parser_table.py
> >
> > => Licensecheck hangs eating cpu cycles (the file has lines with 33k and
> > 71k characters).
>
> Indeed. Thanks for reporting!
>
> - Jonas
>
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
>
> [x] quote me freely [ ] ask before reusing [ ] keep private
Hi,
I have been digging in the code (admittedly using the master branch of
the libregexp-pattern-license-perl and licensecheck rather than the
packages) and basically, it is a DOS from suboptimal regex.
I traced it down to getting stuck on the python_2 "grant_license". This
regex expands to (manually reformatted with /x for readability):
"""
m!
(?^:
(?:
(?: (?:[Ll]icensed|[Rr]eleased) [ ] under|(?:according [ ] to|as
[ ] governed [ ] by|under) [ ] the [ ] (?:conditions|terms)
[ ] of)(?:(?:[Tt]he [ ] )?Python-2.0
| (?:[Tt]he [ ])?Python(?: [ ] [Ll]icense)? [ ] 2.0
| (?:[Tt]he [ ])?Python-2.0
| (?:[Tt]he [ ])?Python [ ] Software [ ]
Foundation(?: [ ] [Ll]icense)? [ ] version [ ] 2
| (?:[Tt]he [ ])?python2
| (?:[Tt]he [ ])?Python-2
| (?:[Tt]he [ ])?PSF-2
| (?:[Tt]he [ ])?Python(?: [ ] [Ll]icense)? [ ] Version [ ] 2
| (?:[Tt]he [ ])?PYTHON [ ] SOFTWARE [ ] FOUNDATION [ ] LICENSE [
] VERSION [ ] 2
| (?:[Tt]he [ ])?python-license-2.0)
| (?:\W*\S+\W*)PSF [ ] is [ ] making [ ] Python [ ] available [ ]
to [ ] Licensee
)
)
!x
"""
The problem is the *last* alternative, namely:
"""
(?:\W*\S+\W*)PSF [ ] is [ ] making [ ] [...]
"""
That \W*\S+\W* (known as ${BB} in the libregexp-pattern-license-perl
code) is stirring up hell. Basically, perl wants to find the *longest*
match and will spent stupid amount of time in this "trivial" regex
enumerating exponentially many "non-matches" ([1] strikes again).
Simply removing ${BB} will make the code continue past the python_2 test
relatively fast. For the python_2 case, I think that the phrase "PSF
is making Python available to Licensee" would be sufficient enough to
consider it a match (i.e. ${BB} is redundant) - though it will change
behaviour on an anchored match (I hope this is not a problem).
Though it then gets stuck in the next regex "cube" (from
@L_type_unversioned) and that is as far down the rabbit hole I ventured
in terms of regex getting stuck (note that "cube" indirectly uses the
$BB regex too).
Thanks,
~Niels
[1] https://swtch.com/~rsc/regexp/regexp1.html
