Re: Tomcat and MySQL

Doug Carter wrote:
> On Thu, Nov 13, 2008 at 10:57:06AM -0500, Fernando Nasser wrote:
>   
>> Jason Corley wrote:
>>     
>>> On Thu, Nov 13, 2008 at 9:46 AM, Doug Carter <dcarter@...> 
>>> wrote:
>>>       
>>>> I can manually copy the mysql jar to the common/lib location, but I'd
>>>> rather not do things manually like this, and use jpackage to configure
>>>> it for me. Has anyone done this? Any clues on how to proceed?
>>>>         
>>> /usr/bin/build-jar-repository /path/to/tomcatversion/libdir 
>>> mysql-connector-java
>>>
>>>       
>> I think Doug thinks our mysql-connector-java package should do that in 
>> %post or something....
>>
>> The problem is, will it do it for tomcat5?  or tomcat6?  And it must BR 
>> the one it will install the link...  Or maybe it can own those 
>> drectories as well and install the links regardless.
>>     
>
> Well, now that you mention it... that would be nice. After all, why
> download something if it can't be accessed? But I see your point about
> which tomcat version.
>
> Thanks a lot to both of you,
>

Re: Tomcat and MySQL

Yeah it's definitely an issue of scale.  At some point we have to
expect that sysadmins will... Well, admin the system. 
Jason

On Mon, Dec 1, 2008 at 10:37 AM, Will Tatam <will.tatam@...> wrote:
> Doug Carter wrote:
>>
>> On Thu, Nov 13, 2008 at 10:57:06AM -0500, Fernando Nasser wrote:
>>
>>>
>>> Jason Corley wrote:
>>>
>>>>
>>>> On Thu, Nov 13, 2008 at 9:46 AM, Doug Carter <dcarter@...>
>>>> wrote:
>>>>
>>>>>
>>>>> I can manually copy the mysql jar to the common/lib location, but I'd
>>>>> rather not do things manually like this, and use jpackage to configure
>>>>> it for me. Has anyone done this? Any clues on how to proceed?
>>>>>
>>>>
>>>> /usr/bin/build-jar-repository /path/to/tomcatversion/libdir
>>>> mysql-connector-java
>>>>
>>>>
>>>
>>> I think Doug thinks our mysql-connector-java package should do that in
>>> %post or something....
>>>

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.

JPP 5 - Release ?

What it is we are waiting on for jpp5 ? Talk of a beta was some time ago ?

Given I've been happily running jpackage 5 in production systems for 
over a year , without really much in the way of issues, it's can't be 
too far away from being of use to the general public :)

--

-- 
Will Tatam
Systems Architect
Red61

0845 867 2203 ext 103 

_______________________________________________
JPackage-discuss mailing list
JPackage-discuss@...
https://www.zarb.org/mailman/listinfo/jpackage-discuss

Re: JPP 5 - Release ?

Will Tatam wrote:
> What it is we are waiting on for jpp5 ? Talk of a beta was some time ago ?
> 

The beta is there, it is just not browsable yet because I needed a db 
created and then had no time to do it.

We are waiting a full rebuild in mock, some of the packages in the beta 
were not built in mock and have even some missing BuildRequires as I've 
learned painfully.  Once that is done, we should ship JPP 5 and 
concentrate on JPP 6.

> Given I've been happily running jpackage 5 in production systems for 
> over a year , without really much in the way of issues, it's can't be 
> too far away from being of use to the general public :)
> 

You are right.  It is more like a good cleanup effort.

> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> JPackage-discuss mailing list
> JPackage-discuss@...
> https://www.zarb.org/mailman/listinfo/jpackage-discuss

Re: JPP 5 - Release ?

Fernando Nasser wrote:
> Will Tatam wrote:
>> What it is we are waiting on for jpp5 ? Talk of a beta was some time 
>> ago ?
>>
>
> The beta is there, it is just not browsable yet because I needed a db 
> created and then had no time to do it.
Surely better to clean 5 then rebuild rather than have a 5.0-beta that's 
the same as 5 that we then delete ?
>
> We are waiting a full rebuild in mock, some of the packages in the 
> beta were not built in mock and have even some missing BuildRequires 
> as I've learned painfully.  Once that is done, we should ship JPP 5 
> and concentrate on JPP 6.
>
We can tell what's been built in mock by checking the build host

Any existing magic to build the packages in the right order, inc 
bootstraping ?

p.s good job I just ordered more ram for the build server :)

--

-- 
Will Tatam
Systems Architect
Red61

0845 867 2203 ext 103 

Re: JPP 5 - Release ?

Will Tatam wrote:
> Fernando Nasser wrote:
>> Will Tatam wrote:
>>> What it is we are waiting on for jpp5 ? Talk of a beta was some time 
>>> ago ?
>>>
>>
>> The beta is there, it is just not browsable yet because I needed a db 
>> created and then had no time to do it.
> Surely better to clean 5 then rebuild rather than have a 5.0-beta that's 
> the same as 5 that we then delete ?

The releases are just snapshots taken with "cp -pr", they are frozen 
forever.  Any newer release comes as another snapshot from the current 
brach (another cp -pr).,  So there is only one live thing being working 
on which is the JPP-5 branch.

>>
>> We are waiting a full rebuild in mock, some of the packages in the 
>> beta were not built in mock and have even some missing BuildRequires 
>> as I've learned painfully.  Once that is done, we should ship JPP 5 
>> and concentrate on JPP 6.
>>
> We can tell what's been built in mock by checking the build host
> 
> Any existing magic to build the packages in the right order, inc 
> bootstraping ?
> 

No, but in theory we should have most of what is needed to rebuild 

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.

Re: JPP 5 - Release ?

>
>>>
>>> We are waiting a full rebuild in mock, some of the packages in the 
>>> beta were not built in mock and have even some missing BuildRequires 
>>> as I've learned painfully.  Once that is done, we should ship JPP 5 
>>> and concentrate on JPP 6.
>>>
>> We can tell what's been built in mock by checking the build host
>>
>> Any existing magic to build the packages in the right order, inc 
>> bootstraping ?
>>
>
> No, but in theory we should have most of what is needed to rebuild 
> everything already in JPP 5.0, as we have cut the umbilical cord with 
> JPP 1.7 a long time ago.  But as we never did the mass rebuild, there 
> can be still a few ones that we need to bring in.
That's not strictly true, at the moment we are still building with the 
1.7 bootstrap enabled.
As for the mass-rebuild. If it's our stated objective to be 100% mock 
built for the final release of 5.0 then should i add a hock to the 
rpmupload script that checks the build host ? This would ensure that 
uploaders are totally aware of this restriction

--

-- 
Will Tatam
Systems Architect
Red61

0845 867 2203 ext 103 

Re: JPP 5 - Release ?

Not that I think anyone would do this bit buildhost could be munged
(just change hostname on local box) so maybe we should add a couple of
checks.  Rpm version, buildhost, etc.
Jason

On 12/3/08, Will Tatam <will.tatam@...> wrote:
>>
>>>>
>>>> We are waiting a full rebuild in mock, some of the packages in the
>>>> beta were not built in mock and have even some missing BuildRequires
>>>> as I've learned painfully.  Once that is done, we should ship JPP 5
>>>> and concentrate on JPP 6.
>>>>
>>> We can tell what's been built in mock by checking the build host
>>>
>>> Any existing magic to build the packages in the right order, inc
>>> bootstraping ?
>>>
>>
>> No, but in theory we should have most of what is needed to rebuild
>> everything already in JPP 5.0, as we have cut the umbilical cord with
>> JPP 1.7 a long time ago.  But as we never did the mass rebuild, there
>> can be still a few ones that we need to bring in.
> That's not strictly true, at the moment we are still building with the
> 1.7 bootstrap enabled.
> As for the mass-rebuild. If it's our stated objective to be 100% mock
> built for the final release of 5.0 then should i add a hock to the
> rpmupload script that checks the build host ? This would ensure that
> uploaders are totally aware of this restriction
>