[ATrpms-users] Re: mythtv on centos4

2005-07-28 Thread Axel Thimm
On Wed, Jul 27, 2005 at 10:34:07AM -0400, Wayne Steenburg wrote:
 O
   then if I do an 'up2date --dry-run mythtv-suite' I end up with:
   
   Unresolvable chain of dependencies:
   mythtv-suite-0.18.1-55.at http://mythtv-suite-0.18.1-55.at requires 
   mythplugins = 0.18.1
   
   If I look in http://atrpms.net/dist/el4/mythplugins/ everything seems to 
   be 
   x86_64 which sadly isn't my architecture!
   Am I looking in the wrong place?
  
  No, mythplugins requires transcode and transcode only builds for el4-x86_64
 
 
 Axel, is this a change from how this was previously done?

No, previously transcode would not build anymore for any distro due to
libquicktime/ffmpeg, so the mythplugins were built w/o
transcode. After transcode would build for 12/14 distributions I
switched it on again.

 I have all the mythplugins for el4 i386 compiled without transcode
 support.  I don't mind not being able to rip a dvd or transcode a
 recording, but not having mythmusic, mythdvd, mythgame, etc, would
 kind of suck.

Yes, the fact that these are bundled in one tar files now makes it
rather hard. Before 0.18 these were separate and a failing mythdvd
would not affect the rest.

A workaround would be to introduce more switches to the specfile, but
perhaps finidng the reason transcode fails would be easier ...

 I'm currently helping a friend redo his mythbox using CentOS 4 and
 I'll need to bring over some loose rpms from apt's cache to help him
 finish.
 
 Are your build logs publicly available?

No, unfortunately not. They should become so, and I hope to find time
in the next eaons to redo the whole website/repo creation thing (that
last a couple of eaons by themselves ...).

 I'm no expert, but I'd be happy to take a look at them.  I found
 transcode for el4 i386 at one of those other repos so I know it
 can compile.  But will it run properly... :)

The builds end with

gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_REENTRANT -DMOD_PATH=\/usr/lib/transcode\ 
-I.. -I../src -I../libtc -I/usr/include -I../libac3 -I../avilib -I/usr/include 
-I/usr/include -I/usr/include -I/usr/include/libxml2 -I../libvo -I/usr/include 
-I/usr/include -I/usr/include -DUSE_XIO -I../libxio -Wall -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe 
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 -march=i386 -mtune=pentium4 
-fasynchronous-unwind-tables -MT import_im.lo -MD -MP -MF .deps/import_im.Tpo 
-c import_im.c -o import_im.o /dev/null 21
/bin/sh ../libtool --mode=link gcc  -Wall -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe 
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 -march=i386 -mtune=pentium4 
-fasynchronous-unwind-tables   -o import_im.la -rpath /usr/lib/transcode 
-module -avoid-version  import_im.lo -lMagick -lz -lm -lm  -lm -lz -ldl
libtool: link: cannot find the library `/usr/lib/libxml2.la'
make[3]: *** [import_im.la] Error 1

The reason is that Red Hat manically kills *.la files, but this seems
to only work if all *.la files are removed. When a project still gets
to ship its *.la files the dependencies are checked through the la
files and fail. I suspect ImageMagick.

Try to rebuild, it should stop at the same spot. If not, you'll have
found the fix :)
-- 
Axel.Thimm at ATrpms.net


pgp98PyRot6Jq.pgp
Description: PGP signature
___
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users


[ATrpms-users] Re: atrpms, gcc, libtool and what did i do wrong?

2005-07-28 Thread Robert P. J. Day
On Thu, 28 Jul 2005, Axel Thimm wrote:
...
 Try using smart to resolve this:

 yum install smart
 smart update
 smart upgrade

 Loading cache...
 Updating cache...    
 [100%]

 Computing transaction...

 Upgrading packages (32):
   aprlibgfortran
   apr-devel  libgnat
   audit-libs libmudflap
   cpplibmudflap-devel
   gcclibobjc
   gcc-c++libstdc++
   gcc-gfortran   libstdc++-devel
   gcc-gnat   mgetty
   gcc-java   mgetty-sendfax
   gcc-objc   mgetty-viewfax
   gnome-panelmgetty-voice
   gnome-panel-devel  system-config-bind
   libgcc system-config-printer
   libgcj system-config-printer-gui
   libgcj-devel   tar
   libgcj-src util-linux

 Downgrading packages (1):
   libtool

 63.6MB of package files are needed. 571.8kB will be used.

 Confirm changes? (Y/n):

i just tried the above and, surprisingly, i was told No interesting
upgrades available, even though i know at least gcc can be upgraded.

rday

___
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users


[ATrpms-users] Dag FC1 repo for newer yum version

2005-07-28 Thread Michael Mansour
Hi Axel,

In upgrading one of my FC1 machines to the new yum you've supplied in your repo:

yum-2.3.4-62.rhfc1.at

The following dependencies were installed:

I will install/upgrade these to satisfy the dependencies:
[deps: libxml2_2 2.6.19-1_20.rhfc1.at.i386]
[deps: libbeecrypt6 4.1.2-8_9.rhfc1.at.i386]
[deps: sqlite-devel 3.1.2-2.99_1.rhfc1.at.i386]
[deps: rpm-build 4.4.1-22_48.rhfc1.at.i386]
[deps: librpm4.4 4.4.1-22_48.rhfc1.at.i386]
[deps: neon-devel 0.24.7-2.99_1.rhfc1.at.i386]
[deps: rpm-devel 4.4.1-22_48.rhfc1.at.i386]
[deps: popt 1.10.1-22_48.rhfc1.at.i386]
[deps: neon 0.24.7-2.99_1.rhfc1.at.i386]
[deps: librpm4.2 4.2.1-0.30_19.6.rhfc1.at.i386]
[deps: atrpms-package-config 99-1.rhfc1.at.i386]
[deps: rpm 4.4.1-22_48.rhfc1.at.i386]
[deps: pythonabi 2.2.3-1.rhfc1.at.i386]
[deps: libxml2 2.6.19-1_20.rhfc1.at.i386]
[deps: elfutils-devel 0.89-2.i386]
[deps: python-elementtree 1.2.6-3.99_1.rhfc1.at.i386]
[deps: libxml2-python 2.6.19-1_20.rhfc1.at.i386]
[deps: rpm-python24 4.4.1-21_5.rhfc1.at.i386]
[deps: libxml2-python24 2.6.19-1_21.rhfc1.at.i386]
[deps: python-sqlite 1.1.6-0.99_1.rhfc1.at.i386]
[deps: sqlite 3.1.2-2.99_1.rhfc1.at.i386]
[deps: python-urlgrabber 2.9.6-0.99_1.rhfc1.at.noarch]
[deps: rpm-python 4.4.1-22_48.rhfc1.at.i386]
[deps: libxml2-devel 2.6.19-1_20.rhfc1.at.i386]
Is this ok [y/N]: y

I notice there the atrpms-package-config package, as this only contained
atrpms.repo and base.repo, I decided to also install medley-package-config:

medley-package-config-99-1.rhfc1.at

this seemed to contain everything I wanted (actually more than I wanted) but
also missed newrpms:

[newrpms.sunsite.dk]
name=Fedora Core $releasever NewRPMS.sunsite.dk
baseurl=http://newrpms.sunsite.dk/apt/redhat/en/i386/fc$releasever

which I added myself as a repo drop file.

Anyway, running a yum check-update, al the kde-redhat and jpackage stuff
failed so I added enable=0 to each of those repoid's, and then ran again:

# yum check-update
Setting up repositories
dries 100% |=|  951 B00:00
atrpms100% |=|  951 B00:00
http://apt.sw.be/fedora/1/en/i386/dag/repodata/repomd.xml: [Errno 4] IOError:
HTTP Error 404: Date: Fri, 29 Jul 2005 01:52:53 GMT
Server: Apache/2.1.5-dev (Unix)
Content-Length: 314
Content-Type: text/html; charset=iso-8859-1
X-Cache: MISS from jewel.micoots.com
Proxy-Connection: close
Trying other mirror.
Cannot open/read repomd.xml file for repository: dag
failure: repodata/repomd.xml from dag: [Errno 256] No more mirrors to try.
Error: failure: repodata/repomd.xml from dag: [Errno 256] No more mirrors to 
try.

This fails on the dag repo. Checking the file:

# cat dag.repo
#
#
[dag]
name=Fedora Core 1 - i386 - Dag's repo
baseurl=http://apt.sw.be/fedora/1/en/i386/dag
failovermethod=priority
enabled=1

and comparing to my older dag repo entry for yum 2.0:

[dag]
name=Dag RPM Repository for Fedora Core
baseurl=http://apt.sw.be/fedora/$releasever/en/$basearch/dag

Its exactly the same. So I went to Dag's website:

http://apt.sw.be/fedora/1/en/i386/dag/

RPMS/   28-Jul-2005 02:41-   
headers/28-Jul-2005 02:41-  

which doesn't contain the required repodata directory.

This seems to mean that when upgrading to yum 2.3.4, we lose access to Dag's
repo which seems to be yum 2.0 compatible?

Is there a way to make this work?

Thanks.

Michael.


___
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users