<freemangordon>
uvos__: so, shall I change to signed long long int?
<uvos__>
i dont think it makes a difference, just like intmax_t could (really should) be 128 long long can be anything too, but in practice is 64bit. So no strong opinion
<uvos__>
its fine
<freemangordon>
ok
<freemangordon>
so, it seems time_t is 32bits on daedalus and 64 bits on excalibur
<Wizzup>
freemangordon: great :)
<sicelo>
yup, excalibur being based on trixie, which had the t64 transition :-)
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
<Wizzup>
freemangordon: ok, well, with that out of the way we should release daedalus soon (assuming no more big blockers)
arno11 has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
Livio has joined #maemo-leste
Daanct12 has quit [Quit: WeeChat 4.6.2]
xmn has quit [Remote host closed the connection]
parazyd has quit [Ping timeout: 272 seconds]
xmn has joined #maemo-leste
parazyd has joined #maemo-leste
parazyd has quit [Changing host]
parazyd has joined #maemo-leste
ceene has quit [Ping timeout: 252 seconds]
Livio has quit [Ping timeout: 264 seconds]
fmg_d4 has quit [Ping timeout: 276 seconds]
<freemangordon>
Wizzup: right
<uvos__>
do we have a daedalus-devel repo already?
<freemangordon>
I think yes
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
<uvos__>
ok so if we are releasing deadalus soon i presume i shal now stop building for non devlel daedalus directly and will do so.
<sicelo>
uvos__: freemangordon: i think sphone needs to be rebuilt asap ... the rtcom change is crashing sphone
<sicelo>
"rtcom_el_iter_get_values: bug in library, unexpected type gint64"
<sicelo>
started just after upgrading
ladslat has joined #maemo-leste
<ladslat>
hello
<ladslat>
frick
arno11 has left #maemo-leste [#maemo-leste]
<ladslat>
i mispelled ladsalt
ladslat has left #maemo-leste [#maemo-leste]
ladsalt has joined #maemo-leste
<ladsalt>
back
<ladsalt>
hello everyone
<ladsalt>
id like to know if maemo supports modern firefox
ladsalt has quit [Remote host closed the connection]
ladsalt has joined #maemo-leste
<uvos__>
freemangordon: please rebuild sphone, i cant atm
<uvos__>
ladsalt: sure maemo is just devuan (which is essentally debian)
<uvos__>
you can install and run anything that runs on debian
<uvos__>
however of our supported phones only the pinephone is fast enough to have a decent expirance
<uvos__>
n900 just flat dosent have the ram and droid 4/ mapphones is are painfull with modern ff
<uvos__>
chromium dose a bit better, jib dose better still but is still a bit unfinished, theres also qtwebbrowser
<uvos__>
for n900 the only thing you can really use is dillo and things like links2
<ladsalt>
i hope one day maemo will be supported on anything with a unlocked bios like other linux phones
<ladsalt>
in the mean time ill just have to wait for my pixel 8a to crap out so i can switch to pinephone
<uvos__>
its hard as arm based phones dont follow a standard and are all special snoflakes you need to write specific support for
<uvos__>
a generic arm phone distro will never happen as a result
<uvos__>
with current hardware anyhow
<uvos__>
google is slowly pushing for things to standardize as they are a bit sick of dealing with this with android too
<ladsalt>
also x86 phones must hog up the battery like crazy
<ladsalt>
although one could use limbo vm or somethin and use it as there launcher on android
<ladsalt>
however i know it will happen someday
<sicelo>
ladsalt: well, any mainlined phone should be supported in leste. just needs someone to do the basic integration work (not a lot if mainline linux is already working well on said phone)
* sicelo
is working on Librem5 support, for example (but getting sidetracked a lot - but at least so far it's been distraction with important leste stuff)
<sicelo>
so if you have in mind a phone that pmOS supports using mainline, this channel might be able to help you get it up and running with Leste to nearly the same level of functionality as pmOS
<ladsalt>
well im not sure getting it running on a tensor cpu will be very pratical
<ladsalt>
why does my maemo vm just go blank after a while
<ladsalt>
is it in sleep mode or something?
<sicelo>
yes, because the phone also defaults to that
<sicelo>
just go to Display settings and disable the timeout (i seem to think it should default to that on VM)
<ladsalt>
oddly enough i cant seem to wake it up
<uvos__>
we dont currently have a mechnaism to have different gconf defaults for specific device builds
<uvos__>
ladsalt: you have to press power
<ladsalt>
problem
<ladsalt>
im on a vm
<ladsalt>
there is no power button
<uvos__>
vms ususally have a way to press power
<Wizzup>
the qemu gtk interface has a 'shut down' option
<Wizzup>
hit that and it'll press the button
<ladsalt>
on virtualbox
apac has joined #maemo-leste
<uvos__>
"also x86 phones must hog up the battery like crazy" x86 phones exited
<uvos__>
they where not really better
<uvos__>
as just becasue you are x86 dosent mean you are a pc with acpi and probeable buses like pci
<uvos__>
the x86 phones where also special snoflakes that needed you to write specific support
<uvos__>
what you want is a phone that is also an IBM PC comptable / acpi device
<ladsalt>
interesting
<ladsalt>
i just have always heard that x86 tends to use more power
<uvos__>
thats not really true, i mean its bearly true the instruction decoder uses a tiny bit more power
<uvos__>
but the main reason why practical x86 devices use more power is because they are not as optimized for that
<uvos__>
the instruction set has very litttle to do with it
<uvos__>
Motorola made a x86 phone that is related to the devices we support at around the same time:
<sicelo>
aka 1.x is OS2005, 2.x is OS2006. The 770 ran both. and sorry, it's not N770 :-)
ladsalt has joined #maemo-leste
<ladsalt>
i give up lol
<sicelo>
use the proot way really
<ladsalt>
cant get adb to work
<ladsalt>
id rather just wait for a chance to get a pine phone
<ladsalt>
you know what would be really cursed?
<ladsalt>
wine
<ladsalt>
on maemo
<ladsalt>
how do i get snap working?
<ladsalt>
just doing "sudo apt install snap" seems not to work
<ladsalt>
i type snap after and returns a not found
apac has quit [Ping timeout: 252 seconds]
<sicelo>
isn't that an Ubuntu thing?
<sicelo>
anyway, the OS is basically Devuan ... so whatever way works on Devuan/Debian should work
ladsalt has quit [Quit: Client closed]
ladsalt has joined #maemo-leste
<ladsalt>
how would i get glibc working?
<sicelo>
it's working already, no? deb/vuan is a glibc distro
<ladsalt>
i meant it isnt preinstalled
<sicelo>
it is
<sicelo>
without it, there's basically no distro :-)
<ladsalt>
when i try to run snap it says its missing
<sicelo>
then snap is wrong or you should share the real error from snap
<sicelo>
glibc --> lib6 2.36-9 is the version we're currently running in Leste
<sicelo>
s/lib6/libc6/
<sicelo>
btw, what you you want/need snap for?
<ladsalt>
its just easier to use then apt
<sicelo>
easier for?
<ladsalt>
snap: /lib/x86_64-linux-gnu/libc.so.6: version "GLIBC_2.34" not found (required by snap)
<sicelo>
i admit i don't know a lot about snaps, but afaik it's for specially packaged packages, not just about anything
<sicelo>
so if you want a replacement for apt, snap is likely not the solution ...
<ladsalt>
its easier because you usually dont have to get dependencies and also firefox requires it from what ive experienced
<sicelo>
FF doesn't require it, no
<ladsalt>
huh odd
<ladsalt>
awhile back i tried making my own bloatfree distro without snap and when i ran firefox it required snap
<sicelo>
what's the real problem with FF :-)
<ladsalt>
well there is that firefox also is demanding glibc
<sicelo>
i'm still using FF (currently v. 138) and I've never installed snap
<ladsalt>
my memory is wrong i guess
<sicelo>
20:56 < ladsalt> snap: /lib/x86_64-linux-gnu/libc.so.6: version "GLIBC_2.34" not found (required by snap) <<< looks like here it's looking for a very specific glibc version
_fab has joined #maemo-leste
<sicelo>
as indicated already, daedalus has glibc 2.36
<ladsalt>
tryin to run --fix-broken install just removes snapd guess it cant find the version specifyed
<ladsalt>
this is very confusign
<ladsalt>
confusing*
<sicelo>
still didn't understand why snapd is needed in the first place though ... so it's not easy to advise accordingly
<sicelo>
why not install Synaptic?
Livio has joined #maemo-leste
_fab has quit [Ping timeout: 260 seconds]
<ladsalt>
good idea
<ladsalt>
just repeats waiting for cache lock: could not get lock
<ladsalt>
what is the sudo password on the vm (synaptic requires it
<ladsalt>
fixed
ladsalt31 has joined #maemo-leste
<ladsalt31>
any good browsers on synaptic?
<ladsalt31>
that supports maemo
ladsalt has quit [Ping timeout: 240 seconds]
<sicelo>
firefox?
<sicelo>
might be named firefox-esr
<sicelo>
freemangordon: i suddenly miss the sharing plugins from Fremantle :p
<ladsalt31>
i tried "firefox" and it said it was basically a package that didnt exist and was just refrenced by another one from what i remember
<ladsalt31>
yup it was that it was firefox-esr
Twig has quit [Ping timeout: 276 seconds]
mp107 has quit [Ping timeout: 272 seconds]
mp107 has joined #maemo-leste
<ladsalt31>
a maemo themed android launcher would be really cool
<ladsalt31>
and it could have termux as the terminal
<ladsalt31>
would 100% use that
<ladsalt31>
bye!
ladsalt has joined #maemo-leste
<ladsalt>
back
<ladsalt>
how good does leste run on a n900?
ladsalt has quit [Client Quit]
ladsalt31 has quit [Ping timeout: 240 seconds]
ladsalt has joined #maemo-leste
ladsalt has quit [Client Quit]
ladsalt has joined #maemo-leste
ladsalt has quit [Client Quit]
saeed has quit [Ping timeout: 244 seconds]
saeed has joined #maemo-leste
apac has joined #maemo-leste
branon has quit [Remote host closed the connection]
branon has joined #maemo-leste
<f_>
ladsalt Apparently very good
Livio_ has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
fantom has joined #maemo-leste
a_fantom has quit [Ping timeout: 244 seconds]
<freemangordon>
sicelo: will do, tomorrow
<freemangordon>
though, I don;t see why would sphone crash