(FEDORA-EPEL-2017-c5103075f3)
> A simple mechanism to assemble Java archives
>
>
> Update Information:
>
> Package shrinkwrap java library for EPEL7
>
> ----
On Wed, Nov 2, 2016 at 3:23 PM Jason L Tibbitts III <ti...@math.uh.edu>
wrote:
> >>>>> "C" == Christopher <ctubb...@fedoraproject.org> writes:
>
> C> Also, after taking a package, how does one check to see if all of its
> C> dependenci
On Tue, Nov 1, 2016 at 3:00 PM wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for
> sure
> that the package should be retired, please do so now with a proper reason:
>
On Wed, Jan 10, 2018 at 1:53 AM Ding Yi Chen wrote:
> I received a bug[1] asking to remove EPEL7 branch, as the package
> LibRaw, is already in RHEL.
>
> How should I do that?
>
>
Would (warning: this will lose history) `git push --delete origin epel7`
work? It'd be a shame to
RHN is RHN, but not EPEL.
http://pkgs.org/search/?keyword=sun-codemodel
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Hi all,
dropbear in EPEL6 will be updated to 2013.62 later in updates-testing
with support of ECC.
Full changelog is there: https://matt.ucc.asn.au/dropbear/CHANGES
If you have any questions or objections, please reply here.
Thanks.
--
Yours sincerely,
Christopher Meng
Fєdоґa ї₴ al$о a кїпd
Hi,
I've created this package since 1.3.6 in EPEL branch so sysadmins you
can use this awesome tools to check your system's security via `sudo
yum install lynis`. Note please don't rely on this software blindly.
Thanks.
--
Yours sincerely,
Christopher Meng
Fєdоґa ї₴ al$о a кїпd оf нaт lїкє Яёd
branch from EPEL6?
How to deal with systemd related things?
Is it possible to branch from branches determined by packagers?
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Wed, Dec 18, 2013 at 6:58 AM, Morten Stevens
mstev...@fedoraproject.org wrote:
My preference is also el7, because we have also a Packager and Vendor
tag to declare these packages as Fedora EPEL (and not rhel) packages.
Why should these 2 tags be used still?
Hi,
I wonder if I need to add epel7 to the branch list or the system will do for me?
I want to package for epel7 also.
Thanks.
--
Yours sincerely,
Christopher Meng
Noob here.
http://cicku.me
___
epel-devel mailing list
epel-devel
On Jan 3, 2014 1:02 AM, Kevin Fenzi
When we are ready for branches we will announce and that will include
the process and what you need to do.
Thanks, but what I've seen is that someone is requesting SCM on epel7. I
was just curious about that.
___
I'm the i3* maintainer now.
I will do this of course, but before RHEL7 pushed to final release, please
don't rush.
Thanks.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
I would suggest you using pip to install these packages.
First these packages in repo are old and may not match your need.
https://bugzilla.redhat.com/show_bug.cgi?id=852998
Second these packages are used for Fedora infrastructure apps, and since
the technology is moving forwardly, these
I've taken the acl.
Thanks.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
a question, what's the difference between
RHEL(CentOS) and Amazon?
Thanks.
Yours sincerely,
Christopher Meng
Noob here.
http://cicku.me
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel
On Fri, May 9, 2014 at 9:57 AM, Matthew Miller mat...@fedoraproject.org wrote:
Quite a lot; they make no attempt at compatibility. I think I'd respond with
that. EPEL packages might work on Amazon Linux, and they might not.
Matthew, thanks for your reply.
I took the info from the bug, and
NO.
Feel free to do that.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
You'd better open a bug in the bugzilla under Fedora EPEL against the
relevant component if it is available in the EPEL6.
If not, open a bug under Fedora and request the epel7 branch.
Thanks.
___
epel-devel mailing list
Hi all,
I strongly suggest that please also update this package to the latest
version 4.39 instead of using 4.38.
Thanks.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Wed, Jul 9, 2014 at 4:02 PM, Jens Petersen peter...@redhat.com wrote:
I strongly suggest that please also update this package to the latest
version 4.39 instead of using 4.38.
What is the advantage of 4.39? It is not in rawhide yet though...
Version 4.39:
- Added ballot, checkmark, heavy
this rpm to repo line. thanks,
Have you checked?
http://koji.fedoraproject.org/koji/buildinfo?buildID=543666
Yours sincerely,
Christopher Meng
http://cicku.me
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org
Deps are satisfied already based on the successful build of the thunar.
http://koji.fedoraproject.org/koji/buildinfo?buildID=543669
Thanks for the report.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
makes the
broken xfdesktop in the EPEL7, so he will fix it soon.
There are some xfce guys in this list, you can await their answers.
Thanks.
Yours sincerely,
Christopher Meng
http://cicku.me
___
epel-devel mailing list
epel-devel
This list is not the right place to discuss these stuffs.
If you want to let them land in the EPEL7, please fill bugs in Bugzilla
against the relevant component. I'm sure most of the owners of those
packages may not subscribe to this list.
___
Actually the epel7 Request page should only be edited by the existing
packagers, or someone may get annoyed.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Tue, Jul 22, 2014 at 9:20 AM, Zhiwei Zhu z_...@wargaming.net wrote:
Hi Christopher,
I have removed the part added by me. Sorry for the mistake.
Well no problem, you are new to here ;)
We need to focus on these packages now as they are required by people.
Yours sincerely,
Christopher Meng
Have you asked the Fedora maintainer of those 21 packages?
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
There are packages still notready for EPEL7 at least.
--
Yours sincerely,
Christopher Meng
http://cicku.me
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Good to hear.
Thanks!
--
Yours sincerely,
Christopher Meng
http://cicku.me
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
You can report a bug against noip:
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedoraversion=rawhidecomponent=noip
IMO noip should switch to systemd. I've written one and if noip Fedora
maintainer won't maintain it in EPEL, I could offer a hand.
On Sat, Aug 30, 2014 at 7:55 PM, LOEFFLER Peter
peter.loeff...@herold.at wrote:
I think it's a good idea to switch to systemd.
Did i get it right that i shoud report a bug that a systemd script is missing
and you will offer it at bugzilla?
You can report a bug first, I will arrive there
Hi,
Redis in EPEL6 is pretty dated, I'd like to update it to the latest
2.x version but somehow I haven't done major update like this.
Is it allowed to update the package from 2.4 to 2.8 for new RHEL 6.x
like 6.8 release?
Thanks.
--
Yours sincerely,
Christopher Meng
http://awk.io
* Versions lower than 2.8 had been dropped from supported lifecycle
for a long time.
* Backporting fixes to 2.4 doesn't make too much sense.
* Config change is needed
(https://raw.githubusercontent.com/antirez/redis/2.6/00-RELEASENOTES).
--
Yours sincerely,
Christopher Meng
http://awk.io
Hi,
In trying to install trojita, I got the following error:
$ sudo yum install trojita
Loaded plugins: langpacks
Resolving Dependencies
--> Running transaction check
---> Package trojita.x86_64 0:0.7-4.el7 will be installed
--> Processing Dependency: libQt5WebKitWidgets.so.5(Qt_5)(64bit) for
On 02/24/2018 02:15 PM, Sérgio Basto wrote:
On Sat, 2018-02-24 at 17:45 +, Christopher Brown wrote:
Hi,
In trying to install trojita, I got the following error:
$ sudo yum install trojita
Loaded plugins: langpacks
Resolving Dependencies
--> Running transaction check
---> P
bserver module or cmd line.
Thanks for the clarification, but you're right, that won't help here, as
NC has extensive runtime PHP7.2+ dependencies.
Christopher
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-
n updated one on Copr instead.
Thanks to all of you, you helped tremendously.
Christopher
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduc
und
- see about creating nextcloud-XX and maybe nextcloud-latest modules
for inclusion in epel8
- epel7: ???
Christopher
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel
hat
simply follows upstream release channel (i.e. N+1.0 replaces N.x, even
if N is still supported and receiving updates) in addition
tonextcloud-. Or have a normal (ursine?) package for that. That
way users can choose between an automatically updating or version-stable
Nextcloud, and whatever they
On 12.10.20 10:49, Leon Fauster wrote:
> Not sure but IIRC EPEL should not depend on software collections ...?
Can someone confirm that? If the package can't depend on php7.2+, then
the question of how to deal with EPEL7 is moot.
Christopher
___
e
on updates or is it better to retire it from EPEL?
I suspect that EPEL users would probably prefer to run it from
upstream's containers anyways, so retiring might make more sense, but
I'm open either way.
Christopher
___
epel-devel mailing list --
updates to whenever
CentOS/RHEL release a new version won't work either.
I think I'll retire and look into re-adding it via modularity.
Christopher
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le
el and would allow to update nextcloud at
> users own pace.
I'm sort of hesitant to dive into learning how modularity works, though
... although, maybe a good opportunity to learn.
Christopher
___
epel-devel mailing list -- epel-devel@lists.fedoraproje
I think
most problems are going to be with database changes, and that's not
really testable on an empty test install ...
Christopher
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-d
On 09.12.20 15:20, Troy Dawson wrote:
> Does anyone know of a group that is going to start their own RHEL Clone?
I'm sure the Scientific Linux people will do something, given that they
just recently decided to not release SL8 but rather use CentOS 8. I feel
quite bad for them, actually ...
Some
why would you get and keep a RHEL dev subscription
when you could just not check the EPEL-boxes?
From a purely technical perspective, i.e. pretending it were CentFork
Community Linux, are there reasons not to use Oracle Linux?
Christopher
___
epel-devel ma
I found it useful to ship the nextcloud package as a module, particularly in
EPEL, but if after multiple years there really are only 12 packages in the repo
and even those may or may not work then that is a pretty clear argument for
eating the sunk cost & abandoning the idea.
-- Christo
Hello,
I have a RHEL 9 system running PHP 8.1 from the Red Hat AppStream module. I
tried to install php-sodium and php-pecl-imagick from EPEL 9 on it, but DNF
gave an error that basically said those packages only work with PHP 8.0. Would
it be possible to provide versions of those packages
48 matches
Mail list logo