Bug#850988: marked as done (autopkgtest: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 08:51:39 +0100
with message-id <20170128075139.4dsl77dahov5l...@xanadu.blop.info>
and subject line Re: Bug#850988: autopkgtest: FTBFS: Test failures
has caused the Debian Bug report #850988,
regarding autopkgtest: FTBFS: Test failures
to be marked as done.

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

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


-- 
850988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autopkgtest
Version: 4.2.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> autopkgtest: DBG: testbed command exited with code 100
> autopkgtest: DBG: BadPackageError Test dependencies are unsatisfiable. A 
> common reason is that your testbed is out of date with respect to the 
> archive, and you need to use a current testbed, or try "--setup-commands 
> ro-apt-update".
> autopkgtest: DBG: testbed stop
> autopkgtest: DBG: testbed close, scratch=/tmp/autopkgtest.AaVGT6
> autopkgtest: DBG: sending command to testbed: close
> autopkgtest: DBG: got reply from testbed: ok
> autopkgtest: DBG: sending command to testbed: quit
> autopkgtest [22:26:59]: ERROR: erroneous package: Test dependencies are 
> unsatisfiable. A common reason is that your testbed is out of date with 
> respect to the archive, and you need to use a current testbed, or try 
> "--setup-commands ro-apt-update".
> autopkgtest: DBG: testbed stop
> 
> 
> --
> Ran 52 tests in 99.473s
> 
> FAILED (failures=1, skipped=2)
> debian/rules:38: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/autopkgtest_4.2.2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On 27/01/17 at 22:23 +0100, Paul Gevers wrote:
> Hi Lucas,
> 
> > On Wed, 11 Jan 2017 at 19:48:38 +0100, Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> 
> On Mon, 16 Jan 2017 09:13:58 + Simon McVittie  wrote:
> > This appears to be because at the time of this test run, python3-wand
> > was uninstallable (#850815), and autopkgtest happens to use that package
> > in its tests (it downloads it from the already-configured apt source,
> > see #833503).
> 
> Does autopkgtest still fail rebuilding in your setup? If not, can you
> close this bug?

It doesn't, closing

Lucas--- End Message ---

Bug#849382: marked as done ([apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 08:53:16 +0100
with message-id <20170128075316.ppwoxozp6hu7h4g4@crossbow>
and subject line Re: Bug#849382: [apt] Every package on the system gets 
silently upgraded to backports. The result is severe system breakage, 
malfunctioning and data loss.
has caused the Debian Bug report #849382,
regarding [apt] Every package on the system gets silently upgraded to 
backports. The result is severe system breakage, malfunctioning and data loss.
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.)


-- 
849382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---


Package: apt
Version: 1.0.9.8.4
Severity: critical

--- Please enter the report below this line. ---
I use Debian 8 64bit with GNOME installed with standard install procedure from 
netinstall and using tasksel.
This occured to me the second time. First time was a year ago, I reinstalled 
Debian then and a year after this happens again.
Both occurences were on Debian 8, stable at the time. They were installed from 
the stable repo, I have logs of that.

I did not make any changes to my system lately and I generally do not tinker.
The only new packages that I installed during recent month were mktorrent, 
mediainfo
Backports repo was pinned to 100 according to apt-cache policy after system 
installation and now too, after the bug occured. I did not change pinning 
settings ever on this machine nor any other.



# TLDR
Every package on system gets updated to the version from backports silently 
(yes, I did click the upgrade button without checking if the right versions are 
installed of each package) even though backports repo is pinned to 100. This 
results in slow breakage of everything, max few days to make the machine 
useless to do work as usual.



# Description of what happened
Few days ago (it's worth noting that the machine was on for perhaps a week and 
package upgrades were performed) I noticed that hibernation stopped working on 
my system for no apparent reason. Every time after I hibernated the machine, 
upon booting it restarted and then at the next boot ext4 was performing fs 
check and repairing lots of errors.
The next thing I noticed was that disk IO became extremely slow. It's the most 
stable consumer SSD available at the moment, Intel 730. It performed no problem 
before, but now if I move 100 or even 50 files, bunch of kilobytes in size 
(together 1MB) the operation can take a minute or even more. No noticeable disk 
problems with playing 1080p videos or browsing the web. Another system on this 
machine (Windows) doesn't seem to exhibit similar issues.
Next thing is a message asking if software upgrades should be installed when I 
click the power off button in GNOME. Next boot it installs them, but system 
crashes. Then when I boot again, ext4 check and repair and lots of errors. BTW 
While writing this, I clicked that GNOME power button and canceled, clicked 
again, window didn't appear and the system turned itself off.
Evolution email client started showing folders I disabled and some errors about 
cache (missing or something).
Firefox signed me out from every single website.
I became worried about what's happening with my machine, tried apt-get update 
and upgrade manually (I normally use apt-config-auto-update), that's what 
upgrade says "The following packages have been kept back: linux-image-amd64". 
So it occured to me that it may be the same bug that killed my machine a year 
ago, I runned "dpkg -l  |awk '/^ii/ && $3 ~ /bpo[6-8]/ {print $2}'" to see what 
backports are installed, and yes, every package that has a backport version 
available was switched to that version silently and apt-cache policy still says 
backports are pinned to 100! This is exactly what happened a year ago.
The only sane fix for this machine now is a complete reinstall.
Worth noting that a year ago this made dpkg unusable, ie. no package could be 
installed or upgraded because of dependency breakage.



# List of backports installed.
Before that the only backports I had on my system were: apt-config-auto-update 
(installed it with apt-get -t jessie-backports install), python-idna 
(automatically installed with torbrowser-launcher), python-axolotl (installed 
with apt-get install python-axolotl).

Now "dpkg -l  |awk '/^ii/ && $3 ~ /bpo[6-8]/ {print $2}'" shows this:
apt-config-auto-update
autopoint
calibre
calibre-bin
dh-python
dmidecode
e2fslibs:amd64
e2fsprogs
exfat-fuse
exfat-utils
ffmpeg
firmware-realtek
fonts-opensymbol
geoip-database
gettext
gettext-base

Processed: severity of 836241 is serious

[Debian Bug Tracking System]

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

> severity 836241 serious
Bug #836241 [plasma-workspace] plasma-workspace: Digital clock widget wants 
qml-module-org-kde-kholidays
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: Bug#852840: xsane: FTBFS against libsane-dev 1.0.25-3 - sane-config not found

[Debian Bug Tracking System]

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

> tags 852840 + pending
Bug #852840 [xsane] xsane: FTBFS against libsane-dev 1.0.25-3 - sane-config not 
found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852840: xsane: FTBFS against libsane-dev 1.0.25-3 - sane-config not found

[Jörg Frings-Fürst]

tags 852840 + pending
thanks


Hello Andreas,

thanks for your bug report and your patch!

I have uploaded a new releases to mentors. My mentor is informed.


Have a nice weekend.

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

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

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

Threema: SYR8SJXB

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

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


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

Bug#852822: marked as done (signing buildinfo by default breaks compatibility)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 06:33:41 +
with message-id 
and subject line Bug#852822: fixed in dpkg 1.18.20
has caused the Debian Bug report #852822,
regarding signing buildinfo by default breaks compatibility
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.)


-- 
852822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.18.19
Severity: serious

>From the changelog:

   * Add support for signed .buildinfo files to dpkg-buildpackage. Add new
 -ui and --unsigned-buildinfo options. Closes: #843925

This suggests that buildinfo files will now be signed by default.  The
manpage and my ad-hoc tests agree.

Previously runes like
  dpkg-buildpackage -uc -b
  dpkg-buildpackage -F -uc -us
were known and recommended as ways to build packages locally.

Now these runes would have to be
  dpkg-buildpackage -uc -b -ui
  dpkg-buildpackage -F -uc -us -ui

But those runes are not supported by dpkg in jessie.

This means that there is no longer a rune for `build this package but
do not sign anything' that will work both before and after this
change.

IMO that is a serious regression.

IMO the correct fix is to, by default, sign the buildinfo iff the
.changes are being signed.  That way -uc is sufficient.

Thanks for your attention.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.18.20

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Jan 2017 06:32:53 +0100
Source: dpkg
Binary: dpkg libdpkg-dev dpkg-dev libdpkg-perl dselect
Architecture: source
Version: 1.18.20
Distribution: unstable
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Description:
 dpkg   - Debian package management system
 dpkg-dev   - Debian package development tools
 dselect- Debian package management front-end
 libdpkg-dev - Debian package management static library
 libdpkg-perl - Dpkg perl modules
Closes: 852822
Changes:
 dpkg (1.18.20) unstable; urgency=medium
 .
   [ Guillem Jover ]
   * Add a new --no-sign option to dpkg-buildpackage, to make it possible to
 disable all signing in a future-proof way.
   * Make dpkg-buildpackage --unsigned-changes not sign .buildinfo either.
 This breaks the expectations of users and tools, because there was no
 way previously to request no signing at all. Closes: #852822
   * Perl modules:
 - Mask the machine bits for SH and MIPS in the ELF processor flags in
   Dpkg::Shlibs::Objdump. These do not define the ABI, and make the
   objects not match when they should, when looking for shared libraries
   from dpkg-shlibdeps.
 - Encode the ELF ABI as a big-endian byte stream, so that decoding for
   output gives meaningful results.
 - Disable the NFS-unsafe warning on Linux, as using flock() on NFS has
   been safe for some time now. Addresses: #677865 (on Linux)
   * Documentation:
 - Document the Built-For-Profile field in deb-changes(5).
 .
   [ Updated scripts translations ]
   * German (Helge Kreutzmann).
 .
   [ Updated man pages translations ]
   * German (Helge Kreutzmann).
Checksums-Sha1:
 19e4d79a084249f0d081692ec283221007489b9d 2032 dpkg_1.18.20.dsc
 abd47591d9f10dc898d9de2d27870cc4482aefcf 4518520 dpkg_1.18.20.tar.xz
 cf0625761a7e02c377b3689d115a574dd56d94ad 7301 dpkg_1.18.20_amd64.buildinfo
Checksums-Sha256:
 86ca96c38c17b4b53fe6dca09be66c3b54bb71681603124d9cd7ccbfb46ae1c7 2032 
dpkg_1.18.20.dsc
 b3f7e6ceeb4a6e0276988abad0ba05cba64f34db55e4f96ca811327880e7c7a4 4518520 

Bug#852850: marked as done (hilive: FTBFS (dh_auto_configure fails))

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 06:33:46 +
with message-id 
and subject line Bug#852850: fixed in hilive 0.3-2
has caused the Debian Bug report #852850,
regarding hilive: FTBFS (dh_auto_configure fails)
to be marked as done.

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

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


-- 
852850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hilive
Version: 0.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_testdir -a
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 6.2.1
-- The CXX compiler identification is GNU 6.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

Feature record: CXX_FEATURE:0cxx_delegating_constructors
Feature record: CXX_FEATURE:0cxx_deleted_functions
Feature record: CXX_FEATURE:0cxx_digit_separators
Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
Feature record: CXX_FEATURE:0cxx_explicit_conversions
Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
Feature record: CXX_FEATURE:0cxx_extern_templates
Feature record: CXX_FEATURE:0cxx_final
Feature record: CXX_FEATURE:0cxx_func_identifier
Feature record: CXX_FEATURE:0cxx_generalized_initializers
Feature record: CXX_FEATURE:0cxx_generic_lambdas
Feature record: CXX_FEATURE:0cxx_inheriting_constructors
Feature record: CXX_FEATURE:0cxx_inline_namespaces
Feature record: CXX_FEATURE:0cxx_lambdas
Feature record: CXX_FEATURE:0cxx_lambda_init_captures
Feature record: CXX_FEATURE:0cxx_local_type_template_args
Feature record: CXX_FEATURE:0cxx_long_long_type
Feature record: CXX_FEATURE:0cxx_noexcept
Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
Feature record: CXX_FEATURE:0cxx_nullptr
Feature record: CXX_FEATURE:0cxx_override
Feature record: CXX_FEATURE:0cxx_range_for
Feature record: CXX_FEATURE:0cxx_raw_string_literals
Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
Feature record: CXX_FEATURE:0cxx_return_type_deduction
Feature record: CXX_FEATURE:0cxx_right_angle_brackets
Feature record: CXX_FEATURE:0cxx_rvalue_references
Feature record: CXX_FEATURE:0cxx_sizeof_member
Feature record: CXX_FEATURE:0cxx_static_assert
Feature record: CXX_FEATURE:0cxx_strong_enums
Feature record: CXX_FEATURE:1cxx_template_template_parameters
Feature record: CXX_FEATURE:0cxx_thread_local
Feature record: CXX_FEATURE:0cxx_trailing_return_types
Feature record: CXX_FEATURE:0cxx_unicode_literals
Feature record: CXX_FEATURE:0cxx_uniform_initialization
Feature record: CXX_FEATURE:0cxx_unrestricted_unions
Feature record: CXX_FEATURE:0cxx_user_literals
Feature record: CXX_FEATURE:0cxx_variable_templates
Feature record: CXX_FEATURE:0cxx_variadic_macros
Feature record: CXX_FEATURE:0cxx_variadic_templates
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
debian/rules:10: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


A similar failure happens here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: hilive
Source-Version: 0.3-2

We believe that the bug you reported is fixed in the latest version of
hilive, 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 

Processed: Bug#852822 in package dpkg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 852822 pending
Bug #852822 [dpkg-dev] signing buildinfo by default breaks compatibility
Added tag(s) pending.

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

Bug#852822: in package dpkg marked as pending

[Guillem Jover]

Control: tag 852822 pending

Hi!

Bug #852822 in package dpkg reported by you has been fixed in
the dpkg/dpkg.git Git repository. You can see the changelog below, and
you can check the diff of the fix at:

https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=5124722

---
commit 5124722df07abb3f440221c28bc578ed8286
Author: Guillem Jover 
Date:   Sat Jan 28 00:04:33 2017 +0100

dpkg-buildpackage: Make --unsigned-changes not sign .buildinfo either

There was no option to disable signing globally, so many users and
tools rely on the two existing options to disable it. But with the
introduction of signed .buildinfo files, there is no way for old tools
to request the right thing.

Abuse --unsigned-changes to mean not signing .buildinfo either.

Closes: #852822

diff --git a/debian/changelog b/debian/changelog
index 9363b7e..919cc8c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,9 @@ dpkg (1.18.20) UNRELEASED; urgency=medium
   [ Guillem Jover ]
   * Add a new --no-sign option to dpkg-buildpackage, to make it possible to
 disable all signing in a future-proof way.
+  * Make dpkg-buildpackage --unsigned-changes not sign .buildinfo either.
+This breaks the expectations of users and tools, because there was no
+way previously to request no signing at all. Closes: #852822
   * Perl modules:
 - Mask the machine bits for SH and MIPS in the ELF processor flags in
   Dpkg::Shlibs::Objdump. These do not define the ABI, and make the

Processed: emacs-goodies-el: diff for NMU version 36.3+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 851605 + patch
Bug #851605 [emacs-goodies-el] emacs-goodies-el: fails to upgrade lenny -> 
squeeze -> wheezy -> jessie
Added tag(s) patch.
> tags 851605 + pending
Bug #851605 [emacs-goodies-el] emacs-goodies-el: fails to upgrade lenny -> 
squeeze -> wheezy -> jessie
Added tag(s) pending.

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

Bug#851605: emacs-goodies-el: diff for NMU version 36.3+nmu1

[Sean Whitton]

Control: tags 851605 + patch
Control: tags 851605 + pending

Dear maintainer,

I've prepared an NMU for emacs-goodies-el (versioned as 36.3+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should delay
it longer.

Regards.

-- 
Sean Whitton
diff -Nru emacs-goodies-el-36.3/debian/changelog emacs-goodies-el-36.3+nmu1/debian/changelog
--- emacs-goodies-el-36.3/debian/changelog	2016-11-21 13:20:03.0 -0700
+++ emacs-goodies-el-36.3+nmu1/debian/changelog	2017-01-27 22:15:49.0 -0700
@@ -1,3 +1,13 @@
+emacs-goodies-el (36.3+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * emacs-goodies-el:
+  - Bug fix: "fails to upgrade lenny -> squeeze -> wheezy -> jessie",
+thanks to Andreas Beckmann (Closes: #851605).  Skip byte-compilation
+for minibuffer-complete-cycle.el on emacs22.
+
+ -- Sean Whitton   Fri, 27 Jan 2017 22:15:49 -0700
+
 emacs-goodies-el (36.3) unstable; urgency=high
 
   * emacs-goodies-el:
diff -Nru emacs-goodies-el-36.3/debian/emacs-goodies-el.emacsen-install.in emacs-goodies-el-36.3+nmu1/debian/emacs-goodies-el.emacsen-install.in
--- emacs-goodies-el-36.3/debian/emacs-goodies-el.emacsen-install.in	2016-11-21 13:17:53.0 -0700
+++ emacs-goodies-el-36.3+nmu1/debian/emacs-goodies-el.emacsen-install.in	2017-01-27 19:27:51.0 -0700
@@ -21,6 +21,7 @@
 EXCLUDED_xemacs21="csv-mode.el minibuf-electric.el pp-c-l.el tabbar.el todoo.el rfcview.el upstart-mode.el maplev.el button-lock.el"
 #EXCLUDED_emacs_snapshot="cua.el cfengine.el ibuffer.el ido.el newsticker.el table.el "
 #EXCLUDED_emacs22="cua.el cfengine.el ibuffer.el ido.el newsticker.el table.el "
+EXCLUDED_emacs22="minibuffer-complete-cycle.el"
 EXCLUDED_emacs23="minibuffer-complete-cycle.el"
 
 # Skip byte-compilation here if necessary:


signature.asc
Description: PGP signature

Bug#852822: signing buildinfo by default breaks compatibility

[Guillem Jover]

Hi!

On Fri, 2017-01-27 at 15:58:32 +, Ian Jackson wrote:
> Package: dpkg-dev
> Version: 1.18.19
> Severity: serious

> >From the changelog:
> 
>* Add support for signed .buildinfo files to dpkg-buildpackage. Add new
>  -ui and --unsigned-buildinfo options. Closes: #843925
> 
> This suggests that buildinfo files will now be signed by default.  The
> manpage and my ad-hoc tests agree.
> 
> Previously runes like
>   dpkg-buildpackage -uc -b
>   dpkg-buildpackage -F -uc -us
> were known and recommended as ways to build packages locally.
> 
> Now these runes would have to be
>   dpkg-buildpackage -uc -b -ui
>   dpkg-buildpackage -F -uc -us -ui

I actually realized this while I was waking up today, and brought it
up on IRC. My biggest concern was the buildd network, because that
is explicitly not signing files from inside the chroots. But due to
gnupg not being installed anymore by default (and very few packages
at least directly Build-Depending on it), and the buildd chroots not
containing any home directory, the signing is not performed anyway.
So in that sense the upload was "safe" from the major fallout. And I
was then planning on fixing this for .20, after the testing migration
as it indeed breaks user's and other tools expectations.

> IMO the correct fix is to, by default, sign the buildinfo iff the
> .changes are being signed.  That way -uc is sufficient.

Yes, that's also the conclusion I had arrived at noon, even though
that makes the semantics suck a bit, but oh well. The other thing I
was planning (and I've done locally), is to add a new --no-sign
option which will make this kind of thing future-proof.

Thanks,
Guillem

Bug#852867: icedove: debuild fails because mozilla build system requires SHELL env var set

[Thomas Nyberg]

Package: icedove
Version: 1:45.6.0-1~deb8u1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

   * What led up to the situation?

I tried building the package to investigate some segfaults, but was unable to
build it with debuild.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I exported `SHELL=/bin/bash` in debian/rules.

   * What was the outcome of this action?

It fixed the problem.

More info:

Mozilla's build system requires the SHELL environment variable to be
set, but it is cleared in the debian build system. This sets the
variable again. See here for discussion:

   https://lists.debian.org/debian-devel/2017/01/msg00645.html

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

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

Versions of packages icedove depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3+deb8u1
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u6
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3+deb8u1
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpixman-1-0 0.32.6-3
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  psmisc22.21-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
pn  iceowl-extension  

Versions of packages icedove suggests:
ii  fonts-lyx 2.1.2-2
ii  libgssapi-krb5-2  1.12.1+dfsg-19+deb8u2

-- no debconf information
Export SHELL env var for Mozilla build system

Mozilla's build system requires the SHELL environment variable to be
set, but it is cleared in the debian build system. This sets the
variable again. See here for discussion:

   https://lists.debian.org/debian-devel/2017/01/msg00645.html
--- a/debian/rules
+++ b/debian/rules
@@ -4,6 +4,13 @@
 # Uncomment this to turn on verbose mode.
 # export DH_VERBOSE=1
 
+# Mozilla's build system requires the SHELL environment variable to be set, but
+# it is cleared in the debian build system. This sets the variable again.
+# See here for discussion:
+#
+#   https://lists.debian.org/debian-devel/2017/01/msg00645.html
+export SHELL=/bin/bash
+
 # checking the release type, if $(RELEASE)=UNRELEASED we won't build
 # the icedove-dbg package
 RELEASE := $(shell head -1 debian/changelog | cut -d" " -f3 | tr -d ';')

Processed: severity of 852208 is serious

[Debian Bug Tracking System]

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

> severity 852208 serious
Bug #852208 [isso] breaks with newer versions of html5lib
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#852709: [debian-mysql] Bug#852709: Patch

[James Clarke]

> On 27 Jan 2017, at 21:07, Otto Kekäläinen  wrote:
> 
> I've now built and uploaded 10.1.21-5.
> 
> Post upload I diffed the filelists (public at
> http://labs.seravo.fi/~otto/debian/mariadb-10.1-sid-amd64/?C=M;O=D)
> and I noticed my amd64 sid pbuilder is not generating
> mariadb-plugin-tokudb anymore...
> 
> James: can you please review your commits today and track down where
> the mistake was? Now we have the problem at hand, that if I re-upload
> a version where mariadb-plugin-tokudb is back again, then DAK will
> detect a new package and the whole mariadb-10.1 will need to go though
> the NEW queue again..
> 
> 
> $ diff -u filelist-2db349e.log filelist-d237cd1.log
> --- filelist-2db349e.log 2017-01-25 16:03:08.0 +0200
> +++ filelist-d237cd1.log 2017-01-27 22:02:01.0 +0200
> @@ -177,8 +177,8 @@
> drwxr-xr-x root/root ./usr/lib/
> drwxr-xr-x root/root ./usr/lib/debug/
> drwxr-xr-x root/root ./usr/lib/debug/.build-id/
> -drwxr-xr-x root/root ./usr/lib/debug/.build-id/80/
> --rw-r--r-- root/root
> ./usr/lib/debug/.build-id/80/7640a5d6deb080854ee8a35ee5156f876be14c.debug
> +drwxr-xr-x root/root ./usr/lib/debug/.build-id/e4/
> +-rw-r--r-- root/root
> ./usr/lib/debug/.build-id/e4/1ba3aae4ba6b95b07e7f31c1b001fa1fddcdac.debug
> drwxr-xr-x root/root ./usr/share/
> drwxr-xr-x root/root ./usr/share/doc/
> lrwxrwxrwx root/root ./usr/share/doc/libmariadbd18-dbgsym
> @@ -529,45 +529,6 @@
> drwxr-xr-x root/root ./usr/share/doc/
> lrwxrwxrwx root/root ./usr/share/doc/mariadb-plugin-spider-dbgsym
> 
> -mariadb-plugin-tokudb
> -drwxr-xr-x root/root ./
> -drwxr-xr-x root/root ./etc/
> -drwxr-xr-x root/root ./etc/mysql/
> -drwxr-xr-x root/root ./etc/mysql/mariadb.conf.d/
> --rw-r--r-- root/root ./etc/mysql/mariadb.conf.d/tokudb.cnf
> -drwxr-xr-x root/root ./usr/
> -drwxr-xr-x root/root ./usr/bin/
> --rwxr-xr-x root/root ./usr/bin/tokuftdump
> -drwxr-xr-x root/root ./usr/lib/
> -drwxr-xr-x root/root ./usr/lib/x86_64-linux-gnu/
> -drwxr-xr-x root/root ./usr/lib/x86_64-linux-gnu/mariadb18/
> -drwxr-xr-x root/root ./usr/lib/x86_64-linux-gnu/mariadb18/plugin/
> --rw-r--r-- root/root ./usr/lib/x86_64-linux-gnu/mariadb18/plugin/ha_tokudb.so
> -drwxr-xr-x root/root ./usr/share/
> -drwxr-xr-x root/root ./usr/share/doc/
> -drwxr-xr-x root/root ./usr/share/doc/mariadb-plugin-tokudb/
> --rw-r--r-- root/root 
> ./usr/share/doc/mariadb-plugin-tokudb/changelog.Debian.gz
> --rw-r--r-- root/root ./usr/share/doc/mariadb-plugin-tokudb/copyright
> -drwxr-xr-x root/root ./usr/share/doc/mariadb-plugin-tokudb/README.md/
> --rw-r--r-- root/root
> ./usr/share/doc/mariadb-plugin-tokudb/README.md/README.md.gz
> -drwxr-xr-x root/root ./usr/share/man/
> -drwxr-xr-x root/root ./usr/share/man/man1/
> --rw-r--r-- root/root ./usr/share/man/man1/tokuftdump.1.gz
> -
> -mariadb-plugin-tokudb-dbgsym
> -drwxr-xr-x root/root ./
> -drwxr-xr-x root/root ./usr/
> -drwxr-xr-x root/root ./usr/lib/
> -drwxr-xr-x root/root ./usr/lib/debug/
> -drwxr-xr-x root/root ./usr/lib/debug/.build-id/
> -drwxr-xr-x root/root ./usr/lib/debug/.build-id/d9/
> --rw-r--r-- root/root
> ./usr/lib/debug/.build-id/d9/72c47905eb64c2b1755e086ae77db8ffa2b004.debug
> -drwxr-xr-x root/root ./usr/lib/debug/.build-id/fd/
> --rw-r--r-- root/root
> ./usr/lib/debug/.build-id/fd/7bb08c929158052c7eb0428c7180568374eb29.debug
> -drwxr-xr-x root/root ./usr/share/
> -drwxr-xr-x root/root ./usr/share/doc/
> -lrwxrwxrwx root/root ./usr/share/doc/mariadb-plugin-tokudb-dbgsym
> -
> mariadb-server-10.1
> drwxr-xr-x root/root ./
> drwxr-xr-x root/root ./etc/
> @@ -678,6 +639,9 @@
> -rw-r--r-- root/root ./usr/share/man/man1/aria_ftdump.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/aria_pack.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/aria_read_log.1.gz
> +-rw-r--r-- root/root ./usr/share/man/man1/galera_new_cluster.1.gz
> +-rw-r--r-- root/root ./usr/share/man/man1/galera_recovery.1.gz
> +-rw-r--r-- root/root ./usr/share/man/man1/mariadb-service-convert.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/msql2mysql.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/myisamchk.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/myisam_ftdump.1.gz
> @@ -688,6 +652,7 @@
> -rw-r--r-- root/root ./usr/share/man/man1/mysql_convert_table_format.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/mysqld_multi.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/mysqld_safe.1.gz
> +-rw-r--r-- root/root ./usr/share/man/man1/mysqld_safe_helper.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/mysqlhotcopy.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/mysql_install_db.1.gz
> -rw-r--r-- root/root ./usr/share/man/man1/mysql_plugin.1.gz
> @@ -921,8 +886,8 @@
> -rw-r--r-- root/root
> ./usr/lib/debug/.build-id/09/df4fe8db8d9dbf6167dbca178e9e6fc785891c.debug
> drwxr-xr-x root/root ./usr/lib/debug/.build-id/33/
> -rw-r--r-- root/root
> 

Bug#852850: [Debian-med-packaging] Bug#852850: hilive: FTBFS (dh_auto_configure fails)

[Sascha Steinbiss]

Hi Andreas,

> ...
> CMake Error at CMakeLists.txt:37 (find_package):
>  By not providing "FindSeqAn.cmake" in CMAKE_MODULE_PATH this project has
>  asked CMake to find a package configuration file provided by "SeqAn", but
>  CMake did not find one.
> 
>  Could not find a package configuration file provided by "SeqAn" with any of
>  the following names:
> 
>SeqAnConfig.cmake
>seqan-config.cmake
> 
>  Add the installation prefix of "SeqAn" to CMAKE_PREFIX_PATH or set
>  "SeqAn_DIR" to a directory containing one of the above files.  If "SeqAn"
>  provides a separate development package or SDK, be sure it has been
>  installed.
> 
> ...
> 
> 
> From libseqan-dev 2.2.0+dfsg-5 to 2.3.1+dfsg-3 the seqan input files
> have completely changed.  Any hint from somebody with more cmake
> experience than I have whether I can / should fix hilive to adapt
> properly or whether libseqan-dev needs to be adapted?


https://anonscm.debian.org/cgit/debian-med/lambda-align.git/diff/debian/patches/set-seqan-cmake-dir.patch
 seems to have solved that problem for me in lambda-align.

Cheers
Sascha


signature.asc
Description: Message signed with OpenPGP

Bug#851790: marked as done (installation-reports: DNS not working)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 23:33:31 +
with message-id <e1cxg1l-0003cg...@fasolo.debian.org>
and subject line Bug#851790: fixed in debian-installer 20170127
has caused the Debian Bug report #851790,
regarding installation-reports: DNS not working
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.)


-- 
851790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

The current installer, with the new 4.9 kernel, is unable to resolve
domains, so is quite seriously broken.

This was noted during install on an arm64 gigabyte MP30-AR1
desktop/server, when choose-mirror failed, but it soon became clear
that DNS was not working.

Testing on an x86 VM with the same daily image (18th Jan 2017) found
the same problem. Going back to the rc1 installer image (4.8 kernel)
it works OK.

Tests showed that the network came up fine and things are pingable by IP, but 
not name:
# ping wookware.org   
ping: bad address 'wookware.org'
# ping 93.93.131.118
PING 93.93.131.118 (93.93.131.118): 56 data bytes
64 bytes from 93.93.131.118: seq=0 ttl=50 time=19.892 ms

similarly the failing line from the choose-mirror log works if an address is 
inserted:
Jan 18 17:04:11 choose-mirror[31201]: DEBUG: command: wget --no-verbose 
http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | grep 
-E '^(Suite|Codename|Architectures):'   

Jan 18 17:04:11 choose-mirror[31201]: WARNING **: mirror does not support the 
specified release (stretch) 

# wget --no-verbose 
http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | grep 
-E '^(Suite|Codename|Architectures):'
wget: unable to resolve host address 'debian-mirror.cambridge.arm.com'

# wget --no-verbose http://10.1.194.51/debian/dists/stretch/Release -O - | gre
p -E '^(Suite|Codename|Architectures):'
Suite: testing
Codename: stretch
Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
2017-01-18 17:47:12 URL:http://10.1.194.51/debian/dists/stretch/Release 
[177979/177979] -> "-" [1]

resolv.conf is as expected:
search cambridge.arm.com
nameserver 10.1.2.24
nameserver 10.1.2.23

(adding nameserver 8.8.8.8 makes no difference)

Watching packets go by when doing a VM install it is clear that the
local DNS server returns the correct response, but this is being ignored
or lost by the D-I initrd.

attached is an strace of strace ping wookware.org > /tmp/tracelog 2>&1

That gets a response from the server OK, but then goes on to ask the
other one. a working strace then uses the provided IP address. So
there is nothing obviously going wrong there.

-- Package-specific info:

Boot method: USB
Image version: 
http://gemmei.acc.umu.se/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
Date: 

Machine: Gigabyte MP30-AR1, (and x86 VM)
Partitions: (default guided LVM, with separate /home chosen)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[E]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Worked as expected until DNS needed

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

removed automatic info as this report written on different machine fro install.
execve("/bin/ping", ["ping", "wookware.org"], [/* 14 vars */]) = 0
brk(NULL)   = 0xc9893000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x86677000
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
o

Bug#847345: marked as done (libx11-6: the locale is not supported by Xlib, continuing without locale support)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 23:33:44 +
with message-id 
and subject line Bug#847345: fixed in libx11 2:1.6.4-3
has caused the Debian Bug report #847345,
regarding libx11-6: the locale is not supported by Xlib, continuing without 
locale support
to be marked as done.

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

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


-- 
847345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libx11-6
Version: 2:1.6.4-2
Severity: normal

Dear Maintainer,
after upgrade from 2:1.6.3-1 to 2:1.6.4-2 the $subj warning is displayed
and I can't enter national letters into rxvt-unicode terminal.

  zito@bobek:~$ urxvt
  urxvt: the locale is not supported by Xlib, continuing without locale support.

I did downgrade back to 2:1.6.3-1 and the problem is gone.

My locale settings:

  zito@bobek:~$ cat /etc/default/locale 
  LANG=en_US.UTF-8
  LC_CTYPE="cs_CZ.UTF-8"
  LC_COLLATE="C"

  zito@bobek:~$ locale -a
  C
  C.UTF-8
  POSIX
  cs_CZ
  cs_CZ.iso88592
  cs_CZ.utf8
  czech
  en_US
  en_US.iso88591
  en_US.utf8

Thanks
Cheers
-- 
Zito


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

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

Versions of packages libx11-6 depends on:
ii  libc62.24-8
ii  libx11-data  2:1.6.4-2
ii  libxcb1  1.12-1

libx11-6 recommends no packages.

libx11-6 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libx11
Source-Version: 2:1.6.4-3

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated libx11 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Jan 2017 00:06:50 +0100
Source: libx11
Binary: libx11-6 libx11-6-udeb libx11-data libx11-dev libx11-xcb1 
libx11-xcb-dev libx11-doc
Architecture: source
Version: 2:1.6.4-3
Distribution: unstable
Urgency: high
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 libx11-6   - X11 client-side library
 libx11-6-udeb - X11 client-side library (udeb)
 libx11-data - X11 client-side library
 libx11-dev - X11 client-side library (development headers)
 libx11-doc - X11 client-side library (development documentation)
 libx11-xcb-dev - Xlib/XCB interface library (development headers)
 libx11-xcb1 - Xlib/XCB interface library
Closes: 847345
Changes:
 libx11 (2:1.6.4-3) unstable; urgency=high
 .
   [ Emilio Pozuelo Monfort ]
   * debian/libx11-6.symbols: use arch-bits=64 rather than listing all
 64-bits architectures, which is not future-proof.
 .
   [ Julien Cristau ]
   * Fix two regressions introduced in 2:1.6.4-1:
 + Fix wrong Xfree in XListFonts failure path
 + Revert cs_CZ.UTF-8 XLC_LOCALE to en_US.UTF-8 (closes: #847345)
   * Build-depend on dpkg-dev 1.18.0 for arch-bits support in dpkg-gensymbols.
Checksums-Sha1:
 1b739a8c7c6a39788b2a1c3bcc48127aeb506459 2397 libx11_1.6.4-3.dsc
 484fc393abddf1091f31c844849ed5537cf1de3e 41366 libx11_1.6.4-3.diff.gz
Checksums-Sha256:
 4c5d6add2ba969067ca111c827ae94264e4c22776e22f318d264545dc1c6a300 2397 
libx11_1.6.4-3.dsc
 2c936827bca63eaf5b66683bdcd0ecf013d152c35439f792475db85c5c2338fd 41366 
libx11_1.6.4-3.diff.gz
Files:
 5d2abe6040553a736b1599b9cb5275f6 2397 x11 optional libx11_1.6.4-3.dsc
 fae6d856dcc2f5cd576f2b1edcfaf5fb 41366 x11 optional libx11_1.6.4-3.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAliL1XkACgkQnbAjVVb4
z63GLA//Ry5envDgKOfU62ou1C8TyfbuIE2cntYsI8UXfa48w2lsXu0iOv+MKGV7
/Af7T+RLZbZT+zUeMSLm1R4OHPJ7l7MXXsLtNpxM/ADfaXi3maKrwYqpi2UIFZhn
XEShNa9hDgFQ0A8ErLs12IidhymhtIC9D8LiRBaUmPhTNCNCb+KYtBoMlRvg31mo

Bug#852850: hilive: FTBFS (dh_auto_configure fails)

[Andreas Tille]

Hi,

the real build error of hilive is

...
CMake Error at CMakeLists.txt:37 (find_package):
  By not providing "FindSeqAn.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "SeqAn", but
  CMake did not find one.

  Could not find a package configuration file provided by "SeqAn" with any of
  the following names:

SeqAnConfig.cmake
seqan-config.cmake

  Add the installation prefix of "SeqAn" to CMAKE_PREFIX_PATH or set
  "SeqAn_DIR" to a directory containing one of the above files.  If "SeqAn"
  provides a separate development package or SDK, be sure it has been
  installed.

...


>From libseqan-dev 2.2.0+dfsg-5 to 2.3.1+dfsg-3 the seqan input files
have completely changed.  Any hint from somebody with more cmake
experience than I have whether I can / should fix hilive to adapt
properly or whether libseqan-dev needs to be adapted?

Kind regards and thanks for any tip

 Andreas.

-- 
http://fam-tille.de

Bug#852851: marked as done (mknbi: FTBFS (undefined reference to _GLOBAL_OFFSET_TABLE_'))

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 22:49:30 +
with message-id 
and subject line Bug#852851: fixed in mknbi 1.4.4-13
has caused the Debian Bug report #852851,
regarding mknbi: FTBFS (undefined reference to _GLOBAL_OFFSET_TABLE_')
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.)


-- 
852851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mknbi
Version: 1.4.4-12
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -B"
but it failed:


[...]
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer 
-fgnu89-inline -fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format 
-Wno-unused -DVERSION=\"1.4.4\" -c printf.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer 
-fgnu89-inline -fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format 
-Wno-unused -DVERSION=\"1.4.4\" -c string.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -E -DRELOC=0x92800  start32.S | as --32 -o start32@0x92800.o
ld -N -Ttext 0x92800 -e _start --oformat binary -m elf_i386 -o 
first32@0x92800.linux start32@0x92800.o first32.o memsizes.o printf.o string.o
first32.o: In function `gettag':
first32.c:(.text+0x8): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `copy_nonws':
first32.c:(.text+0xcc): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `discard_arg':
first32.c:(.text+0x128): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `outtag':
first32.c:(.text+0x169): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `putchar':
first32.c:(.text+0x1dc): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o:first32.c:(.text+0x213): more undefined references to 
`_GLOBAL_OFFSET_TABLE_' follow
Makefile:99: recipe for target 'first32@0x92800.linux' failed
make[2]: *** [first32@0x92800.linux] Error 1
rm start32@0x92800.o
make[2]: Leaving directory '/<>'
debian/rules:18: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


It also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/mknbi.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: mknbi
Source-Version: 1.4.4-13

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Jan 2017 00:23:07 +0200
Source: mknbi
Binary: mknbi
Architecture: source
Version: 1.4.4-13
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 mknbi  - Create tagged images for Etherboot or Netboot
Closes: 852851
Changes:
 mknbi (1.4.4-13) unstable; urgency=medium
 .
   * QA upload.
   * Add patch from Steve Beattie to fix PIE FTBFS. (Closes: #852851)
Checksums-Sha1:
 29c97b156e455164a514c0ef7c2af0bed902597b 1881 mknbi_1.4.4-13.dsc
 e097a3f19dd1e9e14765f827bed94bd0a98de031 5754 mknbi_1.4.4-13.debian.tar.gz
Checksums-Sha256:
 648650f3fa76c1eda71d36c28d330e7b38056c8363fff93c8d1417a5c424067f 1881 
mknbi_1.4.4-13.dsc
 4a2f261a29b28f2a35eec5b80709f0d26706e6dfe8ba832c8f8786229d9c827a 5754 
mknbi_1.4.4-13.debian.tar.gz
Files:
 

Bug#852850: hilive: FTBFS (dh_auto_configure fails)

[Andreas Tille]

Hi Santiago,

I suspect this is due to the fact that libseqan-dev 2.3.1+dfsg 
installs the cmake files into wrong directory.  I'll verify this
assumption and reassign.

Thanks for your thorough QA work

Andreas.

-- 
http://fam-tille.de

Bug#850235: marked as done (nuitka: FTBFS (SyntaxError: duplicate argument 'a' in function definition))

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 17:09:39 -0500
with message-id <20170127220939.ga5...@onerussian.com>
and subject line fixed in recent upload
has caused the Debian Bug report #850235,
regarding nuitka: FTBFS (SyntaxError: duplicate argument 'a' in function 
definition)
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.)


-- 
850235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nuitka
Version: 0.5.24.4+ds-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/nuitka-0.5.24.4+ds'
rst2pdf README.rst
rst2pdf Developer_Manual.rst
cp Changelog.rst changelog
cp Developer_Manual.rst Developer_Manual.txt
make[1]: Leaving directory '/<>/nuitka-0.5.24.4+ds'
   debian/rules override_dh_auto_test

[... snipped ...]

Comparing output of 'PrintFuture.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'Recursion.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'Referencing.py' using 'python3.5-dbg' with flags silent, 
expect_success, remove_output, recurse_all, original_file, python_debug, 
recurse_not:test_common ...
Comparing output of 'Referencing32.py' using 'python3.5-dbg' with flags silent, 
expect_success, remove_output, recurse_all, original_file, python_debug, 
recurse_not:test_common ...
Comparing output of 'Referencing33.py' using 'python3.5-dbg' with flags silent, 
expect_success, remove_output, recurse_all, original_file, python_debug, 
recurse_not:test_common ...
Comparing output of 'Referencing35.py' using 'python3.5-dbg' with flags silent, 
expect_success, remove_output, recurse_all, original_file, python_debug, 
recurse_not:test_common ...
Comparing output of 'Slots.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'ThreadedGenerators.py' using 'python3.5' with flags 
silent, expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TrickAssignments32.py' using 'python3.5' with flags 
silent, expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TryContinueFinally.py' using 'python3.5' with flags 
silent, expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TryExceptContinue.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TryExceptFinally.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TryExceptFrames.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TryReturnFinally.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'TryYieldFinally.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'Unicode.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'Unpacking35.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'Varargs.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'WithStatements.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file ...
Comparing output of 'YieldFrom33.py' using 'python3.5' with flags silent, 
expect_success, remove_output, recurse_all, original_file, ignore_stderr ...
Running the syntax tests with options '' with python3.5:
Run './tests/syntax/run_all.py search' in '/<>/nuitka-0.5.24.4+ds'.
Using concrete python 3.5.2 on x86_64
Comparing output of 'BreakWithoutLoop.py' using 'python3.5' with flags silent, 
expect_failure, remove_output ...
Comparing output of 'ClassReturn.py' using 'python3.5' with flags silent, 
expect_failure, remove_output ...
Comparing 

Bug#852853: Pending fixes for bugs in the libwww-curl-perl package

[pkg-perl-maintainers]

tag 852853 + pending
thanks

Some bugs in the libwww-curl-perl package are closed in revision
eaa9b76b4266bea58a643889062e0221eb2b9a70 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libwww-curl-perl.git/commit/?id=eaa9b76

Commit message:

Add patch add curl's new multiarch include path to Makefile.PL.

Thanks: Santiago Vila for the bug report.
Closes: #852853

Processed: Pending fixes for bugs in the libwww-curl-perl package

[Debian Bug Tracking System]

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

> tag 852853 + pending
Bug #852853 [src:libwww-curl-perl] libwww-curl-perl: FTBFS (Cannot find curl.h)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852853: libwww-curl-perl: FTBFS (Cannot find curl.h)

[gregor herrmann]

Control: tag -1 + confirmed

On Fri, 27 Jan 2017 20:51:04 +, Santiago Vila wrote:

> I tried to build this package in stretch with "dpkg-buildpackage -B"
> but it failed:
> 
> 
> [...]
>  debian/rules build-arch
> dh build-arch
>dh_testdir -a
>dh_update_autotools_config -a
>dh_auto_configure -a
>   perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
> "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,-z,now"
> Locating required external dependency bin:curl-config... found at 
> /usr/bin/curl-config.
> The version is libcurl 7.52.1
> Cannot find curl.h - cannot build constants files  - see Makefile.PL at 
> Makefile.PL line 96.
> dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor OPTIMIZE=-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,-z,now returned exit code 2
> debian/rules:6: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> 

Thanks, same here.

Seems like curl 7.52.1-1 moved the headers:

  * Another attempt at making -dev packages multi-arch.

and our libwww-curl-perl's Makefile.PL is bad at guessing the correct
include path.


Some looking around:

Makefile.PL adds $ARGV[0] to the @includes array, and `perl -I.
Makefile.PL /usr/include/x86_64-linux-gnu' works but passing it via

dh_auto_configure -- $(INCLUDEDIR)

fails as that gets appended at the end:

dh_auto_configure -- /usr/include/x86_64-linux-gnu
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/build/libwww-curl-perl-4.17=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 
-fdebug-prefix-map=/build/libwww-curl-perl-4.17=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" 
/usr/include/x86_64-linux-gnu

So I guess patching Makefile.PL it is.
Ok, pushed to git, reviews welcome.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Frank Zappa: METAL MAN HAS WON HIS WINGS


signature.asc
Description: Digital Signature

Processed: Re: Bug#852853: libwww-curl-perl: FTBFS (Cannot find curl.h)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #852853 [src:libwww-curl-perl] libwww-curl-perl: FTBFS (Cannot find curl.h)
Added tag(s) confirmed.

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

Bug#806067: marked as done (lilypond: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 21:48:54 +
with message-id 
and subject line Bug#806067: fixed in lilypond 2.18.2-6
has caused the Debian Bug report #806067,
regarding lilypond: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
to be marked as done.

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

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


-- 
806067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lilypond
Version: 2.18.2-4
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --parallel --with autotools-dev --with python2 --with quilt
   dh_testroot -i -O--parallel
   dh_prep -i -O--parallel
   dh_installdirs -i -O--parallel
   debian/rules override_dh_auto_install-indep
make[1]: Entering directory '/<>'
/usr/bin/make install-doc WEB_TARGETS="offline" 
prefix=/<>/debian/tmp/usr/
make[2]: Entering directory '/<>'
/usr/bin/make --no-builtin-rules out=www install-WWW
make[3]: Entering directory '/<>'
/<>/scripts/build/out/install -c -m 755 -d 
/<>/debian/tmp/usr//share/doc/lilypond/html
rsync -rl --exclude='*.signature' ./out-www/offline-root/ 
/<>/debian/tmp/usr//share/doc/lilypond/html
/usr/bin/make -C Documentation omf-local-install
make[4]: Entering directory '/<>/Documentation'
/<>/scripts/build/out/install -c -d 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2
/<>/scripts/build/out/install -c -m 644 
./out-www/internals.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/internals.html.omf 
&&   /<>/scripts/build/out/install -c -m 644 
./out-www/internals.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/internals.pdf.omf && 
  /<>/scripts/build/out/install -c -m 644 
./out-www/contributor.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/contributor.html.omf 
&&   /<>/scripts/build/out/install -c -m 644 
./out-www/web.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/web.html.omf &&   
/<>/scripts/build/out/install -c -m 644 
./out-www/contributor.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/contributor.pdf.omf 
&&   /<>/scripts/build/out/install -c -m 644 ./out-www/web.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/web.pdf.omf &&   
/<>/scripts/build
 /out/install -c -m 644 ./out-www/essay.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/essay.html.omf &&   
/<>/scripts/build/out/install -c -m 644 ./out-www/usage.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/usage.html.omf &&   
/<>/scripts/build/out/install -c -m 644 
./out-www/music-glossary.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/music-glossary.html.omf
 &&   /<>/scripts/build/out/install -c -m 644 
./out-www/learning.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/learning.html.omf && 
  /<>/scripts/build/out/install -c -m 644 
./out-www/snippets.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/snippets.html.omf && 
  /<>/scripts/build/out/install -c -m 644 
./out-www/notation.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/notation.html.omf && 
  /<>/scripts/build/out/install -c -m 
 644 ./out-www/extending.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/extending.html.omf 
&&   /<>/scripts/build/out/install -c -m 644 
./out-www/changes.html.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/changes.html.omf &&  
 /<>/scripts/build/out/install -c -m 644 ./out-www/essay.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/essay.pdf.omf &&   
/<>/scripts/build/out/install -c -m 644 ./out-www/usage.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/usage.pdf.omf &&   
/<>/scripts/build/out/install -c -m 644 
./out-www/music-glossary.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/music-glossary.pdf.omf
 &&   /<>/scripts/build/out/install -c -m 644 
./out-www/learning.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/learning.pdf.omf &&  
 /<>/scripts/build/out/install -c -m 644 ./out-www/snippets.pdf.
 omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/snippets.pdf.omf &&  
 /<>/scripts/build/out/install -c -m 644 
./out-www/notation.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/notation.pdf.omf &&  
 /<>/scripts/build/out/install -c -m 644 
./out-www/extending.pdf.omf 
/<>/debian/tmp/usr//share/omf/lilypond/2.18.2/extending.pdf.omf && 
  

Bug#850988: autopkgtest: FTBFS: Test failures

[Paul Gevers]

Hi Lucas,

> On Wed, 11 Jan 2017 at 19:48:38 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

On Mon, 16 Jan 2017 09:13:58 + Simon McVittie  wrote:
> This appears to be because at the time of this test run, python3-wand
> was uninstallable (#850815), and autopkgtest happens to use that package
> in its tests (it downloads it from the already-configured apt source,
> see #833503).

Does autopkgtest still fail rebuilding in your setup? If not, can you
close this bug?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#852728: marked as done (FTBFS on non-Linux architectures)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 21:19:54 +
with message-id 
and subject line Bug#852728: fixed in mariadb-10.1 10.1.21-5
has caused the Debian Bug report #852728,
regarding FTBFS on non-Linux architectures
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.)


-- 
852728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.1
Version: 10.1.21-2
Severity: normal
Tags: patch

The package was failing to build because it was unconditionally trying to
install systemd files and Linux-only utilities. Patch attached (tested
on kfreebsd-amd64).

Regards,
James
>From e30d6b243b57664ef398df2b00534041a2109b0b Mon Sep 17 00:00:00 2001
From: James Clarke 
Date: Thu, 26 Jan 2017 18:59:28 +
Subject: [PATCH] Fix FTBFS on non-Linux architectures

---
 debian/mariadb-server-10.1.install | 9 +
 debian/rules   | 3 +++
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/debian/mariadb-server-10.1.install b/debian/mariadb-server-10.1.install
old mode 100644
new mode 100755
index 03def793..f4a875db
--- a/debian/mariadb-server-10.1.install
+++ b/debian/mariadb-server-10.1.install
@@ -1,3 +1,4 @@
+#!/usr/bin/dh-exec
 debian/additions/debian-start etc/mysql
 debian/additions/debian-start.inc.sh usr/share/mysql
 debian/additions/echo_stderr usr/share/mysql
@@ -5,15 +6,15 @@ debian/additions/mariadb.conf.d/50-mysqld_safe.cnf etc/mysql/mariadb.conf.d
 debian/additions/mariadb.conf.d/50-server.cnf etc/mysql/mariadb.conf.d
 debian/additions/source_mariadb-10.1.py usr/share/apport/package-hooks
 etc/apparmor.d/usr.sbin.mysqld
-lib/systemd/system/mariadb@bootstrap.service.d/use_galera_new_cluster.conf
+[linux-any] lib/systemd/system/mariadb@bootstrap.service.d/use_galera_new_cluster.conf
 usr/bin/aria_chk
 usr/bin/aria_dump_log
 usr/bin/aria_ftdump
 usr/bin/aria_pack
 usr/bin/aria_read_log
-usr/bin/galera_new_cluster
-usr/bin/galera_recovery
-usr/bin/mariadb-service-convert
+[linux-any] usr/bin/galera_new_cluster
+[linux-any] usr/bin/galera_recovery
+[linux-any] usr/bin/mariadb-service-convert
 usr/bin/msql2mysql
 usr/bin/my_print_defaults
 usr/bin/myisam_ftdump
diff --git a/debian/rules b/debian/rules
index 197a54e1..a50a9d91 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,6 +14,7 @@ BUILDDIR := builddir
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_SYSTEM ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_SYSTEM)
 DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
+DEB_BUILD_ARCH_OS ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS)
 DEBVERSION := $(shell dpkg-parsechangelog | awk '/^Version: / { print $$2 }' | sed 's/^.*-//' )
 DEB_SOURCE_PACKAGE ?= $(strip $(shell egrep '^Source: ' debian/control | cut -f 2 -d ':'))
 DEB_VERSION ?= $(shell dpkg-parsechangelog | egrep '^Version:' | cut -f 2 -d ' ')
@@ -125,9 +126,11 @@ override_dh_auto_install:
 	# If Mroonga plugin was not built skip the package
 	[ -f $(BUILDDIR)/storage/mroonga/ha_mroonga.so ] || sed -i -e "/Package: mariadb-plugin-mroonga/,+9d" debian/control
 
+ifneq (,$(filter linux,$(DEB_BUILD_ARCH_OS)))
 	# Copy systemd files to a location available for dh_installinit
 	cp $(BUILDDIR)/support-files/mariadb.service debian/mariadb-server-10.1.mariadb.service
 	cp $(BUILDDIR)/support-files/mariadb@.service debian/mariadb-server-10.1.mariadb@.service
+endif
 
 	# make install
 	cd $(BUILDDIR) && $(MAKE) install DESTDIR=$(TMP)
-- 
2.11.0

--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.21-5

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

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.1 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, 27 Jan 2017 20:42:36 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 

Bug#852853: libwww-curl-perl: FTBFS (Cannot find curl.h)

[Santiago Vila]

Package: src:libwww-curl-perl
Version: 4.17-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -B"
but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_testdir -a
   dh_update_autotools_config -a
   dh_auto_configure -a
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now"
Locating required external dependency bin:curl-config... found at 
/usr/bin/curl-config.
The version is libcurl 7.52.1
Cannot find curl.h - cannot build constants files  - see Makefile.PL at 
Makefile.PL line 96.
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 LD=x86_64-linux-gnu-gcc 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now returned exit code 2
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


It also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libwww-curl-perl.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#852851: mknbi: FTBFS (undefined reference to _GLOBAL_OFFSET_TABLE_')

[Santiago Vila]

Package: src:mknbi
Version: 1.4.4-12
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -B"
but it failed:


[...]
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer 
-fgnu89-inline -fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format 
-Wno-unused -DVERSION=\"1.4.4\" -c printf.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer 
-fgnu89-inline -fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format 
-Wno-unused -DVERSION=\"1.4.4\" -c string.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -E -DRELOC=0x92800  start32.S | as --32 -o start32@0x92800.o
ld -N -Ttext 0x92800 -e _start --oformat binary -m elf_i386 -o 
first32@0x92800.linux start32@0x92800.o first32.o memsizes.o printf.o string.o
first32.o: In function `gettag':
first32.c:(.text+0x8): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `copy_nonws':
first32.c:(.text+0xcc): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `discard_arg':
first32.c:(.text+0x128): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `outtag':
first32.c:(.text+0x169): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o: In function `putchar':
first32.c:(.text+0x1dc): undefined reference to `_GLOBAL_OFFSET_TABLE_'
first32.o:first32.c:(.text+0x213): more undefined references to 
`_GLOBAL_OFFSET_TABLE_' follow
Makefile:99: recipe for target 'first32@0x92800.linux' failed
make[2]: *** [first32@0x92800.linux] Error 1
rm start32@0x92800.o
make[2]: Leaving directory '/<>'
debian/rules:18: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


It also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/mknbi.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#852850: hilive: FTBFS (dh_auto_configure fails)

[Santiago Vila]

Package: src:hilive
Version: 0.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_testdir -a
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 6.2.1
-- The CXX compiler identification is GNU 6.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

Feature record: CXX_FEATURE:0cxx_delegating_constructors
Feature record: CXX_FEATURE:0cxx_deleted_functions
Feature record: CXX_FEATURE:0cxx_digit_separators
Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
Feature record: CXX_FEATURE:0cxx_explicit_conversions
Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
Feature record: CXX_FEATURE:0cxx_extern_templates
Feature record: CXX_FEATURE:0cxx_final
Feature record: CXX_FEATURE:0cxx_func_identifier
Feature record: CXX_FEATURE:0cxx_generalized_initializers
Feature record: CXX_FEATURE:0cxx_generic_lambdas
Feature record: CXX_FEATURE:0cxx_inheriting_constructors
Feature record: CXX_FEATURE:0cxx_inline_namespaces
Feature record: CXX_FEATURE:0cxx_lambdas
Feature record: CXX_FEATURE:0cxx_lambda_init_captures
Feature record: CXX_FEATURE:0cxx_local_type_template_args
Feature record: CXX_FEATURE:0cxx_long_long_type
Feature record: CXX_FEATURE:0cxx_noexcept
Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
Feature record: CXX_FEATURE:0cxx_nullptr
Feature record: CXX_FEATURE:0cxx_override
Feature record: CXX_FEATURE:0cxx_range_for
Feature record: CXX_FEATURE:0cxx_raw_string_literals
Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
Feature record: CXX_FEATURE:0cxx_return_type_deduction
Feature record: CXX_FEATURE:0cxx_right_angle_brackets
Feature record: CXX_FEATURE:0cxx_rvalue_references
Feature record: CXX_FEATURE:0cxx_sizeof_member
Feature record: CXX_FEATURE:0cxx_static_assert
Feature record: CXX_FEATURE:0cxx_strong_enums
Feature record: CXX_FEATURE:1cxx_template_template_parameters
Feature record: CXX_FEATURE:0cxx_thread_local
Feature record: CXX_FEATURE:0cxx_trailing_return_types
Feature record: CXX_FEATURE:0cxx_unicode_literals
Feature record: CXX_FEATURE:0cxx_uniform_initialization
Feature record: CXX_FEATURE:0cxx_unrestricted_unions
Feature record: CXX_FEATURE:0cxx_user_literals
Feature record: CXX_FEATURE:0cxx_variable_templates
Feature record: CXX_FEATURE:0cxx_variadic_macros
Feature record: CXX_FEATURE:0cxx_variadic_templates
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
debian/rules:10: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


A similar failure happens here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Hilmar Preuße]

tags 755992 - moreinfo
stop

Am 27.01.2017 um 20:51 tastete Hilmar Preuße:


tags 755992 + fixed-upstream
stop

Processed: Re: Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Debian Bug Tracking System]

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

> tags 755992 - moreinfo
Bug #755992 [proftpd-mod-clamav] proftpd-mod-clamav: error: Can not stat file 
(9): Bad file descriptor
Removed tag(s) moreinfo.
> stop
Stopping processing here.

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

Processed: Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Debian Bug Tracking System]

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

> tags 755992 + fixed-upstream
Bug #755992 [proftpd-mod-clamav] proftpd-mod-clamav: error: Can not stat file 
(9): Bad file descriptor
Added tag(s) fixed-upstream.
> stop
Stopping processing here.

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

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Hilmar Preuße]

tags 755992 + fixed-upstream
stop

On 13.01.2017 20:28, Adrian Bunk wrote:

On Thu, Sep 22, 2016 at 01:19:07PM +0200, Hilmar Preuße wrote:


Hi,


I assume that it has been fixed in [1], Further I suspect(!) that the fix is
already in our git repository. I've build packages based on our git[2] for
i386. Would you be so kind to test them?

If you need other arches (e.g. amd64) please call back.


Has there been any feedback regarding whether this might already be fixed?

Currently this bug would prevent that proftpd-mod-clamav could be in
stretch.


We don't have the fix for that in our git, but version 0.14 fixes the
problem (as described by submitters). We have to import the latest 
version of the module from upstream.


Hilmar

Bug#850762: fixed in setserial 2.17-50

[Andreas Beckmann]

On 2017-01-27 17:09, Andreas Henriksson wrote:
> Hello Thorsten Alteholz, Andreas Beckmann.
> 
> On Sun, Jan 22, 2017 at 03:50:31PM +, Thorsten Alteholz wrote:
> [...]
>>* debian/control: add dependency to lsb-base (Closes: #850762)
> [...]
> 
> This change is WRONG. You're now depending on something which you don't
> actually need!
> (I'm not sure what the kosher interpretation of policy is on this
> but I'm willing to bet overinflating dependencies is RC just like
> lacking dependencies.)
> 
> In a sysvinit-core system lsb-base is guaranteed to be there.
> On a systemd (default init) system, the init scripts is masked
> by the native systemd units shipped in the setserial package.
> 
> I guess Andreas Beckmann managed to produce the piuparts error by
> having a broken chroot, eg. having no init system + no policy-rc.d.

The piuparts chroot is *not broken*.

> Andreas please confirm you're missing policy-rc.d (and have an
> init-less chroot, e.g. debootstrap --variant=minbase).

There is usually no init system installed, but a policy-rc.d exists to
prevent starting of services (with exceptions for mysql and postgresql).

If something still runs into the missing lsb-base dependency, the
initscript must be executed by some means that avoid invoke-rc.d.


We looked into the missing lsb-base dependencies and whether these could
be checked for with piuparts, but concluded that this does not work
since the initscrips are usually not executed if running under piuparts.

> The broken setup Andreas is likely running is now auto-detected
> and automagically handled with init-system-helpers 1.47 (currently
> in sid, soon hopefully migrating to stretch). In other words
> Andreas should not be able to reproduce this problem using
> init-system-helpers 1.47 -- where he'll just get a big fat angry warning
> about his system missing policy-rc.d and then automatically acting
> like it was there to avoid tripping any errors.
>
>
https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/commit/?id=289e032e9eb213480e65b47cb1233a6f98bfad4f

Andreas

PS: just consider a package which
  Build-Depends: setserial
this must still install cleanly in a whatsoever minimal chroot.

Bug#852840: xsane: FTBFS against libsane-dev 1.0.25-3 - sane-config not found

[Andreas Metzler]

Package: xsane
Version: 0.999-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hello,

the removal of sane-config from sane-backends in version 1.0.25-3 broke
compilation of xsane:

checking for sane-config... no
checking for SANE - version >= 1.0.0... no
*** The sane-config script installed by SANE could not be found
*** If SANE was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the SANE_CONFIG environment variable to the
*** full path to sane-config.

Find attached a minimal seems-to-work-for-me patch.

cu Andreas

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages xsane depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-8
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.3-1
ii  libgimp2.0   2.8.18-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  liblcms2-2   2.8-3
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  libpng16-16  1.6.28-1
ii  libsane  1.0.25-2+b1
ii  libtiff5 4.0.7-5
ii  xsane-common 0.999-4
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages xsane recommends:
ii  cups-client2.2.1-4
ii  firefox [www-browser]  52.0~b1-1
ii  w3m [www-browser]  0.5.3-34

Versions of packages xsane suggests:
ii  gimp  2.8.18-1
pn  gocr | cuneiform | tesseract-ocr | ocrad  
pn  gv
pn  hylafax-client | mgetty-fax   

-- no debconf information
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- a/configure.in
+++ b/configure.in
@@ -165,8 +165,10 @@ fi
 
 AC_SUBST(INTLSUB)
 
-AM_PATH_SANE(1.0.0, HAVE_SANE=yes, )
-
+PKG_CHECK_MODULES([SANE], [sane-backends >= 1.0.0])
+PKG_CHECK_VAR([SANE_PREFIX], [sane-backends >= 1.0.0], [prefix])
+PKG_CHECK_VAR([SANE_LDFLAGS], [sane-backends >= 1.0.0], [ldflags],
+  [HAVE_SANE=yes])
 if test "${USE_GIMP}" = "yes"; then
   if test "${TRY_GIMP_2}" = "yes"; then
 AM_PATH_GIMP_2_0(1.3.23, HAVE_GIMP=yes, )

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 813054 https://bugzilla.mozilla.org/show_bug.cgi?id=1334543
Bug #813054 [src:firefox] firefox: contains JSHint work under non-free licence
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1334543'.
> thanks
Stopping processing here.

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

Bug#805988: aboot : cross-compile aboot-base

[jhcha54008]

I am unsure : shouldn't the build dependencies
gcc-alpha-linux-gnu [!alpha], libc6.1-dev-alpha-cross [!alpha]
appear in a field
Build-Depends-Indep
instead of
Build-Depends ?

They are required to build aboot-base (Arch: all)
and not aboot-cross (Arch: any).

Regards,
JH Chatenet

Bug#849831: Evil licence

[Emilio Pozuelo Monfort]

Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1334543
Control: forwarded 849832 https://bugzilla.mozilla.org/show_bug.cgi?id=1334543

On Thu, 28 Jan 2016 22:52:08 +0100 Bastien ROUCARIES
 wrote:
> severity: serious
> user: debian...@lists.debian.org
> usertags: json-evil-license
> package: iceweasel
> version: 44.0-1
> 
> Hi,
> 
> mozilla/dom/system/gonk/tests/marionette/ril_jshint/jshint.js
> 
> is licenced under evil licence...
> 
> Please repack and notify archive.debian.org in order to remove old package.

Not sure that is necessary, given the file is distributable and I don't think
it's used in the resulting binaries.

Cheers,
Emilio

Processed: Issue looks RC and no rationale was given for downgrading

[Debian Bug Tracking System]

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

> severity 847311 grave
Bug #847311 [amavisd-new] amavisd-new: After the last Debian update Amavis does 
not read data type float from Mysql DB correctly. All fields are "0".
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Evil licence

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1334543
Bug #849831 [firefox-esr] firefox: contains JSHint work under non-free licence
Bug #849833 [firefox-esr] firefox: contains JSHint work under non-free licence
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1334543'.
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1334543'.
> forwarded 849832 https://bugzilla.mozilla.org/show_bug.cgi?id=1334543
Bug #849832 [icedove] firefox: contains JSHint work under non-free licence
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1334543'.

-- 
849831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849831
849832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849832
849833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#849833: Evil licence

[Emilio Pozuelo Monfort]

Control: reassign -1 firefox-esr
Control: forcemerge -1 849831

On Thu, 28 Jan 2016 22:52:08 +0100 Bastien ROUCARIES
 wrote:
> severity: serious
> user: debian...@lists.debian.org
> usertags: json-evil-license
> package: iceweasel
> version: 44.0-1
> 
> Hi,
> 
> mozilla/dom/system/gonk/tests/marionette/ril_jshint/jshint.js
> 
> is licenced under evil licence...
> 
> Please repack and notify archive.debian.org in order to remove old package.

iceweasel and firefox-esr are the same source these days. No need to have two
bugs for the same thing.

Cheers,
Emilio

Processed: Re: Evil licence

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 firefox-esr
Bug #849833 [iceweasel] firefox: contains JSHint work under non-free licence
Bug reassigned from package 'iceweasel' to 'firefox-esr'.
Ignoring request to alter found versions of bug #849833 to the same values 
previously set
Ignoring request to alter fixed versions of bug #849833 to the same values 
previously set
> forcemerge -1 849831
Bug #849833 [firefox-esr] firefox: contains JSHint work under non-free licence
Bug #849831 [firefox-esr] firefox: contains JSHint work under non-free licence
Merged 849831 849833

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

Processed: Re: devscripts: [bts] "bts show" command displays error: (process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #789955 [iceweasel] devscripts: [bts] "bts show" command displays error: 
(process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Bug #798988 [iceweasel] g_slice_set_config: assertion 'sys_page_size == 0' 
failed
Severity set to 'minor' from 'grave'
Severity set to 'minor' from 'grave'
> forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=833117
Bug #789955 [iceweasel] devscripts: [bts] "bts show" command displays error: 
(process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Bug #798988 [iceweasel] g_slice_set_config: assertion 'sys_page_size == 0' 
failed
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=833117'.
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=833117'.

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

Bug#789955: devscripts: [bts] "bts show" command displays error: (process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

[Emilio Pozuelo Monfort]

Control: severity -1 minor
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=833117

This is just a cosmetic issue, there is no impact on the browser experience
whatsoever. Downgrading.

Cheers,
Emilio

Processed: Re: Bug#825355: firefox-esr: FTBFS on arm64: Error while running startup cache precompilation

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #825355 [src:firefox-esr] firefox-esr: FTBFS on arm64: Error while running 
startup cache precompilation
Severity set to 'important' from 'serious'

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

Bug#825355: firefox-esr: FTBFS on arm64: Error while running startup cache precompilation

[Emilio Pozuelo Monfort]

Control: severity -1 important

On 26/05/16 16:23, Emilio Pozuelo Monfort wrote:
> On 26/05/16 14:48, Mike Hommey wrote:
>> On Thu, May 26, 2016 at 12:56:28PM +0200, Emilio Pozuelo Monfort wrote:
>>> Source: firefox-esr
>>> Version: 45.1.1esr-1
>>> Severity: serious
>>>
>>> Hi,
>>>
>>> firefox-esr failed to build on arm64:
>>>
>>> Executing /«PKGBUILDDIR»/build-browser/dist/bin/xpcshell -g 
>>> /«PKGBUILDDIR»/build-browser/dist/bin/ -a 
>>> /«PKGBUILDDIR»/build-browser/dist/bin/ -f 
>>> /«PKGBUILDDIR»/toolkit/mozapps/installer/precompile_cache.js -e 
>>> precompile_startupcache("resource://gre/");
>>> resource://gre/components/ActivityMessageConfigurator.js
>>> resource://gre/modules/commonjs/sdk/ui/sidebar/contract.js
>>> [...]
>>> resource://gre/modules/workers/require.js
>>> ERROR!! RequestSyncService - Failed to retrieve data from the database.
>>> Executing /«PKGBUILDDIR»/build-browser/dist/bin/xpcshell -g 
>>> /«PKGBUILDDIR»/build-browser/dist/bin/ -a 
>>> /«PKGBUILDDIR»/build-browser/dist/bin/browser -f 
>>> /«PKGBUILDDIR»/toolkit/mozapps/installer/precompile_cache.js -e 
>>> precompile_startupcache("resource://app/");
>>> resource://app/components/ChromeProfileMigrator.js
>>> resource://app/components/ExperimentsService.js
>>> [...]
>>> resource://app/modules/Chat.jsm
>>> resource://app/modules/ContentClick.jsm
>>> Traceback (most recent call last):
>>>   File "/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.py", line 406, in 
>>> 
>>> main()
>>>   File "/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.py", line 400, in 
>>> main
>>> args.source, gre_path, base)
>>>   File "/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.py", line 161, in 
>>> precompile_cache
>>> errors.fatal('Error while running startup cache precompilation')
>>>   File "/«PKGBUILDDIR»/python/mozbuild/mozpack/errors.py", line 103, in 
>>> fatal
>>> self._handle(self.FATAL, msg)
>>>   File "/«PKGBUILDDIR»/python/mozbuild/mozpack/errors.py", line 98, in 
>>> _handle
>>> raise ErrorMessage(msg)
>>> mozpack.errors.ErrorMessage: Error: Error while running startup cache 
>>> precompilation
>>> /«PKGBUILDDIR»/toolkit/mozapps/installer/packager.mk:41: recipe for target 
>>> 'stage-package' failed
>>>
>>> Logs at 
>>> https://buildd.debian.org/status/logs.php?pkg=firefox-esr=45.1.1esr-1%2Bb1=arm64
>>
>> Interestingly 45.1.1esr-1 built fine, and none of the versions that
>> failed have differences with it that would matter for that build error.
>> So there seems to be some erratic (random) failure. If your immediate
>> concern is getting it built for a transition, please try to retrigger
>> builds.
> 
> It failed twice with the same error. I have given it back again, let's see how
> that goes.

This looks like a random failure indeed:

https://buildd.debian.org/status/logs.php?pkg=firefox-esr=arm64

Downgrading to important.

Cheers,
Emilio

Bug#850976: marked as done (firefox-esr: FTBFS: configure: error: cannot determine icu version number from uvernum.h header file)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 17:56:29 +0100
with message-id 
and subject line Re: firefox-esr: FTBFS: configure: error: cannot determine icu 
version number from uvernum.h header file
has caused the Debian Bug report #850976,
regarding firefox-esr: FTBFS: configure: error: cannot determine icu version 
number from uvernum.h header file
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.)


-- 
850976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox-esr
Version: 45.6.0esr-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking for stdint.h... yes
> checking for inttypes.h... yes
> checking for posix_fadvise... yes
> checking for posix_fallocate... yes
> sed: character class syntax is [[:space:]], not [:space:]
> configure: error: cannot determine icu version number from uvernum.h header 
> file 
> -- config.log --
> /usr/bin/ld: total time in link: 0.02
> /usr/bin/ld: data size 4583424
> configure:27972: checking for FT_Load_Sfnt_Table
> configure:28004: gcc -o conftest -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-schedule-insns2 -fno-delete-null-pointer-checks 
> -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections 
> -fdata-sections -fno-math-errno -pthread -pipe -I/usr/include/freetype2 
> -Wdate-time -D_FORTIFY_SOURCE=2 -lpthread  -Wl,--as-needed 
> -Wl,--reduce-memory-overheads -Wl,--no-keep-memory -Wl,--stats 
> -Wl,-z,noexecstack -Wl,-z,text -Wl,--build-id conftest.c -ldl  -lfreetype 1>&5
> /usr/bin/ld: total time in link: 0.02
> /usr/bin/ld: data size 4583424
> configure:28042: checking for fontconfig/fcfreetype.h
> configure:28055: gcc -c -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-schedule-insns2 -fno-delete-null-pointer-checks 
> -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections 
> -fdata-sections -fno-math-errno -pthread -pipe -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2  conftest.c 1>&5
> configure:28145: checking for fontconfig
> configure:28152: checking _FONTCONFIG_CFLAGS
> configure:28157: checking _FONTCONFIG_LIBS
> configure:28346: checking for stdint.h
> configure:28359: gcc -c -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-schedule-insns2 -fno-delete-null-pointer-checks 
> -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections 
> -fdata-sections -fno-math-errno -pthread -pipe -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c 1>&5
> configure:28346: checking for inttypes.h
> configure:28359: gcc -c -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-schedule-insns2 -fno-delete-null-pointer-checks 
> -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections 
> -fdata-sections -fno-math-errno -pthread -pipe -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c 1>&5
> configure:29789: checking for posix_fadvise
> configure:29821: gcc -o conftest -Wall -Wempty-body -Wpointer-to-int-cast 
> -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-schedule-insns2 -fno-delete-null-pointer-checks -std=gnu99 
> -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections 
> -fno-math-errno -pthread -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -lpthread  
> -Wl,--as-needed -Wl,--reduce-memory-overheads -Wl,--no-keep-memory 
> -Wl,--stats -Wl,-z,noexecstack -Wl,-z,text -Wl,--build-id conftest.c -ldl  
> 1>&5
> /usr/bin/ld: total time in link: 0.02
> /usr/bin/ld: data size 4329472
> configure:29789: checking for posix_fallocate
> configure:29821: gcc -o conftest -Wall -Wempty-body -Wpointer-to-int-cast 
> -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-schedule-insns2 -fno-delete-null-pointer-checks -std=gnu99 
> -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections 
> -fno-math-errno -pthread -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -lpthread  
> -Wl,--as-needed -Wl,--reduce-memory-overheads -Wl,--no-keep-memory 
> -Wl,--stats -Wl,-z,noexecstack -Wl,-z,text -Wl,--build-id conftest.c -ldl  
> 1>&5
> /usr/bin/ld: total time in link: 0.02
> /usr/bin/ld: data size 4333568
> configure:29875: gcc -c -Wall -Wempty-body -Wpointer-to-int-cast 
> 

Bug#852321: timidity: fails to start after installation

[Thorsten Glaser]

Adam Borowski dixit:

>Besides fluid, there's also timgm6mb-soundfont.

There probably also is “whatever MuseScore uses”, which I have
installed on my system already anyway…

bye,
//mirabilos
-- 
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.

Processed: Still open in experimental

[Debian Bug Tracking System]

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

> unarchive 845030
Bug #845030 {Done: Lev Lamberov } [src:swi-prolog] 
swi-prolog: configure does not find libssl, builds without OpenSSL support
Unarchived Bug 845030
> unarchive 837359
Bug #837359 {Done: Mehdi Dogguy } [src:ocaml] ocaml: FTBFS on 
-fPIE binNMU on armhf - test failure
Unarchived Bug 837359
> thanks
Stopping processing here.

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

Bug#850762: fixed in setserial 2.17-50

[Andreas Henriksson]

Hello Thorsten Alteholz, Andreas Beckmann.

On Sun, Jan 22, 2017 at 03:50:31PM +, Thorsten Alteholz wrote:
[...]
>* debian/control: add dependency to lsb-base (Closes: #850762)
[...]

This change is WRONG. You're now depending on something which you don't
actually need!
(I'm not sure what the kosher interpretation of policy is on this
but I'm willing to bet overinflating dependencies is RC just like
lacking dependencies.)

In a sysvinit-core system lsb-base is guaranteed to be there.
On a systemd (default init) system, the init scripts is masked
by the native systemd units shipped in the setserial package.

I guess Andreas Beckmann managed to produce the piuparts error by
having a broken chroot, eg. having no init system + no policy-rc.d.
Andreas please confirm you're missing policy-rc.d (and have an
init-less chroot, e.g. debootstrap --variant=minbase).

The broken setup Andreas is likely running is now auto-detected
and automagically handled with init-system-helpers 1.47 (currently
in sid, soon hopefully migrating to stretch). In other words
Andreas should not be able to reproduce this problem using
init-system-helpers 1.47 -- where he'll just get a big fat angry warning
about his system missing policy-rc.d and then automatically acting
like it was there to avoid tripping any errors.

https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/commit/?id=289e032e9eb213480e65b47cb1233a6f98bfad4f

Regards,
Andreas Henriksson

Bug#852819: Separating typeshed into own package?

[Leonhard Weber]

Uppon further fiddling, perhaps it is best to move the typeshed out into
its own package? Will give it a shot, perhaps I learn how to properly
package in the process.



signature.asc
Description: OpenPGP digital signature

Bug#851838: httest: diff for NMU version 2.4.18-1.1

[Eva Ramon]

Thanks Sebastian!

On Jan 24, 2017 21:51, "Sebastian Andrzej Siewior" 
wrote:

> Control: tags 851838 + patch
>
> Dear maintainer,
>
> I've prepared an NMU for httest (versioned as 2.4.18-1.1). The diff
> is attached to this message.
>
> Regards.
> Sebastian
>

Bug#852822: signing buildinfo by default breaks compatibility

[Ian Jackson]

Package: dpkg-dev
Version: 1.18.19
Severity: serious

>From the changelog:

   * Add support for signed .buildinfo files to dpkg-buildpackage. Add new
 -ui and --unsigned-buildinfo options. Closes: #843925

This suggests that buildinfo files will now be signed by default.  The
manpage and my ad-hoc tests agree.

Previously runes like
  dpkg-buildpackage -uc -b
  dpkg-buildpackage -F -uc -us
were known and recommended as ways to build packages locally.

Now these runes would have to be
  dpkg-buildpackage -uc -b -ui
  dpkg-buildpackage -F -uc -us -ui

But those runes are not supported by dpkg in jessie.

This means that there is no longer a rune for `build this package but
do not sign anything' that will work both before and after this
change.

IMO that is a serious regression.

IMO the correct fix is to, by default, sign the buildinfo iff the
.changes are being signed.  That way -uc is sufficient.

Thanks for your attention.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#852819: [mypy] Package is missing typeshed defs for python stdlib's

[Leonhard Weber]

Package: mypy
Version: 0.470-1
Severity: serious

Hi, the package stops shipping the upstream typeshed. This results in an
error
described in upstream issues #2480, and follow-up #2483, explaining this is
because mypy currently does not  sanitize its input while walking a
typeshed
location.

Bottomline; typeshed is missing in package, and mypy is rendered inoperable
unless manually instructed to load typeshed from a specified and manually
prepared location.

--- System information. ---
Architecture:
Kernel: Linux 4.8.0-2-amd64

--- Package information. ---
Depends (Version) | Installed
===-+-==
python3-typed-ast | 0.6.3-1
python3:any (>= 3.3.2-2~) |




signature.asc
Description: OpenPGP digital signature

Bug#844980: undertaker is waiting for binutils testing migration

[Adrian Bunk]

undertaker is waiting for gcc-6 testing migration,
which itself depends on binutils testing migration.

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

Processed: Bug is also in the version in stretch

[Debian Bug Tracking System]

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

> found 852781 1:7.4p1-5
Bug #852781 [openssh-server] openssh-server: Wrong default for setting 
PermitRootLogin (yes instead of prohibit-password) in clean install
Marked as found in versions openssh/1:7.4p1-5.
> thanks
Stopping processing here.

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

Bug#852781: openssh-server: Wrong default for setting PermitRootLogin (yes instead of prohibit-password) in clean install

[Christoph Anton Mitterer]

On Fri, 2017-01-27 at 10:34 +0100, lopiuh wrote:
>    * What outcome did you expect instead?
> [...]
> #LoginGraceTime 2m
> PermitRootLogin prohibit-password
> #StrictModes yes
> #MaxAuthTries 6
> #MaxSessions 10
> [...]


No, the outcome shouldn't be that, it should be left just at default
(which is already prohibit-password) and not set explicitly.

Debian's SSH already mangles around with too many security relevant
options for not good or little good reasons (see several of my bug
reports on these).
It's not that I'd generally condemn deviation from upstream defaults,
but there should be really strong grounds for doing so.

Setting this explicitly causes just further pain later if that value
should ever change again in the upstream defaults to something even
more secure or better.


Best wishes,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#852681: skysentials: unfit for main (or should document Skype-independent features)

[Jonas Smedegaard]

Quoting Gianfranco Costamagna (2017-01-27 14:53:18)
> On Thu, 26 Jan 2017 12:19:09 +0100 Jonas Smedegaard  wrote:
>> [...] the package is not fit for Debian main, but should be moved to 
>> contrib
[...]
> Package: skysentials (1.0.1-5) [contrib] 
> 
> sorry but I don't get it :)
> 
> $ rmadison -u debian skysentials
> skysentials | 1.0.1-5   | buildd-unstable/contrib | source, all
> skysentials | 1.0.1-5   | unstable/contrib| source, all

Arrgh, indeed it is just my glasses needing cleaning :-P

Sorry for the noise!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: Re: skysentials: unfit for main (or should document Skype-independent features)

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #852681 [skysentials] skysentials: unfit for main (or should document 
Skype-independent features)
Marked Bug as done

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

Bug#852681: skysentials: unfit for main (or should document Skype-independent features)

[Gianfranco Costamagna]

control: close -1
On Thu, 26 Jan 2017 12:19:09 +0100 Jonas Smedegaard  wrote:
> Package: skysentials
> Version: 1.0.1-5
> Severity: serious
> Justification: Policy 2.2.2
> 
> It seems from the package description that this package is usable only
> as an addon to skype.
> 
> If that is true, then the package is not fit for Debian main, but should
> be moved to contrib (and the suggestion on skype bumped to depends).
> 
> If false, then please describe in long description the uses of the
> package standalone.
> 

Package: skysentials (1.0.1-5) [contrib] 

sorry but I don't get it :)

$ rmadison -u debian skysentials
skysentials | 1.0.1-5   | buildd-unstable/contrib | source, all
skysentials | 1.0.1-5   | unstable/contrib| source, all


G.



signature.asc
Description: OpenPGP digital signature

Bug#811960: marked as done (pulseview: FTBFS with GCC 6: is deprecated)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 13:48:51 +
with message-id 
and subject line Bug#811960: fixed in pulseview 0.2.0-1.2
has caused the Debian Bug report #811960,
regarding pulseview: FTBFS with GCC 6: is deprecated
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.)


-- 
811960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseview
Version: 0.2.0-1.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-deprecated-declarations

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /usr/bin/c++   -DENABLE_DECODE -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
> -D__STDC_LIMIT_MACROS -isystem /usr/include/qt4 -isystem 
> /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore 
> -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/usr/lib/x86_64-linux-gnu/libzip/include -I/usr/include/libusb-1.0 
> -I/usr/include/python3.5m -I/usr/include/x86_64-linux-gnu/python3.5m 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2-Wall -Wextra -Werror -o 
> CMakeFiles/pulseview.dir/pv/mainwindow.cpp.o -c 
> /<>/pv/mainwindow.cpp
> In file included from /<>/pv/mainwindow.cpp:46:0:
> /<>/pv/dialogs/about.h:47:7: error: 'template class 
> std::auto_ptr' is deprecated [-Werror=deprecated-declarations]
>   std::auto_ptr supportedDoc;
>^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/boost/config/no_tr1/memory.hpp:21,
>  from /usr/include/boost/get_pointer.hpp:14,
>  from /usr/include/boost/bind/mem_fn.hpp:25,
>  from /usr/include/boost/mem_fn.hpp:22,
>  from /usr/include/boost/bind/bind.hpp:26,
>  from /usr/include/boost/bind.hpp:22,
>  from /<>/pv/mainwindow.cpp:25:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> cc1plus: all warnings being treated as errors
> CMakeFiles/pulseview.dir/build.make:334: recipe for target 
> 'CMakeFiles/pulseview.dir/pv/mainwindow.cpp.o' failed
> make[3]: *** [CMakeFiles/pulseview.dir/pv/mainwindow.cpp.o] Error 1
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> CMakeFiles/Makefile2:70: recipe for target 'CMakeFiles/pulseview.dir/all' 
> failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: pulseview
Source-Version: 0.2.0-1.2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated pulseview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Jan 2017 14:19:00 +0100
Source: pulseview
Binary: pulseview
Architecture: source
Version: 0.2.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann 
Changed-By: Mattia Rizzolo 
Description:
 pulseview  - sigrok logic analyzer, oscilloscope, and MSO GUI
Closes: 781944 811960
Changes:
 pulseview (0.2.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump debhelper compat level to 10.
   * Add patch from upstream to fix build with GCC 6.  Closes: #811960
   * Drop menu file; the T-CTTE decided to deprecate the menu system, see 
#741573
   * Install a .desktop file and the icon.
 Thanks to 

Bug#852808: diaspora-common: fails to upgrade from stretch: chown: cannot access '/var/lib/diaspora': No such file or directory

[Andreas Beckmann]

Package: diaspora-common
Version: 0.6.3.0+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'sid' fails.

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

[...]
  Preparing to unpack .../24-diaspora-common_0.6.3.0+debian1_all.deb ...
  Unpacking diaspora-common (0.6.3.0+debian1) over (0.6.0.0+debian6) ...
[...]
  Setting up diaspora-common (0.6.3.0+debian1) ...
  Installing new version of config file /etc/diaspora/diaspora-common.conf ...
  Creating/updating diaspora user account...
  chown: cannot access '/var/lib/diaspora': No such file or directory
  dpkg: error processing package diaspora-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up nginx (1.10.2-4) ...
  Processing triggers for libc-bin (2.24-9) ...
  Errors were encountered while processing:
   diaspora-common


cheers,

Andreas


diaspora-common_0.6.3.0+debian1.log.gz
Description: application/gzip

Processed: user debian...@lists.debian.org, usertagging 789872, affects 789872, usertagging 811746 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 789872 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 789872 + libmaya-calendar0
Bug #789872 [maya-calendar] maya-calendar: FTBFS with current evolution
Added indication that 789872 affects libmaya-calendar0
> usertags 811746 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 811746 + elmer libelmersolver-6.1 libelmersolver-7.0
Bug #811746 [elmerfem] elmerfem: FTBFS with GCC 6: narrowing conversion
Added indication that 811746 affects elmer, libelmersolver-6.1, and 
libelmersolver-7.0
> usertags 811672 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 811672 + libqtcore4-perl
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Added indication that 811672 affects libqtcore4-perl
> usertags 768583 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 768583 + libqinfinity3
Bug #768583 [libqinfinity] libqinfinity: Build-Depends on unavailable 
libinfinity-0.5-dev
Added indication that 768583 affects libqinfinity3
> usertags 813175 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 813175 + liblucene-net3.0-cil
Bug #813175 [lucene-net] lucene-net: FTBFS CSC: error CS0518: The predefined 
type `System.Object' is not defined or imported
Added indication that 813175 affects liblucene-net3.0-cil
> usertags 717424 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 717424 + librhash1.0-cil librhash-perl librhash-php5 ruby-rhash
Bug #717424 [rhash-bindings] rhash-bindings: FTBFS: sh: 
debian/librhash1.0-cil/DEBIAN/clilibs: No such file or directory
Added indication that 717424 affects librhash1.0-cil, librhash-perl, 
librhash-php5, and ruby-rhash
> usertags 825546 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 785990 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 785990 3.1-6
Bug #785990 [src:distcc] distcc: deprecation of python-support
Marked as found in versions distcc/3.1-6.
> affects 785990 + distcc-pump
Bug #785990 [src:distcc] distcc: deprecation of python-support
Added indication that 785990 affects distcc-pump
> usertags 840305 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 728372 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> usertags 832330 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 832330 + libgnokii7
Bug #832330 [src:gnokii] gnokii: FTBFS in experimental: undefined references to 
GUI_HideAbout, CloseLogosWindow
Added indication that 832330 affects libgnokii7
> usertags 845637 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 845637 + xserver-xorg-video-glamo
Bug #845637 [src:xf86-video-glamo] FTBFS with xserver 1.19
Added indication that 845637 affects xserver-xorg-video-glamo
> usertags 846696 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20161202.
Usertags are now: piuparts qa-ftbfs qa-ftbfs-20161202.
> usertags 830596 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 750228 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 831238 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20160714.
Usertags are now: qa-ftbfs qa-ftbfs-20160714 piuparts.
> usertags 821634 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 804369 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 846854 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 746005 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 813596 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 813596 + libfloat-coq
Bug #813596 [src:coq-float] coq-float: FTBFS: make[2]: *** No rule to make 
target 'depend'.  Stop.
Added indication that 813596 affects libfloat-coq
> usertags 825231 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 825011 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 825012 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 707852 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 838897 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 846219 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 846219 + fusionforge-plugin-extsubproj
Bug #846219 [src:fusionforge] Missing runtime dependencies (former libarc-php, 
libgraphite-php and php-http)
Added indication that 846219 affects fusionforge-plugin-extsubproj
> usertags 708699 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 708699 + fso-gta02 fso-gta01
Bug #708699 [src:fso-common] fso-common: fso-gta0[12] uninstallable
Added indication that 708699 affects fso-gta02 and fso-gta01
> 

Bug#852627: lcms2: diff for NMU version 2.8-3.1

[Salvatore Bonaccorso]

Hi Thomas,

On Fri, Jan 27, 2017 at 07:59:14AM +0100, Salvatore Bonaccorso wrote:
> Hi Thomas,
> 
> On Fri, Jan 27, 2017 at 07:27:43AM +0100, Thomas Weber wrote:
> > HI Salvatore,
> > On Thu, Jan 26, 2017 at 09:44:49PM +0100, Salvatore Bonaccorso wrote:
> > > Control: tags 852627 + pending
> > > 
> > > Dear maintainer,
> > > 
> > > I've prepared an NMU for lcms2 (versioned as 2.8-3.1) and
> > > uploaded it to DELAYED/2. Please feel free to tell me if I
> > > should delay it longer.
> > 
> > Sorry, I just uploaded 2.8-4 without checking the bug log again (I
> > prepard the fix yesterday). So, your NMU will probably never hit
> > unstable. I am sorry for the extra work.
> 
> No problem! Thanks for the fix to unstable an the unblock request!

Btw, I just prepared as well an update for jessie-security and should
be able to upload shortly.

Regards,
Salvatore

Bug#852728: [debian-mysql] Bug#852728:

[Otto Kekäläinen]

Fixed already in https://github.com/ottok/mariadb-10.1/pull/6

I will upload ASAP when possible. Some other changes may come in today too.

Processed: Re: bug 852728

[Debian Bug Tracking System]

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

> found 852728 10.1.21-4
Bug #852728 {Done: Otto Kekäläinen } [src:mariadb-10.1] FTBFS 
on non-Linux architectures
Marked as found in versions mariadb-10.1/10.1.21-4 and reopened.
> thanks
Stopping processing here.

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

Bug#820974: plans for bug #820974

[Michael Gilbert]

On Thu, Jan 26, 2017 at 6:41 AM, Arturo Borrero Gonzalez wrote:
> could you please share yours plans regarding this bug?

Patches welcome?

Best wishes,
Mike

Processed: bug 852728

[Debian Bug Tracking System]

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

> severity 852728 serious
Bug #852728 {Done: Otto Kekäläinen } [src:mariadb-10.1] FTBFS 
on non-Linux architectures
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#852800: python-networking-sfc: uninstallable, needs to support python-sqlalchemy 1.1

[Andreas Beckmann]

Package: python-networking-sfc
Version: 2.0.1~git20160926.27f311e-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

# apt-get install python-networking-sfc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python-networking-sfc : Depends: python-sqlalchemy (< 1.1) but 1.1.5+ds1-1 is 
to be installed
E: Unable to correct problems, you have held broken packages.


Cheers,

Andreas

Processed: Found 814978 gcc-6/6.3.0-5

[Debian Bug Tracking System]

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

> found 814978 gcc-6/6.3.0-5
Bug #814978 [src:gcc-5] gcc-5: gnat paths are wrong due to ada-gcc-name.diff
Marked as found in versions gcc-6/6.3.0-5.
> thanks
Stopping processing here.

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

Processed (with 1 error): Update bug 814978 to: found in gcc-6 and severity serious

[Debian Bug Tracking System]

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

> severity 814978 serious
Bug #814978 [src:gcc-5] gcc-5: gnat paths are wrong due to ada-gcc-name.diff
Severity set to 'serious' from 'important'
> found 814978 6.3.0-5
Bug #814978 [src:gcc-5] gcc-5: gnat paths are wrong due to ada-gcc-name.diff
The source 'gcc-5' and version '6.3.0-5' do not appear to match any binary 
packages
Marked as found in versions gcc-5/6.3.0-5.
> tags 814978 patch
Bug #814978 [src:gcc-5] gcc-5: gnat paths are wrong due to ada-gcc-name.diff
Added tag(s) patch.
> usertags gnat-6
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#852767: marked as pending

[Craig Small]

tag 852767 pending
thanks

Hello,

Bug #852767 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/wordpress.git;a=commitdiff;h=956bd02

---
commit 956bd029374b7fa6e046c055e65a0fcae52a9a18
Author: Craig Small 
Date:   Fri Jan 27 20:32:25 2017 +1100

Stop CSRF with Flash upload

CVE-2017-5489 Cross-Site Request Forgery (CSRF) via Flash Upload
changet 39838 and 39857

diff --git a/debian/changelog b/debian/changelog
index 27c9c07..fce21ef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,22 +1,32 @@
-wordpress (4.1+dfsg-1+deb8u12) jessie-security; urgency=high
+wordpress (4.1+dfsg-1+deb8u12) UNRELEASED; urgency=high
 
   *  Backport patches from 4.7.1 Closes: #851310
- - CVE-2016-10066, CVE-2016-10045 Potential Remote Command
-   Execution (RCE) in PHPMailer
- - CVE-2017-5488 Authenticated Cross-Site scripting (XSS) in
-   update-core.php
- - CVE-2017-5490 Stored Cross-Site Scripting (XSS) via Theme
-   Name fallback
- - CVE-2017-5491 Post via Email Checks mail.example.com by
-   Default
- - CVE-2017-5492 Accessibility Mode Cross-Site Request
-   Forgery (CSRF)
- - CVE-2017-5493 Cryptographically Weak Pseudo-Random
-   Number Generator
+ - CVE-2016-10066
+   Potential Remote Command Execution (RCE) in PHPMailer
+ - CVE-2017-5488
+   Authenticated Cross-Site scripting (XSS) in update-core.php
+ - CVE-2017-5490
+   Stored Cross-Site Scripting (XSS) via Theme Name fallback
+ - CVE-2017-5491
+   Post via Email Checks mail.example.com by Default
+ - CVE-2017-5492
+   Accessibility Mode Cross-Site Request Forgery (CSRF)
+ - CVE-2017-5493
+   Cryptographically Weak Pseudo-Random Number Generator
+ - CVE-2017-5489
+   Cross-Site Request Forgery (CSRF) via Flash Upload
+   Changesets 39838 and 39857, thanks Seb 
   * Not vulnerable
- * CVE-2017-5487 User Information Disclosure via REST API - API doesn't 
exist
-  * Documented not vulnerable but unsure (no changeset or proof of concept)
- * CVE-2017-5489 Cross-Site Request Forgery (CSRF) via Flash Upload
+ - CVE-2017-5487
+   User Information Disclosure via REST API - API doesn't exist
+  * Backport patches from 4.7.2 Closes: #852767
+ - CVE-2017-
+   The user interface for assigning taxonomy terms in Press This is
+   shown to users who do not have permissions to use it.
+ - CVE-2017-
+   WP_Query is vulnerable to a SQL injection (SQLi)
+ - CVE-2017-
+   XSS in the posts list table
 
  -- Craig Small   Sun, 15 Jan 2017 22:57:30 +1100
 

Bug#852767: marked as pending

[Craig Small]

tag 852767 pending
thanks

Hello,

Bug #852767 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/wordpress.git;a=commitdiff;h=f296dbb

---
commit f296dbb87731274d1c499b28fc52f2de542c1f28
Author: Craig Small 
Date:   Fri Jan 27 18:40:02 2017 +1100

changelog: update to 4.7.2

The CVE IDs are not known as yet.

diff --git a/debian/changelog b/debian/changelog
index 3788568..bda9430 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,13 +1,34 @@
+wordpress (4.7.2+dfsg-1) UNRELEASED; urgency=high
+
+  *  New upstream release fixes 3 security issues Closes: #852767
+ - CVE-2017-
+   The user interface for assigning taxonomy terms in Press This is
+   shown to users who do not have permissions to use it.
+ - CVE-2017-
+   WP_Query is vulnerable to a SQL injection (SQLi)
+ - CVE-2017-
+   XSS in the posts list table
+  
+ -- Craig Small   Fri, 27 Jan 2017 18:29:40 +1100
+
 wordpress (4.7.1+dfsg-1) unstable; urgency=high
 
   * New upstream release fixes 8 security issues, Closes: #851310 
-- Cryptographically Weak Pseudo-Random Number Generator
-- Accessibility Mode Cross-Site Request Forgery (CSRF)
-- Post via Email Checks mail.example.com by Default
+- CVE-2017-5493
+  Cryptographically Weak Pseudo-Random Number Generator
+- CVE-2017-5492
+  Accessibility Mode Cross-Site Request Forgery (CSRF)
+- CVE-2017-5491
+  Post via Email Checks mail.example.com by Default
+  CVE-2017-5490
 - Stored Cross-Site Scripting (XSS) via Theme Name fallback
+  CVE-2017-5489
 - Cross-Site Request Forgery (CSRF) via Flash Upload
+  CVE-2017-5488
 - Authenticated Cross-Site scripting (XSS) in update-core.php
+  CVE-2017-5487
 - User Information Disclosure via REST API
+  CVE-2016-10066
 - Potential Remote Command Execution (RCE) in PHPMailer
 
  -- Craig Small   Sat, 14 Jan 2017 09:30:12 +1100

Bug#852709: [debian-mysql] Bug#852709:

[Dieter Adriaenssens]

>
> See also discussion at https://github.com/ottok/mariadb-10.1/pull/8


I guess you mean https://github.com/ottok/mariadb-10.1/pull/7


About my patch, I wrongfully assumed the architecture names were wildcards
for all platforms. Thanks for pointing this out and for the improved patch,
James Clarke.

-- 
Kind regards,

Dieter Adriaenssens

Processed: Bug#852767 marked as pending

[Debian Bug Tracking System]

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

> tag 852767 pending
Bug #852767 [src:wordpress] wordpress: 4.7.2 security release
Ignoring request to alter tags of bug #852767 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#852532: Acknowledgement (olvwm: source code not 64-bit clean, SIGSEGV everywhere)

[Adam M. Costello]

I retract "SIGSEGV everywhere".  If I compile client.c with -O0, then
the third SIGSEGV is avoided, and I don't see any others.

Summary: olvwm runs on my system only if I make all three of these
changes, each of which avoids a SIGSEGV:

In cursors.c, remove (int) from this line:
st_insert(cursorTable, (int) p->name, (char *) p->num);

In image.c, #include "mem.h".

Compile client.c with -O0.

Alternatively, the first two SIGSEGVs (but not the third) can be avoided
by making no code changes but instead linking with -no-pie.

AMC

Bug#849122: new version of wpa-supplicant uploaded -- please test

[data cruncher]

Hi

I tried this new version, and it didn't work.
Then i tried with the mac randomization 'off', and it works.
I tried also the previous version (2.6-2, where the bug first happened),
and with randomization on 'off', it works as well.

Regards

On Thu, Jan 26, 2017 at 6:36 PM, Andrew Shadura  wrote:

> Hi everyone,
>
> I have cherry-picked a few patches from the upstream Git repository.
>
> While I don't have much hope they fix all of your issues, there's still
> some chance they do improve the state of things.
>
> Please test this version, ensuring you have the latest NM/wicd/whatever
> installed, making sure you don't have misconfigurations with MSCHAPv2 as
> in [1], and you have MAC randomisation disabled as in [2].
>
> If by any chance you're not observing your symptoms any longer, please
> report here, and if you have enough time, try reverting [2] and seeing
> whether that breaks it again or not — and report here again.
>
> Thanks.
>
> [1]:
> https://wiki.archlinux.org/index.php/WPA_supplicant#
> Problems_with_eduroam_and_other_MSCHAPv2_connections
>
> [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077#50
>
> --
> Cheers,
>   Andrew
>
>

Processed: reopening 852250

[Debian Bug Tracking System]

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

> reopen 852250
Bug #852250 {Done: Mathieu Parent } [lua-socket] 
[lua-socket] luasocket was not compiled with UNIX sockets support
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions luasocket/3.0~rc1+git+ac3201d-3.
> thanks
Stopping processing here.

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

Processed: tagging 852457

[Debian Bug Tracking System]

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

> tags 852457 + sid
Bug #852457 [src:myodbc] myodbc: switch to build depend on the metapackage 
default-libmysqlclient-dev
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#846848: marked as done (check-mk: Provides binary package for nagios3 which has been removed from unstable)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jan 2017 07:48:44 +
with message-id 
and subject line Bug#846848: fixed in check-mk 1.2.8p16-1
has caused the Debian Bug report #846848,
regarding check-mk: Provides binary package for nagios3 which has been removed 
from unstable
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.)


-- 
846848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: check-mk
Version: 1.2.6p12-1
Severity: normal
Tags: patch

Dear Maintainer,

Please update your package to deal with the nagios3 removal from Debian
(#845765).

Consider applying the attached patch.

Kind Regards,

Bas
>From 6a4eb878a7c58b971833e6f38fea528069a7facc Mon Sep 17 00:00:00 2001
From: Bas Couwenberg 
Date: Sat, 3 Dec 2016 18:12:35 +0100
Subject: Drop binary package for nagios3 which is no longer in Debian.

---
 debian/README.Debian| 13 ++
 debian/apache.nagios3   | 76 --
 debian/changelog|  7 +++
 debian/check-mk-config-nagios3.install  |  2 -
 debian/check-mk-config-nagios3.links|  2 -
 debian/check-mk-config-nagios3.postinst | 83 -
 debian/check-mk-config-nagios3.postrm   | 32 -
 debian/check-mk-config-nagios3.preinst  | 10 
 debian/check-mk-config-nagios3.prerm|  0
 debian/control  | 19 +---
 debian/defaults.nagios3 | 54 -
 debian/rules|  5 --
 12 files changed, 14 insertions(+), 289 deletions(-)
 delete mode 100644 debian/apache.nagios3
 delete mode 100644 debian/check-mk-config-nagios3.install
 delete mode 100644 debian/check-mk-config-nagios3.links
 delete mode 100644 debian/check-mk-config-nagios3.postinst
 delete mode 100644 debian/check-mk-config-nagios3.postrm
 delete mode 100644 debian/check-mk-config-nagios3.preinst
 delete mode 100644 debian/check-mk-config-nagios3.prerm
 delete mode 100644 debian/defaults.nagios3

diff --git a/debian/README.Debian b/debian/README.Debian
index 46f1a9b..d51b733 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -1,12 +1,9 @@
 check-mk-livestatus
 ===
 
-To load the event broker add the following lines to your Nagios/Icinga
+To load the event broker add the following lines to your Icinga
 configuration:
 
-Nagios3:
-broker_module=/usr/lib/check_mk/livestatus.o /var/lib/nagios3/rw/live
-
 Icinga:
 broker_module=/usr/lib/check_mk/livestatus.o /var/lib/icinga/rw/live
 
@@ -25,10 +22,10 @@ On the server side you need multisite enabled to see the logs. If you also want
 to acknowledge the alarms (recommended) put www-data into the nagios group
 
 
-check-mk-config-nagios3 and check-mk-config-icinga
-==
+check-mk-config-icinga
+==
 
 Check-MK's web frontend "Multisite" (package "check-mk-multisite") and the
-server part of Check-MK ("check-mk-server") can only be used with either
-Nagios3 or Icinga. Please install the adequate "check-mk-config-*" package.
+server part of Check-MK ("check-mk-server") can only be used with Icinga.
+Please install the "check-mk-config-icinga" package.
 
diff --git a/debian/apache.nagios3 b/debian/apache.nagios3
deleted file mode 100644
index 1cc690e..000
--- a/debian/apache.nagios3
+++ /dev/null
@@ -1,76 +0,0 @@
-# Created by setup of check_mk version 1.2.6p12
-# This file will *not* be overwritten at the next setup
-# of check_mk. You may edit it as needed. In order to get
-# a new version, please delete it and re-run setup.sh.
-
-# Note for RedHat 5.3 users (and probably other version:
-# this file must be loaded *after* python.conf, otherwise
-#  does not trigger! For that
-# reason, it is installed as zzz_ Sorry for the
-# inconveniance.
-
-
-  Alias /check_mk /usr/share/check_mk/web/htdocs
-  
-AddHandler mod_python .py
-PythonHandler index
-PythonDebug On
-	DirectoryIndex index.py
-
-#Handle apache 2.2 and 2.4
-= 2.3>
-Require local
-
-
-Order deny,allow
-allow from all
-
-	# Need Nagios authentification. Please edit the
-	# following: Set AuthName and AuthUserFile to the
-	# same value that you use for your Nagios configuration!
-Order deny,allow
-allow from all
-	AuthName "Nagios Access"
-AuthType Basic
-AuthUserFile /etc/nagios3/htpasswd.users
-  

Processed: mricron FTBFS on armhf: parconvert.s:3121: Error: co-processor offset out of range

[Debian Bug Tracking System]

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

> clone 851834 -1
Bug #851834 [src:mricron] mricron FTBFS on armhf: parconvert.s:3121: Error: 
co-processor offset out of range
Bug 851834 cloned as bug 852798
> reassign -1 fpc
Bug #852798 [src:mricron] mricron FTBFS on armhf: parconvert.s:3121: Error: 
co-processor offset out of range
Bug reassigned from package 'src:mricron' to 'fpc'.
No longer marked as found in versions mricron/0.20140804.1~dfsg.1-2.
Ignoring request to alter fixed versions of bug #852798 to the same values 
previously set
> retitle -1 fpc: Error: co-processor offset out of range on armhf
Bug #852798 [fpc] mricron FTBFS on armhf: parconvert.s:3121: Error: 
co-processor offset out of range
Changed Bug title to 'fpc: Error: co-processor offset out of range on armhf' 
from 'mricron FTBFS on armhf: parconvert.s:3121: Error: co-processor offset out 
of range'.
> severity -1 normal
Bug #852798 [fpc] fpc: Error: co-processor offset out of range on armhf
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: Bug#852767 marked as pending

[Debian Bug Tracking System]

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

> tag 852767 pending
Bug #852767 [src:wordpress] wordpress: 4.7.2 security release
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Michael Meskes]

On Wed, Jan 25, 2017 at 10:48:43PM +0100, Mathieu Parent wrote:
The patch does not seem to work. I just installed 
lua-socket_3.0~rc1+git+ac3201d-3_amd64.deb manually, re-started prosody and got 
'luasocket was not compiled with UNIX sockets support' again.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#852008: gprolog: non-standard gcc/g++ used for build (gcc-5)

[James Cowgill]

On Fri, 20 Jan 2017 18:21:39 +0100 Matthias Klose  wrote:
> Package: src:gprolog
> Version: 1.4.5-4
> Severity: serious
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: non-standard-compiler, gcc-5, gcc-5-legacy
> 
> This package builds with a non standard compiler version; please check
> if this package can be built with the default version of gcc/g++, or
> with gcc-6/g++-6.

It looks like the original GCC ICE (which is the reason gcc-5 is used)
might be this upstream bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78580

However it is only fixed in gcc-7 at the moment.

James



signature.asc
Description: OpenPGP digital signature

Bug#851513: Unstable upload

[Jonathan Carter]

An unstable upload would be great. The 4.9 kernel hit stable so this is
starting to become a problem for people who are testing stretch already
and I'm sure they'll all appreciate it.

Bug#851379: dietlibc FTBFS on arm64: Bus error when running tst-calloc.c

[Christian Seiler]

On 01/26/2017 10:17 PM, Thorsten Glaser wrote:
> Christian Seiler dixit:
>> -g, and generate a backtrace? That might already help me to figure
>> out what's going on...
> 
> Recursive calls; the SIGBUS is likely a stack underflow.

So it looked at this yesterday evening and I couldn't really make heads
or tails from the backtrace, so let's try this again with a fresh pair
of eyes.

I would expect stack exhaustion to cause a SIGSEGV, but not a SIGBUS.
Example:

void foo()
{
  char a[8192];
  a[0] = '\0';
  // Prevent tail-recursion optimization by the compiler:
  void (* volatile bar)() = 
  bar();
  (void) a;
}

int main()
{
  foo();
  return 0;
}

This segfaults, but doesn't generate SIGBUS.

> (gdb) set pagination off
> (gdb) r
> Starting program: /home/tg/dietlibc-0.34~cvs20160606/debian/unittests/ttt
> [Inferior 1 (process 29556) exited normally]
> (gdb) r
> Starting program: /home/tg/dietlibc-0.34~cvs20160606/debian/unittests/ttt
> 
> Program received signal SIGBUS, Bus error.
> 0x00401740 in __testandset ()
> (gdb) bt
> #0  0x00401740 in __testandset ()
> #1  0x004016a0 in __pthread_lock ()
> #2  0x004016a0 in __pthread_lock ()
> #3  0x004016a0 in __pthread_lock ()
> #4  0x004016a0 in __pthread_lock ()
> #5  0x004016a0 in __pthread_lock ()

I don't think this is stack exhaustion; I think the stack frame
is being corrupted here and that's why gdb can't figure out the
proper stack frame.

> (sid_arm64-dchroot)tg@asachi:~/dietlibc-0.34~cvs20160606$ gdb 
> debian/unittests/ttt
> Breakpoint 1, 0x00401674 in __pthread_lock ()
> (gdb) bt
> #0  0x00401674 in __pthread_lock ()
> #1  0x00400858 in __thread_find_ ()
> #2  0x00400894 in __thread_self ()
> #3  0x0040059c in malloc ()
> #4  0x0040059c in malloc ()
> #5  0x0040059c in malloc ()
> #6  0x0040059c in malloc ()
> #7  0x0040059c in malloc ()
> […]

This would also indicate stack frame corruption (and hence gdb
being unable to properly trace this), because malloc() (see
libpthread/pthread_sys_alloc.c) does _not_ call itself directly.

> Your debian/patches/bugfixes/thread-self-vs-tcb.diff replaces the inline
> assembly implementation of __thread_self with one ending up recursively
> calling a chain malloc → __thread_self → __thread_find_ → __pthread_lock
> probably because it uses some structure that needs to be malloc(3)ed to
> work, but is needed for malloc(3) to function.

No, because __thread_self and __thread_find_ and __pthread_lock
never call malloc().

If that were the case, you'd see that loop in the stack trace,
and not just the same function repeated over and over again.

Whether this is a stack exhaustion or not can easily be seen:

Print the current stack pointer in gdb:
print $sp

Look at /proc/$PID/maps to see in which range the stack resides.
I'd be surprised if $sp was even close to the lower end of that
address range.

Unfortunately, if the stack frame really is corrupted, I'd really
need to look at this on the porterbox directly (because I don't
think it's a productive use of both of our time to do this via
email), so I'll have to wait until I get my account.

Regards,
Christian

Bug#832931: (no subject)

[Otto Kekäläinen]

2017-01-27 9:18 GMT+02:00 Otto Kekäläinen :
> Please also note the related
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852728 and PR at
> https://github.com/ottok/mariadb-10.1/pull/8

Actually Bug#852728 has nothing to do with this, my mistake. But the
PR is relevant.

(I seem to be making stupid mistakes way too much now, maybe I should
take a break from this topic and continue with fresh eyes later.)

Bug#852781: openssh-server: Wrong default for setting PermitRootLogin (yes instead of prohibit-password) in clean install

[lopiuh]

Package: openssh-server
Version: 1:7.4p1-6
Severity: serious
Justification: Policy 10.7.3

Dear Maintainer,

as discussed in https://lists.debian.org/debian-ssh/2017/01/msg00059.html
PermitRootLogin gets wrong default in /etc/ssh/sshd_config

   * What led up to the situation?
Clean installation, no old config file (/etc/ssh/sshd_config) present
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
nothing special
   * What was the outcome of this action?
[...]
#LoginGraceTime 2m
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
[...]
   * What outcome did you expect instead?
[...]
#LoginGraceTime 2m
PermitRootLogin prohibit-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
[...]


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages openssh-server depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  dpkg   1.18.18
ii  init-system-helpers1.47
ii  libaudit1  1:2.6.7-1
ii  libc6  2.24-9
ii  libcomerr2 1.43.3-1
ii  libgssapi-krb5-2   1.15-1
ii  libkrb5-3  1.15-1
ii  libpam-modules 1.1.8-3.5
ii  libpam-runtime 1.1.8-3.5
ii  libpam0g   1.1.8-3.5
ii  libselinux12.6-3
ii  libssl1.0.21.0.2k-1
ii  libsystemd0232-14
ii  libwrap0   7.6.q-26
ii  lsb-base   9.20161125
ii  openssh-client 1:7.4p1-6
ii  openssh-sftp-server1:7.4p1-6
ii  procps 2:3.3.12-3
ii  ucf3.0036
ii  zlib1g 1:1.2.8.dfsg-4

Versions of packages openssh-server recommends:
ii  libpam-systemd  232-14
ii  ncurses-term6.0+20161126-1
ii  xauth   1:1.0.9-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- debconf-show failed