Hi Nilesh,
For now, I have just done that for you.
Thank you very much!
Control: forwarded -1 https://github.com/kovidgoyal/kitty/
issues/10174
Since this appears to be an issue with the upstream code and not the
Debian> package, please consider to forward reports like this to the
upstream bug tracker instead of here.
Debian specifically asks not to submit bugs upstream, see
https://www.debian.org/Bugs/Reporting
> Don't file bugs upstream
>
> If you file a bug in Debian, don't send a copy to the upstream
> software maintainers yourself to start with, as it is possible that
> the bug exists only in Debian. If necessary, the maintainer of the
> package will forward the bug upstream, or ask you to do so after
> they've checked that it isn't Debian-specific.
I don't run kitty from source, so I'm not really inclined to submit bugs
upstream for a Debian package.
In addition to this, it isn't really a nice way for users to having to
understand which package requires you to submit upstream vs to Debian,
eg, zsh just forwards the bugs upstream. One would need to look into
salsa to see if custom patches are applied for Debian and exclude or
include those before building from source in order to confirm the bug is
indeed upstream.
Debian also doesn't always track upstreams versions, it may be behind,
filing bugs upstream may cause annoyances with upstream maintainers,
xscreensaver is the most notable example of this.
I therefor will continue to use reportbug to submit bugs against
packages in Debian, you as a package maintainer should also know there
is a bug in testing/unstable and not just upstream.
I hope you can understand my reasoning in this. Thanks again for filing
the bug upstream.
Cheers,
Wesley
--
Wesley Schwengle
E: [email protected]
