I have set up a lutris environment on Fedora 34. With using wine which is in Fedora repositories games simply not working, with using wine in official WineHQ repository games run flawlessly. I also tried to build wine from source but it seems same as the wine in Fedora repositories. All three of wine are capable of starting other programs other than games. So what is the difference between official WineHQ packages and Fedora repository packages.
Related
I tried to install podman on SLES 12 straightforwardly, but it looks like the package is missing.
dmitry#sles12:~> sudo zypper in podman
Refreshing service 'Advanced_Systems_Management_Module_x86_64'.
Refreshing service 'Containers_Module_x86_64'.
Refreshing service 'Legacy_Module_x86_64'.
Refreshing service 'Public_Cloud_Module_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Server_x86_64'.
Refreshing service 'Web_and_Scripting_Module_x86_64'.
Loading repository data...
Reading installed packages...
'podman' not found in package names. Trying capabilities.
No provider of 'podman' found.
Resolving package dependencies...
Nothing to do.
The only piece of information I found about running podman on SLES 12 is
SLES 12 is a bad platform to play with current container technology.
It's too old for that and build/based around docker, not podman.
source: https://lists.opensuse.org/opensuse-kubic/2019-10/msg00009.html
As far as I know SLES 12 is still supported.
I checked the latest release notes of SLES 12 SP4 and SLES 12 SP5, these two were released after the first public release of podman, but there is no any mention of podman.
Podman is not officially provided for SLE-11.
Please have a look at the release notes of SLES 15 SP2 ("5.2.1 Support for podman"):
Starting with SUSE Linux Enterprise Server 15 SP2, podman is a supported container engine. However, certain features of podman are currently not supported: [...]
Source: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/#jsc-SLE-9112
You could try an unsupported version of podman by using the package from the community-based Virtualization:containers repository:
https://build.opensuse.org/package/show/Virtualization%3Acontainers/podman
Exemplary procedure:
zypper ar --refresh https://download.opensuse.org/repositories/Virtualization:/containers/SLE_12_SP5/Virtualization:containers.repo
zypper ref
zypper in podman
You'd surely need to accept/trust the repo's signing details during the procedure and eventually you're going to need to install additional dependencies from other repositories as well.
Moving to SLES 15 SP2 might be the easier way to go.
I am attempting to install closed source software from Silego, GreenPAK Designer, on a machine running Fedora 19. The supported installation packages on Silego's Website only target Ubuntu and Debian. I downloaded the .deb package and used Alien to convert to an RPM. So far so good, but a dry run of yum install showed dependency errors, which I solved by installing the necessary packages with yum:
qt5-qbase
qt5-qbase-gui
qt5-qtdeclarative
qt5-qtlocation
qwt
Now, yum installed the above libraries in /usr/lib/ but the GreenPAK RPM defaults to /usr/local/bin as the output dir. I figured I could run
sudo yum localinstall --nodeps --noscripts greenpak-designer-x.x.x.rpm
and get a successful install but I received conflict errors relating to dirs such as '/', '/usr', '/usr/bin' etc. I worked around this issue with:
rpmrebuild -pe --notest-install --replacefiles --noscripts greenpak-designer.x.x.x.rpm
and removing the offending lines in the script. It allowed me to install rpm but the software is broken because of dependency issues (not surprisingly). From the system log:
Jan 4 16:06:49 pelican gnome-session[1729]: /usr/local/greenpak-designer/bin/GP5: error while loading shared libraries: libicui18n.so.52: cannot open shared object file: No such file or directory
The machine has a /usr/lib/libicui18n.so.50
One thing I did not try is rebuilding my shared object cache with ldconfig, which sometimes solves problems with missing .so links when building from source but I don't see how that would apply in this instance (I'm not trying to link object files to libraries, rather simply trying to drop binaries in default install locations, no?)
Of course, I contacted the vendor and begged for an RPM. The contact was helpful but informed me the software folks are on a well deserved break. I thought I'd continue puttering with this in the meantime while I have time.
Any ideas? It seems the solution to this problem would be helpful when trying to install almost any closed source software targeting Debian on a Fedora box.
I am using Fedora 23. I installed Wine 1.75 in it, but i cannot install .NET framework 4. When i try to install framework 4 it shows "already installed a same or higher version". I don't know how to remove the higher version.
Only way to remove dotnet from a wineprefix is manually removing its files. (assuming this does not break something else, which it may)
It is much easier to delete the whole wine folder and start from a new fresh prefix.
Step-by-step and assuming you got wine installed in ~/.wine you should:
remove existing wine prefix:
rm -rf ~/.wine
make a new win32 architecture wine prefix (no need to specify
wineprefix path - it defaults to ~/.wine)
WINEARCH=win32 winecfg
Now, it is much easier to have winetricks installed for such tasks, so make sure you do that before going on.
Afterwards, depending on what dotnet you want, install it like so:
winetricks dotnet452
or for dotnet 3.5sp1:
winetricks dotnet35sp1
or whatever other dotnet version you want. You can see all the dlls
winetricks has scripts on how to install:
winetricks dlls list
Also keep in mind that you don't have to install all previous dotnets one-by-one, the winetricks script will do that for you with usually better results.
Finally remember that if you install dotnet2 and then run winetricks again to install another dotnet on top, it won't work and even if you -f force it.
For further info on the subject, check the wine app db dotnet 40 entry and the arch wiki article on wine
Fedora 23 provides the odb-2.4.0 package.
This git repo
git://pkgs.fedoraproject.org/odb.git
is probably where a fedora-modified copy of the sources exist.
The upstream git repo exists here
git://scm.codesynthesis.com/odb/odb.git
I need the newer upstream version which doesn't crash for some code i have, while odb 2.4 does.
How can I go about building and installing the newer version, and potentially, after more commits in upstream, rebuild and reinstall the newer version?
Do I make a source rpm and install on my machine, and another with an identical fedora?
I am reading
https://fedoraproject.org/wiki/How_to_create_an_RPM_package
but I do not need to deploy this package to fedora, i just would use the RPM mechanism to facilitate installing unreleased versions?
Can I use COPR for that, add my own repo, and install from it instead?
In COPR, can I reuse the SPEC file from the odb2.4.0 rpm and update it to the newer odb?
On my Fedora 19 system, yum update attempts to reinstall a large number packages I have previously removed. This should not happen, as the packages listed are not installed and should not be suggested by yum. How can I make yum work in the expected manner - with updates suggesting only upgrades to preinstalled packages.
Background: I have been trying out new DEs - installing and removing them as I go. Currently, I'm in a DE-less state, booting directly into a tty terminal. My system has no (or a few hidden) xfce or cinnamon packages to "upgrade", yet the package manager is suggesting 300 packages to install, totaling 600M of new install.
Terminal output gist:
https://gist.github.com/Redoubts/29400f0b98cd13120a6a#file-gistfile1-txt
Short answer - It's not possible to disallow installing any packages from the depenency chain. Either you install all of them or drop those who depends on unwanted packages.
In some cases, when the package from a dependency chain is required only during some specific stages of installation (say for execution of a pre- or post-install scripts), it's possible to remove thise package later, after the complete installation. But that's not what you want I suppose.