Warren Togami wrote:
>* Time-limit to publish where no negative comments are posted >within
the Bugzilla report. Senior developers reserve the right to >hold an
update if a good technical reason can be stated. (Insert >more details
I'm not going to weigh in on whether or not a countdown for a move from
testing to release is a good idea or not. But if a clock is started it
would be nice to know if there will be a way for community testers to
not only abort the countdown by finding regressions in the test packages
but also a way to accelerate the timetable if the fix in testing is
'important' and community members want to do what is in their power to
get the package out of testing as quickly as possible so it can be
Starting a clock...does not, on the face of things, encourage active
testing by the community...since if people wait for the clock to expire,
the testing package gets released if no regressions are found. No
testing...no regressions. And of course not having a clock, could mean,
that good packages will linger in testing even though they are
reasonably well crafted updates.
-jef"just give me a policy that i can beat people over the head
Has anyone been able to compile anaconda 9.2 against 2.6.0-test9
kernel headers? I am running into kernel header-related problems.
I've seen that other software projects are facing similar difficulty
with 2.6. I imagine it has something to do with what code is protected
by #ifdef __KERNEL__'s as the kernel itself compiles fine. I get the
[mike@imp anaconda-9.2]$ make
for d in isys loader2 po stubs textw utils scripts bootdisk installclasses iw pixmaps isomd5sum command-stubs fonts; do make -C $d; [ $? = 0 ] || exit 1; done
make: Entering directory `/home/mike/development/anaconda-9.2-cryptoroot/anaconda-9.2/isys'
for d in gzlib; do make -C $d; done
make: Entering directory `/home/mike/development/anaconda-9.2-cryptoroot/anaconda-9.2/isys/gzlib'
make: Nothing to be done for `all'.
make: Leaving directory `/home/mike/development/anaconda-9.2-cryptoroot/anaconda-9.2/isys/gzlib'
cc -c -ffunction-sections -I/usr/include/python2.2 -I.. -Wall -Os -g -DHAVE_NFS -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Werror -fPIC -o isys.lo isys.c
In file included from /usr/include/linux/blockgroup_lock.h:8,
/usr/include/linux/spinlock.h: In function `bit_spin_lock':
/usr/include/linux/spinlock.h:413: invalid type argument of `->'
/usr/include/linux/spinlock.h: In function `bit_spin_trylock':
/usr/include/linux/spinlock.h:436: invalid type argument of `->'
/usr/include/linux/spinlock.h: In function `bit_spin_unlock':
/usr/include/linux/spinlock.h:451: invalid type argument of `->'
/usr/include/linux/spinlock.h:451: `TIF_NEED_RESCHED' undeclared (first use in this function)
/usr/include/linux/spinlock.h:451: (Each undeclared identifier is reported only once
/usr/include/linux/spinlock.h:451: for each function it appears in.)
/usr/include/linux/spinlock.h: In function `bit_spin_is_locked':
/usr/include/linux/spinlock.h:462: invalid type argument of `->'
In file included from /usr/include/linux/ext2_fs_sb.h:20,
/usr/include/linux/percpu_counter.h: In function `percpu_counter_mod':
/usr/include/linux/percpu_counter.h:75: invalid type argument of `->'
/usr/include/linux/percpu_counter.h:77: invalid type argument of `->'
/usr/include/linux/percpu_counter.h:77: `TIF_NEED_RESCHED' undeclared (first use in this function)
In file included from /usr/include/linux/ext2_fs.h:20,
/usr/include/linux/ext2_fs_sb.h: At top level:
/usr/include/linux/ext2_fs_sb.h:40: parse error before "uid_t"
/usr/include/linux/ext2_fs_sb.h:48: parse error before "s_next_generation"
/usr/include/linux/ext2_fs_sb.h:50: parse error before '*' token
/usr/include/linux/ext2_fs_sb.h:55: parse error before '}' token
In file included from /usr/include/linux/ext3_fs.h:20,
/usr/include/linux/ext3_fs_i.h:80: field `i_orphan' has incomplete type
/usr/include/linux/ext3_fs_i.h:97: parse error before "loff_t"
/usr/include/linux/ext3_fs_i.h:111: parse error before '}' token
In file included from /usr/include/linux/ext3_fs.h:21,
/usr/include/linux/ext3_fs_sb.h:44: parse error before "uid_t"
/usr/include/linux/ext3_fs_sb.h:52: parse error before "s_next_generation"
/usr/include/linux/ext3_fs_sb.h:53: parse error before "s_hash_seed"
/usr/include/linux/ext3_fs_sb.h:55: parse error before '*' token
/usr/include/linux/ext3_fs_sb.h:71: parse error before '}' token
In file included from isys.c:5:
/usr/include/linux/ext3_fs.h:618: parse error before "u32"
/usr/include/linux/ext3_fs.h:621: parse error before '*' token
/usr/include/linux/ext3_fs.h:622: parse error before '}' token
In file included from /usr/include/linux/timer.h:5,
/usr/include/linux/list.h:576:2: #warning "don't include kernel headers in userspace"
In file included from /usr/include/linux/workqueue.h:8,
/usr/include/linux/timer.h:11: field `entry' has incomplete type
/usr/include/linux/timer.h:21: confused by earlier errors, bailing out
make: *** [isys.lo] Error 1
make: Leaving directory `/home/mike/development/anaconda-9.2-cryptoroot/anaconda-9.2/isys'
make: *** [subdirs] Error 1
On Thu, 13 Nov 2003, Neal D. Becker wrote:
> Where? There is no x86_64 dir here:
Look in what used to be Red Hat Rawhide, but is now Fedora Development,
there is an x86_64 directory in there that has the packages. Any mirror
Justin M. Forbes
Full Legal Name: Michael Alan Koziarski
Location: Wellington, New Zealand
Profession: Software Engineer
Company: A Retail bank
My Goals in the Fedora Project:
There are hundreds of excellent but lightly used libraries available
for software development under linux. My goal is to package these
libraries so that software developers, both commercial and open source,
have a wide range of options available.
The lower the barrier to entry is the more people can participate, the
more people participating, the better.
I'm not really a packaging expert, so while I'm willing to help with QA,
I fear I may be more trouble than I'm worth.
I've helped out with the LyX document processor in the past,
contributing the odd patch, I also ran their bugzilla installation for a
I'm familiar with a variety of languages. Currently I'm paid to program
Java, but I love using python and/or C++
Why should you trust me? .... Up to you really. (yes, this question may
be a little blunt)
GPG Key Fingerprint:
1024D/4743E9E9 2003-10-05 Michael A. Koziarski <michael(a)koziarski.org>
Key fingerprint = B77A 1053 C228 08D9 0866 5D60 39FF 0BD3 4743 E9E9
1. Full legal name
Karl Brian DeBisschop
2. Country, City
Quincy, MA, USA
3. Profession or Student status
Director of Software Engineering and Development, Infoplease.com
4. Company or School
Infoplease is a tiny little part of Pearson Education.
The over-inflated title is a holdover from when we were a startup in
those dot-com bubble days. But we are still here, so we probably didn't
do everything wrong.
5. Your goals in the Fedora Project
My immediate goal is to submit for consideration minor changes to
diskcheck that cause inodes to be checked in addition to bytes free.
I also would like to get nagios and the nagios plugins into Fedora, but
that would come later.
I wouldn't mind doing some QA, but I've having a hard time figuring out
all the policies and how Fedora works right now, so that too would
probably best be later, I think.
6. Historical qualifications
I have been the lead developer for the nagios plugins
(nagiosplug.sourceforge.net) since the time the plugins were separated
from the main nagios project, maybe about 3 years ago.
I have from time to time worked with Lamar Owen in developing and
debugging the RPMs for postgresql.
Over the last several years I've been programming in perl and php for my
work, and C for the nagios plugins. Before that I did a fair amount of
fortran work, but unless we start putting groundwater flow models into
Fedora Core, that may be less useful.
Why should you trust me? Good question... I'm still working to figure
out all the project policies, and most of my programming skills are self
taught. But I tend to be aware of my limitations, willing to lurk/search
around for answers when time allows, and ask direct questions when it
does not. And I think my experience with nagios plugins has been a
fairly good education in open source coding.
7. GPG KEYID and fingerprint
pub 1024D/CA2294A0 2003-11-12 Karl DeBisschop (Personal Key) <karl(a)debisschop.net>
Key fingerprint = 8D09 F9FB 0859 CA98 EDC5 0316 9B39 B0E7 CA22
sub 1024g/9C869B9C 2003-11-12
Karl DeBisschop <kdebisschop(a)alert.infoplease.com>
I have been working for the past several weeks on a visual gui
front end for yum. I am considering bringing that knowledge with me to
work on the fedora project.
But, Frankly, I am concerned about contributing to a program
with a trademarked name. I am interested in giving back to the
entiregnu/linux community not just the redhat community.
If someone likes my product, I would like them to be able to
freely use my work irregardless of their distro/flavor.
With this in mind what are your suggestions?
a. Go ahead and work on redhat-config-*.
b. Seek renaming of redhat-config-* to something vendor neutral.
c. Put my work in an up stream project and let it trickle down.
Does anyone knows, if there's any attemp out there to make a MS Exchange Server-compatible Mail/Groupware server ?
I mean, something like (Open)Exchange Server, that implements the Exchange protocol.
I guess it's a closed protocol, but perhaps, someone has tried to get into it !
* Wed Nov 12 2003 Phil Knirsch <pknirsch(a)redhat.com> 2:1.2.1-4.1
* Wed Nov 12 2003 Phil Knirsch <pknirsch(a)redhat.com> 2:1.2.1-4
- Another fix for the new automenu patch. Target was an optional parameter in
old s390utils, provided compatibility behaviour.