FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Java

 
 
LinkBack Thread Tools
 
Old 08-05-2011, 11:40 AM
Niels Thykier
 
Default Update on eclipse 3.7

Hi

This email is BCC'ed to #631061 and #631382; please consider following
up to d-java@l.d.o as it makes coordination easier.

I have managed to successfully compile eclipse 3.7 using part of the
debian packaging I just pushed to the git repository[1]. There are at
least six issues atm.

First off, my build did not use any of the patches in d/patches.
Hopefully it means most of them are redundant, but more likely it means
something will break.
Note: Some of these patches may require
eclipse-build-generatedScripts.tar.bz2 to be updated. If the build
fails horribly after applying a refreshed patch due to "missing classes"
or "cannot find package", you probably hit one of those cases.

Secondly, upstream commented out a couple of architecture support
patches in the upstream build.xml. As I recall the argument was they
did not apply cleanly, so they need to be refreshed as well.

Third, the "eclipse-build-generatedScripts.tar.bz2" in the upstream
git does not work for us. I have deviced a functional version for
Debian at [2].

Four, there are some zip/pre-compiled crap in the upstream sources we
need to get removed. Most of it will probably be fixed with refreshing
the Debian patches and just removing the left overs, but we need to
double check this.

Five, we need some upstream tarballs (my builds were done with -b).
But we generally need to deal with item four first.

Six, the upstream branch (merged into master as well) is some older
version of eclipse (I think 3.6.2, but I could be wrong). This is
trivially fixable once we got some clean tarballs from item five.

If you would like to help with any of those, feel free to claim a task
and work on it. Alternatively, there are some upstream bugs that we
could really benefit from, if they were fixed (see [3] for more info).

Caveat: If you work on any of these tasks, you must be ready to send a
patch upstream. Upstream only accepts patches from the original author
and only via their BTS. It is a part of their "IP Cleanness" strategy
and they do not make exceptions!


Getting some working sources:

$ # Fetch eclipse-3.7.0-src.tar.bz2 from
http://download.eclipse.org/technology/linuxtools/eclipse-build/3.7.x_Indigo/
$ git clone git://anonscm.debian.org/pkg-java/eclipse.git
$ tar xjf eclipse-3.7.0-src.tar.bz2
$ git clone
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/
e-b
$ cd e-b/eclipse-build
$ ln -s ../eclipse-build-config .
$ ln -s ../eclipse-build-feature .
$ mv ../../eclipse-3.7.0-src eclipse
$ cp -r ../../eclipse/debian/ .
$ # install B-D from d/control and dpkg-buildpackage -us -uc -b
# should work up to dh_install that will fail due to a missing
# manpage carried on one of our patches.

Help is much appreciated and questions are welcome, happy hacking.
~Niels

[1] http://git.debian.org/?p=pkg-java/eclipse.git;a=summary
master branch

[2]
http://people.debian.org/~nthykier/eclipse-build-generatedScripts.tar.bz2

[3] Upstream bugs that needs fixing (eclipse 3.7):
- Better support for shared read-only installs (#587657)
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=351485
- This bug is really a pain; cost two t-p-u for Squeeze
- Default update site list blank in shared install
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=249133
- patches welcome (see comment #25)


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E3BD696.50008@thykier.net">http://lists.debian.org/4E3BD696.50008@thykier.net
 
Old 08-05-2011, 02:32 PM
Niels Thykier
 
Default Update on eclipse 3.7

On 2011-08-05 13:40, Niels Thykier wrote:
> Hi
>
> This email is BCC'ed to #631061 and #631382; please consider following
> up to d-java@l.d.o as it makes coordination easier.
>
> I have managed to successfully compile eclipse 3.7 using part of the
> debian packaging I just pushed to the git repository[1]. There are at
> least six issues atm.
>
> First off, my build did not use any of the patches in d/patches.
> Hopefully it means most of them are redundant, but more likely it means
> something will break.
> Note: Some of these patches may require
> eclipse-build-generatedScripts.tar.bz2 to be updated. If the build
> fails horribly after applying a refreshed patch due to "missing classes"
> or "cannot find package", you probably hit one of those cases.
>
> Secondly, upstream commented out a couple of architecture support
> patches in the upstream build.xml. As I recall the argument was they
> did not apply cleanly, so they need to be refreshed as well.
>

This one has been applied upstream[1].

[1]
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/commit/?id=fff4c2c133d9fb2241533ae09f9a1add84844e84

> Third, the "eclipse-build-generatedScripts.tar.bz2" in the upstream
> git does not work for us. I have deviced a functional version for
> Debian at [2].
>
> Four, there are some zip/pre-compiled crap in the upstream sources we
> need to get removed. Most of it will probably be fixed with refreshing
> the Debian patches and just removing the left overs, but we need to
> double check this.
>
> Five, we need some upstream tarballs (my builds were done with -b).
> But we generally need to deal with item four first.
>
> Six, the upstream branch (merged into master as well) is some older
> version of eclipse (I think 3.6.2, but I could be wrong). This is
> trivially fixable once we got some clean tarballs from item five.
>
> If you would like to help with any of those, feel free to claim a task
> and work on it. Alternatively, there are some upstream bugs that we
> could really benefit from, if they were fixed (see [3] for more info).
>
> Caveat: If you work on any of these tasks, you must be ready to send a
> patch upstream. Upstream only accepts patches from the original author
> and only via their BTS. It is a part of their "IP Cleanness" strategy
> and they do not make exceptions!
>
>
> Getting some working sources:
>
> $ # Fetch eclipse-3.7.0-src.tar.bz2 from
> http://download.eclipse.org/technology/linuxtools/eclipse-build/3.7.x_Indigo/
> $ git clone git://anonscm.debian.org/pkg-java/eclipse.git
> $ tar xjf eclipse-3.7.0-src.tar.bz2
> $ git clone
> http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/
> e-b
> $ cd e-b/eclipse-build
> $ ln -s ../eclipse-build-config .
> $ ln -s ../eclipse-build-feature .
> $ mv ../../eclipse-3.7.0-src eclipse
> $ cp -r ../../eclipse/debian/ .

I forgot to add two lines here:
$ # open nonosgidependencies.properties and comment out
# ant-testuitl.jar line
$ wget
http://people.debian.org/~nthykier/eclipse-build-generatedScripts.tar.bz2

> $ # install B-D from d/control and dpkg-buildpackage -us -uc -b
> # should work up to dh_install that will fail due to a missing
> # manpage carried on one of our patches.
>
> Help is much appreciated and questions are welcome, happy hacking.
> ~Niels
>
> [1] http://git.debian.org/?p=pkg-java/eclipse.git;a=summary
> master branch
>
> [2]
> http://people.debian.org/~nthykier/eclipse-build-generatedScripts.tar.bz2
>
> [3] Upstream bugs that needs fixing (eclipse 3.7):
> - Better support for shared read-only installs (#587657)
> - https://bugs.eclipse.org/bugs/show_bug.cgi?id=351485
> - This bug is really a pain; cost two t-p-u for Squeeze
> - Default update site list blank in shared install
> - https://bugs.eclipse.org/bugs/show_bug.cgi?id=249133
> - patches welcome (see comment #25)
>
>

~Niels


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E3BFF19.6020404@thykier.net">http://lists.debian.org/4E3BFF19.6020404@thykier.net
 
Old 08-08-2011, 10:47 PM
Niels Thykier
 
Default Update on eclipse 3.7

On 2011-08-05 13:40, Niels Thykier wrote:
> Hi
>

Hi,

> This email is BCC'ed to #631061 and #631382; please consider following
> up to d-java@l.d.o as it makes coordination easier.
>
> I have managed to successfully compile eclipse 3.7 using part of the
> debian packaging I just pushed to the git repository[1]. There are at
> least six issues atm.
>

Time for an update, I guess. The attentive reader will have noticed
eclipse 3.7 (3.7~exp-1) got upload to experimental. Obviously this
means that...

> First off, my build did not use any of the patches in d/patches.
> Hopefully it means most of them are redundant, but more likely it means
> something will break.
> Note: Some of these patches may require
> eclipse-build-generatedScripts.tar.bz2 to be updated. If the build
> fails horribly after applying a refreshed patch due to "missing classes"
> or "cannot find package", you probably hit one of those cases.
>

this is fixed.

> Secondly, upstream commented out a couple of architecture support
> patches in the upstream build.xml. As I recall the argument was they
> did not apply cleanly, so they need to be refreshed as well.
>

this is has not been b0rked since it was fixed. :P

> Third, the "eclipse-build-generatedScripts.tar.bz2" in the upstream
> git does not work for us. I have deviced a functional version for
> Debian at [2].
>

this is out-dated; use the one from the package (also in git).

> Four, there are some zip/pre-compiled crap in the upstream sources we
> need to get removed. Most of it will probably be fixed with refreshing
> the Debian patches and just removing the left overs, but we need to
> double check this.
>

as far as I can tell, this has been fixed. But if something sneaked
past me, let me know.

> Five, we need some upstream tarballs (my builds were done with -b).
> But we generally need to deal with item four first.
>

this has been fixed.

> Six, the upstream branch (merged into master as well) is some older
> version of eclipse (I think 3.6.2, but I could be wrong). This is
> trivially fixable once we got some clean tarballs from item five.
>

the upstream and master branches on the git has been updated to 3.7.


Okay, end of updates. Time for the second round of things that needs to
be checked/fixed. These items stalls uploading 3.7 to sid.

* Test the binaries - so far I only know it builds on amd64. It
*probably* works, but feel free to take it for a spin.

* Check that other eclipse packages still build. Particularly, check
the "pdebuild" script in eclipse-pde was generated correctly.
- feel free to file bugs accordingly.
- eclipse-cdt will probably need a new upstream version.

* Check up on some of the lintian warnings. There was at least one
warning about a symlink being absolute. I could not figure out why
dh_link did not fix it.

* All the other issues I forgot about. Yes, I expect you to know what
I forgot! :P

> If you would like to help with any of those, feel free to claim a task
> and work on it. Alternatively, there are some upstream bugs that we
> could really benefit from, if they were fixed (see [3] for more info).
>
> [...]
>
> Getting some working sources:
>
> [...]
>

reduced to:
$ git clone git://git.debian.org/git/pkg-java/eclipse.git
$ # wget tarballs from $local_mirror when they arrive

> Help is much appreciated and questions are welcome, happy hacking.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Particularly that still holds!

~Niels


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E40676F.80808@thykier.net">http://lists.debian.org/4E40676F.80808@thykier.net
 

Thread Tools




All times are GMT. The time now is 10:30 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org