Re: Schedule for Wednesday's FESCo Meeting (2013-11-13)
On Wed, Nov 13, 2013 at 5:34 AM, Kevin Fenzi wrote: > 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 '2013-10-23 18:00 UTC' > Two small typos above. Try date -d '2013-11-13 18:00 UTC' or just date -d '18:00 UTC' Fred -- 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 (2013-11-13)
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 '2013-10-23 18:00 UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #1185 Enable "-Werror=format-security" by default .fesco 1185 https://fedorahosted.org/fesco/ticket/1185 = New business = #topic #1195 WG autonomy .fesco 1195 https://fedorahosted.org/fesco/ticket/1195 #topic #1196 Set deadline for PRDs .fesco 1196 https://fedorahosted.org/fesco/ticket/1196 #topic #1198 Possible changes to Fedora EOL bug procedure .fesco 1198 https://fedorahosted.org/fesco/ticket/1198 #topic #1199 Ratify Base Working Group governance charter .fesco 1199 https://fedorahosted.org/fesco/ticket/1199 = 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. signature.asc Description: 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: Can we have better ssh fingerprint collision messages?
On Tue, Nov 12, 2013 at 01:24:16PM +0100, Reindl Harald wrote: > Am 12.11.2013 13:21, schrieb Matthew Miller: > > Harald, I'm not seeing the behavior you see either -- if I replace a host > > key with another one in known_hosts, I get the correct man-in-the-middle > > message > > interesting, i can reproduce this as often i want in case > i am doing it in the first one for the short hostname only > and leave the entry with the FQ and IP-address untouched Yeah, sure. That's the standard SSH behaviour. As far as it is concerned those are different hosts. If one wants to change that OpenSSH upstream would be the appropriate place to do that. I don't think such modifications should be made in distribution packages. Especially not without even trying to get upstream feedback on the issue. Lars -- 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 to handle non-free parts of a free software project
Manuel Faux (manuel.f...@conf.at) said: > I want to give the option to manually download the file, if one accepts > the non-free license of Oracle. Which file system path would be > appropriate to be prepared for that file? I would not feel comfortable > to add the file to add the file inside /usr/lib/jvm/... or something. This came up tangentially in the OpenH264 discussions - if you're intending to have mechanisms to automatically download non-free code to the system, please check with FESCo on how you intend to do this and handle it. Bill -- 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: Announcing the release of Fedora 20 Beta!
On Tue, Nov 12, 2013 at 9:57 AM, Dennis Gilmore wrote: > -BEGIN PGP SIGNED MESSAGE- > *** Note on performance *** > > Fedora development releases use a kernel with extra debug information to help > us understand and resolve issues faster; however, this can have a significant > impact on performance. Refer to the kernel debug strategy for more details. > You > can boot with slub_debug=- or use the kernel from nodebug repository to > disable > the extra debug info. This is inaccurate. The kernels we ship in Beta are typically not debug kernels. Booting with slub_debug=- on the Beta kernel is a no-op, and there isn't a nodebug repository for Branched. > *** Issues and Details *** > > Heisenbug Alpha is a testing release. To report issues encountered during Probably should have said Heisenbug Beta 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: New Bug Tracker Ready for Use (Finally)
On Tue, 12 Nov 2013 10:02:34 -0500 (EST) Kamil Paral wrote: > > After a bit more work than I was hoping and some email issues with > > RHIT (I haven't been working on this the _whole_ time :-P), I have > > a new phabricator instance up and running in the fedora cloud. > > > > https://phab.qadevel.cloud.fedoraproject.org/ > > Thanks. Do you intend to forward all ticket changes to qa-devel > mailing lists? I've been going back and forth on that one. On the one hand, that makes it much easier to follow what's going on. On the other hand, it makes quite a bit of noise on the list and I've never been a huge fan of getting 2 emails for every single email set out by trac on tickets I'm involved in. I suppose that I could just quit my whining and start using email filters that aren't quite so braindead as zimbra's, though. Other thoughts? Tim signature.asc Description: PGP signature ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
[Test-Announce] 2013-11-13 @ **17:00 UTC** - F20 Final Blocker Bug Review #1
# F20 Final Blocker Review meeting #1 # Date: 2013-11-13 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-blocker-review on irc.freenode.net It's time for the first Fedora 20 Final Blocker Review meeting! We'll be running through the final blockers and freeze exception bugs. To date we have 16 proposed blockers and 4 proposed FE's. The current list is available at: http://qa.fedoraproject.org/blockerbugs/current We'll be reviewing the bugs to determine ... 1. Whether they meet the beta release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria For guidance on Blocker and FreezeException bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process For the blocker review meeting protocol, see -https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you there! == // Mike Fedora QA irc: roshi | twitter: roshi_fedora blog: roshi.fedorapeople.org signature.asc Description: PGP signature ___ 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
Re: [Owner-change] Fedora packages ownership change
2013/11/12 Richard W.M. Jones : > On Mon, Nov 11, 2013 at 10:00:07AM +, nob...@fedoraproject.org wrote: >> erlang-riak_kv [EL-6] was orphaned by peter >> [and many more] > > I'm just about to take some of these erlang packages in EPEL 6. The > ones which are dependencies of RabbitMQ only. > > Does anyone object if I update these at will? I'm unclear on the ABI > requirements of Erlang, and whether or not this would cause problems > for users of the package(s) in EPEL. ABI will be broken in some cases indeed, but since almost nobody uses Erlang from EPEL I doubt if anyone will complain. -- With best regards, Peter Lemenkov. -- 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 989982] perl-SOAP-Lite-1.06 is available
https://bugzilla.redhat.com/show_bug.cgi?id=989982 Petr Šabata changed: What|Removed |Added Blocks||1029578 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1029578 [Bug 1029578] Review Request: perl-XMLRPC-Lite - Client and server implementation of XML-RPC protocol -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9BJiH8yLy4&a=cc_unsubscribe -- 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: Introducing Taskotron (the system formerly known as Taskbot)
On Tue, 12 Nov 2013 09:52:44 -0500 (EST) Kamil Paral wrote: > > tl;dr - taskbot is now taskotron > > The king is dead, long live the king! > > How do you pronounce taskotron? Same as > http://www.thefreedictionary.com/cyclotron ? I had been pronouncing it as task-əʊ-trʌn http://www.phon.ucl.ac.uk/home/wells/phoneticsymbolsforenglish.htm Tim signature.asc Description: PGP signature ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Self Introduction
- Original Message - > On Tue, Nov 12, 2013 at 11:56 PM, Ben Nemec wrote: > > > As I understand it, the original maintainer of the package isn't very > > active anymore (if at all), so I'm not sure that's going to be an option. > > The bug I opened for the new version has been sitting for over a month > > assigned to the current maintainer and there's been no response. Is there > > a policy on transferring ownership of an abandoned package? > > See: > > https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Thanks, I'll get started on that. -Ben -- 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: [Owner-change] Fedora packages ownership change
On Mon, Nov 11, 2013 at 10:00:07AM +, nob...@fedoraproject.org wrote: > erlang-riak_kv [EL-6] was orphaned by peter > [and many more] I'm just about to take some of these erlang packages in EPEL 6. The ones which are dependencies of RabbitMQ only. Does anyone object if I update these at will? I'm unclear on the ABI requirements of Erlang, and whether or not this would cause problems for users of the package(s) in EPEL. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones 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: Self Introduction
On Tue, Nov 12, 2013 at 11:56 PM, Ben Nemec wrote: > As I understand it, the original maintainer of the package isn't very active > anymore (if at all), so I'm not sure that's going to be an option. The bug I > opened for the new version has been sitting for over a month assigned to the > current maintainer and there's been no response. Is there a policy on > transferring ownership of an abandoned package? See: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers -- Yours sincerely, Christopher Meng Fєdоґa ї₴ al$о a кїпd оf нaт lїкє Яёd Haт. http://cicku.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
orphan/retire gradle
hi i decide to remove gradle form Fedora there are too many problems actually for maintain this package incompatible dependencies (gradle may require package versions no longer shipped in Fedora) or for e.g. conflicts with objectweb-asm 3.3.1 and 4.1 libraries https://bugzilla.redhat.com/show_bug.cgi?id=976330 https://bugzilla.redhat.com/show_bug.cgi?id=958008 https://bugzilla.redhat.com/show_bug.cgi?id=985702 regards 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: Self Introduction
- Original Message - > On 11/10/2013 06:48 PM, Ben Nemec wrote: > > Hi, > > > > I'm looking to become a co-maintainer on at least one package (and > > likely more in the near future), and I see one of the steps is an > > introduction to the list, so here goes: > > > > I was recently hired by Red Hat to work on the OpenStack project, and > > I've been involved to one extent or another with Linux and open > > source for about ten years now. I haven't done a ton of packaging > > work, but I did release rpms for one of my projects so I have some > > experience with it. > > > > My first package is up for review here: > > https://bugzilla.redhat.com/show_bug.cgi?id=1016943 and it's looking > > like I will be getting more involved in the packaging of > > OpenStack-related components soon, so I look forward to working with > > the Fedora community on that as well. And of course I will continue > > to scratch any itches that come up now that I'm using Fedora as my > > primary OS for work. :-) > > > Welcome to the team! > > Please note, you don't need to submit a package for review, if you'd > like to become a co-maintainer and the current maintainer will mentor you. As I understand it, the original maintainer of the package isn't very active anymore (if at all), so I'm not sure that's going to be an option. The bug I opened for the new version has been sitting for over a month assigned to the current maintainer and there's been no response. Is there a policy on transferring ownership of an abandoned package? -Ben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
I would like to become the owner of python3-cherrypy
Hi, according to [1] I should "Announce on devel which packages you would like to become the owner of." So that's it. The Review request is at [2]. [1] http://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers [2] https://bugzilla.redhat.com/show_bug.cgi?id=1029565 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] 389-ds-base_Debian_Wheezy - Build # 102 - Fixed!
389-ds-base_Debian_Wheezy - Build # 102 - Fixed: See attached build log for details. build.log Description: Binary data -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Announcing the release of Fedora 20 Beta!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Fedora 20 "Heisenbug" beta release has arrived with a preview of the latest fantastic, free, and open source technology currently under development. Take a peek inside: *** What is the Beta Release? *** The beta release is the last important milestone before the release of Fedora 20. A Beta release is code-complete and bears a very strong resemblance to the third and final release. Only critical bug fixes will be pushed as updates up to the general release of Fedora 20. The final release of Fedora 20 is expected in early December. Meanwhile, download the beta of Fedora 20 and help us make it even better: http://fedoraproject.org/get-prerelease We need your help to make Fedora 20 the best release yet, so please take some time to download and try out the beta and make sure the things that are important to you are working. If you find a bug, please report it – every bug you uncover is a chance to improve the experience for millions of Fedora users worldwide. Together, we can make Fedora 20 a rock-solid distribution. We have a culture of coordinating new features and pushing fixes upstream as much as feasible and your feedback will help improve not only Fedora but Linux and free software on the whole. (See the end of this announcement for more information on how to help.) Since it's a beta release, some problems may still be lurking. A list of problems that we already know about can be found at the Common F20 bugs page, found at http://fedoraproject.org/wiki/Common_F20_bugs. == 10 Years of Fedora == The Fedora 20 release coincides nicely with the 10th anniversary of Fedora. The first Fedora release (then called Fedora Core 1) came out on November 6, 2003. Since then, the Fedora Project has become an active and vibrant community that produces nearly a dozen "spins" that are tailor made for desktop users, hardware design, gaming, musicians, artists, and early classroom environments. == ARM as a Primary Architecture == While Fedora has supported a number of hardware architectures over the years, x86/x86_64 has been the default for the majority of Fedora users and for the Linux community in general. ARM, however, has been making massive strides. It already dominates the mobile market, and is becoming a go-to platform for hobbyists and makers, and is showing enormous promise for the server market as well. In keeping with Fedora's commitment to innovation, the Fedora community has been pushing to make ARM a primary architecture to satisfy the needs of users and developers targeting the ARM platform. *** Maturity and Advanced Features *** Sometimes it's not the big new features that make a users' experience better, it's the little enhancements or long-awaited tricky features that really help make a new release the bee's knees. === NetworkManager Improvements === NetworkManager is getting several improvements in Fedora 20 that will be welcome additions for power users and system administrators. Users will now be able to add, edit, delete, activate, and de-activate network connections via the nmcli command line tool, which will make life much easier for non-desktop uses of Fedora. NetworkManager is also getting support for bonding interfaces and bridging interfaces. Bonding and bridging are used in many enterprise setups and are necessary for virtualization and fail-over scenarios. === No Default Sendmail, Syslog === Fedora 20 removes some services that many users find unnecessary, though (of course) they will remain available as installable packages for users who might need them. The systemd journal now takes the place as the default logging solution, having been tested and able to manage persistent logging in place of syslog. Also, Sendmail will no longer be installed by default, as most Fedora installs have no need of a Mail Transfer Agent (MTA). === Cloud and Virtualization Improvements === The Fedora 20 release continues the Fedora tradition of adopting and integrating leading edge technologies used in cloud computing. This release includes a number of features that will make working with virtualization and cloud computing much easier. === First-Class Cloud Images === The Fedora Cloud SIG has been working hard on providing images that are well-suited to running as guests in public and private clouds like Amazon Web Services (AWS) and OpenStack. If you're using public or private cloud, you should definitely test-drive the beta images today! === OS Installer Support for LVM Thin Provisioning === LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation. === VM Snapshot UI with virt-manager === This change will make taking VM snapshots much easier. qemu and libvirt have all the major pieces in place for performing safe VM snapshots/checkpoints, however there isn
Re: unaccessability
No. - Original Message - > On 2013-11-11, Branislav Blaskovic wrote: > > Of course there have to be mentioned that the app is made for > > terminal. > > > BTW, is there an XDG way how to spawn an user-preferred terminal emulator > (and and application inside)? > > -- 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 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F-20 Branched report: 20131112 changes
Compose started at Tue Nov 12 09:15:02 UTC 2013 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client avro-thrift-1.7.5-1.fc20.noarch requires mvn(org.apache.thrift:libthrift) avro-thrift-1.7.5-1.fc20.noarch requires libthrift-java [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [condor-wallaby] condor-wallaby-client-5.0.3-5.fc20.noarch requires python-qpid-qmf >= 0:0.9.1073306 [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [glite-lb-common] glite-lb-common-9.0.7-2.fc20.armv7hl requires libclassad.so.5 [glpi] glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Version glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Stdlib glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-ServiceManager glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Loader glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-I18n glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Cache-apc glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Cache [gnome-do-plugins] gnome-do-plugins-thunderbird-0.8.4-14.fc20.armv7hl requires thunderbird [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) >= 0:0.16.0 [gradle] gradle-1.0-18.fc20.noarch requires plexus-container-default [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [htrace] htrace-2.03-2.fc20.noarch requires mvn(org.apache.thrift:libthrift) [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [mozilla-firetray] mozilla-firetray-thunderbird-0.3.6-0.5.143svn.fc18.1.armv7hl requires thunderbird >= 0:11 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc >= 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openlmi-providers] openlmi-0.4.0-1.fc20.noarch requires openlmi-power [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [pure] pure-doc-0.57-4.fc20.noarch requires pure = 0:0.57-4.fc20 [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.53.0 [qpid-cpp] qpid-cpp-server-ha-0.24-6.fc20.armv7hl requires qpid-qmf(armv7hl-32) qpid-tools-0.24-6.fc20.noarch requires python-qpid-qmf [rootplot] rootplot-2.2.1-7.fc19.noarch requires root-python [ruby-spqr] ruby-spqr-0.3.6-7.fc20.noarch requires ruby-qpid-qmf [rubygem-audited-activerecord] rubygem-audited-activerecord-3.0.0-3.fc19.noarch requires rubygem(activerecord) < 0:4 [scilab] scilab-doc-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 scilab-tests-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 [spacewalk-admin] spacewalk-admin-2.0.1-2.fc20.noarch requires sp
Re: unaccessability
On 2013-11-11, Branislav Blaskovic wrote: > Of course there have to be mentioned that the app is made for > terminal. > BTW, is there an XDG way how to spawn an user-preferred terminal emulator (and and application inside)? -- 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: Can we have better ssh fingerprint collision messages?
Am 12.11.2013 13:26, schrieb Tomas Mraz: > On Út, 2013-11-12 at 07:21 -0500, Matthew Miller wrote: >> On Tue, Nov 12, 2013 at 12:31:04PM +0100, Reindl Harald wrote: It can't... but you have to be sure you have edited any entries that may apply and that it is absolutely correct on the change ... frankly it's quicker and simpler to test via changing the target host's key rather than your known_hosts >>> and that this is needed shows IMHO a bug because it should >>> in all cases give out the same warning message >> >> Harald, I'm not seeing the behavior you see either -- if I replace a host >> key with another one in known_hosts, I get the correct man-in-the-middle >> message. > Exactly, I verified that too. But I actually first made a mistake by > deleting the 'ssh-rsa' and not copying it from the other host entry > which made the line invalid and the message was the same as for first > contact with the server. So I wonder if Harald did the same mistake see below the difference in "known_hosts", the third line with the used hostname [harry@rh:~/.ssh]$ ssh harry@srv-rhsoft The authenticity of host '[srv-rhsoft]:22 ([62.178.102.6]:22)' can't be established. RSA key fingerprint is 4d:64:fa:f7:78:ac:f2:2d:59:4d:59:35:5d:a2:ca:70. Are you sure you want to continue connecting (yes/no)? _ before: local ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== local.rhsoft.net ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== srv-rhsoft ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== srv-rhsoft.rhsoft.net ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== ns3 ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== ns3.rhsoft.net ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== 62.178.102.6 ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== _ now: local ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== local.rhsoft.net ssh-rsa B3NzaC1yc2EBIwAAAQEAzTBd2hor7lh2ien9j9ghkrqNGIh0t3AbUfwlABMnHIcSA9CATSctmwfHWkjob9CLCYIVF38hQPAbvSV9WyNu2BGHzuiXPPnvIxM06U4ot6Xs8B0Wcj3MtrBzbMCcl1b6tVNREPSwxDiUiDdmWgQpkbFIr+qX/D7CrJLfc5ON/VF/ZSe46hJw8YUoDa19hCXfZe0P4UK9iXLfhrjPKMl+x6/2F/CKwmtAdCXpWd1D3M/fozTSjiG2BBszWTZFCDKdtBOhB2tpndyzatkpFR6Ik7JR5/YzwZghayWs9PZyOb7M4RHnPAzZX0yy9lrHyi+///VKSyxv2xUxXXGc6AiBhw== srv-rhsoft
Re: Can we have better ssh fingerprint collision messages?
On 11/12/2013 08:42 AM, valent.turko...@gmail.com wrote: I work a lot with different kind of routers, openwrt and other embedded systems, and they all usually use same address - 192.168.1.1, so Ubuntu message is quite useful because gives me simple command that I just copy/paste so I can get rid of old finderprint and I can connect to new device with same IP but obviously different ssh fingerprint. 1) I get same message on Fedora. Not sure how you think that Ubuntu differs. 2) if you know that some machines change fingerprint and you *trust it* you can do: ~/.ssh/config: Host 192.168.1.1 UserKnownHostsFile /dev/null -- Miroslav Suchy, RHCE, RHCDS Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys -- 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: Can we have better ssh fingerprint collision messages?
On Út, 2013-11-12 at 07:21 -0500, Matthew Miller wrote: > On Tue, Nov 12, 2013 at 12:31:04PM +0100, Reindl Harald wrote: > > > It can't... but you have to be sure you have edited any entries that may > > > apply and that it is absolutely correct on > > > the change ... frankly it's quicker and simpler to test via changing the > > > target host's key rather than your > > > known_hosts > > and that this is needed shows IMHO a bug because it should > > in all cases give out the same warning message > > Harald, I'm not seeing the behavior you see either -- if I replace a host > key with another one in known_hosts, I get the correct man-in-the-middle > message. Exactly, I verified that too. But I actually first made a mistake by deleting the 'ssh-rsa' and not copying it from the other host entry which made the line invalid and the message was the same as for first contact with the server. So I wonder if Harald did the same mistake. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb (You'll never know whether the road is wrong though.) -- 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: Can we have better ssh fingerprint collision messages?
Am 12.11.2013 13:21, schrieb Matthew Miller: > On Tue, Nov 12, 2013 at 12:31:04PM +0100, Reindl Harald wrote: >>> It can't... but you have to be sure you have edited any entries that may >>> apply and that it is absolutely correct on >>> the change ... frankly it's quicker and simpler to test via changing the >>> target host's key rather than your >>> known_hosts >> and that this is needed shows IMHO a bug because it should >> in all cases give out the same warning message > > Harald, I'm not seeing the behavior you see either -- if I replace a host > key with another one in known_hosts, I get the correct man-in-the-middle > message interesting, i can reproduce this as often i want in case i am doing it in the first one for the short hostname only and leave the entry with the FQ and IP-address untouched openssh-clients-6.2p2-5.fc19.x86_64 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: Can we have better ssh fingerprint collision messages?
On Tue, Nov 12, 2013 at 12:31:04PM +0100, Reindl Harald wrote: > > It can't... but you have to be sure you have edited any entries that may > > apply and that it is absolutely correct on > > the change ... frankly it's quicker and simpler to test via changing the > > target host's key rather than your > > known_hosts > and that this is needed shows IMHO a bug because it should > in all cases give out the same warning message Harald, I'm not seeing the behavior you see either -- if I replace a host key with another one in known_hosts, I get the correct man-in-the-middle message. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- 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: Can we have better ssh fingerprint collision messages?
Am 12.11.2013 12:25, schrieb James Hogarth: > Did you edit the key for both the IP address and the hostname in known_hosts? no, because i tried to show in which cases the message the OP wnats to see is *not* given > It's feasible that if you only changed the hostname and not the IP based one > behaviour would be different. > > Indeed if I just ssh-keygen -R fqdn and then ssh to a box after the key has > changed there will be similar > complaints as it verifies on the latter too. > > and now you can explain me where is the difference in the key on the > server has changed and having a different but valid key than the > servers one on "known_hosts" > > It can't... but you have to be sure you have edited any entries that may > apply and that it is absolutely correct on > the change ... frankly it's quicker and simpler to test via changing the > target host's key rather than your > known_hosts and that this is needed shows IMHO a bug because it should in all cases give out the same warning message 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: Can we have better ssh fingerprint collision messages?
On 12 November 2013 09:40, Reindl Harald wrote: > jesus christ *from* "AAA" *to* "==" means *the whole valid key* > because quote two complete keys is a little bit long > > so what is there invalid > > Reindl please calm down ... step away from the keyboard then come back in fresh temperament. If you re-read your original message it is somewhat ambiguous as it can easily be read (and indeed I first read it as) that you changed AAA to == ... ie just those characters. > you ssh command must have some magic that it can distinct if the > server changed it's key or the one in "known_hosts" > > Did you edit the key for both the IP address and the hostname in known_hosts? It's feasible that if you only changed the hostname and not the IP based one behaviour would be different. Indeed if I just ssh-keygen -R fqdn and then ssh to a box after the key has changed there will be similar complaints as it verifies on the latter too. > and now you can explain me where is the difference in the key on the > server has changed and having a different but valid key than the > servers one on "known_hosts" > It can't... but you have to be sure you have edited any entries that may apply and that it is absolutely correct on the change ... frankly it's quicker and simpler to test via changing the target host's key rather than your known_hosts. James -- 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 Base Design WG] Committee FESCO approved, next steps
On Wed, Nov 06, 2013 at 02:41:25PM +0100, Phil Knirsch wrote: > On 11/06/2013 05:43 AM, Jon wrote: > Right, release cycle will definitely be a hot topic, and i'd like us to Maybe too early, it's probably better to answer "what do you want to release" before you choice the right release cycle :-) It means -- what is QA role, how important is upstream role, do you want to backport often, how stable code is expected, how important are a new features, do you have man-power for all your dreams? > investigate different types as well, e.g. not a time based but a major > feature based cycle (e.g. new upstream kernel -> new release), continuous, +1 I can imagine that we will synchronize (for example) kernel + util-linux + udev + systemd upgrades for the Fedora Base upgrade, NACK feature backports and fix only "really important bugs" in already released Base packages. > support time for releases, what about feature backports and so forth. Lots > revolving around those topics i think. > > One request i also already got was if we in the Base WG could take a look at > containers/sandboxes for applications as well. Basically so that the > technology could be used by any derived product built on top of Base. And as > there are currently multiple competing technologies being worked on > (docker.io, systemd containers, libvirt-lxc, openshift cartridges) we'd need > to evaluate those and decide which one(s) we'd want to offer as a "standard" > from the Base product. From long term point of view I'm almost sure that we will see tendency to add more and more packages to the Base ;-) Karel -- Karel Zak http://karelzak.blogspot.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
Re: Can we have better ssh fingerprint collision messages?
Am 12.11.2013 03:11, schrieb Chris Adams: > Once upon a time, Reindl Harald said: >> these lines are not written by hand and i replaced the key from "AAA" to "==" >> of the first one with the key off a completly different host in the file >> resulting in the message i posted by ssh "harry@srv-rhsoft" > > Replacing characters is making entries "by hand". Replacing the first > characters with "==" creates an invalid key (it is base64 encoded which > cannot have "=" characters except at the end for padding as needed); it > could be OpenSSH ignores invalid lines (I don't know). jesus christ *from* "AAA" *to* "==" means *the whole valid key* because quote two complete keys is a little bit long so what is there invalid >>> If there is no match to the host, you get the output you described; if >>> there is a match but the key is different, you get the original poster's >>> desired output. This is standard (and I believe non-configurable) >>> OpenSSH behavior going back to the beginning (and IIRC to the original >>> SSH code before OpenSSH started) >> >> and as i have proven this is *not true* in all situations - period > > That is incorrect. The way to "prove" it is to connect to a host, > change its host key (easiest way is to move /etc/ssh/*key* aside and > restart sshd), and connect again. you ssh command must have some magic that it can distinct if the server changed it's key or the one in "known_hosts" > Otherwise, show a case that didn't involve editing the known_hosts file. > The OpenSSH code only works one way and now you can explain me where is the difference in the key on the server has changed and having a different but valid key than the servers one on "known_hosts" 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: How to handle non-free parts of a free software project
On Tue, 12 Nov 2013 10:25:16 +0100 drago01 wrote: > On Tue, Nov 12, 2013 at 10:16 AM, Manuel Faux > wrote: > > > I little bit more feedback would be welcome. > > > > You don't agree to give the option to manually download the file at > > all, or don't you agree with NOT packing the file > > to /usr/lib/jvm/...? > > > > By not giving the option to manually link to the file we will loose > > the functionality to create Java Web Start war files at all. Also > > other packages require the user to get some non-free files for some > > specific non-crucial functionality. > > Can't you place it somewhere in the users home directory? > ~/.netbeans/xyz ? That's how other packages handle that (eclipse > plugins, firefox plugins etc). Yes, it's possible. If this is common practice, I will realize it in that way. I think there would be an advantage if it would be at a more central place, so that multi-user systems just need it once, but I don't want to go a different way than other packages. > > > Just pretend to "downvote" something without any comment does not > > help anyone at all. > > Indeed "+1" and "-1" mails are just spam. -- 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 to handle non-free parts of a free software project
On Tue, Nov 12, 2013 at 10:16 AM, Manuel Faux wrote: > I little bit more feedback would be welcome. > > You don't agree to give the option to manually download the file at all, > or don't you agree with NOT packing the file to /usr/lib/jvm/...? > > By not giving the option to manually link to the file we will loose the > functionality to create Java Web Start war files at all. Also other > packages require the user to get some non-free files for some specific > non-crucial functionality. Can't you place it somewhere in the users home directory? ~/.netbeans/xyz ? That's how other packages handle that (eclipse plugins, firefox plugins etc). > Just pretend to "downvote" something without any comment does not help > anyone at all. Indeed "+1" and "-1" mails are just spam. -- 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 to handle non-free parts of a free software project
On Tue, 12 Nov 2013 09:56:47 +0100 "punto...@libero.it" wrote: > Il 12/11/2013 08:37, Manuel Faux ha scritto: > > On Tue, 12 Nov 2013 08:11:12 +0100 > > Manuel Faux wrote: > > > >> On Mon, 11 Nov 2013 15:08:10 -0800 > >> Toshio Kuratomi wrote: > >> > >>> On Tue, Nov 12, 2013 at 12:22:16AM +0200, Elad Alfassa wrote: > On Tue, Nov 12, 2013 at 12:13 AM, Manuel Faux > wrote: > > NetBeans 7.4 requires a file called jnlp-servlet.jar which > is part of the Oracle JDK and itself non-free licensed. The file > is not required for building, but for specific functions of the > software. > > > More concrete, the file is required if "one wants to build a > packaged war file of JNLP version of a suite". > > It seems like only the class > jnlp.sample.servlet.JnlpDownloadServlet is required, but I could > not find it in the OpenJKD. > > How is this normally handled? Should we add a file to the > docs which describes that for this specific functionality that > file is required? > Manuel > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: > http://fedoraproject.org/code-of-conduct > > > > The answer is simple. Remove the file. Don't distribute it in > Fedora. Have a README.fedora file in /usr/share/docs/netbeans (or > whatever) which explains that this file was removed due to > licensing issues and how to get it. > > I want to give the option to manually download the file, if one > > accepts the non-free license of Oracle. Which file system path > > would be appropriate to be prepared for that file? I would not feel > > comfortable to add the file to add the file inside /usr/lib/jvm/... > > or something. > > > > Manuel > -1 I little bit more feedback would be welcome. You don't agree to give the option to manually download the file at all, or don't you agree with NOT packing the file to /usr/lib/jvm/...? By not giving the option to manually link to the file we will loose the functionality to create Java Web Start war files at all. Also other packages require the user to get some non-free files for some specific non-crucial functionality. Just pretend to "downvote" something without any comment does not help anyone at all. > >>> Depending on the license, you may just need to remove the file in > >>> the spec file or you may need to clean it from the tarball before > >>> that tarball is uploaded to the lookaside cache (via fedpkg > >>> new-sources). > >>> > >>> You may also need to patch the software so that it gracefully > >>> handles the lack of that file at runtime. Perhaps removing the > >>> menu entry that won't function or popping up a dialog to explain > >>> that the netbeans we ship can't use that non-free functionality. > >>> > >>> -Toshio > >> Thanks for your input. > >> > >> I already asked in the legal mailing list, and it was suggested > >> that I might ask at Oracle if they change the license in a way > >> that it complies to free software. But even if they would do it, > >> it would take some time, and I don't want to wait for that. So in > >> between I will go on by just don't shipping that file. > >> > >> Manuel > -- 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: Can we have better ssh fingerprint collision messages?
On Tue, Nov 12, 2013 at 08:42:06AM +0100, valent.turko...@gmail.com wrote: > I work a lot with different kind of routers, openwrt and other > embedded systems, and they all usually use same address - 192.168.1.1, > so Ubuntu message is quite useful because gives me simple command that > I just copy/paste so I can get rid of old finderprint and I can > connect to new device with same IP but obviously different ssh > fingerprint. I see the message on Fedora that you say only occurs only on Ubuntu. Can you show the precise output you see on your Fedora machine when there is a key mismatch? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ -- 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: Can we have better ssh fingerprint collision messages?
Quoting valent.turko...@gmail.com (2013-11-12 08:42:06) > I work a lot with different kind of routers, openwrt and other > embedded systems, and they all usually use same address - 192.168.1.1, > so Ubuntu message is quite useful because gives me simple command that > I just copy/paste so I can get rid of old finderprint and I can > connect to new device with same IP but obviously different ssh > fingerprint. 1. Don't top-post 2. I hope I'll never be at mercy of administrators like you who copy-paste commands because that's what they are told to. 3. The message appears whenever there is a change in ssh host key for given address. On Fedora as well. If you can't reproduce, you didn't change the host key or you are really connecting to a different host -- Stanislav Ochotnicky Software Engineer - Developer Experience PGP: 7B087241 Red Hat Inc. http://cz.redhat.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
Re: How to handle non-free parts of a free software project
Il 12/11/2013 08:37, Manuel Faux ha scritto: On Tue, 12 Nov 2013 08:11:12 +0100 Manuel Faux wrote: On Mon, 11 Nov 2013 15:08:10 -0800 Toshio Kuratomi wrote: On Tue, Nov 12, 2013 at 12:22:16AM +0200, Elad Alfassa wrote: On Tue, Nov 12, 2013 at 12:13 AM, Manuel Faux wrote: NetBeans 7.4 requires a file called jnlp-servlet.jar which is part of the Oracle JDK and itself non-free licensed. The file is not required for building, but for specific functions of the software. More concrete, the file is required if "one wants to build a packaged war file of JNLP version of a suite". It seems like only the class jnlp.sample.servlet.JnlpDownloadServlet is required, but I could not find it in the OpenJKD. How is this normally handled? Should we add a file to the docs which describes that for this specific functionality that file is required? Manuel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct The answer is simple. Remove the file. Don't distribute it in Fedora. Have a README.fedora file in /usr/share/docs/netbeans (or whatever) which explains that this file was removed due to licensing issues and how to get it. I want to give the option to manually download the file, if one accepts the non-free license of Oracle. Which file system path would be appropriate to be prepared for that file? I would not feel comfortable to add the file to add the file inside /usr/lib/jvm/... or something. Manuel -1 Depending on the license, you may just need to remove the file in the spec file or you may need to clean it from the tarball before that tarball is uploaded to the lookaside cache (via fedpkg new-sources). You may also need to patch the software so that it gracefully handles the lack of that file at runtime. Perhaps removing the menu entry that won't function or popping up a dialog to explain that the netbeans we ship can't use that non-free functionality. -Toshio Thanks for your input. I already asked in the legal mailing list, and it was suggested that I might ask at Oracle if they change the license in a way that it complies to free software. But even if they would do it, it would take some time, and I don't want to wait for that. So in between I will go on by just don't shipping that file. Manuel <>-- 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: Copr
On 11/11/2013 10:08 PM, Zbigniew Jędrzejewski-Szmek wrote: Would it be possible to provide an rpm with the .repo file automatically? (I mean something like fedora-release-rawhide, so that the user can do rpm -ivhhttp://http://copr-fe.cloud.fedoraproject.org/coprs//.../copr---1.noarch instead of copy-pasting the repo file.) Then "installation instructions" could be filled in automatically by copr, since they'd become very generic. Yes. I have idea that Copr would generate rpm for each repository. And then put that those rpm in one repo. And genarete rpm for .repo file. So we would have repository of repositories :) And you would be able to do: rpm -Uvh copr-repos.rpm yum install msuchy-myproject-repo yum install package-from-myproject I wanted to change the name of a package. How can I delete the old package from my copr repo? You could not. Sorry. I have it on my TODO list. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Agenda for today's Env-and-Stacks WG meeting (2013-11-12)
My apologies for the last minute agenda. We'll be holding our initial WG meeting today at 13:00 UTC in #fedora-meeting on Freenode. We'll cover the various items below. I will try and keep the meeting under 1 hour. == Next Steps == - Discussions around the WG governance charter based on Toshio's proposal - PRD == 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
[perl-SOAP-Lite] Add a missing, undetected runtime dependency on LWP::UserAgent
commit 66d02c32226968f44f1e37128fde329107a14bdb
Author: Petr Šabata
Date: Tue Nov 12 17:33:04 2013 +0900
Add a missing, undetected runtime dependency on LWP::UserAgent
perl-SOAP-Lite.spec |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
---
diff --git a/perl-SOAP-Lite.spec b/perl-SOAP-Lite.spec
index db7c99d..eb7c5e7 100644
--- a/perl-SOAP-Lite.spec
+++ b/perl-SOAP-Lite.spec
@@ -1,6 +1,6 @@
Name: perl-SOAP-Lite
Version:1.06
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Client and server side SOAP implementation
License:GPL+ or Artistic
Group: Development/Libraries
@@ -36,6 +36,7 @@ Requires: perl(Compress::Zlib)
Requires: perl(Encode)
Requires: perl(HTTP::Headers)
Requires: perl(HTTP::Request)
+Requires: perl(LWP::UserAgent)
Requires: perl(MIME::Base64)
Requires: perl(MIME::Entity)
Requires: perl(XML::Parser)
@@ -75,6 +76,9 @@ make test
%{_mandir}/man1/*
%changelog
+* Tue Nov 12 2013 Petr Šabata - 1.06-2
+- Add a missing, undetected runtime dependency on LWP::UserAgent
+
* Tue Nov 12 2013 Petr Šabata - 1.06-1
- 1.06 bump
- SOAP::Transport::TCP is back
--
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: How to handle non-free parts of a free software project
Il 12/11/2013 08:11, Manuel Faux ha scritto: On Mon, 11 Nov 2013 15:08:10 -0800 Toshio Kuratomi wrote: On Tue, Nov 12, 2013 at 12:22:16AM +0200, Elad Alfassa wrote: On Tue, Nov 12, 2013 at 12:13 AM, Manuel Faux wrote: NetBeans 7.4 requires a file called jnlp-servlet.jar which is part of the Oracle JDK and itself non-free licensed. The file is not required for building, but for specific functions of the software. More concrete, the file is required if "one wants to build a packaged war file of JNLP version of a suite". It seems like only the class jnlp.sample.servlet.JnlpDownloadServlet is required, but I could not find it in the OpenJKD. How is this normally handled? Should we add a file to the docs which describes that for this specific functionality that file is required? Manuel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct The answer is simple. Remove the file. Don't distribute it in Fedora. Have a README.fedora file in /usr/share/docs/netbeans (or whatever) which explains that this file was removed due to licensing issues and how to get it. +1 Depending on the license, you may just need to remove the file in the spec file or you may need to clean it from the tarball before that tarball is uploaded to the lookaside cache (via fedpkg new-sources). You may also need to patch the software so that it gracefully handles the lack of that file at runtime. Perhaps removing the menu entry that won't function or popping up a dialog to explain that the netbeans we ship can't use that non-free functionality. -Toshio Thanks for your input. I already asked in the legal mailing list, and it was suggested that I might ask at Oracle if they change the license in a way that it complies to free software. But even if they would do it, it would take some time, and I don't want to wait for that. So in between I will go on by just don't shipping that file. Manuel <>-- 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: Self Introduction
On 11/10/2013 06:48 PM, Ben Nemec wrote: > Hi, > > I'm looking to become a co-maintainer on at least one package (and > likely more in the near future), and I see one of the steps is an > introduction to the list, so here goes: > > I was recently hired by Red Hat to work on the OpenStack project, and > I've been involved to one extent or another with Linux and open > source for about ten years now. I haven't done a ton of packaging > work, but I did release rpms for one of my projects so I have some > experience with it. > > My first package is up for review here: > https://bugzilla.redhat.com/show_bug.cgi?id=1016943 and it's looking > like I will be getting more involved in the packaging of > OpenStack-related components soon, so I look forward to working with > the Fedora community on that as well. And of course I will continue > to scratch any itches that come up now that I'm using Fedora as my > primary OS for work. :-) > Welcome to the team! Please note, you don't need to submit a package for review, if you'd like to become a co-maintainer and the current maintainer will mentor you. Matthias -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
