[opensuse] would you please someone build an openSUSE12.3 rpm for YaRock?
Yarock is Qt4 Modern Music Player designed to provide an easy and pretty music collection browser based on cover art. Yarock is written in C++ using Qt and Phonon multimedia framework, only for linux platform. in qt-apps.org website, YaRock has very high rate and lots of fans. YaRock is so good but lacks of rpm files under openSUSE. would you please someone build rpm files for YaRock? thanks advance! the following link is a snapshot for it. http://qt-apps.org/CONTENT/content-pre2/129372-2.jpg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, May 4, 2013 at 2:46 PM, bruce
Yarock is Qt4 Modern Music Player designed to provide an easy and pretty music collection browser based on cover art. Yarock is written in C++ using Qt and Phonon multimedia framework, only for linux platform. in qt-apps.org website, YaRock has very high rate and lots of fans. YaRock is so good but lacks of rpm files under openSUSE. would you please someone build rpm files for YaRock? thanks advance!
the following link is a snapshot for it. http://qt-apps.org/CONTENT/content-pre2/129372-2.jpg
Bruce, This is a user support forum, not a place where devs tend to hang out. Posting on opensuse-packaging or -factory might increase your chances of finding a taker. Regardless, a little more support of " YaRock has very high rate and lots of fans." with some form of statistics, etc. to back that up might help. If you don't know, packaging of tools like YaRock will be done by someone on there personal time, so you need to "sell" the packaging job to someone, not just throw it at the wall and see if it sticks. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
在 2013年5月4日 星期六 15:16:30,Greg Freemyer 写道:
On Sat, May 4, 2013 at 2:46 PM, bruce
wrote: Yarock is Qt4 Modern Music Player designed to provide an easy and pretty music collection browser based on cover art. Yarock is written in C++ using Qt and Phonon multimedia framework, only for linux platform. in qt-apps.org website, YaRock has very high rate and lots of fans. YaRock is so good but lacks of rpm files under openSUSE. would you please someone build rpm files for YaRock? thanks advance!
the following link is a snapshot for it. http://qt-apps.org/CONTENT/content-pre2/129372-2.jpg
Bruce,
This is a user support forum, not a place where devs tend to hang out. Posting on opensuse-packaging or -factory might increase your chances of finding a taker.
Regardless, a little more support of " YaRock has very high rate and lots of fans." with some form of statistics, etc. to back that up might help.
If you don't know, packaging of tools like YaRock will be done by someone on there personal time, so you need to "sell" the packaging job to someone, not just throw it at the wall and see if it sticks.
Greg
sorry about that. at the very beginning i posted a thread in forums.opensue.org , and the administrator told me that posting here would be a better choice. so i did as he told. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/13 20:46, bruce wrote:
Yarock is Qt4 Modern Music Player designed to provide an easy and pretty music collection browser based on cover art. Yarock is written in C++ using Qt and Phonon multimedia framework, only for linux platform. in qt-apps.org website, YaRock has very high rate and lots of fans. YaRock is so good but lacks of rpm files under openSUSE. would you please someone build rpm files for YaRock? thanks advance!
the following link is a snapshot for it. http://qt-apps.org/CONTENT/content-pre2/129372-2.jpg
Hi It's good. Ubuntu has it. It's the only one I've found where you can set the volume levels to equalise between tracks with no fiddling. It just works. But it doesn't build on openSUSE: zypper in libqt4-devel phonon-devel libtag-devel boost-devel Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: boost-devel dbus-1-devel fontconfig-devel font-util freetype2-devel gcc47-c++ gcc-c++ gccmakedep glib2-devel imake libboost_chrono1_49_0 libboost_graph1_49_0 libboost_iostreams1_49_0 libboost_locale1_49_0 libboost_math1_49_0 libboost_mpi1_49_0 libboost_python1_49_0 libboost_random1_49_0 libboost_serialization1_49_0 libboost_test1_49_0 libboost_timer1_49_0 libboost_wave1_49_0 libdmx-devel libdrm-devel libfontenc-devel libFS-devel libgbm-devel libICE-devel libjpeg8-devel libkms1 libkms-devel liblbxutil-devel liblcms-devel libmng-devel liboldX6 liboldX-devel libOSMesa9 libOSMesa-devel libpciaccess-devel libpcre16-0 libpcrecpp0 libpcreposix0 libpixman-1-0-devel libpng12-0 libpng12-compat-devel libpng12-devel libqt4-devel libSM-devel libstdc++47-devel libstdc++-devel libtag-devel libtiff-devel libudev-devel libvnc-devel libVncExt2 libWindowsWM7 libWindowsWM-devel libX11-devel libXau-devel libXaw6 libXaw8 libXaw-devel libxcb-devel libxcb-dpms0 libxcb-record0 libxcb-res0 libxcb-screensaver0 libxcb-sync0 libxcb-xevie0 libxcb-xf86dri0 libxcb-xinerama0 libxcb-xprint0 libxcb-xtest0 libxcb-xvmc0 libXcliplist1 libXcliplist-devel libXcomposite-devel libXcursor-devel libXdamage-devel libXdmcp-devel libXevie1 libXevie-devel libXext-devel libXfixes-devel libXfontcache-devel libXfont-devel libXft-devel libXi-devel libXinerama-devel libxkbfile-devel libxkbui1 libxkbui-devel libXmu-devel libXp-devel libXpm-devel libXprintAppUtil1 libXprintAppUtil-devel libXprintUtil-devel libXrandr-devel libXrender-devel libXres-devel libXScrnSaver-devel libXt-devel libXTrap-devel libXtst-devel libXv-devel libXvMC-devel libXxf86dga-devel libXxf86misc-devel libXxf86vm-devel lndir makedepend Mesa-devel Mesa-libEGL-devel Mesa-libglapi-devel Mesa-libGL-devel Mesa-libGLESv1_CM1 Mesa-libGLESv1_CM-devel Mesa-libGLESv2-devel Mesa-libIndirectGL1 Mesa-libIndirectGL-devel mpi-selector openmpi openmpi-devel pcre-devel phonon-devel python-xcb-proto-devel xbitmaps-devel xcb-util-devel xorg-cf-files xorg-sgml-doctools xorg-x11-devel xorg-x11-proto-devel xorg-x11-util-devel xtrans The following recommended package was automatically selected: libpng12-compat-devel After qmake && make src3party/libechonest/Song.cpp:29:30: fatal error: qjson/serializer.h: No such file or directory compilation terminated. make: *** [build/obj/Song.o] Error 1 Looks like a source file but no tme to investigate. If you like it, it's worth sticking an 8Gb Lubuntu virtualbox up. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[04.05.2013 22:10] [lynn]: > > After qmake && make > > src3party/libechonest/Song.cpp:29:30: fatal error: qjson/serializer.h: > No such file or directory > compilation terminated. > make: *** [build/obj/Song.o] Error 1 > > Looks like a source file but no tme to investigate. If you like it, it's > worth sticking an 8Gb Lubuntu virtualbox up. Maybe it's in one of the following packages? > webpin serializer.h 20 results (20 packages) found for "serializer.h" in openSUSE_123 * php5-pear-XML_Serializer: Swiss-army knife for creating, reading and writing XML files - 0.20.2.8.1.1 [suse-oss] * python-msgpack-python: MessagePack (de)serializer - 0.2.4.4.1.1 [suse-oss] * python3-msgpack-python: MessagePack (de)serializer - 0.2.4.4.1.1 [suse-oss] * perl-MLDBM: store multidimensional hash structures in tied hashes - 2.04.17.1.1 [suse-oss] * bzr: Friendly distributed version control system - 2.5.1.3.1.1 [suse-oss] * kdepimlibs4: KDE PIM Libraries - 4.10.0.1.2.1 [suse-oss] * perl-SOAP-Lite: Perl's Web Services Toolkit - 0.714.4.1.1 [suse-oss] * perl-DBI: Database independent interface for Perl - 1.617.4.1.1 [suse-oss] * perl-CHI: Unified cache handling interface - 0.52.4.1.1 [suse-oss] * xsd: W3C XML schema to C++ data binding compiler - 3.3.0.1.4.1.1 [suse-oss] * perl-YAML-Perl: Pure Perl YAML Implementation - 0.02.9.1.1 [suse-oss] * cobbler: Boot server configurator - 2.2.2.12.1.1 [suse-oss] * kdepim4-runtime: Base package of kdepim - 4.10.0.1.1.1 [suse-oss] * xalan-j2: Java XSLT processor - 2.7.0.259.1.1 [suse-oss] * rubygem-warden-testsuite: Test suite for warden - 1.2.1.2.1.1 [suse-oss] * python-html5lib: HTML parser based on the WHAT-WG Web Applications 1 - 0.95.4.1.1 [suse-oss] * rubygem-yard-testsuite: Test suite for yard - 0.8.3.2.1.1 [suse-oss] * rubygem-warden-doc: RDoc documentation for warden - 1.2.1.2.1.1 [suse-oss] * rubygem-eventmachine-doc: RDoc documentation for eventmachine - 1.0.0.2.1.1 [suse-oss] * kde4-l10n-ia: Interlingua (ia) translations for KDE - 4.10.0.1.1.1 [suse-oss] HTH, Werner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/13 22:21, Werner Flamme wrote:
[04.05.2013 22:10] [lynn]:
After qmake && make
src3party/libechonest/Song.cpp:29:30: fatal error: qjson/serializer.h: No such file or directory Maybe it's in one of the following packages?
webpin serializer.h 20 results (20 packages) found for "serializer.h" in openSUSE_123 Hi Found it. the clue was in the
qjson/serializer.h: We need qjson-devel added to the dependencies for the zypper install. Now it builds just fine. It looks exactly the same as on Ubuntu. The OP wants a rpm. Is that a big step from here? HTH L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn
On 04/05/13 22:21, Werner Flamme wrote:
[04.05.2013 22:10] [lynn]:
After qmake && make
src3party/libechonest/Song.cpp:29:30: fatal error: qjson/serializer.h: No such file or directory Maybe it's in one of the following packages?
webpin serializer.h 20 results (20 packages) found for "serializer.h" in openSUSE_123 Hi Found it. the clue was in the
qjson/serializer.h:
We need qjson-devel added to the dependencies for the zypper install. Now it builds just fine. It looks exactly the same as on Ubuntu.
The OP wants a rpm. Is that a big step from here? HTH L x
Lynn, If you want to build rpm's for opensuse you should get familiar with build.opensuse.org. You see a fairly normal webui, but it back-ended by about 75 machines running a build farm. 100% of opensuse is built and distributed from there. All the official devel projects are there and if I recall correctly about 40,000 people have accounts that let them build packages (rpms or debs). In the case of yarock, I see that it is 4 people's home projects and one "unsupported" project: https://build.opensuse.org/search. (Type yarock in the box and search.) If none of those build for 12.3, you just have to branch one of those that is close to working and edit the specfile to use the tarball you are compiling and to add "BuildRequires: qjson-devel". The specfile in RIP might be the best starting point because the implication is it used to be a supported package and the specfile should have been of a decent quality. For something that simple you can do it all via the webui. Once the build is done, you can install directly from your home project even if you choose not to publish the rpms. Only published rpms show up in the normal search.opensuse.org results. Once your needs get a little more sophisticated you can use "osc" to interact with the build farm and do local builds inside a chroot env. It is all very polished and worth taking the time to learn. Fyi: once you get a package you think is right, you have the option of submitting it to a devel project for review, and from there to factory for inclusion in 13.1. At that point you have joined the ranks of opensuse maintainers. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/05/2013 06:41 AM, Greg Freemyer wrote:
lynn
wrote: On 04/05/13 22:21, Werner Flamme wrote:
[04.05.2013 22:10] [lynn]:
After qmake && make
src3party/libechonest/Song.cpp:29:30: fatal error: qjson/serializer.h: No such file or directory Maybe it's in one of the following packages?
webpin serializer.h 20 results (20 packages) found for "serializer.h" in openSUSE_123 Hi Found it. the clue was in the
qjson/serializer.h:
We need qjson-devel added to the dependencies for the zypper install. Now it builds just fine. It looks exactly the same as on Ubuntu.
The OP wants a rpm. Is that a big step from here? HTH L x
Lynn,
If you want to build rpm's for opensuse you should get familiar with build.opensuse.org. You see a fairly normal webui, but it back-ended by about 75 machines running a build farm.
100% of opensuse is built and distributed from there.
All the official devel projects are there and if I recall correctly about 40,000 people have accounts that let them build packages (rpms or debs).
In the case of yarock, I see that it is 4 people's home projects and one "unsupported" project:
https://build.opensuse.org/search. (Type yarock in the box and search.)
If none of those build for 12.3, you just have to branch one of those that is close to working and edit the specfile to use the tarball you are compiling and to add "BuildRequires: qjson-devel". The specfile in RIP might be the best starting point because the implication is it used to be a supported package and the specfile should have been of a decent quality.
For something that simple you can do it all via the webui. Once the build is done, you can install directly from your home project even if you choose not to publish the rpms. Only published rpms show up in the normal search.opensuse.org results.
Once your needs get a little more sophisticated you can use "osc" to interact with the build farm and do local builds inside a chroot env. It is all very polished and worth taking the time to learn.
Fyi: once you get a package you think is right, you have the option of submitting it to a devel project for review, and from there to factory for inclusion in 13.1. At that point you have joined the ranks of opensuse maintainers.
Greg
Greg, Are there any tutorials for the use of build.opensuse.org? A pointer to those, if they exist, might be useful in "getting familiar" with build.opensuse.org. What is osc? where do I find docs? You seem to live and "swim" in build and have probably forgotten what it it to come in cold. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[05.05.2013 17:42] [Bruce Ferrell]:
Greg,
Are there any tutorials for the use of build.opensuse.org? A pointer to those, if they exist, might be useful in "getting familiar" with build.opensuse.org. What is osc? where do I find docs?
You seem to live and "swim" in build and have probably forgotten what it it to come in cold.
Thanks
I'm not Greg, but... if you really use a web search engine that does not give you http://en.opensuse.org/openSUSE:Build_Service_Tutorial when you search for the three words opensuse build tutorial, you should change it ;-)
From this page, you find liks to alot other pages with more detailed info, all in the openSUSE wiki.
HTH Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Werner Flamme
[05.05.2013 17:42] [Bruce Ferrell]:
Greg,
Are there any tutorials for the use of build.opensuse.org? A pointer
to those, if they exist, might be useful in "getting familiar" with build.opensuse.org. What is osc? where
do I find docs?
You seem to live and "swim" in build and have probably forgotten what it it to come in cold.
Thanks
I'm not Greg, but... if you really use a web search engine that does not give you http://en.opensuse.org/openSUSE:Build_Service_Tutorial when you search for the three words opensuse build tutorial, you should change it ;-)
From this page, you find liks to alot other pages with more detailed info, all in the openSUSE wiki.
HTH Werner
And osc is a command line tool in the normal repos. "zypper in osc" should get it for you among other ways. If you want the latest version then you will want to install it from its devel projects. (I don't recall where I have it installed from.) As to the tutorial be sure you register on the website and log in before you do anything else. There are 2 opensuse mailing lists dedicated to using it. Opensuse-buildservice is for questions about the infrastructure, build software or how the webui works. The Obs software is gpl, so a lot of people (companies) run internal build servers. As an example, I think Dell has one. I assume you they do that so they can build proprietary software that is not allowed on the opensuse system. Opensuse-packaging is about how specfiles, patches, etc. work. In general, if your question is specific to a package or collection of packages, this is the place to ask it. I still ask a lot of questions and most of them go to -packaging. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-05-05 at 20:00 +0200, Werner Flamme wrote:
I'm not Greg, but... if you really use a web search engine that does not give you http://en.opensuse.org/openSUSE:Build_Service_Tutorial when you search for the three words opensuse build tutorial, you should change it ;-)
True... but at https://build.opensuse.org/ there is no link to that tutorial ;-) But there is another to https://en.opensuse.org/openSUSE:Build_Service, and that one does have a link to the tutorial. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGGzqMACgkQtTMYHG2NR9Xf1QCfS7gXpooCplwoQ99Wv8htDRda agkAn2DflZPr5sof7cCYVKUUYaUxLJo3 =OW+l -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 5 May 2013 23:26:44 +0200 (CEST)
"Carlos E. R."
True... but at https://build.opensuse.org/ there is no link to that tutorial ;-)
But there is another to https://en.opensuse.org/openSUSE:Build_Service, and that one does have a link to the tutorial.
Also there are links on https://build.opensuse.org to other sources of information, like: http://openbuildservice.org/help/manuals/obs-reference-guide/ Then there is documentation server: http://doc.opensuse.org/ with links to above reference guide. For those that don't know all documentation sources for openSUSE there is Google, or other search service. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 04 May 2013, Werner Flamme wrote:
[04.05.2013 22:10] [lynn]:
After qmake && make
src3party/libechonest/Song.cpp:29:30: fatal error: qjson/serializer.h: No such file or directory compilation terminated. make: *** [build/obj/Song.o] Error 1
Looks like a source file but no tme to investigate. If you like it, it's worth sticking an 8Gb Lubuntu virtualbox up.
Maybe it's in one of the following packages?
webpin serializer.h 20 results (20 packages) found for "serializer.h" in openSUSE_123
Nope. It's libqjson-devel that's needed. HTH, -dnh -- It is impossible to make anything foolproof because fools are so ingenious. -- from the fortune file -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
bruce
-
Bruce Ferrell
-
Carlos E. R.
-
David Haller
-
Greg Freemyer
-
lynn
-
Rajko
-
Werner Flamme