Page 2 of 9

Fedora Happiness Packets on CentOS 7

I’m writing this for future me. My default OS is Ubuntu so setting up the project on CentOS was new for me.

gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong –param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong –param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c _scandir.c -o build/temp.linux-x86_64-2.7/_scandir.o
unable to execute gcc: No such file or directory
error: command ‘gcc’ failed with exit status 1

yum install gcc

gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong –param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong –param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c _scandir.c -o build/temp.linux-x86_64-2.7/_scandir.o
_scandir.c:14:20: fatal error: Python.h: No such file or directory
#include
^
compilation terminated.
error: command ‘gcc’ failed with exit status 1

yum install python-devel

gcc -pthread -shared -Wl,-z,relro build/temp.linux-x86_64-2.7/Modules/2.x/readline.o readline/libreadline.a readline/libhistory.a -L/usr/lib64 -lncurses -lpython2.7 -o build/lib.linux-x86_64-2.7/gnureadline.so
gcc: error: readline/libreadline.a: No such file or directory
gcc: error: readline/libhistory.a: No such file or directory
error: command ‘gcc’ failed with exit status 1

yum install patch

gcc -pthread -shared -Wl,-z,relro build/temp.linux-x86_64-2.7/Modules/2.x/readline.o readline/libreadline.a readline/libhistory.a -L/usr/lib64 -lncurses -lpython2.7 -o build/lib.linux-x86_64-2.7/gnureadline.so
/usr/bin/ld: cannot find -lncurses
collect2: error: ld returned 1 exit status
error: command ‘gcc’ failed with exit status 1

yum install ncurses-devel

Getting the courses you want at UT Arlington

INCOMING INTERNATIONAL STUDENTS

Like I mentioned in my previous post What I wish I knew before I landed at UT Arlington your seniors are going to have the first pick of the courses nothing much you can do about that.

Get here early

International Orientation -> Departmental Orientation -> Pick classes!

You need to go in that order.

Pick the second last international orientation date (your dates shouldn’t clash with the departmental orientation).

So make sure you get here at least a week before your departmental orientation. Because you need to attend the International orientation and get your medical paperwork done before you can register for classes! I cannot stress this enough. You don’t want to be forced to take courses you don’t like (or those that don’t have much value). If you have prerequisites but you have already taken it in your undergrad, make sure you bring your mark sheets and your syllabus and waive it off.

bring your laptop

Before you attend the Departmental orientation pick the courses you want and add them to your cart. Bring your laptop along for the departmental orientation. As soon as your last hold is removed by the advisor. Open up your laptop and enroll yourself right then and there.

EVERYONE ELSE

Check the UTA calender for enrollment dates https://www.uta.edu/uta/acadcal

Get some coffee, your laptop (don’t forget to add the courses you want to the cart) and prepare to camp out in the library past midnight. You could do this from home but the computers in the library are a bit more reliable. If you do decide to use the libraries’ computer make sure you get there an hour early so you get a system (peak traffic the night before enrollment)

Try to stay logged into your MyMav account (a lot of people are going to be logging in so you might get kicked out). And keep trying to enroll yourself (Who knows you might get lucky?). Even if you get an email from the department saying enrollment starts at 7 AM in the morning, it’s probably going to open at Midnight. So don’t let your guard down!

Checklist for that conference

Grace Hopper Conference 2018

I got a scholarship to attend GHC 18 in Houston! 😀

So I thought I’d collect some general advice from the internet and checklist it.

Checklist:
  • Business Cards
  • Copies of your resume
  • Elevator pitch
  • Mint
  • List of companies you want to interview at and questions you might want to ask them
  • Comfortable shoes
  • Download the conference app
  • Get the career fair guide
  • Pen
  • A nice blazer
  • Thank you notes!
References

https://ghc.anitab.org/news/commentary-perspectives/how-to-make-the-most-of-ghc16/

https://code.likeagirl.io/tips-for-job-hunting-and-interviewing-at-the-grace-hopper-conference-4b5f5fb1d4a

https://ghc.anitab.org/community-blog-ghc/ghc15-tips-to-help-you-be-successful-at-the-career-fair/

GSoC update Week 1 and 2

Week 1:

Week 2 and 3:

OpenID Connect and Authenticating against Ipsilon

Step 1 – Get your credentials

You need to register your app with the OP https://iddev.fedorainfracloud.org/

I used https://github.com/puiterwijk/oidc-register for that.

pip install oidc-register

To register you need the provider, application, and redirect(callback) URLs

oidc-register https://iddev.fedorainfracloud.org/ https://127.0.0.1:8443 https://127.0.0.1:8443/oidc/callback/

Note: You can’t use http unless it’s with a localhost. 

After you do that you should have a client_secrets.json file in the same directory with the client secret and ID

Step 2 – Update your settings

For https://github.com/mozilla/mozilla-django-oidc it’s pretty straightforward. Update or add the OIDC_RP_CLIENT_ID and OIDC_RP_CLIENT_SECRET in the settings.py file or better yet add it as an environment variable. You don’t want to accidentally commit the client ID and secret to your github repository.

export OIDC_RP_CLIENT_ID='xxx'
export OIDC_RP_CLIENT_SECRET='xxx'

Don’t forget to include the Authorizaation, Token and User Info endpoints in your settings file

You might also need to change the signing algorithm to RS256 which requires the public key of the OP or its JWK endpoint https://id.fedoraproject.org/openidc/Jwks

References

https://docs.pagure.org/infra-docs/dev-guide/auth.html

https://fedoraproject.org/wiki/Infrastructure/Authentication

 

© 2018 Anna Philips

Theme by Anders NorénUp ↑