Remix.run Logo
shmerl 4 hours ago

I wish Debian would also transition to a modern bug tracker. Current one is very archaic.

kstrauser 4 hours ago | parent | next [-]

It surely won't win any beauty contests, but do you think it's missing any needed functionality?

Sincere question. I haven't interacted with it much in ages.

agwa 3 hours ago | parent | next [-]

The simple task of following a bug requires you to:

1. Send an empty email to a special address for the bug.

2. Wait 15-30 minutes for Debian's graylisting mail server to accept your email and reply with a confirmation email.

3. Reply to the confirmation email.

The last time I tried to follow a bug, I never got the confirmation email.

In practically every other bug tracker, following a bug is just pressing a button.

Like most of Debian's developer tooling, the bug tracker gets the job done (most of the time) but it's many times more inconvenient than it needs to be.

kstrauser 41 minutes ago | parent | next [-]

Fair points. But without looking at it myself, and for the benefit of people reading along, do you have to do that if you already have an account on the tracker? For instance, it's easy to follow issues on GitHub, but that's after you've jumped through some similar hoops to create an account.

shmerl 3 hours ago | parent | prev [-]

I use reportbug to simplify the process of initial reporting, but whole interaction is still far from convenient.

https://tracker.debian.org/pkg/reportbug

shmerl 3 hours ago | parent | prev | next [-]

It's just annoyingly clunky to use any time I need to interact with it, versus modern bug trackers like GitLab's and etc.

Also, locally patching reportbug to support XDG base directory spec is a chore (since maintainers didn't accept the fix for it for years).

csnover 2 hours ago | parent | prev [-]

As someone who uses Debian and very occasionally interacts with the BTS, what I can say is this:

As far as I know, it is impossible to use the BTS without getting spammed, because the only way to interact with it is via email, and every interaction with the BTS is published without redaction on the web. So, if you ever hope to receive updates, or want to monitor a bug, you are also going to get spam.

Again, because of the email-only design, one must memorise commands or reference a text file to take actions on bugs. This may be decent for power users but it’s a horrible UX for most people. I can only assume that there is some analogue to the `bugreport` command I don’t know of for maintainers that actually offers some amount of UI assistance. As a user, I have no idea how to close my own bugs, or even to know which bugs I’ve created, so the burden falls entirely on the package maintainers to do all the work of keeping the bug tracker tidy (something that developers famously love to do…).

The search/bug view also does not work particularly well in my experience. The way that bugs are organised is totally unintuitive if you don’t already understand how it works. Part of this is a more general issue for all distributions of “which package is actually responsible for this bug?”, but Debian BTS is uniquely bad in my experience. It shows a combination of status and priority states and uses confusing symbols like “(frowning face which HN does not allow)” and “=” and “i” where you have to look at the tooltip just to know what the fuck that means.

joeyh 2 hours ago | parent [-]

The command is `bts` in devscripts. I wrote it in 2001.

thesnide 4 hours ago | parent | prev [-]

to be fair, it fits my exact needs. and without common javacript bloat.

so kudos to its authors

fanf2 4 hours ago | parent [-]

Ian Jackson (the author of this article) also wrote debbugs.