Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some Gazebo Garden debbuilders have this error: Unable to install all build-deb packages #10

Open
Crola1702 opened this issue Nov 21, 2023 · 1 comment

Comments

@Crola1702
Copy link
Contributor

Migrated from https://github.com/osrf/buildfarmer/issues/331 on Jul 28, 2022

This error has happened on 3 debbuilders:

  • ign-launch6-debbuilder
  • ign-gazebo7-debbuilder
  • ign-math7-debbuilder

The error goes like this:

  1. dpkg-deb tries to build debbuilder dependencies: dpkg-deb: building package '[debbuilder]-deps' in ...
  2. Reads database and prepares to unpack debbuilder deps package.
  3. Then, this message shows:
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) [package]-build-deps:amd64 < [version] >
Broken [package]-deps:amd64 Depends on [package 2]:amd64 < none @un H >
  Considering [package 2]:amd64 1 as a solution to [package]-deps:amd64 -2
  Removing [package]-deps:amd64 rather than change [package 2]-dev:amd64
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages will be REMOVED:
  [package]-deps
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 9,216 B disk space will be freed.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 36616 files and directories currently installed.)
Removing [package]-deps ([version]) ...
mk-build-deps: Unable to install [package]-build-deps at /usr/bin/mk-build-deps line 457.
mk-build-deps: Unable to install all build-dep packages
+ sleep 60
+ seconds_waiting=60
+ '[' 60 -ge 300 ']'
+ false

This message shows 5 times (try to install -> fails -> try to install again). Each time seconds_waiting increment in 60 seconds more until it reach 300 seconds. Then it exits the build.

Reference builds:

@Crola1702
Copy link
Contributor Author

Comment by jrivero on Agu 1, 2022

Interesting information in the logs when this failure happens is the name of the packages that are blocking the installation:

For example in https://build.osrfoundation.org/job/ign-rendering7-debbuilder/541/console:

Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) gz-rendering7-build-deps:amd64 < 6.999.999+nightly+git20220731+1r37441a5fdab83b9bcf3deeb6de5e016ad65028c6-1~jammy @iU K Nb Ib >
Broken gz-rendering7-build-deps:amd64 Depends on libgz-common5-events-dev:amd64 < none @un H >
  Considering libgz-common5-events-dev:amd64 1 as a solution to gz-rendering7-build-deps:amd64 -2
  Removing gz-rendering7-build-deps:amd64 rather than change libgz-common5-events-dev:amd64
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0

Seems to be a problem with libgz-common5-events-dev. For debugging I would recommend:

  • Try to replicate the error locally by adapting Dockerfile and build.sh files found in https://build.osrfoundation.org/job/ign-rendering7-debbuilder/541/. Note that some of the paths in that files need to be created manually of modifying.
  • If the error is not reproducible, we probably are in a problem with docker cache in the buildfarm.
  • Once the error is replicated, try to install libgz-common5-events-dev package and see if it installs just fine or there are problems with it.

From that point on, the package manager should tell us more information about what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant