NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS VM 6.7.5 - No apps in the catalog
Hi all, Trying to package an app for ReadyNAS OS, I've set up a Virtualbox VM (following the SDK wiki on GitHub) so i can carry out some tests before buying real hardware. VM installation and usa...
We got a fix to allow the installation of your package with the large number of dependancies on the 6.8.1 beta release:
https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-8-1-RC1/m-p/1356177
Thank you for your reply. I managed to get it working by recreating the VM from scratch. I also accessed the apps page before updating to 6.7.5, if that matters.
I have a couple other questions now, if you don't mind.
I finished packaging an app that needs an up to date mono but the readynas repo is only at 4.2. I added the upstream mono repo in my control file using XB-Repo and XB-Repo-Key-Url, but since packages from the readynas repo have higher priority, it doesn't work as intended. Even setting mono-devel >= 5.0.1 for example does not work, it still tries to pull deps from the readynas repo and thus fails. I manually worked around it by setting a priority of 950 in /etc/apt/preferences.d, but it's not the best experience for future users. Would it be possible to extend the control feature with a XB-Repo-Priority field for example ?
Also I'm experiencing a bug where the package installation hangs after a while, mono-devel pulls _a lot_ of dependencies and the fv-app-install process seems to choke on them, I have to manually kill the process for dpkg to finish its work, after which the app appears correctly in the app list and works fine. Have you already experienced this ?
alucryd wrote:
Would it be possible to extend the control feature with a XB-Repo-Priority field for example ?
I like the request, but I think the issue that you are running into might have been something that we have have imposed with our repo configuration with a mono package. There was a dev a little while ago that was requesting to have a mono version on our ReadyNAS repo, so that is where the conflict that you are encountering.
The version number in mono's repo will be newer than debian's repo, so it should resolve itself when we resolve our repo issue. We have kept the package in the ReadyNAS for 6.7.5 just in case there is an existing app that depends on the mono 4.2 on the readynas repo and older. Once you update to the latest 6.8.0 release, we will be correcting this behavior where you can have the debian and mono repo without the readynas repo causing any packaging conflicts.
alucryd wrote:
Also I'm experiencing a bug where the package installation hangs after a while, mono-devel pulls _a lot_ of dependencies and the fv-app-install process seems to choke on them, I have to manually kill the process for dpkg to finish its work, after which the app appears correctly in the app list and works fine. Have you already experienced this ?
Did you happen to have the package so I can take a look at that issue?
There are not too many apps that are too large, and I know the mono-devel dependancies can be a little bit on the larger side.
Great, looking forward to 6.8 then!
You can find debs for both amd64 and armel on my ftp: ftp.alucryd.xyz:9070, anonymous login works. I can also upload them elsewhere if you'd prefer.- That is a good find with the timing with the larger apps/dependencies.
I am working with the team to better optimize this area.
I also verified that we removed the mono in our repos with 6.8.0+, so the mono installation with your package works better from that regards.Awesome, looking forward to hearing from your progress. Also thank you for removing the outdated mono.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
