Re: fedup for F23 and beyond
On Thu, 2015-05-28 at 15:05 -0600, Kevin Fenzi wrote: With timed: you don't get the newest thing, but switching to the new stuff is more on your schedule. You can ignore the new release for a while and still get bugfixes/security updates until you are ready to do the upgrade. I should add one more thing: in my vision, applications are always updated, period, and that's more important than anything else. We have to do that no matter what, or people will start leaving Fedora for Ubuntu Snappy Whatever which is supposed to arrive real soon now. They're going to have a stable OS with up-to-date applications (not considered part of the OS!), and we need that too to remain competitive. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On 28 May 2015 at 16:42, Michael Catanzaro mcatanz...@gnome.org wrote: On Thu, 2015-05-28 at 15:05 -0600, Kevin Fenzi wrote: With timed: you don't get the newest thing, but switching to the new stuff is more on your schedule. You can ignore the new release for a while and still get bugfixes/security updates until you are ready to do the upgrade. I should add one more thing: in my vision, applications are always updated, period, and that's more important than anything else. We have to do that no matter what, or people will start leaving Fedora for Ubuntu Snappy Whatever which is supposed to arrive real soon now. They're going to have a stable OS with up-to-date applications (not considered part of the OS!), and we need that too to remain competitive. Good luck with that vision. I would buy into it a bit more if this wasn't the same chestnut dragged out every couple of releases to somehow motivate us to accept whatever big OS change is being pushed. It has become the Cry Wolf story and while eventually the wolf eats the flock... it does so because no one believes the criers anymore. Please, come up with a better story than people will drop us for Ubuntu because none of the changes we have done have stopped that from happening when it has happened.. and none of them have made us overtake Ubuntu in the last 8 years. -- Stephen J Smoogen. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, May 28, 2015 at 3:58 PM, Michael Catanzaro mcatanz...@gnome.org wrote: On Thu, 2015-05-28 at 14:39 -0400, Przemek Klosowski wrote: Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution. I think we're already at the point where -- at least for Fedora Workstation (not sure about Server/Cloud), and except for infrastructure issues -- we can stop branding our releases with a version number, and simply have a particularly big offline update every six months. Behind-the-scenes, we still have the six-month cycle, but this is hidden to users. They get Fedora and it's just Fedora, not Fedora 21 or Fedora 22. People stop complaining about the 13-months of support that isn't long enough for them: we wouldn't have that short support window anymore, instead there is *indefinite* support so long as you take your monthly QAed updates pack (five small updates packs, then a big updates pack, then five smaller ones, then a big one, ...). This is the model Windows is moving to, and it makes a lot of sense to me. I think that is technically possible. I also think if it were done without any sort of ABI/API stability kept in mind, people would be irate. Hiding what amounts to a major version release as an updates pack is disingenuous at best, and will break things for users at worst. We cannot do what you describe without a massive amount of re-education on what an update means in Fedora. I'm kind of surprised you even suggested this, given the focus of Workstation is on developers (at the moment) and we're talking in another thread about how to provided some kind of API/ABI at the platform level that developers can depend on. Your goal is nice, but we are nowhere near the point of actually doing what you just said. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, May 28, 2015 at 04:08:23PM -0400, Josh Boyer wrote: about how to provided some kind of API/ABI at the platform level that developers can depend on. Your goal is nice, but we are nowhere near the point of actually doing what you just said. Also, the release cycle is a reliable engine for press attention and coverage. That shouldn't take precedence over good user experience, but _does_ have value. We'd need to find a new way of generating at least that much attention (or ideally, even more, of course). -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, 28 May 2015 14:58:03 -0500 Michael Catanzaro mcatanz...@gnome.org wrote: On Thu, 2015-05-28 at 14:39 -0400, Przemek Klosowski wrote: Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution. I think we're already at the point where -- at least for Fedora Workstation (not sure about Server/Cloud), and except for infrastructure issues -- we can stop branding our releases with a version number, and simply have a particularly big offline update every six months. Behind-the-scenes, we still have the six-month cycle, but this is hidden to users. They get Fedora and it's just Fedora, not Fedora 21 or Fedora 22. People stop complaining about the 13-months of support that isn't long enough for them: we wouldn't have that short support window anymore, instead there is *indefinite* support so long as you take your monthly QAed updates pack (five small updates packs, then a big updates pack, then five smaller ones, then a big one, ...). This is the model Windows is moving to, and it makes a lot of sense to me. Well, this is sort of the old 'rolling release' vs 'timed releases' thing. ;) IMHO, some advanced users prefer/are happy with rolling releases, but I think the majority of users would not be happy at all. With rolling: you get the latest stuff soon, but you cannot decide when you want to deal with that stuff very easily, you have to take it when it's pushed to you (or block security and bugfixes). With timed: you don't get the newest thing, but switching to the new stuff is more on your schedule. You can ignore the new release for a while and still get bugfixes/security updates until you are ready to do the upgrade. In some kind of ideal world it would be great if rawhide was the rolling release and people who liked that model could use it day to day. (Which is really already the case, but things do break so you need to be good at troubleshooting and/or have alternatives in case the thing you normally use breaks). kevin pgpyNZ2Ep1J89.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Secure boot and packaging third-party kernel modules
On 05/28/2015 10:26 AM, David Sommerseth wrote: ... stuff deleted ... Any thoughts or comments to this approach? Anyone got a better idea? Your process looks reasonable. Yes, I do know it is not good to have the keying material for the signing too easily available. So I'm also keen to hear ideas how to protect the key better. With that said, I'm planning on only providing access to the key file to the root user only. And I'll look into if I can restrict the accesss even further with some SELinux rules (so only the ExecStartPre= script can access it together with the preparation script. Systemtap has a similar problem. By definition, we compile kernel modules and still need to work on a secure boot system. To solve it, we automated the process you outlined above and added it to our existing compile server functionality. On a client machine you ask for a systemtap script to run, and behind the scenes the script gets shipped off to a compile server that has a matching kernel devel environment and matching MOKs. The signed module gets shipped back to the client system and run. The advantage we have here is that if you have lots of client systems, none of them have the private MOK key installed on them - only the server has the private key(s). We only pass around public key fingerprints. Another thought ... Are there other packages who could benefit of such a solution if it was made more generic? I'm willing to investigate into this too, if there are more users out there ... Or if someone has already done that - no need to reinvent the wheel! Systemtap's solution is probably pretty specific to ourselves, but the general idea (and perhaps some code) could certainly be borrowed. But really the best solution here is to get the mhvtl kernel module upstream. -- David Smith dsm...@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, 28 May 2015 17:32:24 -0400 Matthew Miller mat...@fedoraproject.org wrote: On Thu, May 28, 2015 at 03:05:03PM -0600, Kevin Fenzi wrote: In some kind of ideal world it would be great if rawhide was the rolling release and people who liked that model could use it day to day. (Which is really already the case, but things do break so you need to be good at troubleshooting and/or have alternatives in case the thing you normally use breaks). Well, and as someone just pointed out to me, fairly enough, on Reddit, Rawhide is often a rolling release of the latest prerelease dev versions of software, and we don't really have a rolling release of the latest stable versions (except to the extent that people push these as updates, which is quite a lot). Sure, agreed. Although there's a lot of stable releases of things that flow into rawhide too in cases where upstream doesn't have a development branch or the maintainer(s) decide something is not stable enough. Of course gnome, kernel, mesa and such are prereleases a good part of the time. kevin pgpXd0oUtej5M.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On 05/28/2015 03:58 PM, Michael Catanzaro wrote: I think we're already at the point where -- at least for Fedora Workstation (not sure about Server/Cloud), and except for infrastructure issues -- we can stop branding our releases with a version number, and simply have a particularly big offline update every six months. Behind-the-scenes, we still have the six-month cycle, but this is hidden to users. They get Fedora and it's just Fedora, not Fedora 21 or Fedora 22. People stop complaining about the 13-months of support that isn't long enough for them: we wouldn't have that short support window anymore, instead there is *indefinite* support so long as you take your monthly QAed updates pack That's exactly what I had in mind. BTW, the support issue is a serious block to Fedora adoption. The N-N+1 model complicates administration: even if in-situ upgrades work it's a different workflow than routine updates. A guarantee of long-term simple updates would definitely help Fedora. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, May 28, 2015 at 4:05 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 28.05.2015 um 21:58 schrieb Michael Catanzaro: On Thu, 2015-05-28 at 14:39 -0400, Przemek Klosowski wrote: Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution. I think we're already at the point where -- at least for Fedora Workstation (not sure about Server/Cloud), and except for infrastructure issues -- we can stop branding our releases with a version number, and simply have a particularly big offline update every six months. Behind-the-scenes, we still have the six-month cycle, but this is hidden to users. They get Fedora and it's just Fedora, not Fedora 21 or Fedora 22. People stop complaining about the 13-months of support that isn't long enough for them: we wouldn't have that short support window anymore, instead there is *indefinite* support so long as you take your monthly QAed updates pack (five small updates packs, then a big updates pack, then five smaller ones, then a big one, ...). This is the model Windows is moving to, and it makes a lot of sense to me when i hear offline update i have enough at all frankly what people really need is relieable and fast *online updates* and not taking the esay road well go offline and that works pretty well over many years now *with expierience* what services you need to restart and if you should log off or just close specific applicatoons and start them again giving up and say meh i am not able and so go offline may work for some part of the userbase, that maybe even fine *as long* efforts to continue what we have now for many many years for advanced users won't die I understand the sentiment. I don't like rebooting for updates either. However, our efforts on live online updates to date have been we'll let RPM update this and maybe throw some scripts at it to restart things and hope it works. It does in a lot of cases and doesn't in others. And our advanced users are distinguished by the fact that they can figure out when it doesn't work and then fix things. That isn't really a _better_ experience than offline updates. It's just familiar to you. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
Am 28.05.2015 um 22:12 schrieb Josh Boyer: On Thu, May 28, 2015 at 4:05 PM, Reindl Harald wrote: when i hear offline update i have enough at all frankly what people really need is relieable and fast *online updates* and not taking the esay road well go offline and that works pretty well over many years now *with expierience* what services you need to restart and if you should log off or just close specific applicatoons and start them again giving up and say meh i am not able and so go offline may work for some part of the userbase, that maybe even fine *as long* efforts to continue what we have now for many many years for advanced users won't die I understand the sentiment. I don't like rebooting for updates either. However, our efforts on live online updates to date have been we'll let RPM update this and maybe throw some scripts at it to restart things and hope it works. It does in a lot of cases and doesn't in others. And our advanced users are distinguished by the fact that they can figure out when it doesn't work and then fix things. That isn't really a _better_ experience than offline updates. It's just familiar to you no, it is not just familiar to me i came in 2006 from Windows because i had enough of this reboots all the time because of updates and software installations and hearing that nearly 10 years later linux distribution seriously consider to went back that road makes me puke signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
Am 28.05.2015 um 21:58 schrieb Michael Catanzaro: On Thu, 2015-05-28 at 14:39 -0400, Przemek Klosowski wrote: Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution. I think we're already at the point where -- at least for Fedora Workstation (not sure about Server/Cloud), and except for infrastructure issues -- we can stop branding our releases with a version number, and simply have a particularly big offline update every six months. Behind-the-scenes, we still have the six-month cycle, but this is hidden to users. They get Fedora and it's just Fedora, not Fedora 21 or Fedora 22. People stop complaining about the 13-months of support that isn't long enough for them: we wouldn't have that short support window anymore, instead there is *indefinite* support so long as you take your monthly QAed updates pack (five small updates packs, then a big updates pack, then five smaller ones, then a big one, ...). This is the model Windows is moving to, and it makes a lot of sense to me when i hear offline update i have enough at all frankly what people really need is relieable and fast *online updates* and not taking the esay road well go offline and that works pretty well over many years now *with expierience* what services you need to restart and if you should log off or just close specific applicatoons and start them again giving up and say meh i am not able and so go offline may work for some part of the userbase, that maybe even fine *as long* efforts to continue what we have now for many many years for advanced users won't die signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, May 28, 2015 at 03:05:03PM -0600, Kevin Fenzi wrote: In some kind of ideal world it would be great if rawhide was the rolling release and people who liked that model could use it day to day. (Which is really already the case, but things do break so you need to be good at troubleshooting and/or have alternatives in case the thing you normally use breaks). Well, and as someone just pointed out to me, fairly enough, on Reddit, Rawhide is often a rolling release of the latest prerelease dev versions of software, and we don't really have a rolling release of the latest stable versions (except to the extent that people push these as updates, which is quite a lot). -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
spot pushed to perl-Test-MockObject (master). 1.20150527
From 489f5cc2b1369ab04301a63d9929f84e370bf472 Mon Sep 17 00:00:00 2001 From: Tom Callaway s...@fedoraproject.org Date: Thu, 28 May 2015 15:13:33 -0400 Subject: 1.20150527 diff --git a/.gitignore b/.gitignore index 0ae376e..03eb18a 100644 --- a/.gitignore +++ b/.gitignore @@ -2,3 +2,4 @@ Test-MockObject-1.09.tar.gz /Test-MockObject-1.20120301.tar.gz /Test-MockObject-1.20140408.tar.gz /Test-MockObject-1.20150521.tar.gz +/Test-MockObject-1.20150527.tar.gz diff --git a/perl-Test-MockObject.spec b/perl-Test-MockObject.spec index 2ab144f..39e2f30 100644 --- a/perl-Test-MockObject.spec +++ b/perl-Test-MockObject.spec @@ -1,5 +1,5 @@ Name: perl-Test-MockObject -Version:1.20150521 +Version:1.20150527 Release:1%{?dist} Summary:Perl extension for emulating troublesome interfaces Group: Development/Libraries @@ -49,6 +49,9 @@ PERL_RUN_ALL_TESTS=1 make test %{_mandir}/man3/*.3pm* %changelog +* Thu May 28 2015 Tom Callaway s...@fedoraproject.org - 1.20150527-1 +- update to 1.20150527 + * Tue May 26 2015 Tom Callaway s...@fedoraproject.org - 1.20150521-1 - update to 1.20150521 diff --git a/sources b/sources index 82bd59d..5fd8bdb 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -824d0e0ca23cec908b436db9d95fa457 Test-MockObject-1.20150521.tar.gz +af960be08a61ed322f585e965a56 Test-MockObject-1.20150527.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-Test-MockObject.git/commit/?h=masterid=489f5cc2b1369ab04301a63d9929f84e370bf472 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Review swaps
On Wed, May 27, 2015 at 9:32 AM, gil punto...@libero.it wrote: Il 27/05/2015 17:28, Jerry James ha scritto: I'm working toward supporting GAP's HAP package, which is used by sagemath. I need reviews for some of the foundational packages (more will be coming). There are some interdependencies, noted below: 1. gap-pkg-autpgrp: https://bugzilla.redhat.com/show_bug.cgi?id=1205777 No dependencies. hi taken can you review this https://bugzilla.redhat.com/show_bug.cgi?id=1215074 thanks in advance gil Done, and thank you. -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Thu, 2015-05-28 at 14:39 -0400, Przemek Klosowski wrote: Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution. I think we're already at the point where -- at least for Fedora Workstation (not sure about Server/Cloud), and except for infrastructure issues -- we can stop branding our releases with a version number, and simply have a particularly big offline update every six months. Behind-the-scenes, we still have the six-month cycle, but this is hidden to users. They get Fedora and it's just Fedora, not Fedora 21 or Fedora 22. People stop complaining about the 13-months of support that isn't long enough for them: we wouldn't have that short support window anymore, instead there is *indefinite* support so long as you take your monthly QAed updates pack (five small updates packs, then a big updates pack, then five smaller ones, then a big one, ...). This is the model Windows is moving to, and it makes a lot of sense to me. Michael -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Including tlp in Fedora Workstation by default
* Do you think that the average user with a clicking sound card or disk ** corruption when suspending would be able to make the link to this new ** package?* Even better ... the integrated mouse pointer on my external ThinkPad USB keyboard stops working if USB suspend is enabled for this device. I get this same issue with my computer, but TLP doesn't suspend input devices... or at least it should. +1 ... If the kernel isn't perfect, lets make the kernel perfect instead. Just my 2 cents. The one thing I like about TLP would be the ability to tune the machine based on power state. If the kernel or gnome or whatever can do this, I applaud it. Something like this should be default and tweak-able. This includes disk spin down time, bus powersave modes and variable writeback rates. It's quite clear that battery life sucks for the stock install... I think some initiative should be taken regardless of the method. I'm sure that laptops are the most effected by this. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fwd: clang++ compiler flags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - Forwarded Message Subject: clang++ compiler flags Date: Thu, 28 May 2015 21:05:55 +0200 From: Antonio Trande anto.tra...@gmail.com To: a...@lists.fedoraproject.org Hi all, 'clang++' compiler is unable to use ARM %optflags used on Fedora packaging: http://koji.fedoraproject.org/koji/getfile?taskID=9868342name=build.logoffset=-4000 Which flags i can use on ARM architectures with clang++ compiler? Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVZ3ABAAoJEF5tK7VWXmU8bYwH/0x4tU6//prUfzxobJFMWD/c aXUQFjVbN72vkaJFwUceBnasQKS8mOIk34AJ4zf7W9I7doypEcEvzeerPIamgRjj +F4INpGo4UqzFjEOIBgowxg4P44KunOlbNSuHlgSdXph/QVhYT1zL2M/edvDEO2a 8gIF7Gh33DlXq9gb6tCb8N0RpNUJHSDd5Ottvr6TQdjyaSBkgB7HyhUAa4mwJGCE ppBu6lMAhgHctw4O/zpZ9WsubwB+gLYXQyX61boRwuctsRz90+i7OebddpxOXpax 0SElf4mrWJ+O5kQ8+4xBPa98LqxFIryqrb/V13uI5mkIg+2zm7rsWKDAlE/7oOE= =zprM -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On 05/28/2015 11:42 AM, Will Woods wrote: Here's how it should work: 1) Download packages for the new system 2) Use the systemd Offline Updates[2] facility to install packages This is really simple - simple enough that it should probably be provided by the system packaging tools themselves. Actually, there is a broad issue here: is there a point where the system is so stable that updating is a continuous process without the need for a Fedora N - N+1 transitions? Specifically, will we have a 3-digit Fedora release in May 2053 :-? It seems to me that the 6-month release cycle has traditionally been driven by two separate reasons: technology and workflow. The first is a need to accommodate major, incompatible technology shifts. The second one just introduces a natural cadence of work leading to an orderly release. Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Minutes from Env-and-Stacks WG meeting (2015-05-28)
== #fedora-meeting-2: Env and Stacks (2015-05-28) == Meeting started by hhorak at 17:00:56 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-2/2015-05-28/env-and-stacks.2015-05-28-17.00.log.html . Meeting summary --- * greetings.. (hhorak, 17:01:28) * how to gather feedback from users? who are our users? (hhorak, 17:08:23) * LINK: https://lists.fedoraproject.org/pipermail/env-and-stacks/2015-May/000783.html (hhorak, 17:09:39) * ACTION: hhorak to initiate a list of questions our WG want all editions to ask.. and will share a link to some collaborative tool.. (hhorak, 17:36:44) * Council Engineering update (hhorak, 17:38:04) * LINK: https://lists.fedoraproject.org/pipermail/env-and-stacks/2015-May/000786.html (hhorak, 17:38:11) * Think about if it would be possible to auto-enable install copr repos: dnf awesome-copr-auto-enable-install-plugin rhscl/httpd24 (vpavlin, 18:01:11) * IDEA: copr to have option to specify the main package from the copr repo, so it may be installed as soon as user says `dnf copr-install rhscl/httpd24` (hhorak, 18:02:22) * IDEA: to prioritize few items from the whole WG's task list and set a concrete goals for F23/F24 based on it.. (hhorak, 18:08:06) * IDEA: for now, playground is launched tomorrow by way of a dnf plugin called playground .. which in fact just recognizes a very small list of copr repos.. over time, the list of copr repos grow.. eventually.. the formal playground repo comes online... (hhorak, 18:15:38) * ACTION: everybody to think about which of the tasks we make goals from for F23/F24 (hhorak, 18:18:37) * ACTION: everybody to think about and write up questions that we want to ask users of editions (hhorak, 18:18:38) Meeting ended at 18:19:16 UTC. Action Items * hhorak to initiate a list of questions our WG want all editions to ask.. and will share a link to some collaborative tool.. * everybody to think about which of the tasks we make goals from for F23/F24 * everybody to think about and write up questions that we want to ask users of editions Action Items, by person --- * hhorak * hhorak to initiate a list of questions our WG want all editions to ask.. and will share a link to some collaborative tool.. * **UNASSIGNED** * everybody to think about which of the tasks we make goals from for F23/F24 * everybody to think about and write up questions that we want to ask users of editions People Present (lines said) --- * hhorak (57) * langdon (37) * vpavlin (36) * zodbot (4) * bowlofeggs (3) * bkabrda (0) * phracek (0) * ttomecek (0) * sicampbell (0) * juhp (0) * ncoghlan (0) * walters (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On 05/28/2015 02:44 PM, Reindl Harald wrote: Am 28.05.2015 um 20:39 schrieb Przemek Klosowski: Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution who talks about a entire new distribution? more than 20 servers installed in 2008 with F9 and now on F21 while fully online and just a reboot like a ordinary kernel update - that's how things have to work Yeah, me too, but we had to use several different tools on the way, and I actually got stuck in some cases, and decided to reinstall those. I am talking about making it a tested, official process. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1225066] perl-Test-MockObject-1.20150527 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225066 --- Comment #7 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- spot's perl-Test-MockObject-1.20150527-1.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=639764 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: fedup for F23 and beyond
Am 28.05.2015 um 20:39 schrieb Przemek Klosowski: On 05/28/2015 11:42 AM, Will Woods wrote: Here's how it should work: 1) Download packages for the new system 2) Use the systemd Offline Updates[2] facility to install packages This is really simple - simple enough that it should probably be provided by the system packaging tools themselves. Actually, there is a broad issue here: is there a point where the system is so stable that updating is a continuous process without the need for a Fedora N - N+1 transitions? Specifically, will we have a 3-digit Fedora release in May 2053 :-? It seems to me that the 6-month release cycle has traditionally been driven by two separate reasons: technology and workflow. The first is a need to accommodate major, incompatible technology shifts. The second one just introduces a natural cadence of work leading to an orderly release. Do you think the tech could stabilize enough to obviate the first reason? The 6-month workflow cadence remains a good idea, of course, but could result in a major offline upgrade, instead of an entire new distribution who talks about a entire new distribution? Fedora dist-upgrades are routine tasks with YUM here for years in production so there is no new distribution nor a real need for going offline and any Fedora release not be able to get upgraded online would be a large step backwards more than 20 servers installed in 2008 with F9 and now on F21 while fully online and just a reboot like a ordinary kernel update - that's how things have to work signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
spot uploaded Test-MockObject-1.20150527.tar.gz for perl-Test-MockObject
af960be08a61ed322f585e965a56 Test-MockObject-1.20150527.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Test-MockObject/Test-MockObject-1.20150527.tar.gz/af960be08a61ed322f585e965a56/Test-MockObject-1.20150527.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Review swaps
On Wed, May 27, 2015 at 10:04 AM, gil punto...@libero.it wrote: hi taken can you review this https://bugzilla.redhat.com/show_bug.cgi?id=1215080 thanks in advance gil Taken, and thank you. -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1226095] perl-Test-Pod-1.50 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1226095 --- Comment #2 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=9873491 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: fedup for F23 and beyond
On Thu, May 28, 2015 at 12:58 PM, Michael Catanzaro mcatanz...@gnome.org wrote: ...we can stop branding our releases with a version number...we still have the six-month cycle, but this is hidden to users...this is the model Windows is moving to... As Josh alluded, I'm not exactly clear on the value of keeping things the same behind the scenes and hiding the release levels from the users. For me, the release change indicates first of all that I should read the release notes and familiarize myself with what has changed. The release number also serves as an easy reference to what levels of software you're running, albeit at a high level (due to maintenance changes). You're always going to need to understand that and if you get rid of the release number you'll need to come up with another type of indicator that is as simple and easy to understand. Matt referenced the advertising factor; and that's a great point. Everyone always is interested in the latest and greatest. The press is geared toward that... everyone is always buzzing about the new Android release, IOS version, Windows version, etc. Speaking of Windows, their strategy has more to do about changes to their revenue model (which has been driven by the fact that Linux, IOS, Android, etc. are Free.) than anything else. They are still talking about major updates and if past experience is any guide you'll probably see major changes identified as Service Pack X as they did in the past. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1226095] New: perl-Test-Pod-1.50 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1226095 Bug ID: 1226095 Summary: perl-Test-Pod-1.50 is available Product: Fedora Version: rawhide Component: perl-Test-Pod Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, pertu...@free.fr, st...@silug.org Latest upstream release: 1.50 Current version/release in rawhide: 1.49-1.fc23 URL: http://search.cpan.org/dist/Test-Pod/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1226095] perl-Test-Pod-1.50 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1226095 --- Comment #1 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Created attachment 1031531 -- https://bugzilla.redhat.com/attachment.cgi?id=1031531action=edit [patch] Update to 1.50 (#1226095) -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (el6) to 'Approved'
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (el6) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-Term-ReadLine-Gnu/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (f22) to 'Approved'
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (f22) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-Term-ReadLine-Gnu/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (f21) to 'Approved'
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (f21) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-Term-ReadLine-Gnu/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[EPEL-devel] [Fedocal] Reminder meeting : EPSCo weekly meeting
Dear all, You are kindly invited to the meeting: EPSCo weekly meeting on 2015-05-29 from 17:00:00 to 18:00:00 UTC At e...@irc.freenode.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/2542/ ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: fedup for F23 and beyond
Am 29.05.2015 um 01:11 schrieb Stephen John Smoogen: On 28 May 2015 at 16:42, Michael Catanzaro mcatanz...@gnome.org wrote: On Thu, 2015-05-28 at 15:05 -0600, Kevin Fenzi wrote: With timed: you don't get the newest thing, but switching to the new stuff is more on your schedule. You can ignore the new release for a while and still get bugfixes/security updates until you are ready to do the upgrade. I should add one more thing: in my vision, applications are always updated, period, and that's more important than anything else. We have to do that no matter what, or people will start leaving Fedora for Ubuntu Snappy Whatever which is supposed to arrive real soon now. They're going to have a stable OS with up-to-date applications (not considered part of the OS!), and we need that too to remain competitive. Good luck with that vision. I would buy into it a bit more if this wasn't the same chestnut dragged out every couple of releases to somehow motivate us to accept whatever big OS change is being pushed. It has become the Cry Wolf story and while eventually the wolf eats the flock... it does so because no one believes the criers anymore me too and besides that gnome is (luckily) not the only desktop on Fedora - Fedora *does not* need to be competitive for the price becoming the same and hit *existing users* in the face which choose Fedora *because it s* Fedora and *not* Ubuntu, Windows or OSX signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (el5) to 'Approved'
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (el5) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-Term-ReadLine-Gnu/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (f20) to 'Approved'
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (f20) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-Term-ReadLine-Gnu/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (master) to 'Approved'
eseyman changed cra's 'commit' permission on perl-Term-ReadLine-Gnu (master) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-Term-ReadLine-Gnu/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: libvpx got soname bump and no one noticed?
W dniu 28.05.2015 o 07:28, Robin Lee pisze: Sorry guys, my fault. (insert local idiom about elephant in a store here). Sorted out with help of spot and kalev. You should update rpmfusion-free-relase. And run 'dnf downgrade ffmpeg-libs'. There is no 'branched' repos in RPMFusion. And before f22 is released, you are actually using the 'rawhide' repos of RPMFusion. But After f22 released, RPMFusion f22 repos is then finally branched and the yum repo configs are updated in new version of rpmfusion-free-release. So, if you run a global 'dnf upgrade' before upgrade rpmfusion-free-release, you will pull in some 'rawhide' packages from RPMFusion. I rebuilt that part of rpmfusion I use (vlc, mplayer and deps). Problem was with VirtualBox... so for some time I will have to deal without winxp vm (used from time to time for tools which are not wine friendly). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: libvpx got soname bump and no one noticed?
On Thu, May 28, 2015 at 9:16 AM, Marcin Juszkiewicz mjuszkiew...@redhat.com wrote: W dniu 28.05.2015 o 07:28, Robin Lee pisze: Sorry guys, my fault. (insert local idiom about elephant in a store here). Sorted out with help of spot and kalev. You should update rpmfusion-free-relase. And run 'dnf downgrade ffmpeg-libs'. There is no 'branched' repos in RPMFusion. And before f22 is released, you are actually using the 'rawhide' repos of RPMFusion. But After f22 released, RPMFusion f22 repos is then finally branched and the yum repo configs are updated in new version of rpmfusion-free-release. So, if you run a global 'dnf upgrade' before upgrade rpmfusion-free-release, you will pull in some 'rawhide' packages from RPMFusion. I rebuilt that part of rpmfusion I use (vlc, mplayer and deps). Problem was with VirtualBox... so for some time I will have to deal without winxp vm (used from time to time for tools which are not wine friendly). You could use Boxes / virt-manager ... ships in the Fedora repo and should be good enough for cases where you do not need hardware accelerated 3D in the guest. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
pghmcfc pushed to perl-parent (perl-parent-0.234-1.fc23). Update to 0.234 (..more)
From 5330f6c608d419408dbf1f1462e2aded5baad169 Mon Sep 17 00:00:00 2001 From: Paul Howarth p...@city-fan.org Date: Thu, 28 May 2015 09:07:30 +0100 Subject: Update to 0.234 - New upstream release 0.234 - Fix the test for PMC loading to work on versions on Perl that don't have Config::non_bincompat_options (CPAN RT#102626) diff --git a/perl-parent.spec b/perl-parent.spec index 7171f3b..24929ec 100644 --- a/perl-parent.spec +++ b/perl-parent.spec @@ -1,6 +1,6 @@ Name: perl-parent Epoch: 1 -Version: 0.233 +Version: 0.234 Release: 1%{?dist} Summary: Establish an ISA relationship with base classes at compile time License: GPL+ or Artistic @@ -61,6 +61,11 @@ rm -rf %{buildroot} %{_mandir}/man3/parent.3* %changelog +* Thu May 28 2015 Paul Howarth p...@city-fan.org - 1:0.234-1 +- Update to 0.234 + - Fix the test for PMC loading to work on versions on Perl that don't have +Config::non_bincompat_options (CPAN RT#102626) + * Tue May 26 2015 Paul Howarth p...@city-fan.org - 1:0.233-1 - Update to 0.233 - The diagnostic about inheriting from ourselves was removed; it served no diff --git a/sources b/sources index 992646e..20441eb 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -fb2d4803c7c2423bae9403bb1cb48384 parent-0.233.tar.gz +b02fc0e7f9b74de42e60816c38be parent-0.234.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-parent.git/commit/?h=perl-parent-0.234-1.fc23id=5330f6c608d419408dbf1f1462e2aded5baad169 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: libvpx got soname bump and no one noticed?
On Thu, May 28, 2015 at 12:44 AM, Marcin Juszkiewicz mjuszkiew...@redhat.com wrote: W dniu 28.05.2015 o 09:27, drago01 pisze: Problem was with VirtualBox... so for some time I will have to deal without winxp vm (used from time to time for tools which are not wine friendly). You could use Boxes / virt-manager ... ships in the Fedora repo and should be good enough for cases where you do not need hardware accelerated 3D in the guest. I am fully aware of it. Just this VM is about 7 years old and recreation of it from scratch would take too much time probably as I forgot what exactly is installed/added there etc. Tools to play with phones, flashing tools, devboards stuff, taxes etc. -- You can open the old .vdi file using virt-manager. Alternativly you could build VirtualBox from source and configure it without libvpx. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Review swaps
Il 27/05/2015 18:04, gil ha scritto: Il 27/05/2015 17:28, Jerry James ha scritto: I'm working toward supporting GAP's HAP package, which is used by sagemath. I need reviews for some of the foundational packages (more will be coming). There are some interdependencies, noted below: 1. gap-pkg-autpgrp: https://bugzilla.redhat.com/show_bug.cgi?id=1205777 No dependencies. 2. gap-pkg-polycyclic: https://bugzilla.redhat.com/show_bug.cgi?id=1205904 Requires #1 and #3, so there is a bootstrap mechanism to build without #3 the first time. 3. gap-pkg-alnuth: https://bugzilla.redhat.com/show_bug.cgi?id=1205905 Requires #2. Tests require #4, so there is a bootstrap mechanism. 4. gap-pkg-radiroot: https://bugzilla.redhat.com/show_bug.cgi?id=1206367 Requires #3. 5. gap-pkg-fga: https://bugzilla.redhat.com/show_bug.cgi?id=1222690 No dependencies. hi taken can you review this https://bugzilla.redhat.com/show_bug.cgi?id=1215080 thanks in advance gil 6. gap-pkg-edim: https://bugzilla.redhat.com/show_bug.cgi?id=1223627 No dependencies. taken Other than the bootstrap builds neeed for #2 and #3, these are all very simple packages. GAP noarch packages are designed to just be unpacked in the parent GAP directory. Numbers 1 through 5 on this list are noarch. Number 6 takes a little more work because of the arch-specific bit, but is still a pretty simple package. Note that I recently changed jobs. I no longer work in a Fedora / RHEL / CentOS shop. I now work in an Ubuntu shop. And my commute time increased as well. Together, this means that my turnaround time for reviews will probably be larger than it has been in the past. If you can handle that, give me some reviews to do for you in exchange for these. Thanks in advance. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
pghmcfc uploaded parent-0.234.tar.gz for perl-parent
b02fc0e7f9b74de42e60816c38be parent-0.234.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-parent/parent-0.234.tar.gz/b02fc0e7f9b74de42e60816c38be/parent-0.234.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: libvpx got soname bump and no one noticed?
W dniu 28.05.2015 o 09:27, drago01 pisze: Problem was with VirtualBox... so for some time I will have to deal without winxp vm (used from time to time for tools which are not wine friendly). You could use Boxes / virt-manager ... ships in the Fedora repo and should be good enough for cases where you do not need hardware accelerated 3D in the guest. I am fully aware of it. Just this VM is about 7 years old and recreation of it from scratch would take too much time probably as I forgot what exactly is installed/added there etc. Tools to play with phones, flashing tools, devboards stuff, taxes etc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
pghmcfc pushed to perl-parent (master). Update to 0.234 (..more)
From 5330f6c608d419408dbf1f1462e2aded5baad169 Mon Sep 17 00:00:00 2001 From: Paul Howarth p...@city-fan.org Date: Thu, 28 May 2015 09:07:30 +0100 Subject: Update to 0.234 - New upstream release 0.234 - Fix the test for PMC loading to work on versions on Perl that don't have Config::non_bincompat_options (CPAN RT#102626) diff --git a/perl-parent.spec b/perl-parent.spec index 7171f3b..24929ec 100644 --- a/perl-parent.spec +++ b/perl-parent.spec @@ -1,6 +1,6 @@ Name: perl-parent Epoch: 1 -Version: 0.233 +Version: 0.234 Release: 1%{?dist} Summary: Establish an ISA relationship with base classes at compile time License: GPL+ or Artistic @@ -61,6 +61,11 @@ rm -rf %{buildroot} %{_mandir}/man3/parent.3* %changelog +* Thu May 28 2015 Paul Howarth p...@city-fan.org - 1:0.234-1 +- Update to 0.234 + - Fix the test for PMC loading to work on versions on Perl that don't have +Config::non_bincompat_options (CPAN RT#102626) + * Tue May 26 2015 Paul Howarth p...@city-fan.org - 1:0.233-1 - Update to 0.233 - The diagnostic about inheriting from ourselves was removed; it served no diff --git a/sources b/sources index 992646e..20441eb 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -fb2d4803c7c2423bae9403bb1cb48384 parent-0.233.tar.gz +b02fc0e7f9b74de42e60816c38be parent-0.234.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-parent.git/commit/?h=masterid=5330f6c608d419408dbf1f1462e2aded5baad169 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1225050] perl-DateTime-Locale-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225050 --- Comment #3 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- psabata's perl-DateTime-Locale-0.46-1.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=639498 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata uploaded SQL-Statement-1.407.tar.gz for perl-SQL-Statement
abeedda4a2c085613cb77fb01631e5de SQL-Statement-1.407.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-SQL-Statement/SQL-Statement-1.407.tar.gz/abeedda4a2c085613cb77fb01631e5de/SQL-Statement-1.407.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
rawhide report: 20150528 changes
Compose started at Thu May 28 05:15:03 UTC 2015 Broken deps for i386 -- [OpenTK] OpenTK-1.1-1.4c.fc22.noarch requires mono(mscorlib) = 0:2.0.0.0 OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Xml) = 0:2.0.0.0 OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Windows.Forms) = 0:2.0.0.0 OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Drawing) = 0:2.0.0.0 OpenTK-1.1-1.4c.fc22.noarch requires mono(System) = 0:2.0.0.0 [RepetierHost] RepetierHost-0.90D-2.fc21.noarch requires mono(mscorlib) = 0:2.0.0.0 RepetierHost-0.90D-2.fc21.noarch requires mono(System.Xml) = 0:2.0.0.0 RepetierHost-0.90D-2.fc21.noarch requires mono(System.Windows.Forms) = 0:2.0.0.0 RepetierHost-0.90D-2.fc21.noarch requires mono(System.Drawing) = 0:2.0.0.0 RepetierHost-0.90D-2.fc21.noarch requires mono(System.Core) = 0:3.5.0.0 RepetierHost-0.90D-2.fc21.noarch requires mono(System) = 0:2.0.0.0 [bless] bless-0.6.0-14.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0 bless-0.6.0-14.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0 bless-0.6.0-14.fc22.i686 requires mono(System) = 0:2.0.0.0 bless-0.6.0-14.fc22.i686 requires mono(Mono.Posix) = 0:2.0.0.0 [boo] boo-0.9.4.9-11.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0 boo-0.9.4.9-11.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0 boo-0.9.4.9-11.fc22.i686 requires mono(System.Core) = 0:3.5.0.0 boo-0.9.4.9-11.fc22.i686 requires mono(System) = 0:2.0.0.0 boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Utilities) = 0:2.0.0.0 boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Tasks) = 0:2.0.0.0 boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Framework) = 0:2.0.0.0 boo-devel-0.9.4.9-11.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0 boo-devel-0.9.4.9-11.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0 boo-devel-0.9.4.9-11.fc22.i686 requires mono(System.Core) = 0:3.5.0.0 boo-devel-0.9.4.9-11.fc22.i686 requires mono(System) = 0:2.0.0.0 boo-devel-0.9.4.9-11.fc22.i686 requires mono(NAnt.DotNetTasks) = 0:0.90.3780.0 boo-devel-0.9.4.9-11.fc22.i686 requires mono(NAnt.Core) = 0:0.90.3780.0 [dmlite-plugins-memcache] dmlite-plugins-memcache-0.5.0-7.fc20.i686 requires libprotobuf.so.8 [eclipse-egit] eclipse-egit-3.7.1-1.fc23.noarch requires osgi(org.eclipse.jgit.java7) [gnome-shell-extension-background-logo] gnome-shell-extension-background-logo-3.17.2-1.fc23.noarch requires gnome-shell = 0:3.17.2 [gnome-shell-extensions] gnome-shell-extension-common-3.17.2-1.fc23.noarch requires gnome-shell = 0:3.17.2 [julia] julia-0.3.7-2.fc23.i686 requires libLLVM-3.5.so julia-devel-0.3.7-2.fc23.i686 requires libLLVM-3.5.so [matreshka] matreshka-servlet-devel-0.7.0-1.fc23.i686 requires matreshka-servlet-lib{?_isa} = 0:0.7.0-1.fc23 matreshka-servlet-lib-0.7.0-1.fc23.i686 requires matreshka{?_isa} = 0:0.7.0-1.fc23 matreshka-spikedog-api-devel-0.7.0-1.fc23.i686 requires matreshka-spikedog-api-lib{?_isa} = 0:0.7.0-1.fc23 matreshka-spikedog-api-lib-0.7.0-1.fc23.i686 requires matreshka{?_isa} = 0:0.7.0-1.fc23 matreshka-spikedog-api-lib-0.7.0-1.fc23.i686 requires matreshka-servlet-api{?_isa} = 0:0.7.0-1.fc23 matreshka-spikedog-core-devel-0.7.0-1.fc23.i686 requires matreshka-spikedog-core-lib{?_isa} = 0:0.7.0-1.fc23 matreshka-spikedog-core-lib-0.7.0-1.fc23.i686 requires matreshka{?_isa} = 0:0.7.0-1.fc23 matreshka-spikedog-core-lib-0.7.0-1.fc23.i686 requires matreshka-servlet-api{?_isa} = 0:0.7.0-1.fc23 [mesos] mesos-0.22.0-SNAPSHOT.1.c513126.fc22.1.i686 requires libprotobuf.so.8 python-mesos-0.22.0-SNAPSHOT.1.c513126.fc22.1.i686 requires libprotobuf.so.8 [mojarra] mojarra-2.1.7-8.fc20.noarch requires tomcat-servlet-3.0-api mojarra-2.1.7-8.fc20.noarch requires tomcat-jsp-2.2-api mojarra-2.1.7-8.fc20.noarch requires tomcat-el-2.2-api [monodevelop] monodevelop-2.8.8.4-9.fc23.i686 requires mono(mscorlib) = 0:2.0.0.0 monodevelop-2.8.8.4-9.fc23.i686 requires mono(System.Core) = 0:3.5.0.0 monodevelop-2.8.8.4-9.fc23.i686 requires mono(System) = 0:2.0.0.0 monodevelop-2.8.8.4-9.fc23.i686 requires mono(Microsoft.Build.Utilities.v3.5) = 0:3.5.0.0 monodevelop-2.8.8.4-9.fc23.i686 requires mono(Microsoft.Build.Framework) = 0:3.5.0.0 monodevelop-2.8.8.4-9.fc23.i686 requires mono(Microsoft.Build.Engine) = 0:3.5.0.0 [mule] mule-module-builders-2.0.2.20080813-11.fc21.noarch requires tomcat-servlet-3.0-api mule-transport-http-2.0.2.20080813-11.fc21.noarch requires tomcat-servlet-3.0-api mule-transport-servlet-2.0.2.20080813-11.fc21.noarch requires tomcat-servlet-3.0-api [netbeans-platform]
Agenda for Env-and-Stacks WG meeting (2015-05-28)
WG meeting will be at 17:00 UTC (13:00 EST, 19:00 Brno, 13:00 Boston, 2:00+1d Tokyo, 3:00+1d Brisbane) in #fedora-meeting-2 on Freenode. = Topics = * Continue discussion about Fedora Rings -- how to gather feedback from users? who are our users? (https://lists.fedoraproject.org/pipermail/env-and-stacks/2015-May/000783.html) * Council Engineering update (https://lists.fedoraproject.org/pipermail/env-and-stacks/2015-May/000786.html) * RHSCL Docker images compatibility with Fedora/Atomic use cases (are SCL images as developed under https://github.com/sclorg/rhscl2dockerfile/ usable in fedora/atomic or do we search for something different?) * Open Floor -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
psabata uploaded DateTime-Locale-0.46.tar.gz for perl-DateTime-Locale
f60bf58b2e2e29a49d214985fc17adca DateTime-Locale-0.46.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-DateTime-Locale/DateTime-Locale-0.46.tar.gz/f60bf58b2e2e29a49d214985fc17adca/DateTime-Locale-0.46.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-DateTime-Locale (master). 0.46 bump
From 572ddd7d6b5e375353be7e299dee2b189f577795 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0abata?= con...@redhat.com Date: Thu, 28 May 2015 11:19:59 +0200 Subject: 0.46 bump diff --git a/.gitignore b/.gitignore index 81ab018..fa65bcc 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,2 @@ /DateTime-Locale-0.45.tar.gz +/DateTime-Locale-0.46.tar.gz diff --git a/perl-DateTime-Locale.spec b/perl-DateTime-Locale.spec index ab1c9ce..29eaddf 100644 --- a/perl-DateTime-Locale.spec +++ b/perl-DateTime-Locale.spec @@ -1,6 +1,6 @@ Name: perl-DateTime-Locale -Version:0.45 -Release:11%{?dist} +Version:0.46 +Release:1%{?dist} Summary:Localization support for DateTime.pm # package itself is 'same terms as Perl' # modules under DateTime/Locale/ are generated from data provided by the CLDR project @@ -11,26 +11,36 @@ URL:http://search.cpan.org/dist/DateTime-Locale/ Source0: http://www.cpan.org/authors/id/D/DR/DROLSKY/DateTime-Locale-%{version}.tar.gz BuildArch: noarch BuildRequires: glibc-common +# Build BuildRequires: perl -BuildRequires: perl(ExtUtils::MakeMaker) -# Run-time: +BuildRequires: perl(ExtUtils::MakeMaker) = 6.76 +BuildRequires: perl(strict) +BuildRequires: perl(warnings) +# Runtime BuildRequires: perl(base) BuildRequires: perl(Carp) +BuildRequires: perl(Dist::CheckConflicts) = 0.02 BuildRequires: perl(List::MoreUtils) BuildRequires: perl(Params::Validate) = 0.91 -BuildRequires: perl(strict) BuildRequires: perl(utf8) -BuildRequires: perl(warnings) -# Tests: -# File::Find::Rule not used +# Tests only BuildRequires: perl(File::Spec) -BuildRequires: perl(Test::More) +BuildRequires: perl(Test::More) = 0.96 # Optional tests: +BuildRequires: perl(CPAN::Meta) = 2.120900 +BuildRequires: perl(CPAN::Meta::Prereqs) +# XXX: BuildRequires: perl(IO::Handle) +# XXX: BuildRequires: perl(IPC::Open3) +# XXX: BuildRequires: perl(Pod::Wordlist) BuildRequires: perl(Storable) +# XXX: BuildRequires: perl(Test::CPAN::Changes) +# XXX: BuildRequires perl(Test::EOL) +# XXX: BuildRequires: perl(Test::NoTabs) BuildRequires: perl(Test::Output) -# Test::Pod 1.14 not used -# Test::Pod::Coverage 1.04 not used -Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version)) +# XXX: BuildRequires: perl(Test::Pod) = 1.41 +# XXX: BuildRequires: perl(Test::Spelling) = 0.12 +Requires: perl(:MODULE_COMPAT_%(eval $(perl -V:version); echo $version)) +Requires: perl(Dist::CheckConflicts) = 0.02 Requires: perl(Params::Validate) = 0.91 # perl-DateTime-Locale used to be bundled with perl-DateTime # ideally, this would be resolved with @@ -39,8 +49,7 @@ Requires: perl(Params::Validate) = 0.91 # and this would introduce circular build dependencies Conflicts: perl-DateTime = 1:0.7000-3.fc16 -%{?perl_default_filter} -# Remove under-specified dependencies +%global __requires_exclude %{?__requires_exclude:%__requires_exclude|}^perl\\(Dist::CheckConflicts\\)$ %global __requires_exclude %{?__requires_exclude:%__requires_exclude|}^perl\\(Params::Validate\\)$ %description @@ -55,23 +64,26 @@ iconv -f iso-8859-1 -t utf-8 Changes Changes.iconv \ mv -f Changes.iconv Changes %build -perl Makefile.PL INSTALLDIRS=vendor +perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 make %{?_smp_mflags} %install -make pure_install DESTDIR=$RPM_BUILD_ROOT -find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} ';' -%{_fixperms} $RPM_BUILD_ROOT/* +make pure_install DESTDIR=%{buildroot} +%{_fixperms} %{buildroot}/* %check make test %files -%doc Changes LICENSE LICENSE.cldr README +%license LICENSE LICENSE.cldr +%doc Changes README %{perl_vendorlib}/* %{_mandir}/man3/* %changelog +* Wed May 27 2015 Petr Šabata con...@redhat.com - 0.46-1 +- 0.46 bump + * Tue Jan 13 2015 Petr Pisar ppi...@redhat.com - 0.45-11 - Modernize spec file diff --git a/sources b/sources index 812962a..45a2f6e 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -8ba6a4b70f8fa7d987529c2e2c708862 DateTime-Locale-0.45.tar.gz +f60bf58b2e2e29a49d214985fc17adca DateTime-Locale-0.46.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-DateTime-Locale.git/commit/?h=masterid=572ddd7d6b5e375353be7e299dee2b189f577795 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-DateTime-Locale (f22). 0.46 bump
From 572ddd7d6b5e375353be7e299dee2b189f577795 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0abata?= con...@redhat.com Date: Thu, 28 May 2015 11:19:59 +0200 Subject: 0.46 bump diff --git a/.gitignore b/.gitignore index 81ab018..fa65bcc 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,2 @@ /DateTime-Locale-0.45.tar.gz +/DateTime-Locale-0.46.tar.gz diff --git a/perl-DateTime-Locale.spec b/perl-DateTime-Locale.spec index ab1c9ce..29eaddf 100644 --- a/perl-DateTime-Locale.spec +++ b/perl-DateTime-Locale.spec @@ -1,6 +1,6 @@ Name: perl-DateTime-Locale -Version:0.45 -Release:11%{?dist} +Version:0.46 +Release:1%{?dist} Summary:Localization support for DateTime.pm # package itself is 'same terms as Perl' # modules under DateTime/Locale/ are generated from data provided by the CLDR project @@ -11,26 +11,36 @@ URL:http://search.cpan.org/dist/DateTime-Locale/ Source0: http://www.cpan.org/authors/id/D/DR/DROLSKY/DateTime-Locale-%{version}.tar.gz BuildArch: noarch BuildRequires: glibc-common +# Build BuildRequires: perl -BuildRequires: perl(ExtUtils::MakeMaker) -# Run-time: +BuildRequires: perl(ExtUtils::MakeMaker) = 6.76 +BuildRequires: perl(strict) +BuildRequires: perl(warnings) +# Runtime BuildRequires: perl(base) BuildRequires: perl(Carp) +BuildRequires: perl(Dist::CheckConflicts) = 0.02 BuildRequires: perl(List::MoreUtils) BuildRequires: perl(Params::Validate) = 0.91 -BuildRequires: perl(strict) BuildRequires: perl(utf8) -BuildRequires: perl(warnings) -# Tests: -# File::Find::Rule not used +# Tests only BuildRequires: perl(File::Spec) -BuildRequires: perl(Test::More) +BuildRequires: perl(Test::More) = 0.96 # Optional tests: +BuildRequires: perl(CPAN::Meta) = 2.120900 +BuildRequires: perl(CPAN::Meta::Prereqs) +# XXX: BuildRequires: perl(IO::Handle) +# XXX: BuildRequires: perl(IPC::Open3) +# XXX: BuildRequires: perl(Pod::Wordlist) BuildRequires: perl(Storable) +# XXX: BuildRequires: perl(Test::CPAN::Changes) +# XXX: BuildRequires perl(Test::EOL) +# XXX: BuildRequires: perl(Test::NoTabs) BuildRequires: perl(Test::Output) -# Test::Pod 1.14 not used -# Test::Pod::Coverage 1.04 not used -Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version)) +# XXX: BuildRequires: perl(Test::Pod) = 1.41 +# XXX: BuildRequires: perl(Test::Spelling) = 0.12 +Requires: perl(:MODULE_COMPAT_%(eval $(perl -V:version); echo $version)) +Requires: perl(Dist::CheckConflicts) = 0.02 Requires: perl(Params::Validate) = 0.91 # perl-DateTime-Locale used to be bundled with perl-DateTime # ideally, this would be resolved with @@ -39,8 +49,7 @@ Requires: perl(Params::Validate) = 0.91 # and this would introduce circular build dependencies Conflicts: perl-DateTime = 1:0.7000-3.fc16 -%{?perl_default_filter} -# Remove under-specified dependencies +%global __requires_exclude %{?__requires_exclude:%__requires_exclude|}^perl\\(Dist::CheckConflicts\\)$ %global __requires_exclude %{?__requires_exclude:%__requires_exclude|}^perl\\(Params::Validate\\)$ %description @@ -55,23 +64,26 @@ iconv -f iso-8859-1 -t utf-8 Changes Changes.iconv \ mv -f Changes.iconv Changes %build -perl Makefile.PL INSTALLDIRS=vendor +perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 make %{?_smp_mflags} %install -make pure_install DESTDIR=$RPM_BUILD_ROOT -find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} ';' -%{_fixperms} $RPM_BUILD_ROOT/* +make pure_install DESTDIR=%{buildroot} +%{_fixperms} %{buildroot}/* %check make test %files -%doc Changes LICENSE LICENSE.cldr README +%license LICENSE LICENSE.cldr +%doc Changes README %{perl_vendorlib}/* %{_mandir}/man3/* %changelog +* Wed May 27 2015 Petr Šabata con...@redhat.com - 0.46-1 +- 0.46 bump + * Tue Jan 13 2015 Petr Pisar ppi...@redhat.com - 0.45-11 - Modernize spec file diff --git a/sources b/sources index 812962a..45a2f6e 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -8ba6a4b70f8fa7d987529c2e2c708862 DateTime-Locale-0.45.tar.gz +f60bf58b2e2e29a49d214985fc17adca DateTime-Locale-0.46.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-DateTime-Locale.git/commit/?h=f22id=572ddd7d6b5e375353be7e299dee2b189f577795 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1225050] perl-DateTime-Locale-0.46 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225050 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-DateTime-Locale-0.46-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/perl-DateTime-Locale-0.46-1.fc22 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Including tlp in Fedora Workstation by default
On Thu, May 28, 2015 at 12:16 PM, Richard Hughes hughsi...@gmail.com wrote: On 28 May 2015 at 10:45, Nadim Kobeissi nadim@nadim.computer wrote: I would like to suggest that tlp [0] be included with Fedora Workstation by default, starting with Fedora 23. Why can't we just use the correct defaults? Having a configure all the things version of powertop isn't going to help anybody but the power users. This stuff should just work out of the box. There are lots of reasons why some things like USB autosuspend are not enabled by default (sound cards clicking) and ALPM on some chipsets is disabled (risk of disk corruption) and I'd much rather fix the bugs in the kernel than add a whole heap of userspace config options. Seeing options for the CPU scaling governor and CPU undervolting really doesn't make me feel great about this new package installed by default. I understand and appreciate your perspective. I have two counter-arguments, although I do admit they do not fully answer your concern. 1: My understanding is that tlp ships with a default configuration that, without any modification, will enable reasonable settings for power saving. We can just have tlp start on boot with this configuration. This will benefit everyone, not just power users, without any weird or dangerous config tweaks being necessary. If you believe that the default configuration has unsavory settings (for example, if we find that it causes sound card clicking), then the Fedora package can modify these defaults accordingly while keeping the things we like and consider safe. 2: I think anyone will reasonably agree that the Linux kernel should simply be better. But until we're there, perhaps we should consider tlp as a reasonable solution, even if it's a short-term one? We shouldn't inhibit progressively better Fedora user experience until the kernel is perfect; this would mean years of waiting for regular users. Thanks for your response. Nadim Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1225049] perl-SQL-Statement-1.407 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225049 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-SQL-Statement-1.407-1. ||fc23 Resolution|--- |RAWHIDE Last Closed||2015-05-28 06:20:51 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-Module-ScanDeps (master). 1.19 bump
From d09f89c2ff1c3279184625c9c1892adbbd8a7854 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0abata?= con...@redhat.com Date: Thu, 28 May 2015 13:49:20 +0200 Subject: 1.19 bump diff --git a/perl-Module-ScanDeps.spec b/perl-Module-ScanDeps.spec index 3788122..400db97 100644 --- a/perl-Module-ScanDeps.spec +++ b/perl-Module-ScanDeps.spec @@ -1,6 +1,6 @@ Name: perl-Module-ScanDeps Summary:Recursively scan Perl code for dependencies -Version:1.18 +Version:1.19 Release:1%{?dist} License:GPL+ or Artistic Group: Development/Libraries @@ -8,7 +8,7 @@ Source0: http://search.cpan.org/CPAN/authors/id/R/RS/RSCHUPP/Module-ScanD URL:http://search.cpan.org/dist/Module-ScanDeps/ BuildArch: noarch BuildRequires: perl -BuildRequires: perl(ExtUtils::MakeMaker) +BuildRequires: perl(ExtUtils::MakeMaker) = 6.76 BuildRequires: perl(ExtUtils::MM_Unix) BuildRequires: perl(FindBin) BuildRequires: perl(Fcntl) @@ -66,12 +66,11 @@ Test/More.pm). The values are hash references. %setup -q -n Module-ScanDeps-%{version} %build -perl Makefile.PL INSTALLDIRS=vendor +perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 make %{?_smp_mflags} %install make pure_install DESTDIR=%{buildroot} -find %{buildroot} -type f -name .packlist -exec rm -f {} + %{_fixperms} %{buildroot} %check @@ -85,6 +84,9 @@ make test %{_mandir}/man3/Module::ScanDeps.3pm* %changelog +* Thu May 28 2015 Petr Šabata con...@redhat.com - 1.19-1 +- 1.19 bump + * Fri Jan 30 2015 Petr Šabata con...@redhat.com - 1.18-1 - 1.18 bump diff --git a/sources b/sources index fc53721..05a1eb4 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -3e621c9d42ef7e8277d33caf747f7746 Module-ScanDeps-1.18.tar.gz +ea2545dbf46bae4cc43d9d07cad77b96 Module-ScanDeps-1.19.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-Module-ScanDeps.git/commit/?h=masterid=d09f89c2ff1c3279184625c9c1892adbbd8a7854 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata uploaded Module-ScanDeps-1.19.tar.gz for perl-Module-ScanDeps
ea2545dbf46bae4cc43d9d07cad77b96 Module-ScanDeps-1.19.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Module-ScanDeps/Module-ScanDeps-1.19.tar.gz/ea2545dbf46bae4cc43d9d07cad77b96/Module-ScanDeps-1.19.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Including tlp in Fedora Workstation by default
Hi, I would like to suggest that tlp [0] be included with Fedora Workstation by default, starting with Fedora 23. tlp is already a well-maintained Fedora package [1], is quite stable, and achieves dramatic battery life and laptop optimization gains without having to run a daemon or a background process. It also ships with informative stat tools. It seems to be the current leader in zero-configuration laptop performance optimization, and is extremely lightweight. Since Fedora Workstation ships with NetworkManager, the helper package tlp-rdw should also be included [2]. It seems like integrating the existing Fedora package as a default in Fedora Workstation shipments should be a no-brainer. Why isn't this already the case? Can we make this happen? Thanks, Nadim [0] http://www.linrunner.de/en/tlp/tlp.html [1] https://apps.fedoraproject.org/packages/tlp [2] https://apps.fedoraproject.org/packages/tlp-rdw -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
psabata pushed to perl-SQL-Statement (master). 1.407 bump
From d3ffaacee86ba1b739c294e4d7997217caec393f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0abata?= con...@redhat.com Date: Thu, 28 May 2015 12:18:02 +0200 Subject: 1.407 bump diff --git a/.gitignore b/.gitignore index a53a4f0..a791ffc 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,4 @@ SQL-Statement-1.27.tar.gz /SQL-Statement-1.402.tar.gz /SQL-Statement-1.404.tar.gz /SQL-Statement-1.405.tar.gz +/SQL-Statement-1.407.tar.gz diff --git a/perl-SQL-Statement.spec b/perl-SQL-Statement.spec index 80c3bb4..29e5822 100644 --- a/perl-SQL-Statement.spec +++ b/perl-SQL-Statement.spec @@ -1,44 +1,48 @@ Name: perl-SQL-Statement -Version:1.405 -Release:9%{?dist} +Version:1.407 +Release:1%{?dist} Summary:SQL parsing and processing engine Group: Development/Libraries License:GPL+ or Artistic URL:http://search.cpan.org/dist/SQL-Statement/ Source0: http://www.cpan.org/authors/id/R/RE/REHSACK/SQL-Statement-%{version}.tar.gz BuildArch: noarch +# Build BuildRequires: perl -BuildRequires: perl(ExtUtils::MakeMaker) +BuildRequires: perl(ExtUtils::MakeMaker) = 6.76 BuildRequires: perl(strict) BuildRequires: perl(warnings) -# Run-time: +# Runtime BuildRequires: perl(base) BuildRequires: perl(Carp) BuildRequires: perl(Clone) = 0.30 BuildRequires: perl(constant) BuildRequires: perl(Data::Dumper) -BuildRequires: perl(DBI) = 1.612 +BuildRequires: perl(DBI) = 1.616 BuildRequires: perl(Encode) BuildRequires: perl(Errno) BuildRequires: perl(Exporter) BuildRequires: perl(List::Util) -BuildRequires: perl(Math::BigFloat) -BuildRequires: perl(Math::BigInt) +BuildRequires: perl(Math::Base::Convert) BuildRequires: perl(Math::Trig) +BuildRequires: perl(Module::Runtime) BuildRequires: perl(Params::Util) = 1.00 BuildRequires: perl(Scalar::Util) = 1.0 +# XXX: BuildRequires: perl(SQL::UserDefs) BuildRequires: perl(sort) +BuildRequires: perl(Text::Balanced) BuildRequires: perl(Text::Soundex) BuildRequires: perl(Time::HiRes) BuildRequires: perl(vars) -# Tests: +# Tests only BuildRequires: perl(Cwd) BuildRequires: perl(File::Basename) BuildRequires: perl(File::Path) BuildRequires: perl(File::Spec) BuildRequires: perl(lib) +BuildRequires: perl(Test::Deep) BuildRequires: perl(Test::More) -# Optional test: +# Optional tests only # DBD::CSV buildrequires SQL::Statement %if 0%{!?perl_bootstrap:1} BuildRequires: perl(DBD::CSV) = 0.30 @@ -47,11 +51,14 @@ BuildRequires: perl(DBD::DBM) = 0.06 BuildRequires: perl(DBD::File) = 0.40 BuildRequires: perl(DBD::SQLite) BuildRequires: perl(MLDBM) -Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version)) +Requires: perl(:MODULE_COMPAT_%(eval $(perl -V:version); echo $version)) Requires: perl(Clone) = 0.30 -Requires: perl(DBI) = 1.612 +Requires: perl(DBI) = 1.616 +Requires: perl(Math::Base::Convert) Requires: perl(Params::Util) = 1.00 Requires: perl(Scalar::Util) = 1.0 +# This module doesn't seem to exist... +# XXX: Requires: perl(SQL::UserDefs) Requires: perl(Text::Soundex) %global __requires_exclude %{?__requires_exclude:%__requires_exclude|}^perl\\((Clone|Params::Util|Scalar::Util)\\)$ @@ -70,12 +77,11 @@ sed -i -e 's/\r//' README %build export SQL_STATEMENT_WARN_UPDATE=sure -perl Makefile.PL INSTALLDIRS=vendor +perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 make %{?_smp_mflags} %install make pure_install DESTDIR=%{buildroot} -find %{buildroot} -type f -name .packlist -exec rm -f {} ';' chmod -R u+w %{buildroot}/* %check @@ -87,6 +93,9 @@ make test %{_mandir}/man3/*.3pm* %changelog +* Tue May 26 2015 Petr Šabata con...@redhat.com - 1.407-1 +- 1.407 bump + * Sun Sep 07 2014 Jitka Plesnikova jples...@redhat.com - 1.405-9 - Perl 5.20 re-rebuild of bootstrapped packages diff --git a/sources b/sources index 8cd8648..0b15cc1 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -22231c2e28996b5bfea9925d49c11de1 SQL-Statement-1.405.tar.gz +abeedda4a2c085613cb77fb01631e5de SQL-Statement-1.407.tar.gz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-SQL-Statement.git/commit/?h=masterid=d3ffaacee86ba1b739c294e4d7997217caec393f -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
jplesnik pushed to perl-DBIx-Class (master). Disable optional BR perl(Devel::FindRef)
From 45e902677fc6ae4003d83dd79270a3e2b0436d56 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova jples...@redhat.com Date: Thu, 28 May 2015 12:34:36 +0200 Subject: Disable optional BR perl(Devel::FindRef) diff --git a/perl-DBIx-Class.spec b/perl-DBIx-Class.spec index 3e3fd41..b01e9da 100644 --- a/perl-DBIx-Class.spec +++ b/perl-DBIx-Class.spec @@ -1,7 +1,7 @@ Name: perl-DBIx-Class Summary:Extensible and flexible object - relational mapper Version:0.082810 -Release:2%{?dist} +Release:3%{?dist} License:GPL+ or Artistic Group: Development/Libraries Source0: http://search.cpan.org/CPAN/authors/id/R/RI/RIBASUSHI/DBIx-Class-%{version}.tar.gz @@ -104,7 +104,7 @@ BuildRequires: perl(DateTime::Format::Pg) BuildRequires: perl(DateTime::Format::SQLite) BuildRequires: perl(DBD::Pg) BuildRequires: perl(DBD::SQLite) -BuildRequires: perl(Devel::FindRef) +# Optional for TEST_VERBOSE: BuildRequires: perl(Devel::FindRef) BuildRequires: perl(Errno) BuildRequires: perl(File::Compare) BuildRequires: perl(File::Temp) @@ -297,6 +297,9 @@ make test %{_mandir}/man[13]/* %changelog +* Thu May 28 2015 Jitka Plesnikova jples...@redhat.com - 0.082810-3 +- Disable optional BR perl(Devel::FindRef) + * Mon Dec 08 2014 Petr Šabata con...@redhat.com - 0.082810-2 - Explicitly provide modules I missed before, hopefully that's all this time -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-DBIx-Class.git/commit/?h=masterid=45e902677fc6ae4003d83dd79270a3e2b0436d56 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Including tlp in Fedora Workstation by default
On 28 May 2015 at 11:21, Nadim Kobeissi nadim@nadim.computer wrote: 1: My understanding is that tlp ships with a default configuration that, without any modification, will enable reasonable settings for power saving. I think what the kernel is providing is reasonable, from a regression / feature point of view. I agree some of the kconfig options could be modified in a few cases, although this is the pain when we have a single kernel for all the different products. then the Fedora package can modify these defaults accordingly while keeping the things we like and consider safe. Do you think that the average user with a clicking sound card or disk corruption when suspending would be able to make the link to this new package? We shouldn't inhibit progressively better Fedora user experience until the kernel is perfect; this would mean years of waiting for regular users. We shouldn't paper over the cracks. I've seen that again and again and it just stops being maintainable after a few years. Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Including tlp in Fedora Workstation by default
On 28 May 2015 at 10:45, Nadim Kobeissi nadim@nadim.computer wrote: I would like to suggest that tlp [0] be included with Fedora Workstation by default, starting with Fedora 23. Why can't we just use the correct defaults? Having a configure all the things version of powertop isn't going to help anybody but the power users. This stuff should just work out of the box. There are lots of reasons why some things like USB autosuspend are not enabled by default (sound cards clicking) and ALPM on some chipsets is disabled (risk of disk corruption) and I'd much rather fix the bugs in the kernel than add a whole heap of userspace config options. Seeing options for the CPU scaling governor and CPU undervolting really doesn't make me feel great about this new package installed by default. Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1225476] perl-Module-ScanDeps-1.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225476 --- Comment #3 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- psabata's perl-Module-ScanDeps-1.19-1.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=639554 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1219989] perl-Finance-YahooQuote 0.25 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219989 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|0.25-1 |perl-Finance-YahooQuote-0.2 ||5-1.fc21 Resolution|--- |ERRATA Last Closed||2015-05-28 07:59:02 --- Comment #10 from Fedora Update System upda...@fedoraproject.org --- perl-Finance-YahooQuote-0.25-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
jplesnik pushed to perl-XML-TreeBuilder (master). Update list of build-requires and requires
From 6ef1040b7266400a5d85248685e497dafca6ea95 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova jples...@redhat.com Date: Thu, 28 May 2015 14:04:49 +0200 Subject: Update list of build-requires and requires diff --git a/perl-XML-TreeBuilder.spec b/perl-XML-TreeBuilder.spec index ac69085..524584d 100644 --- a/perl-XML-TreeBuilder.spec +++ b/perl-XML-TreeBuilder.spec @@ -1,7 +1,7 @@ Summary: Parser that builds a tree of XML::Element objects Name: perl-XML-TreeBuilder Version: 5.4 -Release: 1%{?dist} +Release: 2%{?dist} License: GPL+ or Artistic Group: Development/Libraries URL: http://search.cpan.org/dist/XML-TreeBuilder/ @@ -11,19 +11,23 @@ Source: http://www.cpan.org/modules/by-module/XML/XML-TreeBuilder-%{version}.ta BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root%(%{__id_u} -n) BuildArch: noarch BuildRequires: perl +BuildRequires: perl(Carp) +BuildRequires: perl(File::Basename) +BuildRequires: perl(File::Spec) BuildRequires: perl(HTML::Element) = 4.1 BuildRequires: perl(HTML::Tagset) +BuildRequires: perl(Module::Build) +BuildRequires: perl(strict) +BuildRequires: perl(Test) +BuildRequires: perl(Test::More) +BuildRequires: perl(Test::Pod) = 1.14 +BuildRequires: perl(Test::Pod::Coverage) = 1.04 +BuildRequires: perl(Test::Perl::Critic) +BuildRequires: perl(vars) +BuildRequires: perl(warnings) +BuildRequires: perl(XML::Catalog) = 1.02 BuildRequires: perl(XML::Parser) -BuildRequires: perl(XML::Catalog) = 1.0.0 -BuildRequires: perl(Devel::Cover) -BuildRequires: perl(Module::Build) -BuildRequires: perl(Test::Exception) -BuildRequires: perl(Test::More) -BuildRequires: perl(Test::Pod) -BuildRequires: perl(Test::Pod::Coverage) -BuildRequires: perl(Test::Perl::Critic) Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version)) -Requires: perl(HTML::Element) perl(HTML::Tagset) perl(XML::Parser) %description perl-XML-TreeBuilder is a Perl module that implements a parser @@ -54,6 +58,9 @@ find $RPM_BUILD_ROOT -type d -depth -exec rmdir {} 2/dev/null ';' %{perl_vendorlib}/XML/ %changelog +* Thu May 28 2015 Jitka Plesnikova jples...@redhat.com - 5.4-2 +- Update list of build-requires and requires + * Fri Aug 29 2014 Jitka Plesnikova jples...@redhat.com - 5.4-1 - Perl 5.20 rebuild -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-XML-TreeBuilder.git/commit/?h=masterid=6ef1040b7266400a5d85248685e497dafca6ea95 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Including tlp in Fedora Workstation by default
On Thu, 2015-05-28 at 11:57 +0100, Richard Hughes wrote: On 28 May 2015 at 11:21, Nadim Kobeissi nadim@nadim.computer wrote: 1: My understanding is that tlp ships with a default configuration that, without any modification, will enable reasonable settings for power saving. I think what the kernel is providing is reasonable, from a regression / feature point of view. I agree some of the kconfig options could be modified in a few cases, although this is the pain when we have a single kernel for all the different products. Actually, it *does* sound like this package might provide a way to mitigate that situation (single kernel). If tlp can accept a configuration file for what tweaks to make, then we can use the per -product config feature to allow us to set certain features differently on Workstation compared to Server/Cloud or non-product. (This would still probably mean shipping things like the USB autosuspend disabled, due to the other effects it can have). Also, it's possible in the Fedora package to ship this tool without the GUI (or at least, separate the GUI into a subpackage which isn't installed by default, similar to how we do things with Epiphany). If we don't *expose* these as options, but instead use the package to tweak our defaults, would that provide some benefit here? signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
RFC: LiveUSB Creator Revamped
Hi everyone, for quite a while, I've been working on implementation of a new, revamped UI, designed by Jakub Steiner for the LiveUSB Creator [0]. Currently, me and Luke are slowly moving to merge the changes back into the master branch of the tree. Some stuff is not done, like descriptions of the images or final look of the icons but the really important things are already there. I'm writing here to ask you guys for input on what you think about how it looks like now. I've set up a Copr repository [1] and put a Windows package together [2]. I'm open to all kinds of feature requests, bug reports, any kind of input that comes to your minds. The Copr version still contains just udisks support. Udisks2 will be added ASAP (when I rebase my branch against master and build the package again). Specifically, what we'd love to settle is: what to do with the main screen with the three promoted images. Obviously, putting a Server or Cloud Product on a USB drive is a nonsense. One could argue the tool at least downloads the images for you, though. Cheers, Martin [0] https://github.com/lmacken/liveusb-creator/tree/feature/new-ui [1] https://copr.fedoraproject.org/coprs/mbriza/unstable/build/94636/ [2a] https://mbriza.fedorapeople.org/liveusb-creator.zip [2b] http://ma.rtinbriza.cz/w/liveusb-creator.zip -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1219989] perl-Finance-YahooQuote 0.25 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219989 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|perl-Finance-YahooQuote-0.2 |perl-Finance-YahooQuote-0.2 |5-1.fc21|5-1.fc20 --- Comment #11 from Fedora Update System upda...@fedoraproject.org --- perl-Finance-YahooQuote-0.25-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: RFC: LiveUSB Creator Revamped
On Thu, 28 May 2015 14:28:17 +0200, Martin Bříza mbr...@redhat.com wrote: Hi everyone, for quite a while, I've been working on implementation of a new, revamped UI, designed by Jakub Steiner for the LiveUSB Creator [0]. Currently, me and Luke are slowly moving to merge the changes back into the master branch of the tree. Some stuff is not done, like descriptions of the images or final look of the icons but the really important things are already there. I'm writing here to ask you guys for input on what you think about how it looks like now. I've set up a Copr repository [1] and put a Windows package together [2]. I'm open to all kinds of feature requests, bug reports, any kind of input that comes to your minds. The Copr version still contains just udisks support. Udisks2 will be added ASAP (when I rebase my branch against master and build the package again). Specifically, what we'd love to settle is: what to do with the main screen with the three promoted images. Obviously, putting a Server or Cloud Product on a USB drive is a nonsense. One could argue the tool at least downloads the images for you, though. Cheers, Martin [0] https://github.com/lmacken/liveusb-creator/tree/feature/new-ui [1] https://copr.fedoraproject.org/coprs/mbriza/unstable/build/94636/ [2a] https://mbriza.fedorapeople.org/liveusb-creator.zip [2b] http://ma.rtinbriza.cz/w/liveusb-creator.zip Also, to see it without actually installing it, there's just a little bit outdated screencap: https://mbriza.fedorapeople.org/liveusb-6.ogv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: RFC: LiveUSB Creator Revamped
On Thu, 2015-05-28 at 14:31 +0200, Martin Bříza wrote: Also, to see it without actually installing it, there's just a little bit outdated screencap: https://mbriza.fedorapeople.org/liveusb-6.ogv That looks quite good! I have just one comment: the Back, Write to USB disk, Cancel, and Write to disk buttons belong in a header bar, at least when running in GNOME. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: RFC: LiveUSB Creator Revamped
It's not nonsense to be able to put Server Product on USB. I've installed Fedora Server on servers that way myself. Not so sure about Cloud images, though. Those generally get uploaded to somewhere else to be used. On Thu, May 28, 2015 at 8:31 AM, Martin Bříza mbr...@redhat.com wrote: On Thu, 28 May 2015 14:28:17 +0200, Martin Bříza mbr...@redhat.com wrote: Hi everyone, for quite a while, I've been working on implementation of a new, revamped UI, designed by Jakub Steiner for the LiveUSB Creator [0]. Currently, me and Luke are slowly moving to merge the changes back into the master branch of the tree. Some stuff is not done, like descriptions of the images or final look of the icons but the really important things are already there. I'm writing here to ask you guys for input on what you think about how it looks like now. I've set up a Copr repository [1] and put a Windows package together [2]. I'm open to all kinds of feature requests, bug reports, any kind of input that comes to your minds. The Copr version still contains just udisks support. Udisks2 will be added ASAP (when I rebase my branch against master and build the package again). Specifically, what we'd love to settle is: what to do with the main screen with the three promoted images. Obviously, putting a Server or Cloud Product on a USB drive is a nonsense. One could argue the tool at least downloads the images for you, though. Cheers, Martin [0] https://github.com/lmacken/liveusb-creator/tree/feature/new-ui [1] https://copr.fedoraproject.org/coprs/mbriza/unstable/build/94636/ [2a] https://mbriza.fedorapeople.org/liveusb-creator.zip [2b] http://ma.rtinbriza.cz/w/liveusb-creator.zip Also, to see it without actually installing it, there's just a little bit outdated screencap: https://mbriza.fedorapeople.org/liveusb-6.ogv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 真実はいつも一つ!/ Always, there's only one truth! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: RFC: LiveUSB Creator Revamped
On Thu, 2015-05-28 at 14:31 +0200, Martin Bříza wrote: On Thu, 28 May 2015 14:28:17 +0200, Martin Bříza mbr...@redhat.com wrote: Hi everyone, for quite a while, I've been working on implementation of a new, revamped UI, designed by Jakub Steiner for the LiveUSB Creator [0]. Currently, me and Luke are slowly moving to merge the changes back into the master branch of the tree. Some stuff is not done, like descriptions of the images or final look of the icons but the really important things are already there. I'm writing here to ask you guys for input on what you think about how it looks like now. I've set up a Copr repository [1] and put a Windows package together [2]. I'm open to all kinds of feature requests, bug reports, any kind of input that comes to your minds. The Copr version still contains just udisks support. Udisks2 will be added ASAP (when I rebase my branch against master and build the package again). Specifically, what we'd love to settle is: what to do with the main screen with the three promoted images. Obviously, putting a Server or Cloud Product on a USB drive is a nonsense. One could argue the tool at least downloads the images for you, though. Cheers, Martin [0] https://github.com/lmacken/liveusb-creator/tree/feature/new-ui [1] https://copr.fedoraproject.org/coprs/mbriza/unstable/build/94636/ [2a] https://mbriza.fedorapeople.org/liveusb-creator.zip [2b] http://ma.rtinbriza.cz/w/liveusb-creator.zip Also, to see it without actually installing it, there's just a little bit outdated screencap: https://mbriza.fedorapeople.org/liveusb-6.ogv It looks neat! A few notes: 1.) There's no scrollbar to scroll the list. It only appears upon scrolling with a mouse wheel which is kind of useless. 2.) It would be nice if the release list was configurable (think /usr/lib/liveusb-creator/releases.d + /etc/liveusb-creator/releases.d instead of hardcoded in releases.py). That way the default installations could bring in the Fedora distributions while an add-on packages could add CentOS, RPM Fusion, etc. 3.) I've launched liveusb-creator_polkit. However it doesn't seem to employ policykit -- the UI itself runs as root! The inconvenient side -effect is that the file picker is not entirely relevant and I have hard time finding the ISO file I've downloaded. 4.) The dependency on udisks is missing and the error is not handled gracefully. The following tracebacks appears on the console: Traceback (most recent call last): File /usr/lib/python2.7/site-packages/liveusb/gui.py, line 830, in USBDeviceEnumerationStart self.live.detect_removable_drives(callback=self.USBDeviceCallback) File /usr/lib/python2.7/site-packages/liveusb/creator.py, line 519, in detect_removable_drives /org/freedesktop/UDisks) File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File /usr/lib64/python2.7/site-packages/dbus/proxies.py, line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 180, in activate_name_owner self.start_service_by_name(bus_name) File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 278, in start_service_by_name 'su', (bus_name, flags))) File /usr/lib64/python2.7/site-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UDisks was not provided by any .service files The UI is just not able to find the flash drive. 5.) The error handling seems messed up. When I hit the write button, there's no error in the UI, but the following is in the console: [gui:246] (u'T', u'h', u'e', u'r', u'e', u' ', u'i', u's', u' ', u'n', u'o', u't', u' ', u'e', u'n', u'o', u'u', u'g', u'h', u' ', u'f', u'r', u'e', u'e', u' ', u's', u'p', u'a', u'c', u'e', u' ', u'o', u'n', u' ', u't', u'h', u'e', u' ', u's', u'e', u'l', u'e', u'c', u't', u'e', u'd', u' ', u'd', u'e', u'v', u'i', u'c', u'e', u'.', u' ', u'R', u'e', u'q', u'u', u'i', u'r', u'e', u'd', u':', u' ', u'1', u'0', u'5', u'6', u'M', u'B', u'.', u' ', u'F', u'r', u'e', u'e', u':', u' ', u'7', u'0', u'2', u'M', u'B', u'.') Traceback (most recent call last): File /usr/lib/python2.7/site-packages/liveusb/gui.py, line 243, in run self.copyImage(now) File /usr/lib/python2.7/site-packages/liveusb/gui.py, line 265, in copyImage self.live.check_free_space() File /usr/lib/python2.7/site-packages/liveusb/creator.py, line 263, in check_free_space str(freebytes/1024**2) + MB))) LiveUSBError: (u'T', u'h', u'e', u'r', u'e', u' ', u'i', u's', u' ', u'n', u'o', u't', u' ', u'e', u'n', u'o', u'u', u'g', u'h', u' ', u'f', u'r', u'e', u'e', u' ', u's', u'p', u'a', u'c', u'e', u' ', u'o', u'n', u' ', u't',
Re: RFC: LiveUSB Creator Revamped
On 05/28/2015 07:36 AM, Neal Gompa wrote: It's not nonsense to be able to put Server Product on USB. I've installed Fedora Server on servers that way myself. Not so sure about Cloud images, though. Those generally get uploaded to somewhere else to be used. On Thu, May 28, 2015 at 8:31 AM, Martin Bříza mbr...@redhat.com mailto:mbr...@redhat.com wrote: On Thu, 28 May 2015 14:28:17 +0200, Martin Bříza mbr...@redhat.com mailto:mbr...@redhat.com wrote: Hi everyone, for quite a while, I've been working on implementation of a new, revamped UI, designed by Jakub Steiner for the LiveUSB Creator [0]. Currently, me and Luke are slowly moving to merge the changes back into the master branch of the tree. Some stuff is not done, like descriptions of the images or final look of the icons but the really important things are already there. I'm writing here to ask you guys for input on what you think about how it looks like now. I've set up a Copr repository [1] and put a Windows package together [2]. I'm open to all kinds of feature requests, bug reports, any kind of input that comes to your minds. The Copr version still contains just udisks support. Udisks2 will be added ASAP (when I rebase my branch against master and build the package again). Specifically, what we'd love to settle is: what to do with the main screen with the three promoted images. Obviously, putting a Server or Cloud Product on a USB drive is a nonsense. One could argue the tool at least downloads the images for you, though. Cheers, Martin [0] https://github.com/lmacken/liveusb-creator/tree/feature/new-ui [1] https://copr.fedoraproject.org/coprs/mbriza/unstable/build/94636/ [2a] https://mbriza.fedorapeople.org/liveusb-creator.zip [2b] http://ma.rtinbriza.cz/w/liveusb-creator.zip Also, to see it without actually installing it, there's just a little bit outdated screencap: https://mbriza.fedorapeople.org/liveusb-6.ogv Server should remain as a choice - that is a common use case for USB drives as Neal stated. I would suggest that Cloud be replaced with Plasma, but I don't know that Plasma has an official Fedora logo in line with the Product logos. Dan -- Dan Mossor, RHCSA Systems Engineer Fedora Server WG | Fedora KDE WG | Fedora QA Team Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: RFC: LiveUSB Creator Revamped
Michael Catanzaro píše v Čt 28. 05. 2015 v 07:55 -0500: On Thu, 2015-05-28 at 14:31 +0200, Martin Bříza wrote: Also, to see it without actually installing it, there's just a little bit outdated screencap: https://mbriza.fedorapeople.org/liveusb-6.ogv That looks quite good! I have just one comment: the Back, Write to USB disk, Cancel, and Write to disk buttons belong in a header bar, at least when running in GNOME. It's written in QML and I don't think something like header bar and CSD is possible there. Jiri -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
limb created the branch 'epel7' for the package 'perl-File-RsyncP'
limb created the branch 'epel7' for the package 'perl-File-RsyncP' https://admin.fedoraproject.org/pkgdb/package/perl-File-RsyncP/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
jplesnik pushed to perl-GraphViz (master). 2.18 bump
From cb939630506bb972f5c2092ce06b16b980f937d1 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova jples...@redhat.com Date: Thu, 28 May 2015 15:37:59 +0200 Subject: 2.18 bump diff --git a/.gitignore b/.gitignore index 6966934..ae21461 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,3 @@ /GraphViz-2.14.tgz /GraphViz-2.16.tgz +/GraphViz-2.18.tgz diff --git a/perl-GraphViz.spec b/perl-GraphViz.spec index c25c470..67e441b 100644 --- a/perl-GraphViz.spec +++ b/perl-GraphViz.spec @@ -1,8 +1,8 @@ Name: perl-GraphViz -Version:2.16 +Version:2.18 Release:1%{?dist} Summary:Interface to the GraphViz graphing tool -License:GPL+ or Artistic +License:Artistic 2.0 Group: Development/Libraries URL:http://search.cpan.org/dist/GraphViz/ Source0: http://www.cpan.org/authors/id/R/RS/RSAVAGE/GraphViz-%{version}.tgz @@ -23,7 +23,7 @@ BuildRequires: perl(LWP::Simple) = 6 BuildRequires: perl(Parse::RecDescent) = 1.965001 BuildRequires: perl(Pod::Usage) = 1.16 BuildRequires: perl(strict) -BuildRequires: perl(Test::More) +BuildRequires: perl(Test::More) = 1.001014 BuildRequires: perl(Time::HiRes) = 1.51 BuildRequires: perl(vars) BuildRequires: perl(warnings) @@ -65,11 +65,15 @@ find %{buildroot} -type f -name .packlist -exec rm -f {} \; make test %files +%license LICENSE %doc Changes README examples/ %{perl_vendorlib}/* %{_mandir}/man3/* %changelog +* Thu May 28 2015 Jitka Plesnikova jples...@redhat.com - 2.18-1 +- 2.18 bump + * Wed Nov 12 2014 Jitka Plesnikova jples...@redhat.com - 2.16-1 - 2.16 bump - Modernize spec file diff --git a/sources b/sources index edd9d3d..8be93ea 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -45954ab14ed5e5d2af0d7edaf982c927 GraphViz-2.16.tgz +cd507325c0bbfcc168a034abaf60a12b GraphViz-2.18.tgz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-GraphViz.git/commit/?h=masterid=cb939630506bb972f5c2092ce06b16b980f937d1 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
jplesnik uploaded GraphViz-2.18.tgz for perl-GraphViz
cd507325c0bbfcc168a034abaf60a12b GraphViz-2.18.tgz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-GraphViz/GraphViz-2.18.tgz/cd507325c0bbfcc168a034abaf60a12b/GraphViz-2.18.tgz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
jplesnik pushed to perl-GraphViz (f22). 2.18 bump
From 0f086d8492452dc86ce15826322ccb9e9a934638 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova jples...@redhat.com Date: Thu, 28 May 2015 15:45:29 +0200 Subject: 2.18 bump diff --git a/.gitignore b/.gitignore index 6966934..ae21461 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,3 @@ /GraphViz-2.14.tgz /GraphViz-2.16.tgz +/GraphViz-2.18.tgz diff --git a/perl-GraphViz.spec b/perl-GraphViz.spec index c25c470..67e441b 100644 --- a/perl-GraphViz.spec +++ b/perl-GraphViz.spec @@ -1,8 +1,8 @@ Name: perl-GraphViz -Version:2.16 +Version:2.18 Release:1%{?dist} Summary:Interface to the GraphViz graphing tool -License:GPL+ or Artistic +License:Artistic 2.0 Group: Development/Libraries URL:http://search.cpan.org/dist/GraphViz/ Source0: http://www.cpan.org/authors/id/R/RS/RSAVAGE/GraphViz-%{version}.tgz @@ -23,7 +23,7 @@ BuildRequires: perl(LWP::Simple) = 6 BuildRequires: perl(Parse::RecDescent) = 1.965001 BuildRequires: perl(Pod::Usage) = 1.16 BuildRequires: perl(strict) -BuildRequires: perl(Test::More) +BuildRequires: perl(Test::More) = 1.001014 BuildRequires: perl(Time::HiRes) = 1.51 BuildRequires: perl(vars) BuildRequires: perl(warnings) @@ -65,11 +65,15 @@ find %{buildroot} -type f -name .packlist -exec rm -f {} \; make test %files +%license LICENSE %doc Changes README examples/ %{perl_vendorlib}/* %{_mandir}/man3/* %changelog +* Thu May 28 2015 Jitka Plesnikova jples...@redhat.com - 2.18-1 +- 2.18 bump + * Wed Nov 12 2014 Jitka Plesnikova jples...@redhat.com - 2.16-1 - 2.16 bump - Modernize spec file diff --git a/sources b/sources index edd9d3d..8be93ea 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -45954ab14ed5e5d2af0d7edaf982c927 GraphViz-2.16.tgz +cd507325c0bbfcc168a034abaf60a12b GraphViz-2.18.tgz -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-GraphViz.git/commit/?h=f22id=0f086d8492452dc86ce15826322ccb9e9a934638 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1225675] perl-GraphViz-2.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225675 --- Comment #3 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- jplesnik's perl-GraphViz-2.18-1.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=639624 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1225675] perl-GraphViz-2.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225675 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-GraphViz-2.18-1.fc23 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1225675] perl-GraphViz-2.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225675 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-GraphViz-2.18-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/perl-GraphViz-2.18-1.fc22 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
limb changed psabata's 'commit' permission on perl-File-RsyncP (epel7) to 'Approved'
limb changed psabata's 'commit' permission on perl-File-RsyncP (epel7) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-RsyncP/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
limb changed psabata's 'watchcommits' permission on perl-File-RsyncP (epel7) to 'Approved'
limb changed psabata's 'watchcommits' permission on perl-File-RsyncP (epel7) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-RsyncP/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
limb changed psabata's 'approveacls' permission on perl-File-RsyncP (epel7) to 'Approved'
limb changed psabata's 'approveacls' permission on perl-File-RsyncP (epel7) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-RsyncP/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
limb changed psabata's 'watchbugzilla' permission on perl-File-RsyncP (epel7) to 'Approved'
limb changed psabata's 'watchbugzilla' permission on perl-File-RsyncP (epel7) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-RsyncP/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Including tlp in Fedora Workstation by default
On Thu, May 28, 2015 at 02:18:21PM +0200, Florian Weimer wrote: Doesn't tuned already do something similar to this? These are the exact words I just typed in another message. :) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 22 Dispplay with stripes
2015-05-27 13:16 GMT-03:00 Ralf Corsepius rc040...@freenet.de: On 05/27/2015 05:27 PM, Sergio Belkin wrote: Video card: Slot: 00:02.0 Class: VGA compatible controller Vendor: Intel Corporation Device: 82945G/GZ Integrated Graphics Controller SVendor:Elitegroup Computer Systems SDevice:Device 1b76 Rev:02 Driver: i915 Module: i915 What did you use to get this list? It's different than the lspci output. lspci identifies mine as: Intel Corporation 82865G Integrated Graphics Controller (rev 02) lspci -v -mm -k ;) Nice, isn't it? It's a bit weird I've reenabled the composite in KDE and problem it went away... Hi, any news, ideas, with about this topic, driver is working terrible, I thought that was a KDE issue, but in MATE it happens either... Today, a similar issue happened to me with the Fedora installer, when installing F22 on my old netbook. When the installation started, initially a couple of horizontal strips appeared, which gradually accumulated until the display was entirely unreadable and distorted. Video card: Slot: 00:02.0 Class: VGA compatible controller Vendor: Intel Corporation Device: Mobile 945GSE Express Integrated Graphics Controller SVendor:Micro-Star International Co., Ltd. [MSI] SDevice:Device 0110 Rev:03 Driver: i915 Module: i915 Ralf I've managed for reduce failures appending the kernel parameter i915.enable_ips=0, but it didn't disappear completely, but at least, I can work using this graphic card. -- -- Sergio Belkin http://www.sergiobelkin.com LPIC-2 Certified - http://www.lpi.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
Sounds great, I know Allan and Richard has some mockups for how they want to do upgrades in GNOME Software, so hopefully this will make it even easier to implement. Christian - Original Message - From: Will Woods wwo...@redhat.com To: devel@lists.fedoraproject.org Sent: Thursday, May 28, 2015 11:42:56 AM Subject: fedup for F23 and beyond [tl;dr: fedup is going away and should be re-implemented by the system packaging tools.] Hey all, F22 is the fifth release we've handled with fedup. A lot has changed since F17, and we've learned some valuable lessons about how upgrades work (and how they fail). We've come to the conclusion that the current design is unsupportable, mostly due to upgrade.img, which turns out to cause more problems than it solves[1]. So! For F23, fedup needs to be redesigned. Here's how it should work: 1) Download packages for the new system 2) Use the systemd Offline Updates[2] facility to install packages This is really simple - simple enough that it should probably be provided by the system packaging tools themselves. As a proof-of-concept, I've implemented it as a DNF plugin, which you can see here[3]: https://github.com/wgwoods/dnf-plugin-fedup This behavior could also be implemented by PackageKit, which would make it easy to write a proper GUI. So that's the plan: drop upgrade.img, move upgrade support into the system packaging tools. Sometimes simpler is better. -w [1] For example, here are three F22 release-blockers, all caused by upgrade.img: https://bugzilla.redhat.com/show_bug.cgi?id=1185604 https://bugzilla.redhat.com/show_bug.cgi?id=1209941 https://bugzilla.redhat.com/show_bug.cgi?id=1207251 That first one is a nasty crash inside systemd, which led to a mailing-list discussion[1a] where Lennart concludes that the double-switchroot thing we're doing with upgrade.img is just not supportable[1b]. And I totally agree. [1a] http://lists.freedesktop.org/archives/systemd-devel/2015-March/029030.html [1b] http://lists.freedesktop.org/archives/systemd-devel/2015-April/031013.html [2] http://www.freedesktop.org/wiki/Software/systemd/SystemUpdates/ [3] It works just fine in F21, if you're feeling brave.. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1190033] perl-Catalyst-View-Mason-0.19-1.fc22 FTBFS: test fails: Error: Can't locate object method BINMODE via package IO::Capture::Tie_STDx at /usr/share/perl5/vendor_perl/Catalyst/Log.pm l
https://bugzilla.redhat.com/show_bug.cgi?id=1190033 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Catalyst-View-Mason-0. |perl-Catalyst-View-Mason-0. |19-2.fc23 |19-2.fc22 Resolution|--- |ERRATA Last Closed||2015-05-28 08:00:30 --- Comment #5 from Fedora Update System upda...@fedoraproject.org --- perl-Catalyst-View-Mason-0.19-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1225476] perl-Module-ScanDeps-1.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1225476 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Module-ScanDeps-1.19-1 ||.fc23 Resolution|--- |RAWHIDE Last Closed||2015-05-28 08:00:36 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1222727] perl-Module-Signature-0.79 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1222727 --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- perl-Module-Signature-0.79-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1222921] perl-HTTP-Tiny-0.056 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1222921 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-HTTP-Tiny-0.056-1.fc23 |perl-HTTP-Tiny-0.056-1.fc22 Resolution|--- |ERRATA Last Closed||2015-05-28 08:06:50 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-HTTP-Tiny-0.056-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Including tlp in Fedora Workstation by default
On 05/28/2015 02:11 PM, Stephen Gallagher wrote: Actually, it *does* sound like this package might provide a way to mitigate that situation (single kernel). If tlp can accept a configuration file for what tweaks to make, then we can use the per -product config feature to allow us to set certain features differently on Workstation compared to Server/Cloud or non-product. (This would still probably mean shipping things like the USB autosuspend disabled, due to the other effects it can have). Doesn't tuned already do something similar to this? -- Florian Weimer / Red Hat Product Security -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Secure boot and packaging third-party kernel modules
Hi, I've started poking into packaging the mhvtl project for Fedora and EPEL. This package also contains a kernel module, which normally works fine - until you hit Secure Boot. So I was wondering how to handle this the best way. AFAIK, there are currently no plans to get the mhvtl.ko kernel module into the upstream kernel. Some packages (VirtualBox, IIRC) can compile the kernel module on-the-fly if it is missing during boot. That's an easy thing to implement. But for secure boot, things gets complicated as the kernel module needs to be signed. I've played with mokutil and the sign-file script which is in kernel-devel, based on this article [1]. This all works fine. I could easily install my own key, compile the mhvtl.ko module and sign it. And then it was possible to load the module. [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html It's also important to remember that kernels do get updated. So when a new kernel is installed, it is (to my knowledge) required to recompile the module. If I'm mistaken, please educate me! My current idea to solve this is to: * Have a preparation script which the admin is required to run on a new system. This scripts generates the needed key material and runs mokutil which installs the key. It will then provide enough information so that the admin can reboot the system and get the MOK key installed. * Have a unit file which runs a ExecStartPre= script. This script will check if the key material exists. If it does, it will check if the mhvtl.ko module for the currently running kernel exists. If the module is missing, it will compile it, sign it and load it. Failures along the way will cause the unit file to fail all together. When the ExecStartPre= script has completed successfully, it will start the needed processes it normally would do. Any thoughts or comments to this approach? Anyone got a better idea? Yes, I do know it is not good to have the keying material for the signing too easily available. So I'm also keen to hear ideas how to protect the key better. With that said, I'm planning on only providing access to the key file to the root user only. And I'll look into if I can restrict the accesss even further with some SELinux rules (so only the ExecStartPre= script can access it together with the preparation script. Another thought ... Are there other packages who could benefit of such a solution if it was made more generic? I'm willing to investigate into this too, if there are more users out there ... Or if someone has already done that - no need to reinvent the wheel! -- kind regards, David Sommerseth -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
psabata pushed to perl-File-RsyncP (epel7). release bump for rebuild
From 40cf1dad314308dad39d7c410d5aa6d0fb8b477e Mon Sep 17 00:00:00 2001 From: Mike McGrath mmcgr...@fedoraproject.org Date: Mon, 11 Sep 2006 02:55:22 + Subject: release bump for rebuild diff --git a/needs.rebuild b/needs.rebuild deleted file mode 100644 index 815fd29..000 --- a/needs.rebuild +++ /dev/null @@ -1 +0,0 @@ -http://fedoraproject.org/wiki/Extras/Schedule/FC6MassRebuild diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index 6765a1d..28a305e 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,6 +1,6 @@ Name: perl-File-RsyncP Version: 0.62 -Release: 2%{?dist} +Release: 3%{?dist} Summary: A perl implementation of an Rsync client License: GPL Group: Development/Libraries @@ -54,6 +54,9 @@ make test %changelog +* Sun Sep 10 2006 Mike McGrath imli...@gmail.com - 0.62-2 +- Rebuild + * Fri Jul 21 2006 Mike McGrath imli...@gmail.com - 0.62-2 - Fixed whitespace issue and removed SMP flags on make -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=40cf1dad314308dad39d7c410d5aa6d0fb8b477e -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-File-RsyncP (epel7). fix br
From 7dcfbe3a41af867bcf3541cc0ce9dbcafbee0c0c Mon Sep 17 00:00:00 2001 From: Tom Callaway s...@fedoraproject.org Date: Mon, 15 Oct 2007 20:36:37 + Subject: fix br diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index 3370a91..00e3a62 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,6 +1,6 @@ Name: perl-File-RsyncP Version: 0.68 -Release: 2%{?dist} +Release: 2%{?dist}.1 Summary: A perl implementation of an Rsync client License: GPLv2 Group: Development/Libraries @@ -10,6 +10,7 @@ BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version)) BuildRequires: %{_bindir}/iconv +BuildRequires: perl(ExtUtils::MakeMaker) %description File::RsyncP is a perl implementation of an Rsync client. It is compatible with @@ -50,6 +51,9 @@ make test %changelog +* Mon Oct 15 2007 Tom spot Callaway tcall...@redhat.com - 0.68-2.1 +- add BR: perl(ExtUtils::MakeMaker) + * Wed Aug 22 2007 Mike McGrath mmcgr...@redhat.com - 0.68-2 - Rebuild for BuildID - License change -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=7dcfbe3a41af867bcf3541cc0ce9dbcafbee0c0c -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-File-RsyncP (epel7). Rebuild and license change
From 30ed3f5b9fa2aa54dc59078f1a04bc6d1d311408 Mon Sep 17 00:00:00 2001 From: Mike McGrath mmcgr...@fedoraproject.org Date: Thu, 23 Aug 2007 02:25:47 + Subject: Rebuild and license change diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index 6c89e56..3370a91 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,8 +1,8 @@ Name: perl-File-RsyncP Version: 0.68 -Release: 1%{?dist} +Release: 2%{?dist} Summary: A perl implementation of an Rsync client -License: GPL +License: GPLv2 Group: Development/Libraries URL: http://search.cpan.org/dist/File-RsyncP/ Source0: http://search.cpan.org/CPAN/authors/id/C/CB/CBARRATT/File-RsyncP-%{version}.tar.gz @@ -50,6 +50,10 @@ make test %changelog +* Wed Aug 22 2007 Mike McGrath mmcgr...@redhat.com - 0.68-2 +- Rebuild for BuildID +- License change + * Mon Jun 04 2007 Mike McGrath mmcgr...@redhat.com - 0.68-1 - Upstream released new version -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=30ed3f5b9fa2aa54dc59078f1a04bc6d1d311408 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-File-RsyncP (epel7). - Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
From f0fa0c06c9e90046750ea708fe00c41aec241a69 Mon Sep 17 00:00:00 2001 From: Dennis Gilmore den...@ausil.us Date: Tue, 8 Feb 2011 16:26:45 -0600 Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index ead714e..c81cb19 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,6 +1,6 @@ Name: perl-File-RsyncP Version: 0.68 -Release: 9%{?dist} +Release: 10%{?dist} Summary: A perl implementation of an Rsync client License: GPLv2 Group: Development/Libraries @@ -51,6 +51,9 @@ make test %changelog +* Tue Feb 08 2011 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.68-10 +- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild + * Thu Dec 16 2010 Marcela Maslanova mmasl...@redhat.com - 0.68-9 - 661697 rebuild for fixing problems with vendorach/lib -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=f0fa0c06c9e90046750ea708fe00c41aec241a69 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-File-RsyncP (epel7). Perl 5.18 rebuild
From ab73d06639ade55d0468df1151e7469067a8f126 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com Date: Thu, 18 Jul 2013 03:04:51 +0200 Subject: Perl 5.18 rebuild diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index 556d453..03d755c 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,6 +1,6 @@ Name: perl-File-RsyncP Version:0.70 -Release:7%{?dist} +Release:8%{?dist} Summary:A perl implementation of an Rsync client License:GPLv2 Group: Development/Libraries @@ -51,6 +51,9 @@ make test %{_mandir}/man3/* %changelog +* Thu Jul 18 2013 Petr Pisar ppi...@redhat.com - 0.70-8 +- Perl 5.18 rebuild + * Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.70-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=ab73d06639ade55d0468df1151e7469067a8f126 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-File-RsyncP (epel7). Perl mass rebuild
From ddcb627f005325f924988b9cc79c29c163e1ec16 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcela=20Ma=C5=A1l=C3=A1=C5=88ov=C3=A1?= mmasl...@redhat.com Date: Fri, 17 Jun 2011 18:57:24 +0200 Subject: Perl mass rebuild diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index 65fe63d..e7a10cf 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,6 +1,6 @@ Name: perl-File-RsyncP Version:0.70 -Release:1%{?dist} +Release:2%{?dist} Summary:A perl implementation of an Rsync client License:GPLv2 Group: Development/Libraries @@ -43,6 +43,9 @@ make test %{_mandir}/man3/* %changelog +* Fri Jun 17 2011 Marcela Mašláňová mmasl...@redhat.com - 0.70-2 +- Perl mass rebuild + * Tue Apr 05 2011 Petr Sabata psab...@redhat.com - 0.70-1 - 0.70 bump - Utilizing parallel make -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=ddcb627f005325f924988b9cc79c29c163e1ec16 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
psabata pushed to perl-File-RsyncP (epel7). Own vendor_perl/File dirs.
From f0c68389a60a3b8aea5e9baf233a185691e35436 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= ville.sky...@iki.fi Date: Wed, 23 Nov 2011 21:34:44 +0200 Subject: Own vendor_perl/File dirs. diff --git a/perl-File-RsyncP.spec b/perl-File-RsyncP.spec index e7a10cf..6646101 100644 --- a/perl-File-RsyncP.spec +++ b/perl-File-RsyncP.spec @@ -1,6 +1,6 @@ Name: perl-File-RsyncP Version:0.70 -Release:2%{?dist} +Release:3%{?dist} Summary:A perl implementation of an Rsync client License:GPLv2 Group: Development/Libraries @@ -37,12 +37,14 @@ make test %files %defattr(-,root,root,-) %doc Changes LICENSE README -%{perl_vendorarch}/File/RsyncP.pm -%{perl_vendorarch}/File/RsyncP/ -%{perl_vendorarch}/auto/File/RsyncP/ +%{perl_vendorarch}/File/ +%{perl_vendorarch}/auto/File/ %{_mandir}/man3/* %changelog +* Wed Nov 23 2011 Ville Skyttä ville.sky...@iki.fi - 0.70-3 +- Own vendor_perl/File dirs. + * Fri Jun 17 2011 Marcela Mašláňová mmasl...@redhat.com - 0.70-2 - Perl mass rebuild -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-File-RsyncP.git/commit/?h=epel7id=f0c68389a60a3b8aea5e9baf233a185691e35436 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel