Bug#916102: ansible: CVE-2018-16876: Information disclosure in vvv+ mode with no_log on
Source: ansible Version: 2.7.1+dfsg-2 Severity: important Tags: patch security upstream Forwarded: https://github.com/ansible/ansible/pull/49569 Hi, The following vulnerability was published for ansible. CVE-2018-16876[0]: Information disclosure in vvv+ mode with no_log on If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-16876 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16876 [1] https://github.com/ansible/ansible/pull/49569 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#916101: mailman3: uses a hard-coded and mismatched api_key in mailman-hyperkitty.cfg
Source: mailman3 Dear Maintainer, mailman-hyperkitty.cfg [1] contains: api_key: SecretArchiverAPIKey mailman3-web postinst however, checks for this api_key and generates a random one if it has not been changed [2]. This means the default setup for hyperkitty contains mismatched api key, and will not work. mailman3 should generate api_key when writing /etc/mailman3/mailman-hyperkitty.cfg. Then the logic for randomizing the password could be removed from mailman3-web. [1]: https://salsa.debian.org/mailman-team/mailman-hyperkitty/blob/master/mailman-hyperkitty.cfg [2]: https://salsa.debian.org/mailman-team/mailman-suite/blob/master/debian/mailman3-web.postinst#L114-125
Bug#916103: systemd: error while loading shared libraries: R_PPC_REL24 relocation out of range
Package: systemd Version: 239-14 Severity: important Dear Maintainer, * What led up to the situation? systemctl is called by cron, by apt-get or directly from shell (starting, stoping services) The situation does not occure in all these situations, but quite frequently (my estimate is 30% of situations) * What exactly did you do (or not do) that was effective (or ineffective)? cron job (which includes restarting of a service) apt-get upgrade * What was the outcome of this action? systemctl error followed by the failure of the action which called systemctl (cron job, apt-get upgrade) systemctl errors reported in logs: /bin/systemctl: error while loading shared libraries: R_PPC_REL24 relocation at 0x0054d880 for symbol `gcry_control' out of range systemctl: error while loading shared libraries: R_PPC_REL24 relocation at 0x005a4c38 for symbol `pthread_setname_np' out of range * What outcome did you expect instead? no systemctl error -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 4.4.161-8da83cc2897da7a453071dbe9bfb6bff-1 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to cs_CZ.UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to cs_CZ.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.52-3 ii libapparmor1 2.13.1-3+b1 ii libaudit11:2.8.4-2 ii libblkid12.33-0.2 ii libc62.27-8 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.6-1 ii libgcrypt20 1.8.4-4 ii libgnutls30 3.5.19-1+b1 ii libgpg-error01.32-3 ii libidn11 1.33-2.2 ii libip4tc01.8.2-2 ii libkmod2 25-2 ii liblz4-1 1.8.2-1 ii liblzma5 5.2.2-1.3 ii libmount12.33-0.2 ii libpam0g 1.1.8-3.8 ii libselinux1 2.8-1+b1 ii libsystemd0 239-14 ii mount2.33-0.2 ii util-linux 2.33-0.2 Versions of packages systemd recommends: ii dbus1.12.12-1 pn libpam-systemd Versions of packages systemd suggests: pn policykit-1 pn systemd-container Versions of packages systemd is related to: pn dracut pn initramfs-tools ii udev 239-14 -- no debconf information
Bug#916104: duperemove FTBFS with glibc 2.28
Source: duperemove Version: 0.11-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/duperemove.html ... dbfile.c: In function '__dbfile_sync_config': dbfile.c:350:16: warning: implicit declaration of function 'major' [-Wimplicit-function-declaration] onefs_major = major(onefs_dev); ^ dbfile.c:355:16: warning: implicit declaration of function 'minor' [-Wimplicit-function-declaration] onefs_minor = minor(onefs_dev); ^ dbfile.c: In function '__dbfile_get_config': dbfile.c:600:16: warning: implicit declaration of function 'makedev' [-Wimplicit-function-declaration] *onefs_dev = makedev(onefs_major, onefs_minor); ^~~ ... cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/1st/duperemove-0.11=. -fstack-protector-strong -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -DVERSTRING=\"v0.11.beta4\" -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -rdynamic -Wl,-z,relro -Wl,-z,now duperemove.o hash-tree.o results-tree.o rbtree.o dedupe.o filerec.o btrfs-util.o util.o memstats.o file_scan.o find_dupes.o run_dedupe.o csum.o dbfile.o interval_tree.o list_sort.o stats.o debug.o csum-xxhash.o xxhash.o csum-murmur3.o -o duperemove -lglib-2.0 -lsqlite3 -lm /usr/bin/ld: dbfile.o: in function `__dbfile_get_config': ./dbfile.c:600: undefined reference to `makedev' /usr/bin/ld: dbfile.o: in function `__dbfile_sync_config': ./dbfile.c:350: undefined reference to `major' /usr/bin/ld: ./dbfile.c:355: undefined reference to `minor' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:82: duperemove] Error 1
Bug#913883: usrmerge: can't merge with iptables and ebtables installed
On Sat, 17 Nov 2018 03:47:09 +0100 Marco d'Itri wrote: > Control: reassign -1 iptables > Control: usertags -1 usrmerge > > On Nov 16, Felipe Sateler wrote: > > > Conversion fails when iptables and ebtables are installed: > > > > FATAL ERROR: > > Both /sbin/ebtables-restore and /usr/sbin/ebtables-restore exist. > Because ebtables installs a /sbin/ebtables-restore binary and recently > iptables started managing a /usr/sbin/ebtables-restore diversion. > > > Uninstalling ebtables makes the conversion pass. Installing ebtables > > again works without error. > But I highly doubt that the ebtables nft emulation would still work at > that point. > > > I have no idea who is at fault here > iptables should not have started managing /usr/sbin/ebtables-restore > without coordinaation with ebtables (or else conflicting with it). > I cannot see how this would not be broken even without a merged-/usr > since systems would have two functionally different ebtables-restore > programs in different directories. > Quickly looking at this bug (that is more or less a duplicate of #912046) it seems (not tested) that the issue could also happen with arptables package as the iptables one adds alternatives for the arptables executables while the "original" package is not doing the same... IMVHO iptables package MUST add a breaks for the current version arptables and ebtables (and also maybe a provides if the executable provides the same interfaces) And arptables and ebtables should either be kicked out of the archive if they are deprecated or must be converted to the alternative system
Bug#912046: debsums: Error: symlink loop detected in path 'sbin/ebtables'.
On Sat, 1 Dec 2018 13:36:11 +0100 gregor herrmann wrote: > On Sat, 27 Oct 2018 17:39:50 +0200, Laurent Bigonville wrote: > > > When running debsums -ac, it complains that: > > > > debsums: Error: symlink loop detected in path 'sbin/ebtables'. Please file a bug against ebtables. > > > > So here is the bug report. > > I can't reproduce this (by installing the package and running > debsums), and I don't see any symlinkery in the package either but I > might miss somthing. > > What do see are alternatives [0] but they all seem to be in the > iptables package and /sbin/ebtables doesn't seem to be involved. > > So maybe this is/was an iptables problem and maybe this was/is fixed > (or maybe I have a to old iptables version). > > Or is this another merged-/usr issue poppoing up? Alright, so it's indeed a problem with usrmerge and the fact that ebtables package is NOT using the alternative for (/usr)/sbin/ebtables Apparently, iptables now adds an alternative to /usr/sbin/ebtables: update-alternatives \ --install /usr/sbin/ebtables ebtables /usr/sbin/ebtables-nft 20 \ --slave /usr/sbin/ebtables-restore ebtables-restore /usr/sbin/ebtables-nft-restore \ --slave /usr/sbin/ebtables-save ebtables-save /usr/sbin/ebtables-nft-save But as the ebtables package is still providing a real executables in /sbin/ebtables* ; with usr-merge it explodes. IMVHO, iptables package should provides "ebtables" (it's providing the same CLI interface right?) and must breaks with the current version of ebtables. And either ebtables must be kicked out of the archive (is this really deprecated?) and/or use the alternatives system. It seems that the same problem exists with the aprtables package The fact that iptables package started providing ebtables/arptables executable without coordination is quite bad. Note there is also bug #913883 that is more than probably a duplicate of this bug.
Bug#916000: [Debian-med-packaging] Bug#916000: ncbi-blast+: FTBFS - Makefile.flat: No such file or directory
On 12/9/18 5:11 PM, Aaron M. Ucko wrote: > Andreas Metzler writes: > >> ncbi-blast+ FTBFS on current sid: > Thanks for the report! It looks like ncbi-blast+ needs another round of > formal patches for compatibility with current Boost. The following > upstream changes should collectively take care of it: > > https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79910 > https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79926 > https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79928 > https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79929 > > Olivier, will you have time to integrate these changes, or should I? no time for the moment, if you can do it, I would appreciate thanks Olivier > -- Olivier Sallou Univ Rennes, Inria, CNRS, IRISA Irisa, Campus de Beaulieu F-35042 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Bug#916105: lxqt-panel: menu-button opens ~5.5cm above panel (on portrait display, normal on landscape)
Package: lxqt-panel Version: 0.13.0-1 Severity: minor Tags: a11y Dear Maintainer, My system is dell 755 (optiplex) with two displays, one landscape & one portrait. I've added two panels, one at bottom of each display. If I open (click) menu on landscape monitor, behavior is expected. If I open (click) menu on portrait monitor, I'd expect menu to open just above panel, but it opens with ~5.5cm gap between panel & bottom of displayed menu. The gap between panel (at bottom of display) & menu contains the normal background (be it wallpaper, terminal, browser, or file manager). Menu works naturally, but having to move mouse further up ~5.5cm isn't ideal. (I tried taking screenshot, but menu would disppear on touch of keys to take image & I'd not get the menu appearing sorry) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxqt-panel depends on: ii libasound2 1.1.7-1+b1 ii libc6 2.27-8 ii libdbusmenu-qt5-2 0.9.3+16.04.20160218-1 ii libkf5solid55.51.0-1 ii libkf5windowsystem5 5.51.0-1 ii liblxqt-globalkeys-ui0 0.13.0-1 ii liblxqt-globalkeys0 0.13.0-1 ii liblxqt00.13.0-1 ii libpulse0 12.2-2 ii libqt5core5a5.11.2+dfsg-7 ii libqt5dbus5 5.11.2+dfsg-7 ii libqt5gui5 5.11.2+dfsg-7 ii libqt5widgets5 5.11.2+dfsg-7 ii libqt5x11extras55.11.2-2 ii libqt5xdg3 3.2.0-2+b2 ii libqt5xml5 5.11.2+dfsg-7 ii libsensors4 1:3.4.0-4 ii libstatgrab10 0.91-1+b2 ii libstdc++6 8.2.0-9 ii libsysstat-qt5-00.4.1-2 ii libx11-62:1.6.7-1 ii libxcb-xkb1 1.13.1-1 ii libxcb1 1.13.1-1 ii libxcomposite1 1:0.4.4-2 ii libxdamage1 1:1.1.4-3 ii libxkbcommon-x11-0 0.8.2-1 ii libxkbcommon0 0.8.2-1 ii libxrender1 1:0.9.10-1 ii lxmenu-data 0.1.5-2 ii lxqt-policykit 0.13.0-1 Versions of packages lxqt-panel recommends: ii lxqt-about 0.13.0-1 ii lxqt-config 0.13.0-1 ii lxqt-notificationd 0.13.0-1 ii lxqt-panel-l10n 0.13.0-1 ii lxqt-qtplugin 0.13.0-2+b2 ii lxqt-runner 0.13.0-1 ii lxqt-session0.13.0-3 ii pavucontrol 3.0-4 ii qlipper 1:5.1.1-3 Versions of packages lxqt-panel suggests: ii lxqt 27 ii lxqt-core 27 -- no debconf information
Bug#909406: [regression] GCC-8 failed to compile Julia on armhf while GCC-7 worked.
On Sun, 9 Dec 2018 at 15:21, Matthias Klose wrote: > please can you recheck with 8.2.0-11 or -12? Also could you recheck on the > armhf > porter boxes once these gcc versions are installable? I've just tried in an Ubuntu PPA as soon as gcc 8.2.0-12ubuntu1 was published. cd /<>/base && /<>/usr/bin/julia -C "armv7-a;armv7-a,neon;armv7-a,neon,vfp4" --output-ji /<>/usr/lib/arm-linux-gnueabihf/julia/corecompiler.ji.tmp --startup-file=no -g0 -O0 compiler/compiler.jl Invalid Thumb instruction at 0xf754f860: 0xf194, 0x000e signal (4): Illegal instruction in expression starting at no file:0 unknown function (ip: 0xf754f85f) true_main at ./ui/./ui/repl.c:103 main at ./ui/./ui/repl.c:233 __libc_start_main at /lib/arm-linux-gnueabihf/libc.so.6 (unknown line) _start at /<>/usr/bin/julia (unknown line) Allocations: 36838 (Pool: 36838; Big: 0); GC: 0 Illegal instruction (core dumped)
Bug#912056: xdffileio: diff for NMU version 0.3-2.1
Control: tags 912056 + patch Control: tags 912056 + pending Dear maintainer, I've prepared an NMU for xdffileio (versioned as 0.3-2.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru xdffileio-0.3/debian/changelog xdffileio-0.3/debian/changelog --- xdffileio-0.3/debian/changelog 2018-09-18 22:53:47.0 +0300 +++ xdffileio-0.3/debian/changelog 2018-12-10 10:41:39.0 +0200 @@ -1,3 +1,11 @@ +xdffileio (0.3-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix frequent parallel FTBFS by using the serial test harness. +(Closes: #912056) + + -- Adrian Bunk Mon, 10 Dec 2018 10:41:39 +0200 + xdffileio (0.3-2) unstable; urgency=medium * Team upload. diff -Nru xdffileio-0.3/debian/patches/serial-tests.patch xdffileio-0.3/debian/patches/serial-tests.patch --- xdffileio-0.3/debian/patches/serial-tests.patch 1970-01-01 02:00:00.0 +0200 +++ xdffileio-0.3/debian/patches/serial-tests.patch 2018-12-10 10:41:39.0 +0200 @@ -0,0 +1,14 @@ +Description: Fix frequent parallel FTBFS by using the serial test harness +Author: Adrian Bunk + +--- xdffileio-0.3.orig/configure.ac xdffileio-0.3/configure.ac +@@ -20,7 +20,7 @@ AC_CONFIG_MACRO_DIR([m4]) + AC_CONFIG_HEADERS([config/config.h]) + + # Setup automake +-AM_INIT_AUTOMAKE([subdir-objects no-dist-gzip dist-bzip2 color-tests]) ++AM_INIT_AUTOMAKE([subdir-objects no-dist-gzip dist-bzip2 color-tests serial-tests]) + m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) + + diff -Nru xdffileio-0.3/debian/patches/series xdffileio-0.3/debian/patches/series --- xdffileio-0.3/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ xdffileio-0.3/debian/patches/series 2018-12-10 10:40:36.0 +0200 @@ -0,0 +1 @@ +serial-tests.patch
Bug#914099: mailman3-full: mailman3-web-qcluster causes high database load
This issue led to a GSOC proposal in order to improve things upstream: * https://lists.mailman3.org/archives/list/mailman-us...@mailman3.org/message/IHU7QQ56TIQCLQIAVRSUEWYOEX3TO4NJ/ * https://gitlab.com/mailman/hyperkitty/issues/208 If it gets picked up, the issue might eventually be fixed upstream. For now, there is https://gitlab.com/mailman/hyperkitty/issues/207 which is at least a good compromise. Stefan
Bug#914340: [DAViCal-devel] Bug#914340: system details
On 04/12/2018 08:41, Florian Schlichting wrote: > Do you want to try with openssl 1.1.0j-1~deb9u1 (make sure to restart > apache2 so all the children use the new libraries) and see if those > segfaults disappear? > Thanks for looking into that I installed the updated openssl Previously Apache / DAViCal would get into this state approximately once a week, so if it runs smoothly for 2-3 weeks then hopefully that is the fix for it. That said, even if a segfault appears in openssl and there is a fix for that, there are sometimes cases where another library mentioned in the stack has used the openssl API incorrectly or passed a bad argument and ideally that code would be examined too. I haven't personally had time to look closely enough at the openssl fix to see if it is such a case. Regards, Daniel
Bug#916107: mongodb: MongoDB should not be part of a stable release
Source: mongodb Version: 1:3.4.15-1 Severity: serious Justification: Cannot be properly supported MongoDB should not be part of (at least) Buster for the following reasons: - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it to be included in Buster. - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch to SSPLv1 complicates matters. As discussed in #915537, we will not be distributing any SSPL-licensed software, and keeping the last AGPL-licensed version (3.6.8 or 4.0.3) without the ability to cherry-pick upstream fixes is not a viable option. (I am currently not considering distributing mongodb in non-free.) I will not request removal immediately, to allow other packages time to adjust their dependencies, but eventually auto-removal will kick in. That said, MongoDB 3.4 will probably remain in sid for as long as it is AGPL-licensed and supported upstream. Apollon [1] https://www.mongodb.com/support-policy
Bug#872036: AH00060: seg fault or similar nasty error detected in the parent process
In case that helps, I just noticed a similar error. I have a maintenance script that - modifies a config file to put the application in maintenance mode - systemctl reload apache2 - performs database maintenance - sets the old config back - systemctl reload apache2 When using this on a new installation where the DB is empty, the maintenance task takes an instant, and the script basically does systemctl reload apache2; systemctl reload apache2 which is enough to reproduce the crash. Jeremy Stanley wrote: This sounds a lot like https://bugzilla.redhat.com/show_bug.cgi?id=1376835 This bug report reads : The problem (httpd with worker/event mpm segfaults after multiple successive graceful reloads) was fixed in 2.4.6-53.el7 (Development Version) However, I'm using Debian Stretch's 2.4.25-3+deb9u6 so AFAIU, this should include the patch. Unless there is something specific to my configuration, the issue can be easily reproduced with systemctl reload apache2; systemctl reload apache2 When adding a sleep of a few hundreds milliseconds in between, the crash does not happen. Also worth noting that despite the error message, apache is up and running at the end of the process, so AFAICT, this is just noise in the logs. -- Jérôme
Bug#916095: lintian: False positive: license-problem-gfdl-invariants
tags 916095 + moreinfo
thanks
Hi Dmitry,
> Dear Maintainer, here is excerpt from cflow.texi (GNU cflow 1.5)
Thanks for your bug reports btw. I'm not 100% sure, but I think the
problem here:
> any later version published by the Free Software Foundation; with no
> Invariant Sections, no Front-Cover and Back-Cover texts. [..]
… is that it is missing an explicit reference to having "no bad
sections". See #698667 for some of the background?
(Attaching offending file for reference.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename cflow.info
@settitle GNU cflow
@c %**end of header
@setchapternewpage odd
@syncodeindex fn cp
@syncodeindex vr cp
@syncodeindex ky cp
@syncodeindex pg cp
@syncodeindex tp cp
@include version.texi
@include rendition.texi
@ifinfo
@dircategory GNU programming tools
@direntry
* cflow: (cflow). Create a graph of control flow within a program.
@end direntry
@dircategory Emacs
@direntry
* cflow mode: (cflow)cflow mode. Major mode for visiting cflow charts.
@end direntry
@end ifinfo
@copying
Published by the Free Software Foundation,
51 Franklin Street, Fifth Floor
Boston, MA 02110-1301, USA
Copyright @copyright{} 2005, 2010, 2014-2016 Sergey Poznyakoff
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover and Back-Cover texts. A copy of
the license is included in the section entitled ``GNU Free Documentation
License''.
@end copying
@titlepage
@title GNU cflow
@subtitle version @value{VERSION}, @value{UPDATED}
@author Sergey Poznyakoff.
@page
@vskip 0pt plus 1filll
@insertcopying
@end titlepage
@page
@summarycontents
@page
@contents
@ifnottex
@node Top
@top GNU cflow
This edition of the @cite{GNU Cflow Manual}, last updated @value{UPDATED},
documents GNU cflow Version @value{VERSION}.
@end ifnottex
@menu
* Intro:: Introduction to @command{cflow}.
* Quick Start:: Simple Ways to Analyze Programs with @command{cflow}.
* Direct and Reverse:: Two Types of Flow Graphs.
* Output Formats:: Supported Output Formats.
* Recursive Calls:: Handling Recursive Calls.
* Symbols:: Controlling Symbol Input and Output.
* Preprocessing:: Source Files Can Be Preprocessed Before Analyzing.
* ASCII Tree:: Using ASCII Art to Produce Flow Graphs.
* Cross-References::Cross-Reference Output.
* Configuration:: Configuration Files and Variables.
* Makefiles:: Using @command{cflow} in Makefiles.
* Options:: Complete Listing of @command{cflow} Options.
* Exit Codes:: Exit Codes,
* Emacs:: Using @command{cflow} with GNU Emacs.
* Reporting Bugs:: How to Report a Bug.
Appendices
* Source of wc command::
* Copying This Manual:: The GNU Free Documentation License.
* Concept Index:: Index of Concepts.
@detailmenu
--- The Detailed Node Listing ---
Controlling Symbol Types
* Syntactic classes::
* Symbol aliases::
* GCC Initialization::
@end detailmenu
@end menu
@node Intro
@chapter Introduction to cflow
@pindex cflow
@cindex cflow, a description of
The @command{cflow} utility analyzes a collection of source files
written in @code{C} programming language and outputs a graph charting
dependencies between various functions.
@cindex direct tree defined
@cindex direct graph defined
@cindex reverse graph defined
@cindex reverse tree defined
The program is able to produce two kind of graphs: direct
and reverse. @dfn{Direct graph} begins with the main function
(@code{main}), and displays recursively all functions called by it.
In contrast, @dfn{reverse graph} is a set of subgraphs, charting for
each function its callers, in the reverse order. Due to their
tree-like appearance, graphs can also be called @dfn{trees}.
In addition to these two output modes, @command{cflow} is able to
produce a @dfn{cross-reference} listing of all the symbols encountered
in the input files.
The utility also provides a detailed control over symbols that will
appear in its output, allowing to omit those that are of no interest
to the user. The exact appearance of the output graphs is also
configurable.
@FIXME{Some notes about when the user might need the utility? For
example, to get a quick acquaintance with the program, etc.}
@FIXME{The utility should also be able to process following input file
formats: @command{yacc} and @command{lex} sources, and object
files. It is a good idea to add a node @samp{POSIX} discussing this.}
@node Quick Start
@chapter Simple Ways to Analyze Programs with @command{cflow}.
Let's begin our acquaintance with the GNU @command{cflow} utility
with an example. Suppose you have a simple implementation of
@com
Bug#912046: [pkg-netfilter-team] Bug#912046: debsums: Error: symlink loop detected in path 'sbin/ebtables'.
On 12/10/18 9:30 AM, Laurent Bigonville wrote: > On Sat, 1 Dec 2018 13:36:11 +0100 gregor herrmann > wrote: > >> On Sat, 27 Oct 2018 17:39:50 +0200, Laurent Bigonville wrote: >> >> > When running debsums -ac, it complains that: >> > >> > debsums: Error: symlink loop detected in path 'sbin/ebtables'. > Please file a bug against ebtables. >> > >> > So here is the bug report. >> >> I can't reproduce this (by installing the package and running >> debsums), and I don't see any symlinkery in the package either but I >> might miss somthing. >> >> What do see are alternatives [0] but they all seem to be in the >> iptables package and /sbin/ebtables doesn't seem to be involved. >> >> So maybe this is/was an iptables problem and maybe this was/is fixed >> (or maybe I have a to old iptables version). >> > >> Or is this another merged-/usr issue poppoing up? > > Alright, so it's indeed a problem with usrmerge and the fact that > ebtables package is NOT using the alternative for (/usr)/sbin/ebtables > > Apparently, iptables now adds an alternative to /usr/sbin/ebtables: > > update-alternatives \ > --install /usr/sbin/ebtables ebtables /usr/sbin/ebtables-nft 20 \ > --slave /usr/sbin/ebtables-restore ebtables-restore > /usr/sbin/ebtables-nft-restore \ > --slave /usr/sbin/ebtables-save ebtables-save > /usr/sbin/ebtables-nft-save > > But as the ebtables package is still providing a real executables in > /sbin/ebtables* ; with usr-merge it explodes. > > IMVHO, iptables package should provides "ebtables" (it's providing the > same CLI interface right?) and must breaks with the current version of > ebtables. And either ebtables must be kicked out of the archive (is this > really deprecated?) and/or use the alternatives system. > > It seems that the same problem exists with the aprtables package The > fact that iptables package started providing ebtables/arptables > executable without coordination is quite bad. > > Note there is also bug #913883 that is more than probably a duplicate of > this bug. > > we are working both in arptables and ebtables and will upload soon.
Bug#915881: Ubuntu's custom build flags are overridden by Debian's
On Sun, Dec 09, 2018 at 11:17:15PM +0100, Guillem Jover wrote: > Iain: Should your mail address really be @debian or perhaps it should > have been either @canonical or @ubuntu instead? For better © tracking. Cheers for that. And sure, s/debian/ubuntu/ works for me too. It's just that my reportbug configuration defaults to d.o and I didn't override it. Merci, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: PGP signature
Bug#916108: [fuse] Can't install fuse on salsa runners (chmod: changing permissions of '/dev/cuse': Read-only system)
Package: fuse Version: 2.9.8-2 Severity: normal Dear maintainer, I have been digging why the package can't be installed on salsa runners and it seems is trying to change the /dev/cuse permissions on post-installation. Honestly, I'm not sure what would be the best approach in this case. Checking that /dev/cuse already has the permissions needed (which is the case) or checking if /dev/cuse is RO. You can see my tries here[0][1][2] to figure out what was happening. Just let me know if I can help with further debugging. [0] https://salsa.debian.org/debian/doit/-/jobs/90476 [1] https://salsa.debian.org/debian/doit/-/jobs/90481 [2] https://salsa.debian.org/debian/doit/-/jobs/90486 Cheers, -- TiN signature.asc Description: OpenPGP digital signature
Bug#915537: MongoDB SSPL v1 license and the DFSG
Hideki, > Could you explain it a bit more, please? Why SSPL doesn't meet our > goal? I don't complain about this judge but more detailed explanation > with some examples is better, IMHO. Before I expound on this topic, are you already acquainted with the general concerns raised about this license outside of Debian? I would not with to patronise you by repeating them to you here. (Just another brief clarification whilst I spot it: I was only speaking to version one of the license in that bug report. As in; "we will not consider any other version of the SSPL beyond version one" should have had a "... in this email" suffix.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#916109: osmium-tool FTBFS with libosmium2-dev 2.15.0-1
Source: osmium-tool
Version: 1.9.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/osmium-tool.html
...
cd /build/1st/osmium-tool-1.9.1/obj-x86_64-linux-gnu/test && /usr/bin/c++
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/build/1st/osmium-tool-1.9.1/obj-x86_64-linux-gnu/src
-I/build/1st/osmium-tool-1.9.1/test/include
-I/build/1st/osmium-tool-1.9.1/test/../src
-I/build/1st/osmium-tool-1.9.1/test/../src/extract
-I/build/1st/osmium-tool-1.9.1/test/../include -isystem
/build/1st/osmium-tool-1.9.1/include -g -O2
-ffile-prefix-map=/build/1st/osmium-tool-1.9.1=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11
-Wall -Wextra -pedantic -Wredundant-decls -Wdisabled-optimization
-Wctor-dtor-privacy -Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo
-Wold-style-cast -pthread -o CMakeFiles/unit_tests.dir/__/src/util.cpp.o -c
/build/1st/osmium-tool-1.9.1/src/util.cpp
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:27:
/usr/include/osmium/tags/tags_filter.hpp:157:44: error: conflicting declaration
'using TagsFilter = class osmium::TagsFilterBase'
using TagsFilter = TagsFilterBase;
^
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:24:
/build/1st/osmium-tool-1.9.1/src/util.hpp:37:11: note: previous declaration as
'class osmium::TagsFilter'
class TagsFilter;
^~
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:33:
/usr/include/c++/8/iostream:60:10: error: 'istream' does not name a type
extern istream cin; /// Linked to standard input
^~~
/usr/include/c++/8/iostream:61:10: error: 'ostream' does not name a type
extern ostream cout; /// Linked to standard output
^~~
/usr/include/c++/8/iostream:62:10: error: 'ostream' does not name a type
extern ostream cerr; /// Linked to standard error (unbuffered)
^~~
/usr/include/c++/8/iostream:63:10: error: 'ostream' does not name a type
extern ostream clog; /// Linked to standard error (buffered)
^~~
/usr/include/c++/8/iostream:66:10: error: 'wistream' does not name a type
extern wistream wcin; /// Linked to standard input
^~~~
/usr/include/c++/8/iostream:67:10: error: 'wostream' does not name a type
extern wostream wcout; /// Linked to standard output
^~~~
/usr/include/c++/8/iostream:68:10: error: 'wostream' does not name a type
extern wostream wcerr; /// Linked to standard error (unbuffered)
^~~~
/usr/include/c++/8/iostream:69:10: error: 'wostream' does not name a type
extern wostream wclog; /// Linked to standard error (buffered)
^~~~
/usr/include/c++/8/iostream:74:10: error: 'ios_base' does not name a type
static ios_base::Init __ioinit;
^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function 'void
osmium::warning(const char*)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:62:10: error: 'cerr' is not a member
of 'std'
std::cerr << "WARNING: " << text;
^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp:62:10: note: 'std::cerr' is defined
in header ''; did you forget to '#include '?
/build/1st/osmium-tool-1.9.1/src/util.cpp:34:1:
+#include
#include
/build/1st/osmium-tool-1.9.1/src/util.cpp:62:10:
std::cerr << "WARNING: " << text;
^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function 'void
osmium::warning(const string&)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:66:10: error: 'cerr' is not a member
of 'std'
std::cerr << "WARNING: " << text;
^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp:66:10: note: 'std::cerr' is defined
in header ''; did you forget to '#include '?
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function
'std::pair >
osmium::get_filter_expression(const string&)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:113:48: error: call of overloaded
'get_types(std::__cxx11::basic_string)' is ambiguous
entities = get_types(str.substr(0, pos));
^
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:24:
/build/1st/osmium-tool-1.9.1/src/util.hpp:50:31: note: candidate:
'osmium::osm_entity_bits::type get_types(const string&)'
osmium::osm_entity_bits::type get_types(const std::string& str);
^
/build/1st/osmium-tool-1.9.1/src/util.cpp:79:31: note: candidate:
'osmium::osm_entity_bits::type osmium::get_types(const string&)'
osmium::osm_entity_bits::type get_types(const std::string& str) {
^
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function 'osmium::StringMatcher
osmium::get_string_matcher(std::__cxx11::string)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:132:28: error: call of overloaded
'strip_whitespace(std::__cxx11::string&)' is ambiguous
strip_whitespace(string);
Bug#916111: ruby-sigar FTBFS with glibc 2.28
Source: ruby-sigar
Version: 0.7.3-1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-sigar.html
...
linux_sigar.c: In function 'get_iostat_proc_dstat':
linux_sigar.c:1177:22: warning: implicit declaration of function 'major'
[-Wimplicit-function-declaration]
#define ST_MAJOR(sb) major((sb).st_rdev)
^
linux_sigar.c:1253:26: note: in expansion of macro 'ST_MAJOR'
ST_MAJOR(sb), ST_MINOR(sb));
^~~~
linux_sigar.c:1178:22: warning: implicit declaration of function 'minor'; did
you mean 'mknod'? [-Wimplicit-function-declaration]
#define ST_MINOR(sb) minor((sb).st_rdev)
^
linux_sigar.c:1253:40: note: in expansion of macro 'ST_MINOR'
ST_MAJOR(sb), ST_MINOR(sb));
^~~~
linux_sigar.c:1177:22: error: called object 'major' is not a function or
function pointer
#define ST_MAJOR(sb) major((sb).st_rdev)
^
linux_sigar.c:1266:23: note: in expansion of macro 'ST_MAJOR'
if ((major == ST_MAJOR(sb)) &&
^~~~
linux_sigar.c:1261:23: note: declared here
unsigned long major, minor;
^
linux_sigar.c:1178:22: error: called object 'minor' is not a function or
function pointer
#define ST_MINOR(sb) minor((sb).st_rdev)
^
linux_sigar.c:1267:24: note: in expansion of macro 'ST_MINOR'
((minor == ST_MINOR(sb)) || (minor == 0)))
^~~~
linux_sigar.c:1261:30: note: declared here
unsigned long major, minor;
^
linux_sigar.c:1178:22: error: called object 'minor' is not a function or
function pointer
#define ST_MINOR(sb) minor((sb).st_rdev)
^
linux_sigar.c:1318:26: note: in expansion of macro 'ST_MINOR'
if (minor == ST_MINOR(sb)) {
^~~~
linux_sigar.c:1261:30: note: declared here
unsigned long major, minor;
^
linux_sigar.c: In function 'get_iostat_procp':
linux_sigar.c:1177:22: error: called object 'major' is not a function or
function pointer
#define ST_MAJOR(sb) major((sb).st_rdev)
^
linux_sigar.c:1369:23: note: in expansion of macro 'ST_MAJOR'
if ((major == ST_MAJOR(sb)) && (minor == ST_MINOR(sb))) {
^~~~
linux_sigar.c:1364:23: note: declared here
unsigned long major, minor;
^
linux_sigar.c:1178:22: error: called object 'minor' is not a function or
function pointer
#define ST_MINOR(sb) minor((sb).st_rdev)
^
linux_sigar.c:1369:50: note: in expansion of macro 'ST_MINOR'
if ((major == ST_MAJOR(sb)) && (minor == ST_MINOR(sb))) {
^~~~
linux_sigar.c:1364:30: note: declared here
unsigned long major, minor;
^
Bug#916112: apt-get purge filename.deb not working like expected
Package: apt Version: 1.8.0~alpha2 Severity: minor Dear Maintainer, apt-get is great to install packages. Especially when the package at hand is locally lying around on the harddisk. It even resolves dependencies through its algorithm. So far, so good. What I tried after an "apt-get -y install ./foo.deb" was an "apt-get -y purge ./foo.deb" to see if it might work too. It seemingly is able to figure out the package name, because it gives these messages: #v+ Note, selecting 'irssi-build-deps' instead of './irssi-build-deps_1.1.1-1_all.deb' irssi-build-deps is already the newest version (1.1.1-1). #v- It seemingly is able to figure out the package name from the given filename, but then seems to have forgotten that a purge was requested, not an install, which feels a bit weird. (Background of this is some auto package building that I want to set up and need to purge the build-dependencies afterwards again, and the basis is just the filename that mk-buid-deps created. Probably not the wisest approach, and I'll look into other ways to do it, but this made me stumble upon this. :)) Hope that helps, Rhonda
Bug#915136: Problem still present
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've tried to upgrade to 11.4.9 and I have the same problem. Error 503 with same log when I try to access to any view of the repository. https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlwON9UACgkQCU2zE9sy 6H+Oow/+IxY19oMihQRTDt1EWNt3cRcdDbZLwaJPvoTz+gvEs70OowZPQCOzgmRl IwPPxaLN45qlFW7LCxqbzJmhLiaBvBeTS07AIPOTbP2zzSDnhJJdW6Iu6UARPWYe LoOlHwPaA6W8G+3e7RODjB5szLHijItW8zeIznj6bHAJeALuSwO/OrkY+XDkovdt HnnX/Xlxo1JBp43TQLOn5++NjzJE7V5YOD9dgwpmIaJ0092Hwcr4zoBgUaTXT1bk zfKnaF1AvGBa1AwQdJ2Hso+DgPpBWkh31Ak8F/vkZtHn3iHaexSDak9xn34Hu2UG qlCYyQuKEtCMSRuubOJxNX795NFUvu0l5lOxyVFb21Ra23Aq3w72LCvsc68O6Ps8 QWROM4phBmRuwSB/ynK8y2d+gRUPA+b7KNBs0zc5dndYLRvARdURQZtADDrv2oxY FQoIxR35V/wrgA34+DpVUTuWL5mt5WAO2zgqoCHVfVRQEh1nlOt0fZ0J5TjWz7jR a2vAtIvI5d8Qf3j4wJVevOloqmZb+32w4WMNKAyzbZN3nXKJ0kHM0fTeOTr5h+6m 8WjhY+jx+CTNoLSvNklh/6N5lrmu5MQxW69XMCyMHCfa/Mhncl3OEJHzHYakRdnj 62v+3jY+b77oWy8MGMqhaxTSkEuZ/xF8svNj8XO1zCoXdmi+5Sk= =0oZl -END PGP SIGNATURE-
Bug#916113: ITP: libjs-jquery-markitup -- jQuery based universal markup editor
Package: wnpp Severity: wishlist Owner: Mike Gabriel * Package name: libjs-jquery-markitup Version : 1.1.15 Upstream Author : Jay Salvat * URL : https://github.com/markitup/1.x * License : Expat Programming Lang: Javascript Description : jQuery based universal markup editor markItUp! is a JavaScript plugin built on the jQuery library. It allows you to turn any textarea into a markup editor. Html, Textile, Wiki Syntax, Markdown, BBcode or even your own Markup system can be easily implemented. . markItUp! is not meant to be a “Full-Features-Out-of-the-Box”-editor. Instead it is a very lightweight, customizable and flexible engine made to meet the developer's needs in their CMSes, blogs, forums or websites. markItUp! is not a WYSIWYG editor, and it never will be. . This Javascript library is required by the upcoming OpenBoard upload, will be shipped under the umbrella of the Debian Javascript Team _and_ will be co-maintained by the Debian Edu Packaging Team.
Bug#826012: Progress?
Hi, this bug blocks two others (which actually add systemd units), makes a ton of sense, and we're reasonably close to freeze time. Please consider applying the supplied patch. Thank you. (Shall I do an NMU?) -- -- Matthias Urlichs signature.asc Description: PGP signature
Bug#916114: xawtv FTBFS with glibc 2.28
Source: xawtv Version: 3.104-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xawtv.html ... common/get_media_devices.c: In function 'fget_associated_device': common/get_media_devices.c:522:14: warning: implicit declaration of function 'major' [-Wimplicit-function-declaration] dev_major = major(f_status.st_rdev); ^ common/get_media_devices.c:523:14: warning: implicit declaration of function 'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration] dev_minor = minor(f_status.st_rdev); ^ ... gcc -Wl,-z,relro -Wl,-z,now -ldl -Wl,-E -o console/webcam console/webcam.o console/ftp.o common/parseconfig.o libng/libng.a -lpthread -ljpeg -lm -ldl /usr/bin/ld: libng/libng.a(get_media_devices.o): in function `fget_associated_device': ./common/get_media_devices.c:522: undefined reference to `major' /usr/bin/ld: ./common/get_media_devices.c:523: undefined reference to `minor' collect2: error: ld returned 1 exit status make[1]: *** [mk/Compile.mk:75: console/streamer] Error 1
Bug#915397: systemd-container: fails to start a container going through machines.target or machinectl
Hi, I could eventually reboot the workstation after I upgraded to Linux 4.19.8, and updated to today's sid. Let me go through your config hints first: # grep CGROUP /boot/config-4.18.0-3-amd64 ... I checked and these were all active in my kernel build as well. $ findmnt ... Maybe check if cgroup2 is mounted for you. All present too. - But anyway, that doesn't matter anymore :-) For no reason that i can explain precisely, since I updated/rebooted, I can use the systemd-container 239-15 to spawn the containers... I guess the best is to close this issue, as "can't reproduce" then. Thank you for your time. -- Edouard Gomez
Bug#911380: Adjust server/Debian/share/ltsp/ltsp-build-client-functions
On Sat, Dec 08, 2018 at 03:08:22PM +0100, Vagrant Cascadian wrote:
> On 2018-12-07, Vagrant Cascadian wrote:
> But it's also possible to have some mirrors include a file:/// url
> that's trusted and some that are not... so it needs to be specified on a
> per-mirror basis.
Just another try w/ conditionally added trust; the attached patch seems
to work for me, please check.
Wolfgang
From 7106088bcbd7d0a0a49144b66ab10ab2f943e9d6 Mon Sep 17 00:00:00 2001
From: Wolfgang Schweer
Date: Mon, 10 Dec 2018 11:02:26 +0100
Subject: [PATCH] Debian: ltsp-build-client: Trust file:/ mirrors that point to
/media/cdrom to be able to use a CDROM now that file:/// mirrors are no
longer trusted by default. https://bugs.debian.org/911380
---
.../Debian/share/ltsp/ltsp-build-client-functions | 13 ++---
.../ltsp-build-client/Debian/010-debootstrap| 6 +-
2 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/server/Debian/share/ltsp/ltsp-build-client-functions b/server/Debian/share/ltsp/ltsp-build-client-functions
index ae019cc9..8fce9652 100644
--- a/server/Debian/share/ltsp/ltsp-build-client-functions
+++ b/server/Debian/share/ltsp/ltsp-build-client-functions
@@ -16,10 +16,17 @@ add_mirrors() {
components="$COMPONENTS"
fi
-echo "deb $mirror $dist $components" >> $ROOT/etc/apt/sources.list
case $mirror in
-*file:///*)
-dir=$(echo "$mirror" | sed -e 's,^file://,,g')
+file:///media/cdrom)
+echo "deb [trusted=yes] $mirror $dist $components" >> $ROOT/etc/apt/sources.list
+;;
+*)
+echo "deb $mirror $dist $components" >> $ROOT/etc/apt/sources.list
+;;
+esac
+
+case $mirror in
+file:///*) dir=$(echo "$mirror" | sed -e 's,^file://,,g')
mkdir -p $ROOT/$dir
chroot_mount $dir $dir --bind
;;
diff --git a/server/share/ltsp/plugins/ltsp-build-client/Debian/010-debootstrap b/server/share/ltsp/plugins/ltsp-build-client/Debian/010-debootstrap
index f7543cb9..64374c73 100644
--- a/server/share/ltsp/plugins/ltsp-build-client/Debian/010-debootstrap
+++ b/server/share/ltsp/plugins/ltsp-build-client/Debian/010-debootstrap
@@ -30,12 +30,8 @@ case "$MODE" in
echo " $0 --dist etch"
exit 1
fi
-# Strip out apt options, such as [trusted=yes] file:/// ...
-# https://bugs.debian.org/911380
-DEBOOTSTRAP_MIRROR="$(echo $MIRROR | sed -e 's,\[.*\],,g')"
-
# Install base packages
-LC_ALL=C ${DEBOOTSTRAP:-"debootstrap"} $DEBOOTSTRAPOPTS --arch $ARCH $DIST $ROOT $DEBOOTSTRAP_MIRROR
+LC_ALL=C ${DEBOOTSTRAP:-"debootstrap"} $DEBOOTSTRAPOPTS --arch $ARCH $DIST $ROOT $MIRROR
if [ -x "$CROSS_ARCH_EMULATOR" ]; then
# configured for cross architecture install. this requires a
# statically built emulator such as qemu, and binfmt_misc
--
2.20.0.rc2
signature.asc
Description: PGP signature
Bug#915397: systemd-container: fails to start a container going through machines.target or machinectl
On 10.12.18 11:29, ed.go...@free.fr wrote: > For no reason that i can explain precisely, since I updated/rebooted, I > can use the systemd-container 239-15 to spawn the containers... Are you saying, it is now working with your custom kernel as well? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#689528: please add virtio support for cdrom at install time
On Sat, Aug 11, 2018 at 01:20:53PM +0100, Ben Hutchings wrote:
> On Mon, 17 Mar 2014 03:32:41 +0100 Cyril Brulebois wrote:
> > I suspect all we need is to add virtio-modules-${kernel:Version} to
> > pkg-lists/cdrom/.cfg files. Quoting for example the amd64 one:
>
> I agree. This should be done for at least amd64 and i386. It is
> probably sensible for all architectures where virtio-modules is built.
This bug also prevents installation of Debian in OpenBSD's native
vmm(4) hypervisor: https://man.openbsd.org/vmm
The vmm hypervisor only provides virtio devices. Installation of Debian
with a netinstall image fails in the same way as described above.
OpenBSD users who want to use Debian in vmm currently have to install
Debian in Qemu and then boot the installed system in vmm. This works
around the problem but it is very inconvenient.
Bug#916116: diceware hard-codes python3.6 for the build
Package: src:diceware Version: 0.9.5-2 Severity: serious Tags: sid buster patch diceware hard-codes python3.6 for the build, which breaks when python3.6 is removed from the set of supported versions. Just remove the X-Python3-Version: 3.6 in the control file.
Bug#826012: Progress?
On 10.12.18 11:09, Matthias Urlichs wrote: > Hi, > > this bug blocks two others (which actually add systemd units) I don't see how a patch to "service" blocks those other two bug reports? Especially #819156 looks like a completely different issue. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#914059: git-remote-gcrypt: fails without mentioning that the fingerprint for the RSA key sent by the remote host has changed
Hi Sean, Sean Whitton: > Here is a patch. Please let me know the results of any testing you're > able to do. I'm running 1.2-1 on sid. I did not test the exact UX failure mode this bug report is about but I confirm that a similar problem is now fixed. When there's a name resolution failure, previously I would see this: gcrypt: Repository not found: ta...@git.tails.boum.org:repo.git gcrypt: ..but repository ID is set. Aborting. … which is not particularly actionable, suggests there's a problem server-side, and has lead to many support requests from my team-mates. Now I also see: nc: getaddrinfo for host "git.tails.boum.org" port 22: Non-recoverable failure in name resolution ssh_exchange_identification: Connection closed by remote host fatal: Could not read from remote repository. … which tells me it's a name resolution problem and is actionable for me :) I assume this improvement is a side-effect of the fix you prepared for this bug, and it's great! Thank you.
Bug#915997: unyaffs FTBFS with glibc 2.28
Control: tags -1 patch fixed-upstream On Sun, 09 Dec 2018 12:27:44 +0200 Adrian Bunk wrote: > Source: unyaffs > Version: 0.9.6-1 > Severity: serious > Tags: ftbfs buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unyaffs.html > > ... > make V=1 -j1 > make[2]: Entering directory '/build/1st/unyaffs-0.9.6' > cc -D_FORTIFY_SOURCE=2 -O2 -Wall -Wl,-z,relro unyaffs.c -o unyaffs > unyaffs.c: In function 'prt_node': > unyaffs.c:360:15: warning: implicit declaration of function 'major' > [-Wimplicit-function-declaration] >major(oh->yst_rdev), >^ > unyaffs.c:361:15: warning: implicit declaration of function 'minor'; did you > mean 'mknod'? [-Wimplicit-function-declaration] Hi, This is fixed upstream in version 0.9.7. https://github.com/ehlers/unyaffs/commit/51f84b5e I've attached a patch based on that but with less noise. The reason for breakage is mentioned in glibc 2.28 changelog. https://lists.gnu.org/archive/html/info-gnu/2018-08/msg0.html "The macros 'major', 'minor', and 'makedev' are now only available from the header " Regards, Juhani Description: Fix FTBFS with glibc 2.28 https://lists.gnu.org/archive/html/info-gnu/2018-08/msg0.html: "The macros 'major', 'minor', and 'makedev' are now only available from the header " Origin: https://github.com/ehlers/unyaffs/commit/51f84b5e80f98e5df531df0be85e7e75b2cd038f Bug-Debian: https://bugs.debian.org/915997 --- a/unyaffs.c +++ b/unyaffs.c @@ -61,6 +61,9 @@ #include #include #include +#if defined(__linux__) || defined(__GLIBC__) +#include +#endif #ifdef HAS_LUTIMES #include #else
Bug#907512: logwatch: some systemd-logind messages not filtered out
Package: logwatch Version: 7.4.3+git20180713-1 Followup-For: Bug #907512 I have the same problem. I am seeing thousands of these lines in my "logwatch --service secure" output. The offending log lines are all of the form: Dec 8 23:36:05 novatech systemd-logind[1332]: Session 10573 logged out. Waiting for processes to exit. The following patch fixes the problem for me (by ignoring those lines): --- /usr/share/logwatch/scripts/services/secure 2018-10-02 18:52:16.0 +0100 +++ /etc/logwatch/scripts/services/secure 2018-12-10 10:36:24.707158248 + @@ -285,6 +285,7 @@ ( $ThisLine =~ /systemd-logind\[\d+\]: New seat seat\d+\./) or ( $ThisLine =~ /systemd-logind\[\d+\]: Watching system buttons on /) or ( $ThisLine =~ /systemd-logind\[\d+\]: Failed to start session scope (\S+): Transaction is destructive\./) or + ( $ThisLine =~ /systemd-logind\[\d+\]: Session \d+ logged out/) or ( $ThisLine =~ /DIGEST-MD5 common mech free/) or ( $ThisLine =~ /sshguard\[\d+\]: Reloading rotated file /) or ( $ThisLine =~ /sshguard\[\d+\]: Exiting on signal/) or -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8), LANGUAGE=en_GB (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages logwatch depends on: ii exim4-daemon-light [mail-transport-agent] 4.91-8+b1 ii perl 5.28.0-3 Versions of packages logwatch recommends: ii libdate-manip-perl 6.73-1 pn libsys-cpu-perl ii libsys-meminfo-perl 0.99-1+b3 Versions of packages logwatch suggests: ii fortune-mod 1:1.99.1-7+b1 -- no debconf information
Bug#916117: src:unyaffs: debian/control VCS fields should indicate where the Debian packaging is maintained
Package: src:unyaffs Version: 0.9.6-1 Severity: minor Dear maintainer, Vcs-Git and Vcs-Browser should indicate where the Debian package is maintained rather than where the upstream source lives. This is documented in Debian policy: https://www.debian.org/doc/debian-policy/ch-controlfields.html#version-control-system-vcs-fields Regards, Juhani -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#916120: automake: "info automake" does not work (has to be "info automake-1.xx")
Package: automake Version: 1:1.15.1-3ubuntu2 Severity: minor Running “info automake” does not work. It would be nice if the automake package installed suitable links or whatever to the actual, versioned, info file. (I understand that the existence of the automake1.11 package requires the versioning and hence causes the original problem.) -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic'), (100, 'bionic-backports'), (90, 'disco') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-39-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages automake depends on: ii autoconf 2.69-11 ii autotools-dev 20180224.1 automake recommends no packages. Versions of packages automake suggests: ii autoconf-doc 2.69-11 ii gnu-standards 2010.03.11-1 -- no debconf information
Bug#914150: pcmanfm: SIGSEGV, Segmentation fault on opening folder
Dear Maintainer, I'm running in stable Debian version (Strecth). I have installed pcmanfm-dbg libfm-dbg libfm-gtk-dbg libfm-modules-dbg. The bug come when i want open a directory with a lot of activity. (It was shared in nfs with an other system that it write inside). I have maked a shortcut to this directory in pcmanfm on the left side. I hope this informations can help to this bug. Thank you for your work Maintainer. Kind regards, Cédric. *** /var/log/messages *** Dec 10 03:12:13 zzz kernel: [106335.569601] pcmanfm[9161]: segfault at 0 ip 7ff9f3d0c8c0 sp 7fff85fd6b88 error 4 in libfm.so.4.0.5[7ff9f3cf6000+41000] Dec 10 07:45:27 zzz kernel: [122730.232063] pcmanfm[16270]: segfault at 0 ip 7fc03589f8c0 sp 7fff881b3648 error 4 in libfm.so.4.0.5[7fc035889000+41000] Dec 10 11:14:05 zzz kernel: [135248.122280] pcmanfm[15575]: segfault at 0 ip 7f60e68718c0 sp 7ffe3aef9e98 error 4 in libfm.so.4.0.5[7f60e685b000+41000] Dec 10 11:14:09 zzz kernel: [135251.823055] pcmanfm[15597]: segfault at 0 ip 7fef9765d8c0 sp 7fff82d57c78 error 4 in libfm.so.4.0.5[7fef97647000+41000] Dec 10 11:14:12 zzz kernel: [135254.923726] pcmanfm[15609]: segfault at 0 ip 7f297ade98c0 sp 7ffc52a8b3f8 error 4 in libfm.so.4.0.5[7f297add3000+41000] *** dbg report *** (gdb) set pagination 0 (gdb) run Thread 1 "pcmanfm" received signal SIGSEGV, Segmentation fault. fm_file_info_get_path (fi=0x0) at base/fm-file-info.c:982 982 base/fm-file-info.c: Aucun fichier ou dossier de ce type. (gdb) bt #0 fm_file_info_get_path (fi=0x0) at base/fm-file-info.c:982 #1 0x75a4c20f in on_file_info_job_finished (job=0x55a1f480, folder=0x55a31450) at base/fm-folder.c:400 #2 0x75257f75 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x75269f82 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x75272bdc in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x75272fbf in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x75a5d980 in fm_job_emit_finished (job=0x55a1f480) at job/fm-job.c:94 #7 on_idle_cleanup (unused=) at job/fm-job.c:578 #8 0x74f7e6aa in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x74f7ea60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x74f7ed82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x773153b7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #12 0x555670e6 in main (argc=, argv=out>) at pcmanfm.c:282 *** System information *** Subject: pcmanfm: SIGSEGV, Segmentation fault on opening folder Package: pcmanfm Version: 1.2.5-3 Severity: normal -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pcmanfm depends on: ii libatk1.0-0 2.22.0-1 ii libc6 2.24-11+deb9u3 ii libcairo2 1.14.8-1 ii libfm-gtk4 1.2.5-1 ii libfm4 1.2.5-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libx11-6 2:1.6.4-3+deb9u1 ii shared-mime-info 1.8-1+deb9u1 Versions of packages pcmanfm recommends: ii gnome-icon-theme 3.12.0-2 ii gvfs-backends 1.30.4-1 ii gvfs-fuse 1.30.4-1 ii lxde-icon-theme 0.5.1-2 ii lxqt-policykit [polkit-1-auth-agent] 0.11.1-1 pcmanfm suggests no packages. -- no debconf information
Bug#916121: array-info FTBFS with glibc 2.28
Source: array-info Version: 0.16-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/array-info.html ... array_utils.c: In function 'open_ctrl': array_utils.c:63:35: warning: implicit declaration of function 'major' [-Wimplicit-function-declaration] array_data->device_major.major = major(stat_buf.st_rdev); ^ array_utils.c:64:35: warning: implicit declaration of function 'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration] array_data->device_major.minor = minor(stat_buf.st_rdev); ^ ... /usr/bin/ld: array_utils.o: in function `open_ctrl': /build/1st/array-info-0.16/array_utils.c:63: undefined reference to `major' /usr/bin/ld: /build/1st/array-info-0.16/array_utils.c:64: undefined reference to `minor' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:41: array-info] Error 1
Bug#826012: Progress?
Hi, Michael Biebl: > On 10.12.18 11:09, Matthias Urlichs wrote: > > Hi, > > > > this bug blocks two others (which actually add systemd units) > > I don't see how a patch to "service" blocks those other two bug reports? > Especially #819156 looks like a completely different issue. > Granted -- #819156 should probably be blocking on 792894 instead. On the other hand -- what do you mean, "patch to service"? The patch in this bug changes 40-systemd to consider .target files in addition to .service. isc-dhcp-server isn't the only init script that would benefit from this change; there are a couple of other multi-service init scripts out there. -- -- Matthias Urlichs signature.asc Description: PGP signature
Bug#826012: Progress?
Hi, > On the other hand -- what do you mean, "patch to service"? Ah. Wrong bug, sorry, you replied to the message in 826012 while the service patch is in 826011. Doesn't change my argument, though -- .target units should be able to override init scripts. -- -- Matthias Urlichs signature.asc Description: PGP signature
Bug#915344: openfoam FTBFS with glibc 2.28
On Sun, 02 Dec 2018 23:37:05 +0200 Adrian Bunk wrote: > Source: openfoam > Version: 4.1+dfsg1-2.2 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openfoam.html > > ... > fileStat.C: In member function 'bool Foam::fileStat::sameDevice(const > Foam::fileStat&) const': > fileStat.C:78:13: error: 'major' was not declared in this scope > major(status_.st_dev) == major(stat2.status().st_dev) > ^ > fileStat.C:79:13: error: 'minor' was not declared in this scope > && minor(status_.st_dev) == minor(stat2.status().st_dev) Hi, This is most likely fixed by this commit https://github.com/OpenFOAM/OpenFOAM-dev/commit/3fba921563fdb4436f73ace89fe9762474907953 The FTBFS is due to glibc changes, https://lists.gnu.org/archive/html/info-gnu/2018-08/msg0.html: "The macros 'major', 'minor', and 'makedev' are now only available from the header " Regards, Juhani
Bug#826012: Progress?
On 10.12.18 12:13, Matthias Urlichs wrote: > On the other hand -- what do you mean, "patch to service"? The patch > in this bug changes 40-systemd to consider .target files in addition to > .service. I was looking at #826011. I guess I got confused as you posted it to both bug reports. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#916122: pbuilder: misleading warning about missing cgroups
Source: pbuilder Version: 0.230.1 Severity: minor Dear maintainer, I noticed that pbuilder prints a warning at the beginning of each build that cgroups are not available: > W: cgroups are not available on the host, not using them. But they actually are available on my system: # grep cgroup /proc/mounts cgroup /sys/fs/cgroup cgroup rw,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,net_cls,perf_event,net_prio,pids 0 0 pbuilder assumes that cgroup support is only available on systems with systemd. But they can also be used with some basic file system operations in the cgroup mount point. Please change the warning message to something like: "W: cgroup support is currenly only implemented for hosts running systemd" (Or instead add cgroup support independent of systemd (and change severity to wishlist) ;) ) Kind regards, Reiner signature.asc Description: PGP signature
Bug#916008: wmhdplop FTBFS with glibc 2.28
Control: tags -1 + fixed-upstream On Sun, 9 Dec 2018 15:43:14 +0100 Andreas Metzler wrote: > On 2018-12-09 Adrian Bunk wrote: > > Source: wmhdplop > > Version: 0.9.10-1 > [...] > > > devnames.c: In function 'device_id_from_name': > > devnames.c:207:13: warning: implicit declaration of function 'major' > > [-Wimplicit-function-declaration] > >*pmajor = major(stat_buf.st_rdev); > > ^ > [...] > > Seems to miss a > #include Looks like that was indeed added in the upstream repo. https://repo.or.cz/dockapps.git/commitdiff/7cf2e5406b9bc98054404c4c0145c2db0c0ef1e8 -- Juhani
Bug#915476: ledmon FTBFS with glibc 2.28
On Tue, 04 Dec 2018 01:44:28 +0200 Adrian Bunk wrote: > Source: ledmon > Version: 0.79-2 > Severity: serious > Tags: ftbfs buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ledmon.html > > ... > smp.c: In function '_open_smp_device': > smp.c:301:46: warning: implicit declaration of function 'makedev' > [-Wimplicit-function-declaration] > if (mknod(buf, S_IFCHR | S_IRUSR | S_IWUSR, makedev(dmaj, dmin)) < 0) > ^~~ > ... > ./src/smp.c:301: undefined reference to `makedev' This will likely just require a including sys/sysmacros.h i.e. this commit https://github.com/intel/ledmon/commit/e51e1a855df80e34e166984373dce7d765d61d52 Quoting https://lists.gnu.org/archive/html/info-gnu/2018-08/msg0.html: "The macros 'major', 'minor', and 'makedev' are now only available from the header " -- Juhani
Bug#915334: Details on faulty code section + proposal
Good Day, It seems that, since GlibC 2.28, a hack in ipl/cfuncs/fpoll.c fails to detect the newer level of Gnu operating system, as the definition of _STDIO_USES_IOSTREAM seems to be have been dropped. The following patch completely drops support for older Gnu libraries: --- icon-9.4.3.orig/ipl/cfuncs/fpoll.c +++ icon-9.4.3/ipl/cfuncs/fpoll.c @@ -59,12 +59,9 @@ int fpoll(int argc, descriptor *argv)/* /* check for data already in buffer */ /* there's no legal way to do this in C; we cheat */ -#if defined(__GLIBC__) && defined(_STDIO_USES_IOSTREAM)/* new GCC library */ +#if defined(__GLIBC__) if (f->_IO_read_ptr < f->_IO_read_end) RetArg(1); -#elif defined(__GLIBC__) /* old GCC library */ - if (f->__bufp < f->__get_limit) - RetArg(1); #elif defined(_FSTDIO) /* new BSD library */ if (f->_r > 0) RetArg(1); I have no idea if this is a good course of action, and am not exactly happy with my patch, but it does fix the build in Unstable without breaking Stable or Testing, according to my few tests. Haven't had much issues rebuilding my Noweb documents/programs afterwards, but I have just the "iconx" package installed. I hope this helps, -- Étienne Mollier
Bug#909875: O: node-groove -- bindings to libgroove
Control: retitle -1 O: node-groove -- bindings to libgroove Control: reassign -1 wnpp
Bug#780706: Dear
Dear friend. I wrote to you earlier but you did not respond to my mail.I am Attorney Matiko Timbo,i have an important matter i want to discus with you. It is very important and requires your immediate attention.Therefore respond immediately for more details. Regards. Barrister, Matiko Timbo
Bug#916124: glibc: Please disable or ignore math/test-float64x-float128-mul on sparc64
Source: glibc Version: 2.28-2 Severity: normal Tags: upstream User: debian-sp...@lists.debian.org Usertags: sparc64 The test math/test-float64x-float128-mul is currently known to be broken on sparc64 and it has been reported upstream [1]. Since this single test prevents glibc 2.28 from being built on sparc64, I would like to ask for this test to be disabled or ignored unless there is something that speaks against this. Upstream has a sparc64 porterbox available through the gcc compile farm which can be used for debugging the problem. Thanks, Adrian > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=23886 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#913136: security update for xml-security-c in Stretch
wf...@niif.hu writes:
> The backport of the patches is fairly straightforward indeed, but up
> to now I couldn't reproduce the issue itself.
Hi Security Team,
After a couple more rounds with upstream it turns out that while #905332
affected simple parsing of the structure, this one affects verification
using an invalid structure. So one has to convince the code to actually
attempt that verification, which does not seem easily possible with the
(recommended) explicit key trust engine. However, deployments using the
PKIX trust engine are still prone to remote DoS, though I can't easily
test this. All in all, for security and symmetry I recommend fixing
this issue in stretch the same way it was fixed in jessie by Thorsten.
Please find the debdiff attached.
--
Thanks,
Feri
diff -Nru xml-security-c-1.7.3/debian/changelog
xml-security-c-1.7.3/debian/changelog
--- xml-security-c-1.7.3/debian/changelog 2018-08-03 11:32:52.0
+0200
+++ xml-security-c-1.7.3/debian/changelog 2018-12-10 11:45:41.0
+0100
@@ -1,3 +1,20 @@
+xml-security-c (1.7.3-4+deb9u2) stretch-security; urgency=high
+
+ * [12dd825] New patches: DSA verification crashes OpenSSL on invalid
+combinations of key content.
+Particular KeyInfo combinations result in incomplete DSA key structures
+that OpenSSL can't handle without crashing. In the case of Shibboleth
+SP software this manifests as a crash in the shibd daemon. Exploitation
+is believed to be possible only in deployments employing the PKIX trust
+engine, which is generally recommended against.
+The upstream patches backported from 2.0.2 apply analogous safeguards to
+the RSA and ECDSA key handling as well.
+Upstream bug: https://issues.apache.org/jira/browse/SANTUARIO-496
+CVE: not assigned
+Thanks to Scott Cantor (Closes: #913136)
+
+ -- Ferenc Wágner Mon, 10 Dec 2018 11:45:41 +0100
+
xml-security-c (1.7.3-4+deb9u1) stretch-security; urgency=high
* [93b87c6] New patch: Default KeyInfo resolver doesn't check for empty
diff -Nru
xml-security-c-1.7.3/debian/patches/SANTUARIO-496-DSA-verification-crashes-OpenSSL-on-invalid.patch
xml-security-c-1.7.3/debian/patches/SANTUARIO-496-DSA-verification-crashes-OpenSSL-on-invalid.patch
---
xml-security-c-1.7.3/debian/patches/SANTUARIO-496-DSA-verification-crashes-OpenSSL-on-invalid.patch
1970-01-01 01:00:00.0 +0100
+++
xml-security-c-1.7.3/debian/patches/SANTUARIO-496-DSA-verification-crashes-OpenSSL-on-invalid.patch
2018-12-10 11:44:59.0 +0100
@@ -0,0 +1,103 @@
+From: Scott Cantor
+Date: Thu, 11 Oct 2018 15:13:40 +
+Subject: SANTUARIO-496 - DSA verification crashes OpenSSL on invalid
+ combinations of key content
+
+Backport of
+git-svn-id:
https://svn.apache.org/repos/asf/santuario/xml-security-cpp/trunk@1843562
13f79535-47bb-0310-9956-ffa450edef68
+---
+ xsec/enc/OpenSSL/OpenSSLCryptoKeyDSA.cpp | 12
+ xsec/enc/OpenSSL/OpenSSLCryptoKeyEC.cpp | 12
+ xsec/enc/OpenSSL/OpenSSLCryptoKeyRSA.cpp | 12
+ 3 files changed, 36 insertions(+)
+
+diff --git a/xsec/enc/OpenSSL/OpenSSLCryptoKeyDSA.cpp
b/xsec/enc/OpenSSL/OpenSSLCryptoKeyDSA.cpp
+index 57999a2..5bdf133 100644
+--- a/xsec/enc/OpenSSL/OpenSSLCryptoKeyDSA.cpp
b/xsec/enc/OpenSSL/OpenSSLCryptoKeyDSA.cpp
+@@ -164,6 +164,12 @@ bool OpenSSLCryptoKeyDSA::verifyBase64Signature(unsigned
char * hashBuf,
+ "OpenSSL:DSA - Attempt to validate signature with empty
key");
+ }
+
++XSECCryptoKey::KeyType keyType = getKeyType();
++if (keyType != KEY_DSA_PAIR && keyType != KEY_DSA_PUBLIC) {
++throw XSECCryptoException(XSECCryptoException::DSAError,
++"OpenSSL:DSA - Attempt to validate signature without public key");
++}
++
+ char* cleanedBase64Signature;
+ unsigned int cleanedBase64SignatureLen = 0;
+
+@@ -264,6 +270,12 @@ unsigned int
OpenSSLCryptoKeyDSA::signBase64Signature(unsigned char * hashBuf,
+ "OpenSSL:DSA - Attempt to sign data with empty key");
+ }
+
++KeyType keyType = getKeyType();
++if (keyType != KEY_DSA_PAIR && keyType != KEY_DSA_PRIVATE) {
++throw XSECCryptoException(XSECCryptoException::DSAError,
++"OpenSSL:DSA - Attempt to sign data without private key");
++}
++
+ DSA_SIG * dsa_sig;
+
+ dsa_sig = DSA_do_sign(hashBuf, hashLen, mp_dsaKey);
+diff --git a/xsec/enc/OpenSSL/OpenSSLCryptoKeyEC.cpp
b/xsec/enc/OpenSSL/OpenSSLCryptoKeyEC.cpp
+index 3233343..09ba69e 100644
+--- a/xsec/enc/OpenSSL/OpenSSLCryptoKeyEC.cpp
b/xsec/enc/OpenSSL/OpenSSLCryptoKeyEC.cpp
+@@ -151,6 +151,12 @@ bool
OpenSSLCryptoKeyEC::verifyBase64SignatureDSA(unsigned char * hashBuf,
+ "OpenSSL:EC - Attempt to validate signature with empty
key");
+ }
+
++KeyType keyType = getKeyType();
++if (keyType != KEY_EC_PAIR && keyType != KEY_EC_PUBLIC) {
++throw XSECCryptoException(XSECCryptoEx
Bug#916125: hunspell: "hunspell -D" does not print loaded dictionary
Package: hunspell
Version: 1.7.0-2
Severity: normal
Tags: patch upstream
Dear Maintainer,
Commit 27829f0 which pplies to version 1.7.0 makes "hunspell -D" without files
quit early.
Too early to print the loaded dictionary, making "hunspell -D" not perform as
expexted, and
breaking eacs flyspell.
Reverting the commit, or moving the leave logic a little later, solves this.
cheers,
Itaï.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (600, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages hunspell depends on:
ii hunspell-en-gb [hunspell-dictionary] 1:6.1.3-1
ii hunspell-es [hunspell-dictionary]1:6.1.3-1
ii hunspell-fr-classical [hunspell-dictionary] 1:6.3-1
ii hunspell-he [hunspell-dictionary]1:6.1.3-1
ii libc62.28-2
ii libgcc1 1:8.2.0-12
ii libhunspell-1.7-01.7.0-2
ii libncursesw6 6.1+20181013-1
ii libreadline7 7.0-5
ii libstdc++6 8.2.0-12
ii libtinfo66.1+20181013-1
hunspell recommends no packages.
Versions of packages hunspell suggests:
ii unzip 6.0-21
-- no debconf information
Description:
TODO: Put a short summary on the line above and replace this paragraph
with a longer explanation of this change. Complete the meta-information
with other relevant fields (see below for details). To make it easier, the
information below has been extracted from the changelog. Adjust it or drop
it.
.
hunspell (1.7.0-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Exit little less early on -D with no file args
Author: Itaï BEN YAACOV
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update: 2018-12-10
--- hunspell-1.7.0.orig/src/tools/hunspell.cxx
+++ hunspell-1.7.0/src/tools/hunspell.cxx
@@ -2066,9 +2066,6 @@ int main(int argc, char** argv) {
gettext(
"AVAILABLE DICTIONARIES (path is not mandatory for -d
option):\n"));
search(path, NULL, NULL);
-if (-1 == arg_files) {
- exit(0);
-}
}
if (!privdicname)
@@ -2116,6 +2113,10 @@ int main(int argc, char** argv) {
exit(1);
}
+ if (showpath && -1 == arg_files) {
+exit(0);
+ }
+
/* open the private dictionaries */
if (HOME) {
buf.assign(HOME);
Bug#909714: gff2aplot: Please provide autopkgtest
Control: tags -1 pending I wrote an autopkgtest which uncovered actual bugs in the software. One was (hopefully - reviews welcome) fixed[1] The test suite exposes some other errors - the output is cp: cannot stat 'taf6.mmhs.genomic.tblastx.png': No such file or directory mogrify: unable to open image `taf6.mmhs.genomic.tblastx.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. cp: cannot stat 'taf6.mmhs.genomic.tblastx.aplot.png': No such file or directory mogrify: unable to open image `taf6.mmhs.genomic.tblastx.aplot.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. cp: cannot stat 'taf6.mmhs.genomic.blastn.aplot_conf.png': No such file or directory mogrify: unable to open image `taf6.mmhs.genomic.blastn.aplot_conf.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. cp: cannot stat 'taf6.mmhs.genomic.tblastx.aplot_conf.png': No such file or directory mogrify: unable to open image `taf6.mmhs.genomic.tblastx.aplot_conf.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. cp: cannot stat 'taf6.mmhs.genomic.blast.merge.png': No such file or directory mogrify: unable to open image `taf6.mmhs.genomic.blast.merge.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. cp: cannot stat 'taf6.mmhs.genomic.blast.merge_conf.png': No such file or directory mogrify: unable to open image `taf6.mmhs.genomic.blast.merge_conf.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. 'taf6.mmhs.genomic.blastn.png' -> 'taf6.mmhs.genomic.blastn.s.png' 'taf6.mmhs.genomic.blastn.aplot.png' -> 'taf6.mmhs.genomic.blastn.aplot.s.png' Some errors were found in logfiles taf6.mmhs.genomic.blast.merge.log:Can't use an undefined value as an ARRAY reference at /usr/bin/gff2aplot line 1737, line 12. taf6.mmhs.genomic.blast.merge_conf.log:Can't use an undefined value as an ARRAY reference at /usr/bin/gff2aplot line 1737. taf6.mmhs.genomic.blastn.aplot.log:Redundant argument in sprintf at /usr/bin/gff2aplot line 3674. taf6.mmhs.genomic.blastn.aplot.log:Use of uninitialized value $_[1] in string at /usr/bin/gff2aplot line 3734, line 1. taf6.mmhs.genomic.blastn.aplot_conf.log:Can't use an undefined value as an ARRAY reference at /usr/bin/gff2aplot line 1737, line 12. taf6.mmhs.genomic.blastn.log:Redundant argument in sprintf at /usr/bin/gff2aplot line 3674. taf6.mmhs.genomic.blastn.log:Use of uninitialized value $_[1] in string at /usr/bin/gff2aplot line 3734, line 1. taf6.mmhs.genomic.tblastx.aplot.log:Redundant argument in sprintf at /usr/bin/gff2aplot line 3674. taf6.mmhs.genomic.tblastx.aplot.log:Use of uninitialized value $_[1] in string at /usr/bin/gff2aplot line 3734, line 1. taf6.mmhs.genomic.tblastx.aplot.log:Can't use an undefined value as an ARRAY reference at /usr/bin/gff2aplot line 2934. taf6.mmhs.genomic.tblastx.aplot_conf.log:Can't use an undefined value as an ARRAY reference at /usr/bin/gff2aplot line 1737, line 12. taf6.mmhs.genomic.tblastx.aplotgff.log:Can't open taf6.mmhs.genomic.tblastx: No such file or directory at /usr/bin/parseblast line 889. taf6.mmhs.genomic.tblastx.log:Redundant argument in sprintf at /usr/bin/gff2aplot line 3674. taf6.mmhs.genomic.tblastx.log:Use of uninitialized value $_[1] in string at /usr/bin/gff2aplot line 3734, line 1. taf6.mmhs.genomic.tblastx.log:Can't use an undefined value as an ARRAY reference at /usr/bin/gff2aplot line 2934. PostScript file ./taf6.mmhs.genomic.blast.merge.ps has zero bytes. PostScript file ./taf6.mmhs.genomic.tblastx.aplot.ps has zero bytes. PostScript file ./taf6.mmhs.genomic.blast.merge_conf.ps has zero bytes. PostScript file ./taf6.mmhs.genomic.tblastx.ps has zero bytes. PostScript file ./taf6.mmhs.genomic.tblastx.aplot_conf.ps has zero bytes. PostScript file ./taf6.mmhs.genomic.blastn.aplot_conf.ps has zero bytes. convert: unable to open image `*.s.png': No such file or directory @ error/blob.c/OpenBlob/2874. convert: image file does not contain any image data `*.s.png' @ error/vid.c/ReadVIDImage/208. convert: no images defined `splicesites.summary.png' @ error/convert.c/ConvertImageCommand/3258. This should be fixed before uploading. Kind regards Andreas. [1] https://salsa.debian.org/med-team/gff2aplot/blob/master/debian/patches/perl_5.28.patch -- http://fam-tille.de
Bug#916126: ITP: rtpengine -- Proxy for RTP and media streams
Package: wnpp Severity: wishlist Owner: Victor Seva -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rtpengine Version : mr6.5.2.1 Upstream Author : Sipwise Development Team * URL : https://github.com/sipwise/rtpengine/ * License : GPL-3+ with OpenSSL exception Programming Lang: C Description : Proxy for RTP and media streams The Sipwise NGCP rtpengine is a proxy for RTP traffic and other UDP based media traffic. It's meant to be used with the Kamailio SIP proxy and forms a drop-in replacement for any of the other available RTP and media proxies. Currently the only supported platform is GNU/Linux. Features Media traffic running over either IPv4 or IPv6 Bridging between IPv4 and IPv6 user agents Bridging between different IP networks or interfaces TOS/QoS field setting Customizable port range Multi-threaded Advertising different addresses for operation behind NAT In-kernel packet forwarding for low-latency and low-CPU performance Automatic fallback to normal userspace operation if kernel module is unavailable Support for Kamailio's rtpproxy module Legacy support for old OpenSER mediaproxy module When used through the rtpengine module (or its older counterpart called rtpproxy-ng), the following additional features are available: Full SDP parsing and rewriting Supports non-standard RTCP ports (RFC 3605) ICE (RFC 5245) support: Bridging between ICE-enabled and ICE-unaware user agents Optionally acting only as additional ICE relay/candidate Optionally forcing relay of media streams by removing other ICE candidates SRTP (RFC 3711) support: Support for SDES (RFC 4568) and DTLS-SRTP (RFC 5764) AES-CM and AES-F8 ciphers, both in userspace and in kernel HMAC-SHA1 packet authentication Bridging between RTP and SRTP user agents Support for RTCP profile with feedback extensions (RTP/AVPF, RFC 4585 and 5124) Arbitrary bridging between any of the supported RTP profiles (RTP/AVP, RTP/AVPF, RTP/SAVP, RTP/SAVPF) RTP/RTCP multiplexing (RFC 5761) and demultiplexing Breaking of BUNDLE'd media streams (draft-ietf-mmusic-sdp-bundle-negotiation) Recording of media streams, decrypted if possible Transcoding and repacketization Rtpengine does not (yet) support: Playback of pre-recorded streams/announcements ZRTP, although ZRTP passes through rtpengine just fine This package will be maintained under the pkg-voip team umbrella -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjxnK3NQqQtRVY3MMUaCbGM9aUGgFAlwOV1QACgkQUaCbGM9a UGiugg//fT1Sq3GdbqCYtZy/qjKUbLqGMM5XOoyz22fOjBPryNvCwdmNWpS/zlIn zKosWxrOcc7oeSch9f249qtbNyhQ52Ctz37W0qnqnOtSpPDtAhV/mMmB0l4R0pGn C5Afz9aTdM6+hVjF4qkdkRSGP0nV5uBwqIaaorFvl+9pAdhLFVfs14Q/KoHMxhTt dnh3jyvanUmru+6Aoy+J+lZRM0SUNec6Sa3q4Vxm38W2mBGcxM2iqu5yHeUckGWm z5vdU7wCmuB2d6IgIHlDS7EJYqsZpjJqWBNWo7qoBqKeU3zIj61c7o6Y4Locvcjr vZ207KnlhQ2oPeX9mtzptRsJKwGbZdWMOfwrVw4gOfyGaw5uumnVODvMR5VZuSBs 7S/fX2YKvVzmZdhPq/xljCG9IzPgea7MEb40N5mVPNEArlsEbAhaqzxn73c80OIy M17bnB1IKmdU4Viy9/edpdt3CRJdRcy7L4URRhLd+y7aHcTqACJ7Llt58MQMeFTP FadFU4niZXBD4Y3yuJKpARleAVaYb12PxIGrJsNnrTjvd74Ii57IuBRjr4D3x1FS tpzs9dk+qfHJoMlRnOZSKVqGiJDgYmF4zA++cRkBwhdUs/dp6RLof3Jlnx3HdSyh fJ27yzMkuNq900UAmwjv1UgoyojvClxjcUoWErzQQrsB47exnuE= =rni1 -END PGP SIGNATURE-
Bug#852312: O: codelite -- Powerful and lightweight IDE
Control: retitle -1 O: codelite -- Powerful and lightweight IDE Hi, On Mon, 23 Jan 2017 13:30:33 + James Cowgill wrote: > Package: wnpp > Severity: normal > > Hi, > > I'd like to give codelite up for adoption if anyone is interested. I > don't really use it much anymore and it could do with a maintainer who > does use it. It's a fairly large package and usually requires quite a > bit of time to update so only adopt this if you're willing to put the > effort into it. I'd prefer not to sponsor this package for anyone as I > expect the review would take just as much time as updating the package > in the first place! There is a git packaging repository on collab-maint. > > I'll continue maintaining it until someone appears. It has become apparent that I don't have the time to keep up maintaining this, therefore I'm orphaning it now. The git repository is here, and it's also pushed to dgit. https://salsa.debian.org/debian/codelite James signature.asc Description: OpenPGP digital signature
Bug#915537: MongoDB SSPL v1 license and the DFSG
On Wed, Dec 05, 2018 at 09:48:03AM +, Debian Bug Tracking System wrote: >... > However, the SSPL is clearly not in the sprit of the DFSG, yet alone > complimentary to the Debian's goals of promoting software or user > freedom. >... You are treating "make it easy to build proprietary services on top of Debian" as the "sprit of the DFSG". There is no general agreement in Debian about this, and another major opinion is along the spirit of the (A)GPL to enforce as much of the system as possible to be non-proprietary. > ... it is difficult to point towards a clear-cut > violation of the DFSG that we could all agree on due to both legal and > language fuzziness. However, even if we could, there is always a > slight tendency to treat the DFSG (and the Open Source Definition more > generally) as a of narrowly-interpretable checklist. >... It was surely not intended, but it comes across like an completely arbitrary decision. Please elaborate what is the relevant difference that makes the AGPL DFSG-free but SSPL v1 not. This might also be useful input for upstream how to make their licence DFSG-compliant - upstream seems to be working on the fuzziness issue, so giving good feedback on that might help them making their licence DFSG-compliant. > Regards, cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#913069: marked as done (transition: python3.7 as default)
Control: reopen -1 Hi, libarcus (3.3.0-2) unstable; urgency=medium . [ Gregor Riepl ] * Blacklisted incompatible python3-sip version (4.19.11+dfsg-1) * Added new symbols that appear with current build dependencies. Closes: #914953 * Depend on python3-dev since we're not building for all Python interpreters. Closes: #913069 That's a release.debian.org tracking bug, not a bug against your package. Please don't close such bugs in uploads to the archive. In this particular case, I would guess you meant to close #905803, which /is/ filed against src:liarcus. Regards, Adam
Bug#785356:
-- Ich wünsche dir einen schönen Tag Ich bin Frau Changing Kong für die Mitarbeiter der Wing Hang Bank hier in Hongkong. Kann ich den Überweisungen von 13,991,674 $ vertrauen? Grüße
Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services
Hi Am 01.06.16 um 14:07 schrieb Terry Burton: > This message [1] identifies that compound target units are the > appropriate mechanism for controlling multiple service units. > > The LSB override hook currently only consider .service units, ignoring > compound .target units. > > Support for this would be useful for providing systemd scripts for > multi-daemon services such as ISC DHCP server (with IPv4 and IPv6; > discussions ongoing here [2]) and PostgreSQL. > > A patch for /lib/lsb/init-functions.d/40-systemd is attached. We probe > for a compound .target unit (having component services in the derived > ConsistsOf property) of matching service name invoking this as we > would a plain .service unit. I don't think using ConsistsOf= is the right property to determine whether to use a target or not. There can be targets without ConsistsOf and there can also be services with ConsistsOf Say you have test.service and test.target. I'm not sure if there is a reliable way to detect whether the user wanted test.service or test.target when running "/etc/init.d/test ..." -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#916127: ITS: mtools
Package: mtools Version: 4.0.18-2.1 Severity: important Dear mtools maintainer, After checking the qualification criteria, I am filing this Intent To Salvage (ITS) bug, following the process outlined in: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging For reference: > After the 21 days delay, if no answer has been sent to the bug [..] … I make this the 31st December 2018. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#916128: coyim FTBFS: test failure
Source: coyim
Version: 0.3.8+ds-5
Severity: serious
Tags: ftbfs
Some recent change in unstable makes coyim FTBFS:
https://tests.reproducible-builds.org/debian/history/coyim.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/coyim.html
...
FAIL: connection_policy_test.go:161:
ConnectionPolicySuite.Test_buildProxyChain_Returns
connection_policy_test.go:181:
c.Check(chain, DeepEquals, expectedProxy)
... obtained *socks.Dialer = &socks.Dialer{cmd:1, proxyNetwork:"tcp",
proxyAddress:"proxy.local", ProxyDial:(func(context.Context, string, string)
(net.Conn, error))(0x678b20), AuthMethods:[]socks.AuthMethod(nil),
Authenticate:(func(context.Context, io.ReadWriter, socks.AuthMethod)
error)(nil)}
... expected *socks.Dialer = &socks.Dialer{cmd:1, proxyNetwork:"tcp",
proxyAddress:"proxy.local", ProxyDial:(func(context.Context, string, string)
(net.Conn, error))(0x678b20), AuthMethods:[]socks.AuthMethod(nil),
Authenticate:(func(context.Context, io.ReadWriter, socks.AuthMethod)
error)(nil)}
OOPS: 31 passed, 1 FAILED
--- FAIL: Test (5.08s)
...
Bug#915136: Follow up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, @praveen, how can I help you to find and/or resolve the bug? I cannot understand the problem itself, but I try to explain in some more detail how the bug have appeared. Installation: - The installation itself is a database migrated from debian gitlab 8.13 directly to 11.1 if I remember correctly. - I didn't use the installation until 11.3, because I've waiting for some information about another bugs (#914159, #914496, and others). - The installation are a usual one, but I've moved /var/lib/gitlab to /home/gitlab with a link. The references on config files of gitlab, gitlab-shell and gitaly to repositories are pointing to correct folder (/home/gitlab/repositories). That's because I didn't have enough space free on /. - Gitlab check didn't show any errors. Installation has been working without problem for some time, doing lot of commits. Work with gitlab: - I've working with another person on a concrete repository. These repo are from gitlab 8.13. Also have a remote (on my local clone) from github, and I merge changes from github to my repo. I've do at least 3 of these merges (with more than 600 commits total) and pushed to gitlab, without problem. - Lot of the merged commits are signed, my ones are signed too. - The problem appears after one concrete commit. I've do a push to the repo of a simple change (a modification of .gitlab.ci.yml only), and, after it, my partner on the project do another one with some code changes. He didn't a pull before doing it, and generated a double commit. One for their changes, and another one "merge branch master...". After push these two commits, the problem appears. I've tried restarting gitlab / gitaly services, I've tried to trigger a repository check. None of them help with the problem. If I can do some tests, please tell me. Thanks, https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlwOZqwACgkQCU2zE9sy 6H8qTQ//c+vNEdnVe05UoQHSVJ/+xbJuJTzY919MhYG6X7i9Yl8XwBB6/Msnh+07 BlqF1NoObHvCe8SMg1Dr3H6qJhbWniykzwZlX+6EkqIjXayzfW547sQzzGgCswwK 5mfJ6QzTaR0NWSC3DmBp/QGYhW5PrXxMujipiH8ERPDXbiRMCjNtwfHh4IF2p3MU ALt2MZN3B6Np6spvm2wNM60l5Cznb7CAE+Z21yKtEZbiwSC8rhtxizFzFJHat1mq qnC3ljep3Vg+jUCwOYPGKNgsWRpWTU31symHHAFZXfB/osAU6X1YixqgP4Gkj88G 77hCqgcIJeViswW5GgwEJaL7a3TLuCB1brAupvHqWzC6+goRDxOoy9yeKD6Xp3LU +/ezJidWBE9/5i/4yUH8c64roATRv5rgEbXl57Nc1L9x7+oKz7T949Roa1037+8a 1oXJ+zHXBtg8DpTzRjOqqoaVUpY9Z/4HGuEZzZFdo1FwQ6fcZsKKYWxrPTJRVmQD /5bKiNUqm7Jfy1JxeZ5lpXILHQDuMwbzrYNWcC18JZvm01lMKR/htcRfIoyaXrqr +eBR9FGOYzVJrkZYmMlx0aaAOh6NaWBMzsaspQDqOY28CNVVst/wAhB1sbUtRc/I lM02oQ1+d+JVuTCYJoZV8Q5GTt91WGKJmqXEmDb7HasS4bo7Mv4= =Ccxa -END PGP SIGNATURE-
Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services
Am 10.12.18 um 14:12 schrieb Michael Biebl: > Say you have test.service and test.target. > I'm not sure if there is a reliable way to detect whether the user > wanted test.service or test.target when running "/etc/init.d/test ..." Just tested systemctl. If you have a test.service and test.target and you run systemctl start test then test.service is started but not test.target. So, I guess what would be more in line with the systemctl behaviour is a patch which does the following: If you run /etc/init.d/test start: - We start test.service if it exists - If test.service does not exist and a test.target exist, start the target. - If no service and target exists, fall through and let the sysv init script handle the request directly Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#912306: ITS: efitools
Hi Arnaud, > ITS: efitools FYI I believe that this bug number has reached the 21 days as specified in: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#909663: ITS: stterm -- missing upstream versions, neglected bugs, unresponsive maintainer
Hi Paride, > ITS: stterm -- missing upstream versions, neglected bugs, unresponsive > maintainer FYI I believe that this bug number has reached the 21 days as specified in: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#914070: ITS: dhcpcd5
Hi Scott, > ITS: dhcpcd5 FYI I believe that this bug number has reached the 21 days as specified in: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#909663: ITS: stterm -- missing upstream versions, neglected bugs, unresponsive maintainer
X-Debbugs-CC: kilob...@angband.pl Chris Lamb wrote on 10/12/2018: > Hi Paride, > >> ITS: stterm -- missing upstream versions, neglected bugs, unresponsive >> maintainer > > FYI I believe that this bug number has reached the 21 days as > specified in: > > > https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging Hi Chris, the new package is ready: https://salsa.debian.org/debian/st It is currently being reviewed by one of my usual sponsors. :) Cheers, Paride
Bug#915112: pymol: FTBFS with glew 2.1
On Fri, 7 Dec 2018 09:47:33 +0200 Juhani Numminen wrote: > Indeed it seems that the patch didn't affect glew.h. I don't know the package > too well but that's a >1 MB header that cannot be found in upstream git, and > I get the impression that it is generated using auto/Makefile. > > The debian build logs don't contain "Creating glew.h" so I believe the > original > upstream-distributed include/GL/glew.h is shipped. The generation of the headers seems to be "special". It starts with cloning a git repository (RC bug? does not include source to regenerate the headers) and quickly fails with bash: bin/update_ext.sh: /bin/bash^M: bad interpreter: No such file or directory where I stopped trying to understand what's happening. You should probably just apply the patch additionally to the shipped include/GL/glew.h Andreas
Bug#906770: README.Debian could use some clarificatons
Le 20/08/2018 à 23:36, Moritz Muehlenhoff a écrit : > For my tests of the jetty9 security update for stretch (released as > DSA 4278) I had looked into creating a test setup and the README.Debian > confused me quite a bit (and external references usally refer to a > totally different way to deploy Jetty using the upstream packages): > > It mentions: > | Additional contexts can be configured and (hot) deployed via the > | /etc/jetty9/contexts directory (linked from /usr/share/jetty9/contexts). > > But it seems that is now replaced by /etc/jetty9/start.d?` Good catch, /contexts is probably a left over from a previous version. But start.d looks more like a directory for .ini config files than .xml context files. > Also from > | Webapps can be deployed by placing them in /var/lib/jetty9/webapps > | (linked from /usr/share/jetty9/webapps) > > it wasn't obvious for me whether the .war file or a config file should > be placed in /var/lib/jetty9/webapps. I think it supports both. Upstream has the following README file in this directory (I'll add it in the next update) : | This directory is scanned by the WebAppDeployer provider for web | applications to deploy using the following conventions: | | + A directory called example/ will be deployed as a standard web | application if it contains a WEB-INF/ subdirectory, otherwise it will be | deployed as context of static content. The context path will be /example | (eg http://localhost:8080/example/) unless the base name is "root" (not | case sensitive), in which case the context path is /. If the directory name | ends with ".d" it is ignored (but may still be used by explicit configuration). | | + A file called example.war will be deployed as a standard web application | with the context path /example (eg http://localhost:8080/example/). If the | base name is root, then the context path is /. If example.war and example/ | exist, then only the WAR is deployed (which may use the directory as an | unpack location). | | + An XML file like example.xml will be deployed as a context whose | configuration is defined by the XML. The context path must be set by | the configuration itself. If example.xml and example.war exist, then | only the XML is deployed (which may use the war in its configuration). | | This directory is scanned for additions, removals and updates | for hot deployment. | | To configure the deployment mechanism, edit the files: |start.d/500-deploy.ini |etc/jetty-deploy.ini | | To disable the auto deploy mechanism use the command: | |java -jar start.jar --disable=deploy
Bug#916129: zita-rev1 FTBFS
Source: zita-rev1 Version: 0.2.1-5 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zita-rev1.html ... g++ -g -O2 -ffile-prefix-map=/build/1st/zita-rev1-0.2.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -ffast-math -Wall -MMD -MP -DVERSION=\"0.2.1\" -DSHARED=\"/usr/share/zita-rev1\" -I/usr/X11R6/include `freetype-config --cflags` -c -o pareq.o pareq.cc /bin/sh: 1: freetype-config: not found In file included from /usr/include/clxclient.h:31, from styles.h:25, from styles.cc:22: /usr/include/X11/Xft/Xft.h:39:10: fatal error: ft2build.h: No such file or directory #include ^~~~ compilation terminated. make[1]: *** [: styles.o] Error 1 freetype-config has been removed in Debian in favour of pkg-config. The package also lacks a direct build dependency on libfreetype6-dev.
Bug#916130: zita-bls1 FTBFS due to freetype-config usage
Source: zita-bls1 Version: 0.1.0-3 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zita-bls1.html ... g++ -g -O2 -ffile-prefix-map=/build/1st/zita-bls1-0.1.0=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -ffast-math -Wall -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.1.0\" -DSHARED=\"/usr/share/zita-bls1\" -I/usr/X11R6/include `freetype-config --cflags` -c -o shuffler.o shuffler.cc /bin/sh: 1: freetype-config: not found In file included from /usr/include/clxclient.h:31, from styles.h:25, from styles.cc:22: /usr/include/X11/Xft/Xft.h:39:10: fatal error: ft2build.h: No such file or directory #include ^~~~ compilation terminated. freetype-config has been removed in Debian in favour of pkg-config. The package also lacks a direct build dependency on libfreetype6-dev.
Bug#913645: Oldstable also affected
Dear Maintainer, since upstream was able to reproduce the problem and locate the commits that cause it I did no further tests. It seems like they will undo two commits in order to solve the problem, hopefully not too many people get bit by this. Cheers, Bastian On 12/3/18 12:58 PM, Bastian Neuburger wrote: Hi Carsten, I forgot to report back, but I also created Upstream bug 1510212 (https://bugzilla.mozilla.org/show_bug.cgi?id=1510212). As I stated there it might take a while until I can test migration again, since I reinstalled my test machine with Buster and thus have no test environment with Jessie or Stretch right now. I'll report back to upstream how this goes.
Bug#905254: Relations to other packages
Cacti: Latest version of cacti upstream still uses PHPMailer 5.2.x. I've created a bug upstream: https://github.com/Cacti/cacti/issues/2206 tt-rss: It seems like latest version don't necessarily use phpmailer anymore: (https://git.tt-rss.org/fox/tt-rss/src/master) >commit 57932e183745bada9c6183056597cb5276f68d10 >Author: Andrew Dolgov >Date: Thu Nov 22 14:45:14 2018 +0300 > >remove PHPMailer and related directives from config.php-dist; add pluggable Mailer class > maybe tt-rss maintainer should be asked to update to latest upstream version? wordpress: I haven't understand what should be done ocsinventory-server & ocsinventory-reports: = Newest upstream version (2.5) will depend on PHPMailer 6.x Not upgrading libphp-phpmailer blocks upgrade to newest upstream versions of these packages (which also somehow blocks #905396 and CVE-2018-14473). I'll try to create the link between those bugs (#905254 block #905396) Br, Cyrille
Bug#916119: dwdiff: Please use pkg-config to detect icu
> Please let me know if you need any help with this change. To be honest I'm an autoconf guy, and dwdiff uses a somewhat ad-hoc config system. No doubt I could puzzle it out, but if you've already run through that gauntlet I'd certainly say: patches welcome! (It looks to me like pkg-config icu-i18n --libs-only-l is all that's needed, and the remaining icu-config calls can be simply stripped out. Maybe pkg-config icu-i18n --cflags just for completeness, although it returns the empty string so in the end there's not much point.)
Bug#916131: RFS: lebiniou/3.29-1 -- displays images that evolve with sound
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "lebiniou": * Package name: lebiniou Version : 3.29-1 Upstream Author : Olivier Girondel * URL : https://biniou.net * License : GPL-2+ Section : graphics It builds this binary packages: lebiniou - displays images that evolve with sound The package appears to be lintian-clean. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/lebiniou Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/lebiniou/lebiniou_3.29-1.dsc Changes since the last upload: * New upstream release 3.29. * debian/control: Remove Build-Depends: libsdl-ttf2.0-dev. * debian/control: Add Build-Depends: libsdl2-ttf-dev, pandoc, libsndfile1-dev. Regards, Olivier Girondel
Bug#916132: hepmc FTBFS: FAIL testWeights
Source: hepmc Version: 2.06.09-3 Severity: serious Tags: ftbfs Some recent change in unstable makes hepmc FTBFS: https://tests.reproducible-builds.org/debian/history/hepmc.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hepmc.html ... make check-TESTS make[3]: Entering directory '/build/1st/hepmc-2.06.09/test' make[4]: Entering directory '/build/1st/hepmc-2.06.09/test' PASS: testSimpleVector PASS: testUnits PASS: testHepMC.sh PASS: testHepMCIteration.sh PASS: testMass.sh PASS: testFlow.sh PASS: testStreamIO.sh PASS: testPrintBug.sh PASS: testMultipleCopies PASS: testPolarization.sh ../test-driver: line 107: 52027 Segmentation fault "$@" > $log_file 2>&1 FAIL: testWeights HepMC 2.06.09: test/test-suite.log # TOTAL: 11 # PASS: 10 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: testWeights = FAIL testWeights (exit status: 139) Testsuite summary for HepMC 2.06.09 # TOTAL: 11 # PASS: 10 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/test-suite.log Please report to https://savannah.cern.ch/projects/hepmc/ make[4]: *** [Makefile:881: test-suite.log] Error 1 Backtrace: Core was generated by `/tmp/hepmc-2.06.09/test/.libs/testWeights'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fc39a374474 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x7fc39a374474 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x7fc39a4ddc08 in std::_Rb_tree_iterator, std::allocator > const, unsigned long> >::operator++ (this=) at /usr/include/c++/8/bits/stl_tree.h:285 #2 HepMC::WeightContainer::pop_back (this=this@entry=0x7ffdd7410790) at WeightContainer.cc:56 #3 0x55e8672df5ab in main () at testWeights.cc:36
Bug#916133: xmlcopyeditor: missing build dependency on pkg-config
Source: xmlcopyeditor Version: 1.2.1.3-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xmlcopyeditor.html ... dh_autoreconf 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:43: error: possibly undefined macro: AC_MSG_RESULT If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:46: error: possibly undefined macro: AC_MSG_ERROR configure.ac:109: error: possibly undefined macro: AC_CHECK_HEADER autoreconf: /usr/bin/autoconf failed with exit status: 1 dh_autoreconf: autoreconf -f -i returned exit code 1 make: *** [debian/rules:25: config-stamp] Error 2
Bug#867548: Available for Additional Testing
I would like to confirm this bug exists on several machines tested with various AMD video card HDMI audio devices in the GCN 1.0 hardware era. Glitches do not appear to be present using onboard Intel HDMI out. I have an Nvidia card I can test if someone needs it, but the issue appears to be AMD specific. Important to note is on the same test machines loaded with kernel firmware directly from kernel.org (as the Debian firmware packages are missing modules): CentOS 7.5 DOES exhibit this same error Ubuntu 16.04 LTS DOES exhibit this same error Ubuntu 18.04 LTS DOES NOT exhibit the same errors, playback is error free. I have four test machines not being used. All HDMI cables and hardware has been confirmed known working good with Ubuntu 18.04 and Windows 10 Pro for glitch free playback. There is something "fixed" in Ubuntu 18.04 LTS. I would be happy to test several hardware configurations to find the root of the problem (pulseaudio, kernel config, kernel compile, driver, etc.) so we can see if this can be patched. I've tried several fixes on various wikis (arch, ubuntu, debian) to no avail. Thanks.
Bug#916134: linux-image-4.18.0-3-amd64: 4.18.0-3 fails to boot, 0-2 works.
Package: src:linux Version: 4.18.20-3 Severity: normal I am unable to boot with 4.18.0-3-amd64 - the grub messages are replaced by a blank screen. I am unable to login, the Caps Lock button does not light up and the laptop is unresponsive to ssh and ping. I am unable to get to any virtual terminal, the only option is to reboot. I tried a variety of systemd debug operations but none made any difference. Note: I also tried rescue mode from the Grub menu but that failed in the same way. I was able to boot 4.18.0-3 to the systemd.unit=emergency.target but I was not able to get to a working system from that login. Switching back to 4.18.0-2 restored all functionality. I tried to reinstall the 4.18.0-3 package but that did not fix the problem. Let me know if there is extra information I can try to provide. -- Package-specific info: ** Kernel log: boot messages should be attached No boot messages are displayed - the screen goes blank and no output is displayed after messages from Grub. ** Model information sys_vendor: LENOVO product_name: 2516CTO product_version: ThinkPad T410 chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: 6IET75WW (1.35 ) board_vendor: LENOVO board_name: 2516CTO board_version: Not Available ** Network interface configuration: auto lo iface lo inet loopback iface eth0 inet dhcp iface wlan0 inet dhcp ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02) Subsystem: Lenovo Core Processor DRAM Controller [17aa:2193] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) Subsystem: Lenovo 5 Series/3400 Series Chipset HECI Controller [17aa:215f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: Intel Corporation 82577LM Gigabit Network Connection [8086:10ea] (rev 06) Subsystem: Lenovo 82577LM Gigabit Network Connection [17aa:2153] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06) (prog-if 20 [EHCI]) Subsystem: Lenovo 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [17aa:2163] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06) Subsystem: Lenovo 5 Series/3400 Series Chipset High Definition Audio [17aa:215e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbor
Bug#916137: opensm: New upstream release (3.3.21)
Package: opensm Version: 3.3.21 Severity: normal Dear Maintainer, there is a new upstream release, which contains important bugfixes, some new features and hardware support aswell. Please consider upgrading. Best Regards Simon Polack
Bug#916136: tomcat8: Changelog-404 for tomcat8 on oldstable
Package: tomcat8 Version: 8.0.14-1+deb8u14 Severity: normal Dear Maintainer, The changelog informations for the tomcat8 package for Debian Jessie (oldstable) seems to be not working anymore. We get 404-Errors if looking at the website (https://metadata.ftp-master.debian.org/changelogs//main/t/tomcat8/tomcat8_8.0.14-1+deb8u14_changelog) as well as looking directly on the server by using the aptitude changelog tomcat8 command (which indirectly requests the same url by wget). Browsing from https://packages.debian.org/de/jessie/tomcat8 you can try it by yourself. For the appropriate Changelog-Links for other Debian Version/Repos (e.g. jessie-backports or stretch) everything works as expected. Kind regards, Stefan Baier -- System Information: Debian Release: 8.11 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-27-pve (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages tomcat8 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56+deb8u1 ii tomcat8-common 8.0.14-1+deb8u14 ii ucf3.0030 Versions of packages tomcat8 recommends: ii authbind 2.1.1 Versions of packages tomcat8 suggests: ii libtcnative-1 1.1.32~repack-2+deb8u2 pn tomcat8-admin pn tomcat8-docs pn tomcat8-examples pn tomcat8-user -- debconf information excluded
Bug#785480: Expanding interest in bcg729
I have just started to update the repo in salsa [0] to the new 1.0.4 upstream version. Help getting the package in shape for inclusion in Debian is appreciated :-) [0] https://salsa.debian.org/pkg-voip-team/bcg729/
Bug#916135: unable to gunzip a symlinked file: Too many levels of symbolic links
Package: gzip Version: 1.9-2.1 Severity: normal File: /bin/gunzip $> rm -rf /tmp/testgz; mkdir /tmp/testgz; cd /tmp/testgz; echo 123 > 123; gzip 123; ln -s 123.gz linked.gz; ls -l; gunzip linked.gz total 4 -rw--- 1 yoh yoh 28 Dec 10 10:47 123.gz lrwxrwxrwx 1 yoh yoh 6 Dec 10 10:47 linked.gz -> 123.gz gzip: skipping: linked.gz is a symbolic link Expected result is to have 123.gz and linked files -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gzip depends on: ii dpkg 1.19.0.5 ii install-info 6.5.0.dfsg.1-2 ii libc6 2.28-2 gzip recommends no packages. Versions of packages gzip suggests: ii less 487-0.1 -- debconf-show failed
Bug#916138: conntrackd: State Accept/Ignore isn't working, always get symbol '}': syntax error. Even "SYNC EXAMPLE 2" from manpage fails.
Package: conntrackd
Version: 1:1.4.4+snapshot20161117-5
Severity: normal
Dear Maintainer,
the block
State Accept {
ESTABLISHED CLOSED TIME_WAIT CLOSE_WAIT
}
is not working and throw a syntax error.
Even the examples in all manuals have this problem.
If I move the block upwards under "filter from userspace/kernelspace" the syntax
error line number get smaller.
[ERROR] parsing config file in line (48), symbol '}': syntax error
If I uncomment the block, the config work.
Thank you in advance, Eike
-- System Information:
Debian Release: 9.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages conntrackd depends on:
ii init-system-helpers 1.48
ii libc6 2.24-11+deb9u3
ii libmnl0 1.0.4-2
ii libnetfilter-conntrack3 1.0.6-2
ii libnetfilter-cthelper0 1.0.0-1
ii libnetfilter-queue1 1.0.2-2
ii libnfnetlink0 1.0.1-3
ii libsystemd0 232-25+deb9u6
conntrackd recommends no packages.
conntrackd suggests no packages.
-- Configuration Files:
/etc/conntrackd/conntrackd.conf changed:
Sync {
Mode NOTRACK {
DisableInternalCache on
DisableExternalCache on
}
TCP {
IPv4_address 192.168.2.100
IPv4_Destination_Address 192.168.2.101
Port 3780
Interface eth2
SndSocketBuffer 1249280
RcvSocketBuffer 1249280
Checksum on
}
Options {
TCPWindowTracking Off
ExpectationSync On
}
}
General {
Systemd on
HashSize 32768
HashLimit 131072
LogFile on
Syslog offconntrackd: State Accept/Ignore isn't working, always get
symbol '}': syntax error. Also "SYNC EXAMPLE 2" from manpage fails.
LockFile /var/lock/conntrack.lock
UNIX {
Path /var/run/conntrackd.ctl
}
NetlinkBufferSize 2097152
NetlinkBufferSizeMaxGrowth 8388608
NetlinkOverrunResync On
NetlinkEventsReliable Off
EventIterationLimit 100
Filter From Userspace {
Protocol Accept {
TCP
SCTP
DCCP
}
Address Ignore {
IPv4_address 127.0.0.1
IPv4_address 192.168.0.0/16
IPv6_address ::1
}
State Accept {
ESTABLISHED CLOSED TIME_WAIT CLOSE_WAIT
}
}
}
-- no debconf information
Bug#916139: trying to overwrite '/usr/lib/cups/filter/hpps', which is also in package hplip 3.17.10+repack0-7
Package: printer-driver-postscript-hp Version: 3.18.12+dfsg0-1 Severity: serious Hi, When upgrading a old VM, I got the following error: Unpacking printer-driver-postscript-hp (3.18.12+dfsg0-1) over (3.17.10+repack0-7) ... dpkg: error processing archive /var/cache/apt/archives/printer-driver-postscript-hp_3.18.12+dfsg0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/cups/filter/hpps', which is also in package hplip 3.17.10+repack0-7 Errors were encountered while processing: /var/cache/apt/archives/printer-driver-postscript-hp_3.18.12+dfsg0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Looks like the Breaks/Replaces against hplip should be bumped. Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages printer-driver-postscript-hp depends on: ii libc6 2.28-2 ii libcups2 2.2.10-1 ii python3 3.7.1-2 ii xz-utils 5.2.2-1.3 printer-driver-postscript-hp recommends no packages. Versions of packages printer-driver-postscript-hp suggests: ii hplip 3.18.12+dfsg0-1 -- no debconf information
Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)
Package: python3-matplotlib-dbg Version: 3.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-matplotlib-dbg_3.0.2-1_amd64.deb ... Unpacking python3-matplotlib-dbg (3.0.2-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-matplotlib-dbg_3.0.2-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/debug/usr/lib/python3/dist-packages/matplotlib/_contour.cpython-36dm-x86_64-linux-gnu.so', which is also in package python-matplotlib-dbg 2.2.3-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-matplotlib-dbg_3.0.2-1_amd64.deb Why is there python3.6 stuff in python-matplotlib-dbg? cheers, Andreas python-matplotlib-dbg=2.2.3-2_python3-matplotlib-dbg=3.0.2-1.log.gz Description: application/gzip
Bug#880393: nmuing cyrus-sasl2
On Sat, 29 Sep 2018 12:23:05 +0200 Helmut Grohne wrote: Control: tags 792851 + pending Control: tags 880393 + pending patch Dear cyrus-sasl2 maintainers, I have prepared a NMU fixing the following bugs: * #792851: FTCBFS This one already had a patch since ages. * #880393: libsasl2-modules-gssapi-heimdal linked against mit krb5 Actually, libgssapiv2.so is built against heimdal correctly. It just happens that the dh_auto_install overwrites the heimdal version with the mit version. Putting the relevant dh_install between the two dh_auto_install fixes the issue. You can find a .debdiff attached. I'll be uploading it to delayed/10 later today. Please let me know if I should delay it any longer. Helmut This problem is causing us serious heartburn. Is there a way to get the corrected stretch .deb file so we can move ahead with our upgrade to stretch? Adam
Bug#916141: deborphan: [INTL:ru] Russian debconf templates translation update
Package: deborphan Version: 1.7.31 Severity: wishlist Tags: l10n patch Russian debconf templates translation update is attached. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ru.po.gz Description: application/gzip
Bug#916142: libpodofo: CVE-2018-5783
Source: libpodofo Version: 0.9.6+dfsg-3 Severity: important Tags: security upstream Forwarded: https://sourceforge.net/p/podofo/tickets/4/ Hi, The following vulnerability was published for libpodofo. CVE-2018-5783[0]: | In PoDoFo 0.9.5, there is an uncontrolled memory allocation in the | PoDoFo::PdfVecObjects::Reserve function (base/PdfVecObjects.h). Remote | attackers could leverage this vulnerability to cause a denial of | service via a crafted pdf file. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-5783 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5783 [1] https://sourceforge.net/p/podofo/tickets/4/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#915136: More info
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've do some more tests on installation, here's the result: kanade:~# gitlab-rake gitlab:git:fsck Check if Gitlab is configured correctly... Performed integrity check for Project/Repo [...] Same message repeated for all repositories The following repositories reported errors: - - SomeGroup/SomeRepo on default: 4:Deadline Exceeded - - Group1/Repo1 on default: 4:Deadline Exceeded <-- This is the repository where i'm working when gitlab fail appears. kanade:~# gitlab-rake gitlab:artifacts:check Check if Gitlab is configured correctly... Checking integrity of Job artifacts Done! kanade:~# gitlab-rake gitlab:lfs:check Check if Gitlab is configured correctly... Checking integrity of LFS objects Done! kanade:~# gitlab-rake gitlab:uploads:check Check if Gitlab is configured correctly... Checking integrity of Uploads - - 1..33: Failures: 0 Done! kanade:~# gitlab-rake gitlab:check Check if Gitlab is configured correctly... Checking GitLab Shell ... GitLab Shell version >= 8.3.3 ? ... OK (8.3.3) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by gitlab:root, or gitlab:gitlab? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... Project / Repo ... ok [...] Same message repeated for all repositories, all OK except empty repositories Running /usr/share/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK Access to /usr/share/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Sidekiq ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Reply by email is disabled in config/gitlab.yml Checking LDAP ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab ... Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... yes Init script up-to-date? ... yes Projects have namespace: ... Project / Repo ... yes [...] Same message repeated for all repositories, all yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.3 ? ... yes (2.5.3) Git version >= 2.9.5 ? ... yes (2.20.0) Git user has default SSH configuration? ... yes Active users: ... 8 Checking GitLab ... Finished kanade:~# gitlab-rake gitlab:env:info Check if Gitlab is configured correctly... System information System: Debian unstable Current User: gitlab Using RVM: no Ruby Version: 2.5.3p105 Gem Version:2.7.6 Bundler Version:1.16.1 Rake Version: 12.3.1 Redis Version: 5.0.2 Git Version:2.20.0. Sidekiq Version:5.2.2 Go Version: unknown GitLab information Version:11.4.9 Revision: Unknown Directory: /usr/share/gitlab DB Adapter: postgresql URL:https://localhost HTTP Clone URL: https://localhost/some-group/some-project.git SSH Clone URL: gitlab@localhost:some-group/some-project.git Using LDAP: no Using Omniauth: no GitLab Shell Version:8.3.3 Repository storage paths: - - default: /home/gitlab/repositories Hooks: /usr/share/gitlab-shell/hooks Git:/usr/bin/git kanade:~# Maybe we need to report the bug to upstream too? I think, probably the bug are debian-specific but they can give us some new information. https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlwOkcoACgkQCU2zE9sy 6H/RIRAAxCGGuQ5Mmh6VrTHQ601GwmikBs24LQr2jXceKseUIP7zbz4xdnmCKBmS qqAXEZQlpacFMBDxeHn77qYxfxP7g43ohsjXAfTkoK1JBkQ2XPbQNIi+lPwNHmjH mvvlNTETVLAgBG9wb5W1cM7j/rZn9Q09mpT9eVqUqT9y2L+/0XhDGoH6uKX3cL+p fhYo/MTn6cp12AIu1/hMWpnLvFanGpLUAGhqBJ12Pte5mvuuoo//7g1Ezg+4WAFH grCyHLdYiJ8RuQC/TaFxka/Oxod3cJzsJkPslOQ1KO+YT4EzY1UeNEotvSpeGFuo jA+KxErt4n3W8srY0t6FZzWtFie/Xx1fnOlB6tVx2OgCJllx00/rl7nntugtbF7c mn87xx3S+oKSwof2nmGIvn+QvMHykfDwXjnSwZmaVdUSxyukXLB14MfbWPZEFA0f xLdIOyR9GK1JjR0ETr5kKiIJNEZyoQiAS5UsSF6WaA339C9xE+ceBhxewM49hnAy lu/CW+FxnIPvuV1WLkVSt9y6b2/D5A7HdLas2WYXPrW5Vx4RVvJ3zNjIxGIIcqhM mnafNKh84JYfFUPSMNZlOsRywOXPy43q94mHrtu3GM0EJ673bsghqX0SDZ8KXjGK desZfuAqQUldVv4ocAULlIFRCC9YSFP3DNzzuN5s2UEftqKwuZg= =BP3W -END PGP SIGNATURE-
Bug#916143: systemd-journal-remote: only installed in /lib/systemd/ not in PATH
Package: systemd-journal-remote Version: 232-25+deb9u6 Severity: important Dear Maintainer, installing systemd-journal-remote with aptitude I'm not finding it as executable in PATH, but only in `/lib/systemd/`. Executing `/lib/systemd/systemd-journal-remote` works as expected. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-journal-remote depends on: ii adduser 3.115 ii libc62.24-11+deb9u3 ii libcurl3-gnutls 7.52.1-5+deb9u8 ii libgnutls30 3.5.8-5+deb9u4 ii libmicrohttpd12 0.9.51-1 ii systemd 232-25+deb9u6 systemd-journal-remote recommends no packages. systemd-journal-remote suggests no packages. -- no debconf information
Bug#916144: autodep8: breaks cdbs packages with substitution variables in Recommends
Package: autodep8
Version: 0.16
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As noted by ntyni on IRC, autodep8 0.16 has issues with (some) cdbs package.
ci.d.n shows dozens of new failures, e.g.
https://ci.debian.net/data/autopkgtest/unstable/amd64/libt/libtest-rdf-perl/1478754/log.gz
which ends with:
badpkg: InvalidControl test /usr/share/pkg-perl-autopkgtest/runner
runtime-deps-and-recommends: Test Depends field contains an invalid dependency
`${cdbs:Recommends}'
autopkgtest [03:56:03]: ERROR: erroneous package: InvalidControl test
/usr/share/pkg-perl-autopkgtest/runner runtime-deps-and-recommends: Test
Depends field contains an invalid dependency `${cdbs:Recommends}'
Or locally, with libtest-rdf-perl:
% autodep8
Test-Command: /usr/share/pkg-perl-autopkgtest/runner build-deps
Depends: @, @builddeps@, pkg-perl-autopkgtest
Features: test-name=autodep8-perl-build-deps
Test-Command: /usr/share/pkg-perl-autopkgtest/runner runtime-deps
Depends: @, pkg-perl-autopkgtest
Features: test-name=autodep8-perl
Test-Command: /usr/share/pkg-perl-autopkgtest/runner runtime-deps-and-recommends
Depends: @, ${cdbs:Recommends}, pkg-perl-autopkgtest
Features: test-name=autodep8-perl-recommends
Note the '${cdbs:Recommends}' which is taken verbatim from the
Recommends in debian/control in the source package.
This probably comes from the new parse_control() function.
I'm not sure how (or if at all) this can be fixed at the source
package level; maybe a @recommends@ which is expanded from the binary
package (in autopkgtest) like @ and @builddeps@ would work better?
(Sorry for missing why this option was not chosen, if this has
already been discussed).
Cheers,
gregor
- -- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages autodep8 depends on:
ii dctrl-tools 2.24-3
ii python3 3.7.1-2
autodep8 recommends no packages.
autodep8 suggests no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlwOk/1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaY4Q//bZT5wGYWcbfG7S6KBo5p0rvxpU6r55R8RskMNhq8W6sVWikKeEFLUwvg
OTDgLDI5uOsBD7pc5gbDq7kCrILLbWehVI1l7opeZcjLjjXfeARBTtFstSuYGKyS
Ixj6b5bXN6mL38bgDVL97t+dZ8qUkUrDpPUVRQo0wvP/bgo74/M59Qf7P8Bb9Dfo
//9CEtOzx2mMmRUCsyxdrYSI2AIYxqZZyfCUc0FrzeOYS16Dz7cBzjJ5SvukXn0H
ZfmrRsZl+9zutl9MiZ+B+XPPQJ5EiZ3GEMr2GEX5tQn4p5etayeiN9eI0lIldp3I
YUg2CNxabtdldGin2TIHzRVPCm/GuXrznznNfvYwfY/dzLk3mm2q7Ye8+uXjatnZ
oEZKX/QbDabUJvtVUGVS04oAv8luHI5rlx2ZuMsCM37NughuFGn2fflaMVhVQ/Br
bFaWhB5teJM7JIw/HuauBRPQ2FiAM1QMcX24RiiPEFVL85UY5smTyFjiW10XqWjh
oVV/DW8Vza1LUWY++F9GzMVMyraYPparTlmSxHxG19+nr0WRUr8Xl2XG+/xH9mUs
C9upbVYp5fA4Qv2y6C6hOmDvaMBAHxzWBT1b4yWx1SWAVgDouJmxJBHH1x+mJ9zW
cC11UYl9chL6aWNkNw3atqwkKyRyiUJUAvEh5teSZUnSqkV3M04=
=L2dc
-END PGP SIGNATURE-
Bug#916135: unable to gunzip a symlinked file: Too many levels of symbolic links
Yaroslav Halchenko wrote: > Package: gzip > Version: 1.9-2.1 > Severity: normal > File: /bin/gunzip > > $> rm -rf /tmp/testgz; mkdir /tmp/testgz; cd /tmp/testgz; echo 123 > 123; > gzip 123; ln -s 123.gz linked.gz; ls -l; gunzip linked.gz > total 4 > -rw--- 1 yoh yoh 28 Dec 10 10:47 123.gz > lrwxrwxrwx 1 yoh yoh 6 Dec 10 10:47 linked.gz -> 123.gz > gzip: skipping: linked.gz is a symbolic link > > Expected result is to have 123.gz and linked files I think you forgot to show how to get the ELOOP message.. -- see shy jo signature.asc Description: PGP signature
Bug#913550: shared-mime-info: Don't assume every *.key file is an Apple Keynote file
Chris Lamb wrote: > A Tails user's OpenPGP armored public key (e.g. exported with "gpg -- > armor --export $KEY_ID" is incorrectly recognised as "application/x- > iwork-keynote-sffkey": […] > Therefore I am requesting you apply this to the local Debian > packaging in time for buster. Many thanks in advance. Gentle ping on this? Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#916145: closure-compiler: Not working with recent JS code
Package: closure-compiler Version: 20130227+dfsg1-9 Severity: important Dear Maintainer, the current version is so old that it got incompatible with recent JS code. E.g. jQuery 3.3.1 cannot be minified as the tool reports parsing errors. Please either update the tool or remove it from the archive. This is now 5 years in unmaintained state. -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages closure-compiler depends on: ii default-jre-headless [java6-runtime-headless]2:1.8-58 ii java-wrappers0.1.28 ii libclosure-compiler-java 20130227+dfsg1-9 ii openjdk-8-jre-headless [java6-runtime-headless] 8u181-b13-2~deb9u1 ii oracle-java8-jdk [java6-runtime-headless]8u77 closure-compiler recommends no packages. closure-compiler suggests no packages. -- no debconf information
Bug#915696: [Pkg-alsa-devel] Bug#915696: Pulseaudio should ship /etc/alsa/conf.d/pulse.conf instead of /usr/share/alsa/alsa.conf.d/pulse.conf
Hi, On Sat, Dec 8, 2018, 10:53 Elimar Riesebieter * Felipe Sateler [2018-12-06 12:13 -0300]: > > > Control: affects -1 libasound2-plugins > > > > Including the Alsa maintainers in the loop, as this may be really a > > bug on their side. > > > > On Thu, Dec 6, 2018 at 3:51 AM Zhong Jianxin wrote: > > > > > > Package: pulseaudio > > > Version: 12.2-2 > > > Severity: important > > > > > > Due to alsa-plugins upstream change here[1], after libasound2-plugins > > > 1.1.7, files in /usr/share/alsa/alsa.conf.d no longer load by default > > > > This looks borked. Why did they remove this? There is no rationale in > > the commit message. > > > > Alsa maintainers, would you consider this a bug in alsa plugins? I > > would think so, but unfortunately > > the bug tracker link in the upstream site is dead. Where would I report > that? > > Since libasound2-plugins 1.1.7-2 the files from alsa-plugins source > in /usr/share/alsa/alsa.conf.d/ are linked to /etc/alsa/conf.d. > pulse.conf should be linked by pulsausdio which installs that file. > > Did I misunderstood something? > Yes, sorry for not including the full context. The proximate problem is that pulseaudio also ships files in /usr/share/alsa/alsa.conf.d, and was thus broken by the change in alsa. However, I question whether that was a good idea at all: users don't usually need to modify these files, and making me ship the files in /etc is a bad idea, because then they would be left after remove.
Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)
On Mon, Dec 10, 2018 at 11:06 AM Andreas Beckmann wrote: > > Package: python3-matplotlib-dbg > Version: 3.0.2-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. > It installed fine in 'sid', then the upgrade to 'experimental' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. is this right approach? there is a new src:matplotlib2 in experimetal NEW to drop py3k packages (so src:matplotlib2 will only ship python2 and src:matplotlib will only ship py3k package), so that should remove the incompatibility? > Why is there python3.6 stuff in python-matplotlib-dbg? no idea, it looks like it's like that even on stretch! sigh -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#915642: AuthBasicProvider PAM crashes apache
Dear Maintainer,
I just tried to reproduce and found it crash on service startup when
using the given /etc/apache2/sites-enabled/default.conf.
It looks like here the apache2 process wants to fork and calls the
fork_handlers. Unfortunately one of them belongs to an unloaded module.
Therefore we end up trying to execute unmapped memory.
>From the similar offset I would expect that the first fork_handler belong
to function deinit from libcap-ng.so.0.
The first one 0x7f50c8e0e660 points to the current location of libcap-ng.so.0.
But the second 0x7f50c8e12660 looks like pointing to an unloaded location of
libcap-ng.so.0.
This situation looks quite similar to what I tried to collect in bug #914565.
And now that I looked up the bugs for libcap-ng0 this one seems related:
#904808.
Kind regards,
Bernhard
#914565 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914565
#904808 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808
(gdb) bt
#0 0x7f50c8e12660 in ?? ()
#1 0x7f50c921470e in __libc_fork () at ../sysdeps/nptl/fork.c:204
#2 0x7f50c9357875 in apr_proc_detach (daemonize=daemonize@entry=1) at
./threadproc/unix/procsup.c:31
#3 0x7f50c8b93fc5 in event_pre_config (pconf=0x7f50c90b8028,
plog=0x7f50c908c028, ptemp=) at event.c:3416
#4 0x55e968fd81be in ap_run_pre_config (pconf=0x7f50c90b8028,
plog=0x7f50c908c028, ptemp=0x7f50c9090028) at config.c:89
#5 0x55e968fb3e5f in main (argc=, argv=) at
main.c:775
(gdb) up
#2 0x7f50c9357875 in apr_proc_detach (daemonize=daemonize@entry=1) at
./threadproc/unix/procsup.c:31
31 if ((x = fork()) > 0) {
(gdb) print *__fork_handlers
$1 = {next = 0x7f50c9309998 , prepare_handler = 0x0,
parent_handler = 0x0, child_handler = 0x7f50c8e0e660 , dso_handle =
0x7f50c93282a0, refcntr = 2, need_signal = 0}
(gdb) print *__fork_handlers->next
$2 = {next = 0x7f50c9309968 , prepare_handler = 0x0,
parent_handler = 0x0, child_handler = 0x7f50c8e12660, dso_handle =
0x7f50c93282a0, refcntr = 2, need_signal = 0}
(gdb) print *__fork_handlers->next->next
$3 = {next = 0x0, prepare_handler = 0x0, parent_handler = 0x0, child_handler =
0x7f50c93133d0 <__reclaim_stacks>, dso_handle = 0x0, refcntr = 1, need_signal =
0}
(gdb) info share
>FromTo Syms Read Shared Object Library
...
0x7f50c8e0e560 0x7f50c8e10419 Yes
/lib/x86_64-linux-gnu/libcap-ng.so.0
...
Bug#846077: sudo: compile sudo with zlib support
sudo 1.8.19p1-2.1 still seems to be built without zlib support. Any chance this could be added to either sudo or sudo-ldap? sudo-ldap probably won't even pull in any new dependencies because it already pulls in zlib1g via libgnutls30 via libldap-2.4-2. Florian signature.asc Description: PGP signature
Bug#914565: php7.3-intl: Segfaults after apache2 graceful restart
While looking into #915642 I found that this bug might just be another case of bug #904808. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808 Kind regards, Bernhard
