On Mon, Mar 20, 2006 at 03:33:22PM +0100, Frank Küster wrote:
> > If foo2 already exists, I'd still go for that solution, but you'll then
> > need to ask for foo2 removal via a bug to ftp.debian.org.
> That's not possible, I think, unfortunately - we don't want teTeX which
> currently provides lib
Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote:
> N.B.: Such questions are easier to answer (less guessing needed w.r.t.
> missing information) given a real example.
I've noticed that. I thought it was a simple question regarding the
infrastructure setup, but it turns out not to be...
"foo" in
On Mon, Mar 20, 2006 at 12:03:13PM +0100, Frank Küster wrote:
> Hi,
>
> assume the following scenario:
>
> - Source package foo creates binary packages libfoo1 and libfoo-dev
> - source package foo2 creates binary packages libfoo2 and libfoo2-dev
>
> Since both versions are API-compatible, libfo
Scripsit Frank Küster <[EMAIL PROTECTED]>
> - Source package foo creates binary packages libfoo1 and libfoo-dev
> - source package foo2 creates binary packages libfoo2 and libfoo2-dev
> Since both versions are API-compatible, libfoo2-dev is renamed to
> foo-dev, replacing the old binary package f
On Mon, Mar 20, 2006 at 12:03:13PM +0100, Frank Küster <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> assume the following scenario:
>
> - Source package foo creates binary packages libfoo1 and libfoo-dev
> - source package foo2 creates binary packages libfoo2 and libfoo2-dev
>
> Since both versions are
Hi,
assume the following scenario:
- Source package foo creates binary packages libfoo1 and libfoo-dev
- source package foo2 creates binary packages libfoo2 and libfoo2-dev
Since both versions are API-compatible, libfoo2-dev is renamed to
foo-dev, replacing the old binary package from source pac
6 matches
Mail list logo