Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 03:41 +, Jóhann B. Guðmundsson wrote: The decision to reject this feature certainly was a lesson in killing momentum which we will never reach again. JBG Ps. Yes I'm pissed and I have every right to be I eventually will get over it and so will you over my rant. I understand, but please don't personalize the argument - FESCo didn't make the decision on any kind of personal grounds, but on technical grounds (worries about whether we would be able to complete backwards compatibility and documentation work in time). They didn't really 'reject' systemd but simply delayed it to F15. All the work we all did on systemd will still be valuable for that time frame. I do wish, though, Bill, that FESCo could have come through with this decision sooner; on a project basis it really does cut things rather fine for rolling RC1, and on a personal basis I could have not bothered with about seven hours of TC1 systemd blocker testing and triage over the last two days :( -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question: how to keep /var/lib/yum/plugins/local small?
What plugins do you have installed? I only get: # pwd /var/lib/yum # du -hs * 1.2Mhistory 0 rpmdb-indexes 4.0Kuuid 9.0Myumdb -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 On 09/15/2010 03:44 PM, Joachim Backes wrote: Is there a yum function to keep */var/lib/yum/plugins/local* small? This directory now uses about 3.0 GB after starting with F14-Alpha and applying all F14 updates. It would be nice if one could reduce the package number by some FIFO algoritm. Any ideas? Kind regards -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On 09/15/2010 11:24 AM, Michal Jaegermann wrote: There is one big difference though. Upstart does work and for a naive user this detail that /sbin/upstart handles sysvinit job is not really visible. In the case of systemd this works mostly. Definitely much better now than when it showed up for the first time but if you will scratch little deeper then various niggling imperfections show up all over. Maybe all this could be fixed in time for a release or maybe not. I think that waiting for F15 until the whole environment matures enough was a responsible decision. BTW - I run rawhide and do not plan to switch that back to upstart. Since, I am a co-maintainer of systemd and watching bugs flow through, I think we need a more concrete list of what is missing/needs to be fixed for this to be acceptable for Fedora 15. I think, off the top of my head, I would like the following * Fedora documentation, especially the longer guides to be updated to cover systemd extensively * system-config-services needs to work with systemd native units * since s-c-services uses chkconfig, chkconfig needs to be hooked up to systemctl * shutdown semantics needs to be fixed (https://bugzilla.redhat.com/show_bug.cgi?id=624149) * Direct option for switching default target (https://bugzilla.redhat.com/show_bug.cgi?id=627277) * Option to revert settings (https://bugzilla.redhat.com/show_bug.cgi?id=630174) Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
New BugZapper Introduction
Dear Zappers, My name is Simon Yan and I would like to be part of the Fedora BugZapper team to do something to make this great Linux distro even better! ;) I've started playing with Fedora since 3 and I kept using it now and then. I wasn't able to follow along with all the releases but I'll keep trying. Other than that, I used mostly RHEL/CentOS in my daily work and sometimes SLES too. I tried a bit about Unbuntu too. Now I'm majorly on a Mac but I kept VMs for Linux all the time. I work as a technical support engineer located in Beijing, China. I'm not on irc a lot but if I do I would use simony as my nick name. I would love to contribute to Fedora in as many ways as I can but as this is the first time I started get involved in the community, I needed someone to hand me over the red pill. ;) -- Regards, Simon Yan http://www.google.com/profiles/simonyanix -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] Anaconda TranslationKeyboard Test Day - Thursday 2010-09-16
Greetings Testers, Anaconda TranslationKeyboard Test Day is coming up tomorrow: https://fedoraproject.org/wiki/Test_Day:Current This day will mainly focus on the translation and keyboard in different languages during installation. Test cases have been well prepared on the wiki page with the help of l10n[1] and i18n[2] team, and the steps are clear for your reference. So if you used to install in your native language or know a second language besides English, this is an opportunity to try them out and help discover the issues in this area. F-14-beta-TC1 images are available for testing in this event, executing tests in virtual guest is also acceptable if you don't have extra space in bare metal. The Test Day will run all day in Freenode IRC #fedora-test-day. See you there!:) [1] https://fedoraproject.org/wiki/L10n [2] https://fedoraproject.org/wiki/I18N -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New BugZapper Introduction
Welcome! Li Rui Bin On Wed, Sep 15, 2010 at 2:30 PM, 益牙 simonya...@gmail.com wrote: Dear Zappers, My name is Simon Yan and I would like to be part of the Fedora BugZapper team to do something to make this great Linux distro even better! ;) I've started playing with Fedora since 3 and I kept using it now and then. I wasn't able to follow along with all the releases but I'll keep trying. Other than that, I used mostly RHEL/CentOS in my daily work and sometimes SLES too. I tried a bit about Unbuntu too. Now I'm majorly on a Mac but I kept VMs for Linux all the time. I work as a technical support engineer located in Beijing, China. I'm not on irc a lot but if I do I would use simony as my nick name. I would love to contribute to Fedora in as many ways as I can but as this is the first time I started get involved in the community, I needed someone to hand me over the red pill. ;) -- Regards, Simon Yan http://www.google.com/profiles/simonyanix -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question: how to keep /var/lib/yum/plugins/local small?
On 09/15/2010 08:04 AM, Steven Haigh wrote: What plugins do you have installed? I only get: # pwd /var/lib/yum # du -hs * 1.2M history 0 rpmdb-indexes 4.0K uuid 9.0M yumdb Hi Steven, cd /var/lib/yum sudo du -hs * 4.6Mhistory 3.8Gplugins 296Krpmdb-indexes 4.0Kuuid 19M yumdb Installed yum plugins: yum-plugin-local (has not been installed explictly, but automatically!) Joachim Backes -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 On 09/15/2010 03:44 PM, Joachim Backes wrote: Is there a yum function to keep */var/lib/yum/plugins/local* small? This directory now uses about 3.0 GB after starting with F14-Alpha and applying all F14 updates. It would be nice if one could reduce the package number by some FIFO algoritm. Any ideas? Kind regards -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question: how to keep /var/lib/yum/plugins/local small?
On 09/15/2010 05:28 PM, Joachim Backes wrote: On 09/15/2010 08:04 AM, Steven Haigh wrote: What plugins do you have installed? I only get: # pwd /var/lib/yum # du -hs * 1.2M history 0rpmdb-indexes 4.0K uuid 9.0M yumdb Hi Steven, cd /var/lib/yum sudo du -hs * 4.6M history 3.8G plugins 296K rpmdb-indexes 4.0K uuid 19M yumdb Installed yum plugins: yum-plugin-local (has not been installed explictly, but automatically!) H - I didn't get that plugin installed - nor is it really required unless you want it... Remove the plugin and you can probably remove the plugins directory completely with no loss of functionality... -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question: how to keep /var/lib/yum/plugins/local small?
On 15/09/10 08:28, Joachim Backes wrote: Installed yum plugins: yum-plugin-local (has not been installed explictly, but automatically!) Joachim Backes If you don't need a local repo: yum erase yum*local -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Bluetooth issues after removing systemd.
Hi all, After applying the latest updates in updates-testing for F14, I cannot enable bluetooth anymore... The latest hal update fixed this, however now I'm not able to enable bluetooth at all. Anyone else? -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question: how to keep /var/lib/yum/plugins/local small?
On 09/15/2010 09:58 AM, Frank Murphy wrote: On 15/09/10 08:28, Joachim Backes wrote: Installed yum plugins: yum-plugin-local (has not been installed explictly, but automatically!) Joachim Backes If you don't need a local repo: yum erase yum*local I did it, but now, I can't downgrade an installed package :-( -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
2010/9/15 Rahul Sundaram methe...@gmail.com: On 09/15/2010 11:24 AM, Michal Jaegermann wrote: There is one big difference though. Upstart does work and for a naive user this detail that /sbin/upstart handles sysvinit job is not really visible. In the case of systemd this works mostly. Definitely much better now than when it showed up for the first time but if you will scratch little deeper then various niggling imperfections show up all over. Maybe all this could be fixed in time for a release or maybe not. I think that waiting for F15 until the whole environment matures enough was a responsible decision. BTW - I run rawhide and do not plan to switch that back to upstart. Since, I am a co-maintainer of systemd and watching bugs flow through, I think we need a more concrete list of what is missing/needs to be fixed for this to be acceptable for Fedora 15. I think, off the top of my head, I would like the following * Fedora documentation, especially the longer guides to be updated to cover systemd extensively Please point me to a similar document written for Upstart. * system-config-services needs to work with systemd native units Does it work with native Upstart jobs? * since s-c-services uses chkconfig, chkconfig needs to be hooked up to systemctl * shutdown semantics needs to be fixed (https://bugzilla.redhat.com/show_bug.cgi?id=624149) Almost fixed AFAICS * Direct option for switching default target (https://bugzilla.redhat.com/show_bug.cgi?id=627277) Is there a special tool for Upstart that modify default runlevel in inittab? * Option to revert settings (https://bugzilla.redhat.com/show_bug.cgi?id=630174) Any counterpart in the Upstart world? I do not think that this were objective criteria. Rahul Regards, Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Question: how to keep /var/lib/yum/plugins/local small?
On 15/09/10 09:22, Joachim Backes wrote: If you don't need a local repo: yum erase yum*local I did it, but now, I can't downgrade an installed package :-( You can if you havn't deleted the 3gb of files. maybe as su\sudo updatedb locate local.conf.rpmsave if that is there it will contain the path to the rpms. -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
2010/9/15 Jóhann B. Guðmundsson johan...@gmail.com: The decision to reject this feature certainly was a lesson in killing momentum which we will never reach again. This is how I also feel. By trying to make Fedora shiny, polished and super-cautious against breaking things we're just creating another Ubuntu clone. This is destroying the very reason people run Fedora in the first place: Fedora is where innovation happens. Innovation is risky, but without it we're unimportant within two releases. Richard. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
2010/9/15 Richard Hughes hughsi...@gmail.com: 2010/9/15 Jóhann B. Guðmundsson johan...@gmail.com: The decision to reject this feature certainly was a lesson in killing momentum which we will never reach again. This is how I also feel. By trying to make Fedora shiny, polished and super-cautious against breaking things we're just creating another Ubuntu clone. This is destroying the very reason people run Fedora in the first place: Fedora is where innovation happens. Innovation is risky, but without it we're unimportant within two releases. Frankly, this list without Systemd will look featureless https://fedoraproject.org/wiki/FeatureList But on the other hand development of Systemd will not be constrained by oh my god, we need to update our new init in stable, disaster! :) Richard. Regards, Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Broken dependencies with Fedora 13 + updates-testing - 2010-09-15
== The results in this summary consider Test Updates! == Broken packages in F-13 + Updates (src.rpm names): almanah gcc (ignored, releng #4084) intellij-idea perl(ignored, multiarch breakage) syncevolution Additional broken packages with Test Updates (src.rpm names): almanah anjuta gedit-vala mozc mumble perl(ignored, multiarch breakage) valide == Broken packages in fedora-13-i386: gedit-vala-0.6.1-1.fc13.i686 requires libvala.so.0 intellij-idea-9.0.1.94.399-10.fc13.i686 requires jna-examples == Broken packages in fedora-13-x86_64: 4:perl-5.10.1-112.fc13.i686 requires perl-libs = 4:5.10.1-112.fc13 gcc-gfortran-4.4.4-2.fc13.i686 requires gcc = 0:4.4.4-2.fc13 gcc-gfortran-4.4.4-2.fc13.i686 requires libgfortran = 0:4.4.4-2.fc13 gedit-vala-0.6.1-1.fc13.x86_64 requires libvala.so.0()(64bit) intellij-idea-9.0.1.94.399-10.fc13.x86_64 requires jna-examples syncevolution-0.9.2+1.0alpha1-1.fc13.i686 requires libedataserver-1.2.so.11 == Broken packages in fedora-updates-13-i386: 1:anjuta-2.30.2.1-1.fc13.i686 requires libvala.so.0 valide-0.7-0.28.20101105svn609.fc13.i686 requires libvala.so.0 == Broken packages in fedora-updates-13-x86_64: 1:anjuta-2.30.2.1-1.fc13.i686 requires libvala.so.0 1:anjuta-2.30.2.1-1.fc13.x86_64 requires libvala.so.0()(64bit) 4:perl-libs-5.10.1-116.fc13.i686 requires perl = 4:5.10.1-116.fc13 valide-0.7-0.28.20101105svn609.fc13.i686 requires libvala.so.0 valide-0.7-0.28.20101105svn609.fc13.x86_64 requires libvala.so.0()(64bit) == Broken packages in fedora-updates-testing-13-i386: almanah-0.7.3-1.fc13.i686 requires libedataserver-1.2.so.11 ibus-mozc-0.13.464.102-0.1.20100910svn.fc13.i686 requires libprotobuf.so.4 mozc-0.13.464.102-0.1.20100910svn.fc13.i686 requires libprotobuf.so.4 mumble-1.2.2-10.fc13.i686 requires libprotobuf.so.4 murmur-1.2.2-10.fc13.i686 requires libprotobuf.so.4 scim-mozc-0.13.464.102-0.1.20100910svn.fc13.i686 requires libprotobuf.so.4 == Broken packages in fedora-updates-testing-13-x86_64: almanah-0.7.3-1.fc13.x86_64 requires libedataserver-1.2.so.11()(64bit) ibus-mozc-0.13.464.102-0.1.20100910svn.fc13.x86_64 requires libprotobuf.so.4()(64bit) mozc-0.13.464.102-0.1.20100910svn.fc13.x86_64 requires libprotobuf.so.4()(64bit) mumble-1.2.2-10.fc13.x86_64 requires libprotobuf.so.4()(64bit) murmur-1.2.2-10.fc13.x86_64 requires libprotobuf.so.4()(64bit) scim-mozc-0.13.464.102-0.1.20100910svn.fc13.x86_64 requires libprotobuf.so.4()(64bit) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #126: Proposed Test Day - openldap with Mozilla NSS for crypto
#126: Proposed Test Day - openldap with Mozilla NSS for crypto ---+ Reporter: rmeggins | Owner: kparal Type: task | Status: new Priority: critical | Milestone: Component: Test Day | Version: Resolution:|Keywords: ---+ Comment (by jlaska): Replying to [comment:2 kparal]: I can take ownership of this, most of the developers organizing this event are from Brno. James, what do you think about the proposed date? Sorry for the delayed response. I don't have any concerns around the proposed date. Let's just make sure all involved understand how the date may impact the ability to incorporate bug fixes into the release. For example, 2010-10-18 is currently the final change deadline for F14. This means that only critical blocker issues impacting the release criteria will accepted after the date. With the test day proposed on 2010-10-14, there isn't a lot of time to incorporate any nice-to-have changes. However, there is no reason the changes can't be pushed out as a day0 update available after 'yum update'. non-long winded version ... I don't have any issues with the date, thanks! :) -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/126#comment:4 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 10:27 +0200, Michał Piotrowski wrote: * Fedora documentation, especially the longer guides to be updated to cover systemd extensively Please point me to a similar document written for Upstart. It doesn't really need one, because it behaves exactly as SysV init did. systemd, as implemented in f14, wouldn't have done; we migrated several services from being sysv-native to being systemd-native, so an administrator would need to know how to use both the sysv and systemd tools to monitor and manage services, and when to use which. With the Fedora implementation of upstart, if you know how to use sysv style init, you're totally fine, you don't need to learn anything new. * system-config-services needs to work with systemd native units Does it work with native Upstart jobs? Again, doesn't matter; we never used any by default. We did use native systemd services (some issues with systemd could only be solved by making services systemd-native). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 09:36 +0100, Richard Hughes wrote: 2010/9/15 Jóhann B. Guðmundsson johan...@gmail.com: The decision to reject this feature certainly was a lesson in killing momentum which we will never reach again. This is how I also feel. By trying to make Fedora shiny, polished and super-cautious against breaking things we're just creating another Ubuntu clone. This is destroying the very reason people run Fedora in the first place: Fedora is where innovation happens. Innovation is risky, but without it we're unimportant within two releases. This seems like an unwarranted extrapolation. If you read the meeting log the decision wasn't taken on any broad ideological basis like this. It was just a fairly pragmatic 'is it totally ready for f14 or would it be better to give it a bit more time and have it in f15' question (which was in fact very close, the vote failed by one). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bluetooth issues after removing systemd.
On 09/15/2010 09:27 PM, Adam Williamson wrote: On Wed, 2010-09-15 at 18:18 +1000, Steven Haigh wrote: Hi all, After applying the latest updates in updates-testing for F14, I cannot enable bluetooth anymore... The latest hal update fixed this, however now I'm not able to enable bluetooth at all. Anyone else? Downgrade bluez package. It got switched to using a native systemd service, which obviously won't work now we reverted to upstart. (It would have been this fix, not the hal update, which made it work for you). The update is https://admin.fedoraproject.org/updates/bluez-4.71-2.fc14 , the change from that needs to be reverted. I downgraded to these: bluez-4.71-1.fc14.i686 bluez-libs-4.71-1.fc14.i686 It seems to suffer from the same issue as before the integration with systemd. I still have to disable and re-enable bluetooth before it works. -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, Sep 15, 2010 at 1:29 PM, Adam Williamson awill...@redhat.com wrote: On Wed, 2010-09-15 at 10:27 +0200, Michał Piotrowski wrote: * system-config-services needs to work with systemd native units Does it work with native Upstart jobs? Again, doesn't matter; we never used any by default. nitpick That's not true /nitpick (We do ship some native upstart services by default) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20100915 changes
Compose started at Wed Sep 15 08:15:32 UTC 2010 Broken deps for x86_64 -- ale-0.9.0.3-2.fc14.x86_64 requires libMagickCore.so.3()(64bit) almanah-0.7.3-3.fc14.x86_64 requires libedataserverui-1.2.so.10()(64bit) antlr3-python-3.1.2-7.fc14.noarch requires python(abi) = 0:2.6 autotrace-0.31.1-24.fc14.i686 requires libMagickCore.so.3 autotrace-0.31.1-24.fc14.x86_64 requires libMagickCore.so.3()(64bit) calibre-0.7.18-2.fc15.x86_64 requires libMagickWand.so.3()(64bit) calibre-0.7.18-2.fc15.x86_64 requires libMagickCore.so.3()(64bit) claws-mail-plugins-geolocation-3.7.6-5.fc15.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) clutter-gst-devel-1.2.0-1.fc15.i686 requires pkgconfig(clutter-1.0) 0:1.3.0 clutter-gst-devel-1.2.0-1.fc15.x86_64 requires pkgconfig(clutter-1.0) 0:1.3.0 clutter-gtkmm-0.9.5-1.fc14.i686 requires libclutter-gtk-0.10.so.0 clutter-gtkmm-0.9.5-1.fc14.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) clutter-gtkmm-devel-0.9.5-1.fc14.i686 requires pkgconfig(clutter-gtk-0.10) = 0:0.10.2 clutter-gtkmm-devel-0.9.5-1.fc14.x86_64 requires pkgconfig(clutter-gtk-0.10) = 0:0.10.2 dmapd-0.0.25-3.fc15.i686 requires libMagickWand.so.3 dmapd-0.0.25-3.fc15.i686 requires libMagickCore.so.3 dmapd-0.0.25-3.fc15.x86_64 requires libMagickWand.so.3()(64bit) dmapd-0.0.25-3.fc15.x86_64 requires libMagickCore.so.3()(64bit) drawtiming-0.7.1-1.1.fc14.x86_64 requires libMagickCore.so.3()(64bit) drawtiming-0.7.1-1.1.fc14.x86_64 requires libMagick++.so.3()(64bit) dx-4.4.4-16.fc14.x86_64 requires libMagickCore.so.3()(64bit) dx-libs-4.4.4-16.fc14.i686 requires libMagickCore.so.3 dx-libs-4.4.4-16.fc14.x86_64 requires libMagickCore.so.3()(64bit) emerillon-0.1.2-7.fc14.x86_64 requires librest-0.6.so.0()(64bit) emerillon-0.1.2-7.fc14.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) entangle-0.1.0-7.fc14.x86_64 requires libmozjs.so()(64bit) ethos-0.2.2-7.fc15.i686 requires libmozjs.so ethos-0.2.2-7.fc15.x86_64 requires libmozjs.so()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libedata-book-1.2.so.2()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libcamel-1.2.so.17()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libgtkhtml-editor.so.0()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libebook-1.2.so.9()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libcamel-provider-1.2.so.17()(64bit) frysk-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) frysk-devel-0.4-26.fc14.i386 requires libgcj.so.10 frysk-devel-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) frysk-gnome-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) gdl-0.9-1.fc15.x86_64 requires libMagickCore.so.3()(64bit) gdl-0.9-1.fc15.x86_64 requires libMagick++.so.3()(64bit) gdl-python-0.9-1.fc15.x86_64 requires libMagickCore.so.3()(64bit) gdl-python-0.9-1.fc15.x86_64 requires libMagick++.so.3()(64bit) gjs-0.7.1-3.fc14.i686 requires libmozjs.so gjs-0.7.1-3.fc14.x86_64 requires libmozjs.so()(64bit) 1:gnome-bluetooth-2.90.0-5.fc15.x86_64 requires libgnome-control-center.so.1()(64bit) 1:gnome-games-extra-2.31.91.1-1.fc15.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) gnome-media-2.31.5-5.fc15.x86_64 requires libgnome-control-center.so.1()(64bit) gnome-panel-2.31.90-1.fc15.x86_64 requires libedataserverui-1.2.so.10()(64bit) gnome-python2-brasero-2.31.1-5.fc14.x86_64 requires libbrasero-media.so.1()(64bit) gnome-python2-brasero-2.31.1-5.fc14.x86_64 requires libbrasero-burn.so.1()(64bit) gnome-python2-totem-2.31.1-5.fc14.x86_64 requires libgnome-media-profiles.so.0()(64bit) gnome-shell-2.31.5-5.fc14.x86_64 requires libmozjs.so()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libchamplain-gtk-0.4.so.0()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libchamplain-0.4.so.0()(64bit) gstreamer-plugins-bad-free-extras-0.10.20-1.fc15.i686 requires libWildMidi.so.0 gstreamer-plugins-bad-free-extras-0.10.20-1.fc15.x86_64 requires libWildMidi.so.0()(64bit) gxine-0.5.905-3.fc13.x86_64 requires libmozjs.so()(64bit) hornsey-1.5.2-0.3.fc15.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) imageinfo-0.05-10.fc14.x86_64 requires libMagickCore.so.3()(64bit) inkscape-0.48.0-1.fc15.x86_64 requires libMagickCore.so.3()(64bit) inkscape-0.48.0-1.fc15.x86_64 requires libMagick++.so.3()(64bit) inkscape-view-0.48.0-1.fc15.x86_64 requires libMagickCore.so.3()(64bit) inkscape-view-0.48.0-1.fc15.x86_64 requires
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 14:09 +0200, drago01 wrote: On Wed, Sep 15, 2010 at 1:29 PM, Adam Williamson awill...@redhat.com wrote: On Wed, 2010-09-15 at 10:27 +0200, Michał Piotrowski wrote: * system-config-services needs to work with systemd native units Does it work with native Upstart jobs? Again, doesn't matter; we never used any by default. nitpick That's not true /nitpick (We do ship some native upstart services by default) Which? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, Sep 15, 2010 at 2:24 PM, Adam Williamson awill...@redhat.com wrote: On Wed, 2010-09-15 at 14:09 +0200, drago01 wrote: On Wed, Sep 15, 2010 at 1:29 PM, Adam Williamson awill...@redhat.com wrote: On Wed, 2010-09-15 at 10:27 +0200, Michał Piotrowski wrote: * system-config-services needs to work with systemd native units Does it work with native Upstart jobs? Again, doesn't matter; we never used any by default. nitpick That's not true /nitpick (We do ship some native upstart services by default) Which? readahead and system-setup-keyboard ... and probably others I can't think of right now. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
Once upon a time, Micha³ Piotrowski mkkp...@gmail.com said: Please point me to a similar document written for Upstart. Please stop comparing everything to what was done for Upstart. That was done in a different set of circumstances, and for almost everything, Upstart was done in a backwards compatible manner. Upstart-specific setups were discouraged (in part because of documentation), so Upstart was never much more than a different program to manage a sysv-init setup. Requirements are an evolving thing as people learn from the past. Responding to every request with a comparison to what was done with Upstart is pointless and irritating. -- Chris Adams cmad...@hiwaay.net Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
Once upon a time, Rahul Sundaram methe...@gmail.com said: * since s-c-services uses chkconfig, chkconfig needs to be hooked up to systemctl IMHO this just needs to be the common-use cases for chkconfig (on, off, --list). The --add, --del, --level, and other options are not things that most sysadmins use (or should use, there are some that use --del instead of off and are suprised when the service comes back on an update). I think service should also be hooked up so that it continues to work for all services (this may be done already, but I've been out of town and busy with a couple of projects and unable to test lately). Again, the common uses (start, stop, restart, condrestart, reload, status) should be sufficient. -- Chris Adams cmad...@hiwaay.net Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 06:46 +0100, Adam Williamson wrote: I do wish, though, Bill, that FESCo could have come through with this decision sooner; on a project basis it really does cut things rather fine for rolling RC1, and on a personal basis I could have not bothered with about seven hours of TC1 systemd blocker testing and triage over the last two days :( I think we all realize that the timing was exceedingly bad on this. I think we should try to distill some lessons from this for how we approach 'invasive' features in the future. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 09:36 +0100, Richard Hughes wrote: 2010/9/15 Jóhann B. Guðmundsson johan...@gmail.com: The decision to reject this feature certainly was a lesson in killing momentum which we will never reach again. This is how I also feel. By trying to make Fedora shiny, polished and super-cautious against breaking things we're just creating another Ubuntu clone I can assure you that deferring systemd to F15 is not going to turn Fedora into an Ubuntu close. Not by a long shot. I share the frustration about this decision, but lets not go overboard. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On 09/15/2010 03:35 PM, Matthias Clasen wrote: I think we all realize that the timing was exceedingly bad on this. I think we should try to distill some lessons from this for how we approach 'invasive' features in the future. If the vore was as close as it was in this case, it begs the question of a proper cost analysis. How much extra burden is now generated in ripping systemd out compared to fixing the known/open bugs? We definitely lose a key component here and the reward is seemingly a lot of extra work on the QA process and participants. It's something that should never happen again. We all learn as we go, but given the collected wisdom of our community, it surprises me that we came to this decision this late in the release cycle. Jan -- Jan H Wildeboer| EMEA Open Source Affairs | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Technopark II, Haus C | Fax:+49 (0)89 205071-111 Werner-von-Siemens-Ring 11 -15 | 85630 Grasbrunn| _ Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 11 -15 85630 Grasbrunn, Handelsregister: Amtsgericht Muenchen HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera _ GPG Key: 3AC3C8AB Fingerprint: 3D1E C4E0 DD67 E16D E47A 9564 A72F 5C39 3AC3 C8AB -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, Sep 15, 2010 at 11:53:36 +0530, Rahul Sundaram methe...@gmail.com wrote: Since, I am a co-maintainer of systemd and watching bugs flow through, I think we need a more concrete list of what is missing/needs to be fixed for this to be acceptable for Fedora 15. I think, off the top of my head, I would like the following * Fedora documentation, especially the longer guides to be updated to cover systemd extensively This should cover how to add new services. I needed to start svscanboot at boot. This used to be something in inittab, that I needed to futz with for upstart. It didn't seem to work in rc.local and when I tried reading the systemd documentation it seemed sort of fuzzy as to what I needed to do. I eventually got it working, but it would be nice to have some more clear cut examples in different cases. I also would like to have an easy way to tell if the config is sane. With some of the early issues with systemd I got my config in a bad state and it wasn't clear how to verify that it was sane or to easily revert it to a sane state. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bluetooth issues after removing systemd.
On 09/15/2010 09:58 PM, Steven Haigh wrote: On 09/15/2010 09:27 PM, Adam Williamson wrote: On Wed, 2010-09-15 at 18:18 +1000, Steven Haigh wrote: Hi all, After applying the latest updates in updates-testing for F14, I cannot enable bluetooth anymore... The latest hal update fixed this, however now I'm not able to enable bluetooth at all. Anyone else? Downgrade bluez package. It got switched to using a native systemd service, which obviously won't work now we reverted to upstart. (It would have been this fix, not the hal update, which made it work for you). The update is https://admin.fedoraproject.org/updates/bluez-4.71-2.fc14 , the change from that needs to be reverted. I downgraded to these: bluez-4.71-1.fc14.i686 bluez-libs-4.71-1.fc14.i686 It seems to suffer from the same issue as before the integration with systemd. I still have to disable and re-enable bluetooth before it works. I also tried 4.71-3 that hasn't been pushed yet - still the same issue... I guess it'll take a little while for the systemd - upstart transition. -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 15:41 +0200, Jan Wildeboer wrote: On 09/15/2010 03:35 PM, Matthias Clasen wrote: I think we all realize that the timing was exceedingly bad on this. I think we should try to distill some lessons from this for how we approach 'invasive' features in the future. If the vore was as close as it was in this case, it begs the question of a proper cost analysis. How much extra burden is now generated in ripping systemd out compared to fixing the known/open bugs? Bill had to do the work of doing the reversion; that's taken him a few hours. We (QA) now should do some quick testing to make sure the reversion works as intended. Everyone who can should go ahead and update to today's updates-testing, which should include the relevant updates, and check that the systemd-sysvinit package disappears, upstart becomes the default init system, and their system boots successfully. I'll test a live spin today too, to make sure that boots right and firstboot behaves. Then we'll hopefully go ahead with RC1 as we would have done with systemd. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 2010-09-15 at 08:42 -0500, Bruno Wolff III wrote: This should cover how to add new services. I needed to start svscanboot at boot. This used to be something in inittab, that I needed to futz with for upstart. It didn't seem to work in rc.local and when I tried reading the systemd documentation it seemed sort of fuzzy as to what I needed to do. I eventually got it working, but it would be nice to have some more clear cut examples in different cases. rc.local should work fine with systemd, it has a service which should just run rc.local. You may have hit a transitory bug where this service wasn't enabled, in which case you'd have to enable it manually, but that was fixed and wouldn't have affected people who didn't run pre-releases. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On 09/15/2010 11:50 PM, Adam Williamson wrote: Then just reboot and make sure the system boots and everything works as before. If so, go file positive karma on the update. If not, file bugs and let us know. Thanks! And make sure that you reboot *before* removing systemd - otherwise you need to power off the system hard to reboot or power off :) -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bluetooth issues after removing systemd.
On Wed, 2010-09-15 at 23:45 +1000, Steven Haigh wrote: It seems to suffer from the same issue as before the integration with systemd. I still have to disable and re-enable bluetooth before it works. I also tried 4.71-3 that hasn't been pushed yet - still the same issue... I guess it'll take a little while for the systemd - upstart transition. No, it ought to work, and it can't take a little time, it needs to work today. Please file a bug and/or a comment on the update. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On Wed, Sep 15, 2010 at 14:50:33 +0100, Adam Williamson awill...@redhat.com wrote: Hi, folks. So, the upstart reversion update is in updates-testing now: https://admin.fedoraproject.org/updates/system-setup-keyboard-0.8.6-2.fc14,firstboot-1.113-2.fc14,upstart-0.6.5-8.fc14 testing should be pretty simple. I did an update from updates-testing today and got the updated packages, so if your mirror's reasonably up to date, just updating an F14 system with updates-testing repo enabled should get you the changes. Are you expecting there to be any impact on the kickstart files for live images? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On Wed, 2010-09-15 at 23:53 +1000, Steven Haigh wrote: On 09/15/2010 11:50 PM, Adam Williamson wrote: Then just reboot and make sure the system boots and everything works as before. If so, go file positive karma on the update. If not, file bugs and let us know. Thanks! And make sure that you reboot *before* removing systemd - otherwise you need to power off the system hard to reboot or power off :) There's no need to remove systemd, really, I wouldn't particularly recommend doing that. We want to test how the reversion works if you just go ahead and do the updates you're provided with, not with manual tweaks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On 09/15/2010 11:56 PM, Adam Williamson wrote: On Wed, 2010-09-15 at 23:53 +1000, Steven Haigh wrote: On 09/15/2010 11:50 PM, Adam Williamson wrote: Then just reboot and make sure the system boots and everything works as before. If so, go file positive karma on the update. If not, file bugs and let us know. Thanks! And make sure that you reboot *before* removing systemd - otherwise you need to power off the system hard to reboot or power off :) There's no need to remove systemd, really, I wouldn't particularly recommend doing that. We want to test how the reversion works if you just go ahead and do the updates you're provided with, not with manual tweaks. Done. https://bugzilla.redhat.com/show_bug.cgi?id=634205 -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, Sep 15, 2010 at 11:53:36AM +0530, Rahul Sundaram wrote: Since, I am a co-maintainer of systemd and watching bugs flow through, I think we need a more concrete list of what is missing/needs to be fixed for this to be acceptable for Fedora 15. I think, off the top of my head, I would like the following Is there a second draft of Bill's initial checklist? -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On 09/15/2010 09:50 AM, Adam Williamson wrote: Hi, folks. So, the upstart reversion update is in updates-testing now: https://admin.fedoraproject.org/updates/system-setup-keyboard-0.8.6-2.fc14,firstboot-1.113-2.fc14,upstart-0.6.5-8.fc14 testing should be pretty simple. I did an update from updates-testing today and got the updated packages, so if your mirror's reasonably up to date, just updating an F14 system with updates-testing repo enabled should get you the changes. Then just reboot and make sure the system boots and everything works as before. If so, go file positive karma on the update. If not, file bugs and let us know. Thanks! Works ok here. Not a proven tester, so can't file karma. Regards, Old Fart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On Wed, 2010-09-15 at 10:20 -0400, Clyde E. Kunkel wrote: On 09/15/2010 09:50 AM, Adam Williamson wrote: Hi, folks. So, the upstart reversion update is in updates-testing now: https://admin.fedoraproject.org/updates/system-setup-keyboard-0.8.6-2.fc14,firstboot-1.113-2.fc14,upstart-0.6.5-8.fc14 testing should be pretty simple. I did an update from updates-testing today and got the updated packages, so if your mirror's reasonably up to date, just updating an F14 system with updates-testing repo enabled should get you the changes. Then just reboot and make sure the system boots and everything works as before. If so, go file positive karma on the update. If not, file bugs and let us know. Thanks! Works ok here. Not a proven tester, so can't file karma. Yes, you can. You've never needed to be a proven tester to file karma, and you still don't. All you need is a FAS account (hit the 'log in' button at the top left). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
2010/9/15 Adam Williamson awill...@redhat.com: Hi, folks. So, the upstart reversion update is in updates-testing now: https://admin.fedoraproject.org/updates/system-setup-keyboard-0.8.6-2.fc14,firstboot-1.113-2.fc14,upstart-0.6.5-8.fc14 testing should be pretty simple. I did an update from updates-testing today and got the updated packages, so if your mirror's reasonably up to date, just updating an F14 system with updates-testing repo enabled should get you the changes. Update was painless here. So how do I restore systemd-sysvinit after this test? Do rpm -ihv --force --nodeps systemd-sysvinit-10-1.fc14.x86_64.rpm do the trick and doesn't make system unbootable? Regards, Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Upstart reversion testing: howto
On Wed, 2010-09-15 at 16:39 +0200, Michał Piotrowski wrote: 2010/9/15 Adam Williamson awill...@redhat.com: Hi, folks. So, the upstart reversion update is in updates-testing now: https://admin.fedoraproject.org/updates/system-setup-keyboard-0.8.6-2.fc14,firstboot-1.113-2.fc14,upstart-0.6.5-8.fc14 testing should be pretty simple. I did an update from updates-testing today and got the updated packages, so if your mirror's reasonably up to date, just updating an F14 system with updates-testing repo enabled should get you the changes. Update was painless here. So how do I restore systemd-sysvinit after this test? The proper answer is 'wait for Lennart to update it'. Do rpm -ihv --force --nodeps systemd-sysvinit-10-1.fc14.x86_64.rpm do the trick and doesn't make system unbootable? I suspect it would, but then the next yum update would have upstart try to replace it again. (You may actually need to remove upstart-sysvinit with --nodeps too). I haven't tested. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-14 Branched report: 20100915 changes
Compose started at Wed Sep 15 13:15:11 UTC 2010 Broken deps for x86_64 -- RackTables-0.18.3-1.fc14.noarch requires /usr/local/bin/php RackTables-0.18.3-1.fc14.noarch requires perl(File::FnMatch) 1:anjuta-2.30.0.0-2.fc14.i686 requires libgladeui-1.so.9 1:anjuta-2.30.0.0-2.fc14.i686 requires libwebkit-1.0.so.2 1:anjuta-2.30.0.0-2.fc14.i686 requires libdevhelp-1.so.1 1:anjuta-2.30.0.0-2.fc14.x86_64 requires libgladeui-1.so.9()(64bit) 1:anjuta-2.30.0.0-2.fc14.x86_64 requires libdevhelp-1.so.1()(64bit) 1:anjuta-2.30.0.0-2.fc14.x86_64 requires libwebkit-1.0.so.2()(64bit) antlr3-python-3.1.2-7.fc14.noarch requires python(abi) = 0:2.6 cyphesis-0.5.21-2.fc13.x86_64 requires libpython2.6.so.1.0()(64bit) empathy-2.31.90-1.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libedata-book-1.2.so.2()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libcamel-1.2.so.17()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libgtkhtml-editor.so.0()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libebook-1.2.so.9()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libcamel-provider-1.2.so.17()(64bit) evolution-sharp-0.21.1-9.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) frysk-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) frysk-devel-0.4-26.fc14.i386 requires libgcj.so.10 frysk-devel-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) frysk-gnome-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) gnome-python2-evolution-2.31.1-5.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libchamplain-gtk-0.4.so.0()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libchamplain-0.4.so.0()(64bit) intellij-idea-9.0.1.94.399-11.fc14.x86_64 requires jna-examples libglade-java-2.12.5-12.fc12.i686 requires libgcj.so.10 libglade-java-2.12.5-12.fc12.x86_64 requires libgcj.so.10()(64bit) libgnome-java-2.12.4-12.fc12.i686 requires libgcj.so.10 libgnome-java-2.12.4-12.fc12.x86_64 requires libgcj.so.10()(64bit) libvte-java-0.12.1-15.fc12.i686 requires libgcj.so.10 libvte-java-0.12.1-15.fc12.x86_64 requires libgcj.so.10()(64bit) matahari-0.0.5-1.fc14.x86_64 requires libqmf.so.1()(64bit) mingw32-OpenSceneGraph-2.8.2-4.fc14.noarch requires mingw32(libpng-3.dll) ovirt-server-0.100-4.fc12.noarch requires qpidd ovirt-server-0.100-4.fc12.noarch requires qpidc perl-Gtk2-MozEmbed-0.08-6.fc14.15.x86_64 requires gecko-libs = 0:1.9.2.4 plee-the-bear-0.4.1-5.fc14.x86_64 requires libboost_thread-mt.so.1.41.0()(64bit) plee-the-bear-0.4.1-5.fc14.x86_64 requires libboost_filesystem-mt.so.1.41.0()(64bit) plee-the-bear-0.4.1-5.fc14.x86_64 requires libboost_system-mt.so.1.41.0()(64bit) python-polybori-0.5-8.fc14.i686 requires libboost_python.so.1.41.0 python-polybori-0.5-8.fc14.x86_64 requires libboost_python.so.1.41.0()(64bit) qtgpsc-0.2.3-6.fc12.x86_64 requires libgps.so.18()(64bit) spacewalk-certs-tools-1.1.1-2.1.fc14.noarch requires spacewalk-backend-libs = 0:0.8.28 viking-0.9.91-3.fc13.x86_64 requires libgps.so.18()(64bit) wfut-1.1.0-8.fc12.x86_64 requires libgcj.so.10()(64bit) Broken deps for i386 -- RackTables-0.18.3-1.fc14.noarch requires /usr/local/bin/php RackTables-0.18.3-1.fc14.noarch requires perl(File::FnMatch) 1:anjuta-2.30.0.0-2.fc14.i686 requires libgladeui-1.so.9 1:anjuta-2.30.0.0-2.fc14.i686 requires libwebkit-1.0.so.2 1:anjuta-2.30.0.0-2.fc14.i686 requires libdevhelp-1.so.1 antlr3-python-3.1.2-7.fc14.noarch requires python(abi) = 0:2.6 cyphesis-0.5.21-2.fc13.i686 requires libpython2.6.so.1.0 empathy-2.31.90-1.fc14.i686 requires libcamel-1.2.so.19 evolution-couchdb-0.4.92-1.fc14.i686 requires libcamel-provider-1.2.so.17 evolution-couchdb-0.4.92-1.fc14.i686 requires libebook-1.2.so.9 evolution-couchdb-0.4.92-1.fc14.i686 requires libgtkhtml-editor.so.0 evolution-couchdb-0.4.92-1.fc14.i686 requires libedata-book-1.2.so.2 evolution-couchdb-0.4.92-1.fc14.i686 requires libcamel-1.2.so.17 evolution-sharp-0.21.1-9.fc14.i686 requires libcamel-1.2.so.19 frysk-0.4-26.fc14.i386 requires libgcj.so.10 frysk-devel-0.4-26.fc14.i386 requires libgcj.so.10 frysk-gnome-0.4-26.fc14.i386 requires libgcj.so.10 gnome-python2-evolution-2.31.1-5.fc14.i686 requires libcamel-1.2.so.19 gpx-viewer-0.1.2-2.fc14.i686 requires libchamplain-gtk-0.4.so.0 gpx-viewer-0.1.2-2.fc14.i686 requires libchamplain-0.4.so.0
[Fedora QA] #127: Proventester mentorship request
#127: Proventester mentorship request -+-- Reporter: salimma | Owner: Type: proventester request | Status: new Priority: major| Milestone: Component: Proventester Mentor Request | Version: Keywords: | -+-- = phenomenon = I'm a Fedora package maintainer, currently with provenpackager and sponsor memberships, and would like to join the proventester team. = reason = I normally run a stable Fedora + test updates on one machine, and a development release starting from the alpha on another, and would like to help updates get processed faster. Especially considering that my own updates might be stalled waiting on a critical path update! = recommendation = -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/127 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-14 Branched report: 20100915 changes
On Wed, Sep 15, 2010 at 03:19:46PM +, Branched Report wrote: python-polybori-0.5-8.fc14.i686 requires libboost_python.so.1.41.0 I rebuilt this and submitted an update. This warning should go away in a week or so when we push to stable. python-psyco-1.6-4.fc12.i686 requires libpython2.6.so.1.0 python-psyco-1.6-4.fc12.i686 requires python(abi) = 0:2.6 My understanding on this was that psyco was broken on python-2.7... Do we want to block this from the F14 release? -Toshio pgpxTRV21eWJo.pgp Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-14 Branched report: 20100915 changes
Toshio Kuratomi (a.bad...@gmail.com) said: python-psyco-1.6-4.fc12.i686 requires libpython2.6.so.1.0 python-psyco-1.6-4.fc12.i686 requires python(abi) = 0:2.6 My understanding on this was that psyco was broken on python-2.7... Do we want to block this from the F14 release? Does anything else require it? Bill -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-14 Branched report: 20100915 changes
On Wed, 2010-09-15 at 11:46 -0400, Bill Nottingham wrote: Toshio Kuratomi (a.bad...@gmail.com) said: python-psyco-1.6-4.fc12.i686 requires libpython2.6.so.1.0 python-psyco-1.6-4.fc12.i686 requires python(abi) = 0:2.6 My understanding on this was that psyco was broken on python-2.7... Do we want to block this from the F14 release? Does anything else require it? IIRC, eclipe-pydev did, but removed it, only using it for optimization. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
drago01 (drag...@gmail.com) said: nitpick That's not true /nitpick (We do ship some native upstart services by default) Which? readahead and system-setup-keyboard ... and probably others I can't think of right now. Those aren't services in the classic sense. They're boot processes, more or less. (And, at least in the case of system-setup-keyboard, they're an implementation detail that the administrator isn't expected to enable or disable, akin to rc.local.) Bill -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-14 Branched report: 20100915 changes
On Wed, Sep 15, 2010 at 11:52:50AM -0400, David Malcolm wrote: On Wed, 2010-09-15 at 11:46 -0400, Bill Nottingham wrote: Toshio Kuratomi (a.bad...@gmail.com) said: python-psyco-1.6-4.fc12.i686 requires libpython2.6.so.1.0 python-psyco-1.6-4.fc12.i686 requires python(abi) = 0:2.6 My understanding on this was that psyco was broken on python-2.7... Do we want to block this from the F14 release? Does anything else require it? IIRC, eclipe-pydev did, but removed it, only using it for optimization. F14 vm: % repoquery -q --whatrequires 'python-psyco' --alldeps python-psyco-0:1.6-4.fc12.i686 So it looks safe to remove in f14. -Toshio pgpXG33eTWNyT.pgp Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-14 Branched report: 20100915 changes
On Wed, 2010-09-15 at 12:21 -0400, Toshio Kuratomi wrote: On Wed, Sep 15, 2010 at 11:52:50AM -0400, David Malcolm wrote: On Wed, 2010-09-15 at 11:46 -0400, Bill Nottingham wrote: Toshio Kuratomi (a.bad...@gmail.com) said: python-psyco-1.6-4.fc12.i686 requires libpython2.6.so.1.0 python-psyco-1.6-4.fc12.i686 requires python(abi) = 0:2.6 My understanding on this was that psyco was broken on python-2.7... Do we want to block this from the F14 release? Does anything else require it? IIRC, eclipe-pydev did, but removed it, only using it for optimization. F14 vm: % repoquery -q --whatrequires 'python-psyco' --alldeps python-psyco-0:1.6-4.fc12.i686 So it looks safe to remove in f14. Right. This came up for Alpha, as eclipse-pydev wound up on the media. As David said, it turned out to only need it for optimization, and nothing else needed it. psyco is not trivial to rebuild against python 2.7 and as of yet no-one's done the work. It would probably be best to block it until a python 2.7 port is available. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F-14 Branched report: 20100915 changes
On Wed, 2010-09-15 at 17:37 +0100, Adam Williamson wrote: On Wed, 2010-09-15 at 12:21 -0400, Toshio Kuratomi wrote: On Wed, Sep 15, 2010 at 11:52:50AM -0400, David Malcolm wrote: On Wed, 2010-09-15 at 11:46 -0400, Bill Nottingham wrote: Toshio Kuratomi (a.bad...@gmail.com) said: python-psyco-1.6-4.fc12.i686 requires libpython2.6.so.1.0 python-psyco-1.6-4.fc12.i686 requires python(abi) = 0:2.6 My understanding on this was that psyco was broken on python-2.7... Do we want to block this from the F14 release? Does anything else require it? IIRC, eclipe-pydev did, but removed it, only using it for optimization. F14 vm: % repoquery -q --whatrequires 'python-psyco' --alldeps python-psyco-0:1.6-4.fc12.i686 So it looks safe to remove in f14. Right. This came up for Alpha, as eclipse-pydev wound up on the media. As David said, it turned out to only need it for optimization, and nothing else needed it. psyco is not trivial to rebuild against python 2.7 and as of yet no-one's done the work. It would probably be best to block it until a python 2.7 port is available. Upstream wrote an experimental port (and it seemed to work), but IIRC I got the impression that they've moved on to PyPy these days. (Bugs in this code are likely to cause random segfaults in python processes, so I'm happy to have this be blocked) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
2010/9/15 Petrus de Calguarium pguec...@gmail.com: I just ran yum update. The result... removed: systemd-sysvinit installed: upstart-sysvinit Adam Williamson advised to wait with those on update from Leenart I have put init=/bin/systemd on the kernel boot line in grub.conf Is this all I need to do in order not to regress my system? I wish to continue to use systemd in F14. You can use this just like you could use upstart with systemd-sysvinit. You can also do missing links by hand. Regards, Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
2010/9/15 Matthew Miller mat...@mattdm.org: On Wed, Sep 15, 2010 at 10:41:36AM -0600, Petrus de Calguarium wrote: Is this all I need to do in order not to regress my system? I wish to continue to use systemd in F14. What are you wanting to get out of having your system using systemd at this point? If it's to help advance systemd as a technology, to test and integrate your own software with it, and/or to be on the leading edge, I highly suggest switching to Rawhide (which is easily done from a test release of Fedora 14: http://fedoraproject.org/wiki/Releases/Rawhide#Yum_update_from_a_test_release). You can then easily stay on the F15 release track when it comes out, if you're ready to move to a more stable solution. If you have a different reason, I'd love to hear it so we can figure out a good solution for you. Keeping the existing Fedora 14 test packages for systemd isn't going to do what you want. Are there any technical problems in developing systemd and it's services on stable F14? -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences Regards, Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, 15 Sep 2010 11:50:14 -0400 Bill Nottingham wrote: I do too. I suspect for situations like this we at a minimum need to adopt a more formal process for pulling feedback/votes/whatever outside of the meeting timeframe, whether it's calling a special session, enforcing a 'you must vote in the ticket by this timeframe or your vote is counted as foo', or something else. You left out removing the fanatical devotion to releasing every six months :-). I've really never understood that one. Why is virtually everything subordinate to getting a release out at an artificial deadline? Why not just release when there appears to be enough things working to justify a new release? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
Matthew Miller wrote: What are you wanting to get out of having your system using systemd at this point? I had no problems with systemd and have already converted my scripts to using systemd. I don't want to regress all my work and have to do it all over and then repeat it all again in 6 months for F15. All was working smoothly for me without problems. I might give rawhide a try. I have never managed to successfully install it, despite about 10 years of trying. Not once did it ever boot or could I even get anaconda to install it without giving me an error at the critical moment or actually writing the files to the partition. Perhaps it will finally work now? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
On Wed, Sep 15, 2010 at 11:02:27AM -0600, Petrus de Calguarium wrote: I might give rawhide a try. I have never managed to successfully install it, despite about 10 years of trying. Not once did it ever boot or could I even get anaconda to install it without giving me an error at the critical moment or actually writing the files to the partition. Perhaps it will finally work now? You shouldn't need to install it from scratch, given where you're at. Just yum update from your F14 test system. -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
Tom Horsley wrote: You left out removing the fanatical devotion to releasing every six months :-). I've really never understood that one. Why is virtually everything subordinate to getting a release out at an artificial deadline? Why not just release when there appears to be enough things working to justify a new release? Excellent point. F13 may be a great release for developers, but for consumers it is a real dud. It doesn't offer anything new or different, just the promise or allure of some background stability issues resolved, perhaps. F14 without systemd will be about the same. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, Sep 15, 2010 at 11:10:12AM -0600, Petrus de Calguarium wrote: Excellent point. F13 may be a great release for developers, but for consumers it is a real dud. It doesn't offer anything new or different, just the promise or allure of some background stability issues resolved, perhaps. F14 without systemd will be about the same. What was F14 with systemd going to offer that's new or different for consumers? I don't mean this as a negative for systemd, but rather that if it's successful, it will _precisely_ be because it's good at handling background issues unobtrusively. -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
Matthew Miller wrote: You shouldn't need to install it from scratch, given where you're at. Just yum update from your F14 test system. You're sure this isn't going to f--k my perfectly running system (yes, I do have f13 installed on a different partition, but I would not be happy with that and would want at least f14, if rawhide screws up). So... I install the fedora-release-rawhide package from rawhide and then yum update, and I guess I would manually have to reinstall systemd-sysvinit, too, right? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
Matthew Miller wrote: What was F14 with systemd going to offer that's new or different for consumers? I guess I can't truly answer that, except for the fact that it was promising and seeming to deliver faster booting. I turn off my computer when I go out and at night, since I have to pay for my electricity, so this is not just a big convenience thing, but also a financial one that I see reflected in my monthly electrical bill. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
On Wed, Sep 15, 2010 at 11:21:40AM -0600, Petrus de Calguarium wrote: You're sure this isn't going to f--k my perfectly running system (yes, I do have f13 installed on a different partition, but I would not be happy with that and would want at least f14, if rawhide screws up). Am I *sure*? No promises! But I've done it several times without issue. Annnd sometimes with moderate but fixable issues. If you're used to running bleeding edge software, you're probably competent to dig yourself out of whatever problems might crop up. I install the fedora-release-rawhide package from rawhide and then yum update, You can install fedora-release-rawhide from F14. Then go to /etc/yum.repos.d/ and change what's enabled, and then yum update. and I guess I would manually have to reinstall systemd-sysvinit, too, right? Probably. And depending on the current state of things, double-check if you still have a default target. -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Rawhide: Upstart, systemd reversion
Greetings: Will there be the same reversion in rawhide too? Sincerely yours, Rob G. Healey -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Rawhide: Upstart, systemd reversion
On Wed, Sep 15, 2010 at 10:35 PM, Rob Healey robheal...@gmail.com wrote: Greetings: Will there be the same reversion in rawhide too? No. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Rawhide: Upstart, systemd reversion
drago01 (drag...@gmail.com) said: Will there be the same reversion in rawhide too? No. In fact, I'm strongly debating flipping it so systemd is mandatory; it enables us to actually merge the changes that allow for cleaner startup/shutdown (moving parts of rc.sysinit, etc. to systemd units.) Bill -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
Matthew Miller mat...@mattdm.org wrote: On Wed, Sep 15, 2010 at 10:41:36AM -0600, Petrus de Calguarium wrote: Is this all I need to do in order not to regress my system? I wish to continue to use systemd in F14. What are you wanting to get out of having your system using systemd at this point? I understood that systemd would be available as an alternative in F14? -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de InformaticaFono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile 234 Fax: +56 32 2797513 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Rawhide: Upstart, systemd reversion
On Wed, Sep 15, 2010 at 10:38 PM, Bill Nottingham nott...@redhat.com wrote: drago01 (drag...@gmail.com) said: Will there be the same reversion in rawhide too? No. In fact, I'm strongly debating flipping it so systemd is mandatory; it enables us to actually merge the changes that allow for cleaner startup/shutdown (moving parts of rc.sysinit, etc. to systemd units.) I kind of like this idea ... if now that we have enough time till F15's release we should do that. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
On 09/15/2010 08:44 PM, Horst H. von Brand wrote: Matthew Millermat...@mattdm.org wrote: On Wed, Sep 15, 2010 at 10:41:36AM -0600, Petrus de Calguarium wrote: Is this all I need to do in order not to regress my system? I wish to continue to use systemd in F14. What are you wanting to get out of having your system using systemd at this point? I understood that systemd would be available as an alternative in F14? No it wont. That seems to be general misconception in the community that it is. ( otherwise systemd spin only would be created ) If you want systemd you will need to upgrade to rawhide which I don't recommend until after alpha ( things usually have settled down around alpha ). Bear in mind that there is no certainty that systemd will be in F15 FESCO ( and others) just assume it will be. Lennart may very well choose to delay systemd until F16 since the window of opportunity of having the necessary community resources dedicated to systemd has passed . The benefit of getting this in F14 was to get over the migration step so you could focus on optimisation/enhancements and integration with *DE and other stuff during the F15 cycle. The migration step has not been removed it just got delayed ( atleast ) six months with less resources to spare. The Gnome Desktop team cant afford weeks of invasive introduction of new code resulting in broken rawhide during the F15 cycle if they are going to be successful migrating to Gnome3 ( which systemd does ). Our soldiers on the front ( Fedora forum channels etc which often seem to get forgotten ) would only have to deal with systemd migration problems after F14 got released and then could focus directly on Gnome3 migration problem after F15 got released instead of having to deal with both at the same time in F15 which puts a lot of strain on those resources. This is why I said it was unwise decision to reject this feature during this release cycle and I'm sure if FESCO bothered to do their due diligence and had done some research spoken to all parties involved then look at the options and weight them from wider community perspective their decision would not have been throwing this away because of some hypothetical bug encounters and some few missing docs ( that were being looked at ). Just my $0.02 JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 13 updates-testing report
The following builds have been pushed to Fedora 13 updates-testing bibletime-2.7.3-1.fc13 eog-2.30.1-2.fc13 font-manager-0.5.6-1.fc13 ibus-1.3.6-2.fc13 libucil-0.9.8-4.fc13 microcode_ctl-1.17-4.fc13 perl-Crypt-SSLeay-0.58-1.fc13 perl-Perl-MinimumVersion-1.26-1.fc13 psacct-6.5.4-2.fc13 python-zope-exceptions-3.6.1-5.fc13 python-zope-interface-3.6.1-4.fc13 rubygem-configuration-1.1.0-1.fc13 star-1.5.1-4.fc13 zint-2.4.0-1.fc13 Details about builds: bibletime-2.7.3-1.fc13 (FEDORA-2010-14776) An easy to use Bible study tool Update Information: A new update that fixes a potential data loss bug ChangeLog: * Tue Sep 14 2010 Deji Akingunola dakin...@gmail.com - 2.7.3-1 - Update to 2.7.3, fixes a potential data loss bug eog-2.30.1-2.fc13 (FEDORA-2010-14770) Eye of GNOME image viewer Update Information: Use the Page Setup tab in the print dialog instead of a separate option. The disabled page setup options in the print dialog give the impression that the options are not available and this can be quite confusing. ChangeLog: * Wed Sep 15 2010 Siddhesh Poyarekar spoya...@redhat.com 2.30.1-2 - Use the Page Setup tab in the print dialog instead of a separate option References: [ 1 ] Bug #564017 - Eog insists on US letter format and ignores system printer setting https://bugzilla.redhat.com/show_bug.cgi?id=564017 font-manager-0.5.6-1.fc13 (FEDORA-2010-14783) A font management application for the GNOME desktop environment Update Information: Update to upstream version. ChangeLog: * Wed Sep 15 2010 Jean-Francois Saucier jfsauc...@infoglobe.ca - 0.5.6-1 - Rebuild new version * Tue Jul 27 2010 David Malcolm dmalc...@redhat.com - 0.5.5.4-2 - Rebuilt for https://fedoraproject.org/wiki/Features/Python_2.7/MassRebuild References: [ 1 ] Bug #628938 - [abrt] font-manager-0.5.5.4-1.fc13: __init__.py:362:list_families_in:IndexError: No such collection or category https://bugzilla.redhat.com/show_bug.cgi?id=628938 ibus-1.3.6-2.fc13 (FEDORA-2010-14778) Intelligent Input Bus for Linux OS Update Information: Bug 621795 - crash in ibus_object_destroy Bug 626652 - ibus memory leak with ibus_input_context_process_key_event ChangeLog: * Wed Sep 15 2010 Takao Fujiwara tfuji...@redhat.com - 1.3.6-2 - Added ibus-621795-engineproxy-segv.patch Fixes Bug 621795 crash in ibus_object_destroy - Added ibus-626652-leak.patch Fixes Bug 626652 - ibus memory leak with ibus_input_context_process_key_event References: [ 1 ] Bug #621795 - [abrt] crash in ibus-1.3.6-1.fc12: ibus_object_destroy: Process /usr/bin/ibus-daemon was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=621795 [ 2 ] Bug #626652 - ibus memory leak with ibus_input_context_process_key_event https://bugzilla.redhat.com/show_bug.cgi?id=626652 libucil-0.9.8-4.fc13 (FEDORA-2010-14789) Library to render text and graphic overlays onto video images Update Information: Fixed some crasher bugs. ChangeLog: * Wed Sep 15 2010 Kamil Dudka kdu...@redhat.com 0.9.8-4 - upstream patch for #632439 - check return value of theora_encode_init() (#627890)
Re: What do consumers wishing to use systemd in F14 need to do?
2010/9/15 Jóhann B. Guðmundsson johan...@gmail.com: On 09/15/2010 08:44 PM, Horst H. von Brand wrote: Matthew Millermat...@mattdm.org wrote: On Wed, Sep 15, 2010 at 10:41:36AM -0600, Petrus de Calguarium wrote: Is this all I need to do in order not to regress my system? I wish to continue to use systemd in F14. What are you wanting to get out of having your system using systemd at this point? I understood that systemd would be available as an alternative in F14? No it wont Where in the 9 effing hecks did you come up with that piece of knowledge? I have seen multiple devels say it will be so I kind of expect the people putting code together will know whats going on. -- Stephen J Smoogen. “The core skill of innovators is error recovery, not failure avoidance.” Randy Nelson, President of Pixar University. We have a strategic plan. It's called doing things. — Herb Kelleher, founder Southwest Airlines -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
since the current justification for having stable releases at all is 'to handle upgrade cases we can't handle with yum' What about installation from media such as DVD for users who cannot reasonably access more than a gigabyte of updates from the Net? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Rawhide and systemd?
Greetings: I know there is some time before Rawhide/ fc15 is even at an alpha stage, but I do agree with Matthew Miller... If it is going to become mandatory for fc15, then I believe it should be done sooner than later and waiting. Sincerely yours, Rob G. Healey -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
On 09/15/2010 10:40 PM, Stephen John Smoogen wrote: Where in the 9 effing hecks did you come up with that piece of knowledge? I have seen multiple devels say it will be so I kind of expect the people putting code together will know whats going on. That's interesting was either on of those Bill or Lennart? If that truly is the case than these are good news and I stand corrected. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: heads-up: upstart reversion coming soon
On Wed, Sep 15, 2010 at 11:24:47PM +0100, Adam Williamson wrote: ...or, since the current justification for having stable releases at all is 'to handle upgrade cases we can't handle with yum', have a new stable release only when we hit such a case (and try to hit as few such cases as possible)... I think going through a process of stabilization and making releases is a good development practice. -- Matthew Miller mat...@mattdm.org Senior Systems Architect -- Instructional Research Computing Services Harvard School of Engineering Applied Sciences -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What do consumers wishing to use systemd in F14 need to do?
Jóhann B. Guðmundsson wrote: https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet That should get the migration process to systemd started and as with all wiki pages dont hesitate to add/enhance if needed. Thanks. Duly noted. I was migrated and will now likely have to regress for 6 months. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 14 updates-testing report
The following builds have been pushed to Fedora 14 updates-testing ImageMagick-6.6.4.1-13.fc14 anaconda-14.17.2-1.fc14 authconfig-6.1.9-1.fc14 calibre-0.7.18-3.fc14 cyphesis-0.5.24-1.fc14 firstboot-1.113-3.fc14 font-manager-0.5.6-1.fc14 gdl-0.9-2.fc14 gdm-2.31.90-7.fc14 gupnp-dlna-0.3.1-1.fc14 kdebase-workspace-4.5.1-3.fc14 kdesvn-1.5.5-1.fc14 libucil-0.9.8-5.fc14 lshw-B.02.14-5.fc14 metacity-2.30.0-8.fc14 microcode_ctl-1.17-4.fc14 ntp-4.2.6p2-5.fc14 openssh-5.5p1-21.fc14 perl-Perl-MinimumVersion-1.26-1.fc14 perl-Text-SpellChecker-0.06-1.fc14 python-cssutils-0.9.7-0.0.b3.fc14 python-zope-exceptions-3.6.1-5.fc14 rabbitmq-server-2.0.0-1.fc14 rubygem-configuration-1.1.0-1.fc14 star-1.5.1-4.fc14 syncevolution-1.0.99.6-1.fc14 xorg-x11-drv-qxl-0.0.20.f14b-2.fc14 zint-2.4.0-1.fc14 Details about builds: ImageMagick-6.6.4.1-13.fc14 (FEDORA-2010-14794) An X application for displaying and manipulating images ChangeLog: * Tue Sep 14 2010 Pavel Alexeev pa...@hubbitus.info - 6.6.4.1-13 - Update to 6.6.4-1 to fix FBFS BZ#631169. * Fri Jul 30 2010 Pavel Alexeev pa...@hubbitus.info - 6.6.2.1-12 - Add %doc LICENSE as it required new Licensing Guidelines Update ( https://fedoraproject.org/wiki/Packaging:LicensingGuidelines ) References: [ 1 ] Bug #631169 - FTBFS ImageMagick-6.6.2.1-11.fc14 https://bugzilla.redhat.com/show_bug.cgi?id=631169 anaconda-14.17.2-1.fc14 (FEDORA-2010-14795) Graphical system installer Update Information: Anaconda update with f14 beta blocker fixes. ChangeLog: * Wed Sep 15 2010 David Lehman dleh...@redhat.com - 14.17.2-1 - Remove old kernels with new bootloader (#633234) (bcl) - Pass xdriver to anaconda in liveinst (#633827) (bcl) - Reset resolver after network device activation (#632489) (rvykydal) - Fix importing the netconfig UI in rescue mode (#632510). (clumens) * Thu Sep 9 2010 David Lehman dleh...@redhat.com - 14.17.1-1 - Re-fix systemd default link (#627401, mschmidt). (clumens) References: [ 1 ] Bug #633234 - Previous grub entry is not overwritten after upgrade with creating new bootloader https://bugzilla.redhat.com/show_bug.cgi?id=633234 [ 2 ] Bug #633827 - liveinst needs to pass --xdriver=* to anaconda when xdriver=* is in /proc/cmdline https://bugzilla.redhat.com/show_bug.cgi?id=633827 [ 3 ] Bug #632489 - Fail to read package metadata after specifying repo= https://bugzilla.redhat.com/show_bug.cgi?id=632489 [ 4 ] Bug #632510 - Installer exited abnormally when starting network in rescue mode https://bugzilla.redhat.com/show_bug.cgi?id=632510 authconfig-6.1.9-1.fc14 (FEDORA-2010-14803) Command line tool for setting up authentication from network services Update Information: Minor update that removes support for the obsolete pam_smb_auth module and adds better synchronization of configuration files with duplicate settings. ChangeLog: * Wed Sep 15 2010 Tomas Mraz tm...@redhat.com - 6.1.9-1 - removed support for setting up pam_smb_auth authentication - long ago deprecated - added code for better synchronization of files with duplicate settings such as login.defs, libuser.conf and system-auth-ac (#565521) References: [ 1 ] Bug #565521 - authconfig should better sync login.defs and other files with duplicate settings https://bugzilla.redhat.com/show_bug.cgi?id=565521 calibre-0.7.18-3.fc14 (FEDORA-2010-14791) E-book converter and library management Update Information: Please test this latest upstream update. It adds support for new devices and other new functionality, as well as fixing several other bugs and
Re: heads-up: upstart reversion coming soon
On 09/15/2010 06:45 PM, Chris Adams wrote: I think service should also be hooked up so that it continues to work for all services (this may be done already, but I've been out of town and busy with a couple of projects and unable to test lately). Again, the common uses (start, stop, restart, condrestart, reload, status) should be sufficient. service already uses systemctl. Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
