Bug#789890: ntop: RRD: Disabled - unable to create base directory
Package: ntop Version: 3:5.0.1+dfsg1-2.1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages ntop depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii libc6 2.19-18 ii libgdbm3 1.8.3-13.1 ii libgeoip1 1.6.5-2 ii libpcap0.8 1.7.3-1 ii libpython2.7 2.7.10-2 ii librrd41.4.8-1.3+b2 ii net-tools 1.60-26+b1 ii ntop-data 3:5.0.1+dfsg1-2.1 ii passwd 1:4.2-3 ii python-mako1.0.0+dfsg-0.1 ii zlib1g 1:1.2.8.dfsg-2+b1 ntop recommends no packages. Versions of packages ntop suggests: ii graphviz 2.38.0-9 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 -- debconf information: ntop/admin_password: (password omitted) ntop/admin_password_again: (password omitted) * ntop/interfaces: eth1, eth0 ntop/password_empty: ntop/password_mismatch: ntop/user: ntop ntop/password_reset: false Comment: Thu Jun 25 08:23:10 2015 RRD: Welcome to Round-Robin Database. (C) 2002-12 by Luca Deri. Thu Jun 25 08:23:10 2015 NETFLOW: Welcome to NetFlow.(C) 2002-12 by Luca Deri Thu Jun 25 08:23:10 2015 Calling plugin start functions (if any) Thu Jun 25 08:23:10 2015 RRD: Welcome to the RRD plugin Thu Jun 25 08:23:10 2015 RRD: Mask for new directories is 0700 Thu Jun 25 08:23:10 2015 RRD: Mask for new files is 0066 Thu Jun 25 08:23:10 2015 THREADMGMT: RRD: Started thread (t2972695360) for data collection Thu Jun 25 08:23:10 2015 THREADMGMT[t2972695360]: RRD: Data collection thread starting [p5769] Thu Jun 25 08:23:10 2015 THREADMGMT[t3057871424]: ntop RUNSTATE: INITNONROOT(3) Thu Jun 25 08:23:10 2015 Now running as requested user 'nobody' (65534:65534) Thu Jun 25 08:23:10 2015 Note: Reporting device initally set to 0 [eth0] (merged) Thu Jun 25 08:23:10 2015 **WARNING** INIT: Unable to create pid file (/var/lib/ntop/ntop.pid) Thu Jun 25 08:23:10 2015 THREADMGMT[t3057871424]: ntop RUNSTATE: RUN(4) Thu Jun 25 08:23:10 2015 THREADMGMT[t3037649728]: SFP: Fingerprint scan thread running [p5769] Thu Jun 25 08:23:10 2015 THREADMGMT[t3027237696]: SIH: Idle host scan thread running [p5769] Thu Jun 25 08:23:10 2015 THREADMGMT[t2964302656]: NPS(1): Started thread for network packet sniffing [eth0] Thu Jun 25 08:23:10 2015 THREADMGMT[t2964302656]: NPS(eth0): pcapDispatch thread starting [p5769] Thu Jun 25 08:23:10 2015 THREADMGMT[t2964302656]: NPS(eth0): pcapDispatch thread running [p5769] Thu Jun 25 08:23:10 2015 CHKVER: Version file is from 'version.ntop.org' Thu Jun 25 08:23:10 2015 CHKVER: as of date is '2012-10-16T11:00:47' Thu Jun 25 08:23:10 2015 CHKVER: This version of ntop is the CURRENT stable version Thu Jun 25 08:23:20 2015 **ERROR** RRD: Disabled - unable to create base directory (err 13, /var/lib/ntop/rrd) End comment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789894: libvolk1.0-dev and libvolk-dev: error when trying to install together
Package: libvolk-dev,libvolk1.0-dev Version: libvolk-dev/3.7.5-5 Version: libvolk1.0-dev/1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-06-25 Architecture: amd64 Distribution: sid 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 gcc-5-base:amd64. (Reading database ... 10902 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.1.1-12_amd64.deb ... Unpacking gcc-5-base:amd64 (5.1.1-12) ... Setting up gcc-5-base:amd64 (5.1.1-12) ... (Reading database ... 10909 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.1.1-12_amd64.deb ... Unpacking libstdc++6:amd64 (5.1.1-12) over (4.8.2-19) ... Setting up libstdc++6:amd64 (5.1.1-12) ... Processing triggers for libc-bin (2.19-18) ... Selecting previously unselected package libboost-system1.55.0:amd64. (Reading database ... 10923 files and directories currently installed.) Preparing to unpack .../libboost-system1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-system1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-filesystem1.55.0:amd64. Preparing to unpack .../libboost-filesystem1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-filesystem1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-program-options1.55.0:amd64. Preparing to unpack .../libboost-program-options1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-program-options1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-test1.55.0:amd64. Preparing to unpack .../libboost-test1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-test1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.24-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.24-1) ... Selecting previously unselected package libvolk0.0.0:amd64. Preparing to unpack .../libvolk0.0.0_3.7.5-5_amd64.deb ... Unpacking libvolk0.0.0:amd64 (3.7.5-5) ... Selecting previously unselected package libvolk-bin. Preparing to unpack .../libvolk-bin_3.7.5-5_amd64.deb ... Unpacking libvolk-bin (3.7.5-5) ... Selecting previously unselected package libvolk-dev. Preparing to unpack .../libvolk-dev_3.7.5-5_amd64.deb ... Unpacking libvolk-dev (3.7.5-5) ... Selecting previously unselected package libvolk1.0:amd64. Preparing to unpack .../libvolk1.0_1.0-1_amd64.deb ... Unpacking libvolk1.0:amd64 (1.0-1) ... Selecting previously unselected package libvolk1.0-dev. Preparing to unpack .../libvolk1.0-dev_1.0-1_amd64.deb ... Unpacking libvolk1.0-dev (1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libvolk1.0-dev_1.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/volk.pc', which is also in package libvolk-dev 3.7.5-5 Processing triggers for man-db (2.7.0.2-5) ... Errors were encountered while processing: /var/cache/apt/archives/libvolk1.0-dev_1.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 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/lib/x86_64-linux-gnu/libvolk.so /usr/lib/x86_64-linux-gnu/pkgconfig/volk.pc This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://qa.debian.org/dose/file-overwrites.html. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789898: bs1770gain: Port it to libav to allow it to be backported to stable
Package: bs1770gain Version: 0.4.2-1 Severity: wishlist The bs1770gain tool only build with the ffmpeg version of libav, because it require support for channels. The channel support for libav is requested in URL: http://bugs.debian.org/788609 , but even if libav would get such support, it is unlikely to get it in Debian stable (aka Jessie). Because of this, it would be great if bs1770gain were ported to libav without channel support. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789897: failure on upgrade, file conflict with ndiff
Package: zenmap Version: 6.47-5 Severity: serious Todays upgrade of zenmap failed: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: ndiff zenmap 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 898 kB of archives. After this operation, 66.6 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ftp.de.debian.org/debian/ sid/main ndiff all 6.47-5 [257 kB] Get:2 http://ftp.de.debian.org/debian/ sid/main zenmap all 6.47-5 [642 kB] Fetched 898 kB in 0s (906 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done (Reading database ... 307698 files and directories currently installed.) Preparing to unpack .../archives/ndiff_6.47-5_all.deb ... Unpacking ndiff (6.47-5) over (6.47-3) ... dpkg: error processing archive /var/cache/apt/archives/ndiff_6.47-5_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/ndiff.py', which is also in package zenmap 6.47-3 Preparing to unpack .../archives/zenmap_6.47-5_all.deb ... Unpacking zenmap (6.47-5) over (6.47-3) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for bamfdaemon (0.2.118-1+b1) ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for gnome-menus (3.13.3-6) ... Processing triggers for mime-support (3.58) ... Processing triggers for desktop-file-utils (0.22-1) ... Errors were encountered while processing: /var/cache/apt/archives/ndiff_6.47-5_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Looks like zenmap is missing a proper versioned Breaks/Replaces: See section 7.6.1: https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces Cheers, Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zenmap depends on: ii nmap6.47-5 ii python 2.7.9-1 ii python-gobject 3.16.2-1 ii python-gtk2 2.24.0-4 Versions of packages zenmap recommends: ii gksu 2.0.2-9 zenmap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
Hi, On Wed, Jun 24, 2015 at 10:35:16PM -0400, Elana Hashman wrote: On 2015-06-15 14:47, Guido Günther wrote: On Fri, Jun 12, 2015 at 02:09:31PM +0200, Guido Günther wrote: Please somebody who's seeing this problem apply the patch mentioned by Han and report the error message you see there. Without me being able to reproduce this is just not progressing anywhere. The snapshot at http://honk.dyn.sigxcpu.org/projects/libvirt/snapshots/ has the necessary patch to (hopefully) get a better error message. Could you please try this version? Cheers, -- Guido Hi Guido, I've installed the packages you provided in the snapshot and the error message was updated. Furthermore, the error message is accurate now: it helped me discover the machine I was running on didn't actually have hardware virtualization capability, which was specified in the XML. (Whoops!) Thanks a lot for testing! I'll push that change into the next point release. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789901: gnome-software: software sources dialog says that none of the sources have packages installed
Package: gnome-software Version: 3.14.2-1 Severity: normal As you can see in this screenshot, the software sources dialog says that none of the sources have packages installed. https://people.debian.org/~pabs/tmp/gnome-software-sources-broken.png -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-software depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii gnome-software-common3.14.2-1 ii gsettings-desktop-schemas3.16.1-1 ii libappstream-glib7 0.4.0-1 ii libatk1.0-0 2.16.0-2 ii libc62.19-18 ii libcairo-gobject21.14.2-2 ii libcairo21.14.2-2 ii libgdk-pixbuf2.0-0 2.31.4-2 ii libglib2.0-0 2.44.1-1 ii libgnome-desktop-3-103.16.2-2 ii libgtk-3-0 3.16.4-2 ii libpackagekit-glib2-18 1.0.6-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libsoup2.4-1 2.50.0-2 ii libsqlite3-0 3.8.10.2-1 gnome-software recommends no packages. gnome-software suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#789905: calypso: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library
Package: calypso Version: 1.4 Severity: important Howdy, The ‘python-daemon’ library has in the past included an internal ‘daemon.pidlockfile’ module for its own use. That functionality has migrated to the ‘lockfile’ distribution (packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’) version 0.9 and later. In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’ module does not exist. Code which attempts to import it will fail. A simple inspection (using ‘grep’) of the Python source for this package shows it is using the obsolete ‘daemon.pidlockfile’ API, and will fail with an ImportError. If the package is unusable without that API, then this bug report should be upgraded to “Severity: serious”. You can fix this bug by: * Work with upstream to remove references to ‘daemon.pidlockfile’, and to migrate to the ‘lockfile.pidlockfile’ API. * Package the new upstream version of this package. * Add to this package a “Depends: python-lockfile (= 0.9)” and/or “Depends: python3-lockfile (= 0.9)”. * Release that package to Debian Sid. If you've already done this, great! Please let me know so that I can keep track of which packages are affected. -- \“My doctor told me to stop having intimate dinners for four. | `\ Unless there are three other people.” —Orson Welles | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789906: pybit: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library
Package: pybit Version: 1.0.0-2.1 Severity: important Howdy, The ‘python-daemon’ library has in the past included an internal ‘daemon.pidlockfile’ module for its own use. That functionality has migrated to the ‘lockfile’ distribution (packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’) version 0.9 and later. In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’ module does not exist. Code which attempts to import it will fail. A simple inspection (using ‘grep’) of the Python source for this package shows it is using the obsolete ‘daemon.pidlockfile’ API, and will fail with an ImportError. If the package is unusable without that API, then this bug report should be upgraded to “Severity: serious”. You can fix this bug by: * Work with upstream to remove references to ‘daemon.pidlockfile’, and to migrate to the ‘lockfile.pidlockfile’ API. * Package the new upstream version of this package. * Add to this package a “Depends: python-lockfile (= 0.9)” and/or “Depends: python3-lockfile (= 0.9)”. * Release that package to Debian Sid. If you've already done this, great! Please let me know so that I can keep track of which packages are affected. -- \“My doctor told me to stop having intimate dinners for four. | `\ Unless there are three other people.” —Orson Welles | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788321: elinks: FTBFS on arm64
Hi Wookey,
On Thu, Jun 25, 2015 at 01:07:08AM +0100, Wookey wrote:
Moritz Mühlenhoff j...@inutil.org wrote:
I have been holding this back since dh compat level 10 is supposed
to do that by default
This has been mentioned as a possible enhancement of debhelper but is
not scheduled or certain yet:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480576#35
so we get to do it manually for a while longer.
Ah, ok. I thought that was done already.
Edmund Grimley Evans edmund.grimley.ev...@gmail.com wrote:
I was able to build successfully if I replaced
--with autoreconf
with either
--with autotools-dev
or
--with autoreconf,autotools-dev
The latter is correct. See
https://wiki.debian.org/Autoreconf#dh-autoreconf_and_autotools-dev
This package uses autoconf, but not libtool or automake. So
dh_autoreconf will not update config.{sub,guess} on its own.
autotools-dev also needs to be installed and used.
I've just confirmed that doing this does indeed fix matters
(autotools-dev is still in the control file so the above one-line
change is all that's needed). Patch attached anyway, as I've done one.
What I don't understand is why elinks built before on arm64, e.g. in
jessie?
I'm happy to NMU this if you like.
Thanks, but I'll do it this weekend, just haven't come around to it yet
(and want to fold in another fix as well).
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789892: gopher: Gophermap lines are not aligned correctly
Package: gopher Version: 3.0.13 Severity: minor Dear Maintainer, as I was setting up the gopherhole of our hackerspace (gopher://gopher.binary-kitchen.de), I was using figlet to add some nice titles to my main gophermap, but one line was always getting not aligned correctly. I checked again if the gophermap was correct, and indeed it was (cat gave me the inteded result). So I tried it with some other gopher clients. Lynx and the floodgap gopher proxy giving me the right result. Here are the Screenshots with the different clients: Debian gopher: http://i.imgur.com/uNhijv9.png Lynx: http://i.imgur.com/BvVwkFE.png floodgap: http://i.imgur.com/K5k0ts6.png As Gopher is a fast-growing emerging technology, I find it important that Debian has a working standard gopher client in its repos. Greetings Phil -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gopher depends on: ii libc62.19-18 ii libncurses5 5.9+20140913-1+b1 gopher recommends no packages. gopher suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789897: Acknowledgement (failure on upgrade, file conflict with ndiff)
Control: reassign -1 ndiff Control: found -1 6.47-5 Control: retitle -1 failure on upgrade, file conflict with zenmap Actually, the bug is in ndiff. I was mislead by this changelog message: * Moved ndiff.py to zenmap (Closes: #789776) Looks like this was actually the other way around. The ndiff.py file was moved from zenmap to ndiff and ndiff doesn't have a proper Breaks/Replaces against zenmap. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#789882: doomsday-compat doesn't handle heretic hexen alternatives
Control: tags -1 +patch Hi Alexandre and Michael, Am Donnerstag, den 25.06.2015, 06:49 +0200 schrieb Alexandre Detiste: I can provide a patch, but this would obviously conflict with the one linked to #787985. not necessarily. We don't need to set gamemode but can provide a fake IWAD if no -iwad parameter was given based on the executable name. This would e.g. make it possible to run hexen -iwad doom.wad and it will start Doom, but I think this is somehow expected. The attached patch applies on top of the ones provided in #787985, #788053 and #788058. Cheers, Fabian diff --git a/debian/doomsday-compat b/debian/doomsday-compat index 998c81d..23ee96f 100755 --- a/debian/doomsday-compat +++ b/debian/doomsday-compat @@ -69,6 +69,21 @@ do cmdline=$cmdline $arg done +# if no -iwad parameter is given, guess from executable name +if [ -z $iwadfile ] +then + case $(basename $0) in + heretic) + iwadfile=heretic.wad + iwadpath=$iwaddir/$iwadfile + ;; + hexen) + iwadfile=hexen.wad + iwadpath=$iwaddir/$iwadfile + ;; + esac +fi + case $(echo $iwadfile | tr '[:upper:]' '[:lower:]') in doom1.wad) gamemode=doom1-share @@ -138,12 +153,23 @@ case $(echo $pwadfile | tr '[:upper:]' '[:lower:]') in ;; esac +# fall back to alternatives if [ $gamemode = doom2 \ -a ! -f $iwaddir/doom2.wad \ -a ! -f $iwaddir/doom2f.wad \ -a -f $iwaddir/freedoom2.wad ] then gamemode=freedoom2 +elif [ \( $gamemode = heretic -o $gamemode = heretic-ext \) \ + -a ! -f $iwaddir/heretic.wad \ + -a -f $iwaddir/heretic1.wad ] +then + gamemode=heretic-share +elif [ $gamemode = hexen \ + -a ! -f $iwaddir/hexen.wad \ + -a -f $iwaddir/hexendemo.wad ] +then + gamemode=hexen-demo fi if [ -n $pwadpath ] signature.asc Description: This is a digitally signed message part
Bug#789900: RM: nautilus-open-terminal -- ROM; ROM; obsoleted by gnome-terminal
Package: ftp.debian.org Severity: normal Hi there, the nautilus-open-terminal package provides a plugin for Nautilus that adds an Open in Terminal item to the context menu for directories. However, meanwhile this functionality has been imported directly into gnome-terminal [1]. Thus, if both nautilus-open-terminal and a recent gnome-terminal package are installed, the Open in Terminal context menu item will appear twice. While this is harmless, it renders the nautilus-open-terminal package obsolete and we think it should be removed from Debian. The maintainer of the nautilus-open-terminal package agrees with this in #766919 [2]. Appropriate Conflicts and Replaces relations will be added to the gnome-terminal package in the next upload. Thank you very much, Fabian [1] https://git.gnome.org/browse/gnome-terminal/commit/src/terminal-nautilus.c?id=0ffe6b51a132ef9b28c58283c4b177f4a82f327a [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766919#40 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789899: evolution-ews: Office 365 account creation unsuccessful and hangs Evolution without evolution-mapi package
Package: evolution-ews Version: 3.12.9~git20141130.278fe7-1+b1 Severity: important Dear Maintainer, I encountered a problem while creating an Office 365 account. I went to Edit-Preferences-Mail Accounts-Add and entered the following configurations: Server type: Exchange Web Services username: tvtuo...@ad.helsinki.fi host url: https://outlook.office365.com/EWS/Exchange.asmx - Fetch URL Everything seemed to work but the account did not appear on the list. I tried this several times and closed and reopended the Evolution also without success. After my attemts I found some Evolution back processes with ps -ef | grep evolution and killed those. After that I restarted Evolution and now the accounts that I had created and all of them started to fetch new mail but it did not seem to work and evolution would hang if I clicked any of the accounts on the list on the left. After restarting Evolution I was able to re-enter Edit-Preferences and I tried deleting the extra accounts. The account would disappear from the list but Evolution would hang again and after restart the account would still be on the list. I was able to resolve all the above issues by installing evolution-mapi package. So it seems that at least with Office 365 accounts the evolution-ews package requires the evolution-mapi package. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_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 evolution-ews depends on: ii evolution 3.12.9~git20141130.241663-1+b1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libcamel-1.2-49 3.12.9~git20141128.5242b0-2+deb8u2 ii libebackend-1.2-7 3.12.9~git20141128.5242b0-2+deb8u2 ii libebook-contacts-1.2-0 3.12.9~git20141128.5242b0-2+deb8u2 ii libecal-1.2-16 3.12.9~git20141128.5242b0-2+deb8u2 ii libedata-book-1.2-203.12.9~git20141128.5242b0-2+deb8u2 ii libedata-cal-1.2-23 3.12.9~git20141128.5242b0-2+deb8u2 ii libedataserver-1.2-18 3.12.9~git20141128.5242b0-2+deb8u2 ii libenchant1c2a 1.6.0-10.1 ii libevolution3.12.9~git20141130.241663-1+b1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk-3-0 3.14.5-1 ii libgtkhtml-4.0-04.8.5-1 ii libgtkhtml-editor-4.0-0 4.8.5-1 ii libical1a 1.0-1.3 ii libjavascriptcoregtk-3.0-0 2.4.8-2 ii libmspack0 0.5-1 ii libnspr42:4.10.7-1 ii libnss3 2:3.17.2-1.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libsecret-1-0 0.18-1+b1 ii libsoup2.4-12.48.0-1 ii libsqlite3-03.8.7.1-1+deb8u1 ii libwebkitgtk-3.0-0 2.4.8-2 ii libxml2 2.9.1+dfsg1-5 evolution-ews recommends no packages. evolution-ews suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789832: unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64
Control: tag -1 - moreinfo unreproducible Control: severity -1 important Hi, solo-debianb...@goeswhere.com wrote: On Thu, Jun 25, 2015 at 12:03:04AM +0200, Axel Beckert wrote: t/undo.t ... ok t/unexpected-cases.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/98 subtests thanks for the report, but I couldn't reproduce this, neither with 0.3.3 nor with the HEAD of the git repository. And https://reproducible.debian.net/rb-pkg/unstable/amd64/unburden-home-dir.html shows different tests failing, but not t/unexpected-cases.t. Can you please explain a little bit more about your setup? pbuilder or sbuild? On which file system where the tests run? (And if the reporting machine was not the same as the machine where the issue happend: Which locale was set? Which init system was used? Which kernel was running?) etc. Hah. After far too much staring, the test which is failing for me is: ok 93 - Make list file t/zo4O_qcnum/list unreadable ok 94 - Call 'perl bin/unburden-home-dir -C t/zo4O_qcnum/config -c /dev/null -L t/zo4O_qcnum/list -l /dev/null' not ok 95 - Check STDERR # Failed test 'Check STDERR' # at t/lib/Test/UBH.pm line 260. # --- Got # +++ Expected # @@ -1 +1,2 @@ # -'' # +'List file t/8mn4dawfHl/list isn\'t readable, skipping at # unburden-home-dir line n. # +' # Looks like you failed 1 test of 98. It's running chmod foo cat foo, and expecting it to fail. It succeeds for me as I have a better simulation of root: I'm running the build as very-nearly root on a VM. (root in an unpriviliged LXC container). Interesting case. The full build log isn't much more useful; sorry for missing some important parts in the initial report: https://paste.debian.net/260610/ Yeah, the above already suffices. Thanks for the details. My specific bug is probably invalid, in this case? Not sure. Will have to investigate. I've allowed myself to at least downgrade it to non-rc. I don't think we expect the builds to pass as root. Well, actually we do expect that. :-) But then again that test should still fail in that case. Weird test, though. Well, it's a test which checks if unburden-home-dir has regressions in error handling. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789618: Shorcuts associated to launchers stopped working
I can confirm this bug on a recently updated testing box. Same situation: no alternative keyboard layouts (I'm using a Belgian keyboard layout) and none of the launcher related keyboard shortcuts work. Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789911: python-gear: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library
Package: python-gear Version: 0.5.5-2 Severity: important Howdy, The ‘python-daemon’ library has in the past included an internal ‘daemon.pidlockfile’ module for its own use. That functionality has migrated to the ‘lockfile’ distribution (packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’) version 0.9 and later. In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’ module does not exist. Code which attempts to import it will fail. A simple inspection (using ‘grep’) of the Python source for this package shows it is using the obsolete ‘daemon.pidlockfile’ API, and will fail with an ImportError. If the package is unusable without that API, then this bug report should be upgraded to “Severity: serious”. You can fix this bug by: * Work with upstream to remove references to ‘daemon.pidlockfile’, and to migrate to the ‘lockfile.pidlockfile’ API. * Package the new upstream version of this package. * Add to this package a “Depends: python-lockfile (= 0.9)” and/or “Depends: python3-lockfile (= 0.9)”. * Release that package to Debian Sid. If you've already done this, great! Please let me know so that I can keep track of which packages are affected. -- \“My doctor told me to stop having intimate dinners for four. | `\ Unless there are three other people.” —Orson Welles | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789907: lava-server: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library
Package: lava-server Version: 2015.06-1 Severity: important Howdy, The ‘python-daemon’ library has in the past included an internal ‘daemon.pidlockfile’ module for its own use. That functionality has migrated to the ‘lockfile’ distribution (packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’) version 0.9 and later. In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’ module does not exist. Code which attempts to import it will fail. A simple inspection (using ‘grep’) of the Python source for this package shows it is using the obsolete ‘daemon.pidlockfile’ API, and will fail with an ImportError. If the package is unusable without that API, then this bug report should be upgraded to “Severity: serious”. You can fix this bug by: * Work with upstream to remove references to ‘daemon.pidlockfile’, and to migrate to the ‘lockfile.pidlockfile’ API. * Package the new upstream version of this package. * Add to this package a “Depends: python-lockfile (= 0.9)” and/or “Depends: python3-lockfile (= 0.9)”. * Release that package to Debian Sid. If you've already done this, great! Please let me know so that I can keep track of which packages are affected. -- \“My doctor told me to stop having intimate dinners for four. | `\ Unless there are three other people.” —Orson Welles | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789909: lavapdu: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library
Package: lavapdu Version: 0.0.4-2 Severity: important Howdy, The ‘python-daemon’ library has in the past included an internal ‘daemon.pidlockfile’ module for its own use. That functionality has migrated to the ‘lockfile’ distribution (packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’) version 0.9 and later. In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’ module does not exist. Code which attempts to import it will fail. A simple inspection (using ‘grep’) of the Python source for this package shows it is using the obsolete ‘daemon.pidlockfile’ API, and will fail with an ImportError. If the package is unusable without that API, then this bug report should be upgraded to “Severity: serious”. You can fix this bug by: * Work with upstream to remove references to ‘daemon.pidlockfile’, and to migrate to the ‘lockfile.pidlockfile’ API. * Package the new upstream version of this package. * Add to this package a “Depends: python-lockfile (= 0.9)” and/or “Depends: python3-lockfile (= 0.9)”. * Release that package to Debian Sid. If you've already done this, great! Please let me know so that I can keep track of which packages are affected. -- \“My doctor told me to stop having intimate dinners for four. | `\ Unless there are three other people.” —Orson Welles | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789908: dbconfig-common: French debconf templates translation
Package: dbconfig-common Version: N/A Severity: wishlist Tags: patch l10n Dear Maintainer, I have totally messed up with the previous translation file; I am truly sorry for that. This one should be correct. Cheers, Please find attached the french debconf templates translation, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.24.0.2-custom (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) # Translation of dbconfig-common debconf templates to French # Copyright (C) 2005-2009 Debian French l10n team debian-l10n-fre...@lists.debian.org # This file is distributed under the same license as the dbconfig-common package. # # Translators: # Christian Perrier bubu...@debian.org, 2005, 2006, 2009. # Julien Patriarca leatherf...@debian.org, 2015. msgid msgstr Project-Id-Version: fr\n Report-Msgid-Bugs-To: dbconfig-com...@packages.debian.org\n POT-Creation-Date: 2015-06-07 21:03+0200\n PO-Revision-Date: 2015-06-15 11:00+0100\n Last-Translator: Julien Patriarca leatherf...@debian.org\n Language-Team: French debian-l10n-fre...@lists.debian.org\n Language: fr\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Poedit-SourceCharset: iso-8859-1\n X-Generator: Poedit 1.7.7\n #. Type: boolean #. Description #: ../dbconfig-common.templates:2001 msgid Will this server be used to access remote databases? msgstr Ce serveur sera-t-il utilisé pour accéder à des bases de données distantes ? #. Type: boolean #. Description #: ../dbconfig-common.templates:2001 msgid For the database types that support it, dbconfig-common includes support for configuring databases on remote systems. When installing a package's database via dbconfig-common, the questions related to remote configuration are asked with a priority such that they are skipped for most systems. msgstr Pour les gestionnaires de bases de données qui le permettent, dbconfig- common gère la configuration des bases de données sur des systèmes distants. Lorsque dbconfig-common crée des bases de données pour un paquet, les questions relatives à la configuration distante sont posées avec une priorité qui les rendra invisibles sur la plupart des systèmes. #. Type: boolean #. Description #: ../dbconfig-common.templates:2001 msgid If you select this option, the default behavior will be to prompt you with questions related to remote database configuration when you install new packages. msgstr Si vous choisissez cette option, les questions relatives à la configuration de bases de données distantes vous seront posées lors de l'installation de nouveaux paquets. #. Type: boolean #. Description #: ../dbconfig-common.templates:2001 msgid If you are unsure, you should not select this option. msgstr Dans le doute, vous ne devriez pas choisir cette option. #. Type: boolean #. Description #: ../dbconfig-common.templates:3001 msgid Keep \administrative\ database passwords? msgstr Faut-il garder les mots de passe des administrateurs des bases de données ? #. Type: boolean #. Description #: ../dbconfig-common.templates:3001 msgid By default, you will be prompted for all administrator-level database passwords when you configure, upgrade, or remove applications with dbconfig- common. These passwords will be stored in debconf's configuration database only for as long as they are needed. msgstr Par défaut, vous devrez indiquer les mots de passe des administrateurs des bases de données lors de chaque configuration, mise à jour ou suppression des applications qui utilisent dbconfig-common. Ces mots de passe ne seront pas conservés plus longtemps que nécessaire dans la base de données de configuration debconf. #. Type: boolean #. Description #: ../dbconfig-common.templates:3001 msgid This behavior can be disabled, in which case the passwords will remain in the debconf database. This database is protected by Unix file permissions, though this is less secure and thus not the default setting. msgstr Ce comportement peut être désactivé, les mots de passe seront alors conservés dans la base de données debconf. La base de données est protégée par les permissions d'accès aux fichiers correspondants Unix, cependant, ce comportement moins sécurisé n'est pas le réglage par défaut. #. Type: boolean #. Description #: ../dbconfig-common.templates:3001 msgid If you would rather not be bothered for an administrative password every time you upgrade a database application with dbconfig-common, you should choose this option.
Bug#789910: bcfg2: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library
Package: bcfg2 Version: 1.3.5-1 Severity: important Howdy, The ‘python-daemon’ library has in the past included an internal ‘daemon.pidlockfile’ module for its own use. That functionality has migrated to the ‘lockfile’ distribution (packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’) version 0.9 and later. In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’ module does not exist. Code which attempts to import it will fail. A simple inspection (using ‘grep’) of the Python source for this package shows it is using the obsolete ‘daemon.pidlockfile’ API, and will fail with an ImportError. If the package is unusable without that API, then this bug report should be upgraded to “Severity: serious”. You can fix this bug by: * Work with upstream to remove references to ‘daemon.pidlockfile’, and to migrate to the ‘lockfile.pidlockfile’ API. * Package the new upstream version of this package. * Add to this package a “Depends: python-lockfile (= 0.9)” and/or “Depends: python3-lockfile (= 0.9)”. * Release that package to Debian Sid. If you've already done this, great! Please let me know so that I can keep track of which packages are affected. -- \“My doctor told me to stop having intimate dinners for four. | `\ Unless there are three other people.” —Orson Welles | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789975: FTBFS: CMake Error at doc/doxygen .. INSTALL cannot find .. doc/doxygen/deal.tag
Source: deal.ii Version: 8.1.0-4 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: -- Installing: /tmp/buildd/deal.ii-8.1.0/debian/tmp/usr/share/doc/libdeal.ii-doc/LICENSE CMake Error at doc/doxygen/cmake_install.cmake:36 (file): file INSTALL cannot find /tmp/buildd/deal.ii-8.1.0/obj-x86_64-linux-gnu/doc/doxygen/deal.tag. Call Stack (most recent call first): doc/cmake_install.cmake:52 (include) cmake_install.cmake:39 (include) Makefile:88: recipe for target 'install' failed An example build log can be seen: https://reproducible.debian.net/rb-pkg/unstable/amd64/deal.ii.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789979: New upstream release available
Package: teeworlds Severity: wishlist Version 0.6.3 is available from https://www.teeworlds.com/?page=downloads -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789978: FTBFS: lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value)
Source: lua-discount Version: 1.2.10.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build, during tests(?): Making target test for debian/lua5.2.dh-lua.conf ** lua dynamic (5.2) * Test: test_discount.lua lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value) stack traceback: test_discount.lua:49: in main chunk [C]: in ? /usr/share/dh-lua/make/dh-lua.Makefile.single:288: recipe for target 'test-lua-dynamic-real' failed make[2]: *** [test-lua-dynamic-real] Error 1 /usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: recipe for target 'test' failed Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/lua-discount.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789983: Time to remove mips build workaround?
Package: adun.app Version: 0.81-6 Severity: minor debian/rules contains: # Workaround for gcc-4.4 bug 519006. ifneq (,$(findstring mips,$(DEB_BUILD_ARCH))) mipsen-flags := ADDITIONAL_OBJCFLAGS=-g0 ADDITIONAL_CFLAGS=-g0 endif I wonder if it's time to remove that workaround since that bug was fixed in 2010. -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789988: FTBFS: The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved
Package: eclipse-mylyn-tasks-github Version: 3.3.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The package fails to build, probably because egit has changed: @dot: [mkdir] Created dir: /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot [javac] Compiling 50 source files to /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot [javac] 29. ERROR in /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java (at line 27) [javac] import org.eclipse.egit.ui.internal.FilteredCheckboxTree; [javac]^ [javac] The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved [javac] -- [javac] 30. ERROR in /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java (at line 184) [javac] private FilteredCheckboxTree tree; [javac] [javac] FilteredCheckboxTree cannot be resolved to a type etc. Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/eclipse-mylyn-tasks-github.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789974: ITP: gst-plugins-espeak -- GStreamer plugin for eSpeak speech synthesis
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard d...@jones.dk -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: gst-plugins-espeak Version : 0.4.0 Upstream Author : Aleksey Lim alsr...@sugarlabs.org * URL : https://wiki.sugarlabs.org/go/Activity_Team/gst-plugins-espeak * License : GPL-2+ Programming Lang: C Description : GStreamer plugin for eSpeak speech synthesis GStreamer is a streaming media framework, based on graphs of filters which operate on media data. Applications using this library can do anything from real-time sound processing to playing videos, and just about anything else media-related. Its plugin-based architecture means that new data types or processing capabilities can be added simply by installing new plug-ins. . This package contains a GStreamer plugin for using eSpeak library as a sound source for GStreamer. Plugin uses given text to produce audio output. This package is needed for speech synthesis features of the Sugar learning environment. Package will be maintained in the Sugar team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVjFs6AAoJECx8MUbBoAEhNb8P/AlME9sJN8/vdADDUJiYT6nr 9OyBsLDHa6uYF6LKWgmO9deTrWfqJ+t8HhkJZlAmNOmFU5Cz4xbhlUk9RsfoY+4Y wsc40TpkEa0RMFE4S85r9Sj7OrSNBLnXPG0B5mkf/u6VSif4JRzuEYMxywD/q6jo Z3+FLv66i9DfrBspJIksO/6PG73oOOzuTsaUqqZX5Bc+c2qy1DHQzMDZ3YzckXNh NG0Xni2NRr8zV6g7g87RY3Uktwz5LbPtgzoazlxxw8pj0Y0jxD3xjWnfcEYPF3au TQuGq1dhSs/fFjgBpKDeVEFMRLT30zsdIJL85SYrfPRrJoRcNJeW+SwRYveWxWeF KksNJzLODxAb3ZGz+qQGhAcLk/k0DcO0VrvCapwH0eOPAZp3o7Cy7HSWVWu2kZMs HIoKu5RPifaj4Dje6/lQ8Hrg6GNzfjbqTdVExW1qM3RXsvAVH+Z/mfhX6gMd7QXy fRiweDlka0knd5oEz9eTZnrv0qh1ede4Bp5Soij+VxAKUcTjPEdPrVbBzWfvF5dh kpvRO5J+M2tQO8QfwX8sKcMNAGNiWDzL6wqiSadUp7n9t7pqteM9wsErSv8UA8Uj BWZ/OauxJ8Q0Txgo0oXw7Kq9Plw0y3vr3GwPsvrXxSUVovrrgAB/+mXpbtLOem50 f6osgZyvFPQkCGScsNHZ =nUOJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789990: FTBFS: AttributeAlias.java: error: package com.netscape.management.client.util does not exist
Source: 389-ds-console Version: 1.2.7-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: build: [javac] /tmp/buildd/389-ds-console-1.2.7/build.xml:102: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 359 source files to /tmp/buildd/389-ds-console-1.2.7/build/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.5 [javac] /tmp/buildd/389-ds-console-1.2.7/src/com/netscape/admin/dirserv/AttributeAlias.java:23: error: package com.netscape.management.client.util does not exist [javac] import com.netscape.management.client.util.ResourceSet; Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/389-ds-console.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789991: FTBFS: Test failures including FixtureS.TestPanicOnSetUpSuite, FixtureS.TestPanicOnSetUpTest
Source: golang-gocheck Version: 0.0~bzr20131118+85-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build during its tests: -- FAIL: fixture_test.go:132: FixtureS.TestPanicOnSetUpSuite fixture_test.go:153: c.Check(output.value, Matches, expected) value string = + \n + --\n + PANIC: gocheck_test.go:119: FixtureHelper.SetUpSuite\n + \n + ... Panic: SetUpSuite (PC=0x43A0F5)\n + \n + /usr/lib/go/src/runtime/asm_amd64.s:401\n + in call16\n + /usr/lib/go/src/runtime/panic.go:387\n + in gopanic\n + gocheck_test.go:109\n + in FixtureHelper.trace\n + gocheck_test.go:120\n + in FixtureHelper.SetUpSuite\n + /usr/lib/go/src/runtime/asm_amd64.s:401\n + in call16\n regex string = + ^\n + -+\n + PANIC: gocheck_test\\.go:[0-9]+: FixtureHelper.SetUpSuite\n + \n + \\.\\.\\. Panic: SetUpSuite \\(PC=[xA-F0-9]+\\)\n + \n + .+:[0-9]+\n + in panic\n + .*gocheck_test.go:[0-9]+\n + in FixtureHelper.trace\n + .*gocheck_test.go:[0-9]+\n + in FixtureHelper.SetUpSuite\n + .+:[0-9]+\n + in call[0-9]+\n + $ OOPS: 119 passed, 5 FAILED --- FAIL: Test (0.18s) FAIL exit status 1 FAILlaunchpad.net/gocheck 0.186s I can reproduce these five tests failing locally. Jenkins finds some benchmark tests failing too: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-gocheck.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789864: transition: libgdata22
Am 25.06.2015 um 03:10 schrieb Emilio Pozuelo Monfort: Control: tags -1 confirmed On 25/06/15 01:16, Michael Biebl wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I'd like to request a slot for a small transition. libgdata bumped the soname from 19 → 22. The new package is available in experimental and built everywhere. I've rebuilt all rdeps, and I didn't get any build failures, so only a round of binNMUs should be necessary. If there is no conflict with another ongoing transition, it should be good to go. You can go ahead. Thanks Emilio. libgdata is uploaded and has been built everywhere (aside from sparc and hurd). So you can schedule the binNMUs now. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#778101: rcs-blame: ftbfs with GCC-5
Hi, It looks like rcs-blame has bitrotted a bit with GCC-5. Is this something you could address? If you maintain the Cc on this email, our bug tracking system will be kept in the loop. regards Andrew On Thu, Feb 12, 2015 at 10:36:32AM +, Matthias Klose wrote: Package: src:rcs-blame Version: 1.3.1-4 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/rcs-blame_1.3.1-4_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 [...] ../lib/libmisc.a(argp-parse.o): In function `_option_is_end': /«PKGBUILDDIR»/lib/argp.h:605: multiple definition of `_option_is_end' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:605: first defined here ../lib/libmisc.a(argp-pvh.o): In function `argp_usage': /«PKGBUILDDIR»/lib/argp.h:587: multiple definition of `argp_usage' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:587: first defined here ../lib/libmisc.a(argp-pvh.o): In function `_option_is_short': /«PKGBUILDDIR»/lib/argp.h:593: multiple definition of `_option_is_short' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:593: first defined here ../lib/libmisc.a(argp-pvh.o): In function `_option_is_end': /«PKGBUILDDIR»/lib/argp.h:605: multiple definition of `_option_is_end' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:605: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_lmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:243: multiple definition of `argp_fmtstream_set_lmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:243: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_rmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:255: multiple definition of `argp_fmtstream_set_rmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:255: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_wmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:267: multiple definition of `argp_fmtstream_set_wmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:267: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_point': /«PKGBUILDDIR»/lib/argp-fmtstream.h:280: multiple definition of `argp_fmtstream_point' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:280: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_write': /«PKGBUILDDIR»/lib/argp-fmtstream.h:207: multiple definition of `argp_fmtstream_write' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:207: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_putc': /«PKGBUILDDIR»/lib/argp-fmtstream.h:233: multiple definition of `argp_fmtstream_putc' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:233: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_puts': /«PKGBUILDDIR»/lib/argp-fmtstream.h:220: multiple definition of `argp_fmtstream_puts' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:220: first defined here collect2: error: ld returned 1 exit status make[4]: *** [blame] Error 1 Makefile:353: recipe for target 'blame' failed make[4]: Leaving directory '/«PKGBUILDDIR»/src' make[3]: *** [all] Error 2 Makefile:275: recipe for target 'all' failed make[3]: Leaving directory '/«PKGBUILDDIR»/src' make[2]: *** [all-recursive] Error 1 Makefile:322: recipe for target 'all-recursive' failed make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: *** [all] Error 2 Makefile:258: recipe for target 'all' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:7: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 signature.asc Description: Digital signature
Bug#789972: volk: FTBFS on 32-bit arm: undefined reference to `volk_*neon*'
Well, 1.0-4 builds on armhf. So this bug is half-closed. I'm not quite sure how to adjust the cmake logic for Debian's armel architecture. For targets using neon, upstream supports cross compiling Open Embedded builds. Any patch for Debian armel won't go upstream if it breaks cross-builds. Patches welcome. I've got to spend some time studying the cmake build logic. -Maitland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789962: [INTL:es] Spanish translation of the debconf template cobbler
Re-saved and resent so that you (maintainer) have no encoding problem with the file in case you save it from a bugged mutt mail reader es.po Description: application/gettext signature.asc Description: Digital signature
Bug#790000: pcre3: heap overflow vulnerability in find_fixedlength()
Source: pcre3 Version: 1:8.30-5 Severity: important Tags: security upstream patch fixed-upstream Hi A new heap overflow vulnerability was found in pcre3, in find_fixedlenght(). See: https://bugs.exim.org/show_bug.cgi?id=1651 http://vcs.pcre.org/pcre?view=revisionrevision=1571 A CVE has been requested at http://www.openwall.com/lists/oss-security/2015/06/26/1 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790001: base: OpenShot and startup applications bug
Package: base Severity: minor Dear Maintainer, Watch video here: http://youtu.be/LXhgsMPnsaM I wanted to see OpenShot button normal in Startup applications -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790002: base: Openshot and Startup applications bug
Package: base Severity: normal Dear Maintainer, Please look at https://www.youtube.com/watch?v=LXhgsMPnsaM I expected to see normal Openshot button in startup applications -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790003: xfburn: package update request
Package: xfburn Version: 0.5.2-1 Upgrade to xfburn 0.5.4 (2015-05-16) which has [1] - Some autoconf modernization - Use gstreamer 1.0 api - Restore broken icons [3] xfburn is the last user of the gstreamer 0.10 api on Lubuntu and Xubuntu, so it's an image space saving win too. I am hoping to get this for Ubuntu 15.10 [2], but this is just as relevant for Debian XFCE releases. Thanks! Bryan [1] http://git.xfce.org/apps/xfburn/tree/NEWS?id=xfburn-0.5.4 [2] Ubuntu bug report - https://bugs.launchpad.net/ubuntu/+source/xfburn/+bug/1469000 [3] Looks like it might fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718390 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779599: libsocl-contrib-1.2-0, libsocl-1.2-0: missing breaks+replaces against each other
Followup-For: Bug #779599 Control: found -1 1.2.0~rc2+dfsg-1 Still reproducible: Selecting previously unselected package libstarpu-contrib-1.2-1. (Reading database ... 7792 files and directories currently installed.) Preparing to unpack .../libstarpu-contrib-1.2-1_1.2.0~rc2+dfsg-1_amd64.deb ... Unpacking libstarpu-contrib-1.2-1 (1.2.0~rc2+dfsg-1) ... Selecting previously unselected package libsocl-contrib-1.2-0. Preparing to unpack .../libsocl-contrib-1.2-0_1.2.0~rc2+dfsg-1_amd64.deb ... Unpacking libsocl-contrib-1.2-0 (1.2.0~rc2+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsocl-contrib-1.2-0_1.2.0~rc2+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libsocl-1.2.so.0.0.0', which is also in package libsocl-1.2-0 1.2.0~rc2+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/libsocl-contrib-1.2-0_1.2.0~rc2+dfsg-1_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789661: python3-grib: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/grib_repack.1.gz
Followup-For: Bug #789661 Control: found -1 2.0.0-2 problem is still there Selecting previously unselected package python3-grib. Preparing to unpack .../python3-grib_2.0.0-2_amd64.deb ... Unpacking python3-grib (2.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-grib_2.0.0-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/grib_repack.1.gz', which is also in package python-grib-doc 1.9.9-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-grib_2.0.0-2_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789604: release-notes: 'halt' behaviour changed without notice
On Thu, Jun 25, 2015 at 11:38:58AM +0100, Justin B Rye wrote: Vincent McIntyre wrote: I'm submitting this patch on the advice of the systemd maintainers. Could this be applied to the jessie release notes? It's good, but I've got a couple of English usage nitpicks: And I'm happy to have you pick the nits off my contribution :) Would you care to peruse #789652, which is related? Index: en/issues.dbk === --- en/issues.dbk (revision 10955) +++ en/issues.dbk (working copy) @@ -586,7 +586,21 @@ bug #784720/ulink /para /section +section id=systemd-halt-behavior + !-- Wheezy to Jessie (#760923) -- + titlesystemd: behavior of 'halt' command/title + para +The systemitem role=packagesysvinit/systemitem implementation +of the commandhalt/command command powered off the machine as well. +The systemitem role=packagesystemd-sysv/systemitem implementation +halts the system, but does not power off the machine. To halt the +machine and turn it off, use the commandpoweroff/command command. + /para + para +See also ulink url=url-bts;760923Debian bug #760923/ulink + /para /section +/section section id=required-kernel-config-options !-- Wheezy to Jessie -- This version looks good enough to commit. Thanks Vince -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744752: Fwd: ltrace needs to support ppc64le
On 06/24/2015 10:51 PM, Fernando Seiti Furusato wrote: Hello Juan. My apologies if this has already been taken care of, but are you planning on updating this package on Debian repository? I ask because I see that the patches sent by Thierry were already accepted upstream some time ago and this package would be nice to have on ppc64el. Thanks! Hello, If my patch was accepted upstream, there is no official release including it yet. Since the commit a number of new features are not yet debugged so here is what I suggest: Use git dev tree and eventually reset to minimum commit : eea4ad2cce289753aaa35b4e0258a76d8f8f367c 3 tests must be disabled as are in error today: testsuite/ltrace.minor/attach-process-dlopen.exp testsuite/ltrace.main/filters.exp testsuite/ltrace.main/dwarf.exp Making a port from 0.7.3 is a tuff work as there are so many changes in the common code between 0.7.3 and now. Let me know if you need more explanation. ASAP I will investigate current hang in dwarf and filters code, and the deadlock situation found with attach-process-dlopen.exp -- Thierry Fauck @ linux.vnet.ibm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789938: ITP: microbegps -- explorative taxonomic profiling tool for metagenomic data
Package: wnpp Severity: wishlist Owner: Andreas Tille ti...@debian.org * Package name: microbegps Version : 1.0.0 Upstream Author : Martin S. Lindner lindn...@rki.de * URL : http://sourceforge.net/projects/microbegps/ * License : BSD Programming Lang: Python Description : explorative taxonomic profiling tool for metagenomic data MicrobeGPS is a bioinformatics tool for the analysis of metagenomic sequencing data. The goal is to profile the composition of metagenomic communities as accurately as possible and present the results to the user in a convenient manner. One main focus is reliability: the tool calculates quality metrics for the estimated candidates and allows the user to identify false candidates easily. The package is maintained by the Debian Med team and ready for upload since all preconditions are available now. Packaging is at svn://anonscm.debian.org/debian-med/trunk/packages/microbegps/trunk/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778124: Patch for GCC 5 build issue
tags 778124 + patch thanks Here's a fix for the GCC 5 build issue. Long term, upstream should consider Different semantics for inline functions at https://gcc.gnu.org/gcc-5/porting_to.html but it seems there's no active upstream... -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard --- a/debian/rules 2015-06-25 13:09:35.718247053 + +++ b/debian/rules 2015-06-25 13:09:54.082247433 + @@ -13,7 +13,7 @@ DEB_INSTALL_CHANGELOGS_ALL = ChangeLog #CC= gcc -CFLAGS += $(CPPFLAGS) -I. -DUSE_PPP -DUSE_MS_DNS -fno-strict-aliasing -Wno-unused +CFLAGS += $(CPPFLAGS) -I. -DUSE_PPP -DUSE_MS_DNS -fno-strict-aliasing -Wno-unused -std=gnu89 PPPCFLAGS = $(CFLAGS) LDFLAGS += -Wl,--as-needed
Bug#778757: Close
On 2015-06-18 11:29:58 +0200, Vincent Lefevre wrote:
On 2015-06-18 09:31:09 +0200, Anton Gladky wrote:
Well, I tried to install emacs, but the error was still there.
Thanks for the information. I'll try with pbuilder, and see the
difference with debuild (which I'm currently using and for which
I do not get any error).
Indeed, pbuilder showed a missing build dependency, so that I had to
add emacs24. With this dependency, there isn't an error any longer.
However my patch mixed upstream/debian changes and could yield an
error in some cases (this is fine to apply local changes and rebuild
the package with debuild, but not for quilt, which I had to use to
refresh the patch in order to regenerate the dsc file for pbuilder).
I followed some suggestions on:
https://raphaelhertzog.com/2011/07/04/how-to-prepare-patches-for-debian-packages/
I've attached the debdiff output on the dsc files.
--
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
diff -Nru gnuplot5-5.0.1+dfsg1/debian/changelog
gnuplot5-5.0.1+dfsg1/debian/changelog
--- gnuplot5-5.0.1+dfsg1/debian/changelog 2015-06-17 17:54:52.0
+0200
+++ gnuplot5-5.0.1+dfsg1/debian/changelog 2015-06-25 12:19:29.0
+0200
@@ -1,3 +1,10 @@
+gnuplot5 (5.0.1+dfsg1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Provide gnuplot5.info file. (Closes: #778757)
+
+ -- Vincent Lefevre vinc...@vinc17.net Thu, 25 Jun 2015 12:17:34 +0200
+
gnuplot5 (5.0.1+dfsg1-1) unstable; urgency=medium
* [c0fd77e] Imported Upstream version 5.0.1+dfsg
diff -Nru gnuplot5-5.0.1+dfsg1/debian/control
gnuplot5-5.0.1+dfsg1/debian/control
--- gnuplot5-5.0.1+dfsg1/debian/control 2015-04-28 20:31:33.0 +0200
+++ gnuplot5-5.0.1+dfsg1/debian/control 2015-06-25 12:20:33.0 +0200
@@ -31,7 +31,8 @@
texlive-latex-extra,
texlive-latex-recommended,
libwxgtk3.0-dev,
- zlib1g-dev
+ zlib1g-dev,
+ emacs24
Standards-Version: 3.9.6
Vcs-Browser:
https://anonscm.debian.org/cgit/debian-science/packages/gnuplot5.git
Vcs-Git: git://anonscm.debian.org/debian-science/packages/gnuplot5.git
diff -Nru gnuplot5-5.0.1+dfsg1/debian/patches/12_info.patch
gnuplot5-5.0.1+dfsg1/debian/patches/12_info.patch
--- gnuplot5-5.0.1+dfsg1/debian/patches/12_info.patch 1970-01-01
01:00:00.0 +0100
+++ gnuplot5-5.0.1+dfsg1/debian/patches/12_info.patch 2015-06-25
12:20:42.0 +0200
@@ -0,0 +1,85 @@
+Index: gnuplot5-5.0.1+dfsg1/docs/Makefile.am
+===
+--- gnuplot5-5.0.1+dfsg1.orig/docs/Makefile.am
gnuplot5-5.0.1+dfsg1/docs/Makefile.am
+@@ -81,7 +81,7 @@ ELCS = gnuplot-eldoc.elc
+ CLEANFILES = allterm.h gnuplot.tex gnuplot.dvi gnuplot.aux gnuplot.log
\
+ gnuplot.toc gnuplot.ps gpcard.dvi gpcard.log gpcard.ps alldoc2gih \
+ doc2gih gnuplot.gih doc2hlp gnuplot.hlp gnuplot.idx gnuplot.ilg
\
+-gnuplot.ind gnuplot.info* gnuplot.out doc2ipf gnuplot.ipf doc2ms \
++gnuplot.ind gnuplot5.info* gnuplot.out doc2ipf gnuplot.ipf doc2ms \
+ gnuplot.ms doc2rnh gnuplot.rnh doc2rtf gnuplot.rtf gnuplot.nroff \
+ checkdoc gnuplot.txt gnuplot.tmp VERSION gnuplot.4tc gnuplot.4ct \
+ gnuplot.idv gnuplot.xref gnuplot.lg figures pdffigures.aux\
+@@ -301,7 +301,7 @@ wxhelp/doc2html: wxhelp/doc2html.o termd
+ $(LINK) $^
+
+ ### GNU info format
+-info: gnuplot.info
++info: gnuplot5.info
+
+ # Thanks to Bruce Ravel for doc2texi.el!
+ gnuplot.texi gnuplot-eldoc.el: $(srcdir)/doc2texi.el $(srcdir)/gnuplot.doc
+@@ -324,16 +324,16 @@ ${ELCS}: gnuplot-eldoc.el
+ echo No emacs found - cannot create gnuplot-eldoc.elc file ; \
+ fi
+
+-gnuplot.info: gnuplot.texi
+- $(MAKEINFO) -I$(srcdir) $(srcdir)/gnuplot.texi --no-split --force
--output=$@
++gnuplot5.info: gnuplot.texi
++ $(MAKEINFO) -I$(srcdir) gnuplot.texi --no-split --force --output=$@
+
+-install-info: gnuplot.info
++install-info: gnuplot5.info
+ $(top_srcdir)/mkinstalldirs $(DESTDIR)$(infodir)
+- $(INSTALL_DATA) gnuplot.info $(DESTDIR)$(infodir)/gnuplot.info
++ $(INSTALL_DATA) gnuplot5.info $(DESTDIR)$(infodir)/gnuplot5.info
+ @if (install-info --version \
+install-info --version | fgrep -i -v debian) /dev/null 21; then
\
+-echo install-info --info-dir=$(DESTDIR)$(infodir)
$(DESTDIR)$(infodir)/gnuplot.info;\
+-install-info --info-dir=$(DESTDIR)$(infodir)
$(DESTDIR)$(infodir)/gnuplot.info || :;\
++echo install-info --info-dir=$(DESTDIR)$(infodir)
$(DESTDIR)$(infodir)/gnuplot5.info;\
++install-info --info-dir=$(DESTDIR)$(infodir)
$(DESTDIR)$(infodir)/gnuplot5.info || :;\
+ else : ; fi
+
+ # this is how to make OS/2 ipfc documentation
+Index:
Bug#789936: libnetcdf-cxx-legacy-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/ncvalues.h
Package: libnetcdf-cxx-legacy-dev Version: 4.2-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails 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 libnetcdf-c++4. Preparing to unpack .../libnetcdf-c++4_4.2-1~exp1_amd64.deb ... Unpacking libnetcdf-c++4 (4.2-1~exp1) ... Selecting previously unselected package libnetcdf-cxx-legacy-dev. Preparing to unpack .../libnetcdf-cxx-legacy-dev_4.2-1~exp1_amd64.deb ... Unpacking libnetcdf-cxx-legacy-dev (4.2-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libnetcdf-cxx-legacy-dev_4.2-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/include/ncvalues.h', which is also in package libnetcdf-dev 1:4.1.3-7.2 Errors were encountered while processing: /var/cache/apt/archives/libnetcdf-cxx-legacy-dev_4.2-1~exp1_amd64.deb cheers, Andreas libnetcdf-dev=1%4.1.3-7.2_libnetcdf-cxx-legacy-dev=4.2-1~exp1.log.gz Description: application/gzip
Bug#788176: diodon: possible not to depend on zeitgeist?
AFAICS you're also upstream, right? yes 1) Well as you say, it works quite nicely with other DEs, at least those close to GNOME (like Cinnamon). Depending on Zeitgeist more or less excludes these users - maybe not from a technical PoV, but rather because such people typically don't use GNOME for things just like Zeitgeist. IMHO, it's a bit sad to focus such a nice tool only on a few desktop system... I guess as a software project you have to make a decision what the goal is within the limited time and resources available. Do you want to integrate really well with full potential into a subset of DEs or do you want to run with a very small footprint on as many DEs as possible? To do both is as of limited resources not really feasible therefore for Diodon we chose the former. 3) Well I have nothing against using Zeitgeist, but things have worked so fare quite nicely without it, so can't you just make it one optional backend, keeping the previous one as an alternative? Not requiring Zeitgeist has worked before, so why shouldn't it now? The previous backend doesn't work anymore as with Zeitgeist a feature has been added that the clipboard history can be accessed by external services and then a uri opened to paste the content. This is possible as Zeitgeist can be accessed through a DBus service. This feature is already used by services like the Unity Scope but to expanded to more services. Adding another backend would make this integration inconsistent and is therefore not desirable. As for the features: I'm not sure whether e.g. storing clipboard items infinitely is a good idea in all cases, over time this could be quite some privacy issue. (Yes I've seen that you have history clearing). I personally wouldn't need to have anything stored permanently at all,... so maybe as solution could be to store things just in memory, thereby not requiring any storage backend at all? If privacy is your concern it is actually possible to run Zeitgeist in memory only so each time you login your clipboard history is clean. You can do this by setting following env var (e.g. adding it to ~/.pam_environment): ZEITGEIST_DATABASE_PATH=:memory: To summarize: it seems what you are looking for is a clipboard manager with a small footprint with basics function but runs well on all DEs. I think if you want to use Diodon for such a use case an option would be if a maintainer could be found who continues to maintain Diodon version 1.0.3. I am happy to support something like this but do not have the time to maintain it myself. Cheers, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789929: seabios: FreeBSD 10.1 installer does kernel-crash in get_typematic. Looks like Bug 737142 again.
25.06.2015 13:34, Jens-Wolfhard Schicke-Uffmann wrote: Package: seabios Version: 1.8.2-1 [] Steps to fix: wget http://code.coreboot.org/p/seabios/downloads/get/bios.bin-1.8.0.gz gunzip bios.bin-1.8.0.gz qemu-system-x86_64 -boot order=dc -m 1G -vga std -cpu core2duo \ -bios bios.bin-1.8.0 \ # - HERE Note the version number, it is 1.8.0 not 1.8.2. In 1.8.2 we added some more workarounds for old/buggy *bsd behavour, tested with several freebsd and netbsd versions. You can try building seabios with CONFIG_VGA_FIXUP_ASM=n to turn it off. But I'm afraid it will bring the older prob back (which really is #737142). Google says, the same symptoms pop up from time to time and might be related to non-optimal toolchains while building seabios. It is not non-optimal. It is because some versions of GCC, with some command-line flags, generate some CPU instructions which aren't known to some variants of x86emu code used in some operating systems (these days, some bios code is executed, actually emulated, by the OS). These fixups are in order to remove these instructions by reimplementing it in equivalent but simpler and more traditional constructs. I'll try to find some time to take a look but don't expect immediately reply. Meanwhile you can try seabios from jessie which should work. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789330: closed by Dmitry Shachnev
Dmitry == Dmitry Shachnev mity...@debian.org writes: There will be no QString at all â any method that returns a QString in C++ will return a native Python string in PyQt. [...] Now that sounds great, thanks for the details. I'm feeling lucky again. ed. -- // enno@gmx.net /\\\ Mag. Enno Deimel .\o \\ \ _ \Wisely and slow; they stumble that run fast. \\\ \_/ gpg-fp: eefe b049 6fe6 fc0b 0ec4 f39e af6a c178 eb98 909a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789365: transition: ghc-7.8
On 24/06/15 16:12, Joachim Breitner wrote: Hi, Am Dienstag, den 23.06.2015, 15:05 +0200 schrieb Joachim Breitner: * leksah ought to be removed from testing: https://bugs.debian.org/789521 ✓ These two migrated back as there's no RC bug on them. I've re-added the removal hint, but please file a bug. gitit aged, and the ppc64el binNMUs are now done. This should go in tonight if nothing else pops up. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789932: ginkgocadx: FTBFS in unstable
Source: ginkgocadx Version: 3.7.0.1465.37+dfsg-1 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=ginkgocadxsuite=sid I got the same error on amd64. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789935: libnetcdff-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/typesizes.mod
Package: libnetcdff-dev Version: 4.4.2-1~exp2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails 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 libnetcdff6. Preparing to unpack .../libnetcdff6_4.4.2-1~exp2_amd64.deb ... Unpacking libnetcdff6 (4.4.2-1~exp2) ... Selecting previously unselected package libnetcdff-dev. Preparing to unpack .../libnetcdff-dev_4.4.2-1~exp2_amd64.deb ... Unpacking libnetcdff-dev (4.4.2-1~exp2) ... dpkg: error processing archive /var/cache/apt/archives/libnetcdff-dev_4.4.2-1~exp2_amd64.deb (--unpack): trying to overwrite '/usr/include/typesizes.mod', which is also in package libnetcdf-dev 1:4.1.3-7.2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libnetcdff-dev_4.4.2-1~exp2_amd64.deb cheers, Andreas libnetcdf-dev=1%4.1.3-7.2_libnetcdff-dev=4.4.2-1~exp2.log.gz Description: application/gzip
Bug#777788: Patch for GCC 5 build isse
tags 88 + patch thanks Here's a fix for this build issue. Note that there are different ways to solve this, depending on which compilers / C standards you want to support. There's a really good description at https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html Martin -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard Here's a fix for this build issue. Note that there are different ways to solve this, depending on which compilers / C standards you want to support. There's a really good description at https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html Martin diff -urN a/autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch --- autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch 1970-01-01 00:00:00.0 + +++ autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch 2015-06-25 12:49:45.118222413 + @@ -0,0 +1,44 @@ +--- a/c-unit/autounit.h 2006-07-13 20:50:07.0 + b/c-unit/autounit.h 2015-06-25 12:48:20.690220665 + +@@ -200,29 +200,29 @@ + + + #if defined (__STDC_VERSION__) __STDC_VERSION__ = 199901L +-#define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) + +-#define au_assert_fail(t, err_msg, ...) au_assert_true(t, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assert_fail(t, err_msg, ...) au_assert_true(t, 0, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assert_succeed(t, err_msg, ...) au_assert_true(t, 1, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assert_succeed(t, err_msg, ...) au_assert_true(t, 1, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_str(t, str1, str2, err_msg, ...) au_assert_str_int(t, AU_REL_EQUAL, str1, str2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_str(t, str1, str2, err_msg, ...) au_assert_str_int(t, AU_REL_EQUAL, str1, str2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_str(t, type, str1, str2, err_msg, ...) au_assert_str_int(t, type, str1, str2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_str(t, type, str1, str2, err_msg, ...) au_assert_str_int(t, type, str1, str2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_uint64(t, in1, in2, err_msg, ...) au_assert_guint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_uint64(t, in1, in2, err_msg, ...) au_assert_guint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_uint64(t, type, in1, in2, err_msg, ...) au_assert_guint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_uint64(t, type, in1, in2, err_msg, ...) au_assert_guint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_int(t, in1, in2, err_msg, ...) au_assert_gint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_int(t, in1, in2, err_msg, ...) au_assert_gint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_int(t, type, in1, in2, err_msg, ...) au_assert_gint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_int(t, type, in1, in2, err_msg, ...) au_assert_gint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_char(t, in1, in2, err_msg, ...) au_asserteq_char_int(t, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_char(t, in1, in2, err_msg, ...) au_asserteq_char_int(t, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_obj(t, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, AU_REL_EQUAL, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_obj(t, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, AU_REL_EQUAL, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_obj(t, type, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, type, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_obj(t, type, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, type, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + + #define au_assert_null(t, ob1, err_msg, ...) au_assert(t, ob1 == 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) + diff -urN a/autounit-0.20.1/debian/patches/series autounit-0.20.1/debian/patches/series --- autounit-0.20.1/debian/patches/series 2012-02-27 10:04:50.0 + +++ autounit-0.20.1/debian/patches/series 2015-06-25 12:44:01.198215295 + @@ -2,3 +2,4 @@ 10_netstring.patch
Bug#787668: transition: qtbase-opensource-src
Hi! The following qtconnectivity-opensource-src's packages will not longer build on !linux due to bluez not being available there: libqt5bluetooth5, libqt5nfc5, qml-module-qtbluetooth, qml-module-qtnfc, qtconnectivity5-dbg, qtconnectivity5-dev, qtconnectivity5-examples Should I file a bug to ftp masters to get them removed from testing or is something you also manage yourselfs? Thanks in advance, Lisandro. -- Combata las características. Si una característica no es absolutamente esencial, descártela, especialmente si tiene el mismo efecto que se puede alcanzar mediante la combinación de otras características. Andrew S. Tanenbaum, de su libro Computer Networks Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#612381: ITP: philologic - text analysis tool for digital corpora
This just would be really great to have as a package. DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789929: seabios: FreeBSD 10.1 installer does kernel-crash in get_typematic. Looks like Bug 737142 again.
Package: seabios Version: 1.8.2-1 Severity: normal Dear Maintainer, I tried install FreeBSD 10.1 into a qemu-system-x86_64 container. But the installer kernel crashes, the stacktrace shows get_typematic as a likely culprit. Google says, the same symptoms pop up from time to time and might be related to non-optimal toolchains while building seabios. Lo and behold, grabbing a seabios binary directly from coreboot (and supplying it to qemu) solved the issue. % dpkg -l qemu ii qemu1:2.3+dfsg-6 amd64fast processor emulator % dpkg -l seabios ii seabios 1.8.2-1 all Legacy BIOS implementation Steps to reproduce: wget http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-RELEASE-amd64-disc1.iso.xz xz -d /FreeBSD-10.1-RELEASE-amd64-disc1.iso.xz qemu-system-x86_64 -boot order=dc -m 1G -vga std -cpu core2duo \ -drive file=hda,if=ide,media=disk \ -net user,restrict=off -net nic -cdrom FreeBSD-10.1-RELEASE-amd64-disc1.iso Steps to fix: wget http://code.coreboot.org/p/seabios/downloads/get/bios.bin-1.8.0.gz gunzip bios.bin-1.8.0.gz qemu-system-x86_64 -boot order=dc -m 1G -vga std -cpu core2duo \ -bios bios.bin-1.8.0 \ # - HERE -drive file=hda,if=ide,media=disk \ -net user,restrict=off -net nic -cdrom FreeBSD-10.1-RELEASE-amd64-disc1.iso Regards, Drahflow -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) -- no debconf information signature.asc Description: Digital signature
Bug#785231: game-data-packager: update KDE icon cache after dpkg -i
2015-06-25 10:54 GMT+02:00 Simon McVittie s...@debian.org: I'm not particularly keen on introducing more hook points for run some scripts if we don't really need to. Well, I'm now tempted to close this or tag it wontfix and instead write my own wrapper script in /home/$user/bin and left GDP untouched; I end up typing to many things all the time anyway. This would also relief me from having my modified etc/game-data-packager.conf showing up in my git diff all the time and forbidding me from doing git commit -a. Those are appropriate at when you have built the .deb-time... - kbuildsycoca4 for the ones too lazy to try to fix their broken DE (well then if 3 packages are generated, the cache is checked 3 times :-| ) ... but this is when you install the .deb, not necessarily identical. It also has the disadvantage that you noted. Indeed, two sets of hooks would had been needed: - 1 per package - 1 at the end In any case, if KDE needs some arbitrary code execution as root when icons are updated kbuildsycoca4 run as user; but that's a detail that's a bug, which will affect every .deb (not just ours). I guess that some kind of race that only happen when you open the menu right away in the few seconds after the package is installed. Alexandre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789937: xinput --help shows a completely different set of options than the man page
Package: xinput Version: 1.6.1-1 Severity: wishlist File: /usr/share/man/man1/xinput.1.gz $ xinput --help shows all the options but without the --. $ man xinput shows all the options but with the --. I.e., neither shows any of the same options. Nor is there a note on either that both forms work. Nor is any --help listed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789775: zabbix-server: Zabbix server exits after 'One child process died'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/06/15 11:26, Dmitry Smirnov wrote: Two more thoughts -- it may be useful to increase log verbosity and check syslog as well. The latter may answer if zabbix server segfaults or geting OOM-killed... Nothing relevant in syslog. I've upped the debug level hopefull that will catch something if/when it dies next. - -- Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVi+7rAAoJEIOwkgET13LrCmEQAJjeqGH+T6V4xuG1M0UqTGRz EVclMTf2ncWmF6Ejj+PMnLW2chH9kv7+rD2cnVjv3eeY5FP2Bm7sOaYn8wJAqHVa kPHf+U9YzhWHePLPu7FWyN1Dn/pPQSYtRfeqEv4FLV4/ZR/EiEAQJ7OJbyOZDezT M400PqhhLvn3aZRYm6aWta2otCN+32ILYar5JtdSgxz0DsTTXOcam2YBLwuVCqwV y/IQKmo++f2tXRM9MlVs/8aAX68hUEeoOJpwkPe1FwKcu+BglHF9FuJSwBt1Ft+c u4BPo5zXLC2SXYQR5ENhY3yy2kXnrMjGj+agvZZJEc5Fp2x99fWPgYI965iNXxvl 8fW9mM2gyBjAgDeo5WY0Wx+tYfMJIJSL7kpHu4uetbKHZv5GNGsPiziHOB1RZB4A xEKF+uqwk5GzRoy3PjqvbBEEKmi92Z/6c08bn/vOMX03t+bq4sVMwIYqHZlB6KyX aLYNsfOOkmf4jcLVcoG62Fk6FDX0Wy9arOmZdW5K86N1sjKXpGgJhN7mX3OmAnbB 5s6jC1BVyff3vF+RVAvGKwPQbqiGsi3SghxBv57XYphoIdYTJSMh+wiR1ygZ/VSn a6A9qTx/QZP/VzEGn9jDMHZUr255PdUvtWSVw5mstrYjmkEc0X640eV5s+AHA36T E3HCSrU8WnFFeBZJT373 =Of0u -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789260: libburn4: Incompatibility with Plextor PX-608CU burner
Hi, Session error : Во время записи на диск произошла ошибка The curse of i18n. Which of my messages might this be ? (Translators, please judge wisely which message might be for the experts and developers and not for the users.) BraseroLibburn SCSI command 2Ah yielded host problem: 0x7 SG_ERR_DID_ERROR Luckily this was not translated. Regrettably we still have the same cause of failure perceived by libburn: Linux SG_IO indicates error. I've tried to install 1.3.4 and 1.3.8 but the problem is still there I would be astonished if it would vanish. (But one never knows ...) The decisive difference between the Linux distros must be somewhere else. We outruled kernel configuration, version (?), and libburn version. There remains systemd, udev, et.al. And there remains the desktop suite. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789922: kio-dev: uninstallable on current unstable
Hi Lisandro, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: Qt5 is currently going trough a transition, so this is just OK. You just need to wait until it's sorted out. Actually you will need to wait until the package gets pushed to unstable or rebuilt in experimental. It should happen soon though. OK, thank you for your quick answer. I will wait, then. :) Regards -- Florent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789934: libanthyinput-dev: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.a
Package: libanthyinput-dev Version: 1:0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails 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 libanthyinput0:amd64. Preparing to unpack .../libanthyinput0_1%3a0.3-1_amd64.deb ... Unpacking libanthyinput0:amd64 (1:0.3-1) ... dpkg: error processing archive /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', which is also in package libanthy0:amd64 9100h-25 Selecting previously unselected package libanthyinput-dev:amd64. Preparing to unpack .../libanthyinput-dev_1%3a0.3-1_amd64.deb ... Unpacking libanthyinput-dev:amd64 (1:0.3-1) ... dpkg: error processing archive /var/cache/apt/archives/libanthyinput-dev_1%3a0.3-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.a', which is also in package libanthy-dev:amd64 9100h-25 Errors were encountered while processing: /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb /var/cache/apt/archives/libanthyinput-dev_1%3a0.3-1_amd64.deb cheers, Andreas libanthy-dev=9100h-25_libanthyinput-dev=1%0.3-1.log.gz Description: application/gzip
Bug#789792: Ldd fails to identify musl binaries
Both find and ldd supply the correct information. It seems that you are on a glibc based system. In this case ldd belongs to the glibc-gcc-binutils package which is not compatible with the musl binaries. On glibc based systems the musl package provides the command musl-ldd which should work correctly. On native musl based debian systems (which do not yet exist) ldd is working as expected.
Bug#789818: ImportError: No module named sip
Control: reassign -1 python-qt4 4.11.4+dfsg-1 On Wed, Jun 24, 2015 at 4:14 PM, Andreas Hilboll andr...@hilboll.de wrote: `python3-sip` is installed: $ dpkg --get-selections | grep python3-sip python3-sip install sip-api is not: $ dpkg --get-selections | grep sip-api The package name is literally sip-api-11.2 including the number. But I guess it wouldn't show up with that command since it is virtual anyway. The following package changes were applied by the command `apt-get install bitcoind armory`: Package changes: snip +python3-sip 4.16.8+dfsg-1 amd64 So it looks like it lists python3-sip, but not the virtual package, but I guess the virtual package wouldn't be listed there anyway. Since python3-sip was installed during the armory installation, I believe my theory is correct. I also checked with #debian-python on OFTC on IRC. They said to report the bug against python-qt4, so I am reassigning this bug to python-qt4. To summarize the problem for the python-qt4 maintainers who weren't previously included in the emails, it seems like the latest version of python-qt4 in Sid depends on sip-api-11.2 which is provided by either python-sip or python3-sip. But as python-qt4 isn't Python 3 code, it seems like python3-sip shouldn't be an option. In the case of the user who opened the bug, python3-sip was installed as a dependency, but not python-sip preventing my package from running, because pyqt4 in turn wouldn't work without sip for Python 2. Cheers, Joseph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789940: FTBFS: gtk_widget_override_background_color is deprecated and -Werror
Source: libgrip Version: 0.3.8-1 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: gesture.c: In function ‘create_window’: gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations] gtk_widget_override_background_color (app-da, GTK_STATE_NORMAL, white); ^ cc1: all warnings being treated as errors An alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670119: naive implementation of ischroot mountinfo comparison
On Wed, Jun 24, 2015 at 08:15:35PM +0200, Andreas Henriksson wrote: I'm attaching a patch with a naive implementation of the suggestion made by Guillem Jover to compare mountinfo in case anyone finds it useful. Looks reasonable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789941: Performance regression: slow sequential reads for some block devices (readpage vs readpages) - patched in 3.18+
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt11-1
Initially discovered inside a QEMU guest, by doing the following:
# hdparm -t /dev/vda
Under the Wheezy 3.2 kernel:
Timing buffered disk reads: 384 MB in 3.01 seconds = 127.50 MB/sec
Under the Jessie 3.16 kernel:
Timing buffered disk reads: 46 MB in 3.07 seconds = 14.97 MB/sec
After some work swapping kernels, I discovered that this behaviour
exists in the 3.16 and 3.17 kernels, but not in 3.2-3.15 or 3.18+
Watching iostat as the I/O is happening indicated that the 3.16/3.17
guests were performing the I/O in 8-sector (512 bytes per sector)
chunks; in the other kernels, the request sizes were 254 sectors instead.
Some further work identified this patch in 3.18:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/diff/?id=447f05bb488bff4282088259b04f47f0f9f76760
diff --git a/fs/block_dev.c b/fs/block_dev.c
index 6d72746..e2f3ad08 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -304,6 +304,12 @@ static int blkdev_readpage(struct file * file,
struct page * page)
return block_read_full_page(page, blkdev_get_block);
}
+static int blkdev_readpages(struct file *file, struct address_space
*mapping,
+ struct list_head *pages, unsigned nr_pages)
+{
+ return mpage_readpages(mapping, pages, nr_pages, blkdev_get_block);
+}
+
static int blkdev_write_begin(struct file *file, struct address_space
*mapping,
loff_t pos, unsigned len, unsigned flags,
struct page **pagep, void **fsdata)
@@ -1622,6 +1628,7 @@ static int blkdev_releasepage(struct page *page,
gfp_t wait)
static const struct address_space_operations def_blk_aops = {
.readpage = blkdev_readpage,
+ .readpages = blkdev_readpages,
.writepage = blkdev_writepage,
.write_begin= blkdev_write_begin,
.write_end = blkdev_write_end,
It applies cleanly to 3.16 and 3.17; with the patch applied, the
larger request sizes are again seen and performance returns to the
previous level.
Could we apply this to the 3.16 kernel in Jessie?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789077: ruby2.2 transition: binNMUs round 3
On 25/06/15 15:00, Antonio Terceiro wrote: Hi, These packages used to FTBFS, but will now build fine with the new version of gem2deb in unstable. Please binNMU them: ruby-fast-stemmer ruby-blockenspiel ruby-fast-xs ruby-levenshtein raspell ruby-rdiscount ruby-hiredis ruby-rinku ruby-fftw3 ruby-github-markdown ruby-rjb ruby-multibitnums ruby-password ruby-raindrops ruby-rpatricia ruby-gsl ruby-kgio All scheduled. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789894: libvolk1.0-dev and libvolk-dev: error when trying to install together
Followup-For: Bug #789894 Similar problems between libvolk1.0-dev and gnuradio-dev: Selecting previously unselected package libvolk1.0:amd64. Preparing to unpack .../libvolk1.0_1.0-2_amd64.deb ... Unpacking libvolk1.0:amd64 (1.0-2) ... Selecting previously unselected package libvolk1.0-dev. Preparing to unpack .../libvolk1.0-dev_1.0-2_amd64.deb ... Unpacking libvolk1.0-dev (1.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libvolk1.0-dev_1.0-2_amd64.deb (--unpack): trying to overwrite '/usr/include/volk/volk_16i_max_star_horizontal_16i.h', which is also in package gnuradio-dev 3.7.5-5 Errors were encountered while processing: /var/cache/apt/archives/libvolk1.0-dev_1.0-2_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789775: zabbix-server: Zabbix server exits after 'One child process died'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/06/15 23:55, Dmitry Smirnov wrote: On Wed, 24 Jun 2015 11:36:31 Chris Jones wrote: Since upgrading to 2.4.5 (testing) from 2.2.7 (from stable) the Zabbix server stops after running for some time (2-3 days). Although I'm running zabbix-server-mysql for a while, I've never had this problem with 2.4.5. I'm not sure how to troubleshoot it. Could it be a problem in database? If so would you be able to VACUUM Zabbix tables or perhaps try to back-up Zabbix database to make sure it works? Also what init system are you using? Zabbix-server Systemd .service file contains Restart=on-abnormal which should be able to restart server automatically... I using systemd, next time it dies I'll pass on what systemd says about it. A backup (using pg_dump) completed. - -- Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVi9FYAAoJEIOwkgET13LrXBAP/0vZxaSIUlk2X8AE0f+tfyI6 6enGGakXxPL9OgVZu7UelcCQU1KAiFm7Pv1wswjm1I8WZK5rzX6bGsZvQKqJE6Bs gbA6PzKiWqcehKX+qeCMW51f+ki1fY2EF6DsBnV3uMTg3TSOP0Kd0WQbQi5i7iJZ X31bU5/MbTxyIsXDY5Vf5Na+d8JOPISqhQptDjMiYSv780LW9jHtekb/PmUSfBoT Is0PR4wbWyU8akcJrqmgrxOe1xGXf3rsX2EWcWWnfrn7QqdrtvcLEJvqJdZ4e8mh 3xbjNp3cLi4btSQnCYX5yjPjuqLlMpTw4FG0Quu/m6VyBjWv52Hf5PlmgzxmOoih mS/MqDH/+aafGujcmVsFk0pQ40j+VXnjoYUBGJ8QhKuHzAQ26M1E3mqD9wR5mKrE yNsFUqY22TEfZPsuAuv1j6LrTgm9FMy5fKX3F5OzhxfMxQBWXZxpcSQScGufoC4L PMK6cEv1YemIFOqYtoVk9Nt+GkB5oKp/tuLuQLnbakhvikUH4Ol4eoBKc9DM7Bzj ACR7AOvKcSJL/YGKnpX/IOIEHPNO3qhG4kmDdR2is/lrGOb8ET8LbOGsuQ0+A69N EJGeFThaiB8EAwnNia1jTvhFI7gTfnMNA2ZRAZhlCnYwO37hSbwgejCMHY6gylP1 8hwqAvh4tu1xhL64xstB =q+Q+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789931: itksnap: FTBFS in unstable
Source: itksnap Version: 2.2.0-1.1 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=itksnapsuite=sid I got the same error on amd64. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789930: gofigure2: FTBFS in unstable
Source: gofigure2 Version: 0.9.0-3 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=gofigure2suite=sid I got the same error on amd64. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789933: putty eats the CPU after ttyUSB was removed
Package: putty Version: 0.62-9+deb7u2 Severity: normal I use putty to control my embedded devices attached via /dev/ttyUSB interfaces. When an embedded device has powered off the corresponding /dev/ttyUSB device node disappears from my system and the putty proccess begins to eat the CPU time (96-98%). It seems the putty proccess tries to make something with the disappeared device node in the infinite loop. -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.14-0.bpo.1-rt-686-pae (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages putty depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.19-9 ii libcairo2 1.12.2-3 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1+deb7u1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 ii libx11-62:1.5.0-1+deb7u2 ii putty-tools 0.62-9+deb7u2 putty recommends no packages. Versions of packages putty suggests: pn putty-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789789: Musl fails to compile stuff that depends on kernel headers
I am not able to upload a copy of sabotage linux kernel headers due to debian policy. In the current state it is very unlikly that the official debian linux kernel maintainers are willing to provide the appropriate sanitized headers under the musl libc folder. Please see also debian bug 764335 for more information on this topic (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764335) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789077: ruby2.2 transition: binNMUs round 3
Hi, These packages used to FTBFS, but will now build fine with the new version of gem2deb in unstable. Please binNMU them: ruby-fast-stemmer ruby-blockenspiel ruby-fast-xs ruby-levenshtein raspell ruby-rdiscount ruby-hiredis ruby-rinku ruby-fftw3 ruby-github-markdown ruby-rjb ruby-multibitnums ruby-password ruby-raindrops ruby-rpatricia ruby-gsl ruby-kgio -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#578862: verify: close database /var/lib/postfix/verify_cache.db: No such file or directory
Package: postfix Version: 2.22.3-1 Followup-For: Bug #578862 I have observed the same log entries on jessie with 2.22.3-1. The steps taken by Teodor Micu make the message disappear, instead I get expected results such as: Jun 25 09:01:16 www postfix/verify[2244]: cache btree:/var/lib/postfix/verify_cache full cleanup: retained=21 dropped=0 entries root@www:/var/log# ls -al /var/spool/postfix/var/lib/postfix/ total 16 drwxr-xr-x 2 postfix postfix 4096 Jun 24 12:23 . drwxr-xr-x 3 postfix postfix 4096 Jun 24 12:23 .. -rw-r--r-- 1 postfix postfix 8192 Jun 24 12:23 verify_cache.db Is it possible that this is not the same issue that was fixed upstream? -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (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 postfix depends on: ii adduser3.113+nmu3 ii cpio 2.11+dfsg-4.1 ii debconf [debconf-2.0] 1.5.56 ii dpkg 1.17.25 ii libc6 2.19-18 ii libdb5.3 5.3.28-9 ii libsasl2-2 2.1.26.dfsg1-13 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libssl1.0.01.0.1k-3+deb8u1 ii lsb-base 4.1+Debian13+nmu1 ii netbase5.3 ii ssl-cert 1.0.35 Versions of packages postfix recommends: ii python 2.7.9-1 Versions of packages postfix suggests: ii dovecot-core [dovecot-common] 1:2.2.13-11 ii heirloom-mailx [mail-reader] 12.5-4 ii libsasl2-modules 2.1.26.dfsg1-13 pn postfix-cdbnone pn postfix-docnone pn postfix-ldap none pn postfix-mysql none pn postfix-pcre none pn postfix-pgsql none pn procmail none pn resolvconf none pn sasl2-bin none pn ufwnone -- debconf information: postfix/not_configured: postfix/chattr: false postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128 postfix/relayhost: postfix/recipient_delim: + postfix/mailname: /etc/mailname postfix/procmail: * postfix/main_mailer_type: No configuration postfix/destinations: postfix/bad_recipient_delimiter: postfix/mailbox_limit: 0 postfix/rfc1035_violation: false postfix/mydomain_warning: postfix/root_address: postfix/kernel_version_warning: postfix/sqlite_warning: postfix/protocols: postfix/tlsmgr_upgrade_warning: postfix/retry_upgrade_warning: postfix/relay_restrictions_warning: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789939: xserver-xorg-core: vesa int10 doesn't work, patch available
Package: xserver-xorg-core
Version: 2:1.17.1-2
Severity: important
Tags: upstream patch
Dear Maintainer,
Currently this package doesn't when using the VESA driver; the error is visible
in Xorg.0.log.
This is especially important for hurd (where I experienced this bug) because
that's the only driver available in practice.
It is fixed in ubuntu;
xorg-server (2:1.17.1-0ubuntu3) vivid; urgency=medium
* Add a patch to fix vesa int10 failure. (LP: #1433198)
-- Maarten Lankhorst maarten.lankho...@ubuntu.com Thu, 19 Mar 2015 10:13:08
+0100
I am attaching the patch for that to this bug report.
From: Jürg Billeter j...@bitron.ch
To: xorg-de...@lists.x.org
Subject: [PATCH xserver] int10: Fix error check for pci_device_map_legacy
Date: Sat, 7 Feb 2015 18:13:21 +0100
Message-Id: 1423329201-32163-1-git-send-emai...@bitron.ch
List-Id: X.Org development list xorg-devel.lists.x.org
pci_device_map_legacy returns 0 on success.
Signed-off-by: Jürg Billeter j...@bitron.ch
---
hw/xfree86/int10/generic.c| 2 +-
hw/xfree86/os-support/linux/int10/linux.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/xfree86/int10/generic.c b/hw/xfree86/int10/generic.c
index 012d194..8d5c4da 100644
--- a/hw/xfree86/int10/generic.c
+++ b/hw/xfree86/int10/generic.c
@@ -104,7 +104,7 @@ readIntVec(struct pci_device *dev, unsigned char *buf, int len)
{
void *map;
-if (!pci_device_map_legacy(dev, 0, len, 0, map))
+if (pci_device_map_legacy(dev, 0, len, 0, map))
return FALSE;
memcpy(buf, map, len);
diff --git a/hw/xfree86/os-support/linux/int10/linux.c b/hw/xfree86/os-support/linux/int10/linux.c
index 79b9a88..6ca118f 100644
--- a/hw/xfree86/os-support/linux/int10/linux.c
+++ b/hw/xfree86/os-support/linux/int10/linux.c
@@ -75,7 +75,7 @@ readLegacy(struct pci_device *dev, unsigned char *buf, int base, int len)
{
void *map;
-if (!pci_device_map_legacy(dev, base, len, 0, map))
+if (pci_device_map_legacy(dev, base, len, 0, map))
return FALSE;
memcpy(buf, map, len);
-- 2.3.0
Bug#787668: transition: qtbase-opensource-src
Hola Lisandro, On 25/06/15 14:56, Lisandro Damián Nicanor Pérez Meyer wrote: Hi! The following qtconnectivity-opensource-src's packages will not longer build on !linux due to bluez not being available there: libqt5bluetooth5, libqt5nfc5, qml-module-qtbluetooth, qml-module-qtnfc, qtconnectivity5-dbg, qtconnectivity5-dev, qtconnectivity5-examples Should I file a bug to ftp masters to get them removed from testing or is something you also manage yourselfs? Neither kfreebsd nor hurd are in testing, so that doesn't matter for migration purposes. However, if the packages are never going to be built again, you probably want them removed from unstable. For that, file an RM bug against ftp.debian.org specifying the architectures they should be removed from. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789515: cmucl: is the libxp dependency necessary?
Hello Graham, On 21/06/15 19:06, Graham Inggs wrote: Your package depends on libxp. This situation sometimes arises historically from the time before xprint was considered obsolete, with Build-depends: libxp-dev being set in the past and then forgotten and untouched. In fact upstream set a dependency on libXp. Removing it seems not to impact the system, so I'm going to remove it in the next version. This came about by the change from lesstif to the real motif libraries... Best regards, Peter -- signature -at- pvaneynd.mailworks.org http://pvaneynd.dreamwidth.org/ God, root, what is difference?-Pitr|God is more forgiving.-Dave Aronson| signature.asc Description: OpenPGP digital signature
Bug#789260: libburn4: Incompatibility with Plextor PX-608CU burner
Hi, i forgot to mention libburn-1.X.Y/cdrskin/README which explains production of statically linked cdrskin, and especially shell command cdrskin/cdrskin -version which states the version of libburn in use. E.g.: cdrskin 1.3.2 : limited cdrecord compatibility wrapper for libburn Cdrecord 2.01-Emulation Copyright (C) 2006-2013, see libburnia-project.org System adapter: internal GNU/Linux SG_IO adapter sg-linux libburn interface : 1.3.2 libburn in use: 1.3.2 cdrskin version : 1.3.2 Version timestamp : 2013.08.07.093001 Build timestamp : -none-given- Further, there is a system adapter which uses libcdio = 0.83 instead of directly using ioctl(SG_IO). (You need package libcdio-dev for the header files at compile time.) make clean ./configure --enable-libcdio make cdrskin/compile_cdrskin.sh cdrskin/cdrskin -version should then report something like System adapter: sg-libcdio h83 with libcdio 0.83 x86_64-pc-linux-gnu Same higher levels, different transport level. Worth a try. libcdio itself uses ioctl(SG_IO), of course. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785509: RM: appdata-tools -- ROM; deprecated, unused
The transitional appdata-tools from src:appstream-glib is in both unstable and testing now, so it should be safe to go ahead with this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778142: (no subject)
During this years Debconf I will work on this bug. There's a thread about this bug at http://mx.gw.com/pipermail/tcsh-bugs/2015-May/000930.html and also a new upstream version (6.19.00). -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789452: python-qt4-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi Andreas, On Mon, 22 Jun 2015 01:24:09 +0200, Andreas Beckmann wrote: On 2015-06-21 18:20, Dmitry Shachnev wrote: python-sip4-dbg existed only until squeeze, there is no such package in wheezy. Also, it was built from sip4-qt3 source, there is no such source anymore. What does this have to do with python-qt4-dbg package? How can we fix a bug in a package that no longer exists for several releases? oops, missed the small difference between python-qt4-dbg and python-sip4-dbg :-) Probably python-sip should add an unversioned Breaks: python-qt4-dbg to ensure that the old broken transitional (?) package gets removed. I need to check this in more detail, but right now my test machine is unreachable - crashed or network problems. Did you manage to check that? I can add a Breaks if needed. (I assume you again missed that small difference and actually meant Breaks: python-sip4-dbg.) -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#789932: ginkgocadx: FTBFS in unstable
Right, it fails because it can't find ITKConfig.cmake any more. When I update libinsighttoolkit3-dev -- libinsighttoolkit4-dev in Build-Depends build progresses till 73% when it fails with another error: thumbnailscommand.cpp:54:30: fatal error: itkOrientedImage.h: No such file or directory Any ideas? -- Regards, Dmitry Smirnov. --- Do your duty as you see it, and damn the consequences. -- George S. Patton signature.asc Description: This is a digitally signed message part.
Bug#789330: closed by Dmitry Shachnev
Hi Enno,
On Thu, 25 Jun 2015 14:14:32 +0200, Enno wrote:
Dear Dmitry,
Not quite satisfactory:
They want to tell me, that with the upgrade a line like
QString('blahmooh').startswith('blah')
is going to return True instead of raising an AttributeError like now?
There will be no QString at all — any method that returns a QString in C++
will return a native Python string in PyQt.
Try it yourself with:
import sip
sip.setapi('QString', 2)
See http://pyqt.sourceforge.net/Docs/PyQt4/incompatible_apis.html for details.
Any discussion on changing the behavior should happen upstream, we (Debian)
are not really deciding anything here.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
Bug#777974: Patch for GCC 5 build issue
Here's a fix for this build issue. Note that there are different ways to solve this, depending on which compilers / C standards you want to support. There's a really good description at https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html Martin -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard diff -urN a/libspf2-1.2.10/debian/patches/gcc5-build-fix.patch libspf2-1.2.10/debian/patches/gcc5-build-fix.patch --- libspf2-1.2.10/debian/patches/gcc5-build-fix.patch 1970-01-01 00:00:00.0 + +++ libspf2-1.2.10/debian/patches/gcc5-build-fix.patch 2015-06-25 13:03:52.310239946 + @@ -0,0 +1,12 @@ + +--- a/src/include/spf_log.h 2015-06-25 13:00:51.866236212 + b/src/include/spf_log.h 2015-06-25 13:01:11.838236625 + +@@ -63,7 +63,7 @@ + #define SPF_errorf(format, ... ) SPF_errorx( __FILE__, __LINE__, format, __VA_ARGS__ ) + #define SPF_warningf(format, ... ) SPF_warningx( __FILE__, __LINE__, format, __VA_ARGS__ ) + #define SPF_infof(format, ... ) SPF_infox( __FILE__, __LINE__, format, __VA_ARGS__ ) +-#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format, __VA_ARGS__ ) ++#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format, #__VA_ARGS__ ) + + #elif defined( __GNUC__ ) + diff -urN a/libspf2-1.2.10/debian/patches/series libspf2-1.2.10/debian/patches/series --- libspf2-1.2.10/debian/patches/series 2014-10-12 19:15:29.0 + +++ libspf2-1.2.10/debian/patches/series 2015-06-25 13:03:58.486240074 + @@ -1,2 +1,3 @@ spf_dns-include-std-headers.patch abolish-spf-rrtype.patch +gcc5-build-fix.patch
Bug#789260: libburn4: Incompatibility with Plextor PX-608CU burner
I can't compile any versio of libburn with libcdio: dmitry@D-NESTERKIN:~/libburn-1.3.4$ sudo cdrskin/compile_cdrskin.sh Version timestamp : 2013.12.12.093001 Build timestamp : 2015.06.25.130010 compiling program cdrskin/cdrskin.c cdrskin/cdrfifo.c -O2 -DCdrskin_libburn_1_3_4 libburn/cleanup.o libburn/sg.o: In function `sg_grab': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:567: undefined reference to `cdio_get_arg' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:569: undefined reference to `cdio_destroy' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:556: undefined reference to `cdio_open_am' libburn/sg.o: In function `sg_close_drive': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:217: undefined reference to `cdio_destroy' libburn/sg.o: In function `sg_issue_command': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:674: undefined reference to `mmc_run_cmd' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:678: undefined reference to `mmc_last_cmd_sense' libburn/sg.o: In function `sg_give_next_adr_raw': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:232: undefined reference to `cdio_get_devices' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:245: undefined reference to `cdio_free_device_list' libburn/sg.o: In function `sg_id_string': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:351: undefined reference to `cdio_version_string' libburn/sg.o: In function `sg_initialize': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:368: undefined reference to `cdio_loglevel_default' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:372: undefined reference to `libcdio_version_num' libburn/sg.o: In function `sg_obtain_scsi_adr': /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:744: undefined reference to `cdio_open' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:750: undefined reference to `cdio_get_arg' /home/dmitry/libburn-1.3.4/libburn/sg-libcdio.c:756: undefined reference to `cdio_destroy' collect2: error: ld returned 1 exit status +++ FATAL : Compilation of cdrskin failed dmitry@D-NESTERKIN:~/libburn-1.3.4$ sudo dpkg -l |grep libcdio ii libcdio-cdda1 0.83-4.2 amd64library to read and control digital audio CDs ii libcdio-dev 0.83-4.2 amd64library to read and control CD-ROM (development files) ii libcdio-paranoia1 0.83-4.2 amd64library to read digital audio CDs with error correction ii libcdio13 0.83-4.2 amd64library to read and control CD-ROM dmitry@D-NESTERKIN:~/libburn-1.3.4$ Default compilation parameters give me these errors while burning: https://www.dropbox.com/sh/0dbmyd53bx36s7z/AABT5pJnSsvjzuWZwEirJJSba?dl=0 2015-06-25 15:40 GMT+03:00 Thomas Schmitt scdbac...@gmx.net: Hi, Session error : Во время записи на диск произошла ошибка The curse of i18n. Which of my messages might this be ? (Translators, please judge wisely which message might be for the experts and developers and not for the users.) BraseroLibburn SCSI command 2Ah yielded host problem: 0x7 SG_ERR_DID_ERROR Luckily this was not translated. Regrettably we still have the same cause of failure perceived by libburn: Linux SG_IO indicates error. I've tried to install 1.3.4 and 1.3.8 but the problem is still there I would be astonished if it would vanish. (But one never knows ...) The decisive difference between the Linux distros must be somewhere else. We outruled kernel configuration, version (?), and libburn version. There remains systemd, udev, et.al. And there remains the desktop suite. Have a nice day :) Thomas -- С уважением, Нестеркин Дмитрий
Bug#789942: mapnik-vector-tile: FTBFS with mapnik 3.0(?): mapnik/graphics.hpp: No such file or directory
Package: mapnik-vector-tile Version: 0.5.1+dfsg-1.3 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build in sid: ake[2]: Entering directory '/mapnik-vector-tile-0.5.1+dfsg' echo #define MAPNIK_PLUGINDIR \/usr/lib/mapnik/3.0/input\ test/test-cfg.h In file included from test/vector_tile.cpp:6:0: test/test_utils.hpp:6:31: fatal error: mapnik/graphics.hpp: No such file or directory #include mapnik/graphics.hpp ^ compilation terminated. I believe this is due to libmapnik-dev pulling in mapnik 3.0. See also e.g. http://bugs.debian.org/788767 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/mapnik-vector-tile.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789775: zabbix-server: Zabbix server exits after 'One child process died'
Hi Chris, Two more thoughts -- it may be useful to increase log verbosity and check syslog as well. The latter may answer if zabbix server segfaults or geting OOM-killed... -- All the best, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#789604: release-notes: 'halt' behaviour changed without notice
Vincent McIntyre wrote: I'm submitting this patch on the advice of the systemd maintainers. Could this be applied to the jessie release notes? It's good, but I've got a couple of English usage nitpicks: Index: issues.dbk === --- issues.dbk(revision 10955) +++ issues.dbk(working copy) @@ -586,7 +586,22 @@ bug #784720/ulink /para /section +section id=systemd-halt-behaviour + !-- Wheezy to Jessie (#760923) -- + titlesystemd: behaviour of 'halt' command/title ^ The rest of the releasenotes is standardised to en_US (with several behaviors just on this page). + para +The systemitem role=packagesysvinit/systemitem implementation +of the commandhalt/command command powered off the machine as well. +The systemitem role=packagesystemd-sysv/systemitem implementation +of the commandhalt/command halts the system, but does not power off ^^ That's either of halt or of the halt command; or we could just drop the phrase entirely as unnecessary repetition (as in my patch). +the machine. To halt the machine and turn it off, +use the commandpoweroff/command command. + /para + para +See also ulink url=url-bts;760923Debian bug #760923/ulink + /para /section +/section -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package Index: en/issues.dbk === --- en/issues.dbk (revision 10955) +++ en/issues.dbk (working copy) @@ -586,7 +586,21 @@ bug #784720/ulink /para /section +section id=systemd-halt-behavior + !-- Wheezy to Jessie (#760923) -- + titlesystemd: behavior of 'halt' command/title + para +The systemitem role=packagesysvinit/systemitem implementation +of the commandhalt/command command powered off the machine as well. +The systemitem role=packagesystemd-sysv/systemitem implementation +halts the system, but does not power off the machine. To halt the +machine and turn it off, use the commandpoweroff/command command. + /para + para +See also ulink url=url-bts;760923Debian bug #760923/ulink + /para /section +/section section id=required-kernel-config-options !-- Wheezy to Jessie --
Bug#782620: tightvncserver: SIGSEGV in WaitForSomething
Hi again, this just occurred again. This time I can say it happened when I tried to start Kontact (KDEPIM) in VNC. Please fix, a segfault is never acceptable (except in cases of stack underrun in programming language interpreters for languages designed to not limit recursion depth except by the OS). bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789931: itksnap: FTBFS in unstable
It looks like the ITK-SNAP build does not find the ITK directory. This is a pretty outdated version, we are up to 3.2 now... Paul On Thu, Jun 25, 2015 at 12:38 PM, Edmund Grimley Evans edmund.grimley.ev...@gmail.com wrote: Source: itksnap Version: 2.2.0-1.1 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=itksnapsuite=sid I got the same error on amd64. -- Paul A. Yushkevich, Ph.D. Associate Professor Penn Image Computing and Science Laboratory Department of Radiology University of Pennsylvania
Bug#789760: arc diff fails with a conduit error
Control: tags 789760 + patch
On Wed, 24 Jun 2015 at 09:38:42 +0200, Sjoerd Simons wrote:
Exception
ERR-CONDUIT-CORE: Invalid parameter information was passed to method
'differential.query', could not decode JSON serialization. Data:
{authors:[PHID-USER-tiexds33yvgetrvgglxc],status:status-open,ids%3
Looks as though this is actually a curl bug:
https://github.com/bagder/curl/commit/903b6e05565bf826b4194447864288642214b094
Workaround committed upstream for arcanist:
https://github.com/phacility/libphutil/commit/e9fea5c64c0c4ba9b809fc97b16007df891bba60.patch
Regards,
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789828: unreproducible / pbuilder vs. sbuild
I can't reproduce these 2 bugs. Apparently #789828 happens only with sbuild and not with p/cowbuiler, maybe #789830 falls into the same category ... Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Bob Dylan: Sad eyed lady of the lowlands signature.asc Description: Digital Signature
Bug#789943: [pkg-php-pear] Bug#789943: FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica
2015-06-25 17:20 GMT+02:00 David Prévot taf...@debian.org: [...] FWIW, I do use this version for a month already without any issue so far, except maybe not noticing FTBFSes like this one any more. The range specification was updated recently (in Composer 1.0.0~alpha10) [3]. Hypen range is a bit trickier to handle as far as I’ve tried, but is not yet used in what is currently packaged in Debian AFAIK. I've uploaded it you can do future upload as a team upload. -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789984: pulseaudio: Incorrect detecting 2.1 audiosystem on newer laptops (ASUS N750J series)
Package: pulseaudio Version: 5.0-13 Severity: normal Hello! I have notebook ASUS N750JK and Subwoofer Sonic Master. The package pulseaudio don't have news modes (2.1) for this machine. Now exist new version of pulseaudio (v6). Please, replease to new version of pulseaudio in stable realease. Thank you. p.s.: sorry for my bad English. -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pulseaudio depends on: ii adduser 3.113+nmu3 ii libasound21.0.28-1 ii libasound2-plugins1.0.28-1+b1 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libdbus-1-3 1.8.18-0+deb8u1 ii libfftw3-single3 3.3.4-2 ii libgcc1 1:4.9.2-10 ii libice6 2:1.0.9-1+b1 ii libltdl7 2.4.2-1.11 ii liborc-0.4-0 1:0.4.22-1 ii libpulse0 5.0-13 ii libsamplerate00.1.8-8 ii libsm62:1.2.2-1+b1 ii libsndfile1 1.0.25-9.1 ii libspeexdsp1 1.2~rc1.2-1 ii libstdc++64.9.2-10 ii libsystemd0 215-17+deb8u1 ii libtdb1 1.3.1-1 ii libudev1 215-17+deb8u1 ii libwebrtc-audio-processing-0 0.1-3 ii libx11-6 2:1.6.2-3 ii libx11-xcb1 2:1.6.2-3 ii libxcb1 1.10-3+b1 ii libxtst6 2:1.2.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii pulseaudio-utils 5.0-13 ii udev 215-17+deb8u1 Versions of packages pulseaudio recommends: ii pulseaudio-module-x11 5.0-13 ii rtkit 0.11-2 Versions of packages pulseaudio suggests: pn pamannone pn paprefs none pn pavucontrol none pn pavumeternone -- no debconf information # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 # USA. ## Configuration file for PulseAudio clients. See pulse-client.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; default-sink = ; default-source = ; default-server = ; default-dbus-server = ; autospawn = yes ; daemon-binary = /usr/bin/pulseaudio ; extra-arguments = --log-target=syslog ; cookie-file = ; enable-shm = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; auto-connect-localhost = no ; auto-connect-display = no # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 # USA. ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; daemonize = no ; fail = yes ; allow-module-loading = yes ; allow-exit = yes ; use-pid-file = yes ; system-instance = no ; local-server-type = user ; enable-shm = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; lock-memory = no ; cpu-limit = no ; high-priority = yes ; nice-level = -11 ; realtime-scheduling = yes ; realtime-priority = 5 ; exit-idle-time = 20 ; scache-idle-time = 20 ; dl-search-path =
Bug#789985: FTBFS: IRanges_defines.h: fatal error: S4Vectors_defines.h: No such file or directory
Package: r-bioc-shortread Version: 1.22.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: config.status: creating src/Makevars ** libs make[1]: Entering directory '/tmp/buildd/r-bioc-shortread-1.22.0/src' gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I/usr/lib/R/site-library/IRanges/include -I/usr/lib/R/site-library/XVector/include -I/usr/lib/R/site-library/Biostrings/include -fopenmp -fpic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -c Biostrings_stubs.c -o Biostrings_stubs.o In file included from /usr/lib/R/site-library/Biostrings/include/Biostrings_defines.h:18:0, from /usr/lib/R/site-library/Biostrings/include/Biostrings_interface.h:114, from /usr/lib/R/site-library/Biostrings/include/_Biostrings_stubs.c:1, from Biostrings_stubs.c:1: /usr/lib/R/site-library/IRanges/include/IRanges_defines.h:18:31: fatal error: S4Vectors_defines.h: No such file or directory #include S4Vectors_defines.h ^ compilation terminated. /usr/lib/R/etc/Makeconf:134: recipe for target 'Biostrings_stubs.o' failed Maybe this is a bug in r-bioc-biostrings, or r-bioc-iranges? The same bug affects at least r-bioc-genomicalignments, r-bioc-rtracklayer, and r-bioc-variantannotation. (all same maintainer) Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/r-bioc-shortread.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785786: efibootmgr: Could not delete boot variable: Success
On 06/25/2015 05:58 PM, D. Jared Dominguez wrote: Are you still seeing this issue with libefivar0 0.20-4 and efibootmgr 0.12-3? Thank you, this resolves the problem for me! :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775558: digikam crashes on startup - matroska video
This should be fixed by updating to exiv2 library version 0.25. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789956 http://exiv2.org/changelog.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752702: apt: please add a way to to retrieve the location of Packages/Sources files in /var/lib/apt/lists/
On Wed, Jun 24, 2015 at 11:25:54PM +0200, Johannes Schauer wrote: Hi, Quoting David Kalnischkies (2015-06-24 23:18:12) So, long story short, the solution I would like to propose is: $ apt-get files Codename: sid Trusted: yes Created-By: Packages […] so the arguments to apt-get files are fields and values and the command will output all paragraphs where all those fields match? Can one omit these field:value pairs to get everything? This would allow doing a custom selection with the more powerful grep-dctrl tool for example. Sure, but I realize now the doc isn't very clear about that… In fact, it is pretty much expected to us another tool to do the heavy lifting as I really don't want to implement any kind of fancy filtering, hence the deb822 format as in a Debian context that should be easy to deal with. This crude line-filtering is mostly there for times in which you don't want/can't use anything more powerful (like apt testcases where piping is hard™ compared to just calling a single command and performing (additional) tests on its exit status and output automatically). I will add some explicit mentioning of grep-dctrl and an example for good measure. Thanks for the quick feedback! Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#789925: fusionforge-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/locale/bg/LC_MESSAGES/fusionforge.mo
Package: fusionforge-common Version: 6.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails 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 fusionforge-common. Preparing to unpack .../fusionforge-common_6.0.1-1_all.deb ... Unpacking fusionforge-common (6.0.1-1) ... dpkg: error processing archive /var/cache/apt/archives/fusionforge-common_6.0.1-1_all.deb (--unpack): trying to overwrite '/usr/share/locale/bg/LC_MESSAGES/fusionforge.mo', which is also in package gforge-common 5.3.2+20141104-3+deb8u1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../gforge-common_6.0.1-1_all.deb ... Unpacking gforge-common (6.0.1-1) over (5.3.2+20141104-3+deb8u1) ... dpkg: warning: unable to delete old directory '/var/lib/gforge': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/gforge/common/include': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/gforge/common': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/gforge': Directory not empty dpkg: warning: unable to delete old directory '/etc/fusionforge/custom': Directory not empty dpkg: warning: unable to delete old directory '/etc/fusionforge/config.ini.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/fusionforge': Directory not empty Errors were encountered while processing: /var/cache/apt/archives/fusionforge-common_6.0.1-1_all.deb cheers, Andreas gforge-common_6.0.1-1.log.gz Description: application/gzip
