Re: config fragments clean up

2013-07-01 Thread Jon Medhurst (Tixy)
On Mon, 2013-06-24 at 14:41 +0300, Fathi Boudra wrote:
> Hi,
> 
> There's a few warning that nobody noticed or cared until now:
> [...]
> Value requested for CONFIG_OABI_COMPAT not in final .config
> Requested value:  # CONFIG_OABI_COMPAT is not set
> Actual value:
> 
> Value requested for CONFIG_MTD_CHAR not in final .config
> Requested value:  CONFIG_MTD_CHAR=y
> Actual value:
> 
> Value requested for CONFIG_ENABLE_DEFAULT_TRACERS not in final .config
> Requested value:  CONFIG_ENABLE_DEFAULT_TRACERS=y
> Actual value:
> [...]
> 
> MTD_CHAR doesn't exist anymore.
> ENABLE_DEFAULT_TRACERS depends on !GENERIC_TRACER

That option is the minimum required for Gator, but we now have more
trace configs enabled which superced the minimal generic traces, so if
they are staying, then we can drop the default trace option.

> 
> Is there any objection to drop both options from linaro-base.conf?
> I'm not sure what to do with OABI_COMPAT.

I disabled that [1] because it was crashing our kernels when doing ARM
builds, not sure what the current state of the kernel is. It's an
obscure option and I can't imagine that many people actually have it
enabled, so could well still be broken in the mainline kernel.
Irrespective of whether it crashes, do we actually want to have support
for non AEBI user side code? Also, from the help text "This option adds
a tiny overhead to all syscalls and produces a slightly larger kernel."

[1] 
https://git.linaro.org/gitweb?p=kernel/configs.git;a=commit;h=46164b8909c93dc64a4fccd0cf93e5327265a50d

-- 
Tixy


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [ANN] android-build.linaro.org upgrade to Linaro Login Service - complete

2013-07-01 Thread Paul Sokolovsky
Hello Bero,

On Sat, 29 Jun 2013 12:32:05 +0200
Bernhard Rosenkränzer  wrote:

> Hi,
> this breaks things badly for me: The login form is limited to 30
> characters, but bernhard.rosenkran...@linaro.org is 32.
> Even after injecting
> "document.getElementById("id_username").maxLength=35" into the login
> page with a JS debugger, the login fails (probably because the 30
> character limit is not just imposed by the form at random -
> username/permission mappings stored in a sql field limited to 30
> chars?) (Yes, the proper fix would be getting me a shorter name ;) I
> don't have the right permissions to do that though ;) )

Sorry about this, Django's default username length is indeed too
restrictive. I updated it and verified that both DB and form now has
bigger limit (255). Can you please verify it works ok for you?

(Tracked as 
https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1196514 )

> 
> ttyl
> bero
> 
> 
> 
> On 27 June 2013 19:35, Paul Sokolovsky 
> wrote:
> 
> > Hello,
> >
> > After couple of iterations, android-build.linaro.org was updated to
> > authenticate against Linaro Login system. Please use your
> > login.linaro.org username (with @linaro.org suffix) and password to
> > login from now on. Personal jobs were also renamed to have
> > firstname.lastname prefix instead of Launchpad username. If you
> > cannot see your jobs, please contact me to check their state.
> >
> > Below is interim progress report for completeness.
> >
> >
> > Thanks,
> > Paul
> >
> >
> >
> >
> > Begin forwarded message:
> >
> > Date: Wed, 26 Jun 2013 22:43:07 +0300
> > From: Paul Sokolovsky 
> > To: Paul Sokolovsky 
> > Cc: linaro-android , Infrastructure
> > , Linaro Validation
> > , Philip Colmer
> >  Subject: Re: [ANN]
> > android-build.linaro.org upgrade to Linaro Login Service
> >
> >
> > Hello,
> >
> > On Wed, 26 Jun 2013 15:46:50 +0300
> > Paul Sokolovsky  wrote:
> >
> > > Hello,
> > >
> > > With Android releases out, I'd like to proceed with switchover of
> > > Android Build frontend authenticaton to Linaro Login. Estimated
> > > downtime is 2hrs. To minimize impact, I'm scheduling this for
> > > later evening UTC (around 8pm UTC). Let me know if you need
> > > access to a-b at that time (otherwise, upgrade is OKed by Vishal).
> >
> > Upgrade went well, except that now it's not possible to create
> > personal builds. That's because login username is used to form
> > created job name, and with Linaro Login, username is
> > first.l...@linaro.org - that's not valid as part of job name, and
> > besides that, it's too long. Even if I adhocly remapped it to
> > first-last, it's still too long, and still would required boring
> > renaming of existing jobs.
> >
> > Atlassian Crowd supports login aliases, Philip mentioned that it's
> > possible to create one, but I skipped doing that just for me, hoping
> > that it would be offered for all folks as part of git migration or
> > something, but that didn't happen. Well, I guess it's time to raise
> > that request now - going submit ITS ticket for this.
> >
> >
> > --
> > Best Regards,
> > Paul
> >
> > Linaro.org | Open source software for ARM SoCs
> > Follow Linaro: http://www.facebook.com/pages/Linaro
> > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
> >
> >
> > --
> > Best Regards,
> > Paul
> >
> > Linaro.org | Open source software for ARM SoCs
> > Follow Linaro: http://www.facebook.com/pages/Linaro
> > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
> >
> > ___
> > linaro-android mailing list
> > linaro-andr...@lists.linaro.org
> > http://lists.linaro.org/mailman/listinfo/linaro-android
> >



-- 
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev