Andrew Patterson | 8 Jul 02:00 2015
Picon

Bug#778055: Patch for GCC 5 build issue

tags 778055 + patch
thanks

Here's a fix for the GCC 5 build issue.  It adds 'export CFLAGS =
-std=gnu89' to the rules file to use the GNU89 inline semantics.

I tested it with both gcc-5.0 and gcc-4.9.

--

-- 
Andrew Patterson
Hewlett-Packard

Attachment (fix-FTBFS-GCC5.patch): text/x-patch, 261 bytes
Andrew Patterson | 8 Jul 01:52 2015
Picon

Bug#778055: Patch for GCC 5 build issue

tags 778055 + patch

Here's a fix for the GCC 5 build issue.  It adds 'export CFLAGS =
-std=gnu89' to the rules file to use the GNU89 inline semantics.

I tested it with both gcc-5.0 and gcc-4.9.

--

-- 
Andrew Patterson
Hewlett-Packard

Attachment (fix-FTBFS-GCC5.patch): text/x-patch, 261 bytes
Andrew Patterson | 8 Jul 01:47 2015
Picon

Bug#778055: Patch for GCC 5 build issue

tags nnnn + patch

Here's a fix for the GCC 5 build issue.  It adds 'export CFLAGS =
-std=gnu89' to the rules file to use the GNU89 inline semantics.

I tested it with both gcc-5.0 and gcc-4.9.

--

-- 
Andrew Patterson
Hewlett-Packard
Attachment (fix-FTBFS-GCC5.patch): text/x-patch, 260 bytes
Luke Pascoe | 8 Jul 01:00 2015
Picon

Bug#771241: Could someone explain why this fix is still not available for Stable/Jessie?

This is a serious issue which makes stunnel unusable in many configurations, why has it not been backported into 8.0?

Luke Pascoe



E luke <at> osnz.co.nz
P +64 (9) 296 2961
M +64 (27) 426 6649
W www.osnz.co.nz

24 Wellington St
Papakura
Auckland, 2110
New Zealand

Jeremy Lainé | 8 Jul 00:24 2015

Bug#791729: What version of systemsettings?

Hi Diederik,

What version of systemsettings are you running?

Cheers,
Jeremy

