_inky has quit [Read error: Connection reset by peer]
_inky has joined #maemo-leste
_inky has quit [Read error: Connection reset by peer]
_inky has joined #maemo-leste
cockroach has joined #maemo-leste
_inky has quit [Read error: Connection reset by peer]
doc|home has quit [Remote host closed the connection]
doc has joined #maemo-leste
Pali has quit [Ping timeout: 268 seconds]
cockroach has quit [Quit: leaving]
Wikiwide has quit [Ping timeout: 256 seconds]
xmn has quit [Ping timeout: 240 seconds]
xmn has joined #maemo-leste
joerg is now known as Guest8769
joerg has joined #maemo-leste
Guest8769 has quit [Ping timeout: 240 seconds]
macros__ has joined #maemo-leste
macros_ has quit [Ping timeout: 252 seconds]
<freemangordon> Wizzup: again, we shall find what is really broke, I doubt this is the only problematinc package
<freemangordon> weird, in VM apt log I see no triggers for shared-mime-info
<freemangordon> Wizzup: is it possible to create some quick-n-dirty image in the builder that installs hildon-update-category database only
<freemangordon> hmm
<freemangordon> maybe my trigger is wrong
xmn has quit [Quit: ZZZzzz…]
<freemangordon> ugh
<freemangordon> what happens is that update-mime-database is called for empty /usr/share/mime/packages directory it seems
<freemangordon> lemme test something
_inky has joined #maemo-leste
<freemangordon> Wizzup: what I guess happens is that shared-mime-info triggers are triggered before packages is being fully configured
<freemangordon> no idea why that happens, but this is what I suspect
<freemangordon> parazyd: any idea? ^^^
inky has quit [Read error: Connection reset by peer]
_inky has quit [Read error: Connection reset by peer]
<freemangordon> Wizzup: please respin image build when you are around
<parazyd> freemangordon: I don't know how the triggers work nor what the ones you linked are supposed to do.
<freemangordon> parazyd: yeah, ok, docs a bit vague
<freemangordon> I suspect that shared-mime-info postinst is being called before backage is being fully expanded (or whatever the term)
<freemangordon> *package
<freemangordon> that seems to happen in the builder only
<parazyd> aha
<freemangordon> maybe apt is called with some special parameters?
<parazyd> There's a possibility that the chroot divert is blocking this from happening.
<freemangordon> blocking?
<parazyd> But no though
<parazyd> This is just invoke-rc.d
<freemangordon> mhm
<freemangordon> it is rather a bug in dpkg, invoking postinst for triggers before package is expanded
<freemangordon> that's what I suspect
<parazyd> apt is also always called with DEBIAN_FRONTEND=noninteractive
<parazyd> I can't think of anything else
<freemangordon> maybe we can workaround that by having shared-mime-info being installed in an earlier stage
<freemangordon> is that possible?
<freemangordon> though I now changed hildon-update-category-database to have pre-depends on shared-mime-info
<freemangordon> hoping that shared-mime-info will be configured by the time hildon-update-category-database install starts
<freemangordon> parazyd: BTW, do I have login on jenkins?
<freemangordon> in the UI that is
<parazyd> I believe so. Let me check. Should I make you one if you don't?
<freemangordon> don;t know, what I can do from there?
<freemangordon> can I run image builds?
<parazyd> Yes
ungeskriptet[m] has left #maemo-leste [#maemo-leste]
<parazyd> I'm not sure of the implications
<freemangordon> there shouldn't be any, iiuc
<freemangordon> lets first try with my latest changes, if that doesn;t help we can try and move
<parazyd> ok
<freemangordon> ok, so please either create account for me or start leste-image-droid3-dev image build
<mighty17[m]> freemangordon: does glmark2-es2-*/glxgears run for you in the pvr mesa?
<freemangordon> never tried glxmark, but glmark2-es2 runs just fine
<freemangordon> both drm and x11 ones
<freemangordon> not sure if I tried WL one
<freemangordon> there is no point trying glxmark IMO, it will run through llvmpipe if it runs at all
<parazyd> ok, I triggered it
<parazyd> You don't have an account btw.
<parazyd> pm'd
<freemangordon> ok, if this build is still broken, I'll ping you to make the change in the image builder scripts
<freemangordon> thanks!
<freemangordon> a side note - I think we shall enable openrc parallel boot
<parazyd> mhm I think that's safe now.
<freemangordon> mhm
<freemangordon> who shall do that?
<parazyd> It's easy enough to use sed from image-builder, but I'm not sure if Wizzup wants to handle this from a package.
<freemangordon> lets wait for him then
<freemangordon> hmm, what is wrong with the word "master" so jenkins is moving away from it?!?
<parazyd> Yeah...
<freemangordon> no, I really don;t understand. I mean white/black lists, good, someone may feel offended (though, maybe we shall remove the colors themselves then :) ), but "master"?
<freemangordon> unless it has some meaning unknown to me
<freemangordon> maybe some native speaker can explain
<freemangordon> I mean - do we still have slavery so a slave can feel offended?
<freemangordon> parazyd: it seems shared-mime-info is already installed in stage 2(iiuc) it seems it is pulled as a dependency
<freemangordon> no, it is "thirdstage"
<freemangordon> hmm, is that normal: "scandir: Value too large for defined data type"
inky_ has joined #maemo-leste
_inky has joined #maemo-leste
<parazyd> 11:01 <freemangordon> hmm, is that normal: "scandir: Value too large for defined data type"
<parazyd> Where does this appear?
<parazyd> Regarding shared-mime-info, I think it's not part of the usual debootstrap
<parazyd> What I could do, is add an array that we can fill with package names and have them installed during the initial debootstrap.
<parazyd> That could help with a few specific ones
<freemangordon> maybe some openrc warning
<parazyd> hmm I haven't seen that before
<freemangordon> hmm, don;t see that in the VM image build
_inky has quit [Ping timeout: 268 seconds]
wunderwungiel[m] has joined #maemo-leste
<wunderwungiel[m]> Hej
<wunderwungiel[m]> Hello
<freemangordon> parazyd: still broken :(
<wunderwungiel[m]> Is Matrix or IRC chat more active?
<wunderwungiel[m]> ?
<Wizzup> we don't have matrix
<Wizzup> if it exists, it's bridged to irc
<freemangordon> Wizzup: no matter what I do, droid3 images are broken re mime
<freemangordon> it looks like there is no /usr/share/mime/packages/freedesktop.org.xml during image build
<freemangordon> or, /usr is bindmounted somewhere else
<freemangordon> like, if you move /usr/share/mime/packages/freedesktop.org.xml somewhere else and execute update-mime-database, you will get exactly the same /usr/share/mime/ content as on the build image
<freemangordon> I don;t see how libhildonmime can possibly break this
<Wizzup> this is not really my terrain
<Wizzup> it sounds like arm-sdk is perhaps just broken then
<freemangordon> hmm, what about this: Err:1 https://maedevu.maemo.org/leste beowulf InRelease
<freemangordon> at the end of the image build
<freemangordon> Temporary failure resolving 'maedevu.maemo.org'
<freemangordon> could it be dns change breaking that?
<Wizzup> yes, but it cannot cause this
<Wizzup> it is part of this:
<Wizzup> apt-get update
<Wizzup> updatedb
<Wizzup> apt-get clean
<Wizzup> update-ca-certificates
<Wizzup> updatedb is just locate related
<Wizzup> ca certs clearly aren't causing the mime problems
<freemangordon> sure
<Wizzup> and it's the last step
<freemangordon> we have one more error though
<Wizzup> I was just inclined to blame libhildonmime because to my knowledge we were seeing ok images before
<freemangordon> "scandir: Value too large for defined data type"
<Wizzup> let me see
<Wizzup> hm
inky_ has quit [Ping timeout: 240 seconds]
<Wizzup> seems to be openrc/sysvinit related
<freemangordon> mhm
<Wizzup> I think those should be unrelated, but we can go back to images that did work and look at the log
<freemangordon> Wizzup: how hard is to create a simple image that installs hildon-update-category-database (and deps) only?
<Wizzup> I don't know, parazyd would know
<freemangordon> as now it takes 2 hours to test changes
inky_ has joined #maemo-leste
<freemangordon> Wizzup: so, only -dev images are broken, rifght?
<Wizzup> no
<freemangordon> *rigth
<Wizzup> everything is broken
<Wizzup> except for apparently your vm image
<freemangordon> VM is not
<Wizzup> n900 is also broken
<freemangordon> no, VM image is not
<freemangordon> also, the new hildon-update-category-database is only in -devel
<freemangordon> so it cannot affect stable images
<Wizzup> last non-devel change is 2021-09-30 it seems
<freemangordon> int the vm image it is the old version
<freemangordon> 3.x
<Wizzup> 3.1.0?
<freemangordon> mhm
<Wizzup> I mean I can verify and boot the n900 image but someone already did that and reported purple and black
<Wizzup> so I am not sure if that makes sense
<freemangordon> no
<Wizzup> and we don't have -devel n900 images
<freemangordon> but, does it install from beowulf-devel?
<Wizzup> no
<Wizzup> of course not
<Wizzup> only -devel images fetch from beowulf-devel
inky_ has quit [Read error: Connection reset by peer]
<freemangordon> unless I miss something, 4.x of libhildonmime is in -devel only
<Wizzup> yes
<Wizzup> so something else perhaps broke it
<freemangordon> no way then this to break shared-mime-info
<Wizzup> we'd have to go back in time to see which is the last good image
<freemangordon> yeah
<freemangordon> VM one is still good :)
<Wizzup> but I'm at a loss here and it's been years since I managed to even run arm-sdk locally
<Wizzup> so I'm hoping parazyd can fix this
<freemangordon> and it doesn;t have "scandir: Value too large for defined data type" error
<Wizzup> not super related
<freemangordon> n900 image log: Setting up hildon-update-category-database (3.1.0+2m7.1) ...
<Wizzup> could be the backing filesystem or something
<Wizzup> freemangordon: right no surprise there
<Wizzup> parazyd: are you available to look at this? we want to give an image to a lima dev who said he's wanting to boot it on a pinephone and try to fix our problem or give hints
<parazyd> Not today, sorry
<Wizzup> :(
<freemangordon> well, I can try and run armsdk here, but, which repo to clone?
<freemangordon> or it hasn;t moved recently?
<parazyd> git clone https://github.com/maemo-leste/image-builder --recursive
<parazyd> Run it in a VM where an account has nopasswd sudo
<freemangordon> leste VM?
<parazyd> Just Devuan or something
<freemangordon> leste is devuan, no :)
<parazyd> Sure :D
<freemangordon> Wizzup: maybe initial bootstrap is > 2GB
<Wizzup> sure, but what modern fs would not support that
<freemangordon> some 32 bit one?
<freemangordon> :)
<freemangordon> and that would explain why 64bit VM doesn;t have the issue
<freemangordon> lemme see what is the situation on PP
<Wizzup> no scandir error
<freemangordon> uncompressing
<Wizzup> ok
<freemangordon> mhm
<freemangordon> /usr/share/mime is fine
<freemangordon> Unpacking hildon-update-category-database (4.0.0+2m7)
<freemangordon> so, it is something on 32bits
<freemangordon> not related to libhildonmime
<freemangordon> I am going to revert changes in it and force-push
<freemangordon> ok?
<freemangordon> Wizzup: ^^^
<mighty17[m]> `ls /sys/bus/mmc/drivers/mmcblk
<mighty17[m]> bind mmc0:1117 mmc1:0001 uevent unbind`
<mighty17[m]> any idea why mmc4:001 is not in here?
<mighty17[m]> `samsung-espresso3g:/sys/bus/platform/drivers/omap_hsmmc# ls
<mighty17[m]> 4809c000.mmc 480b4000.mmc 480d5000.mmc bind uevent unbind` we have it here
<mighty17[m]> `480d5000.mmc` but no mention of it in dmesg or anywhere
<Wizzup> freemangordon: revert what
<mighty17[m]> only happens on a cold boot, any clues?
<Wizzup> freemangordon: ok, maybe something else is up then, I can try to think about that for a moment
<freemangordon> revert changes I made in libhildonmime
<freemangordon> Wizzup: iiuc, it is some cpio archive, maybe it cannot be more than 2GiB on 32 b its
<freemangordon> Wizzup: so, are you ok with me reverting libhildonmime changes and overwriting the history?
<Wizzup> freemangordon: sure I guess, but I wonder if triggers should really return non-0, but idk
<freemangordon> ok, I'll leave it as it is then
<freemangordon> I'll just pull those changes in master
<Wizzup> parazyd: where is this sysvinit -> openrc transition in the arm-sdk
<Wizzup> parazyd: maybe this is part of the openrc package?
<Wizzup> freemangordon: I don't think cpio is used at this stage, but it's hard to confirm
<Wizzup> anything I grep for I can't find it
<Wizzup> it loads something called zuper or something
<freemangordon> mhm
<Wizzup> seems to be random zsh stuff
<Wizzup> I can't find the entry point lol
<Wizzup> build_image_dist doesn't even occur anywhere
<Wizzup> maybe more gets fetched on demand?
<freemangordon> install dependencies atm, need some time :)
<Wizzup> just grepping for cpio also shows just an env var
<Wizzup> magic
<Wizzup> same for fsck and anything else basically
<Wizzup> mkfs just doesn't occur
<Wizzup> parazyd: where is this missing code?
pere has quit [Ping timeout: 260 seconds]
<Wizzup> lol ok I'll wait for you fmg
<Wizzup> I can't even figure out what kind of fs is being used
<Wizzup> bind mount or otherwise
<freemangordon> iirc it was loop
<Wizzup> in any case I am pretty sure the cpio stuff is not being used and we can disable it as well
<Wizzup> idk it's nowhere to be found
<Wizzup> I think all the magic is in some libdevuansdk
<Wizzup> but it's not checked out
<Wizzup> yeah there it is
<freemangordon> zsh: command not found: build_image_dist
<freemangordon> :(
<Wizzup> the usage of this is a bit awkward
<Wizzup> did you load the sdk stuff
<Wizzup> check the readme
<Wizzup> you need to source sdk and stuff
<freemangordon> yes
<freemangordon> I did
<Wizzup> maybe try build_ + tab tab
<freemangordon> ah :_
<freemangordon> :)
pere has joined #maemo-leste
Pali has joined #maemo-leste
inky_ has joined #maemo-leste
<Wizzup> do we not allow root login on our new images?
<Wizzup> toor doesn't work over ssh
<Wizzup> clearly everything must stand in our way of debugging atm :)
<Wizzup> even changing password doesn't work
<Wizzup> does anyone recall wth we have to do to get access? :D
<freemangordon> user:user
<freemangordon> I found it the hard way :)
<Wizzup> :(
<Wizzup> ok, at least new mesa is on the pinephone image
<freemangordon> ugh, build-dep results in 509 MB
<Wizzup> for?
<freemangordon> shared-mime-info
<Wizzup> mhm
<freemangordon> hmm, I should have disabled manual pages
<freemangordon> the one I built fails to generate mime cache too
<Wizzup> what does strace say?
<freemangordon> I cannot strace in chroot
<Wizzup> I think you can disable that via sysctl
<freemangordon> I will rather put printfs()
<Wizzup> k
inky_ has quit [Ping timeout: 240 seconds]
<freemangordon> Wizzup: well, if you provide what to set via sysctl, I am finr
wunderw has joined #maemo-leste
<Wizzup> freemangordon: try sysctl -w kernel.yama.ptrace_scope=0
<wunderw> Hello :)
<wunderw> I'm writing from N900
* mighty17[m] tries to figure out why sdio doesnt get loaded on cold boot and gets when booted from twrp :(((
<Wizzup> wunderw: confirmed the issue you saw on the new image is a broader problem we're fixing now
<wunderw> Good :)
<wunderw> Installed IRC plugin for conversations and now I enjoy IRC on Fremantle :D
<Wizzup> yeah, we'll have that in leste eventually soon
<Wizzup> (well, deadline is 1 month from now)
<Wizzup> ;)
<freemangordon> /usr/bin/strace: ptrace(PTRACE_TRACEME, ...): Function not implemented
<Wizzup> freemangordon: is /proc mounted
<freemangordon> no :(
<Wizzup> in chroot: mount -t proc none /proc
<Wizzup> or use --rbind from outside chroot
<wunderw> Is this chat only for Leste or mainly for N900?
<freemangordon> didn;t help
<Wizzup> wunderw: not sure what you mean but for leste
<wunderw> Ok
<Wizzup> freemangordon: ok, then I don't really know why
<Wizzup> maybe qemu related or something
<freemangordon> will continue with prints
<freemangordon> mhm
<Wizzup> do you strace from within chroot?
<freemangordon> yes
<freemangordon> you mean I shall strace from outside?
<Wizzup> no, I don't think that makes sense
wunderw has left #maemo-leste [#maemo-leste]
<freemangordon> Wizzup: readdir returns null when trying to find the files in /usr/share/mime/packages
<freemangordon> ls works on that
<freemangordon> I am lost
<freemangordon> ugh, errno is 75
<freemangordon> OS error code 75: Value too large for defined data type
<freemangordon> hehe
<freemangordon> "The bug also affects shared-mime-info. update-mime-database uses readdir "
<freemangordon> :D
<Wizzup> freemangordon: hm... so qemu bug?
<freemangordon> not really
<Wizzup> well one suggestion seems to be to have a 32bit host
<Wizzup> I can spin up another vm now for that
<Wizzup> if parazyd can set that up that is
<freemangordon> mhm
<freemangordon> we need 32bits VM
<Wizzup> parazyd: what do you think ^^
<Wizzup> freemangordon: btw this is not fixed in newer kernel? or ?
<freemangordon> still reading LKML
<tmlind> mighty17[m]: no that's not needed, see the recent mainline wl1251 patches on how the mmc core can handle non-standard devices
<tmlind> see commit 187b164945c4 ("mmc: core: transplant ti,wl1251 quirks from to be retired omap_hsmmc")
<mighty17[m]> Ohk will look, thanks
<mighty17[m]> tmlind: that only works for wl1251? what about other chips?
<mighty17[m]> also doesnt explain mmc not working from cold boot :(
<Wizzup> freemangordon: lmk if you have another suggestion
<Wizzup> otherwise I will do the netinstall for 32 bit
<freemangordon> still reading through bugreports
<freemangordon> we're not the only ones to be bitten by that
<freemangordon> Wizzup: hmm, seems it might not help
<freemangordon> but better try it
<freemangordon> (32 bits on 32 bits)
<tmlind> mighty17[m]: you can add support for other chips
<freemangordon> Wizzup: I don't think we have a solution but to use 32 bits
<Wizzup> freemangordon: ok
inky_ has joined #maemo-leste
<mighty17[m]> tmlind: not merged yet? also from where do we get `card->*` info?
TonyStone has quit [Remote host closed the connection]
<Wizzup> freemangordon: setting it up now
<freemangordon> ok
<mighty17[m]> <mighty17[m]> "tmlind: not merged yet? also..." <- anyways this is a quirk for wl1251 only? as i've never seen it for bcm4330, plus we're moving to sdhci so it should be gone as well? im pretty confused and overwhelmed xD
<Wizzup> freemangordon: the vm is all set up waiting for parazyd to set up jenkins
<Wizzup> and then we should be good to go
xmn has joined #maemo-leste
<freemangordon> Wizzup: does it make sense to clone armsdk there and spin image build?
<freemangordon> armsdk it is not *that* hard once you get used to it :p
<Wizzup> freemangordon: hm?
<Wizzup> freemangordon: I'd rather wait for parazyd to add it to the CI so that we can assign the 32 bit image builder to all 32 bit arches
<Wizzup> s/arches/image builds/
<Wizzup> unless you want me to try and see if it works ok
<freemangordon> yeah, that was the point. up to you though
inky has joined #maemo-leste
inky_ has quit [Read error: Connection reset by peer]
TonyStone has joined #maemo-leste
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 260 seconds]
inky_ has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
inky_ has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
vectis_ has quit [Ping timeout: 268 seconds]
inky_ has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
LjL^ has joined #maemo-leste
doc|home has joined #maemo-leste
pere has quit [*.net *.split]
doc has quit [*.net *.split]
belcher has quit [*.net *.split]
Langoor has quit [*.net *.split]
BenLand100 has quit [*.net *.split]
sunshavi has quit [*.net *.split]
dsc_ has quit [*.net *.split]
freemangordon has quit [*.net *.split]
mrkrisprolls has quit [*.net *.split]
L29Ah has quit [*.net *.split]
avoidr has quit [*.net *.split]
LjL has quit [*.net *.split]
LjL^ is now known as LjL
Wikiwide has joined #maemo-leste
BenLand100 has joined #maemo-leste
Langoor has joined #maemo-leste
sunshavi has joined #maemo-leste
dsc_ has joined #maemo-leste
avoidr has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
pere has joined #maemo-leste
belcher has joined #maemo-leste
freemangordon has joined #maemo-leste
<Wizzup> happy new year!
<Wizzup> this year will be great :)
<r3boot> It will :) Enjoy! :)