Robert Bihlmeyer [EMAIL PROTECTED] immo vero scripsit
If you want to provide further hints, upload a final version containing
you can remove me without ill effects in the description.
I think I would just remove the package, since the package has
only entered unstable, and not on testing nor
On Mon, Jun 18, 2001 at 10:49:35AM +0900, Junichi Uekawa wrote:
Hello,
Upstram of qtecasound has depricated libqtecasound,
and the only application which depended upon libqtecasound (qtecasound, and ecawave)
no longer need the library.
Would I need to make an empty package of
Daniel Stone [EMAIL PROTECTED] writes:
[...]
and make new versions of qtecasound and evawave, that have
Conflicts: libqtecasound, to make sure it gets removed from systems
as well.
This is overzealous unless the new versions do actually conflict with
the old lib (which I assume is not the
On Mon, Jun 18, 2001 at 10:49:35AM +0900, Junichi Uekawa wrote:
Hello,
Upstram of qtecasound has depricated libqtecasound,
and the only application which depended upon libqtecasound (qtecasound, and
ecawave)
no longer need the library.
Would I need to make an empty package of
On Mon, Jun 18, 2001 at 05:02:12PM +1000, Daniel Stone wrote:
On Mon, Jun 18, 2001 at 10:49:35AM +0900, Junichi Uekawa wrote:
Hello,
Upstram of qtecasound has depricated libqtecasound,
and the only application which depended upon libqtecasound (qtecasound, and
ecawave)
no longer
Daniel Stone [EMAIL PROTECTED] writes:
[...]
and make new versions of qtecasound and evawave, that have
Conflicts: libqtecasound, to make sure it gets removed from systems
as well.
This is overzealous unless the new versions do actually conflict with
the old lib (which I assume is not the
6 matches
Mail list logo
