Home » Archived » IMP » lpg update site down
|
| Re: lpg update site down [message #22398 is a reply to message #22344] |
Sat, 05 July 2008 21:04   |
Eclipse User |
|
|
|
Originally posted by: regenmacher.online.de
The LPG update site you mention is ok.
Download is working as expected. There is another problem with this update
site.
Lets sort out. It is no rocked science.
When unziping the lpg.runtime_2.0.12.jar you see at
http://lpg.sourceforge.net/updates
you will get a feature.xml with a ref to lpg.runtime and three refs to
lpg.generator.XXX
After downloading you will see:
(A) in your installed eclipse-features a new entry
Feature Name: LPG Runtime,
Version 2.012,
FeatureId: lpg.runtime
(B) in your installed eclipse-plugins two new entries
(B1)
Plugin Name: LPG Fragment for XXX,
Version 2.0.12,
Plug-in ID: lpg.generator.XXX
(XXX is your OS)
and
(B2)
Plugin Name: LPG Runtime,
Version 2.0.12
Plug-in ID: lpg.runtime
All this is LPG-related with no (direct) relation to IMP. So there is an
extra update site.
BTW: Which eclipse you are using ?
Eclipse 3.4 ??
Downloading the current LPG, eclipse 3.4 will try to get the license-text
from a dead link. So you will get a 440-Error.
Note to the LPG-guys :
Some entries in feature.xml (zipped in lpg.runtime_2.0.12.jar) are dead
("http://www.example.com/license"), so any user downloading the current LPG
via the mentioned update-site will be asked to accept an UNKNOWN license.
Besides some problems with the eclipse-lawyers the user will be confused
about Error 440
Solution: Change the dead link in feature.xml to
http://www.eclipse.org/legal/epl-v10.html (EPL)
michael
..
"Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
news:g4khvo$a0c$1@build.eclipse.org...
> the entire lpg homepage and update site at sourceforge is down (403,
> please chmod it back!).
>
> http://lpg.sourceforge.net/updates/
>
> and another update thing: i just discovered the other imp update site (the
> sourceforge one) and was happy to find the 0.1.75 version online. i know
> imp will automatically add this update site, but because of an error the
> update check would never finish on my installation. but two update sites
> and one advertised dead link is a bit confusing. which one do you use?
>
> and a user story: i work on an ActionScript 3 editor at http://axdt.org in
> my spare time for a month now. I need it for my own work and instead of
> buying the commercial adobe product, i used imp to build myself a simple
> editor in two days. now it has around a hundred users that downloaded and
> installed it (without any project announcement, yet).
>
> i hope i can channel some useful bug reports in future. all bugs i have
> found last month were already fixed on svn.
>
> thank you for your work! and best regards
> mb0
|
|
| |
| Re: lpg update site down [message #22467 is a reply to message #22425] |
Sun, 06 July 2008 13:13 |
| Eclipse User |
|
|
|
Originally posted by: regenmacher.online.de
"Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
news:g4q83i$4gu$1@build.eclipse.org...
> ok, i made a wrong guess, and yes i tried it with 3.4 and had no idea of
> p2 failing with bad urls, saw the 403 in update/plugins and reported.
If it is is really a p2-problem, then here is a work-around:
Step 1
In Eclipse platform version 3.4, the old Update Manager still exists under
the covers for backwards compatibility. You can even re-enable the old
Update user interface by enabling the "Classic Update" capability on the
General > Capabilities preference page.
Step 2
Download LPG via the mentioned update-site
http://lpg.sourceforge.net/updates/ the old way
Step 3
Download IMP via the mentioned update-site
http://download.eclipse.org/technology/imp/updates/ the old way
Step 4
Reverse Step 1
Note 1: current there is no release of imp.
Note 2: leading zero in current numbers (0.1.74)
Note1 + Note2 => imp is a moving target
michael
|
|
|
| Re: lpg update site down [message #22685 is a reply to message #22467] |
Thu, 10 July 2008 16:07 |
 Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Hi All,
We apologize for these problems and don't quite understand what
happened. We had an IBM user (not part of IMP) who also ran into this
situation during the same period. I also am not an expert on the ins
and outs of update sites and the Update Manager, but I'll try to say
something anyway :-).
First, I think the LPG update site on SourceForge was down for at least
a little while. I've had temporary trouble connecting on other
occasions when there was no problem otherwise with the download. Also,
our user here was able to connect and download yesterday without problems.
I had not previously tried installing LPG from the SourceForge update
site using a version of Eclipse 3.4 with the p2 features active.
However, I did that just a few minutes ago and had no problems.
BTW, I am using the 3.4.0 SDK release. We did have other problems with
the p2 features on some of the earlier milestone/RC releases. We are
hoping that those have gone away with the new release. So far we have
not had problems but have only a little experience.
To install LPG from the SourceForge update site, I used the
"traditional" URL http://lpg.sourceforge.net/updates/. This URL is
still good. If you can't connect to this, the problem is not with the URL.
When I installed LPG, I got one feature with two plug-ins:
feature: LPG Runtime 2.0.23 lpg.runtime
plug-in: LPG Fragment for Win32 2.0.12 lpg.generator.win32_x86
plug-in: LPG Runtime 2.0.12 lpg.runtime
Note that the LPG that you get from the SourceForge update site is the
"stand-alone" LPG. You can use it with IMP (which we do sometimes) but
it is an independent parser-generator tool with no dependencies on IMP.
(At least for the time being, when working with IMP, you may at times
need to run the LPG executable as an external tool.)
Since we do still use the "external" LPG with IMP, even if someone has a
problem just with LPG that is unrelated to IMP, we would still like to
hear about it.
NOTE: In the IMP release, there is also a feature and some plug-ins
related to LPG:
feature: LPG IDE and Metatooling 0.1.* org.eclipse.imp.lpg
plug-in: LPG IDE Runtime 0.1.* org.eclipse.imp.lpg.runtime
plug-in: LPG IDE 0.1.* org.eclipse.imp.metatooling
and a couple of others. (These names have changed somewhat in the past
and may change again as we try to find the best way to describe things.)
What is LPG *within* IMP? Mainly it is two things:
1) An IMP-based IDE for LPG grammar specifications. The LPG IDE
Runtime plug-in supports this. (So this is the runtime for the IMP LPG
IDE, not the runtime for the external LPG tool.)
2) LPG-related meta-tooling, which is mainly wizard-related things for
generating LPG grammar skeletons and other parser-related components for
defining languages as part of the development of an IMP IDE. This also
includes a set of LPG grammar templates which are for use within IMP and
which are different from the LPG grammar templates that come with the
LPG external tool.
The LPG plug-ins for IMP *do* have dependencies on other IMP plug-ins,
notably org.eclipse.imp.runtime and org.eclipse.imp.metatooling (and
others that are part of the IMP release).
The latest release of IMP on the Eclipse.org update site is 0.1.74. We
have temporarily frozen our releases there pending the resolution of
some IP issues relating to things used by IMP. As some of you have
noticed, there is a later release (0.1.75) on the IMP SourceForge site.
This was built to validate recent updates to the code base. We are
continuing to update the code base and the changes are being deposited
into the IMP SVN repository on Eclipse.org.
Yes, IMP is a moving target. :-) If it were not, then we would have to
find new work. :-) Before we were on Eclipse, we kept our version
numbers sort of synchronized with the version of Eclipse that was
targeted. Now that we are on Eclipse, we have to number our first
official release beginning with 1, so pre-release versions are back to
starting with 0.*.
> Step 1
> In Eclipse platform version 3.4, the old Update Manager still exists
> under the covers for backwards compatibility. You can even re-enable the
> old Update user interface by enabling the "Classic Update" capability on
> the General > Capabilities preference page.
I didn't know about this; that's really great! But, as I said, I was
able to install LPG using the new update manager in Eclipse 3.4.0.
Anyway, I hope this helps and that you have found a way to work around
the problems if they have not actually disappeared.
Please let us know if you encounter further difficulties!
Regards,
Stan
Michael Strothjohann wrote:
>
> "Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
> news:g4q83i$4gu$1@build.eclipse.org...
>
>> ok, i made a wrong guess, and yes i tried it with 3.4 and had no idea
>> of p2 failing with bad urls, saw the 403 in update/plugins and reported.
>
> If it is is really a p2-problem, then here is a work-around:
>
> Step 1
> In Eclipse platform version 3.4, the old Update Manager still exists
> under the covers for backwards compatibility. You can even re-enable the
> old Update user interface by enabling the "Classic Update" capability on
> the General > Capabilities preference page.
>
> Step 2
> Download LPG via the mentioned update-site
> http://lpg.sourceforge.net/updates/ the old way
>
> Step 3
> Download IMP via the mentioned update-site
> http://download.eclipse.org/technology/imp/updates/ the old way
>
> Step 4
> Reverse Step 1
>
> Note 1: current there is no release of imp.
> Note 2: leading zero in current numbers (0.1.74)
>
> Note1 + Note2 => imp is a moving target
>
> michael
|
|
| |
| Re: lpg update site down [message #22773 is a reply to message #22398] |
Thu, 10 July 2008 16:31 |
Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Michael Strothjohann wrote:
> The LPG update site you mention is ok.
>
> Download is working as expected. There is another problem with this
> update site.
>
> Lets sort out. It is no rocked science.
>
> When unziping the lpg.runtime_2.0.12.jar you see at
> http://lpg.sourceforge.net/updates
> you will get a feature.xml with a ref to lpg.runtime and three refs to
> lpg.generator.XXX
>
> After downloading you will see:
>
> (A) in your installed eclipse-features a new entry
> Feature Name: LPG Runtime,
> Version 2.012,
> FeatureId: lpg.runtime
>
>
> (B) in your installed eclipse-plugins two new entries
>
> (B1)
> Plugin Name: LPG Fragment for XXX,
> Version 2.0.12,
> Plug-in ID: lpg.generator.XXX
> (XXX is your OS)
>
> and
>
> (B2)
> Plugin Name: LPG Runtime,
> Version 2.0.12
> Plug-in ID: lpg.runtime
>
> All this is LPG-related with no (direct) relation to IMP. So there is an
> extra update site.
Yes, this is all correct. (Please see my response to your later post.)
As you say, this is all LPG-specific, relating to LPG as a stand-alone
tool with no dependency on IMP. However, in IMP we do make use of LPG
as an external tool. In particular, the IMP release contains an
IMP-based IDE for LPG grammar specifications (you already know this).
The builder in the LPG IDE runs an LPG generator executable. That
generator executable comes (for now) from the LPG SourceForge site.
> BTW: Which eclipse you are using ?
> Eclipse 3.4 ??
I have recently used 3.3.1.1, 3.4 M7 (with the "classic" update
manager), and 3.4.0 with the new p2 update manager. Going forward I
expect to be using 3.3-something and 3.4.0. We are hoping that IMP can
be used with either of those (this was possible recently, and we would
like to try to keep it that way as long as it's not too much trouble).
>
> Downloading the current LPG, eclipse 3.4 will try to get the
> license-text from a dead link. So you will get a 440-Error.
I recently (an hour ago?) tried this download in 3.4.0 with the p2
update manager and did not have a problem. Please let us know if you do
continue to have trouble.
>
> Note to the LPG-guys :
> Some entries in feature.xml (zipped in lpg.runtime_2.0.12.jar) are dead
> ("http://www.example.com/license"), so any user downloading the current
> LPG via the mentioned update-site will be asked to accept an UNKNOWN
> license. Besides some problems with the eclipse-lawyers the user will be
> confused about Error 440
>
> Solution: Change the dead link in feature.xml to
> http://www.eclipse.org/legal/epl-v10.html (EPL)
Good catch! Thanks! We'll update that.
Regards,
Stan
>
> michael
> .
> "Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
> news:g4khvo$a0c$1@build.eclipse.org...
>> the entire lpg homepage and update site at sourceforge is down (403,
>> please chmod it back!).
>>
>> http://lpg.sourceforge.net/updates/
>>
>> and another update thing: i just discovered the other imp update site
>> (the sourceforge one) and was happy to find the 0.1.75 version online.
>> i know imp will automatically add this update site, but because of an
>> error the update check would never finish on my installation. but two
>> update sites and one advertised dead link is a bit confusing. which
>> one do you use?
>>
>> and a user story: i work on an ActionScript 3 editor at
>> http://axdt.org in my spare time for a month now. I need it for my own
>> work and instead of buying the commercial adobe product, i used imp to
>> build myself a simple editor in two days. now it has around a hundred
>> users that downloaded and installed it (without any project
>> announcement, yet).
>>
>> i hope i can channel some useful bug reports in future. all bugs i
>> have found last month were already fixed on svn.
>>
>> thank you for your work! and best regards
>> mb0
>
|
|
|
| Re: lpg update site down [message #572104 is a reply to message #22344] |
Sat, 05 July 2008 21:04 |
Michael Strothjohann
Messages: 52
Registered: July 2009 |
Member |
|
|
The LPG update site you mention is ok.
Download is working as expected. There is another problem with this update
site.
Lets sort out. It is no rocked science.
When unziping the lpg.runtime_2.0.12.jar you see at
http://lpg.sourceforge.net/updates
you will get a feature.xml with a ref to lpg.runtime and three refs to
lpg.generator.XXX
After downloading you will see:
(A) in your installed eclipse-features a new entry
Feature Name: LPG Runtime,
Version 2.012,
FeatureId: lpg.runtime
(B) in your installed eclipse-plugins two new entries
(B1)
Plugin Name: LPG Fragment for XXX,
Version 2.0.12,
Plug-in ID: lpg.generator.XXX
(XXX is your OS)
and
(B2)
Plugin Name: LPG Runtime,
Version 2.0.12
Plug-in ID: lpg.runtime
All this is LPG-related with no (direct) relation to IMP. So there is an
extra update site.
BTW: Which eclipse you are using ?
Eclipse 3.4 ??
Downloading the current LPG, eclipse 3.4 will try to get the license-text
from a dead link. So you will get a 440-Error.
Note to the LPG-guys :
Some entries in feature.xml (zipped in lpg.runtime_2.0.12.jar) are dead
("http://www.example.com/license"), so any user downloading the current LPG
via the mentioned update-site will be asked to accept an UNKNOWN license.
Besides some problems with the eclipse-lawyers the user will be confused
about Error 440
Solution: Change the dead link in feature.xml to
http://www.eclipse.org/legal/epl-v10.html (EPL)
michael
..
"Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
news:g4khvo$a0c$1@build.eclipse.org...
> the entire lpg homepage and update site at sourceforge is down (403,
> please chmod it back!).
>
> http://lpg.sourceforge.net/updates/
>
> and another update thing: i just discovered the other imp update site (the
> sourceforge one) and was happy to find the 0.1.75 version online. i know
> imp will automatically add this update site, but because of an error the
> update check would never finish on my installation. but two update sites
> and one advertised dead link is a bit confusing. which one do you use?
>
> and a user story: i work on an ActionScript 3 editor at http://axdt.org in
> my spare time for a month now. I need it for my own work and instead of
> buying the commercial adobe product, i used imp to build myself a simple
> editor in two days. now it has around a hundred users that downloaded and
> installed it (without any project announcement, yet).
>
> i hope i can channel some useful bug reports in future. all bugs i have
> found last month were already fixed on svn.
>
> thank you for your work! and best regards
> mb0
|
|
| | |
| Re: lpg update site down [message #572279 is a reply to message #22467] |
Thu, 10 July 2008 16:07 |
Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Hi All,
We apologize for these problems and don't quite understand what
happened. We had an IBM user (not part of IMP) who also ran into this
situation during the same period. I also am not an expert on the ins
and outs of update sites and the Update Manager, but I'll try to say
something anyway :-).
First, I think the LPG update site on SourceForge was down for at least
a little while. I've had temporary trouble connecting on other
occasions when there was no problem otherwise with the download. Also,
our user here was able to connect and download yesterday without problems.
I had not previously tried installing LPG from the SourceForge update
site using a version of Eclipse 3.4 with the p2 features active.
However, I did that just a few minutes ago and had no problems.
BTW, I am using the 3.4.0 SDK release. We did have other problems with
the p2 features on some of the earlier milestone/RC releases. We are
hoping that those have gone away with the new release. So far we have
not had problems but have only a little experience.
To install LPG from the SourceForge update site, I used the
"traditional" URL http://lpg.sourceforge.net/updates/ This URL is
still good. If you can't connect to this, the problem is not with the URL.
When I installed LPG, I got one feature with two plug-ins:
feature: LPG Runtime 2.0.23 lpg.runtime
plug-in: LPG Fragment for Win32 2.0.12 lpg.generator.win32_x86
plug-in: LPG Runtime 2.0.12 lpg.runtime
Note that the LPG that you get from the SourceForge update site is the
"stand-alone" LPG. You can use it with IMP (which we do sometimes) but
it is an independent parser-generator tool with no dependencies on IMP.
(At least for the time being, when working with IMP, you may at times
need to run the LPG executable as an external tool.)
Since we do still use the "external" LPG with IMP, even if someone has a
problem just with LPG that is unrelated to IMP, we would still like to
hear about it.
NOTE: In the IMP release, there is also a feature and some plug-ins
related to LPG:
feature: LPG IDE and Metatooling 0.1.* org.eclipse.imp.lpg
plug-in: LPG IDE Runtime 0.1.* org.eclipse.imp.lpg.runtime
plug-in: LPG IDE 0.1.* org.eclipse.imp.metatooling
and a couple of others. (These names have changed somewhat in the past
and may change again as we try to find the best way to describe things.)
What is LPG *within* IMP? Mainly it is two things:
1) An IMP-based IDE for LPG grammar specifications. The LPG IDE
Runtime plug-in supports this. (So this is the runtime for the IMP LPG
IDE, not the runtime for the external LPG tool.)
2) LPG-related meta-tooling, which is mainly wizard-related things for
generating LPG grammar skeletons and other parser-related components for
defining languages as part of the development of an IMP IDE. This also
includes a set of LPG grammar templates which are for use within IMP and
which are different from the LPG grammar templates that come with the
LPG external tool.
The LPG plug-ins for IMP *do* have dependencies on other IMP plug-ins,
notably org.eclipse.imp.runtime and org.eclipse.imp.metatooling (and
others that are part of the IMP release).
The latest release of IMP on the Eclipse.org update site is 0.1.74. We
have temporarily frozen our releases there pending the resolution of
some IP issues relating to things used by IMP. As some of you have
noticed, there is a later release (0.1.75) on the IMP SourceForge site.
This was built to validate recent updates to the code base. We are
continuing to update the code base and the changes are being deposited
into the IMP SVN repository on Eclipse.org.
Yes, IMP is a moving target. :-) If it were not, then we would have to
find new work. :-) Before we were on Eclipse, we kept our version
numbers sort of synchronized with the version of Eclipse that was
targeted. Now that we are on Eclipse, we have to number our first
official release beginning with 1, so pre-release versions are back to
starting with 0.*.
> Step 1
> In Eclipse platform version 3.4, the old Update Manager still exists
> under the covers for backwards compatibility. You can even re-enable the
> old Update user interface by enabling the "Classic Update" capability on
> the General > Capabilities preference page.
I didn't know about this; that's really great! But, as I said, I was
able to install LPG using the new update manager in Eclipse 3.4.0.
Anyway, I hope this helps and that you have found a way to work around
the problems if they have not actually disappeared.
Please let us know if you encounter further difficulties!
Regards,
Stan
Michael Strothjohann wrote:
>
> "Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
> news:g4q83i$4gu$1@build.eclipse.org...
>
>> ok, i made a wrong guess, and yes i tried it with 3.4 and had no idea
>> of p2 failing with bad urls, saw the 403 in update/plugins and reported.
>
> If it is is really a p2-problem, then here is a work-around:
>
> Step 1
> In Eclipse platform version 3.4, the old Update Manager still exists
> under the covers for backwards compatibility. You can even re-enable the
> old Update user interface by enabling the "Classic Update" capability on
> the General > Capabilities preference page.
>
> Step 2
> Download LPG via the mentioned update-site
> http://lpg.sourceforge.net/updates/ the old way
>
> Step 3
> Download IMP via the mentioned update-site
> http://download.eclipse.org/technology/imp/updates/ the old way
>
> Step 4
> Reverse Step 1
>
> Note 1: current there is no release of imp.
> Note 2: leading zero in current numbers (0.1.74)
>
> Note1 + Note2 => imp is a moving target
>
> michael
|
|
| |
| Re: lpg update site down [message #572324 is a reply to message #22398] |
Thu, 10 July 2008 16:31 |
Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Michael Strothjohann wrote:
> The LPG update site you mention is ok.
>
> Download is working as expected. There is another problem with this
> update site.
>
> Lets sort out. It is no rocked science.
>
> When unziping the lpg.runtime_2.0.12.jar you see at
> http://lpg.sourceforge.net/updates
> you will get a feature.xml with a ref to lpg.runtime and three refs to
> lpg.generator.XXX
>
> After downloading you will see:
>
> (A) in your installed eclipse-features a new entry
> Feature Name: LPG Runtime,
> Version 2.012,
> FeatureId: lpg.runtime
>
>
> (B) in your installed eclipse-plugins two new entries
>
> (B1)
> Plugin Name: LPG Fragment for XXX,
> Version 2.0.12,
> Plug-in ID: lpg.generator.XXX
> (XXX is your OS)
>
> and
>
> (B2)
> Plugin Name: LPG Runtime,
> Version 2.0.12
> Plug-in ID: lpg.runtime
>
> All this is LPG-related with no (direct) relation to IMP. So there is an
> extra update site.
Yes, this is all correct. (Please see my response to your later post.)
As you say, this is all LPG-specific, relating to LPG as a stand-alone
tool with no dependency on IMP. However, in IMP we do make use of LPG
as an external tool. In particular, the IMP release contains an
IMP-based IDE for LPG grammar specifications (you already know this).
The builder in the LPG IDE runs an LPG generator executable. That
generator executable comes (for now) from the LPG SourceForge site.
> BTW: Which eclipse you are using ?
> Eclipse 3.4 ??
I have recently used 3.3.1.1, 3.4 M7 (with the "classic" update
manager), and 3.4.0 with the new p2 update manager. Going forward I
expect to be using 3.3-something and 3.4.0. We are hoping that IMP can
be used with either of those (this was possible recently, and we would
like to try to keep it that way as long as it's not too much trouble).
>
> Downloading the current LPG, eclipse 3.4 will try to get the
> license-text from a dead link. So you will get a 440-Error.
I recently (an hour ago?) tried this download in 3.4.0 with the p2
update manager and did not have a problem. Please let us know if you do
continue to have trouble.
>
> Note to the LPG-guys :
> Some entries in feature.xml (zipped in lpg.runtime_2.0.12.jar) are dead
> ("http://www.example.com/license"), so any user downloading the current
> LPG via the mentioned update-site will be asked to accept an UNKNOWN
> license. Besides some problems with the eclipse-lawyers the user will be
> confused about Error 440
>
> Solution: Change the dead link in feature.xml to
> http://www.eclipse.org/legal/epl-v10.html (EPL)
Good catch! Thanks! We'll update that.
Regards,
Stan
>
> michael
> .
> "Martin Schnabel" <mb0@mb0.org> schrieb im Newsbeitrag
> news:g4khvo$a0c$1@build.eclipse.org...
>> the entire lpg homepage and update site at sourceforge is down (403,
>> please chmod it back!).
>>
>> http://lpg.sourceforge.net/updates/
>>
>> and another update thing: i just discovered the other imp update site
>> (the sourceforge one) and was happy to find the 0.1.75 version online.
>> i know imp will automatically add this update site, but because of an
>> error the update check would never finish on my installation. but two
>> update sites and one advertised dead link is a bit confusing. which
>> one do you use?
>>
>> and a user story: i work on an ActionScript 3 editor at
>> http://axdt.org in my spare time for a month now. I need it for my own
>> work and instead of buying the commercial adobe product, i used imp to
>> build myself a simple editor in two days. now it has around a hundred
>> users that downloaded and installed it (without any project
>> announcement, yet).
>>
>> i hope i can channel some useful bug reports in future. all bugs i
>> have found last month were already fixed on svn.
>>
>> thank you for your work! and best regards
>> mb0
>
|
|
|
Goto Forum:
Current Time: Fri Dec 27 06:29:27 GMT 2024
Powered by FUDForum. Page generated in 0.04096 seconds |
] 
Search
Help
Register
Login
Home
