Re: Bug triage report for 2021-04-19 (Monday Triage)

2021-04-19 Thread Utkarsh Gupta
Hello,

On Tue, Apr 20, 2021 at 5:28 AM Bryce Harrington
 wrote:
> Yes, this reporter doesn't like to use gitlab.com so appears to be
> filing their upstream problems with us.  I guess using us as a proxy?
> I looked at their concerns expressed in one of the other bugs but it
> doesn't really seem to involve us, and indeed is another thing they
> should be working with upstream directly if they want it resolved.

Aah, this also explains #1924618 and #1924622, which I reported in my
triage on Friday.


- u

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Bug triage report for 2021-04-19 (Monday Triage)

2021-04-19 Thread Bryce Harrington
On Tue, Apr 20, 2021 at 12:28:50AM +0100, Robie Basak wrote:
> Bugs last updated between 2021-04-16 (Friday) and 2021-04-18 (Sunday) 
> inclusive
> Date range identified as: "Monday triage"
> 
> LP: #1924609 - (New)[fetchmail]  - onion sites inaccessible 
> due to internal DNS lookup
> 
> I marked this Won't Fix as it's really a Wishlist upstream request.
> Interestingly, upstream fetchmail appears to be subscribed to bugs in
> Ubuntu and response to them. I saw some previous activity from this
> reporter as triaged by Utkarsh. Really their Wishlist requests should be
> going to upstream directly, and I think the Invalid/Won't Fix
> designation for the Ubuntu tasks is correct. I'd prefer to set the
> expectation that no action is to be expected from Ubuntu from what are
> really wishlist feature requests that belong upstream.

Yes, this reporter doesn't like to use gitlab.com so appears to be
filing their upstream problems with us.  I guess using us as a proxy?
I looked at their concerns expressed in one of the other bugs but it
doesn't really seem to involve us, and indeed is another thing they
should be working with upstream directly if they want it resolved.

So, I agree that is probably the best way to triage similar kinds of
bugs from this reporter.

Bryce

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Bug triage report for 2021-04-19 (Monday Triage)

2021-04-19 Thread Robie Basak
Bugs last updated between 2021-04-16 (Friday) and 2021-04-18 (Sunday) inclusive
Date range identified as: "Monday triage"

LP: #1924231 - (New)[qemu]   - Getting qemu: uncaught 
target signal 11 (Segmentation fault) when the installing libc-bin which wget 
depends on.

This was really a backport-to-Focal request for an existing resolved bug
in Launchpad, so I explained, marked it as a duplicate and added a Focal
task on the other bug. Without looking in detail it seemed potentially
non-trivial to backport, and the reporter hasn't identified the patch as
applying cleanly to Focal (rather it's just a request), so I didn't
treat it as "on a plate" and added it to our backlog only.

LP: #1924609 - (New)[fetchmail]  - onion sites inaccessible due 
to internal DNS lookup

I marked this Won't Fix as it's really a Wishlist upstream request.
Interestingly, upstream fetchmail appears to be subscribed to bugs in
Ubuntu and response to them. I saw some previous activity from this
reporter as triaged by Utkarsh. Really their Wishlist requests should be
going to upstream directly, and I think the Invalid/Won't Fix
designation for the Ubuntu tasks is correct. I'd prefer to set the
expectation that no action is to be expected from Ubuntu from what are
really wishlist feature requests that belong upstream.

Most of the other bugs were either in progress by Ubuntu developers or
the usual not proper bug reports (standard template reply ->
Incomplete).

Robie


signature.asc
Description: PGP signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam