Re: apps.formeego.org testing starting
 

Thank you Gents.

Really like what I see so far in the repos.

Re: apps.formeego.org testing starting
 

I have some questions about apps.formeego.org, which weren't answered by anyone so far. See starting from here:
http://forum.meego.com/showthread.php?p=36018#post36018

In short, why can't dependencies on libraries be specified in it?

Re: apps.formeego.org testing starting
 

I am unable to 'rate' a downloaded App. Already have discovered some useful feedback for the developer so would like to share that too.

Re: apps.formeego.org testing starting
 

Short answer: To prevent a dependency mess, we started with 'clean' builds against the sdk only.

Longer answer: Of course we should try to harness the power of shared libraries etc. To prevent people from randomly uploading dependencies and not caring if it breaks other packages, we need to come up with a way to do this properly.

My idea is to have a separate repository where shared libraries are managed (maybe even with a staging repository where we can test breakage when new versions are introduced). We can go for package maintainers per package or a group of interested people who manage the repository.

For this to not become a mess, we need to have a clear policy and good communication between maintainers.

I intend to come up with at proposal on the wiki this week. I'll ask for input/ideas after that. And of course ask for volunteers :)

Re: apps.formeego.org testing starting
 

I guess you are trying this in the client itself? Feedback is not implemented there yet.

Feedback and rating on http://apps.formeego.org should work though.

Re: apps.formeego.org testing starting
 

Thanks for the answer and the work on apps.formeego.org.

I think it is important to the end user :
1) install in the same way softwares with or without dependencies;
2) also install libraries / softwares without icons / softwares CLI (Command Line Interface), there are some waiting for repositories, for example Python Harmattan softwares from the community;
3) easily see the testing softwares from the Apps.ForMeeGo application (without need to go to a web site and install a .deb to enable it).

I now have 7 packages for the case (2), and 3 softwares with GUI and dependencies until the end of this month, all waiting for Apps.Formeego. :cool:

Re: apps.formeego.org testing starting
 

Thanks for the clarification X-Fade! What is considered a clean build against Harmattan and Nemo at the moment? One depending on Harmattan SDK or Mer packages? Will the additional repo with dependencies need to be maintained for Harmattan and Nemo separately?

Re: apps.formeego.org testing starting
 

Clean dependencies means that you don't need any other packages from your home project (Or the project the package is building in)

So once you need to upload a lib first to get your package to build, then you are out of luck in the current setup. Unless you statically link against it. That is a possibility too, but that is not an optimal one.

For extra dependencies to work, we need to address the things I mentioned in my previous posts.

Re: apps.formeego.org testing starting
 

I was asking more about the difference between Harmattan and Nemo in regards to what system packages will be expected by default (since you mentioned SDK packages) and how the proposed repositories where additional dependencies will be added later are going to work out in practice for both (since apps.formeego.org was intended to cater for both systems). Just an example, let's say boost will be added to the new repository. So it'll need to be maintained for all proposed targets? (Harmattan & Nemo at least?).

Re: apps.formeego.org testing starting
 

The repositories would be separate as they have a different target. That is not to say the same packages can't be in both of them. There is the added complication that Harmattan and Nemo are using different packaging. So yes, the shared extra dependencies should be maintained for each target separately.

Re: apps.formeego.org testing starting
 

Two bugs on the site:

Contact link points to applications.

My account Manatus does not get resolved to correct user. Forms seem to mention the account as tjjalava. Might be bad luck but I submitted form for three applications, and the latest one turned into Tjjalava one by one. Apps were Talk.maemo.org, Nivel and Brujula.

Re: apps.formeego.org testing starting
 

I think I remember someone mentioning on IRC, that it might be possible to build both RPM and Debian packages from the same OBS package, provided all the necessary spec, dsc, etc. files are included.

Re: apps.formeego.org testing starting
 

I'm not sure how you know that. It's the only community repository which was proposed after Linux foundation denied such option on meego.com. It was being prepared for a while. In general I agree that some more publicity is needed for it, as well as for other community efforts like Mer and Nemo.

Re: apps.formeego.org testing starting
 

Many apps just lay around somewhere, like on my-meego.com.

Re: apps.formeego.org testing starting
 

Well, not just "lay around"... ;) Almost 80.000 files have been downloaded through My-MeeGo.com during the last couple of months, so I guess they do a good job there and help popularize the Harmattan platform.

Best regards,
Michal Jerz
http://My-MeeGo.com

Re: apps.formeego.org testing starting
 

I have submitted Mieru to apps.formeego.com - looks like application submit works as expected, comments, grading and testing feedback also seem to work fine. :) The only notable issue is that my nickname is somehow doubled when posting comments "martink martink" instead of just "martink".

On a related note:
TESTERS NEEDED ! :)
Mieru already has 2 community QA feedbacks but 4 more are needed for it to pass to the main repository.

Even if you are not really interested in mangas and comic books, you can still help by following the community QA gudelines and filling in feedback for Mieru and quite a few other applications that are currently waiting for feedback on apps.formeego.com. Thanks in advance! :)

Re: apps.formeego.org testing starting
 

A bunch of new apps left the quarantine period on apps.formeego.org today and are now available in the stable repository.

It's a good start! :)
Let's all help to spread the word to get more apps into the testing queue.
And please everyone don't forget to vote for the apps you're using from testing. A smooth QA process is essential. An app currently requires six positive QA results to pass QA.

Re: apps.formeego.org testing starting
 

The server of apss.formeego.org is down ? I can't access to it

Re: apps.formeego.org testing starting
 

same here...

Re: apps.formeego.org testing starting
 

It would be nice to have stuff listed here and ways to connect support if any trouble.
I'm not maintainer in my home project anymore, and i can't delete account or repo to re-create it.
As well uploading file by file is little bit slow. Is there way to select several files for upload?

Re: apps.formeego.org testing starting
 

aPPs not apSS

http://apps.formeego.org/applications/

Re: apps.formeego.org testing starting
 

You do realize that it was posted 5 months ago...

Re: apps.formeego.org testing starting
 

t's nightmare. I did successfully created dsc and tar files but:
It wouldn't build in OBS as i was told because of
$(MAKE) INSTALL_ROOT="$(CURDIR)"/debian/imgrup install
where it needs to be
$(MAKE) INSTALL_ROOT="/usr/src/packages/BUILD"/debian/imgrup install
what s not default by QtCreator and wouldn't build (i'll try to make this dir localy and give to my user permissions now and report later)

As well if i comment $(MAKE) clean it would leave .o files in tar.gz and if i uncomment back there would be no src files at all there.

And there are a lot of problems i met while trying, still no success. It might be possible, but for new developer who just learning and especially want to use QtCreator that is not an option as well as installing scratchbox just to built for OBS, than what si the point in «user-friendly» QtCreator?

I think either the way OBS compiles should be changed (maybe automatic way to change from QtCreator files if needed editing them before compiling and packaging) or plugin on QtCreator side should be done to integrate those things out-of-the-box, it's the main idea of QtCreator, isn't it? Otherwise we all could just use VIM =)


P.S. there were a lot of problems and misunderstandings and not orginized wiki on the way. i may be not pro and expert, but i thought the point of community repo and obs to make it simple so community could use it. otherwise real good devs could set their own repos and tools and they could upload their. It should be easier, otherwise no point in it =\

Re: apps.formeego.org testing starting
 

I use "$(MAKE) INSTALL_ROOT=$(CURDIR)/debian/eyrie install" in my package rules file and OBS doesn't have any problem with it so I'm not sure why it'd cause issues for you, unless perhaps the $CURDIR variable isn't being populated for some reason (so it'd end up trying to install to /debian/imgrup)?

"make clean" shouldn't be deleting source files, it sounds like there's something wrong with your Makefile there (or with your .pro file which generates the Makefile if you're using qmake). But it also shouldn't be installing .o files into your install dir so they shouldn't end up in the package in first place regardless of whether you cleaned or not.

I'm not especially familiar with QtCreator so I'm not sure how exactly it sets everything up but I've be happy to take a look at your original source files if you'd like?

Re: apps.formeego.org testing starting
 

thanks for help, but as we saw on IRC it's always "there is something strange with setup", but i use default setting except changes according the wiki

Re: apps.formeego.org testing starting
 

Hi guys, I also have problem with uploading my app to OBS..
I opened this thread:
http://talk.maemo.org/showthread.php...52#post1216352
But no answer :(
For now i can see OBS created .deb file from my .dsc and tar.gz files in my repo
But still not visible in MeeGo:1.2:Harmattan:Apps:Testing repo..
Someone know how much time this might take?

Re: apps.formeego.org testing starting
 

Try to request again, talked to X-Fade about it today.

Re: apps.formeego.org testing starting
 

Thanks
I tried now and I got this massage again:
For solution, I needed delete my repo and create new one..
After this I saw again the OBS successfully created deb file in my repo and again it's not transfered to MeeGo:1.2:Harmattan:Apps:Testing repo... :(
Maybe I do something wrong or maybe i need to do something else ?
And what heppens when I will update my packages, i need delete previous .deb file ? Or it will changed automaticly to new version ?
Thanks

Re: apps.formeego.org testing starting
 

you need to add repo as described here — http://forum.meego.com/showpost.php?...5&postcount=29

Re: apps.formeego.org testing starting
 

Thank you very much ! Now it's worked !
But why it's not mentioned here in wiki: http://wiki.meego.com/MeeGo_Apps/Submit

And i have another question...
What I need to do for updating my package to new version ?
1. Delete .dsc, .tar.gz and .changes files from my project and reupload new ?
2. Same with screenshots, if I want to update them ?
3. Do I need submit package again or it will do this automaticaly ?
4. Do I need delete previous .deb file or new version automatically will override the previous one?

I want to create a little manual for dumb's like me :)
Thanks

Re: apps.formeego.org testing starting
 

1: Yep, just like that. You can do tha easily using the osc tool with the ar parameter.

2: From my eperience you have to replace the screenshot file/-s & bump the package version.

3: Your repository is independent from the AFM one so you have to submit it manually once you decide to push an update. Also note that package updates reset QA votes.

4: The .deb in the repository is automatically replaced once a new version is built.

Re: apps.formeego.org testing starting
 

Thank you !
What is this: " osc tool with the ar parameter" ?
Sorry I'm noob :D

Re: apps.formeego.org testing starting
 

osc is tool for obs, let's say it's like (not really but «like») git tool just for obs :)

http://en.opensuse.org/openSUSE:OSC here is how to use it (the installations is for opensuse, but i even has it in portage on gentoo).

All you need to install it (i bet it's something like apt-get install osc for ubuntu) and than add repo (from submit wiki on meego) — osc -A https://api.pub.meego.com co home:[username]
than you just go to this home:Schturman/your_mega_app (i assume you already have app there and it would sync it to local folder)
and than copy needed files there , for example new_app-2.0.deb
than just delete old one — osc rm new_app-1.0.deb ,add new — osc add new_app-2.0.deb and commit — osc commit (it would popup terminal editor of your choise, save, press «c» to continue and it would upload new file)
you can add several files before commit as well.

☺☺☺

Re: apps.formeego.org testing starting
 

Oh, and osc ar as help says is addremove (ar) Adds new files, removes disappeared files

Re: apps.formeego.org testing starting
 

As i promised.

Qt Creator and OBS:

In order to build project for COBSQt Creator and OBS:(for example to push it to apps4meego) and still to be able to continue to work with QtCreator you need to make few simple steps i would show in this post. I don't update wiki, as i think i might have problems with grammar and self explanation, so i hope it would be used to update current wiki. As well current wiki is still useful and I just add few aspects and update some info from there, so i suggest to use it along with this howto.

The files to change below are from "/qtc_packaging/debian_harmattan" inside project dir

1) Go to your rule file and change those lines:
#qmake -> ##OBS qmake \\ In my example i use ##OBS qmake -recursive, i think it's related to that i use subdirs as project.
#$(MAKE) -> ##OBS $(MAKE)
#dh_shlibdeps -> ##OBS dh_shlibdeps

as well if there is any comment followed in any of those lines, delete it. and it's important to keep all line starts with "tab" and not with "8 spaces"(in our example those we changed start with ##OBS), otherwise you'll get error.

for aegis matter you need to add those lines after dh_builddeb (change <package> to your app name)
##OBS aegis-deb-add -control debian/<package>/DEBIAN/control .. debian/manifest.aegis=_aegis (as well with "tab" at the beginning)

Here is an example of mine rule file — https://github.com/funkycode/imgrup/...armattan/rules


2)Now go to your main .pro file and add .desktop file to be installed: in my example it looks like:

desktop.files = imgrup_harmattan.desktop
desktop.path = /usr/share/applications
INSTALLS += desktop

(the path is shown for harmattan, for maemo the path would be different)

3)The last thing before packaging and submitting is to fix the deps, for that we go to the control file and add deps we need, i'm not good at this, but i think rzr and few members can help you on that, those are packages installed on OBS when building the app, and AFAIK you still need deps in .pro file. i'll provide example as part of mine:

.....
Build-Depends: debhelper (>= 8.0.0), libqt4-dev, pkg-config,
libshare-ui-dev,libqt4-declarative-dev,
libqtm-multimedia-dev, libqt4-multimedia, libaccounts-qt-dev, libsignon-qt-dev,
libsignon-glib-dev, signon-plugins-dev, signond-dev, libaccountplugin-dev, libaccountsetup-dev,
libnaccounts-ui-dev, libmeegotouch-dev, applauncherd-dev, maemo-meegotouch-interfaces-dev,
libmdatauri-dev, aegis-builder
Standards-Version: 3.9.2

....


(you need to keep format of file right, i'm talking about new lines, spaces and blank lines. So read the output if you have an error)

3.1)Before building you as well can use postinst file to make post install script file =)

4)After that is ready, we would use phako''s (thanks man) script to package:
https://github.com/funkycode/imgrup/...ate-obs-source

which actually use our(QtCreator's) qtc_packaging/debian_harmattan directory with files we just modified and copy it to debian dir, it uncoomments in rule all lines with "##OBS ", build and than delete the dir. The files would be in the parent dir out of project (.tar.gz and .dsc), while script should be run in project dir. Btw you may need to change "SDK_DIR=" as mine set to where it's on my comp, it the directory to QtSDK.

5)
After that we go to obs and we create new repo:
a)Repositories
b)Add repo
c)use the link " pick one via advanced interface." in the top
d)In the "Project" field paste "MeeGo:1.2:Harmattan"
http://i.imgur.com/We4L8.png

Than build your project there (webupload is not nice as it's trying to build even if one file changed(and your upload change the file), and you can upload only one by one, though with ocs you can update and upload few, the basics covered on wiki and it's similar to git in some way). Add both files made by script icon.png and few screen-shots as well.


After you successfully built the project, you should go to your repo an check the file from there and only if it works (i suggest deleting app from phone and re-installing from there, as i submitted first time broken app, coz of not checking it).

After it's all working — you have green light to submit to testing as described at wiki and than it would take some time, as it takes time till bot decides to build and he rebuilds few times, till it get to apps4meego and database of client is re download. So if you built in your repo and submited after, don't worry it should be okay, just give so time(btw you may get email from bot, that it's built and everything ok)


Any feedback and edits are welcome.

Re: apps.formeego.org testing starting
 

please tell it's down now only because of coincidence

Re: apps.formeego.org testing starting
 

It appears to have been down for most of today with that "502 - Bad Gateway" error, I tweeted about it 6 hours ago. I'm not sure whoever is admin'ing the site has noticed it, hopefully whatever is wrong will be fixed soon.

Re: apps.formeego.org testing starting
 

I hope so :(

Re: apps.formeego.org testing starting
 

It is working now.

Re: apps.formeego.org testing starting
 

yup, X-Fade fixed it =P