Bug#846898: Fixed in 3.22.2-2

[David Weinehall]

On Tue, 6 Dec 2016 18:01:02 +0100 Raphael Hertzog 
wrote:
> Version: 3.22.2-2
>
> I just uploaded a new version of mutter with the fix for that
> bug. I was not aware of this bug so I forgot mention it in the
> changelog.

I'm seeing this issue (segfault in gnome-session) even with 3.22.2-2.

Bug#846770: gridengine: FTBFS: cc: error: libsched.a: No such file or directory

[Afif Elghraoui]

Control: tag -1 = confirmed

On الإثنين  5 كانون الأول 2016 01:09, Lucas Nussbaum wrote:
>> I have just tried a parallel build on an up-to-date unstable chroot on
>> > amd64 and it builds just fine for me. Can you confirm?
> No, it still fails for me.
>
> However, it build fine with DEB_BUILD_OPTIONS=parallel=1. So I suspected
> that it fails due to missing dependencies in some makefile.
>
> You can try with e.g. DEB_BUILD_OPTIONS=parallel=64 to see if you
> reproduce it.

I can reproduce it if I try 64 threads, but I've always built with 12
threads without any trouble. Here is the error, untangled from parallelism.

cc -o pdc -L. -Wl,-z,relro -rdynamic
-Wl,-rpath,\$ORIGIN/../../lib/lx-amd64  pdc_main.o procfs_main.o
libsched.a libsgeobj.a libcomm.a libcommlists.a libsgeobjd.a libcull.a
libuti.a libuti2.a  -luti -ldl -lmunge -lssl -lcrypto  -lm -lpthread
-ljemalloc -lmunge
cc: error: libsched.a: No such file or directory
../daemons/common/Makefile:94: recipe for target 'pdc' failed
make[2]: *** [pdc] Error 1

so yes, libsched.a needs to be declared as a prerequisite of pdc.

regards
Afif

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

Processed: Re: gridengine: FTBFS: cc: error: libsched.a: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 = confirmed
Bug #846770 [src:gridengine] gridengine: FTBFS: cc: error: libsched.a: No such 
file or directory
Added tag(s) confirmed; removed tag(s) unreproducible, sid, moreinfo, and 
stretch.

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

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

[Niko Tyni]

On Fri, Dec 09, 2016 at 11:39:58AM +1100, Tony Cook wrote:
> On Fri, Dec 09, 2016 at 01:01:01AM +0100, gregor herrmann wrote:
> > On Fri, 09 Dec 2016 01:14:23 +0200, Niko Tyni wrote:
> > 
> > > TL;dr: this is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176

> > > Unfortunately gcc doesn't seem to have a targeted option to disable this
> > > optimization. Building with -O0 on mips and mipsel is probably the best
> > > workaround we have (-O1 isn't enough.)

> > +# #847397
> > +DEB_HOST_ARCH = $(shell dpkg-architecture -qDEB_HOST_ARCH)
> > +NOOPT = mips mipsel amd64
> > +ifneq (,$(filter $(DEB_HOST_ARCH), $(NOOPT)))
> > +export DEB_CFLAGS_MAINT_STRIP:=-O2
> > +export DEB_CFLAGS_MAINT_APPEND:=-O0
> > +endif

> That certainly looks like a sensible workaround.

Looks good to me too.

> Is there some mechanism that will remove it if the gcc (or perhaps
> kernel) bug is fixed?

The only way I can think of is building and running a test case during
every build and setting the gcc flags based on that. But I suppose this
would give a false negative when building on 'real' 32-bit systems that
don't exhibit the problem, yielding binaries that fail on 64-bit systems.
And it feels overkill to me anyway.

We could leave a bug open about the disabled optimization and hope that
somebody will review the bugs at some point...
-- 
Niko

Processed: affects 847542

[Debian Bug Tracking System]

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

> affects 847542 gnome-shell gdm3
Bug #847542 [libmozjs-24-0] libmozjs-24-0 24.2.0-4 breaks gnome-shell, 
preventing gdm3 from starting
Added indication that 847542 affects gnome-shell and gdm3
> thanks
Stopping processing here.

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

Bug#847542: libmozjs-24-0 24.2.0-4 breaks gnome-shell, preventing gdm3 from starting

[Josh Triplett]

Package: libmozjs-24-0
Version: 24.2.0-4
Severity: grave

Control: affects -1 gnome-shell gdm3

libmozjs-24-0 24.2.0-4 causes the following failure in gnome-shell at
startup:

Dec 08 21:05:51 x gnome-shell[581]: JS ERROR: TypeError: imports.ui is undefined
Dec 08 21:05:51 x gnome-shell[581]: Execution of main.js threw exception: 
JS_EvaluateScript() failed
Dec 08 21:05:51 x gnome-session[483]: gnome-session-binary[483]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Dec 08 21:05:51 x gnome-session-binary[483]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Dec 08 21:05:51 x gnome-shell[634]: JS ERROR: TypeError: imports.ui is undefined
Dec 08 21:05:51 x gnome-shell[634]: Execution of main.js threw exception: 
JS_EvaluateScript() failed
Dec 08 21:05:51 x gnome-session-binary[483]: Unrecoverable failure in required 
component org.gnome.Shell.desktop
Dec 08 21:05:51 x gnome-session-binary[483]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Dec 08 21:05:51 x gnome-session[483]: gnome-session-binary[483]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Dec 08 21:05:51 x gnome-session[483]: gnome-session-binary[483]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
Dec 08 21:05:51 x gnome-session-binary[483]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
Dec 08 21:05:51 x gnome-session[483]: Unable to init server: Could not connect: 
Connection refused
Dec 08 21:05:51 x kernel: gnome-session-f[643]: segfault at 0 ip 
7f7eb997ea29 sp 7ffc78c0ce60 error 4 in 
libgtk-3.so.0.2200.4[7f7eb969c000+6f7000]

Downgrading to 24.2.0-3.1 fixes this problem.

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

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

Versions of packages libmozjs-24-0 depends on:
ii  libc6   2.24-8
ii  libffi6 3.2.1-6
ii  libgcc1 1:6.2.1-5
ii  libnspr42:4.12-6
ii  libstdc++6  6.2.1-5

libmozjs-24-0 recommends no packages.

libmozjs-24-0 suggests no packages.

-- no debconf information

Bug#846918: marked as done (interface opens, but no menus and no action on button clicks)

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 04:33:23 +
with message-id 
and subject line Bug#846918: fixed in jabref 3.6+ds-1
has caused the Debian Bug report #846918,
regarding interface opens, but no menus and no action on button clicks
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.)


-- 
846918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jabref
Version: 2.10+ds-7
Severity: grave

Hello!

Wow, so long time no filing bugs to Debian, seems like a whole new experience :)

Ok, here's the fact: opening a freshly installed jabref, the splash screen
starts fine, the interface opens and everything is visible, but as soon as I
click on _any_ menu item or button in the toolbar, nothing happens (except
stacktraces in console).

Here you are:

/--
| $ DEBUG_WRAPPER=1 jabref
| [debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-8-openjdk-amd64'
| [debug] /usr/bin/jabref: Found JAVA_CMD = 
'/usr/lib/jvm/java-8-openjdk-amd64/bin/java'
| [debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
| [debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-8-openjdk-amd64/bin/java  
-classpath 
/usr/share/java/jabref.jar:/usr/share/java/JPFCodeGenerator-rt.jar:/usr/share/java/antlr.jar:/usr/share/java/antlr3.jar:/usr/share/java/commons-logging.jar:/usr/share/java/glazedlists.jar:/usr/share/java/jempbox.jar:/usr/share/java/jgoodies-common.jar:/usr/share/java/jgoodies-forms.jar:/usr/share/java/jgoodies-looks.jar:/usr/share/java/jpf.jar:/usr/share/java/jpf-boot.jar:/usr/share/java/microba.jar:/usr/share/java/mysql-connector-java.jar:/usr/share/java/pdfbox.jar:/usr/share/java/postgresql.jar:/usr/share/java/spin.jar
 net.sf.jabref.JabRefMain
| Found 2 plugin(s):
|  - net.sf.jabref.export.misq 
(jar:file:/usr/share/jabref/JabRef-2.10.jar!/plugins/net.sf.jabref.export.misq/plugin.xml)
|  - net.sf.jabref.core 
(jar:file:/usr/share/jabref/JabRef-2.10.jar!/plugins/net.sf.jabref.core/plugin.xml)
| 
| Could not get key binding for "Open folder"
\-

So far, looks good.

As soon as I click a menu item:

---8<---
Exception in thread "AWT-EventQueue-0" java.lang.ExceptionInInitializerError
at com.jgoodies.looks.common.ShadowPopup.(ShadowPopup.java:84)
at com.jgoodies.looks.Options.isPopupDropShadowActive(Options.java:639)
at 
com.jgoodies.looks.common.ShadowPopupFactory.getPopup(ShadowPopupFactory.java:177)
at javax.swing.plaf.PopupMenuUI.getPopup(PopupMenuUI.java:61)
at javax.swing.JPopupMenu.showPopup(JPopupMenu.java:837)
at javax.swing.JPopupMenu.setVisible(JPopupMenu.java:790)
at javax.swing.JPopupMenu.show(JPopupMenu.java:965)
at javax.swing.JMenu.setPopupMenuVisible(JMenu.java:345)
at javax.swing.JPopupMenu.menuSelectionChanged(JPopupMenu.java:1478)
at 
javax.swing.MenuSelectionManager.setSelectedPath(MenuSelectionManager.java:125)
at javax.swing.plaf.basic.BasicMenuUI.appendPath(BasicMenuUI.java:222)
at javax.swing.plaf.basic.BasicMenuUI.access$200(BasicMenuUI.java:49)
at 
javax.swing.plaf.basic.BasicMenuUI$Handler.mousePressed(BasicMenuUI.java:461)
at 
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:279)
at java.awt.Component.processMouseEvent(Component.java:6530)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6298)
at java.awt.Container.processEvent(Container.java:2236)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Component.dispatchEvent(Component.java:4711)
at 
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4522)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
at java.awt.Container.dispatchEventImpl(Container.java:2280)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at 

Bug#839048: marked as done (couchjs crashes on ARM64)

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 03:03:43 +
with message-id 
and subject line Bug#839048: fixed in mozjs 1.8.5-1.0.0+dfsg-5.1
has caused the Debian Bug report #839048,
regarding couchjs crashes on ARM64
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.)


-- 
839048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmozjs185-1.0

root@3aeb83a7878f:~# cat a.js
print("hello")
root@3aeb83a7878f:~# couchjs a.js
Segmentation fault (core dumped)

couchjs is in couchdb-bin, but the issues is caused by a bug in mozjs.
There is an assumption that the VA bits is less equal than 47 bits in
mozjs. But it is not true any more when we compile the kernel with 48 VA
bits.

Patch is attached which should fix the problem.

Reference links :
1. upstream fix : https://bugzilla.mozilla.org/show_bug.cgi?id=1143022
2. redhat fix : https://bugzilla.redhat.com/show_bug.cgi?id=1242326

Note : Upstream patch limit the heap in the 47 bits world so that we won't
break the assumption. But the attached patch uses a different fix. It uses
less tag bits so that we can live with 48 VA bits. Because the old mozjs
may take JS objects from C code which is not allocated from JS heap.


Modify_tagged_pointer_structure_js1.8.5.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: mozjs
Source-Version: 1.8.5-1.0.0+dfsg-5.1

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

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
mozjs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Dec 2016 02:53:56 +0100
Source: mozjs
Binary: libmozjs185-1.0 libmozjs185-dev
Architecture: source amd64
Version: 1.8.5-1.0.0+dfsg-5.1
Distribution: sid
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: John Paul Adrian Glaubitz 
Description:
 libmozjs185-1.0 - SpiderMonkey JavaScript engine
 libmozjs185-dev - SpiderMonkey JavaScript library - development headers
