echo+newline in postinst

2004-10-10 Thread Laszlo 'GCS' Boszormenyi
Hi,

 I have to write a newline along with other things to a config file from
postinst. I was told and discovered that echo -e '\nline' is not
supported in every shell. What would be the best solution for this? I
think I should use printf '\nline' as it seems to work in every shell.
Is it ok, or should I use an other solution? Like
'(echo; echo line) config_file'?

Regards,
Laszlo/GCS


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



Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Laszlo 'GCS' Boszormenyi
* martin f krafft [EMAIL PROTECTED] [2004-10-10 17:21:55 +0200]:

 also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.1706 +0200]:
  W: siefs source: configure-generated-file-in-source config.log
  W: siefs source: configure-generated-file-in-source config.status
  W: siefs source: configure-generated-file-in-source config.cache
  
  The mentioned files are in the upstream source and I'm uncertain
  whether to remove the files, ignore the warning or do something
  else about this. Any help is greatly appreciated.
 
 You cannot remove them from source or the orig.tar.gz won't be
 pristine anymore.
 I usually remove them from debian/rules clean: with rm -f
This helps for me.

 I suggest fixing the upstream autotools configuration to make these
 files properly delete and then to send the patch upstream.
 This would be the best, you are right.

Regards,
Laszlo/GCS


signature.asc
Description: Digital signature


Re: echo+newline in postinst

2004-10-10 Thread martin f krafft
also sprach Laszlo 'GCS' Boszormenyi [EMAIL PROTECTED] [2004.10.10.2241 +0200]:
 supported in every shell. What would be the best solution for
 this? I think I should use printf '\nline' as it seems to work
 in every shell.

Yes, this is supported by POSIX.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread martin f krafft
also sprach Laszlo 'GCS' Boszormenyi [EMAIL PROTECTED] [2004.10.10.2246 +0200]:
  I usually remove them from debian/rules clean: with rm -f This
  helps for me.

They will still be in the source package as patch does not by
default delete files.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Mathias Weidner
On Sun, Oct 10, 2004 at 05:21:55PM +0200, martin f krafft wrote:
 also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.1706 +0200]:
  W: siefs source: configure-generated-file-in-source config.log
  W: siefs source: configure-generated-file-in-source config.status
  W: siefs source: configure-generated-file-in-source config.cache
  
  The mentioned files are in the upstream source and I'm uncertain
  whether to remove the files, ignore the warning or do something
  else about this. Any help is greatly appreciated.
 
 You cannot remove them from source or the orig.tar.gz won't be
 pristine anymore.
 
 I suggest fixing the upstream autotools configuration to make these
 files properly delete and then to send the patch upstream. Ignore
 the warning until upstream integrates it, and make sure to pester
 upstream regularly if the warning persists across new versions.

The problem is that I do not know autotools good enough to tell the
upstream author what's wrong with his autotools configuration.

What I've found out so far is that a tarfile produced by 'make dist'
is much cleaner than the original source from upstream. Unfortunately
this would break the subdir /converter (containing vmo2wav, not
included in the package). I investigated this further and found out
that the missing pieces (after 'make dist') will be included if I add
all *.h and COPYRIGHT in converter/Makefile.am to the variable
vmo2wav_SOURCES, then run 'automake' and 'make dist'.

After that the new tarfile does not include these files, and that's
what we want, isn't it.

siefs-0.4/config.cache
siefs-0.4/config.h
siefs-0.4/config.log
siefs-0.4/config.status
siefs-0.4/converter/.deps/
siefs-0.4/converter/.deps/add.Po
siefs-0.4/converter/.deps/decode.Po
siefs-0.4/converter/.deps/gsm_create.Po
siefs-0.4/converter/.deps/gsm_decode.Po
siefs-0.4/converter/.deps/gsm_destroy.Po
siefs-0.4/converter/.deps/gsm_option.Po
siefs-0.4/converter/.deps/long_term.Po
siefs-0.4/converter/.deps/rpe.Po
siefs-0.4/converter/.deps/short_term.Po
siefs-0.4/converter/.deps/table.Po
siefs-0.4/converter/.deps/vmconvert.Po
siefs-0.4/converter/.deps/vmo2wav.Po
siefs-0.4/converter/Makefile
siefs-0.4/Makefile
siefs-0.4/siefs/.deps/
siefs-0.4/siefs/.deps/bfb.Po
siefs-0.4/siefs/.deps/comm.Po
siefs-0.4/siefs/.deps/crcmodel.Po
siefs-0.4/siefs/.deps/obex.Po
siefs-0.4/siefs/.deps/siefs.Po
siefs-0.4/siefs/.deps/slink.Po
siefs-0.4/siefs/Makefile
siefs-0.4/stamp-h
siefs-0.4/stamp-h1
siefs-0.4/stamp-h.in

