Processed: forcibly merging 733422 832878

[Debian Bug Tracking System]

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

> forcemerge 733422 832878
Bug #733422 {Done: Joao Eriberto Mota Filho } [src:hyde] 
hyde: FTBFS: dpkg-buildpackage: dpkg-source: error: unrepresentable changes to 
source
Bug #733422 {Done: Joao Eriberto Mota Filho } [src:hyde] 
hyde: FTBFS: dpkg-buildpackage: dpkg-source: error: unrepresentable changes to 
source
The source 'hyde' and version '0.8.5a1-4.1+rm' do not appear to match any 
binary packages
Marked as fixed in versions hyde/0.8.5a1-4.1+rm.
Added tag(s) buster.
Bug #832878 {Done: Debian FTP Masters } 
[src:hyde] hyde: FTBFS: urllib2.URLError: 
The source hyde and version 0.8.5a1-4.1+rm do not appear to match any binary 
packages
Marked as fixed in versions hyde/0.8.5a1-4.1+rm and hyde/0.8.5a1-4.1; no longer 
marked as fixed in versions 0.8.5a1-4.1+rm.
Added tag(s) patch and jessie.
Merged 733422 832878
> thanks
Stopping processing here.

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

Processed: unarchiving 733422

[Debian Bug Tracking System]

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

> unarchive 733422
Bug #733422 {Done: Joao Eriberto Mota Filho } [src:hyde] 
hyde: FTBFS: dpkg-buildpackage: dpkg-source: error: unrepresentable changes to 
source
Unarchived Bug 733422
> thanks
Stopping processing here.

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

Processed: unarchiving 832878

[Debian Bug Tracking System]

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

> unarchive 832878
Bug #832878 {Done: Debian FTP Masters } 
[src:hyde] hyde: FTBFS: urllib2.URLError: 
Unarchived Bug 832878
> thanks
Stopping processing here.

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

Bug#888101: marked as done (libpinyin13-dev ships same files as libpinyin7-dev without Conflicts)

[Debian Bug Tracking System]

Your message dated Thu, 1 Feb 2018 15:48:47 +0800
with message-id <20180201074847.ga18...@gmail.com>
and subject line Not a bug
has caused the Debian Bug report #888101,
regarding libpinyin13-dev ships same files as libpinyin7-dev without Conflicts
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.)


-- 
888101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpinyin13-dev
Version: 2.1.0-1~exp3
Severity: serious

libpinyin13-dev and libpinyin7-dev both include these files:

/usr/lib/x86_64-linux-gnu/libpinyin.a
/usr/lib/x86_64-linux-gnu/libpinyin.so
/usr/lib/x86_64-linux-gnu/pkgconfig/
/usr/lib/x86_64-linux-gnu/pkgconfig/libpinyin.pc

I think you need to add Conflicts: libpinyin7-dev.

See Debian Policy § 7.4
https://www.debian.org/doc/debian-policy/#conflicting-binary-packages-conflicts

By the way, why haven't you uploaded the new libpinyin to unstable yet?

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

The current control for libpinyin13-dev is:

  Package: libpinyin13-dev
  Provides: libpinyin-dev
  Conflicts: libpinyin-dev

And after checking the policy, I think it falls to the following case
described in policy:

  Conflicts should be used
  ..
* in conjunction with Provides when only one package providing a given 
virtual facility may be unpacked at a time (see Virtual packages - Provides),

So I think we don't need to Conflicts libpinyin7-dev.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


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

Processed: Re: Bug#888957: linuxbrew-wrapper: Linuxbrew formulas may build or install non-free software

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 linuxbrew-wrapper should go to contrib: It is an installer for 
> linuxbrew
Bug #888957 [linuxbrew-wrapper] linuxbrew-wrapper: Linuxbrew formulas may build 
or install non-free software
Changed Bug title to 'linuxbrew-wrapper should go to contrib: It is an 
installer for linuxbrew' from 'linuxbrew-wrapper: Linuxbrew formulas may build 
or install non-free software'.
> found -1 20150804-1
Bug #888957 [linuxbrew-wrapper] linuxbrew-wrapper should go to contrib: It is 
an installer for linuxbrew
Marked as found in versions linuxbrew-wrapper/20150804-1.

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

Bug#888957: linuxbrew-wrapper: Linuxbrew formulas may build or install non-free software

[Adrian Bunk]

Control: retitle -1 linuxbrew-wrapper should go to contrib: It is an installer 
for linuxbrew
Control: found -1 20150804-1

On Wed, Jan 31, 2018 at 10:38:42AM -0500, John Scott wrote:
> Package: linuxbrew-wrapper
> Version: 20170516-2
> Severity: serious
> Justification: Policy 2.2.1
> 
> Though the linuxbrew-wrapper package is free just as Linuxbrew is, Linuxbrew 
> does not commit to only free software. Linuxbrew's OpenCV formula builds with 
> -DOPENCV_ENABLE_NONFREE=ON, and FFmpeg builds with --enable-nonfree. Though a 
> comment in ffmpeg.rb notes that the flag produces unredistributable binaries, 
> no notice is given to the user.
> 
> Users that commit to only using free software may install this package and 
> believe that it is free because it is in main. Though the package is free, 
> and Linuxbrew is free, the purpose of Linuxbrew and this wrapper package is 
> to install software from outside of the Debian repository (some of which is 
> non-free).

With that logic apt would also have to go to contrib.

> I believe that this violates Debian Policy that packages in main "must not 
> require or recommend a package outside of main for compilation or execution."

The accepted interpretation of that section of policy is that a program 
can be in main as long as there is some way to use it with free software.

Additional optional uses with non-free software are fine.

> Because this package is a wrapper that will "invoke upstream install script 
> if found no linuxbrew instance" upon installation, I believe package is not 
> suited for main and is probably better suited for contrib. The Debian Policy 
> Manual says that packages that would be included in contrib include "wrapper 
> packages or other sorts of free accessories for non-free programs." Linuxbrew 
> is a wrapper for installing (with or without building from source) programs 
> that, though many of them are free, some are not.

This is actually a reason why it should be in contrib:
The package is just an installer that downloads the actual program.

cu
Adrian

-- 

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

Bug#887688: [debhelper-devel] Bug#887688: debhelper: empty build of src:ck

[Adrian Bunk]

On Wed, Jan 31, 2018 at 07:11:00PM +, Niels Thykier wrote:
> clone 887688 -1
> retitle -1 debhelper: dh_makeshlibs --no-act isn't and causes FTBFS
> tags 887688 pending
> thanks
> 
> Hi,
> 
> Assuming I have not overlooked something, then I believe this bug is now
> resolved in debhelper and will close it in a few days.  This is because:
> 
>  * I have filed bugs for all known packages that currently FTBFS due to
>empty or incomplete targets (usually caused by .PHONY).  Most of
>these have a patch attached.
> 
>  * The autoreconf related issue was solved in dh-autoreconf/16, which
>solved the problems in some of the originally listed packages.
>(See #887482)
> 
>  * There was a regression in the --no-act that caused a single FTBFS.
>This has a patch in debhelper master that has yet to be uploaded
>(I just cloned this bug for that purpose).
> 
> 
> Overview of the packages mentioned in this bug report
> =

Thanks a lot for doing this.

> Packages that has an open RC bug related to this issue:
> 
>  * apr: #888593 (patch)
>  * ck: #888591 (patch)
>  * cpputest: #888598 (patch)
>  * debian-handbook: #888578 (patch)
>  * iaxmodem: #888601 (patch)
>  * moarvm: #888582 (patch)
>  * jscommunicator: #888579 (patch)
>  * libtemplate-perl: #888663 (patch)
>  * monotone: #888612 (patch)
>...

One new .PHONY case that needs a bug:
  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apr-util.html

> Thanks,
> ~Niels

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 889006 buster sid
Bug #889006 [debhelper,dh-autoreconf] dh-autoreconf is run before patching
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: dh-autoreconf is run before patching

[Debian Bug Tracking System]

Processing control commands:

> found -1 16
Bug #889006 [debhelper,dh-autoreconf] dh-autoreconf is run before patching
There is no source info for the package 'debhelper' at version '16' with 
architecture ''
Marked as found in versions dh-autoreconf/16.
> affects -1 src:dansguardian
Bug #889006 [debhelper,dh-autoreconf] dh-autoreconf is run before patching
Added indication that 889006 affects src:dansguardian

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

Bug#889005: mm3d FTBFS on armel/armhf: error: OpenGL (with GLU) is required

[Adrian Bunk]

Source: mm3d
Version: 1.3.9-1
Severity: serious

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

...
checking for OpenGL... yes
checking for Qt... yes:
QT_CXXFLAGS=-I/usr/include/arm-linux-gnueabi/qt5
QT_DIR=
QT_LIBS=-L/usr/lib/arm-linux-gnueabi/qt5 -lQt5Core -lQt5Gui -lQt5Widgets 
-lQt5OpenGL -lQt5Network 
QT_UIC=/usr/lib/arm-linux-gnueabi/qt5/bin/uic
QT_MOC=/usr/lib/arm-linux-gnueabi/qt5/bin/moc
QT_LRELEASE=/usr/lib/arm-linux-gnueabi/qt5/bin/lrelease
checking correct functioning of Qt installation... success
checking Qt OpenGL... success
checking for x11 fonts... no
checking for gettimeofday... yes

configure: error: OpenGL (with GLU) is required.


Ideally it should be made working when Qt is using
OpenGL ES, but if that is not possible please:
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev, and
- submit a bug against ftp.debian.org asking for the
  removal of the old armel+armhf binaries from unstable

Bug#889006: dh-autoreconf is run before patching

[Adrian Bunk]

Package: debhelper,dh-autoreconf
Severity: serious
Control: found -1 16
Control: affects -1 src:dansguardian

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

...
   dh_autoreconf
configure.ac:14: installing './compile'
src/Makefile.am:13: warning: source file 'contentscanners/clamav.cpp' is in a 
subdirectory,
src/Makefile.am:13: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding 
output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same 
subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
src/Makefile.am:31: warning: source file 'contentscanners/icapscan.cpp' is in a 
subdirectory,
src/Makefile.am:31: but option 'subdir-objects' is disabled
src/Makefile.am:39: warning: source file 'contentscanners/kavdscan.cpp' is in a 
subdirectory,
src/Makefile.am:39: but option 'subdir-objects' is disabled
src/Makefile.am:25: warning: source file 'contentscanners/clamdscan.cpp' is in 
a subdirectory,
src/Makefile.am:25: but option 'subdir-objects' is disabled
src/Makefile.am:43: warning: source file 'contentscanners/commandlinescan.cpp' 
is in a subdirectory,
src/Makefile.am:43: but option 'subdir-objects' is disabled
src/Makefile.am:48: warning: source file 'downloadmanagers/default.cpp' is in a 
subdirectory,
src/Makefile.am:48: but option 'subdir-objects' is disabled
src/Makefile.am:53: warning: source file 'downloadmanagers/fancy.cpp' is in a 
subdirectory,
src/Makefile.am:53: but option 'subdir-objects' is disabled
src/Makefile.am:57: warning: source file 'downloadmanagers/trickle.cpp' is in a 
subdirectory,
src/Makefile.am:57: but option 'subdir-objects' is disabled
src/Makefile.am:62: warning: source file 'authplugins/proxy.cpp' is in a 
subdirectory,
src/Makefile.am:62: but option 'subdir-objects' is disabled
src/Makefile.am:63: warning: source file 'authplugins/ident.cpp' is in a 
subdirectory,
src/Makefile.am:63: but option 'subdir-objects' is disabled
src/Makefile.am:64: warning: source file 'authplugins/ip.cpp' is in a 
subdirectory,
src/Makefile.am:64: but option 'subdir-objects' is disabled
src/Makefile.am:70: warning: source file 'authplugins/ntlm.cpp' is in a 
subdirectory,
src/Makefile.am:70: but option 'subdir-objects' is disabled
src/Makefile.am:65: warning: source file 'authplugins/digest.cpp' is in a 
subdirectory,
src/Makefile.am:65: but option 'subdir-objects' is disabled
   dh_dpatch_patch
applying patch 03_add_unconfigures to ./ ... ok.
applying patch 07_fix_config_paths to ./ ... ok.
applying patch 11_FixOptionContainer.cpp_on_arm to ./ ... ok.
applying patch 50_clamav095_support to ./ ... ok.
applying patch 60_add_gcc4.4_support to ./ ... ok.
applying patch 65-fix_clamdsocket to ./ ... ok.
applying patch 70-gcc4.6 to ./ ... ok.
applying patch 70_fix_clamav_detection to ./ ... ok.
applying patch 80_fix_libcre3_max_sub_expression_allocation to ./ ... ok.
...
checking for CLAMAV... no
configure: error: Package requirements (libclamav >= 4) were not met:

Requested 'libclamav >= 4' but version of libclamav is 0.99.3-beta2


This is caused by:


dh-autoreconf (16) unstable; urgency=medium
...
  * Run dh_autoreconf after dh_update_autotools_config,
not before dh_auto_configure

Processed: Correct the affects

[Debian Bug Tracking System]

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

> affects 888974 - src:ck
Bug #888974 {Done: Niels Thykier } [debhelper] debhelper: 
dh_makeshlibs --no-act isn't and causes FTBFS
Removed indication that 888974 affects src:ck
> affects 888974 src:scidavis
Bug #888974 {Done: Niels Thykier } [debhelper] debhelper: 
dh_makeshlibs --no-act isn't and causes FTBFS
Added indication that 888974 affects src:scidavis
> thanks
Stopping processing here.

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

Bug#888484: [Pkg-clamav-devel] Bug#888484: Updates for stretch/jessie not in security repo

[Salvatore Bonaccorso]

Hi Scott,

On Wed, Jan 31, 2018 at 10:57:30PM -0500, Scott Kitterman wrote:
> On Thursday, February 01, 2018 01:03:29 AM Matija Nalis wrote:
> > nor does debian security tracker list the updates as available for
> > jessie/stretch:
> > https://security-tracker.debian.org/tracker/source-package/clamav
> > 
> > (security-tracked does say in hover text that jessie
> > "gets updated via -updates", so it should pick that up)
> > 
> > it correctly reports wheezy, buster and sid as fixed.
> > 
> > for example, see also
> > https://security-tracker.debian.org/tracker/CVE-2017-12376
> > 
> > this looks to me also like something that should be fixed (somewhere)?
> 
> By design, the security tracker doesn't consider things 'fixed' in stable via 
> updates until after it's included in a Debian point release.  I agree it's 
> not 
> totally clear, but the way it's working is what the security team intends.

JFTR, yes that's correct. As a side node, we might need to look into
starting -updates and consider what is there to be 'accepted' for
stable (oldstable) already by the stable release managers. This would
need some work on the security-tracker side which would not support
that yet. Will think about it.

Regards,
Salvatore

Bug#889003: netgen FTBFS with libtogl-dev 2.0-1

[Adrian Bunk]

Source: netgen
Version: 4.9.13.dfsg-11
Severity: serious

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

...
libtool: link: g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -rdynamic -Wl,-z 
-Wl,relro -o netgen demoview.o ngappinit.o ngpkg.o onetcl.o nginterface.o 
nginterface_v2.o parallelfunc.o parallelinterface.o  
../libsrc/visualization/libvisual.a ../libsrc/csg/.libs/libcsg.a 
../libsrc/geom2d/.libs/libgeom2d.a ../libsrc/interface/.libs/libinterface.a 
../libsrc/stlgeom/.libs/libstl.a ../libsrc/occ/.libs/libocc.a 
../libsrc/meshing/.libs/libmesh.a ../libsrc/gprim/.libs/libgprim.a 
../libsrc/linalg/.libs/libla.a ../libsrc/general/.libs/libgen.a -L/usr/lib 
-lTKernel -lTKGeomBase -lTKMath -lTKG2d -lTKG3d -lTKXSBase -lTKOffset 
-lTKFillet -lTKShHealing -lTKMesh -lTKMeshVS -lTKTopAlgo -lTKGeomAlgo -lTKBool 
-lTKPrim -lTKBO -lTKIGES -lTKBRep -lTKSTEPBase -lTKSTEP -lTKSTL -lTKSTEPAttr 
-lTKSTEP209 -lTKXDESTEP -lTKXDEIGES -lTKXCAF -lTKLCAF -lFWOSPlugin 
-L/usr/lib/tk8.5/Togl1.7 -lTogl -lGLU -L/usr/lib/x86_64-linux-gnu -ltk8.5 
-ltcl8.5 -ljpeg -lGL
  -lXmu -lpthread
ngpkg.o: In function `Ng_Init':
./ng/ngpkg.cpp:5228: undefined reference to `Togl_CreateFunc'
./ng/ngpkg.cpp:5229: undefined reference to `Togl_DestroyFunc'
./ng/ngpkg.cpp:5230: undefined reference to `Togl_DisplayFunc'
./ng/ngpkg.cpp:5231: undefined reference to `Togl_ReshapeFunc'
./ng/ngpkg.cpp:5233: undefined reference to `Togl_CreateCommand'
./ng/ngpkg.cpp:5234: undefined reference to `Togl_CreateCommand'
collect2: error: ld returned 1 exit status
Makefile:526: recipe for target 'netgen' failed
make[3]: *** [netgen] Error 1

Bug#888917: ocrmypdf fails to run it's testsuite

[Sean Whitton]

Hello James,

On Wed, Jan 31 2018, James R Barlow wrote:

> Upstream here.

Thanks for the info.

> The reason the suite fails like that is that mandatory-for-testing
> dependencies were also removed.
>
> The test suite runs on Travis CI in 10-12 minutes. On Debian CI, 15
> minutes. For comparison ffmpeg, another compute intensive CLI program,
> takes 10 minutes.
>
> This is an OCR program and OCR takes a long time. There are
> opportunities to speed up testing on my end but no low hanging fruit
> without removing tests. I've done the obvious: use all cores, use
> caches and dummies where possible. Some OCR on the fly is essential
> because Tesseract is complex enough that output is not identical
> across platforms.
>
> Preserving the dynamically created tests/cache/ folder between test
> runs, if possible in Debian CI, would speed it up a lot.

Unfortunately not possible.

> I could mark a subset of essential tests for packagers so that Debian
> CI can specify it only wants those. There's a number of tests that are
> very unlikely to pass upstream testing (macOS and Ubuntu) then somehow
> fail downstream in Debian.

Just to be clear, this bug is about the tests run during the package
build, which is completely independent of Debian CI (in our terminology,
"autopkgtest" refers to Debian CI).

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: Re: Bug#888917: ocrmypdf fails to run it's testsuite

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +moreinfo
Bug #888917 [src:ocrmypdf] ocrmypdf fails to run it's testsuite
Added tag(s) moreinfo.

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

Bug#888917: ocrmypdf fails to run it's testsuite

[Sean Whitton]

control: tag -1 +moreinfo

Dear Matthias,

On Wed, Jan 31 2018, Matthias Klose wrote:

> The recent changelog reads:
>
>   * Disable test suite at package build time.
> It now takes a prohibitively long time to run, so we are relying on
> autopkgtest instead.
>
> Sorry, but this is one of the most lame excuses I have ever seen. Trying to 
> run
> it on my laptop in unstable needs 30 seconds.  However re-enabling it and
> running it reveals
>
>   === 122 failed, 24 passed, 4 skipped in 33.92 seconds 
>
> these results are after adding tesseract-ocr qpdf unpaper as build 
> dependencies.

Looking at the errors, I strongly suspect that this is because you are
running the test suite on a tmpfs -- we have seen these permission
errors before under those conditions.  Could you try running the test
suite on a totally ordinary file system, please?

I further suspect that the test suite took 30 seconds only because so
many tests failed early.  In recent upstream versions, the test suite
has never finished running on my laptop after leaving it for multiple
hours.  When you run the test suite on a totally ordinary file system,
please report how long it takes, and whether your laptop is very
new/high spec.

I note that Policy does not require that a package be buildable under a
tmpfs, and certainly does not require that its test suite run under a
tmpfs.

> doubting that the primary reason for this change was build time ...

Several things:

1) I ran the test suite using deb-o-matic[1] before uploading.  Needless
   to say, I would not have uploaded had there been failures.

2) I should have mentioned in the changelog that another reason for this
   change was to reduce the number of heavy build dependencies.

   A further reason is that it reduces the amount of fragile code in
   d/rules needed to get the test suite running -- upstream's test suite
   is designed to be run on the installed package.

3) I am of the view that very heavy test suites are better run under
   autopkgtest.  We will soon have testing migration gating on
   autopkgtest, and it is not clear to me that it makes sense for the
   process of stitching the .deb to abort when a single integration test
   fails.

   (Ideally tests would be separated into those that should abort the
   build and those that should not, but in the absence of this work
   being done, it is reasonable not to run any of them.)

4) Your implicit comment that I lied in the changelog and disabled the
   test suite because I knew it would fail is entirely uncalled for.
   Please do not treat fellow package maintainers like that.

[1]  http://debomatic-amd64.debian.net/

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#888484: [Pkg-clamav-devel] Bug#888484: Updates for stretch/jessie not in security repo

[Scott Kitterman]

On Wednesday, January 31, 2018 12:52:35 PM Klaus Keppler wrote:
> Hi,
> 
> is there a special reason why the updates are not published through the
> "security" repositories of Debian Stretch/Jessie?
> 
> - on Debian 7, the update is in "wheezy" (via security)
> - on Debian 8, the update is in "jessie-updates"
> - on Debian 9, the update is in "stretch-updates"
> 
> With regard of the severity of the bug, I can't understand this release
> strategy. Or am I just too impatient?
> 
> Many "sources.list" files do not contain the "-updates" repository, for
> example unmodified Xen instances created with "xen-create-image".
> 
> So I suggest to push this update also into debian-security.
> 
> Thanks for your efforts & best regards

The reason is that typically clamav updates include much more than just 
security fixes (as far as I can recall in roughly a decade of clamav 
maintenance this is the first time it's happened), so are not considered 
suitable for the security repository.

We believe that keeping clamav up to date so that, as a package that provides 
a security service, it is always kept as capable as possible is of overriding 
importance for clamav.

Wheezy is done through 'security' because it's no longer supported by the 
Debian project, but by the Long Term Support team.  The LTS team publishes ALL 
updates (security or not) via the security repository.  For Debian supported 
releases, clamav will always go via updates.

If you are just discovering this now, you've been missing out of clamav 
updates for a long time.  Debian started publishing Stable Update 
Announcements in March, 2011.  The very first clamav stable update 
announcement was published that same month[1].  These clamav updates virtually 
always include security relevant fixes.

Scott K


[1] https://lists.debian.org/debian-stable-announce/2011/03/msg3.html

Bug#888484: [Pkg-clamav-devel] Bug#888484: Updates for stretch/jessie not in security repo

[Scott Kitterman]

On Thursday, February 01, 2018 01:03:29 AM Matija Nalis wrote:
> nor does debian security tracker list the updates as available for
> jessie/stretch:
> https://security-tracker.debian.org/tracker/source-package/clamav
> 
> (security-tracked does say in hover text that jessie
> "gets updated via -updates", so it should pick that up)
> 
> it correctly reports wheezy, buster and sid as fixed.
> 
> for example, see also
> https://security-tracker.debian.org/tracker/CVE-2017-12376
> 
> this looks to me also like something that should be fixed (somewhere)?

By design, the security tracker doesn't consider things 'fixed' in stable via 
updates until after it's included in a Debian point release.  I agree it's not 
totally clear, but the way it's working is what the security team intends.

Scott K

Processed: Move to the package where it was fixed

[Debian Bug Tracking System]

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

> reassign 887482 dh-autoreconf
Bug #887482 {Done: Julian Andres Klode } [src:xorg-server] 
xorg-server: FTBFS: dh_autoreconf can only be run once
Bug reassigned from package 'src:xorg-server' to 'dh-autoreconf'.
No longer marked as found in versions xorg-server/2:1.19.5-1.
No longer marked as fixed in versions dh-autoreconf/16.
> fixed 887482 16
Bug #887482 {Done: Julian Andres Klode } [dh-autoreconf] 
xorg-server: FTBFS: dh_autoreconf can only be run once
Marked as fixed in versions dh-autoreconf/16.
> tags 887482 buster sid
Bug #887482 {Done: Julian Andres Klode } [dh-autoreconf] 
xorg-server: FTBFS: dh_autoreconf can only be run once
Added tag(s) buster and sid.
> affects 887482 src:xorg-server
Bug #887482 {Done: Julian Andres Klode } [dh-autoreconf] 
xorg-server: FTBFS: dh_autoreconf can only be run once
Added indication that 887482 affects src:xorg-server
> thanks
Stopping processing here.

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

Processed: block 886816 with 888717

[Debian Bug Tracking System]

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

> block 886816 with 888717
Bug #886816 {Done: Alexandre Viau } [golang-go.uber-zap-dev] 
golang-go.uber-zap-dev: needs Breaks+Replaces: zap
886816 was blocked by: 888717
886816 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #886816 to the same blocks 
previously set
> thanks
Stopping processing here.

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

Processed: block 886816 with 888717

[Debian Bug Tracking System]

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

> block 886816 with 888717
Bug #886816 {Done: Alexandre Viau } [golang-go.uber-zap-dev] 
golang-go.uber-zap-dev: needs Breaks+Replaces: zap
886816 was not blocked by any bugs.
886816 was not blocking any bugs.
Added blocking bug(s) of 886816: 888717
> thanks
Stopping processing here.

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 888753 buster sid
Bug #888753 [src:sortmail] sortmail: please switch to new gdbm, or prepare to 
use the compat package
Added tag(s) sid and buster.
> tags 888752 buster sid
Bug #888752 [src:ifmail] ifmail: please switch to new gdbm, or prepare to use 
the compat package
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#888994: libjavacc-maven-plugin-java: plugin fails at runtime after jtb 1.4.12-1 update

[tony mancill]

Package: libjavacc-maven-plugin-java
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Packages that build-dep on libjavacc-maven-plugin-java fail a build-time
with:

[INFO] --- javacc-maven-plugin:2.6:javacc (javacc) @ javaparser ---
[WARNING] The POM for edu.ucla.cs.compilers:jtb:jar:debian is missing, no 
dependency information available

This appears correlated with the upload of jtb 1.4.12-1 [1].

[1] https://tracker.debian.org/news/899962


signature.asc
Description: PGP signature

Bug#888484: Updates for stretch/jessie not in security repo

[Matija Nalis]

nor does debian security tracker list the updates as available for 
jessie/stretch:
https://security-tracker.debian.org/tracker/source-package/clamav

(security-tracked does say in hover text that jessie 
"gets updated via -updates", so it should pick that up)

it correctly reports wheezy, buster and sid as fixed.

for example, see also https://security-tracker.debian.org/tracker/CVE-2017-12376

this looks to me also like something that should be fixed (somewhere)?

Bug#888917: ocrmypdf fails to run it's testsuite

[James R Barlow]

Upstream here.

The reason the suite fails like that is that mandatory-for-testing
dependencies were also removed.

The test suite runs on Travis CI in 10-12 minutes. On Debian CI, 15
minutes. For comparison ffmpeg, another compute intensive CLI program,
takes 10 minutes.

This is an OCR program and OCR takes a long time. There are opportunities
to speed up testing on my end but no low hanging fruit without removing
tests. I've done the obvious: use all cores, use caches and dummies where
possible. Some OCR on the fly is essential because Tesseract is complex
enough that output is not identical across platforms.

Preserving the dynamically created tests/cache/ folder between test runs,
if possible in Debian CI, would speed it up a lot.

I could mark a subset of essential tests for packagers so that Debian CI
can specify it only wants those. There's a number of tests that are very
unlikely to pass upstream testing (macOS and Ubuntu) then somehow fail
downstream in Debian.

Processed: [PATCH] Patch for bug 876541

[Debian Bug Tracking System]

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

> found 876541 0.2.3h+dfsg-1
Bug #876541 [xul-ext-sieve] "SyntaxError: missing ] after element list" in 
SieveFilterEditor.js (fixed upstream 0.2.3k)
Marked as found in versions sieve-extension/0.2.3h+dfsg-1.
> tag 876541 patch
Bug #876541 [xul-ext-sieve] "SyntaxError: missing ] after element list" in 
SieveFilterEditor.js (fixed upstream 0.2.3k)
Added tag(s) patch.
> thanks.
Stopping processing here.

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

Bug#876541: [PATCH] Patch for bug 876541

[Thomas Kremer]

found 876541 0.2.3h+dfsg-1
tag 876541 patch

thanks.


And here is your patch.

Questions:
 - This exact version of xul-ext-sieve actually once worked for me. Has
there been a feature reduction in the underlying javascript engine?
 - Will this patch be implemented? In stable?
 - [some self-censored question about anonymous maintainer lists'
reaction patterns]


Yours
Thomas Kremer


-- 
OpenPGP Key ID: 0x6BFFE5CF3C7720398928CE741F2DAE97486A60BF

--- /usr/share/xul-ext/sieve/chrome/chromeFiles/content/editor/SieveFilterEditor.js.orig	2015-08-09 21:40:50.0 +0200
+++ /usr/share/xul-ext/sieve/chrome/chromeFiles/content/editor/SieveFilterEditor.js	2018-01-31 23:34:47.189097792 +0100
@@ -127,14 +127,9 @@
   
   var hash = ch.finish(false);  
   
-  // return the two-digit hexadecimal code for a byte  
-  function toHexString(charCode)  
-  {  
-return ("0" + charCode.toString(16)).slice(-2);  
-  }  
-  
   // convert the binary hash data to a hex string.  
-  return [toHexString(hash.charCodeAt(i)) for (i in hash)].join("");  
+  return Array.from(hash, 
+  function (cur, idx) { return ("0" + hash.charCodeAt(idx).toString(16)).slice(-2); } ).join(""); 
 }
 
 SieveFilterEditor.prototype.onGetScriptResponse

Bug#886816: marked as done (golang-go.uber-zap-dev: needs Breaks+Replaces: zap)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 17:10:36 -0500
with message-id <1c0a8d53-a481-220d-244c-f500270fb...@debian.org>
and subject line Done in 888717
has caused the Debian Bug report #886816,
regarding golang-go.uber-zap-dev: needs Breaks+Replaces: zap
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.)


-- 
886816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-go.uber-zap-dev,zap
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.7.1+git20171031.f85c78b-3
Control: found -1 1.5.0+git20170802.3.e68420e-2

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files ...

Both packages ship /usr/share/gocode/src/go.uber.org/zap/* and the
synopsis matches, so this seems to be independent packaging of the
same software. Please decide which one you want to keep.
There are no rdepends in both cases.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
This was handled in #888717.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: gdbm: bumping severity, transition has started

[Debian Bug Tracking System]

Processing control commands:

> severity 888752 serious
Bug #888752 [src:ifmail] ifmail: please switch to new gdbm, or prepare to use 
the compat package
Severity set to 'serious' from 'important'
> severity 888753 serious
Bug #888753 [src:sortmail] sortmail: please switch to new gdbm, or prepare to 
use the compat package
Severity set to 'serious' from 'important'
> severity 888754 serious
Bug #888754 [src:pike7.8] pike7.8: build fix for new gdbm (>=1.13)
Severity set to 'serious' from 'important'

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

Bug#885670: marked as done (kino: Don't Build-Depend on libgnome)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 22:04:45 +
with message-id 
and subject line Bug#885670: fixed in kino 1.3.4-2.4
has caused the Debian Bug report #885670,
regarding kino: Don't Build-Depend on libgnome
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.)


-- 
885670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kino
Version: 1.3.4-2.3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome libgnomeui
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

It looks like kino has a few unnecessary Build-Depends. You can help by
  dropping the Build-Depends on libgnome2-dev and libgnomeui-dev. (I'm
not actually attaching a patch because this seems trivial enough to not
need a patch.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: kino
Source-Version: 1.3.4-2.4

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated kino package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Jan 2018 22:58:22 +0200
Source: kino
Binary: kino
Architecture: source
Version: 1.3.4-2.4
Distribution: unstable
Urgency: low
Maintainer: Paul Brossier 
Changed-By: Adrian Bunk 
Description:
 kino   - Non-linear editor for Digital Video data
Closes: 885670
Changes:
 kino (1.3.4-2.4) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Remove the unused libgnome2-dev and libgnomeui-dev
 build dependencies. (Closes: #885670)
Checksums-Sha1:
 39338c5071d9312a450cd15aa54f560b29b8c62b 2347 kino_1.3.4-2.4.dsc
 a6cc917e02abd39c2db5acb966ef7fc4bcba2c0f 38989 kino_1.3.4-2.4.diff.gz
Checksums-Sha256:
 5b5223fdc9bd2442ef0c56d283d1361ba697ac2b73173c06086758126af1f7f6 2347 
kino_1.3.4-2.4.dsc
 147f891a0a3da3b7b2175e1f334721183d0707bf8f38f5f80c088e7b2c56bcef 38989 
kino_1.3.4-2.4.diff.gz
Files:
 e8a4b9ee2952620e7caacdd597f35dc1 2347 graphics extra kino_1.3.4-2.4.dsc
 9d0cf6d93199825fda331f70d2c1d268 38989 graphics extra kino_1.3.4-2.4.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlprmFUACgkQiNJCh6LY
mLGjtQ/+MoLIJwB13Uv+X49/8w0ldgv3z+0TJKyF6ePQNfA1nG2m4Ys6lkVEEMnw
s3QekIGgcI9WFIzmjteJQE1aP1/5YJFzQFbUl4PyryJzJHckwE4zhubzIcLDK5PX
8E14Tzt6iMd0LnaaKN2iagsWxkDu2w6qi0Ud8SgF73OLa5gk6pnW+pnJ1z6v1Rjs
z2rnxvh0/eSMulOWSeJINqMBD+Zua0uahXUYzJDXPdAAplhujz6BAVPwwRe8ZbHI
HnSMjF1bArbBFfyKE9ALBYg6wVA1qCr4IKoPrs20vtq0kdYN1kdgEdZn9DmKJQ4f
ykvXkcL+1jgZAvvq/KBjhiBvJIBMklD2vGqci0ERIRfYyKt0Qyb4+aZAkblS2HUg
dJQGa0mqVNQJdG+Fi7j+HYTpn3ZnW/BU8V5a+Lbwnm9Y9+dcPqa7n7D+ItVkcqRh
o6zjtxh5BUiXmNDqusgEVnPR4zOZlKC9ij2p7SU4GCMH2LPO/sMeQS9c0HnYyNIC
aInI1WirJH0qXAPKLl3O+O1TPci/fedfsJBKz4O6ULMryMx5GTuqx3J2m8jXX4M/
AcsIYp0mMv1K2l2hx1sV0VR+PvHKr1mU2Wf/xz7tClNW6LnOTBz55UCMeQmqybxU
pgYq/k3/6QVkuzu2Tb6mwX4CA2tjSAZS6jtTakX3Xiuus4mzFsY=
=6cah
-END PGP SIGNATURE End Message ---

Bug#888251: marked as done (does not allow certain characters in filenames)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 22:04:37 +
with message-id 
and subject line Bug#888251: fixed in debhelper 11.1.4
has caused the Debian Bug report #888251,
regarding does not allow certain characters in filenames
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.)


-- 
888251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.3
Severity: normal
File: /usr/bin/dh_install

Hi,

I'm trying to package something with funny characters in the filename:

#!/usr/bin/dh-exec
plugins_tools/xpi/signed-build/belgium_eid-1.0.27.xpi => 
usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/belgium...@eid.belgium.be.xpi

This causes dh_exec to emit something like
"debian/tmp/dh_exec.XX/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/belgium...@eid.belgium.be.xpi",
but dh_install doesn't find the file. In fact, the error message states
"can't find the file ", but if one then copy/pastes the file into
a command shell from the toplevel pakage directory, and puts "ls" in
front of it, it works just fine.

I wish I could drop the curly braces and @ in the filename, but these
are required by Firefox, so that's just not an option.

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20171216.1
ii  binutils 2.29.90.20180122-1
ii  dh-autoreconf15
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.5
ii  dpkg-dev 1.19.0.5
ii  file 1:5.32-1
ii  libdpkg-perl 1.19.0.5
ii  man-db   2.7.6.1-4
ii  perl 5.26.1-4
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201701
pn  dwz  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.1.4

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 31 Jan 2018 21:36:13 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.1.4
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 886108 888251 888294 888974
Changes:
 debhelper (11.1.4) unstable; urgency=medium
 .
   * qmake.pm/qmake4.pm: Avoid global state in the build systems.
   * dh_makeshlibs: Fix --no-act, which could still cause writes
 to the shlibs file.  Thanks to Sven Joachim for reporting it.
 (Closes: #888974)
   * dh_installdocs: Discard auto-detected main doc package when
 passed -A/--all as it causes file-conflicts.
 (Closes: #886108, #888294)
   * Dh_Lib: Fix regression where "foo{bar}" would not be matched
 when the pattern was handled as a glob.  The bug was
 introduced in debhelper/10.6.  Thanks to Wouter Verhelst for
 finding the bug.  (Closes: #888251)
   * d/control: Update the Vcs-* fields to point to
 salsa.debian.org as a part of the migration from alioth.
   * d/control: Update 

Bug#888974: marked as done (debhelper: dh_makeshlibs --no-act isn't and causes FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 22:04:37 +
with message-id 
and subject line Bug#888974: fixed in debhelper 11.1.4
has caused the Debian Bug report #888974,
regarding debhelper: dh_makeshlibs --no-act isn't and causes FTBFS
to be marked as done.

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

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


-- 
888974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.2
Severity: serious
Control: affects -1 src:ck

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

...
dh clean
   dh_clean
 debian/rules build
make: Nothing to be done for 'build'.
 fakeroot debian/rules binary
dh binary
   debian/rules build
make[1]: Entering directory '/build/1st/ck-0.6.0'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/build/1st/ck-0.6.0'
   dh_testroot
   dh_prep
   dh_install
dh_install: Cannot find (any matches for) "usr/lib/*/lib*.so.*" (tried in ., 
debian/tmp)

dh_install: libck0 missing files: usr/lib/*/lib*.so.*
dh_install: Cannot find (any matches for) "usr/include" (tried in ., debian/tmp)

dh_install: libck-dev missing files: usr/include
dh_install: Cannot find (any matches for) "usr/lib/*/lib*.so" (tried in ., 
debian/tmp)

dh_install: libck-dev missing files: usr/lib/*/lib*.so
dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig" (tried in ., 
debian/tmp)

dh_install: libck-dev missing files: usr/lib/*/pkgconfig
dh_install: Cannot find (any matches for) "usr/share/man" (tried in ., 
debian/tmp)

dh_install: libck-dev missing files: usr/share/man
dh_install: missing files, aborting
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 25


Works after downgrading to debhelper 11
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.1.4

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 31 Jan 2018 21:36:13 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.1.4
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 886108 888251 888294 888974
Changes:
 debhelper (11.1.4) unstable; urgency=medium
 .
   * qmake.pm/qmake4.pm: Avoid global state in the build systems.
   * dh_makeshlibs: Fix --no-act, which could still cause writes
 to the shlibs file.  Thanks to Sven Joachim for reporting it.
 (Closes: #888974)
   * dh_installdocs: Discard auto-detected main doc package when
 passed -A/--all as it causes file-conflicts.
 (Closes: #886108, #888294)
   * Dh_Lib: Fix regression where "foo{bar}" would not be matched
 when the pattern was handled as a glob.  The bug was
 introduced in debhelper/10.6.  Thanks to Wouter Verhelst for
 finding the bug.  (Closes: #888251)
   * d/control: Update the Vcs-* fields to point to
 salsa.debian.org as a part of the migration from alioth.
   * d/control: Update maintainer address debhelper@packages.d.o
 as a part of the migration from alioth.  Any subscription
 to debhelper-de...@lists.alioth.debian.org should be
 replaced by a subscription in tracker.debian.org or
 salsa.debian.org.
   * d/control: Remove Bernhard R. Link from uploaders as he does
 not appear to be active in debhelper at the moment.  Thanks
 to Bernhard for his past contributions.
   * d/control: Bump (Build-)Dependency on dpkg to ensure that
 dpkg provides DEB_RULES_REQUIRES_ROOT and DEB_GAIN_ROOT_CMD
 as a part of its Rules-Requires-Root support.
   * Dh_Lib.pm: Rely on DEB_RULRES_REQUIRES_ROOT instead of the
 field to 

Bug#847135: Not fixed by 7.08

[Mike Miller]

On Wed, Dec 13, 2017 at 14:06:03 +0100, Adam Cecile wrote:
> Hello,

Hi,

> 7.08 still have the issue. I cannot push a docker image through openconnect.
> It stalls around 50Mbytes.

Upstream has kindly asked for more information on your issue, can you
please provide a response to
http://lists.infradead.org/pipermail/openconnect-devel/2017-December/004618.html
?

-- 
mike


signature.asc
Description: PGP signature

Bug#887323: dewalls i386 test failure

[Philip Schuchardt]

Nice! I wonder if i386 don’t support exceptions properly or something...
On Tue, Jan 30, 2018 at 8:07 AM Wookey  wrote:

> On 2018-01-30 06:48 +, Philip Schuchardt wrote:
> > I know I’ve been dragging my feet on this. Let’s see if I can figure
> this out,
> > this week.
>
> I fished out an old netbook which is actually i386. And installed an
> unstable chroot on it (very slowly!) last night. Hopefully this will
> enable some bottom-getting-to.
>
> I should probbaly just have used a debian porter-box, but that machine
> needed updating anyway.
>
> Wookey
> --
> Principal hats:  Linaro, Debian, Wookware, ARM
> http://wookware.org/
>
-- 
Phi|ip

Bug#884173: SIGSEGV since 63.0.3239.84-1 w/ non-built-in extensions

[Nathan Schulte]

I found that, with all versions since (and including) chromium 
63.0.3239.84-1, Chromium would crash (SIGSEGV) shortly after startup or 
immediately at startup.


Initially, I found that disabling the uMatrix extension I have installed 
(from the Chrome Web Store) would avoid the crashes.  That wasn't a 
suitable work-around, so I've been held at version 63.0.3239.40-1.


(https://github.com/gorhill/uMatrix -- 
https://chrome.google.com/webstore/detail/umatrix/ogfcmafjalglgifnmanfmnieipoejdcf)


I found these information interesting, relating to this bug:

1) a bug report for ArchLinux re: Media Router Component, with a comment 
noting that the "load Media Router Component extension" flag may cause 
Chromium to crash:



https://bugs.archlinux.org/task/51832#comment154874



2) Debian ships Chromium with a "default-flag" to disable the media router:

$ grep -n media /etc/chromium.d/default-flags 
15:# Disable the builtin media router (bug #833477)

16:export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --media-router=0"


3) a bug report for Debian, much like the ArchLinux one above:


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


Thanks,

--
Nate

Bug#888403: Fwd: [PATCH 1/1] efi_loader: fix building crt0 on arm

[Vagrant Cascadian]

Thanks for the patch!

It definitely seems to resolve the issue with v2018.03-rc1, but
unfortunately I haven't had success building it with v2018.01 yet:

  /<>/u-boot-2018.01+dfsg1/lib/efi_loader/efi_image_loader.c:
  In function ‘efi_load_pe’:

  /<>/u-boot-2018.01+dfsg1/lib/efi_loader/efi_image_loader.c:208:7:
  error: ‘IMAGE_SUBSYSTEM_SAL_RUNTIME_DRIVER’ undeclared (first use in
  this function); did you mean ‘IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER’?


I get the impression that EFI related support in u-boot has been very
active lately, which this code touches, which makes it harder to apply
patches from upstream directly.


live well,
  vagrant

On 2018-01-31, Heinrich Schuchardt wrote:
> Before the patch an undefined constant EFI_SUBSYSTEM was used in the
> crt0 code. The current version of binutils does not swallow the error.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888403
>
> The necessary constant IMAGE_SUBSYSTEM_EFI_APPLICATION is already
> defined in pe.h. So let's factor out asm-generic/pe.h for the
> image subsystem constants and use it in our assembler code.
>
> IMAGE_SUBSYSTEM_SAL_RUNTIME_DRIVER does not exist in the specification
> let's use IMAGE_SUBSYSTEM_EFI_ROM instead.
>
> The include pe.h is only used in code maintained by Alex so let him be the
> maintainer here too.
>
> Reported-by: Andre Przywara 
> Cc: Alexander Graf 
> Signed-off-by: Heinrich Schuchardt 
> ---
>  MAINTAINERS   |  2 ++
>  arch/arm/lib/crt0_aarch64_efi.S   |  4 +++-
>  arch/arm/lib/crt0_arm_efi.S   |  4 +++-
>  include/asm-generic/pe.h  | 21 +
>  include/pe.h  |  8 ++--
>  lib/efi_loader/efi_image_loader.c |  2 +-
>  6 files changed, 32 insertions(+), 9 deletions(-)
>  create mode 100644 include/asm-generic/pe.h


signature.asc
Description: PGP signature

Bug#541538: pulseaudio: disable flat volumes

[Patrick Dunford]

I have the view the same, it should be so easy to resolve this problem 
in the config file, it must be so simple to implement


In addition to the problems you mention, developers of third party 
applications have to publish this fix and respond to queries of why 
altering the volume level in their applications also alters the system 
volume level.


For example, using Kodi, it would set the volume level every time a new 
track was played, resulting in the user having to keep readjusting the 
system volume level every time. My keyboard has these up/down volume 
control buttons I use to set the system volume. Every time a track 
started to play I would have to keep turning the system volume level 
down because the software had raised it. I should be able to set a 
maximum volume level for the system and not have it altered by applications.


So the question is how easy is it to change this default value and what 
is stopping it from being implemented.



On 01/02/18 01:01, Roland Hieber wrote:

I came here because I was just playing [1] on headphones, and Firefox
seemed to think that it would be a good idea to set the master volume to
100%. My ears are still ringing. At least now I know what to do.

[1]: https://en.wikipedia.org/wiki/File:AFSK_1200_baud.ogg

The fix of changing "flat-volumes = yes" to "flat-volumes = no" in
/etc/pulse/daemon.conf seems to be fairly easy to implement, considering
the fact that this bug is blocking a great number of other bugs, and no
one here apparently has to say any word against it in the comments. Is
there something else blocking it?

  - Roland

Bug#887744: redeclipse FTBFS with glibc 2.26

[Martin Erik Werner]

On Tue, 2018-01-23 at 13:46 +0200, Juhani Numminen wrote:
> On Fri, 19 Jan 2018 17:58:06 +0200 Adrian Bunk 
> wrote:
> > Source: redeclipse
> > ...
> > In file included from /usr/include/math.h:724:0,
> >  from /usr/include/c++/7/cmath:45,
> >  from /usr/include/c++/7/math.h:36,
> >  from shared/cube.h:13,
> >  from shared/crypto.cpp:1:
> > /usr/include/x86_64-linux-gnu/bits/math-finite.h: In function
> > 'double tgamma(double)':
> > /usr/include/x86_64-linux-gnu/bits/math-finite.h:203:21: error:
> > 'gamma_r_finite' was not declared in this scope
> >    _Mdouble_ __res = __REDIRTO (gamma, _r, _MSUF_) (__d,
> > &__local_signgam);
> >  ^
> > /usr/include/x86_64-linux-gnu/bits/math-finite.h:203:21: note:
> > suggested alternative: '__gamma_r_finite'
> 
> The commit "remove gamma name hack" might be related, apparently
> there was some
> preprocessor hackery going on.
> https://github.com/red-eclipse/base/commit/b16b4963c1ad81bb9ef784bc49
> 13a4c8ab5f1bb4

Yep, applying this commit solves the issue.

Previously 'gamma' from math.h was masked in order to make it available
 to be defined by cubescript, and this masking was dependent on
implementation-specifics which had changed.

With this fix cubescript uses a different associated global name
'reqgamma' and thus does not need the masking.

-- 
Martin Erik Werner 

Bug#853008: [debian-mysql] Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

[Lars Tangvald]

On 01/31/2018 02:19 PM, Olaf van der Spek wrote:

Hi,


Anyone else have any good ideas on how to handle this?

I do. The solution is quite simple: do not, ever, remove user data / databases.

It makes everything so much simpler, both on the user side and on the
dev side. No weird questions when installing, no databases gone by
accident..

The problem is that MariaDB and MySQL use the same data location, so 
you'd instead get weird errors when trying to move to a variant/version 
that can't handle the old data (MySQL does not support migration from 
MariaDB, and MariaDB supports specific versions of MySQL). It's 
reasonable for a user to expect that purging one package would let them 
install the other without issues.


There is work going on to deal with this, which should both let users go 
back and forth between incompatible versions and make sure a package can 
only delete its own data.


--
Lars

Processed: limit source to debhelper, tagging 888974

[Debian Bug Tracking System]

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

> limit source debhelper
Limiting to bugs with field 'source' containing at least one of 'debhelper'
Limit currently set to 'source':'debhelper'

> tags 888974 + pending
Bug #888974 [debhelper] debhelper: dh_makeshlibs --no-act isn't and causes FTBFS
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: [debhelper-devel] Bug#887688: debhelper: empty build of src:ck

[Debian Bug Tracking System]

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

> clone 887688 -1
Bug #887688 [debhelper] debhelper: empty build of src:ck
Bug 887688 cloned as bug 888974
> retitle -1 debhelper: dh_makeshlibs --no-act isn't and causes FTBFS
Bug #888974 [debhelper] debhelper: empty build of src:ck
Changed Bug title to 'debhelper: dh_makeshlibs --no-act isn't and causes FTBFS' 
from 'debhelper: empty build of src:ck'.
> tags 887688 pending
Bug #887688 [debhelper] debhelper: empty build of src:ck
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#887688: [debhelper-devel] Bug#887688: debhelper: empty build of src:ck

[Niels Thykier]

clone 887688 -1
retitle -1 debhelper: dh_makeshlibs --no-act isn't and causes FTBFS
tags 887688 pending
thanks

Hi,

Assuming I have not overlooked something, then I believe this bug is now
resolved in debhelper and will close it in a few days.  This is because:

 * I have filed bugs for all known packages that currently FTBFS due to
   empty or incomplete targets (usually caused by .PHONY).  Most of
   these have a patch attached.

 * The autoreconf related issue was solved in dh-autoreconf/16, which
   solved the problems in some of the originally listed packages.
   (See #887482)

 * There was a regression in the --no-act that caused a single FTBFS.
   This has a patch in debhelper master that has yet to be uploaded
   (I just cloned this bug for that purpose).


Overview of the packages mentioned in this bug report
=

Packages that has an open RC bug related to this issue:

 * apr: #888593 (patch)
 * ck: #888591 (patch)
 * cpputest: #888598 (patch)
 * debian-handbook: #888578 (patch)
 * iaxmodem: #888601 (patch)
 * moarvm: #888582 (patch)
 * jscommunicator: #888579 (patch)
 * libtemplate-perl: #888663 (patch)
 * monotone: #888612 (patch)

Packages that were affected and have now been fixed:

 * openal-soft: Already fixed by smcv
 * biojava-live: Already fixed by the maintainer
 * cysignals: Already fixed by the maintainer

Packages with unrelated issues or that were fixed by changes in other
packages:

 * jansson: Fixed in dh-autoreconf/16
 * scidavis: Will move to the cloned bug

Thanks,
~Niels

Bug#886209: marked as done (FTBFS: configure: error: please install and enable pecl/raphf)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 19:54:30 +0100
with message-id <20180131185430.s67uvylaoyhnv...@angband.pl>
and subject line Re: FTBFS: configure: error: please install and enable 
pecl/raphf
has caused the Debian Bug report #886209,
regarding FTBFS: configure: error: please install and enable pecl/raphf
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.)


-- 
886209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-pecl-http
Version: 3.1.0+2.6.0-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build on current unstable:

checking whether ext/raphf is enabled... no
configure: error: please install and enable pecl/raphf
cd build-7.1 && tail -v -n \+0 config.log
==> config.log <==

Tried on armhf amd64.  Log attached.


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

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


php-pecl-http_armhf.build
Description: inode/symlink
--- End Message ---
--- Begin Message ---
On Wed, Jan 31, 2018 at 05:48:29PM +0200, Juhani Numminen wrote:
> On Wed, 03 Jan 2018 04:05:29 +0100 Adam Borowski  wrote:
> > 
> > checking whether ext/raphf is enabled... no
> > configure: error: please install and enable pecl/raphf
> > 
> > Tried on armhf amd64.  Log attached.
> 
> An observation: php7-related binNMUs from today seem to be building 
> successfully.
> 
> https://buildd.debian.org/status/package.php?p=php-pecl-http

Aye, so it does for me.


-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?--- End Message ---

Bug#888403: Fwd: [PATCH 1/1] efi_loader: fix building crt0 on arm

[Heinrich Schuchardt]

 Forwarded Message 
Subject: [PATCH 1/1] efi_loader: fix building crt0 on arm
Date: Wed, 31 Jan 2018 18:45:35 +
From: Heinrich Schuchardt 
To: Alexander Graf 

Before the patch an undefined constant EFI_SUBSYSTEM was used in the
crt0 code. The current version of binutils does not swallow the error.

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

The necessary constant IMAGE_SUBSYSTEM_EFI_APPLICATION is already
defined in pe.h. So let's factor out asm-generic/pe.h for the
image subsystem constants and use it in our assembler code.

IMAGE_SUBSYSTEM_SAL_RUNTIME_DRIVER does not exist in the specification
let's use IMAGE_SUBSYSTEM_EFI_ROM instead.

The include pe.h is only used in code maintained by Alex so let him be the
maintainer here too.

Reported-by: Andre Przywara 
Cc: Alexander Graf 
Signed-off-by: Heinrich Schuchardt 
---
 MAINTAINERS   |  2 ++
 arch/arm/lib/crt0_aarch64_efi.S   |  4 +++-
 arch/arm/lib/crt0_arm_efi.S   |  4 +++-
 include/asm-generic/pe.h  | 21 +
 include/pe.h  |  8 ++--
 lib/efi_loader/efi_image_loader.c |  2 +-
 6 files changed, 32 insertions(+), 9 deletions(-)
 create mode 100644 include/asm-generic/pe.h

diff --git a/MAINTAINERS b/MAINTAINERS
index 0aecc18a6c..879b41c97e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -291,6 +291,8 @@ S:  Maintained
 T: git git://github.com/agraf/u-boot.git
 F: doc/README.iscsi
 F: include/efi*
+F: include/pe.h
+F: include/asm-generic/pe.h
 F: lib/efi*/
 F: test/py/tests/test_efi*
 F: cmd/bootefi.c
diff --git a/arch/arm/lib/crt0_aarch64_efi.S
b/arch/arm/lib/crt0_aarch64_efi.S
index 52056469be..9b0e894f8a 100644
--- a/arch/arm/lib/crt0_aarch64_efi.S
+++ b/arch/arm/lib/crt0_aarch64_efi.S
@@ -8,6 +8,8 @@
  * This file is taken and modified from the gnu-efi project.
  */
 +#include 
+
.section.text.head
/*
@@ -62,7 +64,7 @@ extra_header_fields:
 */
.long   _start - ImageBase  /* SizeOfHeaders */
.long   0   /* CheckSum */
-   .short  EFI_SUBSYSTEM   /* Subsystem */
+   .short  IMAGE_SUBSYSTEM_EFI_APPLICATION /* Subsystem */
.short  0   /* DllCharacteristics */
.quad   0   /* SizeOfStackReserve */
.quad   0   /* SizeOfStackCommit */
diff --git a/arch/arm/lib/crt0_arm_efi.S b/arch/arm/lib/crt0_arm_efi.S
index 967c885982..af55bba4ba 100644
--- a/arch/arm/lib/crt0_arm_efi.S
+++ b/arch/arm/lib/crt0_arm_efi.S
@@ -8,6 +8,8 @@
  * This file is taken and modified from the gnu-efi project.
  */
 +#include 
+
.section.text.head
/*
@@ -64,7 +66,7 @@ extra_header_fields:
 */
.long   _start - image_base /* SizeOfHeaders */
.long   0   /* CheckSum */
-   .short  EFI_SUBSYSTEM   /* Subsystem */
+   .short  IMAGE_SUBSYSTEM_EFI_APPLICATION /* Subsystem */
.short  0   /* DllCharacteristics */
.long   0   /* SizeOfStackReserve */
.long   0   /* SizeOfStackCommit */
diff --git a/include/asm-generic/pe.h b/include/asm-generic/pe.h
new file mode 100644
index 00..d1683f238a
--- /dev/null
+++ b/include/asm-generic/pe.h
@@ -0,0 +1,21 @@
+/*
+ *  Portable Executable and Common Object Constants
+ *
+ *  Copyright (c) 2018 Heinrich Schuchardt
+ *
+ *  based on the "Microsoft Portable Executable and Common Object File
Format
+ *  Specification", revision 11, 2017-01-23
+ *
+ *  SPDX-License-Identifier: GPL-2.0+
+ */
+
+#ifndef _ASM_PE_H
+#define _ASM_PE_H
+
+/* Subsystem type */
+#define IMAGE_SUBSYSTEM_EFI_APPLICATION10
+#define IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER11
+#define IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER 12
+#define IMAGE_SUBSYSTEM_EFI_ROM13
+
+#endif /* _ASM_PE_H */
diff --git a/include/pe.h b/include/pe.h
index 4ef3e92efa..c3a19cef76 100644
--- a/include/pe.h
+++ b/include/pe.h
@@ -11,6 +11,8 @@
 #ifndef _PE_H
 #define _PE_H
 +#include 
+
 typedef struct _IMAGE_DOS_HEADER {
uint16_t e_magic;   /* 00: MZ Header signature */
uint16_t e_cblp;/* 02: Bytes on last page of file */
@@ -62,12 +64,6 @@ typedef struct _IMAGE_DATA_DIRECTORY {
  #define IMAGE_NUMBEROF_DIRECTORY_ENTRIES 16
 -/* PE32+ Subsystem type for EFI images */
-#define IMAGE_SUBSYSTEM_EFI_APPLICATION 10
-#define IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER 11
-#define IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER  12
-#define IMAGE_SUBSYSTEM_SAL_RUNTIME_DRIVER  13
-
 typedef struct _IMAGE_OPTIONAL_HEADER64 {
uint16_t Magic; /* 0x20b */
uint8_t  

Bug#888971: /usr/bin/linux.uml: random segfault in uml mm

[Ritesh Raj Sarraf]

Package: user-mode-linux
Version: 4.14-1um-2
Severity: grave
File: /usr/bin/linux.uml
Tags: upstream
Justification: renders package unusable


Random segfault is seen with latest uml. Needs investigation. Let's not
let this propagate to testing.


[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
 Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
Option “-t” is deprecated and might be removed in a later version of 
gnome-terminal.

random: crng init done
io_thread - read failed, fd = 5, err = 4,reminder = 0

Modules linked in:

Modules linked in:
Pid: -1664957768, comm:  Not tainted 4.14.13
RIP: 0033:[<603e5e5e>]
RSP: a0cc4230  EFLAGS: 00010206
RAX: 60bb6030 RBX: 9d583000 RCX: 0075
RDX: 04dd RSI: a0cc4000 RDI: 609ca277
RBP: 6041735e R08: 60a74906 R09: 609cf8ec
R10: 000b R11: 0246 R12: 
R13:  R14:  R15: a0cc4530
Kernel panic - not syncing: Segfault with no mm
/home/rrs/bin/uml-debian: line 5: 26639 Killed  linux 
ubd0=~/rrs-home/NoTrack/uml.img eth0=daemon mem=1024M rw
23:16 ♒♒♒☹  => 137  



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

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

Versions of packages user-mode-linux depends on:
ii  libc6  2.26-4

Versions of packages user-mode-linux recommends:
ii  uml-utilities  20070815.1-2+b2

Versions of packages user-mode-linux suggests:
ii  gnome-terminal [x-terminal-emulator]  3.26.2-3
pn  rootstrap 
pn  slirp 
ii  tilix [x-terminal-emulator]   1.7.1-2
ii  user-mode-linux-doc   20060501-2
pn  vde2  
ii  xterm [x-terminal-emulator]   331-1

-- no debconf information

Bug#885556: marked as done (multipath-udeb: depends on a non-udeb package: liburcu6)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 22:24:38 +0530
with message-id <1517417678.25006.10.ca...@debian.org>
and subject line Re: Bug#885556: multipath-udeb: depends on a non-udeb package: 
liburcu6
has caused the Debian Bug report #885556,
regarding multipath-udeb: depends on a non-udeb package: liburcu6
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.)


-- 
885556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: multipath-udeb
Version: 0.7.4-2
Severity: serious

[Please keep debian-boot@ in copy of your replies.]

Hi,

Your udeb package depends on a non-udeb package (liburcu6), making it
uninstallable on all architectures.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
On Mon, 2018-01-22 at 17:52 +0100, Cyril Brulebois wrote:
> Hi Ritesh,
> 
> Ritesh Raj Sarraf  (2018-01-19):
> > I'll only be able to be at my computer next week. So you may go
> ahead
> > with the binnmu.
> 
> Thanks for your answer, binNMUs are on the way.

Thank you Cyril. I'm marking this bug as done now.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Bug#887069: Fix

[Vincenzo Gervasi]

For those stuck with a non-working npm, as an emergency fix you can change

/usr/lib/nodejs/node-uuid/index.js ->
../../../share/javascript/node-uuid/node-uuid.js

to

/usr/lib/nodejs/node-uuid/index.js ->
../../../share/javascript/node-uuid/uuid.js

(of course, once the package is updated things should go smoothly on their
own).

-V

Bug#888960: python-sugar-toolkit: Depends on unmaintained python-gconf

[Jeremy Bicha]

Package: python-sugar-toolkit
Version: 0.112-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gnome-python-desktop
Tags: sid buster

The source package gnome-python-desktop is unmaintained upstream. It
has not had a release since GNOME 3 was released in 2011. Therefore,
the Debian GNOME team has removed it from Debian Testing.

Please remove python-sugar-toolkit's dependency on python-gconf (one of
gnome-python-desktop's binary packages).

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

The replacement for gconf is gsettings which is provided in Debian by
the glib2.0 and gobject-introspection source packages. [3]

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject
[3] https://developer.gnome.org/gio/stable/ch34.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#886209: FTBFS: configure: error: please install and enable pecl/raphf

[Juhani Numminen]

On Wed, 03 Jan 2018 04:05:29 +0100 Adam Borowski  wrote:
> Source: php-pecl-http
> Version: 3.1.0+2.6.0-4
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi!
> I'm afraid your package fails to build on current unstable:
> 
> checking whether ext/raphf is enabled... no
> configure: error: please install and enable pecl/raphf
> cd build-7.1 && tail -v -n \+0 config.log
> ==> config.log <==
> 
> Tried on armhf amd64.  Log attached.

An observation: php7-related binNMUs from today seem to be building 
successfully.

https://buildd.debian.org/status/package.php?p=php-pecl-http


Cheers,
Juhani

Bug#888957: linuxbrew-wrapper: Linuxbrew formulas may build or install non-free software

[John Scott]

Package: linuxbrew-wrapper
Version: 20170516-2
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Though the linuxbrew-wrapper package is free just as Linuxbrew is, Linuxbrew 
does not commit to only free software. Linuxbrew's OpenCV formula builds with 
-DOPENCV_ENABLE_NONFREE=ON, and FFmpeg builds with --enable-nonfree. Though a 
comment in ffmpeg.rb notes that the flag produces unredistributable binaries, 
no notice is given to the user.

Users that commit to only using free software may install this package and 
believe that it is free because it is in main. Though the package is free, and 
Linuxbrew is free, the purpose of Linuxbrew and this wrapper package is to 
install software from outside of the Debian repository (some of which is 
non-free).

I believe that this violates Debian Policy that packages in main "must not 
require or recommend a package outside of main for compilation or execution."

Because this package is a wrapper that will "invoke upstream install script if 
found no linuxbrew instance" upon installation, I believe package is not suited 
for main and is probably better suited for contrib. The Debian Policy Manual 
says that packages that would be included in contrib include "wrapper packages 
or other sorts of free accessories for non-free programs." Linuxbrew is a 
wrapper for installing (with or without building from source) programs that, 
though many of them are free, some are not.


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

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

Versions of packages linuxbrew-wrapper depends on:
ii  build-essential12.4
ii  curl   7.58.0-2
ii  git1:2.15.1-3
ii  python-setuptools  38.2.4-2
ii  ruby   1:2.3.3

linuxbrew-wrapper recommends no packages.

linuxbrew-wrapper suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAlpx4wESHGpzY290dEBw
b3N0ZW8ubmV0AAoJEH1hRKYneTBy+e0H/iaJPxn/cQZVjjthqo674US+CXSTfw/+
shS/OmKzvUKfkFF0g0sKyhHmZTPTJtu6fAjYtSjMVLBwJud/nwhv5j5RJ/C/vZKl
zV7JdkL/swOCP/vU5zDWcHpemhyi+JRpujeAIfeghBrASSSj3O1Y8a9N+gsqovCK
HE0/qj63Yg1Qk3o5jlcBmf3MrVAjSCTUYofvpnShYwhqpUGAW1VTCAh/CRrvbOpZ
ssjJsDrTJCqExPLTOINx9tTNk+CCNXQv1xGmmzi9TDB+SUJgkc9IeF4m/IEKzkqE
AkQFIes3WCFOm81cgKd5tWHpbUtXL6YCf/X1tzmJqUWYCGChtXaS7Rs=
=QV9z
-END PGP SIGNATURE-

Bug#888919: marked as done (healpix-cxx FTBFS on armel: hpxtest runs into 150m timeout)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 15:06:05 +
with message-id 
and subject line Bug#888919: fixed in healpix-cxx 3.30.0-8
has caused the Debian Bug report #888919,
regarding healpix-cxx FTBFS on armel: hpxtest runs into 150m timeout
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.)


-- 
888919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpix-cxx
Version: 3.30.0-7
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=healpix-cxx=armel=3.30.0-7=1516966560=0

...
make  check-TESTS
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
E: Build killed with signal TERM after 150 minutes of inactivity


This is caused by:

healpix-cxx (3.30.0-7) unstable; urgency=medium

  * Use Automake parallel test harness, but print test log after
test summary
...


The tests do finish, but on the non-FPU armel port hpxtest needs
longer than 150 minutes.

The timeout is for 150 minutes without console output,
making the build succeed with the serial harness that
outputs during the hpxtest run.
--- End Message ---
--- Begin Message ---
Source: healpix-cxx
Source-Version: 3.30.0-8

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

Debian distribution maintenance software
pp.
Leo Singer  (supplier of updated healpix-cxx 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, 31 Jan 2018 09:08:06 -0500
Source: healpix-cxx
Binary: libhealpix-cxx-dev libhealpix-cxx0
Architecture: source amd64
Version: 3.30.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Leo Singer 
Description:
 libhealpix-cxx-dev - representation of spherical data - C++ development library
 libhealpix-cxx0 - representation of spherical data - C++ shared library
Closes: 888919
Changes:
 healpix-cxx (3.30.0-8) unstable; urgency=medium
 .
   * Switch back to using serial test harness. The parallel test
 harness doesn't print any output until it is done, which
 causes some Debian buildds to time out. (Closes: 888919)
Checksums-Sha1:
 a510345396e7215341b92ba92d0a81675b58b9c6 2082 healpix-cxx_3.30.0-8.dsc
 16cb682a69be82c7b9f2bb22c1d794b80ce51f56 5196 
healpix-cxx_3.30.0-8.debian.tar.xz
 74d170a1aefbb7d782e4df2f9557f61b67884ac9 6674 
healpix-cxx_3.30.0-8_amd64.buildinfo
 8a2a02da45d8d9be4e87447ab4245e3fb1549f9c 9375772 
libhealpix-cxx-dev_3.30.0-8_amd64.deb
 282fb41e5e78045d0b96c7ccb5e1ba3c8467c78b 1705568 
libhealpix-cxx0-dbgsym_3.30.0-8_amd64.deb
 166a00f15ce04e378735bd1f5cf39ad2ef638411 404668 
libhealpix-cxx0_3.30.0-8_amd64.deb
Checksums-Sha256:
 652ebbcaa8d92b000ccbc240586b71f0767afe082c8ee3a927fe21274e713d1a 2082 
healpix-cxx_3.30.0-8.dsc
 922b5452525055d0d576bfc7e39fb542d49ebd453b095c3d088ab923f4894ac2 5196 
healpix-cxx_3.30.0-8.debian.tar.xz
 498ef1d54d2f5dc3e5b05463c5ad6e1f3f08bc22483d72cc1ae7b6e8fbffc896 6674 
healpix-cxx_3.30.0-8_amd64.buildinfo
 1a333c38781387f2d5d694dafcddda88d294060ec2c0497d68ad1f87a6b8de20 9375772 
libhealpix-cxx-dev_3.30.0-8_amd64.deb
 226ad829c5df041ab76e503de0d92ccc502d709b3247447a53aeb061e6e82636 1705568 
libhealpix-cxx0-dbgsym_3.30.0-8_amd64.deb
 96ba2451170fca9880e7948c17e93d062d3ea72efb51d018e2a0de4196362029 404668 
libhealpix-cxx0_3.30.0-8_amd64.deb
Files:
 87a27735e610f75a61cf41f1a50e5c9d 2082 libs optional healpix-cxx_3.30.0-8.dsc
 3bde12f95ef1f9fddb6ee13fef115d25 5196 libs optional 
healpix-cxx_3.30.0-8.debian.tar.xz
 3de0fc1f996f340aea647dbc78edd3f1 6674 libs optional 
healpix-cxx_3.30.0-8_amd64.buildinfo
 f8f5878c99ba80529711beae7e2bf096 9375772 libdevel optional 
libhealpix-cxx-dev_3.30.0-8_amd64.deb
 f6c86c29e99962dd09388a9e6435c26c 1705568 debug optional 
libhealpix-cxx0-dbgsym_3.30.0-8_amd64.deb
 818d97f196ec4c440012143a556c9c71 404668 libs optional 
libhealpix-cxx0_3.30.0-8_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#888953: gobby accesses the network during the build

[Matthias Klose]

Package: src:gobby
Version: 0.6.0~20170204~e5c2d1-2
Severity: serious
Tags: sid buster

While seen on a launchpad build, it looks like a missing build dependency,
because it tries to access the docbookx.dtd from the network:

make[3]: Leaving directory '/<>/po'
Making check in help
make[3]: Entering directory '/<>/help'
xmllint --noout --noent --path C:./C --xinclude --postvalid ./C/gobby.xml
xmllint --noout --xinclude --dtdvalid
'http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd'
gobby-C.omf
error : error : No such file or directory
No such file or directory
warning: failed to load external entity
"http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd;
Could not parse DTD
http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd
./C/gobby.xml:6: warning: failed to load external entity
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
]>
  ^
Makefile:945: recipe for target 'check-doc-omf' failed
make[3]: *** [check-doc-omf] Error 2
make[3]: *** Waiting for unfinished jobs
error : No such file or directory
warning: failed to load external entity
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
validity error : Could not load the external subset
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
Document ./C/gobby.xml does not validate
Makefile:917: recipe for target 'check-doc-docs' failed
make[3]: *** [check-doc-docs] Error 3
make[3]: Leaving directory '/<>/help'
Makefile:1272: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:1567: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2

https://launchpad.net/ubuntu/+source/gobby/0.6.0~20170204~e5c2d1-2/+build/14219811

Bug#861515: marked as done (src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖ copy - timestamp_equal)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 15:16:32 +0100
with message-id <20180131141632.577zzz6vyul6u...@angband.pl>
and subject line Re: unreproducibile
has caused the Debian Bug report #861515,
regarding src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖ 
copy - timestamp_equal
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.)


-- 
861515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-grunt-contrib-copy
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build on at least armhf and i386.

The test that fails is:
✖ copy - timestamp_equal

Architectures I've tested:
✖ armhf (native)
✖ armhf (arm64)
✔ armhf (qemu-user on amd64)
✔ amd64
✖ i386 (native)
✖ i386 (amd64)
✔ arm64 (native)
✔ arm64 (qemu-user on amd64)

It doesn't seem to be filesystem related: all but one were done on btrfs,
but that i386 machine uses ext4.  That machine also uses stretch's official
kernel; the rest are on current mainline.

It's 1.0.0-2, so the previous FTBFS (#860634) is apparently fixed (and the
error is different).


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

Kernel: Linux 4.11.0-rc7-00021-gc7b52626967a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Wed, Jan 31, 2018 at 10:07:39AM +0100, Paolo Greppi wrote:
> this seems now to have gone away by itself,

Aye, works for me too.

>> Architectures I've tested:
>> ✖ armhf (native)
>> ✖ armhf (arm64)
>> ✔ armhf (qemu-user on amd64)
>> ✔ amd64
>> ✖ i386 (native)
>> ✖ i386 (amd64)
>> ✔ arm64 (native)
>> ✔ arm64 (qemu-user on amd64)

Retested on armhf (native), armhf (arm64), i386 (amd64); can't check i386
(native) right now.

> possibly thanks to the upgrade from nodejs 4.x to 8.x:
> I don't see any error on the buildds, and it works without the patch on my 
> x86 VM here.
> 
> So I have reset the repo to the debian/1.0.0-2 tag, and moved the patch
> to a separate branch (wip/paolog/skip_test) in case we need it later.
> 
> @Adam, if you have access to an armhf test machine, you could try yourself on 
> that too.

Tried multiple times, succeeded evert time.

> I'll wait a bit more before I close this one and the upstream bug.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?--- End Message ---

Processed: Re: Bug#541538: pulseaudio: disable flat volumes

[Debian Bug Tracking System]

Processing control commands:

> severity 541538 grave
Bug #541538 [pulseaudio] pulseaudio: disable flat volumes
Bug #674935 [pulseaudio] pulseaudio: disable flat volumes
Bug #674936 [pulseaudio] pulseaudio: disable flat volumes
Bug #697119 [pulseaudio] pulseaudio: disable flat volumes
Bug #782730 [pulseaudio] pulseaudio: Noise when a short sound is played with 
another song playing
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'

-- 
541538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541538
674935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674935
674936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674936
697119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697119
782730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

[Olaf van der Spek]

Hi,

> Anyone else have any good ideas on how to handle this?

I do. The solution is quite simple: do not, ever, remove user data / databases.

It makes everything so much simpler, both on the user side and on the
dev side. No weird questions when installing, no databases gone by
accident..

-- 
Olaf

Bug#888155: apper FTBFS with libpackagekitqt5-dev 1.0.1-1

[Matthias Klumpp]

2018-01-31 12:33 GMT+01:00 Juhani Numminen :
> Control: tags -1 fixed-upstream
>
> On Tue, 23 Jan 2018 19:32:45 +0200 Adrian Bunk  wrote:
>> Source: apper
>> ...
>> CMake Error at CMakeLists.txt:38 (find_package):
>>   Could not find a configuration file for package "PackageKitQt5" that is
>>   compatible with requested version "0.9.0".
>>
>>   The following configuration files were considered but not accepted:
>>
>> 
>> /usr/lib/x86_64-linux-gnu/cmake/packagekitqt5/packagekitqt5-config.cmake, 
>> version: 1.0.1
>
> There's an upstream commit "Make it build with packagekit-qt 1.0.0":
> https://cgit.kde.org/apper.git/commit/?id=55b8fc8c2d1a8a971a31d1c40a185fb978551b84

I am aware, the current plan is to wait for a fresh Apper release
(because there are a lot more improvements made in Git) and fix this
issue then.

Cheers,
Matthias

Bug#884023: New pixmap

[Teus Benschop]

The next "bibledit" package is going to have a renamed pixmap, so it's no
longer going to install the same pixmap as package "bibledit-gtk".

Once the new bibledit package is uploaded to Debian, its changelog will
close this bug, that's bug #884023.

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 888945 buster sid
Bug #888945 [ruby-uglifier] ruby-uglifier FTBFS with node-source-map 0.7
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#887477: marked as done (mysql-5.7: Security fixes from the January 2018 CPU)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 13:07:12 +
with message-id 
and subject line Bug#887477: fixed in mysql-5.7 5.7.21-1
has caused the Debian Bug report #887477,
regarding mysql-5.7: Security fixes from the January 2018 CPU
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.)


-- 
887477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-5.7
Version: 5.7.20-1
Severity: grave
Tags: security upstream

Hi

See
http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixMSQL
for a list of CVEs affecting it and
https://security-tracker.debian.org/mysql-5.7.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mysql-5.7
Source-Version: 5.7.21-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Jan 2018 08:13:12 +0100
Source: mysql-5.7
Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 
mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server 
mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7
Architecture: source
Version: 5.7.21-1
Distribution: unstable
Urgency: high
Maintainer: Debian MySQL Maintainers 
Changed-By: Lars Tangvald 
Description:
 libmysqlclient-dev - MySQL database development files
 libmysqlclient20 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 mysql-client - MySQL database client (metapackage depending on the latest 
versio
 mysql-client-5.7 - MySQL database client binaries
 mysql-client-core-5.7 - MySQL database core client binaries
 mysql-server - MySQL database server (metapackage depending on the latest 
versio
 mysql-server-5.7 - MySQL database server binaries and system database setup
 mysql-server-core-5.7 - MySQL database server binaries
 mysql-source-5.7 - MySQL source
 mysql-testsuite - MySQL regression tests
 mysql-testsuite-5.7 - MySQL 5.7 testsuite
Closes: 887477
Changes:
 mysql-5.7 (5.7.21-1) unstable; urgency=high (security fixes)
 .
   * Imported upstream version 5.7.21 to fix security issues:
 - 
http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
 - CVE-2018-2562 CVE-2018-2565 CVE-2018-2573 CVE-2018-2576
 - CVE-2018-2583 CVE-2018-2586 CVE-2018-2590 CVE-2018-2591
 - CVE-2018-2600 CVE-2018-2612 CVE-2018-2622 CVE-2018-2640
 - CVE-2018-2645 CVE-2018-2646 CVE-2018-2647 CVE-2018-2665
 - CVE-2018-2667 CVE-2018-2668 CVE-2018-2696 CVE-2018-2703
 - CVE-2017-3737
 (Closes: #887477)
Checksums-Sha1:
 8a5ff3493435e5394daceeefce432ae8782d13e2 3252 mysql-5.7_5.7.21-1.dsc
 63b07cfd33d494b223e9b4d73492d3508834abd0 48931457 mysql-5.7_5.7.21.orig.tar.gz
 a576fd9f138cdc94490002721641c51b5f80a663 153668 
mysql-5.7_5.7.21-1.debian.tar.xz
Checksums-Sha256:
 315114fd47fab2dff9632256c582343550da50895df6633bff109abb1deca2e0 3252 
mysql-5.7_5.7.21-1.dsc
 ad29ecb6fb3c3571394fe231633a2d1d188d49e9eb749daa4e8799b7630daa09 48931457 
mysql-5.7_5.7.21.orig.tar.gz
 9a375e417dd966652b202792b6ab3695262bba32ae49fb2f430ab67405588cd3 153668 
mysql-5.7_5.7.21-1.debian.tar.xz
Files:
 7bbe9ef368bdffd60e1f715aeee3f2f2 3252 database optional mysql-5.7_5.7.21-1.dsc
 27313ded360f39f237e99404666bc448 48931457 database optional 
mysql-5.7_5.7.21.orig.tar.gz
 06c60390c5d24f8610389d7de24b2db2 153668 database optional 
mysql-5.7_5.7.21-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJacbknAAoJEOVkucJ1vdUuDX8P/iku+UgvbPmY3ErRlLJGvNTZ
kiOURRGcTqUUclzF8sHq7s3ZipazWMjuWcyuEM/OaUvLqAvSxjs5cShXTQc80l2q
htAm++gXxzlMN1wgoEjfuchpYF5nni3tCj9zEcEguyPnwgmv0+SjnmClEjsFA1MS
8lnwbf+AQKnRAPGUC7iQcT1b34MIbFbjQBCtJ3aWsO1sBsXa6qgsiw80J8GGG73/

Bug#887898: Proper fix for #887898

[Jason Duerstock]

It appears that Red Hat has run into the same thing, and they have a
clearer fix for it:
https://bugzilla.redhat.com/show_bug.cgi?id=1384016

Bug#888484: Updates for stretch/jessie not in security repo

[Andreas Schamanek]

On Wed, 31 Jan 2018, at 12:52, Klaus Keppler wrote:


Many "sources.list" files do not contain the "-updates" repository


Even more so: I do source -updates, however, only now I see why the 
update was not yet installed automagically:


# apt-cache policy clamav
clamav:
  Installed: 0.99.2+dfsg-0+deb8u2
  Candidate: 0.99.2+dfsg-0+deb8u2
  Version table:
 0.99.2+dfsg-0+deb8u3 0
500 http://ftp2.de.debian.org/debian/ jessie-updates/main amd64 Packages
 *** 0.99.2+dfsg-0+deb8u2 0
990 http://ftp2.de.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status

--
-- Andreas

Bug#882095: python-pyrax FTBFS: test failures

[Sascha Girrulat]

Hi,

the support of non keystore authentication were removed since
python-novaclient 7.0.0.[1]

I will take a look if it makes sense to patch python-pyrax another time.

Cheers
Sascha

[1]
https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=daa9bdc82335b37b33d21264a770e10ee452f22c



signature.asc
Description: OpenPGP digital signature

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 888944 buster sid
Bug #888944 [node-css] node-css FTBFS with node-source-map 0.7
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: ruby-uglifier FTBFS with node-source-map 0.7

[Debian Bug Tracking System]

Processing control commands:

> block 888926 by -1
Bug #888926 [node-source-map] tracking bug: breakages in reverse dependencies 
of node-source-map
888926 was blocked by: 888944 46 888942 888943
888926 was blocking: 888279 888940
Added blocking bug(s) of 888926: 888945

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

Bug#888945: ruby-uglifier FTBFS with node-source-map 0.7

[Pirate Praveen]

Package: ruby-uglifier
Version: 2.7.2+dfsg-2
Severity: serious
Control: block 888926 by -1

1) Uglifier should be able to handle an input source map
 # Needs UglifyJS >= 2.5 to work
 Failure/Error: @context.call(Uglifier::JS, options)

 JSON::ParserError:
   765: unexpected token at '(node:8571)
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection
id: 2): TypeError: Cannot read property 'join' of undefined
   (node:8571) [DEP0018] DeprecationWarning: Unhandled promise
rejections are deprecated. In the future, promise rejections that are
not handled will terminate the Node.js process with a non-zero exit code.
   '
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:230:in
`run_uglifyjs'
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:197:in
`compile_with_map'
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:169:in
`compile_with_map'
 #
/<>/ruby-uglifier-2.7.2+dfsg/spec/source_map_spec.rb:78:in
`block (2 levels) in '

Failures:

  1) Uglifier generates source maps
 Failure/Error: @context.call(Uglifier::JS, options)

 ExecJS::RuntimeError:
   SyntaxError: Unexpected token: punc (,)
 # JS_Parse_Error.get ((execjs):3893:621)
 # (execjs):4293:48
 # (execjs):1:102
 # Object. ((execjs):1:120)
 # Module._compile (module.js:635:30)
 # Object.Module._extensions..js (module.js:646:10)
 # Module.load (module.js:554:32)
 # tryModuleLoad (module.js:497:12)
 # Function.Module._load (module.js:489:3)
 # Function.Module.runMain (module.js:676:10)
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:230:in
`run_uglifyjs'
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:197:in
`compile_with_map'
 #
/<>/ruby-uglifier-2.7.2+dfsg/spec/source_map_spec.rb:20:in
`block (2 levels) in '

  2) Uglifier minifies JS
 Failure/Error: @context.call(Uglifier::JS, options)

 ExecJS::RuntimeError:
   SyntaxError: Unexpected token: punc (,)
 # JS_Parse_Error.get ((execjs):3893:621)
 # (execjs):4293:48
 # (execjs):1:102
 # Object. ((execjs):1:120)
 # Module._compile (module.js:635:30)
 # Object.Module._extensions..js (module.js:646:10)
 # Module.load (module.js:554:32)
 # tryModuleLoad (module.js:497:12)
 # Function.Module._load (module.js:489:3)
 # Function.Module.runMain (module.js:676:10)
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:230:in
`run_uglifyjs'
 # /<>/ruby-uglifier-2.7.2+dfsg/lib/uglifier.rb:188:in
`compile'
 # /<>/ruby-uglifier-2.7.2+dfsg/spec/uglifier_spec.rb:8:in
`block (2 levels) in '

Finished in 45.44 seconds (files took 0.1398 seconds to load)
44 examples, 2 failures, 1 pending

Failed examples:

rspec /<>/ruby-uglifier-2.7.2+dfsg/spec/source_map_spec.rb:18
# Uglifier generates source maps
rspec /<>/ruby-uglifier-2.7.2+dfsg/spec/uglifier_spec.rb:6 #
Uglifier minifies JS



signature.asc
Description: OpenPGP digital signature

Processed: Update severity of bug#884116

[Debian Bug Tracking System]

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

> severity 884116 critical
Bug #884116 [src:linux] linux-image-4.9.0-4-amd64: screen atrifacts then crash
Bug #883980 [src:linux] base-files: After updating to 9.3, Screen Sporadically 
Goes Blank
Bug #884001 [src:linux] linux-image-4.9.0-4-amd64: Severe graphics corruption 
on intel graphics after kernel upgrade
Bug #884061 [src:linux] linux-image-4.9.0-4-amd64: screen scrolls wildly
Bug #885570 [src:linux] linux-image-4.9.0-4-amd64: display breakage with Intel 
HD Graphics 5500
Severity set to 'critical' from 'important'
Severity set to 'critical' from 'important'
Severity set to 'critical' from 'important'
Severity set to 'critical' from 'important'
Severity set to 'critical' from 'important'
> thanks
Stopping processing here.

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

Bug#888944: node-css FTBFS with node-source-map 0.7

[Pirate Praveen]

Package: node-css
Version: 2.1.0-2
Severity: serious
Control: block 888926 by -1

108 passing (432ms)
  1 failing

  1) stringify(obj, {sourcemap: true})
   should generate source maps alongside when using identity compiler:
 TypeError: map.originalPositionFor is not a function
  at Context. (test/stringify.js:30:9)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)





signature.asc
Description: OpenPGP digital signature

Processed: node-css FTBFS with node-source-map 0.7

[Debian Bug Tracking System]

Processing control commands:

> block 888926 by -1
Bug #888926 [node-source-map] tracking bug: breakages in reverse dependencies 
of node-source-map
888926 was blocked by: 888943 888942 46
888926 was blocking: 888279 888940
Added blocking bug(s) of 888926: 888944

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

Bug#888484: Updates for stretch/jessie not in security repo

[Klaus Keppler]

Hi,

is there a special reason why the updates are not published through the 
"security" repositories of Debian Stretch/Jessie?


- on Debian 7, the update is in "wheezy" (via security)
- on Debian 8, the update is in "jessie-updates"
- on Debian 9, the update is in "stretch-updates"

With regard of the severity of the bug, I can't understand this release 
strategy. Or am I just too impatient?


Many "sources.list" files do not contain the "-updates" repository, for 
example unmodified Xen instances created with "xen-create-image".


So I suggest to push this update also into debian-security.

Thanks for your efforts & best regards

   -Klaus

Bug#888943: node-concat-with-sourcemaps FTBFS with node-source-map 0.7

[Pirate Praveen]

Package: node-concat-with-sourcemaps
Version: 1.0.4-2
Severity: serious
Control: block 888926 by -1

# should concatenate content with source maps with "\n" and produce
combined source map
/<>/index.js:58
  upstreamSM.eachMapping(function(mapping) {
 ^

TypeError: upstreamSM.eachMapping is not a function
at Concat.add (/<>/index.js:58:18)
at /<>/test/index.js:11:14
at Array.forEach ()
at Test. (/<>/test/index.js:10:19)
at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Test.run (/usr/lib/nodejs/tape/lib/test.js:95:10)
at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Immediate.next [as _onImmediate]
(/usr/lib/nodejs/tape/lib/results.js:71:15)
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)



signature.asc
Description: OpenPGP digital signature

Processed: node-concat-with-sourcemaps FTBFS with node-source-map 0.7

[Debian Bug Tracking System]

Processing control commands:

> block 888926 by -1
Bug #888926 [node-source-map] tracking bug: breakages in reverse dependencies 
of node-source-map
888926 was blocked by: 888942 46
888926 was blocking: 888279 888940
Added blocking bug(s) of 888926: 888943

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

Bug#887446: marked as done (astroplan: FTBFS and Debci failure)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 12:04:40 +
with message-id 
and subject line Bug#887446: fixed in astroplan 0.4-2
has caused the Debian Bug report #887446,
regarding astroplan: FTBFS and Debci failure
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.)


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

Some recent change in unstable makes astroplan FTBFS and Debci fail:

https://ci.debian.net/packages/a/astroplan/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/astroplan.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/astroplan.html

...
=== FAILURES ===
__ test_schedule_insert_slot ___

def test_schedule_insert_slot():
start = Time('2016-02-06 03:00:00')
schedule = Schedule(start, start + 5*u.hour)
# testing for when float comparison doesn't work, does it start/end at 
the right time
duration = 2*u.hour + 1*u.second
end_time = start + duration
block = TransitionBlock.from_duration(duration)
schedule.insert_slot(end_time - duration, block)
assert not end_time - duration == start
assert len(schedule.slots) == 2
assert schedule.slots[0].start == start
schedule = Schedule(start, start + 5*u.hour)
# testing for when float evaluation does work
duration = 2*u.hour
end_time = start + duration
block = TransitionBlock.from_duration(duration)
schedule.insert_slot(end_time - duration, block)
>   assert end_time - duration == start
E   AssertionError: assert ( - ) == 
...
 1 failed, 113 passed, 1 skipped, 11 warnings in 386.32 seconds 
debian/rules:29: recipe for target 'python-test2.7' failed
make[1]: *** [python-test2.7] Error 1
--- End Message ---
--- Begin Message ---
Source: astroplan
Source-Version: 0.4-2

We believe that the bug you reported is fixed in the latest version of
astroplan, 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.
Vincent Prat  (supplier of updated astroplan 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, 31 Jan 2018 11:32:53 +0100
Source: astroplan
Binary: python-astroplan python3-astroplan python-astroplan-doc
Architecture: source
Version: 0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Vincent Prat 
Description:
 python-astroplan - Observation planning package for astronomers (Python 2)
 python-astroplan-doc - Observation planning package for astronomers 
(documentation)
 python3-astroplan - Observation planning package for astronomers (Python 3)
Closes: 887446
Changes:
 astroplan (0.4-2) unstable; urgency=medium
 .
   * Disable assertion failing without any reason (Closes: #887446)
   * Update debhelper compatibility version to 11
   * Update Standard-Version to 4.1.3
   * Update copyright file and use secure URI
Checksums-Sha1:
 00408844165a58511c74f05becce2e1042a7b432 2423 astroplan_0.4-2.dsc
 081d4b5859826308fd686acee22518c688874742 6292 astroplan_0.4-2.debian.tar.xz
 098350b56fbf9af43cd6f833453fc8a478b1d9ad 11340 astroplan_0.4-2_source.buildinfo
Checksums-Sha256:
 3c50d7bd1882c0645ee836d565a92b29c057025b11585b8109a35a64e8a738f0 2423 
astroplan_0.4-2.dsc
 0b79994b2ba337bcf798b948bf20eb7b29cbc31f0d99d93052232bc02c899d62 6292 
astroplan_0.4-2.debian.tar.xz
 8260c7e79f6aca9df6f7271505a26d9ecdf65abed9c5f2bffbe133265ae48ab9 11340 
astroplan_0.4-2_source.buildinfo
Files:
 7062565848ffa4e565e9c6a9c18a3999 2423 python optional astroplan_0.4-2.dsc
 57afa9314b2de78a3ff9c24dba1b2a66 6292 python optional 
astroplan_0.4-2.debian.tar.xz
 871e8d018c1050778639d2c37c82b132 11340 python optional 
astroplan_0.4-2_source.buildinfo

-BEGIN PGP 

Bug#888942: node-combine-source-map FTBFS with node-source-map 0.7

[Pirate Praveen]

Package: node-combine-source-map
Version: 0.8.0+ds-4
Severity: serious
Control: block 888926 by -1

# should concatenate content with source maps with "\n" and produce
combined source map
/<>/index.js:58
  upstreamSM.eachMapping(function(mapping) {
 ^

TypeError: upstreamSM.eachMapping is not a function
at Concat.add (/<>/index.js:58:18)
at /<>/test/index.js:11:14
at Array.forEach ()
at Test. (/<>/test/index.js:10:19)
at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Test.run (/usr/lib/nodejs/tape/lib/test.js:95:10)
at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Immediate.next [as _onImmediate]
(/usr/lib/nodejs/tape/lib/results.js:71:15)
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)



signature.asc
Description: OpenPGP digital signature

Processed: node-combine-source-map FTBFS with node-source-map 0.7

[Debian Bug Tracking System]

Processing control commands:

> block 888926 by -1
Bug #888926 [node-source-map] tracking bug: breakages in reverse dependencies 
of node-source-map
888926 was blocked by: 46
888926 was blocking: 888279 888940
Added blocking bug(s) of 888926: 888942

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

Bug#888155: apper FTBFS with libpackagekitqt5-dev 1.0.1-1

[Juhani Numminen]

Control: tags -1 fixed-upstream

On Tue, 23 Jan 2018 19:32:45 +0200 Adrian Bunk  wrote:
> Source: apper
> ...
> CMake Error at CMakeLists.txt:38 (find_package):
>   Could not find a configuration file for package "PackageKitQt5" that is
>   compatible with requested version "0.9.0".
> 
>   The following configuration files were considered but not accepted:
> 
> /usr/lib/x86_64-linux-gnu/cmake/packagekitqt5/packagekitqt5-config.cmake, 
> version: 1.0.1

There's an upstream commit "Make it build with packagekit-qt 1.0.0":
https://cgit.kde.org/apper.git/commit/?id=55b8fc8c2d1a8a971a31d1c40a185fb978551b84

Cheers,
Juhani

Processed: Re: apper FTBFS with libpackagekitqt5-dev 1.0.1-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #888155 [src:apper] apper FTBFS with libpackagekitqt5-dev 1.0.1-1
Added tag(s) fixed-upstream.

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

Bug#888880: php-solr FTBFS with PHP 7.2: error: 'ZEND_ACC_CLONE' undeclared here

[Juhani Numminen]

On Tue, 30 Jan 2018 22:29:31 +0200 Adrian Bunk  wrote:
> Source: php-solr
> ...
> /<>/build-7.2/src/php7/php_solr.c:560:56: error: 
> 'ZEND_ACC_CLONE' undeclared here (not in a function); did you mean 
> 'ZEND_AST_CLONE'?

Looks like the fix is committed to Debian VCS already.
https://anonscm.debian.org/cgit/pkg-php/php-solr.git/commit/?id=2da573ef2f3fc98f4fb963dec508b4194326989c

Regards,
Juhani

Processed: Re: php-mongodb FTBFS with PHP 7.2: error: 'timelib_time {aka struct _timelib_time}' has no member named 'f'

[Debian Bug Tracking System]

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

> forwarded 81 https://jira.mongodb.org/browse/PHPC-997
Bug #81 [src:php-mongodb] php-mongodb FTBFS with PHP 7.2: error: 
'timelib_time {aka struct _timelib_time}' has no member named 'f'
Set Bug forwarded-to-address to 'https://jira.mongodb.org/browse/PHPC-997'.
> tags 81 fixed-upstream
Bug #81 [src:php-mongodb] php-mongodb FTBFS with PHP 7.2: error: 
'timelib_time {aka struct _timelib_time}' has no member named 'f'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

[Tobias Hansen]

Control: block -1 by 888459 888911

Not a surprise as long as some dependencies are built against libmpfr4.

On 01/31/2018 06:01 AM, Matthias Klose wrote:
> Package: src:sagemath
> Version: 8.2-1
> Severity: serious
> Tags: sid buster
>
> see https://buildd.debian.org/status/package.php?p=sagemath=unstable
>
> test failures on every architecture.
>

Processed: Re: Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 888459 888911
Bug #888912 [src:sagemath] sagemath test failures with mpfr 4.0.0 and several 
architectures
888912 was not blocked by any bugs.
888912 was not blocking any bugs.
Added blocking bug(s) of 888912: 888459 and 888911

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

Bug#888935: node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never'

[Adrian Bunk]

Source: node-xterm
Version: 2.7.0+ds1-1
Severity: serious

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1'
tsc --project .
src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement' does not 
exist on type 'never'.
debian/rules:19: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Processed: Add found version

[Debian Bug Tracking System]

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

> found 888925 2.3.00-4
Bug #888925 [src:libminc] libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt 
to use feature that was not turned on when netCDF was built
Marked as found in versions libminc/2.3.00-4.
> thanks
Stopping processing here.

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

Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3

[Robin Mueller-Bady]

On Wed, 31 Jan 2018 08:56:55 +0300 =?UTF-8?B?0JrQvtC70Y8g0JPRg9GA0YzQtdCy?= 
 wrote:
> Hi,
> 
> 12.01.2018 16:31, Robin пишет:
> > Versions of packages telegram-desktop depends on:
> ...
> > pn  libtgvoip1.0 
> 
> It seems you have no installed package with libtgvoip. This may have led
> to such crash.

If this is the case, it should added as a dependency. Unfortunately, I cannot 
test it as
I'm running the current version of Telegram right now.

> 
> > Setting the environment variabel 'XDG_CURRENT_DESKTOP' to 'NONE' solves the
> > issue temporarily.
> 
> Does I understand correctly, Telegram works fine *some time* and then
> crashes? This may be related to an incoming call that cannot be handle
> properly without libtgvoip, and it's unlikely affected by the
> XDG_CURRENT_DESKTOP environment variable.

Setting XDG_CURRENT_DESKTOP to NONE works fine all the time. If it is not set, 
Telegram
won't start at all due to a SIGSEV. In both ways completely deterministic :-)

Bug#888925: libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt to use feature that was not turned on when netCDF was built

[Bas Couwenberg]

Control: reassign -1 src:libminc

Hi Adrian,

On 2018-01-31 10:06, Adrian Bunk wrote:

I don't know which of the packages is at fault here,
the change that triggered it was the new netcdf.


libminc needs to fix their test or their usage of libnetcdf.

Kind Regards,

Bas

Processed: Re: Bug#888925: libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt to use feature that was not turned on when netCDF was built

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:libminc
Bug #888925 [src:netcdf] libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt 
to use feature that was not turned on when netCDF was built
Bug reassigned from package 'src:netcdf' to 'src:libminc'.
No longer marked as found in versions netcdf/1:4.6.0-2.
Ignoring request to alter fixed versions of bug #888925 to the same values 
previously set

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

Processed: Add version

[Debian Bug Tracking System]

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

> found 888921 2:8.39-8
Bug #888921 [src:pcre3] gcc-7 upgrade adds symbol in pcre3
Marked as found in versions pcre3/2:8.39-8.
> thanks
Stopping processing here.

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

Bug#888933: gli FTBFS with libglm-dev 0.9.9~a2-1

[Adrian Bunk]

Source: gli
Version: 0.8.2.0+ds1-2
Severity: serious
Tags: buster unstable

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

...
In file included from /build/1st/gli-0.8.2.0+ds1/./gli/type.hpp:13:0,
 from /build/1st/gli-0.8.2.0+ds1/./gli/format.hpp:6,
 from /build/1st/gli-0.8.2.0+ds1/./gli/gli.hpp:39,
 from /build/1st/gli-0.8.2.0+ds1/test/bug/bug.cpp:1:
/usr/include/glm/gtx/std_based_type.hpp:21:3: error: #error "GLM: 
GLM_GTX_std_based_type is an experimental extension and may change in the 
future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really 
want to use it."
 # error "GLM: GLM_GTX_std_based_type is an experimental extension and may 
change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, 
if you really want to use it."
   ^

Bug#888931: forge FTBFS with libglm-dev 0.9.9~a2-1

[Adrian Bunk]

Source: forge
Version: 0.9.2-2
Severity: serious
Tags: buster sid experimental

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

...
In file included from /usr/include/glm/gtx/string_cast.hpp:23:0,
 from /build/1st/forge-0.9.2/src/backend/opengl/common.hpp:21,
 from /build/1st/forge-0.9.2/src/backend/opengl/backend.hpp:12,
 from /build/1st/forge-0.9.2/src/backend/window.hpp:12,
 from /build/1st/forge-0.9.2/src/backend/handle.hpp:14,
 from /build/1st/forge-0.9.2/src/api/c/font.cpp:12:
/usr/include/glm/gtx/dual_quaternion.hpp:24:3: error: #error "GLM: 
GLM_GTX_dual_quaternion is an experimental extension and may change in the 
future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really 
want to use it."
 # error "GLM: GLM_GTX_dual_quaternion is an experimental extension and may 
change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, 
if you really want to use it."
   ^

Bug#888932: fw4spl FTBFS with libglm-dev 0.9.9~a2-1

[Adrian Bunk]

Source: fw4spl
Version: 11.0.4-2
Severity: serious

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

...
In file included from 
/build/1st/fw4spl-11.0.4/SrcLib/core/fwMath/src/fwMath/MatrixFunctions.cpp:12:0:
/usr/include/glm/gtx/euler_angles.hpp:19:3: error: #error "GLM: 
GLM_GTX_euler_angles is an experimental extension and may change in the future. 
Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really want to 
use it."
 # error "GLM: GLM_GTX_euler_angles is an experimental extension and may change 
in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you 
really want to use it."
   ^

Bug#888922: marked as done (acbuild: build dependency golang-github-coreos-rkt-dev was renamed)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 09:19:39 +
with message-id 
and subject line Bug#888922: fixed in acbuild 0.4.0+dfsg-2
has caused the Debian Bug report #888922,
regarding acbuild: build dependency golang-github-coreos-rkt-dev was renamed
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.)


-- 
888922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acbuild
Version: 0.4.0+dfsg-1
Severity: serious

 builddeps:acbuild : Depends: golang-github-coreos-rkt-dev (>= 1.8.0~) but it 
is not installable
--- End Message ---
--- Begin Message ---
Source: acbuild
Source-Version: 0.4.0+dfsg-2

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

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated acbuild 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, 31 Jan 2018 09:52:49 +0100
Source: acbuild
Binary: acbuild
Architecture: source
Version: 0.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Michael Stapelberg 
Description:
 acbuild- utility to build and modify App Container Images
Closes: 888922
Changes:
 acbuild (0.4.0+dfsg-2) unstable; urgency=medium
 .
   * rkt-dev was renamed (Closes: #888922)
   * d/control: set XS-Go-Import-Path
Checksums-Sha1:
 454c6db2b8e570db7637196ae291fd3e6494117f 2324 acbuild_0.4.0+dfsg-2.dsc
 ae23c0b6345a5a8fbb28c53a1f26187f854e1518 3784 
acbuild_0.4.0+dfsg-2.debian.tar.xz
 c374609dc6db2b9524797152b83dcdffb027d257 13863 
acbuild_0.4.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 19bbca40dbb7c506c493b078d6c9fbb8bff7c79e2f2452692b7569c760904dda 2324 
acbuild_0.4.0+dfsg-2.dsc
 e5ee474cadf4f6d4a124365745e7edac9e53f95666cbf96ee39f74f90248f46f 3784 
acbuild_0.4.0+dfsg-2.debian.tar.xz
 f630a04d9a25bf316da902d452bc023651442c65545dd1c0c03c05643b1708f1 13863 
acbuild_0.4.0+dfsg-2_amd64.buildinfo
Files:
 babbccd8faec91b53167f8b9db810116 2324 utils extra acbuild_0.4.0+dfsg-2.dsc
 30b2ead21dcb73e07e4ffbd6653bd86f 3784 utils extra 
acbuild_0.4.0+dfsg-2.debian.tar.xz
 29713b28332ba77c09015adc7fcbd8c7 13863 utils extra 
acbuild_0.4.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAlpxhD8ACgkQTnFg7UrI
7h1+rQ//ad5Ymi+Aw6JgA3G5SodqfJJpbdihhXMsW2LYLQ9bEIHWoNzUAWidMX21
kXL9G6vMxnIUJG8B6P3aJIduKl3xsBdUcs2Ni9yfLD3kUaCZhbvzlX7bSflkEEFy
YYj20DUiAUEltVtamAzfnGNSSQV8KNjKqTshZWmCqWEsHOOTPLDYIBGHep/roobD
0ru8CPbSi11vdY239MkN4Vvj35VU3EI2aIQW155ZyZbZ8B4wS90W4BrAOkVa3MNm
K684F4OG8hU8BilGHNslmaIz463L7B2eZWG3w182Vc6rVbslz47u6uytXZd6irCt
icfkMP1KTiJKig8eRdAN/AYf0DXgxz8gg2Uwajc3FpV08qLSpvGeyVS6cXqAel6w
KnM7ym8NM4ItWfIBHoCzQUK3YOTE1i5lJ65Glp4ieK/JrcHsxUWYhBb+GQBxMDog
ofqXqdR9azHU0QoiUJqngs82bVNxNVK6A53QHlspP60yWPlCsjDJ98HCUT5AIQCs
TA1rwO6cTfPg6qpPvDzVKS1oe54MpMeD6ptpISkmvUOQwD7nJEVg9ZSO8/3gOOyH
E/my8d3/whIB5bU0YnUXRDDQjMky6CPms+MzmKMFwZHObPEYP6e4nO+Wpb6E5UOm
v+dnpS4JQzM7a9i/NHBmeCDlY72vxP33qHxfSgyjl508HChMwUI=
=zFPD
-END PGP SIGNATURE End Message ---

Bug#888929: libetonyek FTBFS with libglm-dev 0.9.9~a2-1

[Adrian Bunk]

Source: libetonyek
Version: 0.1.7-2
Severity: serious

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

...
In file included from /usr/include/glm/gtx/quaternion.hpp:20:0,
 from /usr/include/glm/gtx/io.hpp:24,
 from IWORKTransformationTest.cpp:13:
/usr/include/glm/gtx/norm.hpp:21:3: error: #error "GLM: GLM_GTX_norm is an 
experimental extension and may change in the future. Use #define 
GLM_ENABLE_EXPERIMENTAL before including it, if you really want to use it."
 # error "GLM: GLM_GTX_norm is an experimental extension and may change in the 
future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really 
want to use it."
   ^

Bug#888890: marked as done ([libtk-img] Undefined symbol: inflateValidate)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 09:20:27 +
with message-id 
and subject line Bug#90: fixed in libtk-img 1:1.4.7+dfsg-2
has caused the Debian Bug report #90,
regarding [libtk-img] Undefined symbol: inflateValidate
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.)


-- 
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtk-img
Version: 1:1.4.7+dfsg-1
Severity: serious
Affects: saods9

Dear maintainer,

The newly uploaded libtk-img cannot be loaded from within tk:

$ wish
% package require img::tiff
couldn't load file
"/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.7/libzlibtcl1.2.11.so":
/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.7/libzlibtcl1.2.11.so: undefined
symbol: inflateValidate
%

This affects saods9, which shows this as a failure in the last CI test

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/saods9/20180130_115901/log.gz

Cheers

Ole
--- End Message ---
--- Begin Message ---
Source: libtk-img
Source-Version: 1:1.4.7+dfsg-2

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated libtk-img package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 31 Jan 2018 11:46:35 +0300
Source: libtk-img
Binary: libtk-img libtk-img-dev libtk-img-doc
Architecture: source amd64 all
Version: 1:1.4.7+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Sergei Golovan 
Changed-By: Sergei Golovan 
Description:
 libtk-img  - Extended image format support for Tcl/Tk (runtime)
 libtk-img-dev - Extended image format support for Tcl/Tk (development files)
 libtk-img-doc - Extended image format support for Tcl/Tk (manual pages)
Closes: 90
Changes:
 libtk-img (1:1.4.7+dfsg-2) unstable; urgency=medium
 .
   * Downgrade the required zlib version to 1.2.8 (closes: #90).
   * Clarify descriptions for patches in debian/patches/*.
Checksums-Sha1:
 e855bbf94f35149a46e65789afc319b4da444336 2013 libtk-img_1.4.7+dfsg-2.dsc
 a236ec56f3c3025e7ad0e84cab9fc3117b2756cd 13360 
libtk-img_1.4.7+dfsg-2.debian.tar.xz
 0bcf30559f0828428e8ef8c00cd46f75868f0874 2088468 
libtk-img-dbgsym_1.4.7+dfsg-2_amd64.deb
 e6d8c997e9a377c4cbb42ae4487676747889668a 42532 
libtk-img-dev_1.4.7+dfsg-2_amd64.deb
 b6282cd5f636ce990b439727045f29ad941b5053 202904 
libtk-img-doc_1.4.7+dfsg-2_all.deb
 81b4f24c3e6f87f298b52a88ae6adc1170414c04 8166 
libtk-img_1.4.7+dfsg-2_amd64.buildinfo
 163ea211077b393c1e8d544f7e86fe802de0c581 134932 
libtk-img_1.4.7+dfsg-2_amd64.deb
Checksums-Sha256:
 684feef44ab12ffc4bfdd1bc3cb23b73ff716d631256521abb01bd336b1c8393 2013 
libtk-img_1.4.7+dfsg-2.dsc
 53522389879ee0b74b034504240df582d1114db28bca953539a3b8535fbdbab6 13360 
libtk-img_1.4.7+dfsg-2.debian.tar.xz
 b1bebe9257e7372282c3b26a03313f79daa88cf2115b7b4bf095a0abe44e9028 2088468 
libtk-img-dbgsym_1.4.7+dfsg-2_amd64.deb
 ff32e2a2effc93d038e6ac042218a28092c1405b2695598197fbd5d85a7e71f6 42532 
libtk-img-dev_1.4.7+dfsg-2_amd64.deb
 780a5c4fcf756e4c59cf08b7b9c6cf53a7eacde6eea0368b1ce6a0426645e52f 202904 
libtk-img-doc_1.4.7+dfsg-2_all.deb
 aabc6bd07a32f0f96da1e5703a3828c927876135dba56de5ecf594bc613f1560 8166 
libtk-img_1.4.7+dfsg-2_amd64.buildinfo
 890867d638c723eb447ac9580f077053c679b27b78d40a9ae0ae547fd468bff4 134932 
libtk-img_1.4.7+dfsg-2_amd64.deb
Files:
 95a7ef1e7212b3ee4623215c2a26d0fb 2013 libs optional libtk-img_1.4.7+dfsg-2.dsc
 af9211b851c8349b2cb9492ec7bd3875 13360 libs optional 
libtk-img_1.4.7+dfsg-2.debian.tar.xz
 6ebf30401a1d006213ee3895fa626086 2088468 debug optional 
libtk-img-dbgsym_1.4.7+dfsg-2_amd64.deb
 eb1a4385e420c32b42c03a1151bf0d20 42532 libdevel optional 
libtk-img-dev_1.4.7+dfsg-2_amd64.deb
 e6af50a714426297ac11aa300b83e0e4 202904 doc optional 
libtk-img-doc_1.4.7+dfsg-2_all.deb
 ca056fbe751a348840447acf809713b1 8166 libs optional 
libtk-img_1.4.7+dfsg-2_amd64.buildinfo
 

Processed: bug 888795 is forwarded to https://gitlab.inria.fr/solverstack/vite/issues/8

[Debian Bug Tracking System]

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

> forwarded 888795 https://gitlab.inria.fr/solverstack/vite/issues/8
Bug #888795 [vite] vite: FTBFS with glm 0.9.9~a2-1
Set Bug forwarded-to-address to 
'https://gitlab.inria.fr/solverstack/vite/issues/8'.
> thanks
Stopping processing here.

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

Bug#888930: libgltf FTBFS with libglm-dev 0.9.9~a2-1

[Adrian Bunk]

Source: libgltf
Version: 0.1.0-2
Severity: serious

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

...
checking epoxy/gl.h usability... yes
checking epoxy/gl.h presence... yes
checking for epoxy/gl.h... yes
checking glm/glm.hpp usability... yes
checking glm/glm.hpp presence... yes
checking for glm/glm.hpp... yes
checking glm/gtc/matrix_inverse.hpp usability... yes
checking glm/gtc/matrix_inverse.hpp presence... yes
checking for glm/gtc/matrix_inverse.hpp... yes
checking glm/gtc/matrix_transform.hpp usability... yes
checking glm/gtc/matrix_transform.hpp presence... yes
checking for glm/gtc/matrix_transform.hpp... yes
checking glm/gtc/quaternion.hpp usability... yes
checking glm/gtc/quaternion.hpp presence... yes
checking for glm/gtc/quaternion.hpp... yes
checking glm/gtc/type_ptr.hpp usability... yes
checking glm/gtc/type_ptr.hpp presence... yes
checking for glm/gtc/type_ptr.hpp... yes
checking glm/gtx/quaternion.hpp usability... no
checking glm/gtx/quaternion.hpp presence... no
checking for glm/gtx/quaternion.hpp... no
configure: error: Required glm headers not found. Install glm >= 0.9.0.0

Bug#888927: logstalgia FTBFS with libglm-dev 0.9.9~a2-1

[Adrian Bunk]

Source: logstalgia
Version: 1.1.0-1
Severity: serious

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

...
In file included from /usr/include/glm/gtx/norm.hpp:18:0,
 from src/core/vectors.h:37,
 from src/core/plane.h:31,
 from src/core/plane.cpp:28:
/usr/include/glm/gtx/quaternion.hpp:23:3: error: #error "GLM: 
GLM_GTX_quaternion is an experimental extension and may change in the future. 
Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really want to 
use it."
 # error "GLM: GLM_GTX_quaternion is an experimental extension and may change 
in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you 
really want to use it."
   ^

Bug#861515: unreproducibile

[Paolo Greppi]

Hi,

this seems now to have gone away by itself,
possibly thanks to the upgrade from nodejs 4.x to 8.x:
I don't see any error on the buildds, and it works without the patch on my x86 
VM here.

So I have reset the repo to the debian/1.0.0-2 tag, and moved the patch
to a separate branch (wip/paolog/skip_test) in case we need it later.

@Adam, if you have access to an armhf test machine, you could try yourself on 
that too.

I'll wait a bit more before I close this one and the upstream bug.

Paolo

Processed: tracking bug: breakages in reverse dependencies of node-source-map

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 46
Bug #888926 [node-source-map] tracking bug: breakages in reverse dependencies 
of node-source-map
888926 was not blocked by any bugs.
888926 was not blocking any bugs.
Added blocking bug(s) of 888926: 46

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

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

[Adrian Bunk]

Source: gource
Version: 0.47-1
Severity: serious

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

...
In file included from /usr/include/glm/gtx/norm.hpp:18:0,
 from src/core/vectors.h:37,
 from src/core/gl.h:27,
 from src/core/texture.h:34,
 from src/gource_settings.h:23,
 from src/user.h:21,
 from src/action.h:21,
 from src/action.cpp:18:
/usr/include/glm/gtx/quaternion.hpp:23:3: error: #error "GLM: 
GLM_GTX_quaternion is an experimental extension and may change in the future. 
Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really want to 
use it."
 # error "GLM: GLM_GTX_quaternion is an experimental extension and may change 
in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you 
really want to use it."
   ^

Bug#888925: libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt to use feature that was not turned on when netCDF was built

[Adrian Bunk]

Source: netcdf
Version: 1:4.6.0-2
Severity: serious
Control: affects -1 src:libminc

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

...
21/51 Test #21: minc_conversion ..***Failed0.02 sec
nccreate: filename "/tmp/minc-P1g2dy": NetCDF: Attempt to use feature that was 
not turned on when netCDF was built.
...
98% tests passed, 1 tests failed out of 51

Total Test time (real) =  65.14 sec

The following tests FAILED:
 21 - minc_conversion (Failed)
Errors while running CTest
Makefile:143: recipe for target 'test' failed
make[2]: *** [test] Error 8


I don't know which of the packages is at fault here,
the change that triggered it was the new netcdf.