Bug 1955920

Summary: Build error with fedora34 docker image at travis (CI)
Product: [Fedora] Fedora Container Images Reporter: Wolfgang Ulbrich <fedora>
Component: dockerAssignee: Yu Qi Zhang <jzehrarnyg>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: gscrivan, jzehrarnyg, smilner
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-03 15:03:34 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 Wolfgang Ulbrich 2021-05-01 13:42:38 UTC 
Description of problem:

MATE desktop use fedora:latest docker tag for testing our github repos with Travis CI.
Since fedora:latest is fedora 34 builds are failing at Travis CI.
See https://travis-ci.org/github/mate-desktop/mate-panel/jobs/769073247#L591
```
+ ./autogen.sh
/usr/bin/mate-autogen
checking for autoreconf >= 2.53...
  testing autoreconf... found 2.69
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 1.7.3
checking for gtk-doc >= 1.0...
  testing gtkdocize... found 1.33.1
checking for mate-common >= 1.1.0...
  testing mate-doc-common... found 1.24.2
Checking for required M4 macros...
Checking for forbidden M4 macros...
skipping . -- directory is read only
Skipping configure process.
+ scan-build -enable-checker deadcode.DeadStores -enable-checker alpha.deadcode.UnreachableCode -enable-checker alpha.core.CastSize -enable-checker alpha.core.CastToStruct -enable-checker alpha.core.IdenticalExpr -enable-checker alpha.core.SizeofPtr -enable-checker alpha.security.ArrayBoundV2 -enable-checker alpha.security.MallocOverflow -enable-checker alpha.security.ReturnPtrRange -enable-checker alpha.unix.SimpleStream -enable-checker alpha.unix.cstring.BufferOverlap -enable-checker alpha.unix.cstring.NotNullTerminated -enable-checker alpha.unix.cstring.OutOfBounds -enable-checker alpha.core.FixedAddr -enable-checker security.insecureAPI.strcpy ./configure --enable-compile-warnings=maximum
scan-build: Using '/usr/bin/clang-12' for static analysis
Can't exec "./configure": No such file or directory at /usr/bin/scan-build line 1168.
```

Same build with using f33 docker image works fine.
https://travis-ci.org/github/mate-desktop/mate-panel/builds/769122622#L555
```
+ ./autogen.sh
/usr/bin/mate-autogen
checking for autoreconf >= 2.53...
  testing autoreconf... found 2.69
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 1.7.3
checking for gtk-doc >= 1.0...
  testing gtkdocize... found 1.33.1
checking for mate-common >= 1.1.0...
  testing mate-doc-common... found 1.24.2
Checking for required M4 macros...
Checking for forbidden M4 macros...
Processing ./configure.ac
Running gtkdocize...
Running mate-doc-common...
Running autoreconf...
autoreconf: Entering directory `.'
autoreconf: running: autopoint --force
<cut>
```
For some reasons the directory is read only with f34 docker image and configure failed for that reason.
Or something is changed with using 'autotools' for build packages for f34.
But i didn't notice any different when building MATE desktop packages (rpms) at koji build server.
Any idea what can cause this issue?


Version-Release number of selected component (if applicable):

fedora:latest

How reproducible:

Using fedora 34 docker image with travis CI

Actual results:

builds are failing

Expected results:

Building works fine

Additional info:

upstream report https://github.com/fedora-cloud/docker-brew-fedora/issues/93
Comment 1 Wolfgang Ulbrich 2021-05-23 08:54:29 UTC 
Can someone please take a look at this issue?
I really need some help with debugging this problem.
Comment 2 Wolfgang Ulbrich 2021-06-03 15:03:34 UTC 
Problem was caused by using Ubuntu bionic as container host system for Travis CI.
I could fix that with switching all our repo configs to use Ubuntu focal as container host system.
Thank you for your attention.