Bug#909094: gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable
Hello, > The way forward for Kali might be to just push glib2.0, gnome-shell, > mutter, and gnome-shell-extensions to Testing early. I fixed the issue for Kali by forking the package and reverting last changes. > As long as we can get glib to build on armel, all these should land in > Testing in a couple days. Yes I noticed that but I thought I had to report anyway this (very annoying) bug. I hope Gnome Shell will migrate quickly. Thanks Sophie
Bug#909161: hylafax: CVE-2018-17141
Source: hylafax Version: 3:6.0.6-1 Severity: grave Tags: patch security upstream Control: fixed -1 3:6.0.6-7+deb9u1 Hi, The following vulnerability was published for hylafax: CVE-2018-17141[0]. Fix commited as [1]. 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-17141 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17141 [1] http://git.hylafax.org/HylaFAX?a=commit;h=82fa7bdbffc253de4d3e80a87d47fdbf68eabe36 Regards, Salvatore
Processed: hylafax: CVE-2018-17141
Processing control commands: > fixed -1 3:6.0.6-7+deb9u1 Bug #909161 [src:hylafax] hylafax: CVE-2018-17141 The source 'hylafax' and version '3:6.0.6-7+deb9u1' do not appear to match any binary packages Marked as fixed in versions hylafax/3:6.0.6-7+deb9u1. -- 909161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909089: debhelper: GNU configure $prefix expanded too early?
Sven Joachim:
> On 2018-09-18 14:09 +0300, Peter Pentchev wrote:
>
>> Package: debhelper
>> Version: 11.4
>> Severity: serious
>>
>> Hi,
>>
>> Thanks for maintaining and extending debhelper!
>>
>> I don't have much information right now, maybe I'll look into it in
>> the evening (Eastern European time), but trying to build gforth in
>> a chroot containing debhelper-11.4 results in a package where all
>> the paths passed to the GNU configure script as "\$prefix/something"
>> are actually defined as "/something", thus placing binaries in /bin,
>> include files in /include, etc. Installing debhelper-11.3.5 fixes
>> the problem.
>
> Bisection shows that commit a7ec05c10093f ("dh: Track which options have
> been passed") has triggered the problem. I had a look at the gforth
> build logs with debhelper 11.3.5 and 11.4, but could not spot an obvious
> cause. Maybe Niels has more luck.
>
> Cheers,
>Sven
>
Hi,
@Sven: Thanks for bisecting it. FTR, which version of gforth did you
test with?
@Both: I checked the configure lines and they are identical
(bit-for-bit) in the log, so we are probably looking for something
different.
I have compared the build logs from Peter with the amd64 build on the
buildds (with some messaging) and I do not see any obvious problems (I
assume the differences shown are due to -6 vs. -7).
"""
Generated the files with:
grep dh_ \
| grep -v 'The use of "debhelper-compat (= 11)" is experimental' \
| sed 's/-a //'
--- dh_broken.log 2018-09-19 08:00:04.640018651 +0200
+++ dh_ok.log 2018-09-19 08:00:20.952018495 +0200
@@ -1,6 +1,5 @@
debian/rules override_dh_auto_clean
dh_auto_clean
- dh_autoreconf_clean -O--no-parallel
dh_clean -O--no-parallel
dh_update_autotools_config -O--no-parallel
dh_autoreconf -O--no-parallel
@@ -15,8 +14,7 @@
debian/rules override_dh_install
dh_installdocs -O--no-parallel
debian/rules override_dh_installchangelogs
-dh_installchangelogs -X ChangeLog
-set -e; for p in $(dh_listpackages); do \
+dh_installchangelogs NEWS
dh_installman -O--no-parallel
dh_installemacsen -O--no-parallel
dh_lintian -O--no-parallel
"""
The dh_autoreconf_clean omission is expected (dh-autoreconf made it
optional so we could avoid calling it in the initial clean where it is
always a no-op) and the remaining diffs looks like a change to the rules.
I also checked the make install part and both logs installs the files
into /<>/debian/tmp/usr/...
@Peter: Could you try to add a "dh_installdirs" (or mkdir -p $(DG)/)
before the following line?
mv /<>/debian/tmp/* /<>/debian/gforth/
https://sources.debian.org/src/gforth/0.7.3+dfsg-6/debian/rules/#L81
Thanks,
~Niels
Bug#908483: marked as done (spl-dkms: spl-dmks fails to build on Linux 4.18.0-1)
Your message dated Wed, 19 Sep 2018 05:50:48 + with message-id and subject line Bug#908483: fixed in spl-linux 0.7.11-1 has caused the Debian Bug report #908483, regarding spl-dkms: spl-dmks fails to build on Linux 4.18.0-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.) -- 908483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: spl-dkms Version: 0.7.9-3 Severity: important Dear Maintainer, spl-dkms fails to install on sid making zfs module unusable. Please find logs below and let me know if you need any more informations Cheers Marcus --Dpkg log: Loading new spl-0.7.9 DKMS files... Building for 4.18.0-1-amd64 Building initial module for 4.18.0-1-amd64 Error! Bad return status for module build on kernel: 4.18.0-1-amd64 (x86_64) --Relevant lines of /var/lib/dkms/spl/0.7.9/build/make.log: CC [M] /var/lib/dkms/spl/0.7.9/build/module/spl/spl-zlib.o /var/lib/dkms/spl/0.7.9/build/module/spl/spl-vnode.c: In function ‘vn_getattr’: /var/lib/dkms/spl/0.7.9/build/module/spl/spl-vnode.c:308:16: error: incompatible types when assigning to type ‘struct timespec’ from type ‘struct timespec64’ vap->va_atime = stat.atime; ^ /var/lib/dkms/spl/0.7.9/build/module/spl/spl-vnode.c:309:16: error: incompatible types when assigning to type ‘struct timespec’ from type ‘struct timespec64’ vap->va_mtime = stat.mtime; ^ /var/lib/dkms/spl/0.7.9/build/module/spl/spl-vnode.c:310:16: error: incompatible types when assigning to type ‘struct timespec’ from type ‘struct timespec64’ vap->va_ctime = stat.ctime; ^ make[7]: *** [/usr/src/linux-headers-4.18.0-1-common/scripts/Makefile.build:322: /var/lib/dkms/spl/0.7.9/build/module/spl/spl-vnode.o] Fehler 1 make[7]: *** Es wird auf noch nicht beendete Prozesse gewartet LD [M] /var/lib/dkms/spl/0.7.9/build/module/splat/splat.o make[6]: *** [/usr/src/linux-headers-4.18.0-1-common/scripts/Makefile.build:563: /var/lib/dkms/spl/0.7.9/build/module/spl] Fehler 2 make[5]: *** [/usr/src/linux-headers-4.18.0-1-common/Makefile:1518: _module_/var/lib/dkms/spl/0.7.9/build/module] Fehler 2 make[4]: *** [Makefile:146: sub-make] Fehler 2 make[3]: *** [Makefile:8: all] Fehler 2 make[3]: Verzeichnis „/usr/src/linux-headers-4.18.0-1-amd64“ wird verlassen make[2]: *** [Makefile:11: modules] Fehler 2 make[2]: Verzeichnis „/var/lib/dkms/spl/0.7.9/build/module“ wird verlassen make[1]: *** [Makefile:610: all-recursive] Fehler 1 make[1]: Verzeichnis „/var/lib/dkms/spl/0.7.9/build“ wird verlassen make: *** [Makefile:491: all] Fehler 2 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/32 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spl-dkms depends on: ii dkms 2.6.1-1 ii file 1:5.34-2 ii libc6-dev [libc-dev] 2.27-6 ii libelf-dev 0.170-0.5 ii lsb-release 9.20170808 spl-dkms recommends no packages. Versions of packages spl-dkms suggests: ii linux-libc-dev 4.18.6-1 pn spl -- no debconf information --- End Message --- --- Begin Message --- Source: spl-linux Source-Version: 0.7.11-1 We believe that the bug you reported is fixed in the latest version of spl-linux, 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. Mo Zhou (supplier of updated spl-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Sep 2018 04:13:01 + Source: spl-linux Binary: spl-dkms spl Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian ZFS on Linux maintainers Changed-By: Mo Zhou Description: spl- Solaris Porting Layer user-space utilities for Linux spl-dkms - Solar
Bug#909155: apt-cache show multiple packages produces invalid output
Package: apt Version: 1.7.0~rc1 Severity: serious File: /usr/bin/apt-cache If you do a fresh sid debootstrap and then you can get the following interaction: $ apt-cache show gcc-8-base=installed libgcc1=installed Package: gcc-8-base Source: gcc-8 Version: 8.2.0-7 Installed-Size: 244 Maintainer: Debian GCC Maintainers Architecture: amd64 Breaks: gcc-4.4-base (<< 4.4.7), gcc-4.7-base (<< 4.7.3), gcj-4.4-base (<< 4.4.6-9~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.4-base (<< 4.4.6-3~), gnat-4.6 (<< 4.6.1-5~) Description: GCC, the GNU Compiler Collection (base package) Description-md5: b6e93638a6d08ea7a18929d7cf078e5d Multi-Arch: same Homepage: http://gcc.gnu.org/ Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/g/gcc-8/gcc-8-base_8.2.0-7_amd64.deb Size: 187052 MD5sum: 5ae3d2f575c9924ae67fa8dcc4af1e21 SHA256: 9e3dcd13005ccadbb57a8f117cde66aec8b8b8a21492e3aa02d6f54c1288bfb4 Package: libgcc1 Source: gcc-8 (8.2.0-7) Version: 1:8.2.0-7 Installed-Size: 116 Maintainer: Debian GCC Maintainers Architecture: amd64 Depends: gcc-8-base (= 8.2.0-7), libc6 (>= 2.14) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Description: GCC support library Description-md5: bbd60d723e97d8e06c04228ee4c76f10 Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/g/gcc-8/libx32gomp1_8.2.0-7_amd64.deb Size: 77204 MD5sum: 61275848d23df37f647cb6a9b21f4135 SHA256: b8c56221460897e2640baf7bd6e1a9f645346d4178265508a18d48bf8c68e752 Package: libx32gomp1-dbg Source: gcc-8 Version: 8.2.0-7 Installed-Size: 346 Maintainer: Debian GCC Maintainers
Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure
-=| Xavier, 18.09.2018 22:58:48 +0200 |=-
> Le 15/09/2018 à 17:42, Damyan Ivanov a écrit :
> > Adding
> > $SIG{PIPE} = 'IGNORE';
> > at the start of the test seems to make it pass all the time.
> >
> > I wonder if this is the correct fix.
> >
> > -- Damyan
>
> Hello,
>
> I added this hook without success. "reproducible" builds well [1] but
> not buildd [2]
>
> [1]
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnet-server-mail-perl.html)
> [2]
> https://buildd.debian.org/status/package.php?p=libnet-server-mail-perl
The buildd used libio-socket-ssl-perl 2.059-1, which misses a lot of
openssl 1.1.1 fixes.
Perhaps bumping the (build) dependency to version 2.060-3 would help?
Hmm, the reproducible-builds log also shows 2.059-1, but I guess
bumping the version is still worth a try -- may be the failure is hard
to trigger.
-- dam
Processed: bug 908498 is forwarded to https://github.com/collective/icalendar/issues/260
Processing commands for cont...@bugs.debian.org: > forwarded 908498 https://github.com/collective/icalendar/issues/260 Bug #908498 [src:python-icalendar] python-icalendar FTBFS with python-dateutil 2.7.3-1 Set Bug forwarded-to-address to 'https://github.com/collective/icalendar/issues/260'. > thanks Stopping processing here. Please contact me if you need assistance. -- 908498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909084: marked as done (Missing pcre module)
Your message dated Tue, 18 Sep 2018 23:35:07 + with message-id and subject line Bug#909084: fixed in zsh 5.6.2-3 has caused the Debian Bug report #909084, regarding Missing pcre module 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.) -- 909084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zsh Version: 5.6.2-2 Severity: normal In the last release, the pcre module does not seem to be built anymore. This causes "setopt rematch_pcre" to fail: failed to load module `zsh/pcre': /usr/lib/x86_64-linux-gnu/zsh/5.6.2/zsh/pcre.so: cannot open shared object file: No such file or directory -pcre-match not available for regex -- Package-specific info: Packages which depend, recommend, suggest or enhance a zsh package and hence may provide code meant to be sourced in .zshrc: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-==-== ii zshdb 0.92-3 alldebugger for Z-Shell scripts Packages which provide vendor completions: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-==-== ii curl 7.61.0-1 amd64 command line tool for transferring data wi ii git-annex 6.20180913-1 amd64 manage files with git, without checking th ii git-buildpackage 0.9.10 allSuite to help with Debian packages in Git ii khal 1:0.9.8-1 allStandards based CLI and terminal calendar ii mpv1:0.29.0-dmo1 amd64 Free and open-source general-purpose video ii ninja-build1.8.2-1amd64 small build system closest in spirit to Ma ii pass 1.7.3-1alllightweight directory-based password manag ii pulseaudio 12.2-2 amd64 PulseAudio sound server ii radare22.9.0+dfsg-1 amd64 free and advanced command line hexadecimal ii ripgrep0.9.0-6amd64 Recursively searches directories for a reg ii silversearcher-ag 2.1.0-1amd64 very fast grep-like program, alternative t ii systemd239-9 amd64 system and service manager ii systemd-container 239-9 amd64 systemd container/nspawn tools ii systemd-coredump 239-9 amd64 tools for storing and retrieving coredumps ii taskwarrior2.5.1+dfsg-6 amd64 feature-rich console based todo list manag ii udev 239-9 amd64 /dev/ and hotplug management daemon ii youtube-dl 2018.09.10-1 alldownloader of videos from YouTube and othe The following files were modified: /etc/systemd/logind.conf /etc/systemd/resolved.conf /etc/systemd/journald.conf dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/ -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc3-amd64 (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) Versions of packages zsh depends on: ii libc6 2.27-6 ii libcap2 1:2.25-1.2 ii libtinfo6 6.1+20180714-1 ii zsh-common 5.6.2-2 Versions of packages zsh recommends: ii libc6 2.27-6 ii libncursesw6 6.1+20180714-1 Versions of packages zsh suggests: ii zsh-doc 5.6.2-2 --- End Message --- --- Begin Message --- Source: zsh Source-Version: 5.6.2-3 We believe that the bug you reported is fixed in the latest version of zsh, 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 909...@bugs.deb
Bug#908063: marked as done (sylpheed: TLS connection to imap.gmail.com returns self-signed certificate with openssl 1.1.0)
Your message dated Tue, 18 Sep 2018 22:20:52 + with message-id and subject line Bug#908063: fixed in sylpheed 3.7.0-4 has caused the Debian Bug report #908063, regarding sylpheed: TLS connection to imap.gmail.com returns self-signed certificate with openssl 1.1.0 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.) -- 908063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sylpheed Version: 3.7.0-3+b1 Severity: important Tags: upstream patch Dear Maintainer, when using openssl 1.1.0 (now in Unstable) the gmail servers require clients to set the Server Name Indication, responding with an invalid self-signed certificate if this is not the case. Sylpheed does not set the SNI. Here is a link to the upstream bug report in which I provide a patch and a link to a better explanation: https://sylpheed.sraoss.jp/redmine/issues/306 Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylpheed depends on: ii libassuan0 2.5.1-2 ii libatk1.0-0 2.28.1-1 ii libc62.27-6 ii libcairo21.15.12-1 ii libcompfaceg11:1.5.2-5+b2 ii libenchant1c2a 1.6.0-11.1 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libfribidi0 1.0.5-3 ii libgdk-pixbuf2.0-0 2.36.12-2 ii libglib2.0-0 2.58.0-2 ii libgpg-error01.32-1 ii libgpgme11 1.11.1-1 ii libgtk2.0-0 2.24.32-3 ii libgtkspell0 2.0.16-1.2 ii libldap-2.4-22.4.46+dfsg-5 ii libonig5 6.8.2-1 ii libpango-1.0-0 1.42.4-2 ii libpangocairo-1.0-0 1.42.4-2 ii libpangoft2-1.0-01.42.4-2 ii libssl1.11.1.1~~pre9-1 ii pinentry-gtk21.1.0-1+b1 Versions of packages sylpheed recommends: ii aspell-it [aspell-dictionary] 2.4-20070901-0-3 ii bogofilter 1.2.4+dfsg1-13 ii bsfilter 1:1.0.19-2 ii ca-certificates20180409 ii sylpheed-i18n 3.7.0-3 Versions of packages sylpheed suggests: pn claws-mail-tools ii curl 7.61.0-1 pn sylpheed-doc ii sylpheed-plugins 3.7.0-3+b1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? --- End Message --- --- Begin Message --- Source: sylpheed Source-Version: 3.7.0-4 We believe that the bug you reported is fixed in the latest version of sylpheed, 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. Ricardo Mones (supplier of updated sylpheed 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: Tue, 18 Sep 2018 23:45:55 +0200 Source: sylpheed Binary: sylpheed sylpheed-i18n sylpheed-plugins Architecture: source amd64 all Version: 3.7.0-4 Distribution: unstable Urgency: medium Maintainer: Ricardo Mones Changed-By: Ricardo Mones Description: sylpheed - Light weight e-mail client with GTK+ sylpheed-i18n - Locale data for Sylpheed (i18n support) sylpheed-plugins - Loadable modules for extending Sylpheed features Closes: 908063 Changes: sylpheed (3.7.0-4) unstable; urgency=medium . [ Hideki Yamane ] * Set Standards-Version: 4.1.4 with no change . [ Ricardo Mones ] * Patch to set SNI until available in new upstream release. Thanks to Antonio Ospite for the patch (Closes: #908063) * Depends: add sensible-utils to binary Checksums-Sha1: 0b941edbdbf044a6f6459051cbc08915bd3f7f8d 2281 sylpheed_3.7.0-4.dsc f170719fcb8c2ac2cc
Bug#906375: libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types)
Hi, * Emmanuel Bourg [2018-08-29 11:51]: On 28/08/2018 21:31, Jochen Sprickerhof wrote: As a quick fix we could probably hack around the visibility modifiers of Marshaller, but I guess that would be rather ugly. Just mentioning it for completeness. +1 for adjusting the xml-security API. I opened merge requests for this: https://salsa.debian.org/java-team/libxml-security-java/merge_requests/1 https://salsa.debian.org/java-team/libitext5-java/merge_requests/1 Note that the new libitext5 version has runtime errors still, but I have patches for the current Debian version to at lest fix this RC: https://salsa.debian.org/jspricke/libitext5-java/tree/5.5.6 Would be great if one of you could review them. Cheers Jochen signature.asc Description: PGP signature
Processed: Re: Bug#909023: git-annex: fail to copy file contents
Processing control commands: > severity -1 important Bug #909023 [git-annex] git-annex: fail to copy file contents Severity set to 'important' from 'grave' -- 909023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909023: git-annex: fail to copy file contents
control: severity -1 important Dear Marco, On Mon 17 Sep 2018 at 04:39PM +0200, Marco Pattaro wrote: > in short: after upgrading to version 6.20180913-1 I'm unable to sync file > contents. > > My layout is a central bare repository on a machine which runs an older > version > of git-annex (6.20160923-1) and anumber of client, direct, repositories all up > to date with the latest debian testing release. All repositories have > [annex] > version = 5 > > in their .git/config > > After upgrading it fails to do any of: > > $ git annex sync --content > or > $ git annex get > or > $ git annex copy > > with this error message: "fd:23: hClose: resource vanished (Broken pipe)" > > I'm pretty sure the issue is not in my ssh connection whish is working > properly > in other contexts, nor in git because the file index is synced correctly. > > Could this be an incompatibility between git-annex versions? It could be. Could you provide steps to reproduce, please? I.e. please try to reproduce the bug using a fresh repository and tell me exactly what you did. Then I will try to replicate the problem. I am downgrading the severity of the bug because while backwards compatibility is desirable, the lack of it does not render the package useless. -- Sean Whitton signature.asc Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 909099 gimagereader/3.2.3-3
Bug #909099 {Done: Philip Rinn } [gimagereader]
gimagereader: crashes at startup
Marked as fixed in versions gimagereader/3.2.3-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
909099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#909099: marked as done (gimagereader: crashes at startup)
Your message dated Tue, 18 Sep 2018 23:04:54 +0200
with message-id <58c18dc3-ba0b-2195-2a4a-8470f23cf...@inventati.org>
and subject line Re: Bug#909099: gimagereader: crashes at startup
has caused the Debian Bug report #909099,
regarding gimagereader: crashes at startup
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.)
--
909099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimagereader
Version: 3.2.3-2
Severity: grave
This is the answer I got from upstream, apparently it is a build issue.
Date: Tue, 04 Sep 2018 18:22:43 +0200
From: Sandro Mani
Subject: Re: gimagereader-gtk dumps core
Hi
I've been getting many of these lately: debian apparently updated their
tesseract version, and gImageReader needs to be rebuilt against the new
version.
If you are using the debian package from the regular repos, please ask
the maintainer to rebuild it.
Hope this helps
Sandro
On 04.09.2018 18:17, Francesco Potortì wrote:
> As soon as it starts from the command line on an up-to-date Debian
> system:
>
> $ gimagereader-gtk
> !strcmp(locale, "C"):Error:Assert failed:in file baseapi.cpp, line 201
> Gtk-Message: 18:14:49.170: GtkDialog mapped without a transient parent. This
> is discouraged.
> Process Process-10:
> Traceback (most recent call last):
>File "/usr/lib/python3.6/multiprocessing/process.py", line 258, in
> _bootstrap
> self.run()
>File "/usr/lib/python3.6/multiprocessing/process.py", line 93, in run
> self._target(*self._args, **self._kwargs)
>File "/usr/lib/python3/dist-packages/lios/ocr/ocr_engine_base.py", line
> 52, in
> image_file_name :
> child_conn.send(self.ocr_image_to_text(image_file_name))),
>File "/usr/lib/python3/dist-packages/lios/ocr/ocr_engine_tesseract.py",
> line 57, in ocr_image_to_text
> os.remove("/tmp/{0}_for_ocr.png".format(file_name.split("/")[-1]))
> FileNotFoundError: [Errno 2] No such file or directory:
> '/tmp/capitolato#speciale#005.png_for_ocr.png'
> Segmentation fault (core dumped)
> ~/ipin19/capitolato$ gimagereader-gtk
> !strcmp(locale, "C"):Error:Assert failed:in file baseapi.cpp, line 201
> Gtk-Message: 18:15:05.723: GtkDialog mapped without a transient parent. This
> is discouraged.
> Segmentation fault (core dumped)
>
>
>
> gImageReader 3.2.3 (rev )
>
> #1 0x55dbbde54077 in MainWindow::signalHandler(int) ()
> #2 0x7f386d15dfc0 in () at
> /lib/x86_64-linux-gnu/libc.so.6
> #3 0x7f3871a0c2e7 in ERRCODE::error(char const*, TessErrorLogCode, char
> const*, ...) const () at /usr/lib/x86_64-linux-gnu/libtesseract.so.4
> #4 0x7f3871843a9e in tesseract::TessBaseAPI::TessBaseAPI() () at
> /usr/lib/x86_64-linux-gnu/libtesseract.so.4
> #5 0x55dbbde37268 in Config::setDataLocations(int) ()
> #6 0x7f38703791a8 in
> Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) () at
> /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
> #7 0x7f386ed0af6d in g_closure_invoke () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #8 0x7f386ed1d8d1 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #9 0x7f386ed263f5 in g_signal_emit_valist () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #10 0x7f386ed26e0f in g_signal_emit () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #11 0x7f386fb6f7e5 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #12 0x7f386fb71da5 in gtk_combo_box_set_active () at
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #13 0x55dbbde386fb in ComboSetting::ComboSetting(Glib::ustring const&,
> Gtk::ComboBox*) ()
> #14 0x55dbbde34eef in Config::Config() ()
> #15 0x55dbbde56028 in MainWindow::MainWindow() ()
> #16 0x55dbbde9c7dd in Application::on_startup() ()
> #17 0x7f38708a7d2d in
> Gio::Application_Class::startup_callback(_GApplication*) () at
> /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
> #18 0x7f386ed0af6d in g_closure_invoke () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #19 0x7f386ed1de0e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #20 0x7f386ed263f5 in g_signal_emit_valist () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #21 0x7f386ed26e0f in g_signal_emit () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #22 0x7f386f4210a2 in g_application_register () at
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #23 0x7f386f4218b7 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #24 0x7f38708a78fb in Gio::A
Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure
Le 15/09/2018 à 17:42, Damyan Ivanov a écrit :
> -=| gregor herrmann, 14.09.2018 16:08:50 +0200 |=-
>> Control: tag -1 + unreproducible
>>
>> On Fri, 14 Sep 2018 16:52:38 +0300, Adrian Bunk wrote:
>>
>>> Source: libnet-server-mail-perl
>>> Version: 0.25-1
>>> Severity: serious
>>> Tags: ftbfs
>>>
>>> https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl&arch=all&ver=0.25-1&stamp=1536904015&raw=0
>>
>> Thanks for the bug report.
>>
>>> ...
>>> Test Summary Report
>>> ---
>>> t/starttls.t (Wstat: 9 Tests: 3 Failed: 0)
>>> Non-zero wait status: 9
>>> Parse errors: No plan found in TAP output
>>> Files=4, Tests=33, 2 wallclock secs ( 0.05 usr 0.04 sys + 0.67 cusr
>>> 0.20 csys = 0.96 CPU)
>>> Result: FAIL
>>> Failed 1/4 test programs. 0/33 subtests failed.
>>> make[1]: *** [Makefile:861: test_dynamic] Error 255
>>
>> Hm, the package builds for me.
>>
>>
>> The buildd failure is:
>>
>> # Error: TLS handshake failed SSL connect attempt failed at t/starttls.t
>> line 116.
>> # kill 9, 17145 (server)
>> t/starttls.t ..
>> ok 1 - Accepted client for Test01: STARTTLS support
>> ok 2 - Accepted client for Test02: STARTTLS invalid parameters
>> ok 3 - Accepted client for Test03: STARTTLS handshake
>> All 3 subtests passed
>>
>>
>> Line 116 in the test is:
>>
>>112 my $rv =
>>113 IO::Socket::SSL->start_SSL( $s,
>>114 SSL_verify_mode =>
>> IO::Socket::SSL::SSL_VERIFY_NONE, );
>>115
>>116 ( defined $rv && ref $rv eq 'IO::Socket::SSL' )
>>117 or die "TLS handshake failed >" .
>> IO::Socket::SSL::errstr();
>
>
> Building the package several times (sbuild) passes here most of the
> time and then:
>
> # Error: Can't call method "peerhost" on an undefined value at t/starttls.t
> line
> 131.
> # kill 9, 28330 (server)
> t/starttls.t ..
> ok 1 - Accepted client for Test01: STARTTLS support
> ok 2 - Accepted client for Test02: STARTTLS invalid parameters
> ok 3 - Accepted client for Test03: STARTTLS handshake
> All 3 subtests passed
>
> Adding
> $SIG{PIPE} = 'IGNORE';
> at the start of the test seems to make it pass all the time.
>
> I wonder if this is the correct fix.
>
> -- Damyan
Hello,
I added this hook without success. "reproducible" builds well [1] but
not buildd [2]
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnet-server-mail-perl.html)
[2] https://buildd.debian.org/status/package.php?p=libnet-server-mail-perl
Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
hi, On Tue, Sep 18, 2018 at 09:58:10AM +0200, Mattia Rizzolo wrote: > Package: ghostscript > Version: 9.20~dfsg-3.2+deb9u5 > Severity: serious > X-Debbugs-CC: t...@security.debian.org, Moritz Mühlenhoff , > reproducible-bui...@lists.alioth.debian.org > Control: affects -1 diffoscope > > Dear maintainer, > > after the latest ghostscript security update, ps2ascii started to crash: > > |% ps2ascii > /build/diffoscope-101~bpo9+1/.pybuild/pythonX.Y_3.5/build/tests/data/test1.ps > |Error: /typecheck in --.bind-- > |Operand stack: > | --nostringval-- false setshared true --dict:30/32(L)-- > typecheck --nostringval-- currentglobal .currentglobal > |Execution stack: > | %interp_exit .runexec2 --nostringval-- --nostringval-- > --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- > --nostringval-- false 1 %stopped_push 1998 2 3 %oparray_pop > 1997 2 3 %oparray_pop 1981 2 3 %oparray_pop 1868 2 3 > %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- > --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- > 2009 3 3 %oparray_pop --nostringval-- --nostringval-- > --dict:1267/1684(G)-- --nostringval-- 1936 %dict_continue > --nostringval-- 1974 9 4 %oparray_pop --nostringval-- > |Dictionary stack: > | --dict:1267/1684(G)-- --dict:0/20(G)-- --dict:81/200(L)-- > --dict:1267/1684(G)-- > |Current allocation mode is global > |Current file position is 44643 > |GPL Ghostscript 9.20: Unrecoverable error, exit code 1 > > > Downgrading to 9.20~dfsg-3.2+deb9u4 shows the problem is limited to the > latest update: > > |% ps2ascii > /build/diffoscope-101~bpo9+1/.pybuild/pythonX.Y_3.5/build/tests/data/test1.ps > | > | > |Today's date: February 28, 2016 > | > |1 > > > This also causes diffoscope (both 78 in stretch and whatever is in > stretch-backports at the moment) to FTBFS. Some updates: The issue is triggered by the 025_fb713b3818b52d8a6cf62c951eba2e1795ff9624.patch patch, which is http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=fb713b3818b52d8a6cf62c951eba2e1795ff9624 . Ghostscript built from git on fb713b3818b52d8a6cf62c951eba2e1795ff9624 does not seem to tigger the same problem, so if this is correct, we might miss a prerequisite to fb713b3818b52d8a6cf62c951eba2e1795ff9624 . Regards, Salvatore
Processed: affects 909076
Processing commands for cont...@bugs.debian.org: > affects 909076 + release.debian.org Bug #909076 [ghostscript] ghostscript: ps2ascii crashes: Error: /typecheck in --.bind-- Added indication that 909076 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 909076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907688: marked as done (activemq: FTBFS (Plugin org.apache.xbean:maven-xbean-plugin:4.2 or one of its dependencies could not be resolved))
Your message dated Tue, 18 Sep 2018 19:49:15 + with message-id and subject line Bug#907688: fixed in activemq 5.15.6-1 has caused the Debian Bug report #907688, regarding activemq: FTBFS (Plugin org.apache.xbean:maven-xbean-plugin:4.2 or one of its dependencies could not be resolved) 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.) -- 907688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:activemq Version: 5.15.4-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=maven dh_update_autotools_config -i -O--buildsystem=maven dh_autoreconf -i -O--buildsystem=maven dh_auto_configure -i -O--buildsystem=maven mh_patchpoms -plibactivemq-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i -O--buildsystem=maven /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=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [... snipped ...] [INFO] [INFO] --- maven-surefire-plugin:2.21.0:test (default-test) @ activemq-console --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.1.0:jar (default-jar) @ activemq-console --- [INFO] Building jar: /<>/activemq-console/target/activemq-console-5.15.4.jar [INFO] [INFO] --< org.apache.activemq:activemq-ra >--- [INFO] Building ActiveMQ :: RA 5.15.4 [11/15] [INFO] [ jar ]- [WARNING] The POM for org.apache.xbean:maven-xbean-plugin:jar:4.2 is missing, no dependency information available [INFO] [INFO] Reactor Summary: [INFO] [INFO] ActiveMQ 5.15.4 SUCCESS [ 0.063 s] [INFO] ActiveMQ :: Client . SUCCESS [ 10.458 s] [INFO] ActiveMQ :: Openwire Legacy Support SUCCESS [ 2.743 s] [INFO] ActiveMQ :: JAAS ... SUCCESS [ 0.306 s] [INFO] ActiveMQ :: Broker . SUCCESS [ 4.086 s] [INFO] ActiveMQ :: KahaDB Store ... SUCCESS [ 2.348 s] [INFO] ActiveMQ :: STOMP Protocol . SUCCESS [ 0.500 s] [INFO] ActiveMQ :: MQTT Protocol .. SUCCESS [ 0.535 s] [INFO] ActiveMQ :: JDBC Store . SUCCESS [ 0.663 s] [INFO] ActiveMQ :: Console SUCCESS [ 0.958 s] [INFO] ActiveMQ :: RA . FAILURE [ 0.002 s] [INFO] ActiveMQ :: Run Jar SKIPPED [INFO] ActiveMQ :: Shiro .. SKIPPED [INFO] ActiveMQ :: Spring . SKIPPED [INFO] ActiveMQ :: Log4j Appender 5.15.4 .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 24.108 s [INFO] Finished at: 2018-08-28T17:44:53Z [INFO] [ERROR] Plugin org.apache.xbean:maven-xbean-plugin:4.2 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.
Processed: Bug #907688 in activemq marked as pending
Processing control commands: > tag -1 pending Bug #907688 [src:activemq] activemq: FTBFS (Plugin org.apache.xbean:maven-xbean-plugin:4.2 or one of its dependencies could not be resolved) Added tag(s) pending. -- 907688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907688: Bug #907688 in activemq marked as pending
Control: tag -1 pending Hello, Bug #907688 in activemq 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/activemq/commit/2d0e13bac71ad881371ef9010cceb674470723b1 Add a new maven rule for maven-xbean-plugin and fix the current FTBFS. Closes: #907688 (this message was generated automatically) -- Greetings https://bugs.debian.org/907688
Bug#909040: davmail: A JNI error has occurred
Hi, > This is a jarwrapper bug, the CheckProperty class was compiled without > specifying the source/target level, thus defaulting to Java 10 bytecode > (version 54.0). Thanks but the second part of the stacktrace is still on davmail. I need to investigate between these options: 1) make the binary package use java10 but this will require an upload when java11 is out 2) wrapper script to force the user to use java10 3) make it possible to compile davmail with target=1.8 and thus without --add-exports I'd be happy to get advice on this. I think I'll try 3) first. Alex
Bug#909089: debhelper: GNU configure $prefix expanded too early?
On 2018-09-18 14:09 +0300, Peter Pentchev wrote:
> Package: debhelper
> Version: 11.4
> Severity: serious
>
> Hi,
>
> Thanks for maintaining and extending debhelper!
>
> I don't have much information right now, maybe I'll look into it in
> the evening (Eastern European time), but trying to build gforth in
> a chroot containing debhelper-11.4 results in a package where all
> the paths passed to the GNU configure script as "\$prefix/something"
> are actually defined as "/something", thus placing binaries in /bin,
> include files in /include, etc. Installing debhelper-11.3.5 fixes
> the problem.
Bisection shows that commit a7ec05c10093f ("dh: Track which options have
been passed") has triggered the problem. I had a look at the gforth
build logs with debhelper 11.3.5 and 11.4, but could not spot an obvious
cause. Maybe Niels has more luck.
Cheers,
Sven
Bug#879905: glee: source for GLee.c and GLee.h is missing
On Mon, 6 Nov 2017 02:08:44 +0100 Steve Cotton wrote: > On Fri, Oct 27, 2017 at 07:55:52AM +0200, Steve Cotton wrote: > > On Thu, 19 Oct 2017 22:47:00, Ximin Luo wrote: > > > These files are clearly not source code. But luckily it should > > > be possible to regenerate them from the git repo I mentioned: > > > > > > > [..] https://github.com/kallisti5/glee > > > > It seems that repo is also not the complete source, the build > > steps in CMakeLists.txt download specs for the GL extensions from > > http://www.opengl.org/registry/ > > It doesn't manage to download the specifications any more, which is > probably because the website has changed since 2011. OTOH, anything > that works with Debian's 2009 version of GLee can only be using > extensions that existed in 2009. > > AFAICS, what GLeeGen creates is a mix of: > > 1. An easy wrapper for checking if an extension is supported > 2. The DFSG-free files which are now packaged in khronos-api > 3. The specifications under Khronos' speccopyright (not DFSG-free) > > The speccopyright means that we can't make a DFSG version of GLee, but > it also seems that it might be easier to just fix the rdeps to not use > GLee at all. The wrapper for checking if extensions are supported > could be ported to use the khronos-api, if it's needed at all. > > Looking at the packages that use GLee: > > Fife: only a few extensions, all of them now in khronos-api. Would > need the wrapper function. > > FS-UAE: build-depends on glee-dev, but the changelog includes "use > GLEW instead of GLee", none of the binaries depend on libglee, and the > two #includes in the source are commented out. Bug #880944 logged. > > Out Of Order: transitive dependency via Sludge > > Pink Pony: build-depends on glee-dev, but doesn't #include GLee.h > anywhere. Builds and runs fine without it (bug #880941 logged for > dropping the dependency). > > Sludge: if a compile-time check finds OpenGL ES 2.0, the code assumes > that all of the extensions that it wants are already present, and > doesn't use GLee's wrapper. > > Unknown Horizons: transitive dependency via Fife > > Steve > > I ported sludge to use glew instead of glee, and it was the last rdep. glee can be removed now. Best, Tobias
Bug#909068: marked as done (mypy: Crash)
Your message dated Tue, 18 Sep 2018 19:04:28 +
with message-id
and subject line Bug#909068: fixed in mypy 0.630-2
has caused the Debian Bug report #909068,
regarding mypy: Crash
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.)
--
909068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mypy
Version: 0.630-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
$ mypy
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 578, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 895, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (mypy-extensions 0.5.0.dev0
(/usr/lib/python3/dist-packages),
Requirement.parse('mypy_extensions<0.5.0,>=0.4.0'), {'mypy'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/mypy", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3105,
in
@_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3089,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3118,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 580, in
_build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 593, in
_build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 781, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'mypy_extensions<0.5.0,>=0.4.0'
distribution was not found and is required by mypy
Best
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mypy depends on:
ii python3 3.6.6-1
ii python3-mypy 0.630-1
mypy recommends no packages.
Versions of packages mypy suggests:
pn mypy-doc
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 0.630-2
We believe that the bug you reported is fixed in the latest version of
mypy, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated mypy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Sep 2018 11:38:12 -0700
Source: mypy
Binary: mypy mypy-doc python3-mypy
Architecture: source
Version: 0.630-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Michael R. Crusoe
Description:
mypy - optional static typing for Python
mypy-doc - documentation for mypy
python3-mypy - public modules for mypy (Python 3)
Closes: 909068 909070
Changes:
mypy (0.630-2) unstable; urgency=medium
.
* Fix the version of mypy_extension. Closes: #909070, #909068
Checksums-Sha1:
3c36aef1dd9852f7d29d88be9fa62b827ce348d3 2213 mypy_0.630-2.dsc
e1790fc70e70d08c2bf6cb81faf5d6810138e0d8 7400 mypy_0.630-2.debian.tar.xz
23c0d65745a8098f17e29cd3ebf531b92f8fc821 9294 mypy_0.630-2_source.buildinfo
Checksums-Sha256:
13370fedca9c22c4aaee22b18959e61830a611d39e051b14bceeb11831b18024 2213
mypy_0.630-2.dsc
1c2c18b2758002e96a6bfc9bb22c82142bee740d07e9
Bug#909070: marked as done (mypy: autopkgtest regression: The 'mypy_extensions<0.5.0,>=0.4.0' distribution was not found)
Your message dated Tue, 18 Sep 2018 19:04:28 +
with message-id
and subject line Bug#909070: fixed in mypy 0.630-2
has caused the Debian Bug report #909070,
regarding mypy: autopkgtest regression: The 'mypy_extensions<0.5.0,>=0.4.0'
distribution was not found
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.)
--
909070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mypy
Version: 0.630-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of mypy the autopkgtest of mypy fails in testing
when that autopkgtest is run with the binary packages of mypy from
unstable. It passes when run with only packages from testing. I copied
some of the output at the bottom of this report.
Reading the error message, mypy fails to run because because it is
missing a dependency. Therefore I file this bug at severity serious,
please downgrade if I misjudged.
Even before I filed this bug, this regression is contributing to the
delay of the migration to testing [1]. Can you please investigate the
situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=mypy
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mypy/1010214/log.gz
autopkgtest [03:19:46]: test command1: mypy --help
autopkgtest [03:19:46]: test command1: [---
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
578, in _build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
895, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
786, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (mypy-extensions 0.5.0.dev0
(/usr/lib/python3/dist-packages),
Requirement.parse('mypy_extensions<0.5.0,>=0.4.0'), {'mypy'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/mypy", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3105, in
@_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3089, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3118, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
580, in _build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
593, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
781, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'mypy_extensions<0.5.0,>=0.4.0'
distribution was not found and is required by mypy
autopkgtest [03:19:47]: test command1: ---]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 0.630-2
We believe that the bug you reported is fixed in the latest version of
mypy, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated mypy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Sep 2018 11:38:12 -0700
Source: mypy
Binary: mypy mypy-doc python3-mypy
Architecture: source
Version: 0.630-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Michael R. Crusoe
Description:
mypy - optional static typin
Bug#882287: xul-ext-noscript: new upstream version
Jerome BENOIT wrote... > Please consider to the new upstream version 10 > given that the current version of noscript provided in Stretch > does not work with firefox-esr 60.2 recently brought in Stretch. +1 In an attempt to have a usable noscript again, I tried to build the new version but this failed: | make[1]: Entering directory '/<>' | uglifyjs -o \ | chrome/content/noscript/antlr.js \ | debian/antlr3-all.js | fs.js:646 | return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); | ^ | | Error: ENOENT: no such file or directory, open 'chrome/content/noscript/antlr.js' | at Object.fs.openSync (fs.js:646:18) | at Object.fs.writeFileSync (fs.js:1299:33) | at done (/usr/lib/nodejs/uglify-js/bin/uglifyjs:527:16) | at cb (/usr/lib/nodejs/uglify-js/bin/uglifyjs:324:39) | at /usr/lib/nodejs/uglify-js/bin/uglifyjs:391:9 | at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:511:3) This needs somebody with a deeper understanding of the webext concept the the build system. Christoph signature.asc Description: PGP signature
Bug#909126: ompl-plannerarena: missing Breaks+Replaces: ompl-demos (<< 1.4)
Package: ompl-plannerarena Version: 1.4.0+ds1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../ompl-plannerarena_1.4.0+ds1-1_all.deb ... Unpacking ompl-plannerarena (1.4.0+ds1-1) ... dpkg: error processing archive /var/cache/apt/archives/ompl-plannerarena_1.4.0+ds1-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/plannerarena.1.gz', which is also in package ompl-demos 1.2.1+ds1-1 Errors were encountered while processing: /var/cache/apt/archives/ompl-plannerarena_1.4.0+ds1-1_all.deb cheers, Andreas ompl-demos=1.2.1+ds1-1_ompl-plannerarena=1.4.0+ds1-1.log.gz Description: application/gzip
Bug#909123: ruby-active-model-serializers: /usr/bin/rubocop is already shipped by the rubocop package
Package: ruby-active-model-serializers Version: 0.10.7-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. Adding Breaks+Replaces is probably not the correct solution in this case. >From the attached log (scroll to the bottom...): Preparing to unpack .../ruby-active-model-serializers_0.10.7-1_all.deb ... Unpacking ruby-active-model-serializers (0.10.7-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-active-model-serializers_0.10.7-1_all.deb (--unpack): trying to overwrite '/usr/bin/rubocop', which is also in package rubocop 0.52.1+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/ruby-active-model-serializers_0.10.7-1_all.deb cheers, Andreas rubocop=0.52.1+dfsg-1_ruby-active-model-serializers=0.10.7-1.log.gz Description: application/gzip
Bug#909089: debhelper: GNU configure $prefix expanded too early?
Control: tags -1 moreinfo On Tue, 18 Sep 2018 14:09:03 +0300 Peter Pentchev wrote: > Package: debhelper > Version: 11.4 > Severity: serious > > Hi, > > Thanks for maintaining and extending debhelper! > > I don't have much information right now, maybe I'll look into it in > the evening (Eastern European time), but trying to build gforth in > a chroot containing debhelper-11.4 results in a package where all > the paths passed to the GNU configure script as "\$prefix/something" > are actually defined as "/something", thus placing binaries in /bin, > include files in /include, etc. Installing debhelper-11.3.5 fixes > the problem. > > Thanks again for everything you're doing for debhelper and Debian, > and keep up the great work! > > G'luck, > Peter > > [...] Hi Peter, Could you please provide the logs of the build (preferably with "export DH_VERBOSE=1")? Thanks, ~Niels
Processed: Re: debhelper: GNU configure $prefix expanded too early?
Processing control commands: > tags -1 moreinfo Bug #909089 [debhelper] debhelper: GNU configure $prefix expanded too early? Added tag(s) moreinfo. -- 909089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908063: Bug #908063 in sylpheed marked as pending
Control: tag -1 pending Hello, Bug #908063 in sylpheed 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/sylpheed-team/sylpheed/commit/29834adc1a6ff7685990097db08e2ba1bea39c74 Patch to set SNI until available in new upstream release Closes: #908063 Thanks: Antonio Ospite for the patch (this message was generated automatically) -- Greetings https://bugs.debian.org/908063
Bug#908063: marked as done (sylpheed: TLS connection to imap.gmail.com returns self-signed certificate with openssl 1.1.0)
Your message dated Tue, 18 Sep 2018 17:17:08 + with message-id <5ba1331425dc2_22902b1a0fbb90dc28...@godard.mail> and subject line Bug #908063 in sylpheed fixed has caused the Debian Bug report #908063, regarding sylpheed: TLS connection to imap.gmail.com returns self-signed certificate with openssl 1.1.0 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.) -- 908063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sylpheed Version: 3.7.0-3+b1 Severity: important Tags: upstream patch Dear Maintainer, when using openssl 1.1.0 (now in Unstable) the gmail servers require clients to set the Server Name Indication, responding with an invalid self-signed certificate if this is not the case. Sylpheed does not set the SNI. Here is a link to the upstream bug report in which I provide a patch and a link to a better explanation: https://sylpheed.sraoss.jp/redmine/issues/306 Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylpheed depends on: ii libassuan0 2.5.1-2 ii libatk1.0-0 2.28.1-1 ii libc62.27-6 ii libcairo21.15.12-1 ii libcompfaceg11:1.5.2-5+b2 ii libenchant1c2a 1.6.0-11.1 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libfribidi0 1.0.5-3 ii libgdk-pixbuf2.0-0 2.36.12-2 ii libglib2.0-0 2.58.0-2 ii libgpg-error01.32-1 ii libgpgme11 1.11.1-1 ii libgtk2.0-0 2.24.32-3 ii libgtkspell0 2.0.16-1.2 ii libldap-2.4-22.4.46+dfsg-5 ii libonig5 6.8.2-1 ii libpango-1.0-0 1.42.4-2 ii libpangocairo-1.0-0 1.42.4-2 ii libpangoft2-1.0-01.42.4-2 ii libssl1.11.1.1~~pre9-1 ii pinentry-gtk21.1.0-1+b1 Versions of packages sylpheed recommends: ii aspell-it [aspell-dictionary] 2.4-20070901-0-3 ii bogofilter 1.2.4+dfsg1-13 ii bsfilter 1:1.0.19-2 ii ca-certificates20180409 ii sylpheed-i18n 3.7.0-3 Versions of packages sylpheed suggests: pn claws-mail-tools ii curl 7.61.0-1 pn sylpheed-doc ii sylpheed-plugins 3.7.0-3+b1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? --- End Message --- --- Begin Message --- Hello, Bug #908063 in sylpheed reported by you has been fixed in the Git repository. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/sylpheed-team/sylpheed/commit/29834adc1a6ff7685990097db08e2ba1bea39c74 Patch to set SNI until available in new upstream release Closes: #908063 Thanks: Antonio Ospite for the patch (this message was generated automatically) -- Greetings https://bugs.debian.org/908063--- End Message ---
Processed: Bug #908063 in sylpheed marked as pending
Processing control commands:
> tag -1 pending
Bug #908063 {Done: Ricardo Mones } [sylpheed] sylpheed: TLS
connection to imap.gmail.com returns self-signed certificate with openssl 1.1.0
Added tag(s) pending.
--
908063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: mod-gnutls FTBFS: FAIL: test-16_view-status.bash
Processing commands for cont...@bugs.debian.org: > tag 907008 + patch Bug #907008 [src:mod-gnutls] mod-gnutls FTBFS: FAIL: test-16_view-status.bash Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 907008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909120: camitk FTBFS: tests segfault
Source: camitk Version: 4.1.2-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/camitk.html ... The following tests FAILED: 27 - action-editframes-level1-1 (SEGFAULT) 28 - action-editframes-level1-2 (SEGFAULT) 29 - action-cropvolume-level1-1 (SEGFAULT) 30 - action-cropvolume-level1-2 (SEGFAULT) 31 - action-cropvolume-level1-3 (SEGFAULT) 32 - action-imagelut-level1-1 (SEGFAULT) 33 - action-imagelut-level1-2 (SEGFAULT) 34 - action-imagelut-level1-3 (SEGFAULT) 35 - action-imageresampling-level1-1 (SEGFAULT) 36 - action-imageresampling-level1-2 (SEGFAULT) 37 - action-imageresampling-level1-3 (SEGFAULT) 38 - action-multipicking-level1-1 (SEGFAULT) 39 - action-multipicking-level1-2 (SEGFAULT) 40 - action-multipicking-level1-3 (SEGFAULT) 41 - action-pixelcolorchanger-level1-1 (SEGFAULT) 42 - action-pixelcolorchanger-level1-2 (SEGFAULT) 43 - action-pixelcolorchanger-level1-3 (SEGFAULT) 44 - action-reconstruction-level1-1 (SEGFAULT) 45 - action-reconstruction-level1-2 (SEGFAULT) 46 - action-reconstruction-level1-3 (SEGFAULT) 47 - action-reconstruction-integration-test (Failed) 48 - action-reorientimage-level1-1 (SEGFAULT) 49 - action-reorientimage-level1-2 (SEGFAULT) 50 - action-reorientimage-level1-3 (SEGFAULT) 51 - action-showin3d-level1-1 (SEGFAULT) 52 - action-showin3d-level1-2 (SEGFAULT) 53 - action-showin3d-level1-3 (SEGFAULT) 54 - action-volumerendering-level1-1 (SEGFAULT) 55 - action-volumerendering-level1-2 (SEGFAULT) 56 - action-volumerendering-level1-3 (SEGFAULT) 57 - action-imageacquisition-level1-1 (SEGFAULT) 58 - action-imageacquisition-level1-2 (SEGFAULT) 59 - action-basicmesh-level1-1 (SEGFAULT) 60 - action-basicmesh-level1-2 (SEGFAULT) 61 - action-basicmesh-level1-3 (SEGFAULT) 62 - action-basicmesh-level1-4 (SEGFAULT) 63 - action-basicmesh-level1-5 (SEGFAULT) 64 - action-basicmesh-level1-6 (SEGFAULT) 65 - action-basicmesh-level1-7 (SEGFAULT) 66 - action-basicmesh-level1-8 (SEGFAULT) 67 - action-basicmesh-level1-9 (SEGFAULT) 68 - action-basicmesh-level1-10 (SEGFAULT) 69 - action-basicmesh-level1-11 (SEGFAULT) 70 - action-basicmesh-level1-12 (SEGFAULT) 71 - action-basicmesh-level1-13 (SEGFAULT) 72 - action-basicmesh-level1-14 (SEGFAULT) 73 - action-basicmesh-level1-15 (SEGFAULT) 74 - action-basicmesh-level1-16 (SEGFAULT) 75 - action-basicmesh-level1-17 (SEGFAULT) 76 - action-basicmesh-level1-18 (SEGFAULT) 77 - action-basicmesh-level1-19 (SEGFAULT) 78 - action-basicmesh-level1-20 (SEGFAULT) 79 - action-basicmesh-level1-21 (SEGFAULT) 80 - action-basicmesh-level1-22 (SEGFAULT) 81 - action-basicmesh-level1-23 (SEGFAULT) 82 - action-basicmesh-level1-24 (SEGFAULT) 83 - action-basicmesh-level1-25 (SEGFAULT) 84 - action-basictopology-level1-1 (SEGFAULT) 85 - action-basictopology-level1-2 (SEGFAULT) 86 - action-basictopology-level1-3 (SEGFAULT) 87 - action-basictopology-level1-4 (SEGFAULT) 88 - action-basictopology-level1-5 (SEGFAULT) 89 - action-basictopology-level1-6 (SEGFAULT) 90 - action-basictopology-level1-7 (SEGFAULT) 91 - action-basictopology-level1-8 (SEGFAULT) 92 - action-basictopology-level1-9 (SEGFAULT) 93 - action-basictopology-level1-10 (SEGFAULT) 94 - action-basictopology-level1-11 (SEGFAULT) 95 - action-basictopology-level1-12 (SEGFAULT) 96 - action-basictopology-level1-13 (SEGFAULT) 97 - action-basictopology-level1-14 (SEGFAULT) 98 - action-basictopology-level1-15 (SEGFAULT) 99 - action-meshprocessing-level1-1 (SEGFAULT) 100 - action-meshprocessing-level1-2 (SEGFAULT) 101 - action-meshprocessing-level1-3 (SEGFAULT) 102 - action-meshprocessing-level1-4 (SEGFAULT) 103 - action-meshprocessing-level1-5 (SEGFAULT) 104 - action-meshprocessing-level1-6 (SEGFAULT) 105 - action-meshprocessing-level1-7 (SEGFAULT) 106 - action-meshprocessing-level1-8 (SEGFAULT) 107 - action-meshprocessing-level1-9 (SEGFAULT) 108 - action-meshprocessing-level1-10 (SEGFAULT) 109 - action-meshprocessing-level1-11 (SEGFAULT) 110 - action-meshprocessing-level1-12 (SEGFAULT) 111 - action-meshprocessing-level1-13 (SEGFAULT) 112 - action-meshprocessing-level1-14 (SEGFAULT) 113 - action-meshprocessing-level1-15 (SEGFAULT) 114 - action-meshprocessing-level1-16 (SEGFAULT) 115 - action-meshprocessing-level1-17
Bug#907008: mod-gnutls FTBFS: FAIL: test-16_view-status.bash
tag 907008 + patch thanks Hello, As pointed out, cipher suites removed in latest gnutls is causing the test case to fail. The attached patch fixes the failure. It changes the priority string to match the latest default cipher suite. The patch is against upstream code. Thanks, -- Sunil From 45c47fb511257edba59775cb731fdf377553a4ba Mon Sep 17 00:00:00 2001 From: Sunil Mohan Adapa Date: Tue, 18 Sep 2018 09:41:47 -0700 Subject: [PATCH] Fix test 16-view-status by changing priority string From gnutls 3.5.19 release notes: "The ciphers utilizing HMAC-SHA384 and SHA256 have been removed from the default priority strings. They are not necessary for compatibility or other purpose and provide no advantage over their SHA1 counter-parts, as they all depend on the legacy TLS CBC block mode." Pick a new priority string such that the cipher suite matches the default negotiated by gnutls 3.5.19 server and client without explicitly setting a priority string. --- test/tests/16_view-status/gnutls-cli.args | 2 +- test/tests/16_view-status/output | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/test/tests/16_view-status/gnutls-cli.args b/test/tests/16_view-status/gnutls-cli.args index aca8ac0..470925b 100644 --- a/test/tests/16_view-status/gnutls-cli.args +++ b/test/tests/16_view-status/gnutls-cli.args @@ -1,2 +1,2 @@ --x509cafile=authority/x509.pem ---priority=NONE:+VERS-TLS1.2:+AES-128-CBC:+SHA256:+RSA:+COMP-NULL:+SIGN-RSA-SHA256 +--priority=NONE:+VERS-TLS1.2:+ECDHE-RSA:+CURVE-SECP256R1:+AES-256-GCM:+AEAD:+COMP-NULL:+SIGN-RSA-SHA1 diff --git a/test/tests/16_view-status/output b/test/tests/16_view-status/output index 7786244..8bfb45a 100644 --- a/test/tests/16_view-status/output +++ b/test/tests/16_view-status/output @@ -1,5 +1,5 @@ Using TLS:yes -Current TLS session:(TLS1.2)-(RSA)-(AES-128-CBC)-(SHA256) +Current TLS session:(TLS1.2)-(ECDHE-RSA-SECP256R1)-(AES-256-GCM) - Peer has closed the GnuTLS connection -- 2.18.0 signature.asc Description: OpenPGP digital signature
Bug#909092: marked as done (tmuxinator: missing dependency on ruby-xdg)
Your message dated Tue, 18 Sep 2018 16:23:15 + with message-id and subject line Bug#909092: fixed in tmuxinator 0.12.0-2 has caused the Debian Bug report #909092, regarding tmuxinator: missing dependency on ruby-xdg 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.) -- 909092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tmuxinator Version: 0.12.0-1 Severity: serious Justification: Policy 3.5 any tmuxinator command prints the following trace: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- xdg (LoadError) from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' from /usr/lib/ruby/vendor_ruby/tmuxinator.rb:6:in `' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' from /usr/bin/tmuxinator:5:in `' /usr/lib/ruby/vendor_ruby/tmuxinator.rb:6 is require "xdg" but the tmuxinator package does not declare a dependency on "ruby-xdg". after manually installing ruby-xdg, tmuxinator works as expected. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages tmuxinator depends on: ii ruby 1:2.5.1 ii ruby-erubis 2.7.0-3 ii ruby-thor0.19.4-1 ii tmux 2.7-1+b1 tmuxinator recommends no packages. tmuxinator suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tmuxinator Source-Version: 0.12.0-2 We believe that the bug you reported is fixed in the latest version of tmuxinator, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Youhei SASAKI (supplier of updated tmuxinator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Sep 2018 00:52:33 +0900 Source: tmuxinator Binary: tmuxinator Architecture: source all Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Youhei SASAKI Description: tmuxinator - Create and manage tmux sessions easily Closes: 909092 Changes: tmuxinator (0.12.0-2) unstable; urgency=medium . * d/control: Add Depends: ruby-xdg (Closes: #909092) Checksums-Sha1: 99b49770a00cd1f17e7739a9e6a434cde43b63de 2179 tmuxinator_0.12.0-2.dsc c3921e1cde237983ab575c0880c9075baf6afde4 4016 tmuxinator_0.12.0-2.debian.tar.xz fdff0a662fbe1530eeaecf968d72e23683c3064c 22488 tmuxinator_0.12.0-2_all.deb 47bcc75068df6a61ec0e74dd354452286b7f6b35 7981 tmuxinator_0.12.0-2_amd64.buildinfo Checksums-Sha256: 82cb61cae8147397557621a62effaeeb7ad1aec9531a2b3bf37f5dd17773c38e 2179 tmuxinator_0.12.0-2.dsc 51fb1decb74717a8aabe3b8740408756080748deb0e3b2093fbad7258271f177 4016 tmuxinator_0.12.0-2.debian.tar.xz 234db9d137e3776f3e6df04fdfc56eb96b34a8254ab3ef2826a6a4c1726f736f 22488 tmuxinator_0.12.0-2_all.deb a5114819b51fef1838b9a9a87ca416d028f764adfea01cae011f703d1e665731 7981 tmuxinator_0.12.0-2_amd64.buildinfo Files: b9107475a05631ddf02d879c2b5b6586 2179 utils optional tmuxinator_0.12.0-2.dsc e36ce89e43c39d98e24470ae0c945a7b 4016 utils optional tmuxinator_0.12.0-2.debian.tar.xz 611a4a1d1e2c0140506e757d36ab2825 22488 utils optional tmuxinator_0.12.0-2_all.deb 350b04fb05c4e52028640459de32f66b 7981 utils optional tmuxinator_0.12.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZqTqcE/iQFWNasLmk5TzVIkdfgcFAluhH8cACgkQk5TzVIkd fgfq8RAAtF7VX1+ZQKJ10V4S8zfUk/6+hRAlBkBzGOEXRKnnFn0E4PFS73sMJ4vf +Vq37WbV6wrSkMs9CYz8FMaGg0vgTzRJcobSoGNz/KsShkANo9cFJAAzUoEaZPP0 W2ivLxqWNR5dxRBtHR775MBQVxhpVrNLo8wm5i6iydIMRigOqq+luz2XN
Bug#909092: Bug #909092 in tmuxinator marked as pending
Control: tag -1 pending Hello, Bug #909092 in tmuxinator 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/ruby-team/tmuxinator/commit/9ce93438810d1e0b828dd252e26ddc3bcaa3f161 d/control: Add Depends: ruby-xdg (Closes: #909092) Signed-off-by: Youhei SASAKI (this message was generated automatically) -- Greetings https://bugs.debian.org/909092
Processed: Bug #909092 in tmuxinator marked as pending
Processing control commands: > tag -1 pending Bug #909092 [tmuxinator] tmuxinator: missing dependency on ruby-xdg Added tag(s) pending. -- 909092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909084: [Pkg-zsh-devel] Bug#909084: Bug#909084: Missing pcre module
Control: clone -1 -2 Control: retitle -2 Build should fail when PCRE is not available Control: severity -2 wishlist Axel Beckert wrote on Tue, Sep 18, 2018 at 11:53:36 +0200: > Yuri D'Elia wrote: > > In the last release, the pcre module does not seem to be built anymore. > > This causes "setopt rematch_pcre" to fail: > > > > failed to load module `zsh/pcre': > > /usr/lib/x86_64-linux-gnu/zsh/5.6.2/zsh/pcre.so: cannot open shared object > > file: No such file or directory > > -pcre-match not available for regex > > Thanks for the bug report. I just noticed it, too. > > I seem to have missed that the Recommends vanished because of the > according plugin files were no more built. The upstream build system treats PCRE as an optional dependency. In Debian, however, we should have the build fail hard when PCRE is not available, for compatibility reasons. Hereby filing that as #-2. Off the top of my head, we have several options: 1. Pass --with-pcre=foo to configure *and* make sure that configure dies if pcre is not found. (The configure.ac patch can be upstreamed.) 2. After running configure, check that the pcre line in config.modules has the expected values. (not upstreamable) 3. Patch Test/V07pcre to fail, rather than skip, if the PCRE module was not built. (not upstreamable) We can do more than one of these, e.g., #1+#3. Cheers, Daniel
Processed: Re: [Pkg-zsh-devel] Bug#909084: Bug#909084: Missing pcre module
Processing control commands: > clone -1 -2 Bug #909084 [zsh] Missing pcre module Bug 909084 cloned as bug 909114 > retitle -2 Build should fail when PCRE is not available Bug #909114 [zsh] Missing pcre module Changed Bug title to 'Build should fail when PCRE is not available' from 'Missing pcre module'. > severity -2 wishlist Bug #909114 [zsh] Build should fail when PCRE is not available Severity set to 'wishlist' from 'serious' -- 909084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909084 909114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found zfs-linux/0.7.9-3
Processing commands for cont...@bugs.debian.org: > found 909096 zfs-linux/0.7.9-3 Bug #909096 [zfs-linux] zfs-dkms 0.7.9-3 build fails on 4.18.0-1-amd64 cause spl-0.7.9 stuff Bug #908290 [zfs-linux] Please package 0.7.11 Marked as found in versions zfs-linux/0.7.9-3. Marked as found in versions zfs-linux/0.7.9-3. > End of message, stopping processing here. Please contact me if you need assistance. -- 908290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908290 909096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909023: works between two 6.20180913-1 repos
I tried with two clean repositories, one bare and one non-bare. Initially the bare one was from stretch (6.20170101-1+deb9u2) and the other from testing (6.20180913-1), the issue sowed up. Then I upgraded the bare one from stretch/backports (6.20180913-1~bpo9+1) nd... it worked! So I guess this is just a backward compatibility issue, would be nice to know if there's any chance to fix it or else I'm going to move my central repo on some other machine on which I can keep git-annex more up to date. thanks m
Processed: Re: [zfs-dkms]
Processing commands for cont...@bugs.debian.org: > reassign 909096 zfs-linux Bug #909096 [zfs-dkms] zfs-dkms 0.7.9-3 build fails on 4.18.0-1-amd64 cause spl-0.7.9 stuff Bug reassigned from package 'zfs-dkms' to 'zfs-linux'. No longer marked as found in versions zfs-linux/0.7.9-3. Ignoring request to alter fixed versions of bug #909096 to the same values previously set > forcemerge 908290 909096 Bug #908290 [zfs-linux] Please package 0.7.11 Bug #909096 [zfs-linux] zfs-dkms 0.7.9-3 build fails on 4.18.0-1-amd64 cause spl-0.7.9 stuff Severity set to 'serious' from 'normal' Added tag(s) sid, buster, and patch. Merged 908290 909096 > End of message, stopping processing here. Please contact me if you need assistance. -- 908290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908290 909096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): [zfs-dkms]
Processing control commands: > forcemerge 908290 -1 Bug #908290 [zfs-linux] Please package 0.7.11 Unable to merge bugs because: package of #909096 is 'zfs-dkms' not 'zfs-linux' Failed to forcibly merge 908290: Did not alter merged bugs. -- 908290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908290 909096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 908290 909096
Processing commands for cont...@bugs.debian.org: > forcemerge 908290 909096 Bug #908290 [zfs-linux] Please package 0.7.11 Unable to merge bugs because: package of #909096 is 'zfs-dkms' not 'zfs-linux' Failed to forcibly merge 908290: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 908290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908290 909096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fix severities
Processing commands for cont...@bugs.debian.org: > severity 868893 serious Bug #868893 [screenruler] screenruler: Missing dependency prevents screenruler from starting Severity set to 'serious' from 'important' > tags 868893 buster sid Bug #868893 [screenruler] screenruler: Missing dependency prevents screenruler from starting Added tag(s) buster and sid. > severity 899067 serious Bug #899067 [screenruler] screenruler: does not start: `loop': wrong number of arguments Severity set to 'serious' from 'important' > tags 899067 buster sid Bug #899067 [screenruler] screenruler: does not start: `loop': wrong number of arguments Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 868893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868893 899067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908134: marked as done (libpodofo-dev: Wrong linker flag -lpodofo-0 returned from pkg-config)
Your message dated Tue, 18 Sep 2018 14:41:14 + with message-id and subject line Bug#908134: fixed in libpodofo 0.9.5-11 has caused the Debian Bug report #908134, regarding libpodofo-dev: Wrong linker flag -lpodofo-0 returned from pkg-config 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.) -- 908134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpodofo-dev Version: 0.9.6~rc1+dfsg-1 Severity: important Dear Maintainer, When I do pkg-config --libs libpodofo-0, I get: -lpodofo-0 However, using this flag, the linker will fail with /usr/bin/ld: cannot find -lpodofo-0 If I just use -lpodofo, everything is fine. This is a problem for me as I am using meson to build my project, and this uses pdk-config to get the correct flags -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (400, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpodofo-dev depends on: ii libboost-dev1.62.0.1 ii libpodofo0.9.6 0.9.6~rc1+dfsg-1 ii libssl-dev 1.1.0h-4 libpodofo-dev recommends no packages. libpodofo-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libpodofo Source-Version: 0.9.5-11 We believe that the bug you reported is fixed in the latest version of libpodofo, 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. Mattia Rizzolo (supplier of updated libpodofo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Sep 2018 15:40:47 +0200 Source: libpodofo Binary: libpodofo-dev libpodofo-utils libpodofo0.9.5 Architecture: source Version: 0.9.5-11 Distribution: unstable Urgency: medium Maintainer: Mattia Rizzolo Changed-By: Mattia Rizzolo Description: libpodofo-dev - PoDoFo development files libpodofo-utils - PoDoFo utilities libpodofo0.9.5 - PoDoFo - library to work with the PDF file format Closes: 908134 Changes: libpodofo (0.9.5-11) unstable; urgency=medium . * Add patch to fix pkg-config file. This will also rename the file to make more sense, but as it's currently completely broken it doesn't really matter. Closes: #908134; LP: #1792407 Checksums-Sha1: 5d33daa4f6202b377e225fe5da36fa109ba93d37 2130 libpodofo_0.9.5-11.dsc f0faf4bb352e098e591f859f18e2b6be8f1a1f0b 20788 libpodofo_0.9.5-11.debian.tar.xz c81cc171c718815675ac1ccdbd3b2334e4a40d64 8576 libpodofo_0.9.5-11_amd64.buildinfo Checksums-Sha256: 98ba82bd086278907fe18a24674436875435574cbbfb89a6f160c11e76972be6 2130 libpodofo_0.9.5-11.dsc bf50a50ea726b62c3ad4ab98846926d2675f2d0f06f142aa9e1e193d3e38803e 20788 libpodofo_0.9.5-11.debian.tar.xz 674546f62a76085aaf38cdeacd273ec43f16cb900051af06b42016157748a598 8576 libpodofo_0.9.5-11_amd64.buildinfo Files: 251470626a57d38a0bbb3bf08a401f3e 2130 libdevel optional libpodofo_0.9.5-11.dsc f139cd2fd9925d3d3654b112e8263275 20788 libdevel optional libpodofo_0.9.5-11.debian.tar.xz d8b4ff366a298587f7eea541a8917a42 8576 libdevel optional libpodofo_0.9.5-11_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAluhA2UACgkQCBa54Yx2 K60emQ//S9GVSWG7/S0Z8ekDa3+zsSMa3fFdW/HQ/UxvbetV9IT6zjQIMpCZgPW+ tB91LwuX65y8JdiPazntS1IPb7NUm9VpCxIwOPNcnVn/34Sz4rfuth4CyUDo0eES ixx0nGEFG2oV5G8VZ6FYSbIT483aSE4FaSW4ovMW9yNYdA7d7JF8FO5hQPkWr5BU AXwU5GiT8ciw0zfCuJOIRRhiR8FjY9YAb8Fln20J1/pLGKpm4+HZeIVW81M3nJGO TNBNyc4fjG5gBeV2LQE02aIa9RmJngnJUZjoZwMxSp1xYrH82k+wTpJg5JkFlbIG NkzelAMQkNa1jwtPk7POqxSLj/ttsm5+MtaXSC9YAMTMwU3OCjaFLdGVfqVnLEMr QuRe9gXrGey8382dnNz7eMXe5Mlau1OALErLNWtuKziR/GXlnFsYN3X9qhIvRz3t ftKBTf4C1XLIgoSzbkiRo5jIynMC6do1/kBkmo+Zhc/SfoFn0Tcygb5rjf0U+t4i 4ViVdP3kYWkOSVwTkRYEFNlHs5Pze7Vv2I8rP
Bug#906781: marked as done (libpodofo: FTBFS in buster/sid (Error copying directory))
Your message dated Tue, 18 Sep 2018 14:41:25 + with message-id and subject line Bug#906781: fixed in libpodofo 0.9.6+dfsg-1 has caused the Debian Bug report #906781, regarding libpodofo: FTBFS in buster/sid (Error copying 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.) -- 906781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libpodofo Version: 0.9.5-9 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch dh binary-arch dh_update_autotools_config -a dh_autoreconf -a debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- \ -DWANT_FONTCONFIG:BOOL=TRUE \ -DWANT_BOOST:BOOL=1 \ -DPODOFO_BUILD_SHARED:BOOL=TRUE \ -DPODOFO_BUILD_STATIC:BOOL=FALSE \ install -d obj-x86_64-linux-gnu cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DWANT_FONTCONFIG:BOOL=TRUE -DWANT_BOOST:BOOL=1 -DPODOFO_BUILD_SHARED:BOOL=TRUE -DPODOFO_BUILD_STATIC:BOOL=FALSE .. [... snipped ...] make -f test/ParserTest/CMakeFiles/ParserTest.dir/build.make test/ParserTest/CMakeFiles/ParserTest.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 53%] Building CXX object test/ParserTest/CMakeFiles/ParserTest.dir/ParserTest.cpp.o cd /<>/obj-x86_64-linux-gnu/test/ParserTest && /usr/bin/c++ -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/x86_64-linux-gnu -I/usr/include/cppunit -I/usr/include/lua5.1 -I/<>/src -I/usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Woverloaded-virtual -Wswitch-enum -Wcast-qual -Wwrite-strings -Wredundant-decls -Wreorder -Wno-deprecated-declarations -W -o CMakeFiles/ParserTest.dir/ParserTest.cpp.o -c /<>/test/ParserTest/ParserTest.cpp [ 54%] Linking CXX executable ParserTest cd /<>/obj-x86_64-linux-gnu/test/ParserTest && /usr/bin/cmake -E cmake_link_script CMakeFiles/ParserTest.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Woverloaded-virtual -Wswitch-enum -Wcast-qual -Wwrite-strings -Wredundant-decls -Wreorder -Wno-deprecated-declarations -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/ParserTest.dir/ParserTest.cpp.o -o ParserTest -L/<>/obj-x86_64-linux-gnu/src -Wl,-rpath,/<>/obj-x86_64-linux-gnu/src -lpodofo -lfontconfig -lfreetype -lz -lidn -lcrypto -lcrypto -ljpeg -lpthread -lfreetype -lpng -lz -ltiff -lidn -lcrypto -lcrypto -ljpeg -lpthread -lfreetype -lpng -ltiff make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 54%] Built target ParserTest make -f test/SignatureTest/CMakeFiles/SignatureTest.dir/build.make test/SignatureTest/CMakeFiles/SignatureTest.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/test/SignatureTest /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/test/SignatureTest /<>/obj-x86_64-linux-gnu/test/SignatureTest/CMakeFiles/SignatureTest.dir/DependInfo.cmake --color= Scanning dependencies of target SignatureTest make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f test/SignatureTest/CMakeFiles/SignatureTest.dir/build.make test/SignatureTest/CMakeFiles/SignatureTest.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 54%] Building CXX object test/SignatureTest/CMakeFiles/SignatureTest.dir/SignTest.cpp.o cd /<>/obj-x86_64-linux-gnu/test/SignatureTest && /usr/bin/c++ -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/x86_64-linux-gnu -I/usr/include/cppunit -I/usr/include/lua5.1 -I/<>/src -I/usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Woverloaded-virtual -Wswitch-enum -Wcast-qual -Wwrite-strings -Wredundant-decls -Wreorder -Wno-deprecated-declarations -W -o CMakeFiles/SignatureTest.dir/SignTest.cpp.o -c /<>/test/SignatureTest/SignTest.cpp [ 55%] Linking CXX executable SignatureTest cd /
Bug#849308: Please let wireguard migrate to testing
Hello Daniel, we want wireguard in Kali and Kali is based on Debian testing. For now we imported it manually from Debian Unstable but it's counter-productive, we have rolling distributions (kali and testing) and an upstream following a rolling model and yet we don't have its packages automatically. My suggestion is to just let the package migrate to testing so that you can provide stable backports to users. At freeze time, you reconsider the situation: - either it's not a good idea to ship it in stable and then you ask the release manager for a removal hint (quick and easy) - or you discuss with the security team (or SRM) if it's possible to regularly import new upstream release as upstream is only supporting the latest release... - or upstream changed its policy because it has been merged in the kernel and you're good to go Please close this bug. Thank you. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/ signature.asc Description: PGP signature
Bug#909101: npm2deb create fails with Error downloading package %s@s\n" % (self.name, self.version)
package: npm2deb version: 0.2.8-1 severity: grave justification: fails to perform its core function of creating debs npm2deb create @ava/write-file-atomic Traceback (most recent call last): File "/usr/bin/npm2deb", line 7, in sys.exit(main(sys.argv)) File "/usr/lib/python3/dist-packages/npm2deb/scripts.py", line 157, in main args.func(args) File "/usr/lib/python3/dist-packages/npm2deb/scripts.py", line 293, in create npm2deb.start() File "/usr/lib/python3/dist-packages/npm2deb/__init__.py", line 70, in start self.download() File "/usr/lib/python3/dist-packages/npm2deb/__init__.py", line 409, in download exception = "Error downloading package %s@s\n" % (self.name, self.version) signature.asc Description: OpenPGP digital signature
Processed: severity of 894343 is serious
Processing commands for cont...@bugs.debian.org: > severity 894343 serious Bug #894343 [libtins-dev] libtins-dev should depend on libpcap-dev Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 894343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 894345 is serious
Processing commands for cont...@bugs.debian.org: > severity 894345 serious Bug #894345 [dublin-traceroute] dublin-traceroute: libdublintraceroute-dev should depend on libtins-dev and libjsoncpp-dev Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 894345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 908456 895900
Processing commands for cont...@bugs.debian.org:
> forcemerge 908456 895900
Bug #908456 {Done: Thiago Franco de Moraes } [invesalius]
invesalius is no longer installable
Bug #895900 [invesalius] invesalius: Please port to python3
Unset Bug forwarded-to-address
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions invesalius/3.1.2-1.
Marked as found in versions invesalius/3.1.1-1.
Bug #908456 {Done: Thiago Franco de Moraes } [invesalius]
invesalius is no longer installable
Marked as found in versions invesalius/3.1.1-3.
Added tag(s) upstream and fixed-upstream.
Merged 895900 908456
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
895900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895900
908456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895945: gqrx-sdr is not starting due to missing libvolk.so.1.3
Processing commands for cont...@bugs.debian.org: > reassign 895945 libvolk1.3 1.3.1-1 Bug #895945 [gqrx-sdr] gqrx-sdr is not starting due to missing libvolk.so.1.3 Bug reassigned from package 'gqrx-sdr' to 'libvolk1.3'. No longer marked as found in versions gqrx-sdr/2.9-2. Ignoring request to alter fixed versions of bug #895945 to the same values previously set Bug #895945 [libvolk1.3] gqrx-sdr is not starting due to missing libvolk.so.1.3 Marked as found in versions volk/1.3.1-1. > reassign 895893 libvolk1.3 1.3.1-1 Bug #895893 [gqrx-sdr] gqrx-sdr crashes with segfault Bug reassigned from package 'gqrx-sdr' to 'libvolk1.3'. No longer marked as found in versions gqrx-sdr/2.9-2. Ignoring request to alter fixed versions of bug #895893 to the same values previously set Bug #895893 [libvolk1.3] gqrx-sdr crashes with segfault Marked as found in versions volk/1.3.1-1. > forcemerge 895945 895893 Bug #895945 [libvolk1.3] gqrx-sdr is not starting due to missing libvolk.so.1.3 Bug #895893 [libvolk1.3] gqrx-sdr crashes with segfault Merged 895893 895945 > severity 895893 serious Bug #895893 [libvolk1.3] gqrx-sdr crashes with segfault Bug #895945 [libvolk1.3] gqrx-sdr is not starting due to missing libvolk.so.1.3 Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > affects 895893 gqrx-sdr Bug #895893 [libvolk1.3] gqrx-sdr crashes with segfault Bug #895945 [libvolk1.3] gqrx-sdr is not starting due to missing libvolk.so.1.3 Added indication that 895893 affects gqrx-sdr Added indication that 895945 affects gqrx-sdr > fixed 895893 1.4-1 Bug #895893 [libvolk1.3] gqrx-sdr crashes with segfault Bug #895945 [libvolk1.3] gqrx-sdr is not starting due to missing libvolk.so.1.3 There is no source info for the package 'libvolk1.3' at version '1.4-1' with architecture '' Unable to make a source version for version '1.4-1' Marked as fixed in versions 1.4-1. Marked as fixed in versions 1.4-1. > close 895893 Bug #895893 [libvolk1.3] gqrx-sdr crashes with segfault Bug #895945 [libvolk1.3] gqrx-sdr is not starting due to missing libvolk.so.1.3 Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 895893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895893 895945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 879631 896360 895967
Processing commands for cont...@bugs.debian.org: > forcemerge 879631 896360 895967 Bug #879631 [python3-flask-socketio] python3-flask-socketio: missing dependency Bug #895967 [python3-flask-socketio] python3-flask-socketio: Traceback on import Severity set to 'serious' from 'important' Bug #896360 [python3-flask-socketio] python3-flask-socketio: flask_socketio fails to import Merged 879631 895967 896360 > thanks Stopping processing here. Please contact me if you need assistance. -- 879631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879631 895967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895967 896360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 896684 is serious
Processing commands for cont...@bugs.debian.org: > severity 896684 serious Bug #896684 [fontconfig-config] fontconfig-config: Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf, due to many errors Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 896684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 896660 is serious
Processing commands for cont...@bugs.debian.org: > severity 896660 serious Bug #896660 [vagrant] vagrant: Vagrant should depend on rsync Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 896660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909099: gimagereader: crashes at startup
Package: gimagereader
Version: 3.2.3-2
Severity: grave
This is the answer I got from upstream, apparently it is a build issue.
Date: Tue, 04 Sep 2018 18:22:43 +0200
From: Sandro Mani
Subject: Re: gimagereader-gtk dumps core
Hi
I've been getting many of these lately: debian apparently updated their
tesseract version, and gImageReader needs to be rebuilt against the new
version.
If you are using the debian package from the regular repos, please ask
the maintainer to rebuild it.
Hope this helps
Sandro
On 04.09.2018 18:17, Francesco Potortì wrote:
> As soon as it starts from the command line on an up-to-date Debian
> system:
>
> $ gimagereader-gtk
> !strcmp(locale, "C"):Error:Assert failed:in file baseapi.cpp, line 201
> Gtk-Message: 18:14:49.170: GtkDialog mapped without a transient parent. This
> is discouraged.
> Process Process-10:
> Traceback (most recent call last):
>File "/usr/lib/python3.6/multiprocessing/process.py", line 258, in
> _bootstrap
> self.run()
>File "/usr/lib/python3.6/multiprocessing/process.py", line 93, in run
> self._target(*self._args, **self._kwargs)
>File "/usr/lib/python3/dist-packages/lios/ocr/ocr_engine_base.py", line
> 52, in
> image_file_name :
> child_conn.send(self.ocr_image_to_text(image_file_name))),
>File "/usr/lib/python3/dist-packages/lios/ocr/ocr_engine_tesseract.py",
> line 57, in ocr_image_to_text
> os.remove("/tmp/{0}_for_ocr.png".format(file_name.split("/")[-1]))
> FileNotFoundError: [Errno 2] No such file or directory:
> '/tmp/capitolato#speciale#005.png_for_ocr.png'
> Segmentation fault (core dumped)
> ~/ipin19/capitolato$ gimagereader-gtk
> !strcmp(locale, "C"):Error:Assert failed:in file baseapi.cpp, line 201
> Gtk-Message: 18:15:05.723: GtkDialog mapped without a transient parent. This
> is discouraged.
> Segmentation fault (core dumped)
>
>
>
> gImageReader 3.2.3 (rev )
>
> #1 0x55dbbde54077 in MainWindow::signalHandler(int) ()
> #2 0x7f386d15dfc0 in () at
> /lib/x86_64-linux-gnu/libc.so.6
> #3 0x7f3871a0c2e7 in ERRCODE::error(char const*, TessErrorLogCode, char
> const*, ...) const () at /usr/lib/x86_64-linux-gnu/libtesseract.so.4
> #4 0x7f3871843a9e in tesseract::TessBaseAPI::TessBaseAPI() () at
> /usr/lib/x86_64-linux-gnu/libtesseract.so.4
> #5 0x55dbbde37268 in Config::setDataLocations(int) ()
> #6 0x7f38703791a8 in
> Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) () at
> /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
> #7 0x7f386ed0af6d in g_closure_invoke () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #8 0x7f386ed1d8d1 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #9 0x7f386ed263f5 in g_signal_emit_valist () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #10 0x7f386ed26e0f in g_signal_emit () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #11 0x7f386fb6f7e5 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #12 0x7f386fb71da5 in gtk_combo_box_set_active () at
> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #13 0x55dbbde386fb in ComboSetting::ComboSetting(Glib::ustring const&,
> Gtk::ComboBox*) ()
> #14 0x55dbbde34eef in Config::Config() ()
> #15 0x55dbbde56028 in MainWindow::MainWindow() ()
> #16 0x55dbbde9c7dd in Application::on_startup() ()
> #17 0x7f38708a7d2d in
> Gio::Application_Class::startup_callback(_GApplication*) () at
> /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
> #18 0x7f386ed0af6d in g_closure_invoke () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #19 0x7f386ed1de0e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #20 0x7f386ed263f5 in g_signal_emit_valist () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #21 0x7f386ed26e0f in g_signal_emit () at
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #22 0x7f386f4210a2 in g_application_register () at
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #23 0x7f386f4218b7 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #24 0x7f38708a78fb in Gio::Application::local_command_line_vfunc(char**&,
> int&) () at /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
> #25 0x7f38708a7b3d in
> Gio::Application_Class::local_command_line_vfunc_callback(_GApplication*,
> char***, int*) () at /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
> #26 0x7f386f421c46 in g_application_run () at
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #27 0x55dbbde2ab66 in main ()
>
> Thread 8 (Thread 0x7f385a684700 (LWP 9467)):
> #0 0x7f386d215739 in __GI___poll (fds=0x55dbbf51a820, nfds=1,
> timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
> #1 0x7f386ea31439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #2 0x7f386ea3154c in g_main_context_iteration () at
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #3 0x7f385a6a9ccd in () at
> /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.s
Bug#895726: marked as done (python3-gbulb: ModuleNotFoundError: No module named 'gi')
Your message dated Tue, 18 Sep 2018 13:05:14 + with message-id and subject line Bug#895726: fixed in python-gbulb 0.6.1-0.1 has caused the Debian Bug report #895726, regarding python3-gbulb: ModuleNotFoundError: No module named 'gi' 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.) -- 895726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-gbulb Version: 0.5.3-2 Severity: serious Justification: missing dependency After installing python3-gbulb, I tried importing it into a python interpreter: | $ python3 | Python 3.6.5 (default, Apr 1 2018, 05:46:30) | [GCC 7.3.0] on linux | Type "help", "copyright", "credits" or "license" for more information. | >>> import gbulb | Traceback (most recent call last): | File "", line 1, in | File "/usr/lib/python3/dist-packages/gbulb/__init__.py", line 1, in | from .glib_events import * | File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 8, in | from gi.repository import GLib, Gio | ModuleNotFoundError: No module named 'gi' | >>> | $ It looks like python3-gbulb is missing a dependency on python3-gi. After installing that package, the ModuleNotFoundError goes away. Such dependencies are usually inserted via substitution variables and originate from setup.py. Indeed, gbulb's setup.py lacks any requires assignments. Likely, this bug should be fixed upstream rather than simply adding the dependency in debian/control. Helmut --- End Message --- --- Begin Message --- Source: python-gbulb Source-Version: 0.6.1-0.1 We believe that the bug you reported is fixed in the latest version of python-gbulb, 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern (supplier of updated python-gbulb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Sep 2018 14:27:08 +0200 Source: python-gbulb Binary: python3-gbulb python-gbulb-doc Architecture: source Version: 0.6.1-0.1 Distribution: unstable Urgency: medium Maintainer: Konstantinos Margaritis Changed-By: Philipp Kern Description: python-gbulb-doc - PEP 3156 event loop based on GLib (common documentation) python3-gbulb - PEP 3156 event loop based on GLib (Python 3) Closes: 895726 904388 Changes: python-gbulb (0.6.1-0.1) unstable; urgency=medium . * Non-maintainer upload * New upstream release (Closes: #904388) * Add dependency on python3-gi (Closes: #895726) Checksums-Sha1: 5a20fea91ff1f26a4445e02fb8fa14af353daa5d 1610 python-gbulb_0.6.1-0.1.dsc c58fbde124ddc691f95a8927582de590a2650c3b 20651 python-gbulb_0.6.1.orig.tar.gz 5e4183ec710c045d7499b703be7df18b34aba1f0 2264 python-gbulb_0.6.1-0.1.debian.tar.xz 867d800c137440b17ecf49a84ad43381e8fc29b5 7485 python-gbulb_0.6.1-0.1_amd64.buildinfo Checksums-Sha256: d6dfa35feb895a21ed7bbc35d14c638471c94d136e6a856ee1fa9e6f02b32769 1610 python-gbulb_0.6.1-0.1.dsc ab9dbde5d92a2b4f13c7acc9afc7235081a5c999d6807b049e2d8c2ef26c03a9 20651 python-gbulb_0.6.1.orig.tar.gz df5dc006e79ece3836ffed35ab86b872c1e429e5b1389b81e731337e1394b679 2264 python-gbulb_0.6.1-0.1.debian.tar.xz 6d315f29c8c1d8298aa07f5c9aa84f8f667a216a8dee5aae810b9676df848640 7485 python-gbulb_0.6.1-0.1_amd64.buildinfo Files: a31bcf54868ffe65acbda10e6dcb1097 1610 python optional python-gbulb_0.6.1-0.1.dsc aaf38d5da6d80ee10c46f41ca68ea675 20651 python optional python-gbulb_0.6.1.orig.tar.gz c3ea15b6eaba4c4e0ff33b7f9e621807 2264 python optional python-gbulb_0.6.1-0.1.debian.tar.xz 7da9ffc118d20f5e817520c822f47878 7485 python optional python-gbulb_0.6.1-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlug8pERHHBrZXJuQGRl Ymlhbi5vcmcACgkQRG4lRTXQVuy/+QgAxW5FzW+2zJFhSawP1MRpwoM8VbOSeoCg QqAOaSwRh1r3F41Ni0aaolws07M4sUQKSwBn83uEIA1JrnyKgTyEOuV+T+7pp/ev gLFUpevavjsZh6xs1hhpmAcGLRgj3LiajIvOYMoWseCxSCIVkmWTSWC8Zd5Nxs93 XM9pH2bCJCg1/7k4+Gny6rOHTkt7cNLJc4eptTIKUm0n6PGZSwaT/22HDs9VCax2 Ql96cq6GURm5hBRD0bT1xT2K7RBTo3sWGdLd0yeSF4nA2BCJOGYBQ+XR6TtIgHDb j/wDfgSpfe7Fd8SCj13QWVedYxk0JoJqdTCKuJapxse
Bug#904388: marked as done (python3-gbulb: fails to install with Python 3.7)
Your message dated Tue, 18 Sep 2018 13:05:14 + with message-id and subject line Bug#904388: fixed in python-gbulb 0.6.1-0.1 has caused the Debian Bug report #904388, regarding python3-gbulb: fails to install with Python 3.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 904388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-gbulb Version: 0.5.3-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-gbulb (0.5.3-2) ... File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 126 future = tasks.async(future, loop=self) ^ SyntaxError: invalid syntax dpkg: error processing package python3-gbulb (--configure): installed python3-gbulb package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: python3-gbulb "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-gbulb=0.5.3-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-gbulb Source-Version: 0.6.1-0.1 We believe that the bug you reported is fixed in the latest version of python-gbulb, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern (supplier of updated python-gbulb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Sep 2018 14:27:08 +0200 Source: python-gbulb Binary: python3-gbulb python-gbulb-doc Architecture: source Version: 0.6.1-0.1 Distribution: unstable Urgency: medium Maintainer: Konstantinos Margaritis Changed-By: Philipp Kern Description: python-gbulb-doc - PEP 3156 event loop based on GLib (common documentation) python3-gbulb - PEP 3156 event loop based on GLib (Python 3) Closes: 895726 904388 Changes: python-gbulb (0.6.1-0.1) unstable; urgency=medium . * Non-maintainer upload * New upstream release (Closes: #904388) * Add dependency on python3-gi (Closes: #895726) Checksums-Sha1: 5a20fea91ff1f26a4445e02fb8fa14af353daa5d 1610 python-gbulb_0.6.1-0.1.dsc c58fbde124ddc691f95a8927582de590a2650c3b 20651 python-gbulb_0.6.1.orig.tar.gz 5e4183ec710c045d7499b703be7df18b34aba1f0 2264 python-gbulb_0.6.1-0.1.debian.tar.xz 867d800c137440b17ecf49a84ad43381e8fc29b5 7485 python-gbulb_0.6.1-0.1_amd64.buildinfo Checksums-Sha256: d6dfa35feb895a21ed7bbc35d14c638471c94d136e6a856ee1fa9e6f02b32769 1610 python-gbulb_0.6.1-0.1.dsc ab9dbde5d92a2b4f13c7acc9afc7235081a5c999d6807b049e2d8c2ef26c03a9 20651 python-gbulb_0.6.1.orig.tar.gz df5dc006e79ece3836ffed35ab86b872c1e429e5b1389b81e731337e1394b679 2264 python-gbulb_0.6.1-0.1.debian.tar.xz 6d315f29c8c1d8298aa07f5c9aa84f8f667a216a8dee5aae810b9676df848640 7485 python-gbulb_0.6.1-0.1_amd64.buildinfo Files: a31bcf54868ffe65acbda10e6dcb1097 1610 python optional python-gbulb_0.6.1-0.1.dsc aaf38d5da6d80ee10c46f41ca68ea675 20651 python optional python-gbulb_0.6.1.orig.tar.gz c3ea15b6eaba4c4e0ff33b7f9e621807 2264 python optional python-gbulb_0.6.1-0.1.debian.tar.xz 7da9ffc118d20f5e817520c822f47878 7485 python optional python-gbulb_0.6.1-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlug8pERHHBrZXJuQGRl Ymlhbi5vcmcACgkQRG4lRTXQVuy/+QgAxW5FzW+2zJFhSawP1MRpwoM8VbOSeoCg QqAOaSwRh1r3F41Ni0aaolws07M4sUQKSwBn83uEIA1JrnyKgTyEOuV+T+7pp/ev gLFUpevavjsZh6xs1hhpmAcGLRgj3LiajIvOYMoWseCxSCIVkmWTSWC8Zd5Nxs93 XM9pH2bCJCg1/7k4+Gny6rOHTkt7cNLJc4eptTIKUm0n6PGZSwaT/22HDs9VCax2 Ql96cq6GURm5hBRD0bT1xT2K7RBTo3sWGdLd0yeSF4nA2BCJOGYBQ+XR6TtIgHDb j/wDfgSpfe7Fd8SCj13QWVedYxk0JoJqdTCKuJapxseVnBifjdYHjQ== =r6xg -END PGP SIGNATURE End Message ---
Bug#896371: marked as done (python3-gbulb: gbulb fails to import)
Your message dated Tue, 18 Sep 2018 13:05:14 +
with message-id
and subject line Bug#895726: fixed in python-gbulb 0.6.1-0.1
has caused the Debian Bug report #895726,
regarding python3-gbulb: gbulb fails to import
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.)
--
895726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gbulb
Version: 0.5.3-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-gbulb importing the module gbulb
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gbulb/__init__.py", line 1, in
from .glib_events import *
File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 8, in
from gi.repository import GLib, Gio
ModuleNotFoundError: No module named 'gi'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: python-gbulb
Source-Version: 0.6.1-0.1
We believe that the bug you reported is fixed in the latest version of
python-gbulb, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Philipp Kern (supplier of updated python-gbulb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Sep 2018 14:27:08 +0200
Source: python-gbulb
Binary: python3-gbulb python-gbulb-doc
Architecture: source
Version: 0.6.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Konstantinos Margaritis
Changed-By: Philipp Kern
Description:
python-gbulb-doc - PEP 3156 event loop based on GLib (common documentation)
python3-gbulb - PEP 3156 event loop based on GLib (Python 3)
Closes: 895726 904388
Changes:
python-gbulb (0.6.1-0.1) unstable; urgency=medium
.
* Non-maintainer upload
* New upstream release (Closes: #904388)
* Add dependency on python3-gi (Closes: #895726)
Checksums-Sha1:
5a20fea91ff1f26a4445e02fb8fa14af353daa5d 1610 python-gbulb_0.6.1-0.1.dsc
c58fbde124ddc691f95a8927582de590a2650c3b 20651 python-gbulb_0.6.1.orig.tar.gz
5e4183ec710c045d7499b703be7df18b34aba1f0 2264
python-gbulb_0.6.1-0.1.debian.tar.xz
867d800c137440b17ecf49a84ad43381e8fc29b5 7485
python-gbulb_0.6.1-0.1_amd64.buildinfo
Checksums-Sha256:
d6dfa35feb895a21ed7bbc35d14c638471c94d136e6a856ee1fa9e6f02b32769 1610
python-gbulb_0.6.1-0.1.dsc
ab9dbde5d92a2b4f13c7acc9afc7235081a5c999d6807b049e2d8c2ef26c03a9 20651
python-gbulb_0.6.1.orig.tar.gz
df5dc006e79ece3836ffed35ab86b872c1e429e5b1389b81e731337e1394b679 2264
python-gbulb_0.6.1-0.1.debian.tar.xz
6d315f29c8c1d8298aa07f5c9aa84f8f667a216a8dee5aae810b9676df848640 7485
python-gbulb_0.6.1-0.1_amd64.buildinfo
Files:
a31bcf54868ffe65acbda10e6dcb1097 1610 python optional
python-gbulb_0.6.1-0.1.dsc
aaf38d5da6d80ee10c46f41ca68ea675 20651 python optional
python-gbulb_0.6.1.orig.tar.gz
c3ea15b6eaba4c4e0ff33b7f9e621807 2264 python optional
python-gbulb_0.6.1-0.1.debian.tar.xz
7da9ffc118d20f5e817520c822f47878 7485 python optional
python-gbulb_0.6.1-0.1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlug8pERHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuy/+QgAxW5FzW+2zJFhSawP1MRpwoM8VbOSeoCg
QqAOaSwRh1r3F41Ni0aaolws07M4sUQKSwBn83uEIA1JrnyKgTyEOuV+T+7pp/ev
gLFUpevavjsZh6xs1hhpmAcGLRgj3LiajIvOYMoWseCxSCIVkmWTSWC8Zd5Nxs93
XM9pH2bCJCg1/7k4+Gny6rOHTkt7cNLJc4eptTIKUm0n6PGZSwaT/22HDs9VCax2
Ql96cq6GURm5hBRD0bT1xT2K7RBTo3sWGdLd0yeSF4nA2BCJOGYBQ+XR6TtIgHDb
j/wDfgSpfe7Fd8SCj13QWVedYxk0JoJqdTCKuJapxseVnBifjdYHjQ==
=r6xg
-END PGP SIGNATURE End Message ---
Processed: Re: Bug#909094: gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable
Processing control commands: > severity -1 serious Bug #909094 [gnome-shell-extension-workspaces-to-dock] gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable Severity set to 'serious' from 'important' -- 909094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 909094 is serious
Processing commands for cont...@bugs.debian.org: > severity 909094 serious Bug #909094 [gnome-shell-extension-workspaces-to-dock] gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable Ignoring request to change severity of Bug 909094 to the same value. > thanks Stopping processing here. Please contact me if you need assistance. -- 909094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: NMU: New upstream version 0.6.1-0.1
Processing commands for cont...@bugs.debian.org: > package python3-gbulb Limiting to bugs with field 'package' containing at least one of 'python3-gbulb' Limit currently set to 'package':'python3-gbulb' > tag 895726 + pending Bug #895726 [python3-gbulb] python3-gbulb: ModuleNotFoundError: No module named 'gi' Bug #896371 [python3-gbulb] python3-gbulb: gbulb fails to import Added tag(s) pending. Added tag(s) pending. > tag 904388 + pending Bug #904388 [python3-gbulb] python3-gbulb: fails to install with Python 3.7 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 895726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895726 896371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896371 904388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895726: NMU: New upstream version 0.6.1-0.1
package python3-gbulb
tag 895726 + pending
tag 904388 + pending
thanks
Hi,
I have just uploaded 0.6.1-0.1 to DELAYED/0-days per [1]. The NMU diff
is attached. This is a new upstream version because it fixes a bunch of
bugs as well as fixing compatibility with newer Python versions.
Kind regards
Philipp Kern
[1]
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu-guidelinesdiff -Nru python-gbulb-0.5.3/CHANGELOG.md python-gbulb-0.6.1/CHANGELOG.md
--- python-gbulb-0.5.3/CHANGELOG.md 2017-02-22 12:07:07.0 +0100
+++ python-gbulb-0.6.1/CHANGELOG.md 2018-08-10 05:44:52.0 +0200
@@ -1,4 +1,21 @@
# Change Log
+## [0.6.1] - 2018-08-09
+
+### Fixed
+ - Support for 3.7, for real this time. Thank you Philippe Normand!
+
+## [0.6.0] - 2018-08-06
+
+### Fixed
+ - Support for 3.7.
+
+### Added
+ - Preliminary Windows support. Please note that using subprocesses is known
+ not to work. Patches welcome.
+
+### Changed
+ - Support for 3.4 and below has been dropped.
+
## [0.5.3] - 2017-01-27
### Fixed
diff -Nru python-gbulb-0.5.3/debian/changelog python-gbulb-0.6.1/debian/changelog
--- python-gbulb-0.5.3/debian/changelog 2017-02-23 10:19:29.0 +0100
+++ python-gbulb-0.6.1/debian/changelog 2018-09-18 14:27:08.0 +0200
@@ -1,3 +1,11 @@
+python-gbulb (0.6.1-0.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * New upstream release (Closes: #904388)
+ * Add dependency on python3-gi (Closes: #895726)
+
+ -- Philipp Kern Tue, 18 Sep 2018 14:27:08 +0200
+
python-gbulb (0.5.3-2) unstable; urgency=medium
* Fix suggested doc package name
diff -Nru python-gbulb-0.5.3/debian/control python-gbulb-0.6.1/debian/control
--- python-gbulb-0.5.3/debian/control 2017-02-23 10:19:29.0 +0100
+++ python-gbulb-0.6.1/debian/control 2018-09-18 14:27:08.0 +0200
@@ -10,7 +10,7 @@
Package: python3-gbulb
Architecture: all
-Depends: ${python3:Depends}, ${misc:Depends}
+Depends: python3-gi, ${python3:Depends}, ${misc:Depends}
Suggests: python-gbulb-doc
Description: PEP 3156 event loop based on GLib (Python 3)
Gbulb is a Python library that implements a PEP 3156 interface for the GLib
diff -Nru python-gbulb-0.5.3/.drone.yml python-gbulb-0.6.1/.drone.yml
--- python-gbulb-0.5.3/.drone.yml 2017-02-22 12:07:07.0 +0100
+++ python-gbulb-0.6.1/.drone.yml 2018-08-10 05:44:52.0 +0200
@@ -1,9 +1,8 @@
matrix:
PYTHON_VERSION:
-- 3.4.3
-- 3.4.6
-- 3.5.3
-- 3.6.0
+- 3.5.5
+- 3.6.6
+- 3.7.0
pipeline:
build:
diff -Nru python-gbulb-0.5.3/gbulb/glib_events.py python-gbulb-0.6.1/gbulb/glib_events.py
--- python-gbulb-0.5.3/gbulb/glib_events.py 2017-02-22 12:07:07.0 +0100
+++ python-gbulb-0.6.1/gbulb/glib_events.py 2018-08-10 05:44:52.0 +0200
@@ -1,18 +1,64 @@
"""PEP 3156 event loop based on GLib"""
+import asyncio
import os
import signal
+import socket
+import sys
import threading
-from asyncio import events, tasks, unix_events
+import weakref
+from asyncio import constants, events, futures, sslproto, tasks
from gi.repository import GLib, Gio
+from . import transports
+
+
+if hasattr(os, 'set_blocking'):
+def _set_nonblocking(fd):
+os.set_blocking(fd, False)
+elif sys.platform == 'win32':
+def _set_nonblocking(fd):
+pass
+else:
+import fcntl
+
+def _set_nonblocking(fd):
+flags = fcntl.fcntl(fd, fcntl.F_GETFL)
+flags = flags | os.O_NONBLOCK
+fcntl.fcntl(fd, fcntl.F_SETFL, flags)
+
__all__ = ['GLibEventLoop', 'GLibEventLoopPolicy']
-class GLibChildWatcher(unix_events.AbstractChildWatcher):
+# The Windows `asyncio` implementation doesn't actually use this, but
+# `glib` abstracts so nicely over this that we can use it on any platform
+if sys.platform == "win32":
+class AbstractChildWatcher:
+pass
+else:
+from asyncio.unix_events import AbstractChildWatcher
+
+
+class GLibChildWatcher(AbstractChildWatcher):
def __init__(self):
self._sources = {}
+self._handles = {}
+
+# On windows on has to open a process handle for the given PID number
+# before it's possible to use GLib's `child_watch_add` on it
+if sys.platform == "win32":
+
+def _create_handle_for_pid(self, pid):
+import _winapi
+return _winapi.OpenProcess(0x00100400, 0, pid)
+
+def _close_process_handle(self, handle):
+import _winapi
+_winapi.CloseHandle(handle)
+else:
+_create_handle_for_pid = lambda self, pid: pid
+_close_process_handle = lambda self, pid: None
def attach_loop(self, loop):
# just ignored
@@ -21,21 +67,28 @@
def add_child_handler(self, pid, callback, *args):
self.remove_child_handler(pid)
-source = GLib.child_watch_add(0, pid, self.__callback__)
-self._sources[pid] = source, callback, args
+handle = self._create_handle_for_pid(pid)
+sou
Processed: tagging 909076
Processing commands for cont...@bugs.debian.org: > tags 909076 + confirmed Bug #909076 [ghostscript] ghostscript: ps2ascii crashes: Error: /typecheck in --.bind-- Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 909076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905706: [Debian-med-packaging] Bug#905706: libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js
On 09/18/2018 12:12 PM, Andreas Tille wrote: > Hi Olivier, > > the build failure changed after your changes but it does not build here > in a clean and up to date pbuilder chroot (with htsjdk from unstable, > not your new version): indeed it fails to compile with htsjdk from unstable, but works with htsjdk 2.16.1, seems it needs the "new" htsjdk release Olivier > > > * Try: > Run with --debug option to get more log output. Run with --scan to get full > insights. > > * Exception is: > org.gradle.api.tasks.TaskExecutionException: Execution failed for task > ':compileJava'. > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) > at > org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) > at > org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62) > at > org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) > at > org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60) > at > org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97) > at > org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87) > at > org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) > at > org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) > at > org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) > at > org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) > at > org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98) > at > org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626) > at > org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) > Caused by: org.gradle.api.internal.tasks.compile.CompilationFailedException: > Compilation failed; see the compiler error output for details. > at > org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:50) > at > org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:35) > at > org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.delegateAndHandleErrors(NormalizingJavaCompiler.java:98) >
Bug#905706: [Debian-med-packaging] Bug#905706: libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js
On 09/18/2018 12:12 PM, Andreas Tille wrote: > Hi Olivier, > > the build failure changed after your changes but it does not build here > in a clean and up to date pbuilder chroot (with htsjdk from unstable, > not your new version): strange, unless linked to htsjdk version... I gonna have a look. Everything built nicely on my computer > > > * Try: > Run with --debug option to get more log output. Run with --scan to get full > insights. > > * Exception is: > org.gradle.api.tasks.TaskExecutionException: Execution failed for task > ':compileJava'. > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) > at > org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) > at > org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62) > at > org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) > at > org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60) > at > org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97) > at > org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87) > at > org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) > at > org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) > at > org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) > at > org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) > at > org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98) > at > org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626) > at > org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) > Caused by: org.gradle.api.internal.tasks.compile.CompilationFailedException: > Compilation failed; see the compiler error output for details. > at > org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:50) > at > org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:35) > at > org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.delegateAndHandleErrors(NormalizingJavaCompiler.java:98) > at > org.gradle.api.intern
Bug#909092: tmuxinator: missing dependency on ruby-xdg
Package: tmuxinator Version: 0.12.0-1 Severity: serious Justification: Policy 3.5 any tmuxinator command prints the following trace: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- xdg (LoadError) from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' from /usr/lib/ruby/vendor_ruby/tmuxinator.rb:6:in `' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' from /usr/bin/tmuxinator:5:in `' /usr/lib/ruby/vendor_ruby/tmuxinator.rb:6 is require "xdg" but the tmuxinator package does not declare a dependency on "ruby-xdg". after manually installing ruby-xdg, tmuxinator works as expected. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages tmuxinator depends on: ii ruby 1:2.5.1 ii ruby-erubis 2.7.0-3 ii ruby-thor0.19.4-1 ii tmux 2.7-1+b1 tmuxinator recommends no packages. tmuxinator suggests no packages. -- no debconf information
Processed: severity of 896990 is serious
Processing commands for cont...@bugs.debian.org: > severity 896990 serious Bug #896990 [flickrbackup] flickrbackup: Can't authenticate to flickr.com Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 896990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 909086 is serious
Processing commands for cont...@bugs.debian.org: > severity 909086 serious Bug #909086 [opam] opam: Missing dependency on bubblewrap Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 909086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909088: marked as done (jayway-jsonpath: FTBFS on all)
Your message dated Tue, 18 Sep 2018 11:19:14 + with message-id and subject line Bug#909088: fixed in jayway-jsonpath 2.0.0-5 has caused the Debian Bug report #909088, regarding jayway-jsonpath: FTBFS on all 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.) -- 909088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: jayway-jsonpath version: 2.0.0-4 severity: serious Hi, The latest version of jayway-jsonpath in unstable fails on all: https://buildd.debian.org/status/package.php?p=jayway-jsonpath Cheers, Ivo --- End Message --- --- Begin Message --- Source: jayway-jsonpath Source-Version: 2.0.0-5 We believe that the bug you reported is fixed in the latest version of jayway-jsonpath, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated jayway-jsonpath package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Sep 2018 12:52:22 +0200 Source: jayway-jsonpath Binary: libjsonpath-java Architecture: source Version: 2.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libjsonpath-java - Jayway JsonPath - XPath like expressions for JSON Closes: 909088 Changes: jayway-jsonpath (2.0.0-5) unstable; urgency=medium . * Team upload. * No longer build the javadoc (Closes: #909088) Checksums-Sha1: 4dd9e2bb070afbda2878a6cacb530ff21991cad1 2258 jayway-jsonpath_2.0.0-5.dsc 5a3644c4d52099f8fd27e86b2b3d410ab9678fa0 4600 jayway-jsonpath_2.0.0-5.debian.tar.xz abe7046e723acf87452ac9aebaeeb71fcafb76f1 16426 jayway-jsonpath_2.0.0-5_source.buildinfo Checksums-Sha256: bb4ac9b384a58305434e68883b7f8256c55630983508842947edc9067ed1c3ae 2258 jayway-jsonpath_2.0.0-5.dsc eabfe74f45bf7f7f37edb0eea864feb8c1688e90d945d7b9bea381fecdb9808c 4600 jayway-jsonpath_2.0.0-5.debian.tar.xz 24e2c416651d021da4cd3046a18d3130d94c9a58937005e53d0867173bcde824 16426 jayway-jsonpath_2.0.0-5_source.buildinfo Files: d383b423a2d87ef516671dc1f8d0e896 2258 java optional jayway-jsonpath_2.0.0-5.dsc 6236599f7931143231fc3f21ffab45e6 4600 java optional jayway-jsonpath_2.0.0-5.debian.tar.xz c17ef78d8474f8eb3d5adab832549ee2 16426 java optional jayway-jsonpath_2.0.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlug2aQSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsZvoQAMeJGIQq5zO/YxvwuzWfZ3PYsNxib7aU dEPNfwvgyaI+b8BG7zPQN+2PlOl5seuhVnOn+BdIvevWelxpblDUOITfENpmLdES dSPcEqJSW6aVIwc/z/ScKqaGDLpur0opHRk5DUM6ish6q+ztVB20RHUN6hrLiJDr 1+bDALhaawQncjlDaHx4QBAsVPVlT5Fuiwx+/FHOWSPV1zaDC82yhtRGpqMWKkHK VSz2o8ojt15Ff4wz1rgrDBymUNl+FhXnT20VsM79dzzZv4/nwdMMabk130ZrAMph 2JUYtlJ+n4sUQmeYH7nWb8uzg+99cJ72M8A+NOUKtuRsojnI9mXkUApf4ycU/JLO SDXDq4mWjw+2voabw4nniaSAiwFgSSKc8rHTjJB7Izh29ZJhTz2/C3+/GVg3B+em hIBDUwEjhRbRPzjcaVa2U+bPVmDzrPSLVv/jssW0KW6sFvwsPCdJGTwsOHAwLqkv YIv+6JzNoKBymJhKUI1VeeajF5LbABqjsEjpk2uHWG6WqMTDPqa7BraQeyQfSmUV dlgLckToKUmKbnXyvjfc7Cqoji2puscPlZiUwYCPmDMbz6OTqkwZJME8XdO/FYEL du84VCeeIuFSwDJDsT0KXyQ4f2EySkNmxffOImvaogk0sKL5KxCTXaXPeOps9f5a 2IKpXglj93SO =5Gtr -END PGP SIGNATURE End Message ---
Bug#909090: fonts-smc-manjari FTBFS with fontmake 1.6.1-1
Source: fonts-smc-manjari
Version: 1.5.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-smc-manjari.html
...
make -j15 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/build/1st/fonts-smc-manjari-1.5.1'
INFO:fontmake.font_project:Building OTF for Manjari-Thin
INFO:ufo2ft:Pre-processing glyphs
INFO:fontmake.font_project:Building TTF for Manjari-Thin
INFO:ufo2ft:Pre-processing glyphs
INFO:ufo2ft.filters:Running DecomposeComponentsFilter on Manjari-Thin
INFO:ufo2ft.filters:Running DecomposeComponentsFilter on Manjari-Thin
INFO:ufo2ft.filters:Running RemoveOverlapsFilter on Manjari-Thin
INFO:ufo2ft.filters:Running RemoveOverlapsFilter on Manjari-Thin
INFO:ufo2ft.filters:Running CubicToQuadraticFilter on Manjari-Thin
INFO:ufo2ft.filters.cubicToQuadratic:New spline lengths: 1: 1727, 2: 4325, 3:
3737, 4: 574, 5: 20, 6: 2, 7: 5
INFO:ufo2ft:Building OpenType tables
INFO:fontTools.misc.xmlReader:Parsing 'DSIG' table...
WARNING:ufo2ft.featureCompiler:Please change the file name in the include(...);
statement to be relative to the UFO itself, instead of relative to the
'features.fea' file contained in it.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/fontTools/feaLib/lexer.py", line 230, in
__next__
self.lexers_.append(self.make_lexer_(path))
File "/usr/lib/python3/dist-packages/fontTools/feaLib/lexer.py", line 247, in
make_lexer_
fileobj = open(filename, "r", encoding="utf-8")
File "/usr/lib/python3/dist-packages/fontTools/misc/py23.py", line 250, in
open
file, mode, buffering, encoding, errors, newline, closefd)
FileNotFoundError: [Errno 2] No such file or directory:
'/build/1st/fonts-smc-manjari-1.5.1/sources/tables.fea'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "tools/build.py", line 62, in
main()
File "tools/build.py", line 58, in main
build(args)
File "tools/build.py", line 41, in build
subroutinize=True
File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 660, in
run_from_ufos
self.build_ttfs(ufos, **kwargs)
File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 236, in
build_ttfs
self.save_otfs(ufos, ttf=True, **kwargs)
File "/usr/lib/python3/dist-packages/fontTools/misc/loggingTools.py", line
372, in wrapper
return func(*args, **kwds)
File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 395, in
save_otfs
for font, ufo in zip(fonts, ufos):
File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 280, in
_iter_compile
yield compile_func(ufo, **options)
File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 143, in
compileTTF
featureCompilerClass=featureCompilerClass,
File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 230, in
compileFeatures
return featureCompiler.compile()
File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 125, in
compile
self.setupFeatures()
File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 222, in
setupFeatures
featureFile = parseLayoutFeatures(self.ufo)
File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 48, in
parseLayoutFeatures
doc = parser.parse()
File "/usr/lib/python3/dist-packages/fontTools/feaLib/parser.py", line 69, in
parse
statements.append(self.parse_languagesystem_())
File "/usr/lib/python3/dist-packages/fontTools/feaLib/parser.py", line 1209,
in parse_languagesystem_
self.expect_symbol_(";")
File "/usr/lib/python3/dist-packages/fontTools/feaLib/parser.py", line 1532,
in expect_symbol_
self.advance_lexer_()
File "/usr/lib/python3/dist-packages/fontTools/feaLib/parser.py", line 1604,
in advance_lexer_
self.next_token_location_) = next(self.lexer_)
File "/usr/lib/python3/dist-packages/fontTools/feaLib/lexer.py", line 235, in
__next__
raise IncludedFeaNotFound(fname_token, fname_location)
fontTools.feaLib.error.IncludedFeaNotFound:
/build/1st/fonts-smc-manjari-1.5.1/sources/Manjari-Thin.ufo:5:9: tables.fea
make[1]: *** [Makefile:20: ttf] Error 1
make[1]: *** Waiting for unfinished jobs
INFO:ufo2ft:Building OpenType tables
INFO:fontTools.misc.xmlReader:Parsing 'DSIG' table...
WARNING:ufo2ft.featureCompiler:Please change the file name in the include(...);
statement to be relative to the UFO itself, instead of relative to the
'features.fea' file contained in it.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/fontTools/feaLib/lexer.py", line 230, in
__next__
self.lexers_.append(self.make_lexer_(path))
File "/usr/lib/python3/dist-packages/fontTools/feaLib/lexer.py", line 247, in
make_lexer_
fileobj = open(filename, "r", encoding="utf-8")
File "/usr/lib/python3/dist-packages/fontTools/misc/py23.py", line 250, in
open
file, mode, buffering, encoding, errors, newline, closefd)
Fil
Bug#909089: debhelper: GNU configure $prefix expanded too early?
Package: debhelper Version: 11.4 Severity: serious Hi, Thanks for maintaining and extending debhelper! I don't have much information right now, maybe I'll look into it in the evening (Eastern European time), but trying to build gforth in a chroot containing debhelper-11.4 results in a package where all the paths passed to the GNU configure script as "\$prefix/something" are actually defined as "/something", thus placing binaries in /bin, include files in /include, etc. Installing debhelper-11.3.5 fixes the problem. Thanks again for everything you're doing for debhelper and Debian, and keep up the great work! G'luck, Peter -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debhelper depends on: ii autotools-dev20180224.1 ii dh-autoreconf19 ii dh-strip-nondeterminism 0.042-1 ii dpkg 1.19.0.5+b1 ii dpkg-dev 1.19.0.5 ii dwz 0.12-2 ii file 1:5.34-2 ii libdpkg-perl 1.19.0.5 ii man-db 2.8.4-2 ii perl 5.26.2-7 ii po-debconf 1.0.20 debhelper recommends no packages. Versions of packages debhelper suggests: pn dh-make -- no debconf information signature.asc Description: PGP signature
Bug#897223: marked as done (python-kmodpy breaks package system in multiarch setting)
Your message dated Tue, 18 Sep 2018 11:04:06 + with message-id and subject line Bug#897223: fixed in kmodpy 0.1.10-2.1 has caused the Debian Bug report #897223, regarding python-kmodpy breaks package system in multiarch setting 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.) -- 897223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-kmodpy Version: 0.1.10-2 Severity: important Dear Maintainer, python-kmodpy is marked as Multi-Arch: same but its postinst and preinst scripts call pycompile and pyclean without specifying the package architecture. As a result if python-kmodpy is installed for more than one architecture the package name is ambiguous, causing the postinst and prerm scripts fail. This then prevents any package from being installed or removed, thus breaking the system permanently. The solution is to replace the following line in /var/lib/dpkg/info/libccnet0:*.postinst pycompile -p python-kmodpy with pycompile -p python-kmodpy:$DPKG_MAINTSCRIPT_ARCH And the following line in /var/lib/dpkg/info/libccnet0:*.prerm pyclean -p python-kmodpy with pyclean -p python-kmodpy:$DPKG_MAINTSCRIPT_ARCH Note that this bugs still affects Debian 9.4, the current stable release. See also bug #770625 which shows how this same bug was fixed in gir1.2-ibus-1.0. -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 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) Versions of packages python-kmodpy:amd64 depends on: ii libkmod2 23-2 ii python2.7.13-2 python-kmodpy:amd64 recommends no packages. python-kmodpy:amd64 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: kmodpy Source-Version: 0.1.10-2.1 We believe that the bug you reported is fixed in the latest version of kmodpy, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated kmodpy 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: Sun, 16 Sep 2018 13:26:10 +0300 Source: kmodpy Binary: python-kmodpy Architecture: source Version: 0.1.10-2.1 Distribution: unstable Urgency: high Maintainer: Chrysostomos Nanakos Changed-By: Adrian Bunk Description: python-kmodpy - Python binding for kmod Closes: 897223 Changes: kmodpy (0.1.10-2.1) unstable; urgency=high . * Non-maintainer upload. * Remove the incorrect Multi-Arch: same. (Closes: #897223) Checksums-Sha1: 9f5be7377e30aa3ed537e7508d31cb8143d7883e 1902 kmodpy_0.1.10-2.1.dsc 01df11358d49d773f258f097811aa53692a3 2332 kmodpy_0.1.10-2.1.debian.tar.xz Checksums-Sha256: af2555e98f6ce54a5862ce521645a16fedc88e8700b73e9157f9a904222688de 1902 kmodpy_0.1.10-2.1.dsc 3893b21f28c1cf06edafc4fd4b1ebc481d6ba2bcd79a1f9f620c4c5ba4aeff3c 2332 kmodpy_0.1.10-2.1.debian.tar.xz Files: de2eef8cb8a9921dedbc1bccce3fdee4 1902 python optional kmodpy_0.1.10-2.1.dsc c527a4cfecf45f72223022db6e75ca1f 2332 python optional kmodpy_0.1.10-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlueMKoACgkQiNJCh6LY mLHWfQ//eq+fqtVi9YyOHCpj3gBBzksaK+N7mjG6gN/xdSlL4UYuDPZNw5Dyd4z4 mROntfitus8W4su/rq5/bO6e2TDZ+ftmIu2Phde7YirlpZq6CC+hEtpk4whPRbAT QIWxPChHcgPjkst0S5sRPlFtJB5WYBfE00WOTrT4vzHW1PLu2Q2c7OuZTJEFg9D3 phFCqg8+sG06IT34w32Vi+aZlCzGGewPdqEg5qzF4MQlTa3wu9I1V+0qkUfG6AlE LmsBLx2sMSpV/JytjHKHQyCJ4Ms1dqM3cknYFLuscQ/Jv7FLyzjTBCmIhxn0Dm6V 4WQjOATZS8GDsPhOeWPs1O6HiaEMMS4GqxdG8Z6im/69+VcnDozQRYfdnkcefN64 tGK+6NzVOLyXlp4MQk5wXI+uqu4i8MCA2IIhTqBj1IRVzO6Fk5Yf3li9eidVQ9kZ ybM9Z2XWwLDwqqAiVCQDO0LELxgt0S5KHB+WM9NDA2dsekBWRdCyCpMPGAwOPuIX vktIgS8FJzFV0PLkLN/PcG9T9N1pfUNX+2M8LIYYObfjPC0+SbgHVl0rEnS666du Ve0ewukDjls7QFmuTaKPq4clWVFAc9BuwxmexVlBGUi
Processed: your mail
Processing commands for cont...@bugs.debian.org: > clone 908979 -1 Bug #908979 [gradle-debian-helper] jayway-jsonpath: FTBFS on all Bug 908979 cloned as bug 909088 > reassign -1 src:jayway-jsonpath Bug #909088 [gradle-debian-helper] jayway-jsonpath: FTBFS on all Bug reassigned from package 'gradle-debian-helper' to 'src:jayway-jsonpath'. No longer marked as found in versions gradle-debian-helper/2.0. Ignoring request to alter fixed versions of bug #909088 to the same values previously set > retitle 908979 gradle-debian-helper: Hook injection doesn't work with Gradle > daemon Bug #908979 [gradle-debian-helper] jayway-jsonpath: FTBFS on all Changed Bug title to 'gradle-debian-helper: Hook injection doesn't work with Gradle daemon' from 'jayway-jsonpath: FTBFS on all'. > fixed 908979 2.0.1 Bug #908979 [gradle-debian-helper] gradle-debian-helper: Hook injection doesn't work with Gradle daemon Marked as fixed in versions gradle-debian-helper/2.0.1. > close 908979 Bug #908979 [gradle-debian-helper] gradle-debian-helper: Hook injection doesn't work with Gradle daemon Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 908979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908979 909088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908979: fixed in gradle-debian-helper 2.0.1
Le 17/09/2018 à 13:59, Ivo De Decker a écrit : > Unfortunately, jayway-jsonpath failed again, using the new > gradle-debian-helper: > > https://buildd.debian.org/status/fetch.php?pkg=jayway-jsonpath&arch=all&ver=2.0.0-4&stamp=1537180937&raw=0 I saw that too but this is a different error this time. gradle-debian-helper isn't to blame here, I think jayway-jsonpath is simply missing a build dependency on default-jdk-doc (or should disable the generation of the javadoc since it's doesn't create a doc package). Emmanuel Bourg
Bug#905706: [Debian-med-packaging] Bug#905706: libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js
Hi Olivier, the build failure changed after your changes but it does not build here in a clean and up to date pbuilder chroot (with htsjdk from unstable, not your new version): * Try: Run with --debug option to get more log output. Run with --scan to get full insights. * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':compileJava'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62) at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97) at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87) at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) Caused by: org.gradle.api.internal.tasks.compile.CompilationFailedException: Compilation failed; see the compiler error output for details. at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:50) at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:35) at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.delegateAndHandleErrors(NormalizingJavaCompiler.java:98) at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:51) at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:37) at org.gradle.api.internal.tasks.compile.CleaningJavaCompilerSupport.execute(CleaningJavaCompilerSupport.java:
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 909000 enigmail 2:1.9.9-1~deb9u1 Bug #909000 [src:enigmail] Enigmail 2.0 needed in Stretch after Thunderbird 60 upload Bug #909001 [src:enigmail] enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1) Bug reassigned from package 'src:enigmail' to 'enigmail'. Bug reassigned from package 'src:enigmail' to 'enigmail'. No longer marked as found in versions enigmail/2:1.9.9-1~deb9u1. No longer marked as found in versions enigmail/2:1.9.9-1~deb9u1. Ignoring request to alter fixed versions of bug #909000 to the same values previously set Ignoring request to alter fixed versions of bug #909001 to the same values previously set Bug #909000 [enigmail] Enigmail 2.0 needed in Stretch after Thunderbird 60 upload Bug #909001 [enigmail] enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1) Marked as found in versions enigmail/2:1.9.9-1~deb9u1. Marked as found in versions enigmail/2:1.9.9-1~deb9u1. > forcemerge 909000 909081 Bug #909000 [enigmail] Enigmail 2.0 needed in Stretch after Thunderbird 60 upload Bug #909001 [enigmail] enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1) Bug #909081 [enigmail] [enigmail] impossible install enigmail Severity set to 'grave' from 'important' Bug #909001 [enigmail] enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1) Merged 909000 909001 909081 > thanks Stopping processing here. Please contact me if you need assistance. -- 909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000 909001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909001 909081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908688: marked as done (flask FTBFS with sphinx 1.7.9-1)
Your message dated Tue, 18 Sep 2018 10:04:26 + with message-id and subject line Bug#908688: fixed in flask 1.0.2-2 has caused the Debian Bug report #908688, regarding flask FTBFS with sphinx 1.7.9-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.) -- 908688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flask Version: 1.0.2-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flask.html ... debian/rules override_dh_install make[1]: Entering directory '/build/1st/flask-1.0.2' dh_install rm /build/1st/flask-1.0.2/debian/python-flask/usr/bin/flask make[1]: Leaving directory '/build/1st/flask-1.0.2' dh_installdocs -O--buildsystem=pybuild debian/rules override_dh_sphinxdoc make[1]: Entering directory '/build/1st/flask-1.0.2' http_proxy='http://127.0.0.1:9/' PYTHONPATH=. sphinx-build -N -q -E -b html docs/ debian/python-flask-doc/usr/share/doc/python-flask-doc/html/ Configuration error: There is a programable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 161, in __init__ execfile_(filename, config) File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in execfile_ exec_(code, _globals) File "conf.py", line 7, in from pallets_sphinx_themes import DocVersion, ProjectLink, get_version ImportError: cannot import name 'DocVersion' make[1]: *** [debian/rules:19: override_dh_sphinxdoc] Error 2 --- End Message --- --- Begin Message --- Source: flask Source-Version: 1.0.2-2 We believe that the bug you reported is fixed in the latest version of flask, 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. Ondřej Nový (supplier of updated flask package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Sep 2018 11:42:45 +0200 Source: flask Binary: python-flask python3-flask python-flask-doc Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Ondřej Nový Description: python-flask - micro web framework based on Werkzeug and Jinja2 - Python 2.7 python-flask-doc - micro web framework based on Werkzeug and Jinja2 - documentation python3-flask - micro web framework based on Werkzeug and Jinja2 - Python 3.x Closes: 908688 Changes: flask (1.0.2-2) unstable; urgency=medium . * Convert git repository from git-dpm to gbp layout * Use 'python3 -m sphinx' instead of sphinx-build for building docs * Add d/p/0002-remove-DocVersion-related.patch and d/p/0003-fix-issue-no-theme-named-flask-found.patch and d/p/0004-empty-CONTRIBUTING-rst.patch and d/p/0005-remove-carbon-ads.patch: Make docs build compatible with newer pallets_sphinx_themes (Closes: #908688) * Bump standards version to 4.2.1 (no changes) Checksums-Sha1: 788d6ee2e553a50ce9cbe56b2cd43bbb335e265c 2521 flask_1.0.2-2.dsc dc74cc2729b705cc282eb411585cb60412b43fff 6288 flask_1.0.2-2.debian.tar.xz 4ca84cf9c10c68208378c706b51fa07a67d52507 8961 flask_1.0.2-2_amd64.buildinfo Checksums-Sha256: d529a5d8e36940a2df38584fdf459ad4b72ef5f28c68cc5f8301cdd5cde6f305 2521 flask_1.0.2-2.dsc 201fe14e61c7c66e2c5ed00a75bff8af18535eb20b7c96264a07d0b2e5de8c81 6288 flask_1.0.2-2.debian.tar.xz 5e097ccf063d79a9ce1311137156cc36fe2389edbfd054835478706ac533bf55 8961 flask_1.0.2-2_amd64.buildinfo Files: 8217beb9aaab298c4ca37ece91860bc0 2521 python optional flask_1.0.2-2.dsc d4bb1941516005029f371b1c4c0eb4d3 6288 python optional flask_1.0.2-2.debian.tar.xz 4674fb72f987c96638241dc49e4e15da 8961 python optional flask_1.0.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAlugyi8ACgkQNXMSVZ0e BktqCA/9FUz7Fr1BdBjRUhm7sQAZmUayhIxOBFECGLsc5Fg+iNmXl4erSj8QKKDy /2vtTvRcfdPSlKWbtWLhqALcjKKcPMYALzkygxYJqHXel5fcf9Fq2kSQAbUjZgVX bfJb2xq53eauhS+SuAXbIyw4jwGw5jkGJ1C93N+8hkyTgXKAjNDUJTrvT+2e/Llj i+KtALwjLAgUC+04QQPwaU0AgKE6j3OrmRfvIYaNY5yeECc
Bug#909084: [Pkg-zsh-devel] Bug#909084: Missing pcre module
On Tue, Sep 18 2018, Axel Beckert wrote: > Reason seems that pcre2 and pcre3 are not exchangable without code > changes at all as it initially sounded in that LP bug report: > > https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/8 > https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/9 > https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/21 It's also a very unfortunate numbering of pcre I have to say [!].
Processed: Re: [Pkg-zsh-devel] Bug#909084: Missing pcre module
Processing control commands: > tag -1 + confirmed pending Bug #909084 [zsh] Missing pcre module Added tag(s) confirmed and pending. > severity -1 serious Bug #909084 [zsh] Missing pcre module Severity set to 'serious' from 'normal' -- 909084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working
On Tue, Sep 18, 2018 at 07:17:15PM +1200, Tim Makarios wrote: > On 18/09/18 17:55, Mike Hommey wrote: > > So the crash is happening in JITed code, which is not expected: the JIT > > should disable itself. There might be something wrong either in the > > detection or maybe some parts don't disable themselves as they're > > supposed to. > > > > Can you try starting with `firefox-esr -safe-mode`? > > That works. > > > If that works, can > > you then go to about:config and switch javascript.options.ion to false, > > then restart without -safe-mode? > > That crashes. > > > If that works, stop there. If it > > doesn't work, can you try -safe-mode again, and switch > > javascript.options.baselinejit to false? > > And now it works in non-safe-mode! > > Incidentally, since you're talking about Javascript, I thought it might be > relevant that I'm using the NoScript add-on, so I thought I'd try disabling > that (which worked), and setting javascript.options.baselinejit and > javascript.options.ion back to true. When I switched > javascript.options.baselinejit back to true, Firefox instantly crashed. > (But, of course, it's recoverable again via -safe-mode.) > > Setting only javascript.options.ion back to true *doesn't* crash Firefox, or > prevent it from starting. Can you restore all the prefs and addons you changed to what they were before and try the following package? https://people.debian.org/~glandium/firefox-esr_60.2.0esr-1~deb9u2.2_i386.deb sha256: 4f092e11faf729316ea96be5b9f6ecca58ea1f001279c44406a8d505b021c17f (Others who have experienced the crash on startup are invited to try this package as well) Thanks Mike
Bug#907079: marked as done (Not using SNI)
Your message dated Tue, 18 Sep 2018 09:19:58 + with message-id and subject line Bug#907079: fixed in python-imaplib2 2.57-5 has caused the Debian Bug report #907079, regarding Not using SNI 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.) -- 907079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openssl Version: 1.1.1~~pre9-1 Severity: critical Justification: renders other packages unusable Hi, I have got openssl 1.1.1~~pre9-1 as it is landed in sid. After upgrading certain applications are not able to establish connection. Example of offlineimap: ERROR: Unknown SSL protocol connecting to host 'imap.gmail.com' for repository 'showmax-remote'. OpenSSL responded: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:726) Example of openvpn: Thu Aug 23 14:46:07 2018 OpenSSL: error:1425F18C:SSL routines:ssl_choose_client_version:version too low Thu Aug 23 14:46:07 2018 TLS_ERROR: BIO read tls_read_plaintext error Thu Aug 23 14:46:07 2018 TLS Error: TLS object -> incoming plaintext read error Thu Aug 23 14:46:07 2018 TLS Error: TLS handshake failed I went through changelogs, but was not seen anything what would help me in debugging the issue. Interestingly s_client and curl is able to establish a connection even with new version. Maybe that can be related to different default cipher_set? Thank you for any hints. Antonin signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: python-imaplib2 Source-Version: 2.57-5 We believe that the bug you reported is fixed in the latest version of python-imaplib2, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated python-imaplib2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Sep 2018 12:04:58 +0300 Source: python-imaplib2 Binary: python-imaplib2 python3-imaplib2 Architecture: source Version: 2.57-5 Distribution: unstable Urgency: medium Maintainer: Ulises Vitulli Changed-By: Ilias Tsitsimpis Description: python-imaplib2 - Threaded Python IMAP4 client python3-imaplib2 - Threaded Python IMAP4 client (Python 3) Closes: 907079 Changes: python-imaplib2 (2.57-5) unstable; urgency=medium . * Use SSLContext if available so we send SNI. Thanks to Julien Cristau for the patch (Closes: #907079) Checksums-Sha1: 7d2e943923477bb9e64b680b58644d780433acac 2106 python-imaplib2_2.57-5.dsc 7dc0f52d11f31ce59550207657808ec00ddad336 6760 python-imaplib2_2.57-5.debian.tar.xz 5300f80819d75aef619c3bd9f5309211749d9607 7071 python-imaplib2_2.57-5_amd64.buildinfo Checksums-Sha256: 7d67a1557ac872373fc7d068748e14585e767fb3104440ffd7a9b7005cfd7198 2106 python-imaplib2_2.57-5.dsc 34df52e0552644a000bef9f836c44883ecfe343dd1faeeab6cc3c36698037a57 6760 python-imaplib2_2.57-5.debian.tar.xz d569da6c046e24f4e35870b16f3894d5ed4348f217fe66728116bd68f612accc 7071 python-imaplib2_2.57-5_amd64.buildinfo Files: 3040a12eb536b4722652aabcd720ead6 2106 python optional python-imaplib2_2.57-5.dsc 1cda4183c1879c31e6c63aab86de6d41 6760 python optional python-imaplib2_2.57-5.debian.tar.xz 478ef3b5a6f3657b58b0ac0d9209f4e5 7071 python optional python-imaplib2_2.57-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlugwbsUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDzM+A/8COyxaWKfg+TJV1XFV3hiM+2nc3WZ sECAlNYU4+2TuQD3eKbCo2vQjt3hyr0WTk4kY8AxBdg9L/m2cLflfNW3Jfc773F9 v9ITaaso8tt/ie2tQt8DnOxOuCcCF92Iq2Us9EGJDzaLxLShw9Ip/+7nR+T1ma2/ HC/dUm0rmv8iBsi3pxwa39FwDxQsY6TSx5U6KfYB4QjIj3wnT6E7boKlvXpIPRA4 Y4o2dXNGGCulH56N6JU5tkdtWRDKlyUFJMIqWnn34UJSKO3E7WmgrpPcjnL3iG4h 2wwdNsYmTLzT/34crYNwgjcD6RxIKkBmBxCr3edELuArQcYiPlxUCtWYqw+aGier +y7HRCcQWNrIWKgD/82ZuelhsodYY+q6/eS6Z4/PWazVFy+4Y5EnwL+2SUbiVe+S 4zFdx25F5QblmuDOH3SHW+xq/+zcMUHdXTE6bG/+4zbTyKpuVpfgFza7E3yCU21g 8wi2KNrpOTXrC0e0Jo7SL8A+NoZMFB3akoSH8I/FYieNlC9Qtk9nhwe5UrP8jXZF gJzOcajbSGL4NrwX6Pl79TEujTj2rsosRYdjg2e46Biwl8f1LBQKv+vegHFikHO/ Ky1eBSHvZ/ZRx8IBDG4B7rKbuxvzJ/9/c+AS+e0k
Processed: affects 909076
Processing commands for cont...@bugs.debian.org: > affects 909076 + security.debian.org Bug #909076 [ghostscript] ghostscript: ps2ascii crashes: Error: /typecheck in --.bind-- Added indication that 909076 affects security.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 909076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905706: [Debian-med-packaging] Bug#905706: libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js
On 09/18/2018 10:02 AM, Olivier Sallou wrote: > > On 09/17/2018 04:36 PM, Andreas Tille wrote: >> Control: tags -1 pending >> >> This issue should be fixed in >> >> https://salsa.debian.org/med-team/picard-tools/commit/4da851972983cee93a3cce27bfbb40f9648dcc3d >> >> >> While fixing the bug I also tried to upgrade the package to the latest >> upstream >> version. Unfortunately this failed with: >> >> >> Compiling build file '/build/picard-tools-2.18.14+dfsg/build.gradle' using >> BuildScriptTransformer. >> Adding Maven pom generation to project 'picard' >> Linking the generated javadoc to the system JDK API documentation >> >> FAILURE: Build failed with an exception. >> >> * Where: >> Build file '/build/picard-tools-2.18.14+dfsg/build.gradle' line: 53 I have fixed the build issue, and pushed updates in git. build was tested against latest htsjdk 2.16.1 (not yet pushed to sid) >> >> * What went wrong: >> A problem occurred evaluating root project 'picard'. >>> The ClassLoader obtained from the Java ToolProvider is null. A Java 8 JDK >>> must be installed. See >>> https://github.com/broadinstitute/picard/blob/master/README.md#building-picard >>> for information on how to build picard > I fixed the issue and could compile, however there is one test failing > for the moment. > I gonna investiguate and push my updates afterwards. > > Olivier >> * Try: >> Run with --debug option to get more log output. >> >> * Exception is: >> org.gradle.api.GradleScriptException: A problem occurred evaluating root >> project 'picard'. >> at >> org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:92) >> at >> org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:176) >> at >> org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) >> at >> org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:181) >> at >> org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:39) >> at >> org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26) >> at >> org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34) >> at >> org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:70) >> at >> org.gradle.configuration.project.LifecycleProjectEvaluator.access$000(LifecycleProjectEvaluator.java:33) >> at >> org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:53) >> at >> org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:50) >> at >> org.gradle.internal.Transformers$4.transform(Transformers.java:169) >> at >> org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106) >> at >> org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61) >> at >> org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:50) >> at >> org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:599) >> at >> org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:125) >> at >> org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35) >> at >> org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:60) >> at >> org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:38) >> at >> org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:233) >> at >> org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:230) >> at >> org.gradle.internal.Transformers$4.transform(Transformers.java:169) >> at >> org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106) >> at >> org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:56) >> at >> org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:160) >> at >> org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:119) >> at >> org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:102) >> at >> org.gradle.launcher.exec.GradleBuildController.run(GradleBuildController.java:71) >> at >> org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActi
Bug#903580: aegisub still can't be installed on unstable
Package: aegisub Version: 3.2.2+dfsg-3+b6 Followup-For: Bug #903580 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I'm trying to install aegisub on a sid machine * What exactly did you do (or not do) that was effective (or ineffective)? apt install aegisub * What was the outcome of this action? The following packages have unmet dependencies: aegisub : Depends: libboost-regex1.62.0 but it is not going to be installed apt install libboost-regex1.62.0 libboost-regex1.62.0 is already the newest version (1.62.0+dfsg-10). * What outcome did you expect instead? to install and run? :-) *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages aegisub depends on: ii libasound2 1.1.6-1 ii libass91:0.14.0-2 ii libboost-filesystem1.62.0 1.62.0+dfsg-10 ii libboost-locale1.62.0 1.62.0+dfsg-10 ii libboost-regex1.62.0 1.62.0+dfsg-10 ii libboost-system1.62.0 1.62.0+dfsg-10 ii libboost-thread1.62.0 1.62.0+dfsg-10 ii libc6 2.27-6 ii libffms2-4 2.23-3+b1 ii libfftw3-double3 3.3.8-2 ii libfontconfig1 2.13.0-5 ii libgcc11:8.2.0-6 ii libgl1 1.1.0-1 ii libgl1-mesa-glx18.1.8-1 ii libhunspell-1.6-0 1.6.2-1+b1 ii libicu57 57.1-9 ii libluajit-5.1-22.1.0~beta3+dfsg-5.1 ii libpulse0 12.2-2 ii libstdc++6 8.2.0-6 ii libwxbase3.0-0v5 3.0.4+dfsg-4 ii libwxgtk3.0-0v53.0.4+dfsg-4 ii zlib1g 1:1.2.11.dfsg-1 aegisub recommends no packages. Versions of packages aegisub suggests: pn aegisub-l10n
Bug#905706: [Debian-med-packaging] Bug#905706: libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js
On 09/17/2018 04:36 PM, Andreas Tille wrote: > Control: tags -1 pending > > This issue should be fixed in > > https://salsa.debian.org/med-team/picard-tools/commit/4da851972983cee93a3cce27bfbb40f9648dcc3d > > > While fixing the bug I also tried to upgrade the package to the latest > upstream > version. Unfortunately this failed with: > > > Compiling build file '/build/picard-tools-2.18.14+dfsg/build.gradle' using > BuildScriptTransformer. > Adding Maven pom generation to project 'picard' > Linking the generated javadoc to the system JDK API documentation > > FAILURE: Build failed with an exception. > > * Where: > Build file '/build/picard-tools-2.18.14+dfsg/build.gradle' line: 53 > > * What went wrong: > A problem occurred evaluating root project 'picard'. >> The ClassLoader obtained from the Java ToolProvider is null. A Java 8 JDK >> must be installed. See >> https://github.com/broadinstitute/picard/blob/master/README.md#building-picard >> for information on how to build picard I fixed the issue and could compile, however there is one test failing for the moment. I gonna investiguate and push my updates afterwards. Olivier > * Try: > Run with --debug option to get more log output. > > * Exception is: > org.gradle.api.GradleScriptException: A problem occurred evaluating root > project 'picard'. > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:92) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:176) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:181) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:39) > at > org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26) > at > org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34) > at > org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:70) > at > org.gradle.configuration.project.LifecycleProjectEvaluator.access$000(LifecycleProjectEvaluator.java:33) > at > org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:53) > at > org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:50) > at org.gradle.internal.Transformers$4.transform(Transformers.java:169) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61) > at > org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:50) > at > org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:599) > at > org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:125) > at > org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35) > at > org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:60) > at > org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:38) > at > org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:233) > at > org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:230) > at org.gradle.internal.Transformers$4.transform(Transformers.java:169) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:56) > at > org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:160) > at > org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:119) > at > org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:102) > at > org.gradle.launcher.exec.GradleBuildController.run(GradleBuildController.java:71) > at > org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28) > at > org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) > at > org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:41) > at > org.gradle.launcher.exec.InPro
Processed: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Processing control commands: > affects -1 diffoscope Bug #909076 [ghostscript] ghostscript: ps2ascii crashes: Error: /typecheck in --.bind-- Added indication that 909076 affects diffoscope -- 909076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Package: ghostscript Version: 9.20~dfsg-3.2+deb9u5 Severity: serious X-Debbugs-CC: t...@security.debian.org, Moritz Mühlenhoff , reproducible-bui...@lists.alioth.debian.org Control: affects -1 diffoscope Dear maintainer, after the latest ghostscript security update, ps2ascii started to crash: |% ps2ascii /build/diffoscope-101~bpo9+1/.pybuild/pythonX.Y_3.5/build/tests/data/test1.ps |Error: /typecheck in --.bind-- |Operand stack: | --nostringval-- false setshared true --dict:30/32(L)-- typecheck --nostringval-- currentglobal .currentglobal |Execution stack: | %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1998 2 3 %oparray_pop 1997 2 3 %oparray_pop 1981 2 3 %oparray_pop 1868 2 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 2009 3 3 %oparray_pop --nostringval-- --nostringval-- --dict:1267/1684(G)-- --nostringval-- 1936 %dict_continue --nostringval-- 1974 9 4 %oparray_pop --nostringval-- |Dictionary stack: | --dict:1267/1684(G)-- --dict:0/20(G)-- --dict:81/200(L)-- --dict:1267/1684(G)-- |Current allocation mode is global |Current file position is 44643 |GPL Ghostscript 9.20: Unrecoverable error, exit code 1 Downgrading to 9.20~dfsg-3.2+deb9u4 shows the problem is limited to the latest update: |% ps2ascii /build/diffoscope-101~bpo9+1/.pybuild/pythonX.Y_3.5/build/tests/data/test1.ps | | |Today's date: February 28, 2016 | |1 This also causes diffoscope (both 78 in stretch and whatever is in stretch-backports at the moment) to FTBFS. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#909075: Keep libhandy out of testing for now
Source: libhandy Version: Keep libhandy out of testing Severity: grave While there will be users showing up let's keep libhandy out of testing to spare library transitions until things have settled in. Cheers, -- Guido -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working
On 18/09/18 17:55, Mike Hommey wrote: So the crash is happening in JITed code, which is not expected: the JIT should disable itself. There might be something wrong either in the detection or maybe some parts don't disable themselves as they're supposed to. Can you try starting with `firefox-esr -safe-mode`? That works. If that works, can you then go to about:config and switch javascript.options.ion to false, then restart without -safe-mode? That crashes. If that works, stop there. If it doesn't work, can you try -safe-mode again, and switch javascript.options.baselinejit to false? And now it works in non-safe-mode! Incidentally, since you're talking about Javascript, I thought it might be relevant that I'm using the NoScript add-on, so I thought I'd try disabling that (which worked), and setting javascript.options.baselinejit and javascript.options.ion back to true. When I switched javascript.options.baselinejit back to true, Firefox instantly crashed. (But, of course, it's recoverable again via -safe-mode.) Setting only javascript.options.ion back to true *doesn't* crash Firefox, or prevent it from starting. Tim <><
Bug#900401: marked as done (/usr/bin/virsh: After latest Debian upgrade many commands stopped working)
Your message dated Tue, 18 Sep 2018 08:57:26 +0200 with message-id <20180918065726.ga2...@bogon.m.sigxcpu.org> and subject line Re: Bug#900401: libvirt-daemon: Both virsh and virt-manager hang on connection after dist-upgrade has caused the Debian Bug report #900401, regarding /usr/bin/virsh: After latest Debian upgrade many commands stopped working 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.) -- 900401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libvirt-clients Version: 3.0.0-4+deb9u3 Severity: important File: /usr/bin/virsh Dear Maintainer, virsh commands like virsh list virsh shutdown hangs directly when issued. virsh can be started as a shell but when the commands are executed it hangs. This happens even if virsh is run as root. Nothing is seen in syslog. The commands did work before the latest qemu sets of packages where installed. (I am following Debian stable) Maybe this a problem of on of those packages instead? -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libvirt-clients depends on: ii libapparmor12.11.0-3+deb9u2 ii libaudit1 1:2.6.7-2 ii libavahi-client30.6.32-2 ii libavahi-common30.6.32-2 ii libc6 2.24-11+deb9u3 ii libcap-ng0 0.7.7-3+b1 ii libdbus-1-3 1.10.26-0+deb9u1 ii libdevmapper1.02.1 2:1.02.137-2 ii libgnutls30 3.5.8-5+deb9u3 ii libnl-3-200 3.2.27-2 ii libnl-route-3-200 3.2.27-2 ii libnuma12.0.11-2.1 ii libreadline77.0-3 ii libsasl2-2 2.1.27~101-g0780600+dfsg-3 ii libselinux1 2.6-3+b3 ii libssh2-1 1.7.0-1 ii libvirt03.0.0-4+deb9u3 ii libxen-4.8 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libyajl22.1.0-2+b3 libvirt-clients recommends no packages. Versions of packages libvirt-clients suggests: ii libvirt-daemon 3.0.0-4+deb9u3 -- no debconf information --- End Message --- --- Begin Message --- Version: libvirt-daemon/4.3.0-1 Hi, On Mon, Sep 17, 2018 at 02:30:58PM -0400, Paul Sandulescu wrote: >The way I solved this, and it's been a while now, is by building libvirt >from apt-get source. No patch, same version, everything worked. Maybe some >package corruption occurred, although symptoms were quite unusual. I think >you can close this one. Thanks for reportin back. Closing then. Cheer, -- Guido--- End Message ---
