home.social

Search

1000 results for “ermo”

  1. @ermo

    Given that you've built this package from source, run

    sh bsd/nosh-bundles/post-install

    pkg has sh source the scripts, so sh doesn't know to print line numbers in the error messages. If you tell sh to run the script from file it will, which will help narrow down which of the ~1100 lines it is.

    You don't need to run the script as the superuser to get sh to find this particular error. Ignore all of the permissions errors that will come out, though. (-:

    #nosh

  2. @ermo

    Confusing. The only package with a post-install script that uses redo is nosh-run-system-manager. That does have a declared dependency upon redo in its +MANIFEST.

    In any case, the unterminated quoted string error would not be the result of a missing redo utility. That's a script syntax error, not a command going wrong error. sh unfortunately doesn't report such a syntax error here.

    #nosh

  3. @ermo

    Important note 1C does address how one goes back to the old system.

    The pre-deinstall script for the nosh-run-system-manager package (on FreeBSD) makes that very modification persistently in /boot/loader.conf , so just uninstalling that package is also a way back.

    (On Debian Linux, the mechanism is a symbolic link; and again, installing and deinstalling the package persistently switches the #nosh system manager in and out.)

    #SystemManager

  4. @ermo

    I've updated #djbwares 10 to 12 on the WWW page.

    Thank you for the reminder. I do need to get back to this.

  5. @ermo

    Excellent.

    Yes, the latest released versions are supposed to be a version behind the actual development source. I freeze the source, do a binaries release, and start a new development version.

    So #redo latest binary release is 1.5, and #nosh is 1.41.

    #djbwares is at version 12, with version 13 under development. I must have forgotten to update the WWW page.

  6. Nach der #Ermordung von #AlexPretti durch die #ICE sollte für jeden in Deutschland feststehen: Die #FußballWM2026 in den #USA wird komplett ignoriert!
    Mit einer Absage von Seiten der Politik ist unter dieser schwachen Regierung ja nicht zu rechnen.
    #wm2026boykott

  7. ASTOR FILMLOUNGE Berlin
    LA TRAVIATA live aus der Royal Opera London mit Ermonela Jaho

    Dieses Kino ist wirklich Oberklasse. Zum Empfang Freigetränk, neben jedem Platz ein Tischchen, 1,5 Meter Beinfreiheit, Liegesessel, Hocker zum Füße hochlegen, Bedienung mit Speis und Trank am Platz, Garderobe wie im Theater... Das alles macht den Abend neben der großartigen Aufführung zusätzlich zum schönen Erlebnis.

    #ErmonelaJaho #Oper #Verdi #LaTraviata #Berlin #RoyalOpera #London #Kino

  8. ASTOR FILMLOUNGE Berlin
    LA TRAVIATA live aus der Royal Opera London mit Ermonela Jaho.

    Abgesehen davon, dass heute abend ein Sänger:innenfest zu erleben war, habe ich noch nie jemanden auf einer Bühne so ergreifend sterben gesehen. *noch in Tränen geschrieben*

    #ErmonelaJaho #Oper #Verdi #LaTraviata #Berlin #RoyalOpera #London #Kino

  9. Wenn die wunderbare Sängerin und Darstellerin Ermonela Jaho nicht nach Berlin kommt, dann muss man halt andere Wege finden, sie in der Rolle der Violetta zu erleben: Heute geht es in die ASTOR FILMLOUNGE Berlin, hier ist heute eine Liveübertragung von LA TRAVIATA aus der Royal Opera London mit ihr in der Hauptrolle zu erleben.

    #ErmonelaJaho #Oper #Verdi #LaTraviata #Berlin #RoyalOpera #London #Kino

    Bildquelle: Astor Film Lounge/Royal Opera

  10. ermorde menschen in der zelle und du kannst dein job behalten ... aber wehe du fürchtest um dein leben ... 😔 #justizproblem

    RE: https://bsky.app/profile/did:plc:pavt775rsubl35v2xvktuzks/post/3mbr6ukpxxz2i

  11. Ich träume schon lange davon, einmal die fantastische Sängerin Ermonela Jaho auf der Bühne live zu erleben. Leider kommt sie wohl in absehbarer Zeit nicht nach Berlin. Jetzt habe ich das hier entdeckt: LA TRAVIATA in der Inszenierung der Royal Opera mit ihr in der Titelrolle als Filmerlebnis im Kino ASTOR FILMLOUNGE in Berlin.

    *schreibt Weihnachtswunschzettel*
    👇
    berlin.premiumkino.de/vorstell~

    Bildquelle: Astor Filmlounge

    #ErmonelaJaho #Verdi #Oper #Kino #Traviata

  12. 🔁 Olive (@Oliveolive95)

    Scène apocalyptique sur l’A115 coté ermont aujourd’hui mais magnifique scène d’entraide pour relever le motard et débarrasser toute la route des arbres tombés !

    #ermont #tornade
    @TF1 @franceinfo @BFMTV @FranceTV @Prefet95

    [Video is unavailable]

    🐦🔗 twitter.com/Oliveolive95/statu
    🕐 20/10 21:41

  13. 🔁 Olive (@OlivierArbey)

    Scène apocalyptique sur l’A115 coté ermont aujourd’hui mais magnifique scène d’entraide pour relever le motard et débarrasser toute la route des arbres tombés !

    #ermont #tornade
    @TF1 @franceinfo @BFMTV @FranceTV @Prefet95

    [Video is unavailable]

    🐦🔗 twitter.com/OlivierArbey/statu
    🕐 20/10 21:41

  14. ...ermordet systematisch #palästinensische Kinder mit der Unterstützung unserer Regierung und der Mitglieder des [#US-] Kongresses", sagte #CAIR. 1)

    "Unter der #Biden- und jetzt der #Trump-Regierung hat unsere Regierung es nicht nur versäumt, diese Gräueltaten zu stoppen, sondern hat sie durch massive Waffenlieferungen und ständige diplomatische Deckung aktiv ermöglicht. Unsere...

    1)
    Der Rat für amerikanisch-islamische Beziehungen (CAIR)

    @Bundesregierung @palestine

  15. @Engagierte_BuergerInnen_GR

    Na dann bin ich ja beruhigt!

    Ich frage deshalb, weil der gegen manchem - wichtiger zu sein scheint als eine glaubhafte - gegen den - nach dem von -, obwohl die niemanden haben.

  16. @ermo

    There are a much smaller number of people doing SVCB lookups, too. But, interestingly, they are doing them wrongly.

    And with a direct correlation to some other abuses.

    Which does make me think that, in an ironic twist, it is the bad actors running robot vulnerability probes and scrapers that are the early adopters of SVCB, here.

    #djbwares #DomainNameSystem #svcb

  17. @ermo

    This does make you the second person in the world (if you picked up the source after I put it in yesterday) who can run

    dnsqr https google.com

    or even

    dnsqr https jdebp.info

    I didn't think that people were using this, it only having been accepted in November 2023, but I discovered a few lookups in my logs.

    #djbwares #DomainNameSystem #https

  18. @ermo

    Excellent news! Thank you.

    The warnings are mainly Bernstein's buffer library relying upon being able to use one function pointer to point to multiple different functions with different signatures (which is a shenanighan that one could play with old C, but soon no longer) and Bernstein's byte library using char pointers.

    I've fixed a load of places where the Bernstein code was blasé about function signatures. Those are two of the remaining unfixed areas.

    #djbwares #StandardC

  19. @JdeBP 11 builds on my FreeBSD 14.3 box, though I get a bunch of C23 related warnings.

    Build log here: gist.github.com/ermo/3260dba01

  20. @ermo

    #djbwares 11 is available as a source archive in the usual place if you feel like giving it a go. I have no reason to think that I've broken anything. But I have added a fair amount of stuff. (-:

  21. @ermo

    The PC-BSD challenge was, as you can see from the roadmap, not only doing the FreeBSD part but doing the various add-ons that PC-BSD/TrueOS had, as well.

    jdebp.info/Softwares/nosh/road

    #GhostBSD seems to be the spritual successor to that. So as long as it has ZFS on root, and no bloody GRUB, I'm going to attempt it.

    In an ironic twist, in 1.41 several of the PC-BSD services are now disabled, for security reasons.

    #PCBSD #TrueOS #nosh

  22. @ermo

    This is still low on the priority list, though.

    I'm tackling some of the things that I had explicitly put off until #nosh 1.42. #uschedule ported to NetBSD. dri framebuffer realizers. An #OpenBSD build machine somehow. Renaming the stuff that ends in -tty. And that big #GhostBSD conversion.

    My internal TODO file is not empty. (-:

  23. @ermo

    I'm very slowly creeping towards having checksum files auto-built. There's a missing part that needs to be done.

    But I'm at least over one initial hurdle of switching from pax -z to pax -j. Not that that helps in the #FreeBSD 10 case because FreeBSD 10's pax does not have -j.

    (Make an archive with -z and it isn't idempotent, because #gzip has a timestamp.)

    So there's still the installing #GhostBSD mountain to climb, and seeing whether that has pax -j yet. (-:

    #bzip2 #pax

  24. @ermo

    Sounds a bit complex. (-:

    Debian apt-ftparchive source actually makes checksum lists for source packages.

    No handy equivalent in pkg repo, though.

    It's not going to be high on the priority list. I could possibly modify the .do scripts to do something non-standard.

    In the meantime, the HTTP Last-Modified: response header is right and the If-Modified-Since: request header is respected by Bernstein publicfile. For what that's worth.

    #publicfile #APT #pkg_ng #FreeBSD

  25. @JdeBP I can confirm that redo-1.5, djbwares-11, and nosh-1.41 build packages just fine on both 13.5 and 14.3.

    Build logs on 14.3 in case you end up spotting something interesting:

    - redo-1.5: gist.github.com/ermo/98d627c15
    - djbwares-11: gist.github.com/ermo/238af2423
    - nosh-1.41: gist.github.com/ermo/166ecefe1

  26. @ermo

    That may well be useful.

    #redo version 1.2 (sic!) is in the #FreeBSD ports tree. I was just talking to @schmonz about the state of that port and how I have no real way to let the person behind it know that it's in very poor shape.

    Neither #djbwares nor #nosh are in the FreeBSD ports tree. Presumably there are people working on ports, but that one of them was a decade ago an undergraduate on the other side of the planet shows the kind of barriers in place here.

  27. @ermo

    I'm doing #djbwares 10 next; right now, in fact (although I need to make a trip to the shops).

    When I put it out, that's a good intermediate step to try next. It will test that you have a working redo without being a massive build that builds hundreds of things (as is the case for nosh).

    It has the same basic command workflow as for building redo. There's a new accompanying Guide that details building from source but there aren't any real surprises over building #redo.

  28. @ermo

    That's possibly a good approach with 1.41, until I sort out the #GhostBSD machine.

    You can take the first step in trying it again, right now. #redo version 1.5 is out.

    (Ignore the one in ports. Whoever is in charge of that hasn't made it past version 1.2 and is still using a WWW site that preceded the WWW site that I lost to Brexit half a decade ago.)

    As you can see from package/debian/control it has a build dependency upon perl; but I think that that and base are all that you need.