Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 10 of 10
  1. #1
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    900

    Server updates when running with --nomysqueezebox command line

    Appears that nocpan is not returned as a valid list of installers when checking for updates with --nomysqueezebox commandline option
    Code:
    [17-02-06 19:53:06.5697] Slim::Utils::Update::getUpdateInstaller (334) Reading update installer path from /tmp/slimupdate/server.version
    [17-02-06 19:53:06.5703] Slim::Utils::Update::getUpdateInstaller (337) No '/tmp/slimupdate/server.version' available.
    [17-02-06 19:53:06.5707] Slim::Utils::Update::checkVersion (78) Checking version now.
    [17-02-06 19:53:06.5713] Slim::Utils::Update::checkVersion (93) Using URL: http://repos.squeezecommunity.org/7.9.0/servers.xml?version=7.9.0&revision=1484464958&lang=EN&geturl=1&os=nocpan&uuid=c16935f3-34da-490c-bc5f-1298b2f78914&pcount=0
    [17-02-06 19:53:06.8887] Slim::Utils::Update::checkVersionCB (128) Got list of installers:
    {
      deb => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver_7.9.0~1485931015_all.deb",
            version => "7.9.0",
          },
      debamd64 => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver_7.9.0~1485931015_amd64.deb",
            version => "7.9.0",
          },
      debarm => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver_7.9.0~1485931015_arm.deb",
            version => "7.9.0",
          },
      debi386 => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver_7.9.0~1485931015_i386.deb",
            version => "7.9.0",
          },
      default => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/?ver=7.9",
            version => "7.9.0",
          },
      osx => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/LogitechMediaServer-7.9.0-1485931015.pkg",
            version => "7.9.0",
          },
      readynas => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver-7.9.0-1485931015-sparc-readynas.bin",
            version => "7.9.0",
          },
      readynasarm => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver-7.9.0-1485931015-arm-readynas.bin",
            version => "7.9.0",
          },
      readynaspro => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver-7.9.0-1485931015-i386-readynas.bin",
            version => "7.9.0",
          },
      rpm => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver-7.9.0-0.1.1485931015.noarch.rpm",
            version => "7.9.0",
          },
      whs => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/LogitechMediaServer-7.9.0-1485931015-whs.msi",
            version => "7.9.0",
          },
      win => {
            revision => "1485931015",
            url => "http://downloads.slimdevices.com/nightly/7.9/sc/481dece/LogitechMediaServer-7.9.0-1485931015.exe",
            version => "7.9.0",
          },
    }
    [17-02-06 19:53:06.8894] Slim::Utils::Update::checkVersionCB (153) No new Logitech Media Server version available

  2. #2
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,781
    Would something like this be good enough?

    Code:
              'nocpan' => {
                            'url' => 'http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver-7.9.0-1485931015-noCPAN.tgz',
                            'revision' => 1485931015,
                            'version' => '7.9.0'
                          },
    Michael

    http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo

  3. #3
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    900
    I think so. As long as LMS gets the revision and update URL, Update.pm should be happy.

  4. #4
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,781

    Server updates when running with--nomysqueezebox command line

    > I think so. As long as LMS gets the revision and update URL, Update.pm
    > should be happy.


    I'm a little confused: as you are providing your own tcz build, why
    would you use the in-built update checker at all?

    --

    Michael

  5. #5
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    900
    Quote Originally Posted by mherger View Post
    I'm a little confused: as you are providing your own tcz build, why
    would you use the in-built update checker at all?
    Because you led me down the rabbit hole.

    http://forums.slimdevices.com/showth...l=1#post845536

    Anyway, the change you made to the server response took care of the problem.

  6. #6
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,781

    Server updates when running with--nomysqueezebox command line

    > Because you led me down the rabbit hole.

    I still don't see why LMS on pCP should check for noCPAN if you were to
    provide your own packages. We'd have to build tcz packages and include
    them in the update check instead to make this work, wouldn't we?

    FWIW: I'd be willing to look into building those files for you with all
    the others. Those build systems don't do anything else. They're not too
    busy... Are all scripts etc. committed in your repository?

    --

    Michael

  7. #7
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    900
    Quote Originally Posted by mherger View Post
    > Because you led me down the rabbit hole.

    I still don't see why LMS on pCP should check for noCPAN if you were to
    provide your own packages. We'd have to build tcz packages and include
    them in the update check instead to make this work, wouldn't we?

    FWIW: I'd be willing to look into building those files for you with all
    the others. Those build systems don't do anything else. They're not too
    busy... Are all scripts etc. committed in your repository?

    --

    Michael
    I use the noCPAN tarball, as I keep all of the binaries in a separate extension, and it was easier for me to script the re-packing of the tcz from the no cpan tarball, than it was for me to automate building distributing the tcz. (At the time I did this, I wasn't part of the pCP team......and didn't have access to a repo for others to grab nightlies from)

    Starting with the noCpan tarball, I add the files that are contained here https://github.com/paul-1/lms-update-script

    The Update script
    1) Updates itself from github
    2) Grabs the update link the LMS saves via Update.pm. Then Downloads the noCPAN tarball
    3) Downloads the other LMS customizations and init.d files from github
    4) updates all of the permissions
    5) Repacks the extension

    If you were to build the tcz from the LMS build system. Some minor changes to the LMS customizations would be needed. The update script would get much smaller. At this point, the only file likely to ever change was the init.d script. Not sure how we could coordinate this.

  8. #8
    Senior Member sbp's Avatar
    Join Date
    Apr 2010
    Location
    Denmark
    Posts
    1,088
    Paul, you are the expert here as you made the LMS script that allows LMS on pCP - so therefore I might be wrong.

    But I'm thinking it could be a problem that pCP often use a more up-to-date version of Perl than most other distros, and therefore would have problems using a pre-build version of LMS ? I thought that this was the reason for us to use the noCPAN version and build the package?
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://sites.google.com/site/picoreplayer/home

    Please donate if you like the piCorePlayer

  9. #9
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,781

    Server updates when running with--nomysqueezebox command line

    > I use the noCPAN tarball, as I keep all of the binaries in a separate

    Oh, you use the update checker in your build script, not in LMS...

    > The Update script
    > 1) Updates itself from github
    > 2) Grabs the update link the LMS saves via Update.pm. Then Downloads
    > the noCPAN tarball
    > 3) Downloads the other LMS customizations and init.d files from github
    > 4) updates all of the permissions
    > 5) Repacks the extension


    But that update script is run on your end, not the user's? The latter
    would simply download the resulting tcz file?

    > If you were to build the tcz from the LMS build system. Some minor
    > changes to the LMS customizations would be needed. The update script
    > would get much smaller. At this point, the only file likely to ever
    > change was the init.d script. Not sure how we could coordinate this.


    I take it from the update script that you're running it on a Pi (eg.
    checking for OpenSSL)? I might give porting it to our build system a try
    when I find a few spare cycles.

    --

    Michael

  10. #10
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    900
    Quote Originally Posted by mherger View Post
    > I use the noCPAN tarball, as I keep all of the binaries in a separate

    Oh, you use the update checker in your build script, not in LMS...
    They are both in there. It looks for the update URL that LMS update checker downloads. I also have a provision to check directly.

    But that update script is run on your end, not the user's? The latter
    would simply download the resulting tcz file?
    The update script runs on the users pi.

    I take it from the update script that you're running it on a Pi (eg.
    checking for OpenSSL)? I might give porting it to our build system a try
    when I find a few spare cycles.
    The OpenSSL check is because github is https. pCPused to use dropbear for ssh, so we did not have OpenSSL loaded by default.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •