Are you already familiar with the basic concepts of the specfile library? Then welcome to a collection of some slightly more advanced topics that you could find useful. If you're not that familiar and would like to start with something easier, you can take a look at Introduction to specfile library.
We are reaching the end of the year and it’s a good time to look back at the Packit highlights of this year. And it was a year!
After 105 minor releases we are almost ready to announce our first major release, Packit 1.0.0!
This term has been thrown around a bit in issues here and there relating to the dashboard and people usually get confused, and rightfully so! Lets dive in and see what Project Mycorrhiza is and why we chose this name.
Photo by Malene Thyssen - Own work, CC BY-SA 3.0, Link
Were you annoyed by Packit creating divergent branches in your package's dist-git repository? You'll be happy to know that Packit now supports a new dist_git_branches syntax that enables fast-forwarding commits between branches.
We are happy to announce that support for non-git upstreams in the pull_from_upstream job is here!
This enhancement simplifies configuration by removing the need to define upstream_project_url,
opening the door for more use cases, while also simplifying the onboarding in general.
It’s been a month since two Packit members (Laura and František) attended Flock, the annual Fedora conference, in Rochester. Let’s see some highlights from our journey There and Back Again. Sadly the travel there wasn’t as expected at all, but luckily the tornadoes did not stop us and we both made it to Rochester.
We are excited to announce a new experimental feature in our service: the integration of Static Application Security Testing (SAST) using OpenScanHub.
OpenScanHub is a service that runs various static analyzers on RPM packages - by default Cppcheck,
ShellCheck and the static analyzers embedded in GCC.
Let's have a look at the details of the prototype!
Last month, we had the pleasure of engaging with a dynamic audience during our interactive talk on changelogs at the DevConf in Brno, Czech Republic. In case you missed it, you can watch the recording here. Throughout the session, we explored various aspects of changelog usage, including their content, format, and the potential for automation. By asking a series of questions to the attendees, we gathered insights and opinions that highlighted both common practices and divergent viewpoints within the community. In this follow-up article, we aim to summarise the key findings from our discussion, analyse the trends and preferences that emerged, and offer our reflections on the role of changelogs in software development.
The first part of June is usually quite busy for our team. Why? The last couple of years, this has been a time of DevConf.CZ conference. (The unpredictable January had been changed into a more pleasant June.) Even though the conference itself is important, it’s used as an opportunity for various people from around the globe to come to Brno and thanks to that, a lot is happening also during the days around. For the Packit team, it’s a nice opportunity to have the whole team together in one place – we can do some fun teambuilding (like canoeing this year) but also discuss any technical topics or meet our users and realise how are the real people behind all the nicknames. This time we also prepared something for them:
