Jump to content


FredFrin

Member Since 11 Oct 2010
Offline Last Active 14 Aug 2021 20:40
-----

Posts I've Made

In Topic: Openpli Quick setup Ubuntu/debian

18 January 2013 - 00:08

@MiLo : I do not have a sources/svn subdir. I tried creating one - also no help.
I thought maybe you meant cvs so I moved that out of sources - no help



~/openpli/trunk/pli-oe$ find sources | grep svn
sources/root_openpli.svn.sourceforge.net_.svnroot.openpli.trunk.cdk.cdk_295_.tar.gz



ssh is unable to connect to cvs.tuxbox.org. This site says it's down.
so I don't understand yr proposed solutions ... I would have expected that the workaround
needed is

- place the missing files (obtained from elsewhere) in sources so the retrieval is no longer attempted,
- or alter the URI from which the the build tries to collect the files to something valid.


... but then I havn't built OpenPli before ...


NOTE: package tuxbox-common-openpli+svn296: started
NOTE: package tuxbox-common-openpli+svn296-r2: task do_fetch: started
NOTE: Fetch cvs://anoncvs@cvs.tuxbox.org/cvs/tuxbox/;module=cdk/root/share/tuxbox;method=ext;tag=dreambox;date=20090305
ssh: connect to host cvs.tuxbox.org port 22: Connection refused
cvs [checkout aborted]: end of file from server (consult above messages if any)
NOTE: Task failed: Fetch failed: cdk/root/share/tuxbox


In Topic: Openpli Quick setup Ubuntu/debian

14 January 2013 - 00:49

@Persian Prince:

Thanks for yr post - but it's not helping me get any further :(

I placed the files you posted in source & created the ".done" touch files, get same issue.

cvs.tuxbox.org site states it has moved, so it looks like nobody can build
unless they have previously downloaded the necessary goodies from here?

Shouldn't the bitbake file be fixed ??? This would get rid of the prob once and for all ...

openembedded/packages/tuxbox/tuxbox-common.bb

This contains:


SRC_URI = "cvs://anoncvs@cvs.tuxbox.org/cvs/tuxbox/;module=cdk/root/share/tuxbox;method=ext;tag=dreambox;date=${SRCDATE} \
        http://dreamboxupdate.com/download/opendreambox/tuxbox-common-r11.tar.gz"
...

SRC_URI += " ${PLISVNURL}/${PLISVNBRANCH}/cdk/cdk/root;module=share;rev=${PLISVNREV};proto=${PLISVNPROTO} \
        ${PLISVNURL}/${PLISVNBRANCH}/cdk/cdk/root;module=etc;rev=${PLISVNREV};proto=${PLISVNPROTO}"

Does anyone have the file to be retrieved by the first URI, or have the correction needed for the bb?
(and will any others from cvs.tuxbox.org be needed)??

In Topic: Openpli Quick setup Ubuntu/debian

8 January 2013 - 00:23

... and then it fails at the next hurdle. Same trick does not work this time ;(
Placing tuxbox-common-r11.tar.gz into sources does not work this time ...

NOTE: package tuxbox-common-openpli+svn295: started
NOTE: package tuxbox-common-openpli+svn295-r2: task do_fetch: started
NOTE: Fetch cvs://anoncvs@cvs.tuxbox.org/cvs/tuxbox/;module=cdk/root/share/tuxbox;method=ext;tag=dreambox;date=20090305UTC
ssh: connect to host cvs.tuxbox.org port 22: Connection refused
cvs [checkout aborted]: end of file from server (consult above messages if any)
NOTE: Task failed: Fetch failed: cdk/root/share/tuxbox
NOTE: package tuxbox-common-openpli+svn295-r2: task do_fetch: failed
ERROR: TaskFailed event exception, aborting
NOTE: package tuxbox-common-openpli+svn295: failed
ERROR: Build of dreambox-image failed

Seems a lot of hacking is needed to build .... is running make_oe_image the wrong thing to do??

In Topic: Openpli Quick setup Ubuntu/debian

7 January 2013 - 23:55

Re Build:

A number of sites providing package sources seem to have 'gone'. So far I've found sources
elsewhere & manually placed them in the source dir.

openembedded/packages/tuxbox/dvbsnoop.bb contains an error causing checkout to fail & build to hang:

Remove the UTC from the following line & it works :

SRCDATE="20081001UTC"

cheers,
ff

In Topic: 3TB Hard Disc in OpenPLi ?

8 October 2012 - 09:31

On my PC I was mounting the disk via a Docking Station via eSATA, which worked.
At the Dreambox end I was using an identical docking station, but via USB.

I tried at the PC via USB & see the same failure - so the cause seems to be
a limitation in the USB functionality of the docking Station. Looking at the
manufacturers site seems to confirm this.