Why does eclipse-platform depend on tomcat?
by Christoph Höger
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
just wondering why eclipse should need an application server...
regards
chrsitoph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHTciihMBO4cVSGS8RAi7eAKC4dy6fKffNvue67yQ2mVSnW4lb2QCgl5o+
l/0A0qtBB2wCAMDKqn6Emsc=
=QmOv
-----END PGP SIGNATURE-----
16 years, 5 months
Re: rpms/postfix/devel postfix.spec,1.60,1.61
by Devrim GÜNDÜZ
Hi,
On Wed, 2007-11-28 at 12:22 -0500, Thomas Woerner wrote:
> Modified Files:
> postfix.spec
> Log Message:
> - made the MYSQL and PGSQL defines overloadable as build argument
Why do we enable MySQL support, but disable PostgreSQL support? I think
we should either set MySQL to 0, or make both 1, or move database
supports under seperate RPMs, like postfix-pgsql and postfix-mysql.
( /me hides his signature. ;) )
Regards,
--
Devrim GÜNDÜZ , RHCE
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
16 years, 5 months
FYI: mail-notification switches to GPLv3
by Thorsten Leemhuis
FYI, mail-notification switches to GPLv3 for version 5.0-rc1, which I
just submitted for building in rawhide. There are afaik no packages that
link against mail-notification, so this shouldn't create trouble for
anyone afaics.
CU
knurd
16 years, 5 months
Disable RPM's autoprovide function
by Stewart Adam
Hi,
A bug report at Livna (#1741) pointed out that the
xorg-x11-drv-nvidia-libs-32bit package is pulled in over mesa-libGL.i386
when the 32-bit library "libGL.so.1" is required on x86_64 (in the
user's case, it was while installing wine). libGL.so.1 is automatically
provided because of the scripts that RPM runs at the end of a build - Is
there some way to override this or disable it so that libGL.so.1 is only
provided by mesa-libGL?
Thanks,
Stewart
16 years, 5 months
updates-testing notification changes
by Luke Macken
As decided during last weeks QA meeting[0], bodhi will no longer spam
fedora-test-list with updates-testing notifications.
Bodhi now has RSS feeds that support querying updates using any combination
of release, status, or type:
https://admin.fedoraproject.org/updates/rss/rss2.0?status={pending,testin...
If you want to see a list of updates-testing packages that you have
installed on your local system, install the bodhi-client[1] package and run
`bodhi --testable`. From here, your testing feedback is encouraged and
will help ensure that we don't push any broken packages out to our users.
I also added support for anonymous access and feedback, so discussions about
test updates can now be held inside of bodhi. At the moment, anonymous
feedback is able to effect an updates karma. This is subject to
changing in the future, so if anyone notices this feature getting
abused, please let me know.
http://bodhi.fedoraproject.org
luke
[0]: http://fedoraproject.org/wiki/QA/Meetings/20071114
[1]: https://hosted.fedoraproject.org/projects/bodhi/wiki/CLI
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
16 years, 5 months
Outage of all Phoenix based systems
by Jesse Keating
Many of our systems just experienced a service blip due to a router
restart. We are currently working to bring services back online.
These services include but are not limited to; koji, bodhi, dist-cvs,
hosted.fedoraproject.org, mirrormanager, wiki, transifex, and more.
I will send another notice when services are back in order.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
16 years, 5 months
Plan for tomorrows (20071129) FESCO meeting
by Brian Pepple
Hi,
Please find below the list of topics that are likely to come up in the
next FESCo meeting that is scheduled for tomorrow, Thursday at 18:00 UTC
in #fedora-meeting on irc.freenode.org:
/topic FESCo meeting -- Any objection to this week's report from FPC at
https://www.redhat.com/archives/fedora-devel-list/2007-November/msg01850....
/topic MISC - Fonts Comps Policy -
http://fedoraproject.org/wiki/PackagingDrafts/FontsComps - Nicolas
Mailhot
/topic MISC - Drop orphans from F8< at some point during F9 - f13
/topic MISC - Using Matt Domsch's "doesn't rebuild" bugs as AWOL
detection, mark as orphaned at some point in F9, drop in F9+
/topic MISC - Do more frequent conflicts testing, with bugs filed, and
use AWOL detection
/topic MISC - automate the mailings of multiarch conflicts, it is hard
to test for people without biarch computers - from Patrice Dumas
/topic FESCO-Meeting -- Plan to get Merge Reviews finished by F9 -- all
/topic FESCO-Meeting -- Features -
http://fedoraproject.org/wiki/Releases/9/FeatureList -- all
/topic Status Update: Compat Policy
http://fedoraproject.org/wiki/JeremyKatz/DraftCompatPackages - jeremy
/topic Status Update: FESCo Proposal Template - f13
/topic FESCo meeting -- Free discussion around Fedora
You want something to be discussed? Send a note to the list in reply to
this mail and I'll add it to the schedule (I can't promise we will get
to it tomorrow, since we have a pretty full schedule). You can also
propose topics in the meeting while it is in the "Free discussion around
Fedora" phase.
If your name/nick is on above list please update the status on the
Extras schedule pages in the wiki ahead of the meeting. That way all the
other FESCo members and interested contributors know what up ahead of
the meeting. And we will avoid long delays in the meeting -- those often
arise if someone describes the recent happenings on a topic directly in
the meeting while all the others have to wait for his slow typing...
Later,
/B
--
Brian Pepple <bpepple(a)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
16 years, 5 months
AWOL: jpo
by Tom Callaway
It seems that Jose Pedro Oliveira (aka jpo) is not coming back to
Fedora. He has 28 open bug tickets, most of them in the new state, and
he has not touched any of his packages or bugzilla since June.
I'm initiating the AWOL process so that we can work on finding new homes
for all of his many packages, and start bugfixing them.
Here's the buglist:
https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&short_desc_...
I think that all reasonable attempts to contact the maintainer have been
made, I emailed him several months ago to try and get a response and got
none.
If he does not respond to this email in a week, I'll take over all of
his packages (temporarily) and post to fedora-devel that they're all up
for grabs.
Thanks,
~spot
16 years, 5 months
Should "yum install" be case sensitive?
by Michał Bentkowski
Hi!
Recently, a funny thing happened on Polish Fedora forum. Some users
were talking about Miro but rest of them weren't able even to install
that... After some time it turned out that they tried to type "yum
install miro" instead of "yum install Miro".
So my question is the same as in the topic: should "yum install" be
case sensitive?
I haven't checked but I'm quite sure (correct me if I'm wrong) that
there are no packages in repo whose names differ in letter size.
What's more: "yum list" command is case insensitive and there's
nothing wrong with it, is there? I know that you can say that these
users I wrote about in the beginning should have used "yum list" first
and then they would have found out why things went wrong but it makes
a need to type more and more commands.
"yum install" gives a summary what packages are going to be installed
so if a user wanted to run "Foo", but not "foo" she/he could break the
installation.
Besides, pressing SHIFT key could be painful ;-)
So my proposal is to make "yum install" (and probably "yum update" as
well) case insensitive.
Just think about it :)
Regards.
--
Michał Bentkowski
mr.ecik(a)gmail.com
16 years, 5 months
