Improvements To RPM Lint Results and Reviewing Submit Requests

In this update, we’re introducing two improvements that make reviewing RPM lint results and Submit Requests easier: a dedicated view for RPM lint results, and a clearer, more helpful display of build statuses in Submit Requests.

We started the redesign of the request workflow in August 2022. Then, in September 2022, we focused on the support of multi-action submit requests. We continued in October 2022 with improvements regarding the Build Results tab and superseded conversations, and we presented build results with a pinch of salt in November 2022. In January 2023, we worked on facilitating the review process. In February 2023 we enhanced the review process with comments on changes. Later, in April 2023, we focused on improving the comments on changes and supporting new types of actions. In June 2023 we worked on maintenance action types. In July 2023 we introduced Set Bugowner action and diff comments for non-beta users. In September 2023 we focused on Build Results Summary Gets Into Shape. Later 2023, in November, we added the Build Status Refresh and Other Insights on Our Request Page. The year 2024 started with Revamping the Request Build Status Page and Introducing the Dark Mode. We continued in February with Build Results Summary Chart Links to Build Results Overview and in April with Improvements On the Redesigned Request Page. In 2025 we worked again on the Request Page by improving UI/UX aspects

The request redesign is part of the beta program.

A New Place For RPM Lints

Previously we were showing the RPM lint results in a small box next to the build results, which had the unfortunate outcome of cramming dense logs into a very small area, and as a tab in the Submit Request, with no connection to a specific build result.

We now show the RPM lint results on a dedicated page under a new ‘RPM Lint’ tab within the package show page. This has the benefit of having a whole page to render the RPM lint. Then, on a Submit Request, we link to this tab from each specific build result, sending you directly to the relevant RPM Lint. No need to find your way through the repository and architecture dropdown selectors.

Build or Not to Build? That’s the Question.

To find out faster if a Submit Request builds or not we’ve changed how we render the build results when a Submit Request is open. The first build results that you’ll find, are the ones from the repositories of the target package, because if that’s not building it’s very likely the Submit Request will not be accepted, right?

How To Give Us Feedback

There are two ways to reach us:

• On GitHub, by opening an issue and / or commenting on an already opened issue.
• On IRC, by talking directly to us. We are in the channel #opensuse-buildservice on Libera.Chat.

Please note that we favor GitHub to gather feedback as it allows us to easily keep track of the discussions.