Re: ansible in Fedora 23+ (python3)
On Tue, 2015-10-13 at 21:06 -0600, Kevin Fenzi wrote: > I don't see how that could work. Ansible has tons of modules, which > ones are "standard" ? Such a package would have a ton of deps... Right. Sometimes you need the Docker bits, sometimes you don't. One thing that's a bit awkward is that you can't install packages OOTB with Docker on F23, because neither yum nor python2-dnf is installed by default. *That* seems like arguably a real problem. Beyond that, though, why not just have your ansible play ensure its own deps are installed? If you're dealing with docker, make sure the package you need is installed before you run any docker steps... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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: ansible in Fedora 23+ (python3)
On Tue, 2015-10-13 at 20:57 -0700, Adam Williamson wrote: > On Tue, 2015-10-13 at 21:06 -0600, Kevin Fenzi wrote: > > > I don't see how that could work. Ansible has tons of modules, which > > ones are "standard" ? Such a package would have a ton of deps... > > Right. Sometimes you need the Docker bits, sometimes you don't. > > One thing that's a bit awkward is that you can't install packages > OOTB > with Docker on F23, D'oh, of course I meant ansible. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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: ansible in Fedora 23+ (python3)
On Tue, 13 Oct 2015 20:36:39 -0600 Orion Poplawski wrote: > On 10/13/2015 08:21 PM, Dusty Mabe wrote: > > > > > > Hey all, > > > > Just wondering if anyone has started to feel any pain from trying to > > use ansible with F23 systems. As part of the Fedora Cloud working > > group it would be nice to ship a system that could be targeted by > > ansible out of the box. Unfortunately, since ansible uses python 2.X > > vs python 3 it doesn't really work. > > > > A simple answer would be to "just install python", but I actually > > hit several roadblocks because of python packages that are usually > > there but have been replaced by their python 3 counterparts. As an > > example for one ansible playbook like [1] I had to install these > > rpms in order to get it to work: > > > > python libselinux-python python-dnf python-docker-py I'm not sure how thats a roadblock... 4 packages and their deps? > > Unfortunately there isn't a catchall that is a workaround for this > > problem because the libraries you need on the system depend on the > > modules you will use. Right. > > Does anyone have a good solution for this? Obviously it would be > > nice if ansible went to python3 but I think they have stated > > clearly that they are sticking with python2 for backwards compat > > with systems that still need 2.4. Install the python2 packages you need. > > -Dusty > > > > [1] - > > https://github.com/dustymabe/vagrantdirs/blob/master/f22/playbook.yml > > > > I suspect this is probably better to be hashed out in a bugreport, > but perhaps one solution would be to produce an ansible-runtime meta > package or comps group that pulls in standard packages needed to run > ansible locally. Otherwise I don't see how you get around what you > need on a system by just installing it. I don't see how that could work. Ansible has tons of modules, which ones are "standard" ? Such a package would have a ton of deps... kevin pgp27lHXzivJr.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: ansible in Fedora 23+ (python3)
On 10/13/2015 08:21 PM, Dusty Mabe wrote: Hey all, Just wondering if anyone has started to feel any pain from trying to use ansible with F23 systems. As part of the Fedora Cloud working group it would be nice to ship a system that could be targeted by ansible out of the box. Unfortunately, since ansible uses python 2.X vs python 3 it doesn't really work. A simple answer would be to "just install python", but I actually hit several roadblocks because of python packages that are usually there but have been replaced by their python 3 counterparts. As an example for one ansible playbook like [1] I had to install these rpms in order to get it to work: python libselinux-python python-dnf python-docker-py Unfortunately there isn't a catchall that is a workaround for this problem because the libraries you need on the system depend on the modules you will use. Does anyone have a good solution for this? Obviously it would be nice if ansible went to python3 but I think they have stated clearly that they are sticking with python2 for backwards compat with systems that still need 2.4. -Dusty [1] - https://github.com/dustymabe/vagrantdirs/blob/master/f22/playbook.yml I suspect this is probably better to be hashed out in a bugreport, but perhaps one solution would be to produce an ansible-runtime meta package or comps group that pulls in standard packages needed to run ansible locally. Otherwise I don't see how you get around what you need on a system by just installing it. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
ansible in Fedora 23+ (python3)
Hey all, Just wondering if anyone has started to feel any pain from trying to use ansible with F23 systems. As part of the Fedora Cloud working group it would be nice to ship a system that could be targeted by ansible out of the box. Unfortunately, since ansible uses python 2.X vs python 3 it doesn't really work. A simple answer would be to "just install python", but I actually hit several roadblocks because of python packages that are usually there but have been replaced by their python 3 counterparts. As an example for one ansible playbook like [1] I had to install these rpms in order to get it to work: python libselinux-python python-dnf python-docker-py Unfortunately there isn't a catchall that is a workaround for this problem because the libraries you need on the system depend on the modules you will use. Does anyone have a good solution for this? Obviously it would be nice if ansible went to python3 but I think they have stated clearly that they are sticking with python2 for backwards compat with systems that still need 2.4. -Dusty [1] - https://github.com/dustymabe/vagrantdirs/blob/master/f22/playbook.yml -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Fedora 23 Final Test Compose 9 (TC9) Available Now!
As scheduled [1], Fedora 23 Final Test Compose 9 (TC9) is now available for testing. Please help us complete all the validation testing! This one contains the installer images that were missing from TC6, though the Docker image is missing, releng says. openQA is grinding away now, the first few tests have passed. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/6266#comment:2 . Please see the following pages for download links and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download- ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Workstation and Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Server: https://fedoraproject.org/wiki/Test_Results:Current_Server_Test Cloud: https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test Summary: https://fedoraproject.org/wiki/Test_Results:Current_Summary All Alpha, Beta and Final priority test cases for each of these test pages [2] must pass in order to meet the Final Release Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5]. Create Fedora 23 Final test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/6266 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-23/f-23-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_23_Final_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://admin.fedoraproject.org/mailman/listinfo/test -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Schedule for Wednesday's FESCo Meeting (2015-10-14)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2015-10-14 18:00 UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #615 Strategy for services that do not have systemd native unit files .fesco 615 https://fedorahosted.org/fesco/ticket/615 = New business = #topic #1486 FESCo elections for F24/F25 .fesco 1486 https://fedorahosted.org/fesco/ticket/1486 #topic #1489 F24 System Wide Change: NetworkManager 1.2 .fesco 1489 https://fedorahosted.org/fesco/ticket/1489 #topic #1490 restore MPI Requires Provides as F23 change .fesco 1490 https://fedorahosted.org/fesco/ticket/1490 #topic #1491 clarifications/improvements for new bundling policy .fesco 1491 https://fedorahosted.org/fesco/ticket/1491 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
review swap
Hi I need reviews this packages for upgrade ApacheDS to 2.0.0-M20. apached/s-ldap-api https://bugzilla.redhat.com/show_bug.cgi?id=1255815 Let me know what I can review for you in exchange. Thanks in advance gil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Onwnership of Fedora Electronic Lab packages
Hi there, I would like to announce that I'm willing to take ownership of the following orphaned packages that are part of the Fedora Electronic Lab, maintain and update it as required. archimedes covered electric emacs-verilog-mode fped freehdl gds2pov geda-gaf gerbv iverilog keurocalc kmenu-gnome kpolynome ktechlab libstroke linsmith mot-adms netgen ngspice ovm pcb pharosc pikdev piklab pikloops qt-qsa sk2py toped trac-peerreview-plugin wb_builder Best regards! -- *Kiara Navarro* *Founder of Panamahitek* *Fedora Project Contributor * www.panamahitek.com *GPG-KEY*: A81DB1D8 -- 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: Current Rawhide problems you might want to know about
On 14.10.2015 00:13, Richard W.M. Jones wrote: On Tue, Oct 13, 2015 at 03:00:27PM -0600, Chris Murphy wrote: Maybe strace will show where it gets hung up? Tried it of course - strace doesn't work across the setuid boundary. Maybe I can attach a trace tool (which?) to sshd (how?) and find out where it is spending its time. This stuff should be easier ... Sysdig [1] logs all (or some if filter is specified) syscalls via kernel module (in binary format like tshark): sysdig -w /tmp/all.scap sysdig -r /tmp/all.scap Kind regards, Alek [1] http://www.sysdig.org/install/ -- 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 3:37 PM, Chris Murphy wrote: > On Tue, Oct 13, 2015 at 3:31 PM, Matthew Miller > wrote: >> On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote: >>> > Is it DNS? That's my go-to blame victim for ssh delays. >>> I think it's dbus actually: >>> https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3 >> >> Is kdbus enabled? > > Any journal messages between those two time stamps where the gap is? > > Maybe add a -v to strace and see if something else shows up. Nothing > else is forking, so... OK so this is like throwing spaghetti, but maybe valgrind, something like: valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes -v sudo bash Of course that'll almost certainly lead you down a debug package installation rabbit hole for a period of time. -- Chris Murphy -- 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 3:31 PM, Matthew Miller wrote: > On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote: >> > Is it DNS? That's my go-to blame victim for ssh delays. >> I think it's dbus actually: >> https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3 > > Is kdbus enabled? Any journal messages between those two time stamps where the gap is? Maybe add a -v to strace and see if something else shows up. Nothing else is forking, so... -- Chris Murphy -- 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: Better irc policies?
On Mon, 2015-06-15 at 11:22 +0100, Richard W.M. Jones wrote: > On Wed, Jun 10, 2015 at 01:50:31PM -0700, Gerald B. Cox wrote: > > On Wed, Jun 10, 2015 at 1:27 PM, Andreas Tunek > .com> > > wrote: > > > > > Yeah, you have to do a lot of quite complicated stuff before you > > > can > > > register and get any support via irc. To register to this mailing > > > list > > > you just send an email (or can you fill in a form as well). > > > > > > > Complicated is relative. If you don't understand how it works, > > it's best > > to research. There > > are many guides a google search away. > > > > IRC can be helpful for support, but being interactive you're > > assuming that > > someone is standing by > > waiting for you to ask a question - which may or may not be the > > case. IRC > > is more functional for online > > meetings and group discussions. Mailing lists, forums, bugzilla, > > etc. are > > better for support and investigation of issues. > > Also IRC is either not archived and made searchable, or where it is > archived it's usually hard to follow the conversation thread. > > Therefore we answer questions on IRC over and over and over again. > (In #libguestfs I try to add such questions to our FAQ, when I have > the time and remember to do it). https://ask.fedoraproject.org or > mailing lists are a much better solution. To set the cat among the pigeons a bit, it'd sure be interesting to consider setting up one of the F/OSS Slack-alikes for Fedora use...of course, there's a question of at what point we have too many tools. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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: Current Rawhide problems you might want to know about
19844 22:16:16.857460 ppoll([{fd=8, events=POLLIN}], 1, {24,
999885000}, NULL, 8) = 0 (Timeout)
19844 22:16:41.864999
open("/usr/share/locale/en_GB.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
That's a huge gap while nothing at all is showing up in the strace.
---
Chris Murphy
--
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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote: > > Is it DNS? That's my go-to blame victim for ssh delays. > I think it's dbus actually: > https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3 Is kdbus enabled? -- Matthew Miller 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 05:16:17PM -0400, Matthew Miller wrote: > On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote: > > * On x86_64, ssh logins take quite a long time - about 30 seconds. I > > have no idea what component to assign this to, so I didn't file a > > bug about it yet. > > Is it DNS? That's my go-to blame victim for ssh delays. I think it's dbus actually: https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote: > * On x86_64, ssh logins take quite a long time - about 30 seconds. I > have no idea what component to assign this to, so I didn't file a > bug about it yet. Is it DNS? That's my go-to blame victim for ssh delays. -- Matthew Miller 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 03:00:27PM -0600, Chris Murphy wrote: > Maybe strace will show where it gets hung up? Tried it of course - strace doesn't work across the setuid boundary. Maybe I can attach a trace tool (which?) to sshd (how?) and find out where it is spending its time. This stuff should be easier ... Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- 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: Current Rawhide problems you might want to know about
Maybe strace will show where it gets hung up? --- Chris Murphy -- 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 09:11:59PM +0100, Richard W.M. Jones wrote: > On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote: > > * On x86_64, ssh logins take quite a long time - about 30 seconds. I > > have no idea what component to assign this to, so I didn't file a > > bug about it yet. > > Not just logins, 'sudo bash' too. BZ is here: https://bugzilla.redhat.com/show_bug.cgi?id=1271394 I have no idea how to debug this, or even what component to assign it to. Suggestions? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- 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: Current Rawhide problems you might want to know about
On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote: > * On x86_64, ssh logins take quite a long time - about 30 seconds. I > have no idea what component to assign this to, so I didn't file a > bug about it yet. Not just logins, 'sudo bash' too. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.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
Current Rawhide problems you might want to know about
A couple of things: * systemd in aarch64 crashes on boot: https://bugzilla.redhat.com/show_bug.cgi?id=1271387 * On x86_64, ssh logins take quite a long time - about 30 seconds. I have no idea what component to assign this to, so I didn't file a bug about it yet. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora 23 Branched 20151013 compose check report
No missing expected images. Images in this compose but not 23 Branched 20151012: Kde disk raw armhfp Soas disk raw armhfp Server disk raw armhfp No images in 23 Branched 20151012 but not this. Failed openQA tests: 10 of 52 ID: 5681Test: x86_64 universal server_no_swap@uefi ID: 5676Test: i386 universal server_software_raid ID: 5663Test: x86_64 generic_boot default_install ID: 5662Test: x86_64 kde_live default_install ID: 5661Test: i386 kde_live default_install ID: 5658Test: i386 workstation_live default_install ID: 5653Test: i386 universal upgrade_desktop_32bit ID: 5638Test: x86_64 universal server_simple_free_space@uefi ID: 5636Test: x86_64 universal server_delete_partial@uefi ID: 5629Test: x86_64 universal upgrade_desktop_64bit Passed openQA tests: 42 of 52 -- Mail generated by check-compose: https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora Rawhide 20151013 compose check report
No missing expected images. Images in this compose but not Rawhide 20151012: Workstation disk raw armhfp No images in Rawhide 20151012 but not this. Failed openQA tests: 24 of 52 ID: 5670Test: x86_64 universal server_btrfs@uefi ID: 5657Test: i386 kde_live default_install ID: 5609Test: x86_64 kde_live default_install ID: 5606Test: i386 workstation_live default_install ID: 5602Test: i386 universal upgrade_desktop_32bit ID: 5601Test: i386 universal server_lvmthin ID: 5600Test: i386 universal server_ext3 ID: 5599Test: i386 universal server_btrfs ID: 5598Test: i386 universal server_software_raid ID: 5593Test: x86_64 universal server_no_swap@uefi ID: 5592Test: x86_64 universal server_lvmthin@uefi ID: 5591Test: x86_64 universal server_ext3@uefi ID: 5589Test: x86_64 universal server_software_raid@uefi ID: 5587Test: x86_64 universal server_simple_free_space@uefi ID: 5585Test: x86_64 universal server_delete_partial@uefi ID: 5582Test: x86_64 universal european_language_install ID: 5578Test: x86_64 universal upgrade_desktop_64bit ID: 5577Test: x86_64 universal upgrade_minimal_64bit ID: 5575Test: x86_64 universal server_no_swap ID: 5574Test: x86_64 universal server_lvmthin ID: 5573Test: x86_64 universal server_ext3 ID: 5572Test: x86_64 universal server_btrfs ID: 5571Test: x86_64 universal server_software_raid ID: 5563Test: x86_64 universal server_delete_pata Passed openQA tests: 28 of 52 -- Mail generated by check-compose: https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose -- 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: Best practice to determine which packages need to be rebuilt
On Tue, Oct 13, 2015 at 1:49 PM, Neal Gompa wrote: > Ideally, Koschei[0] should be doing this for us, right? > Neat, but kinda after the fact, right? I'm trying to be proactive and make sure that all dependencies CAN rebuild against the new version (probably using mockchain) before doing a build in rawhide since there's no option when you build for rawhide to stop the update. Thanks, 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: Best practice to determine which packages need to be rebuilt
Ideally, Koschei[0] should be doing this for us, right? [0]: https://apps.fedoraproject.org/koschei On Tue, Oct 13, 2015 at 2:22 PM, Richard Shaw wrote: > I frequently see various incantations that people use to determine what > packages need to be rebuilt based on an ABI/API incompatible change to a > library. > > Shouldn't we have a best practice documented in the wiki for something > that's needed so frequently? And to take it one step further, how about > creating a shell script in one of the rpm developer packages? > > Thanks, > 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 > -- 真実はいつも一つ！/ 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
Best practice to determine which packages need to be rebuilt
I frequently see various incantations that people use to determine what packages need to be rebuilt based on an ABI/API incompatible change to a library. Shouldn't we have a best practice documented in the wiki for something that's needed so frequently? And to take it one step further, how about creating a shell script in one of the rpm developer packages? Thanks, 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
Fedora 23 Final Freeze
Hi all, Today is an important day on the Fedora 23 schedule[1], with a significant cut-offs. Today is the Final Freeze[2]. This means that only packages which fix accepted blocker or freeze exception bugs[3][4] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. Regards Dennis [1] https://fedoraproject.org/wiki/Releases/23/Schedule [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process signature.asc Description: This is a digitally signed message part. ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce-- 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: Setting + for fedora-review?
On Friday, October 09, 2015 08:44:11 AM Kevin Fenzi wrote: > On Fri, 09 Oct 2015 10:40:28 -0400 > > Stephen Chandler Paul wrote: > > Hi, I recently did a review swap with someone, and approved their > > package. https://bugzilla.redhat.com/show_bug.cgi?id=1257410 > > (I should note Lyude is the same person as me, that's just my non > > -redhat bugzilla account) > > The guide here https://fedoraproject.org/wiki/Package_Review_Process > > sa ys that I should now set the flag for this package to +, however it > > seems I lack the permissions to do so on both my personal and red hat > > account. Am I supposed to have someone from the Fedora development > > team do this or am I missing something here? > > I would think your Red Hat account would be able to do it, but your > Fedora account should be able to to as long as you are in the packager > group and the email address you have in fas is the same as your > bugzilla account. Is that the case? Red Hat accounts can not set the flag, you need to be in fedora-bugs to set the flag which you should get automatically when you become a packager in fas. Dennis 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
python-pexpect 4.x coming to F23 and Rawhide
Hi folks, today I managed to fix all critical issues regarding pexpect 4.x. Most interested feature of this release is supporting asyncio. Changelog: http://pexpect.readthedocs.org/en/stable/history.html#releases I don't think that someone will see regressions, because I more or less checked relnotes, source code of projects dependent on it in Fedora and found nothing to be broken. List of dependencies: catfish-0:1.3.2-2.fc24.noarch cinnamon-0:2.6.13-10.fc24.x86_64 openstack-trove-guestagent-1:4.0.0-0.1.0rc2.fc24.noarch python-hardware-0:0.17-1.fc24.noarch python-invoke-0:0.9.0-5.fc23.noarch python-ipython-console-0:3.2.1-5.fc24.noarch stylus-toolbox-0:0.2.7-10.fc23.noarch python3-hardware-0:0.17-1.fc24.noarch python3-invoke-0:0.9.0-5.fc23.noarch python3-ipython-console-0:3.2.1-5.fc24.noarch I've increased positive karma for this update to ensure that testing will be enough. Bodhi link: https://bodhi.fedoraproject.org/updates/python-pexpect-4.0.1-3.fc23 -- -Igor Gnatenko -- 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: Summary/Minutes from today's FESCo Meeting (2015-10-07)
Hey, everyone — this thread seems to be going off the rails. Discussion about the importance and merits of distro uniqueness is of course fine, but please keep it technical rather than personal. -- Matthew Miller 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: Hi Guys !
Thanks guys ! got a Lenovo T410 and things just work great with Fedora 22 . I ll keep tht list with me as i am planning to get another laptop in future . 2015-10-11 19:51 GMT+01:00 Andrey Ponomarenko : > Jules Bashizi wrote: > >> I got admission into some British university and I am to buy a laptop . >> wish to know a machine which is good with Linux . any advice on which and >> where to get it please ! >> > > Take a look at this list of laptops/notebooks tested with the Linux > kernels from 3.14 to 4.1: > http://hw.rosalinux.ru/index.php?show=machines&ftype=notebook > > You can sort the list by the computer model and select a most popular one. > > -- > Andrey Ponomarenko > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > -- Irenge B. Jules IT Assistant Windle Trust International Kenya email : jbi.oct...@gmail.com Tel No 0729410174 Kenya -- 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: Summary/Minutes from today's FESCo Meeting (2015-10-07)
On 2015-10-13, Bastien Nocera wrote: > We already did the "distributions aren't compatible" thing in the 90's. > Great. Then there is no (new) problem. > If Ubuntu and Fedora binaries aren't compatible, which one do you think > is going to get used by developers that need to generate programs running > on Ubuntu? If I need binary for A, I will use A. So simple. -- Petr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
jplesnik pushed to perl-Flickr-API (master). "1.25 bump"
From 812552a22c785450f6daf7c9ed87b4efd3554ac6 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova
Date: Tue, 13 Oct 2015 14:32:50 +0200
Subject: 1.25 bump
---
.gitignore | 1 +
...PI-1.13-Do-not-install-examples-into-PATH.patch | 35 --
perl-Flickr-API.spec | 19 +++-
sources| 2 +-
4 files changed, 13 insertions(+), 44 deletions(-)
delete mode 100644 Flickr-API-1.13-Do-not-install-examples-into-PATH.patch
diff --git a/.gitignore b/.gitignore
index d3fa128..2b7410b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@ Flickr-API-1.02.tar.gz
/Flickr-API-1.04.tar.gz
/Flickr-API-1.05.tar.gz
/Flickr-API-1.13.tar.gz
+/Flickr-API-1.25.tar.gz
diff --git a/Flickr-API-1.13-Do-not-install-examples-into-PATH.patch
b/Flickr-API-1.13-Do-not-install-examples-into-PATH.patch
deleted file mode 100644
index 6cb9b50..000
--- a/Flickr-API-1.13-Do-not-install-examples-into-PATH.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 668a4b58b1cd7d8bf9b449bb66566351158f0efe Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?=
-Date: Tue, 23 Jun 2015 16:27:45 +0200
-Subject: [PATCH] Do not install examples into PATH
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-CPAN RT#105426
-
-Signed-off-by: Petr Písař
- Makefile.PL | 8
- 1 file changed, 8 deletions(-)
-
-diff --git a/Makefile.PL b/Makefile.PL
-index cb3d8d7..95cd7bb 100644
a/Makefile.PL
-+++ b/Makefile.PL
-@@ -53,12 +53,4 @@ WriteMakefile(
-
'Term::ReadKey' => 0,
-
'Getopt::Long' => 0,
- },
--'EXE_FILES' =>
--[
--'examples/flickr_oauth_authentication.pl',
--'examples/flickr_method_test_echo.pl',
--'examples/flickr_method_test_login.pl',
--'examples/flickr_dump_stored_config.pl',
--'examples/flickr_make_stored_config.pl',
--]
- );
---
-2.1.0
-
diff --git a/perl-Flickr-API.spec b/perl-Flickr-API.spec
index e84c9ff..19771b0 100644
--- a/perl-Flickr-API.spec
+++ b/perl-Flickr-API.spec
@@ -1,15 +1,11 @@
Name: perl-Flickr-API
-Version:1.13
+Version:1.25
Release:1%{?dist}
Summary:Perl interface to the Flickr API
-# LICENSE: Artistic 2.0
-# examples/flickr_method_test_login.pl: GPL+ or Artistic
-License:(Artistic 2.0) and (GPL+ or Artistic)
+License:Artistic 2.0
Group: Development/Libraries
URL:http://search.cpan.org/dist/Flickr-API/
Source0:
http://www.cpan.org/authors/id/L/LB/LBMOORE/Flickr-API-%{version}.tar.gz
-# Do not install examples as tools into PATH, CPAN RT#105426
-Patch0: Flickr-API-1.13-Do-not-install-examples-into-PATH.patch
BuildArch: noarch
BuildRequires: coreutils
BuildRequires: findutils
@@ -21,24 +17,27 @@ BuildRequires: perl(Carp)
# Compress::Zlib is optional
BuildRequires: perl(Digest::MD5)
BuildRequires: perl(Encode)
+BuildRequires: perl(File::Temp)
# HTTP::Message 1.56 needed because it brings decoded_content()
BuildRequires: perl(HTTP::Message) >= 1.56
BuildRequires: perl(HTTP::Request)
BuildRequires: perl(HTTP::Response)
BuildRequires: perl(LWP::UserAgent)
BuildRequires: perl(Net::OAuth)
+BuildRequires: perl(parent)
BuildRequires: perl(Scalar::Util)
BuildRequires: perl(Storable)
BuildRequires: perl(strict)
BuildRequires: perl(URI) >= 1.18
BuildRequires: perl(warnings)
+BuildRequires: perl(XML::LibXML::Simple)
BuildRequires: perl(XML::Parser::Lite::Tree) >= 0.06
# Tests:
BuildRequires: perl(Data::Dumper)
BuildRequires: perl(File::Temp)
BuildRequires: perl(Term::ReadLine)
BuildRequires: perl(Test::More)
-BuildRequires: perl(XML::Simple)
+BuildRequires: perl(Test::Script)
Requires: perl(:MODULE_COMPAT_%(eval "`perl -V:version`"; echo $version))
# HTTP::Message 1.56 needed because it brings decoded_content()
Requires: perl(HTTP::Message) >= 1.56
@@ -53,7 +52,6 @@ A simple interface for using the Flickr API.
%prep
%setup -q -n Flickr-API-%{version}
-%patch0 -p1
%build
perl Makefile.PL INSTALLDIRS=vendor - 1.25-1
+- 1.25 bump
+
* Tue Jun 23 2015 Petr Pisar - 1.13-1
- 1.13 bump
- License corrected to (Artistic 2.0) and (GPL+ or Artistic)
diff --git a/sources b/sources
index 7b92d10..2b785cb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-1fd7a1156edd2848bddc0c9395c06e7f Flickr-API-1.13.tar.gz
+9088fcba353353963816fff6b5a43978 Flickr-API-1.25.tar.gz
--
cgit v0.11.2
http://pkgs.fedoraproject.org/cgit/perl-Flickr-API.git/commit/?h=master&id=812552a22c785450f6daf7c9ed87b4efd3554ac6
--
Fedora Extras Perl SIG
F-23 Branched report: 20151013 changes
Compose started at Tue Oct 13 07:15:03 UTC 2015 Broken deps for armhfp -- [CableSwig] CableSwig-3.20.0-13.fc23.armv7hl requires gccxml [apache-scout] apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws) apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:juddi-client) [hbase] hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) [netbeans-platform] 1:netbeans-platform-harness-7.0.1-11.fc22.armv7hl requires cobertura >= 0:1.9.3 [nodejs-grunt-contrib-copy] nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(file-sync-cmp) < 0:0.2 nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(file-sync-cmp) >= 0:0.1.0 nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(chalk) >= 0:0.5.1 [oat] oat-appraiser-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api oat-client-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api [oozie] oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.pig:pig) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-serde) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-metastore) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-exec) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-common) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-cli) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:webhcat-java-client) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:hcatalog-server-extensions) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:hcatalog-pig-adapter) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:hcatalog-core) [openstack-swift] openstack-swift-2.3.0-2.fc23.noarch requires python-pyeclib [pyjigdo] pyjigdo-0.4.0.3-9.fc23.noarch requires fuseiso [python-fiat] python-fiat-1.5.0-2.fc23.noarch requires ScientificPython [vfrnav] vfrnav-20141211-1.fc22.armv7hl requires libgps.so.21 vfrnav-utils-20141211-1.fc22.armv7hl requires libgdal.so.1 Broken deps for i386 -- [CableSwig] CableSwig-3.20.0-13.fc23.i686 requires gccxml [apache-scout] apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws) apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:juddi-client) [hbase] hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) [netbeans-platform] 1:netbeans-platform-harness-7.0.1-11.fc22.i686 requires cobertura >= 0:1.9.3 [nodejs-grunt-contrib-copy] nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(file-sync-cmp) < 0:0.2 nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(file-sync-cmp) >= 0:0.1.0 nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(chalk) >= 0:0.5.1 [oat] oat-appraiser-1.6.0-16.fc22.i686 requires tomcat-servlet-3.0-api oat-client-1.6.0-16.fc22.i686 requires tomcat-servlet-3.0-api [openstack-swift] openstack-swift-2.3.0-2.fc23.noarch requires python-pyeclib [pure] pure-0.62-2.fc22.i686 requires libLLVM-3.5.so [pyjigdo] pyjigdo-0.4.0.3-9.fc23.noarch requires fuseiso [python-fiat] python-fiat-1.5.0-2.fc23.noarch requires ScientificPython [spark] spark-0.9.1-0.3.rc3.fc21.i686 requires mvn(com.typesafe.akka:akka-remote_2.10) spark-0.9.1-0.3.rc3.fc21.i686 requires mvn(com.typesafe.akka:akka-actor_2.10) [vfrnav] vfrnav-20141211-1.fc22.i686 requires libgps.so.21 vfrnav-utils-20141211-1.fc22.i686 requires libgdal.so.1 Broken deps for x86_64 -- [CableSwig] CableSwig-3.20.0-13.fc23.x86_64 requires gccxml [apache-scout] apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws) apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:juddi-client) [hbase] hbase-0.98.3-4.fc22.noarch require
rawhide report: 20151013 changes
Compose started at Tue Oct 13 05:15:03 UTC 2015 Broken deps for i386 -- [CableSwig] CableSwig-3.20.0-13.fc23.i686 requires gccxml [IQmol] IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2 [alliance] alliance-5.0-40.20090901snap.fc22.i686 requires libXm.so.2 [bro] bro-2.3.2-6.fc23.i686 requires libjemalloc.so.1 [bwm-ng] bwm-ng-0.6-18.fc24.i686 requires libstatgrab.so.6 [fence-agents] fence-agents-common-4.0.20-1.fc24.i686 requires pexpect [gnash] 1:gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-klash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-klash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-plugin-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:python-gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:python-gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:python-gnash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:python-gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 [golang-github-kraman-libcontainer] golang-github-kraman-libcontainer-devel-0-0.4.gitd700e5b.fc24.noarch requires golang(github.com/docker/docker/pkg/netlink) [golang-github-prometheus-prometheus] golang-github-prometheus-prometheus-devel-0.15.0-1.fc24.noarch requires golang(gopkg.in/fsnotify.v1) [grace] grace-5.1.25-2.fc23.i686 requires libXm.so.2 [hbase] hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) [js-of-ocaml] js-of-ocaml-2.4-8.fc23.i686 requires ocaml(runtime) = 0:4.02.2 js-of-ocaml-2.4-8.fc23.i686 requires ocaml(Lwt_list) = 0:0ce891783d3177cd33ebd9ed60d4b62d js-of-ocaml-2.4-8.fc23.i686 requires ocaml(Lwt) = 0:6f62eda62952a3e464e9c34a825cf0de [kdevelop-php] kdevelop-php-1.7.2-1.fc24.i686 requires kdevelop = 9:4.7.1 [netbeans-platform] 1:netbeans-platform-harness-7.0.1-11.fc22.i686 requires cobertura >
Re: Summary/Minutes from today's FESCo Meeting (2015-10-07)
- Original Message - > On 2015-10-13, Bastien Nocera wrote: > >> Bastien Nocera wrote: > >> > 2 distributions add slightly different versions of the same > >> > functionality > >> > -> incompatible > >> > >> I said that carrying more feature patches makes it "more likely" that > >> packages from other distros will work, not "100% certain" (which is > >> obviously not possible when there are incompatible versions of the same > >> patchset floating around). > >> > >> > Application compiled on Fedora using the new features -> doesn't work on > >> > other distribution > >> > >> And that's not a problem for OUR users, only for those of the other > >> distribution. So why would that be ours to worry about? > > > > That's a problem for OUR users because when they use Fedora, they want to > > be > > able to make a tarball of their software for their friend on Ubuntu to > > test. > > Here, you're making Fedora a bad choice for developers that want to target > > more than just Fedora. > > > If you exchange Fedora and Ubuntu, you will get the same valid > statement. This is not about Fedora or Ubuntu. It's about you don't like > diverse world where distributions differ. I enjoy it when people tell me what I don't like. > I have a good news for you: > There are different operating sytems where executing foreign blobs is > standard practice because there is exactly one distribution of the > operating system. We already did the "distributions aren't compatible" thing in the 90's. If Ubuntu and Fedora binaries aren't compatible, which one do you think is going to get used by developers that need to generate programs running on Ubuntu? -- 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: Summary/Minutes from today's FESCo Meeting (2015-10-07)
On 2015-10-13, Bastien Nocera wrote: >> Bastien Nocera wrote: >> > 2 distributions add slightly different versions of the same functionality >> > -> incompatible >> >> I said that carrying more feature patches makes it "more likely" that >> packages from other distros will work, not "100% certain" (which is >> obviously not possible when there are incompatible versions of the same >> patchset floating around). >> >> > Application compiled on Fedora using the new features -> doesn't work on >> > other distribution >> >> And that's not a problem for OUR users, only for those of the other >> distribution. So why would that be ours to worry about? > > That's a problem for OUR users because when they use Fedora, they want to be > able to make a tarball of their software for their friend on Ubuntu to test. > Here, you're making Fedora a bad choice for developers that want to target > more than just Fedora. > If you exchange Fedora and Ubuntu, you will get the same valid statement. This is not about Fedora or Ubuntu. It's about you don't like diverse world where distributions differ. I have a good news for you: There are different operating sytems where executing foreign blobs is standard practice because there is exactly one distribution of the operating system. -- Petr -- 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: Summary/Minutes from today's FESCo Meeting (2015-10-07)
- Original Message -
> Bastien Nocera wrote:
> > 2 distributions add slightly different versions of the same functionality
> > -> incompatible
>
> I said that carrying more feature patches makes it "more likely" that
> packages from other distros will work, not "100% certain" (which is
> obviously not possible when there are incompatible versions of the same
> patchset floating around).
>
> > Application compiled on Fedora using the new features -> doesn't work on
> > other distribution
>
> And that's not a problem for OUR users, only for those of the other
> distribution. So why would that be ours to worry about?
That's a problem for OUR users because when they use Fedora, they want to be
able to make a tarball of their software for their friend on Ubuntu to test.
Here, you're making Fedora a bad choice for developers that want to target
more than just Fedora.
> > Your advice would be making Fedora a _worse_ distribution for third-party
> > developers, and you equate those third-party developers to developers of
> > proprietary applications.
>
> GCC supports __attribute__((deprecated("message"))) these days. So we can
> tag the added functions with something like:
> __attribute__((deprecated("nonstandard function added by a non-upstream
> patch to make FooApp work, use in other applications strongly
> discouraged")))
>
> If the developers opt to use those functions anyway, then that's not our
> problem.
This isn't made to tag symbols that aren't upstream, and the end-user
application
will just barf out with unresolved symbols when you try to run it, which is
far from useful.
> > Not all Free Software is easy to compile from source, not all Free
> > Software is packaged in Fedora. Forcing users to become packagers before
> > they can use a third-party software is detrimental to Fedora's success.
>
> I don't really agree, at least not fully. I think packaging software
> properly is a much more effective way to spend our time than making third-
> party blobs work as is, especially WHEN those binaries are actually Free
> Software and can thus be packaged properly from source.
Should I send you emails every time a software I want to use isn't packaged?
Because that's what it sounds like you want me to do :)
> Sure, the USERS
> should not have to become packagers, but the existing packagers should not
> waste their time on compatibility with binary blobs, but spend it usefully
> on packaging Free Software from source.
I'll ask something, in earnest: have you ever written and shipped non-trivial
software on Linux?
Because I don't think you would give those advices if you had.
--
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: how set InitialCC in pkgdb2 for new package
Il 13/10/2015 10:54, Pierre-Yves Chibon ha scritto: https://github.com/fedora-infra/pkgdb2/issues/192 This is fixed in 1.31 which is now running in prod:) Happy packaging! Pierre Thanks! gil -- 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: how set InitialCC in pkgdb2 for new package
On Mon, Oct 12, 2015 at 09:51:26PM +0200, gil wrote: > > > Il 08/10/2015 18:11, Pierre-Yves Chibon ha scritto: > >On Thu, Oct 08, 2015 at 04:57:27PM +0200, Vít Ondruch wrote: > >>Dne 8.10.2015 v 16:44 gil napsal(a): > >>>hi > >>>i missing somethings... > >>>how can set InitialCC with java-sig in pkgdb for a new package? > >>>regards > >>>thanks in advance > >>>gil > >>>https://admin.fedoraproject.org/pkgdb/package/requests/476 > >>>https://admin.fedoraproject.org/pkgdb/package/requests/477 > >>>https://admin.fedoraproject.org/pkgdb/package/requests/479 > >>https://github.com/fedora-infra/pkgdb2/issues/192 > >So the short answer is that it's not currently implemented because adding > >another user/group once the package is in pkgdb, the basic steps are: > >1. Go to one of your package > >2. Click on: Manage the `committers/watchers/admins` any of these > >3. There is then an ``Add someone`` button you can use > > > >There is currently a bug that's preventing pseudo-user (such as java-sig) > >from > >being added to a package, but I already have the fix and it'll be > >reviewed/merged/released asap :) > > > already done this procedure but i return this error "User "java-sig" is not > in the packager group" > https://github.com/fedora-infra/pkgdb2/issues/192 This is fixed in 1.31 which is now running in prod :) Happy packaging! Pierre -- 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 1271121] New: Upgrade perl-Starlet to 0.26
https://bugzilla.redhat.com/show_bug.cgi?id=1271121 Bug ID: 1271121 Summary: Upgrade perl-Starlet to 0.26 Product: Fedora Version: rawhide Component: perl-Starlet Keywords: FutureFeature Assignee: rc040...@freenet.de Reporter: ppi...@redhat.com QA Contact: extras...@fedoraproject.org CC: perl-de...@lists.fedoraproject.org, rc040...@freenet.de Latest Fedora delivers 0.25 version. Upstream released 0.26. Please upgrade. Also please enable release monitoring service to receive notification about future releases. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Eclipse fedorapackager plugin and it's future
On 10/08/2015 02:24 PM, Aleksandar Kurtakov wrote: > Hi everyone, > Fedorapackager eclipse plugin has been neglected for quite some time and > updates are broken after the Bodhi2 update. > So are there any users left? Is anyone interested in maintaining it? > Enhancing it? > Any feedback is more than welcome as it might be time to let it rest in peace > if no interest. I don't regularly use eclipse-fedorapackager, but I have a few enhancements on my TODO list (and as always, lacking time to actually implement them). Most important feature I have in mind - support for Copr. Java API is already included in Copr upstream at [1]. Michael Simacek is (or was) working on the GUI part. I think that this feature could help new contributors who are not familiar with packaging tools, but want to create or customize packages and publish them in Copr. (This would be integrated with DevAssistant too.) [1] https://git.fedorahosted.org/cgit/copr.git/tree/java (Personally I don't care about Bodhi2 support too much - I submit updates only like once a month or so.) > > Alexander Kurtakov > Red Hat Eclipse team > -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk -- 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: how set InitialCC in pkgdb2 for new package
On Tue, Oct 13, 2015 at 09:50:51AM +0200, Mikolaj Izdebski wrote: > On 10/08/2015 06:11 PM, Pierre-Yves Chibon wrote: > > On Thu, Oct 08, 2015 at 04:57:27PM +0200, Vít Ondruch wrote: > >> Dne 8.10.2015 v 16:44 gil napsal(a): > >>> hi > >>> i missing somethings... > >>> how can set InitialCC with java-sig in pkgdb for a new package? > >>> regards > >>> thanks in advance > >>> gil > >>> https://admin.fedoraproject.org/pkgdb/package/requests/476 > >>> https://admin.fedoraproject.org/pkgdb/package/requests/477 > >>> https://admin.fedoraproject.org/pkgdb/package/requests/479 > >> > >> https://github.com/fedora-infra/pkgdb2/issues/192 > > > > So the short answer is that it's not currently implemented because adding > > another user/group once the package is in pkgdb, the basic steps are: > > 1. Go to one of your package > > 2. Click on: Manage the `committers/watchers/admins` any of these > > 3. There is then an ``Add someone`` button you can use > > That's a lot of manual steps, especially if you need to add 3 or 4 users > to all new packages you create, like in my case. But this can be easily > scripted using pkgdb2 API (or with packagedb-cli tool). > > To make the whole process of adding new package scriptable, please > consider implementing API for requesting new packages too: > > https://github.com/fedora-infra/pkgdb2/issues/239 It's on the list ;-) Just hasn't made it to the top of it yet :) Pierre -- 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: how set InitialCC in pkgdb2 for new package
On 10/08/2015 06:11 PM, Pierre-Yves Chibon wrote: > On Thu, Oct 08, 2015 at 04:57:27PM +0200, Vít Ondruch wrote: >> Dne 8.10.2015 v 16:44 gil napsal(a): >>> hi >>> i missing somethings... >>> how can set InitialCC with java-sig in pkgdb for a new package? >>> regards >>> thanks in advance >>> gil >>> https://admin.fedoraproject.org/pkgdb/package/requests/476 >>> https://admin.fedoraproject.org/pkgdb/package/requests/477 >>> https://admin.fedoraproject.org/pkgdb/package/requests/479 >> >> https://github.com/fedora-infra/pkgdb2/issues/192 > > So the short answer is that it's not currently implemented because adding > another user/group once the package is in pkgdb, the basic steps are: > 1. Go to one of your package > 2. Click on: Manage the `committers/watchers/admins` any of these > 3. There is then an ``Add someone`` button you can use That's a lot of manual steps, especially if you need to add 3 or 4 users to all new packages you create, like in my case. But this can be easily scripted using pkgdb2 API (or with packagedb-cli tool). To make the whole process of adding new package scriptable, please consider implementing API for requesting new packages too: https://github.com/fedora-infra/pkgdb2/issues/239 > > There is currently a bug that's preventing pseudo-user (such as java-sig) from > being added to a package, but I already have the fix and it'll be > reviewed/merged/released asap :) FWIW, I successfully added java-sig to two of my packages yesterday using web UI: https://admin.fedoraproject.org/pkgdb/acl/$package/give/ -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
