Introducing modulemd-tools

Hello, I would like to let you know, that we started a project called modulemd-tools. It is a collection of small tools for parsing and generating modulemd YAML files. At this moment, it provides two scripts - one for generating a modulemd YAML file based on an existing YUM repository, the other

Vim :Gbrowse support for pagure

Hello, I don't know how many of you are Vim users and what fraction of those use plugins. Anyway, there is a great, well-known plugin called vim-fugitive (by notorious Tim Pope), that provides a lot of cool features. My favorite one is probably `:Gbrowse` command, which opens the current file, lin

Temporarily using `best=False' for EPEL-8 builds in Copr

Hello, currently, there is a problem with building EPEL-8 packages because of DNF bugs regarding modularity (see RHBZ 1758459). The only known workaround is to use DNF with `best=False'. Even though it is something you don't really want to use longterm, we are patching mock configs epel-8-* chroo

Re: Temporarily using `best=False' for EPEL-8 builds in Copr

> These bugs exist in RHEL 8 as well as CentOS 8 based environments. Why do you > think that modularity will *ever* work this way? I don't know whether this question was aimed directly to me, but if so ... I am sorry, I can't help you here. You will probably need to talk directly to the modularit

Tito 0.6.12 release

Hello, I am happy to announce that after two years since the last tito [1] release, the 0.6.12 is finally out! See release notes [2] This very moment, updates were submitted to bodhi [3], feel free to try them. [1] https://github.com/dgoodwin/tito/ [2] https://github.com/dgoodwin/tito/releases

Outage: Upgrade of Copr servers - 2019-07-18 05:00 UTC

There will be an outage starting at 2019-07-18 05:00 UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2019-07-18 05:00 UTC' Reason for outage: Upgrade of Copr servers to Fedora 30. Affected Se

Re: Outage: Upgrade of Copr servers - 2019-07-18 05:00 UTC

The outage is done, all our servers are now running Fedora 30 and everything should work again. We apologize for any inconvenience caused by the outage. Jakub On Tue, Jul 16, 2019 at 10:03 PM Jakub Kadlcik wrote: > > There will be an outage starting at 2019-07-18 05:00 UTC, which wil

Disabling Fedora 28 chroots in Copr

Hello, we have just disabled Fedora 28 chroots in Copr. According to the Fedora wiki [1], Fedora 28 reached the end of its life on 2019-05-28 and therefore we are disabling it in Copr. That effectively means that from this moment, it is no longer possible to submit builds for the following chroo

Backend storage clean-up

Hello, we have decided that it is a time to go through Copr backend data and clean it up a little. Due to several bugs forgetting to remove backend data after removing their records from the database, _temporarily_ backing up some folder here and there, etc, we ended up with a lot of unknown data,

Re: Copr Build System - review of 2019 and vote for features in 2020

> For what it's worth, I never got the promised notification for my Coprs. > The legacy chroots are just gone forever with no warning whatsoever. I am truly sorry to hear that. I am afraid, that there is no way to recover those data. Thank you for reporting it though, I have investigated the issue

Re: Highlights from the latest Copr release

Hello Kevin, thank you for your feedback. > This is still inherently flawed and unsafe because you have absolutely no > way of guaranteeing that the notification mail actually reached the > maintainer, only that it has been sent. E-mail is not a certified delivery > mechanism. True, that's why we

Disabling Fedora 29 chroots in Copr

Hello, we have just disabled Fedora 29 chroots in Copr. According to the Fedora wiki [1], Fedora 29 reached the end of its life on 2019-11-30 and therefore we are disabling it in Copr. That effectively means that from this moment, it is no longer possible to submit builds for the following chroo

Re: Disabling Fedora 29 chroots in Copr

I would like to ask you, can anyone with non Red Hat email confirm, that they get the notifications? The subject is > [Copr] upcoming deletion of outdated chroots in your projects Thank you, Jakub On Mon, Feb 17, 2020 at 12:21 AM Jakub Kadlcik wrote: > > Hello, > > we hav

Re: Disabling Fedora 29 chroots in Copr

Thank you guys! Jakub On Tue, Feb 18, 2020 at 12:42 PM Frantisek Zatloukal wrote: > > Got one about a day ago :) > > On Tue, Feb 18, 2020 at 12:17 PM Jakub Kadlcik wrote: >> >> I would like to ask you, can anyone with non Red Hat email confirm, >> that they get

Outage: Migration of Copr servers - 2020-02-23 06:00 UTC

There will be an outage starting at 2020-02-23 06:00 UTC, which will last approximately 7 hours (but can take more if something goes wrong). To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2020-02-23 06:00 UTC' Reason for outage: Moving

Re: Outage: Migration of Copr servers - 2020-02-23 06:00 UTC

F32 chroot (for > those projects that follow fedora branching). So the builds are going to > be copied even though they can be incompatible. > > It might be a good idea to not build against fedora-rawhide* chroots for now, > till the next week. > > Thanks for understanding,

M-x browse-at-remote support for Pagure

Hello, recently I've announced on this mailing list, that I implemented Pagure support for :Gbrowse command in Vim. If you are not familiar with this feature, it allows you to open a current file or line selection on a remote hosting platform such as GitHub, GitLab, Pagure, etc. Then you can easil

Highlights from the latest Copr release

Hello, recently (on Feb 19) a major Copr update took place. It was announced, but release notes weren't attached. Because a list of all changes would be long and boring, I rather decided to present you some highlights of the release. - Allow per-package chroot-blacklisting by wildcard patterns

Copr is going to remove build data from end-of-life chroots

Hello, I would like to let you know, that in the following few days, you will start receiving automatized notifications from Copr, telling you about deleting repositories for outdated chroots and how to proceed if you want to keep them for your projects. Please read more information about how it i

Fedora 30 chroots now available in Copr

Hello, I've just enabled F30 chroots in Copr. The projects that have "Follow Fedora branching" enabled, have them automatically activated as well builds from rawhide forked into them. Jakub ___ devel mailing list -- devel@lists.fedoraproject.org To unsu

Re: Copr is going to remove build data from end-of-life chroots

it to 180. The chroots, that will be outdated in the future will be preserved 180 days by default. Jakub On Sun, Mar 10, 2019 at 10:58 PM Jakub Kadlcik wrote: > > Hello, > I would like to let you know, that in the following few days, > you will start receiving automatized notificatio

Fwd: Outage: Upgrade of Copr servers - 2019-04-24 17:00 UTC

There will be an outage starting at 2019-04-24 17:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2019-04-24 17:00 UTC' Reason for outage: Upgrade of Copr services to the newest version. A

New Copr release

Hello, I am happy to announce a new Copr release. This time we have focused mainly on improving a CI experience and freeing up some disk space, but there is much more. These are some highlights from this release. - CLI support for managing permissions For

Re: Auto-assign packager sponsors to tickets?

Oh, and I forgot one important thing. Any sponsor that would disagree with being assigned tickets this way would be able to opt out by adding something like `auto_assign: false` to their sponsor.yaml https://github.com/FrostyX/fedora-sponsors#b-your-personal-config-on-fedorapeopleorg Jakub On Sat

Re: Auto-assign packager sponsors to tickets?

> If they wait for months, I think they don't want to be sponsored. I respectfully disagree here, IMHO we communicate a message that a sponsor will find the contributor, not the other way around. Just so I don't repeat the same message in my own words, everything that Miroslav said, sounds true to

Re: Auto-assign packager sponsors to tickets?

cause there is thousand of them each year. That would be insane. But how many new contributors that need to be sponsored do we have each year? My guess is that not even every sponsor would get a ticket within the year. Jakub On Sun, Apr 2, 2023 at 5:07 PM Jakub Kadlcik wrote: > > > If

Re: Auto-assign packager sponsors to tickets?

> It absoletely does. ;) And it even allows us to retrospectively see how many packagers were sponsored in the last month/year/... https://gist.github.com/FrostyX/47defa18348fbb917e73d7b2e7660ca2 Fedora-messaging is awesome :-) On Mon, Apr 3, 2023 at 10:33 PM Kevin Fenzi wrote: > > On Mon, Apr

Re: Auto-assign packager sponsors to tickets?

Thank you all for the feedback. > The bottom line is that package reviews can be quite time consuming. I > don't think the issue is with sponsorship itself. Sorry Jason, I probably didn't communicate my idea as clearly as I should. My intention wasn't to assign sponsors to review tickets and mak

Non-responsive maintainer - rkuska

Hello, per the Non-responsive maintainer policy https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers I am sending this email. We (copr-sig) would like to (co)maintain the python-flask-whooshee package but @rkuska can't give us permission because he lost access to

Re: Auto-assign packager sponsors to tickets?

I want to thank you all for the feedback. Everything was already mentioned in the discussion so I am not going to dig into details again. Just a quick summary for anyone who wants TL;DR for this thread: - I am not going to implement the original proposal or any variation of it - Instead, I am goi

Re: Fedora Review Service

edora infra issue and discuss their requirements and deployment options. Jakub On Fri, Dec 2, 2022 at 6:49 PM Adam Williamson wrote: > > On Fri, 2022-12-02 at 18:20 +0100, Jakub Kadlcik wrote: > > Hello folks, > > > > for a couple of years now, I've been interested i

Re: Fedora Review Service

, and therefore cover more tickets as a consequence. Jakub On Sat, Dec 3, 2022 at 12:25 PM Vitaly Zaitsev via devel wrote: > > On 02/12/2022 18:20, Jakub Kadlcik wrote: > > I started working on a service [2] that listens to fedora-messaging > > and for every new RHBZ review ticket or

Re: Fedora Review Service

I created the Fedora Infra ticket https://pagure.io/fedora-infrastructure/issue/11028 Jakub On Sat, Dec 3, 2022 at 1:00 PM Jakub Kadlcik wrote: > > > fedora-review require a lot of manual checks from reviewer (especially > > licenses). It can't be fully automated. > &g

Re: Orphaned packages looking for new maintainers

Hello Miro, > tito frostyx, maxamillion, orphan 3 weeks ago Taking On Tue, Dec 20, 2022 at 12:30 AM Emmanuel Seyman wrote: > > * Miro Hrončok [19/12/2022 16:43] : > > > > perl-Mail-Procmailorphan 0 weeks > > ago > > Taken. > > Emmanuel > __

Re: Fedora Review Service

: > > On Wed, 2023-01-04 at 23:41 +0100, Miro Hrončok wrote: > > On 02. 12. 22 18:20, Jakub Kadlcik wrote: > > > Hello folks, > > > > > > for a couple of years now, I've been interested in the Fedora > > > package > > > review process.

Re: Fedora Linux 38 branched

Hello Tomas, thank you for the announcement. We also branched Fedora 38 in Copr so that everybody can submit builds for it by now. Also, all projects with the "Follow Fedora branching" option configured in their project settings have F38 chroots automatically enabled and they contain the last buil

Re: Screen brightness keys not working

Hello Iñaki, I don't know what caused your issue but I had screen brightness issues in the past and started using a tool called `light` as an alternative to `xbacklight`. It is in Fedora https://src.fedoraproject.org/rpms/light. Maybe you want to try it as a temporary workaround until you find a pr

Re: fedora-review workarounds for dnf5

Hello Jerry, I proposed a workaround a few days ago https://pagure.io/FedoraReview/pull-request/485 but your patch looks like a proper fix. I'll try it and merge to the fedora-review codebase. Does anybody know what was the purpose of --resolve and if it will be no problem when we remove it? Jak

Re: fedora-review workarounds for dnf5

Thank you very much Michel for going through the release. It couldn't be easy. There is a reported bug in Bodhi, so it will need some minor fixups but we are close. Really looking forward to it. Jakub On Tue, Jul 25, 2023 at 4:48 AM Michel Alexandre Salim wrote: > > Hi all, > > On Mon, Jul 17,

Re: fedora-review workarounds for dnf5

Hello Sandro, > I noticed that in f39 builds in Copr the directory containing the > results is now named after the package. Comparing that to the > "traditional" fedora-review directory in f38 builds, I miss the > `licensecheck.txt` file. It suddenly started happening and I don't know what is to

Fedora Review Service and setting the AutomationTriaged keyword

Hello, a year ago I announced and launched the Fedora Review Service . Nobody complained that it

Re: Fedora Review Service and setting the AutomationTriaged keyword

Thank you for the feedback Dominik, > Cool! Go for it. > Great idea. I am going for it then :-) On Sat, Dec 9, 2023 at 10:20 PM Dominik 'Rathann' Mierzejewski < domi...@greysector.net> wrote: > On Saturday, 09 December 2023 at 19:32, Jakub Kadlcik wrote: > > He

fedora-distro-aliases - The easiest way to get numbers of active Fedora releases

Hello, I just wanted to quickly announce a small project I did in collaboration with the Packit folks. Do you have some tools or services that perform actions on all currently active Fedora releases? And do you have to manually update their list every time a new Fedora release is branched or EOLed

Re: fedora-distro-aliases - The easiest way to get numbers of active Fedora releases

lease subscribe the issue, I will fix it soon :-) On Fri, Jan 19, 2024 at 8:34 PM Stephen Gallagher wrote: > On Thu, Jan 18, 2024 at 10:32 AM Stephen Gallagher > wrote: > > > > On Wed, Jan 17, 2024 at 5:58 AM Jakub Kadlcik > wrote: > > > > > > Hello, >

Re: fedora-distro-aliases - The easiest way to get numbers of active Fedora releases

I published version 1.2 which doesn't depend on bodhi-client anymore. It is now on PyPI and Bodhi updates are in testing. On Tue, Jan 23, 2024 at 12:59 PM Jakub Kadlcik wrote: > Thank you for the feedback Stephen, > I didn't realize how many and how complicated dependencies the

Cached Package Review Tracker - Tickets that passed automated review

Hello, if you use the Cached Package Review Tracker https://fedoraproject.org/PackageReviewStatus/ there is a new "feature" that you may find useful. Fedora Review Service runs the fedora-review tool on every new Bugzilla ticket. If no errors are found, the ticket is marked with a special keyword.

Re: Announce: Log Detective - AI tool to analyze build logs failures

Hello all, I recorded a very short video showing how you can contribute to the Log Detective project. https://www.youtube.com/watch?v=_-O7ryKCnlQ Any help will be greatly appreciated :-) Jakub On Wed, Jan 17, 2024 at 8:26 PM Jiri Kyjovsky wrote: > Hello Tristan, > > We store the data in json

Fedora Review feature in Copr and Fedora Review Service work again

Hello fellow package maintainers, we had multiple reports over the last weeks that the fedora-review feature in Copr produces empty review.txt templates for F40 and Fedora Rawhide. And as a consequence the Fedora Review Service points to empty review.txt files. The issue is in the fedora-review to

User SSH access to Copr builders

Hello, this may be a useful feature for many people, so I wanted to announce it separately. Debugging failed Copr builds became much easier with the last release. https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html You can now enable SSH access to the builder, connect using your pubke

Fwd: I made a new Fedora Apps page, do you want it?

Hello, I am reimplementing the current https://apps.fedoraproject.org page. It is not finished yet, but I wanted to share a demo with you: https://fedora-apps.netlify.app The upstream is here: https://github.com/frostyx/fedora-apps/ Do you have any interest to eventually switch to this implement

Re: I made a new Fedora Apps page, do you want it?

ttps://getfedora.org/ > Though I would like the viewing window to expand when zoomed in so that it > fills the screen. Cool idea. Will do, thanks. Jakub On Thu, Sep 8, 2022 at 2:32 PM stan via devel wrote: > > On Thu, 8 Sep 2022 12:38:49 +0200 > Jakub Kadlcik wrote: > > > He

Fedora Review Service

Hello folks, for a couple of years now, I've been interested in the Fedora package review process. Our queue is in hundreds of waiting packages for as long as I can remember. I believe the situation can be improved. Since summer, I did ~40 package reviews to get a better grasp of the situation an

Mock v5.6 and mock-core-configs v40.4 release

Hello maintainers, We released a new version of Mock, the chroot build environment manager for building RPMs, and a new version of mock-core-configs. The notable changes are big performance improvements for bash completion, many bugfixes, new Circle Linux 9 configs, and more. Full release notes:

Service monitoring in CommuniShift/OpenShift?

I am running a service in Fedora CommuniShift (planning to move it to Fedora production OpenShift instance in case it is relevant). Can anybody please help me understand how to configure some monitoring for it? Is it possible to configure nagios.fedoraproject.org for it? Or is there any other reco

Re: Service monitoring in CommuniShift/OpenShift?

ns regarding the migration process were answered in https://pagure.io/fedora-infrastructure/issue/11814 so I will just have to prioritize that. Then I will get back to you in regards to the Nagios configuration. Thank you again, Jakub On Sun, Jun 2, 2024 at 7:35 PM Kevin Fenzi wrote: > On Sa

Re: Disabling Fedora 30 chroots in Copr

13.html [4] https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#eol-chroot-repositories Jakub On Tue, Aug 18, 2020 at 3:12 PM Jakub Kadlcik wrote: > > Hello, > > we have just disabled Fedora 30 chroots in Copr. > > According to the Fedora wiki [1], Fedora 30 reac

Re: Disabling Fedora 30 chroots in Copr

Hello Alexander, what do those chroots say in their "Remaining time" column, please? Jakub On Mon, Nov 23, 2020 at 8:34 AM Alexander Ploumistos wrote: > > Hello Jakub, > > I noticed that some of my projects still have chroots for even older > releases, e.g. F28, F29 without the option to remove

Re: Disabling Fedora 30 chroots in Copr

projects still have chroots for even older > releases, e.g. F28, F29 without the option to remove them. Or did I misunderstood? Thank you for the feedback, Jakub On Mon, Nov 23, 2020 at 10:04 AM Alexander Ploumistos wrote: > > On Mon, Nov 23, 2020 at 9:54 AM Jakub Kadlcik wrote: > &

Re: Disabling Fedora 30 chroots in Copr

Ah, so you meant the F28 and F29 chroots listed here in the build details, e.g. https://copr.fedorainfracloud.org/coprs/alexpl/molsketch/build/869545/ That is as expected. Possibly we can improve our deletion script to hide/remove them as well but it is not done yet. The important thing (from our

Disabling Fedora 30 chroots in Copr

Hello, we have just disabled Fedora 30 chroots in Copr. According to the Fedora wiki [1], Fedora 30 reached the end of its life on 2020-05-26 and therefore we are disabling it in Copr. That effectively means that from this moment, it is no longer possible to submit builds for the following chroo

Re: Package wishlist site?

Thank you for the feedback. It all makes sense, and I agree with your points, so I won't put any more effort into this idea. I am also glad, that this discussion happened and the idea won't be itching my brain anymore. Jakub On Sun, Dec 26, 2021 at 7:31 AM Dan Čermák wrote: > > Hi Jakube, > > Ja

Web assets in Fedora

Hello, I've written a blog post about web assets in Fedora. Do you bundle third-party libraries/frameworks like jQuery, Bootstrap or Patternfly into your project and commit them to the git repository? There is a much better solution how to do it. If you are interested, please read the article htt

Improving Fedora sponsors discoverability

Hello fellow Fedora people, Inspired by @msuchy's Flock 2016 presentation, I would like to tackle one of the topics discussed there - The discoverability of Fedora sponsors for newcomers. I have a website ready to be deployed. If you are interested in the technical details, please see this RFE h

Re: Improving Fedora sponsors discoverability

to you? Jakub On Tue, Jun 15, 2021 at 7:43 PM Kevin Fenzi wrote: > > On Fri, Jun 11, 2021 at 05:03:36PM +0200, Jakub Kadlcik wrote: > > Hello fellow Fedora people, > > > > Inspired by @msuchy's Flock 2016 presentation, I > > would like to tackle one of the topi

Packager sponsors site

Hello, I am happy to announce that I deployed this little site https://docs.pagure.org/fedora-sponsors/ Its goal is to help new Fedora packagers find the right sponsor for them (based on the used programming language, domain of the project, native language of the packager, etc). Please share the

Re: Packager sponsors site

> I suggest you update the relevant wiki page [1] Good idea, thank you. Updated, please take a look. > I filed your first ticket, about how timezones are displayed. Thank you, I will revisit the timezones generation. Jakub On Mon, Jul 12, 2021 at 5:10 AM Otto Urpelainen wrote: >

Re: Copr Modularity, the End of an Era

On Thu, Oct 31, 2024 at 1:24 PM Nikita Popov wrote: > On Wed, Oct 23, 2024 at 5:32 PM Jakub Kadlcik wrote: > >> Hello everybody, >> I'd like to announce that all Modularity features in Copr (except for >> module hotfixes) are now deprecated, and we have a plan to slowly

Copr Modularity, the End of an Era

Hello everybody, I'd like to announce that all Modularity features in Copr (except for module hotfixes) are now deprecated, and we have a plan to slowly remove them from our codebase. For more reasoning and the retirement schedule, please read my blog post - https://frostyx.cz/posts/copr-modularit