Bug 24702 - Release of gawk 5.0.0 was on 12th April
Summary: Release of gawk 5.0.0 was on 12th April
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: Mageia 8
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-22 15:04 CEST by Artem Kurashov
Modified: 2019-11-28 16:30 CET (History)
2 users (show)

See Also:
Source RPM: gawk
CVE:
Status comment: Has some backward-incompatible changes and needs to wait till after Mageia 7 is released


Attachments

Description Artem Kurashov 2019-04-22 15:04:13 CEST
Release of gawk 5.0.0 was on 12th April, but in the Cauldron still gawk 4.2.1.
Comment 1 David Walser 2019-04-22 16:08:46 CEST
Yes, we saw.  It has some backward-incompatible changes, and we're just about to freeze for Mageia 7, so we'll update gawk after Cauldron re-opens for Mageia 8.
Comment 2 Marja Van Waes 2019-04-22 16:56:20 CEST
(In reply to David Walser from comment #1)
> Yes, we saw.  It has some backward-incompatible changes, and we're just
> about to freeze for Mageia 7, so we'll update gawk after Cauldron re-opens
> for Mageia 8.

I hope our gawk maintainer doesn't mind my already assigning to him.

@ Shlomi

If that irritates you, then please assign back to BugSquad and I'll try to remember to reassign to you when Mageia 8 cauldron opens :-)

Target Milestone: --- => Mageia 8
Component: New RPM package request => RPM Packages
Status comment: (none) => Has some backward-incompatible changes and needs to wait till after Mageia 7 is released
Source RPM: (none) => gawk
Assignee: bugsquad => shlomif
CC: (none) => marja11

Comment 3 Lewis Smith 2019-11-28 16:05:21 CET
Re-assigning globally due to change to no specific maintainer.

Assignee: shlomif => pkg-bugs

Comment 4 David Walser 2019-11-28 16:30:06 CET
Fixed by Shlomi on July 12.  5.0.1 is in Cauldron.

CC: (none) => shlomif
Resolution: (none) => FIXED
Status: NEW => RESOLVED


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