Bug 2171455 - caddy: FTBFS in Fedora rawhide/f38
Summary: caddy: FTBFS in Fedora rawhide/f38
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: caddy
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F38FTBFS
TreeView+ depends on / blocked
 
Reported: 2023-02-20 11:45 UTC by Fedora Release Engineering
Modified: 2023-08-27 00:43 UTC (History)
4 users (show)

Fixed In Version: caddy-2.6.4-1.fc38
Clone Of:
Environment:
Last Closed: 2023-08-27 00:43:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fedora Release Engineering 2023-02-20 11:45:28 UTC
caddy failed to build from source in Fedora rawhide/f38

https://koji.fedoraproject.org/koji/taskinfo?taskID=96315245


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
Please fix caddy at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
caddy will be orphaned. Before branching of Fedora 39,
caddy will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Mark E. Fuller 2023-05-21 18:41:53 UTC
I've started taking a look at this and think I can rebuild and update caddy while also unbundling

For reference, the following packages appear to be needed:
No matching package to install: 'golang(github.com/caddyserver/certmagic)'
No matching package to install: 'golang(github.com/quic-go/quic-go)'
No matching package to install: 'golang(github.com/quic-go/quic-go/http3)'
No matching package to install: 'golang(github.com/smallstep/certificates/acme)'
No matching package to install: 'golang(github.com/smallstep/certificates/acme/api)'
No matching package to install: 'golang(github.com/smallstep/certificates/acme/db/nosql)'
No matching package to install: 'golang(github.com/smallstep/certificates/authority)'
No matching package to install: 'golang(github.com/smallstep/certificates/authority/provisioner)'
No matching package to install: 'golang(github.com/smallstep/certificates/db)'
No matching package to install: 'golang(github.com/smallstep/nosql)'
No matching package to install: 'golang(github.com/smallstep/truststore)'
No matching package to install: 'golang(github.com/tailscale/tscert)'
No matching package to install: 'golang(github.com/yuin/goldmark-highlighting/v2)'
No matching package to install: 'golang(go.opentelemetry.io/otel/semconv/v1.17.0)'
No matching package to install: 'golang(go.step.sm/crypto/keyutil)'
No matching package to install: 'golang(go.step.sm/crypto/x509util)'

Comment 2 Carl George 🤠 2023-07-27 04:41:40 UTC
Please do not unbundle the dependencies of this package.  The upstream adds and removes dependencies too often to keep up with in my opinion.  I'm actually preparing a rawhide update to caddy 2.7.0~beta2 in order to resolve bug 2225732.  That pre-release is needed to work with golang 1.21~rc3 that is already in rawhide.  With that update I'm removing all the vendor conditionals to clean up the spec file, because I have no intention of using them in the future.

Once 2.7.0 final is tagged upstream, I can update rawhide and f38 to that version.

Comment 3 Fedora Release Engineering 2023-08-16 07:07:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 4 Carl George 🤠 2023-08-18 03:54:06 UTC
It looks like caddy 2.7 has a few backwards-incompatible changes.

https://github.com/caddyserver/caddy/releases/tag/v2.7.3

The original problem for the F38 FTBFS was that caddy 2.5.2 used quic 0.28.0, which was not compatible with golang 1.20.x.

https://github.com/caddyserver/caddy/blob/v2.5.2/go.mod#L17
https://github.com/quic-go/quic-go/blob/v0.28.0/internal/qtls/go120.go

I can resolve the F38 FTBFS by only updating caddy from 2.5.2 to 2.6.4 (which matches the epel8 branch), so I'm going to go that route.

Comment 5 Fedora Update System 2023-08-18 04:06:52 UTC
FEDORA-2023-74e5545901 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-74e5545901

Comment 6 Fedora Update System 2023-08-19 01:44:03 UTC
FEDORA-2023-74e5545901 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-74e5545901`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-74e5545901

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

Comment 7 Fedora Update System 2023-08-27 00:43:10 UTC
FEDORA-2023-74e5545901 has been pushed to the Fedora 38 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.