date:20231003

Fedora 39 compose report: 20231003.n.0 changes

2023-10-03 Thread Fedora Branched Report

OLD: Fedora-39-20231002.n.0
NEW: Fedora-39-20231003.n.0

= SUMMARY =
Added images:5
Dropped images:  1
Added packages:  4
Dropped packages:1
Upgraded packages:   92
Downgraded packages: 0

Size of added packages:  12.22 MiB
Size of dropped packages:317.38 KiB
Size of upgraded packages:   4.23 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Scientific vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-39-20231003.n.0.x86_64.vagrant-libvirt.box
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-39-20231003.n.0.iso
Image: Scientific_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Scientific_KDE-Live-x86_64-39-20231003.n.0.iso
Image: Scientific vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-39-20231003.n.0.x86_64.vagrant-virtualbox.box
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-39-20231003.n.0.iso

= DROPPED IMAGES =
Image: Container_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Base-39-20231002.n.0.ppc64le.tar.xz

= ADDED PACKAGES =
Package: python-watchfiles-0.20.0-1.fc39
Summary: Simple, modern and high performance file watching and code reload in 
python
RPMs:python3-watchfiles
Size:1.62 MiB

Package: rust-eza-0.13.1-1.fc39
Summary: Modern replacement for ls
RPMs:eza rust-eza+default-devel rust-eza+git-devel rust-eza+git2-devel 
rust-eza+nix-devel rust-eza+vendored-libgit2-devel rust-eza-devel
Size:3.13 MiB

Package: rust-gst-plugin-gtk4-0.11.0-2.fc39
Summary: GStreamer GTK 4 Sink element and Paintable widget
RPMs:gstreamer1-plugin-gtk4 rust-gst-plugin-gtk4+capi-devel 
rust-gst-plugin-gtk4+default-devel rust-gst-plugin-gtk4+doc-devel 
rust-gst-plugin-gtk4+gdk_wayland-devel rust-gst-plugin-gtk4+gdk_x11-devel 
rust-gst-plugin-gtk4+gst_gl-devel rust-gst-plugin-gtk4+gst_gl_egl-devel 
rust-gst-plugin-gtk4+gst_gl_wayland-devel rust-gst-plugin-gtk4+gst_gl_x11-devel 
rust-gst-plugin-gtk4+static-devel rust-gst-plugin-gtk4+wayland-devel 
rust-gst-plugin-gtk4+x11egl-devel rust-gst-plugin-gtk4+x11glx-devel 
rust-gst-plugin-gtk4-devel
Size:1.74 MiB

Package: snapshot-45.0-2.fc39
Summary: Take pictures and videos
RPMs:snapshot
Size:5.72 MiB


= DROPPED PACKAGES =
Package: python-bloom-0.11.2-4.fc39
Summary: Bloom is a release automation tool
RPMs:python-bloom-doc python3-bloom
Size:317.38 KiB


= UPGRADED PACKAGES =
Package:  adobe-source-sans-pro-fonts-3.052-1.fc39
Old package:  adobe-source-sans-pro-fonts-3.046-6.fc39
Summary:  A set of OpenType fonts designed for user interfaces
RPMs: adobe-source-sans-pro-fonts
Size: 1.47 MiB
Size change:  178.34 KiB
Changelog:
  * Sun Sep 24 2023 Mohamed El Morabity  - 
3.052-1
  - Update to 3.052


Package:  authselect-1.4.3-1.fc39
Old package:  authselect-1.4.2-3.fc39
Summary:  Configures authentication and identity sources from supported 
profiles
RPMs: authselect authselect-devel authselect-libs
Size: 1.87 MiB
Size change:  20.83 KiB
Changelog:
  * Wed Sep 27 2023 Pavel B??ezina  - 1.4.3-1
  - Rebase to 1.4.3


Package:  bcm283x-firmware-20230921-1.6b37a45.fc39
Old package:  bcm283x-firmware-20230810-1.74ad049.fc39
Summary:  Firmware for the Broadcom bcm283x/bcm2711 used in the Raspberry Pi
RPMs: bcm2711-firmware bcm2835-firmware bcm283x-firmware 
bcm283x-overlays
Size: 6.97 MiB
Size change:  1.65 KiB
Changelog:
  * Tue Aug 22 2023 Peter Robinson  - 
20230810-1.74ad049
  - Update to latest firmware

  * Mon Sep 25 2023 Peter Robinson  - 
20230921-1.6b37a45
  - Update to latest firmware


Package:  boost-1.81.0-8.fc39
Old package:  boost-1.81.0-7.fc39
Summary:  The free peer-reviewed portable C++ source libraries
RPMs: boost boost-atomic boost-b2 boost-build boost-chrono 
boost-container boost-context boost-contract boost-coroutine boost-date-time 
boost-devel boost-doc boost-doctools boost-examples boost-fiber 
boost-filesystem boost-graph boost-graph-mpich boost-graph-openmpi 
boost-iostreams boost-json boost-locale boost-log boost-math boost-mpich 
boost-mpich-devel boost-mpich-python3 boost-mpich-python3-devel boost-nowide 
boost-numpy3 boost-openmpi boost-openmpi-devel boost-openmpi-python3 
boost-openmpi-python3-devel boost-program-options boost-python3 boost-random 
boost-regex boost-serialization boost-stacktrace boost-static boost-system 
boost-test boost-thread boost-timer boost-type_erasure boost-url boost-wave
Size: 337.85 MiB
Size change:  -184.20 KiB
Changelog:
  * Sun Aug 20 2023 Kefu Chai  - 1.81.0-8
  - Add patch for Boost.Accumulators bug
See https://github.com/boostorg/accumulators/pull/54


Package:  btrfsd-0.2.0-1.fc39
Old package:  btrfsd-0.1.0-1.fc39
Summary:  Tiny Btrfs

Re: Orphaning all my packages

2023-10-03 Thread Sérgio Basto

On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:
> Am 03.10.23 um 20:46 schrieb Sérgio Basto:
> > On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:
> > > On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce
> > > 
> > > wrote:
> > > > Additionally *all* of the code is fully available in git form
> > > > on
> > > > gitlab
> > > > as part of CentOS Stream.
> > > 
> > > We all know or should know that this is false. It's easy enough
> > > to
> > > disprove with a counterexample:
> > > 
> > > https://access.redhat.com/errata/RHSA-2023:1918
> > > 
> > > Try to find the code for that webkit2gtk3-2.36.7-
> > > 1.el9_1.3.src.rpm in
> > > CentOS Stream. It isn't there, and never will be.
> > > 
> > 
> > it is here :
> > https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9
> > 
> 
> 
> Since June 21 the strategy changed. Such commits do not get pushed 
> anymore. But you are right, to prove it a different example is
> necessary ...
> 


I believe you, but this version is an "right most" bump and is "just"
one security fix, when in Centos Stream [1], 6 months ago we already
have a higher version, this seems a work of security team, not real
development ...  and if these security releases aren't published
anymore is an issue I understand but I don't understand why the people
are so afraid of use Centos Stream version instead . 

[1]
https://gitlab.com/redhat/centos-stream/rpms/webkit2gtk3/-/commits/c9s/

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

-- 
Sérgio M. B.
___
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: Orphaning all my packages

2023-10-03 Thread Carlos Rodriguez Fernandez

Because when they ask “where is the code?”, they are asking a different
question than yours :)

Regards,
Carlos

On Tue, Oct 3, 2023 at 2:30 PM Simo Sorce  wrote:

> On Tue, 2023-10-03 at 23:13 +0200, Leon Fauster via devel wrote:
> > Am 03.10.23 um 21:29 schrieb Simo Sorce:
> > > On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:
> > > > Am 03.10.23 um 20:46 schrieb Sérgio Basto:
> > > > > On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:
> > > > > > On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce <
> s...@redhat.com>
> > > > > > wrote:
> > > > > > > Additionally *all* of the code is fully available in git form
> on
> > > > > > > gitlab
> > > > > > > as part of CentOS Stream.
> > > > > >
> > > > > > We all know or should know that this is false. It's easy enough
> to
> > > > > > disprove with a counterexample:
> > > > > >
> > > > > > https://access.redhat.com/errata/RHSA-2023:1918
> > > > > >
> > > > > > Try to find the code for that
> webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
> > > > > > CentOS Stream. It isn't there, and never will be.
> > > > > >
> > > > >
> > > > > it is here :
> > > > >
> https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9
> > > > >
> > > >
> > > >
> > > > Since June 21 the strategy changed. Such commits do not get pushed
> > > > anymore. But you are right, to prove it a different example is
> necessary ...
> > >
> > > You are wrong and have been mislead.
> > > Nothing has changed in how we develop and publish code in gitlab.
> >
> >
> > Nope, I do not argue about processes at all. Its about resulting code
> > fragments. Speak, having in gitlab version 8 of a package and in the
> > current/latest RHEL release (9.2) version 7 with backports of 8 doesn't
> > mean that the code is in gitlab. The code differs and its not
> > accessible. Thats all about.
>
> The code is still in gitlab, in most cases in directly accessible in
> individual commits. In some cases, like the one Michael mentioned,
> where a rebase landed early in the CentOS branch the code may land
> together with other changes, but it is not like it is not there.
> There are is a no regression policy in RHEL, so if CentOS is ahead it
> means it already has all of the code in question.
>
> And if there is an actual reason to need to know what exact change
> landed in RHEL there are several avenues to find out (just grab a
> developer subscription for example).
>
> I just find that this is generally just a mental exercise, but not
> something people do or need to do on a regular basis, and does not
> prevent any use, study, sharing or enjoyment of the code.
>
> Claiming the code is inaccessible sounds odd to me.
> But perhaps I am just old and remember when all you got from upstream
> was a tarball and you had to figure out what actual changes went in
> manually with diff ... no commits or commit messages and often not even
> a reasonable changelog ...
>
> Simo.
>
> --
> Simo Sorce,
> DE @ RHEL Crypto Team,
> Red Hat, Inc
>
>
>
> ___
> 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: Orphaning all my packages

2023-10-03 Thread Carlos Rodriguez-Fernandez

Leon,
I don't think this has ever been about whether a piece of code is
present in version 8 (using your example), but about the free (gratis)
availability of the combination of version 7 with selected backports
from version 8 that has been thoroughly tested by RedHat teams and their
infrastructure. It is the value of the QA done that it is no longer
available for free.

Regards,
Carlos.

On 10/3/23 14:13, Leon Fauster via devel wrote:

Am 03.10.23 um 21:29 schrieb Simo Sorce:

On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:

Am 03.10.23 um 20:46 schrieb Sérgio Basto:

On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:

On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce
wrote:

Additionally *all* of the code is fully available in git form on
gitlab
as part of CentOS Stream.

We all know or should know that this is false. It's easy enough to
disprove with a counterexample:

https://access.redhat.com/errata/RHSA-2023:1918

Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
CentOS Stream. It isn't there, and never will be.

it is here :
https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9

Since June 21 the strategy changed. Such commits do not get pushed
anymore. But you are right, to prove it a different example is
necessary ...

You are wrong and have been mislead.
Nothing has changed in how we develop and publish code in gitlab.

Nope, I do not argue about processes at all. Its about resulting code
fragments. Speak, having in gitlab version 8 of a package and in the
current/latest RHEL release (9.2) version 7 with backports of 8 doesn't
mean that the code is in gitlab. The code differs and its not
accessible. Thats all about.

OpenPGP_0x47EBED05C3375B1F.asc
Description: OpenPGP public key

OpenPGP_signature
Description: OpenPGP digital 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: Orphaning all my packages

2023-10-03 Thread Simo Sorce

On Tue, 2023-10-03 at 23:13 +0200, Leon Fauster via devel wrote:
> Am 03.10.23 um 21:29 schrieb Simo Sorce:
> > On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:
> > > Am 03.10.23 um 20:46 schrieb Sérgio Basto:
> > > > On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:
> > > > > On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
> > > > > wrote:
> > > > > > Additionally *all* of the code is fully available in git form on
> > > > > > gitlab
> > > > > > as part of CentOS Stream.
> > > > > 
> > > > > We all know or should know that this is false. It's easy enough to
> > > > > disprove with a counterexample:
> > > > > 
> > > > > https://access.redhat.com/errata/RHSA-2023:1918
> > > > > 
> > > > > Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
> > > > > CentOS Stream. It isn't there, and never will be.
> > > > > 
> > > > 
> > > > it is here :
> > > > https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9
> > > > 
> > > 
> > > 
> > > Since June 21 the strategy changed. Such commits do not get pushed
> > > anymore. But you are right, to prove it a different example is necessary 
> > > ...
> > 
> > You are wrong and have been mislead.
> > Nothing has changed in how we develop and publish code in gitlab.
> 
> 
> Nope, I do not argue about processes at all. Its about resulting code
> fragments. Speak, having in gitlab version 8 of a package and in the
> current/latest RHEL release (9.2) version 7 with backports of 8 doesn't
> mean that the code is in gitlab. The code differs and its not
> accessible. Thats all about.

The code is still in gitlab, in most cases in directly accessible in
individual commits. In some cases, like the one Michael mentioned,
where a rebase landed early in the CentOS branch the code may land
together with other changes, but it is not like it is not there.
There are is a no regression policy in RHEL, so if CentOS is ahead it
means it already has all of the code in question.

And if there is an actual reason to need to know what exact change
landed in RHEL there are several avenues to find out (just grab a
developer subscription for example).

I just find that this is generally just a mental exercise, but not
something people do or need to do on a regular basis, and does not
prevent any use, study, sharing or enjoyment of the code.

Claiming the code is inaccessible sounds odd to me.
But perhaps I am just old and remember when all you got from upstream
was a tarball and you had to figure out what actual changes went in
manually with diff ... no commits or commit messages and often not even
a reasonable changelog ... 

Simo.

-- 
Simo Sorce,
DE @ RHEL Crypto Team,
Red Hat, Inc

___
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: Orphaning all my packages

2023-10-03 Thread Leon Fauster via devel


Am 03.10.23 um 21:29 schrieb Simo Sorce:

On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:

Am 03.10.23 um 20:46 schrieb Sérgio Basto:

On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:

On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
wrote:

Additionally *all* of the code is fully available in git form on
gitlab
as part of CentOS Stream.


We all know or should know that this is false. It's easy enough to
disprove with a counterexample:

https://access.redhat.com/errata/RHSA-2023:1918

Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
CentOS Stream. It isn't there, and never will be.



it is here :
https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9




Since June 21 the strategy changed. Such commits do not get pushed
anymore. But you are right, to prove it a different example is necessary ...


You are wrong and have been mislead.
Nothing has changed in how we develop and publish code in gitlab.



Nope, I do not argue about processes at all. Its about resulting code
fragments. Speak, having in gitlab version 8 of a package and in the
current/latest RHEL release (9.2) version 7 with backports of 8 doesn't
mean that the code is in gitlab. The code differs and its not
accessible. Thats all about.

--
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: Orphaning all my packages

2023-10-03 Thread Matthew Miller

On Tue, Oct 03, 2023 at 04:36:20PM +0200, Michael J Gruber wrote:
> Thank you for all the effort you have put into maintaining these
> packages so far, for the benefit of all of Fedora, and consequently
> its downstream!

Indeed -- thank you Todd.

-- 
Matthew Miller

Fedora Project Leader
___
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 Linux 39 Final Freeze

2023-10-03 Thread Tomas Hrcka

Hi all,

Today, 2023-10-03, is an important day on the Fedora Linux 39 schedule
[1], with significant cut-offs.

Today we have the Final Freeze [2] which starts at 14:00 UTC. This means
that only packages that fix accepted blocker or freeze exception bugs
[3][4][5] will be marked as 'stable' and included in the Final composes.
Other builds will remain in updates-testing until the Final release is
approved, at which point the Final freeze is lifted and packages can
move to the 'updates' repository. Pending updates will be pushed before
the final release as zero day updates.

Regards,
Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html
[2] https://fedoraproject.org/wiki/Milestone_freezes
[3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[5] https://qa.fedoraproject.org/blockerbugs/milestone/39/final/buglist



-- 
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
___
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

Re: Orphaning all my packages

2023-10-03 Thread Michael Catanzaro

On Tue, Oct 3 2023 at 03:32:36 PM -0400, Solomon Peachy via devel 
 wrote:

However, this has _always_ been the situation for RHEL.  Only the
sources for the _latest_ point release (eg RHEL 7.4) were ever made
available to the general public; updates/fixes backported to prior
versions (eg RHEL 7.3) never saw the precise corresponding sources
released (directly) to the public.  Pre-Stream CentOS therefore only
ever received updates for the _latest_ point release of RHEL.


So as you mention, we've indeed never published the code for "Extended 
Update Support" branches; that has always been private to customers 
only. But we did previously publish the code for the latest stable RHEL 
branches on git.centos.org, and no longer do so. That's what has 
changed.


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: Orphaning all my packages

2023-10-03 Thread Michael Catanzaro

On Tue, Oct 3 2023 at 02:23:34 PM -0400, Stephen Gallagher 
 wrote:

The *exact* set of source code that the package was built for is
included in the Source RPM and all of the individual changes that
comprised it are part of the c9s branch in CentOS Stream (or the
maintainer has been regressing code, in which case that should be
addressed). No, the git repo might not contain a specific git
reference that directly matches the SRPM you cite, but that's not at
all the same thing as "the code isn't available in git".


OK, technically the changes are indeed sort of included in the c9s 
branch in CentOS Stream, but only along with 6000 other upstream 
changes from the upstream source tarball. You'll never plausibly figure 
out what changes correspond to this RHEL update from CentOS Stream. You 
really need that RHEL subscription to get the SRPMs and diff them to 
see what changed. It's really an incredible stretch to claim the code 
is there in CentOS Stream when you have to search for the needle in a 
haystack to find them (and how would you possibly know what to look 
for?). And even this much is not guaranteed. I could have easily 
applied a different fix to this RHEL branch than I did to CentOS 
Stream. Such situations are hardly uncommon.


So let's stop this weird claim that the code is there, please; it's 
silly and just spreading confusion. We publish code for CentOS Stream. 
We don't publish code for RHEL anymore except to customers. That's just 
how it is.


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: Orphaning all my packages

2023-10-03 Thread Michael Catanzaro




On Tue, Oct 3 2023 at 07:46:58 PM +0100, Sérgio Basto 
 wrote:



it is here :
https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9


Well OK yes, but that only worked because my example was from before we 
stopped publishing sources to git.centos.org. You were supposed to use 
CentOS Stream for this exercise. :P


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: Mock v5.0 released (and mock-core-configs v39)

2023-10-03 Thread Kevin Fenzi

On Tue, Oct 03, 2023 at 10:30:45AM +0200, Pavel Raiskup wrote:
> 
> Well, in what shape is our "layered image" build system?  Aren't we able

Terrible, and going to be decomissioned after f39 release. ;) 

But if you mean base images... those are fine.

> to create a new official image say `fedora-mock-bootstrap:`
> that would be automatically built (ideally at least as frequently as the
> base image is)?  This way we could optimize fedora builds for everyone.

Yes, we could. Just wouldn't be a layer, it would be it's own image. 

kevin


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

Re: Orphaning all my packages

2023-10-03 Thread Solomon Peachy via devel

On Tue, Oct 03, 2023 at 08:50:53PM +0200, Leon Fauster via devel wrote:
> If a bumped version of a package fixes an issue (stream variant of 
> CentOS) e.g 2.2, and a released package (rhel variant) has a 
> backported fix for e.g. 2.1, that doesn't mean that the code is also 
> in the stream git just because both code fragments fixes the same 
> issue. The backported code can be very different, and its not in the 
> git branch of the stream variant. So, that code is not available in 
> git, and to cite Michael "and never will be."

However, this has _always_ been the situation for RHEL.  Only the 
sources for the _latest_ point release (eg RHEL 7.4) were ever made 
available to the general public; updates/fixes backported to prior 
versions (eg RHEL 7.3) never saw the precise corresponding sources 
released (directly) to the public.  Pre-Stream CentOS therefore only 
ever received updates for the _latest_ point release of RHEL.

(Of course, actual RH customers can always download the corresponding 
 SRPMs, and RH will send the sources to any third party who makes a 
 request in writing, for $5)

So, yeah.  Complaining _now_ about what's been the operating policy for 
two decades seems pretty silly.

 - Solomon
-- 
Solomon Peachypizza at shaftnet dot org (email&xmpp)
  @pizza:shaftnet dot org   (matrix)
Dowling Park, FL  speachy (libera.chat)


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

Re: Orphaning all my packages

2023-10-03 Thread Simo Sorce

On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:
> Am 03.10.23 um 20:46 schrieb Sérgio Basto:
> > On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:
> > > On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
> > > wrote:
> > > > Additionally *all* of the code is fully available in git form on
> > > > gitlab
> > > > as part of CentOS Stream.
> > > 
> > > We all know or should know that this is false. It's easy enough to
> > > disprove with a counterexample:
> > > 
> > > https://access.redhat.com/errata/RHSA-2023:1918
> > > 
> > > Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
> > > CentOS Stream. It isn't there, and never will be.
> > > 
> > 
> > it is here :
> > https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9
> > 
> 
> 
> Since June 21 the strategy changed. Such commits do not get pushed 
> anymore. But you are right, to prove it a different example is necessary ...

You are wrong and have been mislead.
Nothing has changed in how we develop and publish code in gitlab.

Simo.

-- 
Simo Sorce,
DE @ RHEL Crypto Team,
Red Hat, Inc



___
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

appstream does not allow for being an email address, how to validate? (was: Packaging guidelines - validation of AppStream metadata files)

2023-10-03 Thread Marcus Müller


Hi list,

just a heads up: because we're talking about how to validate appstream metadata: When 
validating metadata, one of the "default" warnings you get is:


> In the past, mailto: URL schemas to link to email addresses were also supported for 
this URL type. It is recommended to not use them in new metadata, as they provide poor 
usability on most systems when users click on such a link and no local email client is 
configured.


I just got word from upstream that the official standing is that a point of contact for a 
software package can not validly be an email address:


https://github.com/ximion/appstream/issues/331

I believe they do that in good faith ("most probably don't even have an email client set 
up"), but this basically means I can not write *correct* and *valid* metadata at the same 
time:


Our whole social maintenance infrastructure (and, debian all the same) is built on the 
fact that packagers have email addresses. It's the *one* common medium.
I've hence asked whether that ruling could be softened; after all, a user interface 
problem ("can't open mail client upon a click") is not the same as a metadata issue. 
Sadly, appstream maintenance and I seem to disagree here.


Either way, as far as I understand we aim for zero-warning, yet correct metadata. I'm 
involved in upstream packaging of software myself, so I wonder how I can make my upstream 
metainfo ideally 100% applicable for fedora, yet correct. Email *is* the way to reach the 
software maintainers.


Best,
Marcus

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

Fedora rawhide compose report: 20231003.n.0 changes

2023-10-03 Thread Fedora Rawhide Report

OLD: Fedora-Rawhide-20231002.n.0
NEW: Fedora-Rawhide-20231003.n.0

= SUMMARY =
Added images:2
Dropped images:  3
Added packages:  9
Dropped packages:1
Upgraded packages:   89
Downgraded packages: 0

Size of added packages:  5.95 MiB
Size of dropped packages:317.40 KiB
Size of upgraded packages:   9.79 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20231003.n.0.iso
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20231003.n.0.iso

= DROPPED IMAGES =
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20231002.n.0.iso
Image: LXQt live aarch64
Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20231002.n.0.iso
Image: Workstation live ppc64le
Path: 
Workstation/ppc64le/iso/Fedora-Workstation-Live-ppc64le-Rawhide-20231002.n.0.iso

= ADDED PACKAGES =
Package: kf6-kcalendarcore-5.240.0^20230829.232751.2905599-1.fc40
Summary: KDE Frameworks 6 Tier 1 KCalendarCore Library
RPMs:kf6-kcalendarcore kf6-kcalendarcore-devel
Size:2.11 MiB

Package: kf6-kcodecs-5.240.0^20230829.232811.ea56b58-1.fc40
Summary: KDE Frameworks 6 Tier 1 addon with string manipulation methods
RPMs:kf6-kcodecs kf6-kcodecs-devel
Size:1.13 MiB

Package: kf6-kitemmodels-5.240.0^20230914.113622.4c5c663-1.fc40
Summary: KDE Frameworks 6 Tier 1 addon with item models
RPMs:kf6-kitemmodels kf6-kitemmodels-devel
Size:1.10 MiB

Package: kf6-prison-5.240.0^20230925.220236.d99e5a2-1.fc40
Summary: KDE Frameworks 6 Tier 1 barcode library
RPMs:kf6-prison kf6-prison-devel
Size:558.65 KiB

Package: lklug-fonts-0.6-29.20090803cvs.fc40
Summary: Fonts for Sinhala language
RPMs:lklug-fonts
Size:90.45 KiB

Package: pthreadpool-0.0^git20230829.4fe0e1e-2.fc40
Summary: Portable thread pool
RPMs:pthreadpool pthreadpool-devel
Size:267.91 KiB

Package: python-annotated-types-0.5.0-1.fc40
Summary: Reusable constraint types to use with typing.Annotated
RPMs:python3-annotated-types
Size:25.30 KiB

Package: python-pybv-0.7.5-1.fc40
Summary: A lightweight I/O utility for the BrainVision data format
RPMs:python-pybv-doc python3-pybv python3-pybv+export
Size:168.72 KiB

Package: rutabaga-gfx-ffi-0.1.2-2.20230913gitc3ad0e43e.fc40
Summary: Handling virtio-gpu protocols
RPMs:rutabaga-gfx-ffi rutabaga-gfx-ffi-devel
Size:536.79 KiB


= DROPPED PACKAGES =
Package: python-bloom-0.11.2-4.fc39
Summary: Bloom is a release automation tool
RPMs:python-bloom-doc python3-bloom
Size:317.40 KiB


= UPGRADED PACKAGES =
Package:  SDL2-2.28.4-1.fc40
Old package:  SDL2-2.26.5-2.fc39
Summary:  Cross-platform multimedia library
RPMs: SDL2 SDL2-devel SDL2-static
Size: 9.57 MiB
Size change:  91.99 KiB
Changelog:
  * Mon Oct 02 2023 Tom Callaway  - 2.28.4-1
  - update to 2.28.4


Package:  ansible-core-2.16.0~b1-2.fc40
Old package:  ansible-core-2.16.0~b1-1.fc40
Summary:  A radically simple IT automation system
RPMs: ansible-core ansible-core-doc
Size: 5.12 MiB
Size change:  368 B
Changelog:
  * Mon Oct 02 2023 Miro Hron??ok  - 2.16.0~b1-2
  - Do not use tomcli in Fedora ELN, avoid pulling unwanted dependencies


Package:  aubit4gl-1.6.1.p3-1.fc40
Old package:  aubit4gl-1.6.1.p2-1.fc40
Summary:  IBM Informix 4GL compatible compiler
RPMs: aubit4gl aubit4gl-devel
Size: 3.97 MiB
Size change:  -2.45 MiB
Changelog:
  * Mon Oct 02 2023 Chad Lemmen  - 1.6.1.p3-1
  - added configure option --with-informix
  - cleaned up include directory to match upstream
  - updated to 1.6.1.p3


Package:  autorestic-1.7.9-1.fc40
Old package:  autorestic-1.7.7-1.fc39
Summary:  Config driven, easy backup cli for restic
RPMs: autorestic
Size: 11.57 MiB
Size change:  72.33 KiB
Changelog:
  * Mon Jul 31 2023 Major Hayden  - 1.7.7-2
  - Add packit config

  * Mon Oct 02 2023 Major Hayden  - 1.7.7-3
  - Skip bodhi updates from packit

  * Mon Oct 02 2023 Major Hayden  - 1.7.9-1
  - Update to 1.7.9


Package:  boost-1.81.0-9.fc40
Old package:  boost-1.81.0-6.fc39
Summary:  The free peer-reviewed portable C++ source libraries
RPMs: boost boost-atomic boost-b2 boost-build boost-chrono 
boost-container boost-context boost-contract boost-coroutine boost-date-time 
boost-devel boost-doc boost-doctools boost-examples boost-fiber 
boost-filesystem boost-graph boost-graph-mpich boost-graph-openmpi 
boost-iostreams boost-json boost-locale boost-log boost-math boost-mpich 
boost-mpich-devel boost-mpich-python3 boost-mpich-python3-devel boost-nowide 
boost-numpy3 boost-openmpi boost-openmpi-devel boost-openmpi-python3 
boost-openmpi-python3-devel boost-program-options boost-python3 boost-random 
boost-regex boost

Re: Orphaning all my packages

2023-10-03 Thread Leon Fauster via devel


Am 03.10.23 um 20:46 schrieb Sérgio Basto:

On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:

On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
wrote:

Additionally *all* of the code is fully available in git form on
gitlab
as part of CentOS Stream.


We all know or should know that this is false. It's easy enough to
disprove with a counterexample:

https://access.redhat.com/errata/RHSA-2023:1918

Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
CentOS Stream. It isn't there, and never will be.



it is here :
https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9




Since June 21 the strategy changed. Such commits do not get pushed 
anymore. But you are right, to prove it a different example is necessary ...


--
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: Orphaning all my packages

2023-10-03 Thread Leon Fauster via devel


Am 03.10.23 um 20:23 schrieb Stephen Gallagher:

On Tue, Oct 3, 2023 at 2:14 PM Michael Catanzaro  wrote:


On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
wrote:

Additionally *all* of the code is fully available in git form on
gitlab
as part of CentOS Stream.


We all know or should know that this is false. It's easy enough to
disprove with a counterexample:

https://access.redhat.com/errata/RHSA-2023:1918

Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
CentOS Stream. It isn't there, and never will be.



The *exact* set of source code that the package was built for is
included in the Source RPM and all of the individual changes that
comprised it are part of the c9s branch in CentOS Stream (or the
maintainer has been regressing code, in which case that should be
addressed). No, the git repo might not contain a specific git
reference that directly matches the SRPM you cite, but that's not at
all the same thing as "the code isn't available in git".



Not sure if its intentional or not but the misunderstanding
in the communication is ridiculous. Some one argues that the code
is available and forget to explain what code is mentioned. If a bumped
version of a package fixes an issue (stream variant of CentOS) e.g 2.2,
and a released package (rhel variant) has a backported fix for e.g. 2.1,
that doesn't mean that the code is also in the stream git just because
both code fragments fixes the same issue. The backported code can be
very different, and its not in the git branch of the stream variant.
So, that code is not available in git, and to cite Michael "and never
will be."

--
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: Orphaning all my packages

2023-10-03 Thread Sérgio Basto

On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:
> On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
> wrote:
> > Additionally *all* of the code is fully available in git form on 
> > gitlab
> > as part of CentOS Stream.
> 
> We all know or should know that this is false. It's easy enough to 
> disprove with a counterexample:
> 
> https://access.redhat.com/errata/RHSA-2023:1918
> 
> Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
> CentOS Stream. It isn't there, and never will be.
> 

it is here :
https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9


> 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

-- 
Sérgio M. B.
___
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: Orphaning all my packages

2023-10-03 Thread Stephen Gallagher

On Tue, Oct 3, 2023 at 2:14 PM Michael Catanzaro  wrote:
>
> On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce 
> wrote:
> > Additionally *all* of the code is fully available in git form on
> > gitlab
> > as part of CentOS Stream.
>
> We all know or should know that this is false. It's easy enough to
> disprove with a counterexample:
>
> https://access.redhat.com/errata/RHSA-2023:1918
>
> Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
> CentOS Stream. It isn't there, and never will be.
>

The *exact* set of source code that the package was built for is
included in the Source RPM and all of the individual changes that
comprised it are part of the c9s branch in CentOS Stream (or the
maintainer has been regressing code, in which case that should be
addressed). No, the git repo might not contain a specific git
reference that directly matches the SRPM you cite, but that's not at
all the same thing as "the code isn't available in git".
___
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: Orphaning all my packages

2023-10-03 Thread Michael Catanzaro

On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce  
wrote:
Additionally *all* of the code is fully available in git form on 
gitlab

as part of CentOS Stream.


We all know or should know that this is false. It's easy enough to 
disprove with a counterexample:


https://access.redhat.com/errata/RHSA-2023:1918

Try to find the code for that webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in 
CentOS Stream. It isn't there, and never will be.


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: Orphaning all my packages

2023-10-03 Thread Simo Sorce

On Tue, 2023-10-03 at 11:33 -0400, Todd Zullinger wrote:
> Sérgio Basto wrote:
> > On Tue, 2023-10-03 at 10:25 -0400, Todd Zullinger wrote:
> > > a project
> > > where the primary sponsor and downstream no longer provides
> > > source code freely and openly
> > 
> > what you are talking about ? all RHEL Source are freely available on
> > Centos Stream , and RHEL never was free . 
> 
> That's not the case, but I don't wish to go wildly off-topic
> about it either.
> 
> _Most_ of the source is available, but not all of it.  This
> is a case where -- for me -- close is not good enough.
> 
> To each their own.

Todd,
you can definitely choose where to contribute and that is fine, and
thanks for what you contributed till today.

However, *all* of RHEL code is available with "free as in freedom"
licenses to all RHEL customers, as the licenses dictate (and beyond as
we apply the same rigor to *all* code as if all were GPLed).
You can see that for free (gratis) by subscribing to the developer
subscription if you are curious.

Additionally *all* of the code is fully available in git form on gitlab
as part of CentOS Stream.

If that is not enough for you, that's fine, just do not spread false
information.

Thanks,
Simo.

-- 
Simo Sorce,
DE @ RHEL Crypto Team,
Red Hat, Inc

___
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: Orphaning all my packages

2023-10-03 Thread Leon Fauster via devel


Am 03.10.23 um 17:33 schrieb Todd Zullinger:

Sérgio Basto wrote:

On Tue, 2023-10-03 at 10:25 -0400, Todd Zullinger wrote:

a project
where the primary sponsor and downstream no longer provides
source code freely and openly


what you are talking about ? all RHEL Source are freely available on
Centos Stream , and RHEL never was free .


That's not the case, but I don't wish to go wildly off-topic
about it either.

_Most_ of the source is available, but not all of it.  This
is a case where -- for me -- close is not good enough.

To each their own.



I personally was shocked after the related announcement of RH
and my affective reaction was similar to yours. But, taking
a wider look at the ecosystem reveals that RH is giving a lot
to the "community" [1] and I am sure that the landscape would not
look like this (viable projects) if RH did not exist.

Anyway, a lot of companies provide commercial products, that use
open source as their ground floor. Stopping the support in upstream
projects because of that, hits the wrong "people" (IMO).

Nevertheless, thank you for your long contribution!

[1] https://www.redhat.com/en/about/open-source-program-office/contributions

--
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: Orphaning all my packages

2023-10-03 Thread Todd Zullinger

Sérgio Basto wrote:
> On Tue, 2023-10-03 at 10:25 -0400, Todd Zullinger wrote:
>> a project
>> where the primary sponsor and downstream no longer provides
>> source code freely and openly
> 
> what you are talking about ? all RHEL Source are freely available on
> Centos Stream , and RHEL never was free . 

That's not the case, but I don't wish to go wildly off-topic
about it either.

_Most_ of the source is available, but not all of it.  This
is a case where -- for me -- close is not good enough.

To each their own.

-- 
Todd


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

Re: Orphaning all my packages

2023-10-03 Thread Robby Callicotte via devel

On Tuesday, October 3, 2023 9:32:17 AM CDT Jonathan Wright via devel wrote:
> I've picked up git and paperkey.
> 
> On Tue, Oct 3, 2023 at 9:25 AM Todd Zullinger  wrote:
> > Hi,
> > 
> > I'm orphaning all my packages (which I effectively did
> > months ago).  It's been fun being a maintainer since 2006.
> > 
> > However, I am not interested in contributing to a project
> > where the primary sponsor and downstream no longer provides
> > source code freely and openly.  It's simply not consistent
> > with why I use and contribute to Fedora and Free/Open Source
> > Software in general.
> > 
> > I'm a maintainer of the following packages:
> > cgit
> > git
> > paperkey
> > 
> > I'm an admin of the following packages:
> > fail2ban
> > rubygem-asciidoctor
> > 
> > I have commit privileges on these additional packages:
> > asciidoc
> > git-filter-repo
> > rpmlint
> > 
> > Thanks,
> > 
> > --
> > Todd Zullinger
> > ___
> > 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/de...@lists.fedoraproject.or
> > g
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue

Thank you for all you have done.

I have picked up cgit

--
Robby Callicotte


___
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: Orphaning all my packages

2023-10-03 Thread Sérgio Basto

On Tue, 2023-10-03 at 10:25 -0400, Todd Zullinger wrote:
> a project
> where the primary sponsor and downstream no longer provides
> source code freely and openly

what you are talking about ? all RHEL Source are freely available on
Centos Stream , and RHEL never was free . 

-- 
Sérgio M. B.
___
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: Orphaning all my packages

2023-10-03 Thread Leslie Satenstein via devel

Hi  Todd Zullinger

Got your message! 

Leslie Satenstein   
PS. 
I share your views.  I am a senior, age 82.7 (Born Jan 1941), and while I did a 
great deal of QA / Testing,I am very disappointed in the direction that both 
the Europeans and Americans are heading.  
There is, underway now, a strong European attack against the government, 
regarding FOSS.  If the government wins, 
much opensource will be considered propriatory.  The Americans will "Monkey 
see, Monkey do", to incorporate the same.
You made a decision that I support.
Take care.
 

On Tuesday, October 3, 2023 at 10:25:40 a.m. EDT, Todd Zullinger 
 wrote:  
 
 Hi,

I'm orphaning all my packages (which I effectively did
months ago).  It's been fun being a maintainer since 2006.

However, I am not interested in contributing to a project
where the primary sponsor and downstream no longer provides
source code freely and openly.  It's simply not consistent
with why I use and contribute to Fedora and Free/Open Source
Software in general.

I'm a maintainer of the following packages:

    cgit
    git
    paperkey

I'm an admin of the following packages:

    fail2ban
    rubygem-asciidoctor

I have commit privileges on these additional packages:

    asciidoc
    git-filter-repo
    rpmlint

Thanks,

-- 
Todd Zullinger
___
 
To  


| 
| 
|  | 
OpenID transaction in progress


 |

 |

 |



  ___
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: Orphaning all my packages

2023-10-03 Thread Todd Zullinger

Hi,

Michael J Gruber wrote:
> Thank you for all the effort you have put into maintaining these
> packages so far, for the benefit of all of Fedora, and consequently
> its downstream!

Thanks!

> Your reasons resonate with me, though I'm not taking the same
> conclusions. Have you arranged "succession" with your git
> co-maintainers?

I have not, but I presumed that git would be picked up
quickly as it's a rather important package.  And it looks
like that's already happened. :)

All the best,,

-- 
Todd


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

Re: Orphaning all my packages

2023-10-03 Thread Michael J Gruber

Am Di., 3. Okt. 2023 um 16:25 Uhr schrieb Todd Zullinger :
>
> Hi,
>
> I'm orphaning all my packages (which I effectively did
> months ago).  It's been fun being a maintainer since 2006.
>
> However, I am not interested in contributing to a project
> where the primary sponsor and downstream no longer provides
> source code freely and openly.  It's simply not consistent
> with why I use and contribute to Fedora and Free/Open Source
> Software in general.
>
> I'm a maintainer of the following packages:
>
> cgit
> git
> paperkey
>
> I'm an admin of the following packages:
>
> fail2ban
> rubygem-asciidoctor
>
> I have commit privileges on these additional packages:
>
> asciidoc
> git-filter-repo
> rpmlint
>
> Thanks,

Thank you for all the effort you have put into maintaining these
packages so far, for the benefit of all of Fedora, and consequently
its downstream!

Your reasons resonate with me, though I'm not taking the same
conclusions. Have you arranged "succession" with your git
co-maintainers?

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: Orphaning all my packages

2023-10-03 Thread Jonathan Wright via devel

I've picked up git and paperkey.

On Tue, Oct 3, 2023 at 9:25 AM Todd Zullinger  wrote:

> Hi,
>
> I'm orphaning all my packages (which I effectively did
> months ago).  It's been fun being a maintainer since 2006.
>
> However, I am not interested in contributing to a project
> where the primary sponsor and downstream no longer provides
> source code freely and openly.  It's simply not consistent
> with why I use and contribute to Fedora and Free/Open Source
> Software in general.
>
> I'm a maintainer of the following packages:
>
> cgit
> git
> paperkey
>
> I'm an admin of the following packages:
>
> fail2ban
> rubygem-asciidoctor
>
> I have commit privileges on these additional packages:
>
> asciidoc
> git-filter-repo
> rpmlint
>
> Thanks,
>
> --
> Todd Zullinger
> ___
> 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 Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

Orphaning all my packages

2023-10-03 Thread Todd Zullinger

Hi,

I'm orphaning all my packages (which I effectively did
months ago).  It's been fun being a maintainer since 2006.

However, I am not interested in contributing to a project
where the primary sponsor and downstream no longer provides
source code freely and openly.  It's simply not consistent
with why I use and contribute to Fedora and Free/Open Source
Software in general.

I'm a maintainer of the following packages:

cgit
git
paperkey

I'm an admin of the following packages:

fail2ban
rubygem-asciidoctor

I have commit privileges on these additional packages:

asciidoc
git-filter-repo
rpmlint

Thanks,

-- 
Todd Zullinger
___
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: Contact attempt for the Inactive Packagers Policy for the F39 release cycle

2023-10-03 Thread Mattia Verga via devel

Please, if you have not received this email directly from me (not through the 
mailing list) and you are not listed in the affected username, there's no need 
to reply.

Thank you.

Mattia

Il 03/10/23 13:57, Adam Piasecki ha scritto:

> Hello,
>
> Yes - I would like my account to continue being listed in the `packager` 
> group, as I am eager to contribute to Fedora.
>
> Regards,
> Adam Piasecki.
>
> On Tue, 3 Oct 2023 at 04:23, jeff stewart  wrote:
>
>> Yes still interested in contributing to fedora
>>
>> On Thu, Sep 28, 2023, 9:06 AM Mattia Verga via devel 
>>  wrote:
>>
>>> 
>>> This email was sent both to the mailing list for raising awareness to
>>> the community and BCC directly to the affected users from which we need
>>> a reply. If you have received this email only from the mailing list, you
>>> can ignore the next part.
>>> 
>>>
>>> Hello,
>>>
>>> during our periodic check as per the "Inactive packagers policy" [1] we
>>> detected no activity from you as a packager, nor in other Fedora
>>> community places, like Bodhi or mailing lists.
>>>
>>> In order to reduce security risks from possible accounts hijacking we
>>> tried to contact you by tagging your username in the appropriate ticket
>>> within pagure.io repository [2], but your username is not registered
>>> there, so we cannot contact you in that way.
>>>
>>> Please, let us know if you're still intersted in participating in Fedora
>>> and if you still need your account to be listed in the packager group.
>>> You can reply here in the mailing list, so that your activity can be
>>> detected by the script, or just login in pagure.io with your Fedora
>>> account and reply to the ticket which refers to your username.
>>>
>>> Without any reply from you, one week after the release of F39 the
>>> `packager` group membership will be removed from your account and any
>>> package for which you are the main admin will be orphaned, so that
>>> co-maintainers can pick them up.
>>>
>>> [1]
>>> https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/
>>> [2] https://pagure.io/find-inactive-packagers/issues
>>>
>>> Thank you.
>>>
>>> Mattia
>>>
>>> -
>>>
>>> This is the full list of usernames which cannot be reached by tag in
>>> pagure.io:
>>>
>>> gsgatlin
>>> dmarlin
>>> andriy
>>> buytenh
>>> jbernard
>>> shardy
>>> bhills
>>> lgao
>>> lgoncalv
>>> krionbsd
>>> rkennke
>>> angelonord
>>> athomas
>>> dmaley
>>> eglynn
>>> endur
>>> florencia
>>> mwringe
>>> rosslagerwall
>>> sgros
>>> tlavocat
>>> xinghong
>>> pcullen
>>> jshort
>>>
>>> -
>>>
>>> ___
>>> 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
>>
>> ___
>> 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: SPDX Statistics - Munich Agreement edition

2023-10-03 Thread Miroslav Suchý


Dne 03. 10. 23 v 9:31 John Reiser napsal(a):


Especially because texlive was such an outlier, then any linear estimate
should state the starting and ending dates that were used for the projection. 


https://docs.google.com/spreadsheets/d/1QVMEzXWML-6_Mrlln02axFAaRKCQ8zE807rpCjus-8s/edit#gid=0

See the formula in cell A53

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
___
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: Contact attempt for the Inactive Packagers Policy for the F39 release cycle

2023-10-03 Thread Adam Piasecki

Hello,

Yes - I would like my account to continue being listed in the `*packager*`
group, as I am eager to contribute to Fedora.

Regards,
Adam Piasecki.

On Tue, 3 Oct 2023 at 04:23, jeff stewart  wrote:

> Yes still interested in contributing to fedora
>
> On Thu, Sep 28, 2023, 9:06 AM Mattia Verga via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> 
>> This email was sent both to the mailing list for raising awareness to
>> the community and BCC directly to the affected users from which we need
>> a reply. If you have received this email only from the mailing list, you
>> can ignore the next part.
>> 
>>
>> Hello,
>>
>> during our periodic check as per the "Inactive packagers policy" [1] we
>> detected no activity from you as a packager, nor in other Fedora
>> community places, like Bodhi or mailing lists.
>>
>> In order to reduce security risks from possible accounts hijacking we
>> tried to contact you by tagging your username in the appropriate ticket
>> within pagure.io repository [2], but your username is not registered
>> there, so we cannot contact you in that way.
>>
>> Please, let us know if you're still intersted in participating in Fedora
>> and if you still need your account to be listed in the packager group.
>> You can reply here in the mailing list, so that your activity can be
>> detected by the script, or just login in pagure.io with your Fedora
>> account and reply to the ticket which refers to your username.
>>
>> Without any reply from you, one week after the release of F39 the
>> `packager` group membership will be removed from your account and any
>> package for which you are the main admin will be orphaned, so that
>> co-maintainers can pick them up.
>>
>> [1]
>> https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/
>> [2] https://pagure.io/find-inactive-packagers/issues
>>
>> Thank you.
>>
>> Mattia
>>
>> -
>>
>> This is the full list of usernames which cannot be reached by tag in
>> pagure.io:
>>
>> gsgatlin
>> dmarlin
>> andriy
>> buytenh
>> jbernard
>> shardy
>> bhills
>> lgao
>> lgoncalv
>> krionbsd
>> rkennke
>> angelonord
>> athomas
>> dmaley
>> eglynn
>> endur
>> florencia
>> mwringe
>> rosslagerwall
>> sgros
>> tlavocat
>> xinghong
>> pcullen
>> jshort
>>
>> -
>>
>> ___
>> 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
>>
> ___
> 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: PHP 8.3 mass rebuild - Done

2023-10-03 Thread Remi Collet


Le 03/10/2023 à 07:39, Remi Collet a écrit :

Hi,

https://fedoraproject.org/wiki/Changes/php83

Mass rebuild is started in f40-build-side-74920


Mass rebuild is done and update pushed in stable:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-246a5cdcbe

Single FTBFS (already reported, not related to PHP)
mapserver-8.0.1-6.fc40
https://bugzilla.redhat.com/show_bug.cgi?id=2241706

58 Builds:
php-8.3.0~RC3-2.fc40
libguestfs-1.51.7-2.fc40
libkolabxml-1.2.0-19.fc40
mlt-7.18.0-4.fc40
php-ast-1.1.0-6.fc40
php-facedetect-1.2.0-0.34.20201021git2a8974b.fc40
php-geos-1.0.0-28.fc40
php-libvirt-0.5.7-1.fc40
php-maxminddb-1.11.0-11.fc40
php-pecl-amqp-2.1.0-2.fc40
php-pecl-apcu-5.1.22-6.fc40
php-pecl-apfd-1.0.3-9.fc40
php-pecl-dio-0.2.1-5.fc40
php-pecl-ds-1.4.0-7.fc40
php-pecl-event-3.0.8-5.fc40
php-pecl-fann-1.2.0~RC2-5.fc40
php-pecl-gearman-2.1.0-12.fc40
php-pecl-geoip-1.1.1-24.fc40
php-pecl-gmagick-2.0.6~RC1-10.fc40
php-pecl-http-4.2.4-2.fc40
php-pecl-igbinary-3.2.14-1.fc40
php-pecl-imagick-3.7.0-9.fc40
php-pecl-inotify-3.0.0-9.fc40
php-pecl-ip2location-8.2.0-3.fc40
php-pecl-json-post-1.1.0-9.fc40
php-pecl-krb5-1.1.5-3.fc40
php-pecl-lzf-1.7.0-8.fc40
php-pecl-mailparse-3.1.6-2.fc40
php-pecl-mcrypt-1.0.6-3.fc40
php-pecl-memcache-8.2-3.fc40
php-pecl-memcached-3.2.0-7.fc40
php-pecl-mongodb-1.16.2-2.fc40
php-pecl-msgpack-2.2.0-3.fc40
php-pecl-oauth-2.0.7-13.fc40
php-pecl-pcov-1.0.11-7.fc40
php-pecl-pq-2.2.2-3.fc40
php-pecl-raphf-2.0.1-13.fc40
php-pecl-redis5-5.3.7-6.fc40
php-pecl-rpminfo-0.7.0-2.fc40
php-pecl-rrd-2.0.3-10.fc40
php-pecl-selinux-0.6.0-7.fc40
php-pecl-ssdeep-1.1.0-18.fc40
php-pecl-ssh2-1.4-3.fc40
php-pecl-uopz-7.1.1-9.fc40
php-pecl-uuid-1.2.0-11.fc40
php-pecl-var-representation-0.1.4-4.fc40
php-pecl-xattr-1.4.0-13.fc40
php-pecl-xdebug3-3.3.0~alpha2-1.fc40
php-pecl-xmldiff-1.1.3-9.fc40
php-pecl-xmlrpc-1.0.0~rc3-8.fc40
php-pecl-yac-2.3.1-8.fc40
php-pecl-zip-1.22.2-2.fc40
php-phpiredis-1.0.1-14.fc40
php-smbclient-1.1.1-3.fc40
php-zmq-1.1.3-27.fc40
php-zstd-0.13.1-2.fc40
remctl-3.18-9.fc40
uwsgi-2.0.22-6.fc40


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

Orphaning scalacheck

2023-10-03 Thread Christiano Anderson

Hi,

I'm orphaning the scalacheck package.

Best,

Christiano
___
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: Mock v5.0 released (and mock-core-configs v39)

2023-10-03 Thread Pavel Raiskup

On neděle 20. srpna 2023 11:27:44 CEST Miroslav Suchý wrote:
> Dne 14. 08. 23 v 21:30 Michael J Gruber napsal(a):
> > Is this supposed to work now?
> >
> > With mock-5.0-1.fc38.noarch and after scrubbing, the image is pulled but
> > then not used because it is "not marked ready" (rawhide, f39, f38). Am I
> > holding it wrong?
> 
> 1) When image is not marked ready then it is still used. Only
>additional packages are installed into chroot when image is
>unpacked. It is still faster than installing whole chroot using
>DNF.
> 
> 2) Only RHEL images has all packages installed by default:
> 
> https://github.com/rpm-software-management/mock/commit/e7139e1ce10198066b13fd6d3e899e507c637bf8
> 
> Other images does not have necessary tools installed.
> 
> I do not expect that default Fedora images will have all packages
> installed by default. It does not make sense.
> 
> This is targeted for teams that do frequent builds and they can prepare
> the image tuned for their needs and mark it as ready. It will
> significantly lower the time before mock starts rpmbuild.

Well, in what shape is our "layered image" build system?  Aren't we able
to create a new official image say `fedora-mock-bootstrap:`
that would be automatically built (ideally at least as frequently as the
base image is)?  This way we could optimize fedora builds for everyone.

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

[Test-Announce] Join Us for Fedora 39 Cloud Test Day on October 3rd & 4th!

2023-10-03 Thread Sumantro Mukherjee

Dear Fedora Community,

We're excited to announce the Fedora 39 Cloud Test Day[0], and we need
your help! Before the official release of Fedora 39, we're seeking
community members to participate in a focused testing event. By
contributing, you'll be helping to ensure the stability and quality of
the upcoming Fedora Cloud release.

[0] http://fedoraproject.org/wiki/Test_Day:2023-10-03_Fedora_39_Cloud_Testday

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

Re: SPDX Statistics - Munich Agreement edition

2023-10-03 Thread John Reiser


New projection when we will be finished is 2024-08-06.  Pure linear 
approximation.


Especially because texlive was such an outlier, then any linear estimate
should state the starting and ending dates that were used for the projection.
Similar to financial statistics, it might be better
to use a moving average over a constant trailing duration
(such as previous 90 days), perhaps with adjustment due to texlive.
___
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

39 matches

Mail list logo