Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
So I guess there must be a bug somewhere in my package files. There is, it's in the changelog. The canonical place for the version string is in your changelog - debian tools look for that string and assign the version based on that. Here's the first line of your changelog for verion 0.6.4: mclock (0.6.4) stable; urgency=low As you can see there is no -1 after the version number. Also, the following word after the version in parentheses is stable, but it really should be unstable since this signifies which debian repository this package is destined for. Of course, Maemo is not debian, so this is irrelevant at this point in time. Thanks for the help, I'll go after that and hunt and hopefully fix the bug. (For me, finding this would have been like a needle in a haystack) I recommend using the tools recommended by debian and Maemo[0], specifically dh_make. The simple reason I recommend dh_make is that I have more experience with that then py2deb and I know that dh_make is well tested and used extensively in debian. 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) Best regards -Tom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
Hi, Ok this is clearly a bug of py2deb which didn't include the package number. I ll fix this tomorrow in the morning. Best regards, 2009/9/28 Thomas Waelti twae...@gmail.com: So I guess there must be a bug somewhere in my package files. There is, it's in the changelog. The canonical place for the version string is in your changelog - debian tools look for that string and assign the version based on that. Here's the first line of your changelog for verion 0.6.4: mclock (0.6.4) stable; urgency=low As you can see there is no -1 after the version number. Also, the following word after the version in parentheses is stable, but it really should be unstable since this signifies which debian repository this package is destined for. Of course, Maemo is not debian, so this is irrelevant at this point in time. Thanks for the help, I'll go after that and hunt and hopefully fix the bug. (For me, finding this would have been like a needle in a haystack) I recommend using the tools recommended by debian and Maemo[0], specifically dh_make. The simple reason I recommend dh_make is that I have more experience with that then py2deb and I know that dh_make is well tested and used extensively in debian. 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) Best regards -Tom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Benoît HERVIER - http://khertan.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
Hello Benoît Here is the fix: Change line 312 (? depending on your current version...) to #== # CREATE debian/changelog #== clog=%(name)s (%(version)s-%(buildversion)s) stable; urgency=low The proof that it works: http://maemo.org/packages/view/mclock/ :-) 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.) Merci and thanks to all involved - case closed -Tom 2009/9/28 Benoît HERVIER kher...@khertan.net Hi, Ok this is clearly a bug of py2deb which didn't include the package number. I ll fix this tomorrow in the morning. Best regards, 2009/9/28 Thomas Waelti twae...@gmail.com: So I guess there must be a bug somewhere in my package files. There is, it's in the changelog. The canonical place for the version string is in your changelog - debian tools look for that string and assign the version based on that. Here's the first line of your changelog for verion 0.6.4: mclock (0.6.4) stable; urgency=low As you can see there is no -1 after the version number. Also, the following word after the version in parentheses is stable, but it really should be unstable since this signifies which debian repository this package is destined for. Of course, Maemo is not debian, so this is irrelevant at this point in time. Thanks for the help, I'll go after that and hunt and hopefully fix the bug. (For me, finding this would have been like a needle in a haystack) I recommend using the tools recommended by debian and Maemo[0], specifically dh_make. The simple reason I recommend dh_make is that I have more experience with that then py2deb and I know that dh_make is well tested and used extensively in debian. 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) Best regards -Tom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Benoît HERVIER - http://khertan.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
The diablo version was the last ... but ... maybe it s the fremantle which is older :) Anyway i ll push it. Thx for the fix. Le 28 septembre 2009 22:24, Thomas Wälti twae...@gmail.com a écrit : Hello Benoît Here is the fix: Change line 312 (? depending on your current version...) to #== # CREATE debian/changelog #== clog=%(name)s (%(version)s-%(buildversion)s) stable; urgency=low The proof that it works: http://maemo.org/packages/view/mclock/ :-) 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.) Merci and thanks to all involved - case closed -Tom 2009/9/28 Benoît HERVIER kher...@khertan.net Hi, Ok this is clearly a bug of py2deb which didn't include the package number. I ll fix this tomorrow in the morning. Best regards, 2009/9/28 Thomas Waelti twae...@gmail.com: So I guess there must be a bug somewhere in my package files. There is, it's in the changelog. The canonical place for the version string is in your changelog - debian tools look for that string and assign the version based on that. Here's the first line of your changelog for verion 0.6.4: mclock (0.6.4) stable; urgency=low As you can see there is no -1 after the version number. Also, the following word after the version in parentheses is stable, but it really should be unstable since this signifies which debian repository this package is destined for. Of course, Maemo is not debian, so this is irrelevant at this point in time. Thanks for the help, I'll go after that and hunt and hopefully fix the bug. (For me, finding this would have been like a needle in a haystack) I recommend using the tools recommended by debian and Maemo[0], specifically dh_make. The simple reason I recommend dh_make is that I have more experience with that then py2deb and I know that dh_make is well tested and used extensively in debian. 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) Best regards -Tom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Benoît HERVIER - http://khertan.net/ -- Benoît HERVIER - http://khertan.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
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
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
On Sep 26, 2009, at 9:27, Thomas Waelti wrote: 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. There is, it's in the changelog. However, looking at the files in e.g. https://garage.maemo.org/builder/fremantle/mclock_0.6.4-1/ doesn't reveal any problem. The canonical place for the version string is in your changelog - debian tools look for that string and assign the version based on that. Here's the first line of your changelog for verion 0.6.4: mclock (0.6.4) stable; urgency=low As you can see there is no -1 after the version number. Also, the following word after the version in parentheses is stable, but it really should be unstable since this signifies which debian repository this package is destined for. Of course, Maemo is not debian, so this is irrelevant at this point in time. Can you help me track that bug down? Yes, of course. :-) Important to note that py2deb is a community tool, not a maemo tool, nor even a debian tool. So direct support for py2deb will have to come from the developer, but I'm happy to look at the code to check for bugs. It would not only help me, but all people who plan to use py2deb for their packaging. I recommend using the tools recommended by debian and Maemo[0], specifically dh_make. The simple reason I recommend dh_make is that I have more experience with that then py2deb and I know that dh_make is well tested and used extensively in debian. I will gladly send you the files privately in a separate email if this helps. Not necessary - I have a garage login. ;-) Best regardds, Jeremiah 0. http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging%2C_Deploying_and_Distributing ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
Hello all I was now able to resolve my issues with mclock. The problems I had was a combination of bugs, timing misfortunes and misunderstandings ony my side :-) Preface: The autobuilder is quite quick in building such a small app as mine. After my upload using the extras-assistant, the files remained in queue for a few minutes and then took another few minutes to build. However, it takes a relatively LONG time to get loaded to the repository (about 1/2 hour). The first issue was my mistake to assume that once I got the Build OK email from autobuilder, the app would be available from the repos quite immediately. I did therefore not properly check the actuality of the app version in the repo before testing from it. I solved this by learning to wait :-) (and using apt-cache show mclock to learn about the version and build currently available) 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. Therefore, all my subsequent (increased) builds of version 0.6.0 were ignored by the repo loader, the original 0.6.0 therefore being the one remaining in the repo. This I resolved by increasing the minor version (instead of just the build number). However, this is not the proper way and I want therefore ask Jeremiah and/or the person responsible for the repo loader if they can take a look at the files I uploaded and see if they find an error in my .dsc or .changes file. This would help me fix any bug in py2deb. (The original issue with wrong package names and version depends was solved quite quickly - the best way for me was to simply use the package search interface (http://maemo.org/packages/) and search for the desired substring. This will give a list of currently available packages and their version numbers.) Current status:You can now get mclock from the fremantle extras-devel repo. Therefore, I'd be glad for any testers. I'd be especially interest to know if the app icon shows up correctly right after the install or if you get the default app icon (blue square). The latter would mean that my postinstall doesn't yet run correctly (gtk-update-icon-cache...). Using the package viewer, you can also take a look at tit under http://maemo.org/packages/view/mclock/ Thanks for bearing with me - it's part of my battle to make simple python development accessible on Maemo to casual Windows-based users without hardcore Linux knowhow :-) Best regards -Tom On Mon, Sep 21, 2009 at 23:01, Thomas Waelti twae...@gmail.com wrote: Thanks you both for all the support. Unfortunately, from evaluation of your feedbacks, I found out that the information in http://maemo.org/packages/view/mclock/ is outdated and does not reflect the currently uploaded package (build3) but instead still contains the information from an earlier build. The errors mentioned in there were (hopefully) resolved by me in the way you mentioned in build3 which is the most recently uploaded package. Is there a problem with the queue for loading into fremantle extras-devel repository (taking too long) or is my package so wrong (perhaps a py2deb bug)? It did however build OK ( https://garage.maemo.org/builder/fremantle/mclock_0.6.0-3/) [2009-09-21 20:55:21] Processing package mclock 0.6.0-3. Uploader: twaelti, builder: builder1 [2009-09-21 20:55:29] Building mclock 0.6.0-3 for target 'maemo-fremantle-i386-extras-devel' [2009-09-21 20:56:26] OK [2009-09-21 20:56:27] Signing build results [2009-09-21 20:56:34] mclock 0.6.0-3 has been queued for loading into fremantle extras-devel repository I will wait for the repository and package view webpage to get updated with the newer build and try again tomorrow. Thanks! -Tom On Mon, Sep 21, 2009 at 4:02 PM, Jeremiah Foster jerem...@jeremiahfoster.com wrote: The following packages have unmet dependencies: mclock: Depends: gnome-python (= 2.26.1-1maemo1) Depends: pygtk (= 2.12.1-6maemo7) but it is not installable Depends: pygame (= 1.8.1release-0maemo3) but it is not You are using the wrong package names, you should use: python-gtk2 python-pygame Regards, ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
On Sep 21, 2009, at 21:13, Thomas Wälti wrote: Hello Jeremiah Hi Tom! (I'm CCing the development list as well, in case anyone else has this problem.) My name is Tom (maemo user twaelti) and I'm the developer of mClock. I've also used this application to create the pypackager and py2deb wiki pages. Want I want to achieve is to make app development using Python accessible for entry/casual developers. Sounds great. [sbox-FREMANTLE_X86: ~/MyDocs/mclock] apt-get install mclock Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: mclock: Depends: gnome-python (= 2.26.1-1maemo1) Depends: pygtk (= 2.12.1-6maemo7) but it is not installable Depends: pygame (= 1.8.1release-0maemo3) but it is not installable E: Broken packages Can you help me resolve this problem? Here's your problem: Depends: pygtk (= 2.12.1-6maemo7) but it is not installable Depends: pygame (= 1.8.1release-0maemo3) but it is not installable More about the package can be found at http://maemo.org/packages/view/mclock/ Looking around a little more closely at the link you sent, I can see that you are also not identifying which section your software goes in. See this link for the warning: http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_i386/mclock/0.6.0 If you need more information on Maemo packaging policy (specifically where to place your software in the user/ tree) see this link: http://wiki.maemo.org/Task:Packaging_Policy_proposed_changes It depends on python-gtk2 (= 2.12.1-6maemo4), python-pygame (= 1.8.1release-0maemo1), gnome-python (= 2.26.1-1maemo1), python- hildon (= 0.9.0-1maemo1), python-osso (= 0.3-2maemo3) My guess is that there is a problem with one of the underlying dependenices, but how to find out? The clearest message you receive is at the end of apt-get's run, when it says; The following packages have unmet dependencies: What has happened is that you depend on two python libraries that are newer than the libraries in the repos. Can you help me solve this issue? The simplest way is for you to upload the required dependencies, or to use the existing dependencies with your software. This means there is extra work for you to do one way or the other - if you decide to upload newer versions of your dependencies, you'll have to package them yourself. If you go back and use the existing dependencies (which might be a good idea) then you will have to change your software to use different functions and / or libraries to get the functionality you need. I would like to have the app in the repo before the summit :-) Three weeks left - but definitely doable. (I used apt-cache show... and also searched for the python packages through http://maemo.org/packages/ , but don't know how to continue). I think the best thing for you and your users (remember they are going to use the existing repos too) is for you to limit the amount of dependencies your software uses. Yes, this limits the functionality you can use and also limits the opportunity to use code already written, but it avoids hard to solve dependency problems. Of course, only you can decide exactly what balance you want to strike, but adapting your software to the existing libraries means you are more likely to have stable, well-tested dependencies. Jeremiah___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
On Mon, Sep 21, 2009 at 4:02 PM, Jeremiah Foster jerem...@jeremiahfoster.com wrote: The following packages have unmet dependencies: mclock: Depends: gnome-python (= 2.26.1-1maemo1) Depends: pygtk (= 2.12.1-6maemo7) but it is not installable Depends: pygame (= 1.8.1release-0maemo3) but it is not You are using the wrong package names, you should use: python-gtk2 python-pygame Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debmaster: Help for PyMaemo dependency hell on Fremantle?
Thanks you both for all the support. Unfortunately, from evaluation of your feedbacks, I found out that the information in http://maemo.org/packages/view/mclock/ is outdated and does not reflect the currently uploaded package (build3) but instead still contains the information from an earlier build. The errors mentioned in there were (hopefully) resolved by me in the way you mentioned in build3 which is the most recently uploaded package. Is there a problem with the queue for loading into fremantle extras-devel repository (taking too long) or is my package so wrong (perhaps a py2deb bug)? It did however build OK (https://garage.maemo.org/builder/fremantle/mclock_0.6.0-3/) [2009-09-21 20:55:21] Processing package mclock 0.6.0-3. Uploader: twaelti, builder: builder1 [2009-09-21 20:55:29] Building mclock 0.6.0-3 for target 'maemo-fremantle-i386-extras-devel' [2009-09-21 20:56:26] OK [2009-09-21 20:56:27] Signing build results [2009-09-21 20:56:34] mclock 0.6.0-3 has been queued for loading into fremantle extras-devel repository I will wait for the repository and package view webpage to get updated with the newer build and try again tomorrow. Thanks! -Tom On Mon, Sep 21, 2009 at 4:02 PM, Jeremiah Foster jerem...@jeremiahfoster.com wrote: The following packages have unmet dependencies: mclock: Depends: gnome-python (= 2.26.1-1maemo1) Depends: pygtk (= 2.12.1-6maemo7) but it is not installable Depends: pygame (= 1.8.1release-0maemo3) but it is not You are using the wrong package names, you should use: python-gtk2 python-pygame Regards, ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
