Re: fkinit -u instructions

2023-02-14 Thread Petr Pisar
V Tue, Feb 14, 2023 at 04:35:22PM +, Kenneth Goldman napsal(a):
> An explanation of the Kerberos ticket - why it's needed,

It's written there: "Koji uses Kerberos for authentication".

> how long it lasts, what fails when it expires, etc. - would be useful.
> 
These details are in a linked "See Infrastructure/Kerberos" document.

-- Petr


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


MDAPI Rewrite - Out Now in Production

2023-02-14 Thread Akashdeep Dhar
Hello everyone,

I hope you are doing well.

I wanted to let you know that the rewritten MDAPI is out now in production.

You can find the production deployment here[1].

The announcement of the testing deployment made on the staging environment
was made previously[2][3].

Please reach out to the project repository[4] for more information, filing
issue tickets and contributing.

Index

   1. https://mdapi.fedoraproject.org/
   2.
   
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KAZOUBVPGV62UKESGNKOTWW554QDEX4Q/
   3.
   
https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/message/KAZOUBVPGV62UKESGNKOTWW554QDEX4Q/
   4. https://github.com/fedora-infra/mdapi


Regards,
Akashdeep Dhar (he/him),
Objective Representative, Fedora Council
Red Hat Community Platform Engineering
t0xic0...@fedoraproject.org
akashd...@redhat.com
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[Bug 2158089] Add perl-Locale-Codes to EPEL9

2023-02-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2158089

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Locale-Codes-3.72-3.el
   ||9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2023-02-15 02:16:31



--- Comment #6 from Fedora Update System  ---
FEDORA-EPEL-2023-83be207a49 has been pushed to the Fedora EPEL 9 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=2158089
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


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

2023-02-14 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-855ba97187   
shapelib-1.3.0-3.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8535da02dc   
radare2-5.8.2-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0b707dda92   
chromium-110.0.5481.77-1.el7


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

apptainer-1.1.6-1.el7

Details about builds:



 apptainer-1.1.6-1.el7 (FEDORA-EPEL-2023-1eae057392)
 Application and environment virtualization formerly known as Singularity

Update Information:

Update to upstream 1.1.6

ChangeLog:

* Tue Feb 14 2023 Dave Dykstra  - 1.1.6-1
- Update to upstream 1.1.6.

References:

  [ 1 ] Bug #2161895 - apptainer does not declare bundled dependencies
https://bugzilla.redhat.com/show_bug.cgi?id=2161895
  [ 2 ] Bug #2161899 - apptainer: vulnerable to CVE-2022-23538
https://bugzilla.redhat.com/show_bug.cgi?id=2161899


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


[Bug 2125015] perl-Gtk3 EPEL9

2023-02-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2023-c75f9ec210 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c75f9ec210

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


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


Re: Fedora Linux 38 blocker status summary

2023-02-14 Thread Kevin Kofler via devel
Adam Williamson wrote:

> On Tue, 2023-02-14 at 16:44 +0100, Kevin Kofler via devel wrote:
>> Peter Robinson wrote:
>> > It was decided years ago that all desktops would have some Fedora
>> > similarities, backgrounds, browser etc.
>> 
>> If and when that was decided, that was without involving the maintainers
>> of the Spins. I know because I was directly involved with maintaining the
>> KDE Spin at the time.
> 
> It was decided by the KDE SIG in 2015:
> https://lists.fedoraproject.org/pipermail/kde/2015-August/015363.html

Well, as you point out yourself:

> For the record, I think Peter was mistaken in saying this was about "It
> was decided years ago that all desktops would have some Fedora
> similarities, backgrounds, browser etc." AFAICT this simply seems to
> have been a choice the KDE SIG decided to make on its own initiative.

what was decided back then was NOT that "all desktops would have some Fedora
similarities, backgrounds, browser etc.", but that AT THAT TIME (which was 
BEFORE QtWebEngine entered Fedora! The strict bundling rules that prevented 
it from passing review were loosened only a few months later), the KDE Spin 
would ship with Firefox. That is different because that decision was not a 
categorical decision that the KDE Spin, or even ALL Spins, would always ship 
Firefox (which is something at least the KDE SIG had never agreed to), but a 
momentaneous decision for Fedora 23 that could be revisited later.

In fact, there was a later vote for Fedora 25:
https://meetbot-raw.fedoraproject.org/fedora-meeting/2016-08-09/kde-sig.2016-08-09-15.05.log.html
which proposed switching to QupZilla/Falkon, vote which turned out much 
closer than the 2015 vote where KWebKitPart had started to age and there had 
been no viable alternative in Fedora other than Firefox.

In discussions after that vote, I was told that the decision could be 
reconsidered again under some conditions, but unfortunately, said conditions 
kept changing. As had been the case already in the time leading to the 2016 
vote. For F24, first the excuse was that QupZilla was not packaged, then 
that it was version 1.9.99 and not 2.0.0, then that it was too late in the 
release cycle (but the switch to Firefox for F23 had happened *during Final 
Freeze*!). But I had expected it to be pretty much a given that we would 
switch to QupZilla for F25, also based on the discussions immediately prior 
to the 2016 vote, and then it surprisingly still did not get a majority, and 
there were again new excuses being brought up. And that continued again and 
again.

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: fedpkg: Failed to get repository name from Git url or pushurl

2023-02-14 Thread Artur Frenszek-Iwicki
> Is there another argument to fedpkg?
fedpkg has a --name argument, you can try using that.

Alternatively, if you're just taking your first steps with packaging, you can 
try:
$ rpmbuild -bs path/to/your.spec
$ mock path/to/file-created-by-previous-command.srpm

This will first build an SRPM ("source rpm"), and then build it in mock,
which is pretty much exactly what "fedpkg mockbuild" does.

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


Fedora 38 compose report: 20230214.n.1 changes

2023-02-14 Thread Fedora Rawhide Report
OLD: Fedora-38-20230213.n.1
NEW: Fedora-38-20230214.n.1

= SUMMARY =
Added images:4
Dropped images:  7
Added packages:  4
Dropped packages:0
Upgraded packages:   52
Downgraded packages: 0

Size of added packages:  26.83 MiB
Size of dropped packages:0 B
Size of upgraded packages:   2.38 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-38-20230214.n.1.ppc64le.raw.xz
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-38-20230214.n.1.ppc64le.qcow2
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230214.n.1.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-38-20230214.n.1.iso

= DROPPED IMAGES =
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-38-20230213.n.1.aarch64.raw.xz
Image: Cloud_Base qcow2 s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-38-20230213.n.1.s390x.qcow2
Image: Server_KVM qcow2 ppc64le
Path: Server/ppc64le/images/Fedora-Server-KVM-38-20230213.n.1.ppc64le.qcow2
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-38-20230213.n.1.iso
Image: LXQt raw-xz aarch64
Path: Spins/aarch64/images/Fedora-LXQt-38-20230213.n.1.aarch64.raw.xz
Image: Cloud_Base raw-xz s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-38-20230213.n.1.s390x.raw.xz
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-38-20230213.n.1.iso

= ADDED PACKAGES =
Package: bitstower-markets-0.5.4-1.fc38
Summary: A stock and currency tracker
RPMs:bitstower-markets
Size:389.10 KiB

Package: f38-backgrounds-38.0.0-2.fc38
Summary: Fedora 38 default desktop background
RPMs:f38-backgrounds f38-backgrounds-base f38-backgrounds-extras-base 
f38-backgrounds-extras-gnome f38-backgrounds-extras-kde 
f38-backgrounds-extras-mate f38-backgrounds-extras-xfce f38-backgrounds-gnome 
f38-backgrounds-kde f38-backgrounds-mate f38-backgrounds-xfce
Size:26.31 MiB

Package: python-result-0.9.0-2.fc38
Summary: A Rust-like result type for Python
RPMs:python3-result
Size:20.58 KiB

Package: whatip-1.1-1.fc38
Summary: Info on your IP address
RPMs:whatip
Size:128.75 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  OpenImageIO-2.4.8.1-1.fc38
Old package:  OpenImageIO-2.4.8.0-1.fc38
Summary:  Library for reading and writing images
RPMs: OpenImageIO OpenImageIO-devel OpenImageIO-iv OpenImageIO-utils 
python3-openimageio
Size: 21.47 MiB
Size change:  -13.43 KiB
Changelog:
  * Tue Feb 14 2023 Richard Shaw  - 2.4.8.1-1
  - Update to 2.4.8.1.


Package:  R-igraph-1.4.0-1.fc38
Old package:  R-igraph-1.3.5-3.fc38
Summary:  Network Analysis and Visualization
RPMs: R-igraph
Size: 18.05 MiB
Size change:  2.00 MiB
Changelog:
  * Mon Feb 13 2023 Tom Callaway  - 1.4.0-1
  - update to 1.4.0
  - disable tests until R-vdiffr makes it into Fedora (if ever)


Package:  azote-1.9.7-3.fc38
Old package:  azote-1.9.7-2.fc38
Summary:  Wallpaper and color manager for Sway, i3 and some other WMs
RPMs: azote
Size: 4.44 MiB
Size change:  107 B
Changelog:
  * Mon Feb 13 2023 Bob Hepple  - 1.9.7-3
  - added azote.svg to /usr/share/pixmaps RHBZ#2169207


Package:  azure-cli-2.45.0-2.fc38
Old package:  azure-cli-2.45.0-1.fc38
Summary:  Microsoft Azure Command-Line Tools
RPMs: azure-cli python3-azure-cli-core python3-azure-cli-telemetry 
python3-azure-cli-testsdk
Size: 8.52 MiB
Size change:  -555 B
Changelog:
  * Tue Feb 14 2023 Major Hayden  - 2.45.0-2
  - Allow newer version of packaging


Package:  blender-1:3.4.1-11.fc38
Old package:  blender-1:3.4.1-8.fc38
Summary:  3D modeling, animation, rendering and post-production
RPMs: blender blender-rpm-macros
Size: 200.64 MiB
Size change:  -3.86 KiB
Changelog:
  * Sat Feb 11 2023 Luya Tshimbalanga  - 1:3.4.1-9
  - Rebuild for embree-4.0.0

  * Sun Feb 12 2023 Luya Tshimbalanga  - 1:3.4.1-10
  - Port to embree4

  * Sun Feb 12 2023 Luya Tshimbalanga  - 1:3.4.1-11
  - Further port to embree4


Package:  buildah-1.29.0-2.fc38
Old package:  buildah-1.29.0-1.fc38
Summary:  A command line tool used for creating OCI Images
RPMs: buildah buildah-tests
Size: 135.79 MiB
Size change:  31.09 KiB
Changelog:
  * Thu Feb 09 2023 Lokesh Mandvekar  - 1.29.0-2
  - exclusivearch: golang_arches_future


Package:  check-0.15.2-9.fc38
Old package:  check-0.15.2-8.fc38
Summary:  A unit test framework for C
RPMs: check check-checkmk check-devel check-static mingw32-check 
mingw64-check
Added RPMs:   mingw32-check mingw64-check
Size: 1.11 MiB
Size change:  233.83 KiB
Changelog:
  * Mon Feb 13 2023 Marc-Andr?? Lureau

Re: Enabling plymouth on livemedia-creator iso creation

2023-02-14 Thread Neal Gompa
On Tue, Feb 14, 2023 at 5:19 PM Brian C. Lane  wrote:
>
> Way back in the day... :) livemedia-creator inherited an '--omit
> plymouth' from the boot.iso creation process. The boot.iso was changed a
> few years later, but lmc kept it. Fred noticed this and submitted
> https://github.com/weldr/lorax/pull/1307 to conditionally fix it.
>
> But I think we can just remove it. This has been working fine for the
> boot.iso and in my testing here with a BIOS and UEFI VM it works fine
> when you drop it from lmc's dracut configuration as well.
>
> So, are there any objections to
> https://github.com/weldr/lorax/pull/1308 for rawhide at least? I'm not
> sure if we want to change it for F38 at this point or not (less change
> is better).
>

Oh we should pull this also into F38. I had been trying to figure out
why it was like this forever to fix it. :)



-- 
真実はいつも一つ!/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Enabling plymouth on livemedia-creator iso creation

