Bug#818470: missing dependencies on ruby modules

[Pirate Praveen]

On Thu, 17 Mar 2016 12:13:47 +0100 Matthias Klose  wrote:
> Package: src:ruby-mousetrap-rails
> Version: 1.4.6-4
> Severity: serious


It is not correct to use serious severity for autopkgtest failures. Only
test dependencies are missing.



signature.asc
Description: OpenPGP digital signature

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

[Ben Finney]

On Mon, Jun 6, 2016, at 15:15, Carlos Donizete Froes wrote:
> Hi Ben,

Thank you for replying interleaved, this is more natural to follow as a
discussion.
 
> Review Package:
> 
> > Please correct the “VCS-Git” and “VCS-Browser” fields. The value 
> > of those fields should be for the VCS tracking the Debian packaging
> > work. 
> 
> Deleted lines "Vcs-*" in "d/control".

Why delete them?

You should be tracking your Debian packaging work in a VCS, and that VCS
repository should be online for others (read-only).

-- 
 \
  `\
_o__) Ben Finney 

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

[Carlos Donizete Froes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Ben,

Review Package:

> Please correct the “VCS-Git” and “VCS-Browser” fields. The value 
> of those fields should be for the VCS tracking the Debian packaging
> work. 
> In other words, the VCS referenced by those fields should get me the
> files needed to build the Debian package from source. See the
> Developer's Reference, §6.2.5 “Version Control System location”
> URL:https://www.debian.org/doc/manuals/developers-reference/best-pkg
> ing-practices.html#bpp-vcs.

Deleted lines "Vcs-*" in "d/control".

> Please correct the package description. The synopsis should not be
> just an arbitrary phrase about the package it should be a noun
> phrase describing what the package *is*. See §6.2.1 – §6
> .2.3 URL:https://www.debian.org/doc/manuals/developers-
> reference/best-pkg
> ing-practices.html#bpp-desc-basics.

I changed the description short and long of the package, if do not get
good text, please, could give a hint in the text?

> At URL:https://mentors.debian.net/package/runescape is reported
> that the Uscan configuration file (the ‘debian/watch’ file) doesn't
> work. Have you investigated that? What is the result?

Apparently is correct:

=
packages@debian$ ls
CHANGELOG  debian  extra  LICENSE  makefile  README.md  runescape.c  sc
ript.sh
packages@debian$ uscan --report-status --no-verbose 
uscan: Newest version of runescape on remote site is 0.1, local version
is 0.1
packages@debian$ uscan
uscan info: uscan (version 2.16.4) See uscan(1) for help
uscan info: Scan watch files in .
uscan info: Check debian/watch and debian/changelog in .
uscan info: package="runescape" version="0.1-1" (as seen in
debian/changelog)
uscan info: package="runescape" version="0.1" (no epoch/revision)
uscan info: ./debian/changelog sets package="runescape" version="0.1"
uscan info: Process ./debian/watch (package=runescape version=0.1)
uscan info: Found upstream signing keyring: debian/upstream/signing-
key.asc
uscan info: opts:
pgpsigurlmangle=s/$/.asc/,filenamemangle=s/.+\/(\d\S*)\.tar\.gz/runesca
pe-$1\.tar\.gz/
uscan info: line: https://github.com/coringao/runescape/tags
.*/(\d\S*)\.tar\.gz
uscan info: Parsing pgpsigurlmangle=s/$/.asc/
uscan info: Parsing filenamemangle=s/.+\/(\d\S*)\.tar\.gz/runescape-
$1\.tar\.gz/
uscan info: line: https://github.com/coringao/runescape/tags
.*/(\d\S*)\.tar\.gz
uscan info: Last orig.tar.* tarball version (from debian/changelog):
0.1
uscan info: Last orig.tar.* tarball version (dversionmangled): 0.1
uscan info: Requesting URL:
   https://github.com/coringao/runescape/tags
uscan info: Matching pattern:
   (?:(?:https://github.com)?\/coringao\/runescape\/tags)?.*/(\d\S*)\.t
ar\.gz
uscan info: Found the following matching hrefs on the web page (newest
first):
   /coringao/runescape/archive/0.1.tar.gz (0.1) index=0.1-1 
uscan info: Matching target for downloadurlmangle: https://github.com/c
oringao/runescape/archive/0.1.tar.gz
uscan info: Upstream URL (downloadurlmangled):
   https://github.com/coringao/runescape/archive/0.1.tar.gz
uscan info: Newest upstream tarball version selected for download
(uversionmangled): 0.1
uscan info: Matching target for filenamemangle:
/coringao/runescape/archive/0.1.tar.gz
uscan info: Download filename (filenamemangled): runescape-0.1.tar.gz
uscan: Newest version of runescape on remote site is 0.1, local version
is 0.1
uscan info:=> Package is up to date for from
  https://github.com/coringao/runescape/archive/0.1.tar.gz
uscan info: Scan finished
=

These changes is available for mentors.

https://mentors.debian.net/package/runescape

Thank you for your help.

- -- 
Carlos Donizete Froes [a.k.a coringao]
- -
https://wiki.debian.org/coringao
GPG: 4096R/C325F557
EAD9 DDCB DC86 4561
7612  A34F A9CD 6C31 C325 F557
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXVQbnAAoJEG8gQ2p1i6qVXVgP/j7vevZz04C9jag5BrJZ5IAX
XCPPK40mqfXHIRraCJloa8yNu8BlZl261o8dq4vSFhvTUm6Iy/bu5tck8nxTnkSJ
2NPhGEVcN28WjLG0hjtwhaCtC1cE1jzKcASH4h1+pn2iXwIvbhjXmwt2nWqRWCHu
TcjUCaeSpW876v/oIIyZ/LDAfBt588M1zenWFhLwCYUBwp1+OW68TxrOtwAr1h+M
UyqvyfG340eqcmvyNh4lTz0yld+AZ2WFVxDF6XrgCzdf+wPV04GpDTtk7fhOwB6+
cqf3sAOc1R4RlvuJOrM1KhTDfCWMv7V4sQaNvL+nYzrJGaSoMa7S85panN9fApo6
yLj32BzbssVelzwy3UUBM3yKz+LKT0Xgae+j330JH3wFApKIM4XI3w19ICoTub2K
djAQHgJAyvLgil1gpP/0Rl00kii7lGKgOPiWv7dQG0L6qF+B/GcfdCuF80LviWFz
JIUwbq0upDN3st7pHJ/GfMmbhyt52YrAGm19J0t4D5JI/qSjpTTkeEAE7yOj32KR
CQp6T0rQjFwU8dMuGiCJ5O/5xDKL9kiSlZ5WSJn0sVT6pJ1B+Tnktp+ctyJjh+xK
K1q7YyKV1Fp2EzuZd+bHSvKVce8ZyqkWdwt+aE4lDN9y9GIjj2lxPGJX26nCx7XJ
l+Fsd6N9QpKZPficax+P
=AeX1
-END PGP SIGNATURE-

Bug#826534: reportbug xrdp gives: IndexError: list index out of range

[Arthur Marsh]

Package: reportbug
Version: 6.6.6
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

I attempted to report a bug against xrdp:

 reportbug xrdp
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could 
not open display
  warnings.warn(str(e), _gtk.Warning)
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Arthur Marsh ' as your from address.
Getting status for xrdp...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2247, in 
main()
  File "/usr/bin/reportbug", line 1115, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1419, in user_interface
status = utils.get_package_status(package)
  File "/usr/lib/python2.7/dist-packages/reportbug/utils.py", line 387, in 
get_package_status
conffiles = conffiles + [re.findall(r' (.+) ([0-9a-f]+).*$', line)[0]]
IndexError: list index out of range

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

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


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/amarsh04/.reportbugrc:
reportbug_version "3.5"
mode standard
ui text
realname "Arthur Marsh"
email "arthur.ma...@internode.on.net"

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

Kernel: Linux 4.7.0-rc1+ (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages reportbug depends on:
ii  apt   1.2.12
ii  python-reportbug  6.6.6
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf-utils  1.5.59
ii  debsums2.1.2
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.87-3
ii  exim4-daemon-light [mail-transport-agent]  4.87-3
ii  file   1:5.25-2
ii  gnupg  1.4.20-6
ii  python-gtk22.24.0-4
pn  python-gtkspellcheck   
pn  python-urwid   
pn  python-vte 
ii  xdg-utils  1.1.1-1

Versions of packages python-reportbug depends on:
ii  apt   1.2.12
ii  file  1:5.25-2
ii  python-debian 0.1.27
ii  python-debianbts  2.6.0
pn  python:any

python-reportbug suggests no packages.

-- no debconf information

Bug#807853: (no subject)

[Mauro Sacchetto]

news about solutions for this bug?
when will we see again k3b in Testing?
tnax

Bug#826533: figlet: Please split data out of the package so it can be used by toilet

[Ben Longbons]

Package: figlet
Version: 2.2.5-2
Severity: wishlist

Dear Maintainer,

Most packages have an arch-independent foo-data package even if it
*isn't* usable by other packages.


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

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

Versions of packages figlet depends on:
ii  libc6  2.22-9

figlet recommends no packages.

figlet suggests no packages.

-- no debconf information

Bug#826531: RFS: flycheck/27-1 -- modern on-the-fly syntax checking for Emacs

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update to flycheck.

* Package name: flycheck
  Version : 27-1
  Upstream Author : Sebastian Wiesner and Flycheck contributors
* URL : http://www.flycheck.org/
* License : GPL-3+
  Section : lisp

Changes since the last upload:

  * Package new upstream release.
  * Run test suite with dh_elpa_test.
- Bump debhelper compat level to 10.
- Override Lintian tag due to using experimental compat level:
  package-needs-versioned-debhelper-build-depends.
  * Build dependency changes:
- New build-dep for testsuite: cppcheck.
- New build dependency on elpa-buttercup for dh_elpa_test.
- Build dependency on dh-elpa tightened for dh_elpa_test.
- Tighten build dependencies on hlint and rustc to ensure test suite passes.
  * Quilt patch changes:
- Drop 0004-update-pylint-expected-values.patch.
  Merged upstream.
- Drop 0010-skip-haskell-stack-tests-when-homedir-nonexistent.patch.
  Merged upstream.
- Drop 0011-hack-Makefile-to-silence-cmd-not-found-errors.patch.
  No longer required.
- Add 0010-disable-MELPA-tests.patch.
- Add 0011-disable-code-style-spec-test.patch.
- Add 0013-patch-test-runner.patch.
- Add 0014-Fix-cppcheck-test.patch.
- Add 0015-pass-epg-gpg-home-directory-to-gpg-invocation.patch.
- Add 0016-update-expected-values-for-rustc-version-1.9.0.patch.
- Refresh remaining patches.
  * Documentation changes:
- Remove d/copyright entry for obsoleted file test/flycheck-checkdoc.el.
- Add d/copyright entry for new file test/test-code-style.el.
- Drop debian/info since upstream's info manual no longer exists.
- Don't install CREDITS.md since upstream's credits file no longer exists.
- Merge and install two upstream changelogs.
  * Override dh_auto_build to avoid Cask.
  * Remove comments from d/control due to #823708.
  * Create README.source with information from comments.
  * Run wrap-and-sort -abst.
  * Bump standards version to 3.9.8 (no changes required).

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/f/flycheck/flycheck_27-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/flycheck.git
cd flycheck
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#826532: ITP: lua-torch-torch7/0~20160604-g69d7a01 -- Torch Package for Torch Framework

[Mo Zhou]

Package:wnpp
Severity: wishlist
Owner: lumin 

* Package name: lua-torch-torch7
  Version : 0~20160604-g69d7a01
  Upstream Author : Torch Developers
* URL : https://github.com/torch/
​torch7

* License : BSD-3-Clause
  Programming Lang: lua
  Description :
​
Torch Package for Torch Framework

 Torch is the main package in Torch7 where data structures for
 multi-dimensional tensors and mathematical operations over these
 are defined. Additionally, it provides many utilities for accessing
 files, serializing objects of arbitrary types and other useful utilities.
 .
 The Torch Package contains Tensor Library, File I/O Interface Library,
 and some Useful Utilities.


This is the dependency table of Torch package:

/extra/luafilesystem  pass  <== exists in archive
/extra/penlight   pass  <== exists in archive
/extra/lua-cjson  pass  <== exists in archive

/extra/luaffifb   upstream?, dep lua >= 5.1
/pkg/sundown  upstream?, dep lua >= 5.1
/pkg/cwraporig, dep lua >= 5.1, can be used independent
​   ​
 <== ITP: lua-
​torch-​
cwrap
/pkg/pathsorig, dep lua >= 5.1
​ <== ITP: lua-torch-paths​

/pkg/torchorig, dep lua >= 5.1, dep paths >= 1.0, dep cwrap >=
1.0  <== ITP: lua-torch-torch7
/pkg/dok  orig, dep lua >= 5.1, dep sundown >= 1.0
/exe/treplorig, dep torch >= 7.0, dep penlight >= 1.1.0
/pkg/sys  orig, dep torch >= 7.0
/pkg/xlua orig, dep sys >= 1.0, dep torch >= 7.0
/extra/nn orig, dep torch >= 7.0, dep luaffi
/extra/graph  orig, dep torch >= 7.0
/extra/nngraphorig, dep torch >= 7.0, dep graph, dep nn
/pkg/imageorig, dep torch >= 7.0, dep sys >= 1.0, dep xlua
>= 1.0, dep dok
/pkg/optimorig, dep torch >= 7.0, dep sys >= 1.0

-- 
Best,
Lumin

Bug#826530: firewalld: command "systemctl reload firewalld" stops firewalld

[Alexandre de Verteuil]

Package: firewalld
Version: 0.3.12-1
Severity: normal
Tags: upstream

Dear Maintainer,

Executing "systemctl reload firewalld" sometimes silently stops firewalld. The
only way to notice that firewalld is stopped is "systemctl status firewalld" or
trying to execute a firewall-cmd command, which fails with an error message.

The status of firewalld on servers must be manually checked and the service
started where required.

See the related bug on the Red Hat bugtracker:
https://bugzilla.redhat.com/show_bug.cgi?id=1313023

If I understand correctly, this bug is fixed in firewalld-0.4.2.

Thanks and regards,

--Alexandre de Verteuil


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

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

Versions of packages firewalld depends on:
ii  dbus 1.8.20-0+deb8u1
ii  gir1.2-glib-2.0  1.42.0-2.2
ii  init-system-helpers  1.22
ii  iptables 1.4.21-2+b1
ii  policykit-1  0.105-8
ii  python   2.7.9-1
ii  python-dbus  1.2.0-2+b3
ii  python-gi3.14.0-1
ii  python-slip-dbus 0.6.0-2

Versions of packages firewalld recommends:
ii  ebtables  2.0.10.4-3

firewalld suggests no packages.

-- no debconf information

Bug#826529: ITP: lua-torch-paths/0~20160203-g68d579a -- Filename Manipulation Package for Torch Framework

[Mo Zhou]

Package:wnpp
Severity: wishlist
Owner: lumin 

* Package name: lua-torch-paths

  Version :
​
0~20160203-g68d579a
  Upstream Author : Torch Developers
* URL : https://github.com/torch/
​paths​

* License : BSD-3-Clause
  Programming Lang: lua
  Description :
​
Filename Manipulation Package for Torch Framework

​
 This package provides portable functions and variables to manipulate
 the file system :
 .
  * Manipulating filenames: functions for manipulating filenames ;
  * Directory functions: functions for listing and manipulating directories
;
  * Directory paths: paths to well known directories ;
  * Miscellaneous: uncategorized functions ;
 .
 When this package is loaded, it also computes a number of useful
 variables indicating where the various Torch components are installed.
 Do not change their values.


This is the dependency table of Torch package:

/extra/luafilesystem  pass  <== exists in archive
/extra/penlight   pass  <== exists in archive
/extra/lua-cjson  pass  <== exists in archive

/extra/luaffifb   upstream?, dep lua >= 5.1
/pkg/sundown  upstream?, dep lua >= 5.1
/pkg/cwraporig, dep lua >= 5.1, can be used independent
​   ​
 <== ITP: lua-
​torch-​
cwrap
/pkg/pathsorig, dep lua >= 5.1
​ <== ITP: lua-torch-paths​

/pkg/torchorig, dep lua >= 5.1, dep paths >= 1.0, dep cwrap >=
1.0
/pkg/dok  orig, dep lua >= 5.1, dep sundown >= 1.0
/exe/treplorig, dep torch >= 7.0, dep penlight >= 1.1.0
/pkg/sys  orig, dep torch >= 7.0
/pkg/xlua orig, dep sys >= 1.0, dep torch >= 7.0
/extra/nn orig, dep torch >= 7.0, dep luaffi
/extra/graph  orig, dep torch >= 7.0
/extra/nngraphorig, dep torch >= 7.0, dep graph, dep nn
/pkg/imageorig, dep torch >= 7.0, dep sys >= 1.0, dep xlua
>= 1.0, dep dok
/pkg/optimorig, dep torch >= 7.0, dep sys >= 1.0
-- 
Best,
Lumin

Bug#826528: ITP: lua-torch-cwrap/0~20160222-gdbd0a62 -- CWrap package for Torch Framework

[Mo Zhou]

Package:wnpp
Severity: wishlist
Owner: lumin 

* Package name: lua-torch-cwrap
  Version : 0~20160222-gdbd0a62
  Upstream Author : Torch Developers
* URL : https://github.com/torch/cwrap
* License : BSD-3-Clause
  Programming Lang: lua
  Description : CWrap package for Torch Framework

 The cwrap package helps you to automate the generation of Lua/C wrappers
 around existing C functions, such that these functions would be callable
 from Lua. This package is used by the torch package, but does not depend
 on anything, and could be used by anyone using Lua.

This is the dependency table of Torch package:

/extra/luafilesystem  pass  <== exists in archive
/extra/penlight   pass  <== exists in archive
/extra/lua-cjson  pass  <== exists in archive

/extra/luaffifb   upstream?, dep lua >= 5.1
/pkg/sundown  upstream?, dep lua >= 5.1
/pkg/cwraporig, dep lua >= 5.1, can be used independent
 <== ITP: lua-cwrap
/pkg/pathsorig, dep lua >= 5.1
/pkg/torchorig, dep lua >= 5.1, dep paths >= 1.0, dep cwrap >= 1.0
/pkg/dok  orig, dep lua >= 5.1, dep sundown >= 1.0
/exe/treplorig, dep torch >= 7.0, dep penlight >= 1.1.0
/pkg/sys  orig, dep torch >= 7.0
/pkg/xlua orig, dep sys >= 1.0, dep torch >= 7.0
/extra/nn orig, dep torch >= 7.0, dep luaffi
/extra/graph  orig, dep torch >= 7.0
/extra/nngraphorig, dep torch >= 7.0, dep graph, dep nn
/pkg/imageorig, dep torch >= 7.0, dep sys >= 1.0, dep xlua
>= 1.0, dep dok
/pkg/optimorig, dep torch >= 7.0, dep sys >= 1.0

-- 
Best,
Lumin

Bug#703237:

[Paul Wise]

On Mon, Jun 6, 2016 at 3:38 AM, SamuelOPH wrote:

> Looking at packages.debian.org i believe this was fixed some time ago,
> please correct me if i'm wrong.

No, this isn't fixed yet. For example compare unstable/experimental here:

https://packages.debian.org/search?keywords=glibc

sid (unstable) (lisp): clisp module that adds the glibc bindings
experimental (rc-buggy) (lisp): clisp module that adds the glibc bindings

It should look like this instead:

sid (unstable) (lisp): clisp module that adds the glibc bindings
rc-buggy (experimental) (lisp): clisp module that adds the glibc bindings

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

[Carlos Donizete Froes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Ben,

Deleted lines "VCS-*" in "d/control".

Thank you for your help.

- -- 
Carlos Donizete Froes [a.k.a coringao]
- -
https://wiki.debian.org/coringao
GPG: 4096R/C325F557
EAD9 DDCB DC86 4561
7612  A34F A9CD 6C31 C325 F557

Em Seg, 2016-06-06 às 12:43 +1000, Ben Finney escreveu:
> Carlos Donizete Froes  writes:
> 
> > I made the changes recommended me. Please could again analyze my
> > package?
> > 
> > https://mentors.debian.net/package/runescape
> 
> Please correct the “VCS-Git” and “VCS-Browser” fields. The value of
> those fields should be for the VCS tracking the Debian packaging
> work.
> 
> In other words, the VCS referenced by those fields should get me the
> files needed to build the Debian package from source. See the
> Developer's Reference, §6.2.5 “Version Control System location”
>  ing-practices.html#bpp-vcs>;.
> 
> 
> Please correct the package description. The synopsis should not be
> just
> an arbitrary phrase about the package; it should be a noun phrase
> describing what the package *is*. See §6.2.1 – §6.2.3
>  ing-practices.html#bpp-desc-basics>;.
> 
> 
> At ; is reported
> that
> the Uscan configuration file (the ‘debian/watch’ file) doesn't work.
> Have you investigated that? What is the result?
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXVO0KAAoJEG8gQ2p1i6qVHmgQAK0cWof3v18hOZwn8P5KJN8T
NKOPLurBcW8DoB0X7DVcWqWhOA8kZi/VPV988NH3aBnb/AmHR9HyVPgy+B1rq1RV
tohztRYIgEbh97nZx2pkobkcM5tMBmINtEuX9uAsB2hNhgGoTnKywVM1sWdMUL3x
93aXmjaLUNfpKFRktKtbml4LZw+rUhwaYkGt9XJjbbsSckX8+TVfqIv2TIHlL1u8
qEoUnqz0n+o7Raw7G7cbyoHpJyx0UwXi4I4sczLtO+HDhbZ/y85HYK/3VrZoUtu1
IrsGFgBjhq4UTy/En5SYTzprq3j3yAX8+43kpMF6mipT6QxEZv4dpEvEHO9K+Fxo
qgHcWkXK6Pk8indapHMX+W9zMFMfZykXqLzKIokSoHAlpaEISsfdCuaD+NggZWQp
VJKtEn7XZqzDO/eo3ltqah7eqX6nvT3pQUX8sKOWvQU1aZRQWCdWLxL2YwREEhlG
Oz6hJgbuV6fq0dKNc95amBM/lOSEA6L5wbvUz6MCrZwbOdSbiqPCw/CRB70GAF9z
nCs4AakT4ngZUrwzNGqLpsVXznhnpPbOVJxwp5lLcKcpghIFck7FwJb7+0suTjDR
MqD0+NOcTwt2hlF/OcZydK6t/usaYk30JCVXfrmWXQD6CM3R8JITrP/9fAh3Put5
aaUVnCBbaxmsqXE20rmW
=aWfd
-END PGP SIGNATURE-

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

[Ben Finney]

Carlos Donizete Froes  writes:

> I made the changes recommended me. Please could again analyze my
> package?
>
> https://mentors.debian.net/package/runescape

Please correct the “VCS-Git” and “VCS-Browser” fields. The value of
those fields should be for the VCS tracking the Debian packaging work.

In other words, the VCS referenced by those fields should get me the
files needed to build the Debian package from source. See the
Developer's Reference, §6.2.5 “Version Control System location”
.


Please correct the package description. The synopsis should not be just
an arbitrary phrase about the package; it should be a noun phrase
describing what the package *is*. See §6.2.1 – §6.2.3
.


At  is reported that
the Uscan configuration file (the ‘debian/watch’ file) doesn't work.
Have you investigated that? What is the result?

-- 
 \ “I got some new underwear the other day. Well, new to me.” —Emo |
  `\   Philips |
_o__)  |
Ben Finney 

Bug#806945: bash: Please make bash build reproducibly

[Ximin Luo]

(Chet, your specific attention is required for this email, please)

Ximin Luo:
> On Sat, 28 May 2016 13:38:35 +0200 Reiner Herrmann  wrote:
>> After that, the only remaining issue is that the included header file
>> /usr/include/bash/config.h varies depending on the kernel version used
>> during build [1] (with kernel <4, PGRP_PIPE is defined).
> 
> For this particular example, we can just patch this out, i.e. remove it from 
> the installed config.h. Debian already forces PGRP_PIPE 1 in config-bot.h, 
> which config.h includes at the end.
> 

I dug into this a bit more and it looks like the cause of the difference is 
this snippet from configure.ac:

linux*) LOCAL_LDFLAGS=-rdynamic  # allow dynamic loading
case "`uname -r`" in
2.[[456789]]*|3*)   AC_DEFINE(PGRP_PIPE) ;;
esac ;;


This was added between bash-3.0.16 and bash-3.1, way before Linux 4 came out. 
So I wonder if this snippet should instead be:

linux*) LOCAL_LDFLAGS=-rdynamic  # allow dynamic loading
case "`uname -r`" in
1.*|2.[[0123]]*) true ;;
*) AC_DEFINE(PGRP_PIPE) ;;
esac ;;

to set this for all future kernels? Then Debian (and probably other distros) 
could get rid of our patch, too.

However, the question still remains why config.h is installed into the end-user 
system, and if bash-built-with-linux-5 required PGRP_PIPE to be *undefined*, we 
would still have a reproducibility problem.

Ximin

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

[Carlos Donizete Froes]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello Gianfranco,

I made the changes recommended me. Please could again analyze my
package?

https://mentors.debian.net/package/runescape

Thank you!

- -- 
Carlos Donizete Froes [a.k.a coringao]
- -
https://wiki.debian.org/coringao
GPG: 4096R/C325F557
EAD9 DDCB DC86 4561
7612  A34F A9CD 6C31 C325 F557

Em Qua, 2016-06-01 às 15:02 +, Gianfranco Costamagna escreveu:
> control: owner -1 !
> control: tags -1 moreinfo
> 
> Hi, I tried to build and run, and (I admit, I'm behind a proxy)
> 
> it failed with an error like
> runescape 
> mv: cannot stat 'jagexappletviewer.jar': No such file or directory
> Gtk-Message: GtkDialog mapped without a transient parent. This is
> discouraged.
> 
> 
> and now:
> runescape 
> Gtk-Message: GtkDialog mapped without a transient parent. This is
> discouraged.
> English
> Error: Could not find or load main class jagexappletviewer
> 
> 
> I don't understand why desktop, install manpages are part of Debian
> and not upstream packaging
> a simple Makefile for upstream can simplify a lot the Debian
> packaging, and make easier life
> for other linux distros.
> 
> 
> head -n 1 debian/upstream/signing-key.asc
> -BEGIN PGP PRIVATE KEY BLOCK-
> 
> ^
> 
> LOOL
> I guess you need to change that
> gpg debian/upstream/signing-key.asc
> sec  4096R/C325F557 2016-03-09 Carlos Donizete Froes (a.k.a coringao)
> 
> 
> 
> please revoke it, and generate a new one (I can do this for you,
> because now everybody has your private key)
> 
> 
> BTW (check-all-the-things review, package from debian/experimental)
> 
> find -type f -iname '*.asc' -exec cat {} + | hot dearmor | hokey lint
> hokey (hopenpgp-tools) 0.17
> Copyright (C) 2012-2015  Clint Adams
> hokey comes with ABSOLUTELY NO WARRANTY. This is free software, and
> you are welcome to redistribute it under certain conditions.
> hot (hopenpgp-tools) 0.17
> Copyright (C) 2012-2015  Clint Adams
> hot comes with ABSOLUTELY NO WARRANTY. This is free software, and you
> are welcome to redistribute it under certain conditions.
> 
> Key has potential validity: good
> Key has fingerprint: EAD9 DDCB DC86 4561 7612  A34F A9CD 6C31 C325
> F557
> Checking to see if key is OpenPGPv4: V4
> Checking to see if key is RSA or DSA (>= 2048-bit): RSA 4096
> Checking user-ID- and user-attribute-related items:
> Carlos Donizete Froes (a.k.a coringao) :
> Self-sig hash algorithms: [SHA-1]
> Preferred hash algorithms: [ SHA-256
> , SHA-1
> , SHA-384
> , SHA-512
> , SHA-224 ]
> Key expiration times: []
> Key usage flags: [[ sign-data
> , certify-keys ]]
> 
> 
> 
> $ grep --recursive --perl-regexp --null-data --files-with-matches
> '(?s)-BEGIN PGP PRIVATE KEY BLOCK-.*-END PGP PRIVATE KEY
> BLOCK-' .
> 
> 
> 
> Please add some upstream metadata: https://wiki.debian.org/UpstreamMe
> tadata
> 
> 
> 
> 
> I guess this is all for today!
> 
> G.
> 
> 
> 
> 
> Il Venerdì 27 Maggio 2016 19:24, Carlos Donizete Froes  up.net> ha scritto:
> Em 23-05-2016 6:22, Mattia Rizzolo escreveu:
> 
> > Hi Carlos!
> > 
> > On Tue, Feb 16, 2016 at 07:30:51PM +, James Cowgill wrote:
> > > I have a few comments on this pavkage.
> > 
> > This was Feb 16, more than 3 months ago, but with no replies from
> > you.
> > Are you still interested in this package?
> 
> Hello Mattia,
> 
> I apologize to leave long without work in this package, it was more 
> because of the other packages that I have and I ended up leaving
> aside.
> 
> I made some changes in this package and is available on mentors to 
> analyze.
> 
> https://mentors.debian.net/package/runescape
> 
> Thank you!
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXVNeOAAoJEG8gQ2p1i6qVdB4P/j2MifIoP3t5iWCtP3zMFJGD
Xp/BNY65Fvyfu8JrTVmqB8J/6SiX99F8heilvaY0/hZsWBHlYsuI71xRV/no4Wtf
OabKvdIyjXFEB7pjSxXdcsFUEZ5uVO7SPvlCfYDo2lwQNpEdWyhybzHHYp/48I9a
M2lmwUJL7IHeXgAmXUXstLfaFg+WEi4V9e5R+3rEzkm6yJklRaaLBbsFw2fNCMCk
BUD6IOoEmoc9PEpRIIziwZrrqL00p09wXh7QdofBqOkOf6K4vwYDGTZmnpfaxesR
vwLESnlXZ2kc8lpXEcIvBijnt/K1+Y+9popcWNTFqgU8itMRIiMG+yGgat6zeb+r
ELqvPftZ98pMaM57isLLRirihguaLdijJecMHzTnWL2dB8SXt0olIRwuuizAUOZ8
CkMKwzzeKfoCXKFFnlUpQABhsoN5elIaizT65ew+0mrux49TYyrOwvJK1vjzCdCo
+Dhk92mi/mQmP8LTsdqhj/7BtsHrtrpaJpww749jJg67pWzdFVZ1zfcfSpby7/T5
zf/qOjNAO+VsJtq3MZiqx6C73zOabtezrtXdUiIhILUvSJjGXIPeLXz8+9e3URJf
sgySPuLS1hvPBy4yFhfmcqjkjC9wW78mZo63fTuGMcIrbo8RhQg5ghm7Q6X5a9mR
rzcNERM6CZzHd9jS0QTG
=oE2l
-END PGP SIGNATURE-

Bug#826218: [pkg-apparmor] Bug#826218: Bug#826218: Complain still interferes

[John Johansen]

On 06/05/2016 04:14 PM, Christian Boltz wrote:
> Hello,
> 
> Am Sonntag, 5. Juni 2016, 13:34:19 CEST schrieb Guido Günther:
>> On Sat, Jun 04, 2016 at 06:38:46PM +0200, Christian Boltz wrote:
>>> deny rules are enforced even if you switch the profile to complain
>>> mode, and don't leave any log events behind. You might want to
>>> change them to"audit deny" temporarily to get log events (with
>>> AUDIT).
>>
>> I did not know. Thanks! IMHO this needs to be mentioned in the
>> aa-complain manpage to fulfill the "no PhD in computer science needed
>> for" promise.
> 
> Good point. I just commited an updated manpage upstream (will be in 
> 2.11, 2.10.2 and 2.9.4 whenever they get released).
> 
>> The issue turned out to be environment scrubbing:
>>
>> https://www.redhat.com/archives/libvir-list/2016-June/msg00117.html
>>
>> but I think the issue is still valid: getting an idea what gets
>> dropped to the floor is too hard atm. With complain mode I'd exepct:
>>
>> * denials logged by default
> 
> The whole point of deny rules is to silence the logging  (except if they 
> also have the audit keyword).
> 
> You can enable the logging by adding the audit keyword, but the general 
> rule is not to log anything that is already handled (allowed or denied) 
> in the profile.

I will add that new versions of apparmor will be picking up a new mode
that will not apply quieting for known denials.

> 
>> * a way to audit calls to subprocesses indicating whether the
>>   environment was scrubbed or not
> 
> You'll get this information by reading the profile ;-)   It already had 
> "/usr/sbin/* PUx" [1] which also allowed /usr/sbin/virtlogd - but with 
> environment scrubbing.
> 
> I'm CC'ing another upstream developer, but I wouldn't be surprised if he 
> tells you the same ;-)
> 
So the logging of scrubbing is not where I would like at the moment. We do
have work planned around improving environment variable handling so this
hasn't been touched yet.

With that said if you turn of debug mode apparmor will log a few extra
messages to dmesg (not via the audit subsystem). This will let you see
when environment scrubbing has been applied.

  echo 1 > /sys/module/apparmor/parameters/debug

Also not this isn't going to give you a flood of extra messages its just
for a few things like, env scrubbing, clearing unsafe personality bits,
no new privs etc.

> @John: Do you have a different opinion on Guido's points?
> 

yeah we should be logging extra info. As for complain mode we aren't
changing its behavior but their will be a new mode that is closer to
what I think he wants.

Also it is possible to turn off deny audit quieting by doing

echo -n noquiet >/sys/module/apparmor/parameters/audit

sadly this is global, not per profile

>> * other stuff I might not even know about yet like DBus denials …
> 
DBus denials are weird in that they are handled by an apparmor extension
inside of the user space daemon which will use the audit subsystem if it
can (system bus + audit subsystem is set up) but will fallback to regular
syslog if it can't.

So session bus and system bus can end up in different logs, and there
are a few other oddities. There is some work that could be done to improve
it but right now priorities are else where, and there is a hesitancy
to put a lot more effort into it until the whole kdbus thing is more
clear.

> Actually I can't tell you too much about DBus because only the Ubuntu 
> kernel has DBus support for AppArmor (it's not upstreamed yet), and I'm 
> using openSUSE ;-)
> 
right, sorry I still mean to get you experimental kernels in the build
service. I have just been side tracked.

Bug#790098: Using Gnome HiDPI settings confuses emacs window geometry

[Christophe Troestler]

You should start Emacs with

   GDK_SCALE= emacs

(make a script).

Bug#826527: needrestart: override_rc option does not work

[Paul Wise]

Package: needrestart
Version: 2.8-1
Severity: normal

The option to ignore dbus/NetworkManager does not seem to work:

root@chianamo ~ # grep -riE '(dbus|net).*0' /etc/needrestart/
/etc/needrestart/needrestart.conf:q(^dbus) => 0,
/etc/needrestart/needrestart.conf:q(^network-manager) => 0,
/etc/needrestart/needrestart.conf:q(^NetworkManager) => 0,
root@chianamo ~ # needrestart
Scanning processes...
Scanning candidates...
Scanning linux images...
Running kernel seems to be up-to-date.
Services to be restarted:
 systemctl restart cron.service
 systemctl restart dbus.service
 systemctl restart NetworkManager.service
No containers need to be restarted.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages needrestart depends on:
ii  dpkg   1.18.7
ii  gettext-base   0.19.7-2
ii  libintl-perl   1.24-1
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.21-1
ii  libproc-processtable-perl  0.53-1+b1
ii  libsort-naturally-perl 1.03-1
ii  libterm-readkey-perl   2.33-1+b1
ii  perl   5.22.2-1
ii  xz-utils   5.1.1alpha+20120614-2.1

needrestart recommends no packages.

Versions of packages needrestart suggests:
ii  libnotify-bin0.7.6-2
ii  needrestart-session  0.3-2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#153244: evolution: doesn't respect Mail-Followup-To

[Josh Triplett]

Package: evolution
Version: 3.20.2-2
Followup-For: Bug #153244
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=244791
Control: tags -1 + upstream

"Reply to list" (Ctrl-L) doesn't respect Mail-Followup-To either; that
makes it difficult for people who *do* want to get CCed on list mail.

- Josh Triplett

Bug#826526: needrestart: systemctl_combine option does not work

[Paul Wise]

Package: needrestart
Version: 2.8-1
Severity: normal

The systemctl_combine option does not appear to work:

root@chianamo ~ # grep -r systemctl_combine /etc/needrestart/
/etc/needrestart/needrestart.conf:$nrconf{systemctl_combine} = 1;
/etc/needrestart/conf.d/pabs.conf:$nrconf{systemctl_combine} = 1;
root@chianamo ~ # needrestart
Scanning processes...
Scanning candidates...
Scanning linux images...
Running kernel seems to be up-to-date.
Services to be restarted:
 systemctl restart cron.service
 systemctl restart dbus.service
 systemctl restart NetworkManager.service
No containers need to be restarted.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages needrestart depends on:
ii  dpkg   1.18.7
ii  gettext-base   0.19.7-2
ii  libintl-perl   1.24-1
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.21-1
ii  libproc-processtable-perl  0.53-1+b1
ii  libsort-naturally-perl 1.03-1
ii  libterm-readkey-perl   2.33-1+b1
ii  perl   5.22.2-1
ii  xz-utils   5.1.1alpha+20120614-2.1

needrestart recommends no packages.

Versions of packages needrestart suggests:
ii  libnotify-bin0.7.6-2
ii  needrestart-session  0.3-2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#826525: irssi segfaults with "commands.c: No such file or directory" when /part command is used in query

[Joseph Bisch]

Package: irssi
Version: 0.8.17-1

I am experiencing a segfault with irssi on Debian Jessie. I am able to
consistently reproduce it. I have attached the backtrace, strace, and my
config file for irssi. The steps to reproduce the segfault are:

1) Use my irssi config that is attached (rename irssi.config to config
   and move to ~/.irssi/config).

2) Start irssi from terminal using "irssi" (you can use the --config
   option to specify the location of the config file if you didn't
   follow step one).

3) Enter "/connect irc.freenode.net".

4) Switch to the query with Jeremy_Rand in window 2 (I use esc+2).

5) Enter "/part". After you press enter, you get a segfault.

I am linking to the relevant line in sources.d.n for convenience.[0]

I also was able to reproduce this issue with irssi 0.8.19-1 from Arch
Linux using my Debian Jessie config, so this issue probably belongs
upstream. Please let me know if I should report this upstream.

[0] - http://sources.debian.net/src/irssi/0.8.17-1/src/core/commands.c/#L681

Thank you,

Joseph
681 commands.c: No such file or directory.
(gdb) backtrace
#0  0x0047859a in get_optional_channel (require_name=0, 
data=0x7fffda78, 
active_item=0x7497b0) at commands.c:681
#1  cmd_get_params (data=data@entry=0x4a851f "", 
free_me=free_me@entry=0x7fffdb28, 
count=count@entry=73730) at commands.c:740
#2  0x0045aee1 in cmd_part (data=0x4a851f "", server=0x83fdb0, 
item=0x7497b0)
at irc-commands.c:161
#3  0x0048aeb2 in signal_emit_real (rec=rec@entry=0x703d50, 
params=params@entry=3, 
va=va@entry=0x7fffdbc8, first_hook=) at signals.c:242
#4  0x0048b2fd in signal_emit (signal=signal@entry=0x847280 "command 
part", 
params=params@entry=3) at signals.c:286
#5  0x00477440 in parse_command (item=0x7497b0, server=0x83fdb0, 
expand_aliases=, command=0x847261 "part") at commands.c:899
#6  event_command (line=0x847261 "part", server=0x83fdb0, item=0x7497b0) at 
commands.c:945
#7  0x0048aeb2 in signal_emit_real (rec=rec@entry=0x6e7610, 
params=params@entry=3, 
va=va@entry=0x7fffdd78, first_hook=) at signals.c:242
#8  0x0048b2fd in signal_emit (signal=signal@entry=0x49940d "send 
command", 
params=params@entry=3) at signals.c:286
#9  0x0041a233 in key_send_line () at gui-readline.c:439
#10 0x0048aeb2 in signal_emit_real (rec=rec@entry=0x74a5c0, 
params=params@entry=3, 
va=va@entry=0x7fffdf08, first_hook=) at signals.c:242
#11 0x0048b2fd in signal_emit (signal=signal@entry=0x846eb0 "key 
send_line", 
params=params@entry=3) at signals.c:286
#12 0x0044cdc3 in sig_multi (data=, gui_data=0x0) at 
keyboard.c:653
#13 0x0048aeb2 in signal_emit_real (rec=rec@entry=0x71d3d0, 
params=params@entry=3, 
va=va@entry=0x7fffe0a8, first_hook=) at signals.c:242
#14 0x0048b2fd in signal_emit (signal=signal@entry=0x846ef0 "key 
multi", params=params@entry=3)
at signals.c:286
#15 0x0044d6f3 in key_emit_signal (keyboard=0x7220d0, key=0x731090, 
key=0x731090)
at keyboard.c:552
#16 key_pressed (keyboard=0x7220d0, key=key@entry=0x7fffe1d0 "^J") at 
keyboard.c:608
#17 0x00419a01 in sig_gui_key_pressed (keyp=0xa) at gui-readline.c:406
#18 0x0048aeb2 in signal_emit_real (rec=rec@entry=0x7508d0, 
params=params@entry=1, 
va=va@entry=0x7fffe288, first_hook=) at signals.c:242
#19 0x0048b2fd in signal_emit (signal=, params=1) at 
signals.c:286
#20 0x0041ac77 in sig_input () at gui-readline.c:664
#21 0x0047e133 in irssi_io_invoke (source=, 
condition=, 
data=) at misc.c:54
#22 0x76bfbb6d in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x76bfbf48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x76bfbffc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00416c34 in main (argc=, argv=0x7fffe648) at 
irssi.c:379
servers = (
  { address = "eu.irc6.net"; chatnet = "IRCnet"; port = "6667"; },
  { address = "open.ircnet.net"; chatnet = "IRCnet"; port = "6667"; },
  { address = "irc.efnet.org"; chatnet = "EFNet"; port = "6667"; },
  { 
address = "irc.undernet.org";
chatnet = "Undernet";
port = "6667";
  },
  { address = "irc.dal.net"; chatnet = "DALnet"; port = "6667"; },
  { 
address = "irc.quakenet.org";
chatnet = "QuakeNet";
port = "6667";
  },
  { address = "irc.oftc.net"; chatnet = "OFTC"; port = "6667"; },
  {
address = "irc.gamesurge.net";
chatnet = "GameSurge";
port = "6667";
  },
  { address = "irc.webchat.org"; chatnet = "WebChat"; port = "6667"; },
  { address = "irc.rizon.net"; chatnet = "Rizon"; port = "6667"; },
  { address = "irc.link-net.org"; chatnet = "LinkNet"; port = "6667"; },
  { address = "silc.silcnet.org"; chatnet = "SILC"; port = "706"; }
);

chatnets = {
  IRCnet = {
type = "IRC";
max_kicks = "4";
max_msgs = "5";
 

Bug#824391: [Pkg-shadow-devel] Bug#824391: please add ttySAC* to securetty

[Serge E. Hallyn]

On Mon, Jun 06, 2016 at 01:49:39AM +0200, Steinar H. Gunderson wrote:
> On Mon, May 16, 2016 at 03:01:59PM +, Serge Hallyn wrote:
> > Seems reasonable to me.
> 
> I see there hasn't been a maintainer upload of shadow since November 2014
> (there was an NMU November 2015). Does this mean that if I want this for
> stretch, I'll need to NMU?

Or become the new maintainer? :)

Bug#826511: Aarch64 QEMU Bug

[Ben Hutchings]

On Sun, 2016-06-05 at 16:22 -0400, Mike wrote:
> Package: debian-installer
> Version: 20160516+b1
> 
> Installing Debian using QEMU aarch64 (and looks like arm as well) requires
> extra steps due to lack of initrd and kernel support for virtio devices.
> While there is a workaround documented below, this seems like something
> that should be added to the distro build to incorporate support directly.
> 
> https://gmplib.org/~tege/qemu.html
> 
> See block 14.
> 

We certainly build the virtio drivers and a virtio-modules package for
arm64 and armhf.  So I think this is only a bug in the installer build
configuration.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be
development of an easy way to factor large prime numbers. - Bill Gates


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

Bug#792457: viking: crashed in gdk_rgb_convert_0888 when zooming (bad pointer?)

[Vincent Lefevre]

Control: tags -1 upstream fixed-upstream
Control: severity -1 grave
Control: forwarded -1 https://sourceforge.net/p/viking/bugs/126/

On 2015-08-18 23:27:09 +0200, Ralf Horstmann wrote:
> Got crashes with same backtrace on OpenBSD-current. Reported upstream here:
> 
> https://sourceforge.net/p/viking/bugs/126/
> 
> I've linked this bug in the upstream ticket.

Thanks. I'm raising the severity because this bug occurs very often
and yields data loss (current edition is lost). Moreover, a new
upstream bug-fix release, where this bug is fixed (according to its
changelog), has been available for several months!

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

Bug#821352: Problems with ouse and touchpad settings (it was:Re: Bug#822081: gnome-control-center: Mouse settings have no effect since 3.20)

[Leandro Doctors]

Dear all.

(CC: to #823372, #821352 and #825100 since I believe all these bugs
should be merged.)

I have the same problems (see attached screenshot), namely:
1) The mouse settings panel does not appear complete any more.
2) All customization (natural scrolling, primary button, touchpad's
touch-twice-to-click...) is gone.

Contrary to other people, this bug did not manifest immediately after
upgrading to GNOME 3.20 (something I did around ten days ago), but
only around three days ago.

I am trying to generate the list of installed packages (reportbug is
somehow malfunctioning). However, for your information I am using
(mostly) testing. For now, enjoy my screenshot.

Best,
Leandro

Bug#826368: viking: crash in __strncmp_sse42 when zooming

[Vincent Lefevre]

On 2016-06-05 02:59:08 +0200, Vincent Lefevre wrote:
> With valgrind:
> 
> [...]
> ** (viking:32741): WARNING **: curl_download_uri: http response: 504 for uri 
> http://otile1.mqcdn.com/tiles/1.0.0/osm/18/134592/93539.png
> 
> 
> ** (viking:32741): WARNING **: Download error: 
> /home/vinc17/.viking-maps/t19s-1z0/134592/93539
> ==32741== 
> ==32741== Process terminating with default action of signal 11 (SIGSEGV): 
> dumping core
> ==32741==  Access not within mapped region at address 0x29052042
> ==32741==at 0x58BFB20: gdk_rgb_convert_0888 (gdkrgb.c:2146)
[...]

This one looks more like bug 792457, but I don't know if they are
related.

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

Bug#825918: Bug#813546: Actually 1954 error message groups

[積丹尼 Dan Jacobson]

> "GJ" == Guillem Jover  writes:

GJ> I guess you have tried to install this package many many times? Also
GJ> you are having this problem when installing a package not even from
GJ> unstable but from experimental! This needs fixing in the affected
GJ> package.

Maybe on a clean install one wouldn't see problems, but I even see
directories "/etc/etc/" in those messages.

GJ> Again there is no infinite loop in dpkg, the relevant script just takes
GJ> a list of files and scans for their ownership, this just takes some

Yes, it just very much appears like an infinite loop, as the differing
parts of each error messages (concerned filenames) aren't shown.

GJ> time because I'm assuming it goes over all documentation from
GJ> imagemagick-doc. Perhaps the only possible problem here is that the
GJ> error messages are not clear on what's going on, but because that should
GJ> not happen in the first place and the problem here is really in
GJ> imagemagick, this is at most minor in dpkg, and I could perhaps improve
GJ> the error reporting, I'd rather see such errors so that they can be fixed
GJ> instead of hiding them. So I'm probably just going to close this bug
GJ> again in a bit.

Please instead of closing it, reassign it to the package that caused the
errors. Thanks.

Bug#826161: dpkg-buildpackage -g should create a changes file for 'all' architectures

[Guillem Jover]

Hi!

On Thu, 2016-06-02 at 15:47:03 -0400, Greg Manning wrote:
> Package: dpkg-dev
> Version: 1.17.26
> Severity: normal
> 
> Dear Maintainer,
> 
> When building an architecture independent package:
> 
> "dpkg-buildpackage -A" generates ..._all.changes  (correct)
> 
> but
> 
> "dpkg-buildpackage -g" generates ..._amd64.changes (incorrect)
> 
> i.e. the changes filename incorrectly mentions the architecture of the build 
> machine.

> I have been using 1.17.26 on jessie; 1.18.7 seems to give the same results.
> Note that in 1.18.7, -g is supposed to be equivalent to --build=source,all.
> And --build=source,all generates ..._all.changes (correctly).

I don't see how --build=source,all would generate an _all.changes
files, it just behaves the same as -g, --build=all does generate
_all.changes though. But in any case I'll fix the behavior of -g
and --build=source,all to use all as the arch for the changes file.

Thanks,
Guillem

Bug#826334: dget: removes existing dir by default without asking

[Guillem Jover]

Control: severity -1 wishlist

On Sun, 2016-06-05 at 12:58:50 +0200, Sven Joachim wrote:
> Control: notfound -1 1.17.27
> Control: tags -1 - unreproducible moreinfo

> On 2016-06-05 00:49 +0200, Guillem Jover wrote:
> > Control: severity -1 important
> > Control: tags -1 unreproducible moreinfo

> > On Sat, 2016-06-04 at 17:43:41 +0100, Adam D. Barratt wrote:
> >> Control: reassign -1 dpkg-dev 1.17.27
> >> Control: affects -1 devscripts
> >> Control: retitle -1 dpkg-source -x overwrites existing directories
> >> 
> >> On Sat, 2016-06-04 at 18:08 +0200, ydir...@free.fr wrote:
> >> > dget unpacks the downloaded source by default, even if the target 
> >> > directory was
> >> > pre-existing.  Moreover, it does not just unpack it above the 
> >> > pre-existing dir,
> >> > but removes it first, together with all the other files it may contain !
> >> 
> >> Nope. dget simply calls "dpkg-source -x". The effect is trivially
> >> reproducible by calling "dpkg-source -x somepackage.dsc
> >> an-existing-directory" without needing to involve dget at all.
> >
> > Hmm, I'm afraid I cannot reproduce this on stable nor unstable. I've
> > tried with devscripts, fbset, dpkg-repack and dgit, to try different
> > source formats:
> >
> >   $ dpkg-source -x devscripts_2.16.4.dsc new-dir
> >   dpkg-source: info: extracting devscripts in new-dir
> >   dpkg-source: info: unpacking devscripts_2.16.4.tar.xz
> >   $ dpkg-source -x devscripts_2.16.4.dsc new-dir
> >   dpkg-source: error: unpack target exists: new-dir
> >
> > I'd appreciate if any of you could provide a reproducer for this?
> 
> As Adam had already mentioned: omit the new-dir argument, then
> dpkg-source -x will happily rm -rf the directory into which the source
> package is unpacked.  This behavior has been present "forever" (well,
> the oldest version I could test is dpkg-dev 1.6.15 from potato).

Ah, right, this has been the intended behavior all along. And as such
I'm very much uncomfortable with changing it. I'm fine with adding a
new option to make it error out on existing directory though, which is
what I'm going to do. dget then could make use of it if desired.

Thanks,
Guillem

Bug#783210: glibc: please make the package build reproducibly

[Ximin Luo]

On Mon, 19 Oct 2015 10:11:25 +0200 Aurelien Jarno  wrote:
> It means that the point 3 (usage of __DATE__ and __TIME__) is the only
> one left to address in the version currently in experimental.
> 

Hi, GCC have now added support for SOURCE_DATE_EPOCH so we can use this 
instead. Debhelper now sets this environment variable automatically, and GCC 
should automatically read it, so perhaps we can get rid of the whole 
(3)-related patch, but I haven't tested this yet.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git

Bug#825918: Bug#813546: Actually 1954 error message groups

[Guillem Jover]

Control: severity -1 minor
Control: forcemerge -1 813546

On Fri, 2016-06-03 at 21:17:11 +0800, 積丹尼 Dan Jacobson wrote:
> reopen 825918

> There is actually 1954 error groups on my machine.

I don't know really what that means, though.

> A normal user would and should kill the seemingly runaway situation
> before hit computer locks up or disks get filled.
> 
> # sort /tmp/apt_term_log.txt |uniq -c|sort -nr|head
>1954 dpkg-query: package 'imagemagick' is not installed
>1954 and dpkg --contents (= dpkg-deb --contents) to list their contents.
>1954 Use dpkg --info (= dpkg-deb --info) to examine archive files,
>   2 Processing triggers for libc-bin (2.23-0experimental2) ...
>   1 dpkg: warning: unable to delete old directory 
> '/etc/etc/ImageMagick-6': Directory not empty
>   1 dpkg: warning: unable to delete old directory '/etc/etc': Directory 
> not empty
>   1 dpkg: error processing archive 
> /var/cache/apt/archives/imagemagick_8%3a6.9.2.10+dfsg-2_all.deb (--unpack):
>   1 dpkg-query: no packages found matching imagemagick:all
>   1 dpkg-maintscript-helper: error: directory 
> '/usr/share/doc/imagemagick' contains files not owned by package 
> imagemagick:all, cannot switch to symlink
>   1 Unpacking libmagickwand-6.q16-2:i386 (8:6.9.2.10+dfsg-2+b1) over 
> (8:6.9.2.10+dfsg-1) ...
>

I guess you have tried to install this package many many times? Also
you are having this problem when installing a package not even from
unstable but from experimental! This needs fixing in the affected
package.

Again there is no infinite loop in dpkg, the relevant script just takes
a list of files and scans for their ownership, this just takes some
time because I'm assuming it goes over all documentation from
imagemagick-doc. Perhaps the only possible problem here is that the
error messages are not clear on what's going on, but because that should
not happen in the first place and the problem here is really in
imagemagick, this is at most minor in dpkg, and I could perhaps improve
the error reporting, I'd rather see such errors so that they can be fixed
instead of hiding them. So I'm probably just going to close this bug
again in a bit.

Regards,
Guillem

Bug#826523: ftp.debian.org: RM: src:cross-gcc-defaults -- ROM; superceded by gcc-defaults

[Dima Kogan]

Package: ftp.debian.org
Severity: normal

Hello. Please remove the src:cross-gcc-defaults source package. The
binary packages it produces have been superceded by src:gcc-defaults.

This package has been maintained by Helmut Grohne, Wookey, (Cc-ed here)
and myself.

Thanks
dima

Bug#826524: opensc-pkcs11: Fix interaction with DNIe UI

[Javier Serrano Polo]

Package: opensc-pkcs11
Version: 0.16.0~rc2-1
Severity: minor
Tags: patch

The interaction with the DNIe UI does not work on Firefox because an
alarm interrupts the read operations, aborting the confirmation.
Description: Fix interaction with DNIe UI
 The interaction with the DNIe UI does not work on Firefox because an alarm
 interrupts the read operations, aborting the confirmation. This is fixed by
 using nointr_fgets(). There are side issues:
 * Forked process should abort on failure instead of continuing with OpenSC.
 * Useless initializations with memset().
 * Size adjustments in read and write operations.
Author: Javier Serrano Polo 
Forwarded: https://github.com/OpenSC/OpenSC/pull/789

Index: opensc-0.16.0~rc2/src/libopensc/card-dnie.c
===
--- opensc-0.16.0~rc2.orig/src/libopensc/card-dnie.c	2016-06-05 20:48:32.0 +0200
+++ opensc-0.16.0~rc2/src/libopensc/card-dnie.c	2016-06-06 01:42:11.0 +0200
@@ -162,6 +162,25 @@
 char *user_consent_msgs[] = { "SETTITLE", "SETDESC", "CONFIRM", "BYE" };
 
 /**
+ * Do fgets() without interruptions.
+ *
+ * Retry the operation if it is interrupted, such as with receiving an alarm.
+ *
+ * @param s Buffer receiving the data
+ * @param size Size of the buffer
+ * @param stream Stream to read
+ * @return s on success, NULL on error
+ */
+static char *nointr_fgets(char *s, int size, FILE *stream)
+{
+	while (fgets(s, size, stream) == NULL) {
+		if (feof(stream) || errno != EINTR)
+			return NULL;
+	}
+	return s;
+}
+
+/**
  * Ask for user consent.
  *
  * Check for user consent configuration,
@@ -283,9 +302,8 @@
 		/* call exec() with proper user_consent_app from configuration */
 		/* if ok should never return */
 		execlp(GET_DNIE_UI_CTX(card).user_consent_app, GET_DNIE_UI_CTX(card).user_consent_app, (char *)NULL);
-		res = SC_ERROR_INTERNAL;
-		msg = "execlp() error";	/* exec() failed */
-		goto do_error;
+		sc_log(card->ctx, "execlp() error");
+		abort();
 	default:		/* parent */
 		/* Close the pipe ends that the child uses to read from / write to
 		 * so when we close the others, an EOF will be transmitted properly.
@@ -304,22 +322,24 @@
 			goto do_error;
 		}
 		/* read and ignore first line */
-		fflush(stdin);
+		if (nointr_fgets(buf, sizeof(buf), fin) == NULL) {
+			res = SC_ERROR_INTERNAL;
+			msg = "nointr_fgets() Unexpected IOError/EOF";
+			goto do_error;
+		}
 		for (n = 0; n<4; n++) {
 			char *pt;
-			memset(outbuf, 0, sizeof(outbuf));
-			if (n==0) snprintf(outbuf,1023,"%s %s\n",user_consent_msgs[0],title);
-			else if (n==1) snprintf(outbuf,1023,"%s %s\n",user_consent_msgs[1],message);
-			else snprintf(outbuf,1023,"%s\n",user_consent_msgs[n]);
+			if (n==0) snprintf(outbuf, sizeof outbuf,"%s %s\n",user_consent_msgs[0],title);
+			else if (n==1) snprintf(outbuf, sizeof outbuf,"%s %s\n",user_consent_msgs[1],message);
+			else snprintf(outbuf, sizeof outbuf,"%s\n",user_consent_msgs[n]);
 			/* send message */
 			fputs(outbuf, fout);
 			fflush(fout);
 			/* get response */
-			memset(buf, 0, sizeof(buf));
-			pt=fgets(buf, sizeof(buf) - 1, fin);
+			pt=nointr_fgets(buf, sizeof(buf), fin);
 			if (pt==NULL) {
 res = SC_ERROR_INTERNAL;
-msg = "fgets() Unexpected IOError/EOF";
+msg = "nointr_fgets() Unexpected IOError/EOF";
 goto do_error;
 			}
 			if (strstr(buf, "OK") == NULL) {


smime.p7s
Description: S/MIME cryptographic signature

Bug#816624: Please orphan python-selenium: no reply from current maintainer for months

[Sascha Girrulat]

Hi Thomas,

Am 06.06.2016 um 01:16 schrieb Thomas Goirand:

> Very good. If you need me to sponsor the package, please let me know.
i just ask Guido to sponsor the package selenium-firefoxdriver but maybe
the package python-selenium_2.53.2+dfsg1. It refers to
python-selenium_2.53.2+dfsg1.orig.tar.gz and i couldn't upload the new
source because it's still present from your upload and my uploads with
or without are rejected.

> Also, what about co-maintainance of these packages? Are you open to the
> idea?
That would be fine for me and it would increase the quality of the package.

Regards
Sascha



signature.asc
Description: OpenPGP digital signature

Bug#824391: [Pkg-shadow-devel] Bug#824391: please add ttySAC* to securetty

[Mike Frysinger]

please see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768020;msg=7
-mike


signature.asc
Description: Digital signature

Bug#826522: hdf5: systemwide plugin folders

[Jerome Benoit]

Source: hdf5
Severity: wishlist
Tags: upstream

Dear Maintainer:

Please provide (default) systemwide folders to place hdf5 
plugins/modules:
one within the /usr hierarchy; a second one within the /usr/local 
hierarchy.
This request might be forwarded to the upstream team.

Thanks,
Jerome

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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#643595: Quick review for snes9x

[Sérgio Benjamim]

Hey

We don't need necessarily drop this package. People still likes the gtk 
standalone version.


sergio-br2


On 05/06/2016 06:03, John Paul Adrian Glaubitz wrote:

Hi!

On 06/04/2016 06:52 AM, Sérgio Benjamim wrote:

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

It's the libretro core of Snes9x, basically you use a frontend like RetroArch 
to get access to the core, no gtk or legacy CLI stuff. Wanna move the sponsoring
from this package to there?

Do you want to drop the old snes9x package then? I'd be fine with that
as avoiding duplication is always a good thing.

Adrian

Bug#824391: [Pkg-shadow-devel] Bug#824391: please add ttySAC* to securetty

[Steinar H. Gunderson]

On Mon, May 16, 2016 at 03:01:59PM +, Serge Hallyn wrote:
> Seems reasonable to me.

I see there hasn't been a maintainer upload of shadow since November 2014
(there was an NMU November 2015). Does this mean that if I want this for
stretch, I'll need to NMU?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#763974: [patch] python-pypdf is deprecated

[Luciano Bello]

here is the patch. I would really love to remove python-pypdf. Shall I NMU?

/l--- a/lib/pdfimposer.py
+++ b/lib/pdfimposer.py
@@ -53,9 +53,7 @@ import sys
 import os
 import types
 
-import pyPdf
-import pyPdf.generic
-import pyPdf.pdf
+import PyPDF2 as pyPdf
 
 # XXX: Fix these translatable strings
 try:

Bug#826218: [pkg-apparmor] Bug#826218: Bug#826218: Complain still interferes

[Christian Boltz]

Hello,

Am Sonntag, 5. Juni 2016, 13:34:19 CEST schrieb Guido Günther:
> On Sat, Jun 04, 2016 at 06:38:46PM +0200, Christian Boltz wrote:
> > deny rules are enforced even if you switch the profile to complain
> > mode, and don't leave any log events behind. You might want to
> > change them to"audit deny" temporarily to get log events (with
> > AUDIT).
> 
> I did not know. Thanks! IMHO this needs to be mentioned in the
> aa-complain manpage to fulfill the "no PhD in computer science needed
> for" promise.

Good point. I just commited an updated manpage upstream (will be in 
2.11, 2.10.2 and 2.9.4 whenever they get released).

> The issue turned out to be environment scrubbing:
>
> https://www.redhat.com/archives/libvir-list/2016-June/msg00117.html
> 
> but I think the issue is still valid: getting an idea what gets
> dropped to the floor is too hard atm. With complain mode I'd exepct:
> 
> * denials logged by default

The whole point of deny rules is to silence the logging  (except if they 
also have the audit keyword).

You can enable the logging by adding the audit keyword, but the general 
rule is not to log anything that is already handled (allowed or denied) 
in the profile.

> * a way to audit calls to subprocesses indicating whether the
>   environment was scrubbed or not

You'll get this information by reading the profile ;-)   It already had 
"/usr/sbin/* PUx" [1] which also allowed /usr/sbin/virtlogd - but with 
environment scrubbing.

I'm CC'ing another upstream developer, but I wouldn't be surprised if he 
tells you the same ;-)

@John: Do you have a different opinion on Guido's points?

> * other stuff I might not even know about yet like DBus denials …

Actually I can't tell you too much about DBus because only the Ubuntu 
kernel has DBus support for AppArmor (it's not upstreamed yet), and I'm 
using openSUSE ;-)


Regards,

Christian Boltz

[1] I'm not sure if this rule (and the other broad PUx rules) are a good 
idea [2], but a) I don't know libvirtd good enough to judge on it
and b) that's a totally different topic ;-)

[2] These PUx rules allow to execute _all_ programs, and most of them
unconfined (except if a profile for this program exists). 
I slightly ;-) doubt libvirtd needs to execute all of them...

-- 
[bugzilla is] being as co-operative as a 2 legged donkey
pulling a 10 ton tractor under attack by an army of bees
[Richard Brown in opensuse-factory]


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

Bug#826469: closed by Thomas Goirand <z...@debian.org> (Re: [PKG-Openstack-devel] Bug#826469: Registering keystone endpoint - "unmatched '{' in format")

[Turbo Fredriksson]

On Jun 6, 2016, at 12:15 AM, Debian Bug Tracking System wrote:

> Therefore, closing the bug. If you want to contribute such a fix, I
> welcome you to do so, but IMO, we have much more important things to do.

The "fix" is to _ALWAYS_ put variables in situation marks!
This is considered to be "good practice" (and if one runs any
[shell] script through shellcheck, it will warn).

Bug#826453: closed by Thomas Goirand <z...@debian.org> (Re: [PKG-Openstack-devel] Bug#826453: Creating the temporary my.cfg file when password contains symbols fails connect)

[Turbo Fredriksson]

On Jun 6, 2016, at 12:15 AM, Debian Bug Tracking System wrote:

>> The problem might also exist somewhere in dbconfig.. :(
> 
> Exactly, which makes it pointless to fix in the OpenStack packages.

I did say "also"..

Bug#816624: Please orphan python-selenium: no reply from current maintainer for months

[Thomas Goirand]

On 06/05/2016 10:44 PM, Sascha Girrulat wrote:
> Hi Thomas,
> 
> i did a import of your patches. Thanks a lot for you great work and your
> endless patience.
> 
> I did also a small update to python-selenium_2.53.2+dfsg1-1 with a newer
> dependency to selenium-firefoxdriver. For the related
> selenium-firefoxdriver package i did also a update to the newer version
> 2.53.2. The upload of this one will take a small while because i need a
> update of my pending (sponsored) upload of
> selenium-firefoxdriver_2.48.0-1. It makes sense to update this package
> related to python-selenium because it contains the non-free webdriver
> parts of selenium for firefox.
> 
> Regards
> Sascha

Hi Sascha,

Very good. If you need me to sponsor the package, please let me know.

Also, what about co-maintainance of these packages? Are you open to the
idea?

Cheers,

Thomas Goirand (zigo)

Bug#824673: wine32-development-tools:i386 cannot be installed on amd64

[Jens Reyer]

control: tags -1 + pending
control: tags 823264 + patch

I committed several changes on git branch master to either install
wine32-tools, or 32-bit libwine-dev with wine64-tools, and document how
to get 32-bit results.

They should be in the next "wine-development" release, and if they work
out well I'll apply them for "wine".


On 05/30/2016 10:21 PM, Javier Serrano Polo wrote:
> El dl 30 de 05 de 2016 a les 01:27 +0200, Jens Reyer va escriure: 
>> ${perl:Depends} | perl:any [i386],
> 
> This might break in the future if ${perl:Depends} is substituted with
> "perl, foobar".

I considered this issue, but according to the manpage it resolves to
only one value (perl or perlapi), see below.

Greets
jre

--
commit 2e52d32383b040ff7118e46b441410d64f184655
Author: Jens Reyer 
Date:   Sun Jun 5 19:13:52 2016 +0200

Document generating 32-bit results with the -tools packages.

See: #824673
Thanks: Andrey Gursky and Javier Serrano Polo

commit 4b5983772f8ecc8bf93c5da27f39e6d138ca4ab5
Author: Jens Reyer 
Date:   Sun Jun 5 16:21:58 2016 +0200

Let libwine-dev prefer wine64-tools to wine32-tools.

Otherwise, if libwine-dev is installed from a 32-bit and a 64-bit
arch, the recommends may be resolved to wine32-tools and
wine64-tools (which conflict with each other).

This also prevents issues on arm64 with 32-bit libwine-dev
installed while wine32-tools is not installable because of its
dependencies there.

commit 5854b7a988c4c4da97a5fec59058027a24544dfd
Author: Jens Reyer 
Date:   Sun Jun 5 16:29:31 2016 +0200

Make wineNN-tools multi-arch installable.

Closes: #824673
Closes: #823264 (stable)
Thanks: Javier Serrano Polo

Add alternative dependencies to wine32-tools (i386 only) and make
it M-A:foreign, so amd64 packages can depend on it.

Note: perl:Depends resolves to only one value (perl or perlapi),
so there's currently no risk of a malformed expression. A general
fix has been requested in #824696 (debhelper: dh_perl should
report perl:any when usage is architecture independent).

