Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] freezing cerowrt-3.3
Date: Tue, 1 May 2012 05:25:30 -0700	[thread overview]
Message-ID: <CAA93jw68MALDbLVDSh8frfPcouoUbugFOxxqhoOAV3cL0VhGrQ@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YDYWE3d7XkdXXs=0fgZpvhuE=_uoMrreRNkggA79XDCDA@mail.gmail.com>

Heh. That's an old mistake. The diversity enabled version of babeld
got merged to head a long time ago. (well, there was a ECN patch in it
that juliusz didn't like)

Just change the .config for babelz to not do it or uninstall it.
we use the official babeld in full diversity mode instead.

On Tue, May 1, 2012 at 4:48 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
> Dave,
>
> While we're on the subject of freezing. I'm trying to build after the latest
> changes and it "freezes" on babeld after this:
>  make[3] -C feeds/cero/net/aqm-scripts compile
>  make[3] -C feeds/cero/net/babelz compile
>
> ~src/cerowrt/wndr3700v2/tmp/babeld-20111019 is empty and when I ctrl+c that
> and make V=99, then it shows that it can't wget babeld-20111019.tar.gz from
> mirror2.openwrt.org (rightly so, as it's babeld-1.3.1.tar.gz there) and
> tries to git clone it from some .fr site.
> But the git clone command hangs.
>
> Question, how/where do I update from babeld-20111019 to babeld-1.3.1 ?
>
> Regards,
> Maciej
>
> On Tue, May 1, 2012 at 10:19 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> Based on the sudden interest in building cerowrt, and my threats to freeze
>> 'later this week', I figured I'd freeze tonight just to keep you on your
>> toes.
>>
>> While some dig the 'branch' facility in git - I do use it myself - I think
>> it's
>> saner to have a separate repo name for each major branch. So I renamed
>> several repos tonight. After a linux 3.4 or 3.5 (there isn't anything in
>> 3.4 we
>> need so...) process starts up, we'll start a 'next' set of repos.
>>
>> I'm certainly open to discussion as to how
>> and what to do with development moving forward, but I'd really like to
>> have something stable enough for your mom and dad to use day to day,
>> and move on to focusing on some narrow problems like aqm development
>> rather than "tracking and fixing the whole universe".
>>
>> So... *my* intent is to only push major bugs fixes and fixes for
>> CVEs (security violations) into these repos,
>>
>> For a while, anyway.
>>
>> you will need to edit your .git/config for your copy of the
>> cerowrt-luci and ceropackages repos to append a -3.3 to
>> point to the right renamed repos on github.
>>
>> I have also frozen the copy of the openwrt package database:
>>
>> git clone git://github.com/dtaht/cerowrt-packages-3.3.git
>>
>> You will want to edit your feeds.conf to point to that rather than
>> 'packages'.
>>
>> As freezes go, this is still kind of a dairy queen kind of soft freeze,
>> there's a couple things left to land.
>>
>> I have pushed out the current patch set for 3.3.4-4. While I continue to
>> battle bug #379 I'm pretty happy with it under normal use.
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> US Tel: 1-239-829-5608
>> http://www.bufferbloat.net
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

  parent reply	other threads:[~2012-05-01 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01  8:19 Dave Taht
2012-05-01 11:48 ` Maciej Soltysiak
2012-05-01 12:24   ` Ketan Kulkarni
2012-05-01 12:25   ` Dave Taht [this message]
2012-05-01 17:40     ` Maciej Soltysiak
2012-05-01 17:52       ` Dave Taht
2012-05-01 19:11         ` Maciej Soltysiak
2012-05-01 21:50           ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw68MALDbLVDSh8frfPcouoUbugFOxxqhoOAV3cL0VhGrQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox