[root@localhost ~]# yum install vlc
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
The yum is not looking for a repo to get this mess. How can
this be? I have removed all livna repos but it does not even
use them.
Hasn't this thread gotten too long. GO GIANTS!!!!
See you in Green Bay,
Max
It was hard to do things on the computer and watch My Cowgirls
get beat again. Hard to understand but it appears the Q'back has
forgot how to pass.
Karl
The way things are going on this thread , i don't know that I'd
split my attention between the computer and the television.
4th and game ......interception!!!!GO GIANTS!!!
-Max
I went the manual way. I used rpm -i rpmname and it printed a long
list of dependents and I one by satisfied the dependents. But when
I tried to load the vlc file it gave me this:
[root@localhost Desktop]# rpm -i --force vlc-0.8.6d-1.fc8.i386.rpm
error: unpacking of archive failed on file /usr/bin/vlc;478c1014:
cpio: read
This makes me think the rpm file is bad. What do you think?
Karl
Have you tried installing from source?
-Max
Yes but that does not work either, problem of some sort.
Karl
--
Karl F. Larsen, AKA K5DI
Linux User
#450462 http://counter.li.org.
PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-15-2008, 08:42 PM
Chris Jones
Updates
Well he's done every other conceivably not so bright thing , maybe that
will bring him full circle or maybe it will turn this into the longest
thread in history. Does anyone happen to know the message count on the
longest thread in fedora-list history?
No idea. But there is a perverse irony in the possibility that
discussing how long is the longest thread in Fedora history makes this
that thread...
Chris
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-15-2008, 11:14 PM
David Boles
Updates
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Jones wrote:
|
|> Well he's done every other conceivably not so bright thing , maybe
|> that will bring him full circle or maybe it will turn this into the
|> longest thread in history. Does anyone happen to know the message
|> count on the longest thread in fedora-list history?
|
| No idea. But there is a perverse irony in the possibility that
| discussing how long is the longest thread in Fedora history makes this
| that thread...
Not only Karl.
But have you noticed a trend lately?
'I don't know what this is. I don't know what I am doing. I don't know how
to fix this if this breaks. Ah - what the heck I'll do it anyway.
Followed by a *boom!*'
- --
~ David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-15-2008, 11:48 PM
max
Updates
----
Are we there yet? I don't think so. More to the point, I think that
since you are cognizant of the effort, you essentially cheapen the
achievement.
Craig
Does that mean that anyone who ever set out to break a record missed the
point? or is it only because padding the thread is considered cheap when
its done for the sake of padding? what's the count?(I should have asked
that last in another post!)
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
04-23-2010, 09:54 PM
Hristo Petkov
Updates
Hi,
> And we can address part of the 'update frequency' problem client-side,
> by only checking for new updates once a week.
>
> But one problem which we cannot address client-side, and for which 'do
> nothing now and reassess later' will not help at all is the amount of
> updates. Even if you only check once per week, the flood of pointless
> updates is a problem. That is that part of the problem that we need to
> address with Jon's 'establishing norms or rules to limit changes'.
In my view the problem is not in the updates themselves, but rather in the Fedora specification of developing new software versions which should differ significantly from the previous ones.
Who really needs all these distos to change at the 'speed of light in vacuum'.
New distros - yes, but not like this, and not so
often.
Perhaps the new distro should be something like a compilation of the old distros with the updates. In this way the problem with the compatibility of the distros would be solved as well.
For over 30 years of software monopoly on the market MS has all in all 9 OS, and within less time some other people have 14.
Maybe this needs some interpretation.
Regards
*
--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop
06-30-2010, 07:54 AM
Neil Winchurst
Updates
Sometimes when I look at the list of updates available (by clicking on
the little triangle on the panel), there are items that I don't want to
run. At the moment there are three referring to Firefox for example.
I have quit the update but of course the triangle is still showing on
the panel. How can I remove these updates without running them please?
There could be more updates to come in the future but I won't know by
seeing the triangle suddenly appear because it is there all the time now.
Thanks
Neil
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
09-06-2011, 05:22 PM
Frank McCormick
Updates
I ran apt-get update this morning...and got a hash sum mismatch on
several repositories. Anyone else having this problem ?
--
Cheers
Frank
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
I suppose this should go to the bug tracker, however I'll do it here first.
It seems a bit much to file a pair of bugs for.
During my updates this evening the libpng/libtiff rebuild bit.
( 7/85) upgrading gdk-pixbuf2
[----------------------------------------------------------------------------------------]
100%
g_module_open() failed for
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so:
libpng14.so.14: cannot open shared object file: No such file or directory
(29/85) upgrading libwmf
[----------------------------------------------------------------------------------------]
100%
g_module_open() failed for
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so:
libpng14.so.14: cannot open shared object file: No such file or directory
I got the pkgbuilds from the svn repos, rebuilt the packages, and
everything worked fine.
Myra
--
Chaos, panic, disaster, my work here is done!
01-31-2012, 07:10 AM
Allan McRae
Updates
On 31/01/12 17:48, Myra Nelson wrote:
> I suppose this should go to the bug tracker, however I'll do it here first.
> It seems a bit much to file a pair of bugs for.
>
> During my updates this evening the libpng/libtiff rebuild bit.
>
> ( 7/85) upgrading gdk-pixbuf2
>
> [----------------------------------------------------------------------------------------]
> 100%
> g_module_open() failed for
> /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so:
> libpng14.so.14: cannot open shared object file: No such file or directory
>
> (29/85) upgrading libwmf
>
> [----------------------------------------------------------------------------------------]
> 100%
> g_module_open() failed for
> /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so:
> libpng14.so.14: cannot open shared object file: No such file or directory
>
>
> I got the pkgbuilds from the svn repos, rebuilt the packages, and
> everything worked fine.
>
Just reinstalling them would be enough... This is an issue with
running the install scripts and the order in which the packages are
installed. I believe that this is being looked into.
Updates
