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

[FLOSS] Installation of self-packaged packages fails on Debian (bullseye) #4543

Open
0x6178656c opened this issue Oct 12, 2022 · 5 comments
Open

Comments

@0x6178656c
Copy link
Contributor

0x6178656c commented Oct 12, 2022

Steps to Reproduce the Problem

I am trying to install self-packaged packages in Debian following the guide: https://www.libelektra.org/installation/installation#cpack

I ran the command in a container specified by the following file

FROM debian:bullseye-20221004

RUN apt-get update && apt-get install --yes cmake build-essential git

RUN apt-get update && apt-get install --yes debhelper d-shlibs

RUN git clone https://github.com/ElektraInitiative/libelektra.git /libelektra

RUN mkdir -p /libelektra/build

WORKDIR /libelektra/build

RUN cmake ..

RUN LD_LIBRARY_PATH=$(pwd)/lib:${LD_LIBRARY_PATH} make package -j2

After building the image

docker build -t libelektra-debianpackagetest .

I launch the container

docker run -it --rm libelektra-debianpackagetest

And then inside the container I do

cd package
apt install ./*

Expected Result

The packages should install with few or no errors and programs such as kdb should be available afterwards.

Actual Result

apt reports an error:

root@7fea9540d1ee:/libelektra/build/package# apt install ./*
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'elektra-bin-dbgsym' instead of './elektra-bin-dbgsym_0.9.11-1_amd64.ddeb'
Note, selecting 'elektra-bin-extra' instead of './elektra-bin-extra_0.9.11-1_amd64.deb'
Note, selecting 'elektra-bin' instead of './elektra-bin_0.9.11-1_amd64.deb'
Note, selecting 'elektra-dbg' instead of './elektra-dbg_0.9.11-1_amd64.deb'
Note, selecting 'elektra-doc' instead of './elektra-doc_0.9.11-1_all.deb'
Note, selecting 'elektra-misc' instead of './elektra-misc_0.9.11-1_all.deb'
Note, selecting 'elektra-tests-dbgsym' instead of './elektra-tests-dbgsym_0.9.11-1_amd64.ddeb'
Note, selecting 'elektra-tests' instead of './elektra-tests_0.9.11-1_amd64.deb'
Note, selecting 'libelektra-dev' instead of './libelektra-dev_0.9.11-1_amd64.deb'
Note, selecting 'libelektra5-all' instead of './libelektra5-all_0.9.11-1_amd64.deb'
Note, selecting 'libelektra5-dbgsym' instead of './libelektra5-dbgsym_0.9.11-1_amd64.ddeb'
Note, selecting 'libelektra5-experimental-dbgsym' instead of './libelektra5-experimental-dbgsym_0.9.11-1_amd64.ddeb'
Note, selecting 'libelektra5-experimental' instead of './libelektra5-experimental_0.9.11-1_amd64.deb'
Note, selecting 'libelektra5-full-dbgsym' instead of './libelektra5-extra-dbgsym_0.9.11-1_amd64.ddeb'
Note, selecting 'libelektra5-extra' instead of './libelektra5-extra_0.9.11-1_amd64.deb'
Note, selecting 'libelektra5-full' instead of './libelektra5-full_0.9.11-1_amd64.deb'
Note, selecting 'libelektra5' instead of './libelektra5_0.9.11-1_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 elektra-dbg : Depends: libelektra5-extra-dbgsym but it is not installable
E: Unable to correct problems, you have held broken packages.

Note the problem persists when using apt-get instead of apt.

I have also verified that the shell (bash) expands the file names as needed:

root@7fea9540d1ee:/libelektra/build/package# echo ./*
./elektra-bin-dbgsym_0.9.11-1_amd64.ddeb ./elektra-bin-extra_0.9.11-1_amd64.deb ./elektra-bin_0.9.11-1_amd64.deb ./elektra-dbg_0.9.11-1_amd64.deb ./elektra-doc_0.9.11-1_all.deb ./elektra-misc_0.9.11-1_all.deb ./elektra-tests-dbgsym_0.9.11-1_amd64.ddeb ./elektra-tests_0.9.11-1_amd64.deb ./libelektra-dev_0.9.11-1_amd64.deb ./libelektra5-all_0.9.11-1_amd64.deb ./libelektra5-dbgsym_0.9.11-1_amd64.ddeb ./libelektra5-experimental-dbgsym_0.9.11-1_amd64.ddeb ./libelektra5-experimental_0.9.11-1_amd64.deb ./libelektra5-extra-dbgsym_0.9.11-1_amd64.ddeb ./libelektra5-extra_0.9.11-1_amd64.deb ./libelektra5-full_0.9.11-1_amd64.deb ./libelektra5_0.9.11-1_amd64.deb

System Information

  • Elektra: master 930673f
  • Operating System: Debian GNU/Linux 11 (bullseye)
@0x6178656c
Copy link
Contributor Author

0x6178656c commented Oct 12, 2022

Running the build script scripts/packaging/package.sh results in installable packages:

FROM debian:bullseye-20221004

RUN apt-get update && apt-get install --yes cmake build-essential git

RUN apt-get update && apt-get install --yes debhelper d-shlibs

RUN git clone https://github.com/ElektraInitiative/libelektra.git /libelektra

RUN mkdir -p /libelektra/build

WORKDIR /libelektra/build

RUN apt-get update && apt-get install --yes lua5.4 python3

RUN bash ../scripts/packaging/package.sh

Note the additional dependencies on Lua and Python.

After that I could install the packages using apt.

So probably only the documentation needs to be updated.

@markus2330
Copy link
Contributor

Thank you for reporting this issue!

So probably only the documentation needs to be updated.

I think you can omit the only. Writing clear and helpful documentation is an important task.

Please update the documentation as necessary. I am afraid "scripts/packaging/package.sh" is not referred to anywhere.

@0x6178656c 0x6178656c self-assigned this Oct 17, 2022
@flo91 flo91 changed the title Installation of self-packaged packages fails on Debian (bullseye) [FLOSS] Installation of self-packaged packages fails on Debian (bullseye) Oct 18, 2022
@markus2330
Copy link
Contributor

@0x6178656c you are still assigned here, is this on purpose?

@0x6178656c
Copy link
Contributor Author

@0x6178656c you are still assigned here, is this on purpose?

Not on purpose.

@0x6178656c 0x6178656c removed their assignment May 2, 2023
Copy link

github-actions bot commented May 2, 2024

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot added the stale label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants