Bug#778151: Patch for GCC5 build error
tags 778151 + patch
thanks
Here's a fix for the GCC 5 build issue. I added extern to
inline function in render.c. The package builds and links with GCC 5
with this change.
Upstream may prefer to move to C99 instead, please see section
Different semantics for inline functions at
https://gcc.gnu.org/gcc-5/porting_to.html for more background.
--
Nicholas Luedtke
Linux for HP Helion OpenStack, Hewlett-Packard
Description: Fixes GCC5 build error
TODO: ADD extern to put_pixel to conform to the gnu99 std.
.
tuxonice-userui (1.1+dfsg1.gc3bdd83-3.1) UNRELEASED; urgency=medium
.
* Non-maintainer upload.
* Fixed GCC5 build error.
Author: Nicholas Luedtkenicholas.lued...@hp.com
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: vendor|upstream|other, url of original patch
Bug: url in upstream bugtracker
Bug-Debian: https://bugs.debian.org/bugnumber
Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
Forwarded: no|not-needed|url proving that it has been forwarded
Reviewed-By: name and email of someone who approved the patch
Last-Update: -MM-DD
--- tuxonice-userui-1.1+dfsg1.gc3bdd83.orig/fbsplash/render.c
+++ tuxonice-userui-1.1+dfsg1.gc3bdd83/fbsplash/render.c
@@ -45,7 +45,7 @@ void render_icon(icon *ticon, u8 *target
}
}
-inline void put_pixel (u8 a, u8 r, u8 g, u8 b, u8 *src, u8 *dst, u8 add)
+extern inline void put_pixel (u8 a, u8 r, u8 g, u8 b, u8 *src, u8 *dst, u8 add)
{
if (fb_opt) {
if (a != 255) {
Processed: Patch for GCC5 build error
Processing commands for cont...@bugs.debian.org: tags 778151 + patch Bug #778151 [src:tuxonice-userui] tuxonice-userui: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789348: marked as done (mate-applets: Unable to install mate-applets because of a file conflict in mate-applets-common)
Your message dated Fri, 17 Jul 2015 12:50:00 +
with message-id e1zg55u-0006sr...@franck.debian.org
and subject line Bug#789348: fixed in mate-applets 1.10.3+dfsg1-1~exp2
has caused the Debian Bug report #789348,
regarding mate-applets: Unable to install mate-applets because of a file
conflict in mate-applets-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.)
--
789348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: mate-applets
Version: 1.10.0+dfsg1-1~exp1
Justification: renders package unusable
Severity: grave
Dear Maintainer,
I was trying to install mate-applets when ran into this :-
[$] sudo aptitude install mate-applets=1.10.0+dfsg1-1~exp1
mate-applets-common=1.10.0+dfsg1-1~exp1
The following packages will be upgraded:
mate-applets mate-applets-common
The following partially installed packages will be configured:
mate-sensors-applet{b}
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 965 kB of archives. After unpacking 387 kB will be freed.
The following packages have unmet dependencies:
mate-sensors-applet : Depends: mate-sensors-applet-common (=
1.10.1+dfsg1-1~exp1) but it is not going to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) mate-sensors-applet
Accept this solution? [Y/n/q/?] Y
The following packages will be REMOVED:
libmate-sensors-applet-plugin0{u} mate-sensors-applet{a}
The following packages will be upgraded:
mate-applets mate-applets-common
2 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 965 kB of archives. After unpacking 668 kB will be freed.
Do you want to continue? [Y/n/?] Y
Get: 1 http://httpredir.debian.org//debian/ experimental/main
mate-applets amd64 1.10.0+dfsg1-1~exp1 [221 kB]
Get: 2 http://httpredir.debian.org//debian/ experimental/main
mate-applets-common all 1.10.0+dfsg1-1~exp1 [743 kB]
Fetched 965 kB in 12s (78.9 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
apt-listchanges: Mailing root: apt-listchanges: changelogs for debian
D01: ensure_diversions: new, (re)loading
D01: process queue pkg mate-sensors-applet:amd64 queue.len 1
progress 1, try 1
D01: deferred_remove package mate-sensors-applet:amd64
D01: checking dependencies for remove 'mate-sensors-applet:amd64'
(Reading database ... 918842 files and directories currently installed.)
Removing mate-sensors-applet (1.10.1+dfsg1-1~exp1) ...
D01: removal_bulk package mate-sensors-applet:amd64
D01: ensure_diversions: same, skipping
D01: removal_bulk cleaning info directory
D01: removal_bulk purging? foundpostrm=1
D01: removal done
D01: process queue pkg libmate-sensors-applet-plugin0:amd64
queue.len 0 progress 1, try 1
D01: deferred_remove package libmate-sensors-applet-plugin0:amd64
D01: checking dependencies for remove 'libmate-sensors-applet-plugin0:amd64'
Removing libmate-sensors-applet-plugin0 (1.10.1+dfsg1-1~exp1) ...
D01: removal_bulk package libmate-sensors-applet-plugin0:amd64
D01: ensure_diversions: same, skipping
D01: removal_bulk cleaning info directory
D01: removal_bulk purging? foundpostrm=1
D01: removal done
Processing triggers for libc-bin (2.19-18) ...
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
D01: ensure_diversions: new, (re)loading
D01: ensure_statoverrides: new, (re)loading
(Reading database ... 918807 files and directories currently installed.)
Preparing to unpack .../mate-applets_1.10.0+dfsg1-1~exp1_amd64.deb ...
D01: process_archive oldversionstatus=installed
Unpacking mate-applets (1.10.0+dfsg1-1~exp1) over (1.8.1+dfsg1-3) ...
D01: process_archive updating info directory
D01: generating infodb hashfile
Preparing to unpack .../mate-applets-common_1.10.0+dfsg1-1~exp1_all.deb ...
D01: process_archive oldversionstatus=installed
Unpacking mate-applets-common (1.10.0+dfsg1-1~exp1) over (1.8.1+dfsg1-3) ...
dpkg: error processing archive
/var/cache/apt/archives/mate-applets-common_1.10.0+dfsg1-1~exp1_all.deb
(--unpack):
trying to overwrite
'/usr/share/dbus-1/services/org.mate.panel.applet.DriveMountAppletFactory.service',
which is also in package mate-applets 1.10.0+dfsg1-1~exp1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for dbus (1.9.16-2) ...
D01: ensure_diversions: same, skipping
Processing triggers
Bug#792617: marked as done (elasticsearch: CVE-2015-5377 CVE-2015-5531)
Your message dated Fri, 17 Jul 2015 12:19:00 + with message-id e1zg4bu-00071f...@franck.debian.org and subject line Bug#792617: fixed in elasticsearch 1.6.1+dfsg-1 has caused the Debian Bug report #792617, regarding elasticsearch: CVE-2015-5377 CVE-2015-5531 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.) -- 792617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: elasticsearch Version: 1.0.3+dfsg-5 Severity: grave Tags: security upstream fixed-upstream Justification: user security hole Hi, the following vulnerabilities were published for elasticsearch. Reporting them right now as severity grave since some details are missed so feel free to downgrade. CVE-2015-5377[0]: Remote code execution vulnerability CVE-2015-5531[1]: Directory traversal vulnerability If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-5377 [1] https://security-tracker.debian.org/tracker/CVE-2015-5531 [2] https://www.elastic.co/blog/elasticsearch-1-7-0-and-1-6-1-released#security Regards, Salvatore ---End Message--- ---BeginMessage--- Source: elasticsearch Source-Version: 1.6.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of elasticsearch, 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 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated elasticsearch 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, 17 Jul 2015 13:18:00 +0200 Source: elasticsearch Binary: libelasticsearch1.6-java elasticsearch Architecture: source all Version: 1.6.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: elasticsearch - Open Source, Distributed, RESTful Search Engine libelasticsearch1.6-java - Open Source, Distributed, RESTful Search Engine -- libraries Closes: 792617 Changes: elasticsearch (1.6.1+dfsg-1) unstable; urgency=medium . * Team upload. * New upstream version - This fixes CVE-2015-5377 CVE-2015-5531 (Closes: #792617) Checksums-Sha1: 1eb21f5295e08033c8cd5df18261fbbc31f8eb46 2733 elasticsearch_1.6.1+dfsg-1.dsc c1f34cc1779b847128fabd0e1ba9e5945f96139c 9295720 elasticsearch_1.6.1+dfsg.orig.tar.xz 1cddae2da97901e7b550a7e7efa31c12219fdf0c 9492 elasticsearch_1.6.1+dfsg-1.debian.tar.xz 4852f5c97092e81864886a911cf9796bce9704ce 18576 elasticsearch_1.6.1+dfsg-1_all.deb 6c40cf27821aa3b8e69498cdeb7fcd9e840197f6 12168804 libelasticsearch1.6-java_1.6.1+dfsg-1_all.deb Checksums-Sha256: 30a43f8da4c436d00f382de51df795b640fd2165abf63658b9dac303457d5388 2733 elasticsearch_1.6.1+dfsg-1.dsc e00c88f0d516797778058dffe306180933471fda9897d7295440876c352421fa 9295720 elasticsearch_1.6.1+dfsg.orig.tar.xz b5c358503040706ebfc1ef74daf4c88fac5210dd194ed76b44930488eb8a0015 9492 elasticsearch_1.6.1+dfsg-1.debian.tar.xz f0312af5d526b11560b6e12ac9e5cebcb5160acddbc60f3c9e334202c5882672 18576 elasticsearch_1.6.1+dfsg-1_all.deb e2d028ef300ebc61fff22264a377e4b6318a28c45d8487d4e9ba04e2ee21675a 12168804 libelasticsearch1.6-java_1.6.1+dfsg-1_all.deb Files: 9e4ae87dbb84d9ff0757c39e01993630 2733 database optional elasticsearch_1.6.1+dfsg-1.dsc 32d2d21a8c58609bff401fe776e94f97 9295720 database optional elasticsearch_1.6.1+dfsg.orig.tar.xz b80dd3df43b32946fab33567abec82e2 9492 database optional elasticsearch_1.6.1+dfsg-1.debian.tar.xz d1f0532149ed346d12752dce689372f7 18576 database optional elasticsearch_1.6.1+dfsg-1_all.deb b7d5d6b7598ff4a759917e0fdad2a355 12168804 java optional libelasticsearch1.6-java_1.6.1+dfsg-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqO7EAAoJEHW3EGNcITp+F2gP/ilNwPQPTfFvjGeuSSYYpP0q 1qZWIZZZ4R517TjPDa4eryWkRzqiSUJlJNwXMqz6HltX5Y0BBlm2+kgrTmaZzQFD 35zhnLSXb9T8+27yqpKkNWHryJGoYVtHFUEg5HEeQ8mIMiEYFSQyOS3ohKRnrT+j
Processed: Bug#789348 marked as pending
Processing commands for cont...@bugs.debian.org: tag 789348 pending Bug #789348 [mate-applets] mate-applets: Unable to install mate-applets because of a file conflict in mate-applets-common Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 789348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789348: marked as pending
tag 789348 pending thanks Hello, Bug #789348 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-mate/mate-applets.git;a=commitdiff;h=3c2bb27 --- commit 3c2bb276ba157ac5b47ea8c228d4429db7bd040f Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de Date: Fri Jul 17 14:41:41 2015 +0200 upload to experimental (debian/1.10.3+dfsg1-1~exp2) diff --git a/debian/changelog b/debian/changelog index 5827725..3b049be 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +mate-applets (1.10.3+dfsg1-1~exp2) experimental; urgency=medium + + * debian/mate-applets-common.install: ++ Don't ship /etc files in mate-applets-common. (Closes: #789348). + + -- Mike Gabriel sunwea...@debian.org Fri, 17 Jul 2015 14:35:06 +0200 + mate-applets (1.10.3+dfsg1-1~exp1) experimental; urgency=medium * New upstream release. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788095: can't load pygit2: PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/$
Followup-For: Bug #788095 Package: python-pygit2 Version: 0.22.0-3 Dear Maintainer, It looks like this issue is still present in 0.22.0-3. I get the following error messages when attempting to import the module: $ python -c 'import pygit2' Traceback (most recent call last): File string, line 1, in module File /usr/lib/python2.7/dist-packages/pygit2/__init__.py, line 35, in module from .blame import Blame, BlameHunk File /usr/lib/python2.7/dist-packages/pygit2/blame.py, line 32, in module from .errors import check_error File /usr/lib/python2.7/dist-packages/pygit2/errors.py, line 29, in module from .ffi import ffi, C File /usr/lib/python2.7/dist-packages/pygit2/ffi.py, line 35, in module ffi, C = get_ffi() File /usr/lib/python2.7/dist-packages/pygit2/_utils.py, line 101, in get_ffi include_dirs=[libgit2_include], library_dirs=[libgit2_lib]) File /usr/lib/python2.7/dist-packages/cffi/api.py, line 373, in verify lib = self.verifier.load_library() File /usr/lib/python2.7/dist-packages/cffi/verifier.py, line 95, in load_library self._write_source() File /usr/lib/python2.7/dist-packages/cffi/verifier.py, line 183, in _write_source with open(self.sourcefilename, w) as fp: IOError: [Errno 2] No such file or directory: '/usr/lib/python2.7/dist-packages/pygit2/__pycache__/pygit2_cffi_ab5e9344x5470904.c' $ python3 -c 'import pygit2' Traceback (most recent call last): File string, line 1, in module File /usr/lib/python3/dist-packages/pygit2/__init__.py, line 35, in module from .blame import Blame, BlameHunk File /usr/lib/python3/dist-packages/pygit2/blame.py, line 32, in module from .errors import check_error File /usr/lib/python3/dist-packages/pygit2/errors.py, line 29, in module from .ffi import ffi, C File /usr/lib/python3/dist-packages/pygit2/ffi.py, line 35, in module ffi, C = get_ffi() File /usr/lib/python3/dist-packages/pygit2/_utils.py, line 101, in get_ffi include_dirs=[libgit2_include], library_dirs=[libgit2_lib]) File /usr/lib/python3/dist-packages/cffi/api.py, line 373, in verify lib = self.verifier.load_library() File /usr/lib/python3/dist-packages/cffi/verifier.py, line 95, in load_library self._write_source() File /usr/lib/python3/dist-packages/cffi/verifier.py, line 183, in _write_source with open(self.sourcefilename, w) as fp: PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/pygit2/__pycache__/pygit2_cffi_1b714a1x5470904.c' The same bug also shows up in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/python-pygit2/+bug/1475431 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core) 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 python-pygit2 depends on: ii dpkg 1.18.1 ii libc62.19-19 ii libgit2-22 0.22.2-2 ii python 2.7.9-1 ii python-cffi 1.1.2-1 pn python:any none python-pygit2 recommends no packages. Versions of packages python-pygit2 suggests: pn python-pygit2-doc none -- no debconf information -- mvh / best regards Hans Joachim Desserud http://desserud.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792361: redmine: dpkg --configure broken when installing ruby packages
Hi, 2015-07-17 9:51 GMT+02:00 Pirate Praveen prav...@onenetbeyond.org: ... Can this be even made a policy? If a single application is blocking a library update the older version can be embedded in that application. Does not sound like a good idea. It is also against Debian Policy. Working with upstream to help them in migrating to the latest versions of their dependencies is the established and proper way to go. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: Unable to upgrade from wheezy to jessie
package: s3ql
severity: grave
version: 2.11.1+dfsg-1
Justification: Renders filesystem unusable and data accessible
Hi.
I'm upgrading a system from wheezy to jessie.
Wheezy ships s3ql 1.11, jessie ships version 2.11.
I have a filesystem that I can easily mount and fsck in wheezy, but when
I try to run the jessie s3qladm upgrade command I get:
Getting file system parameters..
File system revision too old to upgrade!
You need to use an older S3QL version to upgrade to a more recent
revision before you can use this version to upgrade to the newest
revision.
Uncaught top-level exception:
Traceback (most recent call last):
File /usr/bin/s3qladm, line 9, in module
load_entry_point('s3ql==2.11.1', 'console_scripts', 's3qladm')()
File /usr/lib/s3ql/s3ql/adm.py, line 96, in main
options.cachedir))
File /usr/lib/s3ql/s3ql/adm.py, line 316, in upgrade
print(get_old_rev_msg(param['revision'] + 1, 's3qladm'))
File /usr/lib/s3ql/s3ql/adm.py, line 224, in
get_old_rev_msg
''' % { 'version': REV_VER_MAP[rev],
KeyError: 17
It's critical that there be a documented procedure that works for
upgrading from the version in wheezy to the version in jessie using
tools in jessie.
There was another upgrade at version 2.5, which is not in either wheezy
or jessie. However, it needs to be possible to upgrade from one Debian
release to the next using the software in Debian.
I believe this problem is important enough to fix in a Jessie point
release and would be happy to help with any process issues that come up
in making that happen.
pgpqzly9nonTg.pgp
Description: PGP signature
Bug#791574: strip-nondeterminism: failure in zip.pm, breaking package builds
Hi, I tried to reproduce this problem but was unable to reproduce it in a pbuilder environment. Are any specific build options needed to reproduce this (since in my build log dh_strip_nondeterminism -O--parallel is not even called: ... dh_link -O--parallel debian/rules override_dh_compress ... Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784565: marked as done (nx-libs-lite: parts are derived from non-free code)
Your message dated Fri, 17 Jul 2015 13:00:23 + with message-id e1zg5fx-00032o...@franck.debian.org and subject line Bug#784565: fixed in nx-libs-lite 3.5.0.32-1 has caused the Debian Bug report #784565, regarding nx-libs-lite: parts are derived from non-free code 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.) -- 784565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nx-libs-lite Version: 3.5.0.27-1 Severity: serious Justification: Policy 2.2.1 Hello and thanks for maintaining this package in Debian! I noticed that the debian/copyright states: [...] | Parts of this software are derived from DXPC project. These copyright | notices apply to original DXPC code: | |Redistribution and use in source and binary forms are permitted provided |that the above copyright notice and this paragraph are duplicated in all |such forms. | |THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED |WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF |MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. | |Copyright (c) 1995,1996 Brian Pane |Copyright (c) 1996,1997 Zachary Vonler and Brian Pane |Copyright (c) 1999 Kevin Vigor and Brian Pane |Copyright (c) 2000,2001 Gian Filippo Pinzari and Brian Pane [...] This license lacks the permission to modify the DXPC code. Hence, the original DXPC code does not appear to comply with the DFSG. And the nx-libs-lite is in part derived from DXPC code. This basically means that nx-libs-lite includes parts which are non-free (as they are derived from non-modifiable code) and are also possibly legally undistributable (as they are non-modifiable, but actually modified). The combination with the rest of nx-libs-lite (which is GPL-licensed) may also be legally undistributable (since the license with no permission to modify is GPL-incompatible). If there's anything I misunderstood, please clarify. Otherwise, please address this issue as soon as possible. The copyright owners for the original DXPC code should be contacted and persuaded to re-license under GPL-compatible terms. Thanks for your time. Bye. ---End Message--- ---BeginMessage--- Source: nx-libs-lite Source-Version: 3.5.0.32-1 We believe that the bug you reported is fixed in the latest version of nx-libs-lite, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel sunwea...@debian.org (supplier of updated nx-libs-lite 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, 16 Jul 2015 08:00:43 +0200 Source: nx-libs-lite Binary: nxproxy nxproxy-dbg libxcomp3 libxcomp-dev libxcomp3-dbg Architecture: source amd64 Version: 3.5.0.32-1 Distribution: unstable Urgency: medium Maintainer: X2Go Packaging Team pkg-x2go-de...@lists.alioth.debian.org Changed-By: Mike Gabriel sunwea...@debian.org Description: libxcomp-dev - NX X compression library headers libxcomp3 - NX X compression library libxcomp3-dbg - nx-X11 compression library (debug package) nxproxy- NX proxy nxproxy-dbg - NX proxy (debug package) Closes: 784565 Changes: nx-libs-lite (3.5.0.32-1) unstable; urgency=medium . * New upstream release. * debian/libxcomp3.docs: + Add README.on-retroactive-DXPC-license to bin:package libxcomp3. Document retroactive DXPC relicensing process in May 2015. (Closes: #784565). * debian/control: + Don't use subfolder x2go/ on Alioth's collab-maint anymore. + Bump Standards: to 3.9.6. No changes needed. + Turn into multi-arch package. + Add debug bin:packages. * debian/rules: + Add get-orig-source rule. + Harden the build process. + Use doc/changelog as upstream changelog. * debian/rules, debian/*.install: + Use upstream's Makefile install rule to install files into the bin:packages. * debian/watch: + Adapt to new file name pattern used for upstream tarball (underscore - dash). * debian/copyright: + Update license information for DXPC
Bug#789346: marked as pending
tag 789346 pending thanks Hello, Bug #789346 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-mate/mate-sensors-applet.git;a=commitdiff;h=fffea71 --- commit fffea71fbbf68f326150cce7e8e5237cfcf65ca0 Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de Date: Sun Jun 21 17:07:19 2015 +0200 upload to experimental (debian/1.10.1+dfsg1-1~exp2) diff --git a/debian/changelog b/debian/changelog index d2be2b5..2224443 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +mate-sensors-applet (1.10.1+dfsg1-1~exp2) experimental; urgency=medium + + * debian/control: ++ Fix Breaks:/Replaces: version (mate-sensors-applet-common) + mate-sensors-applet ( 1.9.0) instead of ( 1.8.0). (Closes: + #789346). + + -- Mike Gabriel sunwea...@debian.org Sun, 21 Jun 2015 17:03:07 +0200 + mate-sensors-applet (1.10.1+dfsg1-1~exp1) experimental; urgency=low [ Martin Wimpress ] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777778: aptitude: ftbfs with GCC-5
reopen 78 thanks this fails later, once xapian and cwidget are built using GCC 5. Making all in matching make[6]: Entering directory '/scratch/packages/tmp/aptitude-0.6.11/build-arch/src/generic/apt/matching' g++ -DLOCALEDIR=\/usr/share/locale\ -DHAVE_CONFIG_H -I. -I../../../../../src/generic/apt/matching -I../../../.. -I../../../.. -I../../../../../src/generic/apt/matching -I../../../../.. -I../../../../../src -D_FORTIFY_SOURCE=2 -I/usr/include -DHELPDIR=\/usr/share/aptitude\ -DPKGDATADIR=\/usr/share/aptitude\ -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -O2 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -D_REENTRANT -fno-strict-aliasing -Wall -c -o parse.o ../../../../../src/generic/apt/matching/parse.cc In file included from ../../../../../src/generic/util/immset.h:31:0, from ../../../../../src/generic/apt/matching/parse.cc:54: ../../../../../src/generic/util/compare3.h:294:62: error: template argument 1 is invalid class compare3_fstd::basic_stringcharT, traits, Alloc ^ ../../../../../src/generic/util/compare3.h:332:42: error: template argument 1 is invalid class compare3_fstd::listT, Alloc ^ ../../../../../src/generic/util/compare3.h:333:57: error: template argument 1 is invalid : public compare3_f_containerstd::listT, Alloc ^ Makefile:405: recipe for target 'parse.o' failed make[6]: *** [parse.o] Error 1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#789346 marked as pending
Processing commands for cont...@bugs.debian.org:
tag 789346 pending
Bug #789346 {Done: Mike Gabriel sunwea...@debian.org} [mate-sensors-applet]
mate-sensors-applet: Cannot install mate-sensors-applet-common because a .mo
file is also present in mate-sensors-applet
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
789346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#777778: aptitude: ftbfs with GCC-5
Processing commands for cont...@bugs.debian.org:
reopen 78
Bug #78 {Done: Martin Michlmayr t...@hp.com} [src:aptitude] aptitude:
ftbfs with GCC-5
Bug reopened
Ignoring request to alter fixed versions of bug #78 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: FTBFS: Error in ruby2.1: munmap_chunk(): invalid pointer
Processing control commands: tags -1 unreproducible moreinfo Bug #791768 [src:ruby-bert] FTBFS: Error in ruby2.1: munmap_chunk(): invalid pointer Added tag(s) unreproducible and moreinfo. severity -1 important Bug #791768 [src:ruby-bert] FTBFS: Error in ruby2.1: munmap_chunk(): invalid pointer Severity set to 'important' from 'serious' -- 791768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791768: FTBFS: Error in ruby2.1: munmap_chunk(): invalid pointer
Control: tags -1 unreproducible moreinfo
Control: severity -1 important
Hi Christian,
On Wed, 08 Jul 2015 12:57:05 +0200 Christian Hofstaedtler
z...@debian.org wrote:
Source: ruby-bert
Version: 1.1.6-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
your package FTBFS, but built in the past.
Relevant snippet from the build log:
RUBYLIB=/«PKGBUILDDIR»/debian/ruby-bert/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0:/«PKGBUILDDIR»/debian/ruby-bert/usr/lib/ruby/vendor_ruby:.
ruby2.1 -ryaml -e YAML.load_file\(\debian/ruby-test-files.yaml\\).each\
\{\ \|f\|\ require\ f\ \}
*** Error in `ruby2.1': munmap_chunk(): invalid pointer: 0x7fcf31e78e30
***
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:115:in `exit': no implicit
conversion from nil to integer (TypeError)
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:115:in
`run_ruby'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:162:in
`do_run_tests'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:69:in
`run_tests'
from /usr/bin/gem2deb-test-runner:53:in `main'
ERROR: Test ruby2.1 failed. Exiting.
I could not reproduce the issue in a clean unstable chroot using sbuild
today by building the package three times.
I see similar crashes on sparc and ppc64 [1] thus the problem may not
appear all the time or is in a build-depenency. I'm decreasing severity
for now, but I'm also checking if Valgrind finds something during the build.
Cheers,
Balint
[1] https://buildd.debian.org/status/package.php?p=ruby-bertsuite=unstable
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792656: mirage: fails to install: mirage.postinst: update-desktop-database: not found
Package: mirage Version: 0.9.5.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Setting up mirage (0.9.5.1-4) ... /var/lib/dpkg/info/mirage.postinst: 20: /var/lib/dpkg/info/mirage.postinst: update-desktop-database: not found dpkg: error processing package mirage (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: mirage cheers, Andreas mirage_0.9.5.1-4.log.gz Description: application/gzip
Bug#792361: redmine: dpkg --configure broken when installing ruby packages
On Thursday 16 July 2015 10:58 PM, Antonio Terceiro wrote: Can I upload ruby-jquery-rails3 to fix the situation? this would remedy the original problem temporarily, but will create another one. It took us more than 1.5 years to get rid of ruby-rack1.4¹ ¹ https://tracker.debian.org/pkg/ruby-rack1.4 I would rather revert ruby-jquery-rails to the previous version using an upstream version number such as 4.0.4.REALLY.3.1.2, and work on doing a _planned_ update of all of these moving parts, staging the changes in experimental and being sure of what we are doing before doing it in unstable. Or would be better if we embed jquery-rails 3 with redmine like we did bootstrap-sass 2 for diaspora? Since we will need jquery-rails sometime soon. Can this be even made a policy? If a single application is blocking a library update the older version can be embedded in that application. signature.asc Description: OpenPGP digital signature
Processed (with 2 errors): Re: Bug#789348: fixed in mate-applets 1.10.0+dfsg1-1~exp2
Processing control commands:
found -1 1.10.3+dfsg1-1~exp1
Bug #789348 {Done: Mike Gabriel sunwea...@debian.org} [mate-applets]
mate-applets: Unable to install mate-applets because of a file conflict in
mate-applets-common
Marked as found in versions mate-applets/1.10.3+dfsg1-1~exp1 and reopened.
user debian...@lists.debian.org
Unknown command or malformed arguments to command.
usertag -1 piuparts
Unknown command or malformed arguments to command.
--
789348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792655: Further details on 792655
I cleared configuration files and reinstalled all packages. The daemon is reproducibly crashing when I access the CUPS configuration page on port 631 AND if the folder /etc/cups/ssl exists. If the folder doesn't exist, it does not crash but does also not work properly here. System log shows lines like cupsd[24851]: segfault at fada0245 ip b7676614 sp bff7aa60 error 7 in libgnutls-deb0.so.28.41.0[b75c2000+13a000] I believe that this is a linking problem, was it linked against the correct version of the libgnutls library? I remember that this worked after the upgrade to Debian 8, so could the be a defective security update? smime.p7s Description: S/MIME Cryptographic Signature
Bug#792659: tesseract-ocr-dev: fails to install, trying to overwrite other packages files: /usr/share/tesseract-ocr/language-specific.sh
Package: tesseract-ocr-dev Version: 3.04.00-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package tesseract-ocr-dev. (Reading database ... (Reading database ... 7610 files and directories currently installed.) Preparing to unpack .../tesseract-ocr-dev_3.04.00-3_all.deb ... Unpacking tesseract-ocr-dev (3.04.00-3) ... dpkg: error processing archive /var/cache/apt/archives/tesseract-ocr-dev_3.04.00-3_all.deb (--unpack): trying to overwrite '/usr/share/tesseract-ocr/language-specific.sh', which is also in package libtesseract-dev 3.04.00-3 Errors were encountered while processing: /var/cache/apt/archives/tesseract-ocr-dev_3.04.00-3_all.deb cheers, Andreas tesseract-ocr-dev_3.04.00-3.log.gz Description: application/gzip
Processed: notfound 711354 in 3.16.1-1, notfixed 778657 in 2.0.26-4, notfixed 789128 in 2.2.0-2 ...
Processing commands for cont...@bugs.debian.org:
# unconfuse bts: may not be found and fixed in the same version
notfound 711354 3.16.1-1
Bug #711354 {Done: Tomas Pospisek t...@sourcepole.ch} [gnote] gnote: Can't
use synchronization (WebDAV or local folder)
Bug #789947 {Done: Tomas Pospisek t...@sourcepole.ch} [gnote] gnote: Crash
when synchronizing
No longer marked as found in versions gnote/3.16.1-1.
No longer marked as found in versions gnote/3.16.1-1.
notfixed 778657 2.0.26-4
Bug #778657 {Done: Daniel Kahn Gillmor d...@fifthhorseman.net} [gnupg-agent]
gnupg-agent: Test for existing gpg-agent in /etc/X11/Xsession.d/90gpg-agent is
always true
No longer marked as fixed in versions gnupg2/2.0.26-4.
notfixed 789128 2.2.0-2
Bug #789128 {Done: Lior Kaplan kap...@debian.org} [php5-memcached] Installing
the package php5-memcached causes version incompatibility with php5-common
No longer marked as fixed in versions 2.2.0-2.
notfound 791428 3.16.3-1
Bug #791428 {Done: Michael Biebl bi...@debian.org} [mutter] mutter: Please
apply fix to Can click through full screen windows in sloppy/mouse mode
No longer marked as found in versions mutter/3.16.3-1.
found 789756 2.1.0-2
Bug #789756 {Done: Bas Couwenberg sebas...@debian.org}
[libosmium-dev,libosmium2-dev] libosmium2-dev and libosmium-dev: error when
trying to install together
There is no source info for the package 'libosmium-dev' at version '2.1.0-2'
with architecture ''
Marked as found in versions libosmium/2.1.0-2.
tags 765776 + sid stretch
Bug #765776 {Done: Sebastian Ramacher sramac...@debian.org}
[gstreamer0.10-plugins-bad] gstreamer0.10-plugins-bad: libdirac is unmaintained
upstream - please stop link against it if at all possible
Added tag(s) stretch and sid.
tags 788128 + sid stretch
Bug #788128 [libfile-scan-perl] libfile-scan-perl: most probably outdated,
should be removed?
Added tag(s) stretch and sid.
tags 791866 + sid stretch
Bug #791866 [visolate] visolate: build hardcodes specific version of
commons-cli.jar
Added tag(s) sid and stretch.
tags 784199 + sid stretch
Bug #784199 {Done: Guo Yixuan (郭溢譞) culu@gmail.com} [src:librime]
librime: need to rebuild against new libyaml-cpp
Added tag(s) stretch and sid.
# ports only
reassign 792555 src:eglibc 2.19-19
Bug #792555 [libc6.1-alphaev67] segfaults occurring when libc6.1-alphaev67
installed on alpha.
Warning: Unknown package 'libc6.1-alphaev67'
Bug reassigned from package 'libc6.1-alphaev67' to 'src:eglibc'.
Warning: Unknown package 'src:eglibc'
Warning: Unknown package 'src:eglibc'
No longer marked as found in versions 2.19-19.
Warning: Unknown package 'src:eglibc'
Warning: Unknown package 'src:eglibc'
Ignoring request to alter fixed versions of bug #792555 to the same values
previously set
Warning: Unknown package 'src:eglibc'
Bug #792555 [src:eglibc] segfaults occurring when libc6.1-alphaev67 installed
on alpha.
Warning: Unknown package 'src:eglibc'
The source 'eglibc' and version '2.19-19' do not appear to match any binary
packages
Marked as found in versions eglibc/2.19-19.
Warning: Unknown package 'src:eglibc'
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
usertags 789348 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
found 749317 2015.07.11
Bug #749317 [debian-security-support] debian-security-support: unowned
directory after purge: /var/lib/debian-security-support/
Marked as found in versions debian-security-support/2015.07.11.
found 782098 2.2.0-1
Bug #782098 [openexr,libopenexr-dev] openexr, libopenexr-dev: directory vs.
symlink conflict: /usr/share/doc/{openexr, libopenexr-dev} -
/usr/share/doc/libopenexr6
Marked as found in versions openexr/2.2.0-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
711354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711354
749317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749317
765776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765776
778657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778657
782098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782098
784199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784199
788128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788128
789128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789128
789348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789348
789756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789756
789947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789947
791428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791428
791866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791866
792555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789348: fixed in mate-applets 1.10.0+dfsg1-1~exp2
Control: found -1 1.10.3+dfsg1-1~exp1 Control: user debian...@lists.debian.org Control: usertag -1 piuparts And back again: Selecting previously unselected package mate-applets. (Reading database ... 22873 files and directories currently installed.) Preparing to unpack .../mate-applets_1.10.3+dfsg1-1~exp1_amd64.deb ... Unpacking mate-applets (1.10.3+dfsg1-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/mate-applets_1.10.3+dfsg1-1~exp1_amd64.deb (--unpack): trying to overwrite '/etc/sound/events/mate-battstat_applet.soundlist', which is also in package mate-applets-common 1.10.3+dfsg1-1~exp1 Errors were encountered while processing: /var/cache/apt/archives/mate-applets_1.10.3+dfsg1-1~exp1_amd64.deb Andreas PS: you could test your packages ;-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790287: marked as done (sunpinyin: FTBFS: pod2man error (no name given for document))
Your message dated Fri, 17 Jul 2015 07:34:51 + with message-id e1zg0av-0007fe...@franck.debian.org and subject line Bug#790287: fixed in sunpinyin 2.0.3+git20140127-2 has caused the Debian Bug report #790287, regarding sunpinyin: FTBFS: pod2man error (no name given for document) 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.) -- 790287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sunpinyin Version: 2.0.3+git20140127-1.1 Severity: serious From my pbuilder build log: ... g++ -o src/ime-core/userdict.os -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -DHAVE_CONFIG_H -DSUNPINYIN_DATA_DIR='/usr/lib/x86_64-linux-gnu/sunpinyin/data' -I. -Isrc -Isrc/ime-core -Isrc/lexicon -Isrc/pinyin -Isrc/slm -Isrc/slm/slmbuild -Isrc/slm/ids2ngram -Isrc/slm/tslminfo -Isrc/slm/mmseg -Isrc/slm/thread -Isrc/slm/tslmpack -Isrc/slm/slmprune -Isrc/slm/slminfo -Isrc/slm/tools -Isrc/slm/slmseg -Isrc/slm/tslmendian -Isrc/slm/getwordfreq src/ime-core/userdict.cpp g++ -o libsunpinyin.so.3.0 -Wl,-z,relro -Wl,-soname=libsunpinyin.so.3 -shared src/portability.os src/slm/slm.os src/lexicon/pytrie.os src/pinyin/pinyin_data.os src/pinyin/pinyin_seg.os src/pinyin/shuangpin_data.os src/pinyin/shuangpin_seg.os src/pinyin/hunpin_seg.os src/ime-core/imi_context.os src/ime-core/imi_data.os src/ime-core/lattice_states.os src/ime-core/imi_view.os src/ime-core/imi_uiobjects.os src/ime-core/imi_view_classic.os src/ime-core/imi_winHandler.os src/ime-core/ic_history.os src/ime-core/imi_funcobjs.os src/ime-core/imi_options.os src/ime-core/imi_option_event.os src/ime-core/userdict.os -lsqlite3 pod2man man/genpyt.pod man/genpyt.1 IO::File=IO(0x1b2e190) around line 1: No name given for document POD document had syntax errors at /usr/bin/pod2man line 71. scons: *** [man/genpyt.1] Error 255 scons: building terminated because of errors. debian/rules:22: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/buildd/sunpinyin-2.0.3+git20140127' debian/rules:14: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: sunpinyin Source-Version: 2.0.3+git20140127-2 We believe that the bug you reported is fixed in the latest version of sunpinyin, 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 790...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guo Yixuan (郭溢譞) culu@gmail.com (supplier of updated sunpinyin 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, 05 Jul 2015 15:20:03 -0400 Source: sunpinyin Binary: libsunpinyin-dev libsunpinyin3 libsunpinyin3-dbg python-sunpinyin sunpinyin-utils Architecture: source amd64 all Version: 2.0.3+git20140127-2 Distribution: unstable Urgency: medium Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org Changed-By: Guo Yixuan (郭溢譞) culu@gmail.com Description: libsunpinyin-dev - Simplified Chinese Input Method from SUN (development) libsunpinyin3 - Simplified Chinese Input Method from SUN (runtime) libsunpinyin3-dbg - Simplified Chinese Input Method from SUN (debug) python-sunpinyin - Simplified Chinese Input Method from SUN (Python binding) sunpinyin-utils - Simplified Chinese Input Method from SUN (utilities) Closes: 790287 Changes: sunpinyin (2.0.3+git20140127-2) unstable; urgency=medium . * Team upload. * Fixed pod2man invocations. (Closes: #790287) * Acknowledge Chen Baozi's NMU. Checksums-Sha1: 9d34bff09b5dd76ccbce8029acb45d9e228023f6 2023 sunpinyin_2.0.3+git20140127-2.dsc 47754b00436452a9f8528d103defc7ecb3ce5157 10836 sunpinyin_2.0.3+git20140127-2.debian.tar.xz b0c43b0c84e844b1708a5e74bfea064be16416e1 44124 libsunpinyin-dev_2.0.3+git20140127-2_amd64.deb fa2ab663bdb1eec3baaceec4c81b1f59898c5f4c 1537722 libsunpinyin3-dbg_2.0.3+git20140127-2_amd64.deb 25aeec618f2ca37579fbe50f937482424a06ff28 135608
Bug#789348: fixed in mate-applets 1.10.0+dfsg1-1~exp2
On 07/17/2015 09:12 AM, Andreas Beckmann wrote: PS: you could test your packages ;-) Well, you're right. But, OTOH, please keep in mind that you're using packages from the experimental archive. You usually get to keep the pieces when you take any packages from there and they break. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792524: same crash again
I've observed the same crash again but this time it was not preceded by any message from gnome-session/gnome-shell/mutter in the log Looking through the logs, I found the same message has been occurring intermittently at different times, even when the machine didn't crash, therefore, I would suggest keeping this bug open but lowering the severity and changing the bug title to focus on what this message means gnome-session[2616]: (gnome-shell:2782): mutter-CRITICAL **: meta_window_focus: assertion '!window-override_redirect' failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792655: cups-daemon: cupsd sefaults when handling ssl with libgnutls
Package: cups-daemon Version: 1.7.5-11+deb8u1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) 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) Versions of packages cups-daemon depends on: ii adduser 3.113+nmu3 ii bc 1.06.95-9 ii dpkg 1.17.25 ii init-system-helpers 1.22 ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libc62.19-18 ii libcups2 1.7.5-11+deb8u1 ii libcupsmime1 1.7.5-11+deb8u1 ii libdbus-1-3 1.8.18-0+deb8u1 ii libgnutls-deb0-283.3.8-6+deb8u1 ii libgssapi-krb5-2 1.12.1+dfsg-19 ii libpam0g 1.1.8-3.1 ii libpaper11.1.24+nmu4 ii libsystemd0 215-17+deb8u1 ii lsb-base 4.1+Debian13+nmu1 ii procps 2:3.3.9-9 ii ssl-cert 1.0.35 Versions of packages cups-daemon recommends: ii avahi-daemon 0.6.31-5 ii colord1.2.1-1+b2 ii cups-browsed 1.0.61-5+deb8u1 Versions of packages cups-daemon suggests: ii cups1.7.5-11+deb8u1 ii cups-bsd1.7.5-11+deb8u1 ii cups-client 1.7.5-11+deb8u1 ii cups-common 1.7.5-11+deb8u1 ii cups-filters [foomatic-filters] 1.0.61-5+deb8u1 ii cups-pdf2.6.1-15 ii cups-ppdc 1.7.5-11+deb8u1 ii cups-server-common 1.7.5-11+deb8u1 ii foomatic-db 20150411-1 ii ghostscript 9.06~dfsg-2 ii hplip 3.14.6-1+b2 ii poppler-utils 0.26.5-2 ii printer-driver-cups-pdf [cups-pdf] 2.6.1-15 ii printer-driver-gutenprint 5.2.10-3 ii printer-driver-hpcups 3.14.6-1+b2 ii smbclient 2:4.1.17+dfsg-2 ii udev215-17+deb8u1 -- Configuration Files: /etc/pam.d/cups [Errno 13] Keine Berechtigung: u'/etc/pam.d/cups' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791574: [Reproducible-builds] Bug#791574: strip-nondeterminism: failure in zip.pm, breaking package builds
On Fri, Jul 17, 2015 at 03:52:15PM +0200, Andreas Tille wrote: I tried to reproduce this problem but was unable to reproduce it in a pbuilder environment. Are any specific build options needed to reproduce this (since in my build log dh_strip_nondeterminism -O--parallel is not even called: ... dh_link -O--parallel debian/rules override_dh_compress ... Well, currently it's called by our modified debhelper. The bug to get it mainlined is #759895. Either you install our patched debhelper or you modify the package to call it. dh patch: https://anonscm.debian.org/cgit/reproducible/debhelper.git/commit/?id=cb27ff633c19deb7e027045e219771668e598fb0 -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature
Bug#792685: Unable to upgrade from wheezy to jessie
On Jul 17 2015, Sam Hartman hartm...@debian.org wrote: I have a filesystem that I can easily mount and fsck in wheezy, but when I try to run the jessie s3qladm upgrade command I get: Getting file system parameters.. File system revision too old to upgrade! [...] It's critical that there be a documented procedure that works for upgrading from the version in wheezy to the version in jessie using tools in jessie. At the moment the only way is to download intermediate S3QL versions and use them to upgrade in several steps. There is a chance that all required versions are available on snapshot.debian.org, but I haven't checked. I agree that this is unfortunate, but preserving backwards compatibility over so many upstream versions just for Debian wheezy users did not seem worth the time. Theoretically, it is possible to do all the upgrades in one step and integrate that into Jessie's s3ql package, but that would be a major coding effort. I guess it would have been better to package S3QL 2.x as a new s3ql2 package instead of it replacing the s3ql package. But I don't think there is a way to recticify that now - or is there? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778146: Patch for GCC5 build issue
tags 778145 + patch
thanks
Here's a fix for the GCC 5 build issue. Removed inline from function
signatures to work with test cases. The package builds and links with
GCC 5 with this change.
Upstream may prefer to move to C99 instead, please see section
Different semantics for inline functions at
https://gcc.gnu.org/gcc-5/porting_to.html for more background.
--
Nicholas Luedtke
Linux for HP Helion OpenStack, Hewlett-Packard
Description: Fixxed GCC5 build issue
Removed inline from problematic functions.
.
tinyscheme (1.41-1.1) UNRELEASED; urgency=medium
.
* Non-maintainer upload.
* Fixed GCC5 build issue.
Author: Nicholas Luedtke Nicholas lued...@hp.com
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: vendor|upstream|other, url of original patch
Bug: url in upstream bugtracker
Bug-Debian: https://bugs.debian.org/bugnumber
Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
Forwarded: no|not-needed|url proving that it has been forwarded
Reviewed-By: name and email of someone who approved the patch
Last-Update: -MM-DD
--- tinyscheme-1.41.orig/scheme.c
+++ tinyscheme-1.41/scheme.c
@@ -200,8 +200,8 @@ INTERFACE double rvalue(pointer p){
INTERFACE long charvalue(pointer p) { return ivalue_unchecked(p); }
INTERFACE INLINE int is_port(pointer p) { return (type(p)==T_PORT); }
-INTERFACE INLINE int is_inport(pointer p) { return is_port(p) p-_object._port-kind port_input; }
-INTERFACE INLINE int is_outport(pointer p) { return is_port(p) p-_object._port-kind port_output; }
+INTERFACE int is_inport(pointer p) { return is_port(p) p-_object._port-kind port_input; }
+INTERFACE int is_outport(pointer p) { return is_port(p) p-_object._port-kind port_output; }
INTERFACE INLINE int is_pair(pointer p) { return (type(p)==T_PAIR); }
#define car(p) ((p)-_object._cons._car)
@@ -226,7 +226,7 @@ INTERFACE INLINE char *syntaxname(pointe
static const char *procname(pointer x);
INTERFACE INLINE int is_closure(pointer p) { return (type(p)==T_CLOSURE); }
-INTERFACE INLINE int is_macro(pointer p){ return (type(p)==T_MACRO); }
+INTERFACE int is_macro(pointer p){ return (type(p)==T_MACRO); }
INTERFACE INLINE pointer closure_code(pointer p) { return car(p); }
INTERFACE INLINE pointer closure_env(pointer p){ return cdr(p); }
Processed: Patch for GCC5 build issue
Processing commands for cont...@bugs.debian.org: tags 778145 + patch Bug #778145 [src:thewidgetfactory] thewidgetfactory: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777819: marked as done (clementine: ftbfs with GCC-5)
Your message dated Fri, 17 Jul 2015 15:49:39 + with message-id e1zg7tl-0004gg...@franck.debian.org and subject line Bug#777819: fixed in clementine 1.2.3+dfsg-3 has caused the Debian Bug report #777819, regarding clementine: ftbfs with GCC-5 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.) -- 777819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:clementine Version: 1.2.3+dfsg-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/clementine_1.2.3+dfsg-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] [ 65%] Building CXX object src/CMakeFiles/clementine_lib.dir/ui/console.cpp.o cd /«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/src /usr/bin/c++ -DBOOST_BIND_NO_PLACEHOLDERS -DMYGPO_EXPORT= -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_OPENGL_LIB -DQT_SQL_LIB -DQT_STRICT_ITERATORS -DQT_USE_QSTRINGBUILDER -DQT_XML_LIB -DQT_NO_DEBUG_OUTPUT -DQT_NO_WARNING_OUTPUT -Woverloaded-virtual -Wall -Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs -Wno-unused-private-field -Wno-unknown-warning-option --std=c++0x -U__STRICT_ANSI__ -Werror -I/usr/include/taglib -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtCore -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -isystem /usr/include/qt4/QtOpenGL -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtDBus -isystem /usr/include/qt4/QtXml -isystem /usr/include/qt4/QtSql -isystem /usr/include/qt4/QtNetwork -I/«BUILDDIR»/cl ementine-1.2.3+dfsg -I/«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/src -I/«BUILDDIR»/clementine-1.2.3+dfsg/src -I/«BUILDDIR»/clementine-1.2.3+dfsg/src/../3rdparty/gmock/gtest/include -I/«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu -I/«BUILDDIR»/clementine-1.2.3+dfsg/3rdparty/qtsingleapplication -I/«BUILDDIR»/clementine-1.2.3+dfsg/3rdparty/qtiocompressor -I/usr/include/qxt/QxtCore -I/usr/include/qxt/QxtGui -I/«BUILDDIR»/clementine-1.2.3+dfsg/3rdparty/sha2 -I/«BUILDDIR»/clementine-1.2.3+dfsg/3rdparty/libmygpo-qt -I/«BUILDDIR»/clementine-1.2.3+dfsg/ext/libclementine-common -I/«BUILDDIR»/clementine-1.2.3+dfsg/ext/libclementine-tagreader -I/«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/ext/libclementine-tagreader -I/«BUILDDIR»/clementine-1.2.3+dfsg/ext/libclementine-remote -I/«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/ext/libclementine-remote -I/«BUILDDIR»/clementine-1.2.3+dfsg/ext/libclementine-spotifyblob -I/«BUILDDIR» /clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/ext/libclementine-spotifyblob -I/usr/include/QtCrypto -I/usr/include/gpod-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/p11-kit-1 -I/usr/include/libusb-1.0 -o CMakeFiles/clementine_lib.dir/ui/console.cpp.o -c /«BUILDDIR»/clementine-1.2.3+dfsg/src/ui/console.cpp /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/CMakeFiles [ 65%] Building CXX object src/CMakeFiles/clementine_lib.dir/ui/coverfromurldialog.cpp.o cd /«BUILDDIR»/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/src /usr/bin/c++ -DBOOST_BIND_NO_PLACEHOLDERS -DMYGPO_EXPORT= -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG
Bug#778175: Unable to reproduce GCC-5 build issue
Control: fixed -1 3.2.1~dfsg1-1 On Mon, Jul 6, 2015 at 10:42 PM, Dall, Elizabeth J betty.d...@hp.com wrote: fixed 778175 3.2.1 thanks Corrected the version number which the FTBFS is fixed in. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#778175: Unable to reproduce GCC-5 build issue
Processing control commands:
fixed -1 3.2.1~dfsg1-1
Bug #778175 {Done: László Böszörményi (GCS) g...@debian.org} [src:wxsqlite3]
wxsqlite3: ftbfs with GCC-5
Marked as fixed in versions wxsqlite3/3.2.1~dfsg1-1.
--
778175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf
Followup-For: Bug #787533 Control: tag -1 patch Hi Otto, you can find the patches needed to fix this issue in git://git.debian.org/users/anbe/tmp/mariadb-10.0.git Andreas Beckmann (4): mariadb-common: make mysql-common dependency versioned mariadb-common.postinst: drop fallback my.cnf symlink management simplify mariadb-common maintainer scripts mariadb-common.preinst: undo my.cnf symlink and my.cnf.old from the fallback See #792080 for details and corresponding patches for mysql-common. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf
Processing control commands: tag -1 patch Bug #787533 [mariadb-common] mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf Added tag(s) patch. -- 787533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink
On 2015-07-14 18:33, Robie Basak wrote: Hi Andreas, On Sat, Jul 11, 2015 at 03:29:02AM +0200, Andreas Beckmann wrote: Since the issue is hard to describe in detail and with all pitfalls without digging into it and testing it, I rather developed patches that I tested in sid and stretch, to ensure sane upgrade paths. The commit messages should explain all the problems involved ... if you have more questions, just ask. Thank you for looking at this! I hadn't quite got round to it since I ended up focusing on the piuparts logger thing on my last pass over the MySQL packaging. And many thanks again for digging into this! These all look fine to me, I pushed another one to deregister the my.cnf.fallback alternative on removal, otherwise purge gets noisy about the dangling link. but I presume depend on mariadb uploading a 10.0.20-3 with corresponding changes? I'm happy to commit this to git and get an upload (I'm DM now but I don't think I'm in the keyring yet) If your regular sponsor is unavailable, I can help with uploading :-) but I guess we should coordinate with Otto for a corresponding mariadb upload? I have just posted the mariadb changes to #787533. In my tests with piuparts the upgrade paths now looks fine. Only people that track sid and use mariadb, i.e. that had upgraded to mysql-common 5.6.25-2, may end up with an unneccessary my.cnf.migrated (could be the pristine my.cnf from before the switch). It would be quite easy to detect this as well, we would just need a (list of) md5sums of the old pristine my.cnf to compare against. Regarding myriadb - hmm, I make the typo quite often :-) - ... I would even allow mariadb-10.0 10.0.20-2 to migrate to testing first, but as long as it FTBFS on powerpc this is not going to happen ... Any update to mariadb-10.0 in sid that does not include my changes would require a corresponding version bump in the Breaks in mysql-common. Will we have to adjust the versioning of the Breaks/Depends somehow to also cover Ubuntu properly? And now we are moving slightly offtopic in this bug: * Have you considered building mysql-common from a separate source package? Because since it is a required part for all mysql compatible stuff it shouldn't be blocked by being bundled to a specific implementation that is temporarily not being ready for migration * What are your plans for the mysql-5.5 - 5.6 switch? Is mysql-5.5 planned to be made installable again or is it just going to be removed? Are there any packages (outside src:mysql-5.5) depending on the versioned *-5.5 package names? Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink
Hi Andreas, Some quick answers (without looking at detail): On Fri, Jul 17, 2015 at 01:10:35PM +0200, Andreas Beckmann wrote: I pushed another one to deregister the my.cnf.fallback alternative on removal, otherwise purge gets noisy about the dangling link. Having looked at your previous patches I feel that you have a better grasp on this fix than I do and agree with the principle of your proposed fix, so I'm happy to take your direction on this - both on the patches and on coordination with mariadb. Please feel free to upload from VCS as needed to fix this issue. In my tests with piuparts the upgrade paths now looks fine. Only people that track sid and use mariadb, i.e. that had upgraded to mysql-common 5.6.25-2, may end up with an unneccessary my.cnf.migrated (could be the pristine my.cnf from before the switch). It would be quite easy to detect this as well, we would just need a (list of) md5sums of the old pristine my.cnf to compare against. We can do this later too, right? Will we have to adjust the versioning of the Breaks/Depends somehow to also cover Ubuntu properly? mariadb in Ubuntu has never created the symlink. As it had the mysql-common update-alternatives symlink code first, it didn't need it. It was my error in understanding that this was blocking Otto in Debian since mysql-common wasn't updated in Debian (jessie was in freeze at the time we did it, and I neglected it after jessie was released). I'll take a look before I update Ubuntu. I might just need to make sure that the symlink is never deleted, or verify that the code won't ever do that. And now we are moving slightly offtopic in this bug: I'll take this off the bug and reply on the list. Robie signature.asc Description: Digital signature
Processed: Fixing tag of wrong bug number
Processing commands for cont...@bugs.debian.org: tags 778145 - patch Bug #778145 [src:thewidgetfactory] thewidgetfactory: ftbfs with GCC-5 Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch for GCC5 build issue
Processing commands for cont...@bugs.debian.org: tags 778146 + patch Bug #778146 [src:tinyscheme] tinyscheme: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Reproducible-builds] Bug#792591: prettytable: FTBFS when locale-all is installed instead of locales
Processing commands for cont...@bugs.debian.org: affects 788352 prettytable Bug #788352 [locales-all] locales-all must not provide: locales if it doesnt provide the same features Added indication that 788352 affects prettytable thanks Stopping processing here. Please contact me if you need assistance. -- 788352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fixed, pending upload
Processing commands for cont...@bugs.debian.org: tags 791574 + fixed-upstream Bug #791574 [strip-nondeterminism] strip-nondeterminism: failure in zip.pm, breaking package builds Added tag(s) fixed-upstream. tags 791574 + pending Bug #791574 [strip-nondeterminism] strip-nondeterminism: failure in zip.pm, breaking package builds Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 791574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778117: marked as done (shibboleth-sp2: ftbfs with GCC-5)
Your message dated Fri, 17 Jul 2015 17:20:11 +
with message-id e1zg9ix-0004no...@franck.debian.org
and subject line Bug#778117: fixed in shibboleth-sp2 2.5.3+dfsg-2.1
has caused the Debian Bug report #778117,
regarding shibboleth-sp2: ftbfs with GCC-5
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.)
--
778117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:shibboleth-sp2
Version: 2.5.3+dfsg-1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/shibboleth-sp2_2.5.3+dfsg-1_unstable_gcc5.log
The last lines of the build log are at the end of this report.
To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files. For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html
[...]
| #define HAVE_PWD_H 1
| #define HAVE_SYS_SOCKET_H 1
| #define SHIBSP_HAVE_SYS_SOCKET_H 1
| #define HAVE_STRCHR 1
| #define HAVE_STRDUP 1
| #define HAVE_STRSTR 1
| #define HAVE_TIMEGM 1
| #define HAVE_GMTIME_R 1
| #define HAVE_LOCALTIME_R 1
| #define HAVE_STRTOK_R 1
| #define HAVE_STRCASECMP 1
| #define HAVE_GETPWNAM 1
| #define HAVE_GETGRNAM 1
| #define HAVE_STRUCT_SOCKADDR_STORAGE 1
| #define HAVE_SOCK_CLOEXEC 1
| /* end confdefs.h. */
| #include pthread.h
| int
| main ()
| {
| pthread_t th; pthread_join(th, 0);
| pthread_attr_init(0); pthread_cleanup_push(0, 0);
| pthread_create(0,0,0,0); pthread_cleanup_pop(0);
| ;
| return 0;
| }
configure:18789: result: no
configure:18697: checking whether pthreads work with -kthread
configure:18780: gcc -o conftest -Wall -g -O2 -fPIE -fstack-protector-strong
-Wformat -Werror=format-security -O2 -DNDEBUG -kthread -D_FORTIFY_SOURCE=2
-fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed conftest.c 5
gcc: error: unrecognized command line option '-kthread'
configure:18780: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME shibboleth
| #define PACKAGE_TARNAME shibboleth-sp
| #define PACKAGE_VERSION 2.5.3
| #define PACKAGE_STRING shibboleth 2.5.3
| #define PACKAGE_BUGREPORT https://issues.shibboleth.net/;
| #define PACKAGE_URL
| #define PACKAGE shibboleth-sp
| #define VERSION 2.5.3
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
Source: shibboleth-sp2
Source-Version: 2.5.3+dfsg-2.1
We believe that the bug you reported is fixed in the latest version of
shibboleth-sp2, 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 778...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated shibboleth-sp2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 Jul 2015 15:56:14 +0200
Source: shibboleth-sp2
Binary: libapache2-mod-shib2 libshibsp6 libshibsp-plugins libshibsp-dev
libshibsp-doc shibboleth-sp2-common shibboleth-sp2-schemas shibboleth-sp2-utils
Architecture: source amd64 all
Version: 2.5.3+dfsg-2.1
Bug#777837: Patch for GCC5 build issue
Here's a fix for the GCC 5 build issue. I added extern to
inline function in jcode.c. The package builds and links with GCC 5 with
this change.
Alternatively, simply get rid of the inline declaration. All the calls
to isjisp are in different translation units so they never get inlined
anyway.
Patch:
--- a/src/jcode.c
+++ b/src/jcode.c
@@ -275,7 +275,7 @@ gchar *iconv_convert2(const gchar *icode, const gchar
*ocode, const gchar *orig)
return(result);
}
-inline gboolean isjisp(const gchar *buff){
+gboolean isjisp(const gchar *buff){
g_assert(buff != NULL);
if((buff[0] = 0x21) (buff[0] = 0x74)
--- a/src/jcode.h
+++ b/src/jcode.h
@@ -31,7 +31,7 @@ enum {
gchar *iconv_convert(const gchar *icode, const gchar *ocode, const gchar
*inbuf);
gchar *iconv_convert2(const gchar *icode, const gchar *ocode, const gchar
*orig);
-inline gboolean isjisp(const gchar *buff);
+gboolean isjisp(const gchar *buff);
gboolean iseuckanji(const guchar *buff);
gboolean iseuchiragana(const guchar *buff);
gboolean iseuckatakana(const guchar *buff);
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: Unable to upgrade from wheezy to jessie
Nikolaus == Nikolaus Rath nikol...@rath.org writes: Nikolaus I agree that this is unfortunate, but preserving backwards Nikolaus compatibility over so many upstream versions just for Nikolaus Debian wheezy users did not seem worth the time. I totally understand that it's a lot of work and totally get that you might not want to do that work. However, Debian as a project balances stability and upgrade tradeoffs across the project, and this is one of those areas where a project goal may require more work to be put into a package for that package to be suitable for inclusion in a Debian release. No one is obligated to do that work, but Debian's philosophy is generally that if the work to make upgrades work well can't be done, then a package should not be included in releases. If a package is not going to provide an upgrade from one debian release to the next, it should not generally be in the Debian release. It would be fine for it to continue to be in unstable. We need to figure out if someone is willing to commit to doing the necessary work for stretch and if not probably leave s3ql in unstable but pull from stretch and investigate whether it should be pulled from Jessie in a point release. s3ql tends to get used for backups and other things where availability is quite important and saying oops, you don't get your data when you upgraded, is kind of a big deal. If Debian users can't count on maintaining access to their data after the upgrades, then we probably want to warn them about that up front, and the experience may not be good enough to actually recommend that people store data in s3ql. I understand that as an upstream author you might well want a more rapid deployment cycle than Debian's release process. That's fine. I'm not judging anything here. I'm just saying that if software's going to be in a Debian release it needs to live up to what that means. Nikolaus Theoretically, it is possible to do all the upgrades in Nikolaus one step and integrate that into Jessie's s3ql package, Nikolaus but that would be a major coding effort. Nikolaus I guess it would have been better to package S3QL 2.x as a Nikolaus new s3ql2 package instead of it replacing the s3ql Nikolaus package. But I don't think there is a way to recticify Nikolaus that now - or is there? But then people still lose their data from wheezy-jessie. So, you talked about it being a lot of work to do the upgrade in one step. Why does that need to happen? Why can't the upgrade be handled in two steps and we just package the necessary parts to do all the steps? How much harder are we talking about than getting the s3qladm and s3ql libraries from the 2.5 version of s3ql into Jessie? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777928: marked as done (kmplayer: ftbfs with GCC-5)
Your message dated Fri, 17 Jul 2015 16:49:41 + with message-id e1zg8pr-0007tn...@franck.debian.org and subject line Bug#777928: fixed in kmplayer 1:0.11.3d-2.1 has caused the Debian Bug report #777928, regarding kmplayer: ftbfs with GCC-5 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.) -- 777928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:kmplayer Version: 1:0.11.3d-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/kmplayer_0.11.3d-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] /«PKGBUILDDIR»/src/kmplayerplaylist.h:526:14: note: previous declaration of 'KMPlayer::NodeList KMPlayer::Node::childNodes() const' NodeList childNodes () const; ^ /«PKGBUILDDIR»/src/kmplayer_part.cpp:143:47: warning: unused parameter 'n' [-Wunused-parameter] const QString file, PlayListNotify * n) ^ /«PKGBUILDDIR»/src/kmplayer_part.cpp: In constructor 'KMPlayerPart::KMPlayerPart(QWidget*, QObject*, const QStringList)': /«PKGBUILDDIR»/src/kmplayer_part.cpp:246:45: warning: variable 'it' set but not used [-Wunused-but-set-variable] QStringList::const_iterator it = sl.constBegin (); ^ /«PKGBUILDDIR»/src/kmplayer_part.cpp: In member function 'void KMPlayerLiveConnectExtension::evaluate(const QString, bool, QString)': /«PKGBUILDDIR»/src/kmplayer_part.cpp:1130:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (i == object_counter-1) ^ /«PKGBUILDDIR»/src/kmplayer_part.cpp: In member function 'virtual bool KMPlayerLiveConnectExtension::call(long unsigned int, const QString, const QStringList, KParts::LiveConnectExtension::Type, long unsigned int, QString)': /«PKGBUILDDIR»/src/kmplayer_part.cpp:1424:32: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] for (unsigned int i = 0; i args.size (); ++i) ^ Linking CXX shared module ../lib/libkmplayerpart.so cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src /usr/bin/cmake -E cmake_link_script CMakeFiles/kmplayerpart.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc -Wl,-z,relro -shared -Wl,-soname,libkmplayerpart.so -o ../lib/libkmplayerpart.so CMakeFiles/kmplayerpart.dir/kmplayerpart_automoc.o CMakeFiles/kmplayerpart.dir/kmplayer_part.o -L/«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib ../lib/libkmplayercommon.so -lkmediaplayer /usr/lib/libkparts.so.4.14.2 /usr/lib/libkdeui.so.5.14.2 /usr/lib/x86_64-linux-gnu/libQt3Support.so /usr/lib/libkde3support.so.4.14.2 /usr/lib/libkparts.so.4.14.2 /usr/lib/x86_64-linux-gnu/libQt3Support.so /usr/lib/libkio.so.5.14.2 /usr/lib/libne pomukutils.so.4.14.2 /usr/lib/x86_64-linux-gnu/libQtNetwork.so /usr/lib/x86_64-linux-gnu/libQtXml.so /usr/lib/libnepomuk.so.4.14.2 /usr/lib/libkdeui.so.5.14.2
Bug#791574: Fixed, pending upload
tags 791574 + fixed-upstream tags 791574 + pending thanks This was caused by a zip64 archive in the golang test suite. Archive::Zip, and hence strip-nondeterminism, doesn't support zip64 archives. Fortunately, zip64 archives are rare and the one in the golang source doesn't contain any nondeterminism, so I've modified strip-nondeterminism to just ignore zip64 archives. -- Andrew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777929: marked as done (kphotoalbum: ftbfs with GCC-5)
Your message dated Fri, 17 Jul 2015 17:34:22 + with message-id e1zg9wg-0006oi...@franck.debian.org and subject line Bug#777929: fixed in kphotoalbum 4.5-1.1 has caused the Debian Bug report #777929, regarding kphotoalbum: ftbfs with GCC-5 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.) -- 777929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:kphotoalbum Version: 4.5-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/kphotoalbum_4.5-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] [ 65%] Building CXX object CMakeFiles/kphotoalbum.dir/ImageManager/PreloadRequest.cpp.o /usr/bin/c++ -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=25 -DKDE_DEPRECATED_WARNINGS -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -D_BSD_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 -Doverride= -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -std=c++11 -DNDEBUG -DQT_NO_DEBUG -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR» -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp -I/usr/i nclude/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/marble -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -fexceptions -UQT_NO_EXCEPTIONS -o CMakeFiles/kphotoalbum.dir/ImageManager/PreloadRequest.cpp.o -c /«PKGBUILDDIR»/ImageManager/PreloadRequest.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles [ 65%] Building CXX object CMakeFiles/kphotoalbum.dir/ImageManager/CancelEvent.cpp.o /usr/bin/c++ -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=25 -DKDE_DEPRECATED_WARNINGS -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -D_BSD_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 -Doverride= -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -std=c++11 -DNDEBUG -DQT_NO_DEBUG -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR» -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp -I/usr/i nclude/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore
Bug#791574: [Reproducible-builds] Bug#791574: strip-nondeterminism: failure in zip.pm, breaking package builds
Hi Matthia, On Fri, Jul 17, 2015 at 04:07:26PM +, Mattia Rizzolo wrote: On Fri, Jul 17, 2015 at 03:52:15PM +0200, Andreas Tille wrote: I tried to reproduce this problem but was unable to reproduce it in a pbuilder environment. Are any specific build options needed to reproduce this (since in my build log dh_strip_nondeterminism -O--parallel is not even called: ... dh_link -O--parallel debian/rules override_dh_compress ... Well, currently it's called by our modified debhelper. The bug to get it mainlined is #759895. Either you install our patched debhelper or you modify the package to call it. dh patch: https://anonscm.debian.org/cgit/reproducible/debhelper.git/commit/?id=cb27ff633c19deb7e027045e219771668e598fb0 Ahhh, that's interesting. My situation is that I just wanted to find out why some of our team packages are about to be removed. I do not expect myself to be very helpful in fixing the problem. The only thing I would like to know is why this bug is qualified as serious if there is no build error when using the available tools but fails only with a patched tool. IMHO this does qualify as important as maximum. Please do not understand me wrong: Any bug should be fixed but I see no point in kicking a chain of packages out uf testing only because a package using a patched debhelper fails to build. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774149: Workaround working
Hi Rogério I would really appreciate if you keep usbmount alive. The idea of a small tool to daemonize mount sounds interesting, but this is one point where I am not sure. I've read an article about udev, where it was stated, that udev should not start a daemon directly, but should use systemd to do it. Adding a dependency to systemd gives the project a complexity and political level I don't like. This was the point where I started on thinking about using at to do the job. To complete your question: This bug only affects fuse based filesystems on my side. best regards, Jürgen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#791574: [Reproducible-builds] Bug#791574: strip-nondeterminism: failure in zip.pm, breaking package builds
Processing commands for cont...@bugs.debian.org: severity 791574 important Bug #791574 [strip-nondeterminism] strip-nondeterminism: failure in zip.pm, breaking package builds Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 791574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791574: [Reproducible-builds] Bug#791574: strip-nondeterminism: failure in zip.pm, breaking package builds
severity 791574 important thanks On Fri, 17 Jul 2015 20:08:13 +0200 Andreas Tille andr...@an3as.eu wrote: Ahhh, that's interesting. My situation is that I just wanted to find out why some of our team packages are about to be removed. I do not expect myself to be very helpful in fixing the problem. The only thing I would like to know is why this bug is qualified as serious if there is no build error when using the available tools but fails only with a patched tool. IMHO this does qualify as important as maximum. Please do not understand me wrong: Any bug should be fixed but I see no point in kicking a chain of packages out uf testing only because a package using a patched debhelper fails to build. Hi Andreas, I agree the severity was set too high considering it only affected builds with a patched debhelper. I had no idea strip-nondeterminism had accumulated so many reverse dependencies, or I would have been more proactive about making sure packages outside of the reproducible builds effort weren't bothered with an auto-removal notice. I just decreased the severity, and a fixed package will be uploaded to unstable soon anyways, so you don't have to worry about your packages being kicked out. Cheers, Andrew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778121: sks-ecc: ftbfs with GCC-5
tags 778121 +patch Build failure is due to changing inline function semantics in C11 spec, which is default now in gcc5. Work around by adding -std=gnu89 as gcc parameter. --- sks-ecc-0.93.orig/Makefile +++ sks-ecc-0.93/Makefile @@ -18,6 +18,9 @@ CC=gcc #CFLAGS+= -s CFLAGS += -DVERSION='$(VER)' +# Revert back to gnu89 standard for gcc 5 +CFLAGS += -std=gnu89 + #INST = /usr/local/bin #INST = $(HOME)/bin INST = $(DESTDIR)/usr/bin -- Brett Johnson br...@hp.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: sks-ecc: ftbfs with GCC-5
Processing commands for cont...@bugs.debian.org: tags 778121 +patch Bug #778121 [src:sks-ecc] sks-ecc: ftbfs with GCC-5 Added tag(s) patch. Build failure is due to changing inline function semantics in C11 spec, Unknown command or malformed arguments to command. which is default now in gcc5. Work around by adding -std=gnu89 as Unknown command or malformed arguments to command. gcc parameter. Unknown command or malformed arguments to command. --- sks-ecc-0.93.orig/Makefile Unknown command or malformed arguments to command. +++ sks-ecc-0.93/Makefile Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 778121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792659: tesseract-ocr-dev: fails to install, trying to overwrite other packages files: /usr/share/tesseract-ocr/language-specific.sh
Thanks, I'll investigate today.
Bug#792742: [sqlitebrowser]
Package: sqlitebrowser Severity: grave --- Please enter the report below this line. --- HI PLEASE IGNORE MY PREVIOUS MESSAGE (IT FOLLOWS) == Hi, I have installed sqliteborwser and synaptic declares that should exists the file /usr/bin/sqlitebrowser but it is not present! So this software is not usable Command 504 of 6 $ls /usr/bin/sq* /usr/bin/sq/usr/bin/sqlsharp /usr/bin/sqlt-diagram /usr/bin/sqlt-diff-old /usr/bin/sqlt-graph /usr/bin/squiggle /usr/bin/sqlmetal /usr/bin/sqlt /usr/bin/sqlt-diff /usr/bin/sqlt-dumper/usr/bin/squeak Please contact me if you need more information Best Marco --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable-updates ftp.it.debian.org 500 stable security.debian.org 500 stable repo.wuala.com 500 stable ftp.it.debian.org 500 stable apt.spideroak.com 500 jessie linux.dropbox.com 500 debian packages.linuxmint.com 100 jessie-backports ftp.it.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790043: marked as done (mapnik: no longer builds python bindings)
Your message dated Sat, 18 Jul 2015 02:28:22 +0200 with message-id 55a99da6.1060...@xs4all.nl and subject line Re: Bug#790043: mapnik: no longer builds python bindings has caused the Debian Bug report #790043, regarding mapnik: no longer builds python bindings 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.) -- 790043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mapnik Version: 3.0.0~rc3+ds-1 Severity: serious Hi, mapnik no longer builds the python bindings, but tilelite still depends on those. Something needs to be done here so that mapnik can be in a releasable state: either the bindings are brought back (possibly from a different source package) or codelite needs to be fixed / removed. Emilio ---End Message--- ---BeginMessage--- Control: fixed -1 python-mapnik/1:0.0~20150708-c005502-1 On 06/27/2015 02:23 PM, Sebastiaan Couwenberg wrote: On 06/26/2015 07:31 PM, Sebastiaan Couwenberg wrote: On 06/26/2015 07:26 PM, Jérémy Lal wrote: indeed upstream moved python bindings development to a separate project https://github.com/mapnik/python-mapnik Anyone interested in helping ? I'm not used to packaging python modules. Yes, I'm started to work on a python-mapnik package from that git repository. I was unstable to use pypi.debian.net despite there being a 0.1 release on pypi.python.org. python-mapnik doesn't support Python 3, so that will need to be fixed for it to have a future post-buster. Initial packaging for python-mapnik is available on Alioth: http://anonscm.debian.org/cgit/pkg-grass/python-mapnik.git Unfortunately the code in the python-mapnik git repository is not compatible with mapnik 3.0.0-RC3. With the changes in mapnik (3.0.0+ds-2) and a patch for the boost libraries the new python-mapnik package builds successfully. It was accepted into unstable yesterday, which should resolve this issue. I've also updated the python-mapnik dependency in tilelite to no longer use the python-mapnik2 transitional package. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1---End Message---
Processed: wnpp
Processing commands for cont...@bugs.debian.org: block 792084 by 792751 Bug #792084 [yaboot] FTBFS: Fails to build from source 792084 was not blocked by any bugs. 792084 was blocking: 774845 784387 Added blocking bug(s) of 792084: 792751 thanks Stopping processing here. Please contact me if you need assistance. -- 792084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791729: Executing via systemsettings is not the only way to do it
kde-gtk-config doesn't require systemsettings at all. As a work-around unstill both systemsettings and kde-gtk-config you can execute the following: kcmshell5 kde-gtk-config This is only a transient issue as we migrate from KDE4 SC to Plasma 5. Adjusting severity accordingly. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 791729 is important
Processing commands for cont...@bugs.debian.org: severity 791729 important Bug #791729 [kde-config-gtk-style] kde-config-gtk-style: Upgrading to version 4:5.3.2-1 makes it not work anymore Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 791729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790529: closing 790529
close 790529 1.0.1-3 thanks Missing breaks/replaces were added. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 790529
Processing commands for cont...@bugs.debian.org: close 790529 1.0.1-3 Bug #790529 [debconf-kde-data] debconf-kde-data: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/bs/LC_MESSAGES/libdebconf-kde.mo Marked as fixed in versions debconf-kde/1.0.1-3. Bug #790529 [debconf-kde-data] debconf-kde-data: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/bs/LC_MESSAGES/libdebconf-kde.mo Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 790529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792289: marked as done (plasma-workspace: can't open files)
Your message dated Sat, 18 Jul 2015 04:19:20 + with message-id e1zgjaq-0005rn...@franck.debian.org and subject line Bug#792289: fixed in plasma-workspace 4:5.3.2-2 has caused the Debian Bug report #792289, regarding plasma-workspace: can't open files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 792289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: plasma-workspace Version: 4:5.3.2-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, the open file dialog is broken after installing this (or one of the deps, I am not sure how to track this exactly) but now file dialogs are not working any longer. I first tried changing the default desktop image, but the dialog does not show any file. Then I tried using relational and opening a file, but the application just got stuck without showing the dialog. With KDE4 it worked fine, it got broken by plasma5. I am flagging this as critical, because I think it is a major functionality that is not available at the moment. Best regards. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.8j (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-workspace depends on: ii dbus-x111.8.18-1 ii frameworkintegration5.12.0-1 ii gdb 7.8.1-1 ii kactivities 5.12.0-1 ii kde-cli-tools 4:5.3.2-2 ii kded5 5.12.0-1 ii kinit 5.12.0-1 ii kio-extras 4:5.3.2-2 ii libc6 2.19-19 ii libcln6 1.3.4-1 ii libdbusmenu-qt5-2 0.9.3+15.10.20150604-1 ii libgcc1 1:5.1.1-14 ii libgps213.11-3 ii libice6 2:1.0.9-1+b1 ii libkf5activities5 5.12.0-1 ii libkf5auth5 5.12.0-1 ii libkf5baloo15.9.2-2 ii libkf5bookmarks55.12.0-1 ii libkf5completion5 5.12.0-1 ii libkf5configcore5 5.12.0-1 ii libkf5configgui55.12.0-1 ii libkf5configwidgets55.12.0-1 ii libkf5coreaddons5 5.12.0-1 ii libkf5crash55.12.0-1 ii libkf5dbusaddons5 5.12.0-1 ii libkf5declarative5 5.12.0-1 ii libkf5globalaccel-bin 5.12.0-1 ii libkf5globalaccel5 5.12.0-1 ii libkf5guiaddons55.12.0-1 ii libkf5i18n5 5.12.0-1 ii libkf5iconthemes5 5.12.0-1 ii libkf5idletime5 5.12.0-1 ii libkf5itemviews55.12.0-1 ii libkf5jobwidgets5 5.12.0-1 ii libkf5js5 5.12.0-1 ii libkf5jsembed5 5.12.0-1 ii libkf5kdelibs4support5 5.12.0-1 ii libkf5kiocore5 5.12.0-1 ii libkf5kiofilewidgets5 5.12.0-1 ii libkf5kiowidgets5 5.12.0-1 ii libkf5networkmanagerqt6 5.12.0-1 ii libkf5newstuff5 5.12.0-1 ii libkf5notifications55.12.0-1 ii libkf5notifyconfig5 5.12.0-1 ii libkf5package5 5.12.0-1 ii libkf5plasma5 5.12.0-1 ii libkf5plasmaquick5 5.12.0-1 ii libkf5runner5 5.12.0-1 ii libkf5screen6 4:5.3.2-1 ii libkf5service-bin 5.12.0-1 ii libkf5service5 5.12.0-1 ii libkf5solid55.12.0-1 ii libkf5su5 5.12.0-1 ii libkf5texteditor5 5.12.0-1 ii libkf5textwidgets5 5.12.0-1 ii libkf5wallet5 5.12.0-1 ii libkf5waylandclient54:5.3.2-1 ii libkf5waylandserver54:5.3.2-1 ii libkf5webkit5 5.12.0-1 ii libkf5widgetsaddons55.12.0-1 ii libkf5windowsystem5 5.12.0-1 ii libkf5xmlgui5
Processed: iep: /usr/bin/iep is already provided by the emboss package
Processing control commands: affects -1 + emboss Bug #792748 [iep] iep: /usr/bin/iep is already provided by the emboss package Added indication that 792748 affects emboss -- 792748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792748: iep: /usr/bin/iep is already provided by the emboss package
Package: iep Version: 3.6.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: affects -1 + emboss Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package iep. Preparing to unpack .../archives/iep_3.6.1-1_all.deb ... Unpacking iep (3.6.1-1) ... dpkg: error processing archive /var/cache/apt/archives/iep_3.6.1-1_all.deb (--unpack): trying to overwrite '/usr/bin/iep', which is also in package emboss 6.6.0+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/iep_3.6.1-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/iep Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html emboss=6.6.0+dfsg-1_iep=3.6.1-1.log.gz Description: application/gzip
Processed: Processed: Mark as fixed
Processing commands for cont...@bugs.debian.org:
found 790043 mapnik/3.0.0~rc3+ds-1
Bug #790043 {Done: Sebastiaan Couwenberg sebas...@xs4all.nl} [python-mapnik]
mapnik: no longer builds python bindings
Marked as found in versions mapnik/3.0.0~rc3+ds-1 and reopened.
fixed 790043 python-mapnik/1:0.0~20150708-c005502-1
Bug #790043 [python-mapnik] mapnik: no longer builds python bindings
Marked as fixed in versions python-mapnik/1:0.0~20150708-c005502-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
790043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Mark as fixed
Processing commands for cont...@bugs.debian.org:
fixed 790043 python-mapnik/1:0.0~20150708-c005502-1
Bug #790043 {Done: Sebastiaan Couwenberg sebas...@xs4all.nl} [src:mapnik]
mapnik: no longer builds python bindings
Marked as fixed in versions python-mapnik/1:0.0~20150708-c005502-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
790043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Reassign to python-mapnik
Processing commands for cont...@bugs.debian.org:
reassign 790043 python-mapnik
Bug #790043 {Done: Sebastiaan Couwenberg sebas...@xs4all.nl} [src:mapnik]
mapnik: no longer builds python bindings
Bug reassigned from package 'src:mapnik' to 'python-mapnik'.
No longer marked as found in versions mapnik/3.0.0~rc3+ds-1.
No longer marked as fixed in versions python-mapnik/1:0.0~20150708-c005502-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
790043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: Unable to upgrade from wheezy to jessie
On Jul 17 2015, Sam Hartman hartm...@debian.org wrote: If a package is not going to provide an upgrade from one debian release to the next, it should not generally be in the Debian release. It would be fine for it to continue to be in unstable. We need to figure out if someone is willing to commit to doing the necessary work for stretch and if not probably leave s3ql in unstable but pull from stretch and investigate whether it should be pulled from Jessie in a point release. I agree. There shouldn't have been an s3ql package in Wheezy. This was when I was young and inexperienced with Debian packaging. However, the situation is different for Jessie. Now that it is much more mature, there will be issues in keeping the stretch S3QL fully backwards compatible with Jessie S3QL. Nikolaus I guess it would have been better to package S3QL 2.x as a Nikolaus new s3ql2 package instead of it replacing the s3ql Nikolaus package. But I don't think there is a way to recticify Nikolaus that now - or is there? But then people still lose their data from wheezy-jessie. No, in that case we could have kept the old S3QL 1.x package in jessie. Nikolaus Theoretically, it is possible to do all the upgrades in Nikolaus one step and integrate that into Jessie's s3ql package, Nikolaus but that would be a major coding effort. So, you talked about it being a lot of work to do the upgrade in one step. Why does that need to happen? Why can't the upgrade be handled in two steps and we just package the necessary parts to do all the steps? That would mean to package ~5 intermediate S3QL versions. Not a big deal in terms of work (since these versions were already in testing at some point), but do you think that would be acceptable for a point release? How much harder are we talking about than getting the s3qladm and s3ql libraries from the 2.5 version of s3ql into Jessie? I don't understand the question. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778157: user-mode-linux: ftbfs with GCC-5
Control: tags -1 + fixed-upstream * Matthias Klose d...@debian.org, 2015-02-12, 10:37: CC arch/um/kernel/config.o In file included from arch/um/kernel/config.c:8:0: ./arch/um/include/shared/init.h:129:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__used' #define __uml_setup_help __used __section(.uml.help.init) Upstream fix: https://github.com/torvalds/linux/commit/298e20ba8c197e8d429a6c8671550c41c7919033 https://github.com/torvalds/linux/commit/30b11ee9ae23d78de66b9ae315880af17a64ba83 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#778157: user-mode-linux: ftbfs with GCC-5
Processing control commands: tags -1 + fixed-upstream Bug #778157 [src:user-mode-linux] user-mode-linux: ftbfs with GCC-5 Added tag(s) fixed-upstream. -- 778157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790132: nailgun-agent: depends on ohai ( 7) but sid has 8.4.0
Antonio, Excuse me, but did you just upload nailgun-agent without even communicating with me? This isn't the normal way for a package which you may not know. What exactly did you do in the package? Just fixing the dependency isn't enough, and some upstream work has to be done, you're aware of that, right? Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792659: marked as done (tesseract-ocr-dev: fails to install, trying to overwrite other packages files: /usr/share/tesseract-ocr/language-specific.sh)
Your message dated Fri, 17 Jul 2015 23:05:13 + with message-id e1zgegr-0004fi...@franck.debian.org and subject line Bug#792659: fixed in tesseract 3.04.00-4 has caused the Debian Bug report #792659, regarding tesseract-ocr-dev: fails to install, trying to overwrite other packages files: /usr/share/tesseract-ocr/language-specific.sh 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.) -- 792659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tesseract-ocr-dev Version: 3.04.00-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package tesseract-ocr-dev. (Reading database ... (Reading database ... 7610 files and directories currently installed.) Preparing to unpack .../tesseract-ocr-dev_3.04.00-3_all.deb ... Unpacking tesseract-ocr-dev (3.04.00-3) ... dpkg: error processing archive /var/cache/apt/archives/tesseract-ocr-dev_3.04.00-3_all.deb (--unpack): trying to overwrite '/usr/share/tesseract-ocr/language-specific.sh', which is also in package libtesseract-dev 3.04.00-3 Errors were encountered while processing: /var/cache/apt/archives/tesseract-ocr-dev_3.04.00-3_all.deb cheers, Andreas tesseract-ocr-dev_3.04.00-3.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: tesseract Source-Version: 3.04.00-4 We believe that the bug you reported is fixed in the latest version of tesseract, 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 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeff Breidenbach j...@debian.org (supplier of updated tesseract package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Jul 2015 22:25:49 + Source: tesseract Binary: tesseract-ocr-dev libtesseract-dev libtesseract3 tesseract-ocr Architecture: source amd64 all Version: 3.04.00-4 Distribution: unstable Urgency: medium Maintainer: Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com Changed-By: Jeff Breidenbach j...@debian.org Description: libtesseract-dev - Development files for the tesseract command line OCR tool libtesseract3 - Tesseract OCR library tesseract-ocr - Tesseract command line OCR tool tesseract-ocr-dev - transitional dummy package Closes: 792659 Changes: tesseract (3.04.00-4) unstable; urgency=medium . * Fix file overwrite problem (closes: #792659) Checksums-Sha1: aa09ac87a298ae47da39682b1d31e0de7325609d 2064 tesseract_3.04.00-4.dsc d5bfad8c6eff0c4d713e0de911351dd2e5ec33af 6747 tesseract_3.04.00-4.diff.gz e25bdf663dcb3fd6d103ce5973c406aaa9dc4575 1386914 libtesseract-dev_3.04.00-4_amd64.deb 661c65f4203f2f26b5ffcf0c20597c2396fd8cd9 1134766 libtesseract3_3.04.00-4_amd64.deb bfb772717d8be32529ab38050b33d5ef86c915a5 12406 tesseract-ocr-dev_3.04.00-4_all.deb 041d9f106ebfa08fc432bf4ef01be70d600f98df 141674 tesseract-ocr_3.04.00-4_amd64.deb Checksums-Sha256: 316337d3f0312837a281c39df201b9a58bed19abfabd268d7a3a7f2780cd0752 2064 tesseract_3.04.00-4.dsc 644d2d5dff25045b6d10da06b1cc353cceb29a25c84d1d9921416646e61c8c95 6747 tesseract_3.04.00-4.diff.gz 0122f6d3cce7e05081ed2fa2b9ea677610579bdf66596921e8e3d9dd7f0ffb45 1386914 libtesseract-dev_3.04.00-4_amd64.deb 49ea3e72639dea4d6047803fc7e58495873d83ae4f255d74656ec0720f62fe68 1134766 libtesseract3_3.04.00-4_amd64.deb bc0f338188f82dcc3d84f38330728012b69d97e4bf14080856e783ee504b8bb5 12406 tesseract-ocr-dev_3.04.00-4_all.deb 9cb50df686cfde1d8e46eca02065a77449d4663ba7abbbde90133061e2a4d5b7 141674 tesseract-ocr_3.04.00-4_amd64.deb Files: 7157bc83466b7d48f9bde56fb99b62a4 2064 graphics optional tesseract_3.04.00-4.dsc 8d31b4589c44cf8f6d33aa8151cc4930 6747 graphics optional tesseract_3.04.00-4.diff.gz 8cfdf6db2f59136d4ea4dfa2fd0799c8 1386914 libdevel optional
Bug#777853: patch for gcc5 bug
tags 777853 + patch
thanks
Here's a fix for GCC5 build issue. Added extern to inline functions in
ftfil.c
Upstream may prefer to move to C99 instead, please see section
Different semantics for inline functions at
https://gcc.gnu.org/gcc-5/porting_to.html for more background.
--
Alexander Balderson
Linux for HP Helion OpenStack, Hewlett-Packard
--- flow-tools-0.68/lib/ftfil.c 2015-07-17 19:46:14.52000 +
+++ flow-tools-0.68.fixed/lib/ftfil.c 2015-07-17 20:57:52.13600 +
@@ -547,7 +547,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_src_as(struct ftfil_lookup_as *lookup, char *rec,
+extern inline int eval_match_src_as(struct ftfil_lookup_as *lookup, char *rec,
struct fts3rec_offsets *fo)
{
u_int16 *src_as;
@@ -574,7 +574,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_dst_as(struct ftfil_lookup_as *lookup, char *rec,
+extern inline int eval_match_dst_as(struct ftfil_lookup_as *lookup, char *rec,
struct fts3rec_offsets *fo)
{
u_int16 *dst_as;
@@ -602,7 +602,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_prot(struct ftfil_lookup_ip_prot *lookup, char *rec,
+extern inline int eval_match_ip_prot(struct ftfil_lookup_ip_prot *lookup, char *rec,
struct fts3rec_offsets *fo)
{
u_int8 *ip_prot;
@@ -630,7 +630,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_src_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
+extern inline int eval_match_ip_src_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 *src_mask;
@@ -658,7 +658,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_dst_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
+extern inline int eval_match_ip_dst_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 *dst_mask;
@@ -686,7 +686,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_tos(struct ftfil_lookup_ip_tos *lookup,
+extern inline int eval_match_ip_tos(struct ftfil_lookup_ip_tos *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 tos;
@@ -714,7 +714,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_marked_tos(struct ftfil_lookup_ip_tos *lookup,
+extern inline int eval_match_ip_marked_tos(struct ftfil_lookup_ip_tos *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 marked_tos;
@@ -743,7 +743,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_tcp_flags(struct ftfil_lookup_ip_tcp_flags *lookup,
+extern inline int eval_match_ip_tcp_flags(struct ftfil_lookup_ip_tcp_flags *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 tcp_flags;
@@ -772,7 +772,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_src_port(struct ftfil_lookup_ip_port *lookup,
+extern inline int eval_match_ip_src_port(struct ftfil_lookup_ip_port *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int16 *src_port;
@@ -799,7 +799,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_ip_dst_port(struct ftfil_lookup_ip_port *lookup,
+extern inline int eval_match_ip_dst_port(struct ftfil_lookup_ip_port *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int16 *dst_port;
@@ -827,7 +827,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_src_if_index(struct ftfil_lookup_if_index *lookup,
+extern inline int eval_match_src_if_index(struct ftfil_lookup_if_index *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int16 *src_if_index;
@@ -854,7 +854,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_dst_if_index(struct ftfil_lookup_if_index *lookup,
+extern inline int eval_match_dst_if_index(struct ftfil_lookup_if_index *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int16 *dst_if_index;
@@ -882,7 +882,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_engine_id(struct ftfil_lookup_engine *lookup,
+extern inline int eval_match_engine_id(struct ftfil_lookup_engine *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 *engine_id;
@@ -910,7 +910,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_engine_type(struct ftfil_lookup_engine *lookup,
+extern inline int eval_match_engine_type(struct ftfil_lookup_engine *lookup,
char *rec, struct fts3rec_offsets *fo)
{
u_int8 *engine_type;
@@ -937,7 +937,7 @@
* returns: FT_FIL_MODE_PERMIT
* FT_FIL_MODE_DENY
*/
-inline int eval_match_flows(struct ftfil_lookup_counter *lookup, char *rec,
+extern inline int
Processed: patch for gcc5 bug
Processing commands for cont...@bugs.debian.org: tags 777853 + patch Bug #777853 [src:flow-tools] flow-tools: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 777853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792741: [sqlitebrowser]
Package: sqlitebrowser Severity: grave --- Please enter the report below this line. --- Hi, I have installed sqliteborwser and synaptic declares that should exists the file /usr/bin/sqlitebrowser but it is not present! So this software is not usable Command 504 of 6 $ls /usr/bin/sq* /usr/bin/sq/usr/bin/sqlsharp /usr/bin/sqlt-diagram /usr/bin/sqlt-diff-old /usr/bin/sqlt-graph /usr/bin/squiggle /usr/bin/sqlmetal /usr/bin/sqlt /usr/bin/sqlt-diff /usr/bin/sqlt-dumper/usr/bin/squeak Please contact me if you need more information Best Marco --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable-updates ftp.it.debian.org 500 stable security.debian.org 500 stable repo.wuala.com 500 stable ftp.it.debian.org 500 stable apt.spideroak.com 500 jessie linux.dropbox.com 500 debian packages.linuxmint.com 100 jessie-backports ftp.it.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790132: marked as done (nailgun-agent: depends on ohai ( 7) but sid has 8.4.0)
Your message dated Fri, 17 Jul 2015 21:39:37 + with message-id e1zgdm1-0006gk...@franck.debian.org and subject line Bug#790132: fixed in nailgun-agent 3.9.2-1.1 has caused the Debian Bug report #790132, regarding nailgun-agent: depends on ohai ( 7) but sid has 8.4.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 790132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nailgun-agent Version: 3.9.2-1 Severity: serious Tags: sid stretch Your package depends on ohai ( 7), but ohai is at 8.4.0-1 in sid. Please update your package to work with that. Emilio ---End Message--- ---BeginMessage--- Source: nailgun-agent Source-Version: 3.9.2-1.1 We believe that the bug you reported is fixed in the latest version of nailgun-agent, 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 790...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro terce...@debian.org (supplier of updated nailgun-agent 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, 17 Jul 2015 17:54:36 -0300 Source: nailgun-agent Binary: nailgun-agent Architecture: source all Version: 3.9.2-1.1 Distribution: unstable Urgency: medium Maintainer: Thomas Goirand z...@debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: nailgun-agent - collects a server’s hardware information and submits it Closes: 790132 Changes: nailgun-agent (3.9.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop strict dependency on ohai ( 7) (Closes: #790132) Checksums-Sha1: 60e7caa7e3f3deb34d72a9ff6770501f39ac3612 1919 nailgun-agent_3.9.2-1.1.dsc d969c0e9bee4018da09394bcdcc8998d3358104e 1812 nailgun-agent_3.9.2-1.1.debian.tar.xz d7a14885a28cc9196d09105f3f1cecd87d8d1520 7984 nailgun-agent_3.9.2-1.1_all.deb Checksums-Sha256: 58c9708d05c3663b10fd59b4a3ddc54d10a4824cff086967dc44762e56e0ee1d 1919 nailgun-agent_3.9.2-1.1.dsc d6ebdfb100b143d8a58f3af0aaec2eb3634c41b6c8c4960e6af6388dbae66503 1812 nailgun-agent_3.9.2-1.1.debian.tar.xz 8e164dc4a02934f9b0ff9eeca6c6ca6edd287154d43c8b879c4ecdbfc02f 7984 nailgun-agent_3.9.2-1.1_all.deb Files: 57efe5f543697940d17080d150c5ee4b 1919 net extra nailgun-agent_3.9.2-1.1.dsc 6012cf98a35239b56d421071166e6c89 1812 net extra nailgun-agent_3.9.2-1.1.debian.tar.xz d8bc59e9fbb38a64e0b6b67dbf4e6f50 7984 net extra nailgun-agent_3.9.2-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqWw/AAoJEPwNsbvNRgveBjkP/2ie2kIOuuZCTbvEljPPiBJY I3MTptEg9pPtzXkjmCqkuobedcjZyOoB/gMEVBbFTOfvoK8OE20vpNec6YLhEE+U V5QmmxgNO/610fwdPSh/YMO+i+ityP8kltmluXz7Y7wQcyiSY8V1QZrwcRwNW894 2OP5eLlOMBVszexNCQ87axe4hVnGEGKnDv4mK2wPC61kwwu6qHXqGrYtjrBgJvPO KrPgYBRRd7lr6H9V4jPIOonUnveiraEOVWIMQquZTYyje5BovYV4D2Ws2yoQwAij H7DNBFouUUoUyjdkpjyv76F5X5g9PcLH29FtqpkFEMTyShM2A6PdAtnnua63uGn5 k5BDuf9CSab4ocd8vCrYYpzjyHMbLA1OPT5KIvIYoea1euZ6J8QnM3oASmYgz89Z q/acq1/OWgNRQGu4G5CR9Xh6u91NMui5r97OoD7SAVCWJgeVt6XRbIaapJOENkBL +Uo+koMsqoAu0ZvTc0yPOl2rJHs05aEk3a+S7UhzTTOGHw75k6Q2KK9a+jHrHdZn o/QWyUo43zgtCY9b8D03fAayV3opGzpJDbFa6TXrMrgwxDsSKvrxs9dcEsiqN7ol OtMm+se20wTrY20e22apBCmXiOSBiEbTWUMrWIFr0VyuAuj7P1zg3mujP7OEe+CT CMXjUYcsWf+rtvv1O+of =8lB3 -END PGP SIGNATUREEnd Message---
Bug#790132: nailgun-agent: depends on ohai ( 7) but sid has 8.4.0
Hello Thomas,
On Sat, Jul 18, 2015 at 12:37:20AM +0200, Thomas Goirand wrote:
Antonio,
Excuse me, but did you just upload nailgun-agent without even
communicating with me? This isn't the normal way for a package which you
may not know.
the package
a) was blocking the whole chef stack from migrating to testing for
almost a month
b) was already uninstallable in unstable since then
c) had a corresponding RC bug report for 20 days without any sign of a
reaction
What exactly did you do in the package?
diff -Nru nailgun-agent-3.9.2/debian/control nailgun-agent-3.9.2/debian/control
--- nailgun-agent-3.9.2/debian/control 2014-11-18 21:19:56.0 -0200
+++ nailgun-agent-3.9.2/debian/control 2015-07-17 17:56:11.0 -0300
@@ -11,7 +11,7 @@
Package: nailgun-agent
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
-Depends: ohai ( 7),
+Depends: ohai,
ruby-cstruct,
ruby-httpclient,
ruby-json,
(#792737)
Just fixing the dependency isn't enough, and some upstream work has
to be done, you're aware of that, right?
I did test all the data that nailgun-agent uses from ohai, and all that
I could test (i.e. what my system actually provided) is still there.
I didn't mean to cause any problems. If you think I should, I can do a
new upload reverting my change without any problem.
--
Antonio Terceiro terce...@debian.org
signature.asc
Description: Digital signature
