Bug#814131: marked as done (php-pager: Needs an update for PHP 7.0)

[Debian Bug Tracking System]

Your message dated Sun, 15 May 2016 04:54:49 +
with message-id 
and subject line Bug#824247: Removed package(s) from unstable
has caused the Debian Bug report #814131,
regarding php-pager: Needs an update for PHP 7.0
to be marked as done.

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

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


-- 
814131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-pager
Version: 2.4.8-3
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-pager is only used by php-structures-datagrid-renderer-pager, but
it’s going away (#804904, #814108). There has been a new upstream
release five years after the version currently in Debian, but since it
has a low (and shrinking) popcon, it probably isn’t of any use anymore.
There is a priori little point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.4.8-3+rm

Dear submitter,

as the package php-pager has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/824247

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#824367: flashplugin-nonfree: installation fails with "ERROR: failed to get upstream version"

[jerojasro]

On Sat, May 14, 2016 at 09:37:18PM -0500, Javier Eduardo Rojas Romero wrote:
> Package: flashplugin-nonfree
> Version: 1:3.6.1+b1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable

After playing a bit with the issue, I noticed that the Flash installation fails
because the script that gets the current upstream version number times out
while trying to download Adobe's main page. Increasing the timeout of the wget
command used (line 37, get-upstream-version.pl) fixed the issue.

Also, this is not grave, as it only affects users with really lousy Internet
connections.

Bug#824367: flashplugin-nonfree: installation fails with "ERROR: failed to get upstream version"

[Javier Eduardo Rojas Romero]

Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Hello,

"apt-get install flashplugin-nonfree" fails with the following message:

failed to read http://www.adobe.com/ at get-upstream-version.pl line 48.
ERROR: failed to get upstream version
More information might be available at:
  http://wiki.debian.org/FlashPlayer

It seems to me the script (get-upstream-version.pl) needs an update to
deal with Adobe's current version of its website. But I'm not the expert
here :)


-- Package-specific info:
Debian version: stretch/sid
Architecture: amd64
Package version: 1:3.6.1+b1
MD5 checksums:
md5sum: '/var/cache/flashplugin-nonfree/*': No such file or directory
md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or 
directory
Alternatives:
update-alternatives: error: no alternatives for flash-mozilla.so
ls: cannot access '/usr/lib/mozilla/plugins/flash-mozilla.so': No such 
file or directory
/usr/lib/mozilla/plugins/flash-mozilla.so: cannot open 
`/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory)

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.26-8
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.59
ii  gnupg  1.4.20-6
ii  libatk1.0-02.20.0-1
ii  libcairo2  1.14.6-1+b1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libgcc11:5.3.1-14
ii  libglib2.0-0   2.48.0-1
ii  libgtk2.0-02.24.30-1.1
ii  libnspr4   2:4.12-2
ii  libnss32:3.23-2
ii  libpango1.0-0  1.40.1-1
ii  libstdc++6 5.3.1-14
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.17.1-1+b1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.35-1
pn  hal
ii  iceweasel  45.0.2esr-1
pn  konqueror-nsplugins
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information

Processed: Re: Bug#824074: gimp: Crashes (apparently) when Caps Lock key is pressed

[Debian Bug Tracking System]

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

> severity 824074 important
Bug #824074 [gimp] gimp: Crashes (apparently) when Caps Lock key is pressed
Severity set to 'important' from 'grave'
> forwarded 824074 https://bugzilla.gnome.org/show_bug.cgi?id=648419
Bug #824074 [gimp] gimp: Crashes (apparently) when Caps Lock key is pressed
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=648419'.
> reassign 824074 libgtk2.0-0 2.24.30-1.1
Bug #824074 [gimp] gimp: Crashes (apparently) when Caps Lock key is pressed
Bug reassigned from package 'gimp' to 'libgtk2.0-0'.
No longer marked as found in versions gimp/2.8.16-1.
Ignoring request to alter fixed versions of bug #824074 to the same values 
previously set
Bug #824074 [libgtk2.0-0] gimp: Crashes (apparently) when Caps Lock key is 
pressed
Marked as found in versions gtk+2.0/2.24.30-1.1.
> tags 824074 +fixed-upstream
Bug #824074 [libgtk2.0-0] gimp: Crashes (apparently) when Caps Lock key is 
pressed
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Bug#824260: [tlbuild] texlive build failures on Debian - upmendex

[Karl Berry]

Do you think (or AKira) that this is the problem for mips?
For sparc I am a bit stymed.

Yes, it's all about BigEndian architectures (and ICU and upmendex).
(And don't bother explaining that sparc is endian-neutral, the practical
reality is that it is still bigendian in our world.)

And the -DU_IS_BIG_ENDIAN=0 kludge I found is a big pain and I wish
someone, anyone, could find the real bug and the real fix.  (For next
year.)  I can't go there again.

Another approach, simpler and just as viable IMHO, would be (I assume)
--disable-upmendex :).  --karl

Bug#821665: marked as done (tweeper: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 22:27:44 +
with message-id 
and subject line Bug#821665: fixed in tweeper 0.5-1
has caused the Debian Bug report #821665,
regarding tweeper: PHP 7.0 Transition
to be marked as done.

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

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


-- 
821665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tweeper
Version: 0.4-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The tweeper package currently depends on php5 php5-cli php5-curl
php5-xsl .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut&paste since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: tweeper -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUrlXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHPlQQAO38dPtgeYCBQuOwCRSwP+fj
GcOXm6oeQv6KK1QGyFBkMqTxHl0BZCLWmWWlqe5THbKcNxNfGx6C7ZjuZJkJ6IF9
+uACRnK+ILab8JBF0KwTKmQgNXLAClu8c5VDUjS4WzvOUEx+BM05A8+VbI9YCyHH
Ej0fTMJXYSzVxoR5NmauB9yAW0TYLAqvvaGAb9WhxPNJthPOWr+09LkN7yCzp2Vn
9jJjr3u1l2xPVqcFBFobPYE0/O3MBCLwV0VYFz4JAARRpZJWZrT4DZeyylbCRSHZ
B4JZXqBBnhnI3I9uluRnxBNQ6iEla+ezVG2cxVPLwQd8StwEw

Processed: tagging 330695

[Debian Bug Tracking System]

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

> tags 330695 + pending
Bug #330695 [libldap-2.4-2] libldap2: /etc/ldap/ldap.conf breaks multiarch and 
on soname change
Bug #507225 [libldap-2.4-2] libldap-2.4-2: /etc/ldap/ldap.conf went missing 
during install
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824352: lambdabot: FTBFS Expecting one more argument to `DSum Config'

[Ralf Treinen]

Source: lambdabot
Version: 5.0.3-3
Severity: serious

Hello,

even though build-dependencies of lambdabot are now satisfied, it 
FTBFS now at least on arm64, armel, i386, powerpc, ppc64el, s390x
on the autobuilders:

[3 of 3] Compiling Main ( src/Main.hs, 
dist-ghc/build/lambdabot/lambdabot-tmp/Main.o )

src/Main.hs:20:25:
Expecting one more argument to `DSum Config'
The first argument of `IO' should have kind `*',
  but `DSum Config' has kind `(* -> *) -> *'
In the type signature for `flags':
  flags :: [OptDescr (IO (DSum Config))]
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1

-Ralf.

Bug#824347: patches from philp

[Antoine Beaupré]

Actually, I was wondering how this could possibly be working at all, and
I looked at the deployed instance on debian.org. It turns out there's a
patch sitting there, uncommitted:

anarcat@philp:/srv/planet.debian.org/code/venus$ git diff
diff --git a/planet/shell/dj.py b/planet/shell/dj.py
index d2199fc..f26b8da 100644
--- a/planet/shell/dj.py
+++ b/planet/shell/dj.py
@@ -19,7 +19,7 @@ def run(script, doc, output_file=None, options={}):
 # I need to re-import the settings at every call because I have to 
 # set the TEMPLATE_DIRS variable programmatically
 from django.conf import settings
-settings._wrapped=None
+#settings._wrapped=None
 try:
 settings.configure(
 DEBUG=True, TEMPLATE_DEBUG=True, 
@@ -27,6 +27,11 @@ def run(script, doc, output_file=None, options={}):
 )
 except EnvironmentError:
 pass
+except RuntimeError:
+settings.TEMPLATE_DIRS=(os.path.dirname(script),)
+
+import django
+django.setup()
 from django.template import Context
 from django.template.loader import get_template
 
Maybe those 2 (3?) chunks are unrelated but they are certainly relevant
in the discussion here!

A.

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of speech
because I have nothing to say."
- Edward Snowden

Bug#821501: make gosa packages php7 compliant

[Wolfgang Schweer]

While testing gosa in a php7 only environment I found out that these 
changes were needed to get the GOsa² gui working for stretch:



diff --git a/debian/control b/debian/control
index 37ac4ab..649b6c4 100644
--- a/debian/control
+++ b/debian/control
@@ -20,21 +20,22 @@ Depends:
  exim4 | mail-transport-agent,
  fonts-liberation,
  gettext,
- libapache2-mod-php5 | php5-cgi | php5-fpm,
  libcrypt-smbhash-perl,
  libjs-scriptaculous,
- php5,
- php5-cli,
- php5-curl,
- php5-gd,
- php5-imagick | imagemagick (>= 5.4.4.5-1) | graphicsmagick-im-compat,
- php5-imap,
- php5-ldap,
- php5-mcrypt,
- php5-mysqlnd | php5-mysql,
- php5-recode,
+ php,
+ php-xml,
+ php-cli,
+ php-curl,
+ php-gd,
+ php-imagick | imagemagick | graphicsmagick-im-compat,
+ php-imap,
+ php-ldap,
+ php-mbstring,
+ php-mcrypt,
+ php-mysqlnd | php-mysql,
+ php-recode,
  smarty-gettext,
- smarty3 (>= 3.1.10-1),
+ smarty3,
  ${misc:Depends},
 Suggests:
  cyrus21-imapd (>= 2.1.11),
@@ -42,7 +43,7 @@ Suggests:
  gosa-si-server,
  php-apc,
  php-fpdf,
- php5-suhosin,
+ php-suhosin,
  postfix-ldap,
  slapd,
 Conflicts:
@@ -62,7 +63,7 @@ Depends:
  gosa (= ${binary:Version}),
  latex2html,
  lyx,
- php5-cli,
+ php-cli,
  ${misc:Depends},
 Description: GOsa² development utilities
  This package contains a couple of tools to generate online
@@ -75,7 +76,7 @@ Package: gosa-desktop
 Architecture: all
 Depends:
  debconf,
- iceweasel | firefox,
+ firefox-esr | iceweasel,
  ${misc:Depends},
 Description: Desktop integration for GOsa²
  This package includes a Gosa² menu definition for your desktop
diff --git a/debian/gosa-apache.conf b/debian/gosa-apache.conf
index 21c9ab7..049a594 100644
--- a/debian/gosa-apache.conf
+++ b/debian/gosa-apache.conf
@@ -1,7 +1,7 @@
 # Include GOsa to your web service
 Alias /gosa /usr/share/gosa/html
 
-
+
 
 php_admin_flag engine on
 php_admin_flag register_globals off

--

Please note that php-xml and php-mbstring are now needed as additional 
dependencies. A lot of deprecated stuff should be fixed, too, to be on 
the safe side for future PHP releases.

Please test.

Wolfgang


signature.asc
Description: Digital signature

Processed: tagging 824347

[Debian Bug Tracking System]

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

> tags 824347 + patch
Bug #824347 [planet-venus] fails in jessie with 
"django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet."
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#824347: fails in jessie with "django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet."

[Antoine Beaupré]

Package: planet-venus
Version: 0~git9de2109-3
Severity: grave
Tags: upstream

I get a fatal exception when following the bootstrap procedure for
Debian planet documented here:

https://wiki.debian.org/PlanetDebian#test

Here's the backtrace, which happens after all the feeds are parsed (so
it takes a *loong* time to get there on debian-planet!):

INFO:planet.runner:Loading cached data
Traceback (most recent call last):
  File "/usr/bin/planet", line 158, in 
splice.apply(doc.toxml('utf-8'))
  File "/usr/lib/python2.7/dist-packages/planet/splice.py", line 142, in apply
output_file = shell.run(template_file, doc)
  File "/usr/lib/python2.7/dist-packages/planet/shell/__init__.py", line 66, in 
run
module.run(template_resolved, doc, output_file, options)
  File "/usr/lib/python2.7/dist-packages/planet/shell/dj.py", line 38, in run
t = get_template(script)
  File "/usr/lib/python2.7/dist-packages/django/template/loader.py", line 144, 
in get_template
template, origin = find_template(template_name, dirs)
  File "/usr/lib/python2.7/dist-packages/django/template/loader.py", line 126, 
in find_template
loader = find_template_loader(loader_name)
  File "/usr/lib/python2.7/dist-packages/django/template/loader.py", line 98, 
in find_template_loader
TemplateLoader = import_string(loader)
  File "/usr/lib/python2.7/dist-packages/django/utils/module_loading.py", line 
26, in import_string
module = import_module(module_path)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File 
"/usr/lib/python2.7/dist-packages/django/template/loaders/app_directories.py", 
line 33, in 
app_template_dirs = calculate_app_template_dirs()
  File 
"/usr/lib/python2.7/dist-packages/django/template/loaders/app_directories.py", 
line 21, in calculate_app_template_dirs
for app_config in apps.get_app_configs():
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 137, in 
get_app_configs
self.check_apps_ready()
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 124, in 
check_apps_ready
raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

In fact, it actually fails before that, because there are two
dependencies missing (python-django and python-genshi) but that's a
separate issue.

The fix I have found it to patch venus with this:

--- planet-venus-0~git9de2109/planet/shell/dj.py2016-05-13 
15:56:44.0 -0400
+++ /usr/lib/python2.7/dist-packages/planet/shell/dj.py 2016-05-14 
08:43:55.587328754 -0400
@@ -27,6 +27,9 @@
 )
 except RuntimeError:
 pass
+import django
+django.setup()
+
 from django.template import Context
 from django.template.loader import get_template
 
I am not sure it is the correct way of doing this: i am only
marginally familiar with Django. I basically cargo-culted this from:

http://stackoverflow.com/a/27194927/1174784
http://stackoverflow.com/a/26215548/1174784
http://django.readthedocs.io/en/latest/releases/1.7.html#standalone-scripts
https://docs.djangoproject.com/en/1.8/topics/settings/#calling-django-setup-is-required-for-standalone-django-usage

So it looks okay-ish. I still get deprecation warnings, but at least
the feed is generated:

INFO:planet.runner:Loading cached data
/usr/lib/python2.7/dist-packages/django/template/base.py:290: 
RemovedInDjango18Warning: 'The `firstof` template tag is changing to escape its 
arguments; the non-autoescaping version is deprecated. Load it from the 
`future` tag library to start using the new behavior.
  compiled_result = compile_func(self, token)

WARNING:py.warnings:/usr/lib/python2.7/dist-packages/django/template/base.py:290:
 RemovedInDjango18Warning: 'The `firstof` template tag is changing to escape 
its arguments; the non-autoescaping version is deprecated. Load it from the 
`future` tag library to start using the new behavior.
  compiled_result = compile_func(self, token)

Proof it is working: http://paste.anarc.at/planet/www/

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

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

Versions of packages planet-venus depends on:
ii  python  2.7.9-1
ii  python-chardet  2.3.0-1
ii  python-feedparser   5.1.3-3
ii  python-html5lib 0.999-3
ii  python-htmltmpl 1.22-10
ii  python-httplib2 0.9+dfsg-2
ii  python-librdf   1.0.17.1+dfsg-1.1+b1
ii  python-libxml2  2.9.1+dfsg1-5+deb8u1
ii  python-portalocker  0.5.1-1
ii  python-utidylib 0.2-9

Versions of packages planet-venus recommends:
ii  python-beautifulsoup  3.2.1-1
ii  python-libxslt1   1.1.28-2+b2

V

Bug#821660: please update to upstream release 3.1.29

[Wolfgang Schweer]

On Sat, May 14, 2016 at 09:59:23AM +0200, Wolfgang Schweer wrote:
> After testing (manually updated to upstream 3.1.29 and replacing php5 
> with php in debian/control) the package seems to work with php7 - at 
> least with slbackup-php.
> 
> Please test and update the package to use the upstream release 3.1.29.
 
While testing to find out how to get gosa working with php7, I found 
that it's better to keep 3.1.21. So the only thing neede is the 
replacement in debian/control. slbackup-php works too in this case.

Wolfgang


signature.asc
Description: Digital signature

Bug#821258: marked as done (codelite: non-free image (CC-BY-NC-ND))

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 18:18:44 +
with message-id 
and subject line Bug#821258: fixed in codelite 9.1+dfsg2-1
has caused the Debian Bug report #821258,
regarding codelite: non-free image (CC-BY-NC-ND)
to be marked as done.

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

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


-- 
821258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codelite
Version: 9.1+dfsg-2
Severity: serious
Usertags: dfsg

According to its metadata, "icons/find-folder.png" is non-free:

Description: This is the icon from Gentleface.com free icons set. 
UsageTerms: Creative Commons Attribution Non-Commercial No Derivatives

Please investigate.

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: codelite
Source-Version: 9.1+dfsg2-1

We believe that the bug you reported is fixed in the latest version of
codelite, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated codelite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 14 May 2016 18:54:24 +0100
Source: codelite
Binary: codelite codelite-plugins
Architecture: source
Version: 9.1+dfsg2-1
Distribution: unstable
Urgency: medium
Maintainer: James Cowgill 
Changed-By: James Cowgill 
Description:
 codelite   - Powerful and lightweight IDE
 codelite-plugins - Powerful and lightweight IDE - plugins
Closes: 821258
Changes:
 codelite (9.1+dfsg2-1) unstable; urgency=medium
 .
   * Remove unused icons/ directory. (Closes: #821258)
   * Use my debian.org email address.
   * Bump standards to 3.9.8.
Checksums-Sha1:
 9b230847cd7b4ca05064c62f9ad2d0a99118c727 2388 codelite_9.1+dfsg2-1.dsc
 57d75890608d6c66e0a8d285f06ca47e159e0168 13833490 
codelite_9.1+dfsg2.orig.tar.gz
 2a441db6f4006d86629e44b978505f30843127d0 30992 
codelite_9.1+dfsg2-1.debian.tar.xz
Checksums-Sha256:
 f2ad0eef20278d76c6c583a3adcbca10e1194ace131e15f616796be778b9dbb0 2388 
codelite_9.1+dfsg2-1.dsc
 3e3a6988f4e00c00311625749094583d5424c69495a21ebc3d0385d5c0352679 13833490 
codelite_9.1+dfsg2.orig.tar.gz
 814d77dcc7e8d30bb3e7093282be28c7c65b878725900a40b9f93cf716ab8431 30992 
codelite_9.1+dfsg2-1.debian.tar.xz
Files:
 9338118e52c1f4fc683695c27430c471 2388 devel optional codelite_9.1+dfsg2-1.dsc
 8a47d91179b40c29a553d0457c798933 13833490 devel optional 
codelite_9.1+dfsg2.orig.tar.gz
 1037c0494441a281ff40ecedaeb81fc7 30992 devel optional 
codelite_9.1+dfsg2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXN2ZxAAoJEMfxZ23qLQHvZWYP/2jm0WZB45JXroO7EDBHm8jl
ou7lwxHRIattuQPaJTmkLPQtQQpmHmdKF77WnX9oNc5AAz3TsjFC1W7gnEGG17tx
JqWkKMoLtfziK7q4/3+6Z5mrdY4AIdu6+B2L+jF+awKFbLCkbHc0wCDUX2Zv1Ugw
+QG9jl00wT4r5HOi3+tYRfW+IKaYyoP/nCfPutmXsnWSrmTf59QwbX9xvAoHSPFl
JYeOQ/jNCS7XhVduXjZZ4zvhpT/cf94DnKFb6vZxAQK3NWU+oRXMLWROstzUXmGI
B4k/lke5PLAvLQ8SP+qH7yuJoozh2MIKlOp+PNbkFWhxavrl5Kws05p/vqlkXu1N
joMY68ebKEdH7eGGp/rXqlWXyU37SutnfAEA62XFo7eD0yxYwU0zYEOI7yNaj5K0
4t1AKcL6QorrevDo7yO0YRWlhcpk2GBV5vj0Dofk3yO8s/KII6SJcTVrgymGSGn9
ul7R+WMa+exVihxgJ0CKVhp9iuzLLqqpjCfBdvughaJWtoujR6IgsRLCXhpzPkF/
jsJ7sK+20Blaj5BNV8ISW9Ve5v5kMbw/bd3tsBiRcbwedURd7Vo+TGfO/ez6Tz3g
3JzJ6O3IbmzWNu/0wD20do79nllhZ6/ImjTlh/Eevsx5SjerRv7u3MfWsd8tnzK6
7bsnA2GzR7ChpvqMFwiw
=eFfg
-END PGP SIGNATURE End Message ---

Processed: tagging 824045

[Debian Bug Tracking System]

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

> tags 824045 + confirmed
Bug #824045 [src:groovycsv] groovycsv: FTBFS: No cached version of 
org.codehaus.groovy:groovy-all:1.7.3 available for offline mode.
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

[Jonas Smedegaard]

Quoting tYYGH (2016-05-14 18:31:55)
> Le 09/05/2016 à 16:00, Jérémy Lal a écrit :
> > 2016-05-09 15:41 GMT+02:00 Jérémy Lal  > >:
> >
> > Hi,
> >
> > sorry for the delay,
> >
> >
> > Update: v8 has dropped armv5 support, see
> > https://github.com/nodejs/node/issues/5810
> > https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk
> >
> > I'm going to remove "armel" from the list of Architectures.
> >
> > Jérémy
> 
> Thank you for replying Jérémy. Actually, tYYGH is me ;-)
> I’m currently looking for a good alternative to the eSata sheevaplug, 
> ie. a sub-100€/$ (e)Sata-or-USB3 GbEth 2GBram bi/quad-core <5W home server…

...and I am @jonassmedegaard at above referenced github discussion.

Please let's not pollute bugreports further with shopping discussions, 
but instead move that discussion either private or (preferred) to a 
public mailinglist - e.g. either 
freedombox-de...@lists.alioth.debian.org or 
pkg-javascript-de...@lists.alioth.debian.org :-)


 - 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#818552: nodejs on armel (v5l) fails with "illegal instruction"

[tYYGH]

Le 09/05/2016 à 16:00, Jérémy Lal a écrit :

2016-05-09 15:41 GMT+02:00 Jérémy Lal mailto:kapo...@melix.org>>:

Hi,

sorry for the delay,


Update: v8 has dropped armv5 support, see
https://github.com/nodejs/node/issues/5810
https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk

I'm going to remove "armel" from the list of Architectures.

Jérémy


Thank you for replying Jérémy. Actually, tYYGH is me ;-)
I’m currently looking for a good alternative to the eSata sheevaplug, 
ie. a sub-100€/$ (e)Sata-or-USB3 GbEth 2GBram bi/quad-core <5W home server…

Bug#814207: marked as done (lambdabot: FTBFS (missing build-dependency libghc-lambdabot-haskell-plugins-dev (>= 5.0.3))

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 16:29:16 +
with message-id <20160514162916.ga18...@scru.org>
and subject line reference plugins
has caused the Debian Bug report #814207,
regarding lambdabot: FTBFS (missing build-dependency 
libghc-lambdabot-haskell-plugins-dev (>= 5.0.3)
to be marked as done.

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

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


-- 
814207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lambdabot   
Version: 5.0.3-3
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

lambdabot FTBFS on all architectures since it has a build-dependency on

libghc-lambdabot-reference-plugins-dev (>= 5.0.3)

However the version of that package in sid is only 5.0.1-3+b1.

-Ralf.
--- End Message ---
--- Begin Message ---
At some point the buildds built these.--- End Message ---

Bug#821453: marked as done (haskell-lambdabot-haskell-plugins: FTBFS w/ src-exts 1.17.x)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 16:27:59 +
with message-id <20160514162759.ga18...@scru.org>
and subject line newer haskell-src-exts
has caused the Debian Bug report #821453,
regarding haskell-lambdabot-haskell-plugins: FTBFS w/ src-exts 1.17.x
to be marked as done.

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

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


-- 
821453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-haskell-plugins
Version: 5.0.3-3
Severity: serious
Justification: fails to build from source

Builds of haskell-lambdabot-haskell-plugins against current unstable
have been failing with

  src/Lambdabot/Plugin/Haskell/Undo.hs:57:55:
  Couldn't match expected type `Maybe Binds' with actual type `Binds'
  In the fourth argument of `Alt', namely `(BDecls [])'
  In the expression: Alt s pat (UnGuardedRhs x) (BDecls [])

and three more such errors (on lines 72, 106, and 107).  The problem
appears to stem from an incompatible change between versions 1.16.x
and 1.17.x of libghc-src-exts-dev.

Could you please take a look?

Thanks!

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

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)
--- End Message ---
--- Begin Message ---
Version: 5.0.3-5

Patched.--- End Message ---

Bug#819890: ugh

[Clint Adams]

severity 819890 important
quit

This has been worked around by disabling the doctests.  Whatever is
broken on armel is still broken, but that is irrelevant to the testing
migration held up by this bug.

Processed: ugh

[Debian Bug Tracking System]

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

> severity 819890 important
Bug #819890 [haskell-http2] haskell-http2: FTBFS on armel buildds (was: Re: 
Please give back haskell-http2 on armel)
Severity set to 'important' from 'serious'
> quit
Stopping processing here.

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

Bug#762950: marked as done (digikam: Removes all images from database when unaccessible mount is found)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 16:20:19 +
with message-id 
and subject line Bug#762950: fixed in kde4libs 4:4.14.20-1
has caused the Debian Bug report #762950,
regarding digikam: Removes all images from database when unaccessible mount is 
found
to be marked as done.

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

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


-- 
762950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:4.1.0-1+b1
Severity: important

Dear Maintainer,

Digikam has a serious incompatibility with docker.io due to the
particular way the docker daemon manages mounts.  If the docker daemon
is running and the user starts Digikam, Digikam will delete all album
metadata from its database, dissociate all images in the database from
their albums, and show the user an empty album tree.  If the user then
stops the docker daemon and restarts digikam, the album tree will
appear, but all images will be gone.

This happens when the user's album root is under / because docker
creates a second mount point for / that is not readable by digikam.
E.g., when docker is running, my mount table contains

/dev/disk/by-uuid/86efd6d8-2751-47e1-a6d7-2c7bf04f974b on / type ext4 
(rw,noatime,errors=remount-ro,data=ordered)
/dev/disk/by-uuid/86efd6d8-2751-47e1-a6d7-2c7bf04f974b on /var/lib/docker/aufs 
type ext4 (rw,noatime,errors=remount-ro,data=ordered)

where /var/lib/docker (and hence /var/lib/docker/aufs) has permissions
0700 and is owned by root:root.  When digikam starts, it finds the
/var/lib/docker/aufs mount point when scanning for album locations and
outputs the following error:

digikam(4915)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does 
not exist or is not readable: "/var/lib/docker/aufs/home/USER/img/digicam" 

This causes it to delete all rows from the Albums table and NULL out
the album column from the entire Images table (I would expect it to
delete all rows from Images given the delete_album trigger; I'm not
sure why this doesn't happen, but the images are as good as gone once
their album column is NULL).

I can think of a few potential fixes for this.  The most specific fix
would be to handle the case where an album root is mounted multiple
times and some mounts are inaccessible.  A more general fix might be
to be less trigger happy when deleting albums when the folder cannot
be accessed.

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages digikam depends on:
ii  digikam-data  4:4.1.0-1
ii  digikam-private-libs  4:4.1.0-1+b1
ii  kde-runtime   4:4.13.1-1
ii  libc6 2.19-7
ii  libgcc1   1:4.9.1-4
ii  libgphoto2-6  2.5.4-1
ii  libgphoto2-port10 2.5.4-1
ii  libkdcraw23   4:4.13.1-1
ii  libkdecore5   4:4.13.3-1
ii  libkdeui5 4:4.13.3-1
ii  libkexiv2-11  4:4.13.1-1
ii  libkhtml5 4:4.13.3-1
ii  libkio5   4:4.13.3-1
ii  libkipi11 4:4.13.3-1
ii  libknotifyconfig4 4:4.13.3-1
ii  libkparts44:4.13.3-1
ii  libopencv-core2.4 2.4.9+dfsg-1+b1
ii  libopencv-imgproc2.4  2.4.9+dfsg-1+b1
ii  libphonon44:4.7.1-1
ii  libqt4-dbus   4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqt4-sql4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqt4-sql-sqlite 4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqt4-xml4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqtcore44:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libsolid4 4:4.13.3-1
ii  libstdc++64.9.1-4
ii  libthreadweaver4  4:4.13.3-1
ii  perl  5.20.0-4
ii  phonon4:4.7.1-1

Versions of packages digikam recommends:
ii  ffmpegthumbs4:4.10.5-1+b1
ii  google-chrome-stable [www-browser]  36.0.1985.125-1
ii  iceweasel [www-browser] 30.0-2
ii  kipi-plugins4:4.1.0-1+b1
ii  w3m [www-browser]   0.5.3-16

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:4.11.3-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kde4libs
Source-Version: 4:4.14.20-1

We believe that the bug you reported is fixed in the latest version of
kde4libs, which is due to be installed in the D

Bug#824269: cinnamon: Cinnamon crashes with assertion Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window

[George Shuklin]

Package: cinnamon
Version: 2.8.7-1
Severity: critical
Justification: breaks the whole system

Cinnamon crashes after recent update. It cause whole system unusable.

Crash:

**
Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window:
assertion failed: (CLUTTER_IS_STAGE_X11 (impl))
Aborted

tail of strace:

