Bug 2342224

Hi @travier , this is a reminder that the changes testable deadline is set for 4th February. Please ensure your change meets the criteria for this milestone. If you need to retarget to a later release, please do let me know.

https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones

Thanks!
Aoife

Thanks, we'll let you know depending on progress.

Also tracked in https://gitlab.com/fedora/bootc/tracker/-/issues/61

We are reverting the changes in Rawhide & F42 for now until we are ready on all sides.

We will likely push this change to Fedora 43.

Ack, I will make the adjustments to the change to defer it to F43. Thanks Timothée!

Dear change owner, this is a reminder that your change is required to be 100% code complete by August 26, which is the start of beta freeze. Please provide a status update on your change in the Incomplete Changes Report if you are not able to move your change to 'ON_QA' before this date. If you need to defer your change to the next Fedora release, please let me know and I will reassign this bug and the change page. Thank you kindly.

Dear change owner, this is a reminder that your change is required to be 100% code complete by August 26, which is the start of beta freeze. Please provide a status update on your change in the Incomplete Changes Report if you are not able to move your change to 'ON_QA' before this date. If you need to defer your change to the next Fedora release, please let me know and I will reassign this bug and the change page. Thank you kindly.

Things have only just landed in Rawhide so I think we'll keep this for F44.

OK, pushing this change to F44. I'll update the wiki.

I've updated the wiki. I'll let Aoife Moloney update the other parts. Thanks

Hi travier, how goes this change for F44? The testable deadline is today, February 03, 2026, and changes need to be in good shape at this point https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones

Please let me know if you need to defer this to F45, otherwise if you're good to go for the change to be ready to meet the testable requirements, please update the status of the tracker bug to MODIFIED.

Thanks!

I'm re-opening this bz as it has been implemented for F44. See: https://pagure.io/fesco/issue/3563#comment-1008686

This change breaks Postfix.
main.cf: smtp_tls_CAfile = /etc/pki/tls/certs/ca-bundle.crt

Error log:
Apr 30 03:29:53 sol postfix/smtp[25366]: cannot load Certification Authority data, CAfile="/etc/pki/tls/certs/ca-bundle.crt", CApath="/etc/pki/tls/certs": disabling TLS support
Apr 30 03:29:53 sol postfix/smtp[25366]: warning: TLS library problem: error:80000002:system library::No such file or directory:crypto/bio/bss_file.c:67:calling fopen(/etc/pki/tls/certs/ca-bundle.crt, r):
Apr 30 03:29:53 sol postfix/smtp[25366]: warning: TLS library problem: error:10000080:BIO routines::no such file:crypto/bio/bss_file.c:75:
Apr 30 03:29:53 sol postfix/smtp[25366]: warning: TLS library problem: error:05880020:x509 certificate routines::BIO lib:crypto/x509/by_file.c:248:

Sorry, wrong bug id, please delete

(In reply to Dragan from comment #13)
> This change breaks Postfix.
> main.cf: smtp_tls_CAfile = /etc/pki/tls/certs/ca-bundle.crt
> 
> Error log:
> Apr 30 03:29:53 sol postfix/smtp[25366]: cannot load Certification Authority
> data, CAfile="/etc/pki/tls/certs/ca-bundle.crt",
> CApath="/etc/pki/tls/certs": disabling TLS support
> Apr 30 03:29:53 sol postfix/smtp[25366]: warning: TLS library problem:
> error:80000002:system library::No such file or
> directory:crypto/bio/bss_file.c:67:calling
> fopen(/etc/pki/tls/certs/ca-bundle.crt, r):
> Apr 30 03:29:53 sol postfix/smtp[25366]: warning: TLS library problem:
> error:10000080:BIO routines::no such file:crypto/bio/bss_file.c:75:
> Apr 30 03:29:53 sol postfix/smtp[25366]: warning: TLS library problem:
> error:05880020:x509 certificate routines::BIO lib:crypto/x509/by_file.c:248: