Re: [maemo-developers] packages: soname (0c2a, etc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Murray Cumming schrieb: [snip] I could remove the soname/suffix from the package name, which would involve a few more changes to the debian/ stuff than I'd like to make, so I thought I'd check first. Bad idea :-) Those sonames are in debian to indicate that the abi has changed, and thus the packages depending on that lib needs to be recompiled. But there is no previous version of the package for maemo. Currently not, but who can foresee the future? :) As maemo is just a debian derivate i'd just stick to the original. Makes less problems usually. Cheers Adrian - -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBRMcn92cvsWk2zYzGAQpXIg//UB5RE7kpfxHrMQAWqTL29Xk2CMIX85Ms fO0Ly9PTgJX3RrsX+guJDFZKWd9EsxgfNnwlIZvhpE7D5/0S34k0t2tXGiDpZ6YJ 1ZxiUjmAZ7AyxZStaFrT/ukSedLZwv72QkcWKjw/6HpgKUbUwAEghjp9ZKEnzwSF pXEAT6JHchtIQ5CdM/0gc5m2QK9gbVSWukDCw+gPTkaHDweBVrnPFFFexvC1hyKz MziAuzFH6YPRbQLxqzDYFiu5t2nqgeL22OgSMC0WB5zAPgmOQXJ6FDGfJDD3+9Rq p3HjZ1vXCrq/yRn2dx0cRPcCtaPrFACYCISGs4wwGHdfY0MT+ZOM/R4TQ1oEh6Cs y6W9Aq4wjL7lKmhw/9P06VSuoR3OIOGjo6Q4P2s1/p2H3zEVnY2vjhF7bIsWop/5 /ovhX7gXjbaRRVBZRZl3YKD7c97xSvUe0g2/A5eYk+vIWkldpHh9nOFcYuZB3Q8y hNaUuAmZ1EtssnsZMCw5nfUxKPS9TkJRoqhvcue+mJXdatouog21AGr6k4dkBYiT ivZPkbj1Uy5oY9AuwBokI49rU9mrPBjpX7HTXkqUYlT495lFquiAWG8Ls0YRGf3F IvUsFQ+anovElSj8KC+YgF/Fk69hbG0sJ+V3c/qDWUrXF7l8GLC+2WhCpwqzaMcF jA8n6zp2cbE= =QNu2 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] packages: soname (0c2a, etc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Murray Cumming schrieb: But then the question is What is the original? The latest debian one, or the one with an ABI (combination of g++, glibc, and libstdc++) that's most similar to maemo's current ABI. I suspect it's either etch or unstable. Maybe the Nokia/Maemo people can tell us more. Maybe if I could find a policy document for debian, we could create a policy for maemo. http://www.debian.org/devel/ should contain all information needed. Cheers Adrian - -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBRMcpjGcvsWk2zYzGAQpTmQ/9EArJbqg9U1FHw4HGm5mbATwThovr1RkI /XQgSgsXjdYRnhrvquNIW0OS4sdViq7OPgJYRSdQR/8CbNY2DrM0EFgJ+M4koxVF e1awbKmp+VWv4Imi1ElILVOUHolDfdRklTtkDakbyD74kXzK1yz+1G4u2+rn7sE4 EwYVe5VP/DhESRQzrFqE71QF0Y265srL7+uNegF0qwXe1Ss1JeSKfFmi+MTmDBbz yMQpCGDj4Dh5rDqmlatswAZTsgCQ6IBvXAcfeme4X8CsykVbK5Mz3omNN0m312CC Sje73uLRcRyjcVDXDME+zFaMpqB8vjNNQt3rapT1pq4pWY3ZuVjgi88wehYbhzO5 zYCHXXJVcAglA3yoG9Vgf5ff9BRqD0RRLzrfbM1h9jeHjQvyGqKuZeKV+XNy0a42 OHvV/MeJ3XO3pqLpVemYIrKRdUORIk8lTJfp7g+syaXK2JNhb+eRfFs1SZSMXF8z bljQEO5NsZiPfUIfMB7iaqt2H5Z2u27VJSozbfRfv/wcWO5ePPjVS03wbfCSSapU s1OcMYfjzzMrWXixkIwoWScqbYnI41C+SHe58cREb3qWZopxMHzk+FhVjHcrBPPV Fd4mxMeTC1DGR+FTyU2TrRKj7+0n0yIwUjg2QsZ5GRyQ0GwDvDpP/6M/tWnl/Tho jHph/kSNIR8= =XP6y -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] library updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Koen Kooi schrieb: Cute, but the real problem is something different: Day 1: Florian uploads gpe-calendar 0.99-12 + libeventdb1 0.36-17 Day 2: Neal fixes bug in gpe-calendar, florian upload 0.99-13 Koen uses the AI, gets the updated calendar and rejoices Day 3: Neal fixes a bug in libeventdb1 without affecting API or ABI florian uploads libeventdb1 0.36-18 Koen uses the AI and doesn't get the update, and is sad Day 4: Florian upload libeventdb1 with a Section: user/lib Koen uses the AI, sees the update, and is happy I hope this clears it up a bit :) regards, Koen I see :) Seems like this is a bug then, cause an apt-get update apt-get upgrade would have pulled that lib. What was the section before? just lib? Afaik a section user/lib isn't available in debian :) Cheers Adrian - -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBRMDpuGcvsWk2zYzGAQrVZg//fxJIN2yHoJC9eKNQCRREpqsHQkkXAV50 0jsvsm98yK9qe7QwYhu0y83yItyS5KOtmYCJcKu6/ojVsYMhR4r86ZuQsomfNq8z lMFF6q7IG1YEZ+yj++SnEDMeKVQPpNhc5z9gjgyhjnLODB/qynGdcibWeQiuKZCU t7UPOgFge7+IotpFUSrK9H7QmRPIa8K7uEXWx+Lo1lg6oL8GmeVa7VPmAjofzLMz LREFrWtIt8PnTVDsazrFxVF3UrjmP8ObKM5CUzaiByR2k08CSBkaG4xaDI8ftNko tXimY7kYISd7npPscGzW26rckSEYzonfObKAdnk9jjCHqbeJ2kQzdLkftmK4iTcy 9BMn/EMlGXfTwQKlvVh6HaAmBqDQG29GAB5zkgI29eZFd3ny2vVpbf9+blcG5Kp0 OtRzHPwsa5jU+UAOSesYJYuFW10ZFH+XPoUmNEv9x8q8fZcyYAmlYw7Sxrkyih0X 1T8JUwLVZPQNwnI6hx86DlDEJOtsnMxjAoSbw0yMLTu+P26giyyi78hoKQAdZhvv UU/OSJRv8KA18Nm3SSt/myH6qriOuzCS4mCyHMiKDxpphmQRDf5thjND0T1BVJNy zZX7JGLFU4SJ9T571Tk5qkoany634858g/ZyKlO75y7wvvsJPyY6JxaUOil0X3f/ yhg/s7Cijjw= =DNSe -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] library updates
I suppose you read this: http://www.debian.org/doc/maint-guide/ on how to build proper debian archives. But for that lib problem: it can't be too hard to write a control file like this: snip Build-Depends: libfoo-dev ( = 1.0.0-1), bar (= 1.0.0) /snip This will pull libfoo in a package version = 1.0.0-1 from the archive whilst installing via apt-get install (i suppose this works with this graphical installer too *g*) If libfoo 2.1.0 is in the archive this will still work. If the archive has two libs, same name, but different abi then the libs look like this libfoo1 (this has soname 1) libfoo2 (this has soname 2) so in the end if your software needs libfoo1 you add to the build-depends libfoo1-dev (= ) whilst software which uses libfoo2 has libfoo2-dev (= ...) in the build-depends. If you have question on writing the debian/ stuff feel free to ask. Cheers Adrian PS: I maintain software in the Debian archive. -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 pgpJHjNFiGAbO.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] USB Networking
Ian Malcom schrieb: Hello, The procedures at https://maemo.org/maemowiki/HowToSetUpUsbNetworkingDebian assume that usbnet is part of the kernel. I have Debian 3.1 (sarge), which is a 2.4 kernel. As such, I don't believe usbnet is in there. Can anyone clarify? Thanks! Ian Hi, Debian Sarge ships with a 2.6 Kernel too. If you don't need a 2.4 for very special reasons i would advise to use the 2.6 instead. Anyways... usbnet is in Debian 2.4 kernel too. See here: grep -i usbnet /boot/config-2.4.27-2-686 CONFIG_USB_USBNET=m Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] sources/signatures prob
Thanos Panousis schrieb: An apt-get update or a visit to the application manager gives this output. Both a BAD signature from the official repositories(how can that be possible) and a 404 for the repository.maemo.org. How can I solve this...? W: GPG error: http://catalogue.tableteer.nokia.com mistral Release: The following signatures were invalid: BADSIG CBFC2BECC6903E72 Nokia Internet Tablet Archive Automatic Signing Key [EMAIL PROTECTED] W: You may want to run apt-get update to correct these problems E: Some index files failed to download, they have been ignored, or old ones used instead. You'll probably want to run: gpg –recv-key CBFC2BECC6903E72 gpg –armor –export CBFC2BECC6903E72 | apt-key add - This should make this warning go away :) Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] sources/signatures prob
Thanos Panousis schrieb: You'll probably want to run: gpg –recv-key CBFC2BECC6903E72 gpg –armor –export CBFC2BECC6903E72 | apt-key add - This should make this warning go away :) This is what I get with your commands. Sorry but I 'm not familiar with gpg. nokia770-26:~# gpg --recv-key CBFC2BECC6903E72 gpg: no remote program execution supported gpg: keyserver communications error: general error gpg: keyserver receive failed: general error And more errors for the next command of course gpg: WARNING: nothing exported gpg: no valid OpenPGP data found. you need to specifiy a keyserver then. add this to ~/.gnupg/gpg.conf: keyserver hkp://subkeys.pgp.net or via commandline like this: gpg --recv-key CBFC2BECC6903E72 --keyserver hkp://subkeys.pgp.net Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] sources/signatures prob
Adrian Neumaier schrieb: you need to specifiy a keyserver then. add this to ~/.gnupg/gpg.conf: keyserver hkp://subkeys.pgp.net or via commandline like this: gpg --recv-key CBFC2BECC6903E72 --keyserver hkp://subkeys.pgp.net Cheers Adrian Hmm command line is wrong, this should work: gpg --keyserver hkp://subkeys.pgp.net --recv-key CBFC2BECC6903E72 But oth, i don't find this key neither on hkp://subkeys.pgp.net nor ldap://keyserver.pgp.com Perhaps the Nokia guys haven't uploaded the key yet... Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Error while dist-upgrading to Maemo 2.0 final
Luca Donaggio schrieb: I got this error while doing apt-get dist-upgrade: Unpacking replacement sdk-default-theme-config ... dpkg: error processing /var/cache/apt/archives/sdk-default-theme-config_2.0-3_all.deb (--unpack): trying to overwrite `/usr/share/backgrounds/default_bg.desktop', which is also in package sdk-desktop-backgrounds The rest of the upgrade went fine. Luca Donaggio dpkg -i --force-all /var/cache/apt/archives/sdk-default-theme-config_2.0-3_all.deb will solve this problem. This error is nothing serious; dpkg is just complaining that a file is in two packages. Happens sometimes when the maintainer is not careful or a transition going on. Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building a binary package?
Kuisma Salonen schrieb: Now if you actually would make into your source package directory called 'debian' and put there proper 'rules' file there (please correct me if i am missing something (something that is NOT invoked by debian/rules)), you should have working source package. However at this point it might be easier to stick with debhelper and debian policy, so eventually this could be useful reading: http://www.debian.org/doc/devel-manuals debian/ should have: control, rules, changelog rules: for the actual build rules and what to do control: package description, package dependencies et al changelog: revision of the package, package changelog, ... rules without them is useless. to make it easier there is dh_make available in debian (perhaps thats available for maemo too). for example if you have a sourcedirectory foobar-0.1.2 you can run dh_make in this directory and it will setup a basic debian/ subdirectory with most of the files (some of them with the extension .ex) and a foobar-0.1.2.orig. Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Error while dist-upgrading to Maemo 2.0 final
Luca Donaggio schrieb: 2006/7/10, Adrian Neumaier [EMAIL PROTECTED]: Luca Donaggio schrieb: I got this error while doing apt-get dist-upgrade: Unpacking replacement sdk-default-theme-config ... dpkg: error processing /var/cache/apt/archives/sdk-default-theme-config_2.0-3_all.deb (--unpack): trying to overwrite `/usr/share/backgrounds/default_bg.desktop', which is also in package sdk-desktop-backgrounds The rest of the upgrade went fine. Luca Donaggio dpkg -i --force-all /var/cache/apt/archives/sdk-default-theme-config_2.0-3_all.deb will solve this problem. This error is nothing serious; dpkg is just complaining that a file is in two packages. Happens sometimes when the maintainer is not careful or a transition going on. Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers Thanks Adrian, I did as you told me, and I got this new error: fakeroot dpkg -i --force-all /var/cache/apt/archives/sdk-default-theme-config_2.0-3_all.deb (Reading database ... 24431 files and directories currently installed.) Preparing to replace sdk-default-theme-config 2.0-2 (using .../sdk-default-theme-config_2.0-3_all.deb) ... Unpacking replacement sdk-default-theme-config ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/backgrounds/default_bg.desktop', which is also in package sdk-desktop-backgrounds dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/backgrounds/bg_img_01.png', which is also in package sdk-desktop-backgrounds dpkg: also configuring `gtk2-engines-sapwood' (required by `sdk-default-theme-config') dpkg: also configuring `libgtk2.0-0' (required by `gtk2-engines-sapwood') dpkg: also configuring `libgtk2.0-common' (required by `libgtk2.0-0') dpkg: also configuring `libgtk2.0-bin' (required by `libgtk2.0-0') dpkg: also configuring `libfontconfig1' (required by `libgtk2.0-0') dpkg: also configuring `libfontconfig1' (required by `libgtk2.0-bin') Setting up libfontconfig1 (2.3.2-1osso14) ... dpkg: error processing libfontconfig1 (--install): package libfontconfig1 is already installed and configured Setting up libgtk2.0-common (2.6.10-1.osso21) ... Setting up libgtk2.0-bin (2.6.10-1.osso21) ... Updating the IM modules list for GTK+-2.4.0...done. You don't have gdk-pixbuf loaders directory for version 2.6.0. Use default version instead. Updating the gdk-pixbuf loaders list for GTK+-2.6.0...done. Setting up libgtk2.0-0 (2.6.10-1.osso21) ... Setting up gtk2-engines-sapwood (2.24-1) ... Setting up sdk-default-theme-config (2.0-3) ... Errors were encountered while processing: libfontconfig1 Luca Donaggio Either apt-get install -f or apt-get install --reinstall libfontconfig1 should solve this too. You'll probably want to run an apt-get clean in the end too, so /var/cache/apt/archives/ get's cleaned up (saves some diskspace) Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Error while dist-upgrading to Maemo 2.0 final
Luca Donaggio schrieb: Thanks again Adrian, now everything is working perfectly! Maybe Maemo packagers should consider doing an upgrade of the SDK? Luca Donaggio No problem. Beeing a Debian User (and running Unstable on my main computer at home) i encounter this stuff quite frequently *g*. Did you do your upgrade by invoking apt-get upgrade or apt-get dist-upgrade? If you upgrade from one distribution to another (and i think that mistral-beta and mistral can be considered as two different distributions) it's advised to use dist-upgrade. No idea if an upgrade of the SDK helps, but beeing more careful whilst building the packages would help :) Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] CPU transparency: no NFS support in 2.6.15-omap1?
Am Samstag, 10. Juni 2006 02:12 schrieb Charles 'Buck' Krasic: I'm trying to follow the steps to get CPU transparency with the 2.0 developer image, but sbrsh reports NFS mount failures with 'No such device' errors. I believe this means the 770 kernel doesn't have NFS client support?Has anyone else tried it yet? -- Buck Hmm the 1.1 release does contain nfs support in the Kernel. You can check by do a cat /proc/filesystems. If you find a nodev nfs then you have nfs client support in the kernel. Cheers Adrian -- GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org) Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97 pgpuHhP2to7Gx.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
