Unretire lua-coxpcall

[Benson Muite]

Hi

Would like to unretire lua-coxpcall:
https://src.fedoraproject.org/rpms/lua-coxpcall
It is a dependency of https://github.com/lunarmodules/copas which is a 
dependency of https://github.com/lunarmodules/busted which is needed for 
testing other lua packages.


Regards,
Benson
___
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: [Test-Announce] Re: Proposal: make meetings officially every other week

[Philip Rhoades via devel]

Adam,


On 2022-11-19 13:23, Adam Williamson wrote:

On Fri, 2022-10-28 at 17:42 -0700, Adam Williamson wrote:

Hey folks!

The more attentive among you may have noticed I've had a kinda
unofficial policy of holding the QA meetings every other week for a
while. We just don't seem to have as much to discuss/debate as maybe 
we
did five or six years ago. I choose to see this as a positive sign 
that

everything is working smoothly, but maybe others disagree? I dunno.

Anyway, it seems a bit silly that we still notionally schedule a
meeting every week but I almost always cancel half of them. So I'm
proposing we make it official that we only meet every *other* week.
This would save sending out cancellation notices and manually 
canceling

the event in the calendar every other week.

What do folks think? Makes sense? Or would you rather we really do 
meet
every week and find more things to argue about? Or do you hate 
meetings

and wish we only did one a year? :D


Hey again folks. So the response to this was positive, and I've decided
to go ahead and implement it. I unfortunately had to delete and re-
create the calendar.fedoraproject.org



Can someone change the format of that home page from tiled groups to a 
table with headings that can be clicked on to sort columns?  Why does 
anyone use tiles? - they are SO much harder to scan quickly . .


Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
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

[Test-Announce] Re: Proposal: make meetings officially every other week

[Adam Williamson]

On Fri, 2022-10-28 at 17:42 -0700, Adam Williamson wrote:
> Hey folks!
> 
> The more attentive among you may have noticed I've had a kinda
> unofficial policy of holding the QA meetings every other week for a
> while. We just don't seem to have as much to discuss/debate as maybe we
> did five or six years ago. I choose to see this as a positive sign that
> everything is working smoothly, but maybe others disagree? I dunno.
> 
> Anyway, it seems a bit silly that we still notionally schedule a
> meeting every week but I almost always cancel half of them. So I'm
> proposing we make it official that we only meet every *other* week.
> This would save sending out cancellation notices and manually canceling
> the event in the calendar every other week.
> 
> What do folks think? Makes sense? Or would you rather we really do meet
> every week and find more things to argue about? Or do you hate meetings
> and wish we only did one a year? :D

Hey again folks. So the response to this was positive, and I've decided
to go ahead and implement it. I unfortunately had to delete and re-
create the calendar.fedoraproject.org entry for the meeting, as
changing its recurrence to every 14 days didn't seem to work properly.
So if you had any kind of subscription for that entry, you'll have to
set it up for the new one - sorry.

I counted the meeting on November 14 as the first meeting in the new
every-other-week era, so the next meeting will be November 28. I will
not send a cancellation mail for November 21st, but I'm sending this
mail to test-announce to make sure folks are aware of the new era :)

I'll also update the wiki page to explain things.

Thanks folks!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
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

[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-2022-a06d5c7af1   
js-jquery-ui-1.13.2-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d6012d25d2   
drupal7-link-1.11-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-aa5b185b7b   
drupal7-context-3.11-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9e1d9b40a7   
ntfs-3g-2022.10.3-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-30fd5a80a8   
heimdal-7.7.1-1.el7


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

drupal7-addressfield-1.3-1.el7
drupal7-date-2.13-1.el7
drupal7-diff-3.4-1.el7
drupal7-feeds-2.0-0.31.beta6.el7
drupal7-file_entity_inline-1.0-0.20.rc2.el7
drupal7-i18n-1.31-1.el7
drupal7-i18nviews-3.0-0.20.alpha1.el7
drupal7-views_bulk_operations-3.7-1.el7
python-colcon-core-0.11.0-1.el7

Details about builds:



 drupal7-addressfield-1.3-1.el7 (FEDORA-EPEL-2022-fcf06ef288)
 Manage a flexible address field, implementing the xNAL standard

Update Information:

https://www.drupal.org/project/addressfield/releases/7.x-1.3

ChangeLog:

* Thu Nov 17 2022 Shawn Iwinski  - 1.3-1
- Update to 1.3
* Thu Jul 21 2022 Fedora Release Engineering  - 1.2-16
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Thu Jan 20 2022 Fedora Release Engineering  - 1.2-15
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Wed Jul 21 2021 Fedora Release Engineering  - 1.2-14
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Tue Jan 26 2021 Fedora Release Engineering  - 1.2-13
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Mon Jul 27 2020 Fedora Release Engineering  - 1.2-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Fri Jun  5 2020 Shawn Iwinski  - 1.2-11
- Bump build requires drupal7-rpmbuild to ">= 7.70-2" to fix F32+ auto provides
* Tue Jan 28 2020 Fedora Release Engineering  - 1.2-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
* Wed Jul 24 2019 Fedora Release Engineering  - 1.2-9
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
* Thu Jan 31 2019 Fedora Release Engineering  - 1.2-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Thu Jul 12 2018 Fedora Release Engineering  - 1.2-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Wed Feb  7 2018 Fedora Release Engineering  - 1.2-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Jul 26 2017 Fedora Release Engineering  - 1.2-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Fri Feb 10 2017 Fedora Release Engineering  - 1.2-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
* Wed Feb  3 2016 Fedora Release Engineering  - 1.2-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild




 drupal7-date-2.13-1.el7 (FEDORA-EPEL-2022-3fe7d00bef)
 Makes date/time fields available

Update Information:

- https://www.drupal.org/project/date/releases/7.x-2.13 -
https://www.drupal.org/project/date/releases/7.x-2.12 -
https://www.drupal.org/project/date/releases/7.x-2.12-rc1 -
https://www.drupal.org/project/date/releases/7.x-2.11 -
https://www.drupal.org/project/date/releases/7.x-2.11-rc1 -
https://www.drupal.org/project/date/releases/7.x-2.11-beta3 -
https://www.drupal.org/project/date/releases/7.x-2.11-beta2 -
https://www.drupal.org/project/date/releases/7.x-2.11-beta1

ChangeLog:

* Thu Nov 17 2022 Shawn Iwinski  - 2.13-1
- Update to 2.13 (RHBZ #1998661)
* Thu Jul 21 2022 Fedora Release Engineering  - 
2.10-13
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Thu Jan 20 2022 Fedora Release Engineering  - 
2.10-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Wed Jul 21 2021 Fedora Release Engineering  - 
2.10-11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Tue Jan 26 2021 Fedora Release Engineering  - 
2.10-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Mon Jul 27 2020 Fedora Release Engineering  - 2.10-9
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Fri Jun  5 2020 Shawn Iwinski  - 2.10-8
- Bump build requires drupal7-rpmbuild to ">= 7.70-2" to fix F32+ auto provides
* Tue Jan 28 2020 

Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

[Philip Rhoades via devel]

Michael,


On 2022-11-19 05:41, Michael Dawson wrote:

As Web Assembly (WASM) gains momentum we’d like to create a SIG as a
place to collaborate to ensure that Fedora is a great platform to both
build and run WASM workloads. This includes looking at the toolchains
needed to build WASM as a target and the runtimes needed to run WASM.
It will provide a place to bring together efforts across different
ecosystems (nodejs, rust, compiler toolchains, etc.) as well as a
place where people can provide self-help when building and running
WASM workloads.

If you are interested in a WASM Sig please let us know.



I am definitely interested in the area both because of Rust but 
particularly because of WASM . . I don't have a huge amount of time 
though unfortunately . .


P.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
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: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

[Fabio Valentini]

On Fri, Nov 18, 2022 at 7:41 PM Michael Dawson  wrote:
>
> As Web Assembly (WASM) gains momentum we’d like to create a SIG as a place to 
> collaborate to ensure that Fedora is a great platform to both build and run 
> WASM workloads. This includes looking at the toolchains needed to build WASM 
> as a target and the runtimes needed to run WASM. It will provide a place to 
> bring together efforts across different ecosystems (nodejs, rust, compiler 
> toolchains, etc.) as well as a place where people can provide self-help when 
> building and running WASM workloads.
>
> If you are interested in a WASM Sig please let us know.

Speaking from the Rust SIG perspective: The Rust compiler in Fedora
can already produce working wasm32 binaries if
rust-std-static-wasm32-unknown-unknown is installed, no other setup
required.

Running WASM binaries is a different problem ... earlier this year,
there was an attempt to package wasmtime (a high-performance WASM
runtime with support for WASI written in Rust), but this effort was
ultimately abandoned due to unresolved legal questions (unclear
license terms of some of its sub-components).
If these problems could be resolved, having wasmtime in Fedora might
be a great addition.

Fabio
___
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: Orphaned packages looking for new maintainers

[Adam Williamson]

On Mon, 2022-10-31 at 12:18 +0100, Miro Hrončok wrote:
> python-PyRSS2Gen  orphan   3 weeks ago

I missed this, but it's a dependency of python-nikola, which I use to
write my blog. So I guess I'll unretire it and pick it up, if nobody
objects. https://pagure.io/releng/issue/11140
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


___
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: Direct to stable updates

[Adam Williamson]

On Fri, 2022-11-18 at 08:10 +, Mattia Verga via devel wrote:
> Il 17/11/22 18:10, Adam Williamson ha scritto:
> > On Wed, 2022-11-16 at 17:37 +, Mattia Verga via devel wrote:
> > > Kevin, the PR for Bodhi is nearly finished, it will add support for
> > > using the 'frozen' release state to avoid pausing the push cron job and
> > > avoid direct pending to stable push of updates when the release is frozen.
> > > 
> > > I'll open a ticket to releng for changing the usual workflow of new
> > > releases once the PR gets merged and a new Bodhi release is drafted and
> > > pushed to prod. About the avoidance of direct to stable pushing, do you
> > > think it needs to be discussed by FESCo?
> > Hey Mattia! Can you keep me in the loop on the new version and
> > deployment also? The final phase of my work on critical path status by
> > group is waiting on that. Thanks!
> 
> Hello Adam,
> 
> as soon as the last batch of PRs I submitted are merged, I plan to ask
> @abompard (or whoever is taking care of Bodhi now) to draft and deploy
> the new version.
> 
> I can take care of drafting the new version, if they agree, but then
> someone has to deploy it to stg/prod, as I'm not part of infra-sig and I
> don't know ansible/OC. My wishes are to have the new version with the
> new features land in prod early now, so that if a bugfix release is
> needed it can be deployed before the next freeze and that releng can
> adjust their SOP to start using the 'frozen' release state in the next
> release cycle.
> 
> I'll keep you posted. Do you need any other change about gating pushed
> before the next release is drafted?

Thanks! I'll work with nirik on the deployment part. I don't need any
more changes merged (at least, I hope I didn't forget anything),
everything I had planned for Bodhi side has been merged; further
changes will be to our ansible configs and then the openQA scheduler.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
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: Direct to stable updates

[Kevin Fenzi]

On Fri, Nov 18, 2022 at 08:10:56AM +, Mattia Verga via devel wrote:
> Il 17/11/22 18:10, Adam Williamson ha scritto:
> > On Wed, 2022-11-16 at 17:37 +, Mattia Verga via devel wrote:
> >> Kevin, the PR for Bodhi is nearly finished, it will add support for
> >> using the 'frozen' release state to avoid pausing the push cron job and
> >> avoid direct pending to stable push of updates when the release is frozen.
> >>
> >> I'll open a ticket to releng for changing the usual workflow of new
> >> releases once the PR gets merged and a new Bodhi release is drafted and
> >> pushed to prod. About the avoidance of direct to stable pushing, do you
> >> think it needs to be discussed by FESCo?
> > Hey Mattia! Can you keep me in the loop on the new version and
> > deployment also? The final phase of my work on critical path status by
> > group is waiting on that. Thanks!
> 
> Hello Adam,
> 
> as soon as the last batch of PRs I submitted are merged, I plan to ask
> @abompard (or whoever is taking care of Bodhi now) to draft and deploy
> the new version.

I can help with the deployment. :) 

It might also be nice to move bodhi-backend01 to f37.

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of 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

Web Assembly on Fedora: interested in a Fedora SIG to work on this?

[Michael Dawson]

As Web Assembly (WASM) gains momentum we’d like to create a SIG as a place to 
collaborate to ensure that Fedora is a great platform to both build and run 
WASM workloads. This includes looking at the toolchains needed to build WASM as 
a target and the runtimes needed to run WASM. It will provide a place to bring 
together efforts across different ecosystems (nodejs, rust, compiler 
toolchains, etc.) as well as a place where people can provide self-help when 
building and running WASM workloads.

If you are interested in a WASM Sig please let us know.
___
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 proposal: Remove initial-setup from KDE Spin & Kinoite (Self-Contained Change proposal)

[Timothée Ravier]

Thanks, updated
___
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 prospoal: Enable bootupd for Fedora Silverblue & Kinoite (Self-Contained Change proposal)

[Timothée Ravier]

Thanks, updated.
___
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 prospoal: Enable bootupd for Fedora Silverblue & Kinoite (Self-Contained Change proposal)

[Colin Walters]

On Fri, Nov 18, 2022, at 12:35 PM, Timothée Ravier wrote:
>> No, the install script install script in an RPM trigger, so the write is
>> still carried out by RPM.
>> 
>> I don't agree.  Just because a user can mess with files on the system
>> doesn't mean the rpmdb is a lie, nor is it reasonable to go recheck all
>> paths on the filesystem just in case they've done so, or create a daemon
>> to provide an interface for doing that.
>
> Note that this change here is only about Fedora Silverblue & Kinoite 
> (and maybe IoT later). In those variants, /usr is read only and not 
> expected to be changed by users. The rpmdb is thus pretty much 
> guaranteed to match the content of the system by design for /usr.
>
> On rpm-ostree based systems, system composes (image builds), package 
> installation and updates are done "offline" so /boot is not available. 
> The bootloader is not updated by an RPM trigger and this is why we need 
> an additional tool to perform the update at another time. We've created 
> a daemon because we need the update to be reliable so it should not 
> fail if your SSH connections fails or if you Ctrl-C it in the middle, 
> etc. This daemon is really small

I wouldn't even call it a daemon, at least not really.  More in:
https://github.com/coreos/bootupd/pull/401/files

That said, I think Robbie is effectively saying "bootupd seems over-engineered" 
and that's not *entirely* wrong.  It certainly could be simpler; yes, in theory 
we don't strictly need `bootupctl validate`.  But...things like having status 
information going to the journal in a reliable fashion have proven *very* 
useful in the past.  Most classically of course, dnf/apt type systems don't do 
this and it definitely makes things harder to debug after the fact.

The discussion about offline versus live installs touches on
https://github.com/coreos/bootupd/issues/108
and we probably should have an option to do that.
___
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: Regular crash of the internal DirectoryServer389 replication

[Mark Reynolds]

On 11/18/22 8:05 AM, Dip Barua wrote:

Hello all,

I hope you are doing well.
I would like to have your help because I have a Replication crash problem on 
389DS.


Is the server crashing, or is replication not working?  There's a big 
difference between the two.


If it's crashing please obtain a stack trace from the core file:

https://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Crashes

If it's just replication not working then we need a lot more 
information.  Access logs, error logs with replication logging enabled, 
and the replication agreements.


Look through your access log and track down what client is opening 
conn=36614.  is this a replica or some other client?


Mark


Here is the below some Frequent Error :


[25/Oct/2022:02:03:15.698645866 +0200] - ERR - slapi_ldap_bind - Could not send bind 
request for id [cn=Directory Manager] authentication mechanism [SIMPLE]: error -1 (Can't 
contact LDAP server), system error -5987 (Invalid function argument.), network error 107 
(Transport endpoint is not connected, host "wam2p.lefoyer.lu:389")

[25/Oct/2022:02:06:27.558971677 +0200] - INFO - NSMMReplicationPlugin - 
bind_and_check_pwp - agmt="cn=lpfroot12" (wam2p:389): Replication bind with 
SIMPLE auth resumed

[25/Oct/2022:07:25:15.490236609 +0200] - ERR - log_ber_too_big_error - 
conn=36614 fd=78 Incoming BER Element may be misformed. This may indicate an 
attempt to use TLS on a plaintext port, IE ldaps://localhost:389. Check your 
client's LDAP_URI settings.

[25/Oct/2022:12:10:07.709047940 +0200] - ERR - NSMMReplicationPlugin - 
repl5_inc_waitfor_async_results  - Timed out waiting for responses: 330754 
330879

Thanks in advance for your help.

Best Regards,
Dipankar Barua
___
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


--
Directory Server Development Team
___
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: Regular crash of the internal DirectoryServer389 replication

[Alexander Bokovoy]

On pe, 18 marras 2022, Dip Barua wrote:

Hello all,

I hope you are doing well.
I would like to have your help because I have a Replication crash
problem on 389DS.  Here is the below some Frequent Error :


Please open a bug for 389-ds-base package in Fedora's bugzilla.




[25/Oct/2022:02:03:15.698645866 +0200] - ERR - slapi_ldap_bind - Could not send bind 
request for id [cn=Directory Manager] authentication mechanism [SIMPLE]: error -1 (Can't 
contact LDAP server), system error -5987 (Invalid function argument.), network error 107 
(Transport endpoint is not connected, host "wam2p.lefoyer.lu:389")

[25/Oct/2022:02:06:27.558971677 +0200] - INFO - NSMMReplicationPlugin - 
bind_and_check_pwp - agmt="cn=lpfroot12" (wam2p:389): Replication bind with 
SIMPLE auth resumed

[25/Oct/2022:07:25:15.490236609 +0200] - ERR - log_ber_too_big_error - 
conn=36614 fd=78 Incoming BER Element may be misformed. This may indicate an 
attempt to use TLS on a plaintext port, IE ldaps://localhost:389. Check your 
client's LDAP_URI settings.

[25/Oct/2022:12:10:07.709047940 +0200] - ERR - NSMMReplicationPlugin - 
repl5_inc_waitfor_async_results  - Timed out waiting for responses: 330754 
330879

Thanks in advance for your help.

Best Regards,
Dipankar Barua
___
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




--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
___
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 prospoal: Enable bootupd for Fedora Silverblue & Kinoite (Self-Contained Change proposal)

[Timothée Ravier]

> No, the install script install script in an RPM trigger, so the write is
> still carried out by RPM.
> 
> I don't agree.  Just because a user can mess with files on the system
> doesn't mean the rpmdb is a lie, nor is it reasonable to go recheck all
> paths on the filesystem just in case they've done so, or create a daemon
> to provide an interface for doing that.

Note that this change here is only about Fedora Silverblue & Kinoite (and maybe 
IoT later). In those variants, /usr is read only and not expected to be changed 
by users. The rpmdb is thus pretty much guaranteed to match the content of the 
system by design for /usr.

On rpm-ostree based systems, system composes (image builds), package 
installation and updates are done "offline" so /boot is not available. The 
bootloader is not updated by an RPM trigger and this is why we need an 
additional tool to perform the update at another time. We've created a daemon 
because we need the update to be reliable so it should not fail if your SSH 
connections fails or if you Ctrl-C it in the middle, etc. This daemon is really 
small and socket activated so it's mostly never running.
___
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: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Naheem Zaffar]

> > what is the impact of the proposed change on non-x86 platforms? I
> > assume the proposal focuses on x86, but the distro wide flags are shared
> > across all platforms in Fedora, it means aarch64, ppc64le and s390x.
> > With RISC-V waiting behind the door ...
>
> None, because this proposal is not going to be implemented.
>

AFAIK none, but not for that reason: it seems to already be implemented and
part of the aarch64 abi. It would be helpfulmfornthe change request to
confirm this.

For the python code, also none because it will also be implemented as
default via upstream in python 3.12 and thus coming to fedora even without
this change request.

So the situation will be that the slowest mainstream arch and the slowest
mainstream code on all arches will have frame pointers enabled, but not on
the fastest arch for the fastest code.

>
___
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

CPE Weekly Update – Week 46 2022

[Lenka Segura]

*Hi everyone,This is a weekly report from the CPE (Community Platform
Engineering) Team.The report could be found at
https://communityblog.fedoraproject.org/cpe-weekly-update-week-46-2022
/.If
you want to receive weekly reports by emails in the future, please
subscribe to either https://communityblog.fedoraproject.org/
 or
https://discussion.fedoraproject.org/c/news/commblog/61
. We will stop
sending them in 2023.Regards,CPE Team*
___
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

Fwd: FOSDEM 2023 Distributions Devroom - Call for Participation

[Luna Jernberg]

-- Forwarded message -
From: Luna Jernberg 
Date: Fri, Nov 18, 2022 at 5:05 PM
Subject: Re: FOSDEM 2023 Distributions Devroom - Call for Participation
To: ddemaio , bittin , Luna
Jernberg , Luna Jernberg
, ddemaio , Community
support for Fedora users , Justin W.
Flory (he/him) , Vipul Siddharth
, Justin W. Flory
, Justin W. Flory ,
, Shaun McCance ,
,

Cc: 


Hey!

Will help out in the room next year

On Thu, Nov 17, 2022 at 3:18 PM ddemaio  wrote:
>
> Hi all,
> I'm forwarding this info for the project.
>
> *# **FOSDEM 2023 Distributions Devroom - Call for Participation*
>
> We're excited to announce that the Distributions Devroom is returning to
> FOSDEM 2023, in-person in Brussels for the full day on Sunday, February
> 5.
> The call for proposals is now open.
>
>
> *## About the Distributions Devroom*
>
> The Distributions Devroom is run by and for the people who build,
> package,
> and contribute to distributions of Linux and other software.
> Distributions
> remain a critical part of modern IT infrastructure, whether running on
> bare
> metal or in containers, from supercomputers to edge deployments. The
> Distributions Devroom provides a forum to share best practices on the
> entire distribution lifecycle, from building and integration to
> long-term
> support and security fixes.
>
>
> *## Call for Proposals*
>
> We welcome submissions targeted at contributors interested in issues
> unique
> to distributions, especially in the following topics:
>
> * Growing, participating, and working with communities around
> distributions
> * Automating building and testing to minimize human involvement
> * Cross-distribution collaboration on common issues
> * Distribution construction, installation, deployment, packaging, and
> content management
> * Balancing new code and active upstreams versus security updates and
> minimization of breaking changes
> * Delivering architecture-independent software
> * Working with vendors and including them in the community
> * The future of distributions and emerging trends
> * Non-engineering topics inside of distribution communities (e.g.
> documentation, marketing, internationalization, design, community
> operations, etc.)
> * Creating a secure supply chain by evaluating upstream components and
> providing a secure source for downstreams
>
>
> *## Important Dates*
>
> * Submission Deadline: Dec 20th 2022
> * Acceptance notifications: Dec 31th 2022
> * Final schedule announcement: Jan 14th 2022
>
>
> *## Process*
>
> 1. Register a FOSDEM Pentabarf account[1] and sign in.
> 2. Visit the FOSDEM CFP[2] and click "Create Event".
> 3. Make sure "Track" is set to "Distributions devroom" for wranglers to
> receive your submission!
> 4. Complete the form with your presentation details.
>
> Make sure your submission has the following details:
>
> * Title
> * One-paragraph abstract
> * Longer description including the benefit of your talk to your target
> audience, including a definition of your target audience.
> * Approximate length / type of submission (talk, BoF, …)
> * Links to related websites/blogs/talk material (if any)
>
> [1] https://penta.fosdem.org/user/new_account
> [2] https://penta.fosdem.org/submission/FOSDEM23
>
>
> *## About FOSDEM*
>
> FOSDEM is a free event for software developers to meet, share ideas and
> collaborate. Every year, thousands of developers of free and open source
> software from all over the world gather at the event in Brussels. FOSDEM
> hosts dozens of developer rooms, where community members run tracks on
> various topics.
___
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 2073893] CVE-2022-22624 webkitgtk: Use-after-free leading to arbitrary code execution

[bugzilla]

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

Fabio Valentini  changed:

   What|Removed |Added

 CC||decatho...@gmail.com



--- Comment #5 from Fabio Valentini  ---
Why has the Rust SIG been added to CC on this bug? We maintain no projects that
contain WebKit code.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2073893
___
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

SPDX Statistics

[Miroslav Suchý]

3 weeks ago it was:


1.

As of 2022-10-27:

1.

There are 23302 spec files in Fedora

2.

264 mentions "SPDX" in the spec changelog

3.

out of the remaining, 173 packages mention "SPDX" in dist-git log

4.

22865 packages need to be migrated yet.

5.

11371 package has straight answer from `license-fedora2spdx` and the 
migration is trivial.


Today we have:

* 23390 spec files in Fedora

* 29290 license tags in all spec files

* 19985 tags have not been converted to SPDX yet

I count as converted even all rubygem-* packages (509 pkgs) and all rust-* packages (2007 pkgs) - ecosystem maintainers 
will hand them seperately.


That means 9305 license tags has been converted so far. That is big change from 3 weeks ago where we had only 437. Part 
of this big change can be the difference in script that count it. Now I try to validate the license according the old 
rule and the new rule. If the old one is invalid and the new one is valid I assume that it is new package and already 
has the SPDX format.


You rocks in converting the tags. You converted almost 7k tags in just 3 weeks!

Here is the artifact from my check:

https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt

If your package is not listed there, then I assume it is SPDX.

If your package is listed there without any comment, then you still need to convert it, but `license-fedora2spdx` does 
not give straight answer.


If your package is like:

|abcMIDI - can be trivialy converted to GPL-2.0-or-later|

|then you can easily convert your license tag to this string.|

|If your package is like:|

|  abattis-cantarell-fonts warning: not valid as calaway nor as SPDX, please 
check
|

|then your license string is not valid using both old and new rules. But there is a lot of false negative - especially 
the *-fonts because they declare the license using macro, which I am unable to process (yet).|


|Fun fact: the script with the checks runs on my notebook for 32 hours.|

|I will try to re-run the check in few weeks again and will report you on how 
we are going.|

|Miroslav
|

|
|

___
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

Regular crash of the internal DirectoryServer389 replication

[Dip Barua]

Hello all,

I hope you are doing well.
I would like to have your help because I have a Replication crash problem on 
389DS. 
Here is the below some Frequent Error :


[25/Oct/2022:02:03:15.698645866 +0200] - ERR - slapi_ldap_bind - Could not send 
bind request for id [cn=Directory Manager] authentication mechanism [SIMPLE]: 
error -1 (Can't contact LDAP server), system error -5987 (Invalid function 
argument.), network error 107 (Transport endpoint is not connected, host 
"wam2p.lefoyer.lu:389")

