pleroma.debian.social

pleroma.debian.social

Wouter Verhelst | @wouter@pleroma.debian.social

Debian Developer. husband. ex-FOSDEM organizer. Tennis lover. Amateur musician.

If it ain't fun, you're not doing it right.

@lanodan
- the build daemons churn away at building unstable constantly, both to prove that the hardware can keep up and that the toolchain is not riddled with bugs
- after a few years of this, the architecture is added to the official archive. packages from ports are used to build a minimal chroot
- the build system is configured to recompile those packages
- now they build the rest of unstable
@mirabilos @navi @whynothugo

@lanodan
If you dig deep enough, there's always a binary that was used for bootstrapping that isn't available anymore.

How far you need to go for that is what matters, IMO. Debian's process for adding a new port to the archive is:
- someone builds the initial chroot using cross compilers or vendor binaries or something.
- these are used to start the port on ports.debian.net
@whynothugo @navi @mirabilos

@ElizabethLee
I use a wi-fi remote which I can then control with my home assistant setup (but you can also use their phone app if you prefer).

Specifically, mine is a broadlink RM4 mini.

This is more flexible than a universal remote, as it can record the messages from your original remote and that way you can program whatever functionality you need.

Dunno whether that's something you'd consider, but thought I'd mention it.

Don't reply with what you hope, reply with what you expect.

The next AI winter will start...

@bagder
That's only 1.x, right? No plans to get rid of more modern ones?

(Don't expect you to, but it's been my experience that it's better to ask than to indirectly assume all will be fine...)

@fl
Very welcome! Glad you find it useful ๐Ÿ˜Š

@cR0w
(I was at first going to say 'BLE stuff', but that's arguably also computers)

@cR0w
We have a string of led-based Christmas lights that are powered by two of them.

@bagder
Dear Earthling.

This thing came flying on our house. The house collapsed because of it.

We took it apart to figure out where it came from. Imagine our surprise when we discovered it was from Earth.

Please take your crap off our house.

Yours,

The Martian.
(The green type, not the Matt Damon type)

@bagder
Given the amount of emails you get from people seeing your name in legal notices, I'm sure if there are actual martians you'll be the first to find out!

@b0rk
That there is a command 'git rebase -i --autosquash' which you can combine with 'git commit --fixup' to do pretty effing advanced history editing.

I only learned about that after more than a decade of using git. Thanks Stefano!

@ShovelTrouble
Correct, but

(a) the ends do not justify the means, and
(b) deport first then ask questions is not justice.
@eff

@GyrosGeier
Still, if needing extra VRAM may be a reasonable price to pay for some if it means they can move to something more modern without leaving their UI behind.
@ignaloidas

@GyrosGeier
These kinds of issues are why I said "works" rather than the plain unquoted variant of that word ๐Ÿ˜‰
@ignaloidas

@GyrosGeier
Yes, that's what I mean.

Would be awesome because suddenly every window manager "works" with Wayland.

Probably not a good idea though because everything will be very confused.
@ignaloidas

@ignaloidas
To put it otherwise.

I think what I want is a Wayland compositor that doesn't provide a UI, but that instead provides some sort of compatibility layer so you can hook up a window manager to do the actual UI work.
@GyrosGeier @mjg59

@ignaloidas
Not quite.

These are all 'I have a native Wayland application that I want to run in my X11 session'. That's a cool thing, but not what I want to do.

I want to *run* a Wayland environment. Everything should be Wayland, with standard fallback to the XWayland thing for stuff that isn't supported yet.

Except that I just want the UI to be a window manager that expects X11.
@mjg59 @GyrosGeier

@ignaloidas
My understanding of Wayback was that it is a way to provide an X11 implementation that uses the Wayland backend, rather than a way to shoehorn the Wayland frontend under an X11 window manager, which is what I'm suggesting.

Of course my understanding can be wrong, in which case a link to more information would be welcomed by a promise for your favourite beverage at my cost if you look for me at the next FOSDEM ๐Ÿ˜‰
@mjg59 @GyrosGeier

@GyrosGeier
This, but then awesomewm.

I think a more globally useful approach would be to write something that implements the part of an X11 server that the window manager talks to, but that looks like Wayland to the applications. This way, people who really don't want to migrate away from their X11-only environment can keep using it and still use Wayland.

This is probably naive and not possible, but meh, one can dream.
@ignaloidas @mjg59

ยป