Maybe I didn't make it clear enough, sorry about that. The warning already is being logged, but the package name is missing from the log entry after the ':'. The log entry is not saying which package was tried to be installed. I think for completeness sake the package name should be included after the ':' in the log entry (just like it is on the terminal output).

The warning means eopkg did not do anything. Why would you like it be be logged ?

:D Good luck with finals :)

Yea sorry didn't see the other posts. Balancing attention between finals review session and this chain haha

It won't need removing, see my last commit there. We'll handle a full transition when we can do the EFI var manipulation. For now, its harmless for the goofiboot
stub to remain there (and is good for recovery anyway.)

Ehh I'd be more than happy to write up a little guide to remove it if you want. I've done it before. Then you could just put it up somewhere for people to run if they want.

Oh. It's only 84k. OK well thats hardly earth shattering

Ehm not sure atm. If I enable it now we're just gonna have stray/dead goofiboot sitting on the ESP, but I honestly think there's nothing we can do about that :3

Will systemd-boot be enabled for Solus 4 or is that further down the road?

Was implemented when we converted mesa

Ok great, thanks! I'll do better searching around next time.

https://solus-project.com/articles/troubleshooting/general-troubleshooting/en/#eopkg-won-t-install-updates

Obviously this one was wrongly closed.

Finally, rebuild Firefox with --enable-rust-simd and --enable-elf-hack

As per user comment, resolved.

Yes, it seems to be installing properly now.

Note that python-py doesn't exist on Solus (it's called py). python-tox was updated to pull in the correct package names. So you'll need to be installing python-tox and forgot all about trying to install python-py

@igo95862 don't do this. If you are not on unstable, it's better to wait a few more days because there are dependencies between packages and they are not at the same level on stable and on unstable. Also and this is probably why it didn't work for you, you should never have stable AND unstable repositories together.

I am on Stable but I added the Unstable using

Yeah, Phab doesn't let us disable the HTTP link. We only allow HTTPS, but that doesn't prevent you from copying the wrong link, obviously. We might be able to fix this with a redirect, but I can't remember how well Git handles that.

@igo95862 are you on unstable? If so you can update and test now.

I'll fix this up now, python-py is a real package but not one we have.

Kinda replaced by the meta release task

Closing because I've seen no action on this front

Marking as resolved given the above mentioned TLP changes, although we've since removed TLP from our default installs and will be implementing our own solution in the future.

New systemd 235 now in unstable

Patch should be fine. Gonna close this so I don't forget to close it tomorrow.

Took it upstream: https://github.com/clearlinux/clr-boot-manager/issues/77

Yea, I'll poke this on cbm repo now

In T4235#83002, @ikey wrote:

So do you mean fw capsule updates managed by clr-boot-manager? Sounds good to me tbh - so we should raise this on the upstream clr-boot-manager repo. Weird me not
being the upstream anymore :P

In T4235#82998, @yaymalaga wrote:

Now that Make repos go fastly is resolved, you can mark "Draw up a formal sync cycle (i.e. how to remain unblocked and maintain high velocity)" as done right?

Now that Make repos go fastly is resolved, you can mark "Draw up a formal sync cycle (i.e. how to remain unblocked and maintain high velocity)" as done right?

Ikey re binmain: "DIAF you ruined my life"

Closed as of https://github.com/solus-project/ypkg/commit/7956aa698459c06e21e4c7775ee114488eedc5b2

hi @ikey, now that ferryd is done, can this be closed ?

lol

In T4235#80831, @kyrios123 wrote:

All this work for only 2 days...

All this work for only 2 days...

idk im going bed lol

@W-Floyd And some of them deserve to go out for a pint this evening, ain't that right @ikey =)

Not all superheroes wear capes, some of them have bags under their eyes instead ;)

Jesus you don't even wanna know. It's 11:35AM here. All nighter. But ferryd is now actively serving Solus!

About how many hours of sleep did that set you back? :P

ferryd = done

I read the README of acccheck...It states clearly

When I installed samba, there is a binary generated called smb-tools or something similar. I do not think it's function is the same. Reading up on the smbtool GitHub page, I am not sure even if this is what the package is referring to.

Dependency should be on samba and not smbtool

@yaymalaga I would love to see secure boot in Solus but since it was designed with windows in mind there isn't a huge benefit to use it, but it would be nice to have.