Bug#808560: [buildd-tools-devel] Bug#808560: sbuild: Use of uninitialized value $_ in concatenation (.)

[Niko Tyni]

On Wed, Dec 23, 2015 at 11:27:43AM +0200, Niko Tyni wrote:

> I can confirm that sbuild works fine for me again with your patch.
> 
> Please consider an upload soon, this is blocking the Perl 5.22
> transition.

Oh, and we should probably add a Breaks entry on the perl
side for earlier versions when this is fixed, to make sure
partial upgrades pull in a working version.

I've filed #808805 about that.
-- 
Niko Tyni   nt...@debian.org

Bug#808810: python-pygal: incompatibility with lxml 3.5, fails with exception: ValueError: Invalid PI name 'xml'

[Daniele Forsi]

Package: python-pygal
Version: 1.7.0-0-g41186be+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

there is a bug in pygal that makes it crash even when running the first example 
in its documentation, a bug which seems to have been fixed about a month ago in 
version 2.0.11 of pygal; here is the relevant issue 
https://github.com/Kozea/pygal/issues/282

This bugs makes it impossible to generate any SVG (BTW, in this package's 
description, "Python svg graph plotting library", "svg" would be better written 
in uppercase).

This is the example from 
http://www.pygal.org/en/latest/documentation/types/line.html
import pygal

line_chart = pygal.Line()
line_chart.title = 'Browser usage evolution (in %)'
line_chart.x_labels = map(str, range(2002, 2013))
line_chart.add('Firefox', [None, None,0, 16.6,   25,   31, 36.4, 45.5, 
46.3, 42.8, 37.1])
line_chart.add('Chrome',  [None, None, None, None, None, None,0,  3.9, 
10.8, 23.8, 35.3])
line_chart.add('IE',  [85.8, 84.6, 84.7, 74.5,   66, 58.6, 54.7, 44.8, 
36.2, 26.6, 20.1])
line_chart.add('Others',  [14.2, 15.4, 15.3,  8.9,9, 10.4,  8.9,  5.8,  
6.7,  6.8,  7.5])
line_chart.render()

and this is the traceback when running it interactively:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/pygal/ghost.py", line 122, in render
.make_instance(overrides=kwargs)
  File "/usr/lib/python2.7/dist-packages/pygal/ghost.py", line 116, in 
make_instance
self.xml_filters)
  File "/usr/lib/python2.7/dist-packages/pygal/graph/line.py", line 33, in 
__init__
super(Line, self).__init__(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pygal/graph/base.py", line 47, in 
__init__
self.svg = Svg(self)
  File "/usr/lib/python2.7/dist-packages/pygal/svg.py", line 50, in __init__
u('xml'), u("version='1.0' encoding='utf-8'"))]
  File "src/lxml/lxml.etree.pyx", line 3039, in 
lxml.etree.ProcessingInstruction (src/lxml/lxml.etree.c:81073)
ValueError: Invalid PI name 'xml'

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

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

Versions of packages python-pygal depends on:
pn  python:any  

python-pygal recommends no packages.

python-pygal suggests no packages.

-- no debconf information

Processed: severity of 805725 is normal

[Debian Bug Tracking System]

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

> severity 805725 normal
Bug #805725 [docker.io] docker.io is not installable. The 
post-installation-script does not work.
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#808814: checkbox-ng: FTBFS: ImportError: cannot import name 'JobTreeNode'

[Chris Lamb]

Source: checkbox-ng
Version: 0.20.1-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,

checkbox-ng fails to build from source in unstable/amd64:

  [..]

  test_help (test_main.TestMain) ... ERROR
  test_run_without_args (test_main.TestMain) ... ERROR
  test_version (test_main.TestMain) ... ERROR
  test_misc (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: test_help (commands.test_sru.TestSru)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/commands/test_sru.py",
 line 40, in test_help
  main(['sru', '--help'])
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/main.py",
 line 41, in main
  raise SystemExit(CheckboxTool().main(argv))
File "/usr/lib/python3/dist-packages/plainbox/impl/clitools.py", line 310, 
in main
  self._parser = self.construct_parser(early_ns)
File "/usr/lib/python3/dist-packages/plainbox/impl/clitools.py", line 469, 
in construct_parser
  self.add_subcommands(subparsers, early_ns)
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/tools.py",
 line 96, in add_subcommands
  from checkbox_ng.commands.launcher import LauncherCommand
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/commands/launcher.py",
 line 32, in 
  from checkbox_ng.commands.newcli import CliInvocation2
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/commands/newcli.py",
 line 53, in 
  from checkbox_ng.misc import SelectableJobTreeNode
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/misc.py",
 line 30, in 
  from plainbox.impl.job import JobTreeNode
  ImportError: cannot import name 'JobTreeNode'
  
  ==
  ERROR: test_help (test_main.TestMain)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/test_main.py",
 line 50, in test_help
  main(['--help'])
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/main.py",
 line 41, in main
  raise SystemExit(CheckboxTool().main(argv))
File "/usr/lib/python3/dist-packages/plainbox/impl/clitools.py", line 310, 
in main
  self._parser = self.construct_parser(early_ns)
File "/usr/lib/python3/dist-packages/plainbox/impl/clitools.py", line 469, 
in construct_parser
  self.add_subcommands(subparsers, early_ns)
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/tools.py",
 line 96, in add_subcommands
  from checkbox_ng.commands.launcher import LauncherCommand
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/commands/launcher.py",
 line 32, in 
  from checkbox_ng.commands.newcli import CliInvocation2
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/commands/newcli.py",
 line 53, in 
  from checkbox_ng.misc import SelectableJobTreeNode
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/misc.py",
 line 30, in 
  from plainbox.impl.job import JobTreeNode
  ImportError: cannot import name 'JobTreeNode'
  
  ==
  ERROR: test_run_without_args (test_main.TestMain)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/test_main.py",
 line 87, in test_run_without_args
  main([])
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/main.py",
 line 41, in main
  raise SystemExit(CheckboxTool().main(argv))
File "/usr/lib/python3/dist-packages/plainbox/impl/clitools.py", line 310, 
in main
  self._parser = self.construct_parser(early_ns)
File "/usr/lib/python3/dist-packages/plainbox/impl/clitools.py", line 469, 
in construct_parser
  self.add_subcommands(subparsers, early_ns)
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/tools.py",
 line 96, in add_subcommands
  from checkbox_ng.commands.launcher import LauncherCommand
File 
"/home/lamby/temp/cdt.20151223115223.6HzvVjCF7r/checkbox-ng-0.20.1/checkbox_ng/commands/launcher.py",
 line 32, in 
  from checkbox_ng.commands.newcli import CliInvocation2
File 

Processed: reassign 808758 to debhelper, forcibly merging 808603 808758

[Debian Bug Tracking System]

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

> # Another case of #808603 in debhelper
> reassign 808758 debhelper
Bug #808758 [src:jpeginfo] jpeginfo: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug reassigned from package 'src:jpeginfo' to 'debhelper'.
No longer marked as found in versions jpeginfo/1.6.0-6.
Ignoring request to alter fixed versions of bug #808758 to the same values 
previously set
> forcemerge 808603 808758
Bug #808603 [debhelper] debhelper: dh_installmanpages is broken
Bug #808588 [debhelper] code2html: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug #808589 [debhelper] cplay: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Bug #808590 [debhelper] funny-manpages: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug #808592 [debhelper] rinetd: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Bug #808758 [debhelper] jpeginfo: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Marked as found in versions debhelper/9.20151220.
Bug #808588 [debhelper] code2html: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug #808589 [debhelper] cplay: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Bug #808590 [debhelper] funny-manpages: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug #808592 [debhelper] rinetd: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Merged 808588 808589 808590 808592 808603 808758
> thanks
Stopping processing here.

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

Bug#808603: [debhelper-devel] Bug#808603: debhelper: dh_installmanpages is broken

[Axel Beckert]

Control: tag -1 + pending

Hi,

Niko Tyni wrote:
> It looks like 
>  
> https://anonscm.debian.org/cgit/debhelper/debhelper.git/commit/?id=1bd369cc52115fd179a46d6f8d9af6e9f126ffa8
> 
> broke dh_installmanpages, which has
> @allpackages=getpackages('');
> 
> The new code handles a missing argument but not an empty one.
> 
> +   my ($type) = @_;
> +   $type //= 'both';
> 
> This made at least four packages FTBFS, see
>  #808592 #808590 #808589 #808588

At least one more in the meanwhile: #808758

> Not sure which side to fix so I'm leaving it to you.  

Niels has pushed a fix to git two days ago:

https://anonscm.debian.org/cgit/debhelper/debhelper.git/commit/?id=61df6eb53302cadf11c1e0aa87b2ff0af207da2f

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: [debhelper-devel] Bug#808603: debhelper: dh_installmanpages is broken

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #808603 [debhelper] debhelper: dh_installmanpages is broken
Bug #808588 [debhelper] code2html: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug #808589 [debhelper] cplay: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Bug #808590 [debhelper] funny-manpages: FTBFS: dh_installmanpages: getpackages: 
First argument must be one of "arch", "indep" or "both"
Bug #808592 [debhelper] rinetd: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Bug #808758 [debhelper] jpeginfo: FTBFS: dh_installmanpages: getpackages: First 
argument must be one of "arch", "indep" or "both"
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

-- 
808588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808588
808589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808589
808590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808590
808592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808592
808603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808603
808758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#808560: [buildd-tools-devel] Bug#808560: sbuild: Use of uninitialized value $_ in concatenation (.)

[John David Anglin]

On 2015-12-23, at 4:27 AM, Niko Tyni wrote:

> On Tue, Dec 22, 2015 at 09:00:20AM +0200, Niko Tyni wrote:
>> On Tue, Dec 22, 2015 at 07:48:11AM +0100, Johannes Schauer wrote:
> 
>>> If the problem is this change of behaviour as you described it, then the 
>>> fix is
>>> a very simple one:
>> 
>> Cool, thanks! I'm not sure if there are other problems, this was the
>> one I found first.
> 
> I can confirm that sbuild works fine for me again with your patch.

Same here.

Thanks,
--
John David Anglin   dave.ang...@bell.net

Bug#806560: marked as done (python3-udiskie/python-udiskie do not start)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 13:08:54 +
with message-id 
and subject line Bug#806560: fixed in python-udiskie 1.4.1-1
has caused the Debian Bug report #806560,
regarding python3-udiskie/python-udiskie do not start
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.)


-- 
806560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: python3-udiskie/python-udiskie do not start
Package: python3-udiskie
Version: 1.3.2-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,

udiskie fails to start up; the icon appears in the system tray but no menu 
appears when
I click on it.

With python-udiskie, xsession-errors says the following:

--
/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You 
have imported the Gtk 2.0 module.  Because Gtk 2.0 was not designed for use 
with introspection some of the interfaces and API will fail.  As such this is 
not supported by the pygobject development team and we encourage you to port 
your app to Gtk 3 or greater. PyGTK is the recomended python module to use with 
Gtk 2.0
  warnings.warn(warn_msg, RuntimeWarning)
/usr/lib/python2.7/dist-packages/udiskie/prompt.py:24: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk', 
'2.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
Typelib for 'libnotify' is not available. Possible causes include:
- libnotify is not installed
- the typelib is provided by a separate package
- libnotify was built with introspection disabled

Starting udiskie without notifications.
not mounting /org/freedesktop/UDisks2/block_devices/mmcblk0p1: already mounted
"sni-qt/4318" WARN  22:14:33.168 void StatusNotifierItemFactory::connectToSnw() 
Invalid interface to SNW_SERVICE 
[i3bar/src/xcb.c:679] ERROR: Window 0282 violates the XEMBED protocol, 
_XEMBED_INFO not set
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 319, in 
_activate
self._popup_menu(icon, button=0, time=Gtk.get_current_event_time())
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in 
_popup_menu
m.popup(parent_menu_shell=None,
AttributeError: 'Menu' object has no attribute 'popup'
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 319, in 
_activate
self._popup_menu(icon, button=0, time=Gtk.get_current_event_time())
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in 
_popup_menu
m.popup(parent_menu_shell=None,
AttributeError: 'Menu' object has no attribute 'popup'
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 319, in 
_activate
self._popup_menu(icon, button=0, time=Gtk.get_current_event_time())
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in 
_popup_menu
m.popup(parent_menu_shell=None,
AttributeError: 'Menu' object has no attribute 'popup'
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/udiskie/tray.py", line 325, in 
_popup_menu
m.popup(parent_menu_shell=None,
AttributeError: 'Menu' object has no attribute 'popup'
--

With python3-udiskie installed, xsession-errors have the following error:

--
/usr/lib/python3/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have 
imported the Gtk 2.0 module.  Because Gtk 2.0 was not designed for use with 
introspection some of the interfaces and API will fail.  As such this is not 
supported by the pygobject development team and we encourage you to port your 
app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 
2.0
  warnings.warn(warn_msg, RuntimeWarning)
/usr/bin/udiskie:9: PyGIWarning: Gtk was imported without specifying a version 
first. Use gi.require_version('Gtk', '2.0') before import to ensure that the 
right version gets loaded.
  load_entry_point('udiskie==1.3.2', 'console_scripts', 'udiskie')()
Typelib for 'libnotify' is not available. Possible causes include:
- libnotify is not installed
- the typelib is provided by a separate package
- libnotify was built with introspection disabled

Starting udiskie without notifications.
not mounting /org/freedesktop/UDisks2/block_devices/mmcblk0p1: already mounted
"sni-qt/5786" WARN  22:20:51.131 void StatusNotifierItemFactory::connectToSnw() 
Invalid interface to 

Processed: libperl-apireference-perl: FTBFS: missing support for Perl 5.22.1

[Debian Bug Tracking System]

Processing control commands:

> block 796345 with -1
Bug #796345 [release.debian.org] transition: perl 5.22
796345 was blocked by: 787468 808325 807492 805391 799118 807423 790532 802939 
807400 807493 804603 807478 796923 807038 808444 787493 808329 788073 808629 
795127 808583 787453 808560 807324 807422 807474 804590 807401 787450
796345 was blocking: 798309 801659 801660 801661 801662 801663
Added blocking bug(s) of 796345: 808825

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

Bug#808825: libperl-apireference-perl: FTBFS: missing support for Perl 5.22.1

[Niko Tyni]

Package: libperl-apireference-perl
Version: 0.21-2
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition
Control: block 796345 with -1

This package fails to build with Perl 5.22.1, currently in unstable.

  [...]
  Processing: 5.22.0
  echo Current Perl is `perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
  Current Perl is 5_022_001.pm
  test -f lib/Perl/APIReference/V`perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
  debian/rules:8: recipe for target 'regenerated-stamp' failed
 
-- 
Niko Tyni   nt...@debian.org

Bug#808839: fop: Exception java.lang.IllegalArgumentException: URI is not hierarchical

[Sylvain Joubert]

Package: fop
Version: 1:2.0+dfsg-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since I've updated my fop version (to 1:1.1.dfsg2-1) I can't use it anymore as
I get the following error:

[ERROR] FOP - Exception java.lang.IllegalArgumentException: URI is not hierarchical
at java.io.File.(File.java:418)
at org.apache.fop.fonts.FontCache.addFont(FontCache.java:335)
at
org.apache.fop.fonts.autodetect.FontInfoFinder.getFontInfoFromCustomFont(FontInfoFinder.java:157)
at
org.apache.fop.fonts.autodetect.FontInfoFinder.find(FontInfoFinder.java:269)
at org.apache.fop.fonts.FontAdder.add(FontAdder.java:63)
at
org.apache.fop.fonts.FontDetectorFactory$DefaultFontDetector.detect(FontDetectorFactory.java:110)
at
org.apache.fop.fonts.FontManager.autoDetectFonts(FontManager.java:229)
at
org.apache.fop.fonts.DefaultFontConfigurator.configure(DefaultFontConfigurator.java:82)
at
org.apache.fop.render.PrintRendererConfigurator.getCustomFontCollection(PrintRendererConfigurator.java:147)
at
org.apache.fop.render.PrintRendererConfigurator.setupFontInfo(PrintRendererConfigurator.java:127)
at
org.apache.fop.render.intermediate.IFUtil.setupFonts(IFUtil.java:170)
at
org.apache.fop.render.intermediate.IFRenderer.setupFontInfo(IFRenderer.java:187)
at
org.apache.fop.area.RenderPagesModel.(RenderPagesModel.java:75)
at
org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:135)
at org.apache.fop.area.AreaTreeHandler.(AreaTreeHandler.java:105)
at
org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:350)
at org.apache.fop.fo.FOTreeBuilder.(FOTreeBuilder.java:107)
at org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:104)
at org.apache.fop.apps.Fop.(Fop.java:78)
at org.apache.fop.apps.FOUserAgent.newFop(FOUserAgent.java:179)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:107)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)

I also get these warnings just before, maybe it's related:

[INFO] Type1FontLoader - No Unicode mapping for glyph: AFM Char: 153 (anglearc)
[INFO] Type1FontLoader - No Unicode mapping for glyph: AFM Char: 166 (diameter)
[WARN] FOUserAgent - Unable to load font file:
file:/usr/share/fonts/X11/Type1/c059036l.pfb. Reason:
java.io.FileNotFoundException: Neither an AFM nor a PFM file was found for
file:/usr/share/fonts/X11/Type1/c059036l.pfb
[WARN] FOUserAgent - Unable to load font file:
file:/usr/share/fonts/truetype/noto/NotoSerifKhmer-Bold.ttf. Reason:
java.lang.ArrayIndexOutOfBoundsException: 342
[WARN] FOUserAgent - Unable to load font file:
file:/usr/share/fonts/truetype/noto/NotoSerifKhmer-Regular.ttf. Reason:
java.lang.ArrayIndexOutOfBoundsException: 342
[WARN] FOUserAgent - Unable to load font file:
file:/usr/share/fonts/truetype/noto/NotoSansKhmer-Regular.ttf. Reason:
java.lang.ArrayIndexOutOfBoundsException: 223
[WARN] FOUserAgent - Unable to load font file:
file:/usr/share/fonts/truetype/noto/NotoSansKhmer-Bold.ttf. Reason:
java.lang.ArrayIndexOutOfBoundsException: 223

For now, the only workaround I've found is to downgrade fop to its 'stable'
version (1:2.0+dfsg-4)



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable-updates'), (800, 'stable'), (700, 
'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages fop depends on:
ii  default-jre-headless [java2-runtime-headless]2:1.7-52.1
ii  libfop-java  1:2.0+dfsg-4
ii  openjdk-7-jre-headless [java2-runtime-headless]  7u91-2.6.3-1

Versions of packages fop recommends:
ii  libsaxon-java  1:6.5.5-10

Versions of packages fop suggests:
pn  fop-doc  

-- no debconf information

Bug#808826: libkavorka-perl: FTBFS: Can't locate object method "_set_declared_name" via package "Kavorka::Sub::Fun"

[Niko Tyni]

Package: libkavorka-perl
Version: 0.036-1
Severity: serious
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=109841

This package fails to build on current sid.

It's not clear if this is a Perl 5.22 regression or something else,
but it fails reliably here.

  t/01basic.t  
  ok 1 - use Kavorka;
  1..1
  ok
  Can't locate object method "_set_declared_name" via package 
"Kavorka::Sub::Fun" at /<>/blib/lib/Kavorka/Sub.pm line 182.
  t/02named-functions.t .. 
  Dubious, test returned 255 (wstat 65280, 0xff00)
  No subtests run 
  [...]
  Files=43, Tests=1, 16 wallclock secs ( 0.22 usr  0.06 sys + 15.33 cusr  0.68 
csys = 16.29 CPU)
  Result: FAIL
  Failed 41/43 test programs. 0/1 subtests failed.

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

Processed: bug 808825 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=110561

[Debian Bug Tracking System]

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

> forwarded 808825 https://rt.cpan.org/Ticket/Display.html?id=110561
Bug #808825 [libperl-apireference-perl] libperl-apireference-perl: FTBFS: 
missing support for Perl 5.22.1
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=110561'.
> thanks
Stopping processing here.

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

Bug#803033: marked as done (catdoc: non-free Unicode files)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 16:26:35 +
with message-id 
and subject line Bug#803033: fixed in catdoc 1:0.94.3~git20151007.fd634c2+dfsg-1
has caused the Debian Bug report #803033,
regarding catdoc: non-free Unicode files
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.)


