about 13 years ago - 6 comments
Release changes Now that package recipes in Launchpad are out of beta, Vineyard will start publishing daily builds instead of the testing releases you’ve seen so far. This means that although there is already a new daily build out, it does not yet include functioning theme support (not in the GUI at least), but don’t…
about 13 years ago - 2 comments
New pre-release out! It’s building in the PPA right now and available for download here: python-wine pre9 and vineyard pre9. Changes are: vineyard-launcher: Supports symlinking a directory to a configuration Relative file-paths work vineyard-indicator: New icons for all themes based on Connor Carney’s new design vineyard-preferences: Program adding is implemented Lot’s of fixes for program…
about 13 years ago - 19 comments
There have been a few requests for a testing PPA, so that has now been created. You can find it here or add it to your sources by running the following commands in a terminal: sudo add-apt-repository ppa:cybolic/vineyard-testing sudo apt-get update and then install Vineyard by running the following command: sudo apt-get install python-wine vineyard
about 13 years ago - 9 comments
After the somewhat disappointing release of the beta (did anyone download it?), I thought I’d tell a bit about the new features. Steam is supported quite nicely. Steam applications and games are listed and can be run just like normal programs as well as uninstalled directly from Vineyard. New funtions have been added to the…
about 13 years ago - 17 comments
After months of hard work I finally feel that Vineyard and python-wine are ready for a beta release. Program adding is not enabled yet, but here are lots of other goodies: indicator support, winetricks integration, pre-installation of support packages when double-clicking an exe, new configuration options, direct ISO/BIN/NRG/IMG/MDF support for drives, improved cli-client, the beginnings…
about 14 years ago - No comments
Yeah, I know; it’s been a while. But I’ve been busy! I promise! Today I got some time to work on a little thing I’ve been meaning to do for quite some time. Let’s see if you can guess it from this screenshot: That’s right, now no matter if you launch a program from within…
about 13 years ago
It’s still broken because of the dependencies:
andrei@andrei-desktop:~$ sudo apt-get install vineyard python-wine
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
vineyard : Depends: python-wine (>= 0.3) but 0.3~pre6~maverick is to be installed or
python-wine (>= 0.3~pre6) but 0.3~pre6~maverick is to be installed
E: Broken packages
andrei@andrei-desktop:~$
about 13 years ago
Same here.
about 13 years ago
It has been fixed in the latest PPA uploads (tested on Maverick). Thanks!
about 13 years ago
You’re welcome! Thanks for reporting it. Debian packages’ pre-release version numbers are a bit funky 😉
about 13 years ago
Sorry for the hijack, but can you tell me if I can add an existing, installed program to vineyard? In my case I have a existing WoW installation (just copied the folder from my windows partition). I don’t seem to be able to do that.
about 13 years ago
thabkost:
You can definitely do that
Create a new configuration (if you want to keep things separated, I recommend it), open it’s drive from the Tools page and either move, copy or symlink your WoW folder to where it would have been on a real Windows system.
Vineyard won’t automatically pick it up in the Programs listing since it searches the registry database and the local menu entries, but you can run WoW directly from the Tools page by finding its executable.
You’ll soon be able to add programs to the Programs listing – don’t worry, but if you don’t mind getting technical, you can run something like this from a terminal to add it right now (notice the slightly funky use of backslashes to indicate where WoW was copied to):
vineyard-cli --use-conf "The Name of the Configuration you just added" --set-registry 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\Wow' 'VineyardName' 'World of Warcraft'
vineyard-cli --use-conf "The Name of the Configuration you just added" --set-registry 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\Wow' 'VineyardCommand' 'C:\Program\ Files\World\ of\ Warcraft\wow.exe'
about 13 years ago
Thanks, I’ll try it at home, and get back to you with the results
about 13 years ago
I am running U 10.10 with wine installed. When I run “vineyard-preferences” from terminal it just sits there with no output.
about 13 years ago
What happens if you kill it (ctrl+c) and start it again? On rare occasions Gtk has issues with the asynchronous nature of Vineyard and this happens – I’m still trying to narrow down the bug.