PyBombs install maint branch from fresh

Dear Sirs,

I am performing fresh gnuradio installation using pybombs.
Pybombs install master branch by default.
How to make pybombs install ‘maint’ instead?

[email protected]: ~/download/pybombs $ git checkout maint
error: pathspec ‘maint’ did not match any file(s) known to git.

On 07/23/2014 07:14 AM, Activecat wrote:

Dear Sirs,

I am performing fresh gnuradio installation using pybombs.
Pybombs install master branch by default.
How to make pybombs install ‘maint’ instead?

[email protected]: ~/download/pybombs $ git checkout maint
error: pathspec ‘maint’ did not match any file(s) known to git.

This is not how you use git; you need to give it a remote branch to
track first. Also, if you checked out ‘maint’ on pybombs, it wouldn’t
necessarily check out ‘maint’ on any SW package it’s trying to install.

I assume you’re trying to install GNU Radio maint, right? I guess one
way would be to modify the gnuradio.lwr recipe, change the default
branch to maint.

M

On Wed, Jul 23, 2014 at 5:16 PM, Martin B. [email protected]
wrote:

This is not how you use git; you need to give it a remote branch to
track first. Also, if you checked out ‘maint’ on pybombs, it wouldn’t
necessarily check out ‘maint’ on any SW package it’s trying to install.

I assume you’re trying to install GNU Radio maint, right? I guess one
way would be to modify the gnuradio.lwr recipe, change the default
branch to maint.

M

Thanks.
yes, I am trying to install GNU Radio maintenance branch.
I will change the gitbranch of gnuradio.lwr recipe to ‘maint’.
Does this means the uhd.lwr also need to be ‘maint’, or can just be
‘master’ as default?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As UHD and GNU Radio are widely independent, you can use whatever
combination you want in almost any situation (aside from severe API
breakage).

On 23.07.2014 13:09, Activecat wrote:

[email protected]: ~/download/pybombs $ git checkout maint error:

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTz5lmAAoJEBQ6EdjyzlHtydwIAKsGcYwcJCO4lu0LCnoccr5U
wdwU5yDkKqdapAm7N1weZc6eQss2lKpTAu1lD21s6v4WKxC2dIWsvHdqQCWX1mlJ
EtFp3MvrI28QUZppfNUc8y9/wvSIAcCcxxf8xOCug2FZMREzz19rt2WWSSXSf7Ga
yTJcQ2HE85moXck7SW03FfBhK3/smjEnVL5h3ok084Dax0Mbt9HT71YhiKng7N0x
fkFAUch1+LkmUPBoMq6EML1xTnD6RKpl7ny9HtQEkRe41nqJSCd7k6uMVq62Z1uN
dODy8BMg0Lu6VGfGvw2bAjzMEH/qhDlxY743yVr0n8D+IUaquxgyf4FdvLLe07Y=
=4IK4
-----END PGP SIGNATURE-----

Martin,
You are probably right we should track maint by default at this point.
I
think it’s worth adding a Pybombs environment question about which
branch
to track during initial setup for those that prefer to track master
however.
Tim

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim,

idea:
pybombs install package
gets the default branch as in the recipe,
pybombs install package%awesomefeatures
gets the awesomefeatures branch.

That would allow people to specify they want UHD maint, GNU Radio
v3.7.4, and gqrx master, if they really want to.

Greetings,
Marcus

On 23.07.2014 13:18, Tim O’Shea wrote:

On 07/23/2014 07:14 AM, Activecat wrote:
branch to track first. Also, if you checked out ‘maint’ on

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTz5xzAAoJEBQ6EdjyzlHt2oYIAJYYair2p3bJqiYwIMVhtX21
O5DUUVV06LQpEXUbxs99JBeGtA4KoY1KddVW2OPx26yUhP49xBAYO8dbNHth4ft8
PHNjS2vWroGK/8otLM8kkdzr+2+YmCw9zMKW/q/nl/afxsdUmu8N+gY9hZYsBkv8
jF8A4UPk7b8d4r79WxHmiiYHN6FLnW9glfGXDbigJMXyERzNaKJVPoy/o9Z7o5Q7
MLjsWBOkikn6mlNFjXD2VrHRBOJwQrp6gRLtirDhMqaeKepD1QBZddWYv5I5vYB0
5U/DFTN7j3Ar/BXWYiFIGFeUPqFunIw4YO6m/e9z4Le5VuJ0H36d3OptieuS/dE=
=twiT
-----END PGP SIGNATURE-----

On Wed, Jul 23, 2014 at 7:18 PM, Tim O’Shea [email protected]
wrote:

Martin,
You are probably right we should track maint by default at this point.
I think it’s worth adding a Pybombs environment question about which branch
to track during initial setup for those that prefer to track master
however.
Tim

I agree with you.
It is quite strange that the “build-gnuradio” script installs ‘maint’
branch by default, whereas pybombs installs ‘master’ branch by default.
This is lack of consistency.

