Bug#823577: systemd: Systemd-215 does not setup per-session cgroups for each resource type

[Nik Johnson]

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

Dear Maintainer,

Systemd-215, the debian stable release, does not setup per-session cgroups for 
each resource type.
It's well documented with a Google search that lxc unprivileged containers are 
not working on Debian
Jessie. I found Ubuntu bug report 1346734, which documented similar issues, and 
I have backported the
patches. The patches work for both kernel 3.16 and 4.5 (current backport).


-- Package-specific info:

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

Kernel: Linux 4.4.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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#823576: RFS: nfft/3.3.1-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "nfft"

* Package name: nfft
  Version : 3.3.1-1
  Upstream Author : Prof. Dr. Daniel Potts 
* URL :http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
  Section : science

It builds those binary packages:

  libnfft3-2 - library for computing non-uniform Fourier transforms
  libnfft3-dbg - debugging symbols for the NFFT library
  libnfft3-dev - development files for the NFFT library
  libnfft3-doc - documentation for the NFFT library
  libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
  libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
  libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.1-1.dsc


Changes since the last upload:

  * d/gbp.conf: switch packaging branch to debian/master (DEP-14).
  * d/gbp.conf: disable patch numbering with gbp-pq.
  * Update patch queue:
- Drop Use-configured-libdir-in-pkgconfig-file.patch, applied upstream.
- Drop Disable-slow-tests.patch, fixed upstream.
  * Simplify install and lintian-overrides regexes.
  * d/rules: fix buggy clean target.
  * d/rules: detect long-double availability with pkg-config.
  * d/rules: enable testsuite for single and long-double precisions.
  * d/rules: s/COMMON_BUILD_OPTIONS/BUILD_OPTIONS.
  * d/rules: simplify call to doc target.
  * d/rules: comment out DH_VERBOSE.
  * d/control: add mips64el to list of architectures supporting 
long-double.

  * d/control: fix formatting of long description.
  * Bump standards version to 3.9.8, no changes required.

Regards,
Ghislain Vaillant

Bug#823575: RFS: asl/0.1.6-2 [RC]

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "asl"

* Package name: asl
  Version : 0.1.6-2
  Upstream Author : Avtech Scientific 
* URL : http://asl.org.il
* License : AGPL-3
  Section : science

It builds those binary packages:

  libasl-dev - multiphysics simulation software (development files)
  libasl-doc - multiphysics simulation software (documentation)
  libasl0- multiphysics simulation software (shared libraries)

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


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

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

  dget -x https://mentors.debian.net/debian/pool/main/a/asl/asl_0.1.6-2.dsc

Changes since the last upload:

  * d/gbp.conf: use recommended DEP-14 settings:
- Change packaging branch to debian/master.
- Use upstream tag format.
  * Drop -dbg package in favor of autogenerated -dbgsym.
  * Improve generation of -doc package:
- Move doxygen to Build-Depends-Indep.
- Use arch-indep targets to configure and install.
- Install examples.
  * d/rules: do not set CMAKE_BUILD_TYPE explicitly.
  * d/rules: build examples and testsuite conditionally on nocheck.
  * d/rules: add missing maintainer flags.
  * Run cme fix on d/control:
- Fix formatting, wrap and sort.
- Drop versioned dependency on libvtk6-dev.
- Use secure VCS-Git URI.
- Bump standards version to 3.9.8, no changes required.
  * Cherry-pick upstream fix for FTBFS error.
Thanks to Martin Michlmayr (Closes: 822469)

Regards,
Ghislain Vaillant

Bug#823574: knot: fails to upgrade from 'jessie': Error: syntax error (file '/var/backups/knot/20160503-122201/knot.conf', line 6)

[Andreas Beckmann]

Package: knot
Version: 2.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up knot (2.2.0-2) ...
  Installing new version of config file /etc/init.d/knot ...
  Installing new version of config file /etc/knot/knot.conf ...
  Backup config file /etc/knot/knot.conf to /var/backups/knot/20160503-122201.
  Converting config file /etc/knot/knot.conf to new format.
  Error: syntax error (file '/var/backups/knot/20160503-122201/knot.conf', line 
6)
  dpkg: error processing package knot (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


knot_2.2.0-2.log.gz
Description: application/gzip

Bug#823521: RFS: irstlm/6.00.05-1 -- IRST Language Modeling Toolkit

[Ghislain Vaillant]

On 06/05/16 02:48, Giulio Paci wrote:

On 05/05/2016 19:45, Ghislain Vaillant wrote:

On 05/05/16 17:16, Giulio Paci wrote:

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: rbal...@debian.org

Dear Balint,

I am looking for a sponsor for an updated version of my package "irstlm"

   * Package name: irstlm
 Version : 6.00.05-1
 Upstream Author : Marcello Federico 
   * URL : https://github.com/irstlm-team/irstlm/
   * License : LGPL-2.1
 Programming Lang: C++, Perl, Bash
 Description : IRST Language Modeling Toolkit
 Section : misc

This package includes latest upstream releases and several package updates.

You can found the sources for the package and additional information at:

https://anonscm.debian.org/cgit/collab-maint/irstlm.git/

A review of the package is more than welcome.

Regards,
 Giulio Paci



Hi Giulio,

You might be interested to move this package to co-maintenance under the
Debian Science Team [1] and integrate it to one of the tasks [2] in the
future (perhaps the linguistics task [3]?).


You are right, and it is my intention to do so in future.
The only thing stopping me is that at the moment the sponsorhip for this 
package is working and I have very scarce time, so that I had not yet reread 
the rules of the team
(last time I read them was a few years ago).


It is not that much overhead actually. You just need to join the team
on alioth, which will grant you access to the team's git repositories.
Then, you can move the packaging repository over, change the Maintainer 
field to "Debian Science Maintainers 
maintain...@lists.alioth.debian.org>" and move yourself to the
Uploaders field.

That's it.


Regarding the tasks, I think "linguistics" is fine. In addition, what about "machine 
learning" and/or "statistics"?

How can I add them to the tasks? I have found this repository 
https://anonscm.debian.org/cgit/blends/projects/science.git but no clear 
instructions.


This process is actually independent of having the package maintained
under the DST or not. However, you need to join the team to be able to
modify the task files. I can add the package to linguistics, machine
learning and statistics.

You might want to add some upstream metadata [1], so our sentinels can
display additional information about the software such as screenshots,
citations...

[1] https://wiki.debian.org/UpstreamMetadata

Thanks for working on this package.

Cheers,
Ghis

Bug#823573: python-z3: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: python-z3
Version: 4.4.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  testing -> sid

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

0m46.0s ERROR: WARN: Inadequate results from running adequate!
  python-z3:amd64: missing-copyright-file /usr/share/doc/python-z3/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/python-z3/copyright
  # ls -lad /usr/share/doc/python-z3
  drwxr-xr-x 2 root root 40 Apr 29 10:31 /usr/share/doc/python-z3
  # ls -la /usr/share/doc/python-z3/
  total 0
  drwxr-xr-x   2 root root   40 Apr 29 10:31 .
  drwxr-xr-x 112 root root 2400 Apr 29 10:31 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


python-z3_4.4.0-5.log.gz
Description: application/gzip

Bug#823572: sympow: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: sympow
Version: 1.023-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> sid

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

0m53.0s ERROR: WARN: Inadequate results from running adequate!
  sympow: missing-copyright-file /usr/share/doc/sympow/copyright
  
  MISSING COPYRIGHT FILE: /usr/share/doc/sympow/copyright
  # ls -lad /usr/share/doc/sympow
  drwxr-xr-x 2 root root 40 May  3 11:18 /usr/share/doc/sympow
  # ls -la /usr/share/doc/sympow/
  total 0
  drwxr-xr-x   2 root root   40 May  3 11:18 .
  drwxr-xr-x 108 root root 2280 May  3 11:18 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


sympow_1.023-6.log.gz
Description: application/gzip

Bug#823571: influxdb-dev: unhandled symlink to directory conversion: /usr/share/gocode/src/github.com/influxdata/influxdb

[Andreas Beckmann]

Package: influxdb-dev
Version: 0.12.0+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  testing -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m11.3s INFO: dirname part contains a symlink:
  /usr/share/gocode/src/github.com/influxdata/influxdb/client 
(golang-github-influxdb-influxdb-dev) != 
/usr/share/gocode/src/github.com/influxdb/influxdb/client (?)
/usr/share/gocode/src/github.com/influxdata/influxdb -> ../influxdb/influxdb
  /usr/share/gocode/src/github.com/influxdata/influxdb/client/example_test.go 
(golang-github-influxdb-influxdb-dev) != 
/usr/share/gocode/src/github.com/influxdb/influxdb/client/example_test.go (?)
/usr/share/gocode/src/github.com/influxdata/influxdb -> ../influxdb/influxdb
  /usr/share/gocode/src/github.com/influxdata/influxdb/client/influxdb.go 
(golang-github-influxdb-influxdb-dev) != 
/usr/share/gocode/src/github.com/influxdb/influxdb/client/influxdb.go (?)
/usr/share/gocode/src/github.com/influxdata/influxdb -> ../influxdb/influxdb
  /usr/share/gocode/src/github.com/influxdata/influxdb/client/influxdb_test.go 
(golang-github-influxdb-influxdb-dev) != 
/usr/share/gocode/src/github.com/influxdb/influxdb/client/influxdb_test.go (?)
/usr/share/gocode/src/github.com/influxdata/influxdb -> ../influxdb/influxdb
[...]
  /usr/share/gocode/src/github.com/influxdata/influxdb/uuid 
(golang-github-influxdb-influxdb-dev) != 
/usr/share/gocode/src/github.com/influxdb/influxdb/uuid (?)
/usr/share/gocode/src/github.com/influxdata/influxdb -> ../influxdb/influxdb
  /usr/share/gocode/src/github.com/influxdata/influxdb/uuid/uuid.go 
(golang-github-influxdb-influxdb-dev) != 
/usr/share/gocode/src/github.com/influxdb/influxdb/uuid/uuid.go (?)
/usr/share/gocode/src/github.com/influxdata/influxdb -> ../influxdb/influxdb


cheers,

Andreas


influxdb-dev_0.12.0+dfsg1-2.log.gz
Description: application/gzip

Bug#823515: php7.0-cli: missing Depends: php-common (>= 1:37)

[Andreas Beckmann]

Followup-For: Bug #823515

Forgot to attach the piuparts logfile (this is from before 7.0.6-1
migrated to testing yesterday, but the problem is still exactly the same).


Andreas


php7.0-cli_7.0.6-1.log.gz
Description: application/gzip

Bug#823527: tmux: Terminal bell not shown in status line

[Marcel Lippmann]

Hi,

On 06 May 2016, 12:10am +0200, Romain Francoise wrote:
> Can you share your config files?

..tmux.conf:

# set terminal
set -g default-terminal tmux-256color
set -g default-command "$SHELL"
set -g update-environment ""


# windows and panes start index 1
setw -g base-index 1
setw -g pane-base-index 1
set -g renumber-windows on


# set window history limit
set -g history-limit 10


# status line
set -g status on
set -g status-left "#[fg=green][#S] "
set -g status-right ""

setw -g monitor-activity on
set -g visual-activity off
set -g visual-bell off


# mouse settings
set -g mouse on

bind -T root WheelUpPane if-shell -F -t = "#{alternate_on}" "send-keys -M" 
"select-pane -t =; copy-mode -e; send-keys -M"
bind -T root WheelDownPane if-shell -F -t = "#{alternate_on}" "send-keys -M" 
"select-pane -t =; send-keys -M"
bind -T root -n MouseDown2Pane paste-buffer

bind -t vi-copy WheelUpPane halfpage-up
bind -t vi-copy WheelDownPane halfpage-down


# key bindings
unbind C-b
set -g prefix C-a
bind a send-prefix

set -g mode-keys vi

bind h select-pane -L
bind j select-pane -D
bind k select-pane -U
bind l select-pane -R

bind v paste-buffer

bind '"' split-window -c "#{pane_current_path}"
bind '%' split-window -h -c "#{pane_current_path}"

bind '<' swap-window -t -1
bind '>' swap-window -t +1

bind -n C-S-Left previous-window
bind -n C-S-Right next-window


# colours
set -g pane-active-border-bg default

set -g status-bg black
set -g status-fg cyan

setw -g window-status-current-bg default
setw -g window-status-current-fg white

set -g message-fg blue
set -g message-bg white

--8<-


I don’t think that it has anything to do with the config, since it
works with the same config file on Debian stable.  Also, I can
reproduce the behaviour with an empty config file.

Best,

Marcel

Bug#823515: php7.0-cli: missing Depends: php-common (>= 1:37)

[Andreas Beckmann]

Followup-For: Bug #823515

Hi,

during a test with piuparts I noticed some strange behavior w.r.t. the
/usr/bin/phar alternative. After an upgrade from stretch to sid (which
both have the same version of php7.0-cli), the /usr/bin/phar alternative
is not cleaned up. This is not reproducible by just installing the
package in either sid or stretch. An indication from the logfile is
php-common diverting /usr/bin/phar on the upgrade from stretch to sid
*after* php7.0-cli had set up an alternative there in stretch already.
This most likely seems to clash in some way, so there should be a
Depends on php-common (>= 1:37) to ensure the diversion is in place
before the alternative is set up.


Andreas

Bug#823570: apt-cacher-ng: upgrade breaks Remap- repositories with hyphen(s) in name

[Daniel Richard G.]

Package: apt-cacher-ng
Version: 0.9.1-1
Severity: important

I upgraded apt-cacher-ng from 0.8.0-1 to 0.9.1-1, and got this:

# /etc/init.d/apt-cacher-ng start
 * Starting apt-cacher-ng apt-cacher-ng
Warning, unknown configuration directive: Remap-debian-archive
Error reading main options, terminating.

I make use of numerous Remap- directives with repository names
containing hyphens, e.g.

Remap-debian-archive: /debian-archive ; http://archive.debian.org/debian
Remap-debian-archive-security: /debian-archive-security ; 
http://archive.debian.org/debian-security
Remap-debian-ports: /debian-ports ; http://ftp.debian-ports.org/debian
Remap-debian-security: /debian-security ; http://security.debian.org

These were working previously, so this is a regression.

I worked around the issue by changing the strrchr() call in GetPropPtr()
(source/acfg.cc:340) to strchr().

Bug#823534: apt-get remove is unhelpful for virtual packages

[Carsten Hey]

Hi,

* Richard Stallman [2016-05-05 14:48 -0400]:
> Package: apt
> Version: 1.0.1ubuntu2.13+7.0trisquel3
>
> I tried to remove a package which is virtual, specifically nethack.
> apt-get told me it could not do this, but said nothing about
> what to do.

"apt-cache showpkg mail-transport-agent" lists "Reverse Provides:",
but it does not show which m-t-a is installed.  Maybe this is worth
an additional bug report?


> It would surely be easy to make it handle a virtual package by
> seeing which real package provides it, and offering to delete
> that one.

I see three possible ways to address this issue:

 1. Offering to delete the real package, as rms wrote.  apt-get
would then, for instance, ask "... Would you like to remove
postfix instead? [yN]".

This might or might not be useful for /usr/bin/apt, but I hope
apt-get will stay as non-interactive as it has always been.

 2. Provide a more useful output.  A good example is the output of
apt-get _install_ virtual-package on jessie:

# apt-get install mail-transport-agent
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package mail-transport-agent is a virtual package provided by:
  opensmtpd 5.7.3p2-1
  ...
  exim4-daemon-heavy 4.84.2-1
You should explicitly select one to install.

E: Package 'mail-transport-agent' has no installation candidate

 3. "Do What I Mean" (DWIM) - on IRC, it has been suggested to remove
the real package if there is only one provider.

Assume that the packages foo and bar are installed, that foo is not
available via an apt repository anymore, and that bar provides foo.

"apt-get remove foo" would then remove foo the first time
it is run and it would remove bar the second time it is run.
I wouldn't consider this to be an intuitive behaviour.

At least I try to remove packages I removed previously from time
to time (although I know that I already removed them).  And I don't
think I'm the only one who occasionally runs "apt-get install pkg1
pkg2- pkg3-", and then presses the up key and appends additional
package names in order to save some key presses.


> Alas. I can't reproduce this now, or show you the output,
> because I no longer have those packages installed.

On stable, the according output is:

  # apt-get remove mail-transport-agent
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Virtual packages like 'mail-transport-agent' can't be removed
  The following packages were automatically installed ...

I noticed that the 'Virtual packages ...' line vanishes if stdout is
piped through, e.g., cat and wonder if this is done deliberately.


Regards
Carsten

Bug#823569: sysvinit-utils: switch sysvinit-utils/util-linux Breaks/Depends around

[Andreas Henriksson]

Package: sysvinit-utils
Version: 2.88dsf-59.3
Severity: normal

Dear Maintainer,

I'm considering a NMU to switch around the inverted Breaks/Depends
relationship between sysvinit-utils and util-linux (which is/was
a bi-product of the previous but no longer existing dependency
cycle via initscripts, which util-linux no longer depends on).

Doing this means we need a coordinated upload of sysvinit and util-linux.
I suspect since I've seen no actual activity from the prospective
sysvinit adopters that I'll have to NMU sysvinit myself to get this
done. Please speak up ASAP if there's anyone willing to handle this
upload on the sysvinit side or if there's anyone who sees any problems
with the attached patches.
I will proceed very soon, so please speek up if it's just to give you
more time and to give me a sign someone out there is listening.

(The matching util-linux patches has also been included for anyone
interested. Put them in a tarball to keep them separated and avoid
mixing up with actual sysvinit patches.)

Regards,
Andreas Henriksson

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

Kernel: Linux 4.3.0-1-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 sysvinit-utils depends on:
ii  init-system-helpers  1.31
ii  libc62.22-7
ii  startpar 0.59-3

sysvinit-utils recommends no packages.

Versions of packages sysvinit-utils suggests:
pn  bootlogd  
pn  sash  

-- no debconf information
>From 0864dd5eafc8edca3e044841dc5976e16d78ee1f Mon Sep 17 00:00:00 2001
From: Andreas Henriksson 
Date: Fri, 6 May 2016 05:48:00 +0200
Subject: [PATCH 1/3] sysvinit-utils: move util-linux back to Depends (instead
 of Breaks)

- that's where it belonged and can be put now that the cyclic-dep
  (via initscripts pkg) workaround is no longer needed.
- also bump util-linux version to the one with the matching change.

Closes: #-1
Git-Dch: Full
---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 530a23a..f9efc03 100644
--- a/debian/control
+++ b/debian/control
@@ -59,9 +59,9 @@ Conflicts: last, sysvconfig, chkconfig (<< 11.0-79.1-2), startpar (<< 0.58-2)
 Replaces: last, sysvinit (<= 2.86.ds1-65)
 Depends: ${shlibs:Depends}, ${misc:Depends}, init-system-helpers (>= 1.25~)
  , startpar
-Breaks: upstart (<< 1.5-0ubuntu5), systemd (<< 215)
 # sulogin, last, lastb and mesg was moved to the util-linux package
- , util-linux (<< 2.26.2-3)
+ , util-linux (>> 2.28-2~)
+Breaks: upstart (<< 1.5-0ubuntu5), systemd (<< 215)
 Suggests: bootlogd, sash
 Description: System-V-like utilities
  This package contains the important System-V-like utilities.
-- 
2.8.1

>From 55201541b3d534c165987436340ea15dbe7ca7ed Mon Sep 17 00:00:00 2001
From: Andreas Henriksson 
Date: Fri, 6 May 2016 06:07:53 +0200
Subject: [PATCH 2/3] Add a basic debian/gbp.conf with debian/upstream branch
 names

---
 debian/gbp.conf | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 debian/gbp.conf

diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..60ce09b
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,3 @@
+[DEFAULT]
+debian-branch = master
+upstream-branch = upstream/2.88dsf
-- 
2.8.1

>From 1420326055960274cd927facb9b3b1409dfcec07 Mon Sep 17 00:00:00 2001
From: Andreas Henriksson 
Date: Fri, 6 May 2016 05:55:55 +0200
Subject: [PATCH 3/3] Update debian/changelog

---
 debian/changelog | 17 +
 1 file changed, 17 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 2492ab2..13d98c2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+sysvinit (2.88dsf-59.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Petter Reinholdtsen ]
+  * Fix typo in init-d-script(5) reported by Eric S. Raymond.
+
+  [ Andreas Henriksson ]
+  * sysvinit-utils: move util-linux back to Depends (instead of Breaks)
+- that's where it belonged and can be put now that the cyclic-dep
+  (via initscripts pkg) workaround is no longer needed.
+- also bump util-linux version to the one with the matching change.
+Closes: #-1
+  * Add a basic debian/gbp.conf with debian/upstream branch names
+
+ -- Andreas Henriksson   Fri, 06 May 2016 05:55:46 +0200
+
 sysvinit (2.88dsf-59.3) unstable; urgency=medium
 
   * Non-maintainer upload.
-- 
2.8.1



ul-patches.tar
Description: Unix tar archive

Bug#822648: Needs DEP-11 support

[Daniel Richard G.]

Hi Mark,

On Wed, 2016 Apr 27 13:03+0100, Mark Hindley wrote:
> 
> Thanks. I think this is a duplicate of #821159. I gave an updated
> index_files_regexp config that the OP suggested meybe the fix
> (although I wasn't completely sure of his response). Could you
> try that.
>
> I notice that your apt-get trace has some additional SHA1 filenames,
> that I wasn't expecting, so the #821159 may be incomplete.

I tested your proposed fix to lib/apt-cacher.pl in that bug report. Two
changes are needed:

  1. SHA files, and

  2. icons tarballs can be .xz-compressed.

So with

  Components-%VALID_ARCHS%\.yml\.(?:x|g)z
  icons-(64|128)x\g{-1}\.tar\.(?:x|g)z
  [0-9a-f]{64}

the Ubuntu Xenial system updates cleanly.

(Might be good to match the path prefix of the SHA files, since the
basename pattern is a wee bit open-ended...)

Bug#823482: Option author-is-committer = False apparently ignored.

[Charles Plessy]

Le Thu, May 05, 2016 at 01:57:03PM +0200, Guido Günther a écrit :
> On Thu, May 05, 2016 at 04:19:44PM +0900, Charles Plessy wrote:
> > 
> > [import-dsc]
> > author-is-committer = False
> > author-date-is-committer-date = False
> > 
> > Is that a bug or did I misunderstand what `author-is-committer` is actually
> > doing ?
> 
> I think I know what you're talking about but could you attach the output
> of
> 
>git show --pretty=fuller
> 
> of the import and additionally how you want it to look like? The current
> format is not ment to override the author but only the committer so we
> might need an extra option for that.

Thanks Guido for the prompt answer.

Here is a simple test example.

I created an empty repository, and added a gbp configuration
file that turns off `author-is-committer`:

$ grep author-is-committer .git/gbp.conf 
author-is-committer = False

Then, I imported a package made by another developer
(r-cran-doparallel_1.0.10-1.dsc to be precise).

The command `git show --pretty=fuller` shows that he is
listed as "Author" of the commit.

commit 8ba676ef6f78fd7996150bffc68314efb1bd1ad6
Author: Andreas Tille 
AuthorDate: Tue May 3 22:33:20 2016 +0200
Commit: Charles Plessy 
CommitDate: Fri May 6 12:37:27 2016 +0900

Imported Debian patch 1.0.10-1

In a different situation (another package, another maintainer), I would like to
be listed as "Author" of the "Imported Debian patch" commit in order to make it
clear that the repository is not maintained by the official package maintainer.

Thanks for your help !

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Bug#823550: Acknowledgement (dune-functions: FTBFS with glibc 2.23)

[Logan Rosen]

Sorry, this is actually probably caused by GCC 6.

On Thu, May 5, 2016 at 5:36 PM, Debian Bug Tracking System
 wrote:
> Thank you for filing a new Bug report with Debian.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Science Maintainers 
> 
>
> If you wish to submit further information on this problem, please
> send it to 823...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 823550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823550
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#823568: krb5-auth-dialog: Don't autostart for non-Kerberos users

[Daniel Richard G.]

Package: krb5-auth-dialog
Version: 3.12.0-2
Severity: wishlist

When krb5-auth-dialog is installed, it drops a .desktop file into
/etc/xdg/autostart/ so that it starts up as part of the normal desktop
session, without requiring further intervention. I am assembling a
system that will mainly handle users authenticated via Kerberos, so
this is great.

However, there will also be some local-only users (via normal Unix
auth), and for them, the "Network credentials expired" notification
will be confusing and unhelpful. I'd like for the program not to
autostart for them.

(If a local-only user somehow wants to authenticate to some Kerberos
principal graphically, they can always start up the program via the
application menu, of course.)

This minor change to the .desktop file gets me the desired effect...

--- /etc/xdg/autostart/krb5-auth-dialog.desktop.orig
+++ /etc/xdg/autostart/krb5-auth-dialog.desktop
@@ -1,7 +1,7 @@
 [Desktop Entry]
 Name=Kerberos Authentication
 Comment=Kerberos Network Authentication Dialog
-Exec=krb5-auth-dialog
+Exec=sh -c 'test -z "$KRB5CCNAME" || exec krb5-auth-dialog'
 Terminal=false
 Type=Application
 Icon=krb-valid-ticket

...but there may be a better way of doing it. I'd like to request
this behavior.

Bug#823521: RFS: irstlm/6.00.05-1 -- IRST Language Modeling Toolkit

[Giulio Paci]

On 05/05/2016 19:45, Ghislain Vaillant wrote:
> On 05/05/16 17:16, Giulio Paci wrote:
>> Package: sponsorship-requests
>> Severity: normal
>> X-Debbugs-CC: rbal...@debian.org
>>
>> Dear Balint,
>>
>> I am looking for a sponsor for an updated version of my package "irstlm"
>>
>>   * Package name: irstlm
>> Version : 6.00.05-1
>> Upstream Author : Marcello Federico 
>>   * URL : https://github.com/irstlm-team/irstlm/
>>   * License : LGPL-2.1
>> Programming Lang: C++, Perl, Bash
>> Description : IRST Language Modeling Toolkit
>> Section : misc
>>
>> This package includes latest upstream releases and several package updates.
>>
>> You can found the sources for the package and additional information at:
>>
>>https://anonscm.debian.org/cgit/collab-maint/irstlm.git/
>>
>> A review of the package is more than welcome.
>>
>> Regards,
>> Giulio Paci
>>
> 
> Hi Giulio,
> 
> You might be interested to move this package to co-maintenance under the
> Debian Science Team [1] and integrate it to one of the tasks [2] in the
> future (perhaps the linguistics task [3]?).

You are right, and it is my intention to do so in future.
The only thing stopping me is that at the moment the sponsorhip for this 
package is working and I have very scarce time, so that I had not yet reread 
the rules of the team
(last time I read them was a few years ago).

Regarding the tasks, I think "linguistics" is fine. In addition, what about 
"machine learning" and/or "statistics"?

How can I add them to the tasks? I have found this repository 
https://anonscm.debian.org/cgit/blends/projects/science.git but no clear 
instructions.

> A few remarks:
> d/control: the source package is Section: text. Section: libs or
> Section: science is probably more appropriate.

I think science is more appropriate than libs in this case. I switched to 
science section.

> d/control: Homepage should probably be http://hlt-mt.fbk.eu/technologies
> /irstlm

Fixed.

> d/copyright: Source should probably be the Github repository, not the
> sourceforge page, which clearly says: "IRSTLM is no more supported on
> SourceForge."

Fixed.

> 
> [1] https://wiki.debian.org/DebianScience
> [2] http://blends.debian.org/science/tasks/
> [3] http://blends.debian.org/science/tasks/linguistics
> 
> Best regards,
> Ghis




signature.asc
Description: OpenPGP digital signature

Bug#823567: ndiswrapper-dkms fails to compile

[Jon]

Package: ndiswrapper-dkms
Version: 1.59-2
Severity: serious
Tags: d-i patch upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The ndiswrapper source uses the depreciated c function 'strnicmp()',
this function is not in the libc anymore.  It can be replaces with the
working function 'strncasecmp()' without any other changes.

Then it will compile, and I've had zero issues with this so far.

Thanks,
Jon.


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

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

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


-- System Information:
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:core-4.1-ia32:core-4.1-noarch:security-4.0-ia32:security-4.0-noarch:security-4.1-ia32:security-4.1-noarch
Distributor ID: Kali
Description:Kali GNU/Linux 2.0
Release:2.0
Codename:   sana
Architecture: i686

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

Versions of packages ndiswrapper-dkms depends on:
ii  dkms  2.2.0.3-2

ndiswrapper-dkms recommends no packages.

ndiswrapper-dkms suggests no packages.

-- no debconf information

Bug#823538: closed by Adam Borowski (Re: Bug#823538: RFS: classic-theme-restorer/1.5.1-1 -- customize the new Firefox look)

[Sean Whitton]

> The name is misleading, it makes it sound as if only looks are restored
> rather than interface including usability issues.  You might consider
> s/look/interface/ in the description in a future upload.

Thanks for the suggestion -- done -- and for the sponsorship.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#823565: ITP: golang-github-fhs-go-netrc -- netrc file parser for Go programming language.

[Nicolas Braud-Santoni]

Package: wnpp
Severity: wishlist
Owner: Nicolas Braud-Santoni 

* Package name: golang-github-fhs-go-netrc
  Version : 0.0~git20160504.0.4ffed54-1
  Upstream Author : Fazlul Shahriar
* URL : https://github.com/fhs/go-netrc
* License : MIT
  Programming Lang: Go
  Description : netrc file parser for Go programming language.

  This is a dependency of golang-github-octokit-go-octokit

Bug#823020: Bug#823500: cannot boot from ext4

[Cyril Brulebois]

Cyril Brulebois  (2016-05-06):
> Anyway, we could probably implement the change globally regardless, just
> to make it possible to check the hypothesis on a wide range of devices,
> and only figure out later how to fix this in a better way?
> 
> Vagrant, what do you think?

I've pushed a pu/disable-flex_bg branch to partman-ext3's git repository.
Feedback/tests welcome. I can push to master and upload if that looks like
a good idea.


KiBi.


signature.asc
Description: Digital signature

Bug#823564: RM: liblog-any-adapter-screencoloredlevel-perl -- ROM; obsoleted upstream and replaced by liblog-any-adapter-screen-perl

[Jonas Smedegaard]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi ftpmasters,

Please liblog-any-adapter-screencoloredlevel-perl from unstable.

No packages depend on it - the only package that did now depend on its
successor, liblog-any-adapter-screen-perl.

Thanks,

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXK+K8AAoJECx8MUbBoAEhqLgQAKfO5ahdJcOpZCUqbihD3WLI
zxlAW2A/OfuB1Kv933kTog5EN/pgU8XUDdAZOrlLVFM9syM3qX+ULfB+OwmCakc2
Gkrh/9egooCjyKfyGo/LGTL2+E01+cAP4QoIXbDsf2m7zZc/VTPhtVTv6w3Lp/Up
ptsT2npcSvGMp37d6WLvHMarBJ0jk7909USqxhl8h7wXk6s51Oble6TIbrws9MMm
Kkjn7wa4jeRL+qButnbn66RN9j4H0kOfHnv5Yvze93dA+oxXWTh2eqOFTZSjo8nE
HvQ0JkOLjDQ8tvVAb3gni0UoPb3rm6gc+g7WUiqrZfxCfCIwkJgZ8e4EKzfhhca6
aSLELLgcCaYrHBdrdKwUMwfERBN80r3cKqZ5/6vOWs10XfU3/yO5FgfTYGEz1MMJ
BpFRQd176+DMGz575h6UfSAkhLVQ/GIntqq00Wrt+L2RSho9E24jlikAk3rHv/5G
doeGHvhn/DVTrQ8LhrTKJ6qvD8f4qQNLLLYWna+zTkbfRxHw3+WX9d/XzAGOueio
HO3YYWUCpFeAP5cnpMDpOQbWppoHd5TyQkdQTkYBqVYS9ZGFGhYENqO41OQ/I7vS
fLCRAgjzEXfhrbpYvP+4CIi4RIZinxxtl0QS97/n0ocQFSQiRe+0dQeYahysc+XH
ALgIOrJRDiAliBM/233r
=81u4
-END PGP SIGNATURE-

Bug#823020: Bug#823500: cannot boot from ext4

[Cyril Brulebois]

Cyril Brulebois  (2016-05-06):
> Strange, vagrant said partitioning from jessie worked fine?
> 
> Anyway, we could try passing the mentioned option to mkfs.ext* to make
> sure it doesn't get in the way, and see how it goes?
> 
> I suppose we're interested in patching commit.d/format_ext3 from
> src:partman-ext3 (yes, this could be considered confusing). If such a
> package is uploaded to unstable, the next d-i daily build should
> contain the said change.

Of course this is largely suboptimal, as this would disable the flex_bg
option (which is probably the default for good reasons) everywhere.

I'm not at all familiar with u-boot integration. Am I correct in
assuming this only happens after partitions are created? In which case
it doesn't seem possible to:
 - keep on creating the partitions as currently done
 - alter them afterwards when u-boot integration happens

since a quick test with a loopback-mounted image file led to:
| kibi@wodi:/scratch$ sudo mkfs.ext4 /dev/mapper/loop0p1
| […]
| kibi@wodi:/scratch$ sudo tune2fs -l /dev/mapper/loop0p1 | grep flex_bg
| Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink 
extra_isize
| kibi@wodi:/scratch$ sudo tune2fs -O ^flex_bg /dev/mapper/loop0p1 
| tune2fs 1.42.12 (29-Aug-2014)
| Clearing the flex_bg flag would cause the the filesystem to be inconsistent.

(BTW this is with a jessie userspace, so flex_bg was the default there
already?)

Anyway, we could probably implement the change globally regardless, just
to make it possible to check the hypothesis on a wide range of devices,
and only figure out later how to fix this in a better way?

Vagrant, what do you think?


KiBi.


signature.asc
Description: Digital signature

Bug#823561: zynaddsubfx: License should be GPL-2+

[Jonas Smedegaard]

Quoting Javier Serrano Polo (2016-05-06 01:15:11)
> According to 
> https://github.com/LMMS/lmms/issues/2752#issuecomment-217043740 , it 
> looks like the license should be GPL-2+ despite what individual files 
> say.

I am not a lawyer.

That conversation lack any proof of copyright and/or licensing having 
changed from what is explicitly stated in headers of sourcecode.  Only 
the copyright holder can relicense beyond the scope of a previous 
license, so stating that the project as a whole is licensed GPL-3+ when 
some parts of the project is GPL-2 is not possible without the consent 
of copyright holders.

I have posted a comment to the referenced upstream bugreport, to try 
steer the discussion away from "Debian view on things" an instead look 
at actual statements in code.


 - Jonas

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

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


signature.asc
Description: signature

Bug#823563: debian-security-support: fails to remove: update-alternatives: error: no alternatives for security-support-ended

[Andreas Beckmann]

Package: debian-security-support
Version: 2016.05.04+nmu1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

0m29.7s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpxDZO77', 
'apt-get', 'remove', 'gettext-base', 'debian-security-support']
0m31.1s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be REMOVED:
debian-security-support gettext-base
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
  After this operation, 854 kB disk space will be freed.
  (Reading database ... 
(Reading database ... 7462 files and directories currently installed.)
  Removing debian-security-support (2016.05.04+nmu1) ...
  update-alternatives: error: no alternatives for security-support-ended
  dpkg: error processing package debian-security-support (--remove):
   subprocess installed pre-removal script returned error exit status 2
  dpkg: gettext-base: dependency problems, but removing anyway as you requested:
   debian-security-support depends on gettext-base.
  
  Removing gettext-base (0.19.7-2) ...
  /usr/bin/check-support-status: 8: .: gettext.sh: not found
  dpkg: error: error executing hook 'if [ -x 
/usr/share/debian-security-support/check-support-status.hook ] ; then 
/usr/share/debian-security-support/check-support-status.hook ; fi', exit code 
512
  E: Sub-process /usr/bin/dpkg returned an error code (2)
0m31.1s DEBUG: Command failed (status=100), but ignoring error: ['chroot', 
'/tmp/piupartss/tmpxDZO77', 'apt-get', 'remove', 'gettext-base', 
'debian-security-support']

cheers,

Andreas


debian-security-support_2016.05.04+nmu1.log.gz
Description: application/gzip

Bug#821234: twinkle: FTBFS: error: 'ucommon::Digest::Digest(const ucommon::Digest&)' is private

[Logan Rosen]

Package: twinkle
Version: 1:1.9.0+dfsg-3
Followup-For: Bug #821234
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/ucommon-7.0.patch: Grab patch from upstream Git to fix
FTBFS with uCommon 7.0.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru twinkle-1.9.0+dfsg/debian/patches/series twinkle-1.9.0+dfsg/debian/patches/series
--- twinkle-1.9.0+dfsg/debian/patches/series	2016-01-12 05:37:32.0 -0500
+++ twinkle-1.9.0+dfsg/debian/patches/series	2016-05-05 19:02:53.0 -0400
@@ -13,3 +13,4 @@
 historyform-disable-editing.patch
 historyform-show-call-details-of-current-item.patch
 fix-conflicting-definition-of-socklen_t-on-gnu-hurd.patch
+ucommon-7.0.patch
diff -Nru twinkle-1.9.0+dfsg/debian/patches/ucommon-7.0.patch twinkle-1.9.0+dfsg/debian/patches/ucommon-7.0.patch
--- twinkle-1.9.0+dfsg/debian/patches/ucommon-7.0.patch	1969-12-31 19:00:00.0 -0500
+++ twinkle-1.9.0+dfsg/debian/patches/ucommon-7.0.patch	2016-05-05 19:02:00.0 -0400
@@ -0,0 +1,78 @@
+From 60e8be6ad116896bdd612b7e6aaa5623dc303a4e Mon Sep 17 00:00:00 2001
+From: Michal Kubecek 
+Date: Thu, 7 Jan 2016 14:48:02 +0100
+Subject: [PATCH] fix build with ucommon 7.0
+
+New version of ucommon adds some restriction to Digest class which
+break the way twinkle is using it:
+
+- proper initialization using constructor is needed
+- c_str() method is gone; fortunately, str() result can be used to
+  initialize std::string instead
+
+Neither of these changes breaks build with ucommon 6.x.
+---
+ src/parser/request.cpp | 24 
+ 1 file changed, 12 insertions(+), 12 deletions(-)
+
+diff --git a/src/parser/request.cpp b/src/parser/request.cpp
+index 550a011..348d679 100644
+--- a/src/parser/request.cpp
 b/src/parser/request.cpp
+@@ -207,19 +207,19 @@ bool t_request::authorize_md5(const t_digest_challenge &dchlg,
+ 		A2 = method2str(method, unknown_method) + ":" + uri.encode();
+ 		A2 += ":";
+ 		if (body) {
+-			digest_t MD5body = "md5";
++			digest_t MD5body("md5");
+ 			MD5body.puts(body->encode().c_str());
+-			A2 += std::string(MD5body.c_str());
++			A2 += std::string(MD5body.str());
+ 		} else {
+-			digest_t MD5body = "md5";
++			digest_t MD5body("md5");
+ 			MD5body.puts("");
+-			A2 += std::string(MD5body.c_str());
++			A2 += std::string(MD5body.str());
+ 		}
+ 	}
+ 	// RFC 2716 3.2.2.1
+ 	// Caculate digest
+-	digest_t MD5A1 = "md5";
+-	digest_t MD5A2 = "md5";
++	digest_t MD5A1("md5");
++	digest_t MD5A2("md5");
+ 
+ 	MD5A1.puts(A1.c_str());
+ 	MD5A2.puts(A2.c_str());
+@@ -227,24 +227,24 @@ bool t_request::authorize_md5(const t_digest_challenge &dchlg,
+ 	std::string x;
+ 
+ 	if (cmp_nocase(qop, QOP_AUTH) == 0 || cmp_nocase(qop, QOP_AUTH_INT) == 0) {
+-	x = std::string(MD5A1.c_str());
++	x = std::string(MD5A1.str());
+ 		x += ":";
+ 		x += dchlg.nonce + ":";
+ 		x += int2str(nc, "%08x") + ":";
+ 		x += cnonce + ":";
+ 		x += qop + ":";
+-		x += std::string(MD5A2.c_str());
++		x += std::string(MD5A2.str());
+ 	} else {
+-x = std::string(MD5A1.c_str());
++		x = std::string(MD5A1.str());
+ 		x += ":";
+ 		x += dchlg.nonce + ":";
+-		x += std::string(MD5A2.c_str());
++		x += std::string(MD5A2.str());
+ 	}
+ 
+-	digest_t digest = "md5";
++	digest_t digest("md5");
+ 	digest.puts(x.c_str());
+ 
+-	resp = std::string(digest.c_str());
++	resp = std::string(digest.str());
+ 
+ 	return true;
+ }

Bug#775013: mt-st: Pass command-line options to the modprobe call

[Iustin Pop]

On 2015-01-10 01:39:52, Artur Rona wrote:
> Package: mt-st
> Version: 1.1-6
> Tags: patch
> Usertags: origin-ubuntu ubuntu-patch vivid
> 
> In Ubuntu, we've applied the attached patch to achieve the following:
> 
>* debian/mt-st.modprobe:
>   - Pass command-line options to the modprobe call.
> 
> We thought you might be interested in doing the same.

Thanks. The patch makes a lot of sense, however I'm going to close it in
the next upload by removing entirely the modprobe.conf file; as such,
mt-st won't interfere anymore at all with modprobe.

regards,
iustin


signature.asc
Description: PGP signature

Bug#823020: Bug#823500: cannot boot from ext4

[Cyril Brulebois]

Heinrich Schuchardt  (2016-05-05):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> The problem occurs  with ext4 partitions created with either of Jessie
> or Stretch when the partition is created with
> 
> sudo mkfs.ext4 /dev/mmcblk0p1

Strange, vagrant said partitioning from jessie worked fine?

Anyway, we could try passing the mentioned option to mkfs.ext* to make
sure it doesn't get in the way, and see how it goes?

I suppose we're interested in patching commit.d/format_ext3 from
src:partman-ext3 (yes, this could be considered confusing). If such a
package is uploaded to unstable, the next d-i daily build should
contain the said change.


KiBi.


signature.asc
Description: Digital signature

Bug#823483: discover: FTBFS: configure: error: Can't find usb library.

[Cyril Brulebois]

Chris Lamb  (2016-05-05):
> Source: discover
> Version: 2.1.2-7
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> discover fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   dh_testdir
>   dh_testroot
>   dh_prep
>   dh_testdir
>   dh_testroot
>   dh_install
>   dh_installdocs
>   dh_installchangelogs
>   dh_compress
>   dh_fixperms
>   dh_installdeb
>   dh_gencontrol
>   dh_md5sums
>   dh_builddeb
>   dpkg-deb: building package 'discover-build-deps' in 
> '../discover-build-deps_2.1.2-7_all.deb'.
>   
>   The package has been created.
>   Attention, the package has been created in the current directory,
>   not in ".." as indicated by the message above!
>   Selecting previously unselected package discover-build-deps.
>   (Reading database ... 23072 files and directories currently installed.)
>   Preparing to unpack discover-build-deps_2.1.2-7_all.deb ...
>   Unpacking discover-build-deps (2.1.2-7) ...
>   Reading package lists...
>   Building dependency tree...
>   Reading state information...
>   Correcting dependencies... Done
>   The following additional packages will be installed:
> libexpat1-dev libusb-dev
>   The following NEW packages will be installed:
> libexpat1-dev libusb-dev
>   0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
>   1 not fully installed or removed.
>   Need to get 163 kB of archives.
>   After this operation, 1133 kB of additional disk space will be used.
>   Get:1 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
> 2.1.1-1 [126 kB]
>   Get:2 http://httpredir.debian.org/debian sid/main amd64 libusb-dev amd64 
> 2:0.1.12-29 [36.9 kB]

Hi Chris,

Isn't that libusb's #823525 (fixed in -30)?


KiBi.


signature.asc
Description: Digital signature

Bug#823562: RFS: zenburn-emacs/2.4-1 [ITP] -- low contrast color theme for Emacs

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package zenburn-emacs.

Zenburn for Emacs is a popular, low-contrast, easy-on-the-eyes theme I
and many others have been using for years.  I intend to maintain this as
part of the pkg-emacsen team.

* Package name: zenburn-emacs
  Version : 2.4-1
  Upstream Author : Bozhidar Batsov
* URL : http://github.com/bbatsov/zenburn-emacs
* License : GPL-3+
  Section : lisp

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/z/zenburn-emacs/zenburn-emacs_2.4-1.dsc

Or build it with gbp:

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

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#823470: RFS: sequitur-g2p/0.0.r1668.r3-1 -- Grapheme to Phoneme conversion tool

[Giulio Paci]

On 05/05/2016 19:07, Christian Kastner wrote:
> On 2016-05-05 17:16, Giulio Paci wrote:
>>> One thing I'm not quite sure I follow yet is the change in the version
>>> numbering scheme, both upstream and in the package. This is how it looks
>>> to me:
>>>
>>>   1. Upstream re-used revision r1668 and added a -r3 suffix
>>>   -> "r1668" trades a bit of revision semantic for version semantic
>>>
>>>   2. Hence your switch to version semantic in d/changelog
>>>
>>> Is my interpretation correct?
>>
>> You are right. The change is due to the fact that they relied on svn 
>> revisions for releases in the past. Now they have switched to another 
>> repository (probably still svn),
>> and I understand that they are around revision 70 on the new one.
>>
>> My understanding is that they have private versions of intermediate packages 
>> that they did not publish.
>>
>> I have not talked with upstream about this anyway.
> 
> I'd do that when you get the chance, just to clarify what release plans
> they have. Some upstreams may even benefit from a bit of guidance, eg:
> 
> https://wiki.debian.org/UpstreamGuide#Releases_and_Versions

Thank you for this pointer.
I will probably do in future, if I will see further development happening.

Unfortunately this software, as many other developed by students, is very 
important in its field,
but lacks further development once the student is graduated. So I cannot 
foresee any future releases,
unless I (or others) propose further changes and these are accepted.

> In this particular case, I'd actually suggest that you stick to your
> previous approach, and just modify it slightly:
> 
>g2p-r1668.tar.gz => 0+r1668
> g2p-r1668-r3.tar.gz => 0+r1668.r3 (or even just keep -r3!)

I decided to follow the suggestion from 
https://www.debian.org/doc/manuals/maint-guide/first.en.html#idp39551808 :

"You should choose the upstream version to consist only of alphanumerics 
(0-9A-Za-z), plus (+), tildes (~), and periods (.). It must start with a digit 
(0-9)."

> The solution above retains the largest flexibility in the face of
> the current ambiguity. For example, if upstream were to release a version
> '0.0.1', your new solution would no longer work:
> 
> $ dpkg --compare-versions '0.0.r1668.3-1' lt '0.0.1-1' || echo "oops!"
> oops!

You are right. I am still wondering how it happened that I changed the version 
scheme...
Probably the error came from the watch file... Anyway it should be fixed now.

> You can achieve the aforementioned modification by chaining patterns in
> uversionmangle using a semicolon. Based on your previous version:
> 
> -opts="uversionmangle=s/^(.*)$/0+$1/"
> +opts="uversionmangle=s/^(.*)$/0+$1/; s/-r(\d+)/.r$1/"
> 
> $ uscan --report-status | grep -A4 'newest first'
> uscan info: Found the following matching hrefs on the web page (newest 
> first):
>g2p-r1668-r3.tar.gz (0+r1668.r3) index=0+r1668.r3-1 
>g2p-r1668.tar.gz (0+r1668) index=0+r1668-1 
>g2p-r103.tar.gz (0+r103) index=0+r103-1 
>g2p-r96.tar.gz (0+r96) index=0+r96-1
> 
> On a side note: I believe you can simplify the version matching pattern
> in your watch file. You currently match for many possible suffixes, but
> upstream apparently only uses .tar.gz.

I simplified suffix matches.

Bests,
Giulio



signature.asc
Description: OpenPGP digital signature

Bug#820493: aptitude: does not install package from Build-Depends

[Manuel A. Fernandez Montecelo]

2016-05-04 21:16 Manuel A. Fernandez Montecelo:

2016-04-10 03:09 Dmitry Smirnov:


Sorry, I'm unable to spot anything useful... Maybe you could try?
Simple "apt-get source civicrm" is enough to fetch the package suitable to
reproduce the problem.


I don't always have the time, as I didn't have much in the last few
weeks, and with my miserable "broadband" took me the best of an hour to
get the system to an up-to-date state today.  In the weeks in between,
perhaps things changed, so it's difficult to solve things in this way...


Anyway, the basic problem today seems to be that:

The following packages have unmet dependencies:
pbuilder-satisfydepends-dummy : Depends: php-mail-mimedecode which is a virtual 
package and is not provided by any available package

This is because the package has been removed:

https://packages.qa.debian.org/p/php-mail-mimedecode/news/20160502T014605Z.html


So this is the real problem now, your package FTBFS.

About php-gettext, php7.0-common (src: php7.0) provides php-gettext,
that's presumably why the "real" package providing php-gettext (source:
php-gettext) doesn't get pulled in.

You can add a dependency on the exact version of the "real" package if
for some reason php7.0-common as provider of php-gettext is not working
for your package.

So I guess that we can close the bug report now?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#823561: zynaddsubfx: License should be GPL-2+

[Javier Serrano Polo]

Package: zynaddsubfx
Version: 2.5.2-2
Severity: wishlist

According to
https://github.com/LMMS/lmms/issues/2752#issuecomment-217043740 , it
looks like the license should be GPL-2+ despite what individual files
say.


smime.p7s
Description: S/MIME cryptographic signature

Bug#820941: no more seen for 22 days

[Oleg SHALAEV]

Since the bug submition I have not encountered the problem any more;
"aptitude reinstall shorewall" works ok.
It is possible that shorewall does not restart only when the package is 
upgraded to a new version.

Bug#823560: please build a pypy-pyparsing package

[Matthias Klose]

Package: src:pyparsing

please build a pypy-pyparsing package, needed to devendorize the packaging and 
setuptools packages.

Bug#823559: [libtablelayout-java] Please ship pom.xml file

[Giovanni Mascellani]

Package: libtablelayout-java
Version: 20090826-2
Severity: wishlist
Tags: patch

Hi.

Please upload the attached patch or authorize me to do a team upload.
The patch adds the shipping of a pom.xml file to the package, which
helps reverse dependencies that compile with maven.

Thanks, Gio.


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.0.0-1-amd64

Debian Release: stretch/sid
  500 unstablerepos.fds-team.de
  500 unstableftp.ch.debian.org
1 experimentalftp.ch.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Giovanni Mascellani 
PhD Student - Scuola Normale Superiore, Pisa, Italy

http://poisson.phc.unipi.it/~mascellani
diff -Nru libtablelayout-java-20090826/debian/changelog libtablelayout-java-20090826/debian/changelog
--- libtablelayout-java-20090826/debian/changelog	2011-08-30 19:43:26.0 +0200
+++ libtablelayout-java-20090826/debian/changelog	2016-05-06 00:39:21.0 +0200
@@ -1,3 +1,11 @@
+libtablelayout-java (20090826-3) unstable; urgency=medium
+
+  * Team upload.
+  * Install POM for libtablelayout-java.
+  * Delete directory "doc" when cleaning.
+
+ -- Giovanni Mascellani   Fri, 06 May 2016 00:39:19 +0200
+
 libtablelayout-java (20090826-2) unstable; urgency=low
 
   * Switch to debhelper level 7.
diff -Nru libtablelayout-java-20090826/debian/control libtablelayout-java-20090826/debian/control
--- libtablelayout-java-20090826/debian/control	2011-08-30 19:42:52.0 +0200
+++ libtablelayout-java-20090826/debian/control	2016-05-06 00:35:39.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Java Maintainers 
 Uploaders: Torsten Werner 
-Build-Depends: ant, cdbs, debhelper (>= 7), default-jdk
+Build-Depends: ant, cdbs, debhelper (>= 7), default-jdk, maven-repo-helper
 Standards-Version: 3.9.1
 Homepage: https://tablelayout.dev.java.net/
 Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/libtablelayout-java