[25/Oct/2022:02:06:27.558971677 +0200] - INFO - NSMMReplicationPlugin - 
bind_and_check_pwp - agmt="cn=lpfroot12" (wam2p:389): Replication bind with 
SIMPLE auth resumed

[25/Oct/2022:07:25:15.490236609 +0200] - ERR - log_ber_too_big_error - 
conn=36614 fd=78 Incoming BER Element may be misformed. This may indicate an 
attempt to use TLS on a plaintext port, IE ldaps://localhost:389. Check your 
client's LDAP_URI settings.

[25/Oct/2022:12:10:07.709047940 +0200] - ERR - NSMMReplicationPlugin - 
repl5_inc_waitfor_async_results  - Timed out waiting for responses: 330754 
330879

Thanks in advance for your help. 

Best Regards, 
Dipankar Barua
___
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

Fedora rawhide compose report: 20221118.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20221117.n.0
NEW: Fedora-Rawhide-20221118.n.0

= SUMMARY =
Added images:0
Dropped images:  4
Added packages:  2
Dropped packages:1
Upgraded packages:   46
Downgraded packages: 0

Size of added packages:  53.32 KiB
Size of dropped packages:22.22 KiB
Size of upgraded packages:   2.34 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20221117.n.0.ppc64le.tar.xz
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20221117.n.0.ppc64le.qcow2
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20221117.n.0.ppc64le.raw.xz
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20221117.n.0.iso

= ADDED PACKAGES =
Package: python-crossword-0.1.2-1.fc38
Summary: Python library for handling crossword puzzles
RPMs:python3-crossword
Size:31.12 KiB

Package: python-flake8-quotes-3.3.1-2.fc38
Summary: Flake8 extension for checking quotes in python
RPMs:python3-flake8-quotes
Size:22.20 KiB


= DROPPED PACKAGES =
Package: python-PyRSS2Gen-1.1-32.fc37
Summary: A Python library for generating RSS 2.0 feeds
RPMs:python3-PyRSS2Gen
Size:22.22 KiB


= UPGRADED PACKAGES =
Package:  awscli-1.27.11-1.fc38
Old package:  awscli-1.27.10-1.fc38
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.24 MiB
Size change:  -121 B
Changelog:
  * Thu Nov 17 2022 Gwyn Ciesla  - 1.27.11-1
  - 1.27.11


Package:  drupal7-addressfield-1.3-1.fc38
Old package:  drupal7-addressfield-1.2-16.fc37
Summary:  Manage a flexible address field, implementing the xNAL standard
RPMs: drupal7-addressfield
Size: 88.75 KiB
Size change:  1.95 KiB
Changelog:
  * Thu Nov 17 2022 Shawn Iwinski  - 1.3-1
  - Update to 1.3


Package:  drupal7-date-2.13-1.fc38
Old package:  drupal7-date-2.10-13.fc37
Summary:  Makes date/time fields available
RPMs: drupal7-date
Size: 246.69 KiB
Size change:  27.98 KiB
Changelog:
  * Thu Nov 17 2022 Shawn Iwinski  - 2.13-1
  - Update to 2.13 (RHBZ #1998661)


Package:  drupal7-diff-3.4-1.fc38
Old package:  drupal7-diff-3.3-14.fc37
Summary:  Show differences between content revisions
RPMs: drupal7-diff
Size: 54.60 KiB
Size change:  -1 B
Changelog:
  * Thu Nov 17 2022 Shawn Iwinski  - 3.4-1
  - Update to 3.4


Package:  drupal7-i18n-1.31-1.fc38
Old package:  drupal7-i18n-1.26-9.fc37
Summary:  Enables multilingual content
RPMs: drupal7-i18n
Size: 168.53 KiB
Size change:  951 B
Changelog:
  * Thu Nov 17 2022 Shawn Iwinski  - 1.31-1
  - Update to 1.31 (RHBZ #1848185)


Package:  drupal7-transliteration-3.2-17.fc38
Old package:  drupal7-transliteration-3.2-16.fc36
Summary:  Converts non-Latin text to US-ASCII and sanitizes file names
RPMs: drupal7-transliteration
Size: 147.50 KiB
Size change:  -60 B
Changelog:
  * Thu Jul 21 2022 Fedora Release Engineering  - 
3.2-17
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild


Package:  drupal7-views_bulk_operations-3.7-1.fc38
Old package:  drupal7-views_bulk_operations-3.5-9.fc37
Summary:  Provides a way of selecting multiple rows and applying operations 
to them
RPMs: drupal7-views_bulk_operations
Size: 59.03 KiB
Size change:  283 B
Changelog:
  * Thu Nov 17 2022 Shawn Iwinski  - 3.7-1
  - Update to 3.7 (RHBZ #1843610)


Package:  elk-8.5.10-1.fc38
Old package:  elk-8.3.22-2.fc37
Summary:  An all-electron full-potential linearised augmented-plane wave 
code
RPMs: elk elk-common elk-mpich elk-openmpi elk-species
Size: 15.11 MiB
Size change:  126.45 KiB
Changelog:
  * Thu Oct 27 2022 Mamoru TASAKA  - 8.3.22-3
  - Rebuild for new libxc

  * Thu Nov 17 2022 Marcin Dulak  - 8.5.10-1
  - New upstream release
  - Patch for libxc6 compatibility bug #2137308


Package:  elpa-2021.05.002-5.fc38
Old package:  elpa-2021.05.002-4.fc37
Summary:  High-performance library for parallel solution of eigenvalue 
problems
RPMs: elpa elpa-common elpa-common-devel elpa-devel elpa-mpich 
elpa-mpich-devel elpa-openmpi elpa-openmpi-devel
Size: 9.65 MiB
Size change:  -33.08 KiB
Changelog:
  * Fri Nov 18 2022 Mamoru TASAKA  - 2021.05.002-5
  - Rebuild for new papi


Package:  galera-26.4.13-1.fc38
Old package:  galera-26.4.12-1.fc38
Summary:  Synchronous multi-master wsrep provider (replication engine)
RPMs: galera
Size: 4.47 MiB
Size change:  79.18 KiB
Changelog:
  * Tue Nov 15 2022 Michal Schorm  - 26.4.13-1
  - Rebase to 26.4.13


Package:  gap-pkg-grpconst-2.6.3-1.fc38
Old package:  gap-pkg-grpconst

[Bug 2143900] Please provide perl-Module-ScanDeps for EPEL-9

[bugzilla]

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

Marc Dequènes (Duck)  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|NEW |CLOSED
Last Closed||2022-11-18 10:08:33



--- Comment #1 from Marc Dequènes (Duck)  ---
My bad, I did not understand how the repos changed. Looking at a CentOS machine
it is in the CRB (Codeready) sub-repo in /etc/yum.repos.d/centos.repo.
Sorry for the noise.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2143900
___
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 2143900] New: Please provide perl-Module-ScanDeps for EPEL-9

[bugzilla]

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

Bug ID: 2143900
   Summary: Please provide perl-Module-ScanDeps for EPEL-9
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Module-ScanDeps
  Severity: medium
  Assignee: jples...@redhat.com
  Reporter: d...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: anon.am...@gmail.com, jose.p.oliveira@gmail.com,
jples...@redhat.com,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Seems perl-Module-ScanDeps was dropped out of RHEL in version 9 but it's needed
at least for needrestart which is not available but unfortunately uninstallable
because of the lack of EL9 build. Could you please create one?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2143900
___
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] Re: EPEL-9 terrible updates (dav1d, libavif...)

[Nicolas Chauvet]

Le jeu. 17 nov. 2022 à 15:45, Michel Alexandre Salim
 a écrit :

> - I can package a dav1d092 compatibility package to provide
>   libdav1d.so.5
> - I can also package a compatibility libavif package, but against which
>   dav1d?
> - rebuild rpmfusion dependents against dav1d 1.0 and libavif 0.11
As RPM Fusion is concerned, the rebuild is done and is scheduled on
the next push.
(currently occurring).


> ## How do we better address (Fedora, EPEL) <=> RPM Fusion dependencies?
>
> On the Fedora side there is nothing currently that officially considers
> RPM Fusion (beyond the few allowlisted subsets like the Nvidia drivers).
> Amending the incompatible update policy to mention RPM Fusion is
> probably a no-go, but maybe mentioning "consider testing against
> well-known and popular third party repos" is doable?

While there might be a fedora project wide policy not to assume any
3rd party complement (but still the official documentation mentions
the project explicitly these days, with a dedicated notice).
I would still expect an appropriate communication level to be held at
the individual package maintainers level.
Not more, not less than any friendly communication that is expected to
be held to any external projects from Fedora.

Now of course one can't expect to contact any single maintained
project at scale (like copr projects or else), but there I draw the
difference between a single maintained project and a well known
community based one.

Thanks for raising this point.
I hope this problem will be behind us soon.
___
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: EPEL-9 terrible updates (dav1d, libavif...)

[Nicolas Chauvet]

Le jeu. 17 nov. 2022 à 15:45, Michel Alexandre Salim
 a écrit :

> - I can package a dav1d092 compatibility package to provide
>   libdav1d.so.5
> - I can also package a compatibility libavif package, but against which
>   dav1d?
> - rebuild rpmfusion dependents against dav1d 1.0 and libavif 0.11
As RPM Fusion is concerned, the rebuild is done and is scheduled on
the next push.
(currently occurring).


> ## How do we better address (Fedora, EPEL) <=> RPM Fusion dependencies?
>
> On the Fedora side there is nothing currently that officially considers
> RPM Fusion (beyond the few allowlisted subsets like the Nvidia drivers).
> Amending the incompatible update policy to mention RPM Fusion is
> probably a no-go, but maybe mentioning "consider testing against
> well-known and popular third party repos" is doable?

While there might be a fedora project wide policy not to assume any
3rd party complement (but still the official documentation mentions
the project explicitly these days, with a dedicated notice).
I would still expect an appropriate communication level to be held at
the individual package maintainers level.
Not more, not less than any friendly communication that is expected to
be held to any external projects from Fedora.

Now of course one can't expect to contact any single maintained
project at scale (like copr projects or else), but there I draw the
difference between a single maintained project and a well known
community based one.

Thanks for raising this point.
I hope this problem will be behind us soon.
___
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: Non-responsive maintainer check for jehane

[Mattia Verga via devel]

Il 18/11/22 00:11, Sérgio Basto ha scritto:
> Almost a year later we haven't any reply
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2031448
>
>
> Marianne not have any activity since Fev 2022  (expect in a
> tag_package_owners entry!?!? )
>
> Last login in FAS:
> jehane 2021-02-18
>
> Last action on koji:
> Fri, 09 Sep 2022 tag_package_owners entry created by humaton [still
> active]
>
> Last package update on bodhi:
> 2021-02-01 13:54:59 on package perl-POE-Component-Client-Ping-1.176-
> 1.fc33
> Last actions performed according to fedmsg:
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-15 01:23:48
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-15 01:23:48
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-04 15:03:10
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-04 15:03:09
> - org.fedoraproject.prod.bugzilla.bug.update on 2021-12-13 16:34:31
> - org.fedoraproject.prod.bugzilla.bug.new on 2021-12-13 16:34:31
> - org.fedoraproject.prod.bugzilla.bug.update on 2021-12-12 02:40:57
> - org.fedoraproject.prod.bugzilla.bug.new on 2021-12-12 02:40:57
>
See https://pagure.io/find-inactive-packagers/issue/311

They will probably be removed from packagers next week.

Mattia

___
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: Direct to stable updates

[Mattia Verga via devel]

Il 17/11/22 18:10, Adam Williamson ha scritto:
> On Wed, 2022-11-16 at 17:37 +, Mattia Verga via devel wrote:
>> Kevin, the PR for Bodhi is nearly finished, it will add support for
>> using the 'frozen' release state to avoid pausing the push cron job and
>> avoid direct pending to stable push of updates when the release is frozen.
>>
>> I'll open a ticket to releng for changing the usual workflow of new
>> releases once the PR gets merged and a new Bodhi release is drafted and
>> pushed to prod. About the avoidance of direct to stable pushing, do you
>> think it needs to be discussed by FESCo?
> Hey Mattia! Can you keep me in the loop on the new version and
> deployment also? The final phase of my work on critical path status by
> group is waiting on that. Thanks!

Hello Adam,

as soon as the last batch of PRs I submitted are merged, I plan to ask
@abompard (or whoever is taking care of Bodhi now) to draft and deploy
the new version.

I can take care of drafting the new version, if they agree, but then
someone has to deploy it to stg/prod, as I'm not part of infra-sig and I
don't know ansible/OC. My wishes are to have the new version with the
new features land in prod early now, so that if a bugfix release is
needed it can be deployed before the next freeze and that releng can
adjust their SOP to start using the 'frozen' release state in the next
release cycle.

I'll keep you posted. Do you need any other change about gating pushed
before the next release is drafted?

Mattia

___
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