backport fix for autoconf-2.70 to varnish-6.0.x #3851
Labels
No labels
a=ActionBeforeRelease
a=Bugwash Today
a=Implement
a=Move To VIP
a=NextVCL
a=OK'ed
a=RunByUPLEX
a=VDD
a=duplicate
a=feedback please
a=freeze
a=help wanted
a=invalid
a=last call
a=more-info-needed
a=need bugwash
b=breaking
b=bug
b=cleanup
b=enhancement
c=H/2
c=build
c=doc
c=packaging
c=varnishadm
c=varnishapi
c=varnishd
c=varnishhist
c=varnishlog
c=varnishncsa
c=varnishstat
c=varnishtest
c=varnishtop
c=vmod
r=6.0
r=7.0
r=7.1
r=7.2
r=7.3
r=7.4
r=7.5
r=8.0
r=trunk
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
vinyl-cache/vinyl-cache#3851
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Debian packages, and thus also Ubuntu, forces* automake/autoconf to be reran before building a package. As Ubuntu 22.04 has autoconf 2.71, varnish-6.0.10 fails the reconfig because of issue #3491
Please backport the fix in commit
cc8c6a8to the 6.0 LTS stable branch. This will also make it possible for Varnish Software to update their 6.0 PackageCloud set to Ubuntu 22.04.Ingvar
*) Yes, I know this may be overridden
This seems fixed in varnish-6.0.11,
7ec2391I also observe that the packagecloud repo now has packages for ubuntu-22.04. Thank you. Closing.