diff -Nru libtablelayout-java-20090826/debian/libtablelayout-java.poms libtablelayout-java-20090826/debian/libtablelayout-java.poms
--- libtablelayout-java-20090826/debian/libtablelayout-java.poms	1970-01-01 01:00:00.0 +0100
+++ libtablelayout-java-20090826/debian/libtablelayout-java.poms	2016-05-06 00:32:16.0 +0200
@@ -0,0 +1 @@
+debian/pom.xml --no-parent
diff -Nru libtablelayout-java-20090826/debian/pom.xml libtablelayout-java-20090826/debian/pom.xml
--- libtablelayout-java-20090826/debian/pom.xml	1970-01-01 01:00:00.0 +0100
+++ libtablelayout-java-20090826/debian/pom.xml	2016-05-06 00:43:38.0 +0200
@@ -0,0 +1,10 @@
+http://maven.apache.org/POM/4.0.0";
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
+4.0.0
+org.debian
+tablelayout
+jar
+20090826
+TableLayout
+
diff -Nru libtablelayout-java-20090826/debian/rules libtablelayout-java-20090826/debian/rules
--- libtablelayout-java-20090826/debian/rules	2011-08-30 19:42:20.0 +0200
+++ libtablelayout-java-20090826/debian/rules	2016-05-06 00:38:38.0 +0200
@@ -7,3 +7,11 @@
 
 get-orig-source:
 	uscan --force-download
+
+binary-post-install/libtablelayout-java::
+	mh_installpoms -plibtablelayout-java
+	mh_installjar -plibtablelayout-java -l debian/pom.xml tablelayout.jar
+
+clean::
+	rm -fr doc
+	mh_clean


signature.asc
Description: OpenPGP digital signature

Bug#809508: cups: Printing fails with "Filter failed"

[Pierre Rudloff]

Le 26/04/2016 16:52, Brian Potkin a écrit :
> How are you going on with this? I ran a quick test on an up-to-date
> Jessie and all four filters used for the job exited with no errors.

You're right, it seems to work now.

Bug#823558: synaptics stopped being used on Lenovo Yoga laptop

[Joey Hess]

Package: xserver-xorg-input-synaptics
Version: 1.8.3-1+b1
Severity: normal

I rebooted today with the touchpad working fine and it came back up with
it messed up (bad accelleration, no tap click). For some reason, X
stopped using the synaptics driver for it and fell back to libinput
instead. Rebooting didn't help, still libinput.

My laptop is a Lenovo Yoga 11gs, and has a clickpad and a touch screen.
I last upgraded this package in February and have certianly rebooted
since then, but may have upgraded some stuff in the past week that broke
it.

The xorg log file did not show it loading the synaptics module at all.
I tried adding an xorg.conf.d to force it to load:

Section "Module"
Load "synaptics"
EndSection

While the module loaded, it was still not used for the touchpad.
The resulting log file is attached as Xorg.0.log.old.

I was finally able to workaround the problem by forcing 
use of the synaptics driver:

Section "Module"
Load "synaptics"
EndSection

Section "InputClass"
Identifier "touchpad tweaked catchall"
MatchIsTouchpad "on"
Driver "synaptics"
EndSection

The logs below are from starting X in that configuration.

One thing I noticed in the logs when X didn't use synaptics is


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jul  2  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Apr  5 03:05 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0a1e] 
(rev 0b)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 173 May  5 18:25 synaptics.conf

KMS configuration files:

/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160424 (Debian 5.3.1-16) ) #1 SMP Debian 4.5.2-1 (2016-04-28)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root  6592 Sep  8  2014 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 29042 Apr 25  2015 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 24584 May  5 18:26 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   910.095] 
X.Org X Server 1.18.3
Release Date: 2016-04-04
[   910.095] X Protocol Version 11, Revision 0
[   910.095] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   910.095] Current Operating System: Linux darkstar 4.5.0-2-amd64 #1 SMP 
Debian 4.5.2-1 (2016-04-28) x86_64
[   910.095] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-2-amd64 
root=UUID=1619e79b-7dc8-46a1-af37-824e461ea961 ro quiet
[   910.095] Build Date: 05 April 2016  07:00:43AM
[   910.095] xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
[   910.095] Current version of pixman: 0.33.6
[   910.095]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   910.095] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   910.095] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May  5 18:26:06 
2016
[   910.095] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   910.095] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   910.095] (==) No Layout section.  Using the first Screen section.
[   910.095] (==) No screen section available. Using defaults.
[   910.095] (**) |-->Screen "Default Screen Section" (0)
[   910.095] (**) |   |-->Monitor ""
[   910.095] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   910.095] (==) Automatically adding devices
[   910.095] (==) Automatically enabling devices
[   910.095] (==) Automatically adding GPU devices
[   910.095] (==) Max clients allowed: 256, resource mask: 0x1f
[   910.095] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   910.095]Entry deleted from font path.
[   910.095] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   910.095] (==) ModulePath set to "/usr/lib/xorg/modules"
[   910.095] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   910.095] (II) Loader magic: 0x558ae86bfdc0
[   910.095] (II) Module ABI versions:
[   910.096]X.Org ANSI C Emulation: 0.4
[   910.096]X.Org Video Driver:

Bug#823557: ITP: zenburn-emacs -- a low contrast color theme for Emacs

[Sean Whitton]

Package: wnpp
Severity: wishlist
Owner: Sean Whitton 

* Package name: zenburn-emacs
  Version : 2.4
  Upstream Author : Bozhidar Batsov
* URL : http://github.com/bbatsov/zenburn-emacs
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : a low contrast color theme for Emacs

Zenburn for Emacs is a popular, low-contrast, easy-on-the-eyes theme I
and many others have been using for years.

I intend to maintain this as part of the pkg-emacsen team.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#823556: RFP: mattermost -- self-hosted team communication service

[Christian Kastner]

Package: wnpp
Severity: wishlist

* Package name: mattermost
  Version : 2.2.0
  Upstream Author : Mattermost, Inc.
* URL : http://www.mattermost.org/
* License : Apache-2
  Programming Lang: Go, React
  Description : self-hosted team communication service

Mattermost is self-hosted team communication service bringing messaging
and file sharing into one place, accessible across PCs and phones, with
archiving and search.

Mattermost is an open source, self-hosted Slack-alternative. It's
features rival Slack features, it's compatible with existing Slack
integrations, and one can even import users and channel history from
existing Slack teams.

Slack seems to be all the rage these days. It would be nice if we could
offer a similar solution within Debian and thereby also support the FOSS
alternative.



signature.asc
Description: OpenPGP digital signature

Bug#821646: [Pkg-roundcube-maintainers] Bug#821646: roundcube-core: PHP 7.0 Transition

[Sandro Knauß]

Hello,

we currently waiting for upstream to ship the new 1.2 version.Currently they 
released a rc version.The current version 1.1.5 is not compatible with PHP 7, 
as it is written in README from upstream...

Today I stared to package 1.2~rc in experimental branch to prepare 1.2 for 
unstable.Hopefully I will finisch a version for experimental next week.

One Issue - I replaced all php5-X depdendency to php-X but now I get the 
following lintian error:
E: roundcube-core: php-script-but-no-phpX-cli-dep usr/share/roundcube/bin/
cleandb.sh

Is it still the recommended way to depend at php7.0.cli , to not  php-cli? For 
me you php7 transistion mail sounds like, that we should prefer  php-cli over 
php7.0-cli dependency. We need php*-cli as dependency, because we run php 
scripts in post/pre inst scripts.

Regards,

sandro

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

Bug#823527: tmux: Terminal bell not shown in status line

[Romain Francoise]

Hello,

On Thu, May 05, 2016 at 07:29:20PM +0200, Marcel Lippmann wrote:
> The issue is: The occurrence of a bell in a window is not indicated by
> ‘!’ in the status line. Steps to reproduce:

This works as expected for me.
Can you share your config files?

Thanks,
-- 
Romain Francoise 
http://people.debian.org/~rfrancoise/

Bug#823513: [Pkg-clamav-devel] Bug#823513: clamav-freshclam: freshclam fails to download daily.cvd and clamav do not start

[Sebastian Andrzej Siewior]

On 2016-05-05 15:52:43 [+0200], Simone Piccardi wrote:
> After installing clamav-freshclam I got these in syslog:
> May  5 15:32:29 jessie freshclam[4851]: ERROR: Can't download daily.cvd from 
> database.clamav.net
> May  5 15:32:29 jessie freshclam[4851]: Giving up on database.clamav.net...
> May  5 15:32:29 jessie freshclam[4851]: Update failed. Your network may be 
> down or none of the mirrors listed in /etc/clamav/freshclam.conf is working. 
> Check http://www.clamav.net/doc/mirrors-faq.html for possible reasons.

…

> So there is no /var/lib/clamav/daily.cvd downloaded and clamav-daemon was 
> not started, silently failing (no trace in syslog also). I just got it 
> because amavis was angry, and then I got the problem with:
> 
> root@jessie:~# systemctl status clamav-daemon
> ● clamav-daemon.service - Clam AntiVirus userspace daemon
>Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled)
>Active: inactive (dead) since gio 2016-05-05 15:45:31 CEST; 28s ago
>start condition failed at gio 2016-05-05 15:45:53 CEST; 6s ago
>ConditionPathExistsGlob=/var/lib/clamav/daily.{c[vl]d,inc} was not 
> met

yeah. as long as the database is missing you can't start clamd.

> I have jessie-updates in my sources list, and I could just plain take the 
> file 
> with wget, so it's not a network problem.
> 
> I could solve the issue downloading the file with:
> 
> cd /var/lib/clamav/
> wget http://database.clamav.net/daily.cvd
> 
> after this clamav-daemon was startable, but the clamav-freshclam package 
> now is just broken, do not work, and the current configuration prevent 
> also clamav-daemon to work.

can you try `freshclam' on the command line and see if it works? It should
work and so should freshclam from cron. It might been a temporary problem.

Sebastian

Bug#823552: endless "supply vcc not found, using dummy regulator"

[Steinar H. Gunderson]

On Thu, May 05, 2016 at 11:01:48PM +0100, Ben Hutchings wrote:
>> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid 
>> and
>> installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and 
>> updating
>> boot.ini -- I'm not entirely sure if this can be done more automatically),
> That should be handled by flash-kernel though I don't know whether it
> supports this specific machine yet.

Thanks, I'll have a look. Most likely this part is just user cluelessness :-)

>> As a reference point, this did not happen with 4.4.0-0.bpo.1-armmp from
>> jessie-backports, but I'm unsure if this is because of the kernel or due to
>> something in the initramfs differing between jessie and sid.
> It *could* be due to changes in initramfs-tools.
> 
> Anyway, I'll leave this for the ARM porters to diagnose.

OK. I noticed that the network card hangs on the USB bus, so this delays
networking a _lot_ on bootup, but eventually the USB bus comes up and the
network with it.

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

Bug#822245: vlc desktop file missing Mime type 'video/vnd.mpegurl'

[Petter Reinholdtsen]

[Sebastian Ramacher]
> Hi Petter

Hi.

> It's a lot easier for us if you send a patch upstream [1] and point us
> to the commit. Or wait until someone of use has the time to do that.

Right.  I'll try to see if I can do that.  Until then, I decided to
compare the announced supported Mime types for the VLC desktop file and
the browser plugin, and was surprised that there was quite a lot of
difference there:

These are only announced by the desktop file:

application/x-extension-mp4
application/x-flac
application/x-shockwave-flash
audio/amr-wb
audio/vnd.rn-realaudio
audio/x-mp3
audio/x-ms-asf
audio/x-ms-asx
audio/x-ms-wax
audio/x-pn-aiff
audio/x-pn-au
audio/x-pn-realaudio
audio/x-pn-realaudio-plugin
audio/x-pn-wav
audio/x-pn-windows-acm
audio/x-real-audio
audio/x-scpls
audio/x-vorbis+ogg
image/vnd.rn-realpix
misc/ultravox
video/dv
video/mp2t
video/mp4v-es
video/msvideo
video/vnd.rn-realvideo
video/x-anim
video/x-avi
video/x-flc
video/x-fli
video/x-nsv
video/x-ogm+ogg
x-content/audio-cdda
x-content/audio-player
x-content/video-dvd
x-content/video-svcd
x-content/video-vcd
x-scheme-handler/mms
x-scheme-handler/rtmp
x-scheme-handler/rtsp

These are only announced by the browser plugin:

application/mpeg4-iod
application/mpeg4-muxcodetable
application/x-google-vlc-plugin
application/x-mplayer2
application/x-vlc-plugin
audio/3gpp
audio/3gpp2
audio/flac
audio/m4a
audio/ogg;
audio/wav
audio/x-ms-wma
audio/x-realaudio
codecs=opus
video/3gpp
video/3gpp2
video/divx
video/flv
video/mpeg-system
video/x-m4v
video/x-mpeg-system
video/x-ms-asf-plugin
video/x-ms-wvx

I suspect both should agree on the MIME types supported by VLC.  Note
that none of them support the MIME type requested in this bug report.

I used this script to generate the list:
#!/bin/sh
#
# Compare supported MIME types of vlc desktop file and browser plugin.

cat > x.c <
#include 

int main(int argc, char *argv[]) {
  void *lib_handle;
  char *error;
  lib_handle = dlopen(argv[1], RTLD_LAZY);
  if (!lib_handle) {
fprintf(stderr, "error: unable to load library\n");
return(1);
  }
  char * (*func)(void);
  func = dlsym(lib_handle, "NP_GetMIMEDescription");
  if (NULL != (error = dlerror())) {
fprintf(stderr, "error: from dlsym: %s\n", error);
return 1;
  }
  char *mimedesc = (*func)();
  printf("%s\n", mimedesc);
  dlclose(lib_handle);
  return 0;
}
EOF

gcc -o x x.c -ldl

./x /usr/lib/mozilla/plugins/libvlcplugin.so | sed "s/;/;\n/g" | \
cut -d: -f1 |sort > plugin
grep ^MimeType /usr/share/applications/vlc.desktop | cut -d= -f2- | \
 tr ';' "\n" | sort > desktop

echo "These are only announced by the desktop file:"
comm -13 plugin desktop | sed 's/^/\t/'

echo "These are only announced by the browser plugin:"
comm -23 plugin desktop | sed 's/^/\t/'

rm plugin desktop x

--
Happy hacking
Petter Reinholdtsen

Bug#823555: Despite the fact that I have org.gnome.Platform.Locale installed, I have issues when running Pitivi with LANG set to fr_FR.UTF-8

[antistress]

Package: xdg-app
Version: 0.5.0-1

Hi,

Following these instructions to install Pitivi daily bundle through 
xdg-app [1] and trying to run it, I get an error message relative locale 
despite the fact that org.gnome.Platform.Locale is installed :


"./pitivi-xdg-app

==
Updating pitivi
==

-> Updating org.gnome.Platform 3.20

1 metadata, 0 content objects fetched; 313 B transferred in 3 seconds
-> Updating org.gnome.Platform.Locale

1 metadata, 0 content objects fetched; 313 B transferred in 2 seconds
-> Updating org.pitivi.Pitivi master...


Couldn't set locale. /app/share/locale unsupported locale setting
Couldn't set locale. /app/share/locale unsupported locale setting

(pitivi:2): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.

** (pitivi:2): WARNING **: Couldn't connect to accessibility bus: Failed 
to connect to socket /tmp/dbus-CQ7da3CMbG: Connection refused

Traceback (most recent call last):
  File "/app/bin/pitivi", line 147, in 
_check_requirements()
  File "/app/bin/pitivi", line 128, in _check_requirements
if not check_requirements():
  File "/app/lib/pitivi/python/pitivi/check.py", line 276, in 
check_requirements

print((_("Missing soft dependency:")))
UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in 
position 1: ordinal not in range(128)"



Running "$ LANG=fr_FR.UTF-8 xdg-app run org.pitivi.Pitivi" also failed :

"Couldn't set locale. /app/share/locale unsupported locale setting
Couldn't set locale. /app/share/locale unsupported locale setting

(pitivi:2): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.

** (pitivi:2): WARNING **: Couldn't connect to accessibility bus: Failed 
to connect to socket /tmp/dbus-CQ7da3CMbG: Connection refused

Traceback (most recent call last):
  File "/app/bin/pitivi", line 147, in 
_check_requirements()
  File "/app/bin/pitivi", line 128, in _check_requirements
if not check_requirements():
  File "/app/lib/pitivi/python/pitivi/check.py", line 276, in 
check_requirements

print((_("Missing soft dependency:")))
UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in 
position 1: ordinal not in range(128)"



Running "$ xdg-app install --user gnome org.gnome.Platform.Locale 3.20" 
says :

"error: Runtime org.gnome.Platform.Locale, branch 3.20 is already installed"


See also the result of :
"$ xdg-app run --command=bash --filesystem=xdg-download org.pitivi.Pitivi
bash-4.3$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=fr_FR.utf8
LC_CTYPE="fr_FR.utf8"
LC_NUMERIC="fr_FR.utf8"
LC_TIME="fr_FR.utf8"
LC_COLLATE="fr_FR.utf8"
LC_MONETARY="fr_FR.utf8"
LC_MESSAGES="fr_FR.utf8"
LC_PAPER="fr_FR.utf8"
LC_NAME="fr_FR.utf8"
LC_ADDRESS="fr_FR.utf8"
LC_TELEPHONE="fr_FR.utf8"
LC_MEASUREMENT="fr_FR.utf8"
LC_IDENTIFICATION="fr_FR.utf8"
LC_ALL="


Whereas running $ LANG=en_US.UTF-8 xdg-app run org.pitivi.Pitivi works 
(=Pitivi starts)



FWIW I'm running Linux HAL 4.5.0-2-amd64 #1 SMP Debian 4.5.2-1 
(2016-04-28) x86_64 GNU/Linux & libc6 2.22-7



Thanks !

Bug#823552: endless "supply vcc not found, using dummy regulator"

[Ben Hutchings]

On Thu, 2016-05-05 at 23:29 +0200, Steinar H. Gunderson wrote:
> Package: linux-image-4.5.0-2-armmp-lpae
> Version: 4.5.2-1
> Severity: normal
> 
> Hi,
> 
> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid 
> and
> installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating
> boot.ini -- I'm not entirely sure if this can be done more automatically),

That should be handled by flash-kernel though I don't know whether it
supports this specific machine yet.

> the serial console shows tens of thousands of these messages on boot:
> 
> [   47.161428] exynos-dwc3 usb@1200: no suspend clk specified 
>   
> [   47.162811] usb_phy_generic.49646.auto supply vcc not found, using dummy 
> regulator 
> [   47.163532] usb_phy_generic.49647.auto supply vcc not found, using dummy 
> regulator
> 
> They appear to go on forever, blocking boot -- until I set the log level to 0
> to suppress them (using magic SysRq over the serial console), nothing else 
> seems
> to happen on the machine.
> 
> As a reference point, this did not happen with 4.4.0-0.bpo.1-armmp from
> jessie-backports, but I'm unsure if this is because of the kernel or due to
> something in the initramfs differing between jessie and sid.

It *could* be due to changes in initramfs-tools.

Anyway, I'll leave this for the ARM porters to diagnose.

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken.

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

Bug#823553: openexr: FTBFS in testing: fork: Resource temporarily unavailable

[Santiago Vila]

For completeness, I repeated the build without eatmydata
and this was the result.


openexr_2.2.0-10_amd64-20160505-2338.gz
Description: application/gzip

Bug#823554: vulkan: should break/replace upstream-provided packages

[Logan Rosen]

Source: vulkan
Version: 1.0.8.0+dfsg1-1
Severity: normal

Dear Maintainer,

As evidenced by a bug report in Ubuntu [1], the vulkan packages in Debian
conflict with at least one upstream-provided Vulkan SDK package.
Specifically, I was able to find this documentation [2] that lists three
upstream packages:
- vulkan-sdk-runtime
- vulkan-sdk-headers
- vulkan-loader

There should probably be a breaks/replaces relationship against some/all of
these packages to ensure that users aren't trying to install the Debian
packages over the upstream ones (and causing file conflicts).

I'm guessing that at least:
- libvulkan1 should break/replace vulkan-sdk-runtime
- libvulkan-dev should break/replace vulkan-sdk-headers

But I haven't done investigation into the files in each package to see which
conflict.

Thanks,
Logan

[1] https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1572114
[2] 
http://support.amd.com/en-us/kb-articles/Pages/Install-LunarG-Vulkan-SDK.aspx

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#823553: openexr: FTBFS in testing: fork: Resource temporarily unavailable

[Santiago Vila]

Package: src:openexr
Version: 2.2.0-10
Severity: serious

Dear maintainer:

Every time I try to build this package in stretch, it fails:


make  check-TESTS
make[4]: Entering directory '/<>/IlmImfTest'
make[5]: Entering directory '/<>/IlmImfTest'
../test-driver: line 107: 21195 Aborted "$@" > $log_file 2>&1
FAIL: IlmImfTest
make[5]: fork: Resource temporarily unavailable


The build was made on a virtual machine running stretch having 6GB of
RAM and 4 GB of RAM, using sbuild and eatmydata with a stretch chroot.

Disabling eatmydata does not make any difference, it also fails.

This is strange because it built ok on 2016-03-20 (also in testing)
on a machine having less memory.

The full build log is attached.

Thanks.

openexr_2.2.0-10_amd64-20160505-2254.gz
Description: application/gzip

Bug#823496: jessie-pu: package icedove/38.7.0-1~deb8u3

[Adam D. Barratt]

Control: tags -1 + pending

On Thu, 2016-05-05 at 13:15 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On 2016-05-05 12:24, Julien Cristau wrote:
> > One further build fix for icedove, which was applied to unstable but 
> > not
> > jessie-security *sigh*.
> 
> Looks fine to me, thanks.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#819658: jessie-pu: package hexchat/2.10.1-1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2016-04-22 at 21:57 +0100, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed
> 
> On Mon, Apr 11, 2016 at 01:26:45PM -0600, Jesse Rhodes wrote:
> > After discussion in IRC, I now understand that a bug can be closed
> > more than once, which seems a little counter-intuitive at first, but I
> > get why.
> > Here's the updated debdiff with the bug close included. Hopefully this
> > is the final one. Apologies for the extra noise.
> 
> This bit confused me a bit:
> 
> + struct chiper_info {
> + char version[16];
> +-char chiper[24];
> ++char chiper[48];
> + int chiper_bits;
> + };
> 
> I assume this is cipher stuff. At least there is consistency, I suppose.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#823552: endless "supply vcc not found, using dummy regulator"

[Steinar H. Gunderson]

Package: linux-image-4.5.0-2-armmp-lpae
Version: 4.5.2-1
Severity: normal

Hi,

I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid and
installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating
boot.ini -- I'm not entirely sure if this can be done more automatically), the
serial console shows tens of thousands of these messages on boot:

[   47.161428] exynos-dwc3 usb@1200: no suspend clk specified   
[   47.162811] usb_phy_generic.49646.auto supply vcc not found, using dummy 
regulator 
[   47.163532] usb_phy_generic.49647.auto supply vcc not found, using dummy 
regulator

They appear to go on forever, blocking boot -- until I set the log level to 0
to suppress them (using magic SysRq over the serial console), nothing else seems
to happen on the machine.

As a reference point, this did not happen with 4.4.0-0.bpo.1-armmp from
jessie-backports, but I'm unsure if this is because of the kernel or due to
something in the initramfs differing between jessie and sid.

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[John Paul Adrian Glaubitz]

On 05/05/2016 10:45 PM, Lennart Sorensen wrote:
>> I just verified that the patch provided fixes the problem as expected.
> 
> I have submitted it upstream.

Great, that was quick.

Please let me know in the bug tracker when it has been merged upstream,
then Ben will be able to merge it in the Debian kernel.

As I learned recently with two of my own patches, the policy we have in
Debian prevented them from being merged unless they were merged upstream.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#823433: jessie-pu: package openjdk-7/7u101-2.6.6-2~deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2016-05-04 at 19:38 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Wed, 2016-05-04 at 19:34 +0200, Julien Cristau wrote:
> > The latest openjdk-7 security update broke the arm32 JIT.  This was
> > disabled in experimental (7u101-2.6.6-2) and wheezy LTS
> > (7u101-2.6.6-2~deb7u1), but not in jessie-security, so armel and armhf
> > now FTBFS.  This pulls in the changes from 7u101-2.6.6-2.
> 
> The changelog changes are a little ugly, but please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#804807: utopia-documents: FTBFS with swig 3.0

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2015-11-11 12:47:33 [-0800], Steve Langasek wrote:
> The utopia-documents package fails to build in unstable, now that swig has
> been updated to version 3.0.7:

The two patches attached will let build again. However due to #812823 I
don't think it makes sense to apply them.

Sebastian
Index: utopia-documents-2.4.4/libambrosia/ambrosia/utils.cpp
===
--- utopia-documents-2.4.4.orig/libambrosia/ambrosia/utils.cpp
+++ utopia-documents-2.4.4/libambrosia/ambrosia/utils.cpp
@@ -82,7 +82,7 @@ extern "C" {
 glUseProgram = glUseProgramObjectARB;
 #else
 if (!glShaderSource && glShaderSourceARB)
-glShaderSource = (void (*)(GLuint, GLsizei, const GLchar**, const GLint*))glShaderSourceARB;
+glShaderSource = (void (*)(GLuint, GLsizei, const GLchar* const*, const GLint*))glShaderSourceARB;
 if (!glCompileShader && glCompileShaderARB)
 glCompileShader = (void (*)(GLuint))glCompileShaderARB;
 if (!glGetShaderiv && glGetObjectParameterivARB)
Index: utopia-documents-2.4.4/libutopia2/plugins/python/spine/spineapi_python.py
===
--- utopia-documents-2.4.4.orig/libutopia2/plugins/python/spine/spineapi_python.py
+++ utopia-documents-2.4.4/libutopia2/plugins/python/spine/spineapi_python.py
@@ -1,3 +1,4 @@
+%pythoncode %{
 ###
 #   
 #This file is part of the Utopia Documents application.
@@ -28,6 +29,7 @@
 #along with Utopia Documents. If not, see 
 #   
 ###
+%}
 
 %pythonappend Annotation::Annotation() {
 self.beginRegion()
@@ -159,12 +161,12 @@
 else:
 return input
 
-#print (before, label, after)
+# %{ print (before, label, after) }%
 before, label, after = (fuzz(before), fuzz(label, strict = True), fuzz(after))
-#print (before, label, after)
+# %{ print (before, label, after) }%
 regex = "%s.?(%s).?%s" % (before, label, after)
 
-# Now ignore whole matches, and get only the sub-string matches
+# %{ Now ignore whole matches, and get only the sub-string matches }%
 return self.search(regex, spineapi.RegExp + spineapi.IgnoreCase)[1::2]
 
 def annotations(self, scratch = None):
@@ -252,7 +254,7 @@
 try:
 del self[key]
 except KeyError:
-# Ignore
+# {% Ignore }%
 pass
 for i in value:
 self.insertProperty(key, unicode(i))
@@ -334,7 +336,7 @@
 
 def appendTextExtent(self, extent):
 self.regions += extent.boundingBoxes()
-# FIXME how to add text content?
+# %{ FIXME how to add text content? }%
 
 def content(self):
 strippedtxt=self.rich_content
@@ -348,23 +350,23 @@
 if cursor.wordValid():
 text=cursor.wordText().strip()
 
-# replace existing underscores with double underscores
-# we will of course fail to preserve existing double underscores
+# %{ replace existing underscores with double underscores }%
+# %{ we will of course fail to preserve existing double underscores }%
 text.replace('_', "\x2017")
 
-# add a space or font change character if neccessary
+# %{ add a space or font change character if neccessary }%
 if self.rich_content:
 
-# deal with hyphenated lines
-# (hyphenated words should already include the hyphen)
+# %{ deal with hyphenated lines }%
+# %{ (hyphenated words should already include the hyphen) }%
 need_space=True
 
-# shame python does not understand unicode classes
+# %{ shame python does not understand unicode classes }%
 if self.rich_content[-1] in [u"-", u"\x058A", u"\x2010", u"\x2013", u"\x2014", u"\xFE63", u"\xFF0D"]:
 self.rich_content= self.rich_content[0:-1]
 need_space=False
 
-# Mark font changes
+# %{ Mark font changes }%
 if cursor.wordFontName() != self.last_font:
 self.rich_content+="_"
 self.last_font=cursor.wordFontName()
@@ -375,7 +377,7 @@
 self.rich_content=''
 self.last_font=cursor.wordFontName()
 
-# add text
+# %{ add text }%
 self.rich_content+= text
 
   }
Index: utopia-documents-2.4.4/libutopia2_auth/plugins/python/utopia/auth.i
===
--- utopia-documents-2.4.4.orig/libutopia2_auth/plugins/python/utopia/auth.i
+++ utopia

Bug#823549: python-mapnik: please build with pycairo support

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Asbjørn,

Thanks for the patch, I've applied it in git and a new upload to
unstable will follow shortly.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#774711: openssh and putty

[Matt Taggart]

Today I was wondering about what crypto puTTY supports and the implications 
for openssh support in Debian and restricting options as we've been 
discussing in #774711. Here is what I found:

===
puTTY -http://www.chiark.greenend.org.uk/~sgtatham/putty/
current released version 0.67

Documented at
http://the.earth.li/~sgtatham/putty/0.67/htmldoc/Chapter4.html

The following are supported in 0.67, described as openssh option names and 
for newer options the date and release they first appeared in puTTY.

Keys (in sshrsa.c, sshdss.c,sshecc.c)
* ssh-rsa
* ssh-dss
* ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521 
(2014-11-02,0.64)
* ssh-ed25519 (2015-05-09, 0.65)

KEX (in sshdh.c, sshecc.c)
* diffie-hellman-group-exchange-sha256
* diffie-hellman-group14-sha1
* diffie-hellman-group1-sha1
* diffie-hellman-group-exchange-sha1
* ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521 
(2014-11-02,0.64))
* curve25519-sha...@libssh.org (2015-05-09, 0.65)

cipher (in sshaes.c, ssharcf.c, sshblowf.h, sshdes.c, sshccp.c)
* aes256-ctr, aes192-ctr, aes128-ctr
* aes256-cbc, aes192-cbc, aes128-cbc
* rijndael-...@lysator.liu.se
* arcfour256, arcfour128
* blowfish-cbc(128), blowfish-ctr(256, openssh support?)
* 3des-cbc, 3des-ctr(openssh support?)
* chacha20-poly1...@openssh.com (2015-06-07, 0.65)

MAC (in sshsha.c, sshsh256.c sshsh512.c, sshmd5.c, )
* hmac-md5, hmac-md5-...@openssh.com
* hmac-sha1, hmac-sha1-...@openssh.com
* hmac-sha1-96, hmac-sha1-96-...@openssh.com
* hmac-sha2-256, hmac-sha2-256-...@openssh.com (2013-02-20, 0.63)
===

If you want to support squeeze(released 2011-02) and newer and putty 
0.63(released 2013-08) and newer (and you agree with the other decisions 
mentioned in this bug, like dropping rsa1/md5/des/ecdsa) then the minimum 
modern options you need are:

===
HostKeyAlgorithms ssh-ed25519-cert-...@openssh.com, ssh-ed25519,\
ssh-rsa-cert-...@openssh.com, ssh-rsa-cert-...@openssh.com,ssh-rsa

KexAlgorithms curve25519-sha...@libssh.org,\
diffie-hellman-group-exchange-sha256

Ciphers chacha20-poly1...@openssh.com,aes256-...@openssh.com,
aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr

MACs hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,\
hmac-ripemd160-...@openssh.com,umac-128-...@openssh.com,\
hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-...@openssh.com
===

If people encounter other implementations of ssh that can't communicate 
with a debian system using the above, please report it to #774711 as it has 
implicationson what debian/upstream need to support/document.

HTH,

-- 
Matt Taggart
tagg...@debian.org

Bug#812823: utopia-documents: Segmentation fault on start

[Sebastian Andrzej Siewior]

On 2016-01-26 18:38:23 [-0500], Douglas Calvert wrote:
> gdb followus:
> 
> #0  0x7fc100d95795 in QMetaObject::className() const () from 
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

with QT's dbg package I get

#0  QtPrivate::RefCount::deref (this=0x74430f00) at 
../../include/QtCore/../../src/corelib/tools/qrefcount.h:67
#1  QByteArray::~QByteArray (this=, __in_chrg=)
at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:459
#2  rawStringData (index=, mo=mo@entry=0x74873800 
) at kernel/qmetaobject.cpp:156
#3  objectClassName (m=m@entry=0x74873800 ) at 
kernel/qmetaobject.cpp:301
#4  QMetaObject::className (this=this@entry=0x74873800 
) at kernel/qmetaobject.cpp:311

but yes, it crashes on start. I figured out that if you remove 
- libambrosia-atom_basic.so
- libambrosia-chain_basic.so
- libpapyro-ambrosia.so

from /usr/lib/utopia-documents/plugins then it works. Not sure what
those plugins are doing.

Sebastian

Bug#681726: eclipse: Upgrade Eclipse to Juno 4.2

[Markus Koschany]

Am 05.05.2016 um 22:59 schrieb Mykola Nikishov:
> Markus Koschany  writes:
> 
>> The new build system Tycho is completely different and is now Maven
>> based. It must be packaged first. Several modules must be updated as
>> well.
> 
> Strictly speaking, Eclipse Tycho is just a set of Maven plug-ins and
> (just a wild guess) not that hard to package.
> 
> The much bigger problem is p2 repositories that Tycho uses to download
> dependencies from. These dependencies are OSGi bundles and should be
> packaged first, right?

You will have to package all build-dependencies as separate Debian
packages if they are not already available. Downloading dependencies at
build time from untrusted repositories is not allowed in Debian.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#823551: linux-image-4.5.0-2-amd64: [graphdriver] prior storage driver "aufs" failed: driver not supported

[joblack]

Package: src:linux
Version: 4.5.2-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
Docker doesn't start because of missing aufs module

root@koeck:/home/joblack# docker -d

Warning: '-d' is deprecated, it will be removed soon. See usage.
WARN[] please use 'docker daemon' instead.
INFO[] Listening for HTTP on unix (/var/run/docker.sock)
ERRO[] [graphdriver] prior storage driver "aufs" failed: driver not 
supported
FATA[] Error starting daemon: error initializing graphdriver: driver not 
supported
*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160424 (Debian 5.3.1-16) ) #1 SMP Debian 4.5.2-1 (2016-04-28)

** Command line:
BOOT_IMAGE=/vmlinuz-4.5.0-2-amd64 root=/dev/mapper/koeck--vg-root ro quiet

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[1.221592] usb usb1: Product: UHCI Host Controller
[1.221593] usb usb1: Manufacturer: Linux 4.5.0-2-amd64 uhci_hcd
[1.221594] usb usb1: SerialNumber: :00:01.2
[1.221750] hub 1-0:1.0: USB hub found
[1.221758] hub 1-0:1.0: 2 ports detected
[1.255280] FDC 0 is a S82078B
[1.255564] input: VirtualPS/2 VMware VMMouse as 
/devices/platform/i8042/serio1/input/input3
[1.431614] input: VirtualPS/2 VMware VMMouse as 
/devices/platform/i8042/serio1/input/input2
[1.466990]  vda: vda1 vda2 < vda5 >
[1.672686] device-mapper: uevent: version 1.0.3
[1.673103] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: 
dm-de...@redhat.com
[1.684118] usb 1-1: new full-speed USB device number 2 using uhci_hcd
[1.944765] usb 1-1: New USB device found, idVendor=0627, idProduct=0001
[1.944773] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5
[1.944776] usb 1-1: Product: QEMU USB Tablet
[1.944779] usb 1-1: Manufacturer: QEMU 1.0
[1.944782] usb 1-1: SerialNumber: 42
[1.957997] hidraw: raw HID events driver (C) Jiri Kosina
[1.980179] usbcore: registered new interface driver usbhid
[1.980183] usbhid: USB HID core driver
[1.985869] input: QEMU 1.0 QEMU USB Tablet as 
/devices/pci:00/:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
[1.986205] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 
Pointer [QEMU 1.0 QEMU USB Tablet] on usb-:00:01.2-1/input0
[2.000152] tsc: Refined TSC clocksource calibration: 2600.048 MHz
[2.000160] clocksource: tsc: mask: 0x max_cycles: 
0x257a69760b8, max_idle_ns: 440795224253 ns
[   18.371602] random: nonblocking pool is initialized
[   25.212977] NET: Registered protocol family 38
[   44.451223] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   44.597240] PM: Starting manual resume from disk
[   44.597246] PM: Hibernation image partition 253:2 present
[   44.597247] PM: Looking for hibernation image.
[   44.597519] PM: Image not found (code -22)
[   44.597521] PM: Hibernation image not present or could not be loaded.
[   44.643922] SGI XFS with ACLs, security attributes, realtime, no debug 
enabled
[   44.678305] XFS (dm-1): Mounting V4 Filesystem
[   44.831575] XFS (dm-1): Ending clean mount
[   45.034134] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[   45.034188] systemd[1]: Detected virtualization bochs.
[   45.034193] systemd[1]: Detected architecture x86-64.
[   45.035658] systemd[1]: Set hostname to .
[   45.177169] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   45.177419] systemd[1]: Created slice System Slice.
[   45.177476] systemd[1]: Started Dispatch Password Requests to Console 
Directory Watch.
[   45.177518] systemd[1]: Listening on udev Kernel Socket.
[   45.177622] systemd[1]: Listening on Journal Audit Socket.
[   45.177661] systemd[1]: Listening on Syslog Socket.
[   45.177802] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[   45.177816] systemd[1]: Reached target Remote File Systems (Pre).
[   45.177866] systemd[1]: Listening on udev Control Socket.
[   45.178043] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[   45.178180] systemd[1]: Created slice system-systemd\x2dcryptsetup.slice.
[   45.178221] systemd[1]: Listening on LVM2 poll daemon socket.
[   45.178245] systemd[1]: Listening on LVM2 metadata daemon socket.
[   45.178282] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   45.178322] systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
[   45.178354] systemd[1]: Listening on Journal Socket (/dev/log).
[   45.178392] systemd[1]: Listening on Journal Socket.
[   45.188276] systemd[1]: Mounting Huge Pages File System...
[   45.189815] systemd[1]: Starting Loa

Bug#823550: dune-functions: FTBFS with glibc 2.23

[Logan Rosen]

Package: dune-functions
Version: 2.4~20160406ge6b3b4c-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

dune-functions FTBFS in Ubuntu because we switched to glibc 2.23, which
apparently changed the behavior of std::accumulate, as you can see here:
https://launchpadlibrarian.net/257938061/buildlog_ubuntu-yakkety-amd64.dune-functions_2.4~20160406ge6b3b4c-1_BUILDING.txt.gz

The documentation for std::accumulate says to include the  header,
and that fixed the build.

This will have to be bumped to serious importance once glibc 2.23 is in
unstable - better to fix it beforehand!

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/std-accumulate.patch: Include  in files that use
std::accumulate to fix FTBFS with glibc 2.23.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru dune-functions-2.4~20160406ge6b3b4c/debian/patches/series dune-functions-2.4~20160406ge6b3b4c/debian/patches/series
--- dune-functions-2.4~20160406ge6b3b4c/debian/patches/series	2016-04-08 04:13:24.0 -0400
+++ dune-functions-2.4~20160406ge6b3b4c/debian/patches/series	2016-05-05 02:53:32.0 -0400
@@ -1 +1,2 @@
 skip-hybrid-tests.patch
+std-accumulate.patch
diff -Nru dune-functions-2.4~20160406ge6b3b4c/debian/patches/std-accumulate.patch dune-functions-2.4~20160406ge6b3b4c/debian/patches/std-accumulate.patch
--- dune-functions-2.4~20160406ge6b3b4c/debian/patches/std-accumulate.patch	1969-12-31 19:00:00.0 -0500
+++ dune-functions-2.4~20160406ge6b3b4c/debian/patches/std-accumulate.patch	2016-05-05 02:56:42.0 -0400
@@ -0,0 +1,25 @@
+Index: dune-functions-2.4~20160406ge6b3b4c/dune/functions/functionspacebases/bsplinebasis.hh
+===
+--- dune-functions-2.4~20160406ge6b3b4c.orig/dune/functions/functionspacebases/bsplinebasis.hh
 dune-functions-2.4~20160406ge6b3b4c/dune/functions/functionspacebases/bsplinebasis.hh
+@@ -5,6 +5,8 @@
+  * \brief The B-spline global function space basis
+  */
+ 
++#include 
++
+ /** \todo Don't use this matrix */
+ #include 
+ 
+Index: dune-functions-2.4~20160406ge6b3b4c/dune/functions/functionspacebases/test/gridviewfunctionspacebasistest.cc
+===
+--- dune-functions-2.4~20160406ge6b3b4c.orig/dune/functions/functionspacebases/test/gridviewfunctionspacebasistest.cc
 dune-functions-2.4~20160406ge6b3b4c/dune/functions/functionspacebases/test/gridviewfunctionspacebasistest.cc
+@@ -3,6 +3,7 @@
+ #include 
+ 
+ #include 
++#include 
+ 
+ #include 
+ #include 

Bug#823549: python-mapnik: please build with pycairo support

[Asbjørn Sloth Tønnesen]

Package: python-mapnik
Severity: wishlist
Tags: patch

With the current package pycairo support is missing:

>>> import mapnik
_frozen_importlib:222: RuntimeWarning: to-Python converter for 
std::shared_ptr > already registered; second 
conversion method ignored.
_frozen_importlib:222: RuntimeWarning: to-Python converter for 
std::shared_ptr already registered; second conversion 
method ignored.
_frozen_importlib:222: RuntimeWarning: to-Python converter for 
std::shared_ptr already registered; second conversion 
method ignored.
_frozen_importlib:222: RuntimeWarning: to-Python converter for 
std::shared_ptr already registered; second conversion 
method ignored.
_frozen_importlib:222: RuntimeWarning: to-Python converter for 
std::shared_ptr already registered; second conversion method 
ignored.
>>> mapnik.has_cairo()
True
>>> mapnik.has_pycairo()
False

With the attached patch mapnik.has_pycairo() also returns True.

There already is a dependency on python-cairo in the control file,
the condition in setup.py (line 230) just didn't get triggered.

Related upstream issue:
https://github.com/mapnik/python-mapnik/issues/58

Without pycairo support, the included mapnik.printing doesn't work
nor fail nicely.

-- 
Best regards
Asbjørn Sloth Tønnesen


0001-Enable-Cairo-support.patch
Description: Binary data

Bug#823466: [pkg-go] Bug#823466: golang-github-docker-libnetwork: Please update to latest upstream release

[Potter, Tim (HPE Linux Support)]

On 5 May 2016, at 2:17 PM, Dmitry Smirnov  wrote:
> 
> On Thursday, 5 May 2016 1:15:21 AM AEST Potter, Tim (HPE Linux Support)
> wrote:
>> Please upload the latest snapshot of the golang-github-docker-libnetwork
>> package, 0.7.0~rc.6+dfsg.  I've already packaged this in the repo on
>> alioth.
> 
> Do we _really_ need ~RC version? I prefer to upload proper stable releases
> whenever possible...

Me too.  I'd prefer a proper release as well.  However Docker 1.11.0 
specifically depends on
on 0.7.0-rc.6 and there's no newer release.  I just checked and a 0.7.0-rc.7 
came out a while
after I packaged rc.6 though.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#712841: A bit late, but still an issue...

[Martin Michlmayr]

* Christian Mueller  [2016-04-29 22:20]:
> Long story cut short: if there is a way to identify TS-119 vs. TS-219
> hardware, a fix would be very welcome.

There's a configuration file on /dev/mtdblock5 which contains the
device type.  I'm starting to think the easiest solution would be to
mount that device, check the device type and configure qcontrol
accordingly.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#823548: ITP: bubblewrap -- setuid wrapper for unprivileged chroot and namespace manipulation

[Simon McVittie]

Package: wnpp
Severity: wishlist
Owner: Simon McVittie 
Control: affects -1 xdg-app

* Package name: bubblewrap
  Version : (no releases yet)
  Upstream Author : Colin Walters, Alex Larsson
* URL : https://github.com/projectatomic/bubblewrap/
* License : LGPL-2+
  Programming Lang: C
  Description : setuid wrapper for unprivileged chroot and namespace 
manipulation

bubblewrap is a setuid wrapper tool with which unprivileged users can
launch containers, using chroot and various Linux namespace features,
without giving those users access to the full attack surface of user
namespaces.

---

bubblewrap is derived from xdg-app-helper in src:xdg-app, which is itself
derived from linux-user-chroot. The next upstream version of
xdg-app will replace xdg-app-helper with a private copy of bubblewrap as a
git submodule; later versions are intended to use a system copy of
bubblewrap, at least optionally.

When bubblewrap has matured a bit and had some releases, it might make
sense to treat it as superseding linux-user-chroot, possibly with a
transitional package containing a script for command-line compatibility,
so that the overall number of setuid-root things in the archive can
reduce. (linux-user-chroot maintainer in X-Debbugs-Cc)

I intend to maintain this in collab-maint, with pkg-utopia as
the primary maintainer (unless some other team wants it). Co-maintainers
and security audits welcome.

S

Bug#823546: refdb: FTBFS in testing (generating refdb-manual.pdf fails)

[Santiago Vila]

Package: src:refdb
Version: 1.0.2-3
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:

-
Creating PDF manual...
hyphenation temporarily unavailable
xsltproc -o refdb-manual.fo --stringparam hyphenate 0 --nonet --xinclude 
../doc/include/manual-fo.xsl ../doc/refdb-manual
.xml
Making portrait pages on A4 paper (210mmx297mm)
JAVA_OPTS=-Xmx256M fop -fo refdb-manual.fo -pdf refdb-manual.pdf
[ERROR] FOUserAgent - Invalid property value encountered in hyphenate="0": 
org.apache.fop.fo.expr.PropertyException: 
file:/<>/doc/refdb-manual.fo:2:286: No conversion defined 0; 
property:'hyphenate' (See position 2:190720) 
>/doc/refdb-manual.fo:2:286: No conversion defined 0; 
property:'hyphenate'>org.apache.fop.fo.expr.PropertyException: 
file:/<>/doc/refdb-manual.fo:2:286: No conversion defined 0; 
property:'hyphenate'

[...]

Makefile:992: recipe for target 'refdb-manual.pdf' failed
-

The full build log is attached.

Thanks.

refdb_1.0.2-3_amd64-20160505-2238.gz
Description: application/gzip

Bug#823547: clearlooks-phenix-theme: The mecurial vcs listed in the package is not up to date with the latest debian-sources

[Daniel Reurich]

Package: clearlooks-phenix-theme
Version: 6.0.3-1
Severity: normal



-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 1.0 (jessie)
Release:1.0
Codename:   jessie
Architecture: i686

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[Lennart Sorensen]

On Thu, May 05, 2016 at 10:26:18PM +0200, John Paul Adrian Glaubitz wrote:
> Control: tags -1 + patch
> 
> On 05/05/2016 09:32 PM, John Paul Adrian Glaubitz wrote:
> >> If it works, I can submit it to the kernel.  I don't have a powerpcspe
> >> environment to try building it, but I did notice that sstep.o contained
> >> those two instructions when building a ppc32 kernel, and that's wrong.
> >> After the patch those are gone as expected.
> > 
> > I'll test it and let you know.
> 
> I just verified that the patch provided fixes the problem as expected.

I have submitted it upstream.

-- 
Len Sorensen

Bug#823545: anon-proxy: [INTL:nl] Dutch po file for the anon-proxy package

[Frans Spiesschaert]

 

Package: anon-proxy 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch po file for the anon-proxy package. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as "debian/nl.po" in your package build tree. 
=== 
 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#823541: Additional information

[Jon Jahren]

Thanks for the reply!

I have attached information from dmesg, lspci and lsusb in this email if
that is any help. Any other information you need, let me know.

Regards
Jon
[0.00] Linux version 4.5.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 5.3.1 20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 
(2016-04-14)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=baf62f94-62fa-44a3-b3bd-ac371253f3ef ro quiet
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable
[0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xb9bebfff] usable
[0.00] BIOS-e820: [mem 0xb9bec000-0xba760fff] reserved
[0.00] BIOS-e820: [mem 0xba761000-0xba7aefff] ACPI data
[0.00] BIOS-e820: [mem 0xba7af000-0xbc9b2fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbc9b3000-0xbd077fff] reserved
[0.00] BIOS-e820: [mem 0xbd078000-0xbd078fff] usable
[0.00] BIOS-e820: [mem 0xbd079000-0xbd0fefff] reserved
[0.00] BIOS-e820: [mem 0xbd0ff000-0xbd317fff] usable
[0.00] BIOS-e820: [mem 0xbd318000-0xbdff8fff] reserved
[0.00] BIOS-e820: [mem 0xbdff9000-0xbdff] usable
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00043fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.8 present.
[0.00] DMI: ASUS All Series/X99-A, BIOS 1901 08/10/2015
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x44 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-E3FFF write-through
[0.00]   E4000-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base C000 mask 3FFFC000 uncachable
[0.00]   1 base 3800 mask 3FC0 uncachable
[0.00]   2 base BF00 mask 3F00 uncachable
[0.00]   3 base C000 mask 3000 write-through
[0.00]   4 base D000 mask 3E00 write-through
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0xbe000 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at 
[880fd920]
[0.00] Base memory trampoline at [88098000] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x01d33000, 0x01d33fff] PGTABLE
[0.00] BRK [0x01d34000, 0x01d34fff] PGTABLE
[0.00] BRK [0x01d35000, 0x01d35fff] PGTABLE
[0.00] BRK [0x01d36000, 0x01d36fff] PGTABLE
[0.00] BRK [0x01d37000, 0x01d37fff] PGTABLE
[0.00] BRK [0x01d38000, 0x01d38fff] PGTABLE
[0.00] RAMDISK: [mem 0x35fbc000-0x36fd5fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F0540 24 (v02 ALASKA)
[0.00] ACPI: XSDT 0xBA770090 9C (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: FACP 0xBA79F6E0 00010C (v05 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: DSDT 0xBA7701C8 02F515 (v02 ALASKA A M I
01072009 INTL 20091013)
[0.00] ACPI: FACS 0xBC9AFF80 40
[0.00] ACPI: APIC 0xBA79F7F0 000100 (v03 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: FPDT 0xBA79F8F0 44 (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: FIDT 0xBA79F938 9C (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: MCFG 0xBA79F9D8 3C (v01 

Bug#819852: apt-cacher-ng: support by-hash index files

[Eduard Bloch]

Hallo,
* Colin Watson [Tue, Apr 12 2016, 11:40:54AM]:

> The unfortunate thing is that this 404 means that apt switches to its
> fallback behaviour of fetching the old by-name version of the file
> (http://archive.ubuntu.com/ubuntu/dists/xenial/main/source/Sources.xz in
> this case), and since we're already in a situation of skewed mirrors
> this tends to result in a hash sum mismatch as in the bad old days.
> 
> I think we want the default for by-hash files to be that it will try
> other mirrors rather than responding with the 404 from the first one.
> Do you agree, and if so how should that be achieved?

In principle, I agree. There is already a similar mechanism which was
designed to detect a mirror which does not contain the wanted
architecture and therefore rotated the mirror selection to the next
possible one ("key file", see manual).

I will try to make it more generic and detect parts of the path as "key
factor".

Regards,
Eduard.

-- 
Die Kletterer haben den Mount Everest in die höchstgelegene Müllhalde
der Welt verwandelt.
-- Edmund Hillary

Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

[Rene Engelhard]

retitle 823465 New binaries won't run at all on i586 Pentium MMX due to illegal 
instruction
clone 823465 -1
reassign -1 release-notes
reopen -1
retitle -1 Document dropping i586 support
severity -1 important
thanks

On Thu, May 05, 2016 at 10:28:56PM +0200, Rene Engelhard wrote:
> > So are there release notes somewhere? What's the recommended course of
> 
> I don't believe there are, as the release and release notes are still
> a few months away. I believe this WILL be mentioned in the release notes.

Filing a bug wrt that (and reverting your retitling) but I am 100% that would
have happened even without that one.

Regards,
 
Rene

Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

[Rene Engelhard]

On Thu, May 05, 2016 at 06:50:43PM +0200, Pierre Ynard wrote:
> This is my production system and I run a lot of services on it. This

on *unstable*?

> So are there release notes somewhere? What's the recommended course of

I don't believe there are, as the release and release notes are still
a few months away. I believe this WILL be mentioned in the release notes.

> actions? Am I supposed to go ahead with the upgrade, tail the logs and
> eat popcorn while watching them fill with SIGILL?

Again, you use unstable. Your "complaint" would be valid on silent change
in stable - but...

Regards,

Rene

Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

[Neil Williams]

On Thu, 5 May 2016 22:51:47 +0500
Andrey Rahmatullin  wrote:

> On Thu, May 05, 2016 at 06:50:43PM +0200, Pierre Ynard wrote:
> > This is my production system and I run a lot of services on it.  
> You are running sid on your production system, correct?
> 
> > So are there release notes somewhere?   
> I'm sure they will be there in the stretch release notes.

Adding the bug back to CC.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpJCfwyrHVGz.pgp
Description: OpenPGP digital signature

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[John Paul Adrian Glaubitz]

Control: tags -1 + patch

On 05/05/2016 09:32 PM, John Paul Adrian Glaubitz wrote:
>> If it works, I can submit it to the kernel.  I don't have a powerpcspe
>> environment to try building it, but I did notice that sstep.o contained
>> those two instructions when building a ppc32 kernel, and that's wrong.
>> After the patch those are gone as expected.
> 
> I'll test it and let you know.

I just verified that the patch provided fixes the problem as expected.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#823541: debian-installer: Debian installer does not create a bootable system on EFI

[Steve McIntyre]

Hi Jon,

On Thu, May 05, 2016 at 10:01:44PM +0200, Jon Jahren wrote:
>Package: debian-installer
>Severity: important
>
>Dear Maintainer,
>
>When attempting to install Debian testing on an efi system using a nightly
>build because the alpha installer stalls with a systemd dependency, the efi
>partition it creates does not boot, and you have to install in legacy mode to
>get it to boot as normal. The problem with this though, is that the legacy mode
>does not correctly detect other efi installations(e.g Windows).
>
>>From what I gather, after manually mounting the efi system boot after
>installing a legacy boot system, some files are missing. The only file I have
>is grubx64.efi, while for instance an Ubuntu install has:
>grubx64.efi
>shimx64
>MokManager.efi
>grub.cfg
>fwupx64.efi
>fw/

No, the only thing Debian needs (for now) is the grubx64.efi file. If
it's got that far, then the system should be booting; the problem is
more likely to be somewhere else. What hardware do you have, please?

Also: the issue with the systemd dependency has also been fixed for a
while; the latest alpha build is now quite old and you might also be
better using a recent daily or ewwkly build instead.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
You lock the door
And throw away the key
There's someone in my head but it's not me 

Bug#823418: Info received (Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA)

[Marc Haber]

On Thu, May 05, 2016 at 01:15:50PM -0400, hi...@binarystorm.net wrote:
> The only log that I get is
> 2016-05-05 03:23:06 1ayDco-000526-Jn H=(binarystorm.net) [127.0.0.1]
> F= rejected after DATA

try changing:

  denycondition  = ${if > {$max_received_linelength}{998}}


to

  deny
message = Message Header Line to long
condition  = ${if > {$max_received_linelength}{998}}

in /etc/exim4/conf.d/acl/40_exim4-config_check_data and restart exim.
Then wait for the issue to come up again and check your logs again.

Andreas, we should not have any deny stanza in any ACL without an
explicit message.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#823543: Kernel-image-4.5 amd64 does not boot; kernel 4.3 only boots in recovery.

[Jonathan Polak]

Package: src:linux
Version: 4.5.1-1 AND 4.3.5-1
Severity: critical
Justification: breaks the whole system
System type: Lenovo X230
Distro: Debian Testing

I was using kernel 4.3.5-1 because neither kernel 4.4 nor 4.5 booted
normally. (See bug 819597). Between May 2 and May 4 I Upon updating the
following packages ​
 installed_pkgs.txt

​
Upon rebooting on May 5 kernel 4.3 threw a kernel panic and did not boot.
See image in this link:
*​ dump 4.3.pdf
​*


Attempting to boot into kernel 4.5.1-1 also resulted in kernel panic at boot
See image in this link:
 kernel 4.5.pdf

​

 Booting in recovery with kernel 4.5 results in identical kernel panic. ​
 dump 4.5 recovery.pdf

​

The only way to boot was kernel 4.3 recovery. I salvaged the EFI dumps from
the boot fails - they are appended here: ​
 dumpA-4.5.txt

​​
 dumpB-4.5.txt

​A is txt and B is binary. Both were from a failed 4.5 boot.

Bug#823542: imagemagick-common: please mitigate CVE-2016-3714, remote arbitrary code execution during handling of delegates

[Simon McVittie]

Package: imagemagick-common
Version: 8:6.8.9.9-7+b2
Severity: grave
Tags: security
Justification: user security hole

I'm sure you're already aware of
, the most serious
of the recent batch of ImageMagick vulnerabilities published at
.

There does not seem to be a full upstream fix yet, but it seems the
vulnerabilities can be mitigated by altering the policy.xml file in
imagemagick-common. The cost of this mitigation is that some obscure
file formats, and some features that perhaps shouldn't have been
implemented in the first place, are disabled.

Regards,
S

-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
compare:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
convert:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
composite:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
conjure:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
display:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
identify:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
import:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
mogrify:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
montage:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org
stream:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08 http://www.imagemagick.org

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (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.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages imagemagick depends on:
ii  imagemagick-6.q16  8:6.8.9.9-7+b2

imagemagick recommends no packages.

imagemagick suggests no packages.

-- no debconf information

Bug#823540: rustc: Needs versioned binutils dependency

[Olaf Buddenhagen]

Package: rustc
Version: 1.7.0+dfsg1-1
Severity: normal

Dear Maintainer,

Rustc currently only depends on binutils indirectly through gcc -- and doesn't
specify a minimum version of either. However, linking fails with binutils
2.25.1-7:

   Compiling kernel32-sys v0.2.2
error: linking with `cc` failed: exit code: 1
note: "cc" "-Wl,--as-needed" "-m32" "-L" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib" 
"/home/olaf/servo/serde/serde_tests/target/debug/build/kernel32-sys-103730e023e6bbcd/build_script_build.0.o"
 "-o" 
"/home/olaf/servo/serde/serde_tests/target/debug/build/kernel32-sys-103730e023e6bbcd/build_script_build"
 "-Wl,--gc-sections" "-pie" "-nodefaultlibs" "-L" 
"/home/olaf/servo/serde/serde_tests/target/debug/deps" "-L" 
"/home/olaf/servo/serde/serde_tests/target/debug/deps" "-L" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib" "-Wl,-Bstatic" "-Wl,-Bdynamic" 
"/home/olaf/servo/serde/serde_tests/target/debug/deps/libbuild-c5f74941fba769bc.rlib"
 "/usr/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-6a154fe0.rlib" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib/libcollections-6a154fe0.rlib" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib/librustc_unicode-6a154fe0.rlib" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib/librand-6a154fe0.rlib" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib/liballoc-6a154fe0.rlib" "/us
 r/lib/rustlib/i686-unknown-linux-gnu/lib/liballoc_jemalloc-6a154fe0.rlib" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib/liblibc-6a154fe0.rlib" 
"/usr/lib/rustlib/i686-unknown-linux-gnu/lib/libcore-6a154fe0.rlib" "-l" "dl" 
"-l" "pthread" "-l" "gcc_s" "-l" "pthread" "-l" "c" "-l" "m" "-l" "rt" "-l" 
"compiler-rt"
note: /usr/bin/ld: 
/usr/lib/rustlib/i686-unknown-linux-gnu/lib/liballoc_jemalloc-6a154fe0.rlib(jemalloc.pic.o):
 unrecognized relocation (0x2b) in section `.text.malloc_conf_init'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

