Bug 1885589

Summary: latest update (2.8.6) missing from fedora 33
Product: [Fedora] Fedora Reporter: Fabio Valentini <decathorpe>
Component: python-psycopg2Assignee: Patrik Novotný <panovotn>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: devrim, hhorak, jmlich83, kparal, panovotn, pkajaba, praiskup
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-psycopg2-2.8.6-1.fc33 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-23 22:06:01 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 Fabio Valentini 2020-10-06 12:55:17 UTC 
The 2.8.6 update was successfully built for fedora 32, 33, and rawhide/34, but no bodhi update for this f33 build was submitted:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1612215

This leads to package downgrades when upgrading to fedora 33:

- python-psycopg2-doc is newer in 32 than in 33:
  0:2.8.6-1.fc32 > 0:2.8.5-3.fc33
- python3-psycopg2 is newer in 32 than in 33:
  0:2.8.6-1.fc32 > 0:2.8.5-3.fc33
- python3-psycopg2-debug is newer in 32 than in 33:
  0:2.8.6-1.fc32 > 0:2.8.5-3.fc33
- python3-psycopg2-tests is newer in 32 than in 33:
  0:2.8.6-1.fc32 > 0:2.8.5-3.fc33

Please submit the missing bodhi update for the python-psycopg2-2.8.6-1.fc33 build.
Comment 1 Honza Horak 2020-10-07 11:15:28 UTC 
This would be good to fix before F33 final freeze.
Comment 2 Fabio Valentini 2020-10-07 11:46:54 UTC 
The final freeze is in effect since yesterday (row 20 here):
https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html

If it should be pushed to stable regardless, a freeze exception will be necessary.
Comment 3 Fedora Update System 2020-10-07 16:58:04 UTC 
FEDORA-2020-8b696602ab has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8b696602ab
Comment 4 Honza Horak 2020-10-08 06:21:01 UTC 
(In reply to Fabio Valentini from comment #2)
> The final freeze is in effect since yesterday (row 20 here):
> https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
> 
> If it should be pushed to stable regardless, a freeze exception will be
> necessary.

Damn, the time goes quicker these days and I had some wrong date in my memory. I'm thinking about impact of this issue if the exception would not be approved and don't really see anything concrete. On the other hand, the risk of changing the package now is very low, so I agree we might request it and see if it's gonna be approved. Patrik, can you take a look at this, please?
Comment 5 Fedora Update System 2020-10-08 22:18:53 UTC 
FEDORA-2020-8b696602ab has been pushed to the Fedora 33 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-8b696602ab`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8b696602ab

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Kamil Páral 2020-10-13 08:34:01 UTC 
Can you please justify why this should get a freeze exception? If this is solely about upgrades, a freeze exception is not necessary, because this update will be a part of f33-updates repo on the release day (just make sure it's pending stable).
Comment 7 Patrik Novotný 2020-10-13 09:12:49 UTC 
That's what I was thinking. Yet, I chose to follow this procedure just to be sure. I removed the tracker bug from the 'Blocks' section. Thanks for the clarification.
Comment 8 Fedora Update System 2020-10-23 22:06:01 UTC 
FEDORA-2020-8b696602ab has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.