Development

Orphaned taglib

I've orphaned "taglib" in response to the hostilities found in the
FESCo meeting log. Most likely Rex Dieter will pick it up, but I want
to let the list know as there are other dependencies on it.

Bug 549051 - package config file not installed (.pc)

I need help here too. The problem ist here the cmake don´t compile the
.pc file (pkgconfig file)
And upstream don´t will fix that :(.
I have talked about this with cwickert and he have said it is patchable
but he don´t have the time to make it.
Can any other please help me?

https://bugzilla.redhat.com/show_bug.cgi?id=549051

Meeting summary/minutes for 2010-03-09 FESCo meeting

===================================
#fedora-meeting: FESCO (2010-03-09)
===================================

Meeting started by nirik at 20:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2010-03-09/fesco.2010-03...
.

Meeting summary
* #314 Wordpress bundles libraries (nirik, 20:03:59)
* AGREED: wordpress should unbundle libraries that are upstream
identical. Can bundle 3 heavily modified php files. (nirik,
20:11:32)

* Daylight savings time.

F13 Alpha - Zarafa

All,

I'm curious why Fedora chose to include Zarafa as opposed to other (mostly) opensource groupware solutions?

Ones that come to mind: Scalix, Open-Exchange, Zimbra.

Thanks,
Brian

F-13 Branched report: 20100309 changes

Compose started at Tue Mar 9 09:15:13 UTC 2010

Broken deps for i386

Need help with this FTBFS fife bug

Need help with this FTBFS fife bug. It don´t find boost for compiling.
But with F-13 ist works not in devel (F-14)

Can anyone please help to find out why please?

Update policies: What about *regular* updates?

We are talking a lot about update policies recently. While I do (mostly)
agree with those who suggested a more conservative approach, I wonder
what will then happen to packages that actually *need* regular updates.
Let me give you two examples:
1. openal-soft: Is under steady development and improves a lot.
From time to time, I guess once a month, the maintainer pushes
an update. Usually this updates fixes at least one bz issue, so
I don't think it should be a problem with the new policy. I just
want to make sure.
2.

Updates proposal - alternative draft 1

Hi,

Since it is the fav season for proposals apparently, let me throw in my
Fedora/hat in the ring too. This only applies to updates to general
releases.

For critical path packages
(http://fedoraproject.org/wiki/Critical_Path_Packages) :

* Must go through updates-testing repository
* Only major bug fixes and security fixes.
* Must go through updates testing repository even for security fixes
Rationale: Expedited security fixes have caused some serious regressions
in the past (D-Bus, Bind, Thunderbird updates etc).

QA's Package update policy proposal

Hello,

I have been (together with the QA team) working on a 'Package
update policy' proposal. Because Matthew Garrett yesterday
presented his own proposal regarding this topic, we decided
to also present our proposal, albeit still unfinished.

The proposal is here:

https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_policy

I would like to stress that it is still in development and
heavily discussed (see Discussion page). The terminology
may not be correct, because I'm not a native speaker.

KDE-SIG meeting report (10/2010)

This is a report of the weekly KDE-SIG-Meeting with a summary of the
topics that were discussed.

rawhide report: 20100309 changes

Compose started at Tue Mar 9 08:15:08 UTC 2010

Broken deps for i386

Announcing the release of Fedora 13 Alpha!!

The Fedora 13 "Goddard" Alpha release is available! What's next for the
free operating system that shows off the best new technology of
tomorrow? You can see the future now at:

http://fedoraproject.org/get-prerelease?anF13a

== What is the Alpha release? ==

The Alpha release contains all the features of Fedora 13 in a form that
anyone can help test. This testing, guided by the Fedora QA team, helps
us target and identify bugs. When these bugs are fixed, we make a Beta
release available. A Beta release is code-complete, and bears a very
strong resemblance to the third and final release.

[Test-Announce] Announcing the release of Fedora 13 Alpha!!

The Fedora 13 "Goddard" Alpha release is available! What's next for the
free operating system that shows off the best new technology of
tomorrow? You can see the future now at:

http://fedoraproject.org/get-prerelease?anF13a

== What is the Alpha release? ==

The Alpha release contains all the features of Fedora 13 in a form that
anyone can help test. This testing, guided by the Fedora QA team, helps
us target and identify bugs. When these bugs are fixed, we make a Beta
release available. A Beta release is code-complete, and bears a very
strong resemblance to the third and final release.

X.org on F13 Alpha and monitor setup

Today I wanted to give F13 Alpha a test and installed it. The
installation went fine but I do not get a proper screen resolution
setup. The basic setup was done via system-config-display, I only added
a modeline. But it seems to me that the modeline is ignored. Is this a
new behavior because of kernel based mode setting or is this a bug and I
should file a report? At the moment the screen resolution is 1024x768
but I expected 1280x1024. Can someone confirm this behavior?

I'm wondering because before F10 was installed, and I even did not need
to setup a modeline.

Orpahning some packages

Orphaning couple of packages:

- JSDoc (upstream has moved to competing project
http://code.google.com/p/jsdoc-toolkit/, so unless somebody needs this
package, I think it is ready for retiring from Fedora completely)
- python-urllib2_kerberos -- unsuccessful attempt to use this, lost any
interest in the package just a day after packaging it.

Both packages have released ownership, who wants to tenderly love them
so I don't have to coldly left them in the blizzard?

Matěj

[Test-Announce] Bugzappers Meeting Agenda for 2010-03-09

Additions or corrections to the agenda? Reply to this email.

= Agenda =

* follow ups from last meeting

* your item here! (let us know before the meeting)

* open floor

Please do come out for the meeting - it'd be great to see more faces,
and we don't bite, we promise! It's a great opportunity to raise any
issues you've come across while bugzapping, or ask any questions you
might have.

PROPOSAL: Fedora user survey

Folks,

I will propose this to FESCo through their normal channels.

My proposal is that we create a "Fedora User Survey" and create a link
on the fp.o website with a few very simple questions. One of those
questions would be what users think about the current update policy,
using plain (and as non-bias as possible) language to explain.

This isn't an attempt to undermine FESCo, but you have to remember that
users don't typically directly vote for FESCo or otherwise get involved
in big decisions like this that will affect them.

Re: Update question: some user data

fedora for the fact that it is >>leading the way with the newer software and
that it has constant updates. (ie >>freedom,friends,features,first!) this
argument that most fedora users want a more stable system is not >>what the
fedora users i came across are after. tbh i think this whole identity crisis
is blown of of all >>proportion, you'd think that something like this would
have come with the fedora10 dbus probs or the >>'stabilisation cannot be
detected' not now with a little kde popup window :0

+1 for these comments.

Plan for tomorrow's (2010-03-09) FESCo meeting

Following is the list of topics that will be discussed in the FESCo
meeting tomorrow at 20:00UTC (3pm EST) in #fedora-meeting on
irc.freenode.net.

Followups:

#314 Wordpress bundles libraries

New Business:

- Daylight savings time. Move meeting time or keep the same?
- #349 comps in git - notting
- Proposed Updates Policy Change - mjg59
- Fedora Engineering Services Tickets/Updates.

Proposed udpates policy change

This is the policy that I expect to be discussed during the Fesco
meeting tomorrow.

How to install software without root password (PolicyKit?)

Hi, Fedora 12 was planned to have installation of packages without
users needing to enter root password.

How do I enable this feature via PolicyKit?

I read this article:
http://skvidal.wordpress.com/2009/11/18/polkit-and-package-kit-and-chang...
but even after doing that it is still the same and "yum install
package" asks for root password.

Cheers!

F-13 Branched report: 20100308 changes

Compose started at Mon Mar 8 09:15:17 UTC 2010

Broken deps for i386

F13 Release Slogan - Rock it.

For the 13th Release of Fedora, "Goddard," the Fedora Marketing team
ran an open, community based process of slogan submissions, found at
https://fedoraproject.org/wiki/Release_slogan_SOP.

libedit: transferring ownership

I would like to transfer ownership of the libedit package to Kamil
Dudka (kdudka). I am a bit wary of PackageDB transferring not letting
me select the new owner. Could someone please take care of it or
advise what I need to do about this?

I do not want to remain as a co-maintainer.

Thanks,
Debarshi

Upcoming Fedora 13 Schedule

Start End Name
Thu 04-Mar Tue 09-Mar Stage & Sync Alpha to Mirrors
Tue 09-Mar Tue 09-Mar Alpha Public Availability
Tue 09-Mar Tue 23-Mar Alpha Testing
Fri 12-Mar Fri 12-Mar Beta Blocker Meeting (F13Beta) #1
Tue 16-Mar Tue 16-Mar Software: Start Rebuild all translated packages
Tue 16-Mar Tue 23-Mar Software: Rebuild all translated packages
Wed 17-Mar Thu 18-Mar Create Beta Test Compose (TC)
Thu 18-Mar Wed 24-Mar Test Beta 'Test Compose'
Fri 19-Mar Fri 19-Mar Beta Blocker Meeting (F13Beta) #2
Tue 23-Mar Tue 23-Mar End of Alpha Testing

Managing spec files

Hi All,

I am looking at building a fedora package. I have been over guidelines
and taken a look at the build system. What I am not clear on is how I
maintain spec files for different distributions i.e., F12, F11, F10, or
even EPEL.

Do I have to branch and maintain each spec file separately or is there a
better way? Are there any tools that abstract the commonality? Do
people try to write spec files that work on any distro with conditionals?

Thanks for any wise words,

Matt.

rawhide report: 20100308 changes

Compose started at Mon Mar 8 08:15:10 UTC 2010

Broken deps for i386

What are the rules for which package we build against in F-13?

So I submitted a rebuild for libguestfs in F-13 (just now). This
was built against:

plymouth-core-libs 0.8.0-0.20100114.2.fc13

But the version of plymouth that I get when I install plymouth from
F-13 updates-testing on a local machine (after
'yum --enablerepo=\* clean all') is:

plymouth-core-libs 0.8.0-0.20100225.1.fc13

and neither of those versions is mentioned by Bodhi.

How does one deal with obsoleted updates from updates-testing

My F-13 system produces the following output from yum list extras:
Extra Packages
glibc.i686 2.11.90-14
installed
glibc-common.i686 2.11.90-14
installed
glibc-devel.i686 2.11.90-14
@updates-testing
glibc-headers.i686 2.11.90-14
@updates-testing
gtksourceview2.i686 2.9.7-1.fc13
installed
nscd.i686 2.11.90-14
installed

The glibc packages (including nscd) were in updates-testing, but have
been obsoleted, and so 2.11.90-12 is now the current version again.

Push an update to F-13

What is the new process to push an update to F-13 between alpha and beta? The
packages I have in mind are out of the set of critical packages.

Should %{name}-javadoc package require %{name}?

Hello All!

I just found that many java-related packages have packaging issues,
and one of them draws my attention - explicit "Requires: %{name} =
%{version}-%{release}" in some *-javadoc packages. Since my java
experience is rather small, I would like to ask you, dear List,
whether %{name}-javadoc sub-packages really must require %{name}?

howto group push?

mercurial and tortoise-hg need (generally) to be pushed in sync. They
are maintained by 2 different people. What are suggested ways to make sure
pushes are synchronized?

Karma threshold for kernel

Hi,

what kind of karma threshold is set for the kernel?

The page in bodhi says it has a karma of 9, but if you count it, it's
13+ and 10-

And the kernel got -5 since it's pushed to stable. Shouldn't that one
stay out of stable for now?

https://admin.fedoraproject.org/updates/kernel-2.6.32.9-67.fc12

I'm running 2.6.32.9-70 meanwhile from updates-testing.

Announcing `gold-rebuild' - link your packages with gold now

Past months I spent investigating `gold' - the new GNU linker
and how it now works with stock Fedora packages.

Result is `gold-rebuild', Bash script which automates `gold's
involvement in Mock buildroot. Tarball can be obtained here:
http://mnowak.fedorapeople.org/gold-rebuild/dist/

What it can do for you? You give it package name or comps group
to rebuild and it downloads binutils daily snapshot, incorporates
it into latest Rawhide binutils SRPM and builds it with `gold'
instead of usual `ld' as a /usr/bin/ld.

sos update causing PackageKit to barf

The latest sos update is not signed:

[hughsie at hughsie-t61 packages]$ rpm -qp sos-1.9-1.fc12.noarch.rpm
warning: sos-1.9-1.fc12.noarch.rpm: Header V3 RSA/SHA256 Signature,
key ID 57bbccba: NOKEY

This causes PackageKit to barf. How come this update was pushed
without a signature and all the other are fine?

Richard.

should man-pages-* have Requires: man?

For now in fedora there are 11 packages which contains language
mutations of man-pages (man-pages-{cs,da,de,es,fr,it,ja,ko,pl,ru,uk})
and man-pages package.
Only 2 of them (man-pages-es, man-pages-it) requires man package. I
think man dependences should be consistent in all man-pages* packages.
From my point of view man dependency should be in all of them.
Any ideas?
Ivana Hutarova Varekova

I love Fedora

Dear readers.

The last two weeks have had a few big, very hot discussed threads. I
personally was a few times way too much involved with my feelings and
i suspect a few others here as well.

As the subject says it clearly, i love Fedora. I love it as it is. It
is leading edge, i can have latest versions of software in released
Fedora versions without much pain (thirdparty-repos) and still have a
rock solid system. Yes that's what i think about my Fedora.

F-13 Branched report: 20100307 changes

Compose started at Sun Mar 7 09:15:08 UTC 2010

Broken deps for i386

Move a configuration file

Hello,

I have a small question regarding a "configuration file" for BackupPC.

BackupPC requires a file for apache users.

selinux-policy-targeted update failure

Updating : selinux-policy-targeted-3.6.32-92.fc12.noarch
64/215
libsepol.scope_copy_callback: audioentropy: Duplicate declaration in module:
type/attribute entropyd_var_ru\
n_t (No such file or directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file or
directory).
semodule: Failed!

rawhide report: 20100307 changes

Compose started at Sun Mar 7 08:15:15 UTC 2010

Broken deps for i386

New version of PackageDB in staging

Hello all,

The first beta of the new PackageDB is running in our staging environment
now.

https://admin.stg.fedoraproject.org/pkgdb/

All the features for 0.5.x should be present but there's definitely bugs to
be found in the implementation. When you across one, feel free to find me
on IRC to report it (abadger1999) or send email to me
<...> at fedoraproject dot org. If it's not something that I feel will be fixed
for 0.5.0, I'll open a ticket on the fedorahosted trac instance for it.

URLs should no longer change position but a few minor changes in query
parameters may still occur.

"Welcome to Fedora" docs/video/audio

Added marketing in cc (probably better place for discussion).

Does it make sense to ship a small pdf (say having a title "Welcome to
Fedora") or if possible a video for users as an introduction to our
distribution ?

If yes, because it makes sense to keep it as small/simple as possible
what should it target to achieve ?

Points out of my head are:
1. New features
2. Availability of options for just updating system for security
fixes, selected enhancements or bugfixes for some applications
3. Ways to get support/help from community - bonding
4.

Expect more positive bodhi karma / check karma automatism

Good news everyone,

you can probably expect to receive more positive bodhi karma for your
updates in the future (or you already got unexpected much), because
there is now a script called 'fedora-easy-karma'[0], that makes
providing feedback a lot easier.

This makes it more important to consider the "karma automatism" for your
updates. By default testing updates updates are declared stable when
they get three karma points. In the past this probably never happened,
but now I have seen several updates, where this occurred.

F-13 Branched report: 20100306 changes

Compose started at Sat Mar 6 09:15:12 UTC 2010

Broken deps for i386

Update question: some user data

I thought to myself yesterday, 'what this long and fractious thread
about update policy *really* needs is some unscientific and
controversial numbers'. =) So, I ran a forum poll! Everyone loves those,
right?

Here it is: http://forums.fedoraforum.org/showthread.php?t=241710

I tried to present the poll in a very neutral way, and as far as I know,
it hasn't been linked to from anywhere else; only regular forum members
are likely to come across it.

proven packager needed - mrpt

Following the previous thread on opencv:
http://lists.fedoraproject.org/pipermail/devel/2010-February/131584.html

Almost all packages have been rebuilt against opencv-2.0.0-7 (thank you,
guys !) except mrpt.
We didn't get any news from mrpt only maintainer jlblanco and most
packages have been pushed to stable .
I need a proven packager to rebuild mrpt (a simple recompilation should
be fine) so i could push opencv-2.0.0-7 into stable as soon as possible.

regards,
H.

Another great update

While we are at it, here is another great update:
https://admin.fedoraproject.org/updates/F11/FEDORA-2010-3326

* New version introduced in F11.
* Doesn't fix any bugs but it's an enhancement only.
* Useless update description "update to 4.7.1".
* And *of course* it was pushed directly to stable, even in F-13.

Dear maintainers, please stop this!

Regards,
Christoph

rawhide report: 20100306 changes

Compose started at Sat Mar 6 08:15:05 UTC 2010

Broken deps for i386

gcc internal error on F13

I am trying to build a package on F13, and got a gcc internal error:

http://koji.fedoraproject.org/koji/taskinfo?taskID=2034791

I have no idea how to proceed ....

The package builds just fine on F12, F11 and F10.

Koji or me at fault?

Hi,

I've imported monodevelop-debugger-gdb for f13 and rawhide and have
tried to build it. Koji is going through the setup, but then falling
over on the build. Looking at the logs, it looks like a python
problem...

http://koji.fedoraproject.org/koji/taskinfo?taskID=2034431&name=build.log

Can anyone up the food chain verify where the problem is please?

TTFN

Paul

Handling Rawhide

Hi

Everytime I push a new update for Fedora 13 I am also now committing and
building in Rawhide and I am wondering if that is necessary or what
would the best way to avoid repetitiveness? Would the buildsystem
inherit whatever is the newer version in between these branches?

Rahul

Perl, Imap and Kerberos

Hi all,

I am currently writing an IMAP client script in perl.

Since this script will only be used in one single use case and the IMAP
server supports Kerberos authentication, I thought it would be a good
idea to use Mail::ImapClient together with Authen:SASL

This works well until I want to really something, since the kerberos
protocoll implements some encryption of every message and Authen::SASL
does not support more than authentication.

Any ideas how one would implement the en/decryption using perl?

F-13 Branched report: 20100305 changes

Compose started at Fri Mar 5 09:15:06 UTC 2010

Broken deps for i386

Re: Limited options in bugzilla

*>>* flags
*>*> fedora-review: i have only a "?", i dont have any "+"
*>*> fedora-cvs: i can't change it, see the link below.
*>>*
*>*> my info:
*>*> taljurf: Approved Groups: fedorabugs packager marketing altvideos freemedia
*>*> cla_fedora cla_done cvsl10n ambassadors
*>>*
*>>* flags section screenshot (notice the fedora-cvs)
*>*> http://taljurf.fedorapeople.org/bugzilla-flags.png
*>>*
*>*> What should i do?
*>>*
*>*> Thanks in advance
*>[..]

So what should i do, fas is registered to my gmail, while bugzilla is
registered to @fedoraproject.org
i saw some other guys which have their bu

rawhide report: 20100305 changes

Compose started at Fri Mar 5 08:15:12 UTC 2010

Broken deps for i386

Speedup the availability of updates (was: Re: Push scripts, mash) pushes in Bodhi (urgent call for feedback))

Hi,

I have some ideas to speedup the availability of updates. Are there any
reasons except that the tools to do this do not exist yet, to switch to
this? I created a wiki page for this:
https://fedoraproject.org/wiki/User:Till/update_availability_speedup_ideas

The basic idea is to create new repos $repo-recent, that only includes
metadata for the new rpms, but references to the same rpms on the
filesystem that $repo uses.

Regards
Till

Push scripts, mash (was: Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback))

(Starting a new thread because this hardly has anything to do with the
original infamous thread.
Dear hall monitors: I hope I won't get put on moderation for posting this,
but this subthread didn't have much to do with the original subject. If you
also want me to stop posting to this split thread, please tell me and I will
refrain from posting further replies to it.

Limited options in bugzilla

When i'm using bugzilla, i've noticed that i have some limited options in
flags
fedora-review: i have only a "?", i dont have any "+"
fedora-cvs: i can't change it, see the link below.

my info:
taljurf: Approved Groups: fedorabugs packager marketing altvideos freemedia
cla_fedora cla_done cvsl10n ambassadors

flags section screenshot (notice the fedora-cvs)
http://taljurf.fedorapeople.org/bugzilla-flags.png

What should i do?

Thanks in advance

Upcoming Bugzilla Changes

Greetings

I hope everyone is well. With the worst of the “snowpocalypse" behind us 
(here in the Northern Hemisphere) and the branching of Fedora 13, there
is a bit of ‘spring cleaning’ the the bugzappers need to do.

To semi-rolling or not to semi-rolling, that is the question...

Obviously, some people want this and some don't. It isn't appropriate
to simply hand down an edict that things will be one way or the other if
we truly consider Fedora a community run project. It must be a
community decision. That means, as Adam Williamson pointed out, this is
likely a decision to be made by the board, based upon what the community
wants and what's best for Fedora.

But let's be clear. That's a *policy* decision. One of the things that
got very confusing in the previous thread(s) was the intermixing of
policy decisions and technical issues.

F-13 Branched report: 20100304 changes

Compose started at Thu Mar 4 09:15:19 UTC 2010

Broken deps for i386

how to make things better(tm)

To be clear, no one is ignoring anything. (What a silly thing to say?...
well, maybe not so silly... means there's a bad pr/perception problem. :( )

Like most any group making hard decisions, the KDE SIG bases them on the
best information available. Fact is, we extensively tested this new version
for over a month, and every serious issue/blocker that was reported or
identified was addressed prior to releasing this.

Unfortunately, it seems there were more problems than what we were aware of
when the decision was made to do the 4.4.0 (stable) update.

duplicate f13 package announcements

I don't know if this has already been raised but I notice on the
package-<...> at lists dot fedoraproject.org list that several Fedora 13
packages keep getting announced, for example, by checking the archives I
see that fedora-release-13-0.6 has been announced 6 times in March and a
further 7 times in February. I suspect there is a glitch in the package
management system somewhere.

Michael Young

rawhide report: 20100304 changes

Compose started at Thu Mar 4 08:15:15 UTC 2010

Broken deps for i386

Harmless KDE feature upgrades - yeah right

Ironically it happened again, just now when these FESCO threads
are still warm.

My desktop gui processes leak enough mem that I need to restart
couple times a week or system will run out of memory. Today
I started with updating the F11 with yum. During the update,
I noticed that it's pulling in the kde-4.4.0, scary. Then reboot.

Now when I logged in, noticed that desktop has really changed
quite a bit, some visual stuff even fixed.

Then I tried to start kmail to start working.

Problem with openoffice yum update

I cannot do a yum update of openoffice on F-13 RC4 with the
updates-testing repo enabled. There seems to be an inconsistency around
the dep checking, with it wanting both the old and new versions of
openoffice.org-langpack-en.

[Test-Announce] Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC Recap

Greetings,

Representatives from Fedora QA, Rel-Eng and Development met on IRC to
review determine whether the Fedora 13 Alpha release criteria [1] have
been met. The team agreed that the Alpha criteria have been met, and to
proceed with releasing F-13-Alpha-RC4. For additional details, please
refer to the attached minutes.

Thanks,
James

[1] https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria

Provide more testing feedback (was: Re: Refining the update queues/process)

If it is limited on the packages the user is installed, a lot of
packages are not tested.

So here is a first ugly script to easily give feedback for all installed
testing updates that were created after a certain date (I did not find
an easy way to get all testing updates, one did not yet comment on):
http://till.fedorapeople.org/tmp/give-feedback.py

It kind of works like this: Show the update, ask for karma to create a
comment, otherwise it is skipped.

Font rendering in F13

Hey,

early in the F13 cycle, we enabled the bytecode interpreter in our
freetype package, since the patents on that have expired last fall.
Unfortunately, it turned out that many free fonts don't actually benefit
from this, and actually look worse with the bci.

[Guidelines Change] Changes to the Packaging Guidelines 04/09 - 02/10

It has been almost a year since we announced changes to the Packaging
Guidelines, so this will be a long list.

[Test-Announce] SSSDbyDefault Test Day postponed

Greetings,

The scheduled March 4 test day, with a focus on SSSDbyDefault [1], has
been postponed for a later date. Several planned changes to simplify
the user interface of authconfig-gtk were not completed in time for the
test day. The event will be reschedule for a later date.

Apologies for any inconvenience. Stay tuned to
https://fedoraproject.org/wiki/QA/Fedora_13_test_days for further
updates.

Thanks,
James

[1] https://fedoraproject.org/wiki/Features/SSSDByDefault

usb_modeswitch by default

Hi

Increasingly a number of broadband connections require usb_modeswitch to
connect online

http://who-t.blogspot.com/2010/03/vodafone-australia-mobile-broadband-an...

Any opposition to adding this to the base group?

Rahul

[HALL-MONITORED] Update threads are now hall-monitored

Okay. This has gone on long enough. The signal is gone from the
following threads:

* FESCo wants to ban direct stable pushes in Bodhi (urgent call forfeedback)
* Worthless updates
* Refining the update queues/process

Accordingly, I'm marking those threads as Hall-Monitored. Please stop
posting in them. If you have a concrete suggestion on how to improve
Fedora updates, please write it in a wiki page, open a FESCo trac
ticket, and they will consider it.

~spot, Hall Monitor

bz532373, was Re: tor dependency insanity.

I met with them on numerous occasions (eg last at GSoC Mentor Summit
where we toegether worked on fedora tor bugs and created numerous "upstream'
bug reports so I could file the below bugzilla report to you.

WONTFIX:

* Sun Dec 17 2006 Enrico Scholz -
0.1.1.26-1
- do not turn on logging by default; it's easier to say "we do not log
anything" to the police instead of enumerating the logged event
classes and trying to explain that they do not contain any valuable
information

Upstream reports a logging bug.

F-13 Branched report: 20100303 changes

Compose started at Wed Mar 3 09:15:12 UTC 2010

Broken deps for i386

rawhide report: 20100303 changes

Compose started at Wed Mar 3 08:15:10 UTC 2010

Broken deps for i386

Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)

Thanks for the concern, Kevin. When will KDE 4.4.2 be available? I've
skipped all updates on my mother's computer since you pushed 4.4.0 to
updates-"stable". With 4.4.2 I might finally consider applying
updates again.

P.S. If you didn't notice the sarcasm, then I'm not supporting major
updates in the so-called "stable" branches. Such updates are probably
fun for people who want to have shiny toys to play with, but some
people want to get work done. Using Fedora.

List Troll

Build F-13 collection packages for all language translators

Dear Fedora package maintainers

This is kind reminder asking you to rebuild your package with latest
translation. Localization team has been translating for updated and/or
newly added strings since the String is frozen (2010-02-09). To allow
translators to review and correct their latest translation in UI, this
is essential. This is different from 'Rebuild all translated packages
for Beta', this is added entry since Fedora 12 [1].

"Build F-13 collection packages for all language translators" is
expected between 2010-03-03 to 2010-03-05.

gnome-desktop meta package

Folks,

I just did a SPARC install (thanks to Dennis for the assistance too) and
elected only for a very minimal install. I then decided to add GNOME
bits just to see what worked for curiosity. I did an "yum install
gnome-desktop", thinking this would pull in nautilus, etc.

I don't think this is a secondary arch thing, but wouldn't it make sense
that this would pull in more than a few packages?

Jon.

Worthless updates

It took me all of about 2 minutes to find a worthless pending update for
Fedora 11.

https://admin.fedoraproject.org/updates/perl-Locale-Maketext-Lexicon-0.7...

No data in the bodhi ticket.

Rpm changelog says "Upstream update"

If I google for upstream and look for a changelog, I come to this:

http://cpansearch.perl.org/src/DRTECH/Locale-Maketext-Lexicon-0.79/Changes

in which the grand total of changes between what shipped with F11, and
what is in this update is:

* Locale::Maketext::Lexicon::Tie
- Removed a deprecated use of "defined %" for Perl 5.11+

* Locale::Maketext::Lexic

Meeting Summary/minutes for the 2010-03-02 FESCo meeting

===================================
#fedora-meeting: FESCO (2010-03-02)
===================================

Meeting started by nirik at 20:00:00 UTC.

[Test-Announce] Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC (2010-03-03 @ 20:00 EST)

Join us on irc.freenode.net #fedora-meeting for this important meeting.
This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it *WEDNESDAY
EVENING* in North America: 20:00 EST, 17:00 PST.

"Before each public release Development, QA, and Release Engineering
meet to determine if the release criteria are met for a particular
release. This meeting is called the: Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of
the QA Team."

For more details about this important meeting see:
https://fedoraproject.org/wiki/Engineering_Readiness_Meetings

Upcoming Fedora 13 Tasks

Start End Name
Tue 16-Feb Tue 09-Mar Development: Alpha Freeze
Thu 18-Feb Thu 04-Mar Test Alpha Candidate
Wed 03-Mar Wed 03-Mar Alpha Go/No-Go Meeting #2 (20:00 EST)
Wed 03-Mar Fri 05-Mar Build F-13 collection packages for all language
translators
Thu 04-Mar Thu 04-Mar Start Stage & Sync Alpha to Mirrors
Thu 04-Mar Thu 04-Mar Alpha Project Wide Release Readiness Meeting
Thu 04-Mar Tue 09-Mar Stage & Sync Alpha to Mirrors
Fri 05-Mar Fri 05-Mar Alpha Export Control Reporting
Tue 09-Mar Tue 09-Mar Alpha Public Availability
Tue 09-Mar Tue 23-Mar Alpha Testing
Fri

F-13 Branched report: 20100302 changes

Compose started at Tue Mar 2 09:15:13 UTC 2010

Broken deps for i386

tor dependency insanity.

So after having heard the nth discussion about tor, I decided to check it out.
I tried installing it on a stripped down f12 box that has no X, or other stuff
unnecessary for routing network packets.

What happened next has me lost for words.
Our dependency chains suck.

Dave

(12:24:07:root at firewall:~)# yum install tor
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package tor.i686 0:0.2.1.23-1200.fc12 set to be updated
--> Processing Dependency: tor-core = 0.2.1.23-1200.fc12 for package: tor-0.2.1.23-1200.fc12.i686
--> Processing Dependency: tor-lsb = 0.

KDE-SIG meeting report (09/2010)

This is a report of the weekly KDE-SIG-Meeting with a summary of the
topics that were discussed.

rawhide report: 20100302 changes

Compose started at Tue Mar 2 08:15:16 UTC 2010

Broken deps for i386

Invitation to connect on LinkedIn

LinkedIn
------------Henrique Castro requested to add you as a connection on LinkedIn:
Marco,

I'd like to add you to my professional network on LinkedIn.

- Henrique

Accept invitation from Henrique Castro
http://www.linkedin.com/e/XfpwrrIudepdoTBH97AF966XIXLdIgHFX5dOfRhWUqx/bl...

View invitation from Henrique Castro
http://www.linkedin.com/e/XfpwrrIudepdoTBH97AF966XIXLdIgHFX5dOfRhWUqx/bl...

Who broke opencv ? (was Re: Broken dependencies with Fedora 12 + updates-testing - 2010-03-01)

Why opencv has experienced broken dependency at first step ?
I've miss the required announcement, and even if it was announced, it would
have be stroken by a denial from my side!
That kind of development is unappropriate in a stable release.

Nicolas (kwizart)

2010/3/1 Haïkel Guémar <<...> at gmail dot com>

Bodhi karma feature request

Split off from the stable pushes in Bodhi thread just because I'd like
to see it not get lost.

One could argue that the current bodhi karma system is simply too
simplistic for real use cases.

Plan for tomorrow's (2010-03-02) FESCo meeting

Following is the list of topics that will be discussed in the FESCo
meeting tomorrow at 20:00UTC (3pm EST) in #fedora-meeting on
irc.freenode.net.

Followups:

None.

New Business:

#343 cloture rule/procedure for fesco meetings
#344 Policy proposal: contributing to Fedora should be FUN

Fedora Engineering Services Tickets/Discussion
https://fedorahosted.org/fedora-engineering-services/

assigned tickets / status update:

#2 SIGs roundup and pinging - jds2001
#8 Document Fedora as android devel platform - stickster

unassigned tickets:

#4 tool idea: script to evaluate buildroot poisoning

OT: fas-username vs. local username for fedora-cvs

Hi all!

My username on my private pc is josephine, my username on my
workstation is josephine.tannhauser, but my fas-username is tannhauser.

how can I use fedora-cvs on these machines? It seems that fedora-cvs
want to use the local username. How can I change this behavior with
editing a configfile in my home-dir? I don't want to edit the
fedora-cvs package-files.

Currently i have a alternate user on my private pc, but this is not a
good solution. :-)

Thrashing between updates-testing and updates

Currently I am following F13 and I have been noticing a lot of packages
disappearing from updates-testing before showing up in the branched release
(but similar things happen with normal updates, just less often).

When things disappear from updates-testing it isn't immediately obvious
if this is because the updates are bad or because the update has been pushed
to stable.

Since I have a local mirror and the packages disappear between syncs, I end
up downloading them twice.

FESCo wants a more sane updates policy (feedback requested)

Hello,

I have seen the long thread about Updates Policy. I just wish
to inform you that I (as part of the QA team) have been working
on a draft of exactly such a policy. I suppose I will be able
to make it public during this week. I will post a link here,
so all the people will have some basis what to discuss.

The timing of this discussion is quite interesting, because
otherwise the whole discussion would be around my proposal
about a week later.

F-13 Branched report: 20100301 changes

Compose started at Mon Mar 1 09:15:14 UTC 2010

Broken deps for i386

[OFF TOPIC] Brazil may be punished due to government support to Open Software

This is off topic, but important to open software developers & supporters

Brazil may be punished because government supports free software...

IIPA is willing to put Brazil in the black list of copyrights because
Federal & State governments support free software. According to IIPA, by
supporting free software it shows Brazil has an inadequate policy
against violations on intellectual property.

IIPA... & its gangster supporters must be denounced now.

perl-Nmap-Parser license changed from GPLv2+ to MIT

Whilst cleaning up some recently adopted orphans, I discovered that
perl-Nmap-Parser has been tagged with the wrong license since August
2008. Upstream changed the license from GPLv2+ to MIT sometime back in
2007 and I've just corrected it in rawhide (and will do on all
branches too in the near future). Presumably this isn't a problem for
anyone since it's less restrictive now.

Directory ownership bugs

Hi, could these bug messages be a little more specific? I believe I've
fixed this issue [1] (filled originally as [2]) already, but from [1] it
isn't clear what version of the package was tested -- the supposedly
fixed one or some previous version?

Thanks,
Martin

References:
[1] https://bugzilla.redhat.com/show_bug.cgi?id=569387
[2] https://bugzilla.redhat.com/show_bug.cgi?id=534104

Syndicate content