>> The second issue seems to be a bug somewhere between py2deb,
>> autobuilder and the uploader to the repos: the build number isn't
>> recognized by the repo loader.
>
> By "build number" do you mean package version?

Yes, I mean package version, sorry for the wrong terminology.

> Just to clarify things, the software has a version, the debian
> packaging has a version, and the maemo packging has a version. I
> know it is confusing, but lets take a look at a package name:

This I knew, and that's what confused me: When preparing my package for upload, 
I increased my package version number, then prepared the .dsc. and .changes 
etc. using py2deb. If we look at the email from the autobuilder, it seems that 
it properly recognized this in the uploaded files (or at least my filenames 
reflect it :-):

My second package version of the initial fremantle version of mclock:

> [2009-09-21 20:35:21] Processing package mclock 0.6.0-2. Uploader: twaelti, 
> builder: builder1
> [2009-09-21 20:35:34] Building mclock 0.6.0-2 for target 
> 'maemo-fremantle-i386-extras-devel'
> [2009-09-21 20:36:14] OK
> [2009-09-21 20:36:21] Signing build results
> [2009-09-21 20:36:27] mclock 0.6.0-2 has been queued for loading into 
> fremantle extras-devel repository
> [2009-09-21 20:36:27] You can find more info about this build here: 
> https://garage.maemo.org/builder/fremantle/mclock_0.6.0-2/

My first package version of the fifth minor revision of the fremantle version 
of mclock:

> [2009-09-24 22:20:17] Processing package mclock 0.6.4-1. Uploader: twaelti, 
> builder: builder1
> [2009-09-24 22:20:24] Building mclock 0.6.4-1 for target 
> 'maemo-fremantle-i386-extras-devel'
> [2009-09-24 22:21:12] OK
> [2009-09-24 22:21:19] Signing build results
> [2009-09-24 22:21:22] mclock 0.6.4-1 has been queued for loading into 
> fremantle extras-devel repository
> [2009-09-24 22:21:22] You can find more info about this build here: 
> https://garage.maemo.org/builder/fremantle/mclock_0.6.4-1/

Unfrtunatelely, that info about the package version never arrived in the 
repository or package viewer. So I guess there must be a bug somewhere in my 
package files.
However, looking at the files in e.g. 
https://garage.maemo.org/builder/fremantle/mclock_0.6.4-1/ doesn't reveal any 
problem.

Can you help me track that bug down? It would not only help me, but all people 
who plan to use py2deb for their packaging.
I will gladly send you the files privately in a separate email if this helps.

Best regards
-Tom


_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to