Bug#382602: Breaks Root-on-RAID when /boot != /root)

[maximilian attems]

On Sat, Aug 12, 2006 at 02:43:00AM -0400, Daniel Dickinson wrote:
> 
> Upgrading initramfs (when package in testing changed) resulted in
> non-booting system.  I managed to fix things by adding a script to
> init-premount that activates (mdam -assemble's) the raid5 device
> (/dev/md1) that contains my root filessystem.  This probably won't
> occur on systems where /boot is on the root filesystem because (AIUI)
> the boot raid device is automagically activated.
> 
> The reason that the root device isn't activated by mdadm in local-top
> is that it is trying to use /etc/mdadm.conf which it doesn't find.
> (I don't know if /etc/mdadm/mdadm.conf is what it's trying to use, or
> if it is supposed to copy that file to /etc in the initramfs file).

urgs yes there is a typo in scripts/local-top/mdraid,
needs to use /conf/mdadm.conf that is created by mkinitramfs,
instead of /etc/mdadm.conf.

please post which mdadm version you are using?
dpkg -l mdadm
also please post the output of 
mdadm --examine --scan


 
> The script I added is (less the  tags):

looks sane and nice quick workaround.
 
thanks for report!

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382603: totem-mozilla: mozilla plugin complains about missing fd://0

[Martin Waitz]

Package: totem-mozilla
Version: 1.4.4-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

hoi :)

It seems that totem gets the video stream via stdin when used as
mozilla plugin, but it does not understand the URL "fd://0" which is
passed to it.

This error happens when trying to view the videos from
http://tagesschau.de (selecting video in windows media format).

- -- System Information:
Debian Release: testing/unstable
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-2-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages totem-mozilla depends on:
ii  dbus  0.62-4 simple interprocess messaging syst
ii  totem-gstreamer   1.4.4-1A simple media player for the Gnom

Versions of packages totem-mozilla recommends:
ii  epiphany-browser [www 2.14.3-1   Intuitive GNOME web browser
ii  firefox [www-browser] 1.5.dfsg+1.5.0.6-1 lightweight web browser based on M
ii  lynx [www-browser]2.8.5-2sarge2  Text-mode WWW Browser
ii  mozilla-browser [www- 2:1.7.13-0.2   The Mozilla Internet application s

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE271hj/Eaxd/oD7IRAi8KAJ9rwltisgX2u8ZhhPC5reBEb39E5gCfYbr3
KOA0mbxuTiCtGpV2DxWouQ8=
=lF8L
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#379728: slapd: the bug is still there

[Christoph Kaminski]

Package: slapd
Version: 2.3.24-1
Followup-For: Bug #379728

Setting up libldap-2.3-0 (2.3.25-1) ...

Setting up ldap-utils (2.3.25-1) ...
Setting up slapd (2.3.25-1) ...
Installing new version of config file /etc/default/slapd ...
Installing new version of config file /etc/init.d/slapd ...
dpkg: error processing slapd (--configure):
 subprocess post-installation script killed by signal (Interrupt)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)

Versions of packages slapd depends on:
ii  coreutils [fileutils]   5.97-4   The GNU core utilities
ii  debconf [debconf-2.0]   1.5.3Debian configuration management sy
ii  libc6   2.3.6-19 GNU C Library: Shared libraries
ii  libdb4.24.2.52+dfsg-1Berkeley v4.2 Database Libraries [
ii  libiodbc2   3.52.4-3 iODBC Driver Manager
ii  libldap-2.3-0   2.3.24-1 OpenLDAP libraries
ii  libltdl31.6-0+1.5a-4 A system independent dlopen wrappe
ii  libperl5.8  5.8.8-6.1Shared Perl library
ii  libsasl22.1.19.dfsg1-0.2 Authentication abstraction library
ii  libslp1 1.2.1-5  OpenSLP libraries
ii  libssl0.9.8 0.9.8b-3 SSL shared libraries
ii  libwrap07.6.dbs-9Wietse Venema's TCP wrappers libra
ii  perl [libmime-base64-pe 5.8.8-6.1Larry Wall's Practical Extraction 
ii  psmisc  22.3-1   Utilities that use the proc filesy

Versions of packages slapd recommends:
ii  db4.2-util  4.2.52+dfsg-1Berkeley v4.2 Database Utilities
ii  libsasl2-modules2.1.19.dfsg1-0.2 Pluggable Authentication Modules f

-- debconf information:
* slapd/password2: (password omitted)
  slapd/internal/adminpw: (password omitted)
* slapd/password1: (password omitted)
  slapd/fix_directory: true
* shared/organization: chaos
  slapd/upgrade_slapcat_failure:
* slapd/backend: BDB
* slapd/allow_ldap_v2: true
* slapd/no_configuration: false
* slapd/move_old_database: true
  slapd/suffix_change: false
  slapd/slave_databases_require_updateref:
* slapd/dump_database_destdir: /var/backups/slapd-VERSION
  slapd/autoconf_modules: true
* slapd/domain: chaos
  slapd/password_mismatch:
  slapd/invalid_config: true
  slapd/upgrade_slapadd_failure:
* slapd/dump_database: always
  slapd/migrate_ldbm_to_bdb: false
* slapd/purge_database: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#381844: itramfs-tools doesn't produce working ramdisk on amd64 with MODULES=list

[maximilian attems]

On Fri, 11 Aug 2006, Ivan Sergio Borgonovo wrote:

> > yes please use MODULES=most
> 
> I did it, both initrd didn't work.
> The "most" one was twice as large as the "list" ones (the working and
> the not working one), but this didn't help it to work.
> Summary:
> 
> a) 1 "list" initrd generated before last initramfs-tools that is *working* 
> ~300Kb
> 
> b) 1 "list" initrd generated after last initramfs-tools that is *not working* 
> ~360Kb
> 
> c) 1 "most" initrd generated after last initramfs-tools that is *not working* 
> ~600Kb

i'd like to see that initrd, please put it up somewhere on the web,
or send it me privately.
 
> a) and b) were generated with the *same* /etc/initramfs-tools/modules

hmm you didn't share yet the content of /etc/initramfs-tools/modules ??
 
> BTW I used this syntax:
> mkinitramfs -o /root/initrd.img-2.6.17-1-amd64-k8-smp-most
> -r /dev/md3 2.6.17-1-amd64-k8-smp

the root hardcoding shouldn't be necassary, checkout to pass the
right grub root param.

recommended way is:
update-initramfs -u -k 2.6.17-1-amd64-k8-smp

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#357996: Need help?

[Margarita Manterola]

Hi!

It's been more than a month since you promised to work on tulip's new
upstream release.

Are you going to be able to package it soon?  Do you need help with doing
this?  

-- 
Love,
Marga


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382604: zaptel: fails by post-install

[Christoph Kaminski]

Package: zaptel
Version: 1:1.2.7.dfsg-3
Severity: grave
Justification: renders package unusable

