Community Packages

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#45509 - [eclipse-cdt] not working with current eclipse (4.4.2)

Attached to Project: Community Packages
Opened by Johan R (cleanrock) - Tuesday, 30 June 2015, 14:24 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 02 July 2015, 23:48 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Was eclipse-cdt prematurely upgraded or am i missing something ?
I suspect eclipse-cdt should be stepped when there is a supporting eclipse package available.

eclipse-cdt 8.7.0-1
eclipse 4.4.2-1
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Thursday, 02 July 2015, 23:48 GMT
Reason for closing:  None
Additional comments about closing:  Downgraded eclipse-cdt while waiting for the eclipse package.
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 01 July 2015, 14:31 GMT
eclipse-cdt 8.7.0 is the latest stable release. This is not a bug.

The eclipse package can (and is) flagged as out-of-date.

I'll create a TODO list (used as a checklist internally) for eclipse + eclipse-cdt next time there is a release of eclipse-cdt.
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 01 July 2015, 16:55 GMT
Ideally, eclipse should be a split package which also built eclipse-cdt.

Adding depends=('eclipse>=4.5') while waiting for the eclipse package.
Comment by Jan Alexander Steffens (heftig) - Thursday, 02 July 2015, 15:08 GMT
It's definitely a bug to depend on a version not in the repository.
Comment by Alexander F. Rødseth (xyproto) - Thursday, 02 July 2015, 18:43 GMT
I was hoping to avoid reverting it. If the eclipse package could be updated to the latest version, this would not be a problem.

Reverting to eclipse-cdt 8.6.0.

To avoid this in the future (the problem with eclipse in combination with eclipse-cdt was not on purpose), I suggest that eclipse-cdt becomes a split package of the eclipse package, since they always have to be upgraded in lock-step.

If this is not possible, I will create an internal TODO-list for upgrading eclipse + eclipse-cdt together at every new release, where eclipse is upgraded before eclipse-cdt.

Hopefully this resolves the situation in a satisfactory manner.

The updated package will appear in [community] shortly.

Loading...