When: Friday, 2009-10-02 @ 15:00 UTC (11 AM EDT)
Where: #fedora-bugzappers on irc.freenode.net
Join us this Friday for another alliterative installment of ...
<drumroll> ... the Beta Blocker Bug review. Previous reviews have been
successful at keeping the blocker bug list active. Let's continue this
trend by reviewing the current list of unresolved F12Beta bugs .
The list of Fedora 12 Beta blocker bugs  includes:
* 516042 - MODIFIED - Unable to add NFS yum repo during
* 524599 - MODIFIED - Https repository problems
* 519237 - ASSIGNED - bash: cannot set terminal process group
(-1): Inappropriate ioctl for device
* 522675 - ASSIGNED - mouse,keyboard don't work when boot from
* 526158 - NEW - font of f12 beta terminal is very big
* 526208 - ASSIGNED - preupgrade failed from old release (f10,
* 526320 - ASSIGNED - ppc64.img and ppc32.img missing from tree
* 526380 - NEW - Xorg update kills graphics
* 526470 - NEW - NFSv3 mounting broken in dracut netboot
Have an issue you'd like to propose for F12Beta? Please consider the
following criteria when escalating an issue:
* Can this issue be fixed with a future rawhide update or is it
part of the critical path? 
* Is this defect a high (or greater) severity  with no, or an
* Does the presence of this bug dramatically reduce beta test
See you there!
test-announce mailing list
As part of the https://fedoraproject.org/wiki/Features/NFSv4Default feature
I am one commit away from changing the default protocol version NFS will
be using (or at least trying to use).
What does this means to you? Hopefully nothing! In theory this should
be a very seamless transition but with all new technology there
will be (and are) some rough spots.
Why are make the change? See the NFSv4Default wiki for details,
but in a nutshell:
* Better performance - V4 is now a stateful protocol. Meaning the server keeps
state on all the clients access a particular file or directory. This
allows the server to give out delegations (or leases) which in turn
allows the client to aggressive cache both data and meta data locally
* Firewall Friendly- With v4 only one port is used 2049 for all traffic
including mounting and file locking.
* Finally it enables us use upcoming minor releases of the the protocol.
NFS version 4.1 and pNFS are two example of upcoming minor releases.
FYI, V4 was introduced in Fedora Core 2 so it has been around for a while. I
personally have been using it for my home directory for a couple years now..
For more of the nitty gritty details see
That's the good news... Here is the bad....
Because the mount command will try NFS v4 first, mounts to older Linux servers
will start failing like:
# mount linux-server:/export /mnt
mount.nfs: mounting linux-server:/export failed, reason given by server:
No such file or directory
This is due to a defect in the Linux server exporting code, which is fixed
in F-12, *but* there are a number of workarounds
On the server (Which is suggested):
* Add the following entry to the /etc/exports file:
/ *(ro,fsid=0) Note: 'fsid=0' is explained in the exports(5) man pages.
On the client, go back to v3 mounts by doing one of the following:
* Add -o v3 to command line, similar to:
mount linux-server:/export /mnt
* Change the default mount version in the new /etc/nfsmount.conf file by
uncommenting the Nfsvers=3 setting in the 'NFSMount_Global_Options' section.
See nfsmount.conf(5) man page for details. The diff would look like:
--- /etc/nfsmount.conf 2009-09-29 16:58:13.000000000 -0400
+++ /tmp/nfsmount.conf 2009-09-29 16:56:04.000000000 -0400
@@ -29,7 +29,7 @@
# options that can be applied on all NFS mount.
# Protocol Version [2,3,4]
# Network Transport [Udp,Tcp,Rdma]
I'm building custom Fedora remix with some packages from RPMFusion and
updated Fedora packages. Last Live USB image I created booted really slow
(over 5 minutes). I tracked down the issue to nfs service. Even when this
ISO image is used for installing Fedora to HDD the same issue is present.
After stopping nfs service boot time was around 30 seconds!
Did anybody else experience this issue? Should I report this as a bug
agaings NFS or livecd-creator?
pratite me na twitteru - www.twitter.com/valentthttp://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
I was wondering what the consensus on switching to native Upstart
scripts (/etc/event.d/*) vs. keeping the "traditional" SysV init
scripts (/etc/rc.d/init.d) for daemons was? I was looking at
switching Asterisk over and have an Upstart script that seems to work
fairly well. I would be making the change for F-13...
anyone can help ?
it's possible to create a updated DVD with fedora install ?
Itamar Reis Peixoto
+55 11 4063 5033
+55 34 3221 8599
Taking a step back to look at a broader picture,
what is determined here might be helpful when migrating
other packages such as :
java2 ( or whatever Sunacle calls it officially )
Although none of those are as central to the operation
of Fedora as python, they all will suffer migration pains,
and likely will require some type of parallel install
of old and new versions, as well as migration of
requires and provides. perl 6 is in F12 as I recall,
under a pseudonym.
Keeping python2 around ( and perl5, etc. ) named that way
and not moving to compat-python2 or compat-perl5 may not
be a bad thing. Using compat-* as a naming convention does
signal " don't use this unless you have to " however is it
really required ? I know, it may be too early to think about
when python2 moves to a compat-* status, but as slowly as the
migration to python3 is going, there may be a need for
parallel installs of python2, python3, and python4.
I know, ick, but possible.
It might be best to keep the major version number as part
of the package name(s) permanent.
About a year ago, I suggested that BedeWork (http://bedework.org) be
included. I offered to package it with some help. I unfortunately ran
out of time. I now have time to package it and hopefully maintain the
package. Unfortunately, I haven't written an Java code in a decade or
so. I have never messed with Java packages.
The problems I have:
This package has a bunch of property files that you have to edit before
you build the program.
These include database names, locations, user/passwords for the
database, etc. I do not know if this is normal or not. I do not know how
to package this, how to suggest people customize this information, etc.
This program also requires JBoss or Tomcat (maybe there are others that
will work). Since I do not see JBoss in Fedora, Tomcat would be fine. I
have not experience with this. It would be nice if a Tomcat person can
help me with documentation on how to get this working and to use AD
(Kerberos [SPNEGO/GSSAPI] and LDAP) for the authentication and
user/group information as well.
I have a few packages that I have not yet submitted that I have
packaged. These include PyKota (and its dependencies), DSPAM, and C-ICAP
(not yet ready as I have some code I am writing that will be turned over
before I submit this package).
I have no clue about any of the build systems in Fedora, so I will need
help with this as well.
I know that F12 is closed for this, but I could get it ready for F13.
I'm trying to build zkt 0.99c on Fedora 11 (x86_64) and am running
into the following error:
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -g
-DHAVE_CONFIG_H -I. -Wall -Wmissing-prototypes -c -o soaserial.o
In file included from /usr/include/sys/syslog.h:207,
/usr/include/bits/syslog.h: In function 'syslog':
/usr/include/bits/syslog.h:32: error: invalid use of '__builtin_va_arg_pack ()'
Google tells me this has more to do with changes in newer GCC versions
to improve compile-time error detection, but I'm unable to figure out
what the right solution is. Can anyone help out here? I've
successfully compiled older versions of zkt on older versions of
Fedora - this is the first time I've tried it on Fedora 11. I've
attached the spec file that I'm using to build the RPM package.
I've pack library ne7ssh
History in two words:
It contain 6 examples files and Makefile to built it.
I've package it into ne7ssh-examples sub-package.
Michael Schwendt say what it should not be separate sub-package, and
right point me what other documentation have minor size and candidate to
-doc sub-package. I done that. But for right dependency include Require:
ne7ssh-devel, without that examples filed to built. It was also treated
as wrong. I wasn't agree with solution place all docs into -doc but
examples in -devel. I think it is incorrect. I also treat presents of
source files to end-user with known result - missing build dependency is
not correct maintainer decision. Also I agree what -devel dependency in
-doc too is not best...
So, is there any guidelines, policy or something else on this case?
With best wishes, Pavel Alexeev aka Pahan-Hubbitus.