Bug#872970: ITP: ukui-themes -- official themes for the UKUI desktop

[Aron Xu]

Package: wnpp
Severity: wishlist

Package name: ukui-themes
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/ukui-themes
License : GPL-2+
Description : official themes for the UKUI desktop

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.


Regards,
Aron Xu

Bug#872969: ITP: ukui-session-manager -- session manager of the UKUI desktop environment

[Aron Xu]

Package: wnpp
Severity: wishlist

Package name: ukui-session-manager
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/ukui-session-manager
License : GPL-2+
Description : session manager of the UKUI desktop environment

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.


Regards,
Aron Xu

Bug#872968: ITP: ukui-screensaver -- UKUI screen saver and locker

[Aron Xu]

Package: wnpp
Severity: wishlist


Package name: ukui-screensaver
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/ukui-screensaver
License : GPL-2+
Description : UKUI screen saver and locker

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.


Regards,
Aron Xu

Bug#872967: ITP: ukui-menu -- advanced UKUI menu

[Aron Xu]

Package: wnpp
Severity: wishlist

Package name: ukui-menu
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/ukui-menu
License : GPL-2+
Description : advanced UKUI menu

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.


Regards,
Aron Xu

Bug#872965: ITP: peony -- file manager for the UKUI desktop

[Aron Xu]

Package: wnpp
Severity: wishlist

Package name: peony
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/peony
License : GPL-2+
Description : file manager for the UKUI desktop

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.


Regards,
Aron Xu

Bug#872966: ITP: ukui-indicators -- indicators of UKUI desktop

[Aron Xu]

Package: wnpp
Severity: wishlist


Package name: ukui-indicators
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/ukui-indicators
License : GPL-2+
Description : indicators of UKUI desktop

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.

Regards,
Aron

Bug#872964: ITP: ukui-control-center -- control center of UKUI

[Aron Xu]

Package: wnpp
Severity: wishlist


Package name: ukui-control-center
Version : 1.0.3
Upstream Author : Kylin Team 
URL : https://github.com/ukui/ukui-control-center
License : GPL-2+
Description : control center of UKUI

UKUI is a fork of MATE desktop, targeting to be a lightweight desktop
environment for a simpler and more enjoyable experience.


Regards,
Aron Xu

Bug#872896: debian-policy: An html.tar.gz has leaked into the .deb?

[Russ Allbery]

Control: tags -1 pending

Guillem Jover  writes:

> It seems that an html.tar.gz has leaked (?) into the .deb, which
> contains the single single html file plus ancillary files. It is
> not clear whether this is an intentional change as it's not listed
> on the changelog. It looks at least a bit redundant.

Fixed.  Thanks!

-- 
Russ Allbery (r...@debian.org)   

Bug#872900: debian-policy: Very generic info file name

[Russ Allbery]

Guillem Jover  writes:

> While I'm not a very big fan of info files (even when using pinfo),
> it seems for now it's the only way to get section numbers w/o having
> to use a browser. :/ So while using it I noticed that it has been
> installed with an extremely generic name, for something that is a
> global resource. I think it should be renamed to debian-policy.

Fixed in Git.  Thanks!

-- 
Russ Allbery (r...@debian.org)   

Bug#872950: debian-policy: Too much indirection in info file menus

[Russ Allbery]

Control: tags -1 pending

Guillem Jover  writes:

> The info file, on its initial page contains a Menu with the following
> entries:

> ,---
> * Menu:

> * Version::
> * Contents::
> * Legal Notice::
> `---

> For which Version contains a one-liner. It would be nicer if Contents
> would get expanded into the main Menu.

I managed to fix this as well by leaving out the section headings in the
top-level document.

-- 
Russ Allbery (r...@debian.org)   

Bug#865999: [exiv2] Please package exiv2 0.26

[Fulano Diego Perez]

Package: exiv2
Version: 0.25-3.1

also adds support for webp images which is currently missing ...

Bug#872893: debian-policy: Chapters, sections, appendices and numbering

[Russ Allbery]

Control: tags -1 pending

Guillem Jover  writes:

> The appendices are also not easily distinguishable from the other
> sections as they also use numbers intead of say letters.

This is https://github.com/sphinx-doc/sphinx/issues/2502.  I'm going to
close out this specific bug number against Policy by fixing the numbering
and nesting for the main chapters, since I think the appendix numbering is
liveable, but we'll definitely fix this if some solution materializes.

-- 
Russ Allbery (r...@debian.org)   

Bug#844528: Same here

[Mario Lang]

Hi.

I am preparing a custom PXE+TFTP+Rsync-based cluster setup and just
discovered that Debian is missing systemd-firstboot.  It would be quite
nice to be able to call this from my initramfs script.

Since I am using stable, I am stuck here anyway.
But please consider shipping this tool, it is documented all over the
net and it is not immediately obvious to a random user like me why it
was excluded.  Feels like a slightly crippled package now.

I understand that Debian does its installation initialisation
differently.  But given that it is easy to debootstrap and
systemd-nspawn into a chroot, it would be nice to be able to do the
initialisation of essential things after debootstrap with
systemd-firstboot.  After all, Debian has decided to go for systemd.
Why not all the way?

-- 
AR Mario Lang   Phone: +43 316 873 6897
Graz University of Technology  Mobile: +43 664 60 873 6897
IT-Services for research and teaching   Email: ml...@tugraz.at
Steyrergasse 30/1, 8010 Graz, Austriawww.zid.tugraz.at

Bug#872893: debian-policy: Chapters, sections, appendices and numbering

[Russ Allbery]

Guillem Jover  writes:

> Well, that's unfortunate. :( And I've just noticed on the info files
> it's just worse as they do not get their section numbers reset so
> they keep incrementing from the last chapter index. For example
> «Binary packages (…)» used to be appendix B, now it's 2, but on the
> info file it's 14.

Yeah, both the info and PDF documentation have that issue, but HTML
doesn't.  I haven't looked at epub, but it's probably just the HTML output
in another form.

-- 
Russ Allbery (r...@debian.org)   

Bug#872893: debian-policy: Chapters, sections, appendices and numbering

[Russ Allbery]

Guillem Jover  writes:

> At least on the PDF output, the section numbers are wrong, as there are
> now two chapters that include the old sections.

I think I've fixed this.  For reference, the first problem was the
headings in the top-level document for the abstract and the license.  When
I fixed that, Sphinx got a bit more confused, but adding the document
title with the highest-level heading (as documented in the Sphinx docs)
seems to have cleaned that up.

The license got appended to the end of the upgrading checklist if it was
just at the end of the top-level index, so I made it a separate appendix.
The alternative was to put it in front of the main text, and that seemed
awkward.

> The appendices are also not easily distinguishable from the other
> sections as they also use numbers intead of say letters.

This unfortunately really doesn't seem to be fixable in Sphinx right now,
which is frustrating.  :(  But it's more incentive to get rid of the
packaging manual appendices, which are basically long-standing technical
debt, and incorporate that material directly into Policy.  That leaves the
process and the upgrading checklist, which I think could be just left as a
final section of the document.

-- 
Russ Allbery (r...@debian.org)   

Bug#866727: Also affects Ubuntu

[era]

This also affects Ubuntu and has been reported in the wild by users
upgrading from earlier versions of the distro.

https://bugs.launchpad.net/debian/+source/oneliner-el/+bug/1586145

(Notice also the recent duplicate if you have trouble with the error
messages being in German.)

The problem might be with the apel package, which is what provides poe
but I have been unable to spot anything obvious like a particular
version in which poe was added (it's been there like forever; the
changelog mentions it in 2009).

-- 
If this were a real .signature, it would suck less.  Well, maybe not.

Bug#859639: linux-image-4.9.0-2-amd64: random crashes on Thinkpad X201s

[Uwe Laverenz]

Hi,

this is not helpful for Debian Stretch users but just for the record:

The problem seems to be fixed in newer kernels, I don't see the error 
messages or any flickering with kernel 4.12.5-300 on Fedora 26. The 
system works perfectly with modesetting, no workaround needed.


hth,
Uwe

Bug#872944: www.debian.org: Debian Policy Manual not fully published

[Russ Allbery]

Sean Whitton  writes:

> The Debian Policy Manual just changed its HTML output and while the HTML
> has published, the CSS and included images have not.

> Looking at [1], the CSS and included images should have been published
> because they're still installed to
> /usr/share/doc/debian-policy/policy.html/.  So I think this is a problem
> on your end rather than ours.  Please do reassign this bug if I'm wrong
> about that, and thanks in advance for your help.

> [1]  https://anonscm.debian.org/cgit/debwww/cron.git/tree/parts/7doc

Hi debian-www folks,

Just a heads-up that we're fixing some more stuff and Policy 4.1.1.0 will
be a bit different again (it's not yet uploaded).  Here's what I currently
have staged for the next version:

* usr/share/doc/debian-policy/policy.html/ in the package will have the
  multi-file HTML version.  This is a directory with a couple of
  subdirectories, and all the internal HTML links should be relative.
  However, please note that some of the Javascript is symlinks to files
  that are shipped in the libjs-sphinxdoc package, so you may need a bit
  of machinery to turn those symlinks into real files.

* usr/share/doc/debian-policy/policy-1.html will be the single-file HTML
  version.  However, the Sphinix single-file version still requires static
  assets in usr/share/doc/debian-policy/{_images,_static} that will need
  to be in the right position relative to policy-1.html.  These have the
  same symlinks to libjs-sphinxdoc.

The current state in the archive right now only has the single-file
version, and it is in the policy.html subdirectory.  But we got feedback
after this release that people really wanted both versions available.

Unfortunately things might be just a touch chaotic for a bit as we work
through finishing this reStructuredText conversion.  Apologies for the
extra work!  We think the long-term result will be worth it both in terms
of better output and in terms of a more maintainable Policy document.

-- 
Russ Allbery (r...@debian.org)   

Bug#872895: debian-policy: Split html for policy lost

[Russ Allbery]

Control: tags -1 pending

Guillem Jover  writes:

> This version has lost the distinction between a single policy html and
> the one with different files per chapter. This will break links.

Okay, I think this is fixed in Git and Policy should now ship both the
single-file and the multi-file versions in the same directories they were
in before the conversion to reStructuredText.  The multi-file version is
in policy.html and the single-file version is policy-1.html.

This also required adding _static and _images to the top-level of the
usr/share/doc directory because single-file from Sphinx isn't strictly
single file (and we have images now), but I think it should all work.  The
tricky part will be on the debian-www side in copying things over.  I'll
give them a warning that more changes are coming.

-- 
Russ Allbery (r...@debian.org)   

Bug#868659: updating erlang-proper in sid

[Nobuhiro Iwamatsu]

Hi,

I am sorry for the late reply.
I just upload packaged today's upstream HEAD to unstable.

Best regards,
  Nobuhiro

2017-08-14 15:43 GMT+09:00 Philipp Huebner :
> Hi,
>
> #868659 is threatening to remove ejabberd from testing.
>
> If you don't have time to update erlang-proper soon,
> would it be okay for you if I add myself as uploader and do it myself
> next week?
>
> Kind regards,
> --
>  .''`.   Philipp Huebner 
> : :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
> `. `'`
>   `-
>



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#872299: gnome-orca: Orca segfaults on startup

[Tim Smith]

Here's the generated core file:

https://www.dropbox.com/s/94ymmn8uhmdyge4/core?raw=1

Tim

On Tue, Aug 22, 2017 at 6:32 PM, Samuel Thibault 
wrote:

> Hello,
>
> MENGUAL Jean-Philippe, on mer. 16 août 2017 01:21:18 +0200, wrote:
> > Fatal Python error: Segmentation fault
>
> Could you run
>
> ulimit -c unlimited
>
> just before starting orca from the same shell, and put the generated
> core file somewhere for download?
>
> Samuel
>

Bug#872963: apt-ftparchive: Passes through hashes even when explictly disabled.

[Unit 193]

Package: apt-utils
Version: 1.5~beta1
Severity: normal

Dear Maintainer,

When passing options such as APT::FTPArchive::SHA1=false to ftparchive, hashes 
for the source and Debian tarballs are still added to Sources and only the dsc 
is skipped.  This causes warnings from eg, the census tools.

I'd expect when a hash type is disabled, then none of the hashes of that type 
are generated.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages apt-utils depends on:
ii  apt 1.5~beta1
ii  libapt-inst2.0  1.5~beta1
ii  libapt-pkg5.0   1.5~beta1
ii  libc6   2.24-14
ii  libdb5.35.3.28-13
ii  libgcc1 1:7.1.0-13
ii  libstdc++6  7.1.0-13

apt-utils recommends no packages.

apt-utils suggests no packages.

-- no debconf information

Bug#871220: gcc-doc-defaults: FTBFS with GCC-7

[Guo Yixuan]

Control: block -1 by 872959 872961
Control: tag -1 + pending

Hello,

On Sun, Aug 6, 2017 at 8:58 PM, Adam Borowski  wrote:
>
> > gcc-doc-defaults FTBFS since GCC-7 was made the default compiler:
>
> Which raises a question: where's gcc-7-doc?

I'm going to have a new upload, but before that, gcc-7-doc(ITP) and
gcc-6-doc
needs to be uploaded.

https://anonscm.debian.org/gitweb/?p=users/yixuan-guest/gcc-doc-defaults.git

Yixuan

Bug#872962: RFS: gcc-7-doc/7.2.0-1 [ITP]

[郭溢譞]

Package: sponsorship-requests
Severity: normal
Control: block 872959 by -1

Dear mentors,

  I am looking for a sponsor for my package "gcc-7-doc"

Package description:

* Package name: gcc-7-doc
  Version : 7.2.0-1
  Upstream Author : FSF
* URL : https://gcc.gnu.org/
* License : GFDL-1.3+, with invariant sections
  Programming Lang: Texinfo
  Description : documentation for the GNU compilers (gcc, gobjc, g++)
  Section : non-free/doc
  Vcs-Browse  : 
https://anonscm.debian.org/cgit/users/yixuan-guest/gcc-doc.git/log/?id=refs/heads/debian/7

This package contains manual pages and documentation in info, html,
and pdf format, for the GNU compilers.

The documentation is licensed under the terms of the GNU Free
Documentation License, and contains invariant sections, so it can't be
part of Debian main. (See gcc-6-doc as an example.)

It builds those binary packages:

 cpp-7-doc  - documentation for the GNU C preprocessor (cpp)
 gcc-7-doc  - documentation for the GNU compilers (gcc, gobjc, g++)
 gccgo-7-doc - documentation for the GNU Go compiler (gccgo)
 gfortran-7-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-7-doc - documentation for the GNU Ada Compiler (gnat)

Changes for this upload (based on gcc-6-doc):
 gcc-7-doc (7.2.0-1) unstable; urgency=medium
 .
   * New upstream branch. (Closes: #872959)
   * Synced patches with gcc-7, 7.2.0-1.
   * Removed gcj-*-doc package, removed upstream.

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/gcc-7-doc

Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/non-free/g/gcc-7-doc/gcc-7-doc_7.2.0-1.dsc

More information about hello can be obtained from https://www.example.com.

Thanks,
Yixuan

Bug#872961: RFS: gcc-6-doc/6.4.0-1

[郭溢譞]

Package: sponsorship-requests
Severity: normal


Dear mentors,

I am looking for a sponsor for my package "gcc-6-doc"

Changes for this upload:
gcc-6-doc (6.4.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Dropped gcov-fix.diff and small-error.diff.
   * Synced patches with gcc-6, 6.4.0-4.
   * Bumped standards version to 4.0.0, no changes needed.
   * Updated extract-doc-tarball-from-upstream to python3.

Git repo: https://anonscm.debian.org/gitweb/?p=users/yixuan-guest/gcc-doc.git 
branch debian/6

  It builds those binary packages:

 cpp-6-doc  - documentation for the GNU C preprocessor (cpp)
 gcc-6-doc  - documentation for the GNU compilers (gcc, gobjc, g++)
 gccgo-6-doc - documentation for the GNU Go compiler (gccgo)
 gcj-6-doc  - documentation for the GNU Java tools (gcj, gij)
 gfortran-6-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-6-doc - documentation for the GNU Ada Compiler (gnat)

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/gcc-6-doc


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/non-free/g/gcc-6-doc/gcc-6-doc_6.4.0-1.dsc


Thanks,
GUO Yixuan

Bug#872561: sollya: FTBFS on armhf arch

[Steve Langasek]

Control: severity -1 serious

A regression in architecture support is a serious bug by default, and will
block the new version of this package from being published to testing unless
you arrange with the ftpmasters to have the old binaries removed.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#872553: More information

[Cristian Hernán Schmidt]

Upgrade the kernel (4.11.0-1-amd64 -> 4.12.0-1-amd64) and run "xhost
+si:localuser:root", synaptic works again (must run the xhost on each
login).

Bug#846296: ext4 checksum error

[Theodore Ts'o]

Hi, sorry for not responding earlier.  For some reason your bug report
got caught in a spam trap, and the relatively vague subject line meant
I didn't really notice it in the Debian bugs patch for e2fsprogs.
Apologies for that!

What you are seeing is pretty clearly a kernel bug, and not a bug in
e2fsprogs.  So a few questions, if you don't mind:

1) Are you still seeing the problem with a newer kernel?  What's the
latest kernel have you tried?

2) After the failure, have you tried fixing the file system using
e2fsck -f?  What problems, if any, did e2fsck find?

3) Are you using selinux, or are you using extended attributes or
ACL's in your file system?  (There was a bug fixed a while back that
involved races in code when both xattr's and checksums were in use.)

Many thanks,

- Ted

Bug#872888: Not running radsecproxy as root / circumvent a systemd flaw with PID files / dependency on debhelper >=10

[Faidon Liambotis]

Hi Christian!

First off, thanks for the very detailed and constructive bug report!
For future bug reports, please note that it's helpful to keep each issue
in a separate bug report that can be responded to and fixed
independently -- even if that means more bug reports for me to deal
with! :)

On Tue, Aug 22, 2017 at 07:04:18AM +, Christian Strauf wrote:
> (1) There seems to be a flaw in some versions of systemd which
> concerns PID files. If a PID file of a service is manipulated (e. g.
> to contain the value "1"), stopping the service will kill the process
> whose process ID has been added to the PID file. To circumvent this
> you can omit writing a PID file if the daemon allows it. radsecproxy
> is simple enough so that systemd knows the PID after starting it, so
> not writing a PID file isn't a problem in this case. This is what I'd
> suggest for this package. The patch is included in the patch suggested
> for issue (2).

This sounds like a bug in systemd and should probably be addressed
there. Do you know which versions are affected and/or do have a
reference to that flaw?

As far as radsecproxy's unit goes, I think actually the right solution
would be to avoid daemonization altogether and switch to Type=simple.
I've experimented with that, but unfortunately, there are some nasty
side effects with radsecproxy's -f (foreground) option with regards to
logging. I've already raised that with Linus (upstream), as the first
step.

> (2) Right now, radsecproxy is running as root. I'd like to propose the
> following patch so that it's run a an unprivileged user "radsecproxy":

That's a good point! I don't know how I've missed this. I'll have a look
at doing this in the next upload.

> (3) This issue is more a question than a bug report or suggestion.
> Right now the control file has the dependency "debhelper (>= 10)". Is
> this a hard dependency? If not, can it be changed to "debhelper (>=
> 9)" again?

There are various changes between debhelper 9 and 10 (e.g. running
autoreconf by default). In general, there is little downsides with
following the latest debhelper version and I prefer doing that.

If your goal is to build a backport for an older Debian version, you can
either downgrade the dependency in your backport yourself, or even
better, just install debhelper 10, a build-time only dependency, in your
older system. 10.2.5 is available in jessie-backports, precisely because
a lot of newer packages need newer version of debhelper.

> Thanks again for providing this package, it's highly appreciated!

You're very welcome!

Best,
Faidon

Bug#872893: debian-policy: Chapters, sections, appendices and numbering

[Russ Allbery]

Guillem Jover  writes:
> On Tue, 2017-08-22 at 10:44:32 -0700, Sean Whitton wrote:

>> Could you explain "two chapters that include the old sections", please?
>> Or just say which sections are wrong.

>> We tried hard to avoid this, so it's definitely a bug.

> Take section «10.9.1. The use of dpkg-statoverride», this is correct on
> the HTML output and info file, on the PDF it's a section w/o a number
> inside §2.10.9. I've not checked the EPUB file.

Yeah, Sphinx is doing something really weird with how it does section
numbering.  It's counting the top-level document as having three sections
and embedding the contents in section "2" and pushing everything down.
This is the same problem the info documentation is having.

I'll take a look and try to figure out some solution.

-- 
Russ Allbery (r...@debian.org)   

Bug#871310: gcc.1: Some point size changes are wrong in the manual

[Guo Yixuan]

Hello,

On Mon, Aug 7, 2017 at 11:20 AM, Bjarni Ingi Gislason 
wrote:
>
> Package: gcc-6-doc
> Version: 6.3.0-1
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> "man gcc" with
>
> MAN_KEEP_STDERR=yes
> MANOPT=--encoding=latin1 --no-hyphenation --warnings=w --no-justification
> MANWIDTH=80
>
>* What was the outcome of this action?
>
> :3310: warning: \s escape results in non-positive point
size; set to 1
> :3311: warning: \s escape results in non-positive point
size; set to 1
> :25: backtrace: string `C+'
> :3311: warning: \s escape results in non-positive point
size; set to 1
> :3320: warning: \s escape results in non-positive point
size; set to 1
> :3323: warning: \s escape results in non-positive point
size; set to 1
> :3326: warning: \s escape results in non-positive point
size; set to 1
> :3331: warning: \s escape results in non-positive point
size; set to 1
> :: warning: \s escape results in non-positive point
size; set to 1
> :: warning: \s escape results in non-positive point
size; set to 1
> :3336: warning: \s escape results in non-positive point
size; set to 1
> :3337: warning: \s escape results in non-positive point
size; set to 1
> :4668: warning: \s escape results in non-positive point
size; set to 1
> :25: backtrace: string `C+'
> :4668: warning: \s escape results in non-positive point
size; set to 1
> :4670: backtrace
> /home/bg/git/groff/tmac/an-old.tmac:493: backtrace: macro `IP'
> :4670: warning: \s escape results in non-positive point
size; set to 1
> :4670: backtrace
> /home/bg/git/groff/tmac/an-old.tmac:493: backtrace: macro `IP'
> :4670: warning: \s escape results in non-positive point
size; set to 1
> :9001: warning [p 93, 4.5i]: can't break line
> :9023: warning [p 93, 8.2i]: can't break line
> :9234: warning [p 95, 7.3i]: can't break line
>
>* What outcome did you expect instead?
>
>   No warnings
>
>   The escape '\s0' does not get the right former size if another '\s0'
comes
> after it (like '\s-1...\s-2...\s0...\s0').
>
>   The string '\*(C+' gets resized in the manual for "gcc" in some lines.
>   Each use of this string gets the previous size smaller, the warning is
not
> issued until the size is down to less than 1 point.
>
> Patch:
>
> --- gcc.1   2017-08-07 14:54:44.0 +
> +++ gcc.1.new   2017-08-07 14:55:41.0 +
> @@ -22,7 +22,7 @@
>  .\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
>  .\" nothing in troff, for use with C<>.
>  .tr \(*W-
> -.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
> +.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s+2\v'.1v'\h'-1p'
>  .ie n \{\
>  .ds -- \(*W-
>  .ds PI pi
>
>   And then change all the '\s0' into the correct escape (\s-1 ... \s0)
>
> sed -e 's/\\s0/\\s+1/g'  > 

Thank you for the report. The gcc-6.1.gz manpage is generated automatically
from its texinfo source, by texi2pod.pl and then pod2man. If there's any
bug in
the manpage, the problem is more likely to be in pod2man, so it's better to
try to report to the perl package (which contains /usr/bin/pod2man).

Thanks,
Yixuan


>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers proposed-updates
>   APT policy: (500, 'proposed-updates'), (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.30-2u2 (SMP w/2 CPU cores)
> Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591
(charmap=ISO-8859-1), LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages gcc-6-doc depends on:
> ii  gcc-doc-base  6.3.0-1
>
> gcc-6-doc recommends no packages.
>
> Versions of packages gcc-6-doc suggests:
> pn  doc-base  
>
> -- no debconf information
>
> --
> Bjarni I. Gislason




--
GUO Yixuan

Bug#872960: synapse: Fails to start under wayland with segmentation fault.

[Jorge Cardona]

Package: synapse
Version: 0.2.99.2-2+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After updating my system I am running under wayland and the package does not
start.

$ synapse
[INFO 19:42:38.663390] [synapse-main:266] Starting up...
[INFO 19:42:38.839313] [synapse-main:208] Binding activation to
space
Segmentation fault

Thank you!



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

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

Versions of packages synapse depends on:
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-14
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgee-0.8-2 0.18.1-1
ii  libglib2.0-0 2.53.4-3
ii  libgtk-3-0   3.22.18-1
ii  libjson-glib-1.0-0   1.2.8-1
ii  libkeybinder-3.0-0   0.3.1-1
ii  libnotify4   0.7.7-2
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libzeitgeist-2.0-0   0.9.16-0.2+b1

Versions of packages synapse recommends:
ii  pastebinit  1.5-1
ii  zeitgeist   0.9.16-0.2
ii  zeitgeist-core  0.9.16-0.2+b1

synapse suggests no packages.

-- no debconf information

Bug#872893: debian-policy: Chapters, sections, appendices and numbering

[Sean Whitton]

On Tue, Aug 22 2017, Guillem Jover wrote:

> Take section «10.9.1. The use of dpkg-statoverride», this is correct
> on the HTML output and info file, on the PDF it's a section w/o a
> number inside §2.10.9. I've not checked the EPUB file.

Thanks!

> And I've just noticed on the info files it's just worse as they do not
> get their section numbers reset so they keep incrementing from the
> last chapter index. For example «Binary packages (…)» used to be
> appendix B, now it's 2, but on the info file it's 14.

Okay, that sounds like a bug -- thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#872934: fretsonfire: Fails to start (ImportError: No module named Image)

[Markus Koschany]

Control: tags -1 confirmed pending
Control: severity -1 grave

On Tue, 22 Aug 2017 19:00:13 +0200 Hans Joachim Desserud
 wrote:
> Package: fretsonfire
> Version: 1.3.110.dfsg2-4
> Severity: normal
> 
> Dear Maintainer,
> 
> When attempting to start fretsonfire, I get the following error message:
> $ fretsonfire
> Traceback (most recent call last):
>File "./FretsOnFire.py", line 45, in 
>  from GameEngine import GameEngine
>File "/usr/share/games/fretsonfire/game/GameEngine.py", line 34, in 
> 
>  from Data import Data
>File "/usr/share/games/fretsonfire/game/Data.py", line 23, in 
>  from Font import Font
>File "/usr/share/games/fretsonfire/game/Font.py", line 27, in 
>  from Texture import Texture
>File "/usr/share/games/fretsonfire/game/Texture.py", line 27, in 
> 
>  import Image
> ImportError: No module named Image
> 
> 
> (Originally reported in Ubuntu as
> https://bugs.launchpad.net/ubuntu/+source/fretsonfire/+bug/1712247)

Hello,

thank you for the report. This issue is caused by two wrong import
statements. We had to switch from python-imaging to python-pil recently
but I overlooked that python-imaging was still installed on my system,
so I didn't notice the wrong import statement. This should be fixed in a
minute.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#872895: debian-policy: Split html for policy lost

[Sean Whitton]

control: retitle -1 Include multi-page HTML in package
^ see below for explanation

Hello,

On Tue, Aug 22 2017, Mattia Rizzolo wrote:

> On Tue, Aug 22, 2017 at 12:10:36PM -0700, Sean Whitton wrote:
>> - it would be nice to include the multi-page rendering in the package
>
> More than nice, please.  I don't really deal with huge single-page
> documents.  Besides you wrote:
>> The single page output is much more useful to casual readers wanting
>> to look something up
> I deem this completely subjective, please don't assume such assertion as
> facts.  Also, I don't consider myself a "causual reader" and when I want
> to read something up I know what's the name of the paragrah, pick it
> from the index and then head to the relevant, single page.

Right, indeed, you're not a casual reader, and we would expect you to
have the Debian package installed.  I think the web version should be
tailored for people coming from outside the project who don't know that
such a package exists.  For them, it's easier to have a single page.

This is subjective but that doesn't preclude me making a judgement about
what most people would prefer, based on my experience.

>> - since we're publishing only the single-page version on
>> www.debian.org, we need to rewrite the links
>
> Please do publish both.

On Tue, Aug 22 2017, Guillem Jover wrote:

> I guess there are two problems here, one is indeed completely losing
> the multi-page rendering from the package. The other is the default
> change in the web site. IMO the best solution, and what is customary,
> is to present both (or more) rendering and let the user select:
>
>   [HTML one-page] [HTML multi-page] [PDF] [EPUB]

So you'd like https://www.debian.org/doc/debian-policy/ to be a menu?

I think that those who want this should file a bug against
www.debian.org.  It's not really in our purview, since we don't maintain
the script that maintains the /doc/ directory.  Hence I'm retitling this
bug to the part that is the policy editors' responsibility.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#866502: #866502: RFP: riot-web -- Graphical chat client for use with the decentralized matrix communication servers.

[Hubert Chathi]

There are several obstacles to packaging riot-web (both the desktop
version and the webapp version) in Debian.  In addition to react and
electron not being in Debian, as shirish mentioned, the build process
needs a newer version of npm than what is available in Debian, and the
JavaScript version of olm requires emscripten, which is currently not
usable in Debian.  There are probably many other little JavaScript
packages that Riot depends on that are not yet in Debian.

We have a wiki page tracking the packaging status for several
Matrix-related software in Debian, including Riot:
https://wiki.debian.org/Matrix

Hubert

Bug#872556: libc0.1: clock() has wrong scaling factor on hurd

[Samuel Thibault]

Control: tags -1 + pending

Hello,

James Cowgill, on ven. 18 août 2017 14:32:05 +0100, wrote:
> The clock() function on hurd has the wrong scaling factor.

Ok, it seems the confusion is due to this (from times(2) manual):

“Note that clock(3) also returns a value of type clock_t, but this
value is measured in units of CLOCKS_PER_SEC, not the clock ticks used
by times().”

So AIUI, we should drop the clock.c part of the
unsubmitted-clock_t_centiseconds.diff patch. That will fix your
testcase, and I believe will not break guile-2.0.

> While I appreciate that hurd's clock may not be able to be as precise as
> on Linux,

Actually this notion is extremely vague. Linux used to be at 100Hz, then
1000Hz, then variable frequency or even no frequency. It happens that
gnumach stayed at 100Hz.

Now, Linux just always exposes CLK_TCK as 100 to userland, whatever its
actual frequency, thus applications assuming that. And CLOCKS_PER_SEC is
defined to 100 by POSIX, whatever the actual precision.

> The patch header contains a description about applications failing with
> high precision. IMHO those applications are broken. Their bugs should
> not be worked around in libc and that patch should be dropped.

In an ideal world, yes. In the real world we are tired of submitting
patches to all kinds of applications with all kinds of bug submission
procedures, etc. while merely behaving like Linux (i.e. lying) just
"works".

> This was originally found after debugging ffmpeg. I believe the FTBFS on
> hurd is caused by this bug.

Cool!

Thanks,
Samuel

Bug#872959: ITP: gcc-7-doc -- documentation for the GNU compilers (gcc, g++, etc.)

[郭溢譞]

Package: wnpp
Severity: wishlist
Owner: =?utf-8?b?R3VvIFlpeHVhbiAo6YOt5rqi6K2eKQ==?= 

* Package name: gcc-7-doc
  Version : 7.2.0-1
  Upstream Author : FSF
* URL : https://gcc-gnu.org/
* License : GFDL-1.3+, with invariant sections (thus non-free)
  Programming Lang: Texinfo
  Description : documentation for the GNU compilers

This package contains manual pages and documentation in info and
html format, for the GNU compilers.

This documentation is licensed under the terms of the GNU Free
Documentation License, and contains invariant sections, so it can't be
part of Debian main.

Please also include as much relevant information as possible.
For example, consider answering the following questions:
 - why is this package useful/relevant? is it a dependency for
   another package? do you use it? if there are other packages
   providing similar functionality, how does it compare?
 - how do you plan to maintain it? inside a packaging team
   (check list at https://wiki.debian.org/Teams)? are you
   looking for co-maintainers? do you need a sponsor?

I'm maintaining gcc-6-doc and have maintained several earlier versions.
[1] As a DM, I need sponsor on the first upload, and would prefer DM upload
permission for subsequent updates.

[1] http://anonscm.debian.org/gitweb/?p=users/yixuan-guest/gcc-doc.git;a=summary

Thanks,
Yixuan

Bug#872077: quick hack

[AfterSys]

quick hack to fix this

wget --content-disp 
"https://downloads.sourceforge.net/project/xtables-addons/Xtables-addons/xtables-addons-2.13.tar.xz?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fxtables-addons%2Ffiles%2FXtables-addons%2F=1503442551_mirror=kent; 
"https://downloads.sourceforge.net/project/xtables-addons/Xtables-addons/xtables-addons-2.12.tar.xz?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fxtables-addons%2Ffiles%2FXtables-addons%2F=1503442622_mirror=netix;


tar xvf xtables-addons-2.12.tar.xz
tar xvf xtables-addons-2.13.tar.xz

cp -av /usr/src/xtables-addons-2.12 /usr/src/xtables-addons-2.12_dist

rsync -av xtables-addons-2.13/ /usr/src/xtables-addons-2.12/

dkms autoinstall -k 4.12.0-1-amd64

Bug#872956: [debian-policy] warn about danger of pipe in shell snippet of makefile

[Jonathan Nieder]

Hi,

Bastien ROUCARIÈS wrote:

> set -e is not suffisant to detect error in pipe context
>
> cat nonexistant | sed s/some//g will hapilly return 0 and do not fail
>
> exec 3>&1; s=$(exec 4>&1 >&3; { cat nonexistant ; echo $? >&4; } | sed 
> s/some//g ) && exit $s
>
> this could be simplified by using make function
> PIPESAFE=exec 3>&1; s=$$(exec 4>&1 >&3; { $(1) ; echo $$? >&4; } | $(2)) && 
> exit $$s
>
> Could deserve a footnote on 4.6. Error trapping in makefiles

I don't think this belongs in policy.  Maybe devref?

By the way, if you're using bash
(https://www.gnu.org/software/make/manual/html_node/Choosing-the-Shell.html),
you can use "set -o pipefail" to handle this kind of case.

Thanks,
Jonathan

Bug#872955: fstl: crashes with std::bad_alloc

[Eric Cooper]

And here's a backtrace from gdb:

(gdb) run
Starting program: /usr/bin/fstl
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fcc27d49700 (LWP 4164)]
[New Thread 0x7fcc25067700 (LWP 4165)]
[New Thread 0x7fcc1d3df700 (LWP 4166)]
[Thread 0x7fcc1d3df700 (LWP 4166) exited]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Thread 1 "fstl" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fcc31dfe42a in __GI_abort () at abort.c:89
#2  0x7fcc32713bb5 in __gnu_cxx::__verbose_terminate_handler() ()
   from /lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x7fcc32711986 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7fcc327119d1 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x7fcc32711c14 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x7fcc32d03832 in qBadAlloc() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fcc32d80fba in QListData::detach(int) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fcc32d2d1ce in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fcc32ef1b8f in QCoreApplication::arguments() ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fcc33da64df in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x7fcc33da7014 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#12 0x7fcc2ad37d90 in _SmcProcessMessage () from
/lib/x86_64-linux-gnu/libSM.so.6
#13 0x7fcc2ab272a8 in IceProcessMessages () from
/lib/x86_64-linux-gnu/libICE.so.6
#14 0x7fcc32f19e51 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fcc32f935ce in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fcc32f26222 in QSocketNotifier::event(QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fcc337cbbec in QApplicationPrivate::notify_helper(QObject*,
QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fcc337d3381 in QApplication::notify(QObject*, QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fcc32eee850 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fcc32f4286d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fcc30360bf7 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcc30360e60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcc30360f0c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fcc32f423bf in
QEventDispatcherGlib::processEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7fcc32eec83a in
QEventLoop::exec(QFlags) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fcc32ef4edc in QCoreApplication::exec() ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0xa00b in ?? ()
#28 0x7fcc31dea2e1 in __libc_start_main (main=0x9fe0, argc=1,
argv=0x7fffe0f8, init=, fini=,
rtld_fini=, stack_end=0x7fffe0e8) at
../csu/libc-start.c:291
#29 0xa0f9 in ?? ()

On Tue, Aug 22, 2017 at 6:54 PM, Eric Cooper  wrote:
> Here's a core file created when running just "fstl" with no arguments
> (which first printed the following):
>
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
> Aborted (core dumped)
>
> On Tue, Aug 22, 2017 at 6:09 PM, Jakob Haufe  wrote:
>> Control: tags -1 + moreinfo
>>
>> Unfortunately, it doesn't crash here. Can you provide me with a coredump or
>> backtrace? Automatic debug packages for fstl 0.9.2-1 exist as well.

Bug#872958: bridge-utils: Should support hairpin configuration

[Matthew Gabeler-Lee]

Package: bridge-utils
Version: 1.5-13
Severity: normal

bridge-utils can do almost any brctl command with some nice directives in
/etc/network/interfaces ...  except configure hairpin mode on ports.

>From the looks of /lib/bridge-utils/ifupdown.sh, this seems like it
shouldn't be too hard to implement, something like this has the feel of
being close?

if [ "$IF_BRIDGE_HAIRPIN_PORTS" ]; then
  bridge_parse_ports $IF_BRIDGE_HAIRPIN_PORTS | while read i ; do
for port in $i ; do
  brctl hairpin $IFACE $port on
done
  done
fi

I also notice that the hairpin command to brctl is missing from the man pages.

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'stable-debug'), 
(500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages bridge-utils depends on:
ii  libc6  2.24-11+deb9u1

bridge-utils recommends no packages.

Versions of packages bridge-utils suggests:
ii  ifupdown  0.8.19

-- no debconf information

Bug#872867: another option: GENC

[Ben Hildred]

On Tue, Aug 22, 2017 at 2:09 PM, Daniel Pocock  wrote:

>
> Mozilla decided[1] to use GENC[2], a list produced by the US Government
> and including additional countries that are not correctly covered by
> ISO3166.
>
> The US Govertment's approach (making their own list based on ISO3166) is
> similar in some ways to the approach I have suggested for Debian.
>
>
> 1. https://bugzilla.mozilla.org/show_bug.cgi?id=733417#c20
> 2. https://nsgreg.nga.mil/doc/view?i=2500
>
>
Note that GENC 3.0 has been superseded with GENC 3.0.1

 https://nsgreg.nga.mil/doc/view?i=2564



-- 
--
Ben Hildred
Automation Support Services

Bug#871148: Pending fixes for bugs in the maven-clean-plugin package

[pkg-java-maintainers]

tag 871148 + pending
thanks

Some bugs in the maven-clean-plugin package are closed in revision
955fece783ea883009fcab7fd7652ce3e0fe2d0d in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/maven-clean-plugin.git/commit/?id=955fece

Commit message:

Added the missing build dependency on junit4 (Closes: #871148)

Bug#855463: e2image: attempt to seek into a pipe

[Theodore Ts'o]

severity 855463 wishlist
merge 236408 855463
thanks

On Sat, Feb 18, 2017 at 06:13:53PM +0100, G.raud wrote:
> Package: e2fsprogs
> Version: 1.42.12-2+b1
> Severity: normal
> 
> e2image tries to seek into an ouput to stdout ("-"), even when it is a
> pipe:
> 
> --
> #  LC_ALL=C  e2image /dev/mapper/debian-var - | cat >test
> e2image 1.42.12 (29-Aug-2014)
> seek_set: Illegal seek
> --
> 
> According the manpage, only the raw and qcow2 formats require seeking
> into the output.

Actually, the manage states that only the raw mode supports using
stdout:

   If image-file is -, then the output of e2image will be sent to
   standard output, so that the output can be piped to another
   program, such as gzip(1).  (Note that this is currently only
   supported when creating a raw image file using the -r option, since
   the process of creating a normal image file, or QCOW2 image
   currently requires random access to the file, which cannot be done
   using a pipe.  This restriction will hopefully be lifted in a
   future version of e2image.)

The fact that e2image doesn't work on "normal" e2image files is a
long-standing short-coming.  But note that it's really an obsolete
format.  The raw or qcow image formats are actually far more useful,
and the primary use cases of e2image today.  The only reason why
"normal" is still used to describe the original e2image format is for
historical reasons.

Cheers,

- Ted

Bug#872957: Python Tkinter Label() funcion is expecting an integer, getting "Sans"

[Aaron Toponce]

Package: python-tk
Version: 2.7.13-1

When trying to create a Tk Label object, Python Tkinter crashes. Here is the
a traceback of the error:

>>> import Tkinter
>>> tk = Tkinter.Tk()
>>> label = Tkinter.Label(tk, text="Testing")
Traceback (most recent call last):
  File "", line 1, in 
label = Tkinter.Label(tk, text="Testing")
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 2599, in __init__
Widget.__init__(self, master, 'label', cnf, kw)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 2098, in __init__
(widgetName, self._w) + extra + self._options(cnf))
TclError: expected integer but got "Sans"

In addition, the _test() function should pop up a small window with two
buttons. However, it also fails with the same traceback:

>>> Tkinter._test()
Traceback (most recent call last):
  File "", line 1, in 
Tkinter._test()
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 3847, in _test
label = Label(root, text=text)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 2599, in __init__
Widget.__init__(self, master, 'label', cnf, kw)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 2098, in __init__
(widgetName, self._w) + extra + self._options(cnf))
TclError: expected integer but got "Sans"

These tests also fail with the `python3-tk' package, version 3.5.3-2:

$ python3
>>> import tkinter
>>> tkinter._test()
Traceback (most recent call last):
  File "", line 1, in 
tkinter._test()
  File "/usr/lib/python3.5/tkinter/__init__.py", line 3851, in _test
label = Label(root, text=text)
  File "/usr/lib/python3.5/tkinter/__init__.py", line 2617, in __init__
Widget.__init__(self, master, 'label', cnf, kw)
  File "/usr/lib/python3.5/tkinter/__init__.py", line 2150, in __init__
(widgetName, self._w) + extra + self._options(cnf))
_tkinter.TclError: expected integer but got "Sans"
>>> tk = tkinter.Tk()
>>> label = tkinter.Label(tk, text="Testing")
Traceback (most recent call last):
  File "", line 1, in 
label = tkinter.Label(tk, text="Testing")
  File "/usr/lib/python3.5/tkinter/__init__.py", line 2617, in __init__
Widget.__init__(self, master, 'label', cnf, kw)
  File "/usr/lib/python3.5/tkinter/__init__.py", line 2150, in __init__
(widgetName, self._w) + extra + self._options(cnf))
_tkinter.TclError: expected integer but got "Sans"

Both modules depend on:

blt (>= 2.4z-9)
libc6 (>= 2.4)
libtcl8.6 (>= 8.6.0)
libtk8.6 (>= 8.6.0)
libx11-6
tk8.6-blt2.5 (>= 2.5.3)

-- 
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o


signature.asc
Description: PGP signature

Bug#872776: stretch-pu: package unknown-horizons/2017.1+ds-2

[Markus Koschany]

Am 22.08.2017 um 22:21 schrieb Adam D. Barratt:
[...]
> That happened. Please go ahead.

Uploaded. Thanks!

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#872774: stretch-pu: package fife/0.4.0-3

[Markus Koschany]

Am 22.08.2017 um 22:22 schrieb Adam D. Barratt:
> Control: tags -1 + confirmed
> 
> On Mon, 2017-08-21 at 09:24 +0200, Markus Koschany wrote:
>> I would like to fix #871782 [1] in Stretch. There is a memory leak in
>> fife and unknown-horizons that can significantly slow down the game.
>>
>> This is part 1 of the fix. Please find attached a debdiff for
>> unknown-horizons' engine fife.
> 
> Please go ahead.
> 
> Regards,
> 
> Adam

Uploaded. Thank you.







signature.asc
Description: OpenPGP digital signature

Bug#872299: gnome-orca: Orca segfaults on startup

[Samuel Thibault]

Hello,

MENGUAL Jean-Philippe, on mer. 16 août 2017 01:21:18 +0200, wrote:
> Fatal Python error: Segmentation fault

Could you run 

ulimit -c unlimited

just before starting orca from the same shell, and put the generated
core file somewhere for download?

Samuel

Bug#781126: Pending fixes for bugs in the libsnmp-session-perl package

[pkg-perl-maintainers]

tag 781126 + pending
thanks

Some bugs in the libsnmp-session-perl package are closed in revision
f5161f49bea7cfd5e1171c7a4056e81fada4438e in branch 'master' by Roland
Rosenfeld

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

Commit message:

03_Socket6-inet_ntop: Add inet_ntop into import statement (Closes: #781126).

Bug#853462: Patch

[Hilko Bengen]

Control: tag -1 patch

Hi,

here's a simple patch to fix the build with GCC-7.

Cheers,
-Hilko

From: Hilko Bengen 
Date: Tue, 22 Aug 2017 23:58:52 +0200
Subject: Add comments to fix GCC-7 implicit-fallthrough errors

---
 json_object.c  |  3 ++-
 json_tokener.c |  1 +
 linkhash.c | 22 +++---
 3 files changed, 14 insertions(+), 12 deletions(-)

diff --git a/json_object.c b/json_object.c
index 6cc73bc..7ed3940 100644
--- a/json_object.c
+++ b/json_object.c
@@ -551,7 +551,8 @@ int64_t json_object_get_int64(struct json_object *jso)
   case json_type_boolean:
 return jso->o.c_boolean;
   case json_type_string:
-   if (json_parse_int64(jso->o.c_string.str, ) == 0) return cint;
+if (json_parse_int64(jso->o.c_string.str, ) == 0) return cint;
+/* fall-through */
   default:
 return 0;
   }
diff --git a/json_tokener.c b/json_tokener.c
index 9a76293..b23214a 100644
--- a/json_tokener.c
+++ b/json_tokener.c
@@ -305,6 +305,7 @@ struct json_object* json_tokener_parse_ex(struct 
json_tokener *tok,
 tok->err = json_tokener_error_parse_unexpected;
 goto out;
 }
+/* fall-through */
   case '"':
state = json_tokener_state_string;
printbuf_reset(tok->pb);
diff --git a/linkhash.c b/linkhash.c
index 712c387..c766452 100644
--- a/linkhash.c
+++ b/linkhash.c
@@ -376,17 +376,17 @@ static uint32_t hashlittle( const void *key, size_t 
length, uint32_t initval)
 /* last block: affect all 32 bits of (c) */
 switch(length)   /* all the case statements fall through */
 {
-case 12: c+=((uint32_t)k[11])<<24;
-case 11: c+=((uint32_t)k[10])<<16;
-case 10: c+=((uint32_t)k[9])<<8;
-case 9 : c+=k[8];
-case 8 : b+=((uint32_t)k[7])<<24;
-case 7 : b+=((uint32_t)k[6])<<16;
-case 6 : b+=((uint32_t)k[5])<<8;
-case 5 : b+=k[4];
-case 4 : a+=((uint32_t)k[3])<<24;
-case 3 : a+=((uint32_t)k[2])<<16;
-case 2 : a+=((uint32_t)k[1])<<8;
+case 12: c+=((uint32_t)k[11])<<24; /* fall-through */
+case 11: c+=((uint32_t)k[10])<<16; /* fall-through */
+case 10: c+=((uint32_t)k[9])<<8;   /* fall-through */
+case 9 : c+=k[8];  /* fall-through */
+case 8 : b+=((uint32_t)k[7])<<24;  /* fall-through */
+case 7 : b+=((uint32_t)k[6])<<16;  /* fall-through */
+case 6 : b+=((uint32_t)k[5])<<8;   /* fall-through */
+case 5 : b+=k[4];  /* fall-through */
+case 4 : a+=((uint32_t)k[3])<<24;  /* fall-through */
+case 3 : a+=((uint32_t)k[2])<<16;  /* fall-through */
+case 2 : a+=((uint32_t)k[1])<<8;   /* fall-through */
 case 1 : a+=k[0];
  break;
 case 0 : return c;

Bug#872956: [debian-policy] warn about danger of pipe in shell snippet of makefile

[Bastien ROUCARIÈS]

Package: debian-policy
Version: 4.0.1.0
Severity: normal

set -e is not suffisant to detect error in pipe context

cat nonexistant | sed s/some//g will hapilly return 0 and do not fail

exec 3>&1; s=$(exec 4>&1 >&3; { cat nonexistant ; echo $? >&4; } | sed 
s/some//g ) && exit $s

this could be simplified by using make function
PIPESAFE=exec 3>&1; s=$$(exec 4>&1 >&3; { $(1) ; echo $$? >&4; } | $(2)) && 
exit $$s

Could deserve a footnote on 4.6. Error trapping in makefiles





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

Bug#872955: fstl: crashes with std::bad_alloc

[Jakob Haufe]

Control: tags -1 + moreinfo

Unfortunately, it doesn't crash here. Can you provide me with a coredump or
backtrace? Automatic debug packages for fstl 0.9.2-1 exist as well.


pgpk1BbkNue3C.pgp
Description: OpenPGP digital signature

Bug#870996: mod-spamhaus: should mod-spamhaus be removed from unstable?

[Moritz Mühlenhoff]

reassign 870996 ftp.debian.org
retitle 870996 RM: mod-spamhaus -- orphaned, incompatible with Apache 2.4, last 
maintainer upload nine years ago
thanks

Bug#871641: udev: USB serial device wrongly tagged as pci in /dev/serial/by-id/

[Michael Biebl]

Am 10.08.2017 um 11:42 schrieb Nicolas Schodet:
> Package: udev
> Version: 232-25+deb9u1
> Severity: normal
> 
> Dear Maintainer,
> 
> When I plug a USB device using the ACM driver, it is listed in
> /dev/serial/by-id as pci-xx-if00 instead of usb-xx-if00.
> 
> This behaviour changed when tty and serial rules were merged together in
> upstream commit 1c5f4cb19.
> 
> As the device is connected using USB, I think the previous behaviour was
> better as a specific USB device has the same name on any computer.

Please provide a udev dump (udevadm info -e) when the device is attached.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#867733: closed by Dmitry Shachnev <mity...@debian.org> (Bug#867733: fixed in pyqt5 5.7+dfsg-6)

[Linus Lüssing]

Hi Dmitry,

Thanks for looking at this issue, both in experimental and
unstable.

The changelog mentions arm64, armhf and mipsel. However I
only see amd64, arm64 and i386 in experimental/unstable for
python3-pyqt5.qtwebengine on packages.debian.org [0][1].

Were armhf and mispel accidentally forgotten? Or did some build
bots choke on those?

Regards, Linus

[0]: https://packages.debian.org/sid/python3-pyqt5.qtwebengine
[1]: https://packages.debian.org/experimental/python3-pyqt5.qtwebengine


On Tue, Aug 22, 2017 at 12:09:03PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the python3-pyqt5.qtwebengine package:
> 
> #867733: mnemosyne: Package not installable on armhf, dependency issues
> 
> It has been closed by Dmitry Shachnev .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Dmitry Shachnev 
>  by
> replying to this email.
> 
> 
> -- 
> 867733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867733
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Tue, 22 Aug 2017 12:06:12 +
> From: Dmitry Shachnev 
> To: 867733-cl...@bugs.debian.org
> Subject: Bug#867733: fixed in pyqt5 5.7+dfsg-6
> 
> Source: pyqt5
> Source-Version: 5.7+dfsg-6
> 
> We believe that the bug you reported is fixed in the latest version of
> pyqt5, 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 867...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Dmitry Shachnev  (supplier of updated pyqt5 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)
> 
> 
> Format: 1.8
> Date: Tue, 22 Aug 2017 14:41:04 +0300
> Source: pyqt5
> Binary: pyqt5-dev pyqt5-dev-tools pyqt5-doc pyqt5-examples python3-pyqt5 
> python3-pyqt5-dbg python3-dbus.mainloop.pyqt5 python3-dbus.mainloop.pyqt5-dbg 
> python3-pyqt5.qtopengl python3-pyqt5.qtopengl-dbg python3-pyqt5.qtsql 
> python3-pyqt5.qtsql-dbg python3-pyqt5.qtwebchannel 
> python3-pyqt5.qtwebchannel-dbg python3-pyqt5.qtwebengine 
> python3-pyqt5.qtwebengine-dbg python3-pyqt5.qtwebkit 
> python3-pyqt5.qtwebkit-dbg python3-pyqt5.qtwebsockets 
> python3-pyqt5.qtwebsockets-dbg python3-pyqt5.qtxmlpatterns 
> python3-pyqt5.qtxmlpatterns-dbg python3-pyqt5.qtsvg python3-pyqt5.qtsvg-dbg 
> python3-pyqt5.qtmultimedia python3-pyqt5.qtmultimedia-dbg 
> python3-pyqt5.qtquick python3-pyqt5.qtquick-dbg python3-pyqt5.qtserialport 
> python3-pyqt5.qtserialport-dbg python3-pyqt5.qtsensors 
> python3-pyqt5.qtsensors-dbg python3-pyqt5.qtx11extras 
> python3-pyqt5.qtx11extras-dbg python3-pyqt5.qtpositioning 
> python3-pyqt5.qtpositioning-dbg python-pyqt5 python-pyqt5-dbg 
> python-dbus.mainloop.pyqt5
>  python-dbus.mainloop.pyqt5-dbg python-pyqt5.qtopengl 
> python-pyqt5.qtopengl-dbg python-pyqt5.qtsql python-pyqt5.qtsql-dbg 
> python-pyqt5.qtwebchannel python-pyqt5.qtwebchannel-dbg 
> python-pyqt5.qtwebengine python-pyqt5.qtwebengine-dbg python-pyqt5.qtwebkit 
> python-pyqt5.qtwebkit-dbg python-pyqt5.qtwebsockets 
> python-pyqt5.qtwebsockets-dbg python-pyqt5.qtxmlpatterns 
> python-pyqt5.qtxmlpatterns-dbg python-pyqt5.qtsvg python-pyqt5.qtsvg-dbg 
> python-pyqt5.qtmultimedia python-pyqt5.qtmultimedia-dbg python-pyqt5.qtquick 
> python-pyqt5.qtquick-dbg python-pyqt5.qtserialport 
> python-pyqt5.qtserialport-dbg python-pyqt5.qtsensors 
> python-pyqt5.qtsensors-dbg python-pyqt5.qtx11extras 
> python-pyqt5.qtx11extras-dbg python-pyqt5.qtpositioning
>  python-pyqt5.qtpositioning-dbg
> Architecture: source
> Version: 5.7+dfsg-6
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Python Modules Team 
> 
> Changed-By: Dmitry Shachnev 
> Description:
>  pyqt5-dev  - Development files for PyQt5
>  pyqt5-dev-tools - Development tools for PyQt5
>  pyqt5-doc  - Documentation for PyQt5
>  pyqt5-examples - Examples and demos for PyQt5
>  python-dbus.mainloop.pyqt5 - D-Bus Qt main loop support for Python 2
>  python-dbus.mainloop.pyqt5-dbg - D-Bus Qt main loop support for Python 2 
> (debug extension)
>  python-pyqt5 - Python 2 bindings for Qt5
>  python-pyqt5-dbg - Python 2 bindings for Qt5 (debug extensions)
>  python-pyqt5.qtmultimedia - Python 2 bindings for Qt5's Multimedia module
>  python-pyqt5.qtmultimedia-dbg - Python 2 bindings for Qt5's Multimedia 
> module (debug 

Bug#872955: fstl: crashes with std::bad_alloc

[Eric Cooper]

Package: fstl
Version: 0.9.2-1
Followup-For: Bug #872955

When I invoke "fstl" with no arguments, I *sometimes* get the same
error, sometimes it's a segmentation fault with no error message, and
sometimes it opens correctly with its default model.

In the last case, I can then use the File menu to open my example model and
it also opens correctly.

I also kept trying to run "fstl bottom.stl", and it succeeded after I tried
about 5 times.

Bug#872889: python-pil ImageDraw text() regression drawing blank lines of text

[Eric Soroos]

There's a fix for this upstream, merged but not released.

see https://github.com/python-pillow/Pillow/pull/2624

diff --git a/Tests/test_imagefont.py b/Tests/test_imagefont.py
index 12b687c3b..fde312f44 100644
--- a/Tests/test_imagefont.py
+++ b/Tests/test_imagefont.py
@@ -393,6 +393,11 @@ def test_default_font(self):
 # Assert
 self.assert_image_equal(im, target_img)

+def test_getsize_empty(self):
+font = self.get_font()
+# should not crash.
+self.assertEqual((0, 0), font.getsize(''))
+
 def _test_fake_loading_font(self, path_to_fake, fontname):
 # Make a copy of FreeTypeFont so we can patch the original
 free_type_font = copy.deepcopy(ImageFont.FreeTypeFont)
diff --git a/_imagingft.c b/_imagingft.c
index cd17758e4..3eb8bc0b7 100644
--- a/_imagingft.c
+++ b/_imagingft.c
@@ -109,7 +109,7 @@ getfont(PyObject* self_, PyObject* args, PyObject* kw)
 unsigned char* font_bytes;
 int font_bytes_size = 0;
 static char* kwlist[] = {
-"filename", "size", "index", "encoding", "font_bytes",
+"filename", "size", "index", "encoding", "font_bytes",
 "layout_engine", NULL
 };

@@ -449,8 +449,6 @@ font_getsize(FontObject* self, PyObject* args)
 y_max = y_min = 0;

 count = text_layout(string, self, dir, features, _info, 0);
-if (count == 0)
-return NULL;

 for (x = i = 0; i < count; i++) {
 int index, error;



On 08/22/2017 08:56 AM, Aaron Toponce wrote:

Package: python-pil
Version: 4.2.1-1

When using the text() function with the PIL ImageDraw module, if the text
contains a blankline (IE: "\n\n"), PIL crashes.

However, if horizontal whitespace exists in the blank line, the module will not
error out. But if the blank line is excactly "\n\n", without any horizontal
whitespace, an exception is caught, and the ImageDraw module crashes with the
ImageDraw Draw.text() function.

Below is an interactive session in ipython(1). Notice the "\n\n" on input 19,
versus "\n" on input 7 and "\n \n" on input 18:


 In [1]: from PIL import Image
 In [2]: from PIL import ImageDraw
 In [3]: from PIL import ImageFont
 In [4]: from textwrap import TextWrapper
 In [5]: fontfile = 
"/usr/share/fonts/truetype/dejavu/DejaVuSansMono-Bold.ttf"
 In [6]: font = ImageFont.truetype(fontfile, 24)
 In [7]: text = u'FOO\nBAR\nBAZ' # succeeds
 In [8]: tw = TextWrapper()
 In [9]: tw.width = 30
 In [10]: num_lines = text.count("\n")
 In [11]: height = 52 + (26 * num_lines) + 52
 In [12]: background = Image.new("RGB", (500, max(160, height)), (255, 255, 
255))
 In [13]: img = Image.open("/home/aaron/src/ciphermonkey/images/banana.png")
 In [14]: background.paste(img, (20, 10))
 In [15]: draw = ImageDraw.Draw(background)
 In [16]: draw.text((20, 52), text, (0, 0, 0), font=font)
 In [17]: text = u'FOO\nBAR\n \nBAZ' # succeeds
 In [18]: draw.text((20, 52), text, (0, 0, 0), font=font)
 In [19]: text = u'FOO\nBAR\n\nBAZ' # fails
 In [20]: draw.text((20, 52), text, (0, 0, 0), font=font)
 ---
 SystemError   Traceback (most recent call last)
  in ()
 > 1 draw.text((20, 52), text, (0, 0, 0), font=font)
 
 /usr/lib/python2.7/dist-packages/PIL/ImageDraw.pyc in text(self, xy, text, fill, font, anchor, *args, **kwargs)

 207 if self._multiline_check(text):
 208 return self.multiline_text(xy, text, fill, font, 
anchor,
 --> 209*args, **kwargs)
 210 ink, fill = self._getink(fill)
 211 if font is None:
 
 /usr/lib/python2.7/dist-packages/PIL/ImageDraw.pyc in multiline_text(self, xy, text, fill, font, anchor, spacing, align, direction, features)

 231 line_spacing = self.textsize('A', font=font)[1] + spacing
 232 for line in lines:
 --> 233 line_width, line_height = self.textsize(line, font)
 234 widths.append(line_width)
 235 max_width = max(max_width, line_width)
 
 /usr/lib/python2.7/dist-packages/PIL/ImageDraw.pyc in textsize(self, text, font, spacing, direction, features)

 258 if font is None:
 259 font = self.getfont()
 --> 260 return font.getsize(text, direction, features)
 261
 262 def multiline_textsize(self, text, font=None, spacing=4, 
direction=None,
 
 /usr/lib/python2.7/dist-packages/PIL/ImageFont.pyc in getsize(self, text, direction, features)

 154
 155 def getsize(self, text, direction=None, features=None):
 --> 156 size, offset = self.font.getsize(text, direction, features)
 157 return (size[0] + offset[0], size[1] + offset[1])
 158
 
 SystemError: error return 

Bug#853374: Fixed in 0.7.1

[Hilko Bengen]

Control: tag -1 fixed-upstream

Hi,

the package can be updated to upstream version 0.7.1 which no longer has
the FTBFS problem with GCC 7.

Cheers,
-Hilko

Bug#853428: Fixed in 1.7.6-1

[Hilko Bengen]

Control: fixed -1 1.7.6-1

Version 1.7.6-1 of package golang-1.7 builds just fine on unstable using
gcc-7. (Apparently, there is an FTBFS issue on arm64, but that seems to
be a different matter.)

Cheers,
-Hilko

Bug#871223: neverball: Strange squares instead of stars in the goals point

[Markus Koschany]

Control: tags -1 confirmed

On Sun, 06 Aug 2017 21:57:36 -0300 =?utf-8?b?RGFtacOhbiBCYXJiZXLDs24=?=
 wrote:
> Package: neverball
> Version: 1.6.0-8
> Severity: important
> 
> Dear Maintainer,
> 
>* Some graphical glitches occurs in the neverball game after dist-upgrade
> from stretch to buster/testing.
> 
>* The most obvious are squares instead of stars in the goals point.
> 
>* Screenshot attached with example.

Hello,

thank you for the report and sorry for the delay. It looks like an
OpenGL issue to me. Neverball's code didn't change between Stretch and
Buster but there is an ongoing update of Mesa. I have also found a
recent pull request [1] in upstream's Git repository that mentions the
stars to squares change. I will test with this new ENABLE_OPENGLES
option but due to the Mesa update libgles1-mesa-dev cannot be installed
right now, so we need to monitor this situation for a while.

Regards,

Markus

[1] https://github.com/Neverball/neverball/pull/134



signature.asc
Description: OpenPGP digital signature

Bug#872955: fstl: crashes with std::bad_alloc

[Eric Cooper]

Package: fstl
Version: 0.9.2-1
Severity: normal

Trying to run fstl on the attached STL file causes it to crash.

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

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

Versions of packages fstl depends on:
ii  libc6 2.24-14
ii  libgcc1   1:7.1.0-13
ii  libgl1-mesa-dri   13.0.6-1+b2
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-4
ii  libqt5gui55.7.1+dfsg-4
ii  libqt5opengl5 5.7.1+dfsg-4
ii  libqt5widgets55.7.1+dfsg-4
ii  libstdc++67.1.0-13

fstl recommends no packages.

fstl suggests no packages.

-- no debconf information


bottom.stl
Description: Binary data

Bug#855246: e2image: "Value too large for defined data type" while writing file bigger than 2GiB

[Theodore Ts'o]

tags 855246 +pending
thanks

Thanks for reporting this bug.  It will be fixed in the next release
of e2fsprogs.

- Ted

commit 6ca38e8c7dbc4b443602eae2781701b40c90edaf
Author: Theodore Ts'o 
Date:   Tue Aug 22 17:09:31 2017 -0400

libext2fs: fix Large File Support bug in ext2fs_image_inode_write()

We were using lseek() instead of ext2fs_llseek().  This caused e2image
to fail when writing an old-style e2image file if it was larger than
2 GiB.

Addresses-Debian-Bug: #855246

Signed-off-by: Theodore Ts'o 

diff --git a/lib/ext2fs/imager.c b/lib/ext2fs/imager.c
index b643cc6f3..357443f23 100644
--- a/lib/ext2fs/imager.c
+++ b/lib/ext2fs/imager.c
@@ -98,7 +98,8 @@ errcode_t ext2fs_image_inode_write(ext2_filsys fs, int fd, 
int flags)
blk++;
left--;
cp += fs->blocksize;
-   r = lseek(fd, fs->blocksize, SEEK_CUR);
+   r = ext2fs_llseek(fd, fs->blocksize,
+ SEEK_CUR);
if (r < 0) {
retval = errno;
goto errout;

Bug#872943: libpam-heimdal: Cannot configure credential cache file

[Russ Allbery]

Matthew Gabeler-Lee  writes:

> Package: libpam-heimdal
> Version: 4.7-4
> Severity: normal

> The libpam-krb5 package has a couple issues when trying to configure
> credential cache files:

> 1) The documentation claims you can set the credential cache filename in
> krb5.conf, but this appears to be a lie.  If you don't give the pam ccache=
> option, then it uses a hard coded string to form the cache filename,
> disregarding any settings in krb5.conf.

Could you show me your krb5.conf file where you tried to set this?

> 2) Because /usr/share/pam-configs/krb5 is not a conffile, there's no way
> to edit the pam settings without risking them getting clobbered on a
> package update, other than by disabling the module in the system level
> config and then adding it back in by hand, which is a bit of a pain in
> the tuchus.

Yeah, this is how the PAM update system works.  I can't change this as a
PAM package maintainer (and there are a bunch of reasons why it works this
way).  If you have to set PAM options, you have to disable automated
updates and manually configure PAM, and that probably won't change.

However, hopefully I can fix 1 and that will resolve your issue.

-- 
Russ Allbery (r...@debian.org)   

Bug#872954: moc: Key binding added in 04_playtime_perc.patch causes fatal errors

[kirifuda]

Package: moc
Version: 1:2.6.0~svn-r2788-1
Severity: normal
Tags: patch

MOC exits with a fatal error when any of the following conditions is met:
- Any command is bound to Ctrl-p in a custom keymap.
- The toggle_percent command is bound to any key.
This doesn't happen when other default key bindings are modified.

The cause of this seems to be a mistake in 04_playtime_perc.patch:
> From: Elimar Riesebieter 
> Subject: Assign "Switch on/off play time percentage"
>
> Index: moc-2.6~alpha1+r2758/keys.c
> ===
> --- moc-2.6~alpha1+r2758.orig/keys.c
> +++ moc-2.6~alpha1+r2758/keys.c
> @@ -204,7 +204,7 @@ static struct command commands[] = {
>   "toggle_percent",
>   "Switch on/off play time percentage",
>   CON_MENU,
> - { -1 },
> + {CTRL('p'), -1 },
>   0
>   },
>   {

The patch adds a new binding to the keys field, but doesn't update the
default_keys field. The default_keys field is supposed to contain the number of
default bindings.

The patch should look something like this instead:
> --- keys.c.orig
> +++ keys.c
> @@ -204,8 +204,8 @@
>   "toggle_percent",
>   "Switch on/off play time percentage",
>   CON_MENU,
> - { -1 },
> - 0
> + { CTRL('p'), -1 },
> + 1
>   },
>   {
>   KEY_CMD_PLIST_ADD_FILE,

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-92-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages moc depends on:
ii  libasound21.1.0-0ubuntu1
ii  libc6 2.23-0ubuntu9
ii  libcurl3-gnutls   7.47.0-1ubuntu2.2
ii  libdb5.3  5.3.28-11
ii  libfaad2  2.8.0~cvs20150510-1
ii  libflac8  1.3.1-4
ii  libgcc1   1:6.0.1-0ubuntu1
ii  libid3tag00.15.1b-11
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1ubuntu1
ii  libltdl7  2.4.6-0.1
ii  libmad0   0.15.1b-8ubuntu1
ii  libmagic1 1:5.25-2ubuntu1
ii  libmodplug1   1:0.8.8.5-2
ii  libmpcdec62:0.1~r459-4.1build1
ii  libncursesw5  6.0+20160213-1ubuntu1
ii  libogg0   1.3.2-1
ii  libopusfile0  0.7-1
ii  libpopt0  1.16-10
ii  librcc0   0.2.12-0.1
ii  libresid-builder0c2a  2.1.1-14ubuntu2
ii  libsamplerate00.1.8-8
ii  libsidplay2v5 2.1.1-14ubuntu2
ii  libsidutils0  2.1.1-14ubuntu2
ii  libsndfile1   1.0.25-10ubuntu0.16.04.1
ii  libspeex1 1.2~rc1.2-1ubuntu1
ii  libstdc++65.4.0-6ubuntu1~16.04.4
ii  libtagc0  1.9.1-2.4ubuntu1
ii  libtinfo5 6.0+20160213-1ubuntu1
ii  libvorbisfile31.3.5-3
ii  libwavpack1   4.75.2-2

moc recommends no packages.

Versions of packages moc suggests:
pn  moc-ffmpeg-plugin  

-- no debconf information

Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Samuel Thibault]

Hello,

Martin Zobel-Helas, on mar. 22 août 2017 23:10:47 +0200, wrote:
> (beside you seem to time-travel a bit in your debian/changelog entry)

Oops, sorry, will be fixed.

> but i would like to see a bit more testing in unstable. Both bugreport
> and the fix into unstable are from today.
> 
> Thus, tagging moreinfo for now.

Right :)

Samuel

Bug#872950: debian-policy: Too much indirection in info file menus

[Russ Allbery]

Guillem Jover  writes:

> The info file, on its initial page contains a Menu with the following
> entries:

> ,---
> * Menu:

> * Version::
> * Contents::
> * Legal Notice::
> `---

> For which Version contains a one-liner. It would be nicer if Contents
> would get expanded into the main Menu.

Just FYI, some of these bugs are likely to be assigned to Sphinx (with
affects on debian-policy), since I think this is just generic upstream
Sphinx behavior, but I'll take a look and see if there's a way to make
this better before reassigning.

(We didn't have info pages before, so I just turned this on because we
could, as sort of a bonus.)

-- 
Russ Allbery (r...@debian.org)   

Bug#872864: Checkout upstream signatures as well when using pristine-tar

[Chris Lamb]

block 872864 by 871809
thanks

> We should checkout the upstream signatures from the pristine-tar branch
> as well.

This blocks on support in pristine-tar (now pending release).


Regards,

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

Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Martin Zobel-Helas]

Control: tags -1 + moreinfo

Hi, 

On Tue Aug 22, 2017 at 22:43:25 +0200, Samuel Thibault wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Hello,
> 
> Blind users have reported that their screen reader, Orca, would
> sometimes crash when switching from window to window (Bug#872912),
> affecting both stable and testing.  Upstream released a fix, which was
> confirmed by Bug#872912 tester to completely fix the issue in sid.  I
> would thus like to upload the fix to stable, as attached diff shows.

The patch as is looks fine to me (beside you seem to time-travel a bit
in your debian/changelog entry) but i would like to see a bit more
testing in unstable. Both bugreport and the fix into unstable are from
today.

Thus, tagging moreinfo for now.

Cheers,
Martin
-- 
 Martin Zobel-Helas Debian System Administrator
 Debian & GNU/Linux Developer   Debian Listmaster
 http://about.me/zobel   Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 

Bug#872798: nslcd: can be killed by the OOM Killer, DoS

[Vincent Lefevre]

On 2017-08-22 20:51:10 +0200, Arthur de Jong wrote:
> On Tue, 2017-08-22 at 00:52 +0200, Vincent Lefevre wrote:
> > Perhaps not unique to nslcd, but the consequences are the worst when
> > nslcd is killed: one can no longer access to the machine.
> 
> That is true. It is probably also true for systemd, udev and similar
> processes but some of these also seem to tweak oom priority.

Note that contrary to nslcd, these processes run as root, so that
even if they do nothing special, they are less likely to be killed.

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

Bug#872926: sysstat: running sadc results in segmentation fault

[Jamie McClelland]

On 08/22/2017 03:09 PM, Robert Luberda wrote:
> Jamie McClelland writes:
> 
>> I started getting email messages from the sysstat cron job reporting the
>> segmentation fault.
> 
> When did you start receiving those e-mails? Just after upgrade systat to
> 11.5.7 or later i.e. did version 11.5.7 work, but then stopped for some
> reason?

I upgraded to 11.5.7 on July 25, 2017 - and the errors started August
20th. So - I don't think it is related to that upgrade.

However, the problem does seem to correlate with my use of the overlay2
filesystem with docker - perhaps that is the clue? The mtab file
contains a lot of lines related to overlay2 and docker.

>> Here's an strace:
>>
>> open("/etc/mtab", O_RDONLY) = 3
>> fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
>> read(3, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 1024
>> [...]
>> statfs("0", 0x7ffef1ab0890) = -1 ENOENT (No such file or 
>> directory)
>> read(3, "y2/l/7EEOV2FTKYKCYQJPMOALKJSL3M:"..., 1024) = 1024
>> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1} ---
> 
> Looks like the last file read was /etc/mtab (which should be a symlink
> to /proc/self/mtab). Even though the beginning of the file looks pretty
> usual, then something in this file causes sadc to crash.
> 
> Could you please send the contents of the /etc/mtab file, especially the
> lines around the "y2/l/7EEOV2FTKYKCYQJPMOALKJSL3M" string? In case it
> contain data you don't want to share into public, e.g. server names or
> paths on remote servers, please obfuscate it.

Attached.

Thanks for your help!

jamie


-- 
May First/People Link
Growing networks to build a just world
https://mayfirst.org
https://support.mayfirst.org

OpenPGP Key: http://current.workingdirectory.net/pages/identity/
xmpp: ja...@mayfirst.org
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8162252k,nr_inodes=2040563,mode=755 
0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1635072k,mode=755 0 0
/dev/mapper/vg_turkey0-root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup 
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup 
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/perf_event cgroup 
rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs 
rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12886 
0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/mapper/vg_turkey0-var /var ext4 rw,relatime,data=ordered 0 0
/dev/sda3 /boot ext4 rw,relatime,data=ordered 0 0
/dev/mapper/vg_turkey0-srv /srv ext4 rw,relatime,data=ordered 0 0
tmpfs /var/tmp tmpfs rw,relatime 0 0
/dev/mapper/vg_turkey0-docker /var/lib/docker ext4 rw,relatime,data=ordered 0 0
/dev/mapper/vg_turkey0-home /home ext4 rw,relatime,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
tmpfs /run/user/1000 tmpfs 
rw,nosuid,nodev,relatime,size=1635072k,mode=700,uid=1000,gid=1000 0 0
/dev/mapper/vg_turkey0-docker /var/lib/docker/overlay2 ext4 
rw,relatime,data=ordered 0 0
overlay 
/var/lib/docker/overlay2/65da4a2286836f893462520d010450995d988c421437124fad9f486dc2d9d82f/merged
 overlay 
rw,relatime,lowerdir=/var/lib/docker/overlay2/l/NMYHQQQA4WXMLIPCAPGXLUDSDM:/var/lib/docker/overlay2/l/H5R6F5HP3R3SCZZG4A4MYHDX3I:/var/lib/docker/overlay2/l/IIY7KSCIDGMMF4SNSGFA347DNX:/var/lib/docker/overlay2/l/AVNFGYK4HWNLWVOWUWJ4RZO5LW:/var/lib/docker/overlay2/l/MHQ6VBITNXP6HB52UVJIDJBRWF,upperdir=/var/lib/docker/overlay2/65da4a2286836f893462520d010450995d988c421437124fad9f486dc2d9d82f/diff,workdir=/var/lib/docker/overlay2/65da4a2286836f893462520d010450995d988c421437124fad9f486dc2d9d82f/work
 0 0
shm 

Bug#872912: gnome-orca: Segmentation fault when switching between windows.

[Samuel Thibault]

Hello,

Robert Schindler, on mar. 22 août 2017 22:27:27 +0200, wrote:
> It would be great to get that fix into stable, since I can now confirm
> that friends of mine are concerned by this bug as well.

I have submitted the request to debian-release, you can follow bug
#872953 if you want to be notified of the acceptance to stable.

Samuel

Bug#850965: freecad: GNOME Software catalog entry missing

[Graham Inggs]

On 8 July 2017 at 00:52,   wrote:
> The issue is still present although the icons and desktop file seems to be
> correct. Any ideas?

Probably this:
https://wiki.debian.org/AppStream/Guidelines#No_symbolic_links

Since the AppStream Generator relies on packages' md5sums file to
determine the contents of a package, symbolic links are not
recognized. So please do not symlink .desktop files or icons from
other places into /usr/share/pixmaps or the /usr/share/icons/hicolor
subdirectories, because the generator will not see these files then.
Relying on symbolic links in icon-theme packages is fine though.

Bug#872881: The proposed fix is not enough

[Martin Quinson]

reopen 872881
thanks

Hello,

the "-Wl,--as-needed -latomic" trick was not enough, the bug is not
gone. Sorry for not testing it before, I was too confident.

I must confess that I have no idea of how to fix this bug, and any
help would be welcome.

Thanks, Mt.

-- 
Data and source codes are to scientific experimental studies what
proofs are to mathematics. They thus need to be reviewed and shared.



signature.asc
Description: PGP signature

Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Samuel Thibault]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hello,

Blind users have reported that their screen reader, Orca, would
sometimes crash when switching from window to window (Bug#872912),
affecting both stable and testing.  Upstream released a fix, which was
confirmed by Bug#872912 tester to completely fix the issue in sid.  I
would thus like to upload the fix to stable, as attached diff shows.

Samuel

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

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

-- 
Samuel
 Yep. Moi j'ai un clavier à une touche. 
 Par contre, ma souris a 102 boutons, c'est pas toujours pratique.
 -+- OG in: Guide du Cabaliste Usenet - Le mulot contre attaque -+-
commit acbc35d8089e0ad597fd4f22b8c745d87ebe33e8
Author: Samuel Thibault 
Date:   Tue Aug 22 21:07:39 2017 +0200

Upstream fix for crash on switching between windows

patches/accessible_get_parent.diff (Closes: Bug#872912).

diff --git a/debian/changelog b/debian/changelog
index 5e0b720..0252734 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+at-spi2-core (2.22.0-6+deb9u1) stretch; urgency=medium
+
+  * patches/accessible_get_parent.diff: Upstream fix for crash on switching
+between windows (Closes: Bug#872912).
+
+ -- Samuel Thibault   Thu, 10 Aug 2017 21:20:02 +0200
+
 at-spi2-core (2.22.0-6) unstable; urgency=medium
 
   * patches/git-329ef2c4ebcb3aec6dcfcac15357fd583a60c969:
diff --git a/debian/patches/accessible_get_parent.diff 
b/debian/patches/accessible_get_parent.diff
new file mode 100644
index 000..5c1d035
--- /dev/null
+++ b/debian/patches/accessible_get_parent.diff
@@ -0,0 +1,30 @@
+commit 2347dad97cd903f6b7fed5a56b738e9ecdf80cac
+Author: Mike Gorse 
+Date:   Mon May 8 18:59:40 2017 -0500
+
+atspi_accessible_get_parent: move check for NULL AtspiApplication object
+
+Now, if we don't have a cached parent, then we always either return NULL
+or make a D-Bus call. This might make the code more robust, and hoping
+that it will fix https://bugzilla.gnome.org/show_bug.cgi?id=767074,
+though in theory it should make no difference there.
+
+diff --git a/atspi/atspi-accessible.c b/atspi/atspi-accessible.c
+index 4547ef7..b84317f 100644
+--- a/atspi/atspi-accessible.c
 b/atspi/atspi-accessible.c
+@@ -268,11 +268,12 @@ atspi_accessible_get_parent (AtspiAccessible *obj, 
GError **error)
+ {
+   g_return_val_if_fail (obj != NULL, NULL);
+ 
+-  if (obj->parent.app &&
+-  !_atspi_accessible_test_cache (obj, ATSPI_CACHE_PARENT))
++  if (!_atspi_accessible_test_cache (obj, ATSPI_CACHE_PARENT))
+   {
+ DBusMessage *message, *reply;
+ DBusMessageIter iter, iter_variant;
++if (!obj->parent.app)
++  return NULL;
+ message = dbus_message_new_method_call (obj->parent.app->bus_name,
+ obj->parent.path,
+ DBUS_INTERFACE_PROPERTIES, "Get");
diff --git a/debian/patches/series b/debian/patches/series
index 266c41a..eb8e71a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,4 @@ revert-register-late
 register-client-not-too-early
 git-329ef2c4ebcb3aec6dcfcac15357fd583a60c969
 git-eba079f3e72e61e6b55d81727ab50c85d505d296
+accessible_get_parent.diff

Bug#872952: libopencv-calib3d2.4v5: Conflict with GTk3 program

[Cyril Richard]

Package: libopencv-calib3d2.4v5
Version: 2.4.9.1+dfsg1-2
Severity: important

Dear Maintainer,

I'm currently trying to use libopencv-calib3d in a opensource software.
However, everytime I add -lopencv_calib3d in the configure.ac I have this error
while starting the app:

Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same
process is not supported

Of course I do not use GTK2 in my own application and this problem only occurs
wirh the debian package.



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

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

Versions of packages libopencv-calib3d2.4v5 depends on:
ii  libatomic1 7.1.0-13
ii  libc6  2.24-14
ii  libgcc11:7.1.0-13
ii  libopencv-core2.4v52.4.9.1+dfsg1-2
ii  libopencv-features2d2.4v5  2.4.9.1+dfsg1-2
ii  libopencv-flann2.4v5   2.4.9.1+dfsg1-2
ii  libopencv-highgui2.4-deb0  2.4.9.1+dfsg1-2
ii  libopencv-imgproc2.4v5 2.4.9.1+dfsg1-2
ii  libstdc++6 7.1.0-13
ii  libtbb22017~U7-6

libopencv-calib3d2.4v5 recommends no packages.

libopencv-calib3d2.4v5 suggests no packages.

-- no debconf information

Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

[Aaron M. Ucko]

notfixed 872881 3.16+dfsg-2
found 872881 3.16+dfsg-2
thanks

"Aaron M. Ucko"  writes:

>   -Wl,--as-needed -latomic --Wl,--no-as-needed

Thanks for the quick upload.  However, I forgot to note that this
construct needs to appear *after* the object files (or whatever else
needs -latomic) to be effective.  Could you please take another look?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#870513: stretch-pu: package cloud-init/0.7.9-2

[Martin Zobel-Helas]

Hi Thomas, 

On Sun Aug 06, 2017 at 18:12:56 +0100, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
> 
> On Wed, Aug 02, 2017 at 08:45:57PM +0200, Thomas Goirand wrote:
> > diff -Nru cloud-init-0.7.9/debian/cloud-init.NEWS 
> > cloud-init-0.7.9/debian/cloud-init.NEWS
> > --- cloud-init-0.7.9/debian/cloud-init.NEWS 1970-01-01 01:00:00.0 
> > +0100
> > +++ cloud-init-0.7.9/debian/cloud-init.NEWS 2017-08-02 20:28:11.0 
> > +0200
> > @@ -0,0 +1,8 @@
> > +cloud-init default behavior from upstream is to manage sources.list for 
> > Debian,
> > +adding contrib and non-free by default. This is clearly a bug which we have
> > +fixed. If you need contrib and non-free on your computer running 
> > cloud-init,
> > +then please use /etc/apt/sources.list.d facility, instead of the general 
> > file
> > +in /etc/apt/sources.list, as we changed the behavior. Our appologies for 
> > this
> > +change.
> > +
> > + -- Thomas Goirand   Wed, 02 Aug 2017 20:28:11 +0200
> 
> Is NEWS the appropriate place for this, or would README or the changelog be
> better? As it will only be shown when upgrading existing systems, this will
> simply be noise (those systems will already have a sources.list).

did you see this comment from Jonathan?

Cheers,
Martin

-- 
 Martin Zobel-Helas Debian System Administrator
 Debian & GNU/Linux Developer   Debian Listmaster
 http://about.me/zobel   Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 

Bug#866045: let this be for 1.5-13+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-07-03 at 00:02 +0200, Santiago Garcia Mantinan wrote:
> +bridge-utils (1.5-13+deb9u1) stretch; urgency=low
> +
> +  * Fix a problem with some vlan interfaces not being created.
> +Closes: #866687.
[...]
> Will this be ok for an upload?

Yes, thanks.

> If so... when should I upload it?

Now. :-)

> Will a normal dput work given the stretch target on the changelog, or should
> I do something special?

Any method of uploading to ftp-master as usual is fine. dak will dtrt
based on the distribution (from the .changes, but that should generally
match the changelog anyway).

Regards,

Adam

Bug#872951: partimage-server: partimaged-passwd fails to use the correct db utilities

[Jacques Theys]

Package: partimage-server
Version: 0.6.9-4
Severity: important
Tags: patch



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages partimage-server depends on:
ii  adduser  3.115
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-11+deb9u1
ii  libgcc1  1:6.3.0-18
ii  libnewt0.52  0.52.19-1+b1
ii  libpam0g 1.1.8-3.6
ii  libslang22.3.1-5
ii  libssl1.0.2  1.0.2l-2
ii  libstdc++6   6.3.0-18
ii  lsb-base 9.20161125
ii  openssl  1.1.0f-3
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages partimage-server recommends:
ii  db-util  5.3.1

partimage-server suggests no packages.

-- Configuration Files:
/etc/default/partimaged changed:
TARGET=/srv/shared/backup/partimage/
OPTS=-D


-- no debconf information


Patch: in /usr/sbin/partimaged-passwd

19c19
<   for i in 5.1 4.8 4.7; do
---
>   for i in 5.3 5.1 4.8 4.7; do

Bug#870005: stretch-pu: package samba/2:4.5.12+dfsg-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2017-08-20 at 15:53 +0200, Mathieu Parent wrote:
> 2017-08-17 10:53 GMT+02:00 Adam D. Barratt :
> > On 2017-08-17 9:31, Mathieu Parent wrote:
> >>
> >> Hi stable release team,
> >>
> >> I had no response to this bug. I know this is a huge diff, but please
> >> review it.
> >
> >
> > For the record it's not /that/ old yet and the original mail never reached
> > debian-release, presumably due to the diff size.
> 
> OK. I didn't want to be rude, just that the release team respond
> promptly most of the time. Thanks for that.

Clearly we need to be less efficient. :-)

(In all seriousness, most of my time at Debconf was focused on
improving / fixing our tooling, and a combination of work, illness and
jetlag has reduced my free time since.)

> > (Was your mail intentionally copied both to the bug and the list?)
> 
> Yes. I wanted to be sure the mail was catched.

Well, mailing the bug copies it to the list anyway. (Or doesn't, if the
mail is too big for the list's configuration, but then neither copy
would get through.)

+samba (2:4.5.12+dfsg-1) stretch-security; urgency=medium

The distribution there wants to be "stretch", please. (I assume that was
automagically inherited from the previous upload.)

+- Fix outdated DNS Root servers (Closes: #865406)

The fact that needs to be done makes me sad. :-(

With the above change, please go ahead.

Regards,

Adam

Bug#872883: Cannot reproduce this FTBFS on sh4

[Martin Quinson]

tags 872883 moreinfo help
thanks

Hello,

I setup a sh4 sbuild using qemu, and the package builds correctly
here. 

I have no idea of what's going on. If someone could provide me with
with a backtrace obtained on the real machine, I'd be really grateful.

For that, it should be enough to build the file
tools/cmake/test_prog/prog_stacksetup.c and execute the resulting
binary. Unless I'm wrong, it's raising a "Unhandled trap: 0x180",
which I guess is a segfault (but I've no idea).

https://buildd.debian.org/status/fetch.php?pkg=simgrid=sh4=3.16%2Bdfsg-2=1503422042=0

Many thanks in advance,
Mt.

-- 
C combines the power of assembler with the portability of assembler.


signature.asc
Description: PGP signature

Bug#871433: poco: please switch to SSLv23_… or TLS_…_method

[Jochen Sprickerhof]

Hi Sebastian,

* Sebastian Andrzej Siewior  [2017-08-08 00:11]:
> Package: poco
> Version: 1.7.6+dfsg1-5
> Severity: important
> User: pkg-openssl-de...@lists.alioth.debian.org
> Usertags: TLS1.0_1.1_removal
> 
> Your packages uses a function which requests a TLS1.0 and/or TLS1.1 only
> connection. Since openssl 1.1.0f-4 (currently in unstable) this means
> won't work because it provides TLS1.2. See also [0].
> Please switch to
>   SSLv23_method() | SSLv23_server_method() | SSLv23_client_method()
> 

This problem seems to be fixed in the latest version in experimental
(now unstable as well) already:

https://sources.debian.net/src/poco/1.7.8%2Bdfsg1-2/NetSSL_OpenSSL/src/Context.cpp/#L371

Can you please confirm and close this bug report?

Thanks!

Jochen


signature.asc
Description: PGP signature

Bug#870479: Installation of roundcube fails with Maria DB

[Paul Gevers]

Hi,

Before I go to bed...

On 08/21/17 18:41, Sandro Knauß wrote:
> dbc_go roundcube $@

I haven't verified if there are more options, but the documentation
reads everywhere:
dbc_go pkgname "$@" # mind the quotes.

Paul

PS, if anybody that can reproduce this issue can run it with
dbc_debug=true set that would be great for debugging.



signature.asc
Description: OpenPGP digital signature

Bug#872948: debootstrap: Debootstrap does not explain what is calls a Debian base system

[Emmanuel Kasper]

Package: debootstrap
Version: 1.0.89
Severity: minor
Tags: patch

The debootstrap man page says:
The default, with no --variant=X argument, is to create a base Debian 
installation in TARGET.

but does not explain what comes in the base Debian installation.
The patch included tries to improve that.

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages debootstrap depends on:
ii  wget  1.18-5

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2017.5
ii  gnupg   2.1.18-6

debootstrap suggests no packages.

-- no debconf information
commit 5e18585594bf93a1bec5e9f4f2496e016084805c
Author: Emmanuel Kasper 
Date:   Tue Aug 22 22:12:21 2017 +0200

Document which packages are installed by a default variant

The default base system installed by debootstrap includes all packages with 
Pritority essential and
important, but this was not yet documented.

diff --git a/debootstrap.8 b/debootstrap.8
index e802003..a3afc90 100644
--- a/debootstrap.8
+++ b/debootstrap.8
@@ -74,13 +74,13 @@ With this option set, this behaviour is disabled.
 .IP "\fB\-\-variant=minbase|buildd|fakechroot\fP"
 Name of the bootstrap script variant to use.
 Currently, the variants supported are minbase, which only includes
-essential packages and apt; buildd, which installs the build-essential
+\fIessential\fR packages and apt; buildd, which installs the build-essential
 packages into
 .IR TARGET ;
 and fakechroot, which installs the packages without root privileges.
-The default, with no \fB\-\-variant=X\fP argument, is to create a base
-Debian installation in
-.IR TARGET .
+The default, with no \fB\-\-variant=X\fP argument, is to create a
+base Debian installation with all packages of priority \fIessential\fR and
+\fIimportant\fR, including apt.
 .IP
 .IP "\fB\-\-merged-usr\fP"
 Create /{bin,sbin,lib}/ symlinks pointing to their counterparts in /usr/.

Bug#872949: nautilus: "Not a Directory or Filesystem" failures when selecting destination for Copy of Directory using CIFS/SMB to both Debian 9 and Windows 10 systems

[Harrison]

Package: nautilus
Version: 3.22.3-1
Severity: important

I am assuming the problem is in Nautilus and not CIFS.  When I attempted to
Copy a Directory on Debian 9.0.0+ TO both a Debian 9.0.0+ and Windows 10
systems, the selecting of the destination Directory failed with a "Not a
Directory" or "Unknown Filesystem" messages.  I was able to Copy the Directory
FROM my Windows 10 system [and probably could have also copied it FROM the
Debian 9.0.0 system] but it was an inconvience.



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.23-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  gvfs   1.30.4-1
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-11+deb9u1
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libexempi3 2.4.1-1
ii  libexif12  0.6.21-2+b2
ii  libgail-3-03.22.11-1
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libglib2.0-0   2.50.3-2
ii  libglib2.0-data2.50.3-2
ii  libgnome-autoar-0-00.1.1-4+b1
ii  libgnome-desktop-3-12  3.22.2-1
ii  libgtk-3-0 3.22.11-1
ii  libnautilus-extension1a3.22.3-1
ii  libpango-1.0-0 1.40.5-1
ii  libselinux12.6-3+b1
ii  libtracker-sparql-1.0-01.10.5-1
ii  libx11-6   2:1.6.4-3
ii  nautilus-data  3.22.3-1
ii  shared-mime-info   1.8-1

Versions of packages nautilus recommends:
ii  gnome-sushi  3.21.91-2
ii  gvfs-backends1.30.4-1
ii  librsvg2-common  2.40.16-1+b1

Versions of packages nautilus suggests:
ii  brasero  3.12.1-4
ii  eog  3.20.5-1+b1
ii  evince [pdf-viewer]  3.22.1-3+deb9u1
ii  nautilus-sendto  3.8.4-2+b1
ii  totem3.22.1-1
ii  tracker  1.10.5-1
ii  xdg-user-dirs0.15-2+b1

-- no debconf information

Bug#872950: debian-policy: Too much indirection in info file menus

[Guillem Jover]

Package: debian-policy
Version: 4.1.0.0

Hi!

The info file, on its initial page contains a Menu with the following
entries:

,---
* Menu:

* Version::
* Contents::
* Legal Notice::
`---

For which Version contains a one-liner. It would be nicer if Contents
would get expanded into the main Menu.

Thanks,
Guillem

Bug#872912: gnome-orca: Segmentation fault when switching between windows.

[Robert Schindler]

Hi,

Samuel Thibault wrote:
> Ok. I have just uploaded version 2.24.1-2 to sid, you'll be able to
> catch the packages from
> http://incoming.debian.org/debian-buildd/pool/main/a/at-spi2-core/
> when they get installed.
> 
> Could you then confirm that it fixes your bug?  We'll probably be able
> to upload the fix to stable too, then.

Thank you very much. I installed it and have no issues so far.

It would be great to get that fix into stable, since I can now confirm
that friends of mine are concerned by this bug as well. It seems to let
orca crash quite often in various every-day situations. I'm really glad to
see it gone.

Best regards
Robert


signature.asc
Description: PGP signature

Bug#869573: jessie-pu: package kdepim/4:4.14.1-1+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-07-24 at 16:49 +0200, Sandro Knauß wrote:
> Control: tags -1 - moreinfo
> 
> > We'll need to see a debdiff of the proposed package, built and tested on
> > jessie, before going any further, please.
> 
> As it was already proposed as security update, I already built and tested it 
> on jessie.

+kdepim (4:4.14.1-1+deb8u1) jessie-security; urgency=high

The distribution needs to be simply "jessie", as this isn't targetting
the security archive now.

With that change, please go ahead.

Regards,

Adam

Bug#872818: stretch-pu: package cvxopt/1.1.4-1.5+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-08-21 at 17:07 +0200, Sébastien Villemot wrote:
> I would like to do a p-u for cvxopt, fixing bug #859579.
> 
> By the time of the stretch release, cvxopt was not compatible with the new API
> of the GLPK library, so a compatibility layer had been introduced through
> glpk-4.49.diff. But that patch had too much in it, it contained an unneeded
> compatibility function (lpx_main) that was using a missing symbol (glp_main)
> (and this missing symbol had not been detected at compile time, because it is
> in a dynamically-loaded shared object).

Please go ahead.

Regards,

Adam

Bug#872774: stretch-pu: package fife/0.4.0-3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-08-21 at 09:24 +0200, Markus Koschany wrote:
> I would like to fix #871782 [1] in Stretch. There is a memory leak in
> fife and unknown-horizons that can significantly slow down the game.
> 
> This is part 1 of the fix. Please find attached a debdiff for
> unknown-horizons' engine fife.

Please go ahead.

Regards,

Adam

Bug#845297: Git hooks for translation versions

[Lev Lamberov]

Hi,

I was playing with git hooks and realized that they could be used in
migration of the Debian website content from CVS to git and saving
CVS-style translation versions (even throw away "1." part from 1.x and
keep just x). I guess this will make the migration for translators
easier and will not require to completely rewrite translation check
scripts (although some changes will be needed).

Let's store CVS-style version of every translatable file somewhere (in
file, database, or another VCS, "db" hereafter). When someone pushes
changes to the repository these changes are checked with git hook to
fetch a list of changed files. I propose to use update hook, because (1)
it get ref name to update, old and new object names as parameters, (2)
git will accept push only in case when update hook returns 0. The (2) is
important because we don't want to accept changes which are not
reflected in db.

I've wrote some skeletion script, please find it attached. All prints
there are just for debugging purposes, and output is forwarded to git
send-pack, so user will see it. Currently, it doesn't support merges, so
only one parent commit for a given commit.

Say the last commit on the server is eab5, and there are two file, aaa
(version 1.2) and bbb (version 1.7). Someone makes three commits, f3ea
(aaa changed), f2e6 (bbb changed), and d4e3 (both aaa and bbb changed),
and pushes them to the server. The script fetches a list of new commits
(f3ea, f2e6, d4e3) starting from the already known commit (eab5, not
included) to the last new commit (d4e3, included), and iterates through
the list. Since we have three commits there will be three iterations,
each will produce a list of changed files. That is, we will get three
lists: (aaa), (bbb), (aaa, bbb). What follows will depend on design
details. I can see two possible ways:

1. Update db as follows: aaa=1.4, bbb=1.8 (one version bump per commit)
2. Update db as follows: aaa=1.3, bbb=1.8 (one cumulitive version bump
   per file for all commits)

I'm not sure which way is better. We could also store not just the
current version, but rather version history with commit ids
corresponding to each version. I don't think I ever saw reverts in
website content CVS, but guess it also should be taken into account (and
it will require some additional work).

I agree that it may require a lot of work, but still it is an additional
alternative to consider. I'd say that gettext and po4a are good
candidates, but there are some particular shortcomings already mentioned
in the wiki.

Cheers!
Lev Lamberov



update
Description: update

Bug#872928: stretch-pu: package dnsdist/1.1.0-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2017-08-22 at 15:11 +, Christian Hofstaedtler wrote:
> this update fixes low-severity CVEs CVE-2016-7069, CVE-2017-7557,
> purely based on version-targetted patches from upstream.

Please go ahead.

Regards,

Adam

Bug#864911: stretch-pu: package desktop-base/9.0.3+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

[fixed recipients to include the bug rather than debian-release@]

On Sun, 2017-08-20 at 20:18 +0200, Aurélien COUDERC wrote:
> desktop-base (9.0.2+deb9u1) stretch; urgency=medium
> 
>   * Ensure postinst doesn’t fails on upgrade even when an incomplete theme 
> pack
> is active. (Closes: #858643)
>   * Fix XML syntax errors in gnome wallpaper description files making Joy
> wallpapers unavailable by default. (Closes: #862228)
> 
>  -- Aurélien COUDERC   Sun, 20 Aug 2017 20:03:02 +0200
> 
> The first could probably be qualified RC as attempting a reinstall will fail 
> at
> postinst if debian-edu-artwork-spacefun is installed on the system.
> Both fixes have been in testing for weeks now.
> 
> The full diff is attached.

Please go ahead.

> This would be my first pu so explicit advice is welcome to get it right
> (distribution to target, queue…).

The distribution is fine as is. Build the package in a stretch chroot
and upload to ftp-master as usual.

Regards,

Adam

Bug#869574: stretch-pu: package kdepim/4:16.04.3-4

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-08-21 at 18:03 +0200, Sandro Knauß wrote:
> now I rebuilt the package with the attached debdif on a sbuild -d stretch-
> amd64 and tried kontact under a virtualbox.

Please go ahead.

Regards,

Adam

Bug#869577: stretch-pu: package kf5-messagelib/4:16.04.3-3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-08-21 at 18:04 +0200, Sandro Knauß wrote:
> now I rebuilt the package with the attached debdif on a sbuild -d stretch-
> amd64 and tried kontact under a virtualbox.

Please go ahead.

Regards,

Adam

Bug#872895: debian-policy: Split html for policy lost

[Guillem Jover]

Hi!

On Tue, 2017-08-22 at 11:09:37 -0700, Jonathan Nieder wrote:
> Sean Whitton wrote:
> > On Tue, Aug 22 2017, Guillem Jover wrote:
> >> This version has lost the distinction between a single policy html and
> >> the one with different files per chapter. This will break links.
> >
> > This was intentional.  The single page output is much more useful to
> > casual readers wanting to look something up.

When I want to search for something in an on-line document I also
select the single-page document if it's available. Otherwise when I
want to navigate the document or read specific parts, I find the
multi-page way more pleasant and clear, because each chapter is
contained so I know how much there is to finish it, and scrolling or
using say the Ini/End key take you to the expected boundaries, and
it tends to have a global and intrapage TOCs to go to specific parts.

> I don't completely understand.  The old rendering had both single page
> and multi-page versions.  If I understand what you're saying, it is a
> reason that the single-page version is useful, but why does that
> preclude also providing the multi-page rendering?

I guess there are two problems here, one is indeed completely losing
the multi-page rendering from the package. The other is the default
change in the web site. IMO the best solution, and what is customary,
is to present both (or more) rendering and let the user select:

  [HTML one-page] [HTML multi-page] [PDF] [EPUB]

Thanks,
Guillem

Bug#872776: stretch-pu: package unknown-horizons/2017.1+ds-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-08-21 at 13:38 +0100, Adam D. Barratt wrote:
> On 2017-08-21 13:19, Markus Koschany wrote:
> > Am 21.08.2017 um 11:04 schrieb Martin Zobel-Helas:
> >> Hi,
> >> 
> >> On Mon Aug 21, 2017 at 09:27:33 +0200, Markus Koschany wrote:
[...]
> >>> This is part 2 to address a memory leak in unknown-horizons. I have
> >>> just filed another bug report for the game engine called fife.
> >>> 
> >>> This issue is also known as #871037 [1]. Please find attached the
> >>> debdiff for unknown-horizons.
> >> 
> >> If i read the bug version information correctly, this fix wants to 
> >> enter
> >> unstable first? Beside that, the patch looks good to me.
> > 
> > Hi,
> > 
> > the fix is already in unstable and testing (latest upstream version
> > 2017.2). The intended update for Stretch only includes the relevant
> > patches to address the memory leak.
> 
> Then please add an appropriate fixed version to #871037 to make that 
> clear.

That happened. Please go ahead.

Regards,

Adam

Bug#872893: debian-policy: Chapters, sections, appendices and numbering

[Guillem Jover]

Control: tag -1 - moreinfo

Hi!

On Tue, 2017-08-22 at 10:44:32 -0700, Sean Whitton wrote:
> On Tue, Aug 22 2017, Guillem Jover wrote:
> > At least on the PDF output, the section numbers are wrong, as there
> > are now two chapters that include the old sections.
> 
> Could you explain "two chapters that include the old sections", please?
> Or just say which sections are wrong.
> 
> We tried hard to avoid this, so it's definitely a bug.

Take section «10.9.1. The use of dpkg-statoverride», this is correct
on the HTML output and info file, on the PDF it's a section w/o a
number inside §2.10.9. I've not checked the EPUB file.

> > The appendices are also not easily distinguishable from the other
> > sections as they also use numbers intead of say letters.
> 
> This is a limitation of Sphinx.  We aren't going to fix it unless a new
> feature arrives from upstream.

Well, that's unfortunate. :( And I've just noticed on the info files
it's just worse as they do not get their section numbers reset so
they keep incrementing from the last chapter index. For example
«Binary packages (…)» used to be appendix B, now it's 2, but on the
info file it's 14.

Thanks,
Guillem

Bug#872915: Bug#759725: postgresql-common: non-synchronous service postgresql stop

[Ludovic Gasc]

2017-08-22 16:23 GMT+02:00 Christoph Berg :

> I think you can simply use a drop-in config file:
>
> /etc/systemd/system/postgresql@.service.d/type.conf:
> [Service]
> Type=notify
>

With this configuration, the systemctl command never returns.
To be sure I didn't made a mistake during my test, I have edited directly
/lib/systemd/system/postgresql@.service
systemctl stop postgresql
systemctl daemon-reload
systemctl start postgresql

I have enabled full access to sd_notify with NotifyAccess=all in case of
the signal comes from a subprocess, but it doesn't fix the behaviour.