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

Bug#754693: marked as done (RFH action claims that package is not in unstable)



Your message dated Sun, 13 Jul 2014 20:49:16 +0200
with message-id <20140713184916.GI18337@x230-buxy.home.ouaza.com>
and subject line Re: Bug#754693: RFH action claims that package is not in unstable
has caused the Debian Bug report #754693,
regarding RFH action claims that package is not in unstable
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.)


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

Hi,

https://tracker.debian.org/pkg/gnupg lists an action item called "RFH".
Clicking the "?" behind it gives the text:

> Severity: normal
> Created: 2014-07-02
> Last Updated: 2014-07-02
> The WNPP database contains an RFH (Request For Help) entry for this package.
> This is probably an error, as it is neither part of unstable nor experimental.
> Please see bug number #660685 for more information.

The package clearly is in unstable and the tracker knows about this
fact, as seen from the columns on the left.


Cheers,
Thijs

--- End Message ---
--- Begin Message ---
Hi,

On Sun, 13 Jul 2014, Thijs Kinkhorst wrote:
> https://tracker.debian.org/pkg/gnupg lists an action item called "RFH".
> Clicking the "?" behind it gives the text:
[...]
> The package clearly is in unstable and the tracker knows about this
> fact, as seen from the columns on the left.

This was already corrected as of a few days ago but the current
entries in the database had to be regenerated. I just did this.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/

--- End Message ---

Reply to: