Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9094 - Remove junit package from Extra

Attached to Project: Arch Linux
Opened by Vitaliy Berdinskikh (skipper13) - Friday, 04 January 2008, 20:38 GMT
Last edited by Jan de Groot (JGC) - Thursday, 10 January 2008, 21:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
junit in Extra is outdated. And new version present in Unsupported.

Additional info:
* junit 3.8.2 in Extra: http://archlinux.org/packages/search/?repo=all&category=all&q=junit&limit=50
* junit 4.4 in Unsupported: http://aur.archlinux.org/packages.php?do_Details=1&ID=8534&K=junit
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 10 January 2008, 21:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  junit is up2date in extra.
Comment by Greg (dolby) - Friday, 04 January 2008, 21:52 GMT
junit 4.4 is in community not unsupported. this is really wieird though.
Comment by Vitaliy Berdinskikh (skipper13) - Friday, 04 January 2008, 21:58 GMT
Heh, sorry. junit 4.4 in Community.
Comment by Eric Belanger (Snowman) - Saturday, 05 January 2008, 19:57 GMT
junit is required for other packages in extra so it'll remain in extra. Jan could give more details but the junit in extra can't be updated because the more recent versions of junit doesn't work with the other extra packages that depends on it.

Actually, it is the junit package in community that should be removed. But as this is a special case, we might keep it in community in case someone wants the newest version or that the jump-project package in community needs the latest junit.
Comment by Jan de Groot (JGC) - Saturday, 05 January 2008, 21:39 GMT
junit3 and junit4 are two different programs, other distributions ship the 4.x version as junit4, you could have done the same with the community package.

The reason why junit 3.8 was in extra was quite simple:
- other distributions ship 3.8 also
- junit source is a big mess, they maintain their buildable source only in CVS and don't do reliable tagging (same reason why debian and ubuntu are at 4.3 for their junit4 package, there's no reliable CVS tag for 4.4)
- bcprov in extra needs junit as makedepend, which works fine with either version
- I want all my java packages built from source when there's source available.

I updated junit to 4.4 for now, used the 4.3.1 build.xml file from Redhat and made some changes (changed version, no javadoc, don't run the unit tests in junit itself).

Loading...