[Silvan]

openmamba has already a project called netsrpms which provides support for local download and RPM packaging of components which cannot be distributed. Adding support for vscode and edge is now in my TODO list.

[Silvan]

By doing a quick check the license might not allow binary distribution of vscode either, although other official sources like this page seem to be permissive when citing some distributions.
While I need to do further checks when I have time I have removed the visual-studio-package from openmamba repository as a precaution.

[Silvan]

I will do an installation test with the latest livecd ISO image. Did you set automatic login on your installations?

[Silvan]

I cannot get a useful stacktrace.
This and this are reports to a similar problem.
I assume that no system changes have been made and the package kwallet-pam is installed.
If it is a general openmamba problem it should be reproduced by me or reported by other users when updating existing installations or doing a fresh installation but the fact that this is happening only to you and on two installations suggests to investigate on any post installation operation you have made on both systems, for example the installation of any external software might have changed the /etc/pam.d files and as written above it seems that the problem is at PAM level.

[Silvan]

The report you sent (related to another problem) shows a crash of the ksecretd daemon. I don’t know if it is the same installation of this post, in any case it might be worth to see a useful stacktrace of the crash dump. As an example the following console commands might produce the stacktrace as output:

sudo dnf install kf6-kwallet-debug
coredumpctl info -q -r

[Silvan]

I’ve checked but the license does not allow to redistribute Microsoft Edge binaries in a public repository.
By the way it might be provided as an openmamba installable component from network, a specific mechanism which locally downloads the upstream archive and creates the RPM. However this requires some more effort than simply creating the package for the repository so I will evaluate doing this work when possible.

The process of updating packages is managed by a chain of openmamba specific tools called autospec, autodist and webbuild which are today provided in a ready-to-use docker environment with the openmamba-docker-buildvm project. This project provides a web interface and scripts that are periodically run to do batch operations like checking for packages to be updated, build them and release to a repository.

• This reply was modified 5 months, 1 week ago by Silvan.

[Silvan]

Hi,
this would normally happen because the user has set a password for KDE Wallet. You may want to try to open KWalletManager and change the password by setting an empty one.

[Silvan]

Hi,
I’ve updated the kernel to version 6.12.49 and I have included the patch you requested.
The missing files resulting from your build probably are related to a missing dependency that would result by examinating the full build log, maybe kmod.

[Silvan]

You only see a tenth of lines in the Console output box? There should be hundreds if not thousands of lines since the beginning of rpmbuild… maybe the scrollbar is not working?
About not seeing anything “relevant” in /var/webbuild/tmp, did you by chance use the “build” button below the editor or the autodist “build” button in the right?
Additionally, if you clicked on the [x] on the line in the top processes box, then the build log (if done using the “build” button below the editor) is gone.

• This reply was modified 6 months, 2 weeks ago by Silvan.
• This reply was modified 6 months, 2 weeks ago by Silvan.

[Silvan]

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.

[Silvan]

When you build a SRPM using the build button of the **Webbuild** you get the build process in a line in the top box. When build is finished by clicking on this line you get the full scrollable build log in the “Console output” box. The build logs for the processes in the top, which you can show in the console output box, are the files located in /var/webbuild/tmp. Or are you looking for something else?

[Silvan]

Hi,
your previous reply was blocked by the antispam mechanism, maybe due to html code and/or urls it contained, and I have later approved it.

Glad you sorted out your issues.

About Docker unfortunately the resolv.conf file will be overwritten the next time you start the container. Public resources say that if you will recreate the container you may run it with docker run --dns 1.1.1.1 --dns 8.8.8.8 ... to have alternative DNS permanently set.

About package build, as I said you may find build requirements missing (flex in this case) because SRPMs specs do not contain a full list of build requirements and the new container has only a basic know set of general requirement installed.

• This reply was modified 6 months, 2 weeks ago by Silvan.

[Silvan]

This is a Docker issue. If your Docker host is openmamba I can suggest to restart it on the host:
sudo systemctl restart docker.

Possible checks in the running container are the nameservers set in the file /etc/resolv.conf by checking and pinging directly the IP address, by the way this kind of problem when I’ve seen it is usually some sort of problem in docker network interfaces which gets solved when restarting the host service.

[Silvan]

Can you check that the container has access to internet? This is the only explanation I currently have for the “Select a SRPM package” select being empty. You may check if the following command run from a container shell works:

curl https://push.openmamba.org/pub/openmamba/base/SRPMS.base/

The “Select a .spec file” select will be populated when you “Unpack and edit” SRPMS packages.

• This reply was modified 6 months, 3 weeks ago by Silvan.

[Silvan]

Hi,
you should have the “Unpack and edit” button on the right like in the attached image and should start by pressing it.
NOTE: if it is the first time you login press F5 to reload the page, this is a known issue.

Then you get the spec file in the editor and have buttons below. To create a new release add a changelog next to “new release with changelog:” and press the update button. You add the patch from a network url using the “Add patches” box on the right or you should add it manually in the /var/autodist/RPM/SOURCES folder and edit the spec file to add and apply the patch.

Next you may press the “build” button below to start building the package.

These are the very basic things to learn but of course they do not cover everything you may need to know.
By starting a new container you will probably need to install some basic build requirements which are missing.

• This reply was modified 6 months, 3 weeks ago by Silvan.

Attachments:

You must be logged in to view attached files.

[Author]

Posts