As we discussed during last meeting, here is a poll to check if there is a
timeslot that can fit more of the people that are currently interested to
participate in the EPEL Steering Committee Meeting.
https://whenisgood.net/EPEL_Steering_Committee_2024
What day and time would you like? Paint
What I usually do when I need for COPR to handle rpmautospec is to set
the source type to "Custom", and use the following script:
#! /bin/sh -x
git clone
cd
spectool -g
rpmautospec process-distgit
Set the Buildroot dependencies to "git rpmdevtools rpmautospec" and
the Result directory to
duration of the survey for now.
On Sat, Sep 2, 2023 at 6:26 AM Michael J Gruber wrote:
>
> Am Fr., 1. Sept. 2023 um 22:09 Uhr schrieb Stephen Smoogen
> :
> >
> >
> >
> > On Fri, 1 Sept 2023 at 16:03, Diego Herrera wrote:
> >>
> >> Hello, everyone
>
Hello, everyone
The Fedora EPEL SIG is asking for feedback to improve EPEL via this survey!
* https://fedoraproject.limequery.com/2023
The survey is targeting EPEL users and contributors. It asks about
how you use EPEL, how you contribute to it, and on what would you need
to improve that
Hi
There should be no problems from opentoonz packaging side, and if there
are, i'll deal with them ;)
Keep up the good work!
On Thu, May 4, 2023 at 7:24 AM Petr Pisar wrote:
> V Thu, May 04, 2023 at 11:05:21AM -, Artur Frenszek-Iwicki napsal(a):
> > > "dnf repoquery --srpm --whatrequires
I have a roundabout way to make COPR and rpmautospec work with any git repo :)
1. Create a new COPR project
2. Add a new COPR package with source type Custom
- Script
#! /bin/sh -x
git clone
cd
spectool -g
#other stuff you need to prepare
rpmautospec process-distgit
- Build dependencies:
I've been checking the packages that won't install on EPEL [1] and found out
that drbd-pacemaker cant get installed
because of a missing dependency (pacemaker). While researching why, I saw that
pacemaker exists on EPEL7 because it's
provided by the HighAvailability repo, but by policy [2] that
Honestly didn't thought that it could be an option. I'll check that path and
see how it goes.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
it's just a
roundabout way to get the same result.
Is any of these approaches viable from a policy perspective? Is there a
better way to do this? Or should I desist on packaging this project on
Fedora for now?
[1] https://github.com/Genymobile/scrcpy
Best regards.
--
Diego Herrera C
Hello everyone
My name is Diego Herrera, I'm a 35 y/o software developer and a recent hire
at Red Hat CPE Team. I've been actively using Fedora as my workstation
prefered OS since version 16.
I have made a couple of contributions to OSS projects in the past and have
some experience
10 matches
Mail list logo
