-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[Bug]: build-package.sh: cannot compile subpackages #10462
Comments
I will try to fix this bug in |
The issue exists because There was a note for a related issue as well at
Previously, the builds would complete because f0ea9b9#diff-731444686e10066f1aeb6193b5c45aa13844d82e0f54de5aec3c325402972f2bR472 However, at this stage, this will need to fixed, since parent packages may not always be dependencies of other packages. So firstly the |
Ok, I see |
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This also affects normal apt based packaging fyi I think temporarily patching |
The bootstraps generated for apps are done with https://github.com/termux/termux-packages/wiki/For-maintainers#bootstraps Also check termux/termux-app#2892 (comment) I plan on working more on it soon before next termux-app release. Both scripts require lot of changes. |
Actually I have been experimenting I kept retrying (by updating packages that have been outdated) until finally reach this error only to see its been reported a long time ago (but its definitely not related to using pacman) |
You can use changes in #10540 for now. |
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have tested #10540, it shows:
Any idea? |
I can't reproduce the behaviour, atleast when building just command-not-found. Can you try building just command-not-found? Also, make sure you're able to ping |
You're right, it's my network problem, I tried again, it can continue now. |
Sorry for bothering you again, with: Is there a special building parameter for the slim recipe? |
@diyism well what does |
We use
termux-packages/scripts/generate-bootstraps.sh Lines 429 to 472 in 9381ffe
But |
@diyism I encountered both of your problems. Maybe I have to give up previous progress to fix the missing "commands-aarch64-termux-main.h" file? I added nothing but |
By the way I'm using the patch from #10540 as well. |
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is any plan to address these bugs
and |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
@QGB please don't spam random shell commands here. |
@agnostic-apollo
and yeah i am trying to build package locally.
what is my problem? |
@Agono0 This is because build-bootstraps script is broken. There indeed no On other hand generate-bootstraps script works because it operates on already built packages installable by apt, i.e. not their recipes in the termux-packages repository. See this pull request #17031, but anyway built bootstrap still doesn't match generated by generate-bootstraps script. |
@sylirre
Am i doing something wrong? |
@sylirre |
generate-bootstraps is only for official packaging which means it basically useless for Termux derivatives. The Termux application package name should be
It works, but the generated bootstrap archive is much bigger than it should be. Lots of "junk" included which mostly come from subpackage dependencies. |
So , |
still have problem with |
@Agono0 Here is the log file for successfully built bootstraps: bootstraps_build_log.txt Again, if you want to use
There no various hidden workarounds. If deb file is built with prefix |
@sylirre |
seems like i will open new issue for that, as i change
like you see above, first line of the file
and i cannot until now to solve the problem. |
@Agono0 Please don't try to change prefix inside the original precompiled Termux packages. This is not supported! Please look my previous message. Yes, scripts can be easily edited, but binaries are not. Prefix is hardcoded everywhere. Each binary contains at least one reference to the Termux prefix directory. You need to compile everything from scratch. Reminding that |
Thanks so much for info, |
@sylirre
this means that |
Problem description
Now I'm setting up
build-bootstraps.sh
to support compiling bootstrap which will be based on pacman. During testing, a bug was noticed, it appears when the compiler reaches the bzip2 package.Error message (testing happens in docker):
In fact, this can be fixed in
build-bootstraps.sh
, but I don't know if this will be correct.What steps will reproduce the bug?
Command:
What is the expected behavior?
No response
System information
On all devices
The text was updated successfully, but these errors were encountered: