Re: Standardization of packages version name in the extra repositories

Hi! > This is how I read it too. Only if we are the upstream ourselves, we don't > need the suffix. In all other cases we need it? > > "If an upstream package is re-packaged or otherwise modified for maemo, a > maemo revision MUST be appended to the upstream revision." MPP section 3.2 > > > >

Diablo-extras-builder in trouble...

Hi! Can someone please fix this: https://garage.maemo.org/builder/diablo/hildonmm_2.0.1-1/armel.root.log.FAILED.txt The build is unable to run apt-get update and thus fails for any package! Thanks, Johannes ___ maemo-developers mailing list maemo-deve

Re: maemomm autobuilder probems

Hi! > If you think they're ready for extras you should promote them using > promotion interface: https://garage.maemo.org/promoter/diablo Ah, thanks for that hint! > We(community) should decide if we need to continue to run rebuilds or > just remove the page. IMHO these page gives are very go

maemomm autobuilder probems

Hi! Probably I get something wrong here: - I uploaded my packages to diablo-extras-builder - They built fine (got three OK mails for hildonmm, hildonfmmm and maemomm-booster - The packages do NOT show up in the repository nor at https://garage.maemo.org/extras-assistant/maemo_extras_diablo_rebuil

Re: Account does no longer work

Hi! > It would be nice if you could tell us more about the configuration > error, because it happened to me too from time to time in the last days, > a retry a few minutes later allways worked, but today it seems that i am > not able to login at all, i am trying to connect to garage since about >

Re: Account does no longer work

Hi! > > If i understand you can t upload directly to extras diablo > That's why I upload to diablo-extras-builder or is this incorrect? Thanks, Johannes ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/lis

Account does no longer work

-devel/incoming-builder/diablo' returned a nonzero exit code. Error while uploading.gpg: Signatur am So 29 Jun 2008 16:15:10 CEST mit DSA Schlüssel, ID 65C9F9B3, erfolgt gpg: Korrekte Unterschrift von 'Johannes Schmid <[EMAIL PROTECTED]>' gpg: alias "

Changing GPG key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Because I revoked my old GPG key, I wanted to change the key stored for the Maemo extras repository. After my mail to [EMAIL PROTECTED] remained unreplied I would like to ask whom I should contact to change the key. Thanks, Johannes -BEGIN PG

Re: [maemo-developers] Package naming

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Thanks, my fault then. The packages should be at the correct position now. Anyway, is there are a way to remove the deprecated packages from the repositry to avoid confusion? Regards, Johannes Tommi Komulainen wrote: > On Wed, 2006-08-16 at 14:

[maemo-developers] Package naming

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I wonder if there is some convention for naming packages in Maemo. Some libraries are named with a lib* prefix (e.g. libgtk2.0-dev) some aren't (hildon-fm-dev). I have named the C++ wrappers for hildon libhildon-fmmm and libhildon-widgetsmm but I

[maemo-developers] libsigc++ source package missing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! # apt-get source libsigc++-2.0 gives me the following error. Seems like the source tarball was not uploaded correctly. Reading Package Lists... Done Building Dependency Tree... Done Need to get 2300kB of source archives. Get:1 http://repository.