Bug#899439: Bug #899439 in acmetool marked as pending
Control: tag -1 pending Hello, Bug #899439 in acmetool reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/letsencrypt-team/acmetool/commit/0e21a13bb9664445b779e8a67df5c164cea4e393 Update Maintainer address Closes: #899439 Thanks: Lukas Schwaighofer (this message was generated automatically) -- Greetings https://bugs.debian.org/899439
Processed: Bug #899439 in acmetool marked as pending
Processing control commands: > tag -1 pending Bug #899439 [src:acmetool] acmetool: Invalid maintainer address letsencrypt-de...@lists.alioth.debian.org Added tag(s) pending. -- 899439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902469: marked as done (golang-gopkg-hlandau-easyconfig.v1: FTBFS in buster/sid (failing tests))
Your message dated Sat, 17 Nov 2018 05:34:46 + with message-id and subject line Bug#902469: fixed in golang-gopkg-hlandau-easyconfig.v1 1.0.17-1 has caused the Debian Bug report #902469, regarding golang-gopkg-hlandau-easyconfig.v1: FTBFS in buster/sid (failing tests) 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.) -- 902469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-gopkg-hlandau-easyconfig.v1 Version: 1.0.15-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 gopkg.in/hlandau/easyconfig.v1 gopkg.in/hlandau/easyconfig.v1/adaptconf gopkg.in/hlandau/easyconfig.v1/adaptenv gopkg.in/hlandau/easyconfig.v1/adaptflag gopkg.in/hlandau/easyconfig.v1/cflag gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual gopkg.in/hlandau/configurable.v1 github.com/BurntSushi/toml gopkg.in/hlandau/easyconfig.v1/cflag gopkg.in/hlandau/svcutils.v1/exepath gopkg.in/hlandau/easyconfig.v1/adaptconf gopkg.in/hlandau/easyconfig.v1/adaptenv github.com/ogier/pflag github.com/alecthomas/units gopkg.in/alecthomas/kingpin.v2 gopkg.in/hlandau/easyconfig.v1/adaptflag # gopkg.in/hlandau/easyconfig.v1/adaptflag src/gopkg.in/hlandau/easyconfig.v1/adaptflag/adaptflag.go:227:22: cannot use byte(r) (type byte) as type rune in argument to fl.Short gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual dh_auto_build: cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 gopkg.in/hlandau/easyconfig.v1 gopkg.in/hlandau/easyconfig.v1/adaptconf gopkg.in/hlandau/easyconfig.v1/adaptenv gopkg.in/hlandau/easyconfig.v1/adaptflag gopkg.in/hlandau/easyconfig.v1/cflag gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual returned exit code 2 debian/rules:7: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The above is how the build ends in my autobuilder and it's not necessarily the relevant part. The failure is not, however, related to using dpkg-buildpackage -A, as it also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-hlandau-easyconfig.v1.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks. --- End Message --- --- Begin Message --- Source: golang-gopkg-hlandau-easyconfig.v1 Source-Version: 1.0.17-1 We believe that the bug you reported is fixed in the latest version of golang-gopkg-hlandau-easyconfig.v1, 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 902...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Colberg (supplier of updated golang-gopkg-hlandau-easyconfig.v1 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, 16 Nov 2018 23:57:38 -0500 Source: golang-gopkg-hlandau-easyconfig.v1 Binary: golang-gopkg-hlandau-easyconfig.v1-dev Architecture: source Version: 1.0.17-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Peter Colberg Description: golang-gopkg-hlandau-easyconfig.v1-dev - Go package with easy bindings for configurable Closes: 902469 Changes:
Bug#910943: libhtml-tidy-perl: Please upload pending 1.60-2 and coordinate with libtidy transition
On Fri, 16 Nov 2018 10:43:58 -0500, Boyuan Yang wrote: > > > What do you think would be the proper solution? I suppose we upload > > > a tidy-html5 2:5.6.0-9 to drop the reverted part since the next major > > > version of tidy-html5 will adapt such behaviour change anyway. > > Right, I think that makes sense. > I have made the 2:5.6.0-9 upload and the autopkgtest is passing. Thanks. Let's hope this fix lasts for some time now :) 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 VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Cássia Eller: O Segundo Sol signature.asc Description: Digital Signature
Bug#913116: Needs to depend on chromium-sandbox
On Fri, 16 Nov 2018 10:20:07 +0100 Bastian Blank wrote: > Debian does not support unprivileged user namespaces, so chromium needs > to depend on -sandbox to get a working package. Should we, perhaps, support unprivileged user namespaces? Or, at least, a means of granting targeted permission to use such namespaces without being full root?
Processed: found 913915 in 5.4.1~repack-1
Processing commands for cont...@bugs.debian.org: > found 913915 5.4.1~repack-1 Bug #913915 [src:juce] juce: VST2 support has been dropped Marked as found in versions juce/5.4.1~repack-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 913915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 911956
Processing commands for cont...@bugs.debian.org: > affects 911956 src:dcm2niix Bug #911956 [src:yaml-cpp] [src:yaml-cpp] FTBFS with boost1.67 Added indication that 911956 affects src:dcm2niix > thanks Stopping processing here. Please contact me if you need assistance. -- 911956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 911956
Processing commands for cont...@bugs.debian.org: > tags 911956 + ftbfs buster sid Bug #911956 [src:yaml-cpp] [src:yaml-cpp] FTBFS with boost1.67 Added tag(s) ftbfs, buster, and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 911956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 911956 is serious
Processing commands for cont...@bugs.debian.org: > severity 911956 serious Bug #911956 [src:yaml-cpp] [src:yaml-cpp] FTBFS with boost1.67 Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 911956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913840: marked as done (jackson-dataformat-xml FTBFS with libjaxb-api-java 2.3.1)
Your message dated Fri, 16 Nov 2018 22:04:53 + with message-id and subject line Bug#913840: fixed in jackson-dataformat-xml 2.9.7-2 has caused the Debian Bug report #913840, regarding jackson-dataformat-xml FTBFS with libjaxb-api-java 2.3.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 913840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jackson-dataformat-xml Version: 2.9.7-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jackson-dataformat-xml.html ... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 16.337 s [INFO] Finished at: 2018-11-15T06:53:22-12:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default-cli) on project jackson-dataformat-xml: MavenReportException: Error while generating Javadoc: artifact resolver problem - Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact javax.xml.bind:jaxb-api:jar:2.3.0 has not been downloaded from it before. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/jackson-dataformat-xml-2.9.7 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/1st/jackson-dataformat-xml-2.9.7/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/jackson-dataformat-xml-2.9.7/debian -Dmaven.repo.local=/build/1st/jackson-dataformat-xml-2.9.7/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make: *** [debian/rules:4: build] Error 2 --- End Message --- --- Begin Message --- Source: jackson-dataformat-xml Source-Version: 2.9.7-2 We believe that the bug you reported is fixed in the latest version of jackson-dataformat-xml, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated jackson-dataformat-xml 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, 16 Nov 2018 22:36:52 +0100 Source: jackson-dataformat-xml Binary: libjackson2-dataformat-xml-java libjackson2-dataformat-xml-java-doc Architecture: source Version: 2.9.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: libjackson2-dataformat-xml-java - fast and powerful JSON library for Java -- XML dataformat libjackson2-dataformat-xml-java-doc - Documentation for Jackson-dataformat-XML Closes: 913840 Changes: jackson-dataformat-xml (2.9.7-2) unstable; urgency=medium . * Fix FTBFS by changing the jaxb api version to debian in javadoc-classpath.patch. Thanks to Adrian Bunk for the report. (Closes: #913840) Checksums-Sha1: 21ce161bece072881bab8a86471042625006165b 2887 jackson-dataformat-xml_2.9.7-2.dsc ea90414972da155e2958b077b49827bb3f5380d1 4668 jackson-dataformat-xml_2.9.7-2.debian.tar.xz 680b7b654c76e69a3e31e15c871afaff88099401 16436 jackson-dataformat-xml_2.9.7-2_amd64.buildinfo Checksums-Sha256: b8f3e412afc975386318b7250be2b3847c894c22df3fda3cbcfe6fb0e0adb54a 2887 jackson-dataformat-xml_2.9.7-2.dsc 90b7db2364b5f576d6324c4e94f842e90b2366456e2c5795a3e2a3a38b133c5b 4668
Bug#913916: grub-efi-amd64: UEFI boot option removed after update to grub2 2.02~beta3-5+deb9u1
Package: grub-efi-amd64 Version: 2.02~beta3-5+deb9u1 Severity: critical After updating grub2 in Debian stable to 2.02~beta3-5+deb9u1 the UEFI boot option was removed on my Dell Latitude 5480. After rebooting I was greeted with "No bootable devices found". In the setup utility (reached by pressing F2) the UEFI boot sequence was empty. I could fix the problem by adding a new boot option, selecting the file EFI/debian/grubx64.efi. I could reproduce this by downgrading the installed grub2 packages (grub2-common, grub-common, grub-efi-amd64, grub-efi-amd64-bin) to 2.02~beta3-5, making sure the boot option is there, and updating the packages to 2.02~beta3-5+deb9u1 again. After the update the boot option is gone. Just rebooting with either of the versions does not remove the boot option. There is no indication during the update that something went wrong: Setting up grub-efi-amd64 (2.02~beta3-5+deb9u1) ... Installing for x86_64-efi platform. Installation finished. No error reported. Generating grub configuration file ... Found background image: .background_cache.png Found linux image: /boot/vmlinuz-4.9.0-8-amd64 Found initrd image: /boot/initrd.img-4.9.0-8-amd64 Found linux image: /boot/vmlinuz-4.9.0-7-amd64 Found initrd image: /boot/initrd.img-4.9.0-7-amd64 Adding boot menu entry for EFI firmware configuration done Best, Tobias
Bug#871105: Status of debian-faq
Hi Joost, are you still planning to do an upload of debian-faq? Or are any other members of the maintaining team planning an upload? Regards, Tobias signature.asc Description: OpenPGP digital signature
Processed: Bug #913840 in jackson-dataformat-xml marked as pending
Processing control commands: > tag -1 pending Bug #913840 [src:jackson-dataformat-xml] jackson-dataformat-xml FTBFS with libjaxb-api-java 2.3.1 Added tag(s) pending. -- 913840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913840: Bug #913840 in jackson-dataformat-xml marked as pending
Control: tag -1 pending Hello, Bug #913840 in jackson-dataformat-xml reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/jackson-dataformat-xml/commit/eb241ca1e988c0c4be200f74f35f71bfc46b986e Fix FTBFS by changing the jaxb api version to debian in javadoc-classpath.patch. Closes: #913840 Thanks: Adrian Bunk for the report. (this message was generated automatically) -- Greetings https://bugs.debian.org/913840
Bug#913846: qtox: Uninstallable on at least amd64 (might need binNMU against recent ffmpeg)
Control: reassign -1 release.debian.org Control: severity -1 normal Control: retitle -1 nmu: qtox_1.15.0-1 On Thu, Nov 15, 2018 at 10:57:57PM +0100, Axel Beckert wrote: > Package: qtox > Version: 1.15.0-1 > Severity: serious > > qtox is currently uninstallable on at least amd64 due its dependency on > libavdevice57 (still available, but seems to have been replaced by > libavdevice58 and likely will be removed soon) which again depends on > the no more available libsndio6.1. > > A binNMU against the most recent ffmpeg libraries might already help. >... Let's request that, it is not a surprise when some transition was missed that happened during the 5 months where this binary package was in NEW. nmu qtox_1.15.0-1 . amd64 . unstable . -m "Rebuild on current unstable" 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
Processed: Re: Bug#913846: qtox: Uninstallable on at least amd64 (might need binNMU against recent ffmpeg)
Processing control commands: > reassign -1 release.debian.org Bug #913846 [qtox] qtox: Uninstallable on at least amd64 (might need binNMU against recent ffmpeg) Bug reassigned from package 'qtox' to 'release.debian.org'. No longer marked as found in versions qtox/1.15.0-1. Ignoring request to alter fixed versions of bug #913846 to the same values previously set > severity -1 normal Bug #913846 [release.debian.org] qtox: Uninstallable on at least amd64 (might need binNMU against recent ffmpeg) Severity set to 'normal' from 'serious' > retitle -1 nmu: qtox_1.15.0-1 Bug #913846 [release.debian.org] qtox: Uninstallable on at least amd64 (might need binNMU against recent ffmpeg) Changed Bug title to 'nmu: qtox_1.15.0-1' from 'qtox: Uninstallable on at least amd64 (might need binNMU against recent ffmpeg)'. -- 913846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913915: juce: VST2 support has been dropped
Source: juce Severity: serious Tags: upstream Justification: makes rdeps FTBFS juce-5.4 has dropped the built-in VST2 support and now depends on the Steinberg SDK (which - apart from being proprietary and non-free - is no longer available) for download at all. This has severe implications on the the usability of JUCE (as it can no longer be used to build VST2 plugins). Until there is a proper solution for the problem, i suggest to keep JUCE from migrating to testing. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Debian Bugs #913346
Processing commands for cont...@bugs.debian.org: > reassign 913346 sane-backends Bug #913346 [libsane1] libsane1: Cannot update libsane1 Warning: Unknown package 'libsane1' Bug reassigned from package 'libsane1' to 'sane-backends'. No longer marked as found in versions sane-backends/1.0.27-3. Ignoring request to alter fixed versions of bug #913346 to the same values previously set > -- Stopping processing here. Please contact me if you need assistance. -- 913346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913912: libphp-phpmailer: CVE-2018-19296
Source: libphp-phpmailer Version: 5.2.14+dfsg-2.3 Severity: grave Tags: patch security upstream Hi, The following vulnerability was published for libphp-phpmailer. CVE-2018-19296[0]: | PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object | injection attack. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-19296 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19296 [1] https://github.com/PHPMailer/PHPMailer/commit/f1231a9771505f4f34da060390d82eadb8448271 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: ceph: FTBFS on i386 and mipsel (regression)
Processing control commands: > affects -1 release.debian.org,security.debian.org Bug #913909 [src:ceph] ceph: FTBFS on i386 and mipsel (regression) Added indication that 913909 affects release.debian.org and security.debian.org -- 913909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 913896 in 1.9.5-1, tagging 913896 ...
Processing commands for cont...@bugs.debian.org: > found 913896 1.9.5-1 Bug #913896 [src:libbson] CVE-2018-16790 Marked as found in versions libbson/1.9.5-1. > tags 913896 + upstream Bug #913896 [src:libbson] CVE-2018-16790 Added tag(s) upstream. > forwarded 913896 https://jira.mongodb.org/browse/CDRIVER-2819 Bug #913896 [src:libbson] CVE-2018-16790 Set Bug forwarded-to-address to 'https://jira.mongodb.org/browse/CDRIVER-2819'. > thanks Stopping processing here. Please contact me if you need assistance. -- 913896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888383: Bug #888383 in kodi marked as pending
Control: tag -1 pending Hello, Bug #888383 in kodi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/kodi/commit/af19291f3db58def78d845bd4556d9d6fc4c8c14 Upstream fixes for new ffmpeg: debian/patches/19f28e88a5dfed82e9844f69210f7c045f18ca8e.patch debian/patches/c7e2acc1b2ee781af6e14d80da0edd0aa23bdf03.patch Closes: #888383, #912994 (this message was generated automatically) -- Greetings https://bugs.debian.org/888383
Processed: Bug #888383 in kodi marked as pending
Processing control commands: > tag -1 pending Bug #888383 [src:kodi] kodi: FTBFS with FFmpeg 4.0 Bug #913068 [src:kodi] [kodi] Please rebuild kodi against newer libavcodec Added tag(s) pending. Added tag(s) pending. -- 888383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888383 913068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912239: marked as done (ruby-httparty FTBFS: SSL_CTX_use_certificate: ee key too small)
Your message dated Fri, 16 Nov 2018 17:23:12 +
with message-id
and subject line Bug#912239: fixed in ruby-httparty 0.16.2+dfsg1-2
has caused the Debian Bug report #912239,
regarding ruby-httparty FTBFS: SSL_CTX_use_certificate: ee key too small
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.)
--
912239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-httparty
Version: 0.16.2+dfsg1-1
Severity: serious
Tags: ftbfs
ruby-httparty fails to build from source in unstable:
|
GEM_PATH=debian/ruby-httparty/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -e gem\ \"httparty\"
|
|
┌──┐
| │ Run tests for ruby2.5 from debian/ruby-tests.rake
│
|
└──┘
|
| RUBYLIB=/<>/debian/ruby-httparty/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-httparty/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
| /usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*/\*_spec.rb
| /<>/spec/httparty/request/body_spec.rb:3: warning: setting
Encoding.default_external
| Run options: include {:focus=>true}
|
| All examples were filtered out; ignoring {:focus=>true}
|
| Randomized with seed 46039
|
*.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
F#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
F#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
Bug#913005: ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack
Hi Salvatore et al., > Source: ruby-rack […] > CVE-2018-16471[0]: > Possible XSS vulnerability in Rack Security team, like ruby-i18n, I would be more than happy to prepare and upload a stable security upload of this package when addressing it in jessie LTS. Please let me know and I will come back with a debdiff. Ruby team, again, I could easily upload to sid at the same time. Let me know here too. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#913896: CVE-2018-16790
Source: libbson Severity: grave Tags: security Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16790 Cheers, Moritz
Bug#913505: marked as done (hfst-ospell FTBS with ICU 63.1)
Your message dated Fri, 16 Nov 2018 15:53:34 + with message-id and subject line Bug#913505: fixed in hfst-ospell 0.5.0-2 has caused the Debian Bug report #913505, regarding hfst-ospell FTBS with ICU 63.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 913505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hfst-ospell Source-Version: 0.5.0-1 Severity: important Tags: patch Usertags: icu63 Dear Maintainer, ICU 63.1 recently released, packaged and uploaded to experimental. Its transition is going to start soon. However your package fails to build with this version. I attach a patch which fixes the problem. Please check if it works with the version in Sid and upload the package when it's feasible for you. Thanks, Laszlo/GCS From a949408067fa783b0cfc942baf55cc69b743adc5 Mon Sep 17 00:00:00 2001 From: Tino Didriksen Date: Thu, 20 Sep 2018 09:54:23 + Subject: [PATCH] ICU is namespaced in newer versions (fixes #42) --- office.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/office.cc b/office.cc index ecb63c8..822e55a 100644 --- a/office.cc +++ b/office.cc @@ -49,6 +49,7 @@ #include #include #include +using namespace icu; #include "ZHfstOspeller.h" --- End Message --- --- Begin Message --- Source: hfst-ospell Source-Version: 0.5.0-2 We believe that the bug you reported is fixed in the latest version of hfst-ospell, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated hfst-ospell 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: Fri, 16 Nov 2018 20:35:57 +0530 Source: hfst-ospell Binary: hfst-ospell libhfstospell10 hfst-ospell-dev Architecture: source amd64 Version: 0.5.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Kartik Mistry Description: hfst-ospell - Spell checker library and tool based on HFST hfst-ospell-dev - HFST spell checker development files libhfstospell10 - HFST spell checker runtime libraries Closes: 913505 Changes: hfst-ospell (0.5.0-2) unstable; urgency=medium . * Added patch to fix FTBS with ICU 63.1 (Closes: #913505). Checksums-Sha1: 96bae943487674ace049f321f5c2c1d5b882f2bc 2184 hfst-ospell_0.5.0-2.dsc fe6414d456bf64112161e03a5472f24318195214 137916 hfst-ospell_0.5.0.orig.tar.bz2 d0eb3281eb7531493bf78f0272265299b2eaa32e 3340 hfst-ospell_0.5.0-2.debian.tar.xz b39c7d1977bc26cd8b869439ee624f2437be4265 432468 hfst-ospell-dbgsym_0.5.0-2_amd64.deb 1c9004b45d9860279c387e647371c2fcf9b52bf2 25300 hfst-ospell-dev_0.5.0-2_amd64.deb a8f8fb450fc808b08c6ede17a237b03789ee287d 7863 hfst-ospell_0.5.0-2_amd64.buildinfo 13a573b9da41cde7f8e59f4b9f1e459a19a3b8fc 43488 hfst-ospell_0.5.0-2_amd64.deb e41508f8a7501891de5999c2608bb21bf52065db 1172136 libhfstospell10-dbgsym_0.5.0-2_amd64.deb ac7401681a909b75296691e140b30ca869bb07ba 79144 libhfstospell10_0.5.0-2_amd64.deb Checksums-Sha256: 23fd969958dffdf77b6569cd64f62b62fdc329c3c92969d450f7be34b1bd7fb8 2184 hfst-ospell_0.5.0-2.dsc 5bbb6b05a93250e10889387045711286d6c4433014151e7b2f63541077aef8b2 137916 hfst-ospell_0.5.0.orig.tar.bz2 305e3714a1ff2b4dc5e2449b0fedd854bcf774353ae5cb658127f7dd2bbbdf1e 3340 hfst-ospell_0.5.0-2.debian.tar.xz fc9a5fc543802dd787f48fed86839fba3ac6abe1830c615aaa4eb29b845bfc91 432468 hfst-ospell-dbgsym_0.5.0-2_amd64.deb c28d2ab452edc49f53d188cc311a291a909644059803e5a74ea3bc4e4e27add9 25300 hfst-ospell-dev_0.5.0-2_amd64.deb 496289d25ea8b324b20b725b951fce017611c0eb60a3344cbb73e75f99c18ff3 7863 hfst-ospell_0.5.0-2_amd64.buildinfo f1d42912d4be6c3cf80e967d29990c91e54c1b0dd49803a76eac3322b94643a9 43488 hfst-ospell_0.5.0-2_amd64.deb 82e77407022bab218b71a71ac5fe793008f59eb7cca6de2c8a214f0b89b348a4 1172136 libhfstospell10-dbgsym_0.5.0-2_amd64.deb 4c0de0d5a28e459f5e8c6bf2cb9016b063cef74341c357f4a9d47677a8fb2e2b 79144 libhfstospell10_0.5.0-2_amd64.deb Files: 088d001baa27a523c2869340dd0dae42 2184 science optional hfst-ospell_0.5.0-2.dsc 1bc12ae8dc09d6197918054218b5ea3c 137916 science
Bug#910943: libhtml-tidy-perl: Please upload pending 1.60-2 and coordinate with libtidy transition
Hi, gregor herrmann 于2018年11月15日周四 下午4:35写道： > > On Thu, 15 Nov 2018 16:20:48 -0500, Boyuan Yang wrote: > > > > JFTR: tidy-html5 2:5.6.0-7 broke libhtml-tidy-perl's test suite > > > again: > > > https://ci.debian.net/packages/libh/libhtml-tidy-perl/testing/amd64/ > > > > > > I already uploaded a fix (a small change to the test suite to adjust > > > to the changed ouput), so there's nothing left to be done for now. > > > > However I have already uploaded tidy-html5 2:5.6.0-8 to revert the part > > that caused the autopkgtest regression -- it seems that autopkgtest will > > be broken again with current status lol > > Oh, the fun continues :) > > > What do you think would be the proper solution? I suppose we upload > > a tidy-html5 2:5.6.0-9 to drop the reverted part since the next major > > version of tidy-html5 will adapt such behaviour change anyway. > > Right, I think that makes sense. I have made the 2:5.6.0-9 upload and the autopkgtest is passing. Cheers, Boyuan
Bug#908827: marked as done (mesa: Fails to build on Stretch, missing min build dep)
Your message dated Fri, 16 Nov 2018 15:04:16 + with message-id and subject line Bug#908827: fixed in mesa 18.2.4-1 has caused the Debian Bug report #908827, regarding mesa: Fails to build on Stretch, missing min build dep 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.) -- 908827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 18.2.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, Mesa 18.2.0-1 fails to build on Stretch, I can't find the relevant bug report on freedesktop.org but now it requires xcb-proto >= 1.13. After compiling and installing xcb-proto and libxcb 1.13-1 from unstable, the package was built succesfully. -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-rc2-test1 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: mesa Source-Version: 18.2.4-1 We believe that the bug you reported is fixed in the latest version of mesa, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated mesa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Nov 2018 11:20:08 +0200 Source: mesa Binary: libxatracker2 libxatracker-dev libd3dadapter9-mesa libd3dadapter9-mesa-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers mesa-opencl-icd Architecture: source amd64 Version: 18.2.4-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libd3dadapter9-mesa - state-tracker for Direct3D9 libd3dadapter9-mesa-dev - state-tracker for Direct3D9 -- development files libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library libegl1-mesa - transitional dummy package libegl1-mesa-dev - free implementation of the EGL API -- development files libgbm-dev - generic buffer management API -- development files libgbm1- generic buffer management API -- runtime libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development files libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules libgl1-mesa-glx - transitional dummy package libglapi-mesa - free implementation of the GL API -- shared library libgles2-mesa - transitional dummy package libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- development files libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library libosmesa6 - Mesa Off-screen rendering extension libosmesa6-dev - Mesa Off-screen rendering extension -- development files libwayland-egl1-mesa - transitional dummy package libxatracker-dev - X acceleration library -- development files libxatracker2 - X acceleration library -- runtime mesa-common-dev - Developer documentation for Mesa mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime mesa-va-drivers - Mesa VA-API video acceleration drivers mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers mesa-vulkan-drivers - Mesa Vulkan graphics drivers Closes: 907136 908827 909720 Changes: mesa (18.2.4-1) experimental; urgency=medium . [ Andreas Boll ] * New upstream release. - vulkan: Disable randr lease for libxcb < 1.13 (Closes: #908827, #909720). * Drop version from build-deps libxcb-dri3-dev and libxcb-present-dev. * Bump libdrm-dev dependency to 2.4.92. * Enable building etnaviv and imx on arm64 (Closes: #907136). . [ Timo Aaltonen ] *
Bug#913877: [pkg-netfilter-team] Bug#913877: iptables 1.8.2: ERROR when adding REJECT target to custom chains
On 11/16/18 1:18 PM, Amos Jeffries wrote: > My kernel version is 3.16.0-4-amd64. > This kernel is very very old. First thing to do is to upgrade your kernel to something modern. Is not related to the hardware. Both x_tables and nf_tables kernel subsystem received severe updates since 3.16. By mixing modern userspace components with old kernelside modules you are exposed to severe limitations to say the least. > > The main problem as I see it is that the packaging switched straight to > the -nft versions without sufficient checking that it was not breaking > the system by doing so. Surely there are tests that can be done on > install to select the auto/default flavour better? > I don't have time to work on such magic migration mechanisms. But as I said, your issue is not with iptables-nft or nftables itself. You are using a very old kernel which won't work. thanks!
Bug#912661: python-tifffile: tifffile is not installed as distribution
> Debian makes use of the individual files via a mirror at > https://github.com/malaterre/tifffile which seems to exist for Debian > only. I'll remove this repo ASAP, to avoid spreading more confusion. Thanks for the report.
Bug#913877: iptables 1.8.2: ERROR when adding REJECT target to custom chains
My kernel version is 3.16.0-4-amd64. That is due to unrelated driver errors the newer kernels have consistently had on this hardware. I am surely not the only one in this situation. I see there was NEWS mention of unspecified impact with the 1.8.1+ versions but did not pay much attention to since I am not upgrading "between Debian versions" here. The machine in question has always run Sid and gets weekly updates of everything short of full reboot. The main problem as I see it is that the packaging switched straight to the -nft versions without sufficient checking that it was not breaking the system by doing so. Surely there are tests that can be done on install to select the auto/default flavour better? AYJ
Bug#913839: marked as done (htsjdk accesses the internet during the build)
Your message dated Fri, 16 Nov 2018 12:04:19 + with message-id and subject line Bug#913839: fixed in htsjdk 2.16.1+dfsg-3 has caused the Debian Bug report #913839, regarding htsjdk accesses the internet during the build 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.) -- 913839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: htsjdk Version: 2.16.1+dfsg-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/htsjdk.html ... Gradle suite > Gradle test > htsjdk.variant.PrintVariantsExampleTest.testExampleWriteFile FAILED java.net.UnknownHostException: profitbricks-build15-amd64: profitbricks-build15-amd64: Temporary failure in name resolution at java.base/java.net.InetAddress.getLocalHost(InetAddress.java:1642) at htsjdk.variant.example.PrintVariantsExample.printConfigurationInfo(PrintVariantsExample.java:96) at htsjdk.variant.example.PrintVariantsExample.main(PrintVariantsExample.java:70) at htsjdk.variant.PrintVariantsExampleTest.testExampleWriteFile(PrintVariantsExampleTest.java:52) Caused by: java.net.UnknownHostException: profitbricks-build15-amd64: Temporary failure in name resolution at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:929) at java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1515) at java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:848) at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1505) at java.base/java.net.InetAddress.getLocalHost(InetAddress.java:1637) ... 3 more Gradle is still running, please be patient... ... 26571 tests completed, 1 failed, 4 skipped Finished generating test XML results (1.113 secs) into: /build/1st/htsjdk-2.16.1+dfsg/build/test-results/test Generating HTML test report... Finished generating test html results (1.41 secs) into: /build/1st/htsjdk-2.16.1+dfsg/build/reports/tests/test :test FAILED :test (Thread[Task worker for ':' Thread 5,5,main]) completed. Took 12 mins 34.575 secs. FAILURE: Build failed with an exception. --- End Message --- --- Begin Message --- Source: htsjdk Source-Version: 2.16.1+dfsg-3 We believe that the bug you reported is fixed in the latest version of htsjdk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olivier Sallou (supplier of updated htsjdk 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: Fri, 16 Nov 2018 11:06:41 + Source: htsjdk Binary: libhtsjdk-java libhtsjdk-java-doc Architecture: source all Version: 2.16.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Olivier Sallou Description: libhtsjdk-java - Java API for high-throughput sequencing data (HTS) formats libhtsjdk-java-doc - Documentation for the java HTSJDK library Closes: 913839 Changes: htsjdk (2.16.1+dfsg-3) unstable; urgency=medium . * Fix FTBS on debian test servers due to ip/name resolution Remove related test. Closes: #913839 Checksums-Sha1: db3109f65c11677670fe15a5af51539556e629e2 2458 htsjdk_2.16.1+dfsg-3.dsc c92bffa3658390ee86d43b358eed19af87270f91 28528 htsjdk_2.16.1+dfsg-3.debian.tar.xz 1f390bf68b036786c5ef1df1c17fc99080a0bbce 15663 htsjdk_2.16.1+dfsg-3_amd64.buildinfo eff945970fd3b77b101d4ea15c61eec70131da77 1072004 libhtsjdk-java-doc_2.16.1+dfsg-3_all.deb 4caf39c2359963ca0f793d5ae2d85387c8106bea 1493518 libhtsjdk-java_2.16.1+dfsg-3_all.deb Checksums-Sha256: 2c3e34bb64e745c57002b13c5f64c374944a8cf94edb3b10ff891fb9039d4fd2 2458 htsjdk_2.16.1+dfsg-3.dsc 77c09f676051e787c46d5737ec12579f439360e5426bb329f354d568742e5ba8 28528 htsjdk_2.16.1+dfsg-3.debian.tar.xz d3f28513b241908f86007649b2f487f0745d6770abfaed7b1fae138417d79a2e 15663 htsjdk_2.16.1+dfsg-3_amd64.buildinfo
Bug#913877: iptables 1.8.2: ERROR when adding REJECT target to custom chains
Control: tag -1 unreproducible On Fri, 16 Nov 2018 23:20:02 +1300 Amos Jeffries wrote: > Followup experiments isolating the custom sub-chain are showing even > worse behaviour from the new iptables (-nft flavour). > > These commands > > iptables -N test-foo > iptables -I test-foo 1 -s 127.0.0.1 -j REJECT > > Produces this output: > > iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): > rule in chain test-foo > > > And this absurd syslog message: > > x_tables: ip_tables: REJECT target: used from hooks FORWARD, but only > usable from INPUT/FORWARD/OUTPUT > > > Upstream reports that this does work on other systems. Which kernel are you running? Mine is: arturo@endurance:~ $ uname -r 4.18.0-2-amd64 This is my local test: arturo@endurance:~ $ sudo iptables-nft -N test-foo arturo@endurance:~ $ sudo iptables-nft -I test-foo 1 -s 127.0.0.1 -j REJECT arturo@endurance:~ $ sudo iptables-nft-save # Generated by xtables-save v1.8.2 on Fri Nov 16 12:40:51 2018 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :test-foo - [0:0] -A test-foo -s 127.0.0.1/32 -j REJECT --reject-with icmp-port-unreachable COMMIT # Completed on Fri Nov 16 12:40:51 2018 Closing bug now, feel free to reopen if required. Thanks for reporting.
Processed: Re: iptables 1.8.2: ERROR when adding REJECT target to custom chains
Processing control commands: > tag -1 unreproducible Bug #913877 [iptables] iptables 1.8.2: ERROR when adding REJECT target to custom chains Added tag(s) unreproducible. -- 913877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913877: marked as done (iptables 1.8.2: ERROR when adding REJECT target to custom chains)
Your message dated Fri, 16 Nov 2018 12:43:43 +0100 with message-id <90588225-5cfc-834d-50ce-41b2391e5...@debian.org> and subject line Re: iptables 1.8.2: ERROR when adding REJECT target to custom chains has caused the Debian Bug report #913877, regarding iptables 1.8.2: ERROR when adding REJECT target to custom chains 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.) -- 913877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iptables Version: 1.8.2-2 Severity: grave The fail2ban attack prevention software scans log files and adds firewall rules dynamically to iptables/ip6tables to prevent DoS and login scanning attacks in realtime. Since upgrading iptables to the 1.8.2 version it has been completely unable to do that vital task due to problems within nftables / iptables. The example that I am facing right now is with active and large DoS attacks email spam attacks. When fail2ban attempts to add the firewall blocks, such as; iptables -w -I f2b-postfix-sasl 1 -s 80.82.70.189 \ -j REJECT --reject-with icmp-port-unreachable iptables produces an error: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain f2b-postfix-sasl the system log matching that iptables update attempt states: x_tables: ip_tables: REJECT target: used from hooks FORWARD/OUTPUT/POSTROUTING, but only usable from INPUT/FORWARD/OUTPUT Which appears to be a lie. The f2b-postfix-sasl is a sub-chain of the INPUT table and is not in any way connected to the FORWARD, OUTPUT nor POSTROUTING tables. iptables -L -nv Chain INPUT (policy ACCEPT 1727M packets, 3523G bytes) pkts bytes target prot opt in out source destination 9531 7001K f2b-postfix-sasl tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 9531 7001K f2b-courier-auth tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 8629 6907K f2b-postfix tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587 2994 278K f2b-sshd tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 22 6412K 2086M f2b-postfix-sasl tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 6412K 2086M f2b-courier-auth tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 3053K 829M f2b-postfix tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587 11M 663M f2b-sshd tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 22 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 1230M packets, 132G bytes) pkts bytes target prot opt in out source destination Chain f2b-sshd (2 references) pkts bytes target prot opt in out source destination 5988 556K RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2b-postfix (2 references) pkts bytes target prot opt in out source destination 17258 14M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2b-courier-auth (2 references) pkts bytes target prot opt in out source destination 19062 14M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2b-postfix-sasl (2 references) pkts bytes target prot opt in out source destination 19062 14M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 AYJ --- End Message --- --- Begin Message --- Control: tag -1 unreproducible On Fri, 16 Nov 2018 23:20:02 +1300 Amos Jeffries wrote: > Followup experiments isolating the custom sub-chain are showing even > worse behaviour from the new iptables (-nft flavour). > > These commands > > iptables -N test-foo > iptables -I test-foo 1 -s 127.0.0.1 -j REJECT > > Produces this output: > > iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): > rule in chain test-foo > > > And this absurd syslog message: > > x_tables: ip_tables: REJECT target: used from hooks FORWARD, but only > usable from INPUT/FORWARD/OUTPUT > > > Upstream reports that this does work on other systems. Which kernel are you running? Mine is: arturo@endurance:~ $ uname -r 4.18.0-2-amd64 This is my local test: arturo@endurance:~ $ sudo iptables-nft -N test-foo arturo@endurance:~ $ sudo iptables-nft -I test-foo 1 -s 127.0.0.1 -j REJECT arturo@endurance:~ $ sudo iptables-nft-save #
Processed: tagging 913811
Processing commands for cont...@bugs.debian.org: > tags 913811 + pending Bug #913811 [iptables] iptables fails to upgrade from 1.8.1-2 to 1.8.2-1 Bug #913814 [iptables] iptables fails to upgrade: ln: failed to create symbolic link '/sbin/iptables': File exists Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 913811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913811 913814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913469: marked as done (surfraw: Broken Maintainer e-mail address after NMU (was fine before))
Your message dated Fri, 16 Nov 2018 11:20:27 + with message-id and subject line Bug#913469: fixed in surfraw 2.3.0-0.2 has caused the Debian Bug report #913469, regarding surfraw: Broken Maintainer e-mail address after NMU (was fine before) 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.) -- 913469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: surfraw Severity: serious Version: 2.3.0-0.1 Dear Dmitry, the recent NMU of surfraw broke the Maintainer e-mail address: Previously the Maintainer address was surfraw-de...@lists.alioth.debian.org and working (i.e. there was no need to change it): → host -t mx lists.alioth.debian.org lists.alioth.debian.org mail is handled by 10 alioth-lists-mx.debian.net. Now the maintainer e-mail address is surfraw-de...@alioth-listsdebian.net which has a non-existent domain due to a missing a dot between "lists" and "debian": → host -t any alioth-listsdebian.net Host alioth-listsdebian.net not found: 3(NXDOMAIN) So please revert that _unnecessary_ change and change the maintainer address back to its previous value. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: surfraw Source-Version: 2.3.0-0.2 We believe that the bug you reported is fixed in the latest version of surfraw, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Bogatov (supplier of updated surfraw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Nov 2018 10:49:25 + Source: surfraw Binary: surfraw surfraw-extra Architecture: source all Version: 2.3.0-0.2 Distribution: unstable Urgency: medium Maintainer: Debian surfraw maintainers Changed-By: Dmitry Bogatov Description: surfraw- fast unix command line interface to WWW surfraw-extra - extra surfraw search tools with heavy dependencies Closes: 913469 Changes: surfraw (2.3.0-0.2) unstable; urgency=medium . * Revert incorrect update of maintainer email (Closes: #913469) Checksums-Sha1: 63dbbfcfec73cff74b7837f6ae01664c51c8eb55 2274 surfraw_2.3.0-0.2.dsc 1ae7ee88c56af20e14f9f57d15a04a08c15d9973 13396 surfraw_2.3.0-0.2.debian.tar.xz 2a0aef00580fb3248ef8b6223b2e8ef6de74d7cb 33116 surfraw-extra_2.3.0-0.2_all.deb a98827bb67b8c2495e5a55d61cec073409026459 114216 surfraw_2.3.0-0.2_all.deb c8d33bc70416f7c3b9531d5f01615be39f76cca6 5999 surfraw_2.3.0-0.2_amd64.buildinfo Checksums-Sha256: fdabb088de4fdd41538d2396f3cf63164255b95f75fd9625128ab3d3ffe20261 2274 surfraw_2.3.0-0.2.dsc f830185350bf220974d376e286bc2717aeb0e7a851817f74d0dd0c748fb80ee5 13396 surfraw_2.3.0-0.2.debian.tar.xz 07d6f3cdf985ccb096bce34da8db3faf6364e52ce6fb895cdb6bdb75a7028738 33116 surfraw-extra_2.3.0-0.2_all.deb 18b7e2b0efb3b3885c5747b622938fb7dc4ea36b0cfdce98725c97775dc20697 114216 surfraw_2.3.0-0.2_all.deb c968d2d957167a50d4789057fb0ba08ffcf61daad4f04e07856d94a175328f99 5999 surfraw_2.3.0-0.2_amd64.buildinfo Files: 8bdc5947cbf8170b9f665436c3dbe9f1 2274 web optional surfraw_2.3.0-0.2.dsc 4476f2119f974e2149b8948a69883219 13396 web optional surfraw_2.3.0-0.2.debian.tar.xz a1147c8ac673bb5373920eac0fe1c15b 33116 web optional surfraw-extra_2.3.0-0.2_all.deb a0f20194b6024c133755a4b64490c386 114216 web optional surfraw_2.3.0-0.2_all.deb 86df93b16f3a3c220b9853a6d320f53b 5999 web optional surfraw_2.3.0-0.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlvpW5ATHGthY3Rpb25A ZGViaWFuLm9yZwAKCRBIEtjeqCYR5nxMD/iSLAVWZRDOylfetWwDPYFX2EWuGi2q
Bug#913839: not internet access
issue is not related to an internet access. it tries to get local host name or address : java.net.InetAddress.getLocalHost(..) and result in java.net.UnknownHostException: profitbricks-build15-amd64: profitbricks-build15-amd64: Temporary failure in name resolution According to Java: This is achieved by retrieving the name of the host from the system, then resolving that name into an InetAddress. So issue looks related to test server host/ip resolution. not an external access requirement. Anyway, I guess that test could be disable via a patch. -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Bug#913877: iptables 1.8.2: ERROR when adding REJECT target to custom chains
Followup experiments isolating the custom sub-chain are showing even worse behaviour from the new iptables (-nft flavour). These commands iptables -N test-foo iptables -I test-foo 1 -s 127.0.0.1 -j REJECT Produces this output: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain test-foo And this absurd syslog message: x_tables: ip_tables: REJECT target: used from hooks FORWARD, but only usable from INPUT/FORWARD/OUTPUT For anyone else encountering issues from the new packages these commands: update-alternatives --config iptables update-alternatives --config ip6tables to manually override the automatic package default with the '-legacy' flavour is required to restore proper behaviour. AYJ
Bug#913877: [pkg-netfilter-team] Bug#913877: (no subject)
Control: forwarded -1 https://bugzilla.netfilter.org/show_bug.cgi?id=1298
Processed: Re: [pkg-netfilter-team] Bug#913877: (no subject)
Processing control commands: > forwarded -1 https://bugzilla.netfilter.org/show_bug.cgi?id=1298 Bug #913877 [iptables] iptables 1.8.2: ERROR when adding REJECT target to custom chains Set Bug forwarded-to-address to 'https://bugzilla.netfilter.org/show_bug.cgi?id=1298'. -- 913877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913877: (no subject)
Control: forwarded -1 https://bugzilla.netfilter.org/show_bug.cgi?id=1298
Bug#913877: [pkg-netfilter-team] Bug#913877: iptables 1.8.2: ERROR when adding REJECT target to custom chains
Control: forward -1 https://bugzilla.netfilter.org/show_bug.cgi?id=1298 Your bug report has been forwarded upstream.
Bug#911204: marked as done (p4vasp: depend on unmaintained libgnomeui)
Your message dated Fri, 16 Nov 2018 09:49:43 + with message-id and subject line Bug#911204: fixed in p4vasp 0.3.30+dfsg-4 has caused the Debian Bug report #911204, regarding p4vasp: depend on unmaintained libgnomeui 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.) -- 911204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: p4vasp Version: 0.3.30+dfsg-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs libgnomeui Tags: sid buster As announced [1], we do not intend to release Debian 10 "Buster" with the old libgnome (and related) libraries. These libraries have been deprecated and unmaintained for several years. Please port your package to GTK3 and related maintained libraries. p4vasp was removed from Testing 9 months ago because of this issue. If the package can't be ported away from libgnome, it will eventually need to removed from Debian. [1] https://lists.debian.org/debian-devel/2017/10/msg00299.html On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: p4vasp Source-Version: 0.3.30+dfsg-4 We believe that the bug you reported is fixed in the latest version of p4vasp, 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 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated p4vasp 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, 16 Nov 2018 09:32:37 + Source: p4vasp Binary: p4vasp Architecture: source Version: 0.3.30+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Graham Inggs Description: p4vasp - visualization suite for the Vienna Ab-initio Simulation Package ( Closes: 911204 Changes: p4vasp (0.3.30+dfsg-4) unstable; urgency=medium . * Drop dependency on libgnomeui-0, thanks Jeremy Bicha! (Closes: #911204) * Bump Standards-Version to 4.2.1, no changes Checksums-Sha1: 50e4726ea5c35bf2d672e291776a52179c4646bd 1997 p4vasp_0.3.30+dfsg-4.dsc 7ccdd9c0a4cdb9d7e600da7644c9e85fdc2b6ac4 15684 p4vasp_0.3.30+dfsg-4.debian.tar.xz Checksums-Sha256: 381ed6d801b090d30ee95d78e3a0e628e866f3f69a458a377f6293d42bbbecc5 1997 p4vasp_0.3.30+dfsg-4.dsc 6615168d2c7ef8c4a330d64f9afe4007c496f2005bfc2c55cbe59b5683f423f7 15684 p4vasp_0.3.30+dfsg-4.debian.tar.xz Files: 7ad6dcc2a5ea40102a0e429fbeea5be1 1997 science optional p4vasp_0.3.30+dfsg-4.dsc 77d77bcd1d8fc3f4b4cfa7ed12570803 15684 science optional p4vasp_0.3.30+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAlvuj3AACgkQr8/sjmac 4cIoRA//QuncWJz4DEIFiQc8Y4GNkGcqGq/OUZnvGaSUPFiJ8FswdX9do4qGJJQC QJfxS+A7pNAe+Nyip0TtAocaCz2m1C+bJ5sH3HgTmkFH6oN8PiXRgGxnOAjIX1pA ycEFxXRU1xbU9nCwRHbSNWuNNS4m5JyWlVbFhBkhdxh1z3qwOF6ONG6Cb1x6/zJD 941YdAbgPHutG/ywuoK8tI+lbJOUxchRKVeM+cg2EQKxTwkvKvafvn70aoVuR9n3 5XvT+nlta/500ik2ajdWlX3mIfROunhGhiii2sgR9SwptsUE1keLwPcGowymLoEO mF0gyJi/c9ITJUTgaGzbO5zYjncrio6UIuxgZhpmZ52GiX5zvx0uRAHrVV9+qAbC 6tzBX7KWBxi6+sXyNrv6iTHOA/YexpBF2SMbj4w4UMBPyV4T14LdH/2kqBZxbapH MSyvB/2pfDNOvSjKo48o47wsuj2hiPiCOKpCQ/x16IIZ06V8KBGcOkeDjQm3Z71e G9SqeyG2Ehr0asCidhkFrFSqob15oSpn7MFxT5b8dUos/6UeIEio0JmGCRfgjPJH tRM7Byf+uRA/lcola2Ri6Nl4AG0OdUAkOP/eilEZRqvLPRH6ioWRk2Op3byEzpM5 haM7VVZai1ICkCyNq6GrewwdfYwjMX+4EnJyvqlXi05DyvrJDMA= =PTk4 -END PGP SIGNATURE End Message ---
Bug#913877: iptables 1.8.2: ERROR when adding REJECT target to custom chains
Package: iptables Version: 1.8.2-2 Severity: grave The fail2ban attack prevention software scans log files and adds firewall rules dynamically to iptables/ip6tables to prevent DoS and login scanning attacks in realtime. Since upgrading iptables to the 1.8.2 version it has been completely unable to do that vital task due to problems within nftables / iptables. The example that I am facing right now is with active and large DoS attacks email spam attacks. When fail2ban attempts to add the firewall blocks, such as; iptables -w -I f2b-postfix-sasl 1 -s 80.82.70.189 \ -j REJECT --reject-with icmp-port-unreachable iptables produces an error: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain f2b-postfix-sasl the system log matching that iptables update attempt states: x_tables: ip_tables: REJECT target: used from hooks FORWARD/OUTPUT/POSTROUTING, but only usable from INPUT/FORWARD/OUTPUT Which appears to be a lie. The f2b-postfix-sasl is a sub-chain of the INPUT table and is not in any way connected to the FORWARD, OUTPUT nor POSTROUTING tables. iptables -L -nv Chain INPUT (policy ACCEPT 1727M packets, 3523G bytes) pkts bytes target prot opt in out source destination 9531 7001K f2b-postfix-sasl tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 9531 7001K f2b-courier-auth tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 8629 6907K f2b-postfix tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587 2994 278K f2b-sshd tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 22 6412K 2086M f2b-postfix-sasl tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 6412K 2086M f2b-courier-auth tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587,143,993,110,995 3053K 829M f2b-postfix tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 25,465,587 11M 663M f2b-sshd tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 22 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 1230M packets, 132G bytes) pkts bytes target prot opt in out source destination Chain f2b-sshd (2 references) pkts bytes target prot opt in out source destination 5988 556K RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2b-postfix (2 references) pkts bytes target prot opt in out source destination 17258 14M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2b-courier-auth (2 references) pkts bytes target prot opt in out source destination 19062 14M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain f2b-postfix-sasl (2 references) pkts bytes target prot opt in out source destination 19062 14M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 AYJ
Bug#913116: Needs to depend on chromium-sandbox
Control: reopen -1 Debian does not support unprivileged user namespaces, so chromium needs to depend on -sandbox to get a working package. Re-opening, as recommends are not enough. Regards, Bastian for kernel team -- A woman should have compassion. -- Kirk, "Catspaw", stardate 3018.2
Processed: Needs to depend on chromium-sandbox
Processing control commands:
> reopen -1
Bug #913116 {Done: Michael Gilbert } [chromium] Fails to
start without chromium-sandbox installed
'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 chromium-browser/70.0.3538.102-1.
--
913116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#911204: p4vasp: depend on unmaintained libgnomeui
Hi Jeremy On 2018/11/16 04:30, Jeremy Bicha wrote: I looked through the code briefly and I don't think p4vasp actually needs to depend on libgnomeui. Thanks for looking! Can we try removing that dependency since the app seems to at least basically run without it? It looks like some features of the app don't work even with that dependency installed. Yes, that sounds reasonable. I checked the features I know people here are using and it seems fine. Let's get this into testing. Regards Graham
Bug#913820: [Pkg-freeipa-devel] Bug#913820: cockpit-389-ds: Debian-packaged JS libs not sufficient to run cockpit-plugin
On 15.11.2018 18.22, Jan Luca Naumann wrote: > Package: cockpit-389-ds > Version: 1.4.0.18-1 > Severity: grave > Justification: renders package unusable > > At the momenent the package cockpit-389-ds applies a patch to use the Debian > packaged JS libraries. In contrast to the vendored libraries the Debian > versions > do not work with the current version of the cockpit-389-plugin, c.f. the > backtrace attached. Removing the Debian-specific patch and installing the > vendored JS libs resolves the issue. yeah, and all the minified stuff is already in debian/missing-sources, so it should be fine to just drop the patch.. Thanks for the bug! -- t
Bug#858937: kde4libs: Please migrate to openssl1.1 in buster
On Thu, 12 Oct 2017 23:44:27 +0200 Sebastian Andrzej Siewior wrote: > Hi, > > this is a remainder about the openssl transition [0]. We really want to > remove libssl1.0-dev from unstable for Buster. I will raise the severity> of > this bug to serious in a month. Please react before that happens. This is the last blocker for the openssl 1.0 removal from testing. There is a patch at [1], could you look into using it? Thanks, Emilio [1] https://src.fedoraproject.org/rpms/kdelibs/blob/d68bdeabf80bf618b085bfb914c17153115e7e36/f/kdelibs-4.14.38-openssl-1.1.patch
Bug#913813: [Pkg-javascript-devel] Bug#913813: node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed
Control: tags -1 wontfix On Fri, Nov 16, 2018 at 5:50 AM Pirate Praveen wrote: > > > > On 2018, നവംബർ 15 9:01:15 PM IST, Mathieu Malaterre wrote: > >The following information may help to resolve the situation: > > > >The following packages have unmet dependencies: > >node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be > >installed > >E: Unable to correct problems, you have held broken packages. > > It in NEW for last 2 weeks. > > https://ftp-master.debian.org/new/node-yallist_3.0.2-1~bpo9+1.html Sorry for the noise.
Bug#913812: marked as done (node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed)
Your message dated Fri, 16 Nov 2018 09:31:11 +0100 with message-id and subject line Re: [Pkg-javascript-devel] Bug#913812: node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed has caused the Debian Bug report #913812, regarding node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed 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.) -- 913812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-boxen Version: 1.2.2-1~bpo9+1 Severity: grave Looks like the package is pretty much invalid: $ sudo apt-get install -t stretch-backports node-boxen Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed E: Unable to correct problems, you have held broken packages. --- End Message --- --- Begin Message --- Control: tags -1 wontfix On Fri, Nov 16, 2018 at 5:52 AM Pirate Praveen wrote: > > > > On 2018, നവംബർ 15 8:54:58 PM IST, Mathieu Malaterre wrote: > >The following information may help to resolve the situation: > > > >The following packages have unmet dependencies: > >node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be > >installed > >E: Unable to correct problems, you have held broken packages. > > It is in NEW for last 2 weeks > > https://ftp-master.debian.org/new/node-camelcase_4.1.0-1~bpo9+1.html Sorry for the noise.--- End Message ---
Processed: Re: [Pkg-javascript-devel] Bug#913813: node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed
Processing control commands: > tags -1 wontfix Bug #913813 [node-tar] node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed Added tag(s) wontfix. -- 913813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913813: marked as done (node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed)
Your message dated Fri, 16 Nov 2018 09:31:49 +0100 with message-id and subject line Re: [Pkg-javascript-devel] Bug#913813: node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed has caused the Debian Bug report #913813, regarding node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed 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.) -- 913813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-tar Version: 4.4.6+ds1-3~bpo9+1 Severity: grave Looks like the package is pretty much invalid: $ sudo apt-get install -t stretch-backports node-tar Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed E: Unable to correct problems, you have held broken packages. --- End Message --- --- Begin Message --- Control: tags -1 wontfix On Fri, Nov 16, 2018 at 5:50 AM Pirate Praveen wrote: > > > > On 2018, നവംബർ 15 9:01:15 PM IST, Mathieu Malaterre wrote: > >The following information may help to resolve the situation: > > > >The following packages have unmet dependencies: > >node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be > >installed > >E: Unable to correct problems, you have held broken packages. > > It in NEW for last 2 weeks. > > https://ftp-master.debian.org/new/node-yallist_3.0.2-1~bpo9+1.html Sorry for the noise.--- End Message ---
Bug#913812: [Pkg-javascript-devel] Bug#913812: node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed
Control: tags -1 wontfix On Fri, Nov 16, 2018 at 5:52 AM Pirate Praveen wrote: > > > > On 2018, നവംബർ 15 8:54:58 PM IST, Mathieu Malaterre wrote: > >The following information may help to resolve the situation: > > > >The following packages have unmet dependencies: > >node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be > >installed > >E: Unable to correct problems, you have held broken packages. > > It is in NEW for last 2 weeks > > https://ftp-master.debian.org/new/node-camelcase_4.1.0-1~bpo9+1.html Sorry for the noise.
Processed: Re: [Pkg-javascript-devel] Bug#913812: node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed
Processing control commands: > tags -1 wontfix Bug #913812 [node-boxen] node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed Added tag(s) wontfix. -- 913812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911278: [Fwd: php7cc: PHP Fatal error: Uncaught Error: Cannot instantiate interface PhpParser\Parser]
> Ok, I can work on it, however there is an information in README.md in > php7cc repository (https://github.com/sstalle/php7cc) that: > > The project is no longer supported... > > - do you know about this? I did not know about that. Thanks. Then perhaps we should request removal of this package? Or would it be better to at least keep it out of "Buster"? > So the question is if this package is still really needed (i couldn't find > any package which depends on it)? I think this package is still valuable on its own. It is helpful to detect outdated code that needs update for compatibility with PHP-7. I've used "php7cc" to report compatibility problems to some projects. > I have already forked the php7cc repository and did some amendments to > force it working with php-parser 3 - please check > https://github.com/lbacik/php7cc/tree/php-parser-3 - but even if the > script works properly in case of simple task, unit tests fail. So it is > worth nothing. And IMO such approach - with patching actual code - can't > success without active project developing. I'm not qualified to produce a patch for this problem. If you can contribute the patch (upstream and to debian package) then only you can judge whether it is worth the effort. > So what left - from my point of view (if this package is really > needed): > > (1) to add php-parser in version 1.4.1 as a separate package (php- > parser-1.4.1) to fulfill dependency of php7cc. Is it possible? Than you > have to only change the autoload configuration to point to that older > version of php-parser. It is undesirable to introduce an outdated package just to fulfill the dependency. Better to patch "php7cc" for compatibility with up-to-date "php- parser" or remove the former. > (2) "linking php-parser statically" :) with php7cc source - I mean by > this to just add the php-parser code to the php7cc source and remove > the dependency to php-parser package. Once again the autoload file will > have to be edited to load the php-parser from the directory within > php7cc package but it should work. Private code copies are against the policy. In exceptional circumstances it may be justifiable but IMHO not in this case. > Let me know what you think - if you still want to fix this issue i will > also try to catch the author of php7cc to ask him about his opinion in > this matter. It would be great if you could as upstream please. Thank you. -- Regards, Dmitry Smirnov. --- The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part.
