Hi,
I'm not sure I really sure I properly understand the consequences of those
annoucements, but I'm sure I appreciate that fop & batik are part of
Debian.
Any risk that it won't be the case in the future? Anything I can do to
avoid this?
Thanks, Eric
--
Eric de France, d'Allemagne et de Navar
[Eric Lavarde]
> I'm not sure I really sure I properly understand the consequences of those
> annoucements, but I'm sure I appreciate that fop & batik are part of
> Debian.
>
> Any risk that it won't be the case in the future? Anything I can do to
> avoid this?
You can review the bugs listed in h
On Fri, 2006-09-15 at 16:21 -0400, Darrin Thompson wrote:
> On Fri, 2006-09-15 at 13:32 -0400, Darrin Thompson wrote:
> > The only way I can make this process die:
> >
> > * Install tomcat under base-config/tasksel.
> > * The java invocation must be backgrounded with "&"
>
> I'm starting to t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'd like to have your opinion about dropping tomcat5 from the archive
and only use tomcat5.5.
Reason:
Tomcat5 is not developped actively upstream so it'll be hard to maintain
if there are security issues.
Plan:
1° List of packages that nee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
> ...and the same goes for dom4j.
if you intend to co-maintain with pkg-java, it's an excellent idea :-D
Go Marcus go! ;-)
Thanks for your help.
- --
Arnaud Vandyck, STE fi, ULg
Formateur Cellule Programmation.
Java Trap: http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
> Hi,
>
> I've been looking into packaging Maven 1, for some other projects that still
> use it (such as Jackrabbit).
>
> Of course I hit the problem with bootstrapping, as the Maven 2 effort. But I
> hope it will be manageable.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Petter Reinholdtsen wrote:
> [Arnaud Vandyck]
>>> Why would a Depends: | be
>>> unacceptable for a package in main?
>> I don't know, maybe we need other DFSG expert on this issue.
>
> I am not a DFSG expert (who are, and how are they certified. :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Lavarde - Debian wrote:
>> Marcus Better wrote:
>>> what is the status of JaxMe (bug #296117)? Is it ready for upload?
[...]
> I can possibly answer it but I'm innocent: I asked a while ago the same
> question as Marcus, and the answer came from W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tomcat5.5 is now in unstable
Andrew Vaughan wrote:
> On Sunday 03 September 2006 05:46, you wrote:
>> what neds to be to done so it hits unstable/testing?
>>
> I don't know, but Arnaud Vandyck (who did the packaging) is subscribed to
> Debian-java, s
On Fri, 2006-09-15 at 16:21 -0400, Darrin Thompson wrote:
> On Fri, 2006-09-15 at 13:32 -0400, Darrin Thompson wrote:
> > The only way I can make this process die:
> >
> > * Install tomcat under base-config/tasksel.
> > * The java invocation must be backgrounded with "&"
>
> I'm starting to t
On Mon, Sep 18, 2006 at 06:15:12PM +0200, Arnaud Vandyck wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> I'd like to have your opinion about dropping tomcat5 from the archive
> and only use tomcat5.5.
>
> Reason:
>
> Tomcat5 is not developped actively upstream so it'll
On (18/09/06 22:34), Michael Koch wrote:
> On Mon, Sep 18, 2006 at 06:15:12PM +0200, Arnaud Vandyck wrote:
> > Hi all,
> >
> > I'd like to have your opinion about dropping tomcat5 from the archive
> > and only use tomcat5.5.
> >
> > Plan:
> >
> > 1° List of packages that need tomcat5 and does no
On Mon, Sep 18, 2006 at 03:35:15PM +0200, Petter Reinholdtsen wrote:
>
> [Eric Lavarde]
> > I'm not sure I really sure I properly understand the consequences of those
> > annoucements, but I'm sure I appreciate that fop & batik are part of
> > Debian.
> >
> > Any risk that it won't be the case in
13 matches
Mail list logo
