On Tue, Jan 26, 2010 at 16:41, Johnathan Corgan
wrote:
> On Tue, Jan 26, 2010 at 05:38, Johnathan Corgan
> wrote:
>
>> However, it would be possible (as you mentioned) for Bdale to
>> cherry-pick the commits needed to implement the clock rate
>> configuration, and release the patched 3.2.2 into s
On Tue, Jan 26, 2010 at 05:38, Johnathan Corgan
wrote:
> However, it would be possible (as you mentioned) for Bdale to
> cherry-pick the commits needed to implement the clock rate
> configuration, and release the patched 3.2.2 into squeeze with this
> very minor change. I'm not sure if he's read
On Tue, Jan 26, 2010 at 04:39, Alexander Chemeris
wrote:
> Speaking for the whole OpenBTS community - is it possible to release
> 3.2.3 with my patches, enabling runtime FPGA clock frequency setting?
> They're accepted into mainline, but it will take too long to get into next
> stable GnuRadio re
Hi Johnathan,
On Mon, Jan 25, 2010 at 19:57, Johnathan Corgan
wrote:
> On Sat, Jan 23, 2010 at 06:03, Alexander Chemeris
> wrote:
>
>> 1) What is the reason you don't follow usual Debian/Ubuntu layout
>> where you use distribution versions under dists/ instead of
>> package versions? Then it's p
On Sat, Jan 23, 2010 at 06:03, Alexander Chemeris
wrote:
> 1) What is the reason you don't follow usual Debian/Ubuntu layout
> where you use distribution versions under dists/ instead of
> package versions? Then it's possible to build for multiple distributions.
It was mostly expedient at the ti
Hi Johnathan,
Three questions:
1) What is the reason you don't follow usual Debian/Ubuntu layout
where you use distribution versions under dists/ instead of
package versions? Then it's possible to build for multiple distributions.
2) Also, why don't you use Launchpad for hosting? It will build
au
El 20/01/2010 0:55, Johnathan Corgan escribió:
> On Tue, Jan 19, 2010 at 15:31, Alexandru Csete wrote:
>
>> In the Ubuntu personal package archives it is common practice to
>> append "+distribution-name" after the package version,
>> see for example https://launchpad.net/~gpredict-team/+archive/p
On Tue, Jan 19, 2010 at 15:31, Alexandru Csete wrote:
> In the Ubuntu personal package archives it is common practice to
> append "+distribution-name" after the package version,
> see for example https://launchpad.net/~gpredict-team/+archive/ppa/+packages
> I'm not sure if that would work if the
On Tue, Jan 19, 2010 at 15:39, Arturo Rinaldi wrote:
> i've just got the idea that maybe you can publish the patch (the *.orig.tar,
> the *.dsc, the *.diff.gz) in the folder
>
> http://gnuradio.org/ubuntu/dists/unstable/main/source/
>
> as you did for release 472 and 473 so we can eventually buil
Il 19/01/2010 20:06, Johnathan Corgan ha scritto:
2010/1/19 Pedro Lobo:
I've just tried to install the gnuradio debian packages in Ubuntu 9.10
(Karmic), as per the instructions in
http://gnuradio.org/redmine/wiki/gnuradio/DebianPackages, and they don't
work. The problem is that the packages
2010/1/19 Johnathan Corgan :
> Right now I am testing the deb file creation process with 3.3git on
> Karmic (9.10), using Boost 1.40, and these will get posted on
> gnuradio.org in the unstable repository. Depending on time (and
> feedback), I will also build binary packages for 3.3git based on Bo
2010/1/19 Pedro Lobo :
> I've just tried to install the gnuradio debian packages in Ubuntu 9.10
> (Karmic), as per the instructions in
> http://gnuradio.org/redmine/wiki/gnuradio/DebianPackages, and they don't
> work. The problem is that the packages depend on boost version = 1.37.0
> (as opposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, all.
I've just tried to install the gnuradio debian packages in Ubuntu 9.10
(Karmic), as per the instructions in
http://gnuradio.org/redmine/wiki/gnuradio/DebianPackages, and they don't
work. The problem is that the packages depend on boost ver
13 matches
Mail list logo
