<Wizzup>
also, in case people care, there is this: https://gitea.com/gitea/tea this should work with git.maemo.org
pere has joined #maemo-leste
_fab has joined #maemo-leste
<Wizzup>
sicelo: on upower, shall I do the packaging now/today?
_fab has quit [Ping timeout: 260 seconds]
<sicelo>
let me share an updated tree today.
<sicelo>
have been working on debian ofono (it's always excruciating :p ) but i finished yesterday. so today i can finish the upower and leste-config-n900-displace thing
<Wizzup>
ok, I was offering to do the upower if you can point me to a version
<Wizzup>
hm, do we need additional patches for upower, or just the latest tree?
<sicelo>
latest (best) is still sitting on my D4 which is refusing to boot atm :p
<Wizzup>
aha
<sicelo>
actually yes i can share how to go about it:
<sicelo>
take upower 1.90.7 from upstream (not 1.90.8 since that has a nasty bug)
<sicelo>
for packaging in daedalus, in debian/control and meson.build, add a patch to set the gudev-1.0 version to 237 (it actually wants 238, but daedalus does not have it. 237 works fine)
<sicelo>
that's all
<sicelo>
upower upstream will likely release a new version today (1.90.9) fixing the bug i mentioned. so it might also make sense to wait a little bit for the release, then package 1.90.9 as well, since that's what will likely be in Excalibur
<sicelo>
unfortunately, because of the nasty bug, 1.90.9 will ship without my work, so even on Excalibur, we will probably still need to keep our upower fork, unless Debian eventually does upgrade upower in Trixie :'(
<Wizzup>
I don't mind the forks too much
<Wizzup>
but not having them is better
<sicelo>
yeah. at least a fork that's in line with upstream is easy to deal with :-)
<sicelo>
Wizzup: so you'll handle upower?
<Wizzup>
I'll see if I can do it today
doc has quit [Remote host closed the connection]
_fab has joined #maemo-leste
_fab has quit [Ping timeout: 260 seconds]
hm has quit [Remote host closed the connection]
<sicelo>
ah, the D4's battery is completely dead now. pity i have so far struggled to find anything i could mod to fit
<sicelo>
Wizzup: so regarding MRs that were open during migration, is there a way to continue from where we left off, or best reopen? I'm guessing reopen though, since, for example, i am not sure how you can link the source repo for https://git.maemo.org/leste/leste-config/pulls/56 to my new account. or is there a way?
<Wizzup>
I think all the merge requests are just there right?
<Wizzup>
oh, you mean they aren't linked to your local forks
<Wizzup>
probably best to make a new one I think
<sicelo>
ok. i guess you should close that one then, since i won't be able to close it myself
<Wizzup>
ok, just reference the old one and I'll close em
<Wizzup>
freemangordon: btw, let's put procmgrd in our repos, and I can also do some testnig on my n900
pere has quit [Ping timeout: 248 seconds]
_fab has joined #maemo-leste
pere has joined #maemo-leste
ungeskriptet has joined #maemo-leste
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #maemo-leste
ungeskriptet_ has joined #maemo-leste
lexik_ has joined #maemo-leste
lyubov_ has joined #maemo-leste
ungeskriptet has quit [*.net *.split]
lyubov has quit [*.net *.split]
lexik has quit [*.net *.split]
ungeskriptet_ is now known as ungeskriptet
ShadowJK has quit [Ping timeout: 245 seconds]
ShadowJK has joined #maemo-leste
apac has joined #maemo-leste
<sicelo>
Wizzup: for the upower related changes in mce and status-area-applet-battery, please wait until the evening so i can update the MRs. on the D4 i had some extra changes that I needed. I'll mount the SD on PC
<Wizzup>
when I build, I'll do it for daedalus/experimental
<Wizzup>
this way we can be sure not to break for others
<sicelo>
sure. why not daedalus/devel though ... while we probably don't yet want to get it to all users, we do want it to get to most (if not all) testers, i.e. those on -devel.
<sicelo>
aim being - when daedalus releases, we want this to be in core/stable
ceene has quit [Ping timeout: 265 seconds]
ShadowJK has quit [Ping timeout: 260 seconds]
ShadowJK has joined #maemo-leste
ShadowJK has quit [Ping timeout: 252 seconds]
<Wizzup>
sicelo: any boot breaking changes I tend to put in experimental
System_Error has quit [Ping timeout: 264 seconds]
_fab has joined #maemo-leste
<freemangordon>
Wizzup: do we have a minimal VM for excalibur?
System_Error has joined #maemo-leste
ShadowJK has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Remote host closed the connection]
_fab has quit [Quit: _fab]
<Wizzup>
freemangordon: no, I think I just dist-upgraded daedalus
<freemangordon>
ok
mkfx has left #maemo-leste [Error from remote client]
Livio has joined #maemo-leste
<Wizzup>
sicelo: in case it wasn't clear, I just meant that I do my breaking testing in experimental
<Wizzup>
for more regular testing devel is fine
<Wizzup>
I agree it's different with unreleased daedalus, but since a bunch of us are on it already...
<Wizzup>
btw, the 'tea' tool I linked above can be run from a git repo cloned from git.maemo.org and it'll say show pull requests or issues, it's kinda neat
<freemangordon>
Wizzup: re procmgrd: do you want me to do anything?
<freemangordon>
keep in mind it needs new chagnelog if you are going to put in repos
<Wizzup>
if you want you can make a changeog, I'll add it to jenkins now
<Wizzup>
added
<freemangordon>
no, please make changelog and release
<freemangordon>
I am on rtcomel
<freemangordon>
btw, I think I shall implement cgroups support in procmgrd(by using libcgrop), using cgrulesengd will simply add another daemon doing similar to what procmgrd does in terms of netlink/procfs
<freemangordon>
also, cgrulesengd patches only on user and (optional) full binary patch
<freemangordon>
it cannot match on command line arguments or something more sophisticated
<freemangordon>
s/patches/matches
<freemangordon>
Wizzup: hmm, any idea how to get excalibur on armhf?
<freemangordon>
oh, tests are not mighrated, no wondeer they fail
Twig has joined #maemo-leste
System_Error has quit [Ping timeout: 264 seconds]
Livio has quit [Ping timeout: 264 seconds]
System_Error has joined #maemo-leste
mkfx has joined #maemo-leste
<mkfx>
hello.
fantom has joined #maemo-leste
Livio has joined #maemo-leste
<freemangordon>
mkfx: hi!
<sicelo>
freemangordon: excalibur on armhf ... daedalus excalibur you mean?
<Wizzup>
freemangordon: what do you mean not migrated?
<Wizzup>
freemangordon: ok, I will do the changelog
<Wizzup>
freemangordon: re: cgrulesengd, I cna't judge right now, but fine with whatever you prefer
<Wizzup>
freemangordon: I might have a armhf vm for you
<Wizzup>
sicelo: sounds good, just finishing up my work for today and see what I can do then
<sicelo>
now i'll dig up my most recent related mce patches, then sleep after sending them
<sicelo>
ok, for mce, seems https://git.maemo.org/leste/mce/pulls/63 contains the most recent work. pity the import didn't handle the review correctly. not a train smash though
<sicelo>
with upower, status-battery, and mce done, the only remaining stuff will be: (1) shipping a modified UPower.conf [via leste-config] for devices that need it. I think N900 and Droid4 at least. I doubt devices like PP need it
<sicelo>
(2) shipping, via leste-config, an mce-ini file with the new mce keys. Droid 4 probably doesn't need these, since it can just use the CriticalVoltage key. For N900, I do recommend using the new options and not CriticalVoltage. The new keys are sure to allow the calibration trigger to be hit before shutdown begins
<Wizzup>
that sounds good :)
<sicelo>
gn for now. if there is need to clarify anything in connection with the foregoing, you can just ping
<Wizzup>
gn, will do
Livio has quit [Ping timeout: 264 seconds]
<Wizzup>
sicelo: I merged some of the PRs, will make releases tomorrow
<Wizzup>
mkfx: well so armel will require an additional builder, and we'll have to rebuild all our packages, deal with any compiler warnings, other flags, missing asm that nokia had for arm, etc