headers
Jason Corley | 1 Apr 2009 20:05
Picon

Re: jpackage java-1.6.0.13

For future reference, please use the list.  Plenty of people can work
on that package, it's likely someone could have pushed an update
sooner.  At any rate, I've got a nosrc package up for testing (all the
really hard packaging changes were done by Will Tatam, thankfully) at
the following url:

    http://ryu.zarb.org/~jasonc/packages/java-1.6.0-sun-1.6.0.13-1jpp.nosrc.rpm

If anyone can provide feedback (good, bad, or indifferent) that'd be
great.  This particular nosrc package now has Will's work to include
the x86_64 web plugin, which I imagine is of interest to some folks.
Jason

On Fri, Mar 27, 2009 at 6:32 AM, paul <paul@...> wrote:
> hi Jason -
>
>
> i've been hawking jpackage for an update to the jdk and notice that you make
> all the changes to the spec...
>
> great job!!!!
>
> i tried to rebuild the rpms by just changing the version number in the spec
> file and to no avail have not been able to build 13... i've been trying for
> the past three days and have come to ask...
>
> can you update the rpm for build 13 that was released and just bypass 12?
> that would be stellar...
>
> cheers
(Continue reading)

Permalink | Reply | 1 comment |
headers
Will Tatam | 1 Apr 2009 20:28

Re: jpackage java-1.6.0.13

Any also javaws for 64bit

Jason Corley wrote:
> For future reference, please use the list.  Plenty of people can work
> on that package, it's likely someone could have pushed an update
> sooner.  At any rate, I've got a nosrc package up for testing (all the
> really hard packaging changes were done by Will Tatam, thankfully) at
> the following url:
>
>     http://ryu.zarb.org/~jasonc/packages/java-1.6.0-sun-1.6.0.13-1jpp.nosrc.rpm
>
> If anyone can provide feedback (good, bad, or indifferent) that'd be
> great.  This particular nosrc package now has Will's work to include
> the x86_64 web plugin, which I imagine is of interest to some folks.
> Jason
>
> On Fri, Mar 27, 2009 at 6:32 AM, paul <paul@...> wrote:
>   
>> hi Jason -
>>
>>
>> i've been hawking jpackage for an update to the jdk and notice that you make
>> all the changes to the spec...
>>
>> great job!!!!
>>
>> i tried to rebuild the rpms by just changing the version number in the spec
>> file and to no avail have not been able to build 13... i've been trying for
>> the past three days and have come to ask...
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 2 Apr 2009 00:11
Favicon

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)

Permalink | Reply | 0 comments |
headers
Will Tatam | 2 Apr 2009 10:38

Re: jpackage java-1.6.0.13

That is not the plugin. Run rpm -ql pn the plugin package, as  I can't remember the full path, but it's the so
starting jp2

-original message-
Subject: Re: [JPackage-discuss] jpackage java-1.6.0.13
From: paul <paul@...>
Date: 02/04/2009 12:04 am

great! i just built and updated my rpms... eclipse, maven, tomcat, vuze 
and some other java apps all seem to be fine...

the java-plugin doesn't seem to load though in firefox-3.0.8-1.fc10... 
i've linked

/usr/lib/jvm/java-1.6.0-sun-1.6.0.13/jre/lib/amd64/libjavaplugin_jni.so

to my plugins directory and it never loads with firefox...

On 04/01/2009 02:28 PM, Will Tatam wrote:
> Any also javaws for 64bit
> 
> Jason Corley wrote:
>> For future reference, please use the list.  Plenty of people can work
>> on that package, it's likely someone could have pushed an update
>> sooner.  At any rate, I've got a nosrc package up for testing (all the
>> really hard packaging changes were done by Will Tatam, thankfully) at
>> the following url:
>>
>>     
>> http://ryu.zarb.org/~jasonc/packages/java-1.6.0-sun-1.6.0.13-1jpp.nosrc.rpm
(Continue reading)

Permalink | Reply | 1 comment |
headers
paul s | 2 Apr 2009 15:48
Favicon

Re: jpackage java-1.6.0.13

i'm not seeing any other library to be used for the plugin...

http://queuemail.com/rpm-ql-java-1.6.0-sun-plugin-1.6.0.13-1jpp.txt

i noticed that the alternatives is not set to use the plugin... the link
for /etc/alternatives/libjavaplugin.so.x86_64 is never created when the
rpm is installed...

also i can't say thank you enough for being so nice, i know everyone's
time is so valuable and i definitely don't want to come off wrong...
i'll be more then happy to build and test the rpms for you if i can
contribute in some way other then it "doesn't work"...

thank you.

cheers
paul

On 04/02/2009 04:38 AM, Will Tatam wrote:
> That is not the plugin. Run rpm -ql pn the plugin package, as  I can't remember the full path, but it's the so
starting jp2
> 
> -original message-
> Subject: Re: [JPackage-discuss] jpackage java-1.6.0.13
> From: paul <paul@...>
> Date: 02/04/2009 12:04 am
> 
> great! i just built and updated my rpms... eclipse, maven, tomcat, vuze 
> and some other java apps all seem to be fine...
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
paul s | 2 Apr 2009 17:44
Favicon

Re: jpackage java-1.6.0.13

i see, i hardly ever used the plug-in either until recently... and use 
to do all that nspluginwrapper mumbo jumbo till i noticed the plug-in 
was available from using an openjdk rpm...

when i was getting the build errors for javaws and seeing that it builds 
the plug-in rpm i was hoping sun finally made it 64bit...

so using the open-jdk plug-in is fine and both jre's installed are 
synced at thirteen, i'm happy... :-)

On 04/02/2009 10:19 AM, Jason Corley wrote:
> The alternatives bit might be a problem, but the plugins available
> differ between x64 and i586 sun releases.  To make sure it wasn't a
> packaging issue I checked with freshly exploded Sun .bins for i586 and
> x64:
> 
> $
> $ find jdk1.6.0_13.x64 -iname "libjavaplugin*"
> jdk1.6.0_13.x64/jre/lib/amd64/libjavaplugin_jni.so
> $
> $ find jdk1.6.0_13.i586 -iname "libjavaplugin*"
> jdk1.6.0_13.i586/jre/lib/i386/libjavaplugin_nscp_gcc29.so
> jdk1.6.0_13.i586/jre/lib/i386/libjavaplugin_nscp.so
> jdk1.6.0_13.i586/jre/lib/i386/libjavaplugin_jni.so
> jdk1.6.0_13.i586/jre/plugin/i386/ns7/libjavaplugin_oji.so
> jdk1.6.0_13.i586/jre/plugin/i386/ns7-gcc29/libjavaplugin_oji.so
> $
> 
> Honestly I have no idea what the solution is, I don't use the plugin myself.
> Jason
(Continue reading)

Permalink | Reply | 11 comments |
headers
bugzilla | 3 Apr 2009 00:11
Favicon

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)

Permalink | Reply | 0 comments |
headers
Fernando Nasser | 3 Apr 2009 15:37
Picon
Favicon

Re: java-1.5.0-sun-compat

Hi Christophe,

Please use the list (in cc.), the first available person will do it, 
otherwise you will have to wait until I have some free time ;-)

Best regards,
Fernando

Christophe Anzile wrote:
> hi,
> would you mind upload java-1.5.0-sun-compat-1.5.0.18
> [as the sun jdk 1.5.0.17 is no more available]
> thanx.
Permalink | Reply | 0 comments |
headers
bugzilla | 4 Apr 2009 00:12
Favicon

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)

Permalink | Reply | 0 comments |
headers
bugzilla | 5 Apr 2009 00:12
Favicon

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)

Permalink | Reply | 0 comments |

Gmane