Bug#587100: Acknowledgement ([INTL:kk] Kazakh translation update)

[Timur Birsh]

Hello,

There is some update to the translation.

Thanks,
Timur
#
# $Id: kk.po,v 1.1 2009-02-09 19:18:05 bubulle Exp $
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
#
# Baurzhan Muftakhidinov , 2008
# Dauren Sarsenov , 2009
#
msgid ""
msgstr ""
"Project-Id-Version: popularity-contest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2006-07-29 12:23+0200\n"
"PO-Revision-Date: 2010-07-03 12:11+0600\n"
"Last-Translator: Baurzhan Muftakhidinov \n"
"Language-Team: Kazakh \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:4
msgid "Participate in the package usage survey?"
msgstr "Дестелерді қолдану сауалнамасына қатысуды қалайсыз ба?"

#. Type: boolean
#. Description
#: ../templates:4
msgid "The system may anonymously supply the distribution developers with statistics about the most used packages on this system.  This information influences decisions such as which packages should go on the first distribution CD."
msgstr "Жүйе сіздің атыңызды қолданбай-ақ, дистрибутив шығарушыларға дестелер қолдануының статистикасын жібере алады. Бұл ақпарат оларға қандай дестелерді дистрибутивтің бірінші CD дискіне салу керек сияқты есептерді шешуге көмектеседі."

#. Type: boolean
#. Description
#: ../templates:4
msgid "If you choose to participate, the automatic submission script will run once every week, sending statistics to the distribution developers. The collected statistics can be viewed on http://popcon.debian.org/.";
msgstr "Егер сіз қатысуды таңдасаңыз, статистикалық деректер автоматты түрде әр апта сайын дистрибутив шығарушыларға жіберіліп тұрады. Жиналған статистиканы мына жерден көруге болады: http://popcon.debian.org/.";

#. Type: boolean
#. Description
#: ../templates:4
msgid "This choice can be later modified by running \"dpkg-reconfigure popularity-contest\"."
msgstr "Таңдауыңызды кейін \"dpkg-reconfigure popularity-contest\" командасын орындау арқылы өзгерте аласыз."

Bug#587208: Acknowledgement ([INTL:kk] Kazakh translation update)

[Timur Birsh]

Hello,

There is some update to the translation.

Thanks,
Timur
# Dauren Sarsenov , 2009
#
msgid ""
msgstr ""
"Project-Id-Version: win32-loader_i10n\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2010-05-05 16:09+0200\n"
"PO-Revision-Date: 2010-07-03 12:14+0600\n"
"Last-Translator: Baurzhan Muftakhidinov \n"
"Language-Team: Kazakh \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. translate:
#. This must be a valid string recognised by Nsis.  If your
#. language is not yet supported by Nsis, please translate the
#. missing Nsis part first.
#.
#: win32-loader.sh:36
#: win32-loader.c:39
msgid "LANG_ENGLISH"
msgstr "LANG_KAZAKH"

#. translate:
#. This must be the string used by GNU iconv to represent the charset used
#. by Windows for your language.  If you don't know, check
#. [wine]/tools/wmc/lang.c, or http://www.microsoft.com/globaldev/reference/WinCP.mspx
#.
#. IMPORTANT: In the rest of this file, only the subset of UTF-8 that can be
#. converted to this charset should be used.
#: win32-loader.sh:52
msgid "windows-1252"
msgstr "windows-1251"

#. translate:
#. Charset used by NTLDR in your localised version of Windows XP.  If you
#. don't know, maybe http://en.wikipedia.org/wiki/Code_page helps.
#: win32-loader.sh:57
msgid "cp437"
msgstr "cp866"

#. translate:
#. The name of your language _in English_ (must be restricted to ascii)
#: win32-loader.sh:67
msgid "English"
msgstr "Kazakh"

#. translate:
#. IMPORTANT: only the subset of UTF-8 that can be converted to NTLDR charset
#. (e.g. cp437) should be used in this string.  If you don't know which charset
#. applies, limit yourself to ascii.
#: win32-loader.sh:81
msgid "Continue with install process"
msgstr "Орнату үрдісімен жалғастыру"

#. translate:
#. The nlf file for your language should be found in
#. /usr/share/nsis/Contrib/Language files/
#.
#: win32-loader.c:68
msgid "English.nlf"
msgstr "Kazakh.nlf"

#: win32-loader.c:71
msgid "Installer Loader"
msgstr "Орнату бағдарламасын жүктеуші"

#: win32-loader.c:72
msgid "Cannot find win32-loader.ini."
msgstr "win32-loader.ini файлы табылмайды."

#: win32-loader.c:73
msgid "win32-loader.ini is incomplete.  Contact the provider of this medium."
msgstr "win32-loader.ini мазмұны толық емес. Осы дисктің таратушысымен хабарласыңыз."

#: win32-loader.c:74
msgid "This program has detected that your keyboard type is \"$0\".  Is this correct?"
msgstr "Бағдарлама сіздің пернетақтаңызды \"$0\" деп анықтады. Шынымен солай ма?"

#: win32-loader.c:75
msgid ""
"Please send a bug report with the following information:\n"
"\n"
" - Version of Windows.\n"
" - Country settings.\n"
" - Real keyboard type.\n"
" - Detected keyboard type.\n"
"\n"
"Thank you."
msgstr ""
"Келесі ақпараты бар қателер туралы хатты жіберуді өтінеміз:\n"
"\n"
" - Windows нұсқасы.\n"
" - Жергілікті параметрлер.\n"
" - Пернетақтаның нақты түрі.\n"
" - Пернетақтаның анықталған түрі.\n"
"\n"
"Көп рахмет."

#: win32-loader.c:76
msgid "There doesn't seem to be enough free disk space in drive $c.  For a complete desktop install, it is recommended to have at least 3 GB.  If there is already a separate disk or partition for this install, or if you plan to replace Windows completely, you can safely ignore this warning."
msgstr "$c дискісінің бос орны жеткіліксіз болуы мүмкін. Кәдімгі машинаға орнату үшін ұсынылатын бос орынның көлемі кемінде 3 ГБ құрайды. Орнату үшін бөлек диск не бөлім бар болса, не Windows жүйесін толығымен ауыстырамын десеңіз, бұл ескертуді елемей, жалғастыра беріңіз."

#: win32-loader.c:77
msgid "Error: not enough free disk space.  Aborting install."
msgstr "Қате: бос орын жеткіліксіз. Орнату тоқтатылды."

#: win32-loader.c:78
msgid "This program doesn't support Windows $windows_version yet."
msgstr "Бұл бағдарлама әзірге Windows $windows_version нұсқасын қолдамайды."

#: win32-loader.c:79
msgid ""
"The system version you're trying to install is designed to run on modern, 64-bit computers.  However, your computer is incapable of running 64-bit programs.\n"
"\n"
"Use the 32-bit (\"i386\") version, or the Multi-arch version which is able to install either of them.\n"
"\n"
"This installer will abort now."
msgstr ""
"Сіз орнатуды қалаған Debian нұсқасы осы күнгі, 64 разрядтық компьютерлерге арналған. Алайда, сіздің компьютеріңіз 64 разрядтық бағдарламаларды орындай алмайды.\n"
"\n"
"Debian жүйесінің 32 рязрядтық (\"i386\") нұсқасын немесе көп сәулетті нұсқаны қолданыңыз.\n"
"\n"
"Орнату бағдарламасы өз жұмысын тоқтатады."

#: win32-loader.c:80
msgid ""
"Your computer is capable of running modern, 64-bit operating systems.  However, the system version you're trying to install is designed to run on older, 32-bit hardware.\n"
"\n"
"You may still proceed with this install, but in order to take the most advantage of your computer, we recommend that you use the 64-bit (\"amd64\") version instead, or the Multi-arch version which is able to install either of them.\n"
"\n"
"Would you like to abo

Bug#402721: Please make clear, that "conflicts" should only be used when really necessary

[Guillem Jover]

Hi!

On Sat, 2010-07-03 at 13:28:26 -0700, Russ Allbery wrote:
> Tobias Frost  writes:
> > Looking at #262257, as an exampple, there are packages which declares
> > conflicts for whatever reason. However, the reason is NOT, that thec
> > packages could not co-existent on the same system (For the example,
> > retchmail could be also installed with fetchmail -- they do not
> > interfere)
> 
> > My wishlist-entry would be to clarify, tha conflicts should only be
> > used, if the packages "won't do" if both installed... (as the word
> > "conflict" implies. The reason "the other package is doing the same, so
> > conflict on it to prevent both installed" is -- IMHO -- not the
> > intention of conflicts

> This really should be common sense, but it doesn't hurt to say it
> explicitly, which I don't think we were doing before.  Here's a patch that
> implements that.

Yeah, but I've also witnessed (and reported) several of those for shared
libraries on SONAME bump.

> Objections or seconds?
> 
> diff --git a/policy.sgml b/policy.sgml
> index bad28af..efda2a1 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -4778,6 +4778,15 @@ Build-Depends: foo [linux-any], bar [any-i386], baz 
> [!linux-any]
>   
>  
>   
> +   Neither Breaks nor Conflicts should be used
> +   unless two packages cannot be installed at the same time or
> +   installing them both causes one of them to be broken or
> +   unusable.  Having similar functionality or performing the same
> +   tasks as another package is not sufficient reason to
> +   declare Breaks or Conflicts with that package.
> + 
> +
> + 
> A Conflicts entry may have an "earlier than" version
> clause if the reason for the conflict is corrected in a later
> version of one of the packages.  However, normally the presence

Seconded.

regards,
guillem


signature.asc
Description: Digital signature

Bug#588019: upgrading to blueman 1.21-4 fixes the problem

[Németh Márton]

After upgrading to blueman 1.21-4 (which is currently in sid,
see http://packages.debian.org/unstable/x11/blueman ) the problem
is fixed.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588019: more than one python version is installed

[Németh Márton]

Note that there is more than one python version installed on this
computer: python2.5 package version 2.5.5-6 and python2.6 version
2.6.5+20100630-2.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#555977: debian-policy: Constraints on binary package control files

[Guillem Jover]

Hi!

Here's a review from a non-native speaker.

On Sat, 2010-07-03 at 17:40:49 -0700, Russ Allbery wrote:
> diff --git a/policy.sgml b/policy.sgml
> index bad28af..3d5334d 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -804,6 +804,35 @@
>   in the .deb file format.
>
>  
> +  
> + A .deb package contains two sets of files: a set of files
> + to installed on the system when the package is installed, and a

/files to install/, instead of /files to be installed/ given that
there's an “installed” later on?

> + set of files that provide additional metadata about the package or
> + which are executed when the package is installed or removed.  This
> + second set of files is called control information files.
> + Among those files are the package maintainer scripts
> + and control, the binary
> + package control file that contains the control fields for
> + the package.  Other control information files
> + include the shlibs
> + file used to store shared library dependency information
> + and the conffiles file that lists the package's
> + configuration files (described in ).
> +  
> +
> +  
> + There is an unfortunately collision of terminology here between

/There is an unfortunate collision/ or /There is unfortunately a
collision/?

> + control information files and files in the Debian control file
> + format.  Throughout this document, a control file refers
> + to a file in the Debian control file format.  These files are
> + documented in .  Only files referred to
> + specifically as control information files are the files
> + included in the control information file member of
> + the .deb file format used by binary packages.  Most
> + control information files are not in the Debian control file
> + format.
> +  

The rest looked good to me.

regards,
guillem



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588021: jifty: Non-English manpages installed on standard (English) man page directory

[Raphael Geissert]

Package: libjifty-perl
Version: 0.91117+dfsg-1

Hi,

I just noticed via your override for lintian's spelling-error-in-manpage 
warning that the non-English man pages are not installed in the right 
directories. E.g.

usr/share/man/man3/Jifty::Manual::Tutorial_de.3pm.gz
should be moved to
usr/share/man/de/man3/Jifty::Manual::Tutorial.3pm.gz

(and yes, that silences lintian :)

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"

[jonat...@infinitedepth.com.au]

Hi Tomas,

Just worked around the same issue.

Purge the util-vserver package, then make sure you cleanup:

/usr/lib/util-vserver
/etc/vservers/.defaults
/var/lib/vservers

The real issue is old functionality in the "/usr/lib/util-vserver"
folder from etch / older versions.
Give that a shot and see how you go.

PS

Backup /etc/vservers before you purge, for that just in case scenario.


-- 

Kind
regards,




  


  
   Jonathan
Molyneux
  Infinitedepth
Consulting
jonat...@infinitedepth.com.au 

  

Bug#588020: mention cpio(5) on the man page

[jidanni]

Package: cpio
Version: 2.11-4
Severity: wishlist
File: /usr/share/man/man1/cpio.1.gz

Mention cpio(5) on the man page, like man tar does about tar:
SEE ALSO
 tar(5), symlink(7), rmt(8)

Also in the control file, "Suggest: package", for the package that
contains that man page, perhaps libarchive1.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588019: blueman: Unable to start: "ImportError: No module named ..."

[Márton Németh]

Package: blueman
Version: 1.21-3
Severity: grave
Justification: renders package unusable


When I upgraded to blueman 1.21-3 none of the /usr/bin/blueman-* programs
can be run anymore. The last line is always "ImportError: No module named ...".

Here is the complete error list of the blueman-* programs:

$ blueman-services 
Traceback (most recent call last):
  File "/usr/bin/blueman-services", line 11, in 
from blueman.gui.GenericList import GenericList
ImportError: No module named blueman.gui.GenericList
$ blueman-manager 
Traceback (most recent call last):
  File "/usr/bin/blueman-manager", line 34, in 
from blueman.Constants import *
ImportError: No module named blueman.Constants
$ blueman-sendto 
Traceback (most recent call last):
  File "/usr/bin/blueman-sendto", line 37, in 
from blueman.bluez.Adapter import Adapter
ImportError: No module named blueman.bluez.Adapter
$ blueman-applet 
Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 40, in 
from blueman.Constants import *
ImportError: No module named blueman.Constants
$ blueman-assistant 
Traceback (most recent call last):
  File "/usr/bin/blueman-assistant", line 44, in 
from blueman.Functions import *
ImportError: No module named blueman.Functions
$ blueman-adapters 
Traceback (most recent call last):
  File "/usr/bin/blueman-adapters", line 35, in 
import blueman.bluez as Bluez
ImportError: No module named blueman.bluez
$ blueman-browse 
Traceback (most recent call last):
  File "/usr/bin/blueman-browse", line 34, in 
from blueman.bluez.Manager import Manager
ImportError: No module named blueman.bluez.Manager


(There is a similar bugreport at https://bugs.launchpad.net/blueman/+bug/338181
which may be related.)

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages blueman depends on:
ii  bluez 4.66-1 Bluetooth tools and daemons
ii  dbus  1.2.24-1   simple interprocess messaging syst
ii  hicolor-icon-theme0.11-1 default fallback theme for FreeDes
ii  libbluetooth3 4.66-1 Library to use the BlueZ Linux Blu
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libcairo2 1.8.10-4   The Cairo 2D vector graphics libra
ii  libglib2.0-0  2.24.1-1   The GLib library of C routines
ii  libgtk2.0-0   2.20.1-1   The GTK+ graphical user interface 
ii  libpango1.0-0 1.28.1-1   Layout and rendering of internatio
ii  librsvg2-common   2.26.3-1   SAX-based renderer library for SVG
ii  libstartup-notification0  0.10-1 library for program launch feedbac
ii  notification-daemon   0.4.0-2a daemon that displays passive pop
ii  obex-data-server  0.4.5-1+b1 D-Bus service for OBEX client and 
ii  python2.6.5-5An interactive high-level object-o
ii  python-dbus   0.83.1-1   simple interprocess messaging syst
ii  python-gobject2.21.1-2   Python bindings for the GObject li
ii  python-gtk2   2.17.0-2   Python bindings for the GTK+ widge
ii  python-notify 0.1.1-2+b2 Python bindings for libnotify

Versions of packages blueman recommends:
ii  libpulse-mainloop-glib0   0.9.21-1   PulseAudio client libraries (glib 
ii  policykit-1   0.96-2 framework for managing administrat
ii  python-gconf  2.28.1-1   Python bindings for the GConf conf

blueman suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#581070: K3b Doesn't Add Symlinks in Folders

[Tsu Jan]

Hello,

Thanks for your reply and clear explanation. I upgraded to K3b 2.0.0-1 from 
Unstable but the bug is still present, i.e. K3b doesn't add a symlink to the 
burn project automatically when its containing folder 
is added. I'm in Debian Squeeze with the latest updates.

BTW, I couldn't find such a report at 
https://bugs.kde.org/buglist.cgi?quicksearch=k3b.

Regards,

Tsu



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588018: xinit: X11 freezes the whole machine, when playing video

[yellow]

Package: xinit
Version: 1.2.0-2
Severity: important

Dear Sir,

Unfortunaltely I would like to report you the just installed behavior, 
rather not well working. 

Console TTY and the pc is wokring well.
But as soon as I play a video , it has high chances that the whole pc 
freezes ;... no cold reset needed

if I play 2 video with mplayer at the same time, it freezes.

It is for any type of avi or mpeg or format

Ah; I forgot the machine is a : toshiba laptop SM30-404 

I hope that this issue can be solved. If you would like any info aboutth 
the pc , please let me know. 

Debian linux testing has been freshly installed and there is almost no 
packages; simply : sendmail firefox jwm wdm x11-apps xinit lxpanel alsa 
screen

Best regards
Y.

-- System Information:
Debian Release: 5.0.5
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (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 xinit depends on:
ii  coreutils 8.5-1  GNU core utilities
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libx11-6  2:1.3.3-3  X11 client-side library
ii  x11-common1:7.5+6X Window System (X.Org) infrastruc
ii  xauth 1:1.0.4-1  X authentication utility

Versions of packages xinit recommends:
ii  jwm [x-window-manager]2.0.1-3Very small lightweight pure X11 wi
ii  xserver-xorg  1:7.5+6the X.Org X server
ii  xserver-xorg-core [xserver]   2:1.7.7-2  Xorg X server - core server
ii  xterm [x-terminal-emulator]   259-1  X terminal emulator

xinit suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#400322: Limiting non-build-time relationships to a set of architectures?

[Russ Allbery]

Quoting a lot here for context on this old Policy bug.

Guillem Jover  writes:
> On Tue, 2010-02-09 at 20:25:11 +0100, Cyril Brulebois wrote:
>> Frans Pop  (09/02/2010):
>>> On Tuesday 09 February 2010, Cyril Brulebois wrote:
 Frans Pop  (09/02/2010):

> This format is not (yet) allowed by policy: rootskel-gtk
> (>=0.05) [!s390] (except for build dependencies)

 AFAICT, it just works, and not only for Build-Depends. It can't be
 used for an arch: all package, though, since it gets substituted at
 build time, so it probably won't do what you would want.

>>> I know that it is going to be allowed in the future and because of
>>> that I don't doubt that it (mostly?) works.  But AFAIK *currently*
>>> it's not allowed by policy [1], except for build deps. And thus it
>>> should not yet be used in uploads.

> Actually checking now, there does not seem to have been any wording
> proposed yet on #400322, I might try to come up with one.

>> Oops, indeed. Looks like I forgot about that particular point, thanks
>> for pointing this out. It looks like I've been taking it granted for
>> quite some time.

> Hmm, I also seem to have forgotten about this (I'll call that fair
> bias :). I was curious anyway about how long this support has been
> around as I thought it had been long, so did some digging the other
> day:

>  * Introduced in dpkg 1.10.11 (Tue, 16 Sep 2003 12:52:11 -0500)
>Bug: #170575

>  * Regression in dpkg 1.10.14 (Fri, 19 Sep 2003 12:29:34 -0500)

>  * Fixed again in dpkg 1.13.17 (Mon, 20 Mar 2006 03:33:03 +0200)
>Bugs: #252657, #324741, #347819

> Also I don't think much tools except for dpkg-dev scripts actually parse
> the dependency fields in the binary package stanzas in
> debian/control. So this should supposedly not break stuff (but then I've
> not checked, etc).

If this already works, we should document it, since it can be quite
useful.  Here's an attempt at wording.  Please check this and make sure
that I'm correctly documenting what works.

Do architecture restrictions work with Provides?  This documentation says
that they do, but I can easily correct that if it's wrong.

diff --git a/policy.sgml b/policy.sgml
index bad28af..316f753 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -4373,21 +4373,24 @@ Depends: libc6 (>= 2.2.1), exim | mail-transport-agent

 
 
-  All fields that specify build-time relationships
+ Relationships may be restricted to a certain set of
+ architectures.  This is indicated in brackets after each
+ individual package name and the optional version specification.
+ The brackets enclose a list of Debian architecture names
+ separated by whitespace.  Exclamation marks may be prepended to
+ each of the names.  (It is not permitted for some names to be
+ prepended with exclamation marks while others aren't.)
+   
+
+   
+ For build relationship fields
  (Build-Depends, Build-Depends-Indep,
- Build-Conflicts and Build-Conflicts-Indep)
- may be restricted to a certain set of architectures.  This
- is indicated in brackets after each individual package name and
- the optional version specification.  The brackets enclose a
- list of Debian architecture names separated by whitespace.
- Exclamation marks may be prepended to each of the names.
- (It is not permitted for some names to be prepended with
- exclamation marks while others aren't.) If the current Debian
- host architecture is not in this list and there are no
- exclamation marks in the list, or it is in the list with a
- prepended exclamation mark, the package name and the
- associated version specification are ignored completely for
- the purposes of defining the relationships.
+ Build-Conflicts and Build-Conflicts-Indep), if
+ the current Debian host architecture is not in this list and
+ there are no exclamation marks in the list, or it is in the list
+ with a prepended exclamation mark, the package name and the
+ associated version specification are ignored completely for the
+ purposes of defining the relationships.

 

@@ -4404,6 +4407,29 @@ Build-Depends: kernel-headers-2.2.10 [!hurd-i386],

 

+ For binary relationship fields, the architecture restriction
+ syntax is only supported in the source package control
+ file debian/control.  When the corresponding binary
+ package control file is generated, the relationship will either
+ be omitted or included without the architecture restriction
+ based on the architecture of the binary package.  This means
+ that architecture restrictions must not be used in binary
+ relationship fields for architecture-independent packages
+ (Architecture: all).
+   
+
+   
+ For examp

Bug#588017: perl: current directory in @INC potentially harmful

[Ansgar Burchardt]

Package: perl
Version: 5.10.1-13
Severity: grave
Tags: security

Hi,

perl includes the current directory as the last element in @INC when not
running in taint mode (-T).  As many modules try to load other modules
that may or may not be installed, this can result in code execution.

Example:

libtext-csv-perl is installed, libtext-csv-xs-perl is not installed.
When running "perl -mText::CSV" (or running any program using Text::CSV)
the file ./Text/CSV_XS.pm is loaded and the contained code executed.

Other examples include libjson-perl recommending libjson-xs-perl and
libyaml-perl recommending libyaml-syck-perl.

Regards,
Ansgar



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#584325: [nore...@lists.boost.org: Re: [Boost C++ Libraries] #2769: x86_64 + g++: wrong results for sin()]

[Steve M. Robbins]

On Wed, Jun 09, 2010 at 08:57:32AM +0200, Christophe TROESTLER wrote:
> On Tue, 8 Jun 2010 22:15:10 -0500, Steve M. Robbins wrote:
> > 
> > Further information from the Boost bug tracker (below).  It appears
> > this is a bug in the math library [1] and has been known for
> > nearly 8 years [2].
> 
> Is there any plan to eventually switch to something like crlibm [1]
> instead of libultim ?  Without a proper libm, the boost interval
> library is indeed pretty much useless...

From the web page, it sounds like crlibm would be a nice addition.  I
have no plans to do any such work.  It's worth asking about this on
the boost list.

-Steve


signature.asc
Description: Digital signature

Bug#477240: Please clarify status of XSI extensions for kill and trap

[Russ Allbery]

Raphael Geissert  writes:

>> diff --git a/policy.sgml b/policy.sgml
>> index bad28af..1658cbf 100644
>> --- a/policy.sgml
>> +++ b/policy.sgml
>> @@ -7427,7 +7427,19 @@ fname () {
>>  
>>must be supported and must set the value of c to
>>delta.
>> -
>> +
>> +The XSI extension to kill allowing kill
>> +  -signal, where signal is either
>> +  the name of a signal or one of the numeric signals listed in
>> +  the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
>> +  supported.
>> +
>> +The XSI extension to trap allowing numeric
>> +  symbols must be supported.  However, only the signal numbers

> s/symbols/signals/ ?

Whoops, yes.

>> +  listed in the extension, which are the same as
>> +  for kill above, plus SIGPIPE (13) must be
>> +  supported.

> Why did you phrase the second sentence that way? why not something like
> "In addition to the listed signal numbers, which are the same as for
> kill above, SIGPIPE (corresponding to number 13) must be
> supported?"

> The list of signal numbers which are part of the XSI extension are well
> defined, so there shouldn't be any reason to believe others are accepted
> too (and avoids the use of 'only ... must be supported,' which I think
> is easier to misinterpret.)

Yeah, I was trying too hard to avoid a problem which doesn't really
exist.  Here's an updated patch.

diff --git a/policy.sgml b/policy.sgml
index bad28af..8b715d0 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7427,7 +7427,18 @@ fname () {
 
  must be supported and must set the value of c to
  delta.
-
+   
+   The XSI extension to kill allowing kill
+ -signal, where signal is either
+ the name of a signal or one of the numeric signals listed in
+ the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
+ supported.
+   
+   The XSI extension to trap allowing numeric
+ signals must be supported.  In addition to the signal
+ numbers listed in the extension, which are the same as for
+ kill above, 13 (SIGPIPE) must be allowed.
+   
  
  If a shell script requires non-SUSv3 features from the shell
  interpreter other than those listed above, the appropriate shell

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#477240: Please clarify status of XSI extensions for kill and trap

[Raphael Geissert]

Hi Russ,

On Saturday 03 July 2010 18:49:40 Russ Allbery wrote:
> Here's a patch which implements that, plus an additional exception for
> libtool scripts which trap SIGPIPE by number.  Objections or seconds?
> I'm copying Clint as posh maintainer since this will be relevant to which
> features posh implements.

Thanks for coming up with the wording.
 
> diff --git a/policy.sgml b/policy.sgml
> index bad28af..1658cbf 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -7427,7 +7427,19 @@ fname () {
>  
> must be supported and must set the value of c to
> delta.
> -
> + 
> + The XSI extension to kill allowing kill
> +   -signal, where signal is either
> +   the name of a signal or one of the numeric signals listed in
> +   the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
> +   supported.
> + 
> + The XSI extension to trap allowing numeric
> +   symbols must be supported.  However, only the signal numbers

s/symbols/signals/ ?

> +   listed in the extension, which are the same as
> +   for kill above, plus SIGPIPE (13) must be
> +   supported.

Why did you phrase the second sentence that way? why not something like "In 
addition to the listed signal numbers, which are the same as for 
kill above, SIGPIPE (corresponding to number 13) must be 
supported?"

The list of signal numbers which are part of the XSI extension are well 
defined, so there shouldn't be any reason to believe others are accepted too 
(and avoids the use of 'only ... must be supported,' which I think is easier 
to misinterpret.)

> + 
> 
> If a shell script requires non-SUSv3 features from the shell
> interpreter other than those listed above, the appropriate shell

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


signature.asc
Description: This is a digitally signed message part.

Bug#586571: update posted to mentors.net

[Scott Evans]

Tags: moreinfo

I have uploaded version 1.3.0 to mentors.net, can you give this version a
try and advise if this handles this better than what you expected...

-- 
Scott Evans VK7HSE
Phone: +61362291658
Mobile: +61417586157
Skype: vk7hse
sc...@vk7hse.hobby-site.org
http://www.vk7hse.hobby-site.org
PGP/GPG Key ID 2B8CA152


--
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately 
by e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. If you are not the intended recipient you are notified 
that disclosing, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588015: [Pkg-hpijs-devel] Bug#588015: hplip: printing while unplugged/off says succeeds; hpcups filter response to run cupsenable should be automatic

[Mark Hedges]

On Sun, 4 Jul 2010, Mark Purcell wrote:
>
> Btw, could I ask you to use the reportbug(1) for future
> reports as that will also provide some further detail on
> your configuration which greatly assists with debug.
> (hp-check et al)

Uhh, I did use reportbug.  I guess it's not offering to run
hp-check anymore.  Should I file another bug?  ;-)

Here's the output of `hpcheck -r` as my user.  Thanks.  --mark--

hed...@maggie:~$ hp-check -r

HP Linux Imaging and Printing System (ver. 3.10.5)
Dependency/Version Check Utility ver. 14.3

Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied
tarball (.tar.gz or .run) to determine if the proper dependencies are installed 
to successfully
compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb,
.rpm, etc) or an already built HPLIP supplied tarball has the proper 
dependencies installed to
successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the
above cases (both compile- and run-time dependencies).

Saving output in log file: hp-check.log

Initializing. Please wait...

---
| SYSTEM INFO |
---

Basic system information:
Linux maggie.scriptdolphin.com 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 
i686 GNU/Linux

Distribution:
debian testing

Checking Python version...
OK, version 2.6.5 installed

Checking PyQt 4.x version...
OK, version 4.7.3 installed.

Checking for CUPS...
Status: scheduler is running
warning: Version: (Not available - cups-config. Unable to determine installed 
version of CUPS.)
error_log is set to level: warn

Checking for dbus/python-dbus...
dbus daemon is running.
python-dbus version: 0.83.1



| RUNTIME DEPENDENCIES |



Checking for dependency: CUPS - Common Unix Printing System...
OK, found.

Checking for dependency: CUPS DDK - CUPS driver development kit...
warning: NOT FOUND! This is an OPTIONAL/RUNTIME ONLY dependency. Some HPLIP 
functionality may not function properly.

Checking for dependency: GhostScript - PostScript and PDF language interpreter 
and previewer...
OK, found.

Checking for dependency: PIL - Python Imaging Library (required for commandline 
scanning with hp-scan)...
OK, found.

Checking for dependency: PolicyKit - Administrative policy framework...
OK, found.

Checking for dependency: PyQt 4 DBus - DBus Support for PyQt4...
OK, found.

Checking for dependency: Python DBus - Python bindings for DBus...
OK, found.

Checking for dependency: Python libnotify - Python bindings for the libnotify 
Desktop notifications...
OK, found.

Checking for dependency: Python XML libraries...
OK, found.

Checking for dependency: Python 2.3 or greater - Required for fax 
functionality...
OK, found.

Checking for dependency: Reportlab - PDF library for Python...
OK, found.

Checking for dependency: SANE - Scanning library...
OK, found.

Checking for dependency: scanimage - Shell scanning program...
OK, found.

Checking for dependency: xsane - Graphical scanner frontend for SANE...
OK, found.


--
| HPLIP INSTALLATION |
--


Currently installed HPLIP version...
HPLIP 3.10.5 currently installed in '/usr/share/hplip'.

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.10.5

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip-doc/HTML
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv

# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
pp-build=yes
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=yes
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.10.4.16
restricted-build=no
ui-toolkit=qt4
qt3=no
qt4=yes
policy-kit=yes
hpijs-only-build=no
lite-build=no
udev-acl-rules=yes
hpcups-only-build=no
hpijs-only-build=no


Current contents of '/var/lib/hp/hplip.state' file:
# hplip.state - HPLIP runtime persistent variables.

[plugin]
installed=0
eula=0



Current contents of '~/.hplip/hplip.conf' file:
[last_used]
printer_name = Deskjet_D2600_series
working_dir = .
device_uri = "hp:/usb/Deskjet_D2600_series?serial=TH964241X505C9"

[commands]
scan = /usr/bin/xsane -V %SANE_URI%

[installation]
version = 3.10.4.16
date_time = 07/03/2010 20:31:11

[settings]
systray_messages = 0
systray_visible 

Bug#588015: [Pkg-hpijs-devel] Bug#588015: hplip: printing while unplugged/off says succeeds; hpcups filter response to run cupsenable should be automatic

[Mark Purcell]

On Sunday 04 July 2010 13:10:46 Mark Hedges wrote:
> It seems like /usr/lib/cups/filter/hpcups could automatically run `cupsenable`
> when it detects this condition.  Or, is this a bug in package hal-cups-utils?

Thanks Mark,

Sounds like a reasonable idea.  I shall also forward upstream.

Btw, could I ask you to use the reportbug(1) for future reports as that will 
also provide some further detail on your configuration which greatly assists 
with debug. (hp-check et al)

Mark


signature.asc
Description: This is a digitally signed message part.

Bug#588016: fwbuilder-doc: example init script lacks INIT INFO

[ross]

Package: fwbuilder-doc
Version: 3.0.7-1
Severity: normal


The documentation could use some help to work with Squeeze.

I added this near the top of /etc/init.d/fwbuilder:
### BEGIN INIT INFO
# Provides:  firewall
# Required-Start:$network
# Required-Stop: $network
# Default-Start: S
# Default-Stop:  0 6
# Short-Description: Runs iptables firewall script
### END INIT INFO

I dropped a file with the following into /etc/dhcp3/dhclient-exit-hooks.d/:
RUN="yes"
if [ "$RUN" = "yes" ]; then
case $reason in
BOUND|RENEW|REBIND|REBOOT)
if [ "$interface" = "eth1" ] && [ "$new_ip_address" != 
"$old_ip_address" ]; then
invoke-rc.d fwbuilder restart
fi
;;
esac
fi


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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588015: hplip: printing while unplugged/off says succeeds; hpcups filter response to run cupsenable should be automatic

[Mark Hedges]

Package: hplip
Version: 3.10.5-3.2
Severity: normal


I have a D2660.  If I print while the printer is unplugged or
turned off, I still get status notifications that printing
has started and completed successfully.  Then I plug the 
printer in, and see the following in syslog:

Jul  3 19:55:05 maggie kernel: [390445.368077] usb 1-3: new high speed USB 
device using ehci_hcd and address 19
Jul  3 19:55:06 maggie kernel: [390445.503678] usb 1-3: New USB device found, 
idVendor=03f0, idProduct=8011
Jul  3 19:55:06 maggie kernel: [390445.503725] usb 1-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Jul  3 19:55:06 maggie kernel: [390445.503732] usb 1-3: Product: Deskjet D2600 
series
Jul  3 19:55:06 maggie kernel: [390445.503738] usb 1-3: Manufacturer: HP
Jul  3 19:55:06 maggie kernel: [390445.503742] usb 1-3: SerialNumber: 
TH964241X505C9
Jul  3 19:55:06 maggie kernel: [390445.503944] usb 1-3: configuration #1 chosen 
from 1 choice
Jul  3 19:55:06 maggie kernel: [390445.506581] usblp0: USB Bidirectional 
printer dev 19 if 0 alt 0 proto 2 vid 0x03F0 pid 0x8011
Jul  3 19:55:07 maggie hal_lpadmin: add
Jul  3 19:55:07 maggie hal_lpadmin: URIs: 
['hp:/usb/Deskjet_D2600_series?serial=TH964241X505C9', 
'usb://HP/Deskjet%20D2600%20series?serial=TH964241X505C9', 
'hal:///org/freedesktop/Hal/devices/usb_device_3f0_8011_TH964241X505C9_if0_printer_TH964241X505C9']
Jul  3 19:55:07 maggie hal_lpadmin: HPLIP Fax URIs: None
Jul  3 19:55:07 maggie hal_lpadmin: Not adding printer: Deskjet_D2600_series 
already exists
Jul  3 19:55:07 maggie hal_lpadmin: Printer Deskjet_D2600_series exists but is 
disabled, reason: /usr/lib/cups/filter/hpcups failed; use 'cupsenable 
Deskjet_D2600_series' to enable it

When I run `cupsenable Deskjet_D2600_series`, printing starts
for the job that I printed earlier while it was unplugged, it
completes successfully and I get a status notification that
it finished.  syslog then contains the following:

Jul  3 19:55:15 maggie kernel: [390455.306909] usblp0: removed
Jul  3 19:55:16 maggie hal_lpadmin: remove
Jul  3 19:55:16 maggie hal_lpadmin: Found configured printer: 
Deskjet_D2600_series

It seems like /usr/lib/cups/filter/hpcups could automatically run `cupsenable`
when it detects this condition.  Or, is this a bug in package hal-cups-utils?

Thanks.  --mark--

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages hplip depends on:
ii  adduser   3.112  add and remove users and groups
ii  coreutils 8.5-1  GNU core utilities
ii  cups  1.4.3-1Common UNIX Printing System(tm) - 
ii  cups-client   1.4.3-1Common UNIX Printing System(tm) - 
ii  hplip-cups3.10.5-3.2 HP Linux Printing and Imaging - CU
ii  hplip-data3.10.5-3.2 HP Linux Printing and Imaging - da
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libcups2  1.4.3-1Common UNIX Printing System(tm) - 
ii  libdbus-1-3   1.2.24-1   simple interprocess messaging syst
ii  libhpmud0 3.10.5-3.2 HP Multi-Point Transport Driver (h
ii  libsane   1.0.21-2   API library for scanners
ii  libssl0.9.8   0.9.8o-1   SSL shared libraries
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip
ii  policykit-1   0.96-2 framework for managing administrat
ii  python2.6.5-5An interactive high-level object-o
ii  python-dbus   0.83.1-1   simple interprocess messaging syst
ii  python-imaging1.1.7-1+b1 Python Imaging Library
ii  python-notify 0.1.1-2+b2 Python bindings for libnotify
ii  python-pexpect2.3-1  Python module for automating inter
ii  python-support1.0.8  automated rebuilding support for P

Versions of packages hplip recommends:
ii  avahi-daemon  0.6.25-3   Avahi mDNS/DNS-SD daemon
ii  hpijs 3.10.5-3.2 HP Linux Printing and Imaging - gs
ii  sane-utils1.0.21-2   API library for scanners -- utilit

Versions of packages hplip suggests:
ii  gtklp 1.2.7-2printing tool for CUPS on the GNOM
ii  hplip-doc 3.10.5-1   HP Linux Printing and Imaging - do
ii  hplip-gui 3.10.5-3.2 HP Linux Printing and Imaging - GU

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565144: hplip: same problem with D2660 - hp-toolbox reports status 'Good/OK' but bar is empty.

[Mark Hedges]

Package: hplip
Version: 3.10.5-3.2
Severity: normal


I have the same problem with my D2660.  hp-toolbox says the
status of the black 60/60XL cartridge is 'Good/OK' but the
bar is empty (and printing greyscale prints blank pages).
The color cartridge indicator functions correctly.  --mark--

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages hplip depends on:
ii  adduser   3.112  add and remove users and groups
ii  coreutils 8.5-1  GNU core utilities
ii  cups  1.4.3-1Common UNIX Printing System(tm) - 
ii  cups-client   1.4.3-1Common UNIX Printing System(tm) - 
ii  hplip-cups3.10.5-3.2 HP Linux Printing and Imaging - CU
ii  hplip-data3.10.5-3.2 HP Linux Printing and Imaging - da
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libcups2  1.4.3-1Common UNIX Printing System(tm) - 
ii  libdbus-1-3   1.2.24-1   simple interprocess messaging syst
ii  libhpmud0 3.10.5-3.2 HP Multi-Point Transport Driver (h
ii  libsane   1.0.21-2   API library for scanners
ii  libssl0.9.8   0.9.8o-1   SSL shared libraries
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip
ii  policykit-1   0.96-2 framework for managing administrat
ii  python2.6.5-5An interactive high-level object-o
ii  python-dbus   0.83.1-1   simple interprocess messaging syst
ii  python-imaging1.1.7-1+b1 Python Imaging Library
ii  python-notify 0.1.1-2+b2 Python bindings for libnotify
ii  python-pexpect2.3-1  Python module for automating inter
ii  python-support1.0.8  automated rebuilding support for P

Versions of packages hplip recommends:
ii  avahi-daemon  0.6.25-3   Avahi mDNS/DNS-SD daemon
ii  hpijs 3.10.5-3.2 HP Linux Printing and Imaging - gs
ii  sane-utils1.0.21-2   API library for scanners -- utilit

Versions of packages hplip suggests:
ii  gtklp 1.2.7-2printing tool for CUPS on the GNOM
ii  hplip-doc 3.10.5-1   HP Linux Printing and Imaging - do
ii  hplip-gui 3.10.5-3.2 HP Linux Printing and Imaging - GU

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587996: [Bug 243549] Re: k3b: Media info reports seemingly random capacity for 25GB BD-R

[Mark Purcell]

forwarded 587996 https://bugs.kde.org/show_bug.cgi?id=243549
tags 587996 upstream
thanks


On Sunday 04 July 2010 04:18:57 Peter Karbaliotis wrote:
> The drive is an LG BH10.  It would be nice if k3b can be patched so that the
> actual disc capacity is 3.5 TiB.  I won't hold my breath though.  :-)

Peter,

Thanks for your report, this is an upstream issue as there is little Debian can 
do to patch.  I have forwarded your report upstream, but please feel free to 
include any further comments with the upstream report.

Thanks,
Mark


The Debian team values users reports, but we are busy, and so we
kindly ask you to access the upstream support facilities:

There is a user mailing list which maybe used to get support:
http://lists.sourceforge.net/lists/listinfo/k3b-user

To post a message to all the list members, send email to 
k3b-u...@lists.sourceforge.net.


If you know that the bug you want to report is in the "upstream"
code then please check/ file against the KDE Bug tracking system:
https://bugs.kde.org/buglist.cgi?quicksearch=k3b

You can also report bugs directly upstream using the K3b Help:Report Bug
menu entry.


If you feel that the bug is one that other Debian users should
know about then you are welcome to file a report in the Debian BTS
as well.  Please keep in mind, however, that managing bug reports
is part of the maintainers' workload.

As a minimum we ask that you Cc: k3b-u...@lists.sourceforge.net any
reports you file in the Debian Bug Tracking system so that upstream
are aware of the issue you are reporting.


signature.asc
Description: This is a digitally signed message part.

Bug#186102: version numbering for date-releases is flawed

[Russ Allbery]

Josip Rodin  writes:

> The Policy section "Version numbers based on dates" recommends using
> simply MMDD for versions based on dates.

> However, it is not uncommon for upstream authors to release date-based
> versions for betas, and then later switch to e.g. 1.0 for "proper"
> releases.  In such cases, people who used MMDD need to use epochs to
> switch to X.Y.

> This would be fixed by recommending to prepending additional zeros to
> MMDD. I would probably go for 0.0.MMDD. Someone else might want
> more?

The text referred to in this bug is section 3.2.1, which says:

 In general, Debian packages should use the same version numbers as the
 upstream sources.

 However, in some cases where the upstream version number is based on a
 date (e.g., a development "snapshot" release) the package management
 system cannot handle these version numbers without epochs.  For
 example, dpkg will consider "96May01" to be greater than "96Dec24".

 To prevent having to use epochs for every new upstream version, the
 date based portion of the version number should be changed to the
 following format in such cases: "19960501", "19961224".  It is up to
 the maintainer whether they want to bother the upstream maintainer to
 change the version numbers upstream, too.

 Note that other version formats based on dates which are parsed
 correctly by the package management system should _not_ be changed.

 Native Debian packages (i.e., packages which have been written
 especially for Debian) whose version numbers include dates should
 always use the "MMDD" format.

I agree that we shouldn't be recommending MMDD alone for upstream
snapshot releases for the reasons stated in the bug report.  The bug
report predates the introduction of ~, though, which now offers a better
solution to this problem than was available.

However, I think this whole bit really doesn't belong in Policy.  For
packages that are snapshot-based with no regular version number but one
that might show up later, I'd use 0~MMDD.  For ones that are
pre-releases, I'd use ~MMDD.  For ones that postdate an
existing version, I'd use +MMDD.  But all of that feels
like best practices stuff.

Similarly, I'm not seeing why we should say MMDD should be used for
Debian native packages, as opposed to .MM.DD or some other format that
sorts properly.

I therefore think we should rewrite this whole section to remove most of
the details and instead just say not to ever use date-based formats like
96May01 and instead use something based off of MMDD, possibly with
punctuation (but not -).

If that sounds good, I can work on new language.

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Ben Finney]

On 04-Jul-2010, Leo 'costela' Antunes wrote:
> I can't really pinpoint where or how the config-file could have been
> deleted by the maintainer scripts.

I've inspected the VCS logs (I'm using ‘etckeeper’ to track changes in
the ‘/etc/’ tree). The following occurred on 2006-06-16:

=
revno: 107
committer: root 
branch nick: poppy /etc repository
timestamp: Wed 2010-06-16 08:43:28 +1000
message:
  daily autocommit
removed:
  transmission-daemon/settings.json
added:
  transmission-daemon/settings.json.tmp.LZ8ccU
modified:
  .etckeeper
=

and nothing touched anything inside ‘/etc/transmission-daemon/’ since
then.

There was no corresponding Aptitude run on that date, so perhaps it
wasn't done by the packaging scripts at all.

Do you know of a behaviour of any of the Transmission programs that
could have caused this?

-- 
 \“As soon as I get through with you, you'll have a clear case |
  `\   for divorce and so will my wife.” —Groucho Marx |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature

Bug#568293: Related Problem here ...

[Tilo Werner]

Hi,

I'm running a Squeeze 64bit box with ubuntu 10.4 64bit guest and a Windows XP 
32 bit guest. I'm using libvirt for managing.

The second one hangs up randomly causing one cpu of the host system to stay at 
100% load. Randomly means 1-2 times a day :-(. I've searched the net but the 
only useful thing I found was this bugreport and:

http://www.mail-archive.com/kvm-de...@lists.sourceforge.net/msg15009.html

and someone obviously having the same problem:

http://serverfault.com/questions/149098/how-do-i-run-a-stable-windows-xp-kvm-
guest-on-ubuntu-10-04

My setup:

qemu-kvm:

Architecture: amd64
Version: 0.12.4+dfsg-1

libvirt-bin:

Architecture: amd64
Source: libvirt (0.8.1-2)
Version: 0.8.1-2+b1

kvm commandline of the XP guest:

/usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 512 -smp 
1,sockets=1,cores=1,threads=1 -name virtxp -uuid 
012f9c55-3620-70af-9bda-620ce8b599ab -nodefaults -chardev 
socket,id=monitor,path=/var/lib/libvirt/qemu/virtxp.monitor,server,nowait -mon 
chardev=monitor,mode=readline -rtc base=utc -boot c -drive 
file=/home/tilo/Downloads/isos/grml_2010.04.iso,if=none,media=cdrom,id=drive-
ide0-1-0,readonly=on -device ide-drive,bus=ide.1,unit=0,drive=drive-
ide0-1-0,id=ide0-1-0 -drive file=/dev/vol1/virtxp,if=none,id=drive-virtio-
disk0,boot=on -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-
disk0,id=virtio-disk0 -device virtio-net-
pci,vlan=0,id=net0,mac=52:54:00:90:1e:d4,bus=pci.0,addr=0x4 -net 
tap,fd=42,vlan=0,name=hostnet0 -usb -device usb-tablet,id=input0 -vnc 
127.0.0.1:1 -k de -vga vmware -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x3

After writing I will try to use the standard drivers for ethernet and display. 
I had this problem also before switching to virtio drivers ... But I will try.

Please let me know what further information you need.

Thank you,
Tilo



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Leo 'costela' Antunes]

On 04/07/10 03:14, Ben Finney wrote:

>> The deamon was working OK before the upgrade, right?
> 
> I think so, though I've not yet succeeded in starting any torrents
> using Transmission. Certainly there were never any errors from the
> packaging nor the running programs.

I can't really pinpoint where or how the config-file could have been
deleted by the maintainer scripts. To go around this problem I'll just
make the chowns conditional in the next upload (2.01-1, hopefully
tomorrow), but this means the underlying reason for the file's
disappearance is still a mystery.

The preinst script has code which *could* have something to do with it,
but the logic seems innocuous enough. Regardless, I'll keep an eye on
it, but if you happen to remember you rm'd it at some point, let me know! :)


Cheers

-- 
Leo "costela" Antunes
[insert a witty retort here]



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#445203: debian-policy: 10.8. Log files: /etc/logrotate.d/ preferred

[Raphael Geissert]

On Saturday 03 July 2010 20:13:19 Russ Allbery wrote:
> Good point.  Here's an updated patch.
> 
> diff --git a/policy.sgml b/policy.sgml
> index bad28af..9399b1a 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -7868,11 +7868,13 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
>   
> 
>   
> -   Log files must be rotated occasionally so that they don't
> -   grow indefinitely; the best way to do this is to drop a log
> -   rotation configuration file into the directory
> -   /etc/logrotate.d and use the facilities provided by
> -   logrotate.
> +   Log files must be rotated occasionally so that they don't grow
> +   indefinitely.  The best way to do this is to install a log
> +   rotation configuration file in the
> +   directory /etc/logrotate.d, normally
> +   named /etc/logrotate.d/package, and use
> +   the facilities provided by logrotate.
> +   
>   
> The traditional approach to log files has been to set up
> ad hoc log rotation schemes using simple shell
> @@ -7897,25 +7899,28 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
>   section="8">):
> 
>  /var/log/foo/*.log {
> -rotate 12
> -weekly
> -compress
> -postrotate
> -/etc/init.d/foo force-reload
> -endscript
> +rotate 12
> +weekly
> +compress
> +missingok
> +postrotate
> +invoke-rc.d foo force-reload
> +endscript
>  }
> 
> This rotates all files under /var/log/foo, saves 12
> compressed generations, and forces the daemon to reload its
> -   configuration information after the log rotation.
> +   configuration information after the log rotation.  It skips this
> +   log rotation (via missingok) if no such log file is
> +   present, which avoids errors if the package is removed but not
> +   purged.
>   
> 
>   
> -   Log files should be removed when the package is
> -   purged (but not when it is only removed).  This should be
> -   done by the postrm script when it is called
> -   with the argument purge (see  -   id="removedetails">).
> +   Log files should be removed when the package is purged (but not
> +   when it is only removed).  This should be done by
> +   the postrm script when it is called with the
> +   argument purge (see ).
>   
>

Seconded.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


signature.asc
Description: This is a digitally signed message part.

Bug#247465: libxslt precision and GCC

[brian m. carlson]

libxslt does not currently respect IEEE semantics on i386.  However,
starting with GCC 4.5, there is an option called
-fexcess-precision=standard; this option is enabled by default with
-std=c99.

Vincent, can you test-build libxslt with GCC 4.5 using one of those
options and confirm if that fixes the breakage?

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#588014: debian-policy: Dm-Upload-Allowed field is not documented

[Raphael Geissert]

Package: debian-policy
Version: 3.9.0
Severity: wishlist

Hi,

I just noticed the Dm-Upload-Allowed field is not documented at all. Even 
though it was introduced by the means of a GR, I think there's no reason for 
it not to be documented in debian-policy.

Only the syntax and its "current agreed meaning" should be documented, so that 
it is clear that it doesn't (and there is no intention to) overrule the GR.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


signature.asc
Description: This is a digitally signed message part.

Bug#290049: zlib rsyncable

[Mark Brown]

On 4 Jul 2010, at 08:04, Thorsten Glaser  wrote:

> Hi,
> 
> any progress (forwarded to)?

It's been mentioned upstream before now but there's nobody been actively 
pushing anything recently. 

> I have another “hat” on, as BSD developer (who use a zlib based
> compress instead of GNU gzip) I’d also be interested in having
> that upstream… in dpkg it would of course also make sense.

If you're interested I suggest working directly upstream to try to push 
whatever implementation you prefer; an enthusiastic user can't hurt. Not sure 
why nobody seems to do this directly when they write code. I think anything 
useful would have to either extend the API or do something smart with the 
compression level options (which was the main problem with the previous patch 
IIRC). 


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Ben Finney]

On 04-Jul-2010, Leo 'costela' Antunes wrote:
> On 04/07/10 02:45, Ben Finney wrote:
> > The package is already unpacked; should I just try unpacking it again?
> 
> Yes please.

=
$ sudo dpkg --unpack /var/cache/apt/archives/transmission-daemon_2.00-1_i386.deb
(Reading database ... 298301 files and directories currently installed.)
Preparing to replace transmission-daemon 2.00-1 (using 
.../transmission-daemon_2.00-1_i386.deb) ...
 * Stopping bittorrent daemon transmission-daemon
   ...done.
Unpacking replacement transmission-daemon ...
Processing triggers for man-db ...

$ sudo dpkg --configure --pending
Setting up transmission-daemon (2.00-1) ...
chown: cannot access `/etc/transmission-daemon/settings.json': No such file or 
directory
dpkg: error processing transmission-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 transmission-daemon
=

> The deamon was working OK before the upgrade, right?

I think so, though I've not yet succeeded in starting any torrents
using Transmission. Certainly there were never any errors from the
packaging nor the running programs.

-- 
 \  “Those who write software only for pay should go hurt some |
  `\ other field.” —Erik Naggum, in _gnu.misc.discuss_ |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature

Bug#586953: quits command line mode when holding down arrow keys

[Jörg Sommer]

Hi Vladimir,

Vladimir 'φ-coder/phcoder' Serbinenko hat am Fri 02. Jul, 22:21 (+0200) 
geschrieben:
> On 06/21/2010 04:06 PM, Jörg Sommer wrote:
> > Package: grub-ieee1275
> > Version: 1.98+20100617-1
> > Severity: normal
> > Tags: upstream
> >
> > Hi,
> >
> > when switch to the editing mode or the commandline mode from the menu and
> > hold down an arrow key, e.g. right arrow to move to the end of line, the
> > editing mode quits and I'm back to the menu.
> >
> > To me it looks like the arrow keys send multi‐character sequences
> > starting with an escape character. The escape character is used to leave
> > the editing mode, hence the escape is misinterpreted when the key is held
> > down.
> >
> >   
> Could you try the latest upstream bzr?

Sorry for the stupid question: is it available as a Debian package? From
where can I fetch it?

BTW: The named URL in copyright is invalid.

% LCC wget --spider $(grep -o 'http://.*' $D/grub-ieee1275/copyright)
Spider mode enabled. Check if remote file exists.
--2010-07-04 00:12:55--  http://www.gnu.org/software/grub/grub-2.en.html
Resolving www.gnu.org... 199.232.41.10
Connecting to www.gnu.org|199.232.41.10|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
^
Remote file does not exist -- broken link!!!

Bye, Jörg.
-- 
Nichts ist so langweilig, wie die Wiederholung seinerselbst.
(Marcel Reich‐Ranicki)


signature.asc
Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP

Bug#445203: debian-policy: 10.8. Log files: /etc/logrotate.d/ preferred

[Russ Allbery]

Raphael Geissert  writes:

> While we are at it please let's use invoke-rc.d, which is what should be
> used.  The current example could actually be considered as a violation
> of section 9.3.3.2 (if a logrotate file is considered as a "package
> maintainer script,") so please take this email as an objection.

> If invoke-rc.d is not used and the init script follows Policy's
> requirements for 'force-reload' and 'restart,' the service could be
> started in a runlevel where it has been explicitly disabled by the
> administrator.  This does not address the case where a service has been
> stopped but is not disabled for the current runlevel, but that's an
> issue with invoke-rc.d.

Good point.  Here's an updated patch.

diff --git a/policy.sgml b/policy.sgml
index bad28af..9399b1a 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7868,11 +7868,13 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq

 

- Log files must be rotated occasionally so that they don't
- grow indefinitely; the best way to do this is to drop a log
- rotation configuration file into the directory
- /etc/logrotate.d and use the facilities provided by
- logrotate.
+ Log files must be rotated occasionally so that they don't grow
+ indefinitely.  The best way to do this is to install a log
+ rotation configuration file in the
+ directory /etc/logrotate.d, normally
+ named /etc/logrotate.d/package, and use
+ the facilities provided by logrotate.
+ 

  The traditional approach to log files has been to set up
  ad hoc log rotation schemes using simple shell
@@ -7897,25 +7899,28 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
section="8">):
  
 /var/log/foo/*.log {
-rotate 12
-weekly
-compress
-postrotate
-/etc/init.d/foo force-reload
-endscript
+rotate 12
+weekly
+compress
+missingok
+postrotate
+invoke-rc.d foo force-reload
+endscript
 }
  
  This rotates all files under /var/log/foo, saves 12
  compressed generations, and forces the daemon to reload its
- configuration information after the log rotation.
+ configuration information after the log rotation.  It skips this
+ log rotation (via missingok) if no such log file is
+ present, which avoids errors if the package is removed but not
+ purged.

 

- Log files should be removed when the package is
- purged (but not when it is only removed).  This should be
- done by the postrm script when it is called
- with the argument purge (see ).
+ Log files should be removed when the package is purged (but not
+ when it is only removed).  This should be done by
+ the postrm script when it is called with the
+ argument purge (see ).

   

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Leo 'costela' Antunes]

hi

On 04/07/10 02:45, Ben Finney wrote:

> The package is already unpacked; should I just try unpacking it again?
> 

Yes please.
The deamon was working OK before the upgrade, right? If that's the case
I can't really see why the config-file isn't there on upgrade.

Cheers

-- 
Leo "costela" Antunes
[insert a witty retort here]



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#445203: debian-policy: 10.8. Log files: /etc/logrotate.d/ preferred

[Raphael Geissert]

Hi,

On Saturday 03 July 2010 15:13:41 Russ Allbery wrote:
> 
> Here's a proposed patch that implements this.  Objections or seconds?
> 
> diff --git a/policy.sgml b/policy.sgml
> index bad28af..a676e71 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -7868,11 +7868,13 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
>   
> 
>   
> -   Log files must be rotated occasionally so that they don't
> -   grow indefinitely; the best way to do this is to drop a log
> -   rotation configuration file into the directory
> -   /etc/logrotate.d and use the facilities provided by
> -   logrotate.
> +   Log files must be rotated occasionally so that they don't grow
> +   indefinitely.  The best way to do this is to install a log
> +   rotation configuration file in the
> +   directory /etc/logrotate.d, normally
> +   named /etc/logrotate.d/package, and use
> +   the facilities provided by logrotate.
> +   
>   
> The traditional approach to log files has been to set up
> ad hoc log rotation schemes using simple shell
> @@ -7897,25 +7899,28 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
>   section="8">):
> 
>  /var/log/foo/*.log {
> -rotate 12
> -weekly
> -compress
> -postrotate
> -/etc/init.d/foo force-reload
> -endscript
> +rotate 12
> +weekly
> +compress
> +missingok
> +postrotate
> +/etc/init.d/foo force-reload
> +endscript
>  }

While we are at it please let's use invoke-rc.d, which is what should be used.
The current example could actually be considered as a violation of section 
9.3.3.2 (if a logrotate file is considered as a "package maintainer script,") 
so please take this email as an objection.

If invoke-rc.d is not used and the init script follows Policy's requirements 
for 'force-reload' and 'restart,' the service could be started in a runlevel 
where it has been explicitly disabled by the administrator.
This does not address the case where a service has been stopped but is not 
disabled for the current runlevel, but that's an issue with invoke-rc.d.

The rest looks good.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


signature.asc
Description: This is a digitally signed message part.

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Ben Finney]

On 04-Jul-2010, Leo 'costela' Antunes wrote:
> What's the version you're updating from?

According to ‘/var/log/aptitude’:

=
[UPGRADE] transmission 1.93-2 -> 2.00-1
[UPGRADE] transmission-cli 1.93-2 -> 2.00-1
[UPGRADE] transmission-common 1.93-2 -> 2.00-1
[UPGRADE] transmission-daemon 1.93-2 -> 2.00-1
[UPGRADE] transmission-gtk 1.93-2 -> 2.00-1
=

> The lack of config-file is somewhat strange, given that dpkg should
> probably just install the standard config if there isn't any lying
> about.
> Could you also check if dpkg reports any problems on --unpack ?

The package is already unpacked; should I just try unpacking it again?

-- 
 \ “Dyslexia means never having to say that you're ysror.” |
  `\—anonymous |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Leo 'costela' Antunes]

Hi

On 04/07/10 01:45, Ben Finney wrote:
> The post-installation script fails to upgrade to version 2.00-1:
>
> =
> $ ls -l /etc/transmission-daemon/
> total 8
> -rw-r--r-- 1 rootroot 302 Mar 20 01:13 
> README.json
> -rw--- 1 debian-transmission debian-transmission 1874 Jun 15 23:37 
> settings.json.tmp.LZ8ccU
>
> $ sudo dpkg --configure --pending
> Setting up transmission-daemon (2.00-1) ...
> chown: cannot access `/etc/transmission-daemon/settings.json': No such file 
> or directory
> dpkg: error processing transmission-daemon (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  transmission-daemon
> =
>   

What's the version you're updating from? The lack of config-file is
somewhat strange, given that dpkg should probably just install the
standard config if there isn't any lying about.
Could you also check if dpkg reports any problems on --unpack ?


Cheers

-- 

Leo "costela" Antunes
[insert a witty retort here]




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587743: Built from deb-src w/ debugging symbols, and error is not reproducible.

[woolsherpahat]

I went ahead and built the package from the deb-src pacakge with the
debugging symbols (as there no package providing them) included to try
and see if I could generate a useful backtrace. Strangely enough, I
could not reproduce the error. However, the original package exhibited
this bug.

Could the maintainer generate a package with debugging symbols so we
can work with the same binary?

_kce



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#555977: debian-policy: Constraints on binary package control files

[Russ Allbery]

Russ Allbery  writes:

> Lintian has several checks for the control files included in a binary
> package, but so far as I can tell, there is no general discussion in
> Policy right now about these files or any restrictions on them.  This
> seems like something that should be discussed in Policy.

One of the first steps to be able to address this bug is to talk about
these files in a coherent way.  This raises the unfortunate spectre of the
repeated use of "control file" for both files in the control.tar.gz member
of a *.deb archive and for files formatted like the debian/control file.

This patch tries to make the best of a bad situation without inventing new
terminology that's not used anywhere else.  dpkg refers to the
control.tar.gz files as "control information files," which while still far
too close to control file at least has a separate term.  The following
patch changes Policy to consistently refer to these files as control
information files and cleans up other places where "control file" or some
related term was used in a possibly confusing way.  I also took the
opportunity to replace all uses of "control file field" with the shorter
and no more ambiguous "control field."

I think this is, strictly speaking, an informative change that doesn't
require seconds, but I'd appreciate a few more sets of eyes on the change
to be sure I didn't make anything more confusing.

If someone wants to volunteer to come up with a better name for one or the
other of these sets of files and then pursue that name change through to
completion, that would make everything better in the long run, but I don't
want to hold up the rest of this particular bug on making that happen.

diff --git a/policy.sgml b/policy.sgml
index bad28af..3d5334d 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -804,6 +804,35 @@
in the .deb file format.
   
 
+  
+   A .deb package contains two sets of files: a set of files
+   to installed on the system when the package is installed, and a
+   set of files that provide additional metadata about the package or
+   which are executed when the package is installed or removed.  This
+   second set of files is called control information files.
+   Among those files are the package maintainer scripts
+   and control, the binary
+   package control file that contains the control fields for
+   the package.  Other control information files
+   include the shlibs
+   file used to store shared library dependency information
+   and the conffiles file that lists the package's
+   configuration files (described in ).
+  
+
+  
+   There is an unfortunately collision of terminology here between
+   control information files and files in the Debian control file
+   format.  Throughout this document, a control file refers
+   to a file in the Debian control file format.  These files are
+   documented in .  Only files referred to
+   specifically as control information files are the files
+   included in the control information file member of
+   the .deb file format used by binary packages.  Most
+   control information files are not in the Debian control file
+   format.
+  
+
   
The package name
 
@@ -929,9 +958,9 @@
The description of a package
 

- Every Debian package must have an extended description
- stored in the appropriate field of the control record.
- The technical information about the format of the
+ Every Debian package must have a Description control
+ field which contains a synopsis and extended description of the
+ package.  Technical information about the format of the
  Description field is in .

 
@@ -1143,7 +1172,7 @@
  must be available and usable on the system at all times, even
  when packages are in an unconfigured (but unpacked) state.
  Packages are tagged essential for a system using the
- Essential control file field.  The format of the
+ Essential control field.  The format of the
  Essential control field is described in .

@@ -1263,17 +1292,16 @@
 
  
Packages which use the Debian Configuration Management
-   Specification may contain an additional
-   config script and a templates
-   file in their control archive
-   The control.tar.gz inside the .deb.
-   See .
-   .
-   The config script might be run before the
-   preinst script, and before the package is unpacked
-   or any of its dependencies or pre-dependencies are satisfied.
-   Therefore it must work using only the tools present in
-   essential packages.
+   Specification may contain the additional control information
+   files config
+   and templates.  config is an
+   additional maintainer script used for

Bug#588013: minitube does not play stream video because of a missing codec H.264

[Patrick Naylor]

Package: minitube
Version: 1.0-3
Severity: important

It tells "A required codec is missing. You need to install the following
codec(s) to play this content: H.264" upon every video that is trying to play.



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages minitube depends on:
ii  gstreamer0.10-ffmpe 0.10.10-1FFmpeg plugin for GStreamer
ii  gstreamer0.10-plugi 0.10.19-1GStreamer plugins from the "bad" s
ii  gstreamer0.10-x 0.10.29-4GStreamer plugins for X11 and Pang
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.4.4-6GCC support library
ii  libphonon4  4:4.6.0really4.4.2-1 the core library of the Phonon mul
ii  libqt4-network  4:4.6.3-1Qt 4 network module
ii  libqt4-xml  4:4.6.3-1Qt 4 XML module
ii  libqtcore4  4:4.6.3-1Qt 4 core module
ii  libqtgui4   4:4.6.3-1Qt 4 GUI module
ii  libstdc++6  4.4.4-6  The GNU Standard C++ Library v3
ii  phonon  4:4.6.0really4.4.2-1 metapackage for the Phonon multime
ii  phonon-backend-gstr 4:4.6.0really4.4.2-1 Phonon GStreamer 0.10.x backend

minitube recommends no packages.

minitube suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587769: [buildd-tools-devel] Bug#587769: schroot - Failed setup does not cleanup session

[Roger Leigh]

tags 587769 fixed-upstream pending
thanks

On Thu, Jul 01, 2010 at 04:21:45PM +0200, Bastian Blank wrote:
> Package: schroot
> Version: 1.4.5-1
> Severity: normal
> 
> A failed setup leaves a stray session file behind and makes it
> impossible to create this session again.
> 
> | $ schroot -c sid-i386 -n sid-i386-session -b
> | E: 05btrfs: ERROR: can't access to '/srv/chroot/sid/i386/user/sessions'
> | E: sid-i386-session: Chroot setup failed: stage=setup-start
> | $ schroot -c sid-i386 -n sid-i386-session -b
> | E: sid-i386-session: Failed to lock chroot: 
> /var/lib/schroot/session/sid-i386-session: Failed to write session file: File 
> exists

Fixed on schroot-1.4 branch.

Along with the setup script reworking for the other btrfs bug,
session cleanup now always succeeds because we ignore the
nonexistence of resources we were going to clean up anyway when
on the failure and/or cleanup paths.  The only exception to this
are resources we can't clean up such as union filesystems which
require manual intervention (an appropriate warning with
instructions is issued).


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature

Bug#588012: False "Unfinished messages" popups after sending mail

[Pietro Battiston]

Package: evolution
Version: 2.30.1.2-3
Severity: normal
Tags: squeeze

(Almost?) every time that I write and send a message, few seconds after I get
a popup saying there are unfinished messages (the popup which correctly appears 
on Evolution crash or brutal kill) and reproposes the same message I just sent
(often in an older version than what I sent).
  
That never happened before upgrade to 2.30.1.2-3.

Pietro


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (650, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages evolution depends on:
ii  dbus1.2.24-1 simple interprocess messaging syst
ii  debconf [debconf-2.0]   1.5.32   Debian configuration management sy
ii  evolution-common2.30.1.2-3   architecture independent files for
ii  evolution-data-server   2.30.2-1 evolution database backend server
ii  gconf2  2.28.1-3 GNOME configuration database syste
ii  gnome-icon-theme2.30.3-1 GNOME Desktop icon theme
ii  libart-2.0-22.3.21-1 Library of functions for 2D graphi
ii  libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-4 The Cairo 2D vector graphics libra
ii  libcamel1.2-14  2.30.2-1 The Evolution MIME message handlin
ii  libcanberra-gtk00.24-1   Gtk+ helper for playing widget eve
ii  libcanberra00.24-1   a simple abstract interface for pl
ii  libdbus-1-3 1.2.24-1 simple interprocess messaging syst
ii  libdbus-glib-1-20.86-1   simple interprocess messaging syst
ii  libebackend1.2-02.30.2-1 Utility library for evolution data
ii  libebook1.2-9   2.30.2-1 Client library for evolution addre
ii  libecal1.2-72.30.2-1 Client library for evolution calen
ii  libedataserver1.2-132.30.2-1 Utility library for evolution data
ii  libedataserverui1.2-8   2.30.2-1 GUI utility library for evolution 
ii  libegroupwise1.2-13 2.30.2-1 Client library for accessing group
ii  libenchant1c2a  1.6.0-1  a wrapper library for various spel
ii  libevolution2.30.1.2-3   evolution libraries
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii  libgconf2-4 2.28.1-3 GNOME configuration database syste
ii  libgdata-google1.2-12.30.2-1 Client library for accessing Googl
ii  libgdata1.2-1   2.30.2-1 Client library for accessing Googl
ii  libglib2.0-02.24.1-1 The GLib library of C routines
ii  libgnome-desktop-2-17   2.30.0-2 Utility library for loading .deskt
ii  libgnomecanvas2-0   2.30.1-1 A powerful object-oriented display
ii  libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface 
ii  libgtkhtml-editor0  3.30.2-1 HTML rendering/editing library - e
ii  libgtkhtml3.14-19   3.30.2-1 HTML rendering/editing library - r
ii  libgweather12.30.0-2 GWeather shared library
ii  libical00.44-3   iCalendar library implementation i
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libnotify1 [libnotify1- 0.4.5-1  sends desktop notifications to a n
ii  libnspr4-0d 4.8.4-1  NetScape Portable Runtime Library
ii  libnss3-1d  3.12.6-2 Network Security Service libraries
ii  libpango1.0-0   1.28.1-1 Layout and rendering of internatio
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libsoup2.4-12.30.1-1 an HTTP library implementation in 
ii  libsqlite3-03.6.23.1-4   SQLite 3 shared library
ii  libstartup-notification 0.10-1   library for program launch feedbac
ii  libunique-1.0-0 1.1.6-1  Library for writing single instanc
ii  libxml2 2.7.7.dfsg-2 GNOME XML library
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages evolution recommends:
ii  bogofilter   1.2.1-2 a fast Bayesian spam filter (dummy
ii  evolution-plugins2.30.1.2-3  standard plugins for Evolution
ii  evolution-webcal 2.28.1-1webcal: URL handler for GNOME and 
ii  gnome-desktop-data   2.30.0-2Common files for GNOME desktop app
ii  yelp 2.30.1+webkit-1 Help browser for GNOME

Versions of packages evolution suggests:
pn  bug-buddy

Bug#587757: [buildd-tools-devel] Bug#587757: Bug#587757: Bug#587757: Bug#587757: schroot - Fails to end btrfs-snapshot sessions

[Roger Leigh]

tags 587757 + fixed-upstream pending
thanks

On Sat, Jul 03, 2010 at 02:27:39PM +0100, Roger Leigh wrote:
> On Sat, Jul 03, 2010 at 03:02:24PM +0200, Bastian Blank wrote:
> > On Thu, Jul 01, 2010 at 10:27:15PM +0100, Roger Leigh wrote:
> > > Could you possibly try out the attached replacement 00check
> > > script to see if this improves things for you?
> > 
> > Yeah, works.
> 
> Thanks.  I found that there were similar unwarranted assumptions
> for other chroot types, so I'm reworking the checks so they only
> get done at the point in the setup script where they are needed,
> to reduce the chance of this happening again.  This should be
> done later on this weekend, and I'll upload a new version once
> this is done.

Committed on schroot-1.4 branch.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature

Bug#588011: "maintainers version" of /etc/default/grub should not differ from machine to machine

[jidanni]

Package: grub-pc
Version: 1.98+20100702-1
File: /etc/default/grub
Severity: wishlist

Can you fellows please stop making _my_ settings that part of the
"maintainers version" of /etc/default/grub?

One wishes to have them neatly contained in the bottom of that file,
only to find that they end up also in the "maintainers version" of that
file.

The Debian grub packages are the only ones with the _gall_ to absorb
settings from the local environment, and attempt to make them part of
the "maintainers version" of an /etc/default/ file. There ought to be
a Policy against that.

You could have a
GRUB_HELP_USER_MAINTAIN_ETC_DEFAULT_GRUB=yes
variable, but I still think you are going overboard, and the help just
becomes a maintenance tug of war.

You see we users have to sort out what stuff is really new in there from
you guys at the top, and what has been gleaned from my local settings
that were formerly comfortably in the bottom of /etc/default/grub but
end up getting integrated, or shall we say, blended into the top of
/etc/default/grub.

Please also don't assume that users only have one machine, thus they
won't notice that the "maintainers version" differs from machine to
machine.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#477240: Please clarify status of XSI extensions for kill and trap

[Russ Allbery]

Raphael Geissert  writes:

> Based on the results from the last archive-wide checkbashisms check on i386, 
> the situation is as follows:

> There are about *91* unique binary packages with at least one match for
> the trap with signal numbers check.

> And about *112* unique binary packages with at least one match for the
> 'kill -[0-9] or -[A-Z]' check.

> Both checks are meant to detect the usage of the widely used XSI
> extensions for kill and trap as documented in [1] and [2] respectively.

[...]

> As it seems lots of people have agreed on using those XSI extensions
> IMHO the policy should be updated to permit the usage of the XSI
> extensions for the trap and kill built-ins as described in the SUSv3
> Shell Command Language in /bin/sh scripts.

> [1]http://www.opengroup.org/onlinepubs/009695399/utilities/kill.html
> [2]http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html

Here's a patch which implements that, plus an additional exception for
libtool scripts which trap SIGPIPE by number.  Objections or seconds?
I'm copying Clint as posh maintainer since this will be relevant to which
features posh implements.

This was discussed a while back on debian-devel, but unfortunately the
discussion at the time wasn't cc'd to the Policy bug.

diff --git a/policy.sgml b/policy.sgml
index bad28af..1658cbf 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7427,7 +7427,19 @@ fname () {
 
  must be supported and must set the value of c to
  delta.
-
+   
+   The XSI extension to kill allowing kill
+ -signal, where signal is either
+ the name of a signal or one of the numeric signals listed in
+ the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
+ supported.
+   
+   The XSI extension to trap allowing numeric
+ symbols must be supported.  However, only the signal numbers
+ listed in the extension, which are the same as
+ for kill above, plus SIGPIPE (13) must be
+ supported.
+   
  
  If a shell script requires non-SUSv3 features from the shell
  interpreter other than those listed above, the appropriate shell

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588010: transmission-daemon: upgrade fails on "chown: cannot access `/etc/transmission-daemon/settings.json': No such file or directory"

[Ben Finney]

Package: transmission-daemon
Version: 2.00-1
Severity: important

The post-installation script fails to upgrade to version 2.00-1:

=
$ ls -l /etc/transmission-daemon/
total 8
-rw-r--r-- 1 rootroot 302 Mar 20 01:13 
README.json
-rw--- 1 debian-transmission debian-transmission 1874 Jun 15 23:37 
settings.json.tmp.LZ8ccU

$ sudo dpkg --configure --pending
Setting up transmission-daemon (2.00-1) ...
chown: cannot access `/etc/transmission-daemon/settings.json': No such file or 
directory
dpkg: error processing transmission-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 transmission-daemon
=

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages transmission-daemon depends on:
ii  adduser 3.112add and remove users and groups
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libcurl3-gnutls 7.21.0-1 Multi-protocol file transfer libra
ii  libevent-1.4-2  1.4.13-stable-1  An asynchronous event notification
ii  libssl0.9.8 0.9.8o-1 SSL shared libraries
ii  lsb-base3.2-23.1 Linux Standard Base 3.2 init scrip
ii  transmission-common 2.00-1   lightweight BitTorrent client (com
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages transmission-daemon recommends:
ii  transmission-cli  2.00-1 lightweight BitTorrent client (com

transmission-daemon suggests no packages.

-- Configuration Files:
/etc/transmission-daemon/settings.json [Errno 2] No such file or directory: 
u'/etc/transmission-daemon/settings.json'

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588009: fai-server: running 'make-fai-nfsroot -kv' returns an error

[fim...@spotify.com]

Package: fai-server
Version: 3.3.3+spotify
Severity: normal


When running the command 'make-fai-nfsroot -kv', I got the following error, 
followed by an ABEND:

r...@maggie:/etc/fai# make-fai-nfsroot -kv
Using configuration files from /etc/fai
Upgrading nfsroot and installing new packages into the nfsroot.
ln: creating symbolic link `/srv/fai/nfsroot/live/filesystem.dir/usr/sbin/fai': 
File exists
No diversion `any diversion of /sbin/discover-modprobe', none removed
Log file written to /var/log/fai/make-fai-nfsroot.log
r...@maggie:/etc/fai#

Impact:
This error makes updating the contents of the nfsroot environment difficult.

/Mattias Jansson


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages fai-server depends on:
ii  debootstrap1.0.10lenny1  Bootstrap a basic Debian system
ii  fai-client 3.3.3+spotify Fully Automatic Installation clien

Versions of packages fai-server recommends:
ii  dhcp3-server 3.1.1-6+lenny4  DHCP server for automatic IP addre
ii  inetutils-inetd [inet-su 2:1.5.dfsg.1-9  internet super server
ii  iproute  20080725-2  networking and traffic control too
ii  nfs-kernel-server1:1.1.2-6lenny1 support for NFS kernel server
ii  openssh-client   1:5.1p1-5   secure shell client, an rlogin/rsh
ii  openssh-server   1:5.1p1-5   secure shell server, an rshd repla
ii  syslinux-common  2:3.71+dfsg-5   Kernel loader which uses a FAT, ex
ii  tftpd-hpa0.48-2.3HPA's tftp server

Versions of packages fai-server suggests:
ii  apt-move  4.2.27-1+b4Maintain Debian packages in a pack
ii  aptitude  0.4.11.11-1~lenny1 terminal-based package manager
pn  debmirror  (no description available)
ii  genisoimage   9:1.1.9-1  Creates ISO-9660 CD-ROM filesystem
ii  grub  0.97-47lenny2  GRand Unified Bootloader (Legacy v
pn  libproc-daemon-perl(no description available)
pn  perl-tk(no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#546355: closed by Christoph Egger (doesn't appear on buildd (zandonai) or porterbox (zelenka))

[Christoph Egger]

Hi!

Bastian Blank  writes:
>> As clisp was just successfully autobuilt on zandonai I guess the
>> problem is gone. Don't know when this bug was introduced and how it was
>> fixed and am not motivated enough to get out the details as it works
>> now.
>
> This is not acceptable. The bug is reproducable on every mixed-bitness
> system if it does not set personalities.
>
> Bastian

OK wasn't reproducible on any system I have access to and did not
get any reply to the message I sent nearly one month ago (which was
cc-ed to s...@buildd so you should have gotten it) so all I could assume
was it being solved some way or another.

What would you suggest on fixing it? Along #491573 ? How would I
test a "fixed" package?

I'm no expert in s390 architecture -- is that such a common
combination this bug should be "serious"? clisp fails to build on i386
with 64bit kernel as well for example.

Regards

Christoph



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#574624: dibbler-client: Upgrade doesn't work

[Gerfried Fuchs]

Package: dibbler-client
Version: 0.7.3-1
Severity: serious

Hi!

 Given that setting the client start to false hinders package upgrades
or purge or anything because of this bug this is actually a policy
violation because the package doesn't install (or remove) cleanly.

 Please try to get this fixed rather sooner than later,
Rhonda

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.32-5-powerpc
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dibbler-client depends on:
ii  debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.4-5  GCC support library
ii  libstdc++64.4.4-5The GNU Standard C++ Library v3
ii  ucf   3.0025 Update Configuration File: preserv

Versions of packages dibbler-client recommends:
ii  dibbler-doc   0.7.3-1.1  documentation for Dibbler
pn  resolvconf (no description available)

dibbler-client suggests no packages.

-- debconf information:
* dibbler-client/start: false
  dibbler-client/title:
* dibbler-client/options: dns, domain
* dibbler-client/interfaces: eth0



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#290049: zlib rsyncable

[Thorsten Glaser]

Hi,

any progress (forwarded to)?

There’s another patch at
‣ http://lists.samba.org/archive/rsync/2005-February/011653.html
also attached in case it goes “bad”. This seems to use a different
checksum (seems to be the one rsync itself uses?) but can be
parametrised a lot… he does say he has sensible(?) defaults though.

I have another “hat” on, as BSD developer (who use a zlib based
compress instead of GNU gzip) I’d also be interested in having
that upstream… in dpkg it would of course also make sense.

bye,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Huntdiff -Naur original-1.2.2/deflate.c rsyncable-1.2.2/deflate.c

--- original-1.2.2/deflate.c2004-09-15 10:28:14.0 -0700

+++ rsyncable-1.2.2/deflate.c   2005-02-17 14:37:14.660957200 -0700

@@ -98,6 +98,10 @@

 int length));

 #endif

 

+local void rsync_roll(deflate_state *s, unsigned start, unsigned num);

+local void rsync_roll_noop(deflate_state *s, unsigned start, unsigned num);

+local void rsync_roll2(deflate_state *s, unsigned start, unsigned num);

+

 /* ===

  * Local data

  */

@@ -115,6 +119,39 @@

  * See deflate.c for comments about the MIN_MATCH+1.

  */

 

+

+

+/* 

+   Valid values for RSYNC_DEFAULT_CHECKSUM_TYPE are:

+

+   Z_RSYNCABLE_OFF

+   Z_RSYNCABLE_SIMPLESUM

+   Z_RSYNCABLE_RSSUM

+*/

+

+#ifndef RSYNC_DEFAULT_CHECKSUM_TYPE

+#  define RSYNC_DEFAULT_CHECKSUM_TYPE Z_RSYNCABLE_RSSUM

+#endif

+

+#ifndef RSYNC_DEFAULT_WINDOW_SIZE

+#  define RSYNC_DEFAULT_WINDOW_SIZE 30

+#endif

+

+#ifndef RSYNC_DEFAULT_RESET_BLOCK_SIZE

+#  define RSYNC_DEFAULT_RESET_BLOCK_SIZE 4096 

+#endif

+

+#ifndef RSYNC_RESET_MAGIC_VALUE

+#  define RSYNC_RESET_MAGIC_VALUE 0

+#endif

+

+#define RSYNC_SUM_MATCH(s) ((s)->rsync_sum % (s)->rsync_reset_block_size == 
RSYNC_RESET_MAGIC_VALUE)

+/* Whether window sum matches magic value */

+

+/* Global rsync mode control variable */

+int zlib_rsync = 1 ;

+

+

 /* Values for max_lazy_match, good_match and max_chain_length, depending on

  * the desired pack level (0..9). The values given below have been tuned to

  * exclude worst case performance for pathological files. Better values may be

@@ -212,6 +249,36 @@

 /* To do: ignore strm->next_in if we use it as window */

 }

 

+int ZEXPORT deflateSetRsyncParameters_(strm, checksum_type, window_size, 
reset_block_size)

+z_streamp strm;

+int  checksum_type;

+   ulg window_size;

+   ulg reset_block_size;

+{

+   deflate_state *s = strm->state;

+

+   switch(checksum_type){

+   case Z_RSYNCABLE_SIMPLESUM: 

+   s->rsync_rollfunction = rsync_roll; 

+   break;

+   case Z_RSYNCABLE_RSSUM: 

+   s->rsync_rollfunction = rsync_roll2; 

+   break;

+   default: 

+   s->rsync_rollfunction = rsync_roll_noop;

+   }

+

+   s->rsync_window_size = window_size != 0 ? window_size : 
RSYNC_DEFAULT_WINDOW_SIZE;

+   s->rsync_reset_block_size = reset_block_size != 0 ? reset_block_size : 
s->rsync_window_size;

+

+s->rsync_chunk_end = 0xUL;

+s->rsync_sum = 0;

+   s->rsync_s1 = 0;

+   s->rsync_s2 = 0;

+

+   return Z_OK;

+}

+

 /* = */

 int ZEXPORT deflateInit2_(strm, level, method, windowBits, memLevel, strategy,

   version, stream_size)

@@ -307,9 +374,13 @@

 s->strategy = strategy;

 s->method = (Byte)method;

 

+   deflateSetRsyncParameters_(strm, RSYNC_DEFAULT_CHECKSUM_TYPE, 
RSYNC_DEFAULT_WINDOW_SIZE, RSYNC_DEFAULT_RESET_BLOCK_SIZE);

+

 return deflateReset(strm);

 }

 

+

+

 /* = */

 int ZEXPORT deflateSetDictionary (strm, dictionary, dictLength)

 z_streamp strm;

@@ -841,6 +912,13 @@

 #ifdef ASMV

 match_init(); /* initialize the asm code */

 #endif

+

+/* rsync params */

+s->rsync_chunk_end = 0xUL;

+s->rsync_sum = 0;

+   s->rsync_s1 = 0;

+   s->rsync_s2 = 0;

+

 }

 

 #ifndef FASTEST

@@ -1123,6 +1201,8 @@

 zmemcpy(s->window, s->window+wsize, (unsigned)wsize);

 s->match_start -= wsize;

 s->strstart-= wsize; /* we now have strstart >= MAX_DIST */

+if (s->rsync_chunk_end != 0xUL)

+s->rsync_chunk_end -= wsize;

 s->block_start -= (long) wsize;

 

 /* Slide the hash table (could be avoided with 32 bit values

@@ -1184,15 +1264,98 @@

 } 

Bug#588003: "Need help?" link doesn't work

[Mark Purcell]

On Sunday 04 July 2010 06:24:39 Erik Esterer wrote:
> The window to configure the SIP profile has a "Need help?" link on the bottom 
> left corner, but it doesn't work.
> Clicking on this link has no effect at all: nothing happens..

Erik,

For my that button starts up konqueror at http://www.qutecom.com.

Do you have konqueror installed?  Should we make it a depends, I wouldn't of 
thought so..

Mark


signature.asc
Description: This is a digitally signed message part.

Bug#587999: further info

[Ulrich Eckhardt]

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Dec 10  2007 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1940408 Jun  3 18:28 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
:00:10.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 
9200] (rev 
01)

/var/lib/x11/xorg.conf.md5sum does not exist.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 6148 Jul  3 16:47 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# This configfile demonstrates the broken behaviour of xorg
# The problem is that this file as configuration is capable of starting X in
# the configured layout, but once shut down, this does _not_ work a second
# time.
#
# Note:
#   Option  "UseFBDev"  "true"
#  will enable startup.
#
# Configuration:
# xserver-xorg-video-ati 6.6.3-2
# Monitor:
# SyncMaster 225BW on VGA
# Machine:
# Mac Mini PPC

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
#Load   "freetype"
Load"glx"
Load"int10"
Load"vbe"
EndSection

#Section "Extensions"
#Option "Composite" "enable"
#EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "dvorak"
Option  "XkbVariant""dvorak"
Option  "XkbOptions""lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
EndSection

Section "Device"
Identifier  "Builtin Radeon"
Driver  "radeon"
# select model with integrated DVI adapter
Option  "MacModel" "mini-internal"
#   Option  "MonitorLayout" "TMDS,NULL"
#   Option  "PanelSize" "1680x1050"
# ignore monitor mode lines received via DDC but use DDC to detect the 
monitor 
itself
Option  "IgnoreEDID"  "true"
# dynamically scale the chip clock to reduce energy consumption
#Option  "DynamicClocks" "true"
# TODO: try this on
# Option  "DefaultTMDSPLL" "true"
#   Option  "AGPMode"   "4"
#Option  "XAANoOffscreenPixmaps" "true"

#   Option  "UseFBDev"  "false"
#   Option  "UseFBDev"  "true"
#   Option  "AGPFastWrite"  "off"
#   Option  "DDCMode"   "true"
#   Option  "AccelMethod"   "EXA"
#   Option  "AccelMethod"   "XAA"
#   Option  "ReverseDDC""true"
###
#   BusID   "PCI:0:16:0"

# All options supported by the driver (2008-08-24)
#
#Option "SWcursor" "boolean"
#Option "SWcursor" "true"
#Option "NoAccel" "boolean"
#Option "Dac6Bit" "boolean"
#Option "VideoKey" "integer"
#Option "ScalerWidth" "integer"
#Option "AGPMode" "integer"
#Option "AGPFastWrite" "boolean"
#Option "BusType" "string"
#Option "DDCMode" "boolean"
#Option "DisplayPriority" "string"
#Option "ColorTiling" "boolean"
#Option "IgnoreEDID" "boolean"
#Option "PanelSize" "string"
#Option "EnablePageFlip" "boolean"
#Option "ForceMinDotClock" "frequency"
#Option "RenderAccel" "boolean"
#Option "AccelMethod" "string"
# old X accel
Option "AccelMethod" "XAA"
# new X accel
#Option "AccelMethod" "EXA"
#Option "AccelDFS" "boolean"
#Option "FBTexPercent" "integer"
#Option "DepthBits" "integer"
#Option "DMAForXv" "boolean"
#Option "SubPixelOrder" "string"
#Option "DynamicClocks" "boolean"
#Option "VGAAccess" "boolean"
#Option "ReverseDDC" "boolean"
#Option "LVDSProbePLL" "boolea

Bug#546355: closed by Christoph Egger (doesn't appear on buildd (zandonai) or porterbox (zelenka))

[Bastian Blank]

reopen 546355
thanks

> As clisp was just successfully autobuilt on zandonai I guess the
> problem is gone. Don't know when this bug was introduced and how it was
> fixed and am not motivated enough to get out the details as it works
> now.

This is not acceptable. The bug is reproducable on every mixed-bitness
system if it does not set personalities.

Bastian

-- 
Landru! Guide us!
-- A Beta 3-oid, "The Return of the Archons", stardate 3157.4



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588008: # dpkg-reconfigure jackd1 doesn't write any /etc/security/limits.d/audio.conf file

[Robert Auxonne]

Package: jackd1
Version: 1:0.118+svn3796-5
Severity: important
Tags: sid

r...@debian-desktop:/home/robert# dpkg-reconfigure jackd1
mv: impossible d'évaluer « /etc/security/limits.d/audio.conf.disabled »:
Aucun fichier ou dossier de ce type

Then i answered "yes" to the question to activate the real-time priorities, but
:

r...@debian-desktop:/home/robert# cat /etc/security/limits.d/audio.conf
cat: /etc/security/limits.d/audio.conf: Aucun fichier ou dossier de ce type

The file doesn't exist. I had to create and edit the file with a text editor.



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

Kernel: Linux 2.6.31.12-rt21-1-amd64 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages jackd1 depends on:
ii  coreutils  8.5-1 GNU core utilities
ii  debconf [debconf-2.0]  1.5.32Debian configuration management sy
ii  libasound2 1.0.23-1  shared library for ALSA applicatio
ii  libc6  2.11.2-2  Embedded GNU C Library: Shared lib
ii  libcelt0-0 0.7.1-1   The CELT codec runtime library
ii  libjack0   1:0.118+svn3796-5 JACK Audio Connection Kit (librari
ii  libreadline6   6.1-3 GNU readline and history libraries
ii  libsamplerate0 0.1.7-3   Audio sample rate conversion libra
ii  libsndfile11.0.21-2  Library for reading/writing audio 

Versions of packages jackd1 recommends:
ii  jackd1-firewire1:0.118+svn3796-5 JACK Audio Connection Kit (FFADO b
ii  libpam-modules 1.1.1-3   Pluggable Authentication Modules f
ii  qjackctl   0.3.6-1   User interface for controlling the

Versions of packages jackd1 suggests:
pn  jack-tools (no description available)
ii  libjackasyn0  0.11-2+b1  The Asynchrounous JACK Library
pn  meterbridge(no description available)

-- Configuration Files:
/etc/security/limits.d/audio.conf [Errno 2] Aucun fichier ou dossier de ce 
type: u'/etc/security/limits.d/audio.conf'

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587998: edos-distcheck: Please support architecture wildcards

[Andreas Barth]

* Roger Leigh (rle...@debian.org) [100703 21:21]:
> edos-debcheck is used by the Debian wanna-build database, used
> by the build dæmons to check which packages need rebuilding.
> However, it appears that edos-debcheck can't yet cope with
> architecture wildcards which are now permitted in package
> dependencies and build-dependencies and are supported by
> dpkg, sbuild and associated tools.  [I didn't see any use of
> dpkg-architecture in the sources.]

Actually this is not an issue of edos. Edos just sees binary packages
- the architectures are stripped out in wanna-build.


Andi



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#573538: Packaging again sagemath

[Giovanni Mascellani]

Hi to the many recipients of this email.

I'm interested in having sagemath in Debian. I'm not a sagemath power
user and maybe should learn a bit of the many technologies used to build
it in order to maintain it, but I have no problems in learning what I
need (even if this can take time).

Tim, if you can explain a bit how you used to maintain sagemath, I could
get that as a starting point for the new package.

Thanks, Giovanni.
-- 
Giovanni Mascellani 
Pisa, Italy

Web: http://poisson.phc.unipi.it/~mascellani
Jabber: g.mascell...@jabber.org / giova...@elabor.homelinux.org



signature.asc
Description: OpenPGP digital signature

Bug#587222: cryptsetup does not/cannot close dm-crypt devices, if root-fs is on it, but does also not warn about it

[Christoph Anton Mitterer]

And as addition:

When doing (on an already opened and mounted dm-crypt device)...
1) cryptdisk_start foo...
it says it's already running,... and $? = 0
Which is ok so :)

but on:
2) cryptdisk_stop foo...
it says it's busy,... _BUT_ $? = 0
which should be non-zero I guess.


Cheers,
Chris.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588007: rakarrack crashes for certain effects

[Stefan Potyra]

Package: rakarrack
Version: 0.5.8-1
Severity: normal

Hi,

thanks for maintaining rakarrack.

If I select rock amp from the first bank while effects are enabled, rakarrack
crashes. There are a few other effects that also lead to a crash, e.g. metal
amp, also from the first bank. Here's the output that I get:

>>rackarrack

rakarrack 0.5.8_Equinox - Copyright (c) Josep Andreu - Ryan Billing - Douglas 
McClendon - Arnout Engelen
Try 'rakarrack --help' for command-line options.
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and 
others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details


Memory locking is unlimited - this is dangerous. You should probably alter the 
line:
 @audio   -  memlockunlimited
in your /etc/limits.conf to read:
 @audio   -  memlock3045900
JACK compiled with System V SHM support.
loading driver ..
Enhanced3DNow! detected
SSE2 detected
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
Enhanced3DNow! detected
SSE2 detected
subgraph starting at rakarrack timed out (subgraph_wait_fd=9, status = 0, state 
= Running, pollret = 0 revents = 0x0)


 alsa_pcm: xrun of at least 0.734 msecs


zombified - calling shutdown handler
X I/O error
jack main caught signal 12
zsh: exit 1 rakarrack

Cheers,
  Stefan.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rakarrack depends on:
ii  jackd  5 JACK Audio Connection Kit (default
ii  libasound2 1.0.23-1  shared library for ALSA applicatio
ii  libc6  2.11.2-2  Embedded GNU C Library: Shared lib
ii  libfltk1.1 1.1.10-2  Fast Light Toolkit - shared librar
ii  libfontconfig1 2.8.0-2.1 generic font configuration library
ii  libfreetype6   2.3.11-1  FreeType 2 font engine, shared lib
ii  libgcc11:4.4.4-6 GCC support library
ii  libjack0   1:0.118+svn3796-5 JACK Audio Connection Kit (librari
ii  libsamplerate0 0.1.7-3   Audio sample rate conversion libra
ii  libsndfile11.0.21-2  Library for reading/writing audio 
ii  libstdc++6 4.4.4-6   The GNU Standard C++ Library v3
ii  libx11-6   2:1.3.3-3 X11 client-side library
ii  libxft22.1.14-2  FreeType-based font drawing librar
ii  libxpm41:3.5.8-1 X11 pixmap library
ii  libxrender11:0.9.5-2 X Rendering Extension client libra
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

rakarrack recommends no packages.

rakarrack suggests no packages.

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#574131: xdg-utils: xdg-email never launchs a mua if desktop is not gnome neither kde neither xfce

[Per Olofsson]

Hi,

2010-06-28 15:55, Jonathan Nieder skrev:
> Better to put the logic in xdg-email itself, I think, so it can be
> shared across distributions.

Agreed.

> Do you know any programs that open up a message in a user-specified
> mail user agent?  It would be nice to not have to figure this out from
> scratch.

Most e-mail clients seem to accept the recipient address as an argument,
and this is enough for most programs.

> To implement 'xdg-email --cc CC --bcc BCC --subject SUBJECT --body TEXT
> --attach ATTACHMENT ADDRESS':
> 
>  - mutt:
> 
>   file=$(mktemp)
>   echo 'TEXT' >$file
>   mutt -a ATTACHMENT -b BCC -c CC -H "$file" -s SUBJECT -- ADDRESS

Or use "/usr/lib/mutt/mailto-mutt URL".

>  - thunderbird:
> 
>   thunderbird -compose 
> "to='ADDRESS',cc='CC',bcc='BCC',subject='SUBJECT',"\
> "body='TEXT',attachment='ATTACHMENT'"

Or simply "thunderbird URL".

> 
>  - gnus with mailto-url-gnus[2]:
> 
>   emacsclient -a "" -n -c -e "(mailto-url-gnus \"$url\" t t)"
> 
>  - kmail:
> 
>   I have no idea.
> 
> As you can see, I suspect would require some kind of per-package
> registration to be usable.  Grasping at straws, I suggest maybe a
> field in the .desktop file.  Is there prior art for this?  Is there a
> relevant mailng list?

As I said, I think workarounds should go into the xdg-email script.
E-mail clients wishing to avoid workarounds can always learn to accept
mailto: URLs as arguments.

-- 
Pelle



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588006: FTBFS the second time you build (cannot remove `lib/ivis_opengl/GLee.c')

[Goswin von Brederlow]

Package: warzone2100
Version: 2.3.1-1a0.mrvn.1
Severity: normal

Hi,

building the package twice fails with the following error:

# Remove GLee embedded code copy so we never use it
rm lib/ivis_opengl/GLee.c lib/ivis_opengl/GLee.h
rm: cannot remove `lib/ivis_opengl/GLee.c': No such file or directory
rm: cannot remove `lib/ivis_opengl/GLee.h': No such file or directory
make: *** [config.status] Error 1

I suggest adding a '-f' to the rm.

MfG
Goswin

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

Kernel: Linux 2.6.31.6-xen-2010.02.18 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages warzone2100 depends on:
ii  libc6   2.11.1-3 Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.4.4-5GCC support library
ii  libgl1-mesa-glx [libgl1 7.7.1-3  A free implementation of the OpenG
ii  libglc0 0.7.2-3  QuesoGLC GLC implementation
ii  libglee0d1  5.4.0-1  extension loading library for Open
ii  libglu1-mesa [libglu1]  7.7.1-3  The OpenGL utility library (GLU)
ii  libogg0 1.2.0~dfsg-1 Ogg bitstream library
ii  libopenal1  1:1.12.854-2 Software implementation of the Ope
ii  libphysfs1  2.0.1-1  filesystem abstraction library for
ii  libpng12-0  1.2.43-1 PNG library - runtime
ii  libpopt01.16-1   lib for parsing cmdline parameters
ii  libsdl1.2debian 1.2.14-6 Simple DirectMedia Layer
ii  libstdc++6  4.4.4-5  The GNU Standard C++ Library v3
ii  libtheora0  1.1.1+dfsg.1-3   The Theora Video Compression Codec
ii  libvorbis0a 1.3.1-1  The Vorbis General Audio Compressi
ii  libvorbisfile3  1.3.1-1  The Vorbis General Audio Compressi
ii  libx11-62:1.3.3-3X11 client-side library
ii  nvidia-glx  195.36.24-3  NVIDIA binary Xorg driver
ii  warzone2100-data2.3.1-1a0.mrvn.1 data files for warzone2100

Versions of packages warzone2100 recommends:
ii  warzone2100-music   2.3.1-1a0.mrvn.1 official music for warzone2100

warzone2100 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#479172: [PATCH] Ask the user for the package name and version if needed. (Rebased on top of current master)

[Guido Günther]

Hi Matthijs,
On Mon, Jun 28, 2010 at 08:24:30PM +0200, Matthijs Kooijman wrote:
[..snip..] 
> > As for the general idea of this patch: I've been using it for a while now, 
> > and
> > considering most of my upstream packages use a
> > packagename-version-source.tar.gz tarball (and considering that some of them
> > need version some mangling), the prompting really works well for me :-)
Thinking about this again: I think we should go for the prompting. The
only case I'd like to fix first is when you're not on the debian branch
but on upstream and so git-import-orig would not find a debian/changelog
and prompt. We should rather use 'git show' or 'git cat-file' in that
case.
Thanks a lot for your patch!
 -- Guido



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587997: Fails to run on mipsel

[Matt Kraai]

Hi Jakub,

On Sat, Jul 03, 2010 at 09:41:10PM +0200, Jakub Wilk wrote:
> * Matt Kraai , 2010-07-03, 11:38:
>> I backported pytrainer 1.7.2-1 to lenny and tried to run it on a
>> mipsel machine, but it failed to run with the following error:
>>
>> Unsupported sys.platform: linux2-mipsel.
>>
>> The attached patch fixed this problem.
>
> pytrainer won't run also on kfreebsd-* and hurd-*, both with and without  
> Matt's patch. Please consider applying my (untested, sorry) patch  
> instead.

That's a good point, Jakub.  I tested your patch and it works for me.

-- 
Matt  http://ftbfs.org/kraai



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588005: Does antlr3 really requires maven ?

[Vincent Fourmond]

On Sat, Jul 3, 2010 at 10:59 PM, Ludovic Claude
 wrote:
> This dependency is marked as required as gunit-maven-plugin is included in
> the main package. It would be better indeed to put gunit.jar and
> gunit-maven-plugin.jar in a separate package.

  Ah, I though so.

> maven-debian-helper is not yet able to install the jars in several packages,
> I will try to fix that soon.

  Many thanks !

  Vincent



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588001: [Pkg-haskell-maintainers] Bug#588001: FTBFS: shlibs parsing error

[Joachim Breitner]

reassign 588001 haskell-devscripts
affects 588001 haskell-haddock
thanks

Dear Riku,

Am Samstag, den 03.07.2010, 22:59 +0300 schrieb Riku Voipio:
> Package: haskell-haddock
> Version: 2.7.2-4
> Severity: serious
> 
> Package fails to build on the armel buildd:

thanks. for filing the bug report.

> > Kernel: Linux 2.6.26-2-iop32x armel (armv5tel)
> > Toolchain package versions: libc6-dev_2.11.2-1 dpkg-dev_1.15.7.2 
> > linux-libc-dev_2.6.32-15 gcc-4.4_4.4.4-6 g++-4.4_4.4.4-6 binutils_2.20.1-11 
> > libstdc++6-4.4-dev_4.4.4-6 libstdc++6_4.4.4-6
> > Package versions: alex_2.3.3-1 apt_0.7.25.3 base-files_5.7 
> > base-passwd_3.5.22 bash_4.1-3 binutils_2.20.1-11 bsdmainutils_8.0.13 
> > bsdutils_1:2.17.2-3.1 build-essential_11.5 bzip2_1.0.5-4 cdbs_0.4.87 
> > coreutils_8.5-1 cpio_2.11-4 cpp_4:4.4.4-2 cpp-4.4_4.4.4-6 dash_0.5.5.1-7 
> > dctrl-tools_2.14 debconf_1.5.32 debconf-english_1.5.32 debfoster_2.7-1.1 
> > debhelper_7.9.3 debian-archive-keyring_2009.01.31 debianutils_3.2.3 
> > diffutils_1:3.0-1 dmsetup_2:1.02.48-2 dpkg_1.15.7.2 dpkg-dev_1.15.7.2 
> > e2fslibs_1.41.12-2 e2fsprogs_1.41.12-2 fakeroot_1.14.4-1 file_5.04-2 
> > findutils_4.4.2-1 g++_4:4.4.4-2 g++-4.4_4.4.4-6 gcc_4:4.4.4-2 
> > gcc-4.4_4.4.4-6 gcc-4.4-base_4.4.4-6 gettext_0.18.1.1-1 
> > gettext-base_0.18.1.1-1 ghc6_6.12.1-13 ghc6-prof_6.12.1-13 gnupg_1.4.10-4 
> > gpgv_1.4.10-4 grep_2.6.3-3 groff-base_1.20.1-10 gzip_1.3.12-9 
> > happy_1.18.4-2 haskell-devscripts_0.7.10 hostname_3.04 hscolour_1.16-1 
> > html-xml-utils_5.7-2 html2text_1.3.2a-15 initscripts_2.88dsf-9 
> > insserv_1.14.0-2 intltool-debian_0.35.0+20060710.1 libacl1_2.2.49-3 
> > libattr1_1:2.4.44
> > -2 libblkid1_2.17.2-3.1 libbsd-dev_0.2.0-1 libbsd0_0.2.0-1 
> > libbz2-1.0_1.0.5-4 libc-bin_2.11.2-1 libc-dev-bin_2.11.2-1 libc6_2.11.2-1 
> > libc6-dev_2.11.2-1 libcomerr2_1.41.12-2 libcroco3_0.6.2-1 libdb4.7_4.7.25-9 
> > libdb4.8_4.8.30-1 libdevmapper1.02.1_2:1.02.48-2 libdpkg-perl_1.15.7.2 
> > libffi-dev_3.0.9-2 libffi5_3.0.9-2 libgc1c2_1:6.8-1.2 libgcc1_1:4.4.4-6 
> > libgcrypt11_1.4.5-2 libgdbm3_1.8.3-9 libghc6-ghc-paths-dev_0.1.0.6-1 
> > libglib2.0-0_2.24.1-1 libgmp3-dev_2:4.3.2+dfsg-1 libgmp3c2_2:4.3.2+dfsg-1 
> > libgmpxx4ldbl_2:4.3.2+dfsg-1 libgnutls26_2.8.6-1 libgomp1_4.4.4-6 
> > libgpg-error0_1.6-1 libldap-2.4-2_2.4.21-1 liblzma2_4.999.9beta+20100527-1 
> > libmagic1_5.04-2 libmpfr1ldbl_2.4.2-3 libncurses5_5.7+20100313-2 
> > libopencdk10_0.6.6-1 libpam-modules_1.1.1-3 libpam-runtime_1.1.1-3 
> > libpam0g_1.1.1-3 libpcre3_8.02-1 libreadline6_6.1-3 
> > libsasl2-2_2.1.23.dfsg1-5 libselinux1_2.0.94-1 libsepol1_2.0.41-1 
> > libslang2_2.2.2-4 libss2_1.41.12-2 libstdc++6_4.4.4-6 
> > libstdc++6-4.4-dev_4.4.4-6 libtasn1-3_2.7-1 libtimedate-perl_1.2000-1 
> > libudev0_158-
> 
> -snip-
> 
> > dpkg-gencontrol: warning: Depends field of package libghc6-haddock-prof: 
> > unknown substitution variable ${shlibs:Depends}
> > dpkg-gencontrol: warning: can't parse dependency (>= 
> > 2.3.3-10.7.25.35.73.5.224.1-32.20.1-118.0.131:2.17.2-3.111.51.0.5-40.4.878.5-12.11-44:4.4.4-24.4.4-60.5.5.1-72.141.5.321.5.322.7-1.17.9.32009.01.313.2.31:3.0-12:1.02.48-21.15.7.21.15.7.21.41.12-21.41.12-21.14.4-15.04-24.4.2-14:4.4.4-24.4.4-64:4.4.4-24.4.4-64.4.4-60.18.1.1-10.18.1.1-16.12.1-136.12.1-131.4.10-41.4.10-42.6.3-31.20.1-101.3.12-91.18.4-20.7.103.041.16-15.7-21.3.2a-152.88dsf-91.14.0-20.35.0+20060710.12.2.49-31:2.4.44-22.17.2-3.10.2.0-10.2.0-11.0.5-42.11.2-12.11.2-12.11.2-12.11.2-11.41.12-20.6.2-14.7.25-94.8.30-12:1.02.48-21.15.7.23.0.9-23.0.9-21:6.8-1.21:4.4.4-61.4.5-21.8.3-90.1.0.6-12.24.1-12:4.3.2+dfsg-12:4.3.2+dfsg-12:4.3.2+dfsg-12.8.6-14.4.4-61.6-12.4.21-14.999.9beta+20100527-15.04-22.4.2-35.7+20100313-20.6.6-11.1.1-31.1.1-31.1.1-38.02-16.1-32.1.23.dfsg1-52.0.94-12.0.41-12.2.2-41.41.12-24.4.4-64.4.4-62.7-11.2000-1158-10.9.3-12:0.1.12-152.17.2-3.12.7.7.dfsg-42.6.32-151:4.1.4.2-1+b23.2-23.13.81-82.5.7-31.3.3-152.17.2-3.15.7+20100313-25.7+201003
> > 13-21:4.1.4.2-1+b22.6-25.10.1-135.10.1-135.10.1-131.0.166.1-34.2.1-70.0.41.7.2p7-12.88dsf-92.88dsf-92.88dsf-91.23-22010j-1158-12.17.2-3.11:7.5+34.999.9beta+20100527-11:1.2.3.4.dfsg-3)
> > dpkg-gencontrol: error: error occurred while parsing Depends field: 
> > libghc6-haddock-dev (=2.7.2-4), libghc6-cabal-prof-1.8.0.2-80b8f, 
> > libghc6-array-prof-0.3.0.0-dbdf7, libghc6-base-prof-4.2.0.0-14b6a, 
> > libghc6-containers-prof-0.3.0.0-409fe, 
> > libghc6-directory-prof-1.0.1.0-78675, libghc6-filepath-prof-1.1.0.3-73da5, 
> > libghc6-ghc-prof-6.12.1-cf255, (>= 
> > 2.3.3-10.7.25.35.73.5.224.1-32.20.1-118.0.131:2.17.2-3.111.51.0.5-40.4.878.5-12.11-44:4.4.4-24.4.4-60.5.5.1-72.141.5.321.5.322.7-1.17.9.32009.01.313.2.31:3.0-12:1.02.48-21.15.7.21.15.7.21.41.12-21.41.12-21.14.4-15.04-24.4.2-14:4.4.4-24.4.4-64:4.4.4-24.4.4-64.4.4-60.18.1.1-10.18.1.1-16.12.1-136.12.1-131.4.10-41.4.10-42.6.3-31.20.1-101.3.12-91.18.4-20.7.103.041.16-15.7-21.3.2a-152.88dsf-91.14.0-20.35.0+20060710.12.2.49-31:2.4.44-22.17.2-3.10.2.0-10.2.0-11.0.5-42.11.2-12.11.2-12.11.2-12.11.

Bug#588005: Does antlr3 really requires maven ?

[Ludovic Claude]

This dependency is marked as required as gunit-maven-plugin is included 
in the main package. It would be better indeed to put gunit.jar and 
gunit-maven-plugin.jar in a separate package.


maven-debian-helper is not yet able to install the jars in several 
packages, I will try to fix that soon.


Ludovic

Le 03/07/2010 22:36, Vincent Fourmond a écrit :


Package: antlr3
Version: 3.2-3
Severity: wishlist

   Hello,

   While upgrading to the newer antlr3 (3.2-3), I noticed that the
newer antlr3 pulls in maven libmaven2-core-java, which in turn pulls
in about 33 MB of dependencies. Is that absolutely necessary to run
antlr3 ? As maven is a project management tool, I find it weird.

   I'm glad a lot of work has been invested into making debian packages
maven-friendly, but that would be great if that didn't mean we have to
force maven on all users of java software.

   In short, with maven downgraded to a Recommend, would antlr3 still
work ?

   Many thanks,

Vincent

-- System Information:
Debian Release: squeeze/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages antlr3 depends on:
ii  default-jre [java2-runtime]   1.6-38 Standard Java or Java compatible R
ii  default-jre-headless  1.6-38 Standard Java or Java compatible R
ii  libstringtemplate-java3.2.1-1StringTemplate templating engine f
ii  openjdk-6-jre [java2-runtime] 6b18-1.8-3 OpenJDK Java runtime, using Hotspo

Versions of packages antlr3 recommends:
pn  antlr3-gcj  (no description available)

antlr3 suggests no packages.

-- no debconf information




__
This is the maintainer address of Debian's Java team
. Please 
use
debian-j...@lists.debian.org for discussions and questions.







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587997: Fails to run on mipsel

[Jakub Wilk]

* Matt Kraai , 2010-07-03, 11:38:

I backported pytrainer 1.7.2-1 to lenny and tried to run it on a
mipsel machine, but it failed to run with the following error:

Unsupported sys.platform: linux2-mipsel.

The attached patch fixed this problem.


pytrainer won't run also on kfreebsd-* and hurd-*, both with and without 
Matt's patch. Please consider applying my (untested, sorry) patch 
instead.


--
Jakub Wilk
--- pytrainer-1.7.2.orig/pytrainer/lib/system.py
+++ pytrainer-1.7.2/pytrainer/lib/system.py
@@ -37,12 +37,12 @@
 		self._setGpxDir()
 
 	def _setHome(self):
-		if sys.platform == "linux2":
+		if os.name == 'posix':
 			variable = 'HOME'
-		elif sys.platform == "win32":
+		elif os.name == 'nt':
 			variable = 'USERPROFILE'
 		else:
-			print "Unsupported sys.platform: %s." % sys.platform
+			print "Unsupported os.name: %s." % os.name
 			sys.exit(1)
 		self.home = os.environ[variable]
 
@@ -65,12 +65,12 @@
 	os.remove(os.path.join(self.tmpdir, name))

 	def _setConfFiles(self):
-		if sys.platform == "win32":
+		if os.name == 'nt':
 			self.confdir = self.home+"/pytrainer"
-		elif sys.platform == "linux2":
+		elif os.name == 'posix':
 			self.confdir = self.home+"/.pytrainer"
 		else:
-			print "Unsupported sys.platform: %s." % sys.platform
+			print "Unsupported os.name: %s." % os.name
 			sys.exit(1)
 		self.conffile = self.confdir+"/conf.xml"
 		if not os.path.isdir(self.confdir):


signature.asc
Description: Digital signature

Bug#587607: joystick and inputattach no longer exist on s390

[steve]

On Fri, 2 Jul 2010 20:20:29 -0700, Vagrant Cascadian
 wrote:
> On Wed, Jun 30, 2010 at 10:04:39AM +0200, st...@sk2.org wrote:
>> ltsp-client depends on inputattach | joystick, unfortunately neither
are
>> built on s390 any more. Would it be possible to add a !s390 qualifier
to
>> the dependencies? (I don't think ltsp-client on s390 would need
>> inputattach!)
> 
> it's debateable weather s390 would make a decent thin-client at all,
though
> people often come up for unusual use-cases for LTSP. :)

That's what I thought too ;-)

>> Incidentally, I imagine it's really inputattach you're after with this
>> dependency; it might be worth adding (<< 20051019-7) to the joystick
>> dependency since versions of joystick from 20051019-7 onwards no longer
>> provide inputattach, and installing joystick without inputattach would
>> satisfy the dependency without actually providing an inputattach
binary.
> 
> inputattach is the reason for the dependency, yes. thanks for the
> suggestion.
> 
> committed both changes to bzr, and should be included in the next
upload.

Thanks!

Regards,

Stephen




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588005: Does antlr3 really requires maven ?

[Vincent Fourmond]

Package: antlr3
Version: 3.2-3
Severity: wishlist

  Hello,

  While upgrading to the newer antlr3 (3.2-3), I noticed that the
newer antlr3 pulls in maven libmaven2-core-java, which in turn pulls
in about 33 MB of dependencies. Is that absolutely necessary to run
antlr3 ? As maven is a project management tool, I find it weird.

  I'm glad a lot of work has been invested into making debian packages
maven-friendly, but that would be great if that didn't mean we have to
force maven on all users of java software.

  In short, with maven downgraded to a Recommend, would antlr3 still
work ? 

  Many thanks,

   Vincent

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages antlr3 depends on:
ii  default-jre [java2-runtime]   1.6-38 Standard Java or Java compatible R
ii  default-jre-headless  1.6-38 Standard Java or Java compatible R
ii  libstringtemplate-java3.2.1-1StringTemplate templating engine f
ii  openjdk-6-jre [java2-runtime] 6b18-1.8-3 OpenJDK Java runtime, using Hotspo

Versions of packages antlr3 recommends:
pn  antlr3-gcj (no description available)

antlr3 suggests no packages.

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588004: libc6: abort segfaults under race condition with bsd_signal

[brian m. carlson]

Package: libc6
Version: 2.11.2-2
Severity: normal

In the attached source code, there is a race condition between
bsd_signal and abort.  In most instances when the program is run, abort
successfully terminates the program with a SIGABRT.  However, on a very
rare occasion, the program instead terminates with a SIGSEGV.  This
should not happen, as it contradicts both POSIX 1003.1-2008 and also the
abort(3) man page.

Since this condition is very hard to reproduce, I ran it as follows:

  for i in `seq 1 10`; do (ulimit -c unlimited; ./testcase; if [ $? -eq 139 
]; then cp core core.segv; fi); done

"gdb ./testcase core.segv" then gives the following:

  (gdb) bt full
  #0  *__GI_abort () at abort.c:128
  act = {__sigaction_handler = {sa_handler = 0, sa_sigaction = 0}, 
sa_mask = {__val = {18446744073709551615 }}, 
sa_flags = 0, sa_restorer = 0}
  sigs = {__val = {32, 0 }}
  #1  0x0040067a in main () at testcase.c:23
  thrd = 140157473478416

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

Kernel: Linux 2.6.34-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6 depends on:
ii  libc-bin  2.11.2-2   Embedded GNU C Library: Binaries
ii  libgcc1   1:4.5.0-7  GCC support library

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  cdebconf [debconf-2.0]0.149  Debian Configuration Management Sy
ii  debconf [debconf-2.0] 1.5.32 Debian configuration management sy
pn  glibc-doc  (no description available)
ii  locales   2.11.2-2   Embedded GNU C Library: National L

-- debconf information excluded

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
/* Compile with: gcc -g -O3 -pthread -o testcase testcase.c */

#include 
#include 

#ifdef NIH
extern void abort(void);
#else
#include 
#endif

void *ignore_sigabrt(void *dummy)
{
	for (;;)
		bsd_signal(SIGABRT, SIG_IGN);
}

int main(void)
{
	pthread_t thrd;

	pthread_create(&thrd, NULL, ignore_sigabrt, NULL);
	pthread_detach(thrd);

	abort();

	return 0;
}


signature.asc
Description: Digital signature

Bug#402721: Please make clear, that "conflicts" should only be used when really necessary

[Russ Allbery]

Tobias Frost  writes:

> Looking at #262257, as an exampple, there are packages which declares
> conflicts for whatever reason. However, the reason is NOT, that thec
> packages could not co-existent on the same system (For the example,
> retchmail could be also installed with fetchmail -- they do not
> interfere)

> My wishlist-entry would be to clarify, tha conflicts should only be
> used, if the packages "won't do" if both installed... (as the word
> "conflict" implies. The reason "the other package is doing the same, so
> conflict on it to prevent both installed" is -- IMHO -- not the
> intention of conflicts

This really should be common sense, but it doesn't hurt to say it
explicitly, which I don't think we were doing before.  Here's a patch that
implements that.

Objections or seconds?

diff --git a/policy.sgml b/policy.sgml
index bad28af..efda2a1 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -4778,6 +4778,15 @@ Build-Depends: foo [linux-any], bar [any-i386], baz 
[!linux-any]

 

+ Neither Breaks nor Conflicts should be used
+ unless two packages cannot be installed at the same time or
+ installing them both causes one of them to be broken or
+ unusable.  Having similar functionality or performing the same
+ tasks as another package is not sufficient reason to
+ declare Breaks or Conflicts with that package.
+   
+
+   
  A Conflicts entry may have an "earlier than" version
  clause if the reason for the conflict is corrected in a later
  version of one of the packages.  However, normally the presence

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588003: "Need help?" link doesn't work

[Erik Esterer]

Package: qutecom
Version: 2.2~rc3.hg396~dfsg1-6+b1
Severity: normal

The window to configure the SIP profile has a "Need help?" link on the bottom 
left corner, but it doesn't work.
Clicking on this link has no effect at all: nothing happens..

Erik 

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (20, 'experimental'), (20, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qutecom depends on:
ii  libasound2 1.0.23-1  shared library for ALSA applicatio
ii  libavcodec52   5:0.5+svn20091129-0.0 library to encode decode multimedi
ii  libavutil494:0.5.2-1 ffmpeg utility library
ii  libboost-program-o 1.42.0-3  program options library for C++
ii  libboost-serializa 1.42.0-3  serialization library for C++
ii  libboost-signals1. 1.42.0-3  managed signals and slots library 
ii  libboost-thread1.4 1.42.0-3  portable C++ multi-threading
ii  libc6  2.11.2-2  Embedded GNU C Library: Shared lib
ii  libcurl3   7.21.0-1  Multi-protocol file transfer libra
ii  libgcc11:4.4.4-5 GCC support library
ii  libglib2.0-0   2.24.1-1  The GLib library of C routines
ii  libpurple0 2.7.1-1   multi-protocol instant messaging l
ii  libqt4-dbus4:4.6.3-1 Qt 4 D-Bus module
ii  libqt4-network 4:4.6.3-1 Qt 4 network module
ii  libqt4-svg 4:4.6.3-1 Qt 4 SVG module
ii  libqt4-xml 4:4.6.3-1 Qt 4 XML module
ii  libqtcore4 4:4.6.3-1 Qt 4 core module
ii  libqtgui4  4:4.6.3-1 Qt 4 GUI module
ii  libsamplerate0 0.1.7-3   Audio sample rate conversion libra
ii  libsndfile11.0.21-2  Library for reading/writing audio 
ii  libspeex1  1.2~rc1-1 The Speex codec runtime library
ii  libssl0.9.80.9.8o-1  SSL shared libraries
ii  libstdc++6 4.4.4-5   The GNU Standard C++ Library v3
ii  libswscale05:0.5+svn20091129-0.0 ffmpeg video scaling library
ii  libuuid1   2.17.2-3.1Universally Unique ID library
ii  libx11-6   2:1.3.3-3 X11 client-side library
ii  libxau61:1.0.5-2 X11 authorisation library
ii  libxdmcp6  1:1.0.3-2 X11 Display Manager Control Protoc
ii  qutecom-data   2.2~rc3.hg396~dfsg1-6 SIP-based software telephone with 

qutecom recommends no packages.

qutecom suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#571339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571339#15

[Lior Kaplan]

That patch is only for configure.in, and as I wrote in the mail before that:

> After fixing the configure.in/configure about this change, the configure
> scripts fails on some of the fribidi funtionality tests.

I'm sorry if there was an impression I fixed the problem completely.


2010/7/3 Ron Varburg 

>
> Haven't you provided a patch in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571339#15 ?
> Wasn't that patch coordinated with upstream?
>

Bug#587985: [firmware-realtek] Please provide a RTL8191S kernel module

[Ben Hutchings]

On Sat, 2010-07-03 at 20:40 +0100, Antonio Marcos López Alonso wrote:
> El Sábado 03 Julio 2010, escribió:
> > On Sat, 2010-07-03 at 16:26 +0100, Antonio Marcos López Alonso wrote:
> > > Package: firmware-realtek
> > > Version: 0.25
> > > Severity: wishlist
> > 
> > This package is for firmware, not kernel modules.  The clue is in the
> > name.
> > 
> > We aleady provide the rtl8192s_usb kernel module which should handle the
> > RTL8191S, but it does not currently list the right device ID.  I'll try
> > to fix that.
> > 
> > Ben.
> 
> I own an USB wlan dongle (Sitecom WL-352) which claims to be a rtl8191s 
> device 
> (usb-devices). 
> 
> I manually modprobed rtl8192s_usb, then restarted networking service but 
> iwconfig says no wireless extensions are detected.
> 
> Should I file a normal bug report?

No, I've reassigned this bug to the kernel package (linux-2.6) and it
should be fixed in the next version.  Let us know if it isn't.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#585279: closed by Matthias Klose (Re: python2.7-examples: Python string exceptions no more allowed in Python 2.6)

[Sandro Tosi]

reopen 585279
tags 585279 - upstream
thanks

> -- Forwarded message --
> From: Matthias Klose 
> To: 585279-d...@bugs.debian.org
> Date: Sat, 03 Jul 2010 13:47:18 +0200
> Subject: Re: python2.7-examples: Python string exceptions no more allowed in 
> Python 2.6
> tag 585279 + upstream
> tag 585279 + wontfix
> forwarded 585279 http://bugs.python.org/issue9113
> thanks
>
> upstream comment:
>> This is not a problem. Tools/msi is being used with Python 2.5 only.

So stop shipping them in the Debian package (the real solution is
removing them upstream). And stop closing bugs without a clue and
discussing it with the submitter.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#445203: debian-policy: 10.8. Log files: /etc/logrotate.d/ preferred

[Russ Allbery]

Paul Martin  writes:

> Section 10.8 suggests the use of a configuration file in
> /etc/logrotate.d, but doesn't suggest a name.

> I propose that the suggested name be /etc/logrotate.d/ in
> almost all circumstances, irrespective of the name(s) of the files being
> rotated. A logrotate.d configuration file can control the rotation of
> multiple logfiles.

> In addition, could the "missingok" directive be added to the example
> script? If the maintainer forgets to use it and the package is removed
> but not purged before the package generates any log files, it can cause
> logrotate to throw errors during the cron.daily run.

Here's a proposed patch that implements this.  Objections or seconds?

diff --git a/policy.sgml b/policy.sgml
index bad28af..a676e71 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7868,11 +7868,13 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq

 

- Log files must be rotated occasionally so that they don't
- grow indefinitely; the best way to do this is to drop a log
- rotation configuration file into the directory
- /etc/logrotate.d and use the facilities provided by
- logrotate.
+ Log files must be rotated occasionally so that they don't grow
+ indefinitely.  The best way to do this is to install a log
+ rotation configuration file in the
+ directory /etc/logrotate.d, normally
+ named /etc/logrotate.d/package, and use
+ the facilities provided by logrotate.
+ 

  The traditional approach to log files has been to set up
  ad hoc log rotation schemes using simple shell
@@ -7897,25 +7899,28 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
section="8">):
  
 /var/log/foo/*.log {
-rotate 12
-weekly
-compress
-postrotate
-/etc/init.d/foo force-reload
-endscript
+rotate 12
+weekly
+compress
+missingok
+postrotate
+/etc/init.d/foo force-reload
+endscript
 }
  
  This rotates all files under /var/log/foo, saves 12
  compressed generations, and forces the daemon to reload its
- configuration information after the log rotation.
+ configuration information after the log rotation.  It skips this
+ log rotation (via missingok) if no such log file is
+ present, which avoids errors if the package is removed but not
+ purged.

 

- Log files should be removed when the package is
- purged (but not when it is only removed).  This should be
- done by the postrm script when it is called
- with the argument purge (see ).
+ Log files should be removed when the package is purged (but not
+ when it is only removed).  This should be done by
+ the postrm script when it is called with the
+ argument purge (see ).

   

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588002: jove: Beginners menu doesn't work

[Uwe Kappe]

Package: jove
Version: 4.16.0.72-2
Severity: normal

Hi everyone,

since the last upgrade the beginners menu doesn't work. The menu is
shown but pressing F1 vor example executes the command [Esc] x.

Best Regards from Eifel/ Germany
Uwe

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ANSI_X3.4-1968) (ignored: 
LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash

Versions of packages jove depends on:
ii  debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libncurses5   5.7+20100313-2 shared libraries for terminal hand

Versions of packages jove recommends:
ii  postfix [mail-transport-agent 2.7.1-1High-performance mail transport ag

jove suggests no packages.

-- Configuration Files:
/etc/jove/jove.rc changed:
pushlibd
define-macro kill-line 
^[xbeginning-of-line^M^[xset-mark^M^[xnext-line^M^[xkill-region^M^[xpop-mark^M
define-macro nice-right-margin ^[xset right-margin 70^M
1 auto-execute-command auto-fill-mode 
/tmp/\{Re\|article\|rnmail\|snd\.\|nn\.\|post\|mutt\|pn\}
1 auto-execute-macro nice-right-margin 
/tmp/\{Re\|article\|rnmail\|snd\.\|nn\.\|post\|mutt\|pn\}
1 auto-execute-command auto-indent-mode 
/tmp/\{Re\|article\|rnmail\|snd\.\|nn\.\|post\|mutt\|pn\}
1 auto-execute-command auto-fill-mode .*
0 auto-execute-command auto-fill-mode 
.*\.[lcChyfp]$\|.*\.lisp$\|.*\.pl$\|.*\.scm$\|.*\.c++$
1 auto-execute-command auto-indent-mode .*
0 auto-execute-command auto-indent-mode 
.*\.[lcChyfp]$\|.*\.lisp$\|.*\.pl$\|.*\.scm$\|.*\.c++$
1 auto-execute-command c-mode .*\.[cChy]$\|.*\.c++$\|.*\.pl$
1 auto-execute-command lisp-mode .*\.l$\|.*\.lisp$\|.*\.scm$
1 auto-execute-command show-match-mode 
.*\.[lcChyfp]$\|.*\.lisp$\|.*\.scm$\|.*\.c++$\|.*\.pl$
bind-to-key pause-jove ^[S
bind-to-key pause-jove ^[s
set process-prompt ^[^%$#]*[%$#] 
process-bind-to-key interrupt-process ^C^C
process-bind-to-key eof-process ^C^D
process-bind-to-key quit-process ^C^\
process-bind-to-key stop-process ^C^Z
process-bind-to-key dstop-process ^C^Y
bind-to-key previous-line ^[[A
bind-to-key next-line ^[[B
bind-to-key forward-character ^[[C
bind-to-key backward-character ^[[D
bind-to-key previous-line ^[OA
bind-to-key next-line ^[OB
bind-to-key forward-character ^[OC
bind-to-key backward-character ^[OD
set mode-line %[Jove%]%w%w%c(%M)%3c[%b:%n]%2c"%f"%c%i# %m*-%2c%p%2s%(%d%e(%t)%)
set allow-^S-and-^Q on
set disable-biff on
if sh -c 'test ! -f $HOME/.joverc'
source jem.rc
auto-execute-command delete-other-windows .*/teach-jove
endif
1 source jove.rc.$TERM
1 source /etc/jove/jove-local.rc
popd


-- debconf information:
  jove/upgradewarn-2:
  jove/upgradewarn-1:



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#571339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571339#15

[Ron Varburg]

Haven't you provided a patch in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571339#15 ?
Wasn't that patch coordinated with upstream?

> Date: Sat, 3 Jul 2010 22:52:27 +0300
> Subject: Re: Bug#571339: Have you uploaded a new version?
> From: kaplanl...@gmail.com
> To: linux...@hotmail.com
> CC: 571...@bugs.debian.org
>
> Because there isn't any new upstream version and no one provided a patch to 
> fix the FTBFS.
>
> 2010/7/3 Ron Varburg>
>
>
>
> Why is that?
>
>
>
> 
>
>> Date: Sat, 3 Jul 2010 20:07:02 +0300
>
>> Subject: Re: Bug#571339: Have you uploaded a new version?
>
>> From: kaplanl...@gmail.com
>
>> To: linux...@hotmail.com; 571...@bugs.debian.org
>
>>
>
>> Nope.
>
>>
>
>> 2010/7/3 Ron Varburg>
>
>>
>
>>
>
>>
>
>> Have you uploaded a new version?
>
>>
>
>>
>
>>
>
>> _
>
>>
>
>> Hotmail: דואר אלקטרוני מהימן עם הגנה רבת עוצמה של Microsoft מפני הודעות זבל.
>
>>
>
>> https://signup.live.com/signup.aspx?id=60969
>
>>
>
>
>
> _
>
> גישה לדואר אלקטרוני ולשירותים נוספים גם בנסיעות. קבל את Windows Live Hotmail 
> בחינם.
>
> https://signup.live.com/signup.aspx?id=60969
>
  
_
גישה לדואר אלקטרוני ולשירותים נוספים גם בנסיעות. קבל את Windows Live Hotmail 
בחינם.
https://signup.live.com/signup.aspx?id=60969

Bug#588001: FTBFS: shlibs parsing error

[Riku Voipio]

Package: haskell-haddock
Version: 2.7.2-4
Severity: serious

Package fails to build on the armel buildd:

> Kernel: Linux 2.6.26-2-iop32x armel (armv5tel)
> Toolchain package versions: libc6-dev_2.11.2-1 dpkg-dev_1.15.7.2 
> linux-libc-dev_2.6.32-15 gcc-4.4_4.4.4-6 g++-4.4_4.4.4-6 binutils_2.20.1-11 
> libstdc++6-4.4-dev_4.4.4-6 libstdc++6_4.4.4-6
> Package versions: alex_2.3.3-1 apt_0.7.25.3 base-files_5.7 base-passwd_3.5.22 
> bash_4.1-3 binutils_2.20.1-11 bsdmainutils_8.0.13 bsdutils_1:2.17.2-3.1 
> build-essential_11.5 bzip2_1.0.5-4 cdbs_0.4.87 coreutils_8.5-1 cpio_2.11-4 
> cpp_4:4.4.4-2 cpp-4.4_4.4.4-6 dash_0.5.5.1-7 dctrl-tools_2.14 debconf_1.5.32 
> debconf-english_1.5.32 debfoster_2.7-1.1 debhelper_7.9.3 
> debian-archive-keyring_2009.01.31 debianutils_3.2.3 diffutils_1:3.0-1 
> dmsetup_2:1.02.48-2 dpkg_1.15.7.2 dpkg-dev_1.15.7.2 e2fslibs_1.41.12-2 
> e2fsprogs_1.41.12-2 fakeroot_1.14.4-1 file_5.04-2 findutils_4.4.2-1 
> g++_4:4.4.4-2 g++-4.4_4.4.4-6 gcc_4:4.4.4-2 gcc-4.4_4.4.4-6 
> gcc-4.4-base_4.4.4-6 gettext_0.18.1.1-1 gettext-base_0.18.1.1-1 
> ghc6_6.12.1-13 ghc6-prof_6.12.1-13 gnupg_1.4.10-4 gpgv_1.4.10-4 grep_2.6.3-3 
> groff-base_1.20.1-10 gzip_1.3.12-9 happy_1.18.4-2 haskell-devscripts_0.7.10 
> hostname_3.04 hscolour_1.16-1 html-xml-utils_5.7-2 html2text_1.3.2a-15 
> initscripts_2.88dsf-9 insserv_1.14.0-2 intltool-debian_0.35.0+20060710.1 
> libacl1_2.2.49-3 libattr1_1:2.4.44
> -2 libblkid1_2.17.2-3.1 libbsd-dev_0.2.0-1 libbsd0_0.2.0-1 libbz2-1.0_1.0.5-4 
> libc-bin_2.11.2-1 libc-dev-bin_2.11.2-1 libc6_2.11.2-1 libc6-dev_2.11.2-1 
> libcomerr2_1.41.12-2 libcroco3_0.6.2-1 libdb4.7_4.7.25-9 libdb4.8_4.8.30-1 
> libdevmapper1.02.1_2:1.02.48-2 libdpkg-perl_1.15.7.2 libffi-dev_3.0.9-2 
> libffi5_3.0.9-2 libgc1c2_1:6.8-1.2 libgcc1_1:4.4.4-6 libgcrypt11_1.4.5-2 
> libgdbm3_1.8.3-9 libghc6-ghc-paths-dev_0.1.0.6-1 libglib2.0-0_2.24.1-1 
> libgmp3-dev_2:4.3.2+dfsg-1 libgmp3c2_2:4.3.2+dfsg-1 
> libgmpxx4ldbl_2:4.3.2+dfsg-1 libgnutls26_2.8.6-1 libgomp1_4.4.4-6 
> libgpg-error0_1.6-1 libldap-2.4-2_2.4.21-1 liblzma2_4.999.9beta+20100527-1 
> libmagic1_5.04-2 libmpfr1ldbl_2.4.2-3 libncurses5_5.7+20100313-2 
> libopencdk10_0.6.6-1 libpam-modules_1.1.1-3 libpam-runtime_1.1.1-3 
> libpam0g_1.1.1-3 libpcre3_8.02-1 libreadline6_6.1-3 libsasl2-2_2.1.23.dfsg1-5 
> libselinux1_2.0.94-1 libsepol1_2.0.41-1 libslang2_2.2.2-4 libss2_1.41.12-2 
> libstdc++6_4.4.4-6 libstdc++6-4.4-dev_4.4.4-6 libtasn1-3_2.7-1 
> libtimedate-perl_1.2000-1 libudev0_158-

-snip-

> dpkg-gencontrol: warning: Depends field of package libghc6-haddock-prof: 
> unknown substitution variable ${shlibs:Depends}
> dpkg-gencontrol: warning: can't parse dependency (>= 
> 2.3.3-10.7.25.35.73.5.224.1-32.20.1-118.0.131:2.17.2-3.111.51.0.5-40.4.878.5-12.11-44:4.4.4-24.4.4-60.5.5.1-72.141.5.321.5.322.7-1.17.9.32009.01.313.2.31:3.0-12:1.02.48-21.15.7.21.15.7.21.41.12-21.41.12-21.14.4-15.04-24.4.2-14:4.4.4-24.4.4-64:4.4.4-24.4.4-64.4.4-60.18.1.1-10.18.1.1-16.12.1-136.12.1-131.4.10-41.4.10-42.6.3-31.20.1-101.3.12-91.18.4-20.7.103.041.16-15.7-21.3.2a-152.88dsf-91.14.0-20.35.0+20060710.12.2.49-31:2.4.44-22.17.2-3.10.2.0-10.2.0-11.0.5-42.11.2-12.11.2-12.11.2-12.11.2-11.41.12-20.6.2-14.7.25-94.8.30-12:1.02.48-21.15.7.23.0.9-23.0.9-21:6.8-1.21:4.4.4-61.4.5-21.8.3-90.1.0.6-12.24.1-12:4.3.2+dfsg-12:4.3.2+dfsg-12:4.3.2+dfsg-12.8.6-14.4.4-61.6-12.4.21-14.999.9beta+20100527-15.04-22.4.2-35.7+20100313-20.6.6-11.1.1-31.1.1-31.1.1-38.02-16.1-32.1.23.dfsg1-52.0.94-12.0.41-12.2.2-41.41.12-24.4.4-64.4.4-62.7-11.2000-1158-10.9.3-12:0.1.12-152.17.2-3.12.7.7.dfsg-42.6.32-151:4.1.4.2-1+b23.2-23.13.81-82.5.7-31.3.3-152.17.2-3.15.7+20100313-25.7+201003
> 13-21:4.1.4.2-1+b22.6-25.10.1-135.10.1-135.10.1-131.0.166.1-34.2.1-70.0.41.7.2p7-12.88dsf-92.88dsf-92.88dsf-91.23-22010j-1158-12.17.2-3.11:7.5+34.999.9beta+20100527-11:1.2.3.4.dfsg-3)
> dpkg-gencontrol: error: error occurred while parsing Depends field: 
> libghc6-haddock-dev (=2.7.2-4), libghc6-cabal-prof-1.8.0.2-80b8f, 
> libghc6-array-prof-0.3.0.0-dbdf7, libghc6-base-prof-4.2.0.0-14b6a, 
> libghc6-containers-prof-0.3.0.0-409fe, libghc6-directory-prof-1.0.1.0-78675, 
> libghc6-filepath-prof-1.1.0.3-73da5, libghc6-ghc-prof-6.12.1-cf255, (>= 
> 2.3.3-10.7.25.35.73.5.224.1-32.20.1-118.0.131:2.17.2-3.111.51.0.5-40.4.878.5-12.11-44:4.4.4-24.4.4-60.5.5.1-72.141.5.321.5.322.7-1.17.9.32009.01.313.2.31:3.0-12:1.02.48-21.15.7.21.15.7.21.41.12-21.41.12-21.14.4-15.04-24.4.2-14:4.4.4-24.4.4-64:4.4.4-24.4.4-64.4.4-60.18.1.1-10.18.1.1-16.12.1-136.12.1-131.4.10-41.4.10-42.6.3-31.20.1-101.3.12-91.18.4-20.7.103.041.16-15.7-21.3.2a-152.88dsf-91.14.0-20.35.0+20060710.12.2.49-31:2.4.44-22.17.2-3.10.2.0-10.2.0-11.0.5-42.11.2-12.11.2-12.11.2-12.11.2-11.41.12-20.6.2-14.7.25-94.8.30-12:1.02.48-21.15.7.23.0.9-23.0.9-21:6.8-1.21:4.4.4-61.4.5-21.8.3-90.1.0.6-12.24.1-12:4.3.2+dfsg-12:4.3.2+dfsg-12:4.3.2+dfsg-12.8.6-14.4.4-61.6-12.4
> .21-14.999.9beta+20100527-15.04-22.4.2-35.7+20100313-20.6.6-11.1.1-31.1.1-31.1.1-38.02-16.1-32.1.23.dfsg1-52.0.94-12.0.4

Bug#539643: [caff] Try to import key from user keyring first

[Franck Joncourt]

tag 539643 + pending 
retitle 539643 [caff] Try to import key from user keyring first
thanks

Hi Martin,

Commit message:

* caff:
  + Imported keys to be signed from the user GnuPGHome first. Thus, keys
from the key files are not imported if all of the keys are found in the
user GnuPGHome. (Closes: #539643)

I think that should work now in the next release.

Regards,

-- 
Franck Joncourt


signature.asc
Description: Digital signature

Bug#549080: a followup problem

[Heiko Stübner]

After reading [1] it seems to me more work is required there as also the 
kfreebsd architectures have the same problem which won't be fixed by my change. 
[I hadn't thought of the non-linux arches before]

So the core of the problem remains the same  but another solution must be 
found for it.


Could simply defaulting to yes for this check (via a patch) solve it, as we 
only use the gnu userspace at all?


On the other hand the kfreebasd ports are not relase-architectures yet so my 
change could push the final resolve of the bug past sqeezes release depending 
on the workload of people more knowledgable in autotools stuff.


Heiko


[1] http://lists.debian.org/debian-devel/2010/07/msg00051.html



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#459868: debian-policy: Definition of Maintainer: when using a mailing list

[Russ Allbery]

Joerg Jaspert  writes:

> I think policy should include some words on the usage of Mailinglists as
> a Maintainer: address.

[...]

> I propose to add, someone please fix up en_GANNEFF:

> ---+++---
> If the Maintainer address points to a mailing list then that list must
> be configured to accept mail from those role accounts in Debian used to
> send automated mails regarding the package. This includes mail from the
> BTS, all mails from the archive software used on ftp-master as well as
> other role accounts that are commonly agreed on to send automated mails
> to the maintainers. a sample implementation of such a whitelist for
> mailman is running on alioth.debian.org.
> ---+++---

> Additionally I would like:

> +++---+++
> If the Maintainer: field points to a mailing list then the Uploader:
> field has to contain at least one human.
> ---+++---

After reviewing the discussion in this bug and the current maintainer
section in Policy, I propose the following patch, which also defines the
responsibilities of the maintainer more clearly (if we're going to
introduce the term, we should define it, and I think this stays short of
devref territory) and brings the section on orphaning packages more in
line with current project practices.

Objections or seconds?

diff --git a/policy.sgml b/policy.sgml
index bad28af..1bc37b3 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -886,23 +886,38 @@
 
   
 
-  
+  
The maintainer of a package
 

- Every package must have a Debian maintainer (the
- maintainer may be one person or a group of people
- reachable from a common email address, such as a mailing
- list).  The maintainer is responsible for ensuring that
- the package is placed in the appropriate distributions.
-   
-
-   
- The maintainer must be specified in the
- Maintainer control field with their correct name
- and a working email address.  If one person maintains
- several packages, they should try to avoid having
- different forms of their name and email address in
+ Every package must have a Debian maintainer.  The maintainer may
+ be one person or a group of people reachable from a common email
+ address, such as a mailing list.  The maintainer is responsible
+ for maintaining the Debian packaging files, evaluating and
+ responding appropriately to reported bugs, uploading new
+ versions of the package, ensuring that the package is placed in
+ the appropriate archive area and included in Debian releases as
+ appropriate for the stability and utility of the package, and
+ requesting removal of the package from the Debian distribution
+ if it is no longer useful or maintainable.
+   
+
+   
+ The maintainer must be specified in the Maintainer
+ control field with their correct name and a working email
+ address.  The email address given in the Maintainer
+ control field must accept mail from those role accounts in
+ Debian used to send automated mails regarding the package.  This
+ includes non-spam mail from the bug-tracking system, all mail
+ from the Debian archive maintenance software, and other role
+ accounts or automated processes that are commonly agreed on by
+ the project.
+   A sample implementation of such a whitelist written for the
+   Mailman mailing list management software is used for mailing
+   lists hosted by alioth.debian.org.
+ 
+ If one person or team maintains several packages, they should
+ use the same form of their name and email address in
  the Maintainer fields of those packages.

 
@@ -912,15 +927,22 @@

 

- If the maintainer of a package quits from the Debian
- project, "Debian QA Group"
- packa...@qa.debian.org takes over the
- maintainer-ship of the package until someone else
- volunteers for that task. These packages are called
- orphaned packages.
-   The detailed procedure for doing this gracefully can
-   be found in the Debian Developer's Reference,
-   see .
+ If the maintainer of the package is a team of people with a
+ shared email address, the Uploaders control field must
+ be present and must contain at least one human with their
+ personal email address.  See  for the
+ syntax of that field.
+   
+
+   
+ If the maintainer of a package no longer has time or desire to
+ maintain a package, it is orphaned.  The maintainer then becomes
+ Debian QA Group .  These
+ packages are considered maintained by the Debian project as a
+ whole until someone else volunteers to take over maintenance.
+ 
+   The detailed pro

Bug#587999: Xv switches pixel columns

[Julien Cristau]

reassign 587999 xserver-xorg-video-radeon
retitle 587999 [powerpc] Xv switches pixel columns
kthxbye

On Sat, Jul  3, 2010 at 21:22:17 +0200, Ulrich Eckhardt wrote:

> Package: xserver-xorg
> Version: 1:7.5+6
> 
> Using mplayer and xine (didn't try others) with Xv as video output driver, I 
> have the effect that the order of pixel columns is switched. If I use 24 bits 
> color depth, the order is 1,0,3,2 etc. Using 16 bits color depth, the order 
> is 
> 3,2,1,0,7,6,5,4.
> 
> Notes:
>  * I'm using the radeon driver backend.
>  * I'm on a big-endian machine (PPC).
> 
> As a workaround, I can use xshm as video output driver.
> 
Please use 'reportbug -N 587999' to include the necessary information.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#586621: Patch

[Matt Kraai]

tag 586621 patch
thanks

Hi,

As Julien notes, on systems that don't allow embedding, the copy of
core.img in memory is modified before it's compared against the
version read directly from disk.  install_bsd_part and
install_dos_part, which are also used to modify the in-memory copy of
core.img, work around this by only being written to after comparing
core_img to what's on disk.  The attached patch does the same for
prefix, which allowed grub-setup to succeed on my system which was
previously exhibiting the problem.

On a probably unrelated note, when I boot, grub displays an

 error: file not found

error, dumps me into rescue mode, and I can't figure out how to
proceed (ls works but all insmod commands fail with the same error).
I assume this is unrelated, but I may be wrong (and would love for
help).

-- 
Matt  http://ftbfs.org/kraai
diff -ru grub2-1.98+20100702~/util/i386/pc/grub-setup.c grub2-1.98+20100702/util/i386/pc/grub-setup.c
--- grub2-1.98+20100702~/util/i386/pc/grub-setup.c	2010-07-03 12:12:41.0 -0700
+++ grub2-1.98+20100702/util/i386/pc/grub-setup.c	2010-07-03 12:14:07.0 -0700
@@ -99,7 +99,7 @@
   struct grub_boot_blocklist *first_block, *block;
   grub_int32_t *install_dos_part, *install_bsd_part;
   grub_int32_t dos_part, bsd_part;
-  char *prefix;
+  char *new_prefix = NULL, *prefix;
   char *tmp_img;
   int i;
   grub_disk_addr_t first_sector;
@@ -311,12 +311,11 @@
 
 	  if (prefix[0] != '(')
 	{
-	  char *root_part_name, *new_prefix;
+	  char *root_part_name;
 
 	  root_part_name =
 		grub_partition_get_name (root_dev->disk->partition);
 	  new_prefix = xasprintf ("(,%s)%s", root_part_name, prefix);
-	  strcpy (prefix, new_prefix);
 	  free (new_prefix);
 	  free (root_part_name);
 	}
@@ -397,6 +396,9 @@
   *install_dos_part = grub_cpu_to_le32 (dos_part);
   *install_bsd_part = grub_cpu_to_le32 (bsd_part);
 
+  if (new_prefix != NULL)
+strcpy (prefix, new_prefix);
+
   /* The first blocklist contains the whole sectors.  */
   first_block->start = grub_cpu_to_le64 (embed_region.start + 1);
 
@@ -557,6 +559,9 @@
   *install_dos_part = grub_cpu_to_le32 (dos_part);
   *install_bsd_part = grub_cpu_to_le32 (bsd_part);
 
+  if (new_prefix != NULL)
+strcpy (prefix, new_prefix);
+
   /* Write the first two sectors of the core image onto the disk.  */
   grub_util_info ("opening the core image `%s'", core_path);
   fp = fopen (core_path, "r+b");

Bug#571339: Have you uploaded a new version?

[Lior Kaplan]

Because there isn't any new upstream version and no one provided a patch to
fix the FTBFS.

2010/7/3 Ron Varburg 

>
> Why is that?
>
> 
> > Date: Sat, 3 Jul 2010 20:07:02 +0300
> > Subject: Re: Bug#571339: Have you uploaded a new version?
> > From: kaplanl...@gmail.com
> > To: linux...@hotmail.com; 571...@bugs.debian.org
> >
> > Nope.
> >
> > 2010/7/3 Ron Varburg>
> >
> >
> >
> > Have you uploaded a new version?
> >
> >
> >
> > _
> >
> > Hotmail: דואר אלקטרוני מהימן עם הגנה רבת עוצמה של Microsoft מפני הודעות
> זבל.
> >
> > https://signup.live.com/signup.aspx?id=60969
> >
>
> _
> גישה לדואר אלקטרוני ולשירותים נוספים גם בנסיעות. קבל את Windows Live
> Hotmail בחינם.
> https://signup.live.com/signup.aspx?id=60969
>

Bug#588000: override: php-crypt-cbc:php/optional

[Thomas Goirand]

Package: ftp.debian.org
Severity: minor

Please set the section of this package to the new php section instead of
the old web section. I've just uploaded an new Debian release.

Cheers,

Zigo

-- System Information:
Debian Release: 5.0.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-4-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587985: [firmware-realtek] Please provide a RTL8191S kernel module

[Antonio Marcos López Alonso]

El Sábado 03 Julio 2010, escribió:
> On Sat, 2010-07-03 at 16:26 +0100, Antonio Marcos López Alonso wrote:
> > Package: firmware-realtek
> > Version: 0.25
> > Severity: wishlist
> 
> This package is for firmware, not kernel modules.  The clue is in the
> name.
> 
> We aleady provide the rtl8192s_usb kernel module which should handle the
> RTL8191S, but it does not currently list the right device ID.  I'll try
> to fix that.
> 
> Ben.

I own an USB wlan dongle (Sitecom WL-352) which claims to be a rtl8191s device 
(usb-devices). 

I manually modprobed rtl8192s_usb, then restarted networking service but 
iwconfig says no wireless extensions are detected.

Should I file a normal bug report?

Antonio




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#549080: fix

[Heiko Stübner]

Hi all,

it seems the configure script acts differently for glibc-based and other 
systems. Therefore it tests the "target_os" variable for equality to the 
strings "linux" or "linux-gnu" (configure.inc line 101) to determine if it's a 
glibc based systems.

On armel systems the target_os variable contains "linux-gnueabi" therefore 
doesn't match and changes the build system to create the result reported.

In the attached patch I simply added another possible string containing 
"linux-gnueabi" to this test.

After an autoreconf it built and produced a package with the same file 
structure expected from the other architectures.


Heiko
diff --git nss_ldap-264.orig/configure nss_ldap-264/configure
index d61531c..52da797 100755
--- nss_ldap-264.orig/configure
+++ nss_ldap-264/configure
@@ -3422,7 +3422,7 @@ fi
 
 
 
-if test "$target_os" = "linux" -o "$target_os" = "linux-gnu"; then
+if test "$target_os" = "linux" -o "$target_os" = "linux-gnu" -o "$target_os" = "linux-gnueabi"; then
   GLIBC_TRUE=
   GLIBC_FALSE='#'
 else
diff --git nss_ldap-264.orig/configure.in nss_ldap-264/configure.in
index 0453cf1..964acf1 100644
--- nss_ldap-264.orig/configure.in
+++ nss_ldap-264/configure.in
@@ -98,7 +98,7 @@ linux*) nss_ldap_so_LDFLAGS="-shared -Wl,-Bdynamic -Wl,--version-script,\$(srcdi
 esac
 
 AM_CONDITIONAL(GCC, test "$GCC" = "yes")
-AM_CONDITIONAL(GLIBC, test "$target_os" = "linux" -o "$target_os" = "linux-gnu")
+AM_CONDITIONAL(GLIBC, test "$target_os" = "linux" -o "$target_os" = "linux-gnu" -o "$target_os" = "linux-gnueabi")
 AM_CONDITIONAL(AIX, test "$TARGET_OS" = AIX)
 AM_CONDITIONAL(HPUX, test "$TARGET_OS" = HPUX)
 


signature.asc
Description: This is a digitally signed message part.

Bug#475101: obsolete linuxthreads requirement

[Russ Allbery]

Russ Allbery  writes:
> Kurt Roeckx  writes:

>> So it looks to me that _REENTRANT is only used to make some functions
>> like getlogin_r available.

> I believe that's correct, and the discussion at the last DebConf reached
> the same conclusion.  I think this bit in Policy is obsolete.  I already
> closed a Lintian bug about it a while back.

> You may separately need _REENTRANT to get prototypes, but using the right
> feature test macros to get prototypes is a completely different issue and
> I don't think we need to leave this in Policy just for that (otherwise,
> we'd need to talk about GNU_SOURCE and whatnot as well, and I don't see a
> need to go there right now).

>> I think that libraries in Debian should never change behaviour based on
>> _REENTRANT.  If a library can be build to either support threads or not,
>> it should be compiled to support threads.  It might also want to provide
>> one that does and one that doesn't so that you can link to either one,
>> but I would like to discourage that, and the default library should be
>> the one that supports threads.  And if it does provide 2 libraries, the
>> header files for both should be the same and not depend on _REENTRANT.

> I think I agree.  Could someone propose a wording change to Policy to say
> what we really mean here rather than focusing on _REENTRANT?

Here's an attempt at that.  I'm not sure if this says everything that
needs to be said, but I'm not sure what else to say.

I considered saying, as Kurt does above, that two libraries could be
provided, one with thread support and one without, but this poses some
serious problems because both libraries could be loaded into the same
process space and then conflict.  Doing this properly requires symbol
versioning or some other similar mechanism, and at that point I think
we're getting into something that's too difficult and specific to describe
in Policy.  I think I'd rather just let the "should" rather than "must"
provide wiggle-room for that.

Objections or seconds?

diff --git a/policy.sgml b/policy.sgml
index bad28af..1ffe148 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7225,10 +7225,10 @@ INSTALL = install -s # (or use strip on the files in 
debian/tmp)
   for C files) will need to be compiled twice, for the normal
   case. 
 
+

- You must specify the gcc option -D_REENTRANT
- when building a library (either static or shared) to make
- the library compatible with LinuxThreads.
+ Libraries should be built with threading support and to be
+ thread-safe if the library supports this.

 
 

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#564989: Patch fixing freetype's FTBFS with GCC 4.5

[brian m. carlson]

tags 564989 patch
kthxbye

Attached is a patch (which should be added to debian/patches-ft2demos)
that fixes the FTBFS with GCC 4.5.  GCC 4.5 with -Wall enabled complains
about switch statements over enumerated types when there are case values
that are not specified in the enumerated type.  -Werror makes this an
error.

Because the use of grKEY is so embedded in this code, I did not try to
remove it.  I simply made grKey a typedef to int instead of a typedef to
enumerated type.  There are, of course, other ways to solve this, such
as not using -Werror.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
--- ft2demos-2.3.11.orig/graph/grevents.h	2010-07-03 19:09:23.0 +
+++ ft2demos-2.3.11/graph/grevents.h	2010-07-03 19:09:31.0 +
@@ -22,7 +22,7 @@
 #define gr_event_type  (gr_event_mouse | gr_event_key)
 
 
-  typedef enum grKey_
+  enum grKey_
   {
 grKeyNone = 0,
 
@@ -60,7 +60,8 @@
 grKeyForceShort = 0x7FFF  /* this forces the grKey to be stored */
   /* on at least one short !*/
 
-  } grKey;
+  };
+  typedef int grKey;
 
 #define  grKEY(c)((grKey)(c))
 


signature.asc
Description: Digital signature

Bug#587999: Xv switches pixel columns

[Ulrich Eckhardt]

Package: xserver-xorg
Version: 1:7.5+6

Using mplayer and xine (didn't try others) with Xv as video output driver, I 
have the effect that the order of pixel columns is switched. If I use 24 bits 
color depth, the order is 1,0,3,2 etc. Using 16 bits color depth, the order is 
3,2,1,0,7,6,5,4.

Notes:
 * I'm using the radeon driver backend.
 * I'm on a big-endian machine (PPC).

As a workaround, I can use xshm as video output driver.

Cheers!

Uli



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#556015: Clarify requirements for copyright file

[Russ Allbery]

I think there was general consensus on the basic idea of the earlier
version of this patch, but Steve Langasek questioned the need for a
/usr/share/doc symlink to be supported by a direct dependency, as opposed
to an indirect dependency.  This version of the patch relaxes that and
allows the dependency to be indirect, provided that all the packages
involved are built from the same source package.  I believe this means we
will not be imposing any new requirements in this area than what Policy
had already required, but we'll be stating them more clearly.

Here's a revised version of the patch.  Objections or seconds?

diff --git a/policy.sgml b/policy.sgml
index bad28af..fb8468a 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -573,10 +573,14 @@
Copyright considerations
 

- Every package must be accompanied by a verbatim copy of its
+ Every binary package must include a verbatim copy of its
  copyright information and distribution license in the file
- /usr/share/doc/package/copyright
- (see  for further details).
+ /usr/share/doc/package/copyright or
+ symlink the /usr/share/doc/package directory to
+ a package that does (see  for further
+ details).  Every source package must include a verbatim copy of
+ its copyright information and distribution license in the file
+ debian/copyright (see ).

 

@@ -1679,12 +1683,11 @@
   
Copyright: debian/copyright
 
- Every package must be accompanied by a verbatim copy of its
- copyright information and distribution license in the file
- /usr/share/doc/package/copyright
- (see  for further details). Also see
-  for further considerations related
- to copyrights for packages.
+ Every source package must include a verbatim copy of
+ its copyright information and distribution license in the file
+ debian/copyright (see  for
+ further details).  Also see  for further
+ considerations related to copyrights for packages.
 
   
   
@@ -9212,7 +9215,7 @@ END-INFO-DIR-ENTRY

   
 
-  
+  
Additional documentation
 

@@ -9314,39 +9317,88 @@ END-INFO-DIR-ENTRY
Copyright information
 

- Every package must be accompanied by a verbatim copy of its
+ Every binary package must either include a verbatim copy of its
  copyright information and distribution license in the file
- /usr/share/doc/package/copyright. This
- file must neither be compressed nor be a symbolic link.
+ /usr/share/doc/package/copyright or must
+ include a symlink
+ named /usr/share/doc/package that points
+ to the /usr/share/doc directory of another package
+ that includes the copyright file.
+   The perl-base and perl
+   packages do not meet these requirements.
+   perl-base contains the copyright file for
+   both packages in the location appropriate for
+   the perl, and perl does
+   not include either a symlink or a copyright file.  Fixing this
+   would be complex and result in potentially fragile upgrades,
+   in part because perl-base is essential.
+   This is therefore permitted as a special exception.  Other
+   packages do not have the added complexity of being essential
+   and do not get the same exception.
+ 
+ The second option may only be used if all of the following
+ requirements are met:
+ 
+   
+ All the requirements for using a symlink instead of a
+ directory as /usr/share/doc/package
+ described in  must be met.  This means
+ both packages must come from the same source package and the
+ package must depend on the package containing its copyright
+ and distribution license.
+   
+
+   
+ The dependency on the package containing the copyright
+ information and distribution license must be strong
+ (Depends or Pre-Depends).  This dependency
+ may be indirect through other packages (for example,
+ packages A and B may have symlinks pointing to package C
+ with A depending on B and B depending on C), but only if all
+ packages involved in the dependency chain are built from the
+ same source package.
+   
+
+   
+ The /usr/share/doc/package/copyright
+ file contained in the other package must contain the
+ copyright information and distribution license for both
+ packages.
+   
+
+   
+ The copyright file contained in the other package must meet
+ all of the requirements listed below.
+   
+ 

 

Bug#586387: chromium-browser: Lots of UI crashes and weirdness

[Jonathan Nieder]

forwarded 586387 http://crbug.com/48259
quit

Joe Neal wrote:

> Sorry, Just saw this.

No problem.

>>> Sometimes a tab will freeze and become unresponsive and unclosable
[...]
> I also want to add that sometimes when a tab is frozen and I try to go 
> backwards in it, it will stay frozen but open a new tab with the last page in 
> the browser history in it.  If I hit back two or three times in succession it 
> will open two or three new tabs.
[...]
> Other X aps work when I can alt-tab to them but their window manger buttons 
> don't always work.  Nothing Plasma related seems to work, pretty much.   The 
> WM goes wonky using other DEs and WMs so I know it's not a KDE problem 
> though. 
[...]
> Alt-tab works, switching to the console works. Looking top or htop from the 
> console dosn't show any odd processes stuck running in the background or 
> anything like that. 

Thanks; this should be useful information when trying to narrow it down.

> On Monday, June 28, 2010 11:10:11 am you wrote:

>> If you can reproduce this, could you install
>> chromium-browser-dbg and try attaching to the various running chromium
>> processes and getting backtraces from them?
[...]
>
> I'll see what I can come up with

Awesome.

> I don't have an account but I can create one if it looks like debugging this 
> is going to take a while.

I’ve taken the liberty of submitting the issue as .

> I'm not much of a coder but I have been using linux 
> sine when you had to install slackware off floppies so I can probably help 
> figure 
> this out with a little bit of hand holding. 

Can’t ask for much more than that. :)

> In case it's related, I've also been having trouble with what I think is this 
> X bug:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575053

Yikes.  Hopefully not related.

Regards,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587998: edos-distcheck: Please support architecture wildcards

[Roger Leigh]

Package: edos-distcheck
Version: 1.4.2-11
Severity: important

Dear edos-distcheck maintainers,

edos-debcheck is used by the Debian wanna-build database, used
by the build dæmons to check which packages need rebuilding.
However, it appears that edos-debcheck can't yet cope with
architecture wildcards which are now permitted in package
dependencies and build-dependencies and are supported by
dpkg, sbuild and associated tools.  [I didn't see any use of
dpkg-architecture in the sources.]

Please could you consider adding support for architecture
wildcards with dpkg-architecture?  edos-debcheck support is the
last remaining tool needing support, which is blocking use of
wildcards in Debian.

References:
http://lists.debian.org/debian-wb-team/2010/07/msg7.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501230

Support is very simple.  When you get an architecture in
square brackets in a dependency such as

  grub [i386]
  libfreeimage-dev [!linux-any]
  libpng12-dev [any-i386]

you call dpkg-architecture to query if the wildcard matches
the host architecture.  You need to handle the '!' (not) case
yourself.  If the host architecture and dependency architecture
are a straight match, you can skip calling dpkg-architecture if you
want a small optimisation, or else you just ask dpkg-architecture:

Is [linux-any] needed on an amd64 arch?
% dpkg-architecture -aamd64 -ilinux-any 
% echo $?
0
(yes, it matches)

Is [linux-any] needed on a hurd-i386 arch?
% dpkg-architecture -ahurd-i386 -ilinux-any
% echo $?  
1
(no, it doesn't match)

Is [any-i386] needed on a hurd-i386 arch?
% dpkg-architecture -ahurd-i386 '-iany-i386' 
% echo $?   
0
(yes, it matches)

I'm sure you get the idea!

The list thread link above has the patch written for wanna-build
in it which might be useful as an example of how it could be done.


Many thanks,
Roger Leigh

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587997: Fails to run on mipsel

[Matt Kraai]

Package: pytrainer
Tags: patch

Hi,

I backported pytrainer 1.7.2-1 to lenny and tried to run it on a
mipsel machine, but it failed to run with the following error:

 Unsupported sys.platform: linux2-mipsel.

The attached patch fixed this problem.

-- 
Matt  http://ftbfs.org/kraai
--- pytrainer-1.7.2.orig/pytrainer/lib/system.py
+++ pytrainer-1.7.2/pytrainer/lib/system.py
@@ -37,7 +37,7 @@
 		self._setGpxDir()
 
 	def _setHome(self):
-		if sys.platform == "linux2":
+		if sys.platform.startswith("linux2"):
 			variable = 'HOME'
 		elif sys.platform == "win32":
 			variable = 'USERPROFILE'
@@ -67,7 +67,7 @@
 	def _setConfFiles(self):
 		if sys.platform == "win32":
 			self.confdir = self.home+"/pytrainer"
-		elif sys.platform == "linux2":
+		elif sys.platform.startswith("linux2"):
 			self.confdir = self.home+"/.pytrainer"
 		else:
 			print "Unsupported sys.platform: %s." % sys.platform

Bug#509932: shlibs format only addresses one versioning structure

[Russ Allbery]

Steve Langasek  writes:
> On Thu, Jul 01, 2010 at 12:15:38PM -0700, Russ Allbery wrote:
>> diff --git a/policy.sgml b/policy.sgml
>> index 1e641e6..9a72be5 100644
>> --- a/policy.sgml
>> +++ b/policy.sgml
>> @@ -5470,8 +5470,13 @@ Replaces: mail-transport-agent
>>debian/shlibs.local
>>  
>>
>> -This lists overrides for this package.  Its use is
>> -described below (see ).
>> +This lists overrides for this package.  This file should
>> +normally not be used, but may be needed temporarily in
>> +unusual situations to work around bugs in other packages,
>> +or in unusual cases where the normally declared dependency
>> +information in the installed shlibs file for
>> +a library cannot be used.  The contents of this file
>> +override information obtained from any other source.
>>
>>  

> I think the last sentence could use some tweaking - the first time through I
> didn't even parse it as a sentence.  Perhaps:

>This file overrides information obtained from any other source

> ?

Thanks, modified.

> As a side note, I think it would be good to have a longer minimum
> comment period on substantive policy changes.  Two days from patch
> proposal to merge is long enough to get the requisite seconds, but I
> don't think it's long enough to establish that those seconds are a
> consensus, or to allow good counterproposals / objections.  I understand
> you're working through a backlog and heartily appreciate your efforts,
> but there have been a couple patches I've seen go by recently with
> wording I thought could have been improved that were committed before I
> had a chance to react :)

I can let them sit for longer, but first, let me explain the theory and
see if that helps.  My feeling on the wording changes is that since
informative changes can be made without seconds, it's easy enough to make
those changes when people raise them later, even if I've already merged
the initial patch.  Also, since the only point at which we've really
committed to something is with the upload, if someone disagrees entirely
we can always reopen it and pull the patch while the discussion continues.

I can let things sit longer before merging and still work through the
backlog, though.  It just increases the number of things that are in
motion at the same time, and we have fairly good ways of tracking that.

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#587084: Appears to be a Problem with MySQL

[Soren Stoutner]

This bug report indicated that this is a problem with MySQL:

http://gallery.menalto.com/node/95444

An update to MySQL fixed the problem for a user running Fedora Core 12.  
However, it isn't readily apparent what was causing the problem in MySQL and 
if it can be easily integrated into Debian.

Gallery 3 should be available soon.  Perhaps I will just wait for that.

Soren


signature.asc
Description: This is a digitally signed message part.

Bug#586621: grub-pc bug #586621: not fixed yet

[Julien Plissonneau Duquène]

grub-setup still failing as of 1.98+20100702-1:
Setting up grub-pc (1.98+20100702-1) ...
Replacing config file /etc/default/grub with new version
/usr/sbin/grub-setup: warn: Attempting to install GRUB to a partition
instead of the MBR.  This is a BAD idea..
/usr/sbin/grub-setup: warn: Embedding is not possible.  GRUB can only be
installed in this setup by using blocklists.  However, blocklists are
UNRELIABLE and their use is discouraged..
/usr/sbin/grub-setup: error: cannot read `/boot/grub/core.img' correctly.
Generating grub.cfg ...

Workaround unchanged:
echo -en '(,msdos2)/boot/grub' | dd of=/boot/grub/core.img bs=1 seek=540
conv=notrunc
grub-setup --verbose --force /dev/sda2

-- 
Julien Plissonneau Duquène




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#509932: shlibs format only addresses one versioning structure

[Steve Langasek]

On Thu, Jul 01, 2010 at 12:15:38PM -0700, Russ Allbery wrote:
> diff --git a/policy.sgml b/policy.sgml
> index 1e641e6..9a72be5 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -5470,8 +5470,13 @@ Replaces: mail-transport-agent
> debian/shlibs.local
>  
> 
> - This lists overrides for this package.  Its use is
> - described below (see ).
> + This lists overrides for this package.  This file should
> + normally not be used, but may be needed temporarily in
> + unusual situations to work around bugs in other packages,
> + or in unusual cases where the normally declared dependency
> + information in the installed shlibs file for
> + a library cannot be used.  The contents of this file
> + override information obtained from any other source.
> 
>   
>  

I think the last sentence could use some tweaking - the first time through I
didn't even parse it as a sentence.  Perhaps:

   This file overrides information obtained from any other source

?

As a side note, I think it would be good to have a longer minimum comment
period on substantive policy changes.  Two days from patch proposal to merge
is long enough to get the requisite seconds, but I don't think it's long
enough to establish that those seconds are a consensus, or to allow good
counterproposals / objections.  I understand you're working through a
backlog and heartily appreciate your efforts, but there have been a couple
patches I've seen go by recently with wording I thought could have been
improved that were committed before I had a chance to react :)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature