[gentoo-java] Weka package cleanup

[gentoo-java] Weka package cleanup

[Alistair Bush]

[-- Attachment #1: Type: text/plain, Size: 541 bytes --]

While im at work im going to attempt to cleanup as many bugs as possible, Or
at least point them out to the dev's.

For example

https://bugs.gentoo.org/show_bug.cgi?id=95129

This bug can be closed as it seems (by the changelog) to have been fixed
ages ago.

Also weka-3.4.6 needs to still be migrated to gen-2 and hopefully maked
stable as soon as possible.  The lastest ebuild has been around in ~arch for
10 months.  I'll put the migration of weka on my "[Not] To Do List" ;)


I will attempt to do one of these a day.

Thanks

ali_bush

[-- Attachment #2: Type: text/html, Size: 681 bytes --]

Re: [gentoo-java] Weka package cleanup

[Petteri Räty]

Alistair Bush wrote:
> While im at work im going to attempt to cleanup as many bugs as
> possible, Or at least point them out to the dev's.
>

Yeah going through the old bugs is something that no-one seems to do. I
sometimes wonder there to figs a bug or two.

> 
> For example
> 
> https://bugs.gentoo.org/show_bug.cgi?id=95129
> <https://bugs.gentoo.org/show_bug.cgi?id=95129>
> 
> This bug can be closed as it seems (by the changelog) to have been fixed
> ages ago.
> 
> Also weka-3.4.6 needs to still be migrated to gen-2 and hopefully maked
> stable as soon as possible.  The lastest ebuild has been around in ~arch
> for 10 months.  I'll put the migration of weka on my "[Not] To Do List" ;)
> 

Requested stable. At least an improvement. You can file stabilization
bugs too, just file them to java@gentoo.org without arches and we will
do the rest...

Regards,
Petteri
-- 
gentoo-java@gentoo.org mailing list

Re: [gentoo-java] Weka package cleanup

[Alon Bar-Lev]

On 1/16/07, Petteri Räty <betelgeuse@gentoo.org> wrote:
> Yeah going through the old bugs is something that no-one seems to do. I
> sometimes wonder there to figs a bug or two.

Great work!
It seemed that java is not handled through bugzilla :)
There also should be a time table for moving to generation 2 eclass...
I can help... Moving all packages I use to generation 2...
My interest is to stop forcing sun-sdk-1.5 as generation 1...

Best Regards,
Alon Bar-Lev.

-- 
gentoo-java@gentoo.org mailing list

Re: [gentoo-java] Weka package cleanup

[Vlastimil Babka]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alon Bar-Lev wrote:
> On 1/16/07, Petteri Räty <betelgeuse@gentoo.org> wrote:
>> Yeah going through the old bugs is something that no-one seems to do. I
>> sometimes wonder there to figs a bug or two.

Me too, sometimes.

> There also should be a time table for moving to generation 2 eclass...

Not sure about deadlines yet... there's still over 160 packageslots,
look http://dev.gentoo.org/~nelchael/java-generation-2/progress.png

> I can help... Moving all packages I use to generation 2...

Yeah, migrating packages that one has installed is common :) Maybe then
we find the rest isn't that important as not many people use it.
Help would be appreciated for sure. But please don't commit that on your
own without our review, at least for first attempts. Takes some
experience to do it properly (and admittedly, our docs aren't exactly up
to date with the eclasses improvements you can for example see in this ML).

> My interest is to stop forcing sun-sdk-1.5 as generation 1...

It's jdk-1.4 and it will have to be forced in generation 1. The interest
is to remove generation 1 :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFrTrntbrAj05h3oQRAvrAAJ0VFpaTdKqXXNTf/ZZGTpMziU3hBgCgpIZo
elh8/mNwNhM068eokYs4hCs=
=uIpP
-----END PGP SIGNATURE-----
-- 
gentoo-java@gentoo.org mailing list

Re: [gentoo-java] Weka package cleanup

[Alon Bar-Lev]

On 1/16/07, Vlastimil Babka <caster@gentoo.org> wrote:
> > I can help... Moving all packages I use to generation 2...
>
> Yeah, migrating packages that one has installed is common :) Maybe then
> we find the rest isn't that important as not many people use it.
> Help would be appreciated for sure. But please don't commit that on your
> own without our review, at least for first attempts. Takes some
> experience to do it properly (and admittedly, our docs aren't exactly up
> to date with the eclasses improvements you can for example see in this ML).

But you have to promiss me response time...
I will open a bug for each ebuild, and you review it in... a year? :)

> > My interest is to stop forcing sun-sdk-1.5 as generation 1...
>
> It's jdk-1.4 and it will have to be forced in generation 1. The interest
> is to remove generation 1 :)

NO... I force 1.5 to be generation 1... I don't like to have two sdks
on my machine.

Best Regards,
Alon Bar-Lev.
-- 
gentoo-java@gentoo.org mailing list

Re: [gentoo-java] Weka package cleanup

[Alistair Bush]

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

How about I start opening bugs on bugs that have already been fixed but not
closed :)

something like

Bug #123456 is open even tho its been fixed.

I wonder what the bug-wranglers would like of that :D

On 1/17/07, Alon Bar-Lev <alon.barlev@gmail.com> wrote:
>
> On 1/16/07, Vlastimil Babka <caster@gentoo.org> wrote:
> > > I can help... Moving all packages I use to generation 2...
> >
> > Yeah, migrating packages that one has installed is common :) Maybe then
> > we find the rest isn't that important as not many people use it.
> > Help would be appreciated for sure. But please don't commit that on your
> > own without our review, at least for first attempts. Takes some
> > experience to do it properly (and admittedly, our docs aren't exactly up
> > to date with the eclasses improvements you can for example see in this
> ML).
>
> But you have to promiss me response time...
> I will open a bug for each ebuild, and you review it in... a year? :)
>
> > > My interest is to stop forcing sun-sdk-1.5 as generation 1...
> >
> > It's jdk-1.4 and it will have to be forced in generation 1. The interest
> > is to remove generation 1 :)
>
> NO... I force 1.5 to be generation 1... I don't like to have two sdks
> on my machine.
>
> Best Regards,
> Alon Bar-Lev.
> --
> gentoo-java@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1791 bytes --]

Re: [gentoo-java] Weka package cleanup

[Alistair Bush]

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

Oh and while i'm at it.

https://bugs.gentoo.org/show_bug.cgi?id=160845

this would be a nice one for a dev to look at :)


On 1/17/07, Alistair Bush <alistair.bush@gmail.com> wrote:
>
> How about I start opening bugs on bugs that have already been fixed but
> not closed :)
>
> something like
>
> Bug #123456 is open even tho its been fixed.
>
> I wonder what the bug-wranglers would like of that :D
>
> On 1/17/07, Alon Bar-Lev <alon.barlev@gmail.com> wrote:
> >
> > On 1/16/07, Vlastimil Babka <caster@gentoo.org> wrote:
> > > > I can help... Moving all packages I use to generation 2...
> > >
> > > Yeah, migrating packages that one has installed is common :) Maybe
> > then
> > > we find the rest isn't that important as not many people use it.
> > > Help would be appreciated for sure. But please don't commit that on
> > your
> > > own without our review, at least for first attempts. Takes some
> > > experience to do it properly (and admittedly, our docs aren't exactly
> > up
> > > to date with the eclasses improvements you can for example see in this
> > ML).
> >
> > But you have to promiss me response time...
> > I will open a bug for each ebuild, and you review it in... a year? :)
> >
> > > > My interest is to stop forcing sun-sdk-1.5 as generation 1...
> > >
> > > It's jdk-1.4 and it will have to be forced in generation 1. The
> > interest
> > > is to remove generation 1 :)
> >
> > NO... I force 1.5 to be generation 1... I don't like to have two sdks
> > on my machine.
> >
> > Best Regards,
> > Alon Bar-Lev.
> > --
> > gentoo-java@gentoo.org mailing list
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 2679 bytes --]

Re: [gentoo-java] Weka package cleanup

[William L. Thomson Jr.]

[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]

On Tue, 2007-01-16 at 22:55 +0200, Alon Bar-Lev wrote:
> On 1/16/07, Vlastimil Babka <caster@gentoo.org> wrote:
> > > I can help... Moving all packages I use to generation 2...
> >
> > Yeah, migrating packages that one has installed is common :) Maybe then
> > we find the rest isn't that important as not many people use it.
> > Help would be appreciated for sure. But please don't commit that on your
> > own without our review, at least for first attempts. Takes some
> > experience to do it properly (and admittedly, our docs aren't exactly up
> > to date with the eclasses improvements you can for example see in this ML).
> 
> But you have to promiss me response time...

Promises from volunteers, that's asking quite a bit :)

> I will open a bug for each ebuild, and you review it in... a year? :)

Well you can always join the team and help out with the work load if you
are not happy with response time :) Also at times what is critical to
one is not to all. Such is life, but we are trying to improve things.
Just not to many active devs, and with 400+ packages. The load for any
one is quite great. With those like me only able to keep about 10 or so
of those current, and up to date. It leaves quite a load for others.

> > > My interest is to stop forcing sun-sdk-1.5 as generation 1...
> >
> > It's jdk-1.4 and it will have to be forced in generation 1. The interest
> > is to remove generation 1 :)
> 
> NO... I force 1.5 to be generation 1... I don't like to have two sdks
> on my machine.

Yes I mentioned around the time that 1.6 was released we consider
bumping our min version to source/target 1.5. However that will only be
possible once ALL gen 1 packages are migrated, cleaned up, and so on. I
doubt it will happen in the next 5-6 months or so. Hopefully could and
should happen before end of year. IMHO

-- 
William L. Thomson Jr.
Gentoo/Java

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-java] Weka package cleanup

[William L. Thomson Jr.]

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

On Wed, 2007-01-17 at 11:53 +1300, Alistair Bush wrote:
> How about I start opening bugs on bugs that have already been fixed
> but not closed :)

Hmm not sure about that. Buggzie seems stable these days, but still
might be excessive use. Would like to know what others think about that.

> something like
> 
> Bug #123456 is open even tho its been fixed.
> 
> I wonder what the bug-wranglers would like of that :D

Well another route would be to email bug #, and comments to
java@gentoo.org Then the first dev that gets the email can take comments
add to bug and close the one. Instead of having to close and comment on
two :)

To expand that, you could email over a list of bug #s with comments, to
kill more than one bird with a single stone. ;)

-- 
William L. Thomson Jr.
Gentoo/Java

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-java] Weka package cleanup

[Alistair Bush]

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

mmm.... yes java@gentoo.org would be a good place instead of here to email
it.

Basically the aim I have for this is too draw the attention of you dev's to
bugs that are a 'quick' fix.

Therefore meeting the aim of closing bugs without you guys having to do most
of the investigation...

I have also though of going thru bugs.gentoo.org and reassigning the
priority of bugs into categories (rather a large job for anyone who has
other projects they want to get kicking).

eg (as a very ruff guess)
So P1 would be for security exploits and the like.
P2 would be for ebuild related buys
P3 ebuild request
P4 ebuild request that are extremely difficult (or just can't happen because
of lack of resources)
P5 (something even worse than above)

I also believe that there should be some bugs marked as WONTFIX, CANTFIX.

For example jboss https://bugs.gentoo.org/show_bug.cgi?id=148383 and
https://bugs.gentoo.org/show_bug.cgi?id=66965

I believe, and it will be interesting in hereing your views on this, that
bugs should only be open if they are actually going to be worked on.  With
jboss we now have a binary ebuild in the overlay that could replace the
existing versions and these jboss bugs could be closed.

What do you guys think?

Alistair (ali_bush)


On 1/17/07, William L. Thomson Jr. <wltjr@gentoo.org> wrote:
>
> On Wed, 2007-01-17 at 11:53 +1300, Alistair Bush wrote:
> > How about I start opening bugs on bugs that have already been fixed
> > but not closed :)
>
> Hmm not sure about that. Buggzie seems stable these days, but still
> might be excessive use. Would like to know what others think about that.
>
> > something like
> >
> > Bug #123456 is open even tho its been fixed.
> >
> > I wonder what the bug-wranglers would like of that :D
>
> Well another route would be to email bug #, and comments to
> java@gentoo.org Then the first dev that gets the email can take comments
> add to bug and close the one. Instead of having to close and comment on
> two :)
>
> To expand that, you could email over a list of bug #s with comments, to
> kill more than one bird with a single stone. ;)
>
> --
> William L. Thomson Jr.
> Gentoo/Java
>
>
>

[-- Attachment #2: Type: text/html, Size: 2811 bytes --]

Re: [gentoo-java] Weka package cleanup

[William L. Thomson Jr.]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On Tue, 2007-01-16 at 18:37 -0500, William L. Thomson Jr. wrote:
> 
> Well another route would be to email bug #, and comments to
> java@gentoo.org Then the first dev that gets the email can take comments
> add to bug and close the one. Instead of having to close and comment on
> two :)
Doh, wasn't thinking. :o Just comment on bug, and it will email
java@gentoo.org Then first one who responds to the email can just close
with minimal comment :)

-- 
William L. Thomson Jr.
Gentoo/Java

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-java] Weka package cleanup

[William L. Thomson Jr.]

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

On Wed, 2007-01-17 at 13:07 +1300, Alistair Bush wrote:
> 
> Basically the aim I have for this is too draw the attention of you
> dev's to bugs that are a 'quick' fix. 
> 
> Therefore meeting the aim of closing bugs without you guys having to
> do most of the investigation...

Sounds good to me :)

> I have also though of going thru bugs.gentoo.org and reassigning the
> priority of bugs into categories

I don't think anyone would really object to that, other than maybe some
bug spam.

> I also believe that there should be some bugs marked as WONTFIX,
> CANTFIX.

Yes, those are great. Would be nice if there was a YOUFIX :)

> For example jboss https://bugs.gentoo.org/show_bug.cgi?id=148383 and
> https://bugs.gentoo.org/show_bug.cgi?id=66965
> 
> I believe, and it will be interesting in hereing your views on this,
> that bugs should only be open if they are actually going to be worked
> on.

Well since they are stuff that's in tree, in theory they should remain
open. Till there is an alternative in tree, or fix. Otherwise closing
might just cause someone else to file a new bug instead of finding the
pre-existing closed one.

>   With jboss we now have a binary ebuild in the overlay that could
> replace the existing versions and these jboss bugs could be closed. 

Adding binary to tree, ew. Bugs closed, good.

-- 
William L. Thomson Jr.
Gentoo/Java

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-java] Weka package cleanup

[Vlastimil Babka]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alistair Bush wrote:
> I have also though of going thru bugs.gentoo.org
> <http://bugs.gentoo.org> and reassigning the priority of bugs into
> categories (rather a large job for anyone who has other projects they
> want to get kicking).

And I would love to mark stable/keyword requests in a way that I can
filter them easily. They are assigned to us but we are not the ones
solving them :) Be it a special component or keyword, or some unified
form of summary. I see there are already STABLE and TESTED keywords for
arch testers to mark stuff they've tested, so maybe add something
STABLEREQ and KEYWORDREQ? What do you think? If it's sane, it should
probably be discussed on gentoo-dev as some global policy.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFrXT5tbrAj05h3oQRAtj7AJ9ydkaYZBKom7qZ0R6/lTlpSqbnHgCfWvKl
hs3etexbXWaWM8N6WTtOHQQ=
=ndHV
-----END PGP SIGNATURE-----
-- 
gentoo-java@gentoo.org mailing list

Re: [gentoo-java] Weka package cleanup

[Alistair Bush]

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

That sounds like a good idea.

On 1/17/07, Vlastimil Babka <caster@gentoo.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alistair Bush wrote:
> > I have also though of going thru bugs.gentoo.org
> > <http://bugs.gentoo.org> and reassigning the priority of bugs into
> > categories (rather a large job for anyone who has other projects they
> > want to get kicking).
>
> And I would love to mark stable/keyword requests in a way that I can
> filter them easily. They are assigned to us but we are not the ones
> solving them :) Be it a special component or keyword, or some unified
> form of summary. I see there are already STABLE and TESTED keywords for
> arch testers to mark stuff they've tested, so maybe add something
> STABLEREQ and KEYWORDREQ? What do you think? If it's sane, it should
> probably be discussed on gentoo-dev as some global policy.
> - --
> Vlastimil Babka (Caster)
> Gentoo/Java
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFrXT5tbrAj05h3oQRAtj7AJ9ydkaYZBKom7qZ0R6/lTlpSqbnHgCfWvKl
> hs3etexbXWaWM8N6WTtOHQQ=
> =ndHV
> -----END PGP SIGNATURE-----
> --
> gentoo-java@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1733 bytes --]

Re: [gentoo-java] Weka package cleanup

[Alistair Bush]

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

Do we still have a list generated that tells us of all the gen-1 packages
remaining?


On 1/17/07, Alistair Bush <alistair.bush@gmail.com> wrote:
>
> That sounds like a good idea.
>
> On 1/17/07, Vlastimil Babka <caster@gentoo.org> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Alistair Bush wrote:
> > > I have also though of going thru bugs.gentoo.org
> > > <http://bugs.gentoo.org > and reassigning the priority of bugs into
> > > categories (rather a large job for anyone who has other projects they
> > > want to get kicking).
> >
> > And I would love to mark stable/keyword requests in a way that I can
> > filter them easily. They are assigned to us but we are not the ones
> > solving them :) Be it a special component or keyword, or some unified
> > form of summary. I see there are already STABLE and TESTED keywords for
> > arch testers to mark stuff they've tested, so maybe add something
> > STABLEREQ and KEYWORDREQ? What do you think? If it's sane, it should
> > probably be discussed on gentoo-dev as some global policy.
> > - --
> > Vlastimil Babka (Caster)
> > Gentoo/Java
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFFrXT5tbrAj05h3oQRAtj7AJ9ydkaYZBKom7qZ0R6/lTlpSqbnHgCfWvKl
> > hs3etexbXWaWM8N6WTtOHQQ=
> > =ndHV
> > -----END PGP SIGNATURE-----
> > --
> > gentoo-java@gentoo.org mailing list
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 2588 bytes --]

Re: [gentoo-java] Weka package cleanup

[Joshua Nichols]

Alistair Bush wrote:
>
> Do we still have a list generated that tells us of all the gen-1 
> packages remaining?
>
Yep, it's where it was previously at:
http://dev.gentoo.org/~nelchael/java-generation-2/

In particular, see
http://dev.gentoo.org/~nelchael/java-generation-2/not-migrated-current
http://dev.gentoo.org/~nelchael/java-generation-2/progress.png

It may have stopped running for a while, but it was updated recently 
(20070109).

@nelchael, care to enlighten us how this is run? Perhaps we can do 
something (move or otherwise) to ensure this gets run more regularly.

In addition to this script, we probably should get a script going that 
detects things that don't have a gen-2 package that is stablized. It'd 
probably be a relative of one of the scripts at:

http://overlays.gentoo.org/svn/proj/java/scripts/
(I think it's find-unported.py that is being used to generate the above 
mentioned files)


-- 
Joshua Nichols
Gentoo/Java Project Lead
-- 
gentoo-java@gentoo.org mailing list

Re: [gentoo-java] Weka package cleanup

[William L. Thomson Jr.]

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

On Wed, 2007-01-17 at 01:39 -0500, Joshua Nichols wrote:
>
> In addition to this script, we probably should get a script going that 
> detects things that don't have a gen-2 package that is stablized.

Yes that is very important since the 1.4/gen 1 stuff can't go away just
by migrating packages. The migrated packages must be stable first.
Before we can remove the gen 1 versions. Unless the package has never
had a stable version, or no stable gen 1 versions.

-- 
William L. Thomson Jr.
Gentoo/Java

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-java] Weka package cleanup

[Petteri Räty]

Alon Bar-Lev wrote:
> On 1/16/07, Vlastimil Babka <caster@gentoo.org> wrote:
>> > I can help... Moving all packages I use to generation 2...
>>
>> Yeah, migrating packages that one has installed is common :) Maybe then
>> we find the rest isn't that important as not many people use it.
>> Help would be appreciated for sure. But please don't commit that on your
>> own without our review, at least for first attempts. Takes some
>> experience to do it properly (and admittedly, our docs aren't exactly up
>> to date with the eclasses improvements you can for example see in this
>> ML).
> 
> But you have to promiss me response time...
> I will open a bug for each ebuild, and you review it in... a year? :)
> 

The best approach would probably be to give you commit access to the
java overlays. From there it would be immediately useful for our users
and could then be reviewed when java devs have the time. The easiest
approach to get something done in the Gentoo java land is to ping us in
#gentoo-java.

Regards,
Petteri
-- 
gentoo-java@gentoo.org mailing list

[gentoo-java] dev-java/aspectwerkz

[Alistair Bush]

Im just doing more of my bug busting 
<https://bugs.gentoo.org/show_bug.cgi?id=120618>

and have added this ebuild, migrated to gen-2 to the overlay.

sadly ive also realised that this is an example of a package that builds 
certain jars based on jdk version.  Has there been any progress on a policy 
for this?

I would like to get this ebuild into the main tree and stable so that the 
gen-1 packages can be removed.  Would this issue stop that from occuring?

Thanks

ali_bush
-- 
gentoo-java@gentoo.org mailing list