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

[Pirate Praveen]

On Sun, 25 Feb 2018 14:47:19 +1100 Ben Finney  wrote:
> On 25-Feb-2018, Balasankar C wrote:
> 
> > Note: I have enabled the atwho JS file from cloudflare CDN in it.
> 
> How is that related to the upstream source?

These days most browser libraries are developed in a node.js environment
and the output of these source files are generated by tools (module
bundlers) like browserify, rollup and webpack (in this particular case I
think gulp-umd + gulp-concat and other gulp plugins).

cloudflare CDN is distributing the output of these source files
(generated using gulp). Because browsers don't implement all APIs of
Nodejs, we cannot directly use these source files, but need to use a
module bundler like webpack (we have two module bundlers in debian now -
webpack and rollup). I have been replacing many of the build scripts to
use webpack instead of rollup for some time (as rollup was accepted only
a week back).

Many times, there is also an extra step of transpiling before we can
bundle the modules. A transpiler like babel or buble (both now available
in main), convert code written in ES6 version of javascript to ES5 that
browsers understand. In this particular case, we don't have the
transpile step and we directly bundle the modules using gulp-umd and
gulp-concat.



signature.asc
Description: OpenPGP digital signature

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

[Balasankar C]

Hi,


On Sun, 25 Feb 2018 14:47:19 +1100 Ben Finney  wrote:
> On 25-Feb-2018, Balasankar C wrote:
> 
> > Note: I have enabled the atwho JS file from cloudflare CDN in it.
> 
> How is that related to the upstream source?

You can ignore that. I just wanted to demo a working copy first so that
we can see how switching to the packaged one broke the test. Hence made
use of the CDN. It was only meant to show "Upstream one works, packaged
one doesn't.". :)

PS: In case you were asking how the CDN is related to upstream, check
this link: https://cdnjs.com/libraries/at.js . It hosts all the versions
of the library in a central location that websites can use via 

Bug#891395: libfabric1: improperly packaged library support files

[Helmut Grohne]

Package: libfabric1
Version: 1.5.3-1
Severity: serious
Justification: policy 8.2

libfabric1 ships /usr/bin/fi_{info,pingpong,strerror}. These files are
independent of the soname of the library. Debian policy section 8.2
prohibits such files from being shipped in the shared library package.
The typical solution is to split them out into a package named e.g.
libfabric-bin. Thus when libfabric bumps its soname, libfabric-bin would
get taken over by the newer package while libfabric1 and e.g. libfabric2
would remain coinstallable.

Helmut

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

[Pirate Praveen]

On Sun, 25 Feb 2018 15:03:45 +1100 Ben Finney  wrote:
> On 15-Feb-2018, Pirate Praveen wrote:
> 
> > wget `npm view at.js dist.tarball` will get you the dist tarball.
> > Compare dist/js/jquery.atwho.js in the tarball with the file installed
> > by the debian package.
> 
> (There is no ‘npm’ in Debian Buster yet, so I'm not easily able to get
> anything from NPM.)

You can just use wget to get the files from npm registry.

$ npm view at.js dist.tarball
https://registry.npmjs.org/at.js/-/at.js-1.5.3.tgz

(it is the same pattern for all npm modules)

$ wget https://registry.npmjs.org/at.js/-/at.js-1.5.3.tgz

> Looking at the ‘/usr/share/javascript/jquery-atwho/jquery.atwho.js’
> file installed by the Debian package, I see that the Reference Error
> is because ‘Controller’ is defined in a different scope.
> 
> As you have suggested, the custom build rules in the Debian package
> were implemented before we had Gulp in Debian. So the build process
> may be to blame for the error behaviour.
> 
> What should be done in this package to use the ‘gulpfile.js’ tasks,
> now that Gulp is available in Debian?

https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt

You can just call gulp from debian/rules. But you may need to package
some gulp plugins or embed them
https://wiki.debian.org/Javascript/Nodejs/Npm2Deb#Embedding_some_modules
some of them plugins you may be able to skip.

$ npm2deb depends  -r at.js
Module at.js has no dependencies.
Build dependencies:
NPM   Debian
gulp (^3.9.0) node-gulp (3.9.1-6)
gulp-bump (^1.0.0)None
gulp-coffee (^2.3.1)  node-gulp-coffee (2.3.4-1)
gulp-concat (^2.6.0)  node-gulp-concat (2.6.1-1)
gulp-cssmin (^0.1.7)  None
gulp-debug (^2.1.2)   None
gulp-header (^1.7.1)  None
gulp-jasmine (^2.2.1) None
gulp-jasmine-phantom (^2.0.1) None
gulp-rename (^1.2.2)  node-gulp-rename (1.2.2-1)
gulp-uglify (^1.5.1)  None
gulp-umd (^0.2.0) None
gulp-util (^3.0.7)node-gulp-util (3.0.7-1)
jasmine-ajax (^3.2.0) None
jasmine-jquery (^2.1.1)   None
phantomjs (^1.9.19)   None

We can skip phantomjs and jasmine in the first iteration and enable
tests later. For skipping some modules, you have to patch the gulpfile.js.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#889471: libcairo-perl: FTBFS: t/CairoSurface.t failure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libcairo2 1.15.10-1
Bug #889471 [libcairo-perl] libcairo-perl: FTBFS: t/CairoSurface.t failure
Bug reassigned from package 'libcairo-perl' to 'libcairo2'.
No longer marked as found in versions libcairo-perl/1.106-2.
Ignoring request to alter fixed versions of bug #889471 to the same values 
previously set
Bug #889471 [libcairo2] libcairo-perl: FTBFS: t/CairoSurface.t failure
Marked as found in versions cairo/1.15.10-1.
> retitle -1 cairo: PNG handling regression in 1.15.10
Bug #889471 [libcairo2] libcairo-perl: FTBFS: t/CairoSurface.t failure
Changed Bug title to 'cairo: PNG handling regression in 1.15.10' from 
'libcairo-perl: FTBFS: t/CairoSurface.t failure'.
> tag -1 patch fixed-upstream
Bug #889471 [libcairo2] cairo: PNG handling regression in 1.15.10
Added tag(s) patch and fixed-upstream.
> affects -1 libcairo-perl
Bug #889471 [libcairo2] cairo: PNG handling regression in 1.15.10
Added indication that 889471 affects libcairo-perl

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

Bug#889471: libcairo-perl: FTBFS: t/CairoSurface.t failure

[Niko Tyni]

Control: reassign -1 libcairo2 1.15.10-1
Control: retitle -1 cairo: PNG handling regression in 1.15.10
Control: tag -1 patch fixed-upstream
Control: affects -1 libcairo-perl 

On Sat, Feb 03, 2018 at 07:55:23PM +0200, Niko Tyni wrote:
> On Sat, Feb 03, 2018 at 07:19:24PM +0200, Niko Tyni wrote:
> > Package: libcairo-perl
> > Version: 1.106-2
> > Severity: serious
> > User: debian-p...@lists.debian.org
> > Usertags: autopkgtest
> > 
> > As noticed by ci.debian.net, the test suite of this package
> > recently started failing.
> > 
> >   Test Summary Report
> >   ---
> >   t/CairoSurface.t (Wstat: 139 Tests: 41 Failed: 0)
> > Non-zero wait status: 139
> > Parse errors: Bad plan.  You planned 88 tests but ran 41.
> >   Files=9, Tests=256,  0 wallclock secs ( 0.08 usr  0.00 sys +  0.58 cusr  
> > 0.05 csys =  0.71 CPU)
> >   Result: FAIL
> >  
> > Timing suggests src:cairo (1.15.8-3 -> 1.15.10-1) as the probable cause
> > for this regression.
> 
> Confirmed by downgrading libcairo2; that makes the test suite pass again.

This seems to be similar to https://bugs.freedesktop.org/show_bug.cgi?id=104325
as my tests indicate that the corresponding fix

 
https://cgit.freedesktop.org/cairo/commit/?id=82f4028532c11152a0110f1b277e3358dfca6545

also fixes the libcairo-perl test suite crash.

Reassigning accordingly.
-- 
Niko Tyni   nt...@debian.org

Bug#890743: marked as done (libfl-dev: missing dependency on libfl2)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2018 06:19:32 +
with message-id 
and subject line Bug#890743: fixed in flex 2.6.4-6
has caused the Debian Bug report #890743,
regarding libfl-dev: missing dependency on libfl2
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.)


-- 
890743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfl-dev
Version: 2.6.4-5
Severity: serious

The libfl.so symlink is dangling if libfl2 is not installed:

,
| $ file /usr/lib/i386-linux-gnu/libfl.so
| /usr/lib/i386-linux-gnu/libfl.so: broken symbolic link to libfl.so.2.0.0
`

This makes the new libfl2 rather useless, since nothing will ever depend
to it.


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

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

Versions of packages libfl-dev depends on:
ii  flex  2.6.4-5

libfl-dev recommends no packages.

libfl-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flex
Source-Version: 2.6.4-6

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Feb 2018 15:25:10 -0800
Source: flex
Binary: flex flex-doc libfl2 libfl-dev
Architecture: source amd64 all
Version: 2.6.4-6
Distribution: unstable
Urgency: medium
Maintainer: Manoj Srivastava 
Changed-By: Manoj Srivastava 
Description:
 flex   - fast lexical analyzer generator
 flex-doc   - Documentation for flex (a fast lexical analyzer generator)
 libfl-dev  - static library for flex (a fast lexical analyzer generator)
 libfl2 - SHARED library for flex (a fast lexical analyzer generator)
Closes: 890608 890703 890714 890743
Changes:
 flex (2.6.4-6) unstable; urgency=medium
 .
   * Rolled back the feature test POSIX_C_SOURCE changes.
   * Bug fix: "libfl-dev lost libl.a symlink", thanks to Bas Couwenberg
 (Closes: #890608). Made sure the link actually did make it to the
 .deb
   * Bug fix: "Incomplete debian/copyright?", thanks to Chris Lamb (Closes:
 #890714). Updated copyright using automation tools
   * Bug fix: "missing dependency on libfl2", thanks to Sven Joachim
 (Closes: #890743). Updated contreol
   * Bug fix: "all amd64 binaries since 2.6.4-1 built with stale skel.c
 file", thanks to James Cowgill (Closes: #890703).
Checksums-Sha1:
 a9c452d00395da6ee47991655f581265e4ef7273 2044 flex_2.6.4-6.dsc
 929b003d619dc31ab070e1a130ddf1241435ef5c 59099 flex_2.6.4-6.diff.gz
 3cbd737de7635872748d46727b77d7b6efc5b4e3 159784 flex-dbgsym_2.6.4-6_amd64.deb
 396b604445d991324bbc7c60f6ef4dfc57146168 765592 flex-doc_2.6.4-6_all.deb
 e9a5ff072a1717bac153470f7096c4eab9eeeba4 8992 flex_2.6.4-6_amd64.buildinfo
 0fdf7c2babf7102f2a184d29b954f6d3e62874de 454776 flex_2.6.4-6_amd64.deb
 ac545154b468c3aae8b1beac8f2fed6c50c3d287 103900 libfl-dev_2.6.4-6_amd64.deb
 803c146e850ee75ec1fe03111bba3a3877192c7c 2908 libfl2-dbgsym_2.6.4-6_amd64.deb
 0e4327ef6bf59794a247419d976566b586bf43dc 102676 libfl2_2.6.4-6_amd64.deb
Checksums-Sha256:
 43ee3ba775ea5ed88eda4055d91bbc72cc40c6827d72c918f082b6998a194b76 2044 
flex_2.6.4-6.dsc
 b72e76b6cea73e4bca69398db5c8683d44a0139d4dc5869dfe38e0a2a8c1e123 59099 
flex_2.6.4-6.diff.gz
 40f74d7ce6d3898f7d7d986c2c6bb6c61a922a26b852a5905c68975871d63c01 159784 
flex-dbgsym_2.6.4-6_amd64.deb
 be4d20e326229b99f0dd584ec0daa683d1d9de20c6c8051712e330ab119cb256 765592 
flex-doc_2.6.4-6_all.deb
 e6387f33c00f9b44be5313259f6d17d655c51408cf14dea2b43c4a93a6255782 8992 

Bug#890714: marked as done (flex: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2018 06:19:32 +
with message-id 
and subject line Bug#890714: fixed in flex 2.6.4-6
has caused the Debian Bug report #890714,
regarding flex: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
890714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flex
Version: 2.6.4-5
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Manoj Srivastava 

Hi,

I just ACCEPTed flex from NEW but noticed it was missing attribution 
in debian/copyright for at least tools/git2cl.

(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
   `-
--- End Message ---
--- Begin Message ---
Source: flex
Source-Version: 2.6.4-6

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Feb 2018 15:25:10 -0800
Source: flex
Binary: flex flex-doc libfl2 libfl-dev
Architecture: source amd64 all
Version: 2.6.4-6
Distribution: unstable
Urgency: medium
Maintainer: Manoj Srivastava 
Changed-By: Manoj Srivastava 
Description:
 flex   - fast lexical analyzer generator
 flex-doc   - Documentation for flex (a fast lexical analyzer generator)
 libfl-dev  - static library for flex (a fast lexical analyzer generator)
 libfl2 - SHARED library for flex (a fast lexical analyzer generator)
Closes: 890608 890703 890714 890743
Changes:
 flex (2.6.4-6) unstable; urgency=medium
 .
   * Rolled back the feature test POSIX_C_SOURCE changes.
   * Bug fix: "libfl-dev lost libl.a symlink", thanks to Bas Couwenberg
 (Closes: #890608). Made sure the link actually did make it to the
 .deb
   * Bug fix: "Incomplete debian/copyright?", thanks to Chris Lamb (Closes:
 #890714). Updated copyright using automation tools
   * Bug fix: "missing dependency on libfl2", thanks to Sven Joachim
 (Closes: #890743). Updated contreol
   * Bug fix: "all amd64 binaries since 2.6.4-1 built with stale skel.c
 file", thanks to James Cowgill (Closes: #890703).
Checksums-Sha1:
 a9c452d00395da6ee47991655f581265e4ef7273 2044 flex_2.6.4-6.dsc
 929b003d619dc31ab070e1a130ddf1241435ef5c 59099 flex_2.6.4-6.diff.gz
 3cbd737de7635872748d46727b77d7b6efc5b4e3 159784 flex-dbgsym_2.6.4-6_amd64.deb
 396b604445d991324bbc7c60f6ef4dfc57146168 765592 flex-doc_2.6.4-6_all.deb
 e9a5ff072a1717bac153470f7096c4eab9eeeba4 8992 flex_2.6.4-6_amd64.buildinfo
 0fdf7c2babf7102f2a184d29b954f6d3e62874de 454776 flex_2.6.4-6_amd64.deb
 ac545154b468c3aae8b1beac8f2fed6c50c3d287 103900 libfl-dev_2.6.4-6_amd64.deb
 803c146e850ee75ec1fe03111bba3a3877192c7c 2908 libfl2-dbgsym_2.6.4-6_amd64.deb
 0e4327ef6bf59794a247419d976566b586bf43dc 102676 libfl2_2.6.4-6_amd64.deb
Checksums-Sha256:
 43ee3ba775ea5ed88eda4055d91bbc72cc40c6827d72c918f082b6998a194b76 2044 
flex_2.6.4-6.dsc
 b72e76b6cea73e4bca69398db5c8683d44a0139d4dc5869dfe38e0a2a8c1e123 59099 
flex_2.6.4-6.diff.gz
 40f74d7ce6d3898f7d7d986c2c6bb6c61a922a26b852a5905c68975871d63c01 159784 
flex-dbgsym_2.6.4-6_amd64.deb
 be4d20e326229b99f0dd584ec0daa683d1d9de20c6c8051712e330ab119cb256 765592 
flex-doc_2.6.4-6_all.deb
 e6387f33c00f9b44be5313259f6d17d655c51408cf14dea2b43c4a93a6255782 8992 
flex_2.6.4-6_amd64.buildinfo
 d52ad0697f065416c8f628b6daa059cda1fe62dd5d1fa2ec1090e4255f39d52d 454776 
flex_2.6.4-6_amd64.deb
 7990e9839a9762e237515c265dc4c861abb15efb242a36d7107e8f0512d799b7 103900 
libfl-dev_2.6.4-6_amd64.deb
 2592d48c9c3664b271a903bdb19c990664070f8d2a486d6728551393b09a55fc 2908 
libfl2-dbgsym_2.6.4-6_amd64.deb
 7562a49e5e787b870b1f34d866ce7784ca1fd7c70aeea2d4737686d045ff85d2 102676 

Processed: [921fc67] Fix for Bug#890743 committed to git

[Debian Bug Tracking System]

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

> tags 890743 + pending
Bug #890743 [libfl-dev] libfl-dev: missing dependency on libfl2
Ignoring request to alter tags of bug #890743 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: [921fc67] Fix for Bug#890608 committed to git

[Debian Bug Tracking System]

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

> tags 890608 + pending
Bug #890608 [libfl-dev] libfl-dev lost libl.a symlink
Ignoring request to alter tags of bug #890608 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#890608: [921fc67] Fix for Bug#890608 committed to git

[Manoj Srivastava]

tags 890608 + pending
thanks
Hi,

 The following change has been committed for this bug by
 Manoj Srivastava  on the branch 
 dgit/sid at Sat, 24 Feb 2018 21:53:20 -0800.

 The fix will be in the next upload. 
=
[master]: A bug fixing release

Rolled backt he POSIX_X_SOURCE feature  check changes.

Closes: #890608
Closes: #890714
Closes: #890743
Closes: #890703

Signed-off-by: Manoj Srivastava 
=

Processed: [921fc67] Fix for Bug#890714 committed to git

[Debian Bug Tracking System]

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

> tags 890714 + pending
Bug #890714 [src:flex] flex: Incomplete debian/copyright?
Ignoring request to alter tags of bug #890714 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: notfound 890391 in libjs-jquery-atwho/1.5.4+dfsg.1-1, found 890391 in jquery-at.js/1.5.4+dfsg.1-1 ...

[Debian Bug Tracking System]

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

> notfound 890391 libjs-jquery-atwho/1.5.4+dfsg.1-1
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
The source libjs-jquery-atwho and version 1.5.4+dfsg.1-1 do not appear to match 
any binary packages
No longer marked as found in versions libjs-jquery-atwho/1.5.4+dfsg.1-1.
> found 890391 jquery-at.js/1.5.4+dfsg.1-1
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
Marked as found in versions jquery-at.js/1.5.4+dfsg.1-1.
> tags 890391 + help
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
Added tag(s) help.
> thanks
Stopping processing here.

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

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

[Ben Finney]

On 15-Feb-2018, Pirate Praveen wrote:

> wget `npm view at.js dist.tarball` will get you the dist tarball.
> Compare dist/js/jquery.atwho.js in the tarball with the file installed
> by the debian package.

(There is no ‘npm’ in Debian Buster yet, so I'm not easily able to get
anything from NPM.)

Looking at the ‘/usr/share/javascript/jquery-atwho/jquery.atwho.js’
file installed by the Debian package, I see that the Reference Error
is because ‘Controller’ is defined in a different scope.

As you have suggested, the custom build rules in the Debian package
were implemented before we had Gulp in Debian. So the build process
may be to blame for the error behaviour.

What should be done in this package to use the ‘gulpfile.js’ tasks,
now that Gulp is available in Debian?

-- 
 \“Science doesn't work by vote and it doesn't work by |
  `\authority.” —Richard Dawkins, _Big Mistake_ (The Guardian, |
_o__)  2006-12-27) |
Ben Finney 


signature.asc
Description: PGP signature

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

[Ben Finney]

Control: tags -1 - unreproducible + confirmed
Control: found -1 libjs-jquery-atwho/1.5.4+dfsg.1-1

On 25-Feb-2018, Balasankar C wrote:

> Attaching an html test file. It uses the libjs-jquery-caret.js
> package you have in experimental along with the libjs-query-atwho
> package in question.

Thank you. I have modified that so that it simply uses the
Debian-installed package, to show the error (and to use the same file
unchanged to test for whatever fix is implemented). The test file is
attached to this message.


The steps I am using to reproduce the behaviour:

* Install ‘libjs-jquery-caret.js’ version “0.3.1+dfsg.1-2” or later
  (now available in Debian “unstable”).

* Install ‘libjs-jquery-atwho’.

* Open a web browser with a debugger. (I am using Firefox.)

* Load the test page ‘atwho-bug890391-test.html’ with the debugger
  enabled.

  The JavaScript engine will report a “ReferenceError”, shown in the
  console.

This allows us to verify the reported behaviour.


This behaviour is present in version “1.5.3+dfsg.1-1”:

ReferenceError: Controller is not defined
jquery.atwho.min.js:1:10662

and, using the same test case, also in version “1.5.4+dfsg.1-1”:

ReferenceError: Controller is not defined
jquery.atwho.min.js:1:10634

Version “1.5.4” is the latest available from upstream. There are
(apparently?) no relevant upstream changes since that version that
would address this bug.

So unless I have misunderstood the bug, or there are changes in the
upstream source that address this bug, we need some fix that upstream
has not yet implemented.

-- 
 \“Are you pondering what I'm pondering, Pinky?” “Sure, Brain, |
  `\ but how are we going to find chaps our size?” —_Pinky and The |
_o__)   Brain_ |
Ben Finney 

	
	
		
		
	



signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - unreproducible + confirmed
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
Removed tag(s) unreproducible.
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
Added tag(s) confirmed.
> found -1 libjs-jquery-atwho/1.5.4+dfsg.1-1
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
The source libjs-jquery-atwho and version 1.5.4+dfsg.1-1 do not appear to match 
any binary packages
Marked as found in versions libjs-jquery-atwho/1.5.4+dfsg.1-1.

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

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

[Ben Finney]

On 25-Feb-2018, Balasankar C wrote:

> Note: I have enabled the atwho JS file from cloudflare CDN in it.

How is that related to the upstream source?

-- 
 \   “We have clumsy, sputtering, inefficient brains…. It is a |
  `\ *struggle* to be rational and objective, and failures are not |
_o__) evidence for an alternative reality.” —Paul Z. Myers, 2010-10-14 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#890698: marked as done (ruby-rspec-retry: FTBFS and Debci failure with ruby-rspec 3.7.0c1e0m0s1-1)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2018 03:19:28 +
with message-id 
and subject line Bug#890698: fixed in ruby-rspec-retry 0.5.6-1
has caused the Debian Bug report #890698,
regarding ruby-rspec-retry: FTBFS and Debci failure with ruby-rspec 
3.7.0c1e0m0s1-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.)


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

https://ci.debian.net/packages/r/ruby-rspec-retry/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rspec-retry.html

...
┌──┐
│ Checking Rubygems dependency resolution on ruby2.3   │
└──┘

Invalid gemspec in [rspec-retry.gemspec]: No such file or directory - git
GEM_PATH=debian/ruby-rspec-retry/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"rspec-retry\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'rspec-core' (< 3.6, > 3.3) - did find: [rspec-core-3.7.1] (Gem::LoadError)
--- End Message ---
--- Begin Message ---
Source: ruby-rspec-retry
Source-Version: 0.5.6-1

We believe that the bug you reported is fixed in the latest version of
ruby-rspec-retry, 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.
HIGUCHI Daisuke (VDR dai)  (supplier of updated 
ruby-rspec-retry 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: Sun, 25 Feb 2018 11:48:37 +0900
Source: ruby-rspec-retry
Binary: ruby-rspec-retry
Architecture: source all
Version: 0.5.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 ruby-rspec-retry - add support for retrying failing examples in RSpec
Closes: 890698
Changes:
 ruby-rspec-retry (0.5.6-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * New upstream release.
   - added support for rspec 3.7.0 (Closes: #890698).
   * support autopkgtest.
   * eliminate lintian warning: debian-watch-uses-insecure-uri
   * eliminate lintian warning: insecure-copyright-format-uri
   * Move Vcs-* to salsa.debian.org.
   * Bump debhelper compatibility level to 11.
   * Update Standards-Version to 4.1.3.
Checksums-Sha1:
 b2eda3ea5e15d93ec537e1ab7c8e08bfd93cf0a0 2157 ruby-rspec-retry_0.5.6-1.dsc
 82b1f36d2ddea180247c885f3a86cf5518d2d07f 9014 
ruby-rspec-retry_0.5.6.orig.tar.gz
 90237c12fa9b8e587eaf9f65d498a675838af0a8 3076 
ruby-rspec-retry_0.5.6-1.debian.tar.xz
 554193efb2af3a6509db68129ffb1bff75bf8611 8104 ruby-rspec-retry_0.5.6-1_all.deb
 136ad38a00da30613337ebbaa4a8208e04c537aa 6911 
ruby-rspec-retry_0.5.6-1_amd64.buildinfo
Checksums-Sha256:
 f8c4b1f7a1035ed33b65d3ebac03117944ca040c3cac414b0fc298b3807ae39e 2157 
ruby-rspec-retry_0.5.6-1.dsc
 70aecbf9fb1853c06aaa6d2fbe1993236c5e4512c5e318f6618910075457d053 9014 
ruby-rspec-retry_0.5.6.orig.tar.gz
 fbc173e8bd158d3719cd76e0d77a700baa893155c3512b7025602b0679e94a55 3076 
ruby-rspec-retry_0.5.6-1.debian.tar.xz
 59f7d54e84edb28520dacfe63132049fce31953554a25be696817271f5820abf 8104 
ruby-rspec-retry_0.5.6-1_all.deb
 8a953c41d6bfadede488a0011dfdab2465d6213d771d11a4e41abfed3b07dcc8 6911 
ruby-rspec-retry_0.5.6-1_amd64.buildinfo
Files:
 4073e34678cf976427052be811278c24 2157 ruby optional 
ruby-rspec-retry_0.5.6-1.dsc
 dfb5bf62113858625c6288ec5c7962d2 9014 ruby optional 
ruby-rspec-retry_0.5.6.orig.tar.gz
 533de05ce2c92d57097bacb2e3410c4c 3076 ruby optional 
ruby-rspec-retry_0.5.6-1.debian.tar.xz
 97f61f047e3df4555d61e8613e89cb4c 8104 ruby optional 
ruby-rspec-retry_0.5.6-1_all.deb
 

Processed: user debian...@lists.debian.org, affects 889581, found 859811 in 3.8.1-11 ..., affects 887574 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> affects 889581 + syslog-ng-mod-zmq
Bug #889581 [src:syslog-ng-incubator] syslog-ng-incubator: FTBFS with syslog-ng 
3.13.2
Added indication that 889581 affects syslog-ng-mod-zmq
> found 859811 3.8.1-11
Bug #859811 [eclipse-platform-data] eclipse-platform-data: broken symlinks: 
/usr/lib/eclipse/plugins/org.apache.ant_1.8.3.v20120321-1730/{bin, lib}/*
Marked as found in versions eclipse/3.8.1-11.
> found 884900 0.9.6-1~exp2
Bug #884900 [src:gnome-keysign] gnome-keysign: FTBFS on i386: Segmentation 
fault during tests
Marked as found in versions gnome-keysign/0.9.6-1~exp2.
> affects 887574 + texlive-lang-cjk latex-cjk-korean
Bug #887574 [texlive-lang-other] texlive-lang-other: broken symlinks: 
/usr/share/texlive/texmf-dist/fonts/truetype/public/padauk/PadaukBook*.ttf
Added indication that 887574 affects texlive-lang-cjk and latex-cjk-korean
> found 857954 libdevmapper-dev/2:1.02.145-4.1
Bug #857954 [libdevmapper-dev] libdevmapper-dev: broken symlink: 
/usr/lib//libdevmapper-event-lvm2.so -> 
/lib//libdevmapper-event-lvm2.so.2.02
The source libdevmapper-dev and version 2:1.02.145-4.1 do not appear to match 
any binary packages
Marked as found in versions libdevmapper-dev/2:1.02.145-4.1.
> found 696277 1:3.16-2
Bug #696277 [pyro] All manpages are dangling symlinks
Marked as found in versions pyro/1:3.16-2.
> affects 863670 + node-uglifyjs-webpack-plugin
Bug #863670 [node-timers-browserify] node-timers-browserify: broken symlink: 
/usr/share/doc/node-timers-browserify/example/enroll/node_modules/timers-browserify
 -> ../../../../../nodejs/timers-browserify
Added indication that 863670 affects node-uglifyjs-webpack-plugin
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
696277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696277
857954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857954
859811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859811
863670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863670
884900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884900
887574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887574
889581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#891371: goobook: Missing dependency: python-setuptools

[debian]

Package: goobook
Version: 1.9-2
Severity: serious
Justification: Policy 7.2

Dear Maintainer,

the package is missing an dependency: python-setuptools


Without it just crashes when running:

Traceback (most recent call last):
  File "/usr/bin/goobook", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3147, 
in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3131, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3160, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 666, 
in _build_master
ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 984, 
in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 870, 
in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'setuptools>=0.7' distribution was not 
found and is required by goobook


After installing it everything is fine.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (500, 'stable-updates'), (500, 'stable'), 
(500, 'oldstable'), (300, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages goobook depends on:
ii  python2.7.14-4
ii  python-gdata  2.0.18+dfsg1-2
ii  python-httplib2   0.9.2+dfsg-1
ii  python-oauth2client   4.1.2-2
ii  python-pkg-resources  38.4.0-1
ii  python-simplejson 3.13.2-1

goobook recommends no packages.

Versions of packages goobook suggests:
pn  python-keyring  

-- no debconf information

Bug#891370: pki-base-java: broken symlink: /usr/share/pki/lib/pki-tools.jar -> ../../java/pki/pki-tools.jar

[Andreas Beckmann]

Package: pki-base-java
Version: 10.5.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m43.5s ERROR: FAIL: Broken symlinks:
  /usr/share/pki/lib/pki-tools.jar -> ../../java/pki/pki-tools.jar


Is pki-base-java missing a Depends/Recommends/Suggests: pki-tools?


cheers,

Andreas


pki-base-java_10.5.5-1.log.gz
Description: application/gzip

Bug#876216: marked as done (pyfeed: FTBFS with python3.6 as a supported version)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 22:21:00 +
with message-id 
and subject line Bug#876216: fixed in pyfeed 1.0~prerelease-2
has caused the Debian Bug report #876216,
regarding pyfeed: FTBFS with python3.6 as a supported version
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.)


-- 
876216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfeed
Version: 1.0~prerelease-1
Severity: serious
Justification: fails to build from source

Hi,

pyfeed/experimental FTBFS (at least) since python3.6 became a supported
version:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/pyfeed-1.0~prerelease'
set -xe; \
for py in python2.7 python3.6 python3.5; do \
$py setup.py build; \
done
+ python2.7 setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/feed
copying feed/atom.py -> build/lib.linux-x86_64-2.7/feed
copying feed/rss.py -> build/lib.linux-x86_64-2.7/feed
copying feed/opml1.py -> build/lib.linux-x86_64-2.7/feed
copying feed/opml.py -> build/lib.linux-x86_64-2.7/feed
copying feed/__init__.py -> build/lib.linux-x86_64-2.7/feed
copying feed/tools.py -> build/lib.linux-x86_64-2.7/feed
creating build/lib.linux-x86_64-2.7/feed/date
copying feed/date/__init__.py -> build/lib.linux-x86_64-2.7/feed/date
copying feed/date/rfc822.py -> build/lib.linux-x86_64-2.7/feed/date
copying feed/date/tools.py -> build/lib.linux-x86_64-2.7/feed/date
copying feed/date/rfc3339.py -> build/lib.linux-x86_64-2.7/feed/date
+ python3.6 setup.py build
/bin/sh: 3: python3.6: not found
debian/rules:10: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127


Full log attached.

Andreas


pyfeed_1.0~prerelease-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pyfeed
Source-Version: 1.0~prerelease-2

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

Debian distribution maintenance software
pp.
Thomas Preud'homme  (supplier of updated pyfeed 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: Sat, 24 Feb 2018 21:59:35 +
Source: pyfeed
Binary: python-feed python3-feed
Architecture: source all
Version: 1.0~prerelease-2
Distribution: experimental
Urgency: medium
Maintainer: Matteo Cypriani 
Changed-By: Thomas Preud'homme 
Description:
 python-feed - set of Python modules for working with syndication feeds (Python
 python3-feed - set of Python modules for working with syndication feeds (Python
Closes: 876216
Changes:
 pyfeed (1.0~prerelease-2) experimental; urgency=medium
 .
   * debian/control:
 + Fix dependency on python3 for python3-feed (Closes: #876216).
 + Build-Depends on python-all and python3-all instead of python and
   python3 to be able to compile bytecode on all supported python versions
   without FTBFS.
 + Update Vcs fields and use secure URLs.
 + Set priority to optional.
 + Update versioned Build-depends on debhelper.
 + Bump standard version to 4.1.3.
   * debian/copyright:
 + Use secure URL for format field.
   * debian/compat:
 + Bump compatibility to 11.
Checksums-Sha1:
 f6a05137fe052806df889b24b449e3942925faa8 2162 pyfeed_1.0~prerelease-2.dsc
 fde805064d9df8e80cd11a381e8cee5e32ffabf4 2776 
pyfeed_1.0~prerelease-2.debian.tar.xz
 b56345ebf0bf10efbae24cbe1a9180d8d0874e63 6954 
pyfeed_1.0~prerelease-2_amd64.buildinfo
 c4292bed6152a218ed36b530852e814255791558 19876 
python-feed_1.0~prerelease-2_all.deb
 45236e9c79968865ffc8b37ef2fd53abcec2decc 18072 
python3-feed_1.0~prerelease-2_all.deb
Checksums-Sha256:
 81a18875e8106c265bdea24be14002e3da9a9d149a132fdb89488211c05300cc 2162 
pyfeed_1.0~prerelease-2.dsc
 b795369e0c9416b0f25b4335acf67c50e88a1b0ed9b65106aa5a7241908921a5 2776 
pyfeed_1.0~prerelease-2.debian.tar.xz
 

Processed: bug 890317 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=790845

[Debian Bug Tracking System]

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

> forwarded 890317 https://bugzilla.gnome.org/show_bug.cgi?id=790845
Bug #890317 [src:gnucash] gnucash: FTBFS on 32-bit architectures due to test 
failures
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=790845'.
> thanks
Stopping processing here.

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

Bug#889046: Bug #889046 in ruby marked as pending

[terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby/commit/e4c663efe4d661445c2a4b5c49d257317fa0928b


fix test failures after updates in the Japan timezone data

Closes: #889046



(this message was generated automatically)
-- 
Greetings

Processed: Bug #889046 in ruby marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889046 {Done: Antonio Terceiro } [src:ruby2.5] 
ruby2.5 FTBFS with tzdata 2018c-1
Added tag(s) pending.

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

Bug#889046: marked as done (ruby2.5 FTBFS with tzdata 2018c-1)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 22:04:41 +
with message-id 
and subject line Bug#889046: fixed in ruby2.5 2.5.0-5
has caused the Debian Bug report #889046,
regarding ruby2.5 FTBFS with tzdata 2018c-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.)


-- 
889046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby2.5
Version: 2.5.0-4
Severity: serious

https://buildd.debian.org/status/package.php?p=ruby2.5=sid

...
  1) Failure:
TestTimeTZ#test_asia_tokyo [/<>/test/ruby/test_time_tz.rb:129]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 2, 0, 0).
<"1951-05-06 03:00:00 +1000"> expected but was
<"1951-05-06 02:00:00 +1000">.

  2) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_24 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 5, 5, 16, 59, 59).localtime.
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 02:59:59 +1000">.

  3) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_27 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 9, 7, 16, 0, 0).localtime.
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 02:00:00 +1000">.

  4) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_69 
[/<>/test/ruby/test_time_tz.rb:277]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 1, 59, 59).
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 01:59:59 +1000">.

  5) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_72 
[/<>/test/ruby/test_time_tz.rb:295]:
TZ=Asia/Tokyo Time.local(0, 0, 1, 8, 9, 1951, nil, nil, false, nil).
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 01:00:00 +1000">.

Finished tests in 384.583156s, 44.7940 tests/s, 5880.9466 assertions/s.
17227 tests, 2261713 assertions, 5 failures, 0 errors, 60 skips

ruby -v: ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux-gnu]
uncommon.mk:698: recipe for target 'yes-test-almost' failed
make[2]: *** [yes-test-almost] Error 5



http://mm.icann.org/pipermail/tz-announce/2018-January/48.html

   Changes to past time stamps

 Japanese DST transitions (1948-1951) were Sundays at 00:00, not
 Saturdays or Sundays at 02:00.  (Thanks to Takayuki Nikai.)
--- End Message ---
--- Begin Message ---
Source: ruby2.5
Source-Version: 2.5.0-5

We believe that the bug you reported is fixed in the latest version of
ruby2.5, 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.
Antonio Terceiro  (supplier of updated ruby2.5 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: Sat, 24 Feb 2018 12:20:04 -0300
Source: ruby2.5
Binary: ruby2.5 libruby2.5 ruby2.5-dev ruby2.5-doc
Architecture: source
Version: 2.5.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Description:
 libruby2.5 - Libraries necessary to run Ruby 2.5
 ruby2.5- Interpreter of object-oriented scripting language Ruby
 ruby2.5-dev - Header files for compiling extension modules for the Ruby 2.5
 ruby2.5-doc - Documentation for Ruby 2.5
Closes: 889046
Changes:
 ruby2.5 (2.5.0-5) unstable; urgency=medium
 .
   * Change Maintainer: to Debian Ruby Team
   * debian/patches/0005-Fix-tests-to-cope-with-updates-in-tzdata.patch: fix
 test failures after updates in the Japan timezone data (Closes: #889046)
   * 
debian/patches/0006-Rubygems-apply-upstream-patch-to-fix-multiple-vulner.patch:
 upgrade to Rubygems 2.7.6 to fix multiple vulnerabilities
Checksums-Sha1:
 8a29eefdfd528d7d12323f7fd21f05c35a2f5bd7 2376 ruby2.5_2.5.0-5.dsc
 e07ff02efdd5804497a7afea95abe071fa57f01d 115700 ruby2.5_2.5.0-5.debian.tar.xz
 a053265bbd015239566e68ae3c6f1286a901684e 6392 ruby2.5_2.5.0-5_source.buildinfo
Checksums-Sha256:
 c31b5d7ac622129a7c3854532ce1c3688025b2923a72e75bff917012e8c15bd3 2376 
ruby2.5_2.5.0-5.dsc
 25a28e507e5209c4e053eeacda87f4020f0801facce790c5accec25045f65475 115700 
ruby2.5_2.5.0-5.debian.tar.xz
 a321457d9b5b6c98faae80bb8863c819642783b95d9028321de076ff0650be1f 6392 

Bug#847135: marked as done (openconnect: vpn connection mtu too big)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 13:55:25 -0800
with message-id <20180224215525.ga6...@galago.mtmxr.com>
and subject line closing as fixed again
has caused the Debian Bug report #847135,
regarding openconnect: vpn connection mtu too big
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.)


-- 
847135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openconnect
Version: 7.07-1
Severity: important

Dear Maintainer,

* What led up to the situation?
Connecting to the VPN
Any connection sending large amounds of data fails
http downloads of any non trivial file, opening a remote desktop connection

* What exactly did you do (or not do) that was effective (or ineffective)?
connections fail when sending large data as the packet size is too bug

* What was the outcome of this action?
Connections seem to hand or fail

* What outcome did you expect instead?
Successful data transfer

Please see this for discussion of the problem:
https://bbs.archlinux.org/viewtopic.php?id=200183

Adding the script as proposed at the top of the thread works well as does just
setting the MTU to a lower value after connecting

ip link set vpn0 mtu 1186

please could we fix this, it took a little tracking down and I imagine others
might find this harder to find.

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages openconnect depends on:
ii  libc62.24-5
ii  libgnutls30  3.5.6-7
ii  libopenconnect5  7.07-1
ii  libproxy1v5  0.4.13-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  vpnc-scripts 0.1~git20150318-1

openconnect recommends no packages.

openconnect suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
There has been no further information, I'm closing this bug again as
fixed in 7.08-1. The original bug reporter confirmed that 7.08 fixed the
original problem.

If there are similar problems with 7.08, please file a new bug report,
don't reopen this one again.

-- 
mike


signature.asc
Description: PGP signature
--- End Message ---

Processed: fixed 847135 in openconnect/7.08-1

[Debian Bug Tracking System]

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

> fixed 847135 openconnect/7.08-1
Bug #847135 [openconnect] openconnect: vpn connection mtu too big
Marked as fixed in versions openconnect/7.08-1.
> thanks
Stopping processing here.

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

Bug#876236: marked as done (xmlelements: FTBFS with python3.6 as a supported version)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 21:35:34 +
with message-id 
and subject line Bug#876236: fixed in xmlelements 1.0~prerelease-2
has caused the Debian Bug report #876236,
regarding xmlelements: FTBFS with python3.6 as a supported version
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.)


-- 
876236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmlelements
Version: 1.0~prerelease-1
Severity: serious
Justification: fails to build from source

Hi,

xmlelements FTBFS (at least) since python3.6 became a supported python3
version:

 debian/rules build
dh build --with=python2,python3
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/xmlelements-1.0~prerelease'
set -xe; \
for py in python2.7 python3.6 python3.5; do \
$py setup.py build; \
done
+ python2.7 setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
copying xe.py -> build/lib.linux-x86_64-2.7
+ python3.6 setup.py build
/bin/sh: 3: python3.6: not found
debian/rules:10: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127
make[1]: Leaving directory '/build/xmlelements-1.0~prerelease'
debian/rules:28: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


xmlelements_1.0~prerelease-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xmlelements
Source-Version: 1.0~prerelease-2

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

Debian distribution maintenance software
pp.
Thomas Preud'homme  (supplier of updated xmlelements 
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: Sat, 24 Feb 2018 21:19:49 +
Source: xmlelements
Binary: python-xe python3-xe
Architecture: source all
Version: 1.0~prerelease-2
Distribution: experimental
Urgency: medium
Maintainer: Matteo Cypriani 
Changed-By: Thomas Preud'homme 
Description:
 python-xe  - library to work with XML elements (Python 2)
 python3-xe - library to work with XML elements (Python 3)
Closes: 876236 884688
Changes:
 xmlelements (1.0~prerelease-2) experimental; urgency=medium
 .
   * debian/control:
 + Fix dependency on python3 for python3-xe (Closes: #884688).
 + Build-Depends on python-all and python3-all instead of python and
   python3 to be able to compile bytecode on all supported python versions
   without FTBFS (Closes: #876236).
 + Use secure URLs for Vcs fields.
 + Fix typo in package descriptions.
 + Change package priority to optional.
 + Adjust versioned dependency on debhelper.
 + Bump standard version.
   * debian/rules:
 + Compile bytecode for default python last to ensure proper shebang in
   scripts.
   * debian/copyright:
 + Use secure URL for format field.
   * debian/compat:
 + Bump compatibility to 11.
Checksums-Sha1:
 655f121553c082b8bc2f93c0d3c7eb104af33afb 2201 xmlelements_1.0~prerelease-2.dsc
 27101d3d648dfe9c23811361d2729cf452365c5c 2732 
xmlelements_1.0~prerelease-2.debian.tar.xz
 fe810e94187e6ffa0d8813abded4cc49f383b8b2 20812 
python-xe_1.0~prerelease-2_all.deb
 3369113a9bb730029f53599a48cd15b1f18cfb55 18704 
python3-xe_1.0~prerelease-2_all.deb
 1f4c7e87961967fc13cbb5155ffb83eba8dd7132 6963 
xmlelements_1.0~prerelease-2_amd64.buildinfo
Checksums-Sha256:
 b0f4aa444cca3cb4d125c1be77d5fea8df76a39b8c3c8b9dcbdc0461ae3c26a1 2201 
xmlelements_1.0~prerelease-2.dsc
 fdaa0b621a623ba573503304167c335f93eae00b037f3cee3f965379458b1968 2732 
xmlelements_1.0~prerelease-2.debian.tar.xz
 2fc4f1481c6e032b39dd47aeb38891af3515c013361ecb78726dc56d97bb9b11 20812 
python-xe_1.0~prerelease-2_all.deb
 691f63ae084f659b88f9bd91e911f49397653739d3b52cf82f4f26ebbd21 18704 
python3-xe_1.0~prerelease-2_all.deb
 d84c62a18d8099147f9b6569dc8981f60ffc9b4dad3957dd136581bfb37a3bbd 6963 

Bug#884688: marked as done (python3-xe: missing depepdency on the python interpreter)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 21:35:34 +
with message-id 
and subject line Bug#884688: fixed in xmlelements 1.0~prerelease-2
has caused the Debian Bug report #884688,
regarding python3-xe: missing depepdency on the python interpreter
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.)


-- 
884688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-xe
Version: 1.0~prerelease-1
Severity: serious

Dear maintainer,

python3-xe is a Python package but lacks any dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).
--- End Message ---
--- Begin Message ---
Source: xmlelements
Source-Version: 1.0~prerelease-2

We believe that the bug you reported is fixed in the latest version of
xmlelements, 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.
Thomas Preud'homme  (supplier of updated xmlelements 
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: Sat, 24 Feb 2018 21:19:49 +
Source: xmlelements
Binary: python-xe python3-xe
Architecture: source all
Version: 1.0~prerelease-2
Distribution: experimental
Urgency: medium
Maintainer: Matteo Cypriani 
Changed-By: Thomas Preud'homme 
Description:
 python-xe  - library to work with XML elements (Python 2)
 python3-xe - library to work with XML elements (Python 3)
Closes: 876236 884688
Changes:
 xmlelements (1.0~prerelease-2) experimental; urgency=medium
 .
   * debian/control:
 + Fix dependency on python3 for python3-xe (Closes: #884688).
 + Build-Depends on python-all and python3-all instead of python and
   python3 to be able to compile bytecode on all supported python versions
   without FTBFS (Closes: #876236).
 + Use secure URLs for Vcs fields.
 + Fix typo in package descriptions.
 + Change package priority to optional.
 + Adjust versioned dependency on debhelper.
 + Bump standard version.
   * debian/rules:
 + Compile bytecode for default python last to ensure proper shebang in
   scripts.
   * debian/copyright:
 + Use secure URL for format field.
   * debian/compat:
 + Bump compatibility to 11.
Checksums-Sha1:
 655f121553c082b8bc2f93c0d3c7eb104af33afb 2201 xmlelements_1.0~prerelease-2.dsc
 27101d3d648dfe9c23811361d2729cf452365c5c 2732 
xmlelements_1.0~prerelease-2.debian.tar.xz
 fe810e94187e6ffa0d8813abded4cc49f383b8b2 20812 
python-xe_1.0~prerelease-2_all.deb
 3369113a9bb730029f53599a48cd15b1f18cfb55 18704 
python3-xe_1.0~prerelease-2_all.deb
 1f4c7e87961967fc13cbb5155ffb83eba8dd7132 6963 
xmlelements_1.0~prerelease-2_amd64.buildinfo
Checksums-Sha256:
 b0f4aa444cca3cb4d125c1be77d5fea8df76a39b8c3c8b9dcbdc0461ae3c26a1 2201 
xmlelements_1.0~prerelease-2.dsc
 fdaa0b621a623ba573503304167c335f93eae00b037f3cee3f965379458b1968 2732 
xmlelements_1.0~prerelease-2.debian.tar.xz
 2fc4f1481c6e032b39dd47aeb38891af3515c013361ecb78726dc56d97bb9b11 20812 
python-xe_1.0~prerelease-2_all.deb
 691f63ae084f659b88f9bd91e911f49397653739d3b52cf82f4f26ebbd21 18704 
python3-xe_1.0~prerelease-2_all.deb
 d84c62a18d8099147f9b6569dc8981f60ffc9b4dad3957dd136581bfb37a3bbd 6963 
xmlelements_1.0~prerelease-2_amd64.buildinfo
Files:
 5b3171b76c13ce19916de645bc18da9e 2201 python optional 
xmlelements_1.0~prerelease-2.dsc
 2c45b25b7816ea181985e4979b75523a 2732 python optional 
xmlelements_1.0~prerelease-2.debian.tar.xz
 03a42085f62e2cf3e7204238a6d21852 20812 python optional 
python-xe_1.0~prerelease-2_all.deb
 3ccda6903da21cf3277958c642a9020b 18704 python optional 
python3-xe_1.0~prerelease-2_all.deb
 142a63a1c6c1c4cad66c3c6770e2368b 6963 python optional 
xmlelements_1.0~prerelease-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXzX2e6+ottWBygjr0AOFL71SUp4FAlqR1z4ACgkQ0AOFL71S

Bug#891360: python-magnumclient FTBFS: test failures

[Adrian Bunk]

Source: python-magnumclient
Version: 2.7.0-4
Severity: serious

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

...
==
FAIL: magnumclient.tests.test_shell.ShellTest.test_main_endpoint_internal
magnumclient.tests.test_shell.ShellTest.test_main_endpoint_internal
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "magnumclient/tests/test_shell.py", line 296, in 
test_main_endpoint_internal
mock_client.assert_called_once_with(**expected_args)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 948, in 
assert_called_once_with
return self.assert_called_with(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 937, in 
assert_called_with
six.raise_from(AssertionError(_error_message(cause)), cause)
  File "/usr/lib/python2.7/dist-packages/six.py", line 737, in raise_from
raise value
AssertionError: Expected call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v2.0', cloud=None, insecure=False, 
interface='internal', magnum_url=None, password='password', profile=None, 
project_domain_id=None, project_domain_name=None, project_id=None, 
project_name='project_name', region_name=None, service_type='container-infra', 
user_domain_id=None, user_domain_name=None, user_id=None, username='username')
Actual call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v2.0', cloud=None, insecure=False, 
interface='internal', magnum_url=None, password='password', 
project_domain_id=None, project_domain_name=None, project_id=None, 
project_name='project_name', region_name=None, service_type='container-infra', 
user_domain_id=None, user_domain_name=None, user_id=None, username='username')


==
FAIL: magnumclient.tests.test_shell.ShellTestKeystoneV3.test_main_no_region
magnumclient.tests.test_shell.ShellTestKeystoneV3.test_main_no_region
--
_StringException: Traceback (most recent call last):
  File "magnumclient/tests/test_shell.py", line 280, in test_main_no_region
self._test_main_region('bay-list', None)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "magnumclient/tests/test_shell.py", line 266, in _test_main_region
mock_client.assert_called_once_with(**expected_args)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 948, in 
assert_called_once_with
return self.assert_called_with(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 937, in 
assert_called_with
six.raise_from(AssertionError(_error_message(cause)), cause)
  File "/usr/lib/python2.7/dist-packages/six.py", line 737, in raise_from
raise value
AssertionError: Expected call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v3', cloud=None, insecure=False, interface='public', 
magnum_url=None, password='password', profile=None, project_domain_id=None, 
project_domain_name=None, project_id=None, project_name='project_name', 
region_name=None, service_type='container-infra', user_domain_id=None, 
user_domain_name=None, user_id=None, username='username')
Actual call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v3', cloud=None, insecure=False, interface='public', 
magnum_url=None, password='password', project_domain_id=None, 
project_domain_name=None, project_id=None, project_name='project_name', 
region_name=None, service_type='container-infra', user_domain_id=None, 
user_domain_name=None, user_id=None, username='username')


==
FAIL: magnumclient.tests.test_shell.ShellTest.test_main_os_cloud
magnumclient.tests.test_shell.ShellTest.test_main_os_cloud
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "magnumclient/tests/test_shell.py", line 308, in test_main_os_cloud
mock_client.assert_called_once_with(**expected_args)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 948, in 
assert_called_once_with
return self.assert_called_with(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 937, in 
assert_called_with
six.raise_from(AssertionError(_error_message(cause)), cause)
  File "/usr/lib/python2.7/dist-packages/six.py", line 737, in raise_from
raise value
AssertionError: Expected call: Client(api_version='latest', auth_token=None, 
auth_url=None, 

Processed: Re: sane: Agfa SnapScan 1212U does not work after upgrade to stretch.

[Debian Bug Tracking System]

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

> severity 890922 normal
Bug #890922 [sane] sane: Agfa SnapScan 1212U does not work after upgrade to 
stretch.
Severity set to 'normal' from 'grave'
> tags 890922 +moreinfo
Bug #890922 [sane] sane: Agfa SnapScan 1212U does not work after upgrade to 
stretch.
Added tag(s) moreinfo.
> reassign 890922 sane-backends 1.0.25-4.1
Bug #890922 [sane] sane: Agfa SnapScan 1212U does not work after upgrade to 
stretch.
Bug reassigned from package 'sane' to 'sane-backends'.
No longer marked as found in versions sane-frontends/1.0.14-12.
Ignoring request to alter fixed versions of bug #890922 to the same values 
previously set
Bug #890922 [sane-backends] sane: Agfa SnapScan 1212U does not work after 
upgrade to stretch.
There is no source info for the package 'sane-backends' at version '1.0.25-4.1' 
with architecture ''
Unable to make a source version for version '1.0.25-4.1'
Marked as found in versions 1.0.25-4.1.
> thanks
Stopping processing here.

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

Bug#890922: sane: Agfa SnapScan 1212U does not work after upgrade to stretch.

[Jörg Frings-Fürst]

severity 890922 normal
tags 890922 +moreinfo
reassign 890922 sane-backends 1.0.25-4.1
thanks



Hello Michael,

thank you for spending your time helping to make Debian better with
this bug report.


Please can you attach your /etc/sand.d/snapscan.conf and the 
Directory listing ls -l /usr/share/sane/snapscan.

CU
Jörg 



-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.

Bug#890866: mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs

[Theodore Ts'o]

On Tue, Feb 20, 2018 at 11:37:12AM +0100, Andreas Boll wrote:
> 
> Thanks for reporting to upstream!
> Could you test Mesa 18.0.0~rc4-1 from experimental? According to [1]
> some GPU hangs are supposed to be fixed.

Per [1], I've tried 18.0.0~rc4-1, and it appears to fix the issue.
Also, I've since noticed there are similar GPU hangs happening with
17.3.3-1 --- it's just that they are much more easy to reproduce with
17.3.4-1.

Cheers,

- Ted

[1] https://bugs.freedesktop.org/show_bug.cgi?id=105169#c2

Bug#891359: pk4 FTBFS with golang-1.10-go

[Adrian Bunk]

Source: pk4
Version: 5
Severity: serious

https://buildd.debian.org/status/package.php?p=pk4=sid

...
   dh_auto_configure -a -O--buildsystem=golang
dh_auto_configure: Could not symlink 
obj-x86_64-linux-gnu/src/github.com/Debian/pk4/cmd/pk4/testdata/FileImplicit: 
No such file or directory
make: *** [debian/rules:19: build-arch] Error 2

Bug#891358: rawdns FTBFS with golang-1.10-go

[Adrian Bunk]

Source: rawdns
Version: 1.6~ds1-1
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/package.php?p=rawdns=sid

...
dh build-arch --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
dh_auto_configure: Could not symlink 
obj-x86_64-linux-gnu/src/github.com/tianon/rawdns/version.go: No such file or 
directory
make: *** [debian/rules:6: build-arch] Error 2

Bug#891356: golang-google-cloud FTBFS: FAIL google.golang.org/cloud/spanner

[Adrian Bunk]

Source: golang-google-cloud
Version: 0.9.0-4
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-google-cloud=all=0.9.0-4=1519472771=0

...
=== RUN   TestRsdNonblockingStates
FATAL: 2018/02/24 11:45:48 grpc: Server.RegisterService after Server.Serve for 
"google.spanner.v1.Spanner"
FAILgoogle.golang.org/cloud/spanner 0.039s

Bug#888591: ck: diff for NMU version 0.6.0-1.1

[Adrian Bunk]

Control: tags 888591 + pending

Dear maintainer,

I've prepared an NMU for ck (versioned as 0.6.0-1.1) and uploaded
it to DELAYED/5. Please feel free to tell me if I should cancel it.

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

diff -Nru ck-0.6.0/debian/changelog ck-0.6.0/debian/changelog
--- ck-0.6.0/debian/changelog	2017-03-11 01:38:50.0 +0200
+++ ck-0.6.0/debian/changelog	2018-02-24 21:32:28.0 +0200
@@ -1,3 +1,11 @@
+ck (0.6.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch from Niels Thykier to fix FTBFS with
+debhelper >= 11.1. (Closes: #888591)
+
+ -- Adrian Bunk   Sat, 24 Feb 2018 21:32:28 +0200
+
 ck (0.6.0-1) unstable; urgency=medium
 
   * New upstream version 0.6.0
diff -Nru ck-0.6.0/debian/rules ck-0.6.0/debian/rules
--- ck-0.6.0/debian/rules	2017-03-11 01:38:50.0 +0200
+++ ck-0.6.0/debian/rules	2018-02-24 21:32:24.0 +0200
@@ -14,5 +14,10 @@
 %:
 	dh $@
 
+# The build target must not be empty.  Sadly because of how make
+# works, we have do duplicate the target in this case.
+build:
+	dh $@
+
 .PHONY: build
 

Processed: ck: diff for NMU version 0.6.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 888591 + pending
Bug #888591 [src:ck] ck: FTBFS with debhelper/11.1 due to empty build target
Added tag(s) pending.

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

Processed: found 891154 in 7.32-1, found 891153 in 7.32-1, found 891152 in 7.32-1, found 891150 in 7.32-1 ...

[Debian Bug Tracking System]

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

> found 891154 7.32-1
Bug #891154 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: External link injection on 404 pages when linking to the 
current page
Marked as found in versions drupal7/7.32-1.
> found 891153 7.32-1
Bug #891153 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: jQuery vulnerability with untrusted domains
Marked as found in versions drupal7/7.32-1.
> found 891152 7.32-1
Bug #891152 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: Private file access bypass
Marked as found in versions drupal7/7.32-1.
> found 891150 7.32-1
Bug #891150 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: JavaScript cross-site scripting prevention is incomplete
Marked as found in versions drupal7/7.32-1.
> retitle 891150 drupal7: CVE-2017-6927: SA-CORE-2018-001: JavaScript 
> cross-site scripting prevention is incomplete
Bug #891150 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: JavaScript cross-site scripting prevention is incomplete
Changed Bug title to 'drupal7: CVE-2017-6927: SA-CORE-2018-001: JavaScript 
cross-site scripting prevention is incomplete' from 'drupal7: SA-CORE-2018-001: 
JavaScript cross-site scripting prevention is incomplete'.
> retitle 891152 drupal7: CVE-2017-6928: SA-CORE-2018-001: Private file access 
> bypass
Bug #891152 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: Private file access bypass
Changed Bug title to 'drupal7: CVE-2017-6928: SA-CORE-2018-001: Private file 
access bypass' from 'drupal7: SA-CORE-2018-001: Private file access bypass'.
> retitle 891153 drupal7: CVE-2017-6929: jQuery vulnerability with untrusted 
> domains
Bug #891153 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: jQuery vulnerability with untrusted domains
Changed Bug title to 'drupal7: CVE-2017-6929: jQuery vulnerability with 
untrusted domains' from 'drupal7: SA-CORE-2018-001: jQuery vulnerability with 
untrusted domains'.
> retitle 891154 drupal7: CVE-2017-6932: A-CORE-2018-001: External link 
> injection on 404 pages when linking to the current page
Bug #891154 {Done: Gunnar Wolf } [src:drupal7] drupal7: 
SA-CORE-2018-001: External link injection on 404 pages when linking to the 
current page
Changed Bug title to 'drupal7: CVE-2017-6932: A-CORE-2018-001: External link 
injection on 404 pages when linking to the current page' from 'drupal7: 
SA-CORE-2018-001: External link injection on 404 pages when linking to the 
current page'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
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: Based on the information provided the package is completely broken in stretch

[Debian Bug Tracking System]

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

> severity 857906 grave
Bug #857906 [iaxmodem] iaxmodem 1.2.0~dfsg-2+b2 does not work anymore
Severity set to 'grave' from 'normal'
> tags 857906 stretch buster sid
Bug #857906 [iaxmodem] iaxmodem 1.2.0~dfsg-2+b2 does not work anymore
Added tag(s) sid, stretch, and buster.
> thanks
Stopping processing here.

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

Bug#887775: marked as done (libgnomekbd FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 19:49:20 +
with message-id 
and subject line Bug#887775: fixed in libgnomekbd 3.26.0-3
has caused the Debian Bug report #887775,
regarding libgnomekbd FTBFS: symbol differences
to be marked as done.

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

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


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

Some recent change in unstable makes libgnomekbd FTBFS:

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

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/libgnomekbd-3.26.0'
dh_makeshlibs -V -- -c4
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: no debian/symbols file used as basis for generating 
debian/libgnomekbd8/DEBIAN/symbols
--- new_symbol_file (libgnomekbd8_3.26.0-2_amd64)
+++ dpkg-gensymbolsGbx1cw   2018-01-14 10:50:33.771948808 -1200
@@ -83,7 +83,7 @@
  gkbd_configuration_remove_object@Base 3.6.0
  gkbd_configuration_start_listen@Base 3.6.0
  gkbd_configuration_stop_listen@Base 3.6.0
- gkbd_indicator_VOID__VOID@Base 3.26.0
+#MISSING: 3.26.0-2# gkbd_indicator_VOID__VOID@Base 3.26.0
  gkbd_indicator_config_activate@Base 3.6.0
  gkbd_indicator_config_free_image_filenames@Base 3.6.0
  gkbd_indicator_config_get_fg_color_for_widget@Base 3.6.0
@@ -106,7 +106,7 @@
  gkbd_indicator_reinit_ui@Base 3.6.0
  gkbd_indicator_set_angle@Base 3.6.0
  gkbd_indicator_set_parent_tooltips@Base 3.6.0
- gkbd_keyboard_drawing_VOID__UINT@Base 3.26.0
+#MISSING: 3.26.0-2# gkbd_keyboard_drawing_VOID__UINT@Base 3.26.0
  gkbd_keyboard_drawing_dialog_new@Base 3.6.0
  gkbd_keyboard_drawing_dialog_set_group@Base 3.6.0
  gkbd_keyboard_drawing_dialog_set_layout@Base 3.6.0
dh_makeshlibs: failing due to earlier errors
debian/rules:21: recipe for target 'override_dh_makeshlibs' failed
make[1]: *** [override_dh_makeshlibs] Error 2
--- End Message ---
--- Begin Message ---
Source: libgnomekbd
Source-Version: 3.26.0-3

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated libgnomekbd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 14:27:28 -0500
Source: libgnomekbd
Binary: libgnomekbd-dev libgnomekbd8 libgnomekbd-common gkbd-capplet 
gir1.2-gkbd-3.0
Architecture: source
Version: 3.26.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-gkbd-3.0 - GObject introspection data for the GnomeKbd library
 gkbd-capplet - GNOME control center tools for libgnomekbd
 libgnomekbd-common - GNOME library to manage keyboard configuration - common 
files
 libgnomekbd-dev - GNOME library to manage keyboard configuration - development 
file
 libgnomekbd8 - GNOME library to manage keyboard configuration - shared library
Closes: 887775
Changes:
 libgnomekbd (3.26.0-3) unstable; urgency=medium
 .
   * debian/libgnomekbgd8.symbols: Update for latest glib (Closes: #887775)
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Add debian/gbp.conf
   * Bump debhelper compat to 11
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 745d6ebb2b878e9a1177fbd8ccd6fb3efa8f3cae 2458 libgnomekbd_3.26.0-3.dsc
 6ffdef63561a86ce87a23e46c14f70242bf8a017 8344 
libgnomekbd_3.26.0-3.debian.tar.xz
 3769bd14d6fc3bdc3a8bc153b7b65d20286b7b53 16357 
libgnomekbd_3.26.0-3_source.buildinfo
Checksums-Sha256:
 e4534878007d800cccbccda8d6d0e0bb396bad71456686d685942e01ed30df4e 2458 
libgnomekbd_3.26.0-3.dsc
 9dd49405dbcd8b23ae1b0ff927803467cb8c7ccc1129079be9a57dac11ae3e4b 8344 
libgnomekbd_3.26.0-3.debian.tar.xz
 

Bug#891331: Beta from SQLA are *not* to upload, and full of bugs

[Piotr Ożarowski]

[Thomas Goirand, 2018-02-24]
> Please upload a working version of SQLA in Experimental, for example 1.2.1,
> which is accepted by OpenStack, as per this document:

if 1.2.4 works in OpenStack, I will upload it directly into unstable. Is
that OK?

Processed: Bug #887775 in libgnomekbd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #887775 [src:libgnomekbd] libgnomekbd FTBFS: symbol differences
Added tag(s) pending.

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

Bug#887775: Bug #887775 in libgnomekbd marked as pending

[jbicha]

Control: tag -1 pending

Hello,

Bug #887775 in libgnomekbd 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/libgnomekbd/commit/42972a78a87107e609a6e0d8a047b925b9bdda8a


debian/libgnomekbgd8.symbols: Update for latest glib

Closes: #887775



(this message was generated automatically)
-- 
Greetings

Processed: tagging 882268

[Debian Bug Tracking System]

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

> tags 882268 + buster sid
Bug #882268 [src:networking-ovs-dpdk] networking-ovs-dpdk FTBFS: 
AttributeError: 'module' object has no attribute 'VIF_TYPE_VHOST_USER'
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 881212

[Debian Bug Tracking System]

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

> tags 881212 + buster sid
Bug #881212 [src:networking-l2gw] networking-l2gw FTBFS: AttributeError: 
'CLITestV20ExtensionL2GWJSON' object has no attribute 'format'
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 891013

[Debian Bug Tracking System]

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

> tags 891013 + buster sid
Bug #891013 [src:mongo-tools] mongo-tools FTBFS with golang-1.10-go: mongostat 
build failed
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 889748

[Debian Bug Tracking System]

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

> tags 889748 + buster sid
Bug #889748 [src:diagnostics] diagnostics FTBFS: FAIL: stacktrace
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 888089

[Debian Bug Tracking System]

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

> tags 888089 + buster sid
Bug #888089 [src:botan1.10] botan1.10 EOL
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#891351: scilab segfaults at startup

[Michel Briand]

Package: scilab
Version: 5.5.2-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

scilab crashes at startup:

$ scilab
Segmentation fault

Packages installed are:

scilab 5.5.2-4
scilab-ann 0.4.2.4-1
scilab-celestlab 3.0.0-1-2
scilab-cli 5.5.2-4
scilab-data 5.5.2-4
scilab-doc 5.5.2-4
scilab-full-bin 5.5.2-4+b1
scilab-include 5.5.2-4+b1
scilab-minimal-bin 5.5.2-4+b1
scilab-plotlib 0.42-1
scilab-test 5.5.2-4

Best regards,
Michel

Debug:

$ scilab -debug
unning debug of Scilab [gdb]  :  gdb --args /usr/bin/scilab-bin -debug
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/scilab-bin...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/scilab-bin -debug
Installing openjdk unwinder
Traceback (most recent call last):
  File 
"/usr/share/gdb/auto-load/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so-gdb.py",
 line 52, in 
class Types(object):
  File 
"/usr/share/gdb/auto-load/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so-gdb.py",
 line 66, in Types
nmethodp_t = gdb.lookup_type('nmethod').pointer()
gdb.error: No type named nmethod.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd35df700 (LWP 6521)]
[New Thread 0x7fffd34de700 (LWP 6522)]
[New Thread 0x7fffd33dd700 (LWP 6523)]
[New Thread 0x7fffd32dc700 (LWP 6524)]

Thread 1 "scilab-bin" received signal SIGSEGV, Segmentation fault.
0x77de30c9 in _dl_lookup_symbol_x (undef_name=0x7fffeee89102 "strlen", 
undef_map=0x77f86f18, ref=ref@entry=0x7fff8138, 
symbol_scope=0x77f87270, version=0x77f6a5a0, 
type_class=type_class@entry=1, flags=5, skip_map=0x0) at dl-lookup.c:833
833 dl-lookup.c: Aucun fichier ou dossier de ce type.
(gdb) bt
#0  0x77de30c9 in _dl_lookup_symbol_x (
undef_name=0x7fffeee89102 "strlen", undef_map=0x77f86f18, 
ref=ref@entry=0x7fff8138, symbol_scope=0x77f87270, 
version=0x77f6a5a0, type_class=type_class@entry=1, flags=5, 
skip_map=0x0) at dl-lookup.c:833
#1  0x77de7ca4 in _dl_fixup (l=, 
reloc_arg=) at ../elf/dl-runtime.c:111
#2  0x77def37f in _dl_runtime_resolve_sse ()
at ../sysdeps/x86_64/dl-trampoline.h:212
#3  0x7fffec88bd90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x7fffec899038 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x77de2bc3 in do_lookup_x (
undef_name=undef_name@entry=0x7fffedd38e7e "__stpcpy_chk", 
new_hash=new_hash@entry=3373522011, 
old_hash=old_hash@entry=0x7fff84f0, ref=0x7fffedd34778, 
result=result@entry=0x7fff8500, scope=, 
i=, version=0x77f6a7c8, flags=1, skip=, 
type_class=1, undef_map=0x77f87960) at dl-lookup.c:423
#6  0x77de30d1 in _dl_lookup_symbol_x (
undef_name=0x7fffedd38e7e "__stpcpy_chk", undef_map=0x77f87960, 
ref=ref@entry=0x7fff85b8, symbol_scope=0x77f87cb8, 
version=0x77f6a7c8, type_class=type_class@entry=1, flags=1, 
skip_map=0x0) at dl-lookup.c:833
---Type  to continue, or q  to quit---
#7  0x77de7ca4 in _dl_fixup (l=, 
reloc_arg=) at ../elf/dl-runtime.c:111
#8  0x77def37f in _dl_runtime_resolve_sse ()
at ../sysdeps/x86_64/dl-trampoline.h:212
#9  0x77de9984 in _dl_name_match_p (
name=0x7fffa7b0 "\340\247\377\377\377\177", 
name@entry=0x7fffec89e906 "ld-linux-x86-64.so.2", 
map=map@entry=0x7fffad50) at dl-misc.c:295
#10 0x77de1699 in _dl_map_object (loader=0x7fff9780, 
name=0x7fffec89e906 "ld-linux-x86-64.so.2", type=1, trace_mode=0, 
mode=-30992, nsid=0) at dl-load.c:2186
#11 0x7fff9008 in ?? ()
#12 0x7fff9008 in ?? ()
#13 0x7fff9000 in ?? ()
#14 0x7fff8fff in ?? ()
#15 0x7fff8c0c in ?? ()
#16 0x7fff9170 in ?? ()
#17 0x812daafc8086f371 in ?? ()
#18 0x in ?? ()



-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (50, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr 

Processed: tagging 883525

[Debian Bug Tracking System]

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

> tags 883525 + buster sid
Bug #883525 [pdf2htmlex] pdf2htmlex: FTBFS with poppler 0.61.1
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 891238

[Debian Bug Tracking System]

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

> tags 891238 + buster sid
Bug #891238 [openam] openam: Is opennam still maintained?
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: source-highlight: diff for NMU version 3.1.8-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 877645 + pending
Bug #877645 [libsource-highlight-dev] source-highlight: libsource-highlight-dev 
depends on libboost-dev instead of libboost-regex-dev
Added tag(s) pending.

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

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

[Balasankar C]

Heya,

On Fri, 16 Feb 2018 06:10:36 +1100 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.

Attaching an html test file. It uses the libjs-jquery-caret.js package
you have in experimental along with the libjs-query-atwho package in
question.

Testing:
Note: I have enabled the atwho JS file from cloudflare CDN in it.
1. Open your browser and open the console debugger (In Firefox, press
Ctrl-Shift-j)
1. Open the attached file atwho-test.html in browser
2. Try typing `@` to the textbox, and see three names pop up. It means
the CDN one is working
3. Now comment the line which uses CDN and uncomment the one which uses
the packaged one. Save and exit.
4. Refresh the webpage, while keeping an eye on the debugger. You can
see the errors mentioned in this bug report pop up there.
5. Type `@` in the textbox and confirm nothing happens. It means the
packaged one is broken.

Please fix the package.

Regards
Balasankar C
Debian Developer

	
	
		
		
	



signature.asc
Description: OpenPGP digital signature

Bug#877645: source-highlight: diff for NMU version 3.1.8-1.2

[Adrian Bunk]

Control: tags 877645 + pending

Dear maintainer,

I've prepared an NMU for source-highlight (versioned as 3.1.8-1.2) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

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

diff -Nru source-highlight-3.1.8/debian/changelog source-highlight-3.1.8/debian/changelog
--- source-highlight-3.1.8/debian/changelog	2015-10-31 00:23:15.0 +0200
+++ source-highlight-3.1.8/debian/changelog	2018-02-24 20:36:52.0 +0200
@@ -1,3 +1,11 @@
+source-highlight (3.1.8-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * libsource-highlight-dev: Fix the dependency from
+libboost-dev to libboost-regex-dev. (Closes: #877645)
+
+ -- Adrian Bunk   Sat, 24 Feb 2018 20:36:52 +0200
+
 source-highlight (3.1.8-1.1) unstable; urgency=low
 
   * Non-maintainer upload
diff -Nru source-highlight-3.1.8/debian/control source-highlight-3.1.8/debian/control
--- source-highlight-3.1.8/debian/control	2015-10-24 13:58:32.0 +0300
+++ source-highlight-3.1.8/debian/control	2018-02-24 20:36:52.0 +0200
@@ -21,7 +21,7 @@
 Package: libsource-highlight-dev
 Section: libdevel
 Architecture: any
-Depends: dpkg (>= 1.15.4) | install-info, libboost-dev, libsource-highlight4v5 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: dpkg (>= 1.15.4) | install-info, libboost-regex-dev, libsource-highlight4v5 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
 Replaces: source-highlight (<< 3.1.4-1)
 Description: development files for source highlighting library
  These are the development files for the library that underlies the

Bug#891029: proposed solution

[Sebastian Kuzminsky]

Hi Andreas, thanks for the bug report.  This is clearly a problem that
needs to be fixed.

I propose to move all of dxf2gcode's modules (core, gui, globals, etc)
into a new top-level module called dxf2gcode.

Does that seem right to you?  (I'm not an expert python person...)

I've contacted upstream and they are receptive to this proposal.


-- 
Sebastian Kuzminsky

Processed: tagging 889046

[Debian Bug Tracking System]

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

> tags 889046 + fixed-upstream
Bug #889046 [src:ruby2.5] ruby2.5 FTBFS with tzdata 2018c-1
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#882305: libfinance-yahooquote-perl: yahooquote (and smtm) stopped working.

[Dirk Eddelbuettel]

On 24 February 2018 at 20:27, Adrian Bunk wrote:
| On Tue, Nov 21, 2017 at 06:11:46AM -0600, Dirk Eddelbuettel wrote:
| > 
| > On 21 November 2017 at 10:49, Ivan Rossi wrote:
| > | Package: libfinance-yahooquote-perl
| > | Version: 0.25
| > | Severity: grave
| > | Justification: renders package unusable
| > | 
| > | Dear Maintainer,
| > | 
| > | yahooquote (and smtm) stopped working. It seems that yahoo does not allow 
queries anymore.
| > 
| > That is the backend. Yahoo! stopped supporting this.
| > 
| > See several online discussions.
| > 
| > I think the only answer is to withdraw libfinance-yahooquote-perl from CRAN.
| 
| Should libfinance-yahooquote-perl and the reverse dependencies 
| beancounter and smtm be removed from unstable/stable/oldstable,
| or is there any use left for any of these packages?

I had someone email me with a libfinance-quote-perl replacement for data
gathering for beancounter, but it never happened.  I still use beancounter,
but deploy a different data insertion routine (based on R).

smtm is probably dead.

Feel free to remove one or both; they are rather marginal.

Cheers, Dirk
-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#882305: libfinance-yahooquote-perl: yahooquote (and smtm) stopped working.

[Adrian Bunk]

On Tue, Nov 21, 2017 at 06:11:46AM -0600, Dirk Eddelbuettel wrote:
> 
> On 21 November 2017 at 10:49, Ivan Rossi wrote:
> | Package: libfinance-yahooquote-perl
> | Version: 0.25
> | Severity: grave
> | Justification: renders package unusable
> | 
> | Dear Maintainer,
> | 
> | yahooquote (and smtm) stopped working. It seems that yahoo does not allow 
> queries anymore.
> 
> That is the backend. Yahoo! stopped supporting this.
> 
> See several online discussions.
> 
> I think the only answer is to withdraw libfinance-yahooquote-perl from CRAN.

Should libfinance-yahooquote-perl and the reverse dependencies 
beancounter and smtm be removed from unstable/stable/oldstable,
or is there any use left for any of these packages?

> Dirk

Thanks
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#891348: mpich: broken symlink: /usr/lib/TRIPLET/mpich/include -> ../../../include/TRIPLET/mpich

[Andreas Beckmann]

Package: mpich
Version: 3.3~b1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m32.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/TRIPLET/mpich/include -> ../../../include/TRIPLET/mpich


Some placeholders were not substituted ...


cheers,

Andreas


mpich_3.3~b1-4.log.gz
Description: application/gzip

Bug#891345: libosmocore-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libosmocoding.so -> libosmocoding.so.0.0.0

[Andreas Beckmann]

Package: libosmocore-dev
Version: 0.10.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m24.7s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libosmocoding.so -> libosmocoding.so.0.0.0


libosmocoding.so.0.0.0 does not need to exist in any package in the archive.


cheers,

Andreas


libosmocore-dev_0.10.2-2.log.gz
Description: application/gzip

Bug#889184: marked as done (cl-mcclim-doc is empty)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 18:04:24 +
with message-id 
and subject line Bug#889184: fixed in cl-mcclim 0.9.6.dfsg.cvs20100315-3
has caused the Debian Bug report #889184,
regarding cl-mcclim-doc is empty
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.)


-- 
889184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-mcclim-doc
Version: 0.9.6.dfsg.cvs20100315-1
Severity: grave

$ dpkg -L cl-mcclim-doc
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/cl-mcclim-doc
/usr/share/doc/cl-mcclim-doc/README.Debian
/usr/share/doc/cl-mcclim-doc/changelog.Debian.gz
/usr/share/doc/cl-mcclim-doc/copyright
$ cat /usr/share/doc/cl-mcclim-doc/README.Debian
This used to be a McCLIM user manual.  As the copying conditions of the manual
are unclear, it was removed from this package.  If you'd like to resolve the
problem with the author of the manual, please try to do so!

The complete CLIM specification can be found at
http://common-lisp.net/project/mcclim/ .
$ 
--- End Message ---
--- Begin Message ---
Source: cl-mcclim
Source-Version: 0.9.6.dfsg.cvs20100315-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 19:43:50 +0200
Source: cl-mcclim
Binary: cl-mcclim cl-mcclim-examples
Architecture: source
Version: 0.9.6.dfsg.cvs20100315-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 cl-mcclim  - Common Lisp graphic user interface toolkit
 cl-mcclim-examples - Common Lisp graphic user interface toolkit
Closes: 889184
Changes:
 cl-mcclim (0.9.6.dfsg.cvs20100315-3) unstable; urgency=medium
 .
   * QA upload.
   * Drop the empty cl-mcclim-doc package. (Closes: #889184)
Checksums-Sha1:
 fb514c06252fd91a06d7b63705c88d9a21e781f3 1924 
cl-mcclim_0.9.6.dfsg.cvs20100315-3.dsc
 49bf8b798a93587825e9d6e069ee3cbb88e6869d 5320 
cl-mcclim_0.9.6.dfsg.cvs20100315-3.debian.tar.xz
Checksums-Sha256:
 2f98721022eb0ebd2394716e3219db6307d0253d4d4132ce84659d3379225ea9 1924 
cl-mcclim_0.9.6.dfsg.cvs20100315-3.dsc
 0415288bd4d203c38b22261e49f42cdb6fbaa2b7cd0e789d8f2fbdb1b5a3be78 5320 
cl-mcclim_0.9.6.dfsg.cvs20100315-3.debian.tar.xz
Files:
 c82c4db56cfb2d2508e6730dd5837adc 1924 lisp optional 
cl-mcclim_0.9.6.dfsg.cvs20100315-3.dsc
 ada857debaf2427b2e4256aca1d5b8d7 5320 lisp optional 
cl-mcclim_0.9.6.dfsg.cvs20100315-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqRpTAACgkQiNJCh6LY
mLFI9BAAoVSu7Caq2r4n8LJXYUr/dEwjIZbxk0b6VgnDRazT1uh1WvoqNlbmVtrU
iHfdvan9A8VpLOl3IO3sJdHYPil0fysFHO0H1RkTB3Zb4uDB1NXezpXRlWtWKW0D
fjWoZGS8nxYFncL/6FqJFUVsqcxDBO/u0pZZYKSyuTdAwxa+yrCzP5dJHeKVoSmB
X/64atAT+h3neDk4U+JiA4KN32bHAHL14vFvkDBkHCMbWn5GqBWTXdj5Exo7lQSd
jZnaZ+dmToCLMdCyUK92OjNWOHtFTJsrhJJp72MGMUCaoKh3LclTLN3jbgFat9nK
O31yER1OMETmHWemFB52QfhwXO/cAbzul0YfrdGbEgl3TANfxctHvHvCtYIHyTS4
DcegFJmeo1uMiRtWh3t8u41iohe+p5zEb4d+rOdt8oaXv0hPdrnL7C4a0oeYBxhh
z1Ve0JnR70J9QlY3S11UHoDC/kExYWG77NWlOqFaR+pVlv/IWNhlrDHunJv/2Ts9
ovVHtu/e2knBTu/Vna1nfT+yxoeA0kfVvdCdxP8QHHAK4sMUIaXByVA7NvbuHTSX
nNWm22u/M9T0zUpvtSe5H09PKhLCqAk46sK4TsJ03c/KNRIC2v+mfwr5l2QEPybq
DLXViBhsAuxnVHu94Cb8wIk16RsLloKc5ZvzcIouXB+axtyX5bo=
=exq1
-END PGP SIGNATURE End Message ---

Bug#891344: nqp: uninstallable in sid: Depends: moarvm (< 2018.02) but 2018.02+dfsg-1 is to be installed

[Andreas Beckmann]

Package: nqp
Version: 2018.01+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 nqp : Depends: moarvm (< 2018.02) but 2018.02+dfsg-1 is to be installed


Cheers,

Andreas

Processed: camo: diff for NMU version 2.3.0+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 864620 + patch
Bug #864620 [camo] camo: missing dependency on openssl
Added tag(s) patch.
> tags 864620 + pending
Bug #864620 [camo] camo: missing dependency on openssl
Added tag(s) pending.

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

Bug#864620: camo: diff for NMU version 2.3.0+dfsg-1.1

[Adrian Bunk]

Control: tags 864620 + patch
Control: tags 864620 + pending

I've prepared an NMU for camo (versioned as 2.3.0+dfsg-1.1) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should cancel it.

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

diff -Nru camo-2.3.0+dfsg/debian/changelog camo-2.3.0+dfsg/debian/changelog
--- camo-2.3.0+dfsg/debian/changelog	2016-05-15 21:05:30.0 +0300
+++ camo-2.3.0+dfsg/debian/changelog	2018-02-24 19:23:54.0 +0200
@@ -1,3 +1,10 @@
+camo (2.3.0+dfsg-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add the missing dependency on openssl. (Closes: #864620)
+
+ -- Adrian Bunk   Sat, 24 Feb 2018 19:23:54 +0200
+
 camo (2.3.0+dfsg-1) unstable; urgency=medium
 
   [ Luke Faraone ]
diff -Nru camo-2.3.0+dfsg/debian/control camo-2.3.0+dfsg/debian/control
--- camo-2.3.0+dfsg/debian/control	2016-05-15 20:34:37.0 +0300
+++ camo-2.3.0+dfsg/debian/control	2018-02-24 19:22:25.0 +0200
@@ -13,7 +13,7 @@
 
 Package: camo
 Architecture: all
-Depends: nodejs (>= 0.10.0) , ${misc:Depends}
+Depends: nodejs (>= 0.10.0) , ${misc:Depends}, openssl
 Description: SSL/TLS image proxy to prevent mixed-content warnings
  Camo is an image proxy to prevent mixed content warnings on secure
  pages.

Bug#891325: Info received (Bug#891325: Acknowledgement (xfce4-weather-plugin: search function violates provider's usage policy))

[Sergio Gelato]

Here is a minimal patch to add a User-Agent: header to outgoing requests.
I've tested it and found that it restored location search functionality.

I don't consider it a complete fix since it doesn't make the search URI
configurable.
Attempt a minimal fix for Debian #891325.
Index: git/panel-plugin/weather.c
===
--- git.orig/panel-plugin/weather.c	2018-02-24 17:08:19.734257691 +0100
+++ git/panel-plugin/weather.c	2018-02-24 18:04:11.807358994 +0100
@@ -1852,6 +1852,10 @@
 g_object_set(data->session, SOUP_SESSION_TIMEOUT,
  CONN_TIMEOUT, NULL);
 
+/* Set the user agent to something sensible */
+g_object_set(data->session, SOUP_SESSION_USER_AGENT,
+ PACKAGE_NAME "/" PACKAGE_VERSION " ", NULL);
+
 /* Set the proxy URI from environment */
 proxy_uri = g_getenv("HTTP_PROXY");
 if (!proxy_uri)

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

[Pirate Praveen]

[copying the javascript maintainers list]

On Fri, 23 Feb 2018 11:37:31 +1100 Ben Finney  wrote:
> Control: tags -1 + unreproducible

I don't think this really a productive way of collaboration when two
people already reproduced this issue.

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

I don't think that is helpful at multiple levels.

1. It is clearly reproduce-able as two people already confirmed this bug.
2. You can easily compare the upstream built files. You just need to
inspect the two files.
3. When you are creating a custom build system, you are expected to make
sure it produces a result compatible with the original upstream build
system. Look at libjs-jquery as an example.
4. Refusing to use the upstream provided build system just makes this
really hard to support as you have already demonstrated in your
response. It also means you are making the barrier of collaboration
unreasonably high. This method was a last resort option when the build
tools were not packaged. But now when grunt, gulp, webpack, babel all
are available in main, still insisting on your custom reverse engineered
build script is not helpful.
5. It is even more ironic since gitlab is the only reverse dependency
for this library currently.



signature.asc
Description: OpenPGP digital signature

Bug#884973: marked as done (tp-smapi-dkms: build failure with 4.15.0)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 16:49:57 +
with message-id 
and subject line Bug#884973: fixed in tp-smapi 0.43-1
has caused the Debian Bug report #884973,
regarding tp-smapi-dkms: build failure with 4.15.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.)


-- 
884973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tp-smapi-dkms
Version: 0.42-1
Severity: serious
Justification: fails to build from source


Dear maintainer,

tp-smapi doesn't build for the upcoming kernels 4.15:

 /var/lib/dkms/tp_smapi/0.42/build/hdaps.c: In function ‘hdaps_init’:¬
  /var/lib/dkms/tp_smapi/0.42/build/hdaps.c:781:2: error: implicit declaration 
of function ‘init_timer’; did you mean ‘init_timers’? [-Werr>
init_timer(_timer);¬
^~¬
init_timers¬
  /var/lib/dkms/tp_smapi/0.42/build/hdaps.c:782:23: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]¬
hdaps_timer.function = hdaps_mousedev_poll;

Thanks
Elimar

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-rc4-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tp-smapi-dkms depends on:
ii  dkms  2.3-3

tp-smapi-dkms recommends no packages.

tp-smapi-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tp-smapi
Source-Version: 0.43-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 17:35:54 +0100
Source: tp-smapi
Binary: tp-smapi-dkms
Architecture: source
Version: 0.43-1
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov 
Changed-By: Evgeni Golov 
Description:
 tp-smapi-dkms - ThinkPad hardware/firmware access modules source - dkms version
Closes: 884973
Changes:
 tp-smapi (0.43-1) unstable; urgency=medium
 .
   * New upstream version 0.43
 + Support 4.15 kernel
   Closes: #884973
   * move to salsa.d.o
   * Standards-Version: 4.1.3.0
Checksums-Sha1:
 e9d789686694082373b3ea320e8f488a9984a61c 1851 tp-smapi_0.43-1.dsc
 39f80012b3ce369446efc1f08aef6cad713f2abd 40122 tp-smapi_0.43.orig.tar.gz
 147f6dd2acc454325ae140b9b75a0c9b0a7d6719 4316 tp-smapi_0.43-1.debian.tar.xz
 e2a213ec2efe776509bac3676e5498734c67937e 5403 tp-smapi_0.43-1_source.buildinfo
Checksums-Sha256:
 6899f1ceb7b23fe425f946a7b8862b4baa837cd4c1736f64cc1f07ecaad90c28 1851 
tp-smapi_0.43-1.dsc
 bcef9cd045d52a74d719b2a67ac4f5324994a856f123c0fbc55f1d769d367110 40122 
tp-smapi_0.43.orig.tar.gz
 404d1594e2b0ecf20fb240c0edd27d00686afed71a2076dd9683c94733c01c2f 4316 
tp-smapi_0.43-1.debian.tar.xz
 496bffcce697ebc673d32adfc2ee18cf879e49e85e518c635cd3480c100bb000 5403 
tp-smapi_0.43-1_source.buildinfo
Files:
 b9646862160222f654e4b11977d31897 1851 kernel optional tp-smapi_0.43-1.dsc
 c0f48a68aa83826220e965491bd32d17 40122 kernel optional 
tp-smapi_0.43.orig.tar.gz
 aadcbdb523f27ed4a1db19a7d9b64e19 4316 kernel optional 
tp-smapi_0.43-1.debian.tar.xz
 fe5ae4efacfda8aaf82e057ed406eaba 5403 kernel optional 
tp-smapi_0.43-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExW57amdnGPa81AdGTrsFQAtaiq4FAlqRlIMACgkQTrsFQAta
iq4xiA//eRb8GSxLkOGBEF/O04CWLMvEaxSDPb6O7Ky9JP1gU+X5p+eZw7i/d6U1
Os589yosf+CRuwRPkRckFecHITY/e+y5ix/Y+s6t1IJWmib+fGoFyIg+zSnPmjP+
kwrCVi5H/WxJLwmZBfFmL6GHXkYdQAXcAPW/6zNkHFDISXauf1pEWQgIlgvXJb78
gBDofcHQhztoAeOjguQdYoDEvUn5F8P0wxqmbdMmT8D2NmdewX/3M9xB4TMzAWT7
RP7Zuaf1e3Wg1aZu8hcVR9XDv4pGJ99t+1agbDhjPXd6fk+u+NtnhVxNZ4HwMfsW

Bug#884033: scilab-celestlab

[Sylvestre Ledru]

Context:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884033

+ some upstream folks

Le 19/12/2017 à 19:06, Julien Puydt a écrit :
> Hi,
>
> again, a number of heterogeneous strings, then I get a prompt after
> warnings, and quitting (several times) leads to a success.
>
> I haven't reproduced the segfault in this bug report, but I have found
> problems which indicate that the three listed packages do not support
> the most recent scilab version.
>
> What can we do to push things forward?
>
> Snark on #debian-science
>

Bug#891325: Acknowledgement (xfce4-weather-plugin: search function violates provider's usage policy)

[Sergio Gelato]

The Nominatim Usage Policy at 
https://operations.osmfoundation.org/policies/nominatim/ reads in part:

"Apps must make sure that they can switch the service at our request at any 
time (in particular, switching should be possible without requiring a software 
update). If at all possible, set up a proxy and also enable caching of 
requests."

I think that argues for making the search URL configurable by the user at run 
time (especially when one also considers this other suggestion: "If your 
requirements are even larger you can install your own instance of Nominatim"). 
Maybe the User-Agent string could be made configurable as well (with a sensible 
default).

Bug#889903: marked as done (python-gnupg needs an explict b-d on 2to3)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 15:51:20 +
with message-id 
and subject line Bug#889903: fixed in python-gnupg 0.4.1-2
has caused the Debian Bug report #889903,
regarding python-gnupg needs an explict b-d on 2to3
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.)


-- 
889903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-gnupg
Version: 0.4.1-1
Severity: serious
Tags: sid buster

python-gnupg needs an explict b-d on 2to3. The binary is now provided in a
separate package.

Please could you also run the testsuite with verbosity=2 ?

Thanks, Matthias
--- End Message ---
--- Begin Message ---
Source: python-gnupg
Source-Version: 0.4.1-2

We believe that the bug you reported is fixed in the latest version of
python-gnupg, 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.
Elena Grandi  (supplier of updated python-gnupg 
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: Sat, 24 Feb 2018 15:39:45 +0100
Source: python-gnupg
Binary: python-gnupg python3-gnupg
Architecture: source
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Elena Grandi 
Changed-By: Elena Grandi 
Description:
 python-gnupg - Python wrapper for the GNU Privacy Guard (Python 2.x)
 python3-gnupg - Python wrapper for the GNU Privacy Guard (Python 3.x)
Closes: 889903
Changes:
 python-gnupg (0.4.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
 .
   [ Elena Grandi ]
   * Add explicit dependency on 2to3. (Closes: #889903)
   * Update compat to 11
   * Updated Standards-Version to 4.1.3 (no additional changes needed)
Checksums-Sha1:
 c70d65d09b85d21681f9c462f89d97f249445611 1777 python-gnupg_0.4.1-2.dsc
 a7da11ccd84935a39c24b7bc06e11192a90f531c 7632 
python-gnupg_0.4.1-2.debian.tar.xz
 e460ad8021e0eb4e087b6e57d768ba83160d29f0 10023 
python-gnupg_0.4.1-2_source.buildinfo
Checksums-Sha256:
 020d89cc508ba61bb84a721739e995b707670689fcd6808066ebef0f6af1b26a 1777 
python-gnupg_0.4.1-2.dsc
 8bdf0213af11303ba5544768399fe16b337cccdb19702d40ac4b314f6d9b9fd1 7632 
python-gnupg_0.4.1-2.debian.tar.xz
 da7fa1b06991d0a662b1527c5a7978e1a536637127873979eea210b901eb1c41 10023 
python-gnupg_0.4.1-2_source.buildinfo
Files:
 38ecad26e154a86e3f8a8680a853fcfb 1777 python optional python-gnupg_0.4.1-2.dsc
 03659a2047f5904aa290dad510abd4c0 7632 python optional 
python-gnupg_0.4.1-2.debian.tar.xz
 fa5880d0052b1d6a701ca4d343ee7850 10023 python optional 
python-gnupg_0.4.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEtvPLnIYlAkFEv4aRWawWRpiv/+UFAlqRhZgACgkQWawWRpiv
/+UC7ggAl4r4tRcm3vS53JotdwVg28Y9mZHTxTTB7TqdK4J8RYcZCgdmDBK7j8/r
/gJjYc8/2sr2H9UohgYOI7IaWNh4hvsTaBVDPD3nNh5Y8Ub1hXPyjVyo7/HOSq5l
LKbAXVeiPAoWuwA1qo4MEhc6bffkHmQt+/ERTm0mWJY2BQrVUneXnilXyA4kjnWQ
EZx4xiBKt/Knst9ZwDHDd7rqvUZQBD4EImk+8VQ14YIYq5WHtcHdQm28ln3QMe+B
fVwUA83Be+yXHbBIAOyCckdQh2Am2aO/c9Hj62sQV66U85mNNH0KI3Waa2s59xBo
/GivY3nc996rc9JJth6GKIeIGmwkdg==
=KsQb
-END PGP SIGNATURE End Message ---

Bug#891325: xfce4-weather-plugin: search function violates provider's usage policy

[Sergio Gelato]

Package: xfce4-weather-plugin
Version: 0.8.9-1
Severity: serious

The location search functionality is currently broken. On investigation, I find
the following URL in the source code:
http://nominatim.openstreetmap.org/search?q=%s=xml
(where %s is replaced by the sanitized query string).

Using this URL in Firefox returns plausible results. Searching in the plugin
and capturing the wire traffic shows the following:

GET /search?q=%s=xml HTTP/1.1
Host: nominatim.openstreetmap.org
Connection: Keep-Alive

(note the lack of a referrer or user agent in the request), to which the
server responds with



Access blocked


Access blocked

You have been blocked because you have violated the
https://operations.osmfoundation.org/policies/nominatim/;>usage 
policy
of OSM's Nominatim geocoding service. Please be aware that OSM's resources are
limited and shared between many users. The usage policy is there to ensure that
the service remains usable for everybody.

Please review the terms and make sure that your
software adheres to the terms. You should in particular verify that you have 
set a
+valid referrer or a user agent that identifies your application, and
that you are not overusing the service with massive bulk requests.

If you feel that this block is unjustified or remains after you have adopted
your usage, you may contact the Nominatim system administrator at
nomina...@openstreetmap.org to have this block lifted.



I understand that the plugin relies on libsoup for this. The documentation for
soup_session_new_with_options mentions a SOUP_SESSION_USER_AGENT which one may
want to consider using.

Incidentally, libsoup supports TLS. An https:// URL would be an improvement,
except for debugging (so one may want to add a toggle for this, with https
being the default setting).

Bug#884973: tp-smapi-dkms: fails to build with the lates sid kernel (4.15.0-1-amd64)!

[alberto]

Package: tp-smapi-dkms
Followup-For: Bug #884973

Dear Maintainer,

it looks like that NOW that 4.15 is in sid (see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884973), the problem is still 
there.

I confirm the build failure:

Setting up tp-smapi-dkms (0.42-1) ...
Loading new tp_smapi-0.42 DKMS files...
Building for 4.15.0-1-amd64
Building initial module for 4.15.0-1-amd64
Error! Bad return status for module build on kernel: 4.15.0-1-amd64 (x86_64)
Consult /var/lib/dkms/tp_smapi/0.42/build/make.log for more information.

The content of /var/lib/dkms/tp_smapi/0.42/build/make.log is:

[...]
/var/lib/dkms/tp_smapi/0.42/build/hdaps.c: In function ‘hdaps_init’:
/var/lib/dkms/tp_smapi/0.42/build/hdaps.c:781:2: error: implicit declaration of 
function ‘init_timer’; did you mean ‘init_timers’? 
[-Werror=implicit-function-declaration]
  init_timer(_timer);
  ^~
  init_timers
/var/lib/dkms/tp_smapi/0.42/build/hdaps.c:782:23: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
  hdaps_timer.function = hdaps_mousedev_poll;
   ^
cc1: some warnings being treated as errors
[...]



*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages tp-smapi-dkms depends on:
ii  dkms  2.3-3

tp-smapi-dkms recommends no packages.

tp-smapi-dkms suggests no packages.

-- no debconf information

Bug#891330: openjdk-7: several vulnerabilities

[Emilio Pozuelo Monfort]

Source: openjdk-7
Version: 7u161-2.6.12-1
Severity: grave
Tags: security

Hi,

There are several vulnerabilities from the last Oracle CPU. There is
no new Icedtea release at this point AFAICS, so I guess our options are
to wait or to backport the fixes.

Thanks,
Emilio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#844923: marked as done (hg-git: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 14:31:17 +0100
with message-id <03094f8a-879d-d144-977a-12f8e9572...@collabora.co.uk>
and subject line hg-git no longer FTBFS
has caused the Debian Bug report #844923,
regarding hg-git: FTBFS: Test failures
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.)


-- 
844923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hg-git
Version: 0.8.5-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> -  +++ b/d/gamma  Mon Jan 01 00:00:13 2007 +
> -  @@ -1,1 +1,2 @@
> -   gamma
> -  +gamma 2
>
>  
>  incoming -r
> 
> Warning: test-incoming.t output changed
> ~.warning: Tested with unexpected mercurial lib: 
> /usr/lib/python2.7/dist-packages/mercurial
>  (expected /usr/bin/mercurial)
> 
> Skipped test-encoding.t: blacklisted
> Warned test-incoming.t: output changed
> # Ran 36 tests, 1 skipped, 1 warned, 0 failed.
> Makefile:13: recipe for target 'tests' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/hg-git_0.8.5-4_unstable.log

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

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

I think these bugs have been fixed in the last upload.

-- 
Cheers,
  Andrew--- End Message ---

Bug#843635: marked as done (hg-git: FTBFS: AttributeError: 'overlayrepo' object has no attribute 'manifestlog')

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 14:31:17 +0100
with message-id <03094f8a-879d-d144-977a-12f8e9572...@collabora.co.uk>
and subject line hg-git no longer FTBFS
has caused the Debian Bug report #843635,
regarding hg-git: FTBFS: AttributeError: 'overlayrepo' object has no attribute 
'manifestlog'
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.)


-- 
843635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hg-git
Version: 0.8.5-4
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

hg-git fails to build from source in unstable/amd64:

  […]

 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5'
  make tests TESTFLAGS="--blacklist 
/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/debian/hg-git.test_blacklist"
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5'
  cd tests && python run-tests.py --with-hg=`which hg` --blacklist 
/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/debian/hg-git.test_blacklist
  ..
  --- 
/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/tests/test-incoming.t
  +++ 
/home/lamby/temp/cdt.20161108133902.r30Tq7pYYm.db.hg-git/hg-git-0.8.5/tests/test-incoming.t.err
  @@ -55,6 +55,71 @@
 $ fn_git_commit -m'add d/gamma line 2'
 $ cd ../hgrepo
 $ hg incoming -p | grep -v 'no changes found'
  +  ** Unknown exception encountered with possibly-broken third-party 
extension hggit
  +  ** which supports versions 3.7 of Mercurial.
  +  ** Please disable hggit and try your action again.
  +  ** If that fixes the bug please report it to 
https://bitbucket.org/durin42/hg-git/issues
  +  ** Python 2.7.12+ (default, Nov  4 2016, 17:04:30) [GCC 6.2.0 20161027]
  +  ** Mercurial Distributed SCM (version 4.0)
  +  ** Extensions loaded: hggit, strip, mq
  +  Traceback (most recent call last):
  +File "/usr/bin/hg", line 45, in 
  +  mercurial.dispatch.run()
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 60, 
in run
  +  sys.exit((dispatch(request(sys.argv[1:])) or 0) & 255)
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 126, 
in dispatch
  +  ret = _runcatch(req)
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 216, 
in _runcatch
  +  return callcatch(ui, _runcatchfunc)
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 225, 
in callcatch
  +  return func()
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 205, 
in _runcatchfunc
  +  return _dispatch(req)
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 901, 
in _dispatch
  +  cmdpats, cmdoptions)
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 650, 
in runcommand
  +  ret = _runcommand(ui, options, cmd, d)
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 909, 
in _runcommand
  +  return cmdfunc()
  +File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 898, 
in 
  +  d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
  +File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1039, in 
check
  +  return func(*args, **kwargs)
  +File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 
220, in closure
  +  return func(*(args + a), **kw)
  +File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1039, in 
check
  +  return func(*args, **kwargs)
  +File "/usr/lib/python2.7/dist-packages/hgext/mq.py", line 3540, in 
mqcommand
  +  return orig(ui, repo, *args, **kwargs)
  +File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1039, in 
check
  +  return func(*args, **kwargs)
  +File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 
5151, in incoming
  +  return hg.incoming(ui, repo, source, opts)
  +File "/usr/lib/python2.7/dist-packages/mercurial/hg.py", line 837, in 
incoming
  +  return _incoming(display, subreporecurse, ui, repo, source, opts)
  +File "/usr/lib/python2.7/dist-packages/mercurial/hg.py", line 807, in 
_incoming
  +  displaychlist(other, chlist, displayer)
  +File 

Bug#891331: Beta from SQLA are *not* to upload, and full of bugs

[Thomas Goirand]

Source: sqlalchemy
Version: 1.2.0~b2+ds1-1
Severity: grave

Dear maintainer,

According to Mike Bayer, upstream for SQLAlchemy, you should *not* upload any
beta release of SQLAlchemy. Indeed, the version in Experimental has bugs,
for example this one:

http://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-dff3a469788c81a46440584406cb22be

This issue causes more than 600 unit test failures in Nova, about 32 in Manila,
and so on. This makes it impossible for me to run unit tests of OpenStack
Queens using sbuild and experimental, as this bad version of SQLAlchemy in
Experimental render unit tests as broken, when they are not (SQLA 1.2.0~b2 is).

Please upload a working version of SQLA in Experimental, for example 1.2.1,
which is accepted by OpenStack, as per this document:

https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L136

Thanks for your work on SQLA,
Cheers,

Thomas Goirand (zigo)

Bug#858398: Proposed (lib)curl switch to openssl 1.1

[Alessandro Ghedini]

On Wed, Feb 21, 2018 at 11:14:24AM -0800, Steve Langasek wrote:
> Hi again,
> 
> On Tue, Feb 20, 2018 at 06:16:34PM -0800, Steve Langasek wrote:
> > So, despite Julien's valid objection that core library conflicts cause
> > dist-upgrades to be more brittle, I think the right answer here is:
> 
> > - keep all sonames as-is.
> > - rename libcurl3 to libcurl4.
> > - leave the package names of the other variants as-is.
> > - *if* libcurl-gnutls.so.4 and libcurl-nss.so.4 sonames are known to exist
> >   elsewhere outside the Debian ecosystem, fix the symbol versions for
> >   libcurl3-gnutls and libcurl3-nss to use symbol aliases, so that CURL_FOO_4
> >   is used as the preferred name and CURL_FOO_3 is for compatibility only.
> >   (This is only worth doing if this increases binary compatibility;
> >   otherwise it's better to maintain bidirectional binary compatibility for
> >   Debian-built binaries.)
> > - change the symbol versions for libcurl4 to CURL_OPENSSL_4.
> 
> > I would be willing to prepare a patch that implements this.
> 
> I've done this now and raised an MP:
> 
>   https://salsa.debian.org/debian/curl/merge_requests/3
> 
> (I'm assuming there is no point in CURL_FOO_4 symbol version for
> libcurl-gnutls and libcurl-nss, because these sonames come from a
> Debian-specific patch and therefore there's no upstream binary compatibility
> to be concerned about.)
> 
> Thoughts on this?
> 
> In terms of ABI changes, this appears to be a strict subset of what
> Alessandro had proposed and would be binary-compatible for libcurl.so.4; so
> at minimum, we will probably adopt this change in Ubuntu and proceed with
> the transition ASAP there, even if Debian later decides to change the ABI
> for gnutls and nss variants also.

I'm fine with going ahead with just the libcurl3 -> libcurl4 transition for
now.

Julien: is this something that the Release Team would be ok with? As Steve
pinted out before, libcurl3 has significantly lower usage than lubcurl3-gnutls
so impact should be somewhat more limited.

I'd like to go ahead and upload Steve's patch to experimental (which means NEW
queue) soon, and then request the transition.

Cheers


signature.asc
Description: PGP signature

Bug#890927: marked as done (golang-golang-x-tools: FTBFS and Debci failure with golang-1.10-go)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 12:35:17 +
with message-id 
and subject line Bug#890927: fixed in golang-golang-x-tools 
1:0.0~git20180222.0.f8f2f88+ds-1
has caused the Debian Bug report #890927,
regarding golang-golang-x-tools: FTBFS and Debci failure with golang-1.10-go
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.)


-- 
890927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-golang-x-tools
Version: 1:0.0~git20170707.0.bce9606b+ds-1
Severity: serious

https://ci.debian.net/packages/g/golang-golang-x-tools/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-golang-x-tools.html

...
=== RUN   TestRewrites
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 2 files in 2 packages.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 4 occurrences in 1 file in 1 package.
Renamed 4 occurrences in 1 file in 1 package.
Renamed 4 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 3 occurrences in 2 files in 2 packages.
Renamed 3 occurrences in 2 files in 2 packages.
Renamed 3 occurrences in 2 files in 2 packages.
Renamed 5 occurrences in 1 file in 1 package.
Renamed 5 occurrences in 1 file in 1 package.
Renamed 3 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
/go/src/main/0.go:4:6: unused declared but not used
Renamed 2 occurrences in 1 file in 1 package.
--- FAIL: TestRewrites (0.17s)
rename_test.go:1250: -offset "/go/src/main/0.go:#33" -to "F": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#58" -to "F": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#63" -to "G": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#33" -to "F": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#32" -to "g": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#30" -to "g": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#30" -to "g": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
rename_test.go:1250: -offset "/go/src/main/0.go:#30" -to "g": rewritten 
file /go/src/main/0.go does not match expectation; got <<>>
want <<>>
=== RUN   TestDiff
--- PASS: TestDiff (11.59s)
FAIL
FAILgolang.org/x/tools/refactor/rename  12.949s
?   golang.org/x/tools/refactor/satisfy [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 -test.short 
golang.org/x/tools/benchmark/parse golang.org/x/tools/blog 
golang.org/x/tools/blog/atom golang.org/x/tools/cmd/benchcmp 
golang.org/x/tools/cmd/bundle golang.org/x/tools/cmd/callgraph 
golang.org/x/tools/cmd/compilebench golang.org/x/tools/cmd/digraph 
golang.org/x/tools/cmd/eg golang.org/x/tools/cmd/fiximports 
golang.org/x/tools/cmd/go-contrib-init golang.org/x/tools/cmd/godex 
golang.org/x/tools/cmd/godoc golang.org/x/tools/cmd/goimports 
golang.org/x/tools/cmd/gomvpkg golang.org/x/tools/cmd/gorename 
golang.org/x/tools/cmd/gotype golang.org/x/tools/cmd/goyacc 
golang.org/x/tools/cmd/guru golang.org/x/tools/cmd/guru/serial 

Bug#891319: error: module, invalid directory '/usr/lib/x86_64-linux-gnu/knot'

[vv221]

Package: knot
Version: 2.6.5-1
Severity: grave
Justification: renders package unusable

After upgrade from 2.6.4-1 to 2.6.5-1, knot fails to start as a service
with the following errors:

error: module, invalid directory '/usr/lib/x86_64-linux-gnu/knot'
critical: failed to open configuration database '' (invalid parameter)

With version 2.6.5-1 the directory /usr/lib/x86_64-linux-gnu/knot does not
exist.
With version 2.6.4-1 this directory exists but is empty.

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

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

Versions of packages knot depends on:
ii  adduser 3.117
ii  libc6   2.26-6
ii  libdnssec5  2.6.5-1
ii  libedit23.1-20170329-1
ii  libfstrm0   0.3.0-1+b1
ii  libgnutls30 3.5.18-1
ii  libknot72.6.5-1
ii  libprotobuf-c1  1.2.1-2
ii  libsystemd0 237-3
ii  liburcu60.10.1-1
ii  libzscanner12.6.5-1
ii  lsb-base9.20170808
ii  python3 3.6.4-1
ii  python3-yaml3.12-1+b1

Versions of packages knot recommends:
pn  python3-lmdb  

Versions of packages knot suggests:
ii  systemd  237-3

-- no debconf information

Bug#891307: activity-log-manager: Depends on NBS python-zeitgeist

[Jeremy Bicha]

Source: activity-log-manager
Version: 0.8.0-1.2
Severity: serious

activity-log-manager depends on python-zeitgeist. However, the latest
zeitgeist package in Debian dropped python-zeitgeist (no longer built
from source) and now provides python3-zeitgeist.

Like with https://bugs.debian.org/885256 this can be fixed by
upgrading activity-log-manager to the 0.9 series available in Ubuntu
which has switched from python to vala.

Thanks,
Jeremy Bicha

Bug#891304: libconfig-model-backend-augeas-perl: FTBFS: test failures

[Niko Tyni]

Package: libconfig-model-backend-augeas-perl
Version: 0.123-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

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

This regressed around 2018-02-19, probably with

 -libconfig-model-perl 2.116-1
 +libconfig-model-perl 2.117-1

See 
https://ci.debian.net/packages/libc/libconfig-model-backend-augeas-perl/unstable/amd64/

  #   Failed test 'check dump of augeas data'
  #   at t/augeas_backend.t line 93.
  #  got: '
  # '
  # expected: 'record:0
  #   ipaddr=127.0.0.1
  #   canonical=localhost
  #   alias=localhost -
  # record:1
  #   ipaddr=192.168.0.1
  #   canonical=bilbo - -
  # '
  
  [...]
  
  Test Summary Report
  ---
  t/augeas_backend.t (Wstat: 3072 Tests: 18 Failed: 12)
Failed tests:  3, 5-7, 9-10, 13-18
Non-zero exit status: 12
  t/augeas_from_scratch.t (Wstat: 512 Tests: 3 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan.  You planned 4 tests but ran 3.
  Files=4, Tests=26,  3 wallclock secs ( 0.05 usr  0.00 sys +  2.81 cusr  0.15 
csys =  3.01 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org

Processed: Re: onedrive: FTBFS on ppc64el: cc1d: error: cannot find source code for runtime library file 'object.d'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #882685 [src:onedrive] onedrive: FTBFS on ppc64el: cc1d: error: cannot find 
source code for runtime library file 'object.d'
Severity set to 'important' from 'serious'

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

Bug#882685: onedrive: FTBFS on ppc64el: cc1d: error: cannot find source code for runtime library file 'object.d'

[Jeremy Bicha]

Control: severity -1 important

The onedrive ppc64el binaries have been removed from Debian unstable
now. See https://bugs.debian.org/891265 (similar bugs have been filed
for gtk-d and tilix).

Therefore, I'm lowering the severity of this issue since this issue
should no longer block migration to testing.

Thanks,
Jeremy Bicha

Bug#890996: marked as done (profanity FTBFS on s390x: Test failed with exception: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 11:23:40 +
with message-id 
and subject line Bug#890996: fixed in profanity 0.5.1-2
has caused the Debian Bug report #890996,
regarding profanity FTBFS on s390x: Test failed with exception: Segmentation 
fault
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=profanity=s390x=0.5.1-1=1519170089=0

...
[ RUN  ] handle_offline_removes_chat_session
Test failed with exception: Segmentation fault(11)[  FAILED  ] 
handle_offline_removes_chat_session
[ RUN  ] lost_connection_clears_chat_sessions
unittests: src/xmpp/roster_list.c:82: roster_create: Assertion `roster == NULL' 
failed.
FAIL tests/unittests/unittests (exit status: 134)
--- End Message ---
--- Begin Message ---
Source: profanity
Source-Version: 0.5.1-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 10:54:41 +
Source: profanity
Binary: profanity
Architecture: source amd64
Version: 0.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: W. Martin Borgert 
Description:
 profanity  - console based XMPP client
Closes: 890996
Changes:
 profanity (0.5.1-2) unstable; urgency=medium
 .
   * Temporarily disable another problematic unittest (Closes: #890996),
 upstream knows about the unittest issues
   * Bump dh compat to 11
Checksums-Sha1:
 c84bcc452159c482e6fdf04fa8ac291f44601dea 2220 profanity_0.5.1-2.dsc
 43760f583f759415ec693765f8d61c01975b0fcf 4148 profanity_0.5.1-2.debian.tar.xz
 4bbac6d657fcc0a6e2ff92d33c412f5073ce0200 766792 
profanity-dbgsym_0.5.1-2_amd64.deb
 f4bb515aa3582c86e0234d220952e6b400a25910 12105 
profanity_0.5.1-2_amd64.buildinfo
 211580613276d5b28a5fcdacba06795da6092b0d 263812 profanity_0.5.1-2_amd64.deb
Checksums-Sha256:
 87238f286441629e7e3d181730742bce7a1892afb25ee7c2873158b260b6ff59 2220 
profanity_0.5.1-2.dsc
 52df9a762e18930cf7458bc0c819d547a2cbbadfa2a2eb299cb70a67ed9f4ec8 4148 
profanity_0.5.1-2.debian.tar.xz
 aa190e7f8467f0dba11466e6da89902f3af71906bfc2e46cefd241403011bcaf 766792 
profanity-dbgsym_0.5.1-2_amd64.deb
 73a7c99c3646225c53dde82d71286d9b02b76ea6e7e51f393658af4674158aa5 12105 
profanity_0.5.1-2_amd64.buildinfo
 b61d8c2e01e3e26b0641294b40a231a6b05261460dfd5aeb7e37cab5a345ce6c 263812 
profanity_0.5.1-2_amd64.deb
Files:
 c0b23864d9639a87cc22c0cc82882022 2220 net optional profanity_0.5.1-2.dsc
 291845ffa0f8f6813d25d4715fd00d21 4148 net optional 
profanity_0.5.1-2.debian.tar.xz
 f32c67a685ef2947972d58091bcaeb75 766792 debug optional 
profanity-dbgsym_0.5.1-2_amd64.deb
 603659cab8c4971962706d564084e1ac 12105 net optional 
profanity_0.5.1-2_amd64.buildinfo
 4244e7ef367ab66cd12e63275ddc5aa8 263812 net optional 
profanity_0.5.1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAlqRRzsACgkQ4+Chwoa5
Y+r6HRAAwRT2wWOrti+l3QiXiXM/i/opaXedgcVyE4WeB55Td7NFG53Jxw9SLuGV
Q/k8nwsdl04JYJwIG6na2tKECTb6++DsI1hvAaGJ8dxJeeTKKs5wCGeofAZnGndE
h+7QwluoOJMOyyaNlGsnA3JCDRmSjdH4ijdr+3NUeI2IEUiJAtE9BmjT4GQfLNr2
RSpyTrtJLf9/ogZN64zMBl3Wx1pxm1HDcWokSKb5v7HajH+1NPIEySn3RJV1Kfex
WHcMXlUxpBonF2cQ1+C4f7wcUuTuCVytavg4exLAD+oDRy8dpOmVeHapwhnscMOE
s4cG/rUn8oFiFIW2h6dNeJxhRXII7yhqHR3322iVVYFg4ARaW85bFe4N9GF3gTkx
88I8yJoJl5IDyPz8Q4pa9LkJ4kr/lpPq9r1v7G/ELXaGqg9pcTpZAJ5MIPTUZd/b
3/IkJBpmaxKOYGY7yI5dq3R9HMjLPBtg6yjOrYaKrFoW7Xc0+2rVzosrogmK+U+q
J/ZlH7HiSAXYl1YSpwLeqmbcbWDzPSRpzvCbcvbICHo94ExlHsk1jysGjLBUQmrs
MQqjiLnMKeq/x3vmspzq8W8B7KnxhW+f+ntSQm+nvfT6rrYvyQV++PhKQ6JbSQOI
GVzRpKLOVcp9Tu9cRURFO9KD8C64j5JK1/na5skV6REONaMWe5M=
=HYuf
-END PGP 

Bug#890938: marked as done (golang-google-cloud FTBFS: FAIL: TestAgainstJSONEncodingNoTags)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 11:21:44 +
with message-id 
and subject line Bug#890938: fixed in golang-google-cloud 0.9.0-4
has caused the Debian Bug report #890938,
regarding golang-google-cloud FTBFS: FAIL: TestAgainstJSONEncodingNoTags
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.)


-- 
890938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-google-cloud
Version: 0.9.0-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-google-cloud.html

...
=== RUN   TestAgainstJSONEncodingNoTags
--- FAIL: TestAgainstJSONEncodingNoTags (0.00s)
fields_test.go:443: json: cannot set embedded pointer to unexported 
struct: fields.embed2
--- End Message ---
--- Begin Message ---
Source: golang-google-cloud
Source-Version: 0.9.0-4

We believe that the bug you reported is fixed in the latest version of
golang-google-cloud, 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.
Martín Ferrari  (supplier of updated golang-google-cloud 
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: Sat, 24 Feb 2018 11:02:49 +
Source: golang-google-cloud
Binary: golang-google-cloud-dev golang-google-cloud-compute-metadata-dev
Architecture: source
Version: 0.9.0-4
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only 
cloud/compute/metadata)
 golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 890938
Changes:
 golang-google-cloud (0.9.0-4) unstable; urgency=high
 .
   * Fix FTBFS with golang 1.10. Closes: #890938.
   * Bump Standards-Vesion with no changes.
Checksums-Sha1:
 fe1198090f1b082396969faf5add984d509021aa 2709 golang-google-cloud_0.9.0-4.dsc
 857bebbdf95a3d49ba23bec407c0c62db9b36c22 6836 
golang-google-cloud_0.9.0-4.debian.tar.xz
 bb66a36b1f9594c2c1bfdcd7c7007232d8562e55 7010 
golang-google-cloud_0.9.0-4_amd64.buildinfo
Checksums-Sha256:
 1b63929fa4ee764eb982dd1f4761014840a50ad311683d81328407e97df658e0 2709 
golang-google-cloud_0.9.0-4.dsc
 e2c43d7a3d905d45414d0856dcb46e943f736ff2f8cea8b829ec493888f8bc91 6836 
golang-google-cloud_0.9.0-4.debian.tar.xz
 a1051f298a1747b46dea26535ce0e35090e9811a90409886b92f16c817f054cf 7010 
golang-google-cloud_0.9.0-4_amd64.buildinfo
Files:
 a51b94e83780c3583b6ac4bfe0db151d 2709 devel optional 
golang-google-cloud_0.9.0-4.dsc
 c23c47a82d3ed16efd3732f523a59f96 6836 devel optional 
golang-google-cloud_0.9.0-4.debian.tar.xz
 e978339fca75cba042b98d1086677bc6 7010 devel optional 
golang-google-cloud_0.9.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqRRx4ACgkQXdjgv5Gj
09qTxw//du1892xn5hiFx/3aNXM9QVv9I1lJvjQ2oXoaPYSxZG1SBDBavKSOzClO
zDlV1HXBiZfjt/bl4sONX8Cfo4TfiJLoz/ueJrBPWmlYqfDmwbeaIsH1X25AaW2i
Pepz2sK0f8qLavAcJlnuhyEOhrwMy+NlIKarb69hqFRA3Cq8eL3n6AxlG7yeoAZw
BKNPR3XBKoGkrOd+YPVNIQsIHwGrFjD5bXpllsovZVkUwR0XqdbqL7NCmjTiKF4Y
PSOlFRXFCuSYckOoscxoOW0P8o7q908UplJGgdf9mQofeh7NBoKzLWaEoDBzyRas
Mni2fe1C3T2IxwTU8KsdvURiuVw8zmaJAem8u/6gfVUp3TftGDjwC9zAFnBj6nKw
qwxUQKyiLYSCr6SBbiQcgqLAviyZqkvlwtLzBWvE5ZXHGl7afmjp1qbXdyeZuIbd
E7/JbZT0QLeyT+nX7SBRQ5qaptdJj1xSx7GQh9srCLA1RdG1/EpvKtD9UATcuu57
yEA/XcTZgTzld+jfbyhwgcWChguD69ChPhltk7wpK/AkXeWXBDHjFeT5GSd18Fqu
NMkzBEzJI68eC9I4jolaJj8J7/qHBA41GiFgu3gmyf9NC0O5W1XhkcnRNsdGtKX8
gmakEwAe7qJ8aaRYdMDQnBYA3/I4r+4DmHzCAVUIDtP9UVyFuvg=
=cshC
-END PGP SIGNATURE End Message ---

Bug#890938: Pending fixes for bugs in the golang-google-cloud package

[pkg-go-maintainers]

tag 890938 + pending
thanks

Some bugs in the golang-google-cloud package are closed in revision
655bf6e1f5fc6d8fa163e3595ce48558defb8f8c in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-cloud.git/commit/?id=655bf6e

Commit message:

Fix FTBFS with golang 1.10. Closes: #890938.

Processed: Pending fixes for bugs in the golang-google-cloud package

[Debian Bug Tracking System]

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

> tag 890938 + pending
Bug #890938 [src:golang-google-cloud] golang-google-cloud FTBFS: FAIL: 
TestAgainstJSONEncodingNoTags
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: open-coarrays FTBFS with cmake 3.10.2-1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.0.0~rc1-1
Bug #891300 [src:open-coarrays] open-coarrays FTBFS with cmake 3.10.2-1
Marked as fixed in versions open-coarrays/2.0.0~rc1-1.
> close -1
Bug #891300 [src:open-coarrays] open-coarrays FTBFS with cmake 3.10.2-1
Marked Bug as done

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

Bug#891300: open-coarrays FTBFS with cmake 3.10.2-1

[Adrian Bunk]

Source: open-coarrays
Version: 1.9.3-1
Severity: serious
Control: fixed -1 2.0.0~rc1-1
Control: close -1

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

...
cd 
/build/1st/open-coarrays-1.9.3/obj-x86_64-linux-gnu/src/tests/integration/coarrayHelloWorld
 && ../../../../bin/caf -DPREFIX_NAME=_gfortran_caf_ -DGCC_GE_7 
-DMPI_WORKING_MODULE -o 
/build/1st/open-coarrays-1.9.3/obj-x86_64-linux-gnu/bin/OpenCoarrays-1.9.3-tests/hello_multiverse
 
/build/1st/open-coarrays-1.9.3/src/tests/integration/coarrayHelloWorld/hello_multiverse.F90
gfortran: error: : No such file or directory
Error: comand:
   `/usr/bin/mpifort 
-I/build/1st/open-coarrays-1.9.3/obj-x86_64-linux-gnu/include/OpenCoarrays-1.9.3_GNU-7.3.0
 -fcoarray=lib -DPREFIX_NAME=_gfortran_caf_ -DGCC_GE_7 -DMPI_WORKING_MODULE -o 
/build/1st/open-coarrays-1.9.3/obj-x86_64-linux-gnu/bin/OpenCoarrays-1.9.3-tests/hello_multiverse
 
/build/1st/open-coarrays-1.9.3/src/tests/integration/coarrayHelloWorld/hello_multiverse.F90
 
/build/1st/open-coarrays-1.9.3/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libcaf_mpi.a
 `
failed to compile.
make[3]: *** 
[src/tests/integration/coarrayHelloWorld/CMakeFiles/build_hello_multiverse.dir/build.make:65:
 src/tests/integration/coarrayHelloWorld/hello_multiverse] Error 12


This bug appears to be already fixed in the version in experimental.

Bug#728372: marked as done (telepathy-phoenix: FTBFS: undefined reference to symbol 'fs_utils_get_default_element_properties')

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 12:53:50 +0200
with message-id <20180224105350.GB7636@localhost>
and subject line telepathy-phoenix has been removed from experimental
has caused the Debian Bug report #728372,
regarding telepathy-phoenix: FTBFS: undefined reference to symbol 
'fs_utils_get_default_element_properties'
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.)


-- 
728372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telepathy-phoenix
Version: 0.0.1-1
Severity: serious
Justification: fails to build from source
User: debian...@lists.debian.org
Usertags: piuparts


Hi,

telepathy-phoenix no longer builds in sid or experimental:

   dh_auto_build
make[1]: Entering directory `/tmp/buildd/telepathy-phoenix-0.0.1'
make  all-recursive
make[2]: Entering directory `/tmp/buildd/telepathy-phoenix-0.0.1'
Making all in src
make[3]: Entering directory `/tmp/buildd/telepathy-phoenix-0.0.1/src'
sed -e "s,[@]DATADIR[@],/tmp/buildd/telepathy-phoenix-0.0.1/data/uninstalled," \
-e "s,[@]PATH[@],/tmp/buildd/telepathy-phoenix-0.0.1/src," < phoenix.in 
 > phoenix-uninstalled
sed -e "s,[@]DATADIR[@],/tmp/buildd/telepathy-phoenix-0.0.1/data/uninstalled," \
-e "s,[@]PATH[@],/tmp/buildd/telepathy-phoenix-0.0.1/src," < 
phoenix-test.in  > phoenix-test-uninstalled
make  all-am
make[4]: Entering directory `/tmp/buildd/telepathy-phoenix-0.0.1/src'
  CC phoenix_authenticator-authenticator.o
authenticator.c: In function 'main':
authenticator.c:168:3: warning: 'g_type_init' is deprecated (declared at 
/usr/include/glib-2.0/gobject/gtype.h:669) [-Wdeprecated-declarations]
   g_type_init ();
   ^
  CCLD   phoenix-authenticator
  CC phoenix_echo_call-echo-call.o
echo-call.c: In function 'src_pad_unlinked_cb':
echo-call.c:89:3: warning: implicit declaration of function 
'gst_element_get_pad' [-Wimplicit-function-declaration]
   element_srcpad = gst_element_get_pad (element, "src");
   ^
echo-call.c:89:18: warning: assignment makes pointer from integer without a 
cast [enabled by default]
   element_srcpad = gst_element_get_pad (element, "src");
  ^
echo-call.c: In function 'setup_echo_sink':
echo-call.c:120:19: warning: assignment makes pointer from integer without a 
cast [enabled by default]
   element_sinkpad = gst_element_get_pad (element, "sink");
   ^
echo-call.c:121:18: warning: assignment makes pointer from integer without a 
cast [enabled by default]
   element_srcpad = gst_element_get_pad (element, "src");
  ^
echo-call.c: In function 'main':
echo-call.c:551:3: warning: 'g_type_init' is deprecated (declared at 
/usr/include/glib-2.0/gobject/gtype.h:669) [-Wdeprecated-declarations]
   g_type_init ();
   ^
  CC phoenix_echo_call-echo-call-info-dbus.o
echo-call-info-dbus.c: In function 'eci_call_info_skeleton_finalize':
echo-call-info-dbus.c:1094:3: warning: 'g_mutex_clear' is deprecated (declared 
at /usr/include/glib-2.0/glib/gthread.h:167): Not available before 2.32 
[-Wdeprecated-declarations]
   g_mutex_clear (>priv->lock);
   ^
echo-call-info-dbus.c: In function 'eci_call_info_skeleton_init':
echo-call-info-dbus.c:1240:3: warning: 'g_mutex_init' is deprecated (declared 
at /usr/include/glib-2.0/glib/gthread.h:165): Not available before 2.32 
[-Wdeprecated-declarations]
   g_mutex_init (>priv->lock);
   ^
  CCLD   phoenix-echo-call
/usr/bin/ld: phoenix_echo_call-echo-call.o: undefined reference to symbol 
'fs_utils_get_default_element_properties'
/usr/lib/x86_64-linux-gnu/libfarstream-0.2.so.2: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[4]: *** [phoenix-echo-call] Error 1
make[4]: Leaving directory `/tmp/buildd/telepathy-phoenix-0.0.1/src'
make[3]: *** [all] Error 2


Andreas
--- End Message ---
--- Begin Message ---
telepathy-phoenix has been removed from experimental:
  https://bugs.debian.org/890977

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--- End Message ---

Bug#785882: marked as done (telepathy-phoenix: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 12:53:50 +0200
with message-id <20180224105350.GB7636@localhost>
and subject line telepathy-phoenix has been removed from experimental
has caused the Debian Bug report #785882,
regarding telepathy-phoenix: Please update to GStreamer 1.x
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.)


-- 
785882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-phoenix
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package telepathy-phoenix currently still depends on GStreamer
0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
telepathy-phoenix has been removed from experimental:
  https://bugs.debian.org/890977

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--- End Message ---

Bug#891298: fis-gtm: Incomplete debian/copyright?

[Chris Lamb]

Source: fis-gtm
Version: 6.3-003A-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Amul Shah 

Hi,

I just ACCEPTed fis-gtm from NEW but noticed it was missing 
attribution in debian/copyright for at least md5hash.c. Please
clarify the situation in debian/copyright.

This is not exhaustive so please check over the entire package 
carefully - especially that directory for code copies - and address
these on your next upload.


Regards,

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

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Chris Lamb]

Source: gnome-keyring
Version: 3.27.4-2
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi,

I just ACCEPTed gnome-keyring from NEW but noticed it was missing 
attribution in debian/copyright for at least po/*, Collabora/Nokia
(for pkcs11/gkm/*), Steve Grubb, etc.

(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#891296: x2goserver binary-all FTBFS: chmod: cannot access 'debian/x2goserver/usr/lib/x2go/*': No such file or directory

[Adrian Bunk]

Source: x2goserver
Version: 4.1.0.0-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=x2goserver=all=4.1.0.0-2=1519444735=0

...
dh_install
# FIXME: upstream has some X2Go scripts in their tarball that are not executable
chmod a+x debian/x2goserver/usr/lib/x2go/*
chmod: cannot access 'debian/x2goserver/usr/lib/x2go/*': No such file or 
directory
make[1]: *** [debian/rules:31: override_dh_install] Error 1

Bug#891017: marked as done (plasma-desktop-data: fails to upgrade from 'stretch' - trying to overwrite /usr/share/locale/sr/LC_SCRIPTS/kfontinst/kfontinst.js)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 09:04:49 +
with message-id 
and subject line Bug#891017: fixed in plasma-desktop 4:5.12.2-1
has caused the Debian Bug report #891017,
regarding plasma-desktop-data: fails to upgrade from 'stretch' - trying to 
overwrite /usr/share/locale/sr/LC_SCRIPTS/kfontinst/kfontinst.js
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.)


-- 
891017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-desktop-data
Version: 4:5.12.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package plasma-desktop-data.
  Preparing to unpack .../13-plasma-desktop-data_4%3a5.12.0-3_all.deb ...
  Unpacking plasma-desktop-data (4:5.12.0-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-xfTt2o/13-plasma-desktop-data_4%3a5.12.0-3_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/locale/sr/LC_SCRIPTS/kfontinst/kfontinst.js', which is also in 
package kde-l10n-sr 4:16.04.3-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-xfTt2o/13-plasma-desktop-data_4%3a5.12.0-3_all.deb


cheers,

Andreas


kde-l10n-sr=4%16.04.3-1_plasma-desktop-data=4%5.12.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: plasma-desktop
Source-Version: 4:5.12.2-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 09:47:54 +0100
Source: plasma-desktop
Binary: kde-config-touchpad libkfontinst5 libkfontinstui5 plasma-desktop 
plasma-desktop-data plasma-desktop-dev
Architecture: source
Version: 4:5.12.2-1
Distribution: sid
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 kde-config-touchpad - transitional dummy package
 libkfontinst5 - Tools and widgets for the desktop library
 libkfontinstui5 - Tools and widgets for the desktop library
 plasma-desktop - Tools and widgets for the desktop
 plasma-desktop-data - Tools and widgets for the desktop data files
 plasma-desktop-dev - Tools and widgets for the desktop
Closes: 891017
Changes:
 plasma-desktop (4:5.12.2-1) sid; urgency=medium
 .
   * Bump kde-l10n version breaks/replaces.
 LC_SCRIPTS/kfontinst/kfontinst.js is now in plasma-desktop-data.
 Thanks to Andreas Beckmann for the report (Closes: 891017)
   * New upstream release (5.12.2).
   * Drop upstream patch
   * Release to sid
Checksums-Sha1:
 497d0e952ed0bd0cb0cc5d973131e70fdb64fff5 4146 plasma-desktop_5.12.2-1.dsc
 6138ed935bd16a91263a1751cb51209545fcc4f5 8433900 
plasma-desktop_5.12.2.orig.tar.xz
 a8fc5e879c12cb0b59f332839d21060ece2b0b62 22516 
plasma-desktop_5.12.2-1.debian.tar.xz
 232c8f317d2e50c2afe5179f3cb3ab0ff4051c82 28637 
plasma-desktop_5.12.2-1_source.buildinfo
Checksums-Sha256:
 3daadf8a596c27194e9859c273ebd19db4c26ff2e992de3ca6a98446b5f62b7f 4146 
plasma-desktop_5.12.2-1.dsc
 e5118e93b1b01c1acbab3b4c274c2d36f472759c9fd877308ca3efcfc384d573 8433900 
plasma-desktop_5.12.2.orig.tar.xz
 ad2550778ba7d6163a14a6941ad5428ddf75b7c2b4196c92dccf4b5424255149 22516 
plasma-desktop_5.12.2-1.debian.tar.xz
 2cb2b5a823459f6a60c5edb42bf36ae9526041d1d2c3ed1bbb4ecce62e1d1235 28637 
plasma-desktop_5.12.2-1_source.buildinfo

Bug#890852: marked as done (direnv FTBFS with golang-1.10-go: Printf format %/ has unknown verb /)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 09:04:21 +
with message-id 
and subject line Bug#890852: fixed in direnv 2.14.0-2
has caused the Debian Bug report #890852,
regarding direnv FTBFS with golang-1.10-go: Printf format %/ has unknown verb /
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.)


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

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

...
   dh_auto_test
make -j16 test
make[1]: Entering directory '/build/1st/direnv-2.14.0'
go test
go: disabling cache (/nonexistent/first-build/.cache/go-build) due to 
initialization failure: mkdir /nonexistent: permission denied
# _/build/1st/direnv-2.14.0
./cmd_stdlib.go:17: Printf format %/ has unknown verb /
FAIL_/build/1st/direnv-2.14.0 [build failed]
make[1]: *** [Makefile:51: test] Error 2
--- End Message ---
--- Begin Message ---
Source: direnv
Source-Version: 2.14.0-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 08:38:01 +
Source: direnv
Binary: direnv
Architecture: source amd64
Version: 2.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Punit Agrawal 
Changed-By: Punit Agrawal 
Description:
 direnv - Utility to set directory specific environment variables
Closes: 890852
Changes:
 direnv (2.14.0-2) unstable; urgency=medium
 .
   * Fix build failure with golang-1.10 (Closes: #890852)
   * Update standards version to 4.1.3
Checksums-Sha1:
 c51d898dd12325f31780cc2c75b2068267d1508f 1833 direnv_2.14.0-2.dsc
 81d21290d12b19828eece4d4d8eef1cedd03499c 4092 direnv_2.14.0-2.debian.tar.xz
 d83864e412e9ca0b6f7e8bc715ea3196e060d756 5679 direnv_2.14.0-2_amd64.buildinfo
 30f556974f20f861a475ac3230c45d0bc1c16280 707560 direnv_2.14.0-2_amd64.deb
Checksums-Sha256:
 eea74becbe7fe6b9bdee9e3b8c82c48db3e10a8f66394365468b658eead8377f 1833 
direnv_2.14.0-2.dsc
 efe20a28deda2ab08fd6acd9e2e048240cf2747196b87107491fdaa36178d82a 4092 
direnv_2.14.0-2.debian.tar.xz
 4eb879e3c65a1ea770a6719149508b178031171a4a0c23ed93b5e92ed4e5fff4 5679 
direnv_2.14.0-2_amd64.buildinfo
 55b766e8a694ff515693c022bcfd0e2962108b9b551b4a39ce161f000ffc9e76 707560 
direnv_2.14.0-2_amd64.deb
Files:
 ce6d1db17488d9b87681b2b502b8ef5f 1833 utils optional direnv_2.14.0-2.dsc
 c21de7835ff125802bc28723309a67a6 4092 utils optional 
direnv_2.14.0-2.debian.tar.xz
 5b0d8b13087fc16197cbd10fcb12fb37 5679 utils optional 
direnv_2.14.0-2_amd64.buildinfo
 03703f3092d5ae0346fcb3f4fbdcff8c 707560 utils optional 
direnv_2.14.0-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEvZ5M7BP8NElWggdO9Tkv0hP7/t0FAlqRJV8RHHB1bml0QGRl
Ymlhbi5vcmcACgkQ9Tkv0hP7/t3bjxAAj6d9VIjl3y7GoSTKeCoOpZqk5JAjmTu6
8HLYujwWf2lHQSPTc+3MyYApF6edmbkCa8+8VKmTB239yqPjbZPxI5SuxkMkExMt
iLgBxjpL/7pknFdBa7QphVDebRn+bo6kjJlrH6cg6+w//SMILFPE42NVAPQgLn11
f6wZkfd3AMxifTfkrjKF0oVFS6NeZirotL7g8S2/SBr5QQIH/4VuHVpiviWYcTpF
RaLLxhNBCwFUf5yT23xPHmFLOCDEpUwYzbCiQpfaEYKNP5xnMt6CrjXRW1Sj9rQm
vqLYBO5NEbXJcKnPSLFvESu/c0c17p901CYEMCNdoUi1fl4Y0RXJenxryX6sLhW5
ccinOiQG+Idtbvsb22GQn1X02YkhBAe468H/sM67H9QdgU94sGg9s2XQqkdo36c/
MhF16VRQDRyOodPRtyx5TdjU623E7o0Y2gV5IQ2gnpqraDedNCUx4fNv12KCcPE7
Rsc+hHU6HVYFztjNbNexBUzTpcG7TDlkgFnewc0vFCaA6XMeYeVzPgeEeFJCuVgj
St+KZx8L1DYXcBVtBObiNq/BtecYCB2dtUttWYY+M2ecNDEeWQo7ZXwHyAYaYhoH
c6z3trrguEWkodA6b5O4067jWfzgwvgS0x2t63g+DRfmWUOinSWe3geOGVD4sx1r
+hcwM64s5TQ=
=xTys
-END PGP SIGNATURE End Message ---

Bug#890628: marked as done (vmdb2: Test fail with ImportError: No module named yarnutils)

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 08:49:30 +
with message-id 
and subject line Bug#890628: fixed in cmdtest 0.32-1
has caused the Debian Bug report #890628,
regarding vmdb2: Test fail with ImportError: No module named yarnutils
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.)


-- 
890628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vmdb2
Version: 0.11-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

vmdb2 fails to build from source on Debian unstable (and Ubuntu bionic) due to
some test failures:

Parsing scenario file yarns/100-mvp.yarn
Parsing scenario file yarns/900-implements.yarn
Loading shell library yarns/lib.py
Found 3 scenarios
Running scenario happy path
DATADIR is /tmp/tmp2KW6Yu/happy_path/datadir
HOME for tests is /tmp/tmp2KW6Yu/happy_path/datadir/HOME
Running step "GIVEN a specification file called happy.vmdb containing { 
steps: [ { echo: "foo", teardown: "foo_teardown" }, { echo: "bar", teardown: 
"bar_teardown" } ] }"
ERROR: In scenario "happy path"
step "GIVEN a specification file called happy.vmdb containing { steps: [ { 
echo: "foo", teardown: "foo_teardown" }, { echo: "bar", teardown: 
"bar_teardown" } ] }" failed,
with exit code 1:
Standard output from shell command:

Standard error from shell command:
Traceback (most recent call last):
  File "/tmp/tmpWTVTHk", line 7, in 
from yarnutils import *
ImportError: No module named yarnutils

Running scenario jinja2 templating
DATADIR is /tmp/tmp1ZJQ1E/jinja2_templating/datadir
HOME for tests is /tmp/tmp1ZJQ1E/jinja2_templating/datadir/HOME
Running step "GIVEN a specification file called j2.vmdb containing { steps: 
[ { echo: "image is {{ output }}" }, { echo: "bar" }, ] }"
ERROR: In scenario "jinja2 templating"
step "GIVEN a specification file called j2.vmdb containing { steps: [ { echo: 
"image is {{ output }}" }, { echo: "bar" }, ] }" failed,
with exit code 1:
Standard output from shell command:

Standard error from shell command:
Traceback (most recent call last):
  File "/tmp/tmpttBqcz", line 7, in 
from yarnutils import *
ImportError: No module named yarnutils

Running scenario error handling
DATADIR is /tmp/tmp14Foj6/error_handling/datadir
HOME for tests is /tmp/tmp14Foj6/error_handling/datadir/HOME
Running step "GIVEN a specification file called unhappy.vmdb containing { 
steps: [ { echo: "foo", teardown: "foo_teardown" }, { error: "yikes", teardown: 
"WAT?!" }, { echo: "bar_step", teardown: "bar_teardown" } ] }"
ERROR: In scenario "error handling"
step "GIVEN a specification file called unhappy.vmdb containing { steps: [ { 
echo: "foo", teardown: "foo_teardown" }, { error: "yikes", teardown: "WAT?!" }, 
{ echo: "bar_step", teardown: "bar_teardown" } ] }" failed,
with exit code 1:
Standard output from shell command:

Standard error from shell command:
Traceback (most recent call last):
  File "/tmp/tmpXs6YW6", line 7, in 
from yarnutils import *
ImportError: No module named yarnutils

Failed scenarios:
- happy path
- jinja2 templating
- error handling
ERROR: Test suite FAILED in 3 scenarios
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

-- 
Benjamin Drung
Debian & Ubuntu Developer
--- End Message ---
--- Begin Message ---
Source: cmdtest
Source-Version: 0.32-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Feb 2018 09:59:34 +0200
Source: cmdtest
Binary: cmdtest
Architecture: source
Version: 0.32-1
Distribution: unstable
Urgency: medium
Maintainer: Lars Wirzenius 

Bug#889730: marked as done (virtualbox-dkms: No rule to make target '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o')

[Debian Bug Tracking System]

Your message dated Sat, 24 Feb 2018 08:28:38 + (UTC)
with message-id <1886120694.6870770.1519460918...@mail.yahoo.com>
and subject line Re: virtualbox-dkms: No rule to make target
has caused the Debian Bug report #889730,
regarding virtualbox-dkms: No rule to make target 
'/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o'
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.)


-- 
889730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 5.2.6-dfsg-3
Severity: grave
Justification: renders package unusable

The issue arose after I upgraded from kernel version 4.13 to 4.14.

The problem has been addressed in bug report #886747. However I can't
verify the alleged solution, since the URL mentioned in the report
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474) is invalid.

I followed the advice to upgrade the kbuild package, but to no avail.

Here's the make.log:

Tue Feb  6 14:16:38 CET 2018
make: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
  AR  /var/lib/dkms/virtualbox/5.2.6/build/built-in.o
  make[4]: *** No rule to make target
'/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o',
needed by '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/vboxdrv.o'.
Stop.
make[4]: *** Waiting for unfinished jobs
  AR  /var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/built-in.o
  /usr/src/linux-headers-4.14.0-3-common/scripts/Makefile.build:578:
recipe for target '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv' failed
make[3]: *** [/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv] Error 2
/usr/src/linux-headers-4.14.0-3-common/Makefile:1525: recipe for
target '_module_/var/lib/dkms/virtualbox/5.2.6/build' failed
make[2]: *** [_module_/var/lib/dkms/virtualbox/5.2.6/build] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.14.0-3-amd64'




-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_GB.ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.2.6-dfsg-3

virtualbox-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
 '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o'
MIME-Version: 1.0
Content-Type: multipart/alternative; 
boundary="=_Part_6870769_1022836264.1519460918796"

--=_Part_6870769_1022836264.1519460918796
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, 06 Feb 2018 14:26:17 +0100 Martin Haase  wrote:
> Package: virtualbox-dkms
> Version: 5.2.6-dfsg-3
> Severity: grave
> Justification: renders package unusable
>=20


Hello, I tried but I couldn't reproduce... Maybe kernel folks fixed it?
Closing
G.
> The issue arose after I upgraded from kernel version 4.13 to 4.14.
>=20
> The problem has been addressed in bug report #886747. However I can't
> verify the alleged solution, since the URL mentioned in the report
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D886474) is invalid.
>=20
> I followed the advice to upgrade the kbuild package, but to no avail.
>=20
> Here's the make.log:
> 
> Tue Feb=C2=A0 6 14:16:38 CET 2018
> make: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
>=C2=A0=C2=A0 AR=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /var/lib/dkms/virtualbox/5.2=
.6/build/built-in.o
>=C2=A0=C2=A0 make[4]: *** No rule to make target
> '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/linux/SUPDrv-linux.o',
> needed by '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv/vboxdrv.o'.
> Stop.
> make[4]: *** Waiting for unfinished jobs
>=C2=A0=C2=A0 AR=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /var/lib/dkms/virtualbox/5.2=
.6/build/vboxdrv/built-in.o
>=C2=A0=C2=A0 /usr/src/linux-headers-4.14.0-3-common/scripts/Makefile.build=
:578:
> recipe for target '/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv' failed
> make[3]: *** [/var/lib/dkms/virtualbox/5.2.6/build/vboxdrv] Error 2
> /usr/src/linux-headers-4.14.0-3-common/Makefile:1525: recipe for