uname({sysname="Linux", nodename="home", ...}) = 0
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getpid()= 3143
getpid()= 3143
getpid()= 3143
getpid()= 3143
getpid()= 3143
poll([{fd=6, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=6, revents=POLLOUT}])
writev(6,
[{"\26\0\4\0\r\0\300\3v\1\0\0\0072\f\0N\0\4\0\32\0\300\3\226\2\0\0\272\0\0\0"...,
756}, {NULL, 0}, {"", 0}], 3) = 756
poll([{fd=6, events=POLLIN}], 1, -1)= 1 ([{fd=6, revents=POLLIN}])
recvmsg(6, {msg_name(0)=NULL,
msg_iov(1)=[{"W\0\265\1\1\0\300\3\r\0\300\3v\1\0\0\t2\f\0\0072\f\0\0\0\0\0\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 268
recvmsg(6, 0x7ffe6da1b160, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=6, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=6, revents=POLLOUT}])
writev(6, [{"+\0\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4
poll([{fd=6, events=POLLIN}], 1, -1)= 1 ([{fd=6, revents=POLLIN}])
recvmsg(6, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\1\316\1\0\0\0\0\23\0\300\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(6, 0x7ffe6da1b1f0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(6, 0x7ffe6da1b1f0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
getpid()= 3143
getpid()= 3143
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f93c859d428, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(2, "**\nClutter:ERROR:x11/clutter-sta"..., 124**
Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window:
assertion failed: (CLUTTER_IS_STAGE_X11 (impl))
) = 124
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(3143, 3143, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=3143, si_uid=1000} ---
+++ killed by SIGABRT +++
Aborted

backtrace under gdb:

#0  0x75ef1458 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x75ef28da in __GI_abort () at abort.c:89
#2  0x764eed75 in g_assertion_message () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#3  0x764eee0a in g_assertion_message_expr () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#4  0x770ec557 in clutter_x11_get_stage_window () from /usr/lib/x86_64
-linux-gnu/libclutter-1.0.so.0
#5  0x7789ffcd in meta_compositor_manage_screen () from /usr/lib/x86_64
-linux-gnu/libmuffin.so.0
#6  0x778b4ea4 in ?? () from /usr/lib/x86_64-linux-gnu/libmuffin.so.0
#7 0x778c189e in meta_run () from /usr/lib/x86_64-linux-
gnu/libmuffin.so.0 #8
0x5817 in main



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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_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 cinnamon depends on:
ii  caribou  0.4.20-1
ii  cinnamon-common  2.8.7-1
ii  cinnamon-control-center  2.8.1-1
ii  cinnamon-desktop-data2.8.1-1
ii  cinnamon-screensaver 2.8.0-1
ii  cinnamon-session 3.0.0-1
ii  cinnamon-settings-daemon 2.8.4-2
ii  cjs  3.0.1-1
ii  cups-pk-helper   0.2.5-2+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-caribou-1.0   0.4.20-1
ii  gir1.2-clutter-1.0   1.26.0-2
ii  gir1.2-cmenu-3.0 3.0.0-1
ii  gir1.2-cogl-1.0  1.22.0-2
ii  gir1.2-gconf-2.0 3.2.6-3
ii  gir1.2-gdkpixbuf-2.0 2.34.0-1
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.48.0-2
ii  gir1.2-gnomedesktop-3.0  3.20.2-1
ii  gir1.2-gtk-3.0   3.20.4-1
ii  gir1.2-gtkclutter-1.01.8.0-1
ii  gir1.2-javascriptcoregtk-3.0 2.4.11-1
ii  gir1.2-keybinder-3.0

Bug#823281: gnustep-make: build-indep depends on binary-arch

[Eric Heintzmann]

Le 14/05/2016 13:14, Eric Heintzmann a écrit :
> Hi,
>
> Le 03/05/2016 16:00, Santiago Vila a écrit :
>> On Tue, May 03, 2016 at 03:46:13PM +0200, Eric Heintzmann wrote:
>>> Thanks for this bug report and thanks for finding a solution.
>>>
>>> Anyway I plan to repackage the Core GNUstep packages (including
>>> gnustep-make),
>>> and rewriting debian/rules using dh_overrides_* targets.
>>> (If there are no objections from other Debian GNUstep Maintainers)
>>> It should solve these bugs.
>> You are welcome.
>>
>> I tried to find a solution, yes, but the current debian/rules was too
>> much convoluted and I never understood how it really worked.
>>
>> Rewriting it in "dh" seems a very good idea. Wish you luck.
>>
>> Thanks.
> The new gnustep-make package (2.6.8) is available at:
>
> https://mentors.debian.net/debian/pool/main/g/gnustep-make/gnustep-make_2.6.8-1.dsc
>
> It fixes this bug.
>
> Thanks
>

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

  https://mentors.debian.net/package/gnustep-make


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

dget -x
https://mentors.debian.net/debian/pool/main/g/gnustep-make/gnustep-make_2.6.8-1.dsc

  More information about GNUstep can be obtained from
http://gnustep.org/information/aboutGNUstep.html

  Changes since the last upload:

Bug#824260: texlive build failures on Debian - upmendex

[Mojca Miklavec]

On 14 May 2016 at 13:14, Norbert Preining wrote:
>
> Mojca, you had something similar:
>
>> >> Making index file.Segmentation Fault - core dumped
>> >> FAIL tests/upmendex.test (exit status: 1)
>> >
>> > In the case of i386-freebsd, Karl found that the test for upmendex
>> > became OK by explicitly specifying -DU_IS_BIG_ENDIAN=0
>> > in both of CFLAGS and CXXFLAGS (for icu).
>>
>> Thank you very much for the hint. That solved the problem for me as well.

The same flag had to be used for x86_64-solaris. The weird thing is
that after using that flag all other binaries became slower (and all
binaries changed even though they were not supposed to; no other
library uses U_IS_BIG_ENDIAN).

Mojca

Bug#823281: [Debian GNUstep maintainers] Bug#823281: gnustep-make: build-indep depends on binary-arch

[Eric Heintzmann]

Hi,

Le 03/05/2016 16:00, Santiago Vila a écrit :
> On Tue, May 03, 2016 at 03:46:13PM +0200, Eric Heintzmann wrote:
>> Thanks for this bug report and thanks for finding a solution.
>>
>> Anyway I plan to repackage the Core GNUstep packages (including
>> gnustep-make),
>> and rewriting debian/rules using dh_overrides_* targets.
>> (If there are no objections from other Debian GNUstep Maintainers)
>> It should solve these bugs.
> You are welcome.
>
> I tried to find a solution, yes, but the current debian/rules was too
> much convoluted and I never understood how it really worked.
>
> Rewriting it in "dh" seems a very good idea. Wish you luck.
>
> Thanks.
The new gnustep-make package (2.6.8) is available at:

https://mentors.debian.net/debian/pool/main/g/gnustep-make/gnustep-make_2.6.8-1.dsc

It fixes this bug.

Thanks

Bug#824260: texlive build failures on Debian - upmendex

[Norbert Preining]

Hi all,

I have uploaded the current status to Debian, and we got a few
build errors, which some of you might have seen already:

* mips architecture

FAIL: test/upmendex
...
This is upmendex version 0.50 (TeX Live 2016).
Scanning dictionary file ../../../texk/upmendex/tests/uni.dictdone.
Scanning input file ../../../texk/upmendex/tests/uni.idxdone (8 entries 
accepted, 0 rejected).
8 entries accepted, 0 rejected.
Sorting indexdone(24 comparisons).
Sorting pagesdone(0 comparisons).
Making index file.*** stack smashing detected ***: 
/«PKGBUILDDIR»/Work/texk/upmendex/.libs/lt-upmendex terminated
Aborted
FAIL tests/upmendex.test (exit status: 1)



* sparc

FAIL: xetexdir/xetex-bug73
==

This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/Debian) (INITEX)
 restricted \write18 enabled.
(./bug73.tex (../../../texk/web2c/tests/basic.tex
Preloading the plain format: codes, registers,Segmentation fault (core dumped)
FAIL xetexdir/xetex-bug73.test (exit status: 1)




Mojca, you had something similar:

> >> Making index file.Segmentation Fault - core dumped
> >> FAIL tests/upmendex.test (exit status: 1)
> >
> > In the case of i386-freebsd, Karl found that the test for upmendex
> > became OK by explicitly specifying -DU_IS_BIG_ENDIAN=0
> > in both of CFLAGS and CXXFLAGS (for icu).
> 
> Thank you very much for the hint. That solved the problem for me as well.

Do you think (or AKira) that this is the problem for mips?

For sparc I am a bit stymed.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#824074: gimp: Crashes (apparently) when Caps Lock key is pressed

[Guillermo]

I hope this is useful:

Thread 7 (Thread 0x7fffe2824700 (LWP 8297)):
#0  0x7303bae9 in syscall () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x738a4bdf in g_cond_wait (cond=cond@entry=0xd46dc8, 
mutex=mutex@entry=0xd46dc0) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1397
#2  0x7383496b in g_async_queue_pop_intern_unlocked 
(queue=0xd46dc0, wait=wait@entry=1, end_time=end_time@entry=-1) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:419
#3  0x73834e36 in g_async_queue_pop_unlocked (queue=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:475
#4  0x73887565 in g_thread_pool_thread_proxy (pool=0xd46f10) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:245
#5  0x73887565 in g_thread_pool_thread_proxy (data=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:296
#6  0x73886b75 in g_thread_proxy (data=0xc57f20) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread.c:780
#7  0x73302454 in start_thread () at 
/lib/x86_64-linux-gnu/libpthread.so.0

#8  0x7303feed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7fffe3025700 (LWP 8296)):
#0  0x7303bae9 in syscall () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x738a4bdf in g_cond_wait (cond=cond@entry=0xd46dc8, 
mutex=mutex@entry=0xd46dc0) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1397
#2  0x7383496b in g_async_queue_pop_intern_unlocked 
(queue=0xd46dc0, wait=wait@entry=1, end_time=end_time@entry=-1) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:419
#3  0x73834e36 in g_async_queue_pop_unlocked (queue=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:475
#4  0x73887565 in g_thread_pool_thread_proxy (pool=0xd46f10) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:245
#5  0x73887565 in g_thread_pool_thread_proxy (data=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:296
#6  0x73886b75 in g_thread_proxy (data=0xc57ed0) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread.c:780
#7  0x73302454 in start_thread () at 
/lib/x86_64-linux-gnu/libpthread.so.0

#8  0x7303feed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7fffe3826700 (LWP 8295)):
#0  0x7303bae9 in syscall () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x738a4bdf in g_cond_wait (cond=cond@entry=0xd46dc8, 
mutex=mutex@entry=0xd46dc0) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1397
#2  0x7383496b in g_async_queue_pop_intern_unlocked 
(queue=0xd46dc0, wait=wait@entry=1, end_time=end_time@entry=-1) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:419
#3  0x73834e36 in g_async_queue_pop_unlocked (queue=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:475
#4  0x73887565 in g_thread_pool_thread_proxy (pool=0xd46f10) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:245
#5  0x73887565 in g_thread_pool_thread_proxy (data=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:296
#6  0x73886b75 in g_thread_proxy (data=0xc57e80) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread.c:780
#7  0x73302454 in start_thread () at 
/lib/x86_64-linux-gnu/libpthread.so.0

#8  0x7303feed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7fffe4027700 (LWP 8294)):
#0  0x7303bae9 in syscall () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x738a4bdf in g_cond_wait (cond=cond@entry=0xd46dc8, 
mutex=mutex@entry=0xd46dc0) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1397
#2  0x7383496b in g_async_queue_pop_intern_unlocked 
(queue=0xd46dc0, wait=wait@entry=1, end_time=end_time@entry=-1) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:419
#3  0x73834e36 in g_async_queue_pop_unlocked (queue=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gasyncqueue.c:475
#4  0x73887565 in g_thread_pool_thread_proxy (pool=0xd46f10) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:245
#5  0x73887565 in g_thread_pool_thread_proxy (data=out>) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthreadpool.c:296
#6  0x73886b75 in g_thread_proxy (data=0xc57e30) at 
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread.c:780
#7  0x73302454 in start_thread () at 
/lib/x86_64-linux-gnu/libpthread.so.0

#8  0x7303feed in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7fffe4828700 (LWP 8293)):
#0  0x73036e5d in poll () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x7386032c in g_main_context_iterate (priority=2147483647, 
n_fds=2, fds=0x7fffd40010c0, timeout=, context=0xd21b70) 
at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:4135
#2  0x7386032c in g_main_context_iterate (context=0xd21b70, 
block=block@entry=1, dispatch=dis

Bug#807473: Potential data loss and security breach when used with nfs server

[Nick Koretsky]

On Sat, 14 May 2016 10:34:16 +0200 
 Petter Reinholdtsen  wrote:

> Control: forwarded -1 https://github.com/mtorromeo/r8168/issues/4
> 
> I forwarded this issue upstream, and the response there was that a new
> version is available and he wonders if the problem still exist there.
> 
> Perhaps something to check out?

I dont have the original hardware anymore, but i just tried it on another
machine and got the same result.

-- 
  Nick Koretsky (nick.koret...@gmail.com)
  

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

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 10:04:58 +
with message-id 
and subject line Bug#821234: fixed in twinkle 
1:1.9.0+git20160321.0.64a0816+dfsg-1
has caused the Debian Bug report #821234,
regarding twinkle: FTBFS: error: 'ucommon::Digest::Digest(const 
ucommon::Digest&)' is private
to be marked as done.

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

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


-- 
821234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twinkle
Version: 1:1.9.0+dfsg-3
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,

twinkle fails to build from source in unstable/amd64:

  [..]

  [ 43%] Building CXX object 
src/parser/CMakeFiles/libtwinkle-parser.dir/hdr_proxy_authorization.cpp.o
  cd 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu/src/parser
 && /usr/bin/c++   -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB 
-DQT_SCRIPT_LIB -DQT_WIDGETS_LIB -I/usr/include/libxml2 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -fPIC -fPIC   -o 
CMakeFiles/libtwinkle-parser.dir/hdr_proxy_authorization.cpp.o -c 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser/hdr_proxy_authorization.cpp
  [ 44%] Building CXX object 
src/parser/CMakeFiles/libtwinkle-parser.dir/hdr_proxy_require.cpp.o
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu/src/parser
 && /usr/bin/c++   -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB 
-DQT_SCRIPT_LIB -DQT_WIDGETS_LIB -I/usr/include/libxml2 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -fPIC -fPIC   -o 
CMakeFiles/libtwinkle-parser.dir/hdr_proxy_require.cpp.o -c 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser/hdr_proxy_require.cpp
  [ 44%] Built target libtwinkle-audio
  [ 44%] Building CXX object 
src/parser/CMakeFiles/libtwinkle-parser.dir/hdr_rack.cpp.o
  cd 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu/src/parser
 && /usr/bin/c++   -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB 
-DQT_SCRIPT_LIB -DQT_WIDGETS_LIB -I/usr/include/libxml2 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -fPIC -fPIC   -o 
CMakeFiles/libtwinkle-parser.dir/hdr_rack.cpp.o -c 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser/hdr_rack.cpp
  [ 44%] Building CXX object 
src/parser/CMakeFiles/libtwinkle-parser.dir/hdr_record_route.cpp.o
  cd 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu/src/parser
 && /usr/bin/c++   -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB 
-DQT_SCRIPT_LIB -DQT_WIDGETS_LIB -I/usr/include/libxml2 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src 
-I/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -fPIC -fPIC   -o 
CMakeFiles/libtwinkle-parser.dir/hdr_record_route.cpp.o -c 
/home/lamby/temp/cdt.20160416231824.jL9MhpgORp.twinkle/twinkle-1.9.0+dfsg/src/parser/hdr_record_route.cpp
  [ 44%] Building CXX object src/CMakeFiles/libtwinkle.dir/id

Bug#823005: marked as done (pepperflashplugin-nonfree: Missing PGP key)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 10:00:14 +
with message-id 
and subject line Bug#823005: fixed in pepperflashplugin-nonfree 1.8.2+nmu1
has caused the Debian Bug report #823005,
regarding pepperflashplugin-nonfree: Missing PGP key
to be marked as done.

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

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


-- 
823005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.1
Severity: grave
Justification: renders package unusable

Hi,

Google apparently started using a new PGP key, which leads to:

# update-pepperflashplugin-nonfree --install
ERROR: failed to retrieve status information from google : W: There is no 
public key available for the following key IDs:
A040830F7FAC5991
More information might be available at:
  http://wiki.debian.org/PepperFlashPlayer

I tried updating to 1.8.2, no change.

Appending the new key to /usr/lib/pepperflashplugin-nonfree/pubkey-google.txt
solves the problem for me. The old key seems to still be needed, since
with only the new key ih pubkey-google.txt I'm getting the same error
with a different key id.

Regards,
Andreas

-- System Information:
Debian Release: 8.4
  APT prefers stable
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils2.25-5
ii  ca-certificates 20141019+deb8u1
ii  cdebconf [debconf-2.0]  0.192
ii  debconf [debconf-2.0]   1.5.56
ii  gnupg   1.4.18-7+deb8u1
ii  libatk1.0-0 2.14.0-1
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libcurl3-gnutls 7.38.0-4+deb8u3
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-3+deb8u1
ii  libgcc1 1:4.9.2-10
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libnspr42:4.10.7-1+deb8u1
ii  libnss3 2:3.17.2-1.1+deb8u2
ii  libpango-1.0-0  1.36.8-3
ii  libpango1.0-0   1.36.8-3
ii  libstdc++6  4.9.2-10
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxt6  1:1.1.4-1+b1
ii  wget1.16-1

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   50.0.2661.75-1~deb8u1
pn  hal
ii  ttf-dejavu 2.34-1
ii  ttf-mscorefonts-installer  3.6
ii  ttf-xfree86-nonfree4.2.1-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pepperflashplugin-nonfree
Source-Version: 1.8.2+nmu1

We believe that the bug you reported is fixed in the latest version of
pepperflashplugin-nonfree, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 823...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kristian Klausen  (supplier of updated 
pepperflashplugin-nonfree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 May 2016 14:44:52 +0200
Source: pepperflashplugin-nonfree
Binary: pepperflashplugin-nonfree
Architecture: source
Version: 1.8.2+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Kristian Klausen 
Description:
 pepperflashplugin-nonfree - Pepper Flash Player - browser plugin
Closes: 816848 818540 823005
Changes:
 pepperflashplugin-nonfree (1.8.2+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Google public key. Closes: #823005.
   * Remove 32 bit support. Closes: #816848.
   * Don't treat `apt-get update` warnings as errors. Closes: #818540.
   * Validate deb file with sha256sum.
Checksums-Sha1:
 adbc6808e26cbfefd3b68faf647bf8583b09fbae 1560 
pepperflashplugin-nonfree_1.8.2+nmu1.dsc
 aa5c1139942029d19e2df4b1f04fb467a7ed50ad 10040 
pepperflashplugin-nonfree_1.8.2+nmu1.tar.xz
Checksums-Sha256:
 88c03f2cd2da6496502fcd73db3ea768be38b3dbfcf8b88193517bbd4

Bug#818540: marked as done (pepperflashplugin-nonfree: broken by new apt)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 10:00:14 +
with message-id 
and subject line Bug#818540: fixed in pepperflashplugin-nonfree 1.8.2+nmu1
has caused the Debian Bug report #818540,
regarding pepperflashplugin-nonfree: broken by new apt
to be marked as done.

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

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


-- 
818540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.2
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


update-pepperflashplugin-nonfree --install
ERROR: failed to retrieve status information from google : W: 
gpgv:./var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_Release.gpg:
 The repository is insufficiently signed by key 
4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 (weak digest)
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release  
No Hash entry in Release file 
./var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_Release,
 which is considered strong enough for security purposes
E: Some index files failed to download. They have been ignored, or old ones 
used instead.
More information might be available at:
  http://wiki.debian.org/PepperFlashPlayer


And https://dl.google.com/linux/chrome/deb/dists/stable/Release

Origin: Google, Inc.
Label: Google
Suite: stable
Codename: stable
Version: 1.0
Date: Wed, 16 Mar 2016 18:15:33 +
Architectures: amd64
Components: main
Description: Google chrome-linux repository.
MD5Sum:
 89704f9af9e6ccd87c192de11ba4c511 145 main/binary-amd64/Release
 d2b08e4f7fb636a04dcd64b489e6a04f 4153 main/binary-amd64/Packages
 849375690847e5dc7e117bb2d82178f6 977 main/binary-amd64/Packages.gz
 023dad1670d0ef1941e90dce131e1130 1221 main/binary-amd64/Packages.bz2
SHA1:
 153199d8f866350b7853365a4adc95ee687603dd 145 main/binary-amd64/Release
 217fc8e53d8a058ba3bf85d58fbae6dd1aa52aac 4153 main/binary-amd64/Packages
 8bb0e9f192e94d0b59960da2373f5ee8a4d26c6f 977 main/binary-amd64/Packages.gz
 557bd43d561ebaec537c568b88d585b2a2656c48 1221 main/binary-amd64/Packages.bz2


Seems this is not enough for the new apt ...


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJW6xZlXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGfLYP/i7gCEbQQRAwZt0nIT++KbFb
fEJHU4Co+fqIVXgB/PENJFIbrxr2XVSKdZ9Y1N6lnEyuyffWJaOFgLgof/oima7a
ncGjQl7TUplfDLEMqxivsygIBOcklFxUrdeFFSopyCTKrao0EncLx7gKq31egDla
LyBCqiQW0tHSSZT0AakNx4eCEiRWjxuIQk2uz6pR9VAypGT/Ra959TsW6fqPoIZ5
ntQqkoPoZdXu1vUjZF/VjcJL0BNyzHMkA+wwCOe4qFKdROA0sAUhyGJ+VvTPFYY3
3jFobC4wr40ayLmbOAZXMvddSOZae0KSYasV5BM9v5X0gP1TPLzsG5IQVHl8QRru
xjb9K+zSoLC2pnrNmbQ5JDWbQ79bVjZOkB67Z/+uC53hVpsSnUhymC52RYlAJOoG
HH7pZGQJh5duBagL1nro5BmMBLGeru0vNCNmUB+xGYwli6Uu5UMiBGeBsCEX4z3D
8Wq+UzQs97AsO8EmKg3bGNmKbI6uU8de5Muw56I9/NMOgpppvG2N0rk5aTrxwRLD
yUIKuD23jhqG+enEixiS0MdSViOUsvU6OTmpmi4sVZaB6N3VihHq4XStFeBTNESB
lZC/Z4SuGtKZJFNdRE9TFyEQFiPkJss/CrRB8stfI9M9U6U84kqtrJ0HM0njZE31
lytZpnDYVrhgcYYdtXnG
=VeNi
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pepperflashplugin-nonfree
Source-Version: 1.8.2+nmu1

We believe that the bug you reported is fixed in the latest version of
pepperflashplugin-nonfree, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kristian Klausen  (supplier of updated 
pepperflashplugin-nonfree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 May 2016 14:44:52 +0200
Source: pepperflashplugin-nonfree
Binary: pepperflashplugin-nonfree
Architecture: source
Version: 1.8.2+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Kristian Klausen 
Description:
 pepperflashplugin-nonfree - Pepper Flash Player - browser plugin
Closes: 816848 818540 823005
Changes:
 pepperflashplugin-nonfree (1.8.2+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Google public key. Closes: #

Bug#816848: marked as done (pepperflashplugin-nonfree: Google has dropped support for 32 bit Google-Chrome)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 10:00:14 +
with message-id 
and subject line Bug#816848: fixed in pepperflashplugin-nonfree 1.8.2+nmu1
has caused the Debian Bug report #816848,
regarding pepperflashplugin-nonfree: Google has dropped support for 32 bit 
Google-Chrome
to be marked as done.

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

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


-- 
816848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,


The pepperflashplugin-nonfree doesn't update or install pepperflash. I suspect 
the reason
is Google has dropped support for 32 bit Google-Chrome, so the flash package is 
simply not available anymore.

This is the result of running it 



root@frank-debian:/home/frank# update-pepperflashplugin-nonfree --install 
--verbose
options :  --install --verbose --
temporary directory: /tmp/pepperflashplugin-nonfree.lOWqvvqSXk
doing apt-get update on google repository
E: No packages found
E: No packages found
E: No packages found
E: No packages found
E: No packages found
downloading 
http://people.debian.org/~bartm/pepperflashplugin-nonfree/latest-stable-verified.txt
selected action = --install
dpkg-deb: error: --extract needs a target directory.
Perhaps you should be using dpkg --install ?

Type dpkg-deb --help for help about manipulating *.deb files;
Type dpkg --help for help about installing and deinstalling packages.
root@frank-debian:/home/frank# 




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

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils   2.26-5
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.58
ii  gnupg  1.4.20-4
ii  libatk1.0-02.18.0-1
ii  libcairo2  1.14.6-1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.3-3
ii  libgcc11:5.3.1-10
ii  libglib2.0-0   2.46.2-3
ii  libgtk2.0-02.24.29-1
ii  libnspr4   2:4.11-1
ii  libnss32:3.21-1.1
ii  libpango-1.0-0 1.38.1-1
ii  libpango1.0-0  1.38.1-1
ii  libstdc++6 5.3.1-10
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.17.1-1+b1

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   49.0.2623.75-2
pn  hal
ii  ttf-dejavu 2.35-1
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pepperflashplugin-nonfree
Source-Version: 1.8.2+nmu1

We believe that the bug you reported is fixed in the latest version of
pepperflashplugin-nonfree, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kristian Klausen  (supplier of updated 
pepperflashplugin-nonfree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 May 2016 14:44:52 +0200
Source: pepperflashplugin-nonfree
Binary: pepperflashplugin-nonfree
Architecture: source
Version: 1.8.2+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Kristian Klausen 
Description:
 pepperflashplugin-nonfree - Pepper Flash Player - browser plugin
Closes: 816848 818540 823005
Changes:
 pepperflashplugin-nonfree (1.8.2+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Google public key. Closes: #823005.
   * Remove 32 bit support. Closes: #816848.
   * Don't treat `apt-get update` warnings as errors. Closes: #818540.
   * Va

Bug#823503: marked as done (pepperflashplugin-nonfree: Can't install package: No public key for 1397BC53640DB551)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 10:00:14 +
with message-id 
and subject line Bug#823005: fixed in pepperflashplugin-nonfree 1.8.2+nmu1
has caused the Debian Bug report #823005,
regarding pepperflashplugin-nonfree: Can't install package: No public key for 
1397BC53640DB551
to be marked as done.

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

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


-- 
823005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.1
Severity: important

Dear Maintainer,

I reinstalled debian by formatting my root partition and keeping a separate
home partition. Now I cannot install pepperflashplugin-nonfree. I get this
error:
Setting up pepperflashplugin-nonfree (1.8.1) ...
ERROR: failed to retrieve status information from google : W: There is no
public key available for the following key IDs:
1397BC53640DB551

I tried adding the key by using
   sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 1397BC53640DB551

But this did not change the error.



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

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

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils   2.25-5
ii  ca-certificates20141019+deb8u1
ii  debconf [debconf-2.0]  1.5.56
ii  gnupg  1.4.18-7+deb8u1
ii  libatk1.0-02.14.0-1
ii  libcairo2  1.14.0-2.1+deb8u1
ii  libcurl3-gnutls7.38.0-4+deb8u3
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.5.2-3+deb8u1
ii  libgcc11:4.9.2-10
ii  libglib2.0-0   2.42.1-1+b1
ii  libgtk2.0-02.24.25-3+deb8u1
ii  libnspr4   2:4.10.7-1+deb8u1
ii  libnss32:3.17.2-1.1+deb8u2
ii  libpango-1.0-0 1.36.8-3
ii  libpango1.0-0  1.36.8-3
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.4-1+b1
ii  wget   1.16-1

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   50.0.2661.94-1~deb8u1
pn  hal
pn  ttf-dejavu 
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pepperflashplugin-nonfree
Source-Version: 1.8.2+nmu1

We believe that the bug you reported is fixed in the latest version of
pepperflashplugin-nonfree, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 823...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kristian Klausen  (supplier of updated 
pepperflashplugin-nonfree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 May 2016 14:44:52 +0200
Source: pepperflashplugin-nonfree
Binary: pepperflashplugin-nonfree
Architecture: source
Version: 1.8.2+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Kristian Klausen 
Description:
 pepperflashplugin-nonfree - Pepper Flash Player - browser plugin
Closes: 816848 818540 823005
Changes:
 pepperflashplugin-nonfree (1.8.2+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Google public key. Closes: #823005.
   * Remove 32 bit support. Closes: #816848.
   * Don't treat `apt-get update` warnings as errors. Closes: #818540.
   * Validate deb file with sha256sum.
Checksums-Sha1:
 adbc6808e26cbfefd3b68faf647bf8583b09fbae 1560 
pepperflashplugin-nonfree_1.8.2+nmu1.dsc
 aa5c1139942029d19e2df4b1f04fb467a7ed50ad 10040 
pepperflashplugin-nonfree_1.8.2+nmu1.tar.xz
Checksums-Sha256:
 88c03f2cd2da6496502fcd73db3ea768be38b3dbfcf8b88193517bbd4a983e35 1560 
pepperflashplugin-nonfree_1.8.2+nmu1.dsc
 72c363424ee2c9cd333ca78a76c587ae1f95f52b4a5ea5a8ae73b4ba249b8912 10040 
pepperflashplugin-nonfr

Bug#818637: marked as done (The repository is insufficiently signed)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 10:00:14 +
with message-id 
and subject line Bug#818540: fixed in pepperflashplugin-nonfree 1.8.2+nmu1
has caused the Debian Bug report #818540,
regarding The repository is insufficiently signed
to be marked as done.

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

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


-- 
818540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.2

# update-pepperflashplugin-nonfree --status
ERROR: failed to retrieve status information from google : W: 
gpgv:./var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_Release.gpg:
 The repository is insufficiently signed by key 
4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 (weak digest)
More information might be available at:
  http://wiki.debian.org/PepperFlashPlayer
--- End Message ---
--- Begin Message ---
Source: pepperflashplugin-nonfree
Source-Version: 1.8.2+nmu1

We believe that the bug you reported is fixed in the latest version of
pepperflashplugin-nonfree, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kristian Klausen  (supplier of updated 
pepperflashplugin-nonfree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 May 2016 14:44:52 +0200
Source: pepperflashplugin-nonfree
Binary: pepperflashplugin-nonfree
Architecture: source
Version: 1.8.2+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Kristian Klausen 
Description:
 pepperflashplugin-nonfree - Pepper Flash Player - browser plugin
Closes: 816848 818540 823005
Changes:
 pepperflashplugin-nonfree (1.8.2+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Google public key. Closes: #823005.
   * Remove 32 bit support. Closes: #816848.
   * Don't treat `apt-get update` warnings as errors. Closes: #818540.
   * Validate deb file with sha256sum.
Checksums-Sha1:
 adbc6808e26cbfefd3b68faf647bf8583b09fbae 1560 
pepperflashplugin-nonfree_1.8.2+nmu1.dsc
 aa5c1139942029d19e2df4b1f04fb467a7ed50ad 10040 
pepperflashplugin-nonfree_1.8.2+nmu1.tar.xz
Checksums-Sha256:
 88c03f2cd2da6496502fcd73db3ea768be38b3dbfcf8b88193517bbd4a983e35 1560 
pepperflashplugin-nonfree_1.8.2+nmu1.dsc
 72c363424ee2c9cd333ca78a76c587ae1f95f52b4a5ea5a8ae73b4ba249b8912 10040 
pepperflashplugin-nonfree_1.8.2+nmu1.tar.xz
Files:
 c416b8445eacad4e8733915f001b2b50 1560 contrib/web optional 
pepperflashplugin-nonfree_1.8.2+nmu1.dsc
 ce5de144cd4ea823d245bfe7fba7861d 10040 contrib/web optional 
pepperflashplugin-nonfree_1.8.2+nmu1.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXNt98AAoJEPNPCXROn13Zpv0QAI+SFXwjDyxxoETOkJH/7ymK
d3F13mb93b1e3cvtAk2DXgjtccwH0zKGH9m7RsMKzmr+IUlI4Q935l/gyy/4obt5
kMlEZJREp++1/uqamu0g397Jl6CIkpdLn8zFbHBtUFD7M7e0JW3cwOKJwQSBvY8w
UhloP3OcWtVLbfCeqTPSn4GjBf32t5i5qJBpO0kxX5BqycGiJKq5yWbo+3CtCqlJ
b1tcGMY3/+fXMlFa5IOm3ENFy9lnoTKk0Hj3oJEHSL0yuwT+Vp3BiG339G6WZu10
JvDATUZOp/EZeMr0ek9mb3dTcKeRGRCUFi1ZfYDRrBq+41yju2r8tZsCLcCBNaFi
RdmPIkE9R/MeSRXEDEN+mkTljQR67GwPI8aDEEHJR8d6HpsJAfjNyqNVdqMI5mxz
YKzGSGv5WMrqpf1jJngsjJVAhEnFNzOYAxXMfzgMPX+t0Sul9ixHQzDXvNhxz1J+
D+xygGL0O86a5vogJBtK7h1W/QXpZCBeIT6Y78wi1fdKG6UbZf0fien5jFylkR5u
YF4oNgd4SLgNHJvYR725+Pb1HbFd+3bNzSiYXWmlcX2LGcrXTxkwtMdLFqwJuiXN
WWb6Wk+WbDAPPEkrOqwwFnRutoTdGMyOuoIzZsfr5MRyzXA760vt3C+ZLNy2yE3X
fX1pn51fmFKBO8VJRDNh
=Dssn
-END PGP SIGNATURE End Message ---

Bug#823369: marked as done (adacontrol: FTBFS: t_representation_clauses vs. big-endian systems)

[Debian Bug Tracking System]

Your message dated Sat, 14 May 2016 09:49:19 +
with message-id 
and subject line Bug#823369: fixed in adacontrol 1.17r3.1-3
has caused the Debian Bug report #823369,
regarding adacontrol: FTBFS: t_representation_clauses vs. big-endian systems
to be marked as done.

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

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


-- 
823369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adacontrol
Version: 1.17r3.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of adacontrol for big-endian architectures such as mips or
powerpc are now failing:

  t_representation_clauses.adb:89:12: attempt to specify non-contiguous field 
not permitted
  t_representation_clauses.adb:89:12: caused by non-standard Bit_Order specified
  t_representation_clauses.adb:89:12: consider possibility of using Ada 2005 
mode here
  Controlling T_REPRESENTATION_CLAUSES specification ... not found!
  Controlling T_REPRESENTATION_CLAUSES body ... not found!
  [...]
  => t_representation_clauses.txtFAILED
<=
  [...]
  --   Passed= 78, Failed= 1   
--

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: adacontrol
Source-Version: 1.17r3.1-3

We believe that the bug you reported is fixed in the latest version of
adacontrol, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 823...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated adacontrol package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 14 May 2016 10:05:18 +0200
Source: adacontrol
Binary: adacontrol adacontrol-doc
Architecture: source
Version: 1.17r3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Brenta 
Changed-By: Nicolas Boulenguez 
Description:
 adacontrol - Ada rules controller
 adacontrol-doc - Ada rules controller (documentation)
Closes: 823369
Changes:
 adacontrol (1.17r3.1-3) unstable; urgency=medium
 .
   * Update representation clause test for Ada 2005. Closes: #823369.
Checksums-Sha1:
 f4ec3e878ee495dddbc3ac0e7feaac473b75a9bd 2214 adacontrol_1.17r3.1-3.dsc
 81baca81ac29f762a7f5e454d9ca839ece2ea6d5 12360 
adacontrol_1.17r3.1-3.debian.tar.xz
Checksums-Sha256:
 0da18002dc4f630b6ca75e7841efbe896a28b2c185ddbda5256720519f63f5c9 2214 
adacontrol_1.17r3.1-3.dsc
 00cd8fa34af3d551c9524ecc65e4e7caff76a5f3a1e20be8e999251a1c950d4d 12360 
adacontrol_1.17r3.1-3.debian.tar.xz
Files:
 d006b00afb7582470b5463ee3d7099c1 2214 devel optional adacontrol_1.17r3.1-3.dsc
 a02fa3e3be4ef9f3957057fd4f86a242 12360 devel optional 
adacontrol_1.17r3.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXNvHbAAoJELUqnPRJDfyNOF0QAIQaw1wXZrMCczMRxOVYWcwm
ar44uGogcVPJhwrznBcPgCCdAYr8lO8UPb98U+x70EclinNqgDZXDFiG3tUuRuUB
KPkQEG0VdDyC7Xw0vSxsiie878Udo05nr0uLIOv3f/+MsxuNYyvd27eJWVLUr3+q
sbCZJx+ne6LW7ERpdoukmtKJHM5sJ+VzSZsIojTgMRT/L4+BydH18NMxHIEVBCNR
ewe+rboXaIgbTZbjDt1r0EII3ZKrCdpdJ8xa1yhcS0ynJwUpuRcv7pxoj6ykolPF
OKje5K3mktY5WTLhzdNHBimSB2P/Cn3lTDnM4Fc7iPT/ttN02zdE6mJxX1YAFWfE
d1Nt9ndZkedUrc4sMivnKZiW97y26QebRwLDU4qji3ikOom+G0FoUm6tlU+yTCgl
W63zXRlAfI4vbtTJTbAcGD6mZbsutMXa+RJhLkYYbGyigCESPD3TEE8w2S1eXLGI
eMb5yHZYFIiDSMcYYBd8XWYU561TzTPm56+hhTGQkS081oO9GhudeweFO8z8tjHA
Ken6xW4wNNKu9qvMUzqzNakvqacvCmyu+NnnxiWH4X+HGhTDCE5fkklHBt7jm32N
6wX/JPGcFL88loV2zZGl8CRY+esiYVhokOLabSHhKGdjAURWU0adH0pV7FDEw5Pk
wVysEhgdQr1v2bhHU9sq
=JdLS
-END PGP SIGNATURE End Message ---

Bug#823369: adacontrol: FTBFS: new ARM restrictions for representation clauses

[Nicolas Boulenguez]

Package: src:adacontrol
Followup-For: Bug #823369

Hello.

The log attached by Matthias contains the same compiler message,
though the problem is detected far later.

New restrictions make legal Ada95 code illegal in Ada2005 [1].

All Debian architectures ensure "sizeof(long long) == 8" [2]
probably implying "the size of the largest machine scalar is at least 64".
Adding the Ada_2005 and lowering the length of the RecTab string field
to 7 chararcters instead of 10 fixes the issue on partch.debian.org.

[1] http://www.ada-auth.org/cgi-bin/cvsweb.cgi/ais/ai-00133.txt.
[2] https://wiki.debian.org/ArchitectureSpecificsMemo,

Bug#824260: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Bas Couwenberg]

Source: texlive-bin
Version: 2016.20160513.41080-1
Severity: serious
Justification: FTBFS on official and debian-ports architectures
Control: block 823335 by -1

Dear Maintainer,

The changes to fix #824166 were not sufficient to also fix the build
failure on mips, mipsel & sparc64. texlive-bin (2016.20160513.41080-1)
still FTBFS on those architectures.

The build failure on mipsel is preventing the build of vtk6 blocking the
ongoing gdal transition (#823335).

If the test failures cannot be fixed, I suggest to ignore the failures
on these three architectures.

Kind Regards,

Bas

Processed: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Debian Bug Tracking System]

Processing control commands:

> block 823335 by -1
Bug #823335 [release.debian.org] transition: gdal
823335 was not blocked by any bugs.
823335 was not blocking any bugs.
Added blocking bug(s) of 823335: 824260

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

Bug#822325: rustc: FTBFS in testing: test fail

[Luca BRUNO]

severity 822325 minor
tags 822325 + moreinfo
thanks

On Sat, 23 Apr 2016 14:33:48 +0200 (CEST) Santiago Vila  
wrote:

> This package currently fails to build from source in stretch.
> 
> --
> executing x86_64-unknown-linux-gnu/test/run-pass/tcp-stress.stage2-x86_64-
> unknown-linux-gnu 
> --stdout--
> 
> --stderr--
> thread '' panicked at 'called `Result::unwrap()` on an `Err` value: 
> RecvError', src/libcore/result.rs:746
> 
> --
> 
> The build was made on two different QEMU virtual machines with 4GB RAM
> and 4GB swap, running stretch, using sbuild.

This looks like an artifact due to your build environment, as I just tried 
building on a physical stretch amd64 machine and all tests pass:
"""
summary of 50 test runs: 10108 passed; 0 failed; 88 ignored; 0 measured 
"""

A couple of ideas regarding this test:
 * it is heavily threaded, it may trigger some data races in qemu
 * it may be slow to run and thus timing out. Can you try increasing the
   timeout at the top of src/test/run-pass/tcp-stress.rs?
 * It may be dropping the sender to early. Can you try moving the `drop(tx)`
   just before `process::exit(0)`?

Anyway, this looks like just some test instability on an emulated environment, 
and not a real regression. Thus I'm downgrading it.

Can you please try the small changes I suggested above? If so, it may be worth
reporting it directly to upstream.

Ciao, Luca

Processed: Re: rustc: FTBFS in testing: test fail

[Debian Bug Tracking System]

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

> severity 822325 minor
Bug #822325 [src:rustc] rustc: FTBFS in testing: test fail
Severity set to 'minor' from 'serious'
> tags 822325 + moreinfo
Bug #822325 [src:rustc] rustc: FTBFS in testing: test fail
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#821661: php7 support

[Wolfgang Schweer]

After testing, it seems to be that all you need to do is to replace 
php5-cli with php-cli in debian/control.

Please update the package.

Wolfgang


signature.asc
Description: Digital signature

Bug#807473: Potential data loss and security breach when used with nfs server

[Petter Reinholdtsen]

Control: forwarded -1 https://github.com/mtorromeo/r8168/issues/4

I forwarded this issue upstream, and the response there was that a new
version is available and he wonders if the problem still exist there.

Perhaps something to check out?
-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: Bug#807473: Potential data loss and security breach when used with nfs server

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/mtorromeo/r8168/issues/4
Bug #807473 [r8168-dkms] Potential data loss and security breach when used with 
nfs server
Set Bug forwarded-to-address to 'https://github.com/mtorromeo/r8168/issues/4'.

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

Bug#824256: FTBFS on most arches (test timeout)

[Sébastien Villemot]

Package: src:freefem++
Version: 3.46+dfsg1-2
Severity: serious

Dear Maintainer,

freefem++ FTBFS on most release arches (only armel was successful on build
daemons).

The build timeouts during the testsuite.

I have a similar issue on a local amd64 chroot.

Best,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature

Bug#824253: scamper: FTBFS: usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'

[Chris Lamb]

Source: scamper
Version: 20141211d-1
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,

scamper fails to build from source in unstable/amd64:

  [..]

  checking for arpa/inet.h... yes
  checking fcntl.h usability... yes
  checking fcntl.h presence... yes
  checking for fcntl.h... yes
  checking limits.h usability... yes
  checking limits.h presence... yes
  checking for limits.h... yes
  checking netdb.h usability... yes
  checking netdb.h presence... yes
  checking for netdb.h... yes
  checking net/if_dl.h usability... no
  checking net/if_dl.h presence... no
  checking for net/if_dl.h... no
  checking net/if_types.h usability... no
  checking net/if_types.h presence... no
  checking for net/if_types.h... no
  checking netinet/in.h usability... yes
  checking netinet/in.h presence... yes
  checking for netinet/in.h... yes
  checking poll.h usability... yes
  checking poll.h presence... yes
  checking for poll.h... yes
  checking for stdint.h... (cached) yes
  checking for stdlib.h... (cached) yes
  checking for string.h... (cached) yes
  checking sys/epoll.h usability... yes
  checking sys/epoll.h presence... yes
  checking for sys/epoll.h... yes
  checking sys/event.h usability... no
  checking sys/event.h presence... no
  checking for sys/event.h... no
  checking sys/ioctl.h usability... yes
  checking sys/ioctl.h presence... yes
  checking for sys/ioctl.h... yes
  checking sys/param.h usability... yes
  checking sys/param.h presence... yes
  checking for sys/param.h... yes
  checking sys/socket.h usability... yes
  checking sys/socket.h presence... yes
  checking for sys/socket.h... yes
  checking sys/time.h usability... yes
  checking sys/time.h presence... yes
  checking for sys/time.h... yes
  checking for unistd.h... (cached) yes
  checking ifaddrs.h usability... yes
  checking ifaddrs.h presence... yes
  checking for ifaddrs.h... yes
  checking for sys/sysctl.h... yes
  checking for netinet/ip_fw.h... no
  checking for netinet6/ip6_fw.h... no
  checking for an ANSI C-conforming const... yes
  checking for uid_t in sys/types.h... yes
  checking for int16_t... yes
  checking for int32_t... yes
  checking for mode_t... yes
  checking for off_t... yes
  checking for pid_t... yes
  checking for size_t... yes
  checking for ssize_t... yes
  checking whether struct tm is in sys/time.h or time.h... time.h
  checking for uint16_t... yes
  checking for uint32_t... yes
  checking for uint64_t... yes
  checking for uint8_t... yes
  checking for unistd.h... (cached) yes
  checking for working chown... yes
  checking vfork.h usability... no
  checking vfork.h presence... no
  checking for vfork.h... no
  checking for fork... yes
  checking for vfork... yes
  checking for working fork... yes
  checking for working vfork... (cached) yes
  checking for arc4random... no
  checking for arc4random_uniform... no
  checking for atexit... yes
  checking for calloc... yes
  checking for daemon... yes
  checking for endpwent... yes
  checking for epoll_wait... yes
  checking for ftruncate... yes
  checking for getdtablesize... yes
  checking for gethostname... yes
  checking for getifaddrs... yes
  checking for gettimeofday... yes
  checking for kqueue... no
  checking for memmove... yes
  checking for memset... yes
  checking for mkdir... yes
  checking for poll... yes
  checking for rmdir... yes
  checking for select... yes
  checking for socket... yes
  checking for snprintf... yes
  checking for setproctitle... no
  checking for strcasecmp... yes
  checking for strcasestr... yes
  checking for strdup... yes
  checking for strerror... yes
  checking for strncasecmp... yes
  checking for strtol... yes
  checking for uname... yes
  checking size of long... 8
  checking for struct sockaddr.sa_len... no
  checking for struct ip6_ext... no
  checking for library containing getaddrinfo... none required
  checking for library containing inet_ntop... none required
  checking for library containing sqrt... -lm
  checking for pkg-config... no
  checking for openssl/ssl.h in /usr/local/ssl... no
  checking for openssl/ssl.h in /usr/lib/ssl... no
  checking for openssl/ssl.h in /usr/ssl... no
  checking for openssl/ssl.h in /usr/pkg... no
  checking for openssl/ssl.h in /usr/local... no
  checking for openssl/ssl.h in /usr... no
  checking whether compiling and linking against OpenSSL works... no
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  configure: WARNING: unrecognized options: --disable-maintainer-mode
   /bin/bash ./config.status
  config.status: creating Makefile
  config.status: creating scamper/Makefile
  config.status: creating utils/Makefile
  config.status: creating utils/sc_ally/Makefile
  config.status: creating utils/sc_analysis_dump/Makefile
  config.status: creating utils/sc_attach/Makefile
  config.statu

Bug#821660: please update to upstream release 3.1.29

[Wolfgang Schweer]

After testing (manually updated to upstream 3.1.29 and replacing php5 
with php in debian/control) the package seems to work with php7 - at 
least with slbackup-php.

Please test and update the package to use the upstream release 3.1.29.

Wolfgang


signature.asc
Description: Digital signature

Bug#821659: Bumping severity of PHP 7.0 transition bugs to serious

[Wolfgang Schweer]

On Thu, May 05, 2016 at 10:20:58AM +0200, Ondřej Surý wrote:
> I am bumping the severity of this bug to serious, as we are going to 
> remove src:php5 from Debian and your package is blocking the first 
> step which is removal of php5 from testing.  Please either update your 
> package to support PHP 7.0 or remove the package from Debian unstable 
> alltogether.

After testing (with smarty3 manually updated to use upstream release 
3.1.29) this seems to make the package work with php7.

-

diff --git a/debian/control b/debian/control
index 68f7eac..1b15544 100644
--- a/debian/control
+++ b/debian/control
@@ -17,12 +17,12 @@ Package: slbackup-php
 Architecture: all
 Depends:
  ${misc:Depends},
- libapache2-mod-php5 | php5-cgi,
+ php,
  apache2 | httpd,
  ssh,
- php5-cli,
+ php-cli,
  smarty3,
- smarty-gettext (>= 1.0b1-7),
+ smarty-gettext,
 Suggests:
  x-www-browser,
  slbackup,
diff --git a/src/functions.php b/src/functions.php
index 7f52734..89524da 100644
--- a/src/functions.php
+++ b/src/functions.php
@@ -75,7 +75,7 @@ function loadLocale () {
$lang_accept = array () ; 
$lang_accept = explode (",", $_SERVER['HTTP_ACCEPT_LANGUAGE']); 
for ($i = 0 ; $i < count ($lang_accept) ; $i++ ) {
-   $lang_accept[$i] = split(";", $lang_accept[$i]) ; 
+   $lang_accept[$i] = preg_split(';', $lang_accept[$i]) ;
$lang_accept[$i] = $lang_accept[$i][0] ; 
}
 
@@ -101,13 +101,13 @@ function loadLocale () {
$locales = array();
$locales_utf8 = array();
if (isset($found_locale) && !empty($lang_accept[0])) {
-   $found_locale_tuple = split('_', $found_locale);
+   $found_locale_tuple = preg_split('_', $found_locale);
if (count($found_locale_tuple) > 1) {
$locales[] = $found_locale;
$locales_utf8[] = $found_locale.'.UTF-8';
}
foreach ($lang_accept as $lang) {
-   $lang_tuple = split('-',$lang);
+   $lang_tuple = preg_split('-',$lang);
if (count($lang_tuple) > 1) {
$language = strtolower($lang_tuple[0]);
$country = strtoupper($lang_tuple[1]);
 
--

Wolfgang


signature.asc
Description: Digital signature