Chris West (Faux | 8 Jul 00:21 2015

Bug#791731: FTBFS: ld.bfd: cannot find -lX11, -lgdk, -lpango, -lcairo, -latk etc.

Source: cqrlog
Version: 1.9.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds <at> lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build:

/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
/usr/bin/ld.bfd: cannot find -lX11
/usr/bin/ld.bfd: cannot find -lgdk_pixbuf-2.0
/usr/bin/ld.bfd: cannot find -lgtk-x11-2.0
/usr/bin/ld.bfd: cannot find -lgdk-x11-2.0
/usr/bin/ld.bfd: cannot find -lgobject-2.0
/usr/bin/ld.bfd: cannot find -lglib-2.0
/usr/bin/ld.bfd: cannot find -lgthread-2.0
/usr/bin/ld.bfd: cannot find -lgmodule-2.0
/usr/bin/ld.bfd: cannot find -lpango-1.0
/usr/bin/ld.bfd: cannot find -lcairo
/usr/bin/ld.bfd: cannot find -latk-1.0
/usr/bin/ld.bfd: cannot find -lpangocairo-1.0
cqrlog.lpr(63,1) Error: Error while linking
cqrlog.lpr(63,1) Fatal: There were 1 errors compiling module, stopping
ERROR: failed compiling of project /tmp/buildd/cqrlog-1.9.0/src/cqrlog.lpi
Makefile:9: recipe for target 'cqrlog' failed
make[1]: *** [cqrlog] Error 2

The error looks suspiciously similar to https://bugs.debian.org/791407 , which has been fixed manually.

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

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

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

Diederik de Haas | 8 Jul 00:18 2015

Bug#791729: kde-config-gtk-style: Upgrading to version 4:5.3.2-1 makes it not work anymore

Package: kde-config-gtk-style
Version: 4:5.3.2-1
Severity: grave
Justification: renders package unusable

When I upgraded this package to 4:5.3.2-1 it disappeared from System
Settings.
I then did a downgrade to the version in testing and it came back. While
keeping System Settings -> Application Appearance open and then after the 
upgrade selecting 'GTK' again, I saw the following error message:
=====================================================================
Could not find plugin 'GTK' for application 'systemsettings'Library
"kcm_cgc" not found
=====================================================================

At the bottom of the screen I got the following text:
=====================================================================
Possible reasons:
- An error occurred during your last KDE upgrade leaving an orphaned
  control module
- You have old third party modules lying around.

Check these points carefully and try to remove the module mentioned in
the error message. If this fails, consider contacting your distributor
or packager.
=====================================================================

My guess is that it's missing one of more dependencies.

Let me know if you need more info.

Regards,
  Diederik

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

Kernel: Linux 4.0.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 kde-config-gtk-style depends on:
ii  libc6                 2.19-18
ii  libgtk2.0-0           2.24.28-1
ii  libkf5archive5        5.11.0-2
ii  libkf5configwidgets5  5.11.0-1
ii  libkf5coreaddons5     5.11.0-1
ii  libkf5i18n5           5.11.0-1
ii  libkf5iconthemes5     5.11.0-1
ii  libkf5kiocore5        5.11.0-2
ii  libkf5kiowidgets5     5.11.0-2
ii  libkf5newstuff5       5.11.0-1
ii  libkf5widgetsaddons5  5.11.0-2
ii  libqt5core5a          5.4.2+dfsg-4
ii  libqt5gui5            5.4.2+dfsg-4
ii  libqt5widgets5        5.4.2+dfsg-4
ii  libstdc++6            5.1.1-13

kde-config-gtk-style recommends no packages.

Versions of packages kde-config-gtk-style suggests:
pn  kde-config-gtk-style-preview  <none>

-- no debconf information

Thomas Goirand | 7 Jul 23:54 2015
Picon

Bug#788561: Bug RC #788561 (python3-memcache not Python 3 compatible)


On 07/06/2015 01:10 AM, Hugo Lefeuvre wrote:
> Hi Thomas,
> 
>> This has already been done in Sid, and therefore, it is my opinion that
>> we should have one of the below action:
>> 1/ Remove support for Py3 in Jessie, and ask the release team to approve
>> that. I do believe that they will accept this.
>> 2/ Ask for the release team to accept an update to the package version
>> which is in Sid. It's very unlikely that they accept.
>>
>> If you want to work on one of these, it'd be great. But dealing with the
>> release team for doing this type of fix in stable is famously difficult
>> because:
>> 1/ They are very busy
>> 2/ They don't accept often big changes in already existing package, and
>> you need to convince them.
>>
>> Both are very valid reasons and I don't blame the release team for that.
> 
> I'd be glad to try to help you to fix this bug.
> 
> I agree with the fact that it will be quite difficult to update Jessie
> with the version currently in Sid. A lot of changes have been made 
> between 1.53 and 1.54; it will be really hard to prove that this new 
> version won't introduce new bugs. 
> 
> So, the first solution seems to be much easier. Moreover, according to 
> memcache's popcon[0], python3-memcache isn't downloaded a lot. So, it 
> won't be prolematic to remove this package in Jessie, at least for the 
> moment.
> 
> Naturally, I think it's sad to lose memcache's Python 3 support on Jessie, 
> but we must fix this bug, and the first solution seems to be the only 
> realistic solution.
> 
> Maybe that we could try to ask the release team for the second solution,
> and, if they do not accept, ask them for the first solution ?

Yes, that's the way to go. I think it's better to go directly for the
removal of python3-memcached in fact.

> #788561 is now marked as fixed in 1.54+20150423+git+48e882719c-2. Is it
> enough ?

I believe so, yes.

Cheers,

Thomas Goirand (zigo)

Emilio Pozuelo Monfort | 7 Jul 23:43 2015
Picon

Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

Package: node-mapnik
Version: 1.2.3-1
Severity: serious

Your package fails to build against mapnik 3.0.0:

In file included from ../src/node_mapnik.cpp:25:0:
.../src/mapnik_image_view.hpp:7:61: fatal error: mapnik/image_data.hpp: No such file or directory
 #include <mapnik/image_data.hpp>        // for image_data_32
                                                             ^
compilation terminated.

Full logs at https://buildd.debian.org/status/logs.php?pkg=node-mapnik&ver=1.2.3-1%2Bb2

Emilio

Debian Bug Tracking System | 7 Jul 23:27 2015
Picon

Processed: Merge identical systemsettings5 bugs

Processing commands for control <at> bugs.debian.org:

> severity 791699 normal
Bug #791699 [systemsettings] systemsettings: have an empty window
Severity set to 'normal' from 'important'
> severity 790703 normal
Bug #790703 [systemsettings] systemsettings: Completely unusable
Severity set to 'normal' from 'grave'
> severity 791606 normal
Bug #791606 [systemsettings] systemsettings unable to find views quits right after start
Severity set to 'normal' from 'grave'
> merge 791699 790703 791606
Bug #791699 [systemsettings] systemsettings: have an empty window
Bug #790703 [systemsettings] systemsettings: Completely unusable
Marked as found in versions systemsettings/4:5.3.2-2.
Bug #791606 [systemsettings] systemsettings unable to find views quits right after start
Marked as found in versions systemsettings/4:5.3.1-1.
Bug #791699 [systemsettings] systemsettings: have an empty window
Marked as found in versions systemsettings/4:5.3.1-1.
Merged 790703 791606 791699
> thanks
Stopping processing here.

Please contact me if you need assistance.
--

-- 
790703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790703
791606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791606
791699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791699
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems

Salvatore Bonaccorso | 7 Jul 21:59 2015
Picon

Bug#791715: bind9: CVE-2015-4620: Specially Constructed Zone Data Can Cause a Resolver to Crash when Validating

Source: bind9
Version: 1:9.7.3.dfsg-1
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole
Control: fixed -1 1:9.9.5.dfsg-9+deb8u1

Hi,

the following vulnerability was published for bind9.

CVE-2015-4620[0]:
Specially Constructed Zone Data Can Cause a Resolver to Crash when Validating

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-2015-4620
[1] https://kb.isc.org/article/AA-01267

Regards,
Salvatore


Gmane