Upgrading to binutils 2.26-8 solved the issue.

-antrik-

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

Kernel: Linux 4.4.0quad3 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages rustc depends on:
ii  gcc   4:5.2.1-4
ii  libc6 2.19-22
ii  libc6-dev [libc-dev]  2.19-22
ii  libstd-rust-dev   1.7.0+dfsg1-1

Versions of packages rustc recommends:
ii  rust-gdb  1.3.0+dfsg1-1

Versions of packages rustc suggests:
pn  rust-doc  

-- no debconf information

Bug#823541: debian-installer: Debian installer does not create a bootable system on EFI

[Jon Jahren]

Package: debian-installer
Severity: important

Dear Maintainer,

When attempting to install Debian testing on an efi system using a nightly
build because the alpha installer stalls with a systemd dependency, the efi
partition it creates does not boot, and you have to install in legacy mode to
get it to boot as normal. The problem with this though, is that the legacy mode
does not correctly detect other efi installations(e.g Windows).

>From what I gather, after manually mounting the efi system boot after
installing a legacy boot system, some files are missing. The only file I have
is grubx64.efi, while for instance an Ubuntu install has:
grubx64.efi
shimx64
MokManager.efi
grub.cfg
fwupx64.efi
fw/

I tried copying some of the files over to the debian folder and edit the
grub.cfg file, but it didn't have any effect.

