Bug#882141: closed by Scott Kitterman <sc...@kitterman.com> (Bug#882141: fixed in postfix 3.2.4-1)

2018-02-22 Thread Scott Kitterman
On Wed, 21 Feb 2018 19:56:24 +0100 Bastian Blank  wrote:
> On Sun, Feb 11, 2018 at 11:11:16PM -0500, Scott Kitterman wrote:
> > Would you please check that your /lib/systemd/system/postfix@.service has:
> > 
> > After=network-online.target nss-lookup.target
> > Wants=network-online.target
> > 
> > At least as I understand it, that's supposed to make sure the network is 
up 
> > before postfix starts.
> 
> Please tell me how this would change the environment the _generator_ is
> running in.

Maybe I've been away from this bug too long and I need to go restudy how the 
generator works again, but I think the generator running is triggered by 
postfix starting, so (my assumption is) this would cause the starting to be 
delayed until after the network is available which would also make the 
generator run when a network in place.

Scott K



Processed: bug 891151 is forwarded to https://gitlab.dune-project.org/staging/dune-uggrid/merge_requests/88

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 891151 
> https://gitlab.dune-project.org/staging/dune-uggrid/merge_requests/88
Bug #891151 {Done: Adrian Bunk } [src:dune-uggrid] dune-uggrid 
FTBFS with cmake 3.10.2-1
Set Bug forwarded-to-address to 
'https://gitlab.dune-project.org/staging/dune-uggrid/merge_requests/88'.
> thanks
Stopping processing here.

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



Bug#891150: drupal7: SA-CORE-2018-001: Several vulnerabilities

2018-02-22 Thread Gunnar Wolf
Salvatore Bonaccorso dijo [Thu, Feb 22, 2018 at 08:46:30PM +0100]:
> There was a new Drupal security advisory at
> 
> https://www.drupal.org/sa-core-2018-001
> 
> where several issues affect as well drupal7.
> 
>  * JavaScript cross-site scripting prevention is incomplete - Critical -
>Drupal 7 and Drupal 8
>  * Private file access bypass - Moderately Critical - Drupal 7
>  * jQuery vulnerability with untrusted domains - Moderately Critical
>- Drupal 7
>  * External link injection on 404 pages when linking to the current page
>- Less Critical - Drupal 7

I intend to work on this tomorrow; have been quite time-constrained,
so any help will be welcome. But I intend to upload a new version for,
at least, unstable and stable-security tomorrow afternoonish (@mex).

Thanks for the heads-up.



Bug#891178: marked as done (libclojure1.8-java and libclojure-java: error when trying to install together)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2018 03:19:53 +
with message-id 
and subject line Bug#891178: fixed in clojure 1.9.0~alpha15-2
has caused the Debian Bug report #891178,
regarding libclojure1.8-java and libclojure-java: error when trying to install 
together
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.)


-- 
891178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclojure-java,libclojure1.8-java
Version: libclojure-java/1.9.0~alpha15-1
Version: libclojure1.8-java/1.8.0-4
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2018-02-23
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


