date:20230711

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-HTTP-Tiny-0.086-1.fc38 |perl-HTTP-Tiny-0.086-1.fc38
   ||perl-HTTP-Tiny-0.086-1.fc37



--- Comment #6 from Fedora Update System  ---
FEDORA-2023-1be6532d43 has been pushed to the Fedora 37 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=2216784

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202216784%23c6
___
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 2222144] New: perl-Test-Compile-3.3.0 is available

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

Bug ID: 144
   Summary: perl-Test-Compile-3.3.0 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Test-Compile
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mmasl...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 3.3.0
Upstream release that is considered latest: 3.3.0
Current version/release in rawhide: 3.2.2-2.fc39
URL: https://metacpan.org/dist/Test-Compile/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3388/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Test-Compile


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20144%23c0
___
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

Schedule for Thursday's FESCo Meeting (2023-07-13) [NEW MEETING TIME]

2023-07-11 Thread Zbigniew Jędrzejewski-Szmek

Note that the meeting time has moved. Or actually, the meeting time hasn't
moved, but the day is different. It still ends in "y", and also starts with
a "t".

Following is the list of topics that will be discussed in the FESCo
meeting Thursday at 17:00UTC in #fedora-meeting on irc.libera.chat.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2023-07-13 17:00 UTC'

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

= Discussed and Voted in the Ticket =

#3009 Change: Aspell Deprecation
https://pagure.io/fesco/issue/3009
APPROVED (+5, 0, 0)

#3010 Change: Automatic Cloud Reboot on Updates
https://pagure.io/fesco/issue/3010
APPROVED (+6, 0, 0)

#3015 Updates policy exception request for python-openapi-schema-validator
https://pagure.io/fesco/issue/3015
APPROVED (+4, 0, 0)

= Followups =


= New business =

#3020 Proposal: FESCO should own creating issues for change proposals
https://pagure.io/fesco/issue/3020

#3030 Change: FedoraWorkstationImageBuilder
https://pagure.io/fesco/issue/3030

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

#3019 Withdraw F39 Change: AutoFirstBootServices
https://pagure.io/fesco/issue/3019


= Open Floor = 

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

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

Re: [rawhide] ICU upgrade to 73.2

On Tue, Jul 11, 2023 at 11:06 PM Richard W.M. Jones 
wrote:

> Yes I think it's better if you could proceed with brltty.
>
> Note I pushed a commit earlier today which excludes %{ix86} from the
> OCaml subpackage.  In OCaml 5 / Fedora 39 we are going to drop support
> for this architecture entirely.
>
> > - build bumped icu in your side-tag too, so brlapi rebuilt there
> > would be built both against new icu and new ocaml?
>
> I'm not sure whether or not this is necessary, but in any case don't
> worry as I will sort it out when doing the OCaml rebuild.
>
> Rich.
>

FYI, it seems brltty is failing anyway on i686, with:
configure: error: C compiler cannot create executables

( https://koji.fedoraproject.org/koji/taskinfo?taskID=103241186 )

Adding limb to CC.

-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Michael Catanzaro

On Tue, Jul 11 2023 at 09:18:57 PM +0200, Leon Fauster via devel 
 wrote:

C8S ends 2024, while RHEL8 ends 2029
C9S ends 2027, while RHEL9 ends 2032


You're forgetting the Extended life cycle support phase. RHEL 8 and 9 
will both have a 13-year lifecycle (down from 14 years). See this table:


https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates

Michael

___
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: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

2023-07-11 Thread Michael Catanzaro

On Tue, Jul 11 2023 at 02:19:31 PM -0500, Jeremy Linton
wrote:
Having finally had a chance to look at the list of collected metrics
i'm

a bit worried about just how much information is being/can be gathered
by the project, as well as the frequency it is being gathered.

Personally, I think it would benefit fedora if questions such as "is
anyone actually using this hardware/driver/package" could be answered.
OTOH, the metrics presented above go far beyond that. I'm not sure why
its necessary to know how many times, or how long a particular
application is being used.

I think Endless needs more data than we do. ;) If they don't have
application usage data then they could be *really* wasting their time
developing stuff that users are not using. Fedora works a quite
differently, but I can imagine we'd still be interested in counting use
of at least some applications (e.g. was GNOME Builder started today?).

For avoidance of doubt, we won't actually collect the same metrics that
Endless does. Metrics collected by Fedora will need to be individually
approved via some sort of community process.

So, I would suggest that the intended metrics are included as part of
this proposal as well as the interval, and that it wouldn't be changed
without further community approval. Doing this would go a long way to
convincing me, and likely others, that its not worth the effort to
manually rip the entire subsystem out of fedora at the first chance on
my machines.

I agree that community approval should be required to make changes to
what data we collect.

I was really hoping the initial proposal would not include particular
metrics, so that each metric could be discussed separately outside the
discussion of whether we should do this at all, but a lot of people are
requesting this, so maybe we'll need to add a few.

If there is to be a "process" for changing them, then I think that
needs

to be documented here rather than hand waving it away too.

I agree. Once we agree on what process should be used, I'll edit it
into the change proposal. I've started a discussion on this here:

https://discussion.fedoraproject.org/t/potential-process-and-policies-for-approving-particular-metric-collection-a-breakout-topic-for-the-f40-change-request-on-privacy-preserving-telemetry-for-fedora-workstation/85632/2

IMHO, the data shouldn't be collected more frequently than every 6
months or so, which allows each collection to be presented to the
user,

rather than having it just uploading the data in the background. Nor
should it be tracking _user_ actions, which I would differentiate from
machine state (bios machine type, RAM, installed packages, application
crashes, failed suspend/resume, kinds of things).

But given course grained tracking, why isn't it part of server/IoT/etc
as well, other than the current focus on gnome? Surely knowing that
only

one user is running $APPLICATION on a server is useful too.

