-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Update default spksrc image to Debian12 #6183
Conversation
I've been struggling with my newer PR I've been working on due to the old Debian 11 package set, which also doesn't work well with DSM 7.2 due to older libc version. Above an update that I'll begin testing more in depth on my end and check if there's anything breaking elsewhere. One thing that will require testing is the publishing that still relied on older python2 which is no longer available. |
@th0ma7 I already had a look at debian 12 what about using nasm (and yasm) from debian instead of And I added And I would ommit man-db and manpages-dev since we never provide man pages in packages (due lacking man in DSM) IMHO python2 is not available in debian 12 isn't it. |
good idea, let's add them by default. for the time being framework could check if available in path, else use native.
yup,
well, as i am often running in my container as spksrc it is quite useful to have the man pages close by...
indeed, now gone. |
@th0ma7 IMHO you will get errors, since the install RUN command is too long (currently 1184 characters)
if we really need to install all those components, we have to split the installation into two RUN commands |
@th0ma7 As already mentioned somewhere, I suspected problems with old ppc archs under debian 12. With recent tests I found that only a few packages fail to build for arch-ppc853x-5.2 under debian 12:
Further analysis of ffmpeg revealed an error in the Makefiles of ffmpeg The following configure arg must not be defined for OLD_PPC_ARCHS, but only for qoriq
otherwise configure fails with
|
Nice, well done if these are the only ones failing.
In theory fixed now with the RUN division I've setup.
I adjusted ffmpeg accordingly, now to be confirmed if this will run properly as ? if I recall ? changing the |
@th0ma7 you didn't update to debian 12 yet. |
@th0ma7 some more issues:
|
@hgy59 sigh... clearly an oversight, thnx. now fixed (and tested locally) - should now be ok. todo: adjust framework to make usage of local |
This was a false comment |
Dockerfile
Outdated
# Install hg github tool | ||
RUN curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg && \ | ||
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | tee /etc/apt/sources.list.d/github-cli.list > /dev/null && \ | ||
apt update && \ | ||
apt install gh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as commented, gh is installable in debian-bookworm without additional prerequisites...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thnx, now fixed and using default debian repository.
But why should we have github command line tool?
I figured, when things goes sideways gh
can be quite handy to play with your repository. Totally optionnal, agreed, but as our project entirely sits under github, and its nice to have it around once in a while, it doesn't cost too much, further as now part of default debian repository.
I must admit, that I didn't had to use it in a while as I have a strong preference on git
. Although there may be something to do with it for future download options ... Unless you disagree I'd keep it included for now on?
BTW, thnx for the review @hgy59 as I've been pursuing this during the too litle spare time I have currently and while simple it definitively needs another pair of eye :) |
@hgy59 I've updated
Wonder if it would be worth adding a Any thoughts? EDIT: Actually, maybe even a more generic variable name ? |
@hgy59 I've been testing this new container image sucessfully since a few weeks already. Besides proposal above #6183 (comment) which can wait later, anything else missing before merging? |
we don't need any nasm path nor native/nasm if nasm is a dev env prerequisite. |
Description
Update default spksrc image to Debian12
Fixes #
Checklist
all-supported
completed successfullyType of change
smallframework changes