Lit's the same as
As far as I understand,
test, to return true or false (0 or 1) based on conditions.As far as I understand,
test -f hello.txt is the same as [ -f hello.txt ] and can be used with in ifwhile/until statements.
ACorrect
ABack in the old days there was no test built-in
AAnd the shell language only really supported
if command; then; echo “the command was successful”; else; echo “the command failed”; fiAhow to have conditionals without modifying the shell itself? Create a funky binary
[ that evaluates the arguments and sets the return code accordingly
J@EyeCantCU Hey! Can we have
gnome-shell-extension-supergfxctl-gex updated? It looks update upstream released an update to fix Gnome 45 compatibility https://gitlab.com/asus-linux/supergfxctl-gex/-/releases https://copr.fedorainfracloud.org/coprs/eyecantcu/supergfxctl/packages/
EWill get that in the morning. Thanks for letting me know!
JAwesome, thank you so much!
JI tried to show somebody asus-nvidia and they mostly got it working, aside from the supergfxctl extension not being compatible which is needed for their hybrid graphics
J@EyeCantCU It also looks like all of the packages could use an update now that I got to look at all of the versions https://gitlab.com/asus-linux/supergfxctl/-/releases https://gitlab.com/Jhyub/supergfxctl-plasmoid/-/releases
JThe Gnome extension is probably the most noticeable though because of broken Gnome 45 compatibility
EWill get here momentarily 
JThank you
B@EyeCantCU it looks like 19 hours ago you merged some ASUS specific stuff into ublue-os/main ?
EWait what
Bi'm not quite sure how... i don't see PRs approved
EI don't recall doing that
EI'll fix that as well?
Band then some surface changes:
https://github.com/ublue-os/nvidia/commit/de17bdd54df22122adad18b414921ea0238f56de
https://github.com/ublue-os/nvidia/commit/de17bdd54df22122adad18b414921ea0238f56de
EGreat
EI feel like a dumbass
AIs main not protected?
Bi can revert that stuff no problem, i just wonder how it happened... if it's just an accident, no problem... but was it some automation?
EI don't understand how opening an MR into ASUS/Surface NVIDIA would impact main
EAt all.
AIt is protected
Bto me, it looks like the change was merged locally and pushed
EI didn't do that
Bit is protected... but... i think we allow bypassing of rules by those with perms
ENot dumb enough to merge BOTH repos into NVIDIA and force push
B
i'm not quite sure how it happened either, that's why I'm bringing it up EI did this via GitHub last night so maybe I overlooked something there?
EVery confused
AYeah but you still need to force push I believe
Bi agree, i think that's required
EThe PRs never even existed for NVIDIA which makes zero sense
Byep, exactly why i was extra confused
ELike how would both repos get changed from one PR?
Bhonestly, i'm a little nervous about the pull app
EShouldn't the pull app only work one way?
Byes, but i had weird behavior and ended up almost pushing stuff to the wrong repo after adding it
Bi would like to resolve this by force pushing
ublue-os/nvidia such that those last 3 commits never existedEI agree
EApologies for everyone. Really screwed up there
EI hadn't even noticed
BI only noticed due to build failures... and then i was surprised because it was obvious we didn't have PRs for those commits
EMaybe GitHub tried to merge both repositories when the PR was opened?
B@EyeCantCU @akdev
I'll do this now
I'll do this now
EThank you so much
