ANNOUNCE: New smock supports Koji chain building
by Richard W.M. Jones
I've just modified smock so that it can be used to work out a build
order suitable for chain building (in Koji), with maximum parallelism.
Just use smock in the normal way, but add the '--chain' option.
For example:
smock.pl --arch=i386 --distro=fedora-10 --chain ocaml*/devel/*.src.rpm
prints ...
make chain-build CHAIN="ocaml : ocaml-perl4caml ocaml-lablgl ocaml-findlib ocaml-cryptokit ocaml-camlp5 ocaml-camlidl : ocaml-lablgtk ocaml-SDL ocamldsort ocaml-zip ocaml-xml-light ocaml-ulex ocaml-type-conv ocaml-ssl ocaml-sqlite ocaml-res ocaml-postgresql ocaml-pcre ocaml-pa-monad ocaml-ounit ocaml-openin ocaml-omake ocaml-ocamlgraph ocaml-mysql ocaml-libvirt ocaml-lacaml ocaml-json-static ocaml-gsl ocaml-fileutils ocaml-facile ocaml-extlib ocaml-expat ocaml-deriving ocaml-dbus ocaml-curses ocaml-curl ocaml-camomile ocaml-calendar ocaml-bitstring ocaml-bisect ocaml-augeas ocaml-newt : ocaml-camlimages ocaml-cairo ocaml-sexplib ocaml-lwt ocaml-ocamlnet ocaml-mikmatch ocaml-cmigrep ocaml-reins ocaml-csv ocaml-gettext : ocaml-xmlrpc-light ocaml-pxp ocaml-json-wheel ocaml-pgocaml "
To get the latest version of smock, do:
hg clone http://hg.et.redhat.com/misc/fedora-mingw--devel
and it is in the smock/ subdirectory.
Rich.
15 years, 6 months
keyfile plugin as new install default for NetworkManager in F11?
by Martin Ebourne
Fedora is currently using the ifcfg plugin for NetworkManager that stores
system wide network settings in the old network scripts format. This is
clearly useful when upgrading a machine with a working configuration from
an old Fedora release. However the legacy format makes it difficult to
understand the settings and restricts the functionality somewhat.
NetworkManager also includes an alternative system wide settings plugin
called keyfile. This stores system wide connections in ini format files
in the /etc/NetworkManager/system-connections directory. These are a lot
easier to understand and read, and provide much better functionality (eg.
system wide WPA is trivial), and most importantly of all provides a much
more user friendly and consistent GUI giving an excellent user experience.
I switched to keyfile with the Fedora 9 release since ifcfg was not
working for WPA. Back then it was necessary to write the config files by
hand which took quite some figuring out. With Fedora 10 it's now as
simple as configure the network in NetworkManager in the usual way, then
just tick the 'Available to all users' box in the NetworkManager edit
settings dialogue.
Are there any plans to switch to keyfile as the default for new installs
with Fedora 11? It would seem sensible to leave ifcfg for upgrades,
perhaps with an easy way to automatically switch to keyfile if desired.
Cheers,
Martin
PS. These two very minor bugs in F10 are all that separates keyfile from
an excellent user experience for me, on several different machines:
https://bugzilla.redhat.com/show_bug.cgi?id=465633
https://bugzilla.redhat.com/show_bug.cgi?id=471734
15 years, 6 months
Fedora 11 Feature Process reminders
by Jon Stanley
At today's FESCo meeting, the final schedule for Fedora 11 was
approved. Now it's time for some reminders about the feature process
for Fedora 11. We're changing a few things this time around to
hopefully make the whole process run smoother than ever!
First., FESCo will be making decisions regarding dropping incomplete
features at the meeting *2 weeks before* the freeze date, in order to
give rel-eng and QA time to implement whatever contingency plans might
be required prior to the freeze. For Fedora 11, these dates are:
Alpha freeze: 1/20 - FESCo meeting - 1/8
Beta Freeze: 3/10 - FESCo meeting - 2/25
Final Freeze: 4/14 - FESCo meeting - 4/1
Also, note that feature freeze is on 3/3, a week prior to the Beta
freeze. This was done in order to provide more time for testing
between feature freeze and beta freeze, and fix any issues that come
up without having to break the beta freeze.
By the time of the Alpha freeze, features must have a defined
specification (i.e. the scope section of the template must be
complete). This should include criteria of what is required in order
to declare the feature a "success", for example, you're able to adjust
the volume in a variety of ways (name those ways) and that they have
the desired effect for the VolumeControl feature currently scheduled
for F11.
By the time of the beta freeze, features must have a complete test
plan, and be in a testable state. A test plan is NOT simply "use it
and see if it works". Steps that can be reproduced by someone that has
little to no knowledge of your feature area, but a basic
understanding of Fedora and the command line, etc. is what's required
here. Taking the VolumeControl feature, there should be instructions
that tell me what packages need to be installed, what they're expected
to do under various circumstances, and how to make them do those
things.
By final freeze, obviously the feature must be fully implemented and
ready to go out the door.
Also, as feature owners have features that are nearing completion, I
would encourage them to contact either myself or James Laska in order
to schedule a "test day" for that feature. In the past, these have
been incredibly successful in getting test coverage and exposure for
features that may not otherwise get it. The earlier in the process
that this can happen, the better.
I will be handling the QA items that are new to this release, John
Poelstra will continue in his role as the overall Feature Wrangler.
All of this is designed to ensure a high-quality release, and
minimize any schedule slips.
Thanks!
-Jon
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
15 years, 6 months
How to pack cron jobs?
by Pavel Alexeev (aka Pahan-Hubbitus)
Hello.
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
/etc/cron.daily
/etc/cron.hourly
/etc/cron.monthly
/etc/cron.weekly
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.
15 years, 6 months
looking for inotifywait and similar help
by Patrice Dumas
Hello,
Trying to have fcron do the same than cronie, that is regenerate
binary crontabs when /etc/crontab /etc/cron.d/ (or /etc/fcrontab since it
is the same, but for fcron) change, I made a script to watch for
/etc/cron.d/ and /etc/crontab and /etc/fcrontab if they exist (and then
launch a script coming from debian that does all the regeneration work).
However the issue I have is that I don't know how to have inotifywait do
something when /etc/crontab or /etc/fcrontab is created since if I give
a non-existing file as argument it will error out.
Also maybe I should not listen to all the events but only some.
And lastly maybe inotifywait is not the right tool?
The script is here:
http://cvs.fedoraproject.org/viewvc/rpms/fcron/devel/fcron_watch_config?r...
It is launched by an init script through another script,
http://cvs.fedoraproject.org/viewvc/rpms/fcron/devel/daemon_fcron_watch_c...
that doesn't do anything else that starting it with setsid.
Anybody knows what I should do?
--
Pat
15 years, 6 months
gmime soname bump
by Matthias Clasen
I'm building gmime-2.4.3, which changes the libgmime soname to
libgmime-2.4.so.2.
15 years, 6 months
My (unpleasant) fedora 10 installation experience
by Lev Shamardin
Hi all,
Today the file system on my wife's laptop got corrupted (that's another sad
fedora, kerneloops and tuxonice story) and I decided to reinstall everything
from scratch using Fedora 10 installation DVD. The laptop previously had Fedora
9 installed, so my plan was to reinstall the system and then restore the /home
partition with fsck & co.
The installation process from the DVD went quite smoothly, but when I got to the
first boot there were some surprises. Since I was going to recover /home later,
I was not planning to create any users at the first boot, but skipping the
"Create user" screen required to press the "Use network login..." button and
cancel the dialog, otherwise the firstboot continued to complain that I
definitely need to create a user.
This laptop uses wireless to connect to the internet, and guess what? Is is NOT
yet configured when you are running the firstboot. On the Date & Time screen I
selected "Enable network time protocol", pressed forward, and then hit Cancel on
the "Contacting NTP..." dialog (I supposed that I don't want to wait for the
network timeout) and... Firstboot crashed leaving me with an empty screen with a
mouse cursor on it. Ctrl-Alt-F1/F2/etc. brought me to another empty screen,
without a mouse this time. Fortunately Ctrl-Alt-Del from that mouseless screen
worked fine.
Next boot showed firstboot again allowing to test these bugs and finally get
through them to discover another surprise.
I've selected "Russian" keyboard during the installation process. Usually this
assumed that there are two keyboard layouts (English and Russian) and you can
switch between them with a hotkey. But not in the default state of the GDM after
the first boot. The only option I had was Russian input! I tried all common
layout switch shortcuts but have not managed to find one to switch the layout to
english, but I had to type something in english since I have not created any
users and my root user had both english login name and password. So I had to go
to the menus, search for USA keyboard layout and only after this had a chance to
try login to the system. It really seems to me that these layout defaults are
insane. Is it that common to have non-english login names and passwords, really?
Anyway, I failed to login interactively to X as root ("Cannot authenticate
user") and after that even selecting Keyboard: USA did not bring english input
to the gdm! I tried to switch several times, nothing happened. Adding a second
USA layout (USA international this time) partially solved the problem with
switching input language, but I still was not able to login as root to a
graphical terminal to recover the system. Of course some searching in google
delivered the answer that I have to modify the gdm PAM settings, but that only
brought me to a discovery that gdm forgets the input language and layout
settings after asking for the user name! So the complete "root login" procedure
looks like this:
1. Press "other user..." [Why should I do this if there are no users in the
system except root?]
2. Switch layout to USA. [First switch is broken, so]
3. Switch layout to USA (intl). [Aha, english letters finally]
4. Enter user name
5. Switch layout to USA. [Don't forget: the first switch is broken]
6. Switch layout to USA (intl).
7. Enter the root password.
Phew, That was easy!
Never ever before a fresh Fedora installation was that hostile towards system
recovery... Especially to a non-US user. That is sad.
With best regards,
Lev.
15 years, 6 months
Package Review Stats for the week ending November 23, 2007
by Brian Pepple
Top three FAS account holders who have completed reviewing "Package
review" components on bugzilla this week were Parag AN(पराग), Chris
Weyl,and Brian Pepple. Below is the number of completed package reviews
done.
Parag AN(पराग) - 8
Chris Weyl - 6
Brian Pepple - 3
Levente Farkas - 3
Jason Tibbitts - 2
Lucian Langa - 2
Mamoru Tasaka - 2
Marcela Maslanova - 2
Dan Horák - 1
David Woodhouse - 1
Fabian Affolter - 1
Jussi Lehtola - 1
Michael Schwendt - 1
Miroslav Lichvar - 1
Stepan Kasal - 1
Xavier Lamien - 1
Total reviews: 36
Later,
/B
--
Brian Pepple <bpepple(a)fedoraproject.org>
https://fedoraproject.org/wiki/User:Bpepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
15 years, 6 months
