headers
Will Tatam | 1 Nov 2007 16:27

JPP 5.0 - bouncycastle

Can someone bump the release up by one on the 5.0 build of bouncycastle
up by one as they appear to have forgotten to do this when the updated
to support jdk 1.5 and jdk.1.6 and so you end up with yum trying to
install the version from the JPP 1.7 which requires jdk 1.4

---> Package bouncycastle.noarch 0:1.37-4jpp set to be updated
--> Processing Dependency: bouncycastle-jdk1.4 = 1.37-4jpp for package:
bouncycastle
--> Running transaction check
---> Package bouncycastle-jdk1.4.noarch 0:1.37-4jpp set to be updated
--> Processing Dependency: java < 1.5.0 for package: bouncycastle-jdk1.4
--> Finished Dependency Resolution
Error: Missing Dependency: java < 1.5.0 is needed by package
bouncycastle-jdk1.4

--

-- 
Will Tatam
Systems Architect
Red61

0845 867 2203 ext 103
Permalink | Reply | 7 comments |
headers
R.Apel | 1 Nov 2007 16:33
Favicon

Re: JPP 5.0 - bouncycastle

No need to use the bouncycastle main package.
Simply use bouncycastle-jdk1.5 if that is what you need.

I will bump the release anyway 

-----Ursprüngliche Nachricht-----
Von: jpackage-discuss-bounces@...
[mailto:jpackage-discuss-bounces <at> zarb.org] Im Auftrag von Will Tatam
Gesendet: Donnerstag, 1. November 2007 16:28
An: jpackage-discuss@...
Betreff: [JPackage-discuss] JPP 5.0 - bouncycastle

Can someone bump the release up by one on the 5.0 build of bouncycastle up by one as they appear to have
forgotten to do this when the updated to support jdk 1.5 and jdk.1.6 and so you end up with yum trying to
install the version from the JPP 1.7 which requires jdk 1.4

---> Package bouncycastle.noarch 0:1.37-4jpp set to be updated
--> Processing Dependency: bouncycastle-jdk1.4 = 1.37-4jpp for package:
bouncycastle
--> Running transaction check
---> Package bouncycastle-jdk1.4.noarch 0:1.37-4jpp set to be updated
--> Processing Dependency: java < 1.5.0 for package: bouncycastle-jdk1.4 
--> Finished Dependency Resolution
Error: Missing Dependency: java < 1.5.0 is needed by package
bouncycastle-jdk1.4

--
Will Tatam
Systems Architect
Red61
(Continue reading)

Permalink | Reply | 4 comments |
headers
Richi Plana | 1 Nov 2007 16:43

Re: JPP 5.0 - bouncycastle

Does bouncycastly-jdk1.5 virtually provide bouncycastle and obsolete it?
What's the relationship of the two, anyway? The azureus package
explicity requires "bouncycastle".

On Thu, 2007-11-01 at 16:33 +0100, R.Apel <at> t-systems.com wrote:
> No need to use the bouncycastle main package.
> Simply use bouncycastle-jdk1.5 if that is what you need.
> 
> I will bump the release anyway 
> 
> -----Ursprüngliche Nachricht-----
> Von: jpackage-discuss-bounces <at> zarb.org [mailto:jpackage-discuss-bounces <at> zarb.org] Im Auftrag
von Will Tatam
> Gesendet: Donnerstag, 1. November 2007 16:28
> An: jpackage-discuss <at> zarb.org
> Betreff: [JPackage-discuss] JPP 5.0 - bouncycastle
> 
> Can someone bump the release up by one on the 5.0 build of bouncycastle up by one as they appear to have
forgotten to do this when the updated to support jdk 1.5 and jdk.1.6 and so you end up with yum trying to
install the version from the JPP 1.7 which requires jdk 1.4
> 
> ---> Package bouncycastle.noarch 0:1.37-4jpp set to be updated
> --> Processing Dependency: bouncycastle-jdk1.4 = 1.37-4jpp for package:
> bouncycastle
> --> Running transaction check
> ---> Package bouncycastle-jdk1.4.noarch 0:1.37-4jpp set to be updated
> --> Processing Dependency: java < 1.5.0 for package: bouncycastle-jdk1.4 
> --> Finished Dependency Resolution
> Error: Missing Dependency: java < 1.5.0 is needed by package
> bouncycastle-jdk1.4
(Continue reading)

Permalink | Reply | 3 comments |
headers
R.Apel | 1 Nov 2007 16:50
Favicon

Re: JPP 5.0 - bouncycastle

The bouncycastle main package only contains some .html and currently Requires the JPP-Release's 
bouncycastle-jdk1.X subpackage, that is, bouncycastle-jdk1.4 on JPP-1.7 and bouncycastle-jdk1.5 on JPP-5.0

$ export JAVA_HOME=/usr/lib/jvm/java-1.5.0
$ build-classpath bouncycastle
/usr/share/java-1.5.0/bouncycastle/bctsp-1.37.jar:/usr/share/java-1.5.0/bouncycastle/lcrypto-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcprov-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcmail-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcpg-1.37.jar
$ export JAVA_HOME=/usr/lib/jvm/java-1.4.2
$ build-classpath
bouncycastle
/usr/share/java-1.4.2/bouncycastle/bctsp-1.37.jar:/usr/share/java-1.4.2/bouncycastle/lcrypto-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcprov-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcmail-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcpg-1.37.jar 

-----Ursprüngliche Nachricht-----
Von: jpackage-discuss-bounces@...
[mailto:jpackage-discuss-bounces <at> zarb.org] Im Auftrag von Richi Plana
Gesendet: Donnerstag, 1. November 2007 16:44
An: Discussion about JPackage project
Betreff: Re: [JPackage-discuss] JPP 5.0 - bouncycastle

Does bouncycastly-jdk1.5 virtually provide bouncycastle and obsolete it?
What's the relationship of the two, anyway? The azureus package explicity requires "bouncycastle".

On Thu, 2007-11-01 at 16:33 +0100, R.Apel@... wrote:
> No need to use the bouncycastle main package.
> Simply use bouncycastle-jdk1.5 if that is what you need.
> 
> I will bump the release anyway
> 
> -----Ursprüngliche Nachricht-----
> Von: jpackage-discuss-bounces@... 
> [mailto:jpackage-discuss-bounces@...] Im Auftrag von Will Tatam
(Continue reading)

Permalink | Reply | 2 comments |
headers
Richi Plana | 1 Nov 2007 17:06

Re: JPP 5.0 - bouncycastle

So what should JPP-compliant packages who want the bouncycastle jars
actually RPM Require? Is there some smart way yum can figure out the
proper dependency packages to pull out based on a set of package Names,
Provides and Requires?

On Thu, 2007-11-01 at 16:50 +0100, R.Apel <at> t-systems.com wrote:
> The bouncycastle main package only contains some .html and currently Requires the JPP-Release's 
> bouncycastle-jdk1.X subpackage, that is, bouncycastle-jdk1.4 on JPP-1.7 and bouncycastle-jdk1.5 on JPP-5.0
> 
> $ export JAVA_HOME=/usr/lib/jvm/java-1.5.0
> $ build-classpath bouncycastle
> /usr/share/java-1.5.0/bouncycastle/bctsp-1.37.jar:/usr/share/java-1.5.0/bouncycastle/lcrypto-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcprov-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcmail-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcpg-1.37.jar
> $ export JAVA_HOME=/usr/lib/jvm/java-1.4.2
> $ build-classpath bouncycastle
>
/usr/share/java-1.4.2/bouncycastle/bctsp-1.37.jar:/usr/share/java-1.4.2/bouncycastle/lcrypto-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcprov-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcmail-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcpg-1.37.jar 
> 
> -----Ursprüngliche Nachricht-----
> Von: jpackage-discuss-bounces <at> zarb.org [mailto:jpackage-discuss-bounces <at> zarb.org] Im Auftrag
von Richi Plana
> Gesendet: Donnerstag, 1. November 2007 16:44
> An: Discussion about JPackage project
> Betreff: Re: [JPackage-discuss] JPP 5.0 - bouncycastle
> 
> Does bouncycastly-jdk1.5 virtually provide bouncycastle and obsolete it?
> What's the relationship of the two, anyway? The azureus package explicity requires "bouncycastle".
> 
> On Thu, 2007-11-01 at 16:33 +0100, R.Apel <at> t-systems.com wrote:
> > No need to use the bouncycastle main package.
> > Simply use bouncycastle-jdk1.5 if that is what you need.
(Continue reading)

Permalink | Reply | 1 comment |
headers
R.Apel | 1 Nov 2007 17:11
Favicon

Re: JPP 5.0 - bouncycastle

Yum will not know about the JDK(s) you have installed and/or want to use.
You must Require the appropriate BC rpm(s) according to the JDK(s) you are using. 

-----Ursprüngliche Nachricht-----
Von: Richi Plana [mailto:myjpackage@...] 
Gesendet: Donnerstag, 1. November 2007 17:07
An: Discussion about JPackage project
Betreff: Re: [JPackage-discuss] JPP 5.0 - bouncycastle

So what should JPP-compliant packages who want the bouncycastle jars actually RPM Require? Is there some
smart way yum can figure out the proper dependency packages to pull out based on a set of package Names,
Provides and Requires?

