[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#906963: marked as done (keyword subscription does not always work)

Your message dated Mon, 27 Aug 2018 01:18:16 +0200
with message-id <20180826231816.GA24134@home.ouaza.com>
and subject line Re: Bug#906963: keyword subscription does not always work
has caused the Debian Bug report #906963,
regarding keyword subscription does not always work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
906963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906963
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tracker.debian.org
Severity: normal

Hi,

when i click on my tracker profile, I see a number of packages that I
have subscribed to. The latest addition is ser2net, and when I click on
the arrow, I do see the keywords that I am subscribed to:

build contact archive upload-source summary bts-control bts default

I would like to get the vcs messages, so I click on "Modify Keywords",
and am surprised that everything is ticket there. Regardless on which
change I make here, after clicking on "Save changes", nothing changes,
neither in the overview view nor in the "Choose keywords" dialog.

Is this broken, or am I doing things wrong?

Greetings
Marc

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.3-zgws1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Sun, 26 Aug 2018, Marc Haber wrote:
> > Are you observing the same thing?
> 
> Yes, a complete reload fixed the issue

This bug should now be fixed. For some reason to the automatic
close from salsa did not happen. Here's the commit fixing
this:
https://salsa.debian.org/qa/distro-tracker/commit/0a94cd2680e6866e8bc044294b323a2775e9caa4

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

--- End Message ---
Reply to: