Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andreas Tille]

Hi,

On Fri, May 18, 2018 at 07:04:08PM -0400, A. Maitland Bottoms wrote:
> If the problem can be traced to the .pc file and pkg-config I will take blame 
> for a bug.  I am away from an appropriate computer right now, but will 
> investigate further soon.

I hacked around this by simply removing that check.  However, I would
prefer a better solution.  So while the bug is closed I would appreciate
if you would have a look.

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed: unarchiving 831529, reassign 833333 to libavcodec57, forcibly merging 831529 833333, archiving 831529

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 831529
Bug #831529 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #831768 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray stops at start a radiostream
Bug #831909 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #832581 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray crashes when try to play any radiostream
Bug #832964 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: Error in libavcodec.so.57 crashes radiotray
Unarchived Bug 831529
Unarchived Bug 831768
Unarchived Bug 831909
Unarchived Bug 832581
Unarchived Bug 832964
> reassign 83 libavcodec57
Bug #83 [amarok] [amarok] Crashes when playing any file
Bug reassigned from package 'amarok' to 'libavcodec57'.
No longer marked as found in versions amarok/2.8.0-5.
Ignoring request to alter fixed versions of bug #83 to the same values 
previously set
> forcemerge 831529 83
Bug #831529 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #831768 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray stops at start a radiostream
Bug #831909 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #832581 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray crashes when try to play any radiostream
Bug #832964 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: Error in libavcodec.so.57 crashes radiotray
Bug #83 [libavcodec57] [amarok] Crashes when playing any file
Severity set to 'grave' from 'important'
Marked Bug as done
Added indication that 83 affects totem
Marked as fixed in versions ffmpeg/7:3.1.1-4.
Marked as found in versions ffmpeg/7:3.1.1-2.
Added tag(s) confirmed, patch, and upstream.
Bug #831768 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray stops at start a radiostream
Bug #831909 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #832581 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray crashes when try to play any radiostream
Bug #832964 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: Error in libavcodec.so.57 crashes radiotray
Merged 831529 831768 831909 832581 832964 83
> archive 831529
Bug #831529 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #831768 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray stops at start a radiostream
Bug #831909 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: broken option parsing with LANGs with decimal mark different from 
.
Bug #832581 {Done: Sebastian Ramacher } [libavcodec57] 
radiotray crashes when try to play any radiostream
Bug #832964 {Done: Sebastian Ramacher } [libavcodec57] 
libavcodec57: Error in libavcodec.so.57 crashes radiotray
Bug #83 {Done: Sebastian Ramacher } [libavcodec57] 
[amarok] Crashes when playing any file
archived 831529 to archive/29 (from 831529)
archived 831768 to archive/68 (from 831529)
archived 831909 to archive/09 (from 831529)
archived 832581 to archive/81 (from 831529)
archived 832964 to archive/64 (from 831529)
archived 83 to archive/33 (from 831529)
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
831529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831529
831768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831768
831909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831909
832581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832581
832964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832964
83: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#896071: debootstrap fails to retrive Release file over https

[Hideki Yamane]

On Mon, 14 May 2018 00:48:53 +0200
Philipp Kern  wrote:
> any new about incorporating Raphael's suggestion? There's still a grave
> bug opened against debootstrap right now (on a version that is in testing).

 Sorry for late reply, revert previous fix and modified functions as
 Raphael suggested, and it works on my box. Please check it.


diff --git a/functions b/functions
index dc55faf..350f463 100644
--- a/functions
+++ b/functions
@@ -79,6 +79,18 @@ progress_next () {
 wgetprogress () {
[ ! "$VERBOSE" ] && NVSWITCH="-nv"
local ret=0
+
+   set -- -O "$dest" "$from" "$@"
+   if [ -n "$PRIVATEKEY" ]; then
+   set -- "$PRIVATEKEY" "$@"
+   fi
+   if [ -n "$CERTIFICATE" ]; then
+   set -- "$CERTIFICATE" "$@"
+   fi
+   if [ -n "$CHECKCERTIF" ]; then
+   set -- "$CHECKCERTIF" "$@"
+   fi
+
if [ "$USE_DEBIANINSTALLER_INTERACTION" ] && [ "$PROGRESS_NEXT" ]; then
wget "$@" 2>&1 >/dev/null | "$PKGDETAILS" "WGET%" 
"$PROGRESS_NOW" "$PROGRESS_NEXT" "$PROGRESS_END" >&3
ret=$?
@@ -401,20 +413,14 @@ just_get () {
# args: from dest
local from="$1"
local dest="$2"
+
mkdir -p "${dest%/*}"
+
if [ "${from#null:}" != "$from" ]; then
error 1 NOTPREDL "%s was not pre-downloaded" "${from#null:}"
-   elif [ "${from#http://}; != "$from" ] || [ "${from#ftp://}; != "$from" 
]; then
-   # http/ftp mirror
-   if wgetprogress -O "$dest" "$from"; then
-   return 0
-   else
-   rm -f "$dest"
-   return 1
-   fi
-   elif [ "${from#https://}; != "$from" ] ; then
-   # http/ftp mirror
-   if wgetprogress "$CHECKCERTIF" "$CERTIFICATE" "$PRIVATEKEY" -O 
"$dest" "$from"; then
+   elif [ "${from#http://}; != "$from" ] || [ "${from#ftp://}; != "$from" 
] || [ "${from#https://}; != "$from" ]; then
+   # HTTP(S) mirror (FTP mirror is deprecated but not removed)
+   if wgetprogress ; then
return 0
else
rm -f "$dest"

Bug#898088: arc4random_buf() may block for a long time

[Ben Caradoc-Davies]

This also affects xfce4-session:

Bug#899080: xfce4-session hangs in getrandom if crng not ready
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899080

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: severity of 899080 is serious, merging 898088 899080

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 899080 serious
Bug #899080 [src:libbsd] xfce4-session hangs in getrandom if crng not ready
Severity set to 'serious' from 'important'
> merge 898088 899080
Bug #898088 [src:libbsd] arc4random_buf() may block for a long time
Bug #899080 [src:libbsd] xfce4-session hangs in getrandom if crng not ready
Added tag(s) upstream.
Merged 898088 899080
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898088
899080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898501: OpenStack dashboard also affected

[Paul Wise]

On Fri, May 18, 2018 at 6:06 PM, Pierre-Elliott Bécue wrote:

> The appropriate move would be to ask to upstream where each link should
> point to, and fix the package accordingly to their answer.

Even better would be to:

Use a font rendering system like pango that can use all available
fonts on the system, instead of having to use specific fonts.

If that is rejected, use fontconfig to look up the font path instead
of hard-coding the font path.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Processed (with 1 error): merging 898088 899080

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 898088 899080
Bug #898088 [src:libbsd] arc4random_buf() may block for a long time
Unable to merge bugs because:
severity of #899080 is 'important' not 'serious'
Failed to merge 898088: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898088
899080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#896753: marked as done (dkimpy: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Sat, 19 May 2018 01:04:23 +
with message-id 
and subject line Bug#896753: fixed in dkimpy 0.8.0-1
has caused the Debian Bug report #896753,
regarding dkimpy: missing build dependency on python3-distutils
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.)


-- 
896753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dkimpy
Version: 0.7.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dkimpy.html

...
python3 setup.py clean -a
Traceback (most recent call last):
  File "setup.py", line 24, in 
from distutils.core import setup
ModuleNotFoundError: No module named 'distutils.core'
make[1]: *** [debian/rules:25: override_dh_auto_clean] Error 1


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: dkimpy
Source-Version: 0.8.0-1

We believe that the bug you reported is fixed in the latest version of
dkimpy, 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.
Scott Kitterman  (supplier of updated dkimpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2018 20:38:37 -0400
Source: dkimpy
Binary: python-dkim python3-dkim
Architecture: source all
Version: 0.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 python-dkim - Python module for DKIM and ARC signing and verification
 python3-dkim - Python 3 module for DKIM and ARC signing and verification
Closes: 896753
Changes:
 dkimpy (0.8.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
 .
   [ Scott Kitterman ]
   * New upstream release
 - Switches to setuptools, add python-setuptools and python3-setuptools to
   build-depends (Closes: #896753)
 - Clean up debian/rules since moving scripts to language neutral name is
   now done upstream
   * Bump standards-version to 4.1.4 without further change
   * Provide /usr/bin scripts from python3-dkim rather than python-dkim
 - Update package descriptions
 - Python3-dkim Replaces previous versions of python-dkim
Checksums-Sha1:
 5b7634db48dbabcade5babb2f35677291447b453 2019 dkimpy_0.8.0-1.dsc
 4a3dd3c49ec684d0d2deeb793b9dc67a4613e254 49663 dkimpy_0.8.0.orig.tar.gz
 7902ba252c76c15c8b1eadb7025866568a573ad9 4764 dkimpy_0.8.0-1.debian.tar.xz
 dd751d2fa36e4cd98fe3d1471a54491d740fe47c 5544 dkimpy_0.8.0-1_amd64.buildinfo
 dc9a02cc888bd88166a9a43764a649cd4c8493c6 41928 python-dkim_0.8.0-1_all.deb
 38ab37026bd82c98366912fcf3466758bc7189d6 50136 python3-dkim_0.8.0-1_all.deb
Checksums-Sha256:
 7104dc6d1de5549fe99064740e98350afc31d78dd423e03f605f6dec0f8d9bcf 2019 
dkimpy_0.8.0-1.dsc
 f09bd4893885d2e12ec9c0c9e2b6bcce6afe0f0473e0d024b8885e698c17d454 49663 
dkimpy_0.8.0.orig.tar.gz
 4bf00a793391deab1889493a66a478c559c3b8a92f8446ba9cffd99c4ee9e6f9 4764 
dkimpy_0.8.0-1.debian.tar.xz
 fb8b07980591b4816784cd6c95666caedd57d828e194de4706fcbad72ae5d79c 5544 
dkimpy_0.8.0-1_amd64.buildinfo
 b2747c681a3561f98c1370a98dfccf3edb6378d4bd2acbe6cc2c8eac6d6045c5 41928 
python-dkim_0.8.0-1_all.deb
 8d2e3d63a8de116a849cb1e6f4d57e91c52680aca1e686d4ad724a93198eaa64 50136 
python3-dkim_0.8.0-1_all.deb
Files:
 00a50f0d9dd041fdcb1e9f21286e6643 2019 python optional dkimpy_0.8.0-1.dsc
 c7781b91e36efa0a0f3cdc8800b7a7ef 49663 python optional dkimpy_0.8.0.orig.tar.gz
 6ac7048dc45966a82e657ff9e47e2e49 4764 python optional 
dkimpy_0.8.0-1.debian.tar.xz
 02d18798feeb7dba5c80f4c94517bb7f 5544 python optional 
dkimpy_0.8.0-1_amd64.buildinfo
 83e15e3bf52139fdb86d0993ef27a86e 41928 python optional 
python-dkim_0.8.0-1_all.deb
 040f71dfca7dac8e5d6e4cb24f203a34 50136 python optional 
python3-dkim_0.8.0-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: Bug #896753 in dkimpy marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896753 [src:dkimpy] dkimpy: missing build dependency on python3-distutils
Added tag(s) pending.

-- 
896753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#896753: Bug #896753 in dkimpy marked as pending

[scott]

Control: tag -1 pending

Hello,

Bug #896753 in dkimpy 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/python-team/modules/dkimpy/commit/f7aba6e3e3972af40256c7686cb8a17804b12246


Switches to setuptools, add python-setuptools and python3-setuptools to 
build-depends (Closes: #896753)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896753

Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[A. Maitland Bottoms]

If the problem can be traced to the .pc file and pkg-config I will take blame 
for a bug.  I am away from an appropriate computer right now, but will 
investigate further soon.

-Maitland


On May 18, 2018 7:20:55 AM EDT, Andrey Rahmatullin  wrote:
>On Fri, May 18, 2018 at 01:06:18PM +0200, Andreas Tille wrote:
>> > The reason for this: the configure script compiles the following
>code:
>> > 
>> > #include 
>> > #include 
>> > int main() { std::cout << 1 << '\t' << 0; return 0; }
>> > 
>> > in order to check that  exists.
>> > But this code still requires -llog4cpp:
>> 
>> Thanks for the explanation but may be I'm missing your point.  The
>> package installs liblog4cpp.a as well and the dynamic library
>installs
>> the according .so file.  So why should the requriement -llog4cpp not
>> fulfilled?
>The configure script doesn't pass -llog4cpp. It tests for the existence
>of
>the header and tries to find a correct -I option for it. Finding the
>correct -L is the next step.
>
>> > /tmp/cc41MUW4.o: In function
>`__static_initialization_and_destruction_0(int, int)':
>> > 2.cpp:(.text+0x5b): undefined reference to
>`log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
>> > 2.cpp:(.text+0x70): undefined reference to
>`log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
>> > collect2: error: ld returned 1 exit status
>> 
>> Isn't this rather a bug in log4cpp?
>No.
>
>-- 
>WBR, wRAR

Bug#899079: FTBFS: Error: This expression has type

[Adam Borowski]

Source: ocp-indent
Version: 1.5.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
During an archive rebuild, your package failed.  Tried on armhf amd64 -- but
it also has been recently binNMUed on the official buildds, and is all red
on all architectures.

File "src/indentArgs.ml", line 236, characters 62-65:
Error: This expression has type
 [ `I of string * string
 | `Noblank
 | `P of string
 | `Pre of string
 | `S of string ] list
   but an expression was expected of type Cmdliner.Manpage.block list
   Type
 [ `I of string * string
 | `Noblank
 | `P of string
 | `Pre of string
 | `S of string ]
   is not compatible with type
 Cmdliner.Manpage.block =
   [ `Blocks of Cmdliner.Manpage.block list
   | `I of string * string
   | `Noblank
   | `P of string
   | `Pre of string
   | `S of string ] 
   The first variant type does not allow tag(s) `Blocks

Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.16.5-00026-gc10e6da81c74 (SMP w/4 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)


ocp-indent_armhf.build
Description: inode/symlink

Processed: bug 897691 is forwarded to https://github.com/beerfactory/hbmqtt/pull/131

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 897691 https://github.com/beerfactory/hbmqtt/pull/131
Bug #897691 [python3-hbmqtt] python3-hbmqtt: overly generic python module name: 
/usr/lib/python3/dist-packages/scripts/__init__.py
Set Bug forwarded-to-address to 
'https://github.com/beerfactory/hbmqtt/pull/131'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [Debichem-devel] Bug#897492: what are you building?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #897492 [src:psi4] psi4: FTBFS: pybind11.h:1010:105: error: cannot convert 
'void (psi::SuperFunctional::*)(int) const' to 'void (psi::Functional::*)(int) 
const' in return
Added tag(s) patch.

-- 
897492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#897492: [Debichem-devel] Bug#897492: what are you building?

[Gilles Filippini]

Control: tags -1 + patch

Hi,

On Tue, 15 May 2018 00:14:25 +0200 Michael Banck  wrote:
> Hi Lori,
> 
> On Mon, May 14, 2018 at 11:18:43AM -0400, Lori Burns wrote:
> > * What version of psi4 are you trying to build? 
> 
> This should be 1.1.
> 
> > Apparently not a git clone, so I can’t see the version info. If it’s
> > 1.1, then the pybind11 2.2 that you’re using absolutely won’t work (I
> > hadn’t added EXACT to `find_package(pybind11 2.0 EXACT REQUIRED)`
> > then). Moreover, no pb11 2.0 _package_ will work (unless yours was
> > built with CMake, not pip) and you just have to let psi4 build system
> > pull and build its own. 
> 
> Back when 1.1. was introduced to Debian/Ubuntu, pybin11-2.0 was the
> current version and yes, it seems like they were built with cmake, but I
> didnt' dig very deep into this.
> 
> In the meantime, it appears that pybind11 got updated to 2.2.

Could the fix be as simple as the one attached? The package builds fine,
but I don't know how to test it (just investigating this issue because
psi4 is a reverse dependency of hdf5).

Regards,

_g.
diff -Nru psi4-1.1/debian/changelog psi4-1.1/debian/changelog
--- psi4-1.1/debian/changelog   2018-01-14 11:12:10.0 +0100
+++ psi4-1.1/debian/changelog   2018-05-17 20:07:24.0 +0200
@@ -1,3 +1,10 @@
+psi4 (1:1.1-6) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload
+  * Fix FTBFS with pybind11 2.2 (closes: #897492)
+
+ -- Gilles Filippini   Thu, 17 May 2018 20:07:24 +0200
+
 psi4 (1:1.1-5) unstable; urgency=medium
 
   * debian/control (Build-Depends): Added python3-pytest.
diff -Nru psi4-1.1/debian/patches/series psi4-1.1/debian/patches/series
--- psi4-1.1/debian/patches/series  2018-01-13 18:27:21.0 +0100
+++ psi4-1.1/debian/patches/series  2018-05-17 20:04:40.0 +0200
@@ -5,3 +5,4 @@
 libderiv_include_location.patch
 fix_manual_build.patch
 verbose_makefile.patch
+support-pybind11-2.2.patch
diff -Nru psi4-1.1/debian/patches/support-pybind11-2.2.patch 
psi4-1.1/debian/patches/support-pybind11-2.2.patch
--- psi4-1.1/debian/patches/support-pybind11-2.2.patch  1970-01-01 
01:00:00.0 +0100
+++ psi4-1.1/debian/patches/support-pybind11-2.2.patch  2018-05-17 
20:07:24.0 +0200
@@ -0,0 +1,14 @@
+Description: Tentative fix for pybind11 2.2 support
+Index: psi4-1.1/psi4/src/export_functional.cc
+===
+--- psi4-1.1.orig/psi4/src/export_functional.cc
 psi4-1.1/psi4/src/export_functional.cc
+@@ -109,7 +109,7 @@ void export_functional(py::module )
+ def("set_meta_cutoff", ::set_meta_cutoff, "docstring").
+ def("set_parameter", ::set_parameter, "docstring").
+ def("print_out", ::py_print, "docstring").
+-def("print_detail",::py_print_detail, "docstring");
++def("print_detail",::py_print_detail, "docstring");
+ 
+ py::class_(m, "VBase", "docstring").
+ def_static("build", [](std::shared_ptr , 
std::shared_ptr , std::string type){


signature.asc
Description: OpenPGP digital signature

Bug#877295: marked as done (amarok build-depends on removed package libgpod-nogtk-dev)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 22:34:37 +
with message-id 
and subject line Bug#877295: fixed in amarok 2.9.0-1
has caused the Debian Bug report #877295,
regarding amarok build-depends on removed package libgpod-nogtk-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.)


-- 
877295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amarok
Version: 2.8.0-8
Severity: serious
Tags: buster sid

libgpod-nogtk-dev was a transitional package removed in libgpod 0.8.3-9.

amarok is the only package build-depending on libgpod-nogtk-dev.

To fix this bug, remove the first alternative from
  libgpod-nogtk-dev (>= 0.7.0) | libgpod-dev (>= 0.7.0)
--- End Message ---
--- Begin Message ---
Source: amarok
Source-Version: 2.9.0-1

We believe that the bug you reported is fixed in the latest version of
amarok, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated amarok 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, 19 May 2018 00:15:05 +0200
Source: amarok
Binary: amarok amarok-common amarok-doc amarok-utils
Architecture: source
Version: 2.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Pino Toscano 
Description:
 amarok - easy to use media player based on the KDE Platform
 amarok-common - architecture independent files for Amarok
 amarok-doc - Amarok documentation (Handbook)
 amarok-utils - utilities for Amarok media player
Closes: 851945 877295 896941
Changes:
 amarok (2.9.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release:
 - the Wikipedia applet works with the newer Wikipedia APIs
   (Closes: #851945)
   * Update the patches:
 - backport_dont_add_analyzer_when_not_supported.diff: drop, backported from
   upstream
 - backport_dont_crash_on_shuffle_keyb_shortcut.diff: drop, backported from
   upstream
 - backport_dont_allow_analyzer_with_vlc.diff: drop, backported from
   upstream
 - backport_gcc6.diff: drop, backported from upstream
 - backport_mpris2_desktopentry.diff: drop, backported from upstream
 - debian_disable_qtscriptbindings_check_fix.diff: drop, fixed upstream
 - debian_mysqle_amarok_local_errmsg_feature.diff: refresh/update
 - debian_mysqle_force_defaults_file.diff: disable for now, as it does not
   seem to be needed anymore
 - debian_clamz_is_runtime_dependency.diff: refresh
 - ffmpeg_2.9.patch: drop, fixed upstream
 - backport_fix_taglib_version_check.patch: drop, backported from upstream
   * Update install files.
   * Disable the gpodder.net support, as libmygpo-qt will switch soon to Qt5 in
 Debian: (Closes: #896941)
 - remove the libmygpo-qt-dev build dependency
 - update install files
   * Remove the primary libgpod-nogtk-dev build dependency, leaving the
 alternative libgpod-dev. (Closes: #877295)
   * Remove trailing whitespaces in changelog.
   * Simplify watch file, and switch it to https.
   * Update lintian overrides.
   * Remove from debian/tmp all the stuff we do not want, so it is easier to
 spot uninstalled stuff
 - remove debian/not-installed, no more needed now
   * Replace the libmariadbd-dev build dependency with default-libmysqld-dev,
 so we do not rely anymore on a specific MySQL implementation.
   * Disable the mp3tunes service: moc raises a build error related to GLib
 headers, but it does not provide a meaningful error message to diagnose
 the error; patch no-mp3tunes.diff.
   * Bump Standards-Version to 4.1.4, no changes required.
   * Bump the debhelper compatibility to 11:
 - bump the debhelper build dependency to 11~
 - bump compat to 11
 - remove --parallel for dh, as now done by default
   * Pass --fail-missing to dh_missing, so no file is missed.
   * Stop passing -Wl,--no-relax as linker flag on alpha, as 

Processed: [zfs-test]

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #899047 [zfs-test] zfs-test: outdated B+R for files taken over from 
zfsutils-linux
Added tag(s) patch.

-- 
899047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899047: [zfs-test]

[Antonio Russo]

Control: tag -1 patch

I've updated my MR [1] to add the Breaks/Conflicts to complete
the migration of the testing infrastructure. (The earlier
version should have already addressed the duplicate man page issue.)

Antonio

[1] https://salsa.debian.org/zfsonlinux-team/zfs/merge_requests/2

Bug#899077: openmpi: libmca_common_monitoring.so* does not get installed

[Matthias Maier]

Source: openmpi
Version: 3.1.0-1
Severity: serious
Tags: sid

Hi,

Openmpi version 3.1.0 gained a new library,

  libmca_common_monitoring.so -> libmca_common_monitoring.so.50.0.0
  libmca_common_monitoring.so.50 -> libmca_common_monitoring.so.50.0.0
  libmca_common_monitoring.so.50.0.0

that should be installed as well. But, the current libopenmpi3.install
file does not list the library. Running programs linked against version
3.1.0-1 might now fail with

  ""
  mca_base_component_repository_open: unable to open mca_pml_monitoring:
  libmca_common_monitoring.so.50: cannot open shared object file: No such file 
or directory
  ""

Best,
Matthias

Bug#899076: FTBFS: dh_missing: missing files, aborting

[Adam Borowski]

Source: ocaml-migrate-parsetree
Version: 1.0.7-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid that during an archive rebuild on armhf, your package failed. 
Same happens on amd64:

   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: usr/lib/ocaml/ocaml-migrate-parsetree/ocaml-migrate-parsetree.dune 
exists in debian/tmp but is not installed to anywhere
dh_missing: 
usr/lib/ocaml/ocaml-migrate-parsetree/driver-main/ocaml-migrate-parsetree.driver-main.dune
 exists in debian/tmp but is not installed to anywhere
dh_missing: 
usr/lib/ocaml/ocaml-migrate-parsetree-ocamlbuild/migrate_parsetree_ocamlbuild.ml
 exists in debian/tmp but is not installed to anywhere
dh_missing: 
usr/lib/ocaml/ocaml-migrate-parsetree-ocamlbuild/ocaml-migrate-parsetree-ocamlbuild.dune
 exists in debian/tmp but is not installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libmigrate-parsetree-ocaml (9), 
libmigrate-parsetree-ocaml-dev (130), libmigrate-parsetree-ocaml-doc (0), 
libmigrate-parsetree-ocamlbuild-ocaml (6), 
libmigrate-parsetree-ocamlbuild-ocaml-dev (7)
 * dh_installdocs: libmigrate-parsetree-ocaml (0), 
libmigrate-parsetree-ocaml-dev (0), libmigrate-parsetree-ocaml-doc (0), 
libmigrate-parsetree-ocamlbuild-ocaml (0), 
libmigrate-parsetree-ocamlbuild-ocaml-dev (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
make[1]: *** [debian/rules:17: override_dh_missing] Error 2
make[1]: Leaving directory '/<>'


Full log attached.


Meow.
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.16.5-00026-gc10e6da81c74 (SMP w/4 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)


ocaml-migrate-parsetree_armhf.build
Description: inode/symlink

Bug#899062: chezscheme: FTBFS on armhf armel

[Göran Weinholt]

Adam Borowski  writes:

> Source: chezscheme
> Version: 9.5+dfsg-2
> Severity: serious
> Justification: fails to build from source
>
> Hi!
> During an archive rebuild on armhf, I'm afraid that your package failed to
> build.  This error has also been reproduced by official buildds when a
> binNMU to recompile against libncurses6 was attempted.

Hi Adam!

Thanks for your report. I'll explain the source of the problem and my
planned solution. If you have a better idea, then I'd like to hear it.

The source of the problem is bootstrapping the compiler, which can only
be compiled by itself. Upstream does not distribute the "boot files"
required to build Chez Scheme on armel/armhf. Without them we don't have
a runtime that can run the native compiler. Their suggestion is to use
cross compilation and that is what we do when we upload this package.
The package can be cross compiled from amd64/i386 to armel/armhf (and
possibly powerpc as well if a bug is fixed).

To let the buildds get access to the boot files for all our archs, we
have two options as I see it. We either: 1) rebuild the source tarball
to add the boot files for all our archs; or 2) have the source package
build-depend on the binary package and get the boot files from there.
This would only apply to arm/powerpc.

I'd like to go with option 2. Do you see another solution that I have
overlooked?

Regards,

-- 
Göran Weinholt
Debian developer
73 de SA6CJK


signature.asc
Description: PGP signature

Bug#899062: chezscheme: FTBFS on armhf armel

[Adam Borowski]

On Fri, May 18, 2018 at 09:46:48PM +0200, Göran Weinholt wrote:
> To let the buildds get access to the boot files for all our archs, we
> have two options as I see it. We either: 1) rebuild the source tarball
> to add the boot files for all our archs; or 2) have the source package
> build-depend on the binary package and get the boot files from there.
> This would only apply to arm/powerpc.
> 
> I'd like to go with option 2. Do you see another solution that I have
> overlooked?

I don't know your setup well enough to provide a meaningful suggestion,
sorry...


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ Certified airhead; got the CT scan to prove that!
⠈⠳⣄ 

Bug#893546: marked as done (curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 19:49:25 +
with message-id 
and subject line Bug#893546: fixed in curl 7.60.0-1
has caused the Debian Bug report #893546,
regarding curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122
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.)


-- 
893546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: curl
Version: 7.38.0-4
Severity: serious
Tags: patch security upstream fixed-upstream
Justification: regression with respect to stable with security fixes
Control: fixed -1 7.38.0-4+deb8u10
Control: fixed -1 7.52.1-5+deb9u5

Hi,

the following vulnerabilities were published for curl.

CVE-2018-1000120[0]:
| A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0
| in the FTP URL handling that allows an attacker to cause a denial of
| service or worse.

CVE-2018-1000121[1]:
| A NULL pointer dereference exists in curl 7.21.0 to and including curl
| 7.58.0 in the LDAP code that allows an attacker to cause a denial of
| service

CVE-2018-1000122[2]:
| A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0
| in the RTSP+RTP handling code that allows an attacker to cause a
| denial of service or information leakage

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000120
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000120
[1] https://security-tracker.debian.org/tracker/CVE-2018-1000121
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000121
[2] https://security-tracker.debian.org/tracker/CVE-2018-1000122
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000122

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.60.0-1

We believe that the bug you reported is fixed in the latest version of
curl, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessandro Ghedini  (supplier of updated curl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2018 20:21:17 +0100
Source: curl
Binary: curl libcurl3 libcurl3-gnutls libcurl3-nss libcurl4-openssl-dev 
libcurl4-gnutls-dev libcurl4-nss-dev libcurl4-doc
Architecture: source
Version: 7.60.0-1
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Alessandro Ghedini 
Description:
 curl   - command line tool for transferring data with URL syntax
 libcurl3   - easy-to-use client-side URL transfer library (OpenSSL flavour)
 libcurl3-gnutls - easy-to-use client-side URL transfer library (GnuTLS flavour)
 libcurl3-nss - easy-to-use client-side URL transfer library (NSS flavour)
 libcurl4-doc - documentation for libcurl
 libcurl4-gnutls-dev - development files and documentation for libcurl (GnuTLS 
flavour)
 libcurl4-nss-dev - development files and documentation for libcurl (NSS 
flavour)
 libcurl4-openssl-dev - development files and documentation for libcurl 
(OpenSSL flavour)
Closes: 891997 893546 898856
Changes:
 curl (7.60.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #891997, #893546, #898856)
 + Fix use of IPv6 literals with NO_PROXY
 + Fix NIL byte out of bounds write due to FTP path trickery
   as per CVE-2018-1000120
   https://curl.haxx.se/docs/adv_2018-9cd6.html
 + Fix LDAP NULL pointer dereference as per CVE-2018-1000121
   https://curl.haxx.se/docs/adv_2018-97a2.html
 + Fix RTSP RTP buffer over-read as per CVE-2018-1000122
   https://curl.haxx.se/docs/adv_2018-b047.html
 + Fix heap buffer overflow when closing down an FTP connection
   with very long server command replies as per CVE-2018-1000300
   https://curl.haxx.se/docs/adv_2018-82c2.html
 + Fix heap buffer over-read when parsing bad RTSP headers
   as per CVE-2018-1000301
  

Bug#898856: marked as done (curl: CVE-2018-1000301: RTSP bad headers buffer over-read)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 19:49:25 +
with message-id 
and subject line Bug#898856: fixed in curl 7.60.0-1
has caused the Debian Bug report #898856,
regarding curl: CVE-2018-1000301: RTSP bad headers buffer over-read
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.)


-- 
898856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: curl
Version: 7.26.0-1+wheezy13
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for curl:

 https://curl.haxx.se/docs/adv_2018-b138.html

It was given CVE number CVE-2018-1000301[0]:

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-1000301
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000301


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.60.0-1

We believe that the bug you reported is fixed in the latest version of
curl, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessandro Ghedini  (supplier of updated curl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2018 20:21:17 +0100
Source: curl
Binary: curl libcurl3 libcurl3-gnutls libcurl3-nss libcurl4-openssl-dev 
libcurl4-gnutls-dev libcurl4-nss-dev libcurl4-doc
Architecture: source
Version: 7.60.0-1
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Alessandro Ghedini 
Description:
 curl   - command line tool for transferring data with URL syntax
 libcurl3   - easy-to-use client-side URL transfer library (OpenSSL flavour)
 libcurl3-gnutls - easy-to-use client-side URL transfer library (GnuTLS flavour)
 libcurl3-nss - easy-to-use client-side URL transfer library (NSS flavour)
 libcurl4-doc - documentation for libcurl
 libcurl4-gnutls-dev - development files and documentation for libcurl (GnuTLS 
flavour)
 libcurl4-nss-dev - development files and documentation for libcurl (NSS 
flavour)
 libcurl4-openssl-dev - development files and documentation for libcurl 
(OpenSSL flavour)
Closes: 891997 893546 898856
Changes:
 curl (7.60.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #891997, #893546, #898856)
 + Fix use of IPv6 literals with NO_PROXY
 + Fix NIL byte out of bounds write due to FTP path trickery
   as per CVE-2018-1000120
   https://curl.haxx.se/docs/adv_2018-9cd6.html
 + Fix LDAP NULL pointer dereference as per CVE-2018-1000121
   https://curl.haxx.se/docs/adv_2018-97a2.html
 + Fix RTSP RTP buffer over-read as per CVE-2018-1000122
   https://curl.haxx.se/docs/adv_2018-b047.html
 + Fix heap buffer overflow when closing down an FTP connection
   with very long server command replies as per CVE-2018-1000300
   https://curl.haxx.se/docs/adv_2018-82c2.html
 + Fix heap buffer over-read when parsing bad RTSP headers
   as per CVE-2018-1000301
   https://curl.haxx.se/docs/adv_2018-b138.html
   * Refresh patches
   * Bump Standards-Version to 4.1.4 (no changes needed)
Checksums-Sha1:
 17ea89ff570f6466eaab758c5571e9537e3edea2 2678 curl_7.60.0-1.dsc
 31c68f25832ee3af7480a48d1d5dffbe6771df17 3949173 curl_7.60.0.orig.tar.gz
 3bd916f98238507af55094a476f94d5f683ab1f5 28044 curl_7.60.0-1.debian.tar.xz
 d7baa16151de879cb30d649457d02eca0becb5b6 11037 curl_7.60.0-1_amd64.buildinfo
Checksums-Sha256:
 bc0ff8df97daaef91be8492f006705620edb8129a91cf96bd52b321edccbe4be 2678 
curl_7.60.0-1.dsc
 e9c37986337743f37fd14fe8737f246e97aec94b39d1b71e8a5973f72a9fc4f5 3949173 
curl_7.60.0.orig.tar.gz
 9df332182666f04e07a676059942c6c4f7c786be84d938bcaf13bdb4e03c9c15 28044 
curl_7.60.0-1.debian.tar.xz
 

Bug#899065: CVE-2017-9269 CVE-2017-7436 CVE-2017-7435

[Moritz Muehlenhoff]

Source: libzypp
Severity: grave
Tags: security

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7435
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7436
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9269

Cheers,
Moritz

Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

[Chuck Lever]

> On May 17, 2018, at 5:48 PM, Moritz Schlarb  wrote:
> 
> Hi Chuck,
> 
> On 17.05.2018 16:15, Chuck Lever wrote:
> 
>> Just a shot in the dark: Wondering if v3.16 needs
>> 
>> commit ea96d1ecbe4fcb1df487d99309d3157b4ff5fc02
>> Author: Anna Schumaker 
>> AuthorDate: Fri Apr 3 14:35:59 2015 -0400
>> Commit: Trond Myklebust 
>> CommitDate: Thu Apr 23 14:43:54 2015 -0400
>> 
>>nfs: Fetch MOUNTED_ON_FILEID when updating an inode
> 
> Gosh, it seems you're right!
> When I take that patch and apply it, the referrals are being followed again!
> 
> Thanks for your idea!
> Now how do we make sure it gets applied soonish?

Hi Moritz-

Anyone (including you or your distributor) can request that this
patch be applied to the upstream v3.16 LTS branch. Since you have
confirmed that it applies and fixes your problem, it would be
appropriate to report that along with your backport request.


--
Chuck Lever

Bug#898433: FTBFS: README.md -> README.rst

[Harlan Lieberman-Berg]

Oh, I see what's happening.

Lee, can you do a -2 and make sure to merge against git on salsa?

On Fri, May 18, 2018 at 2:49 PM, Harlan Lieberman-Berg
 wrote:
> Hi Daniel,
>
> I'm a bit confused as well.  I didn't upload any debs at all; I did a
> source-only upload.  The buildd's successfully built -2 against the
> original tarball that was uploaded with -1... and I just rebuilt it
> again.
>
> Can you verify your source matches the sha256sum of
> 5e817a3e077565bc1ff294d5a4748fbd8d78435fa721ebf617945568e45d603a?  You
> can retrieve the original source with pristine-tar against the git
> repository on salsa.
>
> On Fri, May 18, 2018 at 1:20 PM, Daniel Baumann
>  wrote:
>> reopen 898433
>> found 898433 2.5.3+dfsg-1
>> thanks
>>
>> Hi,
>>
>> thanks for fixing it, however, your last upload unfortunaly re-imports
>> the problem.
>>
>> I'm a bit confused on how the package could have been built at all. The
>> source package FTBFS'es, but you could upload the *_all.debs. Do you
>> build from different sources than what is included in the source package?
>>
>> Regards,
>> Daniel
>
>
>
> --
> Harlan Lieberman-Berg
> ~hlieberman



-- 
Harlan Lieberman-Berg
~hlieberman

Bug#899062: chezscheme: FTBFS on armhf armel

[Adam Borowski]

Source: chezscheme
Version: 9.5+dfsg-2
Severity: serious
Justification: fails to build from source

Hi!
During an archive rebuild on armhf, I'm afraid that your package failed to
build.  This error has also been reproduced by official buildds when a
binNMU to recompile against libncurses6 was attempted.

.
CC=arm-linux-gnueabihf-gcc ./configure --workarea=build -m=arm32le --threads 
--installprefix=/usr --temproot=/<>/chezscheme-9.5+dfsg/debian/tmp
no suitable machine type found
try rerunning as ./configure -m=
available machine types: a6le, a6nt, a6osx, i3le, i3nt, i3osx, ta6le, ta6nt, 
ta6osx, ti3le, ti3nt, and ti3osx
debian/rules:42: recipe for target 'override_dh_auto_configure' failed
`


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.16.5-00026-gc10e6da81c74 (SMP w/4 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)


chezscheme_armhf.build
Description: inode/symlink

Bug#898433: FTBFS: README.md -> README.rst

[Harlan Lieberman-Berg]

Hi Daniel,

I'm a bit confused as well.  I didn't upload any debs at all; I did a
source-only upload.  The buildd's successfully built -2 against the
original tarball that was uploaded with -1... and I just rebuilt it
again.

Can you verify your source matches the sha256sum of
5e817a3e077565bc1ff294d5a4748fbd8d78435fa721ebf617945568e45d603a?  You
can retrieve the original source with pristine-tar against the git
repository on salsa.

On Fri, May 18, 2018 at 1:20 PM, Daniel Baumann
 wrote:
> reopen 898433
> found 898433 2.5.3+dfsg-1
> thanks
>
> Hi,
>
> thanks for fixing it, however, your last upload unfortunaly re-imports
> the problem.
>
> I'm a bit confused on how the package could have been built at all. The
> source package FTBFS'es, but you could upload the *_all.debs. Do you
> build from different sources than what is included in the source package?
>
> Regards,
> Daniel



-- 
Harlan Lieberman-Berg
~hlieberman

Processed: Re: Bug#899004: gnome-shell: crash on attempt to lock

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #899004 [gnome-shell] gnome-shell: crash on attempt to lock
Added tag(s) moreinfo.

-- 
899004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899004: gnome-shell: crash on attempt to lock

[Simon McVittie]

Control: tags -1 + moreinfo

On Fri, 18 May 2018 at 15:21:57 +0200, Josep M. Perez wrote:
> gnome-shell crashes when I press meta+L to lock the session. After the third
> failed attempt, it crashes and also suspends the computer.

How reproducible is this? If you reboot your computer and try repeatedly
locking your screen, does the same thing happen again?

Is there anything that looks relevant in the systemd journal or syslog
at around the time of the crash?

Did you previously run a version of gnome-shell that did not have this bug?
If you did, what packages did you upgrade around the time it started
happening? (/var/log/apt/history.log* might be useful)

Do you have any GNOME Shell extensions enabled?

I notice that the backtrace you provided involves libnm, the NetworkManager
client library. Is there anything unusual about your networking that might
explain why you see this crash when other people don't?

I uploaded new versions of gnome-shell, mutter and gjs earlier today
(gnome-shell 3.28.2, mutter 3.28.2 and gjs 1.52.3-2). Please could you
try with those when they become available, and report back with whether
this bug is still visible in those versions?

Thanks,
smcv

Bug#806946: bindgraph

[Juri Grabowski]

Hello,

I cannot reproduce it on sid with my settings:

cat <>/etc/bind/named.conf.options
logging {

channel querylog{

file "/var/log/bind9-query.log";
severity debug 10;
print-category yes;
print-time yes;
print-severity yes;
};
category queries { querylog;}; };
EOF
in options section:
querylog yes;

install -D --group=adm --owner=bind --mode=0640 /dev/null 
/var/log/bind9-query.log
service bind9 restart 
service bindgraph restart 
a2enmod cgi
service apache2 restart 
serve http://$FQDN/cgi-bin/bindgraph.cgi

Best Regards,
Juri Grabowski

Processed: Re: FTBFS: README.md -> README.rst

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 898433
Bug #898433 {Done: Harlan Lieberman-Berg } [ansible] 
FTBFS: README.md -> README.rst
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ansible/2.5.2+dfsg-2.
> found 898433 2.5.3+dfsg-1
Bug #898433 [ansible] FTBFS: README.md -> README.rst
Marked as found in versions ansible/2.5.3+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898433: FTBFS: README.md -> README.rst

[Daniel Baumann]

reopen 898433
found 898433 2.5.3+dfsg-1
thanks

Hi,

thanks for fixing it, however, your last upload unfortunaly re-imports
the problem.

I'm a bit confused on how the package could have been built at all. The
source package FTBFS'es, but you could upload the *_all.debs. Do you
build from different sources than what is included in the source package?

Regards,
Daniel

Bug#828475: openssh: Please migrate to openssl1.1 in Buster

[James Cloos]

> Moritz Muehlenhoff  writes:

> This is clearly not ideal,

Many would argue that it is ideal.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#899047: zfs-test: outdated B+R for files taken over from zfsutils-linux

[Fabian Grünbichler]

Package: zfs-test
Version: 0.7.9-2
Severity: serious

commit 2c29cd95fd0e5fccc035bf7dead27a4b73708f12 moved the following
files from zfsutils-linux to zfs-test, without updating zfs-test's
versioned Breaks+Replaces relation accordingly:

/sbin/ztest

the following files are now also installed in zfs-test, in addition to
being installed in zfsutils-linux:

/usr/share/man/man1/ztest.1
/usr/share/man/man1/raidz_test.1
/usr/share/man/man1/test-runner.1

this leads to failed apt runs with messages like the following:

Unpacking zfs-test (0.7.9-2) over (0.7.6-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/zfs-test_0.7.9-2_amd64.deb (--unpack):
 trying to overwrite '/sbin/ztest', which is also in package zfsutils-linux 
0.7.6-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Unpacking zfs-test (0.7.9-2) over (0.7.6-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-jpbbT5/15-zfs-test_0.7.9-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/raidz_test.1.gz', which is also in 
package zfsutils-linux 0.7.9-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

I suggest explicitly listing the man (1) pages to be installed in
zfsutils-linux in debian/zfsutils-linux.install (instead of the whole
/usr/share/man/man1 directory) to get rid of the duplicate files, and
bumping the versioned B+R for zfs-test accordingly (because of the
duplicate files, zfs-test now Breaks and Replaces zfsutils-linux <=
0.7.9-2, and only -3 should move to buster be backported IMHO.

thanks for your consideration!

Bug#898958: peruse: does not start

[Rik Mills]

On 18/05/18 14:25, Juhani Numminen wrote:
> On Thu, 17 May 2018 22:01:59 +0200 Serge Kilimoff-Goriatchkine 
>  wrote:
> are you aware of the Ubuntu changes? Looks like they're related to this issue.
> https://patches.ubuntu.com/p/peruse/peruse_1.2+dfsg-2ubuntu1.patch

Yes, the issue has been brought to Simon and the KDE team's attention.

It is an unfortunate oversight that the wrong version of Kirigami was
assumed as required. While I could 'band aid fix' this in Ubuntu quite
easily, as we had not removed Kirigami v1 source anticipating packaging
persue at a much earlier time, in debian it has been removed.

Both peruse 1.2 branch and Kirigami v1 are unlikely to get much upstream
support in the form of bugfix updates, so at least for debian I think
the consensus was to entourage upstream KDE to release the new Kirigami
v2 based persue as soon as the KDE developer is happy to, and fix the
issue with nice new version of that.

Rik

Bug#899008: marked as done (breezy-debian: FTBFS: Unable to import library "dulwich")

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 16:19:24 +
with message-id 
and subject line Bug#899008: fixed in breezy-debian 2.8.13
has caused the Debian Bug report #899008,
regarding breezy-debian: FTBFS: Unable to import library "dulwich"
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.)


-- 
899008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breezy-debian
Version: 2.8.12
Severity: serious
Justification: FTBFS

When testing packages against the upcoming release of perl, we found
an unrelated FTBFS on a clean sid chroot:

10.863  opening working tree 
'/tmp/testbzr-Mq8mdV.tmp/breezy.plugins.debian.tests.test_upstream.UpstreamBranchSourceTests.test_version_as_revision_invalid_revspec/work'
}}}

Traceback (most recent call last):
  File "/<>/tests/test_upstream.py", line 465, in 
test_version_as_revision_invalid_revspec
source.version_as_revision, "foo", "2.1+bzr4242")
  File "/usr/lib/python2.7/dist-packages/breezy/tests/__init__.py", line 1468, 
in assertRaises
callableObj(*args, **kwargs)
  File "/<>/upstream/branch.py", line 245, in version_as_revision
revspec).as_revision_id(self.upstream_branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 226, in 
as_revision_id
return self._as_revision_id(context_branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 234, in 
_as_revision_id
return self.in_history(context_branch).rev_id
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 208, in 
in_history
return self._match_on_and_check(branch, revs=None)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 196, in 
_match_on_and_check
info = self._match_on(branch, revs)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 313, in 
_match_on
return self._try_spectype(rs_class, branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 297, in 
_try_spectype
return rs.in_history(branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 208, in 
in_history
return self._match_on_and_check(branch, revs=None)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 196, in 
_match_on_and_check
info = self._match_on(branch, revs)
  File "/usr/lib/python2.7/dist-packages/breezy/plugins/git/revspec.py", line 
117, in _match_on
lazy_check_versions()
  File "/usr/lib/python2.7/dist-packages/breezy/plugins/git/__init__.py", line 
82, in lazy_check_versions
import_dulwich()
  File "/usr/lib/python2.7/dist-packages/breezy/plugins/git/__init__.py", line 
69, in import_dulwich
"bzr-git: Please install dulwich, https://www.dulwich.io/;)
breezy.errors.DependencyNotPresent: Unable to import library "dulwich": 
bzr-git: Please install dulwich, https://www.dulwich.io/

--
Ran 532 tests in 11.355s

FAILED (errors=1)
4 tests skipped
--- End Message ---
--- Begin Message ---
Source: breezy-debian
Source-Version: 2.8.13

We believe that the bug you reported is fixed in the latest version of
breezy-debian, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated breezy-debian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2018 16:40:12 +0100
Source: breezy-debian
Binary: brz-debian
Architecture: source
Version: 2.8.13
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Jelmer Vernooij 
Description:
 brz-debian - breezy plugin for Debian package management
Closes: 899008
Changes:
 breezy-debian (2.8.13) unstable; urgency=medium
 .
   * Add dependency on python-dulwich. Closes: #899008
   * Remove obsolete URL from debian/copyright.
   * Change Vcs-Bzr URL to launchpad.
   * debian/source/lintian-overrides: Fix source package name.

Bug#828475: openssh: Please migrate to openssl1.1 in Buster

[Moritz Muehlenhoff]

Hi,
we've discussed the topic of handling this particular bug at the Debian Security
Team sprint and discussing the various non-optimal solutions we feel embedding
libressl into the openssh package is the last disagreeable solution.

- We clearly need openssh in buster
- We clearly don't want OpenSSL 1.0.2 in buster
- It seems very unlikely that openssh will support the OpenSSL 1.1 APIs in
  the short term
- Using the compat patch seems risky
- OpenSSH only uses libcrypto, which is less exposed to high impact
  vulnerabilities compared to libssl. We can triage new openssl/libressl
  vulnerabilities to the extent they affect openssh in our current security
  triage workflows.

This is clearly not ideal, but we can revisit that for every release.
Who knows what happens until then, maybe enterprise distros fork by
openssh by then. Or maybe ongoing code changes in openssh reduce the
set of the compat shim to an extent which makes it sensible to revisit
the whole situation.

I've had a quick look at all openssl CVE IDs from 2017 affecting libcrypto
and I don't think any of the four (the others affects libssl only) would
be something we would have backported to a stable release (two of them
are likely not present in libressl anyway and probably specific to OpenSSL).

Cheers,
Moritz

Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream

[Dominic Hargreaves]

Source: libembperl-perl
Version: 2.5.0-11
Severity: serious
Justification: unmaintained upstream, and will shortly break in Debian
X-Debbugs-Cc: debian-p...@lists.debian.org
User: debian-p...@lists.debian.org
Usertags: perl-5.28-transition hh2018

The upstream version of this package has not worked since 5.18, and we
have had to apply several fixes in Debian since. The build has now
broken again with Perl 5.27:

http://perl.debian.net/rebuild-logs/perl-5.27-throwaway/libembperl-perl_2.5.0-11/libembperl-perl_2.5.0-11_amd64-2018-05-18T08:09:28Z.build

The problem in this case might not be that hard to fix, but I have
been consisdering deprecating/removing this for some time, as there is
a limit to how long we can be de facto upstream for this type of
package.

Currently the package has a popcon of inst: 37 / vote: 22 / recent: 1
suggesting that it is barely used anywhere. So I suggest that rather than
spending any more time maintaining it, we remove it from Debian.

CC to debian-perl to get wider exposure of the proposal.

Cheers,
Dominic.

Bug#898940: lastpass-cli: error: Peer certificate cannot be authenticated with given CA certificates

[Chris Lamb]

Hi,

> lastpass-cli: error: Peer certificate cannot be authenticated with
> given CA certificates

Would you be interested in letting me adopt this package (or co-
maintaining it?).


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#899019: getfem++ FTBFS: FAIL demo_laplacian.py

[Dominic Hargreaves]

Source: getfem++
Version: 5.2+dfsg1-6
Severity: serious
Justification: FTBFS

When testing packages against the upcoming release of perl, we found
an unrelated FTBFS on a clean sid chroot:

===
   getfem 5.2: interface/tests/python/test-suite.log
===

# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: demo_laplacian.py
===

Traceback (most recent call last):
  File "./demo_laplacian.py", line 60, in 
fneum = np.compress(True - ttop - tleft, flst, axis=1)
TypeError: numpy boolean subtract, the `-` operator, is deprecated, use the 
bitwise_xor, the `^` operator, or the logical_xor function instead.
FAIL demo_laplacian.py (exit status: 1)

Bug#899008: breezy-debian: FTBFS: Unable to import library "dulwich"

[Dominic Hargreaves]

Source: breezy-debian
Version: 2.8.12
Severity: serious
Justification: FTBFS

When testing packages against the upcoming release of perl, we found
an unrelated FTBFS on a clean sid chroot:

10.863  opening working tree 
'/tmp/testbzr-Mq8mdV.tmp/breezy.plugins.debian.tests.test_upstream.UpstreamBranchSourceTests.test_version_as_revision_invalid_revspec/work'
}}}

Traceback (most recent call last):
  File "/<>/tests/test_upstream.py", line 465, in 
test_version_as_revision_invalid_revspec
source.version_as_revision, "foo", "2.1+bzr4242")
  File "/usr/lib/python2.7/dist-packages/breezy/tests/__init__.py", line 1468, 
in assertRaises
callableObj(*args, **kwargs)
  File "/<>/upstream/branch.py", line 245, in version_as_revision
revspec).as_revision_id(self.upstream_branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 226, in 
as_revision_id
return self._as_revision_id(context_branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 234, in 
_as_revision_id
return self.in_history(context_branch).rev_id
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 208, in 
in_history
return self._match_on_and_check(branch, revs=None)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 196, in 
_match_on_and_check
info = self._match_on(branch, revs)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 313, in 
_match_on
return self._try_spectype(rs_class, branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 297, in 
_try_spectype
return rs.in_history(branch)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 208, in 
in_history
return self._match_on_and_check(branch, revs=None)
  File "/usr/lib/python2.7/dist-packages/breezy/revisionspec.py", line 196, in 
_match_on_and_check
info = self._match_on(branch, revs)
  File "/usr/lib/python2.7/dist-packages/breezy/plugins/git/revspec.py", line 
117, in _match_on
lazy_check_versions()
  File "/usr/lib/python2.7/dist-packages/breezy/plugins/git/__init__.py", line 
82, in lazy_check_versions
import_dulwich()
  File "/usr/lib/python2.7/dist-packages/breezy/plugins/git/__init__.py", line 
69, in import_dulwich
"bzr-git: Please install dulwich, https://www.dulwich.io/;)
breezy.errors.DependencyNotPresent: Unable to import library "dulwich": 
bzr-git: Please install dulwich, https://www.dulwich.io/

--
Ran 532 tests in 11.355s

FAILED (errors=1)
4 tests skipped

Bug#898501: Bug#: OpenStack dashboard also affected

[Thomas Goirand]

On 05/18/2018 12:06 PM, Pierre-Elliott Bécue wrote:
> Le jeudi 17 mai 2018 à 14:39:25+0200, Thomas Goirand a écrit :
>> Hi,
>>
>> Also, the OpenStack dashboard (aka: Horizon) is also affected. I cannot
>> be installed, and therefore, all its reverse build-depends are also broken.
>>
>> If it's just a mater of fixing a few symlinks, I don't see how hard this
>> can be. Please just restore sanity in:
>> /usr/share/fonts-font-awesome/fonts/
>>
>> and just symlink to the correct location.
>>
>> Cheers,
> 
> Have a look at the deb file tree.
> 
> The truetype font is gone, and the others types has changed in their naming
> convention.
> 
> The appropriate move would be to ask to upstream where each link should
> point to, and fix the package accordingly to their answer.

In my own case (ie: for OpenStack Dashboard, aka Horizon), I don't care
the truetype, I care the webfonts. And that's probably most of the use
cases for other packages in Debian, as this font is for web use (it's
used for its icons). So, I do believe a few symlink corrections can
happen in the fonts-font-awesome package (ie: old names pointing to the
new ones).

Cheers,

Thomas Goirand (zigo)

Bug#898958: peruse: does not start

[Juhani Numminen]

On Thu, 17 May 2018 22:01:59 +0200 Serge Kilimoff-Goriatchkine 
 wrote:
> Package: peruse
> Version: 1.2+dfsg-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> When I just run "peruse" command in my terminal (in fresh installation of 
> peruse from apt), I get the following message that appears :
> 
>   Failed to load the component from disk. Reported error was: 
> "file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain 
> unavailable\nfile:///usr/share/peruse/qml/PeruseMain.qml:27 module 
> \"org.kde.kirigami\" is not installed\n"
> 
> Thanks ! Et merci !

Hello,

Installing the package qml-module-org-kde-kirigami makes it run for me.
qml-module-org-kde-kirigami is no longer in unstable, but can be downloaded
from 
https://packages.debian.org/stretch/amd64/qml-module-org-kde-kirigami/download
and then installed using apt.

Dear Maintainer,
are you aware of the Ubuntu changes? Looks like they're related to this issue.
https://patches.ubuntu.com/p/peruse/peruse_1.2+dfsg-2ubuntu1.patch


Regards,
Juhani

Bug#899004: gnome-shell: crash on attempt to lock

[Josep M. Perez]

Package: gnome-shell
Version: 3.28.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

A backtrace follows:

#0  0x770c14f4 in g_hash_table_iter_init
(iter=iter@entry=0x7ffef010, hash_table=0x10004) at
../../../../glib/ghash.c:769
#1  0x72909042 in nm_ip_address_dup (address=) at libnm-
core/nm-setting-ip-config.c:388
#2  0x773aaecb in g_boxed_copy (boxed_type=93825030200288,
src_boxed=src_boxed@entry=0x563791e0) at ../../../../gobject/gboxed.c:343
#3  0x7609f540 in gjs_boxed_from_c_struct(JSContext*, GIStructInfo*,
void*, GjsBoxedCreationFlags) (context=context@entry=0x55dd7a00,
info=info@entry=0x57aec540, gboxed=0x563791e0, flags=)
at gi/boxed.cpp:1235
#4  0x7609b194 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x58331ca0, arg=arg@entry=0x7ffef4b8,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:2909
#5  0x7609bf33 in gjs_array_from_carray_internal(JSContext*,
JS::MutableHandleValue, GITypeInfo*, guint, gpointer)
(context=context@entry=0x55dd7a00, value_p=..., value_p@entry=...,
param_info=param_info@entry=0x58331ca0, length=1, array=) at
gi/arg.cpp:2346
#6  0x7609a446 in gjs_array_from_boxed_array (arg=0x7ffef998,
param_info=0x58331ca0, array_type=, value_p=...,
context=0x55dd7a00) at gi/arg.cpp:2462
#7  0x7609a446 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x7ffef9c0, arg=arg@entry=0x7ffef998,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:3012
#8  0x760a677e in gjs_invoke_c_function(JSContext*, Function*,
JS::HandleObject, JS::HandleValueArray const&,
mozilla::Maybe, GIArgument*)
(context=context@entry=0x55dd7a00, function=function@entry=0x576f0b00,
obj=...,
obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at
gi/function.cpp:1147
#9  0x760a6a24 in function_call(JSContext*, unsigned int, JS::Value*)
(context=context@entry=0x55dd7a00, js_argc=0, vp=0x55f14d50)
at gi/function.cpp:1406
#10 0x7fffed039fdc in js::CallJSNative(JSContext*, bool (*)(JSContext*,
unsigned int, JS::Value*), JS::CallArgs const&) (args=...,
native=0x760a68c0 ,
cx=0x55dd7a00) at ./js/src/jscntxtinlines.h:239
#11 0x7fffed039fdc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=0x55dd7a00, args=...,
construct=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:447
#12 0x7fffed02d087 in js::CallFromStack(JSContext*, JS::CallArgs const&)
(args=..., cx=) at ./js/src/vm/Interpreter.cpp:510
#13 0x7fffed02d087 in Interpret(JSContext*, js::RunState&)
(cx=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:2922
#14 0x7fffed039846 in js::RunScript(JSContext*, js::RunState&)
(cx=cx@entry=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:405
#15 0x7fffed039e1f in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=cx@entry=0x55dd7a00, args=...,
construct=construct@entry=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:477
#16 0x7fffed03a099 in InternalCall(JSContext*, js::AnyInvokeArgs const&)
(cx=cx@entry=0x55dd7a00, args=...) at ./js/src/vm/Interpreter.cpp:504
#17 0x7fffed03a0f9 in js::Call(JSContext*, JS::Handle,
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle)
(cx=cx@entry=0x55dd7a00, fval=..., fval@entry=..., thisv=...,
thisv@entry=..., args=..., rval=rval@entry=...) at
./js/src/vm/Interpreter.cpp:523
#18 0x7fffece2c079 in js::jit::InvokeFunction(JSContext*,
JS::Handle, bool, unsigned int, JS::Value*,
JS::MutableHandle) (cx=0x55dd7a00, obj=...,
constructing=, argc=, argv=0x7fff06c0,
rval=...) at ./js/src/jit/VMFunctions.cpp:114
#19 0x35b97b5083c6 in  ()
#20 0x7fff0780 in  ()
#21 0x7fff0670 in  ()
#22 0xfff9 in  ()
#23 0x7fffee1dc040 in js::jit::InvokeFunctionInfo () at
/usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#24 0x7fffc05739a0 in  ()
#25 0x35b97b59f89b in  ()
#26 0x7820 in  ()
#27 0x7fffa999c700 in  ()
---Type  to continue, or q  to quit---
#28 0x in  ()

(gdb) info sharedlibrary
>FromTo  Syms Read   Shared Object Library
0x779a8c40  0x779c22de  Yes /usr/lib/gnome-
shell/libgnome-shell.so
0x776290a0  0x7770b162  Yes /usr/lib/x86_64-linux-
gnu/libgio-2.0.so.0
0x773a7f10  0x773d9b3e  Yes /usr/lib/x86_64-linux-

Bug#895882: marked as done (sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography))

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 12:55:03 +
with message-id 
and subject line Bug#895882: fixed in sphinxcontrib-bibtex 0.4.0-1
has caused the Debian Bug report #895882,
regarding sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex 
(Unknown node: bibliography)
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.)


-- 
895882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: triggers
Affects: sphinxcontrib-bibtex

Since the upload of sphinx version 1.7.2-1, the autopkgtest of
sphinxcontrib-bibtex¹ fails with the errors copied below.

As all the failures (25 failures/28 tests) really come from the same
issue (NotImplementedError: Unknown node: bibliography), the ratio
between passes and failures is so high, and the missing node name
suggests core functionality for sphinxcontrib-bibtex I file this bug
with severity *serious* against sphinx. If you believe this was
exaggerated or the issue is really in sphinxcontrib-bibtex, please don't
hesitate to lower it accordingly and/or reassign to sphinxcontrib-bibtex.

I suggest the maintainers of sphinx and sphinxcontrib-bibtex discuss how
this issue should be solved (hence the CC).

Paul

¹ https://ci.debian.net/packages/s/sphinxcontrib-bibtex

==
ERROR: test_bibfilenotfound.test_bibfilenotfound
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line
143, in decorator
func(*(args + (app, status, warning)), **kwargs)
  File
"/tmp/autopkgtest-lxc.pusg50mw/downtmp/autopkgtest_tmp/test/test_bibfilenotfound.py",
line 22, in test_bibfilenotfound
app.builder.build_all()
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 295, in build_all
self.build(None, summary='all source files', method='all')
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 399, in build
self.write(docnames, list(updated_docnames), method)
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 436, in write
self._write_serial(sorted(docnames))
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 445, in _write_serial
self.write_doc(docname, doctree)
  File "/usr/lib/python3/dist-packages/sphinx/builders/html.py", line
602, in write_doc
self.docwriter.write(doctree, destination)
  File "/usr/lib/python3/dist-packages/docutils/writers/__init__.py",
line 80, in write
self.translate()
  File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line 56,
in translate
self.document.walkabout(visitor)
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 174, in
walkabout
if child.walkabout(visitor):
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 166, in
walkabout
visitor.dispatch_visit(self)
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 1882, in
dispatch_visit
return method(node)
  File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line
882, in unknown_visit
raise NotImplementedError('Unknown node: ' + node.__class__.__name__)
NotImplementedError: Unknown node: bibliography

==
ERROR: test_citationnotfound.test_citationnotfound
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line
143, in decorator
func(*(args + (app, status, warning)), **kwargs)
  File
"/tmp/autopkgtest-lxc.pusg50mw/downtmp/autopkgtest_tmp/test/test_citationnotfound.py",
line 22, in test_citationnotfound
app.builder.build_all()
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 295, in build_all
self.build(None, summary='all source files', method='all')
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 399, in build
self.write(docnames, list(updated_docnames), method)
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 436, in write
self._write_serial(sorted(docnames))
  File 

Bug#898964: marked as done (mrs: FTBFS: you don't seem to have log4cpp installed)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 12:05:56 +
with message-id 
and subject line Bug#898964: fixed in mrs 6.0.5+dfsg-6
has caused the Debian Bug report #898964,
regarding mrs: FTBFS: you don't seem to have log4cpp installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mrs
Version: 6.0.5+dfsg-5
Severity: serious

Whilst test-rebuilding packages for the next perl release we found
an unrelated build failure:

Checking for liblog4cpp...

Cannot continue since you don't seem to have log4cpp installed
Please install the log4cpp-dev package and run configure again.
make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2

The full log is here:



This seems likely to be caused by the new release of log4cpp 1.1.3-1
last week.

Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Source: mrs
Source-Version: 6.0.5+dfsg-6

We believe that the bug you reported is fixed in the latest version of
mrs, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mrs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2018 13:37:17 +0200
Source: mrs
Binary: mrs
Architecture: source
Version: 6.0.5+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 mrs- Information Retrieval System for Biomedical databanks
Closes: 898964
Changes:
 mrs (6.0.5+dfsg-6) unstable; urgency=medium
 .
   * Skip broken test for log4cpp - we can be sure that the package exists
 due to Build-Depends anyway
 Closes: #898964
Checksums-Sha1:
 fee370ba9ab7a88177a67bc8b661b38d4453b12c 2291 mrs_6.0.5+dfsg-6.dsc
 62e8b82734c020a6d508d0f86b89105b9269f63b 6900 mrs_6.0.5+dfsg-6.debian.tar.xz
Checksums-Sha256:
 b5dcf41968be626708b57c56de6a947e0ac150466d0969f4d50a9a5f5df9dd8b 2291 
mrs_6.0.5+dfsg-6.dsc
 58ba031630273ab5af971403ebcc8e20a7818f632e953fb67e54110b9da90bc6 6900 
mrs_6.0.5+dfsg-6.debian.tar.xz
Files:
 03793e88b7282e42717436a615d03623 2291 science optional mrs_6.0.5+dfsg-6.dsc
 fa8318c14f30c98c617f145c0d5adaf9 6900 science optional 
mrs_6.0.5+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlr+vRwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGBTA/5AVbLCOHUyr0TfOHQYdONLCJREUdBonPN
iippMSIMGQICGFtI28bm9pKVZiaEsY4MyU1xiwpNX5TX0UDP3Xe0sZbhG8kBMzhG
gHNAB1G9kVbLs0/hoKfZza+OaBgfFkChSKA5aKtcoicAx8TuKwdjhyzIFmUcdk9b
B7XaliIJiaH4UUWvWuAa8klJ5zEaljBhwgv787lVnIcq0DtmAXGha/BI4N7g7Sit
Ip1+QhmfQYUVy3aKM7OOv3/cMA2LiMbyb0My2aZVQMhjLNEaz+dD8MneJw8h78Wu
MFLJ3P0RMoVCVS1d2cCq+0t4u52HTftt7ifNDho0bsTC4kVM+Vo0Dug7eNmfhN70
wNu5xaLk6X+P0xSwVjEj1l1l3xKoViHaQDchH63SpTaEMCTKU4/4cbkyUyuPMCoz
wXCrdhhSM/S07hBVI22VwQvNopad/vJ5MjB81OG/olWG7dhuL4nSKX/++fphKxYd
3qMNclVAlEGO1aTGLe3sWInlNv8pEjagpU3ChPCQvd/HFPuAUI9J4pA03GCuhbVx
5HX26DjDNHgayggI4MsyOKpRlGzH6HUzUG1GU47BTYAg+DRxGAOyRda/JnQGQwYo
oZpOdIJngj3TKJdb8PwkOQDwUKy+aQSqrG+prUewqeSCuH17zghrB+5sCKmnw6Pc
3WJh7iXzc+k=
=e4Ao
-END PGP SIGNATURE End Message ---

Processed: fixing severity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 898997 serious
Bug #898997 [linkchecker] linkchecker: ImportError: No module named 
dns.exception
Bug #897462 [linkchecker] starjava-ttools: FTBFS: ImportError: No module named 
dns.exception
Bug #897495 [linkchecker] starjava-topcat: FTBFS: ImportError: No module named 
dns.exception
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897462
897495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897495
898997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#891842: marked as done (fritzing: looks for core.fzb in the path where lunch. Same as #847655)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 11:50:00 +
with message-id 
and subject line Bug#891842: fixed in fritzing 0.9.3b+dfsg-5
has caused the Debian Bug report #891842,
regarding fritzing: looks for core.fzb in the path where lunch. Same as #847655
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.)


-- 
891842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fritzing
Version: 0.9.3b+dfsg-4.1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

When lunch the sw it doesn't find libraries because is looking for them in a 
relative path where you are.
If the lunch command is given inside /usr/share/fritzing/parts/ everything is 
ok, otherwise it doesn't find libraries.

Fresh install. Already tried to purge and reinstall.

EXAMPLE:
nicola@nicola-debian:~$ fritzing
QIODevice::read (QFile, "/home/nicola/bins/core.fzb"): device not open
QIODevice::read (QFile, "/home/nicola/bins/contribParts.fzb"): device not open
libpng warning: iCCP: known incorrect sRGB profile
QIODevice::read (QFile, "/home/nicola/bins/core.fzb"): device not open
QIODevice::read (QFile, "/home/nicola/bins/contribParts.fzb"): device not open

if:
nicola@nicola-debian:/usr/share/fritzing/parts$ fritzing 
everything is ok.

- //



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (750, 'experimental'), (700, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fritzing depends on:
ii  fritzing-data0.9.3b+dfsg-4.1
ii  libc62.26-6
ii  libgcc1  1:8-20180218-1
ii  libgit2-26   0.26.0+dfsg.1-1.1+b1
ii  libgl1   1.0.0-2
ii  libqt5concurrent55.9.2+dfsg-12
ii  libqt5core5a 5.9.2+dfsg-12
ii  libqt5gui5   5.9.2+dfsg-12
ii  libqt5network5   5.9.2+dfsg-12
ii  libqt5printsupport5  5.9.2+dfsg-12
ii  libqt5serialport55.9.2-2
ii  libqt5sql5   5.9.2+dfsg-12
ii  libqt5sql5-sqlite5.9.2+dfsg-12
ii  libqt5svg5   5.9.2-3
ii  libqt5widgets5   5.9.2+dfsg-12
ii  libqt5xml5   5.9.2+dfsg-12
ii  libstdc++6   8-20180218-1
ii  zlib1g   1:1.2.8.dfsg-5

fritzing recommends no packages.

Versions of packages fritzing suggests:
ii  fritzing-parts  0.9.3b-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fritzing
Source-Version: 0.9.3b+dfsg-5

We believe that the bug you reported is fixed in the latest version of
fritzing, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated fritzing 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, 17 May 2018 20:14:32 +0200
Source: fritzing
Binary: fritzing fritzing-data
Architecture: source all amd64
Version: 0.9.3b+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Enrique Hernández Bello 
Changed-By: Georges Khaznadar 
Description:
 fritzing   - Easy-to-use electronic design software
 fritzing-data - Easy-to-use electronic design software (data files)
Closes: 847655 891842
Changes:
 fritzing (0.9.3b+dfsg-5) unstable; urgency=medium
 .
   * made little modification to force the execution from the directory
 /usr/share/fritzing/parts; Closes: #891842; Closes: #847655 as
 somebody who types 'fritzing' from the command line will no longer
 launch the "unprotected" binary.
Checksums-Sha1:
 07fb912d23e25ca2200aa2faf70bc6cde130d56b 2173 fritzing_0.9.3b+dfsg-5.dsc
 02c1c57e9878194d330511d1825ea8e174ea4087 22652 
fritzing_0.9.3b+dfsg-5.debian.tar.xz
 

Processed: Re-assigning linkchecker bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 897495 linkchecker
Bug #897495 [src:starjava-topcat] starjava-topcat: FTBFS: ImportError: No 
module named dns.exception
Bug reassigned from package 'src:starjava-topcat' to 'linkchecker'.
No longer marked as found in versions starjava-topcat/4.5.1-2.
Ignoring request to alter fixed versions of bug #897495 to the same values 
previously set
> reassign 897462 linkchecker
Bug #897462 [src:starjava-ttools] starjava-ttools: FTBFS: ImportError: No 
module named dns.exception
Bug reassigned from package 'src:starjava-ttools' to 'linkchecker'.
No longer marked as found in versions starjava-ttools/3.1.2-2.
Ignoring request to alter fixed versions of bug #897462 to the same values 
previously set
> forcemerge 898997 897495 897462
Bug #898997 [linkchecker] linkchecker: ImportError: No module named 
dns.exception
Bug #897495 [linkchecker] starjava-topcat: FTBFS: ImportError: No module named 
dns.exception
Severity set to 'normal' from 'serious'
Marked as found in versions linkchecker/9.4.0-1.
Bug #898997 [linkchecker] linkchecker: ImportError: No module named 
dns.exception
Added tag(s) buster and sid.
Bug #897462 [linkchecker] starjava-ttools: FTBFS: ImportError: No module named 
dns.exception
Severity set to 'normal' from 'serious'
Marked as found in versions linkchecker/9.4.0-1.
Merged 897462 897495 898997
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897462
897495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897495
898997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: really add fixed version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 891250 1.45.0-2
Bug #891250 {Done: Pirate Praveen } [src:ruby-fog-core] 
ruby-fog-core: ruby-excon build dependency must be raised to (>= 0.58)
Marked as fixed in versions ruby-fog-core/1.45.0-2.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
891250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andrey Rahmatullin]

On Fri, May 18, 2018 at 01:06:18PM +0200, Andreas Tille wrote:
> > The reason for this: the configure script compiles the following code:
> > 
> > #include 
> > #include 
> > int main() { std::cout << 1 << '\t' << 0; return 0; }
> > 
> > in order to check that  exists.
> > But this code still requires -llog4cpp:
> 
> Thanks for the explanation but may be I'm missing your point.  The
> package installs liblog4cpp.a as well and the dynamic library installs
> the according .so file.  So why should the requriement -llog4cpp not
> fulfilled?
The configure script doesn't pass -llog4cpp. It tests for the existence of
the header and tries to find a correct -I option for it. Finding the
correct -L is the next step.

> > /tmp/cc41MUW4.o: In function 
> > `__static_initialization_and_destruction_0(int, int)':
> > 2.cpp:(.text+0x5b): undefined reference to 
> > `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
> > 2.cpp:(.text+0x70): undefined reference to 
> > `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
> > collect2: error: ld returned 1 exit status
> 
> Isn't this rather a bug in log4cpp?
No.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#891250: marked as done (ruby-fog-core: ruby-excon build dependency must be raised to (>= 0.58))

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 16:46:19 +0530
with message-id <00c5a6ba-b732-c671-4261-d872805f5...@debian.org>
and subject line fixed in last upload
has caused the Debian Bug report #891250,
regarding ruby-fog-core: ruby-excon build dependency must be raised to (>= 0.58)
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.)


-- 
891250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fog-core
Version: 1.45.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=ruby-fog-core=all=1.45.0-1=1519407453=0

...
GEM_PATH=debian/ruby-fog-core/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"fog-core\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'excon' (~> 0.58) - did find: [excon-0.54.0] (Gem::LoadError)
--- End Message ---
--- Begin Message ---

Control: fixed -1 1.45.0-2--- End Message ---

Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andreas Tille]

Hi Andrey,

On Fri, May 18, 2018 at 03:05:24PM +0500, Andrey Rahmatullin wrote:
> On Fri, May 18, 2018 at 11:44:02AM +0200, Andreas Tille wrote:
> > > Checking for liblog4cpp...
> > > 
> > > Cannot continue since you don't seem to have log4cpp installed
> > > Please install the log4cpp-dev package and run configure again.
> > > make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
> The reason for this: the configure script compiles the following code:
> 
> #include 
> #include 
> int main() { std::cout << 1 << '\t' << 0; return 0; }
> 
> in order to check that  exists.
> But this code still requires -llog4cpp:

Thanks for the explanation but may be I'm missing your point.  The
package installs liblog4cpp.a as well and the dynamic library installs
the according .so file.  So why should the requriement -llog4cpp not
fulfilled?
 
> /tmp/cc41MUW4.o: In function `__static_initialization_and_destruction_0(int, 
> int)':
> 2.cpp:(.text+0x5b): undefined reference to 
> `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
> 2.cpp:(.text+0x70): undefined reference to 
> `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
> collect2: error: ld returned 1 exit status

Isn't this rather a bug in log4cpp?
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#897549: marked as done (desktop-base: FTBFS: /bin/sh: 6: Syntax error: word unexpected (expecting "done"))

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 10:49:27 +
with message-id 
and subject line Bug#897549: fixed in desktop-base 9.0.6
has caused the Debian Bug report #897549,
regarding desktop-base: FTBFS: /bin/sh: 6: Syntax error: word unexpected 
(expecting "done")
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.)


-- 
897549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: desktop-base
Version: 9.0.5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean
>dh_auto_clean
>   make -j8 -Oline clean
> /bin/sh: 6: Syntax error: word unexpected (expecting "done")
> make[1]: *** [Makefile:13: clean-grub] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/desktop-base_9.0.5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: desktop-base
Source-Version: 9.0.6

We believe that the bug you reported is fixed in the latest version of
desktop-base, 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.
Aurélien COUDERC  (supplier of updated desktop-base package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Mar 2018 10:20:26 +0100
Source: desktop-base
Binary: desktop-base
Architecture: source
Version: 9.0.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Desktop Team 
Changed-By: Aurélien COUDERC 
Description:
 desktop-base - common files for the Debian Desktop
Closes: 851893 879297 897549 898150
Changes:
 desktop-base (9.0.6) unstable; urgency=medium
 .
   * First release with package sources migrated to git and
 salsa.debian.org!
 - Updated Vcs-* fields accordingly.
 - Add gbp.conf configuration for native package tag names.
 - Add README.contribute for how to contribute with git / salsa.
 .
   * Improve detection of grub efi to choose default background ratio.
   * Add a debian-theme theme for plymouth themes. This should help switching
 the plymouth theme with the rest of the global theme.
   * Try harder detecting if grub is used as bootloader before calling
 update-grub. (Closes: #851893)
   * Misspelled identifier gloabl should be global in softwaves.script.
 (Closes: #898150)
 .
   * Fix FTBFS due to make >= 4.2 being more picky on typos. (Closes: #897549)
   * Bump debhelper version to 11, fix usage of install in Makefiles in the
 move.
   * Drop versioned pre-depends on dpkg for dpkg-maintscript-helper that has
 been available in dpkg since wheezy.
   * Use debian-desktop@l.d.o as Maintainer instead of Gustavo Franco; removed
 Loïc Minier, Fathi Boudra and Eshat Cakar from uploaders. Thanks to all for
 your past work on the package! (Closes: #879297)
   * Bump Standards-Version to 4.1.4 (VCS-* fields already moved to secure URIs
 with the migration to Salsa).
   * Use Rules-Requires-Root: no
   * Fix Lintian issues:
 - unnecessary-testsuite-autopkgtest-header
 - package-uses-deprecated-source-override-location
Checksums-Sha1:
 a849b7a8b9097db7056f94d6f1a9fec9bf3ca25f 1897 desktop-base_9.0.6.dsc
 93dc59296da256c1f6fb87a9995349385f910808 2302932 desktop-base_9.0.6.tar.xz
 2d6d8f2d0c18bfc29159f000338c635f5124e848 9344 
desktop-base_9.0.6_amd64.buildinfo
Checksums-Sha256:
 3f723242f614a20e2707ec1389fb6b01b733bfeed12053f8476badd6ab3df27b 1897 
desktop-base_9.0.6.dsc
 

Processed: affects perl transition

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user debian-p...@lists.debian.org
Setting user to debian-p...@lists.debian.org (was d...@earth.li).
> usertags 898916 perl-5.28-transition
There were no usertags set.
Usertags are now: perl-5.28-transition.
> affects 898916 src:gnumeric
Bug #898916 [dh-autoreconf] dh-autoreconf: Unconditionally invokes gtkdocize 
without dependency
Added indication that 898916 affects src:gnumeric
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
898916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 898920 with 898501

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 898920 with 898501
Bug #898920 [mailman3-web] mailman3-web: FontAwesome.otf missing
898920 was not blocked by any bugs.
898920 was not blocking any bugs.
Added blocking bug(s) of 898920: 898501
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898501: OpenStack dashboard also affected

[Pierre-Elliott Bécue]

Le jeudi 17 mai 2018 à 14:39:25+0200, Thomas Goirand a écrit :
> Hi,
> 
> Also, the OpenStack dashboard (aka: Horizon) is also affected. I cannot
> be installed, and therefore, all its reverse build-depends are also broken.
> 
> If it's just a mater of fixing a few symlinks, I don't see how hard this
> can be. Please just restore sanity in:
> /usr/share/fonts-font-awesome/fonts/
> 
> and just symlink to the correct location.
> 
> Cheers,

Have a look at the deb file tree.

The truetype font is gone, and the others types has changed in their naming
convention.

The appropriate move would be to ask to upstream where each link should
point to, and fix the package accordingly to their answer.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andrey Rahmatullin]

On Fri, May 18, 2018 at 11:44:02AM +0200, Andreas Tille wrote:
> > Checking for liblog4cpp...
> > 
> > Cannot continue since you don't seem to have log4cpp installed
> > Please install the log4cpp-dev package and run configure again.
> > make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
The reason for this: the configure script compiles the following code:

#include 
#include 
int main() { std::cout << 1 << '\t' << 0; return 0; }

in order to check that  exists.
But this code still requires -llog4cpp:

/tmp/cc41MUW4.o: In function `__static_initialization_and_destruction_0(int, 
int)':
2.cpp:(.text+0x5b): undefined reference to 
`log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
2.cpp:(.text+0x70): undefined reference to 
`log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
collect2: error: ld returned 1 exit status

As the configure script first searches for the header and only then for library
there appears to be no way to fix this apart from searching for some other
header that doesn't require linking the library (if that exists).

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#862373: Bug#862475: The State of the YAML

[Damyan Ivanov]

-=| gregor herrmann, 18.05.2018 11:09:23 +0200 |=-
> Quick status update on the perl YAML modules and the problem of
> instantiating objects:
> 
> * libyaml-syck-perl has $YAML::LoadBlessed since a long time
> * libyaml-libyaml-perl since 0.69 and libyaml-perl since 1.25 have
>   added $YAML::LoadBlessed as well
> * all three by default set it to 1 
> 
> (and YAML::Tiny is not affected as far as I know)
> 
> So I guess we have to consider if we're happy with the ability to
> turn off loading objects and recommend it to consumers and close the
> bugs; or if we want to change the defaults, which means setting
> $YAML::LoadBlessed to 0 in all three packages.

FWIW I'd go with the second option, with a note in debian/NEWS.

For me the cost of the possible breakage (easily fixed) is less than 
the gain of protecting everyone else.

(I don't use the object instantiation functionality)


-- dam

Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andreas Tille]

Control: tags -1 help

On Thu, May 17, 2018 at 11:15:17PM +0200, Dominic Hargreaves wrote:
> Whilst test-rebuilding packages for the next perl release we found
> an unrelated build failure:
> 
> Checking for liblog4cpp...
> 
> Cannot continue since you don't seem to have log4cpp installed
> Please install the log4cpp-dev package and run configure again.
> make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
> 
> The full log is here:
> 
> 
> 
> This seems likely to be caused by the new release of log4cpp 1.1.3-1
> last week.

Most probably that is the reason - but how to solve this?  I admit I
have no idea. :-(

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #898964 [src:mrs] mrs: FTBFS: you don't seem to have log4cpp installed
Added tag(s) help.

-- 
898964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898977: marked as done (libnet-dns-zonefile-fast-perl: FTBFS: You are missing required modules for NSEC3 support)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 09:23:35 +
with message-id 
and subject line Bug#898977: fixed in libnet-dns-zonefile-fast-perl 1.24-4
has caused the Debian Bug report #898977,
regarding libnet-dns-zonefile-fast-perl: FTBFS: You are missing required 
modules for NSEC3 support
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.)


-- 
898977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-dns-zonefile-fast-perl
Version: 1.24-3
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest hh2018

As noticed by ci.debian.net, this package recently started
failing its test suite on sid, also making it fail to build
from source.

 
https://ci.debian.net/packages/libn/libnet-dns-zonefile-fast-perl/unstable/amd64/

This was probably broken by 

-libnet-dns-sec-perl 1.03-1
+libnet-dns-sec-perl 1.08-1

>From my build log:

  You are missing required modules for NSEC3 support, line 1
  ...propagated at /<>/blib/lib/Net/DNS/ZoneFile/Fast.pm 
line 195.
  # Looks like your test exited with 2 just after 10.
  [...]
  Test Summary Report
  ---
  t/rr-dnssec.t (Wstat: 512 Tests: 10 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan.  You planned 38 tests but ran 10.
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libnet-dns-zonefile-fast-perl
Source-Version: 1.24-4

We believe that the bug you reported is fixed in the latest version of
libnet-dns-zonefile-fast-perl, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libnet-dns-zonefile-fast-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2018 11:00:21 +0200
Source: libnet-dns-zonefile-fast-perl
Binary: libnet-dns-zonefile-fast-perl
Architecture: source
Version: 1.24-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 898977
Description: 
 libnet-dns-zonefile-fast-perl - fast BIND-style zonefile parser on top of 
Net::DNS
Changes:
 libnet-dns-zonefile-fast-perl (1.24-4) unstable; urgency=medium
 .
   * Team upload.
   * Add missing (build) dependency on libmime-base32-perl.
 Uncovered by changed (build) dependencies in libnet-dns-sec-perl.
 (Closes: #898977)
Checksums-Sha1: 
 261134332963cce66416ae9696157c06ed1ceff2 2455 
libnet-dns-zonefile-fast-perl_1.24-4.dsc
 c2f22ac4762c12320fffaabb88e0752793c6ab14 5272 
libnet-dns-zonefile-fast-perl_1.24-4.debian.tar.xz
Checksums-Sha256: 
 2f0fb8890dc2e3237f5cf10c9637e4f44da784af14b9150980613e9a6a38b467 2455 
libnet-dns-zonefile-fast-perl_1.24-4.dsc
 6a5bee502f78977a326e54ed14dfb9aafc3e51bd75197b940b7e833807d5e843 5272 
libnet-dns-zonefile-fast-perl_1.24-4.debian.tar.xz
Files: 
 30729c21400eea44c8e4232db706c47e 2455 perl optional 
libnet-dns-zonefile-fast-perl_1.24-4.dsc
 d8b1b1333f72dbc63ad085475c604acc 5272 perl optional 
libnet-dns-zonefile-fast-perl_1.24-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlr+lp1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbrnRAAsFDgmnLxsPBlTeTXwBt21DPu5xY00IEAA2ZswUWBGDeyarw1Bebhiqwz
yErDZOpFxjUXFcWQaFF48EqWTQXfaCtdis3AiSSJdeDja5hn60jQvIm2mitYasnO
68WZbb52N4cISgtkgOpLn/WX1qftDaxu4kJF40eVbAEzGOrqzJN4SYCmKhaR67MG
zC0/xgG2FpAviK8KNwYls1oiK4fdFESS3tUA6EUtDZE8oBm5j1Oliydzs/k6Zs+k
DLsYf++KjM5VGHT8GNd5IPJS2sEl51AULlqk6b+HZ7jyckudke1FWkUC85qW16XT
DKgYFxaZzZBd1H/ZFoiOXO2Nu8nFFb6mQxibq6csMCD+3YxTbG9zgznIOw2teDEQ
crIhrmU6kjCLz0ovYZ5w61ibqWs824kxyTYhuoy946Bt1ylIOLSuoAr5ZhmWtfo2
prrjWiAY8nPclQAN8lwUn7M1VfkZtBQy9f4Le0+lhhLxEKyO3OZF5hWavbYHwgqy
zXXBIUzHBhueSJx9HwrmHheHXxUyWSIFankRlX9VZWVGZEvYnCA8L3wtY94o39Tp
gjrAajlAEbMtNLV1i+W4CAx7AZRZ6u73OKVBzTyeVkV4nlupsHwWJCVQ5F5G60vi

Bug#862373: The State of the YAML

[gregor herrmann]

Quick status update on the perl YAML modules and the problem of
instantiating objects:

* libyaml-syck-perl has $YAML::LoadBlessed since a long time
* libyaml-libyaml-perl since 0.69 and libyaml-perl since 1.25 have
  added $YAML::LoadBlessed as well
* all three by default set it to 1 

(and YAML::Tiny is not affected as far as I know)

So I guess we have to consider if we're happy with the ability to
turn off loading objects and recommend it to consumers and close the
bugs; or if we want to change the defaults, which means setting
$YAML::LoadBlessed to 0 in all three packages.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: Bug #898977 in libnet-dns-zonefile-fast-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #898977 [libnet-dns-zonefile-fast-perl] libnet-dns-zonefile-fast-perl: 
FTBFS: You are missing required modules for NSEC3 support
Added tag(s) pending.

-- 
898977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898977: Bug #898977 in libnet-dns-zonefile-fast-perl marked as pending

[gregoa]

Control: tag -1 pending

Hello,

Bug #898977 in libnet-dns-zonefile-fast-perl 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/perl-team/modules/packages/libnet-dns-zonefile-fast-perl/commit/ca191ad73bf7ef8092be530f636873b7916e6b5d


Add missing (build) dependency on libmime-base32-perl.

Uncovered by changed (build) dependencies in libnet-dns-sec-perl.

Closes: #898977



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/898977

Bug#896921: [Pkg-salt-team] Bug#896921: Bug#896921: Salt 2017.7.5 has been released

[Benjamin Drung]

Am Freitag, den 18.05.2018, 06:51 +0200 schrieb Dirk Heinrichs:
> Am 15.05.2018 um 17:51 schrieb Dirk Heinrichs:
> > Am 15.05.2018 um 10:23 schrieb Benjamin Drung:
> > > It could, but fix was merged after the release of 2017.7.5. So I
> > > am
> > > waiting for the release of of 2017.7.6/2018.3.1 that include the
> > > fix. 
> > 
> > Ah, OK.
> 
> BTW: Which version are you planning to use, then? 2017 or 2018?

2018.3 unless there is a blocking reason.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens

signature.asc
Description: This is a digitally signed message part

Processed: severity of 898165 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 898165 serious
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via 
nfs referrals
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 898165 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # regression in stable
> severity 898165 serious
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via 
nfs referrals
Ignoring request to change severity of Bug 898165 to the same value.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#859841: Bug#891872: transition: curl

[Emilio Pozuelo Monfort]

On 18/05/18 09:24, Jan Niehusmann wrote:
> Hi Emilio,
> 
> On Mon, Apr 23, 2018 at 08:38:30PM +0200, Emilio Pozuelo Monfort wrote:
>> Hmm, I just realised libcurl3 ships libcurl.so.4, so that explains the 
>> conflict.
>> I just found the rationale for this in
>> https://salsa.debian.org/debian/curl/merge_requests/2. That means this will 
>> have
>> to wait until there are no conflicting ongoing transitions. I will ack this 
>> when
>> that time comes.
> 
> What's the best way to stay up to date regarding this transition? Is it
> being discussed on some mailing list / IRC channel? Or shall I just
> monitor the ticket on the BTS at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891872 ?

The latter.

At the moment I'm waiting for the icu transition to move on. Once that happens,
I'll see if we can get this started.

Emilio

Bug#859841: Bug#891872: transition: curl

[Jan Niehusmann]

Hi Emilio,

On Mon, Apr 23, 2018 at 08:38:30PM +0200, Emilio Pozuelo Monfort wrote:
> Hmm, I just realised libcurl3 ships libcurl.so.4, so that explains the 
> conflict.
> I just found the rationale for this in
> https://salsa.debian.org/debian/curl/merge_requests/2. That means this will 
> have
> to wait until there are no conflicting ongoing transitions. I will ack this 
> when
> that time comes.

What's the best way to stay up to date regarding this transition? Is it
being discussed on some mailing list / IRC channel? Or shall I just
monitor the ticket on the BTS at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891872 ?

Jan

Processed: Re: Regression in [v2] nfs: Fix ugly referral attributes ?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream patch
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via 
nfs referrals
Ignoring request to alter tags of bug #898165 to the same tags previously set
> severity -1 grave
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via 
nfs referrals
Severity set to 'grave' from 'important'
> summary -1 0
Summary recorded from message bug 898165 message 80
> outlook -1 0
Outlook recorded from message bug 898165 message 82

-- 
898165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 896941, tagging 877295

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 896941 + pending
Bug #896941 [src:amarok] amarok: libmygpo-qt1 removal and replaced by a Qt5 
based version
Added tag(s) pending.
> tags 877295 + pending
Bug #877295 [src:amarok] amarok build-depends on removed package 
libgpod-nogtk-dev
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
877295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877295
896941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898977: libnet-dns-zonefile-fast-perl: FTBFS: You are missing required modules for NSEC3 support

[Niko Tyni]

Package: libnet-dns-zonefile-fast-perl
Version: 1.24-3
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest hh2018

As noticed by ci.debian.net, this package recently started
failing its test suite on sid, also making it fail to build
from source.

 
https://ci.debian.net/packages/libn/libnet-dns-zonefile-fast-perl/unstable/amd64/

This was probably broken by 

-libnet-dns-sec-perl 1.03-1
+libnet-dns-sec-perl 1.08-1

>From my build log:

  You are missing required modules for NSEC3 support, line 1
  ...propagated at /<>/blib/lib/Net/DNS/ZoneFile/Fast.pm 
line 195.
  # Looks like your test exited with 2 just after 10.
  [...]
  Test Summary Report
  ---
  t/rr-dnssec.t (Wstat: 512 Tests: 10 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan.  You planned 38 tests but ran 10.
 
-- 
Niko Tyni   nt...@debian.org

Bug#853371: marked as done (desktopnova FTBFS: dbus-server-bindings.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 07:19:59 +
with message-id 
and subject line Bug#853371: fixed in desktopnova 0.8.1-1.1
has caused the Debian Bug report #853371,
regarding desktopnova FTBFS: dbus-server-bindings.h: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:desktopnova
Version: 0.8.1-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/desktopnova_0.8.1-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/src/misc && /usr/bin/cc   
-I/<>/obj-x86_64-linux-gnu -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2   -o 
CMakeFiles/desktopnova-xml.dir/xml.c.o   -c /<>/src/misc/xml.c
[  8%] Linking C static library libdesktopnova-xml.a
cd /<>/obj-x86_64-linux-gnu/src/misc && /usr/bin/cmake -P 
CMakeFiles/desktopnova-xml.dir/cmake_clean_target.cmake
cd /<>/obj-x86_64-linux-gnu/src/misc && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/desktopnova-xml.dir/link.txt --verbose=1
/usr/bin/ar qc libdesktopnova-xml.a  CMakeFiles/desktopnova-xml.dir/xml.c.o
/usr/bin/ranlib libdesktopnova-xml.a
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  8%] Built target desktopnova-xml
make -f src/misc/CMakeFiles/desktopnova-module.dir/build.make 
src/misc/CMakeFiles/desktopnova-module.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/misc 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/misc 
/<>/obj-x86_64-linux-gnu/src/misc/CMakeFiles/desktopnova-module.dir/DependInfo.cmake
 --color=
Scanning dependencies of target desktopnova-module
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f src/misc/CMakeFiles/desktopnova-module.dir/build.make 
src/misc/CMakeFiles/desktopnova-module.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  9%] Building C object src/misc/CMakeFiles/desktopnova-module.dir/module.c.o
cd /<>/obj-x86_64-linux-gnu/src/misc && /usr/bin/cc   
-I/<>/obj-x86_64-linux-gnu -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2   -o 
CMakeFiles/desktopnova-module.dir/module.c.o   -c 
/<>/src/misc/module.c
[ 10%] Linking C static library libdesktopnova-module.a
cd /<>/obj-x86_64-linux-gnu/src/misc && /usr/bin/cmake -P 
CMakeFiles/desktopnova-module.dir/cmake_clean_target.cmake
cd /<>/obj-x86_64-linux-gnu/src/misc && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/desktopnova-module.dir/link.txt --verbose=1
/usr/bin/ar qc libdesktopnova-module.a  
CMakeFiles/desktopnova-module.dir/module.c.o
/usr/bin/ranlib libdesktopnova-module.a
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 10%] Built target desktopnova-module
make -f src/dbus/CMakeFiles/desktopnova-dbus.dir/build.make 
src/dbus/CMakeFiles/desktopnova-dbus.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/dbus 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/dbus 
/<>/obj-x86_64-linux-gnu/src/dbus/CMakeFiles/desktopnova-dbus.dir/DependInfo.cmake
 --color=
Scanning dependencies of target desktopnova-dbus
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f 

Bug#866766: marked as done (desktopnova FTBFS: dbus-server-bindings.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 07:19:59 +
with message-id 
and subject line Bug#853371: fixed in desktopnova 0.8.1-1.1
has caused the Debian Bug report #853371,
regarding desktopnova FTBFS: dbus-server-bindings.h: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: desktopnova
Version: 0.8.1-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes desktopnova FTBFS:

https://tests.reproducible-builds.org/debian/history/desktopnova.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/desktopnova.html

...
make[3]: Entering directory '/build/1st/desktopnova-0.8.1/obj-x86_64-linux-gnu'
[ 12%] Building C object 
src/dbus/CMakeFiles/desktopnova-dbus.dir/dbus-server.c.o
cd /build/1st/desktopnova-0.8.1/obj-x86_64-linux-gnu/src/dbus && /usr/bin/cc   
-I/build/1st/desktopnova-0.8.1/obj-x86_64-linux-gnu -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/build/1st/desktopnova-0.8.1/obj-x86_64-linux-gnu/src/dbus   -o 
CMakeFiles/desktopnova-dbus.dir/dbus-server.c.o   -c 
/build/1st/desktopnova-0.8.1/src/dbus/dbus-server.c
/build/1st/desktopnova-0.8.1/src/dbus/dbus-server.c:25:34: fatal error: 
dbus-server-bindings.h: No such file or directory
 #include "dbus-server-bindings.h"
  ^
compilation terminated.
src/dbus/CMakeFiles/desktopnova-dbus.dir/build.make:65: recipe for target 
'src/dbus/CMakeFiles/desktopnova-dbus.dir/dbus-server.c.o' failed
make[3]: *** [src/dbus/CMakeFiles/desktopnova-dbus.dir/dbus-server.c.o] Error 1
--- End Message ---
--- Begin Message ---
Source: desktopnova
Source-Version: 0.8.1-1.1

We believe that the bug you reported is fixed in the latest version of
desktopnova, 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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated desktopnova 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, 16 May 2018 02:49:31 -0400
Source: desktopnova
Binary: desktopnova desktopnova-module-gnome desktopnova-module-xfce 
desktopnova-tray
Architecture: source
Version: 0.8.1-1.1
Distribution: unstable
Urgency: low
Maintainer: Stefan Haller 
Changed-By: Unit 193 
Description:
 desktopnova - utility that changes the wallpaper automatically
 desktopnova-module-gnome - GNOME module for DesktopNova
 desktopnova-module-xfce - Xfce module for DesktopNova
 desktopnova-tray - tray icon for DesktopNova
Closes: 851454 853371
Changes:
 desktopnova (0.8.1-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
 .
   [ Juhani Numminen ]
   * d/p/depend-on-generated-files.patch: Added missing dependency information.
 (Closes: #853371)
 .
   [ Unit 193 ]
   * d/compat, d/control:
 - Bump to DH 9, gains exported build flags which gives us debug symbols.
   * d/control: Build-depend on python-minimal. (Closes: #851454)
Checksums-Sha1:
 035dad5269f2d14161cd4d0285adc99b7ca0b436 2092 desktopnova_0.8.1-1.1.dsc
 b2cb0fc29c4d924219a52659c1cd40a14309cfbe 2948 
desktopnova_0.8.1-1.1.debian.tar.xz
 7933f430b9a830d49592e2c7f6ef12753e6f0091 14960 
desktopnova_0.8.1-1.1_amd64.buildinfo
Checksums-Sha256:
 09169993c287eb2c18862adfad33cd5cc0253d0e1f559a592f1261a3f5456241 2092 
desktopnova_0.8.1-1.1.dsc
 070527766da079dc9ce12c1f8c80468848a69b0679bf3fe530c1826719925b98 2948 
desktopnova_0.8.1-1.1.debian.tar.xz
 f722e40d814e688eded5927c91eb85438c7eebccfcd1ff17ff1d0ad5e3445e2d 14960 
desktopnova_0.8.1-1.1_amd64.buildinfo
Files:
 1cc29149eadc3ca856eb0495b56ba57a 2092 misc optional desktopnova_0.8.1-1.1.dsc
 be3a8d53563d6df787e7f34874308d4d 2948 misc optional 
desktopnova_0.8.1-1.1.debian.tar.xz
 2f77f43f9726a28413a91e91b0376ae4 14960 misc optional 
desktopnova_0.8.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#898976: openjdk-7: 2018 Q2 security update

[Emilio Pozuelo Monfort]

Source: openjdk-7
Version: 7u171-2.6.13-1
Severity: serious
Tags: security

Hi,

As usual, there are a few security issues from 2018 Q2. There's no update
yet, though it's in progress:

http://mail.openjdk.java.net/pipermail/jdk7u-dev/2018-May/010767.html

We can either backport those changes or wait for the release.

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.16.0-1-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

Bug#896254: marked as done (python-sagenb: sagenb fails to import)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 06:19:40 +
with message-id 
and subject line Bug#896254: fixed in sagenb 1.0.1+ds1-3
has caused the Debian Bug report #896254,
regarding python-sagenb: sagenb 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.)


-- 
896254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sagenb
Version: 1.0.1+ds1-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-sagenb importing the module sagenb
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/sagenb/__init__.py", line 3, in 

from . import storage
  File "/usr/lib/python2.7/dist-packages/sagenb/storage/__init__.py", line 3, 
in 
from .filesystem_storage import FilesystemDatastore
  File "/usr/lib/python2.7/dist-packages/sagenb/storage/filesystem_storage.py", 
line 54, in 
from sage.misc.temporary_file import atomic_write
ImportError: No module named sage.misc.temporary_file

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: sagenb
Source-Version: 1.0.1+ds1-3

We believe that the bug you reported is fixed in the latest version of
sagenb, 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.
Ximin Luo  (supplier of updated sagenb 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: Thu, 17 May 2018 23:03:16 -0700
Source: sagenb
Binary: python-sagenb
Architecture: source
Version: 1.0.1+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Ximin Luo 
Description:
 python-sagenb - Standalone Sage Notebook
Closes: 896254
Changes:
 sagenb (1.0.1+ds1-3) unstable; urgency=medium
 .
   * Update Vcs-* fields to salsa.
   * Explain that one cannot "import sagenb" without sage. (Closes: #896254)
Checksums-Sha1:
 b60f42963fc30cbb523044e34cfef5b2e39be06a 2142 sagenb_1.0.1+ds1-3.dsc
 234f4a9cca486beb757007feb5d4066241b9add9 16124 sagenb_1.0.1+ds1-3.debian.tar.xz
 c3a7f84e0a6c741cff1980d74d49465ae9143d94 7881 
sagenb_1.0.1+ds1-3_source.buildinfo
Checksums-Sha256:
 7633d5496107f880743ecae331026ab5de489fa7ca5f135576429da2d80a0319 2142 
sagenb_1.0.1+ds1-3.dsc
 81d60eabe661849cbdcd1d806ba176990b4d961848fb853ea088283a0265f695 16124 
sagenb_1.0.1+ds1-3.debian.tar.xz
 e450907045c3210e52bc7f14afaf3762f3c5210f2c0b886536036a6de108c2f2 7881 
sagenb_1.0.1+ds1-3_source.buildinfo
Files:
 796d43a6e81a00c684d5615efa84e719 2142 math optional sagenb_1.0.1+ds1-3.dsc
 13e22cd0232c2db6d57b150806f70666 16124 math optional 
sagenb_1.0.1+ds1-3.debian.tar.xz
 5b9daca44b64af398473c10167b5424b 7881 math optional 
sagenb_1.0.1+ds1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEENmdIajJtsnZtJVVGhg3vO49lC3kFAlr+bUAVHGluZmluaXR5
MEBkZWJpYW4ub3JnAAoJEIYN7zuPZQt5/bkP/jFLOqVAouWcqSmyzZJFou4APhWV
w0DSzO9SEerWn66ToDwb7YZeLKLj2kpvpAD2nU4FLOuE4wRLrXAropn1rOQKBYyN
6d8+PS7CgxvHdTwfpiDt0eCH5Y4aBswT+cjqcYBL1DlTaX0/3Y63vS/2mDYVHyNm
spnWzEToOFUBCqVo0zZhWw8hdaUJSN9l7Rv5IzMG2Rep+tlAgaL5GbYOM2O+rA5c
5XYYX/Yyq7G80k0ID4nyIxtHvo2Khk+gdbTADsBHMddcIVaMkA/DfqP5ReLof6Rq
MSzSyo6Zk8NeLZxdRJkEYe4w7sWB6ENrevelrqmSQdQIS81/ZMsP8cCfYMrxojpf
c4LtpeuCyww6/LY8c16twbCwnbxR4D3Bc2pAKf0+ynQxSfm9szF5kozEbMHmSh6z
gVm82QQQOZ//Nn+v1AKlTeDByAfsqXvuNzHOMOFZW6qJkSsILzcpWIK3iT+GHVKF
iddByHAdD8/RJA8B1akrCJaHwpDITFQh1h1NbTNUKnc00vko6Dkx+R8zniXoBuTp

Bug#853710: [Pkg-xen-devel] Bug#853710: xen: ftbfs with GCC-7

[Emilio Pozuelo Monfort]

Hi,

On Thu, 11 Jan 2018 23:01:46 +0100 Hans van Kranenburg  wrote:
> Just wanted to let know that during the preparations of upgrading the
> package to Xen 4.10 I have been able to build successfully targeting
> unstable so far.

Any progress there? Can you give a status update?

Cheers,
Emilio

Bug#896203: marked as done (python-flask-oldsessions: flask_oldsessions fails to import)

[Debian Bug Tracking System]

Your message dated Fri, 18 May 2018 06:04:29 +
with message-id 
and subject line Bug#896203: fixed in flask-oldsessions 0.10+git20121007-2
has caused the Debian Bug report #896203,
regarding python-flask-oldsessions: flask_oldsessions 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.)


-- 
896203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-flask-oldsessions
Version: 0.10+git20121007-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-flask-oldsessions importing the module flask_oldsessions
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/flask_oldsessions.py", line 13, in 

from werkzeug.contrib.securecookie import SecureCookie
ImportError: No module named werkzeug.contrib.securecookie

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: flask-oldsessions
Source-Version: 0.10+git20121007-2

We believe that the bug you reported is fixed in the latest version of
flask-oldsessions, 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.
Ximin Luo  (supplier of updated flask-oldsessions 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: Thu, 17 May 2018 22:48:54 -0700
Source: flask-oldsessions
Binary: python-flask-oldsessions
Architecture: source
Version: 0.10+git20121007-2
Distribution: unstable
Urgency: medium
Maintainer: Ximin Luo 
Changed-By: Ximin Luo 
Description:
 python-flask-oldsessions - Provides a session class that works like the one 
before 0.10
Closes: 896203
Changes:
 flask-oldsessions (0.10+git20121007-2) unstable; urgency=medium
 .
   * Add missing dependency. (Closes: #896203)
Checksums-Sha1:
 95278a5d8be3dbae029fd20733df92f297bd6ced 1979 
flask-oldsessions_0.10+git20121007-2.dsc
 cb8651be83289166d49f2240c883ac70dec6bdc5 1516 
flask-oldsessions_0.10+git20121007-2.debian.tar.xz
 f192e3b2dce76f21b6ed82774da94b4b1c344c86 6108 
flask-oldsessions_0.10+git20121007-2_source.buildinfo
Checksums-Sha256:
 6569541bd7d175e6b299add073757dda026cabb1ae266380f88007641c7f6df3 1979 
flask-oldsessions_0.10+git20121007-2.dsc
 e71f614504695776829690644be7f0ab374d1f2ee5eb28f40c7926e65985f28a 1516 
flask-oldsessions_0.10+git20121007-2.debian.tar.xz
 61670cae27ee83e3c55b27f389fdcfc47ace8077d09a44106bb77066e9104140 6108 
flask-oldsessions_0.10+git20121007-2_source.buildinfo
Files:
 91f4e46b46fb03317d0d6dbad74e4363 1979 python optional 
flask-oldsessions_0.10+git20121007-2.dsc
 b3eb41ba4c0649e5237e630f38c878e1 1516 python optional 
flask-oldsessions_0.10+git20121007-2.debian.tar.xz
 1102a44796b945d19cc2741fbf80565c 6108 python optional 
flask-oldsessions_0.10+git20121007-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEENmdIajJtsnZtJVVGhg3vO49lC3kFAlr+aWsVHGluZmluaXR5
MEBkZWJpYW4ub3JnAAoJEIYN7zuPZQt5M2gP/R1uNMg4U7TdrLPikf4RZyedEzyD
ulw8xF9TncVuGE7xk3eqYeOEIgocTSsFH1yLOTQ9Ecp572G4tx55eQqRjJpgFI9u
iinKybjzb1INpNpiVd+QSpoTIcsxFQIq8Kxu+i7pKIGXnslUrhqbHimRnJP1SaT/
Zo/qfoM9egK/beDWdejRxpakTwyq6Rn0XmCy1qV+VVwJR2GlAY/E60WtYD+q75tD
r3bzvBwqzsIPed2GQAFDHuX7a5uHxsxIQczUzJTEaU08rnuWyvFl949G/IpsuuJi
IRTQ2WNl91ZBPK9E3S4rC6W9iYHdCP7iQ5IFiq43bS7LmupM45r6eg90CGa4YiIx
QBbpGfbyf5vCVsvhovucR7ElRIXNKfcEVVPxVVeTbdN3LTKIq4+vCFrVBWhWv/SU
AEgX8knt7T3zMUt7WSH0FfsbglG3kN2woLayk2c0Z3P/49WMpKsOI2qHkQ+CQ7CS
foSf5N0S43j56ynRKWCXwmhmx8y9RxXPnGdOnjjzEed9HE9cIvd66QPDccYihsj8