I cant install it :(

apt-get install zaptel
Reading package lists... Done
Building dependency tree... Done
zaptel is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up zaptel (1.2.7.dfsg-3) ...
Zaptel cards initial configuration: ZT_SPANCONFIG failed on span 1: Invalid 
argument (22)
invoke-rc.d: initscript zaptel, action "start" failed.
dpkg: error processing zaptel (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 zaptel
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)

Versions of packages zaptel depends on:
ii  fxload0.0.20020411-1 Firmware download to EZ-USB device
ii  libc6 2.3.6-19   GNU C Library: Shared libraries
ii  libnewt0.52   0.52.2-7   Not Erik's Windowing Toolkit - tex
ii  libusb-0.1-4  2:0.1.12-2 userspace USB programming library
ii  procps1:3.2.7-3  /proc file system utilities

zaptel recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#381315: initramfs-tools: install /usr/share/initramfs-tools/conf.d/* into initramfs image

[maximilian attems]

tags 381315 pending
stop

On Thu, 03 Aug 2006, Vagrant Cascadian wrote:

> Package: initramfs-tools
> Version: 0.73
> Severity: normal
> Tags: patch
> 
> it seems that initramfs-tools includes the
> /usr/share/initramfs-tools/conf.d snippets at build time, but does not
> install them into the initramfs image.

i agree that your patch makes a lot of sense from consistency reasons!

but i thought of /usr/share/initramfs-tools/conf.d, to change the
mkinitramfs building and not the boot, behaviour. like overriding
BUSYBOX=no in /etc/initramfs-tools/initramfs.conf due to
/usr/share/initramfs-tools/conf.d/lvm2 with BUSYBOX=yes

btw a quick scan shows that the conf.d usage is not yet documented,
but you are right the intention was for boottime RESUME setting.

so i'll apply your patch and will think of another location for
the mkinitramfs build tuning.
 
> attached patch is revision 198 from:
> 

thanks.

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382609: ifupdown fails to bring up hotplug discovered interfaces if hard disks do fsck on boot

[Alan Chandler]

Package: ifupdown
Version: 0.6.7
Severity: important

If my computer fails for any reason and I have to reboot without having
shutdown properly then upon restart the start up scripts have to run fsck
on all the disks.

In this instance, ifupdown fails to bring up all the interfaces, so that
once the reboot is complete the computer is isolated from the network.
Rebooting again, with a proper shutdown then allows all network interfaces
to be brought up properly.

It appears to be the interfaces being controlled via hotplug that are the
problem.  In my case eth0 is the device that fails to come up, although the
device eth0 certainly exists after boot (ifconfig eth0 lists the
characteristics)

I am not really sure why this is the case, and some little exploration has
not shown where the problem is.  So I am raising this bug against the
ifupdown package, but I am not sure that is necessarily the correct place.



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages ifupdown depends on:
ii  debconf [debconf-2.0] 1.5.3  Debian configuration management sy
ii  libc6 2.3.6-18   GNU C Library: Shared libraries
ii  net-tools 1.60-17The NET-3 networking toolkit

ifupdown recommends no packages.

-- debconf information:
  ifupdown/convert-interfaces: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#374610: msmtp: TLS handshake failed: A TLS fatal alert has been received.

[Martin Lambers]

On Sun, 16. Jul 2006, 21:24:56 +0200, Martin Lambers wrote:
> I finally found the time to write a patch that adds a tls_sslv3only
> command (and --tls-sslv3only option).
> 
> Do you agree with the patch? Any suggestions for improvements?

Is there still interest in this problem and in the patch?
I will prepare a new release soon and would like to know if I should
include this patch (or a similar one).

Regards,
Martin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382607: CVE-2006-4041: Pike Unspecified SQL Injection Vulnerability

[Stefan Fritsch]

package: pike7.2
version: 7.2.580-3.1
severity: grave
tags: security

A vulnerability has been found in pike which is also present in sarge.
See
http://secunia.com/advisories/20494/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382608: ppp: On 2.6.17 kernel, chat fails with "Can't get terminal parameters" error

[Vincent Lefevre]

Package: ppp
Version: 2.4.4rel-2
Severity: important

With a 2.6.17 kernel (official binary package from Debian), I get
the error in /var/log/syslog:

Aug 12 09:17:59 ay pppd[30971]: pppd 2.4.4 started by root, uid 0
Aug 12 09:18:00 ay chat[30972]: Can't get terminal parameters: Input/output 
error
Aug 12 09:18:00 ay pppd[30971]: Connect script failed
Aug 12 09:18:01 ay pppd[30971]: Exit.

and can't use ppp. No problem with a 2.6.12 kernel I had compiled.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (200, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-20050829
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages ppp depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libpam-modules0.79-3.1   Pluggable Authentication Modules f
ii  libpam-runtime0.79-3.1   Runtime support for the PAM librar
ii  libpam0g  0.79-3.1   Pluggable Authentication Modules l
ii  libpcap0.80.9.4-2System interface for user-level pa
ii  netbase   4.25   Basic TCP/IP networking system
ii  procps1:3.2.7-2  /proc file system utilities
ii  zlib1g1:1.2.3-13 compression library - runtime

ppp recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382605: partman-crypto not entirely localized

[Miroslav Kure]

Package: partman-crypto
Severity: minor
Tags: l10n, patch

Hi,

the template partman-crypto/text/erase_data (_Description: Erase data:)
does not have its choices (yes/no) localizable. Please apply something
like the attached (untested) patch.

-- 
Miroslav Kure
Index: debian/partman-crypto.templates
===
--- debian/partman-crypto.templates (revision 39735)
+++ debian/partman-crypto.templates (working copy)
@@ -112,6 +112,14 @@
 # by "yes" or "no"
 _Description: Erase data:
 
+Template: partman-crypto/text/erase_data
+Type: text
+_Description: yes
+
+Template: partman-crypto/text/dont_erase_data
+Type: text
+_Description: no
+
 Template: partman-crypto/text/erase_data_partition
 Type: text
 _Description: Erase data on this partition
Index: active_partition/erase/choices
===
--- active_partition/erase/choices  (revision 39735)
+++ active_partition/erase/choices  (working copy)
@@ -12,11 +12,19 @@
 
 choice_erase () {
if [ -f $part/skip_erase ]; then
-   #db_metaget partman-crypto/text/erase_data description
-   erase="no"
+   db_metaget partman-crypto/text/erase_data description || RET=''
+   if [ "$RET" ]; then
+   erase="$RET"
+   else
+   erase="no"
+   fi
else
-   #db_metaget partman-crypto/text/dont_erase_data description
-   erase="yes"
+   db_metaget partman-crypto/text/dont_erase_data description || 
RET=''
+   if [ "$RET" ]; then
+   erase="$RET"
+   else
+   erase="yes"
+   fi
fi
 
db_metaget partman-crypto/text/erase_data description

Bug#279168: closed by Chris Lawrence <[EMAIL PROTECTED]> (Fixed)

[Albert Cahalan]

From: Chris Lawrence <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Fri, 11 Aug 2006 18:13:47 -0500
Subject: Fixed
According to the original submitter, this bug is fixed.


No way. I'm the original submitter, and I certainly
said nothing about the bug being fixed. Unless you've
done something to verify that the mail goes through,
the bug is certainly not fixed.

There are several ways to fix this:

a. poll the bugs.debian.org web site.
b. do a direct SMTP connection yourself
c. do some other protocol, like FTP or HTTP
d. write a custom protocol for the job

Until you get back a positive response from the
Debian server, you have no idea what happened.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382611: cloop-utils: "One of: -s, -m, -f or -r required. Exiting..." in spite of "-m".

[Andreas Krüger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: cloop-utils
Version: 2.04-1+eb.1-5
Severity: normal

*** Please type your report below this line ***
I have issued the following command:

create_compressed_fs -m -v -L -1 -B 65536 - -

As a result, I get

ERROR:
Unknown input data size and no tempdata storage strategy has been
choosen.
One of: -s, -m, -f or -r required. Exiting...

Clearly, I *have* issued "-m". So that message is less helpful than it
could be. The manual page does not really tell me what is wrong about my
option usage, either. (I understand that -m is no longer recommended, but
the docs do not tell me that it has been outright disallowed.)

Regards, and thank you for providing fine software

Andreas

- -- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
(charmap=ISO-8859-15)

Versions of packages cloop-utils depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libgcc1   1:4.1.1-5  GCC support library
ii  libstdc++64.1.1-5The GNU Standard C++ Library v3
ii  zlib1g1:1.2.3-13 compression library - runtime

cloop-utils recommends no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFE3Y+CnWrlKaIH40ARAovMAJ94BehOjNNq8fPibfptP9BrxVcBfwCghBrn
SxSNCl7FKpacNzSltl3hHDI=
=SUkq
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382610: module-assistant: Please document that prepare installs build-essential in manpage

[Filipus Klutiero]

Package: module-assistant
Version: 0.10.6
Severity: wishlist

m-a prepare now installs b-e, which surprised me a bit before I looked
at the changelog. Please document this in the manpage.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#374610: msmtp: TLS handshake failed: A TLS fatal alert has been received.

[Julien Louis]

On Sat, Aug 12, 2006 at 09:55:20AM +0200, Martin Lambers wrote:
> 
> Is there still interest in this problem and in the patch?
> I will prepare a new release soon and would like to know if I should
> include this patch (or a similar one).

Well, i didn't have the time to test the patch, i'll try to test it this weekend


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382612: bzr: '~' in Version number violates policy 5.6.12

[Jakob Bohm]

Package: bzr
Version: 0.9~rc1-1
Severity: serious
Justification: Policy 5.6.12

Policy section 5.6.12 lists the permitted characters in package
version numbers, '~' is NOT on the list, and until less than 14
days ago all packages in the archive were compliant with that
rule.  I know for certain that one of my own mirroring scripts
will refuse to accept '~' in package file names, and others
might do the same.

As explained in policy section 5.6.12, if the upstream version
number does not match the format and semantics specified in
section 5.6.12, the maintainer should reformat the version
number in his upload.

Sincerely

Jakob

Footnote: The actual wording in policy 5.6.12 does not use the
standard phrases specified in policy 1.1, making it difficult to
infer if violation of the specified format should be classified
as serious, normal or wishlist.  Based on the nature of the
information, its citing in the first footnote of policy 1.1 and
the general structure of the English language, I interpret "may
only" as a must requirement not to do something else.  In other
words, it is entirely optional for a version number to contain
the character '+' ("may contain only ... '+'"), but it is
required not to use any characters not enumerated there.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (450, 'unstable'), (400, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /basnxt/bin/bash
Kernel: Linux 2.6.17jbj3.4-16
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#328411: note

[Wouter Verhelst]

On Mon, Aug 07, 2006 at 07:40:54PM +0200, Steinar H. Gunderson wrote:
> On Mon, Aug 07, 2006 at 01:37:20PM -0400, Joey Hess wrote:
> > is one, it could be a possibility, except for systems that don't support
> > the ondemand governor.
> 
> Are there any such systems?

Yes. Ondemand only works if the CPU can change its policy reasonably
fast. On processors where this is not possible, you can load the module,
but trying to enable it ("echo -n 'ondemand' > scaling_governor") will
produce an error.

This is true for, e.g., my laptop (PowerPC G4, 8448A if I'm not mistaken
(it's in for repair currently))

-- 
Fun will now commence
  -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382296: So? Shall we wait until we break the world record of identical bug reports?

[Peter Eisentraut]

Christian Perrier wrote:
> Do we do it silently without prompting? This is, strictly speaking,
> non policy compliantbut who wants a package that will panic after
> an upgrade?

You might be thinking of conffiles, but smb.conf is not a conffile.

I propose the following patch:

Index: samba-common.postinst
===
--- samba-common.postinst   (Revision 1121)
+++ samba-common.postinst   (Arbeitskopie)
@@ -136,4 +136,8 @@

 db_stop

+if [ -n "$2" ] && dpkg --compare-versions "$2" lt 3.0.23b-2; then
+   sed -i -e 's/^\([[:space:]]*passdb backend = [[:alpha:]][[:alpha:]]*\) 
guest$/\1/' /etc/samba/smb.conf
+fi
+
 #DEBHELPER#

---

Btw., is there anything wrong with using "sed -i"?  The rest of the
postinst seems to go out of its way to handle sed with manual temp files.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#381677: initramfs-tools: Temporary files and initramfs world-readable

[maximilian attems]

On Sun, 06 Aug 2006, Lionel Elie Mamane wrote:

> The generated initramfs is world-readable (as well as the temporary
> files); this leaks cryptographic keys (in password-protected form) to
> all users on the system when the root fs is encrypted (because these
> keys then get copied to the initramfs, at least in the loop-aes
> case). See bug #378488 for a discussion of this in the context of
> loop-aes.

yaird installs initrd.img with 600 without giving any further
reasons -> see #336454
no reply from maintainer since bug is filed.

 
> This patch fixes that. As making these files running user only
> readable does not, as far as I can see, hurt even when not strictly
> necessary, the patch just does it unconditionnaly.
> 
> 
> Please apply (or comment). Thanks.

i'd have waited for someone else to voice there concerns.
i like the initramfs-tools initrd.img to be debuggable as
user (quick check of their contents).

also loop-aes is quite a specific use case,
so i'm not in big favour of setting the umask in general
to the proposed value as in general there is no gpg key
in the initramfs.

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#269329: I'd like to help

[mb]

Hi,

Not much happening with this package it seems.-

I'm an OX comercial partner and Java dev and would like to help with 
creating/maintaining this package. However, I don't have that much time to 
spare and this is my first try at getting involved with debian as a contributor.

So if there's something I can do to help, let me know - I'm getting sick of 
manually installing OX ;)

Regards, Martin
-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#381743: client-error-document-format-not-supported

[Pascal De Vuyst]

Can you give the output of the following commands:

$ grep -H "*NickName" /etc/cups/ppd/*.ppd
$ lpstat -v

$ ls -l /etc/cups/*.types /etc/cups/*.convs
$ cat /etc/cups/*.types /etc/cups/*.convs | grep "text/plain"
$ ls -l /usr/lib/cups/filter/texttops

$ grep -H "application/vnd.cups-raster" /etc/cups/*.types 
/etc/cups/*.convs | grep pstoraster

$ grep -H "application/vnd.cups-command" /etc/cups/*.types /etc/cups/*.convs

Regards,
Pascal


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#279168: closed by Chris Lawrence <[EMAIL PROTECTED]> (Fixed)

[Chris Lawrence]

On 8/12/06, Albert Cahalan <[EMAIL PROTECTED]> wrote:

> From: Chris Lawrence <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Fri, 11 Aug 2006 18:13:47 -0500
> Subject: Fixed
> According to the original submitter, this bug is fixed.

No way. I'm the original submitter, and I certainly
said nothing about the bug being fixed. Unless you've
done something to verify that the mail goes through,
the bug is certainly not fixed.


My apologies, I misread the report log (confusing someone who had a
very similar problem with you).


There are several ways to fix this:

a. poll the bugs.debian.org web site.
b. do a direct SMTP connection yourself
c. do some other protocol, like FTP or HTTP
d. write a custom protocol for the job

Until you get back a positive response from the
Debian server, you have no idea what happened.


a, c, and d are currently not supported by the Debbugs server (a is
plausible, but you would have to poll for at least 15 minutes as
debbugs does batch processing of the mail queue).  b is an option (you
can set smtphost to bugs.debian.org) but breaks cc's to others.

More to the point, this is a general issue with all MUAs that depend
on an MTA to accomplish delivery for them, and (IMHO) loading down
reportbug with functionality that is only necessary to diagnose
people's broken mail systems wouldn't be a very good tradeoff.

You may reopen the report, but it will probably be downgraded and
marked wontfix.


Chris
--
Chris Lawrence - http://blog.lordsutch.com/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#381481: aptitude: FTBFS: test failure

[Julien Danjou]

reassign 381481 xen-3.0
retitle 381481 pthread_cond_timedwait does not wait enough
severity 381481 important
thanks

On Fri, Aug 11, 2006 at 06:54:43AM -0700, Daniel Burrows wrote:
>   Ick, I didn't realize this was a virtual machine.

I did not say it, so you could not know ;)

> >| ..
> >| rval == -1080447064
> >| 
> >| now2.tv_sec == 1155053066
> >| now.tv_sec + 2 == 1155053066
> >| now2.tv_usec == 882203
> >| now.tv_usec == 887661
> >| F.
> 
>   Hm.  I'm inclined to close this as a bug in xen --
> pthread_cond_timedwait should never ever return success if it hasn't
> waited long enough, which is what appears to be happening. [0] Does xen
> play games with the system clock?

I really think so. Consequently, I reassign this bug to Xen.
And thanks for your good explanation!

Cheers,
-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature

Bug#382612: bzr: '~' in Version number violates policy 5.6.12

[Lars Wirzenius]

severity normal
thanks

la, 2006-08-12 kello 10:41 +0200, Jakob Bohm kirjoitti:
> Policy section 5.6.12 lists the permitted characters in package
> version numbers, '~' is NOT on the list, and until less than 14
> days ago all packages in the archive were compliant with that
> rule.  I know for certain that one of my own mirroring scripts
> will refuse to accept '~' in package file names, and others
> might do the same.

This is changing, see
http://lists.debian.org/debian-devel-announce/2006/08/msg6.html and
replies on debian-devel and debian-policy. Tilde is now de facto
allowed, and policy is going to be updated soon. When things affected by
policy change, it is common for policy updates to lag a bit, since the
policy is supposed to document existing practice. Before there is
existing practice, a policy change is (often) premature.

-- 
It's 1978! Things should be round by now -- Michael Kelso (That 70's
show)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382613: perl-ifeffit: long description not descriptive (and starts with a paragraph)

[Gerfried Fuchs]

Package: perl-ifeffit
Version: 1:1.2.9-1
Severity: minor

Hi!

 The long description isn't really helpful. For a start, it doesn't
describe what IFEFFIT means, and redirecting people to the homepage for
finding out about that shouldn't really be required. The package
description should be usable on its own.

 Furthermore the long description starts off with a paragraph. I'm not
sure if you forgot to copy parts from one of the other packages, or if
this is an accident, but it shouldn't really happen.

 So long,
Alfie
-- 
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.
-- Larry Wall


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#279168: closed by Chris Lawrence <[EMAIL PROTECTED]> (Fixed)

[Albert Cahalan]

On 8/12/06, Chris Lawrence <[EMAIL PROTECTED]> wrote:


More to the point, this is a general issue with all MUAs that depend
on an MTA to accomplish delivery for them, and (IMHO) loading down
reportbug with functionality that is only necessary to diagnose
people's broken mail systems wouldn't be a very good tradeoff.


So an MTA is not allowed to have a bug? :-)

Spam filters seem to eat half the legit email these days.
There might be several on the path to bugs.debian.org.

Supposing that the MTA is indeed misconfigured by the
user's own action (can not blame Debian config), so what?
It's still important to deliver the bug report. There is no
need for reportbug to diagnose broken mail systems; there
is only a need to deliver the bug report if at all possible
and ensure that silent failure can never happen. Feel free
to tell the user "It looks like the email was eaten by a grue."
before offering to try some other method.


You may reopen the report, but it will probably be downgraded and
marked wontfix.


Please do reopen it.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#344072: apache2: Apache 2.2 has been released

[Stefan Fritsch]

On Tuesday 08 August 2006 08:06, Norbert Tretkowski wrote:
> could you please give us a status update about the apache 2.2
> packages?

Are there realistic chances to get 2.2 into etch? If yes, are 
preliminary packets available somewhere?
If no, we should go for 2.0.59. There have been quite a few 
(non-security) bugfixes since 2.0.55.

Cheers,
Stefan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#372505: In config file, browser= does nothing. BROWSER= does, however

[Pierre HABOUZIT]

On Fri, Aug 11, 2006 at 07:18:56PM -0400, Anthony DeRobertis wrote:
> Pierre HABOUZIT wrote:
> >   no it's not, I just tested, the right command is started, and if I
> > grep the entier source, i don't see a single reference to BROWSER.
> >
> >   please provide more informations.
> >
> >   
> Ummm, I sent the config in my bug report as well as the versions. I'm
> not sure what else to send...
> 
> [BTW: I won't be back in front of that machine until Monday, so I can't
> really test it until then]

  I mean, I've tested the config that was supposed to be buggy, and that
works for me.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


signature.asc
Description: Digital signature

Bug#382618: slat: FTBFS: error: 'perm_datum_t' has no member named 'value'

[Julien Danjou]

Package: slat
Version: 2.0-2
Severity: serious

Hello,

There was a problem while autobuilding your package:

> Automatic build of slat_2.0-2 on avidan by sbuild/i386 0.49
> Build started at 20060812-0518
> **
...
>   then mv -f ".deps/scanner.Tpo" ".deps/scanner.Po"; else rm -f 
> ".deps/scanner.Tpo"; exit 1; fi
> if cc -DPACKAGE_NAME=\"slat\" -DPACKAGE_TARNAME=\"slat\" 
> -DPACKAGE_VERSION=\"2.0\" -DPACKAGE_STRING=\"slat\ 2.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"slat\" -DVERSION=\"2.0\" 
> -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_SEPOL_POLICYDB_H=1 -DHAVE_POLICYDB_READ=1  -I. -I.-I../../include 
> -O2 -g -MT slat.o -MD -MP -MF ".deps/slat.Tpo" -c -o slat.o slat.c; \
>   then mv -f ".deps/slat.Tpo" ".deps/slat.Po"; else rm -f 
> ".deps/slat.Tpo"; exit 1; fi
> slat.c: In function 'security_contexts':
> slat.c:226: warning: passing argument 1 of 'role_set' from incompatible 
> pointer type
> slat.c:241: warning: passing argument 1 of 'type_set' from incompatible 
> pointer type
> slat.c: In function 'perm_flow_fun':
> slat.c:327: error: 'perm_datum_t' has no member named 'value'
> slat.c: In function 'flow_in_class':
> slat.c:373: error: 'common_datum_t' has no member named 'value'
> slat.c: In function 'constrain':
> slat.c:573: error: 'class_datum_t' has no member named 'value'
> slat.c: In function 'gencommap':
> slat.c:716: error: 'common_datum_t' has no member named 'value'
> slat.c: In function 'genclsmap':
> slat.c:734: error: 'class_datum_t' has no member named 'value'
> slat.c:739: error: 'common_datum_t' has no member named 'value'
> slat.c: In function 'initcom':
> slat.c:834: error: 'common_datum_t' has no member named 'value'
> slat.c: In function 'action':
> slat.c:904: error: 'common_datum_t' has no member named 'value'
> slat.c:918: error: 'class_datum_t' has no member named 'value'
> slat.c:923: error: 'common_datum_t' has no member named 'value'
> slat.c:925: error: 'common_datum_t' has no member named 'value'
> make[4]: *** [slat.o] Error 1
> make[4]: Leaving directory `/build/buildd/slat-2.0/src/slat'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/build/buildd/slat-2.0/src/slat'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/slat-2.0/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/build/buildd/slat-2.0'
> make: *** [build/slat] Error 2
> **
> Build finished at 20060812-0519
> FAILED [dpkg-buildpackage died]
> --

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature

Bug#382614: -M not documented

[Falk Hueffner]

Package: abcde
Version: 2.3.99.6-1
Severity: normal

The man page mentions the "-M" option, but doesn't document it.

Falk

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: alpha
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.5
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages abcde depends on:
ii  cd-discid 0.9-1  CDDB DiscID utility
ii  cdparanoia3a9.8-13   An audio extraction tool for sampl
ii  flac  1.1.2-5Free Lossless Audio Codec - comman
ii  vorbis-tools  1.1.1-6several Ogg Vorbis tools
ii  wget  1.10.2-1   retrieves files from the web

abcde recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#374610: msmtp: TLS handshake failed: A TLS fatal alert has been received.

[Julien Louis]

On Sat, Aug 12, 2006 at 10:30:26AM +0200, Julien Louis wrote:
> Well, i didn't have the time to test the patch, i'll try to test it this 
> weekend

I've just tested your patch and it works fine, i can get server infos when i run
msmtp -a testaccount -S.

-- 
I do desire we may be better strangers.
-- William Shakespeare, "As You Like It"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382615: xqf: little bug with ping return time

[michaelm]

Package: xqf
Version: 1.0.4-2
Severity: minor

that's a minor bug (more for upstream I guess). 

if the ping return time of a server is too high for some reason, say
half a second or more and i 'refresh' that server before the previous
return has come, it may show a very low ping time since it would
consider the time between the last request for refresh and the return of
the request before it.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=el_GR, LC_CTYPE=el_GR (charmap=ISO-8859-7)

Versions of packages xqf depends on:
ii  libatk1.0-0  1.12.1-1The ATK accessibility toolkit
ii  libc62.3.6-19GNU C Library: Shared libraries
ii  libcairo21.2.2-1 The Cairo 2D vector graphics libra
ii  libfontconfig1   2.3.2-7 generic font configuration library
ii  libgeoip11.3.17-1A non-DNS IP-to-country resolver l
ii  libglib2.0-0 2.10.3-3The GLib library of C routines
ii  libgtk2.0-0  2.8.18-7The GTK+ graphical user interface 
ii  libncurses5  5.5-2   Shared libraries for terminal hand
ii  libpango1.0-01.12.3-1+b1 Layout and rendering of internatio
ii  libreadline5 5.1-7   GNU readline and history libraries
ii  libx11-6 2:1.0.0-8   X11 client-side library
ii  libxcursor1  1.1.5.2-5   X cursor management library
ii  libxext6 1:1.0.0-4   X11 miscellaneous extension librar
ii  libxi6   1:1.0.0-5   X11 Input extension library
ii  libxinerama1 1:1.0.1-4   X11 Xinerama extension library
ii  libxrandr2   2:1.1.0.2-4 X11 RandR extension library
ii  libxrender1  1:0.9.0.2-4 X Rendering Extension client libra
ii  qstat2.10-1  Command-line tool for querying qua
ii  zlib1g   1:1.2.3-13  compression library - runtime

xqf recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382314: [pkg-wpa-devel] Bug#382314: Need to scramble wpa-psk? Apparently yes, but not obvious

[Kel Modderman]

Hi Eduard,

On Thursday 10 August 2006 18:46, Eduard Bloch wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> Hello,
>
> I was using previous versions of wpasupplicant (before ifupdown
> integration) with a self-made conf file containing a preshared key.
> Relevant contents:
>
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> network={
> ssid="secret"
> psk="longsecret"
> # long ascii psk copied from the windows client
> priority=5
> }
>
> That worked fine, wpa_supplicant was started manually and I had no
> complaints. But then came the ifupdownisation, I tried to follow
> README.Debian.gz and README.modes.gz and it still did not work. There
> was no usefull debug information in the logs either (as usual, sorry :-( ).
> Just the usual game "link, few lost pakets, link lost, multiple times".
>
> It was not obvious to me what was wrong. I integrated the values from
> the mentioned config file with "wpa-" prefixes in the interfaces file.
>
> Then I decided to play with the tools mentioned in README.modes.gz, I
> used wpa_passphrase, passed my essid and the old psk to it and it threw
> me some new key inside of a "config section". When I added this new key
> as wpa-psk in the interfaces file, it worked.

Your key is a plaintext passphrase; did you wrap it in quotes like:

wpa-psk "passphrase"

or use the special wpa-passphrase option:

wpa-passphrase passphrase

or did you do:

wpa-psk passphrase

?

>
> Honestly, WTF? What is the difference? Manpage of wpa_passphrase does
> not explain ANYTHING (like where and why I need to generate this key).
> It displays a config section which differs from my old one... why? The
> old one works when the config is supplied with -c configfile, why does
> the same passphrase not work as wpa-psk variable?
>
> I can only ASSUME that the programers decided to switch from a plaintext
> pass phrase to a scrambled form. But in this case, DOCUMENT THE CHANGE
> ON VISIBLE PLACES. Sorry, that's the minimum requirement for
> user-friendlines.


Please advise how we can help improve user friendliness without using 
provocative language. However, I can understand your frustration, I once had 
similar experiences with this very piece of software (and its lack of user 
friendliness).

I will do, to the best of my ability, what is required to enhance the 
user-friendliness quality of wpasupplicant, but first the problem areas need 
to be clearly identified. What specifically is required to satisfy your 
experiences with wpasupplicant?

Are you frustrated at our ifupdown.sh program and documentation? Or the 
upstream documentation? Or both?

Would you like us to better explain the purpose/advantage of generating a 
hexadecimal psk in our documentation? Would you like us to discuss this with 
upstream and make sure the upstream manpage/docs are more clear about why 
wpa_passphrase is useful?

Here is an extract from README.modes that attempts to explain the assumptions 
that our ifupdown.sh script makes:


Notes About Managed Mode

...
The wpasupplicant ifupdown script makes assumptions about the 'type' of input
that is valid for each option. For example, it assumes that some input is
plaintext and wraps quotation marks around the input before passing it on
to wpa_cli, which then adds the input to the network block being formed via
the wpa_supplicant ctrl_interface socket. This can be a point of confusion, 
and
something that has tricked more than a few people in the past. For example:

# Invalid, wpa-ssid expects unquoted plaintext ssid's only
# If you need to use a hexadecimal ssid, please supply a
# wpa_supplicant.conf, and use the 'wpa-conf' option.
wpa-ssid "hostpot12345678"

# Valid, unquoted plaintext string
wpa-ssid hostpot12345678

# Invalid, wpa-psk expects hexadecimal strings only
wpa-psk plaintextpassword

# NOTE: wpa-psk will accept a plaintext string enclosed in quotation
# marks this is equivalent to the 'wpa-passphrase' option
wpa-psk "plaintextpassword"

# Invalid, wpa-passphrase accepts only plaintext strings, as it
# automatically quotes the input
wpa-passphrase "invalidinput"

# Valid, unquoted plaintext string
wpa-passphrase validinput


Do we make poor assumptions? Are our assumptions not clear enough to 
understand?

Thanks, Kel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382617: samhain: FTBFS: multiple undefined references

[Julien Danjou]

Package: samhain
Version: 2.2.0-2
Severity: serious

Hello,

There was a problem while autobuilding your package:

> Automatic build of samhain_2.2.0-2 on avidan by sbuild/i386 0.49
> Build started at 20060812-0354
> **
...
> ./encode 0 ./src/sh_prelude_old.c --> x_sh_prelude_old.c
> ./encode 0 ./src/`echo sh_prelude_old.o |sed 's%\.o$%%'`.c
> echo "gcc  -DHAVE_CONFIG_H -I. -I./include   -O2 -fstack-protector -Wall -W  
> -fno-strength-reduce -fno-omit-frame-pointer -DSH_STANDALONE -o `echo 
> sh_prelude_old.o |sed 's%.*/%%'` -c x_`echo sh_prelude_old.o |sed 
> 's%\.o$%%'`.c"
> gcc  -DHAVE_CONFIG_H -I. -I./include   -O2 -fstack-protector -Wall -W  
> -fno-strength-reduce -fno-omit-frame-pointer -DSH_STANDALONE -o 
> sh_prelude_old.o -c x_sh_prelude_old.c
> gcc  -DHAVE_CONFIG_H -I. -I./include   -O2 -fstack-protector -Wall -W  
> -fno-strength-reduce -fno-omit-frame-pointer -DSH_STANDALONE -o `echo 
> sh_prelude_old.o |sed 's%.*/%%'` -c x_`echo sh_prelude_old.o |sed 
> 's%\.o$%%'`.c
> rm x_`echo sh_prelude_old.o |sed 's%\.o$%%'`.c
> gcc  -DHAVE_CONFIG_H -I. -I./include   -O2 -fstack-protector -Wall -W  
> -fno-strength-reduce -fno-omit-frame-pointer -DSH_STANDALONE -o sh_tiger_i.o 
> -c ./src/sh_tiger1.s
> gcc  -DHAVE_CONFIG_H -I. -I./include   -O2 -fstack-protector -Wall -W  
> -fno-strength-reduce -fno-omit-frame-pointer -DSH_STANDALONE -o sh_tiger_i.o 
> -c ./src/sh_tiger1.s
> gcc  -O  -o samhain sh_tiger_i.o sh_files.o sh_tiger0.o sh_tiger2.o 
> sh_tiger2_64.o samhain.o sh_unix.o sh_utils.o sh_error.o sh_getopt.o 
> sh_readconf.o sh_hash.o sh_mail.o sh_mem.o sh_entropy.o sh_forward.o 
> sh_modules.o sh_utmp.o sh_kern.o sh_suidchk.o sh_srp.o sh_fifo.o sh_tools.o 
> sh_html.o sh_gpg.o sh_cat.o sh_calls.o sh_extern.o sh_database.o sh_err_log.o 
> sh_err_console.o sh_err_syslog.o sh_schedule.o bignum.o trustfile.o 
> rijndael-alg-fst.o rijndael-api-fst.o slib.o zAVLTree.o sh_socket.o 
> sh_ignore.o sh_prelude.o sh_mounts.o sh_userfiles.o sh_prelink.o sh_static.o 
> sh_prelude_old.o  -lnsl  -lnsl -lresolv
> gcc  -O  -o samhain sh_tiger_i.o sh_files.o sh_tiger0.o sh_tiger2.o 
> sh_tiger2_64.o samhain.o sh_unix.o sh_utils.o sh_error.o sh_getopt.o 
> sh_readconf.o sh_hash.o sh_mail.o sh_mem.o sh_entropy.o sh_forward.o 
> sh_modules.o sh_utmp.o sh_kern.o sh_suidchk.o sh_srp.o sh_fifo.o sh_tools.o 
> sh_html.o sh_gpg.o sh_cat.o sh_calls.o sh_extern.o sh_database.o sh_err_log.o 
> sh_err_console.o sh_err_syslog.o sh_schedule.o bignum.o trustfile.o 
> rijndael-alg-fst.o rijndael-api-fst.o slib.o zAVLTree.o sh_socket.o 
> sh_ignore.o sh_prelude.o sh_mounts.o sh_userfiles.o sh_prelink.o sh_static.o 
> sh_prelude_old.o  -lnsl  -lnsl -lresolv
> sh_files.o: In function `sh_files_parse_mask':
> x_sh_files.c:(.text+0x45d): undefined reference to `__stack_chk_guard'
> x_sh_files.c:(.text+0x695): undefined reference to `__stack_chk_guard'
> x_sh_files.c:(.text+0x849): undefined reference to `__stack_chk_fail'
> sh_files.o: In function `sh_files_filecheck':
> x_sh_files.c:(.text+0x1619): undefined reference to `__stack_chk_guard'
> x_sh_files.c:(.text+0x16ad): undefined reference to `__stack_chk_guard'
> x_sh_files.c:(.text+0x1921): undefined reference to `__stack_chk_fail'
> sh_files.o: In function `sh_files_checkdir':
> x_sh_files.c:(.text+0x1f73): undefined reference to `__stack_chk_guard'
> x_sh_files.c:(.text+0x1fbc): undefined reference to `__stack_chk_guard'
> x_sh_files.c:(.text+0x2756): undefined reference to `__stack_chk_fail'
> sh_tiger0.o: In function `md5_buffer':
> x_sh_tiger0.c:(.text+0x2bd3): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x2c09): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x2c1d): undefined reference to `__stack_chk_fail'
> sh_tiger0.o: In function `sh_tiger_hash_val':
> x_sh_tiger0.c:(.text+0x2c8b): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x2cd9): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x348f): undefined reference to `__stack_chk_fail'
> sh_tiger0.o: In function `sh_tiger_hash_gpg':
> x_sh_tiger0.c:(.text+0x37a0): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x38b3): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x3934): undefined reference to `__stack_chk_fail'
> sh_tiger0.o: In function `sh_tiger_generic_hash':
> x_sh_tiger0.c:(.text+0x3a2b): undefined reference to `__stack_chk_guard'
> x_sh_tiger0.c:(.text+0x3a72): undefined reference to `__stack_chk_guard'
> x_

Bug#367221: quodlibet: problem with pygst still happening

[The Anarcat]

Package: quodlibet
Version: 0.22-2
Followup-For: Bug #367221

quodlibet still refuses to start here. I do not know what virtual-python
is, but I don't think I have it installed. I think the problem is due to
the python transition:

[EMAIL PROTECTED]:~$ quodlibet 
Traceback (most recent call last):
  File "/usr/bin/quodlibet", line 305, in ?
import pygst
ImportError: No module named pygst
[EMAIL PROTECTED]:~$ python -V
Python 2.3.5
[EMAIL PROTECTED]:~$ python -c "import pygst; print pygst"

[EMAIL PROTECTED]:~$ locate pygst.py
/usr/lib/python2.3/site-packages/pygst.py
/usr/lib/python2.3/site-packages/pygst.pyc
/usr/lib/python2.3/site-packages/pygst.pyo

notice how pygst is in the python2.3 directories. python2.3 is used by
default on my system but quodlibet explicitely requests 2.4:

$ head -1 /usr/bin/quodlibet
#!/usr/bin/python2.4

Upgrading python-gst0.10 from 0.10.2-1 to 0.10.4-4 fixes the problem,
oddly enough, even though pygst is still in python2.3.. Maybe fixing
quodlibet's depends to force a python-gst upgrade could resolve the
issue for most people?

thanks for the speedy updates of quodlibet, it's great software.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)

