From adam at batkin.net Mon Dec 1 07:29:16 2008 From: adam at batkin.net (Adam Batkin) Date: Mon, 01 Dec 2008 07:29:16 +0000 Subject: Planet Fedora Beat Message-ID: <4933924C.2010201@batkin.net> Hi, it looks like the Planet Fedora beat could use a little help. From what I can tell, a number of people have volunteered over the past few weeks, and maybe they still want to contribute too (I don't want to step on any toes). Since contributions are wiki-based, this is an ideal situation for collaborative writing. So, if there aren't any objections, I'd like to start contributing links/summaries to the Planet Fedora beat for this coming week (starting Monday December 1). Thanks, -Adam Batkin From mspevack at redhat.com Mon Dec 1 10:21:21 2008 From: mspevack at redhat.com (Max Spevack) Date: Mon, 1 Dec 2008 11:21:21 +0100 (CET) Subject: announcements done for nov 30/dec 1 Message-ID: Announcements beat w/ all the F10 stuff is complete. From sundaram at fedoraproject.org Mon Dec 1 10:50:59 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 01 Dec 2008 16:20:59 +0530 Subject: Planet Fedora Beat In-Reply-To: <4933924C.2010201@batkin.net> References: <4933924C.2010201@batkin.net> Message-ID: <4933C193.9030909@fedoraproject.org> Adam Batkin wrote: > Hi, > > it looks like the Planet Fedora beat could use a little help. From what > I can tell, a number of people have volunteered over the past few weeks, > and maybe they still want to contribute too (I don't want to step on any > toes). Since contributions are wiki-based, this is an ideal situation > for collaborative writing. > > So, if there aren't any objections, I'd like to start contributing > links/summaries to the Planet Fedora beat for this coming week (starting > Monday December 1). Please go ahead. More help is certainly welcome. Rahul From pcalarco at nd.edu Mon Dec 1 16:50:49 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 01 Dec 2008 11:50:49 -0500 Subject: Planet Fedora Beat In-Reply-To: <4933924C.2010201@batkin.net> References: <4933924C.2010201@batkin.net> Message-ID: <493415E9.5080103@nd.edu> Hi Adam -- Welcome, and thanks for volunteering! If you have any questions, please don't hesitate to ask! - pascal Adam Batkin wrote: > Hi, > > it looks like the Planet Fedora beat could use a little help. From what > I can tell, a number of people have volunteered over the past few weeks, > and maybe they still want to contribute too (I don't want to step on any > toes). Since contributions are wiki-based, this is an ideal situation > for collaborative writing. > > So, if there aren't any objections, I'd like to start contributing > links/summaries to the Planet Fedora beat for this coming week (starting > Monday December 1). > > Thanks, > > -Adam Batkin > > _______________________________________________ > Fedora-news-list mailing list > Fedora-news-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-news-list From oisinfeeley at imapmail.org Tue Dec 2 02:07:03 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 01 Dec 2008 21:07:03 -0500 Subject: FWN #154 Message-ID: <1228183623.15521.1287727273@webmail.messagingengine.com> Hi all, So I guess we're going for an early Tuesday release of #154 in order to help those of a N.American persuasion recover from their turkey hangovers? If you've got a beat nearly or partly done then please try and wrap it up for Tuesday! So far we have the following completed: Announcements, Artwork, Developments, SecurityAdvisories. Pascal, Huzaifa I will not be available for much time on Tuesday so hopefully the trivial editing I did will be enough of a contribution. Best wishes, -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From oisinfeeley at imapmail.org Tue Dec 2 15:53:13 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Tue, 02 Dec 2008 10:53:13 -0500 Subject: FWN #154 Message-ID: <1228233193.363.1287838139@webmail.messagingengine.com> = Fedora Weekly News Issue 154 = Welcome to Fedora Weekly News Issue 153 for the week ending November 30th, 2008. http://fedoraproject.org/wiki/FWN/Issue154 This week many of us enjoyed Thanksgiving turkey and we all enjoyed a full helping of Fedora 10 and were left stunned and satisfied. In Announcements the availability of third-party repositories and end-of-life of Fedora 8 are detailed. Developments catches up with "Power Management and Filesystem Parameters" and a promising initiative to bring the man pages up-to-date. Artwork passes on some kudos for the "Release Banner for the Website" and the demo of some awesome "Stickers". Don't forget to peruse the SecurityAdvisories! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [1] http://fedoraproject.org/wiki/NewsProject/Join CONTENTS #154 1.1 Announcements 1.1.1 Fedora 10 1.1.2 Other 1.2 Developments 1.2.1 Python Bump to 2.6 in Rawhide 1.2.2 Power Management and Filesystem Parameters 1.2.3 Strange Resolution Problems 1.2.4 Cron Confusion 1.2.5 Man Pages to be Mandatory and Upstreamed 1.3 Artwork 1.3.1 Stickers 1.3.2 Release Banner for the Website 1.3.3 The Download Page 1.4 Security Advisories 1.4.1 Fedora 10 Security Advisories 1.4.2 Fedora 9 Security Advisories 1.4.3 Fedora 8 Security Advisories == Announcements == In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack It was a pretty quiet week in Fedora-land. Nothing really happened, so I guess we can just move ahead to the next section of Fedora Weekly News. Wait, what? Oh, yeah... how silly of me! I guess there was that one small announcement, like the general availability of Fedora 10 on November 25. Fedora 10 Keeping with tradition, the Fedora Project Leader Paul Frields wrote[1] a thank you message to the Fedora community on the eve of the release. Also keeping with tradition, on the morning of the release, a "whimsical" announcement was sent[2] out on the morning of the release. Naturally, some of the third-party packagers of Fedora (RPM Fusion and ATrpms) made their repositories available for Fedora 10 on the release day also [3,4]. Chitlesh Goorah reminded[5] the community that the Spins SIG has released seven Fedora 10 respins, all of which can be downloaded from spins.fedoraproject.org. Finally, Red Hat's CEO Jim Whitehurst sent a congratulatory email to the Fedora community [6]. [1] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00013.html [2] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00015.html [3] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00014.html [4] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00016.html [5] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00022.html [6] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00019.html === Other === Fedora 8 will reach its end-of-life[7] on January 7th (07-01-2009), according[8] to Jon Stanley. [7] http://fedoraproject.org/wiki/LifeCycle [8] http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00021.html == Developments == In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley === Python Bump to 2.6 in Rawhide === The success of Fedora's dogged persistence in pursuing an "upstream all possible patches" methodology was anecdotally highlighted during a thread in which Ignacio Vazquez-Abrams warned that all Python packages in rawhide would soon be affected. An apology was made[1] by Ignacio for a dramatic subject-line ("It's all ASPLODY!), but he explained that "[w]ithin the next few days Python 2.6 will be imported into Rawhide. This means that EVERY single Python-based package in Rawhide will be broken, and that we'll need to slog our way through rebuilding it package by package." Ignacio suggested that the list of approximately seven hundred packages could be examined with a: repoquery --disablerepo=\* --enablerepo={development,rawhide} \ --whatrequires "python(abi)" | sort | less Ignacio expressed[2] willingness to trigger the rebuilds for some of the packages but "[...] there's no way I can get [700] done in a timely fashion." [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01809.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01813.html Ville Skytt? asked[3] "[i]f a package installs some *.py, *.pyc, *.pyo somewhere else than in versioned python dirs, and the source *.py is python 2.6 compatible, will the *.pyc and *.pyo compiled with 2.5 break with 2.6?" Ignacio confirmed[4] that such packages should not need to be recompiled as the API had not changed beween versions 2.5 and 2.6. [3] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01826.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01837.html Tom 'spot' Callaway suggested[5] using a separate Koji tag so that Ignacio could use a process similar to that which Tom had employed for the transition from PERL-5.8 to PERL-5.10. Jeremy Katz remembered[6] that such tagging had been used for past bumping of Python and suggested "It's good to at least get the stack up through yum and friends building and working before thrusting the new python upon everyone as otherwise it's quite difficult for people to even try to fix things on their own." A list of the essential packages was made[7] by Seth Vidal and Konstantin Ryabitsev. [5] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01823.html [6] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01815.html [7] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01820.html On the foot of some skeptical questions from Les Mikesell Tom reported[8] that the end result of following such a process for PERL was that "[Fedora is] closer to perl upstream than we've ever been, and we have most of the long-standing perl bugs resolved (and we fixed the "RHEL slow perl" bug without even being aware of it as a byproduct of the methodology). The fact that you just noticed it means that we must have done some things properly, you're welcome. :)" [8] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01839.html On 28-11-2008 Ignacio reported[9] that "[...] we're going to go ahead and commit 2.6 to Rawhide and start the rebuild of all Python packages in Rawhide. So please keep your hands off any packages that require python(abi) until we're done. Or if you like, you can help out by bumping the release and building against the dist-f11-python tag." He later explained[10] that python-2.6 would appear in rawhide "[...] within 10 days if all goes well. Then releng will need to fold the tag back into f11-dist" and confirmed[11] that the version in Fedora 11 will be Python-2.6. [9] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02126.html [10] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02130.html [11] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02136.html On 30-11-2008 Ignacio posted[12] the results of the "first cycle of rebuilds" and categorized the failures into several convenient classes. On 01-12- 2008 Ignacio posted the results of round two which he explained[13][14] were "a set of packages that a different net caught. I used python(abi)=2.5 for the first set in order to get the low-level packages, and this one uses libpython2.5.so.1.0." The latest follow-up, on 01-12-2008 consisted[15] of the list of packages which "[...] contain compiled Python code but do not have a Requires of python(abi). Please note that this is a packaging bug as the bytecode is specific to the version of the Python it was compiled with. Whether this is a problem with rpm's macros or with the package itself must be dealt with on a case-by-case basis." [12] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02201.html [13] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00014.html [14] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00028.html [15] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00041.html === Power Management and Filesystem Parameters === A series of three disk-power management proposals were published[1] as an RFC by Matthew Garrett. They were generally well-received and discussion was mostly focused on ways to instrument the kernel to measure any resulting changes and to ensure that disk lifetimes are monitored carefully. [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02047.html The first, least controversial, proposal is to get Ingo Molnar's relatime patch upstream. An extensive discussion in LWN[2] explains that this allows applications to keep track of when files have been read without having to constantly update the last file access time, thus reducing the number of writes to the disk. [2] http://www.lwn.net/Articles/244829/ Matthew's second proposal was to "[...] increase the value of dirty_writeback_centisecs. This will result in dirty data spending more time in memory before being pushed out to disk. This is probably more controversial. The effect of this is that a power interruption will potentially result in more data being lost." The third proposal was to enable laptop-mode[3] by default in order to mitigate the second change. [3] cat /usr/share/doc/kernel-doc-2.6.27.5/Documentation/laptops/laptop-mode.txt EricSandeen was interested[4] in how Matthew would measure the effects on power and performance, whether it was possible to identify individual applications causing disk accesses, and whether disk spin-down should be considered. When Matthew replied[5] that it would be difficult to monitor disk access without causing further disk access David Woodhouse suggested using blktrace and this was eagerly recognized[6] by Matthew as exactly what he needed. [4] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02048.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02052.html [6] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02093.html Eric's spin-down suggestion was confirmed: "Yes, the long-term plan involves allowing drive spindown. I'm hoping to do this adaptively to let us avoid the spinup/down tendancies a static timeout provides, but you're right that monitoring SMART information would be a pretty important part of that. I lean towards offering it on desktops and servers, but not enabled by default." Phil Knirsch posted[7] that he was working on similar ideas currently including "the idea if a combination of a monitoring backend and a tuning engine could provide an automatic adoption of the system to the current use. E.g. during daytime when a user works with his machine we would typically see quite a few reads and write all the time. Drive spindowns or other power saving features could during that time be reduced so that the user will have the best performance. During the night (in case he didn't turn of the machine) only very few read and even fewer write operations should happen, at which time the disk could then be powered down most of the time. And of course this can be extended to not only disk drives but other tunable hardware components." [7] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02089.html Some of the pitfalls of choosing defaults for all users were exposed when Ralf Ertzinger and Phil disagreed[8] on the ideal behavior of logging mechanisms. Phil drew a distinction between system logging mechanisms and user application logs and argued that losing data from the latter was not as important. Dariusz Garbowski put[9] the point of view of "Joe the User": "He cares a lot that he lost last hour of his xchat (or whatever he uses) logs. He quite likely doesn't care about last hour of syslog messages (he may not even be aware they exist in the first place)..." [8] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02099.html [9] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02137.html See FWN#88[10],FWN#100[11][12] for previous discussion of power-management in Fedora. [10] https://fedoraproject.org/wiki/FWN/Issue88#PowerTOP_Release_Opens_Up_New_Directions_In_Power_Saving [11] http://fedoraproject.org/wiki/FWN/Issue100#Disabling_Atime [12] http://fedoraproject.org/wiki/FWN/Issue100#Reducing_Power_Usage_Of_Fedora === Strange Resolution Problems === A report of a strange name resolution problem was made[1] by Mark Bidewell. Yum failed to download the Adobe flash-plugin with an error: [Errno 4] IOError: Trying other mirror." , yet it was possible to download it directly over HTTP using the browser. [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02002.html Christian Iseli added[2] that he had a similar "[...] issue which seems to be due to some sort of DNS lookup problem. In my case I'd get the 'Name or service not known' for download1.rpmfusion.org." Christian's troubleshooting revealed that specific sites (linuxdownload.adobe.com and download1.rpmfusion.org) were consistently resolved with ping or firefox but failed with wget and ssh. Moreover: "Putting the IP addresses in /etc/hosts "works around" the problem[.]" [2] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02071.html Following some questions from Seth Vidal nothing seemed[3] obviously wrong and the mystery remains. [3] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02082.html === Cron Confusion === Pavel Alexeev asked[1] for guidance on how to correctly rpm package a cron job. The specific requirement was a cronjob that ran every twenty minutes and might thus use the /etc/cron.d directory provided by cronie ,the SELinux and PAM aware derivative of vixie cron. Pavel wondered how he could make a package which would work for both variants of cron. [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02179.html When Martin Langhoff confirmed that /etc/cron.d was necessary Pavel replied[2]: "[...] /etc/cron.d [is] provided only by cronie [and] now we have several other crons in the repositories[.]" He listed several other implementations of cron found by a # repoquery '*cron*' | egrep -v '^(yum-cron|PackageKit-cron|cronolog)' [2] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02182.html Ignacio Vazquez-Abrams corrected[3] him: "The only replacement for cronie in that list is fcron. Feel free to log a bug against it." Till Maas and Pavel noted[4], however, that the /etc/cron.* directories were also provided by the package named crontabs. [3] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02183.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02187.html Patrice Dumas posted[5] the welcome news that he was "[...] currently preparing a fcron sub-package that would be completly compatible with cronie and would watch /etc/cron.d (using inotifywait). I'll keep the list informed." [5] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02187.html === Man Pages to be Mandatory and Upstreamed === A vigorous thread flowered from the promising seed planted[1] by Michael Cronenworth in which he advocated getting rid of all current documentation: "Yes, what I'm about to describe should obsolete man, info, and all the other dozen "help" documentation found in all the Fedora packages." Michael proposed that a new, lightweight standard of some sort would solve the problem of missing documentation. [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02015.html During the course of the week there have been requests for "NetworkManager cli docs"[2] and "PulseAudio info needed"[3] in which the desired information has mostly been found on external web pages instead of in documentation supplied with the OS. [2] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01757.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02041.html Richard W. M. Jones suggested[4] instead that the Debian model should be followed: "Debian forces all programs to come with a man page. If one is missing, this is considered a bug and packagers have to write one." Patrice Dumas was[5] against compulsion and preferred leaving the choice to the packager. [4] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02023.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02025.html The idea of upstreaming the man pages was introduced[6] by Thorsten Leemhuis: "One reason for that: If you add man pages from debian to a fedora package then you have to recheck every now and then if the man pages are still up2date. That afaics often tends to be forgotten (I'm guilty myself here)." Richard agreed[7] and in the course of several clarifications made the strong point that "[...] it's a really useful feature of Debian that _any_ command, any many configuration files and other files, are documented using 'man'. I find it a big negative against Fedora that things aren't so consistently documented." [6] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02024.html [7] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02050.html There seemed to be little disagreement on the desirability of providing more information but Michael was not impressed[8] with Trond Danielsen's suggestion that yelp would fulfill his requirements: "[...] it lacks in the lightweight department. It eats 40 megs of RAM upon startup and more RAM once searching occurs or pages are opened. Sure, we're all getting gigabytes of RAM these days, but it's a HELP tool with TEXT." Basil Mohamed Gohar was inspired[9] to "[write] or two man pages, because I've run into the missing-man-page problem too often." He suggested a very reasonable sounding action plan for identifying missing man pages and then filling them in with at least stubs in order to form a SIG which would work on providing quality replacements. Gergely Buday also seemed[10] interested. [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00004.html [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00023.html [10] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00060.html == Artwork == In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei === Stickers === In a message posted[1] to both @fedora-art and @fedora-marketing, M?ir?n Duffy showed the community a demo of a sticker sheet "I've been through a few rounds with the printing company to correct various issues and I just received a digital proof from them that I'm pretty happy with" and asking for feedback "Does this look good? If you see any errors or issues let me know and I'll have them fixed, otherwise I'd like to send to send them myapproval ASAP." [1] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00100.html Gerold Kassube asked[2] about the empty stickers "with some I miss the content to fedora and I ask myself: If somebody sees that freedom boble, does he realize that it's fedora or is it only for insider?!" and proposed an alternate slogan "In my head I have a big idea for a sticker which could also be a good marketing which I want to share with you and your outstanding ideas in the past (and I'm also sure in the future). I like the phrase 'Fedora! Leaders not fellows'". In reply, Paul Frields pointed[3] the possibility to combine the stickers "Well, the nice thing about these stickers is they're *extremely* inexpensive. So we can hand out a sheet or two per person, and people can paste *both* a freedom bubble and the logo together!" and stressed the importance of a single, consistent, marketing message "I think it's important for us not to develop too many 'official' slogans, because it dilutes our message. 'What is Fedora? 4 Foundations? IFV? Leaders?'" [2] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00101.html [3] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00103.html === Release Banner for the Website === In a last check before the release day, Ricky Zhou from the website team asked[1] about the status of the graphics to be used on the website "Just to make sure everything will be ready for Tuesday, will we have a final version ready for adding to the site by some time on Monday?" and quickly Paolo Leoni replied[2] with an upload of the needed images and a minor modification[3] from Nicu Buculei. Jaroslav Reznik added[4] a KDE specific flavour it it (the banner contains screenshots of the desktop). [1] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00107.html [2] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00108.html [3] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00116.html [4] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00140.html === The Download Page === In a post to @fedora-art Seth Kenlon expressed[1] his delight with the design of the download page[2] "I don't know who takes care of this stuff, but I was really really impressed with the new/updated download page for fedora 10. The buttons on the right side of the page are brilliant -- "KDE Fans Click Here" and "Need PowerPC? Click here" -- now sure, I'm biased, because those two versions of Fedora happen to be the two that I use :^) but......objectively speaking, that is user friendly and attractive. Great job, who ever did that!" The page was designed, as Ricky Zhou pointed[3] by M?ir?n Duffy "Not surprisingly, this was the work of M?ir?n - thanks a lot for making that page beautiful and easy to use!" [1] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00145.html [2] http://fedoraproject.org/en/get-fedora [3] https://www.redhat.com/archives/fedora-art-list/2008-November/msg00147.html == Security Advisories == In this section, we cover Security Advisories from fedora-package-announce. https://www.redhat.com/mailman/listinfo/fedora-package-announce Contributing Writer: David Nalley === Fedora 10 Security Advisories === * nagios-3.0.5-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00881.html * imlib2-1.4.2-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00906.html * php-Smarty-2.6.20-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00940.html * net-snmp-5.4.2.1-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-November/msg01002.html === Fedora 9 Security Advisories === * imlib2-1.4.2-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00856.html === Fedora 8 Security Advisories === * imlib2-1.4.2-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00858.html ==== Fedora 8 is nearing EOL ==== Per FESCo support for Fedora 8 will be discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From oisinfeeley at imapmail.org Tue Dec 2 16:08:03 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Tue, 02 Dec 2008 11:08:03 -0500 Subject: Translation Beat sabbatical In-Reply-To: <4930D704.4040408@fedoraproject.org> References: <4930D704.4040408@fedoraproject.org> Message-ID: <1228234083.3966.1287841361@webmail.messagingengine.com> On Sat, 29 Nov 2008 11:15:40 +0530, "Runa Bhattacharjee" said: > Hi, > Apologies for the very late notice. This week I won't be able to cover > the Translation Beat as I am > travelling and would be afk. I hope to resume next week if travel plans > are not disturbed. Thanks for the notice Runa I hope you have a good trip. Best wishes, -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From stickster at gmail.com Tue Dec 2 16:11:41 2008 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 2 Dec 2008 11:11:41 -0500 Subject: FWN #154 In-Reply-To: <1228233193.363.1287838139@webmail.messagingengine.com> References: <1228233193.363.1287838139@webmail.messagingengine.com> Message-ID: <20081202161141.GP8620@localhost.localdomain> On Tue, Dec 02, 2008 at 10:53:13AM -0500, Oisin Feeley wrote: > = Fedora Weekly News Issue 154 = Thanks for pulling FWN together as always, folks! I passed this on to the internal Red Hat staff too. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From runab at fedoraproject.org Mon Dec 8 05:35:00 2008 From: runab at fedoraproject.org (Runa Bhattacharjee) Date: Mon, 08 Dec 2008 11:05:00 +0530 Subject: Translation Beat sabbatical In-Reply-To: <1228234083.3966.1287841361@webmail.messagingengine.com> References: <4930D704.4040408@fedoraproject.org> <1228234083.3966.1287841361@webmail.messagingengine.com> Message-ID: <493CB204.80701@fedoraproject.org> Oisin Feeley wrote: > > Thanks for the notice Runa I hope you have a good trip. > Thanks Oisin, it was good. :-) Translation beat is now done for FWN #155. regards Runa From oisinfeeley at imapmail.org Mon Dec 8 17:54:10 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 08 Dec 2008 12:54:10 -0500 Subject: Fedora Weekly News #155 Message-ID: <1228758850.8801.1288917291@webmail.messagingengine.com> Fedora Weekly News Issue 155 Welcome to Fedora Weekly News Issue 155 for the week ending December 7th, 2008. http://fedoraproject.org/wiki/FWN/Issue155 FWN is pleased to announce the return of the Planet Fedora beat. Among other items Adam Batkin lists some "Howtos and Tips" gleaned from blogs. In Announcements the "Fedora 11" naming scheme is discussed. In Developments "The PATH to CAPP" exposes disquiet with some security infrastructure. Translation provides updates on the cancellation of FLSCo elections. Artwork is again bursting at the seems with a "T-Shirt Logo Design Tool" and "Improved Document Templates". SecurityAdvisories lists this week's essential updates. Finally Virtualization continues to race the shocking pace of developments including the "Release of libvirt 0.5.0 and 0.5.1" There's plenty more a mere mouse click away! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [0] http://fedoraproject.org/en/get-fedora [1] http://fedoraproject.org/wiki/NewsProject/Join Fedora Weekly News Issue 155 1.1 Announcements 1.1.1 FUDCon Boston (F11) 1.1.2 Fedora 11 1.1.3 Other 1.2 Planet Fedora 1.2.1 General 1.2.2 How-To and Tips 1.2.3 FOSS.IN 1.3 Developments 1.3.1 The PATH to CAPP Audits 1.3.2 The Looming Py3K Monster 1.3.3 PackageKit Stealth Installations 1.3.4 DNS Resolution Unreliable 1.4 Translation 1.4.1 FLSco Elections Cancelled 1.4.2 Fedora-website Translation Repo Re-enabled 1.4.3 Transifex version updated for translate.fedoraproject.org 1.4.4 New Members in FLP 1.5 Artwork 1.5.1 Improved Document Templates 1.5.2 Postprocessing in Icons 1.5.3 FirstAidKit Artwork 1.5.4 T-Shirt Logo Design Tool 1.6 Security Advisories 1.6.1 Fedora 10 Security Advisories 1.6.2 Fedora 9 Security Advisories 1.6.3 Fedora 8 Security Advisories 1.7 Virtualization 1.7.1 Enterprise Management Tools List 1.7.1.1 Enabling Builds of libvirt for Windows 1.7.1.2 Solaris Support in virtinst 1.7.2 Fedora Xen List 1.7.2.1 Support for Fedora 10 DomU on F8 Dom0 1.7.2.2 Paravirt Ops Dom0 Feature Update 1.7.3 Libvirt List 1.7.3.1 Release of libvirt 0.5.0 and 0.5.1 1.7.3.2 Allow Automatic Driver Probe for Remote TCP Connections 1.7.3.3 Thread Safety for libvirtd Daemon and Drivers 1.7.3.4 libvirt 0.5.0 and KVM Migration Support 1.7.4 oVirt Devel List 1.7.4.1 Some Architecture Diagrams 1.7.4.2 Standalone Console Viewer for oVirt == Announcements == In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack === FUDCon Boston (F11) === Paul Frields made a few announcements this week regarding FUDCon Boston[1], which is January 9-11. Paul mentioned[2] that the event will be held at MIT, he gives information about the social event, and also reminds people to register on the wiki and to make their hotel reservations before December 19th, in order to secure the $99 hotel room rate. [1] http://fedoraproject.org/wiki/FUDCon/FUDConF11 [2] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00000.html === Fedora 11 === Josh Boyer wrote[3] about the process for selecting the Fedora 11 name. "We're doing the name collection differently this year than in the past. Contributors wishing to make a suggestion are asked to go to the F11 naming wiki page[4], and add an entry to the suggestion table found there". [3] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00001.html [4] https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_11 Jon Stanley announced[5,6] the Fedora 11 freeze dates. The Alpha freeze is currently scheduled for January 20, and the Final freeze for April 14. [5] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00005.html [6] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00006.html Ignacio Vazquez-Abrams announced[7] that Python 2.6 is now in Rawhide. For those of you who maintain Python packages, you'll want to read the full announcement. [7] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00007.html Other Finally, Paul Frields announced[8] that Chris Aillon has been re-appointed to the Fedora Board, and will serve another two-release term. [8] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00005.html == Planet Fedora == In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin === General === Fabian Affolter posted[0] a nice graph showing the number of unique fedoraproject.org visitors (progressively growing since 2006!) [0] http://fabaff.blogspot.com/2008/12/fedoraprojectorg-unique-visitors.html Karsten Wade appealed[1] for information about configuring a misbehaving Synaptic touchpad on Fedora 10, followed[2] shortly thereafter by a solution. [1] http://iquaid.org/2008/11/30/synaptic-tapping-fail-is-there-a-good-fix/ [2] http://iquaid.org/2008/12/02/more-than-one-way-to-skin-a-touchpad/ Max Spevack wondered[3] whether there is a nice way to build a custom Fedora mirror tailored specifically to one's installed package set. [3] http://spevack.livejournal.com/69145.html Thorsten Leemhuis critiqued[4] the Fedora Release Notes, providing some suggestions for how to make the important bits stand out more. [4] http://thorstenl.blogspot.com/2008/12/read-same-paragraphs-every-half-year.html A look ahead[5] at some of the innovations in the open source world that we can look forward to during 2009 [5] http://liquidat.wordpress.com/2008/12/01/the-open-source-year-2009/ Luis Villa mused[6][7] on innovation in general and the Linux Desktop (think Gnome and KDE) in particular. [6] http://tieguy.org/blog/2008/12/05/the-linux-desktops-change-problem/ [7] http://tieguy.org/blog/2008/12/06/slight-innovation-followup/ Greg DeKoenigsberg wrote a few[8] posts[9] chronicling[10] his experiences with Sugar [8] http://gregdek.livejournal.com/40932.html [9] http://gregdek.livejournal.com/41431.html [10] http://gregdek.livejournal.com/41616.html Apparently Luis Villa had[11] a similar idea [11] http://tieguy.org/blog/2008/12/02/playing-with-sugar/ A video interview[12] with Paul W. Frields about the Fedora 10 release [12] http://www.redhatmagazine.com/2008/12/02/video-fedora-10/ === How-To and Tips === Tom Tromey wrote an 8-part (so far) series[13] on using a Python-enabled GDB. The series is not just about debugging Python with GDB, but also extending GDB using Python. [13] http://tromey.com/blog/?p=494 Jeroen van Meeuwen provided some instructions for composing EL5 media on Fedora 9 or 10 systems[14] by running Revisor inside mock [14] http://kanarip.livejournal.com/6276.html James Laska wrote a tutorial on how to automate a classroom/lab-type[15] setup using tools such as Cobbler, Snake and Koan [15] http://jlaska.livejournal.com/3696.html Michael Stahnke had some problems (and solutions)[16] for getting Fedora 10 running as a Xen guest on EL5 [16] http://www.stahnkage.com/blogs/index.php?/archives/482-F10-and-Xen-images.html Dale Bewley wrote about expanding[17] an Encrypted Filesystem with LVM and Fedora 10 [17] http://tofu.org/drupal/node/71 Steven Moix managed to get[18] iTunes music sharing working in Fedora 10 [18] http://www.alphatek.info/2008/12/01/itunes-music-sharing-in-fedora-10/ Dave Jones had some tips[19] for making an ASUS Eee PC 900 (or any generally underpowered UMPC with a solid state disk) happier under Linux [19] http://kernelslacker.livejournal.com/132087.html Harald Hoyer also provided some performance advice[20], this time to help identify disk IO bottlenecks during bootup using SystemTap [20] http://www.harald-hoyer.de/personal/blog/fedora-10-disk-io === FOSS.IN === A number of people wrote up their experiences and provided pictures from FOSS.IN: [21] http://james-morris.livejournal.com/36445.html [22] http://james-morris.livejournal.com/36715.html [23] http://soumya.dgplug.org/?p=33 [24] http://kushaldas.in/2008/12/02/through-my-lenses-fossin-2008/ [25] http://rahulpmb.blogspot.com/2008/12/pics-from-fossin.html [26] http://www.tuxmaniac.com/blog/2008/12/07/fossin-2008-lots-of-fun/ == Developments == In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley === The PATH to CAPP Audits === Some tough questioning about the purpose and usefulness of the Common Criteria for Information Technology Security Evaluation (CC)[1] was dished out to the maintainers of shadow-utils (the family of secure utilities for manipulating user accounts and passwords) when it appeared that the need to audit specific behaviors was causing some awkward constraints in OS design. The CC certifications are an ISO standard originally developed by the USA's National Security Agency to specify the expected behavior of systems under certain strictly defined criteria (so called Protection Profiles) to certain levels (Enterprise Evaluation Levels). Red Hat Enterprise Linux (a downstream derivative of Fedora) is able to boast several of them, including CAPP,LSPP and RBACPP to EAL4+[2], enabling RHEL5 to be purchased for use in government programs which require "assured information sharing." See[3][4] for further information. In order to provide the auditing capabilities mandatory to achieve such certifications Steve Grubb and others on his team have been steadily committing changes to Fedora. The specific protection profile under discussion in this case was the Controlled Access Protection Profile (CAPP) and there has been a good deal of unease about the usefulness of such certification in other forums[5]. [1] http://en.wikipedia.org/wiki/Common.Criteria [2] http://www.redhat.com/solutions/government/commoncriteria/ [3] A good blog entry by Sun's Jim Laurent: http://blogs.sun.com/jimlaurent/entry/faq.what.is.a.common [4] https://www2.sans.org/reading.room/whitepapers/standards/1078.php [5] http://www.schneier.com/blog/archives/2005/12/microsoft.windo.html When Callum Lerwick noticed[6] that he could not run usermod as an unprivileged user in order to get its help page he suggested that "[...] it and all the other account tools have been changed to mode 750, inaccessible to normal users" and erroneously attributed this to recent changes made to accommodate changes to the PATH environment variable. Earlier discussion of the addition of the sbin directories to users' PATHs can be found in FWN#146[7]. Jon Stanley replied[8] "These permissions have been in place for over 2 years, with valid reasoning. Just because it's in your PATH doesn't mean you should be able to execute it." Jon appended the 2006 log message which attributed the change to "fix regression. Permissions on user* group* binaries should be 0750, because of CAPP/LSPP certification." Callum posted a list of all the account tools which had such permissions including the shadow-utils account tools and the audit subsystem tools. [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00489.html [7] http://fedoraproject.org/wiki/FWN/Issue146#PATH:.2Fsbin.Tab.Confusion [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00495.html Although the change was actually several years old it appeared to cause surprise in many circles and prompted demands for information on what CAPP was and whether it was of any use to the Fedora Project. Steve Grubb responded[9] to the original query that "[...] you cannot do anything with [the user* commands] unless you are root. Allowing anyone to execute them would require lots of bad things for our LSPP/CAPP evaluations" and suggested that man pages should be used instead of running the tools with the --help argument. [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00501.html Jesse Keating probed what appeared to be a reliance on restricting execution permissions for security. When Steve corrected[10] this to be "[...] more to do with the fact that we have to audit all attempts to modify trusted databases - in this case, shadow [...] if we open the permissions, we need to make these become setuid root so that we send audit events saying they failed" Jesse was even more perturbed[11] and asked "Why would the binary have to be suid? Why can't the binary detect that [the] calling user is not root, and just print out the usage and a message saying that you have to be root? How would this action make it any less auditable?" Later Chris Adams extended[12] the apparent logic: "[...] cat will have to be setuid root so it can audit? What about echo, bash, perl, etc.? This is absurd." [10] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00513.html [11] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00523.html [12] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00575.html >From this point onwards the confusion and questioning gained in volume and intensity with several points being made to question the usefulness of this particular (CAPP) certification. These included the points that any user could obtain copies of the restricted binaries from outside of the system[13] for nefarious testing purposes; and that there were plenty of other tools[14] on the system which might allow violations of the policy. [13] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00514.html [14] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00626.html It would be fair to characterize most of the reactions as hostile. Some of this was due to an apparent impatience with "security certifications" which seemed to be of more interest to managers than achieving practical security. Callum Lerwick suggested[15] "[...] just because RHEL has to do stupid ignorant shit to appease certification authorities doesn't mean Fedora has to do it too." Another part was undoubtedly due to concern about who had made the decision to follow this path. Jesse Keating expressed[16] some frustration and asked "Who's 'we'? Perhaps 'we' shouldn't piss on Fedora in order to meet some cert that I highly highly doubt any Fedora install will find useful." When Seth Vidal and Dominik Mierzejewski also wondered when, and by whom, the decision was made Steve answered[17]: "By me after a group presented the options back in 2005. Back in those days shadow-utils was in 'Core' and that was maintained by Red Hat." [15] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00528.html [16] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00534.html [17] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00584.html Another part of the hostility seemed to originate in the novelty of the certification requirements to many participants. Steve answered many queries as they came in and suggested that it was necessary to take an overview of how the whole process worked. He was pressed by Jeff Spaleta for further details. This led[18] to an interesting quote from the CAPP guidelines and the example of how they are applied to shadow-utils. The guidelines make some assumptions which many will find unrealistic, such as the "[t]he system administrative personnel are not careless, willfully negligent, or hostile, and will follow and abide by the instructions provided by the administrator documentation." While this criticism obviously calls into question the practical usefulness of the CAPP certification it is just one layer designed to perform a specific function, other more apparently useful security can only be built on top of these layers after they are implemented. Steve's post also contained some interesting practical examples of how administrators can use the audit tools to view information gained by instrumenting the shadow-utils code. To see who has modified accounts, and how, one can: #ausearch --start this-month -m ADD_USER #ausearch --start this-month -m ADD_GROUP A view of attempts to change accounts both through the approved shadow-utils (restricted to root) or other non-approved tools can be obtained with a ausearch --start this-month -f /etc/shadow *raw -- aureport -x -i [18] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00585.html Enrico Scholz pointed out[19] that this seemed like security through obscurity because there were other tools (vipw and ldapadd) which could modify the trusted database and Steve responded[20] that vipw was forbidden and that it would be possible to extend the auditing to ldap if someone had the time. In response to Andrew Bartlett Jesse Keating interpreted[21] this "forbidden" as "`forbidden by policy' in which using anything /but/ the audit-able tools is `forbidden by policy'. If you're expecting everybody to follow policy, why not just set policy that says `don't hack this box'. That'll work right?" [19] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00587.html [20] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00588.html [21] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00623.html Callum Lerwick jumped[22] to what was for him the central point: "So I guess this is what all this really comes down to: Do we care about certification?" and asked whether the shadow-utils maintainer(s) would care to put the permissions to a FESCo vote. Steve affirmed[23] that certification was worthwhile with a detailed list of the positive side-effects of the certification process which include: man pages for each syscall, bug fixing and reporting, test suites, crypto work, virtualization with strong guarantees of VM separation and more. It was an impressive list which seemed to counter the dominant assumption that certification was merely another item to be ticked off on a bureaucrat's mindless list. Steve noted that "[a]s a result, Fedora is the ONLY community distribution that actually meets certification requirements. OpenSuse might be close for CAPP, but not LSPP/RSBAC, but that would be the only one I can think of that might be getting close." [22] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00560.html [23] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00563.html While this summary might make it seem as though certification is a slamdunk (and your correspondent has to admit a strong bias in favor of it) it has probably failed to convey the sense of unease expressed by Fedora Project contributors that decisions have been taken without discussion or consultation. Jesse Keating asked[24] Steve Grubb to explain who was providing impetus to the shadow-utils/certification team: "Where is this yelling going on? Where are the bug reports? Where is the public discussion about supposed problems in our install processes? Where is the discussion with domain knowledge experts debating whether or not the complaint has merit? Where is the open and frank discussion?" [24] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00547.html One possible route around what seems to be an impasse was suggested by Jeff Spaleta. Jeff observed[25] that CAPP certification for putative "appliance spins", but not the current set of spins, might make sense and asked[26]: "could some of the restrictions like the permissions be handled in a more modular way? Could for example, things be changed so I could install a specialized fedora-CAPP package at install time which tightens up aspects of the system to bring it into CAPP compliance, instead of expressing those restrictions in the default settings of all installs?" [25] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00556.html [26] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00625.html === The Looming Py3K Monster === Last week we reported that Ignacio Vazquez-Abrams was busy shepherding Python-2.6 into Fedora. This week Michael DeHaan raised[1] the question of what the plan for incorporating Python 3K will be. Michael worried that Py3K's incompatibilities with Python-2.6 "[are] pretty bad for someone who wants to keep a single codebase across EL 4 (Python 2.3) and up, which I think a lot of us do. That gets to be darn impossible and we have to double our involvement with code because we essentially have to maintain a differently-compatible fork for each project." He asked: "Are we looking at also carrying on with packaging 2.N indefinitely when we do decide to carry 3, because as I know it, the code changes to make something Python 3 compatible will be severe and that's a big item for any release, and will probably result in some undiscovered bugs even after the initial ports (if applied)." [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00379.html Although there was some optimism that the "from future import" syntax would allow the use of python-3 features in python-2 Daniel P. Berrange quashed[2] the idea that this was a simple fix because it "[...] isn't much help if python 2.3, 2.4 and 2.5 don't support 'from future import' and you care about shipping stuff that works on the 99% of deployed Linux boxes today which don't have 2.6 let alone 3.0." Basil Mohamed Gohar suggested[3] running the 2to3 tool on the Core packages to gain a sense of what needs to be done. [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00394.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00438.html Some strategies and their implications were detailed[4] by Toshio Kuratomi in a post which comprehensively explains the options. Toshio suggested avoiding maintaining separate python2 and python3 packages within a single version of Fedora due to the resulting double work and space. He suggested that "[...] this decision is only partially within the powers of the Fedora Project to decide. If 80% of our upstream libraries move to py3, we'll need to move to py3 sooner. If 80% refuse to move off of py2, we can take our time working on migration code." In later discussion with Arthur Pemberton he seemed[5] to favor the idea of using python-2.6 while ensuring that all code is as compatible as possible with python-3 and avoided estimating how hard this would be until actual experience is gained with "[...] porting code to 2.6 with 3.x features turned on at some point." [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00420.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00437.html James Antill was[6] skeptical that Py3K would be seen in Fedora any time soon due to the massive changes required and the past history (FWN#114[7])of votes on maintaining compatibility packages: "I'll put money on python3k not being the default in Fedora 12. Hell, I'll even put some money on it not being the default in Fedora 14, at this point. My personal opinion is that we stay with 2.6.* for as long as possible, giving everyone time to dual port and the problems to be found/fixed and then it "should be easy" to have it as a feature and move for one release. But I'll point out that Ignacio Vazquez-Abrams did .all. the work for 2.6 in Fedora 11 ... so feel free to take this as just my opinion." [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00391.html [7] http://fedoraproject.org/wiki/FWN/Issue114#Policy.Proposal.For.New.Compatibility.Packages === PackageKit Stealth Installations === Robert Locke asked[1] how createrepo, anaconda-yum-plugins and preupgrade had been installed without his permission on a fresh Fedora 10 install. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00431.html An answer was posted[2] by Jesse Keating to the effect that this had been done by PackageKit "[...] so that it could offer you the ability to upgrade. We've moved that information to a public webserver rather than being in the preupgrade package so that PK can get this information without stealth installing packages." He added that while there were no "[...] current guidelines that would have caught this [...] it does fall into the `don't do that' category." [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00448.html In further answers Jesse explained[3]: "It was installed so that PackageKit could have the appropriate information to check if there were distro level upgrades (say 9 to 10) available for you. The upstream has been asked to please not install any software in Fedora without a users consent, so hopefully this scenario won't happen again, at least not with PackageKit." [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00505.html === DNS Resolution Unreliable === Previously in FWN#154[1] we reported on some strange name resolution problems. Seth Vidal, as maintainer of the YUM package which looked as though it might be implicated, requested[2] follow-up information. [1] http://fedoraproject.org/wiki/FWN/Issue154#Strange.Resolution.Problems [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00246.html Tim Niemuller replied that the problems persisted for him and were probably not to do with YUM. He added failures with svn to the mix and suggested[3] that "[...] yum is [not] the problem but there is a more general problem related to DNS lookups. As a specialty I'm using nss-mdns. But on F-8/F-9 this has never been a problem, so I suspect this is not what is causing the problem, especially because others have the same problem and I don't think nss-mdns is installed on many machines." [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00305.html Jonathan Underwood posted[4] a link to a heavily commented bugzilla entry opened by Tom Horsley on 2008-08-21. The gist of the comments appears to be that with certain DNS servers there is a problem with simultaneous IPv4 and IPv6 requests being sent. A reported[5] work-around involved using a non-glibc resolver such as dnsmasq and was added[6] to the Fedora Project wiki by Christopher Stone. [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00308.html [5] http://www.fedorafaq.org/f10/#dns-slow [6] https://fedoraproject.org/wiki/Common.F10.bugs#DNS.Resolver.not.Reliable Jakub Jelinek prepared[7] a glibc update which temporarily disables the simultaneous requests and Ben Williams promised that once the issue is cleanly resolved the Fedora Unity team[8] will issue a Fedora 10 re-spin. [7] https://bugzilla.redhat.com/show.bug.cgi?id=459756#c91 [8] http://fedoraunity.org/ == Translation == This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee === FLSco Elections Cancelled === The mid-term elections for Fedora Localization Steering Committee (FLSCo) were cancelled and the Fedora Localization Project decided to go ahead with the current Committee for another release[1][2]. [1] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00011.html [2] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00018.html === Fedora-website Translation Repo Re-enabled === The main repository for the Fedora Website translation was re-enabled post Fedora 10 release and the intermediate test repository is now disabled[3]. As reiterated by RickyZhou, any updations to Fedora Website content are to be submitted to the main repository[4]. [3] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00003.html [4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00001.html === Transifex Version Updated for translate.fedoraproject.org === RickyZhou announced that the transifex version on translate.fedoraproject.org has been updated and very soon new features like translated interface and module descriptions would also be added[5]. [5] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00023.html === New Members in FLP === Nikolay Vladimirov[6] and Daniel Cabrera[7] are the two new members joining the Fedora Localization Project for the Bulgarian and Spanish team respectively. [6] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00004.html [7] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00024.html == Artwork == In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei === Improved Document Templates === M?ir?n Duffy proposed on @fedora-art a new project for Fedora 11 "finding and developing nice-looking, general-purpose templates we could then package up for programs like OpenOffice.org Writer, OpenOffice.org Impress, Scribus, Inkscape, Gimp, etc.", proposal received[2] with enthusiasm by Seth Kenlon, who also asked bout font requirements in those templates "does anyone know if there are special requirements in terms of fonts we could actually use and expect upstream to definitely have?", a question answered[3] quickly by M?ir?n "I think we should only assume users will have access to the fonts packaged for Fedora proper. If we use a font that isn't included in the default live media installation, then we should require the Fedora font package needed." [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00001.html [2] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00008.html [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00009.html === Postprocessing in Icons === MartinSourada raised[1] a technical debate on @fedora-art, questioning if the desktop icons should be always generated directly from the SVG sources or if some additional raster post-processing is allowed "My reason for this is that while I am unable to achieve, to my eye, perfect antialiasing in some cases when using direct export in inkscape, but after exporting it in bigger size applying some filters and resizing to desired size I am able to achieve, to my eye, better results", a question still under debate, awaiting input for contributors with more experience in icon creation. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00005.html === FirstAidKit Artwork === Maria Leandro resumed[1] the work on an older DesignService request[2] "I made some tries and finally came up something he like" a graphic received with only a small concern[3] from Mike Langlie "The Red Cross owns the trademark to the red cross icon/logo. They have sent cease and desist orders to game companies that use it as an icon for health re-ups. They do suggest using a green cross or white cross on a green background instead as a generic alternative", something easily addressed by Maria[4] [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00002.html [2] https://fedoraproject.org/wiki/Artwork/DesignService#Firstaidkit [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00003.html [4] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00004.html === T-Shirt Logo Design Tool === Following a chat on the IRC channel, Charles Brej followed[1] on @fedora-art with a small application which can be used to create T-shirt designs flom 'tag clouds': "I wrote a little tool to create these 'word splat' things with the idea of using the generated images as the Fudcon t-shirt designs". There is a strong possibility to see a number of graphics created during the upcoming year with this tool. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00026.html [2] http://www.cs.man.ac.uk/~brejc8/temp/try3.png == Security Advisories == In this section, we cover Security Advisories from fedora-package-announce. https://www.redhat.com/mailman/listinfo/fedora-package-announce Contributing Writer: David Nalley === Fedora 10 Security Advisories === * lynx-2.8.6-18.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00065.html * wordpress-2.6.5-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00083.html * samba-3.2.5-0.23.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00116.html * blender-2.48a-4.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00178.html * grip-3.2.0-24.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00183.html * dbus-1.2.6-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00209.html * squirrelmail-1.4.17-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00232.html * clamav-0.94.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00308.html * syslog-ng-2.0.10-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00397.html * java-1.6.0-openjdk-1.6.0.0-7.b12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00444.html === Fedora 9 Security Advisories === * wordpress-2.6.5-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00000.html * samba-3.2.5-0.22.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00021.html * lynx-2.8.6-17.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00066.html * squirrelmail-1.4.17-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00223.html * syslog-ng-2.0.10-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00237.html * java-1.6.0-openjdk-1.6.0.0-0.20.b09.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00384.html * dbus-1.2.6-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00436.html === Fedora 8 Security Advisories === Fedora 8 is nearing EOL Per FESCo support for Fedora 8 will be discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html * samba-3.0.33-0.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00141.html * lynx-2.8.6-12.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00143.html * wordpress-2.6.5-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00176.html * squirrelmail-1.4.17-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00449.html * syslog-ng-2.0.10-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00450.html == Virtualization == In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley === Enterprise Management Tools List === This section contains the discussion happening on the et-mgmt-tools list Enabling Builds of libvirt for Windows Richard W.M. Jones sought[1] help in enabling builds of Windows libvirt binaries under Fedora. "It seems like we should have the base MinGW (Windows cross-compiler) packages in Fedora 11 by the end of this week. This email is to document the additional packages we need to get approved, in order to get the cross-compiled libvirt and virt tools into (or buildable by) Fedora 11. If you want to help out, please start reviewing by following the Bugzilla links, and looking at the approved packaging guidelines[2]" [1] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00073.html [2] http://fedoraproject.org/wiki/Packaging/MinGW. ==== Solaris Support in virtinst ==== John Levon submitted several patches to improve Solaris support in image:Echo-package-16px.pngpython-virtinst including and not limited to the following: * Add an option for passing Solaris JumpStart information.[1] * Various utility functions[2]. * "Make 'solaris' a first-class OS type, and select USB tablet support for the appropriate variants."[3] * Add support for Solaris PV.[4] * Support for the vdisk format[5]. John explained "vdisk is basically " Sun's " tap implementation and disk management tool. [1] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00062.html [2] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00063.html [3] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00064.html [4] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00065.html [5] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00067.html === Fedora Xen List === This section contains the discussion happening on the fedora-xen list. ==== Support for Fedora 10 DomU on F8 Dom0 ==== The changes[1] made to the image:Echo-package-16px.pngkernel which obviated image:Echo-package-16px.pngkernel-xen caused image:Echo-package-16px.pngpython-virtinst to fail[2] during the creation of a Fedora 10 Xen guest on a Fedora 8 Xen host. Cole Robinson announced[3] a test build[4] which fixes this problem. Readers are encouraged to test the release and provide positive karma points in bodhi[5] to make the build an official update. [1] http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Adminstrators_Care_About.html#sn-Unified_kernel_image [2] RHBZ #458164 [3] http://www.redhat.com/archives/fedora-xen/2008-November/msg00036.html [4] http://koji.fedoraproject.org/koji/buildinfo?buildID=71125 [5] https://admin.fedoraproject.org/updates/F8/FEDORA-2008-10394 ==== Paravirt Ops Dom0 Feature Update ==== After some prompting[1] from Pasi K?rkk?inen the dom0 support feature page[2] was updated to better clarify where the work to bring dom0 support back to Fedora is being done, and to more accurately represent the current status. The patches[3] are being written by Jeremy Fitzhardinge and others at Citrix/XenSource are being submitted to the mainline kernel. Once accepted in the upstream kernel, efforts will resume within Fedora to make the changes necessary to support dom0. These efforts include[4] ensuring the hypervisor supports bzImage kernels. [1] http://www.redhat.com/archives/fedora-xen/2008-November/msg00021.html [2] http://fedoraproject.org/wiki/Features/XenPvopsDom0 [3] http://xenbits.xen.org/paravirt_ops/patches.hg/ [4] http://www.redhat.com/archives/fedora-xen/2008-November/msg00025.html === Libvirt List === This section contains the discussion happening on the libvir-list. ==== Release of libvirt 0.5.0 and 0.5.1 ==== Daniel Veillard announced[1][2] the releases of image:Echo-package-16px.pnglibvirt 0.5.0 and 0.5.1. "This is a long expected release, with a lot of new features, as a result the small version number is increased." Tarballs and signed RPMs available upstream[3] and in Bodhi[4]. "As stated there is a huge amount of new features and improvement in this release, as well as a lot of bug fixes, the list is quite long". See the post[1] for the full list including the numerous improvments, documentation updates, bug fixes, and cleanups omitted below. New features: * CPU and scheduler support for LXC (Dan Smith) * SDL display configuration (Daniel Berrange) * domain lifecycle event support for QEmu and Xen with python bindings (Ben Guthro and Daniel Berrange) * KVM/QEmu migration support (Rich Jones and Chris Lalancette) * User Mode Linux driver (Daniel Berrange) * API for node device enumeration using HAL and DeviceKit with python bindings (David Lively) "Thanks a lot to everybody who contributed to this release, it is really great to see new people providing significant patches, and the amount of feedback received on the list." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00387.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00148.html [3] ftp://libvirt.org/libvirt/ [4] https://admin.fedoraproject.org/updates/libvirt ==== Allow Automatic Driver Probe for Remote TCP Connections ==== Later described by the release of image:Echo-package-16px.pnglibvirt 0.5.1 as an improvement, Daniel P. Berrange posted[1] the patch to implement a more general method for connecting to remote[2] hypervisor drivers. "When connecting to a local libvirt you can let it automatically probe the hypervisor URI if you don't know it ahead of time. This doesn't work with remote URIs because you need to have something to put in the URI scheme before the hostname: * qemu+ssh://somehost/system * xen+tcp://somehost/system This is then translated into the URI: * qemu:///system * xen:/// ... This patch adds a 'remote' URI scheme, usable like this: * remote+ssh://somehost/ * remote+tcp://somehost/ ... This finally makes the Avahi[3] broadcasts useful - they only include info on the hostname + data transport (SSH, TCP, TLS), not the HV type. So letting us use auto-probing remotely is the missing link." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html [2] http://libvirt.org/remote.html [3] http://www.avahi.org ==== Thread Safety for libvirtd Daemon and Drivers ==== Daniel P. Berrange posted[1] a huge series of 28 patches which add "thread safety for the libvirtd daemon and drivers, and makes the daemon multi-threaded in processing RPC calls. This enables multiple clients to be processed in parallel, without blocking each other. It does not change the thread rules for the virConnectPtr object though, so each individual client is still serialized." ... "This touches a huge amount of code, so I'd like to get this all merged ASAP as it'll be really hard to keep it synced with ongoing changes." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00453.html [2] http://fedoraproject.org/wiki/FWN/Issue148#Experimental_Driver_Thread_Safety ==== libvirt 0.5.0 and KVM Migration Support ==== Micka?l Can?vet wondered[1] if image:Echo-package-16px.pngkvm guest migration was expected to be functional. "I just installed image:Echo-package-16px.pnglibvirt 0.5.0 on Debian Lenny with kvm 0.72 to try kvm migration support." Tests failed with "libvir: error : this function is not supported by the hypervisor: virDomainMigrate." Chris Lalancette confirmed[2] "Yes, it is supposed to work, but yes, you need a very, very new kvm. In particular, you need at least kvm-77, and it won't really work right until you get to kvm-79." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00025.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00027.html === oVirt Devel List === This section contains the discussion happening on the ovirt-devel list. ==== Some Architecture Diagrams ==== Daniel P. Berrange said[1] "I felt I wanted some additional more technically detailed/ focused diagrams to illustrate what we're doing to developers actually writing code for the project." And pointed to oVirt architecure diagrams he created.[2] [1] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00357.html [2] http://ovirt.org/page/ArchDiagrams ==== Standalone Console Viewer for oVirt ==== Continuing work on a executable console solution[1] for oVirt, with a fork of image:Echo-package-16px.pngvirt-viewer, Richard W.M. Jones created[2] ovirt-viewer. [1] https://fedoraproject.org/wiki/FWN/Issue151#oVirt_Console_Conundrum [2] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00412.html -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From oisinfeeley at imapmail.org Mon Dec 8 18:16:16 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 8 Dec 2008 19:16:16 +0100 Subject: Fedora Weekly News #155 Message-ID: <000e01c95961$0fc3cdc0$ba00000a@grecom.local> Fedora Weekly News Issue 155 Welcome to Fedora Weekly News Issue 155 for the week ending December 7th, 2008. http://fedoraproject.org/wiki/FWN/Issue155 FWN is pleased to announce the return of the Planet Fedora beat. Among other items Adam Batkin lists some "Howtos and Tips" gleaned from blogs. In Announcements the "Fedora 11" naming scheme is discussed. In Developments "The PATH to CAPP" exposes disquiet with some security infrastructure. Translation provides updates on the cancellation of FLSCo elections. Artwork is again bursting at the seems with a "T-Shirt Logo Design Tool" and "Improved Document Templates". SecurityAdvisories lists this week's essential updates. Finally Virtualization continues to race the shocking pace of developments including the "Release of libvirt 0.5.0 and 0.5.1" There's plenty more a mere mouse click away! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [0] http://fedoraproject.org/en/get-fedora [1] http://fedoraproject.org/wiki/NewsProject/Join Fedora Weekly News Issue 155 1.1 Announcements 1.1.1 FUDCon Boston (F11) 1.1.2 Fedora 11 1.1.3 Other 1.2 Planet Fedora 1.2.1 General 1.2.2 How-To and Tips 1.2.3 FOSS.IN 1.3 Developments 1.3.1 The PATH to CAPP Audits 1.3.2 The Looming Py3K Monster 1.3.3 PackageKit Stealth Installations 1.3.4 DNS Resolution Unreliable 1.4 Translation 1.4.1 FLSco Elections Cancelled 1.4.2 Fedora-website Translation Repo Re-enabled 1.4.3 Transifex version updated for translate.fedoraproject.org 1.4.4 New Members in FLP 1.5 Artwork 1.5.1 Improved Document Templates 1.5.2 Postprocessing in Icons 1.5.3 FirstAidKit Artwork 1.5.4 T-Shirt Logo Design Tool 1.6 Security Advisories 1.6.1 Fedora 10 Security Advisories 1.6.2 Fedora 9 Security Advisories 1.6.3 Fedora 8 Security Advisories 1.7 Virtualization 1.7.1 Enterprise Management Tools List 1.7.1.1 Enabling Builds of libvirt for Windows 1.7.1.2 Solaris Support in virtinst 1.7.2 Fedora Xen List 1.7.2.1 Support for Fedora 10 DomU on F8 Dom0 1.7.2.2 Paravirt Ops Dom0 Feature Update 1.7.3 Libvirt List 1.7.3.1 Release of libvirt 0.5.0 and 0.5.1 1.7.3.2 Allow Automatic Driver Probe for Remote TCP Connections 1.7.3.3 Thread Safety for libvirtd Daemon and Drivers 1.7.3.4 libvirt 0.5.0 and KVM Migration Support 1.7.4 oVirt Devel List 1.7.4.1 Some Architecture Diagrams 1.7.4.2 Standalone Console Viewer for oVirt == Announcements == In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack === FUDCon Boston (F11) === Paul Frields made a few announcements this week regarding FUDCon Boston[1], which is January 9-11. Paul mentioned[2] that the event will be held at MIT, he gives information about the social event, and also reminds people to register on the wiki and to make their hotel reservations before December 19th, in order to secure the $99 hotel room rate. [1] http://fedoraproject.org/wiki/FUDCon/FUDConF11 [2] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00000.html === Fedora 11 === Josh Boyer wrote[3] about the process for selecting the Fedora 11 name. "We're doing the name collection differently this year than in the past. Contributors wishing to make a suggestion are asked to go to the F11 naming wiki page[4], and add an entry to the suggestion table found there". [3] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00001.html [4] https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_11 Jon Stanley announced[5,6] the Fedora 11 freeze dates. The Alpha freeze is currently scheduled for January 20, and the Final freeze for April 14. [5] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00005.html [6] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00006.html Ignacio Vazquez-Abrams announced[7] that Python 2.6 is now in Rawhide. For those of you who maintain Python packages, you'll want to read the full announcement. [7] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00007.html Other Finally, Paul Frields announced[8] that Chris Aillon has been re-appointed to the Fedora Board, and will serve another two-release term. [8] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00005.html == Planet Fedora == In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin === General === Fabian Affolter posted[0] a nice graph showing the number of unique fedoraproject.org visitors (progressively growing since 2006!) [0] http://fabaff.blogspot.com/2008/12/fedoraprojectorg-unique-visitors.html Karsten Wade appealed[1] for information about configuring a misbehaving Synaptic touchpad on Fedora 10, followed[2] shortly thereafter by a solution. [1] http://iquaid.org/2008/11/30/synaptic-tapping-fail-is-there-a-good-fix/ [2] http://iquaid.org/2008/12/02/more-than-one-way-to-skin-a-touchpad/ Max Spevack wondered[3] whether there is a nice way to build a custom Fedora mirror tailored specifically to one's installed package set. [3] http://spevack.livejournal.com/69145.html Thorsten Leemhuis critiqued[4] the Fedora Release Notes, providing some suggestions for how to make the important bits stand out more. [4] http://thorstenl.blogspot.com/2008/12/read-same-paragraphs-every-half-year.html A look ahead[5] at some of the innovations in the open source world that we can look forward to during 2009 [5] http://liquidat.wordpress.com/2008/12/01/the-open-source-year-2009/ Luis Villa mused[6][7] on innovation in general and the Linux Desktop (think Gnome and KDE) in particular. [6] http://tieguy.org/blog/2008/12/05/the-linux-desktops-change-problem/ [7] http://tieguy.org/blog/2008/12/06/slight-innovation-followup/ Greg DeKoenigsberg wrote a few[8] posts[9] chronicling[10] his experiences with Sugar [8] http://gregdek.livejournal.com/40932.html [9] http://gregdek.livejournal.com/41431.html [10] http://gregdek.livejournal.com/41616.html Apparently Luis Villa had[11] a similar idea [11] http://tieguy.org/blog/2008/12/02/playing-with-sugar/ A video interview[12] with Paul W. Frields about the Fedora 10 release [12] http://www.redhatmagazine.com/2008/12/02/video-fedora-10/ === How-To and Tips === Tom Tromey wrote an 8-part (so far) series[13] on using a Python-enabled GDB. The series is not just about debugging Python with GDB, but also extending GDB using Python. [13] http://tromey.com/blog/?p=494 Jeroen van Meeuwen provided some instructions for composing EL5 media on Fedora 9 or 10 systems[14] by running Revisor inside mock [14] http://kanarip.livejournal.com/6276.html James Laska wrote a tutorial on how to automate a classroom/lab-type[15] setup using tools such as Cobbler, Snake and Koan [15] http://jlaska.livejournal.com/3696.html Michael Stahnke had some problems (and solutions)[16] for getting Fedora 10 running as a Xen guest on EL5 [16] http://www.stahnkage.com/blogs/index.php?/archives/482-F10-and-Xen-images.html Dale Bewley wrote about expanding[17] an Encrypted Filesystem with LVM and Fedora 10 [17] http://tofu.org/drupal/node/71 Steven Moix managed to get[18] iTunes music sharing working in Fedora 10 [18] http://www.alphatek.info/2008/12/01/itunes-music-sharing-in-fedora-10/ Dave Jones had some tips[19] for making an ASUS Eee PC 900 (or any generally underpowered UMPC with a solid state disk) happier under Linux [19] http://kernelslacker.livejournal.com/132087.html Harald Hoyer also provided some performance advice[20], this time to help identify disk IO bottlenecks during bootup using SystemTap [20] http://www.harald-hoyer.de/personal/blog/fedora-10-disk-io === FOSS.IN === A number of people wrote up their experiences and provided pictures from FOSS.IN: [21] http://james-morris.livejournal.com/36445.html [22] http://james-morris.livejournal.com/36715.html [23] http://soumya.dgplug.org/?p=33 [24] http://kushaldas.in/2008/12/02/through-my-lenses-fossin-2008/ [25] http://rahulpmb.blogspot.com/2008/12/pics-from-fossin.html [26] http://www.tuxmaniac.com/blog/2008/12/07/fossin-2008-lots-of-fun/ == Developments == In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley === The PATH to CAPP Audits === Some tough questioning about the purpose and usefulness of the Common Criteria for Information Technology Security Evaluation (CC)[1] was dished out to the maintainers of shadow-utils (the family of secure utilities for manipulating user accounts and passwords) when it appeared that the need to audit specific behaviors was causing some awkward constraints in OS design. The CC certifications are an ISO standard originally developed by the USA's National Security Agency to specify the expected behavior of systems under certain strictly defined criteria (so called Protection Profiles) to certain levels (Enterprise Evaluation Levels). Red Hat Enterprise Linux (a downstream derivative of Fedora) is able to boast several of them, including CAPP,LSPP and RBACPP to EAL4+[2], enabling RHEL5 to be purchased for use in government programs which require "assured information sharing." See[3][4] for further information. In order to provide the auditing capabilities mandatory to achieve such certifications Steve Grubb and others on his team have been steadily committing changes to Fedora. The specific protection profile under discussion in this case was the Controlled Access Protection Profile (CAPP) and there has been a good deal of unease about the usefulness of such certification in other forums[5]. [1] http://en.wikipedia.org/wiki/Common.Criteria [2] http://www.redhat.com/solutions/government/commoncriteria/ [3] A good blog entry by Sun's Jim Laurent: http://blogs.sun.com/jimlaurent/entry/faq.what.is.a.common [4] https://www2.sans.org/reading.room/whitepapers/standards/1078.php [5] http://www.schneier.com/blog/archives/2005/12/microsoft.windo.html When Callum Lerwick noticed[6] that he could not run usermod as an unprivileged user in order to get its help page he suggested that "[...] it and all the other account tools have been changed to mode 750, inaccessible to normal users" and erroneously attributed this to recent changes made to accommodate changes to the PATH environment variable. Earlier discussion of the addition of the sbin directories to users' PATHs can be found in FWN#146[7]. Jon Stanley replied[8] "These permissions have been in place for over 2 years, with valid reasoning. Just because it's in your PATH doesn't mean you should be able to execute it." Jon appended the 2006 log message which attributed the change to "fix regression. Permissions on user* group* binaries should be 0750, because of CAPP/LSPP certification." Callum posted a list of all the account tools which had such permissions including the shadow-utils account tools and the audit subsystem tools. [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00489.html [7] http://fedoraproject.org/wiki/FWN/Issue146#PATH:.2Fsbin.Tab.Confusion [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00495.html Although the change was actually several years old it appeared to cause surprise in many circles and prompted demands for information on what CAPP was and whether it was of any use to the Fedora Project. Steve Grubb responded[9] to the original query that "[...] you cannot do anything with [the user* commands] unless you are root. Allowing anyone to execute them would require lots of bad things for our LSPP/CAPP evaluations" and suggested that man pages should be used instead of running the tools with the --help argument. [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00501.html Jesse Keating probed what appeared to be a reliance on restricting execution permissions for security. When Steve corrected[10] this to be "[...] more to do with the fact that we have to audit all attempts to modify trusted databases - in this case, shadow [...] if we open the permissions, we need to make these become setuid root so that we send audit events saying they failed" Jesse was even more perturbed[11] and asked "Why would the binary have to be suid? Why can't the binary detect that [the] calling user is not root, and just print out the usage and a message saying that you have to be root? How would this action make it any less auditable?" Later Chris Adams extended[12] the apparent logic: "[...] cat will have to be setuid root so it can audit? What about echo, bash, perl, etc.? This is absurd." [10] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00513.html [11] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00523.html [12] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00575.html >From this point onwards the confusion and questioning gained in volume and intensity with several points being made to question the usefulness of this particular (CAPP) certification. These included the points that any user could obtain copies of the restricted binaries from outside of the system[13] for nefarious testing purposes; and that there were plenty of other tools[14] on the system which might allow violations of the policy. [13] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00514.html [14] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00626.html It would be fair to characterize most of the reactions as hostile. Some of this was due to an apparent impatience with "security certifications" which seemed to be of more interest to managers than achieving practical security. Callum Lerwick suggested[15] "[...] just because RHEL has to do stupid ignorant shit to appease certification authorities doesn't mean Fedora has to do it too." Another part was undoubtedly due to concern about who had made the decision to follow this path. Jesse Keating expressed[16] some frustration and asked "Who's 'we'? Perhaps 'we' shouldn't piss on Fedora in order to meet some cert that I highly highly doubt any Fedora install will find useful." When Seth Vidal and Dominik Mierzejewski also wondered when, and by whom, the decision was made Steve answered[17]: "By me after a group presented the options back in 2005. Back in those days shadow-utils was in 'Core' and that was maintained by Red Hat." [15] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00528.html [16] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00534.html [17] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00584.html Another part of the hostility seemed to originate in the novelty of the certification requirements to many participants. Steve answered many queries as they came in and suggested that it was necessary to take an overview of how the whole process worked. He was pressed by Jeff Spaleta for further details. This led[18] to an interesting quote from the CAPP guidelines and the example of how they are applied to shadow-utils. The guidelines make some assumptions which many will find unrealistic, such as the "[t]he system administrative personnel are not careless, willfully negligent, or hostile, and will follow and abide by the instructions provided by the administrator documentation." While this criticism obviously calls into question the practical usefulness of the CAPP certification it is just one layer designed to perform a specific function, other more apparently useful security can only be built on top of these layers after they are implemented. Steve's post also contained some interesting practical examples of how administrators can use the audit tools to view information gained by instrumenting the shadow-utils code. To see who has modified accounts, and how, one can: #ausearch --start this-month -m ADD_USER #ausearch --start this-month -m ADD_GROUP A view of attempts to change accounts both through the approved shadow-utils (restricted to root) or other non-approved tools can be obtained with a ausearch --start this-month -f /etc/shadow *raw -- aureport -x -i [18] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00585.html Enrico Scholz pointed out[19] that this seemed like security through obscurity because there were other tools (vipw and ldapadd) which could modify the trusted database and Steve responded[20] that vipw was forbidden and that it would be possible to extend the auditing to ldap if someone had the time. In response to Andrew Bartlett Jesse Keating interpreted[21] this "forbidden" as "`forbidden by policy' in which using anything /but/ the audit-able tools is `forbidden by policy'. If you're expecting everybody to follow policy, why not just set policy that says `don't hack this box'. That'll work right?" [19] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00587.html [20] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00588.html [21] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00623.html Callum Lerwick jumped[22] to what was for him the central point: "So I guess this is what all this really comes down to: Do we care about certification?" and asked whether the shadow-utils maintainer(s) would care to put the permissions to a FESCo vote. Steve affirmed[23] that certification was worthwhile with a detailed list of the positive side-effects of the certification process which include: man pages for each syscall, bug fixing and reporting, test suites, crypto work, virtualization with strong guarantees of VM separation and more. It was an impressive list which seemed to counter the dominant assumption that certification was merely another item to be ticked off on a bureaucrat's mindless list. Steve noted that "[a]s a result, Fedora is the ONLY community distribution that actually meets certification requirements. OpenSuse might be close for CAPP, but not LSPP/RSBAC, but that would be the only one I can think of that might be getting close." [22] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00560.html [23] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00563.html While this summary might make it seem as though certification is a slamdunk (and your correspondent has to admit a strong bias in favor of it) it has probably failed to convey the sense of unease expressed by Fedora Project contributors that decisions have been taken without discussion or consultation. Jesse Keating asked[24] Steve Grubb to explain who was providing impetus to the shadow-utils/certification team: "Where is this yelling going on? Where are the bug reports? Where is the public discussion about supposed problems in our install processes? Where is the discussion with domain knowledge experts debating whether or not the complaint has merit? Where is the open and frank discussion?" [24] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00547.html One possible route around what seems to be an impasse was suggested by Jeff Spaleta. Jeff observed[25] that CAPP certification for putative "appliance spins", but not the current set of spins, might make sense and asked[26]: "could some of the restrictions like the permissions be handled in a more modular way? Could for example, things be changed so I could install a specialized fedora-CAPP package at install time which tightens up aspects of the system to bring it into CAPP compliance, instead of expressing those restrictions in the default settings of all installs?" [25] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00556.html [26] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00625.html === The Looming Py3K Monster === Last week we reported that Ignacio Vazquez-Abrams was busy shepherding Python-2.6 into Fedora. This week Michael DeHaan raised[1] the question of what the plan for incorporating Python 3K will be. Michael worried that Py3K's incompatibilities with Python-2.6 "[are] pretty bad for someone who wants to keep a single codebase across EL 4 (Python 2.3) and up, which I think a lot of us do. That gets to be darn impossible and we have to double our involvement with code because we essentially have to maintain a differently-compatible fork for each project." He asked: "Are we looking at also carrying on with packaging 2.N indefinitely when we do decide to carry 3, because as I know it, the code changes to make something Python 3 compatible will be severe and that's a big item for any release, and will probably result in some undiscovered bugs even after the initial ports (if applied)." [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00379.html Although there was some optimism that the "from future import" syntax would allow the use of python-3 features in python-2 Daniel P. Berrange quashed[2] the idea that this was a simple fix because it "[...] isn't much help if python 2.3, 2.4 and 2.5 don't support 'from future import' and you care about shipping stuff that works on the 99% of deployed Linux boxes today which don't have 2.6 let alone 3.0." Basil Mohamed Gohar suggested[3] running the 2to3 tool on the Core packages to gain a sense of what needs to be done. [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00394.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00438.html Some strategies and their implications were detailed[4] by Toshio Kuratomi in a post which comprehensively explains the options. Toshio suggested avoiding maintaining separate python2 and python3 packages within a single version of Fedora due to the resulting double work and space. He suggested that "[...] this decision is only partially within the powers of the Fedora Project to decide. If 80% of our upstream libraries move to py3, we'll need to move to py3 sooner. If 80% refuse to move off of py2, we can take our time working on migration code." In later discussion with Arthur Pemberton he seemed[5] to favor the idea of using python-2.6 while ensuring that all code is as compatible as possible with python-3 and avoided estimating how hard this would be until actual experience is gained with "[...] porting code to 2.6 with 3.x features turned on at some point." [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00420.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00437.html James Antill was[6] skeptical that Py3K would be seen in Fedora any time soon due to the massive changes required and the past history (FWN#114[7])of votes on maintaining compatibility packages: "I'll put money on python3k not being the default in Fedora 12. Hell, I'll even put some money on it not being the default in Fedora 14, at this point. My personal opinion is that we stay with 2.6.* for as long as possible, giving everyone time to dual port and the problems to be found/fixed and then it "should be easy" to have it as a feature and move for one release. But I'll point out that Ignacio Vazquez-Abrams did .all. the work for 2.6 in Fedora 11 ... so feel free to take this as just my opinion." [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00391.html [7] http://fedoraproject.org/wiki/FWN/Issue114#Policy.Proposal.For.New.Compatibility.Packages === PackageKit Stealth Installations === Robert Locke asked[1] how createrepo, anaconda-yum-plugins and preupgrade had been installed without his permission on a fresh Fedora 10 install. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00431.html An answer was posted[2] by Jesse Keating to the effect that this had been done by PackageKit "[...] so that it could offer you the ability to upgrade. We've moved that information to a public webserver rather than being in the preupgrade package so that PK can get this information without stealth installing packages." He added that while there were no "[...] current guidelines that would have caught this [...] it does fall into the `don't do that' category." [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00448.html In further answers Jesse explained[3]: "It was installed so that PackageKit could have the appropriate information to check if there were distro level upgrades (say 9 to 10) available for you. The upstream has been asked to please not install any software in Fedora without a users consent, so hopefully this scenario won't happen again, at least not with PackageKit." [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00505.html === DNS Resolution Unreliable === Previously in FWN#154[1] we reported on some strange name resolution problems. Seth Vidal, as maintainer of the YUM package which looked as though it might be implicated, requested[2] follow-up information. [1] http://fedoraproject.org/wiki/FWN/Issue154#Strange.Resolution.Problems [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00246.html Tim Niemuller replied that the problems persisted for him and were probably not to do with YUM. He added failures with svn to the mix and suggested[3] that "[...] yum is [not] the problem but there is a more general problem related to DNS lookups. As a specialty I'm using nss-mdns. But on F-8/F-9 this has never been a problem, so I suspect this is not what is causing the problem, especially because others have the same problem and I don't think nss-mdns is installed on many machines." [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00305.html Jonathan Underwood posted[4] a link to a heavily commented bugzilla entry opened by Tom Horsley on 2008-08-21. The gist of the comments appears to be that with certain DNS servers there is a problem with simultaneous IPv4 and IPv6 requests being sent. A reported[5] work-around involved using a non-glibc resolver such as dnsmasq and was added[6] to the Fedora Project wiki by Christopher Stone. [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00308.html [5] http://www.fedorafaq.org/f10/#dns-slow [6] https://fedoraproject.org/wiki/Common.F10.bugs#DNS.Resolver.not.Reliable Jakub Jelinek prepared[7] a glibc update which temporarily disables the simultaneous requests and Ben Williams promised that once the issue is cleanly resolved the Fedora Unity team[8] will issue a Fedora 10 re-spin. [7] https://bugzilla.redhat.com/show.bug.cgi?id=459756#c91 [8] http://fedoraunity.org/ == Translation == This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee === FLSco Elections Cancelled === The mid-term elections for Fedora Localization Steering Committee (FLSCo) were cancelled and the Fedora Localization Project decided to go ahead with the current Committee for another release[1][2]. [1] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00011.html [2] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00018.html === Fedora-website Translation Repo Re-enabled === The main repository for the Fedora Website translation was re-enabled post Fedora 10 release and the intermediate test repository is now disabled[3]. As reiterated by RickyZhou, any updations to Fedora Website content are to be submitted to the main repository[4]. [3] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00003.html [4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00001.html === Transifex Version Updated for translate.fedoraproject.org === RickyZhou announced that the transifex version on translate.fedoraproject.org has been updated and very soon new features like translated interface and module descriptions would also be added[5]. [5] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00023.html === New Members in FLP === Nikolay Vladimirov[6] and Daniel Cabrera[7] are the two new members joining the Fedora Localization Project for the Bulgarian and Spanish team respectively. [6] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00004.html [7] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00024.html == Artwork == In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei === Improved Document Templates === M?ir?n Duffy proposed on @fedora-art a new project for Fedora 11 "finding and developing nice-looking, general-purpose templates we could then package up for programs like OpenOffice.org Writer, OpenOffice.org Impress, Scribus, Inkscape, Gimp, etc.", proposal received[2] with enthusiasm by Seth Kenlon, who also asked bout font requirements in those templates "does anyone know if there are special requirements in terms of fonts we could actually use and expect upstream to definitely have?", a question answered[3] quickly by M?ir?n "I think we should only assume users will have access to the fonts packaged for Fedora proper. If we use a font that isn't included in the default live media installation, then we should require the Fedora font package needed." [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00001.html [2] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00008.html [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00009.html === Postprocessing in Icons === MartinSourada raised[1] a technical debate on @fedora-art, questioning if the desktop icons should be always generated directly from the SVG sources or if some additional raster post-processing is allowed "My reason for this is that while I am unable to achieve, to my eye, perfect antialiasing in some cases when using direct export in inkscape, but after exporting it in bigger size applying some filters and resizing to desired size I am able to achieve, to my eye, better results", a question still under debate, awaiting input for contributors with more experience in icon creation. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00005.html === FirstAidKit Artwork === Maria Leandro resumed[1] the work on an older DesignService request[2] "I made some tries and finally came up something he like" a graphic received with only a small concern[3] from Mike Langlie "The Red Cross owns the trademark to the red cross icon/logo. They have sent cease and desist orders to game companies that use it as an icon for health re-ups. They do suggest using a green cross or white cross on a green background instead as a generic alternative", something easily addressed by Maria[4] [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00002.html [2] https://fedoraproject.org/wiki/Artwork/DesignService#Firstaidkit [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00003.html [4] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00004.html === T-Shirt Logo Design Tool === Following a chat on the IRC channel, Charles Brej followed[1] on @fedora-art with a small application which can be used to create T-shirt designs flom 'tag clouds': "I wrote a little tool to create these 'word splat' things with the idea of using the generated images as the Fudcon t-shirt designs". There is a strong possibility to see a number of graphics created during the upcoming year with this tool. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00026.html [2] http://www.cs.man.ac.uk/~brejc8/temp/try3.png == Security Advisories == In this section, we cover Security Advisories from fedora-package-announce. https://www.redhat.com/mailman/listinfo/fedora-package-announce Contributing Writer: David Nalley === Fedora 10 Security Advisories === * lynx-2.8.6-18.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00065.html * wordpress-2.6.5-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00083.html * samba-3.2.5-0.23.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00116.html * blender-2.48a-4.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00178.html * grip-3.2.0-24.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00183.html * dbus-1.2.6-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00209.html * squirrelmail-1.4.17-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00232.html * clamav-0.94.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00308.html * syslog-ng-2.0.10-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00397.html * java-1.6.0-openjdk-1.6.0.0-7.b12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00444.html === Fedora 9 Security Advisories === * wordpress-2.6.5-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00000.html * samba-3.2.5-0.22.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00021.html * lynx-2.8.6-17.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00066.html * squirrelmail-1.4.17-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00223.html * syslog-ng-2.0.10-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00237.html * java-1.6.0-openjdk-1.6.0.0-0.20.b09.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00384.html * dbus-1.2.6-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00436.html === Fedora 8 Security Advisories === Fedora 8 is nearing EOL Per FESCo support for Fedora 8 will be discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html * samba-3.0.33-0.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00141.html * lynx-2.8.6-12.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00143.html * wordpress-2.6.5-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00176.html * squirrelmail-1.4.17-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00449.html * syslog-ng-2.0.10-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00450.html == Virtualization == In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley === Enterprise Management Tools List === This section contains the discussion happening on the et-mgmt-tools list Enabling Builds of libvirt for Windows Richard W.M. Jones sought[1] help in enabling builds of Windows libvirt binaries under Fedora. "It seems like we should have the base MinGW (Windows cross-compiler) packages in Fedora 11 by the end of this week. This email is to document the additional packages we need to get approved, in order to get the cross-compiled libvirt and virt tools into (or buildable by) Fedora 11. If you want to help out, please start reviewing by following the Bugzilla links, and looking at the approved packaging guidelines[2]" [1] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00073.html [2] http://fedoraproject.org/wiki/Packaging/MinGW. ==== Solaris Support in virtinst ==== John Levon submitted several patches to improve Solaris support in image:Echo-package-16px.pngpython-virtinst including and not limited to the following: * Add an option for passing Solaris JumpStart information.[1] * Various utility functions[2]. * "Make 'solaris' a first-class OS type, and select USB tablet support for the appropriate variants."[3] * Add support for Solaris PV.[4] * Support for the vdisk format[5]. John explained "vdisk is basically " Sun's " tap implementation and disk management tool. [1] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00062.html [2] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00063.html [3] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00064.html [4] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00065.html [5] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00067.html === Fedora Xen List === This section contains the discussion happening on the fedora-xen list. ==== Support for Fedora 10 DomU on F8 Dom0 ==== The changes[1] made to the image:Echo-package-16px.pngkernel which obviated image:Echo-package-16px.pngkernel-xen caused image:Echo-package-16px.pngpython-virtinst to fail[2] during the creation of a Fedora 10 Xen guest on a Fedora 8 Xen host. Cole Robinson announced[3] a test build[4] which fixes this problem. Readers are encouraged to test the release and provide positive karma points in bodhi[5] to make the build an official update. [1] http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Adminstrators_Care_About.html#sn-Unified_kernel_image [2] RHBZ #458164 [3] http://www.redhat.com/archives/fedora-xen/2008-November/msg00036.html [4] http://koji.fedoraproject.org/koji/buildinfo?buildID=71125 [5] https://admin.fedoraproject.org/updates/F8/FEDORA-2008-10394 ==== Paravirt Ops Dom0 Feature Update ==== After some prompting[1] from Pasi K?rkk?inen the dom0 support feature page[2] was updated to better clarify where the work to bring dom0 support back to Fedora is being done, and to more accurately represent the current status. The patches[3] are being written by Jeremy Fitzhardinge and others at Citrix/XenSource are being submitted to the mainline kernel. Once accepted in the upstream kernel, efforts will resume within Fedora to make the changes necessary to support dom0. These efforts include[4] ensuring the hypervisor supports bzImage kernels. [1] http://www.redhat.com/archives/fedora-xen/2008-November/msg00021.html [2] http://fedoraproject.org/wiki/Features/XenPvopsDom0 [3] http://xenbits.xen.org/paravirt_ops/patches.hg/ [4] http://www.redhat.com/archives/fedora-xen/2008-November/msg00025.html === Libvirt List === This section contains the discussion happening on the libvir-list. ==== Release of libvirt 0.5.0 and 0.5.1 ==== Daniel Veillard announced[1][2] the releases of image:Echo-package-16px.pnglibvirt 0.5.0 and 0.5.1. "This is a long expected release, with a lot of new features, as a result the small version number is increased." Tarballs and signed RPMs available upstream[3] and in Bodhi[4]. "As stated there is a huge amount of new features and improvement in this release, as well as a lot of bug fixes, the list is quite long". See the post[1] for the full list including the numerous improvments, documentation updates, bug fixes, and cleanups omitted below. New features: * CPU and scheduler support for LXC (Dan Smith) * SDL display configuration (Daniel Berrange) * domain lifecycle event support for QEmu and Xen with python bindings (Ben Guthro and Daniel Berrange) * KVM/QEmu migration support (Rich Jones and Chris Lalancette) * User Mode Linux driver (Daniel Berrange) * API for node device enumeration using HAL and DeviceKit with python bindings (David Lively) "Thanks a lot to everybody who contributed to this release, it is really great to see new people providing significant patches, and the amount of feedback received on the list." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00387.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00148.html [3] ftp://libvirt.org/libvirt/ [4] https://admin.fedoraproject.org/updates/libvirt ==== Allow Automatic Driver Probe for Remote TCP Connections ==== Later described by the release of image:Echo-package-16px.pnglibvirt 0.5.1 as an improvement, Daniel P. Berrange posted[1] the patch to implement a more general method for connecting to remote[2] hypervisor drivers. "When connecting to a local libvirt you can let it automatically probe the hypervisor URI if you don't know it ahead of time. This doesn't work with remote URIs because you need to have something to put in the URI scheme before the hostname: * qemu+ssh://somehost/system * xen+tcp://somehost/system This is then translated into the URI: * qemu:///system * xen:/// ... This patch adds a 'remote' URI scheme, usable like this: * remote+ssh://somehost/ * remote+tcp://somehost/ ... This finally makes the Avahi[3] broadcasts useful - they only include info on the hostname + data transport (SSH, TCP, TLS), not the HV type. So letting us use auto-probing remotely is the missing link." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html [2] http://libvirt.org/remote.html [3] http://www.avahi.org ==== Thread Safety for libvirtd Daemon and Drivers ==== Daniel P. Berrange posted[1] a huge series of 28 patches which add "thread safety for the libvirtd daemon and drivers, and makes the daemon multi-threaded in processing RPC calls. This enables multiple clients to be processed in parallel, without blocking each other. It does not change the thread rules for the virConnectPtr object though, so each individual client is still serialized." ... "This touches a huge amount of code, so I'd like to get this all merged ASAP as it'll be really hard to keep it synced with ongoing changes." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00453.html [2] http://fedoraproject.org/wiki/FWN/Issue148#Experimental_Driver_Thread_Safety ==== libvirt 0.5.0 and KVM Migration Support ==== Micka?l Can?vet wondered[1] if image:Echo-package-16px.pngkvm guest migration was expected to be functional. "I just installed image:Echo-package-16px.pnglibvirt 0.5.0 on Debian Lenny with kvm 0.72 to try kvm migration support." Tests failed with "libvir: error : this function is not supported by the hypervisor: virDomainMigrate." Chris Lalancette confirmed[2] "Yes, it is supposed to work, but yes, you need a very, very new kvm. In particular, you need at least kvm-77, and it won't really work right until you get to kvm-79." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00025.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00027.html === oVirt Devel List === This section contains the discussion happening on the ovirt-devel list. ==== Some Architecture Diagrams ==== Daniel P. Berrange said[1] "I felt I wanted some additional more technically detailed/ focused diagrams to illustrate what we're doing to developers actually writing code for the project." And pointed to oVirt architecure diagrams he created.[2] [1] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00357.html [2] http://ovirt.org/page/ArchDiagrams ==== Standalone Console Viewer for oVirt ==== Continuing work on a executable console solution[1] for oVirt, with a fork of image:Echo-package-16px.pngvirt-viewer, Richard W.M. Jones created[2] ovirt-viewer. [1] https://fedoraproject.org/wiki/FWN/Issue151#oVirt_Console_Conundrum [2] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00412.html -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley -- fedora-announce-list mailing list fedora-announce-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-announce-list From oisinfeeley at imapmail.org Mon Dec 8 18:16:06 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 8 Dec 2008 19:16:06 +0100 Subject: Fedora Weekly News #155 Message-ID: <000c01c95961$09cba2d0$ba00000a@grecom.local> Fedora Weekly News Issue 155 Welcome to Fedora Weekly News Issue 155 for the week ending December 7th, 2008. http://fedoraproject.org/wiki/FWN/Issue155 FWN is pleased to announce the return of the Planet Fedora beat. Among other items Adam Batkin lists some "Howtos and Tips" gleaned from blogs. In Announcements the "Fedora 11" naming scheme is discussed. In Developments "The PATH to CAPP" exposes disquiet with some security infrastructure. Translation provides updates on the cancellation of FLSCo elections. Artwork is again bursting at the seems with a "T-Shirt Logo Design Tool" and "Improved Document Templates". SecurityAdvisories lists this week's essential updates. Finally Virtualization continues to race the shocking pace of developments including the "Release of libvirt 0.5.0 and 0.5.1" There's plenty more a mere mouse click away! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [0] http://fedoraproject.org/en/get-fedora [1] http://fedoraproject.org/wiki/NewsProject/Join Fedora Weekly News Issue 155 1.1 Announcements 1.1.1 FUDCon Boston (F11) 1.1.2 Fedora 11 1.1.3 Other 1.2 Planet Fedora 1.2.1 General 1.2.2 How-To and Tips 1.2.3 FOSS.IN 1.3 Developments 1.3.1 The PATH to CAPP Audits 1.3.2 The Looming Py3K Monster 1.3.3 PackageKit Stealth Installations 1.3.4 DNS Resolution Unreliable 1.4 Translation 1.4.1 FLSco Elections Cancelled 1.4.2 Fedora-website Translation Repo Re-enabled 1.4.3 Transifex version updated for translate.fedoraproject.org 1.4.4 New Members in FLP 1.5 Artwork 1.5.1 Improved Document Templates 1.5.2 Postprocessing in Icons 1.5.3 FirstAidKit Artwork 1.5.4 T-Shirt Logo Design Tool 1.6 Security Advisories 1.6.1 Fedora 10 Security Advisories 1.6.2 Fedora 9 Security Advisories 1.6.3 Fedora 8 Security Advisories 1.7 Virtualization 1.7.1 Enterprise Management Tools List 1.7.1.1 Enabling Builds of libvirt for Windows 1.7.1.2 Solaris Support in virtinst 1.7.2 Fedora Xen List 1.7.2.1 Support for Fedora 10 DomU on F8 Dom0 1.7.2.2 Paravirt Ops Dom0 Feature Update 1.7.3 Libvirt List 1.7.3.1 Release of libvirt 0.5.0 and 0.5.1 1.7.3.2 Allow Automatic Driver Probe for Remote TCP Connections 1.7.3.3 Thread Safety for libvirtd Daemon and Drivers 1.7.3.4 libvirt 0.5.0 and KVM Migration Support 1.7.4 oVirt Devel List 1.7.4.1 Some Architecture Diagrams 1.7.4.2 Standalone Console Viewer for oVirt == Announcements == In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack === FUDCon Boston (F11) === Paul Frields made a few announcements this week regarding FUDCon Boston[1], which is January 9-11. Paul mentioned[2] that the event will be held at MIT, he gives information about the social event, and also reminds people to register on the wiki and to make their hotel reservations before December 19th, in order to secure the $99 hotel room rate. [1] http://fedoraproject.org/wiki/FUDCon/FUDConF11 [2] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00000.html === Fedora 11 === Josh Boyer wrote[3] about the process for selecting the Fedora 11 name. "We're doing the name collection differently this year than in the past. Contributors wishing to make a suggestion are asked to go to the F11 naming wiki page[4], and add an entry to the suggestion table found there". [3] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00001.html [4] https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_11 Jon Stanley announced[5,6] the Fedora 11 freeze dates. The Alpha freeze is currently scheduled for January 20, and the Final freeze for April 14. [5] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00005.html [6] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00006.html Ignacio Vazquez-Abrams announced[7] that Python 2.6 is now in Rawhide. For those of you who maintain Python packages, you'll want to read the full announcement. [7] http://www.redhat.com/archives/fedora-devel-announce/2008-December/msg00007.html Other Finally, Paul Frields announced[8] that Chris Aillon has been re-appointed to the Fedora Board, and will serve another two-release term. [8] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00005.html == Planet Fedora == In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin === General === Fabian Affolter posted[0] a nice graph showing the number of unique fedoraproject.org visitors (progressively growing since 2006!) [0] http://fabaff.blogspot.com/2008/12/fedoraprojectorg-unique-visitors.html Karsten Wade appealed[1] for information about configuring a misbehaving Synaptic touchpad on Fedora 10, followed[2] shortly thereafter by a solution. [1] http://iquaid.org/2008/11/30/synaptic-tapping-fail-is-there-a-good-fix/ [2] http://iquaid.org/2008/12/02/more-than-one-way-to-skin-a-touchpad/ Max Spevack wondered[3] whether there is a nice way to build a custom Fedora mirror tailored specifically to one's installed package set. [3] http://spevack.livejournal.com/69145.html Thorsten Leemhuis critiqued[4] the Fedora Release Notes, providing some suggestions for how to make the important bits stand out more. [4] http://thorstenl.blogspot.com/2008/12/read-same-paragraphs-every-half-year.html A look ahead[5] at some of the innovations in the open source world that we can look forward to during 2009 [5] http://liquidat.wordpress.com/2008/12/01/the-open-source-year-2009/ Luis Villa mused[6][7] on innovation in general and the Linux Desktop (think Gnome and KDE) in particular. [6] http://tieguy.org/blog/2008/12/05/the-linux-desktops-change-problem/ [7] http://tieguy.org/blog/2008/12/06/slight-innovation-followup/ Greg DeKoenigsberg wrote a few[8] posts[9] chronicling[10] his experiences with Sugar [8] http://gregdek.livejournal.com/40932.html [9] http://gregdek.livejournal.com/41431.html [10] http://gregdek.livejournal.com/41616.html Apparently Luis Villa had[11] a similar idea [11] http://tieguy.org/blog/2008/12/02/playing-with-sugar/ A video interview[12] with Paul W. Frields about the Fedora 10 release [12] http://www.redhatmagazine.com/2008/12/02/video-fedora-10/ === How-To and Tips === Tom Tromey wrote an 8-part (so far) series[13] on using a Python-enabled GDB. The series is not just about debugging Python with GDB, but also extending GDB using Python. [13] http://tromey.com/blog/?p=494 Jeroen van Meeuwen provided some instructions for composing EL5 media on Fedora 9 or 10 systems[14] by running Revisor inside mock [14] http://kanarip.livejournal.com/6276.html James Laska wrote a tutorial on how to automate a classroom/lab-type[15] setup using tools such as Cobbler, Snake and Koan [15] http://jlaska.livejournal.com/3696.html Michael Stahnke had some problems (and solutions)[16] for getting Fedora 10 running as a Xen guest on EL5 [16] http://www.stahnkage.com/blogs/index.php?/archives/482-F10-and-Xen-images.html Dale Bewley wrote about expanding[17] an Encrypted Filesystem with LVM and Fedora 10 [17] http://tofu.org/drupal/node/71 Steven Moix managed to get[18] iTunes music sharing working in Fedora 10 [18] http://www.alphatek.info/2008/12/01/itunes-music-sharing-in-fedora-10/ Dave Jones had some tips[19] for making an ASUS Eee PC 900 (or any generally underpowered UMPC with a solid state disk) happier under Linux [19] http://kernelslacker.livejournal.com/132087.html Harald Hoyer also provided some performance advice[20], this time to help identify disk IO bottlenecks during bootup using SystemTap [20] http://www.harald-hoyer.de/personal/blog/fedora-10-disk-io === FOSS.IN === A number of people wrote up their experiences and provided pictures from FOSS.IN: [21] http://james-morris.livejournal.com/36445.html [22] http://james-morris.livejournal.com/36715.html [23] http://soumya.dgplug.org/?p=33 [24] http://kushaldas.in/2008/12/02/through-my-lenses-fossin-2008/ [25] http://rahulpmb.blogspot.com/2008/12/pics-from-fossin.html [26] http://www.tuxmaniac.com/blog/2008/12/07/fossin-2008-lots-of-fun/ == Developments == In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley === The PATH to CAPP Audits === Some tough questioning about the purpose and usefulness of the Common Criteria for Information Technology Security Evaluation (CC)[1] was dished out to the maintainers of shadow-utils (the family of secure utilities for manipulating user accounts and passwords) when it appeared that the need to audit specific behaviors was causing some awkward constraints in OS design. The CC certifications are an ISO standard originally developed by the USA's National Security Agency to specify the expected behavior of systems under certain strictly defined criteria (so called Protection Profiles) to certain levels (Enterprise Evaluation Levels). Red Hat Enterprise Linux (a downstream derivative of Fedora) is able to boast several of them, including CAPP,LSPP and RBACPP to EAL4+[2], enabling RHEL5 to be purchased for use in government programs which require "assured information sharing." See[3][4] for further information. In order to provide the auditing capabilities mandatory to achieve such certifications Steve Grubb and others on his team have been steadily committing changes to Fedora. The specific protection profile under discussion in this case was the Controlled Access Protection Profile (CAPP) and there has been a good deal of unease about the usefulness of such certification in other forums[5]. [1] http://en.wikipedia.org/wiki/Common.Criteria [2] http://www.redhat.com/solutions/government/commoncriteria/ [3] A good blog entry by Sun's Jim Laurent: http://blogs.sun.com/jimlaurent/entry/faq.what.is.a.common [4] https://www2.sans.org/reading.room/whitepapers/standards/1078.php [5] http://www.schneier.com/blog/archives/2005/12/microsoft.windo.html When Callum Lerwick noticed[6] that he could not run usermod as an unprivileged user in order to get its help page he suggested that "[...] it and all the other account tools have been changed to mode 750, inaccessible to normal users" and erroneously attributed this to recent changes made to accommodate changes to the PATH environment variable. Earlier discussion of the addition of the sbin directories to users' PATHs can be found in FWN#146[7]. Jon Stanley replied[8] "These permissions have been in place for over 2 years, with valid reasoning. Just because it's in your PATH doesn't mean you should be able to execute it." Jon appended the 2006 log message which attributed the change to "fix regression. Permissions on user* group* binaries should be 0750, because of CAPP/LSPP certification." Callum posted a list of all the account tools which had such permissions including the shadow-utils account tools and the audit subsystem tools. [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00489.html [7] http://fedoraproject.org/wiki/FWN/Issue146#PATH:.2Fsbin.Tab.Confusion [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00495.html Although the change was actually several years old it appeared to cause surprise in many circles and prompted demands for information on what CAPP was and whether it was of any use to the Fedora Project. Steve Grubb responded[9] to the original query that "[...] you cannot do anything with [the user* commands] unless you are root. Allowing anyone to execute them would require lots of bad things for our LSPP/CAPP evaluations" and suggested that man pages should be used instead of running the tools with the --help argument. [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00501.html Jesse Keating probed what appeared to be a reliance on restricting execution permissions for security. When Steve corrected[10] this to be "[...] more to do with the fact that we have to audit all attempts to modify trusted databases - in this case, shadow [...] if we open the permissions, we need to make these become setuid root so that we send audit events saying they failed" Jesse was even more perturbed[11] and asked "Why would the binary have to be suid? Why can't the binary detect that [the] calling user is not root, and just print out the usage and a message saying that you have to be root? How would this action make it any less auditable?" Later Chris Adams extended[12] the apparent logic: "[...] cat will have to be setuid root so it can audit? What about echo, bash, perl, etc.? This is absurd." [10] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00513.html [11] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00523.html [12] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00575.html >From this point onwards the confusion and questioning gained in volume and intensity with several points being made to question the usefulness of this particular (CAPP) certification. These included the points that any user could obtain copies of the restricted binaries from outside of the system[13] for nefarious testing purposes; and that there were plenty of other tools[14] on the system which might allow violations of the policy. [13] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00514.html [14] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00626.html It would be fair to characterize most of the reactions as hostile. Some of this was due to an apparent impatience with "security certifications" which seemed to be of more interest to managers than achieving practical security. Callum Lerwick suggested[15] "[...] just because RHEL has to do stupid ignorant shit to appease certification authorities doesn't mean Fedora has to do it too." Another part was undoubtedly due to concern about who had made the decision to follow this path. Jesse Keating expressed[16] some frustration and asked "Who's 'we'? Perhaps 'we' shouldn't piss on Fedora in order to meet some cert that I highly highly doubt any Fedora install will find useful." When Seth Vidal and Dominik Mierzejewski also wondered when, and by whom, the decision was made Steve answered[17]: "By me after a group presented the options back in 2005. Back in those days shadow-utils was in 'Core' and that was maintained by Red Hat." [15] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00528.html [16] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00534.html [17] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00584.html Another part of the hostility seemed to originate in the novelty of the certification requirements to many participants. Steve answered many queries as they came in and suggested that it was necessary to take an overview of how the whole process worked. He was pressed by Jeff Spaleta for further details. This led[18] to an interesting quote from the CAPP guidelines and the example of how they are applied to shadow-utils. The guidelines make some assumptions which many will find unrealistic, such as the "[t]he system administrative personnel are not careless, willfully negligent, or hostile, and will follow and abide by the instructions provided by the administrator documentation." While this criticism obviously calls into question the practical usefulness of the CAPP certification it is just one layer designed to perform a specific function, other more apparently useful security can only be built on top of these layers after they are implemented. Steve's post also contained some interesting practical examples of how administrators can use the audit tools to view information gained by instrumenting the shadow-utils code. To see who has modified accounts, and how, one can: #ausearch --start this-month -m ADD_USER #ausearch --start this-month -m ADD_GROUP A view of attempts to change accounts both through the approved shadow-utils (restricted to root) or other non-approved tools can be obtained with a ausearch --start this-month -f /etc/shadow *raw -- aureport -x -i [18] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00585.html Enrico Scholz pointed out[19] that this seemed like security through obscurity because there were other tools (vipw and ldapadd) which could modify the trusted database and Steve responded[20] that vipw was forbidden and that it would be possible to extend the auditing to ldap if someone had the time. In response to Andrew Bartlett Jesse Keating interpreted[21] this "forbidden" as "`forbidden by policy' in which using anything /but/ the audit-able tools is `forbidden by policy'. If you're expecting everybody to follow policy, why not just set policy that says `don't hack this box'. That'll work right?" [19] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00587.html [20] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00588.html [21] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00623.html Callum Lerwick jumped[22] to what was for him the central point: "So I guess this is what all this really comes down to: Do we care about certification?" and asked whether the shadow-utils maintainer(s) would care to put the permissions to a FESCo vote. Steve affirmed[23] that certification was worthwhile with a detailed list of the positive side-effects of the certification process which include: man pages for each syscall, bug fixing and reporting, test suites, crypto work, virtualization with strong guarantees of VM separation and more. It was an impressive list which seemed to counter the dominant assumption that certification was merely another item to be ticked off on a bureaucrat's mindless list. Steve noted that "[a]s a result, Fedora is the ONLY community distribution that actually meets certification requirements. OpenSuse might be close for CAPP, but not LSPP/RSBAC, but that would be the only one I can think of that might be getting close." [22] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00560.html [23] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00563.html While this summary might make it seem as though certification is a slamdunk (and your correspondent has to admit a strong bias in favor of it) it has probably failed to convey the sense of unease expressed by Fedora Project contributors that decisions have been taken without discussion or consultation. Jesse Keating asked[24] Steve Grubb to explain who was providing impetus to the shadow-utils/certification team: "Where is this yelling going on? Where are the bug reports? Where is the public discussion about supposed problems in our install processes? Where is the discussion with domain knowledge experts debating whether or not the complaint has merit? Where is the open and frank discussion?" [24] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00547.html One possible route around what seems to be an impasse was suggested by Jeff Spaleta. Jeff observed[25] that CAPP certification for putative "appliance spins", but not the current set of spins, might make sense and asked[26]: "could some of the restrictions like the permissions be handled in a more modular way? Could for example, things be changed so I could install a specialized fedora-CAPP package at install time which tightens up aspects of the system to bring it into CAPP compliance, instead of expressing those restrictions in the default settings of all installs?" [25] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00556.html [26] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00625.html === The Looming Py3K Monster === Last week we reported that Ignacio Vazquez-Abrams was busy shepherding Python-2.6 into Fedora. This week Michael DeHaan raised[1] the question of what the plan for incorporating Python 3K will be. Michael worried that Py3K's incompatibilities with Python-2.6 "[are] pretty bad for someone who wants to keep a single codebase across EL 4 (Python 2.3) and up, which I think a lot of us do. That gets to be darn impossible and we have to double our involvement with code because we essentially have to maintain a differently-compatible fork for each project." He asked: "Are we looking at also carrying on with packaging 2.N indefinitely when we do decide to carry 3, because as I know it, the code changes to make something Python 3 compatible will be severe and that's a big item for any release, and will probably result in some undiscovered bugs even after the initial ports (if applied)." [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00379.html Although there was some optimism that the "from future import" syntax would allow the use of python-3 features in python-2 Daniel P. Berrange quashed[2] the idea that this was a simple fix because it "[...] isn't much help if python 2.3, 2.4 and 2.5 don't support 'from future import' and you care about shipping stuff that works on the 99% of deployed Linux boxes today which don't have 2.6 let alone 3.0." Basil Mohamed Gohar suggested[3] running the 2to3 tool on the Core packages to gain a sense of what needs to be done. [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00394.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00438.html Some strategies and their implications were detailed[4] by Toshio Kuratomi in a post which comprehensively explains the options. Toshio suggested avoiding maintaining separate python2 and python3 packages within a single version of Fedora due to the resulting double work and space. He suggested that "[...] this decision is only partially within the powers of the Fedora Project to decide. If 80% of our upstream libraries move to py3, we'll need to move to py3 sooner. If 80% refuse to move off of py2, we can take our time working on migration code." In later discussion with Arthur Pemberton he seemed[5] to favor the idea of using python-2.6 while ensuring that all code is as compatible as possible with python-3 and avoided estimating how hard this would be until actual experience is gained with "[...] porting code to 2.6 with 3.x features turned on at some point." [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00420.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00437.html James Antill was[6] skeptical that Py3K would be seen in Fedora any time soon due to the massive changes required and the past history (FWN#114[7])of votes on maintaining compatibility packages: "I'll put money on python3k not being the default in Fedora 12. Hell, I'll even put some money on it not being the default in Fedora 14, at this point. My personal opinion is that we stay with 2.6.* for as long as possible, giving everyone time to dual port and the problems to be found/fixed and then it "should be easy" to have it as a feature and move for one release. But I'll point out that Ignacio Vazquez-Abrams did .all. the work for 2.6 in Fedora 11 ... so feel free to take this as just my opinion." [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00391.html [7] http://fedoraproject.org/wiki/FWN/Issue114#Policy.Proposal.For.New.Compatibility.Packages === PackageKit Stealth Installations === Robert Locke asked[1] how createrepo, anaconda-yum-plugins and preupgrade had been installed without his permission on a fresh Fedora 10 install. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00431.html An answer was posted[2] by Jesse Keating to the effect that this had been done by PackageKit "[...] so that it could offer you the ability to upgrade. We've moved that information to a public webserver rather than being in the preupgrade package so that PK can get this information without stealth installing packages." He added that while there were no "[...] current guidelines that would have caught this [...] it does fall into the `don't do that' category." [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00448.html In further answers Jesse explained[3]: "It was installed so that PackageKit could have the appropriate information to check if there were distro level upgrades (say 9 to 10) available for you. The upstream has been asked to please not install any software in Fedora without a users consent, so hopefully this scenario won't happen again, at least not with PackageKit." [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00505.html === DNS Resolution Unreliable === Previously in FWN#154[1] we reported on some strange name resolution problems. Seth Vidal, as maintainer of the YUM package which looked as though it might be implicated, requested[2] follow-up information. [1] http://fedoraproject.org/wiki/FWN/Issue154#Strange.Resolution.Problems [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00246.html Tim Niemuller replied that the problems persisted for him and were probably not to do with YUM. He added failures with svn to the mix and suggested[3] that "[...] yum is [not] the problem but there is a more general problem related to DNS lookups. As a specialty I'm using nss-mdns. But on F-8/F-9 this has never been a problem, so I suspect this is not what is causing the problem, especially because others have the same problem and I don't think nss-mdns is installed on many machines." [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00305.html Jonathan Underwood posted[4] a link to a heavily commented bugzilla entry opened by Tom Horsley on 2008-08-21. The gist of the comments appears to be that with certain DNS servers there is a problem with simultaneous IPv4 and IPv6 requests being sent. A reported[5] work-around involved using a non-glibc resolver such as dnsmasq and was added[6] to the Fedora Project wiki by Christopher Stone. [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00308.html [5] http://www.fedorafaq.org/f10/#dns-slow [6] https://fedoraproject.org/wiki/Common.F10.bugs#DNS.Resolver.not.Reliable Jakub Jelinek prepared[7] a glibc update which temporarily disables the simultaneous requests and Ben Williams promised that once the issue is cleanly resolved the Fedora Unity team[8] will issue a Fedora 10 re-spin. [7] https://bugzilla.redhat.com/show.bug.cgi?id=459756#c91 [8] http://fedoraunity.org/ == Translation == This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee === FLSco Elections Cancelled === The mid-term elections for Fedora Localization Steering Committee (FLSCo) were cancelled and the Fedora Localization Project decided to go ahead with the current Committee for another release[1][2]. [1] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00011.html [2] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00018.html === Fedora-website Translation Repo Re-enabled === The main repository for the Fedora Website translation was re-enabled post Fedora 10 release and the intermediate test repository is now disabled[3]. As reiterated by RickyZhou, any updations to Fedora Website content are to be submitted to the main repository[4]. [3] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00003.html [4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00001.html === Transifex Version Updated for translate.fedoraproject.org === RickyZhou announced that the transifex version on translate.fedoraproject.org has been updated and very soon new features like translated interface and module descriptions would also be added[5]. [5] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00023.html === New Members in FLP === Nikolay Vladimirov[6] and Daniel Cabrera[7] are the two new members joining the Fedora Localization Project for the Bulgarian and Spanish team respectively. [6] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00004.html [7] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00024.html == Artwork == In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei === Improved Document Templates === M?ir?n Duffy proposed on @fedora-art a new project for Fedora 11 "finding and developing nice-looking, general-purpose templates we could then package up for programs like OpenOffice.org Writer, OpenOffice.org Impress, Scribus, Inkscape, Gimp, etc.", proposal received[2] with enthusiasm by Seth Kenlon, who also asked bout font requirements in those templates "does anyone know if there are special requirements in terms of fonts we could actually use and expect upstream to definitely have?", a question answered[3] quickly by M?ir?n "I think we should only assume users will have access to the fonts packaged for Fedora proper. If we use a font that isn't included in the default live media installation, then we should require the Fedora font package needed." [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00001.html [2] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00008.html [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00009.html === Postprocessing in Icons === MartinSourada raised[1] a technical debate on @fedora-art, questioning if the desktop icons should be always generated directly from the SVG sources or if some additional raster post-processing is allowed "My reason for this is that while I am unable to achieve, to my eye, perfect antialiasing in some cases when using direct export in inkscape, but after exporting it in bigger size applying some filters and resizing to desired size I am able to achieve, to my eye, better results", a question still under debate, awaiting input for contributors with more experience in icon creation. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00005.html === FirstAidKit Artwork === Maria Leandro resumed[1] the work on an older DesignService request[2] "I made some tries and finally came up something he like" a graphic received with only a small concern[3] from Mike Langlie "The Red Cross owns the trademark to the red cross icon/logo. They have sent cease and desist orders to game companies that use it as an icon for health re-ups. They do suggest using a green cross or white cross on a green background instead as a generic alternative", something easily addressed by Maria[4] [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00002.html [2] https://fedoraproject.org/wiki/Artwork/DesignService#Firstaidkit [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00003.html [4] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00004.html === T-Shirt Logo Design Tool === Following a chat on the IRC channel, Charles Brej followed[1] on @fedora-art with a small application which can be used to create T-shirt designs flom 'tag clouds': "I wrote a little tool to create these 'word splat' things with the idea of using the generated images as the Fudcon t-shirt designs". There is a strong possibility to see a number of graphics created during the upcoming year with this tool. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00026.html [2] http://www.cs.man.ac.uk/~brejc8/temp/try3.png == Security Advisories == In this section, we cover Security Advisories from fedora-package-announce. https://www.redhat.com/mailman/listinfo/fedora-package-announce Contributing Writer: David Nalley === Fedora 10 Security Advisories === * lynx-2.8.6-18.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00065.html * wordpress-2.6.5-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00083.html * samba-3.2.5-0.23.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00116.html * blender-2.48a-4.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00178.html * grip-3.2.0-24.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00183.html * dbus-1.2.6-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00209.html * squirrelmail-1.4.17-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00232.html * clamav-0.94.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00308.html * syslog-ng-2.0.10-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00397.html * java-1.6.0-openjdk-1.6.0.0-7.b12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00444.html === Fedora 9 Security Advisories === * wordpress-2.6.5-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00000.html * samba-3.2.5-0.22.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00021.html * lynx-2.8.6-17.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00066.html * squirrelmail-1.4.17-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00223.html * syslog-ng-2.0.10-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00237.html * java-1.6.0-openjdk-1.6.0.0-0.20.b09.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00384.html * dbus-1.2.6-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00436.html === Fedora 8 Security Advisories === Fedora 8 is nearing EOL Per FESCo support for Fedora 8 will be discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html * samba-3.0.33-0.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00141.html * lynx-2.8.6-12.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00143.html * wordpress-2.6.5-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00176.html * squirrelmail-1.4.17-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00449.html * syslog-ng-2.0.10-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00450.html == Virtualization == In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley === Enterprise Management Tools List === This section contains the discussion happening on the et-mgmt-tools list Enabling Builds of libvirt for Windows Richard W.M. Jones sought[1] help in enabling builds of Windows libvirt binaries under Fedora. "It seems like we should have the base MinGW (Windows cross-compiler) packages in Fedora 11 by the end of this week. This email is to document the additional packages we need to get approved, in order to get the cross-compiled libvirt and virt tools into (or buildable by) Fedora 11. If you want to help out, please start reviewing by following the Bugzilla links, and looking at the approved packaging guidelines[2]" [1] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00073.html [2] http://fedoraproject.org/wiki/Packaging/MinGW. ==== Solaris Support in virtinst ==== John Levon submitted several patches to improve Solaris support in image:Echo-package-16px.pngpython-virtinst including and not limited to the following: * Add an option for passing Solaris JumpStart information.[1] * Various utility functions[2]. * "Make 'solaris' a first-class OS type, and select USB tablet support for the appropriate variants."[3] * Add support for Solaris PV.[4] * Support for the vdisk format[5]. John explained "vdisk is basically " Sun's " tap implementation and disk management tool. [1] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00062.html [2] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00063.html [3] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00064.html [4] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00065.html [5] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00067.html === Fedora Xen List === This section contains the discussion happening on the fedora-xen list. ==== Support for Fedora 10 DomU on F8 Dom0 ==== The changes[1] made to the image:Echo-package-16px.pngkernel which obviated image:Echo-package-16px.pngkernel-xen caused image:Echo-package-16px.pngpython-virtinst to fail[2] during the creation of a Fedora 10 Xen guest on a Fedora 8 Xen host. Cole Robinson announced[3] a test build[4] which fixes this problem. Readers are encouraged to test the release and provide positive karma points in bodhi[5] to make the build an official update. [1] http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Adminstrators_Care_About.html#sn-Unified_kernel_image [2] RHBZ #458164 [3] http://www.redhat.com/archives/fedora-xen/2008-November/msg00036.html [4] http://koji.fedoraproject.org/koji/buildinfo?buildID=71125 [5] https://admin.fedoraproject.org/updates/F8/FEDORA-2008-10394 ==== Paravirt Ops Dom0 Feature Update ==== After some prompting[1] from Pasi K?rkk?inen the dom0 support feature page[2] was updated to better clarify where the work to bring dom0 support back to Fedora is being done, and to more accurately represent the current status. The patches[3] are being written by Jeremy Fitzhardinge and others at Citrix/XenSource are being submitted to the mainline kernel. Once accepted in the upstream kernel, efforts will resume within Fedora to make the changes necessary to support dom0. These efforts include[4] ensuring the hypervisor supports bzImage kernels. [1] http://www.redhat.com/archives/fedora-xen/2008-November/msg00021.html [2] http://fedoraproject.org/wiki/Features/XenPvopsDom0 [3] http://xenbits.xen.org/paravirt_ops/patches.hg/ [4] http://www.redhat.com/archives/fedora-xen/2008-November/msg00025.html === Libvirt List === This section contains the discussion happening on the libvir-list. ==== Release of libvirt 0.5.0 and 0.5.1 ==== Daniel Veillard announced[1][2] the releases of image:Echo-package-16px.pnglibvirt 0.5.0 and 0.5.1. "This is a long expected release, with a lot of new features, as a result the small version number is increased." Tarballs and signed RPMs available upstream[3] and in Bodhi[4]. "As stated there is a huge amount of new features and improvement in this release, as well as a lot of bug fixes, the list is quite long". See the post[1] for the full list including the numerous improvments, documentation updates, bug fixes, and cleanups omitted below. New features: * CPU and scheduler support for LXC (Dan Smith) * SDL display configuration (Daniel Berrange) * domain lifecycle event support for QEmu and Xen with python bindings (Ben Guthro and Daniel Berrange) * KVM/QEmu migration support (Rich Jones and Chris Lalancette) * User Mode Linux driver (Daniel Berrange) * API for node device enumeration using HAL and DeviceKit with python bindings (David Lively) "Thanks a lot to everybody who contributed to this release, it is really great to see new people providing significant patches, and the amount of feedback received on the list." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00387.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00148.html [3] ftp://libvirt.org/libvirt/ [4] https://admin.fedoraproject.org/updates/libvirt ==== Allow Automatic Driver Probe for Remote TCP Connections ==== Later described by the release of image:Echo-package-16px.pnglibvirt 0.5.1 as an improvement, Daniel P. Berrange posted[1] the patch to implement a more general method for connecting to remote[2] hypervisor drivers. "When connecting to a local libvirt you can let it automatically probe the hypervisor URI if you don't know it ahead of time. This doesn't work with remote URIs because you need to have something to put in the URI scheme before the hostname: * qemu+ssh://somehost/system * xen+tcp://somehost/system This is then translated into the URI: * qemu:///system * xen:/// ... This patch adds a 'remote' URI scheme, usable like this: * remote+ssh://somehost/ * remote+tcp://somehost/ ... This finally makes the Avahi[3] broadcasts useful - they only include info on the hostname + data transport (SSH, TCP, TLS), not the HV type. So letting us use auto-probing remotely is the missing link." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html [2] http://libvirt.org/remote.html [3] http://www.avahi.org ==== Thread Safety for libvirtd Daemon and Drivers ==== Daniel P. Berrange posted[1] a huge series of 28 patches which add "thread safety for the libvirtd daemon and drivers, and makes the daemon multi-threaded in processing RPC calls. This enables multiple clients to be processed in parallel, without blocking each other. It does not change the thread rules for the virConnectPtr object though, so each individual client is still serialized." ... "This touches a huge amount of code, so I'd like to get this all merged ASAP as it'll be really hard to keep it synced with ongoing changes." [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00453.html [2] http://fedoraproject.org/wiki/FWN/Issue148#Experimental_Driver_Thread_Safety ==== libvirt 0.5.0 and KVM Migration Support ==== Micka?l Can?vet wondered[1] if image:Echo-package-16px.pngkvm guest migration was expected to be functional. "I just installed image:Echo-package-16px.pnglibvirt 0.5.0 on Debian Lenny with kvm 0.72 to try kvm migration support." Tests failed with "libvir: error : this function is not supported by the hypervisor: virDomainMigrate." Chris Lalancette confirmed[2] "Yes, it is supposed to work, but yes, you need a very, very new kvm. In particular, you need at least kvm-77, and it won't really work right until you get to kvm-79." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00025.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00027.html === oVirt Devel List === This section contains the discussion happening on the ovirt-devel list. ==== Some Architecture Diagrams ==== Daniel P. Berrange said[1] "I felt I wanted some additional more technically detailed/ focused diagrams to illustrate what we're doing to developers actually writing code for the project." And pointed to oVirt architecure diagrams he created.[2] [1] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00357.html [2] http://ovirt.org/page/ArchDiagrams ==== Standalone Console Viewer for oVirt ==== Continuing work on a executable console solution[1] for oVirt, with a fork of image:Echo-package-16px.pngvirt-viewer, Richard W.M. Jones created[2] ovirt-viewer. [1] https://fedoraproject.org/wiki/FWN/Issue151#oVirt_Console_Conundrum [2] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00412.html -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley -- fedora-announce-list mailing list fedora-announce-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-announce-list From stickster at gmail.com Mon Dec 8 18:23:25 2008 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 8 Dec 2008 13:23:25 -0500 Subject: Fedora Weekly News #155 In-Reply-To: <1228758850.8801.1288917291@webmail.messagingengine.com> References: <1228758850.8801.1288917291@webmail.messagingengine.com> Message-ID: <20081208182325.GJ4566@localhost.localdomain> On Mon, Dec 08, 2008 at 12:54:10PM -0500, Oisin Feeley wrote: > Fedora Weekly News Issue 155 > > Welcome to Fedora Weekly News Issue 155 for the week ending December > 7th, 2008. > > http://fedoraproject.org/wiki/FWN/Issue155 > > FWN is pleased to announce the return of the Planet Fedora beat. Among > other items Adam Batkin lists some "Howtos and Tips" gleaned from blogs. > In Announcements the "Fedora 11" naming scheme is discussed. In > Developments "The PATH to CAPP" exposes disquiet with some security > infrastructure. Translation provides updates on the cancellation of > FLSCo elections. Artwork is again bursting at the seems with a "T-Shirt > Logo Design Tool" and "Improved Document Templates". SecurityAdvisories > lists this week's essential updates. Finally Virtualization continues to > race the shocking pace of developments including the "Release of libvirt > 0.5.0 and 0.5.1" There's plenty more a mere mouse click away! I love this summary, even though I completely failed to forward it as part of my internal Red Hat announcement. I'll make sure to include it next time! :-) -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From fedora at leemhuis.info Tue Dec 9 06:55:01 2008 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Tue, 09 Dec 2008 07:55:01 +0100 Subject: Fedora Weekly News #155 In-Reply-To: <20081208182325.GJ4566@localhost.localdomain> References: <1228758850.8801.1288917291@webmail.messagingengine.com> <20081208182325.GJ4566@localhost.localdomain> Message-ID: <493E1645.4070904@leemhuis.info> Hi! On 08.12.2008 19:23, Paul W. Frields wrote: > On Mon, Dec 08, 2008 at 12:54:10PM -0500, Oisin Feeley wrote: >> Fedora Weekly News Issue 155 >> >> Welcome to Fedora Weekly News Issue 155 for the week ending December >> 7th, 2008. >> >> http://fedoraproject.org/wiki/FWN/Issue155 >> >> FWN is pleased to announce the return of the Planet Fedora beat. Among >> other items Adam Batkin lists some "Howtos and Tips" gleaned from blogs. >> In Announcements the "Fedora 11" naming scheme is discussed. In >> Developments "The PATH to CAPP" exposes disquiet with some security >> infrastructure. Translation provides updates on the cancellation of >> FLSCo elections. Artwork is again bursting at the seems with a "T-Shirt >> Logo Design Tool" and "Improved Document Templates". SecurityAdvisories >> lists this week's essential updates. Finally Virtualization continues to >> race the shocking pace of developments including the "Release of libvirt >> 0.5.0 and 0.5.1" There's plenty more a mere mouse click away! > I love this summary, even though I completely failed to forward it as > part of my internal Red Hat announcement. I'll make sure to include > it next time! :-) I wanted to put it in proper words, but I didn't get around to it, so maybe I'll do it just quickly here: I like the FWN in general. But I noticed I often do not read them. They for me are to long and contain way to many details -- the section "The PATH to CAPP Audits" and "The Looming Py3K Monster" for example contain a lot of information (which were hard work to collect), but if I want that in-depth details I'll go and read the thread on the list directly. I think a little bit less (1/3 or 1/4 the length of what it is now) could me more/better here. And all those links in the text with sections like ---- > [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html > > [2] http://libvirt.org/remote.html > > [3] http://www.avahi.org ---- IMHO make it really hard to read. The OpenSUSE weekly news http://en.opensuse.org/OpenSUSE_Weekly_News/49 look much more professional, are likely a whole less work and they even get them translated because they are shorter/focus on the more important things. Just my 2 cent as seldom reader. I thought you guys maybe wanted to know. And don't let my option confuse you to much. Maybe it's just me. CU knurd From oisinfeeley at imapmail.org Tue Dec 9 14:43:36 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Tue, 09 Dec 2008 09:43:36 -0500 Subject: Fedora Weekly News #155 In-Reply-To: <493E1645.4070904@leemhuis.info> References: <1228758850.8801.1288917291@webmail.messagingengine.com> <20081208182325.GJ4566@localhost.localdomain> <493E1645.4070904@leemhuis.info> Message-ID: <1228833816.15235.1289093103@webmail.messagingengine.com> On Tue, 09 Dec 2008 07:55:01 +0100, "Thorsten Leemhuis" > I wanted to put it in proper words, but I didn't get around to it, so > maybe I'll do it just quickly here: It's really appreciated that you took the time to give some feedback Thorsten. > I like the FWN in general. But I noticed I often do not read them. They > for me are to long and contain way to many details -- the section "The > PATH to CAPP Audits" and "The Looming Py3K Monster" for example contain > a lot of information (which were hard work to collect), I've frequently wondered about that. Does anyone else agree that it's too long? One problem with making things much shorter is that we can either produce what is essentially a simple list of topics, i.e. === CAPP Certification Requirements Cause Unease === Changes made in 2005 to the permissions of shadow-utils tools in order to achieve CAPP certification were called[1] into question. It seems that they may complicate many of what are claimed to be the common use cases of Fedora. Steve Grubb, the shadow-utils maintainer, defended the permissions and explained CAPP certification. [1] Link to start of thread. > but if I want > that in-depth details I'll go and read the thread on the list directly. Why wouldn't you just go and skim the archives directly then? It's easy enough to see what might be the interesting threads. > I think a little bit less (1/3 or 1/4 the length of what it is now) > could me more/better here. 1/3 or 1/4 would actually be a hell of a lot more work. The choices are either: 1) short, nearly content-free summaries which essentially mention the thread and nothing else, or 2)an attempt to provide an unpredjudiced digest. Writing something in between would take a much greater amount of time and probably give rise to a lot more complaints about bias. > > And all those links in the text with sections like > ---- > > [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html > > > > [2] http://libvirt.org/remote.html > > > > [3] http://www.avahi.org > ---- > IMHO make it really hard to read. I would prefer all the links at the bottom of each item. Would that be better or do you just not want to see links except at the end like an attached bibliography? > > The OpenSUSE weekly news > http://en.opensuse.org/OpenSUSE_Weekly_News/49 > look much more professional, For what value of "professional"? To me, like the Ubuntu Weekly News and other distro news I'm not bothered to read them because they're just a collection of links to blog posts. > are likely a whole less work and they even > get them translated because they are shorter/focus on the more important > things. "More important" than what? My impression is that you'd prefer it if there were no "Developments" or "Virtualization" sections and simply a list of what gets posted to @fedora-announce and some entries from Planet. > Just my 2 cent as seldom reader. I thought you guys maybe wanted to > know. And don't let my option confuse you to much. Maybe it's just me. Specifics would be useful (like the comment about the links), otherwise I'm just left with the disappointed feeling that you don't like FWN. Thanks again for the feedback though and it would be nice if you could spare more time to deepen the critique. -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From fedora at leemhuis.info Wed Dec 10 20:37:05 2008 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Wed, 10 Dec 2008 21:37:05 +0100 Subject: Fedora Weekly News #155 In-Reply-To: <1228833816.15235.1289093103@webmail.messagingengine.com> References: <1228758850.8801.1288917291@webmail.messagingengine.com> <20081208182325.GJ4566@localhost.localdomain> <493E1645.4070904@leemhuis.info> <1228833816.15235.1289093103@webmail.messagingengine.com> Message-ID: <49402871.7040802@leemhuis.info> On 09.12.2008 15:43, Oisin Feeley wrote: > On Tue, 09 Dec 2008 07:55:01 +0100, "Thorsten Leemhuis" > >> I wanted to put it in proper words, but I didn't get around to it, so >> maybe I'll do it just quickly here: > It's really appreciated that you took the time to give some feedback > Thorsten. Be careful what you say -- I suppose some people in fedora will call me the always-ranting-guys or something like that ;-) >> I like the FWN in general. But I noticed I often do not read them. They >> for me are to long and contain way to many details -- the section "The >> PATH to CAPP Audits" and "The Looming Py3K Monster" for example contain >> a lot of information (which were hard work to collect), > I've frequently wondered about that. Does anyone else agree that it's > too long? Maybe give it a small test in one of the next issues and ask readers what they prefer? > One problem with making things much shorter is that we can > either produce what is essentially a simple list of topics, i.e. > > === CAPP Certification Requirements Cause Unease === > > Changes made in 2005 to the permissions of shadow-utils tools in order > to achieve CAPP certification were called[1] into question. It seems > that they may complicate many of what are claimed to be the common use > cases of Fedora. Steve Grubb, the shadow-utils maintainer, defended the > permissions and explained CAPP certification. > > [1] Link to start of thread. I would like something like that. That afaics should be enough to make those readers took at the archives that are interested in more details. And afaics it's a whole less work then try to sum up the most important bits of a discussion as it was done in #155 >> but if I want >> that in-depth details I'll go and read the thread on the list directly. > Why wouldn't you just go and skim the archives directly then? It's easy > enough to see what might be the interesting threads. I for one read most of the important fedora lists. But not all -- I for example stopped reading ambassadors and marketing some years ago and would like to rely on FWN to highlight important discussions in a short manner (if there are any); if I then find the topic interesting I'll jump to the list to read the details >> I think a little bit less (1/3 or 1/4 the length of what it is now) >> could me more/better here. > 1/3 or 1/4 would actually be a hell of a lot more work. The choices are > either: 1) short, nearly content-free summaries which essentially > mention the thread and nothing else, or 2)an attempt to provide an > unpredjudiced digest. What I meant is like something like "1)"; but sometimes discussions in subthreads go into a sightly or completely different direction. Then it might be worth to mention them as well. That is afaics done already now, but it's done for way to much subthreads imho. > [...] >> And all those links in the text with sections like >> ---- >>> [1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html >>> >>> [2] http://libvirt.org/remote.html >>> >>> [3] http://www.avahi.org >> ---- >> IMHO make it really hard to read. > I would prefer all the links at the bottom of each item. For text only: Sure. But in HTML/wiki I'd prefer to not see them at all. > [...] >> The OpenSUSE weekly news >> http://en.opensuse.org/OpenSUSE_Weekly_News/49 >> look much more professional, > For what value of "professional"? [...] (a) looks way better (b) you get more information without scrolling (c) it's not that lengthy, which imho is a big plus in todays world, as there are so many information you get offered in different places, hence if I get to many details I'll move on elsewhere >> are likely a whole less work and they even >> get them translated because they are shorter/focus on the more important >> things. > "More important" than what? My impression is that you'd prefer it if > there were no "Developments" or "Virtualization" sections and simply a > list of what gets posted to @fedora-announce and some entries from > Planet. *I* for one would like to see the ten or twelve (?) most important things *for the overall project* mentioned briefly and (in addition) quick one-line links to other things that are also important, but do not qualify as "most important". The Art team for example does great work, but most of the stuff in http://fedoraproject.org/wiki/FWN/LatestIssue#Artwork afaics is only of interest for members of the Art team. Hence it should not be in the FWN; instead it could go to their list if they want to sum up things. That how I did it for EPEL when I was the EPEL Steerign Committee Chair; the most important thins from those reports sometimes were mentioned in the FWN (which also linked to the reports) But again: that's just my option and maybe I'm totally alone with that. >> Just my 2 cent as seldom reader. I thought you guys maybe wanted to >> know. And don't let my option confuse you to much. Maybe it's just me. > Specifics would be useful (like the comment about the links), otherwise > I'm just left with the disappointed feeling that you don't like FWN. Well, yes, I don't like it very much -- mainly because it for me contains simply to many information to read each week. But I like the general idea of FWN and that's why I shared my point of view. I didn#t want to discourage or disappoint you. > [...] Cu knurd From mspevack at redhat.com Wed Dec 10 21:48:07 2008 From: mspevack at redhat.com (Max Spevack) Date: Wed, 10 Dec 2008 22:48:07 +0100 (CET) Subject: Fedora Weekly News #155 In-Reply-To: <49402871.7040802@leemhuis.info> References: <1228758850.8801.1288917291@webmail.messagingengine.com> <20081208182325.GJ4566@localhost.localdomain> <493E1645.4070904@leemhuis.info> <1228833816.15235.1289093103@webmail.messagingengine.com> <49402871.7040802@leemhuis.info> Message-ID: On Wed, 10 Dec 2008, Thorsten Leemhuis wrote: > Be careful what you say -- I suppose some people in fedora will call > me the always-ranting-guys or something like that ;-) Thorsten, of all the people in Fedora, you have earned the right to say whatever you want, whenever you want. :) --Max From oisinfeeley at imapmail.org Thu Dec 11 02:17:17 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Wed, 10 Dec 2008 21:17:17 -0500 Subject: Fedora Weekly News #155 In-Reply-To: <49402871.7040802@leemhuis.info> References: <1228758850.8801.1288917291@webmail.messagingengine.com> <20081208182325.GJ4566@localhost.localdomain> <493E1645.4070904@leemhuis.info> <1228833816.15235.1289093103@webmail.messagingengine.com> <49402871.7040802@leemhuis.info> Message-ID: <1228961837.25273.1289428877@webmail.messagingengine.com> On Wed, 10 Dec 2008 21:37:05 +0100, "Thorsten Leemhuis" > Maybe give it a small test in one of the next issues and ask readers > what they prefer? Makes sense. I'll try it out for the next issue at least. > I for one read most of the important fedora lists. But not all -- I for > example stopped reading ambassadors and marketing some years ago and > would like to rely on FWN to highlight important discussions in a short > manner (if there are any); if I then find the topic interesting I'll > jump to the list to read the details To be honest I have no idea what our reader profiles really are, but given that you're one of the few people to give feedback I'm going to go with a trial run of what you suggest and then see if we get masses of complaints. I suspect that you may be more in tune with what is going on than many of our readers however and there may be a tension between serving your needs and those on the other end of the spectrum: people that don't read much in the way of the mailing lists at all, let alone Bugzilla. [snip] > > I would prefer all the links at the bottom of each item. > > For text only: Sure. But in HTML/wiki I'd prefer to not see them at all. OK, we can do that I think. Just a numbered reference which is an anchor to the actual link should be something we can do. But for the plaintext mailing we'll append the links below each item instead of below each paragraph. > > > [...] > >> The OpenSUSE weekly news > >> http://en.opensuse.org/OpenSUSE_Weekly_News/49 > >> look much more professional, > > For what value of "professional"? [...] > > (a) looks way better > (b) you get more information without scrolling > (c) it's not that lengthy, which imho is a big plus in todays world, as > there are so many information you get offered in different places, hence > if I get to many details I'll move on elsewhere Points taken on board. > > >> are likely a whole less work and they even > >> get them translated because they are shorter/focus on the more important > >> things. > > "More important" than what? My impression is that you'd prefer it if > > there were no "Developments" or "Virtualization" sections and simply a > > list of what gets posted to @fedora-announce and some entries from > > Planet. > > *I* for one would like to see the ten or twelve (?) most important > things *for the overall project* mentioned briefly and (in addition) > quick one-line links to other things that are also important, but do not > qualify as "most important". Hmmm. It's going to be a difficult judgement call to be able to discern what is important "for the overall project". I don't think I'd want to try to do that. Nearly everything on Developments has implications for the overall project. I see the Developments beat as more or less following where the interest and action is, mainly by the volume of posting on a topic. If you, or anyone else, can spot things which should definitely be covered for an upcoming issue then I'd appreciate a friendly ping to make sure I'm on the job. I've tried to do things like cover FESCo deliberations a little so that the context of some of the discussions makes sense to readers who *don't* follow all the important threads, let alone IRC channels. I've realized several weeks that important topics have been neglected, but that's only in retrospect. > > The Art team for example does great work, but most of the stuff in > http://fedoraproject.org/wiki/FWN/LatestIssue#Artwork afaics is only of > interest for members of the Art team. Hence it should not be in the FWN; > instead it could go to their list if they want to sum up things. I really don't think I agree with that. I like reading about what goes on in the Art team as I'm not subscribed to their lists (nor am I going to subscribe), so it's valuable to me to get a quick overview of what they do. Similarly with Virtualization there is no way that I could digest the vast amount of change that's happening and I don't want to be on another list, so getting a weekly digest is absolutely invaluable to me. [snip] > Well, yes, I don't like it very much -- mainly because it for me > contains simply to many information to read each week. But I like the > general idea of FWN and that's why I shared my point of view. I didn#t > want to discourage or disappoint you. As I said before, I really do appreciate the feedback. As Max mentioned in another email your opinion carries a good deal of weight in the project! Apart from that you would be surprised how little feedback we get from anyone. I'm thinking about what you've said and will certainly take a shot at making the Development beat more concise. Apart from anything else it's a mammoth effort to put it out each week. Thanks for sharing your perspective on FWN and I hope that the upcoming issues will be a little more to your taste! Best wishes, -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From dlbewley at lib.ucdavis.edu Mon Dec 8 03:50:52 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sun, 07 Dec 2008 19:50:52 -0800 Subject: issue #155 Message-ID: <1228708252.5033.6.camel@seitan.home.bewley.net> Howdy folks. Virtualization beat is complete. From stickster at gmail.com Thu Dec 11 20:43:51 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 11 Dec 2008 15:43:51 -0500 Subject: FWN "advertisement" Message-ID: <20081211204351.GI7825@localhost.localdomain> Hi news crew, The folks at Red Hat's training offices in APAC would like to know if they may put an announcement in the next issue of the FWN. The announcement offers a substantial discount on training and exams for Red Hat Global Learning courses in Australia and New Zealand, for any Fedora Project members. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mspevack at redhat.com Thu Dec 11 21:50:08 2008 From: mspevack at redhat.com (Max Spevack) Date: Thu, 11 Dec 2008 22:50:08 +0100 (CET) Subject: FWN "advertisement" In-Reply-To: <20081211204351.GI7825@localhost.localdomain> References: <20081211204351.GI7825@localhost.localdomain> Message-ID: On Thu, 11 Dec 2008, Paul W. Frields wrote: > The folks at Red Hat's training offices in APAC would like to know if > they may put an announcement in the next issue of the FWN. The > announcement offers a substantial discount on training and exams for > Red Hat Global Learning courses in Australia and New Zealand, for any > Fedora Project members. What are they willing to pay us? Hey editors, what are our rates for advertising? :D Seriously though, I think we should allow it. --Max From oisinfeeley at imapmail.org Fri Dec 12 00:21:13 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Thu, 11 Dec 2008 19:21:13 -0500 Subject: FWN "advertisement" In-Reply-To: <20081211204351.GI7825@localhost.localdomain> References: <20081211204351.GI7825@localhost.localdomain> Message-ID: <1229041273.18577.1289620933@webmail.messagingengine.com> On Thu, 11 Dec 2008 15:43:51 -0500, "Paul W. Frields" said: > Hi news crew, > > The folks at Red Hat's training offices in APAC would like to know if > they may put an announcement in the next issue of the FWN. The > announcement offers a substantial discount on training and exams for > Red Hat Global Learning courses in Australia and New Zealand, for any > Fedora Project members. Definitely welcome. And it's very nice to see Red Hat offering discounts like this for active contributors. Pascal, Huzaifa: any contradictory opinions? -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From pcalarco at nd.edu Fri Dec 12 02:37:46 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Thu, 11 Dec 2008 21:37:46 -0500 Subject: FWN "advertisement" In-Reply-To: <1229041273.18577.1289620933@webmail.messagingengine.com> References: <20081211204351.GI7825@localhost.localdomain> <1229041273.18577.1289620933@webmail.messagingengine.com> Message-ID: <4941CE7A.3070502@nd.edu> Oisin Feeley wrote: > On Thu, 11 Dec 2008 15:43:51 -0500, "Paul W. Frields" > said: > >> Hi news crew, >> >> The folks at Red Hat's training offices in APAC would like to know if >> they may put an announcement in the next issue of the FWN. The >> announcement offers a substantial discount on training and exams for >> Red Hat Global Learning courses in Australia and New Zealand, for any >> Fedora Project members. >> > > Definitely welcome. And it's very nice to see Red Hat offering discounts > like this for active contributors. > > Pascal, Huzaifa: any contradictory opinions? > > -- > Oisin Feeley > http://fedoraproject.org/wiki/OisinFeeley > This sounds like a great opportunity for those "down under" and its great that FWN can be a vehicle for this. Thanks Paul. - pascal From fedora at leemhuis.info Sat Dec 13 13:16:20 2008 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sat, 13 Dec 2008 14:16:20 +0100 Subject: Fedora Weekly News #155 In-Reply-To: <1228961837.25273.1289428877@webmail.messagingengine.com> References: <1228758850.8801.1288917291@webmail.messagingengine.com> <20081208182325.GJ4566@localhost.localdomain> <493E1645.4070904@leemhuis.info> <1228833816.15235.1289093103@webmail.messagingengine.com> <49402871.7040802@leemhuis.info> <1228961837.25273.1289428877@webmail.messagingengine.com> Message-ID: <4943B5A4.7090005@leemhuis.info> On 11.12.2008 03:17, Oisin Feeley wrote: > On Wed, 10 Dec 2008 21:37:05 +0100, "Thorsten Leemhuis" > [...] >> I for one read most of the important fedora lists. But not all -- I for >> example stopped reading ambassadors and marketing some years ago and >> would like to rely on FWN to highlight important discussions in a short >> manner (if there are any); if I then find the topic interesting I'll >> jump to the list to read the details > To be honest I have no idea what our reader profiles really are, but > given that you're one of the few people to give feedback I'm going to go > with a trial run of what you suggest and then see if we get masses of > complaints. Maybe asking users more directly for their option before testing a different way might be better, because some people always will complain if you change something -- even if the cange definitely makes things better for the masses (not sure if the latter is the case here; it's just meant as general comment) > [snip] >>> I would prefer all the links at the bottom of each item. >> For text only: Sure. But in HTML/wiki I'd prefer to not see them at all. > OK, we can do that I think. Just a numbered reference which is an > anchor to the actual link should be something we can do. But for the > plaintext mailing we'll append the links below each item instead of > below each paragraph. Sounds great to me! > [...] >>>> are likely a whole less work and they even >>>> get them translated because they are shorter/focus on the more important >>>> things. >>> "More important" than what? My impression is that you'd prefer it if >>> there were no "Developments" or "Virtualization" sections and simply a >>> list of what gets posted to @fedora-announce and some entries from >>> Planet. >> *I* for one would like to see the ten or twelve (?) most important >> things *for the overall project* mentioned briefly and (in addition) >> quick one-line links to other things that are also important, but do not >> qualify as "most important". > Hmmm. It's going to be a difficult judgement call to be able to discern > what is important "for the overall project". Sure, it's not easy. > I don't think I'd want to try to do that. Face it: You already did and do some decisions of what's important or not by picking some discussion and ignoring others; and you chose which project areas to report about while others don't get much attention in the FWN. Take EPEL for example, which is not mentioned once in the last ten report afaics. Okay, not much happened in the past ten weeks, but 166 new packages in EPEL5 proper IMHO would have been worth a few words and a link: https://www.redhat.com/archives/epel-devel-list/2008-December/msg00005.html But that not your fault, as I suppose nobody told you about it. It's just meant as example. > Nearly everything on Developments has implications for > the overall project. I see the Developments beat as more or less > following where the interest and action is, mainly by the volume of > posting on a topic. If you, or anyone else, can spot things which should > definitely be covered for an upcoming issue then I'd appreciate a > friendly ping to make sure I'm on the job. When I wrote the EPEL reports back ages ago I tried a few times, but it often failed (which is not your fault; and note, I'm not involved that much anymore in EPEL, it just serves as random example). > I've tried to do things like > cover FESCo deliberations a little so that the context of some of the > discussions makes sense to readers who *don't* follow all the important > threads, let alone IRC channels. I've realized several weeks that > important topics have been neglected, but that's only in retrospect. Sometimes it's IMHO better to neglect important, but not very important topics -- otherwise you write to much in the end that nobody wants to read because it's to long which scares people (like me) away. >> The Art team for example does great work, but most of the stuff in >> http://fedoraproject.org/wiki/FWN/LatestIssue#Artwork afaics is only of >> interest for members of the Art team. Hence it should not be in the FWN; >> instead it could go to their list if they want to sum up things. > I really don't think I agree with that. I like reading about what goes > on in the Art team as I'm not subscribed to their lists (nor am I going > to subscribe), so it's valuable to me to get a quick overview of what > they do. You got me wrong here. I'm fine with reports from the art team and I want to read about the important things they do for the reasons you gave. But for me the current section is to long and to detailed -- the topics "Postprocessing in Icons" and "FirstAidKit Artwork" in FWN155 for example. > Similarly with Virtualization there is no way that I could > digest the vast amount of change that's happening and I don't want to be > on another list, so getting a weekly digest is absolutely invaluable to > me. And for others it might be EPEL, Trans-list, OLPC or one of the other dozens of project areas. If you cover them all that in-depth then the FWN get ever longer and more hard to read. Setting a rough length limit could prevent that. > [...] > I'm thinking about what you've said and will certainly > take a shot at making the Development beat more concise. thx > Apart from > anything else it's a mammoth effort to put it out each week. I know. Many thx for your work. > [...] Cu knurd From dlbewley at lib.ucdavis.edu Sun Dec 14 06:25:08 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sat, 13 Dec 2008 22:25:08 -0800 (PST) Subject: virt complete Message-ID: <6173902.01229235902453.JavaMail.javamailuser@localhost> I'm traveling tomorrow, so virtualization beat is "complete" for 156. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From pcalarco at nd.edu Sun Dec 14 22:41:43 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Sun, 14 Dec 2008 17:41:43 -0500 Subject: FWN "advertisement" In-Reply-To: <20081211204351.GI7825@localhost.localdomain> References: <20081211204351.GI7825@localhost.localdomain> Message-ID: <49458BA7.9040806@nd.edu> Hi Paul -- Do you or the folks at Red Hat have copy for this yet for FWN 156? We're starting to put that issue together, so can plug this into Max's announcements beat when the copy is ready. Thanks! - pascal Paul W. Frields wrote: > Hi news crew, > > The folks at Red Hat's training offices in APAC would like to know if > they may put an announcement in the next issue of the FWN. The > announcement offers a substantial discount on training and exams for > Red Hat Global Learning courses in Australia and New Zealand, for any > Fedora Project members. > > -- > Paul W. Frields http://paul.frields.org/ > gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 > http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ > irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug > From pcalarco at nd.edu Sun Dec 14 22:48:00 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Sun, 14 Dec 2008 17:48:00 -0500 Subject: FWN 156 Message-ID: <49458D20.2040108@nd.edu> Just a couple beats in so far, but I've taken a look at these and made a few minor changes. Thanks to all the writers for this issue! - pascal From mspevack at redhat.com Mon Dec 15 06:04:09 2008 From: mspevack at redhat.com (Max Spevack) Date: Mon, 15 Dec 2008 07:04:09 +0100 (CET) Subject: FWN 156 In-Reply-To: <49458D20.2040108@nd.edu> References: <49458D20.2040108@nd.edu> Message-ID: On Sun, 14 Dec 2008, Pascal Calarco wrote: > Just a couple beats in so far, but I've taken a look at these and made > a few minor changes. Thanks to all the writers for this issue! Announcement beat is in -- there was only one announcement this week, so it should be trivial to edit/finalize. Sorry it was late. --Max From oisinfeeley at imapmail.org Mon Dec 15 12:34:03 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 15 Dec 2008 07:34:03 -0500 Subject: FWN 156 In-Reply-To: <49458D20.2040108@nd.edu> References: <49458D20.2040108@nd.edu> Message-ID: <1229344443.10064.1290108019@webmail.messagingengine.com> On Sun, 14 Dec 2008 17:48:00 -0500, "Pascal Calarco" said: > Just a couple beats in so far, but I've taken a look at these and made a > few minor changes. Thanks to all the writers for this issue! > I'm going to be close to the wire this week, but I'll be there so hold the presses! -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From pcalarco at nd.edu Mon Dec 15 12:33:51 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 15 Dec 2008 07:33:51 -0500 Subject: FWN #156 Message-ID: <49464EAF.60602@nd.edu> I've edited the other beats that have come in and copied these into a page for FWN 156. We'll wait around for most of the morning for any other beats to come in and then write up the intro and ship it out. Thanks everyone! - pascal From pcalarco at nd.edu Mon Dec 15 12:35:00 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 15 Dec 2008 07:35:00 -0500 Subject: FWN 156 In-Reply-To: <1229344443.10064.1290108019@webmail.messagingengine.com> References: <49458D20.2040108@nd.edu> <1229344443.10064.1290108019@webmail.messagingengine.com> Message-ID: <49464EF4.2090803@nd.edu> Oisin Feeley wrote: > On Sun, 14 Dec 2008 17:48:00 -0500, "Pascal Calarco" > said: > >> Just a couple beats in so far, but I've taken a look at these and made a >> few minor changes. Thanks to all the writers for this issue! >> > > I'm going to be close to the wire this week, but I'll be there so hold > the presses! > -- > Oisin Feeley > http://fedoraproject.org/wiki/OisinFeeley > Sounds good, Oisin! From stickster at gmail.com Mon Dec 15 13:36:36 2008 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 15 Dec 2008 08:36:36 -0500 Subject: FWN "advertisement" In-Reply-To: <49458BA7.9040806@nd.edu> References: <20081211204351.GI7825@localhost.localdomain> <49458BA7.9040806@nd.edu> Message-ID: <20081215133636.GJ17949@localhost.localdomain> B1;1704;0cOn Sun, Dec 14, 2008 at 05:41:43PM -0500, Pascal Calarco wrote: > Hi Paul -- > > Do you or the folks at Red Hat have copy for this yet for FWN 156? > We're starting to put that issue together, so can plug this into Max's > announcements beat when the copy is ready. Thanks! Just to close this loop, I sent the copy earlier this morning to the fab-o FWN editorial staff. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From oisinfeeley at imapmail.org Mon Dec 15 16:21:08 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 15 Dec 2008 11:21:08 -0500 Subject: FWN #156 In-Reply-To: <49464EAF.60602@nd.edu> References: <49464EAF.60602@nd.edu> Message-ID: <1229358068.30919.1290147215@webmail.messagingengine.com> On Mon, 15 Dec 2008 07:33:51 -0500, "Pascal Calarco" said: > I've edited the other beats that have come in and copied these into a > page for FWN 156. We'll wait around for most of the morning for any > other beats to come in and then write up the intro and ship it out. > Thanks everyone! > Thanks Pascal, I've just completed my beat and added a sentence to the intro advising that there may be format changes and asking for reader feedback. Are you going to take care of putting the Red Hat discount training ad at the top of announcements? Sorry for my delay this week: a confluence of unpredictable circumstances. best wishes -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From pcalarco at nd.edu Mon Dec 15 17:42:12 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 15 Dec 2008 12:42:12 -0500 Subject: FWN #156 In-Reply-To: <1229358068.30919.1290147215@webmail.messagingengine.com> References: <49464EAF.60602@nd.edu> <1229358068.30919.1290147215@webmail.messagingengine.com> Message-ID: <494696F4.30008@nd.edu> Okay, out of meetings now, so I'll check to see what remains. Thanks all! - pascal Oisin Feeley wrote: > On Mon, 15 Dec 2008 07:33:51 -0500, "Pascal Calarco" > said: >> I've edited the other beats that have come in and copied these into a >> page for FWN 156. We'll wait around for most of the morning for any >> other beats to come in and then write up the intro and ship it out. >> Thanks everyone! >> > > Thanks Pascal, > > I've just completed my beat and added a sentence to the intro advising > that there may be format changes and asking for reader feedback. Are > you going to take care of putting the Red Hat discount training ad at > the top of announcements? > > Sorry for my delay this week: a confluence of unpredictable > circumstances. > > best wishes > -- > Oisin Feeley > http://fedoraproject.org/wiki/OisinFeeley > > _______________________________________________ > Fedora-news-list mailing list > Fedora-news-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-news-list From pcalarco at nd.edu Mon Dec 15 18:29:38 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 15 Dec 2008 13:29:38 -0500 Subject: Fedora Weekly News # 156 Message-ID: <4946A212.10607@nd.edu> -- Fedora Weekly News Issue 156 -- Welcome to Fedora Weekly News Issue 156 for the week ending December 14th, 2008. http://fedoraproject.org/wiki/FWN/Issue156 This week's issue features an exciting discount for Fedora community members in Australia and New Zealand on Red Hat certification training and exams. Coverage of Fedora Planet includes event reports from a FOSS event in India and a Parisian Fedora install fest, along with a nifty XO Exchange Registry. Another flamewar eruption is covered on the Developments beat, along with updates on the D-Bus in Fedora and discussion on making 'updates-testing' more useful. Fedora websites are now available in Russian and Bulgarian, as reported in this issue's Translations beat. The Artwork beat reports on the Fedora Art Team's re-envisioning discussion as well as using the Fedora branding in the OLPC Sugar interface. The security advisory beat updates us on Fedora 9 and 10 updates, along with reminders of Fedora 8 end of life, January 7, 2009. In virtualization news, details of the latest libvert in RHEL and CentOS 5.2. All this and more in this week's FWN! FWN is considering changing the format in response to some reader suggestions. The Developments section this week attempts to be considerably shorter and places URLs below each section instead of interspersing them after each paragraph. We welcome reader feedback on the subject: fedora-news-list at redhat.com. If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [0] http://fedoraproject.org/en/get-fedora [1] http://fedoraproject.org/wiki/NewsProject/Join -- Announcements -- In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack -- Red Hat Certification offer -- STOP THE PRESSES.....50% Discount on Red Hat Certification Exams When the going gets tough - the tough get certified! Maximise your chance of career success in 2009 with Red Hat training and certification Special End of Year Offer for Fedora community members in Australia and New Zealand. 50% discount of all Red Hat Exams taken in Australia and New Zealand by February 28th, 2009 Get your certification today! Act now... simply visit http://www.apac.redhat.com/training/dates.php3 for a complete list of Red Hat exams available until 28th February, 2009 and write "Fedora Community Special" in the Promo code box. Make sure you use your Fedora email id when registering to qualify for the 50% discount. If you have a mate who would benefit from a Red Hat certification, make sure you pass on the good news! -- Terms and Conditions -- This offer begins December 15, 2008 and ends on February 28, 2009. Offer void if participant cancels, no shows, or requests a refund. Offer is subject to availability. Exams, reschedules and any retakes must be completed by February 28, 2009. Participants must register for the promotion at http://www.apac.redhat.com/training/register.php3 and enter ?Fedora Community Special? in the Special Offers section, using their Fedora email id to register. Offer may not be used for exams in which you are already enrolled, cancellations and re-bookings. This offer is not valid in conjunction with any other promotions or special pricing. Participant is responsible for assessing his/her suitability for enrolling in the appropriate exam. Government employees and contractors may not be eligible to receive this offer and the participant acknowledges that his/her employer is aware of and consents to the receipt of the offer, and that the receipt of the offer does not violate the organisation?s policies and regulations. Void where prohibited by law. Offer is available to residents of Australia and New Zealand only. Red Hat reserves the right to withdraw or extend this offer at anytime. -- Updates -- Paul Frields wrote[1] about the update problem affecting D-Bus. "Recently, an update of D-Bus software package in Fedora 10 caused the substantial breakage of some applications, including PackageKit." The announcement includes instructions that explain how a user can update the system manually using yum on the command-line, and return to business-as-usual. If you are unable to perform a normal system update using PackageKit and need help, please read the full announcement. [1] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00012.html -- Planet Fedora -- In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin -- General -- Dave Jones answers[1] some frequently asked questions and common misconceptions regarding Virtual Memory in Linux Tom Tromey concluded[2,3,4] his excellent series on scripting and extending GDB with Python, including some PyGTK widgetry inside GDB. Michael DeHaan contemplates the complexity of software projects and how to encourage new people to get involved and contribute. "Projects that have a lot of complex interrelationships and need a lot of experience with the codebase (that is acquired over a long period of time) are less apt to attract casual contributions"[5] Jesse Keating announced[6] a new Fedora Hosted project, Offtrac: "Offtrac is my attempt at creating a python library for interacting with trac via xmlrpc." The project can already perform a number of tasks including querying, retrieving and creating tickets and milestones. Kulbir Saini presented[7] some ideas for hacking a Linux install to make it boot faster. Luis Villa offered[8] a followup regarding some comments that he had made criticizing OpenOffice.org's user interface and praising Office 2007. M?ir?n Duffy put together[9] an impressive Lightscribe label template for Fedora. Greg DeKoenigsberg introduced[10] the XO Exchange Registry that "connects people who have XOs and don't need them with people who need XOs and don't have them." Tom Callaway ranted[11] (don't worry, those are his own words) about FOSS licensing. He notes that there are no clear standards for what defines a "Free" distribution, as there are often cases where truly difficult questions arise, but adds "This is why for Fedora, the goal of being 100% Free isn't something that we're losing sleep over. Sure, we'd like to be 100% Free, and we're working towards that every day, but actually being 100% Free is HARD, especially if you want more than 700 MB of packages." John Poelstra discussed[12] the "Benefits of Detailed Schedules" after last week's approval of the Fedora 11 schedule. Till Maas announced[13] "some webpages that cache bugzilla queries of package review requests". So if anyone out there would like to jump in and help review some packages, please do so! (there were 719 packages in the NEW state when Till's post went up and already 725 by the time this sentence was written). Luke Macken decided to share[14] a small python program that determines "the amount of time Fedora updates spend in testing within bodhi". Click in to see the results. Matthew Garrett apparently spent a bit of time traveling, and during that time analyzed[15] a number of showers, as a metaphor for UI design in software. Luke Macken committed a Python API for interacting with the Fedora Wiki and shows off[16] some of its statistical gathering abilities. [1] http://kernelslacker.livejournal.com/132396.html [2] http://tromey.com/blog/?p=548 [3] http://tromey.com/blog/?p=550 [4] http://tromey.com/blog/?p=552 [5] http://www.michaeldehaan.net/?p=798 [6] http://jkeating.livejournal.com/66433.html [7] http://fedora.co.in/content/how-boot-your-fedora-faster [8] http://tieguy.org/blog/2008/12/10/why-im-not-a-big-fan-of-ooo-part-53240/ [9] http://mihmo.livejournal.com/65518.html [10] http://gregdek.livejournal.com/42524.html [11] http://spot.livejournal.com/303000.html [12] http://poelcat.wordpress.com/2008/12/12/benefits-of-detailed-schedules/ [13] http://blogs.23.nu/till/2008/12/cached-package-review-buglists/ [14] http://lewk.org/blog/time-in-testing.html [15] http://mjg59.livejournal.com/104279.html [16] http://lewk.org/blog/wiki.html -- Events -- Folks are still posting[17,18,19] photos and writeups of their experience at FOSS.IN. It really sounds like an amazing time was had by all. [17] http://rishikeshsharma.blogspot.com/2008/12/manipur-fedora-10-release-party.html [18] http://sayamindu.randomink.org/ramblings/2008/12/08/fossin-2008/ [19] http://kushaldas.in/2008/12/10/what-else-we-did-at-fossin/ Thomas Canniot wrote[20] about a successful Fedora Install Fest in Paris [20] http://blog.mrtomlinux.org/index.php?post/Fedora-10-Install-Fest-Report -- Developments -- In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley -- Fedora 11: OSS and PulseAudio Conflict Resolved by CUSE ? -- A thread[1] from November led Warren Togami to suggest[2] a plan to use CUSE[3] as part of a strategy to deprecate the near obsolete Open Sound System (OSS) which wreaks havoc with PulseAudio enabled boxes. The plan included a fallback to OSS for users who really wanted it. Bastien Nocera was[4] skeptical that CUSE would be ready in time for Fedora 11 and suggested instead that a list of applications using OSS be created so that they could be fixed. [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01005.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02195.html [3] Character Devices in User space: http://lwn.net/Articles/308445/ [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00872.html -- Rawhide Report 2008-12-08 -- When the latest Rawhide Report logged[1] one maintainers use of cvs-import.sh Dominik Mierzejewski criticised[2] the use of the script for updating. Richard Jones asked[3]: "[I]s this stuff really documented anywhere? I have tended to learn it by osmosis, deduction and reading the horribly complicated rules in Makefile.common." Jason Tibbitts argued[4] that using cvs-import.sh nullified the potential advantages of using an SCM as it sequestered the sources elsewhere. Jesse Keating disagreed[5] due to ease of use issues. A direct answer was provided[6] by Patrice Dumas with links to the relevant portions of the wiki. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00671.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00677.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00691.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00694.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00695.html [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00701.html -- The D-Bus Problem -- Ian Amess asked[1] for the current status of a problem caused by a substantial update of the D-Bus package. The update had resulted in the incapacitation of many packages. The most important of these was PackageKit, the default graphical application for managing software. Colin Walters decided[2] that reverting the update was necessary and that changes to D-Bus policy would be postponed. PackageKit, and its GNOME and KDE clients were updated[3] by Richard Hughes in an attempt to accommodate the changes. Richard testified that "[o]ver the last two days we've all been working really hard on fixing up all the projects after the DBus update. I know personally I'm closing a duplicate bugzilla every 30 minutes." He noted that the delay between creating an update and pushing it to a mirror was a limiting factor in being able to implement these fixes. A post to @fedora-announce by Paul Frields explained[4] the series of steps which allowed users to re-enable normal system updates using PackageKit. As of 2008-12-15 this notice also appears at the top of all the Fedora Project wiki pages. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01391.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01412.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00746.html [4] https://www.redhat.com/archives/fedora-announce-list/2008-December/msg00012.html -- Fedora Com System ? -- An exploration of possible ways to alert users to critical information was initiated[1] by Arthur Pemberton. Most ideas seemed to center around some sort of RSS feed enabled by default on the desktop. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01347.html -- YUM: Enable --skip-broken by Default ? -- Aliasing yum update to yum --skip-broken update was suggested[1] by Steven Moix as a way to prevent a lot of recurring support problems by eliminating dependency problems. It was attempted[2] to strike a balance between reporting these broken dependencies so that they can be fixed and guarding the list of packages on a user's system as private information. A divergent sub-thread delved[3] into the appropriate use of Conflicts: in rpm packages. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01161.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01171.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01349.html -- Making `updates-testing' More Useful -- The means to enable PackageKit to prompt willing users to install testing updates was explored in a thread opened[1] by Matthias Clasen: "Basically, PackageKit should know that these are testing updates, and should ask me 'There are ... package updates available that need testing. Do you want to test these now ?' For extra points, we could even show a 'report back' link somewhere that allows to send comments to bodhi." Richard Hughes prototyped a solution but worried[2] that it would be necessary to make changes to the users' repository configurations without their explicit consent. A sub-thread discussed[3] the problem of out-of-sync mirrors and the use of the --skip-broken option with yum (see also this same FWN#156"YUM: Enable --skip-broken by Default?".) [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00925.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01063.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01314.html -- Fedora Suckage ? -- The tinder for this week's massive flamewar was laid[1] by Robert Scheck in the form of a dryly ironic, multiple-topic rant. Robert attacked the use of "memory wasting" python daemons, lags in pushing updates compared to the EPEL repositories, lack of information on the recent intrusion, poor German translation, the minimal requirements for LiveCD usage, RPM-4.6 bugs, Red Hat employees blocking Merge Reviews, PackageKit bugs, and the EU support organisation for Fedora[2]! Although there were several worthy attempts to make use of the above material for a true conflagration in general the opportunity was wasted and instead several rational, civil discussions of possible underlying causes and explanations took place. There were some worthy attempts to respond to all parts of this portmanteau complaint, but for the most part the discussion fractured naturally into several threads. One such thread was concerned with the pushing of a D-Bus update which broke many applications including PackageKit. Kevin Kofler argued[3] that "[...] we need to be more careful with certain types of security updates, and better let them get some QA even if it means the fix gets delayed." Michael Schwendt asserted[4] the lack of active Quality Assurance as one of the contributing factors. KevinKofler explained[5] that the package had been rushed out "Because it was deemed a security update, complete with a CVE ID[.]" See this FWN#156 "The D-Bus Problem" for more details. Max Spevack took up[6] the complaints about Fedora EMEA and more of that discussion continued[7] on the more appropriate @fedora-ambassadors list. No further information on the security intrusion was forthcoming from Paul Frields but he relayed[8] that the matter was not being forgotten or hushed up and that he planned to meet with others to discuss communication procedures for any possible future intrusions. Richard Hughes asked[9] for specific bugs to be filed instead of general rants: "[...] I think you need to write much shorter, to the point emails. Ranting doesn't have much affect on anything, whilst filing bugs and getting involved upstream does." He also corrected Robert that many of the daemons which he complained about were written in C, not in Python. Colin Walters issued[10] a mea culpa: "Just to be clear, the direct push into stable is my fault; not Red Hat's or other DBus developers or anyone else's. I had originally listed it for updates-testing, but then changed the update to security and in a moment of total stupidity also changed the listing for stable." The idea of "repeatable updates" was raised[11] again by Les Mikesell and critiqued for want of a practical implementation by James Antill. Jesse Keating made[12] a suggestion: "Treat rawhide as your 'new code' land, leave the release trees as your 'testing and working' code. That is don't be so goddamn eager to push new packages and new upstream releases to every freaking branch in existence." Behdad Esfahbod tackled[13] the issue of Red Hat employees allegedly stalling on merge reviews. Behdad criticized the jumbling together of so many issues and repudiated any suggestion that as the maintainer of un-reviewed packages he "[...] must incorporate the merge reviews and close them, no thank you, I don't mind not maintaining anything in Fedora, and I certainly didn't block anyone from making progress in the merge reviews. When you say `The Red Hat people have to follow the Fedora packaging guidelines and rules same as the Fedora folks', does it mean that Fedora should feel free to decide what *I* work on, when it doesn't decide what `other Fedora folks' work on? That doesn't feel right." The criticism of LiveCD localization was handled[14] by Jeroen van Meeuwen and he accepted that it would be useful if there were some manner in which the Spin SIG could create spins and torrent seeds outside of Fedora release engineering. It seemed that the need to make absolutely certain that such torrents and spins are kept available for support purposes may make this difficult. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00722.html [2] EMEA is a non-profit organization with the mission to provide a focal-point and economic base for the European Fedora community. http://fedoraproject.org/wiki/Ambassadors/EMEA [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00733.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00753.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00855.html [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00772.html [7] https://www.redhat.com/archives/fedora-ambassadors-list/2008- December/msg00092.html [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00773.html [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00798.html [10] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00812.html [11] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00832.html [12] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00913.html [13] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00834.html [14] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00899.html -- Help Needed: Sift "rawhide" for .pc Files -- Jesse Keating requested[1] "[...] somebody to examine all the packages in rawhide that provide .pc [pkg-config] files and ensure proper placement of them based on the review guideline. This will likely require interaction with the packages maintainer(s) so the first step should probably be to produce a list of packages that ship .pc in a non -devel package and send the list (sorted by maintainer) to here so that we can discuss and pick off items." Michael Schwendt helped[2] to start the process by providing some lists of non-devel packages which included .pc files or had requires which pulled in packages which provided .pc files. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00612.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00648.html -- Offtrac -- An itch scratched[1] by Jesse Keating was to be able to interact with Trac via the commandline to create milestones for the Fedora 11 release cycle. He implemented his own python library, named Offtrac, to interact with trac using XML-RPC and asked for help in firming up the API and extending his client. Later Jesse explained[2] that the purpose was to "[...] make some aspects of using trac easier for folks, not just project owners but people who file tickets in track, like say for package tagging requests, or blocks, or... " [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00738.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00808.html -- Updates QA and Karma -- The updates system came in for some more questioning (see this FWN#156 "Making `updates-testing' More Useful") when Orion Poplawski showed[1] that an rpcbind update for Fedora 9 may have been pushed to stable despite comments made by him indicating that it failed due to a dependency. Orion asked two questions: "[1] Should update submitters be allowed to give positive karma to their updates? Seems like that they are too biased. [2] Is there any requirement that an update have positive karma before being pushed to stable?" It appeared that ultimately monitoring of such pushes are down to package maintainers and depend upon the good judgment of those doing the updates. Michael Schwendt provided[2] an overview of the situation. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01298.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01427.html -- Translation -- This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee -- Modules Updated in translate.fedoraproject.org 5 modules have been updated[1] in translate.fedoraproject.org due to a move in the backend repositories. These are system-config-(services|date|samba|users|nfs). NilsPhilippsen had earlier conveyed[2] the proposed shift. These modules can now be updated via translate.fedoraprojet.org. DiegoZacarao also adds[1] that the docs modules for these 5 modules would also be added soon for translation submission. [1] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00062.html [2] https://www.redhat.com/archives/fedora-trans-list/2008-November/msg00065.html -- New languages for Fedora Websites -- The Fedora website pages can now be seen in two more languages - Russian[3] and Bulgarian[4]. Additionally, RickyZhou also mentions[5][6] that the language code needs to be added to the LINGUAS file and a ticket with Fedora Infrastructure can be filed to ensure the translations included in Fedora websites. [3] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00054.html [4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00057.html [5] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00056.html [6] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00059.html -- Fedora 10- Release Notes Updation Process -- Any changes to the Fedora 10 Release Notes are to be submitted via translate.fedoraproject.org into the "f1-" branch[7]. KarstenWade also mentions that an intimation to the fedora-docs mailing list would be helpful to ensure that the modifications are accounted for, for the next build. [7] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00036.html -- Suggestions for Fedora Translation Process Improvements -- RobertScheck initiated a general discussion[8] about suggestions to various aspects of the Fedora process including translations. Thomas Spura suggested an an online translation tool[9] that would help more translators to participate in the translation process. Lauri Nurmi reiterates[10] the risks to quality of translations due to a splurge in the quantity of unmonitored translations. [8] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00038.html [9] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00041.html [10] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00042.html -- New Members in FLP -- Christof K?lin[11], Mario Italo[12] and Liu Peng[13] joined the German, Brazilian Portugeuse and Simplified Chinese teams respectively. [11] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00045.html [12] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00063.html [13] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00069.html -- Artwork -- In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei -- Reimagining the Fedora Art Team -- Following a talk on the chat channel, M?ir?n Duffy proposed[1] on @fedora-art a reimagining of the Art Team, as a better way to define the activities encompassed by its members "The Fedora Art Team's name and focus is more on artwork than UI design. Folks in Fedora who need help with UI design or potential contributors who want to help out with UI design might not necessarily link those kinds of tasks to an art team so they might be a bit lost. What if we renamed the art team to be the 'Fedora Design & Creative Team,' and the art team as it is now would be a subgroup of this new design team? Under a 'design' banner, it might be easier for developers seeking out UI design advice to know where to go, and for community UI designers to find a home / a place to get involved." The proposal was welcomed warmly, with only a minor technical concern[2] from Ian Weller "Only thing I'm worried about is renaming all the references to the Art team that we control, but, eh, whatever." [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00059.html [2] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00063.html -- OLPC Branding -- An earlier project of the Art Team, reported back at the time in Fedora Weekly News, to create a secondary mark for Fedora derivatives came to fruition: OLPC has started to use it for Sugar and Paul Frields asked[1] for a guidelines compliance check on @fedora-art and M?ir?n Duffy approved[2] it. This is the first known use of the secondary trademark. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00070.html [2] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00072.html -- A Fedora Promo Video (Beta) -- Mar?a Leandro posted[1] on @fedora-art a video experiment she's working on "I'm working on some videos that can be used on events or some clips. This is the first beta (well... 2nd) and is an easy animation on blender with the 'infinite' and the 'four f's' messages. The idea came up because in LatinAmerica there's an event, FLISoL (installfest) and it was a good idea to have 'something' on the big screen when the Fedora-Team is giving some information, media and stickers" and followed quickly[2] with an improved version. WARNING: the video[3] is available in the "evil" Flash format. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00074.html [2] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00082.html [3] http://www.youtube.com/watch?v=ci2DhmjqWt0 -- Security Advisories -- In this section, we cover Security Advisories from fedora-package-announce. https://www.redhat.com/mailman/listinfo/fedora-package-announce Contributing Writer: David Nalley -- Fedora 10 Security Advisories -- * dbus-1.2.6-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00209.html * squirrelmail-1.4.17-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00232.html * clamav-0.94.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00308.html * syslog-ng-2.0.10-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00397.html * java-1.6.0-openjdk-1.6.0.0-7.b12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00444.html * awstats-6.8-3.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00495.html * vinagre-2.24.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00503.html * cups-1.3.9-4.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00562.html * gallery2-2.3-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00781.html * drupal-6.7-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00806.html * roundcubemail-0.2-4.beta.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00817.html * phpMyAdmin-3.1.1-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00830.html -- Fedora 9 Security Advisories -- * squirrelmail-1.4.17-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00223.html * syslog-ng-2.0.10-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00237.html * java-1.6.0-openjdk-1.6.0.0-0.20.b09.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00384.html * dbus-1.2.6-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00436.html * vinagre-0.5.2-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00473.html * awstats-6.8-3.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00509.html * cups-1.3.9-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00581.html * phpMyAdmin-3.1.1-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00757.html * drupal-6.7-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00767.html * roundcubemail-0.2-4.beta.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00802.html * gallery2-2.3-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00832.html -- Fedora 8 Security Advisories -- Fedora 8 is nearing EOL Per FESCo support for Fedora 8 will be discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html * squirrelmail-1.4.17-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00449.html * syslog-ng-2.0.10-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00450.html * awstats-6.8-3.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00480.html * vinagre-0.4-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00485.html * cups-1.3.9-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00595.html * drupal-5.13-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00740.html * roundcubemail-0.2-4.beta.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00783.html * phpMyAdmin-3.1.1-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00784.html * gallery2-2.3-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00794.html -- Libvirt List -- This section contains the discussion happening on the libvir-list. -- sVirt 0.20 Patch Request for Comments -- James Morris announced[1] "the release of v0.20[2] of sVirt, a project to add security labeling support to Linux-based virtualization. I'm hoping to be able to propose an initial version for upstream merge within the next few minor releases, tasks for which are being scoped out in the new TODO list[3]." "If the current release passes review, the next major task will be to add dynamic MCS labeling of domains and disk images for simple isolation." Daniel P. Berrange said "this patch all looks pretty good to me from a the point of view of libvirt integration & XML config representation." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00260.html [2] http://fedoraproject.org/wiki/FWN/Issue149#sVirt_Initial_Prototype_Release [3] http://selinuxproject.org/page/SVirt/TODO -- Latest libvirt on RHEL and CentOS 5.2 -- Marco Sinhoreli needed[1] image:Echo-package-16px.pnglibvirt 0.5.x for testing oVirt on RHEL 5.2. Marco wondered what was necessary to update from the 0.3.x version available for RHEL. Soon after, Daniel P. Berrange "uploaded[2] a set of patches[3] which make libvirt 0.5.1 work with RHEL-5's version of Xen. Basically we have to tweak a few version assumptions to take account of fact that RHEL-5 Xen has a number of feature backports like the new paravirt framebuffer and NUMA support." "Of course running a newer libvirt on RHEL-5 is totally unsupported but hopefully these will be usful to those who absolutely need this newer libvirt and don't mind about lack of support." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00218.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00298.html [3] http://berrange.fedorapeople.org/libvirt-rhel5-xen/ -- oVirt Devel List -- This section contains the discussion happening on the ovirt-devel list. -- Building oVirt from Rawhide -- Perry Myers posted[1] instructions for building[2] and installing[3] oVirt from rawhide. [1] http://www.redhat.com/archives/ovirt-devel/2008-December/msg00127.html [2] http://ovirt.org/rawhide-build-instructions.html [3] http://ovirt.org/rawhide-install-instructions.html --- end Fedora Weekly News #156 --- Pascal Calarco https://fedoraproject.org/wiki/User:Pcalarco From mspevack at redhat.com Mon Dec 15 18:33:40 2008 From: mspevack at redhat.com (Max Spevack) Date: Mon, 15 Dec 2008 19:33:40 +0100 (CET) Subject: Fedora Weekly News # 156 In-Reply-To: <4946A212.10607@nd.edu> References: <4946A212.10607@nd.edu> Message-ID: > -- Planet Fedora -- > > Contributing Writer: Adam Batkin I love the new Planet Beat. Good job, Adam! --Max From stickster at gmail.com Wed Dec 17 02:55:29 2008 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 16 Dec 2008 21:55:29 -0500 Subject: Ad policy Message-ID: <20081217025529.GA27797@localhost.localdomain> Hello FWN editors, When I hooked you up with the folks from Red Hat's training sales group, it was with the best of intentions. Naturally, the people who are interested in Fedora are probably also interested in Linux training, and that probably means Red Hat certification too. Having them advertise an offer that directly benefited part of our global community and rewarded them for their work in free software seemed like a no-brainer to me. I brought that idea here to the FWN editors, openly and publicly in the Fedora way, and left the decision with you. However, I realize now that some community members might see running that ad as a strange entanglement between Red Hat and Fedora. While I may not agree with that viewpoint, I can understand it. The FWN goes out on our mailing lists, and if we allowed unrestricted ads elsewhere on the mailing lists, assuming anyone wanted to run such ads, it would undoubtedly upset a lot of people. However, if FWN had a clear ad policy, that might help alleviate such concerns in the future. I think the FWN editorial staff should talk with their contributors here, and decide on some sort of advertisement policy for the FWN. I'm not here to dictate that policy to you, because you're the ones who make FWN happen every week. It's a very important service to the community, and one I and many other community members make use of regularly. We're very grateful for your efforts, and I think you're the best judges of how to handle this matter. If you have any questions, I remain on this list, as always, and I'm happy to help. Thanks, and I apologize for the bother. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mspevack at redhat.com Wed Dec 17 15:48:07 2008 From: mspevack at redhat.com (Max Spevack) Date: Wed, 17 Dec 2008 16:48:07 +0100 (CET) Subject: Ad policy In-Reply-To: <20081217025529.GA27797@localhost.localdomain> References: <20081217025529.GA27797@localhost.localdomain> Message-ID: On Tue, 16 Dec 2008, Paul W. Frields wrote: > However, if FWN had a clear ad policy, that might help alleviate such > concerns in the future. I think the FWN editorial staff should talk > with their contributors here, and decide on some sort of advertisement > policy for the FWN. I'm not here to dictate that policy to you, > because you're the ones who make FWN happen every week. It's a very > important service to the community, and one I and many other community > members make use of regularly. We're very grateful for your efforts, > and I think you're the best judges of how to handle this matter. How about "Only ads from sponsors[1], and then subject to edtiorial approval." [1] http://fedoraproject.org/en/sponsors From oisinfeeley at imapmail.org Wed Dec 17 19:04:19 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Wed, 17 Dec 2008 14:04:19 -0500 Subject: Ad policy In-Reply-To: <20081217025529.GA27797@localhost.localdomain> References: <20081217025529.GA27797@localhost.localdomain> Message-ID: <1229540659.4045.1290593621@webmail.messagingengine.com> On Tue, 16 Dec 2008 21:55:29 -0500, "Paul W. Frields" said: [snip introduction detailing how FWN#156 came to run an advertisement] > However, I realize now that some community members might see running > that ad as a strange entanglement between Red Hat and Fedora. While I > may not agree with that viewpoint, I can understand it. The FWN goes > out on our mailing lists, and if we allowed unrestricted ads elsewhere > on the mailing lists, assuming anyone wanted to run such ads, it would > undoubtedly upset a lot of people. I hope no one has actually complained. We ran the ad because it is of direct and immediate interest to a large class of Fedora users (whom I hope read FWN), those who are interested in Fedora as a chance to become acquainted with technologies which may be in future Red Hat releases. So, to me it's definitely news and relevant to the Fedora Project. > However, if FWN had a clear ad policy, that might help alleviate such > concerns in the future. I think the FWN editorial staff should talk > with their contributors here, and decide on some sort of advertisement > policy for the FWN. A policy is a good idea so that all potential viewpoints can be discussed before any crisis and we can't be accused of making inconsistent decisions or practicing some sort of favoritism. I'll offer my simple (probably simplistic) perspective and I hope that the other Beat writers will contribute theirs: * Ads should cohere with the goals of the Fedora Project: promoting freedom and openness i.e. we would not be interested in discounts on non-Free software or training to use non-Free software. * We should not accept money for advertisements in order to maintain our independence. * Ads should offer tangible, immediate benefits to Fedora Project members as long as the other conditions are met. So, for example, if LPI wished to offer a discount to Fedora Project members we would run that too as it is likely to be of material benefit to many members and does not promote non-Free software and is distribution neutral. * Other Operating Systems or distributions are not of interest unless they are derivatives of Fedora. i.e. RHEL, Yellow Dog, BLAG, Aurora, MythDora I'm not sure about hypothetical situations involving non-OS-specific discounts, say for example the FSF or EFF wished to extend some offer to GNU/Linux users in general. I think that should not be a problem unless it were to turn out in the future that more than, say, 20% of our content was advertisements. That seems highly unlikely though. Best wishes, -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From dlbewley at lib.ucdavis.edu Thu Dec 18 04:44:53 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 17 Dec 2008 20:44:53 -0800 (PST) Subject: No Virt beat Message-ID: <1099983942.1063661229575493795.JavaMail.root@zebra.lib.ucdavis.edu> Im away from home due to family illness. Im unlikely to be able to contribute to the next 2 fwn. Certainly not this one. I should be back home and online after new years. sorry From oisinfeeley at imapmail.org Thu Dec 18 11:53:47 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Thu, 18 Dec 2008 06:53:47 -0500 Subject: No Virt beat In-Reply-To: <1099983942.1063661229575493795.JavaMail.root@zebra.lib.ucdavis.edu> References: <1099983942.1063661229575493795.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <1229601227.18221.1290722957@webmail.messagingengine.com> On Wed, 17 Dec 2008 20:44:53 -0800 (PST), "Dale Bewley" said: > Im away from home due to family illness. Im unlikely to be able to > contribute to the next 2 fwn. Certainly not this one. I should be back > home and online after new years. sorry Dale, Sorry to hear about the problems and thanks for the advance notice. Happy Holidays to you and yours, -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From mspevack at redhat.com Thu Dec 18 13:40:28 2008 From: mspevack at redhat.com (Max Spevack) Date: Thu, 18 Dec 2008 14:40:28 +0100 (CET) Subject: is fwn taking a holiday vacation Message-ID: Is FWN going to take vacation on the 29th and 5th? I for one will not be able to write my beats those weeks. This week's beat will be my last until after the new year. --Max From stickster at gmail.com Thu Dec 18 14:09:13 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 18 Dec 2008 09:09:13 -0500 Subject: is fwn taking a holiday vacation In-Reply-To: References: Message-ID: <20081218140913.GE29049@localhost.localdomain> B1;1704;0cOn Thu, Dec 18, 2008 at 02:40:28PM +0100, Max Spevack wrote: > Is FWN going to take vacation on the 29th and 5th? > > I for one will not be able to write my beats those weeks. This week's > beat will be my last until after the new year. In previous years I think FWN has always had a holiday break. It's entirely up to you editors -- if you feel like this is a good chance to take a break and relax, that's an entirely reasonable option. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From oisinfeeley at imapmail.org Thu Dec 18 14:25:10 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Thu, 18 Dec 2008 09:25:10 -0500 Subject: is fwn taking a holiday vacation In-Reply-To: <20081218140913.GE29049@localhost.localdomain> References: <20081218140913.GE29049@localhost.localdomain> Message-ID: <1229610310.18547.1290743583@webmail.messagingengine.com> On Thu, 18 Dec 2008 09:09:13 -0500, "Paul W. Frields" said: > B1;1704;0cOn Thu, Dec 18, 2008 at 02:40:28PM +0100, Max Spevack wrote: > > Is FWN going to take vacation on the 29th and 5th? > > > > I for one will not be able to write my beats those weeks. This week's > > beat will be my last until after the new year. > > In previous years I think FWN has always had a holiday break. It's > entirely up to you editors -- if you feel like this is a good chance > to take a break and relax, that's an entirely reasonable option. I intend this week's issue (#157 covering Dec 14th to 21st) to be my last before the holiday break. I would like to resume on January 11th (#158 covering the week Jan 4th to 10th). Does that sound acceptable to everyone? Happy Holidays, -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From oisinfeeley at imapmail.org Thu Dec 18 14:30:08 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Thu, 18 Dec 2008 09:30:08 -0500 Subject: Ad policy In-Reply-To: References: <20081217025529.GA27797@localhost.localdomain> Message-ID: <1229610608.19469.1290745319@webmail.messagingengine.com> On Wed, 17 Dec 2008 16:48:07 +0100 (CET), "Max Spevack" said: > On Tue, 16 Dec 2008, Paul W. Frields wrote: > > > However, if FWN had a clear ad policy, that might help alleviate such > > concerns in the future. I think the FWN editorial staff should talk > > with their contributors here, and decide on some sort of advertisement > > policy for the FWN. I'm not here to dictate that policy to you, > > because you're the ones who make FWN happen every week. It's a very > > important service to the community, and one I and many other community > > members make use of regularly. We're very grateful for your efforts, > > and I think you're the best judges of how to handle this matter. > > How about "Only ads from sponsors[1], and then subject to edtiorial > approval." > > [1] http://fedoraproject.org/en/sponsors I don't like the idea of running with sponsor's ads to be honest. I think it potentially compromises our integrity as a news source. I'm not dead set against it however, so if everyone else feels I'm being foolish then speak out. I just don't like the implicit pressure that would come with that. It's what has managed to destroy an otherwise free press in many countries. -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From mspevack at redhat.com Thu Dec 18 14:34:16 2008 From: mspevack at redhat.com (Max Spevack) Date: Thu, 18 Dec 2008 15:34:16 +0100 (CET) Subject: is fwn taking a holiday vacation In-Reply-To: <1229610310.18547.1290743583@webmail.messagingengine.com> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> Message-ID: On Thu, 18 Dec 2008, Oisin Feeley wrote: > Does that sound acceptable to everyone? perfection From mspevack at redhat.com Thu Dec 18 14:35:24 2008 From: mspevack at redhat.com (Max Spevack) Date: Thu, 18 Dec 2008 15:35:24 +0100 (CET) Subject: Ad policy In-Reply-To: <1229610608.19469.1290745319@webmail.messagingengine.com> References: <20081217025529.GA27797@localhost.localdomain> <1229610608.19469.1290745319@webmail.messagingengine.com> Message-ID: On Thu, 18 Dec 2008, Oisin Feeley wrote: > I don't like the idea of running with sponsor's ads to be honest. I > think it potentially compromises our integrity as a news source. I'm > not dead set against it however, so if everyone else feels I'm being > foolish then speak out. I just don't like the implicit pressure that > would come with that. It's what has managed to destroy an otherwise > free press in many countries. Fair enough. :) --Max From pcalarco at nd.edu Thu Dec 18 14:35:42 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Thu, 18 Dec 2008 09:35:42 -0500 Subject: is fwn taking a holiday vacation In-Reply-To: <1229610310.18547.1290743583@webmail.messagingengine.com> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> Message-ID: <494A5FBE.7070903@nd.edu> Oisin Feeley wrote: > On Thu, 18 Dec 2008 09:09:13 -0500, "Paul W. Frields" > said: >> B1;1704;0cOn Thu, Dec 18, 2008 at 02:40:28PM +0100, Max Spevack wrote: >>> Is FWN going to take vacation on the 29th and 5th? >>> >>> I for one will not be able to write my beats those weeks. This week's >>> beat will be my last until after the new year. >> In previous years I think FWN has always had a holiday break. It's >> entirely up to you editors -- if you feel like this is a good chance >> to take a break and relax, that's an entirely reasonable option. > > I intend this week's issue (#157 covering Dec 14th to 21st) to be my > last before the holiday break. > > I would like to resume on January 11th (#158 covering the week Jan 4th > to 10th). > > Does that sound acceptable to everyone? A very good suggestion, and I concur with Oisin regarding the timeframe to resume FWN. A Merry Christmas, Hanukkah, Kwanzaa amd winter solitice to you all! - pascal > Happy Holidays, > -- > Oisin Feeley > http://fedoraproject.org/wiki/OisinFeeley From nicu_fedora at nicubunu.ro Thu Dec 18 14:36:12 2008 From: nicu_fedora at nicubunu.ro (Nicu Buculei) Date: Thu, 18 Dec 2008 16:36:12 +0200 Subject: is fwn taking a holiday vacation In-Reply-To: <1229610310.18547.1290743583@webmail.messagingengine.com> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> Message-ID: <494A5FDC.8010807@nicubunu.ro> Oisin Feeley wrote: > > I intend this week's issue (#157 covering Dec 14th to 21st) to be my > last before the holiday break. > > I would like to resume on January 11th (#158 covering the week Jan 4th > to 10th). > > Does that sound acceptable to everyone? I was intending to bring this myself... I won't be online either in the next two weeks, so after #157 the last day when I am available this year is 24 December. In conclusion, I am for a short vacancy. Do not forget to announce it in the welcome part of #157 -- nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com Cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/ Open Clip Art Library: http://www.openclipart.org my Fedora stuff: http://fedora.nicubunu.ro From jmtaylor90 at gmail.com Thu Dec 18 14:53:17 2008 From: jmtaylor90 at gmail.com (Jason Taylor) Date: Thu, 18 Dec 2008 09:53:17 -0500 Subject: is fwn taking a holiday vacation In-Reply-To: <1229610310.18547.1290743583@webmail.messagingengine.com> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> Message-ID: <1229611997.4917.4.camel@localhost.localdomain> On Thu, 2008-12-18 at 09:25 -0500, Oisin Feeley wrote: > On Thu, 18 Dec 2008 09:09:13 -0500, "Paul W. Frields" > said: > > B1;1704;0cOn Thu, Dec 18, 2008 at 02:40:28PM +0100, Max Spevack wrote: > > > Is FWN going to take vacation on the 29th and 5th? > > > > > > I for one will not be able to write my beats those weeks. This week's > > > beat will be my last until after the new year. > > > > In previous years I think FWN has always had a holiday break. It's > > entirely up to you editors -- if you feel like this is a good chance > > to take a break and relax, that's an entirely reasonable option. > > I intend this week's issue (#157 covering Dec 14th to 21st) to be my > last before the holiday break. > > I would like to resume on January 11th (#158 covering the week Jan 4th > to 10th). > > Does that sound acceptable to everyone? > > Happy Holidays, Sounds good to me. Happy Holidays! -Jason -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Thu Dec 18 16:04:28 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 18 Dec 2008 11:04:28 -0500 Subject: is fwn taking a holiday vacation In-Reply-To: <1229610310.18547.1290743583@webmail.messagingengine.com> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> Message-ID: <20081218160428.GJ29049@localhost.localdomain> On Thu, Dec 18, 2008 at 09:25:10AM -0500, Oisin Feeley wrote: > > On Thu, 18 Dec 2008 09:09:13 -0500, "Paul W. Frields" > said: > > B1;1704;0cOn Thu, Dec 18, 2008 at 02:40:28PM +0100, Max Spevack wrote: > > > Is FWN going to take vacation on the 29th and 5th? > > > > > > I for one will not be able to write my beats those weeks. This week's > > > beat will be my last until after the new year. > > > > In previous years I think FWN has always had a holiday break. It's > > entirely up to you editors -- if you feel like this is a good chance > > to take a break and relax, that's an entirely reasonable option. > > I intend this week's issue (#157 covering Dec 14th to 21st) to be my > last before the holiday break. > > I would like to resume on January 11th (#158 covering the week Jan 4th > to 10th). > > Does that sound acceptable to everyone? Once there's a decision -- and it seems pretty well along at this point -- it would probably make sense to send an announcement to the same lists that receive the FWN, stating the plans. Happy holidays everyone! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mspevack at redhat.com Thu Dec 18 20:01:41 2008 From: mspevack at redhat.com (Max Spevack) Date: Thu, 18 Dec 2008 21:01:41 +0100 (CET) Subject: is fwn taking a holiday vacation In-Reply-To: <20081218160428.GJ29049@localhost.localdomain> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> <20081218160428.GJ29049@localhost.localdomain> Message-ID: On Thu, 18 Dec 2008, Paul W. Frields wrote: > Once there's a decision -- and it seems pretty well along at this > point -- it would probably make sense to send an announcement to the > same lists that receive the FWN, stating the plans. Happy holidays > everyone! Why not just include it at the top of the next issue, which is the last of the year, and spare people the extra email? --Max From stickster at gmail.com Thu Dec 18 20:48:12 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 18 Dec 2008 15:48:12 -0500 Subject: is fwn taking a holiday vacation In-Reply-To: References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> <20081218160428.GJ29049@localhost.localdomain> Message-ID: <20081218204812.GJ5958@localhost.localdomain> On Thu, Dec 18, 2008 at 09:01:41PM +0100, Max Spevack wrote: > On Thu, 18 Dec 2008, Paul W. Frields wrote: > >> Once there's a decision -- and it seems pretty well along at this >> point -- it would probably make sense to send an announcement to the >> same lists that receive the FWN, stating the plans. Happy holidays >> everyone! > > Why not just include it at the top of the next issue, which is the last > of the year, and spare people the extra email? Sold! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From runab at fedoraproject.org Fri Dec 19 04:15:18 2008 From: runab at fedoraproject.org (Runa Bhattacharjee) Date: Fri, 19 Dec 2008 09:45:18 +0530 Subject: is fwn taking a holiday vacation In-Reply-To: <1229610310.18547.1290743583@webmail.messagingengine.com> References: <20081218140913.GE29049@localhost.localdomain> <1229610310.18547.1290743583@webmail.messagingengine.com> Message-ID: <494B1FD6.3070409@fedoraproject.org> Oisin Feeley wrote: > > I would like to resume on January 11th (#158 covering the week Jan 4th > to 10th). > > Does that sound acceptable to everyone? Aye from the Translation Beat. However I would be around during most of the holiday period, so if any pending housekeeping work needs to be done, I am all for it. Have a nice and safe holiday break everyone. regards Runa From mspevack at redhat.com Fri Dec 19 10:50:36 2008 From: mspevack at redhat.com (Max Spevack) Date: Fri, 19 Dec 2008 11:50:36 +0100 (CET) Subject: announcements beat Message-ID: Only one announcement, so I added that in. If something interesting happens on Friday or Saturday, I'll add that too. I also put the holiday notice at the top of the announcements beat. --Max From oisinfeeley at imapmail.org Mon Dec 22 16:53:03 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 22 Dec 2008 11:53:03 -0500 Subject: FWN#157 Message-ID: <1229964783.4886.1291345863@webmail.messagingengine.com> Pascal, Huzaifa I seem to have forgotten to sign my Fedora CLA and as a result can't log in to the wiki to make changes. Could one of you guys take care of this week's FWN. I attach my edited Developments beat and also inline below. Things are a bit hectic here with snow removal. I'm going to try and get a fax of the CLA off to Red Hat (I could swear I've already done this, but whatever) but probably I won't be able to log in for a bit. Apologies and Happy Holidays! === Nautilus Spatial-mode Flamewar === The tired, old topic of whether nautilus should use "spatial-mode" as a default was re-opened[1] by MarkG85 in the form of a request for list subscribers to "vote" on the mailing list for a reversion to "browser-mode". In spatial-mode nautilus opens a new window for each directory unless one middle-clicks or holds the shift key down. It was pointed out by several contributors that voting "+/- 1" was not a recognized way to achieve change within the Fedora Project. [[ChrisAdams|Chris Adams]] asked[2] if he and his friends "[...] should [...] all spam fedora-devel with `+1' and `metoo' to change the default background color? What if it is 20 friends, or 100, or 500?" A similar point was made[3] by [[JeffSpaleta|Jef Spaleta]]. [[DimiPaun|Dimi Paun]] expressed[4] frustration with what he charcaterized as "lame community involvenment" and several personal attacks were made on both the maintainer and other contributors who had deprecated the attempt to take a mailing list vote. After tempers had flared Jeff commented[5]: "Noone has figured out how to write a markup language for human intention...and as a result any passionate discussion degrades severely as we are wired to read intention but without body language and vocal ques...we absolutely do it wrong when relying solely on written language. Even more so with English! If we mandated everyone encode thought into Lisp we'd be having more constructive discussions (and less of them). The productivity of the list would be through the roof." In response to a challenge to detail some advantages of spatial-mode [[TomasTorcz|Tomas Torcz]] was among those who offered[6] that the persistent screen placement of directory windows was a major advantage. He also suggested a way to avoid leaving multiple windows open: "When I open new window and don't want parent directory open, I just open with middle button. Some people prefer Shift+click in this situation. I never has to use `Close all parent folder' (ctrlshift-w), but I aware it exist." [[JoonasSaraj?rvi|Joonas Saraj?rvi]] confirmed[7] the persistence as an advantage: "[...] the state of each folder is persistent. Every window opens in the same view that it had when I reopen them. I can have appropriate zoom levels and views for every directory I commonly use." Very much later in the thread, after he had been referred to several times, the package maintainer [[AlexanderLarsson|Alexander Larsson]] replied[8] that he was unconvinced both by the tone and content of the argument that there was a case to be made for changing the default. It is possible to choose which behavior one wants by at least two methods. One can either use the GUI 
Nautilus -> Preferences -> Behavior -> Always open in browser
windows
or else change the GConf setting using gconftool-2 --type boolean --set /apps/nautilus/preferences/always_use_browser true As part of the argument involved a desire to be able to replicate these settings automatically and possibly distribute them to others [[MatthiasClasen|Matthias Clasen]] suggested[9] that anyone wishing to make permanent change to the default settings could create a sabayon profile. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02089.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02286.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02305.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02416.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02392.html [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02387.html [7] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02213.html [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02189.html [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02389.html === Font Package Naming Guidelines === [[NicolasMailhot|Nicholas Mailhot]] ensured[1] that everyone was made aware of the new font package naming rules for Fedora 11. These will help break up large font packages in order to allow users to obtain fonts from desired families without imposing a large download burden. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02597.html === How to become a Co-Maintainer === [[RayVanDolson|Ray Van Dolson]] asked[1] for some information on identifying the current (co)maintainers of the proftpd package, the procedure to become a co-maintainer and the abilities to push bugfixes which this would confer upon him if the primary maintainer were absent. A full answer was provided[2] by [[PatriceDumas|Patrice Dumas]] with links to PackageDB and the policies on the wiki regarding non-responsive maintainers. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02253.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02255.html === Proposed Package Re-Naming Guidelines === Feedback was requested[1] by [[KevinFenzi|Kevin Fenzi]] on a draft guideline concerning the re-naming of packages either as a result of upstream action or locally to adhere to the [[NamingGuidelines]]. [[PatriceDumas|Patrice Dumas]] and [[DennisGilmore|Dennis Gilmore]] remembered[2] that a re-review followed by EOL of the old package was the current practice. [[JasonTibbitts|Jason Tibbitts]][3] and [[JesseKeating|Jesse Keating]][4] referenced IRC discussions of the practice and its advantages in checking the Obsoletes and Provides in discussion with [[JochenSchmitt|Jochen Schmitt.]] Jochen was concerned[5] that the process be kept lightweight as opposed to a full review. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02052.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02054.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02058.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02056.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02060.html === Exiv2 Bump in Rawhide === [[RexDieter|Rex Dieter]] announced[1] that a bump to exiv2-0.18[2] would occur soon including a soname bump. [[JonCiesla|Jon Ciesla]] offered to help and Rex produced[3] a quick list of dependent applications. When [[MatejCepl|Matej Cepl]] struggled with some odd results [[MichaelJChudobiak|Michael Chudobiak]] answered[4] that the API had changed a good deal. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02061.html [2] Exiv is a command-line utility for examining EXIF and IPTC metadata of images. [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02068.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02244.html === wxGTK2 to wxGTK Re-name == [[MichaelSchwendt|Michael Schwendt]] discovered[1] that a rename had been performed[2] some time ago so that there was no wxGTK2-devel package available. [[DanHor?k|Dan Hor?k]] explained[3] that only audacity was affected. There was[4] some discussion about whether versioned Provides should be kept indefinitely. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01897.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01972.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01975.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02046.html === RFC: Description Text in Packages === Follow-up action (see FWN#153[1]) was requested[2] by [[RichardHughes|Richard Hughes]] for packagers to fix "isane descriptions" in their package summary text. Enlightenment was singled out as an example of an undesirable multi-page description. Richard also asked for comments on how bullet-points should be represented and the use of UTF-8. A heated discussion followed[3] in which [[NicolasMailhot|Nicolas Mailhot]] deprecated the possible development of a "broken application-side transcoding system". He advocated the use of UTF-8 over ASCII for several reasons including supporting the default Asian locales. Paragraph boundaries and lists were also mentioned[4] as a special area of concern. This is a long and painful thread to read which expresses a conflict between constraints imposed by PackageKit and how things are currently done. Packagers should probably skim it to determine what final decisions are going to be made. [[RichardHughes|Richard Hughes]] seemed[5] to decide to implement what seemed to him to be sane changes to gnome-packagekit in which "If you're [g]oing to use [UTF-8 representations of skull-and-crossbones and radiation-hazard symbols] in a spec file, then the text box is going to look rubbish and be all on one line. If you use a description longer than a few hundred words, gnome-packagekit will truncate it." [1] http://fedoraproject.org/wiki/FWN/Issue153#RFC:_Fix_Summary_Text_for_Lots_of_Packages [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01550.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01555.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01577.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01927.html -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: all-fwn-157.txt URL: From oisinfeeley at imapmail.org Mon Dec 22 16:59:23 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 22 Dec 2008 11:59:23 -0500 Subject: FWN#157 In-Reply-To: <1229964783.4886.1291345863@webmail.messagingengine.com> References: <1229964783.4886.1291345863@webmail.messagingengine.com> Message-ID: <1229965163.5997.1291347569@webmail.messagingengine.com> On Mon, 22 Dec 2008 11:53:03 -0500, "Oisin Feeley" said: > Pascal, Huzaifa > > I seem to have forgotten to sign my Fedora CLA and as a result can't log > in to the wiki to make changes. Ah. My bad. Everything seems fine now. I think Firefox was caching the password on this machine. I can login now and should be able to do all the necessary. Sorry for the false alarm. -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From pcalarco at nd.edu Mon Dec 22 17:06:13 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 22 Dec 2008 12:06:13 -0500 Subject: FWN#157 In-Reply-To: <1229965163.5997.1291347569@webmail.messagingengine.com> References: <1229964783.4886.1291345863@webmail.messagingengine.com> <1229965163.5997.1291347569@webmail.messagingengine.com> Message-ID: <494FC905.5020004@nd.edu> Hi Oisin -- I've been in meetings this morning, but can help too, if you need. Just let me know. Thanks! - pascal Oisin Feeley wrote: > On Mon, 22 Dec 2008 11:53:03 -0500, "Oisin Feeley" > said: >> Pascal, Huzaifa >> >> I seem to have forgotten to sign my Fedora CLA and as a result can't log >> in to the wiki to make changes. > > Ah. My bad. Everything seems fine now. I think Firefox was caching > the password on this machine. > > I can login now and should be able to do all the necessary. Sorry for > the false alarm. > > -- > Oisin Feeley > http://fedoraproject.org/wiki/OisinFeeley > > _______________________________________________ > Fedora-news-list mailing list > Fedora-news-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-news-list From oisinfeeley at imapmail.org Mon Dec 22 17:36:18 2008 From: oisinfeeley at imapmail.org (Oisin Feeley) Date: Mon, 22 Dec 2008 12:36:18 -0500 Subject: FWN#157 In-Reply-To: <494FC905.5020004@nd.edu> References: <1229964783.4886.1291345863@webmail.messagingengine.com> <1229965163.5997.1291347569@webmail.messagingengine.com> <494FC905.5020004@nd.edu> Message-ID: <1229967378.14588.1291353425@webmail.messagingengine.com> On Mon, 22 Dec 2008 12:06:13 -0500, "Pascal Calarco" said: > Hi Oisin -- > > I've been in meetings this morning, but can help too, if you need. Just > let me know. Thanks! Pascal, If you could send out the mailshot I'd really appreciate it. I've done everything except that. I'd also appreciate it if you could cast your expert eye over the Welcome notice that I hastily cobbled together. It runs the risk of being a bit twee and Western-centric, but I figured that it is in keeping with the theme of the holiday. Best wishes to everyone! Have a well-deserved break: I'm going out to shovel away some more of the huge amount of snow that came down in the Qu?bec area yesterday and is still falling. Otherwise I won't be able to do my very late Xmas shopping! -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley From pcalarco at nd.edu Mon Dec 22 19:45:07 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 22 Dec 2008 14:45:07 -0500 Subject: FWN#157 In-Reply-To: <1229967378.14588.1291353425@webmail.messagingengine.com> References: <1229964783.4886.1291345863@webmail.messagingengine.com> <1229965163.5997.1291347569@webmail.messagingengine.com> <494FC905.5020004@nd.edu> <1229967378.14588.1291353425@webmail.messagingengine.com> Message-ID: <494FEE43.8000800@nd.edu> Okay, back from another meeting; I'll start working on this now. Thanks Oisin! - pascal Oisin Feeley wrote: > On Mon, 22 Dec 2008 12:06:13 -0500, "Pascal Calarco" > said: >> Hi Oisin -- >> >> I've been in meetings this morning, but can help too, if you need. Just >> let me know. Thanks! > > Pascal, > > If you could send out the mailshot I'd really appreciate it. I've done > everything except that. I'd also appreciate it if you could cast your > expert eye over the Welcome notice that I hastily cobbled together. It > runs the risk of being a bit twee and Western-centric, but I figured > that it is in keeping with the theme of the holiday. > > Best wishes to everyone! Have a well-deserved break: I'm going out to > shovel away some more of the huge amount of snow that came down in the > Qu?bec area yesterday and is still falling. Otherwise I won't be able > to do my very late Xmas shopping! From pcalarco at nd.edu Mon Dec 22 19:58:53 2008 From: pcalarco at nd.edu (Pascal Calarco) Date: Mon, 22 Dec 2008 14:58:53 -0500 Subject: Fedora Weekly News #157 Message-ID: <494FF17D.2080800@nd.edu> -- Fedora Weekly News Issue 157 -- Welcome to Fedora Weekly News Issue 157 for the week ending December 21st, 2008. http://fedoraproject.org/wiki/FWN/Issue157 In our last issue of 2008, Announcements reminds you of FWN's holiday schedule and presents the gift of the Omega distro, Planet is chock full of tasty tidbits from the Fedora blogosphere, Developments invites you to warm your hands over a "Nautilus Spatial-mode Flamewar", Documentation invites you to a "Holiday Hackfest", Translations reports on the re-organization of "Sponsors for cvsl10n", Artwork unwraps some shiny "Creation Highlights", SecurityAdvisories lists some ways to avoid a lump of coal from Santa, and the usual sleigh-load of Virtualization goodies includes instructions on "Building oVirt from Rawhide." We would like to thank our readers for their interest and attention and all our contributors for producing the goods week after week. May you all have a happy and relaxing holiday and we look forward to seeing you again in January 2009. If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. We welcome reader feedback: fedora-news-list at redhat.com FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [1] http://fedoraproject.org/wiki/NewsProject/Join -- Announcements -- In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack -- FWN Holiday Break -- Fedora Weekly News will be on vacation for the next two weeks. Our next issue will be published on January 12th. Happy holidays! -- FUDCon Boston 2009 -- FUDCon Boston 2009 is January 9-11. It is not too late to register[1]. [1] https://fedoraproject.org/wiki/FUDCon/FUDConF11 -- Fedora Remixes -- Rahul Sundaram announced[2] the General Availability of Omega 10, "a Linux based operating system and a community Fedora Remix for desktop and laptop users." Sundaram added, "It is a installable Live CD for regular PC (i686 architecture) systems. It has all the features of Fedora 10 and a number of additional multimedia players and codecs. You can play any multimedia including MP3 music or commercial DVD's out of the box." For additional information, and to download Omega or view the kickstart used to create it, please read the full announcement. [2] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00014.html -- Planet Fedora -- In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin -- General -- M?ir?n Duffy said[1] it best: "ZOMG Stickers!!!!11" Rex Dieter announced[2] a new fedora-kde mailing list Harald Hoyer analyzed[3] the Fedora 10 boot process on an EeePC 901 with a solid-state disk, including some easy optimizations Casey Dahlin wrote a series[4,5,6,7] on a new internal state machine driving the Upstart service manager Sankarshan Mukhopadhyay discussed[8] some of the commonly overlooked difficulties of the commonly overlooked process of internationalization (i18n) and localization (l10n) Warren Togami had[9] some problems netbooting old PowerPC Macs as Thin Clients (and is open to suggestions) Tim Waugh posted[10] a tutorial on preventing a Python/GTK+ application from appearing to freeze while performing CUPS operations Abhishek Rane summarized[11] his thoughts on "Best of FOSS and Linux in 2008" Dimitris Glezos described[12] Transifex and their new startup company built around it Christoph Wickert embedded[13] a video interview with Mario Behling talking about LXDE Jef Spaleta offered[14] a number of retrospective questions at the end of his tenure on the Fedora Board S?bastien Bilbeau posted[15] the "25 Best Linux Desktop Customization Screenshots" Yaakov Nemoy mused[16] about the relationship between the Open Source development process and anarchy [1] http://mihmo.livejournal.com/65838.html [2] http://rdieter.livejournal.com/11262.html [3] http://www.harald-hoyer.de/personal/blog/fedora-10-boot-analysis [4] http://screwyouenterpriseedition.blogspot.com/2008/12/new-upstart-state-machine.html [5] http://screwyouenterpriseedition.blogspot.com/2008/12/new-upstart-state-machine-part-2.html [6] http://screwyouenterpriseedition.blogspot.com/2008/12/new-upstart-state-machine-part-3.html [7] http://screwyouenterpriseedition.blogspot.com/2008/12/new-upstart-state-machine-part-4.html [8] http://sankarshan.randomink.org/blog/2008/12/16/and-here-we-go-again-2/ [9] http://wtogami.livejournal.com/29574.html [10] http://cyberelk.net/tim/2008/12/17/cups-gtk-python-and-threading/ [11] http://www.abhishekrane.com/2008/12/17/best-of-foss-and-linux-in-2008/ [12] http://dimitris.glezos.com/weblog/2008/12/17/chasing-a-dream [13] http://www.christoph-wickert.de/blog/2008/12/18/lxde-presentation-at-red-hat-singapore/ [14] http://jspaleta.livejournal.com/29998.html [15] http://www.tux-planet.fr/25-best-linux-desktop-customization-screenshots/ [16] http://loupgaroublond.blogspot.com/2008/12/open-source-and-anarchism.html -- Events -- Fedora Release Party in Milan[17] Fedora Day at Menoufiya Universty, Egypt[18] [17] http://people.byte-code.com/fcrippa/2008/12/19/fedora-release-party-milan-italy/ [18] http://www.fossology.net/Fedora_Day_at_Menoufiya_Universty_Egypt_release_10 -- Developments -- In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley -- Nautilus Spatial-mode Flamewar -- The tired, old topic of whether nautilus should use "spatial-mode" as a default was re-opened[1] by MarkG85 in the form of a request for list subscribers to "vote" on the mailing list for a reversion to "browser-mode". In spatial-mode nautilus opens a new window for each directory unless one middle-clicks or holds the shift key down. It was pointed out by several contributors that voting "+/- 1" was not a recognized way to achieve change within the Fedora Project. Chris Adams asked[2] if he and his friends "[...] should [...] all spam fedora-devel with `+1' and `metoo' to change the default background color? What if it is 20 friends, or 100, or 500?" A similar point was made[3] by Jef Spaleta. Dimi Paun expressed[4] frustration with what he charcaterized as "lame community involvenment" and several personal attacks were made on both the maintainer and other contributors who had deprecated the attempt to take a mailing list vote. After tempers had flared Jeff commented[5]: "Noone has figured out how to write a markup language for human intention...and as a result any passionate discussion degrades severely as we are wired to read intention but without body language and vocal ques...we absolutely do it wrong when relying solely on written language. Even more so with English! If we mandated everyone encode thought into Lisp we'd be having more constructive discussions (and less of them). The productivity of the list would be through the roof." In response to a challenge to detail some advantages of spatial-mode Tomas Torcz was among those who offered[6] that the persistent screen placement of directory windows was a major advantage. He also suggested a way to avoid leaving multiple windows open: "When I open new window and don't want parent directory open, I just open with middle button. Some people prefer Shift+click in this situation. I never has to use `Close all parent folder' (ctrlshift-w), but I aware it exist." Joonas Saraj?rvi confirmed[7] the persistence as an advantage: "[...] the state of each folder is persistent. Every window opens in the same view that it had when I reopen them. I can have appropriate zoom levels and views for every directory I commonly use." Very much later in the thread, after he had been referred to several times, the package maintainer Alexander Larsson replied[8] that he was unconvinced both by the tone and content of the argument that there was a case to be made for changing the default. It is possible to choose which behavior one wants by at least two methods. One can either use the GUI Nautilus -> Preferences -> Behavior -> Always open in browser windows or else change the GConf setting using gconftool-2 --type boolean --set /apps/nautilus/preferences/always_use_browser true As part of the argument involved a desire to be able to replicate these settings automatically and possibly distribute them to others Matthias Clasen suggested[9] that anyone wishing to make permanent change to the default settings could create a sabayon profile. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02089.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02286.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02305.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02416.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02392.html [6] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02387.html [7] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02213.html [8] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02189.html [9] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02389.html -- Font Package Naming Guidelines -- Nicholas Mailhot ensured[1] that everyone was made aware of the new font package naming rules for Fedora 11. These will help break up large font packages in order to allow users to obtain fonts from desired families without imposing a large download burden. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02597.html -- How to become a Co-Maintainer -- Ray Van Dolson asked[1] for some information on identifying the current (co)maintainers of the proftpd package, the procedure to become a co-maintainer and the abilities to push bugfixes which this would confer upon him if the primary maintainer were absent. A full answer was provided[2] by Patrice Dumas with links to PackageDB and the policies on the wiki regarding non-responsive maintainers. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02253.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02255.html -- Proposed Package Re-Naming Guidelines -- Feedback was requested[1] by Kevin Fenzi on a draft guideline concerning the re-naming of packages either as a result of upstream action or locally to adhere to the NamingGuidelines. Patrice Dumas and Dennis Gilmore remembered[2] that a re-review followed by EOL of the old package was the current practice. Jason Tibbitts[3] and Jesse Keating[4] referenced IRC discussions of the practice and its advantages in checking the Obsoletes and Provides in discussion with Jochen Schmitt. Jochen was concerned[5] that the process be kept lightweight as opposed to a full review. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02052.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02054.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02058.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02056.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02060.html -- Exiv2 Bump in Rawhide -- Rex Dieter announced[1] that a bump to exiv2-0.18[2] would occur soon including a soname bump. Jon Ciesla offered to help and Rex produced[3] a quick list of dependent applications. When Matej Cepl struggled with some odd results Michael Chudobiak answered[4] that the API had changed a good deal. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02061.html [2] Exiv is a command-line utility for examining EXIF and IPTC metadata of images. [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02068.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02244.html -- wxGTK2 to wxGTK Re-name -- Michael Schwendt discovered[1] that a rename had been performed[2] some time ago so that there was no wxGTK2-devel package available. Dan Hor?k explained[3] that only audacity was affected. There was[4] some discussion about whether versioned Provides should be kept indefinitely. [1] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01897.html [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01972.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01975.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02046.html -- RFC: Description Text in Packages -- Follow-up action (see FWN#153[1]) was requested[2] by Richard Hughes for packagers to fix "isane descriptions" in their package summary text. Enlightenment was singled out as an example of an undesirable multi-page description. Richard also asked for comments on how bullet-points should be represented and the use of UTF-8. A heated discussion followed[3] in which Nicolas Mailhot deprecated the possible development of a "broken application-side transcoding system". He advocated the use of UTF-8 over ASCII for several reasons including supporting the default Asian locales. Paragraph boundaries and lists were also mentioned[4] as a special area of concern. This is a long and painful thread to read which expresses a conflict between constraints imposed by PackageKit and how things are currently done. Packagers should probably skim it to determine what final decisions are going to be made. Richard Hughes seemed[5] to decide to implement what seemed to him to be sane changes to gnome-packagekit in which "If you're [g]oing to use [UTF-8 representations of skull-and-crossbones and radiation-hazard symbols] in a spec file, then the text box is going to look rubbish and be all on one line. If you use a description longer than a few hundred words, gnome-packagekit will truncate it." [1] http://fedoraproject.org/wiki/FWN/Issue153#RFC:_Fix_Summary_Text_for_Lots_of_Packages [2] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01550.html [3] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01555.html [4] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01577.html [5] https://www.redhat.com/archives/fedora-devel-list/2008-December/msg01927.html -- Documentation -- In this section, we cover the Fedora Documentation Project. http://fedoraproject.org/wiki/DocsProject Contributing Writer: Jason Taylor -- Holiday Hackfest -- This year there is going to be a Virtual Hackfest[0] with the goal of getting Fedora Documentation Project Guides up to date and ready for publication. Karsten presented a ToDo list[1] this week. The dates for the Hackfest are December 27, 2008 through January 4, 2009. [0] https://fedoraproject.org/wiki/Docs_Project_Holiday_Virtual_Hackfest [1] https://www.redhat.com/archives/fedora-docs-list/2008-December/msg00139.html -- Translation -- This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee -- Sponsors for cvsl10n -- The discussion about reorganizing the cvsl10n sponsorship process was restarted by KarstenWade[1], highlighting the long queue of new entrants waiting for sponsorhip. Currently, the policies governing the sponsorship process for the cvsl10n group do not ensure notification to the language team's co-ordinator of a new entrant, unless informed by the latter. As a result of a precaution taken by the current sponsor against arbitrary approval, the waiting queue has been growing. Suggested changes include, providing all the co-ordinators with sponsorship rights. KarstenWade also suggested the renaming of the admin group to "l10n" instead of "cvsl10n". [1] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00079.html -- Kudos for the Serbian Translation Team and FLP -- OisinFeeley and PaulFrields informed[2] about the prompt work done by the Serbian contributors of the Fedora Localization Project, as part of Serbian Government's initiatives to localize open source software. An article in LWN[3] (available publicly after Dec 25th 2008) says that 99% work of the Fedora Translation was completed on time. [2] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00074.html [3] http://lwn.net/Articles/310740/ -- Transifex Outage -- An unplanned outage of the Transifex instance, on http://translate.fedoraproject.org occurred last week, alongwith koji, wiki and smolt outage[4]. [4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00072.html -- Artwork -- In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei -- Perspective and the Echo Icons -- Martin Sourada called for a decision[1] on @fedora-art "we need to make final decisions about the new perspective to Echo and update the guidelines appropriately" with his proposal being "We will start new Echo Perspective icon theme which will * be developed in parallel to the current Echo * until it reaches good enough coverage, it will fallback to current Echo and gnome-icon-theme * use same Perspective Projection as in tango/mango for 32x32 icons and bigger, and in cases where it helps icon distinction in smaller sizes as well, Flat Perspective will be used for the rest * allow small amount of glows/glazes/shines in 256x256 version to achieve better realistic look * use ~ 1 px thick solid borders at all sizes" [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00109.html -- The FUCCon Boston 2009 T-shirt -- In a message addressed to both @fedora-art and @fedora-marketing M?ir?n Duffy asked for a vote[1] for the design of the official T-Shirt for the upcoming FUDCon in Boston "I made the design two-color so hopefully it'll be cheaper to print [...] There's two main designs that are just different in the treatment of the back portion of the shirt" and the majority of the respondents opted for one of them[2], which at the time of this writing should be already going to print. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00092.html [2] https://fedoraproject.org/w/uploads/1/17/Artwork_T(2d)Shirt_fudcon-boston-2009-1_design.png -- Creation Highlights -- This week a few members of the community shared with @fedora-art some of their latest works: * Mar?a Leandro continued her work[1] on a promo video[2] (warning: streaming Flash content); * Susmit Shannigrahi started[3] a leaflet[4] to be handed at Fedora booths; * Mola Pahnadayan created[5] a cool looking 3D composition Blender, pretty much in his style famous form the Fedora Core 6 DNA wallpaper. [1] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00125.html [2] http://www.youtube.com/watch?v=Od8Utt6anLw [3] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00099.html [4] https://fedoraproject.org/wiki/Image:Leaflet.png [5] https://www.redhat.com/archives/fedora-art-list/2008-December/msg00116.html [6] http://mola-mp.deviantart.com/art/Fedora-10-106577570 -- Security Advisories -- In this section, we cover Security Advisories from fedora-package-announce. https://www.redhat.com/mailman/listinfo/fedora-package-announce Contributing Writer: David Nalley -- Fedora 10 Security Advisories -- * dbus-1.2.6-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00209.html * squirrelmail-1.4.17-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00232.html * clamav-0.94.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00308.html * syslog-ng-2.0.10-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00397.html * java-1.6.0-openjdk-1.6.0.0-7.b12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00444.html * awstats-6.8-3.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00495.html * vinagre-2.24.2-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00503.html * cups-1.3.9-4.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00562.html * gallery2-2.3-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00781.html * drupal-6.7-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00806.html * roundcubemail-0.2-4.beta.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00817.html * phpMyAdmin-3.1.1-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00830.html -- Fedora 9 Security Advisories -- * squirrelmail-1.4.17-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00223.html * syslog-ng-2.0.10-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00237.html * java-1.6.0-openjdk-1.6.0.0-0.20.b09.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00384.html * dbus-1.2.6-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00436.html * vinagre-0.5.2-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00473.html * awstats-6.8-3.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00509.html * cups-1.3.9-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00581.html * phpMyAdmin-3.1.1-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00757.html * drupal-6.7-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00767.html * roundcubemail-0.2-4.beta.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00802.html * gallery2-2.3-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00832.html -- Fedora 8 Security Advisories -- Fedora 8 is nearing EOL Per FESCo support for Fedora 8 will be discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html * squirrelmail-1.4.17-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00449.html * syslog-ng-2.0.10-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00450.html * awstats-6.8-3.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00480.html * vinagre-0.4-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00485.html * cups-1.3.9-2.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00595.html * drupal-5.13-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00740.html * roundcubemail-0.2-4.beta.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00783.html * phpMyAdmin-3.1.1-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00784.html * gallery2-2.3-1.fc8 - https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00794.html -- Virtualization -- In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley -- Libvirt List -- This section contains the discussion happening on the libvir-list. -- sVirt 0.20 Patch Request for Comments -- James Morris announced[1] "the release of v0.20[2] of sVirt, a project to add security labeling support to Linux-based virtualization. I'm hoping to be able to propose an initial version for upstream merge within the next few minor releases, tasks for which are being scoped out in the new TODO list[3]." "If the current release passes review, the next major task will be to add dynamic MCS labeling of domains and disk images for simple isolation." Daniel P. Berrange said "this patch all looks pretty good to me from a the point of view of libvirt integration & XML config representation." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00260.html [2] http://fedoraproject.org/wiki/FWN/Issue149#sVirt_Initial_Prototype_Release [3] http://selinuxproject.org/page/SVirt/TODO -- Latest libvirt on RHEL and CentOS 5.2 -- Marco Sinhoreli needed[1] image:Echo-package-16px.pnglibvirt 0.5.x for testing oVirt on RHEL 5.2. Marco wondered what was necessary to update from the 0.3.x version available for RHEL. Soon after, Daniel P. Berrange "uploaded[2] a set of patches[3] which make libvirt 0.5.1 work with RHEL-5's version of Xen. Basically we have to tweak a few version assumptions to take account of fact that RHEL-5 Xen has a number of feature backports like the new paravirt framebuffer and NUMA support." "Of course running a newer libvirt on RHEL-5 is totally unsupported but hopefully these will be usful to those who absolutely need this newer libvirt and don't mind about lack of support." [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00218.html [2] http://www.redhat.com/archives/libvir-list/2008-December/msg00298.html [3] http://berrange.fedorapeople.org/libvirt-rhel5-xen/ -- oVirt Devel List -- This section contains the discussion happening on the ovirt-devel list. -- Building oVirt from Rawhide -- Perry Myers posted[1] instructions for building[2] and installing[3] oVirt from rawhide. --- end FWN 157 --- From panneerselvamit34 at gmail.com Wed Dec 31 12:15:44 2008 From: panneerselvamit34 at gmail.com (panneer selvam) Date: Wed, 31 Dec 2008 17:45:44 +0530 Subject: (no subject) Message-ID: <108832860812310415j15d49056w936eb019c3f7e257@mail.gmail.com> iam panneer linux book -------------- next part -------------- An HTML attachment was scrubbed... URL: From allen.jaloola at gmail.com Wed Dec 31 19:32:57 2008 From: allen.jaloola at gmail.com (Allen Zhu) Date: Wed, 31 Dec 2008 11:32:57 -0800 Subject: (no subject) In-Reply-To: <108832860812310415j15d49056w936eb019c3f7e257@mail.gmail.com> References: <108832860812310415j15d49056w936eb019c3f7e257@mail.gmail.com> Message-ID: Huh? Please don't spam. Thanks... Allen On 12/31/08, panneer selvam wrote: > iam panneer linux book > _______________________________________________ > Fedora-news-list mailing list > Fedora-news-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-news-list > >