--===============1701502296==
Content-Type: multipart/signed;
  boundary="nextPart1508346.gmLLDqzKaN";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1508346.gmLLDqzKaN
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Fathi, Hi All,

I'm resending my questions below, as I am still stuck with them.
Any hints are welcome! :)

Am Samstag, 18. Juni 2011 09:44:23 schrieb Fathi Boudra:
> Project:KDE:Devel is the development area. Everything should go there
> first and isn't targeted for the end users. The audience is
> developers.
>
> When the packages reaches a stable state, they should be promoted to
> an end-user area. That's the areas you mentioned:
> Project:KDE:MeeGo:1.1 -> targeting MeeGo 1.1 users
> Project:KDE:MeeGo:1.2 -> targeting MeeGo 1.2 users
> Project:KDE:Trunk -> targeting MeeGo Trunk (currently it's the
> development branch for MeeGo 1.3)
> Project:KDE:Trunk:Testing -> is a special staging area to reach before
> going into Trunk.

Who decideds what is "stable" and currently does the move?
(I guess there are instructions for doing so, which I will also try to loca=
te=20
and read, but I just assume you have to overview.)

I am still unsure which to recommend currently for people who want to try=20
stuff. To me it seems that users should just pick their MeeGo Version
or go with Project:KDE:Devel if they do not find something.

Shouldn't "Project:KDE:Trunk" better be called somethink with "MeeGo",
I was confused because I was not sure to what product "Trunk" would refer t=
o.
If it had "Project:KDE:MeeGo:1.trunk" it would habe beem clearer to me.

Am Samstag, 18. Juni 2011 09:54:17 schrieb Fathi Boudra:
> >=20
http://repo.pub.meego.com/home:/mdfe:/Project:/KDE:/Experimental/MeeGo_1.2_=
oss/
> >
> > BTW: Is there a way to sign those packages, so that users do not get
> > the signature warnings?
>
> Isn't it because you don't have imported the repo gpg key?
> The easiest way is to disable it: gpgcheck=3D1
> or import the key...

The Zypper warning read like they were not signed, not that I was missing t=
he=20
key, so it was the repo admin not making the right choice I guess!?

> btw, the repo you're using is a personal branch.

Uh, I am still confused about the branches then, when I followed your
link to=20
https://build.pub.meego.com/project/monitor?project=3DProject%3AKDE%3ADevel,
this is one of the options I get. So who's is it? And where do I find the=20
branches that have a wider community that maintains it? Are there any?


Best,
Bernhard
=2D-=20
Managing Director + Owner: www.Intevation.net <- A Free Software Company
Kolabsys.com: Board Member          FSFE.org: Founding GA Member
Intevation GmbH, Osnabr=FCck, DE; Amtsgericht Osnabr=FCck, HRB 18998
Gesch=E4ftsf=FChrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

--nextPart1508346.gmLLDqzKaN
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEABECAAYFAk4Rf7QACgkQh9ag3dpKERaUewCeLF9o9RyfagomyDBYZWkuq2Gf
GbAAoIR1sogf0IPO7aYebWEv3H/SFjf9
=mvYv
-----END PGP SIGNATURE-----

--nextPart1508346.gmLLDqzKaN--

--===============1701502296==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-mobile mailing list
Kde-mobile@kde.org
https://mail.kde.org/mailman/listinfo/kde-mobile

--===============1701502296==--