[Bug 2158385] Upgrade perl-Data-GUID to 0.051

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Data-GUID-0.051-1.fc38
 Resolution|--- |RAWHIDE
Last Closed||2023-01-09 06:55:10



--- Comment #1 from Jitka Plesnikova  ---
Built by corsepiu


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

[Orion Poplawski]

On 1/8/23 19:30, Tom Callaway wrote:

Please open a bug on this so I can track it.



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

On Sat, Jan 7, 2023 at 11:11 AM Orion Poplawski > wrote:


On 1/4/23 17:52, Tom Callaway wrote:
 > Hi Fedora,
 >
 > TeXLive 2022 (composed of texlive-base and texlive SRPMs) is
landing in
 > rawhide today. I've done extensive local testing in mock to try
to make
 > sure it doesn't break anything obvious... but the size and scope
of TL
 > means that there are probably still some bugs introduced by this
update.
 >
 > Please let me know if something stops building as a result of the
new
 > texlive packages, either via email, bugzilla, twitter, mastodon, or
 > carrier pigeon, with as much detail as you can provide.
 >
 > I do not plan to push this to any stable Fedora, BUT, I have
tested with
 > it installed over Fedora 37 and it seems to work okay for me.
 >
 > Apologies on the delay in getting this done. I realize TL 2023 is
 > probably coming out in a few months, hopefully, it will not take
a year
 > for me to get that update in place.
 >
 > ~spot

Seems to be breaking LaTeXML's tests:
https://apps.fedoraproject.org/koschei/package/LaTeXML?collection=f38 


Unfortunately koschei's query to see what else might be affected hits a
gateway timeout:


https://koschei.fedoraproject.org/affected-by/texlive-latex?epoch1=9=20210325=52.fc38=10=svn63825=55.fc38=f38
 


Would be nice if that could be given more time to complete.

-- 
Orion Poplawski

he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com 
Boulder, CO 80301 https://www.nwra.com/ 

___
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



___
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


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic 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

[Test-Announce] Proposal to CANCEL: 2023-01-09 Fedora QA Meeting

[Geoffrey Marr]

Hey everyone,

We still have several people out for the holidays so I am proposing we
cancel the meeting Monday, January 9th, 2023. We can count on having a
meeting the following week. If anyone has anything urgent, let me know and
we can get it posted to the test list in the meantime.

Geoff Marr
IRC: coremodule
___
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

Malicious communication (was: Re: Schedule for Tuesday's FESCo Meeting (2023-01-03))

[Neal Gompa]

On Sun, Jan 8, 2023 at 9:44 PM Kevin Kofler via devel
 wrote:
>
> Kevin Kofler via devel wrote:
> > PS: The impression I get is that everything was deliberately rigged so
> > that the vote would end up the way it did:
> >
> > 1. A new ticket was filed, in order to exclude the participants of the
> > previous discussion.
> > 2. The people watching the old ticket were NOT notified.
> > 3. The Tools Team was NOT notified.
> > 4. The proponents of the Change, on the other hand, WERE notified.
> >
> > So, with all of the above, the discussion participants were preselected to
> > only include people in favor of the change.
> >
> > 5. The ticket was filed in the middle of the holiday season. Many people
> > in Europe are on vacation until today.
> > 6. There was NO thread about the reopening of the discussion on the
> > mailing list. The first message that mentioned the issue on the mailing
> > list was "Schedule for Tuesday's FESCo Meeting (2023-01-03)" from
> > 2023-01-03 09:39 UTC, only 7 hours 21 minutes before the meeting. This is
> > in contrast to the Change policy requiring at least a week between the
> > mailing list announcement and opening the FESCo ticket.
> > 7. Only 4 days had elapsed between the (unannounced) opening of the ticket
> > and the vote. This is clearly insufficient. The one week in the Change
> > policy that I cited above is designed as a minimum time for discussion.
> > 8. The change was approved only 2 weeks before the mass rebuild, leaving
> > little to no time to revert it in the contigency case.
> >
> > So, this ensured that whoever was deliberately NOT invited had no chance
> > to find out by themselves and intervene before it was too late.
> >
> > This strikes me as extremely intransparent and undemocratic.
>
> PPS: This is particularly striking when you consider that the same person
> who filed the new ticket and excluded one side from the discussion entirely
> was the one complaining just a month earlier about the OLD discussion:
>
> > Yes, but the other stakeholder I wanted there didn't even know it was on
> > the agenda yesterday, which meant we mostly heard only one side (the
> > toolchain people).
>
> See: https://pagure.io/fesco/issue/2817#comment-830204
>
> Complaining about something and then deliberately doing the same thing the
> other way round, way to go!
>

You ascribe malice where there is none. The reason I didn't link it in
the original ticket when I made that one was because I didn't think of
it. I don't have some evil plan or something like that as you
describe.

Moreover, your general attitude, tone, and verbiage is unnecessarily
negative. You're also acting like a hypocrite.

I'm extremely tired of how you communicate on this mailing list. I've
been quiet about it for years and years. But people leave Fedora
because of you. Once again, I'm having discussions with people trying
to convince them Fedora isn't a bad place because of you.

You need to sit back and reflect on yourself. Go get some help on
improving your communication or something. If Linus Torvalds can
become a better person and shake off his reputation for tearing people
down, you can change and become a more constructive communicator.

Too many people give you leeway because you're not considered a native
English speaker. You know what? I've met far too many better
communicators who have English as a second, third, or even fourth
language.

There are only three other people in Fedora that give me similar
heartburn, and you should not be in that camp.

Please, for everyone's sake, do something to improve yourself.


-- 
真実はいつも一つ！/ Always, there's only one truth!
___
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: Schedule for Tuesday's FESCo Meeting (2023-01-03)

[Kevin Kofler via devel]

Kevin Kofler via devel wrote:
> PS: The impression I get is that everything was deliberately rigged so
> that the vote would end up the way it did:
> 
> 1. A new ticket was filed, in order to exclude the participants of the
> previous discussion.
> 2. The people watching the old ticket were NOT notified.
> 3. The Tools Team was NOT notified.
> 4. The proponents of the Change, on the other hand, WERE notified.
> 
> So, with all of the above, the discussion participants were preselected to
> only include people in favor of the change.
> 
> 5. The ticket was filed in the middle of the holiday season. Many people
> in Europe are on vacation until today.
> 6. There was NO thread about the reopening of the discussion on the
> mailing list. The first message that mentioned the issue on the mailing
> list was "Schedule for Tuesday's FESCo Meeting (2023-01-03)" from
> 2023-01-03 09:39 UTC, only 7 hours 21 minutes before the meeting. This is
> in contrast to the Change policy requiring at least a week between the
> mailing list announcement and opening the FESCo ticket.
> 7. Only 4 days had elapsed between the (unannounced) opening of the ticket
> and the vote. This is clearly insufficient. The one week in the Change
> policy that I cited above is designed as a minimum time for discussion.
> 8. The change was approved only 2 weeks before the mass rebuild, leaving
> little to no time to revert it in the contigency case.
> 
> So, this ensured that whoever was deliberately NOT invited had no chance
> to find out by themselves and intervene before it was too late.
> 
> This strikes me as extremely intransparent and undemocratic.

PPS: This is particularly striking when you consider that the same person 
who filed the new ticket and excluded one side from the discussion entirely 
was the one complaining just a month earlier about the OLD discussion:

> Yes, but the other stakeholder I wanted there didn't even know it was on
> the agenda yesterday, which meant we mostly heard only one side (the
> toolchain people).

See: https://pagure.io/fesco/issue/2817#comment-830204

Complaining about something and then deliberately doing the same thing the 
other way round, way to 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

Re: TeXLive 2022 landing in rawhide today

[Tom Callaway]

Please open a bug on this so I can track it.

Thanks,
~spot

On Sat, Jan 7, 2023 at 11:11 AM Orion Poplawski  wrote:

> On 1/4/23 17:52, Tom Callaway wrote:
> > Hi Fedora,
> >
> > TeXLive 2022 (composed of texlive-base and texlive SRPMs) is landing in
> > rawhide today. I've done extensive local testing in mock to try to make
> > sure it doesn't break anything obvious... but the size and scope of TL
> > means that there are probably still some bugs introduced by this update.
> >
> > Please let me know if something stops building as a result of the new
> > texlive packages, either via email, bugzilla, twitter, mastodon, or
> > carrier pigeon, with as much detail as you can provide.
> >
> > I do not plan to push this to any stable Fedora, BUT, I have tested with
> > it installed over Fedora 37 and it seems to work okay for me.
> >
> > Apologies on the delay in getting this done. I realize TL 2023 is
> > probably coming out in a few months, hopefully, it will not take a year
> > for me to get that update in place.
> >
> > ~spot
>
> Seems to be breaking LaTeXML's tests:
> https://apps.fedoraproject.org/koschei/package/LaTeXML?collection=f38
>
> Unfortunately koschei's query to see what else might be affected hits a
> gateway timeout:
>
>
> https://koschei.fedoraproject.org/affected-by/texlive-latex?epoch1=9=20210325=52.fc38=10=svn63825=55.fc38=f38
>
> Would be nice if that could be given more time to complete.
>
> --
> Orion Poplawski
> he/him/his  - surely the least important thing about me
> IT Systems Manager 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane   or...@nwra.com
> Boulder, CO 80301 https://www.nwra.com/
>
> ___
> 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
>
___
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: Schedule for Tuesday's FESCo Meeting (2023-01-03)

[Neal Gompa]

On Sun, Jan 8, 2023 at 9:08 PM Kevin Kofler via devel
 wrote:
>
> Also, the pull request implementing the change was merged 6 days BEFORE the
> change was approved by FESCo! It is unacceptable to sneak unapproved changes
> into Rawhide this way in order to "create facts".
>

Actually, no it wasn't. Adding knobs is perfectly fine when it doesn't
have a practical impact by default.

The actual change to switch the default wasn't merged until Friday:
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/231



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
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: Schedule for Tuesday's FESCo Meeting (2023-01-03)

[Kevin Kofler via devel]

Also, the pull request implementing the change was merged 6 days BEFORE the 
change was approved by FESCo! It is unacceptable to sneak unapproved changes 
into Rawhide this way in order to "create facts".

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: TeXLive 2022 landing in rawhide today

[Orion Poplawski]

On 1/8/23 12:11, Kevin Fenzi wrote:

On Sat, Jan 07, 2023 at 09:11:32AM -0700, Orion Poplawski wrote:


Seems to be breaking LaTeXML's tests:
https://apps.fedoraproject.org/koschei/package/LaTeXML?collection=f38

Unfortunately koschei's query to see what else might be affected hits a
gateway timeout:

https://koschei.fedoraproject.org/affected-by/texlive-latex?epoch1=9=20210325=52.fc38=10=svn63825=55.fc38=f38

Would be nice if that could be given more time to complete.


Looks like it takes about 45s for that to load.
I increased the timeout to 180s. :)

