[belese]

sudo apt-get install fakeroot.
but i imagine package will be soon on repo, so maybe you can wait for it if you don't know how to do.

[CurlyMo]

Let's confirm:

Code:

git clone -b development https://github.com/pilight/pilight.git pilight1
git clone -b development --single-branch https://github.com/pilight/pilight.git pilight2
git clone https://github.com/pilight/pilight.git pilight3
git clone --single-branch https://github.com/pilight/pilight.git pilight4
git clone -b master https://github.com/pilight/pilight.git pilight5
git clone -b master --single-branch https://github.com/pilight/pilight.git pilight6

1: 6091
2: 6091
3: 5772
4: 5385
5: 5772
6: 5365

Conclusion, -b makes --single-branch useless.

[f1vefour]

(7th Mar, 2014 09:34 PM)CurlyMo Wrote:  Let's confirm:

Code:

git clone -b development https://github.com/pilight/pilight.git pilight1
git clone -b development --single-branch https://github.com/pilight/pilight.git pilight2
git clone https://github.com/pilight/pilight.git pilight3
git clone --single-branch https://github.com/pilight/pilight.git pilight4
git clone -b master https://github.com/pilight/pilight.git pilight5
git clone -b master --single-branch https://github.com/pilight/pilight.git pilight6

1: 6091
2: 6091
3: 5772
4: 5385
5: 5772
6: 5365

Conclusion, -b makes --single-branch useless.

You can throw a '-depth 1' in to just get the last commit which saves more downloading.

[freem@n]

(7th Mar, 2014 09:34 PM)CurlyMo Wrote:  Let's confirm:

Code:

git clone -b development https://github.com/pilight/pilight.git pilight1
git clone -b development --single-branch https://github.com/pilight/pilight.git pilight2
git clone https://github.com/pilight/pilight.git pilight3
git clone --single-branch https://github.com/pilight/pilight.git pilight4
git clone -b master https://github.com/pilight/pilight.git pilight5
git clone -b master --single-branch https://github.com/pilight/pilight.git pilight6

1: 6091
2: 6091
3: 5772
4: 5385
5: 5772
6: 5365

Conclusion, -b makes --single-branch useless.

and why is there a difference between 5 and 6? shouldn't it be the same according to your conclusion..?

btw: I guess we'll need to close our offtopic conversation soon ;-)

EDIT: nevermind, looking back at the original post there is already --depth 5 in it. I forgot that --depth implies --single-branch, my fault.

[Smultie]

12:59:49 T:3038233376 NOTICE: Starting XBMC (14.0-ALPHA1 Git:20140307-28f60ed). Platform: ARM Linux 32-bit
12:59:49 T:3038233376 NOTICE: Using Release XBMC x32 build, compiled Mar 7 2014 by GCC 4.7.1 for ARM Linux 32-bit 3.2.21

14.0 Alpha? oO

[freem@n]

(7th Mar, 2014 10:23 PM)Smultie Wrote:  12:59:49 T:3038233376 NOTICE: Starting XBMC (14.0-ALPHA1 Git:20140307-28f60ed). Platform: ARM Linux 32-bit
12:59:49 T:3038233376 NOTICE: Using Release XBMC x32 build, compiled Mar 7 2014 by GCC 4.7.1 for ARM Linux 32-bit 3.2.21

14.0 Alpha? oO

I don't understand the new version number either, but I saw it on their GitHub page so it must be correct. https://github.com/xbmc/xbmc/commit/8929a3db1ccaaa77f911f2319bdc7080ce208567

[Smultie]

(7th Mar, 2014 10:32 PM)freem@n Wrote:  

(7th Mar, 2014 10:23 PM)Smultie Wrote:  12:59:49 T:3038233376 NOTICE: Starting XBMC (14.0-ALPHA1 Git:20140307-28f60ed). Platform: ARM Linux 32-bit
12:59:49 T:3038233376 NOTICE: Using Release XBMC x32 build, compiled Mar 7 2014 by GCC 4.7.1 for ARM Linux 32-bit 3.2.21

14.0 Alpha? oO

I don't understand the new version number either, but I saw it on their GitHub page so it must be correct. https://github.com/xbmc/xbmc/commit/8929a3db1ccaaa77f911f2319bdc7080ce208567

I actually wanted to test 13 Beta 1

Btw, so I'm now on 14Alpha, but when I "apg-get upgrade" I see

┌─────────────────[Config > Updates > Check deb upgrades]────────────────────┐
│ │
│ Press [space] to enable or disable an option │
│ # [ Updates ] [ Version ] │
│ ┌────────────────────────────────────────────────────────────────────────┐ │
│ │[ ] 1 [ xbian-package-xbmc-gotham-nightly ] [ 2.9-10.25 (2.9-10.25) ] │ │
│ └────────────────────────────────────────────────────────────────────────┘ │
│ │
├────────────────────────────────────────────────────────────────────────────┤
│ <Select> <Return> │
└────────────────────────────────────────────────────────────────────────────┘

