Search
1000 results for “openela”
-
#OpenELA has automated its process so that new #opensource source code is available just days after each release of new versions of #RHEL.
How fast? ones for RHEL 9.4 and RHEL 8.10 are already out
Can't wait for #RedHat 's response
https://thenewstack.io/openela-liberates-red-hat-enterprise-linux-source-code/
@TheNewStack @sjvn @openela #FOSS -
@openela launches automated process to make new enterprise Linux sources available just days after new RHEL releases https://www.admin-magazine.com/News/OpenELA-Automates-Linux-Source-Access
#EnterpriseLinux #RHEL #Linux #ISV #IHV -
@openela launches automated process to make new enterprise Linux sources available just days after new RHEL releases https://www.admin-magazine.com/News/OpenELA-Automates-Linux-Source-Access
#EnterpriseLinux #RHEL #Linux #ISV #IHV -
@openela launches automated process to make new enterprise Linux sources available just days after new RHEL releases https://www.admin-magazine.com/News/OpenELA-Automates-Linux-Source-Access
#EnterpriseLinux #RHEL #Linux #ISV #IHV -
@openela launches automated process to make new enterprise Linux sources available just days after new RHEL releases https://www.admin-magazine.com/News/OpenELA-Automates-Linux-Source-Access
#EnterpriseLinux #RHEL #Linux #ISV #IHV -
@openela launches automated process to make new enterprise Linux sources available just days after new RHEL releases https://www.admin-magazine.com/News/OpenELA-Automates-Linux-Source-Access
#EnterpriseLinux #RHEL #Linux #ISV #IHV -
Open Enterprise Linux Association (OpenELA) launched a swift automation process for delivering Linux sources. Here's more on that.
https://linuxiac.com/openela-launches-rapid-delivery-of-enterprise-linux-sources/ -
It's pretty neat how much simple flexible tools can be extended. I threw together a few Bash scripts to lookup dependencies for a package, get the names of their sources and auto import them. Oela Importer hasn't been changed at all in order to do this. The scripts are also smart enough not to import a package if it already exists in koji.
-
Documentation for Oela Importer has been written. Oela Box tools are also automatically installed during provisioning now.
https://github.com/maxbyte9p/oelabox/blob/main/docs/topics/operation-Tools.md#oelaimporter
-
Oela Importer has now been redesigned and integrated with Oela Box. There's a few usage examples in the README. The README also explains some hurdles that need to be gotten around. I've also added some pretty neat features such as specifying a slice of repositories to import also called a "chunk".
https://github.com/maxbyte9p/oelabox/blob/main/tools/oelabox-koji/README.md
-
OpenELA maintient le noyau Linux 4.14 en vie.
Le projet OpenELA va fournir aux développeurs une plateforme permettant de collaborer à la maintenance du noyau Linux 4.14, malgré la fin du support communautaire en janvier dernier.
Nous vous en avons déjà parlé à de nombreuses reprises : le OpenELA rassemble Oracle, CIQ et SUSE autour d’un projet de socle commun.#OpenELA #Linuxhttps://lsdm.live/modules/news/article.php?storyid=4995
-
Oela Importer now has a regex mode. Regex mode is disabled by default, but can be enabled using the '-r' flag. I also made the output pretty too.
Also I keep forgetting to announce this. Oela Box now supports Oracle Linux 9.3 as a host!
-
I've decided to redesign Oela Importer into a much simpler tool which can be used in Bash scripts. The experimentation I did with parsing gave me the idea to possibly allow regex to be used to match branches against. Theoretically this design will be more flexible and powerful than the last because of its simplicity.
Development notes can be found on this GitHub issue.
-
The new directory tree structure has been put into place for Oela Box. Slight performance improvements have been gained from doing some tweaking to playbooks. Docs have been updated. Thorough QA testing has also been done to ensure everything is working correctly.
-
A much nicer directory tree is being put into place for Oela Box. This is just a snippet of it. A majority of the Ansible playbooks and task files have been modified to clean up any cruft. Ansible playbooks prefixed with "role" have been removed and integrated with the provisioning playbooks.
The new tree structure is much more organized than the last and allows greater flexibility compared to the old one.
-
ICYMI, the OpenELA source repos are ready for community EL use. As you work with them, remember to document your progress - and check out our contribution guide! Perfection not required, we can help. https://github.com/openela/openela-documentation/blob/main/CONTRIBUTING.md #yournameinlights #resumebuilder
-
🐧 Entdecke #RockyLinux mit Philippe Schmid von Puzzle ITC! Erfahre, warum dieser bug-for-bug kompatible Klon von Red Hat Enterprise Linux und Nachfolger von @centos Linux so begeistert! 🌟
Philippe beleuchtet die starke #Community, die Zukunft von Rocky Linux und die Rolle von #Oracle, #SUSE, #CIQ in der #openela 🚀
Puzzle ITC ist strategischer Partner des amerikanischen Unternehmens CIQ und fungiert als Reseller- und Distributionspartner für Rocky Linux in Europa.
-
User documentation repository created by @openela https://www.admin-magazine.com/News/OpenELA-Creates-User-Documentation-Repository #OpenELA #EnterpriseLinux #CIQ #Oracle #SUSE #documentation #repository
-
#OpenELA Publishes Initial Source Code For Building #RHEL Derivatives
#CIQ (#RockyLinux), #SUSE, and #Oracle decided to form the Open Enterprise #Linux association (OpenELA) to collaborate around the development of distributions with compatibility against #RedHat Enterprise Linux and ensuring open and free access to EL source code. Today they are announcing initial #sourcecode available for their #RHEL8 and #RHEL9
https://www.phoronix.com/news/OpenELA-Initial-Source-Code -
What was the first computer you had, and what was the first thing you did with it? #storytime #rememberwhen #openela
-
I got the OpenELA sed to build in koji after changing the source link in the spec file and creating the source rpm.
-
#OracleLinux 10.0 has been released (#Oracle / #OpenEnterpriseLinuxAssociation / #OpenELA / #RedHat / #EnterpriseLinux / #RHEL / #RedHatEnterpriseLinux / #IBM / #CentOS / #Fedora / #Linux) https://oracle.com/linux/
-
#RockyLinux 10.0 has been released (#RockyEnterpriseSoftwareFoundation / #RESF / #CIQ / #OpenEnterpriseLinuxAssociation / #OpenELA / #RedHat / #EnterpriseLinux / #RHEL / #RedHatEnterpriseLinux / #IBM / #CentOS / #Fedora / #Linux) https://rockylinux.org/
-
#RockyLinux 9.6 has been released (#RockyEnterpriseSoftwareFoundation / #RESF / #CIQ / #OpenEnterpriseLinuxAssociation / #OpenELA / #RedHat / #EnterpriseLinux / #RHEL / #RedHatEnterpriseLinux / #IBM / #CentOS / #Fedora / #Linux) https://rockylinux.org/
-
#OracleLinux 9.6 has been released (#Oracle / #OpenEnterpriseLinuxAssociation / #OpenELA / #RedHat / #EnterpriseLinux / #RHEL / #RedHatEnterpriseLinux / #IBM / #CentOS / #Fedora / #Linux) https://oracle.com/linux/
-
#OracleLinux 9.5 has been released (#Oracle / #OpenEnterpriseLinuxAssociation / #OpenELA / #RedHatEnterpriseLinux / #IBM / #CentOS / #Fedora / #Linux) https://oracle.com/linux/
-
#RockyLinux 9.5 has been released (#RockyEnterpriseSoftwareFoundation / #RESF / #CIQ / #OpenEnterpriseLinuxAssociation / #OpenELA / #RedHat / #EnterpriseLinux / #RHEL / #RedHatEnterpriseLinux / #IBM / #CentOS / #Fedora / #Linux) https://rockylinux.org/
-
I started messing with Koji a bit again. I've been having a weird issue I can't seem to track down where if I build coreutils I can't build anything else. For whatever reason Koji couldn't find the package despite it being there. This is the sole reason why I decided to take a break from Oela Box for a while. Koji just stopped working correctly one day without any changes to its setup or Oela Box.
I decided to start doing some experimenting. I want to slim down EL development tools to make them a little easier to work with and at the same time hopefully make them more powerful.
Right now I'm getting myself familiar with some of Mock's other features. First I'm learning how building from SCM works in Mock. It's a little tricky and works quite differently from how Koji does it, but I find it fairly interesting.
Next I want to see if I can simulate Koji's tagging system by having a local repository that gets checked for package dependencies first.
-
So far I have a way to collect metadata on an OpenELA repository then cache it for later use. The caching is for minimizing the amount of Github API calls over a period of time. The data collected on a repository consists of: repo name, clone url, ssh url, branches, and tags. Just enough data to be useful and not cumbersome.