-- 
803033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: catdoc
Version: 0.94.4-1.1
Severity: serious

According to their headers, the following files are non-free:

Files:
charsets/8859-1.txt 

   
charsets/8859-2.txt 

   
charsets/8859-3.txt 

   
charsets/8859-4.txt 

   
charsets/8859-5.txt 

   
charsets/8859-6.txt 

   
charsets/8859-7.txt 

   
charsets/8859-8.txt 

   
charsets/8859-9.txt 

   
charsets/big5.txt   

   
charsets/cns11643.txt   

   
charsets/jis0201.txt

   
charsets/jis0208.txt

   
charsets/jis0212.txt

   
charsets/shiftjis.txt   

   
Copyright:  

   
1991-1995 Unicode, Inc  

   
License: Unicode-noDistribute   

 [disclaimer excluded]
 .
 Recipient is granted the right to make copies in any form for
 internal distribution and to freely use the information supplied
 in the creation of products supporting Unicode.  Unicode, Inc.
 specifically excludes the right to re-distribute this file directly
 to third parties or other organizations whether for profit or not.

Please investigate.

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

---

"All government, of course, is against liberty.
-- H. L. Mencken


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: catdoc
Source-Version: 1:0.94.3~git20151007.fd634c2+dfsg-1

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

A 

Bug#796931: gnupg-agent: no longer writes $GNUPGHOME/gpg-agent-info-$(hostname) file

[Axel Beckert]

Hi,

Thorsten Glaser wrote:
> severity 796931 serious

I agree with this severity. This issue breaks quite some automatic
stuff and is a severe and unexpected regression.

> It’s actually worse: when using startx or no X environment
> at all, I can no longer use gpg-agent:

Interestingly it still works for me under X, but there are chances
that I used gnupg/gnupg2 from experimental where "gpg" is gpg2.

On some other host I just ran into the issue that this no more works:

> tglase@tglase-nb:~ $ eval $(gpg-agent --daemon --sh)

The point is that neither "gpg-agent --daemon --sh" outputs any shell
code to be eval'ed anymore nor does "gpg-agent --daemon /usr/bin/zsh"
work for me as advertised in gpg-agent's man page (no GPG_* named
environment variables set inside). Because if I try to sign something
inside that shell, it claims that "gpg-agent is not available in this
session" as it does for Thorsten:

> You need a passphrase to unlock the secret key for
> user: "Thorsten Glaser (tarent GmbH) "
> 4096-bit RSA key, ID 5EB8D3B3, created 2009-01-05
> 
> gpg: gpg-agent is not available in this session

Having "gpg-agent --daemon" outputting lines like
"GPG_AGENT_INFO=/tmp/gpg-4hLrL9/S.gpg-agent:5152:1; export
GPG_AGENT_INFO;" respectively setting this in the child process'
environment as it did before would fix the issue for me. But there
seem to be other interfaces I haven't used so far, too.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#808853: libconfig-model-lcdproc-perl: FTBFS: Failed test 'Read configuration and created instance with init() method with warning check '

[Chris Lamb]

Source: libconfig-model-lcdproc-perl
Version: 2.042-4
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,

libconfig-model-lcdproc-perl fails to build from source in unstable/amd64:

  [..]
 dh_auto_test
perl Build test --verbose 1
  
  #   Failed test 'Read configuration and created instance with init() method 
with warning check '
  #   at /usr/share/perl5/Config/Model/Tester.pm line 146.
  # didn't find a warning
  # expected to find warning: (?^:missing DriverPath dir)
  
  #   Failed test 'first check 'server DriverPath' value (mode standard)'
  #   at /usr/share/perl5/Config/Model/Tester.pm line 249.
  #  got: 'server/drivers/'
  # expected: '/usr/lib/x86_64-linux-gnu/lcdproc/'
  
  #   Failed test 'first check 'server DriverPath' value'
  #   at /usr/share/perl5/Config/Model/Tester.pm line 249.
  #  got: '/usr/lib/lcdproc/'
  # expected: '/usr/lib/x86_64-linux-gnu/lcdproc/'
  
  #   Failed test 'Read configuration and created instance with init() method 
with warning check '
  #   at /usr/share/perl5/Config/Model/Tester.pm line 146.
  # didn't find a warning
  # expected to find warning: (?^:missing DriverPath dir)
  
  #   Failed test 'Read configuration and created instance with init() method 
with warning check '
  #   at /usr/share/perl5/Config/Model/Tester.pm line 146.
  # didn't find a warning
  # expected to find warning: (?^:missing DriverPath dir)
  # Looks like you failed 5 tests of 42.
  t/model_tests.t .. 
  ok 1 - compiled
  # Beginning lcdd test (t/model_tests.d/lcdd-test-conf.pl)
  # lcdd uses LCDd model on file LCDd.conf
  # Beginning subtest lcdd t0
  ok 2 - Copied lcdd example t0
  not ok 3 - Read configuration and created instance with init() method with 
warning check 
  ok 4 - apply_fixes called
  ok 5 - Ran dump_tree
  ok 6 - Dumped lcdd config tree in full mode
  ok 7 - Dumped lcdd config tree in custom mode
  ok 8 - first check 'server Hello:0' value
  ok 9 - first check 'server Hello:1' value
  ok 10 - first check 'server Driver' value
  not ok 11 - first check 'server DriverPath' value (mode standard)
  not ok 12 - first check 'server DriverPath' value
  ok 13 - first check 'curses Size' value
  ok 14 - first check 'server AutoRotate' value
  ok 15 - lcdd write back done
  ok 16 - Created instance lcdd-test-t0-w
  ok 17 - Dumped second lcdd config tree in custom mode
  ok 18 - compare original lcdd custom data with 2nd instance custom data
  ok 19 - check that original lcdd file was not clobbered
  # End of subtest lcdd t0
  # Beginning subtest lcdd LDCd-0.5.5
  ok 20 - Copied lcdd example LDCd-0.5.5
  not ok 21 - Read configuration and created instance with init() method with 
warning check 
  ok 22 - apply_fixes called
  ok 23 - Ran dump_tree
  ok 24 - Dumped lcdd config tree in full mode
  ok 25 - Dumped lcdd config tree in custom mode
  ok 26 - lcdd write back done
  ok 27 - Created instance lcdd-test-LDCd-0.5.5-w
  ok 28 - Dumped second lcdd config tree in custom mode
  ok 29 - compare original lcdd custom data with 2nd instance custom data
  ok 30 - check that original lcdd file was not clobbered
  # End of subtest lcdd LDCd-0.5.5
  # Beginning subtest lcdd LDCd-0.5.6
  ok 31 - Copied lcdd example LDCd-0.5.6
  not ok 32 - Read configuration and created instance with init() method with 
warning check 
  ok 33 - apply_fixes called
  ok 34 - Ran dump_tree
  ok 35 - Dumped lcdd config tree in full mode
  ok 36 - Dumped lcdd config tree in custom mode
  ok 37 - lcdd write back done
  ok 38 - Created instance lcdd-test-LDCd-0.5.6-w
  ok 39 - Dumped second lcdd config tree in custom mode
  ok 40 - compare original lcdd custom data with 2nd instance custom data
  ok 41 - check that original lcdd file was not clobbered
  # End of subtest lcdd LDCd-0.5.6
  # End of lcdd test
  ok 42 - test memory cycle
  1..42
  Dubious, test returned 5 (wstat 1280, 0x500)
  Failed 5/42 subtests 
  
  Test Summary Report
  ---
  t/model_tests.t (Wstat: 1280 Tests: 42 Failed: 5)
Failed tests:  3, 11-12, 21, 32
Non-zero exit status: 5
  Files=1, Tests=42,  2 wallclock secs ( 0.02 usr  0.01 sys +  1.47 cusr  0.05 
csys =  1.55 CPU)
  Result: FAIL
  Failed 1/1 test programs. 5/42 subtests failed.
  dh_auto_test: perl Build test --verbose 1 returned exit code 5
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 5

  [..]

The full build log is attached.


Regards,

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


libconfig-model-lcdproc-perl.2.042-4.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808855: ruby-i18n-inflector: FTBFS: Error: test: inflector.strict kind: checks what is the inflection kind of the given token(I18nInflectorTest): I18n::InvalidLocale: :en is not a valid locale

[Chris Lamb]

Source: ruby-i18n-inflector
Version: 2.6.6-2
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,

ruby-i18n-inflector fails to build from source in unstable/amd64:

  [..]

  
===
  Error: test: inflector.strict kind: checks what is the inflection kind of the 
given token(I18nInflectorTest): I18n::InvalidLocale: :en is not a valid locale
  /usr/lib/ruby/vendor_ruby/i18n.rb:284:in `enforce_available_locales!'
  /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale='
  /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale='
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/test/inflector_test.rb:39:in
 `setup'
  
===/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:24:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:25:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data_strict.rb:42:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/backend.rb:331:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
  E
  
===
  Error: test: inflector.strict kinds: lists inflection 
kinds(I18nInflectorTest): I18n::InvalidLocale: :en is not a valid locale
  /usr/lib/ruby/vendor_ruby/i18n.rb:284:in `enforce_available_locales!'
  /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale='
  /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale='
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/test/inflector_test.rb:39:in
 `setup'
  
===/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:24:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:25:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data_strict.rb:42:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/backend.rb:331:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/debian/ruby-i18n-inflector/usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
  
  E
  
===
  Error: test: inflector.strict locale_supported?: checks if a language 
supports inflection(I18nInflectorTest): I18n::InvalidLocale: :en is not a valid 
locale
  /usr/lib/ruby/vendor_ruby/i18n.rb:284:in `enforce_available_locales!'
  /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale='
  /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale='
  
/home/lamby/temp/cdt.20151223193103.MWyTfoa3OE/ruby-i18n-inflector-2.6.6/test/inflector_test.rb:39:in
 `setup'
  

Bug#808856: elki: FTBFS: annot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-source-plugin:jar:2.2.1

[Chris Lamb]

Source: elki
Version: 0.7.0-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,

elki fails to build from source in unstable/amd64:

  [..]
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.270 s
  [INFO] Finished at: 2015-12-23T19:33:57+00:00
  [INFO] Final Memory: 7M/236M
  [INFO] 

  [ERROR] Plugin org.apache.maven.plugins:maven-source-plugin:2.2.1 or one of 
its dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-source-plugin:jar:2.2.1 has not been downloaded 
from it before. -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
  debian/rules:24: recipe for target 'override_dh_auto_clean' failed
  make[1]: *** [override_dh_auto_clean] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223193158.5Ksj0xQQW8/elki-0.7.0'
  debian/rules:11: recipe for target 'clean' failed
  make: *** [clean] Error 2

  [..]

The full build log is attached.


Regards,

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


elki.0.7.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808674: marked as done (networking-mlnx: FTBFS: AttributeError: 'module' object has no attribute 'VIF_TYPE_MLNX_DIRECT')

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 16:32:05 +
with message-id 
and subject line Bug#808674: fixed in networking-mlnx 1:7.0.0-1
has caused the Debian Bug report #808674,
regarding networking-mlnx: FTBFS: AttributeError: 'module' object has no 
attribute 'VIF_TYPE_MLNX_DIRECT'
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.)


-- 
808674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-mlnx
Version: 2015.1~b1+git20150502+400747aa20-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

networking_mlnx.tests.unit.ml2.test_mechanism_sdn.SDNMechanismConfigTests.test_valid_config
networking_mlnx.tests.unit.ml2.test_mechanism_sdn.SDNMechanismConfigTests.test_valid_config
 ... ok

==
FAIL: 
unittest2.loader._FailedTest.networking_mlnx.tests.unit.ml2.drivers.test_mech_mlnx
unittest2.loader._FailedTest.networking_mlnx.tests.unit.ml2.drivers.test_mech_mlnx
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
networking_mlnx.tests.unit.ml2.drivers.test_mech_mlnx
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_mlnx/tests/unit/ml2/drivers/test_mech_mlnx.py", line 24, in 

class MlnxMechanismBaseTestCase(base.AgentMechanismBaseTestCase):
  File "networking_mlnx/tests/unit/ml2/drivers/test_mech_mlnx.py", line 25, in 
MlnxMechanismBaseTestCase
VIF_TYPE = portbindings.VIF_TYPE_MLNX_DIRECT
AttributeError: 'module' object has no attribute 'VIF_TYPE_MLNX_DIRECT'


==
FAIL: 
unittest2.loader._FailedTest.networking_mlnx.tests.unit.ml2.drivers.test_mlnx_comm_utils
unittest2.loader._FailedTest.networking_mlnx.tests.unit.ml2.drivers.test_mlnx_comm_utils
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
networking_mlnx.tests.unit.ml2.drivers.test_mlnx_comm_utils
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_mlnx/tests/unit/ml2/drivers/test_mlnx_comm_utils.py", line 
17, in 
from oslo.config import cfg
ImportError: No module named config


==
FAIL: 
unittest2.loader._FailedTest.networking_mlnx.tests.unit.ml2.drivers.test_mlnx_neutron_agent
unittest2.loader._FailedTest.networking_mlnx.tests.unit.ml2.drivers.test_mlnx_neutron_agent
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
networking_mlnx.tests.unit.ml2.drivers.test_mlnx_neutron_agent
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_mlnx/tests/unit/ml2/drivers/test_mlnx_neutron_agent.py", 
line 22, in 
from networking_mlnx.plugins.ml2.drivers.mlnx.agent import (
  File 
"networking_mlnx/plugins/ml2/drivers/mlnx/agent/mlnx_eswitch_neutron_agent.py", 
line 35, in 
from neutron.openstack.common import loopingcall
ImportError: cannot import name loopingcall


--
Ran 15 tests in 1.579s

FAILED (failures=3)
debian/rules:25: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/networking-mlnx-2015.1~b1+git20150502+400747aa20'
debian/rules:12: recipe for target 'build' failed
make: 

Bug#808842: glib2.0: FTBFS with PCRE 8.38: regex (?(?<ab)) produces different error

[Simon McVittie]

Source: glib2.0
Version: 2.46.2-1
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=759808

GLib 2.46.2-2 FTBFS with a regex test failure on all release architectures
except amd64, where it was built by the maintainer. The same test is also
now failing with the prebuilt 2.46.2-1 on ci.debian.net, so this is not
actually a regression in 2.46.2-2; instead, it's a regression in the new
libpcre3.

The problem appears to be that certain invalid regexes are diagnosed
differently (different error code) with PCRE 8.38.
I have sent a report and patch to GNOME (also attached),


X-Debbugs-Cc set to libpc...@packages.debian.org. Matthew, it would be
great if you could upload new pcre3 versions to experimental initially,
and/or run the GLib regex test against them before uploading to unstable
(install libglib2.0-tests and run
"/usr/lib/glib2.0/installed-tests/glib/regex" - no special options are
needed, and it will exit 0 for success or nonzero for failure).

Regards,
S
>From 414259817e646b8c33907e7ddb3971008a2bc17f Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 23 Dec 2015 15:03:16 +
Subject: [PATCH] regex test: expect ASSERTION_EXPECTED for /(?(?).

The regex /(?Pfoo)\g
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=759808
---
 glib/tests/regex.c | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/glib/tests/regex.c b/glib/tests/regex.c
index 09083a3..777616a 100644
--- a/glib/tests/regex.c
+++ b/glib/tests/regex.c
@@ -2261,7 +2261,14 @@ main (int argc, char *argv[])
   TEST_NEW_FAIL ("^(?(0)f|b)oo", 0, G_REGEX_ERROR_INVALID_CONDITION);
   TEST_NEW_FAIL ("(?<=\\C)X", 0, G_REGEX_ERROR_SINGLE_BYTE_MATCH_IN_LOOKBEHIND);
   TEST_NEW_FAIL ("(?!\\w)(?R)", 0, G_REGEX_ERROR_INFINITE_LOOP);
+#if PCRE_MAJOR > 8 || (PCRE_MAJOR == 8 && PCRE_MINOR >= 38)
+  /* The expected errors changed here. */
+  TEST_NEW_FAIL ("(?Pfoo)\\g

Bug#806560: python3-udiskie/python-udiskie do not start

[Thomas Gläßle]

Hey,

> I just switched to gtk-3, and pushed the new release on unstable.
Sadly, I found additional bugs with (a) python2 and (b) with the udisks1
backend. Trying to get that fixed in the next 2-3 days, sorry for the
inconvenience..

>
> udiskie-mount and udiskie-umount still work, and now launching udiskie from 
> console doesn't show any bad error.
> However I don't see the icon come up, not sure if because I don't have any 
> disk attached or because some runtime dependency is missing...
>
> Thomas, can you enlight me?

Did you start udiskie with `--tray`?
Under which environment are you running? I've already noticed that
ubuntu doesn't show the systray anymore. They replaced it with a similar
notification area for which a different API (AppIndicator) must be used.





signature.asc
Description: OpenPGP digital signature

Bug#794856: marked as done (opencv: non DFSG file in the source package)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 19:00:39 +
with message-id 
and subject line Bug#794856: fixed in opencv 3.0.0+dfsg-1~exp1
has caused the Debian Bug report #794856,
regarding opencv: non DFSG file in the source package
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.)


-- 
794856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencv
Version: 2.4.9.1+dfsg-1.1
Severity: Serious
Justification: non DFSG file in the source package
User: locutusofb...@debian.org
Usertags: license-problem-non-free-img-lenna

Hi opencv Maintainer(s),
your package has been found to contain a copy of a non DFSG
file, that makes your package non DFSG.

This image (called lenna.jpg, or lena.jpg with some variants)
is an image of Lena Söderberg, photographed by Dwight Hooker,
cropped from the centerfold of the November 1972 issue of Playboy magazine.

This file is to be considered distributable but non free
(at the end of this bug report you will find a link to the lintian tag,
with a more complete description of the issue and references)

Below a list of the affected files:
- samples/c/lena.jpg
- samples/cpp/lena.jpg
- samples/cpp/tutorial_code/images/lena.png
- doc/tutorials/introduction/clojure_dev_intro/images/lena.png
- doc/tutorials/introduction/desktop_java/images/lena.png
- modules/java/android_test/res/drawable/lena.jpg
- samples/winrt/OcvImageProcessing/OcvImageProcessing/Assets/Lena.png
- samples/java/clojure/simple-sample/resources/images/lena.png

note, I did stop checking for the all files as soon as I found one
good match, so they might be not all bad references, please update
this bug if not correct.

More information about this issue can be found on the
license-problem-non-free-img-lenna lintian tag [1] and Debian bug [2]

[1] https://lintian.debian.org/tags/license-problem-non-free-img-lenna.html
[2] https://bugs.debian.org/771191

thanks,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: opencv
Source-Version: 3.0.0+dfsg-1~exp1

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated opencv 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: Thu, 10 Dec 2015 00:07:44 +0900
Source: opencv
Binary: opencv-doc libopencv-dev opencv-data libopencv-core-dev 
libopencv-core3.0 libopencv-core3.0-dbg libopencv-ml-dev libopencv-ml3.0 
libopencv-ml3.0-dbg libopencv-imgproc-dev libopencv-imgproc3.0 
libopencv-imgproc3.0-dbg libopencv-imgcodecs-dev libopencv-imgcodecs3.0 
libopencv-imgcodecs3.0-dbg libopencv-video-dev libopencv-video3.0 
libopencv-video3.0-dbg libopencv-videoio-dev libopencv-videoio3.0 
libopencv-videoio3.0-dbg libopencv-objdetect-dev libopencv-objdetect3.0 
libopencv-objdetect3.0-dbg libopencv-highgui-dev libopencv-highgui3.0 
libopencv-highgui3.0-dbg libopencv-calib3d-dev libopencv-calib3d3.0 
libopencv-calib3d3.0-dbg libopencv-flann-dev libopencv-flann3.0 
libopencv-flann3.0-dbg libopencv-features2d-dev libopencv-features2d3.0 
libopencv-features2d3.0-dbg libopencv-ts-dev libopencv-hal-dev 
libopencv-photo-dev libopencv-photo3.0 libopencv-photo3.0-dbg 
libopencv-videostab-dev libopencv-videostab3.0 libopencv-videostab3.0-dbg 
libopencv-stitching-dev
 libopencv-stitching3.0 libopencv-stitching3.0-dbg libopencv-shape-dev 
libopencv-shape3.0 libopencv-shape3.0-dbg libopencv-superres-dev 
libopencv-superres3.0 libopencv-superres3.0-dbg libopencv-viz-dev 
libopencv-viz3.0 libopencv-viz3.0-dbg libopencv3.0-java libopencv3.0-jni
 python-opencv
Architecture: source amd64 all
Version: 3.0.0+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Nobuhiro Iwamatsu 
Description:
 libopencv-calib3d-dev - development files for libopencv-calib3d3.0
 libopencv-calib3d3.0 - computer vision Camera 

Bug#808361: marked as done (FTBFS due to too loose build-depends)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 19:00:40 +
with message-id 
and subject line Bug#808361: fixed in python-letsencrypt 0.1.1-3
has caused the Debian Bug report #808361,
regarding FTBFS due to too loose build-depends
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.)


-- 
808361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-letsencrypt
Version: 0.1.1-1
Severity: serious

The latest upload FTBFS [1].

Looking at the build log, python-acme 0.1.0-3 was installed and it looks
like it actually needs python-acme >= 0.1.1:

No local packages or download links found for acme==0.1.1
error: Could not find suitable distribution for
Requirement.parse('acme==0.1.1')



[1] 
https://buildd.debian.org/status/fetch.php?pkg=python-letsencrypt=all=0.1.1-1=1450241465
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-letsencrypt
Source-Version: 0.1.1-3

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated 
python-letsencrypt 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: Tue, 22 Dec 2015 23:06:12 -0500
Source: python-letsencrypt
Binary: python-letsencrypt letsencrypt python-letsencrypt-doc
Architecture: source all
Version: 0.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Harlan Lieberman-Berg 
Description:
 letsencrypt - Let's Encrypt main client
 python-letsencrypt - Let's Encrypt main library
 python-letsencrypt-doc - Let's Encrypt client documentation
Closes: 808361
Changes:
 python-letsencrypt (0.1.1-3) unstable; urgency=medium
 .
   * New version to fix FTBFS.  (Closes: #808361)
Checksums-Sha1:
 608e02a3fa47abf9878cdebb26bb18d61392e911 2672 python-letsencrypt_0.1.1-3.dsc
 8ab99399d0dec1069797c736c31f682972629975 166683 
python-letsencrypt_0.1.1.orig.tar.gz
 2428879882dfeda689bbb8fec3947ff069fb18f7 7632 
python-letsencrypt_0.1.1-3.debian.tar.xz
 4dbd1e597693f95c2540c7be5c5e67bf6c38b684 11488 letsencrypt_0.1.1-3_all.deb
 2f39e6dd797b325381f6e6f3c0a4caa01ab07b1c 161450 
python-letsencrypt-doc_0.1.1-3_all.deb
 528b291adc99f6510b17f585491b8bfd096bc8c3 81906 
python-letsencrypt_0.1.1-3_all.deb
Checksums-Sha256:
 3e921a8453fd829aee24a73568e9a70297638cdca739117079f379154f29c6ef 2672 
python-letsencrypt_0.1.1-3.dsc
 8e6784031eea7212e128e17be51a8fb8e487d9693a5df89c88be5363261f2ace 166683 
python-letsencrypt_0.1.1.orig.tar.gz
 faba63b9399daf56384cf2d750c273666c5e70f5a82fc8e9778c7c8d13a13d1e 7632 
python-letsencrypt_0.1.1-3.debian.tar.xz
 19fef793e1bc8b938bf9f23a30531e577b0778161ce9a26f8a929c1710c7c642 11488 
letsencrypt_0.1.1-3_all.deb
 cb5d5a9d575413c225a146c6fc0bb7bb2dff5a5e89a2d1cbed085a9b3b6d0c73 161450 
python-letsencrypt-doc_0.1.1-3_all.deb
 8cf4ac4585bc8b3259118370ca60cb9f962d55831c567d03e7570a39a3dc2bcb 81906 
python-letsencrypt_0.1.1-3_all.deb
Files:
 7a976e65431a5094971e16f6dcc6f4cd 2672 python optional 
python-letsencrypt_0.1.1-3.dsc
 ddd393563f3d5835d678b7478148e3d9 166683 python optional 
python-letsencrypt_0.1.1.orig.tar.gz
 d0532843255753b91713304859114346 7632 python optional 
python-letsencrypt_0.1.1-3.debian.tar.xz
 2fae1595cf0fc2ff9eb2cec9c91f2dbe 11488 web optional letsencrypt_0.1.1-3_all.deb
 c31055c6d7949721902e64e1ac1aa4b4 161450 doc optional 
python-letsencrypt-doc_0.1.1-3_all.deb
 236bfc970bf75195f89af0ab133070bb 81906 python optional 
python-letsencrypt_0.1.1-3_all.deb

Bug#808851: artemis: FTBFS: error: package ReferenceSequenceFileFactory does not exist

[Chris Lamb]

Source: artemis
Version: 16.0.0+dfsg-4
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,

artemis fails to build from source in unstable/amd64:

  [..]

  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:76:
 error: cannot find symbol
  indexSeqFile = new IndexedFastaSequenceFile(fasta, fastaIndex);
 ^
symbol:   class IndexedFastaSequenceFile
location: class IndexFastaStream
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:82:
 error: package ReferenceSequenceFileFactory does not exist
  ReferenceSequenceFileFactory.FASTA_EXTENSIONS.toString()+
  ^
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:154:
 error: package ReferenceSequenceFileFactory does not exist
  if(ReferenceSequenceFileFactory.FASTA_EXTENSIONS.contains(".dna"))
 ^
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:156:
 error: package ReferenceSequenceFileFactory does not exist
  ReferenceSequenceFileFactory.FASTA_EXTENSIONS.add(".dna");
  ^
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:157:
 error: package ReferenceSequenceFileFactory does not exist
  ReferenceSequenceFileFactory.FASTA_EXTENSIONS.add(".seq");
  ^
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:158:
 error: package ReferenceSequenceFileFactory does not exist
  ReferenceSequenceFileFactory.FASTA_EXTENSIONS.add(".fas");
  ^
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:159:
 error: package ReferenceSequenceFileFactory does not exist
  ReferenceSequenceFileFactory.FASTA_EXTENSIONS.add(".ffn");
  ^
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/IndexFastaStream.java:269:
 error: cannot find symbol
  ReferenceSequence ref;
  ^
symbol:   class ReferenceSequence
location: class IndexFastaStream
  
/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/alignment/CRAMReferenceSequenceFile.java:84:
 error: cannot find symbol
  return new ReferenceSequence(sequence.getName(), 0, 
 ^
symbol:   class ReferenceSequence
location: class CRAMReferenceSequenceFile
  Note: Some input files use or override a deprecated API.
  Note: Recompile with -Xlint:deprecation for details.
  Note: Some input files use unchecked or unsafe operations.
  Note: Recompile with -Xlint:unchecked for details.
  32 errors
  1 warning
  Makefile:247: recipe for target 
'uk/ac/sanger/artemis/MegaBlastComparisonData.class' failed
  make[2]: *** [uk/ac/sanger/artemis/MegaBlastComparisonData.class] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg'
  debian/rules:39: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223192441.GwNPu7NexT/artemis-16.0.0+dfsg'
  debian/rules:36: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


artemis.16.0.0+dfsg-4.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808691: jboss-xnio: FTBFS: duplicate class: org.xnio._private.Messages_$logger

[Markus Koschany]

On Mon, 21 Dec 2015 22:30:06 +0100 Emmanuel Bourg  wrote:
> Le 21/12/2015 21:59, Markus Koschany a écrit :
> 
> > At the moment I don't see a way to fix this in jboss-xnio
> > or undertow though.
> 
> We can workaround this issue by reverting to the compiler plugin 2.5.
> Build depending on libmaven-compiler-plugin-2.5-java and adding the
> following to the pom works for jboss-xnio:
> 
> 
> 
> 
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.5.1
> 
> 
> 
> 

I tried the same workaround for undertow but I haven't had any luck so
far. I added the same snippet to all pom.xml files but the package still
FTBFS. I have pushed the changes to Git master. Any hint is welcome.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#808687: marked as done (tempest: FTBFS: ImportError: No module named OpenSSL)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 16:35:06 +
with message-id 
and subject line Bug#808687: fixed in tempest 6-1
has caused the Debian Bug report #808687,
regarding tempest: FTBFS: ImportError: No module named OpenSSL
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.)


-- 
808687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tempest
Version: 4-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./tempest/test_discover} --list 
--- import errors ---
Failed to import test module: tempest.tests.cli.test_cli
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest/tests/cli/test_cli.py", line 19, in 
from tempest import cli
  File "tempest/cli/__init__.py", line 22, in 
from tempest.common import credentials
  File "tempest/common/credentials.py", line 16, in 
from tempest.common import accounts
  File "tempest/common/accounts.py", line 22, in 
from tempest import clients
  File "tempest/clients.py", line 92, in 
from tempest.services.image.v1.json.image_client import ImageClientJSON
  File "tempest/services/image/v1/json/image_client.py", line 27, in 
from tempest.common import glance_http
  File "tempest/common/glance_http.py", line 26, in 
import OpenSSL
ImportError: No module named OpenSSL

Failed to import test module: tempest.tests.cmd.test_verify_tempest_config
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest/tests/cmd/test_verify_tempest_config.py", line 20, in 
from tempest.cmd import verify_tempest_config
  File "tempest/cmd/verify_tempest_config.py", line 26, in 
from tempest import clients
  File "tempest/clients.py", line 92, in 
from tempest.services.image.v1.json.image_client import ImageClientJSON
  File "tempest/services/image/v1/json/image_client.py", line 27, in 
from tempest.common import glance_http
  File "tempest/common/glance_http.py", line 26, in 
import OpenSSL
ImportError: No module named OpenSSL

Failed to import test module: tempest.tests.common.test_accounts
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest/tests/common/test_accounts.py", line 25, in 
from tempest.common import accounts
  File "tempest/common/accounts.py", line 22, in 
from tempest import clients
  File "tempest/clients.py", line 92, in 
from tempest.services.image.v1.json.image_client import ImageClientJSON
  File "tempest/services/image/v1/json/image_client.py", line 27, in 
from tempest.common import glance_http
  File "tempest/common/glance_http.py", line 26, in 
import OpenSSL
ImportError: No module named OpenSSL

Failed to import test module: tempest.tests.common.test_admin_available
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest/tests/common/test_admin_available.py", line 15, in 
from oslo.config import cfg
ImportError: No module named oslo.config

...

--
Ran 0 tests in 0.494s

OK
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
testr slowest
debian/rules:45: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 3
make[1]: Leaving directory '/tempest-4'

Full build log:

Bug#795848: problem is fixed in the current release

[Brian Warner]

I only recently heard about this.. we fixed that problem in the
(current) foolscap-0.9.1 release, made on 21-Sep-2015. Upgrading to
0.9.1 ought to resolve this FTBFS.

(there is a new problem that involves a bad interaction between
foolscap-0.9.1 and twisted >=15.3.0, but for teh most part it only
affects Tahoe-LAFS. I'm working on a new foolscap release that will
resolve it, but I don't think that's cause to hold up putting
foolscap-0.9.1 into sid).

cheers,
 -Brian

Bug#808843: python-pyramid: FTBFS: ValueError: Invalid status code, integer required.

[Chris Lamb]

Source: python-pyramid
Version: 1.5.7+dfsg-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,

python-pyramid fails to build from source in unstable/amd64:

  [..]

  
  ==
  ERROR: test_ctor_with_app_iter_doesnt_set_default_app_iter 
(pyramid.tests.test_httpexceptions.TestHTTPException)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 140, in test_ctor_with_app_iter_doesnt_set_default_app_iter
  exc = self._makeOne(app_iter=[b'123'])
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 78, in _makeOne
  return cls(*arg, **kw)
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
 line 209, in __init__
  Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in 
__init__
  self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in 
_status__set
  raise ValueError('Invalid status code, integer required.')
  ValueError: Invalid status code, integer required.
  
  ==
  ERROR: test_ctor_with_body_doesnt_set_default_app_iter 
(pyramid.tests.test_httpexceptions.TestHTTPException)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 132, in test_ctor_with_body_doesnt_set_default_app_iter
  exc = self._makeOne(body=b'123')
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 78, in _makeOne
  return cls(*arg, **kw)
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
 line 209, in __init__
  Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in 
__init__
  self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in 
_status__set
  raise ValueError('Invalid status code, integer required.')
  ValueError: Invalid status code, integer required.
  
  ==
  ERROR: test_ctor_with_unicode_body_doesnt_set_default_app_iter 
(pyramid.tests.test_httpexceptions.TestHTTPException)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 136, in test_ctor_with_unicode_body_doesnt_set_default_app_iter
  exc = self._makeOne(unicode_body=text_('123'))
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 78, in _makeOne
  return cls(*arg, **kw)
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
 line 209, in __init__
  Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in 
__init__
  self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in 
_status__set
  raise ValueError('Invalid status code, integer required.')
  ValueError: Invalid status code, integer required.
  
  ==
  ERROR: test_exception (pyramid.tests.test_httpexceptions.TestHTTPException)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 178, in test_exception
  exc = self._makeOne()
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/tests/test_httpexceptions.py",
 line 78, in _makeOne
  return cls(*arg, **kw)
File 
"/home/lamby/temp/cdt.20151223174338.zixwk4Bz6G/python-pyramid-1.5.7+dfsg/pyramid/httpexceptions.py",
 line 209, in __init__
  Response.__init__(self, status=status, **kw)
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 107, in 
__init__
  self.status = status
File "/usr/lib/python2.7/dist-packages/webob/response.py", line 276, in 
_status__set
  raise 

Bug#808844: python-tasklib: FTBFS: Download error on [..] (accesses the internet during build?)

[Chris Lamb]

Source: python-tasklib
Version: 0.11.0-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,

python-tasklib fails to build from source in unstable/amd64:

  [..]
  running test
  Searching for tzlocal
  Reading https://pypi.python.org/simple/tzlocal/
  Download error on https://pypi.python.org/simple/tzlocal/: [SSL: 
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some 
packages may not be found!
  Couldn't find index page for 'tzlocal' (maybe misspelled?)
  Scanning index of all packages (this may take a while)
  Reading https://pypi.python.org/simple/
  Download error on https://pypi.python.org/simple/: [SSL: 
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some 
packages may not be found!
  No local packages or download links found for tzlocal
  error: Could not find suitable distribution for Requirement.parse('tzlocal')
  debian/rules:25: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223174330.xBnbXKACyh/python-tasklib-0.11.0'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-tasklib.0.11.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808688: marked as done (testresources: FTBFS: FAIL: testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 16:35:13 +
with message-id 
and subject line Bug#808688: fixed in testresources 1.0.0-1
has caused the Debian Bug report #808688,
regarding testresources: FTBFS: FAIL: 
testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests
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.)


-- 
808688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: testresources
Version: 0.2.7-4
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

py3versions: no X-Python3-Version in control file, using supported versions
nosetests
...
--
Ran 107 tests in 0.164s

OK
nosetests3
..F
==
FAIL: 
testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/testresources-0.2.7/lib/testresources/tests/test_optimising_test_suite.py", 
line 513, in testBasicSortTests
[self.case3, self.case2, self.case1, self.case4]])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 356, in 
assertIn
self.assertThat(haystack, Contains(needle), message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: [test_three, test_one, test_two, 
test_four] not in [[test_one, test_two, test_three, test_four], [test_three, 
test_two, test_one, test_four]]


--
Ran 107 tests in 0.144s

FAILED (failures=1)
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/testresources-0.2.7'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/testresources.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: testresources
Source-Version: 1.0.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated testresources 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: Wed, 23 Dec 2015 14:59:37 +
Source: testresources
Binary: python-testresources python3-testresources
Architecture: source all
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-testresources - PyUnit extension for managing expensive test fixtures - 
Python 2.
 python3-testresources - PyUnit extension for managing expensive test fixtures 
- Python 3.
Closes: 808688
Changes:
 testresources (1.0.0-1) unstable; urgency=medium
 .
   * New upstream release:
 - Fixes FTBFS in Sid (Closes: #808688)
   * Switched to git tag packaging workflow.
   * Added export OSLO_PACKAGE_VERSION for pbr.
   * watch file now using github tag.
   * ran wrap-and-sort -t -a
   * Standards-Version is now 3.9.6 (no change)
   * Using -v flag when calling nosetests{3,}
   * Do not run undeterministic test:
 - test_optimising_test_suite.TestGraphStuff.testBasicSortTests
   * Removed reference to lib/testresources/tests/TestUtil.py in

Bug#808826: libkavorka-perl: FTBFS: Can't locate object method "_set_declared_name" via package "Kavorka::Sub::Fun"

[Niko Tyni]

Control: block 796345 with -1

On Wed, Dec 23, 2015 at 04:05:27PM +0200, Niko Tyni wrote:
> Package: libkavorka-perl
> Version: 0.036-1
> Severity: serious
> Forwarded: https://rt.cpan.org/Ticket/Display.html?id=109841
> 
> This package fails to build on current sid.

>   Can't locate object method "_set_declared_name" via package 
> "Kavorka::Sub::Fun" at /<>/blib/lib/Kavorka/Sub.pm line 182.
>   t/02named-functions.t .. 
>   Dubious, test returned 255 (wstat 65280, 0xff00)

It's indeed a regression caused by the perl 5.20 -> 5.22 upgrade.
Not sure why our rebuilds didn't catch it.

It works on stretch, then 'apt-get install perl' breaks it. I see
no source versions changed except perl. Log of the upgrade:

  Preparing to unpack .../libparams-classify-perl_0.013-5+b1_amd64.deb ...
  Unpacking libparams-classify-perl (0.013-5+b1) over (0.013-5) ...
  Preparing to unpack .../libsub-name-perl_0.14-1+b1_amd64.deb ...
  Unpacking libsub-name-perl (0.14-1+b1) over (0.14-1) ...
  Preparing to unpack .../libpadwalker-perl_2.2-1+b1_amd64.deb ...
  Unpacking libpadwalker-perl (2.2-1+b1) over (2.2-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  dpkg: perl-modules: dependency problems, but removing anyway as you requested:
   perl depends on perl-modules (>= 5.20.2-6).
  
  (Reading database ... 19995 files and directories currently installed.)
  Removing perl-modules (5.20.2-6) ...
  (Reading database ... 19270 files and directories currently installed.)
  Preparing to unpack /perl_5.22.1-2_amd64.deb ...
  Unpacking perl (5.22.1-2) over (5.20.2-6) ...
  Selecting previously unselected package perl-modules-5.22.
  Preparing to unpack .../perl-modules-5.22_5.22.1-2_all.deb ...
  Unpacking perl-modules-5.22 (5.22.1-2) ...
  Selecting previously unselected package libperl5.22:amd64.
  Preparing to unpack .../libperl5.22_5.22.1-2_amd64.deb ...
  Unpacking libperl5.22:amd64 (5.22.1-2) ...
  Preparing to unpack /perl-base_5.22.1-2_amd64.deb ...
  Unpacking perl-base (5.22.1-2) over (5.20.2-6) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up perl-base (5.22.1-2) ...
  (Reading database ... 20572 files and directories currently installed.)
  Preparing to unpack .../liblocale-gettext-perl_1.07-1+b1_amd64.deb ...
  Unpacking liblocale-gettext-perl (1.07-1+b1) over (1.07-1) ...
  Preparing to unpack .../libscope-upper-perl_0.28-1+b1_amd64.deb ...
  Unpacking libscope-upper-perl (0.28-1+b1) over (0.28-1) ...
  Preparing to unpack .../libmouse-perl_2.4.5-1+b1_amd64.deb ...
  Unpacking libmouse-perl (2.4.5-1+b1) over (2.4.5-1) ...
  Preparing to unpack .../libclass-load-xs-perl_0.09-1+b1_amd64.deb ...
  Unpacking libclass-load-xs-perl (0.09-1+b1) over (0.09-1) ...
  Preparing to unpack .../libscalar-list-utils-perl_1%3a1.42-1+b1_amd64.deb ...
  Unpacking libscalar-list-utils-perl (1:1.42-1+b1) over (1:1.42-1) ...
  Preparing to unpack .../libparams-validate-perl_1.21-1+b1_amd64.deb ...
  Unpacking libparams-validate-perl (1.21-1+b1) over (1.21-1) ...
  Preparing to unpack .../libsub-identify-perl_0.12-1+b1_amd64.deb ...
  Unpacking libsub-identify-perl (0.12-1+b1) over (0.12-1) ...
  Preparing to unpack .../libdevel-callparser-perl_0.002-1+b2_amd64.deb ...
  Unpacking libdevel-callparser-perl (0.002-1+b2) over (0.002-1+b1) ...
  Preparing to unpack .../libmoose-perl_2.1604-1+b1_amd64.deb ...
  Unpacking libmoose-perl (2.1604-1+b1) over (2.1604-1) ...
  Preparing to unpack .../libdata-alias-perl_1.20-1+b1_amd64.deb ...
  Unpacking libdata-alias-perl (1.20-1+b1) over (1.20-1) ...
  Preparing to unpack .../libdevel-callchecker-perl_0.007-1+b1_amd64.deb ...
  Unpacking libdevel-callchecker-perl (0.007-1+b1) over (0.007-1) ...
  Preparing to unpack .../libvariable-magic-perl_0.59-1+b1_amd64.deb ...
  Unpacking libvariable-magic-perl (0.59-1+b1) over (0.59-1) ...
  Preparing to unpack .../libdatetime-perl_2%3a1.21-1+b1_amd64.deb ...
  Unpacking libdatetime-perl (2:1.21-1+b1) over (2:1.21-1) ...
  Preparing to unpack .../libparse-keyword-perl_0.08-2+b1_amd64.deb ...
  Unpacking libparse-keyword-perl (0.08-2+b1) over (0.08-2) ...
  Preparing to unpack .../liblist-moreutils-perl_0.413-1+b1_amd64.deb ...
  Unpacking liblist-moreutils-perl (0.413-1+b1) over (0.413-1) ...
  Preparing to unpack .../libparams-util-perl_1.07-2+b2_amd64.deb ...
  Unpacking libparams-util-perl (1.07-2+b2) over (1.07-2+b1) ...
  Preparing to unpack .../libtext-charwidth-perl_0.04-7+b4_amd64.deb ...
  Unpacking libtext-charwidth-perl (0.04-7+b4) over (0.04-7+b3) ...
  Preparing to unpack .../libtext-iconv-perl_1.7-5+b3_amd64.deb ...
  Unpacking libtext-iconv-perl (1.7-5+b3) over (1.7-5+b2) ...
  Preparing to unpack .../libpackage-stash-xs-perl_0.28-2+b2_amd64.deb ...
  Unpacking libpackage-stash-xs-perl (0.28-2+b2) over (0.28-2+b1) ...
  Preparing to unpack .../libb-hooks-op-check-perl_0.19-2+b2_amd64.deb ...
  Unpacking libb-hooks-op-check-perl (0.19-2+b2) over (0.19-2+b1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting 

Processed: Re: Bug#808826: libkavorka-perl: FTBFS: Can't locate object method "_set_declared_name" via package "Kavorka::Sub::Fun"

[Debian Bug Tracking System]

Processing control commands:

> block 796345 with -1
Bug #796345 [release.debian.org] transition: perl 5.22
796345 was blocked by: 787493 808583 807324 808329 795127 787468 807401 807474 
808629 788073 807423 796923 790532 807400 807422 804603 804590 807478 808560 
807492 787450 787453 808444 808825 807038 802939 805391 807493 799118 808325
796345 was blocking: 798309 801659 801660 801661 801662 801663
Added blocking bug(s) of 796345: 808826

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

Bug#808763: Running pytest

[Tristan Seligmann]

If you want to run pytest with a particular version of python, then
"pythonX.Y -m pytest" is a much better way than relying on the py.test-X.Y
scripts.

Bug#808850: xfonts-wqy: FTBFS: Type of arg 1 to shift must be array (not constant item) at ./bdfmerge.pl line 35, near "ARGV)"

[Chris Lamb]

Source: xfonts-wqy
Version: 1.0.0~rc1-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,

xfonts-wqy fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package xfonts-wqy
  dpkg-buildpackage: source version 1.0.0~rc1-1
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by ChangZhuo Chen (陳昌倬) 

   dpkg-source --before-build xfonts-wqy-1.0.0~rc1
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean
 dh_testdir
 dh_auto_clean
make -j1 clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151223192453.PThnk7KaAc/xfonts-wqy-1.0.0~rc1'
  rm -f wenquanyi_9pt.pcf wenquanyi_10pt.pcf wenquanyi_11pt.pcf 
wenquanyi_12pt.pcf wenquanyi_13px.pcf wenquanyi_9pt_cjk.bdf 
wenquanyi_10pt_cjk.bdf wenquanyi_11pt_cjk.bdf wenquanyi_12pt_cjk.bdf 
wenquanyi_13px_cjk.bdf
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223192453.PThnk7KaAc/xfonts-wqy-1.0.0~rc1'
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_auto_configure
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151223192453.PThnk7KaAc/xfonts-wqy-1.0.0~rc1'
  ./bdfmerge.pl   0x0--0xwenquanyi_9pt.bdf > wenquanyi_9pt_cjk.bdf
  shift on reference is experimental at ./bdfmerge.pl line 35.
  Type of arg 1 to shift must be array (not constant item) at ./bdfmerge.pl 
line 35, near "ARGV)"
  Execution of ./bdfmerge.pl aborted due to compilation errors.
  Makefile:42: recipe for target 'wenquanyi_9pt.pcf' failed
  make[1]: *** [wenquanyi_9pt.pcf] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223192453.PThnk7KaAc/xfonts-wqy-1.0.0~rc1'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:3: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


xfonts-wqy.1.0.0~rc1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808849: fso-frameworkd: FTBFS: cp: cannot stat 'debian/tmp/usr/bin': No such file or directory

[Chris Lamb]

Source: fso-frameworkd
Version: 0.10.1-2
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,

fso-frameworkd fails to build from source in unstable/amd64:

  [..]

  changing mode of 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/usr/bin/frameworkd
 to 755
  changing mode of 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/usr/bin/dump-netlink
 to 755
  changing mode of 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/usr/bin/opimd_fix_db
 to 755
  running install_data
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/dbus-1
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/dbus-1/system.d
  copying etc/dbus-1/system.d/frameworkd.conf -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/dbus-1/system.d
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/init.d
  copying etc/init.d/frameworkd -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/init.d
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema
  copying etc/freesmartphone/opreferences/schema/phone.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema/
  copying etc/freesmartphone/opreferences/schema/profiles.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema/
  copying etc/freesmartphone/opreferences/schema/rules.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/schema/
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/profiles
  copying etc/freesmartphone/opreferences/conf/profiles/default.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/profiles/
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/default.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/silent.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/vibrate.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  copying etc/freesmartphone/opreferences/conf/phone/ring.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/phone
  creating 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/rules
  copying etc/freesmartphone/opreferences/conf/rules/default.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/rules
  copying etc/freesmartphone/opreferences/conf/rules/silent.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/rules
  copying etc/freesmartphone/opreferences/conf/rules/vibrate.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/rules
  copying etc/freesmartphone/opreferences/conf/rules/ring.yaml -> 
/home/lamby/temp/cdt.20151223192505.alhSxf6VCt/fso-frameworkd-0.10.1/debian/fso-frameworkd/etc/freesmartphone/opreferences/conf/rules
  creating 

Bug#808852: elasticsearch: FTBFS: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.google.guava:guava:jar:18.0

[Chris Lamb]

Source: elasticsearch
Version: 1.7.3+dfsg-2
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,

elasticsearch fails to build from source in unstable/amd64:

  [..]

  -Dfile=/usr/share/java/jts.jar \
  -DgroupId=com.vividsolutions \
  -DartifactId=jts \
  -Dversion=fake \
  -Dpackaging=jar
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building elasticsearch 1.7.3
  [INFO] 

  [INFO] 
  [INFO] --- maven-install-plugin:2.5.2:install-file (default-cli) @ 
elasticsearch ---
  [INFO] Installing /usr/share/java/jts.jar to 
/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian/maven-repo/com/vividsolutions/jts/fake/jts-fake.jar
  [INFO] Installing /tmp/mvninstall1889937690685813395.pom to 
/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian/maven-repo/com/vividsolutions/jts/fake/jts-fake.pom
  [INFO] 

  [INFO] BUILD SUCCESS
  [INFO] 

  [INFO] Total time: 0.801 s
  [INFO] Finished at: 2015-12-23T19:27:13+00:00
  [INFO] Final Memory: 8M/236M
  [INFO] 

  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg'
 dh_auto_build -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building elasticsearch 1.7.3
  [INFO] 

  [WARNING] The POM for com.google.guava:guava:jar:18.0 is missing, no 
dependency information available
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.792 s
  [INFO] Finished at: 2015-12-23T19:27:16+00:00
  [INFO] Final Memory: 7M/236M
  [INFO] 

  [ERROR] Failed to execute goal on project elasticsearch: Could not resolve 
dependencies for project org.elasticsearch:elasticsearch:jar:1.7.3: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.google.guava:guava:jar:18.0 has not been downloaded from it 
before. -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
  dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
  debian/rules:22: recipe for target 'build' 

Bug#808673: marked as done (networking-arista: FTBFS: ImportError: No module named config)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 16:31:59 +
with message-id 
and subject line Bug#808673: fixed in networking-arista 2015.2.0-1
has caused the Debian Bug report #808673,
regarding networking-arista: FTBFS: ImportError: No module named config
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.)


-- 
808673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-arista
Version: 2015.1.3-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

${PYTHON:-python} -m subunit.run discover -t ./ .  
networking_arista.tests.test_networking_arista.TestNetworking_arista.test_something
networking_arista.tests.test_networking_arista.TestNetworking_arista.test_something
 ... ok
unittest2.loader._FailedTest.networking_arista.tests.unit
unittest2.loader._FailedTest.networking_arista.tests.unit ... FAIL

==
FAIL: unittest2.loader._FailedTest.networking_arista.tests.unit
unittest2.loader._FailedTest.networking_arista.tests.unit
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: networking_arista.tests.unit
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 490, in 
_find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_arista/tests/unit/__init__.py", line 16, in 
from oslo.config import cfg
ImportError: No module named config


--
Ran 2 tests in 0.448s

FAILED (failures=1)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/networking-arista-2015.1.3'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/networking-arista.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: networking-arista
Source-Version: 2015.2.0-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated networking-arista 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: Wed, 23 Dec 2015 15:17:30 +0100
Source: networking-arista
Binary: python-networking-arista
Architecture: source all
Version: 2015.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-networking-arista - OpenStack virtual network service - Arista plugin
Closes: 808673
Changes:
 networking-arista (2015.2.0-1) unstable; urgency=medium
 .
   * New upstream release:
 - Updates dependency, and therefore fixes FTBFS (Closes: #808673).
   * Fixed (build-)depends for this release.
Checksums-Sha1:
 e9d59aa7687761bd126cf4ab262b392b25fe7627 2415 networking-arista_2015.2.0-1.dsc
 6625e7a625c92209ed45cd40c76da93d284535f3 36032 
networking-arista_2015.2.0.orig.tar.xz
 87750e393b72a8e9da0dadefd56e9f6ef37caf9e 2624 
networking-arista_2015.2.0-1.debian.tar.xz
 5d0fd2fb997f0f2f6ac8c2885a87c11650cf1e6e 31086 
python-networking-arista_2015.2.0-1_all.deb
Checksums-Sha256:
 eb5a63ab6e00fa8f7e7382575771020f954c430b52e3bd90f54f753532d48fde 2415 

Bug#808825: marked as done (libperl-apireference-perl: FTBFS: missing support for Perl 5.22.1)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 16:31:52 +
with message-id 
and subject line Bug#808825: fixed in libperl-apireference-perl 0.21-3
has caused the Debian Bug report #808825,
regarding libperl-apireference-perl: FTBFS: missing support for Perl 5.22.1
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.)


-- 
808825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libperl-apireference-perl
Version: 0.21-2
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition
Control: block 796345 with -1

This package fails to build with Perl 5.22.1, currently in unstable.

  [...]
  Processing: 5.22.0
  echo Current Perl is `perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
  Current Perl is 5_022_001.pm
  test -f lib/Perl/APIReference/V`perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
  debian/rules:8: recipe for target 'regenerated-stamp' failed
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libperl-apireference-perl
Source-Version: 0.21-3

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libperl-apireference-perl 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: Wed, 23 Dec 2015 15:59:33 +0100
Source: libperl-apireference-perl
Binary: libperl-apireference-perl
Architecture: source
Version: 0.21-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 808825
Description: 
 libperl-apireference-perl - Perl module to programmatically query the perlapi
Changes:
 libperl-apireference-perl (0.21-3) unstable; urgency=medium
 .
   * Add support for 5.22.1. (Closes: #808825)
Checksums-Sha1: 
 698b35b78e091bc2111f15dd0e54eb2e41e2890d 2544 
libperl-apireference-perl_0.21-3.dsc
 948f449ce38126f0b137eb62dead36fb3529ebc7 84044 
libperl-apireference-perl_0.21-3.debian.tar.xz
Checksums-Sha256: 
 91375a9d0e7692186b15109eb0d403679a21b96f84d6d208b9d0f7dfbaecb524 2544 
libperl-apireference-perl_0.21-3.dsc
 1acceded2f4277992f7223cce67325c43aa6846dbc39bfc7faf57c26faa86c36 84044 
libperl-apireference-perl_0.21-3.debian.tar.xz
Files: 
 33126f0c62647d4c16f14ef031fce84b 2544 perl optional 
libperl-apireference-perl_0.21-3.dsc
 ccd17d1703fce0a8b1e4b660cf29aff6 84044 perl optional 
libperl-apireference-perl_0.21-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWercLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG5soP/jKlyJyBrg1Oj1Tzr1+l3FaD
+3NatzZPDJcPIY2wGUg+bLFI5eWt7cJHlKGA4rVkswBeusRMAfMji8bKYsNh+niW
Tg8xQGH24ayki/PDetRg5jHTssh/65fucltqn65WyGGN0CBrygWZHW1b5r1fVfGw
flarBYX/A0G2sR9XpU2fWST9osein6jd+wuPOyRVWnaljLQW7tk/gmjYnM4wD6zN
hqJWwxMijgtIZAhw7152LiO2DlRenO52X2hVlb6hwnnAdygJOClj69GoMHcFQMTq
275HotJwDzNHnkjllUYhqi1Uw+4cGIBrDOC8czt84WqLFYIvqXYfgzd0ODXJfA4r
CUN/TwPwNjLZ5MBXUhH3vPRpcg69T6ltu1dZrqJJ/MmApsyupKhoMvGFF4fL6GqJ
Qw8y6SmooAsJUwIhBlT628xbnosTcvKp1w4mRm97q22AWkL3etiQ09/JDZytq3cW
86Eny5ibKPSAH80y3FzIjS2pLi14BfayqYNexfegRl988GNi3vZ0yt1Klj3L7vi7
JJf6PXDFuM6v0dHxarmfqx6p6J9A++RpOqchMbaZVdLeQfRq5FOiXYOFdeps0bs/
7VlNeFrQjaPYFG2dgQlI82bx8u9cIBgncmHAbwwt7xLdlfRmpaudUBagqJg/6UUt
5hRypeHv0IsNhUPTyWnA
=59FZ
-END PGP SIGNATURE End Message ---

Processed: severity of 806139 is grave

[Debian Bug Tracking System]

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

> severity 806139 grave
Bug #806139 [mona] testsuite times out
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#806139: testsuite times out

[Ralf Treinen]

In fact, mona is completely unusable ATM, no way to get any response
from it. Raising severity level to grave. -Ralf.

Bug#808866: (snappy:15699): Clutter-CRITICAL **: The Clutter backend is not a X11 backend

[Julian Andres Klode]

Package: snappy
Severity: grave

Trying to run snappy just fails:

(snappy:15699): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT 
(object)' failed
No media set. You can drag and drop a file into snappy to play it.
Loading ui!

(snappy:15699): Clutter-CRITICAL **: The Clutter backend is not a X11 backend
**
Clutter:ERROR:x11/clutter-stage-x11.c:1290:clutter_x11_get_stage_window: 
assertion failed: (CLUTTER_IS_STAGE_X11 (impl))
Aborted


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

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

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#808874: debian-installer: FTBFS on i386: 586 vs. 686

[Ben Hutchings]

On Thu, 2015-12-24 at 00:23 +0100, Cyril Brulebois wrote:
> Source: debian-installer
> Severity: serious
> Justification: FTBFS
> 
> Hi,
> 
> linux received this change a while ago, and it has now reached
> unstable and testing:
> > linux (4.3~rc3-1~exp1) experimental; urgency=medium
> > 
> > […]
> >   * [i386] Replace 586 flavour with 686
> > - Enable support for OLPC and other Geode-based systems in the 686 
> > flavour
> > - udeb: Update kernel-versions
> > 
> >  -- Ben Hutchings   Sun, 27 Sep 2015 21:02:54 +0100
> 
> so d-i no longer builds on i386. A few packages have to be tweaked for
> this kind of changes; I'm x-d-cc-ing the kernel team as Ben did most of
> the work past time.

I already updated base-installer for this, and I think the only other
change needed was in build/config/i386.cfg.  I've pushed a change to
that.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.

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

Bug#808875: debian-installer: Perl transition

[Cyril Brulebois]

gregor herrmann  (2015-12-24):
> On Thu, 24 Dec 2015 00:28:40 +0100, Cyril Brulebois wrote:
> 
> > [ Please keep debian-perl@ and debian-release@ in the loop. ]
> 
> > Just wanted to let you know that debian-installer still can't be built
> > since a few packages are missing. In my devel chroot, after a
> > dist-upgrade, I had to rebuild the following packages to make
> > debiandoc-sgml installable:
> >   debiandoc-sgml
> >   libhtml-parser-perl
> >   libhtml-tagset-perl
> >   libroman-perl
> >   libtext-format-perl
> > 
> > I've seen at least one of them getting a binNMU so I thought I'd cc
> > perl and release teams…
> 
> That's surprising, since libhtml-parser-perl is the only arch:any
> package, and it has already been NMUed some days ago. The others
> shouldn't be affected by the transition.

Seems to be a mirror needing a good kick, sorry about that…

The 5.20 → 5.22 thing still stands for -boot@ though.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#808246: Maybe the bugs are related

[Lennart Sorensen]

On Thu, Dec 24, 2015 at 12:33:31AM +0100, Gianluca Renzi wrote:
> In this case I suppose even the userspace code (dynamic linking library)
> could not to be used
> with this linker bug and not only the kernel module loader tool. The
> undefined symbols are discarded in every way. The only way to ensure a
> correct code buildup is to use a -static linking of any external library in
> every piece of code. So no dynamic linking is usable in that way. This bug
> seems so unreal to me...
> Are the gcc team people so silly not to try any created code (even a simple
> checking for an external library) in every supported platform for binutils
> and gcc???
> I suppose not. Are you sure of the bug?
> Can you ask the gnu gcc people to test the ld in a kvm with ppc64 machine?

This is a binutils change, NOT a gcc change.

The only package I changed on the system to get the different result
was binutils.

-- 
Len Sorensen

Bug#808875: debian-installer: Perl transition

[Cyril Brulebois]

Control: severity -1 important
Control: tag -1 patch pending

[ -release dropped ]

gregor herrmann  (2015-12-24):
> On Thu, 24 Dec 2015 00:28:40 +0100, Cyril Brulebois wrote:
> 
> > In addition, one can see that kind of warnings during the build now:
> > | Unescaped left brace in regex is deprecated, passed through in regex;
> > | marked by <-- HERE in m/\${ <-- HERE BOOTPROMPT}\n?$/ at
> > | util/bootvars-subst line 13.
> > 
> > so one has to make sure how much d-i is affected by this transition.
> 
> Here's a patch for these warnings [0].

Thanks! Pushed:
  
https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?id=ed4e1180d72d1d9765b9aeb17605a06f68371b6e

I didn't see any more warnings after a full build here (even if that was
only checked with a few greps).

> [0] which are harmless, unless something tests for "no warnings
> output", but also easy to fix. perldoc perldiag says: […]

Yeah, I think we discussed how much I like having advance warnings; but
it's always a good idea to deal with them before it's too late. :)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#808875: debian-installer: Perl transition

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #808875 [src:debian-installer] debian-installer: Perl transition
Severity set to 'important' from 'serious'
> tag -1 patch pending
Bug #808875 [src:debian-installer] debian-installer: Perl transition
Added tag(s) patch and pending.

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

Bug#808874: debian-installer: FTBFS on i386: 586 vs. 686

[Cyril Brulebois]

Ben Hutchings  (2015-12-24):
> I already updated base-installer for this, and I think the only other
> change needed was in build/config/i386.cfg.  I've pushed a change to
> that.

Checking my notes, it appears the following bits were involved last time:
base-installer, debian-installer, debian-cd, installation guide.

The first two seem covered now, thanks.

Adding debian-cd@ for the third (sorry, didn't do any research for this
one).

The last one seems to have been dealt with in r69410, r69411, r69412
last time; something similar might do the trick this time.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#808886: python-rjsmin: FTBFS: .../openstack-pkg-tools/pkgos.make absent

[Aaron M. Ucko]

Source: python-rjsmin
Version: 1.0.12+dfsg1-1
Severity: serious
Justification: fails to build from source

Builds of python-rjsmin in minimal environments (such as on the
autobuilders) have been failing:

  debian/rules:7: /usr/share/openstack-pkg-tools/pkgos.make: No such file or 
directory

Please declare a build dependency on openstack-pkg-tools and confirm
with pbuilder or the like that you haven't missed anything else.

Thanks!

Bug#798437: still not fixed

[Prasad Annadata]

I downloaded version 1.0.2 from the website (thinking that ubuntu repos may
not have the latest bug fix), I still get the same problem.

prasad@laptop:~/Downloads/simple-image-reducer-1.0.2$
./simple-image-reducer.py
Traceback (most recent call last):
  File "./simple-image-reducer.py", line 29, in 
import EXIF
ImportError: No module named EXIF

Bug#808875: debian-installer: Perl transition

[gregor herrmann]

On Thu, 24 Dec 2015 00:28:40 +0100, Cyril Brulebois wrote:

> In addition, one can see that kind of warnings during the build now:
> | Unescaped left brace in regex is deprecated, passed through in regex;
> | marked by <-- HERE in m/\${ <-- HERE BOOTPROMPT}\n?$/ at
> | util/bootvars-subst line 13.
> 
> so one has to make sure how much d-i is affected by this transition.

Here's a patch for these warnings [0].


Cheers,
gregor


[0] which are harmless, unless something tests for "no warnings
output", but also easy to fix. perldoc perldiag says:

Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/%s/
(D deprecated, regexp) You used a literal "{" character in a regular
expression pattern. You should change to use "\{" instead, because a
future version of Perl (tentatively v5.26) will consider this to be a
syntax error. If the pattern delimiters are also braces, any matching
right brace ("}") should also be escaped to avoid confusing the
parser, for example,

qr{abc\{def\}ghi}


-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Joint Venture: Der Jesus von Oberpleis
diff --git a/build/util/bootvars-subst b/build/util/bootvars-subst
index e3e1fed..16a1227 100755
--- a/build/util/bootvars-subst
+++ b/build/util/bootvars-subst
@@ -10,8 +10,8 @@ while (@ARGV) {
 }
 
 while (<>) {
-	s/\${BOOTPROMPT}\n?$//g; # special case
-	s/\${([a-zA-Z0-9_]+)}/$subst{$1}/g;
+	s/\$\{BOOTPROMPT\}\n?$//g; # special case
+	s/\$\{([a-zA-Z0-9_]+)\}/$subst{$1}/g;
 	
 	print;
 }
diff --git a/build/util/pkg-list b/build/util/pkg-list
index b2faec8..29c56c9 100755
--- a/build/util/pkg-list
+++ b/build/util/pkg-list
@@ -234,10 +234,10 @@ sub getlists {
 next unless length;
 
 # normal kernel version substitution
-if (/\${kernel:Version}/) {
+if (/\$\{kernel:Version\}/) {
 	foreach my $v (@kernel_versions) {
 		my $l=$_;
-		$l=~s/\${kernel:Version}/$v-$kernel_flavour/g;
+		$l=~s/\$\{kernel:Version\}/$v-$kernel_flavour/g;
 		collectpackage($l, \%collect, \%exclude, \@postponed);
 	}
 	next; # move on to the next line


signature.asc
Description: Digital Signature

Bug#808875: debian-installer: Perl transition

[gregor herrmann]

On Thu, 24 Dec 2015 00:28:40 +0100, Cyril Brulebois wrote:

> [ Please keep debian-perl@ and debian-release@ in the loop. ]

> Just wanted to let you know that debian-installer still can't be built
> since a few packages are missing. In my devel chroot, after a
> dist-upgrade, I had to rebuild the following packages to make
> debiandoc-sgml installable:
>   debiandoc-sgml
>   libhtml-parser-perl
>   libhtml-tagset-perl
>   libroman-perl
>   libtext-format-perl
> 
> I've seen at least one of them getting a binNMU so I thought I'd cc
> perl and release teams…

That's surprising, since libhtml-parser-perl is the only arch:any
package, and it has already been NMUed some days ago. The others
shouldn't be affected by the transition.

libhtml-parser-perl | 3.71-2| testing | source, amd64, arm64, 
armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
libhtml-parser-perl | 3.71-2| unstable| source
libhtml-parser-perl | 3.71-2+b1 | unstable| amd64, arm64, armel, 
armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x

Package: debiandoc-sgml
Architecture: all
Depends: libhtml-parser-perl, libroman-perl, libtext-format-perl, sgml-data, 
sgmlspl, sp, sgml-base (>= 1.26+nmu2), perl

Package: libhtml-parser-perl
Architecture: amd64
Depends: perl (>= 5.22.1-1), perlapi-5.22.1, libc6 (>= 2.4), 
libhtml-tagset-perl, liburi-perl

Package: libhtml-tagset-perl
Architecture: all
Depends: perl (>= 5.6.0-16)

Package: libroman-perl
Architecture: all
Depends: perl

Package: libtext-format-perl
Architecture: all
Depends: perl


Cheers,
gregor, probably missing something in his d-i noobiness

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Page: When I Was A Child


signature.asc
Description: Digital Signature

Bug#808878: libwebsockets3: uninstallable: depends on conflicting libwebsockets6

[Jakub Wilk]

Package: libwebsockets3
Version: 1.6.0-2
Severity: grave

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

The following packages have unmet dependencies:
libwebsockets3 : Depends: libwebsockets6 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libwebsockets3 depends on:
ii  libc6  2.21-4
ii  libssl1.0.01.0.2d-1
ii  multiarch-support  2.21-4
ii  zlib1g 1:1.2.8.dfsg-2+b1

--
Jakub Wilk

Bug#800216: marked as done (gniall: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Thu, 24 Dec 2015 01:19:06 +
with message-id 
and subject line Bug#800216: fixed in gniall 0.7.1-7.1
has caused the Debian Bug report #800216,
regarding gniall: Please migrate a supported debhelper compat level
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.)


-- 
800216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gniall
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package gniall is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: gniall
Source-Version: 0.7.1-7.1

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

Debian distribution maintenance software
pp.
Raphael Mota Ramos  (supplier of updated gniall 
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: SHA1

Format: 1.8
Date: Sat, 12 Dec 2015 10:25:50 -0200
Source: gniall
Binary: gniall
Architecture: source
Version: 0.7.1-7.1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar (Debian packages) 
Changed-By: Raphael Mota Ramos 
Description:
 gniall - program that tries to learn a human language
Closes: 800216
Changes:
 gniall (0.7.1-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 9 to avoid a FTBFS. (Closes: #800216)
   * debian/control:
  - Added the ${misc:Depends} variable to provide the
right install dependencies.
  - Bumped Standards-Version to 3.9.6.
   * debian/watch: added.
Checksums-Sha1:
 9508151c0f75d8a770c42572534238403863a0a0 1680 gniall_0.7.1-7.1.dsc
 13ca196b1c291d7b6a4eb77266961c655707f0ae 27107 gniall_0.7.1-7.1.diff.gz
Checksums-Sha256:
 7945d0ddac2385da8d551aa0554e3c60295499a2ad59e0fe1d5c9fb8f5cb7a41 1680 
gniall_0.7.1-7.1.dsc
 155b1887333cf7bb8c62fca375164cfdeeae6f2c5f78e7655a5b39c3a6dfab00 27107 
gniall_0.7.1-7.1.diff.gz
Files:
 6288663c8b92f029433d6b666bf1713e 1680 gnome optional gniall_0.7.1-7.1.dsc
 6392f7a713c98dce8270f8f79ba79d4f 27107 gnome optional gniall_0.7.1-7.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWbfpCAAoJEN5juccE6+nv9I0QAJR/gjCyTxUEKrPWUU4jpIHL
lkVHmmp7QxcUDA6uxdsGUp+JvZMN1xP1a85mjBcU/E8j4b4NTHMJfNDqWTm1dV37
Tpr4cA6VhXfFTyvmlSWQ1vlGUKeysGDzMd7dnMsZlc3gjdo1Cq+3oo5P2lqmUAOD
ZatDRRNezaqMmxqk+8+pL4NhjNv+Hcl64vC9R9Yi2ZUnGH2hZQ1ZspcKUMke6sYt
c6euCDCmDWLZB1/x35MsJxTfQtrBb7uzh0xp1Ic65s8LOGWreuuivBDsy/X8rKY/
TbQ5J83LSmZTpVkbO7WDOWGcmPFTSDWJK/VrlW4YuPi5/NR/onod4wCFkTR1q2w6
6mdYYmnAt6PkuAic4u2qlEhn6w86kzqb3ekxtI9Gy8nVJzhK6jQCQr70+rK4pRzW
oDiiCLBj0NIuBW82BeLRVXrWkyzEt466q8A6Qq62wwf+8whxf3f30D9OSbiw33hP
u5yEue+wDna9pAM+rvM23bZW8/083gHDEZfcfDNUdjH/JhyT3sNmddcPlk0WmENy

Bug#808862: redis: leaves redis-server processes running after build

[Chris Lamb]

> FWIW I had to pkill -9 redis on a couple of buildds, just pkill
> apparently wasn't enough.

Way ahead of you :)

https://github.com/lamby/pkg-redis/commit/b1db71c355b297ff3a438bd769a3ee156b2b2772#diff-d2b2229a977ef7e99780f2207c29b503R31


Regards,

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

Bug#807323: [Pkg-utopia-maintainers] Bug#807323: Bug#807323: gparted needs policykit-1 but its neither in depends or recommends

[Phillip Susi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/22/2015 09:19 PM, Michael Biebl wrote:
>> Why?  The BTS forwards the message automatically doesn't it?
>> 
> No it doesn't.

Sigh... that's another absurd failling in debian bts that requires
constant workarounds... added to my list.

> And I would appreciate if you would stop reopening bug reports for 
> packages you don't maintain.

The entire community would appreciate it if you would stop closing
valid, or likely valid bug reports without a good explanation.

The only thing you have suggested thus far ( after closing the bug
several times ) that is even a possible candidate for a legitimate
reason to do so is the use of policykit-1 from experimental with an
otherwise sid based system.  Until this has been confirmed, or unless
it is a known error that you can be reasonably confident is the case,
and you clearly describe that is what the user has done wrong, it is
inappropriate to dismissively close the bug report out of hand.

That said, I have managed to test your hypothesis and confirmed that
indeed, this does result from doing what you suggest, and that is why
I will no longer reopen this bug report.  It is now up to Shirish to
deny that he did install policykit-1 from experimental on an otherwise
unstable/testing system and if not, reopen the bug.  Coming to this
conclusion should not have taken several rounds of closing and
reopening the bug, but rather is something you should have clearly
spelled out when closing the bug in the first place so that Shrish
could have simply said "oh yea, my bad" and let the matter rest,
rather than contacting me privately wondering why his report had been
summarily dismissed.  Please bear this in mind when closing bug
reports in the future so that such confusion can be avoided.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWe28EAAoJEBB5UWFcu6UWeqoH+wYdRutwix8qyiGEpLf25iSF
CllrkhLQ6q2LoUoomIQ4b04CQmHKC/g2D8qnRPnDnh4dzLZYcDdyqTSTTisxMJxW
UfEY0reTO22GhbqQwGABgzpSL6LJ8p17kNldJIs9j0As4CVajs155LxCAnOW/ddw
B2DzPGJ0INThIVAGESxlqJzc+5r1XyGdZT0CM++DDGG1rVGlxWs4O2RDNb38NQyQ
aniSJ/PTSvUUXJu8ejHUo+hwm42PeqjvVIVzsGaXGrIovU+t590g3+49IAf+788f
WKf0wG6IkbBrtxGI4fOMLZwitX1NqmgPRCPHVaHLIS3ESQzGxraUgXivQD+3UTc=
=CGXU
-END PGP SIGNATURE-

Bug#808862: redis: leaves redis-server processes running after build

[Julien Cristau]

Source: redis
Version: 3.2~rc1-2
Severity: serious

Hi,

the redis build seems to leave redis-server processes running,
presumably from tests.  Seen on hasse.debian.org:

$ ps `pgrep -u buildd`
  PID TTY  STAT   TIME COMMAND
  873 ?Ss 0:37 /usr/bin/perl /usr/bin/buildd
 4973 ?S  0:01 /usr/bin/perl /usr/bin/sbuild --apt-update 
--no-apt-upgrade --no-apt-distupgrade --batch --stats-dir=/home/buildd/stats 
--dist=experimental --sbuild-mode=buildd --mailfrom=buildd on hasse 

Bug#808875: debian-installer: Perl transition

[Cyril Brulebois]

Source: debian-installer
Severity: serious
Justification: BD-Uninstallable etc.

[ Please keep debian-perl@ and debian-release@ in the loop. ]

Hi,

Just wanted to let you know that debian-installer still can't be built
since a few packages are missing. In my devel chroot, after a
dist-upgrade, I had to rebuild the following packages to make
debiandoc-sgml installable:
  debiandoc-sgml
  libhtml-parser-perl
  libhtml-tagset-perl
  libroman-perl
  libtext-format-perl

I've seen at least one of them getting a binNMU so I thought I'd cc
perl and release teams…

In addition, one can see that kind of warnings during the build now:
| Unescaped left brace in regex is deprecated, passed through in regex;
| marked by <-- HERE in m/\${ <-- HERE BOOTPROMPT}\n?$/ at
| util/bootvars-subst line 13.

so one has to make sure how much d-i is affected by this transition.


Mraw,
KiBi.

Bug#806560: python3-udiskie/python-udiskie do not start

[Greg Bognar]

I think we are now talking about different bugs.  I have now solved the bug
that I reported originally -- the tray icon showing up, but no menu.  It can
be fixed by installing the gir1.2-gtk-3.0 package.  (This is on Debian
testing, python3-udiskie.  I have not tested with python-udiskie.)

I suggest making gir1.2-gtk-3.0 a dependency of python3-udiskie.

Cheers,
Greg

Bug#808656: marked as done (ganeti: FTBFS: missing: lens >=3.10 && <4.8, old-time >=1.1.0.0)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 23:35:50 +
with message-id 
and subject line Bug#808656: fixed in ganeti 2.15.1-2
has caused the Debian Bug report #808656,
regarding ganeti: FTBFS: missing: lens >=3.10 && <4.8, old-time >=1.1.0.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.)


-- 
808656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganeti
Version: 2.15.1-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

touch empty-cabal-config
/usr/bin/cabal --config-file=empty-cabal-config configure --user \
  -f`test no == yes && echo "htest" || echo "-htest"` \
  -f`test True == True && echo "mond" || echo "-mond"` \
  -f`test True == True && echo "metad" || echo "-metad"`
Warning: No remote package servers have been specified. Usually you would have
one specified in the config file.
Resolving dependencies...
Configuring ganeti-2.15...
cabal: At least the following dependencies are missing:
lens >=3.10 && <4.8, old-time >=1.1.0.0
Makefile:4381: recipe for target 'cabal_macros.h' failed
make[2]: *** [cabal_macros.h] Error 1
make[2]: Leaving directory '/ganeti-2.15.1'
dh_auto_build: make -j1 returned exit code 2
debian/rules:76: recipe for target 'override_dh_auto_build' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ganeti.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 2.15.1-2

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Mon, 21 Dec 2015 22:16:35 +0200
Source: ganeti
Binary: ganeti2 ganeti ganeti-2.15 ganeti-haskell-2.15 ganeti-htools 
ganeti-htools-2.15 ganeti-doc python-ganeti-rapi
Architecture: source all amd64
Version: 2.15.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Description:
 ganeti - cluster virtualization manager
 ganeti-2.15 - cluster virtualization manager - Python components
 ganeti-doc - cluster virtualization manager - documentation
 ganeti-haskell-2.15 - cluster virtualization manager - Haskell components
 ganeti-htools - cluster virtualization manager - tools (stand-alone)
 ganeti-htools-2.15 - cluster virtualization manager - tools for Ganeti 2.15
 ganeti2- transitional dummy package
 python-ganeti-rapi - cluster virtualization manager - RAPI client library
Closes: 808656
Changes:
 ganeti (2.15.1-2) unstable; urgency=medium
 .
   * vcluster-qa: use an RSA SSH key
 OpenSSH 7.x has deprecated DSA host/user keys. Use an RSA key for the QA
 suite.
   * Remove lens version restriction from cabal template and add missing B-D on
 libghc-old-time-dev (closes: #808656)
   * Fix compilation with GHC 7.10/base 4.8:
 + Backport the following upstream commits:
   o 3aaf10b Define MonadPlus instance definitions using Alternative
   o 503470f Hide isSubsequenceOf when importing from Data.List
   o 1757234 Add signatures for some ambiguous types
   o 1f6838f Append a string when using newName on keywords
   o d61e580 Explicitly define NFData instance for ResultStatus
 + Set FlexibleContexts on src/Ganeti/WConfd/ConfigModifications.hs
Checksums-Sha1:
 79f5ae8a23fd459c9ad7a9da3cb0a6b23a07090e 3290 ganeti_2.15.1-2.dsc
 48ae7a986bb53155582b9e0192880670970f76ea 38872 ganeti_2.15.1-2.debian.tar.xz
 946776abdb10caa46ce77e4e2dff565e6ee852f3 863836 ganeti-2.15_2.15.1-2_all.deb
 

Bug#808312: chemps2: upgrade fail

[Sebastian Wouters]

Hi all,

I hope this fixes bug #808312:
http://anonscm.debian.org/cgit/debichem/packages/chemps2.git/commit/?id=6c7ed80faddc63765bc8e995c7fce14cfff81210
?

The only thing what happened in 1.6-2 is a move of the manpage from the
library (libchemps2-1) to the binary package (chemps2).

Best wishes,
Sebastian

Bug#805499: marked as done (libnanoxml2-java: FTBFS with bnd 2.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 22:22:33 +
with message-id 
and subject line Bug#805499: fixed in libnanoxml2-java 2.2.3.dfsg-5
has caused the Debian Bug report #805499,
regarding libnanoxml2-java: FTBFS with bnd 2.1.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.)


-- 
805499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnanoxml2-java
Version: 2.2.3.dfsg-4
Severity: serious
Tags: patch

Dear maintainer,

libnanoxml2-java FTBFS with bnd 2.1.0. Please find attached a patch
that fixes this issue.

Regards,

Markus
diff -u libnanoxml2-java-2.2.3.dfsg/debian/rules libnanoxml2-java-2.2.3.dfsg/debian/rules
--- libnanoxml2-java-2.2.3.dfsg/debian/rules
+++ libnanoxml2-java-2.2.3.dfsg/debian/rules
@@ -28,7 +28,7 @@
 LITE := nanoxml-lite.jar
 SAX := nanoxml-sax.jar
 
-#Architecture 
+#Architecture
 build: build-stamp
 
 build-stamp:
@@ -37,9 +37,12 @@
 	CLASSPATH=${NANOXML} jh_build -o'${JFLAGS}' -N ${SAX} Sources/SAX/
 	jh_manifest -c /usr/share/java/${NANOXML} ${SAX}
 
-	bnd wrap *.jar
-	rm *.jar
-	prename 's/bar/jar/' *.bar
+	bnd wrap --output $(NANOXML).tmp $(NANOXML)
+	bnd wrap --output $(LITE).tmp $(LITE)
+	bnd wrap --output $(SAX).tmp $(SAX)
+	mv $(NANOXML).tmp $(NANOXML)
+	mv $(LITE).tmp $(LITE)
+	mv $(SAX).tmp $(SAX)
 
 	${JAVA_HOME}/bin/javadoc -author -link /usr/share/doc/default-jdk-doc/api -quiet \
 	-sourcepath Sources/Java/:Sources/Lite/:Sources/SAX/ -source 1.4 \
@@ -61,12 +64,12 @@
 	rm -rf Test/*/*.class
 	rm -rf debian/orig.tmp || echo "No failed source fetch"
 
-	dh_clean 
+	dh_clean
 
 install:
 	dh_testdir
 	dh_testroot
-	dh_clean -k -i 
+	dh_clean -k -i
 
 	jh_installlibs -i
 	jh_installjavadoc -plibnanoxml2-java-doc
@@ -78,10 +81,10 @@
 binary-common:
 	dh_testdir
 	dh_testroot
-	dh_installchangelogs 
+	dh_installchangelogs
 	dh_installdocs
 	dh_link
-	dh_compress 
+	dh_compress
 	dh_fixperms
 	dh_installdeb
 	dh_gencontrol
diff -u libnanoxml2-java-2.2.3.dfsg/debian/changelog libnanoxml2-java-2.2.3.dfsg/debian/changelog
--- libnanoxml2-java-2.2.3.dfsg/debian/changelog
+++ libnanoxml2-java-2.2.3.dfsg/debian/changelog
@@ -1,3 +1,12 @@
+libnanoxml2-java (2.2.3.dfsg-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Transition to bnd 2.1.0.
+  * Do not depend on a Java runtime because the Java Policy does not require
+this anymore.
+
+ -- Markus Koschany   Wed, 18 Nov 2015 21:05:35 +0100
+
 libnanoxml2-java (2.2.3.dfsg-4) unstable; urgency=low
 
   * Removed no longer needed work around for 567899 (Closes: #573697)
diff -u libnanoxml2-java-2.2.3.dfsg/debian/control libnanoxml2-java-2.2.3.dfsg/debian/control
--- libnanoxml2-java-2.2.3.dfsg/debian/control
+++ libnanoxml2-java-2.2.3.dfsg/debian/control
@@ -5,7 +5,7 @@
 Build-Depends: debhelper (>= 5)
 Build-Depends-Indep: default-jdk-doc,
  default-jdk,
- bnd,
+ bnd (>= 2.1.0),
  perl,
  javahelper
 Standards-Version: 3.8.4.0
@@ -13,7 +13,7 @@
 
 Package: libnanoxml2-java
 Architecture: all
-Depends: default-jre-headless | java2-runtime-headless, ${misc:Depends}
+Depends: ${misc:Depends}
 Suggests: libnanoxml2-java-doc
 Description: small XML parser for Java
  NanoXML is a (actually more than one) small XML parser for Java. It
--- End Message ---
--- Begin Message ---
Source: libnanoxml2-java
Source-Version: 2.2.3.dfsg-5

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libnanoxml2-java 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: Wed, 23 Dec 2015 20:40:57 +0100
Source: libnanoxml2-java
Binary: libnanoxml2-java libnanoxml2-java-doc
Architecture: source all
Version: 2.2.3.dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java maintainers 

Bug#808862: redis: leaves redis-server processes running after build

[Chris Lamb]

tags 808862 + pending
thanks

Hm. The code *should* clean this up but I don't trust it enough (and can 
reproduce on some other build environments such as Travis-CI, although not 
locally) so have added a pkill.


Regards,

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

Processed: Re: redis: leaves redis-server processes running after build

[Debian Bug Tracking System]

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

> tags 808862 + pending
Bug #808862 [src:redis] redis: leaves redis-server processes running after build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#806560: python3-udiskie/python-udiskie do not start

[Thomas Gläßle]

> it works with --tray :)
>
> I fail to understand what does it without that parameter then :)

automount + notifications are enabled by default.


>
> thanks!
>
> G.
>
>




signature.asc
Description: OpenPGP digital signature

Bug#808730: stalin: Insecure use of temporary files

[Rob Browning]

Steve Kemp  writes:

> Package: stalin
> Version: 0.11-5
> Severity: critical
> Tags: security
>
>
> When `stalin` launches it attempts to detect its environment via
> the following code in /usr/lib/stalin/QobiScheme.sc:
>
>
> (system "uname -m >/tmp/QobiScheme.tmp")
> ...
> (system "rm -f /tmp/QobiScheme.tmp"))

I have a possible fix for this, which should affect all versions in
Debian (0.11-6 in stretch/sid, 0.11-5 in wheezy/jessie), and I think I
will be able to generate patches (and/or packages) if it seems
acceptable.

The current fix requires two primary changes, one is to stop overriding
the gcc optimization level on amd64 (to revert to the default -O2,
instead of -O0).  Otherwise gcc will segfault (tested against 5.3.1-3,
4.9.3-10, and 4.6.4-7), and we won't be able to build the package.

The second requires changes to the Scheme compiler itself to add support
for a few new functions (debian-popen-in, debian-popen-out, etc.), and
to then use them in stalin.sc and QobiScheme.sc to:

  - rework the (tmp "foo") function to use mktemp

  - replace all uses of fixed /tmp/ paths with use of mktemp, either via
the updated (tmp "foo"), or via a "mktemp -d ..."  temporary
directory.

Potential concerns:

  - This introduces new bindings, though I suspect the
"debian-" prefixes mitigate the likelihood of collisions with
any existing use.

  - The new code may not be heavily tested (though I suspect should be
safer than what we have now).  For example, some of the changes
involve functions that call mpeg_play, which doesn't appear to be in
Debian (anymore).

  - This will require rebuilding the pregenerated[1] C versions of the
compiler (20MB each, one per arch).  In the newer release, they're
in debian/prebuilt-src/.  In the older, they were at the top level.
This will result in a *very* large diff against the previous
versions.

[1] NB: the reason we have the pregenerated files is because creating
them requires ~2GB RAM and about an hour each on a fairly recent amd64
machine.  Though I'd be happy to dispense with them if/when we think
it's reasonable.

In any case, I wanted to contact the security team now, to get an idea
of how you might want to proceed, before I spend more time on the code.
I've nearly finished hacking up a first pass, but it's not likely to be
quite ready yet.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#808537: Please help (Was: Bug#808537: jellyfish: FTBFS: error: 'template class std::auto_ptr' is deprecated [-Werror=deprecated-declarations])

[Andreas Tille]

Hi Gert,

On Wed, Dec 23, 2015 at 06:46:28PM +0100, Gert Wollny wrote:
> > I was hoping that Gert could provide any hint how he fixed #778005
> > but he seems to be offline.  Any hint how to deal with his?
> 
> I was indeed AFK and will be a for few more hours. 

How were you able to respond without keyboard? ;-)
Very cool - thanks a lot!
 
> - Forwarded message from Andreas Tille  -
> > Cc: Gert Wollny 
> > Subject: Re: Bug#808537: jellyfish: FTBFS: error: 'template
> > class std::auto_ptr' is deprecated [-Werror=deprecated-declarations]
> 
> I'll take a look at the code later, but the problem is that when c++11
> is enabled (with g++5 the default I think), then std::auto_ptr is
> deprecated, hence there is a warning. But since someone decided to add
> the -Werror=deprecated-declarations compile flag this warning is
> propagated to an error. 
> 
> One fix is to remove the compile flag, another one replace
> std::auto_ptr with std::unique_ptr. 

I commited a patch but now one unit test is failing... :-(

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#808826: libkavorka-perl: FTBFS: Can't locate object method "_set_declared_name" via package "Kavorka::Sub::Fun"

[Niko Tyni]

retitle 808826 libparse-keyword-perl: breaks Moo::Role on Perl 5.22?
reassign 808826 libparse-keyword-perl 0.08-2
affects 808826 libmoops-perl libkavorka-perl
thanks

On Wed, Dec 23, 2015 at 08:03:33PM +0200, Niko Tyni wrote:
> On Wed, Dec 23, 2015 at 04:05:27PM +0200, Niko Tyni wrote:
> > Package: libkavorka-perl
> > Version: 0.036-1
> > Severity: serious
> > Forwarded: https://rt.cpan.org/Ticket/Display.html?id=109841
> > 
> > This package fails to build on current sid.
> 
> >   Can't locate object method "_set_declared_name" via package 
> > "Kavorka::Sub::Fun" at /<>/blib/lib/Kavorka/Sub.pm line 182.
> >   t/02named-functions.t .. 
> >   Dubious, test returned 255 (wstat 65280, 0xff00)
> 
> It's indeed a regression caused by the perl 5.20 -> 5.22 upgrade.
> Not sure why our rebuilds didn't catch it.

Evidence seems to be pointing at Parse::Keyword. This script:

  #!/usr/bin/perl -w
  use strict;
  
  package M;
  use Moo::Role;
  has myattr => (is => 'rwp');
  1;
  
  package main;
  use Parse::Keyword {};
  
  my $m = bless {}, 'M';
  $m->_set_myattr("foo");
  
  print $m->myattr, "\n";
  1;

outputs "foo" on 5.20 as expected, but dies on 5.22 with

  Can't locate object method "_set_myattr" via package "M" at m.pl line 13.

Removing the "use Parse::Keyword {};" line makes it go away.

The only two reverse dependencies (both build and runtime) of 
libparse-keyword-perl,
libkavorka-perl and libmoops-perl, both currently fail to build from source with
similar messages.

I'm therefore tentatively reassigning this to libparse-keyword-perl,
although it would be nice to distill this further down to something that
takes Moo::Role out of the equation.

I note that Parse::Keyword is officially not recommended for use, so
it might not be worth it blocking the Perl 5.22 transition for this.
Quoting:

DESCRIPTION
   DO NOT USE!
   This module has fundamental errors in the way it handles closures,
   which are not fixable. Runtime keywords will never be able to work
   properly with the current design of this module. There are certain
   cases where this module is still safe to use (keywords that only
   have effect at compile time, or keywords that never call any of
   the "parse_*" functions), but that is limiting enough to make
   this module mostly worthless, and I likely won't be continuing
   to maintain it. Be warned!

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

Processed: Re: Bug#808826: libkavorka-perl: FTBFS: Can't locate object method "_set_declared_name" via package "Kavorka::Sub::Fun"

[Debian Bug Tracking System]

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

> retitle 808826 libparse-keyword-perl: breaks Moo::Role on Perl 5.22?
Bug #808826 [libkavorka-perl] libkavorka-perl: FTBFS: Can't locate object 
method "_set_declared_name" via package "Kavorka::Sub::Fun"
Changed Bug title to 'libparse-keyword-perl: breaks Moo::Role on Perl 5.22?' 
from 'libkavorka-perl: FTBFS: Can't locate object method "_set_declared_name" 
via package "Kavorka::Sub::Fun"'
> reassign 808826 libparse-keyword-perl 0.08-2
Bug #808826 [libkavorka-perl] libparse-keyword-perl: breaks Moo::Role on Perl 
5.22?
Bug reassigned from package 'libkavorka-perl' to 'libparse-keyword-perl'.
No longer marked as found in versions libkavorka-perl/0.036-1.
Ignoring request to alter fixed versions of bug #808826 to the same values 
previously set
Bug #808826 [libparse-keyword-perl] libparse-keyword-perl: breaks Moo::Role on 
Perl 5.22?
Marked as found in versions libparse-keyword-perl/0.08-2.
> affects 808826 libmoops-perl libkavorka-perl
Bug #808826 [libparse-keyword-perl] libparse-keyword-perl: breaks Moo::Role on 
Perl 5.22?
Added indication that 808826 affects libmoops-perl and libkavorka-perl
> thanks
Stopping processing here.

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

Bug#808852: marked as done (elasticsearch: FTBFS: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.google.guava:guava:jar:18.0)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 22:19:46 +
with message-id 
and subject line Bug#808852: fixed in elasticsearch 1.7.3+dfsg-3
has caused the Debian Bug report #808852,
regarding elasticsearch: FTBFS: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
com.google.guava:guava:jar:18.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.)


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

elasticsearch fails to build from source in unstable/amd64:

  [..]

  -Dfile=/usr/share/java/jts.jar \
  -DgroupId=com.vividsolutions \
  -DartifactId=jts \
  -Dversion=fake \
  -Dpackaging=jar
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building elasticsearch 1.7.3
  [INFO] 

  [INFO] 
  [INFO] --- maven-install-plugin:2.5.2:install-file (default-cli) @ 
elasticsearch ---
  [INFO] Installing /usr/share/java/jts.jar to 
/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian/maven-repo/com/vividsolutions/jts/fake/jts-fake.jar
  [INFO] Installing /tmp/mvninstall1889937690685813395.pom to 
/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg/debian/maven-repo/com/vividsolutions/jts/fake/jts-fake.pom
  [INFO] 

  [INFO] BUILD SUCCESS
  [INFO] 

  [INFO] Total time: 0.801 s
  [INFO] Finished at: 2015-12-23T19:27:13+00:00
  [INFO] Final Memory: 8M/236M
  [INFO] 

  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3+dfsg'
 dh_auto_build -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151223192417.KQbN7JxyDK/elasticsearch-1.7.3\+dfsg/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building elasticsearch 1.7.3
  [INFO] 

  [WARNING] The POM for com.google.guava:guava:jar:18.0 is missing, no 
dependency information available
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.792 s
  [INFO] Finished at: 2015-12-23T19:27:16+00:00
  [INFO] Final Memory: 7M/236M
  [INFO] 

  [ERROR] Failed to execute goal on project elasticsearch: Could not resolve 
dependencies for project org.elasticsearch:elasticsearch:jar:1.7.3: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.google.guava:guava:jar:18.0 has not been downloaded from it 
before. -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] 

Bug#806560: python3-udiskie/python-udiskie do not start

[Gianfranco Costamagna]

Hi,



>Sadly, I found additional bugs with (a) python2 and (b) with the udisks1

>backend. Trying to get that fixed in the next 2-3 days, sorry for the
>inconvenience..


not a problem :)

>Did you start udiskie with `--tray`?
>Under which environment are you running? I've already noticed that
>ubuntu doesn't show the systray anymore. They replaced it with a similar
>notification area for which a different API (AppIndicator) must be used.


it works with --tray :)

I fail to understand what does it without that parameter then :)

thanks!

G.

Bug#808866: (snappy:15699): Clutter-CRITICAL **: The Clutter backend is not a X11 backend

[Steinar H. Gunderson]

On Wed, Dec 23, 2015 at 11:40:59PM +0100, Julian Andres Klode wrote:
> Package: snappy
> Severity: grave
> 
> Trying to run snappy just fails:
> 
> (snappy:15699): GLib-GObject-CRITICAL **: g_object_set: assertion 
> 'G_IS_OBJECT (object)' failed
> No media set. You can drag and drop a file into snappy to play it.
> Loading ui!

Hm, why did the BTS sent this to me? I do maintain the snappy source package,
but not the snappy _binary_ package (which has snappy-player as its source
package). Somehow BTS appears confused:

  Package: snappy; Maintainer for snappy is Steinar H. Gunderson 
; Source for snappy is src:snappy-player.

BTS owners, do you have anything to add?

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

Bug#808862: redis: leaves redis-server processes running after build

[Julien Cristau]

On Wed, Dec 23, 2015 at 22:23:36 +, Chris Lamb wrote:

> tags 808862 + pending
> thanks
> 
> Hm. The code *should* clean this up but I don't trust it enough (and can 
> reproduce on some other build environments such as Travis-CI, although not 
> locally) so have added a pkill.
> 
FWIW I had to pkill -9 redis on a couple of buildds, just pkill
apparently wasn't enough.

Cheers,
Julien


signature.asc
Description: PGP signature

Bug#808862: marked as done (redis: leaves redis-server processes running after build)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 23:22:30 +
with message-id 
and subject line Bug#808862: fixed in redis 2:3.2~rc1-3
has caused the Debian Bug report #808862,
regarding redis: leaves redis-server processes running after build
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.)


-- 
808862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redis
Version: 3.2~rc1-2
Severity: serious

Hi,

the redis build seems to leave redis-server processes running,
presumably from tests.  Seen on hasse.debian.org:

$ ps `pgrep -u buildd`
  PID TTY  STAT   TIME COMMAND
  873 ?Ss 0:37 /usr/bin/perl /usr/bin/buildd
 4973 ?S  0:01 /usr/bin/perl /usr/bin/sbuild --apt-update 
--no-apt-upgrade --no-apt-distupgrade --batch --stats-dir=/home/buildd/stats 
--dist=experimental --sbuild-mode=buildd --mailfrom=buildd on hasse 

Bug#808874: debian-installer: FTBFS on i386: 586 vs. 686

[Cyril Brulebois]

Source: debian-installer
Severity: serious
Justification: FTBFS

Hi,

linux received this change a while ago, and it has now reached
unstable and testing:
| linux (4.3~rc3-1~exp1) experimental; urgency=medium
| 
| […]
|   * [i386] Replace 586 flavour with 686
| - Enable support for OLPC and other Geode-based systems in the 686 flavour
| - udeb: Update kernel-versions
| 
|  -- Ben Hutchings   Sun, 27 Sep 2015 21:02:54 +0100

so d-i no longer builds on i386. A few packages have to be tweaked for
this kind of changes; I'm x-d-cc-ing the kernel team as Ben did most of
the work past time.

Mraw,
KiBi.

Bug#808842: glib2.0: FTBFS with PCRE 8.38: regex (?(?<ab)) produces different error

[Matthew Vernon]

On 23/12/15 17:23, Simon McVittie wrote:


X-Debbugs-Cc set to libpc...@packages.debian.org. Matthew, it would be
great if you could upload new pcre3 versions to experimental initially,


Sorry; I'll try and remember to do so for the next upstream release 
(which won't be for a while).


Regards,

Matthew

Bug#808858: [gimp] terminate called after throwing an instance of 'std::bad_alloc'

[Philipp Klaus Krause]

Package: gimp
Version: 2.8.16-1
Severity: serious

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

I cannot start gimp, get "terminate called after throwing an instance of
'std::bad_alloc'". Here's a gdb backtrace:

philipp@notebook4:~$ gdb gimp
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gimp...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gimp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe06ee700 (LWP 15598)]
[New Thread 0x7fffdfeed700 (LWP 15599)]
[New Thread 0x7fffdf6ec700 (LWP 15600)]
[New Thread 0x7fffdeeeb700 (LWP 15601)]
[Thread 0x7fffdeeeb700 (LWP 15601) exited]
[Thread 0x7fffdf6ec700 (LWP 15600) exited]
[Thread 0x7fffdfeed700 (LWP 15599) exited]
[Thread 0x7fffe06ee700 (LWP 15598) exited]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Program received signal SIGABRT, Aborted.
0x72f94657 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
55  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht
gefunden.
(gdb) bt
#0  0x72f94657 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x72f95a2a in __GI_abort () at abort.c:89
#2  0x7fffeacfd35d in __gnu_cxx::__verbose_terminate_handler() ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x7fffeacfb3b6 in ?? () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7fffeacfb401 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x7fffeacfb619 in __cxa_throw () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x7fffeacfbb2c in operator new(unsigned long) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x7fffe19d9648 in ?? () from
/usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1
#8  0x7fffe19d9769 in
llvm::MemoryBuffer::getMemBuffer(llvm::StringRef, llvm::StringRef, bool)
() from /usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1
#9  0x7fffe5a77950 in ?? () from
/usr/lib/x86_64-linux-gnu/beignet//libgbe.so
#10 0x7fffe5a78c13 in ?? () from
/usr/lib/x86_64-linux-gnu/beignet//libgbe.so
#11 0x7fffea3fe12f in ?? () from
/usr/lib/x86_64-linux-gnu/beignet//libcl.so
#12 0x7fffea3f57d6 in clBuildProgram () from
/usr/lib/x86_64-linux-gnu/beignet//libcl.so
#13 0x7fffea40a589 in ?? () from
/usr/lib/x86_64-linux-gnu/beignet//libcl.so
#14 0x7fffea40a72b in ?? () from
/usr/lib/x86_64-linux-gnu/beignet//libcl.so
#15 0x7fffea64c716 in ?? () from /usr/lib/x86_64-linux-gnu/libOpenCL.so
#16 0x7fffea64cd2b in clGetPlatformIDs () from
/usr/lib/x86_64-linux-gnu/libOpenCL.so
#17 0x74bf500c in ?? () from
/usr/lib/x86_64-linux-gnu/libgegl-0.3.so.0
#18 0x74bf5c1b in ?? () from
/usr/lib/x86_64-linux-gnu/libgegl-0.3.so.0
#19 0x74ba6af7 in ?? () from
/usr/lib/x86_64-linux-gnu/libgegl-0.3.so.0
#20 0x73d48015 in g_closure_invoke () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x73d5a061 in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x73d62dfc in g_signal_emit_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x73d6312f in g_signal_emit () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x73d4c544 in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x73d4bdf8 in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x73d4f86d in g_object_set_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x73d5003c in g_object_set () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x74ba74e5 in ?? () from
/usr/lib/x86_64-linux-gnu/libgegl-0.3.so.0
#29 0x7387bd68 in g_option_context_parse () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7387cc24 in g_option_context_parse_strv () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x0048232e in main ()
(gdb)




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

Debian Release: stretch/sid
  500 unstableftp.de.debian.org
  500 testing ftp.de.debian.org
1 experimentalftp.de.debian.org

--- Package information. ---
Depends(Version) | Installed

Bug#796931: gnupg-agent: no longer writes $GNUPGHOME/gpg-agent-info-$(hostname) file

[Thorsten Glaser]

On Wed, 23 Dec 2015, Axel Beckert wrote:

> Having "gpg-agent --daemon" outputting lines like
> "GPG_AGENT_INFO=/tmp/gpg-4hLrL9/S.gpg-agent:5152:1; export
> GPG_AGENT_INFO;" respectively setting this in the child process'
> environment as it did before would fix the issue for me. But there

Indeed. I have a workaround now. Look at the git revision log for…
https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=posix/sysadmin/agents.sh;h=485f025a5171a0721bb0cb10c3676f96393715f3;hb=HEAD
… to see what I did. (That script is supposed to end up in e.g.
/etc/profile.d/ and automatically runs ssh-agent and gpg-agent.)

bye,
//mirabilos
-- 
Yes, I hate users and I want them to suffer.
-- Marco d'Itri on gmane.linux.debian.devel.general

Bug#808763: [Python-modules-team] Bug#808763: Running pytest

[Barry Warsaw]

On Dec 23, 2015, at 07:20 PM, Tristan Seligmann wrote:

>If you want to run pytest with a particular version of python, then
>"pythonX.Y -m pytest" is a much better way than relying on the py.test-X.Y
>scripts.

Sorry, I've had no time to respond in detail, but in general I agree with
this.  It's true of any version-specific script (e.g. pip) even if it is a
less user-friendly ui.

Bug#808246: Maybe the bugs are related

[Gianluca Renzi]

In this case I suppose even the userspace code (dynamic linking library)
could not to be used
with this linker bug and not only the kernel module loader tool. The
undefined symbols are discarded in every way. The only way to ensure a
correct code buildup is to use a -static linking of any external library in
every piece of code. So no dynamic linking is usable in that way. This bug
seems so unreal to me...
Are the gcc team people so silly not to try any created code (even a simple
checking for an external library) in every supported platform for binutils
and gcc???
I suppose not. Are you sure of the bug?
Can you ask the gnu gcc people to test the ld in a kvm with ppc64 machine?

On Tue, Dec 22, 2015 at 11:45 PM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

> I found indications that perhaps both problems are in fact caused by ld
> no longer including undefined symbols in the output.
>
> Here is a section from the working module built with old binutils:
>
>   0012980: 0047 4343 3a20 2844 6562 6961 6e20 342e  .GCC: (Debian 4.
>   0012990: 392e 322d 3130 2920 342e 392e 3200 0047  9.2-10) 4.9.2..G
>   00129a0: 4343 3a20 2844 6562 6961 6e20 342e 392e  CC: (Debian 4.9.
>   00129b0: 322d 3130 2920 342e 392e 3200 0047 4343  2-10) 4.9.2..GCC
>   00129c0: 3a20 2844 6562 6961 6e20 342e 392e 322d  : (Debian 4.9.2-
>   00129d0: 3130 2920 342e 392e 3200 0047 4343 3a20  10) 4.9.2..GCC:
>   00129e0: 2844 6562 6961 6e20 342e 392e 322d 3130  (Debian 4.9.2-10
>   00129f0: 2920 342e 392e 3200 0047 4343 3a20 2844  ) 4.9.2..GCC: (D
>   0012a00: 6562 6961 6e20 342e 392e 322d 3130 2920  ebian 4.9.2-10)
>   0012a10: 342e 392e 3200 0047 4343 3a20 2844 6562  4.9.2..GCC: (Deb
>   0012a20: 6961 6e20 342e 392e 322d 3130 2920 342e  ian 4.9.2-10) 4.
>   0012a30: 392e 3200 0047 4343 3a20 2844 6562 6961  9.2..GCC: (Debia
>   0012a40: 6e20 342e 392e 322d 3130 2920 342e 392e  n 4.9.2-10) 4.9.
>   0012a50: 3200 0047 4343 3a20 2844 6562 6961 6e20  2..GCC: (Debian
>   0012a60: 342e 392e 322d 3130 2920 342e 392e 3200  4.9.2-10) 4.9.2.
>   0012a70: 002e 7379 6d74 6162 002e 7374 7274 6162  ..symtab..strtab
>   0012a80: 002e 7368 7374 7274 6162 002e 6e6f 7465  ..shstrtab..note
>   0012a90: 2e67 6e75 2e62 7569 6c64 2d69 6400 2e72  .gnu.build-id..r
>   0012aa0: 656c 612e 7465 7874 002e 7265 6c61 2e69  ela.text..rela.i
>   0012ab0: 6e69 742e 7465 7874 002e 7265 6c61 2e66  nit.text..rela.f
>   0012ac0: 6978 7570 002e 7265 6c61 2e65 7869 742e  ixup..rela.exit.
>   0012ad0: 7465 7874 002e 7265 6c61 2e74 6578 742e  text..rela.text.
>   0012ae0: 756e 6c69 6b65 6c79 002e 7265 6c61 5f5f  unlikely..rela__
>   0012af0: 6b73 796d 7461 625f 6770 6c00 2e72 656c  ksymtab_gpl..rel
>   0012b00: 612e 726f 6461 7461 002e 7265 6c61 5f5f  a.rodata..rela__
>   0012b10: 6275 675f 7461 626c 6500 2e72 6f64 6174  bug_table..rodat
>   0012b20: 612e 7374 7231 2e38 002e 7265 6c61 5f5f  a.str1.8..rela__
>   0012b30: 6d63 6f75 6e74 5f6c 6f63 002e 7265 6c61  mcount_loc..rela
>   0012b40: 5f5f 6578 5f74 6162 6c65 005f 5f6b 7379  __ex_table.__ksy
>   0012b50: 6d74 6162 5f73 7472 696e 6773 002e 6d6f  mtab_strings..mo
>   0012b60: 6469 6e66 6f00 5f5f 7665 7273 696f 6e73  dinfo.__versions
>   0012b70: 002e 7265 6c61 5f5f 6b63 7263 7461 625f  ..rela__kcrctab_
>   0012b80: 6770 6c00 2e72 656c 612e 6461 7461 002e  gpl..rela.data..
>   0012b90: 7265 6c61 2e64 6174 612e 7265 6c2e 726f  rela.data.rel.ro
>   0012ba0: 002e 7265 6c61 2e6f 7064 002e 7265 6c61  ..rela.opd..rela
>   0012bb0: 2e74 6f63 002e 7265 6c61 2e67 6e75 2e6c  .toc..rela.gnu.l
>   0012bc0: 696e 6b6f 6e63 652e 7468 6973 5f6d 6f64  inkonce.this_mod
>   0012bd0: 756c 6500 2e62 7373 002e 7374 7562 7300  ule..bss..stubs.
>   0012be0: 2e66 7472 6163 652e 7472 616d 7000 2e63  .ftrace.tramp..c
>   0012bf0: 6f6d 6d65 6e74       omment..
>
> And the same section from the new binutils build (the disassenmbled
> module is totally identical as far as code is concerned):
>
>   0012980: 0047 4343 3a20 2844 6562 6961 6e20 342e  .GCC: (Debian 4.
>   0012990: 392e 322d 3130 2920 342e 392e 3200 0047  9.2-10) 4.9.2..G
>   00129a0: 4343 3a20 2844 6562 6961 6e20 342e 392e  CC: (Debian 4.9.
>   00129b0: 322d 3130 2920 342e 392e 3200 0047 4343  2-10) 4.9.2..GCC
>   00129c0: 3a20 2844 6562 6961 6e20 342e 392e 322d  : (Debian 4.9.2-
>   00129d0: 3130 2920 342e 392e 3200 0047 4343 3a20  10) 4.9.2..GCC:
>   00129e0: 2844 6562 6961 6e20 342e 392e 322d 3130  (Debian 4.9.2-10
>   00129f0: 2920 342e 392e 3200 0047 4343 3a20 2844  ) 4.9.2..GCC: (D
>   0012a00: 6562 6961 6e20 342e 392e 322d 3130 2920  ebian 4.9.2-10)
>   0012a10: 342e 392e 3200 0047 4343 3a20 2844 6562  4.9.2..GCC: (Deb
>   0012a20: 6961 6e20 342e 392e 322d 3130 2920 342e  ian 4.9.2-10) 4.
>   0012a30: 392e 3200 0047 4343 3a20 2844 6562 6961  9.2..GCC: (Debia
>   0012a40: 6e20 342e 392e 322d 3130 2920 342e 392e  n 4.9.2-10) 4.9.
>   0012a50: 3200 0047 4343 3a20 2844 6562 6961 6e20  2..GCC: (Debian
>   0012a60: 342e 392e 322d 3130 2920 342e 392e 3200  

Bug#804149: marked as done (CVE-2015-5602: Unauthorized privilege escalation in sudoedit)

[Debian Bug Tracking System]

Your message dated Thu, 24 Dec 2015 05:19:31 +
with message-id 
and subject line Bug#804149: fixed in sudo 1.8.15-1
has caused the Debian Bug report #804149,
regarding CVE-2015-5602: Unauthorized privilege escalation in sudoedit
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.)


-- 
804149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sudo
Version: 1.7.4p4-2.squeeze.4
Severity: critical
Tags: upstream security
Justification: root security hole

Hi,

Apparently a security has been disclosed (CVE-2015-5602) allowing users
to open files with sudoedit that is not supposed to using a symlinks,
see: https://www.exploit-db.com/exploits/37710/

Upstream has released a new fixed version by no following the symlinks
by default.

But according to this comment[0], this is not fixing the issue
completely.

Cheers,

Laurent Bigonville

[0]
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1512781/comments/1
--- End Message ---
--- Begin Message ---
Source: sudo
Source-Version: 1.8.15-1

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated sudo 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: Wed, 23 Dec 2015 11:15:22 -0700
Source: sudo
Binary: sudo sudo-ldap
Architecture: source amd64
Version: 1.8.15-1
Distribution: unstable
Urgency: low
Maintainer: Bdale Garbee 
Changed-By: Bdale Garbee 
Description:
 sudo   - Provide limited super user privileges to specific users
 sudo-ldap  - Provide limited super user privileges to specific users
Closes: 804149
Changes:
 sudo (1.8.15-1) unstable; urgency=low
 .
   * new upstream version, closes: #804149
   * use --with-exampledir to deliver example files more cleanly
Checksums-Sha1:
 5b96d2b4e4a7905a7364b4289a456a467839b515 1954 sudo_1.8.15-1.dsc
 acb5ff3f38fa9e0365f6a91a6620b9846e2ad843 2660128 sudo_1.8.15.orig.tar.gz
 40e11c6db71650b97d42d829a982a598ddb58f7b 22780 sudo_1.8.15-1.debian.tar.xz
 12a5283ab6d39b362a798fc9746a6bb866d4264d 632758 sudo-dbgsym_1.8.15-1_amd64.deb
 e4159a1a9f09737a26399c0feaed3dd6ed73ce72 655768 
sudo-ldap-dbgsym_1.8.15-1_amd64.deb
 4e745063614f18882a43ed33b32397868312718d 1011496 sudo-ldap_1.8.15-1_amd64.deb
 415d181becb2f77ae7e2e71cfeba9d1464dd70a7 982480 sudo_1.8.15-1_amd64.deb
Checksums-Sha256:
 c527c16ccb8f8fb53a22ddb9e52abfba4952a77eb7c0a3fabf2e0c568a45da61 1954 
sudo_1.8.15-1.dsc
 4316381708324da8b6cb151f655c1a11855207c7c02244d8ffdea5104d7cc308 2660128 
sudo_1.8.15.orig.tar.gz
 a9ff349974c2a7926aa7e61a0ed3bd41ed45c188a348ec813417c9131e0158dc 22780 
sudo_1.8.15-1.debian.tar.xz
 595df09993452ed99304f76c95f3363a655d935416bc4eda06c796af86ff792d 632758 
sudo-dbgsym_1.8.15-1_amd64.deb
 aadb1f17f226f8cb06be0f4cf629e1195b9c08421766fd1d87ed295c96ec37bc 655768 
sudo-ldap-dbgsym_1.8.15-1_amd64.deb
 6c4e0b332f642b6a849a8d943e1e085d5e26c4eff6e4a286a82514b296134958 1011496 
sudo-ldap_1.8.15-1_amd64.deb
 f27ad382ff5ca16d09deaee68ecceb3ab536f0249f59fb2307f543e9b7597c71 982480 
sudo_1.8.15-1_amd64.deb
Files:
 e048d01594338c5a1c40c74d8847cc1b 1954 admin optional sudo_1.8.15-1.dsc
 7cf6b9b76d0478a572432bed481dd7b5 2660128 admin optional sudo_1.8.15.orig.tar.gz
 122d9ea4b9b46dd5c2942e759dd33e74 22780 admin optional 
sudo_1.8.15-1.debian.tar.xz
 db5915be9c65b8753ae739b88018c06c 632758 debug extra 
sudo-dbgsym_1.8.15-1_amd64.deb
 7f2b0e5655b5360b956f55e42ab410a5 655768 debug extra 
sudo-ldap-dbgsym_1.8.15-1_amd64.deb
 2fea6b2268a3eac717e71e9e3782211c 1011496 admin optional 
sudo-ldap_1.8.15-1_amd64.deb
 2fcf93dab9350e5a3a7e45431abade59 982480 admin optional sudo_1.8.15-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVnt6DzqTYZbAldlBAQoZHBAAkWJZavqtfPQKvGQ6dU4MeUIEFiSYYMXF
RLOFLTsEqfo6YwEobGUdLRH60Ozyt6OU/R9U+txEW/BY8LaGlDWYuGUeDhK0GinO
Wc5xJ8HkcHHqkHS5TkKKWBq03RFEJMfOI7yU5SegfSIU8ZsJIeUxXR0KUUYO+kWA

Processed: Re: [Pkg-fonts-devel] Bug#808109: fonts-droid-fallback and fonts-droid: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +help
Bug #808109 [fonts-droid-fallback] fonts-droid-fallback and fonts-droid: error 
when trying to install together
Added tag(s) help.

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

Bug#808109: [Pkg-fonts-devel] Bug#808109: fonts-droid-fallback and fonts-droid: error when trying to install together

[Vasudev Kamath]

Control: tag -1 +help

Ralf Treinen  writes:

> Hi again,
>
> sorry but this is not fixed in fonts-android/1:6.0.1r3-1 :
>
> Selecting previously unselected package fonts-droid.
> (Reading database ... 10935 files and directories currently installed.)
> Preparing to unpack .../fonts-droid_1%3a4.4.4r2-7_all.deb ...
> Unpacking fonts-droid (1:4.4.4r2-7) ...
> Selecting previously unselected package fonts-droid-fallback.
> Preparing to unpack .../fonts-droid-fallback_1%3a6.0.1r3-1_all.deb ...
> Unpacking fonts-droid-fallback (1:6.0.1r3-1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/fonts-droid-fallback_1%3a6.0.1r3-1_all.deb (--unpack):
>  trying to overwrite 
> '/usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf', which is also in 
> package fonts-droid 1:4.4.4r2-7
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/fonts-droid-fallback_1%3a6.0.1r3-1_all.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm just wondering why Breaks and Replaces is not having any affect. Or
do I need conflicts relation here?

Any case any suggestion or help is appreciated :-).

Bug#808900: haskell-nats: FTBFS: Haddock failed (no modules?), refusing to create empty documentation package.

[Chris Lamb]

Source: haskell-nats
Version: 1-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,

haskell-nats fails to build from source in unstable/amd64:

  [..]

  Running hscolour for nats-1...
  creating dist-ghc/doc/html/nats
  creating dist-ghc/doc/html
  creating dist-ghc/doc
  creating dist-ghc/doc/html
  creating dist-ghc/doc/html/nats
  Preprocessing library nats-1...
  creating dist-ghc/doc/html/nats/src
  /usr/bin/HsColour -print-css -odist-ghc/doc/html/nats/src/hscolour.css
  /usr/bin/ghc --print-libdir
  Preprocessing library nats-1...
  creating dist-ghc/doc/html/nats
  /usr/bin/haddock 
'--prologue=dist-ghc/doc/html/nats/haddock-prologue1804289383846930886.txt' 
'--dump-interface=dist-ghc/doc/html/nats/nats.haddock' '--package-name=nats' 
'--package-version=1' '--source-module=src/%{MODULE/./-}.html' 
'--source-entity=src/%{MODULE/./-}.html#%{NAME}' 
'--source-entity-line=src/%{MODULE/./-}.html#line-%{LINE}' '--verbosity=1' 
--html --hoogle '--odir=dist-ghc/doc/html/nats/' '--title=nats-1: Natural 
numbers' '--optghc=-fbuilding-cabal-package' '--optghc=-O' 
'--optghc=-outputdir' '--optghc=dist-ghc/build' '--optghc=-odir' 
'--optghc=dist-ghc/build/tmp-1869' '--optghc=-hidir' 
'--optghc=dist-ghc/build/tmp-1869' '--optghc=-stubdir' 
'--optghc=dist-ghc/build/tmp-1869' '--optghc=-i' '--optghc=-idist-ghc/build' 
'--optghc=-i.' '--optghc=-idist-ghc/build/autogen' 
'--optghc=-Idist-ghc/build/autogen' '--optghc=-Idist-ghc/build' 
'--optghc=-optP-D__HADDOCK_VERSION__=2161' '--optghc=-optP-include' 
'--optghc=-optPdist-ghc/build/autogen/cabal_macros.h' 
'--optghc=-this-package-key' '--optghc=nats_Fmk0Emc1i6fF1ZuCqfyZlm' 
'--optghc=-hide-all-packages' '--optghc=-no-user-package-db' 
'--optghc=-package-db' '--optghc=/var/lib/ghc/package.conf.d' 
'--optghc=-XHaskell98' -B/usr/lib/ghc
  haddock: No input file(s).
  Haddock failed (no modules?), refusing to create empty documentation package.
  /usr/share/cdbs/1/class/hlibrary.mk:173: recipe for target 
'build-haddock-stamp' failed
  make: *** [build-haddock-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


haskell-nats.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808898: python-crontab: FTBFS: ImportError: Entry point ('console_scripts', 'py.test-3.5') not found

[Chris Lamb]

Source: python-crontab
Version: 1.9.3-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,

python-crontab fails to build from source in unstable/amd64:

  [..]

  I: pybuild base:184: /usr/bin/python3 setup.py build 
  running build
  running build_py
  copying crontab.py -> 
/home/lamby/temp/cdt.20151224075055.23cbJ3liwi/python-crontab-1.9.3/.pybuild/pythonX.Y_3.4/build
  copying cronlog.py -> 
/home/lamby/temp/cdt.20151224075055.23cbJ3liwi/python-crontab-1.9.3/.pybuild/pythonX.Y_3.4/build
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151224075055.23cbJ3liwi/python-crontab-1.9.3'
  PYBUILD_SYSTEM=custom \
  PYBUILD_TEST_ARGS="py.test-{version}" \
  LC_ALL=C.UTF-8 \
  dh_auto_test
  I: pybuild base:184: py.test-2.7
  = test session starts 
==
  platform linux2 -- Python 2.7.11, pytest-2.8.5, py-1.4.31, pluggy-0.3.1
  rootdir: /home/lamby/temp/cdt.20151224075055.23cbJ3liwi/python-crontab-1.9.3, 
inifile: 
  collected 103 items
  
  tests/test_compatibility.py 
  tests/test_croniter.py 
  tests/test_enums.py 
  tests/test_every.py 
  tests/test_frequency.py 
  tests/test_interaction.py ...
  tests/test_log.py ..
  tests/test_range.py .
  tests/test_removal.py .
  tests/test_system_cron.py ..
  tests/test_usage.py 
  tests/test_utf8.py ..
  
  == 103 passed in 0.39 seconds 
==
  I: pybuild base:184: py.test-3.5
  Traceback (most recent call last):
File "/usr/bin/py.test-3.5", line 9, in 
  load_entry_point('pytest==2.8.5', 'console_scripts', 'py.test-3.5')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, 
in load_entry_point
  return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2719, 
in load_entry_point
  raise ImportError("Entry point %r not found" % ((group, name),))
  ImportError: Entry point ('console_scripts', 'py.test-3.5') not found
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: 
py.test-3.5
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 3.4 
--dir . returned exit code 13
  debian/rules:9: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151224075055.23cbJ3liwi/python-crontab-1.9.3'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-crontab.1.9.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808899: android-platform-frameworks-base: FTBFS: undefined reference to `pseudolocalize_string(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'

[Chris Lamb]

Source: android-platform-frameworks-base
Version: 21-2
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,

android-platform-frameworks-base fails to build from source in unstable/amd64:

  [..]
  g++ -O2 -fPIC -Wno-format-y2k -I../../include -I/usr/include/android -include 
/usr/include/android/arch/linux-x86/AndroidConfig.h -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  
-c -o ZipEntry.o ZipEntry.cpp
  g++ -O2 -fPIC -Wno-format-y2k -I../../include -I/usr/include/android -include 
/usr/include/android/arch/linux-x86/AndroidConfig.h -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  
-c -o ZipFile.o ZipFile.cpp
  g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o aapt AaptAssets.o 
Command.o CrunchCache.o FileFinder.o Main.o Package.o StringPool.o XMLNode.o 
ResourceFilter.o ResourceTable.o Images.o Resource.o SourcePos.o ZipEntry.o 
ZipFile.o -lrt -ldl -lpthread -lz -lexpat -lpng -L/usr/lib/android  -lcutils 
-lhost -llog -lutils -L../../libs/androidfw  -landroidfw 
  XMLNode.o: In function `parseStyledString(Bundle*, char const*, 
android::ResXMLTree*, android::String16 const&, android::String16*, 
android::Vector*, bool, bool)':
  
/home/lamby/temp/cdt.20151224075332.p4r7Xir37v/android-platform-frameworks-base-21/tools/aapt/XMLNode.cpp:214:
 undefined reference to `pseudolocalize_string(std::__cxx11::basic_string const&)'
  collect2: error: ld returned 1 exit status
  Makefile:25: recipe for target 'aapt' failed
  make[2]: *** [aapt] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151224075332.p4r7Xir37v/android-platform-frameworks-base-21/tools/aapt'
  Makefile:4: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151224075332.p4r7Xir37v/android-platform-frameworks-base-21'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:21: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


android-platform-frameworks-base.21-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808896: python-csscompressor: FTBFS: ImportError: Entry point ('console_scripts', 'py.test-3.5') not found

[Chris Lamb]

Source: python-csscompressor
Version: 0.9.4-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,

python-csscompressor fails to build from source in unstable/amd64:

  [..]

 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151224074419.oCO0VfdaIZ/python-csscompressor-0.9.4'
  pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
  pyversions: missing debian/pyversions file, fall back to supported versions
  py3versions: no X-Python3-Version in control file, using supported versions
  ===> Running tests
  set -e ; set -x ; for i in 2.7 3.5 3.4 ; do \
PYMAJOR=`echo $i | cut -d'.' -f1` ; \
echo "===> Testing with python$i (python$PYMAJOR)" ; \
py.test-$i csscompressor/tests ; \
  done
  + echo 2.7
  + cut -d. -f1
  + PYMAJOR=2
  + echo ===> Testing with python2.7 (python2)
  ===> Testing with python2.7 (python2)
  + py.test-2.7 csscompressor/tests
  = test session starts 
==
  platform linux2 -- Python 2.7.11, pytest-2.8.5, py-1.4.31, pluggy-0.3.1
  rootdir: 
/home/lamby/temp/cdt.20151224074419.oCO0VfdaIZ/python-csscompressor-0.9.4, 
inifile: 
  collected 70 items
  
  csscompressor/tests/test_compress.py .
  csscompressor/tests/test_other.py ...
  csscompressor/tests/test_partition.py 
  csscompressor/tests/test_yui.py 
..
  
  == 70 passed in 0.12 seconds 
===
  + echo 3.5
  + cut -d. -f1
  + PYMAJOR=3
  + echo ===> Testing with python3.5 (python3)
  ===> Testing with python3.5 (python3)
  + py.test-3.5 csscompressor/tests
  Traceback (most recent call last):
File "/usr/bin/py.test-3.5", line 9, in 
  load_entry_point('pytest==2.8.5', 'console_scripts', 'py.test-3.5')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, 
in load_entry_point
  return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2719, 
in load_entry_point
  raise ImportError("Entry point %r not found" % ((group, name),))
  ImportError: Entry point ('console_scripts', 'py.test-3.5') not found
  debian/rules:25: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151224074419.oCO0VfdaIZ/python-csscompressor-0.9.4'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-csscompressor.0.9.4-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#806560: python3-udiskie/python-udiskie do not start

[Gianfranco Costamagna]

Hi Greg and Thomas, 


I just switched to gtk-3, and pushed the new release on unstable.

udiskie-mount and udiskie-umount still work, and now launching udiskie from 
console doesn't show any bad error.
However I don't see the icon come up, not sure if because I don't have any disk 
attached or because some runtime dependency is missing...

Thomas, can you enlight me?

(I still haven't ever used that trayicon)

cheers!

Gianfranco



Il Venerdì 18 Dicembre 2015 18:03, Gianfranco Costamagna 
 ha scritto:



Hi,  yes i found the same, but I failed to find the time to fix the gtk issue. 
Honestly i always used the cmdline tool!

I'll try to look at it soon I hope

Thanks for confirming the issue

G.


Sent from Yahoo Mail on Android

On Fri, 18 Dec, 2015 at 16:11, Greg Bognar
> wrote:
>Hi,
>
>After some more testing, it seems that udiskie works fine, it automounts
>volumes and even presents the password dialog window for encrypted volumes.
>
>What is *not* working is the menu that you are supposed to get when you
>click on the system tray icon.  More precisely, it works on one of my
>laptops but not on another one (both under i3).
>
>So it seems that the problem is some missing dependency -- probably some
>gtk2/3 library that is present on one of my machines but not the other one.
>I will try to compare the list of packages on the two machines.  In any
>case, it seems this bug could be fixed by adding the missing library to the
>package(s)'s dependencies.
>
>Cheers,
>Greg
>
>
>On Wed, 16 Dec 2015 14:25:02 + (UTC), Gianfranco Costamagna wrote:
>> 
>> Hi,
>> 
>> I don't use udiskie too much anymore,
>> so if anybody wants to give a try to this package is really welcome.
>> (also to maintain it)
>> 
>> I tried to fix this problem, but I failed, and I will probably not have time 
>> to look at it until a few weeks
>> 
>> cheers,
>> 
>> G.
>

Bug#799718: marked as done (libthread-pool-perl: nondeterministic test failure in t/Pool01.t)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 10:27:02 +
with message-id 
and subject line Bug#799718: fixed in libthread-pool-perl 0.33-2
has caused the Debian Bug report #799718,
regarding libthread-pool-perl: nondeterministic test failure in t/Pool01.t
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.)


-- 
799718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libthread-pool-perl
Version: 0.33-1
Severity: important

This package failed to build in the reproducible.debian.net CI setup,
and I can reproduce this locally by running the test in a loop while
loading the host. Apparently there's a race condition in the test suite.

  t/Pool01.t .. 
  1..42
  ok 1 - use Thread::Pool;
  # Test general functionality
  ok 2 - 'check object type' isa 'Thread::Pool'
  ok 3 - Thread::Pool->can(...)
  ok 4 - check number of workers
  ok 5 - check \# jobs todo, \#1
  ok 6 - check number of workers, \#1
  ok 7 - check first jobid
  ok 8 - check second jobid
  ok 9 - check tid of 2nd worker thread
  ok 10 - check number of workers, \#2
  ok 11 - check number of workers, \#3
  ok 12 - check number of workers, \#4
  ok 13 - check number of removed, \#1
  not ok 14 - check \# jobs todo, \#2
  #   Failed test 'check \# jobs todo, \#2'
  #   at t/Pool01.t line 77.
  ok 15 - check result_dontwait
  ok 16 - check result
  ok 17 - check third jobid
  ok 18 - check result remove
  ok 19 - check number of workers, \#5
  ok 20 - check number of removed, \#2
  ok 21 - check for remaining threads
  ok 22 - check number of workers, \#6
  ok 23 - check number of removed, \#3
  ok 24 - check \# jobs todo, \#3
  ok 25 - check \# jobs done, \#3
  ok 26 - check not-used threads, \#1
  ok 27 - 'check object type' isa 'Thread::Pool'
  ok 28 - check fourth jobid
  ok 29 - check number of workers, \#7
  ok 30 - check result after add
  ok 31 - check result waitfor
  ok 32 - check fifth jobid
  ok 33 - check result after add
  ok 34 - check whether job id found ok
  ok 35 - check sixth jobid
  ok 36 - check result remove_me
  ok 37 - check \# jobs todo, \#4
  ok 38 - check \# jobs done, \#4
  ok 39 - check number of workers, \#7
  ok 40 - check number of removed, \#4
  ok 41 - check for remaining threads
  ok 42 - check not-used threads, \#2
  # Looks like you failed 1 test of 42.
  Dubious, test returned 1 (wstat 256, 0x100)
  Failed 1/42 subtests 
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libthread-pool-perl
Source-Version: 0.33-2

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated libthread-pool-perl 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: Mon, 21 Dec 2015 23:55:57 +0200
Source: libthread-pool-perl
Binary: libthread-pool-perl
Architecture: source
Version: 0.33-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Description:
 libthread-pool-perl - group of threads for performing similar jobs
Closes: 799718
Changes:
 libthread-pool-perl (0.33-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ gregor herrmann ]
   * Rename autopkgtest configuration file(s) as per new pkg-perl-
 autopkgtest schema.
 .
   [ Niko Tyni ]
   * TODO out an undeterministically failing test. (Closes: #799718)
Checksums-Sha1:
 c053af6465e0e6d616d271652c37dce93482f1c6 2160 libthread-pool-perl_0.33-2.dsc
 9a19907d437b144d6d5fa1ad17b72d60dbfdadea 3128 
libthread-pool-perl_0.33-2.debian.tar.xz
Checksums-Sha256:
 09e7982de72227389759272ef485611a76375e769d7d025a3fa974a38dd3c877 2160 
libthread-pool-perl_0.33-2.dsc
 0c7d4521952163c787409593f82f1b4c74be0e21df8c2a94ed91e0bbdea56afd 3128 
libthread-pool-perl_0.33-2.debian.tar.xz
Files:
 9e8669d6d75d6c598eab66d38d2f4ae8 2160 perl optional 
libthread-pool-perl_0.33-2.dsc
 

Bug#806362: marked as done (python-django-bootstrap-form: FTBFS with Django 1.9)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 10:28:34 +
with message-id 
and subject line Bug#806362: fixed in python-django-bootstrap-form 3.1.0-6
has caused the Debian Bug report #806362,
regarding python-django-bootstrap-form: FTBFS with Django 1.9
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.)


-- 
806362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-bootstrap-form
Version: 3.1.0-5
Severity: important
User: python-dja...@packages.debian.org
Usertags: django19 django19-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest release candidate, I noticed that
python-django-bootstrap-form
FTBFS with 1.9~rc2.

Please update your package to work with Django 1.9 as I will uploading
it to unstable once it is released in early December 2015 (and at the
same time raising the severity of this bug to RC).

Typical issues include:

 * "django.utils.importlib" has been removed in favour of just
   "importlib"

 * Template builtins have been removed, removing
   "template.base.builtins", "django.template.base.add_to_builtins",
   etc. You can read more here:
   
https://chris-lamb.co.uk/posts/importerror-cannot-import-name-add_to_builtins-under-django-19

 * "django.forms.models.save_instance" has been removed:

   -
   
https://github.com/django/django/commit/8656cfc4e01332426e5e4b78c20a4e9ec443b293
   -
   
https://github.com/django/django/commit/b11564fd36587b1077bf7d77b62b7879cc08c382

 * "django.utils.unittest" has been removed in favour of just
   "unittest"


The full build log is attached.


Regards,

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


python-django-bootstrap-form_3.1.0-5_amd64.build.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-django-bootstrap-form
Source-Version: 3.1.0-6

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated 
python-django-bootstrap-form 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: Wed, 23 Dec 2015 09:48:16 +
Source: python-django-bootstrap-form
Binary: python-bootstrapform python3-bootstrapform python-bootstrapform-doc
Architecture: source all
Version: 3.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-bootstrapform - generate twitter-bootstrap form output for django form 
- Python 2
 python-bootstrapform-doc - generate twitter-bootstrap form output for django 
form - doc
 python3-bootstrapform - generate twitter-bootstrap form output for django form 
- Python 3
Closes: 806362
Changes:
 python-django-bootstrap-form (3.1.0-6) unstable; urgency=medium
 .
   * Switch from syncdb to migrate, which fixes FTBFS (Closes: #806362).
   * Watch file now using the PyPi redirector.
   * Standards-Version bumped to 3.9.6 (no change).
Checksums-Sha1:
 849ab366a38534069b732c6fd178d8c03da6ba38 2390 
python-django-bootstrap-form_3.1.0-6.dsc
 d2a0b494aae667e7688b391c57b05927530c3e51 4504 
python-django-bootstrap-form_3.1.0-6.debian.tar.xz
 508374a59299ec30cbbdd47b804db306c41bdcc9 43592 
python-bootstrapform-doc_3.1.0-6_all.deb
 ccdfe1116adb6a0b9c28a6582ff22a361febb4cf 5774 
python-bootstrapform_3.1.0-6_all.deb
 f3100786809a63249b4624367d08c99ff6839596 5798 
python3-bootstrapform_3.1.0-6_all.deb
Checksums-Sha256:
 bc65a884ee10b7c63fb83d2db4b34611ec318bbf0bad45741a15f614eb23c992 2390 
python-django-bootstrap-form_3.1.0-6.dsc
 3dbb785ca6a71382311933aaa1c73644504f17a3c9c7671fc19578acdd50501e 4504 
python-django-bootstrap-form_3.1.0-6.debian.tar.xz
 b22e9bec64cc131d5a48002383688e7628a3b3a3ba4c7bb25afbaa0b3b699fce 43592 
python-bootstrapform-doc_3.1.0-6_all.deb
 

Processed: bug 808665 is forwarded to https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=733, tagging 808665

[Debian Bug Tracking System]

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

> forwarded 808665 https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=733
Bug #808665 [src:ldns] ldns: FTBFS: ./install-sh: doc/man/man3/* does not exist.
Set Bug forwarded-to-address to 
'https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=733'.
> tags 808665 + upstream
Bug #808665 [src:ldns] ldns: FTBFS: ./install-sh: doc/man/man3/* does not exist.
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#808665: marked as done (ldns: FTBFS: ./install-sh: doc/man/man3/* does not exist.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2015 10:53:32 +
with message-id 
and subject line Bug#808665: fixed in ldns 1.6.17-7
has caused the Debian Bug report #808665,
regarding ldns: FTBFS: ./install-sh: doc/man/man3/* does not exist.
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.)


-- 
808665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldns
Version: 1.6.17-5
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

./install-sh  -m 755 -d /ldns-1.6.17/debian/tmp/usr/lib
./libtool --tag=CC --quiet --mode=install cp libldns.la 
/ldns-1.6.17/debian/tmp/usr/lib
libtool: install: warning: remember to run `libtool --finish /usr/lib'
./libtool --tag=CC --quiet --mode=finish /ldns-1.6.17/debian/tmp/usr/lib
./install-sh  -d /ldns-1.6.17/debian/tmp/usr/bin
./install-sh  -c -m 755 packaging/ldns-config /ldns-1.6.17/debian/tmp/usr/bin
./install-sh  -d /ldns-1.6.17/debian/tmp/usr/share/man/man1
./install-sh  -c -m 444 ./packaging/ldns-config.1 
/ldns-1.6.17/debian/tmp/usr/share/man/man1/
./install-sh  -d /ldns-1.6.17/debian/tmp/usr/share/man/man3
for f in doc/man/man3/*; do \
./install-sh  -c -m 444 $f /ldns-1.6.17/debian/tmp/usr/share/man/man3/; 
\
done
./install-sh: doc/man/man3/* does not exist.
Makefile:297: recipe for target 'install-manpages' failed
make[2]: *** [install-manpages] Error 1
make[2]: Leaving directory '/ldns-1.6.17'
dh_auto_install: make -j1 install DESTDIR=/ldns-1.6.17/debian/tmp 
AM_UPDATE_INFO_DIR=no DESTDIR=/ldns-1.6.17/debian/tmp returned exit code 2
debian/rules:72: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 2
make[1]: Leaving directory '/ldns-1.6.17'
debian/rules:18: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: debian/rules binary gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ldns.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: ldns
Source-Version: 1.6.17-7

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated ldns 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: Wed, 23 Dec 2015 11:05:32 +0100
Source: ldns
Binary: libldns1 libldns1-dbg libldns-dev ldnsutils python-ldns
Architecture: source amd64
Version: 1.6.17-7
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Ondřej Surý 
Description:
 ldnsutils  - ldns library for DNS programming
 libldns-dev - ldns library for DNS programming
 libldns1   - ldns library for DNS programming
 libldns1-dbg - ldns library for DNS programming (debug symbols)
 python-ldns - Python bindings for the ldns library for DNS programming
Closes: 808665
Changes:
 ldns (1.6.17-7) unstable; urgency=medium
 .
   * Add lintian overrides for slightly errorneous man pages
   * Disable ldns-config distribution; please use pkg-config
   * Add missing dh-python B-D
   * Fix perl error in doxyparse.pl (Closes: #808665)
Checksums-Sha1:
 4fccafe531078de5d68015256a0ec39b8844e462 2257 ldns_1.6.17-7.dsc
 9b39a67a1cc3cb95d90ae4be03c9c2441b9d2b62 14672 ldns_1.6.17-7.debian.tar.xz
 7e16acdb59630cbae56c7c3bd283e3ac549b0783 432260 
ldnsutils-dbgsym_1.6.17-7_amd64.deb
 c5b9b16d3247ce6fb460afe9d41057e3f4792c43 155646 ldnsutils_1.6.17-7_amd64.deb
 8105c21284047c34b8016c1d0f1950e5da4ac088 319950 libldns-dev_1.6.17-7_amd64.deb
 154e23bc3605529254ec3425dcbd3a817a02830a 381104 libldns1-dbg_1.6.17-7_amd64.deb
 3bec76cd6baad4c643a4b1d9da38cb06329c3a83 

Processed: severity of 799188 is serious

[Debian Bug Tracking System]

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

> severity 799188 serious
Bug #799188 [mdpress] mdpress: Fails to start: private method `render' called
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 807435 is serious

[Debian Bug Tracking System]

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

> severity 807435 serious
Bug #807435 [python3-pygit2] python3-pygit2: Fails to import because of 
PermissionError
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#808560: [buildd-tools-devel] Bug#808560: sbuild: Use of uninitialized value $_ in concatenation (.)

[Niko Tyni]

On Tue, Dec 22, 2015 at 09:00:20AM +0200, Niko Tyni wrote:
> On Tue, Dec 22, 2015 at 07:48:11AM +0100, Johannes Schauer wrote:

> > If the problem is this change of behaviour as you described it, then the 
> > fix is
> > a very simple one:
> 
> Cool, thanks! I'm not sure if there are other problems, this was the
> one I found first.

I can confirm that sbuild works fine for me again with your patch.

Please consider an upload soon, this is blocking the Perl 5.22
transition.

Thanks again,
-- 
Niko Tyni   nt...@debian.org

Processed: Upstream

[Debian Bug Tracking System]

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

> forwarded 808293 https://github.com/FreeRADIUS/freeradius-server/issues/1468
Bug #808293 [freeradius] freeradius stopped working after kernel upgrade
Set Bug forwarded-to-address to 
'https://github.com/FreeRADIUS/freeradius-server/issues/1468'.
> thanks
Stopping processing here.

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