unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso--- via Guix-patches via <guix-patches@gnu.org>
To: "Michael Albinus" <michael.albinus@gmx.de>
Cc: 56987@debbugs.gnu.org
Subject: [bug#56987] [PATCH] etc: guix-debbugs.el: new file.
Date: Wed, 10 Aug 2022 20:10:56 +0000	[thread overview]
Message-ID: <5e171ff2c6243ed0808cf15d0bbfa1e0@dismail.de> (raw)
In-Reply-To: <87sfm4dp4r.fsf@gmx.de>

Sorry for top posting...

The emacs debbugs developers are considering to merge this patch to debbugs directly.

I am willing to submit copyright assignment to GNU/FSF.  It looks like the FSF
has a webpage that may make this process easier:

https://sfconservancy.org/assignment/

Should I use that web page to submit my potential copyright assignment?

Now that we are all on the same page:  

August 10, 2022 12:45 PM, "Michael Albinus" <michael.albinus@gmx.de> wrote:

> Joshua Branson <jbranso@dismail.de> writes:
> 
> Hi Joshua,
> 
> just some comments after short reading of the patch.
> 
>> @example
>> @kbd{C-u} @kbd{M-x} debbugs-gnu @kbd{RET} @kbd{RET} guix-patches @kbd{RET} n y
>> @end example
> 
> Alternatively, a user could set debbugs-gnu-default-packages to '("guix" "guix-patches")
> Then it won't be necessary to enter the package name(s) again and again.

I think that I have tried that in my config, and I could not get it to work.

I will try again and get back to you, and update the guix documentation accordingly.

> 
>> +;; Copyright (C) 2022 Joshua Branson
> 
> This would change to FSF, if bundled with the debbugs package.

Will change

> 
>> +;; Package-Requires: ((emacs "24.3"))
> 
> debbugs.el says
> 
> ;; Package-Requires: ((emacs "26.1") (soap-client "3.1.5"))
> 
> So I guess you might lift up the required Emacs version.

Will do.

> 
>> +;; TODO make this by default only search open bugs AND NOT closed bugs.
>> +(defun debbugs-guix-search ()
>> + (interactive)
>> + (debbugs-gnu-search (read-string "Search String: ") nil nil '("guix" "guix-patches") nil))
> 
> As said the other message, it should be
> 
> (debbugs-gnu-search (read-string "Search String: ") '((pending . "pending")) nil '("guix"
> "guix-patches"))

Will change

> 
>> +;; The debbugs database runs once a day. So after I send a bug report
>> +;; and run this command, my latest bug report might not be here. No worries,
>> +;; just wait one day, and it will be there. :)
> 
> To be more precise, the Hyperestraier search engine on debbugs.gnu.org
> makes new indices after that period. New submitted bugs are in the
> debbugs database shortly after sending the message. It is just
> debbugs-gnu-search, which needs these indices.

Will change

> 
>> +;; I have noticed that this function works 80% of the time. But after I close bug reports,
>> +;; it seems to stop working for about 1/2 hour. I'm guessing the server's database
>> +;; resets itself after every time that I close a bug report...
> 
> debbugs.el uses a cache, which flushes the value after an hour. See the
> variable debbugs-cache-expiry.

Maybe, we could mark a bug as done in the cache when one closes the bug via
debbugs.  That may be a little above my paygrade though.

> 
> There is the command debbugs-gnu-rescan, bound to key "g", which rescans
> an existing tabulated list. With a prefix argument ("C-u g"), the cache
> is ignored, and the data are retrieved directly from debbugs.gnu.el.
> 
> However, please be cautious with invalidating the cache. Every action on
> the debbugs.gnu.org server causes a workload there, and we don't want to
> overuse it.
> 
> Best regards, Michael.


I will resubmit this with the goal of merging directly into debbugs.el.

And I am off tomorrow, so I should have some time to do so!




  parent reply	other threads:[~2022-08-10 20:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  1:23 [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-05  1:32 ` Joshua Branson via Guix-patches via
2022-08-10 15:16   ` Joshua Branson via Guix-patches via
2022-08-10 16:44 ` Michael Albinus
2022-08-10 20:10 ` jbranso--- via Guix-patches via [this message]
2022-08-10 20:24   ` Maxime Devos
2022-08-10 20:39   ` jbranso--- via Guix-patches via
2022-08-10 21:22   ` [bug#56987] Requesting help in assigning copright to Emacs's debbugs jbranso--- via Guix-patches via
2022-08-11 19:51     ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
     [not found]     ` <304e6f0d877d6b8bb60db051e661edf1@dismail.de>
2022-08-17 20:14       ` [bug#56987] Fwd: [gnu.org #1863422] Joshua Allen Branson GNU EMACS jbranso--- via Guix-patches via
2022-08-18  9:52         ` Michael Albinus
2022-08-22 17:21           ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-11  6:24   ` Michael Albinus
2022-08-11 15:25     ` Joshua Branson via Guix-patches via
2022-08-11 16:06       ` Michael Albinus
2022-08-13 22:49         ` Joshua Branson via Guix-patches via
2022-08-12 19:17       ` jbranso--- via Guix-patches via
2022-10-01 15:39 ` [bug#56987] [PATCH] added *my-open-bugs functions Joshua Branson via Guix-patches via
2022-10-02 12:52   ` Michael Albinus
2022-10-03 20:02   ` jbranso--- via Guix-patches via
2022-10-04 14:15     ` Michael Albinus
2022-10-05 16:41 ` [bug#56987] [PATCH] new functions 'debbugs-gnu-my-open-bugs' and 'debbugs-gnu-guix-search' Joshua Branson via Guix-patches via
2022-10-05 20:10   ` bug#56987: " Michael Albinus
     [not found] <rt-4.2.16-14-g9a593ee-12923-1660753466-248.1863422-5-0@rt.gnu.org>
     [not found] ` <RT-Ticket-1863422@rt.gnu.org>
     [not found]   ` <rt-4.2.16-14-g9a593ee-21845-1660236515-917.1863103-5-0@rt.gnu.org>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e171ff2c6243ed0808cf15d0bbfa1e0@dismail.de \
    --to=guix-patches@gnu.org \
    --cc=56987@debbugs.gnu.org \
    --cc=jbranso@dismail.de \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).