Steve,
On Fri, 2024-04-19 at 12:28 -0400, Steve Grubb wrote:
> Hello,
>
> I have run into an issue on F39 that I wanted to ask about. I decided
> that I
> wanted to develop an application on github from another account to
> simplify
> which keys are being used. I created the user acct and used
On Mon, 2024-02-05 at 19:11 -0700, Christoph Junghans wrote:
> Hi,
>
> Has anybody seen this error before:
> FEDORA-2024-310c0537ac ejected from the push because "Cannot find
> relevant tag for gromacs-2023.4-1.fc39. None of ['f39-updates',
> 'f39-updates-pending'] are in ['epel9-next-testing',
On Wed, 2023-01-04 at 23:41 +0100, Miro Hrončok wrote:
> On 02. 12. 22 18:20, Jakub Kadlcik wrote:
> > Hello folks,
> >
> > for a couple of years now, I've been interested in the Fedora
> > package
> > review process. Our queue is in hundreds of waiting packages for as
> > long as I can remember.
On Fri, 2022-12-30 at 00:59 -0500, Nico Kadel-Garcia wrote:
> On Wed, Dec 28, 2022 at 7:01 AM Ralf Corsépius
> wrote:
> >
> > Am 28.12.22 um 11:49 schrieb Peter Boy:
> > >
> > > It is a good idea to make the timeout configurable. But the
> > > default timeout for servers must remain unchanged.
On Wed, 2022-12-28 at 13:00 +0100, Ralf Corsépius wrote:
>
>
> Am 28.12.22 um 11:49 schrieb Peter Boy:
> >
> > It is a good idea to make the timeout configurable. But the
> > default timeout for servers must remain unchanged.
>
> My problem is not "defined timeouts" it is systemd delaying
Folks,
I'm currently reviewing a package (c-icap - BZ2119983) which uses
Berkeley DB, a product that is now marked as deprecated.
Currently the packager has decided to bundle BDB into the package, as
it is the only way to get around the issue, but given that BDB looks
like it will be around for
On Sun, 2022-12-18 at 16:07 +0100, Vitaly Zaitsev via devel wrote:
> On 18/12/2022 12:20, Frank Crawford wrote:
> > Can anyone explain what is going on?
>
> Fedora no longer has i686 mirrors, so COPR or mock use Koji's
> buildroot.
> It was recently removed due to F35 EOL
Folks,
I'm trying to build a package (rdiff-backup) for multiple architectures
and releases of Fedora, and all of them work, except fedora-35-i686,
which comes up with the following complaint:
This system is not registered with an entitlement server. You can use
subscription-manager to
On Sun, 2022-09-04 at 17:18 -0700, Kevin Fenzi wrote:
> On Sat, Sep 03, 2022 at 08:32:47PM +1000, Frank Crawford wrote:
> >
> > The document I used
> > was https://docs.fedoraproject.org/en-US/package-
> > maintainers/Package_Update_Guide/#multiple_packages
> >
Kevin,
On Mon, 2022-08-29 at 13:07 -0700, Kevin Fenzi wrote:
> On Sun, Aug 28, 2022 at 07:38:31PM +1000, Frank Crawford wrote:
...
> >
> > I think you answered my issue here, I did not allow sufficient time
> > for
> > the repo to refresh before
On Sat, 2022-08-27 at 14:58 -0500, Maxwell G via epel-devel wrote:
> n 22/08/27 04:03PM, Frank Crawford wrote:
> > While building two related new packages for EPEL9 with a
> > chainbuild,
> > the second one failed, however, now I am trying to work out how to
> > sp
While building two related new packages for EPEL9 with a chainbuild,
the second one failed, however, now I am trying to work out how to
specify the completed package in the build for the second package.
I have tried creating a side-tag and add the completed build to the
side-tag, then building
On Sat, 2022-01-22 at 21:35 -0500, Neal Gompa wrote:
> On Sat, Jan 22, 2022 at 9:28 PM Frank Crawford
> wrote:
> >
> > Folks,
> >
> > Any idea what is going on here? I'm trying to push an update for a
> > package (s3cmd) to EPEL9. The original package
Folks,
Any idea what is going on here? I'm trying to push an update for a
package (s3cmd) to EPEL9. The original package worked fine a few weeks
ago, but this fix is being failed after a day or so sitting testing
state with the following message:
bodhi - 2022-01-23 02:00:24.585391 (karma: 0)
On Thu, 2022-01-06 at 08:10 -0600, Michael Cronenworth wrote:
> On 1/6/22 7:53 AM, Chris Adams wrote:
> > ifcfg scripts don't run an RA server. You can set signaling radvd,
> > which can also be done with NM dispatcher scripts (which would be
> > much
> > more flexible, since it wouldn't be
On Mon, 2021-12-13 at 06:18 -0500, Neal Gompa wrote:
> On Mon, Dec 13, 2021 at 6:13 AM Troy Dawson
> wrote:
> >
> >
> >
> > On Sat, Dec 11, 2021 at 1:58 AM Frank Crawford
> > wrote:
> > >
> > > Folks,
> > >
> &g
Folks,
I'm looking at building a package that currently exists in EPEL8 for
EPEL9. I have a new branch epel9 branch for my package, but when I try
to do a mock build or scratch build it fails with the error:
Error: Error downloading packages:
Status code: 404 for
On Mon, 2021-08-30 at 12:35 -0700, Gordon Messmer wrote:
> On 8/30/21 12:08 PM, Hans de Goede wrote:
> >
> > I checked the entry on a Windows multiboot system and it does not
> > have the
> > "insmod chain" line, maybe droppint that helps?
>
>
> Same result. GRUB returns immediately to its
On Thu, 2020-10-29 at 11:20 +0100, Jan Synacek wrote:
> I orphaned my packages, feel free to take them:
...
> https://src.fedoraproject.org/rpms/logwatch
Thanks for your efforts Jan.
Since I'm involved upstream with logwatch, I've taken this on.
RegardsFrank
>
> On Mon, Apr 20, 2020 at 6:33 AM Frank Crawford <
> fr...@crawford.emu.id.au> wrote:
> > We have pushed into testing and intend to eventually release a new
> > version of rdiff-backup which has a significant incompatibly with
> > the current distributed version
repositories.
If you have any questions about the update, please contact me.
Frank Crawford
FAS: frankcrawford
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora
Folks,
I did a new build to add sysusage to EPEL8 the other day, and pushed it
to bodhi, and today received the following message:
bodhi - 2019-12-27 20:13:12.706366 (karma: 0)
FEDORA-EPEL-2019-e249fc2a74 ejected from the push because "Cannot find
relevant tag for sysusage-5.7-6.el8. None of
In preparation for the move of rdiff-backup to python3, we have built
the current beta for rawhide.
In addition to allow testing over older systems, we have also created a
COPR repo, for F29, F30, F31, EPEL7 and EPEL8 for all support
architectures. This can be accessed as "dnf copr enable
On Sat, 2018-12-01 at 10:12 -0500, Nico Kadel-Garcia wrote:
> On Sat, Dec 1, 2018 at 6:59 AM Frank Crawford
> wrote:
>
> On Sat, 2018-12-01 at 11:38 +, Zbigniew Jędrzejewski-Szmek wrote:
>
> On Sat, Dec 01, 2018 at 10:14:14PM +1100, Frank Crawford wrote:
>
> On
On Sat, 2018-12-01 at 11:38 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Sat, Dec 01, 2018 at 10:14:14PM +1100, Frank Crawford wrote:
> On Fri, 2018-11-30 at 14:15 +0100, Miro Hrončok wrote:
>
> Anyone know why this was orphaned? There doesn't seem to be any
> message about
On Fri, 2018-11-30 at 14:15 +0100, Miro Hrončok wrote:
Anyone know why this was orphaned? There doesn't seem to be any
message about it.
> s3cmd orphan 0 weeks ago
If no one has any idea I'm willing to take it on.
Regards
Frank
___
devel mailing
On Sun, 2018-01-07 at 06:41 +, Peter Robinson wrote:
> On Sun, Jan 7, 2018 at 1:31 AM, Frank Crawford <fr...@crawford.emu.id
> .au> wrote:
> > Folks,
> >
> > Sorry to drop this in here, but I've can't find where else it could
> > go. I'm
> > the mai
Folks,
Sorry to drop this in here, but I've can't find where else it could go.
I'm the maintainer for sysusage, which was un-retired mid 2017, around
the time of conversion to pagure.io for packages.
The builds for F25 & F26 worked fine, and I assumed it would roll over
to F27, etc, but I find
Folks,
I'd like to unretire SysUsage, which was retired 2015-05-19, partly due
to the mass retirement of Christoper Meng and partly due to a hiatus in
development upstream.
However, as upstream has restarted development, with two releases in
the ahead of the retired version, and an
29 matches
Mail list logo
