#8057 Unblock/reactivate the 9.6 stream branch of the postgresql module
Closed: Fixed by mohanboddu. Opened by nphilipp.

  • Describe the issue

    The 9.6 stream branch of the postgresql module is inactive, probably because it's past its EOL date which was set to 2018-12-01 when it was created. The maintainer of the module @praiskup reported this to the Modularity Tracker.

    Two possible remedies come to mind:

    • Manually set the bug_fixes (and security_fixes?) EOL date for the modules/postgresql:9.6 branch to 2021-12-01, corresponding with the upstream EOL date of 2021-11-11.
    • Or, ignore the SL metadata when determining which branch is active (background, #2). This probably involves changes in code/scripts.
  • When do you need this? (YYYY/MM/DD)

    I assume the sooner the better. @praiskup?

  • When is this no longer needed or useful? (YYYY/MM/DD)

    End of 2021 when 9.6 maintenance ceases upstream.

  • If we cannot complete your request, what is the impact?

    The 9.6 stream can't be updated.


Adjust eol of (module)postgresql#9.6 bug_fixes:2018-12-01 to 2021-12-01? [y/N]: y
Set eol to 2021-12-01 on ['(module)postgresql#9.6 bug_fixes:2018-12-01']

When do you need this? (YYYY/MM/DD)
I assume the sooner the better. @praiskup?

Yes, the 9.6 module stream isn't installable in F30 (though it is visible).

Ah, it's fixed now, thank you @ignatenkobrain.

While we are on it, could we do s/rawhide/bug_fixes/ for stream postgresql:10 and postgresql:11 please?

Ah, it's fixed now, thank you @ignatenkobrain.
While we are on it, could we do s/rawhide/bug_fixes/ for stream postgresql:10 and postgresql:11 please?

@praiskup Its fixed.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata