bugzilla | 2 Dec 00:27 2011

Your Bugzilla bug list 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 orREOPENED 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 7 days or more.
(Continue reading)

bugzilla | 3 Dec 00:23 2011

Your Bugzilla bug list 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 orREOPENED 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 7 days or more.
(Continue reading)

bugzilla | 4 Dec 00:23 2011

Your Bugzilla bug list 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 orREOPENED 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 7 days or more.
(Continue reading)

bugzilla | 5 Dec 00:20 2011

Your Bugzilla bug list 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 orREOPENED 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 7 days or more.
(Continue reading)

bugzilla | 6 Dec 00:23 2011

Your Bugzilla bug list 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 orREOPENED 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 7 days or more.
(Continue reading)

Boris Folgmann | 6 Dec 11:42 2011
Picon

JPackage 6 on RHEL/CentOS 6

Hi,

I'm currently setting up some new systems with CentOS 6.1. Some of the 
included Java RPMs are fairly old. See e.g.
https://bugzilla.redhat.com/show_bug.cgi?id=759411

I also thought about using now tomcat 7 for production, which is in 
JPackage 6. But it's hard to get some info about how stable jpp6 is. I 
can't see any developer discussion here for the last years. Only bugzilla 
mails. Do you have a second secret mailing list? Is there a road map about 
releasing jpp6?

I could help updating RPMs for certain libraries I'm using, but it seems to 
be a little bit hard to get involved. I also suggest to set up a Wiki on 
jpackage.org to develop some pages about advice on best practices when 
using jpp.

Anyway, I've tried the jpp6 repo and got this
Error: Package: eclipse-svnkit-1.3.0-3.el6.x86_64 
( <at> anaconda-CentOS-201106060106.x86_64/6.0)
            Requires: svnkit = 1.3.0
            Removing: svnkit-1.3.0-3.el6.x86_64 
( <at> anaconda-CentOS-201106060106.x86_64/6.0)
                svnkit = 1.3.0-3.el6
            Updated By: svnkit-1.3.5-2.jpp6.noarch (jpackage)
                svnkit = 1.3.5-2.jpp6

Which can be solved by removing the affected RPMs (if one doesn't need them):
rpm -e eclipse-svnkit eclipse-subclipse
(Continue reading)

David Walluck | 6 Dec 17:42 2011

Re: JPackage 6 on RHEL/CentOS 6

On 12/06/2011 05:42 AM, Boris Folgmann wrote:
> I'm currently setting up some new systems with CentOS 6.1. Some of the 
> included Java RPMs are fairly old. See e.g.
> https://bugzilla.redhat.com/show_bug.cgi?id=759411

Java packages in RHEL/Fedora are not only old, but they have broken
maven support, so the packages aren't even usable for building against.

This situation has not seemed to improve all that much in RHEL 7 either
(since either the packages aren't being updated or the lack of proper
maven support is being carried along).

My guess would have been that you will see the eclipse packages be
maintained and the others stagnate, but your issue with svnkit seems to
have disproved that.

> Anyway, I've tried the jpp6 repo and got this
> Error: Package: eclipse-svnkit-1.3.0-3.el6.x86_64 
> ( <at> anaconda-CentOS-201106060106.x86_64/6.0)
>             Requires: svnkit = 1.3.0
>             Removing: svnkit-1.3.0-3.el6.x86_64 
> ( <at> anaconda-CentOS-201106060106.x86_64/6.0)
>                 svnkit = 1.3.0-3.el6
>             Updated By: svnkit-1.3.5-2.jpp6.noarch (jpackage)
>                 svnkit = 1.3.5-2.jpp6
> 
> Which can be solved by removing the affected RPMs (if one doesn't need them):
> rpm -e eclipse-svnkit eclipse-subclipse

I would have thought that yum should be able to upgrade svnkit by
(Continue reading)

R.Apel | 6 Dec 18:49 2011

Re: JPackage 6 on RHEL/CentOS 6

Hi Boris,

I built and uploaded Tomcat7 some weeks ago. You have seen it at
6.0/generic/devel/SRPMS/tomcat7-7.0.22-1.jpp6.src.rpm 

Having pushed it to "/devel/" means that I haven not thoroughly tested it yet.

But it is based on the widely (at least by me) used tomcat6 package set and the smoke test I did on my box after
building went fine.

Our intention when putting some package into /devel/ is an invitation to begin using it and report any
problems that may arise.

That said, I can only stress what David wrote already: 
On any platform, be it private or at a customer's, I exclude any java stuff from RHEL/CentOS/Fedora repos
(except eclipse packages may be).

Btw, JPP-6 has not been released yet. We are working now in order to make it self contained, at least from the
run time point of view. After achieving that goal, the build time selfcontainedness is still another story.

Regards
Ralph 

-----Urspr√ľngliche Nachricht-----
Von: jpackage-discuss-bounces@...
[mailto:jpackage-discuss-bounces <at> zarb.org] Im Auftrag von Boris Folgmann
Gesendet: Dienstag, 6. Dezember 2011 11:42
An: jpackage-discuss@...
Betreff: [JPackage-discuss] JPackage 6 on RHEL/CentOS 6

(Continue reading)

bugzilla | 7 Dec 00:24 2011

Your Bugzilla bug list 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 orREOPENED 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 7 days or more.
(Continue reading)

Ralph Apel | 7 Dec 00:17 2011
Picon

Re: JPackage 6 on RHEL/CentOS 6

These are (today) the counts of missing packages in JPP-6 (free) to be
self contained (at run time); focussing on apache-felix obviously...

      1            Requires: aelfred
      1            Requires: anttex >= 0.2-3jpp
      1            Requires: antunit
      1            Requires: apacheds-daemon-bootstrappers
      1            Requires: apache-ibatis-abator-core
      1            Requires: apache-ibatis-sqlmap
      1            Requires: aspectwerkz >= 2.0
      1            Requires: castor0 >= 0.9.5
      1            Requires: cpptasks >= 1.0
      1            Requires: cssparser
      1            Requires: cyberdomo-upnp-stack
      1            Requires: cyberdomo-upnp-stack-jdk13
      1            Requires: dbunit >= 2.2
      1            Requires: dnsjava
      1            Requires: docbook-xsl-java-xalan
      1            Requires: emma
      1            Requires: fit >= 1.1
      1            Requires: grizzly17
      1            Requires: hessian >= 3.0.8
      1            Requires: hibernate2
      1            Requires: hibernate2-tools
      1            Requires: jakarta-commons-grant >= 1.0.b4
      1            Requires: jakarta-commons-jelly-tags-antlr >=
1.0-5jpp
      1            Requires: jakarta-commons-jelly-tags-fmt >= 1.0-5jpp
      1            Requires: jakarta-commons-jelly-tags-http >= 1.0-5jpp
      1            Requires: jakarta-commons-jelly-tags-swing >=
(Continue reading)


Gmane