Closes: 839048
Changes:
 mozjs (1.8.5-1.0.0+dfsg-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add Modify_tagged_pointer_structure_js1.8.5.patch to modify tagged
 pointer to use 48 bit virtual address space (Closes: #839048).
   * Add M68k-alignment-fixes.patch to enforce 32-bit alignment
 on m68k for some StackSegment, JSStackFrame and JSScript.
Checksums-Sha1:
 56833280bcb88fbf7de650c78740cfa3169d43f5 2127 mozjs_1.8.5-1.0.0+dfsg-5.1.dsc
 2c35f979f8ddcb401a243e410984947adec6e623 53464 
mozjs_1.8.5-1.0.0+dfsg-5.1.debian.tar.xz
 ffe116be874f3f44de13c2d45574fdaf092b28e4 84768 
libmozjs185-1.0-dbgsym_1.8.5-1.0.0+dfsg-5.1_amd64.deb
 272bf7de923d47d53b02b4d2575e6a8279f97978 1110242 
libmozjs185-1.0_1.8.5-1.0.0+dfsg-5.1_amd64.deb
 0da6ae099e2c6b812c95ce3ed5756fecda0e5185 1547808 
libmozjs185-dev_1.8.5-1.0.0+dfsg-5.1_amd64.deb
 624432300c8b9580ce5fa344df49e469de83b73f 6037 
mozjs_1.8.5-1.0.0+dfsg-5.1_amd64.buildinfo
Checksums-Sha256:
 96b214ca0f9d3087fde1076723ad8e2e06ad8bd7a85d6fae12d0f565f0c6a7ee 2127 
mozjs_1.8.5-1.0.0+dfsg-5.1.dsc
 c7fed45b2c8f2fb9348aa3bb3267a341c08682958e78e1963a37ec5b5b92d88e 53464 
mozjs_1.8.5-1.0.0+dfsg-5.1.debian.tar.xz
 5f33806b6d1717258a90a63feef48d34b70bb854e5761e7d5184dc15d7dc9353 84768 
libmozjs185-1.0-dbgsym_1.8.5-1.0.0+dfsg-5.1_amd64.deb
 433210d3a8dc8a257997d1d2963a72fd5511f9e6e66e759e1ae8d6f830c84666 1110242 
libmozjs185-1.0_1.8.5-1.0.0+dfsg-5.1_amd64.deb
 87d4f906f51357f425bcbe69fef4c98309e737c7959615885e4e9de5a84f5e78 1547808 
libmozjs185-dev_1.8.5-1.0.0+dfsg-5.1_amd64.deb
 0cb3c77b0dd7b9a574b92ea8ee80fb3cba2f9bda119d1bf2af6cc5beacddefd2 6037 
mozjs_1.8.5-1.0.0+dfsg-5.1_amd64.buildinfo
Files:
 25c8ae2c2a3911c35c3f05a47812f3c5 2127 libs extra mozjs_1.8.5-1.0.0+dfsg-5.1.dsc
 4329984f37dad4dd67f9b985efa1ac3a 53464 libs extra 
mozjs_1.8.5-1.0.0+dfsg-5.1.debian.tar.xz
 

Bug#844341: marked as done (moin: CVE-2016-7148: XSS in AttachFile view (multifile related))

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 01:33:37 +
with message-id 
and subject line Bug#844341: fixed in moin 1.9.9-1
has caused the Debian Bug report #844341,
regarding moin: CVE-2016-7148: XSS in AttachFile view (multifile related)
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.)


-- 
844341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moin
Version: 1.9.8-1
Severity: important
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for moin.

CVE-2016-7148[0]:
XSS in AttachFile view (multifile related)

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7148
[1] http://hg.moinmo.in/moin/1.9/rev/eceb70c41ecc

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: moin
Source-Version: 1.9.9-1

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated moin 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,  8 Dec 2016 22:13:08 +
Source: moin
Binary: python-moinmoin
Architecture: source all
Version: 1.9.9-1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 python-moinmoin - Python clone of WikiWiki - library
Closes: 794014 844338 844340 844341
Changes:
 moin (1.9.9-1) unstable; urgency=medium
 .
   * New upstream release, lots of bug fixes
   * Includes a few security updates:
 + CVE-2016-9119: XSS in GUI editor's link dialogue
   (Closes: #844338)
 + CVE-2016-7146: XSS in GUI editor's attachment dialogue
   (Closes:#844340)
 + CVE-2016-7148: XSS in AttachFile view (multifile related)
   (Closes: #844341)
   * Apply recommended patch from upstream: fix wrong digestmod of hmac.new
 calls
   * Update patches to fit upstream changes:
 + use_systemwide_libs.patch
 + mail-verification.patch
   * Add patch from Paul Wise to implement an incremental dump process in
 moin dump
   * Fix timestamps to make package build reproducibly. Thanks to Eduard
 Sanou for the patch. Closes: #794014
Checksums-Sha1:
 c5b52bbc46da4d278b4e992505ea00dac944c8d3 1851 moin_1.9.9-1.dsc
 d582126c443939cb09e650eeddd677ed7e8c3f99 37206341 moin_1.9.9.orig.tar.gz
 fe32d0193d51e5a7d46a10a7fc2dc6960162cdd0 151888 moin_1.9.9-1.debian.tar.xz
 36f5edd96dc9973173c31a4cf1b9be163891f6bf 5334 moin_1.9.9-1_amd64.buildinfo
 aa34148e565c69e16d8e3445c996a7741316bd57 7982778 
python-moinmoin_1.9.9-1_all.deb
Checksums-Sha256:
 c7da8347baee23ffec9b0a8fa94705aa4d0cfabf5bd9b06d53e07dff77ac938f 1851 
moin_1.9.9-1.dsc
 4397d7760b7ae324d7914ffeb1a9eeb15e09933b61468072acd3c3870351efa4 37206341 
moin_1.9.9.orig.tar.gz
 36ffe07570ace5c281d62e9d507265344a28159bf05e1c800261d9ad450cd76a 151888 
moin_1.9.9-1.debian.tar.xz
 3389ae6d68002699dbd00df498002d1d8e054fc9d2b55b1027547094c9a4cc2c 5334 
moin_1.9.9-1_amd64.buildinfo
 a94b14db49c274684ef4775edff82c2e4658e7946ee251565ae98c8eb1d6ded0 7982778 
python-moinmoin_1.9.9-1_all.deb
Files:
 dc3ec3f28992c14532b7f54c04af21df 1851 net optional moin_1.9.9-1.dsc
 32f02a5d0df06b80d889ca6cdc51593e 37206341 net optional moin_1.9.9.orig.tar.gz
 62a970dbcd97797d8a2320144b74f930 151888 net optional moin_1.9.9-1.debian.tar.xz
 10676e0532049269ef40da0a36369cf4 5334 net optional moin_1.9.9-1_amd64.buildinfo
 a747ee0d9e279a5e35e6f21557c23933 7982778 python optional 
python-moinmoin_1.9.9-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYSgRXAAoJEFh5eVc0QmhOCigP/1OCin2RmTpWLW/+exrnVruC
Xpu+X3RLxSl9b0qaRJRj992rwUWkS21tEMuLaxmaLcuUbOecC0nJljiVJ1ZpKykt

Bug#844338: marked as done (moin: CVE-2016-9119: XSS in GUI editor's link dialogue)

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 01:33:37 +
with message-id 
and subject line Bug#844338: fixed in moin 1.9.9-1
has caused the Debian Bug report #844338,
regarding moin: CVE-2016-9119: XSS in GUI editor's link dialogue
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.)


-- 
844338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moin
Version: 1.9.8-1
Severity: important
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for moin.

CVE-2016-9119[0]:
XSS in GUI editor's link dialogue

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9119
[1] http://hg.moinmo.in/moin/1.9/rev/3bddf075fdbd

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: moin
Source-Version: 1.9.9-1

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated moin 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,  8 Dec 2016 22:13:08 +
Source: moin
Binary: python-moinmoin
Architecture: source all
Version: 1.9.9-1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 python-moinmoin - Python clone of WikiWiki - library
Closes: 794014 844338 844340 844341
Changes:
 moin (1.9.9-1) unstable; urgency=medium
 .
   * New upstream release, lots of bug fixes
   * Includes a few security updates:
 + CVE-2016-9119: XSS in GUI editor's link dialogue
   (Closes: #844338)
 + CVE-2016-7146: XSS in GUI editor's attachment dialogue
   (Closes:#844340)
 + CVE-2016-7148: XSS in AttachFile view (multifile related)
   (Closes: #844341)
   * Apply recommended patch from upstream: fix wrong digestmod of hmac.new
 calls
   * Update patches to fit upstream changes:
 + use_systemwide_libs.patch
 + mail-verification.patch
   * Add patch from Paul Wise to implement an incremental dump process in
 moin dump
   * Fix timestamps to make package build reproducibly. Thanks to Eduard
 Sanou for the patch. Closes: #794014
Checksums-Sha1:
 c5b52bbc46da4d278b4e992505ea00dac944c8d3 1851 moin_1.9.9-1.dsc
 d582126c443939cb09e650eeddd677ed7e8c3f99 37206341 moin_1.9.9.orig.tar.gz
 fe32d0193d51e5a7d46a10a7fc2dc6960162cdd0 151888 moin_1.9.9-1.debian.tar.xz
 36f5edd96dc9973173c31a4cf1b9be163891f6bf 5334 moin_1.9.9-1_amd64.buildinfo
 aa34148e565c69e16d8e3445c996a7741316bd57 7982778 
python-moinmoin_1.9.9-1_all.deb
Checksums-Sha256:
 c7da8347baee23ffec9b0a8fa94705aa4d0cfabf5bd9b06d53e07dff77ac938f 1851 
moin_1.9.9-1.dsc
 4397d7760b7ae324d7914ffeb1a9eeb15e09933b61468072acd3c3870351efa4 37206341 
moin_1.9.9.orig.tar.gz
 36ffe07570ace5c281d62e9d507265344a28159bf05e1c800261d9ad450cd76a 151888 
moin_1.9.9-1.debian.tar.xz
 3389ae6d68002699dbd00df498002d1d8e054fc9d2b55b1027547094c9a4cc2c 5334 
moin_1.9.9-1_amd64.buildinfo
 a94b14db49c274684ef4775edff82c2e4658e7946ee251565ae98c8eb1d6ded0 7982778 
python-moinmoin_1.9.9-1_all.deb
Files:
 dc3ec3f28992c14532b7f54c04af21df 1851 net optional moin_1.9.9-1.dsc
 32f02a5d0df06b80d889ca6cdc51593e 37206341 net optional moin_1.9.9.orig.tar.gz
 62a970dbcd97797d8a2320144b74f930 151888 net optional moin_1.9.9-1.debian.tar.xz
 10676e0532049269ef40da0a36369cf4 5334 net optional moin_1.9.9-1_amd64.buildinfo
 a747ee0d9e279a5e35e6f21557c23933 7982778 python optional 
python-moinmoin_1.9.9-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYSgRXAAoJEFh5eVc0QmhOCigP/1OCin2RmTpWLW/+exrnVruC
Xpu+X3RLxSl9b0qaRJRj992rwUWkS21tEMuLaxmaLcuUbOecC0nJljiVJ1ZpKykt
kLyNmiYT/n+D4UywFhoc19CFPTF3scF0WKpvGVnSqw29GEQYK7xbi6WXyKKtgMUm

Bug#844340: marked as done (moin: CVE-2016-7146: XSS in GUI editor's attachment dialogue)

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 01:33:37 +
with message-id 
and subject line Bug#844340: fixed in moin 1.9.9-1
has caused the Debian Bug report #844340,
regarding moin: CVE-2016-7146: XSS in GUI editor's attachment dialogue
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.)


-- 
844340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moin
Version: 1.9.8-1
Severity: important
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for moin.

CVE-2016-7146[0]:
XSS in GUI editor's attachment dialogue

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7146
[1] http://hg.moinmo.in/moin/1.9/rev/1563d6db198c

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: moin
Source-Version: 1.9.9-1

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated moin 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,  8 Dec 2016 22:13:08 +
Source: moin
Binary: python-moinmoin
Architecture: source all
Version: 1.9.9-1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 python-moinmoin - Python clone of WikiWiki - library
Closes: 794014 844338 844340 844341
Changes:
 moin (1.9.9-1) unstable; urgency=medium
 .
   * New upstream release, lots of bug fixes
   * Includes a few security updates:
 + CVE-2016-9119: XSS in GUI editor's link dialogue
   (Closes: #844338)
 + CVE-2016-7146: XSS in GUI editor's attachment dialogue
   (Closes:#844340)
 + CVE-2016-7148: XSS in AttachFile view (multifile related)
   (Closes: #844341)
   * Apply recommended patch from upstream: fix wrong digestmod of hmac.new
 calls
   * Update patches to fit upstream changes:
 + use_systemwide_libs.patch
 + mail-verification.patch
   * Add patch from Paul Wise to implement an incremental dump process in
 moin dump
   * Fix timestamps to make package build reproducibly. Thanks to Eduard
 Sanou for the patch. Closes: #794014
Checksums-Sha1:
 c5b52bbc46da4d278b4e992505ea00dac944c8d3 1851 moin_1.9.9-1.dsc
 d582126c443939cb09e650eeddd677ed7e8c3f99 37206341 moin_1.9.9.orig.tar.gz
 fe32d0193d51e5a7d46a10a7fc2dc6960162cdd0 151888 moin_1.9.9-1.debian.tar.xz
 36f5edd96dc9973173c31a4cf1b9be163891f6bf 5334 moin_1.9.9-1_amd64.buildinfo
 aa34148e565c69e16d8e3445c996a7741316bd57 7982778 
python-moinmoin_1.9.9-1_all.deb
Checksums-Sha256:
 c7da8347baee23ffec9b0a8fa94705aa4d0cfabf5bd9b06d53e07dff77ac938f 1851 
moin_1.9.9-1.dsc
 4397d7760b7ae324d7914ffeb1a9eeb15e09933b61468072acd3c3870351efa4 37206341 
moin_1.9.9.orig.tar.gz
 36ffe07570ace5c281d62e9d507265344a28159bf05e1c800261d9ad450cd76a 151888 
moin_1.9.9-1.debian.tar.xz
 3389ae6d68002699dbd00df498002d1d8e054fc9d2b55b1027547094c9a4cc2c 5334 
moin_1.9.9-1_amd64.buildinfo
 a94b14db49c274684ef4775edff82c2e4658e7946ee251565ae98c8eb1d6ded0 7982778 
python-moinmoin_1.9.9-1_all.deb
Files:
 dc3ec3f28992c14532b7f54c04af21df 1851 net optional moin_1.9.9-1.dsc
 32f02a5d0df06b80d889ca6cdc51593e 37206341 net optional moin_1.9.9.orig.tar.gz
 62a970dbcd97797d8a2320144b74f930 151888 net optional moin_1.9.9-1.debian.tar.xz
 10676e0532049269ef40da0a36369cf4 5334 net optional moin_1.9.9-1_amd64.buildinfo
 a747ee0d9e279a5e35e6f21557c23933 7982778 python optional 
python-moinmoin_1.9.9-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYSgRXAAoJEFh5eVc0QmhOCigP/1OCin2RmTpWLW/+exrnVruC
Xpu+X3RLxSl9b0qaRJRj992rwUWkS21tEMuLaxmaLcuUbOecC0nJljiVJ1ZpKykt
kLyNmiYT/n+D4UywFhoc19CFPTF3scF0WKpvGVnSqw29GEQYK7xbi6WXyKKtgMUm

Bug#847527: FTBFS on mips*

[Michael Biebl]

Source: kwallet-kf5
Version: 5.28.0-2
Severity: serious

The package FTBFS on mips* with with the following error message

/usr/bin/c++   -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -Wall
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual
-Werror=return-type -pedantic -fexceptions  -Wl,--enable-new-dtags
-Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined
CMakeFiles/kwalletd5.dir/main.cpp.o
CMakeFiles/kwalletd5.dir/kbetterthankdialog.cpp.o
CMakeFiles/kwalletd5.dir/kwalletd.cpp.o
CMakeFiles/kwalletd5.dir/kwalletwizard.cpp.o
CMakeFiles/kwalletd5.dir/ktimeout.cpp.o
CMakeFiles/kwalletd5.dir/kwalletsessionstore.cpp.o
CMakeFiles/kwalletd5.dir/migrationagent.cpp.o
CMakeFiles/kwalletd5.dir/migrationwizard.cpp.o
CMakeFiles/kwalletd5.dir/knewwalletdialog.cpp.o
CMakeFiles/kwalletd5.dir/kwalletadaptor.cpp.o
CMakeFiles/kwalletd5.dir/kwallet4_interface.cpp.o
CMakeFiles/kwalletd5.dir/kwalletd5_automoc.cpp.o  -o kwalletd5
-Wl,-rpath,/«PKGBUILDDIR»/obj-mips-linux-gnu/src/runtime/kwalletd/backend:/«PKGBUILDDIR»/obj-mips-linux-gnu/src/api/KWallet:
-rdynamic backend/libkwalletbackend5.so.5.28.0
../../api/KWallet/libKF5Wallet.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5IconThemes.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5Service.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5DBusAddons.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5Notifications.so.5.28.0
/usr/lib/mips-linux-gnu/libgpgmepp.so -lpthread -lgpgme -lassuan
-L/usr/lib/mips-linux-gnu -lgpg-error -lgcrypt
/usr/lib/mips-linux-gnu/libKF5WindowSystem.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5ConfigWidgets.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5Codecs.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5ConfigGui.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5Auth.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5WidgetsAddons.so.5.28.0
/usr/lib/mips-linux-gnu/libQt5Widgets.so.5.7.1
/usr/lib/mips-linux-gnu/libQt5Gui.so.5.7.1
/usr/lib/mips-linux-gnu/libKF5I18n.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5CoreAddons.so.5.28.0
/usr/lib/mips-linux-gnu/libKF5ConfigCore.so.5.28.0
/usr/lib/mips-linux-gnu/libQt5DBus.so.5.7.1
/usr/lib/mips-linux-gnu/libQt5Xml.so.5.7.1
/usr/lib/mips-linux-gnu/libQt5Core.so.5.7.1 
CMakeFiles/kwalletd5.dir/kwalletd.cpp.o: In function
`KWalletD::keyDoesNotExist(QString const&, QString const&, QString
const&)':
./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cpp:1805:
undefined reference to `KWallet::Backend::entryDoesNotExist(QString
const&, QString const&) const'
./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cpp:1805:
undefined reference to `KWallet::Backend::entryDoesNotExist(QString
const&, QString const&) const'
./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cpp:1810:
undefined reference to `KWallet::Backend::entryDoesNotExist(QString
const&, QString const&) const'
./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cpp:1810:
undefined reference to `KWallet::Backend::entryDoesNotExist(QString
const&, QString const&) const'
collect2: error: ld returned 1 exit status


The full build logs are available at
https://buildd.debian.org/status/package.php?p=kwallet-kf5=unstable




-- 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.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#847526: stimfit FTBFS on architectures where char is unsigned.

[peter green]

Package: stimfit
Version: 0.15.3-1
Severity: serious
Tags: patch


From the armhf build log for the hdf5 binnmu

In file included from biosig4c++/t210/scp-decode.cpp:113:0:
biosig4c++/t210/codes.h:25:37: error: narrowing conversion of '-1' from 'int' 
to 'char' inside { } [-Wnarrowing]

arm64, armel, ppc64el, powerpc and ppc64 have the same problem.

I believe this was triggered by the move to gcc-6. At least on armhf the 
previous successful build was performed with gcc 5.


Adding an explicit typecast makes the package build. I took a quick look 
at the code to try to determine if this fix was correct but I was unable 
to determine what exactly the value in question was actually used for.


I uploaded the fix to raspbian and have attatched a debdiff.

No intent to NMU in debian.

diff -Nru stimfit-0.15.3/debian/changelog stimfit-0.15.3/debian/changelog
--- stimfit-0.15.3/debian/changelog 2016-07-14 10:12:45.0 +
+++ stimfit-0.15.3/debian/changelog 2016-12-09 00:34:10.0 +
@@ -1,3 +1,9 @@
+stimfit (0.15.3-1+rpi1) stretch-staging; urgency=medium
+
+  * Add typecast to fix build failure on architectures where char is unsigned..
+
+ -- Peter Michael Green   Fri, 09 Dec 2016 00:34:10 
+
+
 stimfit (0.15.3-1) unstable; urgency=low
 
   * Fix building with gcc-6 (Closes: #811904)
diff -Nru stimfit-0.15.3/debian/patches/fix-char-signedness.patch 
stimfit-0.15.3/debian/patches/fix-char-signedness.patch
--- stimfit-0.15.3/debian/patches/fix-char-signedness.patch 1970-01-01 
00:00:00.0 +
+++ stimfit-0.15.3/debian/patches/fix-char-signedness.patch 2016-12-09 
00:34:10.0 +
@@ -0,0 +1,14 @@
+Description: Add typecast to fix build failure on architectures where char is 
unsigned..
+Author: Peter Michael Green 
+
+--- stimfit-0.15.3.orig/src/libbiosiglite/biosig4c++/t210/codes.h
 stimfit-0.15.3/src/libbiosiglite/biosig4c++/t210/codes.h
+@@ -22,7 +22,7 @@ Foundation, Inc., 59 Temple Place - Suit
+ #ifndef __CODES_H__
+ #define __CODES_H__
+ 
+-static const char STR_END[]={-1,'\0'};
++static const char STR_END[]={(char)-1,'\0'};
+ static char STR_NULL[]=" unspecified/unknown ";
+ 
+ static alfabetic _special[]={
diff -Nru stimfit-0.15.3/debian/patches/series 
stimfit-0.15.3/debian/patches/series
--- stimfit-0.15.3/debian/patches/series1970-01-01 00:00:00.0 
+
+++ stimfit-0.15.3/debian/patches/series2016-12-09 00:34:10.0 
+
@@ -0,0 +1 @@
+fix-char-signedness.patch

Bug#839579: marked as done (auctex: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory))

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 00:48:24 +
with message-id 
and subject line Bug#839579: fixed in auctex 11.88-2
has caused the Debian Bug report #839579,
regarding auctex: FTBFS when built with dpkg-buildpackage -A (chmod: No such 
file or directory)
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.)


-- 
839579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:auctex
Version: 11.88-1.2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
/bin/bash: git: command not found
dh build-indep --exclude .eperl --with tex
   dh_testdir -i -O--exclude=.eperl
   dh_update_autotools_config -i -O--exclude=.eperl
   dh_auto_configure -i -O--exclude=.eperl
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libexecdir=\${prefix}/lib/auctex 
--disable-maintainer-mode --disable-dependency-tracking
checking for make... make
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for date in ChangeLog... 2014-11-01
checking for release in ChangeLog... not found, using 2014-11-01 instead
checking for date in ChangeLog... 2014-10-29

[... snipped ...]

config.status: creating Makefile
config.status: creating tex-site.el.out
config.status: creating preview/preview.el
config.status: creating doc/Makefile
config.status: creating auctex.el
=== configuring in preview (/<>/preview)
configure: running /bin/bash ./configure --disable-option-checking 
'--prefix=/usr'  '--build=x86_64-linux-gnu' '--includedir=${prefix}/include' 
'--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' 
'--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' 
'--libexecdir=${prefix}/lib/auctex' '--disable-maintainer-mode' 
'--disable-dependency-tracking' 'build_alias=x86_64-linux-gnu' 
--cache-file=/dev/null --srcdir=.
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for /usr/bin/emacs... /usr/bin/emacs
checking if /usr/bin/emacs is XEmacs... no
checking for Emacs prefix... "/usr"
checking if Emacs is recent enough... yes
checking if build directory is valid... yes
checking where lisp files go... ${datadir}/emacs/site-lisp
checking what file to use for preview startup... 
${datadir}/emacs/site-lisp/preview-latex.el
checking where the package lisp files go... ${datadir}/emacs/site-lisp/auctex
checking where the data files go... ${datadir}/emacs/site-lisp/auctex
checking for the location of AUCTeX's tex-site.el... ..
checking for gs... gs
checking for latex... /usr/bin/latex
checking for pdflatex... /usr/bin/pdflatex
checking for tex... /usr/bin/tex
checking for prefix from kpsepath... "/usr"
checking for TDS-compliant directory... ${datadir}/texmf
Preview will be placed in ${datadir}/texmf/tex/latex/preview
Preview docs will be placed in ${datadir}/texmf/doc/latex/styles
checking for texhash... /usr/bin/texhash
checking for initexmf... /usr/bin/texhash
checking for glaring installation conflicts... probably none
configure: creating ./config.status
config.status: creating Makefile
config.status: creating auto.el
config.status: creating latex/Makefile

Congratulations!  Configuration of preview is complete.


Congratulations!  Configuration of AUCTeX is complete.

Type "make" at the prompt to build.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/bin/bash: git: command not found
chmod a+x debian/elcc
chmod: cannot access 'debian/elcc': No such file or directory
debian/rules:43: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:52: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

Please note that there is both a "build" target and an
"override_dh_auto_build" target, but there are not build-arch or
build-indep targets.

This is not very 

Bug#845147: marked as done (golang-github-appc-docker2aci FTBFS on i386 and arm*: error calling MarshalJSON for type types.Labels: bad arch)

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 11:44:54 +1100
with message-id <2649325.jjaRQV9Ky6@deblab>
and subject line Done: golang-github-appc-docker2aci FTBFS on i386 and arm*: 
error calling MarshalJSON for type types.Labels: bad arch
has caused the Debian Bug report #845147,
regarding golang-github-appc-docker2aci FTBFS on i386 and arm*: error calling 
MarshalJSON for type types.Labels: bad arch
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.)


-- 
845147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-appc-docker2aci
Version: 0.14.0+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=golang-github-appc-docker2aci

...
--- FAIL: TestFetchingMultipleLayersV22 (0.00s)
server.go:16: path requested: /v2/
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/manifests/v0.1.0
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/blobs/sha256:06ed250f2530f71b93917021a4ab8ad00dc794cdb3d38624ccc76cb396bc797d
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/blobs/sha256:228b9a6eb6a46656e31afc554598f366258faed297af6ee9bc1a3837f602e6e4
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/blobs/sha256:d55b253d87d1338c84d70093dddafdd4761c36e49389fef217e5557d8b16bce8
v22_test.go:354: error generating ACI: error writing manifest: json: 
error calling MarshalJSON for type schema.ImageManifest: json: error calling 
MarshalJSON for type types.Labels: bad arch "386" for linux (must be one of: 
[amd64 i386 aarch64 aarch64_be armv6l armv7l armv7b ppc64 ppc64le s390x])
FAIL
exit status 1
FAILgithub.com/appc/docker2aci/lib/tests0.033s
?   github.com/appc/docker2aci/pkg/log  [no test files]
dh_auto_test: go test -v -p 1 github.com/appc/docker2aci 
github.com/appc/docker2aci/lib github.com/appc/docker2aci/lib/common 
github.com/appc/docker2aci/lib/internal 
github.com/appc/docker2aci/lib/internal/backend/file 
github.com/appc/docker2aci/lib/internal/backend/repository 
github.com/appc/docker2aci/lib/internal/docker 
github.com/appc/docker2aci/lib/internal/tarball 
github.com/appc/docker2aci/lib/internal/types 
github.com/appc/docker2aci/lib/internal/typesV2 
github.com/appc/docker2aci/lib/internal/util 
github.com/appc/docker2aci/lib/tests github.com/appc/docker2aci/pkg/log 
returned exit code 1
debian/rules:4: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Package: src:golang-github-appc-docker2aci
Version: 0.14.0+dfsg-2

Builds successfully.

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

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B


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

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

[Tony Cook]

On Fri, Dec 09, 2016 at 01:01:01AM +0100, gregor herrmann wrote:
> On Fri, 09 Dec 2016 01:14:23 +0200, Niko Tyni wrote:
> 
> > TL;dr: this is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176
> 
> Oh.
>  
> > > > Otherwise a backtrace for a -g build from the crash would be handy:
> > > >   perl Makefile.PL OPTIMIZE=-g
> > It goes away without the default optimization level -O2.
> > 
> > On eller.debian.org, mipsel chroot, with OPTIMIZE="-g -O2":
> [..]
> 
> I think a want to book a workshop "gdb for harmless perl packagers"
> :)
>  
> > Unfortunately gcc doesn't seem to have a targeted option to disable this
> > optimization. Building with -O0 on mips and mipsel is probably the best
> > workaround we have (-O1 isn't enough.)
> 
> I now cam up with the following change to d/rules:
> 
> +# #847397
> +DEB_HOST_ARCH = $(shell dpkg-architecture -qDEB_HOST_ARCH)
> +NOOPT = mips mipsel amd64
> +ifneq (,$(filter $(DEB_HOST_ARCH), $(NOOPT)))
> +export DEB_CFLAGS_MAINT_STRIP:=-O2
> +export DEB_CFLAGS_MAINT_APPEND:=-O0
> +endif
> 
> (committed and pushed). Does this make sense (if I remove the
> debugging amd64 again, or course)?
> 

That certainly looks like a sensible workaround.

Is there some mechanism that will remove it if the gcc (or perhaps
kernel) bug is fixed?

Tony

Bug#846921: marked as done (spring: FTBFS on i386: relocation R_386_GOTOFF against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when making a shared object)

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 00:34:31 +
with message-id 
and subject line Bug#846921: fixed in spring 103.0+dfsg-2
has caused the Debian Bug report #846921,
regarding spring: FTBFS on i386: relocation R_386_GOTOFF against preemptible 
symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when making a shared object
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.)


-- 
846921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spring
Version: 103.0+dfsg-1
Severity: serious

Your package failed to build on i386:

/usr/bin/c++  -fPIC -g -O2 -fdebug-prefix-map=/«BUILDDIR»/spring-103.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fuse-ld=gold  -std=gnu++11 -fdiagnostics-color=always 
-march=i686 -msse -mfpmath=sse -mno-sse2 -mno-sse3 -mno-ssse3 -mno-sse4.1 
-mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx -mno-fma -mno-fma4 -mno-xop -mno-lwp 
-mno-avx2 -fsingle-precision-constant -frounding-math -mieee-fp -pipe 
-fno-strict-aliasing  -fvisibility=hidden  -fvisibility-inlines-hidden -pthread 
 -O2  -Wformat -Wformat-security -DNDEBUG -g -Wl,-z,relro -shared  -o 
libSkirmishAI.so CMakeFiles/RAI.dir/AIExport.cpp.o 
CMakeFiles/RAI.dir/Builder.cpp.o CMakeFiles/RAI.dir/BuilderPlacement.cpp.o 
CMakeFiles/RAI.dir/CombatManager.cpp.o CMakeFiles/RAI.dir/GResourceMap.cpp.o 
CMakeFiles/RAI.dir/GTerrainMap.cpp.o CMakeFiles/RAI.dir/LogFile.cpp.o 
CMakeFiles/RAI.dir/PowerManager.cpp.o CMakeFiles/RAI.dir/RAI.cpp.o 
CMakeFiles/RAI.dir/SWeaponManager.cpp.o CMakeFiles/RAI.dir/UnitDefHandler.cpp.o 
CMakeFiles/RAI.dir/UnitManager.cpp.o ../../Wrappers/LegacyCpp/libLegacyCpp.a 
../../Wrappers/CUtils/libCUtils.a 
[ 16%] Building CXX object 
AI/Wrappers/Cpp/CMakeFiles/Cpp-AIWrapper.dir/src-generated/WrappFile.cpp.o
cd /«BUILDDIR»/spring-103.0+dfsg/obj-i686-linux-gnu/AI/Wrappers/Cpp && 
/usr/bin/c++   -DBOOST_NO_FENV_H -DBUILDING_AI 
-DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSYNCCHECK 
-DTHREADPOOL -DUSE_LIBSQUISH -D_GLIBCXX_USE_NANOSLEEP -D_GNU_SOURCE=1 
-D_RANDOM_TCC -D_REENTRANT -I/«BUILDDIR»/spring-103.0+dfsg/rts 
-I/«BUILDDIR»/spring-103.0+dfsg/obj-i686-linux-gnu/src-generated/engine 
-I/«BUILDDIR»/spring-103.0+dfsg/rts/ExternalAI/Interface 
-I/«BUILDDIR»/spring-103.0+dfsg/AI/Wrappers 
-I/«BUILDDIR»/spring-103.0+dfsg/AI/Wrappers/Cpp/src 
-I/«BUILDDIR»/spring-103.0+dfsg/obj-i686-linux-gnu/AI/Wrappers/Cpp/src-generated
  -g -O2 -fdebug-prefix-map=/«BUILDDIR»/spring-103.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fuse-ld=gold  -std=gnu++11 -fdiagnostics-color=always 
-march=i686 -msse -mfpmath=sse -mno-sse2 -mno-sse3 -mno-ssse3 -mno-sse4.1 
-mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx -mno-fma -mno-fma4 -mno-xop -mno-lwp 
-mno-avx2 -fsingle-precision-constant -frounding-math -mieee-fp -pipe 
-fno-strict-aliasing  -fvisibility=hidden  -fvisibility-inlines-hidden -pthread 
 -O2  -Wformat -Wformat-security -DNDEBUG -g   -o 
CMakeFiles/Cpp-AIWrapper.dir/src-generated/WrappFile.cpp.o -c 
/«BUILDDIR»/spring-103.0+dfsg/obj-i686-linux-gnu/AI/Wrappers/Cpp/src-generated/WrappFile.cpp
/usr/bin/ld.gold: error: 
../../Wrappers/LegacyCpp/libLegacyCpp.a(AIAICallback.cpp.o): relocation 
R_386_GOTOFF against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used 
when making a shared object
/usr/bin/ld.gold: error: 
../../Wrappers/LegacyCpp/libLegacyCpp.a(AIAICallback.cpp.o): relocation 
R_386_GOTOFF against preemptible symbol _ZNSt6vectorItSaItEED1Ev cannot be used 
when making a shared object
/usr/bin/ld.gold: error: 
../../Wrappers/LegacyCpp/libLegacyCpp.a(AIAICallback.cpp.o): relocation 
R_386_GOTOFF against preemptible symbol _ZNSt6vectorIhSaIhEED1Ev cannot be used 
when making a shared object
collect2: error: ld returned 1 exit status

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

Emilio

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: spring
Source-Version: 103.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
spring, which is due 

Bug#831107: marked as done (stimfit: FTBFS with GCC 6: ./gui/doc.cpp:1269:27: error: no matching function for call to 'transform(std::vector::const_iterator, std::vector::const_iterato

[Debian Bug Tracking System]

Your message dated Fri, 09 Dec 2016 00:21:47 +
with message-id <5849f91b.9040...@p10link.net>
and subject line Re: Bug#831107: stimfit: FTBFS with GCC 6: 
./gui/doc.cpp:1269:27: error: no matching function for call to 
'transform(std::vector::const_iterator, 
std::vector::const_iterator, std::vector::iterator, )'
has caused the Debian Bug report #831107,
regarding stimfit: FTBFS with GCC 6: ./gui/doc.cpp:1269:27: error: no matching 
function for call to 'transform(std::vector::const_iterator, 
std::vector::const_iterator, std::vector::iterator, )'
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.)


-- 
831107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stimfit
Version: 0.15.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[4]: Entering directory '/«PKGBUILDDIR»/src/stimfit'
>   CXX  libstimfit_la-stf.lo
>   CXX  libstimfit_la-app.lo
> ./gui/app.cpp:1419:30: warning: macro "__DATE__" might prevent reproducible 
> builds [-Wdate-time]
>  verString << wxT(__DATE__) << wxT(", ") << wxT(__TIME__);
>   ^
> ./gui/app.cpp:1419:60: warning: macro "__TIME__" might prevent reproducible 
> builds [-Wdate-time]
>  verString << wxT(__DATE__) << wxT(", ") << wxT(__TIME__);
> ^
>   CXX  libstimfit_la-unopt.lo
>   CXX  libstimfit_la-doc.lo
> In file included from ./gui/././../../libstfio/stfio.h:66:0,
>  from ./gui/././../stf.h:71,
>  from ./gui/./app.h:176,
>  from ./gui/doc.cpp:35:
> ./gui/././../../libstfio/./recording.h: In copy constructor 
> 'Recording::Recording(const Recording&)':
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:17: note: declared here
>  std::string time0, date; 
>  ^
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:17: note: declared here
>  std::string time0, date; 
>  ^
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:17: note: declared here
>  std::string time0, date; 
>  ^
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:17: note: declared here
>  std::string time0, date; 
>  ^
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:24: note: declared here
>  std::string time0, date; 
> ^~~~
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:24: note: declared here
>  std::string time0, date; 
> ^~~~
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> ./gui/././../../libstfio/./recording.h:378:24: note: declared here
>  std::string time0, date; 
> ^~~~
> ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> deprecated [-Wdeprecated-declarations]
>  class StfioDll Recording {
> ^
> 

Processed: Pending fixes for bugs in the libimager-perl package

[Debian Bug Tracking System]

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

> tag 847397 + pending
Bug #847397 [src:libimager-perl] libimager-perl FTBFS on mips/mipsel: Failed 
10/66 test programs
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#847397: Pending fixes for bugs in the libimager-perl package

[pkg-perl-maintainers]

tag 847397 + pending
thanks

Some bugs in the libimager-perl package are closed in revision
0d8d69fb6c8dcc6086121c0346b73456f9887e3f in branch 'master' by gregor
herrmann

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

Commit message:

Build with -O0 on mips and mipsel.

Closes: #847397

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

[gregor herrmann]

On Fri, 09 Dec 2016 01:14:23 +0200, Niko Tyni wrote:

> TL;dr: this is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176

Oh.
 
> > > Otherwise a backtrace for a -g build from the crash would be handy:
> > >   perl Makefile.PL OPTIMIZE=-g
> It goes away without the default optimization level -O2.
> 
> On eller.debian.org, mipsel chroot, with OPTIMIZE="-g -O2":
[..]

I think a want to book a workshop "gdb for harmless perl packagers"
:)
 
> Unfortunately gcc doesn't seem to have a targeted option to disable this
> optimization. Building with -O0 on mips and mipsel is probably the best
> workaround we have (-O1 isn't enough.)

I now cam up with the following change to d/rules:

+# #847397
+DEB_HOST_ARCH = $(shell dpkg-architecture -qDEB_HOST_ARCH)
+NOOPT = mips mipsel amd64
+ifneq (,$(filter $(DEB_HOST_ARCH), $(NOOPT)))
+export DEB_CFLAGS_MAINT_STRIP:=-O2
+export DEB_CFLAGS_MAINT_APPEND:=-O0
+endif

(committed and pushed). Does this make sense (if I remove the
debugging amd64 again, or course)?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Bessie Tucker: Fryin' pan skillet blues


signature.asc
Description: Digital Signature

Bug#846782: Re: Bug#846144: gobject-introspection randomly hangs liferea build

[Emilio Pozuelo Monfort]

On 08/12/16 20:27, Paul Gevers wrote:
> Hi
> 
> On 08-12-16 00:18, Emilio Pozuelo Monfort wrote:
>> It would be good to get a backtrace of the hanging process.
> 
> If somebody can tell me how to backtrace a hanging process, I am more
> than willing to generate it. I have now so often seen the hang while
> working on this issue, I would be happy to make progress in such a way.

Just attach to it with gdb when it is hanged, then get the backtrace.

Cheers,
Emilio

Processed: your mail

[Debian Bug Tracking System]

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

> tags 818821 + patch
Bug #818821 [xview] xview: FTBFS with libc 2.23: #error "The GNU C Library no 
longer implements 
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#818821: Fixes for xview build failures on stretch

[Benjamin Moody]

Here are patches to fix these issues.

First, the use of regexp.h as noted by the submitter.

Second, the use of 'union wait' which is apparently also unsupported
by the glibc in stretch.

Third, the manpage preprocessing error.  This is not actually a build
failure (which is presumably a bug in imake.)  And of course, using
'cpp' to preprocess man pages seems like an even worse idea than using
it to preprocess Makefiles.  But, just in case it'll make somebody
happy, here's a patch to fix that issue.
Description: Use POSIX regular expression API in olvwm.
 Do not use the regexp.h functions, which are not available in current
 glibc.

--- xview-3.2p1.4.orig/clients/olvwm-4.1/virtual.c
+++ xview-3.2p1.4/clients/olvwm-4.1/virtual.c
@@ -58,9 +58,19 @@ static regexp_err(int val);
 #define TRUE 1
 #define FALSE 0
 
+#if 1
+#include 
+#define POSIX_REGEXP
+#else
 #include 
+#endif
+
 #ifdef REGEXP
 regexp *expbuf;
+#elif defined(POSIX_REGEXP)
+static regex_t expbuf;
+#else
+static char expbuf[256];
 #endif
 
 #ifdef IDENT
@@ -2146,14 +2156,14 @@ int val;
 }
 }
 
-static char expbuf[256];
-
 static
 rexMatch(string)
 char *string;
 {
 #ifdef REGEXP
 return regexec(expbuf, string);
+#elif defined(POSIX_REGEXP)
+return !regexec(, string, 0, NULL, 0);
 #else
 return step(string,expbuf);
 #endif
@@ -2191,6 +2201,8 @@ char newPattern[256];
 newPattern[j++] = '\0';
 #ifdef REGEXP
 expbuf = regcomp(newPattern);
+#elif defined(POSIX_REGEXP)
+regcomp(, newPattern, 0);
 #else
 #if defined(__linux__) && defined(__GLIBC__)
 /* See comment above.
Description: Use SysV/POSIX APIs/types in place of some old BSD ones.
 Notably, current glibc doesn't support 'union wait'.

--- xview-3.2p1.4.orig/clients/olvwm-4.1/olwm.c
+++ xview-3.2p1.4/clients/olvwm-4.1/olwm.c
@@ -708,7 +708,7 @@ handleChildSignal()
 void
 ReapChildren()
 {
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 pid_t pid;
 int status;
 #else
@@ -720,7 +720,7 @@ ReapChildren()
 	if (!deadChildren)
 		return;
 
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 	sighold(SIGCHLD);
 #else
 	oldmask = sigblock(sigmask(SIGCHLD));
@@ -730,7 +730,7 @@ ReapChildren()
 
 	while (1) {
 
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 pid = waitpid(-1, , WNOHANG);
 #else
 pid = wait3(, WNOHANG, (struct rusage *)0);
@@ -757,7 +757,7 @@ ReapChildren()
 
 	deadChildren = False;
 
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 	sigrelse(SIGCHLD);
 #else
 (void) sigsetmask(oldmask);
--- xview-3.2p1.4.orig/clients/olwm/olwm.c
+++ xview-3.2p1.4/clients/olwm/olwm.c
@@ -634,7 +634,7 @@ handleChildSignal()
 void
 ReapChildren()
 {
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 pid_t pid;
 int status;
 #else
@@ -645,7 +645,7 @@ ReapChildren()
 
 	if (!deadChildren)
 		return;
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 	sighold(SIGCHLD);
 #else
 	oldmask = sigblock(sigmask(SIGCHLD));
@@ -655,7 +655,7 @@ ReapChildren()
 
 	while (1) {
 
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 pid = waitpid(-1, , WNOHANG);
 #else
 pid = wait3(, WNOHANG, (struct rusage *)0);
@@ -682,7 +682,7 @@ ReapChildren()
 
 	deadChildren = False;
 
-#ifdef SYSV
+#if defined(SYSV) || defined(__linux__)
 	sigrelse(SIGCHLD);
 #else
 (void) sigsetmask(oldmask);
--- xview-3.2p1.4.orig/contrib/examples/notifier/ntfy_pipe.c
+++ xview-3.2p1.4/contrib/examples/notifier/ntfy_pipe.c
@@ -161,7 +161,7 @@ Notify_value
 sigchldcatcher(client, pid, status, rusage)
 Notify_client client; /* the client noted in main() */
 int pid; /* the pid that died */
-#ifdef SVR4
+#ifdef SYSV_WAIT
 int *status;
 #else
 union wait *status; /* the status of the process (unused here) */
@@ -169,7 +169,7 @@ union wait *status; /* the status of the
 struct rusage *rusage; /* resources used by this process (unused) */
 {
 if (WIFEXITED(*status)) {
-#ifdef SVR4
+#ifdef SYSV_WAIT
 printf("Process termined with status %d\n", *status);
 #else
 printf("Process termined with status %d\n", status->w_retcode);
--- xview-3.2p1.4.orig/lib/libxview/base/base.h
+++ xview-3.2p1.4/lib/libxview/base/base.h
@@ -63,6 +63,7 @@
 #define XV_OS_SVR4
 #undef XV_USE_TTCOMPAT
 #define SYSV_UCONTEXT 
+#define SYSV_WAIT
 #define XV_USE_XVFCNTL 
 #endif
  
--- xview-3.2p1.4.orig/lib/libxview/misc/expandname.c
+++ xview-3.2p1.4/lib/libxview/misc/expandname.c
@@ -121,11 +121,11 @@ xv_expand_name(name)
 	length += status;
 }
 (void) close(pivec[0]);
-#ifndef SVR4
+#ifndef SYSV_WAIT
 while (wait((union wait *) & status) != pid);
-#else /* SVR4 */
+#else /* SYSV_WAIT */
 while (wait( & status) != pid);
-#endif /* SVR4 */
+#endif /* SYSV_WAIT */
 ;
 status &= 0377;
 if (status != 0 && status != SIGPIPE) {
--- xview-3.2p1.4.orig/lib/libxview/notify/ndisd_wait.c
+++ xview-3.2p1.4/lib/libxview/notify/ndisd_wait.c
@@ -22,11 +22,11 @@ extern

Bug#846706: marked as done (network-manager-openconnect: FTBFS: configure: error: Package requirements (openconnect >= 3.02) were not met)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 23:18:59 +
with message-id 
and subject line Bug#846706: fixed in openconnect 7.07-2
has caused the Debian Bug report #846706,
regarding network-manager-openconnect: FTBFS: configure: error: Package 
requirements (openconnect >= 3.02) were not met
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.)


-- 
846706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-openconnect
Version: 1.2.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> checking for GLIB... yes
> checking for LIBXML... yes
> checking for GTK... yes
> checking for LIBSECRET... yes
> checking for OPENCONNECT... no
> configure: error: Package requirements (openconnect >= 3.02) were not met
> 
> Package 'liblz4', required by 'openconnect', not found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables OPENCONNECT_CFLAGS
> and OPENCONNECT_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>   "tail -v -n +0 config.log"

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/network-manager-openconnect_1.2.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: openconnect
Source-Version: 7.07-2

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

Debian distribution maintenance software
pp.
Mike Miller  (supplier of updated openconnect 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, 08 Dec 2016 15:05:19 -0800
Source: openconnect
Binary: openconnect openconnect-dbg libopenconnect-dev libopenconnect5 
libopenconnect5-dbg
Architecture: source
Version: 7.07-2
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Mike Miller 
Description:
 libopenconnect-dev - open client for Cisco AnyConnect VPN - development files
 libopenconnect5 - open client for Cisco AnyConnect VPN - shared library
 libopenconnect5-dbg - debugging symbols for the libopenconnect5 shared library
 openconnect - open client for Cisco AnyConnect VPN
 openconnect-dbg - debugging symbols for the OpenConnect VPN client
Closes: 846706
Changes:
 openconnect (7.07-2) unstable; urgency=medium
 .
   * d/rules: Build with --as-needed to remove indirect lib dependencies
   * d/control: Add Depends: liblz4-dev for libopenconnect-dev (Closes: 846706)
   * d/control: Use canonical repository URL for Vcs-Browser
   * d/copyright: Refresh copyright information
   * d/copyright: Update Format using "cme fix dpkg-copyright"
Checksums-Sha1:
 9d295d6ae673f4fbd3775e69eb9283b3570a4375 2334 openconnect_7.07-2.dsc
 cda2eb5d55e73b5a150cf5354833cd01edb56865 174484 
openconnect_7.07-2.debian.tar.xz
Checksums-Sha256:
 b61edfed36f434867d87ef4306ac7615edb9ad379a56f43adb0a132b749d3a55 2334 
openconnect_7.07-2.dsc
 6734569071fb51083afb075a9d9db78cac966867e09314093d0b4df30bf51f98 174484 
openconnect_7.07-2.debian.tar.xz
Files:
 569137eda4aaabe6844dd5fed07da150 2334 net optional openconnect_7.07-2.dsc
 5873f0f6ac89badd5e6de8c09d600702 174484 net optional 
openconnect_7.07-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEkwdQA1oV4nw4MHQHKPqAGkO91jcFAlhJ6RcUHG10bWlsbGVy

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

[Niko Tyni]

TL;dr: this is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176

On Thu, Dec 08, 2016 at 08:07:23PM +0100, gregor herrmann wrote:
> On Thu, 08 Dec 2016 09:11:51 +1100, Tony Cook wrote:
> 
> > > https://buildd.debian.org/status/package.php?p=libimager-perl=sid
> > > 
> > > ...
> > > Test Summary Report
> > > ---
> > > t/150-type/030-double.t   (Wstat: 10 Tests: 16 Failed: 0)
> > >   Non-zero wait status: 10
> > >   Parse errors: Bad plan.  You planned 136 tests but ran 16.
> > 
> > This looks like an unaligned access from the tests that failed,
> > probably in imgdouble.c.
> > 
> > Would it be possible to get access to this (or similar) hardware to
> > debug on?
> 
> Difficult :/

There's https://dsa.debian.org/doc/guest-account/ FWIW. But yes,
rather onerous.

> > Otherwise a backtrace for a -g build from the crash would be handy:
> > 
> >   perl Makefile.PL OPTIMIZE=-g

It goes away without the default optimization level -O2.

On eller.debian.org, mipsel chroot, with OPTIMIZE="-g -O2":

  ok 14 -  - got right color (99, 0)
  ok 15 -  - got right color (0, 100)
  ok 16 -  - got right color (99, 100)
  
  Program received signal SIGBUS, Bus error.
  0x77cc099c in i_glinf_ddoub (im=0x55774788, l=, r=, y=, 
  vals=0x5577d0b0) at imgdouble.c:280
  280 vals[i].channel[ch] = ((double *)im->idata)[off];
  (gdb) bt
  #0  0x77cc099c in i_glinf_ddoub (im=0x55774788, l=, 
r=, y=, 
  vals=0x5577d0b0) at imgdouble.c:280
  #1  0x77c68678 in XS_Imager_i_glinf (my_perl=0x5575d008, cv=) 
at Imager.xs:3771
  #2  0x55636f30 in Perl_pp_entersub (my_perl=0x5575d008) at pp_hot.c:3987
  #3  0x5562db20 in Perl_runops_standard (my_perl=0x5575d008) at run.c:41
  #4  0x5559c92c in S_run_body (oldscope=1, my_perl=0x5575d008) at perl.c:2488
  #5  perl_run (my_perl=0x5575d008) at perl.c:2411
  #6  0x5556cce0 in main (argc=, argv=, 
env=) at perlmain.c:116
  (gdb) p i 
  $1 = 0
  (gdb) p ch
  $2 = 1
  (gdb) p off
  $3 = 0
  
Everything looks 8-byte aligned to me:
  
  (gdb) p &(vals[i].channel[ch])
  $4 = (i_fsample_t *) 0x5577d0b8

  (gdb) p &(((double *)im->idata)[off])
  $5 = (double *) 0x77c1c008

Getting desperate enough to disassemble:

  (gdb) disassemble 
  Dump of assembler code for function i_glinf_ddoub:
 0x77cc091c <+0>: bltza3,0x77cc09c8 
 0x77cc0920 <+4>: nop
 0x77cc0924 <+8>: lw  v0,8(a0)
 0x77cc0928 <+12>:slt v0,a3,v0
 0x77cc092c <+16>:beqzv0,0x77cc09c8 
 0x77cc0930 <+20>:nop
 0x77cc0934 <+24>:lw  v0,4(a0)
 0x77cc0938 <+28>:slt v1,a1,v0
 0x77cc093c <+32>:beqzv1,0x77cc09c8 
 0x77cc0940 <+36>:nop
 0x77cc0944 <+40>:bltza1,0x77cc09c8 
 0x77cc0948 <+44>:slt t3,v0,a2
 0x77cc094c <+48>:lw  v1,0(a0)
 0x77cc0950 <+52>:movna2,v0,t3
 0x77cc0954 <+56>:movet3,a2
 0x77cc0958 <+60>:mul a2,a3,v0
 0x77cc095c <+64>:subut3,t3,a1
 0x77cc0960 <+68>:addua3,a2,a1
 0x77cc0964 <+72>:blezt3,0x77cc09d0 
 0x77cc0968 <+76>:mul a3,a3,v1
 0x77cc096c <+80>:lw  t2,16(sp)
 0x77cc0970 <+84>:movev0,zero
 0x77cc0974 <+88>:blezv1,0x77cc09b4 
 0x77cc0978 <+92>:nop
 0x77cc097c <+96>:sll t0,a3,0x3
 0x77cc0980 <+100>:   movea2,zero
 0x77cc0984 <+104>:   subut0,t0,t2
 0x77cc0988 <+108>:   movea1,t2
 0x77cc098c <+112>:   lw  v1,32(a0)
 0x77cc0990 <+116>:   addiu   a2,a2,1
 0x77cc0994 <+120>:   adduv1,v1,a1
 0x77cc0998 <+124>:   addiu   a1,a1,8
  => 0x77cc099c <+128>:   ldxc1   $f0,v1(t0)
 0x77cc09a0 <+132>:   sdc1$f0,-8(a1)
 0x77cc09a4 <+136>:   lw  v1,0(a0)
 0x77cc09a8 <+140>:   slt t1,a2,v1
 0x77cc09ac <+144>:   bnezt1,0x77cc098c 
 0x77cc09b0 <+148>:   addiu   a3,a3,1
 0x77cc09b4 <+152>:   addiu   v0,v0,1
 0x77cc09b8 <+156>:   bne t3,v0,0x77cc0974 
 0x77cc09bc <+160>:   addiu   t2,t2,32
 0x77cc09c0 <+164>:   jr  ra
 0x77cc09c4 <+168>:   nop
 0x77cc09c8 <+172>:   jr  ra
 0x77cc09cc <+176>:   movev0,zero
 0x77cc09d0 <+180>:   jr  ra
 0x77cc09d4 <+184>:   movev0,t3
  End of assembler dump.

This seems to be the toolchain problem described at
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176
as the underlying host here is also a 64-bit one and the conditions match:

  (gdb) p /x $t0   
  $7 = 0xaa882f50
  (gdb) p /x $v1
  $8 = 0xcd3990b8
  (gdb) p /x $t0 + $v1
  $9 = 0x77c1c008

FWIW building with gcc-5 works fine and passes all the tests. 
The disassembled code there uses ldc1 not ldxc1.

Unfortunately gcc doesn't seem to have a targeted option to disable this
optimization. Building with -O0 on mips and mipsel is probably the best
workaround we have 

Processed: Re: luajit: laujit segfaults on arm64

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #818616 [src:luajit] luajit: laujit segfaults on arm64
Severity set to 'serious' from 'important'

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

Bug#839050: marked as done (js24 crashes on ARM64)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 21:49:27 +
with message-id 
and subject line Bug#839050: fixed in mozjs24 24.2.0-4
has caused the Debian Bug report #839050,
regarding js24 crashes on ARM64
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.)


-- 
839050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmozjs-24-bin

root@3aeb83a7878f:~# cat a.js
print("hello")
root@3aeb83a7878f:~# js24 a.js
Segmentation fault (core dumped)

There is an assumption that the VA bits is less equal than 47 bits in
mozjs. But it is not true any more when we compile the kernel with 48 VA
bits.

Patch is attached which should fix the problem which is a back port version
of the upstream fix.

Reference links :
1. upstream fix : https://bugzilla.mozilla.org/show_bug.cgi?id=1143022
2. redhat fix : https://bugzilla.redhat.com/show_bug.cgi?id=1242326


Manually_mmap_heap_memory_esr24.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: mozjs24
Source-Version: 24.2.0-4

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated mozjs24 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, 08 Dec 2016 19:04:08 +
Source: mozjs24
Binary: libmozjs-24-0 libmozjs-24-0-dbg libmozjs-24-dev libmozjs-24-bin 
libmozjs-24-bin-dbg
Architecture: source amd64
Version: 24.2.0-4
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libmozjs-24-0 - Spidermonkey JavaScript engine
 libmozjs-24-0-dbg - Spidermonkey JavaScript engine (debug symbols)
 libmozjs-24-bin - Spidermonkey JavaScript shell
 libmozjs-24-bin-dbg - Spidermonkey JavaScript shell (debug symbols)
 libmozjs-24-dev - Spidermonkey JavaScript library - development headers
Closes: 760757 839050 844257
Changes:
 mozjs24 (24.2.0-4) unstable; urgency=low
 .
   * Backport upstream fix for ARM64 crashes (closes: #839050).
   * Add Multi-Arch field to libmozjs-24-0 and its -dbg variant
 (closes: #760757).
   * Update homepage (closes: #844257).
   * Set SHELL for running configure.
   * Update Standards-Version to 3.9.8 .
Checksums-Sha1:
 8ea55ce24efac148552b7d3db44718d84b6c7377 2134 mozjs24_24.2.0-4.dsc
 920fb85d2eca85e224a8bbf95730f9982637da08 10032 mozjs24_24.2.0-4.debian.tar.xz
 f53d8766567e588241723bd8587f5fdb090c52d2 49484952 
libmozjs-24-0-dbg_24.2.0-4_amd64.deb
 7b18562719d61d2e60a3cdfe79e58c75e7f64e34 1678348 
libmozjs-24-0_24.2.0-4_amd64.deb
 de3f36f001857a82f272745c37972875b71bc576 49517076 
libmozjs-24-bin-dbg_24.2.0-4_amd64.deb
 cbdd6e5efa4328bfe4c3f6b5c60c1f426fb8f457 1744028 
libmozjs-24-bin_24.2.0-4_amd64.deb
 6a031442adfa9bd8ebc93c7e87cee3ec086d3ab4 2478200 
libmozjs-24-dev_24.2.0-4_amd64.deb
 2445723066ad3956cb54a98b12017cd0aeb19e0a 7105 mozjs24_24.2.0-4_amd64.buildinfo
Checksums-Sha256:
 551c819becf91ef02758ce417f182260b462b7a5b2315627e90ed4960509275f 2134 
mozjs24_24.2.0-4.dsc
 9596723c3ad441101607491357900622ac71809586a9b76c8228b3864fb79073 10032 
mozjs24_24.2.0-4.debian.tar.xz
 1360e9c0f8a54055c5e334e4ddc98ad53561af08c461d87c06b1a1ada5f76018 49484952 
libmozjs-24-0-dbg_24.2.0-4_amd64.deb
 9b549bc4af2ef2a3ea8560332d4f0362e893099c86bdb1942a24b4354c80b90b 1678348 
libmozjs-24-0_24.2.0-4_amd64.deb
 673e24a618861e9be30a9207122fb5bb590854f191db640407cbd77fca7d80d6 49517076 
libmozjs-24-bin-dbg_24.2.0-4_amd64.deb
 da7d8b7d1309af1d220190dfa3c164d32a6d26d97ddc4fe1d2639e5b28b6428e 1744028 
libmozjs-24-bin_24.2.0-4_amd64.deb
 4177875cd44f8c47437f0be354e4a98cdde028bc79f088e1d0143cf23978d41a 2478200 
libmozjs-24-dev_24.2.0-4_amd64.deb
 a840c0da321a75fc9eb6318cd7ab9441b6441be45780f38565f48246f89a725e 7105 
mozjs24_24.2.0-4_amd64.buildinfo
Files:
 09214066c404b7858c6303616af8693a 2134 libs optional mozjs24_24.2.0-4.dsc
 5359a47b9752f47e3d6607d56ef58184 

Bug#828342: Building with OpenSSL 1.0.2 is sufficient for stretch

[Sebastian Andrzej Siewior]

On 2016-11-10 13:53:44 [+0200], Adrian Bunk wrote:
> Control: tags -1 patch
> 
> Not a perfect solution but sufficient for stretch is the following 
> change to use OpenSSL 1.0.2:

The patch attached is against 2.4.12. It is probably better to ship
something more recent if at all :)
Can upstream please look at it?

> cu
> Adrian
> 

Sebastian
>From d22a8aad49283131472f79c9a1f369d78a397c9d Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Thu, 8 Dec 2016 20:47:15 +
Subject: [PATCH] httest: add OpenSSL 1.1.0 support

Most things are straight forward but then there is
| sconfig->ssl->state=SSL_ST_ACCEPT;
which I don't understand.

Signed-off-by: Sebastian Andrzej Siewior 
---
 src/eval.c   | 34 -
 src/htntlm.c | 71 ++-
 src/htproxy.c|  4 +++
 src/httest.c | 42 ---
 src/ssl.c| 77 +++-
 src/ssl_module.c | 21 ++--
 6 files changed, 185 insertions(+), 64 deletions(-)

diff --git a/src/eval.c b/src/eval.c
index d99cad8fc151..61268aff720d 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -109,6 +109,16 @@ static apr_status_t math_parse_factor(math_eval_t *hook);
 /
  * Local 
  ***/
+#if OPENSSL_VERSION_NUMBER < 0x1010
+
+#define sk_long_push(x, y)		SKM_sk_push(long, x, y)
+#define sk_long_pop(x)			SKM_sk_pop(long, x)
+#define sk_long_new_null()		SKM_sk_new_null(long)
+
+#else
+DEFINE_STACK_OF(long);
+#endif
+
 /**
  * skip spaces
  * @param hook IN eval instance
@@ -317,7 +327,7 @@ static apr_status_t math_parse_factor(math_eval_t *hook) {
   case MATH_NUM:
 number = apr_pcalloc(hook->pool, sizeof(*number));
 *number = hook->last_number * sign;
-SKM_sk_push(long, hook->stack, number);
+sk_long_push(hook->stack, number);
 math_get_token(hook);
 return APR_SUCCESS;
 break;
@@ -367,8 +377,8 @@ static apr_status_t math_parse_term(math_eval_t *hook) {
   return status;
 }
 
-right = SKM_sk_pop(long, hook->stack);
-left = SKM_sk_pop(long, hook->stack);
+right = sk_long_pop(hook->stack);
+left = sk_long_pop(hook->stack);
 result = apr_pcalloc(hook->pool, sizeof(*result));
 switch (token) {
 case MATH_MUL:
@@ -388,7 +398,7 @@ static apr_status_t math_parse_term(math_eval_t *hook) {
 default:
   break;
 }
-SKM_sk_push(long, hook->stack, result);
+sk_long_push(hook->stack, result);
  
 token = math_peek_token(hook);
   }
@@ -424,8 +434,8 @@ static apr_status_t math_parse_expression(math_eval_t *hook) {
   return status;
 }
 
-right = SKM_sk_pop(long, hook->stack);
-left = SKM_sk_pop(long, hook->stack);
+right = sk_long_pop(hook->stack);
+left = sk_long_pop(hook->stack);
 result = apr_pcalloc(hook->pool, sizeof(*result));
 switch (token) {
 case MATH_ADD:
@@ -437,7 +447,7 @@ static apr_status_t math_parse_expression(math_eval_t *hook) {
 default:
   break;
 }
-SKM_sk_push(long, hook->stack, result);
+sk_long_push(hook->stack, result);
 
 token = math_peek_token(hook);
   }
@@ -474,8 +484,8 @@ static apr_status_t math_parse_equalit(math_eval_t *hook) {
   return status;
 }
 
-right = SKM_sk_pop(long, hook->stack);
-left = SKM_sk_pop(long, hook->stack);
+right = sk_long_pop(hook->stack);
+left = sk_long_pop(hook->stack);
 result = apr_pcalloc(hook->pool, sizeof(*result));
 switch (token) {
 case MATH_EQ:
@@ -499,7 +509,7 @@ static apr_status_t math_parse_equalit(math_eval_t *hook) {
 default:
   break;
 }
-SKM_sk_push(long, hook->stack, result);
+sk_long_push(hook->stack, result);
   }
   return APR_SUCCESS;
 }
@@ -512,7 +522,7 @@ static apr_status_t math_parse_equalit(math_eval_t *hook) {
 static apr_status_t math_parse(math_eval_t * hook, long *val) {
   long *result;
   apr_status_t status = math_parse_equalit(hook);
-  result = SKM_sk_pop(long, hook->stack);
+  result = sk_long_pop(hook->stack);
   *val = *result;
   return status;
 }
@@ -530,7 +540,7 @@ static apr_status_t math_parse(math_eval_t * hook, long *val) {
 math_eval_t *math_eval_make(apr_pool_t * pool) {
   math_eval_t *hook = apr_pcalloc(pool, sizeof(*hook));
   hook->pool = pool; 
-  hook->stack = SKM_sk_new_null(long);
+  hook->stack = sk_long_new_null();
   hook->delimiter = apr_pstrdup(pool, "+-*/=<>!()");
 
   return hook;
diff --git a/src/htntlm.c b/src/htntlm.c
index 69984a19c44f..c4e566766abd 100644
--- a/src/htntlm.c
+++ b/src/htntlm.c
@@ -669,6 +669,31 @@ static unsigned char * get_ntlm_hash(htntlm_t *hook) {
   return get_hash(hook, ntlmbuffer, (DES_cblock *));
 }
 
+#if OPENSSL_VERSION_NUMBER < 0x1010
+
+static inline HMAC_CTX *HMAC_CTX_new(void)
+{
+	

Processed: Re: Help needed for Bug#847171 soapdenovo2: Different output, still FTBFS

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 soapdenovo2: FTBFS with parallel builds (dpkg-buildpackage -J$n, 
> $n > 1)
Bug #847171 [src:soapdenovo2] soapdenovo2: FTBFS: standardPregraph/iterate.o: 
file not recognized: File truncated
Changed Bug title to 'soapdenovo2: FTBFS with parallel builds 
(dpkg-buildpackage -J$n, $n > 1)' from 'soapdenovo2: FTBFS: 
standardPregraph/iterate.o: file not recognized: File truncated'.

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

Bug#847171: Help needed for Bug#847171 soapdenovo2: Different output, still FTBFS

[Christian Seiler]

Control: retitle -1 soapdenovo2: FTBFS with parallel builds (dpkg-buildpackage 
-J$n, $n > 1)

On 12/08/2016 09:17 PM, Andreas Tille wrote:
> On Thu, Dec 08, 2016 at 02:11:07PM +0500, Andrey Rahmatullin wrote:
>> On Thu, Dec 08, 2016 at 09:58:37AM +0100, Andreas Tille wrote:
>>> it seems there are different ways how the build fails but its totally
>>> unclear to me why this happens.
>> The package just built fine in my sbuild chroot for 3 times.
> 
> I tried again and had one build success in pbuilder and in the very
> same pbuilder environment the next build ended with
> 
> ...
> make[2]: Leaving directory '/build/soapdenovo2-240+dfsg1/standardPregraph'
> make[2]: Leaving directory '/build/soapdenovo2-240+dfsg1/standardPregraph'
> standardPregraph/kmerhash.o: In function `search_kmerset2':
> ./kmerhash.c:227: undefined reference to `Kmer2int128'
> standardPregraph/kmerhash.o: In function `put_kmerset2':
> ./kmerhash.c:410: undefined reference to `Kmer2int128'
> standardPregraph/kmerhash.o: In function `modular':
> ./kmerhash.c:56: undefined reference to `Kmer2int128'
> standardPregraph/kmerhash.o: In function `encap_kmerset2':
> ./kmerhash.c:354: undefined reference to `Kmer2int128'
> collect2: error: ld returned 1 exit status
> Makefile:74: recipe for target 'SOAPdenovo-127mer' failed
> make[1]: *** [SOAPdenovo-127mer] Error 1
> make[1]: *** Waiting for unfinished jobs
> standardPregraph/kmerhash.o: In function `search_kmerset2':
> ./kmerhash.c:227: undefined reference to `Kmer2int128'
> standardPregraph/kmerhash.o: In function `put_kmerset2':
> ./kmerhash.c:410: undefined reference to `Kmer2int128'
> standardPregraph/kmerhash.o: In function `modular':
> ./kmerhash.c:56: undefined reference to `Kmer2int128'
> standardPregraph/kmerhash.o: In function `encap_kmerset2':
> ./kmerhash.c:354: undefined reference to `Kmer2int128'
> collect2: error: ld returned 1 exit status
> Makefile:70: recipe for target 'SOAPdenovo-63mer' failed
> make[1]: *** [SOAPdenovo-63mer] Error 1
> make[1]: Leaving directory '/build/soapdenovo2-240+dfsg1'
> dh_auto_build: make -j4 returned exit code 2
> debian/rules:15: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> I: copying local configuration
> E: Failed autobuilding of package
> 
> 
> I admit I'm totally clueless. :-(

Well, the problem is the following: upstream's build system doesn't
support parallel builds, see the Makefile:

all: SOAPdenovo-63mer SOAPdenovo-127mer
# [...]
SOAPdenovo-63mer:
@cd sparsePregraph;make 63mer=1;cd ..;
@cd standardPregraph;make 63mer=1;cd ..;
@$(CC) sparsePregraph/*.o standardPregraph/*.o $(LDFLAGS) $(LIBPATH) 
$(LIBS) $(EXTRA_FLAGS) -o SOAPdenovo-63mer
SOAPdenovo-127mer:
@cd sparsePregraph;make 127mer=1;cd ..;
@cd standardPregraph;make 127mer=1;cd ..;
@$(CC) sparsePregraph/*.o standardPregraph/*.o $(LDFLAGS) $(LIBPATH) 
$(LIBS) $(EXTRA_FLAGS) -o SOAPdenovo-127mer

It builds the project twice, and this has to be done in sequence
for this to work properly, otherwise both builds get in each other's
way.

However, if you look at the build log attached to the bug report,
you'll see that make is invoked with -j9:

   dh_auto_build
make -j9

That's the problem that's occurring here. Because you recently
switched to debhelper compat level 10 and that defaults to parallel
builds - see man 7 debhelper, which mentions that.

What you should do is to pass --max-parallel=1 to either dh or to
dh_auto_build in an override (either will likely work here) in
debian/rules to ensure that upstream's build system is never invoked
with parallel build options. As a more long-term goal you could try
to convince upstream to switch to a build system that supports
parallel building (i.e. write their Makefiles in a more make-like
manner and less in a shell script-like manner), because that will
save time during builds.

Hope that helps.

Regards,
Christian

Bug#847171: Help needed for Bug#847171 soapdenovo2: Different output, still FTBFS

[Andreas Tille]

On Thu, Dec 08, 2016 at 02:11:07PM +0500, Andrey Rahmatullin wrote:
> On Thu, Dec 08, 2016 at 09:58:37AM +0100, Andreas Tille wrote:
> > it seems there are different ways how the build fails but its totally
> > unclear to me why this happens.
> The package just built fine in my sbuild chroot for 3 times.

I tried again and had one build success in pbuilder and in the very
same pbuilder environment the next build ended with

...
make[2]: Leaving directory '/build/soapdenovo2-240+dfsg1/standardPregraph'
make[2]: Leaving directory '/build/soapdenovo2-240+dfsg1/standardPregraph'
standardPregraph/kmerhash.o: In function `search_kmerset2':
./kmerhash.c:227: undefined reference to `Kmer2int128'
standardPregraph/kmerhash.o: In function `put_kmerset2':
./kmerhash.c:410: undefined reference to `Kmer2int128'
standardPregraph/kmerhash.o: In function `modular':
./kmerhash.c:56: undefined reference to `Kmer2int128'
standardPregraph/kmerhash.o: In function `encap_kmerset2':
./kmerhash.c:354: undefined reference to `Kmer2int128'
collect2: error: ld returned 1 exit status
Makefile:74: recipe for target 'SOAPdenovo-127mer' failed
make[1]: *** [SOAPdenovo-127mer] Error 1
make[1]: *** Waiting for unfinished jobs
standardPregraph/kmerhash.o: In function `search_kmerset2':
./kmerhash.c:227: undefined reference to `Kmer2int128'
standardPregraph/kmerhash.o: In function `put_kmerset2':
./kmerhash.c:410: undefined reference to `Kmer2int128'
standardPregraph/kmerhash.o: In function `modular':
./kmerhash.c:56: undefined reference to `Kmer2int128'
standardPregraph/kmerhash.o: In function `encap_kmerset2':
./kmerhash.c:354: undefined reference to `Kmer2int128'
collect2: error: ld returned 1 exit status
Makefile:70: recipe for target 'SOAPdenovo-63mer' failed
make[1]: *** [SOAPdenovo-63mer] Error 1
make[1]: Leaving directory '/build/soapdenovo2-240+dfsg1'
dh_auto_build: make -j4 returned exit code 2
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I: copying local configuration
E: Failed autobuilding of package


I admit I'm totally clueless. :-(

Kind regards

 Andreas.


-- 
http://fam-tille.de

Bug#815725: marked as done (trilinos: FTBFS on non-amd64 64-bit architectures)

[Debian Bug Tracking System]

Your message dated Thu, 8 Dec 2016 22:17:09 +0200
with message-id 

and subject line trilinos: FTBFS on non-amd64 64-bit architectures
has caused the Debian Bug report #815725,
regarding trilinos: FTBFS on non-amd64 64-bit architectures
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.)


-- 
815725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trilinos
Version: 12.4.2-1
Severity: important
Justification: fails to build from source

Builds of trilinos for architectures other than amd64 have been
failing; please either address these errors or set its Architecture
field accordingly.  Specifically:

- On 32-bit architectures such as i386, there are errors related to
  type usage, starting with

  
/«PKGBUILDDIR»/packages/kokkos/core/src/impl/Kokkos_Atomic_Generic.hpp:144:49: 
error: no matching function for call to 'atomic_compare_exchange(long long 
unsigned int*, long long unsigned int&, long long unsigned int&)'
   oldval.i = ::Kokkos::atomic_compare_exchange( (unsigned long long 
int*)dest , assume.i , newval.i );

- On 64-bit architectures other than amd64, there are errors related
  to the use of x86 assembly:

  /tmp/ccSfso5b.s: Assembler messages:
  /tmp/ccSfso5b.s:2095: Error: unknown mnemonic `lock' -- `lock incl[x1,88]'
  /tmp/ccSfso5b.s:2213: Error: unknown mnemonic `lock' -- `lock incl[x1,92]'
  /tmp/ccSfso5b.s:2330: Error: unknown mnemonic `lock' -- `lock incl[x1,68]'
  /tmp/ccSfso5b.s:3627: Error: unknown mnemonic `lock' -- `lock decl[x20]'
  /tmp/ccSfso5b.s:3732: Error: unknown mnemonic `lock' -- `lock decl[x20]'
  packages/kokkos/core/src/CMakeFiles/trilinos_kokkoscore.dir/build.make:401: 
recipe for target 
'packages/kokkos/core/src/CMakeFiles/trilinos_kokkoscore.dir/Threads/Kokkos_Threads_TaskPolicy.cpp.o'
 failed

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Trilinos 12.10.1-1 built on amd64, arm64, mips64el, ppc64el and ppc64.
It also on built on s390x in Ubuntu, where they have libtbb-dev, see #809663.--- End Message ---

Bug#846708: marked as done (fastqc: FTBFS: [javac] /<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30: error: cannot find symbol)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 19:48:28 +
with message-id 
and subject line Bug#846708: fixed in fastqc 0.11.5+dfsg-6
has caused the Debian Bug report #846708,
regarding fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
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.)


-- 
846708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fastqc
Version: 0.11.5+dfsg-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/fastqc-0.11.5+dfsg'
> dh_auto_build
>   ant -Duser.name debian
> Buildfile: /<>/fastqc-0.11.5+dfsg/build.xml
> 
> build-subprojects:
> 
> init:
> [mkdir] Created dir: /<>/fastqc-0.11.5+dfsg/bin
>  [copy] Copying 86 files to /<>/fastqc-0.11.5+dfsg/bin
> 
> build-project:
>  [echo] FastQC: /<>/fastqc-0.11.5+dfsg/build.xml
> [javac] Compiling 67 source files to /<>/fastqc-0.11.5+dfsg/bin
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.5
> [javac] warning: [options] source value 1.5 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] target value 1.5 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete options, 
> use -Xlint:-options.
> [javac] 
> /<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
>  error: cannot find symbol
> [javac] import htsjdk.samtools.SAMFileReader;
> [javac]   ^
> [javac]   symbol:   class SAMFileReader
> [javac]   location: package htsjdk.samtools
> [javac] 
> /<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:47:
>  error: cannot find symbol
> [javac]   private SAMFileReader br;
> [javac]   ^
> [javac]   symbol:   class SAMFileReader
> [javac]   location: class BAMFile
> [javac] 
> /<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:59:
>  error: cannot find symbol
> [javac]   
> SAMFileReader.setDefaultValidationStringency(ValidationStringency.SILENT);
> [javac]   ^
> [javac]   symbol:   variable SAMFileReader
> [javac]   location: class BAMFile
> [javac] 
> /<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:63:
>  error: cannot find symbol
> [javac]   br = new SAMFileReader(fis);
> [javac]^
> [javac]   symbol:   class SAMFileReader
> [javac]   location: class BAMFile
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 4 errors
> [javac] 4 warnings
> 
> BUILD FAILED
> /<>/fastqc-0.11.5+dfsg/build.xml:36: Compile failed; see the 
> compiler error output for details.
> 
> Total time: 1 second
> dh_auto_build: ant -Duser.name debian returned exit code 1
> debian/rules:10: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/fastqc_0.11.5+dfsg-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: fastqc
Source-Version: 0.11.5+dfsg-6

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated fastqc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the 

Bug#846782: Re: Bug#846144: gobject-introspection randomly hangs liferea build

[Paul Gevers]

Hi

On 08-12-16 00:18, Emilio Pozuelo Monfort wrote:
> It would be good to get a backtrace of the hanging process.

If somebody can tell me how to backtrace a hanging process, I am more
than willing to generate it. I have now so often seen the hang while
working on this issue, I would be happy to make progress in such a way.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: validator.js: diff for NMU version 4.7.1+dfsg1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 844647 + patch
Bug #844647 [src:validator.js] validator.js FTBFS: build dependency 
node-contextify was removed
Added tag(s) patch.

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

Bug#845753: Treescape fails to build on i386 and armhf architecture

[Andreas Tille]

Hi Thibaut,

thanks a lot for the pointer to a potential solution of the problem.

On Fri, Dec 02, 2016 at 11:41:09PM +0100, Andreas Tille wrote:
> 
> It would be quite convenient to have a downloadable tarball from CRAN
> mirror since this fits the usual workflow.  If this is not possible I'd
> consider
> 
>
> https://github.com/thibautjombart/treescape/commit/bbd3f0e9c627f04daf21725c02ab8e7c69d61f8f
> 
> as a patch to the packaging.

I tried to find the essential change of this patch ignoring all
autogenerated files I considered (possibly wrongly) the follwing
patch:

 
https://anonscm.debian.org/viewvc/debian-med/trunk/packages/R/r-cran-treescape/trunk/debian/patches/0001-fixing-issue-with-new-release-of-ape.patch?view=markup

I uploaded the package including the patch but the problematic build
issue remains.  While I admit that I have no idea about R internals
nor what ape is doing I somehow can not understand in how far the
error:

...
** preparing package for lazy loading
Creating a generic function for 'toJSON' from package 'jsonlite' in package 
'googleVis'
Warning in rgl.init(initValue, onlyNULL) :
  RGL: unable to open X11 display
Warning: 'rgl_init' failed, running with rgl.useNULL = TRUE
Error: segfault from C stack overflow
* removing 
'/«PKGBUILDDIR»/debian/r-cran-treescape/usr/lib/R/site-library/treescape'
...

should be related.  The full build log is available online

  
https://buildd.debian.org/status/fetch.php?pkg=r-cran-treescape=i386=1.10.17-2=1481212918

the critical part is quite at the end.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#847287: [Pkg-roundcube-maintainers] Bug#847287:

[Guilhem Moulin]

On Thu, 08 Dec 2016 at 19:46:32 +0100, Reiner Buehl wrote:
> Sorry if I ask a stupid question, but do I understand correct, that if I
> have 1.1.5+dfsg.1-1~bpo8+2 installed, then the fix is applied?

That's correct, cf.


https://anonscm.debian.org/cgit/pkg-roundcube/roundcube.git/commit/?h=debian/1.1.5%2bdfsg.1-1_bpo8%2b2=1a45de6cabae3124a8bcb3f72c0265de5ad10efc

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

[gregor herrmann]

On Thu, 08 Dec 2016 09:11:51 +1100, Tony Cook wrote:

> > https://buildd.debian.org/status/package.php?p=libimager-perl=sid
> > 
> > ...
> > Test Summary Report
> > ---
> > t/150-type/030-double.t   (Wstat: 10 Tests: 16 Failed: 0)
> >   Non-zero wait status: 10
> >   Parse errors: Bad plan.  You planned 136 tests but ran 16.
> 
> This looks like an unaligned access from the tests that failed,
> probably in imgdouble.c.
> 
> Would it be possible to get access to this (or similar) hardware to
> debug on?

Difficult :/
 
> Otherwise a backtrace for a -g build from the crash would be handy:
> 
>   perl Makefile.PL OPTIMIZE=-g
>   make
>   gdb --args perl -Mblib t/150-type/030-double.t
>   r
>   
>   bt

Sure; this is from a mips sid chroot on minker (mips* porterbox):

First verify the build failure:

$ dpkg-buildpackage -uc -us
[..]
t/150-type/030-double.t . 
1..136
ok 1 - use Imager;
ok 2 - 1 channel image channel count mismatch
ok 3 - 1 channel image bad mask
ok 4 - 1 channel image thinks it is virtual
# 64 double bits
ok 5 - 1 channel image has bits != 64
ok 6 - 1 channel image isn't direct
ok 7 - 1 channel image width incorrect
ok 8 - 1 channel image height incorrect
ok 9 - 3 channel image channel count mismatch
ok 10 - 3 channel image bad mask
ok 11 - 3 channel image has bits != 64
ok 12 - 3 channel image isn't direct
ok 13 -  - got right color (0, 0)
ok 14 -  - got right color (99, 0)
ok 15 -  - got right color (0, 100)
ok 16 -  - got right color (99, 100)
Failed 120/136 subtests 
[..]
Test Summary Report
---
t/150-type/030-double.t   (Wstat: 10 Tests: 16 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 136 tests but ran 16.
[...]


Good. Now on the the debug build and test:

$ perl Makefile.PL OPTIMIZE=-g
[..]
$ make
[..]
$ gdb --args perl -Mblib t/150-type/030-double.t
[..]
(gdb) r
Starting program: /usr/bin/perl -Mblib t/150-type/030-double.t
warning: GDB can't find the start of the function at 0x77fc6b8c.

GDB is unable to find the start of the function at 0x77fc6b8c
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x77fc6b8c for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mips-linux-gnu/libthread_db.so.1".
warning: GDB can't find the start of the function at 0x77fc7648.
warning: GDB can't find the start of the function at 0x77fca0e8.
warning: GDB can't find the start of the function at 0x77fdb194.
1..136
warning: GDB can't find the start of the function at 0x77fca0e8.
warning: GDB can't find the start of the function at 0x77fdb194.
warning: GDB can't find the start of the function at 0x77fca0e8.
warning: GDB can't find the start of the function at 0x77fdb194.
warning: GDB can't find the start of the function at 0x77fca0e8.
warning: GDB can't find the start of the function at 0x77fdb194.
warning: GDB can't find the start of the function at 0x77fca0e8.
warning: GDB can't find the start of the function at 0x77fdb194.
ok 1 - use Imager;
ok 2 - 1 channel image channel count mismatch
ok 3 - 1 channel image bad mask
ok 4 - 1 channel image thinks it is virtual
# 64 double bits
ok 5 - 1 channel image has bits != 64
ok 6 - 1 channel image isn't direct
ok 7 - 1 channel image width incorrect
ok 8 - 1 channel image height incorrect
ok 9 - 3 channel image channel count mismatch
ok 10 - 3 channel image bad mask
ok 11 - 3 channel image has bits != 64
ok 12 - 3 channel image isn't direct
ok 13 -  - got right color (0, 0)
ok 14 -  - got right color (99, 0)
ok 15 -  - got right color (0, 100)
ok 16 -  - got right color (99, 100)
ok 17 - sanity glin @0 - check colors (0, 0)
ok 18 - sanity glin @100 - check colors (0, 100)
ok 19 - check after write - check colors (0, 1)
ok 20 - couldn't make double image
ok 21 - oo didn't give double image
ok 22 - not monochrome
ok 23 - oo copy didn't give double image
ok 24 - fail making 0 width image
ok 25 - and correct message
ok 26 - fail making 0 height image
ok 27 - and correct message
ok 28 - fail making -ve width image
ok 29 - and correct message
ok 30 - fail making -ve height image
ok 31 - and correct message
ok 32 - fail making 0 channel image
ok 33 - and correct message
ok 34 - fail making 5 channel image
ok 35 - and correct message
ok 36 - integer overflow check - 1 channel
ok 37 - but same width ok
ok 38 - but same height ok
ok 39 - check the error message
ok 40 - integer overflow check - 3 channel
ok 41 - but same width ok
ok 42 - but same height ok
ok 43 - check the error message
# channel mask tests
# with ppix
ok 44 - set to default mask
ok 45 - set to white 

Bug#846781: marked as done (FTBFS: aes.c)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 19:06:22 +
with message-id 
and subject line Bug#846781: fixed in tor 0.2.8.11-1
has caused the Debian Bug report #846781,
regarding FTBFS: aes.c
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.)


-- 
846781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.8.10-1
Severity: serious
Tags: upstream

Tor 0.2.8.10 fails to build from source on a variety of archs, including
the arms, s390x and ppc64el.  It does build on x86.

| ../src/common/aes.c:158:20: error: field 'evp' has incomplete type
|  EVP_CIPHER_CTX evp;
| ^~~
| ../src/common/aes.c: In function 'evaluate_ctr_for_aes':
| ../src/common/aes.c:254:5: warning: implicit declaration of function 
'AES_ctr128_encrypt' [-Wimplicit-function-declaration]
|  AES_ctr128_encrypt([i], [i], 1, , ivec, ivec_tmp, );
|  ^~
| ../src/common/aes.c:254:5: warning: nested extern declaration of 
'AES_ctr128_encrypt' [-Wnested-externs]
--- End Message ---
--- Begin Message ---
Source: tor
Source-Version: 0.2.8.11-1

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

Debian distribution maintenance software
pp.
Peter Palfrader  (supplier of updated tor 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, 08 Dec 2016 17:25:04 +0100
Source: tor
Binary: tor tor-dbg tor-geoipdb
Architecture: source
Version: 0.2.8.11-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Palfrader 
Changed-By: Peter Palfrader 
Description:
 tor- anonymizing overlay network for TCP
 tor-dbg- debugging symbols for Tor
 tor-geoipdb - GeoIP database for Tor
Closes: 846781
Changes:
 tor (0.2.8.11-1) unstable; urgency=medium
 .
   * New upstream version.
 Fixes FTBFS with openssl 1.1 on !x86 archs (closes: #846781).
   * Remove CAP_DAC_OVERRIDE, CAP_CHOWN, CAP_FOWNER from the systemd service
 files' CapabilityBoundingSet.  We may no longer need them.  The upstream
 changelog says that Tor changed some logic with 0.2.8.1-alpha that made
 CAP_CHOWN CAP_FOWNER no longer needed.
Checksums-Sha1:
 4102b127d85020dcbcb60c2905e0fb6334913431 1827 tor_0.2.8.11-1.dsc
 eac299dcc8250cffcea68d8bbbabb9d17942e7ef 5313244 tor_0.2.8.11.orig.tar.gz
 293465d9358507d0311ce225a573b74d9d54ad7e 40194 tor_0.2.8.11-1.diff.gz
Checksums-Sha256:
 3d3fa083bd7042f9bb672d55332fbc564c31b8b37a67b6c0316a7577923a1fe3 1827 
tor_0.2.8.11-1.dsc
 7adea0bfa17edafd4e09453f4f58a0dca737660e5358f9dafd52d55d55dc6ab3 5313244 
tor_0.2.8.11.orig.tar.gz
 3dc7ef9ea3431c257a1de53f4bd610521f36ddd8ec82ef2061fa820972f0 40194 
tor_0.2.8.11-1.diff.gz
Files:
 fda00c8a0765e6a118c0f80e1e5f54b9 1827 net optional tor_0.2.8.11-1.dsc
 53feaecb15be43b09b06ff0a23252e0d 5313244 net optional tor_0.2.8.11.orig.tar.gz
 d8700ddaccc9659d3ddce21c6efcbbd6 40194 net optional tor_0.2.8.11-1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJYSawKAAoJEIYCyCA4cjMfbUAH/3XYrFkM2hBsZ/xIWWSkwrRM
o6IC9nzh61B7VLRY3lB/B0ksUTL2IRKjYNh3SGXN6/q/E03VKd0j71MOmclZPbFH
8DLv5OIR7cHIgT5bc9nQada0px7FCZFGaj6UoTNFqvnO51rGjEVQY1Eb71rNymgn
8EBPFTK96sfkSzK0cksfGjv5MR+2aAh2nRQJ83YBBkv2PgcRuEb9y4K/+AeLDTVd
igvyM0LSGKqv3lp4bOM39Fyyecjt1LxzWbtCIhGEPdc++QdWZumYZBHV4ELWyYMb
5DC/XYJF5jKs74BbLAdleVPhjrGjakIpk6V19pO0LPAZuUCE+/HGg/Az3trdSh8=
=N14t
-END PGP SIGNATURE End Message ---

Bug#847287:

[Reiner Buehl]

Sorry if I ask a stupid question, but do I understand correct, that if I
have 1.1.5+dfsg.1-1~bpo8+2 installed, then the fix is applied?

 

Best regards,

Reiner

 

 

Bug#847493: pkg_resources.DistributionNotFound: The 'PySide' distribution was not found and is required by yubikey-piv-manager

[Luke Faraone]

Package: yubikey-piv-manager
Version: 1.3.0-1
Severity: grave
File: /usr/bin/pivman

Package fails to launch with this exception:

$ pivman
Traceback (most recent call last):
  File "/usr/bin/pivman", line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2994, 
in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2980, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3007, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 658, 
in _build_master
ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 966, 
in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 852, 
in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'PySide' distribution was not found and 
is required by yubikey-piv-manager

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

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

Versions of packages yubikey-piv-manager depends on:
ii  python   2.7.11-2
ii  python-pyside.qtgui  1.2.2-2+b1
ii  python-pyside.qtnetwork  1.2.2-2+b1
pn  python:any   
ii  yubico-piv-tool  1.4.2-1

Versions of packages yubikey-piv-manager recommends:
ii  pcscd  1.8.18-1

yubikey-piv-manager suggests no packages.

-- no debconf information

Processed: libfile-tee-perl: FTBFS randomly (Failed 1/2 test programs)

[Debian Bug Tracking System]

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

> retitle 834912 libfile-tee-perl: FTBFS randomly (Failed 1/2 test programs)
Bug #834912 [src:libfile-tee-perl] libfile-tee-perl: FTBFS too much often 
(Failed 1/2 test programs)
Changed Bug title to 'libfile-tee-perl: FTBFS randomly (Failed 1/2 test 
programs)' from 'libfile-tee-perl: FTBFS too much often (Failed 1/2 test 
programs)'.
> thanks
Stopping processing here.

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

Processed: jclic: FTBFS randomly (Internal compiler error)

[Debian Bug Tracking System]

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

> retitle 836532 jclic: FTBFS randomly (Internal compiler error)
Bug #836532 [src:jclic] jclic: FTBFS too much often (Internal compiler error)
Changed Bug title to 'jclic: FTBFS randomly (Internal compiler error)' from 
'jclic: FTBFS too much often (Internal compiler error)'.
> thanks
Stopping processing here.

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

Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing

[Chris Lamb]

Hi,

> What about wheezy / wheezy-backports? Are these packages affected too?

Yes. Am updating wheezy now with my "LTS" hat on and issuing the
corresponding DLA. :)


Regards,

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 846074 grave
Bug #846074 {Done: to...@debian.org (Dr. Tobias Quathamer)} [dateutils] 
dateutils overrides /usr/bin/dgrep, also in debian-goodies 0.66
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Bug#846074: Info received (#846074,dateutils overrides /usr/bin/dgrep, also in debian-goodies 0.66)

[Debian Bug Tracking System]

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

> reopen 846074
Bug #846074 {Done: to...@debian.org (Dr. Tobias Quathamer)} [dateutils] 
dateutils overrides /usr/bin/dgrep, also in debian-goodies 0.66
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions dateutils/0.4.0-0.2.
> thanks
Stopping processing here.

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

Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing

[Darshaka Pathirana]

On Wed, 07 Dec 2016 12:16:14 +0100 Vincent Bernat
 wrote:
>  ❦  7 décembre 2016 12:08 +0100, Guilhem Moulin  :
>
> >> Is the tag for debian/1.1.5+dfsg.1-1_bpo8+1? The diff for it is pretty
> >> big.
> >
> > 1.1.5+dfsg.1-1_bpo8+1 is the current version from jessie-backports (since
> > April 29).  The diff between 1.1.5+dfsg.1-1_bpo8+1 and 1.1.5+dfsg.1-1_bpo8+2
> > is merely the upstream fix
> >
> > 
> > https://anonscm.debian.org/cgit/pkg-roundcube/roundcube.git/diff/?id=debian/1.1.5%2bdfsg.1-1_bpo8%2b2=debian/1.1.5%2bdfsg.1-1_bpo8%2b1
> 
> I deleted the tag on my side, fetched it again and the diff is now
> OK. I'll upload in the next hour.

Wow. That was quick! Thanks to you all.

What about wheezy / wheezy-backports? Are these packages affected too?

Regards,
 - Darsha



signature.asc
Description: OpenPGP digital signature

Processed: Re: rdflib: FTBFS: Tests failures

[Debian Bug Tracking System]

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

> fixed 844912 rdflib/4.2.1-2
Bug #844912 [src:rdflib] rdflib: FTBFS: Tests failures
Marked as fixed in versions rdflib/4.2.1-2.
> thank you
Stopping processing here.

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

Bug#846074: Info received (#846074,dateutils overrides /usr/bin/dgrep, also in debian-goodies 0.66)

[Thilo Six]

reopen 846074
thanks
--

Hi,

0.4.0-0.2 still not build on all release archs after one week.
reopen and setting severty to RC.


kind regards,

 Thilo

Bug#841257: fixed in sendmail 8.15.2-7

[Andreas Beckmann]

On 2016-12-08 16:46, Axel 'the C.L.A.' Müller wrote:
> Seems to work fine - at least I'm not getting those mails anymore.

I've now implemented a different way to aquire lockfiles for the
cronjobs, let's hope that does work as well. Just uploaded to unstable.


Andreas

Bug#842753: marked as done (FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Thu, 8 Dec 2016 19:10:55 +0100
with message-id <20161208181055.kgtvqmyoa477c...@jadzia.comodo.priv.at>
and subject line Re: Bug#842753: closed by gregor herrmann  
(Bug#842753: fixed in libnet-sip-perl 0.807-1)
has caused the Debian Bug report #842753,
regarding FTBFS: test failures
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.)


-- 
842753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-sip-perl
Version: 0.690-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

0.690-1 fails to build all over the place with more or less failing
tests:

https://buildd.debian.org/status/fetch.php?pkg=libnet-sip-perl=all=0.690-1=1477852334

https://ci.debian.net/packages/libn/libnet-sip-perl/unstable/amd64/
(ok, doesn't look package specific)

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libnet-sip-perl_0.690-1.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/libnet-sip-perl_0.690-1.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.690-1.rbuild.log


Fascinating that it built for me yesterday …


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYF++FXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG5S8P/0yC0nHsTDRSYT4yY4Bd72k/
sGK3SROoWLZssxcQibtwAYiBCTkbDZ4mJwHMmTMOlLyu3jlUNect3cpctL1Cm1rS
jXDo+jPII2QoWd3QMu7no0fbjsUZdznxTxzsZvLOQKF2DsRqFx4vK8p5k5glzLn3
/nCCKdcxPhTVs7kzcA4v2AQvWp+VMDLQSB4LByDZmHMUhu5V80TLbAzNFUP2/o2a
d7XQncuj9E9LeMUoTinFqfEkG+ueoO70F7wYoOB3Hr54qOxUb+RYmbVK2a9jkeNH
vdcHCVIUig6lk9CH/fljCzv4VynzEilOtNlcQANlLORg6ACIpHfUksLCLJtys0xY
j4lrZ8ZWxpguKmdqcNLSeGcdWpAq9aDndMm01X1WC1TDOscUajg/lFA0PS3Ar+bz
gIf4edMgsdEWQlM/80WvtX3LM27tVvo8CPzERXR2VHidVMlDGG7YEBSB4peF18N9
IQHOccGFl7dj2fLoP5TQ3pdeGHYkNMm+3XByGPcSircezur5Qta/XI6+m8ZOZlkK
rdHMYGfGlqfApUCbOuv797G1yJirhoD6mRtf20WE29beB/wajYkGQTTtX9ZtEvhJ
c0oKbRJvHmadrRE55CHhGrLiQmMebL7sRkk4kkoUzYgzsMlUsn7ngfOmcn9gT5wc
SFY4lCtnMYnVQaGX0GaC
=nZRb
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.807-1

On Thu, 08 Dec 2016 00:13:32 +0100, gregor herrmann wrote:

> Control: reopen -1

> > This is an automatic notification regarding your Bug report
> > which was filed against the libnet-sip-perl package:
> > #842753: FTBFS: test failures
> > It has been closed by gregor herrmann .
> That was too fast :/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/libnet-sip-perl.html
> https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.807-1.rbuild.log

This log is interesting: the builder first downloads 0.807-1 and then
builds 0.802-1. -- Detected by upstream, cf.
https://rt.cpan.org/Public/Bug/Display.html?id=118824#txn-1689425

The logs for actual builds of 0.807-1 show no problems with these
kinds of failures anymore, so closing this bug again.

(There's a new test failure on i386 which deserves looking closer
...)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Beast Of Burden


signature.asc
Description: Digital Signature
--- End Message ---

Processed: [bts-link] source package libnet-sip-perl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package libnet-sip-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #842753 (http://bugs.debian.org/842753)
> # Bug title: FTBFS: test failures
> #  * http://rt.cpan.org/Public/Bug/Display.html?id=118824
> #  * remote status changed: open -> resolved
> #  * closed upstream
> tags 842753 + fixed-upstream
Bug #842753 [libnet-sip-perl] FTBFS: test failures
Added tag(s) fixed-upstream.
> usertags 842753 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 842753 + status-resolved
There were no usertags set.
Usertags are now: status-resolved.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:pkcs11-helper

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pkcs11-helper
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #828506 (http://bugs.debian.org/828506)
> # Bug title: pkcs11-helper: FTBFS with openssl 1.1.0
> #  * https://github.com/OpenSC/pkcs11-helper/pull/7
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 828506 + fixed-upstream
Bug #828506 [src:pkcs11-helper] pkcs11-helper: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.
> usertags 828506 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 828506 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#835122: php-doctrine-cache: FTBFS (tests fail depending on stuff previously on /tmp)

[Santiago Vila]

retitle 835122 php-doctrine-cache: FTBFS (tests fail depending on stuff 
previously on /tmp)
thanks

Retitling because we know why it fails and it's not really random.

I would consider disabling the tests, as they are clearly not well
designed.

Thanks.

Processed: Re: php-doctrine-cache: FTBFS (tests fail depending on stuff previously on /tmp)

[Debian Bug Tracking System]

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

> retitle 835122 php-doctrine-cache: FTBFS (tests fail depending on stuff 
> previously on /tmp)
Bug #835122 [src:php-doctrine-cache] php-doctrine-cache: FTBFS too much often 
(failing tests)
Changed Bug title to 'php-doctrine-cache: FTBFS (tests fail depending on stuff 
previously on /tmp)' from 'php-doctrine-cache: FTBFS too much often (failing 
tests)'.
> thanks
Stopping processing here.

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

Processed: colord-gtk: diff for NMU version 0.1.26-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 837843 + patch
Bug #837843 [src:colord-gtk] colord-gtk: FTBFS due to undeclared build 
dependencies
Added tag(s) patch.

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

Bug#837843: colord-gtk: diff for NMU version 0.1.26-1.1

[Andreas Moog]

Control: tags 837843 + patch

Dear maintainer,

as the original bug report suggests, adding intltool to the Build-Depends
is enough to get the package building again.

I've prepared an NMU for colord-gtk (versioned as 0.1.26-1.1) and
will seek a sponsor for it. Please feel free to tell me if I
should delay or cancel the upload.

Regards.

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624
diff -Nru colord-gtk-0.1.26/debian/changelog colord-gtk-0.1.26/debian/changelog
--- colord-gtk-0.1.26/debian/changelog	2015-11-27 07:56:13.0 +0100
+++ colord-gtk-0.1.26/debian/changelog	2016-12-08 18:07:34.0 +0100
@@ -1,3 +1,11 @@
+colord-gtk (0.1.26-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add intltool to Build-Depends to fix FTBFS with newer version of
+gtk-doc-tools (Closes: #837843)
+
+ -- Andreas Moog   Thu, 08 Dec 2016 18:07:34 +0100
+
 colord-gtk (0.1.26-1) unstable; urgency=medium
 
   * Acknowledge NMU. Thanks to Margarita Manterola!
diff -Nru colord-gtk-0.1.26/debian/control colord-gtk-0.1.26/debian/control
--- colord-gtk-0.1.26/debian/control	2015-11-27 07:56:13.0 +0100
+++ colord-gtk-0.1.26/debian/control	2016-12-08 18:07:32.0 +0100
@@ -14,6 +14,7 @@
gobject-introspection,
libgirepository1.0-dev,
docbook-utils,
+   intltool
 Standards-Version: 3.9.6
 Section: graphics
 Homepage: http://www.freedesktop.org/software/colord/


signature.asc
Description: PGP signature

Bug#846423: marked as done (filters: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 17:18:31 +
with message-id 
and subject line Bug#846423: fixed in filters 2.55-2
has caused the Debian Bug report #846423,
regarding filters: add libfl-dev to 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.)


-- 
846423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: filters
Severity: important
User: helm...@debian.org
Usertags: libfldep

filters will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since filters uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: filters
Source-Version: 2.55-2

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

Debian distribution maintenance software
pp.
Marius Gavrilescu  (supplier of updated filters 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, 08 Dec 2016 18:08:58 +0200
Source: filters
Binary: filters
Architecture: source
Version: 2.55-2
Distribution: unstable
Urgency: medium
Maintainer: Marius Gavrilescu 
Changed-By: Marius Gavrilescu 
Description:
 filters- collected filters, including B1FF and the Swedish Chef
Closes: 846423
Changes:
 filters (2.55-2) unstable; urgency=medium
 .
   * Build-Depend on libfl-dev (Closes: #846423)
   * Bump Standards-Version to 3.9.8
   * Use hardening compilation options
Checksums-Sha1:
 7d8e7e7eec19ea5fc0a1154918290fb39eaf08a7 1499 filters_2.55-2.dsc
 a6d37a72c7067323c390c2efb134f054fd64291c 7168 filters_2.55-2.debian.tar.xz
Checksums-Sha256:
 a49f97cb762bb7b4fa9a20ac79c913eff6d963611ae1d53a7771a32a12ed1eb2 1499 
filters_2.55-2.dsc
 44931ae9281b51b0872ffef931e39007465accbed0cac01551b93be71545fc46 7168 
filters_2.55-2.debian.tar.xz
Files:
 5a83ed39c82e60a3b75c62eef57617ed 1499 games optional filters_2.55-2.dsc
 f605186a838831cece2b480c56a5653e 7168 games optional 
filters_2.55-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlhJkIQACgkQLDtDb+rG
gQH1hwf/VV2ysPtzih0rywJxmzSYExbnGjGZ81QQeBtXDCyMZ64H/Q+3WUqSDbnS
xkTtL0B5s7Vl+DP1O+1FnRs++s7gUuyGMGU9xFM25NzBLSoXKpxrxzRZ8Q0w9c3/
sRWUMxzzNEoCQ1noBE+j2V/xqN2Lc0N756Qs6EC3CDVUPbqAgdYn94HLD0ocNYFT
Jm3eY7Lr0ecW2/HUMFSRdO0B6S9VA7mWZ8uw2csycb2+dSIRcpBE7Rm929kgjzHY
H2f6pLfVqbb4lWKdZxJEUcnTLl51hdICPt28M+QUuJ8ZCjMnSHQM7B7fqq+jB7W5
t+27ZYYpiQ+fYaLWUiD0C7e81dKBcw==
=ELH7
-END PGP SIGNATURE End Message ---

Bug#847413: marked as done (gprolog: Debian changelog uncompressed)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 17:18:44 +
with message-id 
and subject line Bug#847413: fixed in gprolog 1.4.5-2
has caused the Debian Bug report #847413,
regarding gprolog: Debian changelog uncompressed
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.)


-- 
847413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gprolog
Version: 1.4.5-1
Severity: serious
Justification: Policy 12.7

gprolog now ships its Debian changelog in uncompressed form, a policy
violation that turns out to reveal a latent bug in apt-listchanges
(which I'll report in a moment, so I can't cite a number yet).

Could you please fix that?

Thanks!

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

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

Versions of packages gprolog depends on:
ii  libc6  2.24-7

gprolog recommends no packages.

gprolog suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gprolog
Source-Version: 1.4.5-2

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

Debian distribution maintenance software
pp.
Salvador Abreu  (supplier of updated gprolog 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, 08 Dec 2016 16:59:50 +
Source: gprolog
Binary: gprolog gprolog-doc
Architecture: source amd64 all
Version: 1.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Salvador Abreu 
Changed-By: Salvador Abreu 
Description:
 gprolog- GNU Prolog compiler
 gprolog-doc - documentation for the GNU Prolog compiler
Closes: 847413
Changes:
 gprolog (1.4.5-2) unstable; urgency=medium
 .
   * Bug fix: "Debian changelog uncompressed", reported by Aaron M. Ucko -
 manually compress changelog and others (closes: #847413).
   * Temporarily exclude mips and mipsel from the target architectures,
 until the old back-end is ported (it's no longer in upstream).
   * Fall back to using gcc 5 because gcc 6 (now current) bombs on i386 for
 src/EnginePl/machine.c
   * Adjust "configure" flags to suit i386 as well.
   * Disable call to mallopt() in machine.c
Checksums-Sha1:
 3b16c36cbd8055d006610ce8bc34e69f3fc3f72e 2035 gprolog_1.4.5-2.dsc
 17342692a096c1cc8e2edd8529394513badf5729 23568 gprolog_1.4.5-2.debian.tar.xz
 75ab52d6b37d4e9aceb1917efaa7224f934a9362 1897744 
gprolog-dbgsym_1.4.5-2_amd64.deb
 f5fbce9127c3ca89063a76a6ec8617a143cd24ac 1004200 gprolog-doc_1.4.5-2_all.deb
 29b358e5cc2cbfcb94ee9dc3545307db55e657e4 8575 gprolog_1.4.5-2_amd64.buildinfo
 de032fb2507b72b2decfe64e96e80a9cd4a512eb 986176 gprolog_1.4.5-2_amd64.deb
Checksums-Sha256:
 217ebd53358d857bcde943a8de45d3e1e6c6e65fc92f85bc2428e3e9893ef7ee 2035 
gprolog_1.4.5-2.dsc
 9e34392d3c81f05e0679f13596105ddbd31c09ae0a9193a76c1001629762952c 23568 
gprolog_1.4.5-2.debian.tar.xz
 744dd8469b7ff94d22c638b6488cbc89d656d87689911d12531ff2f1e4b6d859 1897744 
gprolog-dbgsym_1.4.5-2_amd64.deb
 b43c8f66051e0efa3ef1e9acfdecd9d46e042080122f99029e4af4e5ea8d5629 1004200 
gprolog-doc_1.4.5-2_all.deb
 85e4f943bbd04bf80fd3f7941b64ae095a3a4d714c8457ddd28f3921fc49c9a3 8575 
gprolog_1.4.5-2_amd64.buildinfo
 add18c528b211bb056ed5d452408f889b7be4ec2ce6392ad51d6f6f4392d2a07 986176 
gprolog_1.4.5-2_amd64.deb
Files:
 9cb4c1eb88bac7513d9b5d1c500d59e4 2035 devel optional gprolog_1.4.5-2.dsc
 f5653726794e1bd6fe6cf4594de32add 23568 devel optional 
gprolog_1.4.5-2.debian.tar.xz
 dce210ba2af2818258b8cc09cafce0b9 1897744 debug extra 
gprolog-dbgsym_1.4.5-2_amd64.deb
 b6ea88ae3062f774badaa49802010b45 1004200 doc optional 
gprolog-doc_1.4.5-2_all.deb
 c4e20e02f8f4fa8bd4351bb4ad05d704 8575 devel optional 

Processed: Re: Bug#845753: marked as done (r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow)

[Debian Bug Tracking System]

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

> reopen 845753
Bug #845753 {Done: Andreas Tille } [src:r-cran-treescape] 
r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions r-cran-treescape/1.10.17-2.
> thanks
Stopping processing here.

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

Processed: Re: ruby-httpclient: FTBFS randomly (failing tests)

[Debian Bug Tracking System]

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

> retitle 834686 ruby-httpclient: FTBFS randomly (failing tests)
Bug #834686 [src:ruby-httpclient] ruby-httpclient: FTBFS too much often 
(failing tests)
Changed Bug title to 'ruby-httpclient: FTBFS randomly (failing tests)' from 
'ruby-httpclient: FTBFS too much often (failing tests)'.
> thanks
Stopping processing here.

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

Bug#834686: ruby-httpclient: FTBFS randomly (failing tests)

[Santiago Vila]

retitle 834686 ruby-httpclient: FTBFS randomly (failing tests)
thanks

[ I'm changing the subject because I never liked the old wording ].

If you try to reproduce this, please try a lot of times. After
building this package 100 times today, the failure rate is about 20%.
(Using sbuild on a single CPU QEMU/KVM virtual machine).

Thanks.

Processed: Re: python-async: FTBFS on single CPU machines

[Debian Bug Tracking System]

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

> retitle 834917 python-async: FTBFS on single CPU machines
Bug #834917 [src:python-async] FTBFS on single CPU machines
Changed Bug title to 'python-async: FTBFS on single CPU machines' from 'FTBFS 
on single CPU machines'.
> thanks
Stopping processing here.

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

Bug#842093: [u...@kleine-koenig.org: Re: libupnp: CVE-2016-8863]

[Uwe Kleine-König]

On Thu, Dec 08, 2016 at 02:36:01PM +0100, Uwe Kleine-König wrote:
> I created a patch for CVE-2016-8863 but forgot to Cc: you. Do you care
> to take a look?

I now created a more sophisticated patch and attached it to the original
bug report (https://sourceforge.net/p/pupnp/bugs/133/).

Feedback welcome.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#846502: marked as done (nvidia-driver: could not install nvidia-driver under sid because of dependence broken)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 16:50:34 +
with message-id 
and subject line Bug#845638: fixed in nvidia-graphics-drivers 375.20-4
has caused the Debian Bug report #845638,
regarding nvidia-driver: could not install nvidia-driver under sid because of 
dependence broken
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.)


-- 
845638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 367
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,


 When I upgraded my sid system, I found could not install nvidia-driver 367 
any more, becuase of nvidia-setting or xserver-xorg-video-nvidia.

 I think Upload new version nvidia-setting could fix this problem.

Thanks,
Liang

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 375.20-4

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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, 08 Dec 2016 17:23:29 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libgldispatch0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia 
libglx-nvidia0 libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx 
libgl1-nvidia-glx libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia 
libegl-nvidia0 libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 
libgles2-glvnd-nvidia libgles2-nvidia libgles-nvidia2 libnvidia-eglcore 
libnvidia-egl-wayland nvidia-egl-common nvidia-egl-icd nvidia-vulkan-common 
nvidia-vulkan-icd libnvidia-cfg1 nvidia-alternative nvidia-kernel-support 
nvidia-kernel-dkms nvidia-kernel-source nvidia-vdpau-driver nvidia-smi 
nvidia-cuda-mps libcuda1 libcuda1-i386 libnvidia-compiler 
libnvidia-fatbinaryloader libnvidia-ptxjitcompiler libnvcuvid1 
libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 375.20-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library${nvidia:LegacyDesc}
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
 libegl-nvidia0 - NVIDIA binary EGL library${nvidia:LegacyDesc}
 libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND 
variant)${nvidia:LegacyDesc}
 libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND 
variant)${nvidia:LegacyDe
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND 
variant)${nvidia:Lega
 libgldispatch0-nvidia - Vendor neutral GL dispatch library -- libGLdispatch
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library${nvidia:LegacyDesc}
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library${nvidia:LegacyDesc}
 libgles1-glvnd-nvidia - NVIDIA binary OpenGL|ES 1.x GLVND stub library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library 
(transitional)${nvidia:Legacy
 libgles2-glvnd-nvidia - NVIDIA binary OpenGL|ES 2.x GLVND stub library
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library 
(transitional)${nvidia:Legacy
 libglx-nvidia0 - NVIDIA binary GLX library${nvidia:LegacyDesc}
 

Bug#845638: marked as done (Compatibility with xserver 1.19 / xorg-video-abi-23)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 16:50:34 +
with message-id 
and subject line Bug#845638: fixed in nvidia-graphics-drivers 375.20-4
has caused the Debian Bug report #845638,
regarding Compatibility with xserver 1.19 / xorg-video-abi-23
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.)


-- 
845638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 367.57-2
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 375.20-4

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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, 08 Dec 2016 17:23:29 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libgldispatch0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia 
libglx-nvidia0 libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx 
libgl1-nvidia-glx libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia 
libegl-nvidia0 libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 
libgles2-glvnd-nvidia libgles2-nvidia libgles-nvidia2 libnvidia-eglcore 
libnvidia-egl-wayland nvidia-egl-common nvidia-egl-icd nvidia-vulkan-common 
nvidia-vulkan-icd libnvidia-cfg1 nvidia-alternative nvidia-kernel-support 
nvidia-kernel-dkms nvidia-kernel-source nvidia-vdpau-driver nvidia-smi 
nvidia-cuda-mps libcuda1 libcuda1-i386 libnvidia-compiler 
libnvidia-fatbinaryloader libnvidia-ptxjitcompiler libnvcuvid1 
libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 375.20-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library${nvidia:LegacyDesc}
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
 libegl-nvidia0 - NVIDIA binary EGL library${nvidia:LegacyDesc}
 libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND 
variant)${nvidia:LegacyDesc}
 libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND 
variant)${nvidia:LegacyDe
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND 
variant)${nvidia:Lega
 libgldispatch0-nvidia - Vendor neutral GL dispatch library -- libGLdispatch
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library${nvidia:LegacyDesc}
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library${nvidia:LegacyDesc}
 libgles1-glvnd-nvidia - NVIDIA binary OpenGL|ES 1.x GLVND stub library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library 
(transitional)${nvidia:Legacy
 libgles2-glvnd-nvidia - NVIDIA binary OpenGL|ES 2.x GLVND stub library
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library 
(transitional)${nvidia:Legacy
 libglx-nvidia0 - NVIDIA binary GLX library${nvidia:LegacyDesc}
 libglx0-glvnd-nvidia - Vendor neutral GL dispatch library -- libGLX
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library${nvidia:LegacyDesc}
 libnvidia-cfg1 - NVIDIA binary OpenGL/GLX configuration 
library${nvidia:LegacyDesc
 libnvidia-compiler - NVIDIA runtime compiler library${nvidia:LegacyDesc}
 libnvidia-egl-wayland - NVIDIA binary EGL wayland libraries${nvidia:LegacyDesc}
 

Processed: Re: python-ws4py: FTBFS on single CPU machines

[Debian Bug Tracking System]

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

> retitle 834921 python-ws4py: FTBFS on single CPU machines
Bug #834921 [src:python-ws4py] python-ws4py: FTBFS too much often 
(AssertionError:)
Changed Bug title to 'python-ws4py: FTBFS on single CPU machines' from 
'python-ws4py: FTBFS too much often (AssertionError:)'.
> thanks
Stopping processing here.

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

Bug#834921: python-ws4py: FTBFS on single CPU machines

[Santiago Vila]

retitle 834921 python-ws4py: FTBFS on single CPU machines
thanks

I tried to build this package 200 times today and it failed 200 times.
Then I tried once with a 2-CPU machine and it built ok.

Therefore, to reproduce, please try building on a single-CPU machine.

Thanks.

Processed: forcibly merging 845354 845357 845764

[Debian Bug Tracking System]

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

> forcemerge 845354 845357 845764
Bug #845354 [cinnamon] [nemo] Nemo does not mounts partition
Bug #845764 {Done: Maximiliano Curia } [cinnamon] cinnamon: 
polkit agent isn's set correctly
Severity set to 'serious' from 'normal'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions cinnamon/3.0.7-3.
Added indication that 845764 affects nemo
Bug #845357 [cinnamon] [nemo] Nemo does not open window after pressing "open as 
Root"
Severity set to 'serious' from 'normal'
Added indication that 845357 affects nemo
Marked as fixed in versions cinnamon/3.0.7-3.
Bug #845354 [cinnamon] [nemo] Nemo does not mounts partition
Marked as fixed in versions cinnamon/3.0.7-3.
Bug #845764 [cinnamon] cinnamon: polkit agent isn's set correctly
Marked as fixed in versions cinnamon/3.0.7-3.
Merged 845354 845357 845764
> thanks
Stopping processing here.

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

Bug#846423: filters: add libfl-dev to Build-Depends

[Marius Gavrilescu]

Helmut Grohne  writes:

> filters will soon fail to build from source, beause flex drops its
> dependency on libfl-dev. Since filters uses parts of libfl-dev (e.g.
> libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
> Build-Depends. This change was previously announced[1] to
> debian-devel in accordance with DevRef 7.1.1. Please add the missing
> dependency.

Hi,

I have uploaded a fixed version (2.55-2) to mentors.d.n. It adds the
build dependency, bumps the Standards-Version, and adds hardening build
options. You can get it here: https://mentors.debian.net/package/filters

Would you be willing to sponsor it for me?

Thank you,
-- 
Marius Gavrilescu


signature.asc
Description: PGP signature

Bug#834915: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)

[Jérémy Lal]

2016-12-08 16:30 GMT+01:00 Santiago Vila :
> retitle 834915 node-temp: FTBFS (AssertionError: temp.createWriteStream did 
> not create a file)
> thanks
>
> It really happens all the time, and it also happens here:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-temp.html

I'm not reproducing it in a sbuild schroot.
However i updated the package and enabled the tests in autopkgtest,
but there's no point in uploading it if it doesn't fix the issue.

Jérémy

Processed: Re: python-async: FTBFS on single CPU machines

[Debian Bug Tracking System]

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

> retitle 834917 FTBFS on single CPU machines
Bug #834917 [src:python-async] python-async: FTBFS too much often ('NoneType' 
object is not callable)
Changed Bug title to 'FTBFS on single CPU machines' from 'python-async: FTBFS 
too much often ('NoneType' object is not callable)'.
> thanks
Stopping processing here.

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

Bug#834917: python-async: FTBFS on single CPU machines

[Santiago Vila]

retitle 834917 FTBFS on single CPU machines
thanks

After some tests, it seems this fails when having a single CPU core
(which is what I use all the time).

This is the test which fails:

> ==
> ERROR: test_base (async.test.test_performance.TestThreadPoolPerformance)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/async/test/test_performance.py",
>  line 30, in test_base
> for num_threads in range(0, self.max_threads*2 + 1, self.max_threads // 
> 2):
> ValueError: range() step argument must not be zero

I would just forward this upstream and disable the test,
as this is like having an undeclared "Build-CPU: 2" in debian/control.
(No, there is no such field, and I hope we will never need it).

Thanks.

Bug#845016: marked as done (AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: EVP_CIPHER_CTX_cleanup)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 16:09:21 +
with message-id 
and subject line Bug#845016: fixed in shadowsocks 2.9.0-2
has caused the Debian Bug report #845016,
regarding AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined 
symbol: EVP_CIPHER_CTX_cleanup
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.)


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

(If you believe this is libssl1.1 bug feel free to reassign.)

The program simply won't start in sid:

INFO: loading config from /etc/shadowsocks/config.json
2016-11-19 15:20:09 INFO loading libcrypto from libcrypto.so.1.1
Traceback (most recent call last):
  File "/usr/bin/ssserver", line 11, in 
load_entry_point('shadowsocks==2.9.0', 'console_scripts', 'ssserver')()
  File "/usr/lib/python2.7/dist-packages/shadowsocks/server.py", line 34, in 
main
config = shell.get_config(False)
  File "/usr/lib/python2.7/dist-packages/shadowsocks/shell.py", line 270, in 
get_config
check_config(config, is_local)
  File "/usr/lib/python2.7/dist-packages/shadowsocks/shell.py", line 125, in 
check_config
encrypt.try_cipher(config['password'], config['method'])
  File "/usr/lib/python2.7/dist-packages/shadowsocks/encrypt.py", line 44, in 
try_cipher
Encryptor(key, method)
  File "/usr/lib/python2.7/dist-packages/shadowsocks/encrypt.py", line 84, in 
__init__
random_string(self._method_info[1]))
  File "/usr/lib/python2.7/dist-packages/shadowsocks/encrypt.py", line 110, in 
get_cipher
return m[2](method, key, iv, op)
  File "/usr/lib/python2.7/dist-packages/shadowsocks/crypto/openssl.py", line 
76, in __init__
load_openssl()
  File "/usr/lib/python2.7/dist-packages/shadowsocks/crypto/openssl.py", line 
52, in load_openssl
libcrypto.EVP_CIPHER_CTX_cleanup.argtypes = (c_void_p,)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
func = self.__getitem__(name)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
EVP_CIPHER_CTX_cleanup

Seems to have a closed (unreasolved) upstream issue about it, closed 
inconsistently:
https://github.com/shadowsocks/shadowsocks/issues/646


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages shadowsocks depends on:
ii  lsb-base  9.20161101
ii  python2.7.11-2
ii  python-m2crypto   0.24.0-1
ii  python-pkg-resources  28.7.1-1
pn  python:any

shadowsocks recommends no packages.

shadowsocks suggests no packages.

-- Configuration Files:
/etc/shadowsocks/config.json changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: shadowsocks
Source-Version: 2.9.0-2

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

Debian distribution maintenance software
pp.
Shell.Xu  (supplier of updated shadowsocks 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: Sun, 20 Nov 2016 14:33:31 +0800
Source: shadowsocks
Binary: shadowsocks
Architecture: source all
Version: 2.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Shell.Xu 
Changed-By: Shell.Xu 
Description:
 shadowsocks - Fast tunnel proxy that helps you bypass firewalls
Closes: 845016
Changes:
 shadowsocks (2.9.0-2) unstable; urgency=medium
 .
   [ Shell.Xu ]
   * Fix compatible issue (Closes: #845016)
Checksums-Sha1:
 

Bug#847478: FTBFS: needs to Build-Depends on gperf

[Ximin Luo]

Package: glibc
Version: 2.24-7
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

whilst trying to build glibc:

/usr/bin/install -c -m 644 
/tmp/debrepro.uGH5xEsmL1/build/source/build-tree/amd64-libc/gnu/lib-names-64.h 
/tmp/debrepro.uGH5xEsmL1/build/source/debian/tmp-libc/usr/include/gnu/lib-names-64.h
/usr/bin/install -c -m 644 
/tmp/debrepro.uGH5xEsmL1/build/source/build-tree/amd64-libc/libBrokenLocale.map 
/tmp/debrepro.uGH5xEsmL1/build/source/debian/tmp-libc/usr/lib/x86_64-linux-gnu/libBrokenLocale_pic.map
cd programs \
&& gperf -acCgopt -k1,2,5,9,$ -L ANSI-C -N charmap_hash charmap-kw.gperf > 
charmap-kw.h.new
/bin/bash: line 1: gperf: command not found
Makefile:66: recipe for target 'programs/charmap-kw.h' failed
make[3]: *** [programs/charmap-kw.h] Error 127
make[3]: Leaving directory '/tmp/debrepro.uGH5xEsmL1/build/source/locale'
Makefile:230: recipe for target 'locale/subdir_install' failed
make[2]: *** [locale/subdir_install] Error 2
make[2]: Leaving directory '/tmp/debrepro.uGH5xEsmL1/build/source'
Makefile:12: recipe for target 'install' failed
make[1]: *** [install] Error 2
make[1]: Leaving directory 
'/tmp/debrepro.uGH5xEsmL1/build/source/build-tree/amd64-libc'
debian/rules.d/build.mk:162: recipe for target 
'/tmp/debrepro.uGH5xEsmL1/build/source/stamp-dir/install_libc' failed
make: *** [/tmp/debrepro.uGH5xEsmL1/build/source/stamp-dir/install_libc] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

I: artifacts left in /tmp/debrepro.uGH5xEsmL1

Probably this just needs a Build-Depends: gperf, I am trying the build again 
now.

X

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

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

Bug#845753: marked as done (r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 15:49:35 +
with message-id 
and subject line Bug#845753: fixed in r-cran-treescape 1.10.17-2
has caused the Debian Bug report #845753,
regarding r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack 
overflow
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.)


-- 
845753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-treescape
Version: 1.10.17-1
Severity: serious

https://buildd.debian.org/status/package.php?p=r-cran-treescape=sid

...
** preparing package for lazy loading
Creating a generic function for 'toJSON' from package 'jsonlite' in package 
'googleVis'
Warning in rgl.init(initValue, onlyNULL) :
  RGL: unable to open X11 display
Warning: 'rgl_init' failed, running with rgl.useNULL = TRUE
Error: segfault from C stack overflow
* removing 
'/«PKGBUILDDIR»/debian/r-cran-treescape/usr/lib/R/site-library/treescape'
dh_auto_install: R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-cran-treescape/usr/lib/R/site-library --clean . 
--built-timestamp='Fri, 28 Oct 2016 12:02:47 +0200' returned exit code 1
debian/rules:4: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2
--- End Message ---
--- Begin Message ---
Source: r-cran-treescape
Source-Version: 1.10.17-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-treescape 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, 08 Dec 2016 16:01:06 +0100
Source: r-cran-treescape
Binary: r-cran-treescape
Architecture: source
Version: 1.10.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 r-cran-treescape - GNU R Statistical Exploration of Landscapes of Phylogenetic 
Trees
Closes: 845753
Changes:
 r-cran-treescape (1.10.17-2) unstable; urgency=medium
 .
   * Fix issue with new release of ape
 Closes: #845753
   * debhelper 10
   * d/watch: version=4
Checksums-Sha1:
 72e2873f4b55cdb403874789acfa21d3d6200d37 2392 r-cran-treescape_1.10.17-2.dsc
 ab78ce79535b640711374dcc5ea4a809cc83e626 4180 
r-cran-treescape_1.10.17-2.debian.tar.xz
Checksums-Sha256:
 2effacb24b1c484f875d7a314571149aa7c0faf79077947516b1c905ea208b59 2392 
r-cran-treescape_1.10.17-2.dsc
 3505d26ff17c2716968f7431a6202485547a8445801c4bbc728d69f08efe4111 4180 
r-cran-treescape_1.10.17-2.debian.tar.xz
Files:
 6fa9dcbbba44807865efa9aed0bb7086 2392 gnu-r optional 
r-cran-treescape_1.10.17-2.dsc
 babd26adeb6b123977538c78dd50c066 4180 gnu-r optional 
r-cran-treescape_1.10.17-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYSXwPAAoJEFeKBJTRxkbRtZkP/3JHYOv0MyN/BwLQZ232IeUX
8wubhJMRAeVihsGI4qn1noYiEpT3efV8A+eFC2IJmPam3uK9GVwPFUUdGO/7Whww
l2hztSGV+fnMgjHCa+20b+6TSIa9BOnob/hrYhyr0hw9xcAIj2BctJRRBM1eXDof
23NL2/kc1QQoF6q0H2It5vUgutxLDDaBsFo7vce2lhXO+sTkrCDPM0DL+eNNFjsT
ubYhwtqBCYILHlswuR6WnUcZPJibyrhWYIteExph72BWwylKmAMPPoqtmsYykbQl
4hGxgLksbIlQjE/FPCPY2vDiD8mltt5KawDRmOC6VLicxrb05e+OmPD0IVcaWGfy
SUy9cEDHRTBSIu5BDS7mc6dnyj5rOTTN86fYo+rrUh1/4CbqDuJiGnaSKxOg89eD
r48Fk2EwO2FOf71YzPOK3t3boLIhu/EvQ2zytP0e71GeW73D8WkwL/wfJ/LSo0Ti
2zOiTd4rDoVdy3ah8UK+qwQg8E45xpfA9DQCiulSYO+Ccbl4w+ERWxwJFjiVImSl
dOYuKC9+VHpsSqYTntsVXj1AlVl8WqdYIavt/hh5TDagMWovTIdIN4jIVz+N5XIb
FVDgnahApsVJKcp1i1vXuu4DFAb7Cobvi6FmgNbvAcF09Ds18i8hR4MSOt8IjqN7
Hc+bDXZwXAlh7E1ExJW3
=5cYR
-END PGP SIGNATURE End Message ---

Bug#841257: fixed in sendmail 8.15.2-7

[Axel 'the C.L.A.' Müller]

On Wed, 7 Dec 2016 22:24:22 +0100
Andreas Beckmann  wrote:

> On 2016-12-07 17:12, Axel 'the C.L.A.' Müller wrote:
> > Seems this change now causes cron to spam like:
> > 
> > From: root@e560 (Cron Daemon)
> > To: root@e560
> > Subject: Cron  test -x /etc/init.d/sendmail && test
> > -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail
> > && /usr/share/sendmail/sendmail cron-msp
> > 
> > su: Muss von einem Terminal gestartet werden.
> > 
> > (Translation: "su: Needs to be started from a terminal")
> > 
> 
> can you try to replace the touch_stamp() method in
> /usr/share/sendmail/sendmail with this:
> 
> 
> touch_stamp() {
> if [ "$(id -nu)" = "smmsp" ]; then
> touch "$1"
> else
> su smmsp -s /bin/sh -c "touch '$1'"
> fi
> }
> 
> 
> That should work at least for the smmsp cronjob ...
> 
> 
> Andreas

Seems to work fine - at least I'm not getting those mails anymore.
Thx. :)

Bug#846197: cpl-plugin-xshoo: FTBFS randomly (tests 126 and 230 fail)

[Ole Streicher]

Hi Santiago,

OK, I have run it ~15 times without problems last time. I however just
disabled the wrong of the two errors (one causes the other), so I switch
this now.

However, after digging into the code, the failure looks mystic, since
the number there is just created from a substring "0.9x11" by taking
everything left of the x, and then divided by 3600. The string is fixed
in the test. It looks like that there sometimes an additional digit
slips in, but in one case (20161207T200220Z) the extraction results in
25000 instead of 0.00025. Really strange. But I don't feel that I can do
much here (it is already forwarded). Upstream is informed, however.

So, I disabled the (now hopefully right) test, and the package could be
built now 40 times in a row without failure.

Thumbs crossed :-)

Best regards

Ole

Processed: Re: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)

[Debian Bug Tracking System]

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

> retitle 834915 node-temp: FTBFS (AssertionError: temp.createWriteStream did 
> not create a file)
Bug #834915 [src:node-temp] node-temp: FTBFS too much often (AssertionError: 
temp.createWriteStream did not create a file)
Changed Bug title to 'node-temp: FTBFS (AssertionError: temp.createWriteStream 
did not create a file)' from 'node-temp: FTBFS too much often (AssertionError: 
temp.createWriteStream did not create a file)'.
> thanks
Stopping processing here.

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

Bug#834915: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)

[Santiago Vila]

retitle 834915 node-temp: FTBFS (AssertionError: temp.createWriteStream did not 
create a file)
thanks

It really happens all the time, and it also happens here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-temp.html

Thanks.

Bug#847074: marked as done (postfixadmin: Files missing in 3.0.1)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 15:22:00 +
with message-id 
and subject line Bug#847074: fixed in postfixadmin 3.0-2
has caused the Debian Bug report #847074,
regarding postfixadmin: Files missing in 3.0.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.)


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

Dear Maintainer,

after the update from 2.9.3 to 3.0.1 the package was unusable because several
files are missing like the smarty folder resulting in several reproduceable 
errors.
The solution should be to include the missing files from the original source at 
sourcefourge.

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

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

Versions of packages postfixadmin depends on:
ii  apache2 [httpd]2.4.23-8
ii  dbconfig-common2.0.6
ii  debconf1.5.59
ii  mysql-client   5.6.30-1
ii  php1:7.0+46
ii  php-imap   1:7.0+46
ii  php-mbstring   1:7.0+46
ii  php-mysql  1:7.0+46
ii  php7.0 [php]   7.0.13-2
ii  php7.0-cli [php-cli]   7.0.13-2
ii  php7.0-imap [php-imap] 7.0.13-2
ii  php7.0-mbstring [php-mbstring] 7.0.13-2
ii  php7.0-mysql [php-mysqlnd] 7.0.13-2
ii  postgresql-client  9.6+177
ii  postgresql-client-9.6 [postgresql-client]  9.6.1-2
ii  wwwconfig-common   0.3.0

Versions of packages postfixadmin recommends:
ii  dovecot-core   1:2.2.26.0-4
ii  mysql-server   5.6.30-1
ii  postfix-mysql  3.1.3-4
ii  zendframework  1.12.20+dfsg-1

postfixadmin suggests no packages.

-- Configuration Files:
/etc/postfixadmin/config.inc.php changed [not included]

-- debconf information:
  postfixadmin/app-password-confirm: (password omitted)
  postfixadmin/password-confirm: (password omitted)
  postfixadmin/pgsql/admin-pass: (password omitted)
  postfixadmin/pgsql/app-pass: (password omitted)
  postfixadmin/mysql/admin-pass: (password omitted)
  postfixadmin/mysql/app-pass: (password omitted)
* postfixadmin/mysql/admin-user: debian-sys-maint
  postfixadmin/internal/skip-preseed: false
  postfixadmin/passwords-do-not-match:
  postfixadmin/pgsql/changeconf: false
  postfixadmin/db/basepath:
  postfixadmin/missing-db-package-error: abort
  postfixadmin/dbconfig-upgrade: true
  postfixadmin/pgsql/admin-user: postgres
  postfixadmin/remote/newhost:
  postfixadmin/install-error: abort
  postfixadmin/mysql/method: Unix socket
  postfixadmin/upgrade-error: abort
  postfixadmin/purge: false
* postfixadmin/dbconfig-install: true
  postfixadmin/pgsql/manualconf:
  postfixadmin/remote/port:
  postfixadmin/upgrade-backup: true
* postfixadmin/reconfigure-webserver: apache2
* postfixadmin/dbconfig-remove: true
  postfixadmin/pgsql/authmethod-user: password
  postfixadmin/pgsql/no-empty-passwords:
  postfixadmin/pgsql/authmethod-admin: ident
* postfixadmin/database-type: mysql
  postfixadmin/remove-error: abort
  postfixadmin/db/app-user: postfixadmin@localhost
  postfixadmin/internal/reconfiguring: false
  postfixadmin/dbconfig-reinstall: false
  postfixadmin/remote/host: localhost
  postfixadmin/db/dbname: postfixadmin
  postfixadmin/pgsql/method: TCP/IP
--- End Message ---
--- Begin Message ---
Source: postfixadmin
Source-Version: 3.0-2

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated postfixadmin 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with 

Bug#847218: marked as done (pure-ftpd-common: modifies conffiles (policy 10.7.3): /etc/default/pure-ftpd-common)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 15:22:17 +
with message-id 
and subject line Bug#847218: fixed in pure-ftpd 1.0.43-3
has caused the Debian Bug report #847218,
regarding pure-ftpd-common: modifies conffiles (policy 10.7.3): 
/etc/default/pure-ftpd-common
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.)


-- 
847218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pure-ftpd-common
Version: 1.0.43-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/default/pure-ftpd-common


cheers,

Andreas


pure-ftpd-common_1.0.43-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pure-ftpd
Source-Version: 1.0.43-3

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

Debian distribution maintenance software
pp.
Stefan Hornburg (Racke)  (supplier of updated pure-ftpd 
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, 08 Dec 2016 13:28:56 +0100
Source: pure-ftpd
Binary: pure-ftpd-common pure-ftpd pure-ftpd-mysql pure-ftpd-postgresql 
pure-ftpd-ldap
Architecture: source all amd64
Version: 1.0.43-3
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Stefan Hornburg (Racke) 
Description:
 pure-ftpd  - Secure and efficient FTP server
 pure-ftpd-common - Pure-FTPd FTP server (Common Files)
 pure-ftpd-ldap - Secure and efficient FTP server with LDAP user authentication
 pure-ftpd-mysql - Secure and efficient FTP server with MySQL user 
authentication
 pure-ftpd-postgresql - Secure and efficient FTP server with PostgreSQL user 
authenticati
Closes: 847218
Changes:
 pure-ftpd (1.0.43-3) unstable; urgency=medium
 .
   * Finally fix issue with /etc/default/pure-ftpd-common (Closes: #847218).
Checksums-Sha1:
 e2ccc03885aba1327e506be07c6b8b350dd8c68c 2155 pure-ftpd_1.0.43-3.dsc
 2997eb04e187fa053e6938992a2187d6b0eab8c5 49451 pure-ftpd_1.0.43-3.diff.gz
 e4fe80efad76276693f45944b890aa75be56b310 187736 
pure-ftpd-common_1.0.43-3_all.deb
 7976fa6635b9d1839a3d76bd7e35c2e0de6a45d2 18678 
pure-ftpd-dbgsym_1.0.43-3_amd64.deb
 2d8abffa76a1c0df306cd587db394d6dcb49d409 19774 
pure-ftpd-ldap-dbgsym_1.0.43-3_amd64.deb
 3ca6bc003252741afe0b54e4856fd855f2d2475a 128582 
pure-ftpd-ldap_1.0.43-3_amd64.deb
 fdb637436b3e0e3ee9b28c7d582006423c47543d 19590 
pure-ftpd-mysql-dbgsym_1.0.43-3_amd64.deb
 

Bug#794438: Partition manager does not launch

[Andrius Štikonas]

Hi Boyuan,

Unfortunately, you can't port the new version from Ubuntu because Ubuntu does 
not have a new version. On the other hand, neon ships a working package [1].

Actually, KDE Partition Manager 3.0 will be released on 18 December (providing 
nothing critical is found), so it might make sense to package that version.

Jonathan Carter already packaged kpmcore [2] (basically non-gui parts of KDE 
Partition Manager) in Debian, so that should make job of packaging GUI part of 
KDE Partition Manager much easier.

Best,
Andrius

[1] https://packaging.neon.kde.org/neon-packaging/partitionmanager.git/
[2] https://packages.qa.debian.org/k/kpmcore.html


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

Processed: unset tags

[Debian Bug Tracking System]

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

> tags 846708 - upstream
Bug #846708 [fastqc] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Removed tag(s) upstream.
> tags 846708 - patch
Bug #846708 [fastqc] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

[Michael Biebl]

Am 08.12.2016 um 15:20 schrieb Michael Biebl:

> Installing libnss-mdns, then libnss-resolve leads to
> 
> hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
> [!UNAVAIL=return] dns
> 
> Installing libnss-resolve, then libnss-mdns leads to
> 
> hosts:  files resolve [!UNAVAIL=return] mdns4_minimal 
> [NOTFOUND=return] dns
> 
> 
> So maybe the "obvious" fix is to change libnss-mdns to always insert itself
> before dns *and* resolve? On the other hand, it's quite ugly that mdns needs 
> to
> be taught to cope with this new nss module.
> 
> Martin, Simon, what's your take on this?
> With multiple packages mangling nsswitch.conf, this feels like it's becoming 
> very brittle
> and maybe we need a proper API like pam-auth-update.

Some more thoughts: we have quite a few libnss-* packages
> # apt-cache search --names-only libnss-
> libnss-db - NSS-Modul für die Verwendung der Berkeley-Datenbank als 
> Namensdienst
> libnss-ldap - NSS-Modul für den Einsatz von LDAP als Namensdienst
> libnss-ldapd - NSS-Modul für den Einsatz von LDAP als Namensdienst
> libnss-lwres - NSS-Modul um bind9-lwres als Namensdienst zu nutzen
> libnss-sss - Nss-Modul für den SSS-Daemon (System Security Services)
> libnss-cache - NSS module for using nsscache-generated files
> libnss-docker - nss module for finding Docker containers
> libnss-extrausers - nss module to have an additional passwd, shadow and group 
> file
> libnss-gw-name - nss module that names the current gateway’s IP address
> libnss-mysql-bg - NSS module for using MySQL as a naming service
> libnss-pgsql2 - NSS module for using PostgreSQL as a naming service
> libnss-securepass - NSS (Name Service Switch) module for Securepass
> libnss-libvirt - nss plugin providing IP add ress resolution for virtual 
> machines
> libnss-mdns - NSS module for Multicast DNS name resolution
> libnss-wrapper - NSS wrapper library
> libnss-rainbow2 - nss library for rainbow
> libnss-winbind - Samba nameservice integration plugins
> libnss-myhostname - nss module providing fallback resolution for the current 
> hostname
> libnss-mymachines - nss module to resolve hostnames for local container 
> instances
> libnss-resolve - nss module to resolve names via systemd-resolved
> libnss-systemd - nss module providing dynamic user and group name resolution

The first one that I picked was libnss-ldap
It doesn't mangle libnss-ldap directly, but it ships an example file,
which contains
hosts:  dns ldap

So, libnss-resolve's behaviour of using [!UNAVAIL=return] would break
LDAP hosts resolution as well. I guess, going through the complete list,
we would find more packages which would be affected the same way.

It seems like [!UNAVAIL=return] is generally not safe to use if you
don't know which NSS modules might come after yours.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Processed: spring: FTBFS on i386: relocation R_386_GOTOFF against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when making a shared object

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #847356 [src:binutils] spring: FTBFS on i386: relocation R_386_GOTOFF 
against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when making 
a shared object
Severity set to 'important' from 'serious'

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

Bug#846671: marked as done (artemis: FTBFS: BamView.java:115: error: cannot find symbol)

[Debian Bug Tracking System]

Your message dated Thu, 8 Dec 2016 15:30:19 +0100
with message-id 

and subject line Bug was done - just needed to unmerge 846708
has caused the Debian Bug report #846671,
regarding artemis: FTBFS: BamView.java:115: error: cannot find symbol
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.)


-- 
846671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: artemis
Version: 16.0.0+dfsg-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/artemis-16.0.0+dfsg'
> idlj -Icorba corba/types.idl
> idlj -Icorba corba/nsdb.idl
> idlj -Icorba corba/nsdb_write.idl
> idlj -Icorba corba/seqdb.idl
> CLASSPATH=/usr/share/java/biojava.jar:/usr/share/java/j2ssh-core.jar:/usr/share/java/ibatis.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/postgresql-jdbc3.jar:/usr/share/java/picard.jar:/usr/share/java/htsjdk.jar:/usr/share/java/commons-net.jar:/usr/share/java/batik-awt-util.jar:/usr/share/java/batik-dom.jar:/usr/share/java/batik-ext.jar:/usr/share/java/batik-svggen.jar:/usr/share/java/batik-util.jar:/usr/share/java/batik-xml.jar:/usr/share/EMBOSS/jemboss/lib/jemboss.jar:/<>/artemis-16.0.0+dfsg
>  javac -source 1.5 -target 1.5   
> uk/ac/sanger/artemis/MegaBlastComparisonData.java
> warning: [options] bootstrap class path not set in conjunction with -source 
> 1.5
> warning: [options] source value 1.5 is obsolete and will be removed in a 
> future release
> warning: [options] target value 1.5 is obsolete and will be removed in a 
> future release
> warning: [options] To suppress warnings about obsolete options, use 
> -Xlint:-options.
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/Feature.java:1626: 
> warning: '_' used as an identifier
> catch(OutOfDateException _) 
>  ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/Feature.java:1630: 
> warning: '_' used as an identifier
> catch(EntryInformationException _) 
> ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/Options.java:452: 
> warning: '_' used as an identifier
>   catch(Throwable _) 
>   ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/io/GFFStreamFeature.java:1031:
>  warning: '_' used as an identifier
>   catch(NumberFormatException _)
>   ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/EditMenu.java:1230:
>  warning: '_' used as an identifier
> catch(ReadOnlyException _) 
> ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/EditMenu.java:1269:
>  warning: '_' used as an identifier
> catch(ReadOnlyException _) {}
> ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/EditMenu.java:1986:
>  warning: '_' used as an identifier
>   public void itemStateChanged (ItemEvent _) {
>   ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/EditMenu.java:1995:
>  warning: '_' used as an identifier
>   public void actionPerformed (ActionEvent _) {
>^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/EditMenu.java:2155:
>  warning: '_' used as an identifier
> } catch (OutOfDateException _) {
> ^
>   (use of '_' as an identifier might not be supported in releases after Java 
> SE 8)
> /<>/artemis-16.0.0+dfsg/uk/ac/sanger/artemis/components/EditMenu.java:2157:
>  warning: '_' used as an identifier
> 

Processed: reassign fastqc

[Debian Bug Tracking System]

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

> reassign 846708 fastqc
Bug #846708 [artemis] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Bug reassigned from package 'artemis' to 'fastqc'.
Ignoring request to alter found versions of bug #846708 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846708 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#847356: Processed: spring: FTBFS on i386: relocation R_386_GOTOFF against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when making a shared object

[Matthias Klose]

Control: severity -1 important

On 07.12.2016 15:00, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
>> clone 846921 -1
> Bug #846921 [src:spring] spring: FTBFS on i386: relocation R_386_GOTOFF 
> against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when 
> making a shared object
> Bug 846921 cloned as bug 847356
>> reassign -1 src:binutils
> Bug #847356 [src:spring] spring: FTBFS on i386: relocation R_386_GOTOFF 
> against preemptible symbol _ZNSt6vectorIfSaIfEED1Ev cannot be used when 
> making a shared object
> Bug reassigned from package 'src:spring' to 'src:binutils'.

> Do you agree with this assessment?

no, it's not a RC issue, you use the BFD linker.

Processed: severity of 847462 is important

[Debian Bug Tracking System]

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

> severity 847462 important
Bug #847462 [printer-driver-cups-pdf] printer-driver-cups-pdf: make very ugly 
and uselss pdf which are not searchables
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

[Michael Biebl]

Am 04.12.2016 um 15:36 schrieb Alexander Kurtz:
> Package: libnss-resolve
> Version: 232-6
> Severity: serious
> Justification: Breaks another package
> 
> Hi!
> 
> A freshly installed Debian Stretch system will have a
> /etc/nsswitch.conf like this (see libc-bin's postinst and/or
> /usr/share/libc-bin/nsswitch.conf):
> 
>   # /etc/nsswitch.conf
>   #
>   # Example configuration of GNU Name Service Switch functionality.
>   # If you have the `glibc-doc-reference' and `info' packages installed, 
> try:
>   # `info libc "Name Service Switch"' for information about this file.
> 
>   passwd: compat
>   group:  compat
>   shadow: compat
>   gshadow:files
> 
>   hosts:  files dns
>   networks:   files
> 
>   protocols:  db files
>   services:   db files
>   ethers: db files
>   rpc:db files
> 
>   netgroup:   nis
> 
> Installing libnss-resolve makes these changes:
> 
>   --- nsswitch.conf   2016-12-04 15:16:42.701978711 +0100
>   +++ /etc/nsswitch.conf  2016-12-04 15:16:51.965961200
> +0100
>   @@ -9,7 +9,7 @@
>shadow: compat
>gshadow:files
>
>   -hosts:  files dns
>   +hosts:  files resolve [!UNAVAIL=return] dns
>networks:   files
>
>protocols:  db files
> 
> If the user then installs for example the "gnome" meta package, 
> libnss-mdns and libnss-myhostname will be installed as well because of
> these dependencies/recommendations: 
> 
>   gnome -> avahi-daemon -> libnss-mdns
>   gnome -> gnome-core -> gnome-control-center -> libnss-myhostname
> 
> This results in the following hosts line:
> 
>   hosts:  files resolve [!UNAVAIL=return] mdns4_minimal 
> [NOTFOUND=return] dns myhostname
> 
> However, because of the "[!UNAVAIL=return]" introduced with [0],
> nothing after "resolve" will actually be tried. This is mostly
> harmless, since "resolve" provides a superset of "dns" and
> "myhostname", but it breaks mDNS as resolved currently does not resolve
> mDNS names like "foo.local".
> 
> Please note, that
> 
>  a) This bug depends on the order of package installations. Installing 
> libnss-resolve *AFTER* everything else will avoid the problem.

Installing libnss-mdns, then libnss-resolve leads to

hosts:  files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] 
dns

Installing libnss-resolve, then libnss-mdns leads to

hosts:  files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] 
dns


So maybe the "obvious" fix is to change libnss-mdns to always insert itself
before dns *and* resolve? On the other hand, it's quite ugly that mdns needs to
be taught to cope with this new nss module.

Martin, Simon, what's your take on this?
With multiple packages mangling nsswitch.conf, this feels like it's becoming 
very brittle
and maybe we need a proper API like pam-auth-update.

Michael

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



signature.asc
Description: OpenPGP digital signature

Processed: unmerge

[Debian Bug Tracking System]

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

> unmerge 846671
Bug #846671 [artemis] artemis: FTBFS: BamView.java:115: error: cannot find 
symbol
Bug #846708 [artemis] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Disconnected #846671 from all other report(s).
> thanks
Stopping processing here.

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

Bug#846115: [DRE-maint] Bug#846115: Bug#846115: jekyll: FTBFS randomly (failing tests)

[Christian Hofstaedtler]

* Christian Hofstaedtler  [161208 14:09]:
> * Youhei SASAKI  [161208 12:57]:
> > On Mon, 28 Nov 2016 23:55:37 +0900,
> > Santiago Vila  wrote:
> > > Package: src:jekyll
> > > Version: 3.1.6+dfsg-3
> > >
> > > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > > (which is what the "Arch: all" autobuilder would do to build it)
> > > but it failed:
> > 
> > Hm... *I can't reproduce this bug*.
> 
> I just hit this on the first try, when doing:
> 
>   $ apt-get source jekyll -d
>   $ sbuild jekyll_3.1.6+dfsg-3.dsc -A -d unstable

So, this fails reliably for me in an unpacked source tree, by just
running:


$ SEED=23557 rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -I"lib:lib:test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb"
"test/test_ansi.rb" "test/test_cleaner.rb"
"test/test_coffeescript.rb" "test/test_collections.rb"
"test/test_command.rb" "test/test_commands_serve.rb"
"test/test_configuration.rb" "test/test_doctor_command.rb"
"test/test_document.rb" "test/test_entry_filter.rb"
"test/test_excerpt.rb" "test/test_excerpt_drop.rb"
"test/test_filters.rb" "test/test_front_matter_defaults.rb"
"test/test_generated_site.rb" "test/test_kramdown.rb"
"test/test_layout_reader.rb" "test/test_liquid_extensions.rb"
"test/test_liquid_renderer.rb" "test/test_log_adapter.rb"
"test/test_new_command.rb" "test/test_page.rb"
"test/test_path_sanitization.rb" "test/test_rdiscount.rb"
"test/test_redcarpet.rb" "test/test_regenerator.rb"
"test/test_related_posts.rb" "test/test_sass.rb" "test/test_site.rb"
"test/test_static_file.rb" "test/test_url.rb" "test/test_utils.rb"

(One long line.)

>From what I can tell, depending on the test execution order, the
"default_configuration" hash gets changed: it either has source set
to test/source or it's missing (then PWD is assumed).

Good luck,
-- 
christian hofstaedtler 

Bug#842093: [u...@kleine-koenig.org: Re: libupnp: CVE-2016-8863]

[Uwe Kleine-König]

Hello Marcelo,

I created a patch for CVE-2016-8863 but forgot to Cc: you. Do you care
to take a look?

Best regards
Uwe

- Forwarded message from Uwe Kleine-König  -

Date: Thu, 8 Dec 2016 14:20:32 +0100
From: Uwe Kleine-König 
To: Salvatore Bonaccorso 
Cc: 842...@bugs.debian.org
Subject: Re: libupnp: CVE-2016-8863
Message-ID: <20161208132027.idez435hu4jna...@perseus.defre.kleine-koenig.org>

Control: tag -1 + patch

Hello,

On Tue, Oct 25, 2016 at 10:27:24PM +0200, Salvatore Bonaccorso wrote:
> the following vulnerability was published for libupnp. The issue is
> reproducible easily if libupnp compiled with ASAN and following the
> reproducing steps in the upstream bugreport.

I didn't try to reproduce, but I think the following patch (while not
being pretty) is easy and fixes the issue:

diff --git a/upnp/src/gena/gena_device.c b/upnp/src/gena/gena_device.c
index 58a3e55e8973..700f00b449db 100644
--- a/upnp/src/gena/gena_device.c
+++ b/upnp/src/gena/gena_device.c
@@ -1145,7 +1145,11 @@ static int create_url_list(
 
 if( URLcount > 0 ) {
 out->URLs = malloc(URLS->size + 1);
-out->parsedURLs = malloc(sizeof(uri_type) * URLcount);
+   /*
+* You wonder why there is a +1? See
+* https://sourceforge.net/p/pupnp/bugs/133/
+*/
+out->parsedURLs = malloc(sizeof(uri_type) * (URLcount + 1));
 if (!out->URLs || !out->parsedURLs) {
 free(out->URLs);
 free(out->parsedURLs);

Best regards
Uwe



- End forwarded message -


signature.asc
Description: PGP signature

Bug#846019: pgadmin3: SIGABRT after fatal error complaint regarding libwxgtx ABI mismatch

[Christoph Berg]

Re: Björn Harrtell 2016-12-08 

Processed: Re: libupnp: CVE-2016-8863

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #842093 [src:libupnp] libupnp: CVE-2016-8863
Added tag(s) patch.

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

Bug#842093: libupnp: CVE-2016-8863

[Uwe Kleine-König]

Control: tag -1 + patch

Hello,

On Tue, Oct 25, 2016 at 10:27:24PM +0200, Salvatore Bonaccorso wrote:
> the following vulnerability was published for libupnp. The issue is
> reproducible easily if libupnp compiled with ASAN and following the
> reproducing steps in the upstream bugreport.

I didn't try to reproduce, but I think the following patch (while not
being pretty) is easy and fixes the issue:

diff --git a/upnp/src/gena/gena_device.c b/upnp/src/gena/gena_device.c
index 58a3e55e8973..700f00b449db 100644
--- a/upnp/src/gena/gena_device.c
+++ b/upnp/src/gena/gena_device.c
@@ -1145,7 +1145,11 @@ static int create_url_list(
 
 if( URLcount > 0 ) {
 out->URLs = malloc(URLS->size + 1);
-out->parsedURLs = malloc(sizeof(uri_type) * URLcount);
+   /*
+* You wonder why there is a +1? See
+* https://sourceforge.net/p/pupnp/bugs/133/
+*/
+out->parsedURLs = malloc(sizeof(uri_type) * (URLcount + 1));
 if (!out->URLs || !out->parsedURLs) {
 free(out->URLs);
 free(out->parsedURLs);

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#846115: [DRE-maint] Bug#846115: jekyll: FTBFS randomly (failing tests)

[Christian Hofstaedtler]

* Youhei SASAKI  [161208 12:57]:
> On Mon, 28 Nov 2016 23:55:37 +0900,
> Santiago Vila  wrote:
> > Package: src:jekyll
> > Version: 3.1.6+dfsg-3
> >
> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > (which is what the "Arch: all" autobuilder would do to build it)
> > but it failed:
> 
> Hm... *I can't reproduce this bug*.

I just hit this on the first try, when doing:

  $ apt-get source jekyll -d
  $ sbuild jekyll_3.1.6+dfsg-3.dsc -A -d unstable

Log attached.

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



jekyll_3.1.6+dfsg-3_amd64-2016-12-08T13:00:49Z.build.gz
Description: application/gunzip

Bug#847462: printer-driver-cups-pdf: make very ugly and uselss pdf which are not searchables

[Ferran Juanós]

Package: printer-driver-cups-pdf
Severity: grave
Justification: renders package unusable

Dear Maintainer,

It's not possible to make usable pdf, I have triyed to use the unstable version 
off the package and the result is the same



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

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