We do want to track user action, though (e.g. "what control center
panels are used the most?"

6 months is too infrequent. I'm open to discussing how frequently
metrics are uploaded, but I think the current value is 30 minutes.
Presenting each collection to the user would be too much clutter, but
I'll plan to build some way to inspect this manually for users who want
to do so.

I think telemetry would be useful for server, IoT, and Fedora spins as
well, but this is something for each edition or spin to decide for
themselves. The technology is somewhat tied to GNOME because it depends
on D-Bus and GVariant, but it can be used on servers too.

I also think its useful here to describe _exactly_ how to
disable/remove

the component, as well as where the opt-in/out settings are stored in
the filesystem, how to change it, and where the log of reported data
for

a given machine can be retrieved.

You can do: sudo dnf remove eos-event-recorder-daemon

The settings are stored in /etc/metrics/eos-metrics-permissions.conf

I'm not sure about logs of reported data, I agree but we'll have to
build such functionality if it doesn't exist already.

I'll create a note to edit this into the change proposal.

To make this a little more confusing, metrics collection is actually
separate from uploading. Collection is always initially enabled,
while

uploading is always initially disabled. The graphical toggle enables
or disables both at the same time. That is, a newly-installed Fedora
system will always collect metrics locally at first, but the
collected

metrics will be deleted and never submitted to Fedora if the user
disables the metrics collection toggle on the privacy page. If the
user leaves the toggle enabled, then the collected metrics may be
submitted only after finishing the privacy page.

(trimmed rest)

Thanks for getting this far.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to

Re: OT: Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

2023-07-11 Thread Demi Marie Obenour

On 7/11/23 15:45, Jeremy Linton wrote:
> On 7/10/23 13:16, Demi Marie Obenour wrote:
>> On 7/10/23 02:30, Vitaly Zaitsev via devel wrote:
>>> On 10/07/2023 02:49, Demi Marie Obenour wrote:
 QtWebEngine (used by Falkon) was a
 month or more behind upstream Chromium last I checked.
>>>
>>> Qt5QtWebEngine is an extremely vulnerable thing. It still uses Chromium
>>> 87.0[1].
>>>
>>> Current Chromium version: 105.0.
>>>
>>> [1]: https://wiki.qt.io/QtWebEngine/ChromiumVersions
>>
>> In that case it should be removed from the distribution.  Can KDE
>> mail clients be built without QtWebEngine?  This would disable
>> HTML email support, but plain text mail might still work.
> 
> The problem isn't QtWebEngine, the latest Qt 6.X is using 108 according 
> to the link above.
> 
> The problem seems to be that not everything has moved to the 6.x branch yet.
> 
> https://iskdeusingqt6.org/

It’s a mixture.  The best possible outcome would be for QtWebEngine to be
part of upstream Chromium and use Chromium’s release schedule.  Not sure if
that is possible/practical.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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: [rawhide] ICU upgrade to 73.2

2023-07-11 Thread Richard W.M. Jones

On Tue, Jul 11, 2023 at 10:59:31PM +0200, Frantisek Zatloukal wrote:
> 
> 
> On Tue, Jul 11, 2023 at 10:56 PM Richard W.M. Jones  wrote:
> 
> I think the OCaml build will take a while.
> 
> Is this related to the (concurrent) Perl rebuild?
> 
> 
> No, the perl rebuild is separate from this. There shouldn't be any overlap,
> afaik?
> 
> In such case, I guess I should:
>
> - proceed with brlapi rebuild in my side-tag, merge that side-tag to
> the f39 baserepo tomorrow morning

Yes I think it's better if you could proceed with brltty.

Note I pushed a commit earlier today which excludes %{ix86} from the
OCaml subpackage.  In OCaml 5 / Fedora 39 we are going to drop support
for this architecture entirely.

> - build bumped icu in your side-tag too, so brlapi rebuilt there
> would be built both against new icu and new ocaml?

I'm not sure whether or not this is necessary, but in any case don't
worry as I will sort it out when doing the OCaml rebuild.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
___
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: [rawhide] ICU upgrade to 73.2

On Tue, Jul 11, 2023 at 10:56 PM Richard W.M. Jones 
wrote:

> I think the OCaml build will take a while.
>
> Is this related to the (concurrent) Perl rebuild?
>

No, the perl rebuild is separate from this. There shouldn't be any overlap,
afaik?

In such case, I guess I should:
- proceed with brlapi rebuild in my side-tag, merge that side-tag to the
f39 baserepo tomorrow morning
- build bumped icu in your side-tag too, so brlapi rebuilt there would be
built both against new icu and new ocaml?


-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
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: [rawhide] ICU upgrade to 73.2

2023-07-11 Thread Richard W.M. Jones

On Tue, Jul 11, 2023 at 02:40:42PM -0600, Jerry James wrote:
> On Tue, Jul 11, 2023 at 2:35 PM Frantisek Zatloukal  
> wrote:
> > On Tue, Jul 11, 2023 at 9:47 PM Jerry James  wrote:
> >> > brltty
> >>
> >> This package is also being built in a side tag for the OCaml 5.0.0
> >> update, which is already ongoing.  Can you wait until the OCaml builds
> >> are done to build this one?  Otherwise, we're going to rebuild this
> >> poor package over and over to get all of its deps right.
> >
> >
> > Sure, task https://koji.fedoraproject.org/koji/taskinfo?taskID=103239771 
> > canceled, will wait for ocaml rebuild. Unfortunately, I'd already committed 
> > the bump to the dist-git repo (just release inc), hope that doesn't mind!
> 
> It looks like we haven't gotten to brltty yet in the OCaml builds.
> How long do you think it would be before you could merge your side
> tag?  If it won't be long, maybe we should wait for you.
> 
> CCing Richard Jones, who is actually running the OCaml builds.

I think the OCaml build will take a while.

Is this related to the (concurrent) Perl rebuild?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: F39 Change Proposal: Color Bash Prompt (System Wide)

2023-07-11 Thread Eduard Lucena

What I did with the i3 Spin was to ask to the Design team for something
that fits Fedora's color palette. I think for this you could do the same.


Br,

-- 
Eduard Lucena
Móvil: +56962318010
GNU/Linux User #589060
Ubuntu User #8749
Fedora Marketing Representative
___
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: [rawhide] ICU upgrade to 73.2

On Tue, Jul 11, 2023 at 10:41 PM Jerry James  wrote:

>
> It looks like we haven't gotten to brltty yet in the OCaml builds.
> How long do you think it would be before you could merge your side
> tag?  If it won't be long, maybe we should wait for you.
>
> CCing Richard Jones, who is actually running the OCaml builds.
>
>
I was planning to do the initial merge (minus some long to build packages
like qt webkit/webengine, cross-depending on qtbase packages which also
depend on icu) tomorrow morning CET (in about 10 hours from now).


-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
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: [rawhide] ICU upgrade to 73.2

2023-07-11 Thread Jerry James

On Tue, Jul 11, 2023 at 2:35 PM Frantisek Zatloukal  wrote:
> On Tue, Jul 11, 2023 at 9:47 PM Jerry James  wrote:
>> > brltty
>>
>> This package is also being built in a side tag for the OCaml 5.0.0
>> update, which is already ongoing.  Can you wait until the OCaml builds
>> are done to build this one?  Otherwise, we're going to rebuild this
>> poor package over and over to get all of its deps right.
>
>
> Sure, task https://koji.fedoraproject.org/koji/taskinfo?taskID=103239771 
> canceled, will wait for ocaml rebuild. Unfortunately, I'd already committed 
> the bump to the dist-git repo (just release inc), hope that doesn't mind!

It looks like we haven't gotten to brltty yet in the OCaml builds.
How long do you think it would be before you could merge your side
tag?  If it won't be long, maybe we should wait for you.

CCing Richard Jones, who is actually running the OCaml builds.
-- 
Jerry James
http://www.jamezone.org/
___
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: [rawhide] ICU upgrade to 73.2

On Tue, Jul 11, 2023 at 9:47 PM Jerry James  wrote:

> > brltty
>
> This package is also being built in a side tag for the OCaml 5.0.0
> update, which is already ongoing.  Can you wait until the OCaml builds
> are done to build this one?  Otherwise, we're going to rebuild this
> poor package over and over to get all of its deps right.
>

Sure, task https://koji.fedoraproject.org/koji/taskinfo?taskID=103239771
canceled, will wait for ocaml rebuild. Unfortunately, I'd already
committed the bump to the dist-git repo (just release inc), hope that
doesn't mind!

-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
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: List of long term FTBFS packages to be retired in August

2023-07-11 Thread Mikel Olasagasti

Hi,

Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2023
uzt. 11(a), ar. (15:07)):
>

> golang-code-cloudfoundry-bytefmt go-sig, mikelo2

Fixed

> golang-github-aliyun-cli bdperkin, go-sig

Fixed

> golang-github-d2g-dhcp4clientalexsaezm, go-sig

Fixed

> golang-github-dennwc-varint  alexsaezm, go-sig

Fixed

> golang-github-macaron-inject go-sig, mikelo2

Fixed

> golang-github-moby-spdystreamgo-sig, mikelo2

Builds fine in Koschei and no BZ

> golang-github-openapi-validate   alexsaezm, go-sig

Builds fine in Koschei and no BZ

> golang-github-rogpeppe-charset   go-sig, mikelo2

Fixed

> golang-github-yvasiyarov-metrics alexsaezm, go-sig

Fixed

> golang-gopkg-tomb-1  go-sig, mikelo2

Fixed

> golang-gopkg-validator-2 alexsaezm, go-sig

To retire after uber-tally doesn't depend anymore. Will check after
dep refreshes.

--
Mikel
___
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: [rawhide] ICU upgrade to 73.2

2023-07-11 Thread Jerry James

On Tue, Jul 11, 2023 at 3:10 AM Frantisek Zatloukal  wrote:
> Later today, I'll be starting with rebuilds of packages depending on icu. The 
> rebuilds will take place in f39-build-side-69764 for all packages returned by 
> repoquery --whatrequires 'libicu*.so.72()(64bit)' (list cleaned up, converted 
> to source package names, attached at the end of the message).
>
> Please, if you're going to make changes in affected packages before the side 
> tag gets merged, make the build in the said side tag. I expect to merge the 
> side tag asap with most of the affected packages built and then continue 
> building things that take longer to build (webkit/libreoffice) later.

[snip]

> brltty

This package is also being built in a side tag for the OCaml 5.0.0
update, which is already ongoing.  Can you wait until the OCaml builds
are done to build this one?  Otherwise, we're going to rebuild this
poor package over and over to get all of its deps right.
-- 
Jerry James
http://www.jamezone.org/
___
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

OT: Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

2023-07-11 Thread Jeremy Linton


On 7/10/23 13:16, Demi Marie Obenour wrote:

On 7/10/23 02:30, Vitaly Zaitsev via devel wrote:

On 10/07/2023 02:49, Demi Marie Obenour wrote:

QtWebEngine (used by Falkon) was a
month or more behind upstream Chromium last I checked.


Qt5QtWebEngine is an extremely vulnerable thing. It still uses Chromium
87.0[1].

Current Chromium version: 105.0.

[1]: https://wiki.qt.io/QtWebEngine/ChromiumVersions


In that case it should be removed from the distribution.  Can KDE
mail clients be built without QtWebEngine?  This would disable
HTML email support, but plain text mail might still work.


The problem isn't QtWebEngine, the latest Qt 6.X is using 108 according 
to the link above.


The problem seems to be that not everything has moved to the 6.x branch yet.

https://iskdeusingqt6.org/





More generally, WebKit is the only major browser engine with
upstream support for being embedded, so it is the only embedded
browser engine that is supportable security-wise.  Unfortunately,
it is also the least secure of the major browser engines on Linux
last I checked, and in particular is far behind Chromium.

___
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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Leon Fauster via devel


Am 11.07.23 um 21:02 schrieb Chris Adams:

Once upon a time, Mattia Verga  said:

Since RHEL is made out from Centos Stream and Centos Stream is made out from 
Fedora ELN, can't Alma and Rocky branch directly from Fedora?
Can we collaborate in some way with those communities so that we support each 
other? I mean, like we have Fedora ELN and EPEL...


Their goal is to replicate, as near as practical, the versions, bug
fixes, patches, etc. in RHEL, so that the usage (and for some people,
running of pre-compiled binaries) is functionally identical to a given
RHEL release.  Since Red Hat has long used the "patch rather than
upgrade" approach for most packages during a release's lifetime, the
only way to get a practically-identical system is to get those same
patches.

In theory, any patch to a package in say RHEL 9.2 should eventually land
in CentOS Stream 9, because RHEL 9.3 should be forked from CentOS Stream
9, but that doesn't always happen in a convenient time frame (plus
sometimes something may be fixed one way in a 9.2 update but differently
in 9.3).  Also, CentOS Stream 9 will stop getting updated much sooner
than RHEL 9.x - when RHEL 9.x transitions to "maintenance mode" (no new
functionality planned, just bug/security fixes), CentOS Stream 9 will
stop altogether.

And Fedora ELN is aimed at CentOS Stream 10, which will eventually be
used to make RHEL 10.0, so is not useful for replicating RHEL 9.x
updates.



An addendum to this:

C8S ends 2024, while RHEL8 ends 2029
C9S ends 2027, while RHEL9 ends 2032

--
Leon
___
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: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

2023-07-11 Thread Jeremy Linton


Hi,


On 7/6/23 11:10, Aoife Moloney wrote:

Important process note: we are experimenting with using Fedora

(trimming stuff because this proposal is huge)



We intend to deploy the Endless OS metrics system.
[https://blogs.gnome.org/wjjt/2023/07/05/endless-oss-privacy-preserving-metrics-system/
This blog post] contains a description of how the system works. We do
not plan to deploy the eos-phone-home component in Fedora.


So, the following is just _my_ opinion, don't read more than that into it:


Having finally had a chance to look at the list of collected metrics i'm 
a bit worried about just how much information is being/can be gathered 
by the project, as well as the frequency it is being gathered.


Personally, I think it would benefit fedora if questions such as "is 
anyone actually using this hardware/driver/package" could be answered. 
OTOH, the metrics presented above go far beyond that. I'm not sure why 
its necessary to know how many times, or how long a particular 
application is being used.





=== How will data collection be approved? ===

The proposal owners feel it is essential to ensure the Fedora
community has ultimate oversight over metrics collection. Community
control is required to maintain user trust. If this change proposal is
approved, then we'll need new policies and procedures to ensure
community oversight over metrics collection and ensure Fedora users
can be confident that our metrics collection does not violate their
privacy.


So, I would suggest that the intended metrics are included as part of 
this proposal as well as the interval, and that it wouldn't be changed 
without further community approval. Doing this would go a long way to 
convincing me, and likely others, that its not worth the effort to 
manually rip the entire subsystem out of fedora at the first chance on 
my machines.


If there is to be a "process" for changing them, then I think that needs 
to be documented here rather than hand waving it away too.




We can say "we would never collect personally-identifiable data" and
write software that really doesn't collect any such data, but this
alone will never be enough to ensure user confidence. We will need a
metrics collection policy that describes what sort of data may be
collected by Fedora (anonymous, non-invasive), and what sort of data
may not be collected. Such a policy does not exist currently. We will
also want to ensure the Fedora community has ultimate control over
which particular metrics are collected. One option is that each metric
to be collected should be separately approved by FESCo. Collection of
particular metrics in a particular data format is ultimately an
engineering decision, and therefore FESCo seems like an appropriate
approval point. Because FESCo members are elected regularly by the
Fedora community, this also provides the community with ultimate
control over metrics collection via the election process. But other
oversight and approval structures would work too.

=== What data might we collect? ===

We are not proposing to collect any of these particular metrics just
yet, because a process for Fedora community approval of metrics to be
collected does not yet exist. That said, in the interests of maximum
transparency, we wish to give you an idea of what sorts of metrics we
might propose to collect in the future.

One of the main goals of metrics collection is to analyze whether Red
Hat is achieving its goal to make Fedora Workstation the premier
developer platform for cloud software development. Accordingly, we
want to know things like which IDEs are most popular among our users,
and which runtimes are used to create containers using Toolbx.



IMHO, the data shouldn't be collected more frequently than every 6 
months or so, which allows each collection to be presented to the user, 
rather than having it just uploading the data in the background. Nor 
should it be tracking _user_ actions, which I would differentiate from 
machine state (bios machine type, RAM, installed packages, application 
crashes, failed suspend/resume, kinds of things).



But given course grained tracking, why isn't it part of server/IoT/etc 
as well, other than the current focus on gnome? Surely knowing that only 
one user is running $APPLICATION on a server is useful too.




Metrics can also be used to inform user interface design decisions.
For example, we want to collect the clickthrough rate of the
recommended software banners in GNOME Software to assess which banners
are actually useful to users. We also want to know how frequently
panels in gnome-control-center are visited to determine which panels
could be consolidated or removed, because there are other settings we
want to add, but our usability research indicates that the current
high quantity of settings panels already makes it difficult for users
to find commonly-used settings.


(trimming)


=== User control ===

A new metrics collection setting will be added to the privacy page in

Re: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Chris Adams

Once upon a time, Mattia Verga  said:
> Since RHEL is made out from Centos Stream and Centos Stream is made out from 
> Fedora ELN, can't Alma and Rocky branch directly from Fedora?
> Can we collaborate in some way with those communities so that we support each 
> other? I mean, like we have Fedora ELN and EPEL...

Their goal is to replicate, as near as practical, the versions, bug
fixes, patches, etc. in RHEL, so that the usage (and for some people,
running of pre-compiled binaries) is functionally identical to a given
RHEL release.  Since Red Hat has long used the "patch rather than
upgrade" approach for most packages during a release's lifetime, the
only way to get a practically-identical system is to get those same
patches.

In theory, any patch to a package in say RHEL 9.2 should eventually land
in CentOS Stream 9, because RHEL 9.3 should be forked from CentOS Stream
9, but that doesn't always happen in a convenient time frame (plus
sometimes something may be fixed one way in a 9.2 update but differently
in 9.3).  Also, CentOS Stream 9 will stop getting updated much sooner
than RHEL 9.x - when RHEL 9.x transitions to "maintenance mode" (no new
functionality planned, just bug/security fixes), CentOS Stream 9 will
stop altogether.

And Fedora ELN is aimed at CentOS Stream 10, which will eventually be
used to make RHEL 10.0, so is not useful for replicating RHEL 9.x
updates.

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

CCfits license correction: "BSD" to "CFITSIO"

2023-07-11 Thread Sergio Pascual

Hello, the license of CCfits was incorrectly identified as "BSD", it is
actually "CFITSIO". I have updated it in rawhide.

Regards, Sergio
___
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

cfitsio license correction: "MIT" to "CFITSIO"

2023-07-11 Thread Sergio Pascual

Hello, the license of cfitsio was incorrectly identified as "MIT", it is
actually "CFITSIO". I have updated it in rawhide.

Regards, Sergio
___
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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Andreas Tunek

Den tis 11 juli 2023 kl 19:12 skrev Mattia Verga via devel <
devel@lists.fedoraproject.org>:

> Since RHEL is made out from Centos Stream and Centos Stream is made out
> from Fedora ELN, can't Alma and Rocky branch directly from Fedora?
>
Can we collaborate in some way with those communities so that we support
> each other? I mean, like we have Fedora ELN and EPEL...
>

Wouldn't it make more sense to branch out from CentOS Stream if they want
to be close to RHEL?

/Andreas


>
>
> Inviato da Proton Mail mobile
>
>
>
>  Messaggio originale 
> Il 11 Lug 2023, 12:49, Kevin Kofler via devel <
> devel@lists.fedoraproject.org> ha scritto:
>
>
> Oracle has (finally – the community projects Rocky and Alma were much
> quicker to react) made an announcement about the situation:
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/
> 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
> ___
> 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: Immutable Variants & Persistence

On Tue, Jul 11, 2023 at 10:47 AM Jonathan Steffan 
wrote:

> 2. All userspace is in RAM
>

For example, let's install `dnf install tuxpuck`. I'd expect `tuxpuck` to
be installed and playable. I wouldn't have to reboot after layering this
using ostree.

I'd just like to play the game and reboot. Upon reboot, we are back to step
1.

-- 
Jonathan Steffan
___
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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Mattia Verga via devel

Since RHEL is made out from Centos Stream and Centos Stream is made out from 
Fedora ELN, can't Alma and Rocky branch directly from Fedora?
Can we collaborate in some way with those communities so that we support each 
other? I mean, like we have Fedora ELN and EPEL...

Inviato da Proton Mail mobile

 Messaggio originale 
Il 11 Lug 2023, 12:49, Kevin Kofler via devel ha scritto:

> Oracle has (finally – the community projects Rocky and Alma were much quicker 
> to react) made an announcement about the situation: 
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/
>  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___
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: Immutable Variants & Persistence

Stephen,

Maybe. I was thinking more:

1. Boot Silverblue
2. All userspace is in RAM
3. Reboot
4. See step 1

On Tue, Jul 11, 2023 at 10:42 AM Stephen Gallagher 
wrote:

> On Tue, Jul 11, 2023 at 12:01 PM Jonathan Steffan
>  wrote:
> >
> > On Tue, Jul 11, 2023 at 6:55 AM Richard W.M. Jones 
> wrote:
> >>
> >>
> >> Isn't this what Silverblue is for?
> >>
> >> https://fedoraproject.org/silverblue/
> >
> >
> > Yes, close.
> >
> > Could it be possible that all changes are only recorded COW and after
> reboot they are discarded?
> >
>
> Sounds like "ostree native containers" to me...
> https://coreos.github.io/rpm-ostree/container/
> ___
> 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
>


-- 
Jonathan Steffan
___
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: F39 Change Proposal: Color Bash Prompt (System Wide)

2023-07-11 Thread Eric Curtin

If you are looking for other ideas, I embed loads of useful info in my prompt:

https://imgur.com/a/kVCyVPK

time, so you can roughly measure the time between commands, CPU architecture, 
how far ahead or behind you are in a git repo.

But this gets a +1 from me regardless of the result, colors are good if the 
terminal supports it.
___
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: Immutable Variants & Persistence

2023-07-11 Thread Stephen Gallagher

On Tue, Jul 11, 2023 at 12:01 PM Jonathan Steffan
 wrote:
>
> On Tue, Jul 11, 2023 at 6:55 AM Richard W.M. Jones  wrote:
>>
>>
>> Isn't this what Silverblue is for?
>>
>> https://fedoraproject.org/silverblue/
>
>
> Yes, close.
>
> Could it be possible that all changes are only recorded COW and after reboot 
> they are discarded?
>

Sounds like "ostree native containers" to me...
https://coreos.github.io/rpm-ostree/container/
___
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: Immutable Variants & Persistence

On Tue, Jul 11, 2023 at 6:55 AM Richard W.M. Jones 
wrote:

>
> Isn't this what Silverblue is for?
>
> https://fedoraproject.org/silverblue/


Yes, close.

Could it be possible that all changes are only recorded COW and after
reboot they are discarded?


-- 
Jonathan Steffan
___
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] [Fedocal] Reminder meeting : EPEL Steering Committee

2023-07-11 Thread tdawson

Dear all,

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

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

A general agenda is the following:

#topic aloha

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

#topic Old Business (if needed)

#topic General Issues / Open Floor




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

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

Re: List of long term FTBFS packages to be retired in August

2023-07-11 Thread Jerry James

On Tue, Jul 11, 2023 at 7:07 AM Miro Hrončok  wrote:
> sbcl green, rdieter

About a month ago, I opened a PR to fix this.  It looks like the PR
was merged, but no build was done.  I am taking it upon myself to
update sbcl to the next released version (the PR was for 2.3.5, but
2.3.6 has since been released) and do the build.  I hope I am not
stepping on any toes.

> xmvn-connector-ivy   mizdebsk

The problem appears to be that apache-ivy does not have VFS support,
which xmvn-connector-ivy needs.  It doesn't have VFS support because
apache-commons-vfs was retired.  I need apache-commons-vfs back anyway
for other reasons, so I have filed a review bug:

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

-- 
Jerry James
https://www.jamezone.org/
___
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

jplesnik pushed to rpms/perl-List-MoreUtils-XS (rawhide). "Perl 5.38 rebuild"

Notification time stamped 2023-07-11 14:31:48 UTC

From ba0aeda950118e3f1b168b500a6905619f486412 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jul 11 2023 14:31:40 +
Subject: Perl 5.38 rebuild


---

diff --git a/perl-List-MoreUtils-XS.spec b/perl-List-MoreUtils-XS.spec
index f05c6b8..747c097 100644
--- a/perl-List-MoreUtils-XS.spec
+++ b/perl-List-MoreUtils-XS.spec
@@ -7,7 +7,7 @@
 
 Name:  perl-List-MoreUtils-XS
 Version:   0.430
-Release:   9%{?dist}
+Release:   10%{?dist}
 Summary:   Provide compiled List::MoreUtils functions
 # Code from List-MoreUtils < 0.417 is GPL-1.0-or-later OR Artistic-1.0-Perl
 # Anything after that is Apache-2.0
@@ -89,6 +89,9 @@ make test
 %{_mandir}/man3/List::MoreUtils::XS.3*
 
 %changelog
+* Tue Jul 11 2023 Jitka Plesnikova  - 0.430-10
+- Perl 5.38 rebuild
+
 * Tue Jun 13 2023 Paul Howarth  - 0.430-9
 - Disable extra test in RHEL builds (based on
   https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/pull-request/1)



https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/c/ba0aeda950118e3f1b168b500a6905619f486412?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

Orphaned libdnf-plugin-swidtags, planning to orphan swid-tools

2023-07-11 Thread Jan Pazdziora


Hello,

the SWID tag enablement introduced by
https://fedoraproject.org/wiki/Changes/SWID_Tag_Enablement did not lead
to a wider SWID tag adoption, and other technologies (IMA, SPDX) seem
to be more relevant for the purpose SWID tags were expected to play,
four years later.

For that reason I've orphaned libdnf-plugin-swidtags.

I'm looking for ways to reach out to the rpm-software-management-sig
who are co-maintainers of https://src.fedoraproject.org/rpms/swid-tools
to see what their interest / plang might be about swid-tools but
overall I'm leaning towards orphaning swid-tools as well shortly.

The fact that latest python and dnf5 changes lead to FTBFS or FTI

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

are also contributing to my decision to orphan.

-- 
Jan Pazdziora | Sr. Principal Software Engineer | Red Hat 
___
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 2219122] perl-Statistics-Descriptive-3.0801 is available

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Statistics-Descriptive
   ||-3.0801-1.fc39
 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2023-07-11 14:21:55



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-a7cf84bb45 has been pushed to the Fedora 39 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=2219122

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

Re: Modernize Thread Building Blocks for Fedora 39

2023-07-11 Thread Jonathan Wakely

On Thu, 6 Jul 2023 at 15:15, Jonathan Wakely  wrote:
>
> On Thu, 6 Jul 2023 at 11:46, Jonathan Wakely  wrote:
> >
> > Oops, I meant to CC the package-ow...@fedoraproject.org addresses for
> > the packages I'll be changing (see below).
> >
> > For blender, gazebo, opencascade, and opensubdiv, it's a one line
> > change to the spec file, something like:
> >
> > -BuildRequires:  tbb-devel
> > +BuildRequires:  tbb2020.3-devel
> >
> > If you're happy for me to push that and rebuild the package as
> > provenpackager, let me know and I won't bother you with a pull
> > request.
> >
> > For USD there's a change needed to FindTBB.cmake, so it's slightly
> > more complex (but only slightly).
>
> USD is currently blocked by the python 3.12 update anyway:
>
> DEBUG util.py:442:   Problem 1: conflicting requests
> DEBUG util.py:442:- nothing provides python(abi) = 3.11 needed by
> python3-pyopengl-3.1.6-1.fc38.x86_64 from build
> DEBUG util.py:442:   Problem 2: conflicting requests
> DEBUG util.py:442:- nothing provides python(abi) = 3.11 needed by
> python3-pyside2-1:5.15.7-2.fc38.x86_64 from build
> DEBUG util.py:444:  (try to add '--skip-broken' to skip uninstallable 
> packages)

gazebo is also blocked by the python 3.12 update.

So there are several packages which I need to move to tbb2020.3-devel,
but I can't even do a scratch build to verify that it would build. And
I can't update tbb itself to the new version while packages like
gazebo and blender won't build with the new version.

So I'm doing nothing and hoping that some of the python blockers get
fixed soon enough for me to do the TBB work before the mass rebuild.


>
>
> >
> >
> > On Thu, 6 Jul 2023 at 11:11, Jonathan Wakely  wrote:
> > >
> > > This is a status update for
> > > https://fedoraproject.org/wiki/Changes/F39ModernizeTBB
> > >
> > > The tbb2020.3 compat package has now been added to rawhide:
> > > https://bodhi.fedoraproject.org/updates/FEDORA-2023-15ccd1cedb
> > >
> > > It doesn't include the docs or python modules (you can use the main
> > > tbb package for those).
> > >
> > > The tbb2020.3-devel subpackage conflicts with tbb-devel, as a given
> > > package only needs to build against one or the other, not both.
> > >
> > > Later today I will start submitting pull requests for the packages
> > > which need to switch from BuildRequires: tbb-devel (or similar) to
> > > using tbb2020.3-devel instead. The affected packages are:
> > >
> > > blender
> > > gazebo
> > > opencascade
> > > opensubdiv
> > > usd
> > >
> > > After those packages have been rebuilt against tbb2020.3 I'll create a
> > > side tag and push a new spec file to the 'tbb' package to update it to
> > > version 2021.9.0 (based on the
> > > https://copr.fedorainfracloud.org/coprs/jjames/TBB2021/ package made
> > > by Jerry James). Then the remaining packages that depend on tbb can be
> > > rebuilt against the new tbb in the side tag.
___
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

jplesnik pushed to rpms/perl-IO-FDPass (rawhide). "Perl 5.38 rebuild"

Notification time stamped 2023-07-11 14:06:35 UTC

From f7e7188b71dab4de32516866d0dec5f075a57f94 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jul 11 2023 14:06:26 +
Subject: Perl 5.38 rebuild


---

diff --git a/perl-IO-FDPass.spec b/perl-IO-FDPass.spec
index 6dbde2d..0d1f23d 100644
--- a/perl-IO-FDPass.spec
+++ b/perl-IO-FDPass.spec
@@ -1,6 +1,6 @@
 Name:  perl-IO-FDPass
 Version:   1.3
-Release:   8%{?dist}
+Release:   9%{?dist}
 Summary:   Pass a file descriptor over a socket
 License:   GPL-1.0-or-later OR Artistic-1.0-Perl
 URL:   https://metacpan.org/release/IO-FDPass
@@ -57,6 +57,9 @@ make test
 %{_mandir}/man3/IO::FDPass.3*
 
 %changelog
+* Tue Jul 11 2023 Jitka Plesnikova  - 1.3-9
+- Perl 5.38 rebuild
+
 * Fri Jan 20 2023 Fedora Release Engineering  - 1.3-8
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
 



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

Re: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Michael J Gruber

Kevin Kofler via devel venit, vidit, dixit 2023-07-11 12:49:10:
> Oracle has (finally – the community projects Rocky and Alma were much 
> quicker to react) made an announcement about the situation:
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/

Thanks for the pointer.

They really make sure that they come out as "the last standing good
ones" from this. Cleverly written. And they do have valid points.

It's kind of sad when you know where RedHat and Oracle are coming from,
and how predictable that PR twist ist.

Now, if Orcale really makes sure to pick from CentOS Stream as closely
(to RHEL) as possible we can take gusses how long it will take Alma and
Rocky to change upstreams, or become obsolete.

Michael
___
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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Andreas Tunek

Den tis 11 juli 2023 kl 12:49 skrev Kevin Kofler via devel <
devel@lists.fedoraproject.org>:

> Oracle has (finally – the community projects Rocky and Alma were much
> quicker to react) made an announcement about the situation:
>
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/
>
> Kevin Kofler
>

I wonder what they would build Oracle Linux on if RH stop making RHEL?

"Finally, to IBM, here’s a big idea for you. You say that you don’t want to
pay all those RHEL developers? Here’s how you can save money: just pull
from us. Become a downstream distributor of Oracle Linux. We will happily
take on the burden."

/Andreas



> ___
> 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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Tomasz Torcz

On Tue, Jul 11, 2023 at 12:49:10PM +0200, Kevin Kofler via devel wrote:
> Oracle has (finally – the community projects Rocky and Alma were much 
> quicker to react) made an announcement about the situation:
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/

 SUSE too, but it is not so funny as Oracle's
 https://www.suse.com/news/SUSE-Preserves-Choice-in-Enterprise-Linux/

-- 
Tomasz Torcz“Funeral in the morning, IDE hacking
to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox
___
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 2222007] New: perl-HTTP-Tiny-0.088 is available

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

Bug ID: 007
   Summary: perl-HTTP-Tiny-0.088 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-HTTP-Tiny
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.088
Upstream release that is considered latest: 0.088
Current version/release in rawhide: 0.086-1.fc39
URL: http://search.cpan.org/dist/HTTP-Tiny/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/2982/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-HTTP-Tiny


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20007%23c0
___
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

jplesnik pushed to rpms/perl-Ref-Util-XS (rawhide). "Perl 5.38 rebuild"

Notification time stamped 2023-07-11 13:28:39 UTC

From a097466fa66c63dec4fc5a7291d315e01977d4e4 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jul 11 2023 13:28:33 +
Subject: Perl 5.38 rebuild


---

diff --git a/perl-Ref-Util-XS.spec b/perl-Ref-Util-XS.spec
index a1ada6e..431eb3c 100644
--- a/perl-Ref-Util-XS.spec
+++ b/perl-Ref-Util-XS.spec
@@ -7,7 +7,7 @@
 
 Name:  perl-Ref-Util-XS
 Version:   0.117
-Release:   18%{?dist}
+Release:   19%{?dist}
 Summary:   Utility functions for checking references
 License:   MIT
 URL:   https://metacpan.org/release/Ref-Util-XS
@@ -70,6 +70,9 @@ make test
 %{_mandir}/man3/Ref::Util::XS.3*
 
 %changelog
+* Tue Jul 11 2023 Jitka Plesnikova  - 0.117-19
+- Perl 5.38 rebuild
+
 * Thu May 11 2023 Paul Howarth  - 0.117-18
 - SPDX migration
 - Use author-independent source URL



https://src.fedoraproject.org/rpms/perl-Ref-Util-XS/c/a097466fa66c63dec4fc5a7291d315e01977d4e4?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

jplesnik pushed to rpms/perl-Crypt-IDEA (rawhide). "Perl 5.38 rebuild"

Notification time stamped 2023-07-11 13:20:04 UTC

From 40ff3ff9747140e246e85b7cb90dc634e5115c61 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jul 11 2023 13:19:43 +
Subject: Perl 5.38 rebuild


---

diff --git a/perl-Crypt-IDEA.spec b/perl-Crypt-IDEA.spec
index cb4e0e0..fed3918 100644
--- a/perl-Crypt-IDEA.spec
+++ b/perl-Crypt-IDEA.spec
@@ -1,7 +1,7 @@
 Summary:   Perl interface to IDEA block cipher
 Name:  perl-Crypt-IDEA
 Version:   1.10
-Release:   26%{?dist}
+Release:   27%{?dist}
 License:   BSD with advertising
 URL:   https://metacpan.org/release/Crypt-IDEA
 Source0:   
https://cpan.metacpan.org/modules/by-module/Crypt/Crypt-IDEA-%{version}.tar.gz
@@ -64,6 +64,9 @@ make test
 %{_mandir}/man3/Crypt::IDEA.3*
 
 %changelog
+* Tue Jul 11 2023 Jitka Plesnikova  - 1.10-27
+- Perl 5.38 rebuild
+
 * Fri Jan 20 2023 Fedora Release Engineering  - 
1.10-26
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Crypt-IDEA/c/40ff3ff9747140e246e85b7cb90dc634e5115c61?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 2219122] perl-Statistics-Descriptive-3.0801 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219122%23c1
___
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: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

2023-07-11 Thread Michael Catanzaro



I think what happens is: somebody (anybody) can report a post, if it 
gets enough reports it gets proactively hidden before a moderator can 
review it. Do our moderators eventually review such posts to ensure 
they're truly inappropriate? Seems clear that the post is question 
should not have been hidden.


Michael

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

[rpms/perl-Statistics-Descriptive] PR #1: 3.0801 bump; Package tests

2023-07-11 Thread Jitka Plesnikova


jplesnik merged a pull-request against the project: 
`perl-Statistics-Descriptive` that you are following.

Merged pull-request:

``
3.0801 bump; Package tests
``

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

Re: Immutable Variants & Persistence

2023-07-11 Thread Richard W.M. Jones

On Tue, Jul 11, 2023 at 04:19:13AM -0600, Jonathan Steffan wrote:
> Hello,
>
> During a recent IRC conversation the question of always booting
> Fedora fresh on hardware came up. We've got the Live variants which
> do this already and it's possible to directly write them to a local
> disk. Similar to booting from a USB stick, you could use the local
> hardware instead. However, it's not really a read-only boot. Booting
> from a locally copied Live environment still allows full access.
>
> Is there a way to configure the immutable versions to have a similar
> RAM only overlay?
>
> I'd imagine an immutable base that is automatically updated and has
> all other runtime changes discarded on reboot. There could be an
> automatically logged in user that has extremely limited
> privileges and can only work in the current boot userspace.
>
> Previously this has been discussed as something like a kiosk mode,
> but I could see this used in many other situations.

Isn't this what Silverblue is for?

https://fedoraproject.org/silverblue/

Rich.


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Statistics-Descriptive] PR #1: 3.0801 bump; Package tests

2023-07-11 Thread Jitka Plesnikova


jplesnik opened a new pull-request against the project: 
`perl-Statistics-Descriptive` that you are following:
``
3.0801 bump; Package tests
``

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

Fedora rawhide compose report: 20230711.n.0 changes

2023-07-11 Thread Fedora Rawhide Report

OLD: Fedora-Rawhide-20230710.n.0
NEW: Fedora-Rawhide-20230711.n.0

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

Size of added packages:  53.32 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1.97 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -3.55 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230711.n.0.iso

= DROPPED IMAGES =
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20230710.n.0.iso
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20230710.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230710.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20230710.n.0.iso

= ADDED PACKAGES =
Package: golang-github-hebcal-0.9.22-1.fc39
Summary: A perpetual Jewish Calendar (golang)
RPMs:golang-github-hebcal-devel
Size:105.01 KiB

Package: golang-github-hebcal-greg-1.0.0-1.fc39
Summary: Converts between Gregorian dates and R.D. (Rata Die) day numbers
RPMs:golang-github-hebcal-greg-devel
Size:17.75 KiB

Package: golang-github-hebcal-hdate-1.0.2-1.fc39
Summary: Converts between Hebrew and Gregorian dates
RPMs:golang-github-hebcal-hdate-devel
Size:25.58 KiB

Package: libicu72-72.1-1.fc39
Summary: International Components for Unicode
RPMs:libicu72
Size:52.11 MiB

Package: python-nihtest-1.1.1-1.fc39
Summary: A testing tool for command line utilities
RPMs:python3-nihtest
Size:62.96 KiB

Package: rust-pyo3-build-config0.18-0.18.3-2.fc39
Summary: Build configuration for the PyO3 ecosystem
RPMs:rust-pyo3-build-config0.18+abi3-devel 
rust-pyo3-build-config0.18+abi3-py310-devel 
rust-pyo3-build-config0.18+abi3-py311-devel 
rust-pyo3-build-config0.18+abi3-py37-devel 
rust-pyo3-build-config0.18+abi3-py38-devel 
rust-pyo3-build-config0.18+abi3-py39-devel 
rust-pyo3-build-config0.18+default-devel 
rust-pyo3-build-config0.18+extension-module-devel 
rust-pyo3-build-config0.18+resolve-config-devel rust-pyo3-build-config0.18-devel
Size:100.80 KiB

Package: rust-pyo3-ffi0.18-0.18.3-1.fc39
Summary: Python-API bindings for the PyO3 ecosystem
RPMs:rust-pyo3-ffi0.18+abi3-devel rust-pyo3-ffi0.18+abi3-py310-devel 
rust-pyo3-ffi0.18+abi3-py311-devel rust-pyo3-ffi0.18+abi3-py37-devel 
rust-pyo3-ffi0.18+abi3-py38-devel rust-pyo3-ffi0.18+abi3-py39-devel 
rust-pyo3-ffi0.18+default-devel rust-pyo3-ffi0.18+extension-module-devel 
rust-pyo3-ffi0.18-devel
Size:143.50 KiB

Package: rust-pyo3-macros-backend0.18-0.18.3-2.fc39
Summary: Code generation for PyO3 package
RPMs:rust-pyo3-macros-backend0.18+abi3-devel 
rust-pyo3-macros-backend0.18+default-devel rust-pyo3-macros-backend0.18-devel
Size:65.85 KiB

Package: rust-pyo3-macros0.18-0.18.3-1.fc39
Summary: Proc macros for PyO3 package
RPMs:rust-pyo3-macros0.18+abi3-devel rust-pyo3-macros0.18+default-devel 
rust-pyo3-macros0.18+multiple-pymethods-devel rust-pyo3-macros0.18-devel
Size:36.49 KiB

Package: rust-pyo3_0.18-0.18.3-1.fc39
Summary: Bindings to Python interpreter
RPMs:rust-pyo3_0.18+abi3-devel rust-pyo3_0.18+abi3-py310-devel 
rust-pyo3_0.18+abi3-py311-devel rust-pyo3_0.18+abi3-py37-devel 
rust-pyo3_0.18+abi3-py38-devel rust-pyo3_0.18+abi3-py39-devel 
rust-pyo3_0.18+anyhow-devel rust-pyo3_0.18+auto-initialize-devel 
rust-pyo3_0.18+chrono-devel rust-pyo3_0.18+default-devel 
rust-pyo3_0.18+experimental-inspect-devel rust-pyo3_0.18+extension-module-devel 
rust-pyo3_0.18+eyre-devel rust-pyo3_0.18+full-devel 
rust-pyo3_0.18+hashbrown-devel rust-pyo3_0.18+indexmap-devel 
rust-pyo3_0.18+indoc-devel rust-pyo3_0.18+inventory-devel 
rust-pyo3_0.18+macros-devel rust-pyo3_0.18+multiple-pymethods-devel 
rust-pyo3_0.18+nightly-devel rust-pyo3_0.18+num-bigint-devel 
rust-pyo3_0.18+num-complex-devel rust-pyo3_0.18+pyo3-macros-devel 
rust-pyo3_0.18+serde-devel rust-pyo3_0.18+unindent-devel rust-pyo3_0.18-devel
Size:583.49 KiB

Package: tlmi-auth-1.0.1-1.fc39
Summary: Utility function for certificate based authentication on Lenovo 
platforms
RPMs:tlmi-auth
Size:102.15 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  389-ds-base-2.4.2-2.fc39
Old package:  389-ds-base-2.4.2-1.fc39
Summary:  389 Directory Server (base)
RPMs: 389-ds-base 389-ds-base-devel 389-ds-base-libs 389-ds-base-snmp 
cockpit-389-ds python3-lib389
Size: 21.37 MiB
Size change:  -619 B
Changelog:
  * Mon Jul 10 2023 Mark Reynolds  - 2.4.2-2
  - Bump version to 2.4.2-2
  - Issue 5752 - RFE - Provide a history for LastLoginTime (#5807)
  = Issue 4719 - CI - Add dsconf add a PTA URL test


Package

Re: F39 Change Proposal: Build Fedora Workstation live ISO with Image Builder (System-Wide)

2023-07-11 Thread Ondřej Budai

On Wed, Jun 28, 2023 at 2:53 PM Neal Gompa  wrote:

> On Wed, Jun 28, 2023 at 8:25 AM Ondřej Budai  wrote:
> >
> > Yep, that's a shortcoming of how we currently upload the builds to koji.
> It's something we would like to tackle in the upcoming quarter, see the
> tracking ticket: https://issues.redhat.com/browse/COMPOSER-1801 (public
> link).
> >
>
> I can't comment on that ticket. :(
>
>
FTR, this is now fixed! :) A permission issue on our side.

Ondřej
___
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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]

2023-07-11 Thread Kevin Kofler via devel

Oracle has (finally – the community projects Rocky and Alma were much 
quicker to react) made an announcement about the situation:
https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/

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: Several questionable packages installed on fresh system

2023-07-11 Thread Miro Hrončok


On 11. 07. 23 12:39, Miro Hrončok wrote:

On 10. 07. 23 10:38, Vít Ondruch wrote:

Hi,

