Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?
For me there are still issues with 3.16.0-8-amd64 after updating to 3.16.64-2, so I have to still run some machines on 3.16.0-7 to have them working. After boot dmesg gives output like attached. Software stack which has a problem with this is postfix/rspamd/redis. Redis does consume a lot of CPU and postfix is not able to pass mails to rspamd using milter interface. postfix/smtpd[884]: warning: milter inet:localhost:11332: can't read SMFIC_OPTNEG reply packet header: Connection timed out postfix/smtpd[2999]: warning: milter inet:localhost:11332: read error in initial handshake Downgrading to 3.16.0-7-amd64 3.16.59-1 does fix this issue. [ 313.994685] BUG: unable to handle kernel paging request at 8823300a1998 [ 313.994737] IP: [] put_pid+0x12/0x50 [ 313.994776] PGD 1b11067 PUD 0 [ 313.994799] Oops: [#1] SMP [ 313.994822] Modules linked in: xt_multiport ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_comment xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables ppdev bochs_drm ttm drm_kms_helper evdev drm joydev pcspkr serio_raw shpchp virtio_balloon parport_pc processor parport thermal_sys button autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid dm_mod virtio_blk virtio_net sg sr_mod cdrom ata_generic psmouse uhci_hcd ehci_hcd virtio_pci virtio_ring virtio i2c_piix4 i2c_core usbcore usb_common floppy ata_piix libata scsi_mod [ 313.995268] CPU: 0 PID: 885 Comm: rspamd Not tainted 3.16.0-8-amd64 #1 Debian 3.16.64-2 [ 313.995310] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014 [ 313.995369] task: 8800bbb593d0 ti: 88033044c000 task.ti: 88033044c000 [ 313.995407] RIP: 0010:[] [] put_pid+0x12/0x50 [ 313.995449] RSP: 0018:88033044fea8 EFLAGS: 00010206 [ 313.995477] RAX: 00110060 RBX: 88032f24a140 RCX: 000e [ 313.995514] RDX: RSI: 81848780 RDI: 880330191900 [ 313.995550] RBP: 2000 R08: 81848780 R09: [ 313.995586] R10: R11: 0206 R12: 81889a40 [ 313.995622] R13: 0200 R14: R15: [ 313.995661] FS: 7f3c238b37c0() GS:88033fc0() knlGS: [ 313.995702] CS: 0010 DS: ES: CR0: 80050033 [ 313.995732] CR2: 8823300a1998 CR3: 00032f27c000 CR4: 0670 [ 313.995772] Stack: [ 313.995786] 88032f24a140 8123cfb2 88032fc71400 305653595319 [ 313.995830] 0030303030303030 b99a119d 81889b10 [ 313.995874] 88033044ff70 7f3c17cb17c0 7f3c19851680 [ 313.995918] Call Trace: [ 313.995940] [] ? newseg+0x2b2/0x370 [ 313.995973] [] ? ipcget+0xd9/0x1d0 [ 313.996010] [] ? SyS_shmget+0x42/0x50 [ 313.996044] [] ? system_call_fast_compare_end+0x1c/0x21 [ 313.996079] Code: 48 c1 e2 05 48 85 c9 48 8b 54 10 38 75 85 0f 1f 00 31 c0 c3 0f 1f 44 00 00 0f 1f 44 00 00 48 85 ff 74 1a 53 8b 47 04 48 c1 e0 05 <48> 8b 5c 07 38 8b 07 83 f8 01 74 12 3e ff 0f 74 0d 5b f3 c3 66 [ 313.996288] RIP [] put_pid+0x12/0x50 [ 313.996319] RSP [ 313.996340] CR2: 8823300a1998 [ 313.996361] ---[ end trace ab5bd051ff70cff5 ]---
Processed: Re: riece: error on (wrong-number-of-arguments (1 . 1) 2)
Processing control commands: > tags -1 +patch +pending Bug #927263 [riece] riece: unusable on Emacs 26 Ignoring request to alter tags of bug #927263 to the same tags previously set Bug #927263 [riece] riece: unusable on Emacs 26 Added tag(s) pending. -- 927263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927263: riece: error on (wrong-number-of-arguments (1 . 1) 2)
control: tags -1 +patch +pending Hi, Thanks for your patch, I'll test and upload in this weekend holiday. -- Hideki Yamane
Bug#924591: this requires linking in libsparse, which is from Android sources
On Thu, Apr 18, 2019 at 09:32:06PM +0200, Hans-Christoph Steiner wrote: > > One possibility would be including libsparse as a patch, it doesn't > change a lot: > https://android.googlesource.com/platform/system/core/+log/master/libsparse > > But it depends on Android's libbase and libz-host. This might be "serious" bug from the fastboot package's perspective, but there's no way in heck the release time is going to consider this a bug that is "serious" priority for e2fsprogs. More to the point, there's now way in the world I (or the release and installer teams) are going to make e2fsprogs, which is an "important=yes" package with priority "required" drag in the android-libsparse, android-libbase, and zlib1g packages. So the way you changed android-sdk-platforms-tools to use /sbin/mke2fs was a really bad choice, especially this while we are in release freeze for Buster. There's no way in the world we are going to make a change like this to a package like e2fsprogs which is used by the installer at this point. If we had more time, and if android-libsparse-dev shipped a static library, we could have considered statically linking in android-libsparse, android-libbase, and libz --- and see if they would bloat the mke2fs and debugfs binaries by only a minimal amount. This would also require making changes to e2fsprogs configure and Makefiles, since currently we only have support for linking in libsparse in the AOSP build files. The reason for this is historical; at the time when the intern working with Android team was working on replace Android's make_ext4fs program with mke2fs and e2droid, there was no distribution that was shipping libsparse, and trying to make libsparse available to Linux desktop environments was *way* beyond the scope of the Intern's project and time availability. We can work on this trying to find a solution post-Buster --- either using static linking, or *possibly* figuring out a way to optionally use dlopen() to pull in libsparse for sparse_io.c, much like the way libss optionally pulls in the readline library using dlopen at runtime, back when we cared about making mke2fs fit on a two 1.44 MiB boot/root install floppies. :-) Alternatively, you can build your own version of mke2fs using the libsparse from AOSP. If you want a solution that might make it in during the Buster release freeze, that's probably the short-term solution I would suggest. So your choice --- we can either reassign this bug back to fastboot or android-sdk-platforms-tools, or I can downgrade the severity of this bug for e2fsprogs down to wishlist[1]. Let me know how you want to handle this. Cheers, - Ted [1] This is because I view this both as a "feature request" and "bugs that are very difficult to fix due to major design considerations" (per https://www.debian.org/Bugs/Developer#severities), not to mention that it's going to affect a miniscule fraction of the e2fsprogs package's users.
Bug#927301: marked as done (missing depends on python3-pkg-resources)
Your message dated Fri, 19 Apr 2019 02:35:27 +
with message-id
and subject line Bug#927301: fixed in gpustat 0.5.0-3
has caused the Debian Bug report #927301,
regarding missing depends on python3-pkg-resources
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.)
--
927301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpustat
Version: 0.5.0-2
Hi,
when starting gpustat, it fails with:
No module named 'pkg_resources'
for some reason, the required depends on python3-pkg-resources is not
picked up automatically by ${python3:Depends}.
Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: gpustat
Source-Version: 0.5.0-3
We believe that the bug you reported is fixed in the latest version of
gpustat, 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.
Mo Zhou (supplier of updated gpustat 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, 19 Apr 2019 02:21:20 +
Source: gpustat
Binary: gpustat
Architecture: source all
Version: 0.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Mo Zhou
Description:
gpustat- pretty nvidia device monitor
Closes: 927301
Changes:
gpustat (0.5.0-3) unstable; urgency=medium
.
* Add missing runtime deps python3-pkg-resources. (Closes: #927301)
Although this might be a dh-python bug, let's fixup the superficial
problem first.
* Add the watch file.
Checksums-Sha1:
b5889f51944f215161065c196b1cef54b0a6c50a 2035 gpustat_0.5.0-3.dsc
15a69714d8389a1e53d853829581c05b66469a60 2020 gpustat_0.5.0-3.debian.tar.xz
f7bfee19f1e7ede8f083a79a815c4eba7b9744c2 12408 gpustat_0.5.0-3_all.deb
e7cf607550818f7973140956f759d279d85e1aa1 6826 gpustat_0.5.0-3_amd64.buildinfo
Checksums-Sha256:
38c105fe150e30aa926346e262e6e30cece0b1dc67e7326836f07fecbcdfd1b3 2035
gpustat_0.5.0-3.dsc
10f902acf50f45f75e553a6055d67d3ba06c0cf5a5b4689e42b08f57c0e2a90d 2020
gpustat_0.5.0-3.debian.tar.xz
4d297a3d4fc598e89ebd428e12bac71abee3bf4fd9ab1cf0c3d8844d9b3e5665 12408
gpustat_0.5.0-3_all.deb
c35a06bcf3682b10d60444ddbf15aec3cd956088cf6b33208c9eb4c95ce28e9c 6826
gpustat_0.5.0-3_amd64.buildinfo
Files:
ce2798738e0542fb6d4c861cb7c4fef9 2035 contrib/admin optional
gpustat_0.5.0-3.dsc
2fe6e7f4d55dc61d1e87ff1b55ae916f 2020 contrib/admin optional
gpustat_0.5.0-3.debian.tar.xz
1a8d7f2cd39987ddab0ddecb4a50624d 12408 contrib/admin optional
gpustat_0.5.0-3_all.deb
dfbc95ee7153cfc6a0177c8537e2a963 6826 contrib/admin optional
gpustat_0.5.0-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAly5MQkACgkQYmRes19o
aooapA/+J4t4HrkGKN9T4671z0U+vDNmecKO7T/2Dfkg0F/kz1E5KNGa7xlTr21v
o6N0S0S+W0x08kqUcwmLvdGN+he4RRE4q3Lz8wXoMsQ9B/qKO+TIyR5V0RF2d8ct
i7jrM4IUGPCKARezT7Mb57k+gsQp80Fw8mqlliCK6GyuIlJqUyHe0gSOO8r9eqFe
c727SzwihVAi2MBNG+Xv2QFuyTbHPDUTLsJf+8iMo+9dpSkUQn61I2Qj2j9DLDX4
n5T7PT1ekN+GJ39vBJVe3nUHwY1QuXRwOOHsVEB3nmj7qFotdTvwPvrqw7Hk6Dr8
OntIrgaRAAyIW641TagM0OJvj5FLw8Lx+XnSjIh5CF+b3mUt++rQfAo/GDxMd3cO
I7y2bk3xtLyh6+oAb283T450/z/UhTlYENEUzxrnLXIbMyOLPJGel3g4DzNlEDIL
Uy5V4wcfyWJrg3Yt1Dv2wHdafm3UXW/E4YeHUq1+huKPKLvVycW5J+WtGFisy923
kV6P/dVUys4/eCWi4qnVsjG+g5zr8PcS8iijTOsh69ti+hNAkyYTn0n+22n+UWR1
Rd5kxoZYE6RWzMmb7vYaLJBL3PmiwaJ98wehMj0+/dzdAnEOxJ5MmaChVTB0abQT
6E17ONAGJQHFwHy5RpOAhfTYdstCnqbqWukD72EjeLv7eeDJ/q8=
=+5TY
-END PGP SIGNATURE End Message ---
Bug#927245: caveconverter: FTBFS (jh_build: Cannot find "caveconverter")
On 2019-04-16 19:43 +, Santiago Vila wrote: > Package: src:caveconverter > Version: 0~20170114-4 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > jh_build: Compatibility levels before 9 are deprecated (level 7 in use) > jh_build: Cannot find (any matches for) "caveconverter" (tried in .) Confirmed, thanks. I'll work out what's gone wrong there and upload a fix. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Processed: forcibly merging 927353 927354 927359
Processing commands for cont...@bugs.debian.org: > forcemerge 927353 927354 927359 Bug #927353 [src:htslib] src:htslib: Please stop building on any-i386 Bug #927354 [src:htslib] libhts2: Please stop building on any-i386 Bug #927359 [src:htslib] tabix: Please stop building on any-i386 Merged 927353 927354 927359 > thanks Stopping processing here. Please contact me if you need assistance. -- 927353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927353 927354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927354 927359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 927354 to src:htslib
Processing commands for cont...@bugs.debian.org: > reassign 927354 src:htslib Bug #927354 [libhts2] libhts2: Please stop building on any-i386 Bug reassigned from package 'libhts2' to 'src:htslib'. No longer marked as found in versions htslib/1.9-10. Ignoring request to alter fixed versions of bug #927354 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 927354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 927353 to src:htslib: Please stop building on any-i386
Processing commands for cont...@bugs.debian.org: > retitle 927353 src:htslib: Please stop building on any-i386 Bug #927353 [src:htslib] libhts-dev: Please stop building on any-i386 Changed Bug title to 'src:htslib: Please stop building on any-i386' from 'libhts-dev: Please stop building on any-i386'. > thanks Stopping processing here. Please contact me if you need assistance. -- 927353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 927359 to src:htslib
Processing commands for cont...@bugs.debian.org: > reassign 927359 src:htslib Bug #927359 [tabix] tabix: Please stop building on any-i386 Bug reassigned from package 'tabix' to 'src:htslib'. No longer marked as found in versions htslib/1.9-10. Ignoring request to alter fixed versions of bug #927359 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 927359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): Re: libhts-dev: Please stop building on any-i386
Processing commands for cont...@bugs.debian.org: > # second try > reassign 927353 src:htslib Bug #927353 [libhts-dev] libhts-dev: Please stop building on any-i386 Bug reassigned from package 'libhts-dev' to 'src:htslib'. No longer marked as found in versions htslib/1.9-10. Ignoring request to alter fixed versions of bug #927353 to the same values previously set > forcemerge 927353 927354 927359 Bug #927353 [src:htslib] libhts-dev: Please stop building on any-i386 Unable to merge bugs because: package of #927354 is 'libhts2' not 'src:htslib' package of #927359 is 'tabix' not 'src:htslib' Failed to forcibly merge 927353: Did not alter merged bugs. > retitle 927353 src:htslib: Please stop building on any-i386 Failed to set the title of 927353: failed to get lock on /org/bugs.debian.org/spool/lock/927353 -- Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > thanks Stopping processing here. Please contact me if you need assistance. -- 927353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927353 927354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927354 927359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): Re: libhts-dev: Please stop building on any-i386
Processing commands for cont...@bugs.debian.org: > merge 927353 927354 927359 Bug #927353 [libhts-dev] libhts-dev: Please stop building on any-i386 Unable to merge bugs because: package of #927359 is 'tabix' not 'libhts-dev' package of #927354 is 'libhts2' not 'libhts-dev' Failed to merge 927353: Did not alter merged bugs. > retitle 927353 src:htslib: Please stop building on any-i386 Failed to set the title of 927353: failed to get lock on /org/bugs.debian.org/spool/lock/927353 -- Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /org/bugs.debian.org/spool/lock/927353 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > thanks Stopping processing here. Please contact me if you need assistance. -- 927353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927353 927354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927354 927359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927357: marked as done (samtools: Please stop building on any-i386)
Your message dated Fri, 19 Apr 2019 00:33:26 +0200 with message-id <20190418223323.l455nxwmqs6mb...@debian.org> and subject line Re: augustus: Please stop building on any-i386 has caused the Debian Bug report #927357, regarding samtools: Please stop building on any-i386 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.) -- 927357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: samtools Version: 1.9-4 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James --- End Message --- --- Begin Message --- Hi James, On Thu, Apr 18, 2019 at 01:25:59PM +0100, James Clarke wrote: > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As these packages all build-depend on libhts-dev, there is no change needed in these packages. Once libhts-dev is no longer built on any-i386, the binaries can be removed and the packages will not get rebuilt, because the build-dependencies are not installable. Sorry for not spotting this earlier (during the irc discussion). Thanks, Ivo--- End Message ---
Bug#927358: marked as done (segemehl: Please stop building on any-i386)
Your message dated Fri, 19 Apr 2019 00:33:26 +0200 with message-id <20190418223323.l455nxwmqs6mb...@debian.org> and subject line Re: augustus: Please stop building on any-i386 has caused the Debian Bug report #927358, regarding segemehl: Please stop building on any-i386 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.) -- 927358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: segemehl Version: 0.3.4-1 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James --- End Message --- --- Begin Message --- Hi James, On Thu, Apr 18, 2019 at 01:25:59PM +0100, James Clarke wrote: > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As these packages all build-depend on libhts-dev, there is no change needed in these packages. Once libhts-dev is no longer built on any-i386, the binaries can be removed and the packages will not get rebuilt, because the build-dependencies are not installable. Sorry for not spotting this earlier (during the irc discussion). Thanks, Ivo--- End Message ---
Bug#927353: libhts-dev: Please stop building on any-i386
merge 927353 927354 927359 retitle 927353 src:htslib: Please stop building on any-i386 thanks Hi James, On Thu, Apr 18, 2019 at 01:26:22PM +0100, James Clarke wrote: > Package: libhts-dev > Version: 1.9-10 > Severity: serious > > Hi, > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As libhts-dev, libhts2 and tabix are all built from src:htslib, this is really a single bug: src:htslib should be changed not to build on any-i386. Thanks, Ivo
Bug#927351: marked as done (augustus: Please stop building on any-i386)
Your message dated Fri, 19 Apr 2019 00:33:26 +0200 with message-id <20190418223323.l455nxwmqs6mb...@debian.org> and subject line Re: augustus: Please stop building on any-i386 has caused the Debian Bug report #927351, regarding augustus: Please stop building on any-i386 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.) -- 927351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: augustus Version: 3.3.2+dfsg-2 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James --- End Message --- --- Begin Message --- Hi James, On Thu, Apr 18, 2019 at 01:25:59PM +0100, James Clarke wrote: > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As these packages all build-depend on libhts-dev, there is no change needed in these packages. Once libhts-dev is no longer built on any-i386, the binaries can be removed and the packages will not get rebuilt, because the build-dependencies are not installable. Sorry for not spotting this earlier (during the irc discussion). Thanks, Ivo--- End Message ---
Bug#927355: marked as done (nanopolish: Please stop building on any-i386)
Your message dated Fri, 19 Apr 2019 00:33:26 +0200 with message-id <20190418223323.l455nxwmqs6mb...@debian.org> and subject line Re: augustus: Please stop building on any-i386 has caused the Debian Bug report #927355, regarding nanopolish: Please stop building on any-i386 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.) -- 927355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nanopolish Version: 0.11.0-2 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James --- End Message --- --- Begin Message --- Hi James, On Thu, Apr 18, 2019 at 01:25:59PM +0100, James Clarke wrote: > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As these packages all build-depend on libhts-dev, there is no change needed in these packages. Once libhts-dev is no longer built on any-i386, the binaries can be removed and the packages will not get rebuilt, because the build-dependencies are not installable. Sorry for not spotting this earlier (during the irc discussion). Thanks, Ivo--- End Message ---
Bug#927356: marked as done (qtltools: Please stop building on any-i386)
Your message dated Fri, 19 Apr 2019 00:33:26 +0200 with message-id <20190418223323.l455nxwmqs6mb...@debian.org> and subject line Re: augustus: Please stop building on any-i386 has caused the Debian Bug report #927356, regarding qtltools: Please stop building on any-i386 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.) -- 927356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qtltools Version: 1.1+dfsg-3 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James --- End Message --- --- Begin Message --- Hi James, On Thu, Apr 18, 2019 at 01:25:59PM +0100, James Clarke wrote: > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As these packages all build-depend on libhts-dev, there is no change needed in these packages. Once libhts-dev is no longer built on any-i386, the binaries can be removed and the packages will not get rebuilt, because the build-dependencies are not installable. Sorry for not spotting this earlier (during the irc discussion). Thanks, Ivo--- End Message ---
Bug#927352: marked as done (delly: Please stop building on any-i386)
Your message dated Fri, 19 Apr 2019 00:33:26 +0200 with message-id <20190418223323.l455nxwmqs6mb...@debian.org> and subject line Re: augustus: Please stop building on any-i386 has caused the Debian Bug report #927352, regarding delly: Please stop building on any-i386 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.) -- 927352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: delly Version: 0.8.1-2 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James --- End Message --- --- Begin Message --- Hi James, On Thu, Apr 18, 2019 at 01:25:59PM +0100, James Clarke wrote: > This package uses htslib, which is no longer supported on any-i386. #914991 > removed the binaries on any-i386, but until any-i386 is removed from > Architecture:, wanna-build will re-build the package, thereby reinstating the > binaries on any-i386. Please upload a new version of the source package with > any-i386 removed from Architecture: for this binary package. As these packages all build-depend on libhts-dev, there is no change needed in these packages. Once libhts-dev is no longer built on any-i386, the binaries can be removed and the packages will not get rebuilt, because the build-dependencies are not installable. Sorry for not spotting this earlier (during the irc discussion). Thanks, Ivo--- End Message ---
Processed: Re: Bug#927263: riece: error on (wrong-number-of-arguments (1 . 1) 2)
Processing control commands: > severity -1 grave Bug #927263 [riece] riece: unusable on Emacs 26 Severity set to 'grave' from 'serious' -- 927263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927263: riece: error on (wrong-number-of-arguments (1 . 1) 2)
Control: severity -1 grave
Processed: Re: Bug#927263: riece: error on (wrong-number-of-arguments (1 . 1) 2)
Processing control commands: > retitle -1 riece: unusable on Emacs 26 Bug #927263 [riece] riece: error on (wrong-number-of-arguments (1 . 1) 2) Changed Bug title to 'riece: unusable on Emacs 26' from 'riece: error on (wrong-number-of-arguments (1 . 1) 2)'. > severity -1 serious Bug #927263 [riece] riece: unusable on Emacs 26 Severity set to 'serious' from 'normal' > tags -1 + patch Bug #927263 [riece] riece: unusable on Emacs 26 Added tag(s) patch. -- 927263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#918578: ping this bug again
Processing control commands: > tags -1 patch Bug #918578 [gosa] gosa: GOsa web interface missing password field Added tag(s) patch. -- 918578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918578: ping this bug again
Control: tags -1 patch
Hi all,
On Fr 05 Apr 2019 00:31:03 CEST, Wolfgang Schweer wrote:
Ping this bug again to keep the chance to fix it.
Wolfgang
Patch attached. Sorry for the dramatic pause before sitting down and
finding a fix. Please test.
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
--- a/gosa-core/include/smartyAddons/block.render.php
+++ b/gosa-core/include/smartyAddons/block.render.php
@@ -1,6 +1,6 @@
*/
if(empty($text)) {
--- a/gosa-core/include/smartyAddons/block.tr.php
+++ /dev/null
@@ -1,25 +0,0 @@
-
--- a/gosa-core/include/smartyAddons/function.factory.php
+++ b/gosa-core/include/smartyAddons/function.factory.php
@@ -1,6 +1,6 @@
pgpLG4V1r947u.pgp
Description: Digitale PGP-Signatur
Bug#926758: marked as done (Removing the package breaks the alternative on usr-merge system)
Your message dated Thu, 18 Apr 2019 16:48:29 + with message-id and subject line Bug#926728: fixed in arptables 0.0.4+snapshot20181021-4 has caused the Debian Bug report #926758, regarding Removing the package breaks the alternative on usr-merge system 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.) -- 926758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ebtables Version: 2.0.10.4+snapshot20181205-2 Severity: serious Hello, On system with usr-merge, removing ebtables breaks the alternative. The postinst script install symlinks from /sbin to /usr/sbin, in the prerm script these symlinks are removed. BUT ebtables also add itself as an alternative for ebtables implementations. That means that the symlinks installed by update-alternatives are rm when the package is removed. Not too sure how to fix this, maybe the prerm script should check if the symlinks directly point to a real file and only remove them in that case? Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ebtables depends on: ii libc6 2.28-8 Versions of packages ebtables recommends: ii iptables 1.8.2-4 ii kmod 26-1 ebtables suggests no packages. --- End Message --- --- Begin Message --- Source: arptables Source-Version: 0.0.4+snapshot20181021-4 We believe that the bug you reported is fixed in the latest version of arptables, 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. Alberto Molina Coballes (supplier of updated arptables 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 15:24:53 + Source: arptables Architecture: source Version: 0.0.4+snapshot20181021-4 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Alberto Molina Coballes Closes: 926728 Changes: arptables (0.0.4+snapshot20181021-4) unstable; urgency=medium . [ Arturo Borrero Gonzalez ] * [88703e1] src:arptables: add salsa CI integration . [ Alberto Molina Coballes ] * [eb7a44d] d/arptables.prerm: Remove /sbin symlinks on not usr-merged systems (Closes: #926728) Checksums-Sha1: 4fd10965b2e1d1183a1c6a585b4520b8f9b3522f 2073 arptables_0.0.4+snapshot20181021-4.dsc 26642e86fe7c25f1fb9801d43520bc40b58d140d 4968 arptables_0.0.4+snapshot20181021-4.debian.tar.xz 7873179aefa38635169032f5e4c5a1d53a1c0800 5440 arptables_0.0.4+snapshot20181021-4_amd64.buildinfo Checksums-Sha256: 74ef96250cce6883773c247121e2899e4365a2ffc14a16b37011af28477823c6 2073 arptables_0.0.4+snapshot20181021-4.dsc c9cdfb5daa358bc32129e233576c32b944dfb7a3c3997bd91a2884f510a9ca15 4968 arptables_0.0.4+snapshot20181021-4.debian.tar.xz 2361ee1fade2e46b7e1b95633bcd946367e1420ef4142f22f254302c473bdb8f 5440 arptables_0.0.4+snapshot20181021-4_amd64.buildinfo Files: 7307ead7487e2179b9e7917b09a778dd 2073 net optional arptables_0.0.4+snapshot20181021-4.dsc 635b42ff034cdc01b46ee2df9fd72d08 4968 net optional arptables_0.0.4+snapshot20181021-4.debian.tar.xz 35e757769382d06520a16764a706fc06 5440 net optional arptables_0.0.4+snapshot20181021-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAly4pacACgkQaOcTmB0V FfjIJA//SCgj/R/j9rzsc1qKNZz9GpuWHPoRKS661RIHEfjGewEu7pokbLPU8Hjd /ee4ey3Ub5cUNQsCW0v0N1HR//CIp1YFwNX0T0MEEszy7bEjqv2ZqyROn3vQwGpD KYNZYMAhpqrT/5Y208FZZfIasV69lX5rsJerZfWYJWn+a2urekrXZS6jcc70LWwT AfVmLd42zscEbvMMbFrlVhSDB/FRZxKfeNgSwjIUsuF+gKDDJegGjKrR46RfOjtv XKw98ojxMOs7MIqx+5gAxhK1RSujBUPMMxJVbwOGOSuICAfgpc4tGi6+4v0fJ8Cm
Bug#927385: marked as done (jquery: Prototype Pollution vulnerability)
Your message dated Thu, 18 Apr 2019 21:04:26 + with message-id and subject line Bug#927385: fixed in jquery 3.3.1~dfsg-2 has caused the Debian Bug report #927385, regarding jquery: Prototype Pollution vulnerability 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.) -- 927385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jquery Version: 3.3.1~dfsg-1 Severity: grave Tags: patch security upstream fixed-upstream Justification: user security hole Control: found -1 3.1.1-2 Hi A prototype pollution vulnerability (so far no CVE) has been fixed in jQuery 3.4.0: https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/ Patches: https://github.com/DanielRuf/snyk-js-jquery-174006?files=1 https://snyk.io/vuln/SNYK-JS-JQUERY-174006 Regards, Salvatore --- End Message --- --- Begin Message --- Source: jquery Source-Version: 3.3.1~dfsg-2 We believe that the bug you reported is fixed in the latest version of jquery, 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. Xavier Guimard (supplier of updated jquery 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: Thu, 18 Apr 2019 22:34:14 +0200 Source: jquery Architecture: source Version: 3.3.1~dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 927385 Changes: jquery (3.3.1~dfsg-2) unstable; urgency=medium . * Team upload * Add patch to prevent Object.prototype pollution (Closes: #927385) * Upgrade links to https Checksums-Sha1: c68b8f4dfd48b0fff00894739d377bf370d45127 2070 jquery_3.3.1~dfsg-2.dsc 51bd8d5330e761a474a2f5f1741212ec5ffacd5b 12428 jquery_3.3.1~dfsg-2.debian.tar.xz Checksums-Sha256: 3f053bce209434e572da87b1fa74c0834ec9db4e5af90cb00ea867ec50572c0e 2070 jquery_3.3.1~dfsg-2.dsc 0ff3f35dff884577a0e3b0d285e2b85955b0643dc25a3765b49f64bcbc0dfb68 12428 jquery_3.3.1~dfsg-2.debian.tar.xz Files: 6a9867fd4f75fe097723420c6fa65892 2070 javascript optional jquery_3.3.1~dfsg-2.dsc b09585e6b6e360839a18613da850f93e 12428 javascript optional jquery_3.3.1~dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAly43/YACgkQ9tdMp8mZ 7ul3qA//YEJDt0cuwEexHBYGK+cBt75QkP3XVQLJTHxo46/HCdwlKh81UNhMXf6o in1Zx+ztg6bnwgXWmeC572y46yg4FHi3laZbNDXdzuOnQX/taqdCJlDw0xh6YuRL +0HbEh4n8fzWz018lozJFuK5+npdzN02RrGvh6WJCD3NFGAUuc4rkCTDGK/9trNX H7VAf8bRqUIvVwE3I2uU/wIB3xx+bGL/4+FP0Gu6zJxmlnyGGDlOxJiEi+6+zXir 7zbWSvHoVaohTGn8EBAgOpR+Q+v3xu0pJFw+SH2oXMSVkSwEVIPTLiswQMMnI1ta shzwwkWMcgZ+NCYT9XiblycTciEK2wW345TRV0VlNDf7bt56C269nlPvCkSk3Fsh pCKe1jKsHN+qbXcBz2tWWSMGokSv47Ikco8saHk3dCEYs04t83ixlVK8kvE1H33b MamNUXGkaoSaCnDxX4zh0Q0b32a9JnyQLAzGVqeS5zIeXz+RIIMvxrIqwH5fQmsU u577a+EVKeTEB/3bmLRUkN0lnjtEEBjgps8bWQ56qIYJuoSVGvGBd9uaAdi1SxRq 37weyrq9lW8Qy/eQQS8Iyx6UNnB1zdBiD7umCfPb6i9ub5QNLd9GS518rMv07VQI VLUW0jUuIWz2O7E3zxii7WdVdQBHGDL8yOW6EInrlsOL6iLaibk= =gTRU -END PGP SIGNATURE End Message ---
Bug#927385: Bug #927385 in jquery marked as pending
Control: tag -1 pending Hello, Bug #927385 in jquery reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/jquery/commit/b6fb904f1d1818c03841425de36d037fc0ed2a9b Add patch to prevent Object.prototype pollution Closes: #927385 (this message was generated automatically) -- Greetings https://bugs.debian.org/927385
Processed: Bug #927385 in jquery marked as pending
Processing control commands: > tag -1 pending Bug #927385 [src:jquery] jquery: Prototype Pollution vulnerability Added tag(s) pending. -- 927385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927387: invesalius: crashes after splash screen
Package: invesalius
Version: 3.1.2-2
Severity: grave
Dear Maintainer,
When attempting to run InVesalius for the first time, I am presented
with the first-run language selector followed by the splash screen,
but no window ever appears and the invesalius3 process remains active
until manually terminated. Subsequent run attempts differ only in that
the language selector is not presented and the invesalius3 process
terminates on its own.
The following is the console output:
```
$ invesalius3 -d
/usr/lib/python3/dist-packages/wx/lib/pubsub/__init__.py:25:
wxPyDeprecationWarning: wx.lib.pubsub has been deprecated, plese migrate your
code to use pypubsub, available on PyPI.
wx.wxPyDeprecationWarning)
app.py:234: DeprecationWarning: Yield() is deprecated
wx.Yield()
Could not import dl
/usr/share/invesalius/invesalius/data/transformations.py:1899: UserWarning:
failed to import module _transformations
warnings.warn("failed to import module %s" % name)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/wx/core.py", line 2228, in Notify
self.notify()
File "/usr/lib/python3/dist-packages/wx/core.py", line 3384, in Notify
self.result = self.callable(*self.args, **self.kwargs)
File "app.py", line 240, in Startup
from invesalius.gui.frame import Frame
File "/usr/share/invesalius/invesalius/gui/frame.py", line 41, in
import invesalius.gui.default_tasks as tasks
File "/usr/share/invesalius/invesalius/gui/default_tasks.py", line 28, in
import invesalius.gui.data_notebook as nb
File "/usr/share/invesalius/invesalius/gui/data_notebook.py", line 40, in
import invesalius.data.slice_ as slice_
File "/usr/share/invesalius/invesalius/data/slice_.py", line 34, in
from invesalius.data.mask import Mask
File "/usr/share/invesalius/invesalius/data/mask.py", line 33, in
from invesalius_cy import floodfill
ImportError: cannot import name 'floodfill' from 'invesalius_cy'
(/usr/lib/invesalius/invesalius_cy/__init__.py)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/wx/core.py", line 2228, in Notify
self.notify()
File "/usr/lib/python3/dist-packages/wx/core.py", line 3384, in Notify
self.result = self.callable(*self.args, **self.kwargs)
File "app.py", line 123, in Startup2
self.control = self.splash.control
AttributeError: 'Inv3SplashScreen' object has no attribute 'control'
Traceback (most recent call last):
File "app.py", line 264, in OnClose
if self.fc.IsRunning():
AttributeError: 'Inv3SplashScreen' object has no attribute 'fc'
```
-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 3.0 (Beowulf)
Release:3.0
Codename: beowulf
Architecture: x86_64
Kernel: Linux 4.19.29-gnu (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages invesalius depends on:
ii invesalius-bin3.1.2-2
ii python3 3.7.2-1
ii python3-gdcm 2.8.8-6
ii python3-nibabel 2.3.2-1
ii python3-numpy 1:1.16.2-1
ii python3-pil 5.4.1-2
ii python3-psutil5.5.1-1
ii python3-scipy 1.1.0-3
ii python3-serial3.4-4
ii python3-skimage 0.14.2-2
ii python3-vtk7 7.1.1+dfsg1-12+b1
ii python3-vtkgdcm 2.8.8-6
ii python3-wxgtk4.0 4.0.4+dfsg-2
invesalius recommends no packages.
invesalius suggests no packages.
-- no debconf information
Bug#927385: jquery: Prototype Pollution vulnerability
Source: jquery Version: 3.3.1~dfsg-1 Severity: grave Tags: patch security upstream fixed-upstream Justification: user security hole Control: found -1 3.1.1-2 Hi A prototype pollution vulnerability (so far no CVE) has been fixed in jQuery 3.4.0: https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/ Patches: https://github.com/DanielRuf/snyk-js-jquery-174006?files=1 https://snyk.io/vuln/SNYK-JS-JQUERY-174006 Regards, Salvatore
Bug#883872: marked as done (bitlbee: Extremely incomplete d/copyright)
Your message dated Thu, 18 Apr 2019 19:48:43 + with message-id and subject line Bug#883872: fixed in bitlbee 3.6-1.1 has caused the Debian Bug report #883872, regarding bitlbee: Extremely incomplete d/copyright to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bitlbee Justification: Policy 12.5, 12.5.1 Severity: serious This package has an extremely incorrect d/copyright file. Additionally, this file is not machine readable. It also lacks accurate information such as what "portions" of code a license refers to. Almost none of the copyright information found in the source is represented in d/copyright. A non-inclusive list of a couple unrepresented files: - lib/ftutil.(c|h) - lib/json.(c|h) - lib/Makefile - lib/ns_parse.c - lib/proxy.(c|h) - utils/bitlbee-ctl.pl - protocols/ft.h - protocols/jabber/hipchat.c - protocols/jabber/s5bytestream.c - protocols/jabber/si.c - protocols/msn/Makefile - protocols/oscar/* - [...] -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Michael Lustfield --- End Message --- --- Begin Message --- Source: bitlbee Source-Version: 3.6-1.1 We believe that the bug you reported is fixed in the latest version of bitlbee, 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 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated bitlbee 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 21:27:48 +0200 Source: bitlbee Binary: bitlbee bitlbee-common bitlbee-dbgsym bitlbee-dev bitlbee-libpurple bitlbee-libpurple-dbgsym bitlbee-plugin-otr bitlbee-plugin-otr-dbgsym Architecture: source amd64 Version: 3.6-1.1 Distribution: unstable Urgency: medium Maintainer: Wilmer van der Gaast Changed-By: Andreas Tille Description: bitlbee- IRC to other chat networks gateway (default version) bitlbee-common - IRC to other chat networks gateway (common files/docs) bitlbee-dev - IRC to other chat networks gateway (dev files) bitlbee-libpurple - IRC to other chat networks gateway (using libpurple) bitlbee-plugin-otr - IRC to other chat networks gateway (OTR plugin) Closes: 883872 Changes: bitlbee (3.6-1.1) unstable; urgency=medium . * Non-maintainer upload. * Apply patch to d/copyright provided by Jochen Sprickerhof Closes: #883872 Checksums-Sha1: 79096a8e79c9c550cc178444c176d625a076a846 bitlbee_3.6-1.1.dsc c549fac9cac6af1daec9d9a942c4c46bdb58531a 15940 bitlbee_3.6-1.1.diff.gz 5f9c891f9537d40003dc2df7a5fa6f9b5685662a 79920 bitlbee-common_3.6-1.1_amd64.deb ddaf8af9184d3bc5b7870174f8787b8b71c36acc 728600 bitlbee-dbgsym_3.6-1.1_amd64.deb 6ff64f91641de5f60998aa506c754f2b303d1d0b 30344 bitlbee-dev_3.6-1.1_amd64.deb 77b5c168f40c03e33616527b372d391c32dabf69 636872 bitlbee-libpurple-dbgsym_3.6-1.1_amd64.deb ccce921a069308ed1106ee33177623e6b1dc4bb0 134436 bitlbee-libpurple_3.6-1.1_amd64.deb 464958cff415170986a10ee8ab44a6e08bacfc3b 46620 bitlbee-plugin-otr-dbgsym_3.6-1.1_amd64.deb cb643c7a03b8eb5ecf057d10992908596ae21372 17296 bitlbee-plugin-otr_3.6-1.1_amd64.deb 0e5132234c304c98c8204aeec32f4b33b7513ff9 11271 bitlbee_3.6-1.1_amd64.buildinfo f8686e892ce71dfd2051c467ed437d7b3b5afdb5 156484 bitlbee_3.6-1.1_amd64.deb Checksums-Sha256: 85c02e5a44a6eba9cce6e0ec890e15aa8c32bffebebb54c8317284c57bd2aa45 bitlbee_3.6-1.1.dsc b4bafe4b8a69d42eeedfa99103e897f30e3a0cf6c97eb75b0084516cb4ba8e3d 15940 bitlbee_3.6-1.1.diff.gz 841b2bb13732c10eb06d7ae73253b7506b5d7a0fb449cee0e304192caf4168d8 79920 bitlbee-common_3.6-1.1_amd64.deb 0deda0b0ab5b564a7c01520df976b487d7b211c9bd4342d2f8733c44a7adf574 728600 bitlbee-dbgsym_3.6-1.1_amd64.deb
Processed: jquery: Prototype Pollution vulnerability
Processing control commands: > found -1 3.1.1-2 Bug #927385 [src:jquery] jquery: Prototype Pollution vulnerability Marked as found in versions jquery/3.1.1-2. -- 927385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924591: this requires linking in libsparse, which is from Android sources
One possibility would be including libsparse as a patch, it doesn't change a lot: https://android.googlesource.com/platform/system/core/+log/master/libsparse But it depends on Android's libbase and libz-host.
Processed: [bts-link] source package src:phpldapadmin
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:phpldapadmin > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #867719 (http://bugs.debian.org/867719) > # Bug title: phpldapadmin: CVE-2017-11107 > # * https://github.com/leenooks/phpLDAPadmin/issues/50 > # * remote status changed: open -> closed > # * closed upstream > tags 867719 + fixed-upstream Bug #867719 [src:phpldapadmin] phpldapadmin: CVE-2017-11107 Added tag(s) fixed-upstream. > usertags 867719 - status-open Usertags were: status-open. Usertags are now: . > usertags 867719 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 867719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924591: this requires linking in libsparse, which is from Android sources
Even though buster's e2fsprogs includes support for android_sparse in the source code, it requires linking against libsparse, which is in android-libsparse. That means making e2fsprogs Build-Depend on android-libsparse-dev.
Bug#921599: [debian-mysql] Bug#921599: mariadb-10.3: always connects to localhost ignoring host entry in option file
This is pending since https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/5046bb4fc2a8ff47a1cf139eba468286a29fcf13 Should be fixed when 10.3.14-1 is uploaded.
Bug#924591: the bug is in mke2fs
Control: reassign 924591 e2fsprogs 1.44.5-1
Looks like the bug is because buster's e2fsprogs is not building with
the android_sparse option, even though it is included in the source code.
$ strace -f -e trace=execve -s4000 /usr/bin/fastboot
format:ext4:0x180b0 userdata
execve("/usr/bin/fastboot", ["/usr/bin/fastboot",
"format:ext4:0x180b0", "userdata"], 0x7fff4b65fce0 /* 70 vars */) = 0
Warning: userdata size is 0x000180b0, but 0x180b0 was
requested for formatting.
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
strace: Process 2831 attached
[pid 2831] execve("/usr/lib/android-sdk/platform-tools/mke2fs",
["/usr/lib/android-sdk/platform-tools/mke2fs", "-t", "ext4", "-b",
"4096", "-E", "android_sparse", "-O", "uninit_bg",
"/tmp/TemporaryFile-mslQq9", "1575680"], 0x564330202140 /* 71 vars */) = 0
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-mslQq9: Unimplemented ext2 library function while
setting up superblock
[pid 2831] +++ exited with 1 +++
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=2831,
si_uid=1000, si_status=1, si_utime=0, si_stime=0} ---
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
+++ exited with 1 +++
$ /usr/sbin/mke2fs -t ext4 -b 4096 -E android_sparse -O uninit_bg
/tmp/TemporaryFile-3LivFN 1575680
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-3LivFN: Unimplemented ext2 library function while
setting up superblock
$ /opt/android-sdk/platform-tools/mke2fs -t ext4 -b 4096 -E
android_sparse -O uninit_bg /tmp/TemporaryFile-3LivFN 1575680
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 1575680 4k blocks and 394352 inodes
Filesystem UUID: 45726b57-c5b4-467e-b22d-0165ba9d9e58
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
Processed: the bug is in mke2fs
Processing control commands: > reassign 924591 e2fsprogs 1.44.5-1 Bug #924591 [fastboot] fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs Bug reassigned from package 'fastboot' to 'e2fsprogs'. No longer marked as found in versions android-platform-system-core/1:8.1.0+r23-4. Ignoring request to alter fixed versions of bug #924591 to the same values previously set Bug #924591 [e2fsprogs] fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs Marked as found in versions e2fsprogs/1.44.5-1. -- 924591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#927275: gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot
Processing control commands: > severity -1 normal Bug #927275 [gnome-shell] gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot Severity set to 'normal' from 'serious' > reassign -1 libmutter-3-0 3.30.2-6 Bug #927275 [gnome-shell] gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot Bug reassigned from package 'gnome-shell' to 'libmutter-3-0'. No longer marked as found in versions gnome-shell/3.30.2-3. Ignoring request to alter fixed versions of bug #927275 to the same values previously set Bug #927275 [libmutter-3-0] gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot Marked as found in versions mutter/3.30.2-6. > tags -1 + moreinfo Bug #927275 [libmutter-3-0] gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot Added tag(s) moreinfo. > affects -1 gnome-shell Bug #927275 [libmutter-3-0] gnome-shell - Intel GPU - monitors.xml is ignored and settings are not applied after suspend/reboot Added indication that 927275 affects gnome-shell -- 927275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927275 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
Control: severity -1 normal Control: reassign -1 libmutter-3-0 3.30.2-6 Control: tags -1 + moreinfo Control: affects -1 gnome-shell On Wed, 17 Apr 2019 at 10:32:25 +0200, - wrote: > Severity: serious This is an annoying bug, but is not so serious that removing GNOME from Debian would be better than releasing buster with this bug unfixed, so I'm downgrading it to normal. > Debian Version: Buster with latest updates I've assumed that this means libmutter-3-0 3.30.2-6, among other packages. If possible please report Debian bugs with the reportbug tool, which provides useful information that helps developers to solve the bugs you report. > 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? monitors.xml handling is part of libmutter, which GNOME Shell uses for window management and compositing. I don't know what is causing this or how to solve it, but if you can provide more information, that might help someone else to find a solution: The monitors.xml you attached has two configurations. Do these accurately represent what you configured at your office and your home? * Configuration A: * 1920x1080 SyncMaster, serial number H9XSA30201, on DisplayPort connector DP-1-3, on the left * 1920x1080 SyncMaster, serial number H9XSA30209. on DisplayPort connector DP-1-2, on the right * Laptop's internal display panel disabled * Configuration B: * 2560x1440 FUS P27-8 TE Pro, serial number YVBH702276, on DisplayPort connector DP-5 * Laptop's internal display panel disabled (I'm surprised they're using such different DisplayPort connector IDs when you said you're using the same docking station at each site - I'd expect the labelling to be the same.) Are you using GNOME in Wayland mode (default) or in X11/Xorg mode? If you reconfigure monitors in gnome-control-center, does that temporarily get you back to the desired configuration until the next undock/suspend/resume/dock cycle? If you undock, suspend, resume and connect to *the same* dock, do you get the desired result, or do you get the same problem as if you had connected to the other dock? Does the contents of monitors.xml change during the undock/suspend/resume/dock cycle? For example, please try this: * have the configuration you wanted (or any distinctive configuration, really) * copy monitors.xml to monitors.xml.start * undock * copy monitors.xml to monitors.xml.undocked * suspend * resume * copy monitors.xml to monitors.xml.resumed * dock * copy monitors.xml to monitors.xml.docked * log out and back in (or reboot) * copy monitors.xml to monitors.xml.restarted and compare the various monitors.xml.* files to see whether the contents changed at any point. Is anything interesting or possibly-relevant-looking logged at each step? If you are using Debian's default systemd init system, everything should be logged to the systemd Journal, accessible by running the journalctl command. If you are not using systemd, the logs are more scattered: try ~/.xsession-errors, /var/log/Xorg.*.log and /var/log/syslog. You can leave markers in the systemd Journal or in /var/log/syslog with a command like: logger -t debug-monitor-detection "About to undock..." which might be a useful way to see which messages happened before or after which action you took. It would probably also be useful to install the read-edid package, and record the output of these commands at each step: head /sys/class/drm/card*/modes for x in /sys/class/drm/card*/edid; do echo "$x:"; parse-edid < "$x"; done If none of the above has provided useful information, another thing that might help to find what the problem is or how to fix it would be to edit /usr/share/wayland-sessions/gnome.desktop and modify the line Exec=/usr/bin/gnome-session to be Exec=/usr/bin/env MUTTER_VERBOSE=1 MUTTER_DEBUG=1 /usr/bin/gnome-session which should result in libmutter logging a lot more messages to whatever log you found other gnome-shell messages in. smcv
Bug#924843: Touching bug since otherwise package will be removed
Hi Filippo, msxpertsuite is about to be removed from unstable. Do you need help? Kind regards Andreas. -- http://fam-tille.de
Bug#921599: [debian-mysql] Bug#921599: mariadb-10.3: always connects to localhost ignoring host entry in option file
On Tue, 2 Apr 2019 09:41:25 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: > OK, so current MariaDB 10.3.13 we have in Debian contains MariaDB > Connector C 3.0.9 > > mariadb-10.3$ grep -rF 'SET(CPACK_PACKAGE_VERSION_' libmariadb/CMakeLists.txt > SET(CPACK_PACKAGE_VERSION_MAJOR 3) > SET(CPACK_PACKAGE_VERSION_MINOR 0) > SET(CPACK_PACKAGE_VERSION_PATCH 9) > > This has been fixed upstream in MariaDB Connector C 3.0.10: > https://github.com/MariaDB/mariadb-connector-c/pull/101 > > MariaDB 10.3.14 release preparations are in progress, so this can be > fixed soon via the new upstream release: > https://mariadb.com/kb/en/library/mariadb-10314-release-notes/ > > Hi, Gentle ping on this. :) Thanks, ~Niels
Bug#913641: marked as done (libreoffice-report-builder: report builder reports fail to run after S8195874 in OpenJDK)
Your message dated Thu, 18 Apr 2019 17:32:17 + with message-id and subject line Bug#913641: fixed in libreoffice 1:5.2.7-1+deb9u7 has caused the Debian Bug report #913641, regarding libreoffice-report-builder: report builder reports fail to run after S8195874 in OpenJDK 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.) -- 913641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-report-builder Version: 1:6.1.3-1 Severity: normal Trying to run any report (a report builder one, not a legacy one) fails with error message: Can not activate the factory for org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory Nothing particular on stderr. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (600, 'stable-updates'), (600, 'stable'), (400, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-7-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-report-builder depends on: ii libbase-java 1.1.6-2 ii libcommons-logging-java1.2-1 ii libflute-java 1:1.1.6-3 ii libfonts-java 1.1.6.dfsg-3 ii libformula-java1.1.7.dfsg-2 ii liblayout-java 0.2.10-2 ii libloader-java 1.1.6.dfsg-4 ii libpentaho-reporting-flow-engine-java 0.9.4-4 ii libreoffice-common 1:6.1.3-1 ii libreoffice-core 1:6.1.3-1 ii libreoffice-java-common1:6.1.3-1 ii libreoffice-report-builder-bin 1:6.1.3-1 ii librepository-java 1.1.6-3 ii libsac-java1.3+dfsg-2 ii libserializer-java 1.1.6-4 ii libxml-java1.1.6.dfsg-3 libreoffice-report-builder recommends no packages. libreoffice-report-builder suggests no packages. Versions of packages libreoffice-base depends on: ii libc6 2.27-8 ii libgcc1 1:8.2.0-9 ii libreoffice-base-core 1:6.1.3-1 ii libreoffice-base-drivers 1:6.1.3-1 ii libreoffice-core 1:6.1.3-1 ii libstdc++68.2.0-9 ii uno-libs3 6.1.3-1 ii ure 6.1.3-1 Versions of packages libreoffice-base recommends: ii default-jre [java6-runtime]2:1.8-58 ii libreoffice-java-common1:6.1.3-1 ii libreoffice-writer 1:6.1.3-1 ii openjdk-7-jre [java6-runtime] 7u151-2.6.11-3 ii openjdk-8-jre [java6-runtime] 8u181-b13-2~deb9u1 Versions of packages libreoffice-base suggests: ii unixodbc 2.3.4-1 -- no debconf information --- End Message --- --- Begin Message --- Source: libreoffice Source-Version: 1:5.2.7-1+deb9u7 We believe that the bug you reported is fixed in the latest version of libreoffice, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated libreoffice 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, 23 Jan 2019 18:51:09 +0100 Source: libreoffice Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core libreoffice-common libreoffice-java-common libreoffice-writer libreoffice-calc libreoffice-impress libreoffice-draw libreoffice-math libreoffice-base-core libreoffice-base libreoffice-style-oxygen libreoffice-style-breeze libreoffice-style-tango libreoffice-style-hicontrast libreoffice-style-sifr libreoffice-style-galaxy libreoffice-gnome python3-uno libreoffice-officebean libreoffice-script-provider-python libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-pdfimport libreoffice-avmedia-backend-gstreamer libreoffice-avmedia-backend-vlc
Bug#925257: marked as done (ghostscript: CVE-2019-3838: forceput in DefineResource is still accessible)
Your message dated Thu, 18 Apr 2019 17:32:08 + with message-id and subject line Bug#925257: fixed in ghostscript 9.26a~dfsg-0+deb9u2 has caused the Debian Bug report #925257, regarding ghostscript: CVE-2019-3838: forceput in DefineResource is still accessible 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.) -- 925257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript Version: 9.26a~dfsg-2 Severity: grave Tags: security upstream Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=700576 Control: found -1 9.26a~dfsg-0+deb9u1 Hi, The following vulnerability was published for ghostscript. CVE-2019-3838[0]: forceput in DefineResource is still accessible 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-3838 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3838 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 9.26a~dfsg-0+deb9u2 We believe that the bug you reported is fixed in the latest version of ghostscript, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ghostscript 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 16:40:43 +0200 Source: ghostscript Architecture: source Version: 9.26a~dfsg-0+deb9u2 Distribution: stretch-security Urgency: high Maintainer: Debian Printing Team Changed-By: Salvatore Bonaccorso Closes: 925256 925257 Changes: ghostscript (9.26a~dfsg-0+deb9u2) stretch-security; urgency=high . * Non-maintainer upload by the Security Team. * Have gs_cet.ps run from gs_init.ps * Undef /odef in gs_init.ps * Restrict superexec and remove it from internals and gs_cet.ps (CVE-2019-3835) (Closes: #925256) * Obliterate "superexec". We don't need it, nor do any known apps (CVE-2019-3835) (Closes: #925256) * Make a transient proc executeonly (in DefineResource) (CVE-2019-3838) (Closes: #925257) * an extra transient proc needs executeonly'ed (CVE-2019-3838) (Closes: #925257) Checksums-Sha1: a36471faa5f824feb421b9b8d36a01880ed2 3052 ghostscript_9.26a~dfsg-0+deb9u2.dsc 64988c4bcb2461931ab91c63de5c3c3c7bb14a07 114608 ghostscript_9.26a~dfsg-0+deb9u2.debian.tar.xz Checksums-Sha256: f2db945f626273db54377fd2114278e0bedce96310668b6e550b26305ff9d29c 3052 ghostscript_9.26a~dfsg-0+deb9u2.dsc 83f9bf1932c637733e63e293ed822dff0ea9b47914c743d29725ffc2cee839e8 114608 ghostscript_9.26a~dfsg-0+deb9u2.debian.tar.xz Files: 3eaf5fdf443490ece65b2bf39c69456f 3052 text optional ghostscript_9.26a~dfsg-0+deb9u2.dsc be65f72beb08cce7f64abd31998ceb20 114608 text optional ghostscript_9.26a~dfsg-0+deb9u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlyx+4JfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EQS0P/AnEA56L6SIYVVNp8S2r0ovQSjiB4QID DxQrBdlSBIkOkCvx7yGZpW/opZsPHGnJrqZSdm+eqUckzMSg/x4sPlAo0JxTwmMU 7mgonXwHioqGVUk8qZ4q27KsiOjbOJETpVf90LuDm7lnLGvRjDqeE5ySehHnys2J /63RNYzLAj23H+jwVDsQA7DqLVK1KUHKGqABIyPJzVBnvFzoXAAGdGb9/UouiWsC 5g1TARClQrullhcNz2NcK0PLBbhtN1kxx/CyoBgS8itH3jolqUw4zk03Jx6p7F9f GqP5mHAMoZo9WQBNKnoTr3xV4elUFvxIkPncFfPHpU5315w2K84n50nLGqYy+5k4 VkVB78BuomMyfRlUKZ4YyXPEsWj0GqLZQUOsb7WEx5NzNW9/1Fc8ib0qbij2DSpg jVAapY/zRB+mjMB7ZmYdT3iVGQrQQEkQBMq0vrXZqnZyj3PuvPmE6AMj7MuQ8R5r 85Hj2Kvn2Ni4Ioxnz4h5grO5XI4cjDvNlrY4tlrpW/WHmAMZe4jEVJo3pbchlXbn J3bs2AWiI0J/yEnlcQLjIAgv9mQpFIJLAl8OYj6nSL7Y9xzJjGdVngCB6udS35J1 Bv9mEueZ77YFzBxBJNB+nZFuR7EFDFu94HMqLWDhhIod8432dmHl2m9FzM4YjjlP 3nwxgM0ZrQZZ =tQiH -END PGP SIGNATURE End Message ---
Bug#922453: marked as done (cernlib: fortran modules must be compiled with no stronger optimization than -O1 (aka -O))
Your message dated Thu, 18 Apr 2019 17:32:08 + with message-id and subject line Bug#922453: fixed in cernlib 20061220+dfsg3-4.3+deb9u1 has caused the Debian Bug report #922453, regarding cernlib: fortran modules must be compiled with no stronger optimization than -O1 (aka -O) 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.) -- 922453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cernlib Version: 20061220+dfsg3-4.3 Severity: grave Justification: renders package unusable Tags: patch Message transféré Sujet : cernlib (20061220+dfsg3-4.3build1) misbehaves on x86_64 Date : Mon, 4 Feb 2019 00:52:08 +0100 De : Jacek M. Holeczek Pour : Matthias Klose , Gilles Filippini Hi, I tried to use the cernlib related executables on an Ubuntu 18.04 / x86_64 / gcc 7.3.0. I have found that the "pawX11" misbehaves. The problem is related to the used fortran optimization flag. By default it is now "-O3" but this is producing misbehaving libraries. I tried to rebuild everything using "-O2" but they still misbehaved. Finally, after I switched to "-O" (i.e. "-O1"), they started to behave properly. Please find attached a small patch file which tries to ensure that the fortran source code will be compiled with "-O" (and not "-O3" nor "-O2"). Hope it helps, Best regards, Jacek. diff -Naur cernlib-20061220+dfsg3.original/debian/patches/102-dont-optimize-some-code.dpatch cernlib-20061220+dfsg3/debian/patches/102-dont-optimize-some-code.dpatch --- cernlib-20061220+dfsg3.original/debian/patches/102-dont-optimize-some-code.dpatch 2017-08-06 19:23:39.0 + +++ cernlib-20061220+dfsg3/debian/patches/102-dont-optimize-some-code.dpatch 2019-02-03 21:49:52.638404057 + @@ -20,7 +20,7 @@ +#endif + +/* GCC 7 on 64bit targets, see https://gcc.gnu.org/PR81723 */ -+SpecialFortranLibObjectRule(cwerf64,cwerf64,-O2,NullParameter) ++SpecialFortranLibObjectRule(cwerf64,cwerf64,-O,NullParameter) diff -urNad cernlib-2006.dfsg.2~/src/mathlib/gen/d/Imakefile cernlib-2006.dfsg.2/src/mathlib/gen/d/Imakefile --- cernlib-2006.dfsg.2~/src/mathlib/gen/d/Imakefile 1996-06-12 08:25:38.0 -0700 +++ cernlib-2006.dfsg.2/src/mathlib/gen/d/Imakefile2008-02-22 12:06:26.0 -0800 diff -Naur cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch --- cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch 2013-08-24 09:16:07.0 + +++ cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch 2019-02-03 21:48:36.151806615 + @@ -76,7 +76,7 @@ - PARAMETER (CHPOF = '-c -O -fno-automatic') - PARAMETER (CHPOC = '-c -O2 -m486') -+ PARAMETER (CHPOF = '-c -g -O2 -fno-automatic') ++ PARAMETER (CHPOF = '-c -g -O -fno-automatic') + PARAMETER (CHPOC = '-c -g -O2') PARAMETER (CHPOA = ' ') diff -Naur cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch --- cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch 2015-09-09 01:24:30.0 + +++ cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch 2019-02-03 21:47:38.208869466 + @@ -1794,7 +1794,7 @@ + +#ifdef AMD64Architecture +# ifndef OptimizationLevel -+# define OptimizationLevel -O3 ++# define OptimizationLevel -O +# endif +# ifndef OptimizedCDebugFlags +# define OptimizedCDebugFlags OptimizationLevel signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cernlib Source-Version: 20061220+dfsg3-4.3+deb9u1 We believe that the bug you reported is fixed in the latest version of cernlib, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gilles Filippini (supplier of updated cernlib 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
Bug#924509: marked as done (CVE-2016-9840 CVE-2016-9841 CVE-2016-9842 CVE-2016-9843)
Your message dated Thu, 18 Apr 2019 17:32:53 +
with message-id
and subject line Bug#924509: fixed in rsync 3.1.2-1+deb9u2
has caused the Debian Bug report #924509,
regarding CVE-2016-9840 CVE-2016-9841 CVE-2016-9842 CVE-2016-9843
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.)
--
924509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rsync
Version: 3.1.3-5
Severity: grave
Tags: security
rsync ships a local copy of zlib, which misses the security fixes for
CVE-2016-9840 CVE-2016-9841 CVE-2016-9842 CVE-2016-9843.
I've attached the respective upstream patches.
Also, let's revisit using the shared zlib copy for bullseye, please.
Cheers,
Moritz
>From 6a043145ca6e9c55184013841a67b2fef87e44c0 Mon Sep 17 00:00:00 2001
From: Mark Adler
Date: Wed, 21 Sep 2016 23:35:50 -0700
Subject: [PATCH] Remove offset pointer optimization in inftrees.c.
inftrees.c was subtracting an offset from a pointer to an array,
in order to provide a pointer that allowed indexing starting at
the offset. This is not compliant with the C standard, for which
the behavior of a pointer decremented before its allocated memory
is undefined. Per the recommendation of a security audit of the
zlib code by Trail of Bits and TrustInSoft, in support of the
Mozilla Foundation, this tiny optimization was removed, in order
to avoid the possibility of undefined behavior.
---
inftrees.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/inftrees.c b/inftrees.c
index 22fcd666..0d2670d5 100644
--- a/inftrees.c
+++ b/inftrees.c
@@ -54,7 +54,7 @@ unsigned short FAR *work;
code FAR *next; /* next available space in table */
const unsigned short FAR *base; /* base value table to use */
const unsigned short FAR *extra;/* extra bits table to use */
-int end;/* use base and extra for symbol > end */
+unsigned match; /* use base and extra for symbol >= match */
unsigned short count[MAXBITS+1];/* number of codes of each length */
unsigned short offs[MAXBITS+1]; /* offsets in table for each length */
static const unsigned short lbase[31] = { /* Length codes 257..285 base */
@@ -181,19 +181,17 @@ unsigned short FAR *work;
switch (type) {
case CODES:
base = extra = work;/* dummy value--not used */
-end = 19;
+match = 20;
break;
case LENS:
base = lbase;
-base -= 257;
extra = lext;
-extra -= 257;
-end = 256;
+match = 257;
break;
default:/* DISTS */
base = dbase;
extra = dext;
-end = -1;
+match = 0;
}
/* initialize state for loop */
@@ -216,13 +214,13 @@ unsigned short FAR *work;
for (;;) {
/* create table entry */
here.bits = (unsigned char)(len - drop);
-if ((int)(work[sym]) < end) {
+if (work[sym] + 1 < match) {
here.op = (unsigned char)0;
here.val = work[sym];
}
-else if ((int)(work[sym]) > end) {
-here.op = (unsigned char)(extra[work[sym]]);
-here.val = base[work[sym]];
+else if (work[sym] >= match) {
+here.op = (unsigned char)(extra[work[sym] - match]);
+here.val = base[work[sym] - match];
}
else {
here.op = (unsigned char)(32 + 64); /* end of block */
>From 9aaec95e82117c1cb0f9624264c3618fc380cecb Mon Sep 17 00:00:00 2001
From: Mark Adler
Date: Wed, 21 Sep 2016 22:25:21 -0700
Subject: [PATCH] Use post-increment only in inffast.c.
An old inffast.c optimization turns out to not be optimal anymore
with modern compilers, and furthermore was not compliant with the
C standard, for which decrementing a pointer before its allocated
memory is undefined. Per the recommendation of a security audit of
the zlib code by Trail of Bits and TrustInSoft, in support of the
Mozilla Foundation, this "optimization" was removed, in order to
avoid the possibility of undefined behavior.
---
inffast.c | 81 +--
1 file changed, 31 insertions(+), 50 deletions(-)
diff --git a/inffast.c b/inffast.c
index bda59ceb..f0d163db 100644
--- a/inffast.c
+++ b/inffast.c
@@ -10,25 +10,6 @@
#ifndef ASMINF
-/* Allow machine dependent optimization for post-increment or pre-increment.
- Based on testing to date,
- Pre-increment preferred for:
- - PowerPC G3 (Adler)
Bug#920855: marked as done (mariadb-10.1: FTBFS on mips{,{,64}el}: linker failures)
Your message dated Thu, 18 Apr 2019 17:32:51 +
with message-id
and subject line Bug#920855: fixed in mariadb-10.1 10.1.38-0+deb9u1
has caused the Debian Bug report #920855,
regarding mariadb-10.1: FTBFS on mips{,{,64}el}: linker failures
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.)
--
920855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.1
Version: 10.1.37-0+deb9u1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: affects -1 + release.debian.org security.debian.org
Hi,
The mariadb-10.1 on security.debian.org fails to build on all mipsen, with
similar errors:
> [ 99%] Linking CXX executable explain_filename-t
> cd /<>/builddir/unittest/sql && /usr/bin/cmake -E
> cmake_link_script CMakeFiles/explain_filename-t.dir/link.txt --verbose=1
> /usr/bin/mips-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat
> -Werror=format-security -pie -fPIC -Wl,-z,relro,-z,now -fstack-protector
> --param=ssp-buffer-size=4 -DWITH_INNODB_DISALLOW_WRITES -fno-exceptions
> -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing
> -Wno-uninitialized -D_FORTIFY_SOURCE=2 -DDBUG_OFF
> -specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now
> CMakeFiles/explain_filename-t.dir/explain_filename-t.cc.o -o
> explain_filename-t -lpthread ../../sql/libsql.a ../mytap/libmytap.a
> ../../storage/csv/libcsv.a ../../storage/heap/libheap.a
> ../../storage/maria/libaria.a ../../storage/myisam/libmyisam.a
> ../../storage/myisammrg/libmyisammrg.a
> ../../storage/perfschema/libperfschema.a ../../storage/sequence/libsequence.a
> ../../storage/xtradb/libxtradb.a -laio
> ../../plugin/auth_socket/libauth_socket.a ../../plugin/feedback/libfeedback.a
> ../../plugin/userstat/libuserstat.a ../../sql/libpartition.a
> ../../mysys/libmysys.a ../../mysys_ssl/libmysys_ssl.a ../../dbug/libdbug.a
> ../../mysys/libmysys.a ../../mysys_ssl/libmysys_ssl.a ../../dbug/libdbug.a
> -lz -lm ../../extra/yassl/libyassl.a ../../extra/yassl/taocrypt/libtaocrypt.a
> ../../strings/libstrings.a ../../vio/libvio.a ../../pcre/libpcre.a -lcrypt
> -ldl ../../wsrep/libwsrep.a -lsystemd -latomic -lpthread
> /usr/bin/ld: ../../mysys/libmysys.a(stacktrace.c.o): undefined reference to
> symbol '__bss_start'
> //lib/mips-linux-gnu/libselinux.so.1: error adding symbols: DSO missing from
> command line
> collect2: error: ld returned 1 exit status
Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.38-0+deb9u1
We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Otto Kekäläinen (supplier of updated mariadb-10.1 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: Tue, 16 Apr 2019 14:56:50 +0300
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.38-0+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadbclient-dev - MariaDB database development files
libmariadbclient-dev-compat - MariaDB database development files
(libmysqlclient compatibility)
libmariadbclient18 - MariaDB database client library
libmariadbd-dev - MariaDB embedded database, development files
libmariadbd18 - MariaDB embedded database, shared library
mariadb-client - MariaDB database client
Bug#925256: marked as done (ghostscript: CVE-2019-3835: superexec operator is available)
Your message dated Thu, 18 Apr 2019 17:32:08 + with message-id and subject line Bug#925256: fixed in ghostscript 9.26a~dfsg-0+deb9u2 has caused the Debian Bug report #925256, regarding ghostscript: CVE-2019-3835: superexec operator is available 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.) -- 925256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript Version: 9.26a~dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 9.26a~dfsg-0+deb9u1 Hi, The following vulnerability was published for ghostscript. CVE-2019-3835[0]: superexec operator is available 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-3835 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3835 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 9.26a~dfsg-0+deb9u2 We believe that the bug you reported is fixed in the latest version of ghostscript, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ghostscript 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 16:40:43 +0200 Source: ghostscript Architecture: source Version: 9.26a~dfsg-0+deb9u2 Distribution: stretch-security Urgency: high Maintainer: Debian Printing Team Changed-By: Salvatore Bonaccorso Closes: 925256 925257 Changes: ghostscript (9.26a~dfsg-0+deb9u2) stretch-security; urgency=high . * Non-maintainer upload by the Security Team. * Have gs_cet.ps run from gs_init.ps * Undef /odef in gs_init.ps * Restrict superexec and remove it from internals and gs_cet.ps (CVE-2019-3835) (Closes: #925256) * Obliterate "superexec". We don't need it, nor do any known apps (CVE-2019-3835) (Closes: #925256) * Make a transient proc executeonly (in DefineResource) (CVE-2019-3838) (Closes: #925257) * an extra transient proc needs executeonly'ed (CVE-2019-3838) (Closes: #925257) Checksums-Sha1: a36471faa5f824feb421b9b8d36a01880ed2 3052 ghostscript_9.26a~dfsg-0+deb9u2.dsc 64988c4bcb2461931ab91c63de5c3c3c7bb14a07 114608 ghostscript_9.26a~dfsg-0+deb9u2.debian.tar.xz Checksums-Sha256: f2db945f626273db54377fd2114278e0bedce96310668b6e550b26305ff9d29c 3052 ghostscript_9.26a~dfsg-0+deb9u2.dsc 83f9bf1932c637733e63e293ed822dff0ea9b47914c743d29725ffc2cee839e8 114608 ghostscript_9.26a~dfsg-0+deb9u2.debian.tar.xz Files: 3eaf5fdf443490ece65b2bf39c69456f 3052 text optional ghostscript_9.26a~dfsg-0+deb9u2.dsc be65f72beb08cce7f64abd31998ceb20 114608 text optional ghostscript_9.26a~dfsg-0+deb9u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlyx+4JfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EQS0P/AnEA56L6SIYVVNp8S2r0ovQSjiB4QID DxQrBdlSBIkOkCvx7yGZpW/opZsPHGnJrqZSdm+eqUckzMSg/x4sPlAo0JxTwmMU 7mgonXwHioqGVUk8qZ4q27KsiOjbOJETpVf90LuDm7lnLGvRjDqeE5ySehHnys2J /63RNYzLAj23H+jwVDsQA7DqLVK1KUHKGqABIyPJzVBnvFzoXAAGdGb9/UouiWsC 5g1TARClQrullhcNz2NcK0PLBbhtN1kxx/CyoBgS8itH3jolqUw4zk03Jx6p7F9f GqP5mHAMoZo9WQBNKnoTr3xV4elUFvxIkPncFfPHpU5315w2K84n50nLGqYy+5k4 VkVB78BuomMyfRlUKZ4YyXPEsWj0GqLZQUOsb7WEx5NzNW9/1Fc8ib0qbij2DSpg jVAapY/zRB+mjMB7ZmYdT3iVGQrQQEkQBMq0vrXZqnZyj3PuvPmE6AMj7MuQ8R5r 85Hj2Kvn2Ni4Ioxnz4h5grO5XI4cjDvNlrY4tlrpW/WHmAMZe4jEVJo3pbchlXbn J3bs2AWiI0J/yEnlcQLjIAgv9mQpFIJLAl8OYj6nSL7Y9xzJjGdVngCB6udS35J1 Bv9mEueZ77YFzBxBJNB+nZFuR7EFDFu94HMqLWDhhIod8432dmHl2m9FzM4YjjlP 3nwxgM0ZrQZZ =tQiH -END PGP SIGNATURE End Message ---
Bug#920854: marked as done (mariadb-10.1: FTBFS on s390x (test failure))
Your message dated Thu, 18 Apr 2019 17:32:51 + with message-id and subject line Bug#920854: fixed in mariadb-10.1 10.1.38-0+deb9u1 has caused the Debian Bug report #920854, regarding mariadb-10.1: FTBFS on s390x (test failure) 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.) -- 920854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.1 Version: 10.1.37-0+deb9u1 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: affects -1 + release.debian.org security.debian.org The mariadb-10.1 package on security.d.o doesn't build on s390x, one test fails: > CURRENT_TEST: unit.pcre_test > > PCRE C library tests using test data from /<>/pcre/testdata > PCRE version 8.42 2018-03-20 > > Testing 8-bit library > > Test 1: Main functionality (Compatible with Perl >= 5.10) > OK > OK with study > Test 2: API, errors, internals, and non-Perl stuff (not UTF-8) > Segmentation fault > > ** Test 2 requires a lot of stack. If it has crashed with a > ** segmentation fault, it may be that you do not have enough > ** stack available by default. Please see the 'pcrestack' man > ** page for a discussion of PCRE's stack usage. > > - saving '/<>/builddir/mysql-test/var/1/log/unit.pcre_test/' to > '/<>/builddir/mysql-test/var/log/unit.pcre_test/' > > Retrying test unit.pcre_test, attempt(2/3)... > > unit.pcre_test w1 [ retry-fail ] > Test ended at 2018-11-15 12:08:22 > > CURRENT_TEST: unit.pcre_test > > PCRE C library tests using test data from /<>/pcre/testdata > PCRE version 8.42 2018-03-20 > > Testing 8-bit library > > Test 1: Main functionality (Compatible with Perl >= 5.10) > OK > OK with study > Test 2: API, errors, internals, and non-Perl stuff (not UTF-8) > Segmentation fault > > ** Test 2 requires a lot of stack. If it has crashed with a > ** segmentation fault, it may be that you do not have enough > ** stack available by default. Please see the 'pcrestack' man > ** page for a discussion of PCRE's stack usage. > > - saving '/<>/builddir/mysql-test/var/1/log/unit.pcre_test/' to > '/<>/builddir/mysql-test/var/log/unit.pcre_test/' > > Test unit.pcre_test has failed 2 times, no more retries! Apparently such failures are somehow expected, can we disable that test if not fix it? Cheers, Julien --- End Message --- --- Begin Message --- Source: mariadb-10.1 Source-Version: 10.1.38-0+deb9u1 We believe that the bug you reported is fixed in the latest version of mariadb-10.1, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otto Kekäläinen (supplier of updated mariadb-10.1 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: Tue, 16 Apr 2019 14:56:50 +0300 Source: mariadb-10.1 Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data Architecture: source Version: 10.1.38-0+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Otto Kekäläinen Description: libmariadbclient-dev - MariaDB database development files libmariadbclient-dev-compat - MariaDB database development files (libmysqlclient compatibility) libmariadbclient18 - MariaDB database client library libmariadbd-dev - MariaDB embedded database, development files libmariadbd18 - MariaDB embedded database, shared library mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.1 - MariaDB database client binaries mariadb-client-core-10.1 - MariaDB database core client binaries mariadb-common -
Bug#912848: marked as done (mariadb-10.1: CVE-2018-3282 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156 CVE-2018-3251)
Your message dated Thu, 18 Apr 2019 17:32:18 + with message-id and subject line Bug#912848: fixed in mariadb-10.1 10.1.37-0+deb9u1 has caused the Debian Bug report #912848, regarding mariadb-10.1: CVE-2018-3282 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156 CVE-2018-3251 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.) -- 912848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.1 Version: 10.1.20-1 Severity: grave Tags: security upstream >From https://mariadb.com/kb/en/library/mariadb-10137-release-notes/ and fixed in 10.1.37: Fixes for the following security vulnerabilities: CVE-2018-3282 CVE-2016-9843 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156 CVE-2018-3251 (although the CVE-2016-9843 is for zlib, so not tracked here). Regards, Salvatore --- End Message --- --- Begin Message --- Source: mariadb-10.1 Source-Version: 10.1.37-0+deb9u1 We believe that the bug you reported is fixed in the latest version of mariadb-10.1, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otto Kekäläinen (supplier of updated mariadb-10.1 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, 08 Aug 2018 19:32:41 +0300 Source: mariadb-10.1 Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data Architecture: source Version: 10.1.37-0+deb9u1 Distribution: stretch-security Urgency: high Maintainer: Debian MySQL Maintainers Changed-By: Otto Kekäläinen Description: libmariadbclient-dev - MariaDB database development files libmariadbclient-dev-compat - MariaDB database development files (libmysqlclient compatibility) libmariadbclient18 - MariaDB database client library libmariadbd-dev - MariaDB embedded database, development files libmariadbd18 - MariaDB embedded database, shared library mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.1 - MariaDB database client binaries mariadb-client-core-10.1 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.1 - MariaDB database server binaries mariadb-server-core-10.1 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 885345 912848 Changes: mariadb-10.1 (10.1.37-0+deb9u1) stretch-security; urgency=high . * SECURITY UPDATE: New upstream release 10.1.37. Includes fixes for the following security vulnerabilities (Closes: #912848); - CVE-2018-3282 - CVE-2018-3251 - CVE-2018-3174 - CVE-2018-3156 - CVE-2018-3143 - CVE-2016-9843 * Add (and rename) new man pages * Add Gitlab-CI definition file that can test each commit to this repository * Fix d/control metadata to match status for Debian Stretch * Physically remove patches no longer in series and not applied anyway * Fix wrong-path-for-interpreter in
Bug#927292: marked as done (libqb: Breaks applications not running as root (for example pacemaker-based AKA cib))
Your message dated Thu, 18 Apr 2019 17:18:39 + with message-id and subject line Bug#927292: fixed in libqb 1.0.4-2 has caused the Debian Bug report #927292, regarding libqb: Breaks applications not running as root (for example pacemaker-based AKA cib) 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.) -- 927292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. --- End Message --- --- Begin Message --- Source: libqb Source-Version: 1.0.4-2 We believe that the bug you reported is fixed in the latest version of libqb, 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. Ferenc Wágner (supplier of updated libqb 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: Thu, 18 Apr 2019 18:38:20 +0200 Source: libqb Architecture: source Version: 1.0.4-2 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Ferenc Wágner Closes: 927292 Changes: libqb (1.0.4-2) unstable; urgency=medium . * [55468ba] tests: let ipcserver clean up /dev/shm after ipcclient finishes * [0e7a72d] New patch: Errors are represented as negative values * [5878100] New patch: Allow group access to the IPC directory (Closes: #927292) * [3365b9d] New patch: Make it impossible to truncate or overflow the connection description * [7063176] New patch: Let remote_tempdir() assume a NUL-terminated name Checksums-Sha1: 383e5c166466524e81f2a60d3af5004cda4bdae2 2423 libqb_1.0.4-2.dsc 798ee4c758348ca807d595e9ae47f10693c39dde 16468 libqb_1.0.4-2.debian.tar.xz 51d52bd1a24ad23df7c2412c64f50a35500d2511 8994 libqb_1.0.4-2_amd64.buildinfo Checksums-Sha256: 91040f3c2142193bd15bb0a55e54dc7298f8e6ed6602096aafa07c7b32ea2ab9 2423 libqb_1.0.4-2.dsc 3d1a65accc27dff3fad34776d752178f7d17d01b01760041fa780b1b2dc3e3aa 16468 libqb_1.0.4-2.debian.tar.xz d669139ca6c8b6fbef8581b43df952377bd8942bf0956963d99cdb44605a3b90 8994 libqb_1.0.4-2_amd64.buildinfo Files: 9d6f3efc8c2c41fca0050f3c50ec35c9 2423 libs optional libqb_1.0.4-2.dsc a87bc6a7508c853aec9f57b1e6a7a47c 16468 libs optional libqb_1.0.4-2.debian.tar.xz 58c866442abc342d93c20b2d43c31de1 8994 libs optional libqb_1.0.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAly4qtcACgkQOsj3Fkd+ 2yM1uw//c6USdbjai2yzmaZeJjacDNFrMzZhLdr1UCuFQclaZO7TqPWzaooS0b1o xxbnUQo//rP5XBcX6TAE3xTb2nMfOxWuftV7xVmKH521UuESGuQO2IBJ+H1xwner 5h/0ubJRsMV3n8oxXU0maeJiHf2o5mJriehaL44KRNd24CqI23aHlrLWhEDs8zZ7 82CdJB7wjkDTYXVx4C79zuECCmbnkpGbIU8Uel+6qhxHZuz3gNV5YC/9j6syKkzw 2V4ujA5OSFR4Qtl0Qwo84QQFvJqF3ojwjibDcpL4jQe5mz1EAO+w5h1WEHEIxfij GPrhQZ11wOwx9NTm//BPm8MGx54uvJXQDqsx9NUyRrGOvaXwZB/0nNL+JAHcVjfp WnN+c84djrixhsmsw9HQRuEFRSyaeNCuZnplJeK+1l1An0El9cp5Zp8LGuqzOijh IHuao1yXaB1gIoi8Tbm5EDJrwPep6KW0Yr4PYGkfLSYaV9s3dIS3bHfYulxb8fii qjmJXI4SarWAozFJxA+M3ZQJrUed4rrfNNPmYxf8i/Kn9DGCJXHsCorr783hZfNL JRYiNllXb03E64lBnL5IHufZowg3QSexag4+7NZVGrKXt9P6UFICaNxh5/BsXSJS Hz47/RULMeWacmHdEExeSQevElLrapcgwcsZWzLi3km/ZcCTyKo= =q0ng -END PGP SIGNATURE End Message ---
Bug#926728: marked as done (Removing the package breaks the alternative on usr-merge system)
Your message dated Thu, 18 Apr 2019 16:48:35 + with message-id and subject line Bug#926728: fixed in ebtables 2.0.10.4+snapshot20181205-3 has caused the Debian Bug report #926728, regarding Removing the package breaks the alternative on usr-merge system 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.) -- 926728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ebtables Version: 2.0.10.4+snapshot20181205-2 Severity: serious Hello, On system with usr-merge, removing ebtables breaks the alternative. The postinst script install symlinks from /sbin to /usr/sbin, in the prerm script these symlinks are removed. BUT ebtables also add itself as an alternative for ebtables implementations. That means that the symlinks installed by update-alternatives are rm when the package is removed. Not too sure how to fix this, maybe the prerm script should check if the symlinks directly point to a real file and only remove them in that case? Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ebtables depends on: ii libc6 2.28-8 Versions of packages ebtables recommends: ii iptables 1.8.2-4 ii kmod 26-1 ebtables suggests no packages. --- End Message --- --- Begin Message --- Source: ebtables Source-Version: 2.0.10.4+snapshot20181205-3 We believe that the bug you reported is fixed in the latest version of ebtables, 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. Alberto Molina Coballes (supplier of updated ebtables package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Apr 2019 18:23:43 + Source: ebtables Architecture: source Version: 2.0.10.4+snapshot20181205-3 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Alberto Molina Coballes Closes: 926728 Changes: ebtables (2.0.10.4+snapshot20181205-3) unstable; urgency=medium . [ Arturo Borrero Gonzalez ] * [9b474c7] src:ebtables: add salsa CI integration . [ Alberto Molina Coballes ] * [5dbd22d] Remove /sbin symlinks on not usr-merged systems (Closes: #926728) Checksums-Sha1: ea3eed3e6343f8a1dac54e82180afe5b94df2dc6 2091 ebtables_2.0.10.4+snapshot20181205-3.dsc 2c4bb1deeb62163eea80a0f652c9e05637dd7453 9696 ebtables_2.0.10.4+snapshot20181205-3.debian.tar.xz 45985e264c59fc2059ebe7ed04aa0ffbc0b10e4e 5457 ebtables_2.0.10.4+snapshot20181205-3_amd64.buildinfo Checksums-Sha256: de24cc79e6d7881c9c5b7db72385a7f70d774023dc06e6c640d1b1d396399574 2091 ebtables_2.0.10.4+snapshot20181205-3.dsc 789a86eb2600455ed6c5c1e0a52fd8e5c185149b9d25033fcdadab4e1f9593c6 9696 ebtables_2.0.10.4+snapshot20181205-3.debian.tar.xz da54d199186bae4c7412823007521b3f07dab2e7b4cb16615d842e8f84e7 5457 ebtables_2.0.10.4+snapshot20181205-3_amd64.buildinfo Files: c6739bea6c3458887c598269a8f1b2f3 2091 net optional ebtables_2.0.10.4+snapshot20181205-3.dsc 660259958f18509fa5859371f7b0d686 9696 net optional ebtables_2.0.10.4+snapshot20181205-3.debian.tar.xz fab9f660d818671f952738476922952f 5457 net optional ebtables_2.0.10.4+snapshot20181205-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAly4pQMACgkQaOcTmB0V Ffis3w//XcJ8g9uucVEZGloIgQf4VLRJnZ8GQmlY/LxMYf0tsv2Iy50EESvK/6+/ kqlqAVIN+rG3UhAKD2ixHBBohppSwY8ke0fwcsxhyX1dTggdl47gI2PESowKQ5wP Wp0YJWT9iw825tUzRlIfEI/+K03ZivxgKD5Yhku8zeinZ/g9DbuOTTScc8yRa+il QzeRDawNTgKqqepbjihzbpnTjU/72x/4ZetQBUaEbibwaHdgL+O8hXmT+LaGOCYP qHy8UyLmtfYedKnFzX2FbRrPp61IG13TVSfrhuXYOahUlg6bcnNjRj88/mnRhZWv
Bug#926728: marked as done (Removing the package breaks the alternative on usr-merge system)
Your message dated Thu, 18 Apr 2019 16:48:29 + with message-id and subject line Bug#926728: fixed in arptables 0.0.4+snapshot20181021-4 has caused the Debian Bug report #926728, regarding Removing the package breaks the alternative on usr-merge system 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.) -- 926728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ebtables Version: 2.0.10.4+snapshot20181205-2 Severity: serious Hello, On system with usr-merge, removing ebtables breaks the alternative. The postinst script install symlinks from /sbin to /usr/sbin, in the prerm script these symlinks are removed. BUT ebtables also add itself as an alternative for ebtables implementations. That means that the symlinks installed by update-alternatives are rm when the package is removed. Not too sure how to fix this, maybe the prerm script should check if the symlinks directly point to a real file and only remove them in that case? Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ebtables depends on: ii libc6 2.28-8 Versions of packages ebtables recommends: ii iptables 1.8.2-4 ii kmod 26-1 ebtables suggests no packages. --- End Message --- --- Begin Message --- Source: arptables Source-Version: 0.0.4+snapshot20181021-4 We believe that the bug you reported is fixed in the latest version of arptables, 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. Alberto Molina Coballes (supplier of updated arptables 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 15:24:53 + Source: arptables Architecture: source Version: 0.0.4+snapshot20181021-4 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Alberto Molina Coballes Closes: 926728 Changes: arptables (0.0.4+snapshot20181021-4) unstable; urgency=medium . [ Arturo Borrero Gonzalez ] * [88703e1] src:arptables: add salsa CI integration . [ Alberto Molina Coballes ] * [eb7a44d] d/arptables.prerm: Remove /sbin symlinks on not usr-merged systems (Closes: #926728) Checksums-Sha1: 4fd10965b2e1d1183a1c6a585b4520b8f9b3522f 2073 arptables_0.0.4+snapshot20181021-4.dsc 26642e86fe7c25f1fb9801d43520bc40b58d140d 4968 arptables_0.0.4+snapshot20181021-4.debian.tar.xz 7873179aefa38635169032f5e4c5a1d53a1c0800 5440 arptables_0.0.4+snapshot20181021-4_amd64.buildinfo Checksums-Sha256: 74ef96250cce6883773c247121e2899e4365a2ffc14a16b37011af28477823c6 2073 arptables_0.0.4+snapshot20181021-4.dsc c9cdfb5daa358bc32129e233576c32b944dfb7a3c3997bd91a2884f510a9ca15 4968 arptables_0.0.4+snapshot20181021-4.debian.tar.xz 2361ee1fade2e46b7e1b95633bcd946367e1420ef4142f22f254302c473bdb8f 5440 arptables_0.0.4+snapshot20181021-4_amd64.buildinfo Files: 7307ead7487e2179b9e7917b09a778dd 2073 net optional arptables_0.0.4+snapshot20181021-4.dsc 635b42ff034cdc01b46ee2df9fd72d08 4968 net optional arptables_0.0.4+snapshot20181021-4.debian.tar.xz 35e757769382d06520a16764a706fc06 5440 net optional arptables_0.0.4+snapshot20181021-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAly4pacACgkQaOcTmB0V FfjIJA//SCgj/R/j9rzsc1qKNZz9GpuWHPoRKS661RIHEfjGewEu7pokbLPU8Hjd /ee4ey3Ub5cUNQsCW0v0N1HR//CIp1YFwNX0T0MEEszy7bEjqv2ZqyROn3vQwGpD KYNZYMAhpqrT/5Y208FZZfIasV69lX5rsJerZfWYJWn+a2urekrXZS6jcc70LWwT AfVmLd42zscEbvMMbFrlVhSDB/FRZxKfeNgSwjIUsuF+gKDDJegGjKrR46RfOjtv XKw98ojxMOs7MIqx+5gAxhK1RSujBUPMMxJVbwOGOSuICAfgpc4tGi6+4v0fJ8Cm
Bug#927307: libgraphicsmagick breaks gnudatalanguage
Between the version which worked and the version which is failing, the implementation of magick/resource.c was changed to allocate a semaphore for each resource limit rather than using a single global semaphore across all resource limits. Something else which changed since the changeset version which is reported as "working" is that when an Image is constructed it caches certain resource limits to be used later. It does this in order to improve performance. This means that the resource limit code is being invoked now whereas if an Image was statically constructed, it would not have been invoked before. There is no proper fix other than to make sure that InitializeMagick() has been invoked before any other API elments are used. 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#921838: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:152: installing './compile'
configure.ac:43: installing './missing'
[... snipped ...]
d on input line 40.
) (./group__PPL__C__interface.tex)
Underfull \vbox (badness 7740) has occurred while \output is active [17]
[18] (./group__Init.tex
Underfull \hbox (badness 1) detected at line 35
[][][]
Underfull \hbox (badness 1) detected at line 48
[][][]
[19]) [20] (./group__Version.tex [21]) [22] (./group__Error.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (1.62299pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]O[]U[]T[][][][]O[]F[][]
[][]M[]E[]M[]O[]RY[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]V[]A[]L[]
I[]D[][][][]A[]R[]G[]U[]M[]E[]NT[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]D
[]O[]M[]
Overfull \hbox (1.35289pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]A[]R[]I[]T[]H[]M[]E[]T[]I[]C[][][][]O[]V[]E[
]R[]F[]L[]OW[][], [][]P[]P[]L[][][][]S[]T[]D[]I[]O[][][][]E[]R[]R[]OR[][], [][]
P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]T[]E[]R[]N[]A[]L[][][][]E[]R[]R[]OR[]
[], [][]P[]
! Missing } inserted.
}
l.88 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.88 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/doc/user-configured-c-interface.latex-dir'
make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
dh_auto_build: cd doc && make -j1 user-configured returned exit code 2
make[1]: *** [debian/rules:75: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
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/ppl.html
where you can get a full build log if you need it.
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: texlive-extra
Source-Version: 2018.20190227-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: Thu, 18 Apr 2019 15:20:25 +0900
Source: texlive-extra
Binary:
Bug#921783: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graphite2
Version: 1.3.13-7
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 python3 --buildsystem=cmake --builddirectory=build
dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE:STRING=Release
-DGRAPHITE2_NTRACING:BOOL=ON -DLIB_SUFFIX=/x86_64-linux-gnu
-DPYTHON_EXECUTABLE=/usr/bin/python3
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_BUILD_TYPE:STRING=Release -DGRAPHITE2_NTRACING:BOOL=ON
-DLIB_SUFFIX=/x86_64-linux-gnu -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.2",
minimum required is "3.6")
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
[... snipped ...]
LaTeX Warning: Reference `Font_8h' on page 5 undefined on input line 3.
LaTeX Warning: Reference `Log_8h' on page 5 undefined on input line 4.
LaTeX Warning: Reference `Segment_8h' on page 5 undefined on input line 5.
LaTeX Warning: Reference `Types_8h' on page 5 undefined on input line 6.
) [5] [6]
Chapter 4.
(./structgr__face__ops.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd) [7])
(./structgr__faceinfo.tex
! Missing } inserted.
}
l.84 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.84 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[6]: *** [Makefile:6: refman.pdf] Error 1
make[6]: Leaving directory '/<>/build/doc/doxygen/latex'
make[5]: *** [doc/CMakeFiles/docs.dir/build.make:90:
doc/doxygen/latex/refman.pdf] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [CMakeFiles/Makefile2:1048: doc/CMakeFiles/docs.dir/all] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:1055: doc/CMakeFiles/docs.dir/rule] Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:412: docs] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_build: cd build && make -j1 docs returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
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/graphite2.html
where you can get a full build log if you need it.
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: texlive-extra
Source-Version: 2018.20190227-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the
Bug#920459: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:toulbar2
Version: 1.0.0+dfsg3-1.1
Severity: serious
Tags: sid buster
toulbar2 ftbfs in unstable
[...]
*geometry* driver: auto-detecting
*geometry* detected driver: pdftex
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./index.tex
(/usr/share/texlive/texmf-dist/tex/latex/wasysym/uwasy.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
! Missing } inserted.
}
l.7 \end{longtabu}
?
! Emergency stop.
}
l.7 \end{longtabu}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu/latex'
make[3]: *** [CMakeFiles/doc.dir/build.make:71: doc] Error 2
make[3]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/doc.dir/all] Error 2
[...]
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2018.20190227-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: Thu, 18 Apr 2019 15:20:25 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc
texlive-science texlive-science-doc
Architecture: source all
Version: 2018.20190227-2
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers
Changed-By: Norbert Preining
Description:
texlive-bibtex-extra - TeX Live: BibTeX additional styles
texlive-extra-utils - TeX Live: TeX auxiliary programs
texlive-font-utils - TeX Live: Graphics and font utilities
texlive-fonts-extra - TeX Live: Additional fonts
texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
texlive-fonts-extra-links - TeX Live:
texlive-formats-extra - TeX Live: Additional formats
texlive-games - TeX Live: Games typesetting
texlive-humanities - TeX Live: Humanities packages
texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
texlive-latex-extra - TeX Live: LaTeX additional packages
texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
texlive-music - TeX Live: Music packages
texlive-plain-generic - TeX Live: Plain (La)TeX packages
texlive-pstricks - TeX Live: PSTricks
texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
texlive-publishers - TeX Live: Publisher styles, theses, etc.
texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
texlive-science - TeX Live: Mathematics, natural sciences, computer science
package
texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 920459
Changes:
texlive-extra (2018.20190227-2) unstable; urgency=medium
.
* more tabu fixes (Closes: #920459) (reopened bug, since cloning is not
possible, thanks BTS)
Checksums-Sha1:
34fd36e6bdbb176305aa121bda577b05610e66c0 3390
Bug#921779: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 + with message-id and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2 has caused the Debian Bug report #920459, regarding tabu: breaks with color and/or xcolor when spread or negative X coefficients are used 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:doxygen Version: 1.8.13-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh_testdir /usr/bin/make -C jquery install make[1]: Entering directory '/<>/jquery' java -jar /usr/share/yui-compressor/yui-compressor.jar jquery-1.7.1.js > jquery-1.7.1-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.core.js > jquery.ui-1.8.18.core-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.widget.js > jquery.ui-1.8.18.widget-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.mouse.js > jquery.ui-1.8.18.mouse-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.resizable.js > jquery.ui-1.8.18.resizable-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ba-1.3-hashchange.js > jquery.ba-1.3-hashchange-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.scrollTo-1.4.2.js > jquery.scrollTo-1.4.2-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.powertip-1.2.0.js > jquery.powertip-1.2.0-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-0.2.3.touch-punch.js > jquery.ui-0.2.3.touch-punch-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.smartmenus-1.0.0.js > jquery.smartmenus-1.0.0-min.js [... snipped ...] [100%] Generating trouble.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/trouble.doc /<>/build/doc/ [100%] Generating xmlcmds.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/xmlcmds.doc /<>/build/doc/ [100%] Generating Latex and HTML documentation. cd /<>/build/doc && /<>/build/bin/doxygen This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./_formulas.tex LaTeX2e <2018-12-01> make[4]: Leaving directory '/<>/build' [100%] Built target run_doxygen /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/depend make[4]: Entering directory '/<>/build' cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/doc /<>/build /<>/build/doc /<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake --color= Dependee "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Dependee "/<>/build/doc/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Scanning dependencies of target doxygen_pdf make[4]: Leaving directory '/<>/build' /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/build make[4]: Entering directory '/<>/build' [100%] Generating Doxygen Manual PDF. cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/doxygen_manual.tex . cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/manual.sty . cd /<>/build/latex && /usr/bin/epstopdf /<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf cd /<>/build/latex && /usr/bin/pdflatex -shell-escape doxygen_manual.tex This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex) \write18 enabled. entering extended mode (./doxygen_manual.tex LaTeX2e <2018-12-01> make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1 make[4]: Leaving directory '/<>/build' make[3]: *** [CMakeFiles/Makefile2:445: doc/CMakeFiles/doxygen_pdf.dir/all] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [CMakeFiles/Makefile2:484: doc/CMakeFiles/docs.dir/rule] Error 2 make[2]: Leaving directory '/<>/build' make[1]: *** [Makefile:301: docs] Error 2 make[1]: Leaving directory '/<>/build' make: *** [debian/rules:60: build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2
Bug#921272: marked as done (texlive-latex-extra: package tabu broken when xcolor is used)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding texlive-latex-extra: package tabu broken when xcolor is used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2018.20190131-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Compiling the LaTeX doxygen-generated documentation for debian package
toulbar2 fails.
* What exactly did you do (or not do) that was effective (or
ineffective)?
A minimal latex file does not compile anymore on texlive (did previously)
* What was the outcome of this action?
An error (missing brace) is raised.
* What outcome did you expect instead?
A PDF file should be generated by pdflatex
*** End of the template - remove these template lines ***
-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.
In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.
*** The Debian TeX Team is *not* a LaTeX Help Desk ***
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.
Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.
Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
http://www.minimalbeispiel.de/mini-en.html (english)
or
http://www.minimalbeispiel.de/mini.html (german)
##
minimal input file
\documentclass{article}
\usepackage{array}
\usepackage[table]{xcolor}
\usepackage{longtable}
\usepackage{tabu}
\begin{document}
\begin{longtabu}{X[-1]X[-1]}
\textbf{Cost Function Network Solver} & toulbar2
\end{longtabu}
\end{document}
##
other files
##
List of ls-R files
-rw-r--r-- 1 root root 1201 Feb 3 17:49 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep 2 12:32 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 31 03:53 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 31 03:53 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
-rw-r--r-- 1 root root 475 Feb 3 17:49 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 31 03:53 /usr/share/texmf/web2c/fmtutil.cnf ->
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jan 31 03:53 /usr/share/texmf/web2c/updmap.cfg ->
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Feb 3 17:49
/var/lib/texmf/tex/generic/config/language.dat
##
Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Aug 17 2017 mktex.cnf
-rw-r--r-- 1 root root 475 Feb 3 17:49 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.12-041812-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell:
Bug#924829: marked as done (caffe: FTBFS: Fatal error occurred, no output PDF file produced!)
Your message dated Thu, 18 Apr 2019 15:00:52 + with message-id and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2 has caused the Debian Bug report #920459, regarding caffe: FTBFS: Fatal error occurred, no output PDF file produced! 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caffe Version: 1.0.0+git20180821.99bd997-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory > '/<>/caffe-1.0.0+git20180821.99bd997/doxygen/latex' > rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl > refman.pdf > pdflatex refman > This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./refman.tex > LaTeX2e <2018-12-01> > (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls > Document Class: book 2018/09/03 v1.4i Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty > > Package fixltx2e Warning: fixltx2e is not required with releases after 2015 > (fixltx2e)All fixes are now in the LaTeX kernel. > (fixltx2e)See the latexrelease package for details. > > ) (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty) (./doxygen.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty) > (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def) > (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tabu/tabu.sty > (/usr/share/texlive/texmf-dist/tex/latex/varwidth/varwidth.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjustbox.sty > (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjcalc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/trimclip.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg))) > (/usr/share/texlive/texmf-dist/tex/latex/collectbox/collectbox.sty) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/tc-pdftex.def)) > (/usr/share/texlive/texmf-dist/tex/latex/ifoddpage/ifoddpage.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def > (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu))) > (/usr/share/texlive/texmf-dist/tex/latex/wasysym/wasysym.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/helvet.sty) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/courier.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/sectsty/sectsty.sty) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) >
Bug#920621: marked as done (texlive-base: breaks build of forthcoming doxygen 1.8.15)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding texlive-base: breaks build of forthcoming doxygen 1.8.15
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: 2018.20190126-1
Severity: important
Dear Maintainer,
I am preparing the next relase of doxygen (1.8.15).
Last week it built fine with texlive-base 2018.20181214-1.
I tried today with 2018.20190126-1 and it fails.
You can see the trace of the successful build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680
and of the failed build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/115667
I attach the files necessary to reproduce (I took the files in
doxygen/debian/build at the end of the failed build and blanked a few to reduce
the size of the attachment).
Extract then launch:
/usr/bin/pdflatex -shell-escape doxygen_manual.tex
While processing Chapter 3 (starting.tex) pdflatex from texlive-base
2018.20190126-1 prints a lot of these messages:
]
! Missing } inserted.
}
l.74 \end{longtabu}
I've inserted something that you may have forgotten.
(See the above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! Missing } inserted.
}
l.74 \end{longtabu}
I've inserted something that you may have forgotten.
(See the above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! Missing } inserted.
}
l.74 \end{longtabu}
I've inserted something that you may have forgotten.
(See the above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! Missing \cr inserted.
\cr
l.74 \end{longtabu}
I'm guessing that you meant to end an alignment here.
! Misplaced \cr.
\cr
l.74 \end{longtabu}
I can't figure out why you would want to use a tab mark
or \cr or \span just now. If something like a right brace
up above has ended a previous alignment prematurely,
you're probably due for more error messages, and you
might try typing `S' now just to see what is salvageable.
then bails out with exit code 1 and no PDF file.
If I try that with pdflatex from texlive-base all 2018.20181214-1, it succeeds.
Thanks for any help,
Paolo
##
List of ls-R files
-rw-r--r-- 1 root root 1201 Jan 27 10:43 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep 2 14:32 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 25 23:06 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 25 23:06 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
-rw-r--r-- 1 root root 475 Jan 27 10:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 25 23:06 /usr/share/texmf/web2c/fmtutil.cnf ->
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jan 25 23:06 /usr/share/texmf/web2c/updmap.cfg ->
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Jan 27 10:43
/var/lib/texmf/tex/generic/config/language.dat
##
Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep 2 14:32 mktex.cnf
-rw-r--r-- 1 root root 475 Jan 27 10:43 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via
Bug#921776: marked as done (bliss: FTBFS (LaTeX error))
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding bliss: FTBFS (LaTeX error)
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bliss
Version: 0.73-2
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 autoreconf --builddirectory=_build --parallel
dh_update_autotools_config -i -O--builddirectory=_build -O--parallel
dh_autoreconf -i -O--builddirectory=_build -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:19: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/config.guess'
[... snipped ...]
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 185/65536 hits=1285 misses=221
finished...
cd /<>/_build/DEBIAN/doc/html && { \
rm -f *.md5 jquery.js ; \
rdfind -outputname /dev/null -makesymlinks true . ; \
symlinks -r -c -s -v . ; \
ln -sf /usr/share/javascript/jquery/jquery.js ; \
}
Now scanning ".", found 60 files.
Now have 60 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 384954 bytes or 376 KiB
Removed 60 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making results file /dev/null
Now making symbolic links. creating
Making 0 links.
cd /<>/_build/DEBIAN/doc/latex && { \
make && mv refman.pdf bliss_refman.pdf ; \
}
make[3]: Entering directory '/<>/_build/DEBIAN/doc/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:30: doc] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:16: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
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/bliss.html
where you can get a full build log if you need it.
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: texlive-extra
Source-Version: 2018.20190227-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact
Bug#921802: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:primesieve
Version: 7.3+ds-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 --builddirectory=_build
dh_update_autotools_config -i -O--builddirectory=_build
dh_autoreconf -i -O--builddirectory=_build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
[... snipped ...]
LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.
LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.
LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.
LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.
LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input
line 7.
) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
}
l.175 \end{DoxyParams}
?
! Emergency stop.
}
l.175 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
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/primesieve.html
where you can get a full build log if you need it.
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: texlive-extra
Source-Version: 2018.20190227-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: Thu, 18 Apr 2019 15:20:25 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra
Bug#921789: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librostlab-blast
Version: 1.0.1-9
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:7: installing './compile'
configure.ac:5: installing './missing'
[... snipped ...]
LaTeX Warning: Reference `blast-parser-parser_8h' on page 7 undefined on input
line 5.
LaTeX Warning: Reference `blast-parser-position_8h' on page 7 undefined on inpu
t line 6.
LaTeX Warning: Reference `blast-parser-stack_8h' on page 7 undefined on input l
ine 7.
LaTeX Warning: Reference `blast-result_8h' on page 7 undefined on input line 8.
) [7] [8]
Chapter 5.
(./namespacerostlab.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
LaTeX Font Warning: Font shape `T1/pcr/bc/n' undefined
(Font) using `T1/pcr/m/n' instead on input line 27.
[9]) (./namespacerostlab_1_1blast.tex [10] [11] [12] [13] [14]
! Missing } inserted.
}
l.253 \end{DoxyParams}
?
! Emergency stop.
}
l.253 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:902: ../doxygen-doc/librostlab-blast.pdf] Error 1
make[2]: Leaving directory '/<>/lib'
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
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/librostlab-blast.html
where you can get a full build log if you need it.
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: texlive-extra
Source-Version: 2018.20190227-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: Thu, 18 Apr 2019 15:20:25 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc
texlive-science texlive-science-doc
Architecture: source all
Version: 2018.20190227-2
Bug#921299: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Thu, 18 Apr 2019 15:00:52 + with message-id and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2 has caused the Debian Bug report #920459, regarding tabu: breaks with color and/or xcolor when spread or negative X coefficients are used 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caffe Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ~ --- End Message --- --- Begin Message --- Source: texlive-extra Source-Version: 2018.20190227-2 We believe that the bug you reported is fixed in the latest version of texlive-extra, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated texlive-extra 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: Thu, 18 Apr 2019 15:20:25 +0900 Source: texlive-extra Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc texlive-science texlive-science-doc Architecture: source all Version: 2018.20190227-2 Distribution: unstable Urgency: medium Maintainer: Debian TeX Maintainers Changed-By: Norbert Preining Description: texlive-bibtex-extra - TeX Live: BibTeX additional styles texlive-extra-utils - TeX Live: TeX auxiliary programs texlive-font-utils - TeX Live: Graphics and font utilities texlive-fonts-extra - TeX Live: Additional fonts texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra texlive-fonts-extra-links - TeX Live: texlive-formats-extra - TeX Live: Additional formats texlive-games - TeX Live: Games typesetting texlive-humanities - TeX Live: Humanities packages texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities texlive-latex-extra - TeX Live: LaTeX additional packages texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra texlive-music - TeX Live: Music packages texlive-plain-generic - TeX Live: Plain (La)TeX packages texlive-pstricks - TeX Live: PSTricks texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks texlive-publishers - TeX Live: Publisher styles, theses, etc. texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers texlive-science - TeX Live: Mathematics, natural sciences, computer science package texlive-science-doc - TeX Live: Documentation files for texlive-science Closes: 920459 Changes: texlive-extra (2018.20190227-2) unstable; urgency=medium . * more tabu fixes (Closes: #920459) (reopened bug, since cloning is not possible, thanks BTS) Checksums-Sha1: 34fd36e6bdbb176305aa121bda577b05610e66c0 3390 texlive-extra_2018.20190227-2.dsc 059f4da95a6459cf8baec5e81755825e24b2f156 163604 texlive-extra_2018.20190227-2.debian.tar.xz bf3ddd36dd352b835522d7eac0f0772624cefc5b 61682504 texlive-bibtex-extra_2018.20190227-2_all.deb a050e33d06f8bc8f922e12ac992a028939408652 39445600 texlive-extra-utils_2018.20190227-2_all.deb
Bug#926305: nis startup scripts are completely broken
* Anton Ivanov [2019-04-18 15:05 +0100]: > That is not an advice. > > If nscd is a required dependency, NIS should bring it in. This is not a "must have" > > Presently it is not. > > Still broken The advice is also mentioned in the changelog: * Drop -no-dbus from YPBINDARGS= in /etc/default/nis. We no longer build nis with NetworkManager/D-Bus support, so setting this option made ypbind fail to start. (Closes: #906436) So setting "YPBINDARGS=" in /etc/default/nis should be your first step to get nis working in buster ;-) Elimar -- Alles, was viel bedacht wird, wird bedenklich!;-) Friedrich Nietzsche signature.asc Description: PGP signature
Bug#926305: closed by Elimar Riesebieter (Re: Bug#926305: nis startup scripts are completely broken)
Please reopen. Advice is no replacement for a Depends in the package control file. As shipped the package is still broken and at the reported severity - breaking most of the system A. On 18/04/2019 14:48, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the nis package: #926305: nis startup scripts are completely broken It has been closed by Elimar Riesebieter . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Elimar Riesebieter by replying to this email. -- Anton R. Ivanov https://www.kot-begemot.co.uk/
Bug#926305: nis startup scripts are completely broken
That is not an advice. If nscd is a required dependency, NIS should bring it in. Presently it is not. Still broken A. On 18/04/2019 14:43, Elimar Riesebieter wrote: * Elimar Riesebieter [2019-04-03 11:06 +0200]: * Anton Ivanov [2019-04-03 09:43 +0100]: Package: nis Version: 3.17.1-3+b1 Severity: critical Justification: breaks unrelated software Dear Maintainer, Startup scripts are completely broken. Something in the systemd conversion/autogeneration. The ypbind binary is never started, the script goes into "backgrounded" and fails. From there on the system is unusable - you cannot log in, UIDs and groups do not resolve, etc. The same system operated correctly before buster upgrade and will operate correctly if ypbind is invoked from the command line. This looks like a pure systemd conversion issue of some sort. At my systems installing nscd helped. As well setting "YPBINDARGS=" in /etc/default/nis must be. This bug should be closed as there is no response from the reporter. As well it seems to be fixed following the advices given above, though. Elimar -- Anton R. Ivanov https://www.kot-begemot.co.uk/
Bug#926305: marked as done (nis startup scripts are completely broken)
Your message dated Thu, 18 Apr 2019 15:43:59 +0200 with message-id <20190418134359.t6sqscgqkem7i...@pippin.home.lxtec.de> and subject line Re: Bug#926305: nis startup scripts are completely broken has caused the Debian Bug report #926305, regarding nis startup scripts are completely broken 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.) -- 926305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nis Version: 3.17.1-3+b1 Severity: critical Justification: breaks unrelated software Dear Maintainer, Startup scripts are completely broken. Something in the systemd conversion/autogeneration. The ypbind binary is never started, the script goes into "backgrounded" and fails. From there on the system is unusable - you cannot log in, UIDs and groups do not resolve, etc. The same system operated correctly before buster upgrade and will operate correctly if ypbind is invoked from the command line. This looks like a pure systemd conversion issue of some sort. -- Package-specific info: NIS domain: home -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nis depends on: ii debconf [debconf-2.0] 1.5.71 ii hostname 3.21 ii libc6 2.28-8 ii libgdbm6 1.18.1-4 ii libsystemd0241-1 ii lsb-base 10.2019031300 ii make 4.2.1-1.2 ii netbase5.6 ii rpcbind [portmap] 1.2.5-0.3 nis recommends no packages. Versions of packages nis suggests: pn nscd -- Configuration Files: /etc/yp.conf changed [not included] -- debconf information: * nis/domain: home --- End Message --- --- Begin Message --- * Elimar Riesebieter [2019-04-03 11:06 +0200]: > * Anton Ivanov [2019-04-03 09:43 +0100]: > > > Package: nis > > Version: 3.17.1-3+b1 > > Severity: critical > > Justification: breaks unrelated software > > > > Dear Maintainer, > > > > Startup scripts are completely broken. Something in the systemd > > conversion/autogeneration. > > > > The ypbind binary is never started, the script goes into "backgrounded" and > > fails. From there > > on the system is unusable - you cannot log in, UIDs and groups do not > > resolve, etc. > > > > The same system operated correctly before buster upgrade and will operate > > correctly if > > ypbind is invoked from the command line. > > > > This looks like a pure systemd conversion issue of some sort. > > At my systems installing nscd helped. As well setting "YPBINDARGS=" > in /etc/default/nis must be. This bug should be closed as there is no response from the reporter. As well it seems to be fixed following the advices given above, though. Elimar -- >what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- signature.asc Description: PGP signature --- End Message ---
Bug#926305: nis startup scripts are completely broken
* Elimar Riesebieter [2019-04-03 11:06 +0200]: > * Anton Ivanov [2019-04-03 09:43 +0100]: > > > Package: nis > > Version: 3.17.1-3+b1 > > Severity: critical > > Justification: breaks unrelated software > > > > Dear Maintainer, > > > > Startup scripts are completely broken. Something in the systemd > > conversion/autogeneration. > > > > The ypbind binary is never started, the script goes into "backgrounded" and > > fails. From there > > on the system is unusable - you cannot log in, UIDs and groups do not > > resolve, etc. > > > > The same system operated correctly before buster upgrade and will operate > > correctly if > > ypbind is invoked from the command line. > > > > This looks like a pure systemd conversion issue of some sort. > > At my systems installing nscd helped. As well setting "YPBINDARGS=" > in /etc/default/nis must be. This bug should be closed as there is no response from the reporter. As well it seems to be fixed following the advices given above, though. Elimar -- >what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- signature.asc Description: PGP signature
Bug#927307: libgraphicsmagick breaks gnudatalanguage
On Thu, 18 Apr 2019, László Böszörményi wrote: #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 This problem would occur if the InitializeMagick() function is not called before using any other function. The InitializeMagick() function calls InitializeMagickResources() which allocates the semaphore discovered to be null. C++ adds the interesting wrinkle that statically-constructed objects are constructed before main() is even invoked. Since _dl_start_user() is reported at the bottom of the stack rather than main() this could be a C++ static construction issue, or a shared library constructor function issue. Between the version which worked and the version which is failing, the implementation of magick/resource.c was changed to allocate a semaphore for each resource limit rather than using a single global semaphore across all resource limits. For reasons unknown to me, I did not include a generalized resource limit function in Magick++. For purposes of fuzzing via oss-fuzz, I see that this code is used: Magick::InitializeMagick(nullptr); MagickLib::SetMagickResourceLimit(MagickLib::MemoryResource, 10); MagickLib::SetMagickResourceLimit(MagickLib::WidthResource, 2048); MagickLib::SetMagickResourceLimit(MagickLib::HeightResource, 2048); and this is diving into the C API after calling InitializeMagick(); 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#926351: python3-tesserocr: segfaults on import
Hi, On Fri, 5 Apr 2019 23:26:55 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= wrote: > Dear Maintainer, > just tried to help triaging this issue. Me too. > > Seems this is "expected" behaviour with LC_ALL not > set to "C". In the end it leads to this upstream bug: > > https://github.com/sirfz/tesserocr/issues/165 > > It contains some workarounds and more information. > Yes. There is a simplistic solution. Set 'locale' before 'import tesserocr' doing something like this: >>> import locale >>> locale.setlocale(locale.LC_ALL, 'C') 'C' >>> import tesserocr >>> Or adding some code, like here: https://github.com/WeblateOrg/weblate/commit/6724204977e7c466a463595736cc5299c8f01829 The workaround - set locale - is known. It is in debian/rules[0] file. But the user should be informed about it. [0] - https://sources.debian.org/src/python-tesserocr/2.4.0-4/debian/changelog/ BTW, CI tests never passed. And it is not a reproducible build. Two tests fail. - https://sources.debian.org/src/python-tesserocr/2.4.0-4/tests/test_api.py/#L227 - https://sources.debian.org/src/python-tesserocr/2.4.0-4/tests/test_api.py/#L275 The package was recently added to Debian. Low popcon. Regards, Herbert
Bug#927358: segemehl: Please stop building on any-i386
Package: segemehl Version: 0.3.4-1 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927359: tabix: Please stop building on any-i386
Package: tabix Version: 1.9-10 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927357: samtools: Please stop building on any-i386
Package: samtools Version: 1.9-4 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927356: qtltools: Please stop building on any-i386
Package: qtltools Version: 1.1+dfsg-3 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927354: libhts2: Please stop building on any-i386
Package: libhts2 Version: 1.9-10 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927353: libhts-dev: Please stop building on any-i386
Package: libhts-dev Version: 1.9-10 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927355: nanopolish: Please stop building on any-i386
Package: nanopolish Version: 0.11.0-2 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927352: delly: Please stop building on any-i386
Package: delly Version: 0.8.1-2 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Bug#927351: augustus: Please stop building on any-i386
Package: augustus Version: 3.3.2+dfsg-2 Severity: serious Hi, This package uses htslib, which is no longer supported on any-i386. #914991 removed the binaries on any-i386, but until any-i386 is removed from Architecture:, wanna-build will re-build the package, thereby reinstating the binaries on any-i386. Please upload a new version of the source package with any-i386 removed from Architecture: for this binary package. Regards, James
Processed: severity of 927301 is serious
Processing commands for cont...@bugs.debian.org: > # Missing dependencies are RC > severity 927301 serious Bug #927301 [gpustat] missing depends on python3-pkg-resources Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 927301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ruby-vcr: FTBFS randomly (failing tests)
Processing commands for cont...@bugs.debian.org: > retitle 926827 ruby-vcr: FTBFS randomly (failing tests) Bug #926827 [src:ruby-vcr] ruby-vcr: FTBFS (failing tests) Changed Bug title to 'ruby-vcr: FTBFS randomly (failing tests)' from 'ruby-vcr: FTBFS (failing tests)'. > severity 926827 important Bug #926827 [src:ruby-vcr] ruby-vcr: FTBFS randomly (failing tests) Severity set to 'important' from 'serious' > tags 926827 + patch Bug #926827 [src:ruby-vcr] ruby-vcr: FTBFS randomly (failing tests) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 926827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926827: ruby-vcr: FTBFS randomly (failing tests)
retitle 926827 ruby-vcr: FTBFS randomly (failing tests)
severity 926827 important
tags 926827 + patch
thanks
Hi. This is really random, so I'm downgrading.
I've put a bunch of build logs here from my autobuilders:
https://people.debian.org/~sanvila/build-logs/ruby-vcr/
The failing test seems to be always the same:
---
Failed examples:
rspec ./spec/acceptance/concurrency_spec.rb:15 # VCR when used in a
multithreaded environment with an around_http_request can use a cassette in an
#around_http_request hook
---
If the package is useful "as is", and this failing test does not mean
the package is broken, I would recommend disabling it for buster
before the release. (There will plenty of time to forward the bug
upstream and fix it properly).
The patch below may help, but please be warned that I don't know ruby
and it's untested.
[ Note: If you can't reproduce the randomness, please contact me privately and
I will gladly offer ssh access to a machine where this failure happens ].
Thanks.
--- a/spec/acceptance/concurrency_spec.rb
+++ b/spec/acceptance/concurrency_spec.rb
@@ -12,24 +12,6 @@ describe VCR do
before {
preload_yaml_serializer_to_avoid_circular_require_warning_race_condition }
-it 'can use a cassette in an #around_http_request hook', :if =>
(RUBY_VERSION.to_f > 1.8) do
- VCR.configure do |vcr|
-vcr.around_http_request do |req|
- VCR.use_cassette(req.parsed_uri.path, )
-end
- end
-
- threads = 50.times.map do
-Thread.start do
- Excon.get "http://localhost:#{VCR::SinatraApp.port}/search?q=thread;
-end
- end
- Excon.get "http://localhost:#{VCR::SinatraApp.port}/foo;
- threads.each(&:join)
-
- expect(recorded_content_for("search") +
- recorded_content_for("foo")).to include("query: thread", "FOO!")
-end
end
context 'when used in a multithreaded environment with a cassette',
:with_monkey_patches => :excon do
Processed: salt-doc: broken symlinks
Processing commands for cont...@bugs.debian.org: > severity 919849 grave Bug #919849 [salt-doc] salt-doc: broken symlinks: /usr/share/doc/salt/html/_static/*/bootstrap* -> ../../../../../twitter-bootstrap/files/*/bootstrap* Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 919849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927333: marked as done (node-postcss-reporter: depends on non-existent node-log-symbols)
Your message dated Thu, 18 Apr 2019 08:33:48 + with message-id and subject line Bug#927333: fixed in node-postcss-reporter 6.0.1+~3.0.0-1 has caused the Debian Bug report #927333, regarding node-postcss-reporter: depends on non-existent node-log-symbols 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.) -- 927333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 --- End Message --- --- Begin Message --- Source: node-postcss-reporter Source-Version: 6.0.1+~3.0.0-1 We believe that the bug you reported is fixed in the latest version of node-postcss-reporter, 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. Xavier Guimard (supplier of updated node-postcss-reporter 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: Thu, 18 Apr 2019 09:53:44 +0200 Source: node-postcss-reporter Architecture: source Version: 6.0.1+~3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Xavier Guimard Changed-By: Xavier Guimard Closes: 927333 Changes: node-postcss-reporter (6.0.1+~3.0.0-1) unstable; urgency=medium . * Team upload. . [ Paolo Greppi ] * Update Vcs fields for migration to https://salsa.debian.org/ . [ Xavier Guimard ] * Team upload * Add log-symbols as component (Closes: #927333) * Enable upstream tests using pkg-js-tools. This adds log-symbols and strip-color in debian/tests/test-modules (used for tests only, not installed) * Add upstream/metadata * Bump debhelper compatibility level to 11 * Declare compliance with policy 4.3.0 * Fix d/copyright format url Checksums-Sha1: 39468786856bd1b05ffd6b395d8406a94ae94f37 2578 node-postcss-reporter_6.0.1+~3.0.0-1.dsc b2150925e8feaef7ec20640f1746a574470b1ed1 17047 node-postcss-reporter_6.0.1+~3.0.0.orig-logsymbols.tar.gz adbdf59ed773adc4b1711b8b913a596f94534b36 123851 node-postcss-reporter_6.0.1+~3.0.0.orig.tar.gz 10c75e66edc1076d020c6eaa86378f57fd01ffe9 5528 node-postcss-reporter_6.0.1+~3.0.0-1.debian.tar.xz Checksums-Sha256: 5245af1a162b28a2f1bbc1734cdd009f4c0995a249251dfc54bd649cbdd57f6d 2578 node-postcss-reporter_6.0.1+~3.0.0-1.dsc cfc5e4fdd2b0a2c2548622ae61d0c4ad74e14fc6d8482b79944ee566c8c38382 17047 node-postcss-reporter_6.0.1+~3.0.0.orig-logsymbols.tar.gz 4fe4ca071d27eca50067773a5b8871e5ac6fec82ce3d1120d464dd0e802f1928 123851 node-postcss-reporter_6.0.1+~3.0.0.orig.tar.gz 306b1e6db63eea10da60ef6c2784d1fabc29357959615b366f42b0592f71aa06 5528 node-postcss-reporter_6.0.1+~3.0.0-1.debian.tar.xz Files: 008fc870a1b28b750ba89828ff40ca6c 2578 javascript optional node-postcss-reporter_6.0.1+~3.0.0-1.dsc 684ce2c3e05b64533bf3a73c727adc71 17047 javascript optional node-postcss-reporter_6.0.1+~3.0.0.orig-logsymbols.tar.gz 494d04a73bb1ba44c694652a8fc1c0d6 123851 javascript optional
Processed: Bug #927333 in node-postcss-reporter marked as pending
Processing control commands: > tag -1 pending Bug #927333 [node-postcss-reporter] node-postcss-reporter: depends on non-existent node-log-symbols Added tag(s) pending. -- 927333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927333: Bug #927333 in node-postcss-reporter marked as pending
Control: tag -1 pending Hello, Bug #927333 in node-postcss-reporter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-postcss-reporter/commit/783094e4f2cd1263512b6bdcec95bad6edbf1988 Add log-symbols as component Closes: #927333 (this message was generated automatically) -- Greetings https://bugs.debian.org/927333
Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
reopen 924829 kthxbye Since BTS cannot clone merged bugs, and thus very intelligently we cannot carry over the discussion, let us reopen this bug again .. (so many years and still not fixed lovely BTS ...) Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Processed: Re: Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
Processing commands for cont...@bugs.debian.org:
> reopen 924829
Bug #924829 {Done: Norbert Preining } [texlive-latex-extra]
caffe: FTBFS: Fatal error occurred, no output PDF file produced!
Bug #920459 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
Bug #920621 {Done: Norbert Preining } [texlive-latex-extra]
texlive-base: breaks build of forthcoming doxygen 1.8.15
Bug #921272 {Done: Norbert Preining } [texlive-latex-extra]
texlive-latex-extra: package tabu broken when xcolor is used
Bug #921299 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
Bug #921776 {Done: Norbert Preining } [texlive-latex-extra]
bliss: FTBFS (LaTeX error)
Bug #921779 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
Bug #921783 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
Bug #921789 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
Bug #921802 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
Bug #921838 {Done: Norbert Preining } [texlive-latex-extra]
tabu: breaks with color and/or xcolor when spread or negative X coefficients
are used
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
No longer marked as fixed in versions texlive-extra/2018.20190227-1.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
920621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920621
921272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921272
921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299
921776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921776
921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779
921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783
921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789
921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802
921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838
924829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
Processing commands for cont...@bugs.debian.org: > clone 924829 -1 Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output PDF file produced! Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15 Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is used Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921776 [texlive-latex-extra] bliss: FTBFS (LaTeX error) Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Failed to clone 924829: Bug is marked as being merged with others. Use an existing clone. > close 924829 2018.20190227-1 Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output PDF file produced! Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15 Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is used Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921776 [texlive-latex-extra] bliss: FTBFS (LaTeX error) Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Marked as fixed in versions texlive-extra/2018.20190227-1. Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output PDF file produced! Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming doxygen 1.8.15 Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when xcolor is used Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921776 [texlive-latex-extra] bliss: FTBFS (LaTeX error) Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 920621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920621 921272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921272 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921776:
Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
clone 924829 -1 close 924829 2018.20190227-1 thanks > reopen 924829 This is a different bug then the one reported here. Closing this bug again, and cloning it for another. Uploading after bug number is assigned. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#926872: evolution: Spaces in mail view disappeared with recent updates
On Wednesday, 17 April 2019 19:03:26 CEST Boyuan Yang wrote: > 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. What locale are you using ? Could you try with "LC_ALL=C evolution" ? All the best Dod
Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!
> @Norbert: can we risk it to upload that new tabu.sty to unstable? Yes. Preparing an upload now. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
