PLEASE READ: This list is going to be closed end on 2007-09-10

Hi all,

fedora-maintainers-list is going to be closed as discussed in

https://www.redhat.com/archives/fedora-maintainers/2007-August/msg00530.html

and agreed on by FESCo at the 2007-09-06 meeting:

http://fedoraproject.org/wiki/Extras/SteeringCommittee/Meeting-20070906

The plan is to close the fedora-maintainers-list on 2007-09-10.  The
fedora-devel-list will be the mailing that acts as the direct successor 
for the fedora-maintainers-list.  To subscribe please go to
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Thanks,
/B
--

-- 
Brian Pepple <bpepple <at> fedoraproject.org>

http://fedoraproject.org/wiki/BrianPepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B  CBDE 326A E936 810C C15E

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers

Summary of the 2007-09-04 Packaging Committee meeting

Meeting minutes and full logs of the packaging committee meeting which
occurred on 2007-09-04 are online:

http://fedoraproject.org/wiki/Packaging/Minutes
http://fedoraproject.org/wiki/Packaging/Minutes20070904

Executive summary:

The following draft is now official, having been accepted by FESCO
last week:

 * The first three sections of
   http://fedoraproject.org/wiki/PackagingDrafts/PHP (Requires and
   Provides for PEAR and PECL packages and Macros and Scriptlets for
   PECL packages).

These should be written into the guidelines soon if this hasn't
already been done by the time you read this.

There were no votes this week, so no issues are pending FESCO
ratification.

Misc business:

There was more discussion of the proposed guidelines for packaging
Python eggs: https://fedoraproject.org/wiki/PackagingDrafts/PythonEggs

This is a complex issue; if you have interest in Python packaging then
please read over the draft and voice your concerns.

gkrellm-hddtemp orphan/EOL

Hello,

I just found out that gkrellm can use a server mode hddtemp out of the box, 
which means I'm no longer interested in gkrellm-hddtemp.  If someone still 
wants it, please yell now and volunteer to maintain it - if a new owner does 
not show up, I'll orphan it for <= F-7 and invoke EOL process for F-8+ next 
weekendish.

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers

EPEL SIG Meetings now alternating between 17:00 and 23:00 UTC on Wednesdays

Hi all!

Just FYI, in the EPEL SIG meeting last week it was decided to have
alternating meeting times for our weekly meetings on Wednesdays.

In weeks with an even number (like this one, as it's the 36th week
currently; the gnome panel date applet will tell you the current week
number) we'll have the meetings at 23:00 UTC. In the weeks with and odd
number we'll continue to have them at 17:00 UTC.

Time are daylight saving times. During the winters we'll adjust them by
one hour, to make sure the effective meeting time stays the same.

So join us in the next meeting, which is scheduled for tomorrow at
23:00**UTC in #fedora-meeting.

CU
knurd

P.S.: Note that this new meeting scheme doesn't revert the plan to try
to get more stuff done on the list and less in the meetings. That still
the plan, but we need to experiment a bit how to actually have a good
workflow on the list (and quick meetings that still will be needed).

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers

Does koji keep old buildroots around?

Strange error from Koji today:

http://koji.fedoraproject.org/koji/getfile?taskID=145974&name=root.log

The error is:

Error: Missing Dependency: ocaml = 3.10.0-4.fc8 is needed by package 
ocaml-lablgl

which would indeed be true, except that nothing I have BuildRequire'd 
should need ocaml-lablgl.  In fact I don't want this package around 
right now because it has a broken dependency as above.

The only thing I can think is that koji doesn't start with a completely 
fresh root each time ... Is this true, and if so how to stop it from 
doing that?

Rich.

--

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com

tar problem

I can't understand why when i try to compile with mock (using devel
repo) i obtain this error : 
Building target platforms: i386
Building for target i386
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.76182
+ umask 022
+ cd /builddir/build/BUILD
+ LANG=C
+ export LANG
+ unset DISPLAY
+ cd /builddir/build/BUILD
+ rm -rf libupnp-1.6.0
+ /usr/bin/bzip2 -dc /builddir/build/SOURCES/libupnp-1.6.0.tar.bz2
+ tar -xf -
tar: error while loading shared libraries: libacl.so.1: cannot open
shared object file: No such file or directory

bzip2: I/O or other error, bailing out.  Possible reason follows.
bzip2: Broken pipe
        Input file = /builddir/build/SOURCES/libupnp-1.6.0.tar.bz2,
output file = (stdout)
error: Bad exit status from /var/tmp/rpm-tmp.76182 (%prep)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.76182 (%prep)

Someone could help me ?
Thanks

Eric

APR 32-bit API/ABI break in dist-f8

The apr-1.2.9-2 build on 32-bit platforms dropped LFS support and 
silently broke API and ABI.  This was due to a bug in the configure 
script where open() was called incorrectly when attempting to detect LFS 
capabilities, which started failing with the new glibc.

You are CC'ed on this mail if your package was built against a broken 
APR, either directly or indirectly via httpd or subversion, and needs to 
be rebuilt:

mod_dnssd-0.5-4.fc8.src.rpm:Tue Aug 21 18:20:20 2007
mod_evasive-1.10.1-4.fc8.src.rpm:Wed Aug 29 06:05:03 2007
mod_auth_pam-1.1.1-4.fc8.src.rpm:Wed Aug 29 06:38:41 2007
mod_auth_ntlm_winbind-0.0.0-0.6.20070129svn713.fc8.src.rpm:Wed Aug 29 19:39:46 2007
kdevelop-3.4.1-4.fc8.src.rpm:Thu Aug 30 00:39:38 2007

The following have either been rebuilt, or are being rebuilt:

mod_python-3.3.1-4.src.rpm:Tue Aug 21 12:34:45 2007
apr-1.2.9-2.src.rpm:Tue Aug 21 12:39:00 2007
mod_auth_pgsql-2.0.3-5.src.rpm:Tue Aug 21 13:54:32 2007
apr-util-1.2.8-11.src.rpm:Wed Aug 22 23:05:29 2007
httpd-2.2.4-9.src.rpm:Thu Aug 23 00:46:16 2007
mod_perl-2.0.3-12.src.rpm:Thu Aug 23 09:04:14 2007
subversion-1.4.4-5.src.rpm:Thu Aug 23 10:05:22 2007
mod_fcgid-2.1-5.fc8.src.rpm:Thu Aug 23 10:48:54 2007
rapidsvn-0.9.4-5.fc8.src.rpm:Thu Aug 23 15:41:05 2007
php-5.2.3-8.src.rpm:Tue Aug 28 20:46:11 2007
libapreq2-2.09-0.rc2.6.fc8.src.rpm:Tue Aug 28 23:16:44 2007
mod_security-2.1.1-2.fc8.src.rpm:Wed Aug 29 07:33:25 2007
kdesvn-0.13.0-3.fc8.src.rpm:Tue Aug 28 15:26:49 2007

bodhi: Adding "new package"

Hi,

I am facing a problem with bodhi's usability:

The problem: I have rebuilt a larger number packages for fc7 and want to
push them as updates. The current "new package" field however requires
maintainers to remember all package details of package they might have
pending. I.e. unless a maintainer carefully keeps book of koji-builds,
he will loose oversight.

Also, the "package name expansion magic" currently being used doesn't
help me much. It almost never returns results suitable for me (most of
my rebuilt packages are perl modules. Inserting "perl" or "perl-*"
doesn't help at all).

Can we please have a better method to insert packages to "new updates"?

Or even better: Can we have some sort of "browser" in bodhi, which
contains all "koji-built and yet unreleased packages"?

Ralf

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers

maven...

Hi!

As someone tried to rebuild maven stuff in dist-f8? If I look into koji,
it doesn't seem so.

However, there are for sure problems with ant 1.7. ant 1.6.5 is good 

I don't know if there might be other problems as well, but I would
suggest to try rebuilding maven stuff...

Best,
 Oliver

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers

Fedora branding and fedorapeople.org

Hi,

I've sort of "ripped off" some existing Fedora CSS to use on my own
Fedora hosted page. I've looked at the "Trademark Guidelines" linked
from that very page, but I have to admit that it's a bit too long and
complex for me to understand.

Since I'm not spinning off or forking anything, and using it as part of
the Fedora project itself, is it okay for me to do so?

http://thias.fedorapeople.org/

Just wondering  If not, I'll just have to spend a little time on
creating a different layout.

Matthias

(If anyone is curious about the .htaccess I use for IndexOptions and
SSI, feel free to peek around my home directory, the .htaccess should
be readable through ssh, unlike through http)

--

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.22.5-71.fc7
Load : 0.45 0.63 0.58

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers

Imminent package removal request : d4x

Hi,

Unless I'm mistaken, d4x (downloader for X) is licensed under the
_original_ Artistic license. As such, it is not acceptable for
inclusion in Fedora, so should be removed.

I've notified the author a few weeks ago, asking him if he'd be willing
to switch to the clarified or 2.0 versions of the Artistic license
(which are acceptable for Fedora), but only got one first answer,
nothing since... and nothing happened.

So I have no other choice than to retire the package and ask rel-eng to
remove it from development.

Matthias

--

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.22.5-71.fc7
Load : 0.58 0.72 0.83

--
Fedora-maintainers mailing list
Fedora-maintainers <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-maintainers