Any help greatly appreciated.

Regards
Jon



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

Kernel: Linux 4.5.0-1-amd64 (SMP w/12 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)

Bug#822288: #822288: dh --buildsystem=ruby ignores hardening=+bindnow

[Christian Hofstaedtler]

* Antonio Terceiro  [160505 21:53]:
> Control: reassign -1 libruby2.3
> 
> On Sat, Apr 23, 2016 at 04:35:54PM +0200, Christian Hofstaedtler wrote:
> > Control: reassign -1 gem2deb
> > 
> > Reassigning to gem2deb, which is what provides the ruby buildsystem.
> > Anybody building with mkmf/extconf without ruby buildsystem is on
> > their own.
> > 
> > As a datapoint, mkmf understands --with-cflags="--something" and
> > similar for --with-ldflags.
> 
> actually, as extensions are compiled using the same flags as were used
> to compile Ruby itself, it makes sense to "fix" this in src:ruby2.3 (as
> we also want the binaries built by it to be built with bindnow).

Right, but the "fix" in ruby2.3 will be to build libruby with
bindnow (which appears to be harder than expected).

> Making gem2deb correctly use dpkg-buildflags and pass the flags there
> down to the Ruby extension build is also useful, and is tracked in
> #722154

That's what would help ruby-rrd right now, too.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#822288: #822288: dh --buildsystem=ruby ignores hardening=+bindnow

[Antonio Terceiro]

Control: reassign -1 libruby2.3

On Sat, Apr 23, 2016 at 04:35:54PM +0200, Christian Hofstaedtler wrote:
> Control: reassign -1 gem2deb
> 
> Reassigning to gem2deb, which is what provides the ruby buildsystem.
> Anybody building with mkmf/extconf without ruby buildsystem is on
> their own.
> 
> As a datapoint, mkmf understands --with-cflags="--something" and
> similar for --with-ldflags.

actually, as extensions are compiled using the same flags as were used
to compile Ruby itself, it makes sense to "fix" this in src:ruby2.3 (as
we also want the binaries built by it to be built with bindnow).

Making gem2deb correctly use dpkg-buildflags and pass the flags there
down to the Ruby extension build is also useful, and is tracked in
#722154


signature.asc
Description: PGP signature

Bug#823539: RFS: aggressive-indent-mode/1.7-1 -- Emacs minor mode that reindents code after every change

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update to aggressive-indent-mode.

* Package name: aggressive-indent-mode
  Version : 1.7-1
  Upstream Author : Artur Malabarba 
* URL : https://github.com/Malabarba/aggressive-indent-mode
* License : GPL-2+
  Section : lisp

Changes since the last upload:

  * Package new upstream release.

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/a/aggressive-indent-mode/aggressive-indent-mode_1.7-1.dsc

Or build it with gbp:

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

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#823538: RFS: classic-theme-restorer/1.5.1-1 -- customize the new Firefox look

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a new release of classic-theme-restorer.

* Package name: classic-theme-restorer
  Version : 1.5.1-1
  Upstream Author : Aris 
* URL : https://github.com/Aris-t2/ClassicThemeRestorer
* License : MPL-2.0
  Section : web

Changes since the last upload:

  * Package new upstream version.

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/c/classic-theme-restorer/classic-theme-restorer_1.5.1-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-mozext/classic-theme-restorer.git
git checkout debian/1.5.1-1
git verify-tag debian/1.5.1-1 # if you have my key
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#823537: ITP: ruby-algebrick -- Ruby library for algebraic type definition and pattern matching

[Michael Moll]

Package: wnpp
Severity: wishlist

I'm packaging this in pkg-ruby-extras

Bug#786658: quota: Cannot install quota package on a jessie system

[cep]

On Sun, 20 Mar 2016 09:13:32 +0100 Simone Rossetto  
wrote:


>
> Step 1: enable quota on filesystems.
> I edited /etc/fstab adding, to any partition I want to monitor, the 
following
> settings "usrjquota=aquota.user,jqfmt=vfsv0" (I choose only user 
quota, but

> adding group quota makes no difference)
>
> Step 2: remount filesystems.
> "mount -o remount /mountpoint" for any mountpoint just edited in 
/etc/fstab

>
> Step 3: install quota "aptitude install quota"
> On jessie it fails with the error I already reported, on stretch the
> installation
> completes without errors but the quota is not enabled and on reboot 
no quota

> still present.
>
> To solve the issue I have to stop quota.service, exec "quotacheck 
-cau" and,

> on jessie, disable and mask quotaon.service. Then reboot the system.
>
>
> Bye
> Simone


I confirm.

Paramétrage de quota (4.01-8) ...
Job for quota.service failed. See 'systemctl status quota.service' and 
'journalctl -xn' for details.

invoke-rc.d: initscript quota, action "start" failed.
dpkg: erreur de traitement du paquet quota (--configure) :

And the method of Simone is ok

:~# systemctl stop quota.service
:~# quotacheck -cau
:~# systemctl start quota.service
:~# systemctl enable quota

cep

Bug#823535: requires manual setup to get required capabilities

[Simon McVittie]

Control: retitle 823535 requires manual setup to get required capabilities

On Thu, 05 May 2016 at 21:17:35 +0200, antistress wrote:
> No permissions to creating new namespace, likely because the kernel does not
> allow non-privileged user namespaces. On e.g. debian this can be enabled
> with 'sysctl kernel.unprivileged_userns_clone=1'."
> 
> Then I had to manually key "sysctl kernel.unprivileged_userns_clone=1"

See xdg-app's README.Debian for other possible solutions to getting the
required privileges. I should probably patch this message to point
users to the README.Debian instead of giving a specific command.

> I don't think that user should be bother with that.

No, they shouldn't, but none of the possible solutions is unambiguously
correct: they all lead to additional security exposure. This is one of
the reasons why xdg-app is only available in the experimental suite
at the moment.

If you are not able to make informed decisions about the security
implications of code that you run as root, I would recommend not using
packages from experimental. xdg-app would be in unstable if I thought
it was ready; right now, it isn't.

I'm hoping that bubblewrap, which was recently spun out from xdg-app
(),
will improve on this by being a self-contained and easy-to-audit version
of the part of xdg-app that requires privileges (and in fact I was just
about to file the ITP for it).

(bubblewrap is very similar to the solution involving making
/usr/bin/xdg-app-helper setuid root.)

S

Bug#798102: ams: Lots of kworker activity after wake from hibernate on Powerbook

[Michael Hanselmann]

Hello Dan and Mathieu

On 18.04.2016 18:17, Michael Hanselmann wrote:
> Fortunately I still have two devices with the two variants of the
> sensor. I'm not able to look into this in more detail before early May,
> but then I will try to spin up the hardware and reproduce the issue.

I spent an afternoon trying to debug this issue on a PowerBook5,8 with
Debian Jessie and did not succeed. Suspend doesn't work at all and
hibernation seldomly works, with both Linux 3.16.7-ckt25-2 and
4.5.1-1~bpo8+1. I didn't have more time to look into the actual issue
with the ams driver.

What I can confirm, however, is that the sensor's values can be read
from /sys/devices/platform/ams/current. “jstest” from the joystick
package did not work as it seems to be incompatible with the kernel
interface.

I'll be happy to review any patches, but can't be of much more help at
this time, unfortunately. I've noticed that I'm still listed as the
driver's maintainer and will send a patch to mark it orphaned soon.

Michael



signature.asc
Description: OpenPGP digital signature

Bug#805200: gip: FTBFS: dispatcher.h: fatal error: sigc++/class_slot.h: No such file or directory

[Logan Rosen]

Package: gip
Version: 1.7.0-1-3
Followup-For: Bug #805200
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/70-remove-header.diff: Remove include to fix FTBFS with
newer libsigc++.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru gip-1.7.0-1/debian/patches/70-remove-header.diff gip-1.7.0-1/debian/patches/70-remove-header.diff
--- gip-1.7.0-1/debian/patches/70-remove-header.diff	1969-12-31 19:00:00.0 -0500
+++ gip-1.7.0-1/debian/patches/70-remove-header.diff	2015-12-28 10:44:35.0 -0500
@@ -0,0 +1,16 @@
+Description: remove include to fix FTBFS with newer libsigc++
+Author: Logan Rosen 
+Forwarded: no
+Last-Update: 2016-01-05
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/dispatcher.h
 b/src/dispatcher.h
+@@ -23,7 +23,6 @@
+ #ifndef HAVE_DISPATCHER_H
+ #define HAVE_DISPATCHER_H
+ 
+-#include 
+ #include "gui_mainwindow.h"
+ #include "lib_ipv4.h"
+ 
diff -Nru gip-1.7.0-1/debian/patches/series gip-1.7.0-1/debian/patches/series
--- gip-1.7.0-1/debian/patches/series	2011-11-19 18:07:08.0 -0500
+++ gip-1.7.0-1/debian/patches/series	2015-12-28 10:07:09.0 -0500
@@ -4,3 +4,4 @@
 40-init_lock_events.diff
 50-installer-build_files-sh.diff
 60-binary-hex-network-update.diff
+70-remove-header.diff

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[Lennart Sorensen]

On Thu, May 05, 2016 at 06:59:33PM +0200, John Paul Adrian Glaubitz wrote:
> Source: linux
> Version: 4.5.2-1
> Severity: normal
> User: debian-powe...@lists.debian.org
> Usertags: powerpcspe
> 
> Hi!
> 
> linux currently fails to build from source on powerpcspe since the compiler
> is using FPU instructions which are not available on the e500v2 CPUs [1,2]:
> 
> {standard input}: Assembler messages:
> {standard input}:2227: Error: unrecognized opcode: `ldarx'
> {standard input}:2274: Error: unrecognized opcode: `stdcx.'
> /<>/scripts/Makefile.build:263: recipe for target 
> 'arch/powerpc/lib/sstep.o' failed
> make[6]: *** [arch/powerpc/lib/sstep.o] Error 1
> /<>/Makefile:954: recipe for target 'arch/powerpc/lib' failed
> make[5]: *** [arch/powerpc/lib] Error 2
> make[5]: *** Waiting for unfinished jobs
> 
> Looking at arch/powerpc/lib/sstep.c, there are actually #ifdefs for the 
> CONFIG_PPC_FPU,
> however, it seems there is no way of manually setting CONFIG_PPC_FPU in the 
> kernel
> configuration. I assume, this is done by choosing a certain type of PowerPC 
> hardware.
> 
> In any case, version 3.16.7 still builds fine [3], so this is a regression 
> either
> way. Although we currently have to use a custom kernel for our e500v2 boards
> anyway, it's still desirable to fix any build issues with the kernel package
> on powerpcspe.

Doing this seems to agree:

objdump -d arch/powerpc/lib/sstep.o | grep ldarx
1f0c:   7f 80 e0 a8 ldarx   r28,0,r28

objdump -d arch/powerpc/lib/sstep.o -M 603| grep 1f0c:
1f0c:   7f 80 e0 a8 .long 0x7f80e0a8

And similarly for:

objdump -d arch/powerpc/lib/sstep.o |grep stdcx
1f78:   7d 40 e1 ad stdcx.  r10,0,r28

objdump -d arch/powerpc/lib/sstep.o -M 603 |grep 1f78:
1f78:   7d 40 e1 ad .long 0x7d40e1ad



Going through the list of machine types in objdump I see:

ldarx invalid:
403, 405, 440, 464, 476, 601, 603, 604, 7400, 7410, 7450, 7455, 750cl, 
ppcps, pwr, pwr2, booke, booke32, com, e300, e500, e500mc, e500x2, efs,
ppc, ppc32, pwrx, titan

ldarx valid:
a2, altivec, any, cell, e500mc64, e5500, e6500, power4, power5, power6, 
power7, power8, ppc64, ppc64bridge, pwr4, pwr5, pwr5x, pwr6, pwr7, pwr8,
spe, vle, vsx, htm, 32, 64, 620

So that seems to agree with IBM
https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjr-5rO1cPMAhXMyRoKHd3fBTUQFggbMAA&url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fssw_aix_53%2Fcom.ibm.aix.aixassem%2Fdoc%2Falangref%2Fldarx.htm&usg=AFQjCNF1n3feBCinAC3RjBJy81zCYBES7Q&bvm=bv.121099550,d.d2s
saying ldarx is only to be used in 64 bit mode on a 64 bit powerpc.

-- 
Len Sorensen

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[John Paul Adrian Glaubitz]

On 05/05/2016 09:01 PM, Lennart Sorensen wrote:
> I think this would fix it:
> (...)

Good idea, I'll give that a try!

> It seems that gas on powerpc is willing to accept ldarx and stdcx even
> when compiling in 32 bit mode (even though the instructions are not
> allowed in 32 bit mode), while gas for powerpcspe does not seem willing
> to accept them.  So they need to be left out when building on 32 bit
> systems, just like everywhere else in that file already did.

Indeed. And ldarx and stdcx are definitely not available on e500,
according to the datasheet by NXP.

> If it works, I can submit it to the kernel.  I don't have a powerpcspe
> environment to try building it, but I did notice that sstep.o contained
> those two instructions when building a ppc32 kernel, and that's wrong.
> After the patch those are gone as expected.

I'll test it and let you know.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#821482: drupal7: PHP 7.0 Transition ← Help requested!

[Gunnar Wolf]

tag 821482 + confirmed upstream patch pending
thanks

Hi,

I'm contacting pkg-php-maint as recommendad by Ondřej's original mass
bug filing, hopefully avoiding the removal of Drupal7 from Debian.

As it is now, at version 7.43, Drupal7 is *not* PHP7-clean, and it is
documented with bugs in the upstream tracker:

https://www.drupal.org/node/2656548 — Drupal 7 PHP 7 testing issue
https://www.drupal.org/node/2454439 — [META] Support PHP 7

Following the first link to the bottom, it *seems* that, three days
ago, Mike Carper achieved a clean test run on PHP7:

https://dispatcher.drupalci.org/job/default/124946/testReport/

The patch in question:

https://www.drupal.org/files/issues/drupal-2656548-21-php7.patch

Now, the reason to contact pkg-php-maint... Even though I maintain
Drupal7 for a long time, I do consider myself a PHP newbie. Could you
help me ascertain iv the patch makes linguistic sense in PHP7? Help me
check if this looks like enough, and without changing the logic?

I gave a *very* quick look at it, and the patch looks much shorter
than what I expected. I don't know the extent of the language
incompatibilities between 5.6 and 7, but if this works, I will be a
very happy maintainer.

I have created a "php7" branch in the packaging repository; I have not
built the package yet, but it should be doable trivially:

https://anonscm.debian.org/cgit/collab-maint/drupal7.git/commit/?h=php7

I intend to do as much testing as I can, but any help is welcome. I am
quite time-stressed, and don't want to delay this until I got time to
dig into it.

Thanks a lot!


signature.asc
Description: Digital signature

Bug#800260: argus-client: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: argus-client
Version: 2.0.6.fixes.1-3
Followup-For: Bug #800260
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
  * debian/{dirs,lintian,rules}: Remove now unnecessary Lintian override.
  * debian/rules:
- Don't allow clean to ignore errors.
- Install files into debian/argus-client instead of debian/tmp.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
reverted:
--- argus-client-2.0.6.fixes.1/debian/dirs
+++ argus-client-2.0.6.fixes.1.orig/debian/dirs
@@ -1 +0,0 @@
-usr/share/lintian/overrides
diff -u argus-client-2.0.6.fixes.1/debian/control argus-client-2.0.6.fixes.1/debian/control
--- argus-client-2.0.6.fixes.1/debian/control
+++ argus-client-2.0.6.fixes.1/debian/control
@@ -3,12 +3,12 @@
 Priority: optional
 Maintainer: Andrew Pollock 
 Standards-Version: 3.6.1
-Build-depends: bison, flex, debhelper, devscripts, autotools-dev, libncurses5-dev, dpatch
+Build-depends: bison, flex, debhelper (>= 9), devscripts, autotools-dev, libncurses5-dev, dpatch
 
 Package: argus-client
 Architecture: any
 Recommends: argus-server
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Suggests: librrds-perl
 Description: IP network transaction auditing tool
  argus is a network transaction auditing tool that allows the user
diff -u argus-client-2.0.6.fixes.1/debian/rules argus-client-2.0.6.fixes.1/debian/rules
--- argus-client-2.0.6.fixes.1/debian/rules
+++ argus-client-2.0.6.fixes.1/debian/rules
@@ -25,7 +25,7 @@
 INSTALL_PROGRAM += -s
 endif
 
-tmp = debian/tmp
+packagedir = debian/argus-client
 sysconfdir = etc
 docdir = usr/share/doc
 mandir = usr/share/man
@@ -65,8 +65,8 @@
 clean: unpatch checkroot
 	test -f debian/control
 	rm -f build-stamp
-	rm -rf $(tmp) $(tmp-ALT) debian/substvars debian/files *.orig */*.orig *~ */*~
-	-$(MAKE) -f Makefile.in realclean ALLDIRS="clients common server"
+	rm -rf $(packagedir) $(tmp-ALT) debian/substvars debian/files *.orig */*.orig *~ */*~
+	$(MAKE) -f Makefile.in realclean ALLDIRS="clients common server"
 
 checkroot:
 	test root = "`whoami`" || (echo Need root privelages; exit 1)
@@ -97,74 +97,66 @@
 	# Generate argus-client package.
 	#
 	
-	$(INSTALL_DIR) $(tmp)/$(sysconfdir)
-	$(INSTALL_DIR) $(tmp)/DEBIAN
-	$(INSTALL_DIR) $(tmp)/$(bindir)
-	$(INSTALL_DIR) $(tmp)/{$(mandir),$(bindir)}
-	$(INSTALL_DIR) $(tmp)/$(mandir)/{man1,man5}
-	$(INSTALL_DIR) $(tmp)/$(docdir)/$(PACKAGE)/{examples,html}
+	$(INSTALL_DIR) $(packagedir)/$(sysconfdir)
+	$(INSTALL_DIR) $(packagedir)/DEBIAN
+	$(INSTALL_DIR) $(packagedir)/$(bindir)
+	$(INSTALL_DIR) $(packagedir)/{$(mandir),$(bindir)}
+	$(INSTALL_DIR) $(packagedir)/$(mandir)/{man1,man5}
+	$(INSTALL_DIR) $(packagedir)/$(docdir)/$(PACKAGE)/{examples,html}
 
 	#
 	# Install documentation.
 	#
 	
 	$(INSTALL_FILE) doc/{HOW-TO,FAQ} \
-	$(tmp)/$(docdir)/$(PACKAGE)
-	cp -a support/* $(tmp)/$(docdir)/$(PACKAGE)/examples
-	chmod 644 $(tmp)/$(docdir)/$(PACKAGE)/examples/*
-	chmod 755 $(tmp)/$(docdir)/$(PACKAGE)/examples/{Xml,Config,Tools,Archive,System}
-	chmod 644 $(tmp)/$(docdir)/$(PACKAGE)/examples/README
-	chmod 644 $(tmp)/$(docdir)/$(PACKAGE)/examples/Config/policy.conf
-	$(INSTALL_FILE) man/man5/ra* $(tmp)/$(mandir)/man5
-	$(INSTALL_FILE) man/man1/ra* $(tmp)/$(mandir)/man1
+	$(packagedir)/$(docdir)/$(PACKAGE)
+	cp -a support/* $(packagedir)/$(docdir)/$(PACKAGE)/examples
+	chmod 644 $(packagedir)/$(docdir)/$(PACKAGE)/examples/*
+	chmod 755 $(packagedir)/$(docdir)/$(PACKAGE)/examples/{Xml,Config,Tools,Archive,System}
+	chmod 644 $(packagedir)/$(docdir)/$(PACKAGE)/examples/README
+	chmod 644 $(packagedir)/$(docdir)/$(PACKAGE)/examples/Config/policy.conf
+	$(INSTALL_FILE) man/man5/ra* $(packagedir)/$(mandir)/man5
+	$(INSTALL_FILE) man/man1/ra* $(packagedir)/$(mandir)/man1
 	$(INSTALL_FILE) debian/README.Debian \
-	 $(tmp)/$(docdir)/$(PACKAGE)/README.Debian
+	 $(packagedir)/$(docdir)/$(PACKAGE)/README.Debian
 	$(INSTALL_FILE) debian/copyright \
-	$(tmp)/$(docdir)/$(PACKAGE)/copyright
-	$(INSTALL_FILE) doc/CHANGES "$(tmp)/$(docdir)/$(PACKAGE)"
-	$(INSTALL_FILE) CREDITS "$(tmp)/$(docdir)/$(PACKAGE)"
+	$(packagedir)/$(docdir)/$(PACKAGE)/copyright
+	$(INSTALL_FILE) doc/CHANGES "$(packagedir)/$(docdir)/$(PACKAGE)"
+	$(INSTALL_FILE) CREDITS "$(packagedir)/$(docdir)/$(PACKAG

Bug#823535: Installing Pitivi daily with xdg-app require the user to manually key 'sysctl kernel.unprivileged_userns_clone=1'

[antistress]

Package: xdg-app
Version: 0.5.0-1

Hi,
Following these instructions to install Pitivi daily bundle through 
xdg-app [1], I got this in my terminal :



"-> Updating org.gnome.Platform 3.20

1 metadata, 0 content objects fetched; 313 B transferred in 3 seconds
-> Updating org.gnome.Platform.Locale

1 metadata, 0 content objects fetched; 313 B transferred in 3 seconds
-> Updating org.pitivi.Pitivi master...


No permissions to creating new namespace, likely because the kernel does 
not allow non-privileged user namespaces. On e.g. debian this can be 
enabled with 'sysctl kernel.unprivileged_userns_clone=1'."


Then I had to manually key "sysctl kernel.unprivileged_userns_clone=1"

I don't think that user should be bother with that.

FWIW I'm running Linux HAL 4.5.0-2-amd64 #1 SMP Debian 4.5.2-1 
(2016-04-28) x86_64 GNU/Linux & libc6 2.22-7


Thanks !

[1] http://wiki.pitivi.org/wiki/Install_with_xdg-app

Bug#823536: git-phab: FTBFS without Internet connection

[Logan Rosen]

Package: git-phab
Version: 0~git20160322-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

The buildds for Ubuntu don't have network access since a package shouldn't
depend on an Internet resource to build properly. git-phab currently FTBFS
without an Internet connection during the documentation generation due to a
missing stylesheet.

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on docbook-xsl to fix FTBFS while offline.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru git-phab-0~git20160322/debian/control git-phab-0~git20160322/debian/control
--- git-phab-0~git20160322/debian/control	2016-03-25 08:01:24.0 -0400
+++ git-phab-0~git20160322/debian/control	2016-05-05 15:06:52.0 -0400
@@ -8,7 +8,8 @@
  asciidoc,
  libxml2-utils,
  docbook-xml,
- xsltproc
+ xsltproc,
+ docbook-xsl
 Standards-Version: 3.9.7
 Homepage: https://phabricator.freedesktop.org/diffusion/GITPHAB/
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/git-phab.git

Bug#823526: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[Lennart Sorensen]

On Thu, May 05, 2016 at 06:59:33PM +0200, John Paul Adrian Glaubitz wrote:
> Source: linux
> Version: 4.5.2-1
> Severity: normal
> User: debian-powe...@lists.debian.org
> Usertags: powerpcspe
> 
> Hi!
> 
> linux currently fails to build from source on powerpcspe since the compiler
> is using FPU instructions which are not available on the e500v2 CPUs [1,2]:
> 
> {standard input}: Assembler messages:
> {standard input}:2227: Error: unrecognized opcode: `ldarx'
> {standard input}:2274: Error: unrecognized opcode: `stdcx.'
> /<>/scripts/Makefile.build:263: recipe for target 
> 'arch/powerpc/lib/sstep.o' failed
> make[6]: *** [arch/powerpc/lib/sstep.o] Error 1
> /<>/Makefile:954: recipe for target 'arch/powerpc/lib' failed
> make[5]: *** [arch/powerpc/lib] Error 2
> make[5]: *** Waiting for unfinished jobs
> 
> Looking at arch/powerpc/lib/sstep.c, there are actually #ifdefs for the 
> CONFIG_PPC_FPU,
> however, it seems there is no way of manually setting CONFIG_PPC_FPU in the 
> kernel
> configuration. I assume, this is done by choosing a certain type of PowerPC 
> hardware.
> 
> In any case, version 3.16.7 still builds fine [3], so this is a regression 
> either
> way. Although we currently have to use a custom kernel for our e500v2 boards
> anyway, it's still desirable to fix any build issues with the kernel package
> on powerpcspe.

I think this would fix it:

diff --git a/arch/powerpc/lib/sstep.c b/arch/powerpc/lib/sstep.c
index dc885b3..6d34310 100644
--- a/arch/powerpc/lib/sstep.c
+++ b/arch/powerpc/lib/sstep.c
@@ -1818,9 +1818,11 @@ int __kprobes emulate_step(struct pt_regs *regs, 
unsigned int instr)
case 4:
__get_user_asmx(val, op.ea, err, "lwarx");
break;
+#ifdef __powerpc64__
case 8:
__get_user_asmx(val, op.ea, err, "ldarx");
break;
+#endif
default:
return 0;
}
@@ -1841,9 +1843,11 @@ int __kprobes emulate_step(struct pt_regs *regs, 
unsigned int instr)
case 4:
__put_user_asmx(op.val, op.ea, err, "stwcx.", cr);
break;
+#ifdef __powerpc64__
case 8:
__put_user_asmx(op.val, op.ea, err, "stdcx.", cr);
break;
+#endif
default:
return 0;
}

It seems that gas on powerpc is willing to accept ldarx and stdcx even
when compiling in 32 bit mode (even though the instructions are not
allowed in 32 bit mode), while gas for powerpcspe does not seem willing
to accept them.  So they need to be left out when building on 32 bit
systems, just like everywhere else in that file already did.

If it works, I can submit it to the kernel.  I don't have a powerpcspe
environment to try building it, but I did notice that sstep.o contained
those two instructions when building a ppc32 kernel, and that's wrong.
After the patch those are gone as expected.

-- 
Len Sorensen