Announce: Squeeze on Arch - developer version

[bobertuk]

Any script experts out there?

I've been trying to use SOA-web update on Cubox-4i over the last couple of days and the script now fails partway through with...

Already up-to-date.
:: Synchronising package databases...
core is up to date
downloading extra.db...
downloading community.db...
alarm is up to date
downloading aur.db...
downloading aur.db...
downloading aur.db...
downloading aur.db...
aur is up to date
downloading soa-repo.db...
downloading soa-repo.db...
downloading soa-repo.db...
downloading soa-repo.db...
downloading soa-repo.db...
:: Starting full system upgrade...
there is nothing to do
==> Making package: logitechmediaserver-7.9-lms 1-1 (Thu 23 Apr 21:35:17 BST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating slimserver git repo...
Fetching origin
-> Found service
-> Found install
==> Validating source files with sha1sums...
slimserver ... Skipped
service ... Passed
install ... Passed
==> Extracting sources...
-> Creating working copy of 7.9 git repo...
fatal: Cannot update paths and switch to branch 'makepkg' at the same time.
Did you intend to checkout 'logitechmediaserver-7.9-lms/src/slimserver/origin/public/7.9' which can not be resolved as commit?
==> ERROR: Failure while creating working copy of 7.9 git repo
Aborting...

Update complete: Thu 23 Apr 21:35:19 BST 2015
}



The output is normal until it gets to where it says 'fatal'. I think the script is /aur/soa-aur/SoA-update-all.sh

It was working ok until there were some module updates which were themselves installed by the update script. Any ideas?

Bob

[brillo]

Just tried Squeeze on Arch on a Wandboard Quad.

Setup could not have been easier.

Sounds great too.

I had forgotten how versatile LMS is.

Thank you for this great contribution.

[Krisbee]

Any script experts out there?

I've been trying to use SOA-web update on Cubox-4i over the last couple of days and the script now fails partway through with...


==> Extracting sources...
-> Creating working copy of 7.9 git repo...
fatal: Cannot update paths and switch to branch 'makepkg' at the same time.
Did you intend to checkout 'logitechmediaserver-7.9-lms/src/slimserver/origin/public/7.9' which can not be resolved as commit?
==> ERROR: Failure while creating working copy of 7.9 git repo
Aborting...

Update complete: Thu 23 Apr 21:35:19 BST 2015
}



The output is normal until it gets to where it says 'fatal'. I think the script is /aur/soa-aur/SoA-update-all.sh

It was working ok until there were some module updates which were themselves installed by the update script. Any ideas?

Bob

You need a git / pkgbuild expert ... Something's gone wonky with the LMS build. It's no comfort, but I have a x86_64 test build of SOA running in virtualbox and the "update" function works OK. When you reach the stage of updating any installed LMS you shoudl see this:

synchronising scripts
Already up-to-date.
:: Synchronising package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
 there is nothing to do
==> Making package: logitechmediaserver-7.9-lms 1-1 (Fri 24 Apr 10:08:58 BST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating slimserver git repo...
Fetching origin
  -> Found service
  -> Found install
==> Validating source files with sha1sums...
    slimserver ... Skipped
    service ... Passed
    install ... Passed
==> Extracting sources...
  -> Creating working copy of 7.9 git repo...
Cloning into 'slimserver'...
done.
Checking out files:  32% (1022/3147)   
Checking out files:  33% (1039/3147)   
Checking out files:  34% (1070/3147)   
Checking out files:  35% (1102/3147)   
Checking out files:  36% (1133/3147)   
Checking out files:  37% (1165/3147)   
Checking out files:  38% (1196/3147)   
Checking out files:  39% (1228/3147)   
Checking out files:  40% (1259/3147)   
Checking out files:  41% (1291/3147)   
Checking out files:  42% (1322/3147)   
Checking out files:  43% (1354/3147)   
Checking out files:  44% (1385/3147)   
Checking out files:  45% (1417/3147)   
Checking out files:  46% (1448/3147)   
Checking out files:  47% (1480/3147)   
Checking out files:  48% (1511/3147)   
Checking out files:  48% (1517/3147)   
Checking out files:  49% (1543/3147)   
Checking out files:  50% (1574/3147)   
Checking out files:  51% (1605/3147)   
Checking out files:  52% (1637/3147)   
Checking out files:  53% (1668/3147)   
Checking out files:  54% (1700/3147)   
Checking out files:  55% (1731/3147)   
Checking out files:  56% (1763/3147)   
Checking out files:  57% (1794/3147)   
Checking out files:  58% (1826/3147)   
Checking out files:  59% (1857/3147)   
Checking out files:  60% (1889/3147)   
Checking out files:  61% (1920/3147)   
Checking out files:  62% (1952/3147)   
Checking out files:  63% (1983/3147)   
Checking out files:  64% (2015/3147)   
Checking out files:  65% (2046/3147)   
Checking out files:  66% (2078/3147)   
Checking out files:  67% (2109/3147)   
Checking out files:  68% (2140/3147)   
Checking out files:  69% (2172/3147)   
Checking out files:  70% (2203/3147)   
Checking out files:  71% (2235/3147)   
Checking out files:  72% (2266/3147)   
Checking out files:  73% (2298/3147)   
Checking out files:  74% (2329/3147)   
Checking out files:  75% (2361/3147)   
Checking out files:  76% (2392/3147)   
Checking out files:  77% (2424/3147)   
Checking out files:  78% (2455/3147)   
Checking out files:  79% (2487/3147)   
Checking out files:  80% (2518/3147)   
Checking out files:  81% (2550/3147)   
Checking out files:  82% (2581/3147)   
Checking out files:  83% (2613/3147)   
Checking out files:  84% (2644/3147)   
Checking out files:  85% (2675/3147)   
Checking out files:  86% (2707/3147)   
Checking out files:  87% (2738/3147)   
Checking out files:  88% (2770/3147)   
Checking out files:  89% (2801/3147)   
Checking out files:  90% (2833/3147)   
Checking out files:  91% (2864/3147)   
Checking out files:  92% (2896/3147)   
Checking out files:  93% (2927/3147)   
Checking out files:  94% (2959/3147)   
Checking out files:  95% (2990/3147)   
Checking out files:  96% (3022/3147)   
Checking out files:  97% (3053/3147)   
Checking out files:  98% (3085/3147)   
Checking out files:  99% (3116/3147)   
Checking out files: 100% (3147/3147)   
Checking out files: 100% (3147/3147), done.
Switched to a new branch 'makepkg'
==> Starting pkgver()...
==> Updated version: logitechmediaserver-7.9-lms 7.9r19707.a6dacd2-1
==> WARNING: A package has already been built, installing existing package...
==> Installing package logitechmediaserver-7.9-lms with pacman -U...
warning: logitechmediaserver-7.9-lms-7.9r19707.a6dacd2-1 is up to date -- skipping
loading packages...
 there is nothing to do
==> Cleaning up...

Update complete: Fri 24 Apr 10:09:02 BST 2015

If you look at the directory "/aur/soa-aur/logitechmediaserver-7.9-lms/slimserver" - you should see this:

[root@archvm slimserver]# ls -l
total 64
drwxr-xr-x 2 aur aur  4096 Apr 14 11:54 branches
-rw-r--r-- 1 aur aur   173 Apr 14 11:54 config
-rw-r--r-- 1 aur aur    73 Apr 14 11:54 description
-rw-r--r-- 1 aur aur 19158 Apr 24 10:08 FETCH_HEAD
-rw-r--r-- 1 aur aur    27 Apr 14 12:27 HEAD
drwxr-xr-x 2 aur aur  4096 Apr 14 11:54 hooks
drwxr-xr-x 2 aur aur  4096 Apr 14 11:54 info
drwxr-xr-x 4 aur aur  4096 Apr 14 11:54 objects
-rw-r--r-- 1 aur aur 10401 Apr 14 12:27 packed-refs
drwxr-xr-x 4 aur aur  4096 Apr 14 11:54 refs

You can see how the FETCH_HEAD file is updated when the "Cloning into 'slimserver'" works correctly. What do you see in "/aur/soa-aur/logitechmediaserver-7.9-lms" ?

[surfek]

Otherwise, it's possilby a re-install. But in future if you have a skin selection problem in "jivelite" you don't have to re-install jivelite, just delete the jivelite settings ( a hidden directory ) and reboot

Note the dot

Hi Krisbee - great thanks. Tried to reinstall, but now I get "SSL routines:SSL3_GET_RECORD:decryption failed or bad record" error:

:: Retrieving packages ...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
error: failed retrieving file 'jivelite-r76.de07c79-1-armv7h.pkg.tar.xz' from github.com : SSL read: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac, errno 0
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.

Tried new SoA instal on my wand dual, but get the same when try to isntall jivelite...

by the way - what platform are you guys using for SoA?
Maybe I shall switch from wand dual to something else, which is more common used/less problems?


Best regards,


Michal

[bobertuk]

You need a git / pkgbuild expert ... Something's gone wonky with the LMS build. It's no comfort, but I have a x86_64 test build of SOA running in virtualbox and the "update" function works OK. When you reach the stage of updating any installed LMS you shoudl see this:

synchronising scripts
Already up-to-date.
:: Synchronising package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
 there is nothing to do
==> Making package: logitechmediaserver-7.9-lms 1-1 (Fri 24 Apr 10:08:58 BST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating slimserver git repo...
Fetching origin
  -> Found service
  -> Found install
==> Validating source files with sha1sums...
    slimserver ... Skipped
    service ... Passed
    install ... Passed
==> Extracting sources...
  -> Creating working copy of 7.9 git repo...
Cloning into 'slimserver'...
done.
Checking out files:  32% (1022/3147)   
Checking out files:  33% (1039/3147)   
Checking out files:  34% (1070/3147)   
Checking out files:  35% (1102/3147)   
Checking out files:  36% (1133/3147)   
Checking out files:  37% (1165/3147)   
Checking out files:  38% (1196/3147)   
Checking out files:  39% (1228/3147)   
Checking out files:  40% (1259/3147)   
Checking out files:  41% (1291/3147)   
Checking out files:  42% (1322/3147)   
Checking out files:  43% (1354/3147)   
Checking out files:  44% (1385/3147)   
Checking out files:  45% (1417/3147)   
Checking out files:  46% (1448/3147)   
Checking out files:  47% (1480/3147)   
Checking out files:  48% (1511/3147)   
Checking out files:  48% (1517/3147)   
Checking out files:  49% (1543/3147)   
Checking out files:  50% (1574/3147)   
Checking out files:  51% (1605/3147)   
Checking out files:  52% (1637/3147)   
Checking out files:  53% (1668/3147)   
Checking out files:  54% (1700/3147)   
Checking out files:  55% (1731/3147)   
Checking out files:  56% (1763/3147)   
Checking out files:  57% (1794/3147)   
Checking out files:  58% (1826/3147)   
Checking out files:  59% (1857/3147)   
Checking out files:  60% (1889/3147)   
Checking out files:  61% (1920/3147)   
Checking out files:  62% (1952/3147)   
Checking out files:  63% (1983/3147)   
Checking out files:  64% (2015/3147)   
Checking out files:  65% (2046/3147)   
Checking out files:  66% (2078/3147)   
Checking out files:  67% (2109/3147)   
Checking out files:  68% (2140/3147)   
Checking out files:  69% (2172/3147)   
Checking out files:  70% (2203/3147)   
Checking out files:  71% (2235/3147)   
Checking out files:  72% (2266/3147)   
Checking out files:  73% (2298/3147)   
Checking out files:  74% (2329/3147)   
Checking out files:  75% (2361/3147)   
Checking out files:  76% (2392/3147)   
Checking out files:  77% (2424/3147)   
Checking out files:  78% (2455/3147)   
Checking out files:  79% (2487/3147)   
Checking out files:  80% (2518/3147)   
Checking out files:  81% (2550/3147)   
Checking out files:  82% (2581/3147)   
Checking out files:  83% (2613/3147)   
Checking out files:  84% (2644/3147)   
Checking out files:  85% (2675/3147)   
Checking out files:  86% (2707/3147)   
Checking out files:  87% (2738/3147)   
Checking out files:  88% (2770/3147)   
Checking out files:  89% (2801/3147)   
Checking out files:  90% (2833/3147)   
Checking out files:  91% (2864/3147)   
Checking out files:  92% (2896/3147)   
Checking out files:  93% (2927/3147)   
Checking out files:  94% (2959/3147)   
Checking out files:  95% (2990/3147)   
Checking out files:  96% (3022/3147)   
Checking out files:  97% (3053/3147)   
Checking out files:  98% (3085/3147)   
Checking out files:  99% (3116/3147)   
Checking out files: 100% (3147/3147)   
Checking out files: 100% (3147/3147), done.
Switched to a new branch 'makepkg'
==> Starting pkgver()...
==> Updated version: logitechmediaserver-7.9-lms 7.9r19707.a6dacd2-1
==> WARNING: A package has already been built, installing existing package...
==> Installing package logitechmediaserver-7.9-lms with pacman -U...
warning: logitechmediaserver-7.9-lms-7.9r19707.a6dacd2-1 is up to date -- skipping
loading packages...
 there is nothing to do
==> Cleaning up...

Update complete: Fri 24 Apr 10:09:02 BST 2015

If you look at the directory "/aur/soa-aur/logitechmediaserver-7.9-lms/slimserver" - you should see this:

[root@archvm slimserver]# ls -l
total 64
drwxr-xr-x 2 aur aur  4096 Apr 14 11:54 branches
-rw-r--r-- 1 aur aur   173 Apr 14 11:54 config
-rw-r--r-- 1 aur aur    73 Apr 14 11:54 description
-rw-r--r-- 1 aur aur 19158 Apr 24 10:08 FETCH_HEAD
-rw-r--r-- 1 aur aur    27 Apr 14 12:27 HEAD
drwxr-xr-x 2 aur aur  4096 Apr 14 11:54 hooks
drwxr-xr-x 2 aur aur  4096 Apr 14 11:54 info
drwxr-xr-x 4 aur aur  4096 Apr 14 11:54 objects
-rw-r--r-- 1 aur aur 10401 Apr 14 12:27 packed-refs
drwxr-xr-x 4 aur aur  4096 Apr 14 11:54 refs

You can see how the FETCH_HEAD file is updated when the "Cloning into 'slimserver'" works correctly. What do you see in "/aur/soa-aur/logitechmediaserver-7.9-lms" ?

Thanks for the reply.

I tried something I've not done before...

SOA-web update 'full clean'

And it solved the problem. Updates now work - I don't know what 'full clean' actually does but it's obviously something useful.

[Krisbee]

Thanks for the reply.

I tried something I've not done before...

SOA-web update 'full clean'

And it solved the problem. Updates now work - I don't know what 'full clean' actually does but it's obviously something useful.

Bob,

Glad you're back to the music. The "full clean" executes a git command - "git clean -f". I don't know much about git, so I suppose it unblock your git problem. One to keep in mind.

[Krisbee]

Hi Krisbee - great thanks. Tried to reinstall, but now I get "SSL routines:SSL3_GET_RECORD:decryption failed or bad record" error:

:: Retrieving packages ...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
downloading jivelite-r76.de07c79-1-armv7h.pkg.tar.xz...
error: failed retrieving file 'jivelite-r76.de07c79-1-armv7h.pkg.tar.xz' from github.com : SSL read: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac, errno 0
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.

Tried new SoA instal on my wand dual, but get the same when try to isntall jivelite...

by the way - what platform are you guys using for SoA?
Maybe I shall switch from wand dual to something else, which is more common used/less problems?


Best regards,


Michal

Flacky internet connection? Are you using a wired or a wireless connection? Can you connect to your Wandboard via SHH and check this?

I've just installled jivelite on my RPi and everything is OK.

If you go here, https://github.com/SqueezeOnArch/soa...v7h.pkg.tar.xz on another machine and click on RAW, you can see the package is downloading OK.

I wouldn't abandon your Wandboard until you are certain that the ethernet, or wireless is failing to function.

If you are convinced the Wandboard internet connection is OK, but you still get this problem when trying to install via the webui, you could just try to install from the command line. Connect to the wandbaord via SSH as root and install with:

pacman -S jivelite jivelite-autologin

[steve-g]

I have SoA running LMS on a Pi model B+ and have a USB HD attached via a powered hub and am trying to get Samba to work.

I have changed the mount point to /share_rw rather than /mnt/disk1 that I had initially (after reading through this thread) and turned on Samba server in the WEB UI.

The Web UI reports it as being shared:

/share_rw
/dev/sda1 (ntfs-3g) active
defaults,nofail
shared by Samba Server (writable)

I've set the Samba workgroup to be the same as the PC's workgroup but can't get any of my PCs (desktop and laptop) to see the Samba share (The PCs run Windows 7 64bit if that makes any difference)

The Samba server seems to be running on the Pi so I'm at a bit of a loss as to how to diagnose what the problem is so any help from you Linux / network gurus would be appreciated

[Man in a van]

I have SoA running LMS on a Pi model B+ and have a USB HD attached via a powered hub and am trying to get Samba to work.

I have changed the mount point to /share_rw rather than /mnt/disk1 that I had initially (after reading through this thread) and turned on Samba server in the WEB UI.

The Web UI reports it as being shared:

/share_rw
/dev/sda1 (ntfs-3g) active
defaults,nofail
shared by Samba Server (writable)

I've set the Samba workgroup to be the same as the PC's workgroup but can't get any of my PCs (desktop and laptop) to see the Samba share (The PCs run Windows 7 64bit if that makes any difference)

The Samba server seems to be running on the Pi so I'm at a bit of a loss as to how to diagnose what the problem is so any help from you Linux / network gurus would be appreciated

Steve, I can't strictly help you with the Samba routine (see what I did there) but can't help thinking you are trying to lead a horse to the wrong waterhole.

I have SOA on a Cubox and until the last weekend was running my music files on an attached usb drive (I only had a few numpty attempts at setting up before getting the connection).

I have now connected the LMS to my music folder on a Qnap nas, still using mnt/disk 1 and everything seems to work fine.

I am guessing that as the usb drive is connected to the pi, it is hidden from the rest of the network and might have to be attached to either a PC or router (and maybe mapped in Windows). In fact if you do the latter it should show up as a drive in the LMS settings web gui (I think)

atb

Ronnie

[Krisbee]

I have SoA running LMS on a Pi model B+ and have a USB HD attached via a powered hub and am trying to get Samba to work.

I have changed the mount point to /share_rw rather than /mnt/disk1 that I had initially (after reading through this thread) and turned on Samba server in the WEB UI.

The Web UI reports it as being shared:

/share_rw
/dev/sda1 (ntfs-3g) active
defaults,nofail
shared by Samba Server (writable)

I've set the Samba workgroup to be the same as the PC's workgroup but can't get any of my PCs (desktop and laptop) to see the Samba share (The PCs run Windows 7 64bit if that makes any difference)

The Samba server seems to be running on the Pi so I'm at a bit of a loss as to how to diagnose what the problem is so any help from you Linux / network gurus would be appreciated

First check in Windows using the cmd prompt. If ip address of your Rpi was 192.168.1.50 for example. At Windows cmd prompt , type "net view \\192.168.1.50" Samba shares visable to Windows should be listed. If nothing is listed , connect to rpi via SSH as root and post contents of smb.conf file here. ( or stick it on pastebin and post ref it's a large file)