Bug#487388: Helping with flightgear package

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#487388: Helping with flightgear package

Eddy Petrișor
Hello,

The Debian version of flightgear is 2.6.0 while the current upstream
version is 2.10, and Ove has a RFH for flightgear and in the SVN repo
there were no changes since August 5, last year (revision 229).
There is also a request for the new upstream version (714260).

So, Scott, could you, please package 2.10 in the git repo and NMU it
to unstable (in a delay queue)?

--
Regards,
EddyP
=============================================
The universe is not required to be in perfect harmony with human
ambition. - Carl Sagan


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Markus Wanner-2
Scott,

On 07/29/2013 03:45 PM, Scott Howard wrote:
> You can use it if it helps, or ignore it if it doesn't. It was mostly
> for my own use. I've been really busy lately and haven't gotten around
> to packaging and uploading newer versions.

I've pushed upstream/2.10.0 and an update to the debian packaging of it.
It's based It's based on your changes. I hope that's okay.

Obviously, it's not of much use without an updated simgear package,
which flightgear depends on. I have updates for that ready as well, but
am not sure where to push to.

Can you please import the svn history of simgear into git and create a
repository for it on collab-maint? (I'm just a DM - not sure where else
I should request creation of a repo).

Oh, and then there's fgfs-base as well. I don't think we want all that
data in a git repo. How about a git repo for just the debian directory?

> that git repo uses git-buildpackage and a pristine-tar branch for
> generating tarballs, but again - whomever wants to do the work can do
> it how ever they like.

I didn't ever use git-buildpackage so far... Shoud I have pushed
something to the pristine-tar branch as well?

Regards

Markus Wanner


signature.asc (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Scott Howard-7
On Wed, Jul 31, 2013 at 11:24 AM, Markus Wanner <[hidden email]> wrote:
> Scott,
>
> On 07/29/2013 03:45 PM, Scott Howard wrote:
>> You can use it if it helps, or ignore it if it doesn't. It was mostly
>> for my own use. I've been really busy lately and haven't gotten around
>> to packaging and uploading newer versions.
>
> I've pushed upstream/2.10.0 and an update to the debian packaging of it.
> It's based It's based on your changes. I hope that's okay.

thanks!

>
> Obviously, it's not of much use without an updated simgear package,
> which flightgear depends on. I have updates for that ready as well, but
> am not sure where to push to.
>
> Can you please import the svn history of simgear into git and create a
> repository for it on collab-maint? (I'm just a DM - not sure where else
> I should request creation of a repo).

I'll be traveling a bit, but I'll share how I copied the history from svn->git

https://wiki.debian.org/Alioth/Git#Convert_a_SVN_Alioth_repository_to_Git

And here's how to set up a git repo on the debian servers:
https://wiki.debian.org/Alioth/Git

> Oh, and then there's fgfs-base as well. I don't think we want all that
> data in a git repo. How about a git repo for just the debian directory?

this sounds best for large amount of data

>> that git repo uses git-buildpackage and a pristine-tar branch for
>> generating tarballs, but again - whomever wants to do the work can do
>> it how ever they like.

Here's a good tutorial
https://wiki.debian.org/PackagingWithGit

whenever I use "git-import-dsc" or "git-import-org" I pass the
--pristine-tar argument.

When you build using "git-buildpackage" you can then just use the
--git-pristine-tar argument to generate .orig.tar.gz if you haven't
already downloaded them. It's nice to have that ability.

~Scott


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Markus Wanner-2
In reply to this post by Markus Wanner-2
On 07/31/2013 05:24 PM, Markus Wanner wrote:
> I've pushed upstream/2.10.0 and an update to the debian packaging of it.
> It's based It's based on your changes. I hope that's okay.
>
> Obviously, it's not of much use without an updated simgear package,
> which flightgear depends on. I have updates for that ready as well, but
> am not sure where to push to.

Just as a heads up: all three are now available on collab-maint and are
updated to work together to provide FlightGear 2.10:

http://anonscm.debian.org/gitweb/?p=collab-maint/simgear.git
http://anonscm.debian.org/gitweb/?p=collab-maint/flightgear-data.git
http://anonscm.debian.org/gitweb/?p=collab-maint/flightgear.git

I'm still working on it, but it's worth pointing out a few design
decisions that may be controversial:

 - I moved the scenery data package back into the base one, as it's
   too small to matter (< 10 MiB) and didn't disturb terrasync, either.
 - Split AI data into its own package (ca. 130 MiB)
 - Consistently renamed fgfs to flightgear (package names)
 - Renamed simgear to libsimgear, split to match SONAMES

I'd still like to:

 - Use debhelper 7 for simgear as well. And get rid of the static
   variant of that library in libsimgear-dev. It would simplify rules a
   lot. Anybody opposed to that?

I envision flightgear-data-base to be a package that's sufficient to run
flightgear on. No AI, no object models, only the default c172 aircraft.

(Of course, that currently emits lots of warnings and load errors. I
hope to be able to get rid of those eventually.)

Regards

Markus Wanner


signature.asc (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Scott Howard-7
In reply to this post by Eddy Petrișor
On Sun, Aug 11, 2013 at 7:55 AM, Eddy Petrișor <[hidden email]> wrote:
> 2013/7/29 Scott Howard <[hidden email]>:
>> On Mon, Jul 29, 2013 at 8:43 AM, Markus Wanner <[hidden email]> wrote:
>> You can use it if it helps, or ignore it if it doesn't. It was mostly
>> for my own use. I've been really busy lately and haven't gotten around
>> to packaging and uploading newer versions.
>
> Scott, if the package is prepared by Markus, would you be able to
> upload it to the official archive?

I'll be happy to upload, just let me know when everything is ready
(flightgear, simgear, libraries, etc.)
I cannot test the package myself, my hardware isn't good enough - but
I can make sure it is debian policy compliant and rely on your own
testing.

~Scott


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Markus Wanner-2
On 08/11/2013 05:31 PM, Scott Howard wrote:
> I'll be happy to upload, just let me know when everything is ready
> (flightgear, simgear, libraries, etc.)
> I cannot test the package myself, my hardware isn't good enough - but
> I can make sure it is debian policy compliant and rely on your own
> testing.

I just read that the 2.12 release got postponed to September. So I
currently think it still makes sense to upload 2.10 and gain experience
with it. It's certainly quite a step since 2.6.

Scott, I now consider the packaging here ready for upload to unstable.
Please review:

http://anonscm.debian.org/gitweb/?p=collab-maint/simgear.git
http://anonscm.debian.org/gitweb/?p=collab-maint/flightgear-data.git
http://anonscm.debian.org/gitweb/?p=collab-maint/flightgear.git

Note that flightgear-data is special in that the origin files are not
included in the git tree. Please get the base data from one of the
mirrors and symlink to fgfs-base_2.10.0.orig.tar.bz2 (723 MiB). Two
possible mirrors are:

> ftp://ftp.de.flightgear.org/pub/fgfs/Shared/FlightGear-data-2.10.0.tar.bz2
> ftp://ftp.kingmont.com/flightsims/flightgear/Shared/FlightGear-data-2.10.0.tar.bz2


I'm a DM and would also appreciate upload permissions. Shall I add
myself as an uploader on these packages?


Some implementation notes: I changes the simgear library to use
debhelper 7 as well. This strips the static variant, which I think is
not needed.

I didn't touch how the data package is split, yet. Since my last mail,
that is. I.e. compared to 2.6, I merged scenery back into the base
package, but split out AI, which is a lot bigger.

However, according to upstream, it's not save to leave away portions of
the provided data package (certainly not simple portions like entire AI,
Models, Scenery or Aircraft directories). Thus, strictly speaking, all
data packages are required. And given former bugs, I now simply made all
data packages a dependency. That's a bit unfortunate, but safe.

I intend to look into splitting data packages or providing some kind of
download manager. Together with a better integration with terrasync. But
I don't want to withhold the current packaging because of that.

Regards

Markus Wanner


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Scott Howard-7
On Mon, Aug 19, 2013 at 10:50 AM, Markus Wanner <[hidden email]> wrote:
> I'm a DM and would also appreciate upload permissions. Shall I add
> myself as an uploader on these packages?

Yes, please add yourself as an uploader. I can add DM permissions once
it goes through the new queue, but I think you're taking on the
appropriate responsibility to be an uploader.

I'll check out the packages and upload once you add yourself to debian/control.

Cheers
Scott


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Eddy Petrișor
In reply to this post by Markus Wanner-2
2013/8/19 Markus Wanner <[hidden email]>:
> I intend to look into splitting data packages or providing some kind of
> download manager. Together with a better integration with terrasync. But
> I don't want to withhold the current packaging because of that.

Hi Markus,

When trying to integrate with terrasync, please take into account that
the application is hightly dependent on a specific libsvn version
that, IIRC, is dictated by the server. This could raise some issues if
the version is too old, and might require bundling the lib inside the
terrasync binary/package.


P.S.: Thanks for your work.

--
Regards,
EddyP
=============================================
The universe is not required to be in perfect harmony with human
ambition. - Carl Sagan


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Saikrishna Arcot
According to this post, the flightgear-data repo will get smaller, with some parts being downloaded through other sources. If this happens, would it be possible to re-split the flightgear-data package to have one package per download source?

On Mon 19 Aug 2013 04:51:19 PM EDT, Eddy Petrișor wrote:

2013/8/19 Markus Wanner [hidden email]:

I intend to look into splitting data packages or providing some kind of
download manager. Together with a better integration with terrasync. But
I don't want to withhold the current packaging because of that.


Hi Markus,

When trying to integrate with terrasync, please take into account that
the application is hightly dependent on a specific libsvn version
that, IIRC, is dictated by the server. This could raise some issues if
the version is too old, and might require bundling the lib inside the
terrasync binary/package.


P.S.: Thanks for your work.

-- 
Saikrishna Arcot
Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Markus Wanner-2
On 09/03/2013 05:56 PM, Saikrishna Arcot wrote:
> According to this
> <http://sourceforge.net/mailarchive/forum.php?thread_name=4C5262AE-653A-475F-AD09-91FE7461768C%40mac.com&forum_name=flightgear-devel>
> post, the flightgear-data repo will get smaller, with some parts being
> downloaded through other sources.

Thanks for the heads up. I didn't know about these plans. However, we're
only about to see 2.12, soon-ish....

> If this happens, would it be possible
> to re-split the flightgear-data package to have one package per download
> source?

Of course.

Regards

Markus Wanner


signature.asc (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#487388: [pkg-fgfs-crew] Bug#714260: Helping with flightgear package

Scott Howard-7
All the new packages have cleared the NEW queue and are in
experimental. Markus has been granted DM-upload access to those
packages and is a DM, so it looks like it's ready for him to upload to
experimental when it's ready.

Thanks for your contribution, Markus! If you need anything else, let me know.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]