Conversation
|
@probonopd the test seems to be gone well... should I test also the other 19 or no matters? If not, you can close this PR. PS: I already have a long list of refused PRs here https://github.com/AppImage/appimage.github.io/pulls?q=is%3Apr+author%3Aivan-hc+is%3Aclosed I don't want to lengthen the list with other waste. |
|
Hi @ivan-hc did you talk to the authors to put an officially supported AppImage on https://www.oracle.com/virtualization/technologies/vm/downloads/virtualbox-downloads.html like they have a dmg image for the Mac? |
hi @probonopd , VirtualBox KVM is not VirtualBox https://github.com/cyberus-technology/virtualbox-kvm this is a fork patched to work without the dependency on vboxdrv and it is still in development. The author also contacted me and liked it. Anyway, the point is... this is an Archimage, is it OK for you? |
Interesting, I didn't know that. And I would recommend not to use "Oracle" due to this. But then at least the name should be changed.
Well, the question is more like: is an Archimage OK for the test... apparently it is: |
I was just curious to test the Archimages on your catalog, aware of the validity tests to pass, and I'm glad they passed. But I also know that you use/develop Hello-system, based on FreeBSD if I'm not mistaken... right? Well, the Archimages have a compatibility problem with FreeBSD that I haven't been able to solve yet, despite the 4.3 version that can use PROOT instead of BWRAP in case the system has restrictions in Namespaces (see the latest Ubuntu releases). Did you run my Archimage on your system by any chance? |
|
I've not seen the edit xD
OK, I will do it then... but the AppImge also contains parts with PUEL license, to be honest. I don't think its the case anyway. I developed it for my use case in first, this is my favourite AppImage. VirtualBox KVM does not have a ready package, but only a PKGBUILD for Arch Linux, on AUR. In practice, my AppImage is the only version of VirtualBox that can be installed outside of the distribution repositories or official methods... neither Flatpak nor Snap have one, also because virtualization is difficult for these portable packages. Think that to enable USB support, I had to add an option in the AppImage to add USB support as root user. It does not work out of the box, and it is a known issue in the VirtualBox KVM project. PS: the AppImage is so big also because it has the guest additions iso included. |
the name is provided from the .desktop file, in authomatic. It is a "mod" of VirtualBox after all. Basically VirtualBox is built from source code and then patched. I use ChaoticAUR to complete the process in 5-6 minutes... doing this using AUR takes more than 1 hour. |
|
Interesting!
While I am also developing helloSystem, the project is currently paused, so I don't have a system running FreeBSD around at the moment, sorry. |
- rename the AppImage, see AppImage/appimage.github.io#3452 (comment)
|
In the meantime that the AppImage changes name,,, want to see my workflow? https://github.com/ivan-hc/VirtualBox-appimage/actions/runs/13389024830/job/37392275430 Also, is here some Archimages you are interested in? https://github.com/AppImage/appimage.github.io/pull/3451/files |
|
This is a strange bug of the test script trying to figure out which file was changed. Usually it just takes a re-run. If that doesn't help, I will close this PR and create a fresh one with the same content, then it usually works. |
|
Continues in #3455. |
This is a test related to #3451
I need to see if it has failed because the exceeding of time running, due to the too many apps added.
I'll test this single one this time.