[einar.hjortdal]

Thank you so much

[einar.hjortdal]

No of course there are many lines, I just truncated the last few. But I did find the error, it was above, as you suggested.
I did press the build button below the editor. I don’t even see the other one.
I don’t know the reason why the logs were not matching what I got in the web application before, now they match and are what I’d expect. Thank you for telling me the path of the logs

I have encountered this error now, but I can’t find anything in the log. Do you remember also encountering this error?

RPM build errors:
File not found: /var/autodist/RPM/BUILD/kernel-6.12.37-build/BUILDROOT/lib/modules/6.12.37-2mamba-x86_64/modules.builtin.alias.bin
File not found: /var/autodist/RPM/BUILD/kernel-6.12.37-build/BUILDROOT/lib/modules/6.12.37-2mamba-x86_64/modules.builtin.bin

I tried to upload the log in zst format but I got an error saying I am not allowed to upload this kind of files 😀

I would like to backport this commit to the kernel, because I have a device that would work with this commit that does not work now.
This may be a crazy request but, do you think you could backport this for me?
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btusb.c?id=7722d6fb54e428a8f657fccf422095a8d7e2d72c

• This reply was modified 2 weeks, 1 day ago by einar.hjortdal.
• This reply was modified 2 weeks, 1 day ago by einar.hjortdal.

[einar.hjortdal]

Silvan wrote:

Addition: as most builds are parallelized you often won’t find the error at the very bottom of the build log. By scrolling up the “Console log” you might find the error information many lines before the end. The Console box tries to help by evidencing possible error lines using a red background.

You’re right! I found out by piping the output to a file and grepping, because I couldn’t find the log file.

cat /var/autodist/log/logloglog.log | grep Error
make[3]: *** [arch/x86/boot/compressed/Makefile:140: arch/x86/boot/compressed/vmlinux.bin.zst] Error 127
make[2]: *** [arch/x86/boot/Makefile:100: arch/x86/boot/compressed/vmlinux] Error 2
make[1]: *** [arch/x86/Makefile:312: bzImage] Error 2
make: *** [Makefile:224: __sub-make] Error 2

[einar.hjortdal]

hmm what I pasted above comes from that “Console output” box. To me it seems like it lacks standard error, but maybe I am wrong.

I mean, this doesn’t tell me what the error is, so I can’t fix that.

LD [M]  virt/lib/irqbypass.ko
make: *** [Makefile:224: __sub-make] Error 2
error: Bad exit status from /var/tmp/autodist/rpm-tmp.mcuZwR (%build)

I looked in /var/webbuild/tmp but it doesn’t contain any relevant information.
I’m currently building the kernel without any change. Likely there is a missing dep

[einar.hjortdal]

LD [M]  virt/lib/irqbypass.ko
make: *** [Makefile:224: __sub-make] Error 2
error: Bad exit status from /var/tmp/autodist/rpm-tmp.mcuZwR (%build)

RPM build errors:
Bad exit status from /var/tmp/autodist/rpm-tmp.mcuZwR (%build)
ERROR: rpmbuild exited with error code: '1'
# WEBBUILD_EXITCODE=1

I am getting some errors in the console output, but they don’t contain much information. Where do I find the logs?

[einar.hjortdal]

The issue is not a real issue, it was fixed by installing flex manually in the container.
I am not allowed to modify the message so I must reply here.

[einar.hjortdal]

I have manually edited the /etc/resolv.conf inside the container and the issues were resolved.
I have now a new issue here: https://pastebin.com/x8kaGuuV
It looks like it cannot find the required packages to build.

P.S. I couldn’t submit more information before, somehow the forum limited me

• This reply was modified 2 weeks, 1 day ago by einar.hjortdal.

Attachments:

You must be logged in to view attached files.

[einar.hjortdal]

The docker host is openmamba. You were right, restarting the daemon seemed to fix the issue. But this fix was short-lived, after loading the list of packages and attempting an “unpack and edit”, this issue reappears.

[root@buildvm /]# curl https://push.openmamba.org/pub/openmamba/base/SRPMS.base/
curl: (6) Could not resolve host: push.openmamba.org (Timeout while contacting DNS servers)

But it does resolve the google domain.

[root@buildvm /]# curl google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>

I am suspecting something is up with resolvectl and docker

• This reply was modified 2 weeks, 1 day ago by Silvan.
• This reply was modified 2 weeks, 1 day ago by einar.hjortdal.

Attachments:

You must be logged in to view attached files.

[einar.hjortdal]

[root@buildvm /]# curl https://push.openmamba.org/pub/openmamba/base/SRPMS.base/
curl: (6) Could not resolve host: push.openmamba.org (Timeout while contacting DNS servers)

You guessed right

[einar.hjortdal]

Hi thank you for the reply. I am experienced with rpmbuild. I imagine the /var/autodist/RPM is the usual rpmbuild directory

The build environment is selected just like in your screenshot, but I have no spec to select. I have F5’d but no changes.

Attachments:

You must be logged in to view attached files.

[einar.hjortdal]

I have the container running on my system and the web interface open in my browser.

What I’d like to do is to add a patch the the kernel and get it to package it.

At the top of the web interface I select the base repository, and the SRPMs select appears, but it has no options. What should I do?

I also have spawned a shell in the running container according to the instructions, I suspect I have to setup something else in it through it.

I have also forked the kernel repository on the gitea, to version my changes.

[einar.hjortdal]

Silvan wrote:

discovery is a strict requirement of the KDE Plasma desktop environment as it is provided by openmamba so it is by design a requirement of the desktop-base-kde meta package.

This is what I wanted clarity on.
On other distributions I’ve used previously, discovery is not a strict requirement for plasma.
If this is how it is for openmamba then it is how it is, despite how unnecessary it may seem to me.

[einar.hjortdal]

Is it normal for desktop-base-kde and kwin-x11 to be removed when a user tries to remove discovery? Shouldn’t those packages be independent?

[einar.hjortdal]

I have reinstalled openmamba and I think I understand what is happening:
After installing I tried to remove discover with sudo dnf remove discover

$ sudo dnf remove discover
Dependencies resolved.
================================================================================================================================================================================
Package                                         Architecture                         Version                                      Repository                              Size
================================================================================================================================================================================
Removing:
discover                                        x86_64                               6.4.0-1mamba                                 @rolling                               6.9 M
Removing dependent packages:
desktop-base-kde                                x86_64                               6.0-7mamba                                   @rolling                                35 k
discover-notifier                               x86_64                               6.4.0-1mamba                                 @rolling                               341 k
mambatray                                       x86_64                               5.3-1mamba                                   @System                                 51 k
Removing unused dependencies:
kwin-x11                                        x86_64                               6.4.0-1mamba                                 @rolling                                12 M
libkwin-x11                                     x86_64                               6.4.0-1mamba                                 @rolling                                12 M

Transaction Summary
================================================================================================================================================================================
Remove  6 Packages

Freed space: 32 M
Is this ok [y/N]: n
Operation aborted.

I had discover uninstalled before the plasma 6.4 update.

• This reply was modified 3 months, 2 weeks ago by einar.hjortdal.

[einar.hjortdal]

I think the recent merges fixed the issue

[Author]

Posts