[Debian-olpc-devel] [Sugar-devel] [IAEP] Glucose 0.84 and 0.85 packaged for Debian!

David Farning dfarning at sugarlabs.org
Mon Sep 21 00:30:07 UTC 2009

On Sun, Sep 20, 2009 at 4:56 AM, Jonas Smedegaard <dr at jones.dk> wrote:
> On Sun, Sep 20, 2009 at 03:24:23AM +0200, Jonas Smedegaard wrote:
>> On Sat, Sep 19, 2009 at 06:49:00PM -0500, David Farning wrote:
>>> 2. manually sync /debian from git.debian.org to git.gnewsense.org
>>> 3. do final work in git.gnewsense.org
>> Is Alioth such a cruel place to work together?  Is it me - am I awful to
>> work with?  Why do you ask for my advice on how to most effectively avoid
>> working together with me?!?
> Sorry for being aggressive above!

No problem.  I think we all experience the emotions you expressed from
time to time.  The GPL can be a cruel lover!  The situation is that
Debian is a technically excellent and flexibility which is great for

A couple of months ago your packaging systems was pretty new.... and
confusing.  Yesterday I was able to build test packages for GnewSense
and Ubuntu.  Pretty Cool.

> I realize now (after some sleep, and then working some on a talk I will hold
> next week in Taiwan about interaction between upstreams, distros and
> subdistros) that branching off a Git is a *use* of my work.  I should not
> discourage *use*, even if it comes in a diferent form than I had envisioned.

> So please accept my apology, and if not too late (if my initial response
> didn't discourage you), then please do return with whatever technical
> questions you have regarding early branching for gNewSense.  I shall try to
> help you succeed with your branching of my work if that is really what you
> want to do.
>> Hope you will engage more than just fork off,
> Above remark still stands :-)

This what I was trying to ask, if rather unclearly.  Downstream
projects will require minor modification of your /Debian dir to
accommodate different policies, build tools, and distro dependency
versions, ....

I am wondering, since we are creating fresh downstream package with a
new build-tool, how can we create a useful work flow for both upstream
and downstream.  With down streams using git-buildpackage and cdbs, it
seems pretty straight forward to ensure that useful patches make it
back to git.debian.org.


> Also, I still recommend limiting cross-posts to initial announcements and
> doing follow-ups only at a single list: Invite broadly but have the actual
> conversation in a single "meeting room" rather than shouting all out from
> the hill tops.  For this discussion I recommend using the Alioth list, and
> have added a reply-to accordingly.
> I only continue cross-posting as long as others do.  If you want to read all
> of this thread, then beware that some of it reside only at the Alioth list.
> If you want to spawn a different subtopic which might be better suited for a
> different of the cross-posted lists, then do cross-post, but change the
> subject line, and propose a new single list for follow-ups.
>  - Jonas
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private
> Version: GnuPG v1.4.10 (GNU/Linux)
> iQIcBAEBCgAGBQJKtfw/AAoJECx8MUbBoAEhFv8P/1JzxOMYsne7U4cq6uw1aaF2
> MiFcAJu8MY2T0eY7kBAdyYUbpGy0WLrnrLWHU4u/ZehIldlBNfx8TXX4EMdUVrqd
> C+wcPFZe2DpaUFFnLSzNQo+ntZ1683ZlKBBoltdr0BbwjAPVGIsLFZKrIEZsIQrn
> dZeAsPe75nKBRcwr4wWmvkD6ZcezgZuShd/G3uzNsZCgKxrrvcMXR7hrfxMTpRi1
> snjCZiee+mAQ++svVZuEH/dRUWZSo264nI6sOcodlZHv68UngYVYYFe8XbXFM8S0
> R3AzAQ7ipu9qLfHdmnqXeVkz9qkRpHrzerwCzEVMKLyLn8A8fzgfSqG7sE8lu+go
> AMPZPhtSG1Yy7HvBZrEGyflY89vWIvf+ncXqCywm5EuZGdqOoEmJr7dSpxAG+H4q
> Mzn57oRec0PQlQgjP3zVywbV1hw9VRzz4wOwA7KbDbt72j22YdyvRdQrRm7R1RYv
> nMJA74ygnkznmgsYUTX+KYrUMEFAPX1fUbwgR5gI/qs59v41s8xGo0qwp72Z+69S
> WIgfsxRdjpGux30RzA6q3u9Xe0EoUBobBVUUHbWl3Uz26WpAJIFS/kxXVoLyz6xl
> YfP4zyn3YuVLm3oVh3VvhDZ1i6QnKksz9bxcOiisfXT02NGJ1Dd/Pctd8qJdxGaE
> =WEi+

More information about the Debian-olpc-devel mailing list