Re: [packman] [PM] crystalspace-utils 1.2.1 (openSUSE 11.0/i586)

2008-12-20 Diskussionsfäden Toni
Am Sonntag, 21. Dezember 2008 schrieb Roland Holder:
> Servus Toni!
>
> Ich wollte eben im Betreff benanntes Paket auf meine openSuSE 11.0
> installieren und bekomme dabei reproduzierbar einen buffer overflow.
> Dabei läuft der RPM-Fortschrittsbalken komplett durch und danach
> kommende Scripte verursachen wohl das Problem. Die komplette Ausgabe
> hänge ich mal nicht an, kann sie aber auf Wunsch nachliefern. Sie ist
> nur viele hundert Zeilen lang (backtrace-Ausgabe).

was hast du denn für crystalspace Pakete bereits installiert ?
rpm -qa | grep crystal

was steht in dem logfile:
/tmp/crystalspace-*-install.log ?
(* sollte der Versionsnummer entsprechen)

im %post script wird eigentlich nur ein cslight -video=null für bestimmte maps 
ausgeführt um zu vermeiden, das es beim ersten Start ewig dauert...

evtl mal eine Installation mit rpm -Uhv --noscripts  probieren.

> Vielen Dank für Deine Mühen, Rolle

-- 
have fun
Toni

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] [PM] crystalspace-utils 1.2.1 (openSUSE 11.0/i586)

2008-12-20 Diskussionsfäden Roland Holder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Servus Toni!

Ich wollte eben im Betreff benanntes Paket auf meine openSuSE 11.0
installieren und bekomme dabei reproduzierbar einen buffer overflow.
Dabei läuft der RPM-Fortschrittsbalken komplett durch und danach
kommende Scripte verursachen wohl das Problem. Die komplette Ausgabe
hänge ich mal nicht an, kann sie aber auf Wunsch nachliefern. Sie ist
nur viele hundert Zeilen lang (backtrace-Ausgabe).


Vielen Dank für Deine Mühen, Rolle
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAklNiPAACgkQ23ZOxtu/pP1QtgCdHDobTeEB6Ri8p6yP8JRd9XU6
jZUAn345YZIpZNa6rBUtiKXHRypt1WTq
=ThxV
-END PGP SIGNATURE-

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] [PM] libdvdnav4 4.1.3-1.pm.1 (openSUSE 10.3/i586)

2008-12-20 Diskussionsfäden Malte Gell
Hallo,

libdvdnav 4.1.3 erzeugt bei MPlayer einen Absturz, wenn man eine DVD 
abspielen will, der Aufruf lautet:

mplayer dvdnav://2 -dvd-device /dev/sr1

Der Fehler ist reproduzierbar. Ein manuelles Downgrade zu libdvdnav 
4.1.1 hat bei mir geholfen. Wäre es daher nicht sinnvoll, ein neues 
Paket mit einem Downgrade anzubieten, damit sich wieder DVDs abspielen 
lassen?

Gruß
Malte

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] MPlayer-1.0rc2_r27637-3.pm.3 not stable?

2008-12-20 Diskussionsfäden Malte Gell
On Samstag, 20. Dezember 2008, Malte Gell wrote:
> Hi there,
>
> I installed MPlayer-1.0rc2_r27637-3.pm.3 on openSUSE 10.3 and MPlayer
> can't even play a DVD.
>
> E.g. mplayer dvdnav://2 -dvd-device /dev/sr1 causes MPlayer to crash.
> So my question is, is this version too unstable to use it?

Ok, I now found out, this is actually a libdvdnav issue. Packman 
provides libdvdnav 4.1.3 which causes this behaviour. A downgrade to 
libdvdnav 4.1.1 has solved the issue. It would be nice if Packman would 
also provide a downgrade, so people can play DVDs with MPlayer again.

Malte

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] MPlayer-1.0rc2_r27637-3.pm.3 not stable?

2008-12-20 Diskussionsfäden Malte Gell
Hi there,

I installed MPlayer-1.0rc2_r27637-3.pm.3 on openSUSE 10.3 and MPlayer 
can't even play a DVD.

E.g. mplayer dvdnav://2 -dvd-device /dev/sr1 causes MPlayer to crash. So 
my question is, is this version too unstable to use it?

Regards
Malte

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Packman and Contrib cooperation

2008-12-20 Diskussionsfäden Detlef Reichelt
Hi Pavol,

Am Thu, 18 Dec 2008 18:02:31 +0100
schrieb Pavol Rusnak :

>I have an idea, or proposal if you wish: what do you think of
> moving all the "clean" packages from Packman to this new and shiny
> Contrib repository? :)

thats not realy good for packman to host only the none clean packages,
Now all users say "add packman as a standard repo to get more
packages!". If we only host non clean packages, all users would say "use
packman for all the non legal stuff!". Never wakeup sleeping dogs

Detlef

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] [PM] mediatomb 0.11.0 (openSUSE 10.3/i586)

2008-12-20 Diskussionsfäden Toni
Am Samstag, 20. Dezember 2008 schrieb stefan.berg...@web.de:
> Hi!
>
> I had severe problems getting mediatomb up running / responding. I solved
> it changing the following points (in order of importance):
>
> In /etc/mediatomb/config.xml change:
> /etc/mediatomb
> to
> /var/lib/mediatomb
> then mediatomb should be running / be accessible over http!
> (By the way, the file /var/lib/mediatomb/config.xml is / was a copy of
> /etc/init.d/mediatomb )
did you copy over those files yourself to /var/lib/mediatomb ?
And I guess you are using the sqlite variant, because those directories are 
created by the package mediatomb-sqlite. The sample config.xml I'm using 
where provided a user George Pantazis, but AFAIK he was using a mysql 
database. So I'll check this and perhaps I need to provide a sample config 
for each database back-end.

> In /etc/init.d/mediatomb change the chown statements. Mediatomb is started
> as user 'mediatomb' therefore it has no access to the files if they belong
> to 'nobody'. E.g. change
>  chown nobody $MT_PIDFILE
> to
>  chown "${MT_USER}:${MT_GROUP}" $MT_PIDFILE
why ?
the run-level scripts are started from a root account on machine boot up, the 
pid-file contains no information. And mediatomb does nothing with this file.
It should contain the pid of the mediatomb for killing the process. At the 
moment this is done with killproc. So the actual run-level script implies 
that only one mediatomb process is running on one machine.

> I also changed the used IP to use the Interface, although that should not
> be required. But if getting the IP address it is a good idea to do a
>  export LC_ALL=POSIX
> before calling any commands. My root account comes up with german messages
> by default! I did not change / set this, but that's the way the standard
> configuration does it. Alternative you may replace
> IFACE_IP=`ifconfig | grep -i "$MT_INTERFACE" -A 1|grep "inet addr"|cut -d "
> " -f 12|cut -d ":" -f 2` with
> IFACE_IP=`LC_ALL=POSIX ifconfig | grep -i "$MT_INTERFACE" -A 1|grep "inet
> addr"|cut -d " " -f 12|cut -d ":" -f 2`
this is a good fix, I'll add this in next release, my root-account is in 
english so the command is working for me. But in other languages the output 
could differ and the grep won't match.

> Nevertheless, many thanks providing mediatomb!
thx for feedback and proposed improvals!

> Merry Christmas and a happy new year from Munich,
Merry Christmas and a happy New Year from Wiesbaden,
>  Stefan

-- 
have fun
Toni

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman