IRC log of #maemo for Thursday, 2017-06-29

*** dafox has joined #maemo00:07
*** sq-one has quit IRC00:08
*** dafox has quit IRC00:41
*** Kabouik has quit IRC00:55
freemangordonVajb_: sorry, don't get the question, just ask in whatever form it fits you01:02
parazydfreemangordon, Wizzup: will send you an email with info when i get home01:09
parazydjust finished the videoconf01:09
parazydbbl01:10
*** xy2_ has quit IRC01:12
DocScrutinizer05haha https://lists.dyne.org/lurker/message/20170628.215352.678fe0a2.en.html01:17
DocScrutinizer05better than01:17
Vajb_freemangordon: i meant /query you, if it is ok?01:17
DocScrutinizer05~systemd01:17
infobotsystemd cabal: a bunch of people (Lennart Poettering, Kay Sievers, H. Hoyer, D. Mack, T. Gundersen, D. Herrmann) who want to turn linux into their wet dream perverted version of windows-me-too: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html -- Rumor has it that 2016 systemd will have replaced kernel. See ~nosystemd"01:17
L29Ah~nosystemd01:18
infobotrumour has it, nosystemd is https://devuan.org http://without-systemd.org/wiki/index.php/Arguments_against_systemd http://blog.darknedgy.net/technology/2015/10/11/0/01:18
Vajb_has this rumor been full filled?01:19
*** Kabouik has joined #maemo01:19
*** Pali has quit IRC01:36
*** L29Ah has left #maemo01:55
*** joga_ has quit IRC01:58
*** joga_ has joined #maemo01:58
*** joga_ is now known as joga01:58
*** L29Ah has joined #maemo01:58
parazydemail sent01:59
*** guerby has quit IRC02:00
*** Kabouik has quit IRC02:00
*** guerby has joined #maemo02:07
*** florian has quit IRC02:13
*** LauRoman has quit IRC02:33
*** infobot has quit IRC03:19
*** infobot has joined #maemo03:21
*** cyphase has quit IRC03:51
*** cyphase has joined #maemo04:29
*** ravelo_ has joined #maemo04:47
*** err0r3o3 has quit IRC04:50
*** ravelo has quit IRC04:50
*** cyphase has quit IRC04:51
*** err0r3o3 has joined #maemo04:51
*** florian__ has joined #maemo05:08
*** florian_kc has quit IRC05:12
*** drcode has quit IRC05:57
*** drcode has joined #maemo06:08
*** pagurus has quit IRC06:12
*** CcxWrk has quit IRC06:12
*** pagurus has joined #maemo06:13
*** CcxWrk has joined #maemo06:16
*** povbot has joined #maemo06:35
*** Juesto has joined #maemo06:58
Juestohey06:58
Juestoshouldn't be easier to get maemo working on something like Ubuntu which uses upstart?06:59
*** DocScrutinizer05 has quit IRC07:05
*** DocScrutinizer05 has joined #maemo07:05
L29Ahsomething like ubuntu uses fresh glibc that can't run on something like 2.6.28 that runs on n900, and the upstream kernel hardware support is incomplete and for some parts incompatible with maemo's interfaces07:06
*** buZz has quit IRC07:10
*** buZz has joined #maemo07:20
*** buZz has quit IRC07:24
*** err0r3o3 has quit IRC07:24
*** err0r3o3 has joined #maemo07:26
*** Juesto has quit IRC07:27
*** LauRoman has joined #maemo07:28
*** Juesto has joined #maemo07:33
*** buZz has joined #maemo07:43
*** drcode has quit IRC08:02
*** drcode has joined #maemo08:07
*** spiiroin has quit IRC08:14
*** spiiroin has joined #maemo08:17
*** cyteen has quit IRC08:33
*** cyteen has joined #maemo08:35
*** dmth|intevation has joined #maemo08:35
*** cyphase has quit IRC08:46
*** dafox has joined #maemo09:01
*** cyphase has joined #maemo09:09
*** LauRoman|Alt has joined #maemo09:12
*** cyphase has quit IRC09:15
*** LauRoman has quit IRC09:15
*** Pali has joined #maemo09:26
*** dafox has quit IRC09:27
*** cyteen has quit IRC09:39
*** Pali has quit IRC09:40
*** sfa has joined #maemo09:48
*** eMHa has quit IRC10:03
*** buZz has quit IRC10:13
*** drcode has quit IRC10:20
*** buZz has joined #maemo10:21
*** Juesto has quit IRC10:22
*** sfa has quit IRC10:23
*** drcode has joined #maemo10:29
*** eMHa has joined #maemo10:29
*** jskarvad has joined #maemo10:45
*** jskarvad has quit IRC10:45
*** jskarvad has joined #maemo10:45
sixwheeledbeast^maemo has upstart anyway and ubuntu is now on systemd due to having to follow Debian. This I guess has left upstart un-maintained.10:53
*** ravelo__ has joined #maemo10:56
*** ravelo_ has quit IRC10:59
*** dmth|intevation has quit IRC11:21
*** florian__ is now known as florian11:23
*** dmth|intevation has joined #maemo11:29
*** N-Mi has joined #maemo11:32
*** N-Mi has joined #maemo11:32
*** spiiroin has quit IRC11:36
*** cyteen has joined #maemo11:51
*** spiiroin has joined #maemo11:59
*** TheKit has joined #maemo13:06
*** Smily has quit IRC13:06
*** xy2_ has joined #maemo13:08
*** NeKit has quit IRC13:09
*** Wikiwide has joined #maemo13:18
*** Wikiwide has left #maemo13:18
*** Wikiwide has joined #maemo13:19
WikiwideShould I enable CSSU-devel repository if I already have CSSU-thumb enabled?13:20
bencohcssu-devel really is "devel"13:21
bencohit's not meant for regular use13:22
WikiwideOkay. Will not risk it for everyday device, especially due to lack of microUSB port.13:41
*** xy2_ has quit IRC14:17
*** dmth|intevation has quit IRC14:43
*** dmth|intevation has joined #maemo14:45
*** HRH_H_Cr1b is now known as HRH_H_Crab15:24
*** geaaru has joined #maemo15:25
*** oniongarlic has quit IRC15:25
*** qwazix has quit IRC15:26
DocScrutinizer05cssu-devel *IS* broken - by definition15:27
DocScrutinizer05what you want is cssu-testing which is supposed to have all working packages15:29
DocScrutinizer05and afaik cssu-thumb alrady is an overlay to cssu-t, which in turn is an overlay to maemo core repos15:31
DocScrutinizer05so to make this utterly clear: when you ask apt to install a package, then (if you git thumb config) it shall first look into cssu-thumb, then if not found there it looks into cssu-testing, then finally it shall try to get from maemo core repos and possibly maemo-tools and other auciliary repos15:34
DocScrutinizer05s/git/got/15:34
infobotDocScrutinizer05 meant: so to make this utterly clear: when you ask apt to install a package, then (if you got thumb config) it shall first look into cssu-thumb, then if not found there it looks into cssu-testing, then finally it shall try to get from maemo core repos and possib...15:34
*** qwazix has joined #maemo15:35
DocScrutinizer05it's all about priorities of repos15:37
DocScrutinizer05cssu-thumb is replacing *some* packages found in lower prio repos (I.E. cssu-t and genuine Nokia/maemo-extras repos) by a specially compiked version (some compiler flags basically) that results in smaller binary that only runs on systems with powerkernel_thumbpatched15:41
DocScrutinizer05you don't want any other higer prio repo than cssu-thunb in your config15:41
DocScrutinizer05smae basically applies to CSSU at large, just CSSU has packages with bugfixes replacing packages from lower prio repos15:43
*** xy2_ has joined #maemo15:43
DocScrutinizer05maemo-extras is NOT supposed to repkace any packages from nokia core repos aka system15:44
DocScrutinizer05so maemo-extras is strictly supplementary15:44
DocScrutinizer05gosh my typing sucks, sorry15:45
*** err0r3o3_ has joined #maemo15:45
*** err0r3o3 has quit IRC15:48
*** oniongarlic has joined #maemo15:49
*** chem|st has quit IRC16:14
*** chem|st has joined #maemo16:14
*** xy2_ has quit IRC16:25
*** spiiroin has quit IRC16:25
*** xy2_ has joined #maemo16:30
*** spiiroin has joined #maemo16:41
*** auenf has quit IRC17:14
*** chainsawbike has quit IRC17:19
*** dmth|intevation has quit IRC17:23
*** eMHa has quit IRC17:28
*** auenf has joined #maemo17:41
*** chainsawbike has joined #maemo17:42
*** louis_ has joined #maemo17:43
*** Smily has joined #maemo17:55
*** Pali has joined #maemo18:10
*** florian has quit IRC18:16
freemangordonparazyd: do I get it right that maemo-devuan packages has to be in a repo hosted on maemo servers?18:27
*** eMHa has joined #maemo18:30
DocScrutinizer05good question, I don't think the usual amprolla operation works nice with the classical maemo repo structure18:31
DocScrutinizer05iirc the idea was to have a true full repo for maemo-devuan18:31
DocScrutinizer05on devuan18:31
DocScrutinizer05so you'd need to port *all* packages18:32
freemangordonDocScrutinizer05: yes, but if this is not accepted by devuan guys we will have to host it on maemo servers18:32
freemangordonno, why all packages?18:32
freemangordonit will be a separate repo (if it comes to it)18:33
DocScrutinizer05well, all you want to use, at least. Since you can't 'mirror' to e.g. maemo-extras18:33
DocScrutinizer05and I'd not see how such a devuan specific repo should get hosted on maemo18:33
freemangordonah. but that was clear from the beginning18:33
DocScrutinizer05needlessly complicated, and no rationale for that18:34
freemangordonlets wait for parazyd to elaborate18:34
*** louis_ has quit IRC18:34
Wizzupfreemangordon: I think that was unclear still18:34
DocScrutinizer05jaromil told me he'd love to host the complete maemo-devuan, no need to spread it over several domains18:34
freemangordonWizzup: at least not clear to me what was decided :)18:35
DocScrutinizer05and "using the complete devuan CI" makes sense only when the repo and don't know-what_autobuilder(?) lives on one server, no?18:36
Wizzupfwiw. 'complete maemo-devuan' = whatever extra pkgs we want to add on std devuan (e.g. h-d related packages). definitely not init systems or lots of other things they already have18:37
freemangordonno, why, it might work the same way as maemo infra I guess, spread over several servers18:37
*** louis_ has joined #maemo18:37
DocScrutinizer05maybe several servers but for sure not several domains18:38
freemangordonanway, lets wait for parazyd as we're doing wild guesses now18:38
Wizzupso what we want works just fine with amprolla318:39
DocScrutinizer05Wizzup: yeah, that's what I wonder how much of maemo will be in maemo-devuan in the end. Prolly not much18:40
parazydhey18:40
parazydpatience18:40
parazydlet me type it out18:40
Wizzupwhatever is worth savind can be ported over time ;)18:40
freemangordonDocScrutinizer05: this is snother story18:40
parazydjenkins needs a place to push the packages. dan doesn't want to host it on the devuan infra18:40
DocScrutinizer05I'm personally not interested nuch in a rebase-port18:40
freemangordon*another18:40
parazydbut we can host it on some dyne infra if necessary18:41
freemangordonparazyd: ah, I see18:41
parazydbut i need someone who knows how to setup dak18:41
parazydor whatever repo manager18:41
parazydthen you use amprolla to merge packages you build with devuan's18:41
parazydand you only host the maemo packages built by jenkins18:41
freemangordonparazyd: ok, it is clearer now18:41
parazydand in fact you won't need that much space18:42
parazydi'm guessing armhf/arm64/i386/amd64 is enough18:42
parazydi'm pretty sure i can host this on a machine in our lab in an lxc18:42
freemangordonso, from the end-user perspective, one have to add maemo-devuan repos, hosted on maemo servers in order to be able to install ported hildon-desktop, right?18:43
Wizzupyes18:43
parazydyes, let's call it amprolla.maemo.org18:43
parazydand that's the repository hosting the merged Packages files, and only maemo debs18:43
DocScrutinizer05I don't think a "hmm, devuan is working now on N900, but I'd love to throw in hildon desktop instead of LXDE" has high attractivity, neither is it sustainable in the end from a perspective of manpower needed18:43
parazydother debs are retrieved by nginx rewrites from devuan/debian18:43
freemangordonparazyd: what about armel target?18:44
parazydsure18:44
parazydanything18:44
parazydi'm actually getting a few boards soon that were donated for the devuan build infra18:44
parazydso have to set them up as build slaves18:44
parazydi'll be on and off until tuesday since i'm holding a workshop in france, but i'll try to manage and setup an lxc for you for this stuff18:45
Wizzupparazyd: so we can't just have the maemo-devuan pkgs in a repo without amprolla magic?18:45
parazydand then i guess try to find someone who knows how to setup dak. i'll ask for more info how it has to be setup18:45
freemangordonDocScrutinizer05: it is NOT about n900, but about rebasing maemo and running it on whatever device that can boot linux and has 3d drivers18:45
parazydWizzup: no, you cannot18:45
Wizzupif we just add it in addition to normal devuan pkg repos18:45
DocScrutinizer05I'd prefer the approach to throw in devuan's kernel and core system into a full size maemo18:46
parazydWizzup: you merge the maemo packages with devuan using amprolla18:46
freemangordonthis is the goal, but it will take time18:46
freemangordonDocScrutinizer05: ^^^18:46
DocScrutinizer05your means determine the goal you can reach18:46
* freemangordon is going to have something to eat, bbl18:47
DocScrutinizer05when you start out with a plain devuan it will never be a full maemo any time18:47
parazydwhich is why the packages are being ported18:47
*** Kabouik has joined #maemo18:47
DocScrutinizer05when you start with a full working maemo you can throw in devuan parts on a when-needed basis18:47
bencoh...18:48
parazydi don't think that's sustainable imho18:48
parazydand doesn't work the way you think it works18:48
bencohDocScrutinizer05: *no* you can't and we've been through this a dozen time18:48
DocScrutinizer05yes, we've been through this a dizen times and I not once heard a compelling argument how the "start with plain devuan" approach would eventually result in a full featured maemo18:49
DocScrutinizer05at least not maemo6, maybe maemo818:50
DocScrutinizer05s/maemo6/maemo5/18:50
infobotDocScrutinizer05 meant: at least not maemo5, maybe maemo818:50
WizzupDocScrutinizer05: unless you're going to do the work, why go over it again?18:51
DocScrutinizer05hm?18:53
*** louis_ has quit IRC18:59
DocScrutinizer05there's nothing unusual with "backports", you got that in every distro. However maemo-devuan looks like a forward port of _some_ parts of maemo to devuan, not like a backport of some devuan stuff to maemo, when needed or desirable19:00
Wizzupcorrect, the aim is to produce something that is not loaded with ancient crypto libs and other baggage19:01
DocScrutinizer05the difference being: forward port of maemo could as well happen to any arbitrary other distro19:02
Wizzupyou can try to implement your way and see how it goes19:02
parazydDocScrutinizer05: jaromil says he never offered such a thing (hosting maemo-devuan)19:03
DocScrutinizer05thanks, captain obvious. I heard that bullshit every single time when people are too polite to simply state "I know better, so shut up and take or leave the stuff I do"19:03
DocScrutinizer05then I got that wrong19:03
*** louis_ has joined #maemo19:03
parazydhe says we can't  ensure reliability for anyone19:04
DocScrutinizer05maybe because of that difference in approach19:04
parazydthe CI is ok to use, but can't depend on the infra to do backups/bandwith19:04
parazydmaybe you confused it with the usage of CI/jenkins?19:05
DocScrutinizer05I thought we'd host backports on maemo-devuan, you want (or don't want) to host a complete new unrelated distro there19:05
Wizzupparazyd: it's nbd to host it19:05
parazydok19:05
freemangordonparazyd: I guess maemo admin won;t refuse to host one more repo with a couple of hundred packages19:06
freemangordonmerlin1991: propozed setting up reprepo, is it ok?19:06
DocScrutinizer05in my book maemo-devuan was an overlay of xsorts, just like CSSU19:06
parazydfreemangordon: from my understanding any repo manager is okay19:06
Wizzupoverlay on top of devuan19:07
freemangordonI mean "merlin proposed..."19:07
parazydyeah i understood19:07
freemangordonwhich is what maemo is after all - an overlay on top of debian19:07
DocScrutinizer05nah, technically there's no problem to hostz that stuff on maemo infra19:07
freemangordonDocScrutinizer05: yes, but it will need maintance as well I guess :)19:07
parazydas a matter of fact it could be even better since you already have the repository setup, no?19:07
parazydmight require tweaks only19:08
parazydanyway, as said, i'm going to find out more about the needs for this19:08
merlin1991nah "that repository" is something you don't want to add to19:08
freemangordonmhm :D19:08
DocScrutinizer05yres, and I don't think anybody is going to implement devuan's infra on maemo19:08
parazydmerlin1991: separate repository, same server/manager isn't possible?19:08
merlin1991it's powered by apt-ftparchive a bazillion folders and shellscripts...19:08
merlin1991sure19:08
parazydoh19:08
parazydsimply put, jenkins needs a place to push the .debs. then the repo manager would grab them, generate a repo out of them and amprolla would merge that one with devuan19:09
merlin1991that's easy todo19:10
freemangordonI guess it will not be a problem19:10
merlin1991my tool of choice would be reprepro since I know it19:10
parazyd:)19:10
freemangordonparazyd: where is that amprolla going to work? on maemo servers?19:10
parazydCenturion_Dan mentioned reprepo is okay iirc19:10
parazydfreemangordon: i suppose so19:10
freemangordonok19:10
WizzupI think it's seperable somewhat19:11
parazydit can run remotely, but then you would have to rsync the data between servers19:11
DocScrutinizer05anyway I have to say that at least FPTF approach as discussed by several and agreed upon as feasible is _not_ related in _any_ way to what became of maremo-devuan now19:11
parazydactually19:11
parazydamprolla can run anywhere19:11
parazydi forgot it's nginx that does the rewrites19:11
*** ced117_ has quit IRC19:11
parazydrewrites = pointers to .debs19:11
freemangordonwell, I guess it is better to run on a server, not on a laptop or mobile :)19:12
*** ced117 has joined #maemo19:12
*** ced117 has quit IRC19:12
*** ced117 has joined #maemo19:12
parazydyes ofcource19:12
Wizzuplets get the reprepro workflow going19:12
parazydright19:12
Wizzupworry about amprolla later19:12
parazydi'll ask if there are any specific needs for reprepo+jenkins19:12
freemangordonlets wait for xes and warfare to have their saying19:12
parazydCenturion_Dan is in a +12 timezone19:12
merlin1991if anything reprepro might start complaining about the incoming packages :D19:12
freemangordonalso, I guess we'll need some kind of approval from the council19:13
merlin1991it's quite picky about everthing being in order19:13
DocScrutinizer05FPTF idea was to let maemo evolve bottom-up slowly and organically into what you hope to reach top-down in one huge effort now with maemo-devuan19:13
freemangordonDocScrutinizer05: on what device you're going to run that FPTF-maemo in two years?19:13
*** louis_ has quit IRC19:15
freemangordonDocScrutinizer05: my point - there is a lack of any linux based mobile distro (besides sailfish but it is disputable what kind of linux-based it is)19:15
parazydthe neo90019:15
DocScrutinizer05obviously on those that were targeted by the project, which was from genuine N900 as test platform to Neo900 to e.g beagleboard to padorabox to pyra and maybe eventually even to platforms that don't have OMAP CPU. In two years? no idea since obviosuly everybody thinks you could reach the endpoint of FPTF (run on non-OMAP) in less than 2 years19:16
* parazyd ducks19:16
Wizzupwhat's the point in carrying all that old sw? if it's not maintained and ported to new libs, it'll just rot forever19:16
Wizzupthe point was to take useful parts and have them, not everything per se19:17
DocScrutinizer05and you decide what's useful in maemo? OK19:17
DocScrutinizer05but don't call it maemo then19:17
freemangordonDocScrutinizer05: usefull is everything that is humanly possible to be ported19:17
Wizzupwhy take devuan and then run maemo browser in its current shape on it?19:18
DocScrutinizer05because a friggin lot of other maemo subsystems need that very browser?19:18
Wizzuplike?19:19
freemangordonconversations and what else?19:19
DocScrutinizer05messaging19:19
DocScrutinizer05call history19:19
DocScrutinizer05maps iirc19:19
freemangordonDocScrutinizer05: wrong, it is not using THAT browser, but whatever eal there is19:19
DocScrutinizer05so what?19:19
DocScrutinizer05eal IS 'that browser'19:20
freemangordonno, it is an interface to whatever browser you may want19:20
DocScrutinizer05nitpicking19:20
Wizzuplol19:20
DocScrutinizer05and libcmt is an interface to whatever modem you want19:20
freemangordonafaik no19:21
DocScrutinizer05the question was >>why [...] run maemo browser [...] on it?" and the answer is: you want a browser that supports eal. Zhere's one that already does and of course "you are free to do the work to implement a better one"19:24
*** louis_ has joined #maemo19:24
freemangordonDocScrutinizer05: continuing to use packages from 2009 is not a sane thing in my book19:25
freemangordonand once you try to use newer, it pulls a huge pile of dependencies19:25
DocScrutinizer05I think the answer to that is already in my last few posts19:25
freemangordonand you have to port them as well19:25
freemangordonand you're still outdated as while you were porting, a couple of CVE fixes appear and you have to again backport19:26
xesWTF ...no... i think today i can't read all this backlog ..19:26
freemangordonxes: no, check on ##maemo-admin19:26
xesfreemangordon: ok19:27
freemangordonDocScrutinizer05: the only sane way I know is to bandwagon some modern distro, devuan was chosen because of systemd19:29
freemangordonand because it is debian derivative, the same what maemo is19:30
freemangordonDocScrutinizer05: in terms of FPTF - I am REing closed packages on as-needed basis - if FOSS package has a dependency on closed one, I RE it and it is included. NOTHING is stripped from the system so far19:31
DocScrutinizer05the thing you want to do (port some few 'useful' things to another distro) it doesn't matter basically if there's systemd or if it's debian based. For such a project I had cosen sailfish as new upstream distro19:32
freemangordonDocScrutinizer05: wrong, I don't want to port "few useful" things, but the whole maemo, removing stuff like gnomevfs for example19:33
DocScrutinizer05didn't know maemo had gnomevfs19:33
freemangordonall over the place19:34
freemangordonDocScrutinizer05: where you have a couple of free minutes, look at https://github.com/fremantle-gtk2 to see the number of packages ported so far. And this is just the beginning, however I have hildon-desktop, hildon-status-menu and hildon-home FULLY FUNCTIONAL (sort of) in 64bit devuan19:36
DocScrutinizer05nice, but not relevant for me right now19:37
freemangordonIOW - we have hildon stack ported to recent debian and more or less working19:37
freemangordonthat's another story19:37
bencoh<3 for all the work done so far, by the way19:37
DocScrutinizer05I'm worried about thermal management, power management, audio, connection handling, notifications etc pp19:38
freemangordonI am worried as well, but first was hildon stack, without that running, nothing is possible19:39
DocScrutinizer05hmm except notifications all I listed is unrelated to hildon19:39
freemangordonthis stuff will get ported when it comes to it. And it won;t be stripped, you have my word on that19:39
freemangordonit is, as most of it works as hildon-status-menu plugins ;)19:40
freemangordonconnection-handling: https://github.com/fremantle-gtk2/iphbd19:40
DocScrutinizer05you're talking GUI, I'm talking middleware and drivers19:41
freemangordoniphbd is not gui19:41
freemangordonclockd is not gui19:42
freemangordonneither is alarmd19:42
DocScrutinizer05and I seriously doubt you can come up with a middleware fitting under an existing GUI layer, once the latter is implemented19:42
freemangordonI am not going to come-up with a middleware, but will reuse the one in fremantle19:42
freemangordonwell, some parts will have to be ported, for example to upoer the same way I ported to gio from gnomevfs19:43
freemangordon*upower19:43
freemangordonfor network management I am still to decide, and I am not even sure I am the one that has to take that decision19:44
DocScrutinizer05how is your GUI stuff working then when the middleware is not there. e.g. how would a mediaplayer do audio when there's no mafw it's supposed to use under true maemo? (maybe I should try harder to come up with better example but maybe you get my point nevertheless)19:44
freemangordonDocScrutinizer05: I got your point, thus https://github.com/community-ssu/libplayback, for example19:44
DocScrutinizer05ooh nice19:45
freemangordonstuff gets REed and ported when it comes to it19:45
freemangordonor https://github.com/community-ssu/osso-bookmark-engine19:45
freemangordonetc19:45
DocScrutinizer05ok, I think I get your point too, probably your approach is evidently more feasible than I thought19:46
freemangordonI am going to try to reuse as much as possible from stock maemo. If it is possible(and sane), it will be reused, if not - it will be replaced with upstream equivalents19:46
freemangordonfinally :)19:47
bencoh\o/ :)19:47
bencoh(I think this should be marked as a project milestone ;p)19:47
Wizzup:D19:47
*** louis_ has quit IRC19:48
freemangordonDocScrutinizer05: actually I am trying to achieve FPTF goal, but from the opposite direction, without making maemo fall apart on every package I try to replace with upstream one19:51
DocScrutinizer05yes, what I said, top-down vs bottom-up approach. I didn't realize how close you already are19:56
DocScrutinizer05bottom-up has the immanent advantage to yield results in intermediate states, while top-down has to get pretty close to the final goal before you get useful results19:57
DocScrutinizer05downside of my bottom-up: it's usually much slower19:58
freemangordonwell, not that close, lots of work to be done still. thus we want to setup a repo with what is done so far, make some PR noise in a hope more devs to join as this is not as task for one or two devs19:58
freemangordon*a task19:58
freemangordonthat way I will be able to focus on REing while the others will do the porting of FOSS stuff19:59
freemangordonsounds like a plan, right? :)19:59
DocScrutinizer05I'd like to help with that making-noise, on neo900.org20:00
DocScrutinizer05yes, absilutely, sounds like a decent plan20:00
freemangordonbut first, we need repo running20:00
DocScrutinizer05ack20:00
DocScrutinizer05that been the reason why I offered to run a FPTF repo on neo900 before devuan even existed20:00
*** Wikiwide has left #maemo20:01
sunshavi~fptf20:01
infobothmm... fptf is the Fremantle Porting Task Force, see http://talk.maemo.org/showthread.php?t=9130820:01
sunshavi~reing20:01
freemangordonhaving devuan guys helping us is great thing IMO20:01
DocScrutinizer05:-D20:02
DocScrutinizer05thought the same, that's why I pestered them over at #devuan20:02
DocScrutinizer05and pestered you to join there20:02
freemangordonmhm, many thanks for that one20:02
* DocScrutinizer05 recalls the shitsortm when neo900 newsletter mentioned that devuan is joining forces with maemo now, and sighs20:04
DocScrutinizer05"what, you don't support debian anymore??? I'm not interested anymore in neo900!!"20:05
DocScrutinizer05o.O20:06
*** Smily has quit IRC20:07
*** louis_ has joined #maemo20:10
*** notverynice has joined #maemo20:20
*** xy2_ has quit IRC20:35
*** xy2_ has joined #maemo20:37
*** louis_ has quit IRC21:25
*** florian has joined #maemo21:28
*** xy2_ has quit IRC21:34
*** err0r3o3_ is now known as err0r3o321:35
*** xy2_ has joined #maemo21:47
*** louis_ has joined #maemo21:49
*** louis_ has quit IRC21:54
*** notverynice has quit IRC21:54
*** jskarvad has quit IRC21:56
*** geaaru has quit IRC22:01
*** xy2_ has quit IRC22:02
*** xy2_ has joined #maemo22:05
*** xy2_ has quit IRC22:11
*** xy2_ has joined #maemo22:13
*** dafox has joined #maemo22:46
*** Juesto has joined #maemo23:06
*** florian has quit IRC23:17
*** xorly has joined #maemo23:26
*** dafox has quit IRC23:32
*** dafox has joined #maemo23:53

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!