Bug#657565: xorg-server: please switch to the standard FontPath setup
On Fri, 2012-01-27 at 08:27 +0800, Paul Wise wrote:
Now that x-ttcidfont-conf has been removed, Debian's custom FontPath
serves no purpose, please remove it. I have attached a patch.
Here is a bonus patch to replace x-ttcidfont-conf with a separate
symlink farm maintained using triggers. It uses an IFS hack for a slight
speedup but you may prefer to use the sed version for readability.
--
bye,
pabs
http://wiki.debian.org/PaulWise
From 76e0a3ca842bd4e719f0049e6593a9324097fe6e Mon Sep 17 00:00:00 2001
From: Paul Wise p...@debian.org
Date: Thu, 3 May 2012 12:57:16 +0800
Subject: [PATCH 2/2] Create a symlink farm of available fonts and use
triggers to update it.
---
debian/xserver-xorg-core.dirs |1 +
debian/xserver-xorg-core.links|1 +
debian/xserver-xorg-core.postinst | 52 +
debian/xserver-xorg-core.postrm |1 +
debian/xserver-xorg-core.triggers |1 +
5 files changed, 56 insertions(+)
create mode 100644 debian/xserver-xorg-core.links
create mode 100644 debian/xserver-xorg-core.postinst
create mode 100644 debian/xserver-xorg-core.triggers
diff --git a/debian/xserver-xorg-core.dirs b/debian/xserver-xorg-core.dirs
index bd697ab..b7bff43 100644
--- a/debian/xserver-xorg-core.dirs
+++ b/debian/xserver-xorg-core.dirs
@@ -1 +1,2 @@
etc/X11/fontpath.d
+var/lib/xserver-xorg-core/fonts
diff --git a/debian/xserver-xorg-core.links b/debian/xserver-xorg-core.links
new file mode 100644
index 000..8a2d336
--- /dev/null
+++ b/debian/xserver-xorg-core.links
@@ -0,0 +1 @@
+etc/X11/fontpath.d/system var/lib/xserver-xorg-core/fonts
diff --git a/debian/xserver-xorg-core.postinst b/debian/xserver-xorg-core.postinst
new file mode 100644
index 000..8423765
--- /dev/null
+++ b/debian/xserver-xorg-core.postinst
@@ -0,0 +1,52 @@
+#!/bin/sh
+
+set -e
+
+# Paths
+fonts=/usr/share/fonts
+lnfarm=/var/lib/xserver-xorg/fonts
+
+update_font_symlink_farm ()
+{
+ # Create symlinks for relevant fonts
+ find $fonts -type f ! -wholename $fonts/X11/* |
+while read filename ; do
+ # Strip fonts dir prefix
+ target=${filename#$fonts/}
+ # Hack to replace / characters with _
+ ifs=$IFS; IFS=/; set -- $target; IFS=_; target=$*; IFS=$ifs
+ # Add the symlink farm dir prefix
+ target=$lnfarm/$target
+ # Create a symlink if it is needed
+ ln -s $filename $target 2/dev/null || true
+ # Alternative version that forks sed
+ #ln -s $filename $lnfarm/$(echo $filename | sed s_$fonts/__;s:/:_:g) 2/dev/null || true
+done
+ # Delete broken symlinks
+ find -L $lnfarm -type l -delete 2/dev/null || true
+}
+
+case $1 in
+configure)
+ if [ -n $(find $lnfarm -type d -empty 2/dev/null) ] ; then
+update_font_symlink_farm
+ fi
+ ;;
+triggered)
+ for name in $2; do
+case $name in
+$fonts)
+ update_font_symlink_farm
+ ;;
+*)
+ echo unhandled/unknown trigger!
+ exit 1
+ ;;
+esac
+ done
+ ;;
+esac
+
+#DEBHELPER#
+
+# vim:set ai et sts=2 sw=2 tw=0:
diff --git a/debian/xserver-xorg-core.postrm b/debian/xserver-xorg-core.postrm
index 0eb50b1..006d58a 100644
--- a/debian/xserver-xorg-core.postrm
+++ b/debian/xserver-xorg-core.postrm
@@ -6,6 +6,7 @@ case $1 in
purge)
rm /var/log/Xorg.*.log || true
rm /var/log/Xorg.*.log.old || true
+ find /var/lib/xserver-xorg/fonts/ -type l -delete || true
;;
esac
diff --git a/debian/xserver-xorg-core.triggers b/debian/xserver-xorg-core.triggers
new file mode 100644
index 000..fc1e745
--- /dev/null
+++ b/debian/xserver-xorg-core.triggers
@@ -0,0 +1 @@
+interest /usr/share/fonts
--
1.7.10
signature.asc
Description: This is a digitally signed message part
Bug#671297: isdnutils-base and libcapi20-dev: error when trying to install together
Package: libcapi20-dev,isdnutils-base Version: libcapi20-dev/1:3.22+dfsg1-3 Version: isdnutils-base/1:3.22+dfsg1-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-05-03 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: WARNING: The following packages cannot be authenticated! isdnutils-base libcapi20-3 libcapi20-dev Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package isdnutils-base. (Reading database ... 10558 files and directories currently installed.) Unpacking isdnutils-base (from .../isdnutils-base_1%3a3.22+dfsg1-3_amd64.deb) ... Selecting previously unselected package libcapi20-3. Unpacking libcapi20-3 (from .../libcapi20-3_1%3a3.22+dfsg1-3_amd64.deb) ... Selecting previously unselected package libcapi20-dev. Unpacking libcapi20-dev (from .../libcapi20-dev_1%3a3.22+dfsg1-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libcapi20-dev_1%3a3.22+dfsg1-3_amd64.deb (--unpack): trying to overwrite '/usr/include/isdn_dwabclib.h', which is also in package isdnutils-base 1:3.22+dfsg1-3 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libcapi20-dev_1%3a3.22+dfsg1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) cow-shell unlink .ilist: No such file or directory 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/include/isdn_dwabclib.h -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659702: Announce of the upcoming NMU for the durep package
Dear maintainer of durep and Debian translators, Some days ago, I sent a notice to the maintainer of the durep Debian package, mentioning the status of at least one old po-debconf translation update in the BTS. I announced the intent to build and possibly upload a non-maintainer upload for this package in order to fix this long-time pending localization bug as well as all other pending translations. The package maintainer agreed for the NMU or did not respond in four days, so I will proceed with the NMU. The full planned schedule is available at the end of this mail. The package is currently translated to: cs da de en es fr it ja nl pt ru sv vi Among these, the following translations are incomplete: none If you did any of the, currently incomplete, translations you will get ANOTHER mail with the translation to update. Other translators also have the opportunity to create new translations for this package. Once completed, please send them as a bug report against the durep package so I can incorporate them in the build. The deadline for receiving updates and new translations is Friday, May 11, 2012. If you are not in time you can always send your translation to the BTS. The POT file is attached to this mail. If the maintainer objects to this process I will immediately abort my NMU and send him/her all updates I receive. Otherwise the following will happen (or already has): Saturday, April 28, 2012 : send the first intent to NMU notice to the package maintainer. Thursday, May 03, 2012 : send this notice Friday, May 11, 2012 : (midnight) deadline for receiving translation updates Saturday, May 12, 2012 : build the package and upload it to DELAYED/7-day send the NMU patch to the BTS Saturday, May 19, 2012 : NMU uploaded to incoming Thanks for your efforts and time. -- -- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR EMAIL@ADDRESS, YEAR. # #, fuzzy msgid msgstr Project-Id-Version: PACKAGE VERSION\n Report-Msgid-Bugs-To: du...@packages.debian.org\n POT-Creation-Date: 2010-02-03 17:23+0100\n PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n Last-Translator: FULL NAME EMAIL@ADDRESS\n Language-Team: LANGUAGE l...@li.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=CHARSET\n Content-Transfer-Encoding: 8bit\n #. Type: string #. Description #: ../templates:1001 msgid HTTP directory for supplementary files: msgstr #. Type: string #. Description #: ../templates:1001 msgid If this package shall provide disk usage information through a HTTP CGI- service, it needs a public web directory containing additional files like style sheet and images. This directory should be visible as '/durep' on the web site where the durep.cgi page is located. msgstr #. Type: string #. Description #: ../templates:1001 msgid Due to FHS policy these files are not automatically installed to system directories. To make them accessible, they can either be copied into a location inside the HTTP root directory, or the web server needs to be configured accordingly. msgstr #. Type: string #. Description #: ../templates:1001 msgid To configure the Apache webserver (for example), the following directive creates the needed directory alias: msgstr #. Type: string #. Description #: ../templates:1001 msgid Alias /durep /usr/share/durep/www msgstr #. Type: string #. Description #: ../templates:1001 msgid To install supplementary files into another root directory please specify its path here. The directory must already exist. A typical answer would be '/ var/www'. The subdirectory '/durep' with files will be created automatically, the files will be installed from '/usr/share/durep/www' unless they already exist. msgstr #. Type: boolean #. Description #: ../templates:2001 msgid Do you want to enable daily report generation? msgstr #. Type: boolean #. Description #: ../templates:2001 msgid If you wish, a daily script will create disk usage statistics of chosen filesystems. They will be kept for seven days. msgstr #. Type: boolean #. Description #: ../templates:2001 msgid WARNING: with the default configuration, the statistics are stored in the public httpd directory, /var/www/durep. This may breach the privacy of the users. msgstr #. Type: string #. Description #: ../templates:3001 msgid List of filesystems for durep reports: msgstr #. Type: string #. Description #: ../templates:3001 msgid To specify single filesystems to report on, enter their mount points separated by spaces (eg. \/data /var\). A single dot (\.\) means scanning of the whole UNIX filesystem tree. msgstr signature.asc Description: Digital signature
Bug#671298: libdrmaa-dev and gridengine-drmaa-dev: error when trying to install together
Package: gridengine-drmaa-dev,libdrmaa-dev Version: gridengine-drmaa-dev/6.2u5-5 Version: libdrmaa-dev/6.2u5-4 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-05-03 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: WARNING: The following packages cannot be authenticated! gridengine-drmaa1.0 gridengine-drmaa-dev libdrmaa1.0 libdrmaa-dev Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package gridengine-drmaa1.0. (Reading database ... 10558 files and directories currently installed.) Unpacking gridengine-drmaa1.0 (from .../gridengine-drmaa1.0_6.2u5-5_amd64.deb) ... Selecting previously unselected package gridengine-drmaa-dev. Unpacking gridengine-drmaa-dev (from .../gridengine-drmaa-dev_6.2u5-5_amd64.deb) ... Selecting previously unselected package libdrmaa1.0. Unpacking libdrmaa1.0 (from .../libdrmaa1.0_6.2u5-4_amd64.deb) ... Selecting previously unselected package libdrmaa-dev. Unpacking libdrmaa-dev (from .../libdrmaa-dev_6.2u5-4_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libdrmaa-dev_6.2u5-4_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/jsv_script_interface.3.gz', which is also in package gridengine-drmaa-dev 6.2u5-5 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libdrmaa-dev_6.2u5-4_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/share/man/man3/drmaa_allocate_job_template.3.gz /usr/share/man/man3/drmaa_attributes.3.gz /usr/share/man/man3/drmaa_control.3.gz /usr/share/man/man3/drmaa_delete_job_template.3.gz /usr/share/man/man3/drmaa_exit.3.gz /usr/share/man/man3/drmaa_get_DRMAA_implementation.3.gz /usr/share/man/man3/drmaa_get_DRM_system.3.gz /usr/share/man/man3/drmaa_get_attribute.3.gz /usr/share/man/man3/drmaa_get_attribute_names.3.gz /usr/share/man/man3/drmaa_get_contact.3.gz /usr/share/man/man3/drmaa_get_next_attr_name.3.gz /usr/share/man/man3/drmaa_get_next_attr_value.3.gz /usr/share/man/man3/drmaa_get_next_job_id.3.gz /usr/share/man/man3/drmaa_get_num_attr_names.3.gz /usr/share/man/man3/drmaa_get_num_attr_values.3.gz /usr/share/man/man3/drmaa_get_num_job_ids.3.gz /usr/share/man/man3/drmaa_get_vector_attribute.3.gz /usr/share/man/man3/drmaa_get_vector_attribute_names.3.gz /usr/share/man/man3/drmaa_init.3.gz /usr/share/man/man3/drmaa_job_ps.3.gz /usr/share/man/man3/drmaa_jobcontrol.3.gz /usr/share/man/man3/drmaa_jobtemplate.3.gz /usr/share/man/man3/drmaa_misc.3.gz /usr/share/man/man3/drmaa_release_attr_names.3.gz /usr/share/man/man3/drmaa_release_attr_values.3.gz /usr/share/man/man3/drmaa_release_job_ids.3.gz /usr/share/man/man3/drmaa_run_bulk_jobs.3.gz /usr/share/man/man3/drmaa_run_job.3.gz /usr/share/man/man3/drmaa_session.3.gz /usr/share/man/man3/drmaa_set_attribute.3.gz /usr/share/man/man3/drmaa_set_vector_attribute.3.gz /usr/share/man/man3/drmaa_strerror.3.gz /usr/share/man/man3/drmaa_submit.3.gz /usr/share/man/man3/drmaa_synchronize.3.gz /usr/share/man/man3/drmaa_version.3.gz /usr/share/man/man3/drmaa_wait.3.gz /usr/share/man/man3/drmaa_wcoredump.3.gz /usr/share/man/man3/drmaa_wexitstatus.3.gz /usr/share/man/man3/drmaa_wifaborted.3.gz /usr/share/man/man3/drmaa_wifexited.3.gz /usr/share/man/man3/drmaa_wifsignaled.3.gz /usr/share/man/man3/drmaa_wtermsig.3.gz /usr/share/man/man3/jsv_script_interface.3.gz -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608856: I'm also seeing this in version 10.0.3
Same problem here with Iceweasel 10.0.3. See my backtrace below. However, all the messages below were issued *before* the crash. Thanks, Adriano Running global cleanup code from study base classes. No bp log location saved, using default. [000:001] Browser XEmbed support present: 1 [000:001] Browser toolkit is Gtk2. [000:002] Using Gtk2 toolkit [000:006] Warning(clientchannel.cc:637): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection [000:007] Warning(clientchannel.cc:451): Could not initiate GoogleTalkPlugin connection [000:007] GoogleTalkPlugin not running. Starting new process... [000:007] Warning(optionsfile.cc:47): Load: Could not open file, err=2 [000:007] Warning(clientchannel.cc:607): Failed to get GoogleTalkPlugin path. Trying default. [000:009] Started GoogleTalkPlugin, path=/opt/google/talkplugin/GoogleTalkPlugin [000:009] Waiting for GoogleTalkPlugin to start... sh: 1: lsb_release: not found [001:106] Attempting to connect to GoogleTalkPlugin... [001:106] Read port file, port=51856 [001:111] Initiated connection to GoogleTalkPlugin [001:215] Socket connection established [001:215] ScheduleOnlineCheck: Online check in 5000ms [001:307] Got cookie response, socket is authorized [001:307] AUTHORIZED; socket handshake complete [006:220] HandleOnlineCheck: Starting check [006:220] HandleOnlineCheck: OK; current state: 3 [044:437] Read port file, port=51856 [044:438] Initiated connection to GoogleTalkPlugin [044:673] Socket connection established [044:673] ScheduleOnlineCheck: Online check in 5000ms [044:774] Got cookie response, socket is authorized [044:774] AUTHORIZED; socket handshake complete [049:687] HandleOnlineCheck: Starting check [049:687] HandleOnlineCheck: OK; current state: 3 error: An exception occurred. Traceback (most recent call last): File resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/tabs/tab.js, line 71, in _onReady this._emit(EVENTS.ready.name, this._public); File resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/events.js, line 119, in _emit return this._emitOnObject.apply(this, args); File resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/events.js, line 149, in _emitOnObject listener.apply(targetObj, params); File resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/windows/tabs.js, line 102, in _emitEvent tabs._emit(type, tab); File resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/events.js, line 119, in _emit return this._emitOnObject.apply(this, args); File resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/events.js, line 149, in _emitOnObject listener.apply(targetObj, params); File resource://jid1-f9uj2thwoam5gq-at-jetpack/collusion/lib/main.js, line 374, in null var domain = getDomain(ioService.newURI(tab.url, null, null).host); [Exception... Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.host] nsresult: 0x80004005 (NS_ERROR_FAILURE) location: JS frame :: resource://jid1-f9uj2thwoam5gq-at-jetpack/api-utils/lib/cuddlefish.js - resource://jid1-f9uj2thwoam5gq-at-jetpack/collusion/lib/main.js :: TOP_LEVEL :: line 374 data: no] (firefox-bin:28689): libnotify-WARNING **: Failed to connect to proxy okular(28840)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(28840)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(28840)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(28840)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(28840)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(28840)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x1edfaf8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. okular(29365)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(29365)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(29365)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(29365)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(29365)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(29365)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x16dfe58 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. SSL Observatory: Could not get host IP address. SSL Observatory: Could not get host IP address. java version 1.6.0_24 OpenJDK Runtime Environment (IcedTea6 1.11.1) (6b24-1.11.1-3) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) SSL Observatory: Could not get host IP address. ALSA lib conf.c:1220:(parse_def) show is not a compound ALSA lib conf.c:1686:(snd_config_load1) _toplevel_:24:26:Unexpected char ALSA lib conf.c:3406:(config_file_open) /usr/share/alsa/pulse-alsa.conf may be old or corrupted: consider to remove or fix it Killed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.
Bug#587404: aptitude: keeps running forever on nonassisted script
Daniel Franganillo dfrangani...@gmail.com wrote: Hi, at work we have quite a few debian stable servers updated daily with this script via cron jobs: [snip] The line: yes Y | aptitude -d safe-upgrade /dev/null sometimes keeps running forever, so we have to kill the process, and other times ends as expected. The packages are being downloaded right so we dont know whats exactly doing. Thanks. Hello This looks like a lot like #629266, -d has infinite loop after downloads. There is a patch[1] available which should fix your case also. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629266;msg=17 Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670962: [Pkg-amule-devel] Bug#670962: amule: FTBFS (cannot convert 'UpnpString* {aka s_UpnpString*}' to 'const char*')
Hi Cyril, On Thu, May 3, 2012 at 3:52 AM, Cyril Brulebois k...@debian.org wrote: Anyway, the following patch allows amule to build, but I performed no run-time test. Thanks for the patch! I've just forwarded upstream (which is currently tracking it at http://forum.amule.org/index.php?topic=19738). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671238: linux-image-2.6.32-5-s390x: no CMM with z/VM Resource Manager possible
severity 671238 important thanks On Wed, May 02, 2012 at 07:12:45PM +0200, Martin Grimm wrote: CMM (Cooperative Memory Management) can't be controlled from z/VM Resource Manager because the core component (cmm) is builtin and the needed communication module (smsgiucv) is build as a module. Loading the module smsgiucv doesn't help. Which versions are affected? I believe both Squeeze (2.6.32) and Wheezy (3.2). Bastian -- Fascinating is a word I use for the unexpected. -- Spock, The Squire of Gothos, stardate 2124.5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671299: Replace Indian Rupee sign in all Indian locales
Package: eglibc version: 2.13-32 The new Indian rupee sign U20B9 is not included in any of the Indian locales. I have attached the patch to update all Indian locales for the new Rupee sign. Since it is not included yet, gnome-control-center languages displays the older rupee sign. -- Regards., Prema S ruppeesign.patch Description: Binary data
Bug#671300: fontconfig: [INTL:nl] Dutch translation of debconf templates
Package: fontconfig Severity: wishlist Tags: patch l10n Hello, Attached is the updated Dutch translation of the fontconfig debconf templates. Please include it in your next upload. Kind regards, Jeroen Schot # Dutch translation of fontconfig debconf templates. # Copyright (C) 2004-2007,2012 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the fontconfig package. # Frans Pop arag...@tiscali.nl, 2004, 2005, 2006. # Frans Pop elen...@planet.nl, 2007. # Jeroen Schot sc...@a-eskwadraat.nl, 2012. # msgid msgstr Project-Id-Version: fontconfig 2.9.0-3\n Report-Msgid-Bugs-To: fontcon...@packages.debian.org\n POT-Creation-Date: 2012-04-30 10:00-0700\n PO-Revision-Date: 2012-05-03 09:24+0200\n Last-Translator: Jeroen Schot sc...@a-eskwadraat.nl\n Language-Team: Debian l10n Dutch debian-l10n-du...@lists.debian.org\n Language: nl\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: select #. Choices #: ../fontconfig-config.templates:2001 msgid Native msgstr Standaard #. Type: select #. Choices #: ../fontconfig-config.templates:2001 msgid Autohinter msgstr Autohinter #. Type: select #. Choices #: ../fontconfig-config.templates:2001 msgid None msgstr Niet optimaliseren #. Type: select #. Description #: ../fontconfig-config.templates:2002 msgid Font tuning method for screen (system default): msgstr Optimalisatie van weergave van lettertypen op beeldscherm (systeemstandaard): #. Type: select #. Description #: ../fontconfig-config.templates:2002 msgid Please select the preferred method for tuning fonts for screen rendering. msgstr Selecteer de gewenste methode voor de optimalisatie van de weergave van lettertypen op het beeldscherm. #. Type: select #. Description #: ../fontconfig-config.templates:2002 msgid Select 'Native' if you mostly use DejaVu (the default in Debian) or any of the Microsoft fonts. Select 'Autohinter' if you mostly use other TrueType fonts. Select 'None' if you want blurry text. msgstr Selecteer \Standaard\ als u voornamelijk het lettertype DejaVu (de standaard in Debian) of een van de Microsoft-lettertypen gebruikt. Selecteer \Autohinter\ als u voornamelijk andere TrueType-lettertypen gebruikt. Selecteer \Niet optimaliseren\ als u de voorkeur geeft aan wazige tekst. #. Type: select #. Choices #: ../fontconfig-config.templates:3001 msgid Automatic msgstr Automatisch #. Type: select #. Choices #: ../fontconfig-config.templates:3001 msgid Always msgstr Altijd #. Type: select #. Choices #: ../fontconfig-config.templates:3001 msgid Never msgstr Nooit #. Type: select #. Description #: ../fontconfig-config.templates:3002 msgid Enable subpixel rendering for screen: msgstr Activeren van subpixel-weergave voor beeldscherm: #. Type: select #. Description #: ../fontconfig-config.templates:3002 msgid Rendering text at a subpixel level generally makes it look a bit better on flat (LCD) screens, but can show color artifacts on CRT screens. The \Automatic\ choice will enable it only if a LCD screen is detected. msgstr Het genereren van tekst op subpixel-niveau zorgt over het algemeen voor een verbetering van de weergave op platte beeldschermen (LCD), maar kan op een CRT-scherm leiden tot verkleuringen. De keuze \Automatisch\ zal deze optie alleen inschakelen als een LCD-scherm wordt gedetecteerd. #. Type: boolean #. Description #: ../fontconfig-config.templates:4001 msgid Enable bitmapped fonts by default? msgstr Bitmap-lettertypen standaard activeren? #. Type: boolean #. Description #: ../fontconfig-config.templates:4001 msgid By default, only outline fonts are used by applications which support fontconfig. msgstr Standaard worden alleen 'outline'-lettertypen gebruikt door applicaties die fontconfig ondersteunen. #. Type: boolean #. Description #: ../fontconfig-config.templates:4001 msgid Outline fonts are fonts which scale well to various sizes. In contrast, bitmapped fonts are often lower quality. Enabling this option will affect the systemwide default; this and many other fontconfig options may be enabled or disabled on a per-user basis. msgstr 'Outline'-lettertypen zijn lettertypen die goed geschaald kunnen worden naar verschillende lettergroottes. Daarentegen zijn 'bitmapped'-lettertypen vaak van een lagere kwaliteit. De instelling van deze optie geldt voor het gehele systeem; deze (en vele andere) opties van fontconfig kunnen ook voor elke gebruiker afzonderlijk ingesteld worden.
Bug#656128: Bug #656128 Please enabled hardened build flags
Dear Simon, Thank you very much for following and for detailed description of problem - we will fix it for sure in next upload. Sorry for troubles, I should feel ashamed for missing it. Regards, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671301: mcollective: [INTL:nl] Dutch translation of debconf templates
Package: mcollective Severity: wishlist Tags: patch l10n Hello, Attached is the Dutch translation of the mcollective debconf templates. Please include it in your next upload. Kind regards, Jeroen Schot # Dutch translation of mcollective debconf templates. # Copyright (C) 2012 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the mcollective package. # Jeroen Schot sc...@a-eskwadraat.nl, 2012. # msgid msgstr Project-Id-Version: mcollective 1.2.1+dfsg-2\n Report-Msgid-Bugs-To: mcollect...@packages.debian.org\n POT-Creation-Date: 2011-10-10 07:09+0200\n PO-Revision-Date: 2012-05-03 09:27+0200\n Last-Translator: Jeroen Schot sc...@a-eskwadraat.nl\n Language-Team: Debian l10n Dutch debian-l10n-du...@lists.debian.org\n Language: nl\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: string #. Description #: ../mcollective-common.templates:2001 msgid MCollective PSK: msgstr MCollective PSK: #. Type: string #. Description #: ../mcollective-common.templates:2001 msgid Please specify the Pre-Shared Key that should be used between MCollective instances. msgstr Geef de vooraf gedeelde sleutel (PSK) die gebruikt moet worden tussen de verschillende MCollective-instanties. #. Type: string #. Description #: ../mcollective-common.templates:3001 msgid Message Queue server host: msgstr Message-Qeueu-server: #. Type: string #. Description #: ../mcollective-common.templates:3001 msgid Please specify the hostname or IP address of the Message Queue server for MCollective. msgstr Wat is de computernaam of het IP-adres van de Message-Queue-server voor MCollective? #. Type: string #. Description #: ../mcollective-common.templates:4001 msgid Message Queue server port: msgstr Message-Queue-serverpoort: #. Type: string #. Description #: ../mcollective-common.templates:4001 msgid Please specify the listening port of the Message Queue server. msgstr Op welke poort moet de Message-Queue-server luisteren? #. Type: string #. Description #: ../mcollective-common.templates:5001 msgid Message Queue server username: msgstr Message Queue-servergebruikersnaam: #. Type: string #. Description #: ../mcollective-common.templates:5001 msgid Please specify the STOMP username that should be used with the Message Queue server. msgstr Welke STOMP-gebruikersnaam moet er worden gebruikt met de Message-Queue- server? #. Type: password #. Description #: ../mcollective-common.templates:6001 msgid Message Queue server password: msgstr Message-Queue-serverwachtwoord: #. Type: password #. Description #: ../mcollective-common.templates:6001 msgid Please specify the STOMP password that should be used with the Message Queue server. msgstr Wat is het STOMP-wachtwoord dat moet worden gebruikt met de Message-Queue- server? #. Type: boolean #. Description #: ../mcollective.templates:2001 msgid Start MCollective on boot? msgstr Mcollective opstarten bij de systeemstart? #. Type: boolean #. Description #: ../mcollective.templates:2001 msgid Please choose whether the MCollective daemon should be started when booting this machine. msgstr Geef aan of de MCollective-achtergronddienst moet worden opgestart bij het starten van deze computer.
Bug#671302: libav: circular dependency between libav and opencv
Package: libav Version: 6:0.8.1-7 Severity: important Hi, libav 6:0.8.1-7 reenables the use of opencv... which itself uses libav libraries. This currently makes libav unbuildable on mipsel and hurd-i386, and generically makes libav no more bootstrap'able without having itself compiled already. Could you please drop the opencv usage again, please? Thanks, -- Pino -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669702: The patch networkmanagement.diff works
Dear Maintainer, I confirm that the patch works, and I also would like to see it merged. Thanks for your time, and for making Debian such a great OS.
Bug#670962: amule: FTBFS (cannot convert 'UpnpString* {aka s_UpnpString*}' to 'const char*')
Package: amule
Version: 2.3.1-1
Followup-For: Bug #670962
Tags: +patch
Hi,
I'm very sorry for ths oversight, I sneaked a last minute API change into
the libupnp6 package before the transition and missed this place where it
requires a source change. Please would you apply the attached patch to amule ?
Thanks and apologies
Nick (libupnp maintainer)
Index: amule-2.3.1/src/UPnPBase.cpp
===
--- amule-2.3.1.orig/src/UPnPBase.cpp 2012-05-02 22:13:52.0 +0100
+++ amule-2.3.1/src/UPnPBase.cpp 2012-05-02 22:14:09.0 +0100
@@ -1299,7 +1299,7 @@
} else {
#if 0
TvCtrlPointHandleSubscribeUpdate(
-es_event-PublisherUrl,
+UpnpString_get_String(es_event-PublisherUrl),
es_event-Sid,
es_event-TimeOut );
#endif
@@ -1324,7 +1324,7 @@
int TimeOut = 1801;
int ret = UpnpSubscribe(
upnpCP-m_UPnPClientHandle,
- es_event-PublisherUrl,
+ UpnpString_get_String(es_event-PublisherUrl),
TimeOut,
newSID);
if (ret != UPNP_E_SUCCESS) {
@@ -1333,13 +1333,13 @@
msg.str(), es_event-ErrCode, NULL, NULL);
} else {
ServiceMap::iterator it =
-upnpCP-m_ServiceMap.find(es_event-PublisherUrl);
+upnpCP-m_ServiceMap.find(UpnpString_get_String(es_event-PublisherUrl));
if (it != upnpCP-m_ServiceMap.end()) {
CUPnPService service = *(it-second);
service.SetTimeout(TimeOut);
service.SetSID(newSID);
msg2 Re-subscribed to EventURL '
- es_event-PublisherUrl
+ UpnpString_get_String(es_event-PublisherUrl)
' with SID == '
newSID '.;
AddDebugLogLineC(logUPnP, msg2);
Bug#671303: segfaults at startup when nscd is not running
Package: icedove Version: 10.0.3-3 Severity: important Hello, I am on a system that uses libnss-ldap. Icedove segfaults at startup when nscd is not running: $ icedove -g -d gdb /usr/lib/icedove/run-mozilla.sh -g -d gdb /usr/lib/icedove/icedove-bin MOZILLA_FIVE_HOME=/usr/lib/icedove LD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove/plugins:/usr/lib/icedove DISPLAY=:0 DYLD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove LIBRARY_PATH= SHLIB_PATH=/usr/lib/icedove:/usr/lib/icedove LIBPATH=/usr/lib/icedove:/usr/lib/icedove ADDON_PATH= MOZ_PROGRAM=/usr/lib/icedove/icedove-bin MOZ_TOOLKIT= moz_debug=1 moz_debugger=gdb moz_debugger_args= /usr/bin/gdb --args /usr/lib/icedove/icedove-bin GNU gdb (GDB) 7.4-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from /usr/lib/debug/usr/lib/icedove/icedove-bin...done. done. (gdb) run Starting program: /usr/lib/icedove/icedove-bin [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. strtok_r () at ../sysdeps/x86_64/strtok.S:190 190 ../sysdeps/x86_64/strtok.S: Aucun fichier ou dossier de ce type. (gdb) bt #0 strtok_r () at ../sysdeps/x86_64/strtok.S:190 #1 0x72ba7dec in ldap_str2charray (str=optimized out, brkstr=0x7fffeab7884e , ) at charray.c:218 #2 0x7fffeab623a6 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #3 0x7fffeab63c3f in ldap_int_initialize_global_options () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #4 0x7fffeab63dbd in ldap_int_initialize () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x7fffeab49819 in ldap_create () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x7fffeab49d9a in ldap_initialize () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7fffead8d2c1 in ?? () from /lib/libnss_ldap.so.2 #8 0x7fffead8e43c in ?? () from /lib/libnss_ldap.so.2 #9 0x7fffead8e8ad in ?? () from /lib/libnss_ldap.so.2 #10 0x7fffead8ef77 in _nss_ldap_getpwnam_r () from /lib/libnss_ldap.so.2 #11 0x773d787d in __getpwnam_r (name=0x7fffed83 glondu, resbuf=0x7fffc7c0, buffer=0x76d75800 ocsigen, buflen=1024, result=optimized out) at ../nss/getXXbyYY_r.c:256 #12 0x70514853 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x705153bd in g_get_home_dir () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fffef74d257 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #15 0x7fffef75165f in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #16 0x7fffef7023a5 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #17 0x704f4a60 in g_option_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fffef7028a0 in gtk_parse_args () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #19 0x754f537c in XRE_main (argc=optimized out, argv=optimized out, aAppData=optimized out) at /build/icedove-O32QkX/icedove-10.0.3/mozilla/toolkit/xre/nsAppRunner.cpp:3051 #20 0x00401ef7 in do_main (argv=0x7fffe338, argc=1, exePath=0x7fffd228 /usr/lib/icedove/libxpcom.so) at nsMailApp.cpp:143 #21 main (argc=1, argv=0x7fffe338) at nsMailApp.cpp:226 Icedove works properly when nscd is running. The bug might be in libnss-ldap, but Icedove is the only program I've seen segfaulting in this situation, so I'll let someone more knowlegdeable decide so. Cheers, -- Stéphane -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.3 ii fontconfig2.8.0-3.1 ii libasound21.0.25-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-30 ii libcairo2 1.10.2-7 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libevent-2.0-52.0.18-stable-1 ii libffi5 3.0.10-3 ii libfontconfig12.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-3 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0
Bug#664747: progress on package ?
Ok pushed it to debian: http://ftp-master.debian.org/new/jpylyzer_1.5.0-1.html See full debian/ at: http://anonscm.debian.org/viewvc/python-modules/packages/jpylyzer/trunk/ Pay attention to the way I repackaged everything for debian. pymakespec is not available in debian as far as I know. Let me know what you think of the package. I did restrict it to python 2.7, since it fails to install on python 2.6 2cts On Wed, May 2, 2012 at 11:12 PM, David Tarrant dave...@ecs.soton.ac.uk wrote: I take it you found version 1.5.0 from https://github.com/openplanets/jpylyzer (under tags) This is a fairly recent release, so has been worked on by Johan. As the initial packager I am happy to take advice on what would make the process of gaining a mentor easier. Cheers Dave T On 2 May 2012, at 21:46, Mathieu Malaterre ma...@debian.org wrote: I cannot see any progress on this package. Is this still something you are working on ? Otherwise here is my current status: http://anonscm.debian.org/viewvc/python-modules/packages/jpylyzer/trunk/ It seems to be working nicely. Let me know what you think. Thanks, -M -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664747: progress on package ?
You can also dget it from here: http://mentors.debian.net/package/jpylyzer On Thu, May 3, 2012 at 10:04 AM, Mathieu Malaterre ma...@debian.org wrote: Ok pushed it to debian: http://ftp-master.debian.org/new/jpylyzer_1.5.0-1.html See full debian/ at: http://anonscm.debian.org/viewvc/python-modules/packages/jpylyzer/trunk/ Pay attention to the way I repackaged everything for debian. pymakespec is not available in debian as far as I know. Let me know what you think of the package. I did restrict it to python 2.7, since it fails to install on python 2.6 2cts On Wed, May 2, 2012 at 11:12 PM, David Tarrant dave...@ecs.soton.ac.uk wrote: I take it you found version 1.5.0 from https://github.com/openplanets/jpylyzer (under tags) This is a fairly recent release, so has been worked on by Johan. As the initial packager I am happy to take advice on what would make the process of gaining a mentor easier. Cheers Dave T On 2 May 2012, at 21:46, Mathieu Malaterre ma...@debian.org wrote: I cannot see any progress on this package. Is this still something you are working on ? Otherwise here is my current status: http://anonscm.debian.org/viewvc/python-modules/packages/jpylyzer/trunk/ It seems to be working nicely. Let me know what you think. Thanks, -M -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671304: pulseaudio: please downgrade pulseaudio-esound-compat to Suggests
Package: pulseaudio Version: 1.1-3+b1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The pulseaudio daemon Recommends pulseaudio-esound-compat, even though very few applications in the archive use libesd0 anymore. Practically everything was migrated to Gstreamer. I therefore propose that pulseaudio-esound-compat be demoted to Suggests and that libesd0 Depends on pulseaudio-esound-compat | esound. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-2-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu1 ii consolekit 0.4.5-3 ii libasound2 1.0.25-2 ii libasound2-plugins 1.0.25-1 ii libc6 2.13-30 ii libcap2 1:2.22-1 ii libdbus-1-3 1.5.12-1 ii libfftw3-3 3.3-1 ii libice6 2:1.0.8-2 ii libltdl72.4.2-1 ii liborc-0.4-01:0.4.16-1 ii libpulse0 1.1-3+b1 ii libsamplerate0 0.1.8-4 ii libsm6 2:1.2.1-2 ii libsndfile1 1.0.25-4 ii libspeexdsp11.2~rc1-3 ii libtdb1 1.2.9+git20120207-2 ii libudev0175-3.1 ii libx11-62:1.4.4-4 ii libx11-xcb1 2:1.4.4-4 ii libxcb1 1.8.1-1 ii libxtst62:1.2.0-4 ii lsb-base4.1+Debian0 ii udev175-3.1 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.31-2 ii pulseaudio-esound-compat 1.1-3+b1 ii pulseaudio-module-x11 1.1-3+b1 ii rtkit 0.10-2 Versions of packages pulseaudio suggests: ii paman none ii paprefs none ii pavucontrol none ii pavumeter none ii pulseaudio-utils 1.1-3+b1 - -- Configuration Files: /etc/default/pulseaudio changed [not included] /etc/pulse/daemon.conf changed [not included] /etc/pulse/system.pa changed [not included] - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPokELAAoJEK4fgnfEtNe2LOcP/2s1aj4TiAn1/fkRJdl/Noug yVQe6zV8OosNx9pXaZ8KHknvqNrtft2weXuKvPry83+8cW9PbIHtBcavDZgigNEG psOEfEPRbroQkgvCULb9kedurCQJd9ln3ZEJNVnsCGFuf4rpboXlTCrdEZqrcgDO VmrHaO1RWZNsuvHkXF4lbXB/StAXqtjWSTYqHF0VkeOs+QmtT9xCRvEjZEpTYz+Y 9fos6lMJrm+gNYHsKHFLbxR5sSfpgqewyb9ETWNMOtV0icTjcvpTTfIxSCpsIPxd RrlM4SfzObH4KaqK24hme9mk6yMJgtGr8/n++3eT6MbIHbUPLvcU/AGm2ySvSKY+ TkKxQr/6fKGKSlLNtRJ1gB45YX5gueDk9CdZBOJIYC8c/HScqlT0oxsdE0xxBC0p 80KcQgNb6qsKwhhecppdKC6NiNIA4UE5wqa+gsjf7BRlJIXfZWH9gJ1o2zZLEiI2 5RNLseEhP297XQ8TL6+deSMKfY7C+0z2Jv0hZpNl0MW6zCWnJQorf9C+EeEcZ/B8 s9IKvVLc2v75nVxLziaSkgFFGsbu825CPOmWwOIv+Ljjdx4meo0GTgK7Emov+qKJ ZGUpjMFR8vIjQPX0vm6u/4d4hG/qrJGTF4sSLR9logaezoAKxjv8WqM1psi8AzAP xB/3qf9AvzR7FWgffMgs =1jSs -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#640381: [Pkg-xen-devel] Bug#640381: error xenstore-read: couldn't read path backend/vbd/6/768/node
On Wed, 2012-05-02 at 19:38 -0700, Kitara Lagony wrote: tail /var/log/xen/xen-hotplug.log xenstore-read: couldn't read path backend/vbd/6/768/node /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected I expect this is fixed by xen-unstable 22499:a5a0817d9210 and the followup fix in 22544:f0d26fdebf40. These are included in upstream 4.1 onwards. Ian. -- Ian Campbell Current Noise: Isis - False Light Sometimes when you look into his eyes you get the feeling that someone else is driving. -- David Letterman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671257: gettext: msgfmt output format prevents multiarch migration (fwd)
[ Adding Steve Langasek, multiarch architect in Debian, to Cc list ]. On Thu, 3 May 2012, Bruno Haible wrote: Hi Santiago, A long time ago, people working on embedded systems in Debian had the idea that it would be a good thing to have .mo files in the same endianness as the architecture on which they are used. However, the saving in cpu time was too small to justify the need to have native endianness everywhere. Well, the fact is that this change was made in gettext after all, and now msgfmt creates .mo files in native endianness I don't know where you got this history from. AFAIK, GNU 'msgfmt' always created .mo files in native endianness since the beginning (1995), up until 2005-08-26, when the option --endianness was introduced. Hmm, 2005-08-26? Are you sure of that? I remember well the bug by Neil Williams: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468209 where he asked --endianness to be documented, as he was thinking about using it in his embedded projects to override the current msgfmt default of always creating little endian .mo files. This was in 2008. At that time, msgfmt always created little endian .mo files. The response we gave to him was basically: You don't need this option, as .mo files are always little endian and gettext tools handle both forms just fine. Period. By we I mean the response I gave to him which later you mostly agreed as well: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468209#37 So, imagine my surprise when I started to receive requests from multiarch people so that msgfmt changes to be always little endian. Paul Martin writes: packages with localized strings fail the requirement of multiarch of all shared files being identical across architectures. Maybe the workaround is simply to exclude *.mo files from this requirement? Have you proposed this to the Debian people? I guess people in charge of multiarch would much prefer not to do any exceptions. In some way, they have declared the war to gratuitous differences in binary files, because, well, they are gratuitous! i.e. we would like msgfmt to create always little endian .mo files, as before. You can achieve this behaviour by setting the two environment variables MSGFMT=/usr/bin/msgfmt --endianness=little GMSGFMT=/usr/bin/msgfmt --endianness=little during the 'configure' run, and forcing an update of the .mo files through cd po ; make update-po after make has run. Yes, we could do that, in each and every package, but somehow we feel that's not the best way to solve this. I think it is not too difficult to integrate these two additions into Debian's build system (.spec files, templates, whatever)? Debian's build system is a lot more heterogeneous than that. Some people use debhelper, some people do not and write debian/rules in their own style. Some people use debhelper ultrasimplified dh format, some people do not. The opinion of people in charge of multiarch is that in the long run, it would be much better if msgfmt's default changed in gettext to be little endian again. [ Steve: I think this summarizes your feelings about this, feel free to add any thing I forgot or I didn't explain well to Bruno ]. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671305: dracut: cryptsetup just hangs, making the system unbootable
Package: dracut Version: 018+32+geb6e141-1 So, I had a bit of a bad experience yesterday evening. :-) I switched from initramfs-tools to dracut 18, because I like the idea of dracut, and I had successfully used dracut 17. But after reboot and entering a LUKS password, nothing happened. I rebooted and added [rd.luks=0 rd.shell] to the kernel command line. Trying to open any LUKS device manually showed the same behavior: it just hangs. No reaction to SIGINT. SIGQUIT gets rid of the cryptsetup process. At that point, a /dev/dm-? node has shown up, but doesn't work yet, and none of the symlinks are there. I reverted the machine to initramfs-tools for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671306: 'pinfo dash -' hangs: shows 1st screen, but keys don't work.
Package: pinfo
Version: 0.6.9-5.1
Severity: normal
Dear Maintainer,
I've been testing a local Bourne shell script that uses 'iselect' in a
'while' loop that calls 'pinfo'. When the script opens a file as a
command line argument, 'pinfo' works correctly. When the script inputs
from STDIN, 'pinfo' consistently hangs. (i.e. the first screen of data
is shown, but no pager keys work. 'Ctrl-C' to exit works.) The one line
of code that calls 'pinfo' remains the same, hang or no hang.
This code simulates the hang:
# close STDIN, run pinfo
% pinfo dash -
Maybe 'pinfo' requires an empty and open STDIN.
I used 'strace' and 'diff' to compare good and bad 'pinfo' runs. The
good run succeeds with this call:
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
...while the bad run fails with it, just before some sort of infinite
loop:
select(1, [0], NULL, NULL, {0, 0}) = 1 (in [0], left {0, 0})
'man select' describes a potential 'select' hang, or race condition, and
a related 'pselect' fix:
% man select | grep -A 7 reason that pselect
The reason that pselect() is needed is that if one wants to wait for either
a
signal or for a file descriptor to become ready, then an atomic test is
needed
to prevent race conditions. (Suppose the signal handler sets a global
flag
and returns. Then a test of this global flag followed by a call of
select()
could hang indefinitely if the signal arrived just after the test but
just
before the call. By contrast, pselect() allows one to first block
signals,
handle the signals that have come in, then call pselect() with the
desired
sigmask, avoiding the race.)
Other pagers don't fail this way: 'man dash -' works fine.
HTH...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages pinfo depends on:
ii install-info 4.13a.dfsg.1-10
ii libc6 2.13-31
ii libncursesw5 5.9-7
ii libreadline6 6.2-8
ii libtinfo5 5.9-7
pinfo recommends no packages.
Versions of packages pinfo suggests:
ii balsa [mail-reader] 2.4.11-1
ii bsd-mailx [mail-reader] 8.1.2-0.2006cvs-1
ii claws-mail [mail-reader]3.8.0-1
ii cups-bsd [lpr] 1.5.2-10
ii dillo [www-browser] 3.0.2-2
ii elinks [www-browser]0.12~pre5-7
ii galeon [www-browser]2.0.7-2.1+b1
ii iceape [www-browser]2.7.4-1
ii iceweasel [www-browser] 10.0.4esr-2
ii konqueror [www-browser] 4:4.7.4-2
ii links [www-browser] 2.6-1
ii lynx-cur [www-browser] 2.8.8dev.12-2
ii nmh [mail-reader] 1.3-1+b1
ii opera-static [www-browser] 7.23-20031119.1
ii sylpheed [mail-reader] 3.2.0~beta7-1
-- 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#671307: pppconfig: [INTL:ja] updated Japanese debconf translation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: pppconfig Version: 2.3.18+nmu3 Severity: wishlist Tags: l10n patch Hi, I updated Japanese translation of debconf messages (ja.po). Please apply this. Thanks, - -- Kenshi Muto km...@debian.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.9 http://mailcrypt.sourceforge.net/ iQIcBAEBCgAGBQJPok4BAAoJEB0hyD3EUuD8kq4P/1o3Tv6cNwNbrNAizcAIBUlr pAPfc2vOi+Vkm0Pn0w4rZ+mLaCoKFSLsPK9V6MxHk7NJJThtaw8uKavhiXbcb9aA cgOPl2Epi2d7XsQSpiiuYrjeWV8EZr0d45KnW6tT6mJvhhApl2QdMDlTLHGSxIeR c1T73kG8bKKT7V3WdWx80jVRw0h1IzIRNXg1k42nKOAmQUBP32e40h3iZE0Ko0lO KO+CphEwVc17Tyl0CHLhI0Yv5EY8T5392LRmPvsI7DtGVjgjkzKV4q3u5Sqhclq6 j+2IcgGNgM4xZZ7ateNEjqwSpqbFujp/5mf7Q39EkHSeoXqaTc7LWILM0MjJDRxi LfD2aLINlIPkDITJYmW6HV2d3sFYhGjvBzGqGaTF5GeyNzUCRT6Ilgxn0CGxSdVR t/8BfeACVYv8j+VxqlxWGbEzhYyCH5pDyqadqwDsUgWhfhtjriWP5xiuu+VNssAF m0UtbR00P3yF8Enmy65TVyE8CBN10UOFwoGWkrSRV+8qUGti2hWJUkZdbhdOznUi Ezd/Maz6wYSDbEQVu2B+JtFSqKX1R+ao7HxLnDXq8FWvlGtS8i41L0mZSa+licoW cRkB5+OChLZGwbQpWNg2xpD9KsyUAEfmOaAnWiAWcYrV5JuHJP/e9HtLhZyJrAmF m3fiOYC9IwoEpVh64znD =vUcg -END PGP SIGNATURE- ja.po Description: Binary data
Bug#671309: xserver-xorg-core: 2:1.12.1-1 in unstable (low) dependency problem, doesn't allow xserver-xorg-video-all to install
Package: xserver-xorg-core Version: 2:1.12.1-1 Severity: important Dear Maintainer, * What led up to the situation? Did a fresh install of Debian for my desktop computer. Tried to install desktop with: apt-get install task-desktop Dependency problems arose with xserver-xorg-video-all that did not allow the package to install. [task-desktop] depends on [xserver-xorg-video-all] [xserver-xorg-video-all] depends on [xserver-xorg-core] [xserver-xorg-video-all] depends on [xserver-xorg-video-s3virge] AND [xserver- xorg-video-tdfx] [xserver-xorg-video-s3virge] AND [xserver-xorg-video-tdfx] depends on [xorg- video-abi-11] (which is a virtual package) [xserver-xorg-core] provided virtual package before, but not anymore, instead provides [xorg-video-abi-12] but no [xorg-video-abi-11] Due to this dependency problem [task-desktop] will not install. xserver-xorg-core: 2:1.12.1-1 in unstable (low) is a relatively new package introduced to unstable on May 1, 2012 according to http://packages.qa.debian.org/x/xorg-server.html * What exactly did you do (or not do) that was effective (or ineffective)? I ran tasksel and chose debian desktop choice, rebooted. No GUI display manager was installed. Installed gdm3 and rebooted into gnome-shell and graphical desktop. * What outcome did you expect instead? I expected task-desktop to install, but failed with dependency problems. Tasksel installed a majority of the system but failed to install gdm3 or graphical user interface. Thank you kindly. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 3 01:29 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2072872 Apr 30 18:12 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV350 AS [Radeon 9550] [1002:4153] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-2-686-pae (Debian 3.2.16-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-4) ) #1 SMP Mon Apr 30 05:59:35 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 42171 May 3 01:34 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [16.441] X.Org X Server 1.12.1 Release Date: 2012-04-13 [16.441] X Protocol Version 11, Revision 0 [16.441] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian [16.441] Current Operating System: Linux dhpcd530 3.2.0-2-686-pae #1 SMP Mon Apr 30 05:59:35 UTC 2012 i686 [16.441] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=ff479cf4-146c-40ca-aa61-0ba181d0dfd2 ro quiet [16.441] Build Date: 01 May 2012 01:04:39AM [16.441] xorg-server 2:1.12.1-1 (Cyril Brulebois k...@debian.org) [16.441] Current version of pixman: 0.24.4 [16.441]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [16.441] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [16.442] (==) Log file: /var/log/Xorg.0.log, Time: Thu May 3 01:33:43 2012 [16.466] (==) Using system config directory /usr/share/X11/xorg.conf.d [16.494] (==) No Layout section. Using the first Screen section. [16.494] (==) No screen section available. Using defaults. [16.494] (**) |--Screen Default Screen Section (0) [16.494] (**) | |--Monitor default monitor [16.504] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [16.504] (==) Automatically adding devices [16.504] (==) Automatically enabling devices [16.518] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [16.518]Entry deleted from font path. [16.518] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [16.518]Entry deleted from font path. [16.518] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [16.518]Entry deleted from font path. [16.518] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [16.518]Entry deleted from font path. [16.518] (WW) The directory /usr/share/fonts/X11/75dpi does not exist. [16.518]Entry deleted from font path. [16.518] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [16.518]Entry deleted from font path. [16.518] (==) FontPath set to:
Bug#671310: Missing space in package description
Package: liblcms-utils Version: 1.19.dfsg-1 Severity: minor Hello! You miss a space in the last sentence of this package description between utilities and (jpegicc. While changing the description you could put the last sentence in a new paragraph, which would help reducing the translation work (overlapping decsription with liblcms1). Thanks Erik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671311: cheetah: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: cheetah Version: 2.4.4-2 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild cheetah FTBFS if built twice in a row: | dpkg-source -b cheetah-2.4.4 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building cheetah using existing ./cheetah_2.4.4.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | cheetah-2.4.4/Cheetah.egg-info/PKG-INFO | cheetah-2.4.4/Cheetah.egg-info/SOURCES.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/cheetah_2.4.4-2.diff.3ZAKZj | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b cheetah-2.4.4 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671312: configobj: FTBFS if built twice in a row: unrepresentable changes to source
Source: configobj Version: 4.7.2+ds-3 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild configobj FTBFS if built twice in a row: | dpkg-source -b configobj-4.7.2+ds | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building configobj using existing ./configobj_4.7.2+ds.orig.tar.gz | dpkg-source: warning: file configobj-4.7.2+ds/configobj.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: error: cannot represent change to configobj-4.7.2+ds/api/crarr.png: binary file contents changed | dpkg-source: error: add api/crarr.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b configobj-4.7.2+ds gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671313: django-picklefield: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: django-picklefield Version: 0.2.1-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild django-picklefield FTBFS if built twice in a row: | dpkg-source -b django-picklefield-0.2.1 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building django-picklefield using existing ./django-picklefield_0.2.1.orig.tar.gz | dpkg-source: warning: ignoring deletion of file src/django_picklefield.egg-info/SOURCES.txt | dpkg-source: info: local changes detected, the modified files are: | django-picklefield-0.2.1/src/django_picklefield.egg-info/PKG-INFO | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/django-picklefield_0.2.1-1.diff.h6E7OR | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b django-picklefield-0.2.1 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671314: fookebox: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: fookebox Version: 0.6.0-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild fookebox FTBFS if built twice in a row: | dpkg-source -b fookebox-0.6.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building fookebox using existing ./fookebox_0.6.0.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | fookebox-0.6.0/fookebox.egg-info/PKG-INFO | fookebox-0.6.0/fookebox.egg-info/SOURCES.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/fookebox_0.6.0-1.diff.LKAQlY | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b fookebox-0.6.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671315: ipython: FTBFS if built twice in a row: unrepresentable changes to source
Source: ipython Version: 0.12-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild ipython FTBFS if built twice in a row: | dpkg-source -b ipython-0.12 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building ipython using existing ./ipython_0.12.orig.tar.gz | dpkg-source: warning: newly created empty file 'build/lib/IPython/zmq/pylab/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/zmq/tests/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/quarantine/ipy_server.py has no final newline (either original or modified version) | dpkg-source: warning: file ipython-0.12/build/lib/IPython/quarantine/ipy_fsops.py has no final newline (either original or modified version) | dpkg-source: warning: file ipython-0.12/build/lib/IPython/quarantine/ledit.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/quarantine/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/quarantine/ipy_editors.py has no final newline (either original or modified version) | dpkg-source: warning: file ipython-0.12/build/lib/IPython/quarantine/ipy_synchronize_with.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/quarantine/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/lib/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/extensions/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/testing/plugin/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/parallel/apps/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/parallel/controller/sqlitedb.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/parallel/controller/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/parallel/client/asyncresult.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/parallel/client/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/parallel/scripts/__init__.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/parallel/engine/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/parallel/tests/clienttest.py has no final newline (either original or modified version) | dpkg-source: warning: file ipython-0.12/build/lib/IPython/parallel/tests/test_newserialized.py has no final newline (either original or modified version) | dpkg-source: warning: file ipython-0.12/build/lib/IPython/utils/cursesimport.py has no final newline (either original or modified version) | dpkg-source: warning: file ipython-0.12/build/lib/IPython/utils/codeutil.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/utils/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/utils/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/nbformat/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/nbformat/v1/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/nbformat/v2/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/nbformat/tests/__init__.py' will not be represented in diff | dpkg-source: warning: file ipython-0.12/build/lib/IPython/config/__init__.py has no final newline (either original or modified version) | dpkg-source: warning: newly created empty file 'build/lib/IPython/config/profile/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/config/tests/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/external/ssh/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file 'build/lib/IPython/scripts/__init__.py' will not be represented in diff | dpkg-source: warning: newly created empty file
Bug#671316: kupfer: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: kupfer Version: 0+v207-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild kupfer FTBFS if built twice in a row: | dpkg-source -b kupfer-0+v207 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building kupfer using existing ./kupfer_0+v207.orig.tar.xz | dpkg-source: warning: file kupfer-0+v207/po/.intlcache has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | kupfer-0+v207/.lock-waf_linux2_build | kupfer-0+v207/Documentation/Contributing.html | kupfer-0+v207/Documentation/Copyright.html | kupfer-0+v207/Documentation/GTKTheming.html | kupfer-0+v207/Documentation/Localization.html | kupfer-0+v207/Documentation/Manpage.html | kupfer-0+v207/Documentation/Manual.html | kupfer-0+v207/Documentation/PluginAPI.html | kupfer-0+v207/Documentation/VersionHistory.html | kupfer-0+v207/po/.intlcache | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/kupfer_0+v207-1.diff.r4pqip | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b kupfer-0+v207 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671317: lazygal: FTBFS if built twice in a row: unrepresentable changes to source
Source: lazygal Version: 0.7.1-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild lazygal FTBFS if built twice in a row: | dpkg-source -b lazygal-0.7.1 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building lazygal using existing ./lazygal_0.7.1.orig.tar.gz | dpkg-source: error: cannot represent change to lazygal-0.7.1/build/mo/da_DK/LC_MESSAGES/lazygal.mo: binary file contents changed | dpkg-source: error: add build/mo/da_DK/LC_MESSAGES/lazygal.mo in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to lazygal-0.7.1/build/mo/cs_CZ/LC_MESSAGES/lazygal.mo: binary file contents changed | dpkg-source: error: add build/mo/cs_CZ/LC_MESSAGES/lazygal.mo in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to lazygal-0.7.1/build/mo/it_IT/LC_MESSAGES/lazygal.mo: binary file contents changed | dpkg-source: error: add build/mo/it_IT/LC_MESSAGES/lazygal.mo in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to lazygal-0.7.1/build/mo/fr_FR/LC_MESSAGES/lazygal.mo: binary file contents changed | dpkg-source: error: add build/mo/fr_FR/LC_MESSAGES/lazygal.mo in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b lazygal-0.7.1 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671318: pastescript: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: pastescript Version: 1.7.5-1.1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild pastescript FTBFS if built twice in a row: | dpkg-source -b pastescript-1.7.5 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building pastescript using existing ./pastescript_1.7.5.orig.tar.gz | dpkg-source: warning: ignoring deletion of file PasteScript.egg-info/PKG-INFO | dpkg-source: info: local changes detected, the modified files are: | pastescript-1.7.5/PasteScript.egg-info/SOURCES.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pastescript_1.7.5-1.1.diff.dMXXqI | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b pastescript-1.7.5 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570069: [gud...@gudjon.org: Re: [comedi] libcomedi0 removed from debian testing]
Hi, I've just tried to build a new debian package for libcomedi based on the latest git package Gudjon has provided. It fails trying to patch the comedi-calibrate. It cannot find the ./configure script (though it's there). Here's everything: the original package and my attempt to create a new version. http://www.linux-usb-daq.co.uk/tmp/comedilib.tar.gz Anyway. I've corrected the ./configure call in rules using the new options we have added during the last couple of days. Also played a bit with the build dependencies (removed ruby there, added dblatex, ...). /Bernd Yaroslav Halchenko wrote: Thank you Christoph for the note -- original announcement I guess have slipped through my mailbox without notice ;) Gudjon, I would be glad (whenever time allows) to sponsor the upload to Debian. I will look into current package you have -- only 1 major issue I see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570069 if it is usable on kfreebsd then udev depends should be said [!kfreebsd-amd64] or smth like that OR may be moved into Recommends altogether, OR just do not build for kfreebsd if it is of no use there -- I am just ignorant on this subject. Any input is welcome to help resolving this. GIT version -- would be neat (whenever current one gets back into testing)! On Thu, 05 Apr 2012, Christoph Schmidt-Hieber wrote: Hi Yaro, maybe NeuroDebian can come to the rescue here? Comedi is an incredibly important package, and it would be a shame to see it vanish from the debian repositories. Cheers, Christoph - Forwarded message from Gudjon I. Gudjonsson gud...@gudjon.org - Date: Thu, 5 Apr 2012 14:12:58 +0100 From: Gudjon I. Gudjonsson gud...@gudjon.org To: comedi_l...@googlegroups.com comedi_l...@googlegroups.com Subject: Re: [comedi] libcomedi0 removed from debian testing user-agent: KMail/1.13.7 (Linux/3.1.0-1-686-pae; KDE/4.6.5; i686; ; ) Hi list There is a newer version on my private server (0.8.1-6) deb-src http://213.64.124.152/debian/ source/ but I haven't had time to test it properly. My plan was to upload version 0.8.1-6 wich includes symbols file and then make a package with the current git version. My problem is lack of time and that I am not a Debian Maintainer. If someone wants to take over the maintenance, please do. If somebody is willing to sponsor uploads for me, I am willing to keep on maintaining it but I have been busy lately and will be for 10 more days. Cheers Gudjon On Thursday 05 April 2012 14:52:53 Bernd Porr wrote: Seems so that it needs a new maintainer. I vaguely remember that somebody here wanted to volunteer and that I offered testing the package. Anybody? /Bernd Daniele Nicolodi wrote: On 05/04/12 14:16, Bernd Porr wrote: Hi all, does anybody know why libcomedi0 has been removed from debian testing? It looks like this RC bug is the reason: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570069 This bug is more than two years old, and the comedilib Debian package has not seen any activity since 2008, except a NMU in 2011... http://packages.qa.debian.org/c/comedilib.html Cheers, -- www:http://www.linux-usb-daq.co.uk/ http://www.berndporr.me.uk/ http://www.imdb.com/name/nm3293421/ Mobile: +44 (0)7840 340069 Work: +44 (0)141 330 5237 University of Glasgow School of Engineering 72 Oakfield Avenue (Rankine Building for deliveries) Glasgow, G12 8LT -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625832: python-mpi4py: importing MPI fails
I cannot reproduce this with the version in stable, nor with the unstable version built on stable or in an unstable chroot. I am downgrading this bug and mark it unreproducible for now. How did you compile the above program, what architecture was this on and was it on an update unstable system? Can you try again with an updated unstable system? It seems to work on an up-to-date unstable now. And I am pretty sure it has been working for quite a long time for that matter: I do not recall the whole issue any longer, so it cannot have plagued me for a long time. As it is almost a year since I reported the bug, I cannot recall the exact specs of the system any longer: I can guess from the bug report which computer it was, but not the package versions apart from those present in the report, which are missing some thanks to my reporting it against the wrong package originally. But, as I see no changes to any of the openmpi packages since April 2011, it is hard to see why anything would have changed. From my point of view just mark this solved at the next upload. -Juha signature.asc Description: This is a digitally signed message part.
Bug#651384: httpfs2: does not work with nginx web server [patch]
Following patch addresses issue with httpfs2 and nginx web server.
Please review and apply.
diff httpfs2.c httpfs2.c.new
111c111
static void destroy_url_copy(void *);
---
// static void destroy_url_copy(void *);
405,424c405,424
static int free_url(struct_url* url)
{
if(url-host) free(url-host);
url-host = 0;
if(url-path) free(url-path);
url-path = 0;
if(url-name) free(url-name);
url-name = 0;
#ifdef USE_AUTH
if(url-auth) free(url-auth);
url-auth = 0;
#endif
if(url-sock_type != SOCK_CLOSED)
close_client_force(url);
url-port = 0;
url-proto = 0; /* only after socket closed */
url-file_size=0;
url-last_modified=0;
return 0;
}
---
// static int free_url(struct_url* url)
// {
// if(url-host) free(url-host);
// url-host = 0;
// if(url-path) free(url-path);
// url-path = 0;
// if(url-name) free(url-name);
// url-name = 0;
// #ifdef USE_AUTH
// if(url-auth) free(url-auth);
// url-auth = 0;
// #endif
// if(url-sock_type != SOCK_CLOSED)
// close_client_force(url);
// url-port = 0;
// url-proto = 0; /* only after socket closed */
// url-file_size=0;
// url-last_modified=0;
// return 0;
// }
623a624
629c630
---
632,633c633
{
---
{
649a650
906a908,909
#include string.h
926,934d928
static ssize_t
parse_header(struct_url *url, const char * buf, ssize_t bytes,
const char * method, size_t * content_length, int expect)
{
/* FIXME check the header parser */
int status;
const char * ptr = buf;
const char * end;
int seen_accept = 0, seen_length = 0, seen_close = 0;
936,938c930,931
if (bytes = 0) {
return -1;
}
---
#define HTTP_STATUS HTTP/1.1
#define ERROR -1
940,945c933,934
end = memchr(ptr, '\n', bytes);
if(!end) {
plain_report ( reply does not contain newline!, method, buf, 0);
errno = EIO;
return -1;
}
---
static int check_end_of_header_and_get_len(const char * ptr, int bytes) {
const char * end;
950,953c939
plain_report (reply does not contain end of header!,
method, buf, bytes);
errno = EIO;
return -1;
---
return ERROR;
957a944,945
return header_len;
}
959,974c947,952
end = memchr(ptr, '\n', bytes);
char * http = HTTP/1.1 ;
if(!mempref(ptr, http, end - ptr) || !isdigit( *(ptr + strlen(http))) ) {
plain_report (reply does not contain status!,
method, buf, header_len);
errno = EIO;
return -1;
}
status = strtol( ptr + strlen(http), (char **)ptr, 10);
if (status != expect) {
fprintf(stderr, %s: %s: failed with status: %d%.*s.\n,
argv0, method, status, (end - ptr) - 1, ptr);
if (!strcmp(HEAD, method)) fwrite(buf, bytes, 1, stderr); /*DEBUG*/
errno = EIO;
if (status == 404) errno = ENOENT;
return -1;
---
static int check_exists_http_status(const char * ptr, int bytes) {
char * end = memchr(ptr, '\n', bytes);
if(!mempref(ptr, HTTP_STATUS, end - ptr) || !isdigit( *(ptr +
strlen(HTTP_STATUS))) ) {
return ERROR;
975a954,955
return 1;
}
977c957,962
char * content_length_str = Content-Length: ;
---
static int parse_http_status(const char * ptr) {
int status = strtol( ptr + strlen(HTTP_STATUS), (char **)ptr, 10);
return status;
}
static int check_http_accept_header(const char* buf, int bytes, int
header_len) {
979,983c964,990
char * date = Last-Modified: ;
char * close = Connection: close;
struct tm tm;
while(1)
{
---
const char * ptr = buf;
char * end = memchr(ptr, '\n', bytes);
int seen_accept;
while(1)
{
ptr = end+1;
if( !(ptr buf + (header_len - 4))){
if(! seen_accept){
return ERROR;
}
return header_len;
}
end = memchr(ptr, '\n', bytes - (ptr - buf));
if( mempref(ptr, accept, strlen(accept))) {
seen_accept = 1;
continue;
}
}
}
static int check_http_content_len_header(const char* buf, int bytes, int
header_len, size_t * content_length) {
char * content_length_str = Content-Length: ;
const char * ptr = buf;
int seen_length = 0;
char * end = memchr(ptr, '\n', bytes);
while(1)
{
986,991d992
if(! seen_accept){
plain_report(server must Accept-Range: bytes,
method, buf, 0);
errno = EIO;
return -1;
}
993,996c994
plain_report(reply didn't contain Content-Length!,
method, buf, 0);
errno = EIO;
return -1;
---
return ERROR;
998,1001d995
Bug#669171: git-buildpackage: Create changelog if it does not exist
Guido Günther a...@sigxcpu.org writes:
Hi Daniel,
thanks for your patch. Some more comments below:
I inline an updated version with some tests.
I still have one trouble, when no previous changelog was in the
repository, dch.py raise GbpError, Version %s not found %
cp['Version'] from line 448.
It's triggered by test_create_from_dch_main and
test_create_from_dch_main_with_auto.
The version info is irrelevant in that case:
- We may still need to figure out if the changelog was just created?
- We may look for last modification under the debian/ directory?
- We may set since to the fist commit?
- We may set since to the last merged upstream version?
Regards.
From db8138f40e2e79ffd05c59bc2dc6c47360014515 Mon Sep 17 00:00:00 2001
From: Daniel Dehennin daniel.dehen...@baby-gnu.org
Date: Thu, 3 May 2012 08:32:20 +0200
Subject: [PATCH] Create debian/changelog if it does not exist.
* tests/11_test_changelog_create.py: Test several senarios of
debian/changelog creation.
* gbp/deb/changelog.py: Import scripts from gbp instead of dch to avoid
include errors.
(create): New class method to create debian/changelog with version from
git-dch option -N or upstream tag.
* gbp/scripts/dch.py (guess_version_from_upstream): cp is None when
called by ChangeLog.create().
(main): Create a new changelog if it does not exist.
---
gbp/deb/changelog.py | 36
gbp/scripts/dch.py|8 +++-
tests/11_test_changelog_create.py | 86 +
3 files changed, 129 insertions(+), 1 deletion(-)
create mode 100644 tests/11_test_changelog_create.py
diff --git a/gbp/deb/changelog.py b/gbp/deb/changelog.py
index b8c10b8..a410e86 100644
--- a/gbp/deb/changelog.py
+++ b/gbp/deb/changelog.py
@@ -19,6 +19,7 @@
import email
import os
import subprocess
+from gbp import scripts
class NoChangeLogError(Exception):
No changelog found
@@ -148,3 +149,38 @@ class ChangeLog(object):
return self._cp['Date']
+@classmethod
+def create(klass, repo=None, package=None, version=None, upstream_tag_format=None):
+
+Create an empty debian/changelog
+
+@param repo: git repository object
+@type repo: L{GitRepository}
+@param package: name of the package, get it from debian/control if None
+@type package: C{str}
+@param upstream_tag_format: format of the upstream tag
+@type upstream_tag_format: C{str}
+@return: changelog object
+@rtype: L{ChangeLog}
+
+
+if package == None and os.path.isfile(debian/control):
+try:
+control = open(debian/control, r)
+for line in control:
+if line.startswith(Source: ):
+package = line.split()[1]
+break
+except Exception, e:
+raise NoChangeLogError, Error parsing debian/control: %s % e
+
+if version == None:
+version = scripts.dch.guess_version_from_upstream(repo, upstream_tag_format, None)
+if version == None:
+raise NoChangeLogError, No suitable version found
+
+scripts.dch.spawn_dch(msg=[debian/changelog: generated by git-dch.],
+ newversion=True, version={'version':version},
+ dch_options=--create --package %s % package)
+
+return klass(filename=debian/changelog)
diff --git a/gbp/scripts/dch.py b/gbp/scripts/dch.py
index 14dff29..2a18f47 100644
--- a/gbp/scripts/dch.py
+++ b/gbp/scripts/dch.py
@@ -112,6 +112,8 @@ def guess_version_from_upstream(repo, upstream_tag_format, cp):
version = repo.tag_to_version(tag, upstream_tag_format)
if version:
gbp.log.debug(Found upstream version %s. % version)
+if cp == None:
+return %s-1 % version
if cp.has_epoch():
version = %s:%s % (cp.epoch, version)
if compare_versions(version, cp.version) 0:
@@ -423,7 +425,11 @@ def main(argv):
gbp.log.err(You are not on branch '%s' but on '%s' % (options.debian_branch, branch))
raise GbpError, Use --ignore-branch to ignore or --debian-branch to set the branch name.
-cp = ChangeLog(filename=changelog)
+try:
+cp = ChangeLog(filename=changelog)
+except NoChangeLogError, e:
+gbp.log.debug(No debian/changelog: create a new one)
+cp = ChangeLog.create(repo, version=options.new_version, upstream_tag_format=options.upstream_tag)
if options.since:
since = options.since
diff --git a/tests/11_test_changelog_create.py b/tests/11_test_changelog_create.py
new file mode 100644
index 000..51a8b04
--- /dev/null
+++ b/tests/11_test_changelog_create.py
@@ -0,0 +1,86 @@
+# vim: set fileencoding=utf-8 :
+
+Test L{Changelog}'s create
+
+import sys
+sys.path.insert(0, ..)
Bug#671158: gearmand: FTBFS[kfreebsd]: error: 'O_CLOEXEC' was not declared in this scope
Robert Millan r...@debian.org writes: 2012/5/2 Christoph Egger christ...@debian.org: CXX util/pidfile.o util/pidfile.cc: In member function 'bool datadifferential::util::Pidfile::create()': util/pidfile.cc:122:64: error: 'O_CLOEXEC' was not declared in this scope See #635192. But I don't think we can add O_CLOEXEC for Wheezy (see Aurelien's response in that bug). As workaround it can be defined to 0. Thanks, that was very helpful indeed. :) -- Stig Sandbeck Mathisen s...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671225: apt-file: remove unnecessary rapt-file dependencies
The reason why dpkg --print-architecture is better than dpkg-architecture -qDEB_HOST_ARCH is that dpkg is a standard part of a Debian system, while dpkg-dev brings huge dependencies. Other than that, they are functionally equivalent - they use the Dpkg::Arch Perl module to determine the architecture, but dpkg-architecture calls it at runtime, whereas in dpkg it's called in the configure script and the atchitecture is compiled in as a constant. Regards, ~~helix84 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671229: using Edit Color Map... on a Slice causes paraview to hang
Okay, some more observations: In my unstable chroot, Edit Color Map... actually gives the same error in other cases as well, but it works on another computer running testing (no chroot). So it might be something related to either the chroot part (or the Ubuntu X server part) or some other library used by paraview. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671319: pycha: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: pycha Version: 0.6.0-3 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild pycha FTBFS if built twice in a row: | dpkg-source -b pycha-0.6.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building pycha using existing ./pycha_0.6.0.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | pycha-0.6.0/pycha.egg-info/SOURCES.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pycha_0.6.0-3.diff.B7E_ST | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b pycha-0.6.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671321: pyfribidi: FTBFS if built twice in a row: unrepresentable changes to source
Source: pyfribidi Version: 0.11.0-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild pyfribidi FTBFS if built twice in a row: | dpkg-source -b pyfribidi-0.11.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building pyfribidi using existing ./pyfribidi_0.11.0.orig.tar.bz2 | dpkg-source: error: cannot represent change to pyfribidi-0.11.0/_pyfribidi_d.so: | dpkg-source: error: new version is symlink to /build/pyfribidi-NGtp9f/pyfribidi-0.11.0/build/lib.linux-i686-2.7-pydebug/_pyfribidi_d.so | dpkg-source: error: old version is nonexistent | dpkg-source: error: cannot represent change to pyfribidi-0.11.0/_pyfribidi.so: | dpkg-source: error: new version is symlink to /build/pyfribidi-NGtp9f/pyfribidi-0.11.0/build/lib.linux-i686-2.7/_pyfribidi.so | dpkg-source: error: old version is nonexistent | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b pyfribidi-0.11.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671322: pyscard: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: pyscard Version: 1.6.12-4 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild pyscard FTBFS if built twice in a row: | dpkg-source -b pyscard-1.6.12 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building pyscard using existing ./pyscard_1.6.12.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | pyscard-1.6.12/smartcard/scard/scard.py | pyscard-1.6.12/smartcard/scard/scard_wrap.c | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pyscard_1.6.12-4.diff.wR2P2X | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b pyscard-1.6.12 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671323: python-chaco: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-chaco Version: 4.1.0-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-chaco FTBFS if built twice in a row: | dpkg-source -b python-chaco-4.1.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-chaco using existing ./python-chaco_4.1.0.orig.tar.gz | dpkg-source: warning: file python-chaco-4.1.0/chaco.egg-info/requires.txt has no final newline (either original or modified version) | dpkg-source: warning: file python-chaco-4.1.0/chaco.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | python-chaco-4.1.0/chaco.egg-info/PKG-INFO | python-chaco-4.1.0/chaco.egg-info/SOURCES.txt | python-chaco-4.1.0/chaco.egg-info/dependency_links.txt | python-chaco-4.1.0/chaco.egg-info/not-zip-safe | python-chaco-4.1.0/chaco.egg-info/requires.txt | python-chaco-4.1.0/chaco.egg-info/top_level.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-chaco_4.1.0-1.diff.Ti5xOp | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-chaco-4.1.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671324: python-envisage: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-envisage Version: 4.1.0-2 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-envisage FTBFS if built twice in a row: | dpkg-source -b python-envisage-4.1.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-envisage using existing ./python-envisage_4.1.0.orig.tar.gz | dpkg-source: warning: file python-envisage-4.1.0/envisage.egg-info/requires.txt has no final newline (either original or modified version) | dpkg-source: warning: file python-envisage-4.1.0/envisage.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: warning: file python-envisage-4.1.0/envisage.egg-info/entry_points.txt has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | python-envisage-4.1.0/envisage.egg-info/PKG-INFO | python-envisage-4.1.0/envisage.egg-info/SOURCES.txt | python-envisage-4.1.0/envisage.egg-info/dependency_links.txt | python-envisage-4.1.0/envisage.egg-info/entry_points.txt | python-envisage-4.1.0/envisage.egg-info/not-zip-safe | python-envisage-4.1.0/envisage.egg-info/requires.txt | python-envisage-4.1.0/envisage.egg-info/top_level.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-envisage_4.1.0-2.diff.WlUkbz | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-envisage-4.1.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671325: python-envisagecore: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-envisagecore Version: 3.2.0-2 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-envisagecore FTBFS if built twice in a row: | dpkg-source -b python-envisagecore-3.2.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-envisagecore using existing ./python-envisagecore_3.2.0.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | python-envisagecore-3.2.0/EnvisageCore.egg-info/PKG-INFO | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-envisagecore_3.2.0-2.diff.9_wU2n | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-envisagecore-3.2.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671326: python-envisageplugins: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-envisageplugins Version: 3.2.0-2 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-envisageplugins FTBFS if built twice in a row: | dpkg-source -b python-envisageplugins-3.2.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-envisageplugins using existing ./python-envisageplugins_3.2.0.orig.tar.gz | dpkg-source: warning: file python-envisageplugins-3.2.0/EnvisagePlugins.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: warning: file python-envisageplugins-3.2.0/EnvisagePlugins.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | python-envisageplugins-3.2.0/EnvisagePlugins.egg-info/PKG-INFO | python-envisageplugins-3.2.0/EnvisagePlugins.egg-info/SOURCES.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-envisageplugins_3.2.0-2.diff.CwiNcO | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-envisageplugins-3.2.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671327: python-kajiki: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-kajiki Version: 0.3.4-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-kajiki FTBFS if built twice in a row: | dpkg-source -b python-kajiki-0.3.4 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-kajiki using existing ./python-kajiki_0.3.4.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | python-kajiki-0.3.4/Kajiki.egg-info/PKG-INFO | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-kajiki_0.3.4-1.diff.Ix64xo | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-kajiki-0.3.4 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671328: python-launchpadlib: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-launchpadlib Version: 1.9.12-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-launchpadlib FTBFS if built twice in a row: | dpkg-source -b python-launchpadlib-1.9.12 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-launchpadlib using existing ./python-launchpadlib_1.9.12.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | python-launchpadlib-1.9.12/src/launchpadlib.egg-info/PKG-INFO | python-launchpadlib-1.9.12/src/launchpadlib.egg-info/SOURCES.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-launchpadlib_1.9.12-1.diff.2F0vko | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-launchpadlib-1.9.12 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671329: python-repoze.tm2: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-repoze.tm2 Version: 1.0b2-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-repoze.tm2 FTBFS if built twice in a row: | dpkg-source -b python-repoze.tm2-1.0b2 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-repoze.tm2 using existing ./python-repoze.tm2_1.0b2.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | python-repoze.tm2-1.0b2/build/lib.linux-i686-2.7/repoze/__init__.py | python-repoze.tm2-1.0b2/build/lib.linux-i686-2.7/repoze/tm/__init__.py | python-repoze.tm2-1.0b2/build/lib.linux-i686-2.7/repoze/tm/tests.py | python-repoze.tm2-1.0b2/repoze.tm2.egg-info/PKG-INFO | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-repoze.tm2_1.0b2-1.diff.DDOQNa | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-repoze.tm2-1.0b2 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671330: python-txosc: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: python-txosc Version: 0.2.0-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-txosc FTBFS if built twice in a row: | dpkg-source -b python-txosc-0.2.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-txosc using existing ./python-txosc_0.2.0.orig.tar.gz | dpkg-source: warning: file python-txosc-0.2.0/txosc.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | python-txosc-0.2.0/osc-receive.1 | python-txosc-0.2.0/osc-send.1 | python-txosc-0.2.0/txosc.egg-info/PKG-INFO | python-txosc-0.2.0/txosc.egg-info/SOURCES.txt | python-txosc-0.2.0/txosc.egg-info/dependency_links.txt | python-txosc-0.2.0/txosc.egg-info/top_level.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-txosc_0.2.0-1.diff.pXzQ1b | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b python-txosc-0.2.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671331: soya: FTBFS if built twice in a row: unrepresentable changes to source
Source: soya Version: 0.15~rc1-7 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild soya FTBFS if built twice in a row: | dpkg-source -b soya-0.15~rc1 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building soya using existing ./soya_0.15~rc1.orig.tar.bz2 | dpkg-source: warning: ignoring deletion of file _soya.c | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.6-pydebug/opengl.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.6-pydebug/opengl.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.6-pydebug/chunk.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.6-pydebug/chunk.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.6-pydebug/matrix.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.6-pydebug/matrix.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.6-pydebug/_soya.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.6-pydebug/_soya.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.6-pydebug/sdlconst.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.6-pydebug/sdlconst.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/lib.linux-i686-2.6-pydebug/soya/opengl_d.so: binary file contents changed | dpkg-source: error: add build/lib.linux-i686-2.6-pydebug/soya/opengl_d.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/lib.linux-i686-2.6-pydebug/soya/_soya_d.so: binary file contents changed | dpkg-source: error: add build/lib.linux-i686-2.6-pydebug/soya/_soya_d.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/lib.linux-i686-2.6-pydebug/soya/sdlconst_d.so: binary file contents changed | dpkg-source: error: add build/lib.linux-i686-2.6-pydebug/soya/sdlconst_d.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/lib.linux-i686-2.7-pydebug/soya/opengl_d.so: binary file contents changed | dpkg-source: error: add build/lib.linux-i686-2.7-pydebug/soya/opengl_d.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/lib.linux-i686-2.7-pydebug/soya/_soya_d.so: binary file contents changed | dpkg-source: error: add build/lib.linux-i686-2.7-pydebug/soya/_soya_d.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/lib.linux-i686-2.7-pydebug/soya/sdlconst_d.so: binary file contents changed | dpkg-source: error: add build/lib.linux-i686-2.7-pydebug/soya/sdlconst_d.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.7-pydebug/opengl.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.7-pydebug/opengl.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.7-pydebug/chunk.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.7-pydebug/chunk.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.7-pydebug/matrix.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.7-pydebug/matrix.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to soya-0.15~rc1/build/temp.linux-i686-2.7-pydebug/_soya.o: binary file contents changed | dpkg-source: error: add build/temp.linux-i686-2.7-pydebug/_soya.o in debian/source/include-binaries if you want to
Bug#671332: tagpy: FTBFS if built twice in a row: unrepresentable changes to source
Source: tagpy Version: 0.94.8-3 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild tagpy FTBFS if built twice in a row: | dpkg-source -b tagpy-0.94.8 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building tagpy using existing ./tagpy_0.94.8.orig.tar.gz | dpkg-source: warning: file tagpy-0.94.8/setuptools.pth has no final newline (either original or modified version) | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.6/lib.linux-i686-2.6/_tagpy.so: binary file contents changed | dpkg-source: error: add build2.6/lib.linux-i686-2.6/_tagpy.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.6/temp.linux-i686-2.6/src/wrapper/id3.o: binary file contents changed | dpkg-source: error: add build2.6/temp.linux-i686-2.6/src/wrapper/id3.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.6/temp.linux-i686-2.6/src/wrapper/basics.o: binary file contents changed | dpkg-source: error: add build2.6/temp.linux-i686-2.6/src/wrapper/basics.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.6/temp.linux-i686-2.6/src/wrapper/rest.o: binary file contents changed | dpkg-source: error: add build2.6/temp.linux-i686-2.6/src/wrapper/rest.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.7/lib.linux-i686-2.7/_tagpy.so: binary file contents changed | dpkg-source: error: add build2.7/lib.linux-i686-2.7/_tagpy.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.7/temp.linux-i686-2.7/src/wrapper/id3.o: binary file contents changed | dpkg-source: error: add build2.7/temp.linux-i686-2.7/src/wrapper/id3.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.7/temp.linux-i686-2.7/src/wrapper/basics.o: binary file contents changed | dpkg-source: error: add build2.7/temp.linux-i686-2.7/src/wrapper/basics.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: cannot represent change to tagpy-0.94.8/build2.7/temp.linux-i686-2.7/src/wrapper/rest.o: binary file contents changed | dpkg-source: error: add build2.7/temp.linux-i686-2.7/src/wrapper/rest.o in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b tagpy-0.94.8 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671333: trac-httpauth: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: trac-httpauth Version: 1.1+r6675-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild trac-httpauth FTBFS if built twice in a row: | dpkg-source -b trac-httpauth-1.1+r6675 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building trac-httpauth using existing ./trac-httpauth_1.1+r6675.orig.tar.gz | dpkg-source: warning: file trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/requires.txt has no final newline (either original or modified version) | dpkg-source: warning: file trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/PKG-INFO | trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/SOURCES.txt | trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/dependency_links.txt | trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/entry_points.txt | trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/requires.txt | trac-httpauth-1.1+r6675/trunk/TracHTTPAuth.egg-info/top_level.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/trac-httpauth_1.1+r6675-1.diff.MM9t3k | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b trac-httpauth-1.1+r6675 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671335: trac: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: trac Version: 0.12.2-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild trac FTBFS if built twice in a row: | dpkg-source -b trac-0.12.2 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building trac using existing ./trac_0.12.2.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | trac-0.12.2/Trac.egg-info/PKG-INFO | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/trac_0.12.2-1.diff.CXXbcc | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b trac-0.12.2 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671334: trac-wikiprint: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: trac-wikiprint Version: 1.9.2-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild trac-wikiprint FTBFS if built twice in a row: | dpkg-source -b trac-wikiprint-1.9.2 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building trac-wikiprint using existing ./trac-wikiprint_1.9.2.orig.tar.gz | dpkg-source: warning: file trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/requires.txt has no final newline (either original or modified version) | dpkg-source: warning: file trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: info: local changes detected, the modified files are: | trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/PKG-INFO | trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/SOURCES.txt | trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/dependency_links.txt | trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/entry_points.txt | trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/requires.txt | trac-wikiprint-1.9.2/0.11/TracWikiPrintPlugin.egg-info/top_level.txt | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/trac-wikiprint_1.9.2-1.diff.e8jUWi | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b trac-wikiprint-1.9.2 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671336: writetype: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: writetype Version: 1.2.130+bzr139-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild writetype FTBFS if built twice in a row: | dpkg-source -b writetype-1.2.130+bzr139 | dpkg-source: info: using options from writetype-1.2.130+bzr139/debian/source/options: --compression=bzip2 --compression-level=7 --extend-diff-ignore=(^|/)config.(sub|guess)$ | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: patches are not applied, applying them now | dpkg-source: info: applying desktop.patch | dpkg-source: info: applying url.patch | dpkg-source: info: applying extension.patch | dpkg-source: info: building writetype using existing ./writetype_1.2.130+bzr139.orig.tar.bz2 | dpkg-source: warning: ignoring deletion of file translations/qt_nl_NL.qm | dpkg-source: warning: ignoring deletion of file translations/qt_es_AR.qm | dpkg-source: warning: ignoring deletion of file translations/qt_eu_ES.qm | dpkg-source: warning: ignoring deletion of file translations/qt_es_ES.qm | dpkg-source: warning: ignoring deletion of file translations/qt_es_MX.qm | dpkg-source: info: local changes detected, the modified files are: | writetype-1.2.130+bzr139/translations/qt_es.ts | writetype-1.2.130+bzr139/translations/qt_eu_ES.ts | writetype-1.2.130+bzr139/translations/qt_nl_NL.ts | writetype-1.2.130+bzr139/translations/writetype.ts | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/writetype_1.2.130+bzr139-1.diff.t2tdOO | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b writetype-1.2.130+bzr139 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671337: drift: FTBFS - ghc6: command not found
Package: drift Version: 2.2.3-2+b1 Severity: serious Package fails to build under pbuilder/unstable: checking for a BSD-compatible install... /usr/bin/install -c checking for sh... /bin/sh configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating example/Makefile config.status: creating src/Version.hs config.status: creating DrIFT.spec config.status: creating drift-ghc touch debian/stamp-autotools /usr/bin/make -C . make[2]: Entering directory `/tmp/buildd/drift-2.2.3' Making all in src make[3]: Entering directory `/tmp/buildd/drift-2.2.3/src' sh ./collect_rules.sh Rules.hs /usr/bin/make all-am make[4]: Entering directory `/tmp/buildd/drift-2.2.3/src' ghc6 -O2 -i. -i. -hidir . -odir . -o DrIFT --make ./DrIFT.hs /bin/bash: ghc6: command not found make[4]: *** [DrIFT] Error 127 Even if ghc6 (obsoleted package) was changed to ghc in debian/rules[1], the build fails: ... ghc -O2 -i. -i. -hidir . -odir . -o DrIFT --make ./DrIFT.hs DrIFT.hs:20:18: Could not find module `System' It is a member of the hidden package `haskell98-2.0.0.1'. Use -v to see a list of the files searched for. make[3]: *** [DrIFT] Error 1 Jari [1] -DEB_CONFIGURE_EXTRA_FLAGS := --with-hc=ghc6 +DEB_CONFIGURE_EXTRA_FLAGS := --with-hc=ghc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570069: [gud...@gudjon.org: Re: [comedi] libcomedi0 removed from debian testing]
Hi On Thursday 03 May 2012 11:37:43 Bernd Porr wrote: I've just tried to build a new debian package for libcomedi based on the latest git package Gudjon has provided. It fails trying to patch the comedi-calibrate. It cannot find the ./configure script (though it's there). It is the comedi_calibrate configure script. Did you create your package as a multiple source package? I am going on a holiday for a few days but I will se if I can upgrade my package to the latest git. Here's everything: the original package and my attempt to create a new version. http://www.linux-usb-daq.co.uk/tmp/comedilib.tar.gz Anyway. I've corrected the ./configure call in rules using the new options we have added during the last couple of days. Also played a bit with the build dependencies (removed ruby there, added dblatex, ...). Do you like the multiple source approach? Why is comedi_calibrate a separate source? Can you please add some command line parameter that makes configure not search for libcomedi.so while configuring comedi_calibrate? Then I don't have to patch configure. Patching configure is a bad habit since the configure scripts can be regenerated and then the patch doesn't work anymore. There are dependencies on unnecessary libraries. Is it possible/easy to fix that before the release? Regards Gudjon
Bug#665359: python3-gi: Segfault when computing size of subclasses
reassign 665359 python3.2 3.2.3~rc2-1
thanks
After a multiple-days debugging orgy I finally found what's triggering this.
Please see https://bugzilla.gnome.org/show_bug.cgi?id=669157 for the whole
story, but copying the last comment here for convenience:
The Debian package runs this snippet between configure and make, to configure
static (builtin) vs. dynamic (extensions) modules:
egrep \
^#($$(awk -v ORS='|' '$$2 ~ /^extension$$/ {print $$1}'
debian/PVER-minimal.README.Debian.in)XX) \
Modules/Setup.dist \
| sed -e 's/^#//' -e 's/-Wl,-Bdynamic//;s/-Wl,-Bstatic//' \
$(1)/Modules/Setup.local
When I disable this part, the local build works.
That code results in this Modules/Setup.local:
- 8 -
# Edit this file for local setup changes
array arraymodule.c # array objects
math mathmodule.c _math.c # -lm # math library functions, e.g. sin()
_struct _struct.c # binary structure packing/unpacking
time timemodule.c _time.c # -lm # time operations and variables
_random _randommodule.c # Random number generator
atexit atexitmodule.c # Register functions to be run at
interpreter-shutdown
_elementtree -DUSE_PYEXPAT_CAPI _elementtree.c # elementtree accelerator
_pickle _pickle.c # pickle accelerator
_datetime _datetimemodule.c # datetime accelerator
_bisect _bisectmodule.c # Bisection algorithms
_heapq _heapqmodule.c # Heap queue algorithm
unicodedata unicodedata.c # static Unicode character database
fcntl fcntlmodule.c # fcntl(2) and ioctl(2)
spwd spwdmodule.c # spwd(3)
grp grpmodule.c # grp(3)
select selectmodule.c # select(2); not on ancient System V
_socket socketmodule.c
_ssl _ssl.c -lssl -lcrypto
_posixsubprocess _posixsubprocess.c # POSIX subprocess module helper
_hashlib _hashopenssl.c -lssl -lcrypto
syslog syslogmodule.c # syslog daemon interface
binascii binascii.c
_ctypes _ctypes/_ctypes.c _ctypes/callbacks.c _ctypes/callproc.c
_ctypes/stgdict.c _ctypes/cfield.c _ctypes/malloc_closure.c -lffi
zlib zlibmodule.c -I$(prefix)/include -L$(exec_prefix)/lib -lz
pyexpat pyexpat.c -lexpat
- 8 -
Bisecting this quickly leads to the _ctypes module configuration.
So a small reproducer based on the upstream Python 3.2 build is:
* Configure and build pygobject with PYTHON=python3.2 (or specify the full
path for a local python build)
* Build python 3.2 with the broken _ctypes module configuration:
$ cd /tmp/
$ tar xf python3.2_3.2.3.orig.tar.gz
$ cd python3.2-3.2.3
$ ./configure --with-wide-unicode # to be compatible with the Debian/Ubuntu
python 3.2
$ echo '_ctypes _ctypes/_ctypes.c _ctypes/callbacks.c _ctypes/callproc.c
_ctypes/stgdict.c _ctypes/cfield.c _ctypes/malloc_closure.c -lffi'
Modules/Setup.local
$ make -j4
Then in the pygobject built tree, run
$ (cd tests; TEST_NAMES=test_everything.TestCallbacks PYTHONPATH=..:.
LD_LIBRARY_PATH=./.libs GI_TYPELIB_PATH=. /tmp/python3.2-3.2.3/python
./runtests.py)
which reproduces the failure.
Conversely, if I change the ctypes line in debian/PVER-minimal.README.Debian.in
from
_ctypes extension
to
_ctypes builtin
and build/install the packages, everything works.
For a more convenient reproducer on the Debian side, you can just run
python3 python3-gi-segfault.py, i. e. the attached sample code here.
So there is something wrong with how this configures the _ctypes module to be
linked into python itself, instead of being a separate module
(/usr/lib/python3.2/lib-dynload/_ctypes.cpython-32mu.so) that you get with
builtin (that is indeed pretty confusing, given that I switched it _from_
extension _to_ builtin. Or there is a Python 3.2/libffi bug which causes
that.
Note that this is also tracked in https://launchpad.net/bugs/909292
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
Bug#671338: gridengine-drmaa-dev: leaves alternatives after purge
Package: gridengine-drmaa-dev Version: 6.2u5-5 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see http://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. deconfigured or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove name path'. Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m20.9s ERROR: WARN: Broken symlinks: /usr/lib/libdrmaa.so - /etc/alternatives/libdrmaa.so /etc/alternatives/libdrmaa.so - /usr/lib/gridengine-drmaa/usr/lib/libdrmaa.so 0m22.5s ERROR: FAIL: Package purging left files on system: /etc/alternatives/libdrmaa.so - /usr/lib/gridengine-drmaa/usr/lib/libdrmaa.so not owned /usr/lib/libdrmaa.so - /etc/alternatives/libdrmaa.so not owned cheers, Andreas gridengine-drmaa-dev_6.2u5-5.log.gz Description: GNU Zip compressed data
Bug#406935: another evaluation: 1.3.15-2
On Wed, 2012-05-02 at 13:21 -0400, Antoine Beaupré wrote: On Wed, 25 Apr 2012 23:42:41 -0400, Robert James Clay j...@rocasa.us wrote: On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote: If you tried doing the configuration 'automatically' instead of letting it go manually, it's quite possible that the ledgersmb role is there but does not have the correct permissions. ALTER ROLE ledgersmb WITH SUPERUSER LOGIN NOINHERIT; Then back to setup.pl and see how it goes. I tried that, no luck. The user for ledger is created properly by setup.pl, but i still get prompted for a password popup after logging in: i see the frames, but it is shadowed by a password window. I still get the lsmb13 error. Oh bloody hell: the problem was that I was blocking cookies. I hate it when that happens...g , I can login to ledger now. Glad to hear it! Still a really weird failure mode if you ask me. :) Indeed.g And that can certainly complicate things in applications like this, trying to figure if a particular problem is in the application, or the browser, or the web server, or ... Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671257: gettext: msgfmt output format prevents multiarch migration (fwd)
Santiago Vila wrote: I remember well the bug by Neil Williams: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468209 where he asked --endianness to be documented, as he was thinking about using it in his embedded projects to override the current msgfmt default of always creating little endian .mo files. Let me repeat: The default is that msgfmt creates .mo files in the endianness of the platform where 'msgfmt' runs. (Otherwise, Paul Martin would not have found a multi-arch problem.) Neil Williams's motivation were cross-compiling situations (from x86 to mips systems, for example). He wanted to make 'msgfmt' aware of the target system's endianness. This has a negligible impact and is not a good enough rationale for adding one more option to the manual. But I find Paul Martin's rationale convincing. So I'm adding the documentation. Now, how to use this in the Debian build system, is your turn. The opinion of people in charge of multiarch is that in the long run, it would be much better if msgfmt's default changed in gettext to be little endian again. I don't agree. Users of PowePC systems have the same right to optimized MO files as users of x86 systems. Therefore I would like to have the issue solved in Debian's build system. Let me know if you would need additional targets or variables in Makefile.in.in (on top of the configure option that I already mentioned). Bruno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671320: [Pkg-fglrx-devel] Bug#671320: fglrx-driver: due to dependencies, uninstallable with current xorg in sid
On 2012-05-03 11:47, Giacomo Mulas wrote: with the recent upgrade of xorg in sid, which jumped xserver-xorg-core to version 1.12.1, fglrx-driver became uninstallable, since it depends on xorg-video-abi-11 and xserver-xorg-core ( 2:1.11.99). Are these dependencies just out of caution (i.e. fglrx-driver is untested yet but it might work) or is it known not to work with the current xorg release in sid? Xorg Xserver 1.12 is not yet supported by the FGLRX driver, this needs to be fixed by AMD. (It was tested and reliably crashed, so no workarounds like IgnoreABI are possible.) Please use Xorg from wheezy (or squeeze-backports) for now. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671339: get_crc_table() in zlib.h has wrong return type for LP64
Package: zlib1g-dev:amd64
Version: 1:1.2.6.dfsg-2
The declaration of get_crc_table() in zlib.h has wrong return type for LP64
platforms.
Please update zlib package to zlib-1.2.7 which fixes the problem.
get_crc_table() returns a table for calculating CRC.
zlib-1.2.3 uses unsigned long for the table entries.
zlib-1.2.6 uses unsigned 32 bit integer for the table entries.
However the return type of get_crc_table() is not changed at zlib-1.2.6.
So zlib-1.2.6 has type mismatch between actual table entries and return
type of get_crc_table.
The problem can be reproduced as follows.
% dpkg -l|grep zlib
ii zlib1g:amd64 1:1.2.6.dfsg-2
compression library - runtime
ii zlib1g-dev:amd64 1:1.2.6.dfsg-2
compression library - development
% lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (wheezy)
Release: testing
Codename: wheezy
% cat tst.c
#include stdio.h
#include zlib.h
int main(int argc, char *argv[])
{
printf(zlib header version: %s\n, ZLIB_VERSION);
printf(zlib library version: %s\n, zlibVersion());
printf(sizeof(long) = %d\n, (int)sizeof(long));
printf(sizeof(get_crc_table()[0]) = %d\n,
(int)sizeof(get_crc_table()[0]));
printf(get_crc_table()[0] = %#016lx\n, (unsigned long)get_crc_table()[0]);
printf(get_crc_table()[1] = %#016lx\n, (unsigned long)get_crc_table()[1]);
printf(get_crc_table()[2] = %#016lx\n, (unsigned long)get_crc_table()[2]);
printf(get_crc_table()[3] = %#016lx\n, (unsigned long)get_crc_table()[3]);
return 0;
}
% gcc -Wall tst.c -lz
% ./a.out
zlib header version: 1.2.6
zlib library version: 1.2.6
sizeof(long) = 8
sizeof(get_crc_table()[0]) = 8
get_crc_table()[0] = 0x77073096
get_crc_table()[1] = 0x990951baee0e612c
get_crc_table()[2] = 0x706af48f076dc419
get_crc_table()[3] = 0x9e6495a3e963a535
get_crc_table()[0] returns 0x77073096.
But it should return 0, according to zlib-1.2.6.dfsg/crc32.h.
% head zlib-1.2.6.dfsg/crc32.h
/* crc32.h -- tables for rapid CRC calculation
* Generated automatically by crc32.c
*/
local const crc_table_t FAR crc_table[TBLS][256] =
{
{
0xUL, 0x77073096UL, 0xee0e612cUL, 0x990951baUL, 0x076dc419UL,
0x706af48fUL, 0xe963a535UL, 0x9e6495a3UL, 0x0edb8832UL, 0x79dcb8a4UL,
0xe0d5e91eUL, 0x97d2d988UL, 0x09b64c2bUL, 0x7eb17cbdUL, 0xe7b82d07UL,
zlib-1.2.3 returns 0 correctly as follows.
% dpkg -l|grep zlib
ii zlib1g 1:1.2.3.4.dfsg-3
compression library - runtime
ii zlib1g-dev 1:1.2.3.4.dfsg-3
compression library - development
% lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.4 (squeeze)
Release: 6.0.4
Codename: squeeze
% gcc -Wall tst.c -lz
% ./a.out
zlib header version: 1.2.3.4
zlib library version: 1.2.3.4
sizeof(long) = 8
sizeof(get_crc_table()[0]) = 8
get_crc_table()[0] =
get_crc_table()[1] = 0x0077073096
get_crc_table()[2] = 0x00ee0e612c
get_crc_table()[3] = 0x00990951ba
--
Tanaka Akira
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671200: linux-2.6: Generate leds-modules for Kirkwood Debian installer
* Simon Guinot si...@sequanux.org [2012-04-27 01:15]: On LaCie boards, the leds-ns2 and leds-netxbig drivers are used to configure the LEDs. This drivers are currently not embedded into the network-console installer. As a consequence, it is not possible to change the LEDs behaviour on LaCie boards when the SSH server is ready. Please, consider applying the attached patch. This patch is not correct: --- debian/installer/armel/package-list (revision 18961) +++ debian/installer/armel/package-list (working copy) @@ -5,7 +5,7 @@ # Package: kernel-image Provides_iop32x: rtc-modules -Provides_kirkwood: rtc-modules, jffs2-modules, zlib-modules +Provides_kirkwood: rtc-modules, jffs2-modules, zlib-modules, leds-modules This says that the LEDs moduleas are built-in, which is not the case. You have to create debian/installer/armel/modules/armel-kirkwood/leds-modules with a list of modules. I'm also not sure about the name leds-modules... maybe they should just be added to input-modules or something but I'll leave that to the kernel/installer team to decide. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
* Simon Guinot si...@sequanux.org [2012-04-30 17:49]: You will find in attachment an updated patch. The netboot image is no longer generated. Sorry, I should have asked this before: do the LaCie devices set the correct machine ID in u-boot? If yes, I'm happy to apply this patch, but only after the one for flash-kernel has been accepted. + mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n Debian kernel -d $(TEMP_KERNEL) $(SOME_DEST)/$(EXTRANAME)/lacie/uImage + mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n debian-installer ramdisk -d $(TEMP_INITRD) $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd + update-manifest $(SOME_DEST)/$(EXTRANAME)/Lacie/uImage Linux kernel for LaCie NAS ^ This should be lower-case but I can make that change when applying the patch. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671227: ncurses-term: glitches in bterm
On Wed, May 02, 2012 at 05:13:07PM +0200, Sven Joachim wrote:
Package: ncurses-term
Version: 5.9-7
Severity: normal
On 2012-05-01 12:12 +0200, Samuel Thibault wrote:
There is however apparently a discrepancy between the
bogl-provided bterm and the ncurses-provided bterm (I assumed that they
were the same, but they are not), resulting in quite a few glitches e.g.
in mutt. The ncurses one is probably outdated, we will have to fix that.
It would be nice to have details (or a screenshot).
Running infocmp shows the following differences (bterm-bogl being the
file from bogl 0.1.18-6, bterm-ncurses the file from ncurses-term
5.9-7):
,
| comparing bterm-bogl to bterm-ncurses.
| comparing booleans.
| comparing numbers.
| comparing strings.
| acsc: '``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~',
'aajjkkllmmqqttuuxx'.
| op: NULL, '\E49;39m'.
| sgr: '\E[0m%?%p1%t\E[7m%;%?%p2%t\E[4m%;', NULL.
`
There are comments in ncurses' misc/terminfo.src regarding the
differences in acsc and sgr:
,
| # Notes:
| # bterm only supports acs using wide-characters, has case for these:
qjxamlkut
| # bterm does not support sgr, since it only processes one parameter -TD
`
right (I read the source-code using the Debian package as a reference,
and that's accurate enough barring updates past my review at the end of 2009).
--
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
Bug#670527: libdebian-installer4: missing support for LaCie NASes (Kirkwood)
* Simon Guinot si...@sequanux.org [2012-04-26 12:04]: Support for LaCie Kirkwood machines is missing from map_hardware. This prevents from using Debian installer with the LaCie NASes (based on Kirkwood SoC). Applied, thank you! -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671238: linux-image-2.6.32-5-s390x: no CMM with z/VM Resource Manager possible
Am 03.05.2012 09:06 schrieb Bastian Blank: severity 671238 important thanks On Wed, May 02, 2012 at 07:12:45PM +0200, Martin Grimm wrote: CMM (Cooperative Memory Management) can't be controlled from z/VM Resource Manager because the core component (cmm) is builtin and the needed communication module (smsgiucv) is build as a module. Loading the module smsgiucv doesn't help. Which versions are affected? I believe both Squeeze (2.6.32) and Wheezy (3.2). Bastian Yes, I can confirm the problem for both versions. Martin -- Martin Grimm Zentrum für Informationsverarbeitung und Informationstechnik Dienstsitz Bonn An der Küppe 2 53225 Bonn Tel.: +49 228 99 680 5298 e-mail: extern.martin.gr...@zivit.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671340: ipxe: include undionly.kkpxe
Package: ipxe Version: 1.0.0+git-20120202.f6840ba-3 Severity: wishlist Dear Maintainer, please consider including undionly.kkpxe in ipxe package. We use undionly.kpxe for netbooting computer classes in our university. But there are mainboards that can boot only with undionly.kkpxe, because of buggy BIOS. So for now we compile ipxe manually to boot those computers over the net via iPXE. If undionly.kkpxe will be included in ipxe package we will boot our classes without compiling iPXE manually. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#670782: [Pkg-xfce-devel] Bug#670782: thunar-thumbnailers: dependency required tumbler
Hi, On Sun, Apr 29, 2012 at 12:31:04PM -0400, David Sugar wrote: Well that explains why it didn't work. I thought the package was still valid when I was updating from squeeze recently. Perhaps tumbler should have replaces and/or provides thunar-thumbnailers or something similar? I don't think that's needed/adequate (replaces usually stands for files/dirs' replacements, and provides could be nice if tumbler and thunar-thumbnailers shared a similar interface, but they don't ; tumbler is dbus-activated and more desktop-agnostic, while thunar-thumbnailers was really tied to thunar). Anyway, thunar recommends tumbler, so it should ensure it will be installed on upgrades, unless the user explicitly disabled Automatic installation of recommended packages... but then (s)he knows the consequences. ;-) On 04/29/2012 08:11 AM, Lionel Le Folgoc wrote: Hi, Thanks for your bug report. On Sat, Apr 28, 2012 at 05:55:45PM -0400, David Sugar wrote: Package: thunar-thumbnailers Version: 0.4.1-3 Severity: normal Thunar Thumbnailers requires tumbler to actually produce thumbnails in thunar. By itself installing thunar-thumbnailers is presently actually useless without tumbler installed. On Xfce 4.8 and later, you need tumbler to produce thumbnails. Thunar-thumbnailers was the method for Xfce 4.6, but is deprecated now and isn't used anymore. If you check your package manager, you will see it has already been removed from testing/unstable. -- Best regards, Lionel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670938: flash-kernel: support is missing for LaCie Kirkwood NASes
Loïc, can you please review/apply. * Simon Guinot si...@sequanux.org [2012-04-25 03:42]: Package: flash-kernel Version: 3.0~rc.4 Severity: normal Tags: patch Dear Maintainer, uImage et uInitrd files are not generated for LaCie Kirkwood NASes. Please, consider applying the attached patch. Regards, Simon -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 3.2.0-00010-g0a7ba17 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages flash-kernel depends on: ii devio1.2-1+b1 ii initramfs-tools 0.102 ii linux-base 3.5 flash-kernel recommends no packages. Versions of packages flash-kernel suggests: ii u-boot-tools 2011.12-3 -- no debconf information From 3d9c8dc8e5719d2dbf22da4fecb3005e8dc620fb Mon Sep 17 00:00:00 2001 From: Simon Guinot simon.gui...@sequanux.org Date: Thu, 26 Apr 2012 19:16:27 +0200 Subject: [PATCH] Add support for LaCie Kirkwood NASes This patch provides support for the following LaCie boards: - LaCie 2Big Network v2 - LaCie 5Big Network v2 - LaCie Internet Space v2 - LaCie Network Space v2 - LaCie Network Space Max v2 - LaCie d2 Network v2 --- README|6 ++ db/all.db | 54 ++ 2 files changed, 60 insertions(+) diff --git a/README b/README index 4eb4f35..1d2c600 100644 --- a/README +++ b/README @@ -25,6 +25,12 @@ The following systems are supported: - HP t5325 Thin Client - HP Media Vault mv2120 - Intel SS4000-E + - LaCie 2Big Network v2 + - LaCie 5Big Network v2 + - LaCie Internet Space v2 + - LaCie Network Space v2 + - LaCie Network Space Max v2 + - LaCie d2 Network v2 - Linksys NSLU2 - Marvell DB-78x00-BP Development Board - Marvell OpenRD-Base diff --git a/db/all.db b/db/all.db index 2ce4645..b7f7caa 100644 --- a/db/all.db +++ b/db/all.db @@ -116,6 +116,60 @@ Boot-Multi-Path: /boot/uImage Required-packages: u-boot-tools Bootloader-sets-root: yes +Machine: LaCie 2Big Network v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie 5Big Network v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie Internet Space v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie Network Space v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie Network Space Max v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie d2 Network v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + # Really: Intel SS4000-e and compatibles Machine: Lanner EM7210 Method: redboot -- 1.7.9.5 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670941: network-console: set LED signal on LaCie Kirkwood NASes when SSH is ready
* Simon Guinot si...@sequanux.org [2012-04-25 04:07]: Please consider applying the attached patch. Applied, thanks! -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671341: ITP: libdbix-dr-perl -- easy DBI helper (perl inside SQL and blessed results)
Package: wnpp Severity: wishlist Owner: Dmitry E. Oboukhov un...@debian.org Package name: libdbix-dr-perl Version : 0.18 Upstream Author : Dmitry E. Oboukhov un...@debian.org URL : http://search.cpan.org/~unera/DBIx-DR/ License : Artistic, GPL-1 Programming Lang: Perl Description : easy DBI helper The package extends DBI and allows You: to use perl inside Your SQL requests; to bless resultsets into Your package; to place Your SQL's into dedicated directory; to use usual DBI methods. -- . ''`. Dmitry E. Oboukhov : :’ : email: un...@debian.org jabber://un...@uvw.ru `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537 signature.asc Description: Digital signature
Bug#570069: [gud...@gudjon.org: Re: [comedi] libcomedi0 removed from debian testing]
Can you please add some command line parameter that makes configure not search for libcomedi.so while configuring comedi_calibrate? Just added the option --disable-comedilib-checking to the configure script. It's in the comedi_calibrate git now. /Bernd Gudjon I. Gudjonsson wrote: Hi On Thursday 03 May 2012 11:37:43 Bernd Porr wrote: I've just tried to build a new debian package for libcomedi based on the latest git package Gudjon has provided. It fails trying to patch the comedi-calibrate. It cannot find the ./configure script (though it's there). It is the comedi_calibrate configure script. Did you create your package as a multiple source package? I am going on a holiday for a few days but I will se if I can upgrade my package to the latest git. Here's everything: the original package and my attempt to create a new version. http://www.linux-usb-daq.co.uk/tmp/comedilib.tar.gz Anyway. I've corrected the ./configure call in rules using the new options we have added during the last couple of days. Also played a bit with the build dependencies (removed ruby there, added dblatex, ...). Do you like the multiple source approach? Why is comedi_calibrate a separate source? Can you please add some command line parameter that makes configure not search for libcomedi.so while configuring comedi_calibrate? Then I don't have to patch configure. Patching configure is a bad habit since the configure scripts can be regenerated and then the patch doesn't work anymore. There are dependencies on unnecessary libraries. Is it possible/easy to fix that before the release? Regards Gudjon -- You received this message because you are subscribed to the Google Groups Comedi: Linux Control and Measurement Device Interface group. To post to this group, send email to comedi_l...@googlegroups.com. To unsubscribe from this group, send email to comedi_list+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/comedi_list?hl=en. -- www:http://www.linux-usb-daq.co.uk/ http://www.berndporr.me.uk/ http://www.imdb.com/name/nm3293421/ Mobile: +44 (0)7840 340069 Work: +44 (0)141 330 5237 University of Glasgow School of Engineering 72 Oakfield Avenue (Rankine Building for deliveries) Glasgow, G12 8LT -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671342: RM: console-tools -- ROM; No longer maintained upstream
Package: ftp.debian.org Severity: normal console-tools has not been maintained upstream for many years. In squeeze, we moved to kbd | console-tools, now plan to remove console-tools. Some (3) packages still Depend: on console-tools, but bugs have been submitted and changes are trivial : #645937 goto-fai #671079 hotkey-setup #671081 hibernate #671082 gcpegg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671343: mayavi2: FTBFS if built twice in a row: unrepresentable changes to source
Source: mayavi2 Version: 4.1.0-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild mayavi2 FTBFS if built twice in a row: | dpkg-source -b mayavi2-4.1.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building mayavi2 using existing ./mayavi2_4.1.0.orig.tar.gz | dpkg-source: warning: ignoring deletion of file mayavi/images/m2_about.jpg | dpkg-source: error: cannot represent change to mayavi2-4.1.0/tvtk/tvtk_classes.zip: binary file contents changed | dpkg-source: error: add tvtk/tvtk_classes.zip in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: warning: file mayavi2-4.1.0/mayavi.egg-info/requires.txt has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/mayavi.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/docs/build/tvtk/html/searchindex.js has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/docs/build/tvtk/html/objects.inv has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/docs/build/tvtk/html/devel.html has no final newline (either original or modified version) [SNIP - tons of similar warnings and errors] | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b mayavi2-4.1.0 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671344: python-netaddr: FTBFS if built twice in a row: unrepresentable changes to source
Source: python-netaddr Version: 0.7.6-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild python-netaddr FTBFS if built twice in a row: | dpkg-source -b python-netaddr-0.7.6 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building python-netaddr using existing ./python-netaddr_0.7.6.orig.tar.gz | dpkg-source: error: cannot represent change to python-netaddr-0.7.6/docs/api/crarr.png: binary file contents changed | dpkg-source: error: add docs/api/crarr.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b python-netaddr-0.7.6 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671345: [INTL:pl] Polish debconf translation
Package: durep Severity: wishlist Tags: l10n patch Hi! Please add the attached Polish debconf translation. Thanks in advance, -- Michał Kułach pl.po Description: Binary data
Bug#671346: [INTL:pl] Polish debconf translation
Package: approx Severity: wishlist Tags: l10n patch Hi! Please add the attached Polish debconf translation. Thanks in advance, -- Michał Kułach pl.po Description: Binary data
Bug#671308: [PATCH] wmnut: Helping to update to packaging format 3.0
2012/5/3 jari.aa...@cante.net: Package: wmnut Severity: wishlist Tags: patch Hi, Hi Jari, The dpatch patch management system has been deprecated for some time. The Lintian currently flags use of dpatch packages as an error. The new 3.0 packaging format is an improved version which, among other things, contains patch management built-in. For more information, see: http://wiki.debian.org/Projects/DebSrc3.0 I had some free time; see attached patch to migrate to new package format. Note that all files in debian/patches/* are canocalized to *.patch. Let me know if there is anything that needs adjusting or if it is ok to upload this version in a NMU in case you are working on other issues needing attention. thanks, your contrib here is much appreciated. I'm indeed currently in the depth of completing 2.6.3 packages, and most of all, 2.6.4 upstream + preparation for 2.8.0 to make things easier, I can release a new wmnut upstream... beside from this, note that I'm still looking for a co-maint to help me in NUT related packages maintenance. this would allow me to concentrate even more on upstream developments. would you be interested in? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
On Wed, 2012-05-02 at 13:38 -0400, Antoine Beaupré wrote: On Wed, 25 Apr 2012 22:57:22 -0400, Robert James Clay j...@rocasa.us wrote: On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote: Confusion: two passwords? = I get prompted for a password twice... How are those two different? Should they be the same? I *feel* the first password is the ledgersmb password, but who knows? It seems to be working in the setup.pl script, what is the second one for then? One reason the debconf is not currently enabled by default I am not sure I understand that... When I first put it in (with 1.3.14-2), I had the default to the question Configure LedgerSMB Automatically? as true. I changed that to false with a later version because with the way it was running, it was unclear what it was asking for and because if the 'ledgersmb' role was created, it didn't get created with the correct permissions. If you installed a version before that change and then upgraded; you wouldn't necessarily see that now defaults to not doing it automatically or have the option to turn it back off unless you ran 'dpkg-reconfigure ledgersmb'. is that it is not working as expected. Currently, it can create the ledgersmb role but not with the correct permissions. That, I understand. However, maybe a clever few psql invocations could fix that, no? That's what I've been thinking it will take, assuming there isn't some other way that I just haven't figured out yet. I did add some sql that is supposed to correct the permissions but that doesn't appear to be working. Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671347: cups-lpr disabled after update
Package: cups Version: 1.4.4-7+squeeze1 Severity: normal Installation of the cups-package always disables cups-lpr in /etc/inetd.conf. Please let the entries in /etc/inetd.conf untouched. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 Versions of packages cups depends on: ii adduser 3.112+nmu2 add and remove users and groups ii bc 1.06.95-2The GNU bc arbitrary precision cal ii cups-client 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii cups-common 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii cups-ppdc 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii debconf [debconf-2. 1.5.36.1 Debian configuration management sy ii ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF ii libavahi-client30.6.27-2+squeeze1Avahi client library ii libavahi-common30.6.27-2+squeeze1Avahi common library ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcups21.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii libcupscgi1 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii libcupsdriver1 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii libcupsimage2 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii libcupsmime11.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii libcupsppdc11.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii libdbus-1-3 1.2.24-4+squeeze1simple interprocess messaging syst ii libgcc1 1:4.4.5-8GCC support library ii libgnutls26 2.8.6-1+squeeze2 the GNU TLS library - runtime libr ii libgssapi-krb5-21.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - k ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libkrb5-3 1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7.2 OpenLDAP libraries ii libpam0g1.1.1-6.1+squeeze1 Pluggable Authentication Modules l ii libpaper1 1.1.24 library for handling paper charact ii libpoppler5 0.12.4-1.2 PDF rendering library ii libslp1 1.2.1-7.8OpenSLP libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libusb-0.1-42:0.1.12-16 userspace USB programming library ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii poppler-utils 0.12.4-1.2 PDF utilitites (based on libpopple ii procps 1:3.2.8-9/proc file system utilities ii ssl-cert1.0.28 simple debconf wrapper for OpenSSL ii ttf-freefont20090104-7 Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages cups recommends: ii cups-driver-gutenprint 5.2.6-1 printer drivers for CUPS ii foomatic-filters4.0.5-6+squeeze1 OpenPrinting printer support - fil ii ghostscript-cups8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF Versions of packages cups suggests: ii cups-bsd 1.4.4-7+squeeze1 Common UNIX Printing System(tm) - ii cups-pdf 2.5.0-16 PDF printer for CUPS ii foomatic-db 20100630-1 OpenPrinting printer support - dat ii hplip 3.10.6-2+squeeze1 HP Linux Printing and Imaging Syst ii smbclient 2:3.5.6~dfsg-3squeeze7 command-line SMB/CIFS clients for ii udev 164-3 /dev/ and hotplug management daemo pn xpdf-korean | xpd none (no description available) -- Configuration Files: /etc/cups/cupsd.conf [Errno 13] Keine Berechtigung: u'/etc/cups/cupsd.conf' /etc/cups/mime.convs changed [not included] -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, socket, usb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671348: override: hibernate:utils/optional
Package: ftp.debian.org Severity: normal The pririty for hibernate was changed from extra to optional in 2.0+15+g88d54a8-1. (Describe here the reason for this change) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671302: libav: circular dependency between libav and opencv
On Thu, May 3, 2012 at 3:44 AM, Pino Toscano p...@debian.org wrote: Package: libav Version: 6:0.8.1-7 Severity: important Hi, libav 6:0.8.1-7 reenables the use of opencv... which itself uses libav libraries. This currently makes libav unbuildable on mipsel and hurd-i386, and generically makes libav no more bootstrap'able without having itself compiled already. Could you please drop the opencv usage again, please? Thanks, -- Pino ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers What could be done instead is a binary only upload with opencv support disabled (i.e. use dpkg-buildpackage -B). Doing it on our end will not require changing the version. Once this package is uploaded, the release team can then be asked to do a binNMU for these archs, which will bring back opencv support since the archive will contain the regular *.debian.tar.gz changes that included opencv. I believe this is better than doing a full build on all archs without opencv, then doing another build with opencv. -- ~ Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671340: ipxe: include undionly.kkpxe
03.05.2012 14:03, Kasatkin Nikolay wrote: Package: ipxe Version: 1.0.0+git-20120202.f6840ba-3 Severity: wishlist Dear Maintainer, please consider including undionly.kkpxe in ipxe package. We use undionly.kpxe for netbooting computer classes in our university. But there are mainboards that can boot only with undionly.kkpxe, because of buggy BIOS. So for now we compile ipxe manually to boot those computers over the net via iPXE. If undionly.kkpxe will be included in ipxe package we will boot our classes without compiling iPXE manually. How useful this undionly.kkpxe thing is, generally? The thing is: ipxe has really a TON of various options and configuration variations, packaging all these isn't practical. So we decided to package only one, the most universal variant. For other usages, recompiling from source is the best way to go, since you as a user know best which configuration do you need, exactly. It is not like ipxe is changing 10 times a day, so frequent recompile/reinstall isn't necessary: you compile it only when you hit some limitation or bug, in your version. It is not like ipxe is the place where most recent features are always requireed, either. So I'd say keep it the way the package currently is, and compile site-specific versions as needed, locally. And mark this bugreport as wontfix. Unless ther's a very good reason why this undionly.kkpxe can be useful for a much wider userbase. Also, when including other options, I'd say they should be made available using some configuration mechanism (such as debconf), to be included in a bootloader configuration -- like ipxe.lknl currently handled. 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#671349: O: fsvs -- ENOTIME
Package: wnpp Severity: normal I've not been doing the upstream author a favour by holding on to this package. Releasing as discussed with Iain Lane and Philipp Marek phil...@marek.priv.at. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671350: yafc: New yafc fork
Package: yafc Version: 1.1.1.dfsg.1-4.2 Severity: wishlist Hello, There is a new (and apparently active) fork of yafc here: http://www.yafc-ftp.com/ Considering original upstream has been quite dead for several years, please consider packaging the fork instead. Providing it's good... ;-) Thanks, George -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yafc depends on: ii dpkg 1.16.3 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-32 ii libncurses5 5.9-7 ii libreadline6 6.2-8 ii libtinfo5 5.9-7 yafc recommends no packages. yafc 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#406935: another evaluation: 1.3.15-2
On Wed, 2012-05-02 at 13:38 -0400, Antoine Beaupré wrote: On Wed, 25 Apr 2012 23:24:29 -0400, Robert James Clay j...@rocasa.us wrote: On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote: The darn contrib directory == I still had to configure the contrib_dir. Now I know I had to, but even then: I forgot, so I hit this cryptic message in the web interface: I think this could be improved by having sane defaults. If we disregard backports, there's generally only one version of postgresql in stable Debian releases: * lenny: 8.3 * squeeze: 8.4 * wheezy: 8.4 and 9.1 (but is testing) I'd forgotten that 8.4 is actually still available in wheezy...g The default is 9.1, so that's certainly the version to assume. * sid: 8.4, 9.0, 9.1... So that could be changed so that, for example, the .conf shipped in sid/wheezy would be for 9.1 contrib and so hardcode that path, while the backport would have a modified .conf file for 8.4.. That's what I've been planning on doing, although I hadn't thought as far as what would be needed for a backport. The file itself is already being patched for other reasons (updates for other directories), so this could just be added to it. Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671351: Use these settings for all networks sharing this essid does not work
Package: wicd-curses Version: 1.7.2.3-1 Severity: normal When editing an access point marked with Use these settings for all networks sharing this essid, changes fail to propagate to other access points with the same essid. For example, I checked [X] Automatically connect to this network on the first 'eduroam' access point on the list, hit F10 to save the changes and go back to the main menu and selected the second 'eduroam' ap on the list. The box was not checked, although going back to the first one, I see that it was successfully saved. Similar issues occur when setting the identity for PEAP with GTC, and probably occur when trying to change other settings. Similarly, editing an essid for the first time, and selecting the Use these settings for all networks sharing this essid does not propagate changes to other networks sharing the essid. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_ES.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd-curses depends on: ii python2.7.2-10 ii python-urwid 1.0.1-2 ii wicd-daemon 1.7.2.3-1 Versions of packages wicd-curses recommends: ii sudo 1.8.3p2-1 wicd-curses suggests no packages. Versions of packages wicd-cli depends on: ii python 2.7.2-10 ii wicd-daemon 1.7.2.3-1 Versions of packages wicd-cli recommends: ii sudo 1.8.3p2-1 Versions of packages wicd-gtk depends on: ii python 2.7.2-10 ii python-glade2 2.24.0-3 ii python-gtk22.24.0-3 ii wicd-daemon1.7.2.3-1 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 Versions of packages wicd-daemon depends on: ii adduser 3.113+nmu1 ii dbus1.5.12-1 ii debconf 1.5.42 ii iproute 20120319-1 ii iputils-ping3:20101006-1+b1 ii isc-dhcp-client [dhcp3-client] 4.2.2.dfsg.1-4 ii lsb-base4.1+Debian2 ii net-tools 1.60-24.1 ii psmisc 22.16-1 ii pump0.8.24-7 ii python 2.7.2-10 ii python-dbus 0.84.0-3 ii python-gobject 3.2.0-3 ii python-wicd 1.7.2.3-1 ii wireless-tools 30~pre9-8 ii wpasupplicant 0.7.3-6 wicd-daemon recommends no packages. Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-9 Versions of packages python-wicd depends on: ii python 2.7.2-10 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 -- debconf information: * wicd/users: -- |_)|_/ Ryan Kavanagh | GnuPG key | \| \ http://ryanak.ca/ | 4A11C97A signature.asc Description: Digital signature
Bug#585409: #585409: wine/wine-unstable NMUs; #479659: RFH: wine
Hi Hilko and Michael, First, many thanks for your work towards more recent wine packages in Debian: I definitely hope that this work will allow Wheezy to benefit from wine 1.4 (and wine 1.5.3 as wine-unstable ?). That said, I think that the current pace (and content, FWIW) of the NMUs is fine but aren't really clear in terms of intent: are you interested in just pushing NMUs out as one-shots (and hence letting the current maintainers handle the responsibility of the resulting packages) to just have newer wine versions available or are you interested in becoming (co-)maintainers of wine (and wine-unstable FWIW). In that latter case, this intent should IMHO be clearly stated in the #479659 RFH bug (including links to packaging effort and NMU changes) as that would make the situation much more clear to outsiders just reading the bugreports. Le 24.04.2012 15:23, Hilko Bengen a écrit : Should we build and upload a wine-gecko package or should the dependency in the wine package be modified? If I read [wG] correctly, wine 1.2 needs wine-gecko 1.0.0, which is already packaged as wine-gecko-unstable, so for 1.2, I'd just go with a symlink. [wG] http://wiki.winehq.org/Gecko wine 1.4 would need wine-gecko 1.4 which would IMHO preferably be maintained as the wine-gecko package, allowing the normal and -unstable suites to stay unentangled. (The packaging for wine-gecko should of course be inspired by the one for wine-gecko-unstable.) Do you need help in that domain? Cheers and best regards, OdyX signature.asc Description: OpenPGP digital signature
Bug#668304: mailman: Translations should use unicode charset
On Tue, 10 Apr 2012, Ralf Jung wrote: Package: mailman Version: 1:2.1.13-5 Severity: wishlist Tags: l10n The mailman translations should use uncide as character set instead of the language-specific local character sets. I see no reason not to use unicode nowadays, and after some manual conversion as described on http://www.divideandconquer.se/2009/08/17/convert-mailman-translation-to-utf-8/ mailman is working fine with unicode as charset for the German and English translation. That solution is a hack, really. The gettext system was designed to allow translators to use whatever charset encoding they wish, and there is no need to change all the translations for that. What you need is translations to be *shown* in your own charset, not translations to *be* in UTF8, which is usually irrelevant. The gettext system takes care of charset conversion but apparently it's not working properly. So yes, there seems to be a bug somewhere, but modifying all the translations is the wrong solution. (I was going to report this as a bug but I see that it's already reported) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
On Thu, May 03, 2012 at 11:25:50AM +0100, Martin Michlmayr wrote: * Simon Guinot si...@sequanux.org [2012-04-30 17:49]: You will find in attachment an updated patch. The netboot image is no longer generated. Sorry, I should have asked this before: do the LaCie devices set the correct machine ID in u-boot? If yes, I'm happy to apply this patch, but only after the one for flash-kernel has been accepted. Yes, the LaCie stock U-Boot provides the correct machine ID. + mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n Debian kernel -d $(TEMP_KERNEL) $(SOME_DEST)/$(EXTRANAME)/lacie/uImage + mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n debian-installer ramdisk -d $(TEMP_INITRD) $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd + update-manifest $(SOME_DEST)/$(EXTRANAME)/Lacie/uImage Linux kernel for LaCie NAS ^ This should be lower-case but I can make that change when applying the patch. Argh, it is a typo. Thanks for doing that change. Simon signature.asc Description: Digital signature
Bug#671352: grub-pc - Does not see partition table on AoE devices
Package: grub-pc Version: 1.99-21 Severity: important grub-install /dev/etherd/e0.0 fails to include the module for the partition table. grub-probe --target=partmap -d /dev/etherd/e0.0 does not return anything. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-pc depends on: ii debconf [debconf-2.0] 1.5.42 ii grub-common1.99-21 ii grub-pc-bin1.99-21 ii grub2-common 1.99-21 ii ucf3.0025+nmu3 grub-pc recommends no packages. grub-pc suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668304: [Pkg-mailman-hackers] Bug#668304: mailman: Translations should use unicode charset
On Thu, 3 May 2012, Santiago Vila wrote: That solution is a hack, really. The gettext system was designed to allow translators to use whatever charset encoding they wish, and there is no need to change all the translations for that. Yes, but mailman uses only one encoding per language, and that encoding for both gettext and whatever else it needs to do then. And a hack is still good enough for Mailman 2, I guess. The FSF only wants real fixes to go into Mailman 3… 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-314 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Elmar Geese -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670182: contact with upstream
I had contact with upstream development and he is going to use your patch thanks!. Will package it when the new version appears. Regards, Martijn van Brummelen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667214: Help needed to fix gcc 4.7 bug in jellyfish package
Hi Guillaume,
in the Debian bug tracking system
http://bugs.debian.org/667214
a build problem when using gcc-4.7 was reported. Below you can read
some discussion about a possible fix.
Michael, I can confirm that I also tried to s/uint_t/int/ in
parse_dna.hpp with the same result (same error message) after I did my
initial posting (that's why I did not felt a real need to send another
mail).
And yes, I agree that assigning negative values to unsigned variables
smells like done with some purpose which might stay hidden from the
first look and I would have definitely asked upstream about any problem
my suggested patch might have caused. I just felt like doing some
investigation into the problem might make sense. However, it seems
that this does not lead to any progres.
Guillaume, could you enlighten us a bit about this trick?
Kind regards
Andreas.
On Thu, May 03, 2012 at 09:52:09AM +0200, Michael Wild wrote:
On 05/02/2012 08:33 AM, Andreas Tille wrote:
Hi,
I tried to fix the problem in the jellyfish package but the general
hints given did not helped me really. Any more precise help to fix
this problem:
parse_dna.cc:97:3: error: narrowing conversion of '-3' from 'int' to 'const
uint_t {aka const long unsigned int}' inside { } is ill-formed in C++11
[-Werror=narrowing]
My first idea was to do
--- jellyfish.orig/jellyfish/parse_dna.cc
+++ jellyfish/jellyfish/parse_dna.cc
@@ -57,7 +57,7 @@
}
}
- const uint_t parse_dna::codes[256] = {
+ const int parse_dna::codes[256] = {
-3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -2, -3, -3, -3, -3, -3,
-3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3,
-3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -1, -3, -3,
--- jellyfish.orig/jellyfish/parse_dna.hpp
+++ jellyfish/jellyfish/parse_dna.hpp
@@ -55,7 +55,7 @@
static uint64_t mer_string_to_binary(const char *in, uint_t klen) {
uint64_t res = 0;
for(uint_t i = 0; i klen; i++) {
-const uint_t c = parse_dna::codes[(uint_t)*in++];
+const int c = parse_dna::codes[(int)*in++];
if(c CODE_NOT_DNA)
return 0;
res = (res 2) | c;
because it makes no sense to initialise uint with negative numbers but
this did not changed the error message which sounds totally strange to
me.
Kind regards
Andreas.
You missed the declaration of parse_dna::codes in parse_dna.hpp.
diff --git a/jellyfish/parse_dna.cc b/jellyfish/parse_dna.cc
index ab3ec64..9ea5ae1 100644
--- a/jellyfish/parse_dna.cc
+++ b/jellyfish/parse_dna.cc
@@ -57,7 +57,7 @@ namespace jellyfish {
}
}
- const uint_t parse_dna::codes[256] = {
+ const int parse_dna::codes[256] = {
-3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -2, -3, -3, -3, -3, -3,
-3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3,
-3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -3, -1, -3, -3,
diff --git a/jellyfish/parse_dna.hpp b/jellyfish/parse_dna.hpp
index 0435ae2..7ef8afd 100644
--- a/jellyfish/parse_dna.hpp
+++ b/jellyfish/parse_dna.hpp
@@ -46,7 +46,7 @@ namespace jellyfish {
* '\n': map to -2. ignore
* Other ASCII: map to -3. Skip to next line
*/
-static const uint_t codes[256];
+static const int codes[256];
static const uint_t CODE_RESET = -1;
static const uint_t CODE_IGNORE = -2;
static const uint_t CODE_COMMENT = -3;
@@ -55,7 +55,7 @@ namespace jellyfish {
static uint64_t mer_string_to_binary(const char *in, uint_t klen) {
uint64_t res = 0;
for(uint_t i = 0; i klen; i++) {
-const uint_t c = parse_dna::codes[(uint_t)*in++];
+const int c = parse_dna::codes[(uint_t)*in++];
if(c CODE_NOT_DNA)
return 0;
res = (res 2) | c;
That said, assigning -3 to an unsigned int seems to be a pretty
conscious choice to me, so it might have been done on purpose to create
a wrap-around. Also, the same pattern shows up many other places (e.g.
parse_dna::CODE_RESET, parse_dna::CODE_IGNORE, ...). IMHO bad practice,
but plausible. Probably it's best to contact upstream about this and ask
what their original intention was.
Michael
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fa23929.3000...@gmail.com
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669643: ITP: bugzilla4 -- web-based bug tracking system
Hi. On Fri, Apr 20, 2012 at 01:54:01PM -0400, m...@everybody.org wrote: Package: wnpp Owner: Mark A. Hershberger m...@everybody.org Severity: wishlist * Package name: bugzilla4 Version : 4.0.6 Upstream Author : Mozilla Corp * URL or Web page : http://bugzilla.org/ * License : MPL Description : web-based bug tracking system Great idea. Have you checked why bugzilla3 used to be in Debian, and got removed (see #638705). I guess you'd better have to convince people that things will be improved with the new version, for the success of this ITP ;-) Hope this helps. Best regards, -- Olivier BERGER http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