E: Sub-process false returned an error code (1)
E: Prior errors apply to 
/var/cache/apt/archives/libclojure-java_1.9.0~alpha15-1_all.deb
E: Prior errors apply to 
/var/cache/apt/archives/libclojure1.8-java_1.8.0-4_all.deb
debconf: apt-extracttemplates failed: No such file or directory
Selecting previously unselected package libjsr166y-java.
(Reading database ... 10982 files and directories currently installed.)
Preparing to unpack .../libjsr166y-java_1.7.0-2_all.deb ...
Unpacking libjsr166y-java (1.7.0-2) ...
Selecting previously unselected package libclojure-java.
Preparing to unpack .../libclojure-java_1.9.0~alpha15-1_all.deb ...
Unpacking libclojure-java (1.9.0~alpha15-1) ...
Selecting previously unselected package libclojure1.8-java.
Preparing to unpack .../libclojure1.8-java_1.8.0-4_all.deb ...
Unpacking libclojure1.8-java (1.8.0-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/libclojure1.8-java_1.8.0-4_all.deb (--unpack):
 trying to overwrite '/usr/share/java/clojure.jar', which is also in package 
libclojure-java 1.9.0~alpha15-1
Errors were encountered while processing:
 /var/cache/apt/archives/libclojure1.8-java_1.8.0-4_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/java/clojure.jar

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: clojure
Source-Version: 1.9.0~alpha15-2

We believe that the bug you reported is fixed in the latest version of
clojure, 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.
Elana Hashman  (supplier of updated clojure 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, 22 Feb 2018 21:48:26 -0500
Source: clojure
Binary: clojure libclojure-java
Architecture: source all
Version: 1.9.0~alpha15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Elana Hashman 
Description:
 

Processed: your mail

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 891026 zfs-linux
Bug #891026 [src:zfs-linux] zfs-dkms: Incompatible with kernel 4.15
Bug reassigned from package 'src:zfs-linux' to 'zfs-linux'.
Ignoring request to alter found versions of bug #891026 to the same values 
previously set
Ignoring request to alter fixed versions of bug #891026 to the same values 
previously set
> merge 889795 891026
Bug #889795 [zfs-linux] [zfs-linux] Pleaes Package 0.7.6
Bug #891026 [zfs-linux] zfs-dkms: Incompatible with kernel 4.15
Merged 889795 891026
>
End of message, stopping processing here.

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



Processed (with 1 error): your mail

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 891026 src:zfs-linux
Bug #891026 [zfs-dkms] zfs-dkms: Incompatible with kernel 4.15
Bug reassigned from package 'zfs-dkms' to 'src:zfs-linux'.
No longer marked as found in versions zfs-linux/0.7.5-1.
Ignoring request to alter fixed versions of bug #891026 to the same values 
previously set
> merge 889795 891026
Bug #889795 [zfs-linux] [zfs-linux] Pleaes Package 0.7.6
Unable to merge bugs because:
package of #891026 is 'src:zfs-linux' not 'zfs-linux'
Failed to merge 889795: Did not alter merged bugs.

>
End of message, stopping processing here.

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



Bug#891178: libclojure1.8-java and libclojure-java: error when trying to install together

2018-02-22 Thread Ralf Treinen
Package: libclojure-java,libclojure1.8-java
Version: libclojure-java/1.9.0~alpha15-1
Version: libclojure1.8-java/1.8.0-4
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2018-02-23
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


E: Sub-process false returned an error code (1)
E: Prior errors apply to 
/var/cache/apt/archives/libclojure-java_1.9.0~alpha15-1_all.deb
E: Prior errors apply to 
/var/cache/apt/archives/libclojure1.8-java_1.8.0-4_all.deb
debconf: apt-extracttemplates failed: No such file or directory
Selecting previously unselected package libjsr166y-java.
(Reading database ... 10982 files and directories currently installed.)
Preparing to unpack .../libjsr166y-java_1.7.0-2_all.deb ...
Unpacking libjsr166y-java (1.7.0-2) ...
Selecting previously unselected package libclojure-java.
Preparing to unpack .../libclojure-java_1.9.0~alpha15-1_all.deb ...
Unpacking libclojure-java (1.9.0~alpha15-1) ...
Selecting previously unselected package libclojure1.8-java.
Preparing to unpack .../libclojure1.8-java_1.8.0-4_all.deb ...
Unpacking libclojure1.8-java (1.8.0-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/libclojure1.8-java_1.8.0-4_all.deb (--unpack):
 trying to overwrite '/usr/share/java/clojure.jar', which is also in package 
libclojure-java 1.9.0~alpha15-1
Errors were encountered while processing:
 /var/cache/apt/archives/libclojure1.8-java_1.8.0-4_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/java/clojure.jar

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.



Bug#890407: marked as done (milkytracker: various buffer overflows possibly leading to remote code execution)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2018 00:39:27 +
with message-id 
and subject line Bug#890407: fixed in milkytracker 1.01.00+dfsg-2
has caused the Debian Bug report #890407,
regarding milkytracker: various buffer overflows possibly leading to remote 
code execution
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.)


-- 
890407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: milkytracker
Severity: grave
Tags: security upstream

Forwarding this bug sent to me by Johannes Schultz. It sounds bad. I
have not investigated it (and I don't know if it affects the pre-1.0
version in stable or not)

 Forwarded Message 
Subject: MilkyTracker - critical patches
Date: Wed, 14 Feb 2018 13:39:45 +0100
From: Johannes Schultz 
To: jcowg...@debian.org

Hi James,
I have recently fixed a bunch of very obvious and at the same time very
dangerous bugs in various module loaders in MilkyTracker, most of them
leading to out-of-bond writes both on the heap and stack. I think most
of them would be suitable for remote code execution.
You can find them here:
https://github.com/milkytracker/MilkyTracker/commit/6f7922616f31e5ceddd6f346cfc7f5d61a2f7683
You will also see the individual commits in the commit timeline around
October 2017.
I don't know if there is any immediate release planned by Deltafire, so
I recommend you to update the Debian packages based on those patches ASAP.
The individual diffs can also be found here:
https://sagagames.de/stuff/mt-patches.zip
They should apply to all MilkyTracker versions supported by the various
Debian releases, not just 1.01.00.

Best regards,
Johannes / OpenMPT Dev (and occasionall MilkyTracker bugfixer ;)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: milkytracker
Source-Version: 1.01.00+dfsg-2

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated milkytracker 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, 22 Feb 2018 23:47:13 +
Source: milkytracker
Binary: milkytracker
Architecture: source
Version: 1.01.00+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Team 
Changed-By: James Cowgill 
Description:
 milkytracker - music creation tool inspired by Fast Tracker 2
Closes: 890407
Changes:
 milkytracker (1.01.00+dfsg-2) unstable; urgency=high
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ James Cowgill ]
   * debian/compat:
 - Use debhelper compat 11.
   * debian/control:
 - Set maintainer to debian-multimedia@l.d.o.
 - Set Rules-Requires-Root: no.
 - Bump standards to 4.1.3.
   * debian/patches:
 - Apply upstream patches to fix various buffer overflows.
   Thanks to Johannes Schultz (Closes: #890407)
Checksums-Sha1:
 dd9bb78ddd9bd4538b46e474338e64726fccafb7 2210 milkytracker_1.01.00+dfsg-2.dsc
 a6f1326fd49131fbafb576a0861bdc3edeb23d62 10804 
milkytracker_1.01.00+dfsg-2.debian.tar.xz
 98792c89894562a3aab9874efa513804806462ca 12261 
milkytracker_1.01.00+dfsg-2_source.buildinfo
Checksums-Sha256:
 4184d05a3c50ab99a0f16dceb29e5e125ff94706e27451625b76b29fc82c2301 2210 
milkytracker_1.01.00+dfsg-2.dsc
 6c1186ace963acfa9d78e03c3bb55a5ba2a7d03e45f1e6ad644a30da60f28547 10804 
milkytracker_1.01.00+dfsg-2.debian.tar.xz
 a868874a2c57d83df51f62e1c3075af5fb6cfbcb098438ffec85d71670ea51b2 12261 
milkytracker_1.01.00+dfsg-2_source.buildinfo
Files:
 727990a7ca507937ffe022c830928b0e 2210 sound optional 
milkytracker_1.01.00+dfsg-2.dsc
 1d649ff6700022da9b101adbf0d49455 10804 sound optional 
milkytracker_1.01.00+dfsg-2.debian.tar.xz
 c4be414371267f9abe7383df31c65437 12261 sound optional 
milkytracker_1.01.00+dfsg-2_source.buildinfo


Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

2018-02-22 Thread Ben Finney
Control: tags -1 + unreproducible

On 16-Feb-2018, Ben Finney wrote:

> What I need is some simple script that I can run in a minimal Debian
> environment, first to show the behaviour in this package and, after
> making changes to the package, then to test whether the behaviour is
> correct.

Lacking that, I am unable to reproduce the reported behaviour.

-- 
 \   “If you make people think they're thinking, they'll love you; |
  `\ but if you really make them think, they'll hate you.” —Donald |
_o__) Robert Perry Marquis |
Ben Finney 


signature.asc
Description: PGP signature


Processed: Re: Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + unreproducible
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
Added tag(s) unreproducible.

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



Bug#888928: gource FTBFS with libglm-dev 0.9.9~a2-1

2018-02-22 Thread Andrew Caudwell
This bug was triggered by the libglm-dev package being updated to an alpha
version of glm 0.9.9 a2. I believe this was done to fix an issue compiling
with GCC 7.3 present in the current release 0.9.8.5. While it's relatively
trivial for me to add the extra define to get it to get my software to
compile, this version of GLM also includes a major change of behavior by
removing the default initialization of vector, matrix and quaternion types.
In the case of gource and logstalgia, there is quite a bit of code relying
on the previous behavior so this has created a number of uninitialized
value bugs. Any other software using libglm-dev that depends on this
behavior will have the same issue.

I've raised a bug with the upstream regarding this change:
https://github.com/g-truc/glm/issues/735

IMO the best solution is for libglm-dev to continue to package the current
release 0.9.8.5 but apply a patch fixing the GCC compilation issue.

On Wed, Jan 31, 2018 at 10:23 PM, Adrian Bunk  wrote:

> Source: gource
> Version: 0.47-1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/gource.html
>
> ...
> In file included from /usr/include/glm/gtx/norm.hpp:18:0,
>  from src/core/vectors.h:37,
>  from src/core/gl.h:27,
>  from src/core/texture.h:34,
>  from src/gource_settings.h:23,
>  from src/user.h:21,
>  from src/action.h:21,
>  from src/action.cpp:18:
> /usr/include/glm/gtx/quaternion.hpp:23:3: error: #error "GLM:
> GLM_GTX_quaternion is an experimental extension and may change in the
> future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you
> really want to use it."
>  # error "GLM: GLM_GTX_quaternion is an experimental extension and may
> change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including
> it, if you really want to use it."
>^
>


Bug#889533: leiningen-clojure build dependencies need 1.8 adjustments

2018-02-22 Thread Elana Hashman
Thanks for reopening this! Not sure why the clojure1.8 changelog marked
it as done, as it specified the issues were only partially addressed. I
will be uploading all the bd fixes for leiningen and its multitude of
dependencies in the next day or two :)

- e


signature.asc
Description: Digital signature


Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

2018-02-22 Thread Nicholas D Steeves
On Mon, Jan 15, 2018 at 02:20:28PM +, Dimitri John Ledkov wrote:
> On 15 January 2018 at 00:27, Cyril Brulebois  wrote:
> > Hi,
> >
> > Cyril Brulebois  (2018-01-12):
> >> Your package is no longer installable (along with its rev-dep
> >> partman-btrfs) because it now depends on libzstd1, which isn't
> >> a udeb.
> >
> > It seems zstd is only an option for btrfs-progs, and I've just confirmed
> > that setting --disable-zstd on the dh_auto_configure line lets btrfs-progs
> > build just fine, without the libzstd1 dependency. As far as I can tell,
> > there's no absolute need for this feature in d-i, and we could consider
> > building the udeb without zstd support, instead of requesting the addition
> > of a libzstd1-udeb. What do you think?
> >
> 
> That's an oversight on my part. From the recovery point of view, it
> would be desired to have zstd compression support built-into
> btrfs-progs-udeb such that one can use d-i recovery mode to
> backup/restore btrfs filesystems with zstd compression.
> 
> -- 
> Regards,
> 
> Dimitri.

Hi Cyril! 

I agree that it's not essential for d-i; although, it's worth
mentioning that zstd seems like it will more likely satisfy users who
are coming from zfs' "lz4 compression is usually beneficial" school of
thought than lzo will.

Dmitri, does btrfs send/receive actually require userspace libzstd?
Or is it needed for defrag? (rewrites files, and also optionally
applies, removes, or changes compression type) I'm guessing that
btrfs-check requires it. (check --repair is, broadly speaking,
equivalent to 'fsck.ext4 -p')

The worst-case d-i bloat for an official arch seems to be 193.4kB for
i386, before compression.  Would you please 'reassign -1 libzstd' if
you agree that Debian's rescue mode should support cloning/restoring
subvolumes with compressed files, and/or being able to repair the
(unmounted) rootfs?  It seems strange that buster's initramfs has this
functionality and that rescue mode doesn't.  Alternatively, the btrfs
binary in the udeb could be statically linked...

Thanks,
Nicholas


signature.asc
Description: PGP signature


Processed: Bug #890407 in milkytracker marked as pending

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #890407 [milkytracker] milkytracker: various buffer overflows possibly 
leading to remote code execution
Added tag(s) pending.

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



Bug#890407: Bug #890407 in milkytracker marked as pending

2018-02-22 Thread jcowgill
Control: tag -1 pending

Hello,

Bug #890407 in milkytracker reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/milkytracker/commit/b1ba8ce953f6c4dfd680bcd79524d64b38fa5f22


Apply upstream patches to fix various buffer overflows

Thanks: Johannes Schultz
Closes: #890407



(this message was generated automatically)
-- 
Greetings



Bug#891026: [zfs-dkms]

2018-02-22 Thread Antonio Russo
Control: severity 889795 serious
Control: merge 889795 891026

I've raised the severity of the existing bug given the presence of Linux 4.15
in the repository.

Both spl and zfs packages are pulled into, and merged with, the existing
Debian packaging in

https://github.com/aerusso/pkg-zfsonlinux-zfs
and
https://github.com/aerusso/pkg-zfsonlinux-spl

in branch pulls/proposed-0.7.6. This also includes some other compatibility
fixes from zfsonlinux master (890576).



Processed (with 1 error): [zfs-dkms]

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> severity 889795 serious
Bug #889795 [zfs-linux] [zfs-linux] Pleaes Package 0.7.6
Severity set to 'serious' from 'wishlist'
> merge 889795 891026
Bug #889795 [zfs-linux] [zfs-linux] Pleaes Package 0.7.6
Unable to merge bugs because:
package of #891026 is 'zfs-dkms' not 'zfs-linux'
Failed to merge 889795: Did not alter merged bugs.


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



Bug#873191: marked as done (ffdiaporama: please switch to ffmpeg)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 23:35:36 +
with message-id 
and subject line Bug#873191: fixed in ffdiaporama 2.1+dfsg-1
has caused the Debian Bug report #873191,
regarding ffdiaporama: please switch to ffmpeg
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.)


-- 
873191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libav-tools
Version: 7:3.2.5-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package libav-tools for Buster, as it has been 
released with Stretch.

Thanks for maintaining ffmpeg!


-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: ffdiaporama
Source-Version: 2.1+dfsg-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated ffdiaporama 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, 22 Feb 2018 21:40:49 +
Source: ffdiaporama
Binary: ffdiaporama ffdiaporama-data
Architecture: source
Version: 2.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 ffdiaporama - Movie creator from photos and video clips
 ffdiaporama-data - Data files for ffDiaporama
Closes: 731777 873191 874874 888354
Changes:
 ffdiaporama (2.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ James Cowgill ]
   * New upstream release. (Closes: #731777)
   * Remove background resources. These resources are not released under a DFSG
 free license.
 .
   * debian/compat:
 - Use debhelper compat 11.
   * debian/control
 - Set maintainer to debian-multimedia@l.d.o.
 - Build depend on qtbase5-dev instead of qt5-default.
 - Drop dependency on ffmpeg.
 - Drop shlibs:Depends from ffdiaporama-data.
 - Bump standards version to 4.1.3.
 - Set Rules-Requires-Root: no.
 - Mark ffdiaporama-data as Multi-Arch foreign.
   * debian/copyright:
 - Update for 2.1.
   * debian/ffdiaporama-data.links:
 - Add a dummy background to prevent segfaults.
   * debian/patches:
 - Rename and refresh 01_fix-hardening-flags.patch.
 - Update and split up ffmpeg patches.
 - Add patch to fix uninitialized variable valgrind warnings.
 - Add patch to make LibAvLogCallback thread safe.
 - Add patch to enable rsc subproject.
 - Add patch to fix 64-bit architecture detection.
 - Add patch to prevent phoning home for updates.
 - Add patch to fix FTBFS with FFmpeg 4.0. (Closes: #888354)
   * debian/rules:
 - Remove DH_VERBOSE comment from debian/rules.
 - Install upstream changelog.
 - Export QT_SELECT in debian/rules.
   * debian/watch:
 - Update debian/watch to new source location.
 .
   [ Rico Tzschichholz ]
   * Update fix_hardening_flags.patch
   * Add ffmpeg_2.8.patch for ffmpeg 2.8+ support.
   * Install application icon. (LP: #1280820)
   * Use ffmpeg >= 2.8 and QT5. (Closes: #873191, #874874)
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/control: Set Vcs-* to salsa.debian.org
Checksums-Sha1:
 74aec22f5bc84a6e4f6a80afd37207a0d659597c 2674 ffdiaporama_2.1+dfsg-1.dsc
 6620e077ad91b4b3ec421b911198d458d8c453d4 9806678 
ffdiaporama_2.1+dfsg.orig-rsc.tar.gz
 eb2f3f64e89b7480801fa21b2e6e410977b22695 16063604 
ffdiaporama_2.1+dfsg.orig.tar.gz
 458c0b83587f49c2b8b3bb5874f9810b95b5191f 18328 
ffdiaporama_2.1+dfsg-1.debian.tar.xz
 8d877092fbf5abf5ebb64b93f92df8b0809f5fb5 16682 
ffdiaporama_2.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 48eb85afcd359fe8cf4a72634727b1be7808d42828e75f9dc9aa73db4f2d1818 2674 
ffdiaporama_2.1+dfsg-1.dsc
 e4fda2a2eba8d0b297fcb074fcc3974a31ee447c8b0fd4d7f364513a667666e3 

Bug#891133: marked as done (gnome-maps: make distclean deletes lib/maps-enum-types.[ch], but they cannot be regenerated)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 23:36:23 +
with message-id 
and subject line Bug#891133: fixed in gnome-maps 3.27.90-2
has caused the Debian Bug report #891133,
regarding gnome-maps: make distclean deletes lib/maps-enum-types.[ch], but they 
cannot be regenerated
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.)


-- 
891133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-maps
Version: 3.27.90-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gnome-maps/experimental FTBFS twice in a row. The first build succeeds,
subsequent 'debian/rules clean' calls 'make distclean' which deletes
lib/maps-enum-types.[ch], but these two files cannot be regenerated
for the second build since lib/maps-enum-types.[ch].template are missing.

[...]
   dh_auto_build
make -j4
make[1]: Entering directory '/build/gnome-maps-3.27.90'
Making all in lib
make[2]: Entering directory '/build/gnome-maps-3.27.90/lib'
(glib-mkenums   \
--template ./maps-enum-types.h.template \
maps-contact-store.h maps-contact.h mapsintl.h maps.h 
maps-file-tile-source.h maps-osm.h maps-osm-changeset.h maps-osm-node.h 
maps-osm-object.h maps-osm-relation.h maps-osm-way.h 
maps-osm-oauth-proxy-call.h > xgen-maps-enum-types.h && mv -f 
xgen-maps-enum-types.h maps-enum-types.h)
Traceback (most recent call last):
  File "/usr/bin/glib-mkenums", line 342, in 
read_template_file(options.template)
  File "/usr/bin/glib-mkenums", line 272, in read_template_file
ifile = io.open(file, encoding="utf-8", errors="replace_and_warn")
FileNotFoundError: [Errno 2] No such file or directory: 
'./maps-enum-types.h.template'
Makefile:814: recipe for target 'maps-enum-types.h' failed
make[2]: *** [maps-enum-types.h] Error 1
make[2]: Leaving directory '/build/gnome-maps-3.27.90/lib'
Makefile:442: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/build/gnome-maps-3.27.90'
dh_auto_build: make -j4 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas


gnome-maps_3.27.90-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gnome-maps
Source-Version: 3.27.90-2

We believe that the bug you reported is fixed in the latest version of
gnome-maps, 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.
Simon McVittie  (supplier of updated gnome-maps 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, 22 Feb 2018 19:18:13 +
Source: gnome-maps
Binary: gnome-maps
Architecture: source
Version: 3.27.90-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Description:
 gnome-maps - map application for GNOME
Closes: 891133
Changes:
 gnome-maps (3.27.90-2) experimental; urgency=medium
 .
   * Team upload
   * d/p/dist/Add-missing-template-files-for-enum-types.patch:
 Add missing lib/maps-enum-types.[ch].template, from upstream git
 (Closes: #891133)
   * d/copyright: Add copyright, license details of third-party
 JavaScript noticed while fixing upstream distcheck target
Checksums-Sha1:
 40216e06065ae9e77f80c189139355da6a7db045 2354 gnome-maps_3.27.90-2.dsc
 6acbd45ea4a0bb3dce2b1ea99a5b2f9840fde4df 5696 
gnome-maps_3.27.90-2.debian.tar.xz
 b5527118a3a820f199cbe7f657d52fbfeda23e63 15865 
gnome-maps_3.27.90-2_source.buildinfo
Checksums-Sha256:
 0937392d0a5ffe5a25a2046213abde631b733864d609ee776220025e4d566341 2354 
gnome-maps_3.27.90-2.dsc
 db02f460646817a20f13967250871dc8bfa3ef776af88af1a6ed0952b4ef1fe3 5696 
gnome-maps_3.27.90-2.debian.tar.xz
 fe9757eb086a6028245241f80955c6a0a3e05c3a9a92a0276c6b089a9d91010e 15865 

Bug#885197: marked as done (guile-2.2: Fails to build from source on amd64)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 18:14:55 -0500
with message-id 

and subject line Re: guile-2.2: Fails to build from source on amd64
has caused the Debian Bug report #885197,
regarding guile-2.2: Fails to build from source on amd64
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.)


-- 
885197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guile-2.2
Version: 2.2.2+2-1
Severity: serious

guile-2.2 fails to build from source on amd64 as seen in the
reproducibility builder (where it has never built from source on
amd64):
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-2.2.html

and in Ubuntu:
https://launchpad.net/ubuntu/+source/guile-2.2/2.2.2+2-1/+build/13665026

See also https://.launchpad.net/bugs/1734575

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.2.3+1-2

I'll go ahead and close this one.

Ubuntu has a workaround for arm64…

Thanks,
Jeremy Bicha--- End Message ---


Bug#891172: libhmsbeagle: please drop the spurious B-D: libpoclu-dev

2018-02-22 Thread Andreas Beckmann
Source: libhmsbeagle
Version: 2.1.2+20160831-5
Severity: serious
Tags: sid buster

Hi,

please drop the spurious B-D on libpoclu-dev, the libpoclu-dev and
libpoclu2 packages will be dropped in pocl 1.1.

Maybe you want/need to use
  ocl-icd-opencl-dev | opencl-dev
instead?


Andreas



Processed: leiningen-clojure build dependencies need 1.8 adjustments

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> reopen -1
Bug #889533 {Done: Rob Browning } 
[src:leiningen-clojure] leiningen-clojure FTBFS with libclojure-java 
1.9.0~alpha15-1
'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 clojure1.8/1.8.0-4.

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



Bug#889533: leiningen-clojure build dependencies need 1.8 adjustments

2018-02-22 Thread Adrian Bunk
Control: reopen -1

The leiningen-clojure build dependencies need adjustments
to use 1.8 packages.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#891163: kstars FTBFS: dh_install: Cannot find "usr/lib/*/libexec/kauth/kauth_kstars_helper"

2018-02-22 Thread Adrian Bunk
Source: kstars
Version: 4:17.08.3-2
Severity: serious

Some recent change in unstable makes kstars FTBFS:

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

...
dh_install  
dh_install: Cannot find (any matches for) 
"usr/lib/*/libexec/kauth/kauth_kstars_helper" (tried in ., debian/tmp)

dh_install: kstars missing files: usr/lib/*/libexec/kauth/kauth_kstars_helper
dh_install: missing files, aborting
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_install_dh_install] Error 25
make[1]: Leaving directory '/build/1st/kstars-17.08.3'
make: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: 
debian/dhmk_install] Error 2



Bug#891160: libgaminggear FTBFS with cmake 3.10

2018-02-22 Thread Adrian Bunk
Source: libgaminggear
Version: 0.15.1-6
Severity: serious
Tags: patch

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

...
dh_missing --fail-missing
dh_missing: usr/share/cmake-3.10/Modules/FindGAMINGGEAR0.cmake exists in 
debian/tmp but is not installed to anywhere
dh_missing: missing files, aborting


Fix:

--- debian/not-installed.old2018-02-22 13:51:54.803336922 +
+++ debian/not-installed2018-02-22 13:53:08.511336219 +
@@ -1,2 +1,2 @@
 usr/lib/x86_64-linux-gnu/gaminggear_plugins
-usr/share/cmake-3.9/Modules/FindGAMINGGEAR0.cmake
+usr/share/cmake-*/Modules/FindGAMINGGEAR0.cmake



Bug#891159: usbauth-notifier: Install fails with "preinst: db_stop: not found" and leave package in bad inconsistent state

2018-02-22 Thread Yannick Roehlly
Package: usbauth-notifier
Version: 1.0~git20180119-1
Severity: grave
Justification: renders package unusable

Hi,

Installing usbauth-notifier fails with:

/var/lib/dpkg/tmp.ci/preinst: 15: /var/lib/dpkg/tmp.ci/preinst: db_stop: not 
found

Apparently, ". /usr/share/debconf/confmodule" is missing from the preinst (and
others) script. See bug #443823 for a similar problem.

I used severity "grave" because this leaves the package in "bad inconsistent
state" difficult to handle without having a corrected package.

Yannick

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information



Bug#891156: mutter: Incomplete debian/copyright?

2018-02-22 Thread Chris Lamb
Source: mutter
Version: 3.27.91-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi,

I just ACCEPTed mutter from NEW but noticed it was missing 
attribution in debian/copyright for at least Endless Mobile
(for src/wayland/meta-wayland-region.c) but others in that
dir too.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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



Bug#891157: r-cran-animation: Incomplete debian/copyright?

2018-02-22 Thread Chris Lamb
Source: r-cran-animation
Version: 2.5+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Tille 

Hi,

I just ACCEPTed r-cran-animation from NEW but noticed it was missing 
attribution in debian/copyright for at least Brent Ertz for 
inst/misc/scianimator/css/scianimator.blue.css.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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



Bug#891150: drupal7: SA-CORE-2018-001: Several vulnerabilities

2018-02-22 Thread Salvatore Bonaccorso
Control: clone -1 -2 -3 -4
Control: retitle -1 drupal7: SA-CORE-2018-001: JavaScript cross-site scripting 
prevention is incomplete
Control: retitle -2 drupal7: SA-CORE-2018-001: Private file access bypass
Control: retitle -3 drupal7: SA-CORE-2018-001: jQuery vulnerability with 
untrusted domains
Control: retitle -4 drupal7: SA-CORE-2018-001: External link injection on 404 
pages when linking to the current page

Hi

On Thu, Feb 22, 2018 at 08:46:30PM +0100, Salvatore Bonaccorso wrote:
> Source: drupal7
> Version: 7.56-1
> Severity: grave
> Tags: security upstream
> 
> Hi
> 
> There was a new Drupal security advisory at
> 
> https://www.drupal.org/sa-core-2018-001
> 
> where several issues affect as well drupal7.
> 
>  * JavaScript cross-site scripting prevention is incomplete - Critical -
>Drupal 7 and Drupal 8
>  * Private file access bypass - Moderately Critical - Drupal 7
>  * jQuery vulnerability with untrusted domains - Moderately Critical
>- Drupal 7
>  * External link injection on 404 pages when linking to the current page
>- Less Critical - Drupal 7

Let's split this up actually in the individual issues affecting Drupal
7 since there are no CVE yet available to identify the issues.

Regards,
Salvatore



Processed: Re: Bug#891150: drupal7: SA-CORE-2018-001: Several vulnerabilities

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2 -3 -4
Bug #891150 [src:drupal7] drupal7: SA-CORE-2018-001: Several vulnerabilities
Bug 891150 cloned as bugs 891152-891154
> retitle -1 drupal7: SA-CORE-2018-001: JavaScript cross-site scripting 
> prevention is incomplete
Bug #891150 [src:drupal7] drupal7: SA-CORE-2018-001: Several vulnerabilities
Changed Bug title to 'drupal7: SA-CORE-2018-001: JavaScript cross-site 
scripting prevention is incomplete' from 'drupal7: SA-CORE-2018-001: Several 
vulnerabilities'.
> retitle -2 drupal7: SA-CORE-2018-001: Private file access bypass
Bug #891152 [src:drupal7] drupal7: SA-CORE-2018-001: Several vulnerabilities
Changed Bug title to 'drupal7: SA-CORE-2018-001: Private file access bypass' 
from 'drupal7: SA-CORE-2018-001: Several vulnerabilities'.
> retitle -3 drupal7: SA-CORE-2018-001: jQuery vulnerability with untrusted 
> domains
Bug #891153 [src:drupal7] drupal7: SA-CORE-2018-001: Several vulnerabilities
Changed Bug title to 'drupal7: SA-CORE-2018-001: jQuery vulnerability with 
untrusted domains' from 'drupal7: SA-CORE-2018-001: Several vulnerabilities'.
> retitle -4 drupal7: SA-CORE-2018-001: External link injection on 404 pages 
> when linking to the current page
Bug #891154 [src:drupal7] drupal7: SA-CORE-2018-001: Several vulnerabilities
Changed Bug title to 'drupal7: SA-CORE-2018-001: External link injection on 404 
pages when linking to the current page' from 'drupal7: SA-CORE-2018-001: 
Several vulnerabilities'.

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



Processed: dune-uggrid FTBFS with cmake 3.10.2-1

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> fixed -1 2.6~20180108-1
Bug #891151 [src:dune-uggrid] dune-uggrid FTBFS with cmake 3.10.2-1
Marked as fixed in versions dune-uggrid/2.6~20180108-1.
> close -1
Bug #891151 [src:dune-uggrid] dune-uggrid FTBFS with cmake 3.10.2-1
Marked Bug as done

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



Bug#891151: dune-uggrid FTBFS with cmake 3.10.2-1

2018-02-22 Thread Adrian Bunk
Source: dune-uggrid
Version: 2.5.1-1
Severity: serious
Tags: patch
Control: fixed -1 2.6~20180108-1
Control: close -1

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

...
cd /build/1st/dune-uggrid-2.5.1/build/parallel/dddif && /usr/bin/c++  
-D-pthread -DENABLE_MPI=1 -DFOR_DUNE -DHAVE_CONFIG_H -DMPICH_SKIP_MPICXX 
-DMPIPP_H -DModelP -DUGLIB -DUG_DIM_3 -DUG_USE_NEW_DIMENSION_DEFINES 
-DUG_USE_SYSTEM_HEAP=1 -I/build/1st/dune-uggrid-2.5.1/build 
-I/build/1st/dune-uggrid-2.5.1 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
 -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/build/1st/dune-uggrid-2.5.1/low 
-I/build/1st/dune-uggrid-2.5.1/gm -I/build/1st/dune-uggrid-2.5.1/dev 
-I/build/1st/dune-uggrid-2.5.1/dom -I/build/1st/dune-uggrid-2.5.1/np 
-I/build/1st/dune-uggrid-2.5.1/ui -I/build/1st/dune-uggrid-2.5.1/np/algebra 
-I/build/1st/dune-uggrid-2.5.1/np/udm -I/build/1st/dune-uggrid-2.5.1/parallel 
-I/build/1st/dune-uggrid-2.5.1/parallel/ddd 
-I/build/1st/dune-uggrid-2.5.1/parallel/pp
 if -I/build/1st/dune-uggrid-2.5.1/parallel/dddif 
-I/build/1st/dune-uggrid-2.5.1/parallel/util 
-I/build/1st/dune-uggrid-2.5.1/parallel/ddd/include  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14  -fPIC   -o CMakeFiles/dddif3.dir/memmgr.cc.o -c 
/build/1st/dune-uggrid-2.5.1/parallel/dddif/memmgr.cc
:0:1: error: macro names must be identifiers


Felix Geyer mentioned that the root cause is that the
COMPILE_DEFINITIONS in parallel/CMakeLists.txt should
be replaced with COMPILE_OPTIONS.

The version in experimental seems already fixed.



Bug#891150: drupal7: SA-CORE-2018-001: Several vulnerabilities

2018-02-22 Thread Salvatore Bonaccorso
Source: drupal7
Version: 7.56-1
Severity: grave
Tags: security upstream

Hi

There was a new Drupal security advisory at

https://www.drupal.org/sa-core-2018-001

where several issues affect as well drupal7.

 * JavaScript cross-site scripting prevention is incomplete - Critical -
   Drupal 7 and Drupal 8
 * Private file access bypass - Moderately Critical - Drupal 7
 * jQuery vulnerability with untrusted domains - Moderately Critical
   - Drupal 7
 * External link injection on 404 pages when linking to the current page
   - Less Critical - Drupal 7

and fixed with 7.57 (others are affecting only Drupal 8, which is not
going to be packaged in Debian).

Regards,
Salvatore



Bug#889059: FTBFS with (miniupnpc) 2.0.20171212 (warzone2100)

2018-02-22 Thread peter green

to build with multiple versions of libminiupnpc-dev, replace

I think your suggested replacement is a bit over the top. I don't think there 
is any mileage in debian patches adding support for very old versions of 
miniupnpc.

Also your suggested fix seems to have a couple of issues. Firstly it seems to 
be missing a newline and secondly
it seems to have a wrong variable name in it.

Finally it seems that warzone2100 upstream was using the "API 14+" version of 
the call. Debian then patched it to support the API 8-13 version of the call and broke 
support for API 14+.

So taking this all into account I whipped up a patch to support both the API 
14+ version of that call and the API 8-13 version but not the older versions.

Unfortunately after doing so it seems that the package still failed to build in 
Raspbian buster, the next error was:


netplay.cpp:978:106: error: too few arguments to function ‘void* 
miniwget_getaddr(const char*, int*, char*, int, unsigned int, int*)’
descXML = (char *)miniwget_getaddr(dev->descURL, , lanaddr, 
sizeof(lanaddr), dev->scope_id);


Some searching lead me to 
https://github.com/miniupnp/miniupnp/commit/c4991916e5c12a7754e935e71a5313e75af6aeb9#diff-9813014a8c763f65cfbd4caec9552ddd
 and based on the changes to the testminiwget code in that commit I whipped up 
a patch.

With these fixes I was able to get a succesful build in Raspbian buster.

Debdiff attatched and uploaded to Raspbian, no intent to NMU in Debian.

diff -Nru warzone2100-3.2.1/debian/changelog warzone2100-3.2.1/debian/changelog
--- warzone2100-3.2.1/debian/changelog  2016-11-28 19:51:47.0 +
+++ warzone2100-3.2.1/debian/changelog  2018-02-22 18:35:47.0 +
@@ -1,3 +1,10 @@
+warzone2100 (3.2.1-2+rpi1) buster-staging; urgency=medium
+
+  * Fix build with miniupnpc API 16 (Closes: 889059)
++ Replace fix-upnpDiscover.patch with new patch miniupnpc-api.patch
+
+ -- Peter Michael Green   Thu, 22 Feb 2018 18:35:47 
+
+
 warzone2100 (3.2.1-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru warzone2100-3.2.1/debian/patches/fix-upnpDiscover.patch 
warzone2100-3.2.1/debian/patches/fix-upnpDiscover.patch
--- warzone2100-3.2.1/debian/patches/fix-upnpDiscover.patch 2016-11-28 
19:51:47.0 +
+++ warzone2100-3.2.1/debian/patches/fix-upnpDiscover.patch 1970-01-01 
00:00:00.0 +
@@ -1,23 +0,0 @@
-From: Russell Coker 
-Date: Mon, 19 Sep 2016 23:24:25 +0200
-Subject: fix-upnpDiscover
-
-remove extra arg from upnpDiscover()
-Forwarded: no

- lib/netplay/netplay.cpp | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/lib/netplay/netplay.cpp b/lib/netplay/netplay.cpp
-index 6c14dde..14266db 100644
 a/lib/netplay/netplay.cpp
-+++ b/lib/netplay/netplay.cpp
-@@ -951,7 +951,7 @@ static int upnp_init(void *asdf)
-   if (NetPlay.isUPNP)
-   {
-   debug(LOG_NET, "Searching for UPnP devices for automatic port 
forwarding...");
--  devlist = upnpDiscover(3000, NULL, NULL, 0, 0, 2, );
-+  devlist = upnpDiscover(3000, NULL, NULL, 0, 0, );
-   debug(LOG_NET, "UPnP device search finished.");
-   if (devlist)
-   {
diff -Nru warzone2100-3.2.1/debian/patches/miniupnpc-api.patch 
warzone2100-3.2.1/debian/patches/miniupnpc-api.patch
--- warzone2100-3.2.1/debian/patches/miniupnpc-api.patch1970-01-01 
00:00:00.0 +
+++ warzone2100-3.2.1/debian/patches/miniupnpc-api.patch2018-02-22 
18:24:14.0 +
@@ -0,0 +1,49 @@
+support both mininupnp API
+versions 14+ and the version previously used in Debian.
+
+Thanks to Thomas Bernard for pointing out what the problem with upnpDiscover
+was and providing the #if conditions to use.
+
+miniwget fix based on changes to testminiwget.c at 
+https://github.com/miniupnp/miniupnp/commit/c4991916e5c12a7754e935e71a5313e75af6aeb9#diff-9813014a8c763f65cfbd4caec9552ddd
+
+This patch replaces fix-upnpDiscover.patch by Russel corker 

+which made the package build with the version of miniupnpc in Debian at the 
time 
+but broke support for API version 14+
+
+Author: Peter Michael Green 
+Bug-debian: http://bugs.debian.org/889059
+
+Index: warzone2100-3.2.1/lib/netplay/netplay.cpp
+===
+--- warzone2100-3.2.1.orig/lib/netplay/netplay.cpp
 warzone2100-3.2.1/lib/netplay/netplay.cpp
+@@ -951,7 +951,11 @@ static int upnp_init(void *asdf)
+   if (NetPlay.isUPNP)
+   {
+   debug(LOG_NET, "Searching for UPnP devices for automatic port 
forwarding...");
++#if defined(MINIUPNPC_API_VERSION) && (MINIUPNPC_API_VERSION >= 14)
+   devlist = upnpDiscover(3000, NULL, NULL, 0, 0, 2, );
++#else
++  devlist = upnpDiscover(3000, NULL, NULL, 0, 0, );
++#endif
+   debug(LOG_NET, "UPnP device search finished.");
+   

Bug#891148: sat-xmpp-primitivus : Depends: python-urwid-satext (< 0.7~) but 0.7.0d-1 is to be installed

2018-02-22 Thread Adrian Bunk
Package: sat-xmpp-primitivus
Version: 0.6.1-2
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 sat-xmpp-primitivus : Depends: python-urwid-satext (< 0.7~) but 0.7.0d-1 is to 
be installed



Bug#891133: Bug #891133 in gnome-maps marked as pending

2018-02-22 Thread smcv
Control: tag -1 pending

Hello,

Bug #891133 in gnome-maps 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/gnome-team/gnome-maps/commit/006a85adafac5adeac07233f247dfdf3076d10f0


Add missing lib/maps-enum-types.[ch].template, from upstream git

Closes: #891133



(this message was generated automatically)
-- 
Greetings



Processed: Bug #891133 in gnome-maps marked as pending

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #891133 [src:gnome-maps] gnome-maps: make distclean deletes 
lib/maps-enum-types.[ch], but they cannot be regenerated
Added tag(s) pending.

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



Bug#890517: killer's CRON logs out users once per hour

2018-02-22 Thread Wolfgang Schweer
On Tue, Feb 20, 2018 at 12:54:26PM +0100, Wolfgang Schweer wrote:
> Seems to be X2Go Bug #1171 Create wtmp entry for x2go sessions
> 
> See: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1171

After testing x2goserver on a Stretch system I noticed that X2Go 
sessions can be detected reliably due to some command using a param 
string containing 'X2GO'.

This change would work around the x2go bug running the killer cron job 
only in case an X2Go session isn't detected:

--- a/cron.hourly   2014-06-11 11:15:55.0 +0200
+++ b/cron.hourly   2018-02-22 19:42:36.419963949 +0100
@@ -1,3 +1,3 @@
 #!/bin/sh
 
-if [ -x /usr/sbin/killer ] ; then /usr/sbin/killer; fi
+if [ -x /usr/sbin/killer ] && [ $(ps ax | grep X2GO | wc -l) -le 1 ] ; then 
/usr/sbin/killer; fi

Mike: could you test and give some feedback?

Wolfgang


signature.asc
Description: PGP signature


Processed: fixed 890028 in 4-3

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 890028 4-3
Bug #890028 [src:golang-github-asaskevich-govalidator] 
golang-github-asaskevich-govalidator FTBFS: test failures
Marked as fixed in versions golang-github-asaskevich-govalidator/4-3.
> thanks
Stopping processing here.

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



Processed: re: FTBFS with libminiupnpc-dev 2.0.20171212 (sushi)

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> Tags 889055 +patch
Bug #889055 [src:sushi] FTBFS with libminiupnpc-dev 2.0.20171212
Added tag(s) patch.
> Thanks
Stopping processing here.

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



Bug#889055: FTBFS with libminiupnpc-dev 2.0.20171212 (sushi)

2018-02-22 Thread peter green

Tags 889055 +patch
Thanks


with newer version of libminiupnpc-dev, one should :


I don't think there is any point in adding support for ancient miniupnpc 
versions.
Also there seems to be a missing newline in your suggested code.

Anyway based on the first part of your suggestion I made a patch.

Debdiff attatched and uploaded to Raspbian, no intent to NMU in Debian.

diff -Nru sushi-1.4.0+git20160822+dfsg/debian/changelog 
sushi-1.4.0+git20160822+dfsg/debian/changelog
--- sushi-1.4.0+git20160822+dfsg/debian/changelog   2017-03-20 
22:22:18.0 +
+++ sushi-1.4.0+git20160822+dfsg/debian/changelog   2018-02-22 
16:55:33.0 +
@@ -1,3 +1,10 @@
+sushi (1.4.0+git20160822+dfsg-4+rpi1) buster-staging; urgency=medium
+
+  * Add fix for MINIUPNPC_API_VERSION 14, thanks to nanard for the suggestion
+that the patch is based on. (Closes: 889055)
+
+ -- Peter Michael Green   Thu, 22 Feb 2018 16:55:33 
+
+
 sushi (1.4.0+git20160822+dfsg-4) unstable; urgency=medium
 
   * Revert following change introduced in 1.4.0+git20160822+dfsg-3, it
diff -Nru sushi-1.4.0+git20160822+dfsg/debian/patches/miniupnpc-api-14.diff 
sushi-1.4.0+git20160822+dfsg/debian/patches/miniupnpc-api-14.diff
--- sushi-1.4.0+git20160822+dfsg/debian/patches/miniupnpc-api-14.diff   
1970-01-01 00:00:00.0 +
+++ sushi-1.4.0+git20160822+dfsg/debian/patches/miniupnpc-api-14.diff   
2018-02-22 16:55:33.0 +
@@ -0,0 +1,21 @@
+Description:  Add fix for MINIUPNPC_API_VERSION 14
+ thanks to nanard for the suggestion
+ that the patch is based on.
+Author: Peter Michael Green 
+Bug-Debian: https://bugs.debian.org/889055
+
+--- sushi-1.4.0+git20160822+dfsg.orig/maki/source/plugins/upnp.c
 sushi-1.4.0+git20160822+dfsg/maki/source/plugins/upnp.c
+@@ -267,8 +267,11 @@ init (void)
+   gchar addr[64] = { '\0' };
+ #ifdef HAVE_MINIUPNPC_16
+   gint error;
+-
++#if defined(MINIUPNPC_API_VERSION) && (MINIUPNPC_API_VERSION >= 14)
++  miniupnpc_dev = upnpDiscover(1000, NULL, NULL, 0, 0, 2, 
); /* use default TTL of 2 */
++#else
+   miniupnpc_dev = upnpDiscover(1000, NULL, NULL, 0, 0, );
++#endif
+ #else
+   miniupnpc_dev = upnpDiscover(1000, NULL, NULL, 0);
+ #endif
diff -Nru sushi-1.4.0+git20160822+dfsg/debian/patches/series 
sushi-1.4.0+git20160822+dfsg/debian/patches/series
--- sushi-1.4.0+git20160822+dfsg/debian/patches/series  2017-03-18 
15:37:47.0 +
+++ sushi-1.4.0+git20160822+dfsg/debian/patches/series  2018-02-22 
16:55:33.0 +
@@ -2,3 +2,4 @@
 nigiri-00-fix-gobject-import.diff
 nigiri-01-fix-urwid-indexerror.diff
 nigiri-02-none-has-no-auto_scroll.diff
+miniupnpc-api-14.diff


Bug#853424: gnash: FTBFS with agg 1:2.4-r127+dfsg1-1

2018-02-22 Thread Steve Langasek
Package: gnash
Version: 0.8.11~git20160608-1.3
Followup-For: Bug #853424
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Hello,

Thanks for the hints in this bug regarding the API changes.  I've prepared a
patch which fixes the gnash build against current agg, and have uploaded it
to Ubuntu.  You may wish to consider applying it in Debian as well.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru 
gnash-0.8.11~git20160608/debian/patches/agg-2.4-r127-compatibility.patch 
gnash-0.8.11~git20160608/debian/patches/agg-2.4-r127-compatibility.patch
--- gnash-0.8.11~git20160608/debian/patches/agg-2.4-r127-compatibility.patch
1969-12-31 16:00:00.0 -0800
+++ gnash-0.8.11~git20160608/debian/patches/agg-2.4-r127-compatibility.patch
2018-02-21 21:19:18.0 -0800
@@ -0,0 +1,149 @@
+Description: fix compatibility with agg 2.4r127
+ call agg::rgba8().premultiply() instead of obsoleted rgba8_pre()
+ fix missing consts
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/853424
+
+Index: gnash-0.8.11~git20160608/librender/agg/Renderer_agg_style.h
+===
+--- gnash-0.8.11~git20160608.orig/librender/agg/Renderer_agg_style.h
 gnash-0.8.11~git20160608/librender/agg/Renderer_agg_style.h
+@@ -614,8 +614,8 @@
+ 
+ // add the color to our self-made style handler (basically
+ // just a list)
+-_sh.add_color(agg::rgba8_pre(color.m_r, color.m_g, color.m_b,
+-  color.m_a));
++_sh.add_color(agg::rgba8(color.m_r, color.m_g, color.m_b,
++  color.m_a).premultiply());
+ }
+ 
+ void operator()(const BitmapFill& f) const {
+@@ -652,11 +652,11 @@
+ 
+ if (!bm) {
+ // See misc-swfmill.all/missing_bitmap.swf
+-_sh.add_color(agg::rgba8_pre(255,0,0,255));
++_sh.add_color(agg::rgba8(255,0,0,255).premultiply());
+ }
+ else if ( bm->disposed() ) {
+ // See misc-ming.all/BeginBitmapFill.swf
+-_sh.add_color(agg::rgba8_pre(0,0,0,0));
++_sh.add_color(agg::rgba8(0,0,0,0).premultiply());
+ }
+ else {
+ _sh.add_bitmap(dynamic_cast(bm),
+Index: gnash-0.8.11~git20160608/librender/agg/Renderer_agg.cpp
+===
+--- gnash-0.8.11~git20160608.orig/librender/agg/Renderer_agg.cpp
 gnash-0.8.11~git20160608/librender/agg/Renderer_agg.cpp
+@@ -418,8 +418,8 @@
+ _ras.add_path(stroke);
+ 
+ // Set the color and render the scanlines
+-_renderer.color(agg::rgba8_pre(color.m_r, color.m_g, 
+-color.m_b, color.m_a));
++_renderer.color(agg::rgba8(color.m_r, color.m_g, 
++color.m_b, color.m_a).premultiply());
+ 
+ agg::render_scanlines(_ras, sl, _renderer);
+ 
+@@ -553,7 +553,7 @@
+ 
+ // cloning image accessor is used to avoid disturbing pixels at
+ // the edges for rotated video. 
+-typedef agg::image_accessor_clone Accessor;
++typedef agg::image_accessor_clone Accessor;
+ 
+ /// Types used for different quality.
+ //
+@@ -615,7 +615,7 @@
+ }
+ else {
+ // Untested.
+-typedef agg::scanline_u8_am Scanline;
++typedef agg::scanline_u8_am Scanline;
+ Scanline sl(masks.back().getMask());
+ renderScanlines(path, rbase, sl, sg);
+ }
+@@ -852,7 +852,7 @@
+ // clear the stage using the background color
+ if ( ! _clipbounds.empty() )
+ {
+-const agg::rgba8& col = agg::rgba8_pre(bg.m_r, bg.m_g, bg.m_b, 
bg.m_a);
++const agg::rgba8& col = agg::rgba8(bg.m_r, bg.m_g, bg.m_b, 
bg.m_a).premultiply();
+ for (const auto& bounds : _clipbounds)
+ {
+ clear_framebuffer(bounds, col);
+@@ -981,7 +981,7 @@
+ }
+ else {
+ // Mask is active!
+-typedef agg::scanline_u8_am sl_type;
++typedef agg::scanline_u8_am sl_type;
+ sl_type sl(_alphaMasks.back().getMask());  
+ lr.render(sl, stroke, color);
+ }
+@@ -1425,7 +1425,7 @@
+ 
+   // Mask is active, use alpha mask scanline renderer
+   
+-  typedef agg::scanline_u8_am scanline_type;
++  typedef agg::scanline_u8_am scanline_type;
+   
+   scanline_type sl(_alphaMasks.back().getMask());
+   
+@@ -1538,7 +1538,7 @@
+   // Woohoo! We're drawing a nested mask! Use the previous mask while 
+   // drawing the new one, the result will be the intersection.
+   
+-  typedef 

Processed: [bts-link] source package icinga2

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package icinga2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #883247 (http://bugs.debian.org/883247)
> # Bug title: CVE-2017-16933: icinga2: root privilege escalation via 
> prepare-dirs
> #  * https://github.com/Icinga/icinga2/issues/5793
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 883247 + fixed-upstream
Bug #883247 [icinga2] CVE-2017-16933: icinga2: root privilege escalation via 
prepare-dirs
Added tag(s) fixed-upstream.
> usertags 883247 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 883247 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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



Processed: tagging 876459

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 876459 + sid buster
Bug #876459 {Done: Patrick Matthäi } [needrestart] 
needrestart: Non-interactive mode not being detected properly
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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



Processed: reassign 758622 to src:linux, reassign 766781 to src:linux, reassign 772627 to src:linux ...

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 758622 src:linux
Bug #758622 [linux-image-3.16.0-4-amd64] kernel crashes after soft lockups in 
xen domU
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #758622 to the same values 
previously set
Ignoring request to alter fixed versions of bug #758622 to the same values 
previously set
> reassign 766781 src:linux
Bug #766781 [linux-image-3.16.0-4-amd64] Mic boost control introduces distortion
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #766781 to the same values 
previously set
Ignoring request to alter fixed versions of bug #766781 to the same values 
previously set
> reassign 772627 src:linux 3.16.7-2
Bug #772627 [linux-image-3.16.0-4-amd64] linux: WARNING: CPU: 2 PID: 344 at 
/build/linux-Y9HjRe/linux-3.16.7/drivers/gpu/drm/i915/intel_display.c:953 
ironlake_crtc_disable+0x90/0x910 [i915]()
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
No longer marked as found in versions linux/3.16.7-2.
Ignoring request to alter fixed versions of bug #772627 to the same values 
previously set
Bug #772627 [src:linux] linux: WARNING: CPU: 2 PID: 344 at 
/build/linux-Y9HjRe/linux-3.16.7/drivers/gpu/drm/i915/intel_display.c:953 
ironlake_crtc_disable+0x90/0x910 [i915]()
Marked as found in versions linux/3.16.7-2.
> found 772627 linux/3.16.7-2
Bug #772627 [src:linux] linux: WARNING: CPU: 2 PID: 344 at 
/build/linux-Y9HjRe/linux-3.16.7/drivers/gpu/drm/i915/intel_display.c:953 
ironlake_crtc_disable+0x90/0x910 [i915]()
Ignoring request to alter found versions of bug #772627 to the same values 
previously set
> reassign 773355 src:linux 3.16.7-ckt2-1
Bug #773355 [linux-image-3.16.0-4-amd64] linux-image-3.16.0-4-amd64: kernel bug 
when hotplugging a CPU
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
No longer marked as found in versions linux/3.16.7-ckt2-1.
Ignoring request to alter fixed versions of bug #773355 to the same values 
previously set
Bug #773355 [src:linux] linux-image-3.16.0-4-amd64: kernel bug when hotplugging 
a CPU
Marked as found in versions linux/3.16.7-ckt2-1.
> found 773355 linux/3.16.7-ckt2-1
Bug #773355 [src:linux] linux-image-3.16.0-4-amd64: kernel bug when hotplugging 
a CPU
Ignoring request to alter found versions of bug #773355 to the same values 
previously set
> reassign 773368 src:linux 3.16.7-ckt2-1
Bug #773368 [linux-image-3.16.0-4-amd64] GPU lockup at boot with Nvidia 
Corporation G72M [Quadro NVS 110M/GeForce Go 7300]
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
No longer marked as found in versions linux/3.16.7-ckt2-1.
Ignoring request to alter fixed versions of bug #773368 to the same values 
previously set
Bug #773368 [src:linux] GPU lockup at boot with Nvidia Corporation G72M [Quadro 
NVS 110M/GeForce Go 7300]
Marked as found in versions linux/3.16.7-ckt2-1.
> found 773368 linux/3.16.7-ckt2-1
Bug #773368 [src:linux] GPU lockup at boot with Nvidia Corporation G72M [Quadro 
NVS 110M/GeForce Go 7300]
Ignoring request to alter found versions of bug #773368 to the same values 
previously set
> reassign 775319 src:linux
Bug #775319 [linux-image-3.16.0-4-amd64] pulseaudio: unable to use headphones 
or other line out ports for audio. only speakers
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #775319 to the same values 
previously set
Ignoring request to alter fixed versions of bug #775319 to the same values 
previously set
> reassign 776874 src:linux
Bug #776874 [linux-image-3.16.0-4-amd64] systemd: system auto-resumes when 
pcspkr module is loaded
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #776874 to the same values 
previously set
Ignoring request to alter fixed versions of bug #776874 to the same values 
previously set
> reassign 777440 src:linux
Bug #777440 [linux-image-3.16.0-4-amd64] systemd: Fails to hibernate the system
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #777440 to the same values 
previously set
Ignoring request to alter fixed versions of bug #777440 to the same values 
previously set
> reassign 780520 src:linux
Bug #780520 [linux-image-3.16.0-4-amd64] systemd-sysv: computer restarts after 
shutdown if connected to an external display
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #780520 to the same values 
previously set
Ignoring request to alter fixed versions of bug #780520 to the same values 
previously set
> reassign 780631 src:linux 3.16.7-ckt7-1
Bug #780631 [linux-image-3.16.0-4-amd64] e1000e: Intel I217-V non-functional 
after booting Windows
Bug reassigned from package 

Bug#867404: python3-exam: incorrect dependencies

2018-02-22 Thread Andreas Beckmann
Followup-For: Bug #867404
Control: tag -1 patch pending

Hi,

this will be fixed for stable in the next point release with the
attached debdiff.


Andreas
diff -Nru exam-0.10.5/debian/changelog exam-0.10.5/debian/changelog
--- exam-0.10.5/debian/changelog2016-06-14 19:54:12.0 +0200
+++ exam-0.10.5/debian/changelog2018-02-22 16:11:59.0 +0100
@@ -1,3 +1,19 @@
+exam (0.10.5-1+deb9u1) stretch; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Non-maintainer upload.
+  * Backport fixes from 0.10.5-2 to stretch.
+
+  [ Scott Kitterman ]
+  * Correct Vcs-* fields in debian/control to point to the correct package
+name
+  * Use correct substitution variable for python3-exam so python3 interpreter
+depends are correctly generated (Closes: #867404)
+  * Let dh_python determine the mock depends (corrects issue where python-
+exam incorrectly depended on python-mock instead of python3-mock)
+
+ -- Andreas Beckmann   Thu, 22 Feb 2018 16:11:59 +0100
+
 exam (0.10.5-1) unstable; urgency=low
 
   * Initial release. (Closes: #825822)
diff -Nru exam-0.10.5/debian/control exam-0.10.5/debian/control
--- exam-0.10.5/debian/control  2016-06-14 19:54:12.0 +0200
+++ exam-0.10.5/debian/control  2018-01-14 11:02:56.0 +0100
@@ -21,12 +21,12 @@
 X-Python-Version: >= 2.6
 X-Python3-Version: >= 3.2
 Homepage: https://github.com/fluxx/exam
-Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/python-exam.git
-Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/python-exam.git
+Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/exam.git
+Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/exam.git
 
 Package: python-exam
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-mock
+Depends: ${misc:Depends}, ${python:Depends}
 Description: Python module to help write better tests
  Exam is a Python toolkit for writing better tests.  It aims to remove
  a lot of the boiler plate testing code one often writes, while still
@@ -59,7 +59,7 @@
 
 Package: python3-exam
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-mock
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Python module to help write better tests
  Exam is a Python toolkit for writing better tests.  It aims to remove
  a lot of the boiler plate testing code one often writes, while still


Processed: Re: python3-exam: incorrect dependencies

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 patch pending
Bug #867404 {Done: Scott Kitterman } [python3-exam] 
python3-exam: incorrect dependencies
Added tag(s) pending.

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



Bug#879848: cappuccino: missing dependency on gir1.2-gtk-3.0

2018-02-22 Thread Andreas Beckmann
Followup-For: Bug #879848
Control: tag -1 patch pending

Hi,

this will be fixed in the next stretch point release with the attached
debdiff.


Andreas
diff -u cappuccino-0.5.1/debian/changelog cappuccino-0.5.1/debian/changelog
--- cappuccino-0.5.1/debian/changelog
+++ cappuccino-0.5.1/debian/changelog
@@ -1,3 +1,14 @@
+cappuccino (0.5.1-6+deb9u1) stretch; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Non-maintainer upload.
+  * Backport fix from 0.5.1-7 to stretch.
+
+  [ Breno Leitao ]
+  * Adding gir1.2-gtk-3.0 as a dependency. Closes: #879848
+
+ -- Andreas Beckmann   Thu, 22 Feb 2018 15:58:38 +0100
+
 cappuccino (0.5.1-6) unstable; urgency=medium
 
   * Fix python dependency, moving the debian/rules file to
diff -u cappuccino-0.5.1/debian/control cappuccino-0.5.1/debian/control
--- cappuccino-0.5.1/debian/control
+++ cappuccino-0.5.1/debian/control
@@ -8,7 +8,7 @@
 
 Package: cappuccino
 Architecture: all
-Depends: python3, python3-gi, polygen, ${misc:Depends}
+Depends: python3, python3-gi, polygen, ${misc:Depends},  gir1.2-gtk-3.0
 Description: utility to let your boss think that you're working hard
  Run this software on your computer when you are not motivated to work, and
  enjoy doing something different. If your boss come in your cubicle, he'll


Processed: Re: cappuccino: missing dependency on gir1.2-gtk-3.0

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 patch pending
Bug #879848 {Done: Breno Leitao } [src:cappuccino] 
cappuccino: missing dependency on gir1.2-gtk-3.0
Added tag(s) patch and pending.

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



Processed: Re: [Pkg-chromium-maint] Bug#891062: Bug#891062: chromium: skia fails to build on arm64

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 891062 +pending
Bug #891062 [src:chromium-browser] chromium: skia fails to build on arm64
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#867396: python3-cerealizer: missing python3 dependency

2018-02-22 Thread Andreas Beckmann
Followup-For: Bug #867396
Control: tag -1 patch pending

This will be fixed in the next stretch point release with the attached
debdiff.


Andreas
diff -Nru cerealizer-0.8.1/debian/changelog cerealizer-0.8.1/debian/changelog
--- cerealizer-0.8.1/debian/changelog   2013-08-15 14:51:29.0 +0200
+++ cerealizer-0.8.1/debian/changelog   2018-02-22 15:46:07.0 +0100
@@ -1,3 +1,14 @@
+cerealizer (0.8.1-1+deb9u1) stretch; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Non-maintainer upload.
+  * Backport fix from 0.8.1-2 to stretch.
+
+  [ Vincent Bernat ]
+  * Fix python3-cerealizer Depends field. Closes: #867396.
+
+ -- Andreas Beckmann   Thu, 22 Feb 2018 15:46:07 +0100
+
 cerealizer (0.8.1-1) unstable; urgency=low
 
   [ Jakub Wilk ]
diff -Nru cerealizer-0.8.1/debian/control cerealizer-0.8.1/debian/control
--- cerealizer-0.8.1/debian/control 2013-08-15 14:48:38.0 +0200
+++ cerealizer-0.8.1/debian/control 2018-01-14 10:49:33.0 +0100
@@ -23,7 +23,7 @@
 
 Package: python3-cerealizer
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
+Depends: ${python3:Depends}, ${misc:Depends}
 Description: secure pickle-like module for Python 3
  It support basic types (int, string, unicode, tuple, list,
  dict, set,...), old and new-style classes (you need to


Bug#891062: [Pkg-chromium-maint] Bug#891062: Bug#891062: chromium: skia fails to build on arm64

2018-02-22 Thread Riku Voipio
tags 891062 +pending
thanks

On Thu, Feb 22, 2018 at 11:48:10AM +, Riku Voipio wrote:
> +// On ARM we expect that you're using Clang if you want SkJumper to be fast.
> +// If you are, the baseline float stages will use NEON, and lowp stages will
> +// also be available. (If somehow you're building for ARM not using Clang,
> +// you'll get scalar baseline stages and no lowp support.)
> 
> Well clearly the fallback was not tested.

I've pushed a workaround to the experimental branch. 



Processed: Re: python3-cerealizer: missing python3 dependency

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 patch pending
Bug #867396 {Done: Vincent Bernat } [python3-cerealizer] 
python3-cerealizer: missing python3 dependency
Added tag(s) pending.

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



Processed: found 884514 in 2.0.0-2

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 884514 2.0.0-2
Bug #884514 [ruby-fog-aws] ruby-fog-aws: fails to upgrade from 'sid' - trying 
to overwrite /usr/lib/ruby/vendor_ruby/fog/aws/service_mapper.rb
Marked as found in versions ruby-fog-aws/2.0.0-2.
> thanks
Stopping processing here.

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



Bug#891133: gnome-maps: make distclean deletes lib/maps-enum-types.[ch], but they cannot be regenerated

2018-02-22 Thread Andreas Beckmann
Source: gnome-maps
Version: 3.27.90-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gnome-maps/experimental FTBFS twice in a row. The first build succeeds,
subsequent 'debian/rules clean' calls 'make distclean' which deletes
lib/maps-enum-types.[ch], but these two files cannot be regenerated
for the second build since lib/maps-enum-types.[ch].template are missing.

[...]
   dh_auto_build
make -j4
make[1]: Entering directory '/build/gnome-maps-3.27.90'
Making all in lib
make[2]: Entering directory '/build/gnome-maps-3.27.90/lib'
(glib-mkenums   \
--template ./maps-enum-types.h.template \
maps-contact-store.h maps-contact.h mapsintl.h maps.h 
maps-file-tile-source.h maps-osm.h maps-osm-changeset.h maps-osm-node.h 
maps-osm-object.h maps-osm-relation.h maps-osm-way.h 
maps-osm-oauth-proxy-call.h > xgen-maps-enum-types.h && mv -f 
xgen-maps-enum-types.h maps-enum-types.h)
Traceback (most recent call last):
  File "/usr/bin/glib-mkenums", line 342, in 
read_template_file(options.template)
  File "/usr/bin/glib-mkenums", line 272, in read_template_file
ifile = io.open(file, encoding="utf-8", errors="replace_and_warn")
FileNotFoundError: [Errno 2] No such file or directory: 
'./maps-enum-types.h.template'
Makefile:814: recipe for target 'maps-enum-types.h' failed
make[2]: *** [maps-enum-types.h] Error 1
make[2]: Leaving directory '/build/gnome-maps-3.27.90/lib'
Makefile:442: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/build/gnome-maps-3.27.90'
dh_auto_build: make -j4 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas


gnome-maps_3.27.90-1_twice.log.gz
Description: application/gzip


Bug#891043: src:python-yaql: FTBFS with ply/3.11-1

2018-02-22 Thread Thomas Goirand
On 02/21/2018 08:24 PM, Stefano Rivera wrote:
> Package: src:python-yaql
> Version: 1.1.1-2
> Severity: serious
> Tags: patch upstream
> Justification: fails to build from source (but built successfully in the past)
> Control: fixed -1 1.1.3-1
> 
> I've just uploaded ply 3.11-1, and the only thing this is going to break
> is python-yaql. Sorry for that, but the good news is that this is
> already fixed in 1.1.3-1.
> 
> So, please apply this patch or upload 1.1.3-1 to unstable.
> 
>> ==
>> FAIL: 
>> yaql.tests.test_yaqlization.TestYaqlization.test_yaqlify_decorator_with_parameters
>> yaql.tests.test_yaqlization.TestYaqlization.test_yaqlify_decorator_with_parameters
>> --
>> _StringException: Traceback (most recent call last):
>>   File "yaql/tests/test_yaqlization.py", line 189, in 
>> test_yaqlify_decorator_with_parameters
>> self.assertEqual(555, self.eval('$.attr', C()))
>>   File "yaql/tests/__init__.py", line 90, in eval
>> expr = self.engine(expression)
>>   File "yaql/language/factory.py", line 76, in __call__
>> self.parser.parse(expression, lexer=self.lexer), self)
>>   File "/usr/lib/python2.7/dist-packages/ply/yacc.py", line 333, in parse
>> return self.parseopt_notrack(input, lexer, debug, tracking, tokenfunc)
>>   File "/usr/lib/python2.7/dist-packages/ply/yacc.py", line 1063, in 
>> parseopt_notrack
>> lookahead = get_token() # Get the next token
>>   File "/usr/lib/python2.7/dist-packages/ply/lex.py", line 393, in token
>> newtok = self.lexerrorf(tok)
>>   File "yaql/language/lexer.py", line 148, in t_error
>> raise exceptions.YaqlLexicalException(t.value[0], t.lexpos)
>> yaql.language.exceptions.YaqlLexicalException: Lexical error: illegal 
>> character '$' at position 0
>>
>>
>> --
>> Ran 363 tests in 1.488s
>>
>> FAILED (failures=332)
> 
> SR

Hi Stefano,

Thanks a lot for your care, this is greatly appreciated to see Python
people caring for their reverse (build-)dependencies.

I'll upload all of OpenStack Queens, currently in Experimental, and
which includes yaql, over the course of next week, so no need to worry,
this will close this bug.

Cheers,

Thomas Goirand (zigo)



Bug#891127: python-pysaml2: tests require network access

2018-02-22 Thread Andreas Beckmann
Source: python-pysaml2
Version: 4.0.2-1
Severity: serious
Justification: fails to build from source

Hi,

the test test_load_extern_incommon requires network access:

=== FAILURES ===
__ test_load_extern_incommon ___

def test_load_extern_incommon():
sec_config.xmlsec_binary = sigver.get_xmlsec_binary(["/opt/local/bin"])
mds = MetadataStore(ATTRCONV, sec_config,
disable_ssl_certificate_validation=True)

>   mds.imp(METADATACONF["10"])

tests/test_30_mdstore.py:367: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
src/saml2/mdstore.py:929: in imp
_md.load()
src/saml2/mdstore.py:718: in load
response = self.http.send(self.url)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
url = 'http://md.incommon.org/InCommon/InCommon-metadata-export.xml'
method = 'GET', kwargs = {}
_kwargs = {'allow_redirects': False, 'verify': False}, arg = 'auth'
exc = ConnectionError(MaxRetryError("HTTPConnectionPool(host='md.incommon.org', 
port...lish a new connection: [Errno -3] Temporary failure in name 
resolution',))",),)


Andreas


python-pysaml2_4.0.2-1.log.gz
Description: application/gzip


Bug#891126: python-proliantutils: FTBFS with TypeError: refresh() got an unexpected keyword argument 'force'

2018-02-22 Thread Andreas Beckmann
Source: python-proliantutils
Version: 2.5.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-proliantutils/experimental FTBFS with lots of

==
FAIL: 
proliantutils.tests.redfish.resources.account_service.test_account_service.HPEAccountServiceTestCase.test_accounts
proliantutils.tests.redfish.resources.account_service.test_account_service.HPEAccountServiceTestCase.test_accounts
--
_StringException: Traceback (most recent call last):
  File 
"proliantutils/tests/redfish/resources/account_service/test_account_service.py",
 line 46, in test_accounts
accounts = self.acc_inst.accounts
  File "proliantutils/redfish/resources/account_service/account_service.py", 
line 40, in accounts
self._accounts.refresh(force=False)
TypeError: refresh() got an unexpected keyword argument 'force'


Andreas


python-proliantutils_2.5.0-1.log.gz
Description: application/gzip


Bug#891124: python-oslo.cache: FTBFS with ModuleNotFoundError: No module named 'urllib3', 'oslotest'

2018-02-22 Thread Andreas Beckmann
Source: python-oslo.cache
Version: 1.28.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.cache/experimental FTBFS due to missing python modules:

[...]
===> Testing with python (python3)
+ [ -e .stestr.conf ]
+ [ -e .testr.conf ]
+ rm -rf .testrepository
+ testr-python3 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.ZrHRZ4xdyG
+ tee /tmp/tmp.ZrHRZ4xdyG
+ pwd
+ subunit2pyunit
+ PYTHONPATH=/build/python-oslo.cache-1.28.0 PYTHON=python3.6 testr-python3 run 
--subunit
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
 ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_cache
unittest2.loader._FailedTest.oslo_cache.tests.test_cache ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo
unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_connection_pool
unittest2.loader._FailedTest.oslo_cache.tests.test_connection_pool ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_dict_backend
unittest2.loader._FailedTest.oslo_cache.tests.test_dict_backend ... FAIL
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ ./oslo_cache  

==
FAIL: 
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
oslo_cache.tests.functional.test_cache_backend_etcd3gw
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/python-oslo.cache-1.28.0/oslo_cache/tests/functional/test_cache_backend_etcd3gw.py",
 line 17, in 
import urllib3
ModuleNotFoundError: No module named 'urllib3'


==
FAIL: unittest2.loader._FailedTest.oslo_cache.tests.test_cache
unittest2.loader._FailedTest.oslo_cache.tests.test_cache
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: oslo_cache.tests.test_cache
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "/build/python-oslo.cache-1.28.0/oslo_cache/tests/test_cache.py", line 
24, in 
from oslotest import base
ModuleNotFoundError: No module named 'oslotest'


==
FAIL: unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo
unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
oslo_cache.tests.test_cache_backend_mongo
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/python-oslo.cache-1.28.0/oslo_cache/tests/test_cache_backend_mongo.py", 
line 27, in 
from oslo_cache.tests import test_cache
  File "/build/python-oslo.cache-1.28.0/oslo_cache/tests/test_cache.py", line 
24, in 
from oslotest import base
ModuleNotFoundError: No module named 'oslotest'


==
FAIL: unittest2.loader._FailedTest.oslo_cache.tests.test_connection_pool
unittest2.loader._FailedTest.oslo_cache.tests.test_connection_pool
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: oslo_cache.tests.test_connection_pool
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 

Bug#891012: kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - trying to overwrite usr/share/kicad/*

2018-02-22 Thread Andreas Beckmann
Package: kicad-footprints,kicad-symbols,kicad-templates
Followup-For: Bug #891012

Let's add kicad-packages3d to this list:

  Selecting previously unselected package kicad-packages3d.
  Preparing to unpack .../kicad-packages3d_0~2018.02.17-1_all.deb ...
  Unpacking kicad-packages3d (0~2018.02.17-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-packages3d_0~2018.02.17-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/kicad/modules/packages3d/Converters_DCDC_ACDC.3dshapes/DCDC-Conv_TRACO_TEN20-.wrl',
 which is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-packages3d_0~2018.02.17-1_all.deb


Andreas



Bug#891114: activemq: B-D libjosql-java-doc is no longer available

2018-02-22 Thread Andreas Beckmann
Package: activemq
Version: 5.15.2-2
Severity: serious
Justification: fails to build from source

libjosql-java-doc is no longer built by src:josql


Andreas



Bug#876459: needrestart: Non-interactive mode not being detected properly

2018-02-22 Thread Dominik George
Hi Patrick,

> I regularly see this bug cause important PostgreSQL databases to be
> restarted on Debian stable.
> 
> Can you please make sure to provide an update for the next Debian point
> release? If you need help doing so, feel free to say that.

Any news/opinion on that?

If I do not hear anything from you within this week, I will start
negotiating with therelease team about the patch for the next point
release.

Cheers,
Nik


signature.asc
Description: PGP signature


Bug#884629: marked as done (appstream FTBFS with meson 0.44.0-1)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:51:52 +
with message-id 
and subject line Bug#884627: fixed in meson 0.44.1-1
has caused the Debian Bug report #884627,
regarding appstream FTBFS with meson 0.44.0-1
to be marked as done.

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

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


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

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

...
FAILED: data/org.freedesktop.appstream.cli.metainfo.xml 
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.44.1-1

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2018 00:02:07 +0200
Source: meson
Binary: meson
Architecture: source all
Version: 0.44.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 884627
Changes:
 meson (0.44.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #884627.
Checksums-Sha1:
 c854b26c0e8591be111d9edf43f8da16bf2bd4ca 3208 meson_0.44.1-1.dsc
 12d1d0466955da4f9a7ef158a23d4e37d985d667 1136478 meson_0.44.1.orig.tar.gz
 6b0afb08a619d2297c404c0bfc1bfb6bb4061523 11676 meson_0.44.1-1.debian.tar.xz
 5f60ee37fed20338e42e35df829bc1a351cc79ee 208492 meson_0.44.1-1_all.deb
 b697ebde5a28cd2e9997b814b4e880de4706324d 32288 meson_0.44.1-1_amd64.buildinfo
Checksums-Sha256:
 62080d9dbb1f643a0a6fe2281a7b18b09186ebd64a58db6792943a0305d8e078 3208 
meson_0.44.1-1.dsc
 2ea1a721574adb23160b6481191bcc1173f374e02b0ff3bb0ae85d988d97e4fa 1136478 
meson_0.44.1.orig.tar.gz
 10984a42d2bf8a41ffa9e7329ae075e64cbe3e1bd67f662cd6abc9e16a173dc3 11676 
meson_0.44.1-1.debian.tar.xz
 99d13fabc414c59db1919ae00df7363b36060699b3591d6868f091dae7bf2b0a 208492 
meson_0.44.1-1_all.deb
 8204389e7fdd4ba7464f041ac26c73644951496769e204ab09b23e75cc8beae6 32288 
meson_0.44.1-1_amd64.buildinfo
Files:
 1e5667f7511ceca562483e874316f7be 3208 devel optional meson_0.44.1-1.dsc
 82b1198bf714b5a4da84bfe8376c79cc 1136478 devel optional 
meson_0.44.1.orig.tar.gz
 ca4727ec0fb8b2077c83c7ad1ac3f6b2 11676 devel optional 
meson_0.44.1-1.debian.tar.xz
 5ecdad7d24be35415d70469e073587ae 208492 devel optional meson_0.44.1-1_all.deb
 5bf22ff8673324437a4b3cf38f392839 32288 devel optional 
meson_0.44.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlqOqrkACgkQxrkYDUvY
t64Q5w//Ws48kHAhq8Z4oJITaSh0f6/K+qlK+t4Fh25B7SZ7CYtczrolSIPw+QLo
Qn2RJjNeBtxAJCiklOqnUJjMqKvGf3W+tZLOFA0i5FNLBdwpEn5fZ/PUIj93zyGl
dpoQ9FkTNoWvhv/8+XaEuPK4pmLSv9dGOx4eI9Szx2mNxo03BWfplFUOU5Qi6eVD
Q06faSbBi2ykg8Y5IZ0aOOwDFbln6zxGoSYkAmIItyYxkgAknmzB/66PWFzn/XT6
jTsyxzOZAFXCmjI/LLsYEc1RCqTJC0H1litLyqeUwDK+ocszKC0nFfZn3DPNpO/X
k6NEFUAEi5TayjFw5lD2lo5PlCwwN26ojeTrpTK2dalS7AdbAu3G38lCZAz1kOpq
WtarUPrbAg8Z+qXXCaOzinTBxwoq96H2k2Fc3Ks9oHK0uGN0eGrohMqoETzUvlWK
y+WioCWTlPdDnxekDldlPORYpRoAaDymWdFXQGFypeQRwd9WDkQMoAjpm0GO1KTr
mryUsFxIc5Xxf93/nkHr83hQpsylkUql7YDhtXYLnuF43QBPsLGT8rjtyFXqoc1o
qYAaGUntJ9pDXUDfnNjxVasf3GoerRwlnZOL19nwZ+BTXSbprxp+kQ+muNmVgZdX
QthKdbpHZckUBYqsMjbcjhFgkCwkDcLg7ObI4fDhhPDhum9ge60=
=PjAZ
-END PGP SIGNATURE End Message ---


Bug#884628: marked as done (appstream-generator FTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:51:52 +
with message-id 
and subject line Bug#884627: fixed in meson 0.44.1-1
has caused the Debian Bug report #884627,
regarding appstream-generator FTBFS with meson 0.44.0-1: Subproject_dir must 
not contain a path segment
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.)


-- 
884627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream-generator
Version: 0.6.8-2
Severity: serious

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

...
The Meson build system
Version: 0.44.0
Source dir: /build/1st/appstream-generator-0.6.8
Build dir: /build/1st/appstream-generator-0.6.8/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson.build, line 1, column 0:
Subproject_dir must not contain a path segment.
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.44.1-1

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2018 00:02:07 +0200
Source: meson
Binary: meson
Architecture: source all
Version: 0.44.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 884627
Changes:
 meson (0.44.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #884627.
Checksums-Sha1:
 c854b26c0e8591be111d9edf43f8da16bf2bd4ca 3208 meson_0.44.1-1.dsc
 12d1d0466955da4f9a7ef158a23d4e37d985d667 1136478 meson_0.44.1.orig.tar.gz
 6b0afb08a619d2297c404c0bfc1bfb6bb4061523 11676 meson_0.44.1-1.debian.tar.xz
 5f60ee37fed20338e42e35df829bc1a351cc79ee 208492 meson_0.44.1-1_all.deb
 b697ebde5a28cd2e9997b814b4e880de4706324d 32288 meson_0.44.1-1_amd64.buildinfo
Checksums-Sha256:
 62080d9dbb1f643a0a6fe2281a7b18b09186ebd64a58db6792943a0305d8e078 3208 
meson_0.44.1-1.dsc
 2ea1a721574adb23160b6481191bcc1173f374e02b0ff3bb0ae85d988d97e4fa 1136478 
meson_0.44.1.orig.tar.gz
 10984a42d2bf8a41ffa9e7329ae075e64cbe3e1bd67f662cd6abc9e16a173dc3 11676 
meson_0.44.1-1.debian.tar.xz
 99d13fabc414c59db1919ae00df7363b36060699b3591d6868f091dae7bf2b0a 208492 
meson_0.44.1-1_all.deb
 8204389e7fdd4ba7464f041ac26c73644951496769e204ab09b23e75cc8beae6 32288 
meson_0.44.1-1_amd64.buildinfo
Files:
 1e5667f7511ceca562483e874316f7be 3208 devel optional meson_0.44.1-1.dsc
 82b1198bf714b5a4da84bfe8376c79cc 1136478 devel optional 
meson_0.44.1.orig.tar.gz
 ca4727ec0fb8b2077c83c7ad1ac3f6b2 11676 devel optional 
meson_0.44.1-1.debian.tar.xz
 5ecdad7d24be35415d70469e073587ae 208492 devel optional meson_0.44.1-1_all.deb
 5bf22ff8673324437a4b3cf38f392839 32288 devel optional 
meson_0.44.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlqOqrkACgkQxrkYDUvY
t64Q5w//Ws48kHAhq8Z4oJITaSh0f6/K+qlK+t4Fh25B7SZ7CYtczrolSIPw+QLo
Qn2RJjNeBtxAJCiklOqnUJjMqKvGf3W+tZLOFA0i5FNLBdwpEn5fZ/PUIj93zyGl
dpoQ9FkTNoWvhv/8+XaEuPK4pmLSv9dGOx4eI9Szx2mNxo03BWfplFUOU5Qi6eVD
Q06faSbBi2ykg8Y5IZ0aOOwDFbln6zxGoSYkAmIItyYxkgAknmzB/66PWFzn/XT6
jTsyxzOZAFXCmjI/LLsYEc1RCqTJC0H1litLyqeUwDK+ocszKC0nFfZn3DPNpO/X
k6NEFUAEi5TayjFw5lD2lo5PlCwwN26ojeTrpTK2dalS7AdbAu3G38lCZAz1kOpq
WtarUPrbAg8Z+qXXCaOzinTBxwoq96H2k2Fc3Ks9oHK0uGN0eGrohMqoETzUvlWK
y+WioCWTlPdDnxekDldlPORYpRoAaDymWdFXQGFypeQRwd9WDkQMoAjpm0GO1KTr
mryUsFxIc5Xxf93/nkHr83hQpsylkUql7YDhtXYLnuF43QBPsLGT8rjtyFXqoc1o
qYAaGUntJ9pDXUDfnNjxVasf3GoerRwlnZOL19nwZ+BTXSbprxp+kQ+muNmVgZdX
QthKdbpHZckUBYqsMjbcjhFgkCwkDcLg7ObI4fDhhPDhum9ge60=
=PjAZ
-END PGP SIGNATURE End Message ---


Bug#872831: Bug #872831 in jackd2 marked as pending

2018-02-22 Thread mattia
Control: tag -1 pending

Hello,

Bug #872831 in jackd2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/jackd2/commit/543c170d8d19a8c9a84128a0fa01dc25c9ec1ecf


Revert "libjackserver is a private library and does not need to be exported"

It may even be a private library, but it's in a public namespace, so it
needs to be dealt with as public.

Closes: #872831
This reverts commit f1b2acff8fc96b2692206ecc2c0ac57043410569.



(this message was generated automatically)
-- 
Greetings



Processed: Re: Bug#891063: emacs25: dconf-CRITICAL errors

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 security
Bug #891063 [emacs25] emacs25: dconf-CRITICAL errors
Added tag(s) security.

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



Bug#891062: [Pkg-chromium-maint] Bug#891062: chromium: skia fails to build on arm64

2018-02-22 Thread Riku Voipio
On Wed, Feb 21, 2018 at 09:59:18PM -0500, Michael Gilbert wrote:
> Starting with chromium 65, arm64 fails while building skia.
> 
> ../../third_party/skia/src/jumper/SkJumper_stages.cpp: In function 'F
> from_half(U16)':
> ../../third_party/skia/src/jumper/SkJumper_stages.cpp:670:12: error:
> 'vcvt_f32_f16' was not declared in this scope
>  return vcvt_f32_f16(h);

Looking at the breaking change:

+// On ARM we expect that you're using Clang if you want SkJumper to be fast.
+// If you are, the baseline float stages will use NEON, and lowp stages will
+// also be available. (If somehow you're building for ARM not using Clang,
+// you'll get scalar baseline stages and no lowp support.)

Well clearly the fallback was not tested.



Bug#891110: usbauth-notifier: missing build dependency on libudev-dev

2018-02-22 Thread Adrian Bunk
Source: usbauth-notifier
Version: 1.0~git20180119-1
Severity: serious

https://buildd.debian.org/status/package.php?p=usbauth-notifier=sid

...
checking for USBAUTH... yes
checking for NOTIFY... yes
checking for UDEV... no
configure: error: Package requirements (libudev) were not met:

No package 'libudev' found



Bug#872831: marked as done (libjack-jackd2-0: provides public shared library (libjackserver.so) without shlibs information)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:19:38 +
with message-id 
and subject line Bug#872831: fixed in jackd2 1.9.10+20150825git1ed50c92~dfsg-6
has caused the Debian Bug report #872831,
regarding libjack-jackd2-0: provides public shared library (libjackserver.so) 
without shlibs information
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.)


-- 
872831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjack-jackd2-0
Version: 1.9.10+20150825git1ed50c92~dfsg-5
Severity: serious
Justification: Policy 8.6

Hi,

The libjack-jackd2-0 package provides this public shared library:
/usr/lib/x86_64-linux-gnu/libjackserver.so.0.1.0

However, it does not provide any shlibs or symbols information for it
thus violating Policy 8.6:

"... To allow these dependencies to be constructed, shared libraries
must provide either a symbols file or a shlibs file."

The shlibs file for libjack-jackd2-0 contains only this:
> $ cat /var/lib/dpkg/info/libjack-jackd2-0\:amd64.shlibs 
> libjack 0 libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125
> libjacknet 0 libjack-jackd2-0 (>= 1.9.5~dfsg-14)

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: jackd2
Source-Version: 1.9.10+20150825git1ed50c92~dfsg-6

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated jackd2 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, 22 Feb 2018 11:51:02 +0100
Source: jackd2
Binary: jackd2 libjack-jackd2-0 jackd2-firewire libjack-jackd2-dev
Architecture: source
Version: 1.9.10+20150825git1ed50c92~dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 jackd2 - JACK Audio Connection Kit (server and example clients)
 jackd2-firewire - JACK Audio Connection Kit (FFADO and FreeBoB backends)
 libjack-jackd2-0 - JACK Audio Connection Kit (libraries)
 libjack-jackd2-dev - JACK Audio Connection Kit (development files)
Closes: 853461 872831
Changes:
 jackd2 (1.9.10+20150825git1ed50c92~dfsg-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field.
   * d/control: Set Vcs-* to salsa.debian.org.
 .
   [ Mattia Rizzolo ]
   * Fix FTBFS with GCC 7.  Closes: #853461
   * Revert "libjackserver is a private library and does not need to be 
exported"
 It may even be a private library, but it's in a public namespace, so it
 needs to be dealt with as public.
 This reverts commit f1b2acff8fc96b2692206ecc2c0ac57043410569.
 Closes: #872831
Checksums-Sha1:
 e55cfe59731564632f9accb43994be1fb7b8a3e3 2650 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6.dsc
 0daf9d9310c4a213194cc4c8cb1b0597923c5558 40368 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6.debian.tar.xz
 a1979003f49317dc2438c33dff4a4cf1041b4c56 9526 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6_amd64.buildinfo
Checksums-Sha256:
 47aef1c695f78c7e0e203e254fa7b6572e9ab9eed4614b9640b13a030b3b51b4 2650 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6.dsc
 1dc579ce985a9e5cda9e980e4f80eb67586928336e8c8539b2d086cee0e31883 40368 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6.debian.tar.xz
 6ec7a85bd353efffe57a8f364eeeb14d1b439c84d9125f35a1ea3d40906c9e62 9526 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6_amd64.buildinfo
Files:
 afc902a23b9a39fba368cbaba6e22e87 2650 sound optional 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6.dsc
 32bad38f07a0ef615974ffbd13171df4 40368 sound optional 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6.debian.tar.xz
 67fa9202de9d5d28f7ec0d11ae4e 9526 sound optional 
jackd2_1.9.10+20150825git1ed50c92~dfsg-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlqOorAACgkQCBa54Yx2

Processed: Re: emacs25: dconf-CRITICAL errors

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 891063 When run as root, emacs reads/writes dconf files in a non-root 
> user's /run/user/XXX directory
Bug #891063 [emacs25] emacs25: dconf-CRITICAL errors
Changed Bug title to 'When run as root, emacs reads/writes dconf files in a 
non-root user's /run/user/XXX directory' from 'emacs25: dconf-CRITICAL errors'.
>
End of message, stopping processing here.

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



Bug#891063: emacs25: dconf-CRITICAL errors

2018-02-22 Thread Vincent Lefevre
Control: tags -1 security

On 2018-02-21 22:41:53 -0800, Rob Browning wrote:
> I'm not sure I understand yet how this makes Emacs unusable -- does it
> warn or crash?

I've looked at it more closely, and the problem seems to come from
that when Emacs is run as root after "su" (without using -m or -p),
it still tries to use the user's config and modify things there!
In particular, it can be tricked by the user to create a file
anywhere, like this:

-rw--- 1 root root 2 2018-02-22 12:26:14 /created-by-emacs

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#888779: marked as done (appstream-generator: FTBFS: meson: Subproject_dir must not contain a path segment)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:51:52 +
with message-id 
and subject line Bug#884627: fixed in meson 0.44.1-1
has caused the Debian Bug report #884627,
regarding appstream-generator: FTBFS: meson: Subproject_dir must not contain a 
path segment
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.)


-- 
884627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream-generator
Version: 0.6.8-2
Severity: serious

Hi,

On a rebuild against new libphobos, your package failed to build from source,
see:

https://buildd.debian.org/status/package.php?p=appstream-generator

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.44.1-1

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2018 00:02:07 +0200
Source: meson
Binary: meson
Architecture: source all
Version: 0.44.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 884627
Changes:
 meson (0.44.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #884627.
Checksums-Sha1:
 c854b26c0e8591be111d9edf43f8da16bf2bd4ca 3208 meson_0.44.1-1.dsc
 12d1d0466955da4f9a7ef158a23d4e37d985d667 1136478 meson_0.44.1.orig.tar.gz
 6b0afb08a619d2297c404c0bfc1bfb6bb4061523 11676 meson_0.44.1-1.debian.tar.xz
 5f60ee37fed20338e42e35df829bc1a351cc79ee 208492 meson_0.44.1-1_all.deb
 b697ebde5a28cd2e9997b814b4e880de4706324d 32288 meson_0.44.1-1_amd64.buildinfo
Checksums-Sha256:
 62080d9dbb1f643a0a6fe2281a7b18b09186ebd64a58db6792943a0305d8e078 3208 
meson_0.44.1-1.dsc
 2ea1a721574adb23160b6481191bcc1173f374e02b0ff3bb0ae85d988d97e4fa 1136478 
meson_0.44.1.orig.tar.gz
 10984a42d2bf8a41ffa9e7329ae075e64cbe3e1bd67f662cd6abc9e16a173dc3 11676 
meson_0.44.1-1.debian.tar.xz
 99d13fabc414c59db1919ae00df7363b36060699b3591d6868f091dae7bf2b0a 208492 
meson_0.44.1-1_all.deb
 8204389e7fdd4ba7464f041ac26c73644951496769e204ab09b23e75cc8beae6 32288 
meson_0.44.1-1_amd64.buildinfo
Files:
 1e5667f7511ceca562483e874316f7be 3208 devel optional meson_0.44.1-1.dsc
 82b1198bf714b5a4da84bfe8376c79cc 1136478 devel optional 
meson_0.44.1.orig.tar.gz
 ca4727ec0fb8b2077c83c7ad1ac3f6b2 11676 devel optional 
meson_0.44.1-1.debian.tar.xz
 5ecdad7d24be35415d70469e073587ae 208492 devel optional meson_0.44.1-1_all.deb
 5bf22ff8673324437a4b3cf38f392839 32288 devel optional 
meson_0.44.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlqOqrkACgkQxrkYDUvY
t64Q5w//Ws48kHAhq8Z4oJITaSh0f6/K+qlK+t4Fh25B7SZ7CYtczrolSIPw+QLo
Qn2RJjNeBtxAJCiklOqnUJjMqKvGf3W+tZLOFA0i5FNLBdwpEn5fZ/PUIj93zyGl
dpoQ9FkTNoWvhv/8+XaEuPK4pmLSv9dGOx4eI9Szx2mNxo03BWfplFUOU5Qi6eVD
Q06faSbBi2ykg8Y5IZ0aOOwDFbln6zxGoSYkAmIItyYxkgAknmzB/66PWFzn/XT6
jTsyxzOZAFXCmjI/LLsYEc1RCqTJC0H1litLyqeUwDK+ocszKC0nFfZn3DPNpO/X
k6NEFUAEi5TayjFw5lD2lo5PlCwwN26ojeTrpTK2dalS7AdbAu3G38lCZAz1kOpq
WtarUPrbAg8Z+qXXCaOzinTBxwoq96H2k2Fc3Ks9oHK0uGN0eGrohMqoETzUvlWK
y+WioCWTlPdDnxekDldlPORYpRoAaDymWdFXQGFypeQRwd9WDkQMoAjpm0GO1KTr
mryUsFxIc5Xxf93/nkHr83hQpsylkUql7YDhtXYLnuF43QBPsLGT8rjtyFXqoc1o
qYAaGUntJ9pDXUDfnNjxVasf3GoerRwlnZOL19nwZ+BTXSbprxp+kQ+muNmVgZdX
QthKdbpHZckUBYqsMjbcjhFgkCwkDcLg7ObI4fDhhPDhum9ge60=
=PjAZ
-END PGP SIGNATURE End Message ---


Processed: bug 890934 is forwarded to https://github.com/masterzen/winrm/issues/77

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 890934 https://github.com/masterzen/winrm/issues/77
Bug #890934 [src:golang-github-masterzen-winrm] golang-github-masterzen-winrm: 
FTBFS and Debci failure with golang-1.10-go
Set Bug forwarded-to-address to 'https://github.com/masterzen/winrm/issues/77'.
> thanks
Stopping processing here.

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



Bug#853461: marked as done (jackd2: ftbfs with GCC-7)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:19:38 +
with message-id 
and subject line Bug#853461: fixed in jackd2 1.9.10+20150825git1ed50c92~dfsg-6
has caused the Debian Bug report #853461,
regarding jackd2: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jackd2
Version: 1.9.10+20150825git1ed50c92~dfsg-4
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/jackd2_1.9.10+20150825git1ed50c92~dfsg-4_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

[...]
/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/config.h:20:0: 
warning: "HAVE_OPUS" redefined
 #define HAVE_OPUS 0
 
:0:0: note: this is the location of the previous definition

:0:0: warning: "HAVE_OPUS" redefined
:0:0: note: this is the location of the previous definition
In file included from ../common/JackConstants.h:24:0,
 from ../common/JackMidiPort.h:25,
 from ../common/JackNetTool.h:20,
 from ../common/JackNetTool.cpp:20:
/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/config.h:20:0: 
warning: "HAVE_OPUS" redefined
 #define HAVE_OPUS 0
 
:0:0: note: this is the location of the previous definition

:0:0: warning: "HAVE_OPUS" redefined
:0:0: note: this is the location of the previous definition
In file included from 
/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/common/JackConstants.h:24:0,
 from 
/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/posix/JackCompilerDeps_os.h:23,
 from ../common/JackCompilerDeps.h:23,
 from ../common/JackClientInterface.h:24,
 from ../common/JackDriver.h:25,
 from ../common/JackDriver.cpp:22:
/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/config.h:20:0: 
warning: "HAVE_OPUS" redefined
 #define HAVE_OPUS 0
 
:0:0: note: this is the location of the previous definition

:0:0: warning: "HAVE_OPUS" redefined
:0:0: note: this is the location of the previous definition
In file included from ../common/JackConstants.h:24:0,
 from ../common/JackMidiPort.h:25,
 from ../common/JackNetTool.h:20,
 from ../common/JackNetInterface.h:23,
 from ../common/JackNetManager.h:23,
 from ../common/JackNetManager.cpp:19:
/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/config.h:20:0: 
warning: "HAVE_OPUS" redefined
 #define HAVE_OPUS 0
 
:0:0: note: this is the location of the previous definition

Waf: Leaving directory 
`/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build'
Build failed
 -> task in 'jack_test' failed (exit status 1): 
{task 140585771894352: cxx test.cpp -> test.cpp.1.o}
['/usr/bin/g++', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-g', '-O2', 
'-fdebug-prefix-map=/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg=.', 
'-fstack-protector-strong', '-Wformat', '-Werror=format-security', 
'-fvisibility=hidden', '-Wall', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/linux', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/linux', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/posix', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/posix', 
'-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/common/jack', 

Processed: Bug #872831 in jackd2 marked as pending

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #872831 [libjack-jackd2-0] libjack-jackd2-0: provides public shared library 
(libjackserver.so) without shlibs information
Added tag(s) pending.

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



Bug#884627: marked as done (vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:51:52 +
with message-id 
and subject line Bug#884627: fixed in meson 0.44.1-1
has caused the Debian Bug report #884627,
regarding vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not contain a 
path segment
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.)


-- 
884627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vibe.d
Version: 0.8.1-2
Severity: serious

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

...
Source dir: /build/1st/vibe.d-0.8.1
Build dir: /build/1st/vibe.d-0.8.1/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson.build, line 1, column 0:
Subproject_dir must not contain a path segment.
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.44.1-1

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2018 00:02:07 +0200
Source: meson
Binary: meson
Architecture: source all
Version: 0.44.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 884627
Changes:
 meson (0.44.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #884627.
Checksums-Sha1:
 c854b26c0e8591be111d9edf43f8da16bf2bd4ca 3208 meson_0.44.1-1.dsc
 12d1d0466955da4f9a7ef158a23d4e37d985d667 1136478 meson_0.44.1.orig.tar.gz
 6b0afb08a619d2297c404c0bfc1bfb6bb4061523 11676 meson_0.44.1-1.debian.tar.xz
 5f60ee37fed20338e42e35df829bc1a351cc79ee 208492 meson_0.44.1-1_all.deb
 b697ebde5a28cd2e9997b814b4e880de4706324d 32288 meson_0.44.1-1_amd64.buildinfo
Checksums-Sha256:
 62080d9dbb1f643a0a6fe2281a7b18b09186ebd64a58db6792943a0305d8e078 3208 
meson_0.44.1-1.dsc
 2ea1a721574adb23160b6481191bcc1173f374e02b0ff3bb0ae85d988d97e4fa 1136478 
meson_0.44.1.orig.tar.gz
 10984a42d2bf8a41ffa9e7329ae075e64cbe3e1bd67f662cd6abc9e16a173dc3 11676 
meson_0.44.1-1.debian.tar.xz
 99d13fabc414c59db1919ae00df7363b36060699b3591d6868f091dae7bf2b0a 208492 
meson_0.44.1-1_all.deb
 8204389e7fdd4ba7464f041ac26c73644951496769e204ab09b23e75cc8beae6 32288 
meson_0.44.1-1_amd64.buildinfo
Files:
 1e5667f7511ceca562483e874316f7be 3208 devel optional meson_0.44.1-1.dsc
 82b1198bf714b5a4da84bfe8376c79cc 1136478 devel optional 
meson_0.44.1.orig.tar.gz
 ca4727ec0fb8b2077c83c7ad1ac3f6b2 11676 devel optional 
meson_0.44.1-1.debian.tar.xz
 5ecdad7d24be35415d70469e073587ae 208492 devel optional meson_0.44.1-1_all.deb
 5bf22ff8673324437a4b3cf38f392839 32288 devel optional 
meson_0.44.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlqOqrkACgkQxrkYDUvY
t64Q5w//Ws48kHAhq8Z4oJITaSh0f6/K+qlK+t4Fh25B7SZ7CYtczrolSIPw+QLo
Qn2RJjNeBtxAJCiklOqnUJjMqKvGf3W+tZLOFA0i5FNLBdwpEn5fZ/PUIj93zyGl
dpoQ9FkTNoWvhv/8+XaEuPK4pmLSv9dGOx4eI9Szx2mNxo03BWfplFUOU5Qi6eVD
Q06faSbBi2ykg8Y5IZ0aOOwDFbln6zxGoSYkAmIItyYxkgAknmzB/66PWFzn/XT6
jTsyxzOZAFXCmjI/LLsYEc1RCqTJC0H1litLyqeUwDK+ocszKC0nFfZn3DPNpO/X
k6NEFUAEi5TayjFw5lD2lo5PlCwwN26ojeTrpTK2dalS7AdbAu3G38lCZAz1kOpq
WtarUPrbAg8Z+qXXCaOzinTBxwoq96H2k2Fc3Ks9oHK0uGN0eGrohMqoETzUvlWK
y+WioCWTlPdDnxekDldlPORYpRoAaDymWdFXQGFypeQRwd9WDkQMoAjpm0GO1KTr
mryUsFxIc5Xxf93/nkHr83hQpsylkUql7YDhtXYLnuF43QBPsLGT8rjtyFXqoc1o
qYAaGUntJ9pDXUDfnNjxVasf3GoerRwlnZOL19nwZ+BTXSbprxp+kQ+muNmVgZdX
QthKdbpHZckUBYqsMjbcjhFgkCwkDcLg7ObI4fDhhPDhum9ge60=
=PjAZ
-END PGP SIGNATURE End Message ---


Bug#888780: marked as done (vibe.d: FTBFS: meson: Subproject_dir must not contain a path segment)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 11:51:52 +
with message-id 
and subject line Bug#884627: fixed in meson 0.44.1-1
has caused the Debian Bug report #884627,
regarding vibe.d: FTBFS: meson: Subproject_dir must not contain a path segment
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.)


-- 
884627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vibe.d
Version: 0.8.1-2
Severity: serious

On a rebuild against new libphobos, your package failed to build from source,
see:

https://buildd.debian.org/status/package.php?p=vibe.d

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.44.1-1

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2018 00:02:07 +0200
Source: meson
Binary: meson
Architecture: source all
Version: 0.44.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 884627
Changes:
 meson (0.44.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #884627.
Checksums-Sha1:
 c854b26c0e8591be111d9edf43f8da16bf2bd4ca 3208 meson_0.44.1-1.dsc
 12d1d0466955da4f9a7ef158a23d4e37d985d667 1136478 meson_0.44.1.orig.tar.gz
 6b0afb08a619d2297c404c0bfc1bfb6bb4061523 11676 meson_0.44.1-1.debian.tar.xz
 5f60ee37fed20338e42e35df829bc1a351cc79ee 208492 meson_0.44.1-1_all.deb
 b697ebde5a28cd2e9997b814b4e880de4706324d 32288 meson_0.44.1-1_amd64.buildinfo
Checksums-Sha256:
 62080d9dbb1f643a0a6fe2281a7b18b09186ebd64a58db6792943a0305d8e078 3208 
meson_0.44.1-1.dsc
 2ea1a721574adb23160b6481191bcc1173f374e02b0ff3bb0ae85d988d97e4fa 1136478 
meson_0.44.1.orig.tar.gz
 10984a42d2bf8a41ffa9e7329ae075e64cbe3e1bd67f662cd6abc9e16a173dc3 11676 
meson_0.44.1-1.debian.tar.xz
 99d13fabc414c59db1919ae00df7363b36060699b3591d6868f091dae7bf2b0a 208492 
meson_0.44.1-1_all.deb
 8204389e7fdd4ba7464f041ac26c73644951496769e204ab09b23e75cc8beae6 32288 
meson_0.44.1-1_amd64.buildinfo
Files:
 1e5667f7511ceca562483e874316f7be 3208 devel optional meson_0.44.1-1.dsc
 82b1198bf714b5a4da84bfe8376c79cc 1136478 devel optional 
meson_0.44.1.orig.tar.gz
 ca4727ec0fb8b2077c83c7ad1ac3f6b2 11676 devel optional 
meson_0.44.1-1.debian.tar.xz
 5ecdad7d24be35415d70469e073587ae 208492 devel optional meson_0.44.1-1_all.deb
 5bf22ff8673324437a4b3cf38f392839 32288 devel optional 
meson_0.44.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlqOqrkACgkQxrkYDUvY
t64Q5w//Ws48kHAhq8Z4oJITaSh0f6/K+qlK+t4Fh25B7SZ7CYtczrolSIPw+QLo
Qn2RJjNeBtxAJCiklOqnUJjMqKvGf3W+tZLOFA0i5FNLBdwpEn5fZ/PUIj93zyGl
dpoQ9FkTNoWvhv/8+XaEuPK4pmLSv9dGOx4eI9Szx2mNxo03BWfplFUOU5Qi6eVD
Q06faSbBi2ykg8Y5IZ0aOOwDFbln6zxGoSYkAmIItyYxkgAknmzB/66PWFzn/XT6
jTsyxzOZAFXCmjI/LLsYEc1RCqTJC0H1litLyqeUwDK+ocszKC0nFfZn3DPNpO/X
k6NEFUAEi5TayjFw5lD2lo5PlCwwN26ojeTrpTK2dalS7AdbAu3G38lCZAz1kOpq
WtarUPrbAg8Z+qXXCaOzinTBxwoq96H2k2Fc3Ks9oHK0uGN0eGrohMqoETzUvlWK
y+WioCWTlPdDnxekDldlPORYpRoAaDymWdFXQGFypeQRwd9WDkQMoAjpm0GO1KTr
mryUsFxIc5Xxf93/nkHr83hQpsylkUql7YDhtXYLnuF43QBPsLGT8rjtyFXqoc1o
qYAaGUntJ9pDXUDfnNjxVasf3GoerRwlnZOL19nwZ+BTXSbprxp+kQ+muNmVgZdX
QthKdbpHZckUBYqsMjbcjhFgkCwkDcLg7ObI4fDhhPDhum9ge60=
=PjAZ
-END PGP SIGNATURE End Message ---


Bug#891111: ctdconverter: missing build dependency on 2to3

2018-02-22 Thread Adrian Bunk
Source: ctdconverter
Version: 2.0-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=ctdconverter=all=2.0-2=1519291849=0

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
2to3 --write --nobackups convert.py galaxy/ cwl/ common/
make[1]: 2to3: Command not found
make[1]: *** [debian/rules:23: override_dh_auto_build] Error 127



Bug#891088: miniupnpd: modifies conffiles (policy 10.7.3): /etc/default/miniupnpd

2018-02-22 Thread Andreas Beckmann
Package: miniupnpd
Version: 2.0.20171212-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/#configuration-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/default/miniupnpd


cheers,

Andreas


miniupnpd_2.0.20171212-2.log.gz
Description: application/gzip


Bug#891018: marked as done (webcit: libical2 is obsolete and will be removed soon)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 10:20:51 +
with message-id 
and subject line Bug#891018: fixed in webcit 917-dfsg-2
has caused the Debian Bug report #891018,
regarding webcit: libical2 is obsolete and will be removed soon
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.)


-- 
891018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webcit
Version: 917-dfsg-1
Severity: serious
Tags: patch

libical2 is obsolete and will be removed soon.

Please change the build dependency to libical-dev
and add the attached patch.
--- webcit-917-dfsg.orig/calendar_tools.c
+++ webcit-917-dfsg/calendar_tools.c
@@ -151,7 +151,6 @@
t->minute = IBSTR(vname);
 
/* time zone is set to the default zone for this server */
-   t->is_utc = 0;
t->is_date = 0;
t->zone = get_default_icaltimezone();
 }
@@ -170,7 +169,7 @@
sscanf((char*)BSTR(prefix), "%04d-%02d-%02d", >year, >month, 
>day);
 
/* time zone is set to the default zone for this server */
-   t->is_utc = 1;
+   t->zone = icaltimezone_get_utc_timezone();
t->is_date = 1;
 }
 
--- webcit-917-dfsg.orig/calendar_view.c
+++ webcit-917-dfsg/calendar_view.c
@@ -198,7 +198,6 @@
starting_tm.tm_hour = 0;
starting_tm.tm_min = 0;
today_start_t = icaltime_from_timet_with_zone(mktime(_tm), 0, 
icaltimezone_get_utc_timezone());
-   today_start_t.is_utc = 1;
 
memset(_tm, 0, sizeof(struct tm));
ending_tm.tm_year = year - 1900;
@@ -207,7 +206,6 @@
ending_tm.tm_hour = 23;
ending_tm.tm_min = 59;
today_end_t = icaltime_from_timet_with_zone(mktime(_tm), 0, 
icaltimezone_get_utc_timezone());
-   today_end_t.is_utc = 1;
 
/*
 * Create another one without caring about the timezone for all day 
events.
@@ -854,7 +852,6 @@
starting_tm.tm_hour = 0;
starting_tm.tm_min = 0;
today_start_t = icaltime_from_timet_with_zone(mktime(_tm), 0, 
icaltimezone_get_utc_timezone());
-   today_start_t.is_utc = 1;
 
memset(_tm, 0, sizeof(struct tm));
ending_tm.tm_year = year - 1900;
@@ -863,7 +860,6 @@
ending_tm.tm_hour = 23;
ending_tm.tm_min = 59;
today_end_t = icaltime_from_timet_with_zone(mktime(_tm), 0, 
icaltimezone_get_utc_timezone());
-   today_end_t.is_utc = 1;
 
/*
 * Create another one without caring about the timezone for all day 
events.
--- webcit-917-dfsg.orig/event.c
+++ webcit-917-dfsg/event.c
@@ -264,8 +264,6 @@
((yesbstr("alldayevent")) ? 1 : 0),
icaltimezone_get_utc_timezone()
);
-   t_start.is_utc = 1;
-
}
display_icaltimetype_as_webform(_start, "dtstart", 0);
 
@@ -854,8 +852,8 @@
 
/* Add NOW() to the calendar object... */
icalcomponent_set_dtstamp(vevent,
- icaltime_from_timet(
- time(NULL), 0));
+ icaltime_from_timet_with_zone(
+ time(NULL), 0, 
icaltimezone_get_utc_timezone()));
 
if (havebstr("summary")) {
icalcomponent_add_property(vevent,
--- webcit-917-dfsg.orig/ical_dezonify.c
+++ webcit-917-dfsg/ical_dezonify.c
@@ -116,7 +116,7 @@
syslog(LOG_DEBUG, "* Was: %s\n", 
icaltime_as_ical_string(TheTime));
 #endif
 
-   if (TheTime.is_utc) {
+   if (icaltime_is_utc(TheTime)) {
 #ifdef DBG_ICAL
syslog(LOG_DEBUG, "* This property is ALREADY 
UTC.\n");
 #endif
@@ -126,7 +126,7 @@
 #ifdef DBG_ICAL
syslog(LOG_DEBUG, "* Replacing '%s' TZID with 
'Z' suffix.\n", tzid);
 #endif
-   TheTime.is_utc = 1;
+   TheTime.zone = icaltimezone_get_utc_timezone();
}
 
else {
@@ -146,7 +146,7 @@
t = get_default_icaltimezone();
}
icaltimezone_convert_time(, t, 
icaltimezone_get_utc_timezone());
-   TheTime.is_utc = 1;
+   TheTime.zone = icaltimezone_get_utc_timezone();
}
 
icalproperty_remove_parameter_by_kind(prop, ICAL_TZID_PARAMETER);
--- End Message ---
--- Begin Message ---
Source: webcit
Source-Version: 917-dfsg-2

We believe that the bug you reported is fixed in the latest version of
webcit, 

Bug#891016: marked as done (citadel: libical2 is obsolete and will be removed soon)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 10:19:28 +
with message-id 
and subject line Bug#891016: fixed in citadel 917-2
has caused the Debian Bug report #891016,
regarding citadel: libical2 is obsolete and will be removed soon
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.)


-- 
891016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: citadel
Version: 917-1
Severity: serious
Tags: patch

libical2 is obsolete and will be removed soon.

Please change the build dependency to libical-dev
and add the attached patch.
--- citadel-917.orig/ical_dezonify.c
+++ citadel-917/ical_dezonify.c
@@ -135,13 +135,13 @@
 
/* syslog(LOG_DEBUG, "* Was: %s\n", 
icaltime_as_ical_string(TheTime)); */
 
-   if (TheTime.is_utc) {
+   if (icaltime_is_utc(TheTime)) {
/* syslog(LOG_DEBUG, "* This property is 
ALREADY UTC.\n"); */
}
 
else if (utc_declared_as_tzid) {
/* syslog(LOG_DEBUG, "* Replacing '%s' TZID 
with 'Z' suffix.\n", tzid); */
-   TheTime.is_utc = 1;
+   TheTime.zone = icaltimezone_get_utc_timezone();
}
 
else {
@@ -161,7 +161,7 @@
t,
icaltimezone_get_utc_timezone()
);
-   TheTime.is_utc = 1;
+   TheTime.zone = icaltimezone_get_utc_timezone();
}
 
icalproperty_remove_parameter_by_kind(prop, ICAL_TZID_PARAMETER);
--- citadel-917.orig/modules/calendar/serv_calendar.c
+++ citadel-917/modules/calendar/serv_calendar.c
@@ -235,7 +235,7 @@
/* We found our own address in the attendee list. */
if (me_attend) {
/* Change the partstat from NEEDS-ACTION to ACCEPT or 
DECLINE */
-   icalproperty_remove_parameter(me_attend, 
ICAL_PARTSTAT_PARAMETER);
+   icalproperty_remove_parameter_by_kind(me_attend, 
ICAL_PARTSTAT_PARAMETER);
 
if (!strcasecmp(action, "accept")) {
partstat = 
icalparameter_new_partstat(ICAL_PARTSTAT_ACCEPTED);
@@ -1370,7 +1370,6 @@
if (!icaltime_is_null_time(dtend)) {
dtend = icaltime_add(dtstart, dur);
dtend.zone = dtstart.zone;
-   dtend.is_utc = dtstart.is_utc;
}
++num_recur;
}
@@ -1520,7 +1519,7 @@
icalcomponent_set_method(fb, ICAL_METHOD_PUBLISH);
 
/* Set the DTSTAMP to right now. */
-   icalcomponent_set_dtstamp(fb, icaltime_from_timet(time(NULL), 0));
+   icalcomponent_set_dtstamp(fb, icaltime_from_timet_with_zone(time(NULL), 
0, icaltimezone_get_utc_timezone()));
 
/* Add the user's email address as ORGANIZER */
sprintf(buf, "MAILTO:%s", who);
@@ -1541,10 +1540,10 @@
 * to yesterday and tomorrow as default values.
 */
if (icalcomponent_get_first_property(fb, ICAL_DTSTART_PROPERTY) == 
NULL) {
-   icalcomponent_set_dtstart(fb, 
icaltime_from_timet(time(NULL)-86400L, 0));
+   icalcomponent_set_dtstart(fb, 
icaltime_from_timet_with_zone(time(NULL)-86400L, 0, 
icaltimezone_get_utc_timezone()));
}
if (icalcomponent_get_first_property(fb, ICAL_DTEND_PROPERTY) == NULL) {
-   icalcomponent_set_dtend(fb, 
icaltime_from_timet(time(NULL)+86400L, 0));
+   icalcomponent_set_dtend(fb, 
icaltime_from_timet_with_zone(time(NULL)+86400L, 0, 
icaltimezone_get_utc_timezone()));
}
 
/* Put the freebusy component into the calendar component */
--- End Message ---
--- Begin Message ---
Source: citadel
Source-Version: 917-2

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

(This message was generated automatically at their request; if you
believe that there is a problem with it please 

Bug#891015: marked as done (citadel FTBFS with make 4.2.1)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 10:19:28 +
with message-id 
and subject line Bug#891015: fixed in citadel 917-2
has caused the Debian Bug report #891015,
regarding citadel FTBFS with make 4.2.1
to be marked as done.

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

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


-- 
891015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: citadel
Version: 917-1
Severity: serious
Tags: patch

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

...
make[1]: Leaving directory '/build/1st/citadel-917'
   dh_install
dh_install: Cannot find (any matches for) "etc/citadel/mail.aliases" (tried in 
., debian/tmp)

dh_install: citadel-server missing files: etc/citadel/mail.aliases
dh_install: missing files, aborting
make: *** [debian/rules:104: binary] Error 25


Fix is attached.
--- citadel-917/Makefile.in.old 2018-02-21 14:26:57.616140842 +
+++ citadel-917/Makefile.in 2018-02-21 14:27:10.620140718 +
@@ -231,7 +231,7 @@
$(srcdir)/mkinstalldirs $(DESTDIR)$(ETC_DIR)/
$(INSTALL_DATA) $(srcdir)/public_clients 
$(DESTDIR)$(ETC_DIR)/public_clients
$(INSTALL_DATA) $(srcdir)/citadel_urlshorteners.rc 
$(DESTDIR)$(ETC_DIR)/citadel_urlshorteners.rc
-   $(INSTALL_DATA) $(srcdir)/network/mail.aliases 
$(DESTDIR)$(ETC_DIR)/mail.aliases$
+   $(INSTALL_DATA) $(srcdir)/network/mail.aliases 
$(DESTDIR)$(ETC_DIR)/mail.aliases
 
$(srcdir)/mkinstalldirs $(DESTDIR)$(STATICDATA_DIR)/messages
@for i in  \
--- End Message ---
--- Begin Message ---
Source: citadel
Source-Version: 917-2

We believe that the bug you reported is fixed in the latest version of
citadel, 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.
Michael Meskes  (supplier of updated citadel 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, 22 Feb 2018 10:08:22 +0100
Source: citadel
Binary: citadel-server citadel-doc
Architecture: source all amd64
Version: 917-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Citadel Team 
Changed-By: Michael Meskes 
Description:
 citadel-doc - complete and feature-rich groupware server (documentation)
 citadel-server - complete and feature-rich groupware server
Closes: 891015 891016
Changes:
 citadel (917-2) unstable; urgency=medium
 .
   * Made VCS information points to salsa.
   * Switch build to libical3.
 Thanks to Adrian Bunk  (Closes: #891016)
   * Fix FTBFS with make 4.2.1.
 Thanks to Adrian Bunk  (Closes: #891015)
   * Get rid of recursive chown call in postinst.
Checksums-Sha1:
 c516f70bf9d621eb454bfde3552a289a68788df5 2252 citadel_917-2.dsc
 50c6b00f68e3c07db01d18894208b09039429a36 51215 citadel_917-2.diff.gz
 15e84f7f25ff338a87d6dbf04c21208797ec9449 44092 citadel-doc_917-2_all.deb
 ff2313abf5d34b6f916acb337dc6febaebc89a4c 2125444 
citadel-server-dbgsym_917-2_amd64.deb
 f2f20f9ccef0198443b866773c0ee8913f337634 332540 citadel-server_917-2_amd64.deb
 b135915329284ca7a2b3fbc712550a8a057eb06b 7536 citadel_917-2_amd64.buildinfo
Checksums-Sha256:
 daef4219eff24d9c8af10c7a554fb0831ce8a1d3d5e9d300c071c1d12bbf0ae9 2252 
citadel_917-2.dsc
 894c6156c83dc8fd02f830c5710efcf3614620d8c24889c9941115d5aae04650 51215 
citadel_917-2.diff.gz
 fef976676502619d437054fe7855f5a045743147c458f011082ffdcefe77028e 44092 
citadel-doc_917-2_all.deb
 c731b28be01982809f5e83eb9bb1fec63795c4b344318e5b0661c400fad8134b 2125444 
citadel-server-dbgsym_917-2_amd64.deb
 c78bb6527e2900b10bcc30f232eff6595b14eafdd2a2a33db9391410d18b4095 332540 
citadel-server_917-2_amd64.deb
 5a36c93dfc9a962d452107567874f8e236b982e68aa5d38528b93cba3c887c2c 7536 
citadel_917-2_amd64.buildinfo
Files:
 21ae2b7db26da8472344a0645cd779be 2252 mail optional citadel_917-2.dsc
 2e58457347d11542bfc89aa6a37f45aa 51215 mail optional citadel_917-2.diff.gz
 289d90a79316a11b5862bd3b07c90e69 44092 doc optional citadel-doc_917-2_all.deb
 

Bug#853461: Bug #853461 in jackd2 marked as pending

2018-02-22 Thread mattia
Control: tag -1 pending

Hello,

Bug #853461 in jackd2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/jackd2/commit/5ce69ced691734b8f57398a83edf9a457f8e837a


Fix FTBFS with GCC 7.

Closes: #853461
Signed-off-by: Mattia Rizzolo 



(this message was generated automatically)
-- 
Greetings



Processed: Bug #853461 in jackd2 marked as pending

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #853461 [src:jackd2] jackd2: ftbfs with GCC-7
Added tag(s) pending.

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



Bug#891085: aseba-plugin-blockly: missing build-dependency for python2

2018-02-22 Thread Andreas Beckmann
Source: aseba-plugin-blockly
Version: 20180211+git-1
Severity: serious
Justification: fails to build from source

Hi,

aseba-plugin-blockly FTBFS since it uses python2 without depending on
it:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/aseba-plugin-blockly-20180211+git'
mkdir build
bash build.sh build/blocky.zip
+++ dirname build.sh
++ cd .
++ pwd
+ SRC_DIR=/build/aseba-plugin-blockly-20180211+git
+ BUILD_DIR=/build/aseba-plugin-blockly-20180211+git
++ mktemp -d
+ TEMP_DIR=/tmp/tmp.QJhv5lK8jV
+ trap atexit EXIT
+ cp -r /build/aseba-plugin-blockly-20180211+git/blockly 
/build/aseba-plugin-blockly-20180211+git/closure-library 
/build/aseba-plugin-blockly-20180211+git/thymio_blockly 
/build/aseba-plugin-blockly-20180211+git/index.html 
/build/aseba-plugin-blockly-20180211+git/media /tmp/tmp.QJhv5lK8jV
+ ARCHIVE=/build/aseba-plugin-blockly-20180211+git/blockly.zip
+ '[' '!' -z build/blocky.zip ']'
++ realpath build/blocky.zip
+ ARCHIVE=/build/aseba-plugin-blockly-20180211+git/build/blocky.zip
+ '[' -f /build/aseba-plugin-blockly-20180211+git/build/blocky.zip ']'
+ pushd /tmp/tmp.QJhv5lK8jV
/tmp/tmp.QJhv5lK8jV /build/aseba-plugin-blockly-20180211+git
+ pushd blockly
/tmp/tmp.QJhv5lK8jV/blockly /tmp/tmp.QJhv5lK8jV 
/build/aseba-plugin-blockly-20180211+git
+ echo 'Compiling blockly'
Compiling blockly
+ python2 ./build.py
build.sh: line 33: python2: command not found
+ atexit
+ rm -rf /tmp/tmp.QJhv5lK8jV
make[1]: *** [debian/rules:24: override_dh_auto_build] Error 127
make[1]: Leaving directory '/build/aseba-plugin-blockly-20180211+git'


Andreas


aseba-plugin-blockly_20180211+git-1.log.gz
Description: application/gzip


Bug#828557: marked as done (sslsniff: FTBFS with openssl 1.1.0)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 10:06:22 +
with message-id 
and subject line Bug#828557: fixed in sslsniff 0.8-7
has caused the Debian Bug report #828557,
regarding sslsniff: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sslsniff
Version: 0.8-4.2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/sslsniff_0.8-4.2_amd64-20160529-1540

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: sslsniff
Source-Version: 0.8-7

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated sslsniff 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, 22 Feb 2018 10:40:16 +0100
Source: sslsniff
Binary: sslsniff
Architecture: source
Version: 0.8-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Raphaël Hertzog 
Description:
 sslsniff   - SSL/TLS man-in-the-middle attack tool
Closes: 828557
Changes:
 sslsniff (0.8-7) unstable; urgency=medium
 .
   * Add patch to build against openssl 1.1. Closes: #828557
 Thanks to Hilko Bengen  for the patch.
   * Update Build-Depends to build against openssl 1.1.
   * Switch to debhelper compat level 11.
   * Change priority to optional.
   * Bump Standards-Version to 4.1.3.
   * Update Vcs-* fields for move to salsa.debian.org.
Checksums-Sha1:
 daa864d5ef4a09c574de57eb27fe604811c48083 1759 sslsniff_0.8-7.dsc
 88338144f159519941ce54c8ce21a44ef1781aea 7032 sslsniff_0.8-7.debian.tar.xz
 f8bfa295a630206241cc04f574b0b96c499082a7 5445 sslsniff_0.8-7_source.buildinfo
Checksums-Sha256:
 92a4fd1952ba36053d987514a334bc2d0f5c29cacc94e77dd6b9022ed419003f 1759 
sslsniff_0.8-7.dsc
 378884a1e42f4b3d610b10d30eacce87bed38a824e34f2ee47e475dda18b485b 7032 
sslsniff_0.8-7.debian.tar.xz
 1a522746ee470e4f48d0d580fb08f7798c3edaac69928375425aeb64115bbcd4 5445 
sslsniff_0.8-7_source.buildinfo
Files:
 122fdc465b48d1c624b8f98794d797dc 1759 admin optional sslsniff_0.8-7.dsc
 a16f9a4faee30e8f0bc2d910d3a2a0cf 7032 admin optional 
sslsniff_0.8-7.debian.tar.xz
 16d435fa754450d58aa1d1051dd15c96 5445 admin optional 
sslsniff_0.8-7_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAlqOkwEACgkQA4gdq+vC
mrlyDggAsFFuJl39tdT0LJbM0bejZEnXjGk2Tnrjiu1QRgk/Nm+53PxQSmlHFVRh
BYAYwUHNJsjEaJoPh8OI/01LaAf/XJJYjzzMjtREWx8JjYaArUjopsWiuFZNAsx1
ZLDiCWOHXrbzs9mhXCmmPFCHW5aLLs2x9YppUlm3NvJQ4B01n0sWbR6/XfMh/Jz6
PO7mC8F9q8lUGl+YeMEwMkZ9BWKKErgRWZrosbQ9616fOCLab05CvdzE5CiLoUXX
Rz/pqNA61jYNDY4Fd1Lb/aK04mfvdzwf4hGWO5EenOXTY0MmUHVLsg2Hm5g5XKvK
G3p6uCAEuUbL4VHH69QIs3lZXy/Riw==
=QtG+
-END PGP SIGNATURE End Message ---


Bug#828557: Bug #828557 in sslsniff marked as pending

2018-02-22 Thread hertzog
Control: tag -1 pending

Hello,

Bug #828557 in sslsniff 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/pkg-security-team/sslsniff/commit/08422d74f47a3399a29ee18c6de71324ad24fdbd


Add patch to build against openssl 1.1. Closes: #828557 Thanks to Hilko Bengen 
 for the patch.



(this message was generated automatically)
-- 
Greetings



Processed: Bug #828557 in sslsniff marked as pending

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #828557 [src:sslsniff] sslsniff: FTBFS with openssl 1.1.0
Added tag(s) pending.

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



Processed: Re: Bug#891049: pgmodeler: version in stretch incompatible with db version in stretch

2018-02-22 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #891049 [pgmodeler] pgmodeler: version in stretch incompatible with db 
version in stretch
Severity set to 'serious' from 'normal'

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



Bug#891049: marked as done (pgmodeler: version in stretch incompatible with db version in stretch)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 10:19:23 +0100
with message-id <20180222091923.ga20...@msg.df7cb.de>
and subject line Re: Bug#891049: pgmodeler: version in stretch incompatible 
with db version in stretch
has caused the Debian Bug report #891049,
regarding pgmodeler: version in stretch incompatible with db version in stretch
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.)


-- 
891049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgmodeler
Version: 0.8.2-1+b1
Severity: normal


Hi!

I would like to use pgmodeler in Stretch, but the program can't work
with PostgreSQL 9.6, also in Stretch. I get an error message that only
versions up to 9.5 are supported, and that's the end of the story.


Cheers,
Toni



-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pgmodeler depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libpq59.6.6-0+deb9u1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-2.2+deb9u2
ii  pgmodeler-common  0.8.2-1

pgmodeler recommends no packages.

pgmodeler suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: severity -1 serious
Version: 0.9.1~beta-1

Re: Toni Mueller 2018-02-21 
<151925212500.8837.9009431344134188619.report...@spruce.office.oeko.net>
> I would like to use pgmodeler in Stretch, but the program can't work
> with PostgreSQL 9.6, also in Stretch. I get an error message that only
> versions up to 9.5 are supported, and that's the end of the story.

Oops.

We've only recently imported pgmodeler into the PostgreSQL team, so
obviously this incompatibility fell through the cracks. Sorry.

I don't see that we can realistically upgrade pgmodeler in stretch, so
there's two workarounds available: using pgmodeler from buster, or use
the stretch-pgdg distribution from apt.postgresql.org.

Christoph--- End Message ---


Bug#889533: marked as done (leiningen-clojure FTBFS with libclojure-java 1.9.0~alpha15-1)

2018-02-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Feb 2018 09:00:11 +
with message-id 
and subject line Bug#889533: fixed in clojure1.8 1.8.0-4
has caused the Debian Bug report #889533,
regarding leiningen-clojure FTBFS with libclojure-java 1.9.0~alpha15-1
to be marked as done.

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

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


-- 
889533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leiningen-clojure
Version: 2.8.1-4
Severity: serious

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

...
dh_auto_build -- -f leiningen-core/pom.xml install
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/leiningen-clojure-2.8.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/leiningen-clojure-2.8.1/debian 
-Dmaven.repo.local=/build/1st/leiningen-clojure-2.8.1/debian/maven-repo 
--batch-mode -f leiningen-core/pom.xml install -DskipTests -Dnotimestamp=true 
-Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building leiningen-core 2.8.1
[INFO] 
[WARNING] The POM for org.clojure:clojure:jar:1.8.x is missing, no dependency 
information available
[WARNING] The POM for org.clojure:clojure:jar:debian is missing, no dependency 
information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.680 s
[INFO] Finished at: 2019-03-07T17:33:50-12:00
[INFO] Final Memory: 16M/724M
[INFO] 
[ERROR] Failed to execute goal on project leiningen-core: Could not resolve 
dependencies for project leiningen-core:leiningen-core:jar:2.8.1: Cannot access 
central (https://repo1.maven.org/maven2/) in offline mode and the artifact 
org.clojure:clojure:jar:1.8.x has not been downloaded from it before. -> [Help 
1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/leiningen-clojure-2.8.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/leiningen-clojure-2.8.1/debian 
-Dmaven.repo.local=/build/1st/leiningen-clojure-2.8.1/debian/maven-repo 
--batch-mode -f leiningen-core/pom.xml install -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
debian/rules:63: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: clojure1.8
Source-Version: 1.8.0-4

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

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated clojure1.8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 11:43:56 -0600
Source: clojure1.8
Binary: clojure1.8 libclojure1.8-java
Architecture: source all
Version: 1.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: 

Processed: setting fixed version for 888558

2018-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 888558 python-backports.tempfile/1.0-2
Bug #888558 {Done: Andreas Tille } 
[python-backports.tempfile] python-backports.tempfile: ships file with generic 
name: /usr/lib/python2.7/dist-packages/backports/__init__.py
Marked as fixed in versions python-backports.tempfile/1.0-2.
> thanks
Stopping processing here.

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



Bug#890934: [pkg-go] Bug#890934: golang-github-masterzen-winrm: FTBFS and Debci failure with golang-1.10-go

2018-02-22 Thread Michael Stapelberg
This issue is tracked upstream at
https://github.com/masterzen/winrm/issues/77

On Tue, Feb 20, 2018 at 8:09 PM, Adrian Bunk  wrote:

> Source: golang-github-masterzen-winrm
> Version: 0.0~git20170601.0.1ca0ba6-2
> Severity: serious
>
> https://ci.debian.net/packages/g/golang-github-masterzen-winrm/unstable/
> amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/golang-github-masterzen-winrm.html
>
> ...
>dh_auto_test -O--buildsystem=golang
> cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16
> github.com/masterzen/winrm github.com/masterzen/winrm/soap
> === RUN   Test
>
> --
> FAIL: golang-github-masterzen-winrm_0.0~git20170601.0.1ca0ba6-2/
> obj-x86_64-linux-gnu/src/github.com/masterzen/winrm/client_test.go:89:
> WinRMSuite.TestRunWithString
>
> golang-github-masterzen-winrm_0.0~git20170601.0.1ca0ba6-2/
> obj-x86_64-linux-gnu/src/github.com/masterzen/winrm/client_test.go:100:
> ...open golang-github-masterzen-winrm_0.0~git20170601.0.1ca0ba6-2/
> obj-x86_64-linux-gnu/src/github.com/masterzen/winrm/client_test.go: no
> such file or directory
> ... obtained string = "That's all folks!!!\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
>  \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
>  x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
> x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"
> ... expected string = "That's all folks!!!"
>
> OOPS: 36 passed, 1 FAILED
> --- FAIL: Test (5.25s)
> FAIL
> FAILgithub.com/masterzen/winrm  5.282s
> === RUN   Test
> OK: 6 passed
> --- PASS: Test (0.01s)
> === RUN   TestAddUsualNamespaces
> --- PASS: TestAddUsualNamespaces (0.00s)
> === RUN   TestSetTo
> --- PASS: TestSetTo (0.00s)
> PASS
> ok  github.com/masterzen/winrm/soap 0.027s
> dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16
> github.com/masterzen/winrm github.com/masterzen/winrm/soap returned exit
> code 1
> make: *** [debian/rules:6: build] Error 1
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael


Bug#890939: [pkg-go] Bug#890939: etcd FTBFS

2018-02-22 Thread Michael Stapelberg
Half of this issue can be fixed by re-generating the codec files by setting
“export DH_GOLANG_GO_GENERATE := 1” in debian/rules and adding a
Build-Depends: golang-github-ugorji-go-codec to debian/control.

I haven’t figured out how to re-generate the remaining (failing) files yet.

On Tue, Feb 20, 2018 at 8:57 PM, Adrian Bunk  wrote:

> Source: etcd
> Version: 3.2.9+dfsg-3
> Severity: serious
> Control: affects -1 src:docker-libkv src:golang-github-spf13-viper
> src:golang-github-xordataexchange-crypt src:skydns
>
> Some recent change in unstable makes etcd FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/etcd.html
> https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/etcd.html
>
> ...
> github.com/coreos/etcd/mvcc
> # github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:147:39: not enough arguments in call
> to runtime.AnnotateContext
> have ("golang.org/x/net/context".Context, *http.Request)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> *http.Request)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:149:21: not enough arguments in call
> to runtime.HTTPError
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, error)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> runtime.Marshaler, http.ResponseWriter, *http.Request, error)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:154:21: not enough arguments in call
> to runtime.HTTPError
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, error)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> runtime.Marshaler, http.ResponseWriter, *http.Request, error)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:158:30: not enough arguments in call
> to forward_Election_Campaign_0
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, proto.Message, []func("
> golang.org/x/net/context".Context, http.ResponseWriter, proto.Message)
> error...)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> runtime.Marshaler, http.ResponseWriter, *http.Request, proto.Message,
> ...func("golang.org/x/net/context".Context, http.ResponseWriter,
> proto.Message) error)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:175:39: not enough arguments in call
> to runtime.AnnotateContext
> have ("golang.org/x/net/context".Context, *http.Request)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> *http.Request)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:177:21: not enough arguments in call
> to runtime.HTTPError
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, error)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> runtime.Marshaler, http.ResponseWriter, *http.Request, error)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:182:21: not enough arguments in call
> to runtime.HTTPError
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, error)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> runtime.Marshaler, http.ResponseWriter, *http.Request, error)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:186:30: not enough arguments in call
> to forward_Election_Proclaim_0
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, proto.Message, []func("
> golang.org/x/net/context".Context, http.ResponseWriter, proto.Message)
> error...)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> runtime.Marshaler, http.ResponseWriter, *http.Request, proto.Message,
> ...func("golang.org/x/net/context".Context, http.ResponseWriter,
> proto.Message) error)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:203:39: not enough arguments in call
> to runtime.AnnotateContext
> have ("golang.org/x/net/context".Context, *http.Request)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> *http.Request)
> src/github.com/coreos/etcd/etcdserver/api/v3election/
> v3electionpb/gw/v3election.pb.gw.go:205:21: not enough arguments in call
> to runtime.HTTPError
> have ("golang.org/x/net/context".Context, runtime.Marshaler,
> http.ResponseWriter, *http.Request, error)
> want ("golang.org/x/net/context".Context, *runtime.ServeMux,
> 

Bug#891063: emacs25: dconf-CRITICAL errors

2018-02-22 Thread Vincent Lefevre
On 2018-02-21 22:41:53 -0800, Rob Browning wrote:
> Vincent Lefevre  writes:
> 
> > Package: emacs25
> > Version: 25.2+1-6+b1
> > Severity: grave
> > Justification: renders package unusable
> 
> I'm not sure I understand yet how this makes Emacs unusable -- does it
> warn or crash?

Well, there are critical errors. So this must be really important.
I'm wondering whether this may cause data corruption.

Moreover, each time I start emacs, it takes 24 lines of the terminal
due to these errors, hiding important information.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#889539: pandas FTBFS: test failures

2018-02-22 Thread Lumin
Yaroslav has just uploaded pandas 0.22.0, let's see if this problem
still exists.

On 7 February 2018 at 14:57, Andreas Tille  wrote:
> On Tue, Feb 06, 2018 at 03:51:27PM +, Lumin wrote:
>> Apart from that, the pandas packaging needs a patch [2] to reduce
>> autopkgtest failures.
>
> As always:  Please push your patches. :-)
> You and I are in the same position: We are team members of the maintainer
> team.  I even have the strong impression, that you are the more competent
> team member than me in terms of pandas.  So please do not be shy. ;-)
>
> Thanks a lot and feel to keep on pushing promising patches
>
> Andreas.
>
>> [2]
>> diff --git a/debian/tests/control b/debian/tests/control
>> index 38521c8..ab54101 100644
>> --- a/debian/tests/control
>> +++ b/debian/tests/control
>> @@ -15,6 +15,7 @@ Depends: python-all,
>>   python-xlwt,
>>   python-bs4,
>>   python-html5lib,
>> + python-pytest,
>>   xauth,
>>   xvfb
>>
>> @@ -29,5 +30,6 @@ Depends: python3-all,
>>   python3-tk,
>>   python3-tz,
>>   python3-bs4,
>> + python3-pytest,
>>   xauth,
>>   xvfb
>
> --
> http://fam-tille.de



-- 
Best,