One of the problems with allowing this kind of customization is that a
single set of pybombs recipes is generally intended to represent a fixed
set of versions / branches as far as configuration management.
Supporting additional branch combinations is kind of explosive in terms
of new combinations of supported packages/versions. That said, master
is kind of a moving target. The hope was to have a set of recipes that
tracks master everywhere for the most part (for developers that want
this), and then have numbered known good sets of recipes that track for
instance 3.7.3 or 3.7.4 with known good OOT modules at the time (for
more stable OOT development or pure users). However this is a lot of
time/work to set up and constantly test / release so thus far we haven’t
really been doing that half - The versioned releases are to some extent
already covered by binary packages -
That said, we can always throw this feature in with a danger untested
version combination
caveat …

-Tim

On Wed, Jul 23, 2014 at 7:15 PM, Marcus Müller [email protected]
wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As UHD and GNU Radio are widely independent, you can use whatever
combination you want in almost any situation (aside from severe API
breakage).

Thanks.
Just curious, does below statement still apply …?

We provide UHD and GNU Radio binary installers for Ubuntu and Fedora
users.
There are two choices:

  • Unstable: Built off of GNU Radio’s master branch and an
    unstable
    UHD install, which includes bugfixes and new features.
  • Stable: Built off of GNU Radio’s maint branch and a stable
    UHD
    install, which only includes bugfixes since the last major release.

These GNU Radio installers will only work with their corresponding UHD
binary
. If you use an unstable UHD binary with a stable GNU Radio
binary
(or vice versa), you will not be able to use any gr-uhd features.

http://code.ettus.com/redmine/ettus/projects/uhd/wiki/GNURadio_Linux

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ah well, consistency with the slowly aging build-gnuradio was not the
intended purpose of having pyBOMBS. build-gnuradio is the result of an
ongoing effort to bring a stable GNU Radio to a lot of platforms
without having people worry too much about getting all the
dependencies and the build process right.

PyBOMBS had this in mind too, but also was meant to provide a
comfortable framework to get OOTs and dependencies installed in a
flexible manner; thus, using master made a lot of sense, so the latest
and greatest OOTs could run. However, since maint is so close to
master, and PyBOMBS has hit the mass market, switching to maint does
sound very clever.

On 23.07.2014 14:25, Activecat wrote:

script installs ‘maint’ branch by default, whereas pybombs installs
‘master’ branch by default. This is lack of consistency.

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTz60qAAoJEBQ6EdjyzlHtM7oH/jl3o7vD+jWFr74fS7w5yZ9e
QM1VgJgrrzECMKGvn0NeirttLHJtSoi/Mj0+GasPqMj//yBdbH+OswePEMdhjVnw
DVIssZDLrkR2s4fp8GXw+/qeC+xUU2IFOGPs7MMBkfGDiOcw5fQNsdFK4Vhcvm7M
yb1/bKHu5QGpRmys+JdyfhVALbBcGtTDudb5uyJ/07ablGrQWGx31rq41DBVA66O
sNyj6Yscdo6jhrZImQiDUALL2gnwZrmg5e1jlWHCtAaADS8CGnRPpf446OWu37ae
FYC0q3ZzJVj6sXkF2aB3o/O6dccL+jVRIFMJkZgvyJj0iUkGX/ZZPrupFzxSFag=
=W3+3
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Agreed, that’s why I like the idea of GR being maint by default (so
that dependencies might not change that easily [hoping that maint is
always tested with the minimum required versions]) and letting users
who might want to risk the breakage just choose their version to their
liking – obviously, if you take a different version than the recipe
maintainer thought would be right for you, you’re leaving the safe
path, and no one can really help you there if you have funky version
problems.

Greetings,
Marcus

On 23.07.2014 14:36, Tim wrote:

OOT development or pure users). However this is a lot of

Martin, You are probably right we should track maint by

Dear Sirs,
‘maint’ on pybombs, it wouldn’t necessarily check out
branch. I will change the gitbranch of gnuradio.lwr recipe


Discuss-gnuradio mailing list [email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTz65pAAoJEBQ6EdjyzlHtFoYH/1cmvi9j4BBKlV1NeypGtsQv
XukSmNQJ2gqFSrQvBt3xjVB/5BZYTj4VOkj86hSTr2hn0IucaG81JYt1v/FyN5rM
1rRblVUtyaWuGnN2gREuoGT8jn6GsSFmztHlp6LUj2ZxkCbWAO27fzurT35Bd3Fy
koTQxxF5vxxgtMuoL0/KV2M1znqT84OrHB3V8fuKudKjmp4r3QzgaLtOYLRxlm7b
g7DHLZ4us+8hFaXzUb6rgS+BHDJlic47JsinUCYMIX1QVV//qSg89lZM/n5YqG67
ODdzcs7CGA7c1aWXgFVnfJT5kpJ2oA65X4TglC24OEfnyffKyxkJln56mQ+Jsvk=
=ALg0
-----END PGP SIGNATURE-----

On Wed, Jul 23, 2014 at 8:40 PM, Marcus Müller [email protected]
wrote:

comfortable framework to get OOTs and dependencies installed in a
flexible manner; thus, using master made a lot of sense, so the latest
and greatest OOTs could run. However, since maint is so close to
master, and PyBOMBS has hit the mass market, switching to maint does
sound very clever.

Thanks for clarification.
This makes a very good sense.