Versions of packages quodlibet depends on:
ii  exfalso   0.22-2 audio tag editor for GTK+
ii  gstreamer0.10-plugins-base0.10.8-1   GStreamer plugins from the "base" 
ii  gstreamer0.10-plugins-good0.10.3-2   GStreamer plugins from the "good" 
ii  gstreamer0.10-plugins-ugly0.10.3-2   GStreamer plugins from the "ugly" 
ii  python-central0.5.0  register and build utility for Pyt
ii  python-gst0.100.10.2-1   generic media-playing framework (P
ii  python2.4 2.4.3-7An interactive high-level object-o

Versions of packages quodlibet recommends:
ii  gstreamer0.10-alsa0.10.8-1   GStreamer plugin for ALSA
ii  gstreamer0.10-gnomevfs0.10.8-1   GStreamer plugin for GnomeVFS
ii  python-feedparser 4.1-4  Universal Feed Parser for Python
pn  quodlibet-ext  (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#381232: Solution tested

[bad_mr_frosty_be]

The solution you gave worked for me.

Thanks

regards,

Barth


 p5.vert.ukl.yahoo.com uncompressed Sat Aug 12 09:27:00 GMT 2006 


___ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet 
! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos 
expériences. 
http://fr.answers.yahoo.com 




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382616: package is unusable for standalone development: uglib.h has conflicts with glib-2.0 headers

[Uplink]

Package: liblinphone1-dev
Version: 1.3.5-1
Severity: grave

Hello,

I'm trying to write an application that uses liblinphone, and I'm using 
linphonec as reference. I took out the linphonec sources and wrote a 
custom Makefile in an attempt of building it outside the linphone 
package source tree, but I get warning and errors when I attempt to 
build it.


As far as I understand, this should build:

   #include 
   int main()
   {
   return 0;
   }

but doesn't. I get a few screens full of errors. Here are a few:

/usr/lib/glib-2.0/include/glibconfig.h:33: error: redefinition of `guint8'
/usr/include/linphone/uglib.h:48: error: `guint8' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:34: error: redefinition of `gint16'
/usr/include/linphone/uglib.h:42: error: `gint16' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:35: error: redefinition of `guint16'
/usr/include/linphone/uglib.h:40: error: `guint16' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:39: error: redefinition of `gint32'
/usr/include/linphone/uglib.h:43: error: `gint32' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:40: error: redefinition of `guint32'
/usr/include/linphone/uglib.h:41: error: `guint32' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:46: error: redefinition of `gint64'
/usr/include/linphone/uglib.h:39: error: `gint64' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:47: error: redefinition of `guint64'
/usr/include/linphone/uglib.h:38: error: `guint64' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:58: error: redefinition of `gssize'
/usr/include/linphone/uglib.h:53: error: `gssize' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:59: error: conflicting types for 
`gsize'

/usr/include/linphone/uglib.h:52: error: previous declaration of `gsize'

I attach the Makefile, the stub application from above and the output of 
'make' on my system.


Any ideas how should I proceed in the meantime?

Thanks.
#include 

int main()
{
return 0;
}
gcc  -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
-I/usr/include/linphone -I/usr/include/ortp  emptylinphone.c  -lgthread-2.0 
-lgmodule-2.0 -ldl -lglib-2.0 -llinphone   -o emptylinphone
In file included from /usr/lib/glib-2.0/include/glibconfig.h:9,
 from /usr/include/glib-2.0/glib/gtypes.h:30,
 from /usr/include/glib-2.0/glib/galloca.h:30,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/linphone/linphonecore.h:39,
 from emptylinphone.c:1:
/usr/include/glib-2.0/glib/gmacros.h:69:1: warning: "G_GNUC_CONST" redefined
In file included from /usr/include/linphone/sndcard.h:37,
 from /usr/include/linphone/linphonecore.h:22,
 from emptylinphone.c:1:
/usr/include/linphone/uglib.h:211:1: warning: this is the location of the 
previous definition
In file included from /usr/include/glib-2.0/glib/gtypes.h:30,
 from /usr/include/glib-2.0/glib/galloca.h:30,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/linphone/linphonecore.h:39,
 from emptylinphone.c:1:
/usr/lib/glib-2.0/include/glibconfig.h:33: error: redefinition of `guint8'
/usr/include/linphone/uglib.h:48: error: `guint8' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:34: error: redefinition of `gint16'
/usr/include/linphone/uglib.h:42: error: `gint16' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:35: error: redefinition of `guint16'
/usr/include/linphone/uglib.h:40: error: `guint16' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:39: error: redefinition of `gint32'
/usr/include/linphone/uglib.h:43: error: `gint32' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:40: error: redefinition of `guint32'
/usr/include/linphone/uglib.h:41: error: `guint32' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:46: error: redefinition of `gint64'
/usr/include/linphone/uglib.h:39: error: `gint64' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:47: error: redefinition of `guint64'
/usr/include/linphone/uglib.h:38: error: `guint64' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:58: error: redefinition of `gssize'
/usr/include/linphone/uglib.h:53: error: `gssize' previously declared here
/usr/lib/glib-2.0/include/glibconfig.h:59: error: conflicting types for `gsize'
/usr/include/linphone/uglib.h:52: error: previous declaration of `gsize'
In file included from /usr/include/glib-2.0/glib/gtypes.h:30,
 from /usr/include/glib-2.0/glib/galloca.h:30,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/linphone/linphonecore.h:39,
 from emptylinphone.c:1:
/usr/lib/glib-2.0/include/glibconfig.h:69:1: warning: "GINT_TO_POINTER" 
redefined
In file in

Bug#382619: uswsusp: FTBFS: error: 'SYNC_FILE_RANGE_WRITE' undeclared

[Julien Danjou]

Package: uswsusp
Version: 0.2-2
Severity: serious

Hello,

There was a problem while autobuilding your package:

> Automatic build of uswsusp_0.2-2 on avidan by sbuild/i386 0.49
> Build started at 20060812-0603
> **
...
> cc -Wall -O2 -DS2RAM -c vbetool/vbetool.c -o vbetool/vbetool.o
> cc -Wall -O2 -DS2RAM -c radeontool.c -o radeontool.o
> cc -Wall -O2 -DS2RAM -c dmidecode.c -o dmidecode.o
> cc -g -Wall -I/usr/local/include -DCONFIG_COMPRESS -I../liblzf-1.51 -c 
> bootsplash.c -o bootsplash.o
> cc -g -Wall -I/usr/local/include -DCONFIG_COMPRESS -I../liblzf-1.51 -c 
> splash.c -o splash.o
> cc -g -O2 -DCONFIG_BOTH -Wall -I/usr/local/include -DCONFIG_COMPRESS 
> -I../liblzf-1.51 md5.o encrypt.o config.o suspend.c s2ram.c -o s2disk vt.o 
> vbetool/lrmi.o vbetool/x86-common.o vbetool/vbetool.o radeontool.o 
> dmidecode.o splash.o bootsplash.o -L/usr/local/lib -L../liblzf-1.51 -llzf 
> -lpci
> In file included from suspend.c:34:
> swsusp.h: In function 'start_writeout':
> swsusp.h:141: error: 'SYNC_FILE_RANGE_WRITE' undeclared (first use in this 
> function)
> swsusp.h:141: error: (Each undeclared identifier is reported only once
> swsusp.h:141: error: for each function it appears in.)
> make[1]: *** [s2disk] Error 1
> make[1]: Leaving directory `/build/buildd/uswsusp-0.2/suspend-0.2'
> make: *** [build-stamp] Error 2
> ******
> Build finished at 20060812-0603
> FAILED [dpkg-buildpackage died]
> --

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature

Bug#382578: cdrecord: possible file I/O operation without error checking

[Joerg Schilling]

Your report is not really useful as it does not mention what hapens.
For a real bug report, you need to report the problem in a tracable way:

http://cdrecord.berlios.de/old/private/problems.html


Trying to guess what you may want so say.

If your "problem" is that there is an "error" condition without an error,
file a bug report against the fread(3) implementation on your OS.

fread() is not allowed to set the ferror() condition in case that there 
is no "read error".

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily

Bug#382621: [squirrelmail]: SquirrelMail 1.4.8 released - fixes variable overwriting attack

[Helmut]

Package: squirrelmail
Version: 2:1.4.4-8
Severity: grave
Tags: security patch

http://www.derkeiler.com/Mailing-Lists/securityfocus/bugtraq/2006-08/msg00248.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#293665: quodlibet: link with trac bug

[The Anarcat]

Package: quodlibet
Version: 0.22-2
Followup-For: Bug #293665

forwarded 293665 http://sacredchao.net/quodlibet/ticket/25
thanks

This bug was already notified in the project's Trac long time ago and
closed last year. I added a comment there as to how this was a problem
for me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#372209: slrn: Shows unreadable data on some message types

[Norbert Tretkowski]

tags 372209 +confirmed
tags 372209 +upstream
severity 372209 wishlist
thanks

* Sune Vuorela wrote:
> I read some mailing lists thru gmane. Some of these postings is not
> readable in slrn

Currently slrn doesn't support multipart mime. It's on the wishlist,
but at quite low priority.

Meanwhile you could use this script:
http://www.geocities.com/tsca.geo/slang.html#mime

Norbert


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382532: Strange errors on upgrade.

[Manoj Srivastava]

reassign 382532 dpkg
thanks
Hi,

The odds are that it is either a hardware, kernel or dpkg
 bug. The smart money is on local FS corruption, which has badly
 messed up the upgrade operation (and the file
 /var/lib/dpkg/info/libselinux1.list was damaged in the process).

I am assigning this to dpkg in the name of due diligence, but
 I would urge the reporter to see if something else got corrupted on
 the file system.

manoj
-- 
Remember your place, programmer, that way you may keep your head.
Manoj Srivastava <[EMAIL PROTECTED]>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382620: xwatch: FTBFS: bashisms

[Julien Danjou]

Package: xwatch
Version: 2.11-11
Severity: important

Hello,

There was a problem while autobuilding your package:

> Automatic build of xwatch_2.11-11 on avidan by sbuild/i386 0.49
> Build started at 20060812-0640
> **
...
> install -d debian/xwatch/usr/share/man/man1
> install -m 755 src/xwatch `pwd`/debian/xwatch/usr/bin
> install -m 644 XWatch.ap `pwd`/debian/xwatch/etc/X11/app-defaults/XWatch
> install -d doc/tmp
> cp doc/xwatch.yo doc/tmp
> (cd doc/tmp/; patch < ../../debian/xwatch.yo.debian-patch; yodl2html xwatch 
> && yodl2txt xwatch && yodl2man xwatch && patch < ../xwatch.man.patch && patch 
> < ../../debian/xwatch.man.patch)
> patching file xwatch.yo
> [: 134: ==: unexpected operator
> Yodl2html 2.01.03
> Yodl is processing a(n) report
> Document title: XWatch  The Logfiles Watcher
> xwatch.yo:313: No macro: owner(...)
> [: 134: ==: unexpected operator
> Yodl2html 2.01.03
> Yodl is processing a(n) report
> Document title: XWatch 
>  The Logfiles Watcher
> xwatch.yo:313: No macro: owner(...)
> [: 134: ==: unexpected operator
> Yodl2man 2.01.03
> Yodl is processing a(n) report
> xwatch.yo:313: No macro: owner(...)
> can't find file to patch at input line 3
> Perhaps you should have used the -p or --strip option?
> The text leading up to this was:
> --
> |*** xwatch.man~  Sun Apr 18 19:34:40 1999
> |--- xwatch.man   Sun Apr 18 19:36:52 1999
> --
> File to patch: 
> Skip this patch? [y] 
> Skipping patch.
> 1 out of 1 hunk ignored
> make: *** [binary-arch] Error 1
> **
> Build finished at 20060812-0641
> FAILED [dpkg-buildpackage died]
> --

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature

Bug#382622: p0f v2 (2.0.7) is available

[Dr. Markus Waldeck]

Package: p0f
Version: 2.0.5-1
Severity: normal

*** Please type your report below this line ***
p0f v2 (2.0.7) is available

http://lcamtuf.coredump.cx/p0f.shtml


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages p0f depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libpcap0.70.7.2-7System interface for user-level pa

p0f recommends no packages.

-- no debconf information

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#294507: gnucash: crashes while printing transaction report

[Neil Williams]

>> If I create a transaction report, then print it to the default printer,
>> gnucash crashes (window and process disappear); printing to a file does
>> not crash (and the resulting postscript file can be printed normally).
>> 
>> This machine has cupsys-bsd and cupsys-client, but not cupsys installed.
>> The printer is (obviously) on another machine which does have a CUPS
>> server installed.  Other programs (lpr, gv, a2ps) do not have trouble
>> printing.
> 
> Can you confirm whether this happens with the latest gnucash packages?

This bug is now well over a year old and there is a new version of
gnucash in unstable which uses updated libraries and gnucash code to
support printing.

Could you check in gnucash 2.0.0 or 2.0.1 please?

I also use a network printer via CUPS and I have just printed a
transaction report in gnucash 2.0.1-1 without problems.

-- 

Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/




signature.asc
Description: OpenPGP digital signature

Bug#382604: zaptel: fails by post-install

[Mark Purcell]

On Saturday 12 August 2006 07:56, Christoph Kaminski wrote:
> Setting up zaptel (1.2.7.dfsg-3) ...
> Zaptel cards initial configuration: ZT_SPANCONFIG failed on span 1: Invalid

Thanks Christoph,

This is probably due to a version incompatability bewteen the installed 
zaptel-modules you have installed and your kernel.

What sort of zaptel hardware do you have installed in your system, and when 
was the last time you built the zaptel-modules?

Could you provide the output of:

$ dpkg -l zaptel-modules*

and /etc/zaptel.conf

Thanks,
Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382588: loop-aes-modules: FTBFS: fails to install modules

[Max Vozeler]

Hi Julien,

Thanks for your report. 

On Sat, Aug 12, 2006 at 01:14:59AM +0200, Julien Danjou wrote:
> There was a problem while autobuilding your package:
> 
> > Automatic build of loop-aes-modules_3.1d+3+3 on avidan by sbuild/i386 0.49
> > Build started at 20060812-0033
> > **
> ...
> > dh_builddeb --destdir=/usr/src/linux-headers-2.6.16-2-486/..
> > dpkg-deb: unable to create 
> > `/usr/src/linux-headers-2.6.16-2-486/../loop-aes-2.6.16-2-486_3.1d+3+3_i386.deb':
> >  Permission denied
> > dpkg-deb: building package `loop-aes-2.6.16-2-486' in 
> > `/usr/src/linux-headers-2.6.16-2-486/../loop-aes-2.6.16-2-486_3.1d+3+3_i386.deb'.
> > dh_builddeb: command returned error code 512

This seems to be caused by a change in module-assistant.
It wasn't noticed so far because m-a 0.10.5 was uploaded after 
the lastest loop-aes-modules had already been built:

  module-assistant (0.10.5) unstable; urgency=low
...
* disabled an old crufty "helper" for DEB_DESTDIR && KMAINT mode
  (closes: #368122)

I will fix this in the next upload by explicitly setting
DEB_DESTDIR to the expected directory. It could be that
integration with linux-modules-extra-2.6 will happen earlier, 
so that loop-aes-modules would be obsoleted and removed.

cheers,
Max



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#352895: gnucash --add-price-quotes does not respect the file compression option

[Neil Williams]

Hi Frank,

There's a new version of gnucash in unstable, 2.0.1-1, which is a
substantial upgrade from the previous 1.8 tree.

Please could you confirm a few things and retest in the current version?

1. When you open your gnucash file after running the cron job and save
the file normally, is it recompressed?

2. In your bug report, which is the file being generated by the cron
job? .xac files are normally backup files created by gnucash, your main
data file (comptes-euro.gnucash) appears compressed from the bug report
text.

-- 

Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/




signature.asc
Description: OpenPGP digital signature

Bug#373316: diff for 2.4.4-2.1 NMU

[Pierre HABOUZIT]

Hi,

Attached is the diff for my ecasound2.2 2.4.4-2.1 NMU.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
diff -u ecasound2.2-2.4.4/debian/changelog ecasound2.2-2.4.4/debian/changelog
--- ecasound2.2-2.4.4/debian/changelog
+++ ecasound2.2-2.4.4/debian/changelog
@@ -1,3 +1,14 @@
+ecasound2.2 (2.4.4-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update Build-Depends for kfreebsd-amd64 (Closes: #361469).
+  * Simplify Build-Depends as well.
+  * Update to the last python policy (Closes: #373316).
+  * Bump Standards-Version to 3.7.2.
+  * python-ecasound2.2 is an arch:all package.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 12:30:52 +0200
+
 ecasound2.2 (2.4.4-2) unstable; urgency=low
 
   * Work with newer autoconf/automake ? which seems to be using more {}s.
diff -u ecasound2.2-2.4.4/debian/control ecasound2.2-2.4.4/debian/control
--- ecasound2.2-2.4.4/debian/control
+++ ecasound2.2-2.4.4/debian/control
@@ -2,14 +2,19 @@
 section: sound
 Priority: extra
 Maintainer: Junichi Uekawa <[EMAIL PROTECTED]>
-Standards-Version: 3.6.2
-Build-Depends: libsndfile1-dev (>= 1.0.5), libaudiofile-dev, libasound2-dev 
[!kfreebsd-i386], debhelper (>> 4.1.1), libwrap-dev, libncurses5-dev, 
python2.3-dev, ladspa-sdk (>= 1.0.LGPL-3), libtool, m4, libreadline5-dev, 
libjack0.100.0-dev, libsamplerate0-dev, dpatch, hevea, doxygen, tetex-bin, 
tetex-extra, autoconf, automake1.9, python, yodl, ruby1.8, ruby, 
python-docutils, g++ (>= 4:4.0.0)
+Standards-Version: 3.7.2
+Build-Depends: libsndfile1-dev (>= 1.0.5), libaudiofile-dev,
+ libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
+ debhelper (>> 4.1.1), python-dev, python-support (>= 0.4.0), libwrap-dev,
+ libncurses5-dev, ladspa-sdk (>= 1.0.LGPL-3), libtool, m4, libreadline5-dev,
+ libjack0.100.0-dev, libsamplerate0-dev, dpatch, hevea, doxygen, tetex-bin,
+ tetex-extra, autoconf, automake1.9, yodl, ruby1.8, ruby, python-docutils
 Build-Conflicts: libecasound7, libkvutils2, libecasound7c102, libkvutils2c102
 
 Package: ecasound
 Architecture: any
 Depends: ${shlibs:Depends}, python-ecasound2.2, python
-Suggests: mp3-encoder, mpg321 | mp3-decoder, vorbis-tools, python-ecasound (= 
${Source-Version}), swh-plugins | ladspa-plugin, timidity, mikmod
+Suggests: mp3-encoder, mpg321 | mp3-decoder, vorbis-tools, swh-plugins | 
ladspa-plugin, timidity, mikmod
 Provides: ladspa-host, ecasound
 Replaces: ecasound2.2 (<< 2.3.2-1), libecasound7c102, libecasound7
 Description: Multitrack-capable audio recorder and effect processor
@@ -63,10 +68,10 @@
  modules, some string processing routines, and support for locks.
 
 Package: python-ecasound2.2
-Architecture: any
+Architecture: all
 Section: python
 Depends: ${shlibs:Depends}, ${python:Depends}
-Provides: python-ecasound
+Provides: python-ecasound, ${python:Provides}
 Conflicts: python-ecasound
 Description: python binding files for ecasound 2.2
  Ecasound is a software package designed for multitrack audio
@@ -80,7 +85,6 @@
  creating alternative user-interfaces is easy. 
  .
  Includes python bindings for ecasound.
- Note that this version is for python version 2.3.
 
 Package: libecasound-ruby1.8
 Architecture: any
diff -u ecasound2.2-2.4.4/debian/rules ecasound2.2-2.4.4/debian/rules
--- ecasound2.2-2.4.4/debian/rules
+++ ecasound2.2-2.4.4/debian/rules
@@ -107,7 +107,7 @@
done
# python
mv $(CURDIR)/debian/${ECASOUND}/usr/lib/python* 
$(CURDIR)/debian/$(PYTHONECASOUND)/usr/lib/
-   chmod 644 
$(CURDIR)/debian/$(PYTHONECASOUND)/usr/lib/python2.3/site-packages/pyeca.py
+   chmod 644 
$(CURDIR)/debian/$(PYTHONECASOUND)/usr/lib/python*/site-packages/pyeca.py
# ruby
mv $(CURDIR)/debian/${ECASOUND}/usr/lib/ruby/1.8/ecasound.rb 
$(CURDIR)/debian/$(RUBYECASOUND)/usr/lib/ruby/1.8/
chmod 644 $(CURDIR)/debian/$(RUBYECASOUND)/usr/lib/ruby/1.8/ecasound.rb
@@ -126,6 +126,7 @@
install -m644 -o root -g root ecatools/ecasound.el 
debian/ecasound-el/usr/share/emacs/site-lisp/ecasound-el/ecasound.el
dh_installemacsen -p ecasound-el --priority=60 
dh_installchangelogs  -i
+   dh_pysupport -i
dh_compress -i
dh_fixperms -i
dh_installdeb -i
@@ -151,7 +152,7 @@
dh_installinfo -a
dh_installchangelogs  -a
dh_link -a
-   dh_python -a 
+   dh_pysupport -a
dh_strip -a
dh_shlibdeps -a
dh_compress -a


signature.asc
Description: Digital signature

Bug#382491: segfaults on startup

[Tobias Doerffel]

lmms keeps segfaulting right after the configuration dialog finished:

the maintainer of the debian-package didn't package a new release of
LMMS (which fixes *a lot* of bugs!) yet, so please either stay patient
or download and compile LMMS manually...

toby


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#115465: gnucash: Invoice output suggestion

[Neil Williams]

Hi David,

OK, it's been a terribly long time but, for the record, I just wanted to
review this bug in the light of the current gnucash version, 2.0.1-1.

The invoice-related reports have been overhauled for 2.0 and AFAICT,
your request has been implemented, albeit not quite in the manner you
describe because the invoice structure appears to differ from gnucash
1.6 to 2.0 (I can't remember what 1.6 looked like!)

Every item specified in a gnucash2 invoice is now representable in at
least one of the supported report types for invoices.

If you are still interested in gnucash, please take a look at v2.0 and
let me know if you consider this bug closed.

If there is no response, I'll close the report because gnucash does now
support output of all available invoice fields.

-- 

Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/




signature.asc
Description: OpenPGP digital signature

Bug#344333: libextractor-python: seems fixed with 1:0.5

[Karsten Hilbert]

Package: libextractor-python
Version: 1:0.5
Followup-For: Bug #344333

The package now does pass the unit test. Likely because it
was rewritten using ctypes.

Karsten

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages libextractor-python depends on:
ii  libextractor1c2a  0.5.14-2   extracts meta-data from files of a
ii  python2.3.5-11   An interactive high-level object-o
ii  python-ctypes 0.9.9.6-1  Python package to create and manip

Versions of packages libextractor-python recommends:
ii  libextractor-plugins  0.5.14-2   extracts meta-data from files of a

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382597: clamav-freshclam calls start_daemon in a way that fails

[Stephen Gran]

This one time, at band camp, Chris Lawrence said:
> >
> >[EMAIL PROTECTED]:/home/joey>/etc/init.d/clamav-freshclam start
> >+ start_daemon /usr/bin/freshclam -p /var/run/clamav/freshclam.pid -d 
> >--quiet
> >+ local force nice pidfile exec i
> >+ force=0
> >+ nice=0
> >+ pidfile=/dev/null
> >+ getopts fn:p: opt
> >+ shift 2
> >+ '[' /var/run/clamav/freshclam.pid = -- ']'
> >+ exec=/var/run/clamav/freshclam.pid
> >+ shift
> >+ '[' 0 = 1 ']'
> >+ '[' /dev/null ']'
> >+ /sbin/start-stop-daemon --start --nicelevel 0 --quiet --exec
> >/var/run/clamav/freshclam.pid --oknodo --pidfile /dev/null -- -d --quiet
> >
> >If this is a bug in clamav-freshclam for passing the daemon to start before
> >the options, please reassign the bug; I haven't checked the LSB and this
> >package doesn't seem to bother to document start_daemon's syntax 
> >internally.
> 
> The LSB does require that all options be specified before the
> executable name; I am revising README.Debian in lsb-base to include
> documentation of all of the functions.

The command line options are options to be passed to freshclam on
startup, on the right side of the -- in the s-s-d call.  They are not
arguments to start_daemon.

The problem here is that the clamav init scripts use other functions
from lsb before running start_daemon, and OPTIND is still > 1 in the
second call.  This makes the getopt run in start_daemon do the wrong
thing, and it misparses the arguments.  I have worked around this in 
the clamav init scripts by manually setting OPTIND=1 before each
invocation of start_daemon (as that's the only function where ordering
matters). 

Joey, can you please test that 0.88.4-2 works correctly for you?  It
does here, but I wouldn't mind a second set of eyes on it.

Chris, can you take a look at the patch in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381822;msg=15;att=0 and
see if that looks OK?  It sets OPTIND before each getopt call to avoid
these issues, and it also cleans up the remaining mistakes in my
original patch to you.

Thanks all,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :[EMAIL PROTECTED] |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#382612: bzr: '~' in Version number violates policy 5.6.12

[martin f krafft]

severity wishlist
reassign 382612 debian-policy
retitle 382612 please document ~ as allowable character in version numbers
thanks

No reason to leave this bug open on bzr...

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system


signature.asc
Description: Digital signature (GPG/PGP)

Bug#382623: debconf: [INTL:dz] Dzongkha debconf (program) templates translation

[Tenzin Dendup]

Package: debconf
Version: N/A
Severity: wishlist
Tags: patch l10n

Please find attached the Dzongkha (dz) translation for the 
debconf(program) package

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages debconf depends on:
ii  debconf-i18n  1.5.2  full internationalization support 
ii  perl-base 5.8.8-4The Pathologically Eclectic Rubbis

Versions of packages debconf recommends:
ii  apt-utils 0.6.44.2   APT utility programs

-- debconf information excluded


dz.po.gz
Description: Binary data

Bug#382604: zaptel: fails by post-install

[Christoph Kaminski]

Mark Purcell schrieb:

On Saturday 12 August 2006 07:56, Christoph Kaminski wrote:

Setting up zaptel (1.2.7.dfsg-3) ...
Zaptel cards initial configuration: ZT_SPANCONFIG failed on span 1: Invalid


Thanks Christoph,

This is probably due to a version incompatability bewteen the installed 
zaptel-modules you have installed and your kernel.


What sort of zaptel hardware do you have installed in your system, and when 
was the last time you built the zaptel-modules?


Could you provide the output of:

$ dpkg -l zaptel-modules*

and /etc/zaptel.conf

Thanks,
Mark


dpkg -l | grep zaptel-modules
ii  zaptel-modules-2.6.161.2.6-2+meinkernel.03 
zaptel modules for Linux (kernel 2.6.16).
ii  zaptel-modules-2.6.17-1-k7   1.2.7.dfsg-3+2.6.17-5 
zaptel modules for Linux (kernel 2.6.17-1-k7



Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up zaptel (1.2.7.dfsg-3) ...
Zaptel cards initial configuration: ZT_SPANCONFIG failed on span 1: 
Invalid argument (22)

invoke-rc.d: initscript zaptel, action "start" failed.
dpkg: error processing zaptel (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 zaptel
E: Sub-process /usr/bin/dpkg returned an error code (1)
satan:/usr/src# ztcfg
ZT_SPANCONFIG failed on span 1: Invalid argument (22)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#302908: gnucash: Can't edit old transactions - no currency

[Neil Williams]

Hi Thomas,

The issues behind your bug report were addressed in the transition from
gnucash 1.8 to gnucash 2.0. There were a number of issues with the way
1.8 stored data which were solved in 2.0. Data files created with
previous versions should now be automatically updated when loaded by 2.0
to remove problems like this. (Unfortunately, it also means that such
data files may not be editable / loadable by gnucash 1.8 anymore.)

Please can you test in gnucash 2.0.1-1. Simply upgrade to the latest
version in Debian unstable, load your data file, save it and then retry
to edit the transactions that caused trouble originally.

If you want to retain 1.8 compatibility, copy the file to a new location
before loading it in gnucash 2.0.x

Thanks.

-- 

Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/




signature.asc
Description: OpenPGP digital signature

Bug#379366: Another confirmation of the bug

[Vasilis Vasaitis]

  Hi,

  I'd just like to say that this bug manifests on my system too. The
symptoms are exactly as the other submitters have described. I have
also saved my current prelink cache file in case it might be useful.

Thanks,
Vasilis

-- 
Vasilis Vasaitis
"A man is well or woe as he thinks himself so."




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#360780: build: powerpc problem with sign of char

[Neil Williams]

Hi Jorg:

Note: If the errors you report are in files prefixed with go- or in the
lib/goffice* or lib/libgsf* directories, these are *not* gnucash errors,
they are upstream GOffice issues. As such, you could rebuild with the
goffice development libraries installed and use the upstream code (which
is more recent than the code included in gnucash). GnuCash will
automatically detect libgoffice-1-dev and libgsf-1-dev installations and
use the associated libraries instead of building the code in
lib/goffice* and lib/libgsf*.

Other instances of this issue *have* been addressed upstream and if you
still find issues during the build of the latest 2.0.1 release, please
could you report the names of all files below src/ which are affected.

Thanks.

-- 

Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/




signature.asc
Description: OpenPGP digital signature

Bug#350747: Just updated the server, the problem is not present anymore.

[Jesus Climent]

Hi

Just got my server in shape, and installed stunnel4 from scratch, and not it
works.

Have not done anything, so i guess we can close this bug unless other people
continue having the problem.

Cheers,
-- 
Jesus Climent  info:www.pumuki.org dj:triplestereo.com
Unix SysAdm|Linux User #66350|Debian Developer|2.6.17|Helsinki Finland
GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429  7E18 66FC 1D7F 8694 6D69

And then he ran into my knife... he ran into my knife ten times.
--June (Chicago)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#369116: python-gdchart: Status?

[Pierre HABOUZIT]

rassign 369116 ftp.debian.org
retitle 369116 RM: python-gdcart; RoQA: obsolete, superseeded by python-gdchart2
thanks

On Mon, Aug 07, 2006 at 11:13:19AM +0200, Stefan Huehner wrote:
> Package: python-gdchart
> Followup-For: Bug #369116
> 
> 
> Hi,
> as i've seen no progress or comment on this bug?
> 
> Are there any objections to removing python-gdchart?
> 
> Regards,
> Stefan
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.17-1-amd64-k8-smp
> Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> 
> 

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


signature.asc
Description: Digital signature

Bug#382604: zaptel: fails by post-install

[Mark Purcell]

Thanks,

On Saturday 12 August 2006 12:09, you wrote:
> > What sort of zaptel hardware do you have installed in your system, and
> > when was the last time you built the zaptel-modules?

This could be an issue, what sort of zaptel hardware do you have?

> dpkg -l | grep zaptel-modules
> ii  zaptel-modules-2.6.161.2.6-2+meinkernel.03
>  zaptel modules for Linux (kernel 2.6.16).
> ii  zaptel-modules-2.6.17-1-k7   1.2.7.dfsg-3+2.6.17-5
>  zaptel modules for Linux (kernel 2.6.17-1-k7

Looks like you have built a recent set of modules for your current kernel.  I 
wonder if they are actually loading:

What sort of output do you get from zttool?

> > Could you provide the output of:
> >
> > and /etc/zaptel.conf

Still need a copy of your zaptel.conf.

Also could you provide the list of modules you have loaded:

$ lsmod

Thanks,
Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#302908: gnucash: Can't edit old transactions - no currency

[Neil Williams]

Oops. Didn't read the full report.

The upstream bug referenced in #8 has now been fixed. As the original
problem cannot be reproduced due to a previous glitch, should this
report simply be closed too?

-- 

Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/




signature.asc
Description: OpenPGP digital signature

Bug#382624: xmms_1:1.2.10+20060801-1(unstable/arm/toffee): needs libtool update for arm

[James Troup]

Package: xmms
Version: 1:1.2.10+20060801-1
Severity: important

The version of libtool used to build this source package is too old to
correctly support shared libraries for at least arm.  Please see
http://people.debian.org/~keybuk/libtool-pass_all.html for more
information.

| Automatic build of xmms_1:1.2.10+20060801-1 on toffee by sbuild/arm 85
| Build started at 20060812-0142
| **

[...]

| ** Using build dependencies supplied by package:
| Build-Depends: debhelper (>= 4), dpatch, autotools-dev, automake1.9, libtool, 
gettext, libasound2-dev [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386], 
libaudiofile-dev, libgl1-mesa-dev | xlibmesa-gl-dev, libglib1.2-dev, 
libgtk1.2-dev, libesd0-dev, libice-dev, libmikmod2-dev, libogg-dev, libsm-dev, 
libvorbis-dev, libx11-dev, libxext-dev, libxi-dev, libxxf86vm-dev, libxml-dev, 
libssl-dev, sharutils

[...]

| checking how to recognise dependent libraries... file_magic ELF 
[0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )

[...]

| *** Warning: linker path does not have real file for library -lpthread.

A complete build log can be found at
http://buildd.debian.org/build.php?arch=arm&pkg=xmms&ver=1:1.2.10+20060801-1

-- 
James


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382604: zaptel: fails by post-install

[Christoph Kaminski]

Mark Purcell schrieb:

Thanks,

On Saturday 12 August 2006 12:09, you wrote:

What sort of zaptel hardware do you have installed in your system, and
when was the last time you built the zaptel-modules?


This could be an issue, what sort of zaptel hardware do you have?
01:06.0 Network controller: Cologne Chip Designs GmbH ISDN network 
controller [HFC-PCI] (rev 02)

Subsystem: Cologne Chip Designs GmbH ISDN Board
Flags: bus master, medium devsel, latency 16, IRQ 11
I/O ports at a000 [size=8]
Memory at e4004000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1





dpkg -l | grep zaptel-modules
ii  zaptel-modules-2.6.161.2.6-2+meinkernel.03
 zaptel modules for Linux (kernel 2.6.16).
ii  zaptel-modules-2.6.17-1-k7   1.2.7.dfsg-3+2.6.17-5
 zaptel modules for Linux (kernel 2.6.17-1-k7


Looks like you have built a recent set of modules for your current kernel.  I 
wonder if they are actually loading:


What sort of output do you get from zttool?


Could you provide the output of:

and /etc/zaptel.conf


Still need a copy of your zaptel.conf.

cat /etc/zaptel.conf
# hfc-s pci a span definition
# most of the values should be bogus because we are not really zaptel
loadzone=nl
defaultzone=nl

span=1,1,3,ccs,ami
bchan=1-2
dchan=3



Also could you provide the list of modules you have loaded:

$ lsmod


lsmod
Module  Size  Used by
dm_snapshot15968  0
dm_mirror  19216  0
nls_iso8859_1   4480  0
nls_cp437   6144  0
msdos   9024  0
vfat   12288  0
loop   15368  0
fat47196  2 msdos,vfat
isofs  33020  0
nvidia   4549908  12
binfmt_misc11336  1
ppdev   8772  0
lp 11108  0
ipv6  223968  32
usblp  12992  0
autofs419844  6
ztdummy 3784  0
zaptel203332  1 ztdummy
crc_ccitt   2496  1 zaptel
capi   16512  4
capifs  6024  2 capi
aes28416  1
dm_crypt   11272  1
dm_mod 50520  6 dm_snapshot,dm_mirror,dm_crypt
eeprom  7248  0
asb100 19156  0
hwmon_vid   2880  1 asb100
st 35228  0
advansys   71948  0
capidrv26932  1
isdn  120352  1 capidrv
slhc7040  1 isdn
ide_generic 1664  0 [permanent]
ide_cd 36128  0
cdrom  32864  1 ide_cd
usbhid 36064  1
snd_emu10k1_synth   7232  0
snd_emux_synth 30848  1 snd_emu10k1_synth
snd_seq_virmidi 7168  1 snd_emux_synth
snd_seq_midi_emul   6208  1 snd_emux_synth
snd_seq_dummy   4100  0
snd_seq_oss28928  0
snd_seq_midi8416  0
snd_seq_midi_event  7424  3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq46736  9 
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event

eth139418564  0
sd_mod 19008  1
tsdev   7680  0
snd_emu10k1   101732  5 snd_emu10k1_synth
snd_rawmidi23200  3 snd_seq_virmidi,snd_seq_midi,snd_emu10k1
snd_ac97_codec 82976  1 snd_emu10k1
snd_ac97_bus2624  1 snd_ac97_codec
snd_pcm_oss36704  0
snd_mixer_oss  16192  1 snd_pcm_oss
snd_pcm74884  5 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device  8012  8 
snd_emu10k1_synth,snd_emux_synth,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_emu10k1,snd_rawmidi

snd_timer  21124  3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc  9800  2 snd_emu10k1,snd_pcm
snd_util_mem4864  2 snd_emux_synth,snd_emu10k1
snd_hwdep   8964  2 snd_emux_synth,snd_emu10k1
sata_sil9800  2
fcpci 593536  2
i2c_nforce2 6912  0
psmouse34888  0
snd48548  19 
snd_emux_synth,snd_seq_virmidi,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep

shpchp 34528  0
pci_hotplug27516  1 shpchp
parport_pc 32612  1
parport33544  3 ppdev,lp,parport_pc
kernelcapi 44800  3 capi,capidrv,fcpci
ohci_hcd   18500  0
ehci_hcd   28360  0
nvidia_agp  7772  1
agpgart30152  2 nvidia,nvidia_agp
ohci1394   31088  0
ieee1394   88056  2 eth1394,ohci1394
i2c_core   19904  4 nvidia,eeprom,asb100,i2c_nforce2
serio_raw   6852  0
usbcore   112384  6 usblp,usbhid,ohci_hcd,ehci_hcd
soundcore   9440  1 snd
emu10k1_gp  

Bug#381677: initramfs-tools: Temporary files and initramfs world-readable

[Jonas Smedegaard]

On Sat, 12 Aug 2006 10:43:16 +0200 maximilian attems wrote:

> On Sun, 06 Aug 2006, Lionel Elie Mamane wrote:
> 
> > The generated initramfs is world-readable (as well as the temporary
> > files); this leaks cryptographic keys (in password-protected form)
> > to all users on the system when the root fs is encrypted (because
> > these keys then get copied to the initramfs, at least in the
> > loop-aes case). See bug #378488 for a discussion of this in the
> > context of loop-aes.
> 
> yaird installs initrd.img with 600 without giving any further
> reasons -> see #336454
> no reply from maintainer since bug is filed.

Acknowledged - that bug lack response from me.

But why bring that up here? Is the lack of response in a yaird bugreport
somehow proof of the opposite in intramfs-tools being correct?


But whatever - let's discuss yaird in this initramfs-tools bugreport.

yaird runs as root, and collects info from several places, some of
which may be readable only as root. It then stores that collected info
in a newly created file. As a precaution, this newly created file is
created only accessible by root, so as to not accidentally leak info.

For yaird, this mostly works well. One situation that I am aware of is
the use of ramdisks for diskless environments like lessdisks (see
bug#336518 where access rights is also - lightly - discussed).

Bug#336454 is still open as it indeed is an open issue what is the
"correct" permissions of initrd images, and yaird is controversial in
this area (as well as in other ones!).


 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm


pgp667W0JqmLY.pgp
Description: PGP signature

Bug#373496: diff for 0.9.2-1.1 NMU

[Pierre HABOUZIT]

Hi,

Attached is the diff for my pygtkmvc 0.9.2-1.1 NMU.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
diff -u pygtkmvc-0.9.2/debian/control pygtkmvc-0.9.2/debian/control
--- pygtkmvc-0.9.2/debian/control
+++ pygtkmvc-0.9.2/debian/control
@@ -3,12 +3,14 @@
 Priority: extra
 Maintainer: Johannes Jordens <[EMAIL PROTECTED]>
 Uploaders: Robert Jordens <[EMAIL PROTECTED]>
-Build-Depends-Indep: debhelper (>> 4.1.65), python-dev (>= 2.3)
-Standards-Version: 3.6.1
+Build-Depends: debhelper (>> 4.1.65), python-all-dev (>= 2.3)
+Build-Depends-Indep: python-support (>= 0.4.0)
+Standards-Version: 3.7.2
 
 Package: python-gtkmvc
 Architecture: all
 Depends: ${python:Depends}, python-gtk2 (>= 2.4.0-1), python-glade2 (>= 
2.4.0-1)
+Provides: ${python:Provides}
 Description: model-view-controller (MVC) implementation for pygtk
  This MVC for pygtk2 helps with writing well structured code by splitting 
  the program's code into three distinctive sections. A program 
diff -u pygtkmvc-0.9.2/debian/rules pygtkmvc-0.9.2/debian/rules
--- pygtkmvc-0.9.2/debian/rules
+++ pygtkmvc-0.9.2/debian/rules
@@ -5,19 +5,22 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-PYTHON=python
+PYVERS := $(shell pyversions -s | sed -e 's/$(shell pyversions -d)/python/')
 
 build: build-stamp
 build-stamp:
dh_testdir
-   $(PYTHON) setup.py build
+   set -e; \
+   for py in $(PYVERS); do \
+   $$py setup.py build; done
touch build-stamp
 
 clean:
dh_testdir
dh_testroot
rm -f build-stamp
-   -$(PYTHON) setup.py clean --all
+   for py in $(PYVERS); do \
+   $$py setup.py clean --all; done
dh_clean
 
 # install-ver:
@@ -26,18 +29,21 @@
dh_testroot
dh_clean -k
dh_installdirs
-   $(PYTHON) setup.py install --prefix $(CURDIR)/debian/python-gtkmvc/usr
+   set -e; \
+   for py in $(PYVERS); do \
+   $$py setup.py install --prefix $(CURDIR)/debian/python-gtkmvc/usr; \
+   done
 
 # Build architecture-independent files here.
 binary-indep: build install
dh_testdir
dh_testroot
-   dh_installdocs 
+   dh_installdocs
dh_installexamples
dh_installchangelogs
dh_compress
dh_fixperms
-   dh_python
+   dh_pysupport
dh_installdeb
dh_gencontrol
dh_md5sums
diff -u pygtkmvc-0.9.2/debian/changelog pygtkmvc-0.9.2/debian/changelog
--- pygtkmvc-0.9.2/debian/changelog
+++ pygtkmvc-0.9.2/debian/changelog
@@ -1,3 +1,10 @@
+pygtkmvc (0.9.2-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update package to the last python policy (Closes: #373496).
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 13:31:37 +0200
+
 pygtkmvc (0.9.2-1) unstable; urgency=low
 
   * New upstream release


signature.asc
Description: Digital signature

Bug#382614: -M not documented

[Falk Hueffner]

Jesus Climent <[EMAIL PROTECTED]> writes:

> tags 350747 + pending
> thanks
>
> On Sat, Aug 12, 2006 at 11:34:30AM +0200, Falk Hueffner wrote:
>> 
>> The man page mentions the "-M" option, but doesn't document it.
>
> Updated the man page. The option has been changed to an action, "cue".

While at it, the -a documentation implies that "cue" is done by
default, but it isn't.

-- 
Falk


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#364214: kate-plugins: don't use gmake on Debian

[Andreas Pakulat]

On 22.04.06 00:31:35, Andreas Pakulat wrote:
> I'll also file an upstream report so this hopefully will be more
> configurable in a future KDE version (hopefully before 4.0).

I fixed this myself, using AC_CHECK_PROG to try gmake and make as make
command. It's in 3.5 branch, revision 572366 of kdeaddons. Please
consider updating the kdeaddons package to that revision as currently
the make-plugin is unusable in the default installation.

Andreas

-- 
You are sick, twisted and perverted.  I like that in a person.


pgpm5dxAcxk7N.pgp
Description: PGP signature

Bug#382625: /etc/udev/permissions.rules needs system groups not created

[Fernando Lucas Rodriguez]

Package: udev
Version: 0.093-1
Severity: grave
Justification: renders package unusable

I am using several machines with testing distribution, after udev upgrade all 
of them stop booting properly.
They stop at "udev loading step", and you must press CTRL+C to continue.

After finishing booting and login /etc/init.d/udev restart works properly.

As far as I know udev needs several system groups on startup most of them from 
the
"# misc devices" section from file /etc/udev/permissions.rules
Those groups for me are nvram, sane, audio, tss, rdma

There is no dependency/check for those groups on package install.
After creating the groups manually machines boots fine.



-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 8
lrwxrwxrwx 1 root root  20 2006-07-02 20:02 020_permissions.rules -> 
../permissions.rules
lrwxrwxrwx 1 root root  19 2006-08-06 17:02 025_libgphoto2.rules -> 
../libgphoto2.rules
lrwxrwxrwx 1 root root  16 2006-08-12 12:05 025_libsane.rules -> 
../libsane.rules
lrwxrwxrwx 1 root root  13 2006-07-02 20:02 udev.rules -> ../udev.rules
lrwxrwxrwx 1 root root  25 2006-07-02 20:02 z20_persistent-input.rules -> 
../persistent-input.rules
lrwxrwxrwx 1 root root  19 2006-07-02 20:02 z20_persistent.rules -> 
../persistent.rules
-rw-r--r-- 1 root root 381 2006-07-02 20:02 z25_persistent-cd.rules
-rw-r--r-- 1 root root 577 2006-07-02 20:02 z25_persistent-net.rules
lrwxrwxrwx 1 root root  33 2006-07-02 20:02 z45_persistent-net-generator.rules 
-> ../persistent-net-generator.rules
lrwxrwxrwx 1 root root  12 2006-07-02 20:02 z50_run.rules -> ../run.rules
lrwxrwxrwx 1 root root  16 2006-07-02 20:02 z55_hotplug.rules -> 
../hotplug.rules
lrwxrwxrwx 1 root root  19 2006-07-02 22:19 z60_alsa-utils.rules -> 
../alsa-utils.rules
lrwxrwxrwx 1 root root  15 2006-08-05 16:25 z60_hdparm.rules -> ../hdparm.rules
lrwxrwxrwx 1 root root  29 2006-07-02 20:02 z75_cd-aliases-generator.rules -> 
../cd-aliases-generator.rules

-- /sys/:
/sys/block/hda/dev
/sys/block/hda/hda1/dev
/sys/block/hda/hda2/dev
/sys/block/hda/hda3/dev
/sys/block/hdb/dev
/sys/block/hdc/dev
/sys/block/hdc/hdc1/dev
/sys/block/hdd/dev
/sys/block/hdd/hdd1/dev
/sys/block/ram0/dev
/sys/block/ram10/dev
/sys/block/ram11/dev
/sys/block/ram12/dev
/sys/block/ram13/dev
/sys/block/ram14/dev
/sys/block/ram15/dev
/sys/block/ram1/dev
/sys/block/ram2/dev
/sys/block/ram3/dev
/sys/block/ram4/dev
/sys/block/ram5/dev
/sys/block/ram6/dev
/sys/block/ram7/dev
/sys/block/ram8/dev
/sys/block/ram9/dev
/sys/class/graphics/fb0/dev
/sys/class/input/input0/event0/dev
/sys/class/input/mice/dev
/sys/class/misc/agpgart/dev
/sys/class/misc/device-mapper/dev
/sys/class/misc/hpet/dev
/sys/class/misc/nvram/dev
/sys/class/misc/psaux/dev
/sys/class/misc/rtc/dev
/sys/class/ppdev/parport0/dev
/sys/class/printer/lp0/dev
/sys/class/sound/adsp/dev
/sys/class/sound/audio/dev
/sys/class/sound/controlC0/dev
/sys/class/sound/dsp/dev
/sys/class/sound/mixer/dev
/sys/class/sound/pcmC0D0c/dev
/sys/class/sound/pcmC0D0p/dev
/sys/class/sound/pcmC0D1c/dev
/sys/class/sound/timer/dev
/sys/class/usb_device/usbdev1.1/dev
/sys/class/usb_device/usbdev2.1/dev

-- Kernel configuration:


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (800, 'testing'), (400, 'unstable'), (300, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: 
LC_ALL set to [EMAIL PROTECTED])

Versions of packages udev depends on:
ii  initscripts  2.86.ds1-15 Scripts for initializing and shutt
ii  libc62.3.6-15GNU C Library: Shared libraries
ii  libselinux1  1.30-1  SELinux shared libraries
ii  libvolume-id00.093-1 libvolume_id shared library
ii  lsb-base 3.1-10  Linux Standard Base 3.1 init scrip

udev recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#336454: yaird: Creates initrd with deviating permissions

[Jonas Smedegaard]

On Sun, 30 Oct 2005 13:16:29 +0100 Frans Pop wrote:

> After installing 2.6.14 I noticed that the initrd created by yaird has
> different permissions from all other initrds on my system.
> 
> -rw---   1 root root 1069831 2005-10-30 12:11
> initrd.img-2.6.14-1-686
> 
> All others have -rw-r--r--. Also all kernel images and config files
> are world readable.
> 
> If there is not a good reason for changing permissions, I feel that
> yaird should be consistent with other tools in this respect.

First of all, I apologize for taking so long to respond to this. Thanks
to Maximilian Attems for bringing it to my attention in bug#381677.

yaird runs as root, and collects info from several places, some of
which may be readable only as root. It then stores that collected info
in a newly created file. As a precaution, this newly created file is
created only accessible by root, so as to not accidentally leak info.

This mostly works well. One situation that I am aware of is the use of
ramdisks for diskless environments like lessdisks (see bug#336518 where
access rights is also - lightly - discussed).

I consider the tight permissions a feature, not a bug, but has left
this bugreport open for the benefit of the doubt.

Are you aware of any ill effects of the tight permissions, in addition
to the already known one of tftp publication?

If not, I suggest this bugreport into a wishlist request for support
for optionally relaxing the permissions.


 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm


pgppW09holbwI.pgp
Description: PGP signature

Bug#379454: gcfilms: freezes during initialisation

[Xav]

Mohammed Adnène Trojette wrote:
> On Sun, Jul 23, 2006, Xav wrote:
> 
>>Package: gcfilms
>>Version: 6.1-2
>>Severity: grave
>>Justification: renders package unusable
>>
>>When I launch it, I get this :
>>
>>$ gcfilms 
>>*** unhandled exception in callback:
>>***   Can't locate object method "signal_connect" via package "GCFrame" at
>>/usr/bin/../share/gcfilms/lib/GCMainWindow.pm line 1796.
>>***  ignoring at /usr/bin/gcfilms line 121.
>>
>>This problem is solved by upgrading libgtk2-perl to the testing version 
>>(1:1.121-1)
> 
> 
> Which suite are you using? I see you are using gcfilms version 6.1-2 so
> you must already be using testing. I don't understand exactly where the
> bug stands. Using outdated versions crash but it is fixed in current
> versions, isn't it?
> 
> If so, I think the bug should be closed. What am I misunderstanding
> please?

In fact here I'm using a stable/testing mix. For everyone using this
configuration, I think you shoud fix the version relation for
libgtk2-perl, something like >=1:1.121-1 in your package control file.
That's all !

Thanks for your support.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#369116: python-gdchart: Status?

[Jonas Smedegaard]

rassign 369116 python-gdchart
retitle 369116 Someone wants gd1 removed beforer etch
thanks

On Sat, 12 Aug 2006 13:38:47 +0200 Pierre HABOUZIT wrote:

> rassign 369116 ftp.debian.org
> retitle 369116 RM: python-gdcart; RoQA: obsolete, superseeded by
> python-gdchart2 thanks

Please do not, with no further notice, convert a minor issue to a
request for removal of the package!


> On Mon, Aug 07, 2006 at 11:13:19AM +0200, Stefan Huehner wrote:
> > Package: python-gdchart
> > Followup-For: Bug #369116
> > 
> > 
> > Hi,
> > as i've seen no progress or comment on this bug?
> > 
> > Are there any objections to removing python-gdchart?

Sorry the the late response.

Yes, I object to removing python-gdchart, as it is *not* binary
compatible with python-gdchart2, and is used by moinmoin.


Who is this "we", by the way, that wants gd1 removed from the archive
before etch?

I am the maintainer of the the library itself and several libraries
depending on it. Where can I learn more on this initiative?

I am not against such initiative, but might have insight like the above
about obstacles on the path to reaching that goal.


Kind regards,

 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm


pgpDNOCtATvqU.pgp
Description: PGP signature

Bug#380863: diff for 0.0.4-0.1 NMU

[Pierre HABOUZIT]

Hi,

Attached is the diff for my mailping 0.0.4-0.1 NMU.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
diff -Nru /tmp/QSvvSpJbBA/mailping-0.0.4/debian/changelog 
/tmp/pbsCG6eQG9/mailping-0.0.4/debian/changelog
--- /tmp/QSvvSpJbBA/mailping-0.0.4/debian/changelog 2004-12-13 
21:08:19.0 +0100
+++ /tmp/pbsCG6eQG9/mailping-0.0.4/debian/changelog 2006-08-12 
13:48:51.0 +0200
@@ -1,3 +1,12 @@
+mailping (0.0.4-0.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Bump Standards-Version to 3.7.2.
+  * Update package to the last python policy (Closes: #380863).
+  * Move some things into B-D instead of B-D-I.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 13:45:40 +0200
+
 mailping (0.0.4) unstable; urgency=low
 
   * Skip temporary files when processing the pending directory.
diff -Nru /tmp/QSvvSpJbBA/mailping-0.0.4/debian/control 
/tmp/pbsCG6eQG9/mailping-0.0.4/debian/control
--- /tmp/QSvvSpJbBA/mailping-0.0.4/debian/control   2004-12-13 
21:07:59.0 +0100
+++ /tmp/pbsCG6eQG9/mailping-0.0.4/debian/control   2006-08-12 
13:50:06.0 +0200
@@ -2,8 +2,9 @@
 Section: mail
 Priority: optional
 Maintainer: Tommi Virtanen <[EMAIL PROTECTED]>
-Standards-Version: 3.5.6
-Build-Depends-Indep: python-dev, cdbs, debhelper (>= 4.1.68), xsltproc, 
docbook-xml, docbook-xsl
+Standards-Version: 3.7.2
+Build-Depends: cdbs, debhelper (>= 4.1.68), python-dev
+Build-Depends-Indep: xsltproc, docbook-xml, docbook-xsl, python-support (>= 
0.4.0)
 
 Package: mailping
 Architecture: all
diff -Nru /tmp/QSvvSpJbBA/mailping-0.0.4/debian/pyversions 
/tmp/pbsCG6eQG9/mailping-0.0.4/debian/pyversions
--- /tmp/QSvvSpJbBA/mailping-0.0.4/debian/pyversions1970-01-01 
01:00:00.0 +0100
+++ /tmp/pbsCG6eQG9/mailping-0.0.4/debian/pyversions2006-08-12 
13:50:18.0 +0200
@@ -0,0 +1 @@
+2.3-
diff -Nru /tmp/QSvvSpJbBA/mailping-0.0.4/debian/rules 
/tmp/pbsCG6eQG9/mailping-0.0.4/debian/rules
--- /tmp/QSvvSpJbBA/mailping-0.0.4/debian/rules 2004-04-16 17:42:21.0 
+0200
+++ /tmp/pbsCG6eQG9/mailping-0.0.4/debian/rules 2006-08-12 13:45:01.0 
+0200
@@ -2,8 +2,9 @@
 # -*- mode: makefile; coding: utf-8 -*-
 # Copyright © 2002,2003 Colin Walters <[EMAIL PROTECTED]>
 
-include /usr/share/cdbs/1/rules/debhelper.mk
+## YES I do want debhelper to be after distutils.mk
 include /usr/share/cdbs/1/class/python-distutils.mk
+include /usr/share/cdbs/1/rules/debhelper.mk
 
 DEB_INSTALL_DOCS_mailping := doc/*
 DEB_DH_ALWAYS_EXCLUDE := .svn
@@ -15,6 +16,9 @@
 install/mailping::
cd man && ./run
 
+binary-install/mailping::
+   dh_pysupport
+
 DEB_INSTALL_MANPAGES_mailping := $(patsubst %.xml,%,$(wildcard 
man/*.[0-9].xml))
 
 clean::


signature.asc
Description: Digital signature

Bug#382626: gweather: Iraq locations do not have working weather reports

[Ryan Lackey]

Package: gnome-applets
Version: 2.14.3-1
Severity: minor


gweather includes several locations in Iraq, but weather reports for 
each are unavailable.  There is now weather reporting from BIAP, found
on sites such as weather.com, so having the weather reports fixed would
be great.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.18
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gnome-applets depends on:
ii  debconf [debconf-2.0]  1.5.3 Debian configuration management sy
ii  gconf2 2.14.0-4  GNOME configuration database syste
ii  gnome-applets-data 2.14.3-1  Various applets for GNOME 2 panel 
ii  gnome-icon-theme   2.14.2-1  GNOME Desktop icon theme
ii  gnome-panel2.14.3-1  launcher and docking facility for 
ii  gstreamer0.10-alsa 0.10.9-1  GStreamer plugin for ALSA
ii  gstreamer0.10-plugins-good 0.10.3-2  GStreamer plugins from the "good" 
ii  libapm13.2.2-8   Library for interacting with APM d
ii  libatk1.0-01.12.1-1  The ATK accessibility toolkit
ii  libbonobo2-0   2.14.0-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.14.0-4  The Bonobo UI library
ii  libc6  2.3.6-19  GNU C Library: Shared libraries
ii  libcairo2  1.2.2-1   The Cairo 2D vector graphics libra
ii  libdbus-1-20.62-4simple interprocess messaging syst
ii  libdbus-glib-1-2   0.62-4simple interprocess messaging syst
ii  libfontconfig1 2.3.2-7   generic font configuration library
ii  libgconf2-42.14.0-4  GNOME configuration database syste
ii  libglade2-01:2.6.0-2 library to load .glade files at ru
ii  libglib2.0-0   2.10.3-3  The GLib library of C routines
ii  libgnome-desktop-2 2.14.3-1  Utility library for loading .deskt
ii  libgnome2-02.14.1-3  The GNOME 2 library - runtime file
ii  libgnomeui-0   2.14.1-2  The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 2.14.2-1  GNOME virtual file-system (runtime
ii  libgstreamer-plugins-base0 0.10.9-1  GStreamer libraries from the "base
ii  libgstreamer0.10-0 0.10.9-1  Core GStreamer libraries and eleme
ii  libgtk2.0-02.8.18-7  The GTK+ graphical user interface 
ii  libgtop2-7 2.14.2-2  gtop system monitoring library
ii  libgucharmap4  1:1.6.0-1 Unicode browser widget library (sh
ii  libhal10.5.7-2   Hardware Abstraction Layer - share
ii  libnotify1 0.4.0-1   sends desktop notifications to a n
ii  liborbit2  1:2.14.0-2libraries for ORBit2 - a CORBA ORB
ii  libpanel-applet2-0 2.14.3-1  library for GNOME 2 panel applets
ii  libpango1.0-0  1.12.3-1+b1   Layout and rendering of internatio
ii  libwnck18  2.14.3-1  Window Navigator Construction Kit 
ii  libx11-6   2:1.0.0-8 X11 client-side library
ii  libxcursor11.1.5.2-5 X cursor management library
ii  libxext6   1:1.0.0-4 X11 miscellaneous extension librar
ii  libxfixes3 1:3.0.1.2-4   X11 miscellaneous 'fixes' extensio
ii  libxi6 1:1.0.0-5 X11 Input extension library
ii  libxinerama1   1:1.0.1-4 X11 Xinerama extension library
ii  libxklavier10  2.2-3 X Keyboard Extension high-level AP
ii  libxml22.6.26.dfsg-3 GNOME XML library
ii  libxrandr2 2:1.1.0.2-4   X11 RandR extension library
ii  libxrender11:0.9.0.2-4   X Rendering Extension client libra

Versions of packages gnome-applets recommends:
ii  deskbar-applet   2.14.2-4universal search and navigation ba
ii  gnome-media  2.14.2-1GNOME media utilities
ii  gnome-netstatus-appl 2.12.0-5Network status applet for GNOME 2
ii  gnome-system-monitor 2.14.5-1Process viewer and system resource
ii  imagemagick  7:6.2.4.5.dfsg1-0.9 Image manipulation programs

-- debconf information:
  gnome-applets/cpufreq_SUID_bit: false


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#329387: [bugzilla #329387] new sarge package that fixes CVE-2005-4534

[Martin Schulze]

Alexis Sukrieh wrote:
> Moritz Muehlenhoff wrote:
> >The distribution should be stable-security instead of 
> >testing-proposed-updates. Please also remove all the i18n updates:
> 
> Ok, I'll make a new package with the correct distribution.
> 
> The i18n updates are automatically made by the build process, it's only 
> timtestamp updates, how can I safely disable this?

You simply build the source package before you are working on the
binary package and don't build the source package after you've built
the binary packages.

Regards,

Joey

-- 
Long noun chains don't automatically imply security.  -- Bruce Schneier

Please always Cc to me when replying to me on the lists.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382597: clamav-freshclam calls start_daemon in a way that fails

[Chris Lawrence]

On 8/12/06, Stephen Gran <[EMAIL PROTECTED]> wrote:

This one time, at band camp, Chris Lawrence said:
> >
> >[EMAIL PROTECTED]:/home/joey>/etc/init.d/clamav-freshclam start
> >+ start_daemon /usr/bin/freshclam -p /var/run/clamav/freshclam.pid -d
> >--quiet
> >+ local force nice pidfile exec i
> >+ force=0
> >+ nice=0
> >+ pidfile=/dev/null
> >+ getopts fn:p: opt
> >+ shift 2
> >+ '[' /var/run/clamav/freshclam.pid = -- ']'
> >+ exec=/var/run/clamav/freshclam.pid
> >+ shift
> >+ '[' 0 = 1 ']'
> >+ '[' /dev/null ']'
> >+ /sbin/start-stop-daemon --start --nicelevel 0 --quiet --exec
> >/var/run/clamav/freshclam.pid --oknodo --pidfile /dev/null -- -d --quiet
> >
> >If this is a bug in clamav-freshclam for passing the daemon to start before
> >the options, please reassign the bug; I haven't checked the LSB and this
> >package doesn't seem to bother to document start_daemon's syntax
> >internally.
>
> The LSB does require that all options be specified before the
> executable name; I am revising README.Debian in lsb-base to include
> documentation of all of the functions.

The command line options are options to be passed to freshclam on
startup, on the right side of the -- in the s-s-d call.  They are not
arguments to start_daemon.

The problem here is that the clamav init scripts use other functions
from lsb before running start_daemon, and OPTIND is still > 1 in the
second call.  This makes the getopt run in start_daemon do the wrong
thing, and it misparses the arguments.  I have worked around this in
the clamav init scripts by manually setting OPTIND=1 before each
invocation of start_daemon (as that's the only function where ordering
matters).

Joey, can you please test that 0.88.4-2 works correctly for you?  It
does here, but I wouldn't mind a second set of eyes on it.

Chris, can you take a look at the patch in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381822;msg=15;att=0 and
see if that looks OK?  It sets OPTIND before each getopt call to avoid
these issues, and it also cleans up the remaining mistakes in my
original patch to you.


Er, I think that was already fixed, although it wasn't in -12 (which
is the version Joey reported the issue in).  Maybe I forgot to upload
-13 (which is dated Wednesday here)?

In any event, I am 99.9% sure it's fixed in -14, which I definitely uploaded.

As for clamav, I'd just depend on 3.1-13 or later, rather than
fiddling with OPTIND.


Chris


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#279168: closed by Chris Lawrence <[EMAIL PROTECTED]> (Fixed)

[Chris Lawrence]

reopen 279168
severity 279168 normal
reassign 279168 reportbug, debbugs
retitle 279168: reportbug needs a direct (HTTP?) submission interface to the BTS
thanks

On 8/12/06, Albert Cahalan <[EMAIL PROTECTED]> wrote:

On 8/12/06, Chris Lawrence <[EMAIL PROTECTED]> wrote:

> More to the point, this is a general issue with all MUAs that depend
> on an MTA to accomplish delivery for them, and (IMHO) loading down
> reportbug with functionality that is only necessary to diagnose
> people's broken mail systems wouldn't be a very good tradeoff.

So an MTA is not allowed to have a bug? :-)


Sure... it's just not reportbug's job to figure out if your MTA has a
bug, any more than it's mutt's or Thunderbird's or Evolution's or
mailx's.


Spam filters seem to eat half the legit email these days.
There might be several on the path to bugs.debian.org.


True enough.


Supposing that the MTA is indeed misconfigured by the
user's own action (can not blame Debian config), so what?
It's still important to deliver the bug report. There is no
need for reportbug to diagnose broken mail systems; there
is only a need to deliver the bug report if at all possible
and ensure that silent failure can never happen. Feel free
to tell the user "It looks like the email was eaten by a grue."
before offering to try some other method.


The problem is that there's no deterministic way for reportbug (or any
MUA) to find out whether a mail was ever delivered to its ultimate
endpoint - SMTP just doesn't work that way.  And the BTS works
asynchronously, so there's no way to tell the user definitively "your
email was eaten by a grue" - bugs.d.o could just be having a bad day.


> You may reopen the report, but it will probably be downgraded and
> marked wontfix.

Please do reopen it.


I sense a pronoun shift here.  I don't consider this a bug, at least
not one in reportbug per se.

That said, some sort of way to send some nicely formatted XML
describing a bug report to bugs.debian.org via a HTTP POST request
would be nice.  Considering that I've never convinced the BTS
developers to implement any sort of XML output (which would radically
simplify the BTS parsing code and would curtail weird breakage every
time they fiddle with the web page generation), however, I doubt
they're in any hurry to do input either.


Chris
--
Chris Lawrence - http://blog.lordsutch.com/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380905: diff for 0.9.6-4.1 NMU

[Pierre HABOUZIT]

Hi,

Attached is the diff for my pyg 0.9.6-4.1 NMU.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
diff -Nru /tmp/dvoUgNgmSb/pyg-0.9.6/debian/changelog 
/tmp/9DasJMn1R4/pyg-0.9.6/debian/changelog
--- /tmp/dvoUgNgmSb/pyg-0.9.6/debian/changelog  2004-03-02 21:42:37.0 
+0100
+++ /tmp/9DasJMn1R4/pyg-0.9.6/debian/changelog  2006-08-12 14:04:48.0 
+0200
@@ -1,3 +1,12 @@
+pyg (0.9.6-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update package to the last python policy (Closes: #380905).
+  * Bump DH_COMPAT to 4.
+  * Bump Standards-Version to 3.7.2.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 14:01:38 +0200
+
 pyg (0.9.6-4) unstable; urgency=low
 
   * added some more header to be stripepd in mail2news class
@@ -188,6 +197,3 @@
 
  -- Cosimo Alfarano <[EMAIL PROTECTED]>  Sun, 25 Jun 2000 17:52:35 +0200
 
-Local variables:
-mode: debian-changelog
-End:
diff -Nru /tmp/dvoUgNgmSb/pyg-0.9.6/debian/control 
/tmp/9DasJMn1R4/pyg-0.9.6/debian/control
--- /tmp/dvoUgNgmSb/pyg-0.9.6/debian/control2003-11-05 12:03:38.0 
+0100
+++ /tmp/9DasJMn1R4/pyg-0.9.6/debian/control2006-08-12 14:04:42.0 
+0200
@@ -2,12 +2,12 @@
 Section: news
 Priority: optional
 Maintainer: Cosimo Alfarano <[EMAIL PROTECTED]>
-Standards-Version: 3.6.1.0
-Build-Depends: debhelper (>= 3.0), python-dev (>= 2.1), flex, bison
+Standards-Version: 3.7.2
+Build-Depends: debhelper (>= 3.0), python-dev (>= 2.1), flex, bison, 
python-support (>= 0.4.0)
 
 Package: pyg
 Architecture: any
-Depends: python (>= 2.1)
+Depends: ${python:Depends}
 Suggests: news-transport-system , mail-transport-agent, procmail
 Description: Python Mail <-> News Gateway
  Python Gateway Script from news to mail and vice versa.
diff -Nru /tmp/dvoUgNgmSb/pyg-0.9.6/debian/rules 
/tmp/9DasJMn1R4/pyg-0.9.6/debian/rules
--- /tmp/dvoUgNgmSb/pyg-0.9.6/debian/rules  2001-11-12 23:24:19.0 
+0100
+++ /tmp/9DasJMn1R4/pyg-0.9.6/debian/rules  2006-08-12 14:03:20.0 
+0200
@@ -5,7 +5,7 @@
 #export DH_VERBOSE=1
 
 # This is the debhelper compatability version to use.
-export DH_COMPAT=3
+export DH_COMPAT=4
 
 export package=pyg
 export debdestdir=$(CURDIR)/debian/$(package)
@@ -59,6 +59,8 @@
 
# dh_fixperms doesn't fix perms in /usr/share/doc subdirs
find $(debdestdir)/usr/share/doc/$(package) -type d -exec chmod 0755 {} 
\;
+
+   dh_pysupport

dh_strip
dh_compress


signature.asc
Description: Digital signature

Bug#382605: partman-crypto not entirely localized

[Christian Perrier]

Quoting Miroslav Kure ([EMAIL PROTECTED]):
> Package: partman-crypto
> Severity: minor
> Tags: l10n, patch
> 
> Hi,
> 
> the template partman-crypto/text/erase_data (_Description: Erase data:)
> does not have its choices (yes/no) localizable. Please apply something
> like the attached (untested) patch.


As long as l10n is concerned, I'm OK with that patch.



signature.asc
Description: Digital signature

Bug#377757: forgotten patches

[Corey Wright]

ok, so i'm an idiot and somehow forgot to attach the referenced patches.

for historical record here are the patches that should have been attached
to my original email.

corey
-- 
[EMAIL PROTECTED]
--- scsi-layer.c.orig	2006-07-09 11:13:36.0 -0500
+++ scsi-layer.c	2006-07-10 23:26:57.0 -0500
@@ -209,12 +209,16 @@ static int query_type(DeviceHandle *dh, 
   case  0: 
   {  int layer_type = buf[6] & 0x0f;
 
+	 if(layer_type == 0x01)
+dh->typedescr = "DVD-ROM";
+	 else
 	 if(layer_type & 0x06) 
 	dh->typedescr = "DVD-ROM (faked book type)";
 	 else
 	 {  dh->typedescr = "DVD-ROM";
 	dh->subType = UNSUPPORTED;
 	 }
+	 }
 	 break;
   }
 
--- scsi-layer.c.orig	2006-07-10 23:26:57.0 -0500
+++ scsi-layer.c	2006-07-10 23:31:00.0 -0500
@@ -1034,10 +1034,12 @@ DeviceHandle* OpenAndQueryDevice(char *d
   }
}
 
+/*
if(dh->mainType == DVD && query_copyright(dh))
{  CloseDevice(dh);
   Stop(_("This software does not support encrypted media.\n"));
}
+*/
 
if(dh->sessions>1)
{  int sessions = dh->sessions;

Bug#382314: [pkg-wpa-devel] Bug#382314: Need to scramble wpa-psk? Apparently yes, but not obvious

[Eduard Bloch]

#include 
* Kel Modderman [Sat, Aug 12 2006, 07:39:31PM]:
> Hi Eduard,

> > Then I decided to play with the tools mentioned in README.modes.gz, I
> > used wpa_passphrase, passed my essid and the old psk to it and it threw
> > me some new key inside of a "config section". When I added this new key
> > as wpa-psk in the interfaces file, it worked.
> 
> Your key is a plaintext passphrase; did you wrap it in quotes like:
> 
> wpa-psk "passphrase"

I have not used quotes since there we nothing but ascii letters/numbers.
And even then, README.notes explcitely says "without quotes".

> or use the special wpa-passphrase option:
> 
> wpa-passphrase passphrase

Oh, yes, that is the option I needed in fact. Why have I not discovered
it before? Simply because the first example in README.notes does not
contain it and the difference is not obvious. I guess this is not
obvious from your point of view, but you know all the details but a NEW
USER does not.

So, I suggest that wpasupplicant warns if the psk does not look like a
hexadezimal string! This is a simple method to catch such cases. And
that an error message appears, aka becomes _visible_ in the output,
saying what happened, something like:

PSK KEY CHECK FAILED (psk with non-hexadecimal chars, confused with passhrase?)
CIPHER NEGOTIATION FAILED (missing cipher driver)

And at least Debian's documentation clearly distinguishes between the
key and the key (err, psk used for psk mode vs. passphrase).

> > I can only ASSUME that the programers decided to switch from a plaintext
> > pass phrase to a scrambled form. But in this case, DOCUMENT THE CHANGE
> > ON VISIBLE PLACES. Sorry, that's the minimum requirement for
> > user-friendlines.
> 
> 
> Please advise how we can help improve user friendliness without using 
> provocative language. However, I can understand your frustration, I once had 
> similar experiences with this very piece of software (and its lack of user 
> friendliness).

Okay, see my attached patch for Debian docs.

In addition, I have the suggestion for upstream to print clearly visible
error messages with advices for users instead of hidding them somewhere
in the debug logs which you can get with -d only and which you
need to filter with your mind from different internal log noise.

And I suggest to change the manpage of wpa_passphrase:

| wpa_passphrase - Set WPA passphrase for a SSID

Wrong. It does not set anything. It just generates a config snippet
AFAICS.
Better: "generates WPA-PSK configuration for a SSID/passphrase pair". 

To OVERVIEW, add an explanation sentense: "The passphrase and SSID are
scrambled to generate a hexadezimal representation of the preshared
key."

> I will do, to the best of my ability, what is required to enhance the 
> user-friendliness quality of wpasupplicant, but first the problem areas need 
> to be clearly identified. What specifically is required to satisfy your 
> experiences with wpasupplicant?
> 
> Are you frustrated at our ifupdown.sh program and documentation? Or the 
> upstream documentation? Or both?

Well, both. Your documentation is good, but a bit hard to overview. See
below. About upstream docs, it is not user-friendly. Look at the manpage of
wpa_supplicant. There is a quick-start chapter, but how long do you need
to actually find that quick-start chapter? I would do following changes
(no idea whether you or upstream would like to do that)...

wpa_supplicant: 

OVERVIEW. Three screens, far too long. Full of technical details that
only few users need to know in that depth. Hard to extract the
information that you need for initial configuration. I would move the
chapter to the bottom and rename it to "TECHNICAL OVERVIEW". Or maybe
moved to wpa_background manpage.  For a normal setup, I would begin with
an OVERVIEW chapter with just few sentenses:

"
| wpa_supplicant is a helper application used to establish secure
| connection trough wireless interfaces using an encryption mechanism
| known as WPA (a variant of IEEE 802.1X standard). wpa_supplicant
| supports various WPA modes: the simple mode with a preshared key (aka
| WPA-PSK or "WPA-Personal"), WPA with user authentication (EAP, see
| "TECHNICAL OVERVIEW" for details).
| 
| From application view, wpa_supplicant is a background daemon, watching
| the state of an interface and communicating with the peer about WPA
| related issues.
| 
| Several WiFi drivers on Linux and BSD do support WPA encryption: hostap,
| hermes, madwifi, atmel, wext (generic, recommended), ndiswrapper,
| broadcom, ipw, wired, bsd (generic, recommended), ndis. See SUPPORTED
| DRIVERS below for detailed explanation.
"

SUPPORTED FEATURES. Three screens listing every submode. Do I want to read
all that (unless I have trouble?)? Not really. The ones who care
will find that information either way. I would move the chapter to
bottom, together with "TECHNICAL OVERVIEW".

"AVAILABLE DRIVERS" and "SUPPORTED DRIVERS" - merge those chapters and
move the result to somewhere below COMMA

Bug#373316: diff for 2.4.4-2.1 NMU

[Junichi Uekawa]

Hi,


+ecasound2.2 (2.4.4-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update Build-Depends for kfreebsd-amd64 (Closes: #361469).
+  * Simplify Build-Depends as well.
+  * Update to the last python policy (Closes: #373316).
+  * Bump Standards-Version to 3.7.2.
+  * python-ecasound2.2 is an arch:all package.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 12:30:52 +0200
+



NAK,

changes too many things at once without related bugs.


regards,
junichi
-- 
[EMAIL PROTECTED],netfort.gr.jp}   Debian Project


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382631: aptitude: should make tasks behave like metapackages

[Kim Krecht]

Package: aptitude
Version: 0.4.1-1.1
Severity: wishlist


aptitude should make tasksel tasks as easily trackable as metapackages:

- Packages being installed as a result of selection of one or more tasks 
  should be marked as "automatically installed". Furthermore, aptitude 
  should not automatically remove a package if it is marked as 
  "automatically installed", but a task depending on it is still 
  installed.
- When packages are added to a task, they should be marked for 
  "automatic installation" and thus be installed. Not having one or more 
  dependencies of a task installed should result in "break"ing the task, 
  calling for aptitude's problem resolution.

These changes would also lead to the following desired behaviour:

- When packages are removed from a task, they are also being removed 
  from the system given that no other packages or tasks depend on them 
  and that they have not been set to "manually installed".

I hope, I have made my intentions clear and laid out the most important 
implications of this wishlist item. I did hear that some support for 
this functionality already were in aptitude, but could not find it in 
the darcs repository.

TIA,
Kim~*

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3.1 0.6.45 Advanced front-end for dpkg
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libgcc1   1:4.1.1-5  GCC support library
ii  libncursesw5  5.5-2  Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a2.0.16-3   type-safe Signal Framework for C++
ii  libstdc++64.1.1-5The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do  (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382629: gtranslator: Please update the Hebrew translation mailing list

[Lior Kaplan]

Package: gtranslator
Version: 1.1.6-4
Severity: wishlist
Tags: patch l10n

--- /tmp/languages.c2006-08-12 15:32:06.0 +0300
+++ gtranslator-1.1.6/src/languages.c   2006-08-12 15:32:26.0 +0300
@@ -151,7 +151,7 @@
},
{
 N_("Hebrew"), "he", "UTF-8",
-"", "8bit"
+"[EMAIL PROTECTED]", "8bit"
},
{
 N_("Hindi"), "hi", "UTF-8",

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gtranslator depends on:
ii  libart-2.0-2   2.3.17-1  Library of functions for 2D graphi
ii  libaspell150.60.4-4  GNU Aspell spell-checker runtime l
ii  libatk1.0-01.12.1-1  The ATK accessibility toolkit
ii  libbonobo2-0   2.14.0-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.14.0-4  The Bonobo UI library
ii  libc6  2.3.6-19  GNU C Library: Shared libraries
ii  libcairo2  1.2.2-1   The Cairo 2D vector graphics libra
ii  libfontconfig1 2.3.2-7   generic font configuration library
ii  libgconf2-42.14.0-4  GNOME configuration database syste
ii  libglib2.0-0   2.10.3-3  The GLib library of C routines
ii  libgnome-keyring0  0.4.9-1   GNOME keyring services library
ii  libgnome2-02.14.1-3  The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.14.0-2  A powerful object-oriented display
ii  libgnomeui-0   2.14.1-2  The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 2.14.2-1  GNOME virtual file-system (runtime
ii  libgtk2.0-02.8.18-7  The GTK+ graphical user interface 
ii  libgtkspell0   2.0.10-3+b1   a spell-checking addon for GTK's T
ii  libice61:1.0.0-3 X11 Inter-Client Exchange library
ii  liborbit2  1:2.14.0-2libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0  1.12.3-1+b1   Layout and rendering of internatio
ii  libpopt0   1.10-3lib for parsing cmdline parameters
ii  libsm6 1:1.0.0-4 X11 Session Management library
ii  libx11-6   2:1.0.0-8 X11 client-side library
ii  libxcursor11.1.5.2-5 X cursor management library
ii  libxext6   1:1.0.0-4 X11 miscellaneous extension librar
ii  libxi6 1:1.0.0-5 X11 Input extension library
ii  libxinerama1   1:1.0.1-4 X11 Xinerama extension library
ii  libxml22.6.26.dfsg-3 GNOME XML library
ii  libxrandr2 2:1.1.0.2-4   X11 RandR extension library
ii  libxrender11:0.9.0.2-4   X Rendering Extension client libra
ii  zlib1g 1:1.2.3-13compression library - runtime

gtranslator recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382633: linux-kernel-di-powerpc-2.6: Please support the native ppc64 port

[Andreas Jochens]

Package: linux-kernel-di-powerpc-2.6
Version: 1.19
Severity: wishlist
Tags: patch

Hello,

the attached patch adds support for the native ppc64 port to the
linux-kernel-di-powerpc-2.6 package.

The patch adds an additional line for the native ppc64 kernel
to the 'kernel-versions' file.

The patch also creates a new 'modules/ppc64' directory with 
module files that just include the module files from the 
modules/powerpc-powerpc64 directory.

Regards
Andreas Jochens

diff -urN ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/kernel-versions 
./kernel-versions
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/kernel-versions
2006-06-28 13:25:26.0 +
+++ ./kernel-versions   2006-08-12 05:37:13.0 +
@@ -2,3 +2,4 @@
 powerpc  2.6.16-2 powerpc  2.6.16-2-powerpc-   
linux-image-2.6.16-2-powerpc
 powerpc  2.6.16-2 powerpc642.6.16-2-powerpc64  -   
linux-image-2.6.16-2-powerpc64
 powerpc  2.6.16-2 powerpc-miboot   2.6.16-2-powerpc-miboot -   
linux-image-2.6.16-2-powerpc-miboot
+ppc642.6.16-2 ppc642.6.16-2-ppc64  -   
linux-image-2.6.16-2-ppc64
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/affs-modules 
./modules/ppc64/affs-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/affs-modules 
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/affs-modules2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/affs-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/cdrom-core-modules 
./modules/ppc64/cdrom-core-modules
--- 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/cdrom-core-modules   
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/cdrom-core-modules  2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/cdrom-core-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/crypto-modules 
./modules/ppc64/crypto-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/crypto-modules   
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/crypto-modules  2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/crypto-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/ext2-modules 
./modules/ppc64/ext2-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/ext2-modules 
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/ext2-modules2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/ext2-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/ext3-modules 
./modules/ppc64/ext3-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/ext3-modules 
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/ext3-modules2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/ext3-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/fat-modules 
./modules/ppc64/fat-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/fat-modules  
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/fat-modules 2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/fat-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/firewire-core-modules
 ./modules/ppc64/firewire-core-modules
--- 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/firewire-core-modules
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/firewire-core-modules   2006-08-12 05:38:15.0 
+
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/firewire-core-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/firmware-modules 
./modules/ppc64/firmware-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/firmware-modules 
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/firmware-modules2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/firmware-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/floppy-modules 
./modules/ppc64/floppy-modules
--- ../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/floppy-modules   
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/floppy-modules  2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/floppy-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/fs-common-modules 
./modules/ppc64/fs-common-modules
--- 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/fs-common-modules
1970-01-01 00:00:00.0 +
+++ ./modules/ppc64/fs-common-modules   2006-08-12 05:38:15.0 +
@@ -0,0 +1 @@
+#include "../powerpc-powerpc64/fs-common-modules"
diff -urN 
../tmp-orig/linux-kernel-di-powerpc-2.6-1.19/modules/ppc64/

Bug#382597: clamav-freshclam calls start_daemon in a way that fails

[Stephen Gran]

This one time, at band camp, Chris Lawrence said:
> Er, I think that was already fixed, although it wasn't in -12 (which
> is the version Joey reported the issue in).  Maybe I forgot to upload
> -13 (which is dated Wednesday here)?
> 
> In any event, I am 99.9% sure it's fixed in -14, which I definitely 
> uploaded.

I grabbed -14 from incoming, and it's listed as fixed in -13, but -13
never hit my local mirror.  Either way, it's fixed now.

> As for clamav, I'd just depend on 3.1-13 or later, rather than
> fiddling with OPTIND.

I'm of two minds here - it makes backports harder, but it is also the
right thing to do.  I'll look into it a little later when I have some
more time.

Thanks again,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :[EMAIL PROTECTED] |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#382604: zaptel: fails by post-install

[Mark Purcell]

Christoph,

On Saturday 12 August 2006 12:48, Christoph Kaminski wrote:
> 01:06.0 Network controller: Cologne Chip Designs GmbH ISDN network
> controller [HFC-PCI] (rev 02)

Thanks I think this is the nub of the problem.

Unfortunately I don't have access to ISDN hardware so won't be able to debug 
too well remotely.

> cat /etc/zaptel.conf
> # hfc-s pci a span definition
> # most of the values should be bogus because we are not really zaptel
> loadzone=nl
> defaultzone=nl
>
> span=1,1,3,ccs,ami
> bchan=1-2
> dchan=3

This isn't shipped by the zaptel package, but is used by the package to gain 
configuration details.. Did you provide this config yourself? OR did it come 
with the hardware.

> Zaptel cards initial configuration: ZT_SPANCONFIG failed on span 1: 
> Invalid argument (22)

It seems like the zaptel startup doesn't like the span=1,1,3,ccs,ami from your 
config file.  Did this work with previous versions?

I suspect is is failing on the ztcgf(8) command:

Can you run:

# ztcfg  -vvvt

and forward the results.

Then I would suggest that you need to edit your modified zaptel.conf, until 
ztcfg does run correctly.

I might return to shipping the default zaptel.conf file under /etc so that 
when user mods are made it is brought to immediate attention.  Although the 
default doesn't cover a lot of cases, at least it is a starting point and 
changes will be aparent.

Also the genzaptelconf(8) script, might be able to assist with the 
regeneration of your zaptel.conf file, although we proably don't want to 
automate the running of that just yet.

Mark
Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382627: Building a cross-compiler for ia64 fails

[Christian 'Greek0' Aichinger]

Package: gcc-4.1
Version: 4.1.1-5
Severity: minor
Tags: patch

Hi,
I tried to build a cross-toolchain for ia64, but when compiling gcc
I got a linker error (log is attached).

After searching for some time I found that Herbert Pötzl had already
written a patch to solve this problem. I talked to him and he was
fine with me submitting the patch to the Debian BTS.

There are 2 patches attached, gcc-cross-fix-ia64.diff and apply-me.diff.
The former is Bertl's original patch fixed up for gcc 4.1, the
latter is diff-in-diff, it puts gcc-cross-fix-ia64 into
debian/patches (including dpatch header of course), and adds the
patch to debian_patches in debian/rules.patch.

HTH,
Christian Aichinger
diff -NurpP -x '*.orig' -x '*.libc' gcc-4.0.0.orig/gcc/config/ia64/fde-glibc.c 
gcc-4.0.0.new/gcc/config/ia64/fde-glibc.c
--- gcc-4.0.0.orig/gcc/config/ia64/fde-glibc.c  2003-11-02 18:35:20.0 
+0100
+++ gcc-4.0.0.new/gcc/config/ia64/fde-glibc.c   2005-05-15 02:42:27.675247674 
+0200
@@ -31,6 +31,7 @@
 #ifndef _GNU_SOURCE
 #define _GNU_SOURCE 1
 #endif
+#ifndef inhibit_libc
 #include "config.h"
 #include 
 #include 
@@ -162,3 +163,5 @@ _Unwind_FindTableEntry (void *pc, unsign
 
   return data.ret;
 }
+
+#endif
diff -NurpP -x '*.orig' -x '*.libc' 
gcc-4.0.0.orig/gcc/config/ia64/unwind-ia64.c 
gcc-4.0.0.new/gcc/config/ia64/unwind-ia64.c
--- gcc-4.0.0.orig/gcc/config/ia64/unwind-ia64.c2005-04-06 
05:50:36.0 +0200
+++ gcc-4.0.0.new/gcc/config/ia64/unwind-ia64.c 2005-05-15 02:43:10.842199954 
+0200
@@ -30,7 +30,7 @@
This exception does not however invalidate any other reasons why
the executable file might be covered by the GNU General Public License.  */
 
-
+#ifndef inhibit_libc
 #include "tconfig.h"
 #include "tsystem.h"
 #include "coretypes.h"
@@ -2404,3 +2404,4 @@ alias (_Unwind_SetIP);
 #endif
 
 #endif
+#endif
diff -NurpP -x '*.orig' -x '*.libc' gcc-4.0.0.orig/gcc/config/pa/linux-unwind.h 
gcc-4.0.0.new/gcc/config/pa/linux-unwind.h
--- gcc-4.0.0.orig/gcc/config/pa/linux-unwind.h 2005-02-11 02:46:20.0 
+0100
+++ gcc-4.0.0.new/gcc/config/pa/linux-unwind.h  2005-05-15 02:37:02.0 
+0200
@@ -29,6 +29,7 @@ Boston, MA 02111-1307, USA.  */
 /* Do code reading to identify a signal frame, and set the frame
state data appropriately.  See unwind-dw2.c for the structs.  */
 
+#ifndef inhibit_libc
 #include 
 #include 
 
@@ -136,3 +137,5 @@ pa32_fallback_frame_state (struct _Unwin
   fs->retaddr_column = DWARF_ALT_FRAME_RETURN_COLUMN;
   return _URC_NO_REASON;
 }
+
+#endif
diff -NurpP -x '*.orig' -x '*.libc' gcc-4.0.0.orig/gcc/config/sh/linux-unwind.h 
gcc-4.0.0.new/gcc/config/sh/linux-unwind.h
--- gcc-4.0.0.orig/gcc/config/sh/linux-unwind.h 2005-02-11 02:12:57.0 
+0100
+++ gcc-4.0.0.new/gcc/config/sh/linux-unwind.h  2005-05-15 02:44:31.0 
+0200
@@ -29,6 +29,7 @@ Boston, MA 02111-1307, USA.  */
 /* Do code reading to identify a signal frame, and set the frame
state data appropriately.  See unwind-dw2.c for the structs.  */
 
+#ifndef inhibit_libc
 #include 
 #include 
 #include "insn-constants.h"
@@ -169,3 +170,4 @@ sh_fallback_frame_state (struct _Unwind_
   return _URC_NO_REASON;
 }
 #endif /* defined (__SH5__) */
+#endif
diff -NurpP -x '*.orig' -x '*.libc' gcc-4.0.0.orig/gcc/unwind-compat.c 
gcc-4.0.0.new/gcc/unwind-compat.c
--- gcc-4.0.0.orig/gcc/unwind-compat.c  2004-09-04 02:15:40.0 +0200
+++ gcc-4.0.0.new/gcc/unwind-compat.c   2005-05-15 02:41:17.0 +0200
@@ -29,6 +29,7 @@
02110-1301, USA.  */
 
 #if defined (USE_GAS_SYMVER) && defined (USE_LIBUNWIND_EXCEPTIONS)
+#ifndef inhibit_libc
 #include "tconfig.h"
 #include "tsystem.h"
 #include "unwind.h"
@@ -204,3 +205,4 @@ _Unwind_SetIP (struct _Unwind_Context *c
 }
 symver (_Unwind_SetIP, GCC_3.0);
 #endif
+#endif
diff -NurpP -x '*.orig' -x '*.libc' gcc-4.0.0.orig/gcc/unwind-generic.h 
gcc-4.0.0.new/gcc/unwind-generic.h
--- gcc-4.0.0.orig/gcc/unwind-generic.h 2004-11-30 09:15:39.0 +0100
+++ gcc-4.0.0.new/gcc/unwind-generic.h  2005-05-15 02:38:33.0 +0200
@@ -202,6 +202,7 @@ extern _Unwind_Reason_Code _Unwind_SjLj_
compatible with the standard ABI for IA-64, we inline these.  */
 
 #ifdef __ia64__
+#ifndef inhibit_libc
 #include 
 
 static inline _Unwind_Ptr
@@ -220,6 +221,7 @@ _Unwind_GetTextRelBase (struct _Unwind_C
 
 /* @@@ Retrieve the Backing Store Pointer of the given context.  */
 extern _Unwind_Word _Unwind_GetBSP (struct _Unwind_Context *);
+#endif
 #else
 extern _Unwind_Ptr _Unwind_GetDataRelBase (struct _Unwind_Context *);
 extern _Unwind_Ptr _Unwind_GetTextRelBase (struct _Unwind_Context *);
diff -NurpP -x '*.orig' -x '*.libc' 
gcc-4.0.0.new/gcc/config/alpha/linux-unwind.h 
gcc-4.0.0.new2/gcc/config/alpha/linux-unwind.h
--- gcc-4.0.0.new/gcc/config/alpha/linux-unwind.h   2005-02-11 
02:12:54.0 +0100
+++ gcc-4.0.0.new2/gcc/config/alpha/linux-unwind.h  2005-05-15 
05:09:16.0 +0200
@@ -29,6 +29,7 @@ Boston, MA 02111-1307, USA.  */
 /* Do code rea

Bug#382632: pnet-assemblies: Depends on libgnutls12 but searches for libgnutls.so

[Andreas Metzler]

Package: pnet-assemblies
Version: 0.7.4-1
Severity: serious

pnet-assemblies depends on libgnutls12, even if it is built on a
current sid system where libgnutls-dev is the corresponding package to
libgnutls13.

However afaict pnet-assemblies does not use any file in either
libgnutls12 or libgnutls13, it tries to open the .so file.

-
(SID)[EMAIL PROTECTED]:/tmp/pnet-assemblies-0.7.4/build-tree/pnetlib-0.7.4$ 
./sam
ples/ilrun.sh samples/simple/sslfetch.exe https://db.debian.org/
Connecting to 192.25.206.57:443 ...
Uncaught exception: System.NotSupportedException: The requested feature is not 
supported
at DotGNU.SSL.OpenSSL..ctor() in ./OpenSSL.cs:58
at DotGNU.SSL.SessionProviderFactory.GetProvider(String) in 
./SessionProviderFactory.cs:77
at DotGNU.SSL.SessionProviderFactory.GetProvider() in 
./SessionProviderFactory.cs:101
at SSLFetch.Main(String[]) in ./sslfetch.cs:84
(SID)[EMAIL PROTECTED]:/tmp/pnet-assemblies-0.7.4/build-tree/pnetlib-0.7.4$ 
strace -eopen ./samples/ilrun.sh samples/simple/sslfetch.exe 
https://db.debian.org/ 2>&1 | grep /usr/lib/lib
open("/usr/lib/libz.so.1", O_RDONLY)= 3
open("/usr/lib/libgnutls.so", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/libssl.so", O_RDONLY)= -1 ENOENT (No such file or directory)
-

And indeed the command works after installing either libgnutls-dev or
libssl-dev which contain the .so symlink.

Either the dependency should be change accordingly or it should try to
open libgnutls.13.so and depend on libgnutls13. (Please do not se
libgnutls12, it is obsolete.)

cu andreas



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#373316: diff for 2.4.4-2.1 NMU

[Pierre Habouzit]

Le sam 12 août 2006 14:25, Junichi Uekawa a écrit :
> Hi,
>
>
> +ecasound2.2 (2.4.4-2.1) unstable; urgency=low
> +
> +  * Non-maintainer upload.
> +  * Update Build-Depends for kfreebsd-amd64 (Closes: #361469).
> +  * Simplify Build-Depends as well.
> +  * Update to the last python policy (Closes: #373316).
> +  * Bump Standards-Version to 3.7.2.
> +  * python-ecasound2.2 is an arch:all package.
> +
> + -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 12:30:52
> +0200 +
>
>
>
> NAK,
>
> changes too many things at once without related bugs.

> +  * Update Build-Depends for kfreebsd-amd64 (Closes: #361469).
  has a bug, was a matter of adding some exclusion of build, cannot harm

> +  * Simplify Build-Depends as well.
  you can revert that if yuou want.

> +  * Bump Standards-Version to 3.7.2.
  that is harmful, your package does comply, that's a statement for a
  fact, and does not risk to create bugs.

> +  * Update to the last python policy (Closes: #373316).
> +  * python-ecasound2.2 is an arch:all package.
  those should have been merged in the same item, the policy impose you
  to use arch:all for packages that only ship .py files.


-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpf17xkcuqmO.pgp
Description: PGP signature

Bug#382628: Status of debian-installer for the native ppc64 port

[Andreas Jochens]

Package: debian-installer
Version: 20060806
Severity: wishlist
Tags: patch


Hello Frans,

On 06-Aug-11 19:01, Frans Pop wrote:
> Please submit proposed patches for other d-i packages (or point me to 
> existing ones I've missed), please check that they apply and work with 
> current SVN repository.

thank you for this reminder. The ppc64 patches for the 
'debian-installer', 'linux-kernel-di-powerpc-2.6', 'base-installer'
and 'partman-base' packages were not filed to the BTS because I 
waited for the release of Beta 3.

The revised ppc64 patch for 'debian-installer' which should apply
to the current SVN is attached below. 

This patch adds 'ppc64' to the Build-Depends in debian/control where 
necessary and it creates the ppc64 related files in the build/config and 
build/pkg-lists directories.

The remaining ppc64 patches for the other d-i packages will follow soon.

Thank you again for your help with the integration of the ppc64 port!

Regards
Andreas Jochens

diff -urN 
../tmp-orig/debian-installer-20060806/build/config/ppc64/ppc64/cdrom64.cfg 
./build/config/ppc64/ppc64/cdrom64.cfg
--- ../tmp-orig/debian-installer-20060806/build/config/ppc64/ppc64/cdrom64.cfg  
1970-01-01 00:00:00.0 +
+++ ./build/config/ppc64/ppc64/cdrom64.cfg  2006-08-12 05:16:37.0 
+
@@ -0,0 +1 @@
+include config/powerpc/powerpc64/cdrom64.cfg
diff -urN 
../tmp-orig/debian-installer-20060806/build/config/ppc64/ppc64/netboot64.cfg 
./build/config/ppc64/ppc64/netboot64.cfg
--- 
../tmp-orig/debian-installer-20060806/build/config/ppc64/ppc64/netboot64.cfg
1970-01-01 00:00:00.0 +
+++ ./build/config/ppc64/ppc64/netboot64.cfg2006-08-12 05:16:37.0 
+
@@ -0,0 +1 @@
+include config/powerpc/powerpc64/netboot64.cfg
diff -urN ../tmp-orig/debian-installer-20060806/build/config/ppc64/ppc64.cfg 
./build/config/ppc64/ppc64.cfg
--- ../tmp-orig/debian-installer-20060806/build/config/ppc64/ppc64.cfg  
1970-01-01 00:00:00.0 +
+++ ./build/config/ppc64/ppc64.cfg  2006-08-12 06:30:50.0 +
@@ -0,0 +1,2 @@
+include config/powerpc/powerpc64.cfg
+KERNELVERSION = 2.6.16-2-ppc64
diff -urN ../tmp-orig/debian-installer-20060806/build/config/ppc64.cfg 
./build/config/ppc64.cfg
--- ../tmp-orig/debian-installer-20060806/build/config/ppc64.cfg
1970-01-01 00:00:00.0 +
+++ ./build/config/ppc64.cfg2006-08-12 05:16:37.0 +
@@ -0,0 +1,2 @@
+include config/powerpc.cfg
+SUBARCH_SUPPORTED = ppc64
diff -urN 
../tmp-orig/debian-installer-20060806/build/pkg-lists/cdrom64/ppc64.cfg 
./build/pkg-lists/cdrom64/ppc64.cfg
--- ../tmp-orig/debian-installer-20060806/build/pkg-lists/cdrom64/ppc64.cfg 
1970-01-01 00:00:00.0 +
+++ ./build/pkg-lists/cdrom64/ppc64.cfg 2006-07-25 22:48:21.0 +
@@ -0,0 +1,29 @@
+input-modules-${kernel:Version} [2.6]
+firewire-core-modules-${kernel:Version} [2.6]
+ide-modules-${kernel:Version}
+console-keymaps-at
+console-keymaps-usb
+#include "discover"
+kbd-chooser
+socket-modules-${kernel:Version} ?
+usb-modules-${kernel:Version}
+serial-modules-${kernel:Version}
+usb-serial-modules-${kernel:Version} ?
+# Currently all built into the kernel.
+#input-modules-${kernel:Version}
+#fb-modules-${kernel:Version}
+eject-udeb
+pcmcia-storage-modules-${kernel:Version}
+pcmcia-modules-${kernel:Version}
+pcmcia-cs-udeb [2.4]
+pcmciautils-udeb [2.6]
+floppy-modules-${kernel:Version}
+
+# Support for USB CD-ROMs
+usb-storage-modules-${kernel:Version}
+# Support for SCSI CD-ROMs on common controllers.
+scsi-common-modules-${kernel:Version}
+scsi-modules-${kernel:Version}
+
+hypervisor-modules-${kernel:Version}
+
diff -urN 
../tmp-orig/debian-installer-20060806/build/pkg-lists/netboot64/ppc64.cfg 
./build/pkg-lists/netboot64/ppc64.cfg
--- ../tmp-orig/debian-installer-20060806/build/pkg-lists/netboot64/ppc64.cfg   
1970-01-01 00:00:00.0 +
+++ ./build/pkg-lists/netboot64/ppc64.cfg   2006-07-25 22:48:20.0 
+
@@ -0,0 +1,29 @@
+input-modules-${kernel:Version} [2.6]
+firewire-core-modules-${kernel:Version} [2.6]
+console-keymaps-at
+console-keymaps-usb
+#include "discover"
+usb-discover
+nic-modules-${kernel:Version}
+nic-extra-modules-${kernel:Version}
+socket-modules-${kernel:Version} ?
+isa-pnp-modules-${kernel:Version} [2.4]
+nic-pcmcia-modules-${kernel:Version}
+pcmcia-modules-${kernel:Version}
+floppy-retriever
+pcmcia-cs-udeb [2.4]
+pcmciautils-udeb [2.6]
+floppy-modules-${kernel:Version}
+#fb-modules-${kernel:Version}
+usb-modules-${kernel:Version}
+serial-modules-${kernel:Version}
+usb-serial-modules-${kernel:Version} ?
+dhcp-client-udeb
+
+kbd-chooser
+bogl-bterm-udeb
+hw-detect
+ethdetect
+netcfg
+
+hypervisor-modules-${kernel:Version}
diff -urN ../tmp-orig/debian-installer-20060806/debian/control ./debian/control
--- ../tmp-orig/debian-installer-20060806/debian/control2006-07-30 
15:54:07.0 +
+++ ./debian/control2006-08-12 12:07:43.0 +
@@ -49,7 +49,7 @@
 #  

Bug#380941: diff for 0.18-0.2 NMU

[Pierre HABOUZIT]

Hi,

Attached is the diff for my scalemail 0.18-0.2 NMU.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/debian/changelog 
/tmp/l5oroVfimy/scalemail-0.18/debian/changelog
--- /tmp/5LMtVWdy1R/scalemail-0.18/debian/changelog 2006-07-19 
18:13:48.0 +0200
+++ /tmp/l5oroVfimy/scalemail-0.18/debian/changelog 2006-08-12 
14:20:49.0 +0200
@@ -1,3 +1,15 @@
+scalemail (0.18-0.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update package to the last python policy (Closes: #380941).
+  * Bump Standards-Version to 3.7.2.
+  * Build with default python.
+  * Add missing depends on adduser.
+  * Fix FSF address.
+  * Fix python2.3 shebangs, and ensure we at least build for python2.3.
+
+ -- Pierre Habouzit <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 14:10:48 +0200
+
 scalemail (0.18-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/debian/control 
/tmp/l5oroVfimy/scalemail-0.18/debian/control
--- /tmp/5LMtVWdy1R/scalemail-0.18/debian/control   2006-07-19 
18:12:14.0 +0200
+++ /tmp/l5oroVfimy/scalemail-0.18/debian/control   2006-08-12 
14:14:14.0 +0200
@@ -2,13 +2,13 @@
 Section: mail
 Priority: optional
 Maintainer: Tommi Virtanen <[EMAIL PROTECTED]>
-Standards-Version: 3.6.1
-Build-Depends: cdbs (>= 0.4.8.1), debhelper (>= 4.1.0), python, python2.3, 
python2.3-dev
+Standards-Version: 3.7.2
+Build-Depends: cdbs (>= 0.4.8.1), debhelper (>= 4.1.0), python-dev, 
python-support
 
 Package: scalemail
 Section: mail
 Architecture: all
-Depends: ${python:Depends}, python-twisted-core , python-twisted-mail , 
python-ldaptor , postfix (>= 0.0.20010329.SNAPSHOT), python-zopeinterface
+Depends: ${python:Depends}, python-twisted-core , python-twisted-mail , 
python-ldaptor , postfix (>= 0.0.20010329.SNAPSHOT), python-zopeinterface, 
adduser
 Suggests: courier-imap-ssl | courier-ssl, slapd
 Description: Scalable virtual mail domain system built on Postfix and LDAP
  A scalable (but not HA, at least not yet) virtual domain system for
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/debian/copyright 
/tmp/l5oroVfimy/scalemail-0.18/debian/copyright
--- /tmp/5LMtVWdy1R/scalemail-0.18/debian/copyright 2003-08-03 
12:32:07.0 +0200
+++ /tmp/l5oroVfimy/scalemail-0.18/debian/copyright 2006-08-12 
14:13:35.0 +0200
@@ -22,7 +22,9 @@
 
 You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
-Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
+MA 02110-1301, USA.
+
 
 On Debian Linux systems, the complete text of the GNU General Public
 License can be found in '/usr/share/common-licenses/GPL'.
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/debian/pyversions 
/tmp/l5oroVfimy/scalemail-0.18/debian/pyversions
--- /tmp/5LMtVWdy1R/scalemail-0.18/debian/pyversions1970-01-01 
01:00:00.0 +0100
+++ /tmp/l5oroVfimy/scalemail-0.18/debian/pyversions2006-08-12 
14:17:20.0 +0200
@@ -0,0 +1 @@
+2.3-
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/debian/rules 
/tmp/l5oroVfimy/scalemail-0.18/debian/rules
--- /tmp/5LMtVWdy1R/scalemail-0.18/debian/rules 2004-06-26 17:05:49.0 
+0200
+++ /tmp/l5oroVfimy/scalemail-0.18/debian/rules 2006-08-12 14:08:25.0 
+0200
@@ -1,7 +1,9 @@
 #!/usr/bin/make -f
 # -*- mode: makefile; coding: utf-8 -*-
 
-include /usr/share/cdbs/1/rules/debhelper.mk
+# YES THE SWITCH OF INCLUDE IS ITENTIONNAL
 include /usr/share/cdbs/1/class/python-distutils.mk
+include /usr/share/cdbs/1/rules/debhelper.mk
 
-DEB_PYTHON_COMPILE_VERSION = 2.3
+binary-install/scalemail::
+   dh_pysupport
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/scalemail-courier-login 
/tmp/l5oroVfimy/scalemail-0.18/scalemail-courier-login
--- /tmp/5LMtVWdy1R/scalemail-0.18/scalemail-courier-login  2005-01-17 
16:18:09.0 +0100
+++ /tmp/l5oroVfimy/scalemail-0.18/scalemail-courier-login  2006-08-12 
14:17:09.0 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/python2.3
+#!/usr/bin/python
 
 from scalemail.scripts import courier_login
 courier_login.run()
diff -Nru /tmp/5LMtVWdy1R/scalemail-0.18/scalemail-courier-login-mapper 
/tmp/l5oroVfimy/scalemail-0.18/scalemail-courier-login-mapper
--- /tmp/5LMtVWdy1R/scalemail-0.18/scalemail-courier-login-mapper   
2004-06-26 17:05:49.0 +0200
+++ /tmp/l5oroVfimy/scalemail-0.18/scalemail-courier-login-mapper   
2006-08-12 14:17:12.0 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/python2.3
+#!/usr/bin/python
 #
 #scalemail-courier-login-mapper - make Courier-IMAP match Scalemail 
accounts
 #Copyright (C) 2001  Tommi Virtanen <[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Bug#382630: inn: Could we get Python filtering hooks?

[Matej Cepl]

Package: inn
Version: 1:1.7.2debian-30
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I guess %subj% says it all. According to
http://www.eyrie.org/~eagle/software/inn/docs-2.3/hook-python.html
it shouldn't be that difficult (I don't how heavily are Debian
packages patched).

Thanks,

Matěj

- -- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc4.chelcicky.2
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)

Versions of packages inn depends on:
ii  cron  3.0pl1-95  management of regular background p
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libperl5.85.8.8-6.1  Shared Perl library
ii  perl  5.8.8-6.1  Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.8.4] 5.8.8-6.1  The Pathologically Eclectic Rubbis
ii  postfix [mail-transport-agent 2.2.10-2   A high-performance mail transport 
ii  time  1.7-21 The GNU time program for measuring

inn recommends no packages.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFE3csC4J/vJdlkhKwRAqblAKCGCVbjuVZo0PxBixZGgtMm9w/pnwCeLDV5
A2A7aV6Nikb7IfBQGcIvz7s=
=CO/z
-END PGP SIGNATURE-

Bug#382635: /etc/cron.daily/logrotate is looking in the wrong place

[sacrificial-spam-address]

Package: logrotate
Version: 3.7.1-3

.. for syslogd's pid.  It's checking /var/log/syslog.pid, when
/etc/init.d/sysklogd puts it in /var/run/syslog.pid.

This also causes /etc/cron.daily/logrotate to exit with status 1,
which was helpful in this case, but might not be in general.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382636: debian-history: DPLs information if outdated

[Nacho Barrientos Arias]

Package: debian-history
Version: 2.5
Severity: wishlist
Tags: patch

This bug report complements #305039.

The attached patch works against CVS revision 1.52 of 
ddp/manuals.sgml/project-history/project-history.sgml.

This patch adds information about Anthony Towns, the current
DPL.

Nacho

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.1
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)

-- no debconf information
--- project-history.sgml.orig   2006-08-12 14:17:22.0 +0200
+++ project-history.sgml2006-08-12 14:19:48.0 +0200
@@ -147,7 +147,12 @@
 until March 2005.
 
 
-Branden Robinson was elected in April 2005 and is our current leader.
+Branden Robinson was elected in April 2005 and held the leader position
+until March 2006.
+
+
+Anthony Towns was elected in April 2006 and is our current leader.
+
 
 
 

Bug#382637: ITP: pitchtune -- Precise Instrument Tweaking for Crispy Harmony tuner

[Ludovic RESLINGER]

Package: wnpp
Severity: wishlist
Owner: Ludovic RESLINGER <[EMAIL PROTECTED]>

* Package name: pitchtune
  Version : 0.0.4
  Upstream Author : Haakon Andre Hjortland <[EMAIL PROTECTED]>
* URL : http://pitchtune.sourceforge.net/
  Licence : GPLv2
  Programming Lang: C
  Description : Precise Instrument Tweaking for Crispy Harmony tuner

Cheers,
-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-


signature.asc
Description: Digital signature

Bug#359921: apt-proxy stalls on cache-misses (twisted 2.2 problem?)

[Toni Mueller]

Hello Chris,

On Fri, 11.08.2006 at 18:39:40 +0100, Chris Halls <[EMAIL PROTECTED]> wrote:
> Thanks for your bug report. 1.9.34 fixed a lot of problems in this code. Am I 
> right in thinking you cannot reproduce this problem in that version?

I think so, although I currently have some difficulty verifying that,
due to the twisted 2.4 problem. :-}


Best,
--Toni++



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]