The "Replaces:" Field

2003-02-04 Thread David Lloyd
I don't know if this is the right forum to ask, but I want to replace: [EMAIL PROTECTED]:/usr/share/apps/ksplash/pics$ ls splash_bottom.pngsplash_top.png splash_active_bar.png splash_inactive_bar.png splash_top.png.backup ..with my own but they are owned by "kdeb

The "Replaces:" Field

2003-02-04 Thread David Lloyd
I don't know if this is the right forum to ask, but I want to replace: lloy0076@cirith:/usr/share/apps/ksplash/pics$ ls splash_bottom.pngsplash_top.png splash_active_bar.png splash_inactive_bar.png splash_top.png.backup ..with my own but they are owned by "kdebas

Re: PythonCard packaging advice?

2003-02-04 Thread Kenneth Pronovici
> In general, you have a single source package (e.g. python-pythoncard) which > builds/installs for each available Python version (and Build-Depends on the > -dev version for each of those, obviously) into a python-pythoncard > package, and an empty python-pythoncard package that Depends on the > c

Re: PythonCard packaging advice?

2003-02-04 Thread Kenneth Pronovici
> > > This is getting a bit more complicated than I expected it to be. I'd > > > appreciate any advice you can give me. > > I don't know why you split docs and samples, I'd put them in one package, > > the samples go into /usr/share/doc//examples/. The doc package > > depending on either of the li

Re: PythonCard packaging advice?

2003-02-04 Thread Thomas Wouters
On Tue, Feb 04, 2003 at 10:59:17AM -0600, Kenneth Pronovici wrote: > > > I've now noticed that this doesn't conform to policy and I'm a little > > > confused about what packages I should provide. > > Only the name of the module package is against policy - it should be > > python-pythoncard. > I'm

Re: PythonCard packaging advice?

2003-02-04 Thread Kenneth Pronovici
> In general, you have a single source package (e.g. python-pythoncard) which > builds/installs for each available Python version (and Build-Depends on the > -dev version for each of those, obviously) into a python-pythoncard > package, and an empty python-pythoncard package that Depends on the > c

Re: PythonCard packaging advice?

2003-02-04 Thread Kenneth Pronovici
> > > This is getting a bit more complicated than I expected it to be. I'd > > > appreciate any advice you can give me. > > I don't know why you split docs and samples, I'd put them in one package, > > the samples go into /usr/share/doc//examples/. The doc package > > depending on either of the li

Re: PythonCard packaging advice?

2003-02-04 Thread Thomas Wouters
On Tue, Feb 04, 2003 at 10:59:17AM -0600, Kenneth Pronovici wrote: > > > I've now noticed that this doesn't conform to policy and I'm a little > > > confused about what packages I should provide. > > Only the name of the module package is against policy - it should be > > python-pythoncard. > I'm

Re: PythonCard packaging advice?

2003-02-04 Thread Kenneth Pronovici
> > I've now noticed that this doesn't conform to policy and I'm a little > > confused about what packages I should provide. > Only the name of the module package is against policy - it should be > python-pythoncard. I'm going to take this to mean python2.2-pythoncard/python2.3-pythoncard based o

Re: PythonCard packaging advice?

2003-02-04 Thread Kenneth Pronovici
> > I've now noticed that this doesn't conform to policy and I'm a little > > confused about what packages I should provide. > Only the name of the module package is against policy - it should be > python-pythoncard. I'm going to take this to mean python2.2-pythoncard/python2.3-pythoncard based o

Re: PythonCard packaging advice?

2003-02-04 Thread Martin Sjögren
tis 2003-02-04 klockan 12.46 skrev Bastian Kleineidam: > > This is getting a bit more complicated than I expected it to be. I'd > > appreciate any advice you can give me. > I don't know why you split docs and samples, I'd put them in one package, > the samples go into /usr/share/doc//examples/. Th

Re: PythonCard packaging advice?

2003-02-04 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Feb 03, 2003 at 03:38:11PM -0600, Kenneth Pronovici wrote: > I've now noticed that this doesn't conform to policy and I'm a little > confused about what packages I should provide. Only the name of the module package is against policy - it shou

Re: PythonCard packaging advice?

2003-02-04 Thread Martin Sjögren
tis 2003-02-04 klockan 12.46 skrev Bastian Kleineidam: > > This is getting a bit more complicated than I expected it to be. I'd > > appreciate any advice you can give me. > I don't know why you split docs and samples, I'd put them in one package, > the samples go into /usr/share/doc//examples/. Th

Re: PythonCard packaging advice?

2003-02-04 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Feb 03, 2003 at 03:38:11PM -0600, Kenneth Pronovici wrote: > I've now noticed that this doesn't conform to policy and I'm a little > confused about what packages I should provide. Only the name of the module package is against policy - it shou

Re: Warning about Debian New Maintainer Application

2003-02-04 Thread tony mancill
On Tue, 4 Feb 2003, Craig Small wrote: > On Mon, Feb 03, 2003 at 11:10:48AM +0300, Shiju p. Nair wrote: > > Am currently mainatains two packages ( libnet-easytcp-perl & libmng ) > > both sponsored by Tony Mancil and am interested in adopting more > > orphaned packages. But Tony no longer responds