[EPEL-devel] Re: EPEL-ANNOUNCE Incompatible Upgrade of singularity-ce in EPEL 7 / 8 / 9

[Jonathan Wright via epel-devel]

Thank you for the followup.

On Thu, Apr 11, 2024 at 7:51 PM David Trudgian via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:

> The singularity-ce incompatible upgrade has now been pushed to stable.
>
> This is the final announcement prescribed by the EPEL Incompatible
> Upgrades Policy:
>
>
> https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
>
> Cheers,
>
> DT
>
>
> On 9 Feb 2024, at 10:45, David Trudgian  wrote:
> >
> > After approval in the last EPEL meeting [1], I have submitted an
> incompatible upgrade of singularity-ce to testing for EPEL 7, 8 & 9.
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cbd86d2020
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f299fbc570
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-05e20edbbf
> >
> > These updates upgrade singularity-ce from v3.11.5 to v4.1.1.
> >
> > The following incompatibilities should be noted by users:
> >
> > 1) Some functionality previously provided by the `singularity remote`
> command is split into new `singularity registry` and `singularity
> keyserver` commands.
> > 2) The `singularity remote add` command now sets a newly added remote as
> the default (unless suppressed). Previously the user had to set the default
> remote manually.
> > 3) The deprecated and unmaintained `—vm` flag to start singularity
> inside a Virtual Machine has been removed.
> >
> > 4) Bind mounts are now performed in the order in which they are
> specified. Previously, image based bind mounts were performed before others.
> > 5) Current working directory on the host is now created in the
> container, restoring a behaviour from Singularity <3.6.0 unless suppressed.
> > 6) If the current directory paths on the container and host contains
> symlinks to different locations, the current working directory is not
> mounted.
> >
> > Changes 1,2,3 are expected to have minimal impact, and 4,5,6 are likely
> to be considered bug fixes by many users.
> >
> > No changes are required to existing configuration files for this update.
> >
> > A complete description of changes and additions between v3.11 and v4.1.1
> is available in the upstream documentation at https://sylabs.io/docs/
> >
> > In the absence of any issues, the updates will be pushed to stable after
> a one week testing period has passed, with a follow-up notification here.
> >
> > Cheers,
> >
> > David Trudgian
> >
> >
> > [1] https://pagure.io/epel/issue/265#comment-894790
> > --
> > ___
> > epel-announce mailing list -- epel-annou...@lists.fedoraproject.org
> > To unsubscribe send an email to
> epel-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/epel-annou...@lists.fedoraproject.org
> > Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

[EPEL-devel] Re: activemq-cpp in epel8

[Jonathan Wright via epel-devel]

Managed to get this packed up.  Now we just wait for the peer review from
another packager.

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

On Wed, Apr 3, 2024 at 10:01 AM Jonathan Wright 
wrote:

> Evan,
>
> I will look into this.  Looks like it was retired years ago for failing to
> build: https://bugzilla.redhat.com/show_bug.cgi?id=1674632
>
> It will have to be re-reviewed since it was retired/orphaned more than 6
> weeks ago so a reasonable timeframe to (potentially) get it back into repos
> and EPEL8 is a 2-6 weeks depending on how quickly a reviewer will pick it
> up, and if it will build against modern versions of Fedora/RHEL.
>
> On Wed, Apr 3, 2024 at 9:57 AM Ward, Evan M CIV USN NRL (8112) Washington
> DC (USA) via epel-devel  wrote:
>
>> Hi,
>>
>> Are there any packagers who would like to package activemq-cpp in
>> epel8? It's already in epel7.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=2244652
>>
>> Regards,
>> Evan Ward
>> --
>> ___
>> 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
>>
>
>
> --
> Jonathan Wright
> AlmaLinux Foundation
> Mattermost: chat 
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

[EPEL-devel] Re: activemq-cpp in epel8

[Jonathan Wright via epel-devel]

Evan,

I will look into this.  Looks like it was retired years ago for failing to
build: https://bugzilla.redhat.com/show_bug.cgi?id=1674632

It will have to be re-reviewed since it was retired/orphaned more than 6
weeks ago so a reasonable timeframe to (potentially) get it back into repos
and EPEL8 is a 2-6 weeks depending on how quickly a reviewer will pick it
up, and if it will build against modern versions of Fedora/RHEL.

On Wed, Apr 3, 2024 at 9:57 AM Ward, Evan M CIV USN NRL (8112) Washington
DC (USA) via epel-devel  wrote:

> Hi,
>
> Are there any packagers who would like to package activemq-cpp in
> epel8? It's already in epel7.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2244652
>
> Regards,
> Evan Ward
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

[EPEL-devel] certbot Update From 2.6.0 to 2.9.0 in EPEL9

[Jonathan Wright via epel-devel]

Hello,

I'm updating certbot from 2.6.0 to 2.9.0 in EPEL9 [1].  This contains one
minor, potentially breaking changes though I don't expect it to impact
anyone:

NamespaceConfig now tracks how its arguments were set via a dictionary,
allowing us to remove a bunch
of global state previously needed to inspect whether a user set an argument
or not.

Full release notes are available at
https://github.com/certbot/certbot/releases

This update is being done per the permanent upgrade policy exception
granted by FESCo. [1]

As a side note I plan to update certbot in EPEL8 as far as dependencies
will allow, in the near future.

1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-226fa082a4
2.
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_other_packages

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

[EPEL-devel] Re: qbittorrent in EPEL9

[Jonathan Wright via epel-devel]

I want it just haven't had a chance to circle back.  I saw this email and
glanced back at it but I've been traveling this week.

I'll finish the EPEL request per docs this week and get this rolling.

On Fri, Nov 17, 2023, 09:04 Troy Dawson  wrote:

> It looks like Jonathan Wright was the person who first requested it, I
> don't know if he wants it or not..
> I find it interesting that the person who has been maintaining the package
> in Fedora for the past couple years isn't listed on the owners list.
>
> Doing some quick scratch builds, it looks like the latest version in
> Rawhide (qbittorrent-4.6.0-1.fc40) doesn't build on epel9
> _
>
> /usr/include/libtorrent/storage.hpp:5:2: error: #error "the disk I/O
> subsystem has been overhauled in libtorrent 2.0. storage_interface is no
> longer a customization point, customize disk_interface instead"
> 5 | #error "the disk I/O subsystem has been overhauled in libtorrent
> 2.0. storage_interface is no longer a customization point, customize
> disk_interface instead"
> _
>
> But, it looks like an older version (qbittorrent-4.4.1-1.fc34) builds fine.
>
> Just something to think about for whoever decides to take it.
>
> Troy
>
> On Thu, Nov 16, 2023 at 4:06 PM Palla Dium via epel-devel <
> epel-devel@lists.fedoraproject.org> wrote:
>
>> Hello,
>>
>> as per the EPEL package request documentation, I am kindly asking if
>> there are any packagers who would like to package and maintain qbittorrent
>> on EPEL. The request has been stalled since February 2023.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=2172281
>> https://src.fedoraproject.org/rpms/qbittorrent
>>
>> This would also require updating rb_libtorrent-devel to the latest
>> version: https://src.fedoraproject.org/rpms/rb_libtorrent
>>
>> Thank you very much.
>> --
>> ___
>> 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
>>
> --
> ___
> 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
>
--
___
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

[EPEL-devel] Re: Orphaning packages

[Jonathan Wright via epel-devel]

Lance,

I can sponsor/mentor you.  I'll reach out to ya via Mattermost.

On Tue, Jun 27, 2023 at 10:51 AM Lance Albertson  wrote:

>
>
> On Thu, Jun 22, 2023 at 9:50 AM Othman Madjoudj 
> wrote:
>
>> Hello,
>>
>> Please note that I've orphaned by packages, list in the end of the
>> message.
>>
>> Best regards
>> -Othman
>>
>>  rpms/mod_limitipconn
>>
>
> I'm interested in maintaining this but I am not a packager yet and would
> need to be onboarded if someone is willing to be a mentor.
>
> Thanks-
>
> --
> Lance Albertson
> Director
> Oregon State University | Open Source Lab
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[EPEL-devel] Re: KDE broken on CentOS Stream 9

[Jonathan Wright via epel-devel]

Thanks for all your work keeping KDE running for us EL folks!

On Wed, May 17, 2023 at 10:58 AM Troy Dawson  wrote:

> KDE is still not able to be upgraded in CentOS Stream 9.
> This is my fault.
> I tried to combine the rebuilds needed for the new qt5, with updating the
> rest of the KDE Plasma Desktop.  This didn't go well.
> I will be removing the updates from epel-next-testing and starting again
> with just the packages that need a rebuild due to the qt5 update.
>
> I'm sorry for the inconvenience, and appreciate the patience you have
> shown.
>
> Troy
>
> On Fri, May 5, 2023 at 7:11 AM Troy Dawson  wrote:
>
>> There is a new qt5 update in CentOS Stream 9.  This update will be going
>> out when RHEL 9.3 is released six months from now.  Again, that is RHEL
>> 9.3, NOT 9.2.
>>
>> I am currently rebuilding KDE for CentOS Stream 9.  This will take some
>> time to rebuild and make it through testing.  I am suspecting it will not
>> be in stable until May 18.
>>
>> It is a known issue that is being resolved.  No need for further bugs.
>> If you have already created a bug, please cc me (tdaw...@redhat.com) on
>> it, because most of the bugs do not get assigned to me.
>>
>> Thank You
>> Troy
>>
>> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[EPEL-devel] Re: Ansible in EPEL 9

[Jonathan Wright via epel-devel]

EPEL tracks RHEL, not clones.

EPEL10 is likely to resolve this, however.  Ref
https://discussion.fedoraproject.org/t/epel-10-proposal

On Mon, May 15, 2023 at 1:31 PM Leon Fauster via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:

> Am 10.05.23 um 05:24 schrieb Maxwell G:
> > Hello EPEL users and developers,
> >
> >
> > RHEL 9.2 was released today,
> > so I have updated ansible in EPEL 9 from 6.3.0 to 7.2.0 to match RHEL
> > 9.2's ansible-core bump from 2.13.3 to 2.14.2.
> > Each ansible major version is tied to a specific major version of
> > ansible-core, and we keep them in sync.
> >
> > Along with this change, RHEL 9.2 builds ansible-core for the python3.11
> > stack instead of the default python3 (3.9) stack.
> > Therefore, ansible in EPEL now built for python3.11 as well.
> >
> > Here is the Bodhi update:
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f51a0ff8a1
> > Please help test and give karma.
> >
> > Until this update is pushed to stable, you may receive an error like
> > this when running dnf upgrade
> >
> > ```
> > Error:
> >   Problem: package ansible-6.3.0-2.el9.noarch requires
> python3.9dist(ansible-core) >= 2.13.3, but none of the providers can be
> installed
> >- cannot install both ansible-core-2.14.2-4.el9.x86_64 and
> ansible-core-2.13.3-2.el9_1.x86_64
> >- cannot install both ansible-core-2.14.2-4.el9.x86_64 and
> ansible-core-2.13.3-1.el9.x86_64
> >- cannot install the best update candidate for package
> ansible-core-2.13.3-2.el9_1.x86_64
> >- cannot install the best update candidate for package
> ansible-6.3.0-2.el9.noarch
> > (try to add '--allowerasing' to command line to replace conflicting
> packages or '--skip-broken' to skip uninstallable packages or '--nobest' to
> use not only best candidate packages)
> > ```
> >
> > There are a couple potential solutions:
> >
> > 1. Run
> >   $ dnf upgrade --exclude ansible-core
> > to skip ansible-core and upgrade everything else.
> > 2. In a couple hours from from now (now is 3:15 UTC), you'll be able to
> install
> > ansible 7.2.0 from testing with
> >   $ dnf upgrade --refresh --enablerepo=epel-testing ansible
> ansible-core
> > and then run a plain `dnf upgrade` as usual.
> >
>
>
> While setting up a new workstation with an EL rebuild, I run into the
> situation that ansible is not installable (rocky still on 9.1). Is there
> a change from EPEL side to close this time gap by at least keep older
> packages (current-1) on the repos? Like epel-next closes the "forward"
> gap, this would close such "backward" gap, thought ...
>
> --
> Leon
>
>
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[EPEL-devel] Re: apptainer 1.1.8-1 has an incompatible change for apptainer-suid users

[Jonathan Wright via epel-devel]

Dave (Dykstra),

The process is pretty well laid out at
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/#process_for_incompatible_upgrades

I think leaving the package in epel-testing for now is OK but you
definitely need to hold it from release repos until the policy is followed
and the necessary approvals are obtained from the EPEL steering committee.

I can't currently find it in the docs but I think going ahead and opening
an issue at https://pagure.io/epel/issues will help facilitate the
process.  I'm quite sure that this is/was documented somewhere when
submitted an incompatible update for approval a few months back.  You can
see it at https://pagure.io/epel/issue/212 which might help make more sense
of the process as well.

