Bug 2103481
Summary: | Fedora gpicview build against GTK3 vs GTK2? | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Artem S. Tashkinov <aros> |
Component: | gpicview | Assignee: | Christoph Wickert <christoph.wickert> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | christoph.wickert, mtasaka |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gpicview-0.2.5-16.fc37 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-09-12 17:41:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Artem S. Tashkinov
2022-07-03 17:28:54 UTC
*** Bug 2121874 has been marked as a duplicate of this bug. *** Does this package have a maintainer? This bug was posted almost two months ago and no one has replied yet. That's enough to pen a reply, e.g. "I don't care, I like it GTK2 way" or something. I see 5 people being CC'ed - that's not nice that no one gives a damn. Two of them receive salaries from RedHat which kinda looks to me they could be a little bit more responsive, I don't know. Maybe I misunderstand something. GTK3 has been here for over a decade now and RedHat wants to get rid of GTK2, so building against GTK3 looks logical. If someone objects, we could have gpicview-gtk3 and lxdm-gtk3 packages, so that people could choose which dependencies to deal with. I still don't quite understand the radio silence. If you've got a feeling I'm sort of spamming here that's because I want to. I hate seeing my bug reports having zero reaction from the respective maintainers. I understand it's open source but writing an answer whatever it may be takes maybe a few minutes. Are you so busy with your life you don't care so much? If you don't why don't you walk away from maintaining? Or it's also extremely time consuming? I don't want to sound like an a-hole, I'm just genuinely concerned. I wonder if it's worth repeating this verbal diarrhea in the other similar bug report, bug 2121873. I hope 10 emails in regard to this situation will be enough for someone to become bothered and do something. I am going to with GTK2 for this package for now. 1) GTK2 doesn't support Wayland thus this package will require an extra dependency of running under XWayland which also means more resources (CPU, RAM) being spent unnecessarily. 2) GTK2 was deprecated a decade ago. 3) Fedora has been moving towards GTK3 for quite some time, e.g. XFCE has long fully migrated to GTK3. You've not provided any rationale behind "for now". And for how long exactly? If someone assists, porting to GTK3 may be shorter. If not, I cannot tell for now. FEDORA-2022-fc92c024cb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fc92c024cb FEDORA-2022-fc92c024cb has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fc92c024cb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fc92c024cb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-fc92c024cb has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |