Replies: 4 comments 7 replies
-
|
If everything (at least those packages where it might make a difference) is also available in backports to get new functionallity w/o waiting another two years i can't see any reason why not. |
Beta Was this translation helpful? Give feedback.
-
|
I particularly like |
Beta Was this translation helpful? Give feedback.
-
|
i'm all for reducing the number of random debian repositories out there unless really necessary. i think all grml should be formally packaged in debian, and that normal debian mechanisms (backports, fasttrack) can be used for edge cases (if needed at all). re. grml-live and moving scripts around (which seems, to me, like a rather separate discussion - after all, all those packages could be packaged in debian as well, as is!), i wonder if one could make the argument for a
so i don't quite see why all the scripts are being moved there... but then again, that already happened, so maybe that ship has sailed already and it's too late! :) in any case, total 👍 on deprecating deb.grml.org! |
Beta Was this translation helpful? Give feedback.
-
|
Having the Is there any progress on creating these packages and uploading them to main? Getting a nice console setup via apt is quite useful, so it would be great if there was a viable replacement for deb.grml.org before the current repo is shut down. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Our overall goal is to make grml-live the actual central place for building Grml ISOs, and fully supporting customization from within there. Custom Debian packages for all our other projects/software tend to be hard to maintain, and usually require some extra efforts and knowledge.
Another goal of us is to make our release process as smooth as possible, and reduce manual steps and maintenance efforts also on our side.
Maintenance of https://deb.grml.org/ requires some specific actions around release time and also maintaining the Debian packages requires our time and efforts. We therefore are considering to sunset deb.grml.org. But before going that road, would like to hear, whether there are any good reasons, why we shouldn't be doing so. :)
Current state of our Debian source packages that we shipped in grml-stable repository from deb.grml.org:
Related issues for this are #220, grml/grml-live#344, grml/grml-scripts#27 + grml/grml-etc-core#188
We're trying to integrate as many projects as possible from the list above into grml-live itself. For the remaining ones we plan to support those via Debian itself, and if relevant also provide Debian packages through GitHub Workflows with GitHub Assets.
Do we have any users of deb.grml.org, who might want to add their feedback, f.e. why and how you're using deb.grml.org, and whether our plan makes sense for you, or are we maybe even overlooking something that should prevent us from sunsetting deb.grml.org?
Beta Was this translation helpful? Give feedback.
All reactions