On Sat, Aug 06, 2022 at 10:05:40PM +0200, Maxwell G via epel-devel wrote:
> Hi EPEL folks,
>
> In the past couple EPEL SCo meetings, we have been discussing adding a
> new package retirement policy for EPEL packages.
That reads amusingly to me... to be clear 'new policy' not 'new packages'.
On Fri, Aug 05, 2022 at 07:17:03PM +0200, Dan Horák wrote:
>
> I see 20-30% of steal time in the VM building webkit, which should mean
> the hypervisor's capacity is at/over limit :-( It would benefit from
> having more physical CPUs.
In the past, steal time has been caused by other lpars
On Fri, Aug 05, 2022 at 05:30:14PM +0200, Dan Horák wrote:
> On Thu, 4 Aug 2022 16:55:15 +0200
> Dan Horák wrote:
>
> > On Thu, 4 Aug 2022 23:46:44 +0900
> > Mamoru TASAKA wrote:
> >
> > > Frantisek Zatloukal wrote on 2022/08/02 23:17:
> > > > Hmm,
> > > >
> > > > I am really sorry for this,
On Tue, Aug 02, 2022 at 01:32:07PM +0200, Miro Hrončok wrote:
> >
> > Could you please share a link to the existing script?
> >
https://pagure.io/releng/blob/main/f/scripts/mass_rebuild_file_bugs.py
I wonder if it's hitting a limit from bugzilla now, or perhaps a paging
issue? It definitely
On Mon, Aug 01, 2022 at 03:43:39PM -0700, Kevin Fenzi wrote:
> On Mon, Aug 01, 2022 at 03:04:50PM +0200, Miro Hrončok wrote:
> > On 25. 07. 22 17:57, Kevin Fenzi wrote:
> > > 21713 builds have been tagged into f37, there is currently 1144 failed
> > > build
On Mon, Aug 01, 2022 at 03:04:50PM +0200, Miro Hrončok wrote:
> On 25. 07. 22 17:57, Kevin Fenzi wrote:
> > 21713 builds have been tagged into f37, there is currently 1144 failed
> > builds that need to be addressed by the package maintainers. FTBFS bugs
> >
On Mon, Jul 25, 2022 at 01:54:38PM +0200, Michal Schorm wrote:
> Ah, It's a bit more tangled than I thought:
>
> I've somehow got an impression that the upstream release monitoring is
> not related to Fedora, but I expected the BZ bot should be.
> So I've looked for a place to report issues other
Hi all,
Per the Fedora 37 schedule[1] we started a mass rebuild for Fedora
37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:
https://pagure.io/releng/issues?status=Open=mass+rebuild
The mass rebuild was done in a side tag (f37-rebuild) and moved over to
f37. Failures can be seen
Hi all,
Per the Fedora 37 schedule[1] we started a mass rebuild for Fedora
37 on 2022/07/20. We did a mass rebuild for Fedora 37 for:
https://pagure.io/releng/issues?status=Open=mass+rebuild
The mass rebuild was done in a side tag (f37-rebuild) and moved over to
f37. Failures can be seen
As a quick and dirty thing I took the f37-needs-rebuild list and the
f37-failed to build list and found things that were only on the
needs-rebuild list.
I then filtered out the ones we don't try and mass rebuild (shim,
kernel, grub2, etc) and the silly ones we have like Fedora-Live-Xfce
On Sat, Jul 23, 2022 at 02:49:53PM -0600, Jerry James wrote:
> On Sat, Jul 23, 2022 at 2:35 PM Kevin Fenzi wrote:
> > The packages were signed and the sidetag is through to f37.
> >
> > Also, the signing queue is all caught up.
>
> Can you take a look at gap-4.11.1-
On Sat, Jul 23, 2022 at 10:43:38PM +0200, Fabio Valentini wrote:
>
> Can confirm, looks all good now, thanks!
>
> BTW, I'd like to know whatever magic you did to fedora notifications.
> Because it apparently kept chugging on right through the mass rebuild,
> and is now caught up again. :)
Yeah,
On Sat, Jul 23, 2022 at 10:09:50AM -0700, Kevin Fenzi wrote:
> On Sat, Jul 23, 2022 at 10:37:39AM +0200, Fabio Valentini wrote:
...snip...
>
> So, as long as that sidetag update goes out all should be fine.
The packages were signed and the sidetag is through to f37.
Also, the sign
On Sat, Jul 23, 2022 at 10:37:39AM +0200, Fabio Valentini wrote:
> On Fri, Jul 22, 2022 at 10:30 PM Kevin Fenzi wrote:
> >
> > We have had several issues in the last few days sadly.
> > I think your build ran into systemd-oomd running on some builders after
> > I ha
On Fri, Jul 22, 2022 at 04:26:28PM -, Jonathan Wright via devel wrote:
> Hi,
>
> I'd like to take over the orphaned package dnstracer.
> https://src.fedoraproject.org/rpms/dnstracer
>
> I submitted a ticket with releng for this as there was no "take" button
> present.
>
>
On Fri, Jul 22, 2022 at 02:24:21PM -0500, Maxwell G via devel wrote:
> On 22/07/22 09:08AM, Michael J Gruber wrote:
> > notmuch failed to build from source because of a strange test suite failure
> > on ppc64le:
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091
> >
> > The
Hi all,
Per the Fedora f37 schedule[1] we have started a mass rebuild
on 2022-07-20 for Fedora f37. We are running this mass rebuild
for the changes listed in:
https://pagure.io/releng/issues?status=Open=mass+rebuild
This mass rebuild will be done in a side tag (f37-rebuild) and merged
when
Hi all,
Per the Fedora f37 schedule[1] we have started a mass rebuild
on 2022-07-20 for Fedora f37. We are running this mass rebuild
for the changes listed in:
https://pagure.io/releng/issues?status=Open=mass+rebuild
This mass rebuild will be done in a side tag (f37-rebuild) and merged
when
On Mon, Jul 18, 2022 at 01:30:14PM +0200, Jiri Konecny wrote:
> Hi Kevin,
>
> Dne 16. 07. 22 v 21:35 Kevin Fenzi napsal(a):
> > ...snip...
> > > For this we will create a self-contained boot.iso style image with a
> > > built-in tar-payload (so that the im
On Mon, Jul 18, 2022 at 11:59:49AM +0100, Richard W.M. Jones wrote:
> On Sun, Jul 17, 2022 at 12:50:01PM -0700, Kevin Fenzi wrote:
> > On Sun, Jul 17, 2022 at 08:34:30PM +0100, Richard W.M. Jones wrote:
> > >
> > > https://koji.fedoraproject.org/ko
On Sun, Jul 17, 2022 at 08:34:30PM +0100, Richard W.M. Jones wrote:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=89618509
>
> On ppc64le:
> FAIL: test-checkwrite.sh
>
> There should be a core dump associated with this failure. Is it
> possible someone with Koji access could look to
...snip...
>
> For this we will create a self-contained boot.iso style image with a
> built-in tar-payload (so that the image can work even without network
> access) based on the latest Anaconda upstream code.
What packages will be in this tar-payload?
And can you use the boot.iso to do
On Fri, Jul 15, 2022 at 10:03:48AM -0400, Colin Walters wrote:
> We recently did https://github.com/coreos/fedora-coreos-config/pull/1840 for
> Fedora CoreOS (more background:
> https://github.com/coreos/fedora-coreos-tracker/issues/1244 ) and I'd like to
> consider applying this to all Fedora
On Wed, Jul 13, 2022 at 03:19:12PM -0400, Mark Pearson wrote:
> On 7/13/22 15:13, Kevin Fenzi wrote:
> > On Wed, Jul 13, 2022 at 02:34:12PM -0400, Mark Pearson wrote:
> >> Hi Fedora Devs,
> >>
> >> Would someone be able to help getting an official-respin done
On Wed, Jul 13, 2022 at 02:34:12PM -0400, Mark Pearson wrote:
> Hi Fedora Devs,
>
> Would someone be able to help getting an official-respin done from F36
> latest please? Similar to what was done for the Carbons etc.
>
> We need one for the Z13 & Z16 preload. We're waiting on one FW fix but
>
My 2 cents... we should try and get bodhi (and the rest of the pipeline)
to work with these large updates if at all possible.
Having releng merge tags works of course, but as Adam pointed out, it
skips our CI and feedback testing area. Additionally, it's more work to
releng folks and more
crossposting to infra list to keep folks there in the loop...
On Tue, Jul 12, 2022 at 02:53:24PM +0100, Jonathan Wakely wrote:
> On Mon, 11 Jul 2022 at 15:06, Stephen Smoogen wrote:
> > That said, IRC is actually one of the fastest ones we can push to.
>
> Is
On Sat, Jul 9, 2022, at 8:10 PM, Kevin Fenzi wrote:
> > On Fri, Jul 08, 2022 at 01:02:15PM -, Mukundan Ragavan wrote:
> >> > On Sun, Jul 03, 2022 at 12:11:40PM +0200, Fabio Valentini wrote:
> >> >
> >> > That said, until then I can try and run things on
On Fri, Jul 08, 2022 at 01:02:15PM -, Mukundan Ragavan wrote:
> > On Sun, Jul 03, 2022 at 12:11:40PM +0200, Fabio Valentini wrote:
> >
> > That said, until then I can try and run things on weekends.
>
> Is there a formal process to volunteer to hold the keys to the kingdom?
Yes. Basically
Greetings.
We were having some issues with the management interface on our primary
signing vault. The server was power cycled, but the management is still
not functioning, and now the server isn't processing signing requests
further.
Due to the US holidays there's no one on site right now, but
Greetings.
We were having some issues with the management interface on our primary
signing vault. The server was power cycled, but the management is still
not functioning, and now the server isn't processing signing requests
further.
Due to the US holidays there's no one on site right now, but
On Sun, Jul 03, 2022 at 12:11:40PM +0200, Fabio Valentini wrote:
> On Sun, Jul 3, 2022 at 11:36 AM Ralf Corsépius wrote:
> >
> > Am 03.07.22 um 10:46 schrieb Benson Muite:
> > > Maybe there are contributors where the working week is Sunday-Thursday?
> >
> > I feel, Fedora's leadership has
On Sun, Jul 03, 2022 at 11:52:26AM +0200, Marius Schwarz wrote:
> Am 03.07.22 um 04:02 schrieb Neal Gompa:
> > On Sat, Jul 2, 2022 at 8:52 PM Kevin Kofler via devel
> > wrote:
> > > Kevin Kofler via devel wrote:
> > > > The e-mail address reaches nowhere
> > > or actually, does it still work?
On Sat, Jul 02, 2022 at 05:31:13PM -0500, Maxwell G via devel wrote:
> On Saturday, July 2, 2022 3:11:44 PM CDT Kevin Fenzi wrote:
> > On Sat, Jul 02, 2022 at 11:54:17AM -0500, Maxwell G via devel wrote:
> > > On Saturday, July 2, 2022 10:01:18 AM CDT Micha
On Sat, Jul 02, 2022 at 11:54:17AM -0500, Maxwell G via devel wrote:
> On Saturday, July 2, 2022 10:01:18 AM CDT Michael Catanzaro wrote:
>
> > This is an extremely common problem in Fedora: the de facto maintainer
> > is not the main admin, and so the bugs are assigned to the wrong
> > person.
On Sat, Jun 25, 2022 at 08:53:03PM +0100, Sérgio Basto wrote:
> On Wed, 2022-06-22 at 08:52 -0700, Kevin Fenzi wrote:
> > On Tue, Jun 21, 2022 at 01:47:33PM -0500, Maxwell G via devel wrote:
> > > On Monday, June 20, 2022 10:02:00 AM CDT Sérgio Basto wrote:
> > > >
On Thu, Jun 23, 2022 at 09:53:40AM -0400, Steve Dickson wrote:
> Hello,
>
> I just took over the maintership of nfs4-acl-tools
> and it appears the command has not been part
> of Fedora since f32.
How do you mean 'part of fedora'? The package isn't retired or blocked,
it's available in the repos
h things here?
quay is open source... althought quay.io is a Red Hat run instance of
that.
kevin
--
>
> On Wed, Jun 22, 2022 at 11:57 AM Kevin Fenzi wrote:
>
> > On Tue, Jun 21, 2022 at 03:41:47PM -0400, Matthew Miller wrote:
> > > On Mon, Jun 20, 2022 at 08:21:48AM +0
On Wed, Jun 22, 2022 at 06:18:08PM -0700, Adam Williamson wrote:
> On Thu, 2022-06-09 at 12:48 -0700, Adam Williamson wrote:
> > Hi folks!
> ...
> > I think doing this could really help us keep Rawhide solid and avoid
> > introducing major compose-breaking bugs, at minimal cost. But it's a
> >
On Wed, Jun 22, 2022 at 11:09:13AM -, Michael J Gruber wrote:
> >
> > I also think that every package change (including rebuild) must be
> > tracked in changelog.
>
> I think that convolution is at the very heart of the problem:
>
> As it is, dist-git tracks "packaging sources", i.e. spec
On Tue, Jun 21, 2022 at 03:41:47PM -0400, Matthew Miller wrote:
> On Mon, Jun 20, 2022 at 08:21:48AM +0200, Lumír Balhar wrote:
> > Because we had a lot of troubles with Fedora infra for container
> > images (I can provide more details, if you want), we have decided to
> > move our containers to
On Tue, Jun 21, 2022 at 01:47:33PM -0500, Maxwell G via devel wrote:
> On Monday, June 20, 2022 10:02:00 AM CDT Sérgio Basto wrote:
> > Is is possible include builds of one side-tag into other side-tag ?
>
> It is also possible to `koji tag-build [dest side tag] [NEVR(s) from other
> side tag]`,
I'm definitely in favor, but a couple of questions...
What format image is to be produced? qcow2? or raw.xz? or something
else?
I assume this will not be release blocking at least at first?
Thanks,
kevin
signature.asc
Description: PGP signature
On Fri, Jun 17, 2022 at 02:21:39PM -0700, Adam Williamson wrote:
> On Fri, 2022-06-17 at 11:49 +0200, Miro Hrončok wrote:
...snip...
> >
> > Kevin, Adam, do could you please do some kind of compose validation?
>
> I can validate a compose if Kevin can build one.
I'm not sure I have any easy way
On Sat, Jun 18, 2022 at 01:28:10PM +0200, Vitaly Zaitsev via devel wrote:
> On 18/06/2022 12:57, Mark E. Fuller wrote:
> > Devel List: If no response from Emiliano, what's the process here for
> > taking over a package in this case (and also renaming the repo to drop
> > the version from it)?
>
>
On Sat, Jun 18, 2022 at 02:00:03PM +0200, Vitaly Zaitsev via devel wrote:
> On 18/06/2022 13:47, Richard W.M. Jones wrote:
> > So it sounds like the suffix is used for the purpose I guessed. Why
> > not let any packager use a descriptive suffix (without pre-approval)?
>
> +1. I like this idea.
On Fri, Jun 17, 2022 at 04:15:35PM -0500, Michael Catanzaro wrote:
> On Fri, Jun 17 2022 at 02:00:14 PM -0700, Kevin Fenzi
> wrote:
> > Nope, it has to stay forever. Sorry.
>
> Hi, can you explain why? Since we do not maintain upgrade paths from one
> release to the next
On Fri, Jun 17, 2022 at 10:38:19AM +0100, José Abílio Matos wrote:
> On Thursday, 16 June 2022 17.55.45 WEST Antonio T. sagitter wrote:
> > Hi all.
> >
> > I need to downgrade python-reportlab in Fedora 35 for a missing runtime
> > dependency. What's the most accurate way?
> >
> > Bug ticket:
Big +1 from me... I think this would be great to enable.
kevin
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
On Thu, Jun 09, 2022 at 09:09:30PM +0200, Miro Hrončok wrote:
> Hello,
>
> I've recently seen a package that was imported into Fedora without a package
> review. I've noticed this because the packages doesn't even install and I
> wanted to check if this could have been caught in the package
On Thu, Jun 09, 2022 at 06:47:53PM +0200, Fabio Valentini wrote:
> On Thu, Jun 9, 2022 at 11:38 AM Richard W.M. Jones wrote:
> >
> > Pairs of Bodhi updates which probably should be combined so the
> > packages go out together:
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-8f775872c9
On Wed, Jun 08, 2022 at 07:32:21PM +0200, Miro Hrončok wrote:
>
> Hey Mark,
>
> will rawhide builds in Koji automatically create Bodhi updates after the
> outage is over, or is there some manual action that will be required?
I'm not Mark, but there shouldn't be any manual action needed. When
On Thu, Jun 02, 2022 at 08:34:51PM -0400, Chris wrote:
> Hi,
>
> Can't seem to log into COPR; I can log into everything else, but after
> providing my correct user/pass combo and logging in, the screen just
> returns back as though I never even attempted (the log in).
>
> I tried resetting my
On Tue, May 31, 2022 at 08:59:28AM +0200, Petr Pisar wrote:
> V Tue, May 31, 2022 at 08:07:57AM +0200, Alexander Sosedkin napsal(a):
> > On Mon, May 30, 2022 at 10:34 PM Garry T. Williams
> > wrote:
> > > On Friday, April 29, 2022 5:49:05 PM EDT Ben Cotton wrote:
> > > > Cryptographic policies
On Mon, May 30, 2022 at 02:05:58PM +0200, Miro Hrončok wrote:
> On 30. 05. 22 10:09, Richard W.M. Jones wrote:
> > On Mon, May 30, 2022 at 09:31:21AM +0200, Miro Hrončok wrote:
> > > The following packages are orphaned and will be retired when they
> > > are orphaned for six weeks, unless someone
On Tue, May 24, 2022 at 07:08:00PM +0200, Miro Hrončok wrote:
> Hello Fedorans,
>
> this is a just a heads up: If I ignored your question in a Pagure issue, or
> your pull request, possibly haven't replied to your bugzilla report or a
> devel thread... it's because my email is broken and I don't
On Tue, May 24, 2022 at 04:57:54PM +0200, Jiri Vanek wrote:
>
> We are testing also upstream. note that RH is maintainer of ojdk 11 and 8,
> so we have to. But that is much easier, as the usptream is static within
> intree libraries. And we have to run also for 17 and 18/19 as we need this
>
So, just replying here since this is a nice monster of a thread. ;(
First, just to clear up some previous coments, shim does build against
the oldest stable Fedora in koji and then is manually tagged into newer
ones. This is not at all a good process. It only gets a bodhi update for
the one
On Thu, May 19, 2022 at 07:37:46AM +0200, Branislav Náter wrote:
> Hi,
>
> On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee
> wrote:
>
> > Hi,
> >
> > I am trying to request a package for RHEL 9, but I cannot find RHEL
> > under Projects at issues.redhat.com.
> > What is the correct project
On Thu, May 19, 2022 at 07:37:46AM +0200, Branislav Náter wrote:
> Hi,
>
> On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee
> wrote:
>
> > Hi,
> >
> > I am trying to request a package for RHEL 9, but I cannot find RHEL
> > under Projects at issues.redhat.com.
> > What is the correct project
On Mon, May 09, 2022 at 01:21:53PM -0400, Neal Gompa wrote:
> On Mon, May 9, 2022 at 1:13 PM Kevin Fenzi wrote:
> >
> > On Wed, May 04, 2022 at 09:45:55PM +0300, Otto Urpelainen wrote:
> > > Ondrej Nosek kirjoitti 4.5.2022 klo 18.01:
> > > > Hi all,
>
On Wed, May 04, 2022 at 09:45:55PM +0300, Otto Urpelainen wrote:
> Ondrej Nosek kirjoitti 4.5.2022 klo 18.01:
> > Hi all,
> >
> > A few months ago fedpkg introduced a change which avoids downloading source
> > files (from dist-git) that are not used in the specfile and therefore
> > downloading
On Tue, Apr 26, 2022 at 12:26:06PM +0200, Fabio Valentini wrote:
> On Mon, Apr 25, 2022 at 9:49 PM Adam Williamson
> wrote:
> > Replying to a reply because I can't find the original mail, sorry.
> >
> > I want to be easily able to *NOT* be notified of things I just did. In
> > fact this should
On Mon, Apr 25, 2022 at 04:14:03PM -0400, Matthew Miller wrote:
> On Fri, Apr 22, 2022 at 03:44:01PM +0200, Miro Hrončok wrote:
> > If I understand correctly, SSH access is a security/legal/whatever
> > no-go for nonpackagers, but can we offer some kind of standard git
> > mechanism to
On Fri, Apr 22, 2022 at 11:01:27AM -0400, Neal Gompa wrote:
> On Fri, Apr 22, 2022 at 9:54 AM Miro Hrončok wrote:
> >
> > Hello folks,
> >
> > what would it take to allow non-packagers to push to dist-git forks without
> > fedpkg?
> >
> > The instructions at
> >
On Fri, Apr 22, 2022 at 07:53:10PM +0200, Miro Hrončok wrote:
> Hello,
>
> I've been trying to debug a segfault during %check that only occurs in epel9
> Koji, but not in mock.
>
> At the end, I compared the list of packages with:
...snip...
>
> This seems like my local mock has newer c9s
o updates... not even
security updates. :(
kevin
--
>
> Kind regards,
>
> Michael Trip
>
> On Tue, 2022-04-19 at 13:14 -0700, Kevin Fenzi wrote:
> > Greetings.
> >
> > Just a reminder that ansible-core (The split out ansible 'engine')
> > will
&
Greetings.
Just a reminder that ansible-core (The split out ansible 'engine') will
be landing in RHEL8.6 (and other el builds thereafter). Also, the
ansible 2.9.x ('ansible classic') package is going to going end of life
and no longer supported in that same timeframe.
So, at that time I will be
On Tue, Apr 19, 2022 at 07:48:56PM +0200, Vít Ondruch wrote:
> I think this is broken again. Last notification I have received was at
> 03:50:49 UTC.
Yep. Restarted it.
In other news, we now have the upstream python3 version deployed in
staging and are testing it/fixing issues. After f36 is out
This change has been reworked...
https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs
If folks could take a fresh look and see if this addresses their
concerns, that would be great.
kevin
signature.asc
Description: PGP signature
___
devel mailing
Just to revive this thread, there's a proposed policy discussed at
https://pagure.io/fesco/issue/2759
and codified in https://pagure.io/fesco/fesco-docs/pull-request/61
If all interested parties could take a look and comment back here with
any changes or concerns, FESCo can move it forward.
Because there's no new business and ongoing business/voting is taking
place in tickets, todays FESCo meeting is canceled.
Announcements of decided tickets:
= Discussed and Voted in the Ticket =
Title of issue
https://pagure.io/fesco/issue/###
DECISION (+X, Y, -Z)
Change proposal: Support FIDO
On Sun, Apr 17, 2022 at 12:39:56PM -0400, Stephen John Smoogen wrote:
> On Sun, 17 Apr 2022 at 09:54, Amos wrote:
>
> > > On Wed, 1 Jun 2016 12:31:01 -0600 Erinn Looney-Triggs
> > > >
> > https://fedoraproject.org/wiki/EPEL/FAQ#Does_EPEL_replace_packages_provid...
> >
...snip bios sig plan...
Thanks for that Hans!
If that proves acceptable for change owners here that would perhaps take
care of the short term problem. What about longer term though? Would the
thought be that the BIOS sig would remain around for the forseeable
future maintaining BIOS boot? Or
On Tue, Apr 12, 2022 at 08:21:11PM -, Tom Seewald wrote:
> It's been ~1 month and I am still unable to upgrade to F36 due to the same
> issue with lilv:
>
> Error:
> Problem: lilv-0.24.10-4.fc35.i686 has inferior architecture
> - lilv-0.24.10-4.fc35.x86_64 does not belong to a
Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
irc.libera.chat.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2022-04-12 17:00 UTC'
Links to all issues to be
On Fri, Apr 08, 2022 at 08:54:02PM +0200, Vitaly Zaitsev via devel wrote:
> On 08/04/2022 19:30, Kevin Fenzi wrote:
> > We actually had IMA signing all up and running last year from jan 15th
> > to jan 22nd. As luck would have it, there was a chromium build in that
> &g
On Fri, Apr 08, 2022 at 12:20:00AM +0200, Fabio Valentini wrote:
> On Thu, Apr 7, 2022 at 11:51 PM Peter Robinson wrote:
> >
> > > > There are plenty of things in an RPM build that already inherently take
> > > > O(N) time in the number of files or the total size of the files, even
> > > >
On Fri, Apr 01, 2022 at 07:05:24PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2022 at 10:16:01AM -0700, Kevin Fenzi wrote:
> > On Fri, Apr 01, 2022 at 06:10:03PM +0100, Richard W.M. Jones wrote:
> > > On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote:
> >
On Fri, Apr 01, 2022 at 03:27:30PM -0500, Bruno Wolff III wrote:
> On Fri, Apr 01, 2022 at 10:06:35 -0700,
> Kevin Fenzi wrote:
> >
> > Short version:
> > We updated to koji 1.28.0 yesterday. It has a bug in it where it writes
> > out signed rpms as mode 0600, w
On Fri, Apr 01, 2022 at 06:10:03PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote:
> > On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote:
> > >
> > > Been waiting a couple of hours I think.
> >
On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote:
>
> Been waiting a couple of hours I think.
There's nothing in the queue waiting:
https://koji.fedoraproject.org/kojira/queue
What repo were you waiting for and what package?
kevin
signature.asc
Description: PGP signature
On Fri, Apr 01, 2022 at 11:22:34AM -0500, Bruno Wolff III wrote:
> Today's rawhide compose is taking a long time to sync on the primary
> mirrors. It has been a mix of the update from the 28th and the one for today
> for at least a couple hours. That is much longer than normal.
> Did something
On Fri, Apr 01, 2022 at 06:22:47PM +0200, Hans de Goede wrote:
> Hi,
...snip...
I don't think we should ever allow force pushes in dist git repos.
Even aside detecting if something has been built, you basically screw up
the repo for everyone else who has work in progress against it.
> 2. Or if
On Thu, Mar 31, 2022 at 06:19:06AM -0500, Ron Olson wrote:
> I submitted some builds yesterday and didn’t get any emails,
> and at least as of 6:18 CDT every link I click on the main webpage replies
> with “server is offline”.
This was likely during our scheduled outage.
On Tue, Mar 29, 2022 at 08:12:47PM +0200, Alexander Sosedkin wrote:
>
> "You know these lights in the theaters that go out gradually?
> When the guy ve-ery slo-o-owly pulls the plug out?"
> - a joke from my childhood.
>
>
> Hello, it's been quiet for a while, and I've been busy
> but kept
Planned Outage - Updates / Reboots - 2022-03-31 21:00 UTC
There will be an outage starting at 2022-03-31 21:00 UTC
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2022-03-31 21:00
Planned Outage - Updates / Reboots - 2022-03-31 21:00 UTC
There will be an outage starting at 2022-03-31 21:00 UTC
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2022-03-31 21:00
On Thu, Mar 24, 2022 at 07:09:33PM -0400, Neal Gompa wrote:
> On Thu, Mar 24, 2022 at 6:38 PM Kevin Fenzi wrote:
> >
> > On Thu, Mar 24, 2022 at 07:56:15AM -0700, Troy Dawson wrote:
> > > It was talked about December 2021, and pushed off to the new year.
> > >
On Wed, Mar 23, 2022 at 09:18:08PM -0500, Carl George wrote:
> On Wed, Mar 23, 2022 at 2:54 PM Carl George wrote:
> >
> > Typically EPEL inherits policy from Fedora, diverging when necessary.
> > Here is the corresponding section of Fedora policy.
> >
> > "All package dependencies (build-time or
On Thu, Mar 24, 2022 at 07:56:15AM -0700, Troy Dawson wrote:
> It was talked about December 2021, and pushed off to the new year.
> https://pagure.io/epel/issue/135
> It's the new year, and you are the first this year to ask for it. So, time
> to get it back in the discussions.
> Could you please
On Tue, Mar 22, 2022 at 09:27:31AM +0100, Miro Hrončok wrote:
...snip...
>
> Package (co)maintainers Status
> Change
>
> atomic-reactorcverna,
I wonder... should we stop allowing buildroot overrides?
Or at the very least add a admon to adding a new one in bodhi,
explaining that you should probibly use a side tag, etc?
kevin
signature.asc
Description: PGP signature
___
devel mailing list --
On Sat, Mar 19, 2022 at 11:07:17PM +0100, Fabio Valentini wrote:
> On Sat, Mar 19, 2022 at 11:03 PM Kevin Fenzi wrote:
> >
> > On Sat, Mar 19, 2022 at 10:58:59PM +0100, Fabio Valentini wrote:
> > >
> > > Oh, I think I know what's going on. I looked at
>
On Sat, Mar 19, 2022 at 10:58:59PM +0100, Fabio Valentini wrote:
>
> Oh, I think I know what's going on. I looked at
> src.fedoraproject.org/user/$user.
> But those group memberships are only synced if the user logs in, AFAIK?
> So ... do these packagers retain provenpackager capabilities in
>
On Sat, Mar 19, 2022 at 01:54:08PM +0100, Fabio Valentini wrote:
> On Wed, Feb 9, 2022 at 7:29 PM Ben Cotton wrote:
> >
> > In accordance with FESCo policy[1], the following provenpackagers will
> > be submitted for removal in two weeks based on a lack of Koji builds
> > submitted in the last six
On Thu, Mar 17, 2022 at 10:29:37AM +0100, Vít Ondruch wrote:
>
> Dne 07. 03. 22 v 19:12 Kevin Fenzi napsal(a):
> > I watched it over the weekend, and now it's only 3 days behind. ;(
> > Hopefully it will finish catching up... I'm continuing to watch it.
>
>
> It even
On Wed, Mar 16, 2022 at 01:55:03PM -0400, Neal Becker wrote:
> On Wed, Mar 16, 2022 at 1:45 PM Neal Becker wrote:
>
> >
> >
> > On Wed, Mar 16, 2022 at 1:38 PM Neal Becker wrote:
> >
> >> I believe it is failing on the line:
> >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py",
On Tue, Mar 15, 2022 at 01:21:09PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Tuesday, 15 March 2022 at 11:39, Dominik 'Rathann' Mierzejewski wrote:
> > Hello!
> > Has anyone else seen this?
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=84213778
> > failed on armv7hl:
> >
> >
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:
401 - 500 of 4818 matches
Mail list logo