The reason why I'm asking is that noting that the "problem" exists here in Ubuntu bug tracker as a package bug seems to be an act of questionable usefulness to me.
I'm (as an upstream developer) subscribed to Ubuntu package bug mail to try to get distro-specific / packaging / unforwarded bugs on our radar, and it doesn't help me to get duplicate reports which have already been forwarded upstream. Otherwise, nobody from Ubuntu has looked into this stuff for a decade and helped upstream out, so I'm not holding my breath to see this happening anytime soon.
Therefore, I would prefer if this tracker was used to track package bugs and not to duplicate upstream feature requests.
The reason why I'm asking is that noting that the "problem" exists here in Ubuntu bug tracker as a package bug seems to be an act of questionable usefulness to me.
I'm (as an upstream developer) subscribed to Ubuntu package bug mail to try to get distro-specific / packaging / unforwarded bugs on our radar, and it doesn't help me to get duplicate reports which have already been forwarded upstream. Otherwise, nobody from Ubuntu has looked into this stuff for a decade and helped upstream out, so I'm not holding my breath to see this happening anytime soon.
Therefore, I would prefer if this tracker was used to track package bugs and not to duplicate upstream feature requests.