Also make wine64-tools M-A:foreign, so 32-bit libwine-dev can
depend on it.

commit 2cce63ce6118bac660d7229ee8d9163d70280bbd
Author: Jens Reyer 
Date:   Sun Jun 5 16:04:26 2016 +0200

Add alternative dependency on 32-bit libwine-dev to wine64-tools.

Note: Depending e.g. on libwineVERSION-dev:any doesn't work
because that resolves for the host arch only.

Bug#826521: pulseaudio: auto-mute is not enabled by default

[Salvatore Tomaselli]

Source: pulseaudio
Severity: normal

Dear Maintainer,

I was trying to use a fresh debian installation on my laptop, installing
recommends, and it appears that pulseaudio doesn't automatically mute the
speakers when I plug in a cable in the output jack.

Also, the mixer in KDE showed no clear indication on how to change the setting.

Without pulseaudio, kmix (after enabling all channels) has an option about this.


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

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

Bug#826520: ktorrent: Needless depends on kde-runtime

[Salvatore Tomaselli]

Package: ktorrent
Version: 4.3.1-4
Severity: normal

Dear Maintainer,
ktorrent depends on kde-runtime for no reason.

I satisfied the dependency with equivs and ktorrent is working fine.

This means that the dependency should be removed as it violates Debian policy,
and it might be moved to Suggests or Recommends, if it makes sense to do so.

I suspect that also depending on phonon might not be necessary, but I haven't
tried, since I had it installed for other reasons.

Best

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

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

Versions of packages ktorrent depends on:
ii  kde-runtime5:4.10
ii  ktorrent-data  4.3.1-4
ii  libc6  2.22-10
ii  libgcc11:6.1.1-5
ii  libgeoip1  1.6.9-1
ii  libkcmutils4   4:4.14.20-3
ii  libkdecore54:4.14.20-3
ii  libkdeui5  4:4.14.20-3
ii  libkdewebkit5  4:4.14.20-3
ii  libkdnssd4 4:4.14.20-3
ii  libkio54:4.14.20-3
ii  libknotifyconfig4  4:4.14.20-3
ii  libkparts4 4:4.14.20-3
ii  libkrosscore4  4:4.14.20-3
ii  libktorrent-l10n   1.3.1-5
ii  libktorrent5   1.3.1-5
ii  libphonon4 4:4.9.0-2
ii  libqt4-dbus4:4.8.7+dfsg-8
ii  libqt4-network 4:4.8.7+dfsg-8
ii  libqt4-qt3support  4:4.8.7+dfsg-8
ii  libqt4-xml 4:4.8.7+dfsg-8
ii  libqtcore4 4:4.8.7+dfsg-8
ii  libqtgui4  4:4.8.7+dfsg-8
ii  libqtwebkit4   2.3.4.dfsg-8
ii  libsolid4  4:4.14.20-3
ii  libstdc++6 6.1.1-5
ii  libsyndication44:4.14.10-1+b1
ii  libtag1v5  1.9.1-2.4
ii  phonon 4:4.9.0-2

ktorrent recommends no packages.

Versions of packages ktorrent suggests:
pn  krosspython  

-- no debconf information

Bug#823322: please build "systemd-sysusers" binary

[Dmitry Smirnov]

On Sunday, 5 June 2016 9:58:54 PM AEST Michael Biebl wrote:
> The size is a concern, and we mentioned this before.

How can little size increase be a serious concern?


> This really is a wishlist bug, so bumping the severity is not justified.

This is not a wishlist bug because a strategically important package is 
broken (unusable).

-- 
All the best,
 Dmitry Smirnov.

---

Good luck happens when preparedness meets opportunity.


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

Bug#824566: Debian bug report

[Paul McGuire]

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

 

The problem actually lies in the rstlib package, which has this code
fragment:

 

value = tokin[0].asDict()

ref_path = value.get('ref_path')

if ref_path is not None:

ref_path = " ".join(ref_path.asList())

 

 

In this code, 'tokin' is a pyparsing ParseResults object that is passed into
a parse-time callback.  In version 2.1.0 of pyparsing, I fixed a
long-standing problem in ParseResults.asDict, which did only the shallowest
of conversions of pyparsing's ParseResults objects to nested lists and
dicts. In this case, the 'ref_path' element of 'value' used to be a
ParseResults, which the developer is converting to a list using asList().
With my change in pyparsing 2.1.0, ref_path is now being converted to a list
as part of the improved behavior of asDict(). Unfortunately, this code then
tries to call 'asList()' on that list, which of course, is an error.

 

The fix is to change this code in rstlib to just:

 

value = tokin[0].asDict()

ref_path = value.get('ref_path')

if ref_path is not None:

ref_path = " ".join(ref_path)

 

This change is actually compatible with the old version of pyparsing as well
(since ParseResults also implements list-like iterator behavior). The call
to 'asList()' in this case was never really necessary.

 

I would encourage you to try to get this change in place, as opposed to
reverting pyparsing back to 2.0.3 - there are many other fixes and changes
in the latest 2.1.4 version, and I have a 2.1.5 about to go out this month.

-- Paul McGuire
Austin, Texas, USA
maintainer of pyparsing

(I have also copied Jerome Martin, j...@netiant.com 
, as he is the nominal maintainer of rstlib.)

 



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Bug#826519: Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: libkxl0-dev
Version: 1.1.7-16
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.  Please change the dependency to linux-libc-dev.

Ben.

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

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

Bug#826366: [Pkg-utopia-maintainers] Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

[Michael Biebl]

Am 05.06.2016 um 23:57 schrieb Christoph Anton Mitterer:
> On Sun, 2016-06-05 at 23:44 +0200, Michael Biebl wrote:
>> On remove/purge yes, it makes sense to turn it back into a real file
> 
> but probably only if it's really a symlink to the path used by NM,..
> not e.g. when it's the one from resolvconf?

Sure,
"$(readlink /etc/resolv.conf)" = /var/run/NetworkManager/resolv.conf
would be the test



-- 
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#826366: [Pkg-utopia-maintainers] Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

[Christoph Anton Mitterer]

On Sun, 2016-06-05 at 23:44 +0200, Michael Biebl wrote:
> On remove/purge yes, it makes sense to turn it back into a real file

but probably only if it's really a symlink to the path used by NM,..
not e.g. when it's the one from resolvconf?

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#826518: linux-image-4.5.0-0.bpo.1-armmp: linux-image-4.5.0-0.bpo.2-armmp and linux-image-4.6.0-trunk-armmp fail to boot on cubox-i

[Rainer Dorsch]

Package: src:linux
Version: 4.5.1-1~bpo8+1
Severity: important


Hi,

after upgrading to linux-image-4.5.0-0.bpo.2-armmp my cubox-i did not boot 
anymore. I tested linux-image-4.6.0-trunk-armmp and this resulted in the same 
effect. 

I could not boot with the kernel which had the problem, although reportbug 
requested that ;-)

Booting failure with 4.6.0 from experimental:

U-Boot 2014.10+dfsg1-2 (Nov 02 2014 - 00:31:26)

CPU:   Freescale i.MX6D rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  1 GiB
MMC:   FSL_SDHC: 0
In:serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   Port not available.
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
   scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
** File not found /boot.scr **
** File not found uEnv.txt **
** File not found /zImage **
** File not found /uImage **
938 bytes read in 89 ms (9.8 KiB/s)
Running bootscript from mmc ...
## Executing script at 1080
3620480 bytes read in 308 ms (11.2 MiB/s)
34350 bytes read in 231 ms (144.5 KiB/s)
15046745 bytes read in 13548 ms (1.1 MiB/s)
Booting Debian 4.6.0-trunk-armmp from mmc 0:2...
Kernel image @ 0x1080 [ 0x00 - 0x373e80 ]
## Flattened Device Tree blob at 1800
   Booting using the fdt blob at 0x1800
