Re: Bodhi client calls in the infra

On Mon, Mar 14, 2022 at 04:07:30PM +0100, Aurelien Bompard wrote: > Hey folks! > > We are preparing for the deployment of the next major release of Bodhi > (planned for a Friday evening on an Irish bank holiday during freeze in the > Thanksgiving extended weekend), and the authentication has

Re: FBR: OCP4 storage configuration

On Fri, Mar 11, 2022 at 04:31:31PM +, Mark O'Brien wrote: > Hi All, > > I am asking for forgiveness here. We did this work earlier today and only > realised afterward that a freeze break should have been requested. > > OCP worker node worker06.ocp.iad2.fedoraproject.org had its installed >

Re: undefined symbol `__libc_stack_end' in F36/Rawhide

On Fri, Mar 11, 2022 at 11:21:09AM +, Sérgio Basto wrote: > Hello, > > On Thu, 2022-03-10 at 09:36 +0100, Florian Weimer wrote: > > * Ron Olson: > > > > > Building swiftlang on F36/Rawhide results in a a failure that, > > > boiled down to its essence, appears to be: > > > > > > /usr/bin/ld:

Re: F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)

On Tue, Mar 08, 2022 at 04:28:58PM -0600, Michael Cronenworth wrote: > On 3/8/22 4:08 PM, Kevin Fenzi wrote: > > Perhaps you could share with the list how used/important wine.i686 is > > these days? Are most folks still using it? Slowly switching to > > wine.x86_64? > &

Re: F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)

On Mon, Mar 07, 2022 at 03:54:25PM -0600, Michael Cronenworth wrote: > On 3/7/22 2:03 PM, Neal Gompa wrote: > > A simpler solution would be to just default-off i686 and check-in some > > marker file that indicates the package needs to be built for multilib. > > This is how openSUSE does it today

Re: F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)

On Tue, Mar 08, 2022 at 01:55:47PM -0600, Chris Adams wrote: > > Rather than churn 20,000+ packages (plus add a new requirement for every > new package to include an ExcludeArch), why not address this at the > build system? > > Writing a script to generate a list of the buildroot plus multilib >

Re: F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)

On Mon, Mar 07, 2022 at 12:45:36PM -0800, Adam Williamson wrote: > On Mon, 2022-03-07 at 11:25 -0800, Kevin Fenzi wrote: > > So, I'll go ahead and be a bad guy here: > > > > Perhaps it's time to just retire i686 completely? > > > > Steam is available as a flatpa

Freeze Break request: update mirrors.centos.org cert

We host the mirros.centos.org site on our proxies (redirecting to mirrormanager). It has a letsencrypt cert and it expires on March 22nd. We have a new cert ready now, so I would like to just update it now so it's all in sync. Will require pushing the new cert to the ansible-private repo and

Re: F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)

So, I'll go ahead and be a bad guy here: Perhaps it's time to just retire i686 completely? Steam is available as a flatpak, and old software thats 32bit only and can't be rebuilt could just be run from a f36 container? This would save us: * all the builder resources * all the multilib

Re: VERY late notification emails

On Sat, Mar 05, 2022 at 10:58:53AM +, Dan Čermák wrote: > > > On March 5, 2022 9:03:54 AM UTC, Gary Buhrmaster > wrote: > >On Mon, Feb 28, 2022 at 5:25 PM Kevin Fenzi wrote: > > > >> No, there's things we can do and are trying to do. ;) > > >

[Fedora-legal-list] Re: good/bad v. approved/not-approved

On Thu, Mar 03, 2022 at 05:18:48PM -0500, Richard Fontana wrote: > On Thu, Mar 3, 2022 at 5:08 PM Jilayne Lovejoy wrote: > > > > > > > > On 3/3/22 2:51 PM, Kevin Fenzi wrote: > > > On Thu, Mar 03, 2022 at 12:03:15PM -0700, Jilayne Lovejoy wrote: >

Re: FBR: Update oz on certain aarch64 builders

On Fri, Mar 04, 2022 at 04:26:27PM -0500, Mohan Boddu wrote: > Hello, > > Due to a bug in initial-setup [0] we need to update oz to 0.18.1-2 on > some aarch64 builders. The list is obtained by running > > $ koji list-hosts --enabled --arch armhfp --channel image --arch aarch64 > > Hosts: >

Re: s390x KOJI builders issue

...snip... > > If this is just s390x builders, I'd prefer to see if we cannot rebalance > them to just pass your builds. So, looking at it, we have 20 buildvm's > on a host with 256gb mem. I could bump them all from 10 to 12 without > overcommiting. I don't know if 2gb would help enough tho? Is

[Fedora-legal-list] Re: good/bad v. approved/not-approved

On Thu, Mar 03, 2022 at 12:03:15PM -0700, Jilayne Lovejoy wrote: > Hi all, > > > As has been mentioned here prior, Richard and I are having a look at the > Licensing part of the Wiki with an eye towards any updates and improvements, > as well as moving that to the Fedora Docs (along with David

3 small freeze breaks

Greetings everyone. I have 3 PR's that I would like to get freeze breaks for (+1s from any sysadmin main or releng person). Of course comments from everyone are most welcome too. First: https://pagure.io/fedora-infra/ansible/pull-request/986 proxies: update *.id.fedoraproject.org wildcard to

Re: s390x KOJI builders issue

On Thu, Mar 03, 2022 at 02:32:50AM +0100, Michal Schorm wrote: > In many cases, the build is killed during compilation itself. > I'd understand the situation, if it would consistently fail somewhere > during the testsuite on OOM errors, but it's weirder than that. > > Until now, I didn't have

Re: s390x KOJI builders issue

, after something crashed there (OOM?) ... > > > > This was happening to me on armv7hl a few weeks ago. Kevin Fenzi > > investigated and discovered that the builds kept hitting an OOM > > condition and then restarting, which triggered an infinite loop. Each > > build woul

Re: VERY late notification emails

On Tue, Mar 01, 2022 at 10:42:38AM +0100, Vít Ondruch wrote: > > Dne 28. 02. 22 v 18:24 Kevin Fenzi napsal(a): > > On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote: > > > I almost wrote this a week ago but decided not to as it's been recently > > >

Re: VERY late notification emails

On Tue, Mar 01, 2022 at 08:04:14PM -, Peter Oliver wrote: > > I almost wrote this a week ago but decided not to as it's been recently > > discussed but this is really annoying. 6 days later is more than useless. > > ... > > Is there really nothing we can do about this? > > I think getting

Re: copr expired security certificate?

On Wed, Mar 02, 2022 at 05:06:59PM -0500, Steven A. Falco wrote: > On 3/2/22 04:35 PM, Scott Talbert wrote: > > On Wed, 2 Mar 2022, Steven A. Falco wrote: > > > > > I just tried to connect to copr [1] with firefox, and got a "Did Not > > > Connect: Potential Security Issue" error. > > > > > >

planet

Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it. Right now: fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople). To add a blog/rss feed you have to login there and edit your .planet file, then scripting pulls all those .planet

Re: VERY late notification emails

On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote: > I almost wrote this a week ago but decided not to as it's been recently > discussed but this is really annoying. 6 days later is more than useless. > > Previously it was blamed, at least partially, on the mass rebuild, but > clearly

[Fedora-legal-list] Re: Waydroid LineageOS licensing

On Thu, Feb 17, 2022 at 12:22:55AM +0100, Alessandro Astone wrote: > Hi, > > I'm working on packaging Waydroid for fedora. This is a wrapper around lxc > that natively runs a patched LineageOS android image. While the lxc wrapper > itself is GPL3, the big elephant in the room is the LineageOS

Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)

On Wed, Feb 23, 2022 at 10:19:33AM +0100, Vitaly Zaitsev via devel wrote: > On 22/02/2022 21:45, Peter Robinson wrote: > > Does it make sense to keep FTP with most browsers obsoleting the > > protocol due to lack of security? > > Many Fedora mirrors still use FTP. You can check metalink file.

Re: anheath - reaching out

On Tue, Feb 22, 2022 at 07:57:10PM -0500, Andrew Heath wrote: > Hey all, my name is Andy Heath and I'm a Senior Information systems > engineer at Red Hat. I have been using Fedora for the better part of 7+ > years and would like to give back. Some of the skills I have developed over > the years I

Re: Building VM images for Copr builders

On Wed, Feb 23, 2022 at 06:18:24PM +0100, Pavel Raiskup wrote: > Hello infra! > > Currently, in Copr team we are periodically preparing those kinds of images > for > our VM builders: ...snip... > > - I thought the answer is Image Builder, but there's a missing support for > Fedora ppc64le and

Re: Preventing account takeovers through expired domains

On Wed, Feb 23, 2022 at 10:33:16AM +0100, Vitaly Zaitsev via devel wrote: > On 22/02/2022 12:33, Daniel P. Berrangé wrote: > > Given that the accounts system already supports these OTPs, what > > is the reason for not mandating this OTP based 2FA for*all* > > contributors today, as oppposed to

Re: Preventing account takeovers through expired domains

On Tue, Feb 22, 2022 at 11:33:55AM +, Daniel P. Berrangé wrote: > On Sun, Feb 20, 2022 at 04:08:43PM -0800, Adam Williamson wrote: > > On Sun, 2022-02-20 at 16:42 +, Gary Buhrmaster wrote: > > > Unfortunately, last I checked, the FAS account > > > system did not support adding something >

Fedora 36 Beta Freeze now in effect

Greetings. We are now in the infrastructure freeze leading up to the Fedora 36 Beta release. This is a pre release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 36 Beta when it's available. You can see a list of hosts that do not freeze by

Re: Preventing account takeovers through expired domains

On Sun, Feb 20, 2022 at 04:43:13PM -0800, Gary Buhrmaster wrote: > On Sun, Feb 20, 2022, 16:09 Adam Williamson > wrote: > > > It used to support these, but the support was lost with the recent > > rewrite. However, it supports Google Authenticator-style OTPs. Folks > > with infra privileges on

Re: GNOME (and Cinnamon) issues in Rawhide: status report, including gnome-bluetooth soname issues

On Thu, Feb 17, 2022 at 01:21:15AM +0100, Kevin Kofler via devel wrote: > Adam Williamson wrote: > > AFAIK we've always had that rule. It's always been policy that we don't > > untag once a build has been in a successful compose. I don't think this > > changed "a few years ago", unless I'm

Re: Fedora 36 Mass Branching

On Mon, Feb 14, 2022 at 03:30:52PM +, Jonathan Wakely wrote: > > I can't see how "rawhide/f36 has been completely isolated from > previous releases" can be interpreted to mean that :-) Well, long ago when we branched, there was a inheritence chain in koji, so if you built something in F(n-1)

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

On Sun, Feb 13, 2022 at 05:46:49PM +0100, Zbigniew Jędrzejewski-Szmek wrote: > On Sun, Feb 13, 2022 at 09:43:38AM -0600, Michael Catanzaro wrote: > > On Sun, Feb 13 2022 at 02:26:46 PM +0100, Miro Hrončok > > wrote: > > > Considering most of the dependent packages failed to rebuild in this > > >

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

I think this will be my last reply on the topic...I think people know my view and Kevin's here (but if other folks have more questions, happy to answer them). On Sat, Feb 12, 2022 at 08:09:34PM +0100, Kevin Kofler via devel wrote: > Kevin Fenzi wrote: > > As a release engineer tryi

Re: Fedora rawhide compose report: 20220211.n.3 changes: order of changelogs

On Sat, Feb 12, 2022 at 11:41:22AM +0100, Zbigniew Jędrzejewski-Szmek wrote: > Are the changelogs for packages supposed to be ordered newest-to-latest > or the reverse? Some packages have the changelog one way, some the other… > > I find this confusing, because I always start thinking "is the

[fedora-arm] Re: Fedora on Pinephone Pro & path to upstreaming

On Sat, Feb 12, 2022 at 11:28:08PM +, Peter Robinson wrote: > On Sat, Feb 12, 2022 at 11:19 PM Be wrote: ...snip... > > > > Unless you mean something else by "USB recovery". > > Yes, I do, the rockchip recovery doesn't expose mass storage, that > must be a tow-boot thing, hence why I

[fedora-arm] Re: Fedora on Pinephone Pro & path to upstreaming

On Fri, Feb 11, 2022 at 01:42:39AM -, Be wrote: > Whether Tow Boot or uboot is on the SPI flash isn't really relevant to > distros. The point is that distros shouldn't have to worry about shipping > uboot, just like Fedora doesn't ship UEFI firmware for x86-64. Tow Boot has > some UX

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

On Fri, Feb 11, 2022 at 09:45:53PM +0100, Kevin Kofler via devel wrote: > Miro Hrončok wrote: > > It was actually announced: > > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/ > > > > But for reasons I don't understand,

Re: Problems building on F36, F37 caused by vtk?

On Fri, Feb 11, 2022 at 08:33:14PM +0100, Miro Hrončok wrote: > On 11. 02. 22 20:31, Miro Hrončok wrote: > > On 11. 02. 22 20:21, Kevin Fenzi wrote: > > > > I would be really happy to drop armv7hl for the vtk stack. > > > So, just to clarify and provide more info he

Re: Fedora ID and HTTPS

On Thu, Feb 03, 2022 at 07:16:01AM -0800, Jan Staněk wrote: > Hi list, > > tl;dr: Why is the Fedora ID server using HTTP communication by default? Fedora openid is using http because long ago when we started offering openid users were 'http://username.id.fedoraproject.org' and thus were tied to

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 07:12:04AM -0600, Richard Shaw wrote: > Not quoting anyone in particular but I thought I saw it referenced in this > thread (and definitely the previous thread from last year). > > What's wrong with having someone "sign" the CLA every year? At work a > non-disclosure is

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 11:33:13AM +, Mattia Verga via devel wrote: > Il 11/02/22 12:20, Florian Weimer ha scritto: > > * Mattia Verga via devel: > > > >> Il 11/02/22 10:41, Miro Hrončok ha scritto: > >>> On 11. 02. 22 10:12, Mattia Verga via devel wrote: > Where are those 2543 packagers

Re: Problems building on F36, F37 caused by vtk?

On Thu, Feb 10, 2022 at 07:29:56PM -0700, Orion Poplawski wrote: > On 2/10/22 12:21, Michael Catanzaro wrote: > > On Thu, Feb 10 2022 at 02:09:32 PM -0500, Steven A. Falco > > wrote: > > > g++: fatal error: Killed signal terminated program cc1plus > > > > This indicates the builder ran out of

Re: Bodhi and "update ejected from the push" errors

On Thu, Feb 10, 2022 at 12:31:15PM +, Sérgio Basto wrote: > On Sat, 2022-01-29 at 11:12 -0800, Kevin Fenzi wrote: > > On Sat, Jan 29, 2022 at 05:38:42PM +, Mattia Verga via devel > > wrote: > > > Recently we're having some (a lot) of errors about updates stuck in

Re: Fedora 36 compose report: 20220209.n.0 changes

On Wed, Feb 09, 2022 at 11:02:38PM +, Fedora Rawhide Report wrote: > I guess this doesn't handle the case of the first branched compose of a cycle right. ;) Anyhow, here is the report against the last rawhide compose. OLD: Fedora-Rawhide-20220208.n.0 NEW: Fedora-36-20220209.n.0 =

Re: Fedora kernel emails: too much or just right?

On Tue, Feb 08, 2022 at 02:24:22PM -0500, Donald Zickus wrote: > Hi, > > It has been awhile since we changed how this mailing list is used. As > folks have noticed, we have increased traffic significantly over the > past couple of years to reflect the activity Red Hat developers are > performing

Re: Fedora 36 Mass Branching

On Wed, Feb 09, 2022 at 09:39:16AM +0100, Fabio Valentini wrote: > On Wed, Feb 9, 2022 at 2:32 AM Kevin Fenzi wrote: > > > > And I suppose we should really look at disabling builds on mass branch > > day (while it's happening) it never ends well. :) > > Should I op

Re: Suggestions for fedora

On Wed, Feb 09, 2022 at 09:37:45AM -, Raj J Putari wrote: > Not sure what selinux really is but I think it makes polices based on system > mechanics so nekto or netko the vulnerability scanner can be reversed > engineered to generate custom policies on the fly Well, no. It provides a policy

Re: Fedora 36 Mass Branching

On Wed, Feb 09, 2022 at 06:26:44PM +0100, Fabio Valentini wrote: > On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely wrote: > > > > On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka wrote: > > > > > > Hi All, > > > > > > Fedora 36 has now been branched, please be sure to do a git pull > > > --rebase to pick

Re: Fedora 36 Mass Branching

On Wed, Feb 09, 2022 at 12:42:25AM -, Artur Frenszek-Iwicki wrote: > One of my packages ("blueman") had a new release today, so I updated it. > Despite me committing to the rawhide branch, the build was given the ".f36" > suffix, > so when I pushed to the f36 branch and tried to build the

Re: Fedora 36 Mass Branching

On Tue, Feb 08, 2022 at 03:53:51PM -0800, Michel Alexandre Salim wrote: > On Tue, Feb 08, 2022 at 09:28:53PM +0100, Tomas Hrcka wrote: > > Hi All, > > > > Fedora 36 has now been branched, please be sure to do a git pull > > --rebase to pick up the new branch, as an additional reminder > > Most

[fedora-arm] Re: Fedora on Pinephone Pro & path to upstreaming

On Mon, Jan 31, 2022 at 05:49:14AM -, Be wrote: > Hello, > I've been using Fedora on my Pinephone for like 9 months or so and my > Pinephone Pro Explorer Edition just arrived the other day. The original > Pinephone's boot order had the microSD card before the eMMC which made it > really

Re: Installing from updates-testing not working?

On Sat, Feb 05, 2022 at 04:09:21PM +, Gary Buhrmaster wrote: > On Fri, Feb 4, 2022 at 11:32 AM Ian McInerney via devel > wrote: > > > From a user experience perspective, the mirror lag time on it is very > > annoying. When the update is pushed to testing, Bodhi posts a comment in > > the

Re: CentOS 9 Stream mirror metalink down?

On Fri, Feb 04, 2022 at 09:10:47PM -0500, Fulko Hew wrote: > On Fri, Feb 4, 2022 at 9:02 PM Richard Shaw wrote: > > > I have a CentOS 9 Stream VM I'm trying to update and I'm getting a 503 on: > > > > > > https://mirrors.centos.org/metalink?repo=centos-baseos-9-stream=x86_64=https,http > > > >

Re: Installing from updates-testing not working?

On Thu, Feb 03, 2022 at 06:38:11PM +, Ian McInerney via devel wrote: > > I guess it was a mirror caching issue. I tried again just now and it picked > up the update just fine. I didn't think the updates-testing repo was > mirrored though, but it is very annoying that the mirror sync and the

Re: Self Introduction: Julien Rische

On Thu, Feb 03, 2022 at 05:22:44PM -, Julien Rische wrote: > Hi everyone, > > My name is Julien Rische. I'm from north-east France. > > I joined the Red Hat IdM team last month to take part in the development of > FreeIPA, especially its Kerberos components. I will be contributing upstream >

Re: search among all spec files

On Tue, Feb 01, 2022 at 01:47:43PM -0800, Michel Alexandre Salim wrote: > On Tue, Feb 01, 2022 at 01:16:57AM +0100, Miro Hrončok wrote: > > On 01. 02. 22 1:03, Germano Massullo wrote: > > > Good day. I have to search gcc-toolset among all Fedora packages specs > > > files, in order to read some

Re: GenericError: cannot update build 1910991, state: COMPLETE

On Tue, Feb 01, 2022 at 10:34:24PM +0100, Florian Weimer wrote: > * Kevin Fenzi: > > > On Tue, Feb 01, 2022 at 05:27:22PM +0100, Florian Weimer wrote: > >> <https://koji.fedoraproject.org/koji/taskinfo?taskID=82238153> failed > >> with this error. What is goin

Re: Bodhi's move to OIDC

On Tue, Feb 01, 2022 at 11:31:35AM -0800, Adam Williamson wrote: > On Tue, 2022-02-01 at 11:17 -0800, Kevin Fenzi wrote: > > On Tue, Feb 01, 2022 at 06:15:59PM +0100, Aurelien Bompard wrote: > > > Hey folks! > > > > > ...snip background... > > > > >

Re: Bodhi's move to OIDC

On Tue, Feb 01, 2022 at 06:15:59PM +0100, Aurelien Bompard wrote: > Hey folks! > ...snip background... > > Weirdness aside, I'm wondering if this could hurt people who may run > the bodhi client CLI on a headless server. The browser must be opened > on the same host where the CLI is running.

Re: GenericError: cannot update build 1910991, state: COMPLETE

On Tue, Feb 01, 2022 at 05:27:22PM +0100, Florian Weimer wrote: > failed > with this error. What is going on there? > > I have tagged the glibc-2.34.9000-39.fc36 manually into > f36-updates-candidate, which I assume will subject the

[EPEL-devel] Re: Revisiting policy for limited arch packages?

On Mon, Jan 31, 2022 at 06:48:21PM +, Gary Buhrmaster wrote: > On Mon, Jan 31, 2022 at 4:55 PM Kevin Fenzi wrote: > > > The limited arch policy we had for epel7 had a number of problems. > > At first we just said 'rebuild the exact rhel version' and then we > &

Re: search among all spec files

On Tue, Feb 01, 2022 at 01:03:22AM +0100, Germano Massullo wrote: > Good day. I have to search gcc-toolset among all Fedora packages specs > files, in order to read some example of usage. > Is that possible? For example cloning the whole git repository. Well, each package is it's own git repo,

[EPEL-devel] Re: Revisiting policy for limited arch packages?

On Thu, Jan 27, 2022 at 09:35:27PM -0800, Michel Alexandre Salim wrote: > Hi all, > > I just filed https://pagure.io/epel/issue/152 to ask if we should > revisit the policy for > https://docs.fedoraproject.org/en-US/epel/epel-packaging/#limited_arch_packages > > This policy seems very similar

Re: ppc64le build failures in the mass rebuild

On Mon, Jan 31, 2022 at 02:46:09PM +, Sérgio Basto wrote: > On Mon, 2022-01-31 at 13:36 +0100, Dan Horák wrote: > > On Mon, 31 Jan 2022 12:04:08 + > > Sérgio Basto wrote: > > > > > On Mon, 2022-01-31 at 11:12 +0100, Dan Horák wrote: > > > > Hi, > > > > > > > > as there are still a

Re: -D_FORTIFY_SOURCE not defined errors

On Sat, Jan 29, 2022 at 02:18:14PM +, Sérgio Basto wrote: > On Sat, 2022-01-29 at 09:56 +0100, Jakub Jelinek wrote: > > On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote: > > > One of my packages, stable for a long time, is now getting exotic > > > errors in rawhide such as > > > > >

Re: Bodhi and "update ejected from the push" errors

On Sat, Jan 29, 2022 at 05:38:42PM +, Mattia Verga via devel wrote: > Recently we're having some (a lot) of errors about updates stuck in > Bodhi with errors like "update ejected from the push because Cannot find > relevant tag...". > > I tried to fix some of them myself, and relengs folks

Re: Revisiting Fedora backgrounds spec

On Wed, Jan 26, 2022 at 12:45:07PM -0800, Samuel Sieb wrote: > On 1/26/22 09:50, Kevin Fenzi wrote: > > On Wed, Jan 26, 2022 at 10:10:34AM +0100, Vitaly Zaitsev via devel wrote: > > > On 26/01/2022 07:40, Luya Tshimbalanga wrote: > > > > One of suggestions is mak

Re: Revisiting Fedora backgrounds spec

On Wed, Jan 26, 2022 at 06:53:01PM +, Richard W.M. Jones wrote: > > This makes me wonder if we should (or do?) have a mechanism to remove > a package which is not used. "used" in the sense of being used by any > account on the system, rather than in the dependency sense. If we had > that

Re: Weird bodhi push messages

On Wed, Jan 26, 2022 at 05:48:56PM +, Richard W.M. Jones wrote: > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-6fc6070c5a > https://bodhi.fedoraproject.org/updates/FEDORA-2022-416cd48fd5 > > What do the comments about XX being "ejected" mean? It means the build(s) were not tagged

Re: Incredible lag of koji notifications

On Wed, Jan 26, 2022 at 10:23:49AM +0100, Vitaly Zaitsev via devel wrote: > On 25/01/2022 22:33, Kevin Fenzi wrote: > > login and disable both email and irc. > > Will this disable Bodhi notifications as well? Depends on which ones you mean. If you mean comments on bodhi updat

Re: Revisiting Fedora backgrounds spec

On Wed, Jan 26, 2022 at 10:10:34AM +0100, Vitaly Zaitsev via devel wrote: > On 26/01/2022 07:40, Luya Tshimbalanga wrote: > > One of suggestions is making a package containing a set of 10 Fedora > > release wallpaper. The issue will be the increase of file size as the > > Design Team chose to keep

Re: Incredible lag of koji notifications

On Tue, Jan 25, 2022 at 09:53:10AM +0100, Vitaly Zaitsev via devel wrote: > On 24/01/2022 21:53, Kevin Fenzi wrote: > > We have a number of ideas how to improve this situation and hopefully we > > will get to doing some of that soon. > > Is it possible to completely disabl

Re: mass rebuild status - 2022-01-25

On Tue, Jan 25, 2022 at 08:39:31PM +0100, Iñaki Ucar wrote: > On Tue, 25 Jan 2022 at 19:13, Kevin Fenzi wrote: > > > > Greetings. > > > > The mass rebuild finished it's first pass on saturday morning, leaving > > 3448 failed builds. > > > > We

Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)

On Fri, Jan 21, 2022 at 04:08:04PM +, Roberto Sassu via devel wrote: > Hi everyone > > (note for the infrastructure mailing list: please check if the changes > I'm proposing could be tested in the Fedora infrastructure, like Copr) copr uses a different signing setup... so probibly won't work

Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)

On Fri, Jan 21, 2022 at 04:08:04PM +, Roberto Sassu via devel wrote: > Hi everyone > > (note for the infrastructure mailing list: please check if the changes > I'm proposing could be tested in the Fedora infrastructure, like Copr) copr uses a different signing setup... so probibly won't work

mass rebuild status - 2022-01-25

Greetings. The mass rebuild finished it's first pass on saturday morning, leaving 3448 failed builds. We then did a second pass yesterday ( 2022-01-24 ) of all failed builds, and that resulted in 1282 failed builds. The f36-rebuild tag is being merged now, but unfortunately our SOP had it

mass rebuild status - 2022-01-25

Greetings. The mass rebuild finished it's first pass on saturday morning, leaving 3448 failed builds. We then did a second pass yesterday ( 2022-01-24 ) of all failed builds, and that resulted in 1282 failed builds. The f36-rebuild tag is being merged now, but unfortunately our SOP had it

Re: Incredible lag of koji notifications

On Mon, Jan 24, 2022 at 02:44:21PM -0600, Ron Olson wrote: > Hey all, I _just_ got an email for my failed job from koji > (https://koji.fedoraproject.org/koji/taskinfo?taskID=81627145). The job > started (and finished) on Friday the 21st and yet I just got the email about > five minutes ago. Is

Re: mass rebuild status - 2022-01-24

On Mon, Jan 24, 2022 at 08:08:25PM +0100, Jakub Jelinek wrote: > On Mon, Jan 24, 2022 at 08:00:31PM +0100, Vitaly Zaitsev via devel wrote: > > On 24/01/2022 19:06, Kevin Fenzi wrote: > > > This seems kind of high, so we are going to resubmit all the failed > > > bui

mass rebuild status - 2022-01-24

The mass rebuild finished early saturday morning. This resulted in 3448 failed builds. This seems kind of high, so we are going to resubmit all the failed builds in a short second round to reduce the chance of transitory issues causing the build failures. It's expected that should finish later

Re: s390 ruby build failure

On Fri, Jan 21, 2022 at 12:20:48PM +0100, Vít Ondruch wrote: > > > I can't do that: > > > ~~~ > > $ koji save-failed-tree 81534987 > 2022-01-21 12:20:12,267 [ERROR] koji: ActionNotAllowed: Only owner of failed > task or 'admin' can run this task. And sadly due to the mass rebuild churn it's

Re: F36 Change: DIGLIM (System-Wide Change proposal)

On Wed, Jan 19, 2022 at 11:34:28AM +, Roberto Sassu via devel wrote: > > From: Roberto Sassu > > Sent: Tuesday, January 18, 2022 3:36 PM > > Hi everyone > > > > I recently sent to the kernel mailing lists a patch set to support > > PGP keys and signatures. > > > > Other than allowing the

Fedora 36 Mass Rebuild

Hi all, Per the Fedora 36 schedule[1] we have started a mass rebuild for Fedora 36 on Jan 19th, 2021. We will run a mass rebuild for Fedora 36 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f36-rebuild) and moved

Fedora 36 Mass Rebuild

Hi all, Per the Fedora 36 schedule[1] we have started a mass rebuild for Fedora 36 on Jan 19th, 2021. We will run a mass rebuild for Fedora 36 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f36-rebuild) and moved

Re: hiredis soname bump

Thanks for the fixes. I went ahead and merged the side tag because the broken by gcc packages will be broken by the mass rebuild anyhow. :( I'll try and poke at them some more next weekend... kevin signature.asc Description: PGP signature ___

Re: Self Introduction: Malcolm Inglis (mcinglis)

On Tue, Jan 18, 2022 at 08:31:05AM +0200, Otto Urpelainen wrote: > Thank you, this is great! > > Those two seem to contradict each other: > > # If you are a new packager seeking sponsorship via new package or reviews > # please close this > > and > > # If you are a new packager seeking

Re: hiredis soname bump

On Mon, Jan 17, 2022 at 10:44:57AM +1100, Nathan Scott wrote: > On Mon, Jan 17, 2022 at 10:35 AM Iñaki Ucar wrote: > > On Mon, 17 Jan 2022 at 00:21, Nathan Scott wrote: > > > On Mon, Jan 17, 2022 at 7:05 AM Kevin Fenzi wrote: > > > > > > > > Greetings.

Re: Self Introduction: Malcolm Inglis (mcinglis)

On Mon, Jan 10, 2022 at 10:47:13AM -0800, Kevin Fenzi wrote: > On Mon, Jan 10, 2022 at 11:07:33AM +0100, Vít Ondruch wrote: > > > > Just FTR, I don't think that as a sponsor, I can close the ticket and that > > is a bit discouraging. > > There's no way to tell pagure

koji hubs and builders updated

Just thought I would share that (finally) we have completed upgrades on the koji hubs and builders. The hubs have been upgraded to Fedora 35 and the latest koji version (1.17.1). Builder hypervisors have been upgraded to RHEL8.5 and the latest advanced virt stack. Builders have been

koji hubs and builders updated

Just thought I would share that (finally) we have completed upgrades on the koji hubs and builders. The hubs have been upgraded to Fedora 35 and the latest koji version (1.17.1). Builder hypervisors have been upgraded to RHEL8.5 and the latest advanced virt stack. Builders have been

hiredis soname bump

Greetings. We currently have hiredis-0.13.3-16 in rawhide, I'd like to upgrade to 1.0.2, which includes a soname bump. I plan to make a side tag and build dependent packages the next few days. I've rebuilt everything in a copr: https://copr.fedorainfracloud.org/coprs/kevin/hiredis/builds/

Re: Workflow and other problems with the Fedora container infrastructure

On Thu, Jan 13, 2022 at 02:14:19PM -0500, Neal Gompa wrote: > > One of the things that has recently happened in the Koji space is the > addition of a kiwi-build task to build images using the KIWI tool[1]. > > KIWI supports building all kinds of operating system images, including > OCI

koji hubs and builders updated

Just thought I would share that (finally) we have completed upgrades on the koji hubs and builders. The hubs have been upgraded to Fedora 35 and the latest koji version (1.17.1). Builder hypervisors have been upgraded to RHEL8.5 and the latest advanced virt stack. Builders have been

Re: Wayland and Xfce

On Wed, Jan 12, 2022 at 10:44:59PM -0400, George N. White III wrote: > On Wed, 12 Jan 2022 at 18:48, Sam Varshavchik wrote: > > > Tim via users writes: > > > > > Sam Varshavchik: > > > > Sadly, I expect that Fedora at some point will become exclusively > > > > Gnome and KDE, because only these

Re: Workflow and other problems with the Fedora container infrastructure

On Thu, Jan 13, 2022 at 02:43:50PM +0100, Honza Horak wrote: > On Wed, Jan 12, 2022 at 5:51 AM Kevin Fenzi wrote: > > > On Tue, Jan 11, 2022 at 01:02:59PM +0100, Lumír Balhar wrote: > > > If we migrate our container images to some other registry (e.g. a common > >

Re: Bugzilla email confirmation notices from FAS

On Tue, Jan 11, 2022 at 11:58:36AM -0500, Christopher wrote: > Hi, > > Today, I received an email from f...@fedoraproject.org with the subject > line "Fedora Account System: please verify your Bugzilla email > address". This email has a unique link to accounts.fedoraproject.org. > > Based on the

Re: Workflow and other problems with the Fedora container infrastructure

On Tue, Jan 11, 2022 at 01:02:59PM +0100, Lumír Balhar wrote: > Hello. > > My name is Lumír and I maintain a few layered container images in > Fedora/RHEL/upstream related to Python and S2I (source to image) platform - > namely python3, s2i-core, and s2i-base. > > TL;DR: We (maintainers of

Re: Datanommer / Datagrepper migration

On Mon, Jan 10, 2022 at 11:53:50AM +0100, Aurelien Bompard wrote: > Hey folks! > > I am happy to report that the datanommer data migration is finally > complete! \o/ Hurray! > Now we can move on to migrating the apps themselves. I had initially > written this plan: >

Re: Self Introduction: Malcolm Inglis (mcinglis)

On Mon, Jan 10, 2022 at 11:07:33AM +0100, Vít Ondruch wrote: > > Just FTR, I don't think that as a sponsor, I can close the ticket and that > is a bit discouraging. There's no way to tell pagure.io "everyone in the fedora packager group thats a manager is a admin here", so I have manually been

<    5   6   7   8   9   10   11   12   13   14   >