Re: BTRFS as default in F17?
On Tue, Jan 24, 2012 at 12:04 AM, Peter Robinson wrote: > On Mon, Jan 23, 2012 at 10:56 PM, Greg wrote: >> will BTRFS be default in F17? going by a story posted on Phoronix there's >> likely to be a fsck next month? >> http://www.phoronix.com/scan.php?page=news_item&px=MTA0Njk > > I've heard that for months now. It's also post alpha and feature > freeze so I very much doubt it. We are not post feature freeze ... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
new hardware, more problems
Hi! Some may remember I was struggling with my old (but faithful) T60 and rawhide because of poor performance and increased heat. I have therefore upgraded my hardware (more CPUs, more RAM) and have hit a lot of new annoying to critical bugs with rawhide. Not sure what was the culprit I tried F16 and experienced the same plague (missing icons, ACPI making the machine hang, screensaver locks-up, etc,). So I'd like to know whether it's better to run F16 or rawhide/F17 to report and try to address those bugs? Thanks. Fred -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 Nightlies & Nouveau
On 24/01/2012 3:30 PM, Greg wrote: can anyone boot the Nightlies using Nvidia? when trying to boot it spits out a lot of DRM Nouveau errors ( F16 boots fine ) i have found a similar Bug but from F14. https://bugzilla.redhat.com/show_bug.cgi?id=641387 my Nvidia card being a 550ti 1Gig -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F17 Nightlies & Nouveau
can anyone boot the Nightlies using Nvidia? when trying to boot it spits out a lot of DRM Nouveau errors ( F16 boots fine ) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: BTRFS as default in F17?
On Mon, Jan 23, 2012 at 11:56 PM, Greg wrote: > will BTRFS be default in F17? going by a story posted on Phoronix there's > likely to be a fsck next month? > http://www.phoronix.com/scan.php?page=news_item&px=MTA0Njk Looks like these bugs needs to be resolved first: https://bugzilla.redhat.com/show_bug.cgi?id=689509 Tom -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: BTRFS as default in F17?
On Mon, Jan 23, 2012 at 10:56 PM, Greg wrote: > will BTRFS be default in F17? going by a story posted on Phoronix there's > likely to be a fsck next month? > http://www.phoronix.com/scan.php?page=news_item&px=MTA0Njk I've heard that for months now. It's also post alpha and feature freeze so I very much doubt it. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
BTRFS as default in F17?
will BTRFS be default in F17? going by a story posted on Phoronix there's likely to be a fsck next month? http://www.phoronix.com/scan.php?page=news_item&px=MTA0Njk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging:ScriptletSnippets
On Mon, 2012-01-23 at 21:24 +, Sérgio Basto wrote: > Hi, > from here > http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Icon_Cache > I see > /usr/bin/update-desktop-database &> /dev/null || : > > what does mean this part of the code "|| :" ? || is logical-OR with optimization (i.e., iff the first command fails, do the second). : is the null command. Therefore, this command always returns a success error code (zero), and so an error with update-desktop-database does not terminate the RPM transaction with an error message. -Chris -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Packaging:ScriptletSnippets
Hi, from here http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Icon_Cache I see /usr/bin/update-desktop-database &> /dev/null || : what does mean this part of the code "|| :" ? thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
On Mon, 23 Jan 2012 22:07:31 +0100 Thomas Woerner wrote: > Here are two more in ReadyForWrangler state: > > https://fedoraproject.org/wiki/Features/firewalld-default > https://fedoraproject.org/wiki/Features/network-zones The _submission_ deadline is tomorrow. ;) We will get all the features submitted and ready in next weeks meeting. ;) kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
Here are two more in ReadyForWrangler state: https://fedoraproject.org/wiki/Features/firewalld-default https://fedoraproject.org/wiki/Features/network-zones Thanks, Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17/rawhide uninstallable for 48 days?
Michał Piotrowski wrote: I want to install rawhide on one laptop. I tried to use TC1 netinst image (http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/x86_64/iso/Fedora-17-Alpha-x86_64-netinst.iso), This is not a real TC1 image. Please continue this discussion on the already existing thread[1] on the test list[2] (Fedora Rawhide/F17 testing mailing list). [1] http://lists.fedoraproject.org/pipermail/test/2012-January/105156.html [2] https://admin.fedoraproject.org/mailman/listinfo/test -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F17/rawhide uninstallable for 48 days?
Hi, I want to install rawhide on one laptop. I tried to use TC1 netinst image (http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/x86_64/iso/Fedora-17-Alpha-x86_64-netinst.iso), but it fails on: ImportError: No module named errors I tried to use xfce live cd (http://koji.fedoraproject.org/koji/taskinfo?taskID=3725264), but I see the same error. This error was reported at 2011-12-06 https://bugzilla.redhat.com/show_bug.cgi?id=760786 and possibly fixed at 2011-12-22. More than a month has passed since problem was fixed. I do not understand why fixed version wasn't build for f17/rawhide. -- Best regards, Michal http://eventhorizon.pl/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
PSA: bad HP udev rules somehow break boot with systemd 38
Hey, folks. Just thought I'd throw this one out there in case it helps
anyone else.
So ever since systemd 38 landed in Rawhide, I couldn't boot with it: had
to downgrade to 37 to make the system boot. I was pretty sure it wasn't
a generic problem or else more people would be yelling.
Somehow it turns out to be caused by a bunch of outdated udev rules that
something HP-ish has created on my system at some time:
/etc/udev/rules.d/86-hpmud-hp_laserjet_1000.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_1005_series.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_1018.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_1020.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_p1005.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_p1006.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_p1007.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_p1008.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_p1505.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1102.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1102w.rules
/etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1566.rules
None of these are owned by a package, so I don't know what created them
- hp-setup maybe?
Anyhow, these all have a ton of keys of the form SYSFS{idVendor} in
them. That's been deprecated syntax for udev since like 2006, and they
finally killed it with a recent udev release. So I was getting a ton of
errors in /var/log/messages on boot, of the form:
Jan 23 12:21:29 adam udevd[509]: unknown key 'SYSFS{idVendor}'
in /etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1566.rules:6
Somehow, this would result in the system failing to boot under systemd
38, with the udev service starting and then stopping itself. That would
result in emergency mode, since lots of other services won't start if
udev fails. systemd 37 didn't have a problem booting. I suppose the
large number of errors slows udev start down so much that it hits some
kind of timeout in 38 that isn't in 37, maybe?
Anyhow, the fix turned out to be simple:
sed -i -e 's,SYSFS,ATTR,g' /etc/udev/rules.d/86-*
so if you're hitting a similar issue, and you have those HP udev rules,
try that. Worked for me.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: new comps group proposal: Virtualization Host
Alan Pevec (ape...@gmail.com) said: > Since comps groups can't be extended, flow is to choose Minimal on the > initial Anaconda screen, then Customize Now: > * http://apevec.fedorapeople.org/virtmin1.png > In the next step, under Base System category, new "Virtualization > Host" group is choosen. > * http://apevec.fedorapeople.org/virtmin2.png > > Questions for this list are: > - do you think there's value to have this "Virtualization Host" option > in the first Anaconda screen, among Graphical Desktop/Software > Development/Web Server and Minimal, to avoid the second step? Note that we're redefining comps groups some, which will (eventually) filter into the anaconda interface. http://lists.fedoraproject.org/pipermail/devel/2012-January/161097.html for more details, but in any case, I wouldn't worry about trying to lock down the 'how-to-do-this-in-anaconda'. > - any better suggestions for the name of the group, maybe > "Virtualization Minimal", "Minimal Hypervisor", "Virtualization Node" 'Virtualization Hypervisor'? Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[389-devel] Please review: [389 Project] #139: RFE: eliminate the use of char *dn in favor of Slapi_DN *dn
https://fedorahosted.org/389/ticket/139
https://fedorahosted.org/389/attachment/ticket/139/0001-Trac-Ticket-139-eliminate-the-use-of-char-dn-in-favo.patch
Fix description: The oritinal RFE had been already implemented in
the commit f6397113666f06848412bb12f754f04258cfa5fa:
Reduce the number of DN normalization
In this patch, the Slapi_DN creation (slapi_sdn_{new,set,init}_dn_*)
are replaced with corresponding _normdn_ or _ndn_ APIs which takes
advantage of the knowledge that the DN is already optimized or not.
Note: With the patch applied, the slapi_dn_normalize_ext count called in
the start-up 8682 (times) was lowered to 1113 (times).
--
389-devel mailing list
389-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
[389-devel] Please review: Ticket #264 - upgrade needs better check for "server is running"
https://fedorahosted.org/389/ticket/264 https://fedorahosted.org/389/attachment/ticket/264/0001-Ticket-264-upgrade-needs-better-check-for-server-is-.patch -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Summary/Minutes from today's FESCo meeting (2012-01-23 at 18UTC)
=== #fedora-meeting: FESCO (2012-01-23) === Meeting started by nirik at 18:00:00 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2012-01-23/fesco.2012-01-23-18.00.log.html Meeting summary --- * init process (nirik, 18:00:01) * sponsor request - sdake (nirik, 18:01:39) * AGREED: sponsorship is approved. (nirik, 18:05:51) * F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET (nirik, 18:06:05) * AGREED: Feature is approved (nirik, 18:08:04) * F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD (nirik, 18:08:25) * AGREED: will ask rel-eng for input and revisit next week. (nirik, 18:35:17) * ACTION: bcl to talk with rel-eng. (nirik, 18:36:07) * F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication (nirik, 18:36:18) * AGREED: feature is approved. (nirik, 18:37:10) * F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool (nirik, 18:38:01) * AGREED: feature is approved. (nirik, 18:41:33) * F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster (nirik, 18:42:17) * AGREED: feature is approved. (nirik, 18:52:15) * #758 F17 Feature : Eclipse Juno - https://fedoraproject.org/wiki/Features/EclipseJuno (nirik, 18:58:51) * AGREED: feature is approved (nirik, 19:05:52) * #759 F17 Feature: Opa - https://fedoraproject.org/wiki/Features/Opa09 (nirik, 19:06:18) * AGREED: feature is approved (nirik, 19:08:30) * #760 F17 Feature: Internationalization support for additional Indian languages - http://fedoraproject.org/wiki/Features/Additional_Indic_Langs (nirik, 19:10:06) * AGREED: feature is approved (nirik, 19:10:49) * #761 F17 Feature: DNSSEC on workstations - https://fedoraproject.org/wiki/Features/DNSSEC_on_workstations (nirik, 19:11:12) * AGREED: feature is approved. (nirik, 19:13:38) * #763 F17 Feature: Ext4 support beyond 16T - https://fedoraproject.org/wiki/Features/F17Ext4Above16T (nirik, 19:14:28) * AGREED: feature is approved. (nirik, 19:15:19) * #764 F17 Feature: Haskell Platform 2011.4 - https://fedoraproject.org/wiki/Features/HaskellPlatform2011.4 (nirik, 19:15:35) * AGREED: feature is approved. (nirik, 19:16:30) * #765 F17 Feature: New Features of IPA v3 - https://fedoraproject.org/wiki/Features/IPAv3NewFeatures (nirik, 19:16:41) * AGREED: feature is approved. (nirik, 19:17:58) * #766 F17 Feature: Java 7 - https://fedoraproject.org/wiki/Features/Java7 (nirik, 19:18:04) * AGREED: feature is approved. (nirik, 19:19:32) * #767 F17 Feature - New mkdumprd for kdump - https://fedoraproject.org/wiki/Features/NewMkdumprd (nirik, 19:19:39) * AGREED: feature is approved. (nirik, 19:20:31) * #768 F17 Feature: Virtualization Sandbox - https://fedoraproject.org/wiki/Features/VirtSandbox (nirik, 19:20:37) * AGREED: feature is approved. (nirik, 19:21:56) * #769 F17 Feature: numad (Non-Uniform Memory Alignment Daemon) - https://fedoraproject.org/wiki/Features/numad (nirik, 19:22:29) * AGREED: feature is approved. (nirik, 19:25:25) * #771 F17 Feature: OpenStack Quantum - https://fedoraproject.org/wiki/Features/OpenStack_Quantum (nirik, 19:25:28) * AGREED: feature is approved. (nirik, 19:27:35) * #772 F17 Feature: OpenStack using Qpid - https://fedoraproject.org/wiki/Features/OpenStack_using_Qpid (nirik, 19:27:40) * AGREED: feature is approved. (nirik, 19:29:03) * #773 F17 Feature: Ruby 1.9.3 - https://fedoraproject.org/wiki/Features/Ruby_1.9.3 (nirik, 19:29:23) * AGREED: feature is approved. (nirik, 19:30:13) * #774 F17 Feature: SELinux Deny Ptrace - https://fedoraproject.org/wiki/Features/SELinuxDenyPtrace (nirik, 19:30:42) * AGREED: feature is approved. (nirik, 19:31:53) * #775 F17 Feature: PrivateTmp services - https://fedoraproject.org/wiki/Features/ServicesPrivateTmp (nirik, 19:32:17) * AGREED: feature is approved. (nirik, 19:35:15) * #753 F17 Feature: Wallaby - https://fedoraproject.org/wiki/Features/Wallaby (nirik, 19:35:22) * AGREED: feature is approved. (nirik, 19:37:14) * LINK: https://fedoraproject.org/wiki/Category:FeatureReadyForWrangler (nirik, 19:38:02) * Opa redux (nirik, 19:39:42) * OPA should document the output licensing (nirik, 19:46:56) * EOL package branches default acls (nirik, 19:48:01) * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/3094 (nirik, 19:48:16) * AGREED: fesco is fine with default acls for eol releases. (nirik, 19:50:29) * Open Floor (nirik, 19:50:43) * Cloed/Upstream bugs (nirik, 19:55:33) * ACTION: defer to next week. (nirik, 19:56:49) * Open floor again (nirik, 19:56:56) * ACTION: mmaslano will chair next week (nirik,
Re: Requesting a change to the BugStatusWorkFlow: Closed/UPSTREAM
On Mon, 2012-01-23 at 11:00 -0800, Adam Williamson wrote: > On Mon, 2012-01-23 at 07:42 +0100, David Tardon wrote: > > On Sat, Jan 21, 2012 at 12:27:10PM +, Richard W.M. Jones wrote: > > > On Fri, Jan 20, 2012 at 08:16:31AM +0100, David Tardon wrote: > > > > The libreoffice team uses this resolution for > > > > > > > > 1) bugs that are not reproducible, but we _think_ we know what is the > > > > cause (these are mostly "fire and forget" abrt bugs, where we managed to > > > > get something useful from the backtrace) > > > > > > CLOSED -> WORKSFORME or INSUFFICIENT_DATA > > > > > > > 2) bugs that only appear under very specific conditions and are unlikely > > > > to affect many users. > > > > > > CLOSED -> CANTFIX or WONTFIX > > > > > > I don't think CLOSED -> UPSTREAM is a good resolution for either of > > > these classes of unfixed bugs. > > > > It seems I was not clear enough--I spoke about bugs we _fixed_ in > > upstream, but did not backport the fixes into Fedora. But, well, I do > > not really care so much--I will roll a die the next time I am not sure > > which resolution to pick... > > It's worth noting, as a meta-point to this discussion, that it really > doesn't matter a *huge* deal what resolution you pick. The data isn't > used for a whole lot. I think, really, the only time we ever really use > the resolution information is in random one-shot statistical analyses > people do sometimes, like the X Test Week stats I post each cycle. > > We discussed this proposal at QA meeting today. We have no huge > objection to the change, nor do we think it's a fantastic idea, really > the response was 'meh'. My take on it is that if a developer wants a bug > closed, they're probably going to close the bug. Taking away a > resolution will only mean they'll pick a different one. Oh, and for any packagers who don't know: there is also an Upstream *keyword* you can use as an alternative to the UPSTREAM *resolution*. If you want to note that upstream is 'involved' in a bug in some way, whatever that means to you, without closing the bug, you can use the keyword instead of the resolution. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Requesting a change to the BugStatusWorkFlow: Closed/UPSTREAM
On Mon, 2012-01-23 at 07:42 +0100, David Tardon wrote: > On Sat, Jan 21, 2012 at 12:27:10PM +, Richard W.M. Jones wrote: > > On Fri, Jan 20, 2012 at 08:16:31AM +0100, David Tardon wrote: > > > The libreoffice team uses this resolution for > > > > > > 1) bugs that are not reproducible, but we _think_ we know what is the > > > cause (these are mostly "fire and forget" abrt bugs, where we managed to > > > get something useful from the backtrace) > > > > CLOSED -> WORKSFORME or INSUFFICIENT_DATA > > > > > 2) bugs that only appear under very specific conditions and are unlikely > > > to affect many users. > > > > CLOSED -> CANTFIX or WONTFIX > > > > I don't think CLOSED -> UPSTREAM is a good resolution for either of > > these classes of unfixed bugs. > > It seems I was not clear enough--I spoke about bugs we _fixed_ in > upstream, but did not backport the fixes into Fedora. But, well, I do > not really care so much--I will roll a die the next time I am not sure > which resolution to pick... It's worth noting, as a meta-point to this discussion, that it really doesn't matter a *huge* deal what resolution you pick. The data isn't used for a whole lot. I think, really, the only time we ever really use the resolution information is in random one-shot statistical analyses people do sometimes, like the X Test Week stats I post each cycle. We discussed this proposal at QA meeting today. We have no huge objection to the change, nor do we think it's a fantastic idea, really the response was 'meh'. My take on it is that if a developer wants a bug closed, they're probably going to close the bug. Taking away a resolution will only mean they'll pick a different one. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Requesting a change to the BugStatusWorkFlow: Closed/UPSTREAM
On Sat, 2012-01-21 at 12:33 +, Richard W.M. Jones wrote: > On Thu, Jan 19, 2012 at 06:31:44PM -0500, Stephen Gallagher wrote: > > For the record, I am referencing > > http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#CLOSED > > > > Currently, the official bug lifecycle includes the following phrase: > > "The resolution UPSTREAM can be used by maintainers to denote a bug that > > they expect to be fixed by upstream development and naturally rolled > > back into Fedora as part of the update process. Ideally, a comment > > should be added with a link to the upstream bug report." > > > > I've seen quite a few bugs lately closed with this resolution (mostly in > > the Evolution and GNOME projects for me personally). It seems to me that > > this is terribly useless in terms of informing users when their bugs are > > fixed. > > > > Essentially, when closing this bug as UPSTREAM, we are communicating to > > our users "This will get fixed. Probably. And it will get pulled into > > Fedora eventually. Probably." Most people, when they can actually be > > convinced to file a real bug report (even through ABRT), are doing so > > because they have an issue with the software and want to know when it's > > fixed. > > I was all set to disagree with you, but I think your analysis of the > text on that wiki page is spot on. > > That's not how _I_ use CLOSED -> UPSTREAM. I use it to indicate that > the bug *has been fixed* upstream. And if I'm feeling conscientious I > also add the version number where the fix (is/will) appear. This > should mean the user just needs to wait for the updated version to > appear in Fedora, and won't need to track upstream closely. > > I think the text on the wiki page ought to be changed. Well, it went through a review process on both this list and test list when I was writing it, and that was the text we wound up with. I don't recall the details, but I wouldn't just have pulled the definition out of my ass; it would be based on actual usage by developers. So a single 'that's not how I use it, change it!' request probably isn't enough weight. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
Here is another feature which is belated ReadyForWrangler: https://fedoraproject.org/wiki/Features/OpenStack_Essex Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Perl-Critic-Moose] Import
commit 8d743210b5d6bd683310794ecce620b935148ba4
Author: Petr Písař
Date: Mon Jan 23 18:21:33 2012 +0100
Import
.gitignore |1 +
perl-Perl-Critic-Moose.spec | 65 +++
sources |1 +
3 files changed, 67 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index e69de29..2248aca 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/Perl-Critic-Moose-0.999_002.tar.gz
diff --git a/perl-Perl-Critic-Moose.spec b/perl-Perl-Critic-Moose.spec
new file mode 100644
index 000..084fc7d
--- /dev/null
+++ b/perl-Perl-Critic-Moose.spec
@@ -0,0 +1,65 @@
+%global cpan_version 0.999_002
+Name: perl-Perl-Critic-Moose
+Version:%(echo %{cpan_version} | tr '_' '.')
+Release:1%{?dist}
+Summary:Policies for Perl::Critic concerned with using Moose
+License:GPL+ or Artistic
+Group: Development/Libraries
+URL:http://search.cpan.org/dist/Perl-Critic-Moose/
+Source0:
http://search.cpan.org/CPAN/authors/id/E/EL/ELLIOTJS/Perl-Critic-Moose-%{cpan_version}.tar.gz
+BuildArch: noarch
+BuildRequires: perl(Module::Build)
+# Run-time
+BuildRequires: perl(base)
+BuildRequires: perl(Perl::Critic::Policy) >= 1.098
+BuildRequires: perl(Perl::Critic::Utils) >= 1.098
+BuildRequires: perl(Perl::Critic::Utils::PPI) >= 1.098
+BuildRequires: perl(Readonly)
+# Tests only
+BuildRequires: perl(Carp)
+BuildRequires: perl(Perl::Critic::TestUtils) >= 1.098
+BuildRequires: perl(Perl::Critic::Violation) >= 1.098
+BuildRequires: perl(Test::More)
+Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo
$version))
+Requires: perl(Perl::Critic::Policy) >= 1.098
+Requires: perl(Perl::Critic::Utils) >= 1.098
+Requires: perl(Perl::Critic::Utils::PPI) >= 1.098
+
+# Remove underspecified dependencies
+%global __requires_exclude
%{?__requires_exclude:%__requires_exclude|}^perl\\(Perl::Critic::(Policy|Utils(|::PPI))\\)$
+
+# Augment provide versions with development digits
+%global __provides_exclude
%{?__provides_exclude:%__provides_exclude|}^perl\\(Perl::Critic::(Policy::)?Moose(::.*)?\\)\\s*=
+Provides: perl(Perl::Critic::Moose) = %{version}
+Provides: perl(Perl::Critic::Policy::Moose::ProhibitMultipleWiths) =
%{version}
+Provides: perl(Perl::Critic::Policy::Moose::ProhibitNewMethod) =
%{version}
+Provides: perl(Perl::Critic::Policy::Moose::RequireCleanNamespace) =
%{version}
+Provides: perl(Perl::Critic::Policy::Moose::RequireMakeImmutable) =
%{version}
+
+%description
+Some Perl::Critic policies that will help you keep your code in good shape
+with regards to Moose.
+
+%prep
+%setup -q -n Perl-Critic-Moose-%{cpan_version}
+
+%build
+%{__perl} Build.PL installdirs=vendor
+./Build
+
+%install
+./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
+find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+./Build test
+
+%files
+%doc Changes README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Thu Jan 19 2012 Petr Pisar 0.999.002-1
+- Specfile autogenerated by cpanspec 1.78.
diff --git a/sources b/sources
index e69de29..d0f6ee5 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+0f97e0fd5977eb67389b17080b648de0 Perl-Critic-Moose-0.999_002.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Perl-Critic-Moose-0.999_002.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Perl-Critic-Moose: 0f97e0fd5977eb67389b17080b648de0 Perl-Critic-Moose-0.999_002.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Package review swap - mediawiki-validator
On Mon, 2012-01-23 at 11:34 -0500, Neil Horman wrote: > On Mon, Jan 23, 2012 at 11:11:17AM -0500, James Laska wrote: > > Greetings, > > > > I'm in the process of updating the existing mediawiki-semantic package. > > The new version of mediawiki-semantic adds a dependency on an unpackaged > > extension: Validator. Anyone interested in a review swap? > > > > https://bugzilla.redhat.com/show_bug.cgi?id=784008 > > > > Thanks, > > James > > > I'll swap you for kredentials: > https://bugzilla.redhat.com/show_bug.cgi?id=782456 Deal! signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 784053] New: perl-Sub-WrapPackages provides perl(lib) erroneously
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: perl-Sub-WrapPackages provides perl(lib) erroneously
https://bugzilla.redhat.com/show_bug.cgi?id=784053
Summary: perl-Sub-WrapPackages provides perl(lib) erroneously
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: perl-Sub-WrapPackages
AssignedTo: emmanuel.sey...@club-internet.fr
ReportedBy: ppi...@redhat.com
QAContact: extras...@fedoraproject.org
CC: emmanuel.sey...@club-internet.fr,
fedora-perl-devel-l...@redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
# repoquery --qf '%{SOURCERPM}/%{NEVRA}' --whatprovides 'perl(lib)'
perl-5.14.2-210.fc17.src.rpm/perl-4:5.14.2-210.fc17.x86_64
perl-Sub-WrapPackages-2.0-7.fc17.src.rpm/perl-Sub-WrapPackages-0:2.0-7.fc17.noarch
Why does perl-Sub-WrapPackages provide `perl(lib)'? It redefines package lib in
the middle of lib/Sub/WrapPackages.pm. Sub::WrapPackags POD says:
> Deferred wrapping of subs in packages that aren't yet loaded works
> via a subroutine inserted in @INC. This means that if you mess
> around with @INC, eg by inserting a directoy at the beginning of
> the path, the magic might not get a chance to run. If you "use
> lib" to mess with @INC though, it should work, as I've over-ridden
> lib's import() method. That said, code this funky has no right to
> work. Use with caution!
Please filter `perl(lib)' from set of Provides. I guess other Fedoras than F17
are affected too.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: new comps group proposal: Virtualization Host
On Mon, Jan 23, 2012 at 04:18:17PM +, Daniel P. Berrange wrote: > On Mon, Jan 23, 2012 at 05:09:45PM +0100, Alan Pevec wrote: > > Hi all, > > > > I'd like to add a new group in comps.xml to make it easier to install > > minimal hypervisor based on Fedora. > > It would include only basic virtualization software (libvirt and > > qemu-kvm) and it would serve as a base to install virtualization > > management stack on top of it. > > Initial use-cases are: > > - Fedora oVirt host where vdsm agent is installed on top of proposed > > Virtualization Host group > > Also oVirt Node livecd kickstart would use that group instead of the > > current list of packages: > > > > http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=blob;f=recipe/common-pkgs.ks;hb=HEAD > > > > - Openstack nova nodes where various openstack-* packages are > > installed, depending on the node configuration (compute, controller, > > images or object store service) > > > > Since comps groups can't be extended, flow is to choose Minimal on the > > initial Anaconda screen, then Customize Now: > > * http://apevec.fedorapeople.org/virtmin1.png > > In the next step, under Base System category, new "Virtualization > > Host" group is choosen. > > * http://apevec.fedorapeople.org/virtmin2.png > > > > This should produce a working hypervisor with networking where > > additional packages can be installed using yum. > > > > Questions for this list are: > > - do you think there's value to have this "Virtualization Host" option > > in the first Anaconda screen, among Graphical Desktop/Software > > Development/Web Server and Minimal, to avoid the second step? > > This list of options is defined in anaconda and each option maps to > > a list of actual comps groups > > - any better suggestions for the name of the group, maybe > > "Virtualization Minimal", "Minimal Hypervisor", "Virtualization Node" > > ? +1 to the proposal above. > You don't mention the eisting 'Virtualization' group there, which > is historically what people have installed when wanting a virtualization > host. Admittedly this does include some desktop tools too. > > If introducing a new group for the host, then I'd say we might want > to also change the existing group to be solely the client mgmt tools > "Virtualization Client" ? [...] Old group renamed to "Virtualization Desktop Tools" maybe? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
On Mon, Jan 23, 2012 at 7:27 AM, Kevin Fenzi wrote: > On Mon, 23 Jan 2012 09:26:26 +0100 > Vít Ondruch wrote: > >> Dne 23.1.2012 03:40, Cole Robinson napsal(a): >> > Hi Kevin, >> > >> > I filed a feature page 2 Fridays ago that's been sitting in >> > ReadyForWrangler since: >> > >> > https://fedoraproject.org/wiki/Features/OpenStack_Horizon >> > >> > Anything I can do to get that on track for discussion/approval? >> > There are also a couple other openstack features that are similarly >> > lying in wait AFAICT (page owners cc'd): >> > >> > https://fedoraproject.org/wiki/Features/OpenStack_Quantum >> > https://fedoraproject.org/wiki/Features/OpenStack_using_Qpid >> > >> > Thanks! >> > Cole >> > >> > >> >> Hi Kevin, >> >> I would also like to see reviewed our Ruby 1.9.3 [1] feature >> submission, since it is blocking our progress. >> >> >> Vit >> >> >> [1] https://fedoraproject.org/wiki/Features/Ruby_1.9.3 > > It seems our feature wrangler was/is not only traveling, but sick and > didn't get these moved. Until this morning. ;( > > Since feature freeze is tomorrow, I'd like to see us finish all of them > that are now correctly in ready for fesco or we could do some in a > special session, or just next week. > > #758 F17 Feature : Eclipse Juno - > https://fedoraproject.org/wiki/Features/EclipseJuno > > #759 F17 Feature: Opa - > https://fedoraproject.org/wiki/Features/Opa09 > > #760 F17 Feature: > Internationalization support for additional Indian languages - > http://fedoraproject.org/wiki/Features/Additional_Indic_Langs > > #761 F17 Feature: > DNSSEC on workstations - > https://fedoraproject.org/wiki/Features/DNSSEC_on_workstations > > #762 F17 Feature: > Eclipse Juno - > https://fedoraproject.org/wiki/Features/EclipseJuno > > #763 F17 Feature: > Ext4 support beyond 16T - > https://fedoraproject.org/wiki/Features/F17Ext4Above16T > > #764 F17 Feature: > Haskell Platform 2011.4 - > https://fedoraproject.org/wiki/Features/HaskellPlatform2011.4 > > #765 F17 Feature: > New Features of IPA v3 - > https://fedoraproject.org/wiki/Features/IPAv3NewFeatures > > #766 F17 Feature: > Java 7 - https://fedoraproject.org/wiki/Features/Java7 > > #767 F17 Feature - > New mkdumprd for kdump - > https://fedoraproject.org/wiki/Features/NewMkdumprd > > #768 F17 Feature: > Virtualization Sandbox - > https://fedoraproject.org/wiki/Features/VirtSandbox > > #769 F17 Feature: > numad (Non-Uniform Memory Alignment Daemon) - > https://fedoraproject.org/wiki/Features/numad > > #771 F17 Feature: > OpenStack Quantum - > https://fedoraproject.org/wiki/Features/OpenStack_Quantum > > #772 F17 Feature: > OpenStack using Qpid - > https://fedoraproject.org/wiki/Features/OpenStack_using_Qpid > > #773 F17 Feature: > Ruby 1.9.3 - https://fedoraproject.org/wiki/Features/Ruby_1.9.3 > > #774 F17 Feature: > SELinux Deny Ptrace - > https://fedoraproject.org/wiki/Features/SELinuxDenyPtrace > > #775 F17 Feature: > PrivateTmp services - > https://fedoraproject.org/wiki/Features/ServicesPrivateTmp > > kevin > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel Sorry to be running right up against the deadline, but I just got the green light last week to move ahead with Eucalyptus in the F17 timeframe, so I've set my feature to ReadyForWrangler https://fedoraproject.org/wiki/Features/Eucalyptus --Andy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-HTML-FormHandler] update to 0.36000
commit d0930ebbb03b72902eb6a16853a103a42d75389b
Author: Iain Arnell
Date: Mon Jan 23 17:34:47 2012 +0100
update to 0.36000
.gitignore |1 +
perl-HTML-FormHandler.spec | 10 --
sources|2 +-
3 files changed, 10 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index eb7c8ca..71e4a9e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
/HTML-FormHandler-0.35003.tar.gz
/HTML-FormHandler-0.35005.tar.gz
+/HTML-FormHandler-0.36000.tar.gz
diff --git a/perl-HTML-FormHandler.spec b/perl-HTML-FormHandler.spec
index 9343c14..afbefe8 100644
--- a/perl-HTML-FormHandler.spec
+++ b/perl-HTML-FormHandler.spec
@@ -1,6 +1,6 @@
Name: perl-HTML-FormHandler
-Version:0.35005
-Release:2%{?dist}
+Version:0.36000
+Release:1%{?dist}
Summary:HTML forms using Moose
License:GPL+ or Artistic
Group: Development/Libraries
@@ -10,6 +10,7 @@ BuildArch: noarch
BuildRequires: perl(aliased)
BuildRequires: perl(Carp)
BuildRequires: perl(Class::Load) >= 0.06
+BuildRequires: perl(Config::Any)
BuildRequires: perl(DateTime)
BuildRequires: perl(DateTime::Format::Strptime)
BuildRequires: perl(Email::Valid)
@@ -17,6 +18,7 @@ BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(File::ShareDir)
BuildRequires: perl(File::ShareDir::Install)
BuildRequires: perl(File::Spec)
+BuildRequires: perl(HTML::TreeBuilder)
BuildRequires: perl(Locale::Maketext) >= 1.09
BuildRequires: perl(Moose) >= 2.0007
BuildRequires: perl(MooseX::Getopt) >= 0.16
@@ -24,6 +26,7 @@ BuildRequires: perl(MooseX::Types) >= 0.20
BuildRequires: perl(MooseX::Types::Common)
BuildRequires: perl(MooseX::Types::LoadableClass) >= 0.006
BuildRequires: perl(namespace::autoclean) >= 0.09
+BuildRequires: perl(Sub::Exporter)
BuildRequires: perl(Template)
BuildRequires: perl(Test::Differences)
BuildRequires: perl(Test::Exception)
@@ -80,6 +83,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Mon Jan 23 2012 Iain Arnell 0.36000-1
+- update to latest upstream version
+
* Fri Jan 13 2012 Fedora Release Engineering
- 0.35005-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
diff --git a/sources b/sources
index b3fbecc..a5233a7 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-b5ffc5c1e9787d9fb57181bf2e5b0c58 HTML-FormHandler-0.35005.tar.gz
+7ab88de7f07c74e7016ddea135c5e2e0 HTML-FormHandler-0.36000.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Package review swap - mediawiki-validator
On Mon, Jan 23, 2012 at 11:11:17AM -0500, James Laska wrote: > Greetings, > > I'm in the process of updating the existing mediawiki-semantic package. > The new version of mediawiki-semantic adds a dependency on an unpackaged > extension: Validator. Anyone interested in a review swap? > > https://bugzilla.redhat.com/show_bug.cgi?id=784008 > > Thanks, > James I'll swap you for kredentials: https://bugzilla.redhat.com/show_bug.cgi?id=782456 Neil > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: new comps group proposal: Virtualization Host
On Mon, Jan 23, 2012 at 5:18 PM, Daniel P. Berrange wrote: > You don't mention the eisting 'Virtualization' group there, which > is historically what people have installed when wanting a virtualization > host. Admittedly this does include some desktop tools too. Right, I forgot to mention why existing "Virtualization" is not good enough for this use-cases and it's exactly because it includes GUI stuff which is not needed on the minimal hypervisor install. > If introducing a new group for the host, then I'd say we might want > to also change the existing group to be solely the client mgmt tools > "Virtualization Client" ? It gets even more fuzzy when you wonder > where the new 'GNOME Boxes' app will live - probably under 'GNOME' > desktop I presume ? Renaming current "Virtualization" to "Virtualization Client" makes sense. I would put new Boxes into both Virt.Client and GNOME groups, list of packages are not exclusive. Alan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File HTML-FormHandler-0.36000.tar.gz uploaded to lookaside cache by iarnell
A file has been added to the lookaside cache for perl-HTML-FormHandler: 7ab88de7f07c74e7016ddea135c5e2e0 HTML-FormHandler-0.36000.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: new comps group proposal: Virtualization Host
On Mon, Jan 23, 2012 at 05:09:45PM +0100, Alan Pevec wrote: > Hi all, > > I'd like to add a new group in comps.xml to make it easier to install > minimal hypervisor based on Fedora. > It would include only basic virtualization software (libvirt and > qemu-kvm) and it would serve as a base to install virtualization > management stack on top of it. > Initial use-cases are: > - Fedora oVirt host where vdsm agent is installed on top of proposed > Virtualization Host group > Also oVirt Node livecd kickstart would use that group instead of the > current list of packages: > > http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=blob;f=recipe/common-pkgs.ks;hb=HEAD > > - Openstack nova nodes where various openstack-* packages are > installed, depending on the node configuration (compute, controller, > images or object store service) > > Since comps groups can't be extended, flow is to choose Minimal on the > initial Anaconda screen, then Customize Now: > * http://apevec.fedorapeople.org/virtmin1.png > In the next step, under Base System category, new "Virtualization > Host" group is choosen. > * http://apevec.fedorapeople.org/virtmin2.png > > This should produce a working hypervisor with networking where > additional packages can be installed using yum. > > Questions for this list are: > - do you think there's value to have this "Virtualization Host" option > in the first Anaconda screen, among Graphical Desktop/Software > Development/Web Server and Minimal, to avoid the second step? > This list of options is defined in anaconda and each option maps to > a list of actual comps groups > - any better suggestions for the name of the group, maybe > "Virtualization Minimal", "Minimal Hypervisor", "Virtualization Node" > ? You don't mention the eisting 'Virtualization' group there, which is historically what people have installed when wanting a virtualization host. Admittedly this does include some desktop tools too. If introducing a new group for the host, then I'd say we might want to also change the existing group to be solely the client mgmt tools "Virtualization Client" ? It gets even more fuzzy when you wonder where the new 'GNOME Boxes' app will live - probably under 'GNOME' desktop I presume ? Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Package review swap - mediawiki-validator
Greetings, I'm in the process of updating the existing mediawiki-semantic package. The new version of mediawiki-semantic adds a dependency on an unpackaged extension: Validator. Anyone interested in a review swap? https://bugzilla.redhat.com/show_bug.cgi?id=784008 Thanks, James signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
new comps group proposal: Virtualization Host
Hi all, I'd like to add a new group in comps.xml to make it easier to install minimal hypervisor based on Fedora. It would include only basic virtualization software (libvirt and qemu-kvm) and it would serve as a base to install virtualization management stack on top of it. Initial use-cases are: - Fedora oVirt host where vdsm agent is installed on top of proposed Virtualization Host group Also oVirt Node livecd kickstart would use that group instead of the current list of packages: http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=blob;f=recipe/common-pkgs.ks;hb=HEAD - Openstack nova nodes where various openstack-* packages are installed, depending on the node configuration (compute, controller, images or object store service) Since comps groups can't be extended, flow is to choose Minimal on the initial Anaconda screen, then Customize Now: * http://apevec.fedorapeople.org/virtmin1.png In the next step, under Base System category, new "Virtualization Host" group is choosen. * http://apevec.fedorapeople.org/virtmin2.png This should produce a working hypervisor with networking where additional packages can be installed using yum. Questions for this list are: - do you think there's value to have this "Virtualization Host" option in the first Anaconda screen, among Graphical Desktop/Software Development/Web Server and Minimal, to avoid the second step? This list of options is defined in anaconda and each option maps to a list of actual comps groups - any better suggestions for the name of the group, maybe "Virtualization Minimal", "Minimal Hypervisor", "Virtualization Node" ? Thanks, Alan From 0d381fd2feab8fd7899ffec0e2984c9f7cbf0cca Mon Sep 17 00:00:00 2001 From: Alan Pevec Date: Mon, 23 Jan 2012 17:04:36 +0100 Subject: [PATCH] add Virtualization Host group Smallest possible virtualization host installation for headless nodes, without any graphical interface. Installs on top of core group. --- comps-f17.xml.in | 13 + 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/comps-f17.xml.in b/comps-f17.xml.in index becd1aa..9acf1ca 100644 --- a/comps-f17.xml.in +++ b/comps-f17.xml.in @@ -6130,6 +6130,18 @@ +virtualization-host +<_name>Virtualization Host +<_description>Smallest possible virtualization host installation +false +false + + libvirt + qemu-kvm + NetworkManager + + + walloon-support <_name>Walloon Support <_description/> @@ -6731,6 +6743,7 @@ legacy-software-support system-tools virtualization + virtualization-host -- 1.7.7.5 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
On Mon, 23 Jan 2012 10:33:21 -0500 Stephen Gallagher wrote: > On Mon, 2012-01-23 at 08:27 -0700, Kevin Fenzi wrote: > > Since feature freeze is tomorrow, I'd like to see us finish all of > > them > > Just to clarify, in case anyone just had a heart-attack, tomorrow is > the Feature Submission Deadline, *not* the Feature Freeze. > > According to http://fedoraproject.org/wiki/Releases/17/Schedule the > Feature Freeze date is 2012-02-07 Sorry, thats what I get for posting pre-coffee. ;( Thanks for clearing that up Stephen. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
On Mon, 2012-01-23 at 08:27 -0700, Kevin Fenzi wrote: > Since feature freeze is tomorrow, I'd like to see us finish all of them Just to clarify, in case anyone just had a heart-attack, tomorrow is the Feature Submission Deadline, *not* the Feature Freeze. According to http://fedoraproject.org/wiki/Releases/17/Schedule the Feature Freeze date is 2012-02-07 signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
On Mon, 23 Jan 2012 09:26:26 +0100 Vít Ondruch wrote: > Dne 23.1.2012 03:40, Cole Robinson napsal(a): > > Hi Kevin, > > > > I filed a feature page 2 Fridays ago that's been sitting in > > ReadyForWrangler since: > > > > https://fedoraproject.org/wiki/Features/OpenStack_Horizon > > > > Anything I can do to get that on track for discussion/approval? > > There are also a couple other openstack features that are similarly > > lying in wait AFAICT (page owners cc'd): > > > > https://fedoraproject.org/wiki/Features/OpenStack_Quantum > > https://fedoraproject.org/wiki/Features/OpenStack_using_Qpid > > > > Thanks! > > Cole > > > > > > Hi Kevin, > > I would also like to see reviewed our Ruby 1.9.3 [1] feature > submission, since it is blocking our progress. > > > Vit > > > [1] https://fedoraproject.org/wiki/Features/Ruby_1.9.3 It seems our feature wrangler was/is not only traveling, but sick and didn't get these moved. Until this morning. ;( Since feature freeze is tomorrow, I'd like to see us finish all of them that are now correctly in ready for fesco or we could do some in a special session, or just next week. #758F17 Feature : Eclipse Juno - https://fedoraproject.org/wiki/Features/EclipseJuno #759F17 Feature: Opa - https://fedoraproject.org/wiki/Features/Opa09 #760F17 Feature: Internationalization support for additional Indian languages - http://fedoraproject.org/wiki/Features/Additional_Indic_Langs #761F17 Feature: DNSSEC on workstations - https://fedoraproject.org/wiki/Features/DNSSEC_on_workstations #762F17 Feature: Eclipse Juno - https://fedoraproject.org/wiki/Features/EclipseJuno #763F17 Feature: Ext4 support beyond 16T - https://fedoraproject.org/wiki/Features/F17Ext4Above16T #764F17 Feature: Haskell Platform 2011.4 - https://fedoraproject.org/wiki/Features/HaskellPlatform2011.4 #765F17 Feature: New Features of IPA v3 - https://fedoraproject.org/wiki/Features/IPAv3NewFeatures #766F17 Feature: Java 7 - https://fedoraproject.org/wiki/Features/Java7 #767F17 Feature - New mkdumprd for kdump - https://fedoraproject.org/wiki/Features/NewMkdumprd #768F17 Feature: Virtualization Sandbox - https://fedoraproject.org/wiki/Features/VirtSandbox #769F17 Feature: numad (Non-Uniform Memory Alignment Daemon) - https://fedoraproject.org/wiki/Features/numad #771F17 Feature: OpenStack Quantum - https://fedoraproject.org/wiki/Features/OpenStack_Quantum #772F17 Feature: OpenStack using Qpid - https://fedoraproject.org/wiki/Features/OpenStack_using_Qpid #773F17 Feature: Ruby 1.9.3 - https://fedoraproject.org/wiki/Features/Ruby_1.9.3 #774F17 Feature: SELinux Deny Ptrace - https://fedoraproject.org/wiki/Features/SELinuxDenyPtrace #775F17 Feature: PrivateTmp services - https://fedoraproject.org/wiki/Features/ServicesPrivateTmp kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[pkgdb] perl-Hash-Case ownership changed
Package perl-Hash-Case in Fedora 15 is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-Hash-Case -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Hash-Case ownership changed
Package perl-Hash-Case in Fedora 16 is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-Hash-Case -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Hash-Case ownership changed
Package perl-Hash-Case in Fedora devel is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-Hash-Case -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Hash-WithDefaults ownership changed
Package perl-Hash-WithDefaults in Fedora 15 is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-Hash-WithDefaults -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Hash-WithDefaults ownership changed
Package perl-Hash-WithDefaults in Fedora 16 is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-Hash-WithDefaults -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-Hash-WithDefaults ownership changed
Package perl-Hash-WithDefaults in Fedora devel is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-Hash-WithDefaults -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
gnome-shell in rawhide
Just a heads-up: With the updates I built over the weekend, gnome-shell should be back in working condition in rawhide, at least it works fine for me now. I've also built a number of bug-fixes that should stop gnome-settings-daemon from crashing, but gcc doesn't currently let me rebuild PackageKit. As a workaround, you can disable the updates plugin for now: gsettings set org.gnome.settings-daemon.plugins.updates active false In other news, gnome-disk-utility and gvfs have been switched over to using udisks2 now. This should cause minimal disruption as udisks2 is fully-parallel installable with udisks, which will stay around for a while. Matthias -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[pkgdb] perl-PerlIO-via-symlink ownership changed
Package perl-PerlIO-via-symlink in Fedora 15 is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-PerlIO-via-symlink -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-PerlIO-via-symlink ownership changed
Package perl-PerlIO-via-symlink in Fedora 16 is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-PerlIO-via-symlink -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-PerlIO-via-symlink ownership changed
Package perl-PerlIO-via-symlink in Fedora devel is now owned by ppisar To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-PerlIO-via-symlink -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Requesting a change to the BugStatusWorkFlow: Closed/UPSTREAM
On Fri, 2012-01-20 at 08:16 +0100, David Tardon wrote: > On Thu, Jan 19, 2012 at 06:31:44PM -0500, Stephen Gallagher wrote: > > For the record, I am referencing > > http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#CLOSED > > > > Currently, the official bug lifecycle includes the following phrase: > > "The resolution UPSTREAM can be used by maintainers to denote a bug that > > they expect to be fixed by upstream development and naturally rolled > > back into Fedora as part of the update process. Ideally, a comment > > should be added with a link to the upstream bug report." > > > > I've seen quite a few bugs lately closed with this resolution (mostly in > > the Evolution and GNOME projects for me personally). It seems to me that > > this is terribly useless in terms of informing users when their bugs are > > fixed. > > > > Essentially, when closing this bug as UPSTREAM, we are communicating to > > our users "This will get fixed. Probably. And it will get pulled into > > Fedora eventually. Probably." Most people, when they can actually be > > convinced to file a real bug report (even through ABRT), are doing so > > because they have an issue with the software and want to know when it's > > fixed. > > The libreoffice team uses this resolution for > > 1) bugs that are not reproducible, but we _think_ we know what is the > cause (these are mostly "fire and forget" abrt bugs, where we managed to > get something useful from the backtrace) That says to me "CLOSED/INSUFFICIENT_DATA" or, if you actually suspect you have a fix, it should remain open until the fix is committed upstream. I think I can agree that CLOSED/UPSTREAM is reasonable for fixes that are already committed upstream. > > 2) bugs that only appear under very specific conditions and are unlikely > to affect many users. That's CLOSED/WONTFIX. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Requesting a change to the BugStatusWorkFlow: Closed/UPSTREAM
On Mon, Jan 23, 2012 at 07:42:57AM +0100, David Tardon wrote: > On Sat, Jan 21, 2012 at 12:27:10PM +, Richard W.M. Jones wrote: > > On Fri, Jan 20, 2012 at 08:16:31AM +0100, David Tardon wrote: > > > The libreoffice team uses this resolution for > > > > > > 1) bugs that are not reproducible, but we _think_ we know what is the > > > cause (these are mostly "fire and forget" abrt bugs, where we managed to > > > get something useful from the backtrace) > > > > CLOSED -> WORKSFORME or INSUFFICIENT_DATA > > > > > 2) bugs that only appear under very specific conditions and are unlikely > > > to affect many users. > > > > CLOSED -> CANTFIX or WONTFIX > > > > I don't think CLOSED -> UPSTREAM is a good resolution for either of > > these classes of unfixed bugs. > > It seems I was not clear enough--I spoke about bugs we _fixed_ in > upstream, but did not backport the fixes into Fedora. But, well, I do > not really care so much--I will roll a die the next time I am not sure > which resolution to pick... Ah well if you have *fixed* the bugs, then CLOSED -> UPSTREAM is perfectly reasonable. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2012-01-23 at 18UTC)
Dne 23.1.2012 03:40, Cole Robinson napsal(a): On 01/22/2012 07:44 PM, Kevin Fenzi wrote: Following is the list of topics that will be discussed in the FESCo meeting tomorrow at 18:00UTC (1:00pm EST) in #fedora-meeting on irc.freenode.net. Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic sponsor request - sdake .fesco 724 = New business = #topic F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET .fesco 751 #topic F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD .fesco 752 #topic F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication .fesco 754 #topic F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool .fesco 755 #topic F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster .fesco 756 Hi Kevin, I filed a feature page 2 Fridays ago that's been sitting in ReadyForWrangler since: https://fedoraproject.org/wiki/Features/OpenStack_Horizon Anything I can do to get that on track for discussion/approval? There are also a couple other openstack features that are similarly lying in wait AFAICT (page owners cc'd): https://fedoraproject.org/wiki/Features/OpenStack_Quantum https://fedoraproject.org/wiki/Features/OpenStack_using_Qpid Thanks! Cole Hi Kevin, I would also like to see reviewed our Ruby 1.9.3 [1] feature submission, since it is blocking our progress. Vit [1] https://fedoraproject.org/wiki/Features/Ruby_1.9.3 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
