Hi,
I'm the author of GtkGamma (available at http://gtkgamma.sf.net/) and I'd like
to be an official maintainer for the Debian package myself. I've built a binary
.deb which I've uploaded to the project's site at SF (see above). Everything
necessary to build it is included in the tarball.
I'd
On Sat, Nov 24, 2001 at 09:49:29PM -0500, Adam C Powell IV wrote:
> >>Can I "Build-Depends: ccc [alpha], cfal [alpha]" and still have the
> >>source package in main?
> >>
> >No, that would violate policy (2.1.2).
> >
> Right, thanks for pointing this out (I need to RTFP :-). So the source
> would
James Troup wrote:
Adam C Powell IV <[EMAIL PROTECTED]> writes:
Can I "Build-Depends: ccc [alpha], cfal [alpha]" and still have the
source package in main?
No, that would violate policy (2.1.2).
Right, thanks for pointing this out (I need to RTFP :-). So the source
would become contrib, b
Hi,
I'm the author of GtkGamma (available at http://gtkgamma.sf.net/) and I'd like to be
an official maintainer for the Debian package myself. I've built a binary .deb which
I've uploaded to the project's site at SF (see above). Everything necessary to build
it is included in the tarball.
I'
On Sat, Nov 24, 2001 at 09:49:29PM -0500, Adam C Powell IV wrote:
> >>Can I "Build-Depends: ccc [alpha], cfal [alpha]" and still have the
> >>source package in main?
> >>
> >No, that would violate policy (2.1.2).
> >
> Right, thanks for pointing this out (I need to RTFP :-). So the source
> woul
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> Can I "Build-Depends: ccc [alpha], cfal [alpha]" and still have the
> source package in main?
No, that would violate policy (2.1.2).
--
James
James Troup wrote:
>Adam C Powell IV <[EMAIL PROTECTED]> writes:
>
>>Can I "Build-Depends: ccc [alpha], cfal [alpha]" and still have the
>>source package in main?
>>
>No, that would violate policy (2.1.2).
>
Right, thanks for pointing this out (I need to RTFP :-). So the source
would become con
Greetings,
Having got the non-free cfal (Compaq Fortran for Linux Alpha, yes, the
acronym is backwards :-) compiler to work using my contrib Debian
packaging (realplayer-style RPM unpacker), I built PETSc using it, and
WOW, is it FAST! On a 600 MHz ev5, it is more than 2.5 times as fast
per
I'm the maintainer of the libming packages.
Libming has Python bindings, so i made a package python2-ming.
The Python policy has changed now, and Python 2.1 is now the default
python, so i recompiled my package.
Could someone with python experience (i havn't used python much; i don't
like the ind
I'm the maintainer of the libming packages.
Libming has Python bindings, so i made a package python2-ming.
The Python policy has changed now, and Python 2.1 is now the default
python, so i recompiled my package.
Could someone with python experience (i havn't used python much; i don't
like the in
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> Can I "Build-Depends: ccc [alpha], cfal [alpha]" and still have the
> source package in main?
No, that would violate policy (2.1.2).
--
James
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
Greetings,
Having got the non-free cfal (Compaq Fortran for Linux Alpha, yes, the
acronym is backwards :-) compiler to work using my contrib Debian
packaging (realplayer-style RPM unpacker), I built PETSc using it, and
WOW, is it FAST! On a 600 MHz ev5, it is more than 2.5 times as fast
per
On Fri, Nov 23, 2001 at 10:27:47AM -0800, Sean 'Shaleh' Perry wrote:
>
> On 23-Nov-2001 Alexander Karelas wrote:
> > Are there PDF versions (or any version other than HTML for that matter) of
> > the Debian policy manuals somewhere? I would like to print them.
> >
>
> policy.sgml.gz is the orig
On Fri, Nov 23, 2001 at 10:27:47AM -0800, Sean 'Shaleh' Perry wrote:
>
> On 23-Nov-2001 Alexander Karelas wrote:
> > Are there PDF versions (or any version other than HTML for that matter) of
> > the Debian policy manuals somewhere? I would like to print them.
> >
>
> policy.sgml.gz is the origi
Hi,
This bug is about the pcscd daemon left running afer purging the pcscd
package.
I'm not able to reproduce this error on an Intel machine. Maybe it's an
Sparc specific bug. I don't have such a machine at hand and thats why I'm
asking for help on this list.
The pcscd.prerm does stop the procce
15 matches
Mail list logo
