Testing request: trash-cli
Hi folks, Could someone please install the new trash-cli in rawhide and see if it works as expected please? Upstream's made a lot of changes, and I'd like to know it works before I build for f17 etc. I don't have a rawhide machine handy at the moment :/ It's just a command line client to Trash. Won't take more than 5 minutes to test :) -- Thanks, Regards, Ankur: "FranciscoD" http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/ signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New BugZapper Introduction
Hello Keith, You should be sponsored in the triage group as of this writing and have the bugzilla permissions to get started. You may want to look in to the 'proventesters' group as well. Here is a link for further information. http://fedoraproject.org/wiki/Proven_tester You may have already started reviewing most of this, however, just to be sure here is the information I send to new members. This is a list of components which the BugZappers work on as a priority. If you can help with any of the components on this list please let us know. https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers We'd recommend you pick a component that you feel comfortable working on, then contact its maintainer to say you'll be working on triaging it, and ask if they have any tips or special requests. Then read: https://fedoraproject.org/wiki/BugsAndFeatureRequests https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow https://fedoraproject.org/wiki/BugZappers/Tools https://fedoraproject.org/wiki/BugZappers/FindingBugs https://fedoraproject.org/wiki/BugZappers/How_to_Triage https://fedoraproject.org/wiki/BugZappers/FindingDuplicates https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses To see how the process works (I know that looks like a lot of pages, but several of them are pretty short, and they all work together). Please do join freenode #fedora-bugzappers and ask if you have any questions or problems, there's usually another team member around who can help you out. Thanks a lot for volunteering your time! Do come out to the next meeting - they're bi-weekly, Tuesdays at 21:00 UTC - if you have the time, and we can welcome you there. Best regards, Dennis Johnson irc: fenris02 -- Scire ubi aliquid invenire possis, ea demum maxima pars eruditionis est --Anonymous On Thu, Apr 26, 2012 at 6:07 PM, Keith McGrellis wrote: > Hi, > > I've applied to join the BugZappers group so would like to introduce > myself. > > My name is Keith McGrellis and I live in Belfast, Northern Ireland. > > I've worked with linux both at work and at home for about 15 years now. > I've used a mixture of distributions, including Red Hat, Debian, > Ubuntu and Fedora. > > My main background is sys admin and scripting (mainly bash and perl). > > I'm looking forward to helping with triaging bugs and learning more > about fedora. > > My irc nick is kmcgrell > > Thanks, > Keith > -- > 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
[Test-Announce] Fedora 17 Final Test Compose 2 (TC2) Available Now!
As per the Fedora 17 schedule [1], Fedora 17 Final Test Compose 2 (TC2) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5163 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Security Lab: https://fedoraproject.org/wiki/Test_Results:Current_Security_Lab_Test Ideally, all Alpha, Beta, and Final priority test cases for Installation [2], Base [3], Desktop [4], and Security Lab [5] should pass in order to meet the Final Release Criteria [6]. Help is available on #fedora-qa on irc.freenode.net [7], or on the test list [8]. Create Fedora 17 Final test compose (TC) - live and traditional https://fedorahosted.org/rel-eng/ticket/5163 Fedora 17 Final Blocker tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752650 Fedora 17 Final Nice-To-Have tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752653 [1] http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/QA:Security_Lab_validation_testing [6] https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria [7] irc://irc.freenode.net/fedora-qa [8] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ 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: adobe flash crashes in firefox, not in konqueror
On 04/28/2012 12:15 PM, Peter Gueckel wrote: > My system is up-to-date with updates-testing. > > Since about 2-3 days, coinciding with the release of firefox > 12, I think, the adobe flash plugin crashes in firefox, but > it runs in konqueror, but only this site appears to be > affected: > > http://www.cbc.ca/thenational/watch/ > > Youtube works. > How long does it take to crash? I just installed the latest flash-plugin using the Adobe repo and it is playing just fine F17 fully updated on i686. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
adobe flash crashes in firefox, not in konqueror
My system is up-to-date with updates-testing. Since about 2-3 days, coinciding with the release of firefox 12, I think, the adobe flash plugin crashes in firefox, but it runs in konqueror, but only this site appears to be affected: http://www.cbc.ca/thenational/watch/ Youtube works. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 and data loss
On 04/28/2012 02:16 AM, Adam Williamson wrote: On Fri, 2012-04-27 at 19:21 +0200, sixpack13 wrote: ... Alternatively: if you pick 'custom partition layout', then make sure you _actually check_ the layout before proceeding. Did that ! As I ever do since redhat 6.x ! Please take a look at the snapshot in the bugreport: I can't hardly imagine that one will choose this layout ! Please help, that *no one else* will run in this disaster of data loss !!! -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On 04/27/2012 01:55 PM, george2 wrote: The banking crises was in part formed by many individuals sensing something wasn't right but did not take any personal responsibility to act. If you really meant the words you typed then you would be responding to the replies to your message. It is obvious you wrote a one-off rant that alleviates your ignorance about what the F17 name means. A.K.A. A spam mail to the test list. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On Sat, 2012-04-28 at 01:13 +0100, Adam Williamson wrote: > It's a hot dog. It has always been a hot dog. The name is not an > innuendo, it is not a double entendre. If anyone thinks it is, that's > their problem, not ours. The whole beefy miracle thing is and _has > always been_ about a food product. I believe you -- though no reference to anything other than Fedora appears in the top Google searches for that phrase -- but the fact that nobody outside the US gets the joke should perhaps tell you something. Not that it's offensive (people can be offended at anything) but that it's so obscure as to be completely meaningless. No wonder people try and put interpretations on it. Fedora version names don't matter to anyone, until suddenly they do and not in a good way. Best get rid of them. poc -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Oracle 11gR2 on F17
On Thu, Apr 26, 2012 at 12:46 PM, Tommy Pham wrote: > Hi, > > I'm having another problem installing Oracle 11gR2 on F17. I'm getting: > This is a known bug in Oracle's installer, and apparently they don't care since they don't support Fedora. There is a workaround described here: https://forums.oracle.com/forums/thread.jspa?threadID=1091616 > Has anyone tried to install Oracle 11gR2 on F17? -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On Fri, Apr 27, 2012 at 15:55, george2 wrote: > But also note that few women are involved in the approval processes. The > banking crises was in part formed by many individuals sensing something > wasn't right but did not take any personal responsibility to act. From Bonsai and Origami to Human Rights and Global Warming, there's a wide range of options for entertainment or worthy causes you could join if one wants to invest his/her spare time. Agonizing over a Linux distro release name is a waste of time, if you ask me. But that is just me. FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F17 wants to auto-update LibreOffice URE-runtime when I've got Apache OpenOffice 3.4 installed
I do not have LibreOffice installed on my system, I have Apache OpenOffice 3.4 RC1. However, launching the system updater notifies me that there is an update available for URE-Runtime (a component of LibreOffice) and proceeds to install such update. If this breaks Apache OpenOffice 3.4 who's to blame?. FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
no automatic connection for wireless
Dear folks, I have an acer aspire one netbook with atheros wireless: 01:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) After kernel 3.3.1(3.3.1-5.fc17.i686), the wireless does not connect automatically anymore :(, I have to push the switch on the side back and forth and after two or three moves it then starts. It used to work without this hack before in previous releases since a good while, and now it does not. [root@acer-aspire-1 ~]# uname -a Linux acer-aspire-1 3.3.2-8.fc17.i686 #1 SMP Sat Apr 21 12:41:50 UTC 2012 i686 i686 i386 GNU/Linux What do I need to do? It was working before, but now it does not have. I have to push the switch from side to side to get the wireless up, but before I did not. Is there a way I can get the default behavior back up? In FreeBSD and windows, the wireless comes up without problems, but only in Fedora. I am triple booting this netbook. Best Regards, Antonio -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Oracle 11gR2 on F17
2012/4/27 "Jóhann B. Guðmundsson" : > On 04/26/2012 07:46 PM, Tommy Pham wrote: >> >> INFO: /usr/bin/ld: warning: -z lazyload ignored. >> /usr/bin/ld: warning: -z nolazyload ignored. >> /usr/bin/ld: >> /opt/oracle/product/11.2.0/dbhome_1/sysman/lib//libnmectl.a(nmectlt.o): >> undefined reference to symbol 'B_DestroyKeyObject' >> /usr/bin/ld: note: 'B_DestroyKeyObject' is defined in DSO >> /opt/oracle/product/11.2.0/dbhome_1/lib/libnnz11.so so try adding it >> to the linker command line >> /opt/oracle/product/11.2.0/dbhome_1/lib/libnnz11.so: could not read >> symbols: Invalid operation > > > Did you try adding "-lnnz11" to to the linker command line as is suggested > there? > > JBG > -- No, because the setup is done via GUI made by Oracle. It's not a command-line based like the older versions. The entire setup is somewhat automated barring certain parameters such as destination directory, install options (Enterprise, Standard), etc... There's no configure and no make. I'm thinking there's some RPMs missing so I'm going to compare with CentOS 6.2 minimal desktop which Oracle did install OK with additional dev RPMs such as libstdc++, gcc, kernel headers, etc.. I had those same packages in F17 too but it failed to complete. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 and data loss
On Fri, 2012-04-27 at 19:21 +0200, sixpack13 wrote: > hallo > > according to this: > https://bugzilla.redhat.com/show_bug.cgi?id=817037 > > > I need your help !!! > > > > As you can read in my bug report: > > "... > I ddrescued the disc and with foremost I scratched 116.000 files from it... > > > a "cat /dev/sdb | grep " shows some/most of the files with > complete pathes are still on the disc !!! > > This makes me think: maybe there is an easy way to unchange/recover the > org. disk layout (1 partition whole disk, ext4) and files. > > But I don't know how to do that; I won't treat this disk further. > > ..." > > > Is there someone out there to help me with this problem [easer (as to > "visual grep" throught all 116.000 files, rename and sort them by hand)] As a request for help, there's probably better places to post this where you're more likely to get help, like the user list. It's not strictly anything in particular to do with F17, so it's not restricted to this list. It's just a question about recovering from data loss. > > > > HINTs: > > - shit happens ! > - leave your backup disks unplugged during installation !!! Alternatively: if you pick 'custom partition layout', then make sure you _actually check_ the layout before proceeding. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] ** RE-SCHEDULED ** 2012-05-02 @ 17:00 UTC - F17 Final Blocker Bug Review #2
On 04/27/2012 07:34 PM, Adam Williamson wrote: It's in Proposed Blockers, where it should be. Sorry, shouldn't have scanned, should have studied. Thanks. -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On Fri, 2012-04-27 at 14:55 -0400, george2 wrote: >if one headmaster says the release is inappropriate to use in the > teaching or desktop situation; > >if one religious leader objects to its use in that the supporting > material for the name says "this is your new god" > >if one advocate of equality for women speaks up > >if one government department says its use violates discrimination > in the workplace laws > >if one parent objects > > and it is picked up by the press It's a hot dog. It has always been a hot dog. The name is not an innuendo, it is not a double entendre. If anyone thinks it is, that's their problem, not ours. The whole beefy miracle thing is and _has always been_ about a food product. That aside: this list is for QA work. There's no possible basis for QA as a group to object to this or indeed _any_ given release name. If individual QA members believe there's something so terrible about the release name that it's worth trying to provoke a screaming emergency, then by all means, go ahead and do so - but I can't see any basis for doing so as an action _of the QA group_. We're doing QA, we're not debating implications of the release name. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nfs-idmap.service removed
On Fri, 2012-04-27 at 14:44 -0400, Steve Dickson wrote: > > On 04/27/2012 12:07 PM, Adam Williamson wrote: > > On Fri, 2012-04-27 at 17:07 +0100, Adam Williamson wrote: > >> On Thu, 2012-04-26 at 10:53 -0400, Steve Dickson wrote: > >> > Steve, can you elaborate? Do pure clients never need idmap? > >>> With F17 we moved to the keyring based ID mapping, which eliminates > >>> the need for the rpc.idmapd daemon to be started on the client side. > >>> > >>> Here is how it works... > >>> > >>> With NFS v4 traffic, the kernel will receives a uid string of > >>> "ste...@redhat.com" that needs to be translated into a UID integer. > >>> So the kernel will do a keyring upcall to the nfsidmap binary. > >>> The upcall is enabled with the existence of the > >>> /etc/request-key.d/id_resolver.conf file. > >>> > >>> The nfsidmap binary then converts the "ste...@redhat.com" string > >>> into the 3606 uid. That mapping is cached in the keyring > >>> which makes available the next time its needed. > >>> > >>> The nfsidmap(5) man page explains how entires on that keyring > >>> can be manipulated. > >>> > >>> I hope this helps... > >> > >> Thanks, but how about NFSv3 traffic? F17 clients will presumably still > >> need to interact with NFSv3 servers. > > > > Oh, never mind, of course I'm being dumb: idmap doesn't apply to NFSv3. > No problem I guess people are trying to use the f17 nfs-utils on with > a f15 kernel... which means there will be problems.. maybe I should add > something to the f17 nfs-utils to start rpc.idmap on kernels non 3.3 kernels? No, I don't think we need to support that. 17's supported kernel is 3.3. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 17 updates-testing report
The following Fedora 17 Security updates need testing: https://admin.fedoraproject.org/updates/FEDORA-2012-6273/openstack-nova-2012.1-2.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6282/bugzilla-4.0.6-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5599/phpMyAdmin-3.5.0-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6334/sectool-0.9.5-7.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6494/wordpress-3.3.2-2.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6451/hddtemp-0.3-0.24.beta15.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5785/python3-3.2.3-2.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6588/dokuwiki-0-0.11.20110525.a.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6635/gdb-7.4.50.20120120-42.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5892/python-2.7.3-3.fc17,python-docs-2.7.3-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6600/firefox-12.0-1.fc17,xulrunner-12.0-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6689/openconnect-3.18-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-/bind-dyndb-ldap-1.1.0-0.11.rc1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6674/puppet-2.7.13-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6694/thunderbird-12.0-1.fc17,thunderbird-lightning-1.4-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6704/asterisk-10.3.1-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6132/rubygems-1.8.23-20.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6257/cifs-utils-5.4-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6869/php-5.4.1-1.fc17,maniadrive-1.2-38.fc17 The following Fedora 17 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/FEDORA-2012-6873/gvfs-1.12.2-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6819/libssh2-1.4.1-2.fc17 https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-119.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6811/xorg-x11-drv-synaptics-1.5.99.904-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6800/livecd-tools-17.10-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6786/xorg-x11-xinit-1.3.2-5.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6823/xorg-x11-drv-vesa-2.3.1-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6815/anaconda-17.23-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6660/libvdpau-0.4.1-7.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6693/mactel-boot-0.9-5.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6694/thunderbird-12.0-1.fc17,thunderbird-lightning-1.4-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6686/webkitgtk-1.8.1-1.fc17,webkitgtk3-1.8.1-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6698/perl-Net-SSLeay-1.48-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6635/gdb-7.4.50.20120120-42.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6582/mash-0.5.26-3.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6585/xorg-x11-drv-intel-2.18.0-2.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6603/dracut-018-26.git20120424.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6579/policycoreutils-2.1.11-6.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6580/apper-0.7.1-4.fc17,PackageKit-0.7.4-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6598/openldap-2.4.31-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6458/NetworkManager-0.9.4.0-7.git20120403.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6491/lorax-17.16-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6475/gdisk-0.8.4-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6476/telepathy-glib-0.18.1-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6453/pcre-8.21-5.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6442/taglib-1.7.2-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6576/libselinux-2.1.10-3.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6075/colord-0.1.19-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6111/sane-backends-1.0.22-10.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6165/perl-IO-Socket-SSL-1.66-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5976/pungi-2.11-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5892/python-2.7.3-3.fc17,python-docs-2.7.3-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5710/libpciaccess-0.13.1-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5575/libxcb-1.8.1-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-5335/xmlrpc-c-1.29.3-170
[no subject]
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] ** RE-SCHEDULED ** 2012-05-02 @ 17:00 UTC - F17 Final Blocker Bug Review #2
On Fri, 2012-04-27 at 13:56 -0400, Clyde E. Kunkel wrote: > On 04/27/2012 12:25 PM, Adam Williamson wrote: > > # F17 Final Blocker Review meeting #2 > > # Date: 2012-05-02 > > # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) > > # Location: #fedora-bugzappers on irc.freenode.net > > > > The second F17 final blocker bug review meeting will be re-scheduled to > > Tuesday 2012-05-02 at 17:00 UTC in #fedora-bugzappers, as most regular > > attendees are unavailable at the regular time. > > > > We'll be running through the beta blockers and nice-to-haves. An updated > > list of blocker bugs is available at: > > https://fedoraproject.org/wiki/Current_Release_Blockers. > > > > We'll be reviewing the bugs to determine ... > > > > 1. Whether they meet the final release criteria [1] and should stay > > on the list > > 2. Whether they are getting the attention they need > > > > [1] http://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria > > > > For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to > > - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process > > - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process > > > > For the blocker review meeting protocol, see > > - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting > > > I don't see "Bug 816613 - ValueError: not enough space in VG" on any of > the blocker lists. This is a regression introduced post beta. It's in Proposed Blockers, where it should be. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Oracle 11gR2 on F17
On 04/26/2012 07:46 PM, Tommy Pham wrote: INFO: /usr/bin/ld: warning: -z lazyload ignored. /usr/bin/ld: warning: -z nolazyload ignored. /usr/bin/ld: /opt/oracle/product/11.2.0/dbhome_1/sysman/lib//libnmectl.a(nmectlt.o): undefined reference to symbol 'B_DestroyKeyObject' /usr/bin/ld: note: 'B_DestroyKeyObject' is defined in DSO /opt/oracle/product/11.2.0/dbhome_1/lib/libnnz11.so so try adding it to the linker command line /opt/oracle/product/11.2.0/dbhome_1/lib/libnnz11.so: could not read symbols: Invalid operation Did you try adding "-lnnz11" to to the linker command line as is suggested there? JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On 04/27/2012 06:55 PM, george2 wrote: I don't know the future, but I think that releasing with this name has the potential to be a destroyer of the momentum that the contributors to Fedora with the support of RedHat have worked to build. First and foremost the release name does not have any bearing on the code we ship. Secondly the community votes upon the release name so if you want to affect those resault you do so by casting your vote. Thirdly this is not the list to discuss this. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 15 updates-testing report
The following Fedora 15 Security updates need testing: https://admin.fedoraproject.org/updates/FEDORA-2012-6371/nginx-1.0.15-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-5631/phpMyAdmin-3.5.0-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6395/openssl-1.0.0i-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6414/rubygems-1.7.2-5.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6349/samba4-4.0.0-26.alpha11.fc15.6 https://admin.fedoraproject.org/updates/FEDORA-2012-6396/bugzilla-3.6.9-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6511/wordpress-3.3.2-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6630/dokuwiki-0-0.10.20110525.a.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6610/xulrunner-12.0-1.fc15,firefox-12.0-1.fc15,gnome-python2-extras-2.25.3-35.fc15.7,perl-Gtk2-MozEmbed-0.09-1.fc15.11 https://admin.fedoraproject.org/updates/FEDORA-2012-5916/python3-3.2.3-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6629/gdb-7.3.1-50.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6730/openconnect-3.18-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6717/thunderbird-12.0-1.fc15,thunderbird-lightning-1.4-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6724/asterisk-1.8.11.1-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6759/bind-dyndb-ldap-1.1.0-0.11.rc1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6398/cifs-utils-5.4-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2011-17233/tor-0.2.1.32-1500.fc15 The following Fedora 15 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/FEDORA-2012-6717/thunderbird-12.0-1.fc15,thunderbird-lightning-1.4-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6629/gdb-7.3.1-50.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6552/PackageKit-0.6.17-2.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6517/pcre-8.12-8.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6395/openssl-1.0.0i-1.fc15 https://admin.fedoraproject.org/updates/FEDORA-2012-6373/fuse-2.8.7-1.fc15.1 https://admin.fedoraproject.org/updates/FEDORA-2012-5915/python-2.7.3-2.fc15,python-docs-2.7.3-1.fc15 https://admin.fedoraproject.org/updates/dracut-009-15.fc15 https://admin.fedoraproject.org/updates/FEDORA-2011-13190/phonon-backend-gstreamer-4.5.90-2.fc15,phonon-4.5.57-1.20110914.fc15 The following builds have been pushed to Fedora 15 updates-testing BitchX-1.2-4.fc15 Cython-0.16-1.fc15 fcitx-4.2.2-2.fc15 kdemultimedia-4.6.5-3.fc15 mc-4.8.3-1.fc15 mosh-1.2-1.fc15 rtpproxy-1.2.1-7.fc15 sems-1.4.2-6.fc15 sx-2.10-1.fc15 yagf-0.9.1-3.fc15 zabbix-1.8.12-1.fc15 Details about builds: BitchX-1.2-4.fc15 (FEDORA-2012-6860) IrcII chat client Update Information: Package Name: BitchX Short Description: The Ultimate IRC client. Owners: vicodan Branches: f15 f16 f17 InitialCC: rdieter References: [ 1 ] Bug #812574 - Review Request: BitchX - IRC chat client https://bugzilla.redhat.com/show_bug.cgi?id=812574 Cython-0.16-1.fc15 (FEDORA-2012-6836) A language for writing Python extension modules Update Information: see: http://wiki.cython.org/ReleaseNotes-0.16 ChangeLog: * Fri Apr 27 2012 Neal Becker - 0.16-1 - Update to 0.16 * Thu Jan 12 2012 Fedora Release Engineering - 0.15.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild fcitx-4.2.2-2.fc15 (FEDORA-2012-6851) Free Chinese Input Toy for X (XIM) Update Information: Build with %cmake macro (rhbz 738016) Fix the ownership of directories (rhbz 816513) Upstream to fcitx-4.2.2 Upstream to fcitx-4.2.2 Upstream to fcitx-4.2.2 ChangeLog: * Thu Apr 26 2012 Liang Suilong - 4.2.2-2 - Build with %cmake macro (rhbz 738016) - Fix the ownership of directories (rhbz 816513) * Sun Apr 22 2012 Liang Suilong - 4.2.2-1 - Upgrade to fcitx-4.2.2 --
Fedora 16 updates-testing report
The following Fedora 16 Security updates need testing: https://admin.fedoraproject.org/updates/FEDORA-2012-6365/openstack-nova-2011.3.1-8.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6368/bugzilla-4.0.6-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5624/phpMyAdmin-3.5.0-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6375/cifs-utils-5.4-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6411/nginx-1.0.15-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6409/rubygems-1.8.11-3.fc16.1 https://admin.fedoraproject.org/updates/FEDORA-2012-6529/argyllcms-1.4.0-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5058/expat-2.1.0-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5833/python3-3.2.3-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6628/dokuwiki-0-0.10.20110525.a.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6542/wordpress-3.3.2-2.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5924/python-2.7.3-1.fc16,python-docs-2.7.3-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6738/thunderbird-12.0-1.fc16,thunderbird-lightning-1.4-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6612/asterisk-1.8.11.1-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6614/gdb-7.3.50.20110722-16.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6758/openconnect-3.18-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2011-14691/tomcat6-6.0.32-19.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6722/bind-dyndb-ldap-1.1.0-0.11.rc1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6382/samba4-4.0.0-38.alpha16.fc16 The following Fedora 16 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/FEDORA-2012-6837/livecd-tools-16.14-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6726/livecd-tools-16.13-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6614/gdb-7.3.50.20110722-16.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6613/selinux-policy-3.10.0-86.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6516/pcre-8.12-9.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6389/taglib-1.7.2-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6416/fuse-2.8.7-1.fc16.1 https://admin.fedoraproject.org/updates/FEDORA-2012-6204/libdrm-2.4.33-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6209/xorg-x11-drv-ati-6.14.3-5.20120201git36c190671.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-6004/sane-backends-1.0.22-10.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-5906/rsyslog-5.8.10-1.fc16 https://admin.fedoraproject.org/updates/FEDORA-2012-3319/GConf2-3.2.3-4.fc16 The following builds have been pushed to Fedora 16 updates-testing BitchX-1.2-4.fc16 Cython-0.16-1.fc16 apache-commons-compress-1.4-1.fc16 blueman-1.23-1.fc16 clipit-1.4.2-1.fc16 evtest-1.30-1.fc16 fcitx-4.2.2-2.fc16 lcg-infosites-3.1.0-2.fc16 leechcraft-0.5.65-1.fc16 libsvm-3.12-1.fc16 liferea-1.8.5-1.fc16 livecd-tools-16.14-1.fc16 mosh-1.2-1.fc16 rtpproxy-1.2.1-7.fc16 sems-1.4.2-6.fc16 splix-2.0.1-0.8.20120419svn.fc16 sx-2.10-1.fc16 yagf-0.9.1-3.fc16 zabbix-1.8.12-1.fc16 zanata-util-0.2.7-1.fc16 Details about builds: BitchX-1.2-4.fc16 (FEDORA-2012-6848) IrcII chat client Update Information: Package Name: BitchX Short Description: The Ultimate IRC client. Owners: vicodan Branches: f15 f16 f17 InitialCC: rdieter References: [ 1 ] Bug #812574 - Review Request: BitchX - IRC chat client https://bugzilla.redhat.com/show_bug.cgi?id=812574 Cython-0.16-1.fc16 (FEDORA-2012-6857) A language for writing Python extension modules Update Information: see: http://wiki.cython.org/ReleaseNotes-0.16 ChangeLog: * Fri Apr 27 2012 Neal Becker - 0.16-1 - Update to 0.16 * Thu Jan 12 2012 Fedora Release Engineering - 0.15.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild apache-commons-compress-1.4-1.fc16 (FEDORA-2012-6831) Java API for working wit
Re: Karma needed for TC2 builds
On Fri, Apr 27, 2012 at 17:23:46 +0100, Adam Williamson wrote: Hey, folks! Can people please provide karma for these builds if possible: https://admin.fedoraproject.org/updates/FEDORA-2012-6800/livecd-tools-17.10-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6815/anaconda-17.23-1.fc17 (you can 'yum localinstall' anaconda into a live image, then run an install, to get a smoke test) https://admin.fedoraproject.org/updates/grub-0.97-93.fc17 (need an EFI machine really for this one) we would like to pull them into TC2. Thanks! At the kernel meeting it was noted that it would be nice to get a 3.3.4 kernel on TC2. kernel-3.3.4-1.fc17 is building now. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On Fri, Apr 27, 2012 at 16:07, Frank Murphy wrote: > Lets not delay the release. +1 who cares about the name? FC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On 27/04/12 19:55, george2 wrote: I don't know the future, but I think that releasing with this name has the potential to be a destroyer of the momentum that the contributors to Fedora with the support of RedHat have worked to build. Lets not delay the release. -- Regards, Frank "Jack of all, fubars" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
block on name
I present a request to not move to release F17 until the release name is changed in the released code. I appreciate the comments public and private but it remains that this name may do considerable harm. There is not formal criterion for a blocker bug. So I appeal to this group, as the last in the community, to present their decision that the release is not yet ready, for humanitarian reasons. You would block if there was a flaw in an important technical element, but Fedora is more than technology, it is a community. Most who communicated with me believe this is not the place to raise this request. That iis too late in the process. The name process was discussed by the "board" and they declined to address the concerns raised and defer to address naming and word meaning and connotations at a future release. If this had been flushed-out when the warning was raised, it would not have impacted the placement of the objected-to name in so many places and documentation and release notes. I was not part of those initial dialogs. Some have said to me that it cannot be stopped because "legal" or some other group did not object so it is ok for Testing to assume ok. But also note that few women are involved in the approval processes. The banking crises was in part formed by many individuals sensing something wasn't right but did not take any personal responsibility to act. Consider please: if one headmaster says the release is inappropriate to use in the teaching or desktop situation; if one religious leader objects to its use in that the supporting material for the name says "this is your new god" if one advocate of equality for women speaks up if one government department says its use violates discrimination in the workplace laws if one parent objects and it is picked up by the press I don't know the future, but I think that releasing with this name has the potential to be a destroyer of the momentum that the contributors to Fedora with the support of RedHat have worked to build. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] ** RE-SCHEDULED ** 2012-05-02 @ 17:00 UTC - F17 Final Blocker Bug Review #2
On 04/27/2012 12:25 PM, Adam Williamson wrote: # F17 Final Blocker Review meeting #2 # Date: 2012-05-02 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) # Location: #fedora-bugzappers on irc.freenode.net The second F17 final blocker bug review meeting will be re-scheduled to Tuesday 2012-05-02 at 17:00 UTC in #fedora-bugzappers, as most regular attendees are unavailable at the regular time. We'll be running through the beta blockers and nice-to-haves. An updated list of blocker bugs is available at: https://fedoraproject.org/wiki/Current_Release_Blockers. We'll be reviewing the bugs to determine ... 1. Whether they meet the final release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process For the blocker review meeting protocol, see - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting I don't see "Bug 816613 - ValueError: not enough space in VG" on any of the blocker lists. This is a regression introduced post beta. -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17-branched repo is not installable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/27/2012 12:10 PM, Adam Williamson wrote: > On Thu, 2012-04-26 at 15:18 -0400, Daniel J Walsh wrote: > > selinux-policy needs a newer checkpolicy >>> Thank you. >> I believe the checkpolicy and libsepol have made their way out of >> testing, so they should show up soon. > > Dan, in future, please bundle interdependent packages like this into a > single update, to avoid this kind of problem. Yes Like already told me this, although it would be nice if the tooling took care of this for the user... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+a2ToACgkQrlYvE4MpobOwSACgpAVrKlFwf6ChigPqnND9ivSS BxsAoMl4rZl3/Jup7f+bhM8PpTJGeBOx =4697 -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F17 and data loss
hallo according to this: https://bugzilla.redhat.com/show_bug.cgi?id=817037 I need your help !!! As you can read in my bug report: "... I ddrescued the disc and with foremost I scratched 116.000 files from it... a "cat /dev/sdb | grep " shows some/most of the files with complete pathes are still on the disc !!! This makes me think: maybe there is an easy way to unchange/recover the org. disk layout (1 partition whole disk, ext4) and files. But I don't know how to do that; I won't treat this disk further. ..." Is there someone out there to help me with this problem [easer (as to "visual grep" throught all 116.000 files, rename and sort them by hand)] HINTs: - shit happens ! - leave your backup disks unplugged during installation !!! thx -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] ** RE-SCHEDULED ** 2012-05-02 @ 17:00 UTC - F17 Final Blocker Bug Review #2
# F17 Final Blocker Review meeting #2 # Date: 2012-05-02 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) # Location: #fedora-bugzappers on irc.freenode.net The second F17 final blocker bug review meeting will be re-scheduled to Tuesday 2012-05-02 at 17:00 UTC in #fedora-bugzappers, as most regular attendees are unavailable at the regular time. We'll be running through the beta blockers and nice-to-haves. An updated list of blocker bugs is available at: https://fedoraproject.org/wiki/Current_Release_Blockers. We'll be reviewing the bugs to determine ... 1. Whether they meet the final release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process For the blocker review meeting protocol, see - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ 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
Karma needed for TC2 builds
Hey, folks! Can people please provide karma for these builds if possible: https://admin.fedoraproject.org/updates/FEDORA-2012-6800/livecd-tools-17.10-1.fc17 https://admin.fedoraproject.org/updates/FEDORA-2012-6815/anaconda-17.23-1.fc17 (you can 'yum localinstall' anaconda into a live image, then run an install, to get a smoke test) https://admin.fedoraproject.org/updates/grub-0.97-93.fc17 (need an EFI machine really for this one) we would like to pull them into TC2. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On Fri, 2012-04-27 at 15:30 +0200, Thomas Spura wrote: > On Fri, Apr 27, 2012 at 3:26 PM, Matthias Clasen wrote: > > On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote: > > > >> > >> Apart of this, there are test-cases, which can not be/can not be easily > >> executed inside of a mock-environment as part of building. > > > > Not to mention that running extensive test suites for every build will > > put strain on our build infrastructure. The build system is just not the > > right place for running tests. > > Where else do you want to run AutoQA? AutoQA runs on separate machines from the build farm. The point is that tests put in rpm %check are inevitably run as part of the build process, and so tie up build farm resources. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17-branched repo is not installable
On Thu, 2012-04-26 at 15:18 -0400, Daniel J Walsh wrote: > >>> selinux-policy needs a newer checkpolicy > > Thank you. > I believe the checkpolicy and libsepol have made their way out of testing, so > they should show up soon. Dan, in future, please bundle interdependent packages like this into a single update, to avoid this kind of problem. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nfs-idmap.service removed
On Fri, 2012-04-27 at 17:07 +0100, Adam Williamson wrote: > On Thu, 2012-04-26 at 10:53 -0400, Steve Dickson wrote: > > > > Steve, can you elaborate? Do pure clients never need idmap? > > With F17 we moved to the keyring based ID mapping, which eliminates > > the need for the rpc.idmapd daemon to be started on the client side. > > > > Here is how it works... > > > > With NFS v4 traffic, the kernel will receives a uid string of > > "ste...@redhat.com" that needs to be translated into a UID integer. > > So the kernel will do a keyring upcall to the nfsidmap binary. > > The upcall is enabled with the existence of the > > /etc/request-key.d/id_resolver.conf file. > > > > The nfsidmap binary then converts the "ste...@redhat.com" string > > into the 3606 uid. That mapping is cached in the keyring > > which makes available the next time its needed. > > > > The nfsidmap(5) man page explains how entires on that keyring > > can be manipulated. > > > > I hope this helps... > > Thanks, but how about NFSv3 traffic? F17 clients will presumably still > need to interact with NFSv3 servers. Oh, never mind, of course I'm being dumb: idmap doesn't apply to NFSv3. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nfs-idmap.service removed
On Thu, 2012-04-26 at 10:53 -0400, Steve Dickson wrote: > > Steve, can you elaborate? Do pure clients never need idmap? > With F17 we moved to the keyring based ID mapping, which eliminates > the need for the rpc.idmapd daemon to be started on the client side. > > Here is how it works... > > With NFS v4 traffic, the kernel will receives a uid string of > "ste...@redhat.com" that needs to be translated into a UID integer. > So the kernel will do a keyring upcall to the nfsidmap binary. > The upcall is enabled with the existence of the > /etc/request-key.d/id_resolver.conf file. > > The nfsidmap binary then converts the "ste...@redhat.com" string > into the 3606 uid. That mapping is cached in the keyring > which makes available the next time its needed. > > The nfsidmap(5) man page explains how entires on that keyring > can be manipulated. > > I hope this helps... Thanks, but how about NFSv3 traffic? F17 clients will presumably still need to interact with NFSv3 servers. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2012-04-27 @ 17:00 UTC - F17 Final Blocker Bug Review #2
On Thu, 2012-04-26 at 10:14 -0600, Tim Flink wrote: > # F17 Final Blocker Review meeting #2 > # Date: 2012-04-27 > # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) > # Location: #fedora-bugzappers on irc.freenode.net > > The second F17 final blocker bug review meeting will be this Friday at > 17:00 UTC in #fedora-bugzappers. We'll be running through the beta > blockers and nice-to-haves. An updated list of blocker bugs is > available at: https://fedoraproject.org/wiki/Current_Release_Blockers. > > We'll be reviewing the bugs to determine ... > > 1. Whether they meet the final release criteria [1] and should stay > on the list > 2. Whether they are getting the attention they need > > [1] http://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria > > For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to > - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process > - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process > > For the blocker review meeting protocol, see > - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting > > Tim > ___ > test-announce mailing list > test-annou...@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/test-announce I just realized - I can't attend the meeting (got my times mixed up), I'll be at the opera. I believe Tim said he will also be unable to attend. Is anyone else able to attend and run the meeting? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2012-04-27 @ 17:00 UTC - F17 Final Blocker Bug Review #2
On Thu, 2012-04-26 at 10:14 -0600, Tim Flink wrote: > # F17 Final Blocker Review meeting #2 > # Date: 2012-04-27 > # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) > # Location: #fedora-bugzappers on irc.freenode.net > > The second F17 final blocker bug review meeting will be this Friday at > 17:00 UTC in #fedora-bugzappers. We'll be running through the beta > blockers and nice-to-haves. An updated list of blocker bugs is > available at: https://fedoraproject.org/wiki/Current_Release_Blockers. > > We'll be reviewing the bugs to determine ... > > 1. Whether they meet the final release criteria [1] and should stay > on the list > 2. Whether they are getting the attention they need > > [1] http://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria > > For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to > - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process > - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process > > For the blocker review meeting protocol, see > - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting I just realized - I can't attend the meeting (got my times mixed up), I'll be at the opera. I believe Tim said he will also be unable to attend. Is anyone else able to attend and run the meeting? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On 04/27/2012 04:38 PM, Ed Greshko wrote: > On 04/27/2012 10:28 PM, Ed Greshko wrote: >> Now, I can't get the failure to reproduce at all! > > Well, it gets a bit weirder And still a bit weirder: The problem depends on the runlevel: Booting into runlevel 3 (no graphics) lets my system then reboot flawlessly, the hangup only happens if I try to reboot if I'm in runlevel 5. Kind regards Joachim Backes 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
Fw: nfs-idmap.service removed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Begin forwarded message: Date: Fri, 27 Apr 2012 10:52:14 -0400 From: Steve Dickson To: Dennis Gilmore Subject: Fwd: Re: nfs-idmap.service removed - Original Message Subject: Re: nfs-idmap.service removed Date: Thu, 26 Apr 2012 11:40:07 -0400 From: Steve Dickson To: Ed Greshko CC: For testing and quality assurance of Fedora releases On 04/26/2012 11:31 AM, Ed Greshko wrote: > On 04/26/2012 10:55 PM, Steve Dickson wrote: >> >> On 04/26/2012 08:06 AM, Ed Greshko wrote: >>> On 04/26/2012 07:31 PM, Adam Williamson wrote: On Thu, 2012-04-26 at 07:49 +0800, Ed Greshko wrote: > Is there anywhere documentation outlining the decision to remove > a separate nfs-idmap.service from F17? It seems that > nfs-server.service must be enabled and started in order for > rpc.idmapd. It doesn't seem logical that a system running a NFS > Client Only should be required to also run an NFS server. The changelog message reads: "Removed the nfs-idmap service. rpc.idmap is now part of the nfs-server service" Steve, can you elaborate? Do pure clients never need idmap? >>> Sure they do, if they want uid/gid mapped properly. >>> >>> Here is the output from an F16 system showing the effect >>> >>> First I mount with no rpc.idmap service running >>> >>> [root@f16-1 ~]# mount -t nfs4 192.168.0.55:/syntegra /syntegra >>> [root@f16-1 ~]# ll /syntegra/ >>> total 40 >>> drwxrwxr-x. 3 4294967294 4294967294 4096 Mar 24 2010 HP-Pavilion >>> drwxr-xr-x. 9 4294967294 4294967294 4096 Nov 30 10:21 iso >>> drwxrwxr-x. 7 4294967294 4294967294 4096 Nov 30 10:34 >>> linux-releases drwx--. 2 4294967294 4294967294 16384 Apr 1 >>> 2007 lost+found >>> >>> And...then >>> >>> [root@f16-1 ~]# umount /syntegra >>> [root@f16-1 ~]# systemctl start nfs-idmap.service >>> [root@f16-1 ~]# mount -t nfs4 192.168.0.55:/syntegra /syntegra >>> [root@f16-1 ~]# ll /syntegra/ >>> total 40 >>> drwxrwxr-x. 3 egreshko egreshko 4096 Mar 24 2010 HP-Pavilion >>> drwxr-xr-x. 9 egreshko egreshko 4096 Nov 30 10:21 iso >>> drwxrwxr-x. 7 egreshko egreshko 4096 Nov 30 10:34 linux-releases >>> drwx--. 2 root root 16384 Apr 1 2007 lost+found >>> >>> Notice the difference? >>> >>> >> From your root prompt "[root@f16-1 ~]#" it appears you are on >> a f16 machine... In that cause yes the rpc.idmap service is needed. >> > > I see > > So, what has changed where rpc.idmap service is no longer needed on > the client side to do proper mapping in nfs4? > There was support added to the F17 kernel as well as the F17 nfs-utils, namely the nfsidmap command which replaces the need for the rpc.idmapd daemon. steved. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+astoACgkQkSxm47BaWffWKgCdHvrsYxR5B+Kr8okkDyON6+31 y2kAoMHYqNvUnCAJy2K1jSxmohGEW/Bp =MITH -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fw: nfs-idmap.service removed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Begin forwarded message: Date: Fri, 27 Apr 2012 10:51:49 -0400 From: Steve Dickson To: Dennis Gilmore Subject: Fwd: Re: nfs-idmap.service removed - Original Message Subject: Re: nfs-idmap.service removed Date: Thu, 26 Apr 2012 10:55:53 -0400 From: Steve Dickson To: Ed Greshko CC: For testing and quality assurance of Fedora releases On 04/26/2012 08:06 AM, Ed Greshko wrote: > On 04/26/2012 07:31 PM, Adam Williamson wrote: >> On Thu, 2012-04-26 at 07:49 +0800, Ed Greshko wrote: >>> Is there anywhere documentation outlining the decision to remove a >>> separate nfs-idmap.service from F17? It seems that >>> nfs-server.service must be enabled and started in order for >>> rpc.idmapd. It doesn't seem logical that a system running a NFS >>> Client Only should be required to also run an NFS server. >> The changelog message reads: >> >> "Removed the nfs-idmap service. rpc.idmap is now part of the >> nfs-server service" >> >> Steve, can you elaborate? Do pure clients never need idmap? > > Sure they do, if they want uid/gid mapped properly. > > Here is the output from an F16 system showing the effect > > First I mount with no rpc.idmap service running > > [root@f16-1 ~]# mount -t nfs4 192.168.0.55:/syntegra /syntegra > [root@f16-1 ~]# ll /syntegra/ > total 40 > drwxrwxr-x. 3 4294967294 4294967294 4096 Mar 24 2010 HP-Pavilion > drwxr-xr-x. 9 4294967294 4294967294 4096 Nov 30 10:21 iso > drwxrwxr-x. 7 4294967294 4294967294 4096 Nov 30 10:34 linux-releases > drwx--. 2 4294967294 4294967294 16384 Apr 1 2007 lost+found > > And...then > > [root@f16-1 ~]# umount /syntegra > [root@f16-1 ~]# systemctl start nfs-idmap.service > [root@f16-1 ~]# mount -t nfs4 192.168.0.55:/syntegra /syntegra > [root@f16-1 ~]# ll /syntegra/ > total 40 > drwxrwxr-x. 3 egreshko egreshko 4096 Mar 24 2010 HP-Pavilion > drwxr-xr-x. 9 egreshko egreshko 4096 Nov 30 10:21 iso > drwxrwxr-x. 7 egreshko egreshko 4096 Nov 30 10:34 linux-releases > drwx--. 2 root root 16384 Apr 1 2007 lost+found > > Notice the difference? > > - From your root prompt "[root@f16-1 ~]#" it appears you are on a f16 machine... In that cause yes the rpc.idmap service is needed. steved. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+astIACgkQkSxm47BaWfcAPgCeKXLcZ8VVDLi7/OZWOrEXfNeB IMkAnj6cL1yvF/AsLjhIS/AqmkPRvCRB =C0hD -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fw: nfs-idmap.service removed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Begin forwarded message: Date: Fri, 27 Apr 2012 10:51:34 -0400 From: Steve Dickson To: Dennis Gilmore Subject: Fwd: Re: nfs-idmap.service removed - Original Message Subject: Re: nfs-idmap.service removed Date: Thu, 26 Apr 2012 10:53:16 -0400 From: Steve Dickson To: Adam Williamson CC: For testing and quality assurance of Fedora releases On 04/26/2012 07:31 AM, Adam Williamson wrote: > On Thu, 2012-04-26 at 07:49 +0800, Ed Greshko wrote: >> Is there anywhere documentation outlining the decision to remove a >> separate nfs-idmap.service from F17? It seems that >> nfs-server.service must be enabled and started in order for >> rpc.idmapd. It doesn't seem logical that a system running a NFS >> Client Only should be required to also run an NFS server. > > The changelog message reads: > > "Removed the nfs-idmap service. rpc.idmap is now part of the > nfs-server service" > > Steve, can you elaborate? Do pure clients never need idmap? With F17 we moved to the keyring based ID mapping, which eliminates the need for the rpc.idmapd daemon to be started on the client side. Here is how it works... With NFS v4 traffic, the kernel will receives a uid string of "ste...@redhat.com" that needs to be translated into a UID integer. So the kernel will do a keyring upcall to the nfsidmap binary. The upcall is enabled with the existence of the /etc/request-key.d/id_resolver.conf file. The nfsidmap binary then converts the "ste...@redhat.com" string into the 3606 uid. That mapping is cached in the keyring which makes available the next time its needed. The nfsidmap(5) man page explains how entires on that keyring can be manipulated. I hope this helps... steved. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+assoACgkQkSxm47BaWfduMwCeKDIJcTsD92iQm+RfjTOYQfVH 6nYAn0q23hQ/tRwaYxpXAl31/7dxwHz4 =6wO/ -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On 04/27/2012 10:28 PM, Ed Greshko wrote: > Now, I can't get the failure to reproduce at all! Well, it gets a bit weirder If I shutdown from the login screen I get the 2 minute delay. If I shutdown from within KDE it doesn't "delay" but dies on a kernel panic... Last few lines are... Cannot finalize remaining file systems and devices, giving up. Successfully changed into root pivot. /bin/sh: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory kernel panic - not syncing: Attempted to kill init! -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On 04/27/2012 09:45 PM, Pedro Francisco wrote: > On Fri, Apr 27, 2012 at 8:22 AM, Joachim Backes > wrote: >> after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17), rebooting >> hangs up. > Is it just me or disabling wireless/unplugging the network cable seems to > work ? > OK Now this is really weird My F17 system is in a VM. I'm also using KDE. Before doing the shutdown from the KDE menu I "disconnected the cable" in the VM settings. The shutdown seemed to work immediately but then died on a panic. I tried this a few times and it was repeatable. On a subsequent try I left the cable connected and clicked on "Leave-->Shutdown" but no dialog box popped up. I waited a minute or sonothing. So, I issued an "init 6" and the system rebooted immediately. Now, I can't get the failure to reproduce at all! -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
> On Fri, Apr 27, 2012 at 3:26 PM, Matthias Clasen > wrote: > > On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote: > > > >> > >> Apart of this, there are test-cases, which can not be/can not be > >> easily > >> executed inside of a mock-environment as part of building. > > > > Not to mention that running extensive test suites for every build > > will > > put strain on our build infrastructure. The build system is just > > not the > > right place for running tests. > > Where else do you want to run AutoQA? We have some systems provided by Fedora Infrastructure that we use to execute certain generic tests, like dependency and upgrade path checking. Results are posted into Bodhi as comments to proposed updates. We currently can't execute arbitrary package-specific tests inside AutoQA, I'm sorry. We plan to make it happen some time. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On Fri, Apr 27, 2012 at 8:22 AM, Joachim Backes wrote: > after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17), rebooting > hangs up. Is it just me or disabling wireless/unplugging the network cable seems to work ? -- Pedro -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On Fri, Apr 27, 2012 at 3:26 PM, Matthias Clasen wrote: > On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote: > >> >> Apart of this, there are test-cases, which can not be/can not be easily >> executed inside of a mock-environment as part of building. > > Not to mention that running extensive test suites for every build will > put strain on our build infrastructure. The build system is just not the > right place for running tests. Where else do you want to run AutoQA? -- Tom -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote: > > Apart of this, there are test-cases, which can not be/can not be easily > executed inside of a mock-environment as part of building. Not to mention that running extensive test suites for every build will put strain on our build infrastructure. The build system is just not the right place for running tests. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20120427 changes
Compose started at Fri Apr 27 08:15:04 UTC 2012 Broken deps for x86_64 -- [389-admin] 389-admin-1.1.28-1.fc18.i686 requires libicuuc.so.48 389-admin-1.1.28-1.fc18.i686 requires libicui18n.so.48 389-admin-1.1.28-1.fc18.i686 requires libicudata.so.48 389-admin-1.1.28-1.fc18.x86_64 requires libicuuc.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicui18n.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicudata.so.48()(64bit) [389-adminutil] 389-adminutil-1.1.15-2.fc17.i686 requires libicuuc.so.48 389-adminutil-1.1.15-2.fc17.i686 requires libicui18n.so.48 389-adminutil-1.1.15-2.fc17.i686 requires libicudata.so.48 389-adminutil-1.1.15-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-adminutil-1.1.15-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-adminutil-1.1.15-2.fc17.x86_64 requires libicudata.so.48()(64bit) [389-ds-base] 389-ds-base-1.2.11-0.1.a1.fc18.x86_64 requires libicuuc.so.48()(64bit) 389-ds-base-1.2.11-0.1.a1.fc18.x86_64 requires libicui18n.so.48()(64bit) 389-ds-base-1.2.11-0.1.a1.fc18.x86_64 requires libicudata.so.48()(64bit) 389-ds-base-1.2.11-0.1.a1.fc18.x86_64 requires libdb-5.2.so()(64bit) [389-dsgw] 389-dsgw-1.1.9-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicudata.so.48()(64bit) [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc18.noarch requires ruby-nokogiri [axis2c] axis2c-1.6.0-4.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 axis2c-1.6.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [bibletime] bibletime-2.9.1-1.fc18.x86_64 requires libicuuc.so.48()(64bit) bibletime-2.9.1-1.fc18.x86_64 requires libicui18n.so.48()(64bit) [boost141] boost141-graph-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-graph-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-graph-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-graph-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) boost141-regex-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-regex-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-regex-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-regex-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) [couchdb] couchdb-1.1.1-1.fc18.x86_64 requires libicuuc.so.48()(64bit) couchdb-1.1.1-1.fc18.x86_64 requires libicui18n.so.48()(64bit) couchdb-1.1.1-1.fc18.x86_64 requires libicudata.so.48()(64bit) [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [eclipse-shelled] eclipse-shelled-2.0.2-0.1.20120420svn.fc18.noarch requires eclipse-platform >= 1:4.2.0-6 [gcc-python-plugin] gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 [glump] glump-0.9.11-10.fc17.noarch requires mod_python [gnome-applet-sensors] gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0 gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) [gorm] gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23 gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-gui.so.0.20()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-base.so.1.23()(64bit) [koji] koji-hub-1.6.0-3.fc17.noarch requires mod_python koji-web-1.6.0-3.fc17.noarch requires mod_python [libircclient-qt] libircclient-qt-0.5.0-4.fc17.i686 requires libicuuc.so.48 libircclient-qt-0.5.0-4.fc17.i686 requires libicui18n.so.48 libircclient-qt-0.5.0-4.fc17.i686 requires libicudata.so.48 libircclient-qt-0.5.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit) libircclient-qt-0.5.0-4.fc17.x86_64 requires libicui18n.so.48()(64bit) libircclient-qt-0.5.0-4.fc17.x86_64 requires libicudata.so.48()(64bit) [lv2-ui] lv2-ui-devel-2.4-4.fc17.i686 requires lv2-ui(x86-32) = 0:2.4-4.fc17 [mapnik] mapnik-2.0.0-4.fc17.i686 requires libicuuc.so.48 mapnik-2.0.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit) mapnik-utils-2.0.0-4.fc17.x86_64 requires
Re: Testing of packages
On 04/27/2012 02:11 PM, Matthias Runge wrote: I wonder how different a run-time test-suite dffers from a test suite to be executed during build. There are 2 major differences: 1. The package-to-test itself is not installed to its final destination. 2. A testsuite being run in %check has access to the source-tree and build-tree. Both together imply a %check testsuite usually accesses different files in a different environment than an installed testsuite would. Apart of this, there are test-cases, which can not be/can not be easily executed inside of a mock-environment as part of building. Ralf -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On 27/04/12 13:57, Michael Schwendt wrote: > A wrong approach? > > Why do you insist on using the %check section for that? It's a build-time > feature, found only in the spec file and not packaged in the built rpms > (also due to the test data I've referred to above). > I'm asking if the scripts from check-section are useful here. I understand, those scripts and the corresponding test data are not included in built RPMS. This was why I asked, how to access them. > You would be better served with a run-time test-suite. A collection > of tests that would be included in a built package, could be installed > and run independently, unrelated to the src.rpm build process. Fedora's > AutoQA project sounds like the place where to look for triggers that can > be used to run tests depending on new build results. > I wonder how different a run-time test-suite dffers from a test suite to be executed during build. Thank you for sharing your thoughts with me. -- Matthias Runge -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On Fri, 27 Apr 2012 13:04:56 +0200, MR (Matthias) wrote: > On 27/04/12 12:37, Michael Schwendt wrote: > > > Hardly any %check section uses installed files. Typically, files in the > > buildroot are used, or files plus test data in the builddir. Test data > > won't be available. > > > We encourage our packagers to implement useful check-sections. Which is a recommendation mostly because of existing "make check" or "make test" targets. Additionally, some spec files run custom tests not available in the upstream source tarball (e.g. automation of basic file conversion tests). > To make an example, I'm packaging the python-django framework. I'd like > get python-django's check-section get executed (using a django > installation) when python is updated. Or to get some django-requiring > packages get checked, when django is updated. I'd like to catch not only > API/ABI bumps, but also changed/broken behaviour, produced somewhere else. > > Most of required description is already there, so it can't be to hard, > to execute those tests from check-section. A wrong approach? Why do you insist on using the %check section for that? It's a build-time feature, found only in the spec file and not packaged in the built rpms (also due to the test data I've referred to above). You would be better served with a run-time test-suite. A collection of tests that would be included in a built package, could be installed and run independently, unrelated to the src.rpm build process. Fedora's AutoQA project sounds like the place where to look for triggers that can be used to run tests depending on new build results. -- Fedora release 17 (Beefy Miracle) - Linux 3.3.2-8.fc17.x86_64 loadavg: 0.00 0.01 0.05 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On 27/04/12 12:37, Michael Schwendt wrote: > Hardly any %check section uses installed files. Typically, files in the > buildroot are used, or files plus test data in the builddir. Test data > won't be available. > We encourage our packagers to implement useful check-sections. To make an example, I'm packaging the python-django framework. I'd like get python-django's check-section get executed (using a django installation) when python is updated. Or to get some django-requiring packages get checked, when django is updated. I'd like to catch not only API/ABI bumps, but also changed/broken behaviour, produced somewhere else. Most of required description is already there, so it can't be to hard, to execute those tests from check-section. -- Matthias Runge -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of packages
On Fri, 27 Apr 2012 12:10:11 +0200, MR (Matthias) wrote: > Hi, > > just a half-baked idea, I'm carrying some time with me around. > > Some packages have a check-section being executed during build. Would it > make sense to execute that test, when required packages of that package > get updated (to see, if the update breaks my package)? > > (Or other way around: when submitting an update run checks of dependent > packages) That depends on what tests are performed, how much a test-suite relies on external interfaces, and what unexpected ABI/API/CLI breakage you hope to catch that way. I'd say, every test may be helpful in finding breakage. At a minimum, if an inter-package dependency gets updated, one ought to ensure that a program still starts and isn't affected by dropped symbols, for instance. It may be more productive to skim over the changes in the component that changed and conclude whether it's supposed to be a compatible update or whether its changes ask for increased/longer run-time testing. > If yes, how to automate this? Is there a way to access the check-section > of a package from outside? Hardly any %check section uses installed files. Typically, files in the buildroot are used, or files plus test data in the builddir. Test data won't be available. -- Fedora release 17 (Beefy Miracle) - Linux 3.3.2-8.fc17.x86_64 loadavg: 0.06 0.05 0.05 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Testing of packages
Hi, just a half-baked idea, I'm carrying some time with me around. Some packages have a check-section being executed during build. Would it make sense to execute that test, when required packages of that package get updated (to see, if the update breaks my package)? (Or other way around: when submitting an update run checks of dependent packages) If yes, how to automate this? Is there a way to access the check-section of a package from outside? -- Matthias Runge -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On Fri, Apr 27, 2012 at 09:22:40AM +0200, Joachim Backes wrote: > > after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17), > rebooting hangs up. Pushing the reset button is needed :-( > > I had to downgrade systemd to get rid from this bug. > > No such problems with the previous version. Strange because I see the problem with systemd-44-6.fc17. If systemd is implicated it already appears with 44-6. Both restart and shutdown take about 1 to 2 minutes. Alexander -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] ABRT Test Day tomorrow - 2012-Apr-26
On 04/25/2012 11:55 AM, Michal Nowak wrote: Friends of ABRT, Quality Engineers, fellow testers - There's a Test Day going on tomorrow, Thursday 2012-Apr-26: https://fedoraproject.org/wiki/Test_Day:2012-04-26_ABRT_and_deduplication_service Looking at ABRT v2.0.10 (and related components) in Fedora 17 (see the feature page at https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication). As always, the event is in #fedora-test-day in Freenode IRC, and all the test instructions are on the Wiki. There will be a good turnout of developers, so it's a great chance to help shake out any remaining ABRT bugs for Fedora 17. Please help out if you have a chance! Thanks, Richard & Michal Test Day Summary Two participants attended. Twelve test cases modified and executed, only one of them - vmcore - we were not able to execute due to unknown kdump issue. Eight bugs created: Bug 816595 - Add accelerator to "I don't know what caused this proble... Bug 816607 - [abrt] libreport-gtk-2.0.10-2.fc17: report_tb_was_toggle... Bug 816617 - When "Show all problems" is enabled PolicyKit keeps aski... Bug 816628 - SystemError: could not open configuration file... Bug 816507 - QEMU locked in ioctl spin after guest crashed Bug 816634 - GNOME Shell utilizes 80 % of CPU in QEMU when in-progres... Bug 816230 - system-config-kdump: grubby error Bug 816186 - abrt-gui inotify_add_watch failed Overall ABRT in Fedora 17 looks good. Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On 04/27/2012 09:45 AM, Chuck Forsberg WA7KGX N2469R wrote: > Fedora 16 on omen.com tends to wedge on reboot. > The problem may be related to mounted NFS or CIFS shares. > Sorry, but I'm speaking about F17, not F16. Additionally, I'm not using NFS or CIFS. Kind regards Joachim Backes 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: reboot hangs with systemd-44-7.fc17
On 04/27/2012 03:45 PM, Chuck Forsberg WA7KGX N2469R wrote: > Fedora 16 on omen.com tends to wedge on reboot. > The problem may be related to mounted NFS or CIFS shares. Your issue is not related. The systems I'm testing are F17 with no NFS or CIFS shares and downgrading as suggested by Joachim does result in the problem clearing. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
Fedora 16 on omen.com tends to wedge on reboot. The problem may be related to mounted NFS or CIFS shares. On 04/27/2012 12:22 AM, Joachim Backes wrote: Dear all, after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17), rebooting hangs up. Pushing the reset button is needed :-( I had to downgrade systemd to get rid from this bug. No such problems with the previous version. Anybody sees this too? Kind regards Joachim Backes http://www.rhrk.uni-kl.de/~backes -- Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17: sudo reboot/shutdown -P now taking ~2 mins to shutdown
On 04/26/2012 05:14 AM, Pedro Francisco wrote: > $ sudo reboot > or > $ sudo shutdown -P now > > takes ~1/2 mins to shutdown; using "Restart" or "Shutdown" in GDM/Gnome > session > menu takes ~10 seconds. > > Any ideas why? > > F17, x86. > -- > Pedro > > You are probably seeing https://bugzilla.redhat.com/show_bug.cgi?id=816842 -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: reboot hangs with systemd-44-7.fc17
On 04/27/2012 03:22 PM, Joachim Backes wrote: > Dear all, > > after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17), rebooting > hangs > up. Pushing the reset button is needed :-( > > I had to downgrade systemd to get rid from this bug. > > No such problems with the previous version. > > Anybody sees this too? > > Well, it seems to be doing something and it does shutdown after about 2 minutes. I see the disk activity indicator on my VM blink. -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17: sudo reboot/shutdown -P now taking ~2 mins to shutdown
2012/4/26 Pedro Francisco > $ sudo reboot > or > $ sudo shutdown -P now > > takes ~1/2 mins to shutdown; using "Restart" or "Shutdown" in GDM/Gnome > session menu takes ~10 seconds. > > Any ideas why? > > F17, x86. > -- > Pedro > > same here. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
reboot hangs with systemd-44-7.fc17
Dear all, after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17), rebooting hangs up. Pushing the reset button is needed :-( I had to downgrade systemd to get rid from this bug. No such problems with the previous version. Anybody sees this too? Kind regards Joachim Backes 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
