krb5-auth-dialog 0.16 for F-13
by Bojan Smojver
Could someone with enough karma rebuild krb5-auth-dialog 0.16 for F-13
(this is in relation to bug #597669). The 0.15 is leaking memory like
there is no tomorrow and I'm not getting much traction from the assignee
of the bug...
TIA,
--
Bojan
13 years, 7 months
systemd acceptance, packaging guidelines (was Re: systemd and changes)
by Bill Nottingham
(intentionally breaking thread)
Toshio Kuratomi (a.badger(a)gmail.com) said:
> Maybe I should start a new thread since this isn't really a bug, but it is
> a blocker -- we need to get some packaging guidelines out for systemd.
> I think that the last message on the subject was this one:
>
> http://lists.fedoraproject.org/pipermail/devel/2010-July/139483.html
>
> Could I get a reply as to whether that looks right?
- At the moment, /bin/systemctl is in systemd-units. (I think this
is a bug. Filed.)
- As long as we're still shipping upstart, the sysv scripts would still
need included, and would still need to be set up with chkconfig the
same way.
> As noted in the post, I'm not sure if the outlined procedure correctly
> implements level 1.
I believe it does.
> We should probably also have the scriptlets for implementing level 3 for the
> things basic to the system that require that.
My reading of your mail is different - the case we want to handle is case
#2 (installation of something that starts by default - dbus, NM, etc.)
As I understand it, they would be the same, with the addition of:
%post
if [ 0$1 -eq ]; then
/bin/systemctl enable <foo.service>
fi
with foo.service having the appropriate [Install] stanza that says where it
should start up. As with SysV scripts, we generally do not start services
by default, so this is rare.
Case #3 that you mentioned is something I don't think we have in Fedora -
we never start services on package installation.
This, however, is just packaging guidelines. From readng the thread, there
are many things that I think people would like covered with systemd before
they would feel comfortable with it. So, I'm going to attempt to quantify
what would need to be tested and verified. This document focuses on
backwards compatibility. THIS IS GOING TO BE VERY VERBOSE. Comments, changes,
etc. welcome.
BOOTUP
- System boots successfully to GUI, when configured.
- System boots successfully to text mode, when configured.
- System properly handles being passed [1-5], 'single', 'S', 's', '-s',
booting to the appropriate 'runlevel' (0 and 6 can still work,
but they're sort of pointless anyway) When booted in this manner,
'5' will bring up a GUI, and '3' will not.
SINGLE USER MODE
- Exiting single user mode properly returns to the default state.
- single-user mode output is correctly displayed on the console.
PLYMOUTH
- plymouth is shown on startup.
- plymouth is quit correctly.
- plymouth is shown on shutdown.
- 'esc' to show details still functions in plymouth.
- an equivalent to /var/log/boot.log still exists, and is populated
(can be normal syslog)
- plymouth transition from grub -> boot -> X is seamless for KMS cards,
similar to Fedora 13.
RUNTIME TOOLS
- telinit [0123456] does the proper thing.
- the 'runlevel' command displays correct output if we are in a target
that is aliased to a runlevel.
- 'halt' shuts down, but does not poweroff.
-- 'halt' supports -p, to power off.
- 'poweroff' shuts down, and powers off.
- 'reboot' shuts down and reboots.
- 'halt', 'poweroff', 'reboot' all support '-f', to force the action.
- 'halt', 'poweroff', 'reboot' all properly log to utmp, wtmp, and
the audit layer.
- 'shutdown' shall support the following arguments in a compatible manner:
'r', 'h', 'H', 'P', 'c', 'k', <time>.
- 'telinit' does not error when passed '[Qq]' (to reload its configuration)
and '[Uu]' to re-exec itself. It can optionally make systemd do a similar
action, if valid.
- init shall support a mechanism to re-exec itself to not cause dirty
inodes on shutdown; initscripts will use this method on shutdown.
- the kbdrequest job currently in systemd will be disabled for final release.
- 'ctrl-alt-delete' will reboot the system.
PREFDM
- prefdm starts a configured display manager correctly.
- prefdm starts a installed display manager correctly without additional
configuration.
CONSOLEKIT
- ConsoleKit properly logs system start, stop, and restart.
- The ConsoleKit shutdown/reboot/halt methods work as expected.
SERIAL CONSOLES
- Booting with a primary serial console (via console=) automatically
sets up a getty on the console, and sets up securetty to allow for root
login.
- (optional) Booting with secondary serial consoles does the same.
NON-SERIAL CONSOLES
- By default, 6 gettys will be started in text mode, on tty1-6. 5
gettys will be started in GUI mode, on tty2-6.
- getty and X will not be started on the same tty.
- (optional) The number of ttys started can be configurable.
ERROR HANDLING
- SELinux automatic relabelling will still function.
- fsck will still function.
- Dropping to an emergency shell in the case where either of these fails
shall still function.
SELINUX
- No AVCs from the init system in normal use.
- No AVCs when executing any of the cases specified here
- systemd shall still function if booted with selinux=0.
PACKAGING
- Guidelines for packaging systemd units shall be formalized.
- The behavior when both systemd units and SysV services are present on
the system shall be defined. This includes defined behavior when a
service appears to be 'enabled' for SysV links while 'disabled' for
systemd (and vice-versa).
- The syntax of systemd units shall be frozen for the release (all future
releases? Some set number of releases?)
SERVICE HANDLING
- Running 'chkconfig <foo> <(null)|on|off>' on a service managed by systemd
will return the correct code/perform an appropriate action.
- Running 'service <foo> <start|stop|...>' on a service managed by systemd
will perform the appropriate action (via systemctl), and return
similar errors.
- Running '/etc/init.d/<foo> <start|stop|...>' will not break the systemd
environment, while still performing the action specified, and shall return
similar errors.
GENERAL SANITY
- Booting a system shall achieve a similar result as booting in upstart:
-- The same set of services will be started.
-- The services shall function the same.
-- The same set of devices and filesystems shall be mounted.
-- The same set of devices and filesystems shall be fscked.
ORDERING
- rc.local will run as the final service on bootup.
- gettys will not start until after rc.local.
- prefdm will start coincident to gettys (earlier?)
ADMIN INTERFACE
- The files and paths used by systemd shall be frozen for future releases.
- The basic syntax of systemd commands shall be frozen for future releases.
- The syntax of systemd units shall be frozen for future releases.
ASSORTED RANDOM CONFIGURATIONS
- The system shall properly function with:
-- encrypted /
-- encrypted non-/
-- nfs /
-- iSCSI /
-- LDAP user information
-- IPA/AD user information
-- NIS user information
-- ext* filesystems
-- btrfs filesystems
-- xfs filesystems
ANY REMAINING UPSTART JOBS
- All packaged upstart jobs are modified to have some SysV or systemd-native
equivalent.
... that's all I have at the moment. I'm sure I'm missing something.
Bill
13 years, 7 months
systemd and filesystems with noauto
by Matthew Miller
I have a fstab entry like this:
/dev/sde1 /mnt/sdcard autonoexec,noauto,users,ro,sync,shortname=lower 0 0
which I use in a script to take pictures off my camera's SD card and
transfer them to my photo management system. I've been doing it this way for
a long time, and now with modern Linux I recognize that there's better ways
of doing it. But I was surprised when I updated this system to latest
rawhide and rebooted, because it came up with that filesystem mounted.
Is this expected behavior?
--
Matthew Miller <mattdm(a)mattdm.org>
Senior Systems Architect -- Instructional & Research Computing Services
Harvard School of Engineering & Applied Sciences
13 years, 7 months
Deactivating LVDS display when laptop lid is closed
by Orion Poplawski
Apparently[1] it is up to the desktop environment now to deactivate the LVDS
display if the laptop lid is closed at boot (or whenever?). I now have
several F13 laptops in docks with external monitors that boot with the lid
closed, but kdm_greet puts the login panel on the closed LVDS display (see
bug[2]). I've also filed a Fedora bug for similar stuff here [3]. I don't
know how gdm behaves.
Any other comments/help? I tried doing:
# Disable LVDS if another output is up
if xrandr --current | grep -qE '^(DVI|VGA).* connected'
then
lvds=$(xrandr --current | awk '$1 ~ /LVDS/ { print $1 }')
xrandr --output $lvds --off
fi
in /etc/kde/kdm/Xsetup, but kdm_greet appears to get stuck in an infinite loop
and I only see the small round black spinner cursor, never the login panel.
I thought about posting to the Fedora KDE list, but I'd like to get some wider
input.
1 - https://bugs.freedesktop.org/show_bug.cgi?id=28936
2 - https://bugs.kde.org/show_bug.cgi?id=243807
3 - https://bugzilla.redhat.com/show_bug.cgi?id=539180
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
13 years, 7 months
fedpkg prep
by Steve Dickson
Just curious....
Why does 'fedpkg prep' care that the repo is in an inconsistent state?
I just did a rebase to the latest f14 code on a private branch.
So yes he repo in an inconsistent but that is ok. I'm going to
make some changes to put it back in a consistent state but
I can not do that without a source tree.
So is there a way to do what the old 'make prep' did? That is
stupidity untar the tarball an apply all the current patch
without checking any state??
tia,
steved.
13 years, 7 months
Starting Java SIG
by Stanislav Ochotnicky
Hi everyone,
There has been an effort few years back to start Java SIG but it didn't
work out in the end (no idea why). I decided it's time to try again :-)
I would like to start Java SIG for a lot of reasons. Some of them:
* Packaging guidelines are in need of an update (badly)
* Consistency in java packages is somewhat lacking
* More eyes see more approach, I'd like for all java related commits to
go through an alias so we can all watch out for changes that can
break our stuff
* Have a place where we can collect tips & tricks, solutions to common
problems etc. Currently this information is scattered through
people's wiki pages
* Java needs collaboration more than most other areas, because problems
cannot be safely discovered automatically when someone changes
dependency. This can cause serious headaches (to me at least). Java
SIG to the rescue! :-)
* Other languages have their own SIGs and we don't! :-)
Who am I?
Owner/Co-maintainer of a bunch of Java packages (mostly maven plugins,
apache-commons, junit, velocity, checkstyle, plexus
libraries). Involved in recent update of maven to v2.2.1.
Reply if you're interested with helping out and being able to
see/influence where Java packaging in Fedora is going. I know there will
be at least a few people joining in.
I'll be starting Java SIG wiki page soon, plus I guess we can peruse
java-devel mailing list for SIG discussions.
--
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Associate Software Engineer - Base Operating Systems Brno
PGP: 71A1677C
Red Hat Inc. http://cz.redhat.com
13 years, 7 months
yum appmarket
by Seth Vidal
I mentioned this on:
http://skvidal.wordpress.com/2010/08/19/fedora-app-market-proof-of-concept/
last night but I thought I'd bring it up here:
Yesterday someone was talking about installing apps in fedora and how it
was hard to figure out what to install/try b/c there were too much STUFF
in fedora. They suggested an ‘app store’ like functionality. I explained
that all the resources to do something like that exist in the
infrastructure yum and friends offer now. I decided to prove that
concept a bit.
The concept of an ‘app’ is pretty amorphous but I decided to just use
what Colin Walters said was his definition of an ‘app’ – which is any
pkg containing a .desktop file. So I just whipped up a simple tool to
dump out an xml-file of a format yum is already familiar with based on
that criteria:
http://skvidal.fedorapeople.org/misc/appfinder.py
Running that generates an xml file with only the ‘apps’ defined.
Great. Then I wrote a yum plugin to access and use this data.
and I stuck it in this repo
1. copy this file into /etc/yum.repos.d/
2. run: yum install yum-plugin-appmarket
Now yum will have a few new commands available to it:
app-install Install an App
app-list List Apps
app-remove Remove an App
app-search Search for an App
Some examples:
yum app-search yum
won’t turn up ‘yum’ but it will turn up ‘yumex’.
Fancy, huh?
Now, the concept of an app can be refined in many ways but this is just
to prove that the infrastructure has been available.
-sv
13 years, 7 months
Fedora Notifications System.
by Mahmoud Abdul Jawad
Hi all,,
before two weeks, a discussion started in ambassadors mailing-list about a
work around to deliver the important notifications to the fedora desktop
(whatever the desktop is).
after some discussion, we started with some guide lines & putted them on the
wiki:
https://fedoraproject.org/wiki/Fedora_notifications_system
Continuing, I created an early prototype i want people to check & gives
feedbacks about it.
you can reach it through gitweb:
http://fedorapeople.org/gitweb?p=megenius/public_git/fns.git;a=summary
or, you can grab your own clone from the git repo:
git://fedorapeople.org/megenius/fns.git
keep in mind that last_check file should be writeable by the world, & you
should change its value to an earlier date, so you can see some
notifications.
--
Regards,,
Mahmoud Abdul Jawad
@meGenius
13 years, 7 months
clutter -> 1.3
by Colin Walters
Heads up to Clutter consumers - I'm updating it in f15 to the 1.3
(master) branch. I've tested GNOME Shell and quadrapassel, feel free
to CC me for other fallout.
13 years, 7 months
Nautilus misbehaving
by Paul F. Johnson
Hi,
After the recent rawhide to nautilus 2.90.1-1.fc15.i686, it's stopped
working claiming that I don't have Settings schema
'org.gnome.desktop.lockdown' installed.
What is this and how do I fix the problem?
TTFN
Paul
13 years, 7 months