Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
On Wed, Mar 11, 2009 at 10:16:06PM -0400, Stefan Monnier wrote: When installing opk/ipk packages from e.g. http://www.opkg.org/, there will be problems with unmet dependencies because Debian uses other package names for some of the packages providing the dependencies. I've created a few small packages which create a mapping of the package names so tricks like --force-depends/--ignore-depends should not be necessary. See: http://nospamnospam.homepage.dk/software/download/oedepmappings/ [snip] Also, it would probably be preferable for those packages to have a name that makes it clear that they're not real. E.g. you might call them something like adapter-opkg-foo, and then have them provide the required feature. I would if APT supported it. Unfortunately, the APT support for Provides: is buggy enough that it only works for packages which are already installed, and I'm hoping to eventually be able to do something like # apt-install-package-file http://www.opkg.org/package.opk and have APT install the dependencies automatically (including having them marked as such). -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
maybe it would be easier... or maybe not... opkg and deb packages are similar, so it would be nice to have a cross-tool. As you can see debian packaging some times is slow... that's why sometimes it may be useful to test opkg apps directly. (and after all.. linux is choice, isn't it?) nobody out there, willing to adapt/extend alien? that's the tool written for exactly such purposes -- would be sensible to make it handle [i|o]pk as well, wouldn't it? If you want to give a try, you can starting compiling navit, that right now it's missing on deb repos. i asked today the owner of http://navit.latouche.info/debian/sid/, if he/she could provide an armel deb as well. for the moment i put my newly built deb up to http://www.ginguppin.de/node/26 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
Stefan Monnier monn...@iro.umontreal.ca writes: Well, since [io]pkgs can be found in all kinds of places, it would definitely be preferable to just be able to install [io]pkgs directly Yep but then apt-get --build source does not work. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
Hi list I think also it would be easier and much better to create deb packages. I think the opkg.org website is a very good portal for the dynamism of the community. Why not: * modifiy opkg.org so that for each software, we have 2 text boxes on the right side (where you copy.cut the installation command) : one for ipk, one for deb. * add a Help developper to package page in this website, with a tar containing a foobar application : one for ipk (with ipkg-build), one for debian (I do not know yet what to use :D ) This way everyone can really have the choice of distribution without lacking of openmoko oriented softwares. What do you think ? Kimaidou 2009/3/12 Timo Juhani Lindfors timo.lindf...@iki.fi Rask Ingemann Lambertsen r...@sygehus.dk writes: Nice it would be grat in future if we (debian users) could just add opkg repos as deb ones... maybe with different priority... it may be difficult and risky, but indeed useful! Wouldn't it be much easier to just create real debian packages? If you have some example programs I can give examples of how you can create unofficial debian packages of those. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[OPKG.org] suggestions (was : [debian] Installing *.ipk/*.opk part 1: Dependencies)
maybe some folks weren't interested in the original topic. i do not know php, but maybe someone else can help. i am also forwarding this mail to the german freeyourphone forum. i hope you guys don't mind reposting + top-posting this time. kimaidou schrieb: Hi list I think also it would be easier and much better to create deb packages. I think the opkg.org http://opkg.org website is a very good portal for the dynamism of the community. Why not: * modifiy opkg.org http://opkg.org so that for each software, we have 2 text boxes on the right side (where you copy.cut the installation command) : one for ipk, one for deb. * add a Help developper to package page in this website, with a tar containing a foobar application : one for ipk (with ipkg-build), one for debian (I do not know yet what to use :D ) This way everyone can really have the choice of distribution without lacking of openmoko oriented softwares. What do you think ? Kimaidou 2009/3/12 Timo Juhani Lindfors timo.lindf...@iki.fi mailto:timo.lindf...@iki.fi Rask Ingemann Lambertsen r...@sygehus.dk mailto:r...@sygehus.dk writes: Nice it would be grat in future if we (debian users) could just add opkg repos as deb ones... maybe with different priority... it may be difficult and risky, but indeed useful! Wouldn't it be much easier to just create real debian packages? If you have some example programs I can give examples of how you can create unofficial debian packages of those. ___ Openmoko community mailing list community@lists.openmoko.org mailto:community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
maybe it would be easier... or maybe not... opkg and deb packages are similar, so it would be nice to have a cross-tool. As you can see debian packaging some times is slow... that's why sometimes it may be useful to test opkg apps directly. (and after all.. linux is choice, isn't it?) If you want to give a try, you can starting compiling navit, that right now it's missing on deb repos. d On Thu, Mar 12, 2009 at 11:25 PM, Timo Juhani Lindfors timo.lindf...@iki.fi wrote: Rask Ingemann Lambertsen r...@sygehus.dk writes: Nice it would be grat in future if we (debian users) could just add opkg repos as deb ones... maybe with different priority... it may be difficult and risky, but indeed useful! Wouldn't it be much easier to just create real debian packages? If you have some example programs I can give examples of how you can create unofficial debian packages of those. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
Nice it would be grat in future if we (debian users) could just add opkg repos as deb ones... maybe with different priority... it may be difficult and risky, but indeed useful! Wouldn't it be much easier to just create real debian packages? Well, since [io]pkgs can be found in all kinds of places, it would definitely be preferable to just be able to install [io]pkgs directly without depending on the willingness to make a .deb variant of it. Of course, another option is to create a tool like Alien that takes a .[io]pk and turns it into a .deb. Most likely such a tool would mostly tweak the architecture tag and adjust a few dependencies. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
On Wed, Mar 11, 2009 at 08:00:51PM +0100, Davide Scaini wrote:
Nice it would be grat in future if we (debian users) could just add opkg
repos as deb ones... maybe with different priority... it may be difficult
and risky, but indeed useful!
d
Once the Packages.gz on opkg.org is fixed, this ought to do the trick:
# echo 'deb http://www.opkg.org/packages/ /'
/etc/apt/sources.list.d/opkg.org.list
Currently, the procedure is a bit more involved:
1. Update the package list.
# apt-get update
2. Delete empty dependency lists.
3. Delete junk between package sections.
# sed -i -n -e '/^Depends: *$/ n' -e '/^Package: /,/^$/ p'
/var/lib/apt/lists/www.opkg.org_packages_Packages
4. Fix missing commas in dependency lists.
# sed -i -e '/^Depends: / s/\([[:alnum:]]\) \([[:alnum:]]\)/\1, \2/g'
/var/lib/apt/lists/www.opkg.org_packages_Packages
5. Change the architecture to armel.
# sed -i -e 's/^Architecture: arm.*/Architecture: armel/'
/var/lib/apt/lists/www.opkg.org_packages_Packages
However, apt-get seems to dislike the www.opkg.org server:
# apt-get -o 'DPkg::Options={--force-architecture;}' install gwaterpas
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libfltk
The following NEW packages will be installed:
gwaterpas libfltk
0 upgraded, 2 newly installed, 0 to remove and 210 not upgraded.
Need to get 570B of archives.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
libfltk gwaterpas
Install these packages without verification [y/N]? y
Get:1 http://nospamnospam.homepage.dk libfltk 1.1.9-6 [570B]
Get:2 http://www.opkg.org gwaterpas 0.2 [8620B]
Fetched 9190B in 0s (15.4kB/s)
Failed to fetch http://www.opkg.org/packages/gwaterpas_0.2_armv4t.ipk Size
mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?
--
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
Rask Ingemann Lambertsen r...@sygehus.dk writes: Nice it would be grat in future if we (debian users) could just add opkg repos as deb ones... maybe with different priority... it may be difficult and risky, but indeed useful! Wouldn't it be much easier to just create real debian packages? If you have some example programs I can give examples of how you can create unofficial debian packages of those. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian] Installing *.ipk/*.opk part 1: Dependencies
When installing opk/ipk packages from e.g. http://www.opkg.org/, there will be problems with unmet dependencies because Debian uses other package names for some of the packages providing the dependencies. I've created a few small packages which create a mapping of the package names so tricks like --force-depends/--ignore-depends should not be necessary. See: http://nospamnospam.homepage.dk/software/download/oedepmappings/ It works as a repository too if you run this as root: # echo 'deb http://nospamnospam.homepage.dk/software/download/oedepmappings/ /' /etc/apt/sources.list.d/ril-oedepmappings.list -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
Nice it would be grat in future if we (debian users) could just add opkg repos as deb ones... maybe with different priority... it may be difficult and risky, but indeed useful! d On Wed, Mar 11, 2009 at 11:56 AM, Rask Ingemann Lambertsen r...@sygehus.dkwrote: When installing opk/ipk packages from e.g. http://www.opkg.org/, there will be problems with unmet dependencies because Debian uses other package names for some of the packages providing the dependencies. I've created a few small packages which create a mapping of the package names so tricks like --force-depends/--ignore-depends should not be necessary. See: http://nospamnospam.homepage.dk/software/download/oedepmappings/ It works as a repository too if you run this as root: # echo 'deb http://nospamnospam.homepage.dk/software/download/oedepmappings/ /' /etc/apt/sources.list.d/ril-oedepmappings.list -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
Rask == Rask Ingemann Lambertsen r...@sygehus.dk writes: When installing opk/ipk packages from e.g. http://www.opkg.org/, there will be problems with unmet dependencies because Debian uses other package names for some of the packages providing the dependencies. I've created a few small packages which create a mapping of the package names so tricks like --force-depends/--ignore-depends should not be necessary. See: http://nospamnospam.homepage.dk/software/download/oedepmappings/ It works as a repository too if you run this as root: # echo 'deb http://nospamnospam.homepage.dk/software/download/oedepmappings/ /' /etc/apt/sources.list.d/ril-oedepmappings.list You might want to add a note about it to http://wiki.debian.org/DebianOnFreeRunner (or maybe http://wiki.openmoko.org/wiki/Debian). Stefan PS: I wish those two pages were merged into one. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Installing *.ipk/*.opk part 1: Dependencies
When installing opk/ipk packages from e.g. http://www.opkg.org/, there will be problems with unmet dependencies because Debian uses other package names for some of the packages providing the dependencies. I've created a few small packages which create a mapping of the package names so tricks like --force-depends/--ignore-depends should not be necessary. See: http://nospamnospam.homepage.dk/software/download/oedepmappings/ It works as a repository too if you run this as root: # echo 'deb http://nospamnospam.homepage.dk/software/download/oedepmappings/ /' /etc/apt/sources.list.d/ril-oedepmappings.list You might want to add a note about it to http://wiki.debian.org/DebianOnFreeRunner (or maybe http://wiki.openmoko.org/wiki/Debian). Also, it would probably be preferable for those packages to have a name that makes it clear that they're not real. E.g. you might call them something like adapter-opkg-foo, and then have them provide the required feature. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
