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

mk-build-deps build failure (usage printout) #5

Open
sxiii opened this issue Dec 15, 2021 · 3 comments
Open

mk-build-deps build failure (usage printout) #5

sxiii opened this issue Dec 15, 2021 · 3 comments

Comments

@sxiii
Copy link

sxiii commented Dec 15, 2021

Fails to build with printing out help for mk-build-deps:

(base) [sm@fedora-mbp docker-deb-builder]$ ./build -i docker-deb-builder:20.04 -o output ./sources/bmxlib-libmxf
Running docker:
docker run -it -it -v /home/sm/work/docker-deb-builder/sources/bmxlib-libmxf:/source-ro:ro -v /home/sm/work/docker-deb-builder/output:/output -v /home/sm/work/docker-deb-builder/build-helper.sh:/build-helper.sh:ro -e USER=1000 -e GROUP=1000 --rm  docker-deb-builder:20.04 /build-helper.sh
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Usage:
    mk-build-deps --help|--version

    mk-build-deps [options] control file | package name ...

Do you have any ideas on what should I check? I thought about the dependencies list but it seems to be fine.
Thanks!

@tsaarni
Copy link
Owner

tsaarni commented Dec 22, 2021

Hi @sxiii,
Sorry for delay replying. Does the source code of bmxlib-libmxf have debian/control file and other packaging files that are required by the packaging tools https://wiki.debian.org/Packaging/Intro

@sxiii
Copy link
Author

sxiii commented Dec 28, 2021

That's OK @tsaarni -- Originally it hadn't, but I've written the required files myself when I was trying to make it work :)

@tsaarni
Copy link
Owner

tsaarni commented Dec 30, 2021

I quickly looked at the mk-build-deps script from Debian devscripts package and it seemed to me that the usage could be printed if debian/control was missing, or maybe it could be some typo in the deb packaging files. Other than that, I don't have ideas...

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

2 participants