Bug 2075792

Summary: gerbv project moved, new versions released
Product: [Fedora] Fedora Reporter: Gerd v. Egidy <gerd>
Component: gerbvAssignee: Alain V. <alain.vigne.14>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: alain.vigne.14
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gerbv-2.9.8-1.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-19 00:47:26 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:
Attachments:
Description Flags
patch to spec file none

Description Gerd v. Egidy 2022-04-15 11:16:29 UTC 
Description of problem:
gerbv was hosted on sourceforge for years, but development stalled for some time. This has changed at the end of 2021, the project now moved to github and has released some updated versions since then.

The announcement of the move on Sourceforge can be found here:
https://sourceforge.net/p/gerbv/news/

The new page is at: https://github.com/gerbv/gerbv

Please package the new version 2.8.2 (at the time of writing) for Fedora.

The new versions also addressed some security issues related to parsing malicious gerber files.
Comment 1 Alain V. 2022-04-16 09:21:30 UTC 
I am aware of this change.
But new repo did not configure properly the tar.gz and thus, packaging of v2.8.2 is not possible with current status
Please see and solve https://github.com/gerbv/gerbv/issues/86

Are you one of the new upstream maintainer ?
Comment 2 Gerd v. Egidy 2022-04-16 11:38:42 UTC 
Created attachment 1872927 [details]
patch to spec file
Comment 3 Gerd v. Egidy 2022-04-16 11:40:23 UTC 
I wasn't sure if you were aware of the new URL an releases.

I'm not one of the new maintainers, just a regular user.

I have also seen that they botched the released file. But I was able to build a RPM with just minimal changes, see my patch above.

Maybe you can use that to release 2.8.2 for Fedora.
Comment 4 Alain V. 2022-04-18 12:45:22 UTC 
Thanks a lot: your file helped me to "patch" the config file and be able to handle their GitHub project.
I have submitted new builds for Rawhide and F36.
Have a look (when available ?) and feel free to contact me again, and/or close this ticket.

Regards, 
Alain
Comment 5 Gerd v. Egidy 2022-04-18 14:11:01 UTC 
I tested your RPM and it works well. Thank you.

I suggest to add the README.md file as it contains current information for the user how to contact the authors and a link to the github-project page.
The information in the README (non-markdown) file still contains the old sourceforge and geda-URLs, so it is outdated. So either add both or even
remove the non-markdown version.
Comment 6 Ben Cotton 2022-08-09 13:42:30 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.
Comment 7 Fedora Update System 2023-08-10 02:03:26 UTC 
FEDORA-2023-5f5bea627b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5f5bea627b
Comment 8 Fedora Update System 2023-08-11 02:26:17 UTC 
FEDORA-2023-5f5bea627b 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-2023-5f5bea627b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5f5bea627b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2023-08-19 00:47:26 UTC 
FEDORA-2023-5f5bea627b has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.