Oof, on it

j0rge•46d ago

rpm-md repo 'updates-archive' (cached); generated: 2024-03-28T01:49:15Z solvables: 37996
error: No matches for 'vte-profile' in repo 'copr:copr.fedorainfracloud.org:kylegospo:prompt'

in the container build

j0rge•46d ago

https://github.com/ublue-os/bluefin/actions/runs/8485239207/job/23249661342

GitHub

chore: fix build issues related to tuned-ppd (#1070) · ublue-os/blu...

An interpretation of the Ubuntu spirit built on Fedora technology - chore: fix build issues related to tuned-ppd (#1070) · ublue-os/bluefin@d2be880

j0rge•46d ago

@Kyle Gospo Was gonna say, it's fine on 38 but realized we don't build it for 38 lol

bsherman•46d ago

i'll take a look at the ptyxis copr stuff oh, i can't really help it's all under kyle's copr and personal github repo

Nathaniel•46d ago

Goshdarnit Kyle lol Just kidding Kyle, we appreciate you!

bsherman•46d ago

hmm... I use the same copr as a source for ptyxis on my custom image and as of yesterday's build, my ptyxis is still good i wonder if today's would be broken

j0rge•46d ago

yeah it just broke today maybe we should centralize a bunch of packages in the packages repo while we're converting them to 40?

bsherman•46d ago

interesting that there were no ptyxis copr builds yesterday/today, but i see an update to vte packages that identify themselves as from the copr hmm... yeah, i see the same error after updating to today's build, but the diff is so curious

anguirel in ~
at 16:18:46 $ ptyxis
ptyxis: symbol lookup error: ptyxis: undefined symbol: vte_terminal_get_current_container_runtime

anguirel in ~
at 16:18:58 $ rpm-ostree db diff
ostree diff commit from: rollback deployment (8ef4e52a14c7a948c7217f6a3af51bb7350e443cac9d434a6f30b4b88251c4e5)
ostree diff commit to:   booted deployment (4a7b60e1d69be3e966de307c0a1ec5eeb17429caf73f1375c5175f4922fb03c9)
Upgraded:
  btrfs-progs 6.7.1-1.fc39 -> 6.8-1.fc39
  mesa-vulkan-drivers 23.3.5-10.ublue.0.0.git.41.141da21d -> 23.3.6-1.fc39
  mesa-vulkan-drivers 23.3.5-10.ublue.0.0.git.41.141da21d -> 23.3.6-1.fc39
  vte-profile 0.74.2-3.fc39.prompt -> 0.74.2-4.fc39.prompt
  vte291 0.74.2-3.fc39.prompt -> 0.74.2-4.fc39.prompt
  vte291-gtk4 0.74.2-3.fc39.prompt -> 0.74.2-4.fc39.prompt

anguirel in ~
at 16:18:46 $ ptyxis
ptyxis: symbol lookup error: ptyxis: undefined symbol: vte_terminal_get_current_container_runtime

anguirel in ~
at 16:18:58 $ rpm-ostree db diff
ostree diff commit from: rollback deployment (8ef4e52a14c7a948c7217f6a3af51bb7350e443cac9d434a6f30b4b88251c4e5)
ostree diff commit to:   booted deployment (4a7b60e1d69be3e966de307c0a1ec5eeb17429caf73f1375c5175f4922fb03c9)
Upgraded:
  btrfs-progs 6.7.1-1.fc39 -> 6.8-1.fc39
  mesa-vulkan-drivers 23.3.5-10.ublue.0.0.git.41.141da21d -> 23.3.6-1.fc39
  mesa-vulkan-drivers 23.3.5-10.ublue.0.0.git.41.141da21d -> 23.3.6-1.fc39
  vte-profile 0.74.2-3.fc39.prompt -> 0.74.2-4.fc39.prompt
  vte291 0.74.2-3.fc39.prompt -> 0.74.2-4.fc39.prompt
  vte291-gtk4 0.74.2-3.fc39.prompt -> 0.74.2-4.fc39.prompt

I'm not sure where 0.74.2-4.fc39.prompt is coming from well, per my build log, it's from the prompt COPR as we'd expect: vte291-0.74.2-4.fc39.prompt.x86_64 (copr:copr.fedorainfracloud.org:kylegospo:prompt) i'm just confused since i don't see a build from yesterday: https://copr.fedorainfracloud.org/coprs/kylegospo/prompt/package/vte291/ so why the change?

Noel•46d ago

I think that should go on the list. having the repos spread out everywhere and not all maintainers having access to them is a bit of an issue. not saying I can help troubleshoot RPM package issues.

Nathaniel•46d ago

I agree that this is one case where centralization is a good thing

bsherman•46d ago

i partially agree... we don't pull every package we install under our own control

Noel•46d ago

This may be a non issue once we hopefully get our own repo at some point.

bsherman•46d ago

but... if it's a personal git and copr which is installed on multiple ublue-org images that is maintained by one of us... yeah, it likely fits for being in the org i think the https://github.com/KyleGospo/prompt repo could possibly be a subdir within https://github.com/ublue-os/packages like under staging/prompt or something

j0rge•46d ago

yeah I thought we were going to move stuff into there so sign of ptyxis in distro either or incoming, so I think that blog is wrong

bsherman•46d ago

OH! it looks like this COPR build for vte291 is set to auto-build... i wonder if after kyle made some changes in github yesterday, then vt291, well, auto-built... and Kyle saw that and deleted the build... but maybe the artifact is still inthe copr yum cache or something yeah, i think this theory is correct... Kyle yanked the "bad build" but now, there's nothing there because when i search with DNF, i can't find his vte packages and when i try a rebuild of my image error: No matches for 'vte-profile' in repo 'copr:copr.fedorainfracloud.org:kylegospo:prompt' similar reason bluefin can't rebuild if you guys want, i can work on getting the last good version (for F39) of everything working in a shared copr...

j0rge•46d ago

yeah or just toss it in /packages might as well be the next one?

1/4 Life•46d ago

Almost have the new version of this ready to go And I'll get this into our packages now

j0rge•46d ago

kyle went and got gross

bsherman•46d ago

i see what you did there, you went dark, and came back with a miracle

j0rge•46d ago

I'll be playing destiny with an old friend tonight, so I'll miss this. Please feel empathy for me.

Nathaniel•46d ago

I feel empathy for you playing Destiny 😛 So just run updates from TTY once it's back in place?

1/4 Life•46d ago

Yep Been out at appointments all day, picked a great day for this to happen We're going to get something better out of it though, so at least there's that

bsherman•46d ago

did I correctly deduce what happened? you did delete the build to prevent more breakage, right? fishing for "attaboys" here lol, also, let me know if i can help

Nathaniel•46d ago

https://tenor.com/view/not-the-hero-we-deserve-gif-13014154

Tenor

1/4 Life•46d ago

Yes you are correct, usually that doesn't delete the only available package, but the previous build must have been old enough to trigger that Better than shipping something broken I suppose, but unfortunate

bsherman•46d ago

this is me learning to better use COPR, thank you

1/4 Life•46d ago

Added bonus, this may fix the funny little accessibility icons on switches we were getting in some apps thanks to no longer needing a beta build of libadwaita instead, I'm building the F40 spec on F39 Once I confirm this is all happy, I'll open PRs against Bluefin & Bazzite to switch them to the packages repo for Ptyxis

bsherman•46d ago

it's building!!!

1/4 Life•46d ago

1/4 Life•46d ago

vte291 looks good, waiting on gtk4 then libadwaita then ptyxis for 39 (ptyxis for 40 should build rn)

bsherman•46d ago

my custom F39 and F40 both built... i'll test F39 after dinner with fam I'm sorry to report:

$ ptyxis
ptyxis: symbol lookup error: ptyxis: undefined symbol: vte_event_context_get_coordinates

$ ptyxis
ptyxis: symbol lookup error: ptyxis: undefined symbol: vte_event_context_get_coordinates

1/4 Life•46d ago

ptyxis hasn't built yet almost done

bsherman•46d ago

oh 😄 PHEW! ok, bbiab

1/4 Life•46d ago

@j0rge @bsherman https://github.com/ublue-os/bluefin/pull/1073

GitHub

fix: Use Ptyxis from the ublue-os/staging copr repo by KyleGospo · ...

Ptyxis now lives at staging in a new Fedora 40 compatible format.

1/4 Life•46d ago

Don't merge yet, this is almost done building in copr GTK4 takes a full 50 minutes 😔 feel free to approve if you agree w/ contrainerfile changes though

Universal Blue Join

4.4KMembers

View on Discord

Want results from more Discord servers?

Add your server

Cryobytes Cryoutilities and Bazzite OSHi, looking into squeezing more performance from my Legion GO and ROG Ally both running Bazzite. On Waydroid fails to start: [gbinder] WARNING: Service manager /dev/binder has diedAfter upgrading to the most recent bazzite-deck-gnome release, 39.20240328, my previously working Wa Waydroid failing to start with hybrid Nvidia laptopError: ```13:17:06] Introspect error on :1.922:/ContainerManager: dbus.exceptions.DBusException: org Lenovo Legion Go extend partitionI am wondering if its possible to extend the partition that I originally created. I started with 30 VMware Horizon fails to installTrying to install from a local RPM file I downloaded directly from the website. Renamed the file for Legion Go eGPU – No video out in Game ModeHey all, big fan of the project and recently installed Bazzite on a Legion Go. Absolutely loving it Dual Boot install issue on GPD Win 4Ive been trying to get bazzite installed on a separate partition on my Win 4, but it keeps giving me GNOME Session Restarts (Framework 16)I’ve tested on both Nobara 39 and Bazzite OS (both Fedora 39) and I am getting random session restar Possible ditch of "flatpak uninstall --unused" in ublue-os/config & ublue-updateSince this is merged in flatpak upstream, could we ditch in the future `flatpak uninstall --unused` Legion Go SD card not recognizedRecently installed Bazzite on my Legion Go and having this issue with the internal SD card reader. C Games not launching from Game Mode from LutrisI installed Assassin's Creed via Lutris and added the shortcut to steam. It opens and plays fine on Wifi 6e supported?Hello. Is wifi6e supported on the Legion Go with the latest version of Bazzite? I can connect to m CoreOS kernelsCoreOS kernels thread Can't access port 8080Does bazzite (or silverblue) come with some default firewall? I'm trying to access the CEF remote de bazzite nvidia driver issuetoday my nvidia driver somehow failed and it went back to llvmpipe. i checked ptyxis and it told me Wifi network found, but cant connect to internetI just installed Bazzite on my Lenovo Legion Go for the first time. It can see my wifi network, but Legion Go - Fixed GPU clock not working with Simple DeckyTDPI have a Legion Go with SimpleDeckyTDP isntalled. If I enable it to overwrite the normal Steam TDP c NumLock on logon screenHi I'm new to Linux and decided try bazzite. I have a problem where I have to turn on NumLock every How do I disable the Bazzite splash screen when opening a terminal.I'm using bazzite as my main desktop os and I want to disable the spash screen I see every time I op TDP limit not working?Probably just me doing something wrong but whenever I set the tdp to say 15 or 18, the graph still s

Gaming

Programming

Oof, on it