On Wed, Apr 26, 2023 at 11:20 AM Dave Dykstra via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:

> DT is correct, this change is subject to the EPEL incompatible change
> policy.  apptainer-suid-1.1.8 by default disables mounting of ext3
> filesystems, because of CVE-2023-30549
>
> https://github.com/apptainer/apptainer/security/advisories/GHSA-j4rf-7357-f4cg
> Most users don't use this feature, but a significant minority does.
> Apptainer has a non-setuid alternative for the same functionality if
> unprivileged user namespaces are available.
>
> The summary of the CVE is that the way that apptainer & singularity
> allow mounts of ext3 filesystems in setuid mode raises the severity of
> many ext4 filesystem CVEs (ext3 filesystems are implemented by the ext4
> driver).  OS vendors consider those CVEs to be low or moderate priority
> because they assume that users do not have write access to the
> underlying bits of the filesystem, but apptainer/singularity setuid mode
> gives that access to users by default (before this release of apptainer).
> Since vendors don't see urgency to patch low/moderate CVEs, it can take
> a very long time for them to patch them and in fact RHEL7 is not patched
> for one in particular.  All this information came from a reliable source,
> the owner of the ext4 kernel driver.
>
> I am sorry to see that I have already done one step too many according
> to the incompatible changes policy, and have made the release available
> to epel-testing.  However, I think it's important to make it available
> that way for system administrators to install early.  The large High
> Energy Physics community that I represent has security teams that want
> to be able to notify their site administrators to upgrade to respond to
> this high severity CVE, and it would be so much better if the
> announcement they send can say to install from epel-testing rather than
> having to provide URLs to download from koji.
>
> So, to the EPEL Steering Committee members: must I unpublish this update
> from testing, or may I leave it there and send an announcement to
> epel-announce that it is there and pending approval by the committee?
> The bodhi settings are set so they won't get auto-updated by karma or
> time.
>
> And another question: should I submit an epel ticket for this?  The
> policy doesn't mention that.
>
> Dave
>
> On Wed, Apr 26, 2023 at 09:41:16AM +0100, David Trudgian wrote:
> > Subject: Re: apptainer 1.1.8-1 appears to be an incompatible upgrade for
> apptainer-suid users
> >
> > Hello,
> >
> > The maintainer of the apptainer package has submitted updates to version
> 1.1.8-1 against epel-testing:
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-18a0e3fa23
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-44ff2475c4
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-b31211e2ce
> >
> > I believe that the update should be considered an incompatible upgrade,
> requiring the incompatible upgrades policy to be followed, as it
> significantly changes behaviour for users who have the apptainer-setuid
> sub-package installed.
> >
> > The update now disallows, by default, workflows that involve ext format
> container images and overlays:
> >
> > ```
> > # Before update
> > $ apptainer exec sif-overlay.sif /bin/date
> > Wed Apr 26 09:12:37 BST 2023
> >
> > # Update to the testing package
> > $ sudo dnf update --enablerepo=epel-testing apptainer-suid
> >
> > # After update
> > $ apptainer exec sif-overlay.sif /bin/date
> > FATAL:   configuration disallows users from mounting SIF extfs partition
> in setuid mode, try --userns
> > ```
> >
> > I understand that the update is related to a security issue that
> upstream has published:
> >
> > CVE-2023-30549  -
> https://github.com/apptainer/apptainer/security/advisories/GHSA-j4rf-7357-f4cg
> >
> > However, I don't think this exempts the update from the incompatible
> upgrades policy?
> >
> > I'd also like to note that CVE-2023-30549 is dependent on and
> potentially a duplicate of CVE-2022-1184, which has been patched in EL8 and
> EL9, but admittedly not in EL7.
> >
> > Thanks,
> >
> > DT
> >
> >
> ___
> epel-devel 

[EPEL-devel] Re: Hints for manual upgrading from CentOS 8 Stream to CentOS / Alma / Rockey 9

[Jonathan Wright via epel-devel]

On Wed, Feb 8, 2023 at 3:23 PM Ian Laurie  wrote:

> On 2/9/23 07:38, Richard Shaw wrote:
> > I know upgrades are not supported but its for a small home server that
> > really only does two things:
> For a home server you can use RHEL, the real deal, why mess with
> downstream rebuilds?
>
>
Free or not, the licensing aspect is annoying and that's why many people
still choose rebuilds.


> Just a thought.
>
> Ian
> --
> Ian Laurie
> FAS: nixuser | IRC: nixuser
> TZ: Australia/Sydney
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[EPEL-devel] 'novnc' major version/breaking update in EPEL7

[Jonathan Wright via epel-devel]

Hi,

I intended to update novnc in EPEL7 to version 1.3.0 from 0.5.1.  I am
posting this here per EPEL policy and I've also posted an issue at
https://pagure.io/epel/issue/212 for discussion and the meeting agenda.

I recently took the novnc package which was orphaned and I'm trying to get
it cleaned up a bit. There is currently an open CVE for version 0.5.1 in
EPEL7: https://bugzilla.redhat.com/show_bug.cgi?id=1765662

The vulnerability was not fixed until 0.6.2 which already had breaking
changes from 0.5.1. https://github.com/novnc/noVNC/releases/tag/v0.6.2

There are no known backports of the fixes to 0.5.x and since the fixes were
during a very active time of development with many changes it would be
impractical to create and maintain such backports.

The releases after 0.6.2 do not cite breaking changes to libraries so I
think it makes sense to update to the currently supported upstream release
of 1.3.0.

The total breaking changes cited in changelogs between 0.5.1 and 1.3.0 are
as follows:
- 0.6.1: Warning: this release removes support for legacy browsers, namely
IE9 and below. IE10 may receive "best-effort" support. IE 11+, Edge,
Firefox 31+, and Chrome 44+ continue to be supported
- 0.6.1: Warning: this release includes a number of potentially breaking
changes to internal libraries
- 0.7.0: renamed vnc_auto.html to vnc_simple.html. We can maintain a
symlink to not break this functionality (only for EL7) until its EOL in
2024. https://github.com/novnc/noVNC/issues/695#issuecomment-300999837

RedHat's solution to the issue in their OpenStack product was to rebase to
1.1 (which at the time they rebased was the latest stable release).

https://access.redhat.com/errata/RHSA-2020:0754
https://bugzilla.redhat.com/show_bug.cgi?id=1484711


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[EPEL-devel] Re: Fwd: xscreensaver package for epel9 (Bugzilla 2120163)

[Jonathan Wright via epel-devel]

I replied to the BZ offering to package it in EPEL9.  Requester should get
copied on that.

On Mon, Sep 19, 2022 at 11:29 AM Troy Dawson  wrote:

> For those that are wondering, the latest version in rawhide build on epel9
> without any changes needed.
> So it should be fairly straightforward.
>
> Troy
>
>
> On Mon, Sep 19, 2022 at 4:20 AM Stephen Smoogen 
> wrote:
>
>>
>> This went to the mailing list admins versus the list. I don't think this
>> person is on the list so you will need to cc them an answer.
>>
>> -- Forwarded message -
>> From: metatron...@yahoo.com 
>> Date: Sun, 18 Sept 2022 at 20:01
>> Subject: xscreensaver package for epel9 (Bugzilla 2120163)
>> To: epel-devel-ow...@lists.fedoraproject.org <
>> epel-devel-ow...@lists.fedoraproject.org>
>>
>>
>> Hello EPEL Development Team,
>>
>> I was wondering if there are any packagers who would be willing to
>> package and maintain xscreensaver in EPEL9. I previously created a Bugzilla
>> ticket at https://bugzilla.redhat.com/show_bug.cgi?id=2120163. The
>> current package maintainer for Fedora is not able to maintain an EPEL
>> package (as noted in the comments of the ticket). Is there a packager who
>> would be willing to make xscreensaver available in EPEL9? Thank you so much
>> for your consideration!
>>
>> Regards,
>> metatron320
>>
>>
>>
>>
>> --
>> Stephen Smoogen, Red Hat Automotive
>> Let us be kind to one another, for most of us are fighting a hard battle.
>> -- Ian MacClaren
>> ___
>> 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
>>
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[EPEL-devel] Re: Request for backintime @EPEL9

[Jonathan Wright via epel-devel]

I replied to the BZ.  If the maintainer will add me then I'll package it.

On Sat, Jul 30, 2022 at 4:59 PM tas manian  wrote:

> Hi,
>
> would anyone be willing to package backintime (
> https://github.com/bit-team/backintime) in epel 9 or help get it in the
> existing package please? The current maintainer is unable to build the
> package for EPEL9 and I think backintime is a great tool for simple backups.
> Bugzilla-Request: https://bugzilla.redhat.com/show_bug.cgi?id=2106934
>
>
> Kind regards
>
> tasmanian
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Request for conky package (EPEL8)

[Jonathan Wright via epel-devel]

There is a path to successful builds that I've confirmed with mockbuilds.
I've made the necessary requests to help co-maintain these packages.  Since
the issue hasn't gotten traction anyway I wouldn't expect a response from
the current maintainer so it will be a few weeks before I can get builds
into epel-testing once I'm able to petition releng to be added as a
maintainer per packing guidelines.

On Wed, Jul 27, 2022 at 12:52 PM Alexander Barris via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:

> Great! It looks like Fedora 36 handles wireless-tools deprecation by
> turning off a build flag:
>
> https://src.fedoraproject.org/rpms/conky/c/2a0c7a0ed5318ccb471669a092bcad46872dc7a7?branch=f36
>
> Could something similar be done for EPEL8/EPEL9?
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Request for conky package (EPEL8)

[Jonathan Wright via epel-devel]

wireless-tools is deprecated so we'll need to figure out what will fit into
its place to let the package build.

tolua++ needs a little work to build on epel8 from the looks of it.  If I
can figure out the dep tree and get them building along with conky against
epel8 (I'll aim for epel9 too) then I'll submit the necessary requests to
help maintain the packages.

On Wed, Jul 27, 2022 at 12:10 PM Troy Dawson  wrote:

> I don't want to discourage anyone from taking this, but I just want to
> point out that conky requires wireless-tools and tolua++ to build.
> Neither of which is in epel8 or epel9.
>
>
> On Wed, Jul 27, 2022 at 9:44 AM Barris, Alexander J. [US-US] via
> epel-devel  wrote:
>
>> Hi all,
>>
>> Would someone be willing to package 'conky' for EPEL8?
>> We tried to request it in Bugzilla, but did not get a response from the
>> current Fedora/EPEL7 package maintainer.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1765376
>>
>> Thank you,
>> - Alex
>> ___
>> 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 on the list, report it:
>> https://pagure.io/fedora-infrastructure
>>
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Request for pure-ftpd package

[Jonathan Wright via epel-devel]

@Ming

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c42e39acb0

On Thu, Jul 21, 2022 at 10:28 AM Chris Adams  wrote:

> Once upon a time, Jonathan Wright  said:
> > On Thu, Jul 21, 2022 at 9:37 AM Chris Adams  wrote:
> > > Once upon a time, Jonathan Wright  said:
> > > > I've replied and offered to co-maintain the package.  If the current
> > > > maintainer doesn't reply in 2 weeks I'll petition releng to add me
> as a
> > > > co-maintainer per the packaging process guidelines for stalled EPEL
> > > > requests.
> > >
> > > If you do pick it up... looking at old pure-ftpd bugs, please see my
> > > comment in:
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=502754
> > >
> > >
> > Already working on some builds and reviewing that as well :)  Looks like
> > the packages needs some TLC in general.
>
> Cool, thanks!  I considered offering to co-maintain but I'm not sure I
> have the cycles to give it the TLC it should have.
>
> --
> Chris Adams 
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Request for pure-ftpd package

[Jonathan Wright via epel-devel]

On Thu, Jul 21, 2022 at 9:37 AM Chris Adams  wrote:

> Once upon a time, Jonathan Wright  said:
> > I've replied and offered to co-maintain the package.  If the current
> > maintainer doesn't reply in 2 weeks I'll petition releng to add me as a
> > co-maintainer per the packaging process guidelines for stalled EPEL
> > requests.
>
> If you do pick it up... looking at old pure-ftpd bugs, please see my
> comment in:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=502754
>
>
Already working on some builds and reviewing that as well :)  Looks like
the packages needs some TLC in general.
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Request for pure-ftpd package

[Jonathan Wright via epel-devel]

I've replied and offered to co-maintain the package.  If the current
maintainer doesn't reply in 2 weeks I'll petition releng to add me as a
co-maintainer per the packaging process guidelines for stalled EPEL
requests.

On Wed, Jul 20, 2022 at 11:27 PM Ming  wrote:

> Hi all,
>
> Would anyone be willing to package pure-ftpd in epel or help get it in the
> existing package please? Seems there is no response from current maintainer
> in bugzilla
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2095512
>
> Thanks
> Ming
> ___
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure