Giter Club home page Giter Club logo

repo-build-scripts's People

Contributors

totaam avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar

repo-build-scripts's Issues

some debian containers fail to install dependencies - systemd related

Different from #1.
On Debian sid, it starts here:

Setting up libturbojpeg0-dev:amd64 (1:2.1.5-2) ...
dpkg: dependency problems prevent configuration of dbus-user-session:
 dbus-user-session depends on systemd; however:
  Package systemd is not configured yet.

dpkg: error processing package dbus-user-session (--configure):
 dependency problems - leaving unconfigured
Setting up libwayland-bin (1.21.0-1) ...

Then:

Setting up libproc2-0:amd64 (2:4.0.3-1) ...
dpkg: dependency problems prevent configuration of systemd-timesyncd:
 systemd-timesyncd depends on systemd; however:
  Package systemd is not configured yet.

dpkg: error processing package systemd-timesyncd (--configure):
 dependency problems - leaving unconfigured
Setting up libvorbis0a:amd64 (1.3.7-1) ...
Setting up udev (252.5-2) ...
(..)
Setting up libqrencode-dev:amd64 (4.1.1-1) ...
dpkg: dependency problems prevent configuration of libpam-systemd:amd64:
 libpam-systemd:amd64 depends on systemd (= 252.5-2); however:
  Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libopenjp2-7:amd64 (2.5.0-1+b1) ...
(..)
Setting up libjpeg-dev:amd64 (1:2.1.5-2) ...
dpkg: dependency problems prevent configuration of libnss-systemd:amd64:
 libnss-systemd:amd64 depends on systemd (= 252.5-2); however:
  Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of dconf-service:
 dconf-service depends on default-dbus-session-bus | dbus-session-bus; however:
  Package default-dbus-session-bus is not installed.
  Package dbus-user-session which provides default-dbus-session-bus is not configured yet.
  Package dbus-session-bus is not installed.
  Package dbus-user-session which provides dbus-session-bus is not configured yet.

dpkg: error processing package dconf-service (--configure):
 dependency problems - leaving unconfigured
Setting up libharfbuzz-gobject0:amd64 (6.0.0+dfsg-3) ...
(..)
Setting up libavutil-dev:amd64 (7:5.1.2-3) ...
dpkg: dependency problems prevent configuration of dconf-gsettings-backend:amd64:
 dconf-gsettings-backend:amd64 depends on dconf-service (<< 0.40.0-4.1~); however:
  Package dconf-service is not configured yet.
 dconf-gsettings-backend:amd64 depends on dconf-service (>= 0.40.0-4); however:
  Package dconf-service is not configured yet.

dpkg: error processing package dconf-gsettings-backend:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libegl-dev:amd64 (1.6.0-1) ...
(..)
Setting up libpangoft2-1.0-0:amd64 (1.50.12+ds-1) ...
dpkg: dependency problems prevent configuration of libgtk-3-common:
 libgtk-3-common depends on dconf-gsettings-backend | gsettings-backend; however:
  Package dconf-gsettings-backend:amd64 is not configured yet.
  Package gsettings-backend is not installed.
  Package dconf-gsettings-backend:amd64 which provides gsettings-backend is not configured yet.

dpkg: error processing package libgtk-3-common (--configure):
 dependency problems - leaving unconfigured
Setting up libatk1.0-dev:amd64 (2.46.0-5) ...
Setting up libpangocairo-1.0-0:amd64 (1.50.12+ds-1) ...
Setting up libgdk-pixbuf-2.0-dev:amd64 (2.42.10+dfsg-1+b1) ...
Setting up python-gi-dev (3.42.2-3+b1) ...
dpkg: dependency problems prevent configuration of libgtk-3-dev:amd64:
 libgtk-3-dev:amd64 depends on libgtk-3-common (>= 3.24.36-4); however:
  Package libgtk-3-common is not configured yet.

dpkg: error processing package libgtk-3-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libharfbuzz-dev:amd64 (6.0.0+dfsg-3) ...
Setting up libxmu6:amd64 (2:1.1.3-3) ...
Setting up libpangoxft-1.0-0:amd64 (1.50.12+ds-1) ...
dpkg: dependency problems prevent configuration of libgtk-3-0:amd64:
 libgtk-3-0:amd64 depends on libgtk-3-common (>= 3.24.36-4); however:
  Package libgtk-3-common is not configured yet.

dpkg: error processing package libgtk-3-0:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up pango1.0-tools (1.50.12+ds-1) ...
dpkg: dependency problems prevent configuration of gir1.2-gtk-3.0:amd64:
 gir1.2-gtk-3.0:amd64 depends on libgtk-3-0 (>= 3.24.24); however:
  Package libgtk-3-0:amd64 is not configured yet.
 gir1.2-gtk-3.0:amd64 depends on libgtk-3-common; however:
  Package libgtk-3-common is not configured yet.

dpkg: error processing package gir1.2-gtk-3.0:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libglvnd-dev:amd64 (1.6.0-1) ...
Setting up libxaw7:amd64 (2:1.0.14-1) ...
Setting up librsvg2-2:amd64 (2.54.5+dfsg-1) ...
Setting up gir1.2-pango-1.0:amd64 (1.50.12+ds-1) ...
dpkg: dependency problems prevent configuration of xpra-build-deps:
 xpra-build-deps depends on libgtk-3-dev; however:
  Package libgtk-3-dev:amd64 is not configured yet.

dpkg: error processing package xpra-build-deps (--configure):
 dependency problems - leaving unconfigured
Setting up libpango1.0-dev:amd64 (1.50.12+ds-1) ...

Eventually failing:

Errors were encountered while processing:
 systemd
 dbus-user-session
 systemd-timesyncd
 libpam-systemd:amd64
 libnss-systemd:amd64
 dconf-service
 dconf-gsettings-backend:amd64
 libgtk-3-common
 libgtk-3-dev:amd64
 libgtk-3-0:amd64
 gir1.2-gtk-3.0:amd64
 xpra-build-deps
E: Sub-process /usr/bin/dpkg returned an error code (1)
(Reading database ... 47913 files and directories currently installed.)
Removing xpra-build-deps (5.0-1) ...

And so we can't make builds for those Debian distros until they fix whatever is broken.

buildbot failures

No idea what's going on, trying to install the build dependencies fails, repeatedly:

...
Get:241 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3-magic all 2:0.4.15-1 [9280 B]
Fetched 74.0 MB in 1min 50s (674 kB/s)
Unable to correct missing packages.
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-libc-dev_4.15.0-144.148_amd64.deb  404  Not Found [IP: 91.189.88.142 80]
E: Aborting install.

So I can't post any new builds.

`rpmspec` is buggy

So we end up not rebuilding packages when we should.

$ rpmspec   -q --rpms src/packaging/rpm/python2-Cython.spec 
python2-Cython-0.29.35-1.fc37.src
python2-Cython-debuginfo-0.29.35-1.fc37.src
python2-Cython-debugsource-0.29.35-1.fc37.src
$ rpmspec   -q --srpm  src/packaging/rpm/python2-Cython.spec 
python2-Cython-0.29.35-1.fc37.src

Using --builtrpms makes no difference.
Why on earth is it giving .src rpm names?

CUDA version constraints

RHEL 8 clones ship with Python 3.6 so we can't build pycuda versions newer than 2022.1: Xpra-org/xpra@6b7fb1d or pytools versions newer than 2022.1.13:
Xpra-org/xpra@2bac058

The problem is that CUDA 12 can't be used for building this pycuda version.. so ideally we would need the packaging directory to specify which CUDA version to enable for the builds.

Is #7 a viable solution for this?

buildbot segfaults

Seems to happen more frequently now, on the new buildbot VM.

One build was just hanging, lots of gcc processes "running" but not actually making any progress.
Then lots of random segfaults, on different distro builds:

xpra/server/cystats.c:6282:1: internal compiler error: Segmentation fault

gcc -pthread -shared -Wl,-z,relro -Wl,-z,now -g -Wl,-z,relro -Wl,-z,now -g -Wl,--as-needed -O2 build/temp.linux-x86_64-3.11/xpra/x11/bindings/xi2.o -L/usr/lib64 -lX11 -lXi -o build/lib.linux-x86_64-3.11/xpra/x11/bindings/xi2.cpython-311-x86_64-linux-gnu.so -Wall -Wl,--as-needed
during RTL pass: ree
xpra/x11/bindings/keyboard.c: In function ‘__pyx_pymod_exec_keyboard’:
xpra/x11/bindings/keyboard.c:26055:1: internal compiler error: Segmentation fault
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.rockylinux.org/> for instructions.

collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core dumped

stream9 aarch64 is missing python3-pkgconfig

Which blocks the build of python3-lz4.

That's strange because the x86_64 builds have it: Xpra-org/xpra#3600 (comment)

And rpmfind claims such a package exists: https://www.rpmfind.net/linux/RPM/epel/9/aarch64/Packages/p/python3-pkgconfig-1.5.5-2.el9.noarch.html

Yet:

dnf --enablerepo="*" --disablerepo=repo-local-source --disablerepo=repo-local-build  \
    --disablerepo="*nfv*" --disablerepo="rt*" --disablerepo="resilient*" \
    search python3-pkgconfig

Quite a few repositories have to be disabled to even get this command to run..
Searching for python3-lz4 also returns a blank.

Is aarch64 really supported fully in RHEL9?

almalinux key error

It is impossible to make new builds until this is resolved:

$ dnf update
otal                                                                                                                                                                                                                                                                        13 MB/s |  71 MB     00:05     
AlmaLinux 8 - BaseOS                                                                                                                                                                                                                                                        3.3 MB/s | 3.4 kB     00:00    
Importing GPG key 0xC21AD6EA:
 Userid     : "AlmaLinux <[email protected]>"
 Fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Public key for platform-python-3.6.8-56.el8_9.3.alma.1.x86_64.rpm is not installed. Failing package is: platform-python-3.6.8-56.el8_9.3.alma.1.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for python3-libs-3.6.8-56.el8_9.3.alma.1.x86_64.rpm is not installed. Failing package is: python3-libs-3.6.8-56.el8_9.3.alma.1.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sqlite-libs-3.26.0-19.el8_9.x86_64.rpm is not installed. Failing package is: sqlite-libs-3.26.0-19.el8_9.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Error: GPG check FAILED
Error: while running runtime: exit status 1

Caused by AlmaLinux 8 GPG key change.

BUT, if your system has not received updates for a long time and almalinux-release package version is lower than 8.8-3.el8 you will not be able to install packages signed with the new key until you manually import new GPG key as trusted.

We don't want to upgrade almalinux-release, these are build environments that need to stay pinned on the release they're for.

package ignored

Initially reported in Xpra-org/xpra#4031 (comment)
This causes problems when python2-Cython from our local repository is ignored and RHEL8 uses the one from appstream, which is too old.

$ createrepo -v repo/x86_64  |& grep python2-Cython                                          
14:29:17: Adding pkg: repo/x86_64/python2-Cython-0.29.36-1.el8.x86_64.rpm
14:29:17: Adding pkg: repo/x86_64/python2-Cython-debuginfo-0.29.36-1.el8.x86_64.rpm
14:29:17: Adding pkg: repo/x86_64/python2-Cython-debugsource-0.29.36-1.el8.x86_64.rpm

The package is there, it is added to the repodata and yet:

$ dnf install python2-Cython --disablerepo=appstream --enablerepo=repo-local-build  
Repo Local Build 8 - x86_64                                                                                                                                                                                                                                              3.0 MB/s | 3.0 kB     00:00    
Repo Local Build 8 - x86_64                                                                                                                                                                                                                                               12 MB/s | 287 kB     00:00    
Repo Local Source 8 - x86_64                                                                                                                                                                                                                                             2.9 MB/s | 3.0 kB     00:00    
All matches were filtered out by modular filtering for argument: python2-Cython
Error: Unable to find a match: python2-Cython

Solution was found here; libssh2 filtered out by modular filtering on RHEL 8

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.