kevin


Thank you.


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic 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

Heads-up: xeus 3.0.3 coming to Rawhide with .so version bump

[Elliott Sales de Andrade]

In one week (2022-01-15), or slightly later, I plan to build xeus 3.0.3 for
Rawhide.

This update will bump the .so version from 5 to 8, and xeus remains a leaf
package AFAIK, so there should be no impact to other packages.

-- 
Elliott
___
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: TeXLive 2022 landing in rawhide today

[Kevin Fenzi]

On Sat, Jan 07, 2023 at 09:11:32AM -0700, Orion Poplawski wrote:
> 
> Seems to be breaking LaTeXML's tests:
> https://apps.fedoraproject.org/koschei/package/LaTeXML?collection=f38
> 
> Unfortunately koschei's query to see what else might be affected hits a
> gateway timeout:
> 
> https://koschei.fedoraproject.org/affected-by/texlive-latex?epoch1=9=20210325=52.fc38=10=svn63825=55.fc38=f38
> 
> Would be nice if that could be given more time to complete.

Looks like it takes about 45s for that to load. 
I increased the timeout to 180s. :) 

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

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

[Kevin Kofler via devel]

Vitaly Zaitsev via devel wrote:
> The original proposal received a lot of negative feedback. Only a few
> big corporations will get benefit and end users will get a 3-10%
> performance penalty which is absolutely unacceptable.

Not to mention the size impact. My request in the original discussion to 
quantify the size impact was completely ignored by the change proponents, so 
we have no idea how badly this change will bloat Fedora. This should have 
been the first question by FESCo, even before performance!

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: Schedule for Tuesday's FESCo Meeting (2023-01-03)

[Kevin Kofler via devel]

Kevin Kofler via devel wrote:
> 7. Only 4 days had elapsed between the (unannounced) opening of the ticket
> and the vote. This is clearly insufficient. The one week in the Change

Sorry, there were actually 6 days. Still, less than a week, and there was no 
mailing list announcement. The community was under the impression that the 
matter was settled when it was actually not. So I still believe that the 
transparency policies were not followed.

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: Schedule for Tuesday's FESCo Meeting (2023-01-03)

[Kevin Kofler via devel]

Kevin Kofler via devel wrote:
> Still, it gives an extremely bad impression of rushing this through
> without giving anybody the chance to object.
> 
> I also do not see why this needed to be approved for F38 on such a short
> notice and could not wait for F39.

PS: The impression I get is that everything was deliberately rigged so that 
the vote would end up the way it did:

1. A new ticket was filed, in order to exclude the participants of the 
previous discussion.
2. The people watching the old ticket were NOT notified.
3. The Tools Team was NOT notified.
4. The proponents of the Change, on the other hand, WERE notified.

