Bug#502052: gimp 2.6 uninstallable on i386 experimental :: gimp and gimp-data version mismatch.
Package: gimp Version: 2.6.1-1 Severity: serious Justification: Policy 3.5 Snippet from apt-get install : gimp: Depends: gimp-data (<= 2.6.0-z) but 2.6.1-1 is to be installed I guess that explains it all. gimp is 2.6.0-1 and gimp-data is 2.6.1-1 for i386 on experimental, leaving gimp 2.6 uninstallable. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25lanky (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages gimp depends on: ii gimp-data 2.6.1-1 Data files for GIMP ii libaa1 1.4p5-37+b1 ascii art library ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libbabl-0.0-0 0.0.22-1 Dynamic, any to any, pixel format ii libc6 2.7-10GNU C Library: Shared libraries ii libcairo2 1.6.4-6 The Cairo 2D vector graphics libra ii libdbus-1-31.2.1-3 simple interprocess messaging syst ii libdbus-glib-1-2 0.74-1simple interprocess messaging syst ii libexif12 0.6.16-2.1library to parse EXIF files ii libfontconfig1 2.5.0-2 generic font configuration library ii libfreetype6 2.3.5-1+b1FreeType 2 font engine, shared lib ii libgegl-0.0-0 0.0.18-1 Generic Graphics Library ii libgimp2.0 2.6.0-1 Libraries for the GNU Image Manipu ii libglib2.0-0 2.16.1-2 The GLib library of C routines ii libgtk2.0-02.12.9-2 The GTK+ graphical user interface ii libhal10.5.10-5 Hardware Abstraction Layer - share ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii liblcms1 1.16-8Color management library ii libmng11.0.9-1 Multiple-image Network Graphics li ii libpango1.0-0 1.20.5-1 Layout and rendering of internatio ii libpng12-0 1.2.15~beta5-3PNG library - runtime ii libpoppler-glib3 0.8.2-2 PDF rendering library (GLib-based ii librsvg2-2 2.18.2-1 SAX-based renderer library for SVG ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii libwebkit-1.0-11.0.1-2 Web content engine library for Gtk ii libwmf0.2-70.2.8.4-6 Windows metafile conversion librar ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxmu62:1.0.4-1 X11 miscellaneous utility library ii libxpm41:3.5.7-1 X11 pixmap library ii python 2.5.2-1 An interactive high-level object-o ii python-gtk22.12.1-1 Python bindings for the GTK+ widge ii python-support 0.7.6 automated rebuilding support for p ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime gimp recommends no packages. Versions of packages gimp suggests: ii ghostscript 8.62.dfsg.1-2.1 The GPL Ghostscript PostScript/PDF ii gimp-data-extras 1:2.0.1-3 An extra set of brushes, palettes, pn gimp-help-en | gimp-help (no description available) pn gvfs-backends (no description available) ii libasound2 1.0.16-2ALSA library pn libgimp-perl (no description available) -- Laxminarayan Kamath Ammembal http://lankerisms.blogspot.com (+91) 9945036093 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501988: /usr/bin/plasma: Plasma crashes when trying install new wallpapers
On Sunday 12 October 2008 15:47:11 Saulo Soares de Toledo wrote: > Package: kdebase-workspace-bin > Version: 4:4.1.2-1 > Severity: grave > File: /usr/bin/plasma > Justification: causes non-serious data loss > > I don't know what was. I'm was trying install wallpapers and Plasma show me > the message "Problem while getting informations from server" or something > like this. The, the crash. Where is the data loss? And didn't you say in -84 that wallpaper installation works ? /Sune -- I cannot get access over the line, how does it work? First of all you should overclock the device. signature.asc Description: This is a digitally signed message part.
Bug#493047: Fix confirmed
Margarita Manterola schrieb am Sunday, den 12. October 2008: > I have confirmed that the proposed patch fixes the problem. > > Thomas, will you make the upload? Why? I'm in touch with Thomas and will do the upload on my own. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#496334: mdadm segfault on --assemble --force with raid10
I believe this bug is fixed by
http://neil.brown.name/git?p=mdadm;a=commitdiff;h=60b435db5a7b085ad1204168879037bf14ebd6d1
see below.
NeilBrown
From: Chris Webb <[EMAIL PROTECTED]>
Date: Thu, 19 Jun 2008 06:30:39 + (+1000)
Subject: Fix bug in forced assemble.
X-Git-Tag: mdadm-3.0-devel1~76^2~12
X-Git-Url:
http://neil.brown.name/git?p=mdadm;a=commitdiff_plain;h=60b435db5a7b085ad1204168879037bf14ebd6d1
Fix bug in forced assemble.
From: Chris Webb <[EMAIL PROTECTED]>
We are loading into the already-loaded 'st' instead of the
newly create 'tst', which is clearly wrong.
---
diff --git a/Assemble.c b/Assemble.c
index 36b2304..79f0912 100644
--- a/Assemble.c
+++ b/Assemble.c
@@ -656,7 +656,7 @@ int Assemble(struct supertype *st, char *mddev, int mdfd,
continue;
}
tst = dup_super(st);
- if (tst->ss->load_super(st,fd, NULL)) {
+ if (tst->ss->load_super(tst,fd, NULL)) {
close(fd);
fprintf(stderr, Name ": RAID superblock disappeared
from %s - not updating.\n",
devices[chosen_drive].devname);
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493047: Fix confirmed
I have confirmed that the proposed patch fixes the problem. Thomas, will you make the upload? -- Bessos, Maggie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498095: marked as done (localization-config: configures kde wrong when called with de_DE.UTF-8 as language)
Your message dated Mon, 13 Oct 2008 01:17:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#498095: fixed in localization-config 1.04
has caused the Debian Bug report #498095,
regarding localization-config: configures kde wrong when called with
de_DE.UTF-8 as language
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
498095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498095
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: localization-config
Version: 1.03
Severity: important
Tags: patch
When calling update-locale-config like
"/usr/sbin/update-locale-config de_DE.UTF-8" KDE (as in
/etc/kde3/system.kdeglobals and /etc/kde3/kdm/kdmrc) is configured for
Belgium German settings ("be" as country and "de" as language).
The problem is in the way the locale is mapped to the KDE language.
"langmap.pl" is mapping "de_DE.UTF-8" (actually "de.*") to
'German (BE)'. As for de_DE… there is only "[EMAIL PROTECTED]" in the list and
the algorithm used to determine the entry strips the original local to
de.* and not "de_DE.*".
To make a log story short, the "[EMAIL PROTECTED]" key in langmap.pl may be
change to "de_DE.UTF-8" (as this is the locale you get when you install
Debian with Germany/German settings) or even better "de_DE". This way
the correct language is chosen and the algorithm to find the correct
entry does not need to be modified (this short before the lenny
release).
This bug is important for Debian Edu/Skolelinux there
localization-config is used during installation and new users would be
greeted in Dutch (which happens to be the primary language for Belgium
in KDE) and not German. So it would be nice if a fixed version could be
uploaded to sid and be requested to get a freeze exception for lenny.
Thanks in advance
Greetings
Daniel
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages localization-config depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii libapt-pkg-perl 0.1.22+b1 Perl interface to libapt-pkg
ii libconfig-inifiles-perl 2.39-5 Read .ini-style configuration file
ii locales 2.7-13 GNU C Library: National Language (
ii perl-base 5.10.0-13 minimal Perl system
localization-config recommends no packages.
localization-config suggests no packages.
-- debconf information:
base-config/menu/localization-config-preinst:
base-config/menu/localization-config-postinst:
Index: conffiles.d/common/langmap.pl
===
--- conffiles.d/common/langmap.pl (revision 52332)
+++ conffiles.d/common/langmap.pl (working copy)
@@ -14,7 +14,7 @@
'da_DK' => 'Danish',
'[EMAIL PROTECTED]' => 'German (BE)',
'de_CH' => 'Swiss (DE)',
-'[EMAIL PROTECTED]' => 'German (DE)',
+'de_DE' => 'German (DE)',
'el_GR.UTF-8' => 'Greek',
'en_AU' => 'Australian',
'en_CA' => 'Canadian',
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: localization-config
Source-Version: 1.04
We believe that the bug you reported is fixed in the latest version of
localization-config, which is due to be installed in the Debian FTP archive:
localization-config-udeb_1.04_all.udeb
to pool/main/l/localization-config/localization-config-udeb_1.04_all.udeb
localization-config_1.04.dsc
to pool/main/l/localization-config/localization-config_1.04.dsc
localization-config_1.04.tar.gz
to pool/main/l/localization-config/localization-config_1.04.tar.gz
localization-config_1.04_all.deb
to pool/main/l/localization-config/localization-config_1.04_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings <[EMAIL PROTECTED]> (supplier of updated localization-config
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESS
Bug#498095: localization-config: configures kde wrong when called with de_DE.UTF-8 as language
Fixed in 1.04; NMU-diff follows.
(It's unclear to me what use these language names have now. The langmap
functions are only used by the etch/kde script which seems to map them
back to language/country components! I'm also concerned that it's
ignoring the specified locale encoding, but I'm not entirely clear how
that's used.)
Ben.
diff -Nru localization-config-1.03/conffiles.d/common/langmap.pl
localization-config-1.04/conffiles.d/common/langmap.pl
--- localization-config-1.03/conffiles.d/common/langmap.pl 2007-12-15
00:02:05.0 +
+++ localization-config-1.04/conffiles.d/common/langmap.pl 2008-10-13
01:23:57.0 +0100
@@ -7,66 +7,65 @@
my %lang_locale_map = (
# entries sorted alphabetically
-'bs_BA.ISO8859-2' => 'Bosnian',
-'bg_BG' => 'Bulgarian',
-'[EMAIL PROTECTED]' => 'Catalan',
-'cs_CZ' => 'Czech',
-'da_DK' => 'Danish',
-'[EMAIL PROTECTED]' => 'German (BE)',
+'bs' => 'Bosnian',
+'bg' => 'Bulgarian',
+'ca' => 'Catalan',
+'cs' => 'Czech',
+'da' => 'Danish',
+'de_BE' => 'German (BE)',
'de_CH' => 'Swiss (DE)',
-'[EMAIL PROTECTED]' => 'German (DE)',
-'el_GR.UTF-8' => 'Greek',
+'de' => 'German (DE)',
+'el' => 'Greek',
'en_AU' => 'Australian',
'en_CA' => 'Canadian',
-'[EMAIL PROTECTED]' => 'Irish (UK)',
-'[EMAIL PROTECTED]' => 'Irish',
-'[EMAIL PROTECTED]' => 'Galician',
+'en_IE' => 'Irish (UK)',
+'ga' => 'Irish',
+'gl' => 'Galician',
'en_GB' => 'British',
-'gd_GB' => 'Scots Gaelic',
-'gv_GB' => 'Manx Gaelic',
-'kw_GB' => 'Cornish',
-'en_US' => 'American (US)',
+'gd' => 'Scots Gaelic',
+'gv' => 'Manx Gaelic',
+'kw' => 'Cornish',
+'en' => 'American (US)',
'es' => 'Spanish',
'es_AR' => 'Spanish (AR)',
-'[EMAIL PROTECTED]' => 'Spanish (ES)',
+'es_ES' => 'Spanish (ES)',
'es_MX' => 'Spanish (MX)',
'es_PE' => 'Spanish (PE)',
-'fa_IR.UTF-8' => 'Faroe',
-'[EMAIL PROTECTED]' => 'Finnish',
+'fa' => 'Faroe',
+'fi' => 'Finnish',
'fr_BE' => 'French (BE)',
'fr_CA' => 'French (CA)',
'fr_CH' => 'Swiss (FR)',
-'[EMAIL PROTECTED]' => 'French',
-'he_IL' => 'Hebrew',
-'he_IL.UTF-8' => 'Hebrew',
-'hu_HU' => 'Hungarian',
-'[EMAIL PROTECTED]' => 'Italian',
-'ja_JP.EUC-JP'=> 'Japanese',
-'ko_KR' => 'Korean',
-'lv_LV' => 'Latvian',
-'lt_LT' => 'Lithuanian',
-'mk_MK' => 'Macedonian',
-'nb_NO' => 'Norwegian',
-'[EMAIL PROTECTED]' => 'German (ndk)',
-'[EMAIL PROTECTED]' => 'Dutch (BE)',
-'[EMAIL PROTECTED]' => 'Dutch',
-'nn_NO' => 'New Norwegian',
-'no_NO' => 'Norwegian',
-'pa_IN' => 'Punjabi (Gumurkhi)',
-'pl_PL' => 'Polish',
-'pt_PT' => 'Portuguese',
+'fr' => 'French',
+'he' => 'Hebrew',
+'hu' => 'Hungarian',
+'it' => 'Italian',
+'ja' => 'Japanese',
+'ko' => 'Korean',
+'lv' => 'Latvian',
+'lt' => 'Lithuanian',
+'mk' => 'Macedonian',
+'nb' => 'Norwegian',
+'nds' => 'German (ndk)',
+'nl_BE' => 'Dutch (BE)',
+'nl' => 'Dutch',
+'nn' => 'New Norwegian',
+'no' => 'Norwegian',
+'pa' => 'Punjabi (Gumurkhi)',
+'pl' => 'Polish',
+'pt' => 'Portuguese',
'pt_BR' => 'Brazilian',
-'ru_RU' => 'Russian',
-'se_NO' => 'Saami',
-'sk_SK' => 'Slovakian',
-'sl_SI' => 'Slovenian',
-'sq_AL' => 'Albanian',
-'sv_SE' => 'Swedish',
+'ru' => 'Russian',
+'se' => 'Saami',
+'sk' => 'Slovakian',
+'sl' => 'Slovenian',
+'sq' => 'Albanian',
+'sv' => 'Swedish',
'sv_FI' => 'Swedish (FI)',
-'th_TH' => 'Thai',
-'tr_TR' => 'Turkish',
-'tl_PH' => 'Tagalog',
-'uk_UA' => 'Ukrainian',
+'th' => 'Thai',
+'tr' => 'Turkish',
+'tl' => 'Tagalog',
+'uk' => 'Ukrainian',
) ;
sub get_lang_map() {
diff -Nru localization-config-1.03/debian/changelog
Bug#501959: chm2pdf: proposed NMU
Thanks very much for the quick work on this patch. -Steve On Sun, Oct 12, 2008 at 8:25 PM, Raphael Geissert <[EMAIL PROTECTED]> wrote: > tag 502044 patch > tag 501959 patch > thanks > > Hi, > > Attached is the diff for my proposed NMU. The new package version has NOT been > uploaded to give you the opportunity to make a better upload to address those > issues. > > Note that a separate upload is required for lenny. > > Kind regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500325: xorp: FTBFS: Not using -fPIC to generate shared lib.
On Sun, Oct 12, 2008 at 09:10:35PM +0200, Adeodato Simó wrote: > * Jose Calhariz [Tue, 07 Oct 2008 23:00:16 +0100]: > > > On Tue, Oct 07, 2008 at 06:45:17PM +0200, Adeodato Simó wrote: > > > * Jose Manuel dos Santos Calhariz [Mon, 06 Oct 2008 02:49:29 +0100]: > > > > Hello, > > > > > The configure command have two options: --enable-shared and --with-pic > > > > > I have tried --with-pic in a i386 arch and the shared libraries didn't > > > > have code without -fPIC. The xorp-user mailing list suggested to use > > > > "--enable-shared" for what seams to be the same problem [1], with an > > > > older version compiling in FreeBSD. > > > > > So I sent to the same mailing-list a question about the differences of > > > > the two options. > > > > > Looking inside configure command the differences are real, but minimal > > > > for a Linux system. So in the end could be better adding option > > > > "--with-pic" to the configure command than adding -fPIC to the > > > > compiler options. > > > > Ok, will you be able to upload soon? > > > I may need a sponsor. Exist another unreport FTBFS on the other > > archs, that can be more complicated to solve. I have not investigated > > what is the solution for the failure on sparc and other archs. > > > Do you propose that I make a version 1.5-5 for this bug and a 1.5-6 > > to address the other FTBFS. I have in mentors.debian.net the release 1.5-5 that fix this bug. > > Wow, that's very unfortunate. I'm afraid there isn't really much point > in a -5 that doesn't fix the FTBFS in the rest of arches. > > Do you think you'll have the time to investigate that second FTBFS? I have made a bug report about this second FTBFS with the number 502032. Let's move this talk there, please. > > Thanks, > Jose Calhariz -- -- As oportunidades são como o picles. Se você as agarra com muita força, elas escapam da sua mão --Sandra Bullock signature.asc Description: Digital signature
Processed: chm2pdf: proposed NMU
Processing commands for [EMAIL PROTECTED]: > tag 502044 patch Bug#502044: chm2pdf: bashism in /usr/bin/chm2pdf There were no tags set. Tags added: patch > tag 501959 patch Bug#501959: chm2pdf: Major security (temporary dirs) problems Tags were: security Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501959: chm2pdf: proposed NMU
tag 502044 patch
tag 501959 patch
thanks
Hi,
Attached is the diff for my proposed NMU. The new package version has NOT been
uploaded to give you the opportunity to make a better upload to address those
issues.
Note that a separate upload is required for lenny.
Kind regards,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
diff -u chm2pdf-0.9.1/debian/rules chm2pdf-0.9.1/debian/rules
--- chm2pdf-0.9.1/debian/rules
+++ chm2pdf-0.9.1/debian/rules
@@ -3,6 +3,7 @@
DEB_PYTHON_SYSTEM=pysupport
include /usr/share/cdbs/1/rules/debhelper.mk
+include /usr/share/cdbs/1/rules/patchsys-quilt.mk
# include /usr/share/cdbs/1/rules/simple-patchsys.mk
include /usr/share/cdbs/1/class/python-distutils.mk
diff -u chm2pdf-0.9.1/debian/changelog chm2pdf-0.9.1/debian/changelog
--- chm2pdf-0.9.1/debian/changelog
+++ chm2pdf-0.9.1/debian/changelog
@@ -1,3 +1,14 @@
+chm2pdf (0.9.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/control, debian/rules: use quilt to manage patches
+ * insecure_temp_dirs.diff (Closes: #501959):
+- Don't use static names to create temp dirs.
+- Commented out --dontextract from usage info, as it is not very useful now
+ * bashisms.diff: fix bashism in chm2pdf (Closes: #502044).
+
+ -- Raphael Geissert <[EMAIL PROTECTED]> Sun, 12 Oct 2008 17:54:24 -0500
+
chm2pdf (0.9.1-1) unstable; urgency=low
* New upstream release
diff -u chm2pdf-0.9.1/debian/control chm2pdf-0.9.1/debian/control
--- chm2pdf-0.9.1/debian/control
+++ chm2pdf-0.9.1/debian/control
@@ -5,7 +5,8 @@
Build-Depends: cdbs (>= 0.4.49),
debhelper (>= 5),
python,
- python-support (>= 0.6.4)
+ python-support (>= 0.6.4),
+ quilt
Standards-Version: 3.8.0
Package: chm2pdf
only in patch2:
unchanged:
--- chm2pdf-0.9.1.orig/debian/patches/bashisms.diff
+++ chm2pdf-0.9.1/debian/patches/bashisms.diff
@@ -0,0 +1,13 @@
+Index: chm2pdf-0.9.1/chm2pdf
+===
+--- chm2pdf-0.9.1.orig/chm2pdf
chm2pdf-0.9.1/chm2pdf
+@@ -1087,7 +1087,7 @@ def main(argv):
+ if options['verbose'] == '--verbose' and options['verbositylevel'] == 'high':
+ os.system('extract_chmLib ' + filename + ' ' + CHM2PDF_ORIG_DIR)
+ else:
+-os.system('extract_chmLib ' + filename + ' ' + CHM2PDF_ORIG_DIR + '&> /dev/null')
++os.system('extract_chmLib ' + filename + ' ' + CHM2PDF_ORIG_DIR + '> /dev/null 2>&1')
+
+ convert_to_pdf(cfile, filename, outputfilename, options)
+ shutil.rmtree(CHM2PDF_TEMP_WORK_DIR)
only in patch2:
unchanged:
--- chm2pdf-0.9.1.orig/debian/patches/insecure_temp_dirs.diff
+++ chm2pdf-0.9.1/debian/patches/insecure_temp_dirs.diff
@@ -0,0 +1,73 @@
+Index: chm2pdf-0.9.1/chm2pdf
+===
+--- chm2pdf-0.9.1.orig/chm2pdf
chm2pdf-0.9.1/chm2pdf
+@@ -27,6 +27,8 @@ import sgmllib
+ import os, os.path
+ import re, glob
+ import getopt
++import tempfile
++import shutil
+ # from BeautifulSoup import BeautifulSoup
+
+ global version
+@@ -39,8 +41,8 @@ global CHM2PDF_ORIG_DIR
+ global filename #the input filename
+
+ version = '0.9.1'
+-CHM2PDF_TEMP_WORK_DIR='/tmp/chm2pdf/work'
+-CHM2PDF_TEMP_ORIG_DIR='/tmp/chm2pdf/orig'
++CHM2PDF_TEMP_WORK_DIR=tempfile.mkdtemp()
++CHM2PDF_TEMP_ORIG_DIR=tempfile.mkdtemp()
+
+
+
+@@ -299,16 +301,6 @@ def convert_to_pdf(cfile, filename, outp
+ # ### File extraction and correction: START
+ #
+ if options['dontextract'] == '':
+-
+-try:
+-os.mkdir(CHM2PDF_TEMP_WORK_DIR)
+-except OSError: # The directory already exists.
+-pass
+-
+-try:
+-os.mkdir(CHM2PDF_TEMP_ORIG_DIR)
+-except OSError: # The directory already exists.
+-pass
+
+ try:
+ os.mkdir(CHM2PDF_ORIG_DIR)
+@@ -620,7 +612,7 @@ def usage (name):
+ print '\t--continuous\n\t\tSpecifies that the HTML sources are unstructured (plain web pages).\n\t\tNo page breaks are inserted between each file or URL in the output.'
+ print '\t--cookies \'name="value with space"; name=value\'\n\t\t'
+ print '\t--datadir directory\n\t\tSpecifies the location of the HTMLDOC data files, usually /usr/share/htmldoc or C:\Program Files\HTMLDOC '
+-print "\t--dontextract \n\t\tIf given, %s will not extract the HTML files from the given CHM file, but will use previously extracted copies from the temporary directory " %name + '(i.e. ' + CHM2PDF_TEMP_ORIG_DIR + ' and ' + CHM2PDF_TEMP_WORK_DIR + '). Usually you will use this option after you have used the \'--extract-only\' option to extract the files in order to correct them manually (in ' + CHM2PDF_TEMP_WORK_DIR + '). After the correction, a call with \'--dontextract\' will not overwrite your changes, but will use the corrected files instead.'
++#print "\t--dontextract \n\t\tIf given, %s w
Processed: notfound 423093 in 8.28.8-4
Processing commands for [EMAIL PROTECTED]: > notfound 423093 8.28.8-4 Bug#423093: fglrx-driver: Compiled for 7.1, incompatible with 1.3.0.0 Bug#420174: Cannot Login to X server: module mismatch Bug#420239: fglrx does not work with 2:1.3.0.0.dfsg-1 version of xserver-xorg-core Bug#420379: flgrx fully broken by new xorg versioning policy Bug#420814: doesn't work with the newest xorg version (7.2) Bug#420823: fglrx-kernel-src: (EE) Failed to load module "fglrx" (module requirement mismatch, 0) Bug no longer marked as found in version 8.28.8-4. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502042: now affecting both systems
Turns out that svn-workbench was only still running on the unaffected system because it was still running from a few days ago. Closing and restarting leads to exactly the same error so raising the severity of the bug because now svn-workbench doesn't start on either system. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#500461: libtidy-ruby1.8: SecurityError raised by Tidy.open on ruby1.8 1.8.7.72-1
Processing commands for [EMAIL PROTECTED]: > severity 500461 important Bug#500461: libtidy-ruby1.8: SecurityError raised by Tidy.open on ruby1.8 1.8.7.72-1 Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500461: libtidy-ruby1.8: SecurityError raised by Tidy.open on ruby1.8 1.8.7.72-1
severity 500461 important thanks On Fri, Oct 10, 2008 at 9:41 PM, Gunnar Wolf <[EMAIL PROTECTED]> wrote: > Before anything else: This bug is marked as "grave", because it > "renders package unusable". Dmitry, I'd downgrade the bug's severity, > as the package is perfectly usable as long as you don't raise > $SAFE. Of course, it _is_ a bug, and it _should_ be fixed, but I don't > see it as grave. Good argument about severity, downgraded as advised. > Umh... I'm trying to tackle this, but am still at loss - Anyway, I > think sharing this might help towards finding the solution. (...) > Now, buf comes from Tidybuf, which is also C-based > (DL::Importable::Internal::Memory). And... This is where I am stuck: I > can untaint Tidybuf as an object, but not its contents or > results. And, being it a buffer, it _does_ make sense that the data it > generates is considered tainted. Thanks for the help! I agree with your investigation, although I have doubts about whether DL does the right thing here. I think the problem is not that the data in buf is tainted when it shouldn't be, it's rather that a blanket SecurityError is raised by a library on the data that originates from the same library. But that's just a gut feeling, I haven't had time to dig deep into DL implementation to see how it decides whether to allow tainted parameters to DL calls. -- Dmitry Borodaenko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 501152
Processing commands for [EMAIL PROTECTED]: > tags 501152 patch Bug#501152: binary firmware in drivers/net/starfire_firmware.h There were no tags set. Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501152: binary firmware in drivers/net/starfire_firmware.h
FreeBSD appears to have copied the proper copyright notices into their versions of the firmware: http://fxr.watson.org/fxr/source/dev/sf/starfire_rx.h http://fxr.watson.org/fxr/source/dev/sf/starfire_tx.h "(c)2001 Adaptec, Inc. By using this software you agree that it is licensed to you "AS IS" and that Adaptec makes no warranties, express or implied, regarding the Software. Any redistribution of this Software must include this disclaimer and copyright notice." So this ought to be OK for firmware-nonfree. Ben. signature.asc Description: This is a digitally signed message part
Bug#501153: Tehuti driver and firmware distribution for Linux
I am writing as a member of the Debian project, which distributes a version of Linux. The project is attempting to resolve the licencing of firmware used with Linux. The following may require attention by your legal department. Linux includes a driver and firmware which are listed as copyright of Tehuti Networks and licenced under the GNU General Public Licence (GPL). Thank you for supporting Linux and free software. Unfortunately, applying the GPL to the firmware is problematic, because you distribute it in binary (or equivalent) form, and not the source code that your programmers used to create it. The GPL states that anyone redistributing a work that it covers must also offer to distribute the source code. This means that strictly speaking no-one outside Tehuti Networks is allowed to distribute the firmware, which I assume was not your intent. Please can you clarify the licence for the firmware, and preferably issue a new licence that clearly allows Debian and others to distribute the firmware. Ben. -- Ben Hutchings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494007
Processing commands for [EMAIL PROTECTED]: > tags 494007 patch Bug#494007: binary firmware in drivers/char/drm/r128_cce.c Tags were: help Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494007: binary firmware in drivers/char/drm/r128_cce.c
I asked Dave Airlie about this: 23:36 < bwh> airlied: Do you know who might be a good person to write to at ATI/AMD about the licence for firmware in r128? 23:48 < airlied> bwh: what license you want it under? its already MIT licensed. 23:50 < bwh> airlied: Is it? Thing is, r128_cce.c doesn't have any ATI copyright notice on it. 23:51 < airlied> bwh: fail.. it probably should have, its still MIT licensed though. 23:52 < bwh> So would someone at ATI be able to confirm that? 23:53 < airlied> well the r128_cce.c has the MIT license on top 23:53 < airlied> I'm just looking to see if I have the original DDK release. 23:55 < bwh> airlied: cheers 23:56 < airlied> so the original table was just released under NDA, with permission to reuse in open source. 23:58 < bwh> Funny sort of NDA ;-) Do you have some legally meaningful statement of the permission that you could forward? 23:58 < airlied> bwh: why funny? 23:58 < airlied> I get lots of NDAs like that. 23:59 < airlied> nope I've gotten nothing real, I doubt anyone in AMD has either, this is like a 10 year old part. I don't know if this is sufficient assurance of its licence. Ben. signature.asc Description: This is a digitally signed message part
Bug#501408: libnet-netrc-ruby: FTBFS in lenny: test runner failed
Hi, On Tue, 2008-10-07 at 10:29 +0200, Lucas Nussbaum wrote: > Package: libnet-netrc-ruby > Version: 0.2.1-1.1 > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20081006 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in a lenny chroot, your package failed > to build on i386. I can't reproduce the failure using freshly built pbuilders for lenny/amd64 or lenny/i386 (with an amd64 host system). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494308
Processing commands for [EMAIL PROTECTED]: > tags 494308 patch Bug#494308: binary firmware in drivers/net/e100.c Tags were: help Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494010
Processing commands for [EMAIL PROTECTED]: > tags 494010 patch Bug#494010: binary firmware in drivers/char/dsp56k.c Tags were: patch fixed-upstream help Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498631: Sun GigaSwift driver and firmware distribution for Linux
I am writing as a member of the Debian project, which distributes a version of Linux. The project is attempting to resolve the licencing of firmware used with Linux. Linux includes a driver (cassini) and firmware for GigaSwift NICs which are listed as copyright of Sun Microsystems and licenced under the GNU General Public Licence (GPL). Thank you for supporting Linux and free software. Unfortunately, applying the GPL to the firmware is problematic, because you distribute it in binary (or equivalent) form, and not the source code that your programmers used to create it. The GPL states that anyone redistributing a work that it covers must also offer to distribute the source code. This means that strictly speaking no-one outside Sun Microsystems is allowed to distribute the firmware, which I assume was not your intent. Please can you clarify the licence for the firmware, and preferably issue a new licence that clearly allows Debian and others to distribute the firmware. Ben. -- Ben Hutchings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501800: AW: Bug#501800: Please, provide a full example of the bug
Hello,
attached you will find 2 files which will reproduce the error on my server.
The funny thing is, that named crashes, if you use he line:
allow-update { key ddns; "ADservers"; "lan"; };
But with
allow-update { key ddns; "lan"; "ADservers"; };
it runs. So I can use my old configuration, if I change the order of the
address list of allow-update. Very strange.
I hope, you can reproduce the error now.
With kind regards.
Christian Motschke
-Ursprüngliche Nachricht-
Von: Maximiliano Curia [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 12. Oktober 2008 21:21
An: [EMAIL PROTECTED]
Betreff: Bug#501800: Please, provide a full example of the bug
tags 501800 +moreinfo
thank you
I have tried to reproduce this bug with the following named.local:
key "key-test" {
algorithm hmac-md5;
secret "IVqRBcWBoPU2LhJTFnaJrw==";
};
acl "test" {
192.168.0.0/24;
};
acl "another" {
192.168.1.0/24;
};
zone "example.com" {
type master;
file "/etc/bind/db.local";
allow-update { key key-test; "test"; "another"; };
check-names ignore;
};
And it seems to work. Could you please provide a minimal named.conf.local that
triggers this bug?
Anyway, in the 9.5.0 release sources the file KNOWN-DEFECTS documents an ugly
bug, and an untested patch. It might be worth checking if appling the
patch fixes your problem.
--
A computer scientist is someone who, when told to "Go to Hell,"
sees the "go to," rather than the destination, as harmful.
Saludos /\/\ /\ >< `/
named.conf.options.test
Description: named.conf.options.test
named.conf.local.test
Description: named.conf.local.test
Bug#501393: marked as done (kdeutils-dev unsatisfiable Depends: kdelibs4-dev (>= 4:3.5.10))
Your message dated Sun, 12 Oct 2008 21:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#501393: fixed in kdeutils 4:3.5.10-2 has caused the Debian Bug report #501393, regarding kdeutils-dev unsatisfiable Depends: kdelibs4-dev (>= 4:3.5.10) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 501393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501393 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: kdeutils Version: 4:3.5.10-1 User: [EMAIL PROTECTED] Usertags: kfreebsd Hi, the current version of kdeutils-dev is uninstallable in sid on all architectures. Please, could you either upload kdelibs_3.5.10 or lower the required version. The changelog says: kdeutils (4:3.5.10-1) unstable; urgency=low * New upstream release. All the changes, except fix for KDE bug 139774, were already provided by the patches: ... It looks like "kdelibs4-dev (>= 4:3.5.9)" should be sufficient. Thanks in advance Petr --- End Message --- --- Begin Message --- Source: kdeutils Source-Version: 4:3.5.10-2 We believe that the bug you reported is fixed in the latest version of kdeutils, which is due to be installed in the Debian FTP archive: ark_3.5.10-2_i386.deb to pool/main/k/kdeutils/ark_3.5.10-2_i386.deb kcalc_3.5.10-2_i386.deb to pool/main/k/kdeutils/kcalc_3.5.10-2_i386.deb kcharselect_3.5.10-2_i386.deb to pool/main/k/kdeutils/kcharselect_3.5.10-2_i386.deb kdelirc_3.5.10-2_i386.deb to pool/main/k/kdeutils/kdelirc_3.5.10-2_i386.deb kdessh_3.5.10-2_i386.deb to pool/main/k/kdeutils/kdessh_3.5.10-2_i386.deb kdeutils-dbg_3.5.10-2_i386.deb to pool/main/k/kdeutils/kdeutils-dbg_3.5.10-2_i386.deb kdeutils-dev_3.5.10-2_i386.deb to pool/main/k/kdeutils/kdeutils-dev_3.5.10-2_i386.deb kdeutils-doc-html_3.5.10-2_all.deb to pool/main/k/kdeutils/kdeutils-doc-html_3.5.10-2_all.deb kdeutils-doc_3.5.10-2_all.deb to pool/main/k/kdeutils/kdeutils-doc_3.5.10-2_all.deb kdeutils_3.5.10-2.diff.gz to pool/main/k/kdeutils/kdeutils_3.5.10-2.diff.gz kdeutils_3.5.10-2.dsc to pool/main/k/kdeutils/kdeutils_3.5.10-2.dsc kdeutils_3.5.10-2_all.deb to pool/main/k/kdeutils/kdeutils_3.5.10-2_all.deb kdf_3.5.10-2_i386.deb to pool/main/k/kdeutils/kdf_3.5.10-2_i386.deb kedit_3.5.10-2_i386.deb to pool/main/k/kdeutils/kedit_3.5.10-2_i386.deb kfloppy_3.5.10-2_i386.deb to pool/main/k/kdeutils/kfloppy_3.5.10-2_i386.deb kgpg_3.5.10-2_i386.deb to pool/main/k/kdeutils/kgpg_3.5.10-2_i386.deb khexedit_3.5.10-2_i386.deb to pool/main/k/kdeutils/khexedit_3.5.10-2_i386.deb kjots_3.5.10-2_i386.deb to pool/main/k/kdeutils/kjots_3.5.10-2_i386.deb klaptopdaemon_3.5.10-2_all.deb to pool/main/k/kdeutils/klaptopdaemon_3.5.10-2_all.deb kmilo_3.5.10-2_i386.deb to pool/main/k/kdeutils/kmilo_3.5.10-2_i386.deb kregexpeditor_3.5.10-2_i386.deb to pool/main/k/kdeutils/kregexpeditor_3.5.10-2_i386.deb ksim_3.5.10-2_i386.deb to pool/main/k/kdeutils/ksim_3.5.10-2_i386.deb ktimer_3.5.10-2_i386.deb to pool/main/k/kdeutils/ktimer_3.5.10-2_i386.deb kwalletmanager_3.5.10-2_i386.deb to pool/main/k/kdeutils/kwalletmanager_3.5.10-2_i386.deb superkaramba_3.5.10-2_i386.deb to pool/main/k/kdeutils/superkaramba_3.5.10-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> (supplier of updated kdeutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Oct 2008 22:54:43 +0200 Source: kdeutils Binary: kdeutils kdeutils-doc kdeutils-doc-html kdeutils-dev ark kcalc kcharselect kdelirc kdessh kdf kedit kfloppy kgpg khexedit kjots klaptopdaemon kmilo kregexpeditor ksim ktimer kwalletmanager superkaramba kdeutils-dbg Architecture: source all i386 Version: 4:3.5.10-2 Distribution: unstable Urgency: low Maintainer: Debian Qt/KDE Maintainers <[EMAIL PROTECTED]> Changed-By: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Description: ark- graphical archiving tool for KDE kcalc - calculator for KDE kcharselect - character selector for KDE kdelirc- infrared control for KDE kdessh - ssh frontend for KDE kdeutils - general purpose utiliti
Bug#500807: (no subject)
On Sun, 12 Oct 2008 10:50:24 -0300 David Bremner <[EMAIL PROTECTED]> wrote: > Dear Paul; > > Yes, this is your bug report. It seems that the bug is likely specific > to something about your setup, so we need more information to > (possibly) figure out what is going on. > > As a first step, you could try > > % mv .mozilla-thunderbird .mozilla-thunderbird.bak that removed all of my accounts of course.. > % icedove > > and see if you still have persistent crashes. whe I tried thunderbird, it didn't do it the first day, but it started to do it a day or so later.. > > Also, as I mentioned in my last message, it would be helpful to know > what IMAP server you are connecting to. I'm not aware of a simple way > to find that out within icedove, but it may be helpful to run > > % telnet mailhost 143 > > and look at the greeting the server sends. telnet my_email_server 143 Trying my_email_server_IP... Connected to my_email_server. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2005 Double Precision, Inc. See COPYING for distribution information. -- Paul Cartwright -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475958: document procedure to recover from "/dev/hda became /dev/sda" boot failure
Please let me know if something is wrong or badly written. It's a great idea to document this problem and ways to deal with it. It's an extremely unsettling experience to have it occur unexpectedly. Could I suggest taking your notes one step further, and explaining how to fix it permanently, or avoid it completely (by doing these steps before upgrading). I hope there aren't any errors here, I did proof-read it. I'm not sure if this applies in the same way to platforms other than x86. One can avoid this problem entirely, by using an identifier for the root filesystem that does not change from one boot to the next. There are two possible methods for doing this - labelling the filesystem, or using the filesystem's universal unique identifier (UUID). These methods are supported in Debian since the 'etch' release. The two approaches have advantages and disadvantages. The labelling approach is more readable, but there may be problems if another filesystem on your machine has the same label. The uuid approach is uglier, but having two clashing uuids is highly unlikely. For the examples below we assume the root filesystem is on /dev/hda6. We also assume your system has a working udev installation and ext2 or ext3 filesystems. To implement the labelling approach: 1. Label the filesystem (the name must be < 16 characters) # e2label /dev/hda6 rootfilesys 2. Edit /boot/grub/menu.lst Change the line # kopt=root=/dev/hda6 ro to # kopt=root=LABEL=rootfilesys ro NB: Leave the '#' at the start of the line, it needs to be there. 3. Run update-grub, to update the 'kernel' lines in menu.lst # update-grub 4. Edit /etc/fstab Change the line that mounts the '/' partition, eg. /dev/hda6 / ext3 defaults,errors=remount-ro 0 1 to LABEL=rootfilesys / ext3 defaults,errors=remount-ro 0 1 The change that matters here is the first column, you don't need to modify the other columns of this line. To implement the uuid approach: 1. Find out the universal unique identifier of your filesystem: # ls -l /dev/disk/by-uuid | grep hda6 lrwxrwxrwx 1 root root 24 2008-09-25 08:16 d0dfcc8a-417a-41e3-ad2e-9736317f2d8a -> ../../hda6 The uuid is the name of the symbolic link pointing to /dev/hda6. NB: your filesystem uuid will be a different string. 2. Edit /boot/grub/menu.lst Change the line # kopt=root=/dev/hda6 ro to # kopt=root=UUID=d0dfcc8a-417a-41e3-ad2e-9736317f2d8 ro NB: Leave the '#' at the start of the line, it needs to be there. 3. Run update-grub, to update the 'kernel' lines in menu.lst # update-grub 4. Edit /etc/fstab Change the line that mounts the '/' partition, eg. /dev/hda6 / ext3 defaults,errors=remount-ro 0 1 to UUID=d0dfcc8a-417a-41e3-ad2e-9736317f2d8/ ext3 defaults,errors=remount-ro 0 1 The change that matters here is the first column, you don't need to modify the other columns of this line. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#496387: marked as done (The possibility of attack with the help of symlinks in some Debian packages)
Your message dated Sun, 12 Oct 2008 21:17:58 + with message-id <[EMAIL PROTECTED]> and subject line Bug#496387: fixed in wims 3.62-13.1 has caused the Debian Bug report #496387, regarding The possibility of attack with the help of symlinks in some Debian packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 496387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496387 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: wims Severity: grave Hi, maintainer! This message about the error concerns a few packages at once. I've tested all the packages (for Lenny) on my Debian mirror. All scripts of packages (marked as executable) were tested. In some packages I've discovered scripts with errors which may be used by a user for damaging important system files or user's files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlink with the same name in this directory in order to destroy or rewrite some system or user file. Symlink attack may also lead not only to the data desctruction but to denial of service as well. Even if you create files or directories with help of function 'RANDOM' or pid(), then your system is not protected. Attacker can create many symlinks in order to destroy your data or create 'denial of service' for your package scripts. Even if you make rm(dir) for files/directories, then your system is not protected. Attacker can permanently create symlinks. This list is created with the help of script. This list is sorted by hand. Howewer in some cases mistake is possible. Please, Be understanding to possible mistakes. :) I set Severity into grave for this bug. The table of discovered problems is below. Discussion of this bug you can see in debian-devel@: http://lists.debian.org/debian-devel/2008/08/msg00271.html Binary-package: r-base-core-ra (1.1.1-1) file: /usr/lib/Ra/lib/R/bin/javareconf Binary-package: rccp (0.9-2) file: /usr/lib/rccp/delqueueask Binary-package: mafft (6.240-1) file: /usr/bin/mafft-homologs Binary-package: openoffice.org-common (1:2.4.1-6) file: /usr/lib/openoffice/program/senddoc Binary-package: crossfire-maps (1.11.0-1) file: /usr/share/games/crossfire/maps/Info/combine.pl Binary-package: sgml2x (1.0.0-11.1) file: /usr/bin/rlatex Binary-package: liguidsoap (0.3.6-4) file: /var/lib/liguidsoap/liguidsoap.py Binary-package: citadel-server (7.37-1) file: /usr/lib/citadel-server/migrate_aliases.sh Binary-package: ampache (3.4.1-1) file: /usr/share/ampache/www/locale/base/gather-messages.sh Binary-package: xen-utils-3.2-1 (3.2.1-2) file: /usr/lib/xen-3.2-1/bin/qemu-dm.debug Binary-package: dtc-common (0.29.6-1) file: /usr/share/dtc/admin/accesslog.php file: /usr/share/dtc/admin/sa-wrapper Binary-package: honeyd-common (1.5c-3) file: /usr/share/honeyd/scripts/test.sh Binary-package: lustre-tests (1.6.5-1) file: /usr/lib/lustre/tests/runiozone Binary-package: linuxtrade (3.65-8+b4) file: /usr/share/linuxtrade/bin/linuxtrade.bwkvol file: /usr/share/linuxtrade/bin/linuxtrade.wn file: /usr/share/linuxtrade/bin/moneyam.helper Binary-package: freevo (1.8.1-0) file: /usr/bin/freevo.real Binary-package: fml (4.0.3.dfsg-2) file: /usr/share/fml/libexec/mead.pl Binary-package: rkhunter (1.3.2-3) file: /usr/bin/rkhunter Binary-package: openswan (1:2.4.12+dfsg-1.1) file: /usr/lib/ipsec/livetest Binary-package: linux-patch-openswan (1:2.4.12+dfsg-1.1) file: /usr/src/kernel-patches/all/openswan/packaging/utils/maysnap file: /usr/src/kernel-patches/all/openswan/packaging/utils/maytest Binary-package: aptoncd (0.1-1.1) file: /usr/share/aptoncd/xmlfile.py Binary-package: cdcontrol (1.90-1.1) file: /usr/lib/cdcontrol/writtercontrol Binary-package: newsgate (1.6-23) file: /usr/bin/mkmailpost Binary-package: gpsdrive-scripts (2.10~pre4-3) file: /usr/bin/geo-code Binary-package: impose+ (0.2-11) file: /usr/bin/impose Binary-package: mgt (2.31-5) file: /usr/games/mailgo Binary-package: audiolink (0.05-1) file: /usr/bin/audiolink Binary-package: ibackup (2.27-4.1) file: /usr/bin/ibackup Binary-package: emacspeak (26.0-3) file: /usr/share/emacs/site-lisp/emacspeak/etc/extract-table.pl Binary-package: bk2site (1:1.1.9-3.1) file: /usr/lib/cgi-bin/bk2site/redirect.pl Binary-package: datafreedom-perl (0.1.7-1) file: /usr/bin/dfxml-invoice Binary-package: emacs-jabber (0.7.91-1) file: /usr/lib/emacsen-common/packages/install/emacs-jabber
Bug#501882: Some more info about this bug
On Sunday 12 October 2008 11:12:17 Frank Lichtenheld wrote: > pgsnap fails because /usr/bin/pgsnap does this: > > cd /usr/share/pgsnap > ./pgsnap.php $* > > Obviously this goes terribly wrong if the output directory is relative > (which is the default...). > pgsnap seems to work fine once you give it an absolute directory with the > -o option. > > pgsnap.php needs to get a way to tell the difference between its data > directory (i.e. /usr/share/pgsnap) and the users working directory. I can't > tell how much work that would be exactly, but looks like a invasive change > on first glance. > > Maybe this software isn't ready for a stable release? > > Gruesse, I tried using the -o option before I made the report (-o foo), but it wasn't an absolute path. I just tried it with and absolute path (-o /tmp/foobar) and it worked just fine. (looking at output now) The output looks pretty nice. I was thinking, if it's too invasive to change the code to use a relative directory, maybe it would be easier to write a wrapper that makes an absolute path from a relative one, and passes that to the actual pgsnap command. I can easily do this myself in python, but I don't know how to do it in php or sh (I know how to use `pwd`/output , but I don't know what to do about -o ../../somewhere/else). Also, I think that a warning in the manpage and/or README.Debian describing this behaviour would be enough to make it a normal bug, instead of a grave bug. Until you told me that the -o option needed an absolute path, the command was entirely unusable. Now that I know about it, I can consider it a normal (or probably important is more accurate) bug, but not a release critical one. -- Thanks: Joseph Rawson signature.asc Description: This is a digitally signed message part.
Bug#495211: #495211 - libatomic-ops FTBFS on powerpc
* Mike O'Connor [Sun, 12 Oct 2008 13:39:29 -0400]: > OK, I've uploaded 1.2-4+lenny1 to testing-proposed-updates. Thanks, we'll migrate it to testing once it's built for all architectures. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Que no te vendan amor sin espinas -- Joaquín Sabina, Noches de boda -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501153: Tehuti driver and firmware distribution for Linux
I am writing as a member of the Debian project, which distributes a version of Linux. The project is attempting to resolve the licencing of firmware used with Linux. The following may require attention by your legal department. Linux includes a driver and firmware which are listed as copyright of Tehuti Networks and licenced under the GNU General Public Licence (GPL). Thank you for supporting Linux and free software. Unfortunately, applying the GPL to the firmware is problematic, because you distribute it in binary (or equivalent) form, and not the source code that your programmers used to create it. The GPL states that anyone redistributing a work that it covers must also offer to distribute the source code. This means that strictly speaking no-one outside Tehuti Networks is allowed to distribute the firmware, which I assume was not your intent. Please can you clarify the licence for the firmware, and preferably issue a new licence that clearly allows Debian and others to distribute the firmware. Ben. -- Ben Hutchings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: wims: diff for NMU version 3.62-13.1
Processing commands for [EMAIL PROTECTED]: > tags 496387 +pending Bug#496387: The possibility of attack with the help of symlinks in some Debian packages Tags were: security Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#496387: wims: diff for NMU version 3.62-13.1
tags 496387 +pending
thanks
Hi,
The attached file is the diff for my wims 3.62-13.1 NMU. The associated
changelog entry is:
wims (3.62-13.1) unstable; urgency=medium
* Non-maintainer upload.
* Prevent against the possibility of an attack with the help of symlinks
by patching public_html/bin/coqweb and bin/accounts.sh. Patches (and
patch system) by the regular maintainer. (Closes: #496387)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [EMAIL PROTECTED]
`-
diff -Nru wims-3.62/account.sh.diff wims-3.62/account.sh.diff
--- wims-3.62/account.sh.diff 1970-01-01 01:00:00.0 +0100
+++ wims-3.62/account.sh.diff 2008-10-12 21:21:57.0 +0100
@@ -0,0 +1,27 @@
+--- account.sh.orig2008-08-24 23:15:21.0 +0200
account.sh 2008-08-24 23:19:57.0 +0200
+@@ -77,11 +77,20 @@
+
+ # Now referer logs.
+
+-cat /tmp/referer-home.log | sort | uniq | grep 'http://' | grep -v
'wims\.unice\.fr' | sed 's!http://!!g' | awk -F '#' '{print $1}' >>referer.log
+-echo >/tmp/referer-home.log
++ these following lines were commented because the use of
++ /tmp based files in a script create a security issue
++ Besides, there is little indication in the sources that
++ a file /tmp/referer-home.log shoukd already exist at this point.
++ so the commented lines were perhaps dead code.
+
+-cat referer.log* | grep $workday | awk '{print $3""$4}' \
+- | sort | uniq | sort -k 1 >$tmpdir/acctmp.log
++#cat /tmp/referer-home.log | sort | uniq | grep 'http://' | grep -v
'wims\.unice\.fr' | sed 's!http://!!g' | awk -F '#' '{print $1}' >>referer.log
++#echo >/tmp/referer-home.log
++
++#cat referer.log* | grep $workday | awk '{print $3" "$4}' \
++# | sort | uniq | sort -k 1 >$tmpdir/acctmp.log
++
++ end of the lines commented out for security reasons
++ ===
+
+ grep -v '??' $tmpdir/acctmp.log >referer/refuniq.log
+ a=`grep -c '??' $tmpdir/acctmp.log`
diff -Nru wims-3.62/coqweb.diff wims-3.62/coqweb.diff
--- wims-3.62/coqweb.diff 1970-01-01 01:00:00.0 +0100
+++ wims-3.62/coqweb.diff 2008-10-12 21:21:57.0 +0100
@@ -0,0 +1,19 @@
+--- coqweb.orig2008-08-24 22:57:20.0 +0200
coqweb 2008-08-24 22:59:49.0 +0200
+@@ -18,10 +18,12 @@
+ if [ "$w_croq6_dbg_level" == "1" ];then
+ echo "[coqweb] called with $* ;;"
+ echo "env start "
+- env >/tmp/env$$
+- sed "s/$//" /tmp/sed$$
+- cat /tmp/sed$$
+- rm /tmp/env$$ /tmp/sed$$
++ envfile=$(mktemp -t env.XX)
++ sedfile=$(mktemp -t sed.XX)
++ env > $envfile
++ sed "s/$//" < $envfile > $sedfile
++ cat $sedfile
++ rm $envfile $sedfile
+ echo "env end"
+ echo "coqweb start "
+ fi
diff -Nru wims-3.62/debian/changelog wims-3.62/debian/changelog
--- wims-3.62/debian/changelog 2008-10-12 21:21:56.0 +0100
+++ wims-3.62/debian/changelog 2008-10-12 21:21:57.0 +0100
@@ -1,3 +1,12 @@
+wims (3.62-13.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Prevent against the possibility of an attack with the help of symlinks by
+patching public_html/bin/coqweb and bin/accounts.sh. Patches (and patch
+system) by the regular maintainer. (Closes: #496387)
+
+ -- Chris Lamb <[EMAIL PROTECTED]> Sun, 12 Oct 2008 21:06:10 +0100
+
wims (3.62-13) unstable; urgency=low
* reverted the dependency on octave3.0 (the dependency on octave
diff -Nru wims-3.62/Makefile wims-3.62/Makefile
--- wims-3.62/Makefile 2008-10-12 21:21:56.0 +0100
+++ wims-3.62/Makefile 2008-10-12 21:21:57.0 +0100
@@ -180,6 +180,10 @@
cd $${moddir}; \
done
+patch-for-tmpfile-issues:
+ cd wims/public_html/bin; patch < ../../../coqweb.diff
+ cd wims/bin; patch < ../../account.sh.diff
+
clean-precompiled:
# remove any precompiled file. The bugs must be reported to Gang XIAO
for f in $$(find wims/src -type f -perm 755); do \
@@ -198,6 +202,7 @@
find wims -name ".DS*" -exec rm -f {} \;
patch-and-clean: patch-sources patch-module-manage patch-for-i18n \
+patch-for-tmpfile-issues \
clean-precompiled clean-macos
compile:
signature.asc
Description: PGP signature
Processed: tagging 498516
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 498516 + pending Bug#498516: libc6: should conflict with nscd < 2.8 There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502032: FTBFS: cast from ... to ... increases required alignment of target type
Package: xorp Version: 1.5-4 Severity: serious xorp don't build because of a g++ error: cc1plus: warnings being treated as errors io_link_pcap.cc: In member function 'int IoLinkPcap::join_leave_multicast_group(bool, const Mac&, std::string&)': io_link_pcap.cc:419: warning: cast from 'uint8_t*' to 'ifreq*' increases required alignment of target type The affected archs are: alpha arm armel hppa ia64 mips mipsel sparc The known non affected archs are: i386, amd64, powerpc, s390 Jose Calhariz -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-6-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501152: binary firmware in drivers/net/starfire_firmware.h
You could use this patch and firmware format instead: http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=6963b36bfb1f171ae8ea4884e239bdccc5f47266 Ben. signature.asc Description: This is a digitally signed message part
Processed: tagging 494009
Processing commands for [EMAIL PROTECTED]: > tags 494009 patch Bug#494009: binary firmware in drivers/char/drm/radeon_microcode.h Tags were: help Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498631: binary firmware in drivers/net/cassini.h
You could use this patch and firmware format instead: http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=5263b94d83666854240d254852dd44309c436e25 Ben. signature.asc Description: This is a digitally signed message part
Bug#501153: binary firmware in drivers/net/tehuti_fw.h
You could use this similar patch instead: http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=e41f3e5f8c5110871e376a2566b8eea2932b813b Ben. signature.asc Description: This is a digitally signed message part
Processed: tagging 494468
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 494468 + pending Bug#494468: Postinst violates Debian policy (10.7.3) by not preserving changes to /etc/locale.gen Tags were: pending Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494009: binary firmware in drivers/char/drm/radeon_microcode.h
However, you should probably use this patch and firmware format instead: http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=3a911a216742e4ab998f3281409d46a62f252716 Ben. signature.asc Description: This is a digitally signed message part
Bug#501152: binary firmware in drivers/net/starfire_firmware.h
Here's a patch for starfire to make it use request_firmware. This is
compile-tested only. The firmware files can be produced by writing out
the firmware_rx and firmware_tx arrays as 32-bit little-endian values.
However, the licence remains a problem.
Ben.
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index 4a12477..3e433cb 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -1306,6 +1306,7 @@ config ADAPTEC_STARFIRE
depends on NET_PCI && PCI
select CRC32
select MII
+ select FW_LOADER
help
Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
adapter. The DuraLAN chip is used on the 64 bit PCI boards from
diff --git a/drivers/net/starfire.c b/drivers/net/starfire.c
index 7b7b171..73394d9 100644
--- a/drivers/net/starfire.c
+++ b/drivers/net/starfire.c
@@ -42,11 +42,11 @@
#include
#include
#include
+#include
#include /* Processor type for cache alignment.
*/
#include
#include
-#include "starfire_firmware.h"
/*
* The current frame processor firmware fails to checksum a fragment
* of length 1. If and when this is fixed, the #define below can be removed.
@@ -224,6 +224,8 @@ MODULE_AUTHOR("Donald Becker <[EMAIL PROTECTED]>");
MODULE_DESCRIPTION("Adaptec Starfire Ethernet driver");
MODULE_LICENSE("GPL");
MODULE_VERSION(DRV_VERSION);
+MODULE_FIRMWARE("starfire/gfp_rx.bin");
+MODULE_FIRMWARE("starfire/gfp_tx.bin");
module_param(max_interrupt_work, int, 0);
module_param(mtu, int, 0);
@@ -948,12 +950,21 @@ static int netdev_open(struct net_device *dev)
void __iomem *ioaddr = np->base;
int i, retval;
size_t tx_done_q_size, rx_done_q_size, tx_ring_size, rx_ring_size;
+ const struct firmware *fw_rx, *fw_tx;
+ const __le32 *fw_data;
/* Do we ever need to reset the chip??? */
- retval = request_irq(dev->irq, &intr_handler, IRQF_SHARED, dev->name,
dev);
+ retval = request_firmware(&fw_rx, "starfire/gfp_rx.bin",
&np->pci_dev->dev);
if (retval)
return retval;
+ retval = request_firmware(&fw_tx, "starfire/gfp_tx.bin",
&np->pci_dev->dev);
+ if (retval)
+ goto out_release_fw_rx;
+
+ retval = request_irq(dev->irq, &intr_handler, IRQF_SHARED, dev->name,
dev);
+ if (retval)
+ goto out_release_fw_tx;
/* Disable the Rx and Tx, and reset the chip. */
writel(0, ioaddr + GenCtrl);
@@ -1084,10 +1095,12 @@ static int netdev_open(struct net_device *dev)
#endif /* VLAN_SUPPORT */
/* Load Rx/Tx firmware into the frame processors */
- for (i = 0; i < FIRMWARE_RX_SIZE * 2; i++)
- writel(firmware_rx[i], ioaddr + RxGfpMem + i * 4);
- for (i = 0; i < FIRMWARE_TX_SIZE * 2; i++)
- writel(firmware_tx[i], ioaddr + TxGfpMem + i * 4);
+ fw_data = (const __le32 *)fw_rx->data;
+ for (i = 0; i < fw_rx->size / 4; i++)
+ writel(le32_to_cpu(fw_data[i]), ioaddr + RxGfpMem + i * 4);
+ fw_data = (const __le32 *)fw_tx->data;
+ for (i = 0; i < fw_tx->size / 4; i++)
+ writel(le32_to_cpu(fw_data[i]), ioaddr + TxGfpMem + i * 4);
if (enable_hw_cksum)
/* Enable the Rx and Tx units, and the Rx/Tx frame processors.
*/
writel(TxEnable|TxGFPEnable|RxEnable|RxGFPEnable, ioaddr +
GenCtrl);
@@ -1099,7 +1112,11 @@ static int netdev_open(struct net_device *dev)
printk(KERN_DEBUG "%s: Done netdev_open().\n",
dev->name);
- return 0;
+out_release_fw_tx:
+ release_firmware(fw_tx);
+out_release_fw_rx:
+ release_firmware(fw_rx);
+ return retval;
}
--- END ---
signature.asc
Description: This is a digitally signed message part
Bug#501153: binary firmware in drivers/net/tehuti_fw.h
Here's a patch for tehuti to make it use request_firmware. This is
compile-tested only. The firmware file can be produced by writing out
the array s_loadFirm as 32-bit little-endian values. However, the
licence remains a problem.
Ben.
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index 3e433cb..9e1a73c 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -2569,6 +2569,7 @@ config MLX4_DEBUG
config TEHUTI
tristate "Tehuti Networks 10G Ethernet"
depends on PCI
+ select FW_LOADER
help
Tehuti Networks 10G Ethernet NIC
diff --git a/drivers/net/tehuti.c b/drivers/net/tehuti.c
index 432e837..3f732eb 100644
--- a/drivers/net/tehuti.c
+++ b/drivers/net/tehuti.c
@@ -63,7 +63,6 @@
*/
#include "tehuti.h"
-#include "tehuti_fw.h"
static struct pci_device_id __devinitdata bdx_pci_tbl[] = {
{0x1FC9, 0x3009, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
@@ -319,28 +318,41 @@ static int bdx_poll(struct napi_struct *napi, int budget)
static int bdx_fw_load(struct bdx_priv *priv)
{
+ const struct firmware *fw = NULL;
int master, i;
+ int rc;
ENTER;
master = READ_REG(priv, regINIT_SEMAPHORE);
if (!READ_REG(priv, regINIT_STATUS) && master) {
- bdx_tx_push_desc_safe(priv, s_firmLoad, sizeof(s_firmLoad));
+ rc = request_firmware(&fw, "tehuti/firmware.bin",
&priv->pdev->dev);
+ if (rc)
+ goto out;
+ bdx_tx_push_desc_safe(priv, fw->data, fw->size);
mdelay(100);
}
for (i = 0; i < 200; i++) {
- if (READ_REG(priv, regINIT_STATUS))
- break;
+ if (READ_REG(priv, regINIT_STATUS)) {
+ rc = 0;
+ goto out;
+ }
mdelay(2);
}
+ rc = -EIO;
+out:
+ if (fw)
+ release_firmware(fw);
if (master)
WRITE_REG(priv, regINIT_SEMAPHORE, 1);
- if (i == 200) {
+ if (rc) {
ERR("%s: firmware loading failed\n", priv->ndev->name);
- DBG("VPC = 0x%x VIC = 0x%x INIT_STATUS = 0x%x i=%d\n",
- READ_REG(priv, regVPC),
- READ_REG(priv, regVIC), READ_REG(priv, regINIT_STATUS), i);
- RET(-EIO);
+ if (rc == -EIO)
+ DBG("VPC = 0x%x VIC = 0x%x INIT_STATUS = 0x%x i=%d\n",
+ READ_REG(priv, regVPC),
+ READ_REG(priv, regVIC),
+ READ_REG(priv, regINIT_STATUS), i);
+ RET(rc);
} else {
DBG("%s: firmware loading success\n", priv->ndev->name);
RET(0);
@@ -618,13 +630,6 @@ err:
RET(rc);
}
-static void __init bdx_firmware_endianess(void)
-{
- int i;
- for (i = 0; i < ARRAY_SIZE(s_firmLoad); i++)
- s_firmLoad[i] = CPU_CHIP_SWAP32(s_firmLoad[i]);
-}
-
static int bdx_range_check(struct bdx_priv *priv, u32 offset)
{
return (offset > (u32) (BDX_REGS_SIZE / priv->nic->port_num)) ?
@@ -2498,7 +2503,6 @@ static void __init print_driver_id(void)
static int __init bdx_module_init(void)
{
ENTER;
- bdx_firmware_endianess();
init_txd_sizes();
print_driver_id();
RET(pci_register_driver(&bdx_pci_driver));
@@ -2518,3 +2522,4 @@ module_exit(bdx_module_exit);
MODULE_LICENSE("GPL");
MODULE_AUTHOR(DRIVER_AUTHOR);
MODULE_DESCRIPTION(BDX_DRV_DESC);
+MODULE_FIRMWARE("tehuti/firmware.bin");
diff --git a/drivers/net/tehuti.h b/drivers/net/tehuti.h
index efd170f..b9acb3f 100644
--- a/drivers/net/tehuti.h
+++ b/drivers/net/tehuti.h
@@ -30,6 +30,7 @@
#include
#include
#include
+#include
#include
/* Compile Time Switches */
--- END ---
signature.asc
Description: This is a digitally signed message part
Bug#494010: Source for dsp56k firmware
On Sun, Oct 12, 2008 at 08:10:53PM +0100, Ben Hutchings wrote: > Here is the assembly-language source for the firmware, licenced under > GPLv2. Very nice! Where did you find it? > Adding this to the kernel source package should fix this bug. Actually, it should be assembled and used. AFAICT this is for an m68k processor. I suppose we have a command to assemble this code in binutils-multiarch or so? -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494009: binary firmware in drivers/char/drm/radeon_microcode.h
Here's a patch to radeon to make it use request_firmware. This is
compile-tested only, but I have hardware I can test on shortly. The
firmware files can be produced by writing the arrays as 32-bit
little-endian values. They should be suitable for inclusion in
firmware-nonfree, so I am including a patch for that as well.
Ben.
diff --git a/drivers/char/drm/Kconfig b/drivers/char/drm/Kconfig
index ea26dfd..17edd8a 100644
--- a/drivers/char/drm/Kconfig
+++ b/drivers/char/drm/Kconfig
@@ -35,6 +35,7 @@ config DRM_R128
config DRM_RADEON
tristate "ATI Radeon"
depends on DRM && PCI
+ select FW_LOADER
help
Choose this option if you have an ATI Radeon graphics card. There
are both PCI and AGP versions. You don't need to choose this to
diff --git a/drivers/char/drm/radeon_cp.c b/drivers/char/drm/radeon_cp.c
index e53158f..8408e34 100644
--- a/drivers/char/drm/radeon_cp.c
+++ b/drivers/char/drm/radeon_cp.c
@@ -29,14 +29,14 @@
*Gareth Hughes <[EMAIL PROTECTED]>
*/
+#include
+
#include "drmP.h"
#include "drm.h"
#include "radeon_drm.h"
#include "radeon_drv.h"
#include "r300_reg.h"
-#include "radeon_microcode.h"
-
#define RADEON_FIFO_DEBUG 0
static int radeon_do_cleanup_cp(struct drm_device * dev);
@@ -319,83 +319,71 @@ static void radeon_init_pipes(drm_radeon_private_t
*dev_priv)
* CP control, initialization
*/
+static const char *radeon_cp_family_name(drm_radeon_private_t * dev_priv)
+{
+ switch (dev_priv->flags & RADEON_FAMILY_MASK) {
+ case CHIP_R100: case CHIP_RV100: case CHIP_RV200: case CHIP_RS100:
+ case CHIP_RS200:
+ return "R100";
+ case CHIP_R200: case CHIP_RV250: case CHIP_RV280: case CHIP_RS300:
+ return "R200";
+ case CHIP_R300: case CHIP_R350: case CHIP_RV350: case CHIP_RV380:
+ case CHIP_RS480:
+ return "R300";
+ case CHIP_R420: case CHIP_RV410:
+ return "R400";
+ case CHIP_RS690:
+ return "RS690";
+ case CHIP_RV515: case CHIP_R520: case CHIP_RV530: case CHIP_R580:
+ case CHIP_RV560: case CHIP_RV570:
+ return "R500";
+ default:
+ WARN_ON(1); /* new chip needs a name */
+ return "";
+ }
+}
+
/* Load the microcode for the CP */
static void radeon_cp_load_microcode(drm_radeon_private_t * dev_priv)
{
+ const __le32 *microcode;
int i;
DRM_DEBUG("\n");
radeon_do_wait_for_idle(dev_priv);
+ DRM_INFO("Loading %s Microcode\n", radeon_cp_family_name(dev_priv));
+ microcode = (const __le32 *)dev_priv->microcode->data;
RADEON_WRITE(RADEON_CP_ME_RAM_ADDR, 0);
- if (((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R100) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV100) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV200) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RS100) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RS200)) {
- DRM_INFO("Loading R100 Microcode\n");
- for (i = 0; i < 256; i++) {
- RADEON_WRITE(RADEON_CP_ME_RAM_DATAH,
-R100_cp_microcode[i][1]);
- RADEON_WRITE(RADEON_CP_ME_RAM_DATAL,
-R100_cp_microcode[i][0]);
- }
- } else if (((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R200) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV250) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV280) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RS300)) {
- DRM_INFO("Loading R200 Microcode\n");
- for (i = 0; i < 256; i++) {
- RADEON_WRITE(RADEON_CP_ME_RAM_DATAH,
-R200_cp_microcode[i][1]);
- RADEON_WRITE(RADEON_CP_ME_RAM_DATAL,
-R200_cp_microcode[i][0]);
- }
- } else if (((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R300) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R350) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV350) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV380) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RS480)) {
- DRM_INFO("Loading R300 Microcode\n");
- for (i = 0; i < 256; i++) {
- RADEON_WRITE(RADEON_CP_ME_RAM_DATAH,
-R300_cp_microcode[i][1]);
- RADEON_WRITE(RADEON_CP_ME_RAM_DATAL,
-R300_cp_microcode[i][0]);
- }
- } else if (((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R420) ||
- ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV410
Bug#494007: binary firmware in drivers/char/drm/r128_cce.c
Here's a patch to make r128 use request_firmware. This is
compile-tested only as I don't have appropriate hardware. The firmware
file can be produced by writing the array as 32-bit little-endian
values. However, there is still a problem with its licence.
Ben.
diff --git a/drivers/char/drm/Kconfig b/drivers/char/drm/Kconfig
index 610d6fd..ea26dfd 100644
--- a/drivers/char/drm/Kconfig
+++ b/drivers/char/drm/Kconfig
@@ -26,6 +26,7 @@ config DRM_TDFX
config DRM_R128
tristate "ATI Rage 128"
depends on DRM && PCI
+ select FW_LOADER
help
Choose this option if you have an ATI Rage 128 graphics card. If M
is selected, the module will be called r128. AGP support for
diff --git a/drivers/char/drm/r128_cce.c b/drivers/char/drm/r128_cce.c
index c31afbd..e29c082 100644
--- a/drivers/char/drm/r128_cce.c
+++ b/drivers/char/drm/r128_cce.c
@@ -29,6 +29,8 @@
*Gareth Hughes <[EMAIL PROTECTED]>
*/
+#include
+
#include "drmP.h"
#include "drm.h"
#include "r128_drm.h"
@@ -36,51 +38,6 @@
#define R128_FIFO_DEBUG0
-/* CCE microcode (from ATI) */
-static u32 r128_cce_microcode[] = {
- 0, 276838400, 0, 268449792, 2, 142, 2, 145, 0, 1076765731, 0,
- 1617039951, 0, 774592877, 0, 1987540286, 0, 2307490946U, 0,
- 599558925, 0, 589505315, 0, 596487092, 0, 589505315, 1,
- 11544576, 1, 206848, 1, 311296, 1, 198656, 2, 912273422, 11,
- 262144, 0, 0, 1, 33559837, 1, 7438, 1, 14809, 1, 6615, 12, 28,
- 1, 6614, 12, 28, 2, 23, 11, 18874368, 0, 16790922, 1, 409600, 9,
- 30, 1, 147854772, 16, 420483072, 3, 8192, 0, 10240, 1, 198656,
- 1, 15630, 1, 51200, 10, 34858, 9, 42, 1, 33559823, 2, 10276, 1,
- 15717, 1, 15718, 2, 43, 1, 15936948, 1, 570480831, 1, 14715071,
- 12, 322123831, 1, 33953125, 12, 55, 1, 33559908, 1, 15718, 2,
- 46, 4, 2099258, 1, 526336, 1, 442623, 4, 4194365, 1, 509952, 1,
- 459007, 3, 0, 12, 92, 2, 46, 12, 176, 1, 15734, 1, 206848, 1,
- 18432, 1, 133120, 1, 100670734, 1, 149504, 1, 165888, 1,
- 15975928, 1, 1048576, 6, 3145806, 1, 15715, 16, 2150645232U, 2,
- 268449859, 2, 10307, 12, 176, 1, 15734, 1, 15735, 1, 15630, 1,
- 15631, 1, 5253120, 6, 3145810, 16, 2150645232U, 1, 15864, 2, 82,
- 1, 343310, 1, 1064207, 2, 3145813, 1, 15728, 1, 7817, 1, 15729,
- 3, 15730, 12, 92, 2, 98, 1, 16168, 1, 16167, 1, 16002, 1, 16008,
- 1, 15974, 1, 15975, 1, 15990, 1, 15976, 1, 15977, 1, 15980, 0,
- 15981, 1, 10240, 1, 5253120, 1, 15720, 1, 198656, 6, 110, 1,
- 180224, 1, 103824738, 2, 112, 2, 3145839, 0, 536885440, 1,
- 114880, 14, 125, 12, 206975, 1, 33559995, 12, 198784, 0,
- 33570236, 1, 15803, 0, 15804, 3, 294912, 1, 294912, 3, 442370,
- 1, 11544576, 0, 811612160, 1, 12593152, 1, 11536384, 1,
- 14024704, 7, 310382726, 0, 10240, 1, 14796, 1, 14797, 1, 14793,
- 1, 14794, 0, 14795, 1, 268679168, 1, 9437184, 1, 268449792, 1,
- 198656, 1, 9452827, 1, 1075854602, 1, 1075854603, 1, 557056, 1,
- 114880, 14, 159, 12, 198784, 1, 1109409213, 12, 198783, 1,
- 1107312059, 12, 198784, 1, 1109409212, 2, 162, 1, 1075854781, 1,
- 1073757627, 1, 1075854780, 1, 540672, 1, 10485760, 6, 3145894,
- 16, 274741248, 9, 168, 3, 4194304, 3, 4209949, 0, 0, 0, 256, 14,
- 174, 1, 114857, 1, 33560007, 12, 176, 0, 10240, 1, 114858, 1,
- 33560018, 1, 114857, 3, 33560007, 1, 16008, 1, 114874, 1,
- 33560360, 1, 114875, 1, 33560154, 0, 15963, 0, 256, 0, 4096, 1,
- 409611, 9, 188, 0, 10240, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
-};
-
static int R128_READ_PLL(struct drm_device * dev, int addr)
{
drm_r128_private_t *dev_priv = dev->dev_private;
@@ -176,20 +133,36 @@ static int r128_do_wait_for_idle(drm_r128_private_t *
dev_priv)
*/
/* Load the microcode for the CCE */
-static void r128_cce_load_microcode(drm_r128_private_t * dev_priv)
+static int
+r128_cce_load_microcode(struct drm_device *dev, drm_r128_private_t *dev_priv)
{
- int i;
+ const struct firmware *fw;
+ const __le32 *microcode;
+ int rc, i;
#
DRM_DEBUG("\n");
+ rc = request_firmware(&fw, "r128/cce_ucode.bin", &dev->pdev->dev);
+ if (rc)
+ return rc;
+ if (fw->size != 256 * 8) {
+ release_firmware(fw);
+ return -EINVAL;
+ }
+ microcode = (const __le32 *)fw->data;
+
r128_do_wait_for_idle(dev_priv);
R128_WRITE(R128_PM4_MICROCODE_ADDR, 0);
for (i = 0; i < 256; i++) {
- R128
Bug#501618: marked as done (matplotlib will FTBFS on alpha, hppa, mips, mipsel, sparc)
Your message dated Sun, 12 Oct 2008 19:38:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#501618: fixed in matplotlib 0.98.3-4
has caused the Debian Bug report #501618,
regarding matplotlib will FTBFS on alpha, hppa, mips, mipsel, sparc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
501618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501618
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: matplotlib
Version: 0.98.3-3
Severity: serious
Tags: patch
Matplotlib FTBFS due to a recent change in the platform identifier
for alpha, hppa, mips, mipsel and sparc. The attached patch is an
update to debian/patches/build_fix.patch which fixes the problem.
Thiemo
Index: matplotlib-0.98.3/setupext.py
===
--- matplotlib-0.98.3.orig/setupext.py 2008-10-08 23:30:35.0 +
+++ matplotlib-0.98.3/setupext.py 2008-10-08 23:31:19.0 +
@@ -47,8 +47,12 @@
basedir = {
'win32' : ['win32_static',],
-'linux2' : ['/usr/local', '/usr'],
-'linux' : ['/usr/local', '/usr',],
+'linux2-alpha' : ['/usr'],
+'linux2-hppa' : ['/usr'],
+'linux2-mips' : ['/usr'],
+'linux2-sparc' : ['/usr'],
+'linux2' : ['/usr'],
+'linux' : ['/usr',],
'cygwin' : ['/usr/local', '/usr',],
'darwin' : ['/sw/lib/freetype2', '/sw/lib/freetype219', '/usr/local',
'/usr', '/sw', '/usr/X11R6'],
@@ -56,8 +60,10 @@
'freebsd5' : ['/usr/local', '/usr'],
'freebsd6' : ['/usr/local', '/usr'],
'sunos5' : [os.getenv('MPLIB_BASE') or '/usr/local',],
-'gnukfreebsd5' : ['/usr/local', '/usr'],
-'gnukfreebsd6' : ['/usr/local', '/usr'],
+'gnukfreebsd5' : ['/usr'],
+'gnukfreebsd6' : ['/usr'],
+'gnukfreebsd7' : ['/usr'],
+'gnukfreebsd8' : ['/usr'],
'aix5' : ['/usr/local'],
}
@@ -977,6 +983,10 @@
tk_inc = os.path.normpath(os.path.join(tk_lib_dir,
'../../include'))
+if not os.path.exists(tk_inc):
+tk_inc = os.path.normpath(os.path.join(tk_lib_dir,
+ '../../../include/tcl' + tk_ver))
+
if not os.path.exists(os.path.join(tk_inc, 'tk.h')):
tk_inc = tcl_inc
@@ -994,10 +1004,10 @@
return tcl_lib, tcl_inc, tk_lib, tk_inc
def hardcoded_tcl_config():
-tcl_inc = "/usr/local/include"
-tk_inc = "/usr/local/include"
-tcl_lib = "/usr/local/lib"
-tk_lib = "/usr/local/lib"
+tcl_inc = "/usr/include/tcl8.4"
+tk_inc = "/usr/include/tcl8.4"
+tcl_lib = "/usr/lib"
+tk_lib = "/usr/lib"
return tcl_lib, tcl_inc, tk_lib, tk_inc
def add_tk_flags(module):
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 0.98.3-4
We believe that the bug you reported is fixed in the latest version of
matplotlib, which is due to be installed in the Debian FTP archive:
matplotlib_0.98.3-4.diff.gz
to pool/main/m/matplotlib/matplotlib_0.98.3-4.diff.gz
matplotlib_0.98.3-4.dsc
to pool/main/m/matplotlib/matplotlib_0.98.3-4.dsc
python-matplotlib-data_0.98.3-4_all.deb
to pool/main/m/matplotlib/python-matplotlib-data_0.98.3-4_all.deb
python-matplotlib-dbg_0.98.3-4_amd64.deb
to pool/main/m/matplotlib/python-matplotlib-dbg_0.98.3-4_amd64.deb
python-matplotlib-doc_0.98.3-4_all.deb
to pool/main/m/matplotlib/python-matplotlib-doc_0.98.3-4_all.deb
python-matplotlib_0.98.3-4_amd64.deb
to pool/main/m/matplotlib/python-matplotlib_0.98.3-4_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi <[EMAIL PROTECTED]> (supplier of updated matplotlib package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 25 Aug 2008 23:28:30 +0200
Source: matplotlib
Binary: python-matplotlib python-matplotlib-data python-matplotlib-doc
python-matplotlib-dbg
Architecture: source all amd64
Version: 0.98.3-4
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team <[EMAIL PROTECTED]>
Changed-By: Sandro Tosi <[EMAIL PROTECTED]>
Description:
python-matplotlib - Python based plotting system in a style similar
Processed: jasper: diff for NMU version 1.900.1-5.1
Processing commands for [EMAIL PROTECTED]: > tags 501021 + patch Bug#501021: jasper: CVE-2008-352[0-2] multiple integer overflows in jas_alloc calls Tags were: patch security Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501600: marked as done (libgammu4-dbg: tris to overwrite file owned by libgammu3-dbg)
Your message dated Sun, 12 Oct 2008 19:36:41 + with message-id <[EMAIL PROTECTED]> and subject line Bug#501600: fixed in gammu 1.21.0-2 has caused the Debian Bug report #501600, regarding libgammu4-dbg: tris to overwrite file owned by libgammu3-dbg to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 501600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501600 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libgammu4-dbg Version: 1.21.0-1 Severity: serious 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: Date: 2008-10-06 Architecture: amd64 Distribution: sid Command: apt-get --assume-yes --allow-unauthenticated install libgammu3-dbg libgammu4-dbg Reading package lists... Building dependency tree... The following extra packages will be installed: libbluetooth2 libgammu-common libgammu3 libgammu4 Suggested packages: gammu The following NEW packages will be installed: libbluetooth2 libgammu-common libgammu3 libgammu3-dbg libgammu4 libgammu4-dbg 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 3454kB of archives. After this operation, 9388kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libbluetooth2 libgammu-common libgammu3 libgammu4 libgammu3-dbg libgammu4-dbg Authentication warning overridden. Get:1 http://localhost sid/main libbluetooth2 3.36-1 [49.4kB] Get:2 http://localhost sid/main libgammu-common 1.21.0-1 [148kB] Get:3 http://localhost sid/main libgammu3 1.20.0-1 [462kB] Get:4 http://localhost sid/main libgammu4 1.21.0-1 [476kB] Get:5 http://localhost sid/main libgammu3-dbg 1.20.0-1 [1135kB] Get:6 http://localhost sid/main libgammu4-dbg 1.21.0-1 [1184kB] Fetched 3454kB in 5s (593kB/s) Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libbluetooth2. (Reading database ... 7896 files and directories currently installed.) Unpacking libbluetooth2 (from .../libbluetooth2_3.36-1_amd64.deb) ... Selecting previously deselected package libgammu-common. Unpacking libgammu-common (from .../libgammu-common_1.21.0-1_all.deb) ... Selecting previously deselected package libgammu3. Unpacking libgammu3 (from .../libgammu3_1.20.0-1_amd64.deb) ... Selecting previously deselected package libgammu4. Unpacking libgammu4 (from .../libgammu4_1.21.0-1_amd64.deb) ... Selecting previously deselected package libgammu3-dbg. Unpacking libgammu3-dbg (from .../libgammu3-dbg_1.20.0-1_amd64.deb) ... Selecting previously deselected package libgammu4-dbg. Unpacking libgammu4-dbg (from .../libgammu4-dbg_1.21.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libgammu4-dbg_1.21.0-1_amd64.deb (--unpack): trying to overwrite `/usr/lib/debug/usr/bin/gammu', which is also in package libgammu3-dbg dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libgammu4-dbg_1.21.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File diversions or a Replace relation are another possibility. This bug will be assigned to both packages. -Ralf. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Source: gammu Source-Version: 1.21.0-2 We believe that the bug you reported is fixed in the latest version of gammu, which is due to be installed in the Debian FTP archive: gammu_1.21.0-2.diff.gz to pool/main/g/gammu/gammu_1.21.0-2.diff.gz gammu_1.21.0-2.dsc to pool/main/g/gammu/gammu_1.21.0-2.dsc gammu_1.21.0-2_i386.deb to pool/main/g/gammu/gammu_1.21.0-2_i386.deb libgammu-common_1.21.0-2_all.deb to pool/main/g/gammu/libgammu-common_1.21.0-2_all.deb libgammu-dbg_1.21.0-2_i386.deb to pool/main/g/gammu/libgammu-dbg_1.21.0-2_i386.deb libgammu-dev_1.21.0-2_i386.deb to pool/main/g/gammu/libgammu-dev_1.21.0-2_i386.deb libgammu4_1.21.0-2_i386.deb to pool/main/g/gammu/libgammu4_1.21.
Bug#501021: jasper: diff for NMU version 1.900.1-5.1
tags 501021 + patch
thanks
Dear maintainer,
I've prepared an NMU for jasper (versioned as 1.900.1-5.1) and uploaded it
to DELAYED/02.
PS: for some reason the previous nmudiff was broken, here is the proper one.
Regards.
reverted:
--- jasper-1.900.1/src/libjasper/jpc/jpc_cs.c
+++ jasper-1.900.1.orig/src/libjasper/jpc/jpc_cs.c
@@ -982,10 +982,7 @@
compparms->numstepsizes = (len - n) / 2;
break;
}
+ if (compparms->numstepsizes > 0) {
- if (compparms->numstepsizes > 3 * JPC_MAXRLVLS + 1) {
- jpc_qcx_destroycompparms(compparms);
-return -1;
-} else if (compparms->numstepsizes > 0) {
compparms->stepsizes = jas_malloc(compparms->numstepsizes *
sizeof(uint_fast16_t));
assert(compparms->stepsizes);
reverted:
--- jasper-1.900.1/src/libjasper/jpc/jpc_dec.c
+++ jasper-1.900.1.orig/src/libjasper/jpc/jpc_dec.c
@@ -1069,12 +1069,12 @@
/* Apply an inverse intercomponent transform if necessary. */
switch (tile->cp->mctid) {
case JPC_MCT_RCT:
+ assert(dec->numcomps == 3);
- assert(dec->numcomps == 3 || dec->numcomps == 4);
jpc_irct(tile->tcomps[0].data, tile->tcomps[1].data,
tile->tcomps[2].data);
break;
case JPC_MCT_ICT:
+ assert(dec->numcomps == 3);
- assert(dec->numcomps == 3 || dec->numcomps == 4);
jpc_iict(tile->tcomps[0].data, tile->tcomps[1].data,
tile->tcomps[2].data);
break;
diff -u jasper-1.900.1/debian/changelog jasper-1.900.1/debian/changelog
--- jasper-1.900.1/debian/changelog
+++ jasper-1.900.1/debian/changelog
@@ -1,3 +1,13 @@
+jasper (1.900.1-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * add patches/02_security.dpatch to fix various CVEs (Closes: #501021):
+ + CVE-2008-3522[0]: Buffer overflow.
+ + CVE-2008-3521[1]: unsecure temporary files handling.
+ + CVE-2008-3520[2]: Multiple integer overflows.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]> Sun, 12 Oct 2008 21:40:59 +0200
+
jasper (1.900.1-5) unstable; urgency=low
* Added GeoJP2 patch by Sven Geggus <[EMAIL PROTECTED]>
diff -u jasper-1.900.1/debian/patches/00list
jasper-1.900.1/debian/patches/00list
--- jasper-1.900.1/debian/patches/00list
+++ jasper-1.900.1/debian/patches/00list
@@ -1,0 +2 @@
+02_security.dpatch
only in patch2:
unchanged:
--- jasper-1.900.1.orig/debian/patches/02_security.dpatch
+++ jasper-1.900.1/debian/patches/02_security.dpatch
@@ -0,0 +1,978 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+##
+## All lines beginning with `## DP:' are a description of the patch.
+
[EMAIL PROTECTED]@
+
+diff --git a/src/libjasper/base/jas_cm.c b/src/libjasper/base/jas_cm.c
+index 77514dd..e63a6d2 100644
+--- a/src/libjasper/base/jas_cm.c
b/src/libjasper/base/jas_cm.c
+@@ -704,8 +704,7 @@ static int jas_cmpxformseq_resize(jas_cmpxformseq_t
*pxformseq, int n)
+ {
+ jas_cmpxform_t **p;
+ assert(n >= pxformseq->numpxforms);
+- p = (!pxformseq->pxforms) ? jas_malloc(n * sizeof(jas_cmpxform_t *)) :
+-jas_realloc(pxformseq->pxforms, n * sizeof(jas_cmpxform_t *));
++ p = jas_realloc2(pxformseq->pxforms, n, sizeof(jas_cmpxform_t *));
+ if (!p) {
+ return -1;
+ }
+@@ -889,13 +888,13 @@ static int jas_cmshapmatlut_set(jas_cmshapmatlut_t *lut,
jas_icccurv_t *curv)
+ jas_cmshapmatlut_cleanup(lut);
+ if (curv->numents == 0) {
+ lut->size = 2;
+- if (!(lut->data = jas_malloc(lut->size * sizeof(jas_cmreal_t
++ if (!(lut->data = jas_alloc2(lut->size, sizeof(jas_cmreal_t
+ goto error;
+ lut->data[0] = 0.0;
+ lut->data[1] = 1.0;
+ } else if (curv->numents == 1) {
+ lut->size = 256;
+- if (!(lut->data = jas_malloc(lut->size * sizeof(jas_cmreal_t
++ if (!(lut->data = jas_alloc2(lut->size, sizeof(jas_cmreal_t
+ goto error;
+ gamma = curv->ents[0] / 256.0;
+ for (i = 0; i < lut->size; ++i) {
+@@ -903,7 +902,7 @@ static int jas_cmshapmatlut_set(jas_cmshapmatlut_t *lut,
jas_icccurv_t *curv)
+ }
+ } else {
+ lut->size = curv->numents;
+- if (!(lut->data = jas_malloc(lut->size * sizeof(jas_cmreal_t
++ if (!(lut->data = jas_alloc2(lut->size, sizeof(jas_cmreal_t
+ goto error;
+ for (i = 0; i < lut->size; ++i) {
+ lut->data[i] = curv->ents[i] / 65535.0;
+@@ -953,7 +952,7 @@ static int jas_cmshapmatlut_invert(jas_cmshapmatlut_t
*invlut,
+ return -1;
+ }
+ }
+- if (!(invlut->data = jas_malloc(n * sizeof(jas_cmreal_t
++ if (!(invlut->data = jas_alloc2(n, sizeof(jas_cmreal_t
Processed: jasper: diff for NMU version 1.900.1-5.1
Processing commands for [EMAIL PROTECTED]: > tags 501021 + patch Bug#501021: jasper: CVE-2008-352[0-2] multiple integer overflows in jas_alloc calls Tags were: patch security Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501021: jasper: diff for NMU version 1.900.1-5.1
tags 501021 + patch
thanks
Dear maintainer,
I've prepared an NMU for jasper (versioned as 1.900.1-5.1) and uploaded it
to DELAYED/02.
Regards.
diff -u jasper-1.900.1/debian/changelog jasper-1.900.1/debian/changelog
--- jasper-1.900.1/debian/changelog
+++ jasper-1.900.1/debian/changelog
@@ -1,3 +1,13 @@
+jasper (1.900.1-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * add patches/02_security.dpatch to fix various CVEs (Closes: #501021):
+ + CVE-2008-3522[0]: Buffer overflow.
+ + CVE-2008-3521[1]: unsecure temporary files handling.
+ + CVE-2008-3520[2]: Multiple integer overflows.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]> Sun, 12 Oct 2008 21:40:59 +0200
+
jasper (1.900.1-5) unstable; urgency=low
* Added GeoJP2 patch by Sven Geggus <[EMAIL PROTECTED]>
diff -u jasper-1.900.1/debian/patches/00list
jasper-1.900.1/debian/patches/00list
--- jasper-1.900.1/debian/patches/00list
+++ jasper-1.900.1/debian/patches/00list
@@ -1,0 +2 @@
+02_security.dpatch
only in patch2:
unchanged:
--- jasper-1.900.1.orig/debian/patches/02_security.dpatch
+++ jasper-1.900.1/debian/patches/02_security.dpatch
@@ -0,0 +1,983 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+##
+## All lines beginning with `## DP:' are a description of the patch.
+
[EMAIL PROTECTED]@
+
+diff -Nurad jasper-1.900.1.orig/src/libjasper/base/jas_cm.c
jasper-1.900.1.new/src/libjasper/base/jas_cm.c
+--- jasper-1.900.1.orig/src/libjasper/base/jas_cm.c2007-01-19
22:43:05.0 +0100
jasper-1.900.1.new/src/libjasper/base/jas_cm.c 2008-10-03
14:17:55.0 +0200
+@@ -704,8 +704,7 @@
+ {
+ jas_cmpxform_t **p;
+ assert(n >= pxformseq->numpxforms);
+- p = (!pxformseq->pxforms) ? jas_malloc(n * sizeof(jas_cmpxform_t *)) :
+-jas_realloc(pxformseq->pxforms, n * sizeof(jas_cmpxform_t *));
++ p = jas_realloc2(pxformseq->pxforms, n, sizeof(jas_cmpxform_t *));
+ if (!p) {
+ return -1;
+ }
+@@ -889,13 +888,13 @@
+ jas_cmshapmatlut_cleanup(lut);
+ if (curv->numents == 0) {
+ lut->size = 2;
+- if (!(lut->data = jas_malloc(lut->size * sizeof(jas_cmreal_t
++ if (!(lut->data = jas_alloc2(lut->size, sizeof(jas_cmreal_t
+ goto error;
+ lut->data[0] = 0.0;
+ lut->data[1] = 1.0;
+ } else if (curv->numents == 1) {
+ lut->size = 256;
+- if (!(lut->data = jas_malloc(lut->size * sizeof(jas_cmreal_t
++ if (!(lut->data = jas_alloc2(lut->size, sizeof(jas_cmreal_t
+ goto error;
+ gamma = curv->ents[0] / 256.0;
+ for (i = 0; i < lut->size; ++i) {
+@@ -903,7 +902,7 @@
+ }
+ } else {
+ lut->size = curv->numents;
+- if (!(lut->data = jas_malloc(lut->size * sizeof(jas_cmreal_t
++ if (!(lut->data = jas_alloc2(lut->size, sizeof(jas_cmreal_t
+ goto error;
+ for (i = 0; i < lut->size; ++i) {
+ lut->data[i] = curv->ents[i] / 65535.0;
+@@ -953,7 +952,7 @@
+ return -1;
+ }
+ }
+- if (!(invlut->data = jas_malloc(n * sizeof(jas_cmreal_t
++ if (!(invlut->data = jas_alloc2(n, sizeof(jas_cmreal_t
+ return -1;
+ invlut->size = n;
+ for (i = 0; i < invlut->size; ++i) {
+diff -Nurad jasper-1.900.1.orig/src/libjasper/base/jas_icc.c
jasper-1.900.1.new/src/libjasper/base/jas_icc.c
+--- jasper-1.900.1.orig/src/libjasper/base/jas_icc.c 2007-01-19
22:43:05.0 +0100
jasper-1.900.1.new/src/libjasper/base/jas_icc.c2008-10-03
14:17:55.0 +0200
+@@ -373,7 +373,7 @@
+ jas_icctagtab_t *tagtab;
+
+ tagtab = &prof->tagtab;
+- if (!(tagtab->ents = jas_malloc(prof->attrtab->numattrs *
++ if (!(tagtab->ents = jas_alloc2(prof->attrtab->numattrs,
+ sizeof(jas_icctagtabent_t
+ goto error;
+ tagtab->numents = prof->attrtab->numattrs;
+@@ -522,7 +522,7 @@
+ }
+ if (jas_iccgetuint32(in, &tagtab->numents))
+ goto error;
+- if (!(tagtab->ents = jas_malloc(tagtab->numents *
++ if (!(tagtab->ents = jas_alloc2(tagtab->numents,
+ sizeof(jas_icctagtabent_t
+ goto error;
+ tagtabent = tagtab->ents;
+@@ -743,8 +743,7 @@
+ {
+ jas_iccattr_t *newattrs;
+ assert(maxents >= tab->numattrs);
+- newattrs = tab->attrs ? jas_realloc(tab->attrs, maxents *
+-sizeof(jas_iccattr_t)) : jas_malloc(maxents * sizeof(jas_iccattr_t));
++ newattrs = jas_realloc2(tab->attrs, maxents, sizeof(jas_iccattr_t));
+ if (!newattrs)
+ return -1;
+ tab->attrs = newattrs;
+@@ -999,7 +998,7 @@
+
+ if (jas_iccgetuint32(in, &curv->numents))
+ goto error;
+- if (!(curv->ents = jas_malloc(curv->numents * sizeof(jas_iccuint16_
Bug#485846: marked as done (libanculus-sharp: Debian CLI Policy Violation of §3.2.1)
Your message dated Sun, 12 Oct 2008 19:20:39 + with message-id <[EMAIL PROTECTED]> and subject line Bug#485846: fixed in libanculus-sharp 0.3.1-2 has caused the Debian Bug report #485846, regarding libanculus-sharp: Debian CLI Policy Violation of §3.2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 485846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485846 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libanculus-sharp Severity: serious Debian CLI Policy 3.2.1 [0] requires that library packages use "-cil" as suffix and the assembly ABI version (usually first 2 groups, major +minor) must be used in the package name, which the libanculus-sharp package name doesn't reflect. [0] http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html#s-gac-naming-versioning -- Regards, Mirco 'meebey' Bauer PGP-Key ID: 0xEEF946C8 FOSS Developer[EMAIL PROTECTED] http://www.meebey.net/ PEAR Developer[EMAIL PROTECTED] http://pear.php.net/ Debian Developer [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libanculus-sharp Source-Version: 0.3.1-2 We believe that the bug you reported is fixed in the latest version of libanculus-sharp, which is due to be installed in the Debian FTP archive: libanculus-sharp_0.3.1-2.diff.gz to pool/main/liba/libanculus-sharp/libanculus-sharp_0.3.1-2.diff.gz libanculus-sharp_0.3.1-2.dsc to pool/main/liba/libanculus-sharp/libanculus-sharp_0.3.1-2.dsc libanculus0.3-cil_0.3.1-2_all.deb to pool/main/liba/libanculus-sharp/libanculus0.3-cil_0.3.1-2_all.deb monodoc-anculus-manual_0.3.1-2_all.deb to pool/main/liba/libanculus-sharp/monodoc-anculus-manual_0.3.1-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino <[EMAIL PROTECTED]> (supplier of updated libanculus-sharp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 18 Sep 2008 22:48:53 +0200 Source: libanculus-sharp Binary: libanculus0.3-cil monodoc-anculus-manual Architecture: source all Version: 0.3.1-2 Distribution: unstable Urgency: low Maintainer: Debian CLI Libraries Team <[EMAIL PROTECTED]> Changed-By: David Paleino <[EMAIL PROTECTED]> Description: libanculus0.3-cil - utility library for CLI projects monodoc-anculus-manual - compiled XML documentation for libanculus-sharp Closes: 485846 485847 485848 485851 Changes: libanculus-sharp (0.3.1-2) unstable; urgency=low . * debian/control: - using "CLI projects" instead of "C# projects" in the short description (Closes: #485851) - package renamed to libanculus0.3-cil (Closes: #485846) - Standards-Version bumped to 3.8.0 (no changes needed) - maintainer set to Debian CLI Libraries Team + Vcs-* fields updated - moved myself to Uploaders - added Build-Depends on quilt - added monodoc-anculus-manual package + updated debian/rules + added debian/monodoc-anculus-manual.* files - added (and renamed existing ones) debian/libanculus0.3-cil.* files * debian/rules: - using dh_installcligac to late-GAC install libraries (Closes: #485847) - moving .pc files to "versioned" files (Closes: #485848) - updated to support quilt patching system * debian/installcligac added * debian/links added * debian/patches: - 01-fix_pkgconfig_pc.patch added, to fix .pc files pointing to /usr/lib/cli/anculus-sharp-0.3/. * debian/copyright: - packaging copyright updated to GPL-3+ Checksums-Sha1: f49deb84d7c8e8aa48094de72ff5eaa162141a35 1677 libanculus-sharp_0.3.1-2.dsc 3409684f47c4da4ce3f3d0f5e5b667c82f757820 3639 libanculus-sharp_0.3.1-2.diff.gz c7895eb1006db437d23056b9426223e7246b33c7 34338 libanculus0.3-cil_0.3.1-2_all.deb e4a8c21296b3f80873c8c4000178ffeceaf83138 55978 monodoc-anculus-manual_0.3.1-2_all.deb Checksums-Sha256: 03a791277642328b434cb4a15f5a2fea301faeea0eedb0411f7d908ac52260ea 1677 libanculus-sharp_0.3.1-2.dsc a20064670f7faa0da86f7e8fa3050e9f6babe33b0e830459fee536e850e30742 3639 libanculus-sharp_0.3.1-2.diff.gz 7a0f52
Bug#485848: marked as done (libanculus-sharp: Debian CLI Policy Violation of §3.2.4)
Your message dated Sun, 12 Oct 2008 19:20:39 + with message-id <[EMAIL PROTECTED]> and subject line Bug#485848: fixed in libanculus-sharp 0.3.1-2 has caused the Debian Bug report #485848, regarding libanculus-sharp: Debian CLI Policy Violation of §3.2.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 485848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485848 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libanculus-sharp Severity: serious libanculus-sharp ships unversioned pkg-config files, the Debian CLI Policy requires them to be versioned, see: http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html#s-pkg-config-file And suggests to use unversioned symlinks to the latest versioned pkg-config file. -- Regards, Mirco 'meebey' Bauer PGP-Key ID: 0xEEF946C8 FOSS Developer[EMAIL PROTECTED] http://www.meebey.net/ PEAR Developer[EMAIL PROTECTED] http://pear.php.net/ Debian Developer [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libanculus-sharp Source-Version: 0.3.1-2 We believe that the bug you reported is fixed in the latest version of libanculus-sharp, which is due to be installed in the Debian FTP archive: libanculus-sharp_0.3.1-2.diff.gz to pool/main/liba/libanculus-sharp/libanculus-sharp_0.3.1-2.diff.gz libanculus-sharp_0.3.1-2.dsc to pool/main/liba/libanculus-sharp/libanculus-sharp_0.3.1-2.dsc libanculus0.3-cil_0.3.1-2_all.deb to pool/main/liba/libanculus-sharp/libanculus0.3-cil_0.3.1-2_all.deb monodoc-anculus-manual_0.3.1-2_all.deb to pool/main/liba/libanculus-sharp/monodoc-anculus-manual_0.3.1-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino <[EMAIL PROTECTED]> (supplier of updated libanculus-sharp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 18 Sep 2008 22:48:53 +0200 Source: libanculus-sharp Binary: libanculus0.3-cil monodoc-anculus-manual Architecture: source all Version: 0.3.1-2 Distribution: unstable Urgency: low Maintainer: Debian CLI Libraries Team <[EMAIL PROTECTED]> Changed-By: David Paleino <[EMAIL PROTECTED]> Description: libanculus0.3-cil - utility library for CLI projects monodoc-anculus-manual - compiled XML documentation for libanculus-sharp Closes: 485846 485847 485848 485851 Changes: libanculus-sharp (0.3.1-2) unstable; urgency=low . * debian/control: - using "CLI projects" instead of "C# projects" in the short description (Closes: #485851) - package renamed to libanculus0.3-cil (Closes: #485846) - Standards-Version bumped to 3.8.0 (no changes needed) - maintainer set to Debian CLI Libraries Team + Vcs-* fields updated - moved myself to Uploaders - added Build-Depends on quilt - added monodoc-anculus-manual package + updated debian/rules + added debian/monodoc-anculus-manual.* files - added (and renamed existing ones) debian/libanculus0.3-cil.* files * debian/rules: - using dh_installcligac to late-GAC install libraries (Closes: #485847) - moving .pc files to "versioned" files (Closes: #485848) - updated to support quilt patching system * debian/installcligac added * debian/links added * debian/patches: - 01-fix_pkgconfig_pc.patch added, to fix .pc files pointing to /usr/lib/cli/anculus-sharp-0.3/. * debian/copyright: - packaging copyright updated to GPL-3+ Checksums-Sha1: f49deb84d7c8e8aa48094de72ff5eaa162141a35 1677 libanculus-sharp_0.3.1-2.dsc 3409684f47c4da4ce3f3d0f5e5b667c82f757820 3639 libanculus-sharp_0.3.1-2.diff.gz c7895eb1006db437d23056b9426223e7246b33c7 34338 libanculus0.3-cil_0.3.1-2_all.deb e4a8c21296b3f80873c8c4000178ffeceaf83138 55978 monodoc-anculus-manual_0.3.1-2_all.deb Checksums-Sha256: 03a791277642328b434cb4a15f5a2fea301faeea0eedb0411f7d908ac52260ea 1677 libanculus-sharp_0.3.1-2.dsc a20064670f7faa0da86f7e8fa3050e9f6babe33b0e830459fee536e850e30742 3639 libanculus-sharp_0.3.1-2.diff.gz 7a0f52d7585910a81f7cf7b27887a9b7345e07482f51097353a25d56e390b1
Bug#501800: Please, provide a full example of the bug
tags 501800 +moreinfo
thank you
I have tried to reproduce this bug with the following named.local:
key "key-test" {
algorithm hmac-md5;
secret "IVqRBcWBoPU2LhJTFnaJrw==";
};
acl "test" {
192.168.0.0/24;
};
acl "another" {
192.168.1.0/24;
};
zone "example.com" {
type master;
file "/etc/bind/db.local";
allow-update { key key-test; "test"; "another"; };
check-names ignore;
};
And it seems to work. Could you please provide a minimal named.conf.local that
triggers this bug?
Anyway, in the 9.5.0 release sources the file KNOWN-DEFECTS documents an ugly
bug, and an untested patch. It might be worth checking if appling the
patch fixes your problem.
--
A computer scientist is someone who, when told to "Go to Hell,"
sees the "go to," rather than the destination, as harmful.
Saludos /\/\ /\ >< `/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Please, provide a full example of the bug
Processing commands for [EMAIL PROTECTED]: > tags 501800 +moreinfo Bug#501800: bind9: bind crashes with a list for allow-update There were no tags set. Tags added: moreinfo > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501800: Please, provide a full example of the bug
tags 501800 +moreinfo
thank you
I have tried to reproduce this bug with the following named.local:
key "key-test" {
algorithm hmac-md5;
secret "IVqRBcWBoPU2LhJTFnaJrw==";
};
acl "test" {
192.168.0.0/24;
};
acl "another" {
192.168.1.0/24;
};
zone "example.com" {
type master;
file "/etc/bind/db.local";
allow-update { key key-test; "test"; "another"; };
check-names ignore;
};
And it seems to work. Could you please provide a minimal named.conf.local that
triggers this bug?
Anyway, in the 9.5.0 release sources the file KNOWN-DEFECTS documents an ugly
bug, and an untested patch. It might be worth checking if appling the
patch fixes your problem.
--
A computer scientist is someone who, when told to "Go to Hell,"
sees the "go to," rather than the destination, as harmful.
Saludos /\/\ /\ >< `/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500325: xorp: FTBFS: Not using -fPIC to generate shared lib.
* Jose Calhariz [Tue, 07 Oct 2008 23:00:16 +0100]: > On Tue, Oct 07, 2008 at 06:45:17PM +0200, Adeodato Simó wrote: > > * Jose Manuel dos Santos Calhariz [Mon, 06 Oct 2008 02:49:29 +0100]: > > Hello, > > > The configure command have two options: --enable-shared and --with-pic > > > I have tried --with-pic in a i386 arch and the shared libraries didn't > > > have code without -fPIC. The xorp-user mailing list suggested to use > > > "--enable-shared" for what seams to be the same problem [1], with an > > > older version compiling in FreeBSD. > > > So I sent to the same mailing-list a question about the differences of > > > the two options. > > > Looking inside configure command the differences are real, but minimal > > > for a Linux system. So in the end could be better adding option > > > "--with-pic" to the configure command than adding -fPIC to the > > > compiler options. > > Ok, will you be able to upload soon? > I may need a sponsor. Exist another unreport FTBFS on the other > archs, that can be more complicated to solve. I have not investigated > what is the solution for the failure on sparc and other archs. > Do you propose that I make a version 1.5-5 for this bug and a 1.5-6 > to address the other FTBFS. Wow, that's very unfortunate. I'm afraid there isn't really much point in a -5 that doesn't fix the FTBFS in the rest of arches. Do you think you'll have the time to investigate that second FTBFS? Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org As scarce as truth is, the supply has always been in excess of the demand. -- Josh Billings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494010
Processing commands for [EMAIL PROTECTED]: > tags 494010 patch Bug#494010: binary firmware in drivers/char/dsp56k.c Tags were: fixed-upstream help Tags added: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494010: Source for dsp56k firmware
Here is the assembly-language source for the firmware, licenced under GPLv2. Adding this to the kernel source package should fix this bug. Ben. ; Author: Frederik Noring <[EMAIL PROTECTED]> ; ; This file is subject to the terms and conditions of the GNU General Public ; License. See the file COPYING in the main directory of this archive ; for more details. ; DSP56k loader ; Host Interface M_BCR EQU $FFFE ; Port A Bus Control Register M_PBC EQU $FFE0 ; Port B Control Register M_PBDDR EQU $FFE2 ; Port B Data Direction Register M_PBD EQU $FFE4 ; Port B Data Register M_PCC EQU $FFE1 ; Port C Control Register M_PCDDR EQU $FFE3 ; Port C Data Direction Register M_PCD EQU $FFE5 ; Port C Data Register M_HCR EQU $FFE8 ; Host Control Register M_HSR EQU $FFE9 ; Host Status Register M_HRX EQU $FFEB ; Host Receive Data Register M_HTX EQU $FFEB ; Host Transmit Data Register ; SSI, Synchronous Serial Interface M_RXEQU $FFEF ; Serial Receive Data Register M_TXEQU $FFEF ; Serial Transmit Data Register M_CRA EQU $FFEC ; SSI Control Register A M_CRB EQU $FFED ; SSI Control Register B M_SREQU $FFEE ; SSI Status Register M_TSR EQU $FFEE ; SSI Time Slot Register ; Exception Processing M_IPR EQU $ ; Interrupt Priority Register org P:$0 start jmp <$40 org P:$40 ; ; Zero 16384 DSP X and Y words ; clr A #0,r0 ; clr B #0,r4 ; do #64,<_block1 ; rep #256 ; moveA,X:(r0)+ B,Y:(r4)+ ;_block1; Zero (32768-512) Program words ; clr A #512,r0 ; do #126,<_block2 ; rep #256 ; moveA,P:(r0)+ ;_block2 ; Copy DSP program control move#real,r0 move#upload,r1 do #upload_end-upload,<_copy moveP:(r0)+,x0 movex0,P:(r1)+ _copy movep #>4,X:<$c00,X:<1,X:<0,X:<3,x0 cmp x0,A #>1,x0 jeq <$0 _get_address jclr#0,X:<2,x0 jeq load_X cmp x0,A jeq load_Y load_P do y0,_load jclr#0,X:< signature.asc Description: This is a digitally signed message part
Processed: tagging 499025
Processing commands for [EMAIL PROTECTED]: > tags 499025 etch Bug#499025: heartbeat-2: Primary node thrashes to death with queue error There were no tags set. Tags added: etch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492920: crystalspace - lintian error fixes (patch)
Hi Feel free to NMU If you don't I'll do this week Christian Andres Mejia a écrit : Here's a patch that will address the errors from lintian, which would justify the severity of this bug. The rest of your changes would be severity important I think. Have you tried contacting the current maintainer in getting all your changes uploaded to Debian? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495211: marked as done (libatomic-ops FTBFS on powerpc)
Your message dated Sun, 12 Oct 2008 17:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#495211: fixed in libatomic-ops 1.2-4+lenny1 has caused the Debian Bug report #495211, regarding libatomic-ops FTBFS on powerpc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 495211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495211 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libatomic-ops Version: 1.2-4 Severity: serious libatomic-ops currently fails to build on powerpc/unstable due to a failing test case: [...] make[4]: Entering directory `/home/ths/tf/debs/libatomic-ops-1.2/tests' cc -DHAVE_CONFIG_H -I. -I. -I../src -I./../src -g -O2 -g -Wall -O2 -DNDEBUG -c test_atomic.c cc -g -O2 -g -Wall -O2 -DNDEBUG -o test_atomic test_atomic.o -lpthread ../src/libatomic_ops.a cc -DHAVE_CONFIG_H -I. -I. -I../src -DAO_USE_PTHREAD_DEFS -I./../src -g -O2 -g -Wall -O2 -DNDEBUG -c -o test_atomic_pthreads-test_atomic.o `test -f 'test_atomic.c' || echo './'`test_atomic.c cc -g -O2 -g -Wall -O2 -DNDEBUG -o test_atomic_pthreads test_atomic_pthreads-test_atomic.o -lpthread ../src/libatomic_ops.a cc -DHAVE_CONFIG_H -I. -I. -I../src -I./../src -g -O2 -g -Wall -O2 -DNDEBUG -c test_stack.c test_stack.c: In function 'run_one_test': test_stack.c:113: warning: unused variable 'aux' cc -g -O2 -g -Wall -O2 -DNDEBUG -o test_stack test_stack.o -lpthread ../src/libatomic_ops_gpl.a ../src/libatomic_ops.a cc -DHAVE_CONFIG_H -I. -I. -I../src -I./../src -g -O2 -g -Wall -O2 -DNDEBUG -c test_malloc.c test_malloc.c: In function 'main': test_malloc.c:158: warning: unused variable 'exper_n' cc -g -O2 -g -Wall -O2 -DNDEBUG -o test_malloc test_malloc.o -lpthread ../src/libatomic_ops_gpl.a ../src/libatomic_ops.a make[4]: Leaving directory `/home/ths/tf/debs/libatomic-ops-1.2/tests' /usr/bin/make check-TESTS make[4]: Entering directory `/home/ths/tf/debs/libatomic-ops-1.2/tests' Missing: AO_short_fetch_and_add Missing: AO_short_fetch_and_add1 Missing: AO_short_fetch_and_sub1 Missing: AO_char_fetch_and_add Missing: AO_char_fetch_and_add1 Missing: AO_char_fetch_and_sub1 Missing: AO_int_fetch_and_add Missing: AO_int_fetch_and_add1 Missing: AO_int_fetch_and_sub1 Missing: AO_compare_double_and_swap_double Missing: AO_compare_and_swap_double Missing: AO_nop_acquire Missing: AO_store_acquire Assertion failed test_atomic_include.h:475 (barrier: _acquire) FAIL: test_atomic Missing: AO_nop_acquire Missing: AO_store_acquire Missing: AO_short_store_acquire Missing: AO_char_store_acquire Missing: AO_int_store_acquire Missing: AO_nop_release Missing: AO_load_release Missing: AO_short_load_release Missing: AO_char_load_release Missing: AO_int_load_release Missing: AO_store_read Missing: AO_short_store_read Missing: AO_char_store_read Missing: AO_int_store_read Missing: AO_load_write Missing: AO_short_load_write Missing: AO_char_load_write Missing: AO_int_load_write Missing: AO_nop_release_write Missing: AO_load_release_write Missing: AO_short_load_release_write Missing: AO_char_load_release_write Missing: AO_int_load_release_write Missing: AO_nop_acquire_read Missing: AO_store_acquire_read Missing: AO_short_store_acquire_read Missing: AO_char_store_acquire_read Missing: AO_int_store_acquire_read Testing add1/sub1 Succeeded Testing store_release_write/load_acquire_read Succeeded Testing test_and_set Succeeded PASS: test_atomic_pthreads About 100 pushes + 100 pops in 1 threads: 305 msecs About 100 pushes + 100 pops in 2 threads: 318 msecs About 100 pushes + 100 pops in 3 threads: 298 msecs About 100 pushes + 100 pops in 4 threads: 315 msecs PASS: test_stack Testing AO_malloc/AO_free Succeeded Performing 1000 reversals of 1000 element lists in 10 threads PASS: test_malloc === 1 of 4 tests failed === make[4]: *** [check-TESTS] Error 1 make[4]: Leaving directory `/home/ths/tf/debs/libatomic-ops-1.2/tests' make[3]: *** [check-am] Error 2 make[3]: Leaving directory `/home/ths/tf/debs/libatomic-ops-1.2/tests' make[2]: *** [check] Error 2 make[2]: Leaving directory `/home/ths/tf/debs/libatomic-ops-1.2/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/ths/tf/debs/libatomic-ops-1.2' make: *** [debian/stamp-makefile-check] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 --- End Message --- --- Begin Message --- Source: libatomic-ops Source-Version: 1.2-4+lenny1 We believe that the bug you reported is fixed in the latest version of libatomic-ops, which is due to be in
Processed: asd
Processing commands for [EMAIL PROTECTED]: > # this bug is unreproducible by many, mark it as important unless someone can > reproduce it > severity #495184 important Bug#495184: wodim: --devices works under strace, fails otherwise Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 502001 is important
Processing commands for [EMAIL PROTECTED]: > # workaround exists > severity 502001 important Bug#502001: seyon: will not run with x-terminal-emulator = /usr/bin/konsole Severity set to `important' from `grave' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495211: #495211 - libatomic-ops FTBFS on powerpc
OK, I've uploaded 1.2-4+lenny1 to testing-proposed-updates. Below is the interdiff between 1.2-4 and 1.2.4+lenny1: diff -u libatomic-ops-1.2/debian/patches/05_powerpc_asm.patch libatomic-ops-1.2/debian/patches/05_powerpc_asm.patch --- libatomic-ops-1.2/debian/patches/05_powerpc_asm.patch +++ libatomic-ops-1.2/debian/patches/05_powerpc_asm.patch @@ -5,7 +5,7 @@ /* tried the "y" constraint.*/ __asm__ __volatile__ ( -"lwz %0,%1\n" -+"lwz%X1 %0,%1\n" ++"lwz%U1%X1 %0,%1\n" "cmpw cr7,%0,%0\n" "bne- cr7,1f\n" "1: isync\n" diff -u libatomic-ops-1.2/debian/changelog libatomic-ops-1.2/debian/changelog --- libatomic-ops-1.2/debian/changelog +++ libatomic-ops-1.2/debian/changelog @@ -1,3 +1,14 @@ +libatomic-ops (1.2-4+lenny1) testing-proposed-updates; urgency=medium + + * Non-maintainer upload. + * fixed debian/patches/05_powerpc_asm.patch to get it building on ppc again +(Closes: 495211) + * Uploading to testing-proposed-updates to fix the bug for lenny, becuase +the cvs version in unstable isn't a valid candidate for a freeze +exception. + + -- Mike O'Connor <[EMAIL PROTECTED]> Sun, 12 Oct 2008 16:26:06 -0400 + libatomic-ops (1.2-4) unstable; urgency=low * Closes: #463390 -- Add 06_double.patch to fix some issues with double signature.asc Description: Digital signature
Bug#502001: seyon: will not run with x-terminal-emulator = /usr/bin/konsole
Quoting Mark Pictor ([EMAIL PROTECTED]): > Package: seyon > Version: 2.20c-28 > Severity: grave > Justification: renders package unusable > > > $ seyon > seyon-emu: Unknown option '-n'. > seyon-emu: Use --help to get a list of available command line options. > $ ll /etc/alternatives/x-terminal-emulator > lrwxrwxrwx 1 root root 16 2008-04-11 00:17 > /etc/alternatives/x-terminal-emulator -> > /usr/bin/konsole > > seyon-emu is a symlink. Through a chain of symlinks, it points to konsole. There is a workaround for this: launch "seyon -nodefargs". Indeed, I think this bug is similar to #398508. As there is a workaround, I suggest downgrading this bug to important. signature.asc Description: Digital signature
Processed: tagging 494468
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 494468 + pending Bug#494468: Postinst violates Debian policy (10.7.3) by not preserving changes to /etc/locale.gen There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502005: Removing slocate 3.1-1.1 breaks
Package: slocate Version: 3.1-1.1 Severity: serious Justification: Policy 6.8 Removing slocate fails, which is substantially harder to deal with than the failed upgrade: Removing group `slocate' ... groupdel: error removing group entry /usr/sbin/delgroup: `/usr/sbin/groupdel slocate' returned error code 10. Exiting. dpkg: error processing slocate (--purge): subprocess post-removal script returned error exit status 1 Errors were encountered while processing: slocate The final delgroup in the postrm needs to not break the script if it fails. Tacking in a || echo warning should probably handle it. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (850, 'unstable'), (650, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.17-2-k7 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages slocate depends on: ii adduser 3.107 add and remove users and groups ii dpkg 1.14.22Debian package management system hi libc6 2.7-10 GNU C Library: Shared libraries slocate recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501882: Some more info about this bug
pgsnap fails because /usr/bin/pgsnap does this: cd /usr/share/pgsnap ./pgsnap.php $* Obviously this goes terribly wrong if the output directory is relative (which is the default...). pgsnap seems to work fine once you give it an absolute directory with the -o option. pgsnap.php needs to get a way to tell the difference between its data directory (i.e. /usr/share/pgsnap) and the users working directory. I can't tell how much work that would be exactly, but looks like a invasive change on first glance. Maybe this software isn't ready for a stable release? Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501410: Updating libio-socket-ssl-perl in lenny
Frank Lichtenheld wrote: >>From my testing it seems that this FTBFS does not occour with > version 1.16 of libio-socket-ssl-perl from unstable. I would > therefor suggest letting the new version into testing. The patch > looks small enough. unblocked Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502002: texlive-latex-extra: hilowres.sty is non-free
Package: texlive-latex-extra Version: 2007.dfsg.4-1 Severity: serious Dear Debian release team, in the past, license auditing of texlive has mainly been done by ourselves and the TeX Live team, but we all had many more occupations and never really got to systematically do that. In the last couple of weeks, our second-level upstream, the CTAN team, has added their efforts, and since they deal mainly with cataloguing and updating packages, we have now many more packages for which we can definitely be sure about their license - but also, non-free packages turn up continuously, as you might have noticed by our unfreeze requests. Here's one more, and a question: , | From: Robin Fairbairns <[EMAIL PROTECTED]> | Subject: [tex-live] hilowres package | To: [EMAIL PROTECTED] | Date: Sun, 12 Oct 2008 10:37:24 +0100 | | was unknown licence, but on examination i find it restricts | modification. | | i've therefore changed the catalogue licence to other-nonfree | | robin ` The question: If you would promise to give us a heads-up about two or three weeks before the actual release date, we would stop uploading new upstream versions for every RC bug. Instead, we would do that in one larger upload. We need some days warning in advance, however, because Norbert will be on vacation regularly, and I am very much oppupied with my paid work (and actually away from home and office regularly, without internet access). If you prefer, we can also just make upload for every non-free part that is discovered. Thanks, Frank -- Package-specific info: If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.latex-einfuehrung.de/mini-en.html (english) or http://www.latex-einfuehrung.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 frank frank 1858 13. Apr 2007 /home/frank/.texmf-var/ls-R -rw-r--r-- 1 root root 1804 28. Sep 18:22 /var/lib/texmf/ls-R -rw-rw-r-- 1 root staff 5883 10. Okt 22:31 /usr/local/share/texmf/ls-R lrwxrwxrwx 1 root root 29 30. Jul 22:20 /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 27 28. Sep 18:13 /usr/share/texmf-texlive/ls-R -> /var/lib/texmf/ls-R-TEXLIVE lrwxrwxrwx 1 root root 27 28. Sep 18:13 /usr/share/texmf-texlive/ls-R -> /var/lib/texmf/ls-R-TEXLIVE ## Config files -rw-r--r-- 1 frank frank 17 25. Jun 20:54 /home/frank/.texmf-config/web2c/texmf.cnf -rw-r--r-- 1 frank frank 0 26. Jun 21:44 /home/frank/texmf/web2c/fmtutil.cnf -rw-r--r-- 1 frank frank 20670 18. Mai 2007 /home/frank/.texmf-var/web2c/updmap.cfg -rw-r--r-- 1 root root 14538 28. Sep 18:22 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ insgesamt 15 -rw-r--r-- 1 root root 12304 11. Jun 2007 fmtutil.cnf_onceuponatime -rw-r--r-- 1 root root 283 4. Apr 2007 mktex.cnf ## md5sums of texmf.d 42c20d7e8bd343542772b5a145bf8ad8 /etc/texmf/texmf.d/05TeXMF.cnf 5f7f6652cc8b8071c9e4ea6ba9e9f0a1 /etc/texmf/texmf.d/15Plain.cnf d588a08518f705d06ac262acd78f2bc4 /etc/texmf/texmf.d/20xmltex.cnf 589b39396bf292237eb7ea037cf199f6 /etc/texmf/texmf.d/20xmltex.cnf.bak f68e5add6afd6585b982f2f78e2e6a92 /etc/texmf/texmf.d/45TeXinputs.cnf a97d4dac1333cedb719bc0c9402f4c88 /etc/texmf/texmf.d/45TeXinputs.cnf~ 8a26468004b5ebc7ae9884740356c1d0 /etc/texmf/texmf.d/45TeXinputs.cnf.ucf-dist 5be40776c04076dfd0a43f7ac8abd188 /etc/texmf/texmf.d/45TeXinputs.cnf.ucf-old ea33127256c6a9f37145ae5b16fdb80c /etc/texmf/texmf.d/55Fonts.cnf afccf1d3f87057411166a77c58e00bd1 /etc/texmf/texmf.d/65BibTeX.cnf 9da7c1c7b1eaf06f941af91f48a23068 /etc/texmf/texmf.d/75DviPS.cnf 7ae52efac46feb97010986e57877d12e /etc/texmf/texmf.d/80DVIPDFMx.cnf.bak 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf 37329819f1109e8a457e64b8b58fecdb /etc/texmf/texmf.d/85Misc.cnf 1f00a56be982e52d375c57ff6a5740c4 /etc/texmf/texmf.d/85Misc.cnf.ucf-old 7b9c80b4a90a3e3b5cae01d23fa7056d /etc/texmf/texmf.d/90TeXDoc.cnf bd9a6dcfcc6ca1c479be98c064754de8 /etc/texmf/texmf.d/90TeXDoc.cnf~ a8952d594677235951d447665ec46e9c /etc/texmf/texmf.d/90TeXDoc.cnf.ucf-dist d254e287f481458845f82a71dd44d377 /etc/texmf/texmf.d/95NonPath.cnf 30f4f13357c2761ed01a6a15f28725a5 /etc/texmf/texmf
Bug#502001: seyon: will not run with x-terminal-emulator = /usr/bin/konsole
Package: seyon Version: 2.20c-28 Severity: grave Justification: renders package unusable $ seyon seyon-emu: Unknown option '-n'. seyon-emu: Use --help to get a list of available command line options. $ ll /etc/alternatives/x-terminal-emulator lrwxrwxrwx 1 root root 16 2008-04-11 00:17 /etc/alternatives/x-terminal-emulator -> /usr/bin/konsole seyon-emu is a symlink. Through a chain of symlinks, it points to konsole. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.5-64NV_22sep08 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages seyon depends on: ii debconf [debconf-2.0 1.5.17 Debian configuration management sy ii konsole [x-terminal- 4:3.5.9.dfsg.1-2+b1 X terminal emulator for KDE ii libc62.7-4 GNU C Library: Shared libraries ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libsm6 2:1.0.3-1+b1X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxaw7 2:1.0.4-1 X11 Athena Widget library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxmu6 2:1.0.4-1 X11 miscellaneous utility library ii libxpm4 1:3.5.7-1 X11 pixmap library ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library seyon recommends no packages. Versions of packages seyon suggests: pn ckermit(no description available) pn lrzsz (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed (with 5 errors): Re: splashy: FTBFS when DEB_BUILD_OPTIONS is set to noopt,nostrip
Processing commands for [EMAIL PROTECTED]: > tags 501997 +patch Bug#501997: splashy: FTBFS when DEB_BUILD_OPTIONS is set to noopt,nostrip Tags were: patch Tags added: patch > I've tested this and it does indeed fix the problem. Unknown command or malformed arguments to command. > I have attached a patch with the actual changes needed. Unknown command or malformed arguments to command. > Let me know if you would like an NMU. Unknown command or malformed arguments to command. > Regards, Unknown command or malformed arguments to command. > Bradley Smith Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501997: splashy: FTBFS when DEB_BUILD_OPTIONS is set to noopt,nostrip
tags 501997 +patch I've tested this and it does indeed fix the problem. I have attached a patch with the actual changes needed. Let me know if you would like an NMU. Regards, Bradley Smith -- Bradley Smith <[EMAIL PROTECTED]> GPG: 0xC718D347 diff -u splashy-0.3.10/debian/patches/series splashy-0.3.10/debian/patches/series --- splashy-0.3.10/debian/patches/series +++ splashy-0.3.10/debian/patches/series @@ -1,0 +2 @@ +02_add_missing_headers.diff --- splashy-0.3.10.orig/debian/patches/02_add_missing_headers.diff +++ splashy-0.3.10/debian/patches/02_add_missing_headers.diff @@ -0,0 +1,12 @@ +Index: splashy-0.3.10/src/splashy_config-main.c +=== +--- splashy-0.3.10.orig/src/splashy_config-main.c 2008-10-12 16:28:15.0 +0100 splashy-0.3.10/src/splashy_config-main.c 2008-10-12 16:28:39.0 +0100 +@@ -41,6 +41,7 @@ + #include /* getuid */ + #include /* getopt_long */ + #include ++#include + + #include "common_macros.h" + #include "splashycnf.h" signature.asc Description: PGP signature
Bug#501990: gwenview: Gwenview crashes when trying "Copy to" from a tar.gz file
severity 501990 normal
tags 501990 experimental
stop
Unless I'm misreading, there is no data loss since the tar.gz is not
deleted nor its contents affected. The problem is that files can't be
extracted from tar.gz using Gwenview.
Correct me if I'm wrong...
Thanks,
Christopher Martin
On October 12, 2008 10:03:54 Saulo Soares de Toledo wrote:
> Package: gwenview
> Version: 4:4.1.2-1
> Severity: grave
> Justification: causes non-serious data loss
>
> 1) Open a tar.gz file in Dolphin
> 2) Open with a image file inside this tar.gz with Gwenview, here it's
> possible navigate at image files
> 3) Select "Copy to" option, the window to copy files will open
> 4) When try change the folder to Home or other directory, Gwenview
> crashes. I don't know exactily this last pass, but will crash.
>
>
> The backtrace:
>
> Aplicativo: Gwenview (gwenview), sinal SIGABRT
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb5e8a6c0 (LWP 4272)]
> [KCrash handler]
> #6 0xb7f97424 in __kernel_vsyscall ()
> #7 0xb68e4640 in raise () from /lib/i686/cmov/libc.so.6
> #8 0xb68e6018 in abort () from /lib/i686/cmov/libc.so.6
> #9 0xb6b506cd in qt_message_output (msgType=QtFatalMsg,
> buf=0xbf9ad570 "ASSERT: \"!isEmpty()\" in file
> #/usr/include/qt4/QtCore/qlist.h, line 252") at
> global/qglobal.cpp:2102 #10 0xb6b50796 in qFatal (msg=0xb6c98438
> "ASSERT: \"%s\" in file %s, line #%d")
> at global/qglobal.cpp:2303
> #11 0xb6b50825 in qt_assert (assertion=0xb769cdd7 "!isEmpty()",
> file=0xb769c7d4 "/usr/include/qt4/QtCore/qlist.h", line=252)
> at global/qglobal.cpp:1872
> #12 0xb7657018 in KDirOperator::Private::_k_slotSelectionChanged (
> this=0x9019440) at /usr/include/qt4/QtCore/qlist.h:252
> #13 0xb765eb9f in KDirOperator::qt_metacall (this=0x900afe8,
> _c=QMetaObject::InvokeMetaMethod, _id=56, _a=0xbf9af6d8)
> at
>
> /tmp/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kfile/kdiroperator.moc:
>226 #14 0xb6c5cbd0 in QMetaObject::activate (sender=0x915b120,
> from_signal_index=4, to_signal_index=4, argv=0xbf9af6d8)
> at kernel/qobject.cpp:3031
> #15 0xb6c5d952 in QMetaObject::activate (sender=0x915b120,
> m=0xb761bff0, local_signal_index=0, argv=0xbf9af6d8) at
> kernel/qobject.cpp:3101 #16 0xb737dbe9 in
> QItemSelectionModel::selectionChanged (this=0x915b120,
> [EMAIL PROTECTED], [EMAIL PROTECTED])
> at .moc/release-shared/moc_qitemselectionmodel.cpp:144
> #17 0xb7385770 in QItemSelectionModel::emitSelectionChanged
> (this=0x915b120, [EMAIL PROTECTED], [EMAIL PROTECTED])
> at itemviews/qitemselectionmodel.cpp:1454
> #18 0xb7385a76 in QItemSelectionModel::select (this=0x915b120,
> [EMAIL PROTECTED], command={i = -1080363004})
> at itemviews/qitemselectionmodel.cpp:1013
> #19 0xb7380820 in QItemSelectionModel::select (this=0x915b120,
> [EMAIL PROTECTED], command={i = -1080362952})
> at itemviews/qitemselectionmodel.cpp:901
> #20 0xb7664007 in KDirOperatorDetailView::currentChanged
> (this=0x90a6d10, [EMAIL PROTECTED], [EMAIL PROTECTED])
> at
> /tmp/buildd/kde4libs-4.1.2/kfile/kdiroperatordetailview.cpp:136 #21
> 0xb73319fc in QAbstractItemView::qt_metacall (this=0x90a6d10,
> _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbf9af9b8) at
> .moc/release-shared/moc_qabstractitemview.cpp:227
> #22 0xb7374e2a in QTreeView::qt_metacall (this=0x90a6d10,
> _c=QMetaObject::InvokeMetaMethod, _id=51, _a=0xbf9af9b8)
> at .moc/release-shared/moc_qtreeview.cpp:121
> #23 0xb765418a in KDirOperatorDetailView::qt_metacall
> (this=0x90a6d10, _c=QMetaObject::InvokeMetaMethod, _id=51,
> _a=0xbf9af9b8) at
>
> /tmp/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kfile/moc_kdiroperatord
>etailview_p.cpp:62 #24 0xb6c5cbd0 in QMetaObject::activate
> (sender=0x915b120,
> from_signal_index=5, to_signal_index=5, argv=0xbf9af9b8)
> at kernel/qobject.cpp:3031
> #25 0xb6c5d952 in QMetaObject::activate (sender=0x915b120,
> m=0xb761bff0, local_signal_index=1, argv=0xbf9af9b8) at
> kernel/qobject.cpp:3101 #26 0xb737db99 in
> QItemSelectionModel::currentChanged (this=0x915b120, [EMAIL PROTECTED],
> [EMAIL PROTECTED])
> at .moc/release-shared/moc_qitemselectionmodel.cpp:151
> #27 0xb737dd3d in QItemSelectionModel::setCurrentIndex
> (this=0x915b120, [EMAIL PROTECTED], command={i = -1080362272})
> at itemviews/qitemselectionmodel.cpp:1082
> #28 0xb732fb8a in QAbstractItemView::mousePressEvent (this=0x90a6d10,
> event=0xbf9b04ac) at itemviews/qabstractitemview.cpp:1470
> #29 0xb7373527 in QTreeView::mousePressEvent (this=0x90a6d10,
> event=0xbf9b04ac) at itemviews/qtreeview.cpp:1761
> #30 0xb766404f in KDirOperatorDetailView::mousePressEvent
> (this=0x90a6d10, event=0xbf9b04ac)
> at
> /tmp/buildd/kde4libs-4.1.2/kfile/kdiroperatordetailview.cpp:122 #31
> 0xb6ec17a9 in QWidget::event (this=0x90a6d10, event=0xbf9b04ac) at
> kernel/qwidget.cpp:7159
> #32 0xb71f4ca3 in QFrame::event (this=0x90a6d10, e=0xbf9b04ac)
>
Processed: tagging 497676
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 497676 pending Bug#497676: win32-loader: FTBFS in lenny: Nonexistent build-dependency: loadlin There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#501990: gwenview: Gwenview crashes when trying "Copy to" from a tar.gz file
Processing commands for [EMAIL PROTECTED]: > severity 501990 normal Bug#501990: gwenview: Gwenview crashes when trying "Copy to" from a tar.gz file Severity set to `normal' from `grave' > tags 501990 experimental Bug#501990: gwenview: Gwenview crashes when trying "Copy to" from a tar.gz file There were no tags set. Tags added: experimental > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501997: splashy: FTBFS when DEB_BUILD_OPTIONS is set to noopt,nostrip
Package: splashy Severity: serious Tags: patch thanks Hi, because I intend to debug a segfault in splashy I tried to built the package with DEB_BUILD_OPTIONS=noopt,nostrip. This did not work, because creating splashy cc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/directfb -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O0 -Wall -Werror -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -c -o splashy_config-splashy_config-main.o `test -f 'splashy_config-main.c' || echo './'`splashy_config-main.c cc1: warnings being treated as errors splashy_config-main.c: In function ‘main’: splashy_config-main.c:154: error: implicit declaration of function ‘setlocale’ splashy_config-main.c:154: error: ‘LC_ALL’ undeclared (first use in this function) splashy_config-main.c:154: error: (Each undeclared identifier is reported only once splashy_config-main.c:154: error: for each function it appears in.) The fix is simple. Its just neccessary to add #include at line 44 of src/splashy_config-main.c Thanks and best Regards, Patrick signature.asc Description: Digital signature
Bug#494340: fslview package fixing RC-bugs
* Michael Hanke [Sun, 12 Oct 2008 14:22:05 +0200]: > Dear Release Managers, > the fslview package in lenny (3.0+4.0.2-3) is affected by three RC bugs > (482209, 475993, 475993). All of them are fixed, since version > 3.0+4.0.2-5, but it never got into testing due to a FTBFS on ARM. > Recently, Yaroslav Halchenko was able to determine the cause of the bug > (had already been reported): > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475993#37 > which has its origin in the VTK package and got fixed very recently > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492538 > The package with all RC-bug fixes corresponding to the fslview upstream > version currently in lenny is already in the archive > http://ftp.debian.org/debian/pool/main/f/fslview/fslview_3.0+4.0.2-5.dsc > However, in unstable it has already been replaced by a more recent > upstream version. Can the above package be hinted into testing, or > should I prepare a new upload to testing-proposed-updates? No, it can't be hinted, please reupload 3.0+4.0.2-5 to testing-proposed-updates as 3.0+4.0.2-5+lenny1 or something similar. Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Mankind are very odd creatures: one half censure what they practice, the other half practice what they censure; the rest always say and do as they ought. -- Michel de Montaigne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501990: gwenview: Gwenview crashes when trying "Copy to" from a tar.gz file
Package: gwenview
Version: 4:4.1.2-1
Severity: grave
Justification: causes non-serious data loss
1) Open a tar.gz file in Dolphin
2) Open with a image file inside this tar.gz with Gwenview, here it's
possible navigate at image files
3) Select "Copy to" option, the window to copy files will open
4) When try change the folder to Home or other directory, Gwenview crashes.
I don't know exactily this last pass, but will crash.
The backtrace:
Aplicativo: Gwenview (gwenview), sinal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb5e8a6c0 (LWP 4272)]
[KCrash handler]
#6 0xb7f97424 in __kernel_vsyscall ()
#7 0xb68e4640 in raise () from /lib/i686/cmov/libc.so.6
#8 0xb68e6018 in abort () from /lib/i686/cmov/libc.so.6
#9 0xb6b506cd in qt_message_output (msgType=QtFatalMsg,
buf=0xbf9ad570 "ASSERT: \"!isEmpty()\" in file
#/usr/include/qt4/QtCore/qlist.h, line 252") at global/qglobal.cpp:2102
#10 0xb6b50796 in qFatal (msg=0xb6c98438 "ASSERT: \"%s\" in file %s, line
#%d")
at global/qglobal.cpp:2303
#11 0xb6b50825 in qt_assert (assertion=0xb769cdd7 "!isEmpty()",
file=0xb769c7d4 "/usr/include/qt4/QtCore/qlist.h", line=252)
at global/qglobal.cpp:1872
#12 0xb7657018 in KDirOperator::Private::_k_slotSelectionChanged (
this=0x9019440) at /usr/include/qt4/QtCore/qlist.h:252
#13 0xb765eb9f in KDirOperator::qt_metacall (this=0x900afe8,
_c=QMetaObject::InvokeMetaMethod, _id=56, _a=0xbf9af6d8)
at
/tmp/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kfile/kdiroperator.moc:226
#14 0xb6c5cbd0 in QMetaObject::activate (sender=0x915b120,
from_signal_index=4, to_signal_index=4, argv=0xbf9af6d8)
at kernel/qobject.cpp:3031
#15 0xb6c5d952 in QMetaObject::activate (sender=0x915b120, m=0xb761bff0,
local_signal_index=0, argv=0xbf9af6d8) at kernel/qobject.cpp:3101
#16 0xb737dbe9 in QItemSelectionModel::selectionChanged (this=0x915b120,
[EMAIL PROTECTED], [EMAIL PROTECTED])
at .moc/release-shared/moc_qitemselectionmodel.cpp:144
#17 0xb7385770 in QItemSelectionModel::emitSelectionChanged (this=0x915b120,
[EMAIL PROTECTED], [EMAIL PROTECTED])
at itemviews/qitemselectionmodel.cpp:1454
#18 0xb7385a76 in QItemSelectionModel::select (this=0x915b120,
[EMAIL PROTECTED], command={i = -1080363004})
at itemviews/qitemselectionmodel.cpp:1013
#19 0xb7380820 in QItemSelectionModel::select (this=0x915b120,
[EMAIL PROTECTED], command={i = -1080362952})
at itemviews/qitemselectionmodel.cpp:901
#20 0xb7664007 in KDirOperatorDetailView::currentChanged (this=0x90a6d10,
[EMAIL PROTECTED], [EMAIL PROTECTED])
at /tmp/buildd/kde4libs-4.1.2/kfile/kdiroperatordetailview.cpp:136
#21 0xb73319fc in QAbstractItemView::qt_metacall (this=0x90a6d10,
_c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbf9af9b8)
at .moc/release-shared/moc_qabstractitemview.cpp:227
#22 0xb7374e2a in QTreeView::qt_metacall (this=0x90a6d10,
_c=QMetaObject::InvokeMetaMethod, _id=51, _a=0xbf9af9b8)
at .moc/release-shared/moc_qtreeview.cpp:121
#23 0xb765418a in KDirOperatorDetailView::qt_metacall (this=0x90a6d10,
_c=QMetaObject::InvokeMetaMethod, _id=51, _a=0xbf9af9b8)
at
/tmp/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kfile/moc_kdiroperatordetailview_p.cpp:62
#24 0xb6c5cbd0 in QMetaObject::activate (sender=0x915b120,
from_signal_index=5, to_signal_index=5, argv=0xbf9af9b8)
at kernel/qobject.cpp:3031
#25 0xb6c5d952 in QMetaObject::activate (sender=0x915b120, m=0xb761bff0,
local_signal_index=1, argv=0xbf9af9b8) at kernel/qobject.cpp:3101
#26 0xb737db99 in QItemSelectionModel::currentChanged (this=0x915b120,
[EMAIL PROTECTED], [EMAIL PROTECTED])
at .moc/release-shared/moc_qitemselectionmodel.cpp:151
#27 0xb737dd3d in QItemSelectionModel::setCurrentIndex (this=0x915b120,
[EMAIL PROTECTED], command={i = -1080362272})
at itemviews/qitemselectionmodel.cpp:1082
#28 0xb732fb8a in QAbstractItemView::mousePressEvent (this=0x90a6d10,
event=0xbf9b04ac) at itemviews/qabstractitemview.cpp:1470
#29 0xb7373527 in QTreeView::mousePressEvent (this=0x90a6d10,
event=0xbf9b04ac) at itemviews/qtreeview.cpp:1761
#30 0xb766404f in KDirOperatorDetailView::mousePressEvent (this=0x90a6d10,
event=0xbf9b04ac)
at /tmp/buildd/kde4libs-4.1.2/kfile/kdiroperatordetailview.cpp:122
#31 0xb6ec17a9 in QWidget::event (this=0x90a6d10, event=0xbf9b04ac)
at kernel/qwidget.cpp:7159
#32 0xb71f4ca3 in QFrame::event (this=0x90a6d10, e=0xbf9b04ac)
at widgets/qframe.cpp:651
#33 0xb728b3cf in QAbstractScrollArea::viewportEvent (this=0x90a6d10, e=0x6)
at widgets/qabstractscrollarea.cpp:943
#34 0xb733688f in QAbstractItemView::viewportEvent (this=0x90a6d10,
event=0xbf9b04ac) at itemviews/qabstractitemview.cpp:1429
#35 0xb736e5f4 in QTreeView::viewportEvent (this=0x90a6d10,
event=0xbf9b04ac)
at itemviews/qtreeview.cpp:1265
#36 0xb728d975 in QAbstractScrollAreaFilter::eventFilter (this=0x90c0130,
Bug#470882: /dev/gpmctl freezes acknowledge
On Sun, Oct 12, 2008 at 12:19:49PM +0200, Kurt Roeckx wrote: > On Thu, Oct 09, 2008 at 01:14:28AM +0200, Samuel Thibault wrote: > > > > Now, that being said, that reminds me bug #472063: actually libgpm > > shouldn't even have tried to connect to the server, it should have just > > noticed it is running in an X terminal and set gpm_fd to -2... > > Both people reporting this bug seem to be using rxvt-unicode, and > #472063 is also about that. #472063 is also still open. > > So I've tried a few different things. Using aptitude: > - virtual console shows mouse, but doesn't work as expected. Clicking > somewhere doesn't always seem to have an effect. Click and drag seems > to have a weird effects. ncurses is "only" using a click-style interface for GPM (no dragging). As I recall it, GPM also has some built-in behavior for select/paste which ncurses doesn't try to work around. > - xterm: the mouse icon stays the same as a normal xterm, one used for > selecting text. Clicking someone does seem to have the desired > effect. However, it seems that the place where the cursor is shown > in other cases it just shows an empty space instead of the '-'. I'm not sure why ncurses would behave different from gnome/konsole here. The description isn't clear (to me) though... (coincidentally, I was just testing gnome-terminal with vttest, seeing some mouse-related bugs there ;-) > - rxvt-unicode: The mouse icon is also the text selecting one, and it's > all that it seems to be doing. The cursor is not shown. that may depend on the terminfo (Debian maintains that one). > - gnome-terminal: the mouse icon is a normal pointer. It also works > as expected. When aptitude wasn't started it was the text selection > icon. > - konsole: behaves the same as gnome-terminal. > > For w3m: > - virtual console: no mouse shown, also doesn't seem to have > any effect at all. > - xterm: same as aptitude, but text under cursor still shown. > - rxvt-unicode: same as aptitude, but the cursor is shown now. > - gnome-terminal: same as aptitude. > - konsole: same as aptitude. > > For pdmenu: > - virtual console: no mouse shown, but moving it changes the current > line of the menu. It's shown in white on black, no colors. > - xterm, rxvt-unicode, gnome-terminal, konsole: Just selection > of text. They all show it in color, rxvt-unicode with a grey > background, the rest with a blue background. > > > So it seems to me that the problem might be in the terminal emulator. > > I was not able to reproduce any hanging or segfaults or something > simular. > > > Packages used: > aptitude 0.4.11.8-1 > gpm1.20.4-2 > libncurses55.6+20080830-1 > w3m0.5.2-2+b1 > rxvt-unicode 9.05-1 > gnome-terminal 2.22.3-3 > xterm 235-1 > konsole 4:3.5.9.dfsg.1-5 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpVvTzvIT84N.pgp Description: PGP signature
Bug#500807: (no subject)
Dear Paul; Yes, this is your bug report. It seems that the bug is likely specific to something about your setup, so we need more information to (possibly) figure out what is going on. As a first step, you could try % mv .mozilla-thunderbird .mozilla-thunderbird.bak % icedove and see if you still have persistent crashes. Also, as I mentioned in my last message, it would be helpful to know what IMAP server you are connecting to. I'm not aware of a simple way to find that out within icedove, but it may be helpful to run % telnet mailhost 143 and look at the greeting the server sends. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501988: /usr/bin/plasma: Plasma crashes when trying install new wallpapers
Package: kdebase-workspace-bin Version: 4:4.1.2-1 Severity: grave File: /usr/bin/plasma Justification: causes non-serious data loss I don't know what was. I'm was trying install wallpapers and Plasma show me the message "Problem while getting informations from server" or something like this. The, the crash. The backtrace: - Aplicativo: Área de trabalho do Plasma (plasma), sinal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb4999a90 (LWP 3441)] [New Thread 0xaae63b90 (LWP 4071)] [New Thread 0xab664b90 (LWP 4070)] [New Thread 0xabe65b90 (LWP 4069)] [New Thread 0xac666b90 (LWP 4068)] [New Thread 0xace67b90 (LWP 3978)] [New Thread 0xb1649b90 (LWP 3945)] [New Thread 0xb20bfb90 (LWP 3443)] [New Thread 0xb2a2cb90 (LWP 3442)] [KCrash handler] #6 KTranslatable (this=0xbffbbf8c, [EMAIL PROTECTED]) at /usr/include/qt4/QtCore/qatomic_i386.h:122 #7 0xb658f64e in KNS::Entry::preview (this=0xac18b38) at /tmp/buildd/kde4libs-4.1.2/knewstuff/knewstuff2/core/entry.cpp:175 #8 0xb65c1738 in KNS::ItemsModel::data (this=0xb1eff80, [EMAIL PROTECTED], role=44) at /tmp/buildd/kde4libs-4.1.2/knewstuff/knewstuff2/ui/itemsmodel.cpp:82 #9 0xb7462ece in QSortFilterProxyModel::data (this=0xa74d628, [EMAIL PROTECTED], role=44) at itemviews/qsortfilterproxymodel.cpp:1505 #10 0xb65c37a5 in KNS::ItemsViewDelegate::paint (this=0xb288388, painter=0xbffbc42c, [EMAIL PROTECTED], [EMAIL PROTECTED]) at /usr/include/qt4/QtCore/qabstractitemmodel.h:373 #11 0xb7402cc2 in QListView::paintEvent (this=0xb291b30, e=0xbffbcb6c) at itemviews/qlistview.cpp:1157 #12 0xb6f725ab in QWidget::event (this=0xb291b30, event=0xbffbcb6c) at kernel/qwidget.cpp:7301 #13 0xb72a5ca3 in QFrame::event (this=0xb291b30, e=0xbffbcb6c) at widgets/qframe.cpp:651 #14 0xb733c3cf in QAbstractScrollArea::viewportEvent (this=0xb291b30, e=0xbffbbf90) at widgets/qabstractscrollarea.cpp:943 #15 0xb73e788f in QAbstractItemView::viewportEvent (this=0xb291b30, event=0xbffbcb6c) at itemviews/qabstractitemview.cpp:1429 #16 0xb733e975 in QAbstractScrollAreaFilter::eventFilter (this=0xb2ab610, o=0xae860e8, e=0xbffbcb6c) at widgets/qabstractscrollarea_p.h:96 #17 0xb6b922ba in QCoreApplicationPrivate::sendThroughObjectEventFilters ( this=0x96be568, receiver=0xae860e8, event=0xbffbcb6c) at kernel/qcoreapplication.cpp:694 #18 0xb6f1a77a in QApplicationPrivate::notify_helper (this=0x96be568, receiver=0xae860e8, e=0xbffbcb6c) at kernel/qapplication.cpp:3799 #19 0xb6f226ea in QApplication::notify (this=0x96c18a8, receiver=0xae860e8, e=0xbffbcb6c) at kernel/qapplication.cpp:3768 #20 0xb7ac4c6d in KApplication::notify (this=0x96c18a8, receiver=0xae860e8, event=0xbffbcb6c) at /tmp/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311 #21 0xb6b930d1 in QCoreApplication::notifyInternal (this=0x96c18a8, receiver=0xae860e8, event=0xbffbcb6c) at kernel/qcoreapplication.cpp:587 #22 0xb6f7b1ee in qt_sendSpontaneousEvent (receiver=0xae860e8, event=0xbffbbf90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212 #23 0xb6f70f70 in QWidgetPrivate::drawWidget (this=0xb2c5870, #pdev=0xa7f715c, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4636 #24 0xb6f7171c in QWidgetPrivate::paintSiblingsRecursive (this=0xb41e8b8, pdev=0xa7f715c, [EMAIL PROTECTED], index=4, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=4, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4735 #25 0xb6f70be8 in QWidgetPrivate::drawWidget (this=0xb41e8b8, #pdev=0xa7f715c, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=4, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4677 #26 0xb6f7171c in QWidgetPrivate::paintSiblingsRecursive (this=0xb2b06b0, pdev=0xa7f715c, [EMAIL PROTECTED], index=11, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=4, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4735 #27 0xb6f70be8 in QWidgetPrivate::drawWidget (this=0xb2b06b0, #pdev=0xa7f715c, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=4, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4677 #28 0xb6f7171c in QWidgetPrivate::paintSiblingsRecursive (this=0xb2fbae0, pdev=0xa7f715c, [EMAIL PROTECTED], index=8, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=4, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4735 #29 0xb6f70be8 in QWidgetPrivate::drawWidget (this=0xb2fbae0, #pdev=0xa7f715c, [EMAIL PROTECTED], [EMAIL PROTECTED], flags=4, sharedPainter=0xb523b80) at kernel/qwidget.cpp:4677 #30 0xb70deaae in QWidgetBackingStore::cleanRegion (this=0xacca368, [EMAIL PROTECTED], widget=0x9bc0d40, recursiveCopyToScreen=true) at painting/qbackingstore.cpp:1035 #31 0xb70def77 in qt_syncBackingStore (widget=0x9bc0d40) at painting/qbackingstore.cpp:313 #32 0xb6f723d6 in QWidget::event (this=0x9bc0d40, event=0xb3afb38) at kernel/qwidget.cpp:7447 #33 0xb6f1a7
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > package libghc6-mtl-dev Ignoring bugs not assigned to: libghc6-mtl-dev > severity 498393 important Bug#498393: ghc-pkg: cannot find package mtl-1.0.1 (pre-removal scripts failed) Severity set to `important' from `critical' > kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475993: fslview package fixing RC-bugs
Dear Release Managers, the fslview package in lenny (3.0+4.0.2-3) is affected by three RC bugs (482209, 475993, 475993). All of them are fixed, since version 3.0+4.0.2-5, but it never got into testing due to a FTBFS on ARM. Recently, Yaroslav Halchenko was able to determine the cause of the bug (had already been reported): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475993#37 which has its origin in the VTK package and got fixed very recently http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492538 The package with all RC-bug fixes corresponding to the fslview upstream version currently in lenny is already in the archive http://ftp.debian.org/debian/pool/main/f/fslview/fslview_3.0+4.0.2-5.dsc However, in unstable it has already been replaced by a more recent upstream version. Can the above package be hinted into testing, or should I prepare a new upload to testing-proposed-updates? Thanks, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 signature.asc Description: Digital signature
Bug#498393: not a problem upgrading from etch
I installed libghc6-mtl-dev in an etch chroot, then used dist-upgrade to upgrade the whole chroot, and there was no problem upgrading libghc6-mtl-dev. David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501973: marked as done (enigmail: diff for NMU version 2:0.95.0+1-3.2)
Your message dated Sun, 12 Oct 2008 12:02:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#486491: fixed in enigmail 2:0.95.0+1-3.2
has caused the Debian Bug report #486491,
regarding enigmail: diff for NMU version 2:0.95.0+1-3.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
486491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486491
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: enigmail
Version: 2:0.95.0+1-3.1
Severity: normal
Tags: patch
Hi,
Attached is the diff for my enigmail 2:0.95.0+1-3.2 NMU.
Cheers,
Torsten
diff -u enigmail-0.95.0+1/debian/changelog enigmail-0.95.0+1/debian/changelog
--- enigmail-0.95.0+1/debian/changelog
+++ enigmail-0.95.0+1/debian/changelog
@@ -1,3 +1,12 @@
+enigmail (2:0.95.0+1-3.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix preinst to make sure the upgrade from old version actually works.
+(Closes: #486491, #468954)
+ * Add missing #DEBHELPER# token to preinst.
+
+ -- Torsten Werner <[EMAIL PROTECTED]> Sun, 12 Oct 2008 13:28:24 +0200
+
enigmail (2:0.95.0+1-3.1) unstable; urgency=low
* Non-maintainer upload to fix a long-standing RC bug in Debian.
diff -u enigmail-0.95.0+1/debian/enigmail.preinst enigmail-0.95.0+1/debian/enigmail.preinst
--- enigmail-0.95.0+1/debian/enigmail.preinst
+++ enigmail-0.95.0+1/debian/enigmail.preinst
@@ -6,17 +6,8 @@
-if test ! -d /usr/lib/enigmail/extension/; then
- mkdir -p /usr/lib/enigmail/
- cp -r '/usr/lib/thunderbird/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}' /usr/lib/enigmail/extension
-else
- rm -rf '/usr/lib/thunderbird/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
-fi
+rm -rf '/usr/lib/thunderbird/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
fi
if test -d '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'; then
-if test ! -d /usr/lib/enigmail/extension/; then
- mkdir -p /usr/lib/enigmail/
- cp -r '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}' /usr/lib/enigmail/extension
-else
- rm -rf '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
-fi
+rm -rf '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
fi
fi
+#DEBHELPER#
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:0.95.0+1-3.2
We believe that the bug you reported is fixed in the latest version of
enigmail, which is due to be installed in the Debian FTP archive:
enigmail_0.95.0+1-3.2.diff.gz
to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.diff.gz
enigmail_0.95.0+1-3.2.dsc
to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.dsc
enigmail_0.95.0+1-3.2_i386.deb
to pool/main/e/enigmail/enigmail_0.95.0+1-3.2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Torsten Werner <[EMAIL PROTECTED]> (supplier of updated enigmail package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 12 Oct 2008 13:28:24 +0200
Source: enigmail
Binary: enigmail
Architecture: source i386
Version: 2:0.95.0+1-3.2
Distribution: unstable
Urgency: low
Maintainer: Alexander Sack <[EMAIL PROTECTED]>
Changed-By: Torsten Werner <[EMAIL PROTECTED]>
Description:
enigmail - Enigmail - GPG support for Thunderbird
Closes: 468954 486491
Changes:
enigmail (2:0.95.0+1-3.2) unstable; urgency=low
.
* Non-maintainer upload.
* Fix preinst to make sure the upgrade from old version actually works.
(Closes: #486491, #468954)
* Add missing #DEBHELPER# token to preinst.
Checksums-Sha1:
d79345917497107265bd384a3ef8f0cca842e736 1158 enigmail_0.95.0+1-3.2.dsc
ff8f51290e0cb3040e3ae14d94d6d23aa81d780f 22152 enigmail_0.95.0+1-3.2.diff.gz
0398ceb3de85603514eae96ec958fbe0ee7ea5c8 337168 enigmail_0.95.0+1-3.2_i386.deb
Checksums-Sha256:
c5affe8b27e498afee07449ce903e3b88e41233cf888e7c7fb982ac06ac3dbf5 1158
enigmail_0.95.0+1-3.2.dsc
1733f70fccdd6524cdda4bd8fed31161ea3792aabcea2823d081bb9a99416240 22152
enigmail_0.95.0+1-3.2.diff.gz
57e60062f7ad60aea486307d23dfa51528fd69fb0be0b3884d48233c5e52f393 337168
enigmail_0.95.0+1-3.2_i386.deb
Files:
35bfd5b8aec021e6d1994d21d82df7dc 115
Bug#501973: marked as done (enigmail: diff for NMU version 2:0.95.0+1-3.2)
Your message dated Sun, 12 Oct 2008 12:02:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468954: fixed in enigmail 2:0.95.0+1-3.2
has caused the Debian Bug report #468954,
regarding enigmail: diff for NMU version 2:0.95.0+1-3.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
468954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468954
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: enigmail
Version: 2:0.95.0+1-3.1
Severity: normal
Tags: patch
Hi,
Attached is the diff for my enigmail 2:0.95.0+1-3.2 NMU.
Cheers,
Torsten
diff -u enigmail-0.95.0+1/debian/changelog enigmail-0.95.0+1/debian/changelog
--- enigmail-0.95.0+1/debian/changelog
+++ enigmail-0.95.0+1/debian/changelog
@@ -1,3 +1,12 @@
+enigmail (2:0.95.0+1-3.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix preinst to make sure the upgrade from old version actually works.
+(Closes: #486491, #468954)
+ * Add missing #DEBHELPER# token to preinst.
+
+ -- Torsten Werner <[EMAIL PROTECTED]> Sun, 12 Oct 2008 13:28:24 +0200
+
enigmail (2:0.95.0+1-3.1) unstable; urgency=low
* Non-maintainer upload to fix a long-standing RC bug in Debian.
diff -u enigmail-0.95.0+1/debian/enigmail.preinst enigmail-0.95.0+1/debian/enigmail.preinst
--- enigmail-0.95.0+1/debian/enigmail.preinst
+++ enigmail-0.95.0+1/debian/enigmail.preinst
@@ -6,17 +6,8 @@
-if test ! -d /usr/lib/enigmail/extension/; then
- mkdir -p /usr/lib/enigmail/
- cp -r '/usr/lib/thunderbird/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}' /usr/lib/enigmail/extension
-else
- rm -rf '/usr/lib/thunderbird/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
-fi
+rm -rf '/usr/lib/thunderbird/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
fi
if test -d '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'; then
-if test ! -d /usr/lib/enigmail/extension/; then
- mkdir -p /usr/lib/enigmail/
- cp -r '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}' /usr/lib/enigmail/extension
-else
- rm -rf '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
-fi
+rm -rf '/usr/lib/icedove/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
fi
fi
+#DEBHELPER#
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:0.95.0+1-3.2
We believe that the bug you reported is fixed in the latest version of
enigmail, which is due to be installed in the Debian FTP archive:
enigmail_0.95.0+1-3.2.diff.gz
to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.diff.gz
enigmail_0.95.0+1-3.2.dsc
to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.dsc
enigmail_0.95.0+1-3.2_i386.deb
to pool/main/e/enigmail/enigmail_0.95.0+1-3.2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Torsten Werner <[EMAIL PROTECTED]> (supplier of updated enigmail package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 12 Oct 2008 13:28:24 +0200
Source: enigmail
Binary: enigmail
Architecture: source i386
Version: 2:0.95.0+1-3.2
Distribution: unstable
Urgency: low
Maintainer: Alexander Sack <[EMAIL PROTECTED]>
Changed-By: Torsten Werner <[EMAIL PROTECTED]>
Description:
enigmail - Enigmail - GPG support for Thunderbird
Closes: 468954 486491
Changes:
enigmail (2:0.95.0+1-3.2) unstable; urgency=low
.
* Non-maintainer upload.
* Fix preinst to make sure the upgrade from old version actually works.
(Closes: #486491, #468954)
* Add missing #DEBHELPER# token to preinst.
Checksums-Sha1:
d79345917497107265bd384a3ef8f0cca842e736 1158 enigmail_0.95.0+1-3.2.dsc
ff8f51290e0cb3040e3ae14d94d6d23aa81d780f 22152 enigmail_0.95.0+1-3.2.diff.gz
0398ceb3de85603514eae96ec958fbe0ee7ea5c8 337168 enigmail_0.95.0+1-3.2_i386.deb
Checksums-Sha256:
c5affe8b27e498afee07449ce903e3b88e41233cf888e7c7fb982ac06ac3dbf5 1158
enigmail_0.95.0+1-3.2.dsc
1733f70fccdd6524cdda4bd8fed31161ea3792aabcea2823d081bb9a99416240 22152
enigmail_0.95.0+1-3.2.diff.gz
57e60062f7ad60aea486307d23dfa51528fd69fb0be0b3884d48233c5e52f393 337168
enigmail_0.95.0+1-3.2_i386.deb
Files:
35bfd5b8aec021e6d1994d21d82df7dc 115
Bug#468954: marked as done (enigmail: icedove does not detect upgrade to compatible version)
Your message dated Sun, 12 Oct 2008 12:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#468954: fixed in enigmail 2:0.95.0+1-3.2 has caused the Debian Bug report #468954, regarding enigmail: icedove does not detect upgrade to compatible version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 468954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468954 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: enigmail Version: 2:0.95.0+1-3.1 Severity: normal Hello, after updating enigmail to 2:0.95.0+1-3.1, icedove claims that enigmail 0.94.2 is installed. Which is incompatible with icedove 2.0.0.9 For me it looks like one step is missin g in the update from enigmail 2:0.94.2-2 so enigmail is unusable with icedove (on my computer). Greetings Juergen -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages enigmail depends on: ii gnupg 1.4.6-2+b1 GNU privacy guard - a free PGP rep ii icedove 2.0.0.9-3free/unbranded thunderbird mail/ne ii libc6 2.7-6GNU C Library: Shared libraries ii libgcc1 1:4.3-20080202-1 GCC support library ii libnspr4-0d 4.7.0~1.9b1-2NetScape Portable Runtime Library ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3 enigmail recommends no packages. -- no debconf information -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- End Message --- --- Begin Message --- Source: enigmail Source-Version: 2:0.95.0+1-3.2 We believe that the bug you reported is fixed in the latest version of enigmail, which is due to be installed in the Debian FTP archive: enigmail_0.95.0+1-3.2.diff.gz to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.diff.gz enigmail_0.95.0+1-3.2.dsc to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.dsc enigmail_0.95.0+1-3.2_i386.deb to pool/main/e/enigmail/enigmail_0.95.0+1-3.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner <[EMAIL PROTECTED]> (supplier of updated enigmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Oct 2008 13:28:24 +0200 Source: enigmail Binary: enigmail Architecture: source i386 Version: 2:0.95.0+1-3.2 Distribution: unstable Urgency: low Maintainer: Alexander Sack <[EMAIL PROTECTED]> Changed-By: Torsten Werner <[EMAIL PROTECTED]> Description: enigmail - Enigmail - GPG support for Thunderbird Closes: 468954 486491 Changes: enigmail (2:0.95.0+1-3.2) unstable; urgency=low . * Non-maintainer upload. * Fix preinst to make sure the upgrade from old version actually works. (Closes: #486491, #468954) * Add missing #DEBHELPER# token to preinst. Checksums-Sha1: d79345917497107265bd384a3ef8f0cca842e736 1158 enigmail_0.95.0+1-3.2.dsc ff8f51290e0cb3040e3ae14d94d6d23aa81d780f 22152 enigmail_0.95.0+1-3.2.diff.gz 0398ceb3de85603514eae96ec958fbe0ee7ea5c8 337168 enigmail_0.95.0+1-3.2_i386.deb Checksums-Sha256: c5affe8b27e498afee07449ce903e3b88e41233cf888e7c7fb982ac06ac3dbf5 1158 enigmail_0.95.0+1-3.2.dsc 1733f70fccdd6524cdda4bd8fed31161ea3792aabcea2823d081bb9a99416240 22152 enigmail_0.95.0+1-3.2.diff.gz 57e60062f7ad60aea486307d23dfa51528fd69fb0be0b3884d48233c5e52f393 337168 enigmail_0.95.0+1-3.2_i386.deb Files: 35bfd5b8aec021e6d1994d21d82df7dc 1158 mail optional enigmail_0.95.0+1-3.2.dsc 547e389c33fac8bed4d36e394eedf3b6 22152 mail optional enigmail_0.95.0+1-3.2.diff.gz 30ab4b95a2d7bd03d958fb309e00e79c 337168 mail optional enigmail_0.95.0+1-3.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjx474ACgkQfY3dicTPjsP9XwCfZv2Z676nySN7fiZdkY5ciGt2 i3MAn22UVD0r7W7ygr9IK21kyweB5KvF =CwBn -END PGP SIGNATURE- --- End Message ---
Bug#486491: marked as done (enigmail: does not upgrade from etch to lenny inside people's icedove)
Your message dated Sun, 12 Oct 2008 12:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#486491: fixed in enigmail 2:0.95.0+1-3.2 has caused the Debian Bug report #486491, regarding enigmail: does not upgrade from etch to lenny inside people's icedove to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 486491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486491 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: enigmail Version: 2:0.95.0+1-3.1 Severity: normal hi I have recently upgraded this box from etch to lenny. I just noted today that enigmail did not appear inside icedove anymore, so I went to check into the menu 'Tools -> extra components" (*) and the window was listing "enigmail 0.94 , not compatible with icedove 2.0.0-14" this was quite strange, since 'dpkg -l enigmail' was listing enigmail as being at version 0.95 so I deinstalled and reinstalled enigmail , and now it works fine you may want to check this fact before lenny is released a. (*) ps: I use it_IT locale, the above menu is a rough back translation -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages enigmail depends on: ii gnupg 1.4.6-2.2 GNU privacy guard - a free PGP rep ii icedove 2.0.0.14-1 free/unbranded thunderbird mail/ne ii libc6 2.7-11 GNU C Library: Shared libraries ii libgcc1 1:4.3.0-5 GCC support library ii libnspr4-0d 4.7.1-3NetScape Portable Runtime Library ii libstdc++64.3.0-5The GNU Standard C++ Library v3 enigmail recommends no packages. -- no debconf information -- Andrea Mennucc "The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do, and the GPL sounds like it was written by a human being who wants me to know what I can do." Anonymous,http://www.securityfocus.com/columnists/420 signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: enigmail Source-Version: 2:0.95.0+1-3.2 We believe that the bug you reported is fixed in the latest version of enigmail, which is due to be installed in the Debian FTP archive: enigmail_0.95.0+1-3.2.diff.gz to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.diff.gz enigmail_0.95.0+1-3.2.dsc to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.dsc enigmail_0.95.0+1-3.2_i386.deb to pool/main/e/enigmail/enigmail_0.95.0+1-3.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner <[EMAIL PROTECTED]> (supplier of updated enigmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Oct 2008 13:28:24 +0200 Source: enigmail Binary: enigmail Architecture: source i386 Version: 2:0.95.0+1-3.2 Distribution: unstable Urgency: low Maintainer: Alexander Sack <[EMAIL PROTECTED]> Changed-By: Torsten Werner <[EMAIL PROTECTED]> Description: enigmail - Enigmail - GPG support for Thunderbird Closes: 468954 486491 Changes: enigmail (2:0.95.0+1-3.2) unstable; urgency=low . * Non-maintainer upload. * Fix preinst to make sure the upgrade from old version actually works. (Closes: #486491, #468954) * Add missing #DEBHELPER# token to preinst. Checksums-Sha1: d79345917497107265bd384a3ef8f0cca842e736 1158 enigmail_0.95.0+1-3.2.dsc ff8f51290e0cb3040e3ae14d94d6d23aa81d780f 22152 enigmail_0.95.0+1-3.2.diff.gz 0398ceb3de85603514eae96ec958fbe0ee7ea5c8 337168 enigmail_0.95.0+1-3.2_i386.deb Checksums-Sha256: c5affe8b27e498afee07449ce903e3b88e41233cf888e7c7fb982ac06ac3dbf5 1158 enigmail_0.95.0+1-3.2.dsc 1733f70fccdd6524cdda4bd8fed31161ea3792aabcea2823d081bb9a99416240 22152 enigmail_0.95.0+1-3.2.diff.gz 57e60062f7ad60aea486307d23dfa51528fd69fb0be0b3884d48233c5e52f393 337168 enigmail_0.95.0+1-3.2_i386.deb Files: 35bfd5b8aec021e6d1994d21d82df7dc 1158 mail option
Bug#468954: marked as done (enigmail: icedove does not detect upgrade to compatible version)
Your message dated Sun, 12 Oct 2008 12:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#486491: fixed in enigmail 2:0.95.0+1-3.2 has caused the Debian Bug report #486491, regarding enigmail: icedove does not detect upgrade to compatible version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 486491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486491 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: enigmail Version: 2:0.95.0+1-3.1 Severity: normal Hello, after updating enigmail to 2:0.95.0+1-3.1, icedove claims that enigmail 0.94.2 is installed. Which is incompatible with icedove 2.0.0.9 For me it looks like one step is missin g in the update from enigmail 2:0.94.2-2 so enigmail is unusable with icedove (on my computer). Greetings Juergen -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages enigmail depends on: ii gnupg 1.4.6-2+b1 GNU privacy guard - a free PGP rep ii icedove 2.0.0.9-3free/unbranded thunderbird mail/ne ii libc6 2.7-6GNU C Library: Shared libraries ii libgcc1 1:4.3-20080202-1 GCC support library ii libnspr4-0d 4.7.0~1.9b1-2NetScape Portable Runtime Library ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3 enigmail recommends no packages. -- no debconf information -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- End Message --- --- Begin Message --- Source: enigmail Source-Version: 2:0.95.0+1-3.2 We believe that the bug you reported is fixed in the latest version of enigmail, which is due to be installed in the Debian FTP archive: enigmail_0.95.0+1-3.2.diff.gz to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.diff.gz enigmail_0.95.0+1-3.2.dsc to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.dsc enigmail_0.95.0+1-3.2_i386.deb to pool/main/e/enigmail/enigmail_0.95.0+1-3.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner <[EMAIL PROTECTED]> (supplier of updated enigmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Oct 2008 13:28:24 +0200 Source: enigmail Binary: enigmail Architecture: source i386 Version: 2:0.95.0+1-3.2 Distribution: unstable Urgency: low Maintainer: Alexander Sack <[EMAIL PROTECTED]> Changed-By: Torsten Werner <[EMAIL PROTECTED]> Description: enigmail - Enigmail - GPG support for Thunderbird Closes: 468954 486491 Changes: enigmail (2:0.95.0+1-3.2) unstable; urgency=low . * Non-maintainer upload. * Fix preinst to make sure the upgrade from old version actually works. (Closes: #486491, #468954) * Add missing #DEBHELPER# token to preinst. Checksums-Sha1: d79345917497107265bd384a3ef8f0cca842e736 1158 enigmail_0.95.0+1-3.2.dsc ff8f51290e0cb3040e3ae14d94d6d23aa81d780f 22152 enigmail_0.95.0+1-3.2.diff.gz 0398ceb3de85603514eae96ec958fbe0ee7ea5c8 337168 enigmail_0.95.0+1-3.2_i386.deb Checksums-Sha256: c5affe8b27e498afee07449ce903e3b88e41233cf888e7c7fb982ac06ac3dbf5 1158 enigmail_0.95.0+1-3.2.dsc 1733f70fccdd6524cdda4bd8fed31161ea3792aabcea2823d081bb9a99416240 22152 enigmail_0.95.0+1-3.2.diff.gz 57e60062f7ad60aea486307d23dfa51528fd69fb0be0b3884d48233c5e52f393 337168 enigmail_0.95.0+1-3.2_i386.deb Files: 35bfd5b8aec021e6d1994d21d82df7dc 1158 mail optional enigmail_0.95.0+1-3.2.dsc 547e389c33fac8bed4d36e394eedf3b6 22152 mail optional enigmail_0.95.0+1-3.2.diff.gz 30ab4b95a2d7bd03d958fb309e00e79c 337168 mail optional enigmail_0.95.0+1-3.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjx474ACgkQfY3dicTPjsP9XwCfZv2Z676nySN7fiZdkY5ciGt2 i3MAn22UVD0r7W7ygr9IK21kyweB5KvF =CwBn -END PGP SIGNATURE- --- End Message ---
Bug#486491: marked as done (enigmail: does not upgrade from etch to lenny inside people's icedove)
Your message dated Sun, 12 Oct 2008 12:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#468954: fixed in enigmail 2:0.95.0+1-3.2 has caused the Debian Bug report #468954, regarding enigmail: does not upgrade from etch to lenny inside people's icedove to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 468954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468954 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: enigmail Version: 2:0.95.0+1-3.1 Severity: normal hi I have recently upgraded this box from etch to lenny. I just noted today that enigmail did not appear inside icedove anymore, so I went to check into the menu 'Tools -> extra components" (*) and the window was listing "enigmail 0.94 , not compatible with icedove 2.0.0-14" this was quite strange, since 'dpkg -l enigmail' was listing enigmail as being at version 0.95 so I deinstalled and reinstalled enigmail , and now it works fine you may want to check this fact before lenny is released a. (*) ps: I use it_IT locale, the above menu is a rough back translation -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages enigmail depends on: ii gnupg 1.4.6-2.2 GNU privacy guard - a free PGP rep ii icedove 2.0.0.14-1 free/unbranded thunderbird mail/ne ii libc6 2.7-11 GNU C Library: Shared libraries ii libgcc1 1:4.3.0-5 GCC support library ii libnspr4-0d 4.7.1-3NetScape Portable Runtime Library ii libstdc++64.3.0-5The GNU Standard C++ Library v3 enigmail recommends no packages. -- no debconf information -- Andrea Mennucc "The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do, and the GPL sounds like it was written by a human being who wants me to know what I can do." Anonymous,http://www.securityfocus.com/columnists/420 signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: enigmail Source-Version: 2:0.95.0+1-3.2 We believe that the bug you reported is fixed in the latest version of enigmail, which is due to be installed in the Debian FTP archive: enigmail_0.95.0+1-3.2.diff.gz to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.diff.gz enigmail_0.95.0+1-3.2.dsc to pool/main/e/enigmail/enigmail_0.95.0+1-3.2.dsc enigmail_0.95.0+1-3.2_i386.deb to pool/main/e/enigmail/enigmail_0.95.0+1-3.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner <[EMAIL PROTECTED]> (supplier of updated enigmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Oct 2008 13:28:24 +0200 Source: enigmail Binary: enigmail Architecture: source i386 Version: 2:0.95.0+1-3.2 Distribution: unstable Urgency: low Maintainer: Alexander Sack <[EMAIL PROTECTED]> Changed-By: Torsten Werner <[EMAIL PROTECTED]> Description: enigmail - Enigmail - GPG support for Thunderbird Closes: 468954 486491 Changes: enigmail (2:0.95.0+1-3.2) unstable; urgency=low . * Non-maintainer upload. * Fix preinst to make sure the upgrade from old version actually works. (Closes: #486491, #468954) * Add missing #DEBHELPER# token to preinst. Checksums-Sha1: d79345917497107265bd384a3ef8f0cca842e736 1158 enigmail_0.95.0+1-3.2.dsc ff8f51290e0cb3040e3ae14d94d6d23aa81d780f 22152 enigmail_0.95.0+1-3.2.diff.gz 0398ceb3de85603514eae96ec958fbe0ee7ea5c8 337168 enigmail_0.95.0+1-3.2_i386.deb Checksums-Sha256: c5affe8b27e498afee07449ce903e3b88e41233cf888e7c7fb982ac06ac3dbf5 1158 enigmail_0.95.0+1-3.2.dsc 1733f70fccdd6524cdda4bd8fed31161ea3792aabcea2823d081bb9a99416240 22152 enigmail_0.95.0+1-3.2.diff.gz 57e60062f7ad60aea486307d23dfa51528fd69fb0be0b3884d48233c5e52f393 337168 enigmail_0.95.0+1-3.2_i386.deb Files: 35bfd5b8aec021e6d1994d21d82df7dc 1158 mail option
Processed: forcibly merging 468954 501973
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > forcemerge 468954 501973 Bug#468954: enigmail: icedove does not detect upgrade to compatible version Bug#501973: enigmail: diff for NMU version 2:0.95.0+1-3.2 Bug#486491: enigmail: does not upgrade from etch to lenny inside people's icedove Forcibly Merged 468954 486491 501973. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493169: wine: diff for NMU version 1.0.0-1.1
tags 493169 + patch pending
thanks
I could reproduce the bug by setting audio to JACK in winecfg and then
quitting winecfg, restarting it, and then playing the test sound.
Inspection with WINEDEBUG=trace+jack (and similar) and comparison with
the source seems to indicate that the crash happens when wine
registers the callback functions. This, combined with what I see on
the the bts (the report asking for libjack to be included into Debian)
the timeline of that, and the other comments on the web, leads me to
conclude that libwine-jack never worked on amd64 and should be removed.
I'm uploading the NMU attached below to delayed 2-day so you get a
change to protest.
Kind regards
T.
diff -u wine-1.0.0/debian/control wine-1.0.0/debian/control
--- wine-1.0.0/debian/control
+++ wine-1.0.0/debian/control
@@ -165,7 +165,7 @@
Package: libwine-jack
Section: libs
-Architecture: i386 hurd-i386 kfreebsd-i386 netbsd-i386 amd64 kfreebsd-amd64
powerpc hurd-powerpc kfreebsd-powerpc netbsd-powerpc sparc hurd-sparc
kfreebsd-sparc netbsd-sparc
+Architecture: i386 hurd-i386 kfreebsd-i386 netbsd-i386 powerpc hurd-powerpc
kfreebsd-powerpc netbsd-powerpc sparc hurd-sparc kfreebsd-sparc netbsd-sparc
Depends: ${shlibs:Depends}
Description: Windows API implementation - JACK sound module
Wine is a free MS-Windows API implementation.
diff -u wine-1.0.0/debian/rules wine-1.0.0/debian/rules
--- wine-1.0.0/debian/rules
+++ wine-1.0.0/debian/rules
@@ -302,7 +302,11 @@
mv debian/libwine/usr/lib/wine/d3dxof* debian/libwine-gl/usr/lib/wine
mv debian/libwine/usr/lib/wine/glu32*debian/libwine-gl/usr/lib/wine
mv debian/libwine/usr/lib/wine/opengl32* debian/libwine-gl/usr/lib/wine
+ifeq ($(DEB_HOST_GNU_CPU),x86_64)
+ rm debian/libwine/usr/lib/wine/winejack*
+else
mv debian/libwine/usr/lib/wine/winejack*
debian/libwine-jack/usr/lib/wine
+endif
mv debian/libwine/usr/lib/wine/wldap32*
debian/libwine-ldap/usr/lib/wine
mv debian/libwine/usr/lib/wine/winenas* debian/libwine-nas/usr/lib/wine
mv debian/libwine/usr/lib/wine/wineps*
debian/libwine-print/usr/lib/wine
diff -u wine-1.0.0/debian/changelog wine-1.0.0/debian/changelog
--- wine-1.0.0/debian/changelog
+++ wine-1.0.0/debian/changelog
@@ -1,3 +1,13 @@
+wine (1.0.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Disable libwine-jack on amd64 and kfreebsd-amd64 as libjack's
+callback architecture does not seem to work too well between
+wine using 32 bit libjack and jackd using 64 bit.
+Closes: #493169
+
+ -- Thomas Viehmann <[EMAIL PROTECTED]> Sun, 12 Oct 2008 10:57:43 +0200
+
wine (1.0.0-1) unstable; urgency=high
* New upstream release 1.0, released Jun 17, 2008.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: wine: diff for NMU version 1.0.0-1.1
Processing commands for [EMAIL PROTECTED]: > tags 493169 + patch pending Bug#493169: libwine-jack: segfaults on start (connection attempt to server) There were no tags set. Tags added: patch, pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 486491
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > tags 486491 + pending Bug#486491: enigmail: does not upgrade from etch to lenny inside people's icedove There were no tags set. Bug#468954: enigmail: icedove does not detect upgrade to compatible version Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492970: #492970 - nfs-common 1:1.1.3-1 client disallows access to files/directories where it should allow access - Debian Bug report logs
On Thu, Oct 09, 2008 at 11:48:08AM -0400, Steve Dickson wrote: >Unfortunately, I'm failing miserably on reproducing this... Here is >what I've done: > >Chuck Lever wrote: >>Hi Steve- >> >>As I understand it, the documented bug refers to running nfs-utils >>1.1.3 on kernels older than 2.6.22. > >I created a Fedora 7 KVM guest that runs a 2.6.21 kernel. I installed >the nfs-utils-1.1.3 (F-10) package along with supporting packages >(libgssglue, librpcsecgss and libnfsidmap). I did both mount commands > >mount -o sec=none madhat:/home /mnt/home >mount -o sec=sys madhat:/home /mnt/home > >and was able to write to both mount points. > >>To reproduce this you need to force the use of the legacy mount >>command that parses mount options in user space and passes a binary >>data structure to the kernel via mount(2). I've built util-linux using util-linux-ng-2.14.1.tar.bz2 which was taken from util-linux-ng-2.14.1-2.fc10.src.rpm In a chroot I run './configure; make; make install' and then I used the resulting /bin/mount to mount a file system from a server running 1.1.2 (kogi) on a client running 1.1.3 (hopi) and I still have the following error: [EMAIL PROTECTED]:/mnt/kogi/anibal$ echo hola > a bash: a: Permission denied >If this the case, we need a legacy mount command, then how can it be a >bug in nfs-utils-1.1.3? I've tried mount/umount from various packages: util-linux-ng-2.14.1-2.fc10.src.rpm util-linux_2.13.1.1-1 util-linux_2.14~rc2-0 util-linux_2.14-1ubuntu2 >At this point, this issue is the only one holding up the 1.1.4 release, >so I would like to address it... one way or the other... > >tia, > >steved. signature.asc Description: Digital signature
Bug#501970: perl: FTBFS on arm: ext/threads/shared/t/stress.t failure
Package: perl Version: 5.10.0-16 Severity: serious >From the arm buildd log: http://buildd.debian.org/fetch.cgi?pkg=perl;ver=5.10.0-16;arch=arm;stamp=1223623564 Automatic build of perl_5.10.0-16 on smackdown by sbuild/arm 98 Build started at 20081009-1253 [...] ext/threads/shared/t/stress...FAILED at test 1 [...] Failed 1 test out of 1433, 99.93% okay. ../ext/threads/shared/t/stress.t The test has succeeded on other buildd hosts earlier; while I did change the test to skip it on m68k (see #495826) for 5.10.0-15, the change really shouldn't affect other architectures, and -15 did build OK on hedges. [EMAIL PROTECTED]: could you please schedule a retry so we can see if the problem persists? Does smackdown have less resources than the others? -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
