Re: gitlab migration
James Cloos composed on 2018-06-12 17:38 (UTC-0400): > Two comments: > BZ is superior to GL (or GH or the like). Strongly agree, especially for returning useful search results!!! > Mailing lists are vastly superior to any web-only Strongly agree!!! -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Two comments: BZ is superior to GL (or GH or the like). Mailing lists are vastly superior to any web-only crap. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
> "DS" == Daniel Stone writes: DS> No need to test; it's guaranteed to fail since we require Recaptcha DS> for login due to massive spam issues. Which is of course grossly unethical and malicious and should never be used by any site, under any circumstances. If some sort of captcha is ever desired, it always must be something which works with non-ecmacsipt, TUI browsers. A simple math question with a simple html text box for the answer is OK. Or a technical question specific to the given project. But never goog's malicious crap. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Mass bugzilla closing
To help get the bz backlog down, I'm mass-closing anything that hasn't been touched in over six years and isn't obviously still valid. Apologies for the spam, and we should all feel bad about just how many bugs that closes. - ajax ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
On 2018-06-12 01:35 PM, Daniel Stone wrote: > On 11 June 2018 at 11:33, Michel Dänzer wrote: >> On 2018-06-08 08:08 PM, Adam Jackson wrote: >>> I'd like us to start moving repos and bug tracking into gitlab. >>> Hopefully everyone's aware that gitlab exists and why fdo projects are >>> migrating to it. If not, the thread about Mesa's migration provides >>> some useful background: >>> >>> https://lists.x.org/archives/mesa-dev/2018-May/195634.html >>> >>> This should be mostly mechanical, except for moving some of the older >>> junk into the archive and deciding which drivers _not_ to move yet (I >>> imagine intel has some of its processes hooked up to bz, for example). >> >> As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating >> these to GitLab for Git and patch review. >> >> However, I'm not sure what to do about bugs/issues. My first thought was >> to allow creating new issues in GitLab and disable creating new reports >> in Bugzilla, but not to migrate existing reports from Bugzilla. However, >> it still happens fairly often that a report is initially filed against >> the Xorg drivers, even though it's actually an issue in the X server, >> Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to >> stick to Bugzilla until at least the X server and Mesa have moved to >> GitLab for issue tracking, to hopefully allow moving such misfiled issues. > > One thing some Mesa people said during that discussion is that they > like the ability to move issues between Mesa and the kernel, which > won't be possible if they're on split systems. So I probably wouldn't > hold my breath for that to be honest. Then I'd rather not use GitLab issues for these drivers at all either for the time being. The same argument applies to xserver as well, but I won't stand in the way of migrating that to GitLab issues. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Daniel Stone : > > Hi Alexander, > > On 12 June 2018 at 14:53, Alexander E. Patrakov wrote: > > Daniel Stone : > >> > That said, I could not even create an account with a noscript/xhtml basic > >> > browser (if you want to test that, install the famous noscript module > >> > with an > >> > empty "white list" in firefox or chromium, or use lynx or links or w3m). > >> > >> No need to test; it's guaranteed to fail since we require Recaptcha > >> for login due to massive spam issues. > > > > Have you tested whether Chinese or Russian users can login or sign up? > > Asking because Recaptcha was blocked for quite a long time by Russian > > authorities. > > We do have active users from both countries currently. Great, thanks for confirmation! -- Alexander E. Patrakov ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Hi Alexander, On 12 June 2018 at 14:53, Alexander E. Patrakov wrote: > Daniel Stone : >> > That said, I could not even create an account with a noscript/xhtml basic >> > browser (if you want to test that, install the famous noscript module with >> > an >> > empty "white list" in firefox or chromium, or use lynx or links or w3m). >> >> No need to test; it's guaranteed to fail since we require Recaptcha >> for login due to massive spam issues. > > Have you tested whether Chinese or Russian users can login or sign up? > Asking because Recaptcha was blocked for quite a long time by Russian > authorities. We do have active users from both countries currently. Cheers, Daniel ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Daniel Stone : > > Hi Sylvain, > > On 12 June 2018 at 13:38, wrote: > > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > >> GitLab has a pretty comprehensive and well-documented API which might > >> help if you don't want to use a web browser. There are also clients > >> like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI > >> interface. > > > > Those "web APIs" usually require the use of an heavy javascript browser for > > authentification or "app authorization". > > > > That said, I could not even create an account with a noscript/xhtml basic > > browser (if you want to test that, install the famous noscript module with > > an > > empty "white list" in firefox or chromium, or use lynx or links or w3m). > > No need to test; it's guaranteed to fail since we require Recaptcha > for login due to massive spam issues. Have you tested whether Chinese or Russian users can login or sign up? Asking because Recaptcha was blocked for quite a long time by Russian authorities. Cannot test the situation myself now, because I emigrated several months ago. -- Alexander E. Patrakov ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Hi Sylvain, On 12 June 2018 at 13:38, wrote: > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: >> GitLab has a pretty comprehensive and well-documented API which might >> help if you don't want to use a web browser. There are also clients >> like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI >> interface. > > Those "web APIs" usually require the use of an heavy javascript browser for > authentification or "app authorization". > > That said, I could not even create an account with a noscript/xhtml basic > browser (if you want to test that, install the famous noscript module with an > empty "white list" in firefox or chromium, or use lynx or links or w3m). No need to test; it's guaranteed to fail since we require Recaptcha for login due to massive spam issues. Cheers, Daniel ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Hi Michel, On 11 June 2018 at 11:33, Michel Dänzer wrote: > On 2018-06-08 08:08 PM, Adam Jackson wrote: >> I'd like us to start moving repos and bug tracking into gitlab. >> Hopefully everyone's aware that gitlab exists and why fdo projects are >> migrating to it. If not, the thread about Mesa's migration provides >> some useful background: >> >> https://lists.x.org/archives/mesa-dev/2018-May/195634.html >> >> This should be mostly mechanical, except for moving some of the older >> junk into the archive and deciding which drivers _not_ to move yet (I >> imagine intel has some of its processes hooked up to bz, for example). > > As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating > these to GitLab for Git and patch review. > > However, I'm not sure what to do about bugs/issues. My first thought was > to allow creating new issues in GitLab and disable creating new reports > in Bugzilla, but not to migrate existing reports from Bugzilla. However, > it still happens fairly often that a report is initially filed against > the Xorg drivers, even though it's actually an issue in the X server, > Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to > stick to Bugzilla until at least the X server and Mesa have moved to > GitLab for issue tracking, to hopefully allow moving such misfiled issues. One thing some Mesa people said during that discussion is that they like the ability to move issues between Mesa and the kernel, which won't be possible if they're on split systems. So I probably wouldn't hold my breath for that to be honest. Cheers, Daniel ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
Hi Sylvain, It looks like Mutt is mangling email addresses - I've fixed Michel's. On 11 June 2018 at 14:30, wrote: > On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: >> Adding the amd-gfx list, in cases somebody there has concerns or other >> feedback. > > For feedback: > I attempted a migration on gitlab of my repos but I was blocked because it's > not noscript/xhtml basic browser friendly. > > I was successfull with launchpad.net (which has now git support). > > I did not test if the issue system was noscript/xhtml basic friendly though. GitLab has a pretty comprehensive and well-documented API which might help if you don't want to use a web browser. There are also clients like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI interface. Cheers, Daniel ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: gitlab migration
On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: > Adding the amd-gfx list, in cases somebody there has concerns or other > feedback. For feedback: I attempted a migration on gitlab of my repos but I was blocked because it's not noscript/xhtml basic browser friendly. I was successfull with launchpad.net (which has now git support). I did not test if the issue system was noscript/xhtml basic friendly though. -- Sylvain ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH xserver] xfree86: Makefile shouldn't rely on superuser being named 'root'
On Mon, Jun 11, 2018 at 05:17:31PM -0400, Adam Jackson wrote:
> From: Michał Górny
>
> Change the 'chown' statement in Makefile.am to use the numeric UID
> of superuser instead of relying on the name 'root'.
>
> Bugzilla: https://bugs.freedesktop.org/27726
> Signed-off-by: Adam Jackson
> Signed-off-by: Michał Górny
> ---
Reviewed-by: Peter Hutterer
Cheers,
Peter
> hw/xfree86/Makefile.am | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/xfree86/Makefile.am b/hw/xfree86/Makefile.am
> index 57c8b8dd45..9aeaea1a66 100644
> --- a/hw/xfree86/Makefile.am
> +++ b/hw/xfree86/Makefile.am
> @@ -108,14 +108,14 @@ endif
> install-exec-hook:
> (cd $(DESTDIR)$(bindir) && rm -f X && $(LN_S) Xorg$(EXEEXT) X)
> if INSTALL_SETUID
> - chown root $(DESTDIR)$(bindir)/Xorg
> + chown 0 $(DESTDIR)$(bindir)/Xorg
> chmod u+s $(DESTDIR)$(bindir)/Xorg
> endif
> if SUID_WRAPPER
> $(MKDIR_P) $(DESTDIR)$(SUID_WRAPPER_DIR)
> mv $(DESTDIR)$(bindir)/Xorg $(DESTDIR)$(SUID_WRAPPER_DIR)/Xorg
> ${INSTALL} -m 755 Xorg.sh $(DESTDIR)$(bindir)/Xorg
> - -chown root $(DESTDIR)$(SUID_WRAPPER_DIR)/Xorg.wrap && chmod u+s
> $(DESTDIR)$(SUID_WRAPPER_DIR)/Xorg.wrap
> + -chown 0 $(DESTDIR)$(SUID_WRAPPER_DIR)/Xorg.wrap && chmod u+s
> $(DESTDIR)$(SUID_WRAPPER_DIR)/Xorg.wrap
> endif
>
> uninstall-local:
> --
> 2.17.0
>
> ___
> xorg-devel@lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: https://lists.x.org/mailman/listinfo/xorg-devel
>
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
