Your message dated Wed, 6 Feb 2008 04:23:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Done (somewhat)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gnome-peercast
Severity: normal
Hi!
Peercast has entered debian sid this week!
Then, it has been modified in order to compile shared and static
libraries, so that any program that depends upon peercast's code should
now be linked against it.
As this the case of this app, I'm filling a BR.
You can see a discussion of this matter here [1]
This dependancy is also very important when it comes to security and bug
correction, for instance bug #324392 has also been encountered and
solved for peercast, but it was twice time the same work...
If gnome-peercast includes changes to peercast's code, then we should
discuss and apply patches if it is possible.. If else, then I think this
should be accepted and stated anywhere as a complete fork.
Romain
[1]: http://lists.debian.org/debian-mentors/2005/09/msg00514.html
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.1-bogue
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
Package libpeercast has been removed.
Romain
--- End Message ---
