I'm search documentation, how-to or guidelines how I can correctly pack
cron job, needed by rpm package.
I'm spent big time, but do not find any useful description.
Off course I known about directories
but what if I need start job every 20 minutes?
AFAIK, in cronie rpm presents /etc/cron.d especially for this purposes.
But really it is only true way put cronie into requires? How I can pack
jobs for standard (vixie) cron?
Very thanks for all answers.
Alright, the Rawhide Python packages have had time to flush through, so
we're going to go ahead and commit 2.6 to Rawhide and start the rebuild
of all Python packages in Rawhide. So please keep your hands off any
packages that require python(abi) until we're done. Or if you like, you
can help out by bumping the release and building against the
See you on the flipside.
Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com>
PLEASE don't CC me; I'm already subscribed
$ du -h /usr/share/doc/autofs-5.0.3/*.patch
[$ du -h autofs-5.0.4/patches
So, we've got ~48K of %changelog details in the autofs.spec, but the
question why the %doc line explicitly includes patches/* is not answered.
That clutters up the docdir unnecessarily.
Who can tell why this is done?
Since this morning, initializing fedora-rawhide-i386 mock chroots fail
for me on FC9:
# mock -r fedora-rawhide-i386 init
INFO: mock.py version 0.9.9 starting...
ERROR: Command failed:
# /usr/bin/yum --installroot /var/lib/mock/fedora-rawhide-i386/root/
/bin/sh: error while loading shared libraries: libtinfo.so.5: cannot
open shared object file: No such file or directory
error: %post(bash-3.2-28.fc10.i386) scriptlet failed, exit status 127
I am able to reproduce this error on different fedora-9-i386 and
For whatever reason, so far, on fedora-9-x86_64, "mock -r
fedora-rawhide-x86_64 init" doesn't fail, nor have I encountered this
error on a fedora-rawhide-i386/fedora-9.92-i386 test-machine.
There are two drivers for those cameras:
-the 1.x driver who is in the kernel and is basically useless since the
only OV511 cameras who are not by today standards as obsolete as a 20
Mhz 386 don't work with it.
-the 2.x driver at alpha.dyndns.com/ov511. This is the only one who
the late models who used this chip (and the ones who are still useful).
Probelm is that the author has not updated its site in two years and
that it no longer compiles with present day kernel. I fixed it for
2.6.16 kernels and sent the patches to the author but got no answer.
And kernel 2.6.24 (I think) broke it again (or more exactly made it
no longer compile).
Question if I fix it again what are the chances it ends in Fedora? How
are orphaned drivers handled in the kernel? Someone, who doesn't seem
to be the original author, has been ensuring the 1.x continues compiling
in 2.6.27 despite the changes in interface.
Yesterday, I posted a blog entry about Fedora 10 Release on my
blog and mentioned the Fedora 10 Spins availability with link to Fedora
Project page. I have received a comment which says,
"I might be interested in some of the spins, but it's hard to tell.
The names contain acronyms, and the description simply repeats the
acronym. Unless I recognize what that acronym is, the name is useless.
What's FEL, AOS or broffice? XFCE is the only one I know, though others
might not even know that.
Since the table has a description field for each spin, why not (at
least) expand the acronyms so folks have a clue as to whether or not it
might be useful? Even better, a link to a page describing the spin in
more detail. If it's worth the time and effort to create, it should be
worth the time it takes to write a paragraph describing it."
Well, I also got confused by the acronyms, but quick googling
suggested the Fedora Project Wiki already has pages describing the
acronyms in details. I request people maintaining the spins to link the
description to their respective wiki pages.
Computer Science and Engineering,
International Institute of Information Technology,
Hyderbad, India - 500032.
My Home-Page: http://saini.co.in/
My Project : http://cachevideos.com/
My Web-Blog: http://fedora.co.in/
IRC nick : generalBordeaux
Channels : #fedora, #fedora-devel, #yum on freenode
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.