Fedora

Mukti 2014 is the annual national level technical symposium on Free and Open Source Software of the GNU/Linux Users’ Group NIT Durgapur held from 31st January - 2nd February 2014. I’ve been attending Mukti for last four years. Unlike, the previous years when i usually attended Mukti as a student participant, this year I attended Mukti as a guest speaker. Day 0 (30th January 2014) After a hectic travel from Bangalore to Durgapur via Kolkata. TMC called of the largest Brigade Rally in Kolkata on the very day. The bus i was travelling from Kolkata Airport to Howrah station dropped me at an unknown location. I somehow dragged myself and my luggage to station. The condition at the station was worse, packed compartments including the reserved ones and people fighting for their seats. After a big quarrel, I somehow got my seat. ...

I have been involved in Durgapur Linux User’s Group for around last five years. I have been contributing to various open source projects quite sometime. The primary reason on why I contribute to open source is the feeling, the enjoyment when you send a patch or a PR to a open source project. It makes you happy when millions of people use your few lines of code in day to day life. ...

Lot of things to do! Lot of things to do! Lot of things to do! This was continuously revovlving around my head for last 2 weeks. I had to deploy the work i had done on staging instance and test it. But wait! I had never written a setup.py before, never made a RPM package before. While in college, I had a fascination toward RPM packaging as most of my college seniors had created a RPM package sometime or other. During Mukti 2011, I had attended a RPM packaging workshop by Rahul Sundaram(mether), so i had the idea of how to package a RPM. ...

There has been a lot of changes since I last posted my blog. Darkserver’s command line dashboard now supports the secondary architecture. You can easily shutdown the darkproducer of specifying which architecture to shutdown. .. code:: dark> shutdown darkproducer arch The support for multiple buildqueues was removed. After a rigorous testing on my laptop, i pushed the code to the dev instance that was assigned to me. But, a mysterious error happened, nor the pid or the daemon of darkproducer was getting created. Due to which the complete project came to a halt. Later, it was figured out that i was passing the config(—config) argument as a relative path of the conf file, rather than the absolute path which created all this trouble. So, the proper way to start the darkproducer is: ...

I am currently doing some manual testing of my code, and it proved to be vital. It helped me figure out a lot of bugs. One of seemed weird to me in the beginning: The get here returned an error. .. code:: Method Not Allowed This is an XML-RPC server. Only POST requests are accepted. The project required a heavy amount of download, so my mentor gave me a dev instance to test out my code, all seemed to be fine, with the code properly working on local machine. But on the dev instance a major bug surfaced, all the architecture with referring to the same key. So, currently i started working on implementing different darkproducer-ids for different darkproducers.Also, I need to get started with a long-term bug, my mentor pointed me in the shutdown functionality of darkserver. ...