Bug#917330: marked as done (ruby-kitchen-salt: Incomplete debian/copyright?)
Your message dated Thu, 27 Dec 2018 06:49:33 + with message-id and subject line Bug#917330: fixed in ruby-kitchen-salt 0.4.0-2 has caused the Debian Bug report #917330, regarding ruby-kitchen-salt: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-kitchen-salt Version: 0.4.0-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Mathieu Parent , ftpmas...@debian.org Hi, I just ACCEPTed ruby-kitchen-salt from NEW but noticed it was missing attribution in debian/copyright for at least Chris Lundquist. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: ruby-kitchen-salt Source-Version: 0.4.0-2 We believe that the bug you reported is fixed in the latest version of ruby-kitchen-salt, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Parent (supplier of updated ruby-kitchen-salt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 27 Dec 2018 07:22:27 +0100 Source: ruby-kitchen-salt Binary: ruby-kitchen-salt Architecture: source all Version: 0.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Mathieu Parent Description: ruby-kitchen-salt - salt provisioner for test-kitchen Closes: 917330 Changes: ruby-kitchen-salt (0.4.0-2) unstable; urgency=medium . * Add missing copyright holder (Closes: #917330) * Fix Depends s/ruby-test-kitchen/test-kitchen/ * Standards-Version: 4.3.0 Checksums-Sha1: c64a6029d491707b50a472b5c6e19aae11968d74 2128 ruby-kitchen-salt_0.4.0-2.dsc daa889be6753faedbc9f1283e453ef271a99dc74 1972 ruby-kitchen-salt_0.4.0-2.debian.tar.xz e512c584f48cffcac5eab1f0303fc3de6055744b 15616 ruby-kitchen-salt_0.4.0-2_all.deb aede04fe9f7d3adaffda909d3cfd035c9b06a91b 9275 ruby-kitchen-salt_0.4.0-2_amd64.buildinfo Checksums-Sha256: a8f76e4674269700422a4fb3c3150be5bc4195d801a97423c76b6651692ba2b3 2128 ruby-kitchen-salt_0.4.0-2.dsc 68be9430b6497f626668acded944417866645eff6777af43bbb772247a47cdda 1972 ruby-kitchen-salt_0.4.0-2.debian.tar.xz 78066ed6179edeec3c5c6ee5fb56880d53a371dfa4f5d738df1c1e55a02e2874 15616 ruby-kitchen-salt_0.4.0-2_all.deb 0b80c84c883305efb200189399f3b7bf5c307d0a57825343a91547ff62dbef32 9275 ruby-kitchen-salt_0.4.0-2_amd64.buildinfo Files: 8f890643506cef1efde99d909347652c 2128 ruby optional ruby-kitchen-salt_0.4.0-2.dsc eead6089c497e3cfe3b4dde686c9f5df 1972 ruby optional ruby-kitchen-salt_0.4.0-2.debian.tar.xz e866d085a83a61bcab9647671535850a 15616 ruby optional ruby-kitchen-salt_0.4.0-2_all.deb 0aa5a6c6802ba8b4523950933e351f9b 9275 ruby optional ruby-kitchen-salt_0.4.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEqIGbPTP9weQZ135HrgOYBGZoH6UFAlwkceYACgkQrgOYBGZo H6Xn2BAAossH1OBWfG3iyfbCEWuKuiNOZ9pPBERH8XPoIn2Yo0XTiZ2sabjc+J8m QISUEkAZI4/Qw2WoFVNsPTUWvxolF5y6wLSiPd/A/FW/Wv5YWrXVG9/HS+9jeH2l lcW3J0rv+OBKzo6h0AzEa6Bc0eS12unOy6Wtu+HLaRCfUtgcFWJLLCjNIODabMNB 9jXHRE5VtWCa+bqlQ5cHFsOgat1OufRArcf8FOx37E0DKAy1HQhAyhV20IGYbZI9 zE7r2prqTsEcU0a/Xcz68Qv1PKgqlTXl2YJfvSYoZWbSrrb9q+AJ2CJi72/HHEoJ ddHTmGPHvFztt7JNUrwWxqojNivB6wZZso22uRIHnrUX/ltov4doEDZNLf4/h3cw alP2LWUoYE0qxiVCc8Toqfs5cX8AKiJwOuzaQjv4VksVGEdpxspwRACiZMu57bqx WpFqicvJ2RFeJGc6siYKubEKoKlhJeulnm2iHyIdpwgy4iU2ry903lP/85HwTh54 52Dd/kj8n8JvE0y0QrLG5zeUkHTylKL2M4/omEr61b3H6uL9aIlkYxnVtqB3iV76 2WdxwL7fbsY+wo6GHgDEoAKX+20jr6nI8ntHGURQ1Jx/UbIhTh44EI7XPx2d6BIz cq3mFaS/HEDh+ramasrfTlX/aQQ2ZmGydmyuSNLSqrxoqDkU+f8= =5v/H -END PGP SIGNATURE End Message ---
Bug#917330: Bug #917330 in ruby-kitchen-salt marked as pending
Control: tag -1 pending Hello, Bug #917330 in ruby-kitchen-salt 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/ruby-kitchen-salt/commit/81897d3dede4497b770198bae8b7916b32dd6614 Add missing copyright holder (Closes: #917330) (this message was generated automatically) -- Greetings https://bugs.debian.org/917330
Processed: Bug #917330 in ruby-kitchen-salt marked as pending
Processing control commands: > tag -1 pending Bug #917330 [src:ruby-kitchen-salt] ruby-kitchen-salt: Incomplete debian/copyright? Added tag(s) pending. -- 917330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915691: [Pkg-samba-maint] Samba packages broken on powerpcspe
Le mer. 26 déc. 2018 à 05:43, Vojtech Ruml a écrit : > > Hello, Hello, > > > Samba-common package (= 2:4.9.2+dfsg-2 > > was not built and whole samba installation on my system is completely broken > now. > > Is it possible to resolve this situation ? https://buildd.debian.org/status/package.php?p=samba has: > Dependency installability problem for samba on powerpcspe: > > samba build-depends on: > - glusterfs-common:powerpcspe > glusterfs-common depends on missing: > - liblvm2app2.2:powerpcspe (>= 2.02.176) And glusterfs has build-dependency liblvm2-dev uninstallable on all arches (see https://buildd.debian.org/status/package.php?p=glusterfs=sid). Relevant bug: https://bugs.debian.org/915691 glusterfs-common - Depends on deprecated liblvm2app Patrick, do you intent to work on it soon? If not, I will drop glusterfs support in Samba. Regards Mathieu Parent > > > Thank you, > > > > Vojtech Ruml > > > > root@debian:/data# apt-get install samba > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > samba : Depends: samba-common (= 2:4.9.2+dfsg-2) but 2:4.9.4+dfsg-1 is to be > installed > > Depends: samba-common-bin (= 2:4.9.2+dfsg-2) but it is not going to > be installed > > E: Unable to correct problems, you have held broken packages. > > root@debian:/data# > > ___ > Pkg-samba-maint mailing list > pkg-samba-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-samba-maint
Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup
On Wed, 26 Dec 2018 15:39:19 + Ben Hutchings wrote: > On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote: > > On Tue, 25 Dec 2018 20:52:46 + > > Ben Hutchings wrote: > > > > > Control: reassign -1 udev 240-1 > > > Control: forcemerge 917124 -1 > > > > > > This seems to be a bug in udev, not the kernel. You will only have > > > noticed it once you rebooted for the kernel upgrade. > > > > Nope - in my system's current state, when rebooting into 4.19 there's > > no /dev/mapper symlink, but when rebooting into 4.18 there is. I've > > gone back and forth several times, and the behavior is consistent. > > There's clearly something that 4.19 is doing differently from 4.18. [I > > guess it might still be a udev bug, which is being exposed by some > > change in 4.19.] > > This is probably because the initramfs for 4.18 contains the old > version of udev. Okay, I think I understand. So if I were to update the 4.18 initramfs (with update-initramfs -k 4.18-nnn) now, I would expect to see the same problem with that kernel? Celejar
Bug#916150: marked as done (sketch FTBFS: sketch.texi: Dimension too large)
Your message dated Thu, 27 Dec 2018 01:24:20 +
with message-id
and subject line Bug#916150: fixed in sketch 1:0.3.7-10
has caused the Debian Bug report #916150,
regarding sketch FTBFS: sketch.texi: Dimension too large
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.)
--
916150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sketch
Version: 1:0.3.7-9
Severity: serious
Tags: ftbfs
Some recent change in unstable makes sketch FTBFS:
https://tests.reproducible-builds.org/debian/history/sketch.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sketch.html
...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
(preloaded format=etex)
restricted \write18 enabled.
entering extended mode
(./sketch.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2018-01-09.11]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(/build/1st/sketch-0.3.7/Doc/version.texi)
Writing index file sketch.sx
[1] [2] [-1] Chapter 1
Writing index file sketch.cp
(ex000.eps
)
./sketch.texi:257: Dimension too large.
@epsfxsize
@epsfspecial #1->@epsftmp =10@epsfxsize
@divide @epsftmp by @pspoints @ifnum...
@epsfsetgraph ... to @epsfxsize {@epsfspecial {#1}
@hfil }@else @vfil @hbox t...
@imagexxx ...ysize =#3@relax @fi @epsfbox {#1.eps}
@else @doxeteximage {#1}{#...
@image ...true @fi @else @imagexxx #1,@finish
@fi
@hfil @ignorespaces @image {ex000}
@unskip @hfil
...
l.257 @center @image{ex000}
?
./sketch.texi:257: Emergency stop.
@epsfxsize
@epsfspecial #1->@epsftmp =10@epsfxsize
@divide @epsftmp by @pspoints @ifnum...
@epsfsetgraph ... to @epsfxsize {@epsfspecial {#1}
@hfil }@else @vfil @hbox t...
@imagexxx ...ysize =#3@relax @fi @epsfbox {#1.eps}
@else @doxeteximage {#1}{#...
@image ...true @fi @else @imagexxx #1,@finish
@fi
@hfil @ignorespaces @image {ex000}
@unskip @hfil
...
l.257 @center @image{ex000}
Output written on sketch.dvi (3 pages, 2088 bytes).
Transcript written on sketch.log.
/usr/bin/texi2dvi: etex exited with bad status, quitting.
Died at make.pl line 87, line 3335.
make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: sketch
Source-Version: 1:0.3.7-10
We believe that the bug you reported is fixed in the latest version of
sketch, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Bremner (supplier of updated sketch package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 27 Dec 2018 09:02:19 +0900
Source: sketch
Binary: sketch sketch-doc
Architecture: source
Version: 1:0.3.7-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: David Bremner
Description:
sketch - 3D diagrams for TeX from scene description language
sketch-doc - Extra documentation for the sketch 3D line drawing system
Closes: 916150
Changes:
sketch (1:0.3.7-10) unstable; urgency=medium
.
* Disable epstool in building documentation. (Closes: #916150).
* Add build-dep on texlive-science for siunitx.sty
Checksums-Sha1:
407f826b8c5a80fbfb1a0d0f0cdb2ab9c0819358 2035 sketch_0.3.7-10.dsc
Bug#917383: Precision 5530 unbootable
Package: debian-installer Version: Buster Alpha 4 Severity: critical Tags: d-i Hello, after installing a Precision 5530 with the Alpha 4 version of Buster, the system is unbootable, except for a grub without any configuraiton. Ie, to boot Linux, you need to enter all the partition, modules, kernel and initrd information manually. Cheers, Toni -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#916346: marked as done (crrcsim build depends on libjpeg9-dev)
Your message dated Wed, 26 Dec 2018 23:49:19 + with message-id and subject line Bug#916346: fixed in crrcsim 0.9.13-3.1 has caused the Debian Bug report #916346, regarding crrcsim build depends on libjpeg9-dev 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.) -- 916346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crrcsim Version: 0.9.13-3 Severity: serious crrcsim build depends on libjpeg9-dev that might never be part of a stable release. Please go back to libjpeg-dev. --- End Message --- --- Begin Message --- Source: crrcsim Source-Version: 0.9.13-3.1 We believe that the bug you reported is fixed in the latest version of crrcsim, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated crrcsim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Dec 2018 01:02:57 +0200 Source: crrcsim Binary: crrcsim crrcsim-data crrcsim-doc Architecture: source Version: 0.9.13-3.1 Distribution: unstable Urgency: medium Maintainer: Agustin Henze Changed-By: Adrian Bunk Description: crrcsim- Model-Airplane Flight Simulator crrcsim-data - Data files for crrcsim package crrcsim-doc - Documentation for crrcsim package Closes: 916346 Changes: crrcsim (0.9.13-3.1) unstable; urgency=medium . * Non-maintainer upload. * Switch back to the libjpeg that will be in buster. (Closes: #916346) Checksums-Sha1: 0a7312c057ae6192b8a13b341ea30326fd4983eb 2072 crrcsim_0.9.13-3.1.dsc 796646118c6a42b4688d4d7c600234921c08fc12 10032 crrcsim_0.9.13-3.1.debian.tar.xz Checksums-Sha256: 00a858ec10db23b7df55682f579ae647427a1322748f6fcc3e4c6f5aa386168f 2072 crrcsim_0.9.13-3.1.dsc 989b8152c523402b6e8bf601bb096dc26406d5f0980040f0f43b95323da6e045 10032 crrcsim_0.9.13-3.1.debian.tar.xz Files: bfec05439184409ed085dc48faac9339 2072 games optional crrcsim_0.9.13-3.1.dsc a3d426c5b545ec878ffa1623e78a204b 10032 games optional crrcsim_0.9.13-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlwdcvkACgkQiNJCh6LY mLGc1Q//VwUFbJlhBnscpLWYC1MK5LEOBk+xEVtyfCwWOau0ACCrpG8nXbwsQGZq 5GibTGKIM9vmlsB6spZcXCOmPbN8dcxt5yG9BT0rBDjDbTi+vo9eggiEwIe2qTil X//BFYNTZK2un5Fm3jKbFm/D+2C7CRdJq2av4LsY20itKS0+hdNLRPvhc2L5oy50 MYbZipDjyVrU/Sk59kFXrxmEh1fMGGgAMLI+rTwt3wHfRsiiuIK2fcNzFGysJY4B 2/vKDTmWT2dEJcjkT7diiCLOv66uwkf/KAMoMDKkE4rnKsVbyb2dcnhFdNKI+Bmu 0VL9oYBK6W/aNiI/02g6EUJ0QhEcSJKL1Jm84PGcFmfA4qT7QNN2ojG39gMlikxv FPCGbgYJerbYlj7BNyHlyvahKW94c9jGQgeToYCphPcYHqUQlGXxCX7ew8+1Q9hA nJmtJmaMmJmMPmdH9gd6U2Fk8zQ2uTIYz97VBBa38BI4EueHgwgz4S5x5jdIIg1F vGXOCYwTZWtXuW2pJ927L2znmIzAwhAO/gHqJ3v11+RoBOBTee3oHmPiDE1q6kdH rrMAYqCLG2BzpbIwzuJZoNLtHnV3NC3S39ARJKt1VDKsQguQJTZDIoP+nybU6fps +3HK7NpUEh2ov5hmQdUcGBT9QAxTy4kgAJ7AbKZdM64/uW+A17M= =PBA0 -END PGP SIGNATURE End Message ---
Bug#917382: Should stunserver be removed?
Source: stunserver Severity: serious Should stunserver be removed from the archive? - It's unmaintained (last maintainer upload in 2015) - Dropped from testing over a year ago - Marginal popcon - RC-buggy (one of the handful of remaining packages blocking the removal of OpenSSL 1.0) Cheers, Moritz
Bug#897586: marked as done (src:sogo: FTBFS with gnustep-make in strict v2 mode: specified prefix is not a GNUstep root: '/usr/System')
Your message dated Wed, 26 Dec 2018 23:09:17 + with message-id and subject line Bug#897586: fixed in sogo 4.0.4-2 has caused the Debian Bug report #897586, regarding src:sogo: FTBFS with gnustep-make in strict v2 mode: specified prefix is not a GNUstep root: '/usr/System' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sogo Version: 4.0.0-1 Severity: important User: pkg-gnustep-maintain...@lists.alioth.debian.org Usertags: make-strict-v2-mode The next Debian release of gnustep-make will switch to strict v2 mode; your package FTBFS with the following error: make[1]: Entering directory '/<>' ./configure --with-ssl=gnutls --enable-saml2 --prefix=/usr/System GNUstep environment: system: local: user: path: flat: arch: combo: error: specified prefix is not a GNUstep root: '/usr/System' make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 1 --- End Message --- --- Begin Message --- Source: sogo Source-Version: 4.0.4-2 We believe that the bug you reported is fixed in the latest version of sogo, 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. Jordi Mallach (supplier of updated sogo 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, 26 Dec 2018 23:44:11 +0100 Source: sogo Binary: sogo sogo-common Architecture: source Version: 4.0.4-2 Distribution: unstable Urgency: medium Maintainer: Debian SOGo Maintainers Changed-By: Jordi Mallach Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files Closes: 897586 Changes: sogo (4.0.4-2) unstable; urgency=medium . * Do not pass --prefix to configure (closes: #897586). Checksums-Sha1: 4584a9795366293c964b281eecf73969e56caad4 2135 sogo_4.0.4-2.dsc 2fa17e40a6b22b4e0f158204bc32e6996b2080f3 14432 sogo_4.0.4-2.debian.tar.xz db0f2b41d62edc021a94f6ae17eb7bad3ee3f595 7170 sogo_4.0.4-2_source.buildinfo Checksums-Sha256: 380a7ea0e006c3e822c54548fd9c09e26b1a08e10e96261c38a1d553166fb123 2135 sogo_4.0.4-2.dsc 795af1af44719dc7e068329e789b446055ca4425acc4c493d2b3bbfccedb9c73 14432 sogo_4.0.4-2.debian.tar.xz eb28cea6db1543d83f86023f123ce17fef98c883db7173943d77b506b97157d2 7170 sogo_4.0.4-2_source.buildinfo Files: 9f0df9111e9ac82138b17a672ad25b56 2135 mail optional sogo_4.0.4-2.dsc c70e95234297dd8bbf03be29ba721dcc 14432 mail optional sogo_4.0.4-2.debian.tar.xz 0346f64265498a5f18249f658910f89a 7170 mail optional sogo_4.0.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlwkBHcRHGpvcmRpQGRl Ymlhbi5vcmcACgkQJVAvb8vjywThUhAAsbemLJy4/1cQc5hLU5yH67RT+dt66Tmd UhjCqvJqHq+A36yQ5zCwrMp0gAYxnh1fg253aGPN1cOshFdTRU0LatjbOCpTYryD Tn2Kh9DQbN79PLP3Qmr1bVi9ijIa/ZAzzO8L/qCEDIeu9mduFrRIQQKK9PWi6qCG NmygEwunmi1w31yimID6CQ5kxXXV3c9BVcw04SDuYInCzLH2AElpdLrjNxVxOHw+ naec2CTC86/IXdqf9sqjjcj0j/314wCjaQu3IA0lWXzfZR80QsTmG0+Gcxeq1viy xZPN0lNdwhq5ZYvFJ9/6fvS7uEDkSBpGidEN7IQNfYedl+oBfd6Ul+OIDgy+GfLk clSBmBhFwHq+54YVhRHZcl99QgyTnx5FTPvgw7Qr0RXLN8x+cu+lk0C6Qvr479Qw 1oXNfGUchQhJT+oijbZiJnTLGuVYicYxDNg48BPrQbNOWvNAIenV3n1/9Vp2v/tF YcEQR8zMj+Y+DEdxJoV8WCpkW2Lhl+OahRQgkSAe0iNAKtjiasvzPzuovNOspqSk ZSCwFri1TTowD0LlOO3Qb4kpUw1m7Bjw73A+FjFXg1Waz/gIpuTbg0ISZwBm8Rks 8r8Rxn/yuYZagoe32b7MNSmWM8mNpJr42/LROfMdQnR3xDmz48lMgtTy3qTxzSU3 nCkIhFwRxaQ= =7PON -END PGP SIGNATURE End Message ---
Bug#917380: libmed1v5: libmed.so.1 link is not created
Package: libmed1v5 Version: 4.0.0+repack-1 Severity: grave Justification: renders package unusable The link /usr/lib/libmed.so.1 is no more created which breaks for instance the gmsh package since the libgmsh depends on libmed1v5: Package: libgmsh3 Source: gmsh Version: 3.0.6+dfsg1-4 Installed-Size: 18643 Maintainer: Debian Science Maintainers Architecture: amd64 Depends: libann0, libblas3 | libblas.so.3, libc6 (>= 2.14), libcgns3.3 (>= 3.1.4.2), libfltk-gl1.3 (>= 1.3.0), libfltk-images1.3, libfltk1.3 (>= 1.3.4), libgcc1 (>= 1:4.0), libgl1, libgl2ps1.4, libglu1-mesa | libglu1, libjpeg62-turbo (>= 1.3.1), liblapack3 | liblapack.so.3, libmed1v5, libocct-data-exchange-7.3, libocct-foundation-7.3, libocct-modeling-algorithms-7.3, libocct-modeling-data-7.3, libopenmpi3, libpng16-16 (>= 1.6.2-1), libstdc++6 (>= 5.2), libtet1.5, libx11-6 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8), LANGUAGE= (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmed1v5 depends on: ii libc62.28-3 ii libgcc1 1:8.2.0-13 ii libgfortran5 8.2.0-13 ii libhdf5-openmpi-103 1.10.4+repack-2 ii libopenmpi3 3.1.3-6 ii libquadmath0 8.2.0-13 ii libstdc++6 8.2.0-13 libmed1v5 recommends no packages. Versions of packages libmed1v5 suggests: pn libmed-doc pn libmed-tools -- no debconf information
Bug#916523: marked as done (pyvo: Please remove Python 2 package)
Your message dated Wed, 26 Dec 2018 22:04:54 + with message-id and subject line Bug#916523: fixed in pyvo 0.9.2-1 has caused the Debian Bug report #916523, regarding pyvo: Please remove Python 2 package 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.) -- 916523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyvo Version: 0.8.1-1 Severity: serious Hi, as discussed in the Debian Astro mailing list [1], the Python 2 "python-astropy" package will be dropped, which requires that its reverse dependencies are removed before. This affects this package, since its Python-2 binary package depends from astropy. Could I ask you to remove it? Thanks Ole [1] https://lists.debian.org/debian-astro/2018/11/msg00016.html --- End Message --- --- Begin Message --- Source: pyvo Source-Version: 0.9.2-1 We believe that the bug you reported is fixed in the latest version of pyvo, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated pyvo 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, 26 Dec 2018 15:20:14 -0600 Source: pyvo Binary: python3-pyvo Architecture: source all Version: 0.9.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Josue Ortega Description: python3-pyvo - Python 3 library for data services of the Virtual observatory (VO Closes: 916523 Changes: pyvo (0.9.2-1) unstable; urgency=medium . * New upstream release (0.9.2): - Remove debian/patches/00-fix-async-compat-python37.patch since it has been applied by upstream. * Remove Python 2 package (Closes: #916523). * Bump Standards Version to 4.3.0, no changes were required. Checksums-Sha1: d4468deadb89effd1256f937b30b8aad33eba018 2191 pyvo_0.9.2-1.dsc 133fc0bbf79399bc1da517d564fab3cf301ce503 2157617 pyvo_0.9.2.orig.tar.gz dc17103df52b28519a1fec428ccfdc77669302ef 3980 pyvo_0.9.2-1.debian.tar.xz dbb41d0abe3560ce354156fb97c8601fe48cff34 1284468 python3-pyvo_0.9.2-1_all.deb aabca40598e80613e6d7c554e82e50abc49139a2 7723 pyvo_0.9.2-1_amd64.buildinfo Checksums-Sha256: 37d778cc8b2183b7561799084f81df75ce66dc7c2d0ded62c8fff44f367d8cad 2191 pyvo_0.9.2-1.dsc 8b618a80d890abcfd915e9597e87388f4dfaf283c8cc7e0fad44586b260fb482 2157617 pyvo_0.9.2.orig.tar.gz 8334280cfa81b84f77c22c075b2e991a52560c0c47f4f3ba446c04a1d09a3766 3980 pyvo_0.9.2-1.debian.tar.xz 9215afd3354114fa6d47e61c3de6580bd161e83fc616ad1b9b0e607c7ed0e72a 1284468 python3-pyvo_0.9.2-1_all.deb b669dc1867209c6bc44d29eff30766f070d42d3e05119cea4073a1ebe7cc31ac 7723 pyvo_0.9.2-1_amd64.buildinfo Files: 1a2c4655514f757500305aea99bfd6bb 2191 python optional pyvo_0.9.2-1.dsc 3132dfc067bbef70c8ae3cd04e8912ce 2157617 python optional pyvo_0.9.2.orig.tar.gz a4ed15f06bde9ad3b269323bdcc23185 3980 python optional pyvo_0.9.2-1.debian.tar.xz 9bf90ca0c30649ae3cb460633a92f930 1284468 python optional python3-pyvo_0.9.2-1_all.deb 8144de9a59225d815782b6161025ee89 7723 python optional pyvo_0.9.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlwj9rMRHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+i2xAAmnGnBxkxYcQiYq+NymQANwLmpvLfsRs+ 2Qj+kU7H5saLacLa4oTVa5dpkvyqhwAJB4YfcZ74t16VBBR7ndiE+mcoF8crVUny ga98DpD9/CbS9JaqjMyhyr/YAYYq1Eia09/p8oBlSFR897LE2wLKRxLcK/RIpIre vbvaXVZ0domTfqr+TVeOHdhdur4VV/1FUoJu3ZUV8STg4O1wQ37nko7ecKh8NvGm RF/C4GykCUvgrhH2qFdUoJ0QgQscn3Ba6pQ/L627BKCBOYC4Snjls+WjGuBy6T4E LI6BOE4VnQ1rceZgOC55RJESoyTdyjCl1mH+F4rteGWf2NSAkHq/czpag2cRAD/c udfJdAKlr5JIjUq+HHievv4TDhzZE3bu8sS6d3UI6XvmXbLfuflCHfrARuO/lhml kPbwtqz9PFmTX3SVvCnid9DKnkIg8kCjNU4uN7NPl/oW/quw2dRJQAvSZE3yOPLh g7YpxVHWRrlCHxsWCVJ4tVvBItP3WZbe98bP0zL5NzV0+OF8SBtG97bNLXju8zLM 0SlFCSSWSCpJyjWF46ZUHcXXFAk7deYuJNO73rD6grbf/x8Q6ChmjXG+3/7GNwUE Yf653WnIVfI9X9ypg1EqRjf2eLZ6mCydrZb6rJpF0CD8npsbUN28NxUcIrKbQnYj 6M2tf+OOFto= =Pxde -END PGP SIGNATURE End Message ---
Bug#917378: python3-recommonmark: trying to overwrite '/usr/share/man/man1/cm2html.1.gz', which is also in package python-recommonmark 0.4.0+ds-2
Package: python3-recommonmark Version: 0.4.0+ds-3 Severity: serious Hi, trying to upgrade python3-recommonmark (and friends) fails for me as follows: Preparing to unpack .../python3-recommonmark_0.4.0+ds-3_all.deb ... Unpacking python3-recommonmark (0.4.0+ds-3) over (0.4.0+ds-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-recommonmark_0.4.0+ds-3_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/cm2html.1.gz', which is also in package python-recommonmark 0.4.0+ds-2 Seems as if that file (and possibly further files) moved from python-recommonmark to python3-recommonmark without specifying it with the required Breaks and Replaces header. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-recommonmark depends on: ii python3 3.7.1-3 ii python3-commonmark-bkrs 0.5.4+ds-2 ii python3-docutils 0.14+dfsg-3 ii python3-pkg-resources40.6.2-1 python3-recommonmark recommends no packages. python3-recommonmark suggests no packages. -- no debconf information
Bug#916527: marked as done (galpy: Please remove Python 2 package)
Your message dated Wed, 26 Dec 2018 21:19:39 + with message-id and subject line Bug#916527: fixed in galpy 1.4.0-2 has caused the Debian Bug report #916527, regarding galpy: Please remove Python 2 package 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.) -- 916527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: galpy Version: 1.4.0-1 Severity: serious Hi, as discussed in the Debian Astro mailing list [1], the Python 2 "python-astropy" package will be dropped, which requires that its reverse dependencies are removed before. This affects this package, since its Python-2 binary package recommends astropy. Could I ask you to remove it? Thanks Ole [1] https://lists.debian.org/debian-astro/2018/11/msg00016.html --- End Message --- --- Begin Message --- Source: galpy Source-Version: 1.4.0-2 We believe that the bug you reported is fixed in the latest version of galpy, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated galpy 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, 26 Dec 2018 14:27:59 -0600 Source: galpy Binary: python3-galpy Architecture: source amd64 Version: 1.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Josue Ortega Description: python3-galpy - Python 3 package for Galactic Dynamics Closes: 916527 Changes: galpy (1.4.0-2) unstable; urgency=medium . * Remove Python 2 package. (Closes: #916527) * Bump Standards Version to 4.3.0, no changes required. Checksums-Sha1: 647b95d13cc5b9c648dbd9e27fd9526db1833d98 2154 galpy_1.4.0-2.dsc 45e04eb674bacddb87dbb3eba0f7d6c29e8ff87d 2916 galpy_1.4.0-2.debian.tar.xz b1c43f80dc2d302c341f077226b3f9615b52a90a 7328 galpy_1.4.0-2_amd64.buildinfo 6807902473c8da0a4753fa16c590a6d0f58cebbc 595112 python3-galpy-dbgsym_1.4.0-2_amd64.deb 064dab206bc3d9e3105fa278686d2fb9f6f1479f 396708 python3-galpy_1.4.0-2_amd64.deb Checksums-Sha256: 76879fe0e10a247cb0ffe8b7289938f97941fd48354a350072c2231627b43ec7 2154 galpy_1.4.0-2.dsc b35dcf69ffccafd441629bdeccf55a3af87353eba9702e1e5bdd473cd362eb7a 2916 galpy_1.4.0-2.debian.tar.xz 54ebdca768945b5b597e45483ca574055c277182639d0d80c88b7a4dadd215bd 7328 galpy_1.4.0-2_amd64.buildinfo ec9c7b274735075a02a2b431d0248d4e5cdd9593d9fdd794eeb1d360c7be 595112 python3-galpy-dbgsym_1.4.0-2_amd64.deb 0a5b5e474bb84c3624b688fa470edc317417c66103e41a257d5078c2611321b7 396708 python3-galpy_1.4.0-2_amd64.deb Files: 95d2bf1405d3e3c24341e81406f9c27b 2154 python optional galpy_1.4.0-2.dsc e5f486d2af751bd45a907c2108942d76 2916 python optional galpy_1.4.0-2.debian.tar.xz 73eb901ac8fb6cbfb0370456ab221bd1 7328 python optional galpy_1.4.0-2_amd64.buildinfo 2b3cebae300eeacc5bfbc341b3300668 595112 debug optional python3-galpy-dbgsym_1.4.0-2_amd64.deb 835d67f8ab0422caf981f10ee9da3fe1 396708 python optional python3-galpy_1.4.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlwj50IRHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+QLg//Xy7dJxSHRoLFs7oE/60ClVbwypAQyFww oZsxwRL1a6IYPZe7lWdqMpIDNxlunNcn20oPTyg3/A8LHkMV9q5GCoxBTMIwjLeW OWWK/2smKlvyAicFZMCN94ElHKcKQCiEkGWEjcdZodJU5wAEyldeuJYvITE0keS7 8oUPqwUQiHMSFuzc041OByUYNslXnUzhXjBcaWi5Yf8+GUI0k0EboxaH9dFqp/Du KDk57sGKNP/6Ys0SsuGF4V7Hj9yvumLf3l4QmWuNOFHmQwzw3hPHBr3X1XhTchkc ieFq4ex0XmutisTXESfp18K/DSwtClPGjS+dATWUw3m6vlPtjqhW9IBHJ+qXmhhQ ucWj4K6oPHQPedEeyKFos+uksSfgcsLDEodvmrVJbxFfa3yQSUU5Um836OdLH74C ckM3SONEuNE93KmW9TtU+5GicHB3UsoYmLlnltcoxveGWQvL8t11Ynyp0OClOs1n FmyXV952hxi2U6hdRnj/C8L8y1o6las8JzZ8ZrYVlTXfoYFdOBF/LLZapFZiAHbj vC8FpJSfrsvDEWtYYAC2rY1Up/Uq0Hxwu61DtI27znPd4ee6MEZ6rd6udxf0gHYx ks/vM2WFBuF5FNdyKOmi0jRaVwLU6FHpWM+b9HNPheeRSHY+WxzeHdD1reABqdGz nGSvyMExp54= =/WiP -END PGP SIGNATURE End Message ---
Bug#916522: marked as done (pyavm: Please remove Python 2 package)
Your message dated Wed, 26 Dec 2018 21:19:57 + with message-id and subject line Bug#916522: fixed in pyavm 0.9.4-4 has caused the Debian Bug report #916522, regarding pyavm: Please remove Python 2 package 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.) -- 916522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyavm Version: 0.9.4-3 Severity: serious Hi, as discussed in the Debian Astro mailing list [1], the Python 2 "python-astropy" package will be dropped, which requires that its reverse dependencies are removed before. This affects this package, since its Python-2 binary package depends from astropy. Could I ask you to remove it? Thanks Ole [1] https://lists.debian.org/debian-astro/2018/11/msg00016.html --- End Message --- --- Begin Message --- Source: pyavm Source-Version: 0.9.4-4 We believe that the bug you reported is fixed in the latest version of pyavm, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated pyavm 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, 26 Dec 2018 14:44:33 -0600 Source: pyavm Binary: python3-pyavm Architecture: source all Version: 0.9.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Josue Ortega Description: python3-pyavm - Python3 module to handle Astronomy Visualization Metadata Standar Closes: 916522 Changes: pyavm (0.9.4-4) unstable; urgency=medium . * Remove Python 2 package. (Closes: #916522): - Remove debian/patches/*, no longer needed. * Bump Standards Version to 4.3.0, no changes were required. Checksums-Sha1: 1e1d1908cda6c16dcabf2621421048d8f9dba913 2112 pyavm_0.9.4-4.dsc 36e9ef6b9badcccb54d59d103056277317b6763c 3408 pyavm_0.9.4-4.debian.tar.xz 346cd305e11701df9ac21052fcf033ff8d01b937 7443 pyavm_0.9.4-4_amd64.buildinfo fec5ccf66ff99debf3adccde36277a4a5b2dcd7a 196280 python3-pyavm_0.9.4-4_all.deb Checksums-Sha256: c9b28e1309ee41923b335db93e2d8c1925beef3e36e57530e89afafc5afb6f93 2112 pyavm_0.9.4-4.dsc 67095eef3e9828f726d36e03fdba78f9b4dd4efd9583be6c4361260bae2ee9c8 3408 pyavm_0.9.4-4.debian.tar.xz 9d463aadffe96d9f5bd8fd58c398fc60b2d09a8edcd9a20cbdfca2491bbfa47d 7443 pyavm_0.9.4-4_amd64.buildinfo 0a501b8ef3d4e36216cd0c834a97aa23206786c10af096a770054dbfc286a823 196280 python3-pyavm_0.9.4-4_all.deb Files: 3e68972b208844f0594f05a5e64a449c 2112 python optional pyavm_0.9.4-4.dsc 7a60f195cd62b5884123fa60e7237d76 3408 python optional pyavm_0.9.4-4.debian.tar.xz 5b0e5f3f54bbfd6df7b670580a6589f2 7443 python optional pyavm_0.9.4-4_amd64.buildinfo 6984c226550d22e471a7a3f40fb27e3f 196280 python optional python3-pyavm_0.9.4-4_all.deb -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlwj6pcRHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+aGxAAlj1X/v6/KBlF0Z7hyekeN2xWe3rue4JL 6/oGKOiDrZkvmn58bDYcvXwzOl50OIsN3ucU35T1IohfJLPRzeDT35GfxxJo5e1P Si1wkibxnQguyfu5Vl64A2fCq60Nr67nkTghWaWSWbzviG4Cx11s4LSk5T6hvJrV mjALzc5Egz57t7xoAO2WjuRvB2lnaNPf58GjSE86y95dp/1YYTsf+L9BLlns4Xzt Qsc9Qrjx5cvLIzuaHu+76dNspDsPOKZttfXlpeOGR42AIwsUOb+nxQImRtfbT1cD VToQt4ooxYvRF7Y2llbZ+jFixbzEF0rXmpegx3/iBOhNNmpkP5JxzWOU/7hNjROm JyIBpR5iycIDMt17Wpj3e8uLVdKvFq0ie4aT8zgZiBax7TFX2Lng09hltbK8cTzW YVMeTHIjGvsrLuxVv7bqfIV8r9VbsP01YLsgm4FzEAg395lM4Lq7WlDngNPJZ6FQ As89bIQ0DLr12rO/1pn+neylosnVnKiWAlOrsEEBCd7sQ/2Qk9qUceFr5RXpfiCU W8jzKvwaqlOvZ9ivVUP+XXSrCpV2sfjEHvpWKDCK7CdA7enrEhEwazPfIV4rGHjZ 17en+u2Dkq1gQMx0aLgcn8dRHSHBnUhMIZBRdH2h4IqCY8hOyXYMG0pV1geeyzo4 s4cYJs9wqEA= =0QqL -END PGP SIGNATURE End Message ---
Bug#915589: marked as done (Not compatible with recent haskell-aeson)
Your message dated Wed, 26 Dec 2018 20:55:43 + with message-id <87tvj0ypm8@zephyr.silentflame.com> and subject line Re: Not compatible with recent haskell-aeson has caused the Debian Bug report #915589, regarding Not compatible with recent haskell-aeson 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.) -- 915589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debug-me Version: 1.20170810-2 Severity: serious Tags: ftbfs Control: forwarded -1 https://debug-me.branchable.com/bugs/fails_to_build_against_current_LTS_Haskell/ Current debug-me requires haskell-aeson older than 1.3. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 1.20181208-1 Hello, On Tue 04 Dec 2018 at 09:44pm -0700, Sean Whitton wrote: > Source: debug-me > Version: 1.20170810-2 > Severity: serious > Tags: ftbfs > Control: forwarded -1 > https://debug-me.branchable.com/bugs/fails_to_build_against_current_LTS_Haskell/ > > Current debug-me requires haskell-aeson older than 1.3. Fixed in the latest upstream release. -- Sean Whitton signature.asc Description: PGP signature --- End Message ---
Bug#916324: i3pystatus: Incomplete debian/copyright?
Hi Esteban, > This bug was already fixed, but I have a question. How do you find the Just good ol' GNU grep. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#916948: marked as done (fonts-hack FTBFS: Unable to execute ttfautohint on the Hack-Regular variant set)
Your message dated Wed, 26 Dec 2018 20:43:18 + with message-id and subject line Bug#916948: fixed in fonts-hack 3.003-2 has caused the Debian Bug report #916948, regarding fonts-hack FTBFS: Unable to execute ttfautohint on the Hack-Regular variant set 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.) -- 916948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-hack Version: 3.003-1 Severity: serious Tags: ftbfs Some recent change in unstable makes fonts-hack FTBFS: https://tests.reproducible-builds.org/debian/history/fonts-hack.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-hack.html ... Attempting ttfautohint hinting... Warning: Option `-w G' is deprecated! Use option `-a qsq' instead postbuild_processing/tt-hinting/Hack-Regular-TA.txt:3:1: invalid glyph name (0x204) uni0023 touch 0,1,2,3,18,19,20,21,22,23,24,25,26,27,28,31 x 0.25 @ 13 ^ Unable to execute ttfautohint on the Hack-Regular variant set. Build canceled. make[2]: *** [Makefile:26: ttf] Error 1 --- End Message --- --- Begin Message --- Source: fonts-hack Source-Version: 3.003-2 We believe that the bug you reported is fixed in the latest version of fonts-hack, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath (supplier of updated fonts-hack 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, 25 Dec 2018 12:04:38 +0100 Source: fonts-hack Binary: fonts-hack fonts-hack-ttf fonts-hack-web fonts-hack-otf Architecture: source all Version: 3.003-2 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Fabian Greffrath Description: fonts-hack - Typeface designed for source code fonts-hack-otf - Hack OpenType fonts (transitional package for fonts-hack) fonts-hack-ttf - Hack TrueType fonts (transitional package for fonts-hack) fonts-hack-web - Hack web fonts (transitional package for fonts-hack) Closes: 916948 Changes: fonts-hack (3.003-2) unstable; urgency=medium . [ Paride Legovini ] * d/rules: disable parallel building in a better way . [ Gürkan Myczko ] * Add new file * Update fonts-hack.install . [ Fabian Greffrath ] * Use proper glyphs names in the ttfautohint rules (Closes: #916948). Checksums-Sha1: bb9d623ff3e8059a63eeb5c67264652069b0f80a 2229 fonts-hack_3.003-2.dsc bf326637e10cd7ed0731da7d6bd28e4bfcbbe2c1 6528 fonts-hack_3.003-2.debian.tar.xz d9d9041ef6d4ff9c22a4b96c0a38d2196d227dea 14436 fonts-hack-otf_3.003-2_all.deb c53cdead394a348f81b511ec354c2346c5db33e7 14420 fonts-hack-ttf_3.003-2_all.deb c849bd34a4269aaa833042b0657abda1fadb6b7b 14412 fonts-hack-web_3.003-2_all.deb 8e944f15d664a0f95b956f3675575fb1bdd54777 1630420 fonts-hack_3.003-2_all.deb fa91df4d78200332d248cd8ffa491d2cc0d56519 14132 fonts-hack_3.003-2_amd64.buildinfo Checksums-Sha256: ab888a4adf7d97c1c0c3b1412024b18efb37b80760065436df2f8b3da53b0517 2229 fonts-hack_3.003-2.dsc 7b1fe7764839eaaa2e5f3f614c17f108d0cb91c11a44603c90cf93f22fc9ae4f 6528 fonts-hack_3.003-2.debian.tar.xz d7170fffe6245013cb9b938239829bb3892f39d3ab7e0b22882274be03bd4d42 14436 fonts-hack-otf_3.003-2_all.deb 1a4daf5230c44f0b3a4794d5123c0314b7481627477ef8ee28195d6ffea77ed6 14420 fonts-hack-ttf_3.003-2_all.deb c403c8114717fd3db200324276746d17a971171cd2f330f3d17e896efad52331 14412 fonts-hack-web_3.003-2_all.deb eb6b74d6cf8ab6bbab1bc77ad0ae7708a398df2970d4f9c88aa8068e72540b3f 1630420 fonts-hack_3.003-2_all.deb d00fb13b2c0f2c2b73bf765e1cd524c9067902827f6edd57a3a28015b92ea145 14132 fonts-hack_3.003-2_amd64.buildinfo Files: abdc610f51db4ea951873d03d2b57d0b 2229 fonts optional fonts-hack_3.003-2.dsc e3d4ae5740d282f52f7d977d0736d934 6528 fonts optional fonts-hack_3.003-2.debian.tar.xz 7b38838915a4dd3f464b675bea89784b 14436 oldlibs optional fonts-hack-otf_3.003-2_all.deb a0c680889d7f351ca1bdd72fb6fc7692 14420 oldlibs optional fonts-hack-ttf_3.003-2_all.deb ede320c4761ccdfe8887b06fa02a28c2 14412 oldlibs optional
Bug#916525: marked as done (glueviz: Please remove Python 2 package)
Your message dated Wed, 26 Dec 2018 20:43:34 + with message-id and subject line Bug#916525: fixed in glueviz 0.14.1+dfsg-1 has caused the Debian Bug report #916525, regarding glueviz: Please remove Python 2 package 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.) -- 916525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glueviz Version: 0.13.3+dfsg-1 Severity: serious Hi, as discussed in the Debian Astro mailing list [1], the Python 2 "python-astropy" package will be dropped, which requires that its reverse dependencies are removed before. This affects this package, since its Python-2 binary package depends from astropy. Could I ask you to remove it? Thanks Ole [1] https://lists.debian.org/debian-astro/2018/11/msg00016.html --- End Message --- --- Begin Message --- Source: glueviz Source-Version: 0.14.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of glueviz, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated glueviz 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, 26 Dec 2018 13:19:11 -0600 Source: glueviz Binary: python3-glue glueviz Architecture: source all Version: 0.14.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Josue Ortega Description: glueviz- Linked data visualization python3-glue - Python 3 library for data interaction Closes: 916525 Changes: glueviz (0.14.1+dfsg-1) unstable; urgency=medium . * New upstream release (0.14.1+dfsg-1): - Refresh debian/patches. - debian/glue: bumps entrypoint version. * Remove Python 2 Package (Closes: #916525): - debian/patches: Remove 00-generates-binary-python3-only.patch. - debian/rules: Remove python2 build option. - debian/control: Remove python-glue package. * Bump Standards-Version to 4.3.0, no changes were required. * Add CI tests. * Add patch to avoid of PNG files under /usr/lib/python. Checksums-Sha1: b4c699c4bf3eae32459c7e98d11c4757fbe61384 2587 glueviz_0.14.1+dfsg-1.dsc ee05eee25f71a5e0b72927f89ffd474e76b7baf0 22591327 glueviz_0.14.1+dfsg.orig.tar.gz fe73030febd251de4c4e42ecefd4fe39f6c9a09e 13892 glueviz_0.14.1+dfsg-1.debian.tar.xz cc6593bcdc1bc7ec8daa74f4d1dbddf536f2b22f 331696 glueviz_0.14.1+dfsg-1_all.deb 7f7c9734c0d231655eb88c7e8e449c24eff1df9e 13766 glueviz_0.14.1+dfsg-1_amd64.buildinfo b493debab4d09ebe70ff09d654faa07e3881e6bc 425440 python3-glue_0.14.1+dfsg-1_all.deb Checksums-Sha256: 81f4573afe4d14cc15fd00e9a7db053cb0910d084a66b75dab4bb2a61f172c5f 2587 glueviz_0.14.1+dfsg-1.dsc 1f6601c419cd5b65e8c5ac47041df23f21dca442965a3a2ca8b53920c665955d 22591327 glueviz_0.14.1+dfsg.orig.tar.gz 2d236c84cee3612d62e86bf304c98a3004bbe9186f96c61449b8ef801cb3c77a 13892 glueviz_0.14.1+dfsg-1.debian.tar.xz 5f087341043564202793a82e81b9f02b9c36aa229612ee35946dda18ec4f1ad8 331696 glueviz_0.14.1+dfsg-1_all.deb 900d249a9eaa31c8f0557cf44600c2f02a1c244d6495ec730e599412163784b4 13766 glueviz_0.14.1+dfsg-1_amd64.buildinfo 55dd4aee288d3a4d9bdc7ad894f2cff61460070a2205c8fd387fb20955385712 425440 python3-glue_0.14.1+dfsg-1_all.deb Files: 46d19a5fd425afbdb89facf3390635b7 2587 science optional glueviz_0.14.1+dfsg-1.dsc 2f03ec533b4d470c3f6b0a5d641efafb 22591327 science optional glueviz_0.14.1+dfsg.orig.tar.gz 148a68ea34daeafbe64c6315f5488845 13892 science optional glueviz_0.14.1+dfsg-1.debian.tar.xz cabe00a519b5d681be6ca49afa40ba42 331696 science optional glueviz_0.14.1+dfsg-1_all.deb b0d051b941b4fcce92541dbd70df7bfe 13766 science optional glueviz_0.14.1+dfsg-1_amd64.buildinfo 9fe54a49ef750fa275d2da5f962a4de2 425440 python optional python3-glue_0.14.1+dfsg-1_all.deb -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlwj2joRHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+3txAAjf3krgP8veyuyRPlSTQYSICXf2hnR4QB rskTjeHZ4XmgjQyO6HZE7MoQPGuuvn47d1Vb57wY+zr0DuGLP2F5C10MoBfMZjMF
Processed: Re: Bug#917375: wget: CVE-2018-20483
Processing control commands: > severity -1 serious Bug #917375 [src:wget] wget: CVE-2018-20483 Severity set to 'serious' from 'important' -- 917375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch
Andreas Beckmann writes:
> You most likely want to drop the .preinst and create
> emacs-nox.maintscript instead with this content (one line):
>
> < 8< debian/emacs-nox.maintscript >
> dir_to_symlink /usr/share/doc/emacs-nox emacs-common 1:25.2+1-12~
> < >8 >
>
> and do the same for -gtk and -lucid with adjusted paths.
Hmm, so we actually had that, and then intentionally switched to a
manual approach here:
https://salsa.debian.org/rlb/deb-emacs/commit/c60e9080df0d924d6a45e77725c11959926f24a7
commit c60e9080df0d924d6a45e77725c11959926f24a7
Author: Rob Browning
Date: Sun Aug 12 11:52:59 2018 -0500
Handle the emacs-{gtk,lucid,nox} doc dir transition manually
Before the unversioning, these packages were in a different source
package (emacs-defaults) and were arch all. Since
dpkg-mainscript-helper can't hande "all to any" transitions
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813455), clean up
manually in the preinsts.
Thanks to Sven Joachim for reporting the problem and indentifying the
underlying cause.
Closes: 90
Assuming I understand the situation correctly, it doesn't look like the
original issue has been resolved -- if not, then perhaps we need to
improve the manual handling instead?
Thanks for the help
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#916823: marked as done (libmeep12: missing Breaks+Replaces: libmeep8)
Your message dated Wed, 26 Dec 2018 19:22:01 + with message-id and subject line Bug#916823: fixed in meep 1.7.0-2 has caused the Debian Bug report #916823, regarding libmeep12: missing Breaks+Replaces: libmeep8 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.) -- 916823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmeep12 Version: 1.7.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libmeep12_1.7.0-1_amd64.deb ... Unpacking libmeep12 (1.7.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libmeep12_1.7.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/meep/casimir.scm', which is also in package libmeep8 1.3-4+b4 Errors were encountered while processing: /var/cache/apt/archives/libmeep12_1.7.0-1_amd64.deb cheers, Andreas libmeep8=1.3-4+b4_libmeep12=1.7.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: meep Source-Version: 1.7.0-2 We believe that the bug you reported is fixed in the latest version of meep, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated meep 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, 26 Dec 2018 19:20:24 +0100 Source: meep Binary: meep libmeep12 libmeep-dev python-meep Architecture: source amd64 Version: 1.7.0-2 Distribution: sid Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Description: libmeep-dev - development library for using meep libmeep12 - library for using meep meep - software package for FDTD simulation python-meep - software package for FDTD simulation with Python Closes: 916823 Changes: meep (1.7.0-2) unstable; urgency=medium . * upload to unstable * debian/control: add more Conflicts: (Closes: #916823) Checksums-Sha1: 6e7d1866c539765191ba147d8b3ed1c698149561 2347 meep_1.7.0-2.dsc b440a22182e04882f00578ca6bc45fc23c322d68 10182150 meep_1.7.0.orig.tar.gz c2b8a7c2dd59ffcdab55c5a1ba35f8b79d1c5d1b 141968 meep_1.7.0-2.debian.tar.xz 3411ed4686eb56b36ced96b9ba648ab81fdc85a4 330208 libmeep-dev_1.7.0-2_amd64.deb 84fc936335f692247ec3939935b70e60fe9b5572 2165484 libmeep12-dbgsym_1.7.0-2_amd64.deb 5d5d59209d8ae0d92cd7a177533083f843916358 314548 libmeep12_1.7.0-2_amd64.deb 2c6394150a62ec8903d93713b96be59bfdf26199 1254636 meep-dbgsym_1.7.0-2_amd64.deb b900411874ffcf5ba92b172cd12653cdb4d65db4 9354 meep_1.7.0-2_amd64.buildinfo 249f02a3f9c1819f40e447789608c1b6cf0936ed 213980 meep_1.7.0-2_amd64.deb 6f33641aee7feebe8fdcd88ed47b0fe9e6566c80 2592520 python-meep-dbgsym_1.7.0-2_amd64.deb 798803ef48416c91da78cc55634252437182176e 429888 python-meep_1.7.0-2_amd64.deb Checksums-Sha256: 25c397803e5a4e1704b0e220cca4aa4edab0d059b5dd1469cc37475ce6b704a8 2347 meep_1.7.0-2.dsc a5af8c28da2626a0987a6fd4aa97f4fcc5695cf17f9ee2247caa90208efaa8bf 10182150 meep_1.7.0.orig.tar.gz e9643503a557e19299cc57f9f27e092bb3a53bc1663956334e379de69c3414b1 141968 meep_1.7.0-2.debian.tar.xz 93cd00cc4fef3cb04a40d0f53d06485991a472e6266fdf220c04d3c2dd485abc 330208 libmeep-dev_1.7.0-2_amd64.deb 17e830ae07e54d2beb279e25cf022ef044370c5b6d127ac461ae2bfc14c786b0 2165484 libmeep12-dbgsym_1.7.0-2_amd64.deb 5365c55bd1d2fa69e5c44db3f32955d5b66d8f3e4e09b450afe870270a59fa6a 314548 libmeep12_1.7.0-2_amd64.deb 579869a89a38c5b11b0ee359823fea2f4710b7969fffc1101ea004910a75ff25 1254636 meep-dbgsym_1.7.0-2_amd64.deb 8b1dd8a6b552218adf676795fc4feaa6cf1f12e50d5a38458251c80f8f2635ba 9354 meep_1.7.0-2_amd64.buildinfo
Bug#889557: ovito: (Build-)Depends on obsolete libbotan1.10-dev
Hi Chris, FYI: upstream development version does not depend on libbotan anymore and with the next release this problem should disappear. Best Denis On Thu, Aug 09, 2018 at 10:59:54PM +0200, Chris Hofstaedtler wrote: > Dear ovito Maintainers, > > is there any update on progress of porting to botan2, or at least > moving off botan1.10? > > Cheers, > Chris >
Bug#917372: mnemosyne: can't start, unable to load file, query failed
Package: mnemosyne Version: 2.4-0.1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to start application, from terminal prompt. * What exactly did you do (or not do) that was effective (or ineffective)? I open the database file manually and it's a valid sqlite database, contains some tables. * What was the outcome of this action? I can't start the application. I get a message: Unable to load file, query failed. * What outcome did you expect instead? A working app. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US), LANGUAGE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages mnemosyne depends on: ii libjs-sphinxdoc 1.4.9-2 ii libqt5sql5-sqlite 5.7.1+dfsg-3+b1 ii python3 3.5.3-1 ii python3-cherrypy3 3.5.0-2 ii python3-matplotlib 2.0.0+dfsg1-2 ii python3-pyqt5 5.7+dfsg-5 ii python3-pyqt5.qtsql 5.7+dfsg-5 ii python3-pyqt5.qtwebchannel 5.7+dfsg-5 ii python3-pyqt5.qtwebengine 5.7+dfsg-5 ii python3-webob 1:1.6.2-2 mnemosyne recommends no packages. mnemosyne suggests no packages. -- no debconf information
Bug#916231: Including sys/ioctl.h helps
Hi Sergei, thanks a lot! At least it still builds here, so I just made an upload with this fix. Kind regards, Ralf On 25.12.18 12:34, Sergei Golovan wrote: > Hey Ralf, > > Including sys/ioctl.h into ossp.h doesn't help as it is included into > osspd.c too late (sys/socket.h already did harm by undefining IOC_IN > and IOC_OUT). > > But including sys/ioctl.h directly into osspd.c before sys/socket.h > works. Here is a possible patch: > > --- a/osspd.c > +++ b/osspd.c > @@ -22,6 +22,7 @@ > #include > #include > #include > +#include > #include > #include > #include > > Hopefully, it won't cause damage for other architectures. > > Cheers! >
Bug#916231: marked as done (osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared)
Your message dated Wed, 26 Dec 2018 18:34:17 +
with message-id
and subject line Bug#916231: fixed in osspd 1.3.2-10
has caused the Debian Bug report #916231,
regarding osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared
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.)
--
916231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osspd
Version: 1.3.2-9
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
While trying to cross build osspd for mips, I ran into a failure that I
could reproduce natively on minkus.d.o, but not on amd64. I suspect this
is related to glibc/2.28. A build ends with:
| gcc -Wall -pthread -g -O2 -fdebug-prefix-map=/home/helmutg/osspd-1.3.2=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse
-DSLAVE_DEFAULT_PATH=\"/usr/lib/osspd\" -o osspd osspd.c -lfuse -pthread -L.
-lossp -pthread -Wl,-z,relro
| osspd.c:41:2: warning: #warning mmap support disabled for now [-Wcpp]
| #warning mmap support disabled for now
| ^~~
| In file included from /usr/include/mips-linux-gnu/sys/soundcard.h:1,
| from osspd.c:29:
| osspd.c: In function 'mixer_do_ioctl':
| osspd.c:769:15: error: 'IOC_IN' undeclared (first use in this function); did
you mean 'SIOC_IN'?
| if (!(cmd & (SIOC_IN | SIOC_OUT)))
|^~~
| osspd.c:769:15: note: each undeclared identifier is reported only once for
each function it appears in
| osspd.c:769:25: error: 'IOC_OUT' undeclared (first use in this function); did
you mean 'SIOC_OUT'?
| if (!(cmd & (SIOC_IN | SIOC_OUT)))
| ^~~~
| osspd.c: In function 'notify_poller':
| osspd.c:1842:1: warning: no return statement in function returning non-void
[-Wreturn-type]
| }
| ^
| osspd.c: In function 'ossp_daemonize':
| osspd.c:1923:3: warning: ignoring return value of 'chdir', declared with
attribute warn_unused_result [-Wunused-result]
|chdir("/");
|^~
| At top level:
| osspd.c:1978:39: warning: 'adsp_ops' defined but not used
[-Wunused-const-variable=]
| static const struct cuse_lowlevel_ops adsp_ops = {
|^~~~
| make[2]: *** [Makefile:56: osspd] Error 1
| make[2]: Leaving directory '/home/helmutg/osspd-1.3.2'
| dh_auto_build: make V=1 -j1 SLAVESDIR=/usr/lib/osspd
UDEVDIR=/lib/udev/rules.d returned exit code 2
| make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/home/helmutg/osspd-1.3.2'
| make: *** [debian/rules:7: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
--- End Message ---
--- Begin Message ---
Source: osspd
Source-Version: 1.3.2-10
We believe that the bug you reported is fixed in the latest version of
osspd, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ralf Jung (supplier of updated osspd 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, 26 Dec 2018 19:10:03 +0100
Source: osspd
Binary: osspd osspd-pulseaudio osspd-alsa
Architecture: source amd64
Version: 1.3.2-10
Distribution: unstable
Urgency: medium
Maintainer: Ralf Jung
Changed-By: Ralf Jung
Description:
osspd - OSS Proxy Daemon: Userland OSS emulation
osspd-alsa - OSS Proxy Daemon: ALSA backend (experimental)
osspd-pulseaudio - OSS Proxy Daemon: PulseAudio backend
Closes: 916231
Changes:
osspd (1.3.2-10) unstable; urgency=medium
.
* Fix build on MIPS. (Closes: #916231)
Checksums-Sha1:
b5c643d70e11b8da17219bcd54c34cb20f059ff0 1948 osspd_1.3.2-10.dsc
7440e52a38a0259bce6656d16e15addd7673060f 7184 osspd_1.3.2-10.debian.tar.xz
948fcaaf239bdc73aa21238b2fbb814acecc89d3 31940
osspd-alsa-dbgsym_1.3.2-10_amd64.deb
8f87af010f4d78892ce95d01b13c61e433272161 12272 osspd-alsa_1.3.2-10_amd64.deb
0f39414a5cd34de27901e3d805a03351f15a9ae5 51748 osspd-dbgsym_1.3.2-10_amd64.deb
8889a66ed9ce0b4f3ac2b1e3bf6f5cd567b203a7 53416
Bug#916153: marked as done (kdeclarative FTBFS: symbol differences)
Your message dated Wed, 26 Dec 2018 18:34:03 + with message-id and subject line Bug#916153: fixed in kdeclarative 5.51.0-2 has caused the Debian Bug report #916153, regarding kdeclarative FTBFS: symbol differences 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.) -- 916153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdeclarative Version: 5.51.0-1 Severity: serious Tags: ftbfs Some recent change in unstable makes kdeclarative FTBFS: https://tests.reproducible-builds.org/debian/history/kdeclarative.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kdeclarative.html ... dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkf5declarative5/DEBIAN/symbols doesn't match completely debian/libkf5declarative5.symbols --- debian/libkf5declarative5.symbols (libkf5declarative5_5.51.0-1_amd64) +++ dpkg-gensymbolsVWAQmL 2020-01-11 00:50:03.685630585 -1200 @@ -90,7 +90,7 @@ (arch=!armel !riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.12.0 (arch=armel riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.12.0 (arch=!armel !riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.12.0 - _ZTISt19_Sp_make_shared_tag@Base 5.12.0 +#MISSING: 5.51.0-1# _ZTISt19_Sp_make_shared_tag@Base 5.12.0 (arch=armel riscv64)_ZTISt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE1EE@Base 5.12.0 (arch=!armel !riscv64)_ZTISt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE2EE@Base 5.12.0 _ZTSN12KDeclarative17ConfigPropertyMapE@Base 4.96.0 @@ -109,3 +109,4 @@ _ZTVN12KDeclarative9QmlObjectE@Base 4.96.0 (arch=armel riscv64)_ZTVSt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE1EE@Base 5.12.0 (arch=!armel !riscv64)_ZTVSt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE2EE@Base 5.12.0 + _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-1 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:7: binary] Error 2 --- End Message --- --- Begin Message --- Source: kdeclarative Source-Version: 5.51.0-2 We believe that the bug you reported is fixed in the latest version of kdeclarative, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kdeclarative 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, 26 Dec 2018 19:09:01 +0100 Source: kdeclarative Binary: kpackagelauncherqml libkf5calendarevents5 libkf5declarative-data libkf5declarative-dev libkf5declarative-doc libkf5declarative5 libkf5quickaddons5 qml-module-org-kde-draganddrop qml-module-org-kde-kcm qml-module-org-kde-kconfig qml-module-org-kde-kcoreaddons qml-module-org-kde-kio qml-module-org-kde-kquickcontrols qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-kwindowsystem Architecture: source Version: 5.51.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Description: kpackagelauncherqml - commandline tool for launching kpackage QML application libkf5calendarevents5 - provides integration of QML and KDE frameworks -- calendarevents libkf5declarative-data - provides integration of QML and KDE frameworks libkf5declarative-dev - development files for kdeclarative libkf5declarative-doc - provides integration of QML and KDE frameworks (documentation) libkf5declarative5 - provides integration of QML and KDE frameworks libkf5quickaddons5 - provides integration of QML and KDE frameworks -- quickaddons qml-module-org-kde-draganddrop - provides integration of QML and KDE frameworks - draganddrop qml-module-org-kde-kcm - provides integration of QML and KDE Frameworks - kcm
Bug#917202: marked as done (collectd should be updated for libsensors5)
Your message dated Wed, 26 Dec 2018 18:04:00 + with message-id and subject line Bug#917202: fixed in collectd 5.8.1-1.2 has caused the Debian Bug report #917202, regarding collectd should be updated for libsensors5 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.) -- 917202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lm-sensors Version: 1:3.5.0-3 Severity: normal Dear Maintainer, It does not seem possible to install both libsensors4 and libsensors5 as "apt install libsensors5" will remove libsensors4. This is apparently due to libsensors-config, which is marked as breaking and replacing libsensors4. Alas, this package does not effectively replace libsensors4 since it no longer provides libsensors.so.4. This has the side-effect of breaking collectd's "sensors" plugin, which relies on libsensors.so.4: $ dpkg -L collectd-core | grep sensors /usr/lib/collectd/sensors.so $ ldd /usr/lib/collectd/sensors.so linux-vdso.so.1 (0x7ffe949f2000) libsensors.so.4 => not found libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc8b4c44000) /lib64/ld-linux-x86-64.so.2 (0x7fc8b4e21000) Another option is to remove libsensors5.. but doing so removes lxqt (through lxqt-panel, which explicitly depends on libsensors5). Is there a significant impediment preventing libsensors4 and libsensors5 from living together on the same system? -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 lm-sensors depends on: ii libc62.28-3 ii libsensors5 1:3.5.0-3 ii lsb-base 10.2018112800 ii perl 5.28.1-3 ii sed 4.7-1 lm-sensors recommends no packages. Versions of packages lm-sensors suggests: pn fancontrol pn i2c-tools pn read-edid -- no debconf information --- End Message --- --- Begin Message --- Source: collectd Source-Version: 5.8.1-1.2 We believe that the bug you reported is fixed in the latest version of collectd, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated collectd 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, 25 Dec 2018 12:08:23 +0100 Source: collectd Binary: collectd-core collectd collectd-utils collectd-dbg collectd-dev libcollectdclient-dev libcollectdclient1 Architecture: source Version: 5.8.1-1.2 Distribution: unstable Urgency: medium Maintainer: Sebastian Harl Changed-By: Luca Boccassi Description: collectd - statistics collection and monitoring daemon collectd-core - statistics collection and monitoring daemon (core system) collectd-dbg - statistics collection and monitoring daemon (debugging symbols) collectd-dev - statistics collection and monitoring daemon (development files) collectd-utils - statistics collection and monitoring daemon (utilities) libcollectdclient-dev - client library for collectd's control interface (development file libcollectdclient1 - client library for collectd's control interface Closes: 917202 Changes: collectd (5.8.1-1.2) unstable; urgency=medium . * Non-maintainer upload. * Backport removed_checks_for_upper_limit_of_SENSORS_API.patch from the upstream 5.8 release branch to fix build with libsensors5. (Closes: #917202) Checksums-Sha1: 7d235bd460d475cacc478a39d82f0db701ee744d 3760 collectd_5.8.1-1.2.dsc 5a03311967cc42a25c57a51c102213751fc96d46 78016 collectd_5.8.1-1.2.debian.tar.xz 8819e69867c44a33bc0f49a5e0955de85cc875c4 14397 collectd_5.8.1-1.2_source.buildinfo Checksums-Sha256: 6b090b72e3e12b58e4cde091bb7599f0795f4598f7ff3ba0511786900413d48c 3760 collectd_5.8.1-1.2.dsc 1a18e72daef15f7a1fa7b68c0ee10da3cd3c28e7523bb0d301f2b5d85432ab53 78016
Processed: python-cymruwhois: please rebuild to remove dependency on Python 3.6
Processing control commands: > block 916817 by -1 Bug #916817 [release.debian.org] transition: remove python3.6 916817 was not blocked by any bugs. 916817 was not blocking any bugs. Added blocking bug(s) of 916817: 917369 -- 916817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916817 917369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917369: python-cymruwhois: please rebuild to remove dependency on Python 3.6
Package: python3-cymruwhois Version: 1.6-3 Severity: serious Control: block 916817 by -1 Dear maintainer, like last year, we are trying to remove Python 3.6 in favour of Python 3.7, so this package needs to be rebuilt to change its dependency. I notice that Ubuntu applied a patch http://launchpadlibrarian.net/396733868/python-cymruwhois_1.6-3_1.6-3ubuntu1.diff.gz which allows for an unversioned shebang which in turn causes dh_python3 to not generate a dependency on a specifc Python 3 version. I'm not sure if that patch is correct, but please consider evaluating it as it could help in future transitions. Otherwise, please try to debug why there are strictly versioned shebangs, as those are a rare sight for architecture-independent packages. -- 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#916712: marked as done (libgnutls30: Dummy bug - prevent too fast migration to testing)
Your message dated Wed, 26 Dec 2018 17:56:57 +0100
with message-id <20181226165657.ga1...@argenau.bebt.de>
and subject line Re: Bug#916712: libgnutls30: Dummy bug - prevent too fast
migration to testing
has caused the Debian Bug report #916712,
regarding libgnutls30: Dummy bug - prevent too fast migration to testing
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.)
--
916712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnutls30
Version: 3.6.5-2
Severity: serious
Justification: maintainer's opinion
gnutls 3.6.5-2 would be a candidate for testing migration tomorrow ("Too
young, only 1 of 2 days old"). This is too quick, the changes require
more testing in sid.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 2018-12-26 Niels Thykier wrote:
> On Mon, 17 Dec 2018 19:43:35 +0100 Andreas Metzler wrote:
>> Package: libgnutls30
>> Version: 3.6.5-2
>> Severity: serious
>> Justification: maintainer's opinion
>> gnutls 3.6.5-2 would be a candidate for testing migration tomorrow ("Too
>> young, only 1 of 2 days old"). This is too quick, the changes require
>> more testing in sid.
> Could you comment on how long testing time you expect here? :)
Hello Niels,
well the 10 days we have today is okay, even if it consisted of many
holidays. ;-)
Nothing new I came up, I expect we will see some breakage with TLS1.3
like msmtp's #916683, but they will only pop up when TLS 1.3 server
support is there.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'--- End Message ---
Bug#915483: marked as done (ktexteditor FTBFS: symbol differences)
Your message dated Wed, 26 Dec 2018 16:51:04 + with message-id and subject line Bug#915483: fixed in ktexteditor 5.51.0-3 has caused the Debian Bug report #915483, regarding ktexteditor FTBFS: symbol differences 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.) -- 915483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ktexteditor Version: 5.51.0-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ktexteditor.html ... dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkf5texteditor5/DEBIAN/symbols doesn't match completely debian/libkf5texteditor5.symbols --- debian/libkf5texteditor5.symbols (libkf5texteditor5_5.51.0-2_amd64) +++ dpkg-gensymbolsuZm5bx 2018-12-03 12:02:48.282692789 -1200 @@ -2601,7 +2601,7 @@ (arch=!armel)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.51.0 (arch=armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.51.0 (arch=!armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.51.0 - _ZTISt19_Sp_make_shared_tag@Base 5.50.0 +#MISSING: 5.51.0-2# _ZTISt19_Sp_make_shared_tag@Base 5.50.0 _ZTS10KateBuffer@Base 5.9.0 _ZTS11QSharedData@Base 5.9.0 _ZTS11QTextFormat@Base 5.9.0 @@ -2730,6 +2730,7 @@ _ZTVN6KateVi18EmulatedCommandBarE@Base 5.9.0 _ZTVN6KateVi8ModeBaseE@Base 5.9.0 _ZTVN6KateVi9KeyMapperE@Base 5.9.0 + _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-2 _ZZZN10KAboutDataC4ERK7QStringS2_S2_S2_N13KAboutLicense10LicenseKeyES2_S2_S2_S2_Ed_NKUlvE_clEvE15qstring_literal@Base 5.9.0 (c++)"non-virtual thunk to KTextEditor::ConfigPage::~ConfigPage()@Base" 5.9.0 (c++)"non-virtual thunk to KTextEditor::Document::~Document()@Base" 5.9.0 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:9: binary] Error 2 --- End Message --- --- Begin Message --- Source: ktexteditor Source-Version: 5.51.0-3 We believe that the bug you reported is fixed in the latest version of ktexteditor, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated ktexteditor 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, 26 Dec 2018 17:31:20 +0100 Source: ktexteditor Binary: ktexteditor-data ktexteditor-katepart libkf5texteditor-bin libkf5texteditor-dev libkf5texteditor-doc libkf5texteditor5 Architecture: source Version: 5.51.0-3 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Description: ktexteditor-data - provide advanced plain text editing services ktexteditor-katepart - provide advanced plain text editing services libkf5texteditor-bin - provide advanced plain text editing services (binaries) libkf5texteditor-dev - provide advanced plain text editing services libkf5texteditor-doc - provide advanced plain text editing services (documentation) libkf5texteditor5 - provide advanced plain text editing services Closes: 915483 Changes: ktexteditor (5.51.0-3) unstable; urgency=medium . * Team upload. * Update symbols files. (Closes: #915483) * Update lintian overrides. Checksums-Sha1: ef29df630d84ce2b20d0c66c21216871939a4a0e 3336 ktexteditor_5.51.0-3.dsc cf89bb97c2900ac3a27706f7bdcbcbcb831322cd 43064 ktexteditor_5.51.0-3.debian.tar.xz ecb3b0dd52c37078922e630498140d2036df4ccf 21458 ktexteditor_5.51.0-3_source.buildinfo Checksums-Sha256: 3affc64c22952b2c7c134d8278827cc5c612b932621f7b2a0b61a0240dcf0a1f 3336 ktexteditor_5.51.0-3.dsc 4dad282f1ea3eda256b0cff5714f1dca15167b9ee2aa2545ed5247e3e236fd07 43064 ktexteditor_5.51.0-3.debian.tar.xz b6ecf96ac74d513bde7ac597d7f6ea4394682bd26a858e0dc49fdf9ac9b29861 21458 ktexteditor_5.51.0-3_source.buildinfo Files: b06d5536d1e4e77efb37c47f5ca348d9 3336 libs
Bug#917276: mysql-defaults and MariaDB 10.3
Hi, On Tue, Dec 25, 2018 at 02:29:01PM +0200, Otto Kekäläinen wrote: > Source: mysql-defaults > Version: 1.0.5 > Severity: serious > Justification: makes the package in question unusable or mostly so > > The package has been updated to depend on Mariadb 10.3, which is > currently available only in Debian unstable. This serious bug report > is done to prevent mysql-defaults from entering Debian testing before > mariadb-10.3 has done so. The migration from unstable to testing checks (among other things) for installability, so the dependency on mariadb 10.3 will prevent mysql-defaults from migrating to testing before mariadb-10.3, even without this bug. If that is the only reason for this bug, it is unnecessary. Please note that the RC bugs and autopkgtest regressions for mariadb-10.3 and mysql-defaults (and their rdeps) will prevent the migration to testing and need to be fixed first. Cheers, Ivo
Bug#914632: uw-imap: CVE-2018-19518
> CVE-2018-19518[0]: > | University of Washington IMAP Toolkit 2007f on UNIX, as used in > | imap_open() in PHP and other products, launches an rsh command (by > | means of the imap_rimap function in c-client/imap4r1.c and the > | tcp_aopen function in osdep/unix/tcp_unix.c) without preventing > | argument injection, I'm wondering if anyone would complain if I'd disable RSH (SSH) connections altogether. -- Magnus Holmgren Debian Developer
Bug#912124: marked as done (netkit-bootparamd misses the generator for configure)
Your message dated Wed, 26 Dec 2018 15:50:49 + with message-id and subject line Bug#912124: fixed in netkit-bootparamd 0.17-10 has caused the Debian Bug report #912124, regarding netkit-bootparamd misses the generator for configure 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.) -- 912124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netkit-ntalk Version: 0.17-15 Severity: serious Justification: DFSG #2 User: helm...@debian.org Usertags: rebootstrap The configure file in the netkit-ntalk is generated using confgen from MCONFIG.in. However, the generator is missing. No package in unstable contains said confgen tool. Thus configure cannot be regenerated after fixing a bug. That's a violation of DFSG #2. Helmut --- End Message --- --- Begin Message --- Source: netkit-bootparamd Source-Version: 0.17-10 We believe that the bug you reported is fixed in the latest version of netkit-bootparamd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Gonzalez Iniesta (supplier of updated netkit-bootparamd 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: Wed, 26 Dec 2018 16:17:53 +0100 Source: netkit-bootparamd Binary: bootparamd Architecture: source amd64 Version: 0.17-10 Distribution: unstable Urgency: medium Maintainer: Alberto Gonzalez Iniesta Changed-By: Alberto Gonzalez Iniesta Description: bootparamd - Boot parameter server Closes: 912124 Changes: netkit-bootparamd (0.17-10) unstable; urgency=medium . [ Christoph Biedl ] * Move build system to cmake. (Closes: #912124) * Mayor cleanup in debian/ - Remove bogus debian/bootparams.5 - Move to compat 10 - Move to 3.0 source format . [ Alberto Gonzalez Iniesta ] * Make lintian happy: - Bumped Standards-Version to 4.3.0 - debian/control: Add misc:Depends Checksums-Sha1: 7c8c1e8861aa6ca77b3b6e7df43dc59aef2f9344 1764 netkit-bootparamd_0.17-10.dsc 7f055614d8bcd75758b3401152eeaf757c0da4fa 3688 netkit-bootparamd_0.17-10.debian.tar.xz 7cd7f3513476ab8f8a870c4a0faa2df9638fb68b 25268 bootparamd-dbgsym_0.17-10_amd64.deb 0702dcdd019f7266fcce93983b998c1169dc9ce0 13796 bootparamd_0.17-10_amd64.deb fb2b9faec269355d98e6681f01d1fae92576e634 6853 netkit-bootparamd_0.17-10_amd64.buildinfo Checksums-Sha256: aa0dda25ec3cef92d4f9d697b1d1f1d767de4303517cb68230163601e9cd8108 1764 netkit-bootparamd_0.17-10.dsc 314a85fef47b4d2a2d5eae4af1a16952eb7e643a0b913feeef8f839afd71685f 3688 netkit-bootparamd_0.17-10.debian.tar.xz 7b7496dcaae162ca2d6e0622cbada6042c074336ca0cc7959916878ae0abdeb4 25268 bootparamd-dbgsym_0.17-10_amd64.deb 56b28a096a8a225a908f3e8c1c962f6b8212d99e00d386aba2ee61c602b14934 13796 bootparamd_0.17-10_amd64.deb ed3d1cbc6ecdf2c891966384f03dd32e8976b27b77aa648297c324f119caceaf 6853 netkit-bootparamd_0.17-10_amd64.buildinfo Files: 59a135e3f6732edb25dba7c5985af508 1764 net optional netkit-bootparamd_0.17-10.dsc 318841fcbea3f2f3dfb3f53860c77b80 3688 net optional netkit-bootparamd_0.17-10.debian.tar.xz e02c05c10a29a91a9c1b14bc7ca7d63c 25268 debug optional bootparamd-dbgsym_0.17-10_amd64.deb 8fdde840506a1277ede7d091321c36da 13796 net optional bootparamd_0.17-10_amd64.deb 128a9c26e6a6454aa565b3ce9ad6cb27 6853 net optional netkit-bootparamd_0.17-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEU0fL2D4wqetNfUvyAJszdWuaqlUFAlwjnlYQHGFnaUBpbml0 dGFiLm9yZwAKCRAAmzN1a5qqVb5ID/0SliKNuYR6/tObbT2Jnd1lagmWNm+7p/pP DV1C7Hh1rzZkjUIZqbOY6XSU+adPc9/v/zrsxcTBj8nbHh4ksz+N7oZcxd8FU2Rw MGiSahGIPiYWXFTlgXqDNveu5vHNqj5DRrqOsPR4URpis1TaDBQZwITa2PH4TpYY 7Zk5cGaJJJfvNN65Jjm71eM/wdoSz1/O2QqmbXdIVIHtPcy+xhUQe+xxe2dFbOmc WyH5YzGCFvCjHofDwY0xvdBaK/31bJxLLERV0hHPzsfFM6FyU2VTn7aWgr+kvgN4 XmxdkMIRyMPOmDwdVn+7JmsPyHwiA/Bw8IQYhILP8MYq9VwV116UG55aFuFHG42A PBpmqpau9yYw/SIUxRLAnwq8oZzwpkyO/uRGFdTUKCWiAUEYroNka5i0Met09a10 Zy8J+4iKR5fXR/73GRPuiGxp4R4NN00vtBCtlvmSrC/ijt7VAqu9cc5RC7eCu82r 4Jdykttu0m7ZD5uxjht/JoRMwRNWpHovcok8M0tubg2OfWLAOCiZtq6AmINBsYkG
Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup
On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote: > On Tue, 25 Dec 2018 20:52:46 + > Ben Hutchings wrote: > > > Control: reassign -1 udev 240-1 > > Control: forcemerge 917124 -1 > > > > This seems to be a bug in udev, not the kernel. You will only have > > noticed it once you rebooted for the kernel upgrade. > > Nope - in my system's current state, when rebooting into 4.19 there's > no /dev/mapper symlink, but when rebooting into 4.18 there is. I've > gone back and forth several times, and the behavior is consistent. > There's clearly something that 4.19 is doing differently from 4.18. [I > guess it might still be a udev bug, which is being exposed by some > change in 4.19.] This is probably because the initramfs for 4.18 contains the old version of udev. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: PGP signature
Bug#916324: i3pystatus: Incomplete debian/copyright?
Hi, This bug was already fixed, but I have a question. How do you find the missing license? * *Reading in internet I founded: https://wiki.debian.org/CopyrightReviewTools I tried with that, but I can't get good results. Actually I am using https://salsa.debian.org/salsa-ci-team/pipeline and I really like to add a job that can "check for copyright". Maybe you can give me more info about this. Thanks! On 13/12/18 01:50, Chris Lamb wrote: Source: i3pystatus Version: 3.35~git20180925.a586a50-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Esteban Bosse , ftpmas...@debian.org Hi, I just ACCEPTed i3pystatus from NEW but noticed it was missing attribution in debian/copyright for at least the BSD licnese in i3pystatus/scratchpad.py. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards,
Bug#917300: marked as done (olive: Incomplete debian/copyright?)
Your message dated Wed, 26 Dec 2018 14:49:37 + with message-id and subject line Bug#917300: fixed in olive 20181223-1 has caused the Debian Bug report #917300, regarding olive: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olive Version: 20181130-1 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: Gürkan Myczko , ftpmas...@debian.org Hi, I just ACCEPTed olive from NEW but noticed it was missing attribution in debian/copyright for at least io/crc32.h. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: olive Source-Version: 20181223-1 We believe that the bug you reported is fixed in the latest version of olive, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated olive 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, 26 Dec 2018 14:41:24 +0100 Source: olive Binary: olive Architecture: source Version: 20181223-1 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Description: olive - Professional open-source NLE video editor Closes: 917300 Changes: olive (20181223-1) unstable; urgency=medium . * New upstream version. * debian/copyright: complete attribution. (Closes: #917300) Checksums-Sha1: 5e4e8d39e32aa85c189e74fb3fde85a640b8cb1a 1798 olive_20181223-1.dsc 178fddeabb40951c5bbec290e0a6e0286fe03ad5 1121905 olive_20181223.orig.tar.gz f513e8817b64e63f6e22bff095df25282e96ef52 2872 olive_20181223-1.debian.tar.xz 3ee9880817bce80092006a10473d9b1ae44b37e2 5458 olive_20181223-1_source.buildinfo Checksums-Sha256: a58ca41162a594f4d91dd989ee3f8e2a2c0e38d2f693481a05dc7298ec72f2ed 1798 olive_20181223-1.dsc c4b65afe9ed94f8f8b30b3ea5139bcda1740f04a7819d10e059a62d15b7051ee 1121905 olive_20181223.orig.tar.gz 52ffcaa79514efc16908f1882b5c7476539405b7239cde368d2e6379d9a49515 2872 olive_20181223-1.debian.tar.xz dd8d1727c9680625480d4eac445721b3572e9adb9463f835ee17d6c4dda997c5 5458 olive_20181223-1_source.buildinfo Files: dcc244209fb68f7eb2928770ea430f75 1798 video optional olive_20181223-1.dsc 0183aa23be93e3fa20b70f1233e749fa 1121905 video optional olive_20181223.orig.tar.gz c47417d707d43e2dc56b1b0e30039c17 2872 video optional olive_20181223-1.debian.tar.xz ef7d70b4dae9ccd43e0b900162e65359 5458 video optional olive_20181223-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlwjizQACgkQweDZLphv fH4TeBAAtt0em3Ln/9VYlhmU/oBSUjdpA5lRmmtgJaYwcGB8X6lqKCztQxh/Bd7m X7T3zencCEEzOa10NaBXcblOfYtstPlArHdr0xugdf4Yt2ZVQQPCdtpZonxt9suJ FSfdk97bePdJ/Zb1a1d6g1ss7EPNdGWUJ3D/zeOdq0IeWTzZ4rEPvaumgvR8Opim hwsd1C/zr3mLOSDxtLloOwsVli7BBHs+AfhTre8szDLXSFhaprt3ty0PTDiGm/YM 5CNgfrD1BRLZ6Jxx1J45FbT5GAyVEZFiAZB1/eRVhKvQMX2r53ei/ivZw607Qg+b faPtvm6ytZcLJB1o+auqS6pMj7nMZ4o8FWawMQe1gR/3Qi95yoBQ5Z7IhVM1cxiK kQTZ5aAxhx+TCaieAoSkqsO9yOmk1bRKpDEeVbrFvln7zfbo0LQ70oXEmRiD79lu rVMXKJm8uHBa2hf7CxCEF8RW7ZUrIM1Qcwof/uoVhf39tH8K2v1WR8/Hxu/FTlfW oT9JFvr5rOB0NpH7NJr+6B2CZZZCVhGV5M4IBSCbpQ5+EH4ZnYUgTFCuWkBz6nuh q2Q89ngdyD90C1QUkf2B8R6eoHSoXblJqXjDpBZ2tDHMhl3wOJ0HGwGQAlsVoQnG pQEB3W/LEbvywqIS4pewoI0NqeHISf65GHHPwQoEw7SNPX2a/HQ= =NkWK -END PGP SIGNATURE End Message ---
Bug#915429: marked as done (lsscsi FTBFS with glibc 2.28)
Your message dated Wed, 26 Dec 2018 14:49:04 + with message-id and subject line Bug#915429: fixed in lsscsi 0.30-0.1 has caused the Debian Bug report #915429, regarding lsscsi FTBFS with glibc 2.28 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.) -- 915429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lsscsi Version: 0.28-0.1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lsscsi.html ... lsscsi.c: In function 'collect_dev_nodes': lsscsi.c:973:32: warning: implicit declaration of function 'major' [-Wimplicit-function-declaration] cur_ent->maj = major(stats.st_rdev); ^ lsscsi.c:974:32: warning: implicit declaration of function 'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration] cur_ent->min = minor(stats.st_rdev); ^ mknod ... gcc -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -W -g -O2 -ffile-prefix-map=/build/1st/lsscsi-0.28=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o lsscsi lsscsi.o /usr/bin/ld: lsscsi.o: in function `collect_dev_nodes': ./src/lsscsi.c:973: undefined reference to `major' /usr/bin/ld: ./src/lsscsi.c:974: undefined reference to `minor' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:325: lsscsi] Error 1 --- End Message --- --- Begin Message --- Source: lsscsi Source-Version: 0.30-0.1 We believe that the bug you reported is fixed in the latest version of lsscsi, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated lsscsi 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, 11 Dec 2018 14:35:16 +0100 Source: lsscsi Binary: lsscsi Architecture: source Version: 0.30-0.1 Distribution: unstable Urgency: medium Maintainer: Matt Taggart Changed-By: Hilko Bengen Description: lsscsi - list all SCSI devices (or hosts) currently on system Closes: 915429 Changes: lsscsi (0.30-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream version 0.30, fixing FTBFS (Closes: #915429) * Rebase patches; drop 128-bit wwn truncation fix that has been integrated upstream Checksums-Sha1: e5b7aa7521b51bf8ba1942942a3c5d3cd60239ba 1784 lsscsi_0.30-0.1.dsc 7413c9eda75cf14e1f094a34b3e4ca05fda90fe8 190598 lsscsi_0.30.orig.tar.gz c0597e0a851edd863f1f59d6714a9f7239e66497 3376 lsscsi_0.30-0.1.debian.tar.xz 835ee3748c6919c469746a9f5975904026c132c1 5537 lsscsi_0.30-0.1_source.buildinfo Checksums-Sha256: 6cc34a5011a1aa41d5f8023db7f7476a1341b6b9b72ad9a23e79c611e596b888 1784 lsscsi_0.30-0.1.dsc 619a2187405f02c5f57682f3478bffc75326803cd08839e39d434250c5518b15 190598 lsscsi_0.30.orig.tar.gz 4722c3c029df638f32ce53e5beeffa74cde41fd0afb605baaeace49c99078aa2 3376 lsscsi_0.30-0.1.debian.tar.xz a51f79e61c6d91cb6a9714b07b7f2f394dbde6af883232c20b5fa4571f287c4c 5537 lsscsi_0.30-0.1_source.buildinfo Files: f7fd789a8782c679e81c4bc78c993225 1784 admin optional lsscsi_0.30-0.1.dsc 298a700cd50bb4be1382d618f7b038f4 190598 admin optional lsscsi_0.30.orig.tar.gz 3d03a70d049a9907f67b5868f15eafa0 3376 admin optional lsscsi_0.30-0.1.debian.tar.xz 588040bc96abd8989d8c028eb0a30aec 5537 admin optional lsscsi_0.30-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlwPwAAACgkQdbcQY1wh On4uHw/9Fp9wSgyIoCyj0/+rJdHbX3Yp5tJKnIZv06SjJlBYUbefws3i0V7v9ZOu nK0rK0eTGSiYwsnDNsLw9ibkBC8kIV81BgQE42XW+2xgvLH1OGlJy0I35iplWVBz YK1s2OajmuFXJmXsH9o7L2AWMMkK9+SNkQqwqiVR2cPBwnudak2fcomZqNScqB9F 2tP7OdI6szymGW6je4CQP7G+4eYuUjYNln7FqTXsNopt//VU62nlrJEarBmD3oYY Iw51gNqdTQNesBqvudjX8P4iiU5uOnr97FShS4AIMeJXfgK0ty0RZMITAQ3JO7ND z5GPKZspME6txwCRq3EqyoenQdOR19DOIBaisos7jit1ZFsYKI0P3Zt5HahLXTJA QvGOw9qzFDYG9nJds3pbee5XbwkzbzFUbCnT/ohaNO64NofCZQWsV04oyENdzqvT oaqYGym13wkGIe4N9UxnncF28vkLC2IAxtyV1+h5MwFtHd8PW0ryTXc2u1IkD140
Bug#916953: marked as done (logol FTBFS with swi-prolog 7.7.25+dfsg-2)
Your message dated Wed, 26 Dec 2018 14:48:55 + with message-id and subject line Bug#916953: fixed in logol 1.7.9-1 has caused the Debian Bug report #916953, regarding logol FTBFS with swi-prolog 7.7.25+dfsg-2 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.) -- 916953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: logol Version: 1.7.8-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/logol.html ... [junit] - --- [junit] Testcase: testAmbiguous(org.irisa.genouest.logol.test.GrammarTest):SKIPPED: got: , expected: is [junit] Testcase: testRepeatOverlap(org.irisa.genouest.logol.test.GrammarTest): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at org.irisa.genouest.logol.test.GrammarTest.checkResult(Unknown Source) [junit] at org.irisa.genouest.logol.test.GrammarTest.testRepeatOverlap(Unknown Source) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [junit] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] [junit] ... --- End Message --- --- Begin Message --- Source: logol Source-Version: 1.7.9-1 We believe that the bug you reported is fixed in the latest version of logol, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated logol package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 20 Dec 2018 21:02:51 +0100 Source: logol Binary: logol logol-bin Architecture: source amd64 all Version: 1.7.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: logol - Pattern matching tool using Logol language logol-bin - Pattern matching tool using Logol language Closes: 916953 Changes: logol (1.7.9-1) unstable; urgency=medium . * Team upload. * New upstream version [ Olivier Sallou ] * Fix FTBS with swi-prolog 7.7.25 (Closes: #916953). Checksums-Sha1: e8b4d139cbe844a2e6c4cf1a928d2d718570b281 2331 logol_1.7.9-1.dsc 84b5c5885e2b98545fdaf35389743dbe3e198f2a 2707918 logol_1.7.9.orig.tar.bz2 e4a42ac3c77d02985a5a9c085a607ddffae297be 12004 logol_1.7.9-1.debian.tar.xz d493979f32c346c231d20d7e8da48d57bb91a2ad 197344 logol-bin_1.7.9-1_amd64.deb e40d8b2886d926731cd6e2877287845e0913f2ce 1629376 logol_1.7.9-1_all.deb 57053dd443ef950fff5ba34cf34d4bf35ea060fd 14202 logol_1.7.9-1_amd64.buildinfo Checksums-Sha256: 193d75eb620a25d7eec7887002c8c65b79dd0da0405977af4db176ebd06bd22a 2331 logol_1.7.9-1.dsc 8dcc1c7287c7c25b6def4c3240e2038a0ce70d91fb4335b465d597364fe6e66f 2707918 logol_1.7.9.orig.tar.bz2 059a99761e0a61831e57f85e4cdfea427ab6c80b911e9abaeb74778f8894ab3e 12004 logol_1.7.9-1.debian.tar.xz b0486010ff3765d68f94b6bb2cbdb3ec72ddb677c126af038b5d0cf775fc25e7 197344 logol-bin_1.7.9-1_amd64.deb c8b81effd0472a197cbf468ec8cdb7a21b1395f1d0048aba58e95b7109114dd5 1629376 logol_1.7.9-1_all.deb bb8a984f79c5f6d957c19a4919d197c190dfa2d3d9d3ccd6c5800f30824e8b65 14202 logol_1.7.9-1_amd64.buildinfo Files: b3e8f7fbd9d0690bc21f95fbab964c73 2331 science optional logol_1.7.9-1.dsc 8ca0748a5c12b614319ad8340930cc6f 2707918 science optional logol_1.7.9.orig.tar.bz2 91bdeadcf954408c7c61bc373733c5f6 12004 science optional logol_1.7.9-1.debian.tar.xz 414a5267a20f9cda8d2c790f800069b2 197344 science optional logol-bin_1.7.9-1_amd64.deb 7d9ea864952618e3f2bc44042ec87554 1629376 science optional logol_1.7.9-1_all.deb 3dd1d404ec9d4681a49ef31f6daf84f8 14202 science optional logol_1.7.9-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEX7Rvg9O5UgRjNdJteNxo2zJthDgFAlwjj7ETHG9zYWxsb3VA ZGViaWFuLm9yZwAKCRB43GjbMm2EOCTID/9/WPq9rMXLMIae4mOpXlH8dCe4kr1R
Bug#911084: marked as done (sagemath crashes as cantor backend)
Your message dated Wed, 26 Dec 2018 13:49:04 + with message-id and subject line Bug#911084: fixed in cantor 4:18.12.0-1 has caused the Debian Bug report #911084, regarding sagemath crashes as cantor backend 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.) -- 911084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sagemath Version: 8.3-3 Severity: serious Justification: unkown as above cantor-sage-backend crashes with Segmentation fault. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=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 sagemath depends on: ii cysignals-tools 1.6.7+ds-4 ii cython 0.28.4-1 ii ecl 16.1.2-4+b1 ii eclib-tools 20171002-1+b3 ii f2c 20160102-1 ii fflas-ffpack 2.3.2-3 ii flintqs 1:1.0-3 ii gap-core 4r8p8-3 ii gfan 0.6.2-2 ii gmp-ecm 7.0.4+ds-3 ii ipython 5.5.0-1 ii iso-codes4.1-1 ii jmol 14.6.4+2016.11.05+dfsg1-3.1 ii lcalc1.23+dfsg-7 ii less 487-0.1+b1 ii libatlas3-base [liblapack.so.3] 3.10.3-7+b1 ii libblas3 [libblas.so.3] 3.8.0-1+b1 ii libbrial-groebner3 1.2.0-2 ii libbrial31.2.0-2 ii libc62.27-6 ii libcdd-tools 094h-1+b1 ii libcliquer1 1.21-2 ii libec3 20171002-1+b3 ii libecm1 7.0.4+ds-3 ii libflint-2.5.2 2.5.2-18 ii libflint-arb21:2.14.0-4 ii libgap-sage-44.8.8+3+20160327g69a66f0+dsx-1 ii libgcc1 1:8.2.0-7 ii libgd3 2.2.5-4 ii libgivaro9 4.0.4-2 ii libglpk404.65-2 ii libgmp10 2:6.1.2+dfsg-3 ii libgmpxx4ldbl2:6.1.2+dfsg-3 ii libgsl23 2.5+dfsg-5 ii libgslcblas0 2.5+dfsg-5 ii libiml0 1.0.4-1+b2 ii libjs-mathjax2.7.4+dfsg-1 ii libjs-three 80+dfsg2-2 ii liblapack3 [liblapack.so.3] 3.8.0-1+b1 ii liblfunction01.23+dfsg-7 ii liblinbox-1.5.2-01.5.2-2 ii liblinboxsage-1.5.2-01.5.2-2 ii liblrcalc1 1.2-2+b1 ii libm4ri-0.0.20140914 20140914-2+b1 ii libm4rie-0.0.2015090820150908-2 ii libmpc3 1.1.0-1 ii libmpfi0 1.5.3+ds-2 ii libmpfr6 4.0.1-1 ii libntl35 10.5.0-2 ii libopenblas-base [liblapack.so.3]0.3.3+ds-1 ii libpari-gmp-tls6 2.11.0-1 ii libplanarity03.0.0.5-3 ii libpng16-16 1.6.34-2 ii libppl14 1:1.2-3 ii libpynac18 0.7.22-3 ii libratpoints-2.1.3 1:2.1.3-1+b2 ii libreadline7 7.0-5 ii librw0 0.8+ds-1 ii libsingular4 1:4.1.1-p2+ds-2 ii libstdc++6 8.2.0-7 ii libsymmetrica2
Processed: closing 835649
Processing commands for cont...@bugs.debian.org: > close 835649 Bug #835649 [flashplugin-nonfree] [flashplugin-nonfree] OldStable (Wheezy) version of package is critically out of date Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 835649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#835649: closing 835649
close 835649 thanks
Bug#917205: marked as done (dh-fortran-mod: must not act on arch:all packages)
Your message dated Wed, 26 Dec 2018 13:19:07 + with message-id and subject line Bug#917205: fixed in dh-fortran-mod 0.8 has caused the Debian Bug report #917205, regarding dh-fortran-mod: must not act on arch:all packages 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.) -- 917205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dh-fortran-mod Version: 0.7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects: src:openmpi Hi, during a test with piuparts I noticed the postrm snippets inserted by your package cause errors. >From the attached log (scroll to the bottom...): Purging configuration files for openmpi-common (3.1.3-6) ... rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15': No such file or directory dpkg: error processing package openmpi-common (--purge): installed openmpi-common package post-removal script subprocess returned error exit status 1 This was a test on i386, openmpi-common is an arch:all package built on amd64. As an arch:all package it must not contain arch-specific stuff. Why is anything inserted into the maintainer scripts anyway if there are no fortran mods at all in the package? There could be another bug as can be seen in libopenmpi3:amd64: Purging configuration files for libopenmpi3:amd64 (3.1.3-6) ... rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15': No such file or directory dpkg: error processing package libopenmpi3:amd64 (--purge): installed libopenmpi3:amd64 package post-removal script subprocess returned error exit status 1 I don't know if this was built against dh-fortran-mod 0.6 and should be fixed by rebuilding against 0.7 ... src:openmpi will need a sourceful upload to rebuild the arch:all packages against a fixed dh-fortran-mod, again. And *PLEASE* do *source-only* uploads unless you have something that needs to go through NEW. cheers, Andreas *not amused* --- End Message --- --- Begin Message --- Source: dh-fortran-mod Source-Version: 0.8 We believe that the bug you reported is fixed in the latest version of dh-fortran-mod, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated dh-fortran-mod 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: Wed, 26 Dec 2018 12:59:35 + Source: dh-fortran-mod Binary: dh-fortran-mod Architecture: source all Version: 0.8 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Alastair McKinstry Description: dh-fortran-mod - debhelper add-on to handle Fortran '.mod' files Closes: 917205 Changes: dh-fortran-mod (0.8) unstable; urgency=medium . [ Jelmer Vernooij ] * Use secure copyright file specification URI. . [ Alastair McKinstry ] * Only add postrm/preinst scripts for packages with mod files. Closes: #917205 * Don't fail on postrm if directory already removed Checksums-Sha1: de15ebf7c451d41a1cfb61b94ef7b4c784157f36 1693 dh-fortran-mod_0.8.dsc 0d09c6f5141a7a73e6b49ec69c9e1e86639ce7b3 6440 dh-fortran-mod_0.8.tar.xz 1ef9c5cac449fff40d4458546b4f831fd7656fbc 10072 dh-fortran-mod_0.8_all.deb 97d231e61575c4a65563a0002e452c7786782a3c 5206 dh-fortran-mod_0.8_amd64.buildinfo Checksums-Sha256: 8598541c08ee8610fe85e4fe007a47b60eee03dd4eae81997e2f1d4ce5b0f69f 1693 dh-fortran-mod_0.8.dsc d7024d255b497ecf6ecce90f0286285862227238d73e1be934813704dd1c1d07 6440 dh-fortran-mod_0.8.tar.xz 59a308241922585c72c2c14ab3fc94dc748ced57b67c81ec55860a5d014f9a99 10072 dh-fortran-mod_0.8_all.deb d1042d775ff40f097975e20fb30c84b0af180c503de20d3ba1391592e4d84935 5206 dh-fortran-mod_0.8_amd64.buildinfo Files: a50e59982c1f7c5377a99e13e49717e0 1693 devel optional dh-fortran-mod_0.8.dsc 45add685d62c7a4b7fd6a2fe3fe2670e 6440 devel optional dh-fortran-mod_0.8.tar.xz bde57ddf936bb0e57419b08bf7aa8a4a 10072 devel optional dh-fortran-mod_0.8_all.deb b40a04d826ec8dcd2644b9fbce0f7ce6 5206 devel optional
Bug#917353: [python3-skimage] Cannot import skimage with new numpy
Package: python3-skimage
Version: 0.14.1-2
Severity: serious
Affects: python3-ccdproc, python3-hipspy, python3-sunpy
Tags: patch
Control: forwarded -1 https://github.com/scikit-image/scikit-image/issues/3551
$ python3
Python 3.7.2rc1 (default, Dec 12 2018, 06:25:49)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import skimage
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/skimage/__init__.py", line 167, in
from .util.dtype import (img_as_float32,
File "/usr/lib/python3/dist-packages/skimage/util/__init__.py", line 8, in
from .arraycrop import crop
File "/usr/lib/python3/dist-packages/skimage/util/arraycrop.py", line 8, in
from numpy.lib.arraypad import _validate_lengths
ImportError: cannot import name '_validate_lengths' from 'numpy.lib.arraypad'
(/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
This happens in the CI tests on a number of packages after the update of numpy
(see "Affects").
Since `_validate_lengths` is an internal identifies by Python convention, the
bug is clearly in skimage.
It is resolved in
https://github.com/scikit-image/scikit-image/pull/3556
For convenience, a patch is attached.
Cheers
Ole
From: Egor Panfilov
Date: Thu, 22 Nov 2018 22:16:02 +0200
Subject: Handle deprecation of numpy `_validate_lengths`
https://github.com/scikit-image/scikit-image/pull/3561
https://github.com/scikit-image/scikit-image/pull/3556
https://github.com/scikit-image/scikit-image/issues/3551
---
skimage/util/arraycrop.py | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/skimage/util/arraycrop.py b/skimage/util/arraycrop.py
index e83a6c6..3787770 100644
--- a/skimage/util/arraycrop.py
+++ b/skimage/util/arraycrop.py
@@ -5,8 +5,15 @@ n-dimensional array.
from __future__ import division, absolute_import, print_function
import numpy as np
-from numpy.lib.arraypad import _validate_lengths
+# After numpy 1.15, a new backward compatible function have been implemented.
+# See https://github.com/numpy/numpy/pull/11966
+from distutils.version import LooseVersion as Version
+old_numpy = Version(np.__version__) < Version('1.16')
+if old_numpy:
+from numpy.lib.arraypad import _validate_lengths
+else:
+from numpy.lib.arraypad import _as_pairs
__all__ = ['crop']
@@ -169,7 +176,10 @@ def crop(ar, crop_width, copy=False, order='K'):
view of the input array.
"""
ar = np.array(ar, copy=False)
-crops = _validate_lengths(ar, crop_width)
+if old_numpy:
+crops = _validate_lengths(ar, crop_width)
+else:
+crops = _as_pairs(crop_width, ar.ndim, as_index=True)
slices = tuple(slice(a, ar.shape[i] - b)
for i, (a, b) in enumerate(crops))
if copy:
Bug#917332: FTBFS: quick test gmsh.debug fails
On 2018-12-26 14:02, Graham Inggs wrote: Hi Drew ... It's not PETSc 3.10 because that combination has already built in Ubuntu. I suspect it is #916881. And that bug is helpfully fixed in experimental, but not in unstable... Thanks Graham. Drew
Processed: [python3-skimage] Cannot import skimage with new numpy
Processing control commands: > forwarded -1 https://github.com/scikit-image/scikit-image/issues/3551 Bug #917353 [python3-skimage] [python3-skimage] Cannot import skimage with new numpy Set Bug forwarded-to-address to 'https://github.com/scikit-image/scikit-image/issues/3551'. -- 917353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917332: FTBFS: quick test gmsh.debug fails
Hi Drew On Wed, 26 Dec 2018 at 12:06, Drew Parsons wrote: > deal.ii is unhappy about something. It fails to build against petsc > 3.10 (the current build log used petsc 3.10.2+dfsg1-2). > > PETSc 3.10 doesn't seem to be the problem directly. The build succeeds > but quick test gmsh.debug fails: It's not PETSc 3.10 because that combination has already built in Ubuntu. I suspect it is #916881. Regards Graham
Bug#917299: marked as done (centreon-broker: Incomplete debian/copyright?)
Your message dated Wed, 26 Dec 2018 12:34:09 + with message-id and subject line Bug#917299: fixed in centreon-broker 18.10.0-4 has caused the Debian Bug report #917299, regarding centreon-broker: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: centreon-broker Version: 18.10.0-3 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Sebastien Delafond , ftpmas...@debian.org Hi, I just ACCEPTed centreon-broker from NEW but noticed it was missing attribution in debian/copyright for at least Andreas Ericsson and Max Schubert. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: centreon-broker Source-Version: 18.10.0-4 We believe that the bug you reported is fixed in the latest version of centreon-broker, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond (supplier of updated centreon-broker 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, 26 Dec 2018 13:12:15 +0100 Source: centreon-broker Binary: centreon-broker Architecture: source Version: 18.10.0-4 Distribution: unstable Urgency: medium Maintainer: Freexian Packaging Team Changed-By: Sebastien Delafond Description: centreon-broker - Network, system, applicative supervision and monitoring - broker Closes: 917299 Changes: centreon-broker (18.10.0-4) unstable; urgency=medium . * Add missing attributions in d/copyright (Closes: #917299) Checksums-Sha1: ceb14cee9f6c1ffb03cfafea4b4b067df3105b54 1782 centreon-broker_18.10.0-4.dsc 416289499c0950ef9853aad63e02365811d0407e 3284 centreon-broker_18.10.0-4.debian.tar.xz 185e837862aa17e1a8d1e598e3a46329fd365507 11271 centreon-broker_18.10.0-4_amd64.buildinfo Checksums-Sha256: 56c3f86762ff930e21ab7104c4ed58e14d51f1d6da8fd025fd7f52b29478c7d6 1782 centreon-broker_18.10.0-4.dsc 818a90fe004c8f41980e967062101b81d9b1881564704f82b2d919b7a36080ac 3284 centreon-broker_18.10.0-4.debian.tar.xz b64b23caf0a54fac4e1f4e6678ad9d663dd01e49e22fad4022999f2a35659482 11271 centreon-broker_18.10.0-4_amd64.buildinfo Files: d3e3595f03c9afadde58f8f4fc7bfa4a 1782 net optional centreon-broker_18.10.0-4.dsc cda17e6976b35207a4e626c7ebac8bfb 3284 net optional centreon-broker_18.10.0-4.debian.tar.xz 785d79fd86eb191a142412660da3b962 11271 net optional centreon-broker_18.10.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAlwjcdIACgkQEL6Jg/PV nWTFkAf+Pc9XoU0Imfndd8FI6iatXQQBfm5zVsXxP6Y/m9F89SWJQXaIFWPxnSCV /V6B4Torbzxq2NY/OlxAuDWErGkRA1GGlGP3JBzUodFe6oJ6A9YMXSOvpYf0q2pO udS+Z6brQnEVDP09VBn0XKU9jhKZnvNd19g4YCVaf0/pQ4/rU8NfCafq+5s6doNd tyhf/vbxX1o6PbEmMzM6+hdI42cZ1ob8DEj1J4qwRvRXY11DIQiuUWwjc+RwTO3Z JhX9oj45gg7mzoCI3xvked2n1389Mg+iut3ThOIZNSWPgBEFupqhdGeAprcqktRA Q6sIeFn4HVFDoNSVCOLJmkiUr/11/w== =JVMj -END PGP SIGNATURE End Message ---
Processed: Re: reportbug: -N, --bugnumber options seems to not work
Processing control commands: > reassign -1 pysimplesoap Bug #917258 [reportbug] reportbug: -N, --bugnumber options seems to not work Bug reassigned from package 'reportbug' to 'pysimplesoap'. No longer marked as found in versions reportbug/7.5.1. Ignoring request to alter fixed versions of bug #917258 to the same values previously set > forcemerge 917165 917258 Bug #917165 [pysimplesoap] crash in pysimplesoap breaks bug display in reportbug Bug #917258 [pysimplesoap] reportbug: -N, --bugnumber options seems to not work Set Bug forwarded-to-address to 'https://github.com/pysimplesoap/pysimplesoap/issues/167'. Severity set to 'serious' from 'normal' Added indication that 917258 affects python-debianbts,reportbug Added tag(s) upstream. Merged 917165 917258 -- 917165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917165 917258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916152: marked as done (kactivities-stats FTBFS: symbol differences)
Your message dated Wed, 26 Dec 2018 12:19:48 +
with message-id
and subject line Bug#916152: fixed in kactivities-stats 5.51.0-2
has caused the Debian Bug report #916152,
regarding kactivities-stats FTBFS: symbol differences
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.)
--
916152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kactivities-stats
Version: 5.51.0-1
Severity: serious
Tags: ftbfs
Some recent change in unstable makes kactivities-stats FTBFS:
https://tests.reproducible-builds.org/debian/history/kactivities-stats.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kactivities-stats.html
...
dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5activitiesstats1/DEBIAN/symbols doesn't
match completely debian/libkf5activitiesstats1.symbols
--- debian/libkf5activitiesstats1.symbols
(libkf5activitiesstats1_5.51.0-1_amd64)
+++ dpkg-gensymbolsdpqfZX 2018-12-08 18:30:20.653794179 -1200
@@ -197,7 +197,7 @@
(optional=gccinternal|arch=!armel
!riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.20
(optional=gccinternal|arch=armel
riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.22.0
(optional=gccinternal|arch=!armel
!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.20
- _ZTISt19_Sp_make_shared_tag@Base 5.20
+#MISSING: 5.51.0-1# _ZTISt19_Sp_make_shared_tag@Base 5.20
(optional=templinst|arch=armel
riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base
5.22.0
(optional=templinst|arch=!armel
!riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
5.20
_ZTSN11KActivities5Stats11ResultModelE@Base 5.20
@@ -214,6 +214,7 @@
_ZTVN11KActivities5Stats13ResultWatcherE@Base 5.20
(optional=templinst|arch=armel
riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base
5.22.0
(optional=gccinternal|arch=!armel
!riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
5.20
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-1
_Zls6QDebugRKN11KActivities5Stats5QueryE@Base 5.20
_Zls6QDebugRKN11KActivities5Stats5Terms3UrlE@Base 5.20
_Zls6QDebugRKN11KActivities5Stats5Terms4TypeE@Base 5.20
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:7: binary] Error 2
--- End Message ---
--- Begin Message ---
Source: kactivities-stats
Source-Version: 5.51.0-2
We believe that the bug you reported is fixed in the latest version of
kactivities-stats, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pino Toscano (supplier of updated kactivities-stats 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, 26 Dec 2018 13:02:35 +0100
Source: kactivities-stats
Binary: libkf5activitiesstats-dev libkf5activitiesstats-doc
libkf5activitiesstats1
Architecture: source
Version: 5.51.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers
Changed-By: Pino Toscano
Description:
libkf5activitiesstats-dev - development files for kactivities-stats.
libkf5activitiesstats-doc - usage data collected by the activities system
libkf5activitiesstats1 - usage data collected by the activities system
Closes: 916152
Changes:
kactivities-stats (5.51.0-2) unstable; urgency=medium
.
* Team upload.
* Update symbols files, also from the logs of buildds. (Closes: #916152)
* Remove unused (and wrong) 'testsuite' autopkgtest.
* Remove unused ${shlibs:Depends} from libkf5activitiesstats-doc.
Checksums-Sha1:
b61945ac655cb90e288b5ad840bd704031ed90b9 2828 kactivities-stats_5.51.0-2.dsc
Processed: Re: reportbug: Crashes in soap client, fails to retrive a bugreport
Processing commands for cont...@bugs.debian.org: > retitle 917165 crash in pysimplesoap breaks bug display in reportbug Bug #917165 [pysimplesoap] reportbug: Crashes in soap client, fails to retrive a bugreport Changed Bug title to 'crash in pysimplesoap breaks bug display in reportbug' from 'reportbug: Crashes in soap client, fails to retrive a bugreport'. > forwarded 917165 https://github.com/pysimplesoap/pysimplesoap/issues/167 Bug #917165 [pysimplesoap] crash in pysimplesoap breaks bug display in reportbug Set Bug forwarded-to-address to 'https://github.com/pysimplesoap/pysimplesoap/issues/167'. > thanks Stopping processing here. Please contact me if you need assistance. -- 917165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915154: marked as done (suricata: make distclean deletes rust/vendor, preventing a second build)
Your message dated Wed, 26 Dec 2018 12:06:38 + with message-id and subject line Bug#915154: fixed in suricata 1:4.1.2-1 has caused the Debian Bug report #915154, regarding suricata: make distclean deletes rust/vendor, preventing a second build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: suricata Version: 1:4.1.0-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, suricata/experimental FTBFS twice in a row. make distclean deletes rust/vendor/ which is needed for the second build. diffing the buildlog for the first and second build yields: * cleaning after the first build fakeroot debian/rules clean dh clean --with python2 + dh_auto_clean + make V=1 -j3 distclean +make[1]: Entering directory '/build/suricata-4.1.0' +Making distclean in rust +make[2]: Entering directory '/build/suricata-4.1.0/rust' +rm -rf .libs _libs +rm -rf target +rm -f *.lo +test -z "Cargo.toml" || rm -f Cargo.toml +test . = "." || test -z "" || rm -f +rm -rf vendor gen Cargo.lock +rm -f Makefile +make[2]: Leaving directory '/build/suricata-4.1.0/rust' +Making distclean in src ... * building the source package again +dpkg-source: warning: ignoring deletion of file missing, use --include-removal to override ... +dpkg-source: warning: ignoring deletion of file Makefile.in, use --include-removal to override +dpkg-source: warning: ignoring deletion of file suricata-update/Makefile.in, use --include-removal to override +dpkg-source: warning: ignoring deletion of file suricata-update/Makefile, use --include-removal to override +dpkg-source: warning: ignoring deletion of file src/Makefile.in, use --include-removal to override +dpkg-source: warning: ignoring deletion of file rust/Makefile.in, use --include-removal to override +dpkg-source: warning: ignoring deletion of file rust/Cargo.toml, use --include-removal to override +dpkg-source: warning: ignoring deletion of file rust/Cargo.lock, use --include-removal to override +dpkg-source: warning: ignoring deletion of directory rust/vendor +dpkg-source: warning: ignoring deletion of directory rust/vendor/rusticata-macros +dpkg-source: warning: ignoring deletion of file rust/vendor/rusticata-macros/README.md, use --include-removal to override +dpkg-source: warning: ignoring deletion of file rust/vendor/rusticata-macros/LICENSE-MIT, use --include-removal to override ... * buildiARGO_HOME=/nonexistent/.cargo \ CARGO_TARGET_DIR=/build/suricata-4.1.0/rust/target \ - /usr/bin/cargo build --release --frozen \ + /usr/bin/cargo build --release \ --features "lua " - Compiling libc v0.2.43 - Compiling build_const v0.2.1 - Compiling crc v1.7.0 - Compiling memchr v1.0.2 - Compiling nom v3.2.1 - Compiling rusticata-macros v0.4.1 - Compiling ntp-parser v0.2.1 - Compiling der-parser v0.5.5 - Compiling ipsec-parser v0.3.0 - Compiling kerberos-parser v0.1.4 - Compiling suricata v4.1.0 (/build/suricata-4.1.0/rust) -Finished release [optimized + debuginfo] target(s) in 39.74s +error: failed to load source for a dependency on `crc` + +Caused by: + Unable to update registry `https://github.com/rust-lang/crates.io-index` + +Caused by: + failed to open: /nonexistent/.cargo/registry/index/github.com-1ecc6299db9ec823/.cargo-index-lock + +Caused by: + Permission denied (os error 13) +make[3]: *** [Makefile:535: all-local] Error 101 make[3]: Leaving directory '/build/suricata-4.1.0/rust' Andreas suricata_1%4.1.0-2_twice.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: suricata Source-Version: 1:4.1.2-1 We believe that the bug you reported is fixed in the latest version of suricata, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sascha Steinbiss (supplier of updated suricata 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, 23 Dec 2018
Bug#917225: closed by Sylvestre Ledru (Bug#917225: fixed in rust-exa 0.8.0-2)
On Wed, Dec 26, 2018 at 11:57:10AM +, Debian Bug Tracking System wrote: >* Silent the tests which fails without a terminal (Closes: #917225) Alternatively, you could run them via pipetty (package: colorized-logs). That tool doesn't redirect stdin, but these tests: > Failing tests: > test options::test::oneline_across ... FAILED > test options::view::test::views::empty ... FAILED > test options::view::test::views::gracross ... FAILED > test options::view::test::views::across ... FAILED > test options::view::test::views::grid ... FAILED > test options::view::test::views::just_binary ... FAILED > test options::view::test::views::just_blocks ... FAILED > test options::view::test::views::just_bytes ... FAILED > test options::view::test::views::just_git ... FAILED > test options::view::test::views::just_group ... FAILED > test options::view::test::views::just_header ... FAILED > test options::view::test::views::just_inode ... FAILED > test options::view::test::views::just_links ... FAILED > test options::view::test::views::original_g ... FAILED > test options::view::test::views::lid ... FAILED > test options::view::test::views::leg ... FAILED don't look like they care about that. In case that's a problem, a wrapper like: https://raw.githubusercontent.com/crawl/crawl/master/crawl-ref/source/util/fake_pty.c would do the trick. But then, it's you who knows whether these tests do anything that matters. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in ⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned ⠈⠳⣄ to the city of his birth to die.
Processed (with 1 error): Re: reportbug: Crashes in soap client, fails to retrive a bugreport
Processing control commands: > reassign -1 pysimplesoap Bug #917165 [reportbug] reportbug: Crashes in soap client, fails to retrive a bugreport Bug reassigned from package 'reportbug' to 'pysimplesoap'. No longer marked as found in versions reportbug/7.5.1. Ignoring request to alter fixed versions of bug #917165 to the same values previously set > severity -1 serious Bug #917165 [pysimplesoap] reportbug: Crashes in soap client, fails to retrive a bugreport Severity set to 'serious' from 'important' > affects -1 reportbug Bug #917165 [pysimplesoap] reportbug: Crashes in soap client, fails to retrive a bugreport Added indication that 917165 affects reportbug > affects -1 python-debianbts Bug #917165 [pysimplesoap] reportbug: Crashes in soap client, fails to retrive a bugreport Added indication that 917165 affects python-debianbts > tags -1 upstream Bug #917165 [pysimplesoap] reportbug: Crashes in soap client, fails to retrive a bugreport Added tag(s) upstream. > forwarded -1 Unknown command or malformed arguments to command. -- 917165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917328: marked as done ([src:node-mocha] Sourceless chai)
Your message dated Wed, 26 Dec 2018 11:53:03 + with message-id and subject line Bug#917328: fixed in node-mocha 4.1.0+ds3-1 has caused the Debian Bug report #917328, regarding [src:node-mocha] Sourceless chai 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.) -- 917328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-mocha Version: 4.1.0+ds3-1 Severity: serious chai.js is from libjs-chai and is sourceless signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: node-mocha Source-Version: 4.1.0+ds3-1 We believe that the bug you reported is fixed in the latest version of node-mocha, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated node-mocha 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, 26 Dec 2018 10:10:34 +0100 Source: node-mocha Binary: mocha libjs-mocha Architecture: source Version: 4.1.0+ds3-1 Distribution: unstable Urgency: high Maintainer: Debian Javascript Maintainers Changed-By: Bastien Roucariès Description: libjs-mocha - simple, flexible, fun test framework - JavaScript library mocha - simple, flexible, fun test framework - Node.js module Closes: 917328 Changes: node-mocha (4.1.0+ds3-1) unstable; urgency=high . * Remove sourceless chai. Link to libjs-chai (Closes: #917328) * Add missing link to map file. Checksums-Sha1: 7208fba512e3d87322901b4ec083450cb43c2ba3 3024 node-mocha_4.1.0+ds3-1.dsc 640877b1c752e870e83930b75392c041d99641ad 1122532 node-mocha_4.1.0+ds3.orig.tar.xz 571144148e655139d9da0a1f9d0cbe33ddde15a6 17848 node-mocha_4.1.0+ds3-1.debian.tar.xz ca3c00338fd15b9a906cd5d5c4199d3347d10e7a 16957 node-mocha_4.1.0+ds3-1_source.buildinfo Checksums-Sha256: e8f78740f64e6d0319a5121ee77a54ef6907ff507808cbfb0e2983ca0a75fbaf 3024 node-mocha_4.1.0+ds3-1.dsc 309765c7ea15641e8285212d7b9a926a72769a8df7f11f2708a2b7bb7b81df71 1122532 node-mocha_4.1.0+ds3.orig.tar.xz d3e433d2701f0bd7531b30a1bd1ef0a1380fddc82df0e0db9af36b9488c4b885 17848 node-mocha_4.1.0+ds3-1.debian.tar.xz 93e1c69e4aa86591cc49df5ed1841896f0ad720650d79af66bdea50f6708bc57 16957 node-mocha_4.1.0+ds3-1_source.buildinfo Files: 51643ffe4b4b98b4a86a576d1b642c15 3024 javascript optional node-mocha_4.1.0+ds3-1.dsc 8cc4f4d7d4f7687a276ba5a5a0112a33 1122532 javascript optional node-mocha_4.1.0+ds3.orig.tar.xz bbfeaf9dc402baf524314b4205fb3e19 17848 javascript optional node-mocha_4.1.0+ds3-1.debian.tar.xz 0d2986c411c14711bba918dd5858b0a7 16957 javascript optional node-mocha_4.1.0+ds3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlwjZ4AACgkQADoaLapB CF/6eA/+OE2F9446O1n/isMbv94YucJ3k1ZAh/2C9Q2FV4s98wpVTyF1akgjd+0L uPDCJyf0I5svYiyQVdRWK6tiYpIynq8LV2xBptPisE7qS8zxp/TyoWjOIy71VkPo y6e/tXn0zSCumeeJJYaBVs3TSzHpsrxgvx5V8D3pOzCjzITT9k511fPSqwrsnUro kvb4y98oxYfncua+/HPKCnDWmu4bp40Z2z62Enl7IHEJuKKyBijgz5aK7mXnddAe aH/JpK/6xTrbfULO5Si3s97lPppT8IUJ5tzIluUk/xvRUGnQzlsQYcRTFF2wGXrn uSolijk0yFnnH/DFagO15DujKBh4zVnH4EFHLRibWtvtQwsSUGlzmTL+MpDTCBkT mj7pFGzdYnt1739opqKxq6vgBQpxb4j3Q1Y/28zRXvRniNbTiL5I96NCKHZoEb6X vTF0vuDiQ/ndNPQZRGhuffs9GIl5bzLeVzy+izqxz/OiItLoUWbP2qaysJbkyrd5 M2hHS8KJCpvlUg7mYKQ+gbDB7Zn5tG7YxCVwKoo9eg4TNgfX/FtgmNHuEMDEUMUl 06sOEDY5cxz70FUsGYc/osMvKbD5UONKaBOIBDKpnXbXiGHxKybDuT0+CuoADVre aBaZhmKr/4pmgjUXXYM8ixLrAsJ3VaI4SU9yIFj20VGTNdGtQfA= =Ed2q -END PGP SIGNATURE End Message ---
Bug#917231: marked as done (emerald: Incomplete debian/copyright?)
Your message dated Wed, 26 Dec 2018 11:49:20 + with message-id and subject line Bug#917231: fixed in emerald 0.8.16-2 has caused the Debian Bug report #917231, regarding emerald: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emerald Version: 0.8.16-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Samuel Thibault , ftpmas...@debian.org Hi, I just ACCEPTed emerald from NEW but noticed it was missing attribution in debian/copyright for at least Novell. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: emerald Source-Version: 0.8.16-2 We believe that the bug you reported is fixed in the latest version of emerald, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated emerald 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, 26 Dec 2018 12:46:15 +0100 Source: emerald Binary: emerald libemeraldengine0 libemeraldengine-dev Architecture: source Version: 0.8.16-2 Distribution: unstable Urgency: medium Maintainer: Hypra Team Changed-By: Samuel Thibault Description: emerald- Decorator for compiz libemeraldengine-dev - Development files for emerald engines libemeraldengine0 - Decoration engines for compiz Closes: 917231 Changes: emerald (0.8.16-2) unstable; urgency=medium . * copyright: Fix copyright holders (Closes: Bug#917231). Checksums-Sha1: 79d033663f5054efc934e1ae5315e7248e966d88 2198 emerald_0.8.16-2.dsc c1828ad2fb4a4a6d29a552e57b815f10f4c0330d 4564 emerald_0.8.16-2.debian.tar.xz Checksums-Sha256: cc849bb304b05b6c77ecea2ba5a4f23e66c1ed019ee808f96d0c188e48f21181 2198 emerald_0.8.16-2.dsc 77c6c0cc0a42c31341ee6336c5faef3a9d48c1a8e03d42d0035e83bc9674e1c4 4564 emerald_0.8.16-2.debian.tar.xz Files: f7841d56e4d2affe2ba7a931a6193f3b 2198 x11 optional emerald_0.8.16-2.dsc b4aeb5b577ccc4245e8dcb32e876e33e 4564 x11 optional emerald_0.8.16-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOjpdRkZg6GdhDKQnmWhJwc9WBHgFAlwjancACgkQmWhJwc9W BHjc3Q//adlYti7kWH676D1cL4gjdqCkdhFumZa4MqdHG7uzfyBWzFrWMi8lvjSz xOB80SjHCrr9GSB6N4KVX7ShdPB/NVpJvfMEz+TE9yKpOsVAkqBKL87Ine4OzFIH zU5mLUGW30G7peYmEEycVDW7ZVgTh/1X0zyAzg2Dj5ctUtHKD9omZ0fykzoUfeDx uWaqWj+H+vKAyQBkNKw/hSQWER7AHgzVmKCilPRqT7BtKSGBpTb9gIqUBG28omdX nPY2gJ5lZBkbf8aab/xeiSEvTHN7omWYhR8kVPbXyVAn9Mu5BPIVTUde5DSdC+ey NyqZS032AjNtFaQuenctm2Cd+DtfxOgm1N0dBbeAy1o54oJNVujQ0ymhXpef93tW uuDiRuaZZo8ZwDhnRUCtOg/nBx8CEHI0NDOzqZBYdyrqWHDitTZ3wrhD6ctqa2BS ViL8O4TMBUJPJmJLiji8tfyh0vJ8TnU9QjrQ/h4llkrsqvAXilF7JEPZmx1Kny0H PSXZBlYiodAkdenY8WxrLay9nF2Eez7n2yCTD7+hbkaA7F3a+unZ1nJ7ehsJyHlf X7q2akAPW3adDaR5dUsklllXOJNmQkAUqQ0NqLPrIEtEhxrCre6d6TPsQax0sLc0 dk+IjjlUeTCtplt3pnbj8wDGFCcwo2QF4TmWGXcrImTqF/aZLdk= =6mjL -END PGP SIGNATURE End Message ---
Processed: tagging 917231
Processing commands for cont...@bugs.debian.org: > tags 917231 + pending Bug #917231 [src:emerald] emerald: Incomplete debian/copyright? Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 917231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916154: marked as done (kactivities-kf5 FTBFS: symbol differences)
Your message dated Wed, 26 Dec 2018 11:49:40 + with message-id and subject line Bug#916154: fixed in kactivities-kf5 5.51.0-2 has caused the Debian Bug report #916154, regarding kactivities-kf5 FTBFS: symbol differences 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.) -- 916154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kactivities-kf5 Version: 5.51.0-1 Severity: serious Tags: ftbfs Some recent change in unstable makes kactivities-kf5 FTBFS: https://tests.reproducible-builds.org/debian/history/kactivities-kf5.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kactivities-kf5.html ... dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkf5activities5/DEBIAN/symbols doesn't match completely debian/libkf5activities5.symbols --- debian/libkf5activities5.symbols (libkf5activities5_5.51.0-1_amd64) +++ dpkg-gensymbolsu32sH6 2020-01-11 00:48:10.987456520 -1200 @@ -113,9 +113,9 @@ _ZNK11KActivities8Consumer15currentActivityEv@Base 4.96.0 _ZNK11KActivities8Consumer17runningActivitiesEv@Base 5.23.0 (optional=templinst|arch=armel)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base 5.14.0 - (optional=templinst|arch=!armel !riscv64)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 5.13.0 +#MISSING: 5.51.0-1# (optional=templinst|arch=!armel !riscv64)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 5.13.0 (optional=templinst|arch=armel)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base 5.11.0 - (optional=templinst|arch=!armel !riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 4.98.0 +#MISSING: 5.51.0-1# (optional=templinst|arch=!armel !riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 4.98.0 (optional=templinst|arch=armel riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base 5.21.0 (optional=templinst|arch=armel riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base 5.21.0 (optional=templinst|arch=armel riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE14_M_get_deleterERKSt9type_info@Base 5.21.0 @@ -138,7 +138,7 @@ (arch=!armel !riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 (arch=armel riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.44.0-1 (arch=!armel !riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 - _ZTISt19_Sp_make_shared_tag@Base 5.21.0 +#MISSING: 5.51.0-1# _ZTISt19_Sp_make_shared_tag@Base 5.21.0 (arch=armel riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base 5.44.0-1 (arch=!armel !riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base 5.21.0 _ZTSN11KActivities10ControllerE@Base 4.96.0 @@ -161,3 +161,4 @@ _ZTVN11KActivities8ConsumerE@Base 4.96.0 (arch=armel riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base 5.44.0-1 (arch=!armel !riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base 5.21.0 + _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-1 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:7: binary] Error 2 --- End Message --- --- Begin Message --- Source: kactivities-kf5 Source-Version: 5.51.0-2 We believe that the bug you reported is fixed in the latest version of kactivities-kf5, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kactivities-kf5 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
Bug#917099: hoteldruid: CVE-2018-1000871, SQL injection
Hello Markus, this bug can be exploited only if you already have access to hoteldruid administrator account. Also it only affects mysql database, by default this debian package uses sqlite. Anyway a new version should be out soon. Regards, Marco Il 22/12/18 16:39, Markus Koschany ha scritto: Package: hoteldruid X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for hoteldruid. I couldn't find a bug tracker or code repository for hoteldruid but it seems you are involved in upstream development somehow. Are you aware of this issue already? CVE-2018-1000871[0]: | HotelDruid HotelDruid 2.3.0 version 2.3.0 and earlier contains a SQL | Injection vulnerability in "id_utente_mod" parameter in | gestione_utenti.php file that can result in An attacker can dump all | the database records of backend webserver. This attack appear to be | exploitable via the attack can be done by anyone via specially crafted | sql query passed to the "id_utente_mod=1" parameter. 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-1000871 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000871 Please adjust the affected versions in the BTS as needed. Regards, Markus
Processed: fw
Processing commands for cont...@bugs.debian.org: > forwarded 917225 https://github.com/ogham/exa/issues/318 Bug #917225 [src:rust-exa] rust-exa: FTBFS on all archs: testsuite fails Set Bug forwarded-to-address to 'https://github.com/ogham/exa/issues/318'. > thanks Stopping processing here. Please contact me if you need assistance. -- 917225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916617: marked as done (python-bumps: broken symlink: /usr/lib/python2.7/dist-packages/bumps/dream/_compiled.so -> ../../../../bumps/random123_compiled.so)
Your message dated Wed, 26 Dec 2018 10:43:37 + with message-id and subject line Bug#916617: fixed in python-bumps 0.7.11-2 has caused the Debian Bug report #916617, regarding python-bumps: broken symlink: /usr/lib/python2.7/dist-packages/bumps/dream/_compiled.so -> ../../../../bumps/random123_compiled.so 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.) -- 916617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-bumps Version: 0.7.11-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m8.6s ERROR: FAIL: Broken symlinks: /usr/lib/python2.7/dist-packages/bumps/dream/_compiled.so -> ../../../../bumps/random123_compiled.so (python-bumps) cheers, Andreas python-bumps_0.7.11-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-bumps Source-Version: 0.7.11-2 We believe that the bug you reported is fixed in the latest version of python-bumps, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stuart Prescott (supplier of updated python-bumps 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: Wed, 26 Dec 2018 18:35:44 +1100 Source: python-bumps Binary: python-bumps python3-bumps bumps-private-libs python-bumps-doc Architecture: source Version: 0.7.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Stuart Prescott Description: bumps-private-libs - data fitting and Bayesian uncertainty modeling for inverse proble python-bumps - data fitting and Bayesian uncertainty modeling for inverse proble python-bumps-doc - data fitting and Bayesian uncertainty modeling for inverse proble python3-bumps - data fitting and Bayesian uncertainty modeling for inverse proble Closes: 916617 917062 Changes: python-bumps (0.7.11-2) unstable; urgency=medium . * Ensure arch-dep and arch-indep parts can be built separately (Closes: #917062). * Only try to build shared object on supported architectures. * Make the python-bumps modules packages depend on the compiled libraries in bumps-private-libs where possible (Closes: #916617). * Update Standards-Version to 4.3.0 (no changes required). Checksums-Sha1: fefb6675dd044e7c97fc6ea8e58d7cad2849bdfc 2946 python-bumps_0.7.11-2.dsc 2d8cfd62fc09dd842de7cb018242a1e12f3e9093 12668 python-bumps_0.7.11-2.debian.tar.xz 7e6917248fa99754c92e6e54158b83beea78e197 11456 python-bumps_0.7.11-2_source.buildinfo Checksums-Sha256: 0ff091d514d4fc070efa2b0b7d29cb50be8f06117d5f4f3964c14c14ff63cf4e 2946 python-bumps_0.7.11-2.dsc fcd3529ed40ead4bbc0ac8a6926f90f1d47220c84d0d38f3571ee6915fbee8d7 12668 python-bumps_0.7.11-2.debian.tar.xz 073f873019a55f0cf698b8763e6c72caff8ff8fe2ad0f4d413385f63fdb7a84d 11456 python-bumps_0.7.11-2_source.buildinfo Files: b3b3c40f5e0853e22038226d0628fb2a 2946 science optional python-bumps_0.7.11-2.dsc 82c6fca16caaace65583ee24a7cbd4d4 12668 science optional python-bumps_0.7.11-2.debian.tar.xz 0774a6f742155e737a0aff4872dc10c5 11456 science optional python-bumps_0.7.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlwjVawSHHN0dWFydEBk ZWJpYW4ub3JnAAoJELvBfrsTlvL3w6AP/Ask9UCdXxJUJCLv5Vcr5zhaqx3J+zvr WfrzpUYoVjvY9jIpmvTMVAltB6I7AwIVE1NAGscwX3Xh+pq7yr69+z61g5nYw6X5 R3rfVWTECDlmBKwibYnytqytSj41qfHqRx7xD/c3OCN4ePQRKVHTBEwt6On/3AqP 1M/F+KnH2jbEwNYMaw4KbRFiVnwSqd9V//CCxwAl0moCbx17iCGIxAibJaE7fInD ++itfhYouTBLAx4A053MEpudN1Mxvc69wlB83gKTfiSb2CCVbzpQ6X/QQIU2m+R1 zw/bQu05B+uah6R//v3Qe53lMoHZU+nrhGCSid+62S0ssea9s53686jJOZf2bpKm 9CZAGv3BdlNpP7qzldV+tr9dKk4FrglASddHr/NBM4e6/4xHCwCsxpzIUdMav916 9caFRO/M5gvehPvBpgoeVOd/towgOzw8Lezzmef5yetwgbVbneJgsRPhM4QnASHq yI1BO3ZQsbzQ/FiBHpbedUsB+IDEV5ElWJenf0nszfZWldxnWGyqbnQBSB+1z2yb 6Q9iIMjh7b55cw49ds35D7WNOFRj5qyA68OmAutYJ3wKbqhaWyHvxq3UsF5u/mJI
Bug#917062: marked as done (python-bumps: binary-any FTBFS)
Your message dated Wed, 26 Dec 2018 10:43:37 +
with message-id
and subject line Bug#917062: fixed in python-bumps 0.7.11-2
has caused the Debian Bug report #917062,
regarding python-bumps: binary-any FTBFS
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.)
--
917062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bumps
Version: 0.7.11-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=python-bumps=sid
...
debian/rules override_dh_installinfo
make[1]: Entering directory '/<>'
cd build/texinfo; \
for p in *.png; do mv $p bumps-$p; done; \
sed "s/@image{/@image{bumps-/" -i bumps.texi; \
makeinfo bumps.texi
/bin/sh: 1: cd: can't cd to build/texinfo
mv: cannot stat '*.png': No such file or directory
sed: can't read bumps.texi: No such file or directory
could not open bumps.texi: No such file or directory
make[1]: *** [debian/rules:57: override_dh_installinfo] Error 1
This can be reproduced with
dpkg-buildpackage -B
--- End Message ---
--- Begin Message ---
Source: python-bumps
Source-Version: 0.7.11-2
We believe that the bug you reported is fixed in the latest version of
python-bumps, 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 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stuart Prescott (supplier of updated python-bumps 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: Wed, 26 Dec 2018 18:35:44 +1100
Source: python-bumps
Binary: python-bumps python3-bumps bumps-private-libs python-bumps-doc
Architecture: source
Version: 0.7.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Stuart Prescott
Description:
bumps-private-libs - data fitting and Bayesian uncertainty modeling for
inverse proble
python-bumps - data fitting and Bayesian uncertainty modeling for inverse
proble
python-bumps-doc - data fitting and Bayesian uncertainty modeling for inverse
proble
python3-bumps - data fitting and Bayesian uncertainty modeling for inverse
proble
Closes: 916617 917062
Changes:
python-bumps (0.7.11-2) unstable; urgency=medium
.
* Ensure arch-dep and arch-indep parts can be built separately
(Closes: #917062).
* Only try to build shared object on supported architectures.
* Make the python-bumps modules packages depend on the compiled libraries
in bumps-private-libs where possible (Closes: #916617).
* Update Standards-Version to 4.3.0 (no changes required).
Checksums-Sha1:
fefb6675dd044e7c97fc6ea8e58d7cad2849bdfc 2946 python-bumps_0.7.11-2.dsc
2d8cfd62fc09dd842de7cb018242a1e12f3e9093 12668
python-bumps_0.7.11-2.debian.tar.xz
7e6917248fa99754c92e6e54158b83beea78e197 11456
python-bumps_0.7.11-2_source.buildinfo
Checksums-Sha256:
0ff091d514d4fc070efa2b0b7d29cb50be8f06117d5f4f3964c14c14ff63cf4e 2946
python-bumps_0.7.11-2.dsc
fcd3529ed40ead4bbc0ac8a6926f90f1d47220c84d0d38f3571ee6915fbee8d7 12668
python-bumps_0.7.11-2.debian.tar.xz
073f873019a55f0cf698b8763e6c72caff8ff8fe2ad0f4d413385f63fdb7a84d 11456
python-bumps_0.7.11-2_source.buildinfo
Files:
b3b3c40f5e0853e22038226d0628fb2a 2946 science optional
python-bumps_0.7.11-2.dsc
82c6fca16caaace65583ee24a7cbd4d4 12668 science optional
python-bumps_0.7.11-2.debian.tar.xz
0774a6f742155e737a0aff4872dc10c5 11456 science optional
python-bumps_0.7.11-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCAAwFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlwjVawSHHN0dWFydEBk
ZWJpYW4ub3JnAAoJELvBfrsTlvL3w6AP/Ask9UCdXxJUJCLv5Vcr5zhaqx3J+zvr
WfrzpUYoVjvY9jIpmvTMVAltB6I7AwIVE1NAGscwX3Xh+pq7yr69+z61g5nYw6X5
R3rfVWTECDlmBKwibYnytqytSj41qfHqRx7xD/c3OCN4ePQRKVHTBEwt6On/3AqP
1M/F+KnH2jbEwNYMaw4KbRFiVnwSqd9V//CCxwAl0moCbx17iCGIxAibJaE7fInD
++itfhYouTBLAx4A053MEpudN1Mxvc69wlB83gKTfiSb2CCVbzpQ6X/QQIU2m+R1
zw/bQu05B+uah6R//v3Qe53lMoHZU+nrhGCSid+62S0ssea9s53686jJOZf2bpKm
9CZAGv3BdlNpP7qzldV+tr9dKk4FrglASddHr/NBM4e6/4xHCwCsxpzIUdMav916
9caFRO/M5gvehPvBpgoeVOd/towgOzw8Lezzmef5yetwgbVbneJgsRPhM4QnASHq
yI1BO3ZQsbzQ/FiBHpbedUsB+IDEV5ElWJenf0nszfZWldxnWGyqbnQBSB+1z2yb
Bug#916712: libgnutls30: Dummy bug - prevent too fast migration to testing
On Mon, 17 Dec 2018 19:43:35 +0100 Andreas Metzler wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: serious
> Justification: maintainer's opinion
>
> gnutls 3.6.5-2 would be a candidate for testing migration tomorrow ("Too
> young, only 1 of 2 days old"). This is too quick, the changes require
> more testing in sid.
>
> cu Andreas
>
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
Hi Andreas,
Could you comment on how long testing time you expect here? :)
Thanks,
~Niels
Bug#917332: FTBFS: quick test gmsh.debug fails
Source: deal.ii Version: 9.0.1-1 Severity: serious Justification: FTBFS deal.ii is unhappy about something. It fails to build against petsc 3.10 (the current build log used petsc 3.10.2+dfsg1-2). PETSc 3.10 doesn't seem to be the problem directly. The build succeeds but quick test gmsh.debug fails: [100%] Built target gmsh.debug /usr/bin/make -f tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/build.make tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/depend make[9]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/tests/quick_tests /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/tests/quick_tests /<>/obj-x86_64-linux-gnu/tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/DependInfo.cmake --color= Scanning dependencies of target gmsh.debug.run make[9]: Leaving directory '/<>/obj-x86_64-linux-gnu' /usr/bin/make -f tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/build.make tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/build make[9]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu/tests/quick_tests && ./gmsh.debug > gmsh.debug-OK 2>&1 || ( echo gmsh.debug:\ RUN\ failed.\ Output: && cat gmsh.debug-OK && rm gmsh.debug-OK && exit 1 ) gmsh.debug: RUN failed. Output: An error occurred in line <52> of file >/tests/quick_tests/gmsh.cc> in function int main() The violated condition was: ierr==0 Additional information: This exception -- which is used in many places in the library -- usually indicates that some condition which the author of the code thought must be satisfied at a certain point in an algorithm, is not fulfilled. An example would be that the first part of an algorithm sorts elements of an array in ascending order, and a second part of the algorithm later encounters an element that is not larger than the previous one. There is usually not very much you can do if you encounter such an exception since it indicates an error in deal.II, not in your own program. Try to come up with the smallest possible program that still demonstrates the error and contact the deal.II mailing lists with it to obtain help. Stacktrace: --- #0 ./gmsh.debug: main Aborted make[9]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[7]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu' gmsh.debug: **RUN failed*** ===OUTPUT END === Expected stage PASSED - aborting CMake Error at /<>/cmake/scripts/run_test.cmake:140 (MESSAGE): *** abort 95% tests passed, 1 tests failed out of 19 -- 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.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#896388: marked as done (python-libtiff: libtiff fails to import)
Your message dated Wed, 26 Dec 2018 10:00:12 +
with message-id
and subject line Bug#896388: fixed in pylibtiff 0.4.2-1
has caused the Debian Bug report #896388,
regarding python-libtiff: libtiff 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.)
--
896388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-libtiff
Version: 0.4.1+20160502-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-libtiff importing the module libtiff
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/libtiff/__init__.py", line 20, in
from .libtiff_ctypes import libtiff, TIFF, TIFF3D
File "/usr/lib/python2.7/dist-packages/libtiff/libtiff_ctypes.py", line 56,
in
raise ImportError('Failed to find TIFF library. Make sure that libtiff is
installed and its location is listed in PATH|LD_LIBRARY_PATH|..')
ImportError: Failed to find TIFF library. Make sure that libtiff is installed
and its location is listed in PATH|LD_LIBRARY_PATH|..
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: pylibtiff
Source-Version: 0.4.2-1
We believe that the bug you reported is fixed in the latest version of
pylibtiff, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Valentino (supplier of updated pylibtiff
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, 23 Dec 2018 20:55:59 +
Source: pylibtiff
Binary: python-libtiff python3-libtiff
Architecture: source amd64
Version: 0.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project
Changed-By: Antonio Valentino
Description:
python-libtiff - wrapper to the libtiff library to Python using ctypes
python3-libtiff - wrapper to the libtiff library to Python using ctypes
(Python 3 v
Closes: 705208 866462 896388
Changes:
pylibtiff (0.4.2-1) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/rules: Remove trailing whitespaces
* d/control: Set Vcs-* to salsa.debian.org
.
[ Antonio Valentino ]
* New upstream release.
* Standard version bumped to 4.2.1 (no change).
* d/control:
- depend on python-pil instead of python-imaging (Closes: #866462)
- add build dependency form libtiff-dev
- add dependency form libtiff5 (Closes: #896388)
- specify testsuite (autopkgtest-pkg-python)
- update maintainer and VCS fields (Closes: #705208).
The package has been adopted by the debian-gis team.
* Add upstream/metadata file.
* Switch to pybuild.
* New package for Python 3.
* Set compat to 11.
* d/patches
- drop 0003-ctypes2.patch and 0004-fix_future.patch: no longer necessary
- refresh and renumber remaining patches
* Use pytest for testing.
* Do not install examples: not provided in the source package form PyPi.
* Update watch file.
.
[ Bas Couwenberg ]
* Bump Standards-Version to 4.3.0, no changes.
* Remove unused examples file.
* Update rules file, changes:
- Group and reorder exports
- Remove disabled export
- Run dh_numpy* in dh_python* overrides
- Use $(RM) instead of rm
* Update watch file to handle common issues.
Checksums-Sha1:
218e5cb06646858a83a45d01e9d0616129163a8f 2189 pylibtiff_0.4.2-1.dsc
73cf71df858be50af7e1beb762d19970f22953af 70592 pylibtiff_0.4.2.orig.tar.xz
6bf1ece80b93d280da9ce7fed56e7cb9cdd493be 6512 pylibtiff_0.4.2-1.debian.tar.xz
389cc6ee786f5d8d3e30f08447f851d55db5746d 9396
Bug#866462: marked as done (pylibtiff: depends on obsolete python-imaging (replace with python3-pil or python-pil))
Your message dated Wed, 26 Dec 2018 10:00:12 + with message-id and subject line Bug#866462: fixed in pylibtiff 0.4.2-1 has caused the Debian Bug report #866462, regarding pylibtiff: depends on obsolete python-imaging (replace with python3-pil or python-pil) 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.) -- 866462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pylibtiff Version: 0.4.1+20160502-1 Severity: important Tags: sid buster User: d...@debian.org Usertags: imaging-pillow One or more binary packages built from this source depends on or recommends python-imaging, which is obsolete for some years now. Please build the source using the python-pil package. If your package doesn't need to be built with Python2, please consider using Python3 and depend on python3-pil. Planning to remove python-imaging for the buster release, so the severity of this issues might be raised. --- End Message --- --- Begin Message --- Source: pylibtiff Source-Version: 0.4.2-1 We believe that the bug you reported is fixed in the latest version of pylibtiff, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Valentino (supplier of updated pylibtiff 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, 23 Dec 2018 20:55:59 + Source: pylibtiff Binary: python-libtiff python3-libtiff Architecture: source amd64 Version: 0.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Antonio Valentino Description: python-libtiff - wrapper to the libtiff library to Python using ctypes python3-libtiff - wrapper to the libtiff library to Python using ctypes (Python 3 v Closes: 705208 866462 896388 Changes: pylibtiff (0.4.2-1) unstable; urgency=medium . [ Ondřej Nový ] * d/rules: Remove trailing whitespaces * d/control: Set Vcs-* to salsa.debian.org . [ Antonio Valentino ] * New upstream release. * Standard version bumped to 4.2.1 (no change). * d/control: - depend on python-pil instead of python-imaging (Closes: #866462) - add build dependency form libtiff-dev - add dependency form libtiff5 (Closes: #896388) - specify testsuite (autopkgtest-pkg-python) - update maintainer and VCS fields (Closes: #705208). The package has been adopted by the debian-gis team. * Add upstream/metadata file. * Switch to pybuild. * New package for Python 3. * Set compat to 11. * d/patches - drop 0003-ctypes2.patch and 0004-fix_future.patch: no longer necessary - refresh and renumber remaining patches * Use pytest for testing. * Do not install examples: not provided in the source package form PyPi. * Update watch file. . [ Bas Couwenberg ] * Bump Standards-Version to 4.3.0, no changes. * Remove unused examples file. * Update rules file, changes: - Group and reorder exports - Remove disabled export - Run dh_numpy* in dh_python* overrides - Use $(RM) instead of rm * Update watch file to handle common issues. Checksums-Sha1: 218e5cb06646858a83a45d01e9d0616129163a8f 2189 pylibtiff_0.4.2-1.dsc 73cf71df858be50af7e1beb762d19970f22953af 70592 pylibtiff_0.4.2.orig.tar.xz 6bf1ece80b93d280da9ce7fed56e7cb9cdd493be 6512 pylibtiff_0.4.2-1.debian.tar.xz 389cc6ee786f5d8d3e30f08447f851d55db5746d 9396 pylibtiff_0.4.2-1_amd64.buildinfo 2ecd3dadbcb47c38ff2f1104934e3e3994395ad4 38976 python-libtiff-dbgsym_0.4.2-1_amd64.deb 3d64dfc08f6efed753e6ecfb04965639334fd3fc 72692 python-libtiff_0.4.2-1_amd64.deb 64cd7ad46522f900aec4693d15d5483f70eff75b 43688 python3-libtiff-dbgsym_0.4.2-1_amd64.deb 959ef7955f1e928104996cb754aefbfa3f0a92b3 72820 python3-libtiff_0.4.2-1_amd64.deb Checksums-Sha256: c02e4b5dc651611fe6257b729e48aa2fada2d92f384f89d329d8223b6ca071ef 2189 pylibtiff_0.4.2-1.dsc 5fdb1e649cebbf93b4ff14683bd9152fc4a5c08535fcd351dd368cb6d52fede6 70592 pylibtiff_0.4.2.orig.tar.xz 00758bd5ee2b6e9c8f7821155a831979aba3fc1cc7ccd97bf7a034e639a188b9 6512
Bug#917331: nmh message include via POP3 ignores password (null pointer?)
Package: nmh Version: 1.7.1-2+deb8u1 Severity: serious No matter which password is entered, inc will always send the password string "(null)" to the server, thus failing authentication. It is easily reproducible on fresh installs: First emulate a POP3 server using socat: $ socat TCP4-LISTEN:,reuseaddr=1,bind=127.0.0.1 - Initialize nmh: /usr/bin/mh/install-mh Run the include program: /usr/bin/mh/inc -host 127.0.0.1 -user test -port While inc is running, switch to the "socat" process and enter single lines so that "socat" data looks like that: +OK POP3 service ready USER test +OK PASS (null) No matter which password was used, always "PASS (null)" is sent to server.
Bug#917330: ruby-kitchen-salt: Incomplete debian/copyright?
Source: ruby-kitchen-salt Version: 0.4.0-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Mathieu Parent , ftpmas...@debian.org Hi, I just ACCEPTed ruby-kitchen-salt from NEW but noticed it was missing attribution in debian/copyright for at least Chris Lundquist. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Bug #863675 in mariadb-10.3 marked as pending
Processing control commands: > tag -1 pending Bug #863675 [src:mariadb-10.3] libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config Ignoring request to alter tags of bug #863675 to the same tags previously set -- 863675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#863675: Bug #863675 in mariadb-10.3 marked as pending
Control: tag -1 pending Hello, Bug #863675 in mariadb-10.3 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/mariadb-team/mariadb-10.3/commit/ee5d906cd80f43d80bf20f2973bc4bed3bfc7fb3 Make libmariadb-dev breaks/replaces libmysqlclient-dev (Closes: #863675) This mimics how libmariadbclient-dev used to breaks/replaces the same libmysqlclient-dev package. These packages are not supposed to be co-installable anyway. Among others, the following files conflict: - /usr/bin/mysql_config - libmysqlservices.a - mysql.m4 Also, wrap-and-sort -a in this commit. (this message was generated automatically) -- Greetings https://bugs.debian.org/863675
Bug#917328: [src:node-mocha] Sourceless chai
Package: src:node-mocha Version: 4.1.0+ds3-1 Severity: serious chai.js is from libjs-chai and is sourceless signature.asc Description: This is a digitally signed message part.
Bug#916738: nvidia-alternative: Depends on a non-existent version of glx-alternative which breaks upgrade path.
Version 0.9.0 of glx-alternative-{nvidia,mesa} are available since a few
days. Installation of nvidia packages 410.78-2 went smooth.
--
Best Regards
Joerg Schuetter
Bug#916834: marked as done (freshplayerplugin: FTBFS on big-endian architectures: test fails)
Your message dated Wed, 26 Dec 2018 08:40:10 + with message-id and subject line Bug#916834: fixed in freshplayerplugin 0.3.9-2 has caused the Debian Bug report #916834, regarding freshplayerplugin: FTBFS on big-endian architectures: test fails 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.) -- 916834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freshplayerplugin Version: 0.3.9-1 Severity: serious Hi, On a rebuild against libicu63, your package failed to build on all supported big-endian architectures (mips and s390x): The following tests FAILED: 3 - test_ppb_char_set (Child aborted) Cheers, Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: freshplayerplugin Source-Version: 0.3.9-2 We believe that the bug you reported is fixed in the latest version of freshplayerplugin, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Danjean (supplier of updated freshplayerplugin 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: Wed, 26 Dec 2018 08:46:13 +0100 Source: freshplayerplugin Binary: browser-plugin-freshplayer-pepperflash Architecture: amd64 source Version: 0.3.9-2 Distribution: unstable Urgency: medium Maintainer: Vincent Danjean Changed-By: Vincent Danjean Closes: 916834 Description: browser-plugin-freshplayer-pepperflash - PPAPI-host NPAPI-plugin adapter for pepperflash Changes: freshplayerplugin (0.3.9-2) unstable; urgency=medium . * Fix "FTBFS on big-endian architectures: test fails" using a upstream patch (thanks Rinat Ibragimov) (Closes: #916834) Checksums-Sha1: f1f9be5855f17a555d6cf3efe7d653bda5a742d2 2382 freshplayerplugin_0.3.9-2.dsc 3c46f568fcea9e36f8ae72f59ded403bf4f9e78c 11288 freshplayerplugin_0.3.9-2.debian.tar.xz 251ff001952e0e062f79f7438b0408b743688c8b 16207 freshplayerplugin_0.3.9-2_source.buildinfo bebd167a5af6cf2e4cf2087cc3922c323efc09ca 5034624 browser-plugin-freshplayer-pepperflash-dbgsym_0.3.9-2_amd64.deb 10958a3a12b193cef67e58c31a8af3f2905c97fb 369356 browser-plugin-freshplayer-pepperflash_0.3.9-2_amd64.deb 941485a59a3ce755f573c2d2bcc7b8e718bd4799 14451 freshplayerplugin_0.3.9-2_amd64.buildinfo Checksums-Sha256: b5a7bb7c73840702482884a2ce62545f99211873a18a4982841a038f8001adb7 2382 freshplayerplugin_0.3.9-2.dsc 6e0bff3782eb293a6e72d1a74d1d8113c08f0b5c8d073f5dc6c8b7a322618c35 11288 freshplayerplugin_0.3.9-2.debian.tar.xz 28b493482e2982d93fd2067fd7248b66c5df8b9391f99a22c2a50c4f40c65bad 16207 freshplayerplugin_0.3.9-2_source.buildinfo 10acba7f2f9b2d23a3e49853df60036ce53b9f46cc3d402460770e014636a34f 5034624 browser-plugin-freshplayer-pepperflash-dbgsym_0.3.9-2_amd64.deb 77c824740e621b629fa65a55f288064ae8d60e1354350a441782c64ed56e16e2 369356 browser-plugin-freshplayer-pepperflash_0.3.9-2_amd64.deb a4b099e6a2b75d1b5bda3c3ec1cd5887714a977b67f7465c89632cbd12a2d7b0 14451 freshplayerplugin_0.3.9-2_amd64.buildinfo Files: 9407c775e748f6659107385821a10fbf 2382 contrib/web optional freshplayerplugin_0.3.9-2.dsc 03097068d882da47e9042b20cc51056d 11288 contrib/web optional freshplayerplugin_0.3.9-2.debian.tar.xz 9d4a3cba2fc5c129b1fd7fe17315ae70 16207 contrib/web optional freshplayerplugin_0.3.9-2_source.buildinfo a0ac18fac893c5fb272b96524ac13543 5034624 contrib/debug optional browser-plugin-freshplayer-pepperflash-dbgsym_0.3.9-2_amd64.deb 96ea71b030b99dc7db757e9e83cb32d1 369356 contrib/web optional browser-plugin-freshplayer-pepperflash_0.3.9-2_amd64.deb 574871e5c7cc2c53a2a7abc0985bb9a1
Processed: severity of 917222 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 917222 wishlist Bug #917222 [znc] znc: please provide a znc-plugin-$version that external plugins can depend on Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 917222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
