Re: Dynamic linking to /usr/lib/xxxxx directory.

[Mike Hommey]

On Sat, Dec 16, 2006 at 09:50:18PM -0800, Steve Langasek <[EMAIL PROTECTED]> 
wrote:
> On Sat, Dec 16, 2006 at 10:54:20PM +, Paul Cager wrote:
> > I'm packaging AFNIX which provides four or five executables and a bunch
> > of shared objects that the executables use. Since the SOs are not likely
> > to be of use to anything except the AFNIX system itself, I intend to
> > install the SOs in /usr/lib/afnix/*.so. I'm a newbie as far as SOs are
> > concerned, so can I ask a fairly basic question?
> 
> > How do I link the program so that the end-user does not have to set
> > LD_LIBRARY_PATH?  Is this a job for the "--rpath" ld parameter, or is
> > there a better way?
> 
> You would use -rpath for this, yes.  But please note that installing
> libraries in private directories is discouraged by policy in any case.

Except if they are private objects.

Mike


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

Re: RFS: libssh - SSH and SCP library

[Jean-Philippe Garcia Ballester]

On Sunday 17 December 2006 05:54, Mikhail Gusarov wrote:
> You ([EMAIL PROTECTED]) wrote:
>
>  JGB> Hi everybody, I'm looking for a sponsor for the libssh package :
>  JGB> * Package name: libssh
>
> I have to raise the problem that two projects 'libssh' and 'libssh2'
> (http://libssh2.org/) are existing (and I will ITP libssh2 soon).
>
> This may easily lead to the clash of names.

  I'm aware of this problem, but is there any solution other than one package 
changing its name ?

-- 
Jean-Philippe Garcia Ballester


pgpYFoYtAVE9U.pgp
Description: PGP signature

Re: RFS: libssh - SSH and SCP library

[Mikhail Gusarov]

You ([EMAIL PROTECTED]) wrote:

 >> I have to raise the problem that two projects 'libssh' and 'libssh2'
 >> (http://libssh2.org/) are existing (and I will ITP libssh2 soon).
 >>
 >> This may easily lead to the clash of names.

 JGB> I'm aware of this problem, but is there any solution other than
 JGB> one package changing its name ?

Probably we should accurately specify suffixes of packages, e.g. make
them libssh-0 and libssh2-0 to avoid libssh2 package which is actually
libssh with soname bumped to 2. Source packages libssh and libssh2 are
ok.

Do you have objections to such naming scheme?

-- 
JID: [EMAIL PROTECTED]


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

Re: Two questions on package quality

[Thomas Viehmann]

Nikita V. Youshchenko wrote:
>   (2) binary-without-manpage/no-manual-for-binary should not be added, so 
> linda/lintian complains remind that manual page should be written one day,
Lintian overrides are intended for false positives. Unsing them to
suppress reports of valid packaging problems is completely frivolous and
degrades Debian's overall quality.

> So .orig.tar.gz got repackaged, and now it differs from upstream.
> Should then 'upstream' version string be changed from x.y.z to 
> x.y.z.debian? Or not? Or it does not matter?
If you change the orig.tar.gz, the 'upstream' version should indicate
that. You'd probally want to check with the best packaging practices
suggested by the Developer's Reference[1].

Kind regards

T.

1.
http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-repackagedorigtargz

-- 
Thomas Viehmann, http://thomas.viehmann.net/


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

Bug#403446: ITP: libssh2 -- SSH2 client-side library

[Mikhail Gusarov]

Package: wnpp
Severity: wishlist
Owner: Mikhail Gusarov <[EMAIL PROTECTED]>

* Package name: libssh2
  Version : 0.14
  Upstream Author : Sara Golemon <[EMAIL PROTECTED]>
* URL : http://libssh2.org/
* License : BSD
  Programming Lang: C
  Description : SSH2 client-side library

libssh2 is the thin library implementing client side of SSH2 protocol
as defined by Internet Drafts SECSH-TRANS, SECSH-USERAUTH,
SECSH-CONNECTION, SECSH-ARCH, SECSH-FILEXFER, SECSH-DHGEX,
SECSH-NUMBERS, and SECSH-PUBLICKEY

This boils down to the regular terminal, scp and SFTP sessions; port
forwarding; password, key-based and keyboard-interactive
authentication.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)


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

Re: RFS: libssh - SSH and SCP library

[Mikhail Gusarov]

You ([EMAIL PROTECTED]) wrote:

 >> Probably we should accurately specify suffixes of packages,
 >> e.g. make them libssh-0 and libssh2-0 to avoid libssh2 package
 >> which is actually libssh with soname bumped to 2. Source packages
 >> libssh and libssh2 are ok.

 JGB> Do you mean libssh-SONAME and libssh2-SONAME ?

Yes.

 JGB> If so, I agree to it.

Ok, let's do it.

-- 
JID: [EMAIL PROTECTED]


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

Re: RFS: libssh - SSH and SCP library

[Guus Sliepen]

On Sat, Dec 16, 2006 at 11:03:51PM +0100, Jean-Philippe Garcia Ballester wrote:

>   Hi everybody,
>   I'm looking for a sponsor for the libssh package :
> 
> * Package name: libssh
>   Version : 0.2rc
>   Upstream Author : "Aris Adamantiadis" <[EMAIL PROTECTED]>
> * URL : http://www.0xbadc0de.be/libssh:libssh
> * License : LGPL
>   Description : SSH and SCP library

Make sure you compile it with --with-libgcrypt, so that it really is
LGPL. If it's linked to OpenSSL, then a GPLed application using this
library probably needs to add a license exception before we can
distribute it.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen <[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Re: RFS: libssh - SSH and SCP library

[Guus Sliepen]

On Sun, Dec 17, 2006 at 11:44:27AM +0100, Guus Sliepen wrote:

> Make sure you compile it with --with-libgcrypt, so that it really is
> LGPL. If it's linked to OpenSSL, then a GPLed application using this
> library probably needs to add a license exception before we can
> distribute it.

Ehm, never mind, I should've read your email completely before replying.
I see I'm preaching to the choir :)

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen <[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Re: RFS: libssh - SSH and SCP library

[Jean-Philippe Garcia Ballester]

On Sunday 17 December 2006 10:29, Mikhail Gusarov wrote:
> You ([EMAIL PROTECTED]) wrote:
>  >> Probably we should accurately specify suffixes of packages,
>  >> e.g. make them libssh-0 and libssh2-0 to avoid libssh2 package
>  >> which is actually libssh with soname bumped to 2. Source packages
>  >> libssh and libssh2 are ok.
>
>  JGB> Do you mean libssh-SONAME and libssh2-SONAME ?
>
> Yes.
>
>  JGB> If so, I agree to it.
>
> Ok, let's do it.

  I've updated my package. It now builds libssh-2, libssh-2-dev, and 
libssh-2-dbg.

-- 
Jean-Philippe Garcia Ballester


pgpTv0Wl6AMrj.pgp
Description: PGP signature

Re: madison not working correctly on merkel

[Frederic Peters]

Luk Claes wrote:

> Julian Gilbey wrote:
> > I've noticed (and I'm not the only one) that the package database as
> > access by madison on merkel is no longer up-to-date.  Does anyone know
> > why?  Could someone rectify this situation, please?
> 
> The updates have not been reactivated since the move of ftp-master.d.o AFAIK.

I have been using madison on merkel to produce the GNOME 2.16 status
page[1] and it worked until very recently (sometimes between Nov 19th
and Nov 27h).


Regards,
Frederic

[1] http://www.0d.be/debian/debian-gnome-2.16-status.html



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

Re: madison not working correctly on merkel

[David Weinehall]

On Sun, Dec 17, 2006 at 04:52:04PM +0100, Frederic Peters wrote:
> Luk Claes wrote:
> 
> > Julian Gilbey wrote:
> > > I've noticed (and I'm not the only one) that the package database as
> > > access by madison on merkel is no longer up-to-date.  Does anyone know
> > > why?  Could someone rectify this situation, please?
> > 
> > The updates have not been reactivated since the move of ftp-master.d.o 
> > AFAIK.
> 
> I have been using madison on merkel to produce the GNOME 2.16 status
> page[1] and it worked until very recently (sometimes between Nov 19th
> and Nov 27h).
> 
> 
> Regards,
> Frederic
> 
> [1] http://www.0d.be/debian/debian-gnome-2.16-status.html

Some entries seem to list newer Debian-versions than upstream
versions...  Some watch-files out of sync?


Regards: David
-- 
 /) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window   (\
//  ~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/(/   Beautiful hoar-frost   (/


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

Bug#403506: ITP: fdisk -- linux fdisk replacement based on libparted

[Julien Louis]

Package: wnpp
Severity: wishlist
Owner: Julien Louis <[EMAIL PROTECTED]>

* Package name: fdisk
  Version : 0.9.1
  Upstream Author : Leslie P. Polzer <[EMAIL PROTECTED]>
* URL : http://www.gnu.org/software/fdisk/
* License : GPL
  Programming Lang: C
  Description : linux fdisk replacement based on libparted

 GNU fdisk is a replacement to the old linux fdisk. It provides the same
 features as the original fdisk provides plus some interesting ones like:
  * partition resizing
  * creating filesystem on newly created partitions
  * partition integrity checking
  * copying/moving partition
 .
 GNU fdisk also intend to be a valid replacement for mac-fdisk and FreeBSD
 fdisk.

 Packages are available at: http://kaoru.asyd.net/~ptitlouis/debian/fdisk/

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

-- 
La photo 29 montre que maintenant, les boutons enfoncés ont un cadre  de
contour afin de voir exactement sur quel bouton on se trouve. 
-- Jayce - Un peu de 3D, c'est plus joli. --


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

Bug is very vague, should I close it?

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

>Package: rtorrent
>Version: 0.4.1-1a0.mrvn.1
>Severity: wishlist
>
>Hi,
>
>I would like to see some features like DHT in rtorrent to make it more
>competitive with other clients. For an overview see
>
>http://en.wikipedia.org/wiki/Comparison_of_BitTorrent_software
>
>MfG
>   Goswin

This bug probably will never be solved until rtorrent get all features
of all torrent clients...

So, should I close this bug? There's a lot of bugs requesting specific
features[1] so I don't think this bug it's necessary.

Please CC answers to [EMAIL PROTECTED]

[1]
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=rtorrent&archive=no&pend-exc=pending-fixed&pend-exc=fixed&pend-exc=done&sev-inc=minor&sev-inc=wishlist#_0_6_3
- --

ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFhZX3OKCtW8rKsRgRAuFuAKCoVlUqjyyTgD9BSmz/nUODxVDRVQCgyirN
029JDSq7b3bgUHnB073Dn2E=
=wp9R
-END PGP SIGNATURE-


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

Re: Two questions on package quality

[Russ Allbery]

Nikita V Youshchenko <[EMAIL PROTECTED]> writes:

> 1. Upstream does not provide a manual page for the binary. Packager
> decided to add binary-without-manpage to lintian override file, and Tag:
> no-manual-for-binary to linda override file.

Please don't do this.  The lintian tag can be used by others who have more
time to find all binaries without man pages and contribute man pages for
them, and overriding it defeats that purpose.

An override should only be used when what lintian is finding really isn't
a bug for reasons that lintian can't know about (for example, if the man
page is provided by some other package on which that package depends).  If
the bug is present and fixing it is just hard, please leave the lintian
message there so that it's documented.

> My questions are:

> - Is having a manual page for each binary inside package a mandatory
> requirement these days?

No, it's not mandatory, it's just a bug.

> 2. Upstream tarball contains ttf-dejavu font. Linda found that and
> complained.

Why?

Sure, duplication of code is a bit annoying, but ttf-dejavu appears to be
a free font, so it doesn't hurt anything that the upstream tarball
contains it.  The installed *package* shouldn't duplicate the font and
should instead just depend on the font package it needs (or possibly not
even depend -- if it's only accessing the font via X, it should only
recommend and allow for the possibility that there's an X font server
providing the font).  But there's no harm that I can see in leaving the
font in the upstream tarball unless it's under some other non-DFSG-free
license, and you want to avoid repackaging the upstream tarball when you
can help it.

-- 
Russ Allbery ([EMAIL PROTECTED])   


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

Re: madison not working correctly on merkel

[Loïc Minier]

On Sun, Dec 17, 2006, David Weinehall wrote:
> Some entries seem to list newer Debian-versions than upstream
> versions...  Some watch-files out of sync?

 The list of GNOME versions is built from the 2.16 tarball repository,
 but Debian might have cherry-picked some newer upstream releases, such
 as libxml2 2.6.27.

-- 
Loïc Minier <[EMAIL PROTECTED]>
 "Forget your stupid theme park! I'm gonna make my own! With hookers!
  And blackjack! In fact, forget the theme park!"  -- Bender


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

possible grave bug in debian-installer or ifupdown?

[Bastian Venthur]

Hi,

Two or three weeks ago I installed the current latest Debian/Testing on
two different servers. Last week I had to reboot both and noticed that
none of them appeared back in the network again. I checked them locally
and noticed that on both boxes the network interface was not brought up.
I issued:

# ifup eth0

manually on both boxes but nothing happened. I checked
/etc/network/interfaces on both boxes and noticed the following line:

allow-hotplug eth0

after replacing it with

auto eth0

the problem was fixed. Since I used a standard minimal installation on
two different boxes, I wonder if this is a bug in d-i or ifupdown. So am
I missing something obvious or do we have a grave bug?

Any hints?


Cheers,

Bastian

-- 
Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org


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

Re: Some emacs modes only depends on *emacs21, mass bug filing?

[Arnaud Fontaine]

Hello,

I have just  created a tracker on wotomae in order  to show the progress
of this task:

http://wotomae.debian.net/tracker/emacsen

Regards,
Arnaud Fontaine


pgpse02fcAS8R.pgp
Description: PGP signature

Re: Bug#403506: ITP: fdisk -- linux fdisk replacement based on libparted

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/17/06 09:43, Julien Louis wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Julien Louis <[EMAIL PROTECTED]>
> 
> * Package name: fdisk
>   Version : 0.9.1
>   Upstream Author : Leslie P. Polzer <[EMAIL PROTECTED]>
> * URL : http://www.gnu.org/software/fdisk/
> * License : GPL
>   Programming Lang: C
>   Description : linux fdisk replacement based on libparted
> 
>  GNU fdisk is a replacement to the old linux fdisk. It provides the same
>  features as the original fdisk provides plus some interesting ones like:
>   * partition resizing
>   * creating filesystem on newly created partitions
>   * partition integrity checking
>   * copying/moving partition
>  .
>  GNU fdisk also intend to be a valid replacement for mac-fdisk and FreeBSD
>  fdisk.
> 
>  Packages are available at: http://kaoru.asyd.net/~ptitlouis/debian/fdisk/

Since util-linux already has /sbin/fdisk, naming a package fdisk
seems ambiguous.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFhbSuS9HxQb37XmcRAs6AAJ4ogFkHwnCukj5AbztUtfVrwjeQ4gCfaI4m
8dadsaFP78piOmlvvcKVrkI=
=44bc
-END PGP SIGNATURE-


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

Re: Bug#403506: ITP: fdisk -- linux fdisk replacement based on libparted

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ron Johnson escribió:
> On 12/17/06 09:43, Julien Louis wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Julien Louis <[EMAIL PROTECTED]>
> 
>> * Package name: fdisk
>>   Version : 0.9.1
>>   Upstream Author : Leslie P. Polzer <[EMAIL PROTECTED]>
>> * URL : http://www.gnu.org/software/fdisk/
>> * License : GPL
>>   Programming Lang: C
>>   Description : linux fdisk replacement based on libparted
> 
> Since util-linux already has /sbin/fdisk, naming a package fdisk
> seems ambiguous.

Should be named something like `fdisk-gnu` or `fdiskgnu`, the binary too
for avoid problems with the `fdisk` binary that already exists.

Cheers!!

- --

ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFhbdzOKCtW8rKsRgRAjlOAKDOtfOBx5aTjMmLffHANMwUjMa50wCfSgQf
9lI9jYhW178b5+JxZcaht6M=
=wfgt
-END PGP SIGNATURE-


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

Name of a binary package according to sonames

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm maintaining libtorrent package, this source builds 2 binaries,
libtorrent-rakshasa (is libtorrent9 last version in debian archive) and
libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive),
I get this warning from lintian when I build the package.

Now running lintian...
W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10
Finished running lintian.

The version I'm building is libtorrent-0.11.0 so I don't think I should
call the binary libtorrent10.

What should I do?

Thanks and Cheers!!

- --

ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFhb+VOKCtW8rKsRgRAm69AKCWHPwAP31Vj3yGDcS/xTILRwa4ngCeMPSH
eSc1P96vM8AavyzfsvQxY8Y=
=rZbg
-END PGP SIGNATURE-


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

Re: Bug#403506: ITP: fdisk -- linux fdisk replacement based on libparted

[Julien Louis]

On Sun, Dec 17, 2006 at 05:32:36PM -0400, Jose Luis Rivas Contreras wrote:
 
> Should be named something like `fdisk-gnu` or `fdiskgnu`, the binary too
> for avoid problems with the `fdisk` binary that already exists.

Well, binaries shipped in the packages are already renamed to avoid
conflicts against (c)fdisk binaries shipped in the util-linux package.

I'll rename the package to gnu-fdisk reflect binary name changes.

Cheers

-- 
Christophe Colomb fut le premier socialiste :
il ne savait pas où il allait
il ignorait où il se trouvait
Et tout cela aux frais des autres.
-+- Winston Churchill -+-


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

Re: Bug is very vague, should I close it?

[Ben Finney]

Jose Luis Rivas Contreras <[EMAIL PROTECTED]> writes:

> >Package: rtorrent
> >Version: 0.4.1-1a0.mrvn.1
> >Severity: wishlist
> >
> >Hi,
> >
> >I would like to see some features like DHT in rtorrent to make it
> >more competitive with other clients. For an overview see
> >[...]
>
> This bug probably will never be solved until rtorrent get all
> features of all torrent clients...
>
> So, should I close this bug? There's a lot of bugs requesting
> specific features[1] so I don't think this bug it's necessary.

You could enlist the bug submitter's help. Ask them to retitle the bug
and be more specific about a particular feature, or to close it and
submit separate wishlist bugs for each feature they want.

-- 
 \ "If we don't believe in freedom of expression for people we |
  `\ despise, we don't believe in it at all."  -- Noam Chomsky |
_o__)  |
Ben Finney


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

Bug#403558: ITP: lastfmproxy -- proxy server for the last.fm radio streams

[Romain Beauxis]

Package: wnpp
Severity: wishlist
Owner: Romain Beauxis <[EMAIL PROTECTED]>

* Package name: lastfmproxy
  Version : 1.1
  Upstream Author : Vidar Madsen <[EMAIL PROTECTED]>
* URL : http://vidar.gimp.org/lastfmproxy/
* License : GPL
  Programming Lang: Python
  Description : proxy server for the last.fm radio streams

LastFMProxy is a proxy server for the last.fm radio streams. It allows
you to use your regular old audio player to listen to the last.fm
streams. It does this by acting as a player itself, connecting to the
server on your behalf, but instead of playing the stream, it simply
relays it to whichever other application connecting to it.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)


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

Re: Name of a binary package according to sonames

[Frank Lichtenheld]

On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote:
> The version I'm building is libtorrent-0.11.0 so I don't think I should
> call the binary libtorrent10.

Why not? The version of a library and its soname have seldomly
anything to do with each other (and if so, it may be a sign that
upstream doesn't understand the meaning of a soname).

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


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

Re: possible grave bug in debian-installer or ifupdown?

[Wesley J. Landaker]

On Sunday 17 December 2006 13:58, Bastian Venthur wrote:
> Two or three weeks ago I installed the current latest Debian/Testing on
> two different servers. Last week I had to reboot both and noticed that
> none of them appeared back in the network again. I checked them locally
> and noticed that on both boxes the network interface was not brought up.
> I issued:
>
>   # ifup eth0
>
> manually on both boxes but nothing happened. I checked
> /etc/network/interfaces on both boxes and noticed the following line:
>
>   allow-hotplug eth0
>
> after replacing it with
>
>   auto eth0
>
> the problem was fixed. Since I used a standard minimal installation on
> two different boxes, I wonder if this is a bug in d-i or ifupdown. So am
> I missing something obvious or do we have a grave bug?

It looks like something recent broke this. I can at least confirm it is 
happening on at least one of my boxes that was fairly recently installed 
with etch.

-- 
Wesley J. Landaker <[EMAIL PROTECTED]> 
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2


pgp788JpGbtIr.pgp
Description: PGP signature

Bug#403571: ITP: ccollect -- Tiny backup tool which fetches backups from remote machines

[Mario Iseli]

Package: wnpp
Severity: wishlist
Owner: Mario Iseli <[EMAIL PROTECTED]>

* Package name: ccollect
  Version : 0.5.1
  Upstream Author : Nico Schottelius
* URL : http://linux.schottelius.org/ccollect/
* License : GPL
  Programming Lang: shell
  Description : Tiny backup tool which fetches backups from remote machines

Nice backuptool which fetches the backup via rsync, instead of most
backup tools which put there backups somewhere.

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


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

Re: possible grave bug in debian-installer or ifupdown?

[Anthony Towns]

On Sun, Dec 17, 2006 at 09:58:48PM +0100, Bastian Venthur wrote:
> I issued:
>   # ifup eth0
> manually on both boxes but nothing happened. 

This probably means that ifup thought the interface was already up --
ie there was an "eth0" entry in /etc/network/ifstate. This is supposed to
be cleared on bootup, so should only still be there if eth0 was brought
up. Hard to say much more from a distance though.

> I checked
> /etc/network/interfaces on both boxes and noticed the following line:
>   allow-hotplug eth0
> after replacing it with
>   auto eth0

allow-hotplug interfaces will only be brought up by hotplug (or manually);
you might've deinstall hotplug and replaced it with udev, which would
probably give that result.

> I wonder if this is a bug in d-i or ifupdown. 

If you're not using hotplug, using "allow-hotplug" is the bug.

If eth0 isn't up after a boot, but "ifup eth0" does nothing, there's a
bug there too.

Cheers,
aj



signature.asc
Description: Digital signature

Returned mail: see transcript for details

[dayzers]

The message was not delivered due to the following reason:

Your message was not delivered because the destination computer was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message could not be delivered within 7 days:
Mail server 210.153.52.162 is not responding.

The following recipients could not receive this message:


Please reply to [EMAIL PROTECTED]
if you feel this message to be in error.