[Bug 1845966] Re: Conflicts between std::byte and byte

2019-11-29 Thread Launchpad Bug Tracker
[Expired for gcc-mingw-w64 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gcc-mingw-w64 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread KOLANICH
>it’s on SourceForge, I’m guessing it’s MinGW-w64, but it would be nice to know for sure. It is. >Which version of Ubuntu are you using? Have just migrated to eoan. But the issue was present in cosmic and disco too. >If you can attach the code which failed to build because of the conflict, >I

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread Stephen Kitt
Sorry for the tone, I am taking this seriously, and I realise this is probably very frustrating for you since I assume you’ve run into this while trying to get something done. If you can attach the code which failed to build because of the conflict, I’ll look into the current situation with GCC 8 a

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread Stephen Kitt
So when you say > but upstream maintainers think it is not a bug because "they shouldn't conflict" it’s really one active user with recent commits? Would you mind at least clarifying which project you’re talking about? Since it’s on SourceForge, I’m guessing it’s MinGW-w64, but it would be nice t

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread KOLANICH
>Could you provide a link to the upstream conversation? No. Their bug tracker is on SourceForge, which uses reCAPTCHA, so I cannot sign up (reCAPTCHA is extremily unfriendly to Firefox + privacy.resistFingerprinting users). So I have contacted one of the active users with recent commits and seemen

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread Ubuntu Foundations Team Bug Bot
The attachment "mingw.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, fo

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread Stephen Kitt
Also, what version of the package are you using? There’s no release of gcc 8.1.0 with MinGW-w64 in any supported release of the distributions I’m tracking... ** Changed in: gcc-mingw-w64 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of U

[Bug 1845966] Re: Conflicts between std::byte and byte

2019-09-30 Thread Stephen Kitt
Could you provide a link to the upstream conversation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845966 Title: Conflicts between std::byte and byte To manage notifications about this bug go to