I have recently installed Fedora Rawhide via netinstall and there are some 
questionable packages installed by default, such as:


...
libxcrypt-compat
...

and I wonder what is the mechanism, which pulls these in?


$ rpm -q --recommends python-pip-wheel
(libcrypt.so.1 if python3(x86-32))
(libcrypt.so.1()(64bit) if python3(x86-64))

The comment in spec:

# Some manylinux1 wheels need libcrypt.so.1.
# Manylinux1, a common (as of 2019) platform tag for binary wheels, relies
# on a glibc version that included ancient crypto functions, which were
# moved to libxcrypt and then removed in:
# 
https://fedoraproject.org/wiki/Changes/FullyRemoveDeprecatedAndUnsafeFunctionsFromLibcrypt

# The manylinux1 standard assumed glibc would keep ABI compatibility,
# but that's only the case if libcrypt.so.1 (libxcrypt-compat) is around.
# This should be solved in the next manylinux standard (but it may be
# a long time until manylinux1 is phased out).
# See: https://github.com/pypa/manylinux/issues/305
# Note that manylinux is only applicable to x86 (both 32 and 64 bits)

I wonder if manylinux1 is still applicable to Python 3.12. Will check.


https://discuss.python.org/t/is-it-safe-to-assume-that-manylinux1-and-python-3-12-will-never-be-combined/29455


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

Re: Several questionable packages installed on fresh system

2023-07-11 Thread Miro Hrončok


On 10. 07. 23 10:38, Vít Ondruch wrote:

Hi,

I have recently installed Fedora Rawhide via netinstall and there are some 
questionable packages installed by default, such as:


...
libxcrypt-compat
...

and I wonder what is the mechanism, which pulls these in?


$ rpm -q --recommends python-pip-wheel
(libcrypt.so.1 if python3(x86-32))
(libcrypt.so.1()(64bit) if python3(x86-64))

The comment in spec:

# Some manylinux1 wheels need libcrypt.so.1.
# Manylinux1, a common (as of 2019) platform tag for binary wheels, relies
# on a glibc version that included ancient crypto functions, which were
# moved to libxcrypt and then removed in:
# 
https://fedoraproject.org/wiki/Changes/FullyRemoveDeprecatedAndUnsafeFunctionsFromLibcrypt

# The manylinux1 standard assumed glibc would keep ABI compatibility,
# but that's only the case if libcrypt.so.1 (libxcrypt-compat) is around.
# This should be solved in the next manylinux standard (but it may be
# a long time until manylinux1 is phased out).
# See: https://github.com/pypa/manylinux/issues/305
# Note that manylinux is only applicable to x86 (both 32 and 64 bits)

I wonder if manylinux1 is still applicable to Python 3.12. Will check.

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

Immutable Variants & Persistence

Hello,

During a recent IRC conversation the question of always booting Fedora
fresh on hardware came up. We've got the Live variants which do this
already and it's possible to directly write them to a local disk. Similar
to booting from a USB stick, you could use the local hardware instead.
However, it's not really a read-only boot. Booting from a locally copied
Live environment still allows full access.

Is there a way to configure the immutable versions to have a similar RAM
only overlay?

I'd imagine an immutable base that is automatically updated and has all
other runtime changes discarded on reboot. There could be an automatically
logged in user that has extremely limited privileges and can only work in
the current boot userspace.

Previously this has been discussed as something like a kiosk mode, but I
could see this used in many other situations.

Thanks for any consideration,

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

Orphaned python-guizero

2023-07-11 Thread Miro Hrončok


Hey,

I've just orphaned python-guizero. it used to be a dependency of mu, but at 
least since Fedora 37 it has not been.


The package fails to build with Python 3.12 and hence fails to install.

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

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

Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

2023-07-11 Thread Eike Rathke

Hi,

On Thursday, 2023-07-06 17:10:24 +0100, Aoife Moloney wrote:

> https://discussion.fedoraproject.org/t/f40-change-request-privacy-preserving-telemetry-for-fedora-workstation-system-wide/85320

So this is how a bit harsher criticism on Discourse is handled? By
flagging and hiding?
https://discussion.fedoraproject.org/t/f40-change-request-privacy-preserving-telemetry-for-fedora-workstation-system-wide/85320/378

https://mastodon.ar.al/@aral/110688848596975566

Awesome.

  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


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

[rawhide] ICU upgrade to 73.2

Hi,

Later today, I'll be starting with rebuilds of packages depending on icu.
The rebuilds will take place in f39-build-side-69764 for all packages
returned by repoquery --whatrequires 'libicu*.so.72()(64bit)' (list cleaned
up, converted to source package names, attached at the end of the message).

Please, if you're going to make changes in affected packages before the
side tag gets merged, make the build in the said side tag. I expect to
merge the side tag asap with most of the affected packages built and then
continue building things that take longer to build (webkit/libreoffice)
later.

I am planning to merge the side tag twice, once before the bigger packages
are built (webkitgtk, and other "long to build" packages) to minimize time
in flight to reduce possible conflicts with work of other packagers.

For stuff that may fail to build, either due to newer icu or unrelated
issues, there is a libicu72 compat package already available in rawhide, so
that should take care of FTI issues that'd arise by merging the side tag.
I'll try to help the maintainers with fixing the issues.

I'll post updates to this thread as I progress with the bump.

Packages to be rebuilt (source names):
0ad
389-ds-base
bes
boost
brltty
calamares
calibre
ceph
cfdg
community-mysql
ctdb
cyrus-imapd
darktable
dee
deepin-editor
deepin-system-monitor
dino
dovecot
dovecot-fts-xapian
enchant2
evolution-data-server
freeciv
freerdp
geary
gnome-builder
gnome-text-editor
gnucash
gnustep-base
godot
godot
gspell
harfbuzz
ibus-qt
imv
kbibtex
kdb
kdeplasma-addons
konsole5
libcdr
libe-book
libical
libkiwix
liblcf
libmspub
libphonenumber
libqalculate
libqxp
libreoffice
libtoml
libtranslit
libvisio
libzim
libzmf
maim
mapnik
mongo-c-driver
mozjs102
mozjs91
msort
ncid
ncmpcpp
nuspell
opentrep
openttd
php
php-pecl-http
plasma-workspace
poedit
postfix
postgresql
prelude-lml
prosody
pyicu
python-mapnik
qt5-qtbase
qt5-qtlocation
qt5-qtwebengine
qt5-qtwebkit
qt6-qt5compat
qt6-qtbase
qt6-qtwebengine
R
R-Cairo
R-stringi
raptor2
rpminspect
samba
scribus
seamonkey
slop
strawberry
sword
tarantool
tepl
tesseract
texlive-base
tin
tracker
tracker-miners
unar
v8-314
vte291
webkitgtk
widelands
xalan-c
xfsprogs
xiphos
yaz
yaz
znc

-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
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 2219122] perl-Statistics-Descriptive-3.0801 is available

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 CC|iarn...@gmail.com,  |
   |jakub.jedel...@gmail.com,   |
   |jples...@redhat.com |
 Status|NEW |ASSIGNED




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

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-perlfaq-5.20230701-1.f
   ||c39
 Status|MODIFIED|CLOSED
Last Closed||2023-07-11 06:45:55



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-daae6761d2 has been pushed to the Fedora 39 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=2219017

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

[Bug 2219017] perl-perlfaq-5.20230701 is available