From nkadel at gmail.com Wed Jul 2 09:40:43 2008 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Wed Jul 2 09:41:08 2008 Subject: [suggest] Re: suggest Digest, Vol 37, Issue 1 In-Reply-To: <20080701100109.0DBA9318093@pooch.vmhosting.org> References: <20080701100109.0DBA9318093@pooch.vmhosting.org> Message-ID: <486B30FB.2030902@gmail.com> Dag wrote: Correct. The message to anyone using perl modules is: If you want your product to work on RHEL4, or RHEL5, then do not require any newer versions of those perl modules. It's awkward. There is a serious dependency hell when backporting packages from Fedora, or cross-porting them from Debian or from CPAN modules. It's not that redHat was unreasonable about what they include in the base Perl package, but they include quite a few components that needn't be quite so integral. And the CPAN module management assumes that it can, gracefully, replace components that are part of the central package itself. This is aggravated by modules that have been migrated into the current version of Perl, where attempts to build them discreetly from CPAN simply grabs the complete latest Perl package, and that is a maintenance nightmare to replace. One alternative is to maiintain your own local Perl distribution, call it 'perl-local', leave out the particular modules that conflict, and set 'Provides: perl'-%{version}' in the .spec file for perl-local. I've done that trick at need. I don't recommend it for Dag's wonderful repository, because replacing such a central system component is begging for pain. But I went through this a lot last year, when working with Musicbrainz, and I'm going through it right now with Lilac and its necessary PHP dependency tree. Nico Kadel-Garcia From nkadel at gmail.com Wed Jul 2 09:54:40 2008 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Wed Jul 2 09:55:04 2008 Subject: [suggest] Composing an RPM for PHP propel and PHP zhing, can anyone help me out? Message-ID: <486B3440.7030406@gmail.com> I'm trying to work with Lilac, the new version of the 'Fruity' Nagios configuration tool. Unfortunately, I'm not a PHP expert, and it relies on the PHP 'propel' package. That package is normally installed online, with ' I'm unclear on what parts of the installation I need to do: just dump it in /usr/share/pear, or do I need a '%{post}' step to process it in place to use it? Are any of our contributors comfortable enough with PHP to guide me in building some decent .spec file? And in particular, to satisfy the the php Phing dependencies, as well? From erichey at speakeasy.net Tue Jul 8 00:58:03 2008 From: erichey at speakeasy.net (Eric Heydrick) Date: Tue Jul 8 00:58:26 2008 Subject: [suggest] Contribution: perl-Tie-DxHash 1.03 Message-ID: Attached is a spec file for perl-Tie-DxHash that'll build the tie::dxhash module from cpan. I based the spec on perl-Tie-IxHash from dag.wieers.com. I tested on RHEL5.2. Feel free to include this in RPMforge. I don't wish to be the maintainer. -Eric -------------- next part -------------- # $Id: perl-Tie-IxHash.spec 4261 2006-03-29 17:21:04Z thias $ # Authority: dries # Upstream: Kevin Ruscoe %define real_name Tie-DxHash %define perl_vendorlib %(eval "`perl -V:installvendorlib`"; echo $installvendorlib) %define perl_vendorarch %(eval "`perl -V:installvendorarch`"; echo $installvendorarch) %define perl_archlib %(eval "`perl -V:archlib`"; echo $archlib) %define perl_privlib %(eval "`perl -V:privlib`"; echo $privlib) Summary: Keeps insertion order; allows duplicate keys Name: perl-Tie-DxHash Version: 1.03 Release: 1.0 License: Artistic Group: Applications/CPAN URL: http://search.cpan.org/dist/Tie-DxHash/ Source: http://www.cpan.org/modules/by-module/Tie/Tie-DxHash-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root BuildArch: noarch BuildRequires: perl %description Tie::DxHash implements a hash which preserves insertion order and allows duplicate keys. It was written to facilitate the use of more complex mod_rewrite rules in Apache configuration files written with Perl Sections. See the module's POD for details. %prep %setup -n %{real_name}-%{version} %build %{__perl} Makefile.PL INSTALLDIRS="vendor" PREFIX="%{buildroot}%{_prefix}" %{__make} %{?_smp_mflags} OPTIMIZE="%{optflags}" %install %{__rm} -rf %{buildroot} %makeinstall %{__rm} -f %{buildroot}%{perl_archlib}/perllocal.pod %{__rm} -f %{buildroot}%{perl_vendorarch}/auto/*/*/.packlist %clean %{__rm} -rf %{buildroot} %files %defattr(-, root, root, 0755) %doc Changes README %doc %{_mandir}/man3/* %{perl_vendorlib}/Tie/DxHash.pm %changelog * Mon Jul 07 2008 Eric Heydrick - 1.03-1 - Initial package. From lists07 at abbacomm.net Tue Jul 8 18:49:47 2008 From: lists07 at abbacomm.net (Robert - elists) Date: Tue Jul 8 18:50:21 2008 Subject: [suggest] thanks and clamav freshen Message-ID: <000001c8e11a$a19cdb70$0900000a@msys1> Thanks for all the hard work keeping the repo's going! Can you please freshen clamav? It has had a coupla updates in the last few days Thanks! - rh From lists07 at abbacomm.net Wed Jul 9 18:59:21 2008 From: lists07 at abbacomm.net (Robert - elists) Date: Wed Jul 9 18:59:45 2008 Subject: [suggest] clamming clams! :-) Message-ID: <000901c8e1e5$227b85a0$0900000a@msys1> Hi Thanks for clamav update FYI, It appears that the clamav updates site would be happier if the version numbers were changed just a bit The latest clamav.net software updates included two revisions in one day. Must have been a boo boo that was quickly fixed... Don't worry, we didn't panic! ;-> ClamAV update process started at Wed Jul 9 09:56:11 2008 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.93.2 Recommended version: 0.93.3 DON'T PANIC! Read http://www.clamav.net/support/faq main.cld is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven) daily.cld is up to date (version: 7676, sigs: 35648, f-level: 33, builder: ccordes) if this is something you can address for us please, then please do thanks in advance - rh From lists07 at abbacomm.net Wed Jul 9 19:07:51 2008 From: lists07 at abbacomm.net (Robert - elists) Date: Wed Jul 9 19:08:15 2008 Subject: [suggest] clamav-db dependency issue? Message-ID: <000001c8e1e6$52454c20$0900000a@msys1> Re: the last post we did re "clamav" When we did the update we did an rpmforge repo update like this yum update clam* Yet, it didn't see or grab clamav-db for some reason in the dependencies or whatever Dunno if this is affecting others too... All is better now, we just specified yum update clamav-db to get the last part... hmmmmmmmmmmm Thanks - rh From dag at wieers.com Wed Jul 9 22:16:08 2008 From: dag at wieers.com (Dag Wieers) Date: Wed Jul 9 22:16:40 2008 Subject: [suggest] clamming clams! :-) In-Reply-To: <000901c8e1e5$227b85a0$0900000a@msys1> References: <000901c8e1e5$227b85a0$0900000a@msys1> Message-ID: On Wed, 9 Jul 2008, Robert - elists wrote: > Thanks for clamav update > > FYI, It appears that the clamav updates site would be happier if the version > numbers were changed just a bit > > The latest clamav.net software updates included two revisions in one day. Sigh. They used to announce new releases in advance on a seperate packaging list. Now I have to find out from users :-/ Thanks for reporting, 0.93.3 will appear this night. -- -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] From joey at clean.q7.com Wed Jul 9 22:38:55 2008 From: joey at clean.q7.com (Joe Pruett) Date: Wed Jul 9 22:39:21 2008 Subject: [suggest] confusion about alpine (and rf in general) Message-ID: the rpms i have installed are alpine-1.10-1.el4.rf and 1.10-1.el5.rf. they have a problem with the pine.conf being in /usr/local/lib. when i look at the spec file in svn, it claims to have fixed this problem. the comment for the fix indicates 1.10-2, but the release in the spec is still 1. so i am guessing that the spec should have 2.rf as the release? and that leads me to wonder where the el4/el5 is being stuffed in? there isn't a macro in the release field, so is it done on the fly by the build system? From dag at wieers.com Wed Jul 9 23:14:00 2008 From: dag at wieers.com (Dag Wieers) Date: Wed Jul 9 23:14:23 2008 Subject: [suggest] confusion about alpine (and rf in general) In-Reply-To: References: Message-ID: On Wed, 9 Jul 2008, Joe Pruett wrote: > the rpms i have installed are alpine-1.10-1.el4.rf and > 1.10-1.el5.rf. they have a problem with the pine.conf being > in /usr/local/lib. when i look at the spec file in svn, it > claims to have fixed this problem. the comment for the fix > indicates 1.10-2, but the release in the spec is still 1. Right, I was planning to do it but while wondering whether I should use the original pine.conf or start writing a new one got distracted ... > so i am guessing that the spec should have 2.rf as the > release? and that leads me to wonder where the el4/el5 is > being stuffed in? there isn't a macro in the release field, > so is it done on the fly by the build system? The buildsystem adds the proper disttag. I will add the original pine.conf for now... Thanks for reporting !! -- -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] From joey at clean.q7.com Wed Jul 9 23:22:35 2008 From: joey at clean.q7.com (Joe Pruett) Date: Wed Jul 9 23:23:00 2008 Subject: [suggest] confusion about alpine (and rf in general) In-Reply-To: References: Message-ID: > Right, I was planning to do it but while wondering whether I should use the > original pine.conf or start writing a new one got distracted ... that was another confusion i had, are the support files available anywhere in svn or the like? i was going to try building a new version but wasn't sure what alpine/pine.conf file was being used. i think that running alpine --pinerc to produce a new alpine.conf would be good. i guess that trying to use pine.conf for backwards compatibility is nice, but maybe that should be done via a script? From dsteinbrunner at pobox.com Wed Jul 9 23:31:35 2008 From: dsteinbrunner at pobox.com (David Steinbrunner) Date: Wed Jul 9 23:32:09 2008 Subject: [suggest] Add perl-MooseX-AttributeHelpers Message-ID: Hello, I'm new to the RedHat/RPM/RPMForge scene but thanks to the direction of collages, I'm here. Your site suggests that perl modules are easily added so hopefully me requesting MooseX::AttributeHelpers to be added to the mix is not an issue. I'm aware that it would also require some other modules to be updated but when I sandbox installed all that is needed from cpan I did not have issues using it. Thanks, -- David Steinbrunner From lists07 at abbacomm.net Thu Jul 10 00:23:07 2008 From: lists07 at abbacomm.net (Robert - elists) Date: Thu Jul 10 00:23:36 2008 Subject: [suggest] clamming clams! :-) In-Reply-To: References: <000901c8e1e5$227b85a0$0900000a@msys1> Message-ID: <000c01c8e212$5d4f0e90$0900000a@msys1> > > Sigh. They used to announce new releases in advance on a seperate > packaging list. Now I have to find out from users :-/ > > Thanks for reporting, 0.93.3 will appear this night. > > -- > -- dag wieers, Thanks Dag I do get an email from clamav announce, or something to that effect. That is typically when I ask for a clamav freshen on the suggest @ rpmforge list. It appeared that the RPM's were having a dependency problem and not pulling clamav-db at the same time ??? That is why I had to yum update clamav-db after the initial yum update clam* to get it all. Thanks again! - rh From stefano.biagiotti at vola.it Thu Jul 10 18:35:34 2008 From: stefano.biagiotti at vola.it (Stefano Biagiotti) Date: Thu Jul 10 18:35:57 2008 Subject: [suggest] keepalived for RHEL5 Message-ID: <20080710163534.GA5439@palermo.priv2.gtn.it> Hello. I'm searching for RHEL5 keepalived package, but the list at http://packages.sw.be/keepalived/ shows only RedHat/Fedora/RHEL[234] RPMs. Can you please build keepalived (latest version 1.1.15) for RHEL5 and add it to rpmforge repository? Thank you in advance. -- Stefano Biagiotti From justdave at mozilla.com Fri Jul 11 10:09:35 2008 From: justdave at mozilla.com (Dave Miller) Date: Fri Jul 11 10:10:21 2008 Subject: [suggest] clamming clams! :-) In-Reply-To: References: <000901c8e1e5$227b85a0$0900000a@msys1> Message-ID: <4877153F.4030500@mozilla.com> Dag Wieers wrote on 7/9/08 4:16 PM: > On Wed, 9 Jul 2008, Robert - elists wrote: > >> Thanks for clamav update >> >> FYI, It appears that the clamav updates site would be happier if the >> version >> numbers were changed just a bit >> >> The latest clamav.net software updates included two revisions in one day. > > Sigh. They used to announce new releases in advance on a seperate > packaging list. Now I have to find out from users :-/ > > Thanks for reporting, 0.93.3 will appear this night. Doesn't seem to have shown up yet? Still getting 0.93.2-1.el5 here. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From lists07 at abbacomm.net Sat Jul 12 07:53:25 2008 From: lists07 at abbacomm.net (Robert - elists) Date: Sat Jul 12 07:53:51 2008 Subject: [suggest] 0.93.2 bad buggy clamav code Message-ID: <001201c8e3e3$9a1bbe90$0900000a@msys1> This current clamav clamav i386 0.93.2-1.el4.rf rpmforge 1.3 M clamav-db i386 0.93.2-1.el4.rf rpmforge 15 M clamav-devel i386 0.93.2-1.el4.rf rpmforge 6.9 k clamd i386 0.93.2-1.el4.rf rpmforge 82 k has bad buggy code and needs to be updated to latest - rh From lists07 at abbacomm.net Sat Jul 12 18:34:16 2008 From: lists07 at abbacomm.net (Robert - elists) Date: Sat Jul 12 18:41:05 2008 Subject: [suggest] grateful thanks! Message-ID: <000b01c8e43d$206929c0$0900000a@msys1> To all rpmforge team Thank you for your many efforts and hard work on all the packages and the recent clam fixin's - rh From stefano.biagiotti at vola.it Mon Jul 14 17:17:48 2008 From: stefano.biagiotti at vola.it (Stefano Biagiotti) Date: Mon Jul 14 17:18:22 2008 Subject: [suggest] unrar 3.8.2 Message-ID: <20080714151748.GA6793@palermo.priv2.gtn.it> I'm using unrar from rpmforge. # yum -d 0 list unrar Installed Packages unrar.x86_64 3.7.8-1.el4.rf installed Latest version is 3.8.2 http://www.rarlab.com/rar/unrarsrc-3.8.2.tar.gz Can you please update to the latest version? Thank you in advance. -- Stefano Biagiotti From rpmforge at crawford.homeunix.net Mon Jul 14 19:55:39 2008 From: rpmforge at crawford.homeunix.net (Jollyroger) Date: Mon Jul 14 19:56:08 2008 Subject: [suggest] mediatomb spec file for CentOS 5.2 Message-ID: <487B931B.7000200@crawford.homeunix.net> Note that I'm not on the suggest mailing list, so please make sure I'm in the send to list if replying. Please bare with me as this is the first time I'm doing this if I do something wrong. WARNING: This package creates a group and user "mediatomb" with the uid/gid of 62. I don't know if that uid/gid is used anywhere else. If someone has a better suggestion please let me know and I'll change it and repost I don't mind being contacted if a new version of mediatomb comes out and I haven't seen it yet and you want the new version. I'll try to stay up to date but I haven't found a mediatomb announce list to subscribe to. Jeffrey -------------- next part -------------- Summary: an open source (GPL) UPnP MediaServer with a nice web user interface # I'm hopping that the uid/gid 62 is not used anywhere else, please report if # that is not the case! %define version 0.11.0 %define usr mediatomb %define uid 62 %define grp mediatomb %define gid 62 # Put path locations in variables to ease changes %define config_dir %{_sysconfdir}/mediatomb %define init_dir %{_sysconfdir}/rc.d/init.d %define pid_dir %{_var}/run/mediatomb %define log_dir %{_var}/log/mediatomb Requires: bash >= 3.2-21 Requires: ffmpeg >= 0.4.9-0.9.20070530 Requires: libexif >= 0.6.13-4.0.2 Requires: expat >= 1.95.8-8.2.1 Requires: libgcc >= 4.1.2-42 Requires: js >= 1.60 Requires: file >= 4.17-13 Requires: sqlite >= 3.3.6-2 Requires: taglib >= 1.5 Requires: libstdc++ >= 4.1.2-42 Requires: zlib >= 1.2.3-3 BuildRequires: ffmpeg-devel >= 0.4.9-0.9.20070530 BuildRequires: libexif-devel >= 0.6.13-4.0.2 BuildRequires: expat-devel >= 1.95.8-8.2.1 BuildRequires: js-devel >= 1.60 BuildRequires: sqlite-devel >= 3.3.6-2 BuildRequires: taglib-devel >= 1.5 BuildRequires: libstdc++-devel >= 4.1.2-42 BuildRequires: zlib-devel >= 1.2.3-3 Release: 1.el5 Source1: mediatomb-etc-init.d Source2: mediatomb-etc-logrotate.d Source3: mediatomb-etc-mediatomb-config.xml Group: System Environment/Daemons Name: mediatomb Prefix: %{_prefix} Provides: mediaserver Source: http://downloads.sourceforge.net/mediatomb/mediatomb-%{version}.tar.gz Patch1: mediatomb_centos.patch Buildroot: /tmp/mediatomb-%{version} URL: http://mediatomb.cc/ Version: %{version} License: MediaTomb is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as published by the Free Software Foundation. MediaTomb is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License version 2 along with MediaTomb; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA %description MediaTomb is an open source (GPL) UPnP MediaServer with a nice web user interface, it allows you to stream your digital media through your home network and listen to/watch it on a variety of UPnP compatible devices. MediaTomb implements the UPnP MediaServer V 1.0 specification that can be found on http://www.upnp.org/. The current implementation focuses on parts that are required by the specification, however we look into extending the functionality to cover the optional parts of the spec as well. MediaTomb should work with any UPnP compliant MediaRenderer, please tell us if you experience difficulties with particular models, also take a look at the Supported Devices list for more information. To contact us via email, write to: contact at mediatomb dot cc We have an IRC support channel on the freenode network: chat.freenode.net, #mediatomb. Feel free to join if you have questions or need help with MediaTomb, but be patient since we may be idle (btw. we are in C.E.T.). Also, make sure to visit our support forums since the answer may already be there. %pre %{_sbindir}/groupadd -g %{gid} -r %{grp} 2> /dev/null %{_sbindir}/useradd -d %{config_dir} -s /sbin/nologin -g %{grp} -M -r -u %{uid} %{usr} 2> /dev/null exit 0 %post /sbin/chkconfig --add mediatomb /sbin/chkconfig mediatomb on %preun /sbin/service mediatomb stop > /dev/null 2>&1 if [ "$1" = 0 ]; then # Package is being removed so stop mediatomb # and remove it from the init system. /sbin/chkconfig --del mediatomb > /dev/null 2>&1 fi exit 0 %postun if [ "$1" = 1 ]; then # We are upgrading so we need to restart mediatomb /sbin/service mediatomb restart > /dev/null 2>&1 fi if [ "$1" = 0 ]; then # Do some package cleanup since this is a stright uninstall %{_sbindir}/userdel -f %{usr} > /dev/null 2>&1 %{_sbindir}groupdel -f %{grp} > /dev/null 2>&1 fi exit 0 %prep %setup -q %patch1 -p1 -b .centos5 %build ./configure --prefix=%{buildroot}/%{_prefix} %{__make} %install %{__rm} -rf %{buildroot} %{__make} install %{__mkdir_p} %{buildroot}/%{init_dir} %{__install} -c -m 755 %{SOURCE1} %{buildroot}/%{init_dir}/mediatomb %{__mkdir_p} %{buildroot}/etc/logrotate.d %{__install} -c -m 644 %{SOURCE2} %{buildroot}/etc/logrotate.d/mediatomb %{__mkdir_p} %{buildroot}/etc/mediatomb %{__install} -c -m 644 %{SOURCE3} %{buildroot}/etc/mediatomb/config.xml %{__mkdir_p} %{buildroot}/%{pid_dir} %{__mkdir_p} %{buildroot}/%{log_dir} %files %defattr(-,root,root) # Start with the directories and configuration files. %dir %{_datadir}/mediatomb %dir %{_datadir}/mediatomb/js %dir %{_datadir}/mediatomb/web %dir %{_datadir}/mediatomb/web/icons %dir %{_datadir}/mediatomb/web/icons/nanotree %dir %{_datadir}/mediatomb/web/icons/nanotree/images %dir %{_datadir}/mediatomb/web/js %dir %attr(0755,%{usr},%{grp}) %{log_dir} %dir %attr(0755,%{usr},%{grp}) %{pid_dir} %dir %attr(0755,%{usr},%{grp}) %{config_dir} %config(noreplace) %attr(0644,%{usr},%{grp}) %{config_dir}/config.xml # List of files included in this package %{_sysconfdir}/rc.d/init.d/mediatomb %{_sysconfdir}/logrotate.d/mediatomb %{_bindir}/mediatomb %{_datadir}/mediatomb/mappings.xml %{_datadir}/mediatomb/mysql.sql %{_datadir}/mediatomb/js/import.js %{_datadir}/mediatomb/js/playlists.js %{_datadir}/mediatomb/js/common.js %{_datadir}/mediatomb/web/cds.xml %{_datadir}/mediatomb/web/disabled.html %{_datadir}/mediatomb/web/mr_reg.xml %{_datadir}/mediatomb/web/std_treelook.css %{_datadir}/mediatomb/web/icons/autoscan_inotify_folder_open.png %{_datadir}/mediatomb/web/icons/blank.png %{_datadir}/mediatomb/web/icons/mt-icon120.png %{_datadir}/mediatomb/web/icons/remove_autoscan.png %{_datadir}/mediatomb/web/icons/remove_this.png %{_datadir}/mediatomb/web/icons/status_loading.png %{_datadir}/mediatomb/web/icons/status_updates_pending.png %{_datadir}/mediatomb/web/icons/mediatomb.png %{_datadir}/mediatomb/web/icons/film.png %{_datadir}/mediatomb/web/icons/document-new.png %{_datadir}/mediatomb/web/icons/mt-icon48.png %{_datadir}/mediatomb/web/icons/mt-icon32.bmp %{_datadir}/mediatomb/web/icons/go-previous.png %{_datadir}/mediatomb/web/icons/stock-add.png %{_datadir}/mediatomb/web/icons/folder_new.png %{_datadir}/mediatomb/web/icons/mt-icon48.jpg %{_datadir}/mediatomb/web/icons/go-next.png %{_datadir}/mediatomb/web/icons/autoscan_timed_folder_open.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_inotify_folder_open.png %{_datadir}/mediatomb/web/icons/nanotree/images/plus_last_no_root.png %{_datadir}/mediatomb/web/icons/nanotree/images/plus_last.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_timed_folder_closed.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_inotify_folder_closed.png %{_datadir}/mediatomb/web/icons/nanotree/images/minus_last_no_root.png %{_datadir}/mediatomb/web/icons/nanotree/images/t_no_root.png %{_datadir}/mediatomb/web/icons/nanotree/images/plus_no_root.png %{_datadir}/mediatomb/web/icons/nanotree/images/minus.png %{_datadir}/mediatomb/web/icons/nanotree/images/t.png %{_datadir}/mediatomb/web/icons/nanotree/images/lastnode.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_timed_folder_open.png %{_datadir}/mediatomb/web/icons/nanotree/images/plus.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_timed_config_folder_open.png %{_datadir}/mediatomb/web/icons/nanotree/images/minus_last.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_inotify_config_folder_closed.png %{_datadir}/mediatomb/web/icons/nanotree/images/line.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_inotify_config_folder_open.png %{_datadir}/mediatomb/web/icons/nanotree/images/folder_open.png %{_datadir}/mediatomb/web/icons/nanotree/images/autoscan_timed_config_folder_closed.png %{_datadir}/mediatomb/web/icons/nanotree/images/folder_closed.png %{_datadir}/mediatomb/web/icons/nanotree/images/minus_no_root.png %{_datadir}/mediatomb/web/icons/nanotree/images/white.png %{_datadir}/mediatomb/web/icons/autoscan_timed_config_folder_open.png %{_datadir}/mediatomb/web/icons/mt-icon32.png %{_datadir}/mediatomb/web/icons/status.png %{_datadir}/mediatomb/web/icons/stock_edit.png %{_datadir}/mediatomb/web/icons/stock_exit.png %{_datadir}/mediatomb/web/icons/autoscan_inotify_config_folder_open.png %{_datadir}/mediatomb/web/icons/mt-icon48.bmp %{_datadir}/mediatomb/web/icons/go-last.png %{_datadir}/mediatomb/web/icons/mt-icon32.jpg %{_datadir}/mediatomb/web/icons/add_as_autoscan.png %{_datadir}/mediatomb/web/icons/mt-icon120.bmp %{_datadir}/mediatomb/web/icons/mt-icon120.jpg %{_datadir}/mediatomb/web/icons/go-first.png %{_datadir}/mediatomb/web/icons/remove_all.png %{_datadir}/mediatomb/web/icons/folder_open.png %{_datadir}/mediatomb/web/icons/blank.gif %{_datadir}/mediatomb/web/right.html %{_datadir}/mediatomb/web/left.html %{_datadir}/mediatomb/web/index.html %{_datadir}/mediatomb/web/cm.xml %{_datadir}/mediatomb/web/js/iepngfix.htc %{_datadir}/mediatomb/web/js/nanotree.js %{_datadir}/mediatomb/web/js/items.js %{_datadir}/mediatomb/web/js/autoscan.js %{_datadir}/mediatomb/web/js/tree.js %{_datadir}/mediatomb/web/js/md5.js %{_datadir}/mediatomb/web/js/tasks.js %{_datadir}/mediatomb/web/js/tools.js %{_datadir}/mediatomb/web/js/prototype.js %{_datadir}/mediatomb/web/js/auth.js %{_datadir}/mediatomb/web/js/icons.js %{_datadir}/mediatomb/web/main.css %{_datadir}/mediatomb/web/top.html %{_datadir}/mediatomb/web/topright.html %{_datadir}/mediatomb/web/topleft.html %{_datadir}/mediatomb/web/favicon.ico %{_datadir}/mediatomb/sqlite3.sql %doc %{_mandir}/man1/mediatomb.1.gz %doc README INSTALL README.centos %clean rm -rf %{buildroot} %changelog * Mon Jun 30 2008 Jeffrey Crawford 0.11.0-1.el5 - Inital mediatomb packaging for CentOS -------------- next part -------------- diff -Naur mediatomb-0.11.0.orig/README.centos mediatomb-0.11.0/README.centos --- mediatomb-0.11.0.orig/README.centos 1969-12-31 16:00:00.000000000 -0800 +++ mediatomb-0.11.0/README.centos 2008-07-01 16:12:59.000000000 -0700 @@ -0,0 +1,17 @@ +IMPORTANT NOTES: +Assuming that CentOS is used for production servers. I felt it prudent to make +sure that mediatomb is run as an unprivilaged user. The default user is set up +to be "mediatomb". If you want to be able to share your media files, make sure +that the "mediatomb" user or "mediatomb" group can read your content. + +QUICK START: +Point your browser to http://:49152/ to start adding files that +you want to share with a media device on your network + +The configuration file can be found in /etc/mediatomb/config.xml. There are +comments in the file to set up the server to interact with some media devices. +Playstation 3 for example can be found by searching for "PS3". Some options are +set or changed depending on what devices you are integrating with. + +Note the comment as well to remove the "PC Directory" folder that is listed in +your media device. -------------- next part -------------- #! /bin/bash # # mediatomb Start/Stop the media server. # # chkconfig: 2345 95 55 # description: MediaTomb is a UPnP compatable media player. # processname: mediatomb # config: /etc/mediatomb # pidfile: /var/run/mediatomb/mediatomb.pid # Source function library. . /etc/init.d/functions prog="mediatomb" pidfile="/var/run/mediatomb/mediatomb.pid" config="/etc/mediatomb" logfile="/var/log/mediatomb/mediatomb.log" user="mediatomb" group="mediatomb" start() { echo -n $"Starting $prog: " if [ -e $pidfile ] && [ -e /proc/`cat $pidfile` ]; then echo -n $"cannot start $prog: $prog is already running."; failure $"cannot start $prog: $prog already running."; echo return 1 fi daemon $prog -c $config/config.xml -d -P $pidfile -l $logfile \ -u $user -g $user RETVAL=$? echo return $RETVAL } stop() { echo -n $"Stopping $prog: " if [ ! -e $pidfile ] && [ ! -e /proc`cat $pidfile 2> /dev/null` ]; then echo -n $"cannot stop $prog: $prog is not running." failure $"cannot stop $prog: $prog is not running." echo return 1; fi killproc $prog RETVAL=$? echo [ $RETVAL -eq 0 ] && rm -f $pidfile; return $RETVAL } rhstatus() { status $prog } restart() { stop start } reload() { echo -n $"Reloading $prog daemon configuration: " killproc $prog -HUP RETVAL=$? echo return $RETVAL } case "$1" in start) start ;; stop) stop ;; restart) restart ;; reload) reload ;; status) rhstatus ;; *) echo $"Usage: $0 {start|stop|status|reload|restart}" exit 1 esac -------------- next part -------------- /var/log/mediatomb/*.log { missingok sharedscripts postrotate /bin/kill -HUP `cat /var/run/mediatomb/mediatomb.pid 2> /dev/null` 2> /dev/null || true endscript } -------------- next part -------------- A non-text attachment was scrubbed... Name: mediatomb-etc-mediatomb-config.xml Type: text/xml Size: 5015 bytes Desc: not available Url : http://lists.rpmforge.net/pipermail/suggest/attachments/20080714/8601e44c/mediatomb-etc-mediatomb-config.xml From dries at ulyssis.org Tue Jul 15 17:55:35 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Tue Jul 15 23:22:14 2008 Subject: [suggest] unrar 3.8.2 In-Reply-To: <20080714151748.GA6793@palermo.priv2.gtn.it> References: <20080714151748.GA6793@palermo.priv2.gtn.it> Message-ID: <200807151755.35932.dries@ulyssis.org> On Monday 14 July 2008 05:17:48 pm Stefano Biagiotti wrote: > I'm using unrar from rpmforge. > # yum -d 0 list unrar > Installed Packages > unrar.x86_64 3.7.8-1.el4.rf installed > > Latest version is 3.8.2 > http://www.rarlab.com/rar/unrarsrc-3.8.2.tar.gz > > Can you please update to the latest version? Ok i've updated the spec file, thanks for the information. kind regards, Dries From andrea.francia at gmail.com Thu Jul 17 16:13:36 2008 From: andrea.francia at gmail.com (Andrea Francia) Date: Thu Jul 17 16:14:03 2008 Subject: [suggest] Request for adding trash-cli package to RPMforge.net Message-ID: <615a5cbc0807170713s722126d4o28fea10d607f4921@mail.gmail.com> Hello I want to know if the trash-cli project could be added to the rpmforge.net packages. The homepage is: http://code.google.com/p/trash-cli The sources are available at http://sourceforge.net/project/showfiles.php?group_id=87144 Currently I'm not able to create the rpm .spec file for myself, but I've created the rpm using the python distutils, i.e. with the command: python setup.py bdist_rpm The package could be added? The .spec file is compulsory to get it added to repository? There is some volunteer that want take care of creating it? -- Andrea Francia -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rpmforge.net/pipermail/suggest/attachments/20080717/c7da4ddb/attachment.html From dries at ulyssis.org Fri Jul 18 17:07:24 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Fri Jul 18 17:07:53 2008 Subject: [suggest] Request for adding trash-cli package to RPMforge.net In-Reply-To: <615a5cbc0807170713s722126d4o28fea10d607f4921@mail.gmail.com> References: <615a5cbc0807170713s722126d4o28fea10d607f4921@mail.gmail.com> Message-ID: <200807181707.24434.dries@ulyssis.org> On Thursday 17 July 2008 04:13:36 pm Andrea Francia wrote: > Hello I want to know if the trash-cli project could be added to the > rpmforge.net packages. > > The homepage is: http://code.google.com/p/trash-cli > The sources are available at > http://sourceforge.net/project/showfiles.php?group_id=87144 > > Currently I'm not able to create the rpm .spec file for myself, but I've > created the rpm using the python distutils, i.e. with the command: > python setup.py bdist_rpm > > The package could be added? > The .spec file is compulsory to get it added to repository? > There is some volunteer that want take care of creating it? Hello Andrea, I've added a spec file for trash-cli to the rpmforge svn. You can find it at http://svn.rpmforge.net/svn/trunk/rpms/trash-cli/trash-cli.spec kind regards, Dries From dsteinbrunner at pobox.com Tue Jul 22 17:44:30 2008 From: dsteinbrunner at pobox.com (David Steinbrunner) Date: Tue Jul 22 17:44:58 2008 Subject: [suggest] Requesting perl module Image::IPTCInfo Message-ID: Hello, It does not appear that Image::IPTCInfo is available via RPMforge and it would be great if it was. Thought I should drop the suggestion. Thanks, -- David Steinbrunner From dries at ulyssis.org Wed Jul 23 16:25:21 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Wed Jul 23 16:43:44 2008 Subject: [suggest] Requesting perl module Image::IPTCInfo In-Reply-To: References: Message-ID: <200807231625.21416.dries@ulyssis.org> On Tuesday 22 July 2008 05:44:30 pm David Steinbrunner wrote: > Hello, > > It does not appear that Image::IPTCInfo is available via RPMforge and it > would be great if it was. Thought I should drop the suggestion. Hello David, I've added a spec file for this perl module. kind regards, Dries From dsteinbrunner at pobox.com Thu Jul 24 21:11:46 2008 From: dsteinbrunner at pobox.com (David Steinbrunner) Date: Thu Jul 24 21:12:40 2008 Subject: [suggest] Request for perl module updates and an add Message-ID: Hello, I'm working with the replication feature that is apart of the latest DBIx::Class dev release: http://search.cpan.org/~lsaunders/DBIx-Class-0.08099_04/ It appear the module needs the latest versions of the following modules: Class::MOP Moose MooseX::AttributeHelpers The first two need updated in the RPMforge repos and the last would would need to be added. It would be appreciated if these changes could be made. Thanks, -- David Steinbrunner From dsteinbrunner at pobox.com Thu Jul 24 22:23:41 2008 From: dsteinbrunner at pobox.com (David Steinbrunner) Date: Thu Jul 24 22:24:09 2008 Subject: [suggest] Re: Request for perl module updates and an add In-Reply-To: Message-ID: David Steinbrunner wrote: > I'm working with the replication feature that is apart of the latest > DBIx::Class dev release: > > http://search.cpan.org/~lsaunders/DBIx-Class-0.08099_04/ > > It appear the module needs the latest versions of the following modules: > > Class::MOP > Moose > MooseX::AttributeHelpers > > The first two need updated in the RPMforge repos and the last would would need > to be added. It would be appreciated if these changes could be made. It seems Sub::Identify also needs updated. -- David Steinbrunner From JCasale at activenetwerx.com Thu Jul 24 22:49:05 2008 From: JCasale at activenetwerx.com (Joseph L. Casale) Date: Thu Jul 24 22:49:29 2008 Subject: [suggest] Net::SenderBase Message-ID: <49627735003F5C479100225C339F9FE06FE6AE0E90@Mail.activenetwerx.int> I have an rpm I have built for this based on Dries spec file in svn already. What do I do in order to submit this so it may be included in your repo? Thanks! jlc From dries at ulyssis.org Fri Jul 25 09:32:11 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Fri Jul 25 09:49:39 2008 Subject: [suggest] Add perl-MooseX-AttributeHelpers In-Reply-To: References: Message-ID: <200807250932.11946.dries@ulyssis.org> On Wednesday 09 July 2008 11:31:35 pm David Steinbrunner wrote: > Hello, > > I'm new to the RedHat/RPM/RPMForge scene but thanks to the direction of > collages, I'm here. Your site suggests that perl modules are easily added > so hopefully me requesting MooseX::AttributeHelpers to be added to the mix > is not an issue. I'm aware that it would also require some other modules > to be updated but when I sandbox installed all that is needed from cpan I > did not have issues using it. Hello, I've added a spec file for perl-MooseX-AttributeHelpers to the subversion. kind regards, Dries From dries at ulyssis.org Fri Jul 25 11:16:33 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Fri Jul 25 11:17:04 2008 Subject: [suggest] Contribution: perl-Tie-DxHash 1.03 In-Reply-To: References: Message-ID: <200807251116.34105.dries@ulyssis.org> On Tuesday 08 July 2008 12:58:03 am Eric Heydrick wrote: > Attached is a spec file for perl-Tie-DxHash that'll build the tie::dxhash > module from cpan. I based the spec on perl-Tie-IxHash from dag.wieers.com. > I tested on RHEL5.2. Feel free to include this in RPMforge. I don't wish > to be the maintainer. Thanks! I've included the spec file. kind regards, Dries From dries at ulyssis.org Fri Jul 25 12:03:19 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Fri Jul 25 13:01:51 2008 Subject: [suggest] Re: Request for perl module updates and an add In-Reply-To: References: Message-ID: <200807251203.19898.dries@ulyssis.org> On Thursday 24 July 2008 10:23:41 pm David Steinbrunner wrote: > David Steinbrunner wrote: > > I'm working with the replication feature that is apart of the latest > > DBIx::Class dev release: > > > > http://search.cpan.org/~lsaunders/DBIx-Class-0.08099_04/ > > > > It appear the module needs the latest versions of the following modules: > > > > Class::MOP > > Moose > > MooseX::AttributeHelpers > > > > The first two need updated in the RPMforge repos and the last would would > > need to be added. It would be appreciated if these changes could be > > made. > > It seems Sub::Identify also needs updated. i've updated those spec files in the svn and perl-MooseX-AttributeHelpers is added too. kind regards, Dries From dries at ulyssis.org Fri Jul 25 13:01:18 2008 From: dries at ulyssis.org (Dries Verachtert) Date: Fri Jul 25 13:01:58 2008 Subject: [suggest] Net::SenderBase In-Reply-To: <49627735003F5C479100225C339F9FE06FE6AE0E90@Mail.activenetwerx.int> References: <49627735003F5C479100225C339F9FE06FE6AE0E90@Mail.activenetwerx.int> Message-ID: <200807251301.18250.dries@ulyssis.org> On Thursday 24 July 2008 10:49:05 pm Joseph L. Casale wrote: > I have an rpm I have built for this based on Dries spec file in svn > already. What do I do in order to submit this so it may be included in your > repo? Hello Joseph, Dag and I both use scripts which build spec files +/- automatically from the subversion repository and which place the resulting rpm files at the correct location. So it's easier for us to simply make rpms ourselves. This takes some time, especially generating the metadata for smart/apt/yum. kind regards, Dries From JCasale at activenetwerx.com Fri Jul 25 17:54:35 2008 From: JCasale at activenetwerx.com (Joseph L. Casale) Date: Fri Jul 25 17:55:02 2008 Subject: [suggest] Net::SenderBase In-Reply-To: <200807251301.18250.dries@ulyssis.org> References: <49627735003F5C479100225C339F9FE06FE6AE0E90@Mail.activenetwerx.int> <200807251301.18250.dries@ulyssis.org> Message-ID: <49627735003F5C479100225C339F9FE06FE6AE0E95@Mail.activenetwerx.int> >Hello Joseph, >Dag and I both use scripts which build spec files +/- automatically from the >subversion repository and which place the resulting rpm files at the correct >location. So it's easier for us to simply make rpms ourselves. This takes >some time, especially generating the metadata for smart/apt/yum. >kind regards, >Dries I see, sorry I did not know this! I assumed you were simply helping me along:) I would much rather wait for your signed rpm then use my own, what is the schedule your script runs on so I may know when to check back? Thanks for the help and info. jlc From aluoor at gmail.com Sat Jul 26 18:44:08 2008 From: aluoor at gmail.com (Sven) Date: Sat Jul 26 18:44:34 2008 Subject: [suggest] getmsmp3.spec contribution for review (rip MP3 off MySpace profiles) Message-ID: <488B5458.6010206@gmail.com> Hi all Attached the SPEC file for getmsmp3 software. Getmsmp3 downloads MP3s off MySpace profiles. On my box (CentOS 5.2) it builds without errors and the installed RPM works well. The SPEC file is based on youtube-dl.spec. Please peer-review it and provide feedback. Thanks regards Sven -------------- next part -------------- # $Id$ # Upstream: Peter Willis, peterwwillis@yahoo.com Summary: Perl script that downloads MP3s off MySpace.com Name: getmsmp3 Version: 0.4 Release: 1 License: WTFPL Group: Applications/Internet URL: http://psydev.sourceforge.net/new/misc/getmsmp3 Source: http://psydev.sourceforge.net/new/misc/getmsmp3 BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root Buildarch: noarch Requires: perl >= 5.8.8 %description Getmsmp3 is a small Perl script that downloads MP3s off of MySpace profiles (including band playlists) to the current directory. The source code is released under the DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE :-) %prep %setup -c -T %build %install %{__rm} -rf %{buildroot} %{__install} -p -m0755 -D %{SOURCE0} %{buildroot}%{_bindir}/getmsmp3 %clean %{__rm} -rf %{buildroot} %files %defattr(-, root, root, 0755) %{_bindir}/getmsmp3 %changelog * Sat Jul 26 2008 Sven Aluoor - 0.4 - Initial package. From aye at shaw.ca Sun Jul 27 01:38:04 2008 From: aye at shaw.ca (David Savinkoff) Date: Sun Jul 27 01:38:32 2008 Subject: [suggest] libmpeg2 - SELinux text relocation issues (CentOS 5.2) Message-ID: libmpeg2 needs to be compiled with -fpic in SELinux to prevent the "text relocation" addressing problem in shared libraries. A solution is to simply add the following to libmpeg2.spec CFLAGS="$CFLAGS -fpic"; export CFLAGS The problem is caused by the code shown here: https://trac.videolan.org/libmpeg2/changeset/1184 Note the Message for this code: "libmpeg2/configure.incl: only avoid -fPIC on 32-bit x86 platforms, there have been too many breakage reports." The solution is suggested by the code shown here: https://trac.videolan.org/libmpeg2/changeset/1183 Note the Message for this code: "configure.ac: do not reset user-provided CFLAGS, they should know what they are doing." libmpeg2-0.5.1/configure and configure.ac contain the libtool -prefer-non-pic option to prevent gcc from compiling with -fpic . I believe this is an attempt to get more performance, but it conflicts with SELinux and the proper use of Dynamic Shared Obects. # The new patch was built, installed and ran without SELinux text relocation errors on CentOS 5.2 The following commands also show no Text Relocations: eu-readelf -d libmpeg2.so.0.1.0 | fgrep TEXTREL eu-readelf -d libmpeg2convert.so.0.0.0 | fgrep TEXTREL http://people.redhat.com/drepper/textrelocs.html has excellent information on shared objects and text relocation. # The libmpeg2.spec patch is: --- libmpeg2.spec 2008-07-26 22:07:45.000000000 +0000 +++ libmpeg2.CFLAGS.spec 2008-07-26 22:10:51.000000000 +0000 @@ -61,6 +61,7 @@ %setup %build +CFLAGS="$CFLAGS -fpic"; export CFLAGS %configure \ %ifnarch %{ix86} --disable-accel-detect \ From mic at npgx.com.au Sun Jul 27 04:13:52 2008 From: mic at npgx.com.au (Michael Mansour) Date: Sun Jul 27 04:14:45 2008 Subject: [suggest] awstats 6.8 RPM Message-ID: <20080727021110.M39647@npgx.com.au> Hi Dag, I noticed the new awstats 6.8 RPM has both the awstats.model.conf.rpmnew and awstats.localhost.localdomain.conf files populated with Windows "^M"'s, which I had to remove for them to be usable. This may be an oversight by the awstats developer, but it is a major one when installing on UNIX/Linux. Should this be fixed in RPMforge or reported to the developer to then release a bugfix? Michael. From nkadel at gmail.com Sun Jul 27 12:30:24 2008 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sun Jul 27 12:20:18 2008 Subject: [suggest] Re: suggest Digest, Vol 37, Issue 17 In-Reply-To: <20080727100033.098023180BE@pooch.vmhosting.org> References: <20080727100033.098023180BE@pooch.vmhosting.org> Message-ID: <488C4E40.2010103@gmail.com> suggest-request@lists.rpmforge.net wrote: > > Message: 3 > Date: Sun, 27 Jul 2008 13:13:52 +1100 > From: "Michael Mansour" > Subject: [suggest] awstats 6.8 RPM > To: "suggest lists.rpmforge.net" > Message-ID: <20080727021110.M39647@npgx.com.au> > Content-Type: text/plain; charset=iso-8859-1 > > Hi Dag, > > I noticed the new awstats 6.8 RPM has both the awstats.model.conf.rpmnew and > awstats.localhost.localdomain.conf files populated with Windows "^M"'s, which > I had to remove for them to be usable. > > This may be an oversight by the awstats developer, but it is a major one when > installing on UNIX/Linux. > > Should this be fixed in RPMforge or reported to the developer to then release > a bugfix? > > Michael. > > Wait, wait! I know this one! The answer is 'yes'. Some packages don't update very often, and thus would take an inconvenitnely long time to get updated by the maintainers. Others update very quickly, and the fix propagates very quickly from upstream, so it really varies. Take a look at the awstats source trees and see how often new releases happen: that will help you decide. From pelletierr at csdhr.qc.ca Mon Jul 28 20:01:36 2008 From: pelletierr at csdhr.qc.ca (Pelletier, Robert) Date: Mon Jul 28 20:01:59 2008 Subject: [suggest] Amavisd-New / Netatalk Message-ID: <2E2EF442EFC94A4DB50D15A897C6ADAD66214B@VENUS.admin.csdhr> Hey there! I was wondering if it is possible to update Amavisd-New to 2.6.1, the latest version available, and if it was possible to create a RPM package for NetAtalk 2.0.3. Thanks you for you time and implication in this project, you are saving me a whole lot of time and have been for at least 2 years! Robert Pelletier Technicien informatique dans l'?quipe d'infrastructure Service des technologies de l'information Commission Scolaire des Hautes-Rivi?res T?l?phone : (450) 359-6411 poste 7384 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rpmforge.net/pipermail/suggest/attachments/20080728/36104b1d/attachment.html From nkadel at gmail.com Wed Jul 30 15:14:13 2008 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Wed Jul 30 15:14:36 2008 Subject: [suggest] Please update HylaFAX Message-ID: HylaFAX+ has had a recent update, to version 5.2.6, at http://sourceforge.net/project/showfiles.php?group_id=148904&package_id=164873. Can our faithful repository maintainers update this? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rpmforge.net/pipermail/suggest/attachments/20080730/cac27d86/attachment.html From nkadel at gmail.com Wed Jul 30 17:24:25 2008 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Wed Jul 30 17:24:50 2008 Subject: [suggest] Please package mnogosearch Message-ID: Skipped content of type multipart/alternative-------------- next part -------------- %{?dist: %{expand: %%define dist_%dist 1}} Summary: A fast WWW search engine for websites Name: mnogosearch Version: 3.3.7 Release: 0%{?dist:.%{dist}}%{?pext} License: GPL Group: Applications/Internet Source0: http://www.%{name}.org/Download/%{name}-%{version}.tar.gz URL: http://www.%{name}.org/ Buildroot: /var/tmp/%{name}-root Vendor: Lavtech.Com Corp. Packager: Peter Pramberger Provides: %{name}%{?pext} Requires: mysql openssl readline unixODBC %if 0%{?dist_el3} Requires: rh-postgresql-libs %else Requires: postgresql-libs %endif Prereq: coreutils glibc BuildPrereq: coreutils glibc-devel gcc make BuildPrereq: mysql-devel openssl-devel BuildPrereq: readline-devel unixODBC-devel %if 0%{?dist_el3} BuildPrereq: rh-postgresql-devel %else BuildPrereq: postgresql-devel %endif ExclusiveOS: linux %description mnoGoSearch (formerly known as UdmSearch) is a full-featured Web search engine which you can use to build search engines over HTTP, HTTPS, FTP, and NTTP servers, local files, and database big text fields. It supports Oracle, MySQL, PostgreSQL, miniSQL, Solid, Virtuoso, InterBase, SAPDB, iODBC, EasySoft ODBC, and unixODBC database backends. mnoGoSearch is also known to work with MS SQL, SyBase, and Oracle through ODBC. It has text/html and text/plain built-in support, and external parsers support for other document types. An automatic language/charset guesser for more 70 language/ charset combinations is included, along with basic authorization support, and you may index password-protected intranet HTTP servers with proxy authorization support. %package devel Summary: Development tools for %{name} Group: Development/Libraries Provides: %{name}-devel%{?pext} Requires: %{name} = %{version}-%{release} %{name}%{?pext} %description devel The %{name}-devel package contains the static libraries and header files for developing software using %{name}. %prep %setup -q %build %configure \ CFLAGS="${RPM_OPT_FLAGS}" \ %ifarch x86_64 LDFLAGS="-L%{_libdir}/mysql" \ %endif --sysconfdir=%{_sysconfdir}/%{name} \ --localstatedir=%{_localstatedir}/cache/%{name} \ --datadir=%{_datadir}/%{name} \ --enable-shared \ --enable-static \ --enable-syslog \ --with-openssl=%{_prefix} \ --with-zlib \ --with-readline \ --with-mysql=%{_prefix} \ --with-pgsql=%{_prefix} \ --with-unixODBC=%{_prefix} %{__make} \ all %install [ -n "${RPM_BUILD_ROOT}" -a "${RPM_BUILD_ROOT}" != "/" ] && %{__rm} -rf ${RPM_BUILD_ROOT} %{__mkdir_p} ${RPM_BUILD_ROOT}%{_localstatedir}/cache/%{name}/{cache,raw,splitter,tree} %{__mkdir_p} ${RPM_BUILD_ROOT}%{_localstatedir}/www/icons %{__make} \ DESTDIR=${RPM_BUILD_ROOT} \ install %{__install} -m 0644 misc/*.gif ${RPM_BUILD_ROOT}%{_localstatedir}/www/icons %{__rm} -rf ${RPM_BUILD_ROOT}%{_prefix}/doc %post ldconfig %postun ldconfig %clean [ -n "${RPM_BUILD_ROOT}" -a "${RPM_BUILD_ROOT}" != "/" ] && %{__rm} -rf ${RPM_BUILD_ROOT} %files %defattr(-,root,root) %doc AUTHORS COPYING ChangeLog INSTALL NEWS README* TODO %doc doc/*.html doc/*.xml doc/*.css doc/*.dsl %doc %dir doc/samples %attr(755,root,root) %dir %{_sysconfdir}/%{name} %config(noreplace) %{_sysconfdir}/%{name}/* %{_bindir}/* %{_libdir}/*.so* %{_sbindir}/* %dir %{_datadir}/%{name} %{_datadir}/%{name}/* %{_mandir}/man1/* %{_mandir}/man5/* %attr(755,root,root) %dir %{_localstatedir}/cache/%{name} %attr(755,root,root) %dir %{_localstatedir}/cache/%{name}/* %{_localstatedir}/www/icons/* %files devel %defattr(-,root,root) %{_includedir}/* %{_libdir}/*.*a %changelog * Wed Jul 30 2008 nkdel@gmail.com 3.3.7-0 - Update version (3.3.7) * Fri Oct 19 2007 peter.pramberger@member.fsf.org 3.2.43-8 - new version (3.2.43) * Thu Oct 11 2007 peter.pramberger@member.fsf.org 3.2.42-8 - new version (3.2.42) - removed Oracle support * Thu Dec 14 2006 peter.pramberger@member.fsf.org 3.2.40-7 - new version (3.2.40) * Thu Sep 07 2006 peter.pramberger@member.fsf.org - new version (3.2.39) * Fri Nov 18 2005 peter.pramberger@member.fsf.org - fixed directory permissions in config directory * Wed Nov 16 2005 peter.pramberger@member.fsf.org - created From brandond at uoregon.edu Thu Jul 31 05:35:15 2008 From: brandond at uoregon.edu (Brandon Davidson) Date: Thu Jul 31 05:35:40 2008 Subject: [suggest] New to the list Message-ID: <489132F3.7010708@uoregon.edu> Hi all, I just joined the list at Dag's suggestion, as I understand this is where new/updated package spec file submissions go. I'm somewhat new to the packaging game, so please correct me if I do anything wrong. I'm about to submit spec files for: trac 0.11 (update) python-setuptools 0.6c8 (new) python-genshi 0.5.1 (new) I'm not sure what the naming scheme is for Python modules. For example, Clearsilver just clearsilver, and Trac is just trac, but Twisted is python-twisted. I'll let someone else decide; I'm submitting in the format that makes the most sense to me. Thanks, -Brandon -- Brandon Davidson Systems Administrator University of Oregon Neuroinformatics Center (541) 346-2417 brandond@uoregon.edu Key Fingerprint 1F08 A331 78DF 1EFE F645 8AE5 8FBE 4147 E351 E139 From brandond at uoregon.edu Thu Jul 31 05:40:24 2008 From: brandond at uoregon.edu (Brandon Davidson) Date: Thu Jul 31 05:40:49 2008 Subject: [suggest] Trac 0.11 update Message-ID: <48913428.6060407@uoregon.edu> The attached spec updates Trac to 0.11, the latest stable release. -- Brandon Davidson Systems Administrator University of Oregon Neuroinformatics Center (541) 346-2417 brandond@uoregon.edu Key Fingerprint 1F08 A331 78DF 1EFE F645 8AE5 8FBE 4147 E351 E139 -------------- next part -------------- # $Id$ # Authority: dag %define real_name Trac %define version 0.11 %define release 1 Name: trac Summary: Integrated SCM, wiki, issue tracker and project environment Version: %{version} Release: %{release}.rf License: BSD Group: Development/Libraries URL: http://trac.edgewall.org/ Packager: Dag Wieers Vendor: Dag Apt Repository, http://dag.wieers.com/apt/ Source0: http://ftp.edgewall.com/pub/trac/%{real_name}-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot BuildArch: noarch BuildRequires: python >= 2.3, python-setuptools => 0.6 Requires: python >= 2.3, python-sqlite >= 1.0, subversion >= 1.0.0 Requires: python-genshi >= 0.5, python-setuptools >= 0.6, webserver %description Trac is a minimalistic web-based software project management and bug/issue tracking system. It provides an interface to the Subversion revision control systems, an integrated wiki, flexible issue tracking and convenient report facilities. %prep %setup -n %{real_name}-%{version} %build python setup.py build %install python setup.py install --single-version-externally-managed --optimize=1 --root=$RPM_BUILD_ROOT --record=INSTALLED_FILES %clean rm -rf $RPM_BUILD_ROOT %files -f INSTALLED_FILES %defattr(-,root,root) %changelog * Wed Jul 30 2008 Brandon Davidson 0.11-1 - Updated to release 0.11. - Now requires/uses python-setuptools. - New upstream no longer includes shared static content, so this release also drops the sample apache config, as it is invalid without any static content. * Fri Apr 27 2007 Dag Wieers - 0.10.4-1 - 5226+/dag - Updated to release 0.10.4. * Sat Mar 10 2007 Dag Wieers - 0.10.3.1-1 - Updated to release 0.10.3.1. * Wed Dec 13 2006 Dag Wieers - 0.10.3-1 - Updated to release 0.10.3. * Wed Nov 15 2006 Dag Wieers - 0.10.2-1 - Updated to release 0.10.2. * Thu Nov 09 2006 Dag Wieers - 0.10.1-1 - Updated to release 0.10.1. * Sat Sep 30 2006 Dag Wieers - 0.10-1 - Updated to release 0.10. * Sun Jul 09 2006 Dag Wieers - 0.9.6-1 - Updated to release 0.9.6. * Sat Apr 22 2006 Dries Verachtert - 0.9.5-1 - Updated to release 0.9.5. * Sat Feb 18 2006 Dag Wieers - 0.9.4-1 - Updated to release 0.9.4. * Wed Jan 11 2006 Dag Wieers - 0.9.3-1 - Updated to release 0.9.3. * Tue Dec 06 2005 Dries Verachtert - 0.9.2-1 - Updated to release 0.9.2. * Tue Nov 15 2005 Dries Verachtert - 0.9-1 - Updated to release 0.9. * Tue Jul 19 2005 Dag Wieers - 0.8.4-1 - Updated to release 0.8.4. * Mon Jul 11 2005 Matt Whiteley - 0.8.3-1 - Updated to release 0.8.3. * Wed Jun 01 2005 Matt Whiteley - 0.8.2-1 - Updated to release 0.8.2. - Fixed env in apache conf.d file. * Fri Mar 04 2005 Dag Wieers - 0.8.1-1 - Updated to release 0.8.1. * Wed Jan 19 2005 Dag Wieers - 0.8-4 - Fixed typo causing missing trac.conf. (Simon Perreault) * Mon Nov 29 2004 Dag Wieers - 0.8-3 - Fixed buildroot in %%install phase. (Dimiter Manevski) * Mon Nov 29 2004 Dag Wieers - 0.8-2 - Remove the deprecated subversion-python requirement. (Dimiter Manevski) * Sun Nov 21 2004 Dag Wieers - 0.8-1 - Updated to release 0.8. * Fri Jun 04 2004 Dag Wieers - 0.7.1-1 - Updated to release 0.7.1. * Sun May 30 2004 Dag Wieers - 0.7.0-1 - Updated to release 0.7.0. * Fri Apr 30 2004 Dag Wieers - 0.6.1-1 - Initial package. (using DAR) From brandond at uoregon.edu Thu Jul 31 05:44:16 2008 From: brandond at uoregon.edu (Brandon Davidson) Date: Thu Jul 31 05:44:45 2008 Subject: [suggest] python-setuptools 0.6c8 Message-ID: <48913510.4080501@uoregon.edu> The attached is a spec file for setuptools 0.8c6 Setuptools is required to build both Trac and Genshi, as well as most recent Trac plugins. http://peak.telecommunity.com/DevCenter/setuptools setuptools is a collection of enhancements to the Python distutils (for Python 2.3.5 and up on most platforms; 64-bit platforms require a minimum of Python 2.4) that allow you to more easily build and distribute Python packages, especially ones that have dependencies on other packages. -- Brandon Davidson Systems Administrator University of Oregon Neuroinformatics Center (541) 346-2417 brandond@uoregon.edu Key Fingerprint 1F08 A331 78DF 1EFE F645 8AE5 8FBE 4147 E351 E139 -------------- next part -------------- # $Id$ # Authority: dag %define real_name setuptools %define version 0.6c8 %define release 1 Summary: Download, build, install, upgrade, and uninstall Python packages -- easily! Name: python-%{real_name} Version: %{version} Release: %{release}.rf Source0: http://pypi.python.org/packages/source/s/setuptools/%{real_name}-%{version}.tar.gz License: PSF or ZPL Group: Development/Libraries Url: http://pypi.python.org/pypi/setuptools Packager: Dag Wieers Vendor: Dag Apt Repository, http://dag.wieers.com/apt/ BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot Prefix: %{_prefix} # Proper lib installation requires Python 2.4 on 64bit systems %ifarch ppc64 x86_64 sparc64 BuildRequires: python >= 2.4 Requires: python >= 2.4 %else BuildRequires: python >= 2.3 Requires: python >= 2.3 %endif %description setuptools is a collection of enhancements to the Python distutils that allow you to more easily build and distribute Python packages, especially ones that have dependencies on other packages. %prep %setup -n %{real_name}-%{version} %build python setup.py build %install python setup.py install --single-version-externally-managed --optimize=0 --root=$RPM_BUILD_ROOT --record=INSTALLED_FILES %clean rm -rf $RPM_BUILD_ROOT %files -f INSTALLED_FILES %defattr(-,root,root) %changelog * Wed Jul 30 2008 Brandon Davidson 0.6c8-1 - Initial package From brandond at uoregon.edu Thu Jul 31 05:48:37 2008 From: brandond at uoregon.edu (Brandon Davidson) Date: Thu Jul 31 05:49:02 2008 Subject: [suggest] python-genshi 0.5.1 Message-ID: <48913615.7050704@uoregon.edu> The attached is a spec file for Genshi 0.5.1 Genshi is the HTML templating system used by Trac and possibly other Python projects. http://genshi.edgewall.org/ Genshi is a Python library that provides an integrated set of components for parsing, generating, and processing HTML, XML or other textual content for output generation on the web. -- Brandon Davidson Systems Administrator University of Oregon Neuroinformatics Center (541) 346-2417 brandond@uoregon.edu Key Fingerprint 1F08 A331 78DF 1EFE F645 8AE5 8FBE 4147 E351 E139 -------------- next part -------------- # $Id$ # Authority: dag %define real_name Genshi %define version 0.5.1 %define release 1 Summary: Python toolkit for generation of output for the web Name: python-genshi Version: %{version} Release: %{release}.rf Source0: http://ftp.edgewall.com/pub/genshi/%{real_name}-%{version}.tar.gz License: BSD Group: Development/Libraries Url: http://genshi.edgewall.org/wiki/ Packager: Dag Wieers Vendor: Dag Apt Repository, http://dag.wieers.com/apt/ BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot Prefix: %{_prefix} BuildRequires: python >= 2.3, python-setuptools >= 0.6 Requires: python >= 2.3, python-setuptools => 0.6 %description Genshi is a Python library that provides an integrated set of components for parsing, generating, and processing HTML, XML or other textual content for output generation on the web. %prep %setup -n %{real_name}-%{version} %build python setup.py build %install python setup.py install --single-version-externally-managed --optimize=1 --root=$RPM_BUILD_ROOT --record=INSTALLED_FILES %clean rm -rf $RPM_BUILD_ROOT %files -f INSTALLED_FILES %defattr(-,root,root) %changelog * Wed Jul 30 2008 Brandon Davidson 0.5.1-1 - Initial package