bugzilla | 2 Jun 00:10 2007

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 Jun 13:34 2007
Picon

Re: [JPackage-announce] [RPM (1.7)] qdox15-1.5-5jpp

Caution:
qdox-1.6.2 fails to parse certain java constructs; even
qdox-1.7-SNAPSHOT fails on these...
If you happen to encounter something similar to
syntax error  <at> [219,25] in
file:/path/BUILD/axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/WSDL2CodeMojo.java
followed by a qdox stack trace, try symlinking qdox15.jar to qdox.jar in
your build.

On Sat, 2007-06-02 at 12:39 +0200, Ralph Apel wrote:
> Name        : qdox15                       Relocations: (not relocatable)
> Version     : 1.5                               Vendor: JPackage Project
> Release     : 5jpp                          Build Date: Sat 02 Jun 2007 12:37:13 PM CEST
> Install Date: (not installed)               Build Host: altair.localdomain
> Group       : Development/Libraries/Java    Source RPM: (none)
> Size        : 426097      License: Apache-style Software License
> Signature   : (none)
> Packager    : Ralph Apel <r.apel@...>
> URL         : http://qdox.codehaus.org/
> Summary     : Extract class/interface/method definitions from sources
> Description :
> QDox is a high speed, small footprint parser
> for extracting class/interface/method definitions
> from source files complete with JavaDoc  <at> tags.
> It is designed to be used by active code
> generators or documentation tools.
> 
> ---------------
> Ralph Apel <r.apel at r-apel.de> 0:1.5-5jpp
> - Keep 1.5 to be able to parse certain constructs which
(Continue reading)

bugzilla | 3 Jun 00:10 2007

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)

Mary Ellen Foster | 3 Jun 10:24 2007
Picon

Using jpackage 1.7 on Fedora 7

If I enable jpackage 1.7 on a default install of Fedora 7 (with all
the Java-development stuff enabled) and try a "yum update", several
things fail. Here's the final output:

Error: Missing Dependency: /usr/bin/rebuild-security-providers is
needed by package java-1.5.0-gcj
Error: Missing Dependency: geronimo-specs = 1.0-0.M2.2jpp.12 is needed
by package geronimo-specs-compat
Error: Missing Dependency: lucene = 1.4.3-1jpp.18 is needed by package
lucene-devel

rebuild-security-providers is in the Fedora jpackage-utils and not the
JPackage one; geronimo-specs-compat is a dependency of
mysql-connector-java and, hence, jython and eclipse-pydev; while
Fedora lucene got split a while back into lucene and lucene-devel and
JPackage didn't follow suit.

I tried working around this a bit, but especially the jpackage-utils
dependency seems a bit annoying. (This may have to do with the
SRPM-as-noarch-RPM problem that means you need to --exclude things
twice to get them really excluded.) Is this something I should
bugzilla? Do we want JPackage to work out of the box on Fedora 7? I'm
willing to do some further testing and development on this ...

MEF

--

-- 
Mary Ellen Foster
http://homepages.inf.ed.ac.uk/mef/
(Continue reading)

Nicolas Mailhot | 3 Jun 11:07 2007
Picon

Re: Using jpackage 1.7 on Fedora 7

Le dimanche 03 juin 2007 à 09:24 +0100, Mary Ellen Foster a écrit :

> I tried working around this a bit, but especially the jpackage-utils
> dependency seems a bit annoying. 

Was probably a mistake by Fedora to put Fedora-specific utilities in
jpackage-utils. IMHO either they're useful enough to be merged
jpackage-side, or they should be spun out in a package with a different
name.

--

-- 
Nicolas Mailhot
_______________________________________________
JPackage-discuss mailing list
JPackage-discuss@...
https://www.zarb.org/mailman/listinfo/jpackage-discuss
bugzilla | 4 Jun 00:10 2007

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)

Alexei Dets | 4 Jun 01:30 2007
X-Face

Re: [Bug 273] Broken repository indexes cause installation of SRPM packages

Hi!

> To help, please set up an environment with something like
> rpm-4.4.6-10.1mdv2007.0
> createrepo-0.4.4-1mdv2007.0
> yum-2.6.1-1mdv2007.0
> and try to reproduce the failure with e.g. j-c-lang src and noarch.rpms
> as downloaded via e.g. curl from any JPP repo

Unfortunately, I don't have any Mandriva around and don't have any spare box. 
I thought about installing it to chroot using mock but looks like that 
Mandriva mirrors don't have repodata?

I tried to reproduce the bug using j-c-lang src and noarch.rpms on CentOS 5. 
No bug. Replaced CentOS's createrepo & yum with createrepo-0.4.4-1mdv2007.0 & 
yum-2.6.1-1mdv2007.0. Once again got correct primary.xml.

> The problem behind the scenes is that attribute sourcepackage
> disappeared or changed somewhere between rpm-4.4.2 and rpm-4.4.6 (in
> mandriva??)

This probably explains why everything works correctly on CentOS 5 - it has 
rpm-4.4.2. And even Fedora 7 that was released last week still has rpm-4.4.2!

> May the following info be related?
> http://cvs.mandriva.com/cgi-bin/viewvc.cgi/SPECS/rpm/rpm-4.4.6-SOURCEPACKAG
>E.patch?revision=1.1&view=markup

It looks related but comments in the rpm.spec say that the purpose of this 
patch is to restore the same behavior for src.rpm packages as was in versions 
(Continue reading)

bugzilla | 5 Jun 00:10 2007

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)

bugzilla | 6 Jun 00:10 2007

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)

Les Mikesell | 6 Jun 18:43 2007
Picon

FC6/RHEL5/Centos5?

Last month there was a discussion with the subject: "quick warning to 
those with FC6 orRHEL5build systems" that mentioned some new packages 
but I didn't see any real conclusion.  Is there a way yet to install a 
packaged tomcat that works with Sun Java on Centos5 yet?

--

-- 
   Les Mikesell
    lesmikesell@...

Gmane