On Debian-based distros, when an app is available as a DEB or an AppImage (that doesn’t self-update), but no APT repository, PPA or Flatpak, the only option is to manually download each update, and usually manually check even whether there are updates.

But, what if those would be upgraded at the same time as everything else using the tools you’re familiar with ?

dynapt is a local web server that fetches those DEBs (and AppImages to be wrapped into DEBs) wherever those are, then serves these to APT like any package repository does.

I started building it a few months ago, and after using it to upgrade apps on my computers and servers for some time, I pre-released it for the first time last week.

The stable version will come with a CLI wizard to avoid this manual configuration.

Feedback is welcome :)

  • Daeraxa@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    28 days ago

    Willing to give this a go. My go-to for getting non-repo debs automatically has been deb-get which works well but seems susceptible to issues when changes in the software it lists causes it to break and whilst the fix itself is usually made pretty quickly, it seems to go long periods of time between PR merges and releases (which includes adding new software). If this is a viable replacement for it then i’d love to start using it.

    • KaKi87@jlai.luOP
      link
      fedilink
      arrow-up
      1
      ·
      27 days ago

      Willing to give this a go.

      Alright, don’t hesitate to ask questions if you have any and request help if you need any

      My go-to for getting non-repo debs automatically has been deb-get

      Yes, I mentioned it in the Differences with deb-get & AM section of my tutorial.

      it seems to go long periods of time between PR merges and releases (which includes adding new software)

      Yeah, I could reiterate in that section that my app allows the user to add apps themselves.

  • Asetru@feddit.org
    link
    fedilink
    arrow-up
    1
    ·
    1 month ago

    Sorry to be that guy, but this sounds like a cybersecurity nightmare. While everybody was busy to come up with schemes that make absolutely sure that only trusted sources can update a system to avoid having malicious players push their code to users, this one just takes any rando’s pile of whatever and injects it straight into the system’s core? Like, that doesn’t sound like a good idea.

    • KaKi87@jlai.luOP
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      Well, I’m just automating what people currently have to do manually : visit GitHub and download DEB and install DEB.

      If the automated process would be dangerous then the manual process also would be, and that would be on the maintainer for not providing an APT repository or a Flatpak, not on the user for just downloading from GitHub.

      • cqst@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 month ago

        Well, I’m just automating what people currently have to do manually : visit GitHub and download DEB and install DEB.

        Yeah. You should never do that. Like ever. Build from source; or use a vendored tarball. https://wiki.debian.org/DontBreakDebian

        .deb is a terribly insecure nightmare thats held up by the excellent debian packagers, gpg , and checksums, and stable release model. don’t use .deb files.

          • cqst@lemmy.blahaj.zone
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            1 month ago

            I’m and end user

            Yeah, we all are. What’s your point?

            End users are also developers. All computer users are developers. You are developing.

            user working for end users

            By making a script that lets me get backdoors and shitty packages with ease? The linux package distribution system is a nightmare, Debian is the least bad approach. There is basically always a better option to using a .deb file. If you come across something that isn’t packaged, I recommend Flatpak, building from source (and installing unprivileged), or using the developers vendored tarball (installing unprivileged).

            https://wiki.debian.org/SecureApt

            By using local .debs you lose the benefit of:

            Reproducible builds

            GPG checksums

            Stable release model

            debian security team

            • KaKi87@jlai.luOP
              link
              fedilink
              arrow-up
              1
              ·
              1 month ago

              My point is that I’m working a solution for end users.

              The solutions you’re offering are not user-friendly.

    • markstos@lemmy.world
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 month ago

      No matter where you install from, you have to trust the source. Indeed, you have to trust every step in the supply chain.

      If you are getting your code straight from the author, you are eliminating an exploit that’s introduced by a compromised account of a packager.

      Carry on.