Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360028

Summary:	Qualifiers differ between Indigo SR1 repo and Linux Tools repo
Product:	[Tools] Linux Tools	Reporter:	Martin Oberhuber <mober.at+eclipse>
Component:	Project	Assignee:	Linux Distros Inbox <linux.distros-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	P3	CC:	jjohnstn
Version:	0.8.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	360048
Bug Blocks:

Description Martin Oberhuber

2011-10-05 16:01:10 EDT

Installing Linuxtools Valgrind from
  http://download.eclipse.org/releases/indigo
I get version
  0.8.1.201108301805

but installing from the zipped p2 repo from linuxtools downloads,
  http://www.eclipse.org/downloads/download.php?file=/technology/linuxtools/linuxtools-0.8.1-incubation.zip
I get version
  0.8.1.20110926035

Is it deliberate? Or an oversight?

I know that projects can release at their own pace and project update sites may always have newer content than the indigo repo... but what worries me a bit is that
  - up to the 3rd digit both versions are the same, so from end user's point
    of view it's hard to tell the difference between the two 0.8.1 variants
  - After installing from Indigo SR1 and doing "Check for UPdates" I don't
    get any updates so the linuxtools project repo isn't referenced automatically
  - Even in Preferences : Software sites, where Indigo installs about 30
    project update sites, I don't see the linuxtools project site

In some sense the inconsistency worries me and I'd like to get a comment...

Comment 1 Andrew Overholt

2011-10-05 17:44:37 EDT

Jeff and I discussed this yesterday.  There was a bit of confusion with the process and I'll let him fill in any details on the differences.

I'm not sure why the Linux Tools p2 repo isn't referenced.  I've filed bug 360048 to track that.

Comment 2 Jeff Johnston

2011-10-05 19:17:57 EDT

The confusion is entirely my fault.  I was in charge of the release while Andrew was away and did not realize that the indigo-sr1 build should already be the 0.8.1 release.

I went through the release process steps in our releng wiki.  One of these steps is to run the tycho versions plugin to remove the SNAPSHOT qualifiers from the pom.xml files.  This had not been done for the indigo-sr1 build so I ran it.  This had the unfortunate side effect of removing .qualifier from the profiling and valgrind features.  I fixed this manually.  After fixing this, the build failed due to a long-standing compilation bug in SystemTap ThreadProfiler that normally did not affect the build, presumably since ThreadProfiler is not included as part of the release.  I fixed that so the build would complete.  The build also contains a single bug fix for Lttng (adding missing messages to a new experiment dialog) that was committed by the Lttng folks after the 08/30 build:
SHA-1 e962fd3bcfb150509c64fd5442f06297e06 but before my changes above.

The indigo-sr1 release is from SHA-1 f920f76d4d254b51878bc6d0838a6b02d5d38c22 on the stable-0.8 branch while 0.8.1 is from SHA-1 b5d263782a2d384025a07cfd136fefc0fad7218e

So, at this point, what should/can be done?  The 0.8.1 release has the lttng messages fix but is otherwise source-code-equivalent to what is in indigo-sr1.

Comment 3 Andrew Overholt

2011-10-06 09:21:50 EDT

Thanks for the honest clarification, Jeff.  Please be sure to file a bug about the Tycho Versions bug you ran into; it seems quite serious.

Martin, what would help Wind River in this case?  A statement from the project stating which IU versions to consume?

Comment 4 Martin Oberhuber

2011-10-06 10:07:03 EDT

Hi Andrew,

I don't have very much of an issue from Wind River point of view ... we are consuming 0.8.1 into our product, and knowing that this == Indigo SR1 + ltt fix is good enough for me.

From Community point of view, I'm worried that after consuming Linuxtools from the common repo, a "check for updates" doesn't give me 0.8.1 from the project site. Because this effectively means that you cannot release urgent hotfixes on the project site and deploy them via "check for updates". But that problem should probably be tracked with a different bug.

I'm not sure whether you'll want to notify / inform other Linuxtools consumers about the Indigo SR1 / 0.8.1 mismatch .. perhaps a message on the devlist / newsgroup would be in order, but it may not be a very big deal.

From Wind River point of view I currently care more about 0.9 and bug 360085 :)

Comment 5 Andrew Overholt

2011-10-06 10:57:10 EDT

(In reply to comment #4)
> I don't have very much of an issue from Wind River point of view ... we are
> consuming 0.8.1 into our product, and knowing that this == Indigo SR1 + ltt fix
> is good enough for me.

Thanks for the prompt feedback, Martin.  It's nice having a responsive consumer :)

> From Community point of view, I'm worried that after consuming Linuxtools from
> the common repo, a "check for updates" doesn't give me 0.8.1 from the project
> site. Because this effectively means that you cannot release urgent hotfixes on
> the project site and deploy them via "check for updates". But that problem
> should probably be tracked with a different bug.

Bug 360048 tracks this.

> I'm not sure whether you'll want to notify / inform other Linuxtools consumers
> about the Indigo SR1 / 0.8.1 mismatch .. perhaps a message on the devlist /
> newsgroup would be in order, but it may not be a very big deal.

Jeff, please do this.

> From Wind River point of view I currently care more about 0.9 and bug 360085 :)

Okay :)

I've updated the title of this bug a bit and I'm going to close it since we can't do much about it now.  I'd rather a "SORRY;CANTFIX" resolution but "WONTFIX" will have to do.