On Sat, Feb 24, 2001 at 08:46:18PM +0100, Josip Rodin wrote:
> On Sat, Feb 24, 2001 at 01:43:38PM +, Patrick Caulfield wrote:
> > I've taken one of my packages (dnet-common) and turned its only binary into
> > a
> > shell script so that the package is now architecture independant.
> >
> > If
On Sat, Feb 24, 2001 at 08:46:18PM +0100, Josip Rodin wrote:
> On Sat, Feb 24, 2001 at 01:43:38PM +, Patrick Caulfield wrote:
> > I've taken one of my packages (dnet-common) and turned its only binary into a
> > shell script so that the package is now architecture independant.
> >
> > If I ju
On Sat, Feb 24, 2001 at 01:43:38PM +, Patrick Caulfield wrote:
> I've taken one of my packages (dnet-common) and turned its only binary into a
> shell script so that the package is now architecture independant.
>
> If I just upload the new dnet-common_2.09-1_all.deb, will it remove the
> exis
On Sat, Feb 24, 2001 at 01:43:38PM +, Patrick Caulfield wrote:
> I've taken one of my packages (dnet-common) and turned its only binary into a
> shell script so that the package is now architecture independant.
>
> If I just upload the new dnet-common_2.09-1_all.deb, will it remove the existi
I've taken one of my packages (dnet-common) and turned its only binary into a
shell script so that the package is now architecture independant.
If I just upload the new dnet-common_2.09-1_all.deb, will it remove the existing
dnet-common_2.08-1_i386.deb or do I have to do anything special?
patrick
I've taken one of my packages (dnet-common) and turned its only binary into a
shell script so that the package is now architecture independant.
If I just upload the new dnet-common_2.09-1_all.deb, will it remove the existing
dnet-common_2.08-1_i386.deb or do I have to do anything special?
patric
6 matches
Mail list logo