[Bug 679313] New: perl-SDL is out of date 2.1.3-13 (~2007)
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-SDL is out of date 2.1.3-13 (~2007) https://bugzilla.redhat.com/show_bug.cgi?id=679313 Summary: perl-SDL is out of date 2.1.3-13 (~2007) Product: Fedora Version: 14 Platform: x86_64 OS/Version: Linux Status: NEW Severity: low Priority: unspecified Component: perl-SDL AssignedTo: hdego...@redhat.com ReportedBy: vytautas1...@yahoo.com QAContact: extras...@fedoraproject.org CC: hdego...@redhat.com, fedora-perl-devel-l...@redhat.com Classification: Fedora Description of problem: Plz update it at least to 2.2.x series. -- 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: rpm: working with locale files
- Original Message -
Hi list,
I'm new in rpm building and want to prepare a package for webapp
Habari
(review request: https://bugzilla.redhat.com/show_bug.cgi?id=673630)
but.. I
have a problem with locale files, which are situated in
%{_datadir}/habari/system/locale. When I use %find_lang macro,
rpmbuild have
problem with twice listed files.. Is there any way how to exclude
locale
files from rpm in spec file?
Perhaps you can first remove the locales you want to be removed and then
running find_lang macro?
Looking at your spec file
(http://static.stderr.cz/fedora/habari/0.6.6-2/habari.spec)
it seems you're not using the macro. See
https://fedoraproject.org/wiki/Packaging:Guidelines for info on how to
use it.
Maybe it is a silly question, but I can't google anything.
Thanks for reply,
Jakub J.
Michal
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
File SDL_Perl-v2.2.6.tar.gz uploaded to lookaside cache by jwrdegoede
A file has been added to the lookaside cache for perl-SDL: 445950ca7b9991f34ec792bbac8386b6 SDL_Perl-v2.2.6.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
[Bug 679313] perl-SDL is out of date 2.1.3-13 (~2007)
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=679313 --- Comment #2 from Fedora Update System upda...@fedoraproject.org 2011-02-22 04:21:16 EST --- perl-SDL-2.2.6-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/perl-SDL-2.2.6-1.fc15 -- 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: Which fonts should be pulled in by desktop environments as dependencies?!
Le Lun 21 février 2011 22:27, Hedayat Vatankhah a écrit : On ۱۱/۰۲/۲۲ 12:30, Nicolas Mailhot wrote: Le lundi 21 février 2011 à 21:42 +0330, Hedayat Vatankhah a écrit : Now, as is being discussed in [1], which fonts should be pulled by a desktop environment as its dependencies? A DE should pull in the fonts group. That's the only font list proofed by i18n for each release. Thanks for the answer. I also thought that it is reasonable, but wanted to make sure before calling others for it. I just wonder if it is possible to have group dependencies in comps.xml or by packages! What is the best way for enforcing such dependencies in Fedora? Well that is a question for fedora-devel and the tools people :) -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rawhide report: 20110219 changes - requires perl(Gtk2::
On Tue, 22 Feb 2011 06:57:20 +0100, Ralf Corsepius wrote: On a more abstract level one may consider perl's META.yml-machinery to be a package dependency tracking machinery of its own, in parallel to rpm's dependency tracking machinery, with the essentially the same issues, problems and imperfections as rpm/rpm.specs itself. In such case aren't such missing dependencies a normal upstream bug which should be fixed first as a Fedora patch (of META.yml) and pushed upstream, as usual? Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Mojolicious-1.11.tar.gz uploaded to lookaside cache by yaneti
A file has been added to the lookaside cache for perl-Mojolicious: ac3ba29a1f4d0d2f837668dd3bbb83ec Mojolicious-1.11.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
[perl-Mojolicious/f15/master] Update to latest upstream 1.11
commit 157efecf23344ac0b6c3c47b8bef47a90392e208
Author: Yanko Kaneti yan...@declera.com
Date: Tue Feb 22 12:55:14 2011 +0200
Update to latest upstream 1.11
.gitignore|1 +
perl-Mojolicious.spec | 10 +-
sources |2 +-
3 files changed, 7 insertions(+), 6 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 3199e12..dff28ed 100644
--- a/.gitignore
+++ b/.gitignore
@@ -9,3 +9,4 @@ Mojolicious-0.26.tar.gz
/Mojolicious-0.50.tar.gz
/Mojolicious-1.0.tar.gz
/Mojolicious-1.01.tar.gz
+/Mojolicious-1.11.tar.gz
diff --git a/perl-Mojolicious.spec b/perl-Mojolicious.spec
index 215fa0a..be6c446 100644
--- a/perl-Mojolicious.spec
+++ b/perl-Mojolicious.spec
@@ -1,6 +1,6 @@
Name: perl-Mojolicious
-Version:1.01
-Release:2%{?dist}
+Version:1.11
+Release:1%{?dist}
Summary:A next generation web framework for Perl
License:Artistic 2.0
Group: Development/Libraries
@@ -51,12 +51,12 @@ make test
%{_mandir}/man3/*
%changelog
+* Tue Feb 22 2011 Yanko Kaneti yan...@declera.com 1.11-1
+- Update to latest upstream 1.11.
+
* Tue Feb 08 2011 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.01-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
-* Fri Jan 7 2011 Yanko Kaneti yan...@declera.com 1.01-1
-- Update to latest upstream 1.01.
-
* Mon Dec 27 2010 Yanko Kaneti yan...@declera.com 1.0-1
- Update to latest upstream 1.0.
diff --git a/sources b/sources
index f27f4b5..211409a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-02594b57eb13b6f00d154e15b9aac632 Mojolicious-1.01.tar.gz
+ac3ba29a1f4d0d2f837668dd3bbb83ec Mojolicious-1.11.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: systemd fail-to-boot in rawhide
On Mon, 21.02.11 22:45, Matthew Miller (mat...@mattdm.org) wrote: On Mon, Feb 21, 2011 at 03:54:14PM +0100, Lennart Poettering wrote: Updated to this morning's rawhide. Rebooted. Now, I get to mounting my filesystems, which works succesfully, and then it just sits there. I need more information: Is the plymouth screen shown? Does it react to Esc? Can you switch to another VT? Does it timeout after 60s? Turns out that it was fscking a filesystem that had been scrolled off the screen by other status messages. I left it go overnight and it was up in the morning and I could see the output in the log. The old init system used to give some indication of progress while this was happening (via a hack in fsck, I believe). Is it a systemd change that is suppressing that? Well, this is a difficult problem, unfortunately. We already connect stdout/stderr of fsck with syslog and the console at the same time. That should give you a minimal idea on what is going on. However no progress bar. In the syslog output the progress bar would not make much sense probably. fsck (at least in the ext234 implementation) supports the -C parameter to direct progress bar information (and only the progress bar) to a specific fd. However, that information is intended for applications to parse it, not to show on the screen. I am not really sure what to do about this. One option would be to extend -C to show a human readable progress bar on the file name passed. Then we could just invoke fsck with -C /dev/console and would get a progress bar printed on the console, and the console only. But it keeps me wondering how that would look like if multiple fs are handled in parallel. Another option would be to parse fsck's output and forward it in some form to Plymouth to show in the normal progress bar. But I am not sure if Plymouth can actually do that. (Ray?) Also, this doesn't solve the problem that we might get multiple streams of progress bar information at the same time and for presentation in plymouth we'd need to somehow integrate them into one, and whose responsibility would that be? Plymouth? I think not having the progress bar for F15 is acceptable, but I am all ears for suggestions how to implement this best post-F15. Especially if somebody wants to do the work... ;-) Or maybe the whole problem set goes away by doing nothing since btrfs has no fsck? ;-) Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 679380] New: perl-Coro-5.371 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Coro-5.371 is available https://bugzilla.redhat.com/show_bug.cgi?id=679380 Summary: perl-Coro-5.371 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: perl-Coro AssignedTo: ppi...@redhat.com ReportedBy: upstream-release-monitor...@fedoraproject.org QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, mmasl...@redhat.com, kwiz...@gmail.com, boche...@fedoraproject.org, ppi...@redhat.com, psab...@redhat.com Classification: Fedora Latest upstream release: 5.371 Current version in Fedora Rawhide: 5.26 URL: http://search.cpan.org/dist/Coro/ Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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: installation of my own rpm in a Fedora without internet
On Tue, 2011-02-22 at 09:29 -0300, Domingo Becker wrote: 2011/2/19 Dominic Hopf dma...@googlemail.com: I think that a just installed Fedora box should have the ability to install software from an usb stick without the need of an internet connection. Think about a computer with F14 for managing something in a place without internet connection (I have several cases like this). Is there a way to do this? I usually do this with yum localinstall file.rpm This command doesn't work. [usuario@computadora ~]$ su -c 'yum localinstall --nogpg servbce-2.6.1-2.fc13.i686.rpm ' Contraseña: Complementos cargados:langpacks, presto, refresh-packagekit Adding es_ES to language list Configurando el proceso de instalación local de paquetes Examinando servbce-2.6.1-2.fc13.i686.rpm: servbce-2.6.1-2.fc13.i686 Marcando servbce-2.6.1-2.fc13.i686.rpm para ser instalado Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again [usuario@computadora ~]$ yum --disablerepo='*' --nogpg install file.rpm -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd fail-to-boot in rawhide
On Tue, 2011-02-22 at 13:40 +0100, Lennart Poettering wrote: Or maybe the whole problem set goes away by doing nothing since btrfs has no fsck? ;-) When I spoke with Josef a couple of weeks ago he said btrfs would be getting a fsck very soon. borne out by this comment from Chris: http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg08383.html -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Trying to contact David Zeuthen for nonresponsive maintainer process
On Tue, 2011-02-22 at 13:52 +0100, Tim Niemueller wrote: On 22.02.2011 05:00, Bastien Nocera wrote: On Tue, 2011-02-22 at 00:57 +0100, Tim Niemueller wrote: Is David still around? Yes, and hacking on GNOME 3. And no five minutes to care about older duties or at least reply? Too bad. resolve the issues surrounding Festival? I've asked Jason Tibbitts to approve ACLs for me, so I could approve your requests. If you want to take over the package, let me know, and I'll get David to drop the maintainership. Thanks for looking into this. Surprised David is so unreachable. My pkgdb requests were granted and I can go and add the fix now. Since David is so busy, it seems to be a better option to find a new maintainer for Festival. I'd be happy if any of the many co-maintainers would step up to this. If nobody does I could do it. A word of warning though that desktop development is not my primary concern (anymore), so someone who would look at the dependent packages would be a good idea. My repoquery fu suggests that no other package other than Fawkes (in the future once the mentioned bug is fixed) relies on Festival as a library, but rather other packages (like gnome-speech, kdeaccesibility, asterisk) invoke the command line tool. It might be worth considering upgrading to the latest stable release. But someone who maintained the package before should have a look at the 19 (!) patches if they have been upstreamed, don't need be, or should be. Most of the people in the maintainers list are members of the desktop team at Red Hat, the group which owned the package when it was migrated from Fedora Core to Fedora. I doubt any of them are interested in maintaining it. Anyone interested? I'd join the effort. Most of us already have too much on our plate. If you want to help out, great, otherwise it'll probably stay in a state of disrepair. I don't even know if gnome-speech is still in use, nobody's committed to it in 2 years. The kdeaccessibility or asterisk people should take over it if they care about it. Cheers -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Which fonts should be pulled in by desktop environments as dependencies?!
Nicolas Mailhot wrote: Le Lun 21 février 2011 22:27, Hedayat Vatankhah a écrit : Thanks for the answer. I also thought that it is reasonable, but wanted to make sure before calling others for it. I just wonder if it is possible to have group dependencies in comps.xml or by packages! What is the best way for enforcing such dependencies in Fedora? Well that is a question for fedora-devel and the tools people :) Well, please do not add hardcoded dependencies on all those packages to desktop environment packages. If I don't need fonts for [insert language here], I should be able to remove them. The fonts group in comps, which is already installed by default, is the right place for those fonts. Localized live kickstarts also need to be able to remove fonts for locales they don't support, to make room for packages to support the locales they do support. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Trying to contact David Zeuthen for nonresponsive maintainer process
On Tue, Feb 22, 2011 at 02:05:07PM +, Bastien Nocera wrote: Most of the people in the maintainers list are members of the desktop team at Red Hat, the group which owned the package when it was migrated from Fedora Core to Fedora. I doubt any of them are interested in maintaining it. I'm on the list of people because I did a lot of work on it a few years ago (and am partly responsible for some of the odd decisions which make the package a mess). But since then, I've changed jobs *and* now have two little kids, so although I still have nominal interest, I just don't have the time. *sigh*. -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 15 Alpha RC1 Available Now!
On Mon, Feb 21, 2011 at 9:00 PM, Andre Robatino robat...@fedoraproject.orgwrote: Fedora 15 Alpha RC1 is now available [1]. Please refer to the following pages for download links and testing instructions. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha priority test cases for installation [2] and desktop [3] should pass in order to meet the Alpha Release Criteria [4]. Help is available on #fedora-qa on irc.freenode.net [5], or on the test list [6]. [1] http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [4] https://fedoraproject.org/wiki/Fedora_15_Alpha_Release_Criteria [5] irc://irc.freenode.net/fedora-qa [6] https://admin.fedoraproject.org/mailman/listinfo/test Downloaded both x86_64 images and tested netinstall on VBox (discovered it was looking for a missing .treeinfo in the repository). went fine. more testing later. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd fail-to-boot in rawhide
On Tue, Feb 22, 2011 at 01:40:51PM +0100, Lennart Poettering wrote: the same time. That should give you a minimal idea on what is going on. However no progress bar. In the syslog output the progress bar would not make much sense probably. fsck (at least in the ext234 implementation) supports the -C parameter to direct progress bar information (and only the progress bar) to a specific fd. However, that information is intended for applications to parse it, not to show on the screen. I am not really sure what to do about this. One option would be to extend -C to show a human readable progress bar on the file name passed. Then we could just invoke fsck with -C /dev/console and would get a progress bar printed on the console, and the console only. But it keeps me wondering how that would look like if multiple fs are handled in parallel. It would look pretty ugly. But having no output at all is very undesirable, because it makes the system look hung, and particularly because (as in this case) the most recently-printed messages may have nothing at all to do with what is blocking the boot. Another option would be to parse fsck's output and forward it in some form to Plymouth to show in the normal progress bar. But I am not sure if Plymouth can actually do that. (Ray?) Also, this doesn't solve the Also, it doesn't solve the problem in cases where one isn't running plymouth, which I hope is a use case that systemd intends to take seriously. I think not having the progress bar for F15 is acceptable, but I am all ears for suggestions how to implement this best post-F15. Especially if somebody wants to do the work... ;-) I don't think it's a blocker, but it should probably get put into the release notes. Things like this cause end-user and support-center pain. -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
KDE-SIG meeting report (08/2011)
This is a report of the weekly KDE-SIG-Meeting with a summary of the topics that were discussed. If you want to add a comment please reply to this email or add it to the related meeting page. = Weekly KDE Summary = Week: 08/2011 Time: 2011-02-22 15:00 UTC Meeting page: https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2011-02-22 Meeting minutes: http://meetbot.fedoraproject.org/fedora-meeting/2011-02-22/kde- sig.2011-02-22-15.01.html Meeting log: http://meetbot.fedoraproject.org/fedora-meeting/2011-02-22/kde- sig.2011-02-22-15.01.log.html = Participants = * Kevin Kofler * Jaroslav Reznik * Lukas Tinkl * Rex Dieter * Than Ngo * Radek Novacek = Agenda = topics to discuss: * F15 alpha rc1 out ** Desktop Validation tests * Live image tweaks for Beta ** (Re)add new packages to our spin (kickstart) = Summary = F15 alpha rc1 out * jreznik is running Desktop Validation tests [1] * current spins size is evil 666 MiB for 64 bit, 667 MiB for 32 bit ** we don't want to touch it before Alpha Gold * Plasma logout crasher would be nice to have but it's not a blocker and 4.6.1 will be tagged this week (Thu 24) Live image tweaks for Beta * we have some free space on live CD ** 2 sets of nice to have packages *** stuff that's explicitly dropped from the CD: amarok, digikam, ktorrent *** new stuff that can be added: kamoso (once it passes review), krusader, ??? ** Amarok and Digikam are preferred apps *** but we are not sure we will have space for both (Digikam pulls Marble with big datasets) * AGREED: on priority being: 1. Amarok, 2. Digikam if it fits, 3. ktorrent, 4. other stuff ** discuss the other stuff once we agreed on the highest priority items * ACTION: Kevin_Kofler to do kickstart tweaks * krusader for 1G image as it duplicates Dolphin functionality * kamoso as optional for F15, default for F16 ** it's still alpha, we need more testing but we'd like to have it one day UPnP * jreznik is trying to package UPnP stack ** qtsoap bundled in herqq, dependency for kio-upnp-ms = Next Meeting = http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2011-03-01 = Links = [1] https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test -- Jaroslav Řezník jrez...@redhat.com Software Engineer - Base Operating Systems Brno Office: +420 532 294 275 Mobile: +420 602 797 774 Red Hat, Inc. http://cz.redhat.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd fail-to-boot in rawhide
On Tue, 22.02.11 12:55, Matthew Miller (mat...@mattdm.org) wrote: On Tue, Feb 22, 2011 at 01:40:51PM +0100, Lennart Poettering wrote: the same time. That should give you a minimal idea on what is going on. However no progress bar. In the syslog output the progress bar would not make much sense probably. fsck (at least in the ext234 implementation) supports the -C parameter to direct progress bar information (and only the progress bar) to a specific fd. However, that information is intended for applications to parse it, not to show on the screen. I am not really sure what to do about this. One option would be to extend -C to show a human readable progress bar on the file name passed. Then we could just invoke fsck with -C /dev/console and would get a progress bar printed on the console, and the console only. But it keeps me wondering how that would look like if multiple fs are handled in parallel. It would look pretty ugly. But having no output at all is very undesirable, because it makes the system look hung, and particularly because (as in this case) the most recently-printed messages may have nothing at all to do with what is blocking the boot. What we could do is start fsck always with -V, i.e. verbose mode. Should we? Another option would be to parse fsck's output and forward it in some form to Plymouth to show in the normal progress bar. But I am not sure if Plymouth can actually do that. (Ray?) Also, this doesn't solve the Also, it doesn't solve the problem in cases where one isn't running plymouth, which I hope is a use case that systemd intends to take seriously. Well, I think if we don't show progress bars if Plymouth isn't used then that's completly OK. Also, AFAIK we don't officially support Plymouth-less boots on Fedora right now, even though it should actually work quite well and in systemd in general we definitely want to support boots both with and without Plymouth. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
state of systemd in Fedora and services pledge
Hi, I wonder what is the actual state of Fedora systemd integration? I hope that there is more systemd native services than listed on https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability Currently I have quite a lot of work, but I make a systemd services pledge - I'll write three services per week if 10 other people do the same http://www.pledgebank.com/systemdservices -- Best regards, Michal http://eventhorizon.pl/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Plan for tomorrow's FESCo meeting (2011-02-23)
Following is the list of topics that will be discussed in the FESCo meeting tomorrow at 17:30UTC (12:30pm EDT) in #fedora-meeting on irc.freenode.net. Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #516 Updates policy adjustments/changes .fesco 516 #topic #515 Investigate a features repo for stable releases .fesco 515 #topic #517 Updates Metrics .fesco 517 #544 List of services that may start by default .fesco 544 == New Business == #563 suggested policy: all daemons must set RELRO and PIE flags .fesco 563 #275 Propose a soft-path via co-maintainer status to becoming sponsored .fesco 275 #531 Orphaned package ownership claiming clarification .fesco 531 = Fedora Engineering Services tickets = https://fedorahosted.org/fedora-engineering-services/report/6 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Plans for BTRFS in Fedora
Hello, So we're getting close to having a working fsck tool so I wanted to take the opportunity to talk about the future of BTRFS in Fedora. Coming up in F15 we're going to have the first release of Fedora where we don't need the special boot option to have the ability to format you filesystem as BTRFS. This is in hopes that we can open it up for wider testing before possibly making it the default filesystem. I realize we're in the early stages of F15, but since filesystems are big and important I'd like to get an idea of the amount of work that needs to still be done to get BTRFS in shape for being Fedora's default filesystem. So here are my goals 1) Fedora 16 ships with BTRFS as the default root filesystem. 2) Fedora 16 ships without LVM as the volume manager and instead use BTRFS's built in volume management, again just for the default. Fedora 16 is a very aggressive target, which is also why I'm bringing it up now. I think we will be ready by then. We have had the ability to install Fedora onto BTRFS since F11, and I have been testing it since then without too many issues. Some things that I know are going to be gotcha's at this point 1) GRUB support. Edward Shishkin did GRUB1 patches for BTRFS a while ago, but they were obviously never merged upstream and were also not included into fedora. These would either need to be cleaned up and put into our grub package, or we'd need to put /boot on a different filesystem. I personally hate the idea of having a non-btrfs /boot partition but I'm not the one in charge of GRUB. 2) Anaconda support. I've already talked with Will Woods about this some. Really anaconda will format a normal disk with BTRFS with no problem today, the biggest issue here is adding the volume management stuff and allowing users to create subvolumes via anaconda. 3) All the various little tools that we have for putting together LiveCD's that are very ext* centered. I've not even looked at this yet, but I assume it's going to be kind of a pain. 4) FSCK does actually need to be finished. I don't see this as a problem as Chris is 90% done with it at this point so it should be ready even before F15 ships, but it's worth mentioning. I would really like to see a lot of testing on BTRFS in the F15 cycle just so we know how well it works in the non-developer's use case. It's easy for me to use it because I work on it and I understand the limitations, so it would be nice to have much broader testing. So what are your thoughts? Thanks, Josef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2011-02-23)
Hi, 2011/2/22 Kevin Fenzi ke...@scrye.com: Following is the list of topics that will be discussed in the FESCo meeting tomorrow at 17:30UTC (12:30pm EDT) in #fedora-meeting on irc.freenode.net. Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #516 Updates policy adjustments/changes .fesco 516 #topic #515 Investigate a features repo for stable releases .fesco 515 #topic #517 Updates Metrics .fesco 517 #544 List of services that may start by default .fesco 544 Please post a log after the meeting == New Business == #563 suggested policy: all daemons must set RELRO and PIE flags .fesco 563 #275 Propose a soft-path via co-maintainer status to becoming sponsored .fesco 275 #531 Orphaned package ownership claiming clarification .fesco 531 = Fedora Engineering Services tickets = https://fedorahosted.org/fedora-engineering-services/report/6 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. kevin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Best regards, Michal http://eventhorizon.pl/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On Tue, 22 Feb 2011 14:51:50 -0500 Josef Bacik jo...@toxicpanda.com wrote: Hello, So we're getting close to having a working fsck tool so I wanted to take the opportunity to talk about the future of BTRFS in Fedora. ...snip... 1) GRUB support. Edward Shishkin did GRUB1 patches for BTRFS a while ago, but they were obviously never merged upstream and were also not included into fedora. These would either need to be cleaned up and put into our grub package, or we'd need to put /boot on a different filesystem. I personally hate the idea of having a non-btrfs /boot partition but I'm not the one in charge of GRUB. Perhaps if we are going to the pain of getting btrfs patches working and stable, we could just look at moving to grub2? ...snip... So what are your thoughts? Thanks, Sounds good. I'd suggest filing a feature page already and getting it setup with all the status, etc. That can be a central point for coordinating that effort. Josef 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 (2011-02-23)
On Tue, 22 Feb 2011 20:55:26 +0100 Michał Piotrowski mkkp...@gmail.com wrote: Hi, ...snip... #544 List of services that may start by default .fesco 544 Please post a log after the meeting I always do. ;) Note that I wasn't sure if we are even going to discuss that this week, as it's still somewhat up in the air if FPC is going to handle this fully, handle it moving forward, or not handle it at all. ;) See the above ticket for more info and the FPC's ticket on it. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
1) Fedora 16 ships with BTRFS as the default root filesystem. 2) Fedora 16 ships without LVM as the volume manager and instead use BTRFS's built in volume management, again just for the default. 2) Anaconda support. I've already talked with Will Woods about this some. Really anaconda will format a normal disk with BTRFS with no problem today, the biggest issue here is adding the volume management stuff and allowing users to create subvolumes via anaconda. Given the slate of changes we have lined up for F16 anaconda (https://fedoraproject.org/wiki/Anaconda/Features), I don't know that adding another major storage change is going to happen. I think in large part, we were hoping to be done with major storage changes for a release or two and work on other less touched areas instead (like the UI). But, perhaps we can find some time somewhere. Knowing what the scope of changes looks like might help with the planning a bit. - Chris -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On Tue, Feb 22, 2011 at 3:00 PM, Kevin Fenzi ke...@scrye.com wrote: On Tue, 22 Feb 2011 14:51:50 -0500 Josef Bacik jo...@toxicpanda.com wrote: Hello, So we're getting close to having a working fsck tool so I wanted to take the opportunity to talk about the future of BTRFS in Fedora. ...snip... 1) GRUB support. Edward Shishkin did GRUB1 patches for BTRFS a while ago, but they were obviously never merged upstream and were also not included into fedora. These would either need to be cleaned up and put into our grub package, or we'd need to put /boot on a different filesystem. I personally hate the idea of having a non-btrfs /boot partition but I'm not the one in charge of GRUB. Perhaps if we are going to the pain of getting btrfs patches working and stable, we could just look at moving to grub2? Well I don't think cleaning up the existing patches will be that big of a deal, it's mostly a matter of testing. The problem with GRUB2 is it's GPLv3, explicitly to be a giant pain in the ass for porting any new fs to GRUB since we're all GPLv2 only. Aren't open source licenses grand? ...snip... So what are your thoughts? Thanks, Sounds good. I'd suggest filing a feature page already and getting it setup with all the status, etc. That can be a central point for coordinating that effort. Sounds good, I'll do that, thank you, Josef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
1) GRUB support. Edward Shishkin did GRUB1 patches for BTRFS a while ago, but they were obviously never merged upstream and were also not included into fedora. These would either need to be cleaned up and put into our grub package, or we'd need to put /boot on a different filesystem. I personally hate the idea of having a non-btrfs /boot partition but I'm not the one in charge of GRUB. Perhaps if we are going to the pain of getting btrfs patches working and stable, we could just look at moving to grub2? It's planned: https://fedoraproject.org/wiki/Anaconda/Features/Grub2Migration - Chris -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On 02/22/2011 02:51 PM, Josef Bacik wrote: Hello, So we're getting close to having a working fsck tool so I wanted to take the opportunity to talk about the future of BTRFS in Fedora. Coming up in F15 we're going to have the first release of Fedora where ... So what are your thoughts? Thanks, Josef Exciting indeed - also do you happen to know the status of RAID 5 support ? If I recall correctly, the kernel part was completed some time back .. (several months) but the higher level stuff was not ready back then. thanks gene -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
fail to install gcc on fresh rawhide-from-F15
Hi, With some effort, and help from the guys on #anaconda@freenode (thanks!), today I finally installed a bare-metal F15 system (part of the complication was my existing partitions). Then I updated it to rawhide. However, the whole point of this was to be able to compile and test some things, yet I cannot install gcc: # yum install gcc Loaded plugins: langpacks, presto, refresh-packagekit Adding en_US to language list Setting up Install Process Resolving Dependencies -- Running transaction check --- Package gcc.x86_64 0:4.3.1-6 will be installed -- Processing Dependency: cpp = 4.3.1-6 for package: gcc-4.3.1-6.x86_64 -- Processing Dependency: libgomp = 4.3.1-6 for package: gcc-4.3.1-6.x86_64 -- Processing Dependency: glibc-devel = 2.2.90-12 for package: gcc-4.3.1-6.x86_64 -- Running transaction check --- Package gcc.x86_64 0:4.3.1-6 will be installed -- Processing Dependency: cpp = 4.3.1-6 for package: gcc-4.3.1-6.x86_64 --- Package glibc-devel.x86_64 0:2.8.90-11 will be installed -- Processing Dependency: glibc = 2.8.90-11 for package: glibc-devel-2.8.90-11.x86_64 -- Processing Dependency: glibc-headers = 2.8.90-11 for package: glibc-devel-2.8.90-11.x86_64 --- Package libgomp.i386 0:4.3.1-6 will be installed -- Running transaction check --- Package gcc.x86_64 0:4.3.1-6 will be installed -- Processing Dependency: cpp = 4.3.1-6 for package: gcc-4.3.1-6.x86_64 --- Package glibc.i686 0:2.8.90-11 will be installed -- Processing Dependency: glibc-common = 2.8.90-11 for package: glibc-2.8.90-11.i686 --- Package glibc-headers.x86_64 0:2.8.90-11 will be installed -- Finished Dependency Resolution Error: Package: glibc-2.8.90-11.i686 (rawhide) Requires: glibc-common = 2.8.90-11 Installed: glibc-common-2.13.90-4.x86_64 (@updates-testing/15) glibc-common = 2.13.90-4 Available: glibc-common-2.8.90-11.x86_64 (rawhide) glibc-common = 2.8.90-11 Error: Package: gcc-4.3.1-6.x86_64 (rawhide) Requires: cpp = 4.3.1-6 Installed: cpp-4.6.0-0.7.fc15.x86_64 (@rawhide) cpp = 4.6.0-0.7.fc15 Available: cpp-4.3.1-6.x86_64 (rawhide) cpp = 4.3.1-6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Unfortunately, neither of those you could try ... suggestions helps. Can anyone suggest an easy way out, or should I just wait for a day or two? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 679313] perl-SDL is out of date 2.1.3-13 (~2007)
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=679313 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System upda...@fedoraproject.org 2011-02-22 16:48:48 EST --- perl-SDL-2.2.6-1.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update perl-SDL'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/perl-SDL-2.2.6-1.fc15 -- 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: Plans for BTRFS in Fedora
On Tue, 22.02.11 14:51, Josef Bacik (jo...@toxicpanda.com) wrote: Hello, So we're getting close to having a working fsck tool so I wanted to take the opportunity to talk about the future of BTRFS in Fedora. Coming up in F15 we're going to have the first release of Fedora where we don't need the special boot option to have the ability to format you filesystem as BTRFS. This is in hopes that we can open it up for wider testing before possibly making it the default filesystem. I realize we're in the early stages of F15, but since filesystems are big and important I'd like to get an idea of the amount of work that needs to still be done to get BTRFS in shape for being Fedora's default filesystem. So here are my goals 1) Fedora 16 ships with BTRFS as the default root filesystem. Hmm, what are your plans regarding hierarchy layout for this? My hope is that one day we can ship a read-only root dir by default, or more specifically a btrfs file system with three subvolumes in it: one read-only one mounted to /, and two writable ones mounted to /home and /var, with /tmp mounted from tmpfs. We came a long way with supporting read-only root dirs and it should mostly work now. In F15 for example /etc/mtab is a symlink, and even smaller stuff like /etc/nologin got moved to /var/run, to make write accesses to /etc unnecessary during normal operation. /etc/resolv.conf is the only thing often updated that's left, but with NM using dnsmasq it's static too. By using btrfs subvolumes doing this kind of seperation into writable and non-writable subtrees we don't have to think anymore about the sizes for those file systems at install time, since they all live in the same fs. If this is adopted package managers and system configuration UIs would need to invoke mount / -o rw,remount before doing their work. So, I'd like to see this implemented one day, maybe the adoption of btrfs is the right time to push this through too? I have not filed a feature page for this, as I am not sure I want to push this on F16, and I don't even know if people in general are onboard with this idea. The benefits of this are mostly security and robustness since we know that the actual subvolume the OS is booted from is always in a consistent state during operation and cannot normally be changed. And of course, we get all kind of magic by doing this because we can easily use snapshots to roll back system upgrades while leaving /home completely untouched. Sorry for hijacking your thread like this, Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: state of systemd in Fedora and services pledge
On Tue, 2011-02-22 at 20:40 +0100, Michał Piotrowski wrote: Hi, I wonder what is the actual state of Fedora systemd integration? I hope that there is more systemd native services than listed on https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability I'm planning on review and update that list after alpha. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 679589] [abrt] perl-Padre-0.64-1.fc14: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=679589 --- Comment #1 from Simon Lachance simon...@yahoo.ca 2011-02-22 17:20:27 EST --- Created attachment 480282 -- https://bugzilla.redhat.com/attachment.cgi?id=480282 File: backtrace -- 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
[Bug 679589] New: [abrt] perl-Padre-0.64-1.fc14: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] perl-Padre-0.64-1.fc14: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=679589 Summary: [abrt] perl-Padre-0.64-1.fc14: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) Product: Fedora Version: 14 Platform: i686 OS/Version: Unspecified Status: NEW Status Whiteboard: abrt_hash:88683063c3eb109ed94c48c6eb9878778fccb558 Severity: unspecified Priority: unspecified Component: perl-Padre AssignedTo: mmasl...@redhat.com ReportedBy: simon...@yahoo.ca QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, mmasl...@redhat.com Classification: Fedora abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 23385 bytes cmdline: /usr/bin/perl /usr/bin/padre component: perl-Padre Attached file: coredump, 20643840 bytes crash_function: wxControlContainer::SetLastFocus(wxWindow*) executable: /usr/bin/perl kernel: 2.6.35.11-83.fc14.i686.PAE package: perl-Padre-0.64-1.fc14 rating: 4 reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1298412674 uid: 500 How to reproduce - 1.open terminal on Gnome 3 using gnome-terminal after Alt-F2 2.type padre in terminal 3. -- 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: fail to install gcc on fresh rawhide-from-F15
On Tue, 22 Feb 2011 22:38:24 +0100 Jim Meyering j...@meyering.net wrote: With some effort, and help from the guys on #anaconda@freenode (thanks!), today I finally installed a bare-metal F15 system (part of the complication was my existing partitions). Then I updated it to rawhide. However, the whole point of this was to be able to compile and test some things, yet I cannot install gcc: # yum install gcc (clip) Error: Package: gcc-4.3.1-6.x86_64 (rawhide) Requires: cpp = 4.3.1-6 Installed: cpp-4.6.0-0.7.fc15.x86_64 (@rawhide) cpp = 4.6.0-0.7.fc15 Available: cpp-4.3.1-6.x86_64 (rawhide) cpp = 4.3.1-6 I'd say there's something seriously wrong with your yum configuration or the rawhide mirror you've been using. There hasn't been a gcc-4.3.1 in Fedora for a couple of years. Check that the rawhide yum configuration (package fedora-release-rawhide) is installed, run # yum clean all and try again. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
[...btrfs and read-only root,/etc...] Music to my ears. Glad you're working on this. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
Josef Bacik writes: 2) Fedora 16 ships without LVM as the volume manager and instead use BTRFS's built in volume management, again just for the default. Just to clarify -- F16 will still have LVM, but not used by default. I believe that there's a huge number of existing systems that are partitioned using LVM. pgpY1YS4gcSHd.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On Tue, 2011-02-22 at 14:51 -0500, Josef Bacik wrote: So what are your thoughts? Thanks, Will there be any performance penalties making this move? I ran it on my workstation when F13 came out with updates+snapshots and while updating my desktop responsiveness was well not so good. Novice end users tools ( GUI ) and policy to clean those snapshots and perhaps storing those snapshots in it's own directory and or partition rather than directly on / need be in place before we implement this as an default. I suggest people try it during the F15 atleast those that are considering as an default to catch any potential usability issues it did not eat any babes from me when I ran it. I think we should also ask ourselves these questions.. What benefit will this switch bring to the novice desktop end users? Will the novice desktop end user ever take advantages of any of the features that btrfs brings? Just my 0.0.2 cents.. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: state of systemd in Fedora and services pledge
2011/2/22 Michał Piotrowski mkkp...@gmail.com: Hi, I wonder what is the actual state of Fedora systemd integration? I hope that there is more systemd native services than listed on https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability Currently I have quite a lot of work, but I make a systemd services pledge - I'll write three services per week if 10 other people do the same http://www.pledgebank.com/systemdservices uh... How are you creating the spec file? In testing, I've yet to get a specfile that performs as expected. I'd be happy if you could take a look at the proposed guidelines and figure out if this is a guidelines bug, a systemd bug, a testing bug, or a bug in the packages that I'm testing with. Packages testing with: http://toshio.fedorapeople.org/systemd Proposed Guidelines: https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft FPC Ticket that has a comment with the steps that I tried to test: https://fedorahosted.org/fpc/ticket/31 -Toshio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: fail to install gcc on fresh rawhide-from-F15
On Tue, 2011-02-22 at 22:38 +0100, Jim Meyering wrote: Hi, With some effort, and help from the guys on #anaconda@freenode (thanks!), today I finally installed a bare-metal F15 system (part of the complication was my existing partitions). Then I updated it to rawhide. However, the whole point of this was to be able to compile and test some things, yet I cannot install gcc: # yum install gcc [...] Error: Package: glibc-2.8.90-11.i686 (rawhide) Requires: glibc-common = 2.8.90-11 Installed: glibc-common-2.13.90-4.x86_64 (@updates-testing/15) glibc-common = 2.13.90-4 Available: glibc-common-2.8.90-11.x86_64 (rawhide) glibc-common = 2.8.90-11 Newer glibc in F15 than in rawhide, so yum won't go backwards for glibc-devel ... it tries to go with the .i686 instead (do you not have protected_multilib set?), but that doesn't work out either. distro-sync glibc* on rawhide ... or get glibc-devel from F-15. Error: Package: gcc-4.3.1-6.x86_64 (rawhide) Requires: cpp = 4.3.1-6 Installed: cpp-4.6.0-0.7.fc15.x86_64 (@rawhide) cpp = 4.6.0-0.7.fc15 Available: cpp-4.3.1-6.x86_64 (rawhide) cpp = 4.3.1-6 Dito. cpp. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Orphaning some (GNOMEy) packages
Here's the list of packages, with reasons: - gnome-launch-box, replaced by gnome-shell's builtin features (mostly, filed bugs for the rest) - libgalago, libgalago-gtk, replaced within GNOME with session-wide features, but could still be used by supported applications. First come, first serve. Cheers -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: state of systemd in Fedora and services pledge
On Tue, 22.02.11 12:19, Toshio Kuratomi (a.bad...@gmail.com) wrote: 2011/2/22 Michał Piotrowski mkkp...@gmail.com: Hi, I wonder what is the actual state of Fedora systemd integration? I hope that there is more systemd native services than listed on https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability Currently I have quite a lot of work, but I make a systemd services pledge - I'll write three services per week if 10 other people do the same http://www.pledgebank.com/systemdservices uh... How are you creating the spec file? In testing, I've yet to get a specfile that performs as expected. I'd be happy if you could take a look at the proposed guidelines and figure out if this is a guidelines bug, a systemd bug, a testing bug, or a bug in the packages that I'm testing with. Did you actually check if you had at least chkconfig 1.3.50-1 installed when you tested this, as I wrote in the FPC bug? Also, Michał's work is about adding systemd unit files, not about adding SysV init scripts, because those already exist... Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On Tue, Feb 22, 2011 at 5:07 PM, Lennart Poettering mzerq...@0pointer.de wrote: On Tue, 22.02.11 14:51, Josef Bacik (jo...@toxicpanda.com) wrote: Hello, So we're getting close to having a working fsck tool so I wanted to take the opportunity to talk about the future of BTRFS in Fedora. Coming up in F15 we're going to have the first release of Fedora where we don't need the special boot option to have the ability to format you filesystem as BTRFS. This is in hopes that we can open it up for wider testing before possibly making it the default filesystem. I realize we're in the early stages of F15, but since filesystems are big and important I'd like to get an idea of the amount of work that needs to still be done to get BTRFS in shape for being Fedora's default filesystem. So here are my goals 1) Fedora 16 ships with BTRFS as the default root filesystem. Hmm, what are your plans regarding hierarchy layout for this? My hope is that one day we can ship a read-only root dir by default, or more specifically a btrfs file system with three subvolumes in it: one read-only one mounted to /, and two writable ones mounted to /home and /var, with /tmp mounted from tmpfs. Yeah the hope is to separate out various things into different subvolumes so we can have things that can be independently snapshottable things. We came a long way with supporting read-only root dirs and it should mostly work now. In F15 for example /etc/mtab is a symlink, and even smaller stuff like /etc/nologin got moved to /var/run, to make write accesses to /etc unnecessary during normal operation. /etc/resolv.conf is the only thing often updated that's left, but with NM using dnsmasq it's static too. By using btrfs subvolumes doing this kind of seperation into writable and non-writable subtrees we don't have to think anymore about the sizes for those file systems at install time, since they all live in the same fs. If this is adopted package managers and system configuration UIs would need to invoke mount / -o rw,remount before doing their work. So, I'd like to see this implemented one day, maybe the adoption of btrfs is the right time to push this through too? I have not filed a feature page for this, as I am not sure I want to push this on F16, and I don't even know if people in general are onboard with this idea. The benefits of this are mostly security and robustness since we know that the actual subvolume the OS is booted from is always in a consistent state during operation and cannot normally be changed. And of course, we get all kind of magic by doing this because we can easily use snapshots to roll back system upgrades while leaving /home completely untouched. Sorry for hijacking your thread like this, It's cool, just hilights all the cool stuff we can do with BTRFS :). Thanks, Josef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
2011/2/22 Jóhann B. johan...@gmail.com: On Tue, 2011-02-22 at 14:51 -0500, Josef Bacik wrote: So what are your thoughts? Thanks, Will there be any performance penalties making this move? Who knows, thats what testing is for :). There are some things that suck with BTRFS, but so it goes with filesystems. I ran it on my workstation when F13 came out with updates+snapshots and while updating my desktop responsiveness was well not so good. Novice end users tools ( GUI ) and policy to clean those snapshots and perhaps storing those snapshots in it's own directory and or partition rather than directly on / need be in place before we implement this as an default. They would be helpful, but not necessary. I suggest people try it during the F15 atleast those that are considering as an default to catch any potential usability issues it did not eat any babes from me when I ran it. I think we should also ask ourselves these questions.. What benefit will this switch bring to the novice desktop end users? Various things, better data integrity to start with, and if you install the yum-fs-snapshot you have the ability to rollback easily. Will the novice desktop end user ever take advantages of any of the features that btrfs brings? At the very least you get better data integrity via our checksumming and duplicate metadata on single spindle fs's. Thanks, Josef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On Tue, 2011-02-22 at 14:51 -0500, Josef Bacik wrote: 2) Fedora 16 ships without LVM as the volume manager and instead use BTRFS's built in volume management, again just for the default. In my personal opinion, this is a poor design decision. Yes, BTRFS can do a lot of volume-y things, and these are growing by the day, but I don't want my filesystem replacing a full volume manager and I am concerned that this will lead to less testing and exposure to full LVM use within the Fedora community. Instead, I'd like to counter-propose that everything stay exactly as it is, with users being able to elect to switch to BTRFS (sub)volumes if they are interested in doing so. Should the switch to BTRFS by default happen, this will be one more thing I will have to fix immediately during installation. The list grows longer and longer over time - please don't make this change. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
ABRT bugs for EOL products
I just got an ABRT bug for a Fedora 12 package [1]. Can we prevent bugs being filed for EOL products? Who needs to handle this? Is this a known issue? Thanks! - Orion [1] - https://bugzilla.redhat.com/show_bug.cgi?id=679584 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plans for BTRFS in Fedora
On Tue, Feb 22, 2011 at 14:51:50 -0500, Josef Bacik jo...@toxicpanda.com wrote: 3) All the various little tools that we have for putting together LiveCD's that are very ext* centered. I've not even looked at this yet, but I assume it's going to be kind of a pain. I like to see live CDs just use squashfs directly and not a squashed copy of an ext3/4 image. However this will break using dd to copy the image for installs which will slow things down. Further however, there is at least some interest in having live CDs and ananconda share the same install method, so this might be happening in any case. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Broken dependencies: perl-Kwiki-RecentChanges
perl-Kwiki-RecentChanges has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-RecentChanges-0.14-12.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-RecentChanges-0.14-12.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-Search
perl-Kwiki-Search has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-Search-0.12-14.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-Search-0.12-14.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-Revisions
perl-Kwiki-Revisions has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-Revisions-0.15-14.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-Revisions-0.15-14.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-JSON-RPC
perl-JSON-RPC has broken dependencies in the F-15 tree: On x86_64: perl-JSON-RPC-0.96-7.fc15.noarch requires perl(MyApp) On i386: perl-JSON-RPC-0.96-7.fc15.noarch requires perl(MyApp) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Declare-Constraints-Simple
perl-Declare-Constraints-Simple has broken dependencies in the F-15 tree: On x86_64: perl-Declare-Constraints-Simple-0.03-11.fc15.noarch requires perl(Declare::Constraints::Simple-Library) On i386: perl-Declare-Constraints-Simple-0.03-11.fc15.noarch requires perl(Declare::Constraints::Simple-Library) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Data-ObjectDriver
perl-Data-ObjectDriver has broken dependencies in the F-15 tree: On x86_64: perl-Data-ObjectDriver-0.08-2.fc15.noarch requires perl(DBD::Oracle) perl-Data-ObjectDriver-0.08-2.fc15.noarch requires perl(DBI::db) On i386: perl-Data-ObjectDriver-0.08-2.fc15.noarch requires perl(DBD::Oracle) perl-Data-ObjectDriver-0.08-2.fc15.noarch requires perl(DBI::db) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-Users-Remote
perl-Kwiki-Users-Remote has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-Users-Remote-0.04-12.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-Users-Remote-0.04-12.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-UserName
perl-Kwiki-UserName has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-UserName-0.14-14.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-UserName-0.14-14.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-CGI-Application-Structured-Tools
perl-CGI-Application-Structured-Tools has broken dependencies in the F-15 tree: On x86_64: perl-CGI-Application-Structured-Tools-0.007-4.fc15.noarch requires main_module) perl-CGI-Application-Structured-Tools-0.007-4.fc15.noarch requires perl(tmpl_var) perl-CGI-Application-Structured-Tools-0.007-4.fc15.noarch requires perl(tmpl_var On i386: perl-CGI-Application-Structured-Tools-0.007-4.fc15.noarch requires main_module) perl-CGI-Application-Structured-Tools-0.007-4.fc15.noarch requires perl(tmpl_var) perl-CGI-Application-Structured-Tools-0.007-4.fc15.noarch requires perl(tmpl_var Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Gtk2-Ex-Carp
perl-Gtk2-Ex-Carp has broken dependencies in the F-15 tree: On x86_64: perl-Gtk2-Ex-Carp-0.01-10.fc15.noarch requires perl(Gtk2::Dialog) On i386: perl-Gtk2-Ex-Carp-0.01-10.fc15.noarch requires perl(Gtk2::Dialog) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Object-InsideOut
perl-Object-InsideOut has broken dependencies in the F-15 tree: On x86_64: perl-Object-InsideOut-3.56-5.fc15.noarch requires perl(t::Imp1) perl-Object-InsideOut-3.56-5.fc15.noarch requires perl(t::Imp2) On i386: perl-Object-InsideOut-3.56-5.fc15.noarch requires perl(t::Imp1) perl-Object-InsideOut-3.56-5.fc15.noarch requires perl(t::Imp2) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Ace
perl-Ace has broken dependencies in the F-15 tree: On x86_64: perl-Ace-1.92-7.fc15.noarch requires perl(Ace::Browser::LocalSiteDefs) On i386: perl-Ace-1.92-7.fc15.noarch requires perl(Ace::Browser::LocalSiteDefs) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-CSS-DOM
perl-CSS-DOM has broken dependencies in the F-15 tree: On x86_64: perl-CSS-DOM-0.14-3.fc15.noarch requires perl() On i386: perl-CSS-DOM-0.14-3.fc15.noarch requires perl() Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Pugs-Compiler-Rule
perl-Pugs-Compiler-Rule has broken dependencies in the F-15 tree: On x86_64: perl-Pugs-Compiler-Rule-0.37-8.fc15.noarch requires perl(v6-alpha) On i386: perl-Pugs-Compiler-Rule-0.37-8.fc15.noarch requires perl(v6-alpha) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Net-SSH-Perl
perl-Net-SSH-Perl has broken dependencies in the F-15 tree: On x86_64: perl-Net-SSH-Perl-1.34-10.fc15.noarch requires perl(Crypt::IDEA) On i386: perl-Net-SSH-Perl-1.34-10.fc15.noarch requires perl(Crypt::IDEA) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-bioperl
perl-bioperl has broken dependencies in the F-15 tree: On x86_64: perl-bioperl-1.6.1-6.fc15.noarch requires perl(Bio::Expression::FeatureSet) On i386: perl-bioperl-1.6.1-6.fc15.noarch requires perl(Bio::Expression::FeatureSet) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-DateTime-Set
perl-DateTime-Set has broken dependencies in the F-15 tree: On x86_64: perl-DateTime-Set-0.28-4.fc15.noarch requires perl(Set::Infinite) = 0:0.5502 On i386: perl-DateTime-Set-0.28-4.fc15.noarch requires perl(Set::Infinite) = 0:0.5502 Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-UserPreferences
perl-Kwiki-UserPreferences has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-UserPreferences-0.13-13.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-UserPreferences-0.13-13.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-Raw
perl-Kwiki-Raw has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-Raw-0.02-13.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-Raw-0.02-13.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-DBIx-ContextualFetch
perl-DBIx-ContextualFetch has broken dependencies in the F-15 tree: On x86_64: perl-DBIx-ContextualFetch-1.03-11.fc15.noarch requires perl(DBI::st) perl-DBIx-ContextualFetch-1.03-11.fc15.noarch requires perl(DBI::db) On i386: perl-DBIx-ContextualFetch-1.03-11.fc15.noarch requires perl(DBI::st) perl-DBIx-ContextualFetch-1.03-11.fc15.noarch requires perl(DBI::db) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki
perl-Kwiki has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-0.39-10.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-0.39-10.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Kwiki-NewPage
perl-Kwiki-NewPage has broken dependencies in the F-15 tree: On x86_64: perl-Kwiki-NewPage-0.12-14.fc15.noarch requires perl(mixin) On i386: perl-Kwiki-NewPage-0.12-14.fc15.noarch requires perl(mixin) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Catalyst-Controller-FormBuilder
perl-Catalyst-Controller-FormBuilder has broken dependencies in the F-15 tree: On x86_64: perl-Catalyst-Controller-FormBuilder-0.05-7.fc15.noarch requires perl(Catalyst::View::HTML::Template) On i386: perl-Catalyst-Controller-FormBuilder-0.05-7.fc15.noarch requires perl(Catalyst::View::HTML::Template) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Manipulate Dev. release number properly
Hi! RPM doen't generate proper version numbers for Dev. releases of modules. For example, perl(CPAN) of f14 is actually 1.94_56 which just means 1.9456. But the version generated by RPM is 1.94, much smaller than the actual version. So I hope RPM can manipulate the underscores in version numbers properly. Regards. Robin -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[389-devel] Please Review: (493424) remove unneeded modules for admin server apache config
https://bugzilla.redhat.com/show_bug.cgi?id=493424 https://bugzilla.redhat.com/attachment.cgi?id=480295action=edit -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
