Re: Feature upgrade has given me the bluez - users must remove my app to upgrade
On Wed, Dec 17, 2008 at 9:04 PM, tz tho...@mich.com wrote: This is why NOKIA has to link the tools/sdk packages instead of me doing so in extras. Actually, no, this is why you shouldn't put packages that don't belong in a section with a user/ prefix in user/. . . . Application Manager won't replace packages in user/ with packages that aren't in user/. It's as simple as that. I can't even retrieve osso7 using apt-get source! It keeps getting osso4. That tends to happen when you're fetching from the wrong repository. http://repository.maemo.org/pool/maemo4.1.2/free/b/bluez-utils/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Feature upgrade has given me the bluez - users must remove my app to upgrade
Worse, python2.5-bluez and python2.5-gnome can't be pulled in as dependencies although they are still in Extras. I can find them manually, but they are listed as problems when I try to install minigpsd. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Feature upgrade has given me the bluez - users must remove my app to upgrade
On Thu, Dec 18, 2008 at 7:15 AM, Ryan Abel rabe...@gmail.com wrote: On Wed, Dec 17, 2008 at 9:04 PM, tz tho...@mich.com wrote: I can't even retrieve osso7 using apt-get source! It keeps getting osso4. That tends to happen when you're fetching from the wrong repository. http://repository.maemo.org/pool/maemo4.1.2/free/b/bluez-utils/ diablo is what is in /etc/apt in the sources. Not maemo4.1.2. So do I sed s/diablo/maemo4.1.2/g or wait for something else? I did do the dist-upgrade since that is what it says to do. I love it when I follow instructions precisely and everything breaks. Though the repositories seem to be updating/moving/relinking. Dependencies appear to be resolving. Do I have to reinstall the entire SDK every time they increment the third digit? Also, where is bluez-utils*osso6* ? I think bluez is GPL and the requirement is for the binaries corresponding to the source, not some random (even later, fixed) version. The SSE installed osso6 on the devices, but the SDK has ONLY osso7. I need to generate an osso6 version, or Nokia has to somehow increment bluez-utilities in the SSE to osso7. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Feature upgrade has given me the bluez - users must remove my app to upgrade
This is why NOKIA has to link the tools/sdk packages instead of me doing so in extras. The feature upgrade apparently has set things to bluez-utils-osso6. I haven't verified this. The only things in the repository are osso7. And when I create bluez-utils-test, it will be the current version so when Nokia upgrades, users will HAVE TO REMOVE MY APPLICATION because they will have to remove the old bluez-utils-test-osso4 to upgrade and it is a dependency of my program. Now I have to try to figure out if the report is wrong. If it is wrong and the version is osso7, I now have to play catch-up. I could compile a broken version that doesn't have any osso dependencies and wait for something really bad to happen. But as I noted, the package is not mine, it is Nokias, and Nokia will change the base when they feel like it, and I'm stuck. I can't even retrieve osso7 using apt-get source! It keeps getting osso4. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
