Bug#858882: r-cran-rcppgsl: Missing dependency libgsl-dev
Hi Dirk, did you do any means that the issue will also be fixed in testing? Kind regards Andreas. On Tue, Mar 28, 2017 at 03:09:31PM +0200, Andreas Tille wrote: > > > > | Uploads to testing-proposed-updates are working fine. > > > > I could re-upload. > > I'm not sure what you mean with "re-upload" but under the current > circumstances the bug in testing affecting r-cran-rcppgsl/0.3.1-1 > remains and needs to be fixed by coordination with release team. > > Kind regards > > Andreas. -- http://fam-tille.de
Bug#859310: xserver-xorg-video-nvidia-legacy-304xx: Failed to load module nvidia (module does not exist, 0) No drivers available.
Package: xserver-xorg-video-nvidia-legacy-304xx Version: 304.135-2 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, * What led up to the situation? All the components of the nvidia-legacy-304xx drivers (kernel and xorg) were working fine in jessie. After an upgrade to stretch, the nouveau driver was unreliable (video artifacts, lock-ups) as it had been before in jessie. I had to manually remove packages, blacklist nouveau, install and compile the kernel driver, etc... After all was done X wouldn't start. These are the relevant lines in Xorg.0.log.old before the fix below: [28.868] (II) LoadModule: "nvidia" [28.907] (WW) Warning, couldn't open module nvidia [28.907] (II) UnloadModule: "nvidia" [28.907] (II) Unloading nvidia [28.907] (EE) Failed to load module "nvidia" (module does not exist, 0) [28.907] (EE) No drivers available. [28.907] (EE) Fatal server error: [28.907] (EE) no screens found(EE) * What exactly did you do that was effective? It appears that the kernel driver packages and the xorg driver packages don't agree as to the location of the nvidia_drv.so file. Creating this symbolic link fixes the problem. ln -s /usr/lib/nvidia/legacy-304xx/nvidia_drv.so /usr/lib/xorg/modules/drivers/nvidia_drv.so * What was the outcome of this action? The X server started correctly. After that it was only a matter of setting it up with nvidia-settings. All the information below was collected by reportbug after the symbolic link above was set up and the system rebooted. The Xorg.0.log.old (also below) reflects the problem and contains the few lines included above. -- Package-specific info: uname -a: Linux graviton 4.9.0-2-686-pae #1 SMP Debian 4.9.13-1 (2017-02-27) i686 GNU/Linux /proc/version: Linux version 4.9.0-2-686-pae (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170221 (Debian 6.3.0-8) ) #1 SMP Debian 4.9.13-1 (2017-02-27) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.135 Tue Jan 17 14:54:17 PST 2017 GCC version: gcc version 6.3.0 20170321 (Debian 6.3.0-11) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV41 [GeForce 6800] [10de:00c1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation NV41 [GeForce 6800] [10de:0245] 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: nvidia Kernel modules: nouveau, nvidia_legacy_304xx dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Apr 1 19:55 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Apr 1 19:55 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Apr 1 19:55 /dev/nvidiactl video:x:44:afc,motion OpenGL and NVIDIA library files installed: -rw-r--r-- 1 afc afc 1248 Apr 1 16:50 /etc/X11/xorg.conf lrwxrwxrwx 1 root root 22 Mar 28 22:30 /etc/alternatives/glx -> /usr/lib/mesa-diverted lrwxrwxrwx 1 root root 49 Mar 28 22:30 /etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1 lrwxrwxrwx 1 root root 48 Mar 28 22:30 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 48 Mar 28 22:30 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 52 Mar 28 22:30 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 52 Mar 28 22:30 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 28 Apr 1 15:44 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-304xx lrwxrwxrwx 1 root root 54 Apr 1 15:44 /etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 54 Apr 1 15:44 /etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 62 Apr 1 15:44 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 70 Apr 1 15:44 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 38 Apr 1 15:44 /etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/legacy-304xx/libglx.so lrwxrwxrwx 1 root root 62 Apr 1 15:44 /etc/alternatives/nvidia--libnvidia-cfg.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 61 Apr 1 15:44
Bug#848345: marked as done (hard codes dependency on library package libosl1)
Your message dated Sat, 01 Apr 2017 23:38:56 + with message-idand subject line Bug#848345: fixed in gpsshogi 0.7.0-1.1 has caused the Debian Bug report #848345, regarding hard codes dependency on library package libosl1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 848345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpsshogi Version: 0.7.0 Severity: serious Gpsshogi 9.7.0 can not be freshly installed because it depends on libosl1 (>= 0.6.0) which is not installable but is replaced by libosl1v5:i386 libosl1v5 which is already installed --- System information. --- Architecture: Kernel: Linux 4.8.0-2-amd64 Debian Release: stretch/sid 500 unstablepackages.siduction.org 500 unstable ftp2.de.debian.org 500 stable repo.vivaldi.com 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed ===-+-= libboost-date-time1.58.0| 1.58.0+dfsg-5.1 libboost-filesystem1.58.0 | 1.58.0+dfsg-5.1 libboost-program-options1.58.0 | 1.58.0+dfsg-5.1 libboost-system1.58.0 | 1.58.0+dfsg-5.1 libboost-thread1.58.0 | 1.58.0+dfsg-5.1 libc6 (>= 2.14) | libgcc1 (>= 1:3.0) | libgsl2 | libosl1v5 | libpocofoundation9v5| libpoconet9v5 | libqt4-network (>= 4:4.5.3) | libqt4-qt3support (>= 4:4.5.3) | libqtcore4 (>= 4:4.8.0) | libqtgui4 (>= 4:4.8.0) | libreadline6 (>= 6.0) | libstdc++6 (>= 5.2) | libtcmalloc-minimal4| gpsshogi-data (= 0.6.0-3+nmu2) | Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Source: gpsshogi Source-Version: 0.7.0-1.1 We believe that the bug you reported is fixed in the latest version of gpsshogi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 848...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated gpsshogi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 31 Mar 2017 00:57:08 +0200 Source: gpsshogi Binary: gpsshogi gpsshogi-data Architecture: source Version: 0.7.0-1.1 Distribution: unstable Urgency: medium Maintainer: Daigo Moriwaki Changed-By: Mattia Rizzolo Description: gpsshogi - Shogi playing program based on OpenShogiLib gpsshogi-data - data files for gpsshogi Closes: 848345 Changes: gpsshogi (0.7.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Import back again un-incorporated NMU 0.6.0-3+nmu2. Closes: 848345 * Use HTTPS in Vcs-* headers. * Apply change in git reposiotry from Daigo Moriwaki: specify QT_SELECT=qt5 and add a patch to build with qt5. Checksums-Sha1: 62eee395239cdf1643c5fb43cf30007b829844bf 2177 gpsshogi_0.7.0-1.1.dsc d22a5381cc6cb5e505d419fe7d4f42ea7fd37b1f 11488 gpsshogi_0.7.0-1.1.debian.tar.xz Checksums-Sha256: d8394219b52eca5de47396807312225d2c7b756d51748570a843c3054daa2175 2177 gpsshogi_0.7.0-1.1.dsc 5c51ffa6f55770da9b0d3b7ff38e2ceb55177919dbf5d734075e00522164cc4a 11488 gpsshogi_0.7.0-1.1.debian.tar.xz Files: 3b0208c330a6f2cb6f72c98cc6a4b023 2177 games optional gpsshogi_0.7.0-1.1.dsc 6696a46f78decd8c62c87aff8bde5123 11488 games optional gpsshogi_0.7.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAljdkUAACgkQCBa54Yx2
Bug#795237: marked as done (hard codes dependency on library package libosl1)
Your message dated Sat, 01 Apr 2017 23:38:56 + with message-idand subject line Bug#848345: fixed in gpsshogi 0.7.0-1.1 has caused the Debian Bug report #848345, regarding hard codes dependency on library package libosl1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 848345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpsshogi Severity: serious Version: 0.6.0-3+nmu1 gpsshogi FTBFS in current sid: | gpsusi.cc:906:48: warning: ignoring return value of 'FILE* freopen(const char*, const char*, FILE*)', declared with attribute warn_unused_result [-Wunused-result] | freopen(error_log_file.c_str(), "w", stderr); | ^ | g++ -Wl,--as-needed `dpkg-buildflags --get LDFLAGS` gpsshogi.o -lboost_thread -lboost_program_options -lpthread -losl -lboost_date_time -lboost_filesystem -lboost_serialization -lboost_iostreams -lboost_system -ltcmalloc_minimal -o gpssho | gi | /usr/bin/ld: warning: libboost_program_options.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_program_options.so.1.58.0 | /usr/bin/ld: warning: libboost_filesystem.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_filesystem.so.1.58.0 | /usr/bin/ld: warning: libboost_serialization.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_serialization.so.1.58.0 | /usr/bin/ld: warning: libboost_iostreams.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_iostreams.so.1.58.0 | /usr/bin/ld: warning: libboost_system.so.1.55.0, needed by /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so, may conflict with libboost_system.so.1.58.0 | gpsshogi.o: In function `makeWeightedBook()': | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string const&)' | gpsshogi.o: In function `benchmark(osl::game_playing::SearchPlayer&, std::__cxx11::basic_string const&, int)': | /«PKGBUILDDIR»/bin/benchmark.h:37: undefined reference to `osl::record::csa::CsaFile::CsaFile(std::__cxx11::basic_string const&)' | /«PKGBUILDDIR»/bin/benchmark.h:47: undefined reference to `osl::record::csa::show[abi:cxx11](osl::Move)' | /«PKGBUILDDIR»/bin/benchmark.h:58: undefined reference to `osl::record::csa::show[abi:cxx11](osl::Move)' | gpsshogi.o: In function `play(int, char**)': | /«PKGBUILDDIR»/bin/gpsshogi.cc:153: undefined reference to `osl::OslConfig::configuration[abi:cxx11]()' | /«PKGBUILDDIR»/bin/gpsshogi.cc:266: undefined reference to `osl::record::csa::CsaFile::CsaFile(std::__cxx11::basic_string const&)' | gpsshogi.o: In function `makeWeightedBook()': | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string const&)' | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string const&)' | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string const&)' | /«PKGBUILDDIR»/bin/gpsshogi.cc:53: undefined reference to `osl::OslConfig::openingBook(std::__cxx11::basic_string const&)' | gpsshogi.o: In function `OpeningOptions::OpeningOptions()': | /«PKGBUILDDIR»/bin/options.h:141: undefined reference to `osl::OslConfig::home(std::__cxx11::basic_string const&)' | /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libosl.so: undefined reference to `boost::gregorian::greg_month::get_month_map_ptr()' | collect2: error: ld returned 1 exit status Full build log attached for convenience. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) gpsshogi_0.6.0-3+nmu1_amd64-20150812-0859.build.gz Description: application/gzip signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: gpsshogi Source-Version: 0.7.0-1.1 We believe that the bug you
Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch
Hi! [ Sorry for taking so much time to dig into this. Reproducing, checking and diagnosing trigger issues imply usually spending significant amounts of time on it, which I didn't have back then, and it's a bit of a drag to be the "support channel" for trigger issues too. :) Anyway, thanks go to Niels, who by looking into this, prompted me to do the same. ;) ] On Wed, 2017-02-08 at 11:42:29 +0100, Andreas Beckmann wrote: > Package: dpkg > Version: 1.18.18 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + libcrypt-cracklib-perl > I just noticed this trigger related problem during a piuparts upgrade > test of libcrypt-cracklib-perl from jessie to stretch. I can reproduce > it on both amd64 and i386, but it requires --install-recommends to show > up. If you need more debug info, I can now easily rerun the failed tests > and enter the chroot after the failure to collect more info. > > >From the attached log (scroll to the bottom...): > > [...] > Preparing to unpack .../archives/bash_4.4-4_i386.deb ... > Unpacking bash (4.4-4) over (4.3-11+deb8u1) ... > dpkg: dependency problems prevent processing triggers for cracklib-runtime: >cracklib-runtime depends on libcrack2 (>= 2.9.2-1); however: > Package libcrack2:i386 is not configured yet. […] > dpkg: too many errors, stopping > Errors were encountered while processing: >cracklib-runtime […] >cracklib-runtime > Processing wE: Sub-process /usr/bin/dpkg returned an error code (1) I think this is an issue with apt explicitly asking dpkg to configure only cracklib-runtime when its dependencies are not satisfied because they are awaiting on trigger processing, and apt is not asking for those other packages to be configured too. So dpkg cannot fulfill the request. I think a simple reproducer on a clean chroot, is to: $ cd /var/cache/apt/archives $ apt-get install --install-recommends libcrypt-cracklib-perl $ dpkg --unpack libcrack2_*.deb $ dpkg --install wamerican_*.deb $ dpkg --configure cracklib-runtime My expectation is that after the reported state is found on piuparts, running: $ dpkg --configure --pending or even something like: $ dpkg --configure cracklib-runtime libcrack2 would let dpkg configure that package correctly w/o complaining about the unsatisfiable dependency. Andreas, is that indeed the case? If it is then this needs to be reassigned to apt. Thanks, Guillem
Bug#858219: marked as done (barbican-api: Missing dependency to net-tools)
Your message dated Sat, 01 Apr 2017 23:34:06 + with message-idand subject line Bug#858219: fixed in barbican 1:3.0.0-3 has caused the Debian Bug report #858219, regarding barbican-api: Missing dependency to net-tools to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: barbican-api Severity: normal Dear Maintainer, config script uses pkgos_register_endpoint_config() of pkgos, which itself uses /sbin/route , which is part of net-tools. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (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: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: barbican Source-Version: 1:3.0.0-3 We believe that the bug you reported is fixed in the latest version of barbican, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 858...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Rabel (supplier of updated barbican package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Apr 2017 11:18:11 +0200 Source: barbican Binary: python-barbican barbican-common barbican-api barbican-worker barbican-keystone-listener barbican-doc Architecture: source all Version: 1:3.0.0-3 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack Changed-By: David Rabel Description: barbican-api - OpenStack Key Management Service - API Server barbican-common - OpenStack Key Management Service - common files barbican-doc - OpenStack Key Management Service - doc barbican-keystone-listener - OpenStack Key Management Service - Keystone Listener barbican-worker - OpenStack Key Management Service - Worker Node python-barbican - OpenStack Key Management Service - Python files Closes: 858219 Changes: barbican (1:3.0.0-3) unstable; urgency=medium . * Team upload. * Revert net-tools dependency. * Bump build dependency on openstack-pkg-tools (Closes: #858219). Checksums-Sha1: 3a04915e130a95889b70682391c1f7da6fbcaa81 3597 barbican_3.0.0-3.dsc 7793a0aef26e741579410c3ddaa2674856ec 17848 barbican_3.0.0-3.debian.tar.xz f50bb95809d7831f953ddf22add03fb0c2d18f22 25662 barbican-api_3.0.0-3_all.deb 764de078843b8ca3085a9204a1c8a1a067db252a 31664 barbican-common_3.0.0-3_all.deb d6b9a8b4543db059614a3f5a1884ade6fa0a47ac 207630 barbican-doc_3.0.0-3_all.deb 4ba3f84921282bfec29feac7bfd69f8bc3cec90f 7190 barbican-keystone-listener_3.0.0-3_all.deb fce422f692dbd4029e369db9acd31c45d476606a 7180 barbican-worker_3.0.0-3_all.deb 59f94cdf6b7537b475dbc5aff8330294a5f1adcc 14944 barbican_3.0.0-3_amd64.buildinfo 731ac864ff313b91b3c0722f42b65a9ed60becef 249910 python-barbican_3.0.0-3_all.deb Checksums-Sha256: 11fc3e934f323b4eeb17d0b7d059e6ae270fb67b8f422aaecf74986d781f366a 3597 barbican_3.0.0-3.dsc 917d7e0d1375f64f296c70a13243d590fded439ea33247dc08980d0459955e67 17848 barbican_3.0.0-3.debian.tar.xz 6088c88c1386c4487a44e13b99b9a96dc5998ce1bb5499c5d85776432e331b95 25662 barbican-api_3.0.0-3_all.deb 87b17b801f3cbb7ce935be01765e47b8f34a6d587caeb3ec341a9aa3f2029ead 31664 barbican-common_3.0.0-3_all.deb 16f21f18c272e611ab85b52c1857b763a361aab8b33669c0dd0700419b24af14 207630 barbican-doc_3.0.0-3_all.deb eaf88b8f63b2bff20fe491f7111f9dc980501a8ef673e256100fb7d998d4ca45 7190 barbican-keystone-listener_3.0.0-3_all.deb 0877ee284e7248a694851ae0c337e40278fca3e4c48f69f87b6929ab898a76d1 7180 barbican-worker_3.0.0-3_all.deb 36c398a5699dbf7107eb5f1c93cfb0b357813b5c0a707fc5463fa5e46e7b8c48 14944 barbican_3.0.0-3_amd64.buildinfo 5578fb7027573764ad9895923fc8fa91c80880bb4f3cdff233e6f57bb2523776 249910 python-barbican_3.0.0-3_all.deb Files: 67d5ca8651ffe84cbc0bbe9964c444a4 3597 net extra barbican_3.0.0-3.dsc
Bug#859308: please fix that !
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859309#10 now i cannot report!?!? use report bug! and report bug are broken!? WTH? WTF? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#859309: closed by Michael Biebl <bi...@debian.org> (Re: [Pkg-utopia-maintainers] Bug#859309: network manager broken after using light slim or ldm, complicated with simple packages such slim)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859308 FUCK*** REPORT BUG ITS BROKEN AFTER SOME INSTALL WHAT THE HELLL! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-04-01 19:21 GMT-04:00 Debian Bug Tracking System: > This is an automatic notification regarding your Bug report > which was filed against the network-manager package: > > #859309: network manager broken after using light slim or ldm, complicated > with simple packages such slim > > It has been closed by Michael Biebl . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Biebl > by > replying to this email. > > > -- > 859309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859309 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Mensaje reenviado -- > From: Michael Biebl > To: PICCORO McKAY Lenz , 859309-d...@bugs.debian.org > Cc: > Bcc: > Date: Sun, 2 Apr 2017 01:17:32 +0200 > Subject: Re: [Pkg-utopia-maintainers] Bug#859309: network manager broken > after using light slim or ldm, complicated with simple packages such slim > Please use reportbug to file the bug report. > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > > > -- Mensaje reenviado -- > From: PICCORO McKAY Lenz > To: Debian Bug Tracking System > Cc: > Bcc: > Date: Sat, 1 Apr 2017 19:12:34 -0400 > Subject: network manager broken after using light slim or ldm, complicated > with simple packages such slim > Package: network-manager > Version: 0.9.10.0 > Severity: grave > > Disclaimer: seem was reporte before, market as solved but persist! > > After updating some packages from backports (including changing some > gtk3 engines) > Selecting in the Wifi-Connection the desired connection leads to: > > Failed to add/activate connection > (32) No session found for uid 1000 (unknown) > > aint able to choose a connection, now network manager its the ower of my > desktop > > slim are 1.3.6-4 with the pam support and libpam-systemd is installed > (204-8). > > obviously in this case systemctl does not show any due no operation > was performed > > i reported this agains network manager due all of thoer programs > works, neither n-m, after using slim.. > > all my desktop penbox, lxdm and mate works using slim except the > network manager related packages > > > > systemas@venenux10:~$ nm-applet > > (nm-applet:28979): nm-applet-WARNING **: Failed to register as an > agent: (32) Session not found > > (nm-applet:28979): nm-applet-WARNING **: Falló al añadir/activar la > conexión: (32) No session found for uid 1000 (unknown) > Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. > > > > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com >
Bug#859309: marked as done (network manager broken after using light slim or ldm, complicated with simple packages such slim)
Your message dated Sun, 2 Apr 2017 01:17:32 +0200 with message-id <509e9fe7-af90-1bf8-291c-8f3eff934...@debian.org> and subject line Re: [Pkg-utopia-maintainers] Bug#859309: network manager broken after using light slim or ldm, complicated with simple packages such slim has caused the Debian Bug report #859309, regarding network manager broken after using light slim or ldm, complicated with simple packages such slim to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 859309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: network-manager Version: 0.9.10.0 Severity: grave Disclaimer: seem was reporte before, market as solved but persist! After updating some packages from backports (including changing some gtk3 engines) Selecting in the Wifi-Connection the desired connection leads to: Failed to add/activate connection (32) No session found for uid 1000 (unknown) aint able to choose a connection, now network manager its the ower of my desktop slim are 1.3.6-4 with the pam support and libpam-systemd is installed (204-8). obviously in this case systemctl does not show any due no operation was performed i reported this agains network manager due all of thoer programs works, neither n-m, after using slim.. all my desktop penbox, lxdm and mate works using slim except the network manager related packages systemas@venenux10:~$ nm-applet (nm-applet:28979): nm-applet-WARNING **: Failed to register as an agent: (32) Session not found (nm-applet:28979): nm-applet-WARNING **: Falló al añadir/activar la conexión: (32) No session found for uid 1000 (unknown) Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com --- End Message --- --- Begin Message --- Please use reportbug to file the bug report. -- 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 --- End Message ---
Bug#858215: marked as done (aodh-api: Missing dependency to net-tools)
Your message dated Sat, 01 Apr 2017 23:19:02 + with message-idand subject line Bug#858215: fixed in aodh 3.0.0-4 has caused the Debian Bug report #858215, regarding aodh-api: Missing dependency to net-tools to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: aodh-api Version: 3.0.0-2 Severity: normal Dear Maintainer, config script uses pkgos_register_endpoint_config() of pkgos, which itself uses /sbin/route , which is part of net-tools. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (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: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: aodh Source-Version: 3.0.0-4 We believe that the bug you reported is fixed in the latest version of aodh, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 858...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Rabel (supplier of updated aodh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Apr 2017 11:11:56 +0200 Source: aodh Binary: python-aodh aodh-common aodh-api aodh-evaluator aodh-notifier aodh-listener aodh-expirer aodh-doc Architecture: source all Version: 3.0.0-4 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack Changed-By: David Rabel Description: aodh-api - OpenStack Telemetry (Ceilometer) Alarming - API server aodh-common - OpenStack Telemetry (Ceilometer) Alarming - common files aodh-doc - OpenStack efficient metering counters system - doc aodh-evaluator - OpenStack Telemetry (Ceilometer) Alarming - alarm evaluator aodh-expirer - OpenStack Telemetry (Ceilometer) Alarming - expirer aodh-listener - OpenStack Telemetry (Ceilometer) Alarming - listener aodh-notifier - OpenStack Telemetry (Ceilometer) Alarming - alarm notifier python-aodh - OpenStack Telemetry (Ceilometer) Alarming - Python libraries Closes: 858215 Changes: aodh (3.0.0-4) unstable; urgency=medium . * Team upload. * Revert net-tools dependency. * Bump build dependency on openstack-pkg-tools (Closes: #858215). Checksums-Sha1: 69c7d9aa37b1e88e9b35bd2786339c08c05f890c 3797 aodh_3.0.0-4.dsc 311fb1afd06ea67ab105bb0229f70fcb38762e1c 25872 aodh_3.0.0-4.debian.tar.xz e75d8053efce1b8001344563af66fb85a0a4cf95 27980 aodh-api_3.0.0-4_all.deb d5916d4f6ef96760a30b4c2e10933573fb65dcae 37228 aodh-common_3.0.0-4_all.deb f9f05a295be34a4b0ee4f91376b962f43838eb9c 82510 aodh-doc_3.0.0-4_all.deb 3d091e7987964582aa70e4fadbe9830f3181b64d 6766 aodh-evaluator_3.0.0-4_all.deb c993c092d005b48343123afb055ff2207d8bb28d 6818 aodh-expirer_3.0.0-4_all.deb f032fe529ee71c2e503a536bc8ecb41753d4c899 6780 aodh-listener_3.0.0-4_all.deb c06109ad3984ccc392cf0a16d9f23afb036d52b4 6762 aodh-notifier_3.0.0-4_all.deb e603d951554eeb1d2fd3d6607324d2295501f56d 16810 aodh_3.0.0-4_amd64.buildinfo dc97661cef83eb0de4d20372e8cbd6e40e4b4d4f 111724 python-aodh_3.0.0-4_all.deb Checksums-Sha256: ec0b615f8a8046dc2d743b18ccc8b6eda85462da65eda9df52bc29b987c5 3797 aodh_3.0.0-4.dsc 43a224fe6e7112b1b47e50f720092ed4f27fa5021e5cd94a6e26d5fca8776a46 25872 aodh_3.0.0-4.debian.tar.xz c43703650def210e2385e90a3040b7a3d54104dabbb623eb4c7c651dbd8a3c09 27980 aodh-api_3.0.0-4_all.deb 6fbb6c64bd25a396d345027cdb6f5ac20845f14b0f64d4736182956679666888 37228 aodh-common_3.0.0-4_all.deb 46355dc73d82868c7480e9733535dda28d8f13527d1160289b75038f2dbe8676 82510 aodh-doc_3.0.0-4_all.deb 625242f522dc610046fa7ddbf8ce1ff73d4848c2950475fa66c44a6ddd1b4e50 6766 aodh-evaluator_3.0.0-4_all.deb d84aee7c2d99d4122c0256ebb5ef87a247d0675f80d935295629ece91bd5a60c 6818 aodh-expirer_3.0.0-4_all.deb 3ceedd72e486d3f5671493c2a1afbcb2efb0574cf5234a37b69daa630c0e8c38 6780
Bug#859309: network manager broken after using light slim or ldm, complicated with simple packages such slim
Package: network-manager Version: 0.9.10.0 Severity: grave Disclaimer: seem was reporte before, market as solved but persist! After updating some packages from backports (including changing some gtk3 engines) Selecting in the Wifi-Connection the desired connection leads to: Failed to add/activate connection (32) No session found for uid 1000 (unknown) aint able to choose a connection, now network manager its the ower of my desktop slim are 1.3.6-4 with the pam support and libpam-systemd is installed (204-8). obviously in this case systemctl does not show any due no operation was performed i reported this agains network manager due all of thoer programs works, neither n-m, after using slim.. all my desktop penbox, lxdm and mate works using slim except the network manager related packages systemas@venenux10:~$ nm-applet (nm-applet:28979): nm-applet-WARNING **: Failed to register as an agent: (32) Session not found (nm-applet:28979): nm-applet-WARNING **: Falló al añadir/activar la conexión: (32) No session found for uid 1000 (unknown) Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#859308: reportbug breaks after install some backporte packs
Package: reportbug Version: 6.6.3 Severity: grave firts of all, the stupid report bug are broken so dont say "this was not made using report bug" i'm pn console and report bug web page dont work either this its the backtrace using pipes: Querying Debian BTS for reports on reportbug (source)... Traceback (most recent call last): File "/usr/bin/reportbug", line 2211, in main() File "/usr/bin/reportbug", line 1081, in main return iface.user_interface() File "/usr/bin/reportbug", line 1703, in user_interface latest_first=self.options.latest_first) File "/usr/lib/python2.7/dist-packages/reportbug/ui/text_ui.py", line 517, in handle_bts_query source=source, http_proxy=http_proxy, archived=archived) File "/usr/lib/python2.7/dist-packages/reportbug/debbugs.py", line 1275, in get_reports stats = debianbts.get_status(bugs) File "/usr/lib/pymodules/python2.7/debianbts.py", line 188, in get_status bugs.append(_parse_status(elem)) File "/usr/lib/pymodules/python2.7/debianbts.py", line 281, in _parse_status bug.source = _uc(tmp['source']) File "/usr/lib/pymodules/python2.7/debianbts.py", line 298, in _uc return unicode(string, 'utf-8', 'replace') TypeError: coercing to Unicode: need string or buffer, typedArrayType found systemas@syslaptop1:~$ Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#784181: razorqt: Razor-Qt dead upstream, superseded by LXDE-Qt
Hi Steve, (it's a long message, the important bits are just at the bottom). 2017-04-01 20:48 Steve Langasek: Hi Manuel, In May 2015, you wrote: I plan to ask FTP-masters for removal from unstable in a few months, when the new desktop is usable. But then in December 2016, you wrote: I am not sure, is there a big compelling reason to remove it, like big security bugs? It's dead upstream but it's still working fine without maintainance, and building in all Linux-based architectures. You didn't quote the following paragraphs in that message, which I think that are relevant: "I thought that once removed from unstable and LXQt becoming ready, it would decline in popularity measurably so we could think about removing it... but it's not declining, even as % it's maintaining the same levels [...] Once it disappears from the next stable maybe people migrate to LXQt and we see a big drop, or maybe complain that it was removed from stable or something... but until then, since there seem to be users, I don't have any compelling reason to remove it." Will come back to this later... I don't know if you find it compelling, but you have agreed that this package should not be in the next Debian release, which is why it's removed from testing; but by leaving it in unstable, it may still be included in releases of derivative distributions that pull from unstable. Ubuntu is an example of this - and for Ubuntu, we will manually remove the package - but other distributions may also be affected. You mention popcon as a reason for not removing the package. I guess there are a lot of users who have the package installed because it was a dependency of something else in the archive, and it's still installed because there was no transition which forced it off their systems. I wouldn't read into a high popcon count for a non-leaf package. Some (gentle) popcon saber-rattling: "razorqt-desktop" is not a leaf package, but "razorqt" is, only other "razorqt-*" packages Suggest it. (That's enough to keep it installed once it's been installed in most systems by default, I think, but still). "razorqt" is currently at 157, while it peaked at ~230 or so, and it's at the same level or higher than in mid 2015 (the big GCC-5 / C++11 ABI change): https://qa.debian.org/popcon-graph.php?packages=razorqt_installed=on_legend=on_ticks=on_fmt=%25Y-%25m=1 In percentages it's more clear that there're less installations than in the past: https://qa.debian.org/popcon-graph.php?packages=razorqt_installed=on_percent=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1 This is similar for all packages in this collection (the graph is oddly flattish): https://qa.debian.org/popcon-graph.php?packages=razorqt+libqtxdg0+libqtxdg0-dev+librazorqt0+librazorqt0-dev+razorqt-data+razorqt-appswitcher+razorqt-autosuspend+razorqt-config+razorqt-confupdate+razorqt-desktop+razorqt-globalkeyshortcuts+razorqt-lightdm-greeter+razorqt-notificationd+razorqt-openssh-askpass+razorqt-panel+razorqt-policykit-agent+razorqt-power+razorqt-runner+razorqt-session_installed=on_percent=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1 Anyway, "razorqt-desktop" is a non-leaf packages, but only "razorqt" Depends on it, and only other "razorqt-*" packages Recommend it. AFAIK it's been always like this in the past, there were no external reverse dependencies outside this group of packages. So in light of this, since the dependencies are (and AFAIK always were only) among razorqt packages, I think that it's reasonable to assume that people have installed it on purpose (not pulled by other packages), and there are people using it recently ("vote" columns). I am glad that LXQt is in Debian now, and I would be happy to remove it if the numbers dropped dramatically (that's what I thought that it would happen when I wrote the message back in 2015). But as things stand, there are still more than half the installations reported than at peak times, so I would just feel bad removing it from the archive at this point. Since the release is only weeks/months away, I would like to wait and see what happens. Is there another way to avoid this problem for derivatives, while maintaining it in unstable? Cheers. -- Manuel A. Fernandez Montecelo
Bug#858260: Re: Help needed for pandas bug: Could anybody verify the suspicion that tzdata might have some influence?
The underlying issue (but not strictly a bug as the documentation specifically says not to do that - http://sources.debian.net/src/python-tz/2016.7-0.2/pytz/tzinfo.py/#L247 ) is that passing a pytz tzinfo to the datetime constructor uses its first listed offset, not its correct offset for that date: >>> datetime.datetime(2017,4,1,tzinfo=pytz.timezone('Europe/London')) datetime.datetime(2017, 4, 1, 0, 0, tzinfo=GMT0:00:00 STD>) >>> pytz.timezone('Europe/London').localize(datetime.datetime(2017,4,1)) datetime.datetime(2017, 4, 1, 0, 0, tzinfo=BST+1:00:00 DST>) This suggests the attached fix, but this has *not* been tested. As for why it's only now showing up...there seems to be something weird going on where the initial 'LMT' entries of timezone definitions sometimes get loaded into pytz.timezone objects but often don't: jessie>>> pytz.timezone('Asia/Tokyo')._tzinfos {(datetime.timedelta(0, 32400), datetime.timedelta(0), 'JST'): , (datetime.timedelta(0, 32400), datetime.timedelta(0), 'JCST'): STD>, (datetime.timedelta(0, 36000), datetime.timedelta(0, 3600), 'JDT'): } sid>>> pytz.timezone('Asia/Tokyo')._tzinfos {(datetime.timedelta(0, 32400), datetime.timedelta(0), 'JST'): , (datetime.timedelta(0, 36000), datetime.timedelta(0, 3600), 'JDT'): JDT+10:00:00 DST>, (datetime.timedelta(0, 33540), datetime.timedelta(0), 'LMT'): } --- pandas/tests/test_multilevel0.py 2017-04-01 23:02:44.659970299 +0100 +++ pandas/tests/test_multilevel.py 2017-04-01 22:55:29.031975195 +0100 @@ -84,9 +84,9 @@ class TestMultiLevel(tm.TestCase): # GH 7112 import pytz tz = pytz.timezone('Asia/Tokyo') -expected_tuples = [(1.1, datetime.datetime(2011, 1, 1, tzinfo=tz)), - (1.2, datetime.datetime(2011, 1, 2, tzinfo=tz)), - (1.3, datetime.datetime(2011, 1, 3, tzinfo=tz))] +expected_tuples = [(1.1, tz.localize(datetime.datetime(2011, 1, 1))), + (1.2, tz.localize(datetime.datetime(2011, 1, 2))), + (1.3, tz.localize(datetime.datetime(2011, 1, 3)))] expected = Index([1.1, 1.2, 1.3] + expected_tuples) self.assertTrue(result.equals(expected)) @@ -104,9 +104,9 @@ class TestMultiLevel(tm.TestCase): result = midx_lv3.append(midx_lv2) expected = Index._simple_new( -np.array([(1.1, datetime.datetime(2011, 1, 1, tzinfo=tz), 'A'), - (1.2, datetime.datetime(2011, 1, 2, tzinfo=tz), 'B'), - (1.3, datetime.datetime(2011, 1, 3, tzinfo=tz), 'C')] + +np.array([(1.1, tz.localize(datetime.datetime(2011, 1, 1)), 'A'), + (1.2, tz.localize(datetime.datetime(2011, 1, 2)), 'B'), + (1.3, tz.localize(datetime.datetime(2011, 1, 3)), 'C')] + expected_tuples), None) self.assertTrue(result.equals(expected))
Bug#859260: marked as done (libncbi-vdb-dev: installs .a files to the incorrect directory)
Your message dated Sat, 01 Apr 2017 21:18:49 + with message-idand subject line Bug#859260: fixed in ncbi-vdb 2.8.1+dfsg-2 has caused the Debian Bug report #859260, regarding libncbi-vdb-dev: installs .a files to the incorrect directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 859260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libncbi-vdb-dev Version: 2.8.0+dfsg-1 Severity: serious Tags: patch Hi Maintainer Similar to #859257 in libngs-sdk-dev, .a files are installed to the incorrect directory (e.g. /usr/lib/i686-linux-gnu/ instead of /usr/lib/i386-linux-gnu/). The attached patch use s DEB_HOST_MULTIARCH instead of DEB_BUILD_GNU_TYPE to install .a files to the correct multiarch directory. Regards Graham --- a/debian/rules +++ b/debian/rules @@ -10,7 +10,7 @@ OS := $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) CPU := $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) -BUILDTYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +MULTIARCH := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) # since build-results are not ending up in the proper dir its saver to use "*" instead of "$(CPU)" SODIR := $(DEBPKGNAME)/$(DEBPKGNAME)/$(OS)/gcc VDB_ARCH := $(word 1, $(subst -, ,$(DEB_HOST_MULTIARCH))) @@ -25,7 +25,7 @@ if [ -e ngs-sdk/Makefile.config.$(OS).$(CPU) ] ; then \ dh_auto_clean ; \ fi - rm -rf $(DEBPKGNAME)/$(BUILDTYPE) + rm -rf $(DEBPKGNAME)/$(MULTIARCH) override_dh_auto_configure: # that's no standard configure script lacking support of default options @@ -34,7 +34,7 @@ # so we need to go with patches. The options are specified anyway. ln -s /usr/lib/jvm/default-java/include/jni.h libs/ngs-jni ln -s /usr/lib/jvm/default-java/include/linux/jni_md.h libs/ngs-jni - ./configure --build=$(BUILDTYPE) --prefix=/usr --build-prefix=$(CURDIR)/debian/tmp/usr --with-ngs-sdk-prefix=/usr --with-debug --with-ngs-java-prefix=/usr/share/java + ./configure --build=$(MULTIARCH) --prefix=/usr --build-prefix=$(CURDIR)/debian/tmp/usr --with-ngs-sdk-prefix=/usr --with-debug --with-ngs-java-prefix=/usr/share/java # no idea how to convince configure script to use the correct include dir so patching result afterwards sed -i 's?HDF5_INCDIR = /usr/include?&/hdf5/serial?' build/Makefile.config* @@ -61,16 +61,16 @@ --override s/libmbedcrypto0-dev/libmbedtls-dev/ \ --override s/libmbedtls10-dev/libmbedtls-dev/ \ --override s/libmbedx509-0-dev/libmbedtls-dev/ \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/lib/libncbi-ngs-c++.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp-norsrc.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkff.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libktst.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxfs.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxml.a usr/lib/$(BUILDTYPE) \ ---movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libload.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libtui.a usr/lib/$(BUILDTYPE) \ ---movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libtui_cpp.a usr/lib/$(BUILDTYPE) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/lib/libncbi-ngs-c++.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp-norsrc.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkff.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libktst.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxfs.a usr/lib/$(MULTIARCH) \ +
Bug#859257: marked as done (libngs-sdk-dev: installs .a files to the incorrect directory)
Your message dated Sat, 01 Apr 2017 21:04:53 + with message-idand subject line Bug#859257: fixed in ngs-sdk 1.3.0-2 has caused the Debian Bug report #859257, regarding libngs-sdk-dev: installs .a files to the incorrect directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 859257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libngs-sdk-dev Version: 1.2.3-3 Severity: serious Tags: patch Hi Maintainer .a files are installed to the incorrect directory (e.g. /usr/lib/i686-linux-gnu/ instead of /usr/lib/i386-linux-gnu/) , as can be seen in the following excerpt from a recent buildlog [1]: libngs-sdk-dev_1.3.0-1_i386.deb ─── new debian package, version 2.0. size 99736 bytes: control archive=3479 bytes. 1035 bytes,24 lines control 6887 bytes,98 lines md5sums Package: libngs-sdk-dev Source: ngs-sdk Version: 1.3.0-1 Architecture: i386 ... drwxr-xr-x root/root 0 2016-11-09 07:54 ./usr/lib/ drwxr-xr-x root/root 0 2016-11-09 07:54 ./usr/lib/i386-linux-gnu/ lrwxrwxrwx root/root 0 2016-11-09 07:54 ./usr/lib/i386-linux-gnu/libngs-sdk.so -> libngs-sdk.so.1 drwxr-xr-x root/root 0 2016-11-09 07:54 ./usr/lib/i686-linux-gnu/ lrwxrwxrwx root/root 0 2016-11-09 07:54 ./usr/lib/i686-linux-gnu/libngs-adapt-c++-static.a -> libngs-adapt-c++.a This causes at least sra-sdk to FTBFS on i386 [2] with the following error: checking for ngs-sdk package... includes... /usr libraries... checking /usr/lib/i386-linux-gnu/libngs-c++.a checking /usr/lib32/libngs-c++.a checking /usr/linux/gcc/i386/dbg/lib/libngs-c++.a no libraries... checking /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/lib/i386-linux-gnu/libngs-c++.a checking /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/lib32/libngs-c++.a checking /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/linux/gcc/i386/dbg/lib/libngs-c++.a no not found /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/ngs-sdk libraries... checking /usr/lib/i386-linux-gnu/libngs-c++.a checking /usr/lib32/libngs-c++.a checking /usr/linux/gcc/i386/dbg/lib/libngs-c++.a no ngs-sdk: includes: /usr/include; libs: ; ilibs: not needed configure: error: required ngs-sdk package not found. debian/rules:24: recipe for target 'override_dh_auto_configure' failed The following patch lets the .a files be installed to the correct multiarch directory: --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,7 @@ OS := $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) CPU := $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) BUILDTYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +MULTIARCH := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) # since build-results are not ending up in the proper dir its saver to use "*" instead of "$(CPU)" SODIR := $(DEBPKGNAME)/$(BUILDTYPE)/$(DEBPKGNAME)/$(OS)/gcc/* @@ -61,8 +62,8 @@ --devunversioned \ --exclude-a \ --exclude-la \ ---movedev "$(SODIR)/rel/lib/*.a*" usr/lib/$(BUILDTYPE) \ ---movedev "$(SODIR)/rel/ilib/*.a" usr/lib/$(BUILDTYPE) \ +--movedev "$(SODIR)/rel/lib/*.a*" usr/lib/$(MULTIARCH) \ +--movedev "$(SODIR)/rel/ilib/*.a" usr/lib/$(MULTIARCH) \ --movedev ngs-sdk/ngs usr/include \ $(SODIR)/rel/lib/libngs-sdk.so Regards Graham [1] https://buildd.debian.org/status/fetch.php?pkg=ngs-sdk=i386=1.3.0-1=1478684848=0 [2] https://buildd.debian.org/status/fetch.php?pkg=sra-sdk=i386=2.8.1-2%2Bdfsg-1=1485249305=0 --- End Message --- --- Begin Message --- Source: ngs-sdk Source-Version: 1.3.0-2 We believe that the bug you reported is fixed in the latest version of ngs-sdk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated ngs-sdk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Apr 2017 22:33:07 +0200 Source: ngs-sdk Binary: libngs-sdk1
Bug#851750: marked as done (kpatch: module FTBFS for Linux 4.9)
Your message dated Sat, 01 Apr 2017 21:04:32 + with message-idand subject line Bug#851750: fixed in kpatch 0.3.2-3.1 has caused the Debian Bug report #851750, regarding kpatch: module FTBFS for Linux 4.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 851750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kpatch Version: 0.3.2-3 Severity: serious Justification: fails to build from source Hi, kpatch cannot build the kernel module for the current kernel in sid: DKMS make.log for kpatch-0.3.2 for kernel 4.9.0-1-amd64 (x86_64) Wed Jan 18 12:55:36 UTC 2017 make: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod' make -C core clean make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \ Module.symvers make[1]: Leaving directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' make -C core make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' make -C /lib/modules/4.9.0-1-amd64/build M=/var/lib/dkms/kpatch/0.3.2/build/kmod/core kpatch.ko make[2]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. CC [M] /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.o /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:308:21: error: variable 'kpatch_backtrace_ops' has initializer but incomplete type static const struct stacktrace_ops kpatch_backtrace_ops = { ^~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:309:2: error: unknown field 'address' specified in initializer .address = kpatch_backtrace_address_verify, ^ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:309:13: warning: excess elements in struct initializer .address = kpatch_backtrace_address_verify, ^~~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:309:13: note: (near initialization for 'kpatch_backtrace_ops') /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:310:2: error: unknown field 'stack' specified in initializer .stack = kpatch_backtrace_stack, ^ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:310:12: warning: excess elements in struct initializer .stack = kpatch_backtrace_stack, ^~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:310:12: note: (near initialization for 'kpatch_backtrace_ops') /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:2: error: unknown field 'walk_stack' specified in initializer .walk_stack = print_context_stack_bp, ^ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:16: error: 'print_context_stack_bp' undeclared here (not in a function) .walk_stack = print_context_stack_bp, ^~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:16: warning: excess elements in struct initializer /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:16: note: (near initialization for 'kpatch_backtrace_ops') /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:338:21: error: variable 'kpatch_print_trace_ops' has initializer but incomplete type static const struct stacktrace_ops kpatch_print_trace_ops = { ^~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:339:2: error: unknown field 'stack' specified in initializer .stack = kpatch_print_trace_stack, ^ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:339:12: warning: excess elements in struct initializer .stack = kpatch_print_trace_stack, ^~~~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:339:12: note: (near initialization for 'kpatch_print_trace_ops') /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:340:2: error: unknown field 'address' specified in initializer .address = kpatch_print_trace_address, ^ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:340:13: warning: excess elements in struct initializer .address = kpatch_print_trace_address, ^~ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:340:13: note: (near initialization for 'kpatch_print_trace_ops') /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:341:2: error: unknown field 'walk_stack' specified in initializer .walk_stack = print_context_stack, ^ /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:341:16: error: 'print_context_stack' undeclared here (not in a function) .walk_stack =
Processed: nodejs, ossl1.1
Processing commands for cont...@bugs.debian.org: > # nodejs > unarchive 828457 Bug #828457 {Done: Jérémy Lal} [src:nodejs] nodejs: FTBFS with openssl 1.1.0 Unarchived Bug 828457 > clone 828457 -1 Bug #828457 {Done: Jérémy Lal } [src:nodejs] nodejs: FTBFS with openssl 1.1.0 Bug 828457 cloned as bug 859297 827061 was blocked by: 828552 828509 828314 828310 828316 828576 828409 828277 828302 835585 828361 828611 828613 828585 828271 844926 828354 828440 828489 828339 828255 828619 828342 828599 828385 828391 835794 828350 846769 828285 828419 828434 828618 828593 808669 843988 844833 835800 844836 828467 850881 828490 829452 828363 828517 828616 828293 828615 843852 828588 828530 828595 828497 828337 828587 844975 850880 828496 828322 828233 828394 844664 828345 844706 828262 828421 844877 828294 844234 828430 828565 844947 828229 844838 828228 828424 828523 828254 828320 828267 828284 828242 828541 828436 835789 828427 828274 828527 828529 828603 844213 828559 828381 828555 828334 828336 845106 828356 828288 828280 828324 836419 828235 828589 828417 828495 828429 828493 828457 828248 828433 828295 828301 828355 828390 828279 828328 828488 828232 828399 828444 828083 828524 828289 828514 844301 828389 828539 843871 835811 828547 844906 828531 828249 828512 828448 828317 828392 835793 828519 829465 854468 850883 828418 828443 828380 857199 828620 828437 828502 828258 845729 844951 828459 844909 828591 828422 835804 828297 828369 844311 828311 828371 828259 828608 828386 828485 854470 828269 828511 844271 828461 822380 844904 828376 809271 844949 828246 828610 828308 844936 828583 835785 844366 828507 828357 828594 828578 828362 828401 828453 828330 828492 828609 828338 828466 844948 844815 828510 828480 828344 828411 828518 828406 828542 828435 828534 828383 846113 828309 855007 844345 828331 828268 828373 828341 828573 828469 828360 828234 828465 828484 828265 828500 828410 828313 828244 828584 828602 828366 828536 828543 828298 828569 828412 828446 835797 828535 844928 828563 844907 845016 828525 846908 828581 835790 828287 828260 828575 843682 828375 844254 843532 828515 828617 828438 828579 828487 828315 828387 828562 828568 828252 828455 828325 828528 828606 844931 828405 828304 828400 828396 828397 854253 828257 828556 828296 828548 828604 828601 828241 828231 828580 828358 828379 828415 828398 828464 828538 828303 828491 828574 828561 828550 828505 844503 828508 828473 828474 828456 828501 828253 828364 828600 828240 828378 828586 828283 828442 828272 844534 828251 828614 828597 828596 828335 828388 828263 835796 828567 828370 828333 835799 828533 828278 844018 828323 828540 828494 844870 835786 828243 828256 828460 828261 828292 828598 828564 828590 828319 828306 828343 828348 828127 841635 828454 828526 828382 828452 828570 828282 828432 844920 828374 828230 828281 828082 828450 828367 828414 828407 828447 828521 828605 828458 828532 835549 828318 828352 828275 828416 828403 814600 828428 828420 828482 828290 828545 828582 828516 828577 828139 828553 828264 844347 828377 828359 828612 837960 827068 828558 828431 828478 828426 828384 828468 828393 828499 828238 828554 845030 828423 828479 828607 828395 828402 828472 828305 828270 850882 828549 828462 828463 828506 828237 828365 828349 828321 828504 828470 828551 828276 828592 828340 844845 844800 844916 828445 854257 828476 828439 828571 828347 835798 828372 828326 828404 828286 828239 828346 828566 828291 828351 828250 828503 844663 828544 828546 828368 828537 844945 828307 828300 827061 was not blocking any bugs. Added blocking bug(s) of 827061: 859297 > archive 828457 Bug #828457 {Done: Jérémy Lal } [src:nodejs] nodejs: FTBFS with openssl 1.1.0 archived 828457 to archive/57 (from 828457) > reopen -1 Bug #859297 {Done: Jérémy Lal } [src:nodejs] nodejs: FTBFS with openssl 1.1.0 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions nodejs/4.7.2~dfsg-1. > retitle -1 nodejs: Please migrate to openssl1.1 in buster Bug #859297 [src:nodejs] nodejs: FTBFS with openssl 1.1.0 Changed Bug title to 'nodejs: Please migrate to openssl1.1 in buster' from 'nodejs: FTBFS with openssl 1.1.0'. > unblock 827061 with -1 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828526 828439 835798 828492 828384 828394 828453 828585 828341 828345 828593 828613 828571 828343 828294 837960 828279 844311 828242 828297 828512 828506 835789 828376 828396 844663 850883 828549 844534 828433 828409 835804 844916 828288 828265 828472 841635 828504 828315 828609 828435 828586 828564 844947 828490 828484 828599 828405 844845 828248 844706 828258 828370 828563 844920 828281 828360 835797 828427 846769 828567 828446 828240 828310 828359 828316 828495 828372 828307 828423 828382 828543 828399 845016
Bug#857044: marked as done (gnu-smalltalk FTBFS on ppc64el: intmath.st FAILED (testsuite.at:33))
Your message dated Sat, 1 Apr 2017 23:23:06 +0300 with message-id <20170401202306.eqcoywd5vkjb6ak2@localhost> and subject line Re: Bug#857044: gnu-smalltalk FTBFS on ppc64el: intmath.st FAILED (testsuite.at:33) has caused the Debian Bug report #857044, regarding gnu-smalltalk FTBFS on ppc64el: intmath.st FAILED (testsuite.at:33) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 857044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnu-smalltalk Version: 3.2.5-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=gnu-smalltalk=ppc64el=3.2.5-1+b3=1488894455=0 ... make[3]: Entering directory '/«PKGBUILDDIR»/tests' /bin/bash './testsuite' ## --- ## ## GNU Smalltalk 3.2.5 test suite. ## ## --- ## Regression tests. 1: arrays.st ok 2: classes.st ok 3: blocks.st ok 4: sets.st ok 5: processes.stok 6: exceptions.st ok 7: intmath.st FAILED (testsuite.at:33) 8: floatmath.st E: Caught signal ‘Terminated’: terminating immediately Terminated Makefile:1059: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Terminated --- End Message --- --- Begin Message --- On Tue, Mar 07, 2017 at 04:00:37PM +0200, Adrian Bunk wrote: > Source: gnu-smalltalk > Version: 3.2.5-1 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=gnu-smalltalk=ppc64el=3.2.5-1+b3=1488894455=0 > > ... > make[3]: Entering directory '/«PKGBUILDDIR»/tests' > /bin/bash './testsuite' > ## --- ## > ## GNU Smalltalk 3.2.5 test suite. ## > ## --- ## > > Regression tests. > > 1: arrays.st ok > 2: classes.st ok > 3: blocks.st ok > 4: sets.st ok > 5: processes.stok > 6: exceptions.st ok > 7: intmath.st FAILED (testsuite.at:33) > 8: floatmath.st E: Caught signal > ‘Terminated’: terminating immediately > Terminated > > Makefile:1059: recipe for target 'check-recursive' failed > make[1]: *** [check-recursive] Terminated A later rebuild succeeded: https://buildd.debian.org/status/logs.php?pkg=gnu-smalltalk=ppc64el The intmath.st failure seems to be "normal", and the actual build failure was that floatmath.st was terminated. I am closing this bug, on the assumption that this was caused by some issue on the buildd. 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--- End Message ---
Bug#858553: Re Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
First shot at debugging from my side. Because the error says: Exception at 004BDB6C: EDOMError: EDOMError in DOMDocument.CreateElement. I searched for "DOMDocument.CreateElement". Low and behold, I find something interesting in fpcsrc/packages/fcl-xml/src/dom.pp: function TDOMDocument.CreateElement(const tagName: DOMString): TDOMElement; begin if not IsXmlName(tagName) then raise EDOMError.Create(INVALID_CHARACTER_ERR, 'DOMDocument.CreateElement'); TDOMNode(Result) := Alloc(TDOMElement); Result.Create(Self);http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision=2042 Result.FNSI.QName := FNames.FindOrAdd(DOMPChar(tagName), Length(tagName)); Result.AttachDefaultAttrs; end; First idea that pops into my mind is: it looks like the source of lazarus has characters that fp-docs can't convert. Apparently an error is raised, but converted by fp-docs into exit code 0. Interesting to note, is the delta between 2.4.6 and 3.0.0: - if not IsXmlName(tagName, FXMLVersion = xmlVersion11) then + if not IsXmlName(tagName) then which was done in this commit: http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision=20422 Sending now as I am about to stop for today, but summary as I currently suspect the situation is: 1) fp-doc fails to create error exit code during error 2) lazarus may have xml files that need updating. Probably the next time I spend time on this will be to bisect the documentation creation to see which file(s) need fixing -> to potentially solve issue 2 if that is indeed the issue. Paul signature.asc Description: OpenPGP digital signature
Bug#859295: bup: Fix possible 'bup gc --threshold=0' data loss
Robert Edmondswrites: > Package: bup > Version: 0.29-2 > Severity: critical > Justification: possibility of serious data loss > > Hi, > > The bup 0.29.1 release contains a fix for a bug that can cause serious > data loss (dbda0e98074b8b6ec20f4bdf5479b2847cc8eb0e, attached). Release managers: just a note that upstream is completely in favor of this change. [Robert: thanks for pursuing it.] -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#859295: marked as done (bup: Fix possible 'bup gc --threshold=0' data loss)
Your message dated Sat, 01 Apr 2017 19:18:47 + with message-idand subject line Bug#859295: fixed in bup 0.29-3 has caused the Debian Bug report #859295, regarding bup: Fix possible 'bup gc --threshold=0' data loss to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 859295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bup Version: 0.29-2 Severity: critical Justification: possibility of serious data loss Hi, The bup 0.29.1 release contains a fix for a bug that can cause serious data loss (dbda0e98074b8b6ec20f4bdf5479b2847cc8eb0e, attached). From the upstream release notes: Notable changes in 0.29.1 as compared to 0.29 = May require attention - * Running gc with a --threshold of 0 no longer runs the risk of corrupting the repository. (The default threshold is 10). Previously, gc could delete a packfile after rewriting it when the packfile didn't change. This commit should be cherry-picked for stretch. -- Robert Edmonds edmo...@debian.org >From dbda0e98074b8b6ec20f4bdf5479b2847cc8eb0e Mon Sep 17 00:00:00 2001 From: Tim Riemenschneider Date: Mon, 6 Mar 2017 23:08:46 +0100 Subject: [PATCH] Saveguard against deleting new pack-file (f.e. with threshold=0) Signed-off-by: Tim Riemenschneider [r...@defaultvalue.org: wrap comment line in test-gc.sh; adjust comment whitespace in gc.py] Reviewed-by: Rob Browning Tested-by: Rob Browning --- lib/bup/gc.py | 2 ++ t/test-gc.sh | 19 +++ 2 files changed, 21 insertions(+) diff --git a/lib/bup/gc.py b/lib/bup/gc.py index c0a1c0e..395094a 100644 --- a/lib/bup/gc.py +++ b/lib/bup/gc.py @@ -135,6 +135,8 @@ def sweep(live_objects, existing_count, cat_pipe, threshold, compression, if verbosity and new_pack_prefix: log('created ' + basename(new_pack_prefix) + '\n') for p in ns.stale_files: +if new_pack_prefix and p.startswith(new_pack_prefix): +continue # Don't remove the new pack file if verbosity: log('removing ' + basename(p) + '\n') os.unlink(p) diff --git a/t/test-gc.sh b/t/test-gc.sh index 82be29c..2739ae7 100755 --- a/t/test-gc.sh +++ b/t/test-gc.sh @@ -219,4 +219,23 @@ WVPASSEQ 1 $(echo "$only_in_before" | wc -l) WVPASSEQ 1 $(echo "$only_in_after" | wc -l) WVPASSEQ 1 $(echo "$in_both" | wc -l) +WVSTART "gc (threshold 0)" + +WVPASS rm -rf "$BUP_DIR" +WVPASS bup init +WVPASS rm -rf src && mkdir src +WVPASS echo 0 > src/0 +WVPASS echo 1 > src/1 + +WVPASS bup index src +WVPASS bup save -n src-1 src + +packs_before="$(ls "$BUP_DIR/objects/pack/"*.pack)" || exit $? +WVPASS bup gc -v $GC_OPTS --threshold 0 2>&1 | tee gc.log +packs_after="$(ls "$BUP_DIR/objects/pack/"*.pack)" || exit $? +# Check that the pack was rewritten, but not removed (since the +# result-pack is equal to the source pack) +WVPASSEQ 1 "$(grep -cE '^rewriting ' gc.log)" +WVPASSEQ "$packs_before" "$packs_after" + WVPASS rm -rf "$tmpdir" -- 2.11.0 --- End Message --- --- Begin Message --- Source: bup Source-Version: 0.29-3 We believe that the bug you reported is fixed in the latest version of bup, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Edmonds (supplier of updated bup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Apr 2017 14:38:19 -0400 Source: bup Binary: bup bup-doc Architecture: source amd64 all Version: 0.29-3 Distribution: unstable Urgency: medium Maintainer: Robert Edmonds Changed-By: Robert Edmonds Description: bup- highly efficient file backup system based on git bup-doc- highly efficient file backup system based on git (documentation) Closes: 859295 Changes: bup (0.29-3) unstable;
Processed: Re: Bug#858509: cl-csv-data-table: broken symlink: /usr/share/common-lisp/systems/cl-csv-data-table.asd -> ../source/cl-csv-data-table/cl-csv-data-table.asd
Processing control commands: > tag -1 + patch Bug #858509 [cl-csv-data-table] cl-csv-data-table: broken symlink: /usr/share/common-lisp/systems/cl-csv-data-table.asd -> ../source/cl-csv-data-table/cl-csv-data-table.asd Added tag(s) patch. -- 858509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858509: cl-csv-data-table: broken symlink: /usr/share/common-lisp/systems/cl-csv-data-table.asd -> ../source/cl-csv-data-table/cl-csv-data-table.asd
Control: tag -1 + patch On Thu, 23 Mar 2017 00:04:03 +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. > > >From the attached log (scroll to the bottom...): > > 0m23.3s ERROR: FAIL: Broken symlinks: > /usr/share/common-lisp/systems/cl-csv-data-table.asd -> > ../source/cl-csv-data-table/cl-csv-data-table.asd > > ^^^ > > The package ships > /usr/share/common-lisp/source/cl-csv/cl-csv-data-table.asd > From looking at the 3 binary packages and their .dirs/.install/.links files, it seems that debian/cl-csv-data-table.install should install the files into a directory named after the package, like the others do (and it even creates the directory). Patch attached, not NMUing right now since I don't know the cl enviroment ... Cheers, gregor -- .''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Pink Floyd: Shine On You Crazy Diamond (Parts 6-9) diff -Nru cl-csv-20150608/debian/changelog cl-csv-20150608/debian/changelog --- cl-csv-20150608/debian/changelog 2015-07-15 15:44:31.0 +0200 +++ cl-csv-20150608/debian/changelog 2017-04-01 21:10:33.0 +0200 @@ -1,3 +1,14 @@ +cl-csv (20150608-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix "broken symlink: /usr/share/common-lisp/systems/cl-csv-data- +table.asd -> ../source/cl-csv-data-table/cl-csv-data-table.asd": +debian/cl-csv-data-table.install: install into directory matching package +name. +(Closes: #858509) + + -- gregor herrmannSat, 01 Apr 2017 21:10:33 +0200 + cl-csv (20150608-1) unstable; urgency=medium * Quicklisp release update. diff -Nru cl-csv-20150608/debian/cl-csv-data-table.install cl-csv-20150608/debian/cl-csv-data-table.install --- cl-csv-20150608/debian/cl-csv-data-table.install 2014-04-30 16:01:04.0 +0200 +++ cl-csv-20150608/debian/cl-csv-data-table.install 2017-04-01 21:10:33.0 +0200 @@ -1,2 +1,2 @@ -cl-csv-data-table.asd usr/share/common-lisp/source/cl-csv -data-table.lisp usr/share/common-lisp/source/cl-csv \ No newline at end of file +cl-csv-data-table.asd usr/share/common-lisp/source/cl-csv-data-table +data-table.lisp usr/share/common-lisp/source/cl-csv-data-table signature.asc Description: Digital Signature
Bug#857087: nsscache: /usr/share/nsscache not installed
On Tue, 07 Mar 2017 23:34:14 +0100, Sebastian Hahn wrote: > installing nsscache also installed a symlink from /usr/sbin/nsscache to > ../share/nsscache/nsscache, but /usr/share/nsscache is not being > installed. This differs from the stable package where > /usr/share/nsscache exists. The package in testing and unstable now installs /usr/bin/nsscache, so I guess the broken symlink /usr/sbin/nsscache -> /usr/share/nsscache can just be removed (i.e. debian/links deleted in the source package). Cheers, gregor -- .''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Pink Floyd: Shine On You Crazy Diamond (Parts 6-9) signature.asc Description: Digital Signature
Processed: Bug#858564 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 858564 pending Bug #858564 [samba] Cannot access anything under a subdirectory if symlinks are disallowed Ignoring request to alter tags of bug #858564 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 858564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858564: marked as pending
tag 858564 pending thanks Hello, Bug #858564 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-samba/samba.git/commit/?id=a42f73e --- commit a42f73eaf1e692ff14cc645a6aa47890edfc61e9 Author: Mathieu ParentDate: Sat Apr 1 17:42:00 2017 +0200 Release 2:4.5.8+dfsg-1 diff --git a/debian/changelog b/debian/changelog index 96943d6..ab38326 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +samba (2:4.5.8+dfsg-1) unstable; urgency=high + + * New upstream version +- Drop CVE-2017-2619.patch: merged upstream +- Fix CVE-2017-2619 regression with "follow symlink = no" (Closes: #858564) + + -- Mathieu Parent Sat, 01 Apr 2017 20:39:17 +0200 + samba (2:4.5.6+dfsg-2) unstable; urgency=high * This is a security release in order to address the following defects:
Bug#784181: razorqt: Razor-Qt dead upstream, superseded by LXDE-Qt
Hi Manuel, In May 2015, you wrote: > I plan to ask FTP-masters for removal from unstable in a few months, when > the new desktop is usable. But then in December 2016, you wrote: > I am not sure, is there a big compelling reason to remove it, like big > security bugs? It's dead upstream but it's still working fine without > maintainance, and building in all Linux-based architectures. I don't know if you find it compelling, but you have agreed that this package should not be in the next Debian release, which is why it's removed from testing; but by leaving it in unstable, it may still be included in releases of derivative distributions that pull from unstable. Ubuntu is an example of this - and for Ubuntu, we will manually remove the package - but other distributions may also be affected. You mention popcon as a reason for not removing the package. I guess there are a lot of users who have the package installed because it was a dependency of something else in the archive, and it's still installed because there was no transition which forced it off their systems. I wouldn't read into a high popcon count for a non-leaf package. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Processed: reassign 858528 to init-select
Processing commands for cont...@bugs.debian.org: > # try again, looks like colin's attempt failed > reassign 858528 init-select Bug #858528 [grub-coreboot] grub-coreboot: fails to upgrade from jessie to stretch if init-select was installed Bug reassigned from package 'grub-coreboot' to 'init-select'. No longer marked as found in versions grub2/2.02~beta3-5. Ignoring request to alter fixed versions of bug #858528 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 858528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 806879
Processing commands for cont...@bugs.debian.org: > # delayed/5 > tags 806879 + pending Bug #806879 [src:xsp] xsp: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 806879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859295: bup: Fix possible 'bup gc --threshold=0' data loss
Package: bup Version: 0.29-2 Severity: critical Justification: possibility of serious data loss Hi, The bup 0.29.1 release contains a fix for a bug that can cause serious data loss (dbda0e98074b8b6ec20f4bdf5479b2847cc8eb0e, attached). From the upstream release notes: Notable changes in 0.29.1 as compared to 0.29 = May require attention - * Running gc with a --threshold of 0 no longer runs the risk of corrupting the repository. (The default threshold is 10). Previously, gc could delete a packfile after rewriting it when the packfile didn't change. This commit should be cherry-picked for stretch. -- Robert Edmonds edmo...@debian.org >From dbda0e98074b8b6ec20f4bdf5479b2847cc8eb0e Mon Sep 17 00:00:00 2001 From: Tim RiemenschneiderDate: Mon, 6 Mar 2017 23:08:46 +0100 Subject: [PATCH] Saveguard against deleting new pack-file (f.e. with threshold=0) Signed-off-by: Tim Riemenschneider [r...@defaultvalue.org: wrap comment line in test-gc.sh; adjust comment whitespace in gc.py] Reviewed-by: Rob Browning Tested-by: Rob Browning --- lib/bup/gc.py | 2 ++ t/test-gc.sh | 19 +++ 2 files changed, 21 insertions(+) diff --git a/lib/bup/gc.py b/lib/bup/gc.py index c0a1c0e..395094a 100644 --- a/lib/bup/gc.py +++ b/lib/bup/gc.py @@ -135,6 +135,8 @@ def sweep(live_objects, existing_count, cat_pipe, threshold, compression, if verbosity and new_pack_prefix: log('created ' + basename(new_pack_prefix) + '\n') for p in ns.stale_files: +if new_pack_prefix and p.startswith(new_pack_prefix): +continue # Don't remove the new pack file if verbosity: log('removing ' + basename(p) + '\n') os.unlink(p) diff --git a/t/test-gc.sh b/t/test-gc.sh index 82be29c..2739ae7 100755 --- a/t/test-gc.sh +++ b/t/test-gc.sh @@ -219,4 +219,23 @@ WVPASSEQ 1 $(echo "$only_in_before" | wc -l) WVPASSEQ 1 $(echo "$only_in_after" | wc -l) WVPASSEQ 1 $(echo "$in_both" | wc -l) +WVSTART "gc (threshold 0)" + +WVPASS rm -rf "$BUP_DIR" +WVPASS bup init +WVPASS rm -rf src && mkdir src +WVPASS echo 0 > src/0 +WVPASS echo 1 > src/1 + +WVPASS bup index src +WVPASS bup save -n src-1 src + +packs_before="$(ls "$BUP_DIR/objects/pack/"*.pack)" || exit $? +WVPASS bup gc -v $GC_OPTS --threshold 0 2>&1 | tee gc.log +packs_after="$(ls "$BUP_DIR/objects/pack/"*.pack)" || exit $? +# Check that the pack was rewritten, but not removed (since the +# result-pack is equal to the source pack) +WVPASSEQ 1 "$(grep -cE '^rewriting ' gc.log)" +WVPASSEQ "$packs_before" "$packs_after" + WVPASS rm -rf "$tmpdir" -- 2.11.0
Processed: Re: phpmyadmin: Fails to build from source, illegal character in input string
Processing control commands: > retitle -1 phpmyadmin: Fails to build from source, illegal character in input > string Bug #859219 [phpmyadmin] phpmyadmin sometimes FTBFS in test-suite Changed Bug title to 'phpmyadmin: Fails to build from source, illegal character in input string' from 'phpmyadmin sometimes FTBFS in test-suite'. -- 859219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859219: phpmyadmin: Fails to build from source, illegal character in input string
Control: retitle -1 phpmyadmin: Fails to build from source, illegal character in input string Sorry for the noise, I missed the fact that Michal already responded as I forgot to refresh the bug page that was open in my browser. Paul signature.asc Description: OpenPGP digital signature
Bug#859294: hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)
Source: hunspell-dict-ko Version: 0.6.0-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, hunspell-dict-ko fails to build from source in unstable/amd64: […] dh build dh_testdir dh_update_autotools_config dh_auto_configure dh_auto_build make -j1 make[1]: Entering directory '«BUILDDIR»' python3 make-aff-dic.py ko.aff ko.dic dict-ko-builtins.json dict-ko-galkwi.json Traceback (most recent call last): File "make-aff-dic.py", line 329, in dic.load_json(open(filename)) File "make-aff-dic.py", line 166, in load_json d = json.load(infile) File "/usr/lib/python3.5/json/__init__.py", line 265, in load return loads(fp.read(), File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128) Makefile:28: recipe for target 'ko.aff' failed make[1]: *** [ko.aff] Error 1 make[1]: Leaving directory '«BUILDDIR»' dh_auto_build: make -j1 returned exit code 2 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- hunspell-dict-ko.0.6.0-2.unstable.amd64.log.txt.gz Description: Binary data
Processed: Re: phpmyadmin: Fails to build from source, illegal character in input string
Processing control commands: > retitle -1 phpmyadmin sometimes FTBFS in test-suite Bug #859219 [phpmyadmin] phpmyadmin: Fails to build from source, illegal character in input string Changed Bug title to 'phpmyadmin sometimes FTBFS in test-suite' from 'phpmyadmin: Fails to build from source, illegal character in input string'. -- 859219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859219: phpmyadmin: Fails to build from source, illegal character in input string
Control: retitle -1 phpmyadmin sometimes FTBFS in test-suite On Fri, 31 Mar 2017 14:10:20 -0400 Jeremy Bichawrote: > Package: phpmyadmin > Version: 4:4.6.6-1 > Severity: serious > > phpmyadmin 4:4.6.6-1 and 4:4.6.6-2 fail to build from source in a > clean sid chroot (and in Ubuntu 17.04). Apparently it is more subtle. While trying to reproduce the issue to investigate it I did a no-change test rebuild on debomatic. It succeeds without issues: http://debomatic-amd64.debian.net/distribution#unstable/phpmyadmin/4.6.6-2.1/buildlog Paul signature.asc Description: OpenPGP digital signature
Bug#806879: xsp: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails)
On Mon, Mar 27, 2017 at 05:16:18PM +0100, Jo Shields wrote: > > > On 26/03/17 05:18, tony mancill wrote: > > Package: src:xsp > > Followup-For: Bug #806879 > > > > Hi Debian Mono Group, > > > > The workaround patch works fine. Is there anything preventing an > > upload? Would the team be okay with an NMU? > > NMU is fine > > Sorry, I've been hugely busy & unable to spend much time on Debian stuff Hi Jo, Thanks for the response. An NMU that addresses the (2) outstanding RC bugs has been uploaded to delayed/5. I'm happy to dcut the upload if there's anything amiss. Cheers, tony signature.asc Description: PGP signature
Bug#511645: marked as done (xtrs: hangs on startup due to use of SIGIO)
Your message dated Sat, 01 Apr 2017 15:49:57 + with message-idand subject line Bug#511645: fixed in xtrs 4.9c-4 has caused the Debian Bug report #511645, regarding xtrs: hangs on startup due to use of SIGIO to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 511645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xtrs Version: 4.9c-3 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu intrepid ubuntu-patch Hi, In https://bugs.launchpad.net/bugs/223098 it was reported that xtrs can hang on startup. At http://www.tim-mann.org/xtrs.html the instructions are to remove -DHAVE_SIGIO from the Makefile, which the attached patch does. In addition to that it fixes up a couple of coding issues that Ubuntu's compiler found. There are two instances of "format not a string literal and no format arguments", and some places where the return codes of functions are not checked. For the instances of that problem in trs_disk.c I just hid the problem, as there is no error checking of other functions in that code it didn't seem worth having it. Obviously adding error checking would be preferable. Please consider applying the patch. Thanks, James --- xtrs-4.9c.orig/Makefile +++ xtrs-4.9c/Makefile @@ -143,7 +143,7 @@ include Makefile.local CFLAGS = $(DEBUG) $(ENDIAN) $(DEFAULT_ROM) $(READLINE) $(DISKDIR) $(IFLAGS) \ - $(APPDEFAULTS) -DKBWAIT -DHAVE_SIGIO + $(APPDEFAULTS) -DKBWAIT LIBS = $(XLIB) $(READLINELIBS) $(EXTRALIBS) ZMACFLAGS = -h only in patch2: unchanged: --- xtrs-4.9c.orig/debug.c +++ xtrs-4.9c/debug.c @@ -515,7 +515,7 @@ { if(!strcmp(command, "help") || !strcmp(command, "?")) { - printf(help_message); + printf("%s", help_message); } else if (!strcmp(command, "zbxinfo")) { only in patch2: unchanged: --- xtrs-4.9c.orig/dis.c +++ xtrs-4.9c/dis.c @@ -2115,7 +2115,7 @@ break; case A_0: /* No args */ case A_0B: /* No args, backskip over last opcode byte */ - printf (code->name); + printf ("%s", code->name); break; case A_8R: /* One 8-bit relative address */ printf (code->name, (pc + 1 + (char) mem_read(pc)) & 0x); only in patch2: unchanged: --- xtrs-4.9c.orig/mkdisk.c +++ xtrs-4.9c/mkdisk.c @@ -15,6 +15,7 @@ #include #include +#include #include #include #include @@ -44,6 +45,7 @@ int cyl = -1, sec = -1, gran = -1, dir = -1, eight = 0, ignden = 0; int writeprot = 0, unprot = 0; int i, c, oumask; + int written; char *fname; FILE *f; @@ -385,7 +387,15 @@ perror(fname); exit(1); } -fwrite(, sizeof(rhh), 1, f); +do { + written = fwrite(, sizeof(rhh), 1, f); + if (written >= 1) +break; +} while (written >= 0 || errno == EINTR); +if (written < 0) { + perror(fname); + exit(1); +} } fclose(f); return 0; only in patch2: unchanged: --- xtrs-4.9c.orig/trs_disk.c +++ xtrs-4.9c/trs_disk.c @@ -674,7 +674,7 @@ } else { newlen = offset(d, 0); } -ftruncate(fileno(d->file), newlen); +if (ftruncate(fileno(d->file), newlen)) {} } } @@ -808,7 +808,7 @@ /* Read first block of ids */ fseek(d->file, JV3_IDSTART, 0); -fread((void*)>u.jv3.id[0], 3, JV3_SECSPERBLK, d->file); +if (fread((void*)>u.jv3.id[0], 3, JV3_SECSPERBLK, d->file)) {} /* Scan to find their offsets */ ofst = JV3_SECSTART; @@ -2217,7 +2217,7 @@ fseek(d->file, DMK_HDR_SIZE + (d->phytrack * d->u.dmk.nsides + state.curside) * d->u.dmk.tracklen, 0); -fwrite(d->u.dmk.buf, d->u.dmk.curbyte, 1, d->file); +if (fwrite(d->u.dmk.buf, d->u.dmk.curbyte, 1, d->file)) {} if (d->phytrack >= d->u.dmk.ntracks) { d->u.dmk.ntracks = d->phytrack + 1; fseek(d->file, DMK_NTRACKS, 0); --- End Message --- --- Begin Message --- Source: xtrs Source-Version: 4.9c-4 We believe that the bug you reported is fixed in the latest version of xtrs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 511...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. G. Branden Robinson (supplier of updated xtrs package) (This message was generated automatically at their
Processed: Re: Bug#859150: installation-guide: leaves many /tmp/tmp* files behind
Processing control commands: > tags -1 + pending Bug #859150 [src:installation-guide] installation-guide: leaves many /tmp/tmp* files behind Added tag(s) pending. -- 859150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859150: installation-guide: leaves many /tmp/tmp* files behind
Control: tags -1 + pending Cyril Bruleboiswrote: > Source: installation-guide > Severity: serious > Tags: patch > Justification: Fills up /tmp on dillon.debian.org > > Hi, > > Maybe to ease hands-on debugging, dblatex is called with the -d flag, > which tells it to leave temporary files behind. This ends up filling > up dillon's /tmp (in addition to being rather bad style in the first > place…). > > Two possibilities: > - remove the -d flag entirely (untested); > - or set TMPDIR to a subdirectory of $tempdir, which gets automatically >removed after a build. > > The attached patch implements the second solution, but comments are > welcome. Patch tested and applied. Thanks -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0 " J E S S I E " . Registered Linux User #311290 - https://linuxcounter.net/
Bug#845323: marked as done (ovirt-guest-agent: Ovirt-guest-agent crashes with a stack smash)
Your message dated Sat, 1 Apr 2017 16:07:28 +0200 with message-idand subject line Re: Bug#845323: ovirt-guest-agent: Ovirt-guest-agent crashes with a stack smash has caused the Debian Bug report #845323, regarding ovirt-guest-agent: Ovirt-guest-agent crashes with a stack smash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 845323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ovirt-guest-agent Version: 1.0.12.2.dfsg-2 Severity: important When starting the ovirt-guest-agent it crashed with a stack smash. Happens with 1.0.12.2.dfsg-2 and dfsg-1. Same issue on sid. The ovirt-guest-agent from http://download.opensuse.org/repositories/home:/evilissimo:/deb/Debian_7.0/ works (https://www.ovirt.org/documentation/how-to/guest-agent/install-the-guest-agent-in-debian/) That's the error from journalctl -xe: Nov 22 13:23:12 atlassian systemd[1]: Starting oVirt Guest Agent... -- Subject: Unit ovirt-guest-agent.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit ovirt-guest-agent.service has begun starting up. Nov 22 13:23:12 atlassian systemd[1]: Started oVirt Guest Agent. -- Subject: Unit ovirt-guest-agent.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit ovirt-guest-agent.service has finished starting up. -- -- The start-up result is done. Nov 22 13:23:12 atlassian python[21668]: *** stack smashing detected ***: /usr/bin/python terminated Nov 22 13:23:12 atlassian python[21668]: === Backtrace: = Nov 22 13:23:12 atlassian python[21668]: /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7fc78928dbcb] Nov 22 13:23:12 atlassian python[21668]: /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fc7893160e7] Nov 22 13:23:12 atlassian python[21668]: /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7fc7893160b0] Nov 22 13:23:12 atlassian python[21668]: /usr/lib/python2.7/dist-packages/ethtool.so(+0x381d)[0x7fc784dcb81d] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyEval_EvalFrameEx+0x62a)[0x4c38da] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyEval_EvalFrameEx+0x5eef)[0x4c919f] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyEval_EvalFrameEx+0x5eef)[0x4c919f] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyEval_EvalCodeEx+0x255)[0x4c1a45] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python[0x4de44e] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyObject_Call+0x43)[0x4b0273] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python[0x4f452e] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyObject_Call+0x43)[0x4b0273] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python(PyEval_CallObjectWithKeywords+0x30)[0x4cda30] Nov 22 13:23:12 atlassian python[21668]: /usr/bin/python[0x595562] Nov 22 13:23:12 atlassian python[21668]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7464)[0x7fc789ee7464] Nov 22 13:23:12 atlassian python[21668]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x5f)[0x7fc7893059df] Nov 22 13:23:12 atlassian python[21668]: === Memory map: Nov 22 13:23:12 atlassian python[21668]: 0040-006ea000 r-xp fe:03 924288 /usr/bin/python2.7 Nov 22 13:23:12 atlassian python[21668]: 008e9000-008eb000 r--p 002e9000 fe:03 924288 /usr/bin/python2.7 Nov 22 13:23:12 atlassian python[21668]: 008eb000-00962000 rw-p 002eb000 fe:03 924288 /usr/bin/python2.7 Nov 22 13:23:12 atlassian python[21668]: 00962000-00985000 rw-p 00:00 0 Nov 22 13:23:12 atlassian python[21668]: 01667000-0193b000 rw-p 00:00 0 [heap] Nov 22 13:23:12 atlassian python[21668]: 7fc77800-7fc778021000 rw-p 00:00 0 Nov 22 13:23:12 atlassian python[21668]: 7fc778021000-7fc77c00 ---p 00:00 0 Nov 22 13:23:12 atlassian python[21668]: 7fc77f5ed000-7fc77f5f7000 r-xp fe:03 130994 /lib/x86_64-linux-gnu/libnss_files-2.24.so Nov 22 13:23:12 atlassian python[21668]: 7fc77f5f7000-7fc77f7f7000 ---p a000 fe:03 130994 /lib/x86_64-linux-gnu/libnss_files-2.24.so Nov 22 13:23:12 atlassian python[21668]: 7fc77f7f7000-7fc77f7f8000 r--p a000 fe:03 130994 /lib/x86_64-linux-gnu/libnss_files-2.24.so Nov 22 13:23:12 atlassian python[21668]:
Processed: Re: Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install
Processing control commands: > severity -1 normal Bug #858955 [subversion] subversion: Error unable to retrieve any working copy after upgrade/install Severity set to 'normal' from 'grave' -- 858955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install
Control: severity -1 normal On Wed, Mar 29, 2017 at 08:21:23AM -0400, PICCORO McKAY Lenz wrote: > 2017-03-28 23:04 GMT-04:00 James McCoy: > > This discussion is specifically talking about when a 411 status is > returned, not a 413. > > the document only cited 411 error as example, could not cover all the cases > due > there are more, if u understand how to work http 1.1 vs other http 1.X and 2 You're right that it documented the known problems. However, given that 1.8.1 was published almost 4 years ago, I'd expect that common problems would have come up. Given that there's an easy workaround (set http-chunked-requests to off) I'm lowering the severity of the bug. I agree that the general setup you describe of having a proxy is common, but I think the particular proxy or proxy configuration you happen to be interacting with is rather broken. Making it more robust to standard HTTP headers is a much better fix than disabling auto-detection of the correct http-chunked-requests setting for a broader class of users. > well ist not working, i provide not only one, i provide two urls where u come > and get to test.. once with svn 1.6.12 and once with svn 1.7.0 rc1 and theres > no work > > seend to you in private mail: The IP URL is just plain broken. All I get is a 500 response, no matter how I try to run svn. The name-based URL does respond when http-chunked-requests is disabled, but breaks when auto-detection is enabled. I'll discuss this with upstream to see if there's something better than can be done here. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 859019 serious Bug #859019 [python-numpy] new bugfix release available Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 859019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858553: [Pkg-pascal-devel] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
Hi Peter, On 04/01/17 11:24, peter green wrote: > On 31/03/17 19:11, Paul Gevers wrote: >> On Fri, 24 Mar 2017 19:46:23 +0100 Abou Al Montacir >>wrote: >>> OK, I'm going to have a look at the code and guess what it the issue. >>> If I don't manage to get any idea I'll ask upstream. >> I am just curious, are you progressing on this issue? Did you contact >> upstream about it? If so, is the conversation public and can you share a >> link to it? > Umm, this discussion is being sent to a Debian bug report, so of course > it's public. Sorry if I wasn't clear. For the question about the link to the conversation, I meant a possible discussion with upstream. I don't expect upstream to look here. In the Debian bug, I don't remember seeing any further information from Abou or upstream after the note I quoted above. Paul signature.asc Description: OpenPGP digital signature
Bug#858553: [Pkg-pascal-devel] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
On Sat, Apr 01, 2017 at 10:24:27AM +0100, peter green wrote: > On 31/03/17 19:11, Paul Gevers wrote: > > On Fri, 24 Mar 2017 19:46:23 +0100 Abou Al Montacir > >wrote: > > > OK, I'm going to have a look at the code and guess what it the issue. > > > If I don't manage to get any idea I'll ask upstream. > > I am just curious, are you progressing on this issue? Did you contact > > upstream about it? If so, is the conversation public and can you share a > > link to it? > Umm, this discussion is being sent to a Debian bug report, so of course it's > public. I’m guessing Paul is referring to the putative discussion between Abou and upstream, which hasn’t been sent to the bug report. Regards, Stephen signature.asc Description: PGP signature
Bug#857923: golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev
Control: tags -1 +patch pending Just pushed a fix to git repo: https://anonscm.debian.org/cgit/pkg-go/packages/golang-go-dbus.git/commit/?id=7dd07f6 I'll ask sponsor to upload later. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpWsY80J5rWV.pgp Description: PGP signature
Processed: Re: Bug#857923: golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev
Processing control commands: > tags -1 +patch pending Bug #857923 [src:golang-go-dbus] golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev Added tag(s) patch. -- 857923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859262: freezes Orca screen reader
Package: synaptic Version: 0.84.2 Severity: grave Synaptic often freezes the Orca screen reader so that Orca speaks nothing until Synaptic is closed. The same happens on both of my laptops running Debian Stretch. I am blind so I have to use computer using Orca screen reader. It happens wery often that when I e.g click the Reload button in Synaptic, or select Reload from the Synaptic menu, then Orca screen reader stops speaking. Synapticdoes not freeze the whole desktop, just Orca. This problem seems to happen randomly, sometimes it happens sometimes it does not. When Synaptic has finished reloading the package database information Orca may start speaking again, but often it does not. If it does not then I have to close the Synaptic by pressing alt + F4 after which Orca starts to speak again. It also happens sometimes that if I have reloaded repository package database information and click Mark all updades after that then Orca stops speaking. On my second laptop it currently happens almost every time that Orca stops speaking when I click the Mark all updates or select it from the menu. Tkhat also seems to happen randomly, sometimes it happens sometimes not. I have not noticed any problems like that when I have used other applications, this happns only when I am using Synaptic. As I said I have two laptops running Debian Stretch and both have the same problems. Both laptops have been upgraded from Jessie to Stretch. The first laptop was almost clean Jessie installation before it was upgraded to Stretch, it still has wery little apps installed. I am using Gnome desktop. I am blind so it is difficult for me to try to figure out what is wrong. I I have used both espeak and espeak-ng speech synthetisers with Orca screen reader, the same problem exists notmatter which of those is in use. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages synaptic depends on: ii hicolor-icon-theme 0.15-1 ii libapt-inst2.0 1.4~rc2 ii libapt-pkg5.01.4~rc2 ii libatk1.0-0 2.22.0-1 ii libc62.24-9 ii libcairo-gobject21.14.8-1 ii libcairo21.14.8-1 ii libept1.5.0 1.1+nmu3+b1 ii libgcc1 1:6.3.0-11 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgnutls30 3.5.8-3 ii libgtk-3-0 3.22.9-4 ii libpango-1.0-0 1.40.4-1 ii libpangocairo-1.0-0 1.40.4-1 ii libpcre2-8-0 10.22-3 ii libstdc++6 6.3.0-11 ii libvte-2.91-00.46.1-1 ii libx11-6 2:1.6.4-3 ii libxapian30 1.4.3-1 ii policykit-1 0.105-17 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages synaptic recommends: ii libgtk2-perl 2:1.2499-1 ii rarian-compat 0.8.1-6+b1 ii xdg-utils 1.1.1-1 Versions of packages synaptic suggests: ii apt-xapian-index 0.49 pn deborphan pn dwww ii menu 2.1.47+b1 ii software-properties-gtk 0.96.20.2-1 ii tasksel 3.39 -- no debconf information
Bug#859257: libngs-sdk-dev: installs .a files to the incorrect directory
After filing #859260 and #859261, I looked at this again. The attached patch uses DEB_HOST_MULTIARCH instead of DEB_BUILD_GNU_TYPE throughout debian/rules. --- a/debian/rules +++ b/debian/rules @@ -8,9 +8,9 @@ OS := $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) CPU := $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) -BUILDTYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +MULTIARCH := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) # since build-results are not ending up in the proper dir its saver to use "*" instead of "$(CPU)" -SODIR := $(DEBPKGNAME)/$(BUILDTYPE)/$(DEBPKGNAME)/$(OS)/gcc/* +SODIR := $(DEBPKGNAME)/$(MULTIARCH)/$(DEBPKGNAME)/$(OS)/gcc/* build2vers := $(shell pyversions -sv) build3vers := $(shell py3versions -sv) @@ -23,19 +23,19 @@ #dh_auto_clean --sourcedirectory=$(DEBPKGNAME) ; \ dh_auto_clean ; \ fi - rm -rf ngs-java/$(BUILDTYPE) - rm -rf ngs-bam/$(BUILDTYPE) + rm -rf ngs-java/$(MULTIARCH) + rm -rf ngs-bam/$(MULTIARCH) rm -f ngs-bam/Makefile.config rm -f ngs-bam/Makefile.config.install.linux.x86_64.prl rm -f ngs-bam/Makefile.config.linux.x86_64 rm -f ngs-bam/reconfigure - rm -rf $(DEBPKGNAME)/$(BUILDTYPE) + rm -rf $(DEBPKGNAME)/$(MULTIARCH) rm -rf ngs-python/build override_dh_auto_configure: # # that's no standard configure script lacking support of default options \ - ./configure --build=$(BUILDTYPE) --prefix=/usr -- --source=1.7 + ./configure --build=$(MULTIARCH) --prefix=/usr -- --source=1.7 override_dh_auto_build: #dh_auto_build --sourcedirectory=$(DEBPKGNAME) @@ -43,7 +43,7 @@ dh_auto_build --sourcedirectory=$(DEBPKGNAME) # Remove ngs-bam generation, expects ngs-sdk and cannot find a way # to specify it - #cd ngs-bam && LD_LIBRARY_PATH=../$(SODIR)/rel/lib ./configure --build=$(BUILDTYPE) --prefix=/usr --with-ngs-sdk-prefix=../ngs-sdk + #cd ngs-bam && LD_LIBRARY_PATH=../$(SODIR)/rel/lib ./configure --build=$(MULTIARCH) --prefix=/usr --with-ngs-sdk-prefix=../ngs-sdk #dh_auto_build --sourcedirectory=ngs-bam dh_auto_build --sourcedirectory=ngs-java -- JAVAC="javac -source 1.7 -target 1.7" markdown_py -f README.html README.md @@ -52,8 +52,8 @@ make -C $(DEBPKGNAME)/test # Tests of Java binding disabled because need external lib ncbi-vdb, # not available in Debian at this time - #CLASSPATH=../$(BUILDTYPE)/ngs-java/jar/ngs-java.jar LD_LIBRARY_PATH=$(SODIR)/rel/lib:$(LD_LIBRARY_PATH) make -C ngs-java/examples - #CLASSPATH=../$(BUILDTYPE)/ngs-java/jar/ngs-java.jar LD_LIBRARY_PATH=../../$(SODIR)/rel/lib:$(LD_LIBRARY_PATH) make -C ngs-java/examples run_all + #CLASSPATH=../$(MULTIARCH)/ngs-java/jar/ngs-java.jar LD_LIBRARY_PATH=$(SODIR)/rel/lib:$(LD_LIBRARY_PATH) make -C ngs-java/examples + #CLASSPATH=../$(MULTIARCH)/ngs-java/jar/ngs-java.jar LD_LIBRARY_PATH=../../$(SODIR)/rel/lib:$(LD_LIBRARY_PATH) make -C ngs-java/examples run_all override_dh_auto_install: d-shlibmove --commit \ @@ -61,8 +61,8 @@ --devunversioned \ --exclude-a \ --exclude-la \ - --movedev "$(SODIR)/rel/lib/*.a*" usr/lib/$(BUILDTYPE) \ - --movedev "$(SODIR)/rel/ilib/*.a" usr/lib/$(BUILDTYPE) \ + --movedev "$(SODIR)/rel/lib/*.a*" usr/lib/$(MULTIARCH) \ + --movedev "$(SODIR)/rel/ilib/*.a" usr/lib/$(MULTIARCH) \ --movedev ngs-sdk/ngs usr/include \ $(SODIR)/rel/lib/libngs-sdk.so
Bug#857923: Pending fixes for bugs in the golang-go-dbus package
tag 857923 + pending thanks Some bugs in the golang-go-dbus package are closed in revision 7dd07f6d40363926298305d4d0201076228d1b4b in branch 'master' by Roger Shimizu The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-go-dbus.git/commit/?id=7dd07f6 Commit message: debian/control: Update Build-Depends on golang-check.v1-dev Update Build-Depends on golang-check.v1-dev instead of golang-gocheck-dev which is already non-active upstream. Closes: #857923
Processed: Pending fixes for bugs in the golang-go-dbus package
Processing commands for cont...@bugs.debian.org: > tag 857923 + pending Bug #857923 [src:golang-go-dbus] golang-go-dbus: build-depend on obsoleted package golang-gocheck-dev Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 857923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859260: libncbi-vdb-dev: installs .a files to the incorrect directory
Package: libncbi-vdb-dev Version: 2.8.0+dfsg-1 Severity: serious Tags: patch Hi Maintainer Similar to #859257 in libngs-sdk-dev, .a files are installed to the incorrect directory (e.g. /usr/lib/i686-linux-gnu/ instead of /usr/lib/i386-linux-gnu/). The attached patch use s DEB_HOST_MULTIARCH instead of DEB_BUILD_GNU_TYPE to install .a files to the correct multiarch directory. Regards Graham --- a/debian/rules +++ b/debian/rules @@ -10,7 +10,7 @@ OS := $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) CPU := $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) -BUILDTYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +MULTIARCH := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) # since build-results are not ending up in the proper dir its saver to use "*" instead of "$(CPU)" SODIR := $(DEBPKGNAME)/$(DEBPKGNAME)/$(OS)/gcc VDB_ARCH := $(word 1, $(subst -, ,$(DEB_HOST_MULTIARCH))) @@ -25,7 +25,7 @@ if [ -e ngs-sdk/Makefile.config.$(OS).$(CPU) ] ; then \ dh_auto_clean ; \ fi - rm -rf $(DEBPKGNAME)/$(BUILDTYPE) + rm -rf $(DEBPKGNAME)/$(MULTIARCH) override_dh_auto_configure: # that's no standard configure script lacking support of default options @@ -34,7 +34,7 @@ # so we need to go with patches. The options are specified anyway. ln -s /usr/lib/jvm/default-java/include/jni.h libs/ngs-jni ln -s /usr/lib/jvm/default-java/include/linux/jni_md.h libs/ngs-jni - ./configure --build=$(BUILDTYPE) --prefix=/usr --build-prefix=$(CURDIR)/debian/tmp/usr --with-ngs-sdk-prefix=/usr --with-debug --with-ngs-java-prefix=/usr/share/java + ./configure --build=$(MULTIARCH) --prefix=/usr --build-prefix=$(CURDIR)/debian/tmp/usr --with-ngs-sdk-prefix=/usr --with-debug --with-ngs-java-prefix=/usr/share/java # no idea how to convince configure script to use the correct include dir so patching result afterwards sed -i 's?HDF5_INCDIR = /usr/include?&/hdf5/serial?' build/Makefile.config* @@ -61,16 +61,16 @@ --override s/libmbedcrypto0-dev/libmbedtls-dev/ \ --override s/libmbedtls10-dev/libmbedtls-dev/ \ --override s/libmbedx509-0-dev/libmbedtls-dev/ \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/lib/libncbi-ngs-c++.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp-norsrc.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkff.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libktst.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxfs.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxml.a usr/lib/$(BUILDTYPE) \ ---movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libload.a usr/lib/$(BUILDTYPE) \ - --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libtui.a usr/lib/$(BUILDTYPE) \ ---movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libtui_cpp.a usr/lib/$(BUILDTYPE) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/lib/libncbi-ngs-c++.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkapp-norsrc.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkff.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libktst.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxfs.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libkxml.a usr/lib/$(MULTIARCH) \ +--movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libload.a usr/lib/$(MULTIARCH) \ + --movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libtui.a usr/lib/$(MULTIARCH) \ +--movedev debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/ilib/libtui_cpp.a usr/lib/$(MULTIARCH) \ --movedev interfaces usr/include \ debian/tmp/usr/$(DEBPKGNAME)/$(OS)/gcc/*/dbg/lib/libncbi-vdb.so mv debian/libncbi-vdb-dev/usr/include/interfaces debian/libncbi-vdb-dev/usr/include/$(DEBPKGNAME)
Bug#859255: binNMU needed for more R packages.
severity 859255 normal user release.debian@packages.debian.org usertags 859255 binnmu thanks On Sat, 2017-04-01 at 15:24 +0900, Charles Plessy wrote: > Package: release.debian.org > Severity: grave > X-Debbugs-CC: debian-...@lists.debian.org, debian-scie...@lists.debian.org I fixed this last time, but didn't explicitly tell you. release.debian.org bugs are *not* RC, please don't set them as such. The packages that you're asking for binNMUs for might be broken, the release metapackage is not. Regards, Adam
Processed: Re: Bug#859255: binNMU needed for more R packages.
Processing commands for cont...@bugs.debian.org: > severity 859255 normal Bug #859255 [release.debian.org] binNMU needed for more R packages. Severity set to 'normal' from 'grave' > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was a...@adam-barratt.org.uk). > usertags 859255 binnmu There were no usertags set. Usertags are now: binnmu. > thanks Stopping processing here. Please contact me if you need assistance. -- 859255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859259: tigervnc: CVE-2017-7392 CVE-2017-7393 CVE-2017-7394 CVE-2017-7395 CVE-2017-7396
Source: tigervnc Version: 1.7.0+dfsg-6 Severity: grave Tags: patch security upstream Justification: user security hole Hi, the following vulnerabilities were published for tigervnc. CVE-2017-7392[0]: | In TigerVNC 1.7.1 (SSecurityVeNCrypt.cxx | SSecurityVeNCrypt::SSecurityVeNCrypt), an unauthenticated client can | cause a small memory leak in the server. CVE-2017-7393[1]: | In TigerVNC 1.7.1 (VNCSConnectionST.cxx VNCSConnectionST::fence), an | authenticated client can cause a double free, leading to denial of | service or potentially code execution. CVE-2017-7394[2]: | In TigerVNC 1.7.1 (SSecurityPlain.cxx SSecurityPlain::processMsg), | unauthenticated users can crash the server by sending long usernames. CVE-2017-7395[3]: | In TigerVNC 1.7.1 (SMsgReader.cxx SMsgReader::readClientCutText), by | causing an integer overflow, an authenticated client can crash the | server. CVE-2017-7396[4]: | In TigerVNC 1.7.1 (CConnection.cxx CConnection::CConnection), an | unauthenticated client can cause a small memory leak in the server. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-7392 [1] https://security-tracker.debian.org/tracker/CVE-2017-7393 [2] https://security-tracker.debian.org/tracker/CVE-2017-7394 [3] https://security-tracker.debian.org/tracker/CVE-2017-7395 [4] https://security-tracker.debian.org/tracker/CVE-2017-7396 Regards, Salvatore
Processed: reassign 859081 to android-libutils-dev, affects 859081 ...
Processing commands for cont...@bugs.debian.org: > reassign 859081 android-libutils-dev 1:7.0.0+r1-4 Bug #859081 [src:android-platform-frameworks-base] android-platform-frameworks-base: FTBFS: Util.cpp:445:63: error: too few arguments to function 'void utf16_to_utf8 Bug reassigned from package 'src:android-platform-frameworks-base' to 'android-libutils-dev'. No longer marked as found in versions android-platform-frameworks-base/1:7.0.0+r1-3. Ignoring request to alter fixed versions of bug #859081 to the same values previously set Bug #859081 [android-libutils-dev] android-platform-frameworks-base: FTBFS: Util.cpp:445:63: error: too few arguments to function 'void utf16_to_utf8 Marked as found in versions android-platform-system-core/1:7.0.0+r1-4. > affects 859081 android-platform-frameworks-base Bug #859081 [android-libutils-dev] android-platform-frameworks-base: FTBFS: Util.cpp:445:63: error: too few arguments to function 'void utf16_to_utf8 Added indication that 859081 affects android-platform-frameworks-base > retitle 859081 API change in utf16_to_utf8 breaking other packages Bug #859081 [android-libutils-dev] android-platform-frameworks-base: FTBFS: Util.cpp:445:63: error: too few arguments to function 'void utf16_to_utf8 Changed Bug title to 'API change in utf16_to_utf8 breaking other packages' from 'android-platform-frameworks-base: FTBFS: Util.cpp:445:63: error: too few arguments to function 'void utf16_to_utf8'. > thanks Stopping processing here. Please contact me if you need assistance. -- 859081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858553: [Pkg-pascal-devel] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
On 31/03/17 19:11, Paul Gevers wrote: Hi Abou, On Fri, 24 Mar 2017 19:46:23 +0100 Abou Al Montacirwrote: OK, I'm going to have a look at the code and guess what it the issue. If I don't manage to get any idea I'll ask upstream. I am just curious, are you progressing on this issue? Did you contact upstream about it? If so, is the conversation public and can you share a link to it? Umm, this discussion is being sent to a Debian bug report, so of course it's public. Of course I want to help, but I have no idea where to start or what to do. Paul
Bug#859101: marked as pending
tag 859101 pending thanks Hello, Bug #859101 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-samba/samba.git/commit/?id=0a7e378 --- commit 0a7e37892154dbef5c256ed17a0ea8b4b0abac00 Author: Mathieu ParentDate: Sat Apr 1 11:10:35 2017 +0200 Re-release 2:4.2.14+dfsg-0+deb8u5 diff --git a/debian/changelog b/debian/changelog index 57b2ce1..7c157ce 100644 --- a/debian/changelog +++ b/debian/changelog @@ -21,8 +21,10 @@ samba (2:4.2.14+dfsg-0+deb8u5) jessie-security; urgency=high - selftest: add content to files created during shadow_copy2 test - selftest: check file readability in shadow_copy2 test - selftest: test listing directories inside snapshots + * Fix `net ads join` freeze when run a second time (Closes: #859101) since 4.2 +- libads: Fix deadlock when re-joining a domain and updating keytab - -- Mathieu Parent Thu, 30 Mar 2017 22:15:40 +0200 + -- Mathieu Parent Sat, 01 Apr 2017 11:10:22 +0200 samba (2:4.2.14+dfsg-0+deb8u4) jessie-security; urgency=high
Processed: Bug#859101 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 859101 pending Bug #859101 [samba-common-bin] regression: net: security update makes `net ads join` freeze when run a second time Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 859101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen
Processing commands for cont...@bugs.debian.org: > reopen 858215 Bug #858215 {Done: David Rabel} [aodh-api] aodh-api: Missing dependency to net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions keystone/2:10.0.0-7 and aodh/3.0.0-3. > reopen 858704 Bug #858704 {Done: David Rabel } [manila-api] manila-api: Missing dependency net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions manila/1:3.0.0-3. > reopen 858711 Bug #858711 {Done: David Rabel } [sahara-api] sahara-api: Missing dependency net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions sahara/1:5.0.0-3. > reopen 858707 Bug #858707 {Done: David Rabel } [murano-api] murano-api: Missing dependency net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions murano/1:3.0.0-4. > reopen 858714 Bug #858714 {Done: David Rabel } [zaqar-server] zaqar-server: Missing dependency net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions zaqar/3.0.0-3. > reopen 858697 Bug #858697 {Done: David Rabel } [gnocchi-api] gnocchi-api: Missing dependency net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions gnocchi/3.0.4-2. > reopen 858215 Bug #858215 [aodh-api] aodh-api: Missing dependency to net-tools Bug 858215 is not marked as done; doing nothing. > reopen 858219 Bug #858219 {Done: David Rabel } [barbican-api] barbican-api: Missing dependency to net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions barbican/1:3.0.0-2. > reopen 858123 Bug #858123 {Done: David Rabel } [glance-api] glance-api: Automatic installation/configuration via debconf fails without net-tools 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions glance/2:13.0.0-3. > End of message, stopping processing here. Please contact me if you need assistance. -- 858123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858123 858215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858215 858219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858219 858697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858697 858704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858704 858707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858707 858711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858711 858714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859257: libngs-sdk-dev: installs .a files to the incorrect directory
Package: libngs-sdk-dev Version: 1.2.3-3 Severity: serious Tags: patch Hi Maintainer .a files are installed to the incorrect directory (e.g. /usr/lib/i686-linux-gnu/ instead of /usr/lib/i386-linux-gnu/) , as can be seen in the following excerpt from a recent buildlog [1]: libngs-sdk-dev_1.3.0-1_i386.deb ─── new debian package, version 2.0. size 99736 bytes: control archive=3479 bytes. 1035 bytes,24 lines control 6887 bytes,98 lines md5sums Package: libngs-sdk-dev Source: ngs-sdk Version: 1.3.0-1 Architecture: i386 ... drwxr-xr-x root/root 0 2016-11-09 07:54 ./usr/lib/ drwxr-xr-x root/root 0 2016-11-09 07:54 ./usr/lib/i386-linux-gnu/ lrwxrwxrwx root/root 0 2016-11-09 07:54 ./usr/lib/i386-linux-gnu/libngs-sdk.so -> libngs-sdk.so.1 drwxr-xr-x root/root 0 2016-11-09 07:54 ./usr/lib/i686-linux-gnu/ lrwxrwxrwx root/root 0 2016-11-09 07:54 ./usr/lib/i686-linux-gnu/libngs-adapt-c++-static.a -> libngs-adapt-c++.a This causes at least sra-sdk to FTBFS on i386 [2] with the following error: checking for ngs-sdk package... includes... /usr libraries... checking /usr/lib/i386-linux-gnu/libngs-c++.a checking /usr/lib32/libngs-c++.a checking /usr/linux/gcc/i386/dbg/lib/libngs-c++.a no libraries... checking /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/lib/i386-linux-gnu/libngs-c++.a checking /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/lib32/libngs-c++.a checking /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/linux/gcc/i386/dbg/lib/libngs-c++.a no not found /«BUILDDIR»/sra-sdk-2.8.1-2+dfsg/debian/tmp/usr/ngs-sdk libraries... checking /usr/lib/i386-linux-gnu/libngs-c++.a checking /usr/lib32/libngs-c++.a checking /usr/linux/gcc/i386/dbg/lib/libngs-c++.a no ngs-sdk: includes: /usr/include; libs: ; ilibs: not needed configure: error: required ngs-sdk package not found. debian/rules:24: recipe for target 'override_dh_auto_configure' failed The following patch lets the .a files be installed to the correct multiarch directory: --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,7 @@ OS := $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) CPU := $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) BUILDTYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +MULTIARCH := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) # since build-results are not ending up in the proper dir its saver to use "*" instead of "$(CPU)" SODIR := $(DEBPKGNAME)/$(BUILDTYPE)/$(DEBPKGNAME)/$(OS)/gcc/* @@ -61,8 +62,8 @@ --devunversioned \ --exclude-a \ --exclude-la \ ---movedev "$(SODIR)/rel/lib/*.a*" usr/lib/$(BUILDTYPE) \ ---movedev "$(SODIR)/rel/ilib/*.a" usr/lib/$(BUILDTYPE) \ +--movedev "$(SODIR)/rel/lib/*.a*" usr/lib/$(MULTIARCH) \ +--movedev "$(SODIR)/rel/ilib/*.a" usr/lib/$(MULTIARCH) \ --movedev ngs-sdk/ngs usr/include \ $(SODIR)/rel/lib/libngs-sdk.so Regards Graham [1] https://buildd.debian.org/status/fetch.php?pkg=ngs-sdk=i386=1.3.0-1=1478684848=0 [2] https://buildd.debian.org/status/fetch.php?pkg=sra-sdk=i386=2.8.1-2%2Bdfsg-1=1485249305=0
Processed: Re: Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)
Processing commands for cont...@bugs.debian.org: > severity 859217 important Bug #859217 [nageru] nageru: just segfaults Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 859217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)
severity 859217 important thanks On Sat, Apr 01, 2017 at 02:34:13AM +0300, Adrian Bunk wrote: > I am also getting segfaults when trying to start Nageru on my computer > (old AMD card). > > Whether Nageru is ever expected to work on my or Antonios computer is > one thing. > > But failing with a segfault is clearly a bug in the error handling. > > It is fine to display a window "Sorry, your hardware is not supported", > segfaulting just causes user confusion. [1] Hi, While I agree failing to show a friendly message is a bug, I'm not sure whether it fits the definition of grave (“makes the package in question unusable or mostly so”). I'll try to investigate how easy it is to show something friendlier -- I honestly don't know, and it would probably require poking a bit around into Qt implementation details. At that point, it will be up to the release team to see if they will accept an upload to stretch to fix this bug. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#859255: binNMU needed for more R packages.
Package: release.debian.org Severity: grave X-Debbugs-CC: debian-...@lists.debian.org, debian-scie...@lists.debian.org Hello again, as a follow-up to #858183, I looked at which other R Bioconductor packages were broken by R 3.3.3-1, and it seems that the previous round of binNMUs did not repair some of them. Can you make the followig binNMUs ? nmu r-bioc-rsamtools_1.26.1-2 . ANY . -m "Rebuild for R 3.3.3." nmu r-bioc-shortread_1.32.0-1 . ANY . -m "Rebuild for R 3.3.3." nmu r-bioc-variantannotation_1.20.2-1 . ANY . -m "Rebuild for R 3.3.3." nmu r-bioc-genomicalignments_1.10.0-1 . ANY . -m "Rebuild for R 3.3.3." Note to debian-science: there are also R CRAN packages that fail with R 3.3.3, (r-cran-lubridate, r-cran-spam), but I am not yet sure if a binNMU is enough. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
Bug#857343: closed by Markus Koschany <a...@debian.org> (Bug#857343: fixed in logback 1:1.1.9-2)
The POC is a simple Eclipse java project. UnsafeReceiver will open a ServerSocketReceiver on port and wait forever. Injector will then open a client Socket to the ServerSocketReceiver and serialize a Calculator instance through the wire. Calculator implements ILoggingEvent to prevent ClassCastException on deserialization but Logback won't check more and getLoggerName() is called. In this case, the gnome calculator is executed. Regards, Fabrice Le 31/03/2017 à 14:10, Markus Koschany a écrit : You could also attach the POC to this bug report. The vulnerability is publicly known by now anyway. Markus poc_logback.tar.gz Description: GNU Zip compressed data