Joachim Schrod | 1 Oct 11:15 2008
Picon

Re: tomcat6 package on non-RH/Fedora systems

Jesse Keating wrote:
> On Mon, 2008-09-29 at 15:06 -0400, Jason Corley wrote:
>> Changed from file based Requires: to package name thereby breaking
>> non-Fedora/RHEL derived distros.  SuSE does not have /sbin/chkconfig
>> in a package named chkconfig nor is there a package named initscripts
>> (I've not used SuSE in years so I'm just going by what was said in the
>> email).
>> Jason
> 
> I talked with spot, and it was an incorrect assumption that those file
> requires were dragging in the large 'filelist' metadata in yum repos.
> Turns out it isn't, and this change can be reverted.  Let me know if you
> want me to revert it in Fedora specs.

I was away at a customer's site for the last week, so I succeeded 
only today to check the changed tomcat6 package (version 
6.0.18-3.jpp5).

It still has some Fedora-isms that I haven't resolved fully.

  -- The startup script is placed in /etc/rc.d/init.d/ and not in
     /etc/init.d/ as it is done in the tomcat6 package. This will
     break usage on SUSE and Debian-derived systems, as this
     directory does not exist there. (I used a symlink to get rid
     of that problem.)

  -- The startup script sources /etc/rc.d/init.d/functions to get
     status(), echo_success(), and other shell functions. This
     function collection does neither exist on SUSE nor on Debian.
     Using functions from CentOS doesn't work either as it expects
(Continue reading)

Will Tatam | 1 Oct 11:58 2008

jbossas-4.2.3-8.jpp5 - broken

dangling: /usr/share/jbossas/server/all/lib/jboss-jaxws-ext.jar ->
/usr/share/java/jbossws/jboss-jaxws-ext.jar
dangling: /usr/share/jbossas/server/default/lib/jboss-jaxws-ext.jar ->
/usr/share/java/jbossws/jboss-jaxws-ext.jar
dangling: /usr/share/jbossas/client/jboss-jaxws-ext.jar ->
/usr/share/java/jbossws/jboss-jaxws-ext.jar

when using

jbossws-2.0.1-3.SP2.6.jpp5

--

-- 
Will Tatam
Systems Architect
Red61

0845 867 2203 ext 103
Jason Corley | 1 Oct 17:02 2008
Picon

Re: tomcat6 package on non-RH/Fedora systems

On Wed, Oct 1, 2008 at 5:15 AM, Joachim Schrod <jschrod@...> wrote:
> It still has some Fedora-isms that I haven't resolved fully.

The only solution I can really think of is to fully lsb-ify the init
script.  A quick test of the following patch to the current init
script seems to work on CentOS 5.2:
    http://ryu.zarb.org/~jasonc/tomcat6-6.0.init.txt
Joachim, can you please test on SuSE (and btw, what version are you using)?

>  -- The startup script is placed in /etc/rc.d/init.d/ and not in
>     /etc/init.d/ as it is done in the tomcat6 package.

My personal interpretation is that LSB mandates /etc/init.d
installation for init scripts, but I've not found agreement to that
when I've brought it up in Fedora bugzilla in the past.  I think we
need to revert to installation into /etc/init.d/ for JPackage and we
will just have to have that point of divergence between Fedora and
JPackage.

Jason
bugzilla | 2 Oct 00:09 2008

Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla bug tracking system
(https://www.jpackage.org/bugzilla/) that require
attention.

All of these bugs are in the NEW or REOPENED state, and have not been
touched in 7 days or more.
You need to take a look at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to
    someone else. (Hint: if you don't know who to reassign it to, make
    sure that the Component field seems reasonable, and then use the
    "Reassign bug to default assignee of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark
it if you like!):
https://www.jpackage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/hcidOUDYf1g9hUCZPvPmw <at> public.gmane.org

Or, you can use the general query page, at 
https://www.jpackage.org/bugzilla/query.cgi

Appended below are the individual URLs to get to all of your NEW bugs
that haven't been touched for a week or more.
(Continue reading)

Ralph Apel | 2 Oct 07:33 2008
Picon

Re: jbossas BRs

What I really intended to ask for is:
Why do we need an "equals" (B)R for something like servlet_2_5_api?
Who is expecting catastrophic changes to occur from servletapi6-6.0.10
to servletapi6-6.0.11?
Aren't we being governed by some kind of non technicians (lawyers, may
be)?

On Thu, 2008-09-25 at 14:19 -0400, David Walluck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ralph Apel wrote:
> | error: Failed build dependencies:
> |         servletapi6-repolib = 0:6.0.10 is needed by
> | jbossas-4.2.3-3.jpp5.noarch
> |
> | Why?
> 
> In order to avoid adding a repolib to tomcat6, I built
> servletapi6-repolib from the same sources. That version is now at 6.0.18
> (to match the upstream tomcat6 version).
> 
> The problem is with the strict '=' instead of '>=', and that buildmagic
> expects exact versions. In this case, we say we are version 2.5-brew
> (the servlet api version, not the tomcat version), so relaxing this is safe.
> 
> I will fix it.
> 
> - --
> Sincerely,
(Continue reading)

Ralph Apel | 2 Oct 07:37 2008
Picon

jakarta-commons-lang 2.3

jakarta-commons-lang seems to be among the packages with "frozen
version", i.e. 2.1
There is a jakarta-commons-lang-2.3 in JPP-1.7 but in the QA system this
package has been explicitly excluded from use.
As a consequence, maven2-plugin-enforcer cannot currently be used. Its
use must be patched out, or it might possibly be patched to work with
commons-lang-2.1..
But, who needs maven2-plugin-enforcer anyway? :-(  
Joachim Schrod | 2 Oct 12:35 2008
Picon

Re: tomcat6 package on non-RH/Fedora systems

Jason Corley wrote:
> On Wed, Oct 1, 2008 at 5:15 AM, Joachim Schrod <jschrod@...> wrote:
>> It still has some Fedora-isms that I haven't resolved fully.
> 
> The only solution I can really think of is to fully lsb-ify the init
> script.  A quick test of the following patch to the current init
> script seems to work on CentOS 5.2:
>     http://ryu.zarb.org/~jasonc/tomcat6-6.0.init.txt
> Joachim, can you please test on SuSE

Works like a charm, great!

One proposal, though: The usage message is missing its line end, 
owing to "echo -n". I've attached a patch, trivial as it is.

 > (and btw, what version are you using)?

That's on SUSE 10.3. It also works on 10.0 and 10.1, I just tried.
But I've got no 11.0 here with JPackage installed, sorry.

Thanks for the fast reaction!

	Joachim

--

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod				Email: jschrod@...
Roedermark, Germany
(Continue reading)

Jason Corley | 2 Oct 15:48 2008
Picon

Re: tomcat6 package on non-RH/Fedora systems

David pushed a new package with a modified initscript that included
the echos.  I haven't tested yet but the diff looked fine to me.  Let
us know how it works for you.
Jason

On Thu, Oct 2, 2008 at 6:35 AM, Joachim Schrod <jschrod@...> wrote:
> Jason Corley wrote:
>>
>> On Wed, Oct 1, 2008 at 5:15 AM, Joachim Schrod <jschrod@...> wrote:
>>>
>>> It still has some Fedora-isms that I haven't resolved fully.
>>
>> The only solution I can really think of is to fully lsb-ify the init
>> script.  A quick test of the following patch to the current init
>> script seems to work on CentOS 5.2:
>>    http://ryu.zarb.org/~jasonc/tomcat6-6.0.init.txt
>> Joachim, can you please test on SuSE
>
> Works like a charm, great!
>
> One proposal, though: The usage message is missing its line end, owing to
> "echo -n". I've attached a patch, trivial as it is.
>
>> (and btw, what version are you using)?
>
> That's on SUSE 10.3. It also works on 10.0 and 10.1, I just tried.
> But I've got no 11.0 here with JPackage installed, sorry.
>
> Thanks for the fast reaction!
>
(Continue reading)

Fernando Nasser | 2 Oct 16:40 2008
Picon

Re: jbossas BRs

Ralph Apel wrote:
> What I really intended to ask for is:
> Why do we need an "equals" (B)R for something like servlet_2_5_api?
> Who is expecting catastrophic changes to occur from servletapi6-6.0.10
> to servletapi6-6.0.11?

= for servlet_2_5_api

 >= for servletapi6

All that needs to be enforced in this case is the API level.

We are already making sure JPP 5.0 has compatible packages so your JBoss 
AS does not screw up your customers data ;-)

> Aren't we being governed by some kind of non technicians (lawyers, may
> be)?
> 

On the contrary, the recommendation to keep the dependencies as close as 
possible to what has been tested, conformance tested, and is supported 
by the upstream developers come only from these strictly technical 
people, and the most authoritative ones you can find...

> On Thu, 2008-09-25 at 14:19 -0400, David Walluck wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Ralph Apel wrote:
>> | error: Failed build dependencies:
(Continue reading)

Fernando Nasser | 2 Oct 16:46 2008
Picon

Re: jakarta-commons-lang 2.3

Ralph Apel wrote:
> jakarta-commons-lang seems to be among the packages with "frozen
> version", i.e. 2.1
> There is a jakarta-commons-lang-2.3 in JPP-1.7 but in the QA system this
> package has been explicitly excluded from use.
> As a consequence, maven2-plugin-enforcer cannot currently be used. Its
> use must be patched out, or it might possibly be patched to work with
> commons-lang-2.1..

You know, if a change from 2.3 to 2.1 breaks maven2-plugin-enforcer, who 
can tell how many of our JPP packages will be broken by a lang 2.3?

If you can prove you can rebuild all JPP 5.0 packages that depend on 
commons lang to 2.3 I'd vote that we upgrade.  It seems it is used in 
the JBoss AS indirectly (used to build xstream, which is needed by 
picocontainer etc., very low in the chain).

BTW, JBoss AS 5 CR2 uses commons-lang 2.3 in the build.

Cheers,
Fernando

Gmane