Blogs

This article is a summary of all the changes made on Automated Gentoo System Updater project during week 8 of GSoC. Project is hosted on GitHub, blog post can be also found on Gentoo Blogs. Progress on Week 8 Currently, the updater supports two methods of notifications: IRC bot and email. The IRC bot was built using Python’s sockets library with SSL support. Although functional, it remains quite basic and encounters issues with sending out the report properly in approximately 20% of cases....

This article is a summary of all the changes made on Automated Gentoo System Updater project during weeks 6 and 7 of GSoC. Project is hosted on GitHub, blog post can be also found on Gentoo Blogs. Progress on Weeks 6 + 7 These 2 weeks were spent on the parser and the reporter. During this time, I’ve added many features to it, but there are still much more things left to be done....

This article is a summary of all the changes made on Automated Gentoo System Updater project during week 5 of GSoC. Project is hosted on GitHub, blog post can be also found on Gentoo Blogs. Progress on Week 5 Week started off by receiving some feedback from the community in the forums. Here are some nice ideas that community have suggested to implement: Fallback to the latest version of the package if an error is encountered during an update; Add an option to control Portage niceness; Estimate update time; Notify users about obsolete USE flags; Think of a way to make updater work on binpkg servers....

This article is a summary of all the changes made on Automated Gentoo System Updater project during week 4 of GSoC. Project is hosted on Github, blog post can be also found on Gentoo Blogs. Progress on Week 4 Started the week by discovering that my updates to ebuild were not accepted in the GURU overlay. The issue arose due to a misuse of USE flags feature in the ebuild. Maintainers of GURU (big thanks to antecrescent!...

Introduction gentoo_update (Github repo) is a tool that automatically updates Gentoo Linux. Motivation Gentoo Linux gives users maximum flexibility and control over the system. A great example of this is the OS upgrade process. Users have a large selection of different command utilities and a bunch of configuration options to choose from to tailor the upgrade process to their needs. Here is the list of some tools that are commonly used during an upgrade:...

This article is a summary of all the changes made on Automated Gentoo System Updater project during week 3 of GSoC. Project is hosted on Github, blog post can be also found on Gentoo Blogs Progress on Week 3 gentoo_update finally received some Github stars! It also has received 2 issues (#7 and #8). In #7 someone suggested to remove update.sh from being installed in the PATH, and only expose gentoo-update as entry point....

This article is a summary of all the changes made on Automated Gentoo System Updater project during week 2 of GSoC. Project is hosted on Github Progress on Week 2 This week was all about packaging and testing. The updater is still in its infancy, but it’s much better to package everything nicely right away and not think about this in the future. I kicked things off by bundling all the code into one directory and set it up as a Python module....

This article is a summary of all the changes made on Automated Gentoo System Updater project during week 1 of GSoC. Project is hosted on Github Progress on Week 1 The most basic version of the updater program is ready. By default it only installs security patches from GLSA using glsa-check, but it also allows users to update @world with their custom update flags. Additionally, after an update users can choose to:...

In this article I want to share my experience in applying to Google Summer of Code 2023 (GSoC). I was lucky enough to get accepted and I hope that this article will help someone in their future applications. Disclaimer: This article is not a guide on how to get accepted, it’s just my journey and my thoughts on the process. The outcome depends on your skills, organization, the project idea, Google and most importantly - luck....

Consider a large inventory file full of hosts, some of them only have private IP addresses, but some of them have public IPs as well. The goal is to identify which hosts have a public IP and print it in a debug message. The process involves running a playbook with a custom filter plugin to examine every host. If a public IP exists on a host, the print a debug message to identify the host....