<freemangordon>
arno11: ^^^ this might help a lot on n900, but I have no time now to play with it, you may want to
uvos__ has joined #maemo-leste
_fab has quit [Ping timeout: 240 seconds]
<sicelo>
freemangordon: thanks for the ofono patches. will build and test in a bit. just take upstream and apply? no other patches needed?
<freemangordon>
umm, use our repo and apply
<freemangordon>
upstream still does not have d4 qmi patch
<freemangordon>
sicelo: however, I will push to leste repo in the evening, so, maybe just wait
<sicelo>
cool, thanks. no rush from my end since i'm also at $day_job right now anyway
uvos__ has quit [Quit: Konversation terminated!]
_fab has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
freemangordon: it seems you made a patch for it: commit ee6731e307
<arno11>
but seems never applied
xinomilo has joined #maemo-leste
apac has joined #maemo-leste
_fab has quit [Ping timeout: 240 seconds]
<Wizzup>
arno11: what do you mean, never applied?
<arno11>
i mean the patch is there, but some files involved not
_fab has joined #maemo-leste
_fab has quit [Remote host closed the connection]
<arno11>
Wizzup: scratch that, seems ok
_fab has joined #maemo-leste
arno11 has quit [Quit: arno11]
_fab has quit [Ping timeout: 240 seconds]
_fab has joined #maemo-leste
mkf has left #maemo-leste [Disconnected: Replaced by new connection]
mkf has joined #maemo-leste
_fab has quit [Ping timeout: 260 seconds]
arno11 has joined #maemo-leste
<arno11>
Wizzup: freemangordon: in fact, that's wrong: in jenkins, i see 'dpkg-source applying *.patch then 'unapplying *.patch --after-build !
<arno11>
*for gtk
<Wizzup>
I think that's normal quitl behaviour
<Wizzup>
quilt
<arno11>
ok but patches are not applied, right ?
<Wizzup>
I think they are
<Wizzup>
but worth checking
<Wizzup>
bbiab
<arno11>
ok
xinomilo has quit [Quit: Leaving]
<sicelo>
arno11: yes, Wizzup is right. dpkg-buildpackage applies everything in debian/patches, builds the package, then unapplies the patches. if it didn't, then the source files would be left in a different state than it was before build
<arno11>
ok, makes sense, ty
arno11 has quit [Quit: arno11]
narodnik has quit [Ping timeout: 276 seconds]
pere has quit [Ping timeout: 240 seconds]
pere has joined #maemo-leste
LeePen has quit [Read error: Connection reset by peer]
LeePen has joined #maemo-leste
narodnik has joined #maemo-leste
_fab has joined #maemo-leste
_fab has quit [Ping timeout: 240 seconds]
ceene has quit [Ping timeout: 248 seconds]
narodnik has quit [Ping timeout: 252 seconds]
_fab has joined #maemo-leste
Anasko has quit [Ping timeout: 245 seconds]
_fab has quit [Ping timeout: 245 seconds]
<sicelo>
nice, fmg's patches already merged by upstream.
<freemangordon>
yep
<freemangordon>
will push to our repo in a while
<freemangordon>
Wizzup: or, you can do as well, just take upstream patches and apply
apac has quit [Ping timeout: 248 seconds]
a_fantom has quit [Quit: Connection error?!]
narodnik has joined #maemo-leste
<Wizzup>
freemangordon: do you want me to make a new release?
<sicelo>
i believe, Yes, at least for -devel
vectis has joined #maemo-leste
<Wizzup>
freemangordon: looks like they merged both patches
<freemangordon>
Wizzup: yes, pull those 2 patches and make a new release, directly for -stable
<Wizzup>
ok
<freemangordon>
Wizzup: keep in mind that after the upgrade *all* unacked SMS-es will be re-send :)
<Wizzup>
freemangordon: what is the practical impact
<freemangordon>
you'll receive them again
<Wizzup>
yes, but since when?
<freemangordon>
since first that was not acked (unless the network timed them out)
<sicelo>
:-)
<freemangordon>
you'll receive them in a row :)
<freemangordon>
another option - move the sim to another phone
<sicelo>
i took my droid 4 sim to my android phone some time ago and was flooded, so yeah. but at least there's peace afterwards
<freemangordon>
yeah, this will happen only once
<Wizzup>
interesting, how many SMSes does the network keep
<Wizzup>
I suspect most would be timed out, otherwise they'd try to send them again, no?
<Wizzup>
freemangordon: so take 2.12 or do you want a newer ofono with your patches
<Wizzup>
They seem to be on 2.17
<Wizzup>
nevermind
<Wizzup>
we're also on 2.17
_fab has joined #maemo-leste
vectis has quit [Ping timeout: 276 seconds]
_fab has quit [Ping timeout: 240 seconds]
<Wizzup>
freemangordon: building for devel
<Wizzup>
just to be careful
vectis has joined #maemo-leste
<sicelo>
seems done. let me upgrade
<Wizzup>
not yet, few more mins
<Wizzup>
sicelo: should be ok now
vectis has quit [Ping timeout: 252 seconds]
vectis has joined #maemo-leste
narodnik has quit [Ping timeout: 248 seconds]
<sicelo>
Wizzup: something's not right with mce in repos ... could explain why your friend has an issue (or maybe not)
<sicelo>
anyway, battery-upower module is missing with mce in daedalus-devel repos. just noticed now while updating ofono
<Wizzup>
sicelo: hm...
<sicelo>
the packaging itself seems ok, because i cloned the tree just now, and built locally. the module was correctly installed. so maybe the builder had a glitch. perhaps just force a rebuild?
xmn has quit [Ping timeout: 268 seconds]
xmn_ has joined #maemo-leste
xmn_ has quit [Read error: Connection reset by peer]
kiva has joined #maemo-leste
kiva has quit [Quit: Client closed]
akossh has joined #maemo-leste
akossh has quit [Ping timeout: 245 seconds]
xmn_ has joined #maemo-leste
xmn_ has quit [Ping timeout: 260 seconds]
xmn_ has joined #maemo-leste
xmn_ has quit [Ping timeout: 260 seconds]
akossh has joined #maemo-leste
<freemangordon>
hmm, in the VM SMS was successfully received by ofono, however, there is no new SMS notification from conversations, weird
<freemangordon>
Wizzup: does new ofono work for you?
xmn_ has joined #maemo-leste
* sicelo
tries an sms
apac has joined #maemo-leste
<freemangordon>
and?
<sicelo>
sorry, got distracted. but i've got the sms
<sicelo>
no duplicate yet, so i think we're good
vectis has quit [Ping timeout: 252 seconds]
apac has quit [Ping timeout: 245 seconds]
apac has joined #maemo-leste
<Wizzup>
freemangordon: will check tomorrow morning :)
<sicelo>
so far good on my end. by this time, the sms would already be duplicated. i tested with two