2023-02-14 Thread Kevin Fenzi
On Tue, Feb 14, 2023 at 02:19:15PM -0800, Brian C. Lane wrote:
> Way back in the day... :) livemedia-creator inherited an '--omit
> plymouth' from the boot.iso creation process. The boot.iso was changed a
> few years later, but lmc kept it. Fred noticed this and submitted
> https://github.com/weldr/lorax/pull/1307 to conditionally fix it.
> 
> But I think we can just remove it. This has been working fine for the
> boot.iso and in my testing here with a BIOS and UEFI VM it works fine
> when you drop it from lmc's dracut configuration as well.
> 
> So, are there any objections to
> https://github.com/weldr/lorax/pull/1308 for rawhide at least? I'm not
> sure if we want to change it for F38 at this point or not (less change
> is better).

Seems fine to me. If you are gonna do it for f38, I would do it very
soon so there's time before freeze to revert if anything happens...

kevin


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


Enabling plymouth on livemedia-creator iso creation

2023-02-14 Thread Brian C. Lane
Way back in the day... :) livemedia-creator inherited an '--omit
plymouth' from the boot.iso creation process. The boot.iso was changed a
few years later, but lmc kept it. Fred noticed this and submitted
https://github.com/weldr/lorax/pull/1307 to conditionally fix it.

But I think we can just remove it. This has been working fine for the
boot.iso and in my testing here with a BIOS and UEFI VM it works fine
when you drop it from lmc's dracut configuration as well.

So, are there any objections to
https://github.com/weldr/lorax/pull/1308 for rawhide at least? I'm not
sure if we want to change it for F38 at this point or not (less change
is better).

Brian

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


F38 Change complete (100% complete) deadline in one week

2023-02-14 Thread Ben Cotton
As a reminder, F38 Changes should be 100% complete by Tuesday 21
February. Change owners can indicate this by setting the Bugzilla
tracker to the ON_QA state. F38 will enter beta freeze on that date.

More schedule details are available at
https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


F38 Change complete (100% complete) deadline in one week

2023-02-14 Thread Ben Cotton
As a reminder, F38 Changes should be 100% complete by Tuesday 21
February. Change owners can indicate this by setting the Bugzilla
tracker to the ON_QA state. F38 will enter beta freeze on that date.

More schedule details are available at
https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Small rant: installer environment size

2023-02-14 Thread Brian C. Lane
On Tue, Feb 14, 2023 at 06:40:05PM +0100, Florian Weimer wrote:
> 
> I'm still curious about the impact of glibc-all-langpacks on
> download/image size.

FWIW here is the discussion that happened when that was added:
https://bugzilla.redhat.com/show_bug.cgi?id=1312607

Brian

-- 
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
___
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: TSS maintainer volunteer

2023-02-14 Thread Kenneth Goldman


From: Peter Robinson 
Sent: Monday, February 13, 2023 4:57 PM
To: Development discussions related to Fedora 
Subject: [EXTERNAL] Re: TSS maintainer volunteer
jQcmQRYFpfptBannerEnd

On Mon, Feb 13, 2023 at 9:16 PM Kenneth Goldman  
wrote:
I have a fedora account.

How do I get packager status?  How do I work with a packager - is that a 
person or a program?

A quick google gave me this link: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Joining-5Fthe-5FPackage-5FMaintainers_=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=s70Bz9k22m9018JPgVNOAnmz7DqkzTJI_QXmAfcI-pzZbLnQwyYpgp0rgTxhQ1Hg=3fAYyQr_EQBDWPP3121TuoPS_dDADrPuxuTVcuf5W88=

I found that and followed all the steps.  However, it ends at Finding software 
you wish to maintain for Fedora".

What's next?


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


fedpkg: Failed to get repository name from Git url or pushurl

2023-02-14 Thread Kenneth Goldman
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/

Working through the basic tutorial there:

fedpkg --release f37 mockbuild

fails with

Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl
[repeats forever]

How does fedpkg know what to build?  Does it default to whatever .spec file
exists?
Is there another argument to fedpkg. Are there some other steps between
Rpmdev-newspec and fedpkg?

What am I missing?


--
Work 1-914-945-2415



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


Re: libindi upgrade to 2.0.0 and soname bump

2023-02-14 Thread Marc Deop i Argemí
On Tuesday, 14 February 2023 19:13:39 CET Mattia Verga wrote:
> To the kstars maintainers: I can take care to upgrade the package, if
> you want (it's just a simple version bump and upload new sources).
> 
> To the stellarium maintainers: I will wait for a patch from upstream
> before pushing the side-tag (I hope before it expires).
> 
> To both kstars and stellarium maintainers: if possible, I'd like the
> upgrades to land in f38 also, let me know.

No complains from me, you are taking care of everything :-)

Best regards,

Marc


___
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: fkinit -u instructions

2023-02-14 Thread Ewoud Kohl van Wijngaarden

On Tue, Feb 14, 2023 at 06:10:39PM +, Kenneth Goldman wrote:

-Original Message-
From: Clemens Lang 
Sent: Tuesday, February 14, 2023 12:59 PM
To: Development discussions related to Fedora



>> Someone posted that the prompt for an OTP can be ignored and that the
>> Fedora password is enough.
>
> IIRC, if you *have* an OTP, you have to include it. If you *don't*
> have one, of course you just put your password. We should make this
> clear too (assuming I'm right).

You are right, but fkinit will tell you, so I don’t think we need to clarify 
this in
the documentation:


:) cllang@frootmig:~$ fkinit -u clang
Enter your password and OTP concatenated. (Ignore that the prompt is for
only the token) Enter OTP Token Value:
:) cllang@frootmig:~$


For a newbie (me), it's not clear what the OTP is.  Is it something from here?


Perhaps it should spell out One Time Password. Just as 2FA should 
probably be written as two-factor authentication.



https://accounts.fedoraproject.org/user/kgold/settings/otp/

If correct, might a link be useful, along with some guidance on then to use it?


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


Re: libindi upgrade to 2.0.0 and soname bump

2023-02-14 Thread Mattia Verga via devel
Il 04/02/23 18:41, Mattia Verga ha scritto:
> Hello folks,
>
> in a week or so (after f38 branch) I plan to upgrade libindi core (AKA
> indilib), indi-3rdparty-libraries and indi-3rdparty-drivers to 2.0.0.
> This will make the soname bump to 2 and will need the two dependent
> packages, kstars and stellarium, to be upgraded to be compatible with it.
>
> At a first glance, kstars should already be compatible with INDI2 by
> upgrading to 3.6.3, at least. Stellarium, however, doesn't seem to have
> been fixed yet.
>
> I will announce here the side-tag used for INDI2. Meanwhile, I've set up
> a COPR repository at [1] to play with kstars and stellarium build
> failures. As my time permits, I'll try to build there kstars 3.6.3 and
> I'll get in touch with upstream stellarium to try to find a quick fix
> for that.
>
> Have a nice weekend
> Mattia
>
> [1] https://copr.fedorainfracloud.org/coprs/mattia/INDI2-test/
>
>
So, I've built libindi 2.0.0 under f39-build-side-63222.

I'm building indi-3rdparty-libraries and indi-3rdparty-drivers 2.0.0 now
and I'll take care of building phd2 from the latest git snapshot which
was fixed to be compatible with libindi 2.0.0.

The remaining software that need to be rebuild are:

- kstars (needs to be upgraded to 3.6.3, I've verified in COPR that the
new version fixes compatibility with libindi 2)
- stellarium (we need to wait for a fix from upstream, see
https://github.com/Stellarium/stellarium/issues/3038 )

To the kstars maintainers: I can take care to upgrade the package, if
you want (it's just a simple version bump and upload new sources).

To the stellarium maintainers: I will wait for a patch from upstream
before pushing the side-tag (I hope before it expires).

To both kstars and stellarium maintainers: if possible, I'd like the
upgrades to land in f38 also, let me know.

Mattia

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


RE: fkinit -u instructions

2023-02-14 Thread Kenneth Goldman
> -Original Message-
> From: Clemens Lang 
> Sent: Tuesday, February 14, 2023 12:59 PM
> To: Development discussions related to Fedora

> >> Someone posted that the prompt for an OTP can be ignored and that the
> >> Fedora password is enough.
> >
> > IIRC, if you *have* an OTP, you have to include it. If you *don't*
> > have one, of course you just put your password. We should make this
> > clear too (assuming I'm right).
> 
> You are right, but fkinit will tell you, so I don’t think we need to clarify 
> this in
> the documentation:
> 
> 
> :) cllang@frootmig:~$ fkinit -u clang
> Enter your password and OTP concatenated. (Ignore that the prompt is for
> only the token) Enter OTP Token Value:
> :) cllang@frootmig:~$

For a newbie (me), it's not clear what the OTP is.  Is it something from here?

https://accounts.fedoraproject.org/user/kgold/settings/otp/

If correct, might a link be useful, along with some guidance on then to use it?



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


Re: fkinit -u instructions

2023-02-14 Thread Clemens Lang

Hi Adam,


Adam Williamson  wrote:


On Tue, 2023-02-14 at 16:35 +, Kenneth Goldman wrote:

Yes, much better, thanks.

Someone posted that the prompt for an OTP can be ignored and that the  
Fedora

password is enough.


IIRC, if you *have* an OTP, you have to include it. If you *don't* have
one, of course you just put your password. We should make this clear
too (assuming I'm right).


You are right, but fkinit will tell you, so I don’t think we need to clarify
this in the documentation:


:) cllang@frootmig:~$ fkinit -u clang
Enter your password and OTP concatenated. (Ignore that the prompt is for  
only the token)

Enter OTP Token Value:
:) cllang@frootmig:~$


HTH,
Clemens


--
Clemens Lang
RHEL Crypto Team
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: fkinit -u instructions

2023-02-14 Thread Adam Williamson
On Tue, 2023-02-14 at 16:35 +, Kenneth Goldman wrote:
> Yes, much better, thanks.
> 
> Someone posted that the prompt for an OTP can be ignored and that the Fedora 
> password is enough.

IIRC, if you *have* an OTP, you have to include it. If you *don't* have
one, of course you just put your password. We should make this clear
too (assuming I'm right).
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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


Re: Fedora Linux 38 blocker status summary

2023-02-14 Thread Adam Williamson
On Tue, 2023-02-14 at 16:44 +0100, Kevin Kofler via devel wrote:
> Peter Robinson wrote:
> > It was decided years ago that all desktops would have some Fedora
> > similarities, backgrounds, browser etc.
> 
> If and when that was decided, that was without involving the maintainers of 
> the Spins. I know because I was directly involved with maintaining the KDE 
> Spin at the time.

It was decided by the KDE SIG in 2015:
https://lists.fedoraproject.org/pipermail/kde/2015-August/015363.html
There is a reference to it being "Based on our prior kde-sig meeting",
which I believe refers to this meeting:
https://meetbot-raw.fedoraproject.org/teams/kde-sig/kde-sig.2015-08-04-15.08.log.txt
you participated extensively in both the meeting and the mailing list
thread, strongly opposing the change, but you were outvoted, and the
proposal passed, per:
https://lists.fedoraproject.org/pipermail/kde/2015-August/015521.html
it certainly wasn't decided "without involving the maintainers of the
Spins".

For the record, I think Peter was mistaken in saying this was about "It
was decided years ago that all desktops would have some Fedora
similarities, backgrounds, browser etc." AFAICT this simply seems to
have been a choice the KDE SIG decided to make on its own initiative.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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


Re: Small rant: installer environment size

2023-02-14 Thread Florian Weimer
* Adam Williamson:

> On Tue, 2023-02-14 at 09:40 +0100, Florian Weimer wrote:
>> * Adam Williamson:
>> 
>> > On Thu, 2022-12-08 at 07:57 +0100, Florian Weimer wrote:
>> > > * Adam Williamson:
>> > > 
>> > > > 1. /usr/lib/locale/locale-archive , from glibc-all-langpacks - this is
>> > > > 224M uncompressed. A quick test just compressing the file with xz on my
>> > > > system shows it compresses to around 11M, though, so that's probably
>> > > > all it adds up to after compression (the image is an xz-compressed
>> > > > squashfs)
>> > > 
>> > > Isn't the compression block-based?  I think it would be interesting to
>> > > measure the image size with the file removed.
>> > 
>> > I'll try it tomorrow, it's not too hard.
>> 
>> Have you posted the outcome of the experiment somewhere?
>
> Sorry, after we established I was wrong about the image being loaded
> into memory, this became less important so I don't think I went ahead
> with it. If you're still interested I can try and find a minute to do
> it this week, once we have Rawhide and F38 calmed down after
> branching...

I'm still curious about the impact of glibc-all-langpacks on
download/image size.

Thanks,
Florian
___
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: Small rant: installer environment size

2023-02-14 Thread Adam Williamson
On Tue, 2023-02-14 at 09:40 +0100, Florian Weimer wrote:
> * Adam Williamson:
> 
> > On Thu, 2022-12-08 at 07:57 +0100, Florian Weimer wrote:
> > > * Adam Williamson:
> > > 
> > > > 1. /usr/lib/locale/locale-archive , from glibc-all-langpacks - this is
> > > > 224M uncompressed. A quick test just compressing the file with xz on my
> > > > system shows it compresses to around 11M, though, so that's probably
> > > > all it adds up to after compression (the image is an xz-compressed
> > > > squashfs)
> > > 
> > > Isn't the compression block-based?  I think it would be interesting to
> > > measure the image size with the file removed.
> > 
> > I'll try it tomorrow, it's not too hard.
> 
> Have you posted the outcome of the experiment somewhere?

Sorry, after we established I was wrong about the image being loaded
into memory, this became less important so I don't think I went ahead
with it. If you're still interested I can try and find a minute to do
it this week, once we have Rawhide and F38 calmed down after
branching...
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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


RE: fkinit -u instructions

2023-02-14 Thread Kenneth Goldman
Yes, much better, thanks.

Someone posted that the prompt for an OTP can be ignored and that the Fedora 
password is enough.

An explanation of the Kerberos ticket - why it's needed, how long it lasts, 
what fails when it expires, etc. - would be useful.

> -Original Message-
> From: Petr Pisar 
> Sent: Tuesday, February 14, 2023 11:28 AM
> To: devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: fkinit -u instructions
>
> V Tue, Feb 14, 2023 at 04:04:06PM +0100, blinxen napsal(a):
> > > 1. fas_id is not defined.  Is it my local Linux user ID, my Fedora
> > > login
> > ID, or something else?
> >
> > "fas_id" is your FAS (Fedora Account) name, for me this would be 
> > "blinxen".
> >
> > > Is password my local or Fedora password?
> >
> > It is your FAS (Fedora Account) password
> >
> Does this make the documentation more understandable
> ?
>
> -- Petr


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


Re: Fedora Linux 38 blocker status summary

2023-02-14 Thread Marc Deop i Argemí
On Friday, 10 February 2023 15:11:19 CET Marc Deop i Argemí wrote:
> On Friday, 10 February 2023 14:47:19 CET Ben Cotton wrote:
> 
> > 3. kwin — kwin_wayland often crashed when used as the sddm Wayland
> > compositor and logging out of Plasma resulting in a black screen — NEW
> > ACTION: Maintainer to diagnose issue
> 
> 
> 
> Does it help if I build Plasma 5.27.0 on a F38 sidetag so we can investigate
>  if the issue persists?

Just for your information, I have built KDE Plasma 5.27.0 (which includes 
kwin) on sidetag f38-build-side-63172.

I am uncertain if I should trigger an update on F38 now.

Thoughts?

Best regards,

Marc Deop


___
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: fkinit -u instructions

2023-02-14 Thread Petr Pisar
V Tue, Feb 14, 2023 at 04:04:06PM +0100, blinxen napsal(a):
> > 1. fas_id is not defined.  Is it my local Linux user ID, my Fedora login
> ID, or something else?
> 
> "fas_id" is your FAS (Fedora Account) name, for me this would be "blinxen".
> 
> > Is password my local or Fedora password?
> 
> It is your FAS (Fedora Account) password
>
Does this make the documentation more understandable
?

-- Petr


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


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

2023-02-14 Thread tdawson
Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2023-02-15 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: Fedora Linux 38 blocker status summary

2023-02-14 Thread Kevin Kofler via devel
Michael Catanzaro wrote:
> As a browser maintainer itself, I'm very supportive of the Falkon
> project. I consider it to be KDE's equivalent of Epiphany, sort of a
> sister project, more or less.

Agreed. I also think that the "Workstation Edition" should be shipping 
Epiphany instead of Firefox (also the main thing that keeps it from being a 
true "GNOME Spin", though the naming is of course also marketing), but 
myself not using GNOME, I admittedly do not care as much about that than 
about Falkon which I maintain in Fedora and would really like to finally see 
as the default (and ideally only) browser on the KDE Spin.

> I looked into this a couple months ago and if I remember correctly,
> they *are* impressively backporting quite a few CVE fixes, but I don't
> think they are *comprehensively* doing so? My suspicion is that if a
> fix does not apply cleanly, or looks difficult, they probably move on
> to the next one? It's really hard just to determine whether a fix is
> still required. (Disclaimer: I'm not looking at the git repo right now
> or cross-referencing to a list of Chromium CVEs. May be wrong. Don't
> treat this as gospel.)

Well, one issue is that, as far as I can tell, Google does not always 
document which commit fixes a given CVE. For most CVEs, they do, but for 
some (maybe those discovered by Apple which is famously against any sort of 
responsible disclosure and in favor of strict "security by obscurity"?), 
there is an awful lack of details. So, obviously, it is hard to identify the 
fixes to backport in those cases.

But one thing to also keep in mind is that not all Chrome/Chromium CVEs also 
affect QtWebEngine. Some are in code that is only shipped in the Chrome 
and/or Chromium browser and not in derived browsers/libraries like 
QtWebEngine. So just comparing the lists of fixed CVEs also does not tell us 
the whole truth. It is not obvious how many CVEs should be fixed in 
QtWebEngine, but are not.

> Additionally, I don't know about Chromium, but in WebKit I recently
> estimated that only about 5% of issues flagged as fixing security
> vulnerabilities receive CVEs. (Maybe Chromium does better at this?) And
> it is impossible to know what percentage of security fixes get flagged
> as such, but my guess is that percentage is itself pretty low. I'd
> further guess that the situation with Chromium is similar. So even if
> you backport fixes for every single CVE, you will not be in good shape.

QtWebEngine also backports some security fixes with only a Chromium bug ID 
("security bug n"), but that is rather the exception. I obviously do 
not know how many security fixes remain undiscovered by the backporters.

> My conclusion was that QtWebEngine was that the Qt 5 version is too
> old. I think QtWebEngine should adopt the same strategy that WebKitGTK
> and Firefox ESR use: regularly rebase to latest upstream version.
> WebKitGTK does that twice per year. Firefox does it every 9 months.
> Backports are an appropriate way to fill the gap between rebases, but
> they are NOT a substitute for regular rebases.

Well, Qt does pretty much exactly that, *but* the problem is, Qt 5 is in LTS 
"very strict" mode by now, i.e., in maintenance mode. From the point of view 
of Qt, applications are not supposed to use it anymore. The Qt 6 QtWebEngine 
has been rebased several times since. The problem is that the KDE ecosystem 
cannot move on to Qt 6 as fast as Qt upstream would like it to. In part due 
to Qt itself (e.g., QtWebEngine was not included at all in 6.0 and 6.1!), in 
part due to the KDE Frameworks (which are being ported to Qt 6 right now, 
they were blocked due to the aforementioned missing features in Qt 6 
itself). So we are stuck on the legacy branch.

Maybe an unofficial backport of QtWebEngine 6.2 LTS, QtWebEngine 6.4, and/or 
the upcoming QtWebEngine 6.5 LTS to Qt 5 would help close the gap. But 
someone would have to do the work (and hope not to get sued by Qt over 
trademarks).

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


Re: Fedora Linux 38 blocker status summary

2023-02-14 Thread Kevin Kofler via devel
Peter Robinson wrote:
> It was decided years ago that all desktops would have some Fedora
> similarities, backgrounds, browser etc.

If and when that was decided, that was without involving the maintainers of 
the Spins. I know because I was directly involved with maintaining the KDE 
Spin at the time.

And it is already the case that some Spins use a non-Firefox default browser 
that fits better into that Spin's environment (and IMHO that is a good 
thing).

> But there's also 2 other web engines other than firefox and
> QtWebEngine (qt5-qtwebkit and webkit2gtk3)

I want those off the Spin as well. They should stay in the repos for the 
users who need applications using them, but qt5-qtwebkit is a legacy 
compatibility library that should not be installed by default on any Spin, 
and webkit2gtk3 is a GTK-based library that should not be installed by 
default on a Qt-based Spin.

> as well as a DB server

Blame Akonadi for that. It can theoretically work without MariaDB, but the 
performance of the SQLite backend is poor (due mainly to locking/concurrency 
issues inherent to file-based databases), so it is not recommended. I think 
the way Akonadi is designed is broken and needs to be fixed (and the above 
is one of the reasons), but KDE has been sticking to that design since 4.x 
days and is not interested in a major redesign.

Dropping Akonadi would probably be possible, but it would mean losing some 
Plasma features, and it is not clear what mail program would be shipped 
then. At least as long as Trojitá depends on the legacy QtWebKit, see above. 
Shipping Akonadi with SQLite could be a compromise, but that too would IMHO 
need at least a replacement for KMail (which is the most performance-
critical Akonadi user) to be viable. And that is just my view as a Trojitá 
user who heavily dislikes Akonadi due to past awful experiences with KMail. 
The current KDE SIG members will probably be even less interested than me in 
replacing or nerfing (by using SQLite instead of MariaDB) Akonadi.

> and the gcc toolchain

Huh? The KDE Spin now installs the GCC toolchain by default? Since when? It 
did not back when I helped maintain the Spin, nor more recently when I based 
the Kannolo Fedora Remix on it. Is that for akmod/DKMS/… kernel modules? KDE 
Plasma definitely does not (mandatorily) require a toolchain at runtime.

> which I would bet the average user either don't use
> or don't need to have installed from the outset.

For the database server, see above: users of Akonadi are using a per-user 
instance of it behind the scenes, often without knowing it. For the GCC 
toolchain, you may be right, though users of kernel modules from RPM Fusion 
are forced to use it these days because they (sadly) no longer ship binary 
kmod packages. (Even for blobs like the NVidia driver, the glue code is 
always recompiled from an akmod and no completely binary kmod is shipped.)

> I bet there's a lot of low hanging fruit that could slim down KDE
> rather than just moaning about Firefox which I suspect a lot more
> people use by default that a lot of the other components.

I agree that there are other components that should not be on the Spin (only 
in the repository), but the redundant browser as a leaf application surely 
is the lowest-hanging fruit.

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: fkinit -u instructions

2023-02-14 Thread blinxen

Hi Kenneth


> 1. fas_id is not defined.  Is it my local Linux user ID, my Fedora 
login ID, or something else?


"fas_id" is your FAS (Fedora Account) name, for me this would be "blinxen".

> Is password my local or Fedora password?

It is your FAS (Fedora Account) password

> What would my OTP be?

OTP is used for two-factor authentication. If you don't know what that 
is, then you can just ignore it.



I hope this helps.


Hussein

Am 14.02.23 um 15:56 schrieb Kenneth Goldman:

fkinit -u instructions

I'm working through the Packager instructions at

_https://docs.fedoraproject.org/en-US/package-maintainers/Installing_Packager_Tools/_

There is a step:

$ fkinit -u 

1. fas_id is not defined.  Is it my local Linux user ID, my Fedora 
login ID, or something else?


2. When I try it, I get

Enter your password and OTP concatenated. (Ignore that the prompt is 
for only the token)


Is password my local or Fedora password?

What would my OTP be?

--

Work 1-914-945-2415



___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-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: Fedora Linux 38 blocker status summary

2023-02-14 Thread Michael Catanzaro
As a browser maintainer itself, I'm very supportive of the Falkon 
project. I consider it to be KDE's equivalent of Epiphany, sort of a 
sister project, more or less.


On Tue, Feb 14 2023 at 03:44:06 AM +0100, Kevin Kofler via devel 
 wrote:
Even Qt 5 QtWebEngine (considered obsolete by Qt) still gets security 
fixes,
and they are published in git under the LGPL as soon as the 
commercial Qt
5.15.x LTS release is released. (In fact, they are pushed even 
earlier, as
soon as they are backported by Qt developers, and the branch is then 
tagged
when the commercial LTS is released. But the backports typically 
happen on
the Qt release schedule, meaning they are usually only done in git 
when a Qt

release is planned soon, not daily.)


I looked into this a couple months ago and if I remember correctly, 
they *are* impressively backporting quite a few CVE fixes, but I don't 
think they are *comprehensively* doing so? My suspicion is that if a 
fix does not apply cleanly, or looks difficult, they probably move on 
to the next one? It's really hard just to determine whether a fix is 
still required. (Disclaimer: I'm not looking at the git repo right now 
or cross-referencing to a list of Chromium CVEs. May be wrong. Don't 
treat this as gospel.)


Additionally, I don't know about Chromium, but in WebKit I recently 
estimated that only about 5% of issues flagged as fixing security 
vulnerabilities receive CVEs. (Maybe Chromium does better at this?) And 
it is impossible to know what percentage of security fixes get flagged 
as such, but my guess is that percentage is itself pretty low. I'd 
further guess that the situation with Chromium is similar. So even if 
you backport fixes for every single CVE, you will not be in good shape.


My conclusion was that QtWebEngine was that the Qt 5 version is too 
old. I think QtWebEngine should adopt the same strategy that WebKitGTK 
and Firefox ESR use: regularly rebase to latest upstream version. 
WebKitGTK does that twice per year. Firefox does it every 9 months. 
Backports are an appropriate way to fill the gap between rebases, but 
they are NOT a substitute for regular rebases.


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


fkinit -u instructions

2023-02-14 Thread Kenneth Goldman
I'm working through the Packager instructions at

https://docs.fedoraproject.org/en-US/package-maintainers/Installing_Packager
_Tools/

There is a step:

$ fkinit -u 

1.  fas_id is not defined.  Is it my local Linux user ID, my Fedora
login ID, or something else?
2.  When I try it, I get

Enter your password and OTP concatenated. (Ignore that the prompt is for
only the token)

Is password my local or Fedora password?
What would my OTP be?

--
Work 1-914-945-2415




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


Re: openexr: Any s390x people in the house?

2023-02-14 Thread Fabio Valentini
On Tue, Feb 14, 2023 at 3:08 PM Dan Horák  wrote:
>
> On Tue, 14 Feb 2023 07:19:38 -0600
> Richard Shaw  wrote:
>
> > I currently have to disable tests for s390x[1] (and ppc64le) for likely
> > endianess issues.
> >
> > Troubleshooting these is more than a little outside of my wheelhouse.
> >
> > I hate keeping them disabled so I wanted to see if anyone could spare a few
> > cycles to investigate.
>
> I will try to allocate some cycles for those

When I read "EXR" and "s390x" in the same sentence it rang a bell - we
currently disable support for the EXR image format in the "image" Rust
crate, because the "exr" [0] crate does not support big-endian
architectures, either (due to missing implementation of the "pxr24"
compression method on big-endian architectures). I don't know if it's
related to the problem in OpenEXR, but I thought it worth mentioning
in case it helps narrow down the problem.

Fabio

[0]: https://crates.io/crates/exr
___
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: openexr: Any s390x people in the house?

2023-02-14 Thread Dan Horák
On Tue, 14 Feb 2023 07:19:38 -0600
Richard Shaw  wrote:

> I currently have to disable tests for s390x[1] (and ppc64le) for likely
> endianess issues.
> 
> Troubleshooting these is more than a little outside of my wheelhouse.
> 
> I hate keeping them disabled so I wanted to see if anyone could spare a few
> cycles to investigate.

I will try to allocate some cycles for those


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


Today is the Fedora 38 "Retire FTI packages in NEW state" moment, but it's (close to) no-op

2023-02-14 Thread Miro Hrončok
The only packages that would be retired are orphaned for 5 weeks already and 
will be retired in (less than) a week. I decided not to bother with them 
individually and let them be retired naturally.


https://bugzilla.redhat.com/buglist.cgi?bug_id=2140817,2140818,2140819

--
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: openexr: Any s390x people in the house?

2023-02-14 Thread Stephen Smoogen
On Tue, 14 Feb 2023 at 08:21, Richard Shaw  wrote:

> I currently have to disable tests for s390x[1] (and ppc64le) for likely
> endianess issues.
>
>
Well if it is failing for the same reason on s390x (big endian) and ppc64le
(little endian).. I don't think the problem is all about endian parts.



> Troubleshooting these is more than a little outside of my wheelhouse.
>
> I hate keeping them disabled so I wanted to see if anyone could spare a
> few cycles to investigate.
>
> Thanks,
> Richard
>
> [1] https://github.com/AcademySoftwareFoundation/openexr/issues/1175
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


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


openexr: Any s390x people in the house?

2023-02-14 Thread Richard Shaw
I currently have to disable tests for s390x[1] (and ppc64le) for likely
endianess issues.

Troubleshooting these is more than a little outside of my wheelhouse.

I hate keeping them disabled so I wanted to see if anyone could spare a few
cycles to investigate.

Thanks,
Richard

[1] https://github.com/AcademySoftwareFoundation/openexr/issues/1175
___
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 2169177] perl-Prima-1.67001 is available

2023-02-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2169177



--- Comment #2 from Petr Pisar  ---
It fails a test on s390x:

#   Failed test 'one pixel is red'
#   at t/Object/Application.t line 58.
#   Failed test 'another is green'
#   at t/Object/Application.t line 60.
# Looks like you failed 2 tests of 17.
t/Object/Application.t .. 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/17 subtests


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

2023-02-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2169177

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Prima-1.67.1-1.fc39



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for Fedora ≥ 38.


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


Re: Fedora Linux 38 blocker status summary

