Recently I signed up a new account on https://tracker.debian.org.
However, I am not receiving notifications when I expect that I should have.

I set up subscriptions for multiple packages, including
linux-image-amd64, openssh-server, and openssh-sftp-server, all of which
have been updated in recent weeks, during the time the new account and
subscriptions existed. I should have recieved some kind of notification,
but nothing has come in.

I did receive the original confirmation email, which is required to set
up and authorize the account.

The subscription email is aith7eigh9eaphee@jmomo.net

This might be related to #1071469

In my case it it seemed to have worked for a while, but then after a while I
got a notification with the following content:
"The email didi.debian@cknow.org bounces too much, it has been unsubscribed
from the Debian Package Tracker."

No idea why it received bounces, nor did I receive a message that they
happened, in which case I could've tried to do something about it.

Hello,

All those package names are "binary packages" and not "source packages".
The package tracker is based on source packages and you can only subscribe
to source packages.

If you use the web interface to subscribe, this can't happen in theory. If
you use the mail interface, you should get a warning about the fact that
you are subscribing to a source package that doesn't exist...

Have a nice day!

There is no indication to me that I am experiencing a similar issue, but
thanks for the suggestion.

I am sorry, but you are very confused and mistaken.

It was not appropriate to have closed this bug since you did not address
the issue documented in the bug report.

Even if there is a problem with the Binary Package keyword feature, that
does not explain why I did not receive any emails during this time
period, when the other  keywords should have also triggered a notification.

For example, I did receive notifications for openssh on the
debian-devel-changes@lists.debian.org and
debian-changes@lists.debian.org mailing lists, which I was also
subscribed to.

In regards to your argument about the Binary Packages keyword...

My interaction with tracker was entirely through the web interface at
https://tracker.debian.org.

Adding the "Binary package" keyword through the web interface is trivial
and obvious. Simply click on the "Modify keywords" button and it's a
checkbox item. This isn't something hidden or obscure.

It is true that the "Binary Package keywords were not enabled by
default. I specifically checked them.

Debian's documentation for tracker says:

"The followed keyword are disabled by default but users can opt-in to
each of them if they wish to receive the corresponding messages:"

and

"upload-binary Notification of a binary package upload that got accepted
in the archive. In the case of Debian, it means a dozen of emails for
each source package upload, every time that the package has been built
for another architecture."

Reference: https://qa.pages.debian.net/distro-tracker/usage/messages.html

Your own documentation says this is possible and explains how to do it.

If your documentation and website are wrong, I would suggest you might
want to look into fixing that.

It just occurred to me that the package names themselves might a part of
the problem, rather than just the checkboxes.

linux-image-amd64, openssh-server, and openssh-sftp-server are all
Package Names. I suspect this is what the term "Binary package" means,
but the documentation is not entirely clear on that.

openssh-server and openssh-sftp-server come from the source repo
"openssh", from which the packages are built.

Again, like the Binary Packages checkboxes, the web user interface
allows these package names to be selected. Simply type in "openssh" into
the package name text field and allow the auto-complete popup to provide
a large selection of "Binary Packages" to choose from.

Further, if I enter "openssh-sftp-server" into the field directly, no
error or warning is presented.

Hi J Mo,

I am not sure if this was your intent, but your message comes off as
hostile and a bit rude, please remember that everyone here is a volunteer and
trying their best.

Specifically:

and


I can appreciate that it can be frustrating to have an issue closed when
you don't feel like its resolved. But I would ask you to be kinder
in your communication in the future.

Lev, I would ask that you assume good faith on my part. I was not trying
to be rude.

Let's try to keep things factual.

Here is a gallery of screenshots demonstrating my prior claims:

https://imgur.com/a/Ff2BDLO

If anyone is not able to reproduce these conditions, please let me know
and we will work it out.

Yes, exactly, that's what I meant.

I have opened https://salsa.debian.org/qa/distro-tracker/-/issues/72 to
track this issue. I prefer gitlab for generic bugs and feature requests on
distro-tracker (the BTS entry is for things that apply only to
tracker.debian.org, i.e. the debian instance).

If you subscribe to source packages, you will receive email notifications.

Cheers,

Before creating this bug, I had requested a salsa.debian.org gitlab
account and the request was rejected.