delay archive for "important" bugs

delay archive for "important" bugs

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

The bug tracker moves a bug to "archive" state after a month (according
to the blurb on the homepage).  Is it possible to customize this for
Emacs to delay the move (to say, three months) for "important" bugs?

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: delay archive for "important" bugs

[Michael Albinus]

Thien-Thi Nguyen <ttn@gnu.org> writes:

> The bug tracker moves a bug to "archive" state after a month (according
> to the blurb on the homepage).

That happens only for closed bugs.

> Is it possible to customize this for Emacs to delay the move (to say,
> three months) for "important" bugs?

Why? You could always access the archived bugs as well:

<advertisement>

(debbugs-gnu '("important") '("emacs") t)

</advertisement>

Best regards, Michael.

Re: delay archive for "important" bugs

[Glenn Morris]

Thien-Thi Nguyen wrote:

> The bug tracker moves a bug to "archive" state after a month (according
> to the blurb on the homepage).  Is it possible to customize this for
> Emacs to delay the move (to say, three months) for "important" bugs?

AFAIK this is not possible. I can't see why it matters.
Please note that the help-debbugs list exists and is more appropriate
for such questions IMO.

Re: delay archive for "important" bugs

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]

() Michael Albinus <michael.albinus@gmx.de>
() Mon, 13 Jan 2014 15:30:52 +0100

   > The bug tracker moves a bug to "archive" state after a month
   > (according to the blurb on the homepage).

   That happens only for closed bugs.

Really?  Earlier today, 15344 was not "closed" AFAICT but anyway, i had
to "unarchive" it to be able to continue its thread (via bug-gnu-emacs).
(A previous mail went to /dev/null.)

Perhaps this is a PEBKAC situation -- i wouldn't be surprised...

   > Is it possible to customize this for Emacs to delay the move (to say,
   > three months) for "important" bugs?

   Why?

If a bug is "important", i think it should be visible longer on the
default "browse" link, reproduced here:

http://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;max-bugs=100;base-order=1;bug-rev=1

(from <http://debbugs.gnu.org/Emacs.html>).  I understand that this is
just a question of presentation; i need to play w/ the form...

Hmm, after playing a bit, i think the timeout value has nothing to do w/
whether or not the bug shows up on the default page, but rather the
‘max-bugs’ parameter, plus the particular mix of current bugs...

OK, never mind.  Sorry for the misplaced angst.

   You could always access the archived bugs as well: [debbugs-gnu]

Cool.  I like debbugs-org, too.

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: delay archive for "important" bugs

[Michael Albinus]

Thien-Thi Nguyen <ttn@gnu.org> writes:

>    > The bug tracker moves a bug to "archive" state after a month
>    > (according to the blurb on the homepage).
>
>    That happens only for closed bugs.
>
> Really?  Earlier today, 15344 was not "closed" AFAICT but anyway, i had
> to "unarchive" it to be able to continue its thread (via bug-gnu-emacs).
> (A previous mail went to /dev/null.)

Hmm. On "Thu, 10 Oct 2013 17:19:04 -0400", this bug was confirmed by
Glenn (see message #22). Maybe this triggers also archiving after 4
weeks, dunno.

>    > Is it possible to customize this for Emacs to delay the move (to say,
>    > three months) for "important" bugs?
>
>    Why?
>
> If a bug is "important", i think it should be visible longer on the
> default "browse" link, reproduced here:

Sure.

> Hmm, after playing a bit, i think the timeout value has nothing to do w/
> whether or not the bug shows up on the default page, but rather the
> ‘max-bugs’ parameter, plus the particular mix of current bugs...

Don't understand. What do you mean with 'max-bugs'? The number of bugs
presented when searching?

>    You could always access the archived bugs as well: [debbugs-gnu]
>
> Cool.  I like debbugs-org, too.

Thanks. There are some new patches in the git repo which allow to save
and reuse the result of debbugs-org in a file xxx.org. This was inspired
by a patch from Sebastien.

I haven't increased the debbugs version yet (publishing to the public
ELPA visibility), waiting for comments on usefulness. Maybe you give it
a try ...

Best regards, Michael.

Re: delay archive for "important" bugs

[Glenn Morris]

Michael Albinus wrote:

>> Really?  Earlier today, 15344 was not "closed" AFAICT but anyway, i had
>> to "unarchive" it to be able to continue its thread (via bug-gnu-emacs).
>> (A previous mail went to /dev/null.)
>
> Hmm. On "Thu, 10 Oct 2013 17:19:04 -0400", this bug was confirmed by
> Glenn (see message #22). Maybe this triggers also archiving after 4
> weeks, dunno.

No, of course it does not. The bug was never archived. This is all just
a misunderstanding. If you search for 100 bugs, you will never see more
than 100 bugs. If the one you expected to see is not there, it does not
mean it was archived.

>> If a bug is "important", i think it should be visible longer on the
>> default "browse" link, reproduced here:
>
> Sure.

Disagree. The "default browse link" is just the most 100 recent reports.

If you want to see important ones, use eg

http://debbugs.gnu.org/cgi/pkgreport.cgi?include=severity%3Aimportant;package=emacs

Re: delay archive for "important" bugs

[Glenn Morris]

Thien-Thi Nguyen wrote:

> (A previous mail went to /dev/null.)

You'll get an auto-response if you try to mail an archived bug.
Mail does not simply vanish.

Anyway, I checked and your first mail was (only just) classified as
spam, sorry. Mainly because:

  1.3 RCVD_IN_RP_RNBL        RBL: Relay in RNBL,
                             https://senderscore.org/blacklistlookup/
                             [79.45.43.190 listed in bl.score.senderscore.com]
  3.6 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
                             [79.45.43.190 listed in zen.spamhaus.org]

If you'd have informed help-debbugs, I could have restored it.

The successful mail you sent did not get "RCVD_IN_RP_RNBL" (but still
only just passed).

(I'm not an expert in this stuff.)

Re: delay archive for "important" bugs

[Bastien]

Michael Albinus <michael.albinus@gmx.de> writes:

> Thanks. There are some new patches in the git repo which allow to save
> and reuse the result of debbugs-org in a file xxx.org. This was inspired
> by a patch from Sebastien.

In case the real Sebastien reads this and wonders if he's crazy:

  s/Sebastien/Bastien

:)

-- 
 Bastien

Re: delay archive for "important" bugs

[Michael Albinus]

Bastien <bzg@gnu.org> writes:

>> Thanks. There are some new patches in the git repo which allow to save
>> and reuse the result of debbugs-org in a file xxx.org. This was inspired
>> by a patch from Sebastien.
>
> In case the real Sebastien reads this and wonders if he's crazy:
>
>   s/Sebastien/Bastien

Oops. Sorry for that!

Best regards, Michael.

Re: delay archive for "important" bugs

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

() Glenn Morris <rgm@gnu.org>
() Mon, 13 Jan 2014 17:13:08 -0500

   > (A previous mail went to /dev/null.)

   first mail was (only just) classified as spam

OK that explains it.

   If you'd have informed help-debbugs, I could have restored it.

OK.  Should this be mentioned in admin/notes/bugtracker?  BTW, there is
another i sent (same thread) that got likewise stuck.  Could you please
discard it?  (The bug has since been marked "Done".)

   The successful mail you sent did not get "RCVD_IN_RP_RNBL" (but still
   only just passed).

   (I'm not an expert in this stuff.)

Me neither.  Unfortunately, my (residential ADSL) ISP's relay rejects
mail sent to debbugs (dot gnu...) w/ a "non-existent domain" complaint
and so i configured the local MTA to send directly (no "smarthost").  I
wonder if there is a better way, apart from using another ISP...

Anyway, i'll go browse help-debbugs archives now and direct my confusion
there in the future.

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: delay archive for "important" bugs

[Glenn Morris]

Thien-Thi Nguyen wrote:

> Unfortunately, my (residential ADSL) ISP's relay rejects
> mail sent to debbugs (dot gnu...) w/ a "non-existent domain" complaint

Hmm. Sorry, that's above my paygrade.
If it helps, you can mail bug-gnu-emacs@gnu instead.
So long as your mails are replies to existing bugs (essentially, if the
subject starts with "Re: bug#123"), they will still go to the right
place, just as if you had mailed 123@debbugs.

Re: delay archive for "important" bugs

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

() Glenn Morris <rgm@gnu.org>
() Tue, 14 Jan 2014 13:19:11 -0500

   Hmm. Sorry, that's above my paygrade.

No worries.  I'll figure something out (and post findings) eventually.

   If it helps, you can mail bug-gnu-emacs@gnu instead.  So long as
   your mails are replies to existing bugs (essentially, if the subject
   starts with "Re: bug#123"), they will still go to the right place,
   just as if you had mailed 123@debbugs.

Right.  It was for the (mistaken need to do the) "unarchive" action
that i had to send to control at debbugs.  I'll stop meddling w/ that
now -- there are more than enough non-archived bugs to look at still!

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: ttn unable to mail to debbugs.gnu.org (was: delay archive for "important" bugs)

[Joshua Judson Rosen]

Glenn Morris <rgm@gnu.org> writes:
>
> Thien-Thi Nguyen wrote:
>
> > Unfortunately, my (residential ADSL) ISP's relay rejects
> > mail sent to debbugs (dot gnu...) w/ a "non-existent domain" complaint
>
> Hmm. Sorry, that's above my paygrade.

It may be because debbugs.gnu.org has no MX record in DNS. I seem to
recall having had that problem with some mail server my e-mail was
passing through, at some point.

Debian uses an explicit MX record to for their debbugs instance, FYI.

debbugs.gnu.org also has no SOA record, but the SOA for gnu.org says
the person to e-mail is "hostmaster" at that domain.

-- 
"'tis an ill wind that blows no minds."

Re: ttn unable to mail to debbugs.gnu.org

[Glenn Morris]

Joshua Judson Rosen wrote:

> It may be because debbugs.gnu.org has no MX record in DNS. I seem to
> recall having had that problem with some mail server my e-mail was
> passing through, at some point.
>
> Debian uses an explicit MX record to for their debbugs instance, FYI.
>
> debbugs.gnu.org also has no SOA record, but the SOA for gnu.org says
> the person to e-mail is "hostmaster" at that domain.

Like I said, this is above my level.
I'll pass it on to sysadmin@gnu, thanks.

Re: ttn unable to mail to debbugs.gnu.org

[Glenn Morris]

Glenn Morris wrote:

>> It may be because debbugs.gnu.org has no MX record in DNS. I seem to
>> recall having had that problem with some mail server my e-mail was
>> passing through, at some point.
[...]
> I'll pass it on to sysadmin@gnu, thanks.

I'm told this is fixed now.

Re: ttn unable to mail to debbugs.gnu.org

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

() Glenn Morris <rgm@gnu.org>
() Thu, 16 Jan 2014 16:14:15 -0500

   I'm told this is fixed now.

Cool.  I confirm that All Goes Well now.  Thanks!

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]