Hello Benoît<br><br>Here is the fix: Change line 312 (? depending on your current version...) to<br> #==========================================================================<br> # CREATE debian/changelog<br>
#==========================================================================<br> clog="""%(name)s (%(version)s-%(buildversion)s) stable; urgency=low<br><br>The proof that it works: <a href="http://maemo.org/packages/view/mclock/">http://maemo.org/packages/view/mclock/</a> :-)<br>
<br>PS: Can you afterwards upload py2deb (0.5.0) to the diablo and fremantle repos? (I believe in diablo is still the old version without the script support.)<br><br>Merci and thanks to all involved - case closed<br>-Tom<br>
<br> <br><br><div class="gmail_quote">2009/9/28 Benoît HERVIER <span dir="ltr"><<a href="mailto:khertan@khertan.net">khertan@khertan.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
Ok this is clearly a bug of py2deb which didn't include the package number.<br>
I ll fix this tomorrow in the morning.<br>
<br>
Best regards,<br>
<br>
2009/9/28 Thomas Waelti <<a href="mailto:twaelti@gmail.com">twaelti@gmail.com</a>>:<br>
<div><div></div><div class="h5">>>> So I guess there must be a bug somewhere in my package files.<br>
>><br>
>> There is, it's in the changelog.<br>
>><br>
>> The canonical place for the version string is in your changelog -<br>
>> debian tools look for that string and assign the version based on<br>
>> that. Here's the first line of your changelog for verion 0.6.4:<br>
>><br>
>> mclock (0.6.4) stable; urgency=low<br>
>><br>
>> As you can see there is no -1 after the version number. Also, the<br>
>> following word after the version in parentheses is "stable", but it<br>
>> really should be "unstable" since this signifies which debian<br>
>> repository this package is destined for. Of course, Maemo is not<br>
>> debian, so this is irrelevant at this point in time.<br>
><br>
> Thanks for the help, I'll go after that and hunt and hopefully fix the bug.<br>
> (For me, finding this would have been like a needle in a haystack....)<br>
><br>
>> I recommend using the tools recommended by debian and Maemo[0],<br>
>> specifically dh_make. The simple reason I recommend dh_make is that I<br>
>> have more experience with that then py2deb and I know that dh_make is<br>
>> well tested and used extensively in debian.<br>
><br>
> Yes, I fully understand and agree. However, the idea is to offer an option to build a package for people without a linux desktop, so that they can prepare the package parts directly on their device and upload from there (same goes for pypackager). This also offers a quick way to "package" command line hacks (such as the gconf options for the display timeout, aka moreDimmingOptions)<br>
><br>
> Best regards<br>
> -Tom<br>
><br>
</div></div>> _______________________________________________<br>
> maemo-developers mailing list<br>
> <a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
> <a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
><br>
<font color="#888888"><br>
<br>
<br>
--<br>
Benoît HERVIER - <a href="http://khertan.net/" target="_blank">http://khertan.net/</a><br>
</font></blockquote></div><br>