May 16, 201511 yr Author Hi Squid, I see that the latest update allows editing of the existing container's xml when clicking on the template repo container icon. Well, one issue I'm observing is that when the dev makes a change to the template xml, like add a new variable, the only way it shows up is if the user removes the container and reinstalls? Before, an update would also update the xml and add the variables. I updated my rdp-calibre container and added self updating through an EDGE variable. I also added Height and Width variables for the rdp resolution. None of them show up unless I remove and reinstall. What is the best way for the dev to go about updating the xml? Thanks Fixed in today's update (2015.05.16) Now regardless of the running state of the container, clicking the icon will always add / readd the container using the default values (back to the same behaviour pre 2015.05.09). To edit a container already running, click it's wrench. Also fixed a minor display abberation in tabbed mode introduced by 6.0RC1
May 17, 201511 yr Hi Squid, I see that the latest update allows editing of the existing container's xml when clicking on the template repo container icon. Well, one issue I'm observing is that when the dev makes a change to the template xml, like add a new variable, the only way it shows up is if the user removes the container and reinstalls? Before, an update would also update the xml and add the variables. I updated my rdp-calibre container and added self updating through an EDGE variable. I also added Height and Width variables for the rdp resolution. None of them show up unless I remove and reinstall. What is the best way for the dev to go about updating the xml? Thanks Fixed in today's update (2015.05.16) Now regardless of the running state of the container, clicking the icon will always add / readd the container using the default values (back to the same behaviour pre 2015.05.09). To edit a container already running, click it's wrench. Also fixed a minor display abberation in tabbed mode introduced by 6.0RC1 New update works great, thanks so much
May 29, 201511 yr Author New plugin: Community Applications released here: http://lime-technology.com/forum/index.php?topic=40262.0 You must uninstall Community Repositories before installing the new plugin. ** This plug-in will soon be deprecated, as the new Community Applications plugin puts the emphasis within the lists on the Applications themselves, instead of on the repositories which is really all the end-user cares about. It also supports categories for the applications.
June 14, 201511 yr I updated my rdp-calibre container and added self updating through an EDGE variable. I also added Height and Width variables for the rdp resolution. None of them show up unless I remove and reinstall. Installed this docker today and it installed and started without any problems. It does however give an error if I try and start the server from the Calibre GUI mentioning a 172.x.x.x network (which is not one I use). The server is actually started and I can connect to it from outside the docker, but because the GUI does not realise this it gives no option to stop the running server.
June 14, 201511 yr Author I updated my rdp-calibre container and added self updating through an EDGE variable. I also added Height and Width variables for the rdp resolution. None of them show up unless I remove and reinstall. Installed this docker today and it installed and started without any problems. It does however give an error if I try and start the server from the Calibre GUI mentioning a 172.x.x.x network (which is not one I use). The server is actually started and I can connect to it from outside the docker, but because the GUI does not realise this it gives no option to stop the running server. Might not be a bad idea to post this in Aptalca's thread. Not sure if he monitors this one or not.
August 12, 201510 yr Just updated this and got: Verifying package community.repositories-2015.05.03.txz. expr: syntax error /sbin/installpkg: line 432: [: -lt: unary operator expected /sbin/installpkg: line 434: [: -lt: unary operator expected expr: syntax error /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 469: echo: write error: No space left on device cat: write error: No space left on device Installing package community.repositories-2015.05.03.txz: PACKAGE DESCRIPTION: /sbin/installpkg: line 537: echo: write error: No space left on device /sbin/installpkg: line 538: echo: write error: No space left on device /sbin/installpkg: line 539: echo: write error: No space left on device /sbin/installpkg: line 540: echo: write error: No space left on device /sbin/installpkg: line 545: echo: write error: No space left on device /sbin/installpkg: line 550: echo: write error: No space left on device WARNING: Package has not been created with 'makepkg' /sbin/installpkg: line 559: echo: write error: No space left on device Package community.repositories-2015.05.03.txz installed. Over 7G free on flash Myk This isn't related to the flash but to your tmpfs, and likely it is full. Check wih the command df -h /var/log It is possible to increase the size of the file system on the fly, provided that you have enough RAM memory. Use this command for example to double to size from default 128M to 256M. mount -o remount,size=256m /var/log This keeps happening to me. I upped from 128 to 256 and then to 512. Each time filling up within a week... LT, can you sort this out?
August 12, 201510 yr Just updated this and got: Verifying package community.repositories-2015.05.03.txz. expr: syntax error /sbin/installpkg: line 432: [: -lt: unary operator expected /sbin/installpkg: line 434: [: -lt: unary operator expected expr: syntax error /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 469: echo: write error: No space left on device cat: write error: No space left on device Installing package community.repositories-2015.05.03.txz: PACKAGE DESCRIPTION: /sbin/installpkg: line 537: echo: write error: No space left on device /sbin/installpkg: line 538: echo: write error: No space left on device /sbin/installpkg: line 539: echo: write error: No space left on device /sbin/installpkg: line 540: echo: write error: No space left on device /sbin/installpkg: line 545: echo: write error: No space left on device /sbin/installpkg: line 550: echo: write error: No space left on device WARNING: Package has not been created with 'makepkg' /sbin/installpkg: line 559: echo: write error: No space left on device Package community.repositories-2015.05.03.txz installed. Over 7G free on flash Myk This isn't related to the flash but to your tmpfs, and likely it is full. Check wih the command df -h /var/log It is possible to increase the size of the file system on the fly, provided that you have enough RAM memory. Use this command for example to double to size from default 128M to 256M. mount -o remount,size=256m /var/log This keeps happening to me. I upped from 128 to 256 and then to 512. Each time filling up within a week... LT, can you sort this out? Ironic, might be worth posting in the defect forum or Roadmap forum, suspect it isn't going to get seen here, especially as this plugin is now deprecated..
Archived
This topic is now archived and is closed to further replies.