So, with all of the above, the discussion participants were preselected to 
only include people in favor of the change.

5. The ticket was filed in the middle of the holiday season. Many people in 
Europe are on vacation until today.
6. There was NO thread about the reopening of the discussion on the mailing 
list. The first message that mentioned the issue on the mailing list was 
"Schedule for Tuesday's FESCo Meeting (2023-01-03)" from 2023-01-03 09:39 
UTC, only 7 hours 21 minutes before the meeting. This is in contrast to the 
Change policy requiring at least a week between the mailing list 
announcement and opening the FESCo ticket.
7. Only 4 days had elapsed between the (unannounced) opening of the ticket 
and the vote. This is clearly insufficient. The one week in the Change 
policy that I cited above is designed as a minimum time for discussion.
8. The change was approved only 2 weeks before the mass rebuild, leaving 
little to no time to revert it in the contigency case.

So, this ensured that whoever was deliberately NOT invited had no chance to 
find out by themselves and intervene before it was too late.

This strikes me as extremely intransparent and undemocratic.

Therefore, I hereby request that the vote be annulled as having happened in 
violation of the Change policy.

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: flatbuffers 23.1.4 coming to Rawhide with .so version bump

[Ben Beasley]

In one week (2022-01-15), or slightly later, I plan to build flatbuffers 
23.1.4 for Rawhide[1].


The .so versioning for flatbuffers is not quite right; the version 
number is based on the year, and the .so version is the major version 
number. Since upstream offers no ABI stability guarantees, they have 
been asked to start using the whole version number as the SOVERSION in 
the future[2] to make sure there aren’t ABI changes without .so version 
bumps.


Anyway, for better or worse, this update will bump the .so version from 
22 to 23, and flatbuffers remains a leaf package, so there should be no 
impact to other packages.


[1] https://src.fedoraproject.org/rpms/flatbuffers/pull-request/4

[2] https://github.com/google/flatbuffers/issues/7759
___
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 2159041] perl-Perl-Critic-1.148 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Perl-Critic-1.148-1.fc
   ||38
Last Closed||2023-01-08 13:42:43



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-2a54806bd7 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2159041
___
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 2159041] perl-Perl-Critic-1.148 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2159041
___
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: WASM from Ruby - Lightning Chess Web App

[Jun Aruga (he / him)]

On Sun, Jan 8, 2023 at 11:51 AM Philip Rhoades via devel
 wrote:
>
> People,
>
> Over the holidays we had our irregular Family Lightning Chess
> competition (10 seconds per move) - I have not found an online web site
> that will work exactly with our rules and it occurs to me that this
> would be a nice project for me to get working via a Ruby2WASM project.
> If I could get that project working, it would allow the family to have
> at least annual electronic competitions for the times when not all the
> relatives can physically make it to the one place at the one time . .
>
> What do you think?

Good idea!
Ruby 3.2 released a few weeks ago, started to support the WASM built
feature, and I guess that people want to use it easily.
The first choice for the packaging is to create WASM built binaries as
a sub package of "ruby" https://src.fedoraproject.org/rpms/ruby or to
create a new package with the new RPM spec file.

We discussed if we shipped WASM binaries a bit in the ruby-sig@
mailing list. I can recommend you to join the list to discuss people
in the ruby related packages  if you like.

* Ruby 3.2 - ruby-sig@
  
https://lists.fedoraproject.org/archives/list/ruby-...@lists.fedoraproject.org/thread/FK3XRKUICBS7HFZVEENSEGJ4ZMKCVNWF/

Fedora WASM SIP might be launched. You can check the situation.

* Web Assembly on Fedora: interested in a Fedora SIG to work on this?
  
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JO2YYDQPC65EMQVO6UCHDV4SAKQNSGKV/

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
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

pghmcfc pushed to rpms/perl-Params-ValidationCompiler (rawhide). "Update to 0.31 (..more)"

[notifications]

Notification time stamped 2023-01-08 13:04:27 UTC

From 731daddbfc2a89127f7c2f85ff4ba55e5adb61fc Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Jan 08 2023 13:03:35 +
Subject: Update to 0.31


- New upstream release 0.31
  - Require Class::XSAccessor 1.17+ when trying to load it; earlier versions
cause test failures (GH#27)
- Use SPDX-format license tag

---

diff --git a/perl-Params-ValidationCompiler.rpmlintrc 
b/perl-Params-ValidationCompiler.rpmlintrc
deleted file mode 100644
index b53aedf..000
--- a/perl-Params-ValidationCompiler.rpmlintrc
+++ /dev/null
@@ -1,3 +0,0 @@
-from Config import *
-addFilter("spelling-error %description -l en_US uncompromised -> ");
-addFilter("spelling-error Summary\(en_US\) validator -> ");
diff --git a/perl-Params-ValidationCompiler.spec 
b/perl-Params-ValidationCompiler.spec
index a5733d8..595d0cc 100644
--- a/perl-Params-ValidationCompiler.spec
+++ b/perl-Params-ValidationCompiler.spec
@@ -6,10 +6,10 @@
 %endif
 
 Name:  perl-Params-ValidationCompiler
-Version:   0.30
-Release:   17%{?dist}
+Version:   0.31
+Release:   1%{?dist}
 Summary:   Build an optimized subroutine parameter validator once, use it 
forever
-License:   Artistic 2.0
+License:   Artistic-2.0
 URL:   https://metacpan.org/release/Params-ValidationCompiler
 Source0:   
https://cpan.metacpan.org/modules/by-module/Params/Params-ValidationCompiler-%{version}.tar.gz
 BuildArch: noarch
@@ -22,7 +22,7 @@ BuildRequires:perl(ExtUtils::MakeMaker) > 6.75
 # Module
 BuildRequires: perl(B)
 BuildRequires: perl(Carp)
-BuildRequires: perl(Class::XSAccessor)
+BuildRequires: perl(Class::XSAccessor) >= 1.17
 BuildRequires: perl(Eval::Closure)
 BuildRequires: perl(Exception::Class)
 BuildRequires: perl(Exporter)
@@ -57,7 +57,7 @@ BuildRequires:perl(Types::Standard)
 %endif
 # Dependencies
 Requires:  perl(:MODULE_COMPAT_%(eval "`perl -V:version`"; echo $version))
-Recommends:perl(Class::XSAccessor)
+Recommends:perl(Class::XSAccessor) >= 1.17
 Recommends:perl(Sub::Util) >= 1.40
 
 %description
@@ -87,6 +87,12 @@ make test
 %{_mandir}/man3/Params::ValidationCompiler::Exceptions.3*
 
 %changelog
+* Sun Jan  8 2023 Paul Howarth  - 0.31-1
+- Update to 0.31
+  - Require Class::XSAccessor 1.17+ when trying to load it; earlier versions
+cause test failures (GH#27)
+- Use SPDX-format license tag
+
 * Fri Jul 22 2022 Fedora Release Engineering  - 
0.30-17
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
 
diff --git a/sources b/sources
index 178b644..482bbcf 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Params-ValidationCompiler-0.30.tar.gz) = 
5911f9317f0b72e17c72435420a3b6b9f36780ab70715510c46e847970094e730169b9b3085f29cb23ee0aca2e78f7f9edd0d093859a1062869f35c90172bf05
+SHA512 (Params-ValidationCompiler-0.31.tar.gz) = 
e3265cc6a5fc9761dd6ae82c3875711c5766242ab0f1edd74cc74296fdac22b6c23e48ba4768e895701ca8a00bd81677056713124b8edaa0b340eae1b33cf9c4



https://src.fedoraproject.org/rpms/perl-Params-ValidationCompiler/c/731daddbfc2a89127f7c2f85ff4ba55e5adb61fc?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

[Bug 2159015] perl-Test-Deep-1.204 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Test-Deep-1.204-1.fc38
 Resolution|--- |ERRATA
Last Closed||2023-01-08 12:54:42



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-f83e021125 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2159015
___
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 2159015] perl-Test-Deep-1.204 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


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

WASM from Ruby - Lightning Chess Web App

[Philip Rhoades via devel]

People,

Over the holidays we had our irregular Family Lightning Chess 
competition (10 seconds per move) - I have not found an online web site 
that will work exactly with our rules and it occurs to me that this 
would be a nice project for me to get working via a Ruby2WASM project.  
If I could get that project working, it would allow the family to have 
at least annual electronic competitions for the times when not all the 
relatives can physically make it to the one place at the one time . .


What do you think?

Regards,

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

Re: Review requests: perl-Feature-Compat-Class, perl-Feature-Compat-Try (needed for licensecheck update)

[Arthur Bols]

On 6/01/2023 13:47, Sandro Mani wrote:

Hi

licensecheck-3.3.1 grew two new dependencies, reviews here:

perl-Feature-Compat-Class: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2158741
perl-Feature-Compat-Try: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2158742


Happy to review in exchange.

Thanks
Sandro


I took perl-Feature-Compat-Class, the other one was already taken by Petr.
If you have some free time, I'd love to have diff-so-fancy (perl script) 
reviewed: https://bugzilla.redhat.com/show_bug.cgi?id=2150097


--
Arthur Bols
fas/irc: principis
___
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