From: Angus Hedger on
Hey there,

Yes, as far as I know that would work, but if you are not careful you will
end up upgrading you'er whole system to sid (as someone who added unstable
sources to his Lenny install once by accident and ended up
in dependency hell with half the system upgraded and half not).

Also sid is not recommended unless you are experienced with debian and
willing to fix it if everything breaks ;)

So, I would recommended not changing your sources.list like that myself.

Regards,

Angus.

On Sun, Jan 10, 2010 at 11:03 PM, Tsang Kim Wai <tkwinfo(a)gmail.com> wrote:

> Hi All,
>
> Thanks for all your information. The eclipse 3.5 works OK.
>
> But if I want to try one of Mathias suggestion to upgrade my old
> eclipse 3.2 to eclipse 3.4 in the unstable release, then, in my
> understanding, I would need to edit the "/etc/apt/sources.list" file to
> change any "lenny" keywork to "sid".
>
> My sources.list file contains the following lines :
>
> deb http://ftp.hk.debian.org/debian/ lenny main contrib non-free
> deb-src http://ftp.hk.debian.org/debian/ lenny main contrib non-free
>
> deb http://security.debian.org/ lenny/updates main contrib non-free
> deb-src http://security.debian.org/ lenny/updates main contrib non-free
>
> deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib
> non-free
> deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
> contrib non-free
>
> Then I think replacing all "lenny" to "sid" should change my Debian
> system from stable to un-stable release so that I could upgrade eclipse 3.2
> to eclipse 3.4 by running just "apt-get install eclipse". Is that the case ?
>
>
> Alternatively, if I don't change my Debian system to un-stable release
> through editing "sources.list", could I still upgrade my old eclipse 3.2 to
> eclipse 3.4 in other way ?
>
> Any comment / suggestion.
>
> Regards
> Lawrence
>
>
>
> On Mon, Jan 11, 2010 at 1:54 AM, Mathias <m9236(a)abc.se> wrote:
>
>> On Sun, 10 Jan 2010, Tsang Kim Wai wrote:
>>
>> Hi Nick Douma, Liam O'Toole and Mathias,
>>>
>>> It works by simply extracting the downloaded Eclipse 3.5 binary file
>>> into /usr/local/eclipse-3.5/ directory and then run the eclipse script
>>> under
>>> that directory. But I think, the eclipse 3.5 simple installation may
>>> depend
>>> on some configurations of my old eclipse 3.2 installation. That is, I may
>>> not un-install eclipse 3.2 while expecting eclipse 3.5 would work
>>> properly.
>>> Is that the case ?
>>>
>>> Anyway, thank you for all your suggestions.
>>>
>>> Yeah, seeing how the apt system on debian mostly works to maintain and
>> upgrade the packages to newer version, the 3.4 that is in unstable would
>> replace the 3.2 one, unless some changes were made to the newer package.
>>
>> As mentioned earlier, creating a symlink in /usr/bin seems like a good
>> idea too.
>>
>> Mat
>
>
>
From: Zhan on
On Mon, Jan 11, 2010 at 9:06 AM, Angus Hedger <demidevil(a)gmail.com> wrote:

> Hey there,
>
> Yes, as far as I know that would work, but if you are not careful you will
> end up upgrading you'er whole system to sid (as someone who added unstable
> sources to his Lenny install once by accident and ended up
> in dependency hell with half the system upgraded and half not).
>
> Also sid is not recommended unless you are experienced with debian and
> willing to fix it if everything breaks ;)
>
> So, I would recommended not changing your sources.list like that myself.
>
> Regards,
>
> Angus.
>
> On Sun, Jan 10, 2010 at 11:03 PM, Tsang Kim Wai <tkwinfo(a)gmail.com> wrote:
>
>> Hi All,
>>
>> Thanks for all your information. The eclipse 3.5 works OK.
>>
>> But if I want to try one of Mathias suggestion to upgrade my old
>> eclipse 3.2 to eclipse 3.4 in the unstable release, then, in my
>> understanding, I would need to edit the "/etc/apt/sources.list" file to
>> change any "lenny" keywork to "sid".
>>
>> My sources.list file contains the following lines :
>>
>> deb http://ftp.hk.debian.org/debian/ lenny main contrib non-free
>> deb-src http://ftp.hk.debian.org/debian/ lenny main contrib non-free
>>
>> deb http://security.debian.org/ lenny/updates main contrib non-free
>> deb-src http://security.debian.org/ lenny/updates main contrib non-free
>>
>> deb http://volatile.debian.org/debian-volatile lenny/volatile main
>> contrib non-free
>> deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
>> contrib non-free
>>
>> Then I think replacing all "lenny" to "sid" should change my Debian
>> system from stable to un-stable release so that I could upgrade eclipse 3.2
>> to eclipse 3.4 by running just "apt-get install eclipse". Is that the case ?
>>
>>
>> Alternatively, if I don't change my Debian system to un-stable
>> release through editing "sources.list", could I still upgrade my old eclipse
>> 3.2 to eclipse 3.4 in other way ?
>>
>> Any comment / suggestion.
>>
>> Regards
>> Lawrence
>>
>>
>>
>> On Mon, Jan 11, 2010 at 1:54 AM, Mathias <m9236(a)abc.se> wrote:
>>
>>> On Sun, 10 Jan 2010, Tsang Kim Wai wrote:
>>>
>>> Hi Nick Douma, Liam O'Toole and Mathias,
>>>>
>>>> It works by simply extracting the downloaded Eclipse 3.5 binary
>>>> file
>>>> into /usr/local/eclipse-3.5/ directory and then run the eclipse script
>>>> under
>>>> that directory. But I think, the eclipse 3.5 simple installation may
>>>> depend
>>>> on some configurations of my old eclipse 3.2 installation. That is, I
>>>> may
>>>> not un-install eclipse 3.2 while expecting eclipse 3.5 would work
>>>> properly.
>>>> Is that the case ?
>>>>
>>>> Anyway, thank you for all your suggestions.
>>>>
>>>> Yeah, seeing how the apt system on debian mostly works to maintain and
>>> upgrade the packages to newer version, the 3.4 that is in unstable would
>>> replace the 3.2 one, unless some changes were made to the newer package.
>>>
>>> As mentioned earlier, creating a symlink in /usr/bin seems like a good
>>> idea too.
>>>
>>> Mat
>>
>>
>>
>
Hi there,

yes, change your source list to Sid/unstable will help you to install 3.4 in
Debian way.

A few suggestions though:
1: backup you current source list;
2: comment out security and volatile lines for Sid;
3: just upgrade eclipse and switch back to Lenny if you prefer staying in
the stable/boring land and do a source list update immediately.

--
Thanks and regards,

Zhan
From: Tsang Kim Wai on
Hi Angus Hedger, Zhan and All,

Thanks for all the suggestions.

As upgrading to "un-stable" may not be reversible, I think I would be
happy to stay in the "stable" release with eclipse 3.2 and eclipse 3.5
installed. That's enough.

Regards
Lawrence


On Mon, Jan 11, 2010 at 3:25 PM, Zhan <zhan(a)games.com> wrote:

>
>
> On Mon, Jan 11, 2010 at 9:06 AM, Angus Hedger <demidevil(a)gmail.com> wrote:
>
>> Hey there,
>>
>> Yes, as far as I know that would work, but if you are not careful you will
>> end up upgrading you'er whole system to sid (as someone who added unstable
>> sources to his Lenny install once by accident and ended up
>> in dependency hell with half the system upgraded and half not).
>>
>> Also sid is not recommended unless you are experienced with debian and
>> willing to fix it if everything breaks ;)
>>
>> So, I would recommended not changing your sources.list like that myself.
>>
>> Regards,
>>
>> Angus.
>>
>> On Sun, Jan 10, 2010 at 11:03 PM, Tsang Kim Wai <tkwinfo(a)gmail.com>wrote:
>>
>>> Hi All,
>>>
>>> Thanks for all your information. The eclipse 3.5 works OK.
>>>
>>> But if I want to try one of Mathias suggestion to upgrade my old
>>> eclipse 3.2 to eclipse 3.4 in the unstable release, then, in my
>>> understanding, I would need to edit the "/etc/apt/sources.list" file to
>>> change any "lenny" keywork to "sid".
>>>
>>> My sources.list file contains the following lines :
>>>
>>> deb http://ftp.hk.debian.org/debian/ lenny main contrib non-free
>>> deb-src http://ftp.hk.debian.org/debian/ lenny main contrib non-free
>>>
>>> deb http://security.debian.org/ lenny/updates main contrib non-free
>>> deb-src http://security.debian.org/ lenny/updates main contrib non-free
>>>
>>> deb http://volatile.debian.org/debian-volatile lenny/volatile main
>>> contrib non-free
>>> deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
>>> contrib non-free
>>>
>>> Then I think replacing all "lenny" to "sid" should change my Debian
>>> system from stable to un-stable release so that I could upgrade eclipse 3.2
>>> to eclipse 3.4 by running just "apt-get install eclipse". Is that the case ?
>>>
>>>
>>> Alternatively, if I don't change my Debian system to un-stable
>>> release through editing "sources.list", could I still upgrade my old eclipse
>>> 3.2 to eclipse 3.4 in other way ?
>>>
>>> Any comment / suggestion.
>>>
>>> Regards
>>> Lawrence
>>>
>>>
>>>
>>> On Mon, Jan 11, 2010 at 1:54 AM, Mathias <m9236(a)abc.se> wrote:
>>>
>>>> On Sun, 10 Jan 2010, Tsang Kim Wai wrote:
>>>>
>>>> Hi Nick Douma, Liam O'Toole and Mathias,
>>>>>
>>>>> It works by simply extracting the downloaded Eclipse 3.5 binary
>>>>> file
>>>>> into /usr/local/eclipse-3.5/ directory and then run the eclipse script
>>>>> under
>>>>> that directory. But I think, the eclipse 3.5 simple installation may
>>>>> depend
>>>>> on some configurations of my old eclipse 3.2 installation. That is, I
>>>>> may
>>>>> not un-install eclipse 3.2 while expecting eclipse 3.5 would work
>>>>> properly.
>>>>> Is that the case ?
>>>>>
>>>>> Anyway, thank you for all your suggestions.
>>>>>
>>>>> Yeah, seeing how the apt system on debian mostly works to maintain and
>>>> upgrade the packages to newer version, the 3.4 that is in unstable would
>>>> replace the 3.2 one, unless some changes were made to the newer package.
>>>>
>>>> As mentioned earlier, creating a symlink in /usr/bin seems like a good
>>>> idea too.
>>>>
>>>> Mat
>>>
>>>
>>>
>>
> Hi there,
>
> yes, change your source list to Sid/unstable will help you to install 3.4
> in Debian way.
>
> A few suggestions though:
> 1: backup you current source list;
> 2: comment out security and volatile lines for Sid;
> 3: just upgrade eclipse and switch back to Lenny if you prefer staying in
> the stable/boring land and do a source list update immediately.
>
> --
> Thanks and regards,
>
> Zhan
>