Hi,
I am in the process to rename one of my packages (source and binary
packages), from "sextractor" to "source-extractor" (see #941466 for
rationale).
For this, I followed the Wiki; in d/control:
Package: source-extractor
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Breaks: sex
On Mon, Dec 10, 2001 at 01:52:15AM +0100, Christian Surchi wrote:
> On Mon, Dec 10, 2001 at 12:42:32AM +, Mark Brown wrote:
> > Effectively what you're doing is turning the old package into a virtual
> > package provided by the new one.
> I remember some messages about it and I don't think we
On Mon, Dec 10, 2001 at 12:42:32AM +, Mark Brown wrote:
> Effectively what you're doing is turning the old package into a virtual
> package provided by the new one.
I remember some messages about it and I don't think we could simply
"invent" virtual packages. And then, don't you suggest any "C
On Mon, Dec 10, 2001 at 01:11:19AM +0100, Christian Surchi wrote:
> Provide: is for virtual package. If you change name you should have a
> new package with Conflicts: and Replaces:.
Effectively what you're doing is turning the old package into a virtual
package provided by the new one.
--
"You
On Sun, Dec 09, 2001 at 02:42:05PM +, Mark Brown wrote:
> > The problem is I already released the debian package tclassic, so I
> > obviously need to get that out of pools if I change the name. The question
> > is how?
>
> Upload the new package, having it replace and provide the original
> pa
On Mon, Dec 10, 2001 at 01:52:15AM +0100, Christian Surchi wrote:
> On Mon, Dec 10, 2001 at 12:42:32AM +, Mark Brown wrote:
> > Effectively what you're doing is turning the old package into a virtual
> > package provided by the new one.
> I remember some messages about it and I don't think w
On Mon, Dec 10, 2001 at 12:42:32AM +, Mark Brown wrote:
> Effectively what you're doing is turning the old package into a virtual
> package provided by the new one.
I remember some messages about it and I don't think we could simply
"invent" virtual packages. And then, don't you suggest any "
On Mon, Dec 10, 2001 at 01:11:19AM +0100, Christian Surchi wrote:
> Provide: is for virtual package. If you change name you should have a
> new package with Conflicts: and Replaces:.
Effectively what you're doing is turning the old package into a virtual
package provided by the new one.
--
"Yo
On Sun, Dec 09, 2001 at 02:42:05PM +, Mark Brown wrote:
> > The problem is I already released the debian package tclassic, so I
> > obviously need to get that out of pools if I change the name. The question
> > is how?
>
> Upload the new package, having it replace and provide the original
> p
On Sun, Dec 09, 2001 at 03:41:54PM +0100, Stefan Hornburg (Racke) wrote:
> File a bug against ftp.debian.org to remove the stale packages.
But don't do that until the package is accepted under the new name.
Ben
--
nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED]
Debian http
On Sun, Dec 09, 2001 at 03:41:54PM +0100, Stefan Hornburg (Racke) wrote:
> File a bug against ftp.debian.org to remove the stale packages.
But don't do that until the package is accepted under the new name.
Ben
--
nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED]
Debian htt
Abraham vd Merwe <[EMAIL PROTECTED]> writes:
> Hi Hereward!
>
> > > What do I do if I want to change a package's name?
> > >
> >
> > If you mean have a different debian name to the upstream all you have to do
> > is
> > change it in debian/control and in then add a new changelog enty changing
On Sun, Dec 09, 2001 at 02:53:01PM +0200, Abraham vd Merwe wrote:
> The problem is I already released the debian package tclassic, so I
> obviously need to get that out of pools if I change the name. The question
> is how?
Upload the new package, having it replace and provide the original
package
Hi Hereward!
> > What do I do if I want to change a package's name?
> >
>
> If you mean have a different debian name to the upstream all you have to do is
> change it in debian/control and in then add a new changelog enty changing the
> package name on the first line.
No, what happened was that
Once upon a time (actually it was more like Sun, 9 Dec 2001 14:39:29 +0200),
Abraham vd Merwe <[EMAIL PROTECTED]> wrote:
> Hi!
>
> What do I do if I want to change a package's name?
>
If you mean have a different debian name to the upstream all you have to do is
change it in debian/control and
Abraham vd Merwe <[EMAIL PROTECTED]> writes:
> Hi Hereward!
>
> > > What do I do if I want to change a package's name?
> > >
> >
> > If you mean have a different debian name to the upstream all you have to do is
> > change it in debian/control and in then add a new changelog enty changing the
On Sun, Dec 09, 2001 at 02:53:01PM +0200, Abraham vd Merwe wrote:
> The problem is I already released the debian package tclassic, so I
> obviously need to get that out of pools if I change the name. The question
> is how?
Upload the new package, having it replace and provide the original
packag
Hi!
What do I do if I want to change a package's name?
--
Regards
Abraham
Home is the place where, when you have to go there, they have to take you in.
-- Robert Frost, "The Death of the Hired Man"
___
Abraham vd Merwe [ZR1BBQ]
Hi Hereward!
> > What do I do if I want to change a package's name?
> >
>
> If you mean have a different debian name to the upstream all you have to do is
> change it in debian/control and in then add a new changelog enty changing the
> package name on the first line.
No, what happened was tha
Once upon a time (actually it was more like Sun, 9 Dec 2001 14:39:29 +0200),
Abraham vd Merwe <[EMAIL PROTECTED]> wrote:
> Hi!
>
> What do I do if I want to change a package's name?
>
If you mean have a different debian name to the upstream all you have to do is
change it in debian/control and
Hi!
What do I do if I want to change a package's name?
--
Regards
Abraham
Home is the place where, when you have to go there, they have to take you in.
-- Robert Frost, "The Death of the Hired Man"
___
Abraham vd Merwe [ZR1BBQ
Daniel Stone <[EMAIL PROTECTED]> wrote:
>On Sat, May 26, 2001 at 10:04:45PM +0200, Michael Wiedmann wrote:
>> What is the proposed handling of a package whose name has changed?
>> (e.g.: the author of foo-0.1.tar.gz, Debian package foo_0.1-1_i386.deb,
>> changes the name of the package to bar-0.2.
Daniel Stone <[EMAIL PROTECTED]> wrote:
>On Sat, May 26, 2001 at 10:04:45PM +0200, Michael Wiedmann wrote:
>> What is the proposed handling of a package whose name has changed?
>> (e.g.: the author of foo-0.1.tar.gz, Debian package foo_0.1-1_i386.deb,
>> changes the name of the package to bar-0.2
On Sat, May 26, 2001 at 10:04:45PM +0200, Michael Wiedmann wrote:
> What is the proposed handling of a package whose name has changed?
> (e.g.: the author of foo-0.1.tar.gz, Debian package foo_0.1-1_i386.deb,
> changes the name of the package to bar-0.2.tar.gz)
>
> The only thing which comes to m
On Sat, May 26, 2001 at 10:04:45PM +0200, Michael Wiedmann wrote:
> What is the proposed handling of a package whose name has changed?
> (e.g.: the author of foo-0.1.tar.gz, Debian package foo_0.1-1_i386.deb,
> changes the name of the package to bar-0.2.tar.gz)
>
> The only thing which comes to
What is the proposed handling of a package whose name has changed?
(e.g.: the author of foo-0.1.tar.gz, Debian package foo_0.1-1_i386.deb,
changes the name of the package to bar-0.2.tar.gz)
The only thing which comes to my mind is treating the old package
as 'conflict' for the new one, but there
What is the proposed handling of a package whose name has changed?
(e.g.: the author of foo-0.1.tar.gz, Debian package foo_0.1-1_i386.deb,
changes the name of the package to bar-0.2.tar.gz)
The only thing which comes to my mind is treating the old package
as 'conflict' for the new one, but there
27 matches
Mail list logo
