**** BEGIN LOGGING AT Thu Jul 13 03:00:03 2017 Jul 13 04:02:26 enyc: what's the problem with porting maemo to Neo900? technically maemo doesn't even need any porting for Neo900, it's the same platform Jul 13 04:03:46 even the PVR should be backward compatible to the slightly lower version number in OMAP3430 Jul 13 04:04:12 the ONALY thing that gives me worries is NOLO Jul 13 04:04:19 ONLY* Jul 13 04:05:27 even BME is no issue, we simply don't need it in Neo900 Jul 13 04:08:07 what actually changes in hw is the modem (new one being a really open protocol, inlike the friggin ISI on BB5 modem) incl audio via standard PCM instead ISI, and the WLAN/BT module, though that's close enough to what's in N900 to not really introduce major problems, just new firmware needed I'd think Jul 13 04:37:48 DocScrutinizer05: N900's NOLO is used in Neo900? Jul 13 04:38:12 err, I don't think so, see above Jul 13 04:38:52 mmm yeah, hardware init's gonna be ever so slightly different. guessing it'll be u-boot SPL? Jul 13 04:38:59 somebody will have to patch uBoot to fully replace all necessary NOLO functions Jul 13 04:41:05 but the reference TI x-loader should be enough to boot u-boot right? Jul 13 05:05:37 yep Jul 13 05:06:33 not only should, MUST Jul 13 05:07:10 and is proven to work Jul 13 05:07:46 what's not proven is particularly maemo coming up without NOLO doing some arcane init for it Jul 13 05:08:14 though nobody found out so far what exactly Jul 13 05:08:55 not like a lot of tests and investigating had been done at all Jul 13 05:09:38 Pali once tried to boot maemo with xloder->uBoot->linux iirc, and reported problems Jul 13 05:09:58 s/linux/maemo fremantle/ Jul 13 05:11:20 quite possibly could have been one of the watchdogs, or the modem at large Jul 13 05:12:10 or, don't know, GP xloader instead of HS-xloader Jul 13 05:14:06 Neo900 anyway is a GP device, while N900 is a HS device in GP mode Jul 13 05:15:03 so on Neo900 the GP xloader should work Jul 13 05:26:26 DocScrutinizer05: n900 is HS device in HS mode :) Jul 13 05:32:31 is it? Jul 13 05:32:54 well, seems the xloader already drops the ball, no? Jul 13 05:35:04 I'm not 100% clear if there's a true GP mode on HS devices Jul 13 05:36:14 I'm also not sure about GP devices checksumming the xloader or not, and if yes then with which cert Jul 13 05:43:45 DocScrutinizer05: it is not about bootloader signatures only, there is more than that Jul 13 05:43:56 firewalls, etc Jul 13 05:44:00 I know Jul 13 05:44:18 but all that isn't available to GP devices Jul 13 05:44:28 also, HS devices have crypto module while GO does not afaik Jul 13 05:44:33 *GP Jul 13 05:44:49 and not available to HS devices in tainted mode - at least most of it Jul 13 05:45:28 tainted mode? you can;t boot unsigned bootloader so no way to taint it Jul 13 05:46:07 I *rhink* this was a paradox, in that GP devices have the crypto hardware available to 'userland' while in HS devices it's hidden behind the firewalls in DOM0 aka whatever monitor Jul 13 05:46:54 you can drop the DOM0 control Jul 13 05:47:38 if N900 wasn't 'tainted' then you could do full control over all the firewalls and stuff Jul 13 05:47:54 others call it 'sealed' Jul 13 05:51:00 the idea of M-Shield / trustzone is to have the system split into a secure land and a userland. The processes running in secure land have full control over the complete hardware and the userland processes. Much like virtualization Jul 13 05:51:29 when there's not a single process running in secure mode anymore, you basically dropped or tainted secure mode Jul 13 05:52:14 ah, I see what you meant Jul 13 05:52:17 I don't know if any processes run in secure mode on N900 Jul 13 05:52:27 I don't think so Jul 13 05:52:49 there is afaik Jul 13 05:53:01 think about the modem PPA Jul 13 05:53:15 what's PPA? Jul 13 05:53:51 Primary Protected Application Jul 13 05:54:16 modem is a separate system pretty much unlinked from maemo system and OMAP3430 Jul 13 05:54:20 though PPA might not be the correct term here Jul 13 05:54:38 DocScrutinizer05: part of the modem FW runs on OMAP Jul 13 05:54:44 nope Jul 13 05:54:45 afaik Jul 13 05:55:03 at least it exposes supervisor functions Jul 13 05:55:18 or "BIOS" functions Jul 13 05:55:26 the OMAP? yes Jul 13 05:55:42 and moded FW adds to that Jul 13 05:55:50 it exposes additional functions Jul 13 05:55:54 that's why I said I don't know if it runs any (waiting) secure processes Jul 13 05:56:16 that's why I said there are :) Jul 13 05:56:19 I know you're calling that monitor Jul 13 05:56:25 mhm Jul 13 05:57:04 also, on n900 omap there is a some memory chuck reserved for the modem FW Jul 13 05:57:09 iirc Jul 13 05:57:12 could mean there's a process warting for a hw trigger, like a mailbox (FIFO) event or a write to a special RAM addr Jul 13 05:57:21 yep, exactly Jul 13 05:58:21 if there was a memory chunk reserved for modem, we would need a blob in flash to store the firmware that's running in there Jul 13 05:58:42 there is Jul 13 05:58:48 that's pretty much exactly what e.g jolla does Jul 13 05:58:53 * freemangordon tries to find it Jul 13 05:59:33 it has a few partitions to store the modem firmware Jul 13 06:00:13 those are protected by checksum so user can't tamper with them Jul 13 06:00:35 can't see any faintly similar thing in maemo storage Jul 13 06:01:20 the "cmt" stuff Jul 13 06:01:30 part of it runs on OMAP, afaik Jul 13 06:01:42 those are drivers afaik Jul 13 06:02:00 and they run as normal processes under linux Jul 13 06:02:33 no, this is BB5 firmware and part of it is loaded as secure application on OMAP, don;t ask me how Jul 13 06:02:47 but I do :-) Jul 13 06:03:05 there is PPA call called something like "load PA" Jul 13 06:03:08 which file exactly? Jul 13 06:03:21 cmt-2nd Jul 13 06:03:28 cmt-algo Jul 13 06:03:40 those are FIASCO parts Jul 13 06:03:49 and cmt-mcusw, but this is what runs on BB5 I guess Jul 13 06:03:55 never seen them on OMAP maemo filesystem Jul 13 06:03:56 yes, part of FIASKO Jul 13 06:04:09 but it doesn;t really matter Jul 13 06:04:30 those are stored in the modem Jul 13 06:04:48 ooh it matters a whole friggin lot, this is exactly the backdoor into your system you don't want Jul 13 06:04:52 anyway/ me got to run Jul 13 06:04:59 sure Jul 13 06:05:16 but only if that code is running on OMAP not modem Jul 13 06:05:21 this is not like jolla and other MT socs Jul 13 06:05:40 well, AFAIK part of that code runs on OMAP Jul 13 06:05:48 might be wrong though Jul 13 06:06:18 however, bye, gtg Jul 13 06:06:36 I wouldn't know what it got to do there, since the modem itself is only attached via a SSI interface and a few GPIOs Jul 13 06:07:18 But I guess NOLO knows how to talk with it Jul 13 06:07:22 and libisi is talking directly to HSI/SSI Jul 13 06:08:10 so you could safely delete those blobs and get rid of the processes that are run from them, they don't contribute to the modem function after all Jul 13 06:09:14 note that ISI once been 'publicly' specified Jul 13 06:09:51 DocScrutinizer05: I am not 100% sure those run on OMAP, it could be the 2nd stage BL for the OMAP in BB% along with its PPA and OS Jul 13 06:10:19 so you could talk to the SSI interface from any arbitrary system, without any userland/APE arcane processes Jul 13 06:10:40 yes, that's most likely what it is Jul 13 06:12:36 in OMAP secure land only processes started from ROMBL, xloader, and possibly NOLO Jul 13 06:12:48 aiui Jul 13 06:13:46 you *could* call a monitor function to load a new process from userland storage into secure land, but that would only fly if that code is crypto-protected Jul 13 06:16:18 well, if there's already a supervisor process running in secure, then that process as well could load more stuff from userland storage, check the signature, decrypt, and start a process from it Jul 13 06:26:00 re modem and what it can do on system: aiui there's one of the watchdogs actually living on modem, pinging libisi I guess, and when it times out, it can reboot the APE OMAP via a GPIO Jul 13 06:27:57 same works in other direction too, APE can instruct modem to reboot and I guess libisi or cmt-whatever (prolly must be a process in the end) has a warchdog pinging the modem and resetting it via a GPIO when timing out Jul 13 08:01:00 hi all Jul 13 08:02:03 https://bpaste.net/show/941fbf4f87a7 Jul 13 08:02:30 matrix-pidgin Jul 13 08:03:07 libmatrix.h:96:18: error: glib.h: No such file or directory Jul 13 08:03:14 you miss a bunch of -dev packages Jul 13 08:03:37 and build/lib programs too Jul 13 08:03:45 make: pkg-config: Command not found Jul 13 08:03:52 aha yes Jul 13 08:04:49 KotCzarny do you think it's possible to fix? Jul 13 08:05:02 if one knows what he is doing, maybe Jul 13 08:05:22 but if they need recent libs, it will be hard Jul 13 08:08:01 KotCzarny https://bpaste.net/show/fde962c671d5 Jul 13 08:08:17 what can you say about this? Jul 13 08:08:29 omemo for pidgin Jul 13 08:09:32 missing lib, read the install instruction for that package Jul 13 08:10:26 https://github.com/gkdr/lurch Jul 13 08:11:45 ibpurple-dev, libmxml-dev, libxml2-dev, libsqlite3-dev, libgcrypt20-dev yes? Jul 13 08:13:37 seems that you didnt dl/unpack libsignal-protocol-c Jul 13 08:14:10 the path looks weird to me Jul 13 08:14:35 no clue here though Jul 13 08:15:06 just wondering what's /lib/axc/lib Jul 13 08:19:08 particularly for *building* stuff there Jul 13 08:22:28 ok i try Jul 13 08:22:47 are you trying to build on device? Jul 13 08:22:53 *sigh* Jul 13 08:23:33 anyway, iirc purple-matrix needs a newer glib/json than available on maemo5, so .... Jul 13 08:23:51 (not absoluetly certain about that but I think I checked back then) Jul 13 08:26:33 when you'r actually building in a genuine maemo environment (on device, in emu) then you don't have and shall not have write access in /lib/ as user anyway, and that's absolutely fine. Packages shouldn't build in /lib/ Jul 13 08:27:01 sorry friends I do not know much English Jul 13 08:27:35 so I have a library that would fix the problem? :) Jul 13 08:27:45 do not use "cd /lib/..." for "make" Jul 13 08:28:47 https://bpaste.net/show/44a1767099ec Jul 13 08:30:57 Nokia-N900:/home/user/MyDocs/lurch# make Jul 13 08:30:58 cd ./lib/axc/lib/libsignal-protocol-c/ && \ Jul 13 08:31:00 mkdir -p build && \ Jul 13 08:31:01 is ODD Jul 13 08:31:18 that make job is nonsense in my book Jul 13 08:31:31 change your glasses, that's relative dir Jul 13 08:31:39 duh!!! Jul 13 08:31:46 indeed missing my glasses Jul 13 08:32:17 vahe[m]: nevermind, I was wrong Jul 13 08:33:10 :) Jul 13 08:33:27 I think it is interesting Jul 13 08:33:45 there's hardly anything more nasty than a cd ./foo... since a cd foo would do as well Jul 13 08:34:20 why not updated pidgin? and how can I update ? Jul 13 08:35:30 2.12.0 Jul 13 08:35:47 it would be cool Jul 13 08:36:05 updating pidgin might be do-able actually Jul 13 08:36:50 I have now 2.10.11 Jul 13 08:37:15 well, I'm waiting for that maemo.org update in repo Jul 13 08:37:35 but that's completely unrelated to your matrix plugin Jul 13 08:38:07 I got another new N900 I have to use not less than 10 years))) Jul 13 08:38:37 bencoh Yes, you rightly said, but I stopped not know what to do Jul 13 08:38:51 + omemo plugin Jul 13 08:39:15 may the problem is that I eat everything all at once :P Jul 13 08:39:38 1. you shouldn't build on device (n900) Jul 13 08:39:42 may the problem is that I want to do everything at once Jul 13 08:39:42 build using scratchbox Jul 13 08:39:50 you'll only get troubles by building on device Jul 13 08:39:59 everything will just be more complicated Jul 13 08:40:50 2. you should probably learn more about building process Jul 13 08:41:31 as for the glib/json version issue, trying to build it shows minor problems regarding glib Jul 13 08:41:41 json should be fine Jul 13 08:41:57 and the minor glib issues seam relatively easy to fix/workaround Jul 13 08:42:00 seem* Jul 13 08:42:21 aha thansk Jul 13 08:42:23 then you'll have to build/import http_parser Jul 13 08:42:29 bencoh building process? Jul 13 08:43:15 (http-parser should be pretty simple/standalone, unless it got bloated during the past years) Jul 13 08:43:59 vahe[m]: how to build projects in general and which tools you need / how to troubleshoot issues Jul 13 08:44:12 * DocScrutinizer05 could come up with just two valid usecases for ./ when addressing a binary in local dir that also exists in path: ./date, or when filename is borked: cd ./-badidea Jul 13 08:44:45 I don't like complicated ,so it's easier for me to refuse the setting of the matrix and оmemo Jul 13 08:45:06 I thought maybe just need to add the lib Jul 13 08:45:11 doc: or when include lib is built outside current program tree and prefix is dynamic Jul 13 08:45:16 DocScrutinizer05: you forgot about paths splitted in several $VAR Jul 13 08:45:28 $TOP/foo/bar Jul 13 08:45:29 hmmm Jul 13 08:45:37 anyway Jul 13 08:45:43 yeah Jul 13 08:47:10 TOP=`cwd` Jul 13 08:47:55 err pwd Jul 13 08:49:10 bencoh libhttp_parser you say no for Maemo? Jul 13 08:49:53 sorry, I bad know English Jul 13 08:50:05 and probably did not understand that Jul 13 08:52:03 he said it should be simple to build Jul 13 08:53:44 thanks all Jul 13 08:54:06 but use scratchbox! not on device Jul 13 08:54:25 ~sb Jul 13 08:54:40 fsckng bot! Jul 13 08:56:25 ~sb Jul 13 08:56:27 methinks scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB Jul 13 08:58:21 vahe[m]: http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide Jul 13 08:58:50 http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Development_Environment/Maemo_SDK Jul 13 08:59:14 I'm not familiar with scratchbox, but be sure to get acquainted now Jul 13 08:59:17 thanks again :) Jul 13 08:59:57 get the VM, most easy way to use sb Jul 13 09:00:04 http://maemo.merlin1991.at/files/SB Jul 13 09:00:49 it's a VM image Jul 13 09:01:18 virtualbox etc Jul 13 09:03:14 ah ok Jul 13 09:03:26 installing scratchbox is a tad annoying and tedious otherwise Jul 13 09:03:42 DocScrutinizer05: hrrm why 10.04 outdated system ooi ??? Jul 13 09:04:04 hm? Jul 13 09:04:11 because maemo is old. 2010. Jul 13 09:04:19 the txt along with that image suggests 10.04 lts Jul 13 09:04:24 no longer in pattches Jul 13 09:04:51 so what? you're not supposed to browse the internet with this VM Jul 13 09:05:13 it has all the tools you need and they fit together Jul 13 09:05:30 right, but what about compiler bugs, kernel, things like update for stack-clash vulnerability, .... Jul 13 09:06:19 when you're interested in keeping sb up to date, you rather install genuine Jul 13 09:06:27 you didnt get the 'maemo is old' part, did you? Jul 13 09:06:29 good luck! Jul 13 09:06:41 n900 runs with 2.6.28 kernel Jul 13 09:08:43 enyc: actually maemo packages require such old autotools, it craps itself on some things on kernels > 2.6 ... Jul 13 09:11:23 hrrrrrrrm Jul 13 09:14:20 also libtool and autotools in sdk repo don't excalty play along which is why the scratchbox makes some vodoo, which in turn isn't available if you install a recent version of scratchbox... Jul 13 09:14:31 it's a big everything too old clusterfuck Jul 13 09:14:59 you notice ie. that argz.m4 is missing but used if you install the latest scratchbox natively Jul 13 09:21:12 "'s a big everything too old clusterfuck" indeed :/ Jul 13 09:38:26 http://muarf.org/~bencoh/maemo/libmatrix.so no fucking idea whether this is supposed to work, but ... feel free to try Jul 13 09:44:46 i see ;p Jul 13 09:45:09 KotCzarny: the 2.6.28 kernel being heavily-patched from original for drivers and allsorts? Jul 13 09:47:40 no Jul 13 09:48:30 it just has dirivers that are not, or were not, upstreamed back when. Most are now, though Jul 13 10:13:19 So, what's involved in producing a 2.6.32 -or- 3.2 or 3.16 or 4.9/newer kernel for N900 // old-maemo ?? would that be driver-interface-incompatible with older software? Jul 13 10:13:51 was pointed out to me 2.6.32 maintaned by RHEL6 / centos 6.9 so could at least build a security-patched 2.6.32 kernel in first-instance... Jul 13 10:18:15 (if that would work with the drivers-for-2.6.28 ??) Jul 13 10:27:32 enyc: even if it works that would mean you have a recent kernel, yay Jul 13 10:27:38 now go and update *everyhing else* Jul 13 10:28:22 actually people do have recent kernel with patches ontop to export interfaces for old maemo running Jul 13 10:28:40 but as far as security goes that is like a single drop ontop a forestfire Jul 13 10:29:35 merlin1991: that figures Jul 13 12:20:13 merlin1991: what does this mean//say about usefulness of porting maemo to newer hardware, neo900 or otherwise...? Jul 13 12:20:55 merlin1991: vs. just making a newer debian//devuan//whatever linux work on open//semi-open HW gadget ? Jul 13 12:21:15 linux / gnu / whatever desktop, i should say Jul 13 12:39:48 enyc: actually some are already trying to port/rebase (bits of) maemo on top of de{bi,vu}an Jul 13 12:42:39 bencoh: ok that makes sense, where are repos, wikis, IRC channels, testable versions, ??? Jul 13 12:43:37 in the git Jul 13 12:43:46 and you are on the channel Jul 13 12:45:30 join #fptp Jul 13 12:45:50 hrrm err there was a fptf at some poi too... Jul 13 12:45:57 * enyc looks confused Jul 13 12:46:19 KotCzarny: what git where? what wiki? whats' workable//installable at the moment? Jul 13 14:55:10 enyc: you can check out https://github.com/fremantle-gtk3/ Jul 13 14:55:31 it has lots of bits that are part of the core maemo experience there already Jul 13 14:57:35 hm at least I think that is the right one Jul 13 14:58:55 [D Jul 13 14:59:07 sorry, Jul 13 14:59:44 was that the gtk crapper utf code that breaks xchat on maemo? :D Jul 13 15:01:34 haha. no. some crap i had in my irssi Jul 13 15:01:50 merlin1991: enyc: https://github.com/fremantle-gtk2/ Jul 13 15:02:00 uh Jul 13 15:02:02 * merlin1991 hides Jul 13 15:02:05 gtk3 port is suspended for a while Jul 13 15:02:33 is gtk2 still seeing upstream support? Jul 13 15:02:44 afaik yes Jul 13 15:02:54 support == bugfixes Jul 13 15:03:21 after all there are a couple of DEs still using it Jul 13 15:03:39 what's that gnome fork that sticks with gtk2? Jul 13 15:03:49 lxde? Jul 13 15:04:05 or was it xfce, not sure Jul 13 15:04:35 looks like they are still doing stuff on gtk2.x Jul 13 15:04:36 https://git.gnome.org/browse/gtk+/log/?h=gtk-2-24 Jul 13 15:04:52 what made you suspend the gtk3 efforts? Jul 13 15:05:08 too many pieces are missing Jul 13 15:05:39 so I would have lost focus fighting with gtk instead of maemo as a whole Jul 13 15:05:44 gnome fork was mate iirc Jul 13 15:14:10 MATE, ported to gtk3 enitrely in latest Mint 18.2 release... Jul 13 15:14:28 but MATE versions using gtk2 still about // in use Jul 13 16:23:58 now that's strange .... http://maemo.org/packages/repository/builds/fremantle_extras-devel_free_source/all/ Jul 13 16:24:25 the "latest builds" preview on the right side is outdated Jul 13 18:03:16 not strange, that's called "midgard" ;-) Jul 13 18:04:00 prolly one of the midgard "cronjobs" (some really weird thing) craped his pants Jul 13 18:06:11 only a 2 or maybe 3 people on this planet would know where to look at to start trying to fix it. I'm not one of them Jul 13 18:16:30 don't ask me to understand this: http://wstaw.org/m/2017/07/13/plasma-desktopvI8317.png Jul 13 18:21:59 say this loud and fast, 5 times: >>Packages Package Packageevent<< ! http://wstaw.org/m/2017/07/13/plasma-desktophr8317.png Jul 13 18:23:16 sorry, feeling this headache again. Already forgot about it the last few years as long as I didn't look at that shit anymore Jul 13 18:24:35 >>Comments Comment<< >>Favourites Favourite<< Jul 13 18:25:38 * DocScrutinizer05 sings "tag link - linktagtag, tag link linktagtag" Jul 13 18:26:31 * DocScrutinizer05 got that midgard madness again :-S WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHH! Jul 13 18:28:04 Alt+F4 to the rescue Jul 13 19:27:18 Hi guis Jul 13 19:29:18 i'm trying to install python 2.4 with synaptic on my n900, but synaptic still try to use old repos Jul 13 19:39:18 is the muarf mirror work? Jul 13 19:39:57 yes Jul 13 19:40:35 so why synaptic can't work with it? Jul 13 19:40:56 but I doubt it has python2.4 Jul 13 19:41:28 crap Jul 13 19:41:40 you should probably check: Jul 13 19:41:45 ~plg Jul 13 19:41:50 ~pkg Jul 13 19:42:00 ~packages Jul 13 19:42:03 pkg is probably http://maemo.org/packages/ Jul 13 19:42:25 ~ping Jul 13 19:42:25 ~pong Jul 13 19:42:27 its very important to me to get pyobd on my n900 Jul 13 19:42:30 ~rtt Jul 13 19:42:30 hmm... rtt is round trip time Jul 13 19:43:57 kalin: why python2.4? Jul 13 19:44:56 pyobd dependecies... Jul 13 19:45:14 and pyserial Jul 13 19:46:45 I need to run this app to finish my education Jul 13 19:47:43 seems like python.2.4.4 (final bugfix release) was released in 2005 and since then python2.5 is recommended? Jul 13 19:48:49 I doubt you could find python2.4 for maemo, when it shipped with python2.5 a 8 years ago Jul 13 19:49:10 what you suppose to i do? Jul 13 19:49:25 education? Jul 13 19:49:39 yes Jul 13 19:49:45 try running your progrom on python2.5, if there are compatibility issues, go and fix them in the program code Jul 13 19:49:59 program* Jul 13 19:50:35 https://www.python.org/download/releases/2.4.4/ Jul 13 19:50:36 easy to say :D Jul 13 19:51:11 pyobd on n900 runs just fine. what dependencies you don't meet? Jul 13 19:51:53 python 2.4 and pyserial Jul 13 19:51:59 lol, even their website is already rotten and dust: https://www.python.org/download/releases/2.4.4/NEWS.txt 404 Jul 13 19:52:21 n900's pyobd uses python 2.5 Jul 13 19:53:33 looks like a nice educational lesson to make a python2.4 program run on python2.5 Jul 13 19:54:50 https://www.python.org/doc/versions/ Jul 13 19:55:54 https://docs.python.org/release/2.5/whatsnew/whatsnew25.html Jul 13 19:56:19 sicelo, how to show my terminal to see Jul 13 19:56:54 screenshot, or pipe to a text file or pipe directly to a pastebin Jul 13 19:57:08 https://docs.python.org/release/2.5/whatsnew/porting.html Jul 13 19:58:31 echo "this is your program that creates output" | netcat termbin.com 9999 Jul 13 19:59:38 particularly: ssh user@N900 echo "this is your program that creates output" | netcat termbin.com 9999 Jul 13 20:00:51 i have idea Jul 13 20:01:25 will use ssh from notebook to login in my n900 Jul 13 20:05:16 ~repos Jul 13 20:05:16 from memory, repos is "deb http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/apps/ ./ ;; deb http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/mr0/ ./", or see http://wiki.maemo.org/Repository#List_of_Maemo_repositories, or see ~jrrepos Jul 13 20:05:55 kalin: also check your repos against the abovve Jul 13 20:08:59 http://paste.debian.net/976389/ Jul 13 20:20:00 http://maemo.org/packages/view/pyobd/ Jul 13 20:20:21 even in testing :-) Jul 13 20:20:36 err maemo-extras Jul 13 20:21:12 ~jrrepos Jul 13 20:21:12 extra, extra, read all about it, jrrepos is http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/ Jul 13 20:21:17 ~ham Jul 13 20:21:18 ham is, like, Hildon Application Manager. Slow as molasses. Anticipate you got time for a beer or two until it finishes whatever it does, or see ~speedyham Jul 13 20:21:42 /home/user # apt-get install pyobd Jul 13 20:21:42 Reading package lists... Done Jul 13 20:21:42 Building dependency tree Jul 13 20:21:42 Reading state information... Done Jul 13 20:21:46 E: Couldn't find package pyobd Jul 13 20:21:48 /home/user # apt-get install pyobd Jul 13 20:21:50 E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable) Jul 13 20:21:52 E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? Jul 13 20:21:54 /home/user # apt-get install pyobd Jul 13 20:21:56 Reading package lists... Done Jul 13 20:21:58 Building dependency tree Jul 13 20:22:00 Reading state information... Done Jul 13 20:22:02 You might want to run `apt-get -f install' to correct these: Jul 13 20:22:04 The following packages have unmet dependencies: Jul 13 20:22:06 pyobd: Depends: python-serial but it is not going to be installed Jul 13 20:22:08 Depends: python-wxgtk2.6 but it is not going to be installed Jul 13 20:22:10 sociality: Depends: libqjson0 but it is not going to be installed Jul 13 20:22:12 E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). Jul 13 20:22:35 please use pastebin! Jul 13 20:22:45 ok, sorry Jul 13 20:23:58 check in package interface ^^^ where the missing dependencies are from Jul 13 20:24:14 prolly should fix your catalogs Jul 13 20:24:26 or did you forget to apt-get update? Jul 13 20:26:34 actually why did you issze the same command three times? and more weird, why did you get different results on all three runs? Jul 13 20:26:58 when i try apt-get update i gives me keyexpired Jul 13 20:27:08 honestly you probbaly rather should use HAM Jul 13 20:27:22 keyexpired is a warning Jul 13 20:27:25 ignore it Jul 13 20:27:36 +1 re- HAM Jul 13 20:30:04 how to ignore this Jul 13 20:30:38 look into a different direction ;-) Jul 13 20:30:57 :D Jul 13 20:32:31 kalin: first step is to ensure you have corect repos. infobot gave you links Jul 13 20:33:34 i did use microb install link Jul 13 20:33:46 yes, and ideally use ~jrrepos Jul 13 20:34:11 which ones you adfed? Jul 13 20:34:25 then check "catalogs" in HAM, disable obsolete/defective ones Jul 13 20:34:57 sicelo: btw congrats! Jul 13 20:35:52 sicelo, both muarf and linenoise Jul 13 20:36:05 no, please don't install both Jul 13 20:36:19 it doesn't help, only slows down stuff Jul 13 20:36:32 muarf is it Jul 13 20:36:34 thanks DocScrutinizer05 :)) .. now the hard work begins Jul 13 20:38:12 ok, so now i must remove linenoise repo? Jul 13 20:38:55 yes Jul 13 20:38:57 http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/recommended.install Jul 13 20:39:55 or, use http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/muarf_devel_tools.install and disbale the tools and devel repos Jul 13 20:40:16 DocScrutinizer05, only this one or with muarf? Jul 13 20:40:28 both include muarf Jul 13 20:40:34 ok Jul 13 20:40:56 recommended is a symlink to muarf.install Jul 13 20:41:33 also read my comment on bottom of that webpage Jul 13 20:44:38 why the F* I got the muarf installfiles twice, with %20 amd with space? Jul 13 20:46:40 HAM is so slow... Jul 13 20:48:20 bencoh: uri = http://maemo.muarf.org/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/apps/ vs uri = http://mirrors.muarf.org/maemo/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/ssu/apps/ ?? Jul 13 20:49:36 bencoh: I gather I can discard the urglier of both (mirrors.muarf)? Jul 13 20:50:12 bencoh: which one is the recommended correct URL? Jul 13 20:55:06 ~tell kalin about speedyham Jul 13 20:59:07