On Thu, 2007-11-01 at 16:50 +0100, R.Apel@... wrote:
> The bouncycastle main package only contains some .html and currently 
> Requires the JPP-Release's bouncycastle-jdk1.X subpackage, that is, 
> bouncycastle-jdk1.4 on JPP-1.7 and bouncycastle-jdk1.5 on JPP-5.0
> 
> $ export JAVA_HOME=/usr/lib/jvm/java-1.5.0 $ build-classpath 
> bouncycastle 
> /usr/share/java-1.5.0/bouncycastle/bctsp-1.37.jar:/usr/share/java-1.5.
> 0/bouncycastle/lcrypto-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcp
> rov-1.37.jar:/usr/share/java-1.5.0/bouncycastle/bcmail-1.37.jar:/usr/s
> hare/java-1.5.0/bouncycastle/bcpg-1.37.jar
> $ export JAVA_HOME=/usr/lib/jvm/java-1.4.2 $ build-classpath 
> bouncycastle 
> /usr/share/java-1.4.2/bouncycastle/bctsp-1.37.jar:/usr/share/java-1.4.
> 2/bouncycastle/lcrypto-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcp
> rov-1.37.jar:/usr/share/java-1.4.2/bouncycastle/bcmail-1.37.jar:/usr/s
> hare/java-1.4.2/bouncycastle/bcpg-1.37.jar
(Continue reading)

Permalink | Reply | 0 comments |
headers
Will Tatam | 1 Nov 2007 17:44

Re: JPP 5.0 - bouncycastle

should all these packages have deps to bouncycastle-jdk1.4 rather than
some virtual package provided by any of the jdk subpackages ?
e.g jxta and p2psockets

Will Tatam wrote:
> Can someone bump the release up by one on the 5.0 build of bouncycastle
> up by one as they appear to have forgotten to do this when the updated
> to support jdk 1.5 and jdk.1.6 and so you end up with yum trying to
> install the version from the JPP 1.7 which requires jdk 1.4
>
> ---> Package bouncycastle.noarch 0:1.37-4jpp set to be updated
> --> Processing Dependency: bouncycastle-jdk1.4 = 1.37-4jpp for package:
> bouncycastle
> --> Running transaction check
> ---> Package bouncycastle-jdk1.4.noarch 0:1.37-4jpp set to be updated
> --> Processing Dependency: java < 1.5.0 for package: bouncycastle-jdk1.4
> --> Finished Dependency Resolution
> Error: Missing Dependency: java < 1.5.0 is needed by package
> bouncycastle-jdk1.4
>
>   

--

-- 
Will Tatam
Systems Architect
Red61

0845 867 2203 ext 103
Permalink | Reply | 1 comment |
headers
R.Apel | 1 Nov 2007 17:52
Favicon

Re: JPP 5.0 - bouncycastle

You may use bouncycastle-provider as a Requires but this is provided by either.

Another possibility is Require bouncycastle and fine tune repo priorities:
Prio(1.7) < Prio(5.0) for a jpp17 mock root
Prio(1.7) > Prio(5.0) for a jpp50 mock root

-----Ursprüngliche Nachricht-----
Von: Will Tatam [mailto:will.tatam@...] 
Gesendet: Donnerstag, 1. November 2007 17:45
An: Discussion about JPackage project
Betreff: Re: [JPackage-discuss] JPP 5.0 - bouncycastle

should all these packages have deps to bouncycastle-jdk1.4 rather than some virtual package provided by
any of the jdk subpackages ?
e.g jxta and p2psockets

Will Tatam wrote:
> Can someone bump the release up by one on the 5.0 build of 
> bouncycastle up by one as they appear to have forgotten to do this 
> when the updated to support jdk 1.5 and jdk.1.6 and so you end up with 
> yum trying to install the version from the JPP 1.7 which requires jdk 
> 1.4
>
> ---> Package bouncycastle.noarch 0:1.37-4jpp set to be updated
> --> Processing Dependency: bouncycastle-jdk1.4 = 1.37-4jpp for package:
> bouncycastle
> --> Running transaction check
> ---> Package bouncycastle-jdk1.4.noarch 0:1.37-4jpp set to be updated
> --> Processing Dependency: java < 1.5.0 for package: 
> --> bouncycastle-jdk1.4 Finished Dependency Resolution
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 2 Nov 2007 00:08
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
Greg Wilkins | 2 Nov 2007 04:33
Gravatar

Jetty6 6.1.6rc1 RPMS


Hi all,

I've spruced up the SRPMS for jetty 6.1.6rc1 a little bit. Main additions
are better capture of stderr/stdout into files that rollover
and a demos RPM that includes some webapps to show how it works.

What I would like to get some help with for this release or the next,
is how to build some native code.  We have a setuid module
that needs the maven2 native plugin to build.  If we can get this
built then we could make an i386 RPM that had the setuid code
and jetty could do the open port 80 and then change to jetty user
thing.

Also what is the path from having a jpackage in the devel repo
to having it listed on your website?

cheers

--

-- 
Greg Wilkins<gregw@...>                       US:  +1  3104915462
http://www.webtide.com           UK: +44(0)2079932589 AU: +61(0)417786631
Permalink | Reply | 3 comments |

Gmane