Live data from Hacker News

Debian Packages That Need Lovin'

wnpp.debian.net

51–60 of 151 posts

Re: Debian Packages That Need Lovin'

#51

I once built a whole deployment system out of packaging all our services as Debian packages and running them out of our own apt repo. Once we got it working, this was a really low maintenance system and bringing new servers online was stupid easy. Since then Debian packages have become easier to create and maintain. And it’s a great skill if you ever need to create e.g. a custom-compiled version of nginx or some such…

Yeah, same here. It’s really nice to be able to spin up a clean Ubuntu VM on any provider, and just adding your repo, key and being an apt install away from deployment. Makes it super easy for us to deploy dedicated instances for Enterprise customers as well - no exotic dependencies and no problem if they want on prem or wherever else.

Re: Debian Packages That Need Lovin'

#52

If you sort by Installs this is kind of disturbing. A lot of well known packages (Apache2 / OpenSSL / LibreOffice etc.) have no owner? https://wnpp.debian.net/?sort=installs%2Fdesc&page=1

I think the list of packages that need lovin', needs lovin' itself. It seems this list is abandonware.

If you look into the details for some these packages, you will see that it is a dead discussion forgotten even by the person who initiated it, a decade ago.

E.g. the discussion about Libreoffice is not about Libreoffice at all, but Apache Open Office, and you can see that there are people who have offered help, but the OP never responded to their offers.

Just click on the links on the package names and read for yourself.

Re: Debian Packages That Need Lovin'

#54

why is eclipse so many version behind the current version? I do not think it would hurt to update a little faster.

Why would you need a package for Eclipse. Download it is a ZIP, extract it in the location of your choice and run it from there. (Portable app)

I have been using it like that almost every day for 15 years now.

Re: Debian Packages That Need Lovin'

#55

I once built a whole deployment system out of packaging all our services as Debian packages and running them out of our own apt repo. Once we got it working, this was a really low maintenance system and bringing new servers online was stupid easy. Since then Debian packages have become easier to create and maintain. And it’s a great skill if you ever need to create e.g. a custom-compiled version of nginx or some such…

I'm helping with building that part at my current job and the main problem that I'm finding is that the documentation is not good at all. There's a lot of trial and error, outdated documentation and such that makes it hard to get started.

I do agree that once it's setup properly with a CI pipeline, it becomes a breeze to install and maintain updated systems.

Re: Debian Packages That Need Lovin'

#56

If I want to help, what should I do?

Well, you need to get competent enough before you take on a role as package maintainer. For start, imagine that you are one.

First, choose a package that really matters to you. On a daily basis. A package that you yourself would NEED to have it up2date the next day a new version is out.

Get the source deb and try to build it. Usually it's not very hard.

Then, try to do the same on all the debian variants (unstable, stable, ...)

If you succeed and the package works, you have the prerequisite competencies, at least as a beginner.

Then, these are some of the things that you will need to do, quite often.

Change the configuration of the package description so that you can build it with a later version of the source. For all variants of the distro.

Then try the same with the package dependencies, where those dependecies are not needed for other packages.

Then try to push it as close towards the latest source version, as you can without breaking stuff.

Once you do all that without issues and you are confident that you can use the version you built from source as a daily driver and you are not bothered by that, contact the original maintainer directly and offer help, sharing the details what you did as proof that you are competent enough.

If the maintainer is uncollaborative or unresponsive, put up your own repo for public use, and invite the public to install the package from your repo, so that the public will see some benefit and you will receive zillion of bug reports to further streghten your competence level.

Re: Debian Packages That Need Lovin'

#58

I have been using Debian on and off since the late 90s, including some time creating packages. It was wonderful to be able to install a recent, working version of pretty much anything you wanted for the vast majority of that time. More recently, so many things I want to use are not available as a reasonably up-to-date package. Some examples are hugo and eclipse, where the versions provided are unusably ancient. https…

Homebrew is meant to be language agnostic.

Re: Debian Packages That Need Lovin'

#59

Looking at orphans by installs and I remember using some of these 20 years ago, but do people even use libgpod and xmms anymore?

that's my first reaction to this list too - is a debian-specific package really providing more value than the effort of maintaining it for a lot of this software? even libgpod and xmms are relatively high-profile examples.

i do appreciate being able to apt-get install some obscure package and have often wondered how it's a sustainable system that maintainers are putting in effort to package these things up into a distro for me. but maybe it isn't?

Re: Debian Packages That Need Lovin'

#60
post #46

I once built a whole deployment system out of packaging all our services as Debian packages and running them out of our own apt repo. Once we got it working, this was a really low maintenance system and bringing new servers online was stupid easy. Since then Debian packages have become easier to create and maintain. And it’s a great skill if you ever need to create e.g. a custom-compiled version of nginx or some such…

What do you recommend for learning that stuff?

I wish I could recommend something but I learned it years ago and I honestly don’t remember where from. I’ll try to put together a modern version of my old LUG talk on the subject to show people how to get started.
Post reply on HN