2023-02-14 Thread mkolman
On Mon, 2023-02-13 at 15:09 -0500, Neal Gompa wrote:
> On Mon, Feb 13, 2023 at 1:56 PM Kevin Kofler via devel
>  wrote:
> > 
> > Stephen Smoogen wrote:
> > > I did a check on some.. I only downloaded 3 isos so this isn't a
> > > complete
> > > set.
> > 
> > I think trying to track down 11 to 16 years of creeping bloat now
> > is pretty
> > much a lost cause, but one thing I notice:
> > 
> > > The 20 largest packages on 33 is:
> > [snip]
> > > 47955205 qt5-qtwebkit
> > > 60158710 webkit2gtk3
> > [snip]
> > > 165482197 qt5-qtwebengine
> > [snip]
> > > 271515808 firefox
> > 
> > Having 4 different web engines on the Spin definitely does not
> > help.
> > qt5-qtwebengine is the one that logically should be there, the
> > others are
> > bloat.
> > 
> > Of these, Firefox is the largest and even overall the second
> > largest package
> > on the Spin (and that does not even include the size of the
> > separate
> > firefox-langpacks package that should be added to the Firefox
> > size). It is
> > entirely unnecessary on the KDE Spin because we already have
> > Falkon:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1920298
> > 
> > webkit2gtk3 was probably dragged in by the Anaconda → Yelp →
> > WebKitGTK
> > dependency chain. I blame Anaconda for that dependency bloat.
> > 
> > (Of course, the Anaconda web UI will make the situation even worse
> > there, in
> > that one of the above will become required by Anaconda to even just
> > display
> > its UI. I think switching to Calamares should be seriously
> > considered at
> > least for the KDE Spin.)
> > 
> > As for qt5-qtwebkit, I am not sure what dragged this in on F33. We
> > have been
> > trying to get rid of QtWebKit uses. I do not know yet what dragged
> > this in
> > on F33 and whether that has been fixed since.
> > 
> 
> FYI, if the GTK-based Anaconda UI goes away, the KDE variants
> probably
> ship a thin QtWebEngine wrapper or use Firefox instead for the
> web-based UI. No reason to depend on WebKitGTK for this.
Yes, that should be eventually possible - as long as PatternFly renders
correctly in the Web engine, it should be usable to show the Web UI
locally.

Its not like there would be much sense to target a single web engine,
given that the Web UI will support remote access and users can run
various browsers on their end.
> 
> 
> 
> 
> --
> 真実はいつも一つ!/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
___
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


procps-ng-4.0.2 rebase with new library and its name change

2023-02-14 Thread Jan Rybar
Hello,

I've made a rebase to the newest procps-ng, which had switched to its
newlib branch completely. This brings a massively-rewritten library,
formerly libprocps.so. The library changed its name to libproc2.

For this reason, I created a side-tag f39-build-side-63116.

Please ping me any time in case of a question.

Cheers,
Jan (jrybar)
___
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 2169177] perl-Prima-1.67001 is available

2023-02-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2169177

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value
 CC|ppi...@redhat.com   |




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

2023-02-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |MODIFIED



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


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


Re: Fedora Linux 38 branched

2023-02-14 Thread Iñaki Ucar
On Tue, 14 Feb 2023 at 10:46, Pavel Raiskup  wrote:
>
> On pátek 10. února 2023 11:38:25 CET Iñaki Ucar wrote:
> > On Fri, 10 Feb 2023 at 11:35, Peter Robinson  wrote:
> > >
> > > On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar  
> > > wrote:
> > > >
> > > > On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik  wrote:
> > > > >
> > > > > Hello Tomas,
> > > > > thank you for the announcement.
> > > > >
> > > > > We also branched Fedora 38 in Copr so that everybody can submit builds
> > > > > for it by now. Also, all projects with the "Follow Fedora branching"
> > > > > option configured in their project settings have F38 chroots
> > > > > automatically enabled and they contain the last build results from
> > > > > Fedora Rawhide before the branch.
> > > >
> > > > Is this still ongoing? I don't see F38 in my projects.
> > >
> > > I do in all of my packages, you should just need to do a git pull to
> > > get the new branches.
> >
> > I meant in Copr.
>
> Just confirming - Copr branching is a two-phase process;  we first link the
> RPMs from rawhide to the branched release, and then we enable (when we know 
> the
> chroot is building fine).
> https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process
>
> When Jakub announced, we just had those packages hardlinked, and RPMs 
> available
> on backend.  But the 38 chroots got enabled later (next day).

Ok, got it, thanks.

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


Re: Fedora Linux 38 branched

2023-02-14 Thread Pavel Raiskup
On pátek 10. února 2023 11:38:25 CET Iñaki Ucar wrote:
> On Fri, 10 Feb 2023 at 11:35, Peter Robinson  wrote:
> >
> > On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar  wrote:
> > >
> > > On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik  wrote:
> > > >
> > > > Hello Tomas,
> > > > thank you for the announcement.
> > > >
> > > > We also branched Fedora 38 in Copr so that everybody can submit builds
> > > > for it by now. Also, all projects with the "Follow Fedora branching"
> > > > option configured in their project settings have F38 chroots
> > > > automatically enabled and they contain the last build results from
> > > > Fedora Rawhide before the branch.
> > >
> > > Is this still ongoing? I don't see F38 in my projects.
> >
> > I do in all of my packages, you should just need to do a git pull to
> > get the new branches.
> 
> I meant in Copr.

Just confirming - Copr branching is a two-phase process;  we first link the
RPMs from rawhide to the branched release, and then we enable (when we know the
chroot is building fine).
https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process

When Jakub announced, we just had those packages hardlinked, and RPMs available
on backend.  But the 38 chroots got enabled later (next day).

Pavel


___
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


bmon license corrected

2023-02-14 Thread Boian Bonev via devel
Hi,

While doing the SPDX change, I noticed that the former bmon license was
specified as "BSD and GPLv2" which is not correct. The only files in the source
mentioning GPL are generated by autoconf. Everything else is licensed under BSD
and MIT, which translates to "BSD-2-Clause and MIT"...

Please correct me, if I am wrong.

ps. Update is in progress

With best regards,
b.


signature.asc
Description: This is a digitally signed message part
___
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: Small rant: installer environment size

2023-02-14 Thread Florian Weimer
* Adam Williamson:

> On Thu, 2022-12-08 at 07:57 +0100, Florian Weimer wrote:
>> * Adam Williamson:
>> 
>> > 1. /usr/lib/locale/locale-archive , from glibc-all-langpacks - this is
>> > 224M uncompressed. A quick test just compressing the file with xz on my
>> > system shows it compresses to around 11M, though, so that's probably
>> > all it adds up to after compression (the image is an xz-compressed
>> > squashfs)
>> 
>> Isn't the compression block-based?  I think it would be interesting to
>> measure the image size with the file removed.
>
> I'll try it tomorrow, it's not too hard.

Have you posted the outcome of the experiment somewhere?

Thanks,
Florian
___
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