EHCI failed to shut down host controller.
   Using Device Tree in place at 1800, end 1800b62d

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.6.0-trunk-armmp (debian-
ker...@lists.debian.org) (gcc version 5.3.1 20160509 (Debian 5.3.1-19) ) #1 
SMP Debian 4.6-1~exp1 (20)
[0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), 
cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] Machine model: SolidRun Cubox-i Dual/Quad
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 16 MiB at 0x4f00
[0.00] Memory policy: Data cache writealloc
[0.00] percpu: Embedded 13 pages/cpu @ef6c s20876 r8192 d24180 
u53248
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 260416
[0.00] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 
rootfstype=ext4 ro rootwait console=ttymxc0,115200 console=tty1 elevator=noop
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 
bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Memory: 993568K/1048576K available (7773K kernel code, 932K 
rwdata, 2560K rodata, 1024K init, 390K bss, 38624K reserved, 16384K cma-
reserved,)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xf080 - 0xff80   ( 240 MB)
[0.00] lowmem  : 0xc000 - 0xf000   ( 768 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0xc0008000 - 0xc0b175d8   (11326 kB)
[0.00]   .init : 0xc0c0 - 0xc0d0   (1024 kB)
[0.00]   .data : 0xc0d0 - 0xc0de9274   ( 933 kB)
[0.00].bss : 0xc0deb000 - 0xc0e4c9c4   ( 391 kB)
[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] L2C-310 erratum 769419 enabled
[0.00] L2C-310 enabling early BRESP for Cortex-A9
[0.00] L2C-310 full line of zeros enabled for Cortex-A9
[0.00] L2C-310 ID prefetch enabled, offset 1 lines
[0.00] L2C-310 dynamic clock gating enabled, standby mode enabled
[0.00] L2C-310 cache controller enabled, 16 ways, 1024 kB
[0.00] L2C-310: CACHE_ID 0x41c7, AUX_CTRL 0x76070001
[0.00] Switching to timer-based delay loop, resolution 333ns
[0.07] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 
715827882841ns
[0.27] clocksource: mxc_timer1: mask: 0x max_cycles: 
0x, max_idle_ns: 637086815595 ns
[0.002819] Console: colour dummy device 80x30
[0.003690] console [tty1] enabled
[0.003734] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 6.00 BogoMIPS (lpj=12000)
[0.003787] pid_max: default: 32768 minimum: 301
[0.004004] Security Framework initialized
[0.004034] Yama: disabled by default; enable with sysctl 

Bug#826379: Maintaining of CodeBlocks

[Alexander Gerasiov]

Hello Vincent,

On Sat, 4 Jun 2016 22:29:22 -0700
Vincent Cheng  wrote:


> >> License: RDS-Data-Security
> >>  License to copy and use this software is granted provided that
> >>  it is identified as the "RSA Data Security, Inc. MD5 Message
> >>  Digest Algorithm" in all material mentioning or referencing this
> >>  software or this function.
> >>  .
> >>  License is also granted to make and use derivative works
> >>  provided that such works are identified as "derived from the RSA
> >>  Data Security, Inc. MD5 Message Digest Algorithm" in all
> >>  material mentioning or referencing the derived work.
> >
> > 1. I believe this clause forces Debian to mention RSA Data Security
> > on every html page and in every place where CodeBlock is mentioned.
> > Isn't it?
> >
> > 2. Your main code is GPL v3 (note, 3d version, not 3+, because there
> > are several files which don't allow "any later version"). But GPL is
> > not compatible with such advertising clauses, see famous BSD-4 vs
> > GPL example:
> > http://www.gnu.org/licenses/license-list.html#OriginalBSD
> >
> > I cc debian-legal, these guys will correct me, if I'm wrong.
> 
> Ah, you're right that the RSA license contains wording that is quite
> similar to 4-clause BSD's advertising clause. I've filed #826379 to
> keep track of this issue, and will report a bug upstream as well.
> 
> I do want to point out that 4-clause BSD is actually DFSG-compatible
> and suitable for Debian main [1], so there's still no reason to
> believe that the RSA md5 license violates the DFSG as you originally
> claim, even though it contains an advertising clause. Codeblocks is
> non-distributable merely due to GPL's incompatibility with the RSA md5
> license (not because it's non-free).

1. Well it's clear that it's not GPL compatible, so you could not
redistribute it in binary form, so it's _technically_ violate DFSG.

2. This license is much more restrictive then BSD one. It's not only
require you to mention original author in your advertise. It says you
must attribute CodeBlocks as "derived from the RSA Data Security, Inc.
MD5 Message Digest Algorithm" in "_all_ material _mentioning_ or
referencing the derived work". As for me this is inappropriate for Free
Software. (e.g. I don't think it will pass The dissident test)

But yes, it's somewhere on the edge between free and non-free, so other
person could judge a little bit different and consider it as
DFSG-compliant (but still GPL-incompatible).

Anyway, there are some free md5 implementation, so it's not difficult
to fix this problem. Take a look at the patch attached. (I have not
really tested it, but it looks Ok.)


-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: g...@cs.msu.su  Homepage: http://gerasiov.net  Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1
Author: Alexander Gerasiov 
	Alexander Peslyak 
Description: Replace MD5 implemention.
 Use one by Alexander Peslyak, better known as Solar Designer 
 insted of original by RSA Data Security, Inc. with GPL-incompatible license.
Bug-Debian: http://bugs.debian.org/826379
diff --git a/src/plugins/contrib/source_exporter/wxPdfDocument/Makefile.am b/src/plugins/contrib/source_exporter/wxPdfDocument/Makefile.am
index 6ca0ad4..de8bf9d 100644
--- a/src/plugins/contrib/source_exporter/wxPdfDocument/Makefile.am
+++ b/src/plugins/contrib/source_exporter/wxPdfDocument/Makefile.am
@@ -47,7 +47,8 @@ libwxPdfDocument_la_SOURCES = src/pdfannotation.cpp \
 src/pdfrijndael.cpp \
 src/pdftemplate.cpp \
 src/pdfutility.cpp \
-src/pdfxml.cpp
+src/pdfxml.cpp \
+src/md5.c
 
 noinst_HEADERS = include/wx/pdfannotation.h \
 include/wx/pdfarraydouble.h \
diff --git a/src/plugins/contrib/source_exporter/wxPdfDocument/src/md5.c b/src/plugins/contrib/source_exporter/wxPdfDocument/src/md5.c
new file mode 100644
index 000..52d96ac
--- /dev/null
+++ b/src/plugins/contrib/source_exporter/wxPdfDocument/src/md5.c
@@ -0,0 +1,296 @@
+/*
+ * This is an OpenSSL-compatible implementation of the RSA Data Security, Inc.
+ * MD5 Message-Digest Algorithm (RFC 1321).
+ *
+ * Homepage:
+ * http://openwall.info/wiki/people/solar/software/public-domain-source-code/md5
+ *
+ * Author:
+ * Alexander Peslyak, better known as Solar Designer 
+ *
+ * This software was written by Alexander Peslyak in 2001.  No copyright is
+ * claimed, and the software is hereby placed in the public domain.
+ * In case this attempt to disclaim copyright and place the software in the
+ * public domain is deemed null and void, then the software is
+ * Copyright (c) 2001 Alexander Peslyak and it is hereby released to the
+ * general public under the following terms:
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted.
+ *
+ * There's ABSOLUTELY NO WARRANTY, express or implied.
+ *
+ * (This is a heavily cut-down "BSD license".)
+ *
+ * This differs from Colin Plumb's older 

Bug#826366: [Pkg-utopia-maintainers] Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

[Michael Biebl]

Hi Julian


Am 05.06.2016 um 01:56 schrieb Julian Gilbey:
> I have been having some problems with network-manager recently (as
> reported in another bug report), so I thought I'd try out wicd
> instead.  I purged NM and the related packages, but wicd would not
> work.  I tracked down the reason: /etc/resolv.conf was still symlinked
> to the now non-existent file /var/run/NetworkManager/resolv.conf
> 
> So when network-manager shuts down, it should revert /etc/resolv.conf
> to a regular file.  This should also be checked when the package is
> removed (and unarguably when the package is purged).

I'm not convinced replacing /etc/resolv.conf on stop is a good idea, so
I won't do that.

On remove/purge yes, it makes sense to turn it back into a real file
(I'll probably just make it an empty one), since other tools expect it
to be a file and behave differently if it's a symlink.

Regards,
Michael
-- 
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#812495: wireshark-qt: "No interface selected" when clicking on "Start capturing packets" or "Restart current capture"

[Balint Reczey]

Control: severity 826385 normal
Control: forcemerge -1 826385

Hi,

On Sat, 20 Feb 2016 20:17:56 +0100 Eduard Bloch  wrote:
> Control: severity 812495 normal
> 
> I disagree on the severity. This leaves the mentioned control buttons in
> defacto broken state, they are not usable anymore.

I provided a workaround in the other bug.

> 
> Did upstream test this UI at all?

Yes, but apparently there are still bugs to be fixed. Please use the GTK
UI until the Qt UI fits your needs and thank you for the bug reports.

Cheers,
Balint

Bug#677865: [PATCH] Always use flock for file locking; drop Recommends on libfile-fcntllock-perl

[Josh Triplett]

Control: tags -1 + patch

The attached patch implements the change I suggested, dropping fcntl
locking in favor of flock, and documenting that change in the changelog
along with the rationale.

- Josh Triplett
>From 0c6eddc8200e7bea482ad65c5870f7977847d26a Mon Sep 17 00:00:00 2001
From: Josh Triplett 
Date: Sun, 5 Jun 2016 14:27:38 -0700
Subject: [PATCH] Always use flock for file locking; drop Recommends on
 libfile-fcntllock-perl

Per the flock(2) manpage, NFS clients going back to Linux 2.6.12
translate flock into an fcntl lock on the entire file.
---
 debian/changelog |  6 ++
 debian/control   |  2 +-
 scripts/Dpkg/File.pm | 18 ++
 3 files changed, 9 insertions(+), 17 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index f963c99..1c5c8d8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,11 @@
 dpkg (1.18.8) UNRELEASED; urgency=medium
 
+  [ Josh Triplett ]
+  * Always use flock for file locking, dropping optional use of fcntl locking
+via File::FcntlLock; drop Recommends on libfile-fcntllock-perl.  Per the
+flock(2) manpage, NFS clients going back to Linux 2.6.12 translate flock
+into an fcntl lock on the entire file.  Closes: #677865, #679777
+
   [ Updated programs translations ]
   * German (Sven Joachim).
 
diff --git a/debian/control b/debian/control
index 80bd9a4..3916790 100644
--- a/debian/control
+++ b/debian/control
@@ -70,7 +70,7 @@ Priority: optional
 Architecture: all
 Multi-Arch: foreign
 Depends: dpkg (>= 1.16.3), perl, ${misc:Depends}
-Recommends: libfile-fcntllock-perl, bzip2, xz-utils
+Recommends: bzip2, xz-utils
 Suggests: debian-keyring, gnupg | gnupg2, gpgv | gpgv2,
  gcc | c-compiler, binutils, patch
 Breaks: dpkg-dev (<< 1.15.6), patch (<< 2.7)
diff --git a/scripts/Dpkg/File.pm b/scripts/Dpkg/File.pm
index c6ae326..f50099e 100644
--- a/scripts/Dpkg/File.pm
+++ b/scripts/Dpkg/File.pm
@@ -34,22 +34,8 @@ use Dpkg::ErrorHandling;
 sub file_lock($$) {
 my ($fh, $filename) = @_;
 
-# A strict dependency on libfile-fcntllock-perl being it an XS module,
-# and dpkg-dev indirectly making use of it, makes building new perl
-# package which bump the perl ABI impossible as these packages cannot
-# be installed alongside.
-eval 'use File::FcntlLock';
-if ($@) {
-warning(g_('File::FcntlLock not available; using flock which is not NFS-safe'));
-flock($fh, LOCK_EX)
-or syserr(g_('failed to get a write lock on %s'), $filename);
-} else {
-eval q{
-my $fs = File::FcntlLock->new(l_type => F_WRLCK);
-$fs->lock($fh, F_SETLKW)
-or syserr(g_('failed to get a write lock on %s'), $filename);
-}
-}
+flock($fh, LOCK_EX)
+or syserr(g_('failed to get a write lock on %s'), $filename);
 }
 
 sub file_slurp {
-- 
2.8.1

Bug#826517: sucrack: Problems while searching for a new upstream version

[Marcos]

Package: sucrack
Version: 1.2.3-1
Severity: minor

Dear Maintainers

Uscan had problems while searching for a new upstream version of sucrack due to
some changes in the URLs at upstream web. I send a patch for debian/watch file
in order to fix this issue.



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

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

Versions of packages sucrack depends on:
ii  libc6  2.19-18+deb8u4

sucrack recommends no packages.

sucrack suggests no packages.
 debian/watch | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/watch b/debian/watch
index af5df3c..345f80f 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,4 @@
 version=3
-http://labs.portcullis.co.uk/application/sucrack /download/sucrack-(.*)\.tar\.gz
+
+https://labs.portcullis.co.uk/tools/sucrack/ https://labs.portcullis.co.uk/download/sucrack-(.*)\.tar\.gz
+

Bug#826303: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#826303: virtualbox-dkms: Installation unsuccesfull)

[Gianfranco Costamagna]

Hi,



>It was not my intention to use an old kernel.
>
>It seems strange to me that the routine 'apt-get upgrade' haven't  
>upgraded the kernel.


yes, the main difference between upgrade and dist-upgrade is the kernel
upgrade :)
>'apt-get dist-upgrade' helped, I just forgot about dpkg-reconfigure  
>virtualbox-dkms.
>
>Now the problem is solved, thank you very much for your help.


I'm really happy your system is back on track!
BTW if you know how to write some documentation, and where, I'm happy to
listen :)

Gianfranco

-- 
Prof. dr hab. Janusz S. Bień -  Uniwersytet Warszawski (Katedra  
Lingwistyki Formalnej)
Prof. Janusz S. Bień - University of Warsaw (Formal Linguistics Department)
jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/

Bug#826516: grub-probe: double free or corruption in special case (fixed upstream)

[Markus Schuster]

Package: grub-common
Version: 2.02~beta2-22+deb8u1

In some special cases grub-probe fails with "double free or corruption 
(fasttop)". 

My HDD layout looked like that:
4 HDDs, GPT:
1) 1MB bios_boot
2) MD RAID1 (spanning all 4 HDDs), /boot, ext4
3) MD RAID1 (spanning 2x2 HDDs), PVs for LVM (stripped LVs)

grub-install crashed during Debian installation, preventing a successfull 
Debian installation, but it's really grub-probe causing the problem.
The same setup using MSDOS partitioning scheme works without problems.

It's actually fixed upstream:
http://savannah.gnu.org/bugs/?41582

Fixed in Ubuntu as well:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1330963

Hope that's enough information.

Best regards,
Markus

Bug#822701: samtools: FTBFS: UNEXPECTED PASS: Task worked when we expected failure;

[Afif Elghraoui]

Many thanks for the detailed explanation. It's very helpful and
informative, but I'll just reply to a couple points here.

على الجمعـة  3 حزيران 2016 ‫04:12، كتب John Marshall:
> On 1 Jun 2016, at 05:25, Afif Elghraoui  wrote:
> 
> Thank you; I am glad to see the specific contexts leading to your concerns 
> and sorry to have interpreted the previous comment as FUD.
> 

I'm glad everything is all cleared up now.

[...]
> I am sure you agree that fixing bugs is beneficial.  Unfortunately it is 
> always the case that client software's test suites may be broken by bug fixes 
> in a library used (if only because expected output differs), so it is 
> possible that you may have to tolerate mere test failures when building 
> old-{sam,bcf}tools-with-newer-htslib (or patch the old release's test suite 
> until it succeeds).
> 
> But presumably Debian has some policy for this scenario, which is surely not 
> uncommon?
>

The breakage is not really a big problem for us, because the failures
only appear in Debian Unstable during the gap between when htslib is
updated and samtools and bcftools follow (and they are packaged to
require at least the corresponding version of htslib) . Any stable
release should have a set of matching versions of the three packages and
people using Unstable should know what they're in for.


Many thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#826515: gwakeonlan: NMU

[Gianfranco Costamagna]

Package: gwakeonlan
Version: 0.5.1-1.1
Severity: serious
Justification: useless package
Tags: patch pending

Dear maintainer,

I've prepared an NMU for gwakeonlan (versioned as 0.5.1-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.


Gianfranco


debdiff
Description: Binary data

Bug#821308: Bug doesn't appear in 4.5.4-1

[Nicholas D Steeves]

control: notfound -1 linux/4.3.5-1
control: fixed -1 linux/4.5.0-2

Hi Markus,

Thank you for the confirmation! :-)

Cheers,
Nicholas

Bug#826374: mate-desktop: Provide an alternative GTK2 build of MATE

[MENGUAL Jean-Philippe]

Le 05/06/2016 à 10:28, John Paul Adrian Glaubitz a écrit :
> On 06/05/2016 04:20 AM, Tom Maneiro wrote:
>> Recently MATE 1.14 landed on Testing, which brought to the table a change of
>> massive importance: the switch to GTK3 from GTK2. While this was a expected
>> change, clearly outlined at upstream's roadmap (it's basically their only
>> choice if they want to support Wayland), for some users dealing with constant
>> (and INTENTIONAL) breakages at GTK3 upstream (themes being the #1 offender,

Could you precise the problem? What are the problems you have, exactly?
Are they reported somewhere against DTK?

That's right it will be hard to maintain 2 GTK releases, as there are 3
people and probably still one release before freeze, or bugs. But if you
report bugs, probably we can fix them in GTK or MATE, include them in
next stable, and go ahead.


> Moreover, they have actually finished the design recently and it's now
> considered stable, see [1].
> 
>> among other things) it's an undesired and uncomfortable change for such users
>> (including myself). For now I don't really care about Wayland support (not 
>> that
>> I don't want it, but right now it isn't a priority for my specific needs).
>> Dealing with such upstream issues at GTK3 is annoying to the point of making
>> MATE unusable for some of us!

Why? What kind of problems do you experience?

> "for me", "for some of us", "I don't care about Wayland support". Do you see
> a pattern here? I mean, I don't think I need to explain more why those are
> actually very bad arguments.
> 
> Linux desperately needs Wayland to replace X11 because the latter is an 
> absolute
> mess [2] and a security nightmare. They are still finding and fixing X.Org
> security issues all the time and the fact that the X server runs as root
> is a huge problem.
> 
>> Fortunately MATE doesn't intend to drop GTK2 support yet, and 1.14 can still 
>> be
>> built against GTK2. Checking other distros, there are PPAs for Ubuntu (albeit
>> aimed at older LTS releases), but obviously we need a Debian-specific
>> alternative. What I suggest is having both flavors of MATE (GTK2 and GTK3)
>> available, at least for a while. Obviously you can't have both installed at 
>> the
>> same time, so you can choose between GTK versions and the packages will take
>> care of the rest.
> 
> You know that this basically doubles the amount of work that the maintainers
> have, don't you? I think you underestimate the effort required to fulfill
> your request. Making both MATE GTK2 and GTK3 builds would mean the MATE
> maintainers would have to maintain approximately 100 packages instead
> of just 51 as of now [3]. Do you really expect the maintainers to take
> this additional load of work just because some users are feeling they
> don't want to use a GTK3-based version of MATE?
> 
> This isn't even taken then security implications into considerations
> into account which arise when having to deal with effectively a
> second desktop which builds on top of an outdated and soon to be
> deprecated version of GTK.
> 
> Like with Qt3, we can be quite confident that Debian is going to
> drop support for GTK2 at some point simply because having a set
> of libraries which are used by so many other packages in the
> distribution without active maintenance and thus security support
> is not acceptable in Debian.
> 
>> Really, I love MATE to the point of it being my DE of choice for Linux, and 
>> I'm
>> using it across all of my desktop Debian installs, but the switch to GTK3 
>> have
>> made me reconsider my choice of desktop, as I'm tired of dealing with the
>> obvious disconnect among GTK3 developers with its real-world users.

Explain your points. You know, the Debian you should use is stable to
get GTK2. And testing should be to prepare future. If future could be a
problem, explain why and let's fix problems. Are GTK devs (at least
maintainers) aware of it? I heard of weird upstream decisions, but I
think users feedback are needed to help Debian patching or not GTK.

Regards,

> Sorry, but we cannot take request of individual users into consideration and
> as I have explained above, there are actual reasons why this particular
> decision was made, the primary concern being security. We are not
> going to rollback any decisions which improve security in the long
> time.
> 
> If you feel uncomfortable with the changes, you are free to stay on
> Jessie which is going to be supported until 2020 or switch to any
> other distribution of your choice. I am pretty sure that most
> distributions will drop GTK2 support at some point, so you will not
> have much choice, I'm afraid.
> 
> Alternatively, you can try building MATE based on GTK2 yourself,
> or, use a source-based distribution like Gentoo which will allow
> you to build MATE with GTK2 support without much effort.
> 
> Thanks,
> Adrian
> 
>> [1] https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/
>> [2] https://www.youtube.com/watch?v=RIctzAQOe44
>> [3] 

Bug#826514: chromium bug

[-]

Package: chromiumVersion: all bug: chromium (64-bit) compilation is wrong. atom 
cpu-s throw illegal instruction on start. chromium not work on some atom cpu-s 
(probably lack of sse3, or other instructions). please compile every module 
with -march=k8, so it will run properly. thankyou. affected cpu: n455 
greetingsGeri

Bug#826043: apt: gpg validation fails on hurd

[Amos Jeffries]

On 3/06/2016 10:38 p.m., David Kalnischkies wrote:
> 
> btw: I just checked: I introduced the first of the two finds (which is
> the more obvious problem as that codepath is used more) on 7 Jul 2015
> (25f27319) [the other is 6 Dec 2015], so that problem isn't recent but
> lingers there since 1.1 and I have to wonder if something changed in
> regards to this on hurd (or d-i) or if that really is some huge
> Baader-Meinhof bias… [2]
> 
> (and I am bit surprised we had nobody on non-hurd complain about
> 'strange' messages being emitted while using apt-key – but perhaps that
> just means nobody is using apt-key anymore… if only that were true…)


FWIW; I had these messages show up around the end of year after
upgrading a previous install. But that installation was screwed up in
may ways so I didn't report bugs. The usual apt-keys solution seemed to
fix it then but not recently.

This bug was already being discussed before I got satisfied that its a
bug in apt and not myself.

Amos

Bug#826513: Does not create the rabbitmq user specified

[Turbo Fredriksson]

Package: ironic-common
Version: 1:5.1.0-2
Severity: normal

The config/postinst does as for a RabbitMQ user (defaults to 'guest'),
but if other user specified, this is not created.

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/16 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 ironic-common depends on:
ii  adduser3.114
ii  dbconfig-common2.0.4
ii  debconf [debconf-2.0]  1.5.59
ii  ipmitool   1.8.17-1
ii  lsb-base   9.20160110
ii  python-ironic  1:5.1.0-2
pn  python:any 
ii  sqlite33.13.0-1
ii  sudo   1.8.15-1.1

ironic-common recommends no packages.

ironic-common suggests no packages.

-- debconf information:
* ironic/rabbit_password: (password omitted)
  ironic-common/app-password-confirm: (password omitted)
  ironic-common/pgsql/admin-pass: (password omitted)
  ironic-common/mysql/admin-pass: (password omitted)
  ironic-common/password-confirm: (password omitted)
  ironic-common/mysql/app-pass: (password omitted)
* ironic/admin-password: (password omitted)
  ironic-common/pgsql/app-pass: (password omitted)
  ironic-common/remove-error: abort
* ironic/configure_db: true
  ironic-common/mysql/method: Unix socket
  ironic-common/db/dbname: ironicdb
* ironic/enabled_drivers: pxe_ipmitool, pxe_ipminative, pxe_ssh, pxe_seamicro, 
pxe_iboot, pxe_ilo, pxe_drac, pxe_snmp
* ironic/auth-host: 127.0.0.1
  ironic-common/pgsql/authmethod-user: password
  ironic/admin-user: admin
  ironic-common/passwords-do-not-match:
  ironic-common/install-error: abort
  ironic-common/remote/port:
* ironic-common/database-type: mysql
  ironic-common/pgsql/changeconf: false
  ironic-common/pgsql/no-empty-passwords:
  ironic-common/remote/newhost:
  ironic-common/purge: false
  ironic-common/pgsql/admin-user: postgres
* ironic-common/dbconfig-install: true
  ironic-common/db/app-user: ironic-common
  ironic-common/missing-db-package-error: abort
* ironic-common/mysql/admin-user: debian-sys-maint
  ironic-common/pgsql/authmethod-admin: ident
  ironic/admin-tenant-name: admin
  ironic-common/internal/reconfiguring: false
* ironic/rabbit_userid: openstack
  ironic-common/remote/host: localhost
  ironic-common/internal/skip-preseed: false
* ironic/rabbit_host: localhost
  ironic-common/dbconfig-remove: true
  ironic-common/dbconfig-reinstall: false
  ironic-common/pgsql/manualconf:
  ironic-common/upgrade-error: abort
  ironic-common/db/basepath: /var/lib/ironic
  ironic-common/upgrade-backup: true
  ironic-common/pgsql/method: TCP/IP
  ironic-common/dbconfig-upgrade: true

Bug#825957: wireshark-common: Please don't depend twice on "debconf"

[Bálint Réczey]

Control: tags -1 confirmed pending

Hi Manuel,

2016-05-31 20:02 GMT+02:00 Manuel A. Fernandez Montecelo :
> Package: wireshark-common
> Version: 2.0.3+geed34f0-1
> Severity: wishlist
>
> Hi,
>
>   $ apt-cache show wireshark-common | sed -n '/^Depends: / s|, |,\n  |gp'
>   Depends: libc6 (>= 2.15),
> libcap2 (>= 1:2.10),
> libgcrypt20 (>= 1.7.0),
> libglib2.0-0 (>= 2.31.18),
> libnl-3-200 (>= 3.2.7),
> libnl-genl-3-200 (>= 3.2.7),
> libpcap0.8 (>= 1.5.1),
> libwireshark6 (>= 2.0.3+geed34f0-1),
> libwiretap5 (>= 2.0.3+geed34f0-1),
> libwsutil6 (>= 1.99.2),
> zlib1g (>= 1:1.1.4),
> debconf (>= 0.5) | debconf-2.0,
> debconf,
> libcap2-bin
>
>
> I think that the extra "debconf" in debian/control is causing the last one,
> while the first ones are generated automatically by ${misc:Depends} or 
> similar.
>
> debconf is "Prio: required" so probably it's unneeded in any case, but besides
> that the dependency prevents to switch to "cdebconf", which in principle 
> should
> be a valid substitute.
>
> So I think that, either way, the explicit dependency can and probably should 
> be
> removed from the wireshark-common package definition in debian/control.

Thank you for the bug report. I'll fix that in the next upload.

Cheers,
Balint

Bug#826406: [Pkg-clamav-devel] Bug#826406: Too abrupt removal of AllowSupplementaryGroups option in stable

[Hans van Kranenburg]

Hi Sebastian,

On 06/05/2016 08:09 PM, Sebastian Andrzej Siewior wrote:

On 2016-06-05 13:27:08 [+0200], Hans van Kranenburg wrote:


The version in the main Debian Stable archive (so not in the additional
jessie-updates) has the option AllowSupplementaryGroups removed (see
#822444), which prevents the program from starting when this option is
present in the configuration file:

clamd[27916]: ERROR: Parse error at line 12: Unknown option
AllowSupplementaryGroups
clamd[27916]: ERROR: Can't open/parse the config file /etc/clamav/clamd.conf

I had to set this option to be able to use clamav with postfix on my
incoming mail servers, and I should not expect them to stop processing mail
because of stable updates.

Updates of packages in Debian Stable must never break existing installations
by changing APIs (configuration file considered being some kind of API).


I wasn't aware that this might break existing installations. I had always the
debconf popping up and the the diff was simple so…


At least make the option deprecated and ignore it with a warning if set, and
only make it disappear when upgrading to Stretch.


So you want me to do another stable update and ignore this option if
set/unset. Sounds reasonable give the circumstances. Did you have
unattended-upgrades running?


Yes, it was upgraded by unattended, so my day started with figuring out 
what happened, after a report from a user expecting some mail, and 
nagios yelling about the deferred mail queue size in a few locations.


I'd recommend to do a regression update, since you don't know where this 
configuration exists and since it's possible to get those mail servers, 
or whatever it is going again with another update if the user didn't 
find out yet it was broken.


I don't think the change of forcing/defaulting the option to True would 
lead to any problem in stable, as the whole option was a bit stupid to 
begin with imho. It took me a few hours and a few w*f moments while 
upgrading from Wheezy a while ago to debug and find out about it. :o)


Going back to the old behaviour is also not an option, because it will 
make users angry who found out, or read this report today, threw out the 
option to fix it and then have their clamav broken another time. :D


Thanks,

--
Hans van Kranenburg - System / Network Engineer
T +31 (0)10 2760434 | hans.van.kranenb...@mendix.com | www.mendix.com

Bug#826512: [systemd] automount hangs after first unmount

[Michael Biebl]

Control: forwarded -1 https://github.com/systemd/systemd/issues/3332
Am 05.06.2016 um 22:29 schrieb Adrien CLERC:

> Recently (maybe after upgrade to systemd 230?), my automount settings
> only work for the first mount request.

This should be
https://github.com/systemd/systemd/issues/3332
which is fixed by
https://github.com/systemd/systemd/pull/3434


-- 
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#816624: Please orphan python-selenium: no reply from current maintainer for months

[Sascha Girrulat]

Hi Thomas,

i did a import of your patches. Thanks a lot for you great work and your
endless patience.

I did also a small update to python-selenium_2.53.2+dfsg1-1 with a newer
dependency to selenium-firefoxdriver. For the related
selenium-firefoxdriver package i did also a update to the newer version
2.53.2. The upload of this one will take a small while because i need a
update of my pending (sponsored) upload of
selenium-firefoxdriver_2.48.0-1. It makes sense to update this package
related to python-selenium because it contains the non-free webdriver
parts of selenium for firefox.

Regards
Sascha

Am 05.06.2016 um 21:07 schrieb Sascha Girrulat:
> Hi,
> 
> omg sry. Id used a mail client on a other workstation and it filtered
> all this mail into a spam folder. I'm really sorry i know that my
> responses are not really fast but something like that should not happen.
> Please accept my apologies.
> 
> I just saw the upload and then i started to search whats going wrong and
> found this mails.
> 
> There a some more smaller bugs in the package left if you like i could
> apply the patchsets and start to fix them immediately.
> 
> Regards
> Sascha
> 
> Am 31.05.2016 um 19:54 schrieb Mattia Rizzolo:
>> On Tue, May 31, 2016 at 07:03:05PM +0200, Thomas Goirand wrote:
 This timeframe doesn't designate a person as MIA, sorry.
>>>
>>> Hum... ok. What's the usual timeframe then?
>>
>> Usually we start "pestering" people after they are inactive for more
>> than a year.
>> There are exception of course.
>>
>>> The unresponsiveness of maintainers combined with the strong ownership
>>> of packages is one thing which very frustrating in Debian. It gives the
>>> feeling that no mater what, we can't do anything.
>>
>> Yes, I'm sure you know that's a common complaint from a lot of people
>> about how debian works.  The situation improved though.
>>
>>> Would you consider then, that I is ok to NMU the package, to upgrade to
>>> the latest upstream release and address the 2 other open bugs, plus some
>>> packaging clean-ups (if needed, as I haven't checked yet...)?
>>
>> An NMU is always fine, assuming the usual procedure, that I'm sure you
>> know very well, is followed.
>>
> 



signature.asc
Description: OpenPGP digital signature

Bug#826241: [Pkg-dns-devel] Bug#826241: Bug#826241: unbound: Provide $named facility under systemd

[Michael Biebl]

Am 05.06.2016 um 22:34 schrieb Michael Biebl:

> With that all said, attached is an updated unbound-resolvconf.service,
> which should work properly.

3rd time's the charm. I typoed the Condition (Excutable)

Fixed service file attached.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
[Unit]
Description=Unbound DNS server via resolvconf
After=unbound.service
PartOf=unbound.service
ConditionFileIsExecutable=/sbin/resolvconf

[Service]
ExecStart=/usr/lib/unbound/package-helper resolvconf_start
ExecStop=/usr/lib/unbound/package-helper resolvconf_stop

[Install]
WantedBy=unbound.service


signature.asc
Description: OpenPGP digital signature

Bug#826241: [Pkg-dns-devel] Bug#826241: Bug#826241: unbound: Provide $named facility under systemd

[Michael Biebl]

Hi

Am 04.06.2016 um 23:23 schrieb Michael Biebl:
> Control: tags -1 - patch
> 
> Am 04.06.2016 um 22:50 schrieb Michael Biebl:
>> I think we should have a working solution now, so I'm tentatively
>> marking this bug with patch-available. 
> 
> Hm, looks like there is still a deadlock situation with the service
> files I attached earlier. Therefor removing the patch tag again for now.
> Will investigate.

Ok, I guess I have the missing ingredient now. We need to make the
unbound-resolvconf.service unit use Type=simple not oneshot.
oneshot blocks until the started process has completed, with Type=simple
we don't block.

Also (and this is stolen from bind9), we probably want

[Install]
WantedBy=unbound.service

This makes sure when unbound.service is started, the resolvconf service
is as well.
Using PartOf=unbound.service only takes care of the stop and restart case.

With that all said, attached is an updated unbound-resolvconf.service,
which should work properly.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
[Unit]
Description=Unbound DNS server via resolvconf
After=unbound.service
PartOf=unbound.service
ConditionFileIsExcutable=/sbin/resolvconf

[Service]
ExecStart=/usr/lib/unbound/package-helper resolvconf_start
ExecStop=/usr/lib/unbound/package-helper resolvconf_stop

[Install]
WantedBy=unbound.service


signature.asc
Description: OpenPGP digital signature

Bug#826512: [systemd] automount hangs after first unmount

[Adrien CLERC]

Package: systemd
Version: 230-2
Severity: normal

--- Please enter the report below this line. ---
Hi,

Recently (maybe after upgrade to systemd 230?), my automount settings
only work for the first mount request.

E.g., I have in fstab:

belette:/nas/musique /home/adrien/Musiquenfs   
defaults,users,noauto,x-systemd.automount,x-systemd.idle-timeout=10s   
00

The 10s setting is for debugging purpose, I usually use 10m.

# systemctl start home-adrien-Musique.automount
# journalctl -u home-adrien-Musique.automount -u
home-adrien-Musique.mount -f
-- Logs begin at dim. 2016-06-05 08:11:02 CEST. --
juin 05 22:17:53 complexe systemd[1]: Set up automount
home-adrien-Musique.automount.
juin 05 22:17:53 complexe systemd[1]: home-adrien-Musique.automount: Got
automount request for /home/adrien/Musique, triggered by 1084
(gvfs-udisks2-vo)
juin 05 22:17:53 complexe systemd[1]: Mounting /home/adrien/Musique...
juin 05 22:17:53 complexe systemd[1]: Mounted /home/adrien/Musique.
juin 05 22:18:03 complexe systemd[1]: Unmounting /home/adrien/Musique...
juin 05 22:18:03 complexe systemd[1]: Unmounted /home/adrien/Musique.


After waiting for the unmount, I open another terminal, and try to 'll
/home/adrien/Musique'. The process is stalled and nothing shows up in
the log.

Starting the mount manually is working, so NFS seems out of the issue,
but I'm open for testing suggestions.

Adrien
--- System information. ---
Architecture: amd64
Kernel: Linux 4.5.0-2-amd64

Debian Release: stretch/sid
500 unstable ftp.fr.debian.org
1 experimental ftp.fr.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-==
libacl1 (>= 2.2.51-8) | 2.2.52-3
libapparmor1 (>= 2.9.0-3+exp2) | 2.10-4
libaudit1 (>= 1:2.2.1) | 1:2.5.2-1
libblkid1 (>= 2.19.1) | 2.28-5
libcap2 (>= 1:2.10) | 1:2.25-1
libcryptsetup4 (>= 2:1.4.3) | 2:1.7.0-2
libgpg-error0 (>= 1.14) | 1.22-2
libkmod2 (>= 5~) | 22-1.1
libmount1 (>= 2.26.2) | 2.28-5
libpam0g (>= 0.99.7.1) | 1.1.8-3.3
libseccomp2 (>= 2.1.0) | 2.3.1-2
libselinux1 (>= 2.1.9) | 2.5-3
libsystemd0 (= 230-2) | 230-2
util-linux (>= 2.27.1) | 2.28-5
mount (>= 2.26) | 2.28-5
adduser | 3.114
libcap2-bin | 1:2.25-1


Package Status (Version) | Installed
=-+-===
udev | 230-2


Recommends (Version) | Installed
=-+-===
libpam-systemd | 230-2
dbus | 1.10.8-1


Suggests (Version) | Installed
-+-===
systemd-ui |
systemd-container |



--- Output from package bug script ---

Bug#826511: Aarch64 QEMU Bug

[Mike]

Package: debian-installer
Version: 20160516+b1

Installing Debian using QEMU aarch64 (and looks like arm as well) requires
extra steps due to lack of initrd and kernel support for virtio devices.
While there is a workaround documented below, this seems like something
that should be added to the distro build to incorporate support directly.

https://gmplib.org/~tege/qemu.html

See block 14.

Best,

Mike

Bug#826510: systemctl: using "isolate" is too brutal and kills processes

[nsa spy]

Package: systemd
Version: 215-17+deb8u4
Severity: normal

dear maintainer,

systemctl: using "isolate" is too brutal and kills processes

in "systemctl" command subcommand "isolate" is doing something unwanted.
"isolate" kills processes and restarts them like networking (something in it) 
and TTYs which are unwanted functions. there is three possible suggestions to 
rectify these. a) making isolate less brutal, meaning it doesn't kill and 
restart 
processes which are going to be on in new runlevel. b) proposing new subcommand 
"approach" which switches runlevel without restarting processes which are going 
to be on in new runlevel. c) which is less recommended is using option 
"IgnoreOnIsolate=yes" on systemd settings to prevent restarts on key processes. 

this bug is reported in upstream already but i send it anyway if there is 
debian specific issues here.
https://github.com/systemd/systemd/issues/2607

earlier bug i reported.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801562



-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u4
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2+deb8u1
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1+deb8u1+b1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u4
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u4
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.20-0+deb8u1
ii  libpam-systemd  215-17+deb8u4

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information

Bug#823322: please build "systemd-sysusers" binary

[Michael Biebl]

Control: severity -1 wishlist

Am 05.06.2016 um 17:59 schrieb Dmitry Smirnov:
> Could we introduce raw "systemd-sysusers" binary ASAP to fix "rkt" please?
> 
> Other supporting files can be added later at your convenience.
> 
> I understand there were no objections so I'm raising severity of this bug in 
> hope that it could get attention rather sooner than later.

The size is a concern, and we mentioned this before.
This really is a wishlist bug, so bumping the severity is not justified.

Regards,
Michael


-- 
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#806494: [pkg-gnupg-maint] Bug#806494: gnupg: please make the build reproducible

[Werner Koch]

On Sun,  5 Jun 2016 13:07, intrig...@debian.org said:

> I gave it a try and AFAICT it won't be a small fix in the Makefile:
> the yat2m-stamp changes depend on defs.inc, defsincdate, mkdefsinc and
> friends. Then mkdefsinc.c imported from the v2.x tree does not compile

Right, I feared that there was some more complicated stuff. 

> So, maybe it's acceptable to carry a very simple Debian-only solution
> for GnuPG v1.x, until it is fully replaced by v2.x? The attached patch

I'd say, go for it.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
/* EFH in Erkrath: https://alt-hochdahl.de/haus */

Bug#826508: debuild: Does not recognize -J option to dpkg-buildpackage

[Josh Triplett]

Package: devscripts
Version: 2.16.5
Severity: normal
File: /usr/bin/debuild

$ debuild -b -Jauto
debuild: unknown dpkg-buildpackage/debuild option: -Jauto

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
BTS_SMTP_HELO=joshtriplett.org
BTS_SMTP_HOST=reportbug.debian.org:587
BTS_SUPPRESS_ACKS=yes
DEBUILD_DPKG_BUILDPACKAGE_OPTS="-us -uc"
DEBUILD_PREPEND_PATH=/usr/lib/ccache

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.7
ii  libc62.22-10
ii  perl 5.22.2-1
pn  python3:any  

Versions of packages devscripts recommends:
ii  apt 1.2.12
pn  at  
ii  curl7.47.0-1
ii  dctrl-tools 2.24-2
pn  debian-keyring  
ii  dput0.9.6.4
ii  equivs  2.0.9+nmu1
ii  fakeroot1.20.2-2
ii  file1:5.25-2
ii  gnupg   1.4.20-6
ii  gnupg2  2.1.11-7
pn  libdistro-info-perl 
ii  libencode-locale-perl   1.05-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.19-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  lintian 2.5.44
ii  man-db  2.7.5-1
ii  patch   2.7.5-1
ii  patchutils  0.3.4-1
pn  python3-debian  
pn  python3-magic   
ii  sensible-utils  0.0.9
ii  strace  4.12-3
ii  unzip   6.0-20
pn  wdiff   
ii  wget1.17.1-2
ii  xz-utils5.1.1alpha+20120614-2.1

Versions of packages devscripts suggests:
pn  bsd-mailx | mailx
ii  build-essential  12.2
pn  cvs-buildpackage 
pn  devscripts-el
pn  diffoscope   
pn  dose-extra   
ii  gnuplot5 [gnuplot]   5.0.3+dfsg2-2
ii  gpgv 1.4.20-6
pn  libauthen-sasl-perl  
ii  libfile-desktopentry-perl0.22-1
ii  libnet-smtp-ssl-perl 1.03-1
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
pn  mozilla-devscripts   
ii  mutt 1.6.0-1
ii  openssh-client [ssh-client]  1:7.2p2-5
pn  svn-buildpackage 
pn  w3m  

-- no debconf information

Bug#826509: xscreensaver: Please hide xscreensaver-properties.desktop in GNOME

[Laurent Bigonville]

Package: xscreensaver
Version: 5.34-2
Severity: normal

Hi,

I would be nice if xscreensaver-properties.desktop was not displayed by
default in GNOME (and probably others).

GNOME is providing its owned screensaver implementation and in a near
future we are planning to switch to wayland, that would mean that
xscreensaver will not work anyway.

Cheers,

Laurent Bigonville

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

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

Bug#826507: xindy: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: xindy
Version: 2.5.1.20160104-1
Severity: minor
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\indexentry{ <-- HERE (.+)--([8-9a-f][0-9a-f])\}\{1\}/ at 
./make-inp-rules.pl line 11.

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/xindy_2.5.1.20160104-1/
-- 
Niko Tyni   nt...@debian.org

Bug#826505: swissknife: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: swissknife
Version: 1.67-1.1
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^(\S{ <-- HERE 0,-1}/|-(?![>\-]))/ at 
/<>/blib/lib/SWISS/TextFunc.pm line 196,  chunk 25.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^(\S{ <-- HERE 0,-1}(?>/blib/lib/SWISS/TextFunc.pm line 
196,  chunk 25.

It looks like the offending file is installed in a binary package,
so this probably has runtime effects as well.

A full build log is available at
  http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/swissknife_1.67-1.1/
-- 
Niko Tyni   nt...@debian.org

Bug#677865: Alternative solution: flock is NFS-safe now

[Josh Triplett]

Rather than depending on or recommending libfile-fcntllock-perl, I think
dpkg-dev can now just unconditionally use flock.  According to "man 2
flock":
> In Linux kernels up to 2.6.11, flock() does not lock files over NFS (i.e., the
> scope of locks was limited to the local system). Instead, one could use
> fcntl(2) byte-range locking, which does work over NFS, given a sufficiently
> recent version of Linux and a server which supports locking. Since Linux
> 2.6.12, NFS clients support flock() locks by emulating them as byte-range 
> locks
> on the entire file. This means that fcntl(2) and flock() locks do interact 
> with
> one another over NFS.

So, on 2.6.12 and newer, flock on NFS will transparently uses fcntl locks.  No
supported version of Debian runs on a kernel older than 2.6.12.

Given that, I would suggest dropping the Recommends and the optional use
of File::FcntlLock entirely.

- Josh Triplett

Bug#826506: tiarra: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: tiarra
Version: 20100212+r39209-1
Severity: minor
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\%PRE{ <-- HERE (.+?)}ERP\%/ at 
main/Configuration/Preprocessor.pm line 168.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\%CODE{ <-- HERE (. *?)}EDOC\%/ at main/Configuration/Block.pm 
line 143.

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/tiarra_20100212+r39209-1/
-- 
Niko Tyni   nt...@debian.org

Bug#825240: ldapscripts: Please use SASLAUTH from /etc/nsdlcd.conf (sasl_mech)

[Alexander Gerasiov]

Hello James,

On Sun, 5 Jun 2016 10:49:54 -0400
James Valleroy  wrote:

> A patch to implement this change is available at
> https://github.com/gerasiov/ldapscripts/pull/1.
Oh, thanks, I'll use it. 

-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: g...@cs.msu.su  Homepage: http://gerasiov.net  Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1


pgpGvWRa5Yc6G.pgp
Description: OpenPGP digital signature

Bug#703237:

[SamuelOPH]

Looking at packages.debian.org i believe this was fixed some time ago,
please correct me if i'm wrong.

Could this be closed?

Samuel Henrique O. P. [samueloph]

Bug#806494: gnupg: please make the build reproducible

[intrigeri]

Control: tag -1 + patch

Hi,

Werner Koch wrote (04 Jun 2016 16:23:11 GMT) :
> On Sat,  4 Jun 2016 14:25, intrig...@debian.org said:

>> Werner, could this change be backported to GnuPG 1.x? (I do realize
>> that it's not merely about ya2tm.c, since e.g. doc/Makefile.am is
>> also affected.)

> If it is only to update yat2m and a small fix in the Makefile, a tested
> patch would be appreciated.

I gave it a try and AFAICT it won't be a small fix in the Makefile:
the yat2m-stamp changes depend on defs.inc, defsincdate, mkdefsinc and
friends. Then mkdefsinc.c imported from the v2.x tree does not compile
as-is. I gave up at that point, and I'm not convinced that it's worth
investing more time to fix this upstream in the v1.x tree, given that
the problem is solved in the v2.x one already.

So, maybe it's acceptable to carry a very simple Debian-only solution
for GnuPG v1.x, until it is fully replaced by v2.x? The attached patch
does that, by updating yat2m to the one included in 2.1.11, and
patching doc/Makefile.am to pass it --date $SOURCE_DATE_EPOCH
(initialized in debian/rules for now).

Cheers,
-- 
intrigeri

>From 16528b21bc7ebba9b8215dfe9882eb8e6fcbec85 Mon Sep 17 00:00:00 2001
From: intrigeri 
Date: Sat, 4 Jun 2016 18:03:03 +
Subject: [PATCH] Make man pages not embed a build-time dependent timestamp.

---
 ...03-yat2m-Update-from-the-gnupg-2.1.11-tag.patch | 90 ++
 ...DATE_EPOCH-if-set-when-building-with-yat2.patch | 20 +
 debian/patches/series  |  2 +
 debian/rules   |  3 +
 4 files changed, 115 insertions(+)
 create mode 100644 debian/patches/0003-yat2m-Update-from-the-gnupg-2.1.11-tag.patch
 create mode 100644 debian/patches/0004-Use-SOURCE_DATE_EPOCH-if-set-when-building-with-yat2.patch

diff --git a/debian/patches/0003-yat2m-Update-from-the-gnupg-2.1.11-tag.patch b/debian/patches/0003-yat2m-Update-from-the-gnupg-2.1.11-tag.patch
new file mode 100644
index 000..a544d1e
--- /dev/null
+++ b/debian/patches/0003-yat2m-Update-from-the-gnupg-2.1.11-tag.patch
@@ -0,0 +1,90 @@
+From: intrigeri 
+Date: Sat, 4 Jun 2016 17:59:48 +
+Subject: yat2m: Update from the gnupg-2.1.11 tag.
+
+---
+ doc/yat2m.c | 24 
+ 1 file changed, 20 insertions(+), 4 deletions(-)
+
+diff --git a/doc/yat2m.c b/doc/yat2m.c
+index 86c3c70..1634985 100644
+--- a/doc/yat2m.c
 b/doc/yat2m.c
+@@ -1,5 +1,5 @@
+ /* yat2m.c - Yet Another Texi 2 Man converter
+- *	Copyright (C) 2005, 2013 g10 Code GmbH
++ *	Copyright (C) 2005, 2013, 2015 g10 Code GmbH
+  *  Copyright (C) 2006, 2008, 2011 Free Software Foundation, Inc.
+  *
+  * This program is free software; you can redistribute it and/or modify
+@@ -120,6 +120,7 @@ static int quiet;
+ static int debug;
+ static const char *opt_source;
+ static const char *opt_release;
++static const char *opt_date;
+ static const char *opt_select;
+ static const char *opt_include;
+ static int opt_store;
+@@ -323,8 +324,12 @@ isodatestring (void)
+ {
+   static char buffer[11+5];
+   struct tm *tp;
+-  time_t atime = time (NULL);
++  time_t atime;
+ 
++  if (opt_date && *opt_date)
++atime = strtoul (opt_date, NULL, 10);
++  else
++atime = time (NULL);
+   if (atime < 0)
+ strcpy (buffer, "" "-??" "-??");
+   else
+@@ -679,6 +684,7 @@ proc_texi_cmd (FILE *fp, const char *command, const char *rest, size_t len,
+   } cmdtbl[] = {
+ { "command", 0, "\\fB", "\\fR" },
+ { "code",0, "\\fB", "\\fR" },
++{ "url", 0, "\\fB", "\\fR" },
+ { "sc",  0, "\\fB", "\\fR" },
+ { "var", 0, "\\fI", "\\fR" },
+ { "samp",0, "\\(aq", "\\(aq"  },
+@@ -1367,7 +1373,7 @@ parse_file (const char *fname, FILE *fp, char **section_name, int in_pause)
+ }
+ 
+   if (!incfp)
+-err ("can't open include file '%s':%s",
++err ("can't open include file '%s': %s",
+  incname, strerror (errno));
+   else
+ {
+@@ -1466,13 +1472,14 @@ main (int argc, char **argv)
+ "Extract man pages from a Texinfo source.\n\n"
+ "  --source NAMEuse NAME as source field\n"
+ "  --release STRING use STRING as the release field\n"
++"  --date EPOCH use EPOCH as publication date\n"
+ "  --store  write output using @manpage name\n"
+ "  --select NAMEonly output pages with @manpage NAME\n"
+ "  --verboseenable extra informational output\n"
+ "  --debug  enable additional debug output\n"
+ "  --help   display this help and exit\n"
+ "  -I DIR   also search in include DIR\n"
+-"  -D gpgonethe only useable define\n\n"
++"  -D gpgonethe only usable define\n\n"
+ "With no 

Bug#826504: sdf: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: sdf
Version: 2.001+1-3
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/{{ <-- HERE .:([^}]*)}}/ at 
/<>/sdf-2.001+1/debian/sdf/usr/share/perl5/sdf/tomif.pl line 4462.

It looks like the offending file is installed in a binary package,
so this probably has runtime effects as well.

A full build log is available at
  http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/sdf_2.001+1-3/
-- 
Niko Tyni   nt...@debian.org

Bug#826503: asis: FTBFS: gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.6: undefined symbol: __gnat_objlist_file_supported

[Emilio Pozuelo Monfort]

Source: asis
Version: 2015-1
Severity: serious

Your package failed to build in unstable on many architectures:

gprbuild -XLIBRARY_KIND=dynamic asis.gpr -XPROCESSORS=4 -R -v -eS \
  "-XADAFLAGS=-g -O2 -fstack-protector-strong -gnatfno -gnatwa -gnatVa" 
"-XLDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs" 
"-Xsoversion=2015"
gprbuild: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnatprj.so.6: 
undefined symbol: __gnat_objlist_file_supported
debian/rules:59: recipe for target 'build-asis-dynamic' failed
make[1]: *** [build-asis-dynamic] Error 127
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:38: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Logs at https://buildd.debian.org/status/package.php?p=asis

Emilio

Bug#826501: haskell-devscripts: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: haskell-devscripts
Version: 0.10.2.3
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building the pkg-haskell-tools package triggers deprecation warnings
with Perl 5.24 (currently in experimental), and probably with Perl 5.22
(current sid) too.

  dh_haskell_blurbs "ghc" -ppkg-haskell-tools
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\${ <-- HERE Newline}$/ at -e line 1.

It looks like this comes from line 61 or so in dh_haskell_blurbs:
perl -pe 's/\n$/\${Newline}/'|   # prepare for dpkg-gencontrol
perl -pe 's/\${Newline}$//'  # but not final lineline

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/pkg-haskell-tools_0.10.2/
-- 
Niko Tyni   nt...@debian.org

Bug#826502: quilt: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: quilt
Version: 0.63-3
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  perl -pe 'if (/\\sh{.*}/) {s:\\sh{(.*)}:$1:}'\
   < doc/tmp/main.html > doc/quilt.html
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\sh{ <-- HERE .*}/ at -e line 1.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\sh{ <-- HERE (.*)}/ at -e line 1.
  [...]
  make[2]: Entering directory '/<>'
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/%{ <-- HERE (\w+)}/ at ./run line 114.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/%{ <-- HERE \?}/ at ./run line 290.
  [...]

A full build log is available at
  http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/quilt_0.63-3/
-- 
Niko Tyni   nt...@debian.org

Bug#826360: dietlibc: Unit tests should be built with SSP enabled

[Christian Seiler]

Control: tags -1 + pending

On 06/05/2016 12:38 AM, Christian Seiler wrote:
> Submitting this as a bug so I don't forget about it: in order to
> prevent things like #826359 from happening in the future, the unit
> tests should be built with SSP (-fstack-protector-strong) by
> default.

This is now in git. (Although it wouldn't have caught #826359 after
all, in retrospect, but still useful to have.)

Regards,
Christian



signature.asc
Description: OpenPGP digital signature

Bug#826359: dietlibc: x32: SSP triggered by autotools test, causes FTBFS on rdeps

[Christian Seiler]

Control: tags -1 + pending

On 06/05/2016 12:33 AM, Christian Seiler wrote:
> Submitting this as a bug so I don't forget about it: after uploading
> dietlibc to sid today, the buildds started to build rdeps on x32.
> But the build of tiny-initramfs failed on x32 due to an autoconf test
> causing the SSP to be triggered:
> 
> https://buildd.debian.org/status/fetch.php?pkg=tiny-initramfs=x32=0.1-2=1465065787
> 
> There is probably something wrong with some code of dietlibc-dev on
> x32, and the SSP catches that mistake.

struct stat didn't have the right size, causing fopen() to trigger the
SSP (sic!), fixed now in git, also added a test for fopen() to catch
this kind of stuff earlier.

Regards,
Christian



signature.asc
Description: OpenPGP digital signature

Bug#826500: perlbrew: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: perlbrew
Version: 0.75-1
Severity: minor
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/ \$fatpacked{ <-- HERE "App/perlbrew.pm"} / at t/http.t line 
37.

A full build log is available at
  http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/perlbrew_0.75-1/
-- 
Niko Tyni   nt...@debian.org

Bug#826499: pangzero: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: pangzero
Version: 1.4.1+git20121103-1
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/Games::PangZero::Players\[0]->{ <-- HERE keys}->\[0] = (.+?)$/ 
at /<>/pangzero-1.4.1+git20121103/blib/lib/Games/PangZero/Config.pm 
line 107.

The offending file is installed in a binary package, so this probably
has runtime effects as well.

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/pangzero_1.4.1+git20121103-1/
-- 
Niko Tyni   nt...@debian.org

Bug#826498: automake1.11: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: automake1.11
Version: 1:1.11.6-3
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building the muttprint package triggers deprecation warnings with Perl
5.24 (currently in experimental), and probably with Perl 5.22 (current
sid) too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake-1.11 line 
4159.

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

Bug#826497: metamonger: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: metamonger
Version: 0.20150503-1
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/"001":{ <-- HERE "atime":1337,"mode":"0775","mtime":42}/ at 
t/009-save-noact.t line 16.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/"004":{ <-- HERE \S+,"mode":"0666",\S+}/ at t/009-save-noact.t 
line 17.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/"metadata":{ <-- HERE / at ./metamonger line 436.

It looks like './metamonger' is also installed in a binary package, so
this probably has runtime effects too.

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/metamonger_0.20150503-1/
-- 
Niko Tyni   nt...@debian.org

Bug#818897: Exim4 change CWD string to /

[Серж ИвановЪ]

On Thu, 21 Apr 2016 19:30:15 +0200 Andreas Metzler  wrote:
> On 2016-04-20 Roman Bulakh  wrote:
> > On 2016-03-27 Andreas Metzler  wrote:
> >> On 2016-03-21 Roman Bulakh  wrote:
> >>> Package: exim4
> >>> Version: 4.80-7+deb7u2
>
> >>> After updates exim to version 4.80-7+deb7u2 exim.c change CWD dir to /
> >>> on startup.
> [...]
> >> /usr/share/doc/exim4-base/changelog.Debian.gz
> >> exim4 (4.80-7+deb7u2) wheezy-security; urgency=high
> >>   * 88_CVE-2016-1531.diff:
> >> [...]
> >> + Exim changes it's working directory to / right after startup.
> >> [...]
> >>   * 89_01_only_warn_on_nonempty_environment.diff,
> >> 89_02_Store-the-initial-working-directory.diff: Upstream followups
on the
> >> CVE fix (Thanks, Heiko Schlittermann!):
> >> [...]
> >> + Store the initial working directory and make it available in the
new
> >>   expansion variable $initial_cwd.
>
>
> >> Sadly I made an error with the latter patch, but it is going to be
fixed
> >> in the next point release. See , you
can
> >> already grab 4.80-7+deb7u3 directly from the mirrors.
> >> http://ftp.at.debian.org/debian/pool/main/e/exim4/
> [...]
>
> > Problem is not fixed. I have exim 4.80-7+deb7u3 but cwd still "cwd=/"
>
> Please re-read my comment. I did not say exim stopped changing to / but
> "Store the initial working directory and make it available in the new
> expansion variable $initial_cwd.".
>
> You'll need to change your config.
>
> cu Andreas
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
>
>

Using this code "warn log_message = $initial_cwd" in acl_not_smtp yields
"2016-06-05 13:16:51 1b9V6x-00059W-3B U=root Warning: /"
as apposed to correct behavior,

can you clarify needed config changes, what are we missing here?

Bug#826496: libxml-twig-perl: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: libxml-twig-perl
Version: 1:3.48-1
Severity: minor
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=105702
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in 
m/(\$[a-z_]+(?:\[\d\])?|\$t(?:wig)?->root|\$t(?:wig)?->twig_current|\$t(?:wig)?->{
 <-- HERE 
'?twig_root'?}|\$t(?:wig)?->{'?twig_current'?})->set_gi\(\s*(PCDATA|CDATA|PI|COMMENT|ENT)\s*\)/
 at speedup line 41, <> line 1.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in 
m/(\$[a-z_]+(?:\[\d\])?|\$t(?:wig)?->root|\$t(?:wig)?->twig_current|\$t(?:wig)?->{
 <-- HERE '?twig_root'?}|\$t(?:wig)?->{'?twig_current'?})->del_(twig_current)/ 
at speedup line 43, <> line 1.
  [...]

A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/libxml-twig-perl_3.48-1/
-- 
Niko Tyni   nt...@debian.org

Bug#826495: libwww-search-perl: Unescaped left brace in regex is deprecated

[Niko Tyni]

Package: libwww-search-perl
Version: 2.51.50-1
Severity: minor
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=114735
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers deprecation warnings with Perl 5.24
(currently in experimental), and probably with Perl 5.22 (current sid)
too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(pm_to_blib\(){{ <-- HERE \@ARGV}}/ at Makefile.PL line 120.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(from_to\s+=>\s+){{ <-- HERE \@ARGV}}/ at Makefile.PL line 124.
  [...]
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(pm_to_blib\(){{ <-- HERE \@ARGV}}/ at Makefile.PL line 56.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(from_to\s+=>\s+){{ <-- HERE \@ARGV}}/ at Makefile.PL line 60.


A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/libwww-search-perl_2.51.50-1/
-- 
Niko Tyni   nt...@debian.org