Policy on Bodhi?
by Richard W.M. Jones
Is there a policy on Bodhi? I don't mean how to use it, I mean
questions such as:
- How long packages should stay in each state (pending / testing /
updates)?
- Can I push a package directly into a stable update without
waiting around for testing? (if I know there's not going to be
many testers, and I need it as a dep for another package)
- Is it allowed / not-allowed to troll users into adding karma? Or at
least to encourage them to put comments?
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
16 years
yum --skip-boken not work
by Oscar Bacho
Hi Guy
yum --skip-broken update no work in today rawhide.
exit said Skip-broken could not solve problems. It is totem problem.
Oscar
16 years
Offline: 2008-05-28 Through 2008-06-03
by Peter Gordon
Hi, all.
As I posted on the Vacation wiki page, I'll be gone from May 28 through
June 3 (or 2008-05-28 through 2008-06-03 for those that prefer ISO-8601
dates).
I'm heading to New Jersey/New York to visit family, and will probably
not have any 'Net access while there; but if so, it'll only be email
checking and similar. I won't bring my electronic keys or certificates
with me, so I'll have no commit or build capabilities while I'm away.
I'd greatly appreciate it if the Fedora community would care for my
packages [1] whilst I am away, especially watching for any
security/crasher fixes or the like that may need swift action.
Thanks!
[1] https://admin.fedoraproject.org/pkgdb/users/packages/pgordon
--
Peter Gordon (codergeek42)
GnuPG Public Key ID: 0xFFC19479 / Fingerprint:
DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479
16 years
Fedora's vmlinuz broken with mkelfimage
by Warren Togami
https://fedorahosted.org/k12linux/wiki/Notes/Coreboot
Something about Fedora's vmlinuz fails to load the initrd when it is
wrapped with mkelfimage. Full details at this page.
mkelfimage is necessary to wrap the vmlinuz and initrd into a single
bootable image if your hardware uses coreboot. qemu network booting
exhibits the same broken behavior, so this should be easy for others to
test without special coreboot hardware.
My latest theory: Something about how the Fedora kernel is configured or
built made it incompatible with mkelfimage. Ubuntu's recent kernels
work while our Fedora kernels from F8 (and possibly all the way back to
2006 as OLPC encountered) are broken.
http://people.redhat.com/wtogami/temp/config-2.6.24-16-generic
Here is Ubuntu's kernel config file if anyone wants to compare it.
Any ideas?
Warren Togami
wtogami(a)redhat.com
16 years
livecd-creator and selinux, status at the end of week 1
by Eric Paris
I've spent pretty much all week flailing around try to get
livecd-creator working with selinux enforcing with F10 as both the host
and the image. Next week begins the journey of working on making old
composes work on F10. Where do I stand? Well, it seems to work! I
booted an image and logged in.
Changes I've made so far (doesn't look like a whole lot for basically a
week of work....)
policycoreutils got some updates to allow users to be created in the
chroot (already built and in koji) and to make relabeling a little
better.
libselinux has no changes with my current approach. I do not want rpm
running inside the chroot to transition to rpm_t, nor do I want
scriptlets to run as rpm_script_t as then those scriptlets can cause
transitions to things like depmod_t which isn't going to have
permissions necessary to run with the possibly screwy labels inside the
chroot.
I added one rule to policy to allow hal to respond back to chroot
allow hald_t unconfined_notrans_t:dbus send_msg;
Create a fake /selinux inside the chroot it contains:
mls -> copy from host
poliyver -> copy from host
enforce -> 0
load -> /dev/null
This means that from the point of view of the inside of the chroot
selinux is "on" but not enforcing. The not enforcing part is important
because some programs (passwd for example) try to determine if selinux
is going to permit something before it actually tries it. If passwd
realizes that selinux is enforcing but then it doesn't have a
real /selinux to make those decisions it gets mad. So I'm lieing to the
chroot.
Changes to livecd-creator:
diff -Naupr imgcreate/creator.py imgcreate.new/creator.py
--- imgcreate/creator.py 2008-05-06 12:16:08.000000000 -0400
+++ imgcreate.new/creator.py 2008-05-16 13:01:05.000000000 -0400
@@ -22,6 +22,7 @@ import stat
import sys
import tempfile
import shutil
+import selinux
import yum
import rpm
@@ -427,7 +428,7 @@ class ImageCreator(object):
self._mount_instroot(base_on)
- for d in ("/dev/pts", "/etc", "/boot", "/var/log", "/var/cache/yum"):
+ for d in ("/dev/pts", "/etc", "/boot", "/var/log", "/var/cache/yum", "/sys", "/proc"):
makedirs(self._instroot + d)
cachesrc = cachedir or (self.__builddir + "/yum-cache")
@@ -439,10 +440,6 @@ class ImageCreator(object):
(cachesrc, "/var/cache/yum")]:
self.__bindmounts.append(BindChrootMount(f, self._instroot, dest))
- # /selinux should only be mounted if selinux is enabled (enforcing or permissive)
- if kickstart.selinux_enabled(self.ks):
- self.__bindmounts.append(BindChrootMount("/selinux", self._instroot, None))
-
# Create minimum /dev
origumask = os.umask(0000)
devices = [('null', 1, 3, 0666),
@@ -460,6 +457,20 @@ class ImageCreator(object):
os.symlink('/proc/self/fd/2', self._instroot + "/dev/stderr")
os.umask(origumask)
+ # selinux whoo hooo
+ if kickstart.selinux_enabled(self.ks):
+ makedirs(self._instroot + "/selinux")
+ # this should actually create our new fake /selinux, not bind from the host, though i haven't decided how
+ self.__bindmounts.append(BindChrootMount("/selinux1", self._instroot, "/selinux"))
+
+ # label the fs like it is a root before the bind mounting
+ cmd = "/sbin/setfiles -F -r %s %s %s" % (self._instroot, selinux.selinux_file_context_path(), self._instroot)
+ os.system(cmd)
+ # these dumb things don't get magically fixed, so make the user generic
+ for f in ["/proc", "/sys", "/selinux"]:
+ cmd = "chcon -u system_u %s" % (self._instroot + f)
+ os.system(cmd)
+
self._do_bindmounts()
os.symlink("../proc/mounts", self._instroot + "/etc/mtab")
diff -Naupr imgcreate/kickstart.py imgcreate.new/kickstart.py
--- imgcreate/kickstart.py 2008-05-06 12:16:08.000000000 -0400
+++ imgcreate.new/kickstart.py 2008-05-15 10:10:40.000000000 -0400
@@ -372,11 +372,11 @@ class SelinuxConfig(KickstartConfig):
if ksselinux.selinux == ksconstants.SELINUX_DISABLED:
return
- if not os.path.exists(self.path("/sbin/restorecon")):
+ if os.path.exists(self.path("/sbin/restorecon")):
+ self.call(["/sbin/restorecon", "-l", "-v", "-r", "-F", "-e", "/proc", "-e", "/sys", "-e", "/dev", "-e", "/selinux", "/"])
+ else:
return
- self.call(["/sbin/restorecon", "-l", "-v", "-r", "/"])
-
def apply(self, ksselinux):
if os.path.exists(self.path("/usr/sbin/lokkit")):
args = ["/usr/sbin/lokkit", "-f", "--quiet", "--nostart"]
16 years
plans to improve dual head support in system-config-display etc?
by David Mansfield
Just curious about the direction this is going w.r.t xrandr 1.2 type
displays.
I have an ATI and many co-workers have Nvidia with multiple monitors
attached which work great using the new xrandr based configuration. But
sadly s-c-d doesn't really understand this in F9. It only understands
dual head in the old xinerama sense.
Also, xorg.conf seems pretty poor for a users individual prefs. as to
what resolutions to use, as it's system-global not per-user.
Can someone point me towards any prior discussion on how this is
'supposed' to work in F10/future?
Thanks,
David
16 years
GDM setup
by John.Mizell@tch.com
It seem that there is not an setup gui for GDM now in fedora 9. I also
checked to see the documentation at
http://live.gnome.org/GDM/2.22/Configuration but it it not clear on how to
enable remote x11 apps to display locally.
Is there a work around and will this be added in a gui setup later on?
John Mizell
Systems Administrator
TCH
4185 Harrison Blvd. Suite 202
Ogden, Utah 84403
801-624-4604
16 years
Looking for the latest version of asterisk-strip.sh
by William F. Acker WB2FLW +1 303 722 7209
Hi all,
with the release of asterisk-1.6.0-0.12.beta7.1, it was discovered
that we needed to strip the tarball again. However, the script doesn't
seem to have been re-included in the SRPM. Does anyone know where I can
find the one that includes the latest removals? I'd like to build beta9
since there's a good chance that it fixes some of the bugs that have been
bugging me.
TIA.
Bill in Denver
16 years
Bodhi documentation for new packages
by Aaron S. Hawley
[Please, Cc me replies, thanks.]
The directions for joining Fedora as a package maintainer[1] are really
great. Unfortunately, they trail off at the end when it comes to
important tasks of making the package live using the Bodhi system,
section "Request updates to released Fedoras for your new package". I
ran into this roadblock last month, and it hasn't improved since.
As a new maintainer, I know very little about the updates infrastructure
of Fedora, which I predict is assumed knowledge about using Bodhi. This
is probably unfair to new maintainers. Here's my proposal for what this
section should say. It is also what I did, so I'm sure it needs
correction, and let me know so I can get my new package (gnue-common)
live. Thanks for Fedora, /a
-- BEGIN --
The first field asks for the name of the "Package". This will feature a
name completion system, but is currently broken. It uses the tag used
in Fedora CVS and the Koji build system, e.g.
<package-name>-<version>-<release>.fc9.
For new packages, choose "enhancement" as the "type" of update.
Keep the "Request" as "testing".
There are no bugs that are related to any new package, so leave the
"Bugs" field blank.
For new packages, add a copy of the package's description in the "Notes"
section so end users will know what it is.[2]
-- END --
1. <http://fedoraproject.org/wiki/PackageMaintainers/Join>
2. Taken from "Bodhi workflow and Q&A",
<http://fedoraproject.org/wiki/Infrastructure/UpdatesSystem/Bodhi-info-DRAFT>.
16 years