Bug 1823350 - doxygen-1.8.18 is available
Summary: doxygen-1.8.18 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: doxygen
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-13 12:33 UTC by Upstream Release Monitoring
Modified: 2020-07-15 01:12 UTC (History)
2 users (show)

Fixed In Version: doxygen-1.8.18-1.fc33 doxygen-1.8.18-4.fc32
Clone Of:
Environment:
Last Closed: 2020-07-15 01:12:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2020-04-13 12:33:06 UTC
Latest upstream release: 1.8.18
Current version/release in rawhide: 1.8.17-3.fc33
URL: http://www.doxygen.nl/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/457/

Comment 1 Upstream Release Monitoring 2020-04-13 12:33:11 UTC
The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you.  Please use URLs in your Source declarations if possible.

- doxywizard.desktop

Comment 2 Sandro Mani 2020-05-18 09:28:17 UTC
Due to a ghostscript bug, doxygen 1.8.17 currently generates broken images via ps2epsi (see https://github.com/doxygen/doxygen/issues/7484). This is fixed (workaround-ed) in 1.8.18.

Comment 3 Till Hofmann 2020-05-25 10:17:01 UTC
This update should also fix an issue with wrong warnings about missing return type documentation for functions returning void:
https://github.com/doxygen/doxygen/issues/7411

It would be really helpful if this could be updated soon.

(This currently breaks our CI builds because they check for doxygen warnings)

Comment 4 Till Hofmann 2020-05-25 10:44:35 UTC
PR: https://src.fedoraproject.org/rpms/doxygen/pull-request/5

Comment 5 Than Ngo 2020-05-25 14:44:13 UTC
it's fixed in doxygen-1.8.18-1.fc33

Comment 6 Till Hofmann 2020-05-25 15:37:47 UTC
Great, thanks!

Can you also update the F32 package?

Comment 7 Than Ngo 2020-05-26 07:29:17 UTC
(In reply to Till Hofmann from comment #6)
> Great, thanks!
> 
> Can you also update the F32 package?

there're still 2 issues which i want to fix before i push it into f32 update

Comment 8 Till Hofmann 2020-06-23 13:51:42 UTC
I'd really like to see this updated in F32, even if there are some unfixed issues. Currently, this is blocking our whole team from switching to F32.

Is there any chance you could push this to F32 soon?

Thanks!

Comment 9 Fedora Update System 2020-07-08 13:04:53 UTC
FEDORA-2020-00f0cae5af has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-00f0cae5af

Comment 10 Fedora Update System 2020-07-09 19:58:14 UTC
FEDORA-2020-00f0cae5af has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-00f0cae5af`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-00f0cae5af

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2020-07-15 01:12:15 UTC
FEDORA-2020-00f0cae5af has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.