RE: Who can close BZs?
> Date: Fri, 6 Dec 2013 15:58:41 + > From: johan...@gmail.com > To: test@lists.fedoraproject.org > Subject: Re: Who can close BZs? > > > On 12/06/2013 03:56 PM, Karel Volný wrote: > > > > Hi, > > > > Dne pátek, 6. prosince 2013 16:19:35 CEST, Clyde E. Kunkel napsal(a): > >> Is there a policy or other guidance on who is allowed to close > >> another persons bz? For example, can a person who is not a member of > >> the action developer or bugzappers group close a bz, especially a > >> non-trivial bz? > > > > well, anyone with the appropriate permissions (even some robots)? > > > > while a formal policy could be nice, I guess it is better not to > > complicate the rules ... anyone helping to clean the mess in bugzilla > > is welcome; if someone has a few spare cycles and notices something > > could be closed, why not to do it instead of the overloaded developer? > > > > - if you think that some bug has been closed improperly, let's talk > > about that concrete case and not about policies > > > > FYI I'm pretty sure RH bugzilla admin frown upon giving Fedora QA > community members those privileges... > > JBG As an aside, I had those priveleges for years before I started working at Red Hat. John. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On 06.12.2013 22:22, Adam Williamson wrote: > On Fri, 2013-12-06 at 13:14 -0800, Adam Williamson wrote: >> and engineers tend not to be fans of efficiency >> over unnecessary discussion. > > As you may have guessed, I trapped myself between two different drafts > of that clause :) Should read 'tend to be fans...', of course. > It's not a coincidence. poma I’m coming home I’m coming home tell the World I’m coming home -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New test case: SMB browsing
On Sex, 2013-12-06 at 18:01 -0800, Adam Williamson wrote: > On Sat, 2013-12-07 at 01:35 +, Sérgio Basto wrote: > > On Sex, 2013-12-06 at 15:41 -0800, Adam Williamson wrote: > > > Hi, folks. I've been doing some polish testing on F20 in the last few > > > days, and thought it'd make sense to write up my tests as test cases. > > > Here's the first: > > > > > > https://fedoraproject.org/wiki/QA:Testcase_desktop_network_smb > > > > wiki says: "Attempt to browse SMB shares on the local network with the > > desktop's normal method for doing so. For GNOME, open Files, click > > Browse Network under Network in the left-hand pane, and double-click > > Windows Network. For KDE, open Dolphin, click Network under Places in > > the left-hand pane, and expand or click on Samba Shares" > > > > I don't believe :) that you don't include in this test smb4k, I'm the > > maintainer of it . Can I include it ? smb4k (smb for kde) is much better > > browser, IMO, that kde network of dolphin and have more options etc. > > It's not about what's the best tool: it's a desktop polish test case. > The point is to answer the question 'does this fairly commonly used > function work right out of the box?' So testing with smb4k would be > outside the scope of this test. > > What would make sense would be to write a separate test for smb4k. Or, > heck, a whole set of test cases! We've been wanting to have more test > cases for more applications for a long time. But it wouldn't make sense > as a 'desktop validation' test unless smb4k comes installed out of the > box and Fedora users are all used to using that, not Dolphin, to browse > SMB shares. What you mean with "comes installed out of the box" ? , should be install , I not mean that is , as default in KDE-desktop, it is a great tool, you mean be default or yum install smb4k is enough ? > If you do write one or more test cases for smb4k, add this to the > bottom: > > [[Category:Package_smb4k_test_cases]] > > and then when you send out an update for the smb4k package, the test > cases will be listed in Bodhi as good tests to run to test the > update. :) Many thanks for this tips , I will read carefully and take action, but don't know when, I'm pretty busy > > > it's a test case for browsing SMB shares. Note that I'm fairly sure it's > > > currently broken if you have firewalld enabled, even if you allow the > > > 'samba-client' service; I have a bug reported at > > > https://bugzilla.redha.com/show_bug.cgi?id=1038959 where we're trying to > > > figure out why. > > > > I will try do the test case with the smb4k ... > > It's broken at a much lower level, it's something firewalld is doing > wrong I believe. With smb4k you can change the defaults, and choose other kind of authentications, for example I need an old authentication to access a NAS server with a old Samba (which can't change it). I will try debug it :) but perhaps just can do the tests Monday afternoon . Many thanks, -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: deja-dup
On Fri, Dec 6, 2013 at 6:04 PM, Adam Williamson wrote: > On Sat, 2013-12-07 at 12:45 +1100, Ankur Sinha wrote: > > On Fri, 2013-12-06 at 02:06 -0800, Adam Williamson wrote: > > > in the cases I recall seeing, that wasn't it. It just never showed. > > > > It'd be a bug then. Working here: > > http://ankursinha.fedorapeople.org/misc/dejadup-de-activities.png > > Like I said, it's transient. That's one reason I didn't report it yet: > hard to nail down. > > But now I'm looking out for it, I've seen it several times just today. > For me it always seems to be control-center applets, though. If I just > hit super and type 'user', sometimes, the 'Users' panel isn't shown in > the results. Typing extra letters doesn't help - so typing 's' to make > it 'users' doesn't make it show up - but deleting the 'r' so it's now > 'use' makes it show Displays, Mouse & Touchpad, and Online Accounts (but > not Users!), and then typing the r again - so we're back to 'user' - > makes Users show up (and the other three go away; they were matching on > the word "use", I guess). > > For me, after yum installing it because I thought that I had to after typing a search couldn't find it and now can, I found it hidden in utilities. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: deja-dup
On Sat, 2013-12-07 at 12:45 +1100, Ankur Sinha wrote: > On Fri, 2013-12-06 at 02:06 -0800, Adam Williamson wrote: > > in the cases I recall seeing, that wasn't it. It just never showed. > > It'd be a bug then. Working here: > http://ankursinha.fedorapeople.org/misc/dejadup-de-activities.png Like I said, it's transient. That's one reason I didn't report it yet: hard to nail down. But now I'm looking out for it, I've seen it several times just today. For me it always seems to be control-center applets, though. If I just hit super and type 'user', sometimes, the 'Users' panel isn't shown in the results. Typing extra letters doesn't help - so typing 's' to make it 'users' doesn't make it show up - but deleting the 'r' so it's now 'use' makes it show Displays, Mouse & Touchpad, and Online Accounts (but not Users!), and then typing the r again - so we're back to 'user' - makes Users show up (and the other three go away; they were matching on the word "use", I guess). Doesn't happen 100% of the time, though, and I can't find any useful debugging output in any logs when it does happen :/ -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New test case: SMB browsing
On Sat, 2013-12-07 at 01:35 +, Sérgio Basto wrote: > On Sex, 2013-12-06 at 15:41 -0800, Adam Williamson wrote: > > Hi, folks. I've been doing some polish testing on F20 in the last few > > days, and thought it'd make sense to write up my tests as test cases. > > Here's the first: > > > > https://fedoraproject.org/wiki/QA:Testcase_desktop_network_smb > > wiki says: "Attempt to browse SMB shares on the local network with the > desktop's normal method for doing so. For GNOME, open Files, click > Browse Network under Network in the left-hand pane, and double-click > Windows Network. For KDE, open Dolphin, click Network under Places in > the left-hand pane, and expand or click on Samba Shares" > > I don't believe :) that you don't include in this test smb4k, I'm the > maintainer of it . Can I include it ? smb4k (smb for kde) is much better > browser, IMO, that kde network of dolphin and have more options etc. It's not about what's the best tool: it's a desktop polish test case. The point is to answer the question 'does this fairly commonly used function work right out of the box?' So testing with smb4k would be outside the scope of this test. What would make sense would be to write a separate test for smb4k. Or, heck, a whole set of test cases! We've been wanting to have more test cases for more applications for a long time. But it wouldn't make sense as a 'desktop validation' test unless smb4k comes installed out of the box and Fedora users are all used to using that, not Dolphin, to browse SMB shares. If you do write one or more test cases for smb4k, add this to the bottom: [[Category:Package_smb4k_test_cases]] and then when you send out an update for the smb4k package, the test cases will be listed in Bodhi as good tests to run to test the update. :) > > it's a test case for browsing SMB shares. Note that I'm fairly sure it's > > currently broken if you have firewalld enabled, even if you allow the > > 'samba-client' service; I have a bug reported at > > https://bugzilla.redha.com/show_bug.cgi?id=1038959 where we're trying to > > figure out why. > > I will try do the test case with the smb4k ... It's broken at a much lower level, it's something firewalld is doing wrong I believe. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: deja-dup
On Fri, 2013-12-06 at 02:06 -0800, Adam Williamson wrote: > in the cases I recall seeing, that wasn't it. It just never showed. It'd be a bug then. Working here: http://ankursinha.fedorapeople.org/misc/dejadup-de-activities.png -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG 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 test case: SMB browsing
On Sex, 2013-12-06 at 15:41 -0800, Adam Williamson wrote: > Hi, folks. I've been doing some polish testing on F20 in the last few > days, and thought it'd make sense to write up my tests as test cases. > Here's the first: > > https://fedoraproject.org/wiki/QA:Testcase_desktop_network_smb wiki says: "Attempt to browse SMB shares on the local network with the desktop's normal method for doing so. For GNOME, open Files, click Browse Network under Network in the left-hand pane, and double-click Windows Network. For KDE, open Dolphin, click Network under Places in the left-hand pane, and expand or click on Samba Shares" I don't believe :) that you don't include in this test smb4k, I'm the maintainer of it . Can I include it ? smb4k (smb for kde) is much better browser, IMO, that kde network of dolphin and have more options etc. > it's a test case for browsing SMB shares. Note that I'm fairly sure it's > currently broken if you have firewalld enabled, even if you allow the > 'samba-client' service; I have a bug reported at > https://bugzilla.redha.com/show_bug.cgi?id=1038959 where we're trying to > figure out why. I will try do the test case with the smb4k ... > For now the test case is just sitting in the wiki, but for F21 I'm > thinking of proposing adding a set of 'optional' desktop test cases, > like we have 'optional' install test cases - ones that it is good to run > and check, but we don't block the release on at any milestone. This > would be one of them. Another I'm planning to write is 'set up a printer > and print a test page' - I'm thinking along those kinds of lines. There > are probably other kinds of network browsing we can cover too. > > Thoughts, queries, corrections, improvements etc? Thanks! > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New test case: SMB browsing
On Dec 6, 2013, at 4:41 PM, Adam Williamson wrote: > > For now the test case is just sitting in the wiki, but for F21 I'm > thinking of proposing adding a set of 'optional' desktop test cases, > like we have 'optional' install test cases It's a good idea. For what it's worth, Apple has promoted SMB as the default protocol for file sharing on OS X 10.9 released in October. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
New test case: SMB browsing
Hi, folks. I've been doing some polish testing on F20 in the last few days, and thought it'd make sense to write up my tests as test cases. Here's the first: https://fedoraproject.org/wiki/QA:Testcase_desktop_network_smb it's a test case for browsing SMB shares. Note that I'm fairly sure it's currently broken if you have firewalld enabled, even if you allow the 'samba-client' service; I have a bug reported at https://bugzilla.redha.com/show_bug.cgi?id=1038959 where we're trying to figure out why. For now the test case is just sitting in the wiki, but for F21 I'm thinking of proposing adding a set of 'optional' desktop test cases, like we have 'optional' install test cases - ones that it is good to run and check, but we don't block the release on at any milestone. This would be one of them. Another I'm planning to write is 'set up a printer and print a test page' - I'm thinking along those kinds of lines. There are probably other kinds of network browsing we can cover too. Thoughts, queries, corrections, improvements etc? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nvidia driver choices
On 12/07/13 07:04, Lawrence E Graves wrote: > > On 12/06/2013 01:54 PM, Adam Jackson wrote: >> On Fri, 2013-12-06 at 12:53 -0800, Adam Williamson wrote: >>> On Fri, 2013-12-06 at 13:10 -0700, Lawrence E Graves wrote: I don't mean to be a pain in the ---, but there is only one choice of nvidia drivers which are 304.116. Who do I report this problem to? >>> Given that you don't provide any information on where it is you're >>> making this choice, we can't possibly tell you... >> More strongly, telling us who you're getting them from would also tell >> you who to report it to. >> >> - ajax >> >> > I thought the rpmfusion is where all the nvidia drivers come from. > It is probably the most common place. But you could also download and install directly from nVidia. But, since you have indicated you're talking about rpmfusion, they have their own mailing lists and bugzilla system for reporting problems and asking for help. -- Getting tired of non-Fedora discussions and self-serving posts -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Re: Nvidia driver choices
On 12/06/2013 01:54 PM, Adam Jackson wrote: On Fri, 2013-12-06 at 12:53 -0800, Adam Williamson wrote: On Fri, 2013-12-06 at 13:10 -0700, Lawrence E Graves wrote: I don't mean to be a pain in the ---, but there is only one choice of nvidia drivers which are 304.116. Who do I report this problem to? Given that you don't provide any information on where it is you're making this choice, we can't possibly tell you... More strongly, telling us who you're getting them from would also tell you who to report it to. - ajax I thought the rpmfusion is where all the nvidia drivers come from. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: springframework - there is no package for F20
On 06.12.2013 04:48, Orion Poplawski wrote: > On 12/05/2013 05:49 PM, Ankur Sinha wrote: >> On Thu, 2013-12-05 at 16:05 +0100, Mateusz Marzantowicz wrote: >>> Are there any chances to have this packages [1] for Fedora 20? I know >>> it's only about release number but I don't feel comfortable with >>> packages not targeted at my current system release. >>> >>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1035257 >>> >> >> Hi Mateusz, >> >> The package failed to build from source (FTBFS) during the mass >> rebuild[1], and therefore isn't available in the F20+ repositories. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=993376 >> >> The maintainer should've fixed this up, but hasn't done it yet. You'll >> have to wait until he does. You can help the maintainer out by >> co-maintaining the package. It's one of the ways you get sponsored as a >> fedora packager if you aren't one already: >> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer >> >> > > I've made a first attempt to fix, but it still doesn't build. This one > will need a committed maintainer I think. > > Thanks, for quick bug fix action. I'll test tomorrow if everything works after upgrading to fc20 package. It looks like there is another package related to Java named snappy-java that FTBFS [1]. I'm not posting it as new thread because it is very similar to springframework issue. I'm not using this packages directly, they are pulled as dependencies when installing FreeIPA server. [1] https://bugzilla.redhat.com/show_bug.cgi?id=993357 Mateusz Marzantowicz -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On Fri, 2013-12-06 at 13:14 -0800, Adam Williamson wrote: > and engineers tend not to be fans of efficiency > over unnecessary discussion. As you may have guessed, I trapped myself between two different drafts of that clause :) Should read 'tend to be fans...', of course. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On Fri, 2013-12-06 at 16:03 -0500, Clyde E. Kunkel wrote: > On 12/06/2013 03:34 PM, Adam Williamson wrote: > > On Fri, 2013-12-06 at 15:28 -0500, Clyde E. Kunkel wrote: > > > >> All of the above is fine. However, your are exhibiting profound > >> arrogance in stepping in for real fedora managers/developers. Do your > >> RFEs and your own bzs, but, leave other peoples bz reports alone. > > > > You are assuming a policy that does not exist. I don't believe there is > > any rule or policy which Chris' closure of your bug violated. > > > > As someone said upthread, Fedora is intentionally not hedged around with > > *too* many hard and fast rules. There are various statuses in FAS which > > translate into 'editbugs' privileges - which allow you to close others' > > bugs - and it's generally not considered a problem for people with > > editbugs privileges to do something like this. > > > > If Chris' change had actually been completely wrong, that might have > > been a problem, and the appropriate thing to do would be to reverse it, > > and then keep an eye out to make sure he wasn't repeatedly doing silly > > things, or just trolling, or something. At the point where someone > > exhibits a pattern of bad behaviour, then is the time when we get > > together as a group and say 'hmm, maybe something should be done about > > this'. But no, there is no rule that says 'Chris can't close a bug Clyde > > filed against anaconda'. > > > > It is ungentlemanly This seems an entirely irrelevant consideration, this is not a gentlemen's club. > and discourteous. What is wrong with a > person-to-person discourse first. Bug trackers are not forums. They are tools for tracking bugs. This bug was correctly tracked. 'Discourse' is not required. > There are no rules for that either, > just well-accepted social norms. In my experience, the norm with bugtrackers is just what Chris did. We try to make Fedora a welcoming environment, but it is also an engineering project, and engineers tend not to be fans of efficiency over unnecessary discussion. As I keep saying: you would get much more traction with your complaint if Chris' decision had been _wrong_. Since it's correct, I'm not sure anyone's going to see much of a problem with it. Correctness is highly valued in collaborative development communities like Fedora. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On 12/06/2013 03:34 PM, Adam Williamson wrote: On Fri, 2013-12-06 at 15:28 -0500, Clyde E. Kunkel wrote: All of the above is fine. However, your are exhibiting profound arrogance in stepping in for real fedora managers/developers. Do your RFEs and your own bzs, but, leave other peoples bz reports alone. You are assuming a policy that does not exist. I don't believe there is any rule or policy which Chris' closure of your bug violated. As someone said upthread, Fedora is intentionally not hedged around with *too* many hard and fast rules. There are various statuses in FAS which translate into 'editbugs' privileges - which allow you to close others' bugs - and it's generally not considered a problem for people with editbugs privileges to do something like this. If Chris' change had actually been completely wrong, that might have been a problem, and the appropriate thing to do would be to reverse it, and then keep an eye out to make sure he wasn't repeatedly doing silly things, or just trolling, or something. At the point where someone exhibits a pattern of bad behaviour, then is the time when we get together as a group and say 'hmm, maybe something should be done about this'. But no, there is no rule that says 'Chris can't close a bug Clyde filed against anaconda'. It is ungentlemanly and discourteous. What is wrong with a person-to-person discourse first. There are no rules for that either, just well-accepted social norms. -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nvidia driver choices
On Fri, 2013-12-06 at 12:53 -0800, Adam Williamson wrote: > On Fri, 2013-12-06 at 13:10 -0700, Lawrence E Graves wrote: > > I don't mean to be a pain in the ---, but there is only one choice of > > nvidia drivers which are 304.116. Who do I report this problem to? > > Given that you don't provide any information on where it is you're > making this choice, we can't possibly tell you... More strongly, telling us who you're getting them from would also tell you who to report it to. - ajax -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nvidia driver choices
On Fri, 2013-12-06 at 13:10 -0700, Lawrence E Graves wrote: > I don't mean to be a pain in the ---, but there is only one choice of > nvidia drivers which are 304.116. Who do I report this problem to? Given that you don't provide any information on where it is you're making this choice, we can't possibly tell you... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Updates in Fedora 20 TC5
On Fri, 2013-12-06 at 13:12 -0700, Lawrence E Graves wrote: > Thank you for the answer to this problem. > On 12/06/2013 01:02 PM, Lawrence E Graves wrote: > > Package systemd-libs-208-9 is not signed is the error message I am > > receiving in Fedora 20 TC5 install. The package really isn't signed. It'll be fixed in tomorrow's repo. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On Fri, 2013-12-06 at 15:28 -0500, Clyde E. Kunkel wrote: > All of the above is fine. However, your are exhibiting profound > arrogance in stepping in for real fedora managers/developers. Do your > RFEs and your own bzs, but, leave other peoples bz reports alone. You are assuming a policy that does not exist. I don't believe there is any rule or policy which Chris' closure of your bug violated. As someone said upthread, Fedora is intentionally not hedged around with *too* many hard and fast rules. There are various statuses in FAS which translate into 'editbugs' privileges - which allow you to close others' bugs - and it's generally not considered a problem for people with editbugs privileges to do something like this. If Chris' change had actually been completely wrong, that might have been a problem, and the appropriate thing to do would be to reverse it, and then keep an eye out to make sure he wasn't repeatedly doing silly things, or just trolling, or something. At the point where someone exhibits a pattern of bad behaviour, then is the time when we get together as a group and say 'hmm, maybe something should be done about this'. But no, there is no rule that says 'Chris can't close a bug Clyde filed against anaconda'. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: how to fix updates in fedora 20? yum problem
> -Original Message- > From: nonamed...@gmail.com > Sent: Fri, 06 Dec 2013 14:24:18 -0600 > To: test@lists.fedoraproject.org > Subject: Re: how to fix updates in fedora 20? yum problem > > On 12/06/2013 02:17 PM, Antonio Olivares wrote: >> Dear all, >> >> I believe this has been reported, but where is the workaround for this: >> > >> > http://mirror.cpsc.ucalgary.ca/mirror/fedora/linux/updates/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates http://fedora.bhs.mirrors.ovh.net/linux/updates/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates >> http://mirrors.ucr.ac.cr/fedora/updates/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates >> [root@localhost ~]# >> >> I have two machines running beta and tc5 using installation cd which >> gets latest packages. >> >> >> Best Regards, >> >> >> Antonio >> >> >> FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on >> your desktop! >> Check it out at http://www.inbox.com/marineaquarium >> >> > > Bugzilla is here - https://bugzilla.redhat.com/show_bug.cgi?id=1039052 > > Fix is here - > https://admin.fedoraproject.org/updates/FEDORA-2013-22841/yum-3.4.3-120.fc20 > > Hope that helps! > -- That did the trick! Thank you very much! I got the file from here: http://koji.fedoraproject.org/koji/buildinfo?buildID=483265 Best Regards, Antonio FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No updates in Fedora TC5
On Fri, 06 Dec 2013 09:39:26 -0700 Lawrence E Graves wrote: > I have just downloaded Fedora TC5 and the install went fine until I > done yum -y update and got the message there are no updates. Please > advise. Thats completely normal at this point. updates-testing is disabled by default. The only updates you will see show up are things that fix accepted blocker or freeze exceptions that have been pushed stable. At this point there's very few of those going out. The next flood of updates you will see is once we have a go on final release, the updates repo will be populated and all the stuff waiting for stable now that was not a blocker or fe will go into the updates repo. Or if you re-enable the updates-testing repo you will see more updates flowing. kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On 12/06/2013 03:07 PM, Chris Murphy wrote: On Dec 6, 2013, at 10:31 AM, Clyde E. Kunkel wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1038885 Closed the first time because it's not an F20 bug. As mentioned in bug 864198 it's intended behavior. Also closed because the summary about it not installing the boot loader on btrfs doesn't make sense because that's not the problem nor how it would work if it did work, and the description has nothing to do with the actual problem or getting it fixed. I'd always intended to create a clearly described and explicit rawhide RFE tracking bug for the issue, and it was impossible to clean up and change your bug into that without requiring the reader to read 7 comments that have nothing to do with actually progressing the real problems. So that's why I closed it a 2nd time, after creating the tracker bug, for which there will eventually be other bugs it depends on, not just the grubby bug. There are issues with grub2 and os-prober that also need to be addressed for certain use cases. The rationale for the change is thoroughly discussed in several blocker reviews. It's not some arbitrary change, it was made based on several release criteria being violated. Yes it would have been better to fix that old grubby bug that was also an F20 blocker for a month. But it's worse to throw razor blades at hapless users, excusing it with the suggestion they don't really matter when those with secret decoder ring hacks to work around the problem can easily do so. You can still use kickstart to make the layout as you wish. The real issue is that grub-mkconfig isn't confused about /boot being located on btrfs subvolumes. Why? It seems a possible answer for grubby's confusion is located in grub. Chris Murphy All of the above is fine. However, your are exhibiting profound arrogance in stepping in for real fedora managers/developers. Do your RFEs and your own bzs, but, leave other peoples bz reports alone. -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No updates in Fedora TC5
On Fri, Dec 06, 2013 at 16:45:11 +, Sérgio Basto wrote: TOP POSTING TC5 is before alfa , you mean Fedora final candidate RC5 ? or what ever ? when is not specific means that you are talking about pre alfa composes. please be more specific . Thanks, No he means final TC5. We haven't started doing final RCs yet because there are open blocker bugs. There are TCs and RCs for each of alpha, beta and final. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: how to fix updates in fedora 20? yum problem
On 12/06/2013 02:17 PM, Antonio Olivares wrote: Dear all, I believe this has been reported, but where is the workaround for this: http://mirror.cpsc.ucalgary.ca/mirror/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://fedora.bhs.mirrors.ovh.net/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.ucr.ac.cr/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates [root@localhost ~]# I have two machines running beta and tc5 using installation cd which gets latest packages. Best Regards, Antonio FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium Bugzilla is here - https://bugzilla.redhat.com/show_bug.cgi?id=1039052 Fix is here - https://admin.fedoraproject.org/updates/FEDORA-2013-22841/yum-3.4.3-120.fc20 Hope that helps! -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
how to fix updates in fedora 20? yum problem
Dear all, I believe this has been reported, but where is the workaround for this: One of the configured repositories failed (Fedora 20 - x86_64 - Updates), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable updates 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=updates.skip_if_unavailable=true failure: repodata/repomd.xml from updates: [Errno 256] No more mirrors to try. http://mirrors.kernel.org/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.rit.edu/fedora/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.pnl.gov/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://fedora.osuosl.org/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates ftp://ftp.osuosl.org/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://ftp.ussg.iu.edu/linux/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.web-ster.com/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.usc.edu/pub/linux/distributions/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://linux.mirrors.es.net/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.cc.vt.edu/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.mit.edu/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.ptd.net/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.anl.gov/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://archive.linux.duke.edu/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.umd.edu/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.metrocast.net/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.tummy.com/pub/fedora.redhat.com/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates ftp://mirror.cs.princeton.edu/pub/mirrors/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirrors.servercentral.net/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.fdcservers.net/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://ftp.linux.ncsu.edu/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.cogentco.com/pub/linux/fedora/linux/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.itc.virginia.edu/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://mirror.nexcess.net/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates http://fedora.mirror.lstn.net/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates ftp://mirror.lstn.net/fedora/updates/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match
Re: Updates in Fedora 20 TC5
Thank you for the answer to this problem. On 12/06/2013 01:02 PM, Lawrence E Graves wrote: Package systemd-libs-208-9 is not signed is the error message I am receiving in Fedora 20 TC5 install. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Nvidia driver choices
I don't mean to be a pain in the ---, but there is only one choice of nvidia drivers which are 304.116. Who do I report this problem to? -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On Dec 6, 2013, at 10:31 AM, Clyde E. Kunkel wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=1038885 Closed the first time because it's not an F20 bug. As mentioned in bug 864198 it's intended behavior. Also closed because the summary about it not installing the boot loader on btrfs doesn't make sense because that's not the problem nor how it would work if it did work, and the description has nothing to do with the actual problem or getting it fixed. I'd always intended to create a clearly described and explicit rawhide RFE tracking bug for the issue, and it was impossible to clean up and change your bug into that without requiring the reader to read 7 comments that have nothing to do with actually progressing the real problems. So that's why I closed it a 2nd time, after creating the tracker bug, for which there will eventually be other bugs it depends on, not just the grubby bug. There are issues with grub2 and os-prober that also need to be addressed for certain use cases. The rationale for the change is thoroughly discussed in several blocker reviews. It's not some arbitrary change, it was made based on several release criteria being violated. Yes it would have been better to fix that old grubby bug that was also an F20 blocker for a month. But it's worse to throw razor blades at hapless users, excusing it with the suggestion they don't really matter when those with secret decoder ring hacks to work around the problem can easily do so. You can still use kickstart to make the layout as you wish. The real issue is that grub-mkconfig isn't confused about /boot being located on btrfs subvolumes. Why? It seems a possible answer for grubby's confusion is located in grub. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Updates in Fedora 20 TC5
Package systemd-libs-208-9 is not signed is the error message I am receiving in Fedora 20 TC5 install. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On 06.12.2013 19:37, Simon G. wrote: > See https://bugzilla.redhat.com/show_bug.cgi?id=1039052 > and > https://admin.fedoraproject.org/updates/yum-3.4.3-120.fc20?_csrf_token=88c0eb78b5fd4d9eb03e957cc9042ad6c25c3f7c I simply can not accept that something like yum can be broken! And please do not top-post, my mind hurt! poma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
See https://bugzilla.redhat.com/show_bug.cgi?id=1039052 and https://admin.fedoraproject.org/updates/yum-3.4.3-120.fc20?_csrf_token=88c0eb78b5fd4d9eb03e957cc9042ad6c25c3f7c 2013/12/6 poma : > On 06.12.2013 12:12, Chuck Forsberg WA7KGX wrote: >> I installed quite a number of packages with the >> yum that came with TC5. Plenty of complaints >> about mirrors but eventually everything asked for >> was installed. Seems like reasonable behavior >> when the mirrors aren't widely populated. > > Exactly. > It seems to me that this is mentioned mass times, but it happens that > people forget the simplest things. > So it's good that someone is always yelling so that all of us don't fall > asleep. > Haha > > > poma > > > -- > 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: Who can close BZs?
On 06.12.2013 18:31, Clyde E. Kunkel wrote: > On 12/06/2013 10:56 AM, Karel Volný wrote: >> >> Hi, >> >> Dne pátek, 6. prosince 2013 16:19:35 CEST, Clyde E. Kunkel napsal(a): >>> Is there a policy or other guidance on who is allowed to close another >>> persons bz? For example, can a person who is not a member of the >>> action developer or bugzappers group close a bz, especially a >>> non-trivial bz? >> >> well, anyone with the appropriate permissions (even some robots)? >> >> while a formal policy could be nice, I guess it is better not to >> complicate the rules ... anyone helping to clean the mess in bugzilla is >> welcome; if someone has a few spare cycles and notices something could >> be closed, why not to do it instead of the overloaded developer? >> >> - if you think that some bug has been closed improperly, let's talk >> about that concrete case and not about policies >> >> K. >> > > https://bugzilla.redhat.com/show_bug.cgi?id=1038885 Throughout "history" you can see who did what, https://bugzilla.redhat.com/show_activity.cgi?id=1038885 It seems that an "expert" closed report to open the same as that. Hah poma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On 12/06/2013 10:56 AM, Karel Volný wrote: Hi, Dne pátek, 6. prosince 2013 16:19:35 CEST, Clyde E. Kunkel napsal(a): Is there a policy or other guidance on who is allowed to close another persons bz? For example, can a person who is not a member of the action developer or bugzappers group close a bz, especially a non-trivial bz? well, anyone with the appropriate permissions (even some robots)? while a formal policy could be nice, I guess it is better not to complicate the rules ... anyone helping to clean the mess in bugzilla is welcome; if someone has a few spare cycles and notices something could be closed, why not to do it instead of the overloaded developer? - if you think that some bug has been closed improperly, let's talk about that concrete case and not about policies K. https://bugzilla.redhat.com/show_bug.cgi?id=1038885 -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
systemd-208-9.fc20 package in f20 unsigned
Greetings. systemd-208-9.fc20 was pushed into the base fedora 20 repos last night (as it fixed a blocker bug for the upcoming release). However, it was not signed properly, so Fedora 20 prerelease users will see an error about the package not being signed. This has already been corrected and the signed package will be in tomorrow's branched compose. Please wait for that compose to update, or if you need to test that the blocker is fixed, you can use --nogpgcheck to upgrade to the new package. Thanks, kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Update problems
Tried updating Fedora 20 TC5 and this is the results: Package systemd-208-9.fc20.x86_64.rpm is not signed -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: No updates in Fedora TC5
TOP POSTING TC5 is before alfa , you mean Fedora final candidate RC5 ? or what ever ? when is not specific means that you are talking about pre alfa composes. please be more specific . Thanks, On Sex, 2013-12-06 at 09:39 -0700, Lawrence E Graves wrote: > I have just downloaded Fedora TC5 and the install went fine until I done > yum -y update and got the message there are no updates. Please advise. > > -- > All things are workable but don't all things work. > Prov. 3:5 & 6 > -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
No updates in Fedora TC5
I have just downloaded Fedora TC5 and the install went fine until I done yum -y update and got the message there are no updates. Please advise. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
On 12/06/2013 03:56 PM, Karel Volný wrote: Hi, Dne pátek, 6. prosince 2013 16:19:35 CEST, Clyde E. Kunkel napsal(a): Is there a policy or other guidance on who is allowed to close another persons bz? For example, can a person who is not a member of the action developer or bugzappers group close a bz, especially a non-trivial bz? well, anyone with the appropriate permissions (even some robots)? while a formal policy could be nice, I guess it is better not to complicate the rules ... anyone helping to clean the mess in bugzilla is welcome; if someone has a few spare cycles and notices something could be closed, why not to do it instead of the overloaded developer? - if you think that some bug has been closed improperly, let's talk about that concrete case and not about policies FYI I'm pretty sure RH bugzilla admin frown upon giving Fedora QA community members those privileges... JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20 KDE popups (SOLVED)
On Fri, 2013-12-06 at 02:36 -0600, Mike Chambers wrote: > It seems I am getting a popup msg (in the top middle of the msg it has > the topic "Local system message service) with various warnings/msgs from > my log(s),and the popups appear in the top/middle of my screen, one on > top of the other. And you have to click on them to get rid of them. > > How the heck do you turn that off? It is very annoying to say the > least. Founded out how to turn it off.. System Settings/Application and System Notifications -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Who can close BZs?
Hi, Dne pátek, 6. prosince 2013 16:19:35 CEST, Clyde E. Kunkel napsal(a): Is there a policy or other guidance on who is allowed to close another persons bz? For example, can a person who is not a member of the action developer or bugzappers group close a bz, especially a non-trivial bz? well, anyone with the appropriate permissions (even some robots)? while a formal policy could be nice, I guess it is better not to complicate the rules ... anyone helping to clean the mess in bugzilla is welcome; if someone has a few spare cycles and notices something could be closed, why not to do it instead of the overloaded developer? - if you think that some bug has been closed improperly, let's talk about that concrete case and not about policies K. -- Karel Volný QE BaseOs/Daemons Team Red Hat Czech, Brno tel. +420 532294274 (RH: +420 532294111 ext 8262074) xmpp ka...@jabber.cz :: "Never attribute to malice what can :: easily be explained by stupidity." -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Who can close BZs?
Is there a policy or other guidance on who is allowed to close another persons bz? For example, can a person who is not a member of the action developer or bugzappers group close a bz, especially a non-trivial bz? TIA -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On 06.12.2013 12:12, Chuck Forsberg WA7KGX wrote: > I installed quite a number of packages with the > yum that came with TC5. Plenty of complaints > about mirrors but eventually everything asked for > was installed. Seems like reasonable behavior > when the mirrors aren't widely populated. Exactly. It seems to me that this is mentioned mass times, but it happens that people forget the simplest things. So it's good that someone is always yelling so that all of us don't fall asleep. Haha poma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-20 Branched report: 20131206 changes
Compose started at Fri Dec 6 07:15:02 UTC 2013 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [ghc-hjsmin] ghc-hjsmin-devel-0.1.4.3-2.fc20.armv7hl requires ghc-devel(language-javascript-0.5.8-28fa88554adf134b03284de53334e91d) [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) >= 0:0.16.0 [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc >= 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [owncloud] owncloud-5.0.13-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [php-Assetic] php-Assetic-1.1.2-1.fc20.noarch requires php-pear(pear.symfony.com/Process) < 0:3.0 php-Assetic-1.1.2-1.fc20.noarch requires php-pear(pear.symfony.com/Process) >= 0:2.1 [php-Metadata] php-Metadata-1.5.0-1.fc20.noarch requires php-pear(pear.symfony.com/DependencyInjection) [php-SymfonyCmfRouting] php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) < 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) >= 0:2.2 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/HttpKernel) < 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/HttpKernel) >= 0:2.2 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) < 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) >= 0:2.2 [php-doctrine-DoctrineDBAL] php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires php-pear(pear.symfony.com/Console) < 0:3.0 php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires php-pear(pear.symfony.com/Console) >= 0:2.0 [php-doctrine-DoctrineORM] php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Yaml) < 0:3.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Yaml) >= 0:2.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Console) < 0:3.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Console) >= 0:2.0 [php-guzzle-Guzzle] php-guzzle-Guzzle-3.7.4-2.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) >= 0:2.1.0 [php-phpunit-DbUnit] php-phpunit-DbUnit-1.3.0-1.fc20.noarch require
Re: F20: Updates-testing mirrors inoperable?
On Fri, 06 Dec 2013 10:41:30 +0100 Joachim Backes wrote: > Hi all, > > anybody sees this too if including the updates-testing repo to "yum > update": > > Happened with me but still updated. -- Regards, Frank www.frankly3d.com -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
I installed quite a number of packages with the yum that came with TC5. Plenty of complaints about mirrors but eventually everything asked for was installed. Seems like reasonable behavior when the mirrors aren't widely populated. -- Chuck Forsberg WA7KGX 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: Fedora 20 Final blocker - Please add symfony packages.
Le 28/11/2013 03:25, Adam Williamson a écrit : > Hi, folks. We have just over one week to the Fedora 20 Go/No-Go meeting, > and a big happy pile of blocker bugs - everyone's having fun! In order > to be able to complete testing in time for the go/no-go meeting Please consider for F20Final: https://bugzilla.redhat.com/show_bug.cgi?id=1021749 https://admin.fedoraproject.org/updates/FEDORA-2013-22356 Having a broken PHPUnit in F20 will make most of the PHP packages FTBFS. Note: retiring a package before the new one is pushed is just a VERY bad idea (despite comment#34 on bz) Remi. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On 12/06/2013 11:18 AM, Dan Horák wrote: > On Fri, 06 Dec 2013 02:12:48 -0800 > Adam Williamson wrote: > >> On Fri, 2013-12-06 at 11:10 +0100, Dan Horák wrote: >> Hi Igor, thank you, did help :-) >>> >>> are you sure this is a problem in yum itself and not in the mirror >>> infrastructure? >> >> If downgrading yum helps, then it does rather suggest yum's involved >> in the problem. > > there was both a yum downgrade and "yum clean all" done, it's not clear > what step fixes the problem Dan, First I did "yum clean all", but that did not help !! Joachim Backes > > > Dan > -- Fedora release 20 (Heisenbug) Kernel-3.11.10-301.fc20.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On Fri, 06 Dec 2013 02:12:48 -0800 Adam Williamson wrote: > On Fri, 2013-12-06 at 11:10 +0100, Dan Horák wrote: > > > > Hi Igor, > > > > > > thank you, did help :-) > > > > are you sure this is a problem in yum itself and not in the mirror > > infrastructure? > > If downgrading yum helps, then it does rather suggest yum's involved > in the problem. there was both a yum downgrade and "yum clean all" done, it's not clear what step fixes the problem Dan -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On Fri, 2013-12-06 at 11:10 +0100, Dan Horák wrote: > > Hi Igor, > > > > thank you, did help :-) > > are you sure this is a problem in yum itself and not in the mirror > infrastructure? If downgrading yum helps, then it does rather suggest yum's involved in the problem. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On Fri, 06 Dec 2013 10:53:09 +0100 Joachim Backes wrote: > On 12/06/2013 10:45 AM, Igor Gnatenko wrote: > > On Fri, 2013-12-06 at 10:41 +0100, Joachim Backes wrote: > >> Hi all, > >> > >> anybody sees this too if including the updates-testing repo to > >> "yum update": > >> > >> sudo yum update --enablerepo=updates-testing > >> Loaded plugins: langpacks > >> updates-testing/20/x86_64/metalink | 27 kB > >> 00:00 > >> updates-testing | 4.6 kB > >> 00:00 > >> http://ftp-stud.hs-esslingen.de/pub/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://mirrors.n-ix.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://mirror1.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://mirror2.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://mirror.fraunhofer.de/dl.fedoraproject.org/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://ftp.byfly.by/pub/fedoraproject.org/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://mirror.1000mbps.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://sunsite.mff.cuni.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> updates-testing | 4.6 kB > >> 00:00 > >> http://ultra.linux.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: > >> [Errno -1] repomd.xml does not match metalink for updates-testing > >> Trying other mirror. > >> > >> .. And so on. > >> > >> Kind regards > >> > >> Joachim Backes > >> > >> -- > >> > >> Fedora release 20 (Heisenbug) > >> Kernel-3.11.10-301.fc20.x86_64 > >> > >> Joachim Backes > >> https://www-user.rhrk.uni-kl.de/~backes > > > > Confirm! You can fix this by: > > # yum --disablerepo=updates,updates-testing downgrade yum > > # yum clean all > > # yum makecache > > > > and sure -1 karma in [0]bodhi > > > > [0]https://admin.fedoraproject.org/updates/FEDORA-2013-22706/yum-3.4.3-119.fc20 > > > > Hi Igor, > > thank you, did help :-) are you sure this is a problem in yum itself and not in the mirror infrastructure? Dan -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: deja-dup
On Fri, 2013-12-06 at 18:37 +1100, Ankur Sinha wrote: > On Thu, 2013-12-05 at 22:31 -0800, Richard Vickery wrote: > > If it happened to you, Adam, as well, I wonder if it might be a bug? > > Does if happen to others? Being somewhat ignorant, I thought the > > problem was me and how I installed it, which is why I brought it up. > > It would be interesting to find out the randomness of this thing. > > > > Well, it does happen. It's probably due to latency in the search > results. If you hit in "de" and wait a bit, it does show up. in the cases I recall seeing, that wasn't it. It just never showed. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On 12/06/2013 10:45 AM, Igor Gnatenko wrote: > On Fri, 2013-12-06 at 10:41 +0100, Joachim Backes wrote: >> Hi all, >> >> anybody sees this too if including the updates-testing repo to "yum update": >> >> sudo yum update --enablerepo=updates-testing >> Loaded plugins: langpacks >> updates-testing/20/x86_64/metalink | 27 kB >> 00:00 >> updates-testing | 4.6 kB >> 00:00 >> http://ftp-stud.hs-esslingen.de/pub/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://mirrors.n-ix.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://mirror1.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://mirror2.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://mirror.fraunhofer.de/dl.fedoraproject.org/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://ftp.byfly.by/pub/fedoraproject.org/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://mirror.1000mbps.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://sunsite.mff.cuni.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> updates-testing | 4.6 kB >> 00:00 >> http://ultra.linux.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for updates-testing >> Trying other mirror. >> >> .. And so on. >> >> Kind regards >> >> Joachim Backes >> >> -- >> >> Fedora release 20 (Heisenbug) >> Kernel-3.11.10-301.fc20.x86_64 >> >> Joachim Backes >> https://www-user.rhrk.uni-kl.de/~backes > > Confirm! You can fix this by: > # yum --disablerepo=updates,updates-testing downgrade yum > # yum clean all > # yum makecache > > and sure -1 karma in [0]bodhi > > [0]https://admin.fedoraproject.org/updates/FEDORA-2013-22706/yum-3.4.3-119.fc20 > Hi Igor, thank you, did help :-) Joachim Backes -- Fedora release 20 (Heisenbug) Kernel-3.11.10-301.fc20.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: Updates-testing mirrors inoperable?
On Fri, 2013-12-06 at 10:41 +0100, Joachim Backes wrote: > Hi all, > > anybody sees this too if including the updates-testing repo to "yum update": > > sudo yum update --enablerepo=updates-testing > Loaded plugins: langpacks > updates-testing/20/x86_64/metalink | 27 kB > 00:00 > updates-testing | 4.6 kB > 00:00 > http://ftp-stud.hs-esslingen.de/pub/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://mirrors.n-ix.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://mirror1.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://mirror2.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://mirror.fraunhofer.de/dl.fedoraproject.org/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://ftp.byfly.by/pub/fedoraproject.org/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://mirror.1000mbps.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://sunsite.mff.cuni.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > updates-testing | 4.6 kB > 00:00 > http://ultra.linux.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for updates-testing > Trying other mirror. > > .. And so on. > > Kind regards > > Joachim Backes > > -- > > Fedora release 20 (Heisenbug) > Kernel-3.11.10-301.fc20.x86_64 > > Joachim Backes > https://www-user.rhrk.uni-kl.de/~backes Confirm! You can fix this by: # yum --disablerepo=updates,updates-testing downgrade yum # yum clean all # yum makecache and sure -1 karma in [0]bodhi [0]https://admin.fedoraproject.org/updates/FEDORA-2013-22706/yum-3.4.3-119.fc20 -- -Igor Gnatenko -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F20: Updates-testing mirrors inoperable?
Hi all, anybody sees this too if including the updates-testing repo to "yum update": sudo yum update --enablerepo=updates-testing Loaded plugins: langpacks updates-testing/20/x86_64/metalink | 27 kB 00:00 updates-testing | 4.6 kB 00:00 http://ftp-stud.hs-esslingen.de/pub/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://mirrors.n-ix.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://mirror1.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://mirror2.atrpms.net/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://mirror.fraunhofer.de/dl.fedoraproject.org/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://ftp.byfly.by/pub/fedoraproject.org/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://mirror.1000mbps.com/fedora/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://sunsite.mff.cuni.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. updates-testing | 4.6 kB 00:00 http://ultra.linux.cz/MIRRORS/fedora.redhat.com/linux/updates/testing/20/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates-testing Trying other mirror. .. And so on. Kind regards Joachim Backes -- Fedora release 20 (Heisenbug) Kernel-3.11.10-301.fc20.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F20 KDE popups
It seems I am getting a popup msg (in the top middle of the msg it has the topic "Local system message service) with various warnings/msgs from my log(s),and the popups appear in the top/middle of my screen, one on top of the other. And you have to click on them to get rid of them. How the heck do you turn that off? It is very annoying to say the least. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
