Fedora Electronics Lab through EPEL question

Tue Aug 24 14:41:52 UTC 2010

Manuel Wolfshant,
Thank you for responding.  From your answer:

> All packages in Fedora (and EPEL) install the binaries and the man pages
> in the same way. IF a package provides a runable binary it will be in
> your $PATH; if it has manpages, they will be below $MANPATH.

I can only assume that the installations failed even though the messages said "completed".  I did not install them as a private user.  I executed "yum install alliance" (and the other tools too) as root.

After installation, every tool file is owned by root and none of the files are executable.  The man files are all gzipped.

Attempts to reinstall result in a message that the tool is already installed.

I will try your suggestion and use rpm -ql and repoquery -l to see if there's some clue as to how I should proceed but my gut feeling is these commands will leave me still clueless.

Any ideas on what I did wrong or what steps were omitted from the installation procedure?

Thanks,
Bob P.

-----Original Message-----
From: epel-devel-list-bounces at redhat.com [mailto:epel-devel-list-bounces at redhat.com] On Behalf Of epel-devel-list-request at redhat.com
Sent: Tuesday, August 24, 2010 6:00 AM
To: epel-devel-list at redhat.com
Subject: epel-devel-list Digest, Vol 43, Issue 32

Send epel-devel-list mailing list submissions to
        epel-devel-list at redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.redhat.com/mailman/listinfo/epel-devel-list
or, via email, send a message with subject or body 'help' to
        epel-devel-list-request at redhat.com

You can reach the person managing the list at
        epel-devel-list-owner at redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of epel-devel-list digest..."

Today's Topics:

   1. Re: Catalyst in EPEL 6 (Chris Adams)
   2. Fedora Electronics Lab through EPEL question (Robert Peruzzi)
   3. Re: Fedora Electronics Lab through EPEL question
      (Manuel Wolfshant)
   4. epel beta report: 20100823 changes (EPEL Beta Report)
   5. Re: Catalyst in EPEL 6 (Iain Arnell)
   6. Re: Catalyst in EPEL 6 (Mark Chappell)

----------------------------------------------------------------------

Message: 1
Date: Mon, 23 Aug 2010 16:32:47 -0500
From: Chris Adams <cmadams at hiwaay.net>
To: EPEL development disccusion <epel-devel-list at redhat.com>
Subject: Re: Catalyst in EPEL 6
Message-ID: <20100823213247.GF603853 at hiwaay.net>
Content-Type: text/plain; charset=us-ascii

Once upon a time, Michael Stahnke <mastahnke at gmail.com> said:
> If each shop is doing it themselves, that's a lot of wasted
> productivity over the long haul.  Ideally, this is done in EPEL which
> will handle the default case (which is hopefully good enough for most
> shops).  After that shops may require adjustments to packages or
> produce newer ones in year 3-7 of the RHEL lifecycle.  I'd hope that
> EPEL can at least be a decent starting point though.

I package up several things myself, mainly because I need it "now".  I
have plans to push some of those packages to Fedora and EPEL (or just
EPEL, in the case of local rebuilds of Fedora packages), but I haven't
had enough round tuits to get that done.

I did separate my local RHEL repo into repos based on the source of the
package, like "fedora-add" for things I've rebuilt from Fedora,
"fedora-replace" for a few things where I needed a newer version than
RHEL/EPEL, "hiwaay-add" for my packages, etc.  Ideally that will make it
easier for me to work with Fedora and EPEL to get my work into the
repos.

--
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

------------------------------

Message: 2
Date: Mon, 23 Aug 2010 17:37:11 -0400
From: Robert Peruzzi <peruzzi at rperuzzi.com>
To: "epel-devel-list at redhat.com" <epel-devel-list at redhat.com>
Subject: Fedora Electronics Lab through EPEL question
Message-ID:
        <7E04D3604915E449B5F991F9DA0E7D7702B64BE062 at mse21be1.mse21.exchange.ms>

Content-Type: text/plain; charset="iso-8859-1"

EPEL Helpers,

I'm running RHEL 5.1.19.6 and I want to be able to run CAD tools from FEL.  Following directions on the EPEL web page I downloaded an EPEL package as root, then installed all the FEL tools individually with, for instance:

# yum install alliance

About ? of the installations succeeded, but I'll ask about the failures another time. For the "successful" installations:

?        What is the next step to add the programs to PATH and the man pages to MANPATH, and make myself the owner (rather than root) and make the executables executable so I can learn to run these tools?

?        Is there a few commands to do this for me or do I need to write my own script or execute the steps one at a time for each tool?

?        Are there more steps I'm missing beyond editing PATH and MANPATH, then doing a chown and chmod?

Thank you,

Bob Peruzzi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/epel-devel-list/attachments/20100823/72bc029e/attachment.html>

------------------------------

Message: 3
Date: Tue, 24 Aug 2010 00:47:39 +0300
From: Manuel Wolfshant <wolfy at nobugconsulting.ro>
To: EPEL development disccusion <epel-devel-list at redhat.com>
Subject: Re: Fedora Electronics Lab through EPEL question
Message-ID: <4C72EC7B.5080203 at nobugconsulting.ro>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 08/24/2010 12:37 AM, Robert Peruzzi wrote:
>
> EPEL Helpers,
>
> I?m running RHEL 5.1.19.6 and I want to be able to run CAD tools from
> FEL. Following directions on the EPEL web page I downloaded an EPEL
> package as root, then installed all the FEL tools individually with,
> for instance:
>
> # yum install alliance
>
> About ? of the installations succeeded, but I?ll ask about the
> failures another time. For the ?successful? installations:
>
> ? What is the next step to add the programs to PATH and the man pages
> to MANPATH, and make myself the owner (rather than root) and make the
> executables executable so I can learn to run these tools?
>
All packages in Fedora (and EPEL) install the binaries and the man pages
in the same way. IF a package provides a runable binary it will be in
your $PATH; if it has manpages, they will be below $MANPATH.
You can always use rpm -ql or repoquery -l to list the content of the
package that you have installed ( or even before installing) and look
around to see what is installed and where.
Installing as a private user rather than root can be done but is not
supported. If you really want to do that, create a chroot ( or a
fakeroot...) and install over there. Keep in mind that most probably
those applications will need dependencies ( libraries) which will be
found in the system directories,. hence will not be available in the
chroot unless you specifically place them there, too

> ? Is there a few commands to do this for me
>
find the name of binaries and locations/names of manpages: yes
install as user: no

> or do I need to write my own script or execute the steps one at a time
> for each tool?
>
> ? Are there more steps I?m missing beyond editing PATH and MANPATH,
> then doing a chown and chmod?
>

------------------------------

Message: 4
Date: Mon, 23 Aug 2010 23:23:12 +0000
From: EPEL Beta Report <epel at fedoraproject.org>
To: epel-devel-list at redhat.com
Subject: epel beta report: 20100823 changes
Message-ID: <20100823232312.GA31474 at relepel01.phx2.fedoraproject.org>
Content-Type: text/plain; charset=us-ascii

Compose started at Mon Aug 23 23:02:17 UTC 2010

New package fmtools
        Simple Video for Linux radio card programs
New package libXcm
        X Color Management Library
New package mac-robber
        Tool to create a timeline of file activity for mounted file systems
New package matio
        Library for reading/writing Matlab MAT files
New package nntpgrab
        Download files from the usenet
New package par2cmdline
        PAR 2.0 compatible file verification and repair tool
New package perl-AnyEvent
        Framework for multiple event loops
New package perl-BDB
        Asynchronous Berkeley DB access
New package perl-Email-Find
        Find RFC 822 email addresses in plain text
New package perl-ExtUtils-CChecker
        Configure-time utilities for using C headers, libraries, or OS features
New package perl-Return-Value
        Polymorphic Return Values
New package php-pear-Image-Canvas
        Common interface to image drawing
New package php-pear-Net-UserAgent-Detect
        Extract information from an HTTP user agent
New package php-pear-Structures-DataGrid-DataSource-Array
        DataSource driver using arrays
New package php-pear-Structures-DataGrid-DataSource-DataObject
        DataSource driver using PEAR::DB_DataObject
New package php-pear-Structures-DataGrid-DataSource-MDB2
        DataSource driver using PEAR::MDB2 and an SQL query
New package php-pear-Structures-DataGrid-DataSource-RSS
        DataSource driver using RSS files
New package php-pear-Structures-DataGrid-Renderer-Pager
        Renderer driver using PEAR::Pager
New package php-pear-Validate
        Validation Class for Various Data Types
New package php-pear-XML-Beautifier
        Class to format XML documents
New package php-pear-XML-Serializer
        Swiss-army knife for reading and writing XML files
Updated Packages:

dirac-1.0.2-4.el6
-----------------
* Mon Aug 23 2010 Nicolas Chauvet <kwizart at gmail.com> - 1.0.2-4
- rebuilt for cppunit update in EL6

emacs-spice-mode-1.2.25-4.el6
-----------------------------
* Sun Aug 22 2010 Arun SAG <sagarun at gmail.com> - 1.2.25-4
- Fixed instllation failure due to failed dependency gwave in EL5

phpMyAdmin-3.3.5.1-1.el6
------------------------
* Fri Aug 20 2010 Robert Scheck <robert at fedoraproject.org> 3.3.5.1-1
- Upstream released 3.3.5.1 (#625877, #625878)
- Added patch to fix wrong variable check at nopassword (#622428)

qucs-0.0.15-5.el6
-----------------
* Sat Aug 21 2010 Chitlesh Goorah <chitlesh [AT] fedoraproject DOT org> - 0.0.15-5
- Patch no longer needed with freehdl-0.0.7

rmanage-0.1.8-1.el6
-------------------
* Fri Aug 20 2010 Parag Nemade <panemade AT gmail.com>- 0.1.8-1
- Update to next update version 0.1.8

sems-1.2.1-6.el6
----------------
* Fri Aug 20 2010 Peter Lemenkov <lemenkov at gmail.com> 1.2.1-6
- Fixed severe issue in early_announce module (see %patch12)

* Sat Jul 31 2010 Toshio Kuratomi <toshio at fedoraproject.org> 1.2.1-5
- rebuild for python 2.7

spamassassin-FuzzyOcr-3.6.0-4.el6
---------------------------------
* Sun Aug 22 2010 Andrew Colin Kissa <andrew at topdog.za.net> - 3.6.0-4
- fix bugzilla bug #621785

Summary:
Added Packages: 21
Removed Packages: 0
Modified Packages: 7

------------------------------

Message: 5
Date: Tue, 24 Aug 2010 10:57:01 +0200
From: Iain Arnell <iarnell at gmail.com>
To: EPEL development disccusion <epel-devel-list at redhat.com>
Subject: Re: Catalyst in EPEL 6
Message-ID:
        <AANLkTimqkYc5+9zNFy14kCr867zU6gBx3uRqj5PNnomz at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Sat, Aug 21, 2010 at 11:36 PM, Stephen John Smoogen <smooge at gmail.com> wrote:
> On Sat, Aug 21, 2010 at 13:36, Edward Trochim <ejtrochim at alaska.edu> wrote:
>> Hello all,
>>
>> Are there plans to bring the perl Catalyst framework to EPEL 6? The runtime
>> and many of the plugins are already in Fedora 12. I am interested in
>> providing any help that is needed; however, I have never created any
>> packages for either Fedora or EPEL.
>>
>
> No one has expressed an interest before. I would say that the first
> thing to look for is help in the Fedora Perl SIG

It certainly seems possible. I only find 40 missing deps for a minimal
installation. The biggest problem is that last time I checked, Chris
Weyl wasn't interested in EPEL.

berrange  perl-Array-Diff
berrange  perl-Module-CPANTS-Analyse *
cweyl     perl-Catalyst-Action-RenderView
cweyl     perl-Catalyst-Devel
cweyl     perl-Catalyst-Plugin-ConfigLoader
cweyl     perl-Catalyst-Plugin-Static-Simple
cweyl     perl-Catalyst-Plugin-SubRequest
cweyl     perl-Catalyst-Runtime
cweyl     perl-Class-C3-Adopt-NEXT
cweyl     perl-Config-Any
cweyl     perl-Data-Alias
cweyl     perl-Data-Dump *
cweyl     perl-Data-Visitor
cweyl     perl-File-ChangeNotify
cweyl     perl-File-Modified
cweyl     perl-HTTP-Request-AsCGI
cweyl     perl-MooseX-Emulate-Class-Accessor-Fast
cweyl     perl-MooseX-MethodAttributes
cweyl     perl-MooseX-Params-Validate
cweyl     perl-MooseX-SemiAffordanceAccessor
cweyl     perl-namespace-autoclean
cweyl     perl-String-RewritePrefix
cweyl     perl-Test-use-ok
cweyl     perl-Text-SimpleTable
cweyl     perl-Tie-ToObject
cweyl     perl-Tree-Simple-VisitorFactory
eseyman   perl-Variable-Magic
iarnell   perl-Devel-Hide
iarnell   perl-Term-Size-Any
iarnell   perl-Term-Size-Perl
iburrell  perl-Path-Class *
lkundrak  perl-Test-MockObject *
spot      perl-UNIVERSAL-can *
spot      perl-UNIVERSAL-isa *
steve     perl-Devel-Caller *
till      fcgi *
tremble   perl-B-Hooks-EndOfScope *
tremble   perl-MooseX-Types *
tremble   perl-namespace-clean *
tremble   perl-Test-Kwalitee *

(*) already exists in EPEL, but no builds for EL-6 yet.

--
Iain.

------------------------------

Message: 6
Date: Tue, 24 Aug 2010 10:59:17 +0100
From: Mark Chappell <tremble at tremble.org.uk>
To: EPEL development disccusion <epel-devel-list at redhat.com>
Subject: Re: Catalyst in EPEL 6
Message-ID: <4C7397F5.9070305 at tremble.org.uk>
Content-Type: text/plain; charset=ISO-8859-1

Edward Trochim wrote:
> We are seriously considering using Catalyst for a new webapp we will be developing soon and we want to be able to deploy it using the same mechanisms as all our other software. We could use CPAN, and we are prepared to go that route if we need to, but we would prefer to keep everything in RPMs. There are actually several deployment strategies I am investigating right now, this is just one of them.

Are you already a Fedora Packager?  If so then cweyl seems quite happy
to let people maintain his packages over in EPEL.

The packages I've not built yet in that list are because I've not had
chance to chase done the last few dependencies and I've been on holiday
and am about to move country.  I'm willing to help co-maintain the extra
packages in EPEL, but I'm unlikely to be doing that much over the next 2
to 3 weeks.

Mark

------------------------------

_______________________________________________
epel-devel-list mailing list
epel-devel-list at redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list

End of epel-devel-list Digest, Vol 43, Issue 32
***********************************************