[Bug 2212782] perl-HTTP-OAI-4.13 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2212782



--- Comment #5 from Fedora Update System  ---
FEDORA-2023-ed3cc3a007 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-ed3cc3a007`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed3cc3a007

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2212782

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202212782%23c5
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2212782] perl-HTTP-OAI-4.13 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2212782

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-4ed60aa04c has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-4ed60aa04c`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-4ed60aa04c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2212782

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202212782%23c4
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-becb7041de   
perl-HTML-StripScripts-1.06-22.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-423bcaf739   
radare2-5.8.6-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-787571a7ba   
chromium-114.0.5735.106-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

barman-3.5.0-3.el7
tito-0.6.23-1.el7

Details about builds:



 barman-3.5.0-3.el7 (FEDORA-EPEL-2023-387c8ef0a9)
 Backup and Recovery Manager for PostgreSQL

Update Information:

Adjust dependencies when pep-0440 is applied.

ChangeLog:

* Tue Jun 13 2023 Simone Caronni  - 3.5.0-3
- Remove Python dependencies version, pep-0440 is enforced when building
  packages.

References:

  [ 1 ] Bug #2214012 - dnf install barman fails on python3dist error
https://bugzilla.redhat.com/show_bug.cgi?id=2214012




 tito-0.6.23-1.el7 (FEDORA-EPEL-2023-107aae49e7)
 A tool for managing rpm based git projects

Update Information:

https://github.com/rpm-software-management/tito/releases/tag/tito-0.6.23-1

ChangeLog:

* Tue Jun 13 2023 Jakub Kadlcik  0.6.23-1
- Replace `submodule--helper list` with `git config --get-regexp`
- do not overwrite packit.yaml and its variants (msu...@redhat.com)
- packit: fixing the Fedora build failures (prais...@redhat.com)
- Don't upload patches to the lookaside cache (fros...@email.cz)
- use spdx license (msu...@redhat.com)


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

ACPI-related bug in 6.3.X? At least an issue in ucsi_acpi, affecting several systems

[Christopher Klooz via devel]

In case you are already aware of the issue, feel free to ignore this 
mail. I just want to make aware that there could be multiple 
interrelated (bug) reports that might be considered in conjunction and 
not on their own, given that the amount of affected users is above 
average (I could imagine this is not limited to ask.Fedora).


As far as it concerns ask.Fedora: since 6.3 was introduced, we have many 
users in ask.Fedora with issues that seem to be ACPI related (more 
precisely, `ucsi_acpi`, but maybe not just this) and that makes it 
impossible to use kernels after 6.2.15 except with 
`module_blacklist=ucsi_acpi`.


I already asked the users to provide a bug report (this is how I became 
aware that the report template was broken ;), but I am not sure if the 
report(s) illustrate the number of users that have come up with the same 
issue. Since not all users with issues end up on ask.Fedora, we don't 
know the actual number of affected systems, but so many users with the 
same kernel issue is a seldom phenomenon.


So far, most users with 6.3.X ACPI-related issues are found in this topics:

https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading-to-kernel-6-3-4/83605/

-> black screen after grub menu with stable kernels after 6.2.15
-> everything fine with 6.2.15
-> mitigation: module_blacklist=ucsi_acpi (several users confirmed this 
to mitigate the issue)


Links to the related bug reports are contained.

The nvidia-driver issue that has accidentally merged in this topic is 
something different (the nvidia case is alredy solved anyway by an 
earlier kernel fix). The case in which already 6.2.15 was affected seems 
to be something different as well.


Except those nvidia-driver-users where a fixed kernel already solved the 
issue, in the cases where we identified it, affected users had `cat 
/proc/sys/kernel/tainted` = 0. Of course not all useres provided 
documentation so we cannot know for sure if that applies to all.


Additionally, it might be noted that we have further reports on 
ask.Fedora where users have issues that could have a link to ACPI, but 
not to `ucsi_acpi` in specific - so far it is only the correlation that 
6.2.15 works but everything later not, and that the respectively 
described issue could be explained by ACPI-related bugs (don't know 
yet). One F37 user consolidated their data in this bug report: 
https://bugzilla.redhat.com/show_bug.cgi?id=2213179 -> here the 
mitigation is removing the KVM switch in between system and monitor, 
although it works fine in 6.2.15. I think that's all reports with 
noteworthy data/documentation.


Not sure if we have further related reports elsewhere. Also, I check at 
the moment only those topics that are explicitly added to the #kernel 
category since I have little time, so maybe we have more reports about it.


Best,
Chris
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Modules without modularity

[Brad Smith]

Is this thread on alternatives to alternatives also relevant:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4AUQVBKLQBU6LIWZGVXN2CM3XTYQAKXZ/#4AUQVBKLQBU6LIWZGVXN2CM3XTYQAKXZ
?

Modules provide a mechanism for system level switches between
alternative versions as does Petr's  proposal (i.e. sudo required). As
others have remarked, there is also a need for a similar capability at
the user level (without sudo; e.g. environment modules) or even at the
shell level.

It would be nice if there were a compendium of all similar options for Fedora.

On Tue, Jun 13, 2023 at 12:21 PM Christopher  wrote:
>
> On Tue, Jun 13, 2023 at 12:33 PM Petr Pisar  wrote:
> >
> > Hello,
> >
> > as it seems that module build infrastructure isn't getting any better, as
> > modular YUM repositories are going to be deconfigured
> > ,
> > there is a time to look at different ways how to package alternative 
> > content.
> >

best regards

Brad
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

[Miro Hrončok]

On 13. 06. 23 14:02, Tomas Hrnciar wrote:

Hello,

in order to deliver Python 3.12, we are running a coordinated rebuild in a side 
tag.


https://fedoraproject.org/wiki/Changes/Python3.12 



We anticipate starting this rebuildsometimethis week.

If you see a "Rebuilt for Python 3.12" (or similar) commit in your package, 
please don't rebuild it in regular rawhideor another rawhide side tag. If you 
need to, please let us know, so we can coordinate.


If you'd like to build apackageafter we already rebuilt it, you should be able 
to build it in the side tag via:


on branch rawhide:
$ fedpkg build --target=f39-python
$ koji wait-repo f39-python --build 

Note that it will take a while before all the essential packages are rebuilt, 
so don't expect all your dependencies to be available right away. Please, don't 
attempt to build your package in the side tag before we do.
When in trouble, ask here or on IRC (#fedora-python on Libera.Chat). Ping me 
(thrnciar) or Miro (mhroncok) if you need to talk to us.


Builds: 
https://koji.fedoraproject.org/koji/builds?latest=0=f39-python=-build_id=0 


Please avoid any potentially disturbing or major changes in Python packages 
until the rebuild is over.


Thanks. Let us know if you have any questions.


FTR it has started.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

[Miro Hrončok]

On 13. 06. 23 14:02, Tomas Hrnciar wrote:

Hello,

in order to deliver Python 3.12, we are running a coordinated rebuild in a side 
tag.


https://fedoraproject.org/wiki/Changes/Python3.12 



We anticipate starting this rebuildsometimethis week.

If you see a "Rebuilt for Python 3.12" (or similar) commit in your package, 
please don't rebuild it in regular rawhideor another rawhide side tag. If you 
need to, please let us know, so we can coordinate.


If you'd like to build apackageafter we already rebuilt it, you should be able 
to build it in the side tag via:


on branch rawhide:
$ fedpkg build --target=f39-python
$ koji wait-repo f39-python --build 

Note that it will take a while before all the essential packages are rebuilt, 
so don't expect all your dependencies to be available right away. Please, don't 
attempt to build your package in the side tag before we do.
When in trouble, ask here or on IRC (#fedora-python on Libera.Chat). Ping me 
(thrnciar) or Miro (mhroncok) if you need to talk to us.


Builds: 
https://koji.fedoraproject.org/koji/builds?latest=0=f39-python=-build_id=0 


Please avoid any potentially disturbing or major changes in Python packages 
until the rebuild is over.


Thanks. Let us know if you have any questions.


FTR it has started.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Modules without modularity

[Christopher]

On Tue, Jun 13, 2023 at 12:33 PM Petr Pisar  wrote:
>
> Hello,
>
> as it seems that module build infrastructure isn't getting any better, as
> modular YUM repositories are going to be deconfigured
> ,
> there is a time to look at different ways how to package alternative content.
>
> There are few aproaches, like compat packages, or full namespacing (Python).
> Yet modularity had some unique features, especially retaining nonmangled
> package names and other RPM dependencies.
>
> I spent some time thinking how to approximate the nice features with current
> state of RPM, Koji, and DNF and come up with this approach
> . The linked approach achieves
> it at the expense of dedicated build targets and an inability to introduce
> completely new modules (as opposite to new streams of existing modules) after
> releasing an installation media.
>
> Comments are welcome.
>
> -- Petr

(First the negative... don't worry, it's not all negative)
I wonder why we need this at all. I believe that modularity has failed
to gain a foothold in Fedora, just like scl before it, because Fedora
just doesn't need this. One of the best things about Fedora is the
dependency-convergence and curated nature of all the packaged
versions, so that everything works out of the box. The use cases for
alternative versions are edge cases that the vast majority of users do
not need or care about. And the ones that most users do care about
(making sure their application works) are usually satisfied with
compat packaging, when needed.

So much (over-?)engineering has gone into such niche use cases, and
Fedora is arguably no better off for all that effort. Nowadays, it's
so easy to spin up a VM or container using older versions of things,
if you need them, or you can use snaps or flatpaks, or
language-specific version management tools like mvn or rvm, for the
developer use cases. What is the real benefit to Fedora to continue to
push down the path of alternative, mutually-exclusive streams that
affect the entire system? My experience struggling with modularity as
a casual packager, and as a user, has left a bad taste in my mouth for
any similar attempts, and I'm highly skeptical of the need of such a
thing (and bracing for the impact when it all comes crashing down on
my favorite OS due to unintended consequences).

(Now the positive)
That said, I like the simplicity of your approach, using metapackages
and native RPM tooling to handle the situation. However niche the use
case is, having such a simple approach means that it's merely a matter
of documenting some guidelines for packagers to follow if they have
need of that situation. I still think that the need for that will be
rare, and wonder how many of these kinds of metapackages would
actually get created in Fedora. I suspect that it would be very few.
But the important bit is that if they do get created, they are
unlikely to affect me unless I want to use them. This is very
different from modularity, which seemed to have a downstream impact on
everybody, especially when you were forced to use modularity if your
dependencies were... which I think was enough to oust a lot of casual
packagers, because they had to understand a whole new dimension of
packaging guidelines and tooling. Your approach requires none of that.

The one downside to your approach, that I think was an early selling
point of modularity, is that yours kind of requires that the
alternative streams are built for every Fedora version. I think
modularity marketed itself as being able to have a module whose
version lifetimes were longer than OS release cycles (which could
reduce packager workload for streams that were slow-moving and didn't
change across Fedora releases). I don't know how much that actually
happened in practice, though, so I don't know if anybody will care
about that difference in your approach.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Summary/Minutes from today's FESCo Meeting (2023-06-13)

[Fabio Valentini]

===
#fedora-meeting: FESCo (2023-06-13)
===


Meeting started by decathorpe at 17:00:25 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-06-13/fesco.2023-06-13-17.00.log.html
.



Meeting summary
---
* Init Process  (decathorpe, 17:01:05)
  * LINK:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/2Q7NDMZEQS5L4UZNTLL2HOB3ZE5P75RH/
Schedule  (decathorpe, 17:06:03)

* #3008 Change: Build JDKs once, repack everywhere  (decathorpe,
  17:06:59)
  * AGREED: REJECTED (+4, 0, -2): Change proposal is not accepted as-is
(decathorpe, 17:36:50)
  * AGREED: AGREED (+6, 0, -0) The change owners will discuss the actual
workflow with rleng and update the change proposal accordingly,
resubmitting it when ready.  (decathorpe, 17:44:37)

* Next Week's Chair 晴  (decathorpe, 17:47:44)
  * ACTION: zbyszek to set up a whenisgood poll  (decathorpe, 17:55:28)
  * Chair for the meeting in ~two weeks will be determined based on the
new meeting day / time  (decathorpe, 17:55:48)

* Open Floor  (decathorpe, 17:55:54)

Meeting ended at 17:59:01 UTC.




Action Items

* zbyszek to set up a whenisgood poll




Action Items, by person
---
* zbyszek
  * zbyszek to set up a whenisgood poll
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* mhroncok (63)
* decathorpe (59)
* sgallagh (47)
* nirik (37)
* zbyszek (31)
* jvanek (30)
* zodbot (14)
* tstellar (14)
* zbyszek[m] (1)
* dcantrell (0)
* music (0)
* mhayden (0)
* Conan_Kudo (0)
* Pharaoh_Atem (0)
* Son_Goku (0)
* King_InuYasha (0)
* Sir_Gallantmon (0)
* Eighth_Doctor (0)




Generated by `MeetBot`_ 0.4

.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora Copr builders updated to Fedora 38

[Stephen Gallagher]

On Tue, Jun 13, 2023 at 8:44 AM Kevin Kofler via devel
 wrote:
>
> Kevin Kofler via devel wrote:
> > Gary Buhrmaster wrote:
> >> Well, EL6 ELS support is still available for (around)
> >> another year, so it is a nice to have to support those
> >> limping along with EL6, but I would generally agree
> >> with the principal that if supporting a product past
> >> official EOL becomes overly onerous that support
> >> should end, or be explicitly funded out of the ELS
> >> fees if the ELS community needs that support.
> >
> > EPEL is not covered by ELS, hence EPEL is already EOL.
>
> PS: I also do not see why Fedora should be supporting the users of a
> commercial subscription scheme with free services such as Copr.
>

First, let me be clear: I agree with you and Smooge that EPEL 6 should
already be dead in COPR. That said, Fedora *itself* is a free service
supporting the users of and funded by a commercial subscription
offering. No need to support good arguments with flawed ones.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Modules without modularity

[Petr Pisar]

Hello,

as it seems that module build infrastructure isn't getting any better, as
modular YUM repositories are going to be deconfigured
,
there is a time to look at different ways how to package alternative content.

There are few aproaches, like compat packages, or full namespacing (Python).
Yet modularity had some unique features, especially retaining nonmangled
package names and other RPM dependencies.

I spent some time thinking how to approximate the nice features with current
state of RPM, Koji, and DNF and come up with this approach
. The linked approach achieves
it at the expense of dedicated build targets and an inability to introduce
completely new modules (as opposite to new streams of existing modules) after
releasing an installation media.

Comments are welcome.

-- Petr


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 Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Packaging coccinelle in EPEL9

[Martin Oliveira]

Hello,

I'm wondering if there is anyone interested in packaging coccinelle [1] for 
EPEL9. It is already available on EPEL 7 and 8.

An issue was opened last year [2] but at the time there were some missing 
dependencies. A thread on epel-devel from around that time [3] discusses the 
problems that were roadblocking it, but seems to indicate that this would have 
been resolved for 9.1[4]. I commented on the original issue but was asked to 
post to the list.

I'm able to build it from source using the instructions available at [5].

Thanks,
Martin

[1]: https://coccinelle.lip6.fr/
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2030779#c13
[3]: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/FHC3MQZNRT72QL6TPVZCQORYBGSJZMDO/
[4]: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/S2R3LGONYJ4R4OI4PVLNX2YOCTU4AFQT/
[5]: https://github.com/coccinelle/coccinelle/blob/master/install.txt
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2072968] Review Request: perl-Alien-libmaxminddb - Find libmaxminddb

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2072968



