Description of problem: - you don't Require either zenity nor kdialog for the GUI part although you ship the .desktop file that runs --gui (shouldn't one of those be required or at least suggested?) Requires: (zenity or kdialog) oder Suggests: (zenity or kdialog) - you don't touch the self-update facility, shouldn't this be disabled when shipping it via package management ? Version-Release number of selected component (if applicable): - How reproducible: yes Steps to Reproduce: 1. dnf install winetricks 2. winetricks --gui 3. Actual results: 1. no desktop file installed 2. GUI does not work because neither zenity nor kdialog installed as dependency 3. winetricks still warns about any new release of upstream Expected results: 1. desktop file is available 2. GUI works without any additional packages to install manually 3. no warnings about any not packaged version Additional info: Am 16.07.2018 um 17:34 schrieb Florian Hubold.
Maybe new update with recent upstream release. https://github.com/Winetricks/winetricks/releases/tag/20181203
Reassigning to wine maintainers. Are you interested to take responsibility for winetricks as well? I don't have enough time to actively maintain this package and this bug is about usability that could prevent users from trying. Nevertheless, there's also playonlinux available which does a much better job for my personal belongings. I can forward the original mail if anyone is interested in details about initial conversation with the user who reported.
IIUIC, reassigning this bug to wine is the wrong thing to do, this is a problem in winetricks, so it should stay reported against winetricks. I assigned it back. Raphael, if you want to stop maintaining winetricks, you can CC wine maintainers here or email them outside of bugzilla (or ask the community on devel list, which you already did, great).
Kamil, thanks for caring. Isn't there a SIG for wine packaging? We could assgin commit ACL to this individual group.
I don't really know. But you can email the current wine admins (andreas.bierfert at lowlatency.de and mike at cchtml.com) and ask. It would make sense if wine maintainers also maintained or had access to winetricks, if they're willing.
> It would make sense if wine maintainers also maintained or had access to winetricks, if they're willing. Done already. We're still looking for a new responsible main admin.
I have no interest. Sorry. I don't use winetricks and it isn't directly involved with upstream wine.
(In reply to Michael Cronenworth from comment #7) > I have no interest. Sorry. I don't use winetricks and it isn't directly > involved with upstream wine. Please follow our unorphan process. https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package
winetricks-20181203-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea2550435b
winetricks-20181203-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-eece9e9b31
winetricks-20181203-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-eece9e9b31
winetricks-20181203-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea2550435b
Thanks again for the help. Really like those kind of smooth transition process.
winetricks-20181203-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
winetricks-20181203-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.