What I don't know is if that's the right way to go.

Mathias


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



Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread martin f krafft
also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.2255 +0200]:
 After that the new tarfile does not include these files, and that's
 what we want, isn't it.

Yes, but we also want the tarfile to be the same as the one
distributed by upstream. So please send the fix upstream and ignore
the warnings for now. They really do not matter *that* much.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Look young, feel smart

2004-10-10 Thread samara sanchez
Time is Stealing Your Most Precious Possession

Visit here to increase your quality of life
http://a.08Y.greatproductcorner.com/a/

Phenomenal effects on the sleep problems that have plagued me since my
teens.Kevin W., Rockford, IL



po box listed above and link works

The quality of included studies was poor overall  We did not detect bias
induced by any of the measures assessed  We could not obtain data on all
cause fatality for 33% of studies  It is unlikely that missing results would
shift the results for studies comparing the same  lactam relative risk 1 02
0 76 to 1 38 but it is of concern that studies comparing different  lactams
0 85 0 69 to 1 05 may not detect important harm to patients  . The officer
chuckled, as if much amused
Hamericans is bloomin' green, he remarked, so youse can stand for
Hamerican, right enough.


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



daemon users' $HOMEs?

2004-10-10 Thread martin f krafft
I have an unclarity about the $HOME of daemon users in hook scripts:

If there is no directory that we could call $HOME for the daemon,
what to do? --no-create-home is definitely needed, and not
specifying --home yields /home/$DAEMON in /etc/passwd, which is
nonexistant. Is that preferred, or should something like
/nonexistant be used instead?

Thanks for any answers or pointers. The policy does not seem to care
about this. And neither does devel-ref state something along the
lines.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Mathias Weidner
Dear mentors,

I'm looking for a sponsor to help me get this package into debian.

Package name : siefs
Version  : 0.2
Upstream Author  : Dmitry Zakharov [EMAIL PROTECTED]
URL  : http://mirror01.iptelecom.net.ua/~dmitry_z/siefs/
License  : GPL
Description  : virtual filesystem for accessing memory of Siemens mobiles
Long Description :
 SieFS is a virtual filesystem for accessing Siemens mobile phones
 memory (flexmem or MultiMediaCard). It's possible to mount your
 phone (by datacable or IRDA) and work with it like with any other
 removable storage.

The files are at
http://weidner.in-bad-schmiedeberg.de/computer/linux/debian/siefs/download/

This would close Bug# 238314 filed by Bartosz Fenski.

I contacted Bartosz Fenski as he had packaged siefs by himself. Since
he does not have the time to make this package as good as it should
be, he allowed me to hijack the package.

At the moment there are a few warnings provided by lintian:

$ lintian siefs_0.2-1_i386.changes 
W: siefs source: configure-generated-file-in-source config.log
W: siefs source: configure-generated-file-in-source config.status
W: siefs source: configure-generated-file-in-source config.cache

The mentioned files are in the upstream source and I'm uncertain
whether to remove the files, ignore the warning or do something else
about this. Any help is greatly appreciated.

Thanks for taking your time,

Bye,

Mathias



Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread martin f krafft
also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.1706 +0200]:
 W: siefs source: configure-generated-file-in-source config.log
 W: siefs source: configure-generated-file-in-source config.status
 W: siefs source: configure-generated-file-in-source config.cache
 
 The mentioned files are in the upstream source and I'm uncertain
 whether to remove the files, ignore the warning or do something
 else about this. Any help is greatly appreciated.

You cannot remove them from source or the orig.tar.gz won't be
pristine anymore.

I suggest fixing the upstream autotools configuration to make these
files properly delete and then to send the patch upstream. Ignore
the warning until upstream integrates it, and make sure to pester
upstream regularly if the warning persists across new versions.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Bartosz Fenski aka fEnIo
On Sun, Oct 10, 2004 at 05:06:10PM +0200, Mathias Weidner wrote:
 I'm looking for a sponsor to help me get this package into debian.
 
 Package name : siefs
 Version  : 0.2
 Upstream Author  : Dmitry Zakharov [EMAIL PROTECTED]
 URL  : http://mirror01.iptelecom.net.ua/~dmitry_z/siefs/
 License  : GPL
 Description  : virtual filesystem for accessing memory of Siemens mobiles
 Long Description :
  SieFS is a virtual filesystem for accessing Siemens mobile phones
  memory (flexmem or MultiMediaCard). It's possible to mount your
  phone (by datacable or IRDA) and work with it like with any other
  removable storage.
 
 The files are at
 http://weidner.in-bad-schmiedeberg.de/computer/linux/debian/siefs/download/
 
 This would close Bug# 238314 filed by Bartosz Fenski.
 
 I contacted Bartosz Fenski as he had packaged siefs by himself. Since
 he does not have the time to make this package as good as it should
 be, he allowed me to hijack the package.

Hello Mathias. First of all thanks for taking care of siefs.

 At the moment there are a few warnings provided by lintian:
 
 $ lintian siefs_0.2-1_i386.changes 
 W: siefs source: configure-generated-file-in-source config.log
 W: siefs source: configure-generated-file-in-source config.status
 W: siefs source: configure-generated-file-in-source config.cache
 
 The mentioned files are in the upstream source and I'm uncertain
 whether to remove the files, ignore the warning or do something else
 about this. Any help is greatly appreciated.
 
 Thanks for taking your time,

Do you know that there is newer version available?
http://mirror01.iptelecom.net.ua/~dmitry_z/siefs/

It's 0.4 version and it fixes some bugs and supports some new phones, so
you certainly should start from that source.

Second thing. As you said I don't have time to make this package as good as
it should be, but you didn't make it either ;)

As far as I looked to similar packages, all filesystems have to provide
some mount.name_of_filesystem binaries.
Take a look at shfs or smbfs if you need examples.

Also there is problem with vmo2wav binary. It also exists in obexftp
package. So I suppose there are three ways of fixing it:

1) make your package conflict with obexftp
2) ask obexftp's maintainer to remove vmo2wav binary from his package 
   in fact our (that from siefs) binary is better, it has some output
   messages and seems to be more up2date.
3) ask obexftp's maintainer to remove vmo2wav binary and create two binary
   packages from siefs - siefs  vmo2wav. Then obexftp's maintainer could
   set obexftp dependant on vmo2wav.

regards
fEnIo

-- 
  _  Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | 
IRC:fEnIo
_|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska
(0 0)  phone:+48602383548 | Slackware - the weakest link
ooO--(_)--Ooo  http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001


signature.asc
Description: Digital signature


Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread martin f krafft
also sprach Bartosz Fenski aka fEnIo [EMAIL PROTECTED] [2004.10.10.1755 
+0200]:
 Also there is problem with vmo2wav binary. It also exists in
 obexftp package. So I suppose there are three ways of fixing it:

It has no place in either, really. I suggest removing it from siefs
and filing a bug against obexftp to export all such conversion
utilities to another binary package.

 1) make your package conflict with obexftp

no!

 2) ask obexftp's maintainer to remove vmo2wav binary from his package 
in fact our (that from siefs) binary is better, it has some output
messages and seems to be more up2date.

then please put it in another binary package.

 3) ask obexftp's maintainer to remove vmo2wav binary and create two binary
packages from siefs - siefs  vmo2wav. Then obexftp's maintainer could
set obexftp dependant on vmo2wav.

exactly.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: /usr/include/linux/irq.h Question.

2004-10-10 Thread Eric Dickner

--- martin f krafft [EMAIL PROTECTED] wrote:
 If it's a kernel driver, it should use the
 kernel-headers-2.x.xx-xxx
 package's files.
 
 If it's a userspace driver, it's just plain broken.

It's a kernel module driver, added with insmod and the
rest; it's not compiled inside the kernel itself.

When I compiled it under 2.2.20-idepci it did need the
proper kernel-headers-2. and for this compiling I
do have the new, matching set of headers.  But it
isn't getting far enough into the compile to use them,
as far as I can tell.

Also...I went from 2.2.20-idepci with a apt-get
dist-upgrade so I think I have a new libc6 package;
2.2.x to 2.3.x.  Could that be the problem?

ejd



___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com



Re: /usr/include/linux/irq.h Question.

2004-10-10 Thread martin f krafft
also sprach Eric Dickner [EMAIL PROTECTED] [2004.10.10.1821 +0200]:
 When I compiled it under 2.2.20-idepci it did need the
 proper kernel-headers-2. and for this compiling I
 do have the new, matching set of headers.  But it
 isn't getting far enough into the compile to use them,
 as far as I can tell.

It would have surprised me to find Broadcom actually have a clue. As
the maintainer of bcm{44,57}00-source, I can sing a song about that.

So it looks like you will have to fix their stuff.

 Also...I went from 2.2.20-idepci with a apt-get
 dist-upgrade so I think I have a new libc6 package;
 2.2.x to 2.3.x.  Could that be the problem?

Kernel mode drivers should not care about libc6 just like user space
drivers should not care about (linux-)?kernel-headers.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: daemon users' $HOMEs?

2004-10-10 Thread Sven Mueller

martin f krafft [u] wrote on 10/10/2004 15:11:

I have an unclarity about the $HOME of daemon users in hook scripts:

If there is no directory that we could call $HOME for the daemon,
what to do? --no-create-home is definitely needed, and not
specifying --home yields /home/$DAEMON in /etc/passwd, which is
nonexistant. Is that preferred, or should something like
/nonexistant be used instead?

Thanks for any answers or pointers. The policy does not seem to care
about this. And neither does devel-ref state something along the
lines.


Most system users seem to set their home directory to the variable data 
path their daemon uses. www-data uses /var/www, irc uses /var/run/ircd, 
sshd uses /var/run/sshd. However hacluster (heartbeat) uses /tmp.
/tmp is also the recommended home directory for system users on Mandrake 
and Redhat IIRC.
If the daemon doesn't have any run-time data which would belong in 
/var/lib or /var/spool, I would say use /tmp.


Regards,
Sven



Re: daemon users' $HOMEs?

2004-10-10 Thread martin f krafft
also sprach Sven Mueller [EMAIL PROTECTED] [2004.10.10.1928 +0200]:
 /var/run/ircd, sshd uses /var/run/sshd. However hacluster
 (heartbeat) uses /tmp. /tmp is also the recommended home directory
 for system users on Mandrake and Redhat IIRC.

Call me strange, but something about /tmp strikes me as
inappropriate. It won't matter in this case, I guess, but still...

 If the daemon doesn't have any run-time data which would belong in 
 /var/lib or /var/spool, I would say use /tmp.

nobody has /nonexistent... maybe that's better then as it makes the
claim explicit.

Anyway, Sven, this is about your package spampd, and I suggested
/nonexistant. Better make that =~ s/a/e/ for consistency...

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: daemon users' $HOMEs?

2004-10-10 Thread Sven Mueller

martin f krafft [u] wrote on 10/10/2004 19:33:

also sprach Sven Mueller [EMAIL PROTECTED] [2004.10.10.1928 +0200]:


/var/run/ircd, sshd uses /var/run/sshd. However hacluster
(heartbeat) uses /tmp. /tmp is also the recommended home directory
for system users on Mandrake and Redhat IIRC.


Call me strange, but something about /tmp strikes me as
inappropriate. It won't matter in this case, I guess, but still...


I know what you mean. If the daemon doesn't expect it's homedirectory to 
be /tmp, there might be exploitable race-conditions.


If the daemon doesn't have any run-time data which would belong in 
/var/lib or /var/spool, I would say use /tmp.


nobody has /nonexistent... maybe that's better then as it makes the
claim explicit.


You've certainly got a point there.


Anyway, Sven, this is about your package spampd, and I suggested
/nonexistant. Better make that =~ s/a/e/ for consistency...


I know you where talking about my package, but I wanted this to turn 
into a discussion a bit more generic.


cu,
sven

--
-[ Ciphire Signature ]--
From: [EMAIL PROTECTED] signed email body (873 characters)
Date: on 10 October 2004 at 18:00:01 GMT
To:   debian-mentors@lists.debian.org

: The message above has been secured using Ciphire Mail.
: Verify this signature and download your free encryption
: software at www.ciphire.com. The three garbled lines
: below are the sender's verifiable encoded signature.

00fAEAAACheGlBaQMAAKwCAAIAAgACACA2A5rfIAG/9i0QTXWRxDN1xNHi9n
zP50IdFpQpJDdATQEAgQr8ZB70IOSGevJtyc2iyrsTaJECa5ZA26iXocSUnP2ET7
JepQwzUO1tgP3txDPGSZMrDkbcc0eOfeb1WOiSlA==
--[ End Ciphire Signed Message ]



Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Mathias Weidner
Hello,

I've uploaded a new package from version 0.4 at the same location.

Package name : siefs
Version  : 0.4
Upstream Author  : Dmitry Zakharov [EMAIL PROTECTED]
URL  : http://mirror01.iptelecom.net.ua/~dmitry_z/siefs/
License  : GPL
Description  : virtual filesystem for accessing memory of Siemens mobiles
Long Description :
 SieFS is a virtual filesystem for accessing Siemens mobile phones
 memory (flexmem or MultiMediaCard). It's possible to mount your
 phone (by datacable or IRDA) and work with it like with any other
 removable storage.

The files are at
http://weidner.in-bad-schmiedeberg.de/computer/linux/debian/siefs/download/

On Sun, Oct 10, 2004 at 05:55:37PM +0200, Bartosz Fenski aka fEnIo wrote:
[...]
 Do you know that there is newer version available?
 http://mirror01.iptelecom.net.ua/~dmitry_z/siefs/
 
 It's 0.4 version and it fixes some bugs and supports some new phones, so
 you certainly should start from that source.

In fact I wasn't aware of this version even though it was uploaded the
same day I built the package for 0.2.

 As far as I looked to similar packages, all filesystems have to provide
 some mount.name_of_filesystem binaries.
 Take a look at shfs or smbfs if you need examples.

This was already done in the package for version 0.2 and is so in 0.4.

 Also there is problem with vmo2wav binary. It also exists in obexftp
 package. So I suppose there are three ways of fixing it:

As I mentioned in the private mail I choose the fourth way and did not
include vmo2wav until this would be settled with the maintainer of
obexftp.

On Sun, Oct 10, 2004 at 06:03:01PM +0200, martin f krafft wrote:
 also sprach Bartosz Fenski aka fEnIo [EMAIL PROTECTED] [2004.10.10.1755 
 +0200]:
  Also there is problem with vmo2wav binary. It also exists in
  obexftp package. So I suppose there are three ways of fixing it:
 
 It has no place in either, really. I suggest removing it from siefs

That's what I did in the old and new package.

  3) ask obexftp's maintainer to remove vmo2wav binary and create two binary
 packages from siefs - siefs  vmo2wav. Then obexftp's maintainer could
 set obexftp dependant on vmo2wav.
 
 exactly.

I would do this in a later version, once the package is in a shape to
be uploaded.

I had some problems first with the new package but found them related
to the kernel version (both package work fine with 2.6.7-1-686 and not
with 2.6.8-1-686).

Mathias



echo+newline in postinst

2004-10-10 Thread Laszlo 'GCS' Boszormenyi
Hi,

 I have to write a newline along with other things to a config file from
postinst. I was told and discovered that echo -e '\nline' is not
supported in every shell. What would be the best solution for this? I
think I should use printf '\nline' as it seems to work in every shell.
Is it ok, or should I use an other solution? Like
'(echo; echo line) config_file'?

Regards,
Laszlo/GCS



Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Laszlo 'GCS' Boszormenyi
* martin f krafft [EMAIL PROTECTED] [2004-10-10 17:21:55 +0200]:

 also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.1706 +0200]:
  W: siefs source: configure-generated-file-in-source config.log
  W: siefs source: configure-generated-file-in-source config.status
  W: siefs source: configure-generated-file-in-source config.cache
  
  The mentioned files are in the upstream source and I'm uncertain
  whether to remove the files, ignore the warning or do something
  else about this. Any help is greatly appreciated.
 
 You cannot remove them from source or the orig.tar.gz won't be
 pristine anymore.
 I usually remove them from debian/rules clean: with rm -f
This helps for me.

 I suggest fixing the upstream autotools configuration to make these
 files properly delete and then to send the patch upstream.
 This would be the best, you are right.

Regards,
Laszlo/GCS


signature.asc
Description: Digital signature


Re: echo+newline in postinst

2004-10-10 Thread martin f krafft
also sprach Laszlo 'GCS' Boszormenyi [EMAIL PROTECTED] [2004.10.10.2241 
+0200]:
 supported in every shell. What would be the best solution for
 this? I think I should use printf '\nline' as it seems to work
 in every shell.

Yes, this is supported by POSIX.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread martin f krafft
also sprach Laszlo 'GCS' Boszormenyi [EMAIL PROTECTED] [2004.10.10.2246 
+0200]:
  I usually remove them from debian/rules clean: with rm -f This
  helps for me.