--- Comment #13 from Fedora Admin user for bugzilla script actions 
 ---
The Pagure repository was created at
https://src.fedoraproject.org/rpms/perl-Alien-libmaxminddb


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2072968

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202072968%23c13
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2023-06-14 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:
This is the weekly EPEL Steering Committee Meeting.

A general agenda is the following:

#topic aloha

#topic EPEL Issues https://pagure.io/epel/issues
* https://pagure.io/epel/issues?tags=meeting=Open

#topic Old Business (if needed)

#topic General Issues / Open Floor




Source: https://calendar.fedoraproject.org//meeting/9854/

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: SecureBoot certificates

[Chris Murphy]

On Wed, May 31, 2023, at 1:31 PM, przemek klosowski via devel wrote:
> I also have a recently updated F38 with shim-x64-15.6-2.x86_64. The 
> BOOTX64.EFI file has two certificates

Ha! Yeah so I'm just repeating what you said two weeks ago.

I don't have an explanation for the dual signatures, whether or not it's a 
problem.

-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: SecureBoot certificates

[Chris Murphy]

OK I tried this again and discover shim is signed twice.

Issuer: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, 
CN=Microsoft Corporation UEFI CA 2011
Not Before: Sep  9 19:40:20 2021 GMT
Not After : Sep  1 19:40:20 2022 GMT

Issuer: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, 
CN=Microsoft Corporation Third Party Marketplace Root
Not Before: Jun 27 21:22:45 2011 GMT
Not After : Jun 27 21:32:45 2026 GMT

This is the same for EFI/fedora/shimx64.efi and EFI/BOOT/BOOTX64.EFI which also 
have the same sha256sum hashes.

So maybe there isn't actually a problem other than it's confusing that there 
are two signatures that also have different validity periods? I'm not sure what 
it means.

--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora Copr builders updated to Fedora 38

[Neal H. Walfield]

On Thu, 08 Jun 2023 21:37:09 +0200,
Ondřej Budai wrote:
> RPM Sequoia's crypto policies can be configured, so you should be able to 
> re-enable SHA-1. However, this would
> be a global change, not only for EL6... See
> https://docs.rs/sequoia-policy-config/latest/sequoia_policy_config/#hash-functions
> ...
> On Thu, Jun 8, 2023 at 5:42 PM Pavel Raiskup  wrote:
> 
>  Hello maintainers!
> 
>  Copr builders have been updated to Fedora 38 today (some old builders
>  might still be running F37 ATM, but when they finish the task(s) they
>  work on, they will be deleted). Our testsuite is passing just fine, so
>  you _should_ be fine too :-).  Please let us know if you have some
>  troubles.
> 
>  There was one important change in Fedora 38 - RPM switched to the
>  Sequoia crypto backend.  It refuses SHA-1 in crypto;  which basically
>  disallows Mock to properly check EL6 GPG signatures.  To allow further
>  builds, we switched to gpgcheck=0 for all epel-6 chroots.  If you know a
>  better work-around, let me know.

I find this behavior surprising.  The default policy as set by
fedora-crypto-policies is for rpm-sequoia is to accept SHA-1 (and
DSA-1024, ...):

  
https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/blob/master/policies/FEDORA38.pol#L75

What policy are you using?


Neal
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 election results

[Justin W. Flory (he/him)]

Ah! Well, that would explain it… sometimes my timezone math is bad. 
Seems everything is on track. Let me know if anything seems amiss with this
election round.

Cheers,
Justin (he/him)
Sent from mobile

On Tue, Jun 13, 2023, 14:46 Miro Hrončok  wrote:

> On 13. 06. 23 15:21, Justin W. Flory (he/him) wrote:
> > The link is working right for me. Try now?
>
> It works now. I believe it was published at 08:00 UTC and I was looking at
> it
> at 07:43 UTC. Your email was sent at 07:00 UTC.
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Schedule for Tuesday's FESCo Meeting (2023-06-13) - #inaction Edition

[Fabio Valentini]

= Preface =

Members of the Fedora Engineering Steering Committee (FESCo) would like to
express their gratitude to Ben "#action bcotton" Cotton for his tireless work
as - both the most recent and last - Fedora Program Manager (FPgM). We were
surprised to learn that his role had been eliminated in the recent layoffs.
He contributed significantly to ensure recent on-time Fedora releases, and
improved many processes in the project. He will be missed, and we wish him the
very best.

= Schedule =

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 '2023-06-13 17:00 UTC'

Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

#2999 Nonresponsive maintainer: eclipseo
https://pagure.io/fesco/issue/2999
APPROVED (+2, 0, -0)

#3003 Change: Vagrant 2.3
https://pagure.io/fesco/issue/3003
APPROVED (+5, 0, -0)

#3005 Change: Flatpaks without Modules
https://pagure.io/fesco/issue/3005
APPROVED (+8, 0, -0)

#3006 Change: Retire AWS CLI version 1 package awscli
https://pagure.io/fesco/issue/3006
APPROVED (+4, 0, -0)

#3007 Change: No fedora-repos-modular in default installation
https://pagure.io/fesco/issue/3007
APPROVED (+8, 0, -0)

= Followups =

N/A

= New business =

#3008 Change: Build JDKs once, repack everywhere
https://pagure.io/fesco/issue/3008

= Open Floor =

For more complete details, please visit each individual issue. The report of
the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can reply to this
e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or
bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 election results

[Miro Hrončok]

On 13. 06. 23 15:21, Justin W. Flory (he/him) wrote:

The link is working right for me. Try now?


It works now. I believe it was published at 08:00 UTC and I was looking at it 
at 07:43 UTC. Your email was sent at 07:00 UTC.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 election results

[Justin W. Flory (he/him)]

The link is working right for me. Try now?

Cheers,
Justin (he/him)
Sent from mobile

On Tue, Jun 13, 2023, 08:43 Miro Hrončok  wrote:

> On 13. 06. 23 9:00, Justin W. Flory (he/him) wrote:
> > For more details, visit the Community Blog post:
> > https://communityblog.fedoraproject.org/fedora-linux-38-election-results
> > <
> https://communityblog.fedoraproject.org/fedora-linux-38-election-results>
>
> Error 404
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

[Tomas Hrnciar]

Hello,

in order to deliver Python 3.12, we are running a coordinated rebuild in a
side tag.

https://fedoraproject.org/wiki/Changes/Python3.12

We anticipate starting this rebuild sometime this week.

If you see a "Rebuilt for Python 3.12" (or similar) commit in your package,
please don't rebuild it in regular rawhide or another rawhide side tag. If
you need to, please let us know, so we can coordinate.

If you'd like to build a package after we already rebuilt it, you should be
able to build it in the side tag via:

on branch rawhide:
$ fedpkg build --target=f39-python
$ koji wait-repo f39-python --build 

Note that it will take a while before all the essential packages are
rebuilt, so don't expect all your dependencies to be available right
away. Please,
don't attempt to build your package in the side tag before we do.
When in trouble, ask here or on IRC (#fedora-python on Libera.Chat). Ping
me (thrnciar) or Miro (mhroncok) if you need to talk to us.

Builds:
https://koji.fedoraproject.org/koji/builds?latest=0=f39-python=-build_id=0

Please avoid any potentially disturbing or major changes in Python packages
until the rebuild is over.

Thanks. Let us know if you have any questions.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F38 election results

[Justin W. Flory (he/him)]

Greetings, all! The elections for the Fedora Linux 38 cycle have completed.


*## Fedora Council*

Sumantro Mukherjee is elected to the Fedora Council.

*## Fedora Engineering Steering Committee (FESCo)*

The following candidates are elected to FESCo:

   - Stephen Gallagher
   - Neal Gompa
   - Major Hayden
   - Tom Stellard

*## Fedora Mindshare Committee*

David Duncan is elected to the Fedora Mindshare Committee.


Congratulations to all those elected and thank you to the candidates and
voters. I will process the "paperwork" to update memberships and
documentation over the next 1-2 weeks.

For more details, visit the Community Blog post:
https://communityblog.fedoraproject.org/fedora-linux-38-election-results

-- 
*Cheers*,
*Justin W. Flory* (*he/him*) ||  j...@redhat.com ||  jwf.io
*Fedora* Community Architect
TZ=America/New_York (UTC-4) 

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Making systemd-boot option available for installation?

[Jeremy Linton]

Hi,

On 6/5/23 03:24, Zbigniew Jędrzejewski-Szmek wrote:

On Fri, Jun 02, 2023 at 05:25:22PM -0700, Luya Tshimbalanga wrote:

Hello team,

I would like to bring back the topic related to the selection of bootloader
notably either GRUB2 and systemd-boot. With the recent adoption on UKI
kernel, it would be great to get systemd-boot ready for at least Fedora 39
which is useful for devices like laptops. Currently, some methods allow to
install systemd-boot with extra step to keep supporting secure boot while
preserving GRUB2 [1]. What is the missing step to enable secure boot for
systemd-boot without at least keeping GRUB 2?


Hi Luya,

my goal is to have systemd-boot built as a ready-to-install Fedora package
with a Fedora signature for SecureBoot. The signature would use a different
certificate than grub2, and would not be trusted by our shim build. (This
way, we don't have to touch the complicated issue of making shim trust sd-boot.)
Users would be able to self-enroll those sd-boot singing keys on their machines,
getting reasonable protection from SecureBoot and being able to build
useful policies for tpm-encrypted secrets.


I tend to agree this is the right way to use systemd-boot although users 
depending on 3rd party modules will be again locked out of the secure 
boot path without the shim + MOKs. That support exists in systemd-boot 
today but it might be a good idea to provide a switch to disable the 
shim support in sdboot if the plan is to have a clean secure boot setup 
without MOKs. AKA systemd-boot-signed and a systemd-boot-signed-for-shim 
package.





Unfortunately, this requires releng to adjust the infrastructure to do the
signing, and this is not progressing at all [1].

Also, there has been work to add support for sd-boot to Anaconda [2,3].
There has been more progress there, but what we have is not a complete solution.


It is with the comps change below and the acceptance of the sdbubby 
package which is shimming things like kdumpctl to the systemd interface. 
Granted its not complete given the secure boot path hasn't been solved, 
but it does allow for testing a machine that can be updated, and 
generally works transparently. Once a signed package is available it 
should be fairly simple to assure the secure boot keys that need 
enrolling are positioned on the ESP for systemd-boot to enroll during 
the next reboot.




[1] https://pagure.io/releng/issue/10765
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2106706
[3] https://github.com/rhinstaller/anaconda/pull/4368

In general, I think it'd be nice to make the process of installing sd-boot much
much simpler than it is currently. 'bootctl install' takes care of installation
process, if the system already has the expected layout. So the installation 
procedure
for Fedora should be just 'dnf install …' of a single package. But this doesn't
currently work because of a few issues:

1. the /boot partition is formatted with ext4


I don't think this is really a problem with the current anaconda + 
systemd-boot-unsigned + sdubby package. If the user default installs 
with inst.sdboot they get a separate /boot partition, and it continues 
to hold parts of the kernel debug/etc packages that aren't needed for 
boot. The kernel, initrd and loader entries have all been moved to the 
/boot/efi ESP partition under the assumption that systemd-boot systems 
will have larger ESPs and the /boot partition can be removed in its 
entirety. This works quite well today if the user uses the inst.sdboot 
option and simply deletes the /boot partition with the partition tools 
in anaconda.




2. partitions don't have parttype uuids conforming to Discoverable Partitions 
Spec [4]
(or has this been fixed? I need to check.)


I'm not sure this is needed either given the kernel + initrd is on the ESP.


3. grub2 and shim carry files directly in their rpm payload, hardcoding paths 
and
causing any changes to layout to conflict with what rpm thinks about the 
file system.
(This part was discussed on fedora-devel recently too.)


The anaconda inst.sdboot option explicitly doesn't install grub, grubby, 
grub efi tools, nor shim. Although as noted in the review comments the 
sdubby package "pins" the install location that bootctl/etc are aware 
of. Which IMHO isn't a problem given the above.


https://bugzilla.redhat.com/show_bug.cgi?id=2134972

And as I mention in that ticket I'm not sure I view it as a problem 
either since fedora has an existing filesystem layout, and something has 
to make the choice about where the files are located and that is usually 
the responsibility of rpm/etc on fedora systems since it also aids in 
auditing the files, dealing with updates, etc. I'm personally not super 
happy using `bootctl install` to move the EFI bootloader executable to 
the ESP, since I think its totally unnecessarily now that systemd-boot 
its its own package, but that is what anaconda is doing at the moment.


Nor am I entirely sure the default location 

Re: Fedora Copr builders updated to Fedora 38

[Kevin Kofler via devel]

Kevin Kofler via devel wrote:
> Gary Buhrmaster wrote:
>> Well, EL6 ELS support is still available for (around)
>> another year, so it is a nice to have to support those
>> limping along with EL6, but I would generally agree
>> with the principal that if supporting a product past
>> official EOL becomes overly onerous that support
>> should end, or be explicitly funded out of the ELS
>> fees if the ELS community needs that support.
> 
> EPEL is not covered by ELS, hence EPEL is already EOL.

PS: I also do not see why Fedora should be supporting the users of a 
commercial subscription scheme with free services such as Copr.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora Copr builders updated to Fedora 38

[Stephen Smoogen]

On Tue, 13 Jun 2023 at 08:21, Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:

> Gary Buhrmaster wrote:
> > Well, EL6 ELS support is still available for (around)
> > another year, so it is a nice to have to support those
> > limping along with EL6, but I would generally agree
> > with the principal that if supporting a product past
> > official EOL becomes overly onerous that support
> > should end, or be explicitly funded out of the ELS
> > fees if the ELS community needs that support.
>
> EPEL is not covered by ELS, hence EPEL is already EOL.
>
> If we are going to support distros that had their EOL 2½ years ago, I want
> my Fedora 31 to 36 buildroots back! (Fedora 31 had its EOL only 6 days
> before EPEL 6, Fedora 32 to 36 had theirs more recently.)
>
>
I am in agreement with Kevin on this. While there are people who might
still want to build for their EL6 systems (including myself *cough*), I
think there is a point where its usage of the COPR project's limited
resources. If you really need to build stuff against end of life releases,
then one needs to do the work themselves or join together with other people
who can help pay for those resources.



> > I do not consider setting gpgcheck=0 overly
> > onerous for EPEL6
>
> I consider it a security risk and a no go.
>
> Kevin Kofler
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2214232] perl-PAR-Packer-1.058 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2214232

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-PAR-Packer-1.058-1.fc3
   ||9
 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2023-06-13 12:30:05




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2214232
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora Copr builders updated to Fedora 38

[Kevin Kofler via devel]

Gary Buhrmaster wrote:
> Well, EL6 ELS support is still available for (around)
> another year, so it is a nice to have to support those
> limping along with EL6, but I would generally agree
> with the principal that if supporting a product past
> official EOL becomes overly onerous that support
> should end, or be explicitly funded out of the ELS
> fees if the ELS community needs that support.

EPEL is not covered by ELS, hence EPEL is already EOL.

If we are going to support distros that had their EOL 2½ years ago, I want 
my Fedora 31 to 36 buildroots back! (Fedora 31 had its EOL only 6 days 
before EPEL 6, Fedora 32 to 36 had theirs more recently.)

> I do not consider setting gpgcheck=0 overly
> onerous for EPEL6

I consider it a security risk and a no go.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

[Tomas Hrnciar]

Hello,

in order to deliver Python 3.12, we are running a coordinated rebuild in a
side tag.

https://fedoraproject.org/wiki/Changes/Python3.12

We anticipate starting this rebuild sometime this week.

If you see a "Rebuilt for Python 3.12" (or similar) commit in your package,
please don't rebuild it in regular rawhide or another rawhide side tag. If
you need to, please let us know, so we can coordinate.

If you'd like to build a package after we already rebuilt it, you should be
able to build it in the side tag via:

on branch rawhide:
$ fedpkg build --target=f39-python
$ koji wait-repo f39-python --build 

Note that it will take a while before all the essential packages are
rebuilt, so don't expect all your dependencies to be available right
away. Please,
don't attempt to build your package in the side tag before we do.
When in trouble, ask here or on IRC (#fedora-python on Libera.Chat). Ping
me (thrnciar) or Miro (mhroncok) if you need to talk to us.

Builds:
https://koji.fedoraproject.org/koji/builds?latest=0=f39-python=-build_id=0

Please avoid any potentially disturbing or major changes in Python packages
until the rebuild is over.

Thanks. Let us know if you have any questions.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

[Tomas Hrnciar]

Hello,

in order to deliver Python 3.12, we are running a coordinated rebuild in a
side tag.

https://fedoraproject.org/wiki/Changes/Python3.12

We anticipate starting this rebuild sometime this week.

If you see a "Rebuilt for Python 3.12" (or similar) commit in your package,
please don't rebuild it in regular rawhide or another rawhide side tag. If
you need to, please let us know, so we can coordinate.

If you'd like to build a package after we already rebuilt it, you should be
able to build it in the side tag via:

on branch rawhide:
$ fedpkg build --target=f39-python
$ koji wait-repo f39-python --build 

Note that it will take a while before all the essential packages are
rebuilt, so don't expect all your dependencies to be available right
away. Please,
don't attempt to build your package in the side tag before we do.
When in trouble, ask here or on IRC (#fedora-python on Libera.Chat). Ping
me (thrnciar) or Miro (mhroncok) if you need to talk to us.

Builds:
https://koji.fedoraproject.org/koji/builds?latest=0=f39-python=-build_id=0

Please avoid any potentially disturbing or major changes in Python packages
until the rebuild is over.

Thanks. Let us know if you have any questions.
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2072968] Review Request: perl-Alien-libmaxminddb - Find libmaxminddb

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2072968



--- Comment #12 from Michal Josef Spacek  ---
@andr...@andreasvoegele.com Hi Andreas, you were sponsored. You could request
branch and build package.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2072968

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202072968%23c12
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20230613.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230612.n.0
NEW: Fedora-Rawhide-20230613.n.0

= SUMMARY =
Added images:4
Dropped images:  3
Added packages:  7
Dropped packages:1
Upgraded packages:   144
Downgraded packages: 0

Size of added packages:  7.01 MiB
Size of dropped packages:513.84 KiB
Size of upgraded packages:   2.18 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   4.17 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20230613.n.0.iso
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20230613.n.0.iso
Image: Python_Classroom vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-Rawhide-20230613.n.0.x86_64.vagrant-virtualbox.box
Image: Python_Classroom vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-Rawhide-20230613.n.0.x86_64.vagrant-libvirt.box

= DROPPED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20230612.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20230612.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230612.n.0.iso

= ADDED PACKAGES =
Package: c-icap-0.5.11-12.20230403git1238524.fc39
Summary: An implementation of an ICAP server
RPMs:c-icap c-icap-devel c-icap-libs c-icap-perl
Size:1.88 MiB

Package: lua-luautf8-0.1.5-1.fc39
Summary: A UTF-8 support module for Lua
RPMs:lua-luautf8
Size:161.86 KiB

Package: netrate-0.1-4.fc39
Summary: Network interface traffic meter
RPMs:netrate
Size:93.11 KiB

Package: perl-Lingua-EN-Syllable-1:0.31-1.fc39
Summary: Routine for estimating syllable count in words
RPMs:perl-Lingua-EN-Syllable
Size:19.71 KiB

Package: rust-dtoa0.4-0.4.8-1.fc39
Summary: Fast functions for printing floating-point primitives to an io::Write
RPMs:rust-dtoa0.4+default-devel rust-dtoa0.4-devel
Size:30.46 KiB

Package: stats-collect-1.0.6-1.fc39
Summary: A tool for collecting and visualising system statistics and telemetry
RPMs:stats-collect
Size:332.81 KiB

Package: tuigreet-0.8.0-1.fc39
Summary: Graphical console greeter for greetd
RPMs:tuigreet
Size:4.50 MiB


= DROPPED PACKAGES =
Package: mozplugger-2.1.6-18.fc38
Summary: A generic mozilla plug-in
RPMs:mozplugger
Size:513.84 KiB


= UPGRADED PACKAGES =
Package:  ServiceReport-2.2.3-2.fc39
Old package:  ServiceReport-2.2.3-1.fc39
Summary:  A tool to validate and repair First Failure Data Capture (FFDC) 
configuration
RPMs: ServiceReport
Size: 101.44 KiB
Size change:  -382 B
Changelog:
  * Mon Jun 12 2023 Than Ngo  - 2.2.3-2
  - migrated to SPDX license


Package:  akmods-0.5.8-1.fc39
Old package:  akmods-0.5.7-10.fc38
Summary:  Automatic kmods build and install tool
RPMs: akmods
Size: 33.22 KiB
Size change:  460 B
Changelog:
  * Fri May 05 2023 Nicolas Chauvet  - 0.5.8-1
  - Don't emit weak-deps from deprecated arches on all
  - Allow akmods --rebuild to force rebuild+reinstall - rhbz#2140012
  - ensure to build for grub or systemd-boot default kernel - rhbz#2124086
  - Drop "which" as akmods dependency


Package:  akonadi-1.13.0-123.fc39
Old package:  akonadi-1.13.0-122.fc38
Summary:  PIM Storage Service Libraries
RPMs: akonadi akonadi-devel
Size: 604.97 KiB
Size change:  -1.40 KiB
Changelog:
  * Mon Jun 12 2023 Than Ngo  - 1.13.0-123
  - migrated to SPDX license


Package:  ansible-freeipa-1.11.0-1.fc39
Old package:  ansible-freeipa-1.10.0-1.fc39
Summary:  Roles and playbooks to deploy FreeIPA servers, replicas and 
clients
RPMs: ansible-freeipa ansible-freeipa-tests
Size: 565.06 KiB
Size change:  16.01 KiB
Changelog:
  * Mon Jun 12 2023 Thomas Woerner  - 1.11.0-1
  - Update to version 1.11.0
https://github.com/freeipa/ansible-freeipa/releases/tag/v1.11.0
Highlights:
- Multiple service management with ipaservice module
- New ipacert module for certificate management
- Action group support for the Ansible collections on Ansible Galaxy and
  Ansible AutomationHub
- Fixed maxsequence handling in ipapwpolicy module
- Even more Ansible lint driven changes


Package:  apt-2.7.1-1.fc39
Old package:  apt-2.5.6-1.fc39
Summary:  Command-line package manager for Debian packages
RPMs: apt apt-apidoc apt-devel apt-doc apt-libs apt-utils
Size: 14.11 MiB
Size change:  66.80 KiB
Changelog:
  * Mon Jun 12 2023 Mosaab Alzoubi  - 2.7.1-1
  - Update to 2.7.1


Package:  arts-8:1.5.10-57.fc39
Old package:  arts-8:1.5.10-56.fc38
Summary:  aRts (analog realtime synthesizer) - the KDE sound system
RPMs: arts arts-devel
Size:   

[Test-Announce] Fedora 39 Rawhide 20230613.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 39 Rawhide 20230613.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
pykickstart - 20230610.n.0: pykickstart-3.47-1.fc39.src, 20230613.n.0: 
pykickstart-3.48-1.fc39.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/39

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230613.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-List-MoreUtils-XS] PR #1: Disable extra test in RHEL builds

[Paul Howarth]

pghmcfc commented on the pull-request: `Disable extra test in RHEL builds` that 
you are following:
``
I didn't merge the PR but did something similar based on the usual pattern for 
such things in our perl modules.
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

pghmcfc pushed to rpms/perl-List-MoreUtils-XS (rawhide). "Silence build-time warnings about missing bundled modules"

[notifications]

Notification time stamped 2023-06-13 09:25:14 UTC

From 4199e4f7be2f76fa9f8cd8f7b3f219c8561844ac Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Jun 13 2023 09:18:01 +
Subject: Silence build-time warnings about missing bundled modules


---

diff --git a/perl-List-MoreUtils-XS.spec b/perl-List-MoreUtils-XS.spec
index bc2c49c..f05c6b8 100644
--- a/perl-List-MoreUtils-XS.spec
+++ b/perl-List-MoreUtils-XS.spec
@@ -63,6 +63,7 @@ This module provides accelerated versions of functions in 
List::MoreUtils.
 # Unbundle bundled modules except private inc::Config::AutoConf::LMU
 %patch -P 0
 find inc/ -type f ! -name LMU.pm -print -delete
+perl -i -ne 'print $_ unless m{^inc/} and not m{LMU\.pm}' MANIFEST
 
 %build
 perl Makefile.PL \
@@ -91,6 +92,7 @@ make test
 * Tue Jun 13 2023 Paul Howarth  - 0.430-9
 - Disable extra test in RHEL builds (based on
   https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/pull-request/1)
+- Silence build-time warnings about missing bundled modules
 
 * Fri Jan 20 2023 Fedora Release Engineering  - 
0.430-8
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild



https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/c/4199e4f7be2f76fa9f8cd8f7b3f219c8561844ac?branch=rawhide
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

pghmcfc pushed to rpms/perl-List-MoreUtils-XS (rawhide). "Disable extra test in RHEL builds (..more)"

[notifications]

Notification time stamped 2023-06-13 09:25:14 UTC

From 102ebafc207194a99ec10432b6480844ff4e28ef Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Jun 13 2023 09:11:16 +
Subject: Disable extra test in RHEL builds


Based on:
https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/pull-request/1

---

diff --git a/perl-List-MoreUtils-XS.spec b/perl-List-MoreUtils-XS.spec
index 410f355..bc2c49c 100644
--- a/perl-List-MoreUtils-XS.spec
+++ b/perl-List-MoreUtils-XS.spec
@@ -1,9 +1,13 @@
 # Run extra tests
+%if ! (0%{?rhel})
 %bcond_without perl_List_MoreUtils_XS_enables_extra_test
+%else
+%bcond_with perl_List_MoreUtils_XS_enables_extra_test
+%endif
 
 Name:  perl-List-MoreUtils-XS
 Version:   0.430
-Release:   8%{?dist}
+Release:   9%{?dist}
 Summary:   Provide compiled List::MoreUtils functions
 # Code from List-MoreUtils < 0.417 is GPL-1.0-or-later OR Artistic-1.0-Perl
 # Anything after that is Apache-2.0
@@ -84,6 +88,10 @@ make test
 %{_mandir}/man3/List::MoreUtils::XS.3*
 
 %changelog
+* Tue Jun 13 2023 Paul Howarth  - 0.430-9
+- Disable extra test in RHEL builds (based on
+  https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/pull-request/1)
+
 * Fri Jan 20 2023 Fedora Release Engineering  - 
0.430-8
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/c/102ebafc207194a99ec10432b6480844ff4e28ef?branch=rawhide
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: nest: python package still setup.py; also needs to be built for MPI

[David Schwörer]

Hi Ankur,

Not sure whether that helps, but BOUT++ (requires MPI) switched to a custom 
back end [1] when it switched to cmake [2] from configure + calling setup.py. 
The main motivation was to enable packaging in fedora, but it also allowed to 
just pip install the whole package, as BOUT++ is now PEP-517 enabled.

This doesn't call the pyproject macros, but just the cmake ones [3], so not 
sure this is applicable to what you need, but maybe it offers at least some 
insight into how it is done for other MPI codes ...

Best,
David

[1] 
https://github.com/boutproject/BOUT-dev/blob/master/tools/pylib/_boutpp_build/backend.py
[2] 
https://github.com/boutproject/BOUT-dev/blob/master/tools/pylib/_boutpp_build/CMakeLists.txt
[3] https://src.fedoraproject.org/rpms/bout++/blob/rawhide/f/bout++.spec
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 election results

[Miro Hrončok]

On 13. 06. 23 9:00, Justin W. Flory (he/him) wrote:

For more details, visit the Community Blog post:
https://communityblog.fedoraproject.org/fedora-linux-38-election-results 



Error 404

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F38 election results

[Justin W. Flory (he/him)]

Greetings, all! The elections for the Fedora Linux 38 cycle have completed.


*## Fedora Council*

Sumantro Mukherjee is elected to the Fedora Council.

*## Fedora Engineering Steering Committee (FESCo)*

The following candidates are elected to FESCo:

   - Stephen Gallagher
   - Neal Gompa
   - Major Hayden
   - Tom Stellard

*## Fedora Mindshare Committee*

David Duncan is elected to the Fedora Mindshare Committee.


Congratulations to all those elected and thank you to the candidates and
voters. I will process the "paperwork" to update memberships and
documentation over the next 1-2 weeks.

For more details, visit the Community Blog post:
https://communityblog.fedoraproject.org/fedora-linux-38-election-results

-- 
*Cheers*,
*Justin W. Flory* (*he/him*) ||  j...@redhat.com ||  jwf.io
*Fedora* Community Architect
TZ=America/New_York (UTC-4) 

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Plan / proposal: enable openQA update testing and potentially gating on Rawhide updates

[Petr Pisar]

V Mon, Jun 12, 2023 at 08:29:13AM -0700, Adam Williamson napsal(a):
> On Mon, 2023-06-12 at 12:05 +0200, Petr Pisar wrote:
> >  or there must be some one else to do it.
> 
> We (QA team) will do this.
> 
> > I would expect answers for these questions to be available in a 
> > documentation.
> > Yet, I can any pointer to the documentation from a page with the results.
> 
> That's a good idea, I'll see if we can work in a link somewhere in
> Bodhi, the openQA UI, or both.

Thanks for the exhaustive answer.

-- Petr


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 Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2212782] perl-HTTP-OAI-4.13 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2212782



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-ed3cc3a007 has been submitted as an update to Fedora 37.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed3cc3a007


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2212782

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202212782%23c3
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2212782] perl-HTTP-OAI-4.13 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2212782



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-4ed60aa04c has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-4ed60aa04c


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2212782

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202212782%23c2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue