Re: AppData - how to properly handle them
On Tue, 2013-12-24 at 03:03 +0100, Miro Hrončok wrote: > How does GNOME Software knows about appdata files in non installed > packages? > > I mean - is it all stored > in /usr/share/app-info/xmls/fedora-20.xml.gz? > > Or is it in the repository somewhere? Currently Richard generates this appdata from *all* fedora packages (and sundry files in the github repo[1]) and ships the metadata files in the gnome-software related packages. In the future, this will hopefully be integrated with koji etc. and be done automatically. I don't know the status of this yet. > When I upgrade my package to add/modify appdata, should I do anything > else? No. You don't need to do anything. Whenever Richard re-runs his compose, the updates will be pulled in. > > Will other repos than the official provide appdata as well? If no, is > it > possible to do it somehow? E.g. for rpmfusion or repos in Copr? They can. Please read: https://blogs.gnome.org/hughsie/2013/10/16/how-to-generate-appstream-metadata-for-fedora/ [1] https://github.com/hughsie/fedora-appstream -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG signature.asc Description: This is a digitally signed message part -- 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: AppData - how to properly handle them
On Tue, 2013-12-24 at 02:55 +0100, Miro Hrončok wrote: > 1) Should the package with foo.appdata.xml require some package that > owns /usr/share/appdata? (and do we have such package) It's OK to co-own the /usr/share/appdate directory https://fedoraproject.org/wiki/Packaging:Guidelines#The_directory_is_owned_by_a_package_which_is_not_required_for_your_package_to_function > > 2) Should I run appdata-validate in %check? Richard runs this when generating the metadata from appdata files already. Please do run it before you add your appdata file to the package or submit it upstream. > > 3) Do we have guidelines for this? Not yet. -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG signature.asc Description: This is a digitally signed message part -- 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: AppData - how to properly handle them
And more questions: How does GNOME Software knows about appdata files in non installed packages? I mean - is it all stored in /usr/share/app-info/xmls/fedora-20.xml.gz? Or is it in the repository somewhere? When I upgrade my package to add/modify appdata, should I do anything else? Will other repos than the official provide appdata as well? If no, is it possible to do it somehow? E.g. for rpmfusion or repos in Copr? I was trying to search those info somewhere, but I think this is either totally undocumented or deep in mailing list archive. There is nathing relevant about appdata on wiki. -- 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
AppData - how to properly handle them
Hi, I'm playing a bit with GNOME Software and I have questions about AppData files. 1) Should the package with foo.appdata.xml require some package that owns /usr/share/appdata? (and do we have such package) 2) Should I run appdata-validate in %check? 3) Do we have guidelines for this? -- 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
[Owner-change] Fedora packages ownership change
Change in ownership over the last 168 hours === 1 packages were orphaned nvclock [devel,f18,f19,f20] was orphaned by drago01 Utility that allows users to overclock NVIDIA based video cards https://admin.fedoraproject.org/pkgdb/acls/name/nvclock 6 packages unorphaned - xqueraltunorphaned : openstack-nova [EL-6,devel,f18,f19,f20] cicku unorphaned : gpodder [EL-6] jkoncickunorphaned : tcsh [devel] amluto unorphaned : fish [devel] nalimilan unorphaned : double-conversion [devel] besser82unorphaned : wordnet [EL-5,f18] 4 packages were retired mate-file-manager-share [devel] was retired by raveit65 Easy sharing folder via Samba (CIFS protocol) https://admin.fedoraproject.org/pkgdb/acls/name/mate-file-manager-share cpan-upload [devel] was retired by mmaslano Automate the uploading of files to the CPAN (PAUSE) https://admin.fedoraproject.org/pkgdb/acls/name/cpan-upload mate-document-viewer [devel] was retired by raveit65 Document viewer https://admin.fedoraproject.org/pkgdb/acls/name/mate-document-viewer python-trml2pdf [devel,f20] was retired by ciupicri Tiny RML2PDF is a tool to easily create PDF documents without programming https://admin.fedoraproject.org/pkgdb/acls/name/python-trml2pdf 4 packages changed owner limbgave to nalimilan : double-conversion [f19,f20] limbgave to zultron: libmodbus [EL-6] limbgave to amluto : fish [f19,f20] limbgave to farnz : python-gstreamer1 [f20] Sources: https://github.com/pypingou/fedora-owner-change -- 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: FDO and LTO (optimizations)
On Fri, 2013-12-20 at 14:10 -0500, Neal Becker wrote: > I was reading some of the discussion of feedback directed optimization and > link > time optimization for python here: > > http://permalink.gmane.org/gmane.comp.python.devel/143941 > > I'm wondering if Fedora should be enabling some of these optimizations? We discussed doing this a while back for CPython in Fedora; it's probably worthwhile, but AFAIK no-one's gotten around to it. I filed a couple of bugs to track this: Python 2: https://bugzilla.redhat.com/show_bug.cgi?id=613045 Python 3: https://bugzilla.redhat.com/show_bug.cgi?id=613046 so if someone wants to try to implement this, that would be great. IIRC the upstream makefile already has a pre-canned way to do at least the PGO of this - but we'd need to set things up so that there's a "training" run to generate the profile data for the PGO build. I'd recommend using the upstream Python benchmarking suite: http://hg.python.org/benchmarks since it contains examples of real, idiomatic code, rather than made-up benchmarks, and hence is likely to be good "training" for the PGO. IIRC Debian's builds already do something like this. [FWIW, note that LTO has seen some big improvements in gcc upstream, which should land within the upcoming 4.9] Hope this is helpful Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20131223 changes
Compose started at Mon Dec 23 05:15:03 UTC 2013 Broken deps for i386 -- [InsightToolkit] InsightToolkit-4.4.2-4.fc21.i686 requires libRlapack.so InsightToolkit-4.4.2-4.fc21.i686 requires libRblas.so [LuxRender] LuxRender-1.0-16.fc21.i686 requires libImath-2_0.so.10 LuxRender-1.0-16.fc21.i686 requires libIlmThread-2_0.so.10 LuxRender-1.0-16.fc21.i686 requires libIlmImf-Imf_2_0.so.20 LuxRender-1.0-16.fc21.i686 requires libIex-2_0.so.10 LuxRender-1.0-16.fc21.i686 requires libHalf.so.10 LuxRender-core-1.0-16.fc21.i686 requires libImath-2_0.so.10 LuxRender-core-1.0-16.fc21.i686 requires libIlmThread-2_0.so.10 LuxRender-core-1.0-16.fc21.i686 requires libIlmImf-Imf_2_0.so.20 LuxRender-core-1.0-16.fc21.i686 requires libIex-2_0.so.10 LuxRender-core-1.0-16.fc21.i686 requires libHalf.so.10 LuxRender-lib-1.0-16.fc21.i686 requires libImath-2_0.so.10 LuxRender-lib-1.0-16.fc21.i686 requires libIlmThread-2_0.so.10 LuxRender-lib-1.0-16.fc21.i686 requires libIlmImf-Imf_2_0.so.20 LuxRender-lib-1.0-16.fc21.i686 requires libIex-2_0.so.10 LuxRender-lib-1.0-16.fc21.i686 requires libHalf.so.10 [OpenEXR_CTL] OpenEXR_CTL-1.0.1-16.fc20.i686 requires libImath.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmThread.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmImf.so.7 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIexMath.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIex.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libHalf.so.6 OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIlmThread.so.6 OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIlmImf.so.7 OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIex.so.6 [OpenEXR_Viewers] OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libImath-2_0.so.10 OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIlmThread-2_0.so.10 OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIlmImf-Imf_2_0.so.20 OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIexMath-2_0.so.10 OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libIex-2_0.so.10 OpenEXR_Viewers-2.0.1-3.fc21.i686 requires libHalf.so.10 [R-maanova] R-maanova-1.30.0-2.fc20.i686 requires libRlapack.so R-maanova-1.30.0-2.fc20.i686 requires libRblas.so [R-msm] R-msm-1.1.4-2.fc20.i686 requires libRlapack.so R-msm-1.1.4-2.fc20.i686 requires libRblas.so [aime] aime-7.20131209-1.fc21.i686 requires /usr/sbin/install-info aime-7.20131209-1.fc21.i686 requires /usr/sbin/install-info [bijiben] bijiben-3.11.1-1.fc21.i686 requires libtracker-sparql-0.16.so.0 [brasero] brasero-3.11.3-1.fc21.i686 requires libtracker-sparql-0.16.so.0 [converseen] converseen-0.6.2-2.fc20.i686 requires libMagick++-6.Q16.so.1 [derelict] derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod [dmapd] dmapd-0.0.55-5.fc21.i686 requires libImath-2_0.so.10 dmapd-0.0.55-5.fc21.i686 requires libIlmThread-2_0.so.10 dmapd-0.0.55-5.fc21.i686 requires libIlmImf-Imf_2_0.so.20 dmapd-0.0.55-5.fc21.i686 requires libIexMath-2_0.so.10 dmapd-0.0.55-5.fc21.i686 requires libIex-2_0.so.10 dmapd-0.0.55-5.fc21.i686 requires libHalf.so.10 [dragonegg] dragonegg-3.3-11.fc21.i686 requires gcc = 0:4.8.2-1.fc21 [drawtiming] drawtiming-0.7.1-11.fc20.i686 requires libMagick++-6.Q16.so.1 [enblend] enblend-4.1.2-3.fc21.i686 requires libvigraimpex.so.4 [evolution-rss] 1:evolution-rss-0.3.94-2.fc21.i686 requires libcamel-1.2.so.46 [gammaray] gammaray-1.3.2-1.fc21.i686 requires libRlapack.so gammaray-1.3.2-1.fc21.i686 requires libRblas.so [gnome-packagekit] gnome-packagekit-3.11.3-1.fc21.i686 requires PackageKit-libs(x86-32) >= 0:0.5.0 [gnome-shell] gnome-shell-3.11.2-3.fc21.i686 requires libgnome-bluetooth-applet.so.0 [gnome-shell-extensions] gnome-shell-extension-common-3.11.3-1.fc21.noarch requires gnome-shell >= 0:3.11.3 [gnome-user-share] gnome-user-share-3.10.1-1.fc21.i686 requires libgnome-bluetooth.so.12 [gpsdrive] gpsdrive-2.11-20.fc20.i686 requires libgps.so.20 [grilo-plugins] grilo-plugins-0.2.9-2.fc21.i686 requires libtracker-sparql-0.16.so.0 [gtkd] gtkd-2.0.0-29.20120815git9ae9181.fc18.i686 requires libphobos-ldc.so.60 [httpdtap] httpdtap-0.2-2.fc21.noarch requires kernel-debuginfo httpdtap-0.2-2.fc21.noarch requires httpd-debuginfo httpdtap-0.2-2.fc21.noarch requires apr-util-debuginfo httpdtap-0.2-2.fc21.noarch requires apr-debuginfo [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [libghemical] libgh
Orphaning packages
Hi all, Due to lack of time I'm orphaning the following packages: - pyutil - python-zfec - python-zbase32 - python-setuptools_trial - python-foolscap - pycryptopp They're pretty low maintenance, please pick them up if you want. Kind regards, Ruben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