They will still be in the source package as patch does not by
default delete files.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread Mathias Weidner
On Sun, Oct 10, 2004 at 05:21:55PM +0200, martin f krafft wrote:
 also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.1706 +0200]:
  W: siefs source: configure-generated-file-in-source config.log
  W: siefs source: configure-generated-file-in-source config.status
  W: siefs source: configure-generated-file-in-source config.cache
  
  The mentioned files are in the upstream source and I'm uncertain
  whether to remove the files, ignore the warning or do something
  else about this. Any help is greatly appreciated.
 
 You cannot remove them from source or the orig.tar.gz won't be
 pristine anymore.
 
 I suggest fixing the upstream autotools configuration to make these
 files properly delete and then to send the patch upstream. Ignore
 the warning until upstream integrates it, and make sure to pester
 upstream regularly if the warning persists across new versions.

The problem is that I do not know autotools good enough to tell the
upstream author what's wrong with his autotools configuration.

What I've found out so far is that a tarfile produced by 'make dist'
is much cleaner than the original source from upstream. Unfortunately
this would break the subdir /converter (containing vmo2wav, not
included in the package). I investigated this further and found out
that the missing pieces (after 'make dist') will be included if I add
all *.h and COPYRIGHT in converter/Makefile.am to the variable
vmo2wav_SOURCES, then run 'automake' and 'make dist'.

After that the new tarfile does not include these files, and that's
what we want, isn't it.

siefs-0.4/config.cache
siefs-0.4/config.h
siefs-0.4/config.log
siefs-0.4/config.status
siefs-0.4/converter/.deps/
siefs-0.4/converter/.deps/add.Po
siefs-0.4/converter/.deps/decode.Po
siefs-0.4/converter/.deps/gsm_create.Po
siefs-0.4/converter/.deps/gsm_decode.Po
siefs-0.4/converter/.deps/gsm_destroy.Po
siefs-0.4/converter/.deps/gsm_option.Po
siefs-0.4/converter/.deps/long_term.Po
siefs-0.4/converter/.deps/rpe.Po
siefs-0.4/converter/.deps/short_term.Po
siefs-0.4/converter/.deps/table.Po
siefs-0.4/converter/.deps/vmconvert.Po
siefs-0.4/converter/.deps/vmo2wav.Po
siefs-0.4/converter/Makefile
siefs-0.4/Makefile
siefs-0.4/siefs/.deps/
siefs-0.4/siefs/.deps/bfb.Po
siefs-0.4/siefs/.deps/comm.Po
siefs-0.4/siefs/.deps/crcmodel.Po
siefs-0.4/siefs/.deps/obex.Po
siefs-0.4/siefs/.deps/siefs.Po
siefs-0.4/siefs/.deps/slink.Po
siefs-0.4/siefs/Makefile
siefs-0.4/stamp-h
siefs-0.4/stamp-h1
siefs-0.4/stamp-h.in

What I don't know is if that's the right way to go.

Mathias



Re: Bug# 238314 RFS: siefs - virtual fs for accessing Siemens mobiles

2004-10-10 Thread martin f krafft
also sprach Mathias Weidner [EMAIL PROTECTED] [2004.10.10.2255 +0200]:
 After that the new tarfile does not include these files, and that's
 what we want, isn't it.

Yes, but we also want the tarfile to be the same as the one
distributed by upstream. So please send the fix upstream and ignore
the warnings for now. They really do not matter *that* much.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


signature.asc
Description: Digital signature


Look young, feel smart

2004-10-10 Thread samara sanchez
Time is Stealing Your Most Precious Possession

Visit here to increase your quality of life
http://a.08Y.greatproductcorner.com/a/

Phenomenal effects on the sleep problems that have plagued me since my
teens.Kevin W., Rockford, IL



po box listed above and link works

The quality of included studies was poor overall  We did not detect bias
induced by any of the measures assessed  We could not obtain data on all
cause fatality for 33% of studies  It is unlikely that missing results would
shift the results for studies comparing the same  lactam relative risk 1 02
0 76 to 1 38 but it is of concern that studies comparing different  lactams
0 85 0 69 to 1 05 may not detect important harm to patients  . The officer
chuckled, as if much amused
Hamericans is bloomin' green, he remarked, so youse can stand for
Hamerican, right enough.