https://bugs.devuan.org/Reporting.html
remember that bugs in unforked packages (those that Devuan uses directly from Debian) should usually be reported to Debian's BTS unless you think you have found a Devuan specific problem.
Sometimes it is necessary to send a copy of a bug report to somewhere else besides the mailing list and the package maintainer, which is where they are normally sent.You could do this by CC'ing your bug report to the other address(es), but then the other copies would not have the bug report number put in the Reply-To field and the Subject line. When the recipients reply they will probably preserve the submit@??? entry in the header and have their message filed as a new bug report. This leads to many duplicated reports. The right way to do this is to use the X-Debbugs-CC header. This will cause the bug tracking system to send a copy of your report to the address(es) in the X-Debbugs-CC line as well as to any mailing list.
In this case, Devuan's "dialog" version (1.3-20201126-1) is the Debian unforked package, so it should be sent to Debian (view
https://www.debian.org/Bugs/Reporting ). Optionally you can CCed the upstream author, although usually the package maintainer informs the upstream author.
Best regards.
En sábado, 27 de noviembre de 2021 19:14:39 CET, viverna via Dng <dng@???> escribió:
I have found a bug in dialog.
How do I report a bug? Devuan, debian or to the author of the software?
--
_________
< Viverna >
---------
\ ^ /^
\ / \ // \
\ |\___/| / \// .\
\ /0 0 \__ / // | \ \ *----*
/ / \/_/ // | \ \ \ |
@_^_@`/ \/_ // | \ \ \/\ \
//_^_/ \/_ // | \ \ \ \
( //) | \/// | \ \ | |
( / /) | // | \ _\ | /
( // /) | ; -. | _ _\.-~ / /
(( / / )) | _ *-.|.-~-. .~ ~
(( // / )) \ / ~-. _ .-~ /
(( /// )) `. } { /
(( / )) .----~-.\ \-` .~
///.----..< \ _ -~
///-._ _ _ _ _ _ _{^ - - - - ~
_______________________________________________
Dng mailing list
Dng@???
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng