• 2 Posts
  • 1.52K Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle





  • So I started out with a bugreport to BoxBuddy because that’s where I first found it. Then they said it was just running a distrobox create --clone yaddayadda so I then went to distrobox issues. Then when I tried it in a dualboot on that same machine of Fedora 41 and it worked, I went searching for the Aurora issues tracker with no luck, and then I got on with my life.


  • I’m curious enough, but this seemed like it was going to be hard to track down a way to fix it, and I needed that laptop working for other things, and Aurora was being really flakey in other ways as well so I just nuked it.

    I’m happy to burn time debugging an issue for a project, but when I tried to track down a way to bugreport to Aurora, I didn’t find anything easily. And this promised to turn into a fingerpointing issue, so I moved on.


  • ikidd@lemmy.worldtoProgrammer Humor@programming.devWorks on my machine
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    edit-2
    3 days ago

    It’s about predictable troubleshooting for a bug, not about whether you can install it. No doubt you can, but now the dev has to figure out what particular feature in your OS is causing the issue.

    I had this recently, installed Distrobox, which is just a set of scripts, on Aurora. Could not --clone a container, no how. Blow the OS out and install Fedora 41 which is what Aurora is derived from except it’s rpm-ostree, and not a problem cloning a Distrobox. Closed the bug as there was no point trying to figure out what went on there for some weird edge case of using a specific distro.