Winding down my Debian involvement • Hacker News Board

Re: Winding down my Debian involvement

#161

Post by bubblethink » Mon, Mar 11, 2019, 6:56 AM UTC

h1d wrote: post #143

bubblethink wrote: post #52

Earlier quoted context omitted.

I think ubuntu has done a decent job with universe by and large. I find it in much better shape overall than epel. A good way to judge the health of these auxiliary repos is to look at the age of chromium. Ubuntu is generally good with patching at least security issues in universe. epel is still running behind by a month or two despite the security disclosures. So RH ought to take a page from Canonical's book when it…

I don't mind RH being slower as I take it that's what makes RH what it is. Old packages but most stable.

It's not about RH packages directly. They are fine. As it is with universe on ubuntu, you quite likely need epel on rhel for doing quite a lot of basic stuff. If you are able to get by with just the proper supported packages in each distro, this doesn't affect you. And that's where the two diverge. universe is in better shape since it is semi-official, v/s epel which is completely unofficial/community-based.

Re: Winding down my Debian involvement

#162

Post by z3t4 » Mon, Mar 11, 2019, 7:13 AM UTC

I haven't made any debian packages, I heard it's a lot of work, but these looks good, not bad:

* Granting personal freedom to individual maintainers

* All maintainers need to read up on what the new thing is, how it might break, whether/how it affects them, manually run some tests, and finally decide to opt in.

Re: Winding down my Debian involvement

#163

Post by kilburn » Mon, Mar 11, 2019, 7:18 AM UTC

monocasa wrote: post #133

sanxiyn wrote: post #124

Earlier quoted context omitted.

The original problem with reporting bugs to a mailing list was mails for many bugs were mixed and you couldn't easily get the state of individual bugs. Debbugs, by automatically creating a new mailing list for individual bugs, does solve this problem admirably. The new problem is that new people hate emails. I think the merit of this problem is debatable.

Mailing lists have had threads for decades.

Broken email clients and careless people break those all the time though...

Re: Winding down my Debian involvement

#164

Post by Annatar » Mon, Mar 11, 2019, 7:19 AM UTC

I'm curious as to what the author would think of this in contrast to Debian:

https://illumos.org/books/dev/

Re: Winding down my Debian involvement

#165

Post by tbodt » Mon, Mar 11, 2019, 7:23 AM UTC

chubot wrote: post #46

Instead, currently, all packages become lint-unclean, all maintainers need to read up on what the new thing is, how it might break, whether/how it affects them, manually run some tests, and finally decide to opt in. This causes a lot of overhead and manually executed mechanical changes across packages. I always wondered if Debian/Ubuntu could benefit from a "monorepo". It seems to work for other distributions, e.g. A…

Reading between the lines I see "wouldn't it be nice if Debian's repository was like Google's repository"

Re: Winding down my Debian involvement

#166

Post by sanxiyn » Mon, Mar 11, 2019, 7:29 AM UTC

monocasa wrote: post #133

sanxiyn wrote: post #124

Earlier quoted context omitted.

The original problem with reporting bugs to a mailing list was mails for many bugs were mixed and you couldn't easily get the state of individual bugs. Debbugs, by automatically creating a new mailing list for individual bugs, does solve this problem admirably. The new problem is that new people hate emails. I think the merit of this problem is debatable.

Mailing lists have had threads for decades.

You can subscribe to individual bugs in Debbugs, you can't subscribe to threads. Threads also don't have short ID (bug 123456) and don't have metadata like whether the bug is closed.

Re: Winding down my Debian involvement

#167

Post by vbernat » Mon, Mar 11, 2019, 7:29 AM UTC

chubot wrote: post #46

Instead, currently, all packages become lint-unclean, all maintainers need to read up on what the new thing is, how it might break, whether/how it affects them, manually run some tests, and finally decide to opt in. This causes a lot of overhead and manually executed mechanical changes across packages. I always wondered if Debian/Ubuntu could benefit from a "monorepo". It seems to work for other distributions, e.g. A…

A mono repo is not needed. Some teams are able to push changes to all the packages of the team without it and without much effort (for example, the Debian Python Modules Team does that quite often). It's more a social problem: all packages should be maintained in the same way and people should be allowed to do global changes. This is true for some teams, not for some others.

Re: Winding down my Debian involvement

#168

Post by IloveHN84 » Mon, Mar 11, 2019, 7:37 AM UTC

jcoffland wrote: post #66

I've been using Debian for over 10 years and I still love it as a user. But as a developer, I find it extremely frustrating. I've several times attempted to figure out how to package my open-source projects [1] [2] for Debian but the process is a nightmare. As I understand it, I first have to find someone with appropriate privileges to mentor me. I should be able to just submit a potential package for review. Then th…

Why not using CMake/cpack? It can generate 100% valid Debian packages and you don't need to do a C++ project, but you can package whatever you want.

Re: Winding down my Debian involvement

#169

Post by vbernat » Mon, Mar 11, 2019, 7:43 AM UTC

Conan_Kudo wrote: post #151

So I've been involved in Fedora for as long as Michael has been involved in Debian, and I have attempted branching out into other distribution communities over the years. To this day, the Debian community is the only community where I have not been able to get past the initial stages to get involved. And you don't have to look too hard to see that I'm in quite a few communities... There's a lot of parallels to Debian…

As a Debian Developer, I often point people to Fedora to show you can be a community distribution very similar to Debian and still be modern in your practice. Your post is insightful.

Re: Winding down my Debian involvement

#170

Post by secure » Mon, Mar 11, 2019, 7:53 AM UTC

switz wrote: post #60

secure wrote: post #24

Earlier quoted context omitted.

Sorry about that! I’m not great with Web Design, as you can tell. If anyone wants to contribute a CSS fix, or just a pointer to a good article on how to fix this, I’d be very grateful!

You could add the following CSS to the container (`.row` here but you should make the class name a bit more specific) which will stack the sidebar and your content into a backwards column (so the sidebar shows up after scrolling past the content, which looks and feels ok for a quick & scrappy mobile fix. display: flex; flex-direction: reverse-column; Put that in a media query to only target phones/small devices. Feel…

Thank you so much! Committed your suggestion in https://github.com/stapelberg/hugo/commit/3a7227fef47fc49550....

Let me know your Paypal, if you have any, and I’ll gladly invite you for a virtual coffee as a sign of my gratitude :)