On Tue, Feb 4, 2020 at 12:37 AM Petr Pisar wrote:
>
> On Mon, Feb 03, 2020 at 02:35:43PM -0500, Stephen John Smoogen wrote:
> > My main job is working with Fedora Infrastructure, and we are trying to
> > work out how to handle:
> >
> > https://pagure.io/fedora-infrastructure/issue/8558
> >
> >
On Mon, Feb 3, 2020 at 12:29 PM Neal Gompa wrote:
>
> On Mon, Feb 3, 2020 at 2:36 PM Stephen John Smoogen wrote:
> >
> >
> > My main job is working with Fedora Infrastructure, and we are trying to
> > work out how to handle:
> >
> > https://pagure.io/fedora-infrastructure/issue/8558
> >
> > The
On Thu, Jan 30, 2020 at 6:21 AM Richard W.M. Jones wrote:
>
> MinGW is a Windows cross compiler for Fedora. There is a base
> toolchain like mingw-filesystem and mingw-gcc, and many cross-compiled
> libraries like mingw-glib2 which you can link with your programs to
> make Windows binaries, all
Hi Derek,
Maybe if you asked in the bug to be the maintainer of xlockmore for
epel8 they would grant that.
It's very likely that the owners of the package aren't actively
reading epel-devel.
On Sat, Dec 14, 2019 at 9:53 PM Derek Schrock
wrote:
>
> Would it be possible for someone to push
Thank you for letting us know.
The need to inform epel-devel of adding a package is only if the
package is a "Limited Arch" package. Since your package is a noarch
package, and thus will be available for all arches, you do not need to
inform us, nor wait for our approval.
Please proceed with the
On Mon, Dec 16, 2019 at 7:45 AM Yaakov Selkowitz wrote:
>
> On Mon, 2019-12-16 at 06:37 -0800, Troy Dawson wrote:
> > On Sat, Dec 14, 2019 at 10:31 AM Kevin Fenzi wrote:
> > > On Fri, Dec 13, 2019 at 09:19:16PM -0500, Mukundan Ragavan wrote:
> > > > It appears
On Sat, Dec 14, 2019 at 10:31 AM Kevin Fenzi wrote:
>
> On Fri, Dec 13, 2019 at 09:19:16PM -0500, Mukundan Ragavan wrote:
> > It appears that upower is in RHEL-8 but only in x86_64 and powerpc 64
> > architectures. Due to this, some of my builds fail. This one for example
> > -
On Wed, Dec 11, 2019 at 2:25 PM Troy Dawson wrote:
>
> Now that modules in epel are close to becoming reality [1] it has
> brought up a question.
> If it's already been asked and answered, please point me to it.
>
> If we are building a module, and one of the packages in tha
On Wed, Dec 11, 2019 at 2:25 PM Troy Dawson wrote:
>
> Now that modules in epel are close to becoming reality [1] it has
> brought up a question.
> If it's already been asked and answered, please point me to it.
>
> If we are building a module, and one of the packages in tha
that package in the module, and filter it
out, so that it is only used in the module?
Or, should we continue to wait for the solution to our missing devel
package problem.
Troy Dawson
[1] - Many thanks to Merlin and Mohan for their tremendous efforts
That is up to you. If you do a 'git merge master' and those three
files are removed, things will still build just fine in epel8.
If you want your package to build in both epel8 and epel8-playground
with each build, then you should leave package.cnf alone, or add it
later.
That is a personal
I believe the answer is "yes" ... to both.
As far as I know, there aren't any differences. Where there are
differences, we're trying to get rid of the differences.
Example is that the automatic python dependencies weren't turned on in
epel8. That should be fixed in a few days, so you should be
On Mon, Nov 18, 2019 at 7:25 AM Stephen John Smoogen wrote:
>
> On Mon, 18 Nov 2019 at 09:55, Troy Dawson wrote:
> >
> > Hi,
> > This has come up in multiple conversations, with no answer.
> >
>
> Honestly I don't think we ever came up with an idea of anyt
Hi,
This has come up in multiple conversations, with no answer.
With modularity coming up, I'm planning on transitioning KDE from
epel8-playground to regular epel8 modules.
I will have alot of packages that I no longer want in playground, but
don't want removed from epel8.
How do I do that?
My
Not sure why, but this was assigned to "Orphaned Owner".
In Fedora it was recently updated this last June, and has been rebuilt for F32.
Anyway, just letting people know, if they want to support this, it's
theirs for the taking.
Also, the only reason my name is anywhere near it was because I
Hi Denis,
On Wed, Nov 13, 2019 at 3:13 PM Denis Arnaud
wrote:
>
> Hi,
>
> the Python (3) bindings are missing on RHEL/CentOS/EPEL 8 for the protobuf
> package (https://src.fedoraproject.org/rpms/protobuf).
> A bug request has been created on Bugzilla
>
On Tue, Nov 5, 2019 at 11:01 AM Edward Diener
wrote:
>
> On 11/5/2019 12:11 PM, Troy Dawson wrote:
> > To get a package in EPEL8, please open a bugzilla to have it put in.
> > I just checked, and there currently isn't a bugzilla requesting it.
> > It will also need th
To get a package in EPEL8, please open a bugzilla to have it put in.
I just checked, and there currently isn't a bugzilla requesting it.
It will also need the following packages put into EPEL8 to build and
possibly run.
python3-cairosvg
python3-dnfdaemon
python3-notify2
python3-pystray
For KDE, I built all the packages in epel8-playground. At the time,
it seemed like the right thing to do. (Whether it was or not is
another discussion). I also built several packages in playground that
were not part of KDE, but were build and runtime dependencies.
Those non-KDE packages, I
ub.com/fedora-modularity/depchase?
> That basically does what you are doing and with some small changes it
> can perform much more things.
>
> On Tue, Oct 29, 2019 at 3:27 PM Troy Dawson wrote:
> >
> > On Mon, Oct 28, 2019 at 2:58 PM Peter Robinson wrote:
> > >
>
On Mon, Oct 28, 2019 at 2:58 PM Peter Robinson wrote:
>
> On Mon, Oct 28, 2019 at 8:00 PM Troy Dawson wrote:
> >
> > I would like to introduce a plan I call Square 1 [1][2]
> >
> > There are two goals to Square 1.
> > The first is to get, and keep, the c
laps with the Fedora Minimization efforts.[6]
Square 1 hopes to utilize, rather than duplicate, their efforts. And
maybe some tools created for Square 1 can help the minimization
efforts.
Thoughts?
Ideas?
Comments?
Troy Dawson
[1] - Square 1 is at the heart of Ring Zero
[2] - This has nothing to
giflib-devel is a sub-package of giflib.
It is already in RHEL8 and Centos8, just not in the BaseOS or AppStream repo's.
For CentOS 8 it is in the PowerTools repo
dnf config-manager --enable PowerTools
On Fri, Oct 25, 2019 at 1:29 PM Mateo wrote:
>
> Hi EPEL developers.
>
> I am using Centos
On Fri, Oct 25, 2019 at 2:28 PM BoBo Shaq wrote:
>
> I follow the procedure from this page:
> https://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL
> First, I was contact witch owner giflib package by the mail.
> He wrote me that he is not interested in maintaining the package.
>
No, libgdiplus-devel is a sub-package of libgdiplus.
libgdiplus is not found in RHEL8 or CentOS8, so you will need to
request it for epel8.
I'm not sure how you asked for giflib, but the best way is to open a
bugzilla bug requesting an epel8 build.
That way the request is able to be tracked.
Doing
On Fri, Oct 25, 2019 at 9:10 AM Richard Shaw wrote:
>
> On Fri, Oct 25, 2019 at 9:16 AM Troy Dawson wrote:
>>
>> All of the ones I've requested, I waited a few days to see if the
>> maintainer would pick it up. And after that I asked if they would
>> mind if I
All of the ones I've requested, I waited a few days to see if the
maintainer would pick it up. And after that I asked if they would
mind if I maintained it in EPEL8. About half of those the maintainer
was fine with me maintaining the package in EPEL8.
So, to answer your question, yes you can.
On Tue, Oct 22, 2019 at 5:06 AM Stephen John Smoogen wrote:
>
> On Tue, 22 Oct 2019 at 06:27, Tomas Krizek wrote:
> >
> > Hi,
> >
> > I'm trying to build lua-http package for EPEL8, which has lua-lpeg as a
> > dependency.
> >
> > While lua-lpeg was maintained in EPEL7, it was moved to the base
>
I say put them in the main EPEL 8, without modules.
They get built against the default RHEL8 ruby module.
When RHEL8 get's another ruby module, then we can create and EPEL8
rubygem module that works for that RHEL8 module.
But have all the rubygems in non-module EPEL8, be built against the
default
On Thu, Oct 10, 2019 at 7:46 AM Robert-André Mauchin wrote:
>
> On Wednesday, 9 October 2019 23:22:11 CEST Troy Dawson wrote:
> > * golang-*-devel (Not really broken, you should never need to install these)
> > ** I will not file bugzilla's on these. These -devel packages
-goraft-raft-devel
golang-github-rackspace-gophercloud-devel
golang-github-spacemonkeygo-spacelog-devel
golang-golangorg-oauth2-devel
golang-google-golangorg-cloud-devel
Troy Dawson
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
On Thu, Oct 3, 2019 at 7:54 AM Steve Siirila wrote:
>
> When will opendmarc fixes made nearly two years ago make it into EPEL for
> RHEL 7? We pretty much have had to hold off running it as it crashes
> whenever we receive email from a site with a malformed DMARC TXT record. A
> patch has
On Thu, Oct 3, 2019 at 7:05 AM Matthew Miller wrote:
>
> On Tue, Sep 24, 2019 at 02:54:26PM -0700, Kevin Fenzi wrote:
> > After the announcement today of centos-stream, I wonder if it would make
> > sense to move epel8-playground to build against that instead of the
> > latest rhel8 release?
>
>
On Thu, Sep 26, 2019 at 10:48 AM Robbie Harwood wrote:
>
> Pierre-Yves Chibon writes:
>
> > Here is what the vision we came to and that we would like to discuss:
> >
> > ○ Every changes to dist-git is done via pull-requests
> > ○ Pull-requests are automatically tested
> > ○ Every commit to
On Thu, Sep 26, 2019 at 6:56 AM Pierre-Yves Chibon wrote:
>
> On Thu, Sep 26, 2019 at 06:38:45AM -0700, Troy Dawson wrote:
> > On Thu, Sep 26, 2019 at 6:11 AM Pierre-Yves Chibon
> > wrote:
> > >
> > > On Thu, Sep 26, 2019 at 03:01:25PM +0200, Remi Collet
On Thu, Sep 26, 2019 at 6:11 AM Pierre-Yves Chibon wrote:
>
> On Thu, Sep 26, 2019 at 03:01:25PM +0200, Remi Collet wrote:
> > Le 26/09/2019 à 11:36, Pierre-Yves Chibon a écrit :
> > > Here is what the vision we came to and that we would like to discuss:
> > >
> > > ○ Every changes to dist-git is
On Thu, Sep 26, 2019 at 1:26 AM Petr Pisar wrote:
>
> On Wed, Sep 25, 2019 at 11:16:57AM -0700, Troy Dawson wrote:
> > On Wed, Sep 25, 2019 at 11:13 AM Troy Dawson wrote:
> > >
> > > On Wed, Sep 25, 2019 at 8:41 AM Stephen Gallagher
> > > wrote:
> >
On Wed, Sep 25, 2019 at 11:13 AM Troy Dawson wrote:
>
> On Wed, Sep 25, 2019 at 8:41 AM Stephen Gallagher wrote:
> >
> > On Tue, Sep 24, 2019 at 6:13 PM Neal Gompa wrote:
> > >
> > > On Tue, Sep 24, 2019 at 5:54 PM Kevin Fenzi wrote:
> > > >
On Wed, Sep 25, 2019 at 8:41 AM Stephen Gallagher wrote:
>
> On Tue, Sep 24, 2019 at 6:13 PM Neal Gompa wrote:
> >
> > On Tue, Sep 24, 2019 at 5:54 PM Kevin Fenzi wrote:
> > >
> > > After the announcement today of centos-stream, I wonder if it would make
> > > sense to move epel8-playground to
With the release of CentOS 8, and some testing, I have a few changes
to the installation instructions.
On Tue, Sep 3, 2019 at 2:01 PM Troy Dawson wrote:
>
> # KDE now available on EPEL 8 playground
>
> Many thanks to all those who have helped make this happen.
>
> ## Why playg
Actually, looking closer, there is not package called "vulkan".
So, not having 'vulkan-devel' is very logical.
For RHEL8 vulkan synced with F29, which split it's packaging up. In
vulkan's place is
vulkan-headers
vulkan-loader
vulkan-tools
vulkan-validation-layers
So, look what you would use in
Is this really an architecture variance?
Which architecture *has* vulkan-devel?
On Tue, Sep 24, 2019 at 2:18 PM Michael Cronenworth wrote:
>
> The lack of uniformity among arches on RHEL 8 is becoming annoying.
>
> The latest one is a head-scratcher:
>
> No matching package to install:
On Mon, Sep 23, 2019 at 10:53 AM Stephen John Smoogen wrote:
>
> On Mon, 23 Sep 2019 at 12:31, Thomas Stephen Lee wrote:
> >
> > Hi,
> >
> > download the tar version and extract
> >
> > https://download.teamviewer.com/download/linux/teamviewer_amd64.tar.xz
> >
> > cd to the folder
> >
> > run
>
On Fri, Sep 20, 2019 at 6:12 AM Troy Dawson wrote:
>
> On Thu, Sep 19, 2019 at 9:09 PM Orion Poplawski wrote:
> >
> > On 9/3/19 3:01 PM, Troy Dawson wrote:
> > > # KDE now available on EPEL 8 playground
> > >
> > > Many thanks to all those who
On Thu, Sep 19, 2019 at 9:09 PM Orion Poplawski wrote:
>
> On 9/3/19 3:01 PM, Troy Dawson wrote:
> > # KDE now available on EPEL 8 playground
> >
> > Many thanks to all those who have helped make this happen.
>
> Thanks!
>
> > [3] - Currently gdm does not
On Tue, Sep 17, 2019 at 10:34 AM Daniel Walsh wrote:
>
> On 9/17/19 8:04 AM, Colin Walters wrote:
> >
> > On Mon, Sep 16, 2019, at 12:45 PM, Troy Dawson wrote:
> >> systemd-sysusers seeks to unify user creation[1]. It also has the
> >> benefit of
in container needs to add a user, then
systemd is pulled in and that container grows by up to 60M.[2]
Minimizing containers, both in the short term and long term, are
important to the minimization team. We have opened an issue for
this.[3]
Any ideas on what we recommend to users?
Troy Dawson
[1
ng with modules,
you start with non-playground.
Option 3, I don't like. -testing should have nothing to do with
-playground. I'm not against the -playground packages going through
bodhi, but I am against modules going through bodhi, but regular rpm's
not going through it.
Troy D
# KDE now available on EPEL 8 playground
Many thanks to all those who have helped make this happen.
## Why playground only
KDE on EPEL 8 really needs to be in modules.[1] So we don't have to
pull all the KDE packages out of normal EPEL8, we have chosen to only
have them in EPEL8 playground,
On Wed, Aug 28, 2019 at 1:19 AM Petr Pisar wrote:
>
> On Wed, Aug 28, 2019 at 09:15:47AM +0200, Mikolaj Izdebski wrote:
> > Fedora infrastructure has been asked [1] to enable Koschei [2] for
> > EPEL 8. Would this be useful to anyone?
>
> Yes.
>
> > If yes, which of build targets
> >
On Fri, Aug 23, 2019 at 8:21 AM Stephen John Smoogen wrote:
>
> On Fri, 23 Aug 2019 at 11:03, Paul Howarth wrote:
> >
> > The EL-8 non-default repo Code Ready Builder is primarily targeted at
> > developers, but it looks to me like it's going to be a required repo
> > for a lot of EPEL-8 users,
On Sun, Aug 25, 2019 at 2:05 PM Stephen John Smoogen wrote:
>
> On Sun, 25 Aug 2019 at 08:31, Mukundan Ragavan wrote:
> >
> > The package "itstool" seems to be missing in some architectures (s390x
> > and aarch64) although it should be provided by RHEL server rpms. It
> > appears to be available
On Fri, Aug 23, 2019 at 5:27 AM Stephen John Smoogen wrote:
>
> The following answers are just my opinions and not policy.
>
> On Fri, 23 Aug 2019 at 06:52, Petr Pisar wrote:
> >
> > Case: RHEL delivers an M module with no default stream, there is no S
> > stream.
> > Can I add a new S stream
epel8-playground
> > issue. I wonder how many other people had or will have the same
> > problem. I assume this is going to fix the problem and if not I will
> > follow up.
> >
> > Thanks,
> >
> > Dave
> >
> > On Thu, Aug 15, 2019 at 06:25:41AM -07
On Fri, Aug 16, 2019 at 12:40 AM Vitaly Zaitsev via devel
wrote:
>
> On 16.08.2019 6:22, Richard Shaw wrote:
> > I assume this is because LibRaw is available in RHEL but only for x86_64
> > and ppc64le?
>
> The same as Pidgin and lots of other apps/libs. You need to add
> "ExclusiveArch: x86_64
Note: I am not an expert of gcc-objc.
I just see that it wasn't built with the RHEL8 gcc and I'm answering
accordingly.
Someone else might have different, better answers.
On Thu, Aug 15, 2019 at 9:14 AM Orion Poplawski wrote:
>
> What to do about missing gcc-objc from RHEL8?
Open a customer
Oh ... then there really is a problem. 12 hours (or longer) is a very
long time for a package to not make it into the repo. The longest I
had to wait was 4 hours, because I was doing things in the middle of
the F31 mass rebuild.
I'm afraid helping with this is above my fedora permissions. I
cted] HEAD -> epel8-playground (pre-receive hook declined)
> error: failed to push some refs to
> 'ssh://d...@pkgs.fedoraproject.org/rpms/singularity.git'
> Could not execute push: Failed to execute command.
>
> Dave
>
> On Mon, Aug 12, 2019 at 02:47:08PM -0700, Troy Dawson
On Wed, Aug 14, 2019 at 6:39 AM Troy Dawson wrote:
>
> On Wed, Aug 14, 2019 at 6:36 AM Stephen John Smoogen wrote:
> >
> >
> >
> > On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote:
> >>
> >> I have hdf5 (amongst others) in a buildroot override b
On Wed, Aug 14, 2019 at 6:36 AM Stephen John Smoogen wrote:
>
>
>
> On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote:
>>
>> I have hdf5 (amongst others) in a buildroot override but when I tried to
>> build OpenImageIO I got the following errors in root.log:
>>
Where is the link to that
On Tue, Aug 13, 2019 at 5:22 AM Mattias Ellert
wrote:
>
> Hi!
>
> I recently had a discussion about the use of the playground on
> pagure.io: https://pagure.io/releng/issue/8582
>
> I was asked to bring the discussion here to epel-devel.
>
> I quote my last comment from the thread below. If you
Looks like you need at least fedpkg-1.37-3.el7 for it to work with the
playground stuff, so you should be good.
When I did the branches for KDE (about 350 of them) there were 6 that
didn't properly branch to epel8-playground.
They *said* they were branched, but they weren't.
I was able to push and
/koji/buildinfo?buildID=991833
If the arch you want it x86_64, here is the link (so you don't have to
go to the build page first)
https://kojipkgs.fedoraproject.org//packages/partclone/0.3.11/1.el7/x86_64/partclone-0.3.11-1.el7.x86_64.rpm
If you need so
On Wed, Aug 7, 2019 at 8:44 AM Pablo Sebastián Greco
wrote:
>
>
> El 7/8/19 a las 12:30, Stephen John Smoogen escribió:
>
>
>
> On Wed, 7 Aug 2019 at 10:52, Vitaly Zaitsev via devel
> wrote:
>>
>> Hello all.
>>
>> While building my Fedora packages for EPEL8, got a very strange error on
>>
On Wed, Aug 7, 2019 at 8:44 AM Pablo Sebastián Greco
wrote:
>
>
> El 7/8/19 a las 12:30, Stephen John Smoogen escribió:
>
>
>
> On Wed, 7 Aug 2019 at 10:52, Vitaly Zaitsev via devel
> wrote:
>>
>> Hello all.
>>
>> While building my Fedora packages for EPEL8, got a very strange error on
>>
oing EPEL stuff), but I feel it would fit in
with my RHEL9 and Fedora IoT efforts. Plus, I'm always trying to get
installs and systems as small as possible.
Troy Dawson
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
On Thu, May 30, 2019 at 12:18 PM Kevin Fenzi wrote:
>
> > As discussed in the EPEL SIG meeting yesterday, I've written up my
> > thoughts on how to handle epel8 branches.
>
> TLDR: I like it. ;)
>
> > # Considerations
> > * The process must be simple for a Fedora packager to adapt to
> > * It
On Thu, May 16, 2019 at 6:50 PM Chris Adams wrote:
>
> Once upon a time, Stephen John Smoogen said:
> > RHEL-8 was built with various packages which are not shipped in
> > BaseOS/AppStream/CRB. Some like screen are in the buildroot for the
> > packages which depend on them but were decided not
On Thu, May 9, 2019 at 12:38 PM Orion Poplawski wrote:
>
> On 5/8/19 4:09 PM, Troy Dawson wrote:
> > On Fri, Jan 18, 2019 at 9:03 AM Troy Dawson wrote:
> >>
> >> I have uploaded my build to my fedora people area. Unfortunately the
> >> source rpm's w
the latest, and "other" python
version (python3_other_pkgversion), then that package now has
python34- and python36-
What to do?
Open a bugzilla on the package, requesting that it be fixed so it
builds for both versions of python.
Troy Dawson
tdisco-1.1-1.el6"]
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2011-4742
2011-12-31 19:07:08 ["trac-peerreview-plugin-0.11-5.svn11062.el6"]
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2012-0004
Troy Dawson
epel-list-2012
Description: Binary data
epel-list-2014
Des
Yes.
There are several of us that are KDE users (Well, I am, and I assume
there are others).
It will probably be a case of figuring out who is the maintainer or if
we do it as a group.
There are a few of us who have rebuilt it already for RHEL8 Beta. As
far as I know, I am the only one who is
On Tue, Mar 12, 2019 at 9:56 AM Troy Dawson wrote:
>
> The epel7 python rebuild has finished. All of the resulting packages
> are now in Bohdi updates.
> They will remain in updates until at least April 2.
> They have not made it into epel-testing yet.
> Due to a Bohdi bug [1
The epel7 python rebuild has finished. All of the resulting packages
are now in Bohdi updates.
They will remain in updates until at least April 2.
They have not made it into epel-testing yet.
Due to a Bohdi bug [1], we had to break up the updates. So we now
have 6 updates, that we will treat as
On Mon, Mar 11, 2019 at 9:42 AM Miro Hrončok wrote:
>
> On 11. 03. 19 15:54, Troy Dawson wrote:
> > On Sat, Mar 9, 2019 at 8:16 PM Kevin Fenzi wrote:
> >>
> >> On 3/9/19 7:15 PM, Troy Dawson wrote:
> >>> Hello,
> >>> There are a fe
On Sat, Mar 9, 2019 at 8:16 PM Kevin Fenzi wrote:
>
> On 3/9/19 7:15 PM, Troy Dawson wrote:
> > Hello,
> > There are a few questions I have, and since I'm not positive who all
> > of the correct people ask are, I'm sending to the epel-devel list.
> >
> > Bef
On Sat, Mar 9, 2019 at 8:19 PM Kevin Fenzi wrote:
>
> On 3/9/19 7:16 PM, Troy Dawson wrote:
> > On Sat, Mar 9, 2019 at 9:47 AM Benjamin Pereto
> > wrote:
> >>
> >> Hi,
> >>
> >> I saw that you rebuilt borgbackup (
> >> ht
On Sat, Mar 9, 2019 at 9:47 AM Benjamin Pereto wrote:
>
> Hi,
>
> I saw that you rebuilt borgbackup (
> https://apps.fedoraproject.org/packages/borgbackup) for python3.6.
>
> thanks for that!
>
> Now I wanted to build a new package with the new upstream release and ran in
> some issues to deploy.
Hello,
There are a few questions I have, and since I'm not positive who all
of the correct people ask are, I'm sending to the epel-devel list.
Before I start the questions, thank you to everyone who helped out in
getting the build failures working. Thank you. thank you. thank you.
We have all
On Fri, Feb 15, 2019 at 8:34 AM Stephen John Smoogen wrote:
>
> On Fri, 15 Feb 2019 at 09:39, Troy Dawson wrote:
> >
> > I want to make sure I'm reading this right.
> > A packager puts a package into EPEL.
> > If the user does nothing, that package continues to be i
I want to make sure I'm reading this right.
A packager puts a package into EPEL.
If the user does nothing, that package continues to be in EPEL.
If the user wishes to end support, they sent off and email, compose
one final build (if it can compose), wait for it to land, then send
off another
There are a set of packages in EPEL7 that have been obsoleted by other
packages (mostly) in EPEL7. Many have been obsoleted for several
years. I would like permission to remove these obsoleted packages,
similar in the way that I cleaned up many of the failed to install
packages.
I will open a
On Sun, Nov 18, 2018 at 11:00 AM Kevin Fenzi wrote:
>
> On 11/17/18 4:09 PM, Orion Poplawski wrote:
>
> > I'm afraid I'm still very unfamiliar with modules, but it does seem like
> > this will be very central to how we deliver packages to EPEL-8. My
> > initial questions are:
>
> Yeah, I don't
My apologies for delaying my work on this.
Priorities got shifted so I'm starting this work today.
On Wed, Nov 14, 2018 at 10:50 AM Stephen John Smoogen wrote:
>
> On Wed, 14 Nov 2018 at 13:00, Troy Dawson wrote:
> >
> > Here are the list of packages with bad dependenc
bug.cgi?id=1647581
- No Comment
xfce4-vala https://bugzilla.redhat.com/show_bug.cgi?id=1647569
- Rebuilt - On QA
On Thu, Nov 8, 2018 at 1:35 PM Troy Dawson wrote:
>
> On Wed, Nov 7, 2018 at 12:56 PM Troy Dawson wrote:
> >
> > Hi,
> > I'm going through the lists o
On Wed, Nov 7, 2018 at 12:56 PM Troy Dawson wrote:
>
> Hi,
> I'm going through the lists of EPEL7 packages that are not able to be
> installed on RHEL 7.6, and opening bugzilla's for them. I am keeping
> track of all those bugs with a tracker bug.[1]
> My apologies t
Hi,
I'm going through the lists of EPEL7 packages that are not able to be
installed on RHEL 7.6, and opening bugzilla's for them. I am keeping
track of all those bugs with a tracker bug.[1]
My apologies to the epel-release maintainers for using their package
for the tracker.
I've only created 6
On Thu, Jan 11, 2018 at 11:55 PM, Panu Matilainen <pmati...@redhat.com> wrote:
> On 01/12/2018 06:08 AM, Luya Tshimbalanga wrote:
>>
>> On 2018-01-11 01:02 PM, Troy Dawson wrote:
>>>
>>> Hello,
>>> Python3 will be in the next major RHEL release. I
Hello,
Python3 will be in the next major RHEL release. I don't mean RHEL
7.6, but with numbers higher than 7.
There are many, many packages with something like the following
if 0%{?fedora}
%define with_python3 1
%endif
If you have something like that, please change it to something like
and then make one tweek [2] to the spec file
to get it to build on RHEL7.
I have uploaded my built packages incase others want to try them on
rhel7. [1]
One feature that I think would be nice, would be to make it easy to
find, setup and connect to localhost connections.
Keep up the good work.
Troy Dawson
On 01/09/2015 02:41 PM, Troy Dawson wrote:
Hi,
I will be taking ownership of html2text on EPEL6.
I am already the maintainer for EPEL7, but I missed the notification
that the EPEL6 version was being orphaned because of filters.
Troy Dawson
Hi All,
This has turned out to be much more
On 02/25/2015 10:23 AM, Vít Ondruch wrote:
Dne 25.2.2015 v 17:18 Troy Dawson napsal(a):
On 01/09/2015 02:41 PM, Troy Dawson wrote:
Hi,
I will be taking ownership of html2text on EPEL6.
I am already the maintainer for EPEL7, but I missed the notification
that the EPEL6 version was being
Hi,
I will be taking ownership of html2text on EPEL6.
I am already the maintainer for EPEL7, but I missed the notification
that the EPEL6 version was being orphaned because of filters.
Troy Dawson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo
rubygem-openshift-origin-dns-bind
rubygem-openshift-origin-dns-nsupdate
rubygem-openshift-origin-msg-broker-mcollective
rubygem-openshift-origin-node
I will also go through and make sure any pending review requests are
closed as well.
Please let me know if there are any questions.
Thanks
Troy Dawson
?
--- Is there an easy to find option to turn them off/on?
Thanks
Troy Dawson
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1074600
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On 06/27/2014 09:17 AM, Rahul Sundaram wrote:
Hi
On Fri, Jun 27, 2014 at 10:07 AM, Troy Dawson wrote:
The fact that Fedora practically forces people to use delta rpm's has
rattled my cage for quite a while.
[Snipped]
--- Does it force you to do them like yum does
On 06/27/2014 10:45 AM, Rahul Sundaram wrote:
Hi
On Fri, Jun 27, 2014 at 11:26 AM, Troy Dawson wrote:
It is a hidden default that is not in any man page or documentation.
Yes, I used a poor choice of words.
man yum.conf
deltarpm
When non-zero, delta
.
Troy Dawson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Hello,
I only had positive tests from everyone, so I have marked
mongodb-2.4.6-1.el6 as stable.
It usually takes a few days for it to make it into the repo and pushed
out to the mirrors. So expect it within a week.
Thank You
Troy Dawson
On 09/23/2013 03:49 PM, Troy Dawson wrote:
Hello
Troy Dawson
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
401 - 500 of 517 matches
Mail list logo
