Re: December 2020 (old) bugs squashing!

[zimoun]

Hi Maxim,

On Sun, 10 Jan 2021 at 22:06, Maxim Cournoyer  wrote:

> Eh, 2020 is behind us and I don't think I managed to close much bugs in
> last December; it's a priority I'll try to keep up with in 2021.  Let's
> bring the number of issues down to something we can fit in our head more
> easily!

Yeah, with the Chris’ initiative about patches, we should be able to
significantly down the number of items… well, even if the number of new
issues and new patches increases faster than we are able to close old
ones. Sisyphean task? ;-)

Personally, I am trying to deal with one old items per day; on average.
Until “normal” social life pops up again. :-D

Cheers,
simon

Re: December 2020 (old) bugs squashing!

[Maxim Cournoyer]

Hi Simon,

zimoun  writes:

> Hi,
>
> Let’s have an Advent calendar effort!  Everybody out there who is not
> familiar with this tradition of an « Advent calendar » and to avoid any
> ambiguity, I am appropriating myself the concept*: all of us try to
> close one or more bug per day from 1rst to 31th December, then 2021 will
> start on new balls as in tennis match. :-)
>
> In priority let pick bugs older than #3 (~Jan. 2018).
>
> 
>
> From Debbugs, I count 151 bugs or forgotten patches, almost 3 years!
> Time to close them or investigate more.
>
>
> If you do not know how to proceed:
>
>  1. pick an old bug and read the thread
>  2. if the last message is ending with an unanswered question, then mark
> it as moreinfo: send an email to cont...@debbugs.gnu.org using the
> bug number (e.g., 23456) with:
>
>   tags 23456 moreinfo
>   thanks
>
> Please give a look at:
>  
> 
>  3. if you do not know what to do, then reply by asking if the bug is
> still relevant for the author.  Please provide one line to remember
> the topic and the link which points to the bug:
>
>   
>
>   4. if it is a patch, then check if it is not superseded by something
>  already merged, else try to apply it and report success, rebase or
>  failure.
>
> Last, good candidates are bugs with only one or two messages.
>
>
> I hereby offer some ’(define drink)’ for the one who will close as many
> issues as possible in those 31 days.  Well, with the hope to meet those
> bug fighters once real time meeting will be possible again, otherwise
> you will win my gratitude. :-)
>
> For now, Tobias and Maxim have good score but hey we are only the 1th
> day. ;-)

Eh, 2020 is behind us and I don't think I managed to close much bugs in
last December; it's a priority I'll try to keep up with in 2021.  Let's
bring the number of issues down to something we can fit in our head more
easily!

Thanks for the initiative :-).

Maxim

Re: December 2020 (old) bugs squashing!

[zimoun]

Hey ho!

On Sat, 05 Dec 2020 at 16:26, Ludovic Courtès  wrote:

>> In priority let pick bugs older than #3 (~Jan. 2018).
>>
>> 
>>
>> From Debbugs, I count 151 bugs or forgotten patches, almost 3 years!
>> Time to close them or investigate more.
>
> Great initiative!  Go go bug fixers!

Until now, the scoring is:

 + 11 really old bugs
 + 12 old bugs
 + 7 “recent“ bugs

in addition to all the patches merged on Fri. the 18th.  Neat, isn’t it?



Thank you for all the people involved!

The month is not done yet.  A lot of bugs and/or patches are simply
forgotten; a simple email asking relevance if often enough to close it.


If you do not know how to be more familiar with Guix, I can tell you
that digging into the Bugs is a fun experience for learning. :-)


Cheers,
simon

| Num |   Bug | My remember / topic 
 |
|-+---+--|
|  1. | 21992 | About the size of items to download 
 |
|  2. | 22251 | ghc-memory test suite fails on i686 
 |
|  3. | 23874 | patched 
 |
|  4. | 24674 | Dropbear bundled libraries  
 |
|  5. | 26715 | xorg-service exotic 
 |
|  6. | 26981 | make dist   
 |
|  7. | 27145 | document bournish/recovery repl 
 |
|  8. | 27237 | wicd-curses: `urwid' is not available   
 |
|  9. | 27861 | python-graphne  
 |
| 10. | 28810 | Bayfront https file URLs trigger gnutls error   
 |
| 11. | 29771 | Package list no longer being updated
 |
|-+---+--|
| 12. | 30027 | core-updates and Guile 2.2  
 |
| 13. | 30486 | [PATCH] gnu: Add python-boto3 and python2-boto3.
 |
| 14. | 30825 | (Mathieu)   
 |
| 15. | 31602 | Repro of libreoffice fixed  
 |
| 16. | 32709 | Clojure doesn't provide "clojure" executable
 |
| 17. | 33106 | (asked relevance)   
 |
| 18. | 33370 | Cuirass: Trigger 'guix publish' baking  
 |
| 19. | 33636 |  not handling HTML attachments properly   
 |
| 20. | 34061 | bug: failed to compute derivation   
 |
| 21. | 34699 | [PATCH] gnu: add emacs-smart-hungry-delete. 
 |
| 22. | 34811 | Make package name regexes case-insensitive  
 |
| 23. | 37583 | Documentation needed: pam-services in operating-system 
structure |
|-+---+--|
| 24. | 40450 | (asked relevance)   
 |
| 25. | 42405 | r-hdf5array fails to build  
 |
| 26. | 44401 | Add poetry (check if true)  
 |
| 27. | 44452 | Clash Guile 
 |
| 28. | 44485 | mistake 
 |
| 29. | 44928 | guix upgrade command does not accept a list of packages 
 |
| 30. | 44952 | Guix cross-compilation is broken (fixed!)   
 |

Re: December 2020 (old) bugs squashing!

[Bonface M. K.]

Hi!

zimoun  writes:

> Hi,
>
> On Sat, 05 Dec 2020 at 20:42, "Bonface M. K."  
> wrote:
>
>> Just curious, how do you get debbugs to show
>> forgotten patches. I'm only beginning to use it
>> now ...
>
> Forgotten patches are just old patches. ;-)
>
>
> What I do with Emacs is: “M-x debbugs-gnu“ to have all the bugs and
> patches; with something in my config file as:
>
>   (setq
>debbugs-gnu-default-packages '("guix-patches" "guix")
>gnus-summary-line-format "%I%(%[ %n%]%) %s\n"))
>
> Then I scroll down the buffer, generally M-> and I look for the state
> normal in red; which means no answer in the thread.  And I pick one from
> my interest, or hitting p to move.  In any case, it is worth to read all
> of them. :-) Next, I try to understand and/or to reproduce.  Three
> cases:
>
>  a) lacking info so reply for asking more details
>  b) appear to me not-a-bug anymore so ask for status
>  c) real bug so report/update what I did
>
> In addition, I have an Org-mode to track what I open and then remind me
> 3 weeks later in my agenda.  If no answer, I mark it as moreinfo with
> ’M-x debbugs-gnu-send-control-message’ (C).  Otherwise I add an item to
> my TODO list to work on it if I feel enough annoyed.  Time to time, when
> I attend to boring meeting, I review all the moreinfo and close some if
> they are too old, ask again if I am not confident.
>
>
> Reading the bugs via Debbugs, I do ‘M-x org-capture’ (C-ctth blabla C-c
> C-c) then stash the link of the bug ’M-x my/guix-issue’ and start the
> reply ’M-x gnus-summary-wide-reply-with-original’ (R), edit, and ’M-x
> message-send-and-exit’ (C-c C-c), assuming that Emacs is configured to
> send email. :-)
>
>
> Snippet of my config:
>
>   (define-key gnus-summary-mode-map "R" 
> 'gnus-summary-wide-reply-with-original)
>   (define-key gnus-article-mode-map "R" 
> 'gnus-summary-wide-reply-with-original)
>
>   (setq
>org-capture-templates
>(backquote
> (("t" "Todo")
>  ("th" "Hunt" entry
>   (file+headline "~/org/todo.org" "Bug Hunt")
>   ,(my/org-templates-file "todo-bug.org"))
>   org-capture-templates-contexts
>   '(("th" ((in-mode . "gnus-summary-mode")))
> ("th" ((in-mode . "gnus-article-mode")
>
>
> where the capture is:
>
> * TODO  [#C] Bug %?:hunt:
>   SCHEDULED:  %(org-insert-time-stamp (org-read-date nil t "+3w"))
>   :LOGBOOK:
>   CLOCK: %U--%U =>  0:00
>   :OPEN: %U
>   :END:
>   :PROPERTIES:
>   :Open: %U
>   :Subject: %:subject
>   :Date: %:date
>   :MessageID: %:message-id
>   :END:
>
>
> and the helper is:
>
> (defmacro defun-bug->url (name url  docstring)
>   "Macro returning yankage #bug URL.
>
> The `interactive' function that the macro returns is then referred by NAME.
>
> Please provide a DOCSTRING."
>   (let ((fun (intern (symbol-name name)))
> (doc (concat docstring "\n\n"
>(format "Yankable result: `%sNUMBER'." url
> `(defun ,fun (number)
>,doc
> (interactive
>  (list
>   (progn
> (when (not (boundp 'debbugs-gnu-bug-number))
>   (setq debbugs-gnu-bug-number -2))
> (read-string
>  (format "Bug number (%s): " debbugs-gnu-bug-number)
>  nil nil debbugs-gnu-bug-number
>   (let ((str (format "%s%s" ,url number)))
> (kill-new str)
> (when current-prefix-arg
>   (browse-url str))
> (message (format "%s killed." str))
>
> (defun-bug->url my/guix-issues "http://issues.guix.gnu.org/issue/;
>   "Add URL of bug NUMBER to `kill-ring'.")
> (defun-bug->url my/guix-debbugs 
> "https://debbugs.gnu.org/cgi/bugreport.cgi?bug=;
>   "Add (old) URL of bug NUMBER to `kill-ring'.")
>
>
> Last, there is one point I do not like with the Emacs front-end of
> Debbugs is that the network is required.  Well, I would prefer dump all
> the mbox and work with Emacs+Notmuch but I have not yet configured that.
> If someone has tip, please share. :-)
>
> Or maybe fetch from issues.guix.gnu.org the Mumi maildir+mu database.
>
> Hope that helps,
> simon
>

Thanks! This is very helpful and useful. I'm going
to try(with some modifications) this workflow out
:)

-- 
Bonface M. K. 
Humble GNU Emacs User / Bearer of scheme-y parens
Curator:  / Twitter: @BonfaceKilz
GPG Key: D4F09EB110177E03C28E2FE1F5BBAE1E0392253F


signature.asc
Description: PGP signature

Re: December 2020 (old) bugs squashing!

[zimoun]

Hi,

On Sat, 05 Dec 2020 at 20:42, "Bonface M. K."  wrote:

> Just curious, how do you get debbugs to show
> forgotten patches. I'm only beginning to use it
> now ...

Forgotten patches are just old patches. ;-)


What I do with Emacs is: “M-x debbugs-gnu“ to have all the bugs and
patches; with something in my config file as:

  (setq
   debbugs-gnu-default-packages '("guix-patches" "guix")
   gnus-summary-line-format "%I%(%[ %n%]%) %s\n"))

Then I scroll down the buffer, generally M-> and I look for the state
normal in red; which means no answer in the thread.  And I pick one from
my interest, or hitting p to move.  In any case, it is worth to read all
of them. :-) Next, I try to understand and/or to reproduce.  Three
cases:

 a) lacking info so reply for asking more details
 b) appear to me not-a-bug anymore so ask for status
 c) real bug so report/update what I did

In addition, I have an Org-mode to track what I open and then remind me
3 weeks later in my agenda.  If no answer, I mark it as moreinfo with
’M-x debbugs-gnu-send-control-message’ (C).  Otherwise I add an item to
my TODO list to work on it if I feel enough annoyed.  Time to time, when
I attend to boring meeting, I review all the moreinfo and close some if
they are too old, ask again if I am not confident.


Reading the bugs via Debbugs, I do ‘M-x org-capture’ (C-ctth blabla C-c
C-c) then stash the link of the bug ’M-x my/guix-issue’ and start the
reply ’M-x gnus-summary-wide-reply-with-original’ (R), edit, and ’M-x
message-send-and-exit’ (C-c C-c), assuming that Emacs is configured to
send email. :-)


Snippet of my config:

--8<---cut here---start->8---
  (define-key gnus-summary-mode-map "R" 'gnus-summary-wide-reply-with-original)
  (define-key gnus-article-mode-map "R" 'gnus-summary-wide-reply-with-original)

  (setq
   org-capture-templates
   (backquote
(("t" "Todo")
 ("th" "Hunt" entry
  (file+headline "~/org/todo.org" "Bug Hunt")
  ,(my/org-templates-file "todo-bug.org"))
  org-capture-templates-contexts
  '(("th" ((in-mode . "gnus-summary-mode")))
("th" ((in-mode . "gnus-article-mode")
--8<---cut here---end--->8---

where the capture is:

--8<---cut here---start->8---
* TODO  [#C] Bug %?:hunt:
  SCHEDULED:  %(org-insert-time-stamp (org-read-date nil t "+3w"))
  :LOGBOOK:
  CLOCK: %U--%U =>  0:00
  :OPEN: %U
  :END:
  :PROPERTIES:
  :Open: %U
  :Subject: %:subject
  :Date: %:date
  :MessageID: %:message-id
  :END:
--8<---cut here---end--->8---

and the helper is:

--8<---cut here---start->8---
(defmacro defun-bug->url (name url  docstring)
  "Macro returning yankage #bug URL.

The `interactive' function that the macro returns is then referred by NAME.

Please provide a DOCSTRING."
  (let ((fun (intern (symbol-name name)))
(doc (concat docstring "\n\n"
   (format "Yankable result: `%sNUMBER'." url
`(defun ,fun (number)
   ,doc
(interactive
 (list
  (progn
(when (not (boundp 'debbugs-gnu-bug-number))
  (setq debbugs-gnu-bug-number -2))
(read-string
 (format "Bug number (%s): " debbugs-gnu-bug-number)
 nil nil debbugs-gnu-bug-number
  (let ((str (format "%s%s" ,url number)))
(kill-new str)
(when current-prefix-arg
  (browse-url str))
(message (format "%s killed." str))

(defun-bug->url my/guix-issues "http://issues.guix.gnu.org/issue/;
  "Add URL of bug NUMBER to `kill-ring'.")
(defun-bug->url my/guix-debbugs "https://debbugs.gnu.org/cgi/bugreport.cgi?bug=;
  "Add (old) URL of bug NUMBER to `kill-ring'.")
--8<---cut here---end--->8---


Last, there is one point I do not like with the Emacs front-end of
Debbugs is that the network is required.  Well, I would prefer dump all
the mbox and work with Emacs+Notmuch but I have not yet configured that.
If someone has tip, please share. :-)

Or maybe fetch from issues.guix.gnu.org the Mumi maildir+mu database.

Hope that helps,
simon

Re: December 2020 (old) bugs squashing!

[Bonface M. K.]

Ricardo Wurmus  writes:

> Bonface M. K.  writes:
>
>> Just curious, how do you get debbugs to show
>> forgotten patches. I'm only beginning to use it
>> now ...
>
> Debbugs doesn’t have a built-in mechanism to query forgotten issues.
> Mumi implements “forgotten-bug-numbers”, which has the following
> docstring:
>
>   "Return the numbers of issues that are open but haven't seen any
> activity for a while.  The duration is given by SECONDS-AGO, which
> defaults to 30 days."

Thanks for the feedback :)

-- 
Bonface M. K. 
Humble GNU Emacs User / Bearer of scheme-y parens
Curator:  / Twitter: @BonfaceKilz
GPG Key: D4F09EB110177E03C28E2FE1F5BBAE1E0392253F


signature.asc
Description: PGP signature

Re: December 2020 (old) bugs squashing!

[Ricardo Wurmus]

Bonface M. K.  writes:

> Just curious, how do you get debbugs to show
> forgotten patches. I'm only beginning to use it
> now ...

Debbugs doesn’t have a built-in mechanism to query forgotten issues.
Mumi implements “forgotten-bug-numbers”, which has the following
docstring:

  "Return the numbers of issues that are open but haven't seen any
activity for a while.  The duration is given by SECONDS-AGO, which
defaults to 30 days."

-- 
Ricardo

Re: December 2020 (old) bugs squashing!

[Bonface M. K.]

zimoun  writes:

> Hi,
>
> Let’s have an Advent calendar effort!  Everybody out there who is not
> familiar with this tradition of an « Advent calendar » and to avoid any
> ambiguity, I am appropriating myself the concept*: all of us try to
> close one or more bug per day from 1rst to 31th December, then 2021 will
> start on new balls as in tennis match. :-)
>
> In priority let pick bugs older than #3 (~Jan. 2018).
>
> 
>
> From Debbugs, I count 151 bugs or forgotten patches, almost 3 years!
> Time to close them or investigate more.
>

Just curious, how do you get debbugs to show
forgotten patches. I'm only beginning to use it
now ...

[...]
-- 
Bonface M. K. 
Humble GNU Emacs User / Bearer of scheme-y parens
Curator:  / Twitter: @BonfaceKilz
GPG Key: D4F09EB110177E03C28E2FE1F5BBAE1E0392253F


signature.asc
Description: PGP signature

Re: December 2020 (old) bugs squashing!

[Ludovic Courtès]

Hey ho!

zimoun  skribis:

> Let’s have an Advent calendar effort!  Everybody out there who is not
> familiar with this tradition of an « Advent calendar » and to avoid any
> ambiguity, I am appropriating myself the concept*: all of us try to
> close one or more bug per day from 1rst to 31th December, then 2021 will
> start on new balls as in tennis match. :-)
>
> In priority let pick bugs older than #3 (~Jan. 2018).
>
> 
>
> From Debbugs, I count 151 bugs or forgotten patches, almost 3 years!
> Time to close them or investigate more.

Great initiative!  Go go bug fixers!

Nitpick: I’d call it “month of the forgotten bugs”, or “Northern
hemisphere winter of bugs”, or “the advent of fixed bugs” (lowercase).

For an immersive experience, participants may consider running:

  guix environment --ad-hoc xsnow -- xsnow

Ludo’.