On Wed, 2024-06-26 at 14:06 -0400, Scott Talbert wrote:
> Hi,
>
> Can someone please check this update for mesa? [1]
>
> If I'm reading the results correctly, it seems like it is waiting on
> update.server_freeipa_replication_replica for 64bit server, but if you
> click on that test, it shows
Hi,
Can someone please check this update for mesa? [1]
If I'm reading the results correctly, it seems like it is waiting on
update.server_freeipa_replication_replica for 64bit server, but if you
click on that test, it shows that test passed 3 hours ago.
Thanks,
Scott
[1]
Hi all,
Today's an important day on the Fedora Linux f40 schedule [1], with
several significant cut-offs. First of all, today is the Bodhi
updates-testing activation point [2]. That means that from now all
Fedora Linux 40 packages must be submitted to updates-testing and pass
the relevant
Hi all,
Today's an important day on the Fedora Linux f40 schedule [1], with
several significant cut-offs. First of all, today is the Bodhi
updates-testing activation point [2]. That means that from now all
Fedora Linux 40 packages must be submitted to updates-testing and pass
the relevant
Actually, someone else did that for you:
https://github.com/fedora-infra/bodhi/issues/4737
Not much mind reading! ;-)
Mattia
--
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le
On Tue, Feb 6, 2024 at 3:12 AM Christoph Junghans wrote:
>
> Hi,
>
> Has anybody seen this error before:
> FEDORA-2024-310c0537ac ejected from the push because "Cannot find
> relevant tag for gromacs-2023.4-1.fc39. None of ['f39-updates',
> 'f39-updates-pending'] are in ['epel9-next-testing',
On Mon, Feb 5, 2024 at 11:20 AM Mattia Verga via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> Hello,
> I'd like to announce that Bodhi 8.0.2 has been deployed today and brings a
> feature which was requested specifically for EPEL: from now on (if
> everything work
On Mon, Feb 5, 2024 at 9:12 PM Christoph Junghans wrote:
>
> Hi,
>
> Has anybody seen this error before:
> FEDORA-2024-310c0537ac ejected from the push because "Cannot find
> relevant tag for gromacs-2023.4-1.fc39. None of ['f39-updates',
> 'f39-updates-pending'] are in ['epel9-next-testing',
updates-testing', 'f39-updates-testing',
> 'f39-container-updates-testing', 'f39-flatpak-updates-testing']."
I have been getting that today for FEDORA-2024-8093469165.
I've tried unpushing it and the will push it again when that has been
sorted out, to see what happens, but I susp
V Mon, Feb 05, 2024 at 07:00:28PM +, Mattia Verga via devel napsal(a):
> - There should be no more Updates ejected from the composes that remain
> stuck in pending state due to wrong tags applied to their builds (or,
> better, they should be automatically pushed again after 48 hours)
> - The
Hi,
Has anybody seen this error before:
FEDORA-2024-310c0537ac ejected from the push because "Cannot find
relevant tag for gromacs-2023.4-1.fc39. None of ['f39-updates',
'f39-updates-pending'] are in ['epel9-next-testing', 'epel7-testing',
'eln-updates-testing', 'epel8-testing', 'epel9-testing',
Hello,
I'd like to announce that Bodhi 8.0.2 has been deployed today and brings a
feature which was requested specifically for EPEL: from now on (if everything
works as expected) all builds submitted as buildroot overrides for EPEL9 will
also be tagged as buildroot overrides for EPEL9N
Hello folks,
we (well, mostly kevin) have just deployed Bodhi 8.0.2 in prod.
There are several changes in the background, but what can be of some
interest for you, users and developers, are these points:
- Fixed “cannot access local variable ‘tags’” error when editing flatpak
updates
On Thu, Dec 21, 2023 at 02:13:26PM -0600, Michel Lind wrote:
> Dear all,
>
> I'm happy to be able to provide this holiday present to the infra team
> (and other interested parties) - after chasing through tens of
> dependencies, going through multiple stalled EPEL requests, and evolving
> ebranch
Dear all,
I'm happy to be able to provide this holiday present to the infra team
(and other interested parties) - after chasing through tens of
dependencies, going through multiple stalled EPEL requests, and evolving
ebranch to automate some of these pain points, the `mailman3` web
components are
On Fri, 2023-11-24 at 09:51 +, Mattia Verga via devel wrote:
> I must say this is really a rare case when an automatic update which is
> gated by failing tests and stuck in testing
It's really not *that* rare any more, since we do quite extensive
gating of critical path updates on openQA
I make
>>>> sure that doesn't happen?
>>>>
>>>> As it's for rawhide, I didn't create the Bodhi update, and I don't see
>>>> an option to delete it.
>>>>
>>> There's no option to delete Bodhi updates. It can only be done by
>>>
admins intervening, your only option
is to bump a release and do new build. The old, stuck update will get
superseded by the new update.
This is unfair. I remember times when there was no bodhi updates for rawhide - when you build something in rawhide it
went to next compose and there was nothing
; > >
> > > As it's for rawhide, I didn't create the Bodhi update, and I
> > > don't see
> > > an option to delete it.
> > >
> > There's no option to delete Bodhi updates. It can only be done by
> > hacking the database directly, but it is usu
; > > As it's for rawhide, I didn't create the Bodhi update, and I don't see
> > > an option to delete it.
> > >
> > There's no option to delete Bodhi updates. It can only be done by
> > hacking the database directly, but it is usually never necessary.
> >
* Mattia Verga via devel:
> Il 23/11/23 16:40, Florian Weimer ha scritto:
>> I've got an update that I don't see pushed to stable. How do I make
>> sure that doesn't happen?
>>
>> As it's for rawhide, I didn't create the Bodhi update, and I don't see
>> an
Il 23/11/23 16:40, Florian Weimer ha scritto:
> I've got an update that I don't see pushed to stable. How do I make
> sure that doesn't happen?
>
> As it's for rawhide, I didn't create the Bodhi update, and I don't see
> an option to delete it.
>
There's no option to delete Bod
On Thu, Nov 23, 2023 at 4:40 PM Florian Weimer wrote:
>
> I've got an update that I don't see pushed to stable. How do I make
> sure that doesn't happen?
>
> As it's for rawhide, I didn't create the Bodhi update, and I don't see
> an option to delete it.
If it's still pe
V Thu, Nov 23, 2023 at 04:40:39PM +0100, Florian Weimer napsal(a):
> I've got an update that I don't see pushed to stable. How do I make
> sure that doesn't happen?
>
> As it's for rawhide, I didn't create the Bodhi update, and I don't see
> an option to delete it.
>
That's th
I've got an update that I don't see pushed to stable. How do I make
sure that doesn't happen?
As it's for rawhide, I didn't create the Bodhi update, and I don't see
an option to delete it.
Thanks,
Florian
--
___
devel mailing list -- devel
t; back
> > the previous soname.
> >
> > Apologies for the troubles.
>
> Hello,
>
> this is not the first time I saw a bodhi update that breaks dozens of
> dependencies, goes unnoticed for a week and is automatically pushed stable,
> only to discover many packag
t; back
> > the previous soname.
> >
> > Apologies for the troubles.
>
> Hello,
>
> this is not the first time I saw a bodhi update that breaks dozens of
> dependencies, goes unnoticed for a week and is automatically pushed stable,
> only to discover many packag
On Tue, Nov 07, 2023 at 04:20:52PM +0100, Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
> > this is not the first time I saw a bodhi update that breaks dozens of
> > dependencies, goes unnoticed for a week and is automatically pushed
> > stable, only to discov
Miro Hrončok wrote:
> this is not the first time I saw a bodhi update that breaks dozens of
> dependencies, goes unnoticed for a week and is automatically pushed
> stable, only to discover many packages fail to install.
The most important measure would be to abolish automatic pushes. Th
-3.6.2-8.really3.5.3.fc37 to address this, please don't
rebuild any dependencies in the meantime, as the new package will bring back
the previous soname.
Apologies for the troubles.
Hello,
this is not the first time I saw a bodhi update that breaks dozens of
dependencies, goes unnoticed
-3.6.2-8.really3.5.3.fc37 to address this, please don't
rebuild any dependencies in the meantime, as the new package will bring back
the previous soname.
Apologies for the troubles.
Hello,
this is not the first time I saw a bodhi update that breaks dozens of
dependencies, goes unnoticed
On 10/25/23 19:14, Mattia Verga via devel wrote:
Il 25/10/23 12:54, Tomas Hrcka ha scritto:
This looks like a bug in bodhi.
Actually, it was done that way on purpose. The HTML rendered output
shows frozen releases in the same table of pending releases by a hack,
but for API purposes I just
Il 25/10/23 12:54, Tomas Hrcka ha scritto:
> This looks like a bug in bodhi.
>
Actually, it was done that way on purpose. The HTML rendered output
shows frozen releases in the same table of pending releases by a hack,
but for API purposes I just let the output being pedantic about the
req
On 10/25/23 15:17, Clement Verna wrote:
On Wed, 25 Oct 2023 at 12:55, Tomas Hrcka <mailto:thr...@redhat.com>> wrote:
This looks like a bug in bodhi.
the web UI lists correct releases pending and current.
On Wed, Oct 25, 2023 at 11:57 AM Pavel Březina mailto:pbrez...@r
On Wed, Oct 25, 2023 at 3:17 PM Clement Verna wrote:
>
> On Wed, 25 Oct 2023 at 12:55, Tomas Hrcka wrote:
>>
>> This looks like a bug in bodhi.
>>
>> the web UI lists correct releases pending and current.
>>
>> On Wed, Oct 25, 2023 at 11:57 AM Pavel Bř
On Wed, 25 Oct 2023 at 12:55, Tomas Hrcka wrote:
> This looks like a bug in bodhi.
>
> the web UI lists correct releases pending and current.
>
> On Wed, Oct 25, 2023 at 11:57 AM Pavel Březina
> wrote:
> >
> > Hi,
> > Fedora 39 stopped showing in pen
This looks like a bug in bodhi.
the web UI lists correct releases pending and current.
On Wed, Oct 25, 2023 at 11:57 AM Pavel Březina wrote:
>
> Hi,
> Fedora 39 stopped showing in pending releases (and is not in current
> either) when using:
>
> curl https://bodhi.fedorapr
or is it a bodhi bug?
We rely on this information to automatically pick up fedora versions for
SSSD PR CI.
Thanks.
Pavel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code
Hi all,
Today's an important day on the Fedora Linux 39 schedule [1], with
several significant cut-offs. First of all, today is the Bodhi
updates-testing activation point [2]. That means that from now all
Fedora Linux 39 packages must be submitted to updates-testing and pass
the relevant
Hi all,
Today's an important day on the Fedora Linux 39 schedule [1], with
several significant cut-offs. First of all, today is the Bodhi
updates-testing activation point [2]. That means that from now all
Fedora Linux 39 packages must be submitted to updates-testing and pass
the relevant
On Fri, 2023-08-04 at 23:43 +0100, Adam Williamson wrote:
>
> Practically speaking, we should be able to just re-run the tests and it
> should come out good. I'll bonk that button now.
Ah, as the failure wasn't a gating one, Bodhi doesn't show the Re-
Trigger Tests button. So I
On Fri, 2023-08-04 at 15:40 +0200, Dan Horák wrote:
> Hi,
>
> seems there is an issue with the test results presented in bodhi, please
> see https://bodhi.fedoraproject.org/updates/FEDORA-2023-94f22746e1
>
> bodhi thinks fedora-ci.koji-build.rpmdeplint.functional failed (it's
Hi,
seems there is an issue with the test results presented in bodhi, please
see https://bodhi.fedoraproject.org/updates/FEDORA-2023-94f22746e1
bodhi thinks fedora-ci.koji-build.rpmdeplint.functional failed (it's
"red"), but when I click on the test in bodhi testing farm say "pas
On Mon, Jun 26, 2023 at 3:59 PM Richard W.M. Jones wrote:
>
> eg:
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-b95ba15d84
>
> Preparing the system for testing...
> Ignoring "--fixrepo" option as it has no effect on Fedora profiles
> Enabling buildroot repository...
> Unknown argument
eg:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-b95ba15d84
Preparing the system for testing...
Ignoring "--fixrepo" option as it has no effect on Fedora profiles
Enabling buildroot repository...
Unknown argument "config-manager" for command "dnf5". Add "--help" for more
information about
On Wednesday, 31 May 2023 at 09:08, Mattia Verga via devel wrote:
> Il 30/05/23 22:15, Adam Williamson ha scritto:
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-f563346d4d is
> > similar, but this time it was ejected from its push *to stable* (not to
> > testing), again allegedly for
Il 30/05/23 22:15, Adam Williamson ha scritto:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-2b17e1e469 is stuck
> because it was ejected from its initial push to testing,
> which means the 7 day push to stable timer never really kicks in
> (it needs to be *in testing* for seven days).
Il 30/05/23 22:15, Adam Williamson ha scritto:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-f563346d4d is
> similar, but this time it was ejected from its push *to stable* (not to
> testing), again allegedly for a missing tag. The builds have now
> actually been deleted(!), so that
On Tue, May 30, 2023 at 4:16 PM Adam Williamson
wrote:
> On Tue, 2023-05-30 at 21:52 +0200, Mikel Olasagasti wrote:
> > Hi all,
> >
> > There are currently 157 updates in testing or pending status in Bodhi
> > that were created before 2023:
> >
> >
&g
On Tue, 2023-05-30 at 16:45 -0700, Brian C. Lane wrote:
> On Tue, May 30, 2023 at 01:15:08PM -0700, Adam Williamson wrote:
>
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf8feea173
>
> Thanks for the heads up, I don't see anything in the UI allowing me to
> rerun the test (or waive
On Tue, 2023-05-30 at 16:45 -0700, Brian C. Lane wrote:
> On Tue, May 30, 2023 at 01:15:08PM -0700, Adam Williamson wrote:
>
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf8feea173
>
> Thanks for the heads up, I don't see anything in the UI allowing me to
> rerun the test (or waive
On Tue, May 30, 2023 at 01:15:08PM -0700, Adam Williamson wrote:
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf8feea173
Thanks for the heads up, I don't see anything in the UI allowing me to
rerun the test (or waive it, but I'd rather see the logs from the
failure first).
Not sure
On Tue, May 30, 2023 at 09:52:11PM +0200, Mikel Olasagasti wrote:
> Hi all,
>
> There are currently 157 updates in testing or pending status in Bodhi
> that were created before 2023:
>
> https://bodhi.fedoraproject.org/updates/?search=_before=2023=pending=testing=1
>
On Tue, 2023-05-30 at 21:52 +0200, Mikel Olasagasti wrote:
> Hi all,
>
> There are currently 157 updates in testing or pending status in Bodhi
> that were created before 2023:
>
> https://bodhi.fedoraproject.org/updates/?search=_before=2023=pending=testing=1
>
> There
Hi all,
There are currently 157 updates in testing or pending status in Bodhi
that were created before 2023:
https://bodhi.fedoraproject.org/updates/?search=_before=2023=pending=testing=1
There are 7 Fedora updates, 6 for Fedora-37 and one in
pending->testing status for Fedora-35. The r
Il 30/03/23 01:26, Miro Hrončok ha scritto:
> On 28. 03. 23 10:57, Mattia Verga via devel wrote:
>> Most of the updates which have notes longer than 10k characters are
>> rawhide automatic updates which copies the RPM changelog over and over,
> What will happen now, when an automatic rawhide like
On 28. 03. 23 10:57, Mattia Verga via devel wrote:
Most of the updates which have notes longer than 10k characters are
rawhide automatic updates which copies the RPM changelog over and over,
What will happen now, when an automatic rawhide like this is created? Will the
notes be truncated, or
On 28. 03. 23 10:57, Mattia Verga via devel wrote:
I want to point out that copying the full upstream
changelogs into updates notes is not recommended.
It's actually forbidden.
https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs
"They must never simply contain an entire
On Wed, 2023-03-29 at 13:11 -0700, Kevin Fenzi wrote:
> On Wed, Mar 29, 2023 at 11:24:40AM -0700, Adam Williamson wrote:
> > On Tue, 2023-03-28 at 08:57 +, Mattia Verga via devel wrote:
> > >
> > > Other changes between the currently deployed Bodhi 7.0.1 and the
&
On Wed, Mar 29, 2023 at 11:24:40AM -0700, Adam Williamson wrote:
> On Tue, 2023-03-28 at 08:57 +, Mattia Verga via devel wrote:
> >
> > Other changes between the currently deployed Bodhi 7.0.1 and the
> > upcoming Bodhi 7.1.1 I encourage you to look at the upstream c
On Tue, 2023-03-28 at 08:57 +, Mattia Verga via devel wrote:
>
> Other changes between the currently deployed Bodhi 7.0.1 and the
> upcoming Bodhi 7.1.1 I encourage you to look at the upstream changelog
> at https://github.com/fedora-infra/bodhi/releases
So another fairly no
Hello folks,
Bodhi will probably be upgraded to 7.1.1 before the F38 final freeze and
I want to highlight a notable change which may impact update
submissions. The change is that update notes field will now be limited
to 10k characters length.
The request came from https://github.com/fedora-infra
On Sat, 2023-03-04 at 02:25 +0100, Fabio Valentini wrote:
> On Sat, Mar 4, 2023, 02:21 Adam Williamson
> wrote:
>
> > On Fri, 2023-03-03 at 15:31 -0800, Adam Williamson wrote:
> > >
> > > Interestingly, this is only the case for the F38 update. Check the F39
> > > update:
> > >
On Sat, Mar 4, 2023, 02:21 Adam Williamson
wrote:
> On Fri, 2023-03-03 at 15:31 -0800, Adam Williamson wrote:
> >
> > Interestingly, this is only the case for the F38 update. Check the F39
> > update:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2023-23789cd657
> >
> > it's *only* in
On Fri, 2023-03-03 at 15:31 -0800, Adam Williamson wrote:
>
> Interestingly, this is only the case for the F38 update. Check the F39
> update:
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-23789cd657
>
> it's *only* in @critical-path-build, it's not in @core or the kde,
> gnome or server
On 04. 03. 23 0:31, Adam Williamson wrote:
On Fri, 2023-03-03 at 22:24 +0100, Miro Hrončok wrote:
On 03. 03. 23 20:10, Adam Williamson wrote:
On Fri, 2023-03-03 at 18:37 +0100, Miro Hrončok wrote:
Hello,
I've noticed in
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
On Fri, 2023-03-03 at 22:24 +0100, Miro Hrončok wrote:
> On 03. 03. 23 20:10, Adam Williamson wrote:
> > On Fri, 2023-03-03 at 18:37 +0100, Miro Hrončok wrote:
> > > Hello,
> > > I've noticed in
> > >
> > > https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
> > >
On 03. 03. 23 20:10, Adam Williamson wrote:
On Fri, 2023-03-03 at 18:37 +0100, Miro Hrončok wrote:
Hello,
I've noticed in
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
On Fri, 2023-03-03 at 18:37 +0100, Miro Hrončok wrote:
> Hello,
> I've noticed in
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
>
> That the
Hello,
I've noticed in
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f34afe57a9
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a61dbc3c1d
That the update is marked as critpath (which is probably correct because
On Fri, Feb 03, 2023 at 05:27:06PM -0700, Orion Poplawski wrote:
>
> Thanks, but no go:
>
> bodhi updates trigger-tests FEDORA-2023-96ebcd6f4d
> Login successful!
> Traceback (most recent call last):
This may well be because those updates are in a updates push right n
don't
see that now. Is my only option to waive the test results?
Try a command line: bodhi updates trigger-tests FEDORA-2023-96ebcd6f4d.
Thanks, but no go:
bodhi updates trigger-tests FEDORA-2023-96ebcd6f4d
Login successful!
Traceback (most recent call last):
File "/usr/lib/python3.11
see that now. Is my only option to waive the test results?
>
Try a command line: bodhi updates trigger-tests FEDORA-2023-96ebcd6f4d.
-- Petr
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To u
I've got a couple updates with missing tests:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-96ebcd6f4d
https://bodhi.fedoraproject.org/updates/FEDORA-2023-23e26fcc32
it seems like I used to have the option to resubmit the tests but I
don't see that now. Is my only option to waive the
No worries. Thanks!
On 1/27/23 19:41, Davide Cavalca wrote:
On 2023-01-27 10:34, Christopher Klooz wrote:
Hi,
I just saw that a package (x11docker) seems to be orphaned: we ship a
very old release (many releases since June 2021), and when reviewing
the release notes of subsequent releases on
On 2023-01-27 10:34, Christopher Klooz wrote:
Hi,
I just saw that a package (x11docker) seems to be orphaned: we ship a
very old release (many releases since June 2021), and when reviewing
the release notes of subsequent releases on github of that package, I
think this old release (from June
Hi,
I just saw that a package (x11docker) seems to be orphaned: we ship a
very old release (many releases since June 2021), and when reviewing the
release notes of subsequent releases on github of that package, I think
this old release (from June 2021) should no longer be deployed: see
On Tue, 2023-01-17 at 05:39 +, Mattia Verga via devel wrote:
> Hello folks,
>
> I'd like to announce that Bodhi 7.0.1 has been deployed to production.
> Apart from a webUI new look, due to the switch to fedora-bootstrap 2.x,
> these are the main changes that may interest yo
Yay! Thank you!
--
Bojan
-Original Message-
From: Mattia Verga
Reply-To: devel@lists.fedoraproject.org
To: devel-annou...@lists.fedoraproject.org
Subject: Bodhi 7.0.1 deployed to prod
Date: 17/01/23 16:39:49
- Frozen releases updates will now be forced into testing before being
pushed
On Tue, Jan 17, 2023 at 7:05 PM Mattia Verga via devel
wrote:
>
> Il 17/01/23 12:54, Miro Hrončok ha scritto:
> >
> > Is it possible that bodhi no longer automatically recognizes the changelog
> > of
> > Rawhide updates?
> >
> > See before the updat
Il 17/01/23 12:54, Miro Hrončok ha scritto:
>
> Is it possible that bodhi no longer automatically recognizes the changelog of
> Rawhide updates?
>
> See before the update:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-9090058f62
>
> And after:
>
> https:
On 17/01/2023 16:15, Fabio Valentini wrote:
On Tue, Jan 17, 2023 at 4:13 PM Richard Shaw wrote:
On Tue, Jan 17, 2023 at 8:18 AM Arthur Bols wrote:
On 17/01/2023 14:57, Stephen Smoogen wrote:
So bodhi and pagure are at different datacenters with hopefully different
network paths. Could
On Tue, Jan 17, 2023 at 4:13 PM Richard Shaw wrote:
>
> On Tue, Jan 17, 2023 at 8:18 AM Arthur Bols wrote:
>>
>> On 17/01/2023 14:57, Stephen Smoogen wrote:
>> > So bodhi and pagure are at different datacenters with hopefully different
>> > network paths. Cou
On Tue, Jan 17, 2023 at 8:18 AM Arthur Bols wrote:
> On 17/01/2023 14:57, Stephen Smoogen wrote:
> > So bodhi and pagure are at different datacenters with hopefully different
> > network paths. Could people do some mtr or traceroutes from their
> locations
> > so we can s
On Tue, Jan 17, 2023 at 8:21 AM Stephen Smoogen wrote:
>
>
> On Tue, 17 Jan 2023 at 09:19, Arthur Bols wrote:
>
>> On 17/01/2023 14:57, Stephen Smoogen wrote:
>> > So bodhi and pagure are at different datacenters with hopefully
>> different
>> &g
On Tue, 17 Jan 2023 at 09:19, Arthur Bols wrote:
> On 17/01/2023 14:57, Stephen Smoogen wrote:
> > So bodhi and pagure are at different datacenters with hopefully different
> > network paths. Could people do some mtr or traceroutes from their
> locations
> > so we can s
On 17/01/2023 14:57, Stephen Smoogen wrote:
So bodhi and pagure are at different datacenters with hopefully different
network paths. Could people do some mtr or traceroutes from their locations
so we can see if this can be ironed out. Currently the limited tools we
have in Fedora Infra
ng delays between sending a
>> query
>> > > and
>> > > receiving the response. However, no HTTP errors.
>> > >
>> >
>> > I only got the timeout once, but it's been very slow and not properly
>> > loading completely. I'm trying bodhi com
> >
> > I only got the timeout once, but it's been very slow and not properly
> > loading completely. I'm trying bodhi command line for an update and
> having
> > similar issues but I think my update did finally get created though.
> >
> > One of the attemp
gt; >
> > Since yesterday I randomly experience long delays between sending a query
> > and
> > receiving the response. However, no HTTP errors.
> >
>
> I only got the timeout once, but it's been very slow and not properly
> loading completely. I'm trying bodhi com
> and
> receiving the response. However, no HTTP errors.
>
I only got the timeout once, but it's been very slow and not properly
loading completely. I'm trying bodhi command line for an update and having
similar issues but I think my update did finally get created though.
One of the att
V Tue, Jan 17, 2023 at 07:28:32AM -0600, Richard Shaw napsal(a):
> Is anyone but me experiencing this? I want to know before I call C Spire.
>
Since yesterday I randomly experience long delays between sending a query and
receiving the response. However, no HTTP errors.
-- Petr
signature.asc
Is anyone but me experiencing this? I want to know before I call C Spire.
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Hello folks,
I'd like to announce that Bodhi 7.0.1 has been deployed to production.
Apart from a webUI new look, due to the switch to fedora-bootstrap 2.x,
these are the main changes that may interest you:
- Bodhi client now autenticates using Kerberos by default and falls back
to browser-based
Hello folks,
I'd like to announce that Bodhi 7.0.1 has been deployed to production.
Apart from a webUI new look, due to the switch to fedora-bootstrap 2.x,
these are the main changes that may interest you:
- Bodhi client now autenticates using Kerberos by default and falls back
to browser-based
On 17. 01. 23 1:07, Kevin Fenzi wrote:
Hey folks, just a heads up that bodhi has been updated to 7.0.1 now.
https://bodhi.fedoraproject.org
See:
https://github.com/fedora-infra/bodhi/releases
for a full list of bugs fixed/enhancements.
Note that this adds the concept of 'frozen' releases
Hey folks, just a heads up that bodhi has been updated to 7.0.1 now.
https://bodhi.fedoraproject.org
See:
https://github.com/fedora-infra/bodhi/releases
for a full list of bugs fixed/enhancements.
Note that this adds the concept of 'frozen' releases, which will:
* show a warning / note
Hey folks, just a heads up that bodhi has been updated to 7.0.1 now.
https://bodhi.fedoraproject.org
See:
https://github.com/fedora-infra/bodhi/releases
for a full list of bugs fixed/enhancements.
Note that this adds the concept of 'frozen' releases, which will:
* show a warning / note
Il 07/01/23 09:31, Mattia Verga ha scritto:
> I've attempted to build an updated bodhi-server release for testing it
> into staging, just a few more commits which fixes some glitches in the
> web UI. However, running the tests in Koji fail both on F36 and F
I've attempted to build an updated bodhi-server release for testing it
into staging, just a few more commits which fixes some glitches in the
web UI. However, running the tests in Koji fail both on F36 and F37:
E subprocess.CalledProcessError: Command '['dnf',
'--disablerepo
1 - 100 of 2038 matches
Mail list logo
