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-chan...@lists.debian.org and debian-chan...@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.



On 7/5/24 9:38 AM, Raphael Hertzog wrote:
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...

Reply via email to