Should I run this update, or will it put me back on 13Alpha?
Answer: back to 13 alpha

[belese]

I think Irridium will like your Post :-)

[Smultie]

It's small(er) again!

[teekay]

(7th Mar, 2014 10:32 PM)freem@n Wrote:  

(7th Mar, 2014 10:23 PM)Smultie Wrote:  12:59:49 T:3038233376 NOTICE: Starting XBMC (14.0-ALPHA1 Git:20140307-28f60ed). Platform: ARM Linux 32-bit
12:59:49 T:3038233376 NOTICE: Using Release XBMC x32 build, compiled Mar 7 2014 by GCC 4.7.1 for ARM Linux 32-bit 3.2.21

14.0 Alpha? oO

I don't understand the new version number either, but I saw it on their GitHub page so it must be correct. https://github.com/xbmc/xbmc/commit/8929a3db1ccaaa77f911f2319bdc7080ce208567

Gotham got a beta release, and at that point it also got a Gotham branch. Master moves on to 14.0.
So, the Gotham nightly package isn't compiling Gotham currently, it's compiling H? Well, actually it isn't compiling anything, seems the ready compiled binaries are checked into git by Koenkk, and obviously he's checking out the master branch. I wonder if there's a buildroot or something so we could really compile our own XBMC and use the stuff from xbian-package-xbmc repo to package it - that would be cool (and help us to help Koenkk I guess). IMHO it would make more sense to have the packages:
* xbian-package-xbmc-nightly (from master)
* xbian-package-xbmc-gotham-nightly (from Gotham branch)
* xbian-package-xbmc-gotham-beta (for released -beta and -rc version)
Shouldn't be hard to do, we just need to know how the compile is done. It's like "give us fish, or even better teach us how to fish!"

[mk01]

@teekay

there is build root and was failed lately

I informed Koen about this and he corrected.

Anyhow please open issue on git for the actual version. ;-)

[teekay]

Thanks for the info. Now I found the build root via the dev wiki on github.

After adding libxslt-dev, updating the videocore firmware headers and fixing their /usr/include mess (it was copied, not symlinked to /opt/vc/include/*) in /opt/bcm-root , I was able to compile the Gotham branch using the instructions on the dev wiki (replacing master with Gotham branch, of course).

Having an up2date buildroot would be great. Will Koen upload a fixed one to sf.net then?

Edit: post log or it didn't happen

Code:

12:20:51 T:3037589504  NOTICE: Starting XBMC (13.0-BETA3 Git:20140315-4910748). Platform: ARM Linux 32-bit
12:20:51 T:3037589504  NOTICE: Using Release XBMC x32 build, compiled Mar 17 2014 by GCC 4.7.1 for ARM Linux 32-bit 3.2.21

That looks better.

[Jaman42]

Hi,
Not sure if I should ask here or in the RC1 thread, I am trying to get a nightly build of Gotham running on my Pi with Xbian RC1. After additional attempts I finally got Xbian RC1 up and running. But when I install Xbmc nightly using "sudo apt-get install xbian-package-xbmc-gotham-nightly" it won't load XBMC on reboot.

On first reboot after the installation it freezes when configuring the network, then a minute or so after it reboots again. This time it seem to be passing the network configuration and get stuck in a endless loop (with occasional reboots in between it looks like) where it says "Starting XBMC" or something like that.

If I revert back to the FRODO release everything is back working again.

Any advice?

Thanks for reading

*Edit: Can some files from the old version be interfering somehow? Worth to try and remove /usr/local/share/xbmc and install xbian-package-config-xbmc again?

[teekay]

(17th Mar, 2014 08:03 PM)Jaman42 Wrote:  Hi,
Not sure if I should ask here or in the RC1 thread, I am trying to get a nightly build of Gotham running on my Pi with Xbian RC1. After additional attempts I finally got Xbian RC1 up and running. But when I install Xbmc nightly using "sudo apt-get install xbian-package-xbmc-gotham-nightly" it won't load XBMC on reboot.

On first reboot after the installation it freezes when configuring the network, then a minute or so after it reboots again. This time it seem to be passing the network configuration and get stuck in a endless loop (with occasional reboots in between it looks like) where it says "Starting XBMC" or something like that.

If I revert back to the FRODO release everything is back working again.

Any advice?

Thanks for reading

Check /var/log/upstart/xbmc.log - it should say something about a missing library libvorbisenc.so.2
You can fix it with

Code:

apt-get install libvorbisenc2

[Jaman42]

Spot on! Thanks!

I will remember to check the logs next time