IRC log for #maemo-ssu on 20140705

00:21.29*** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
00:47.35*** join/#maemo-ssu aap (~drew@cpe-71-72-180-216.woh.res.rr.com)
02:01.52*** join/#maemo-ssu silviof1 (~silviof@unaffiliated/silviof)
02:35.33*** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn)
05:36.43*** join/#maemo-ssu dhbiker (~dhbiker@APN-122-201-107-gprs.simobil.net)
05:51.21*** join/#maemo-ssu Roomer (~CLD@95-28-71-210.broadband.corbina.ru)
06:58.11*** join/#maemo-ssu dhbiker (~dhbiker@APN-123-48-177-gprs.simobil.net)
07:59.22*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
08:25.37*** join/#maemo-ssu Raimu (rmaunula@tuomi.oulu.fi)
08:35.57*** join/#maemo-ssu Roomer (~CLD@95-28-71-210.broadband.corbina.ru)
08:40.47*** join/#maemo-ssu sixwheeledbeast (~paul@78.144.105.255)
08:48.38*** join/#maemo-ssu Roomer (~CLD@95-28-71-210.broadband.corbina.ru)
08:52.41*** join/#maemo-ssu LauRoman (~LauRoman@5-14-94-113.residential.rdsnet.ro)
09:05.43*** join/#maemo-ssu eugene_42 (~eugene@109.188.124.136)
09:13.35*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
09:18.16*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
09:21.33*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
09:30.22*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
10:16.51*** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz)
10:35.58*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
11:31.28*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
11:50.05*** join/#maemo-ssu eugene_42 (~eugene@109.188.124.180)
13:17.44*** join/#maemo-ssu arcean (~arcean@aacw181.neoplus.adsl.tpnet.pl)
13:28.09*** join/#maemo-ssu sixwheeledbeast (~paul@2a01:348:6:860a:45be:cea0:7070:1191)
13:59.43*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
14:03.43*** join/#maemo-ssu sixwheeledbeast (~paul@2a01:348:6:860a:45be:cea0:7070:1191)
14:52.41*** join/#maemo-ssu sixwheeledbeast (~paul@2a01:348:6:860a:45be:cea0:7070:1191)
15:50.02freemangordonsixwheeledbeast: hi! do you need any help?
15:51.18sixwheeledbeastfreemangordon: well I wanted to check I was doing everything correctly and then try to release it.
15:51.41freemangordonso, do you need help or not? :)
15:52.01freemangordonsixwheeledbeast: BTW...
15:52.07sixwheeledbeasthow do we go about testing it for general release
15:52.20sixwheeledbeasts/for/before/
15:52.38freemangordonin order to be sure everything is set-up correctly, you can bring your own apt repo
15:53.00freemangordonon your PC that is, add that repo to your test device, etc.
15:53.31freemangordonalso, I think merlin1991 has such repo set up already, but not sure
15:53.57freemangordonsixwheeledbeast: what will be included in that release?
15:54.13freemangordonwhat was devided on the last meeting?
15:54.18freemangordon*decided
15:55.12sixwheeledbeastfreemangordon: the packages in the list from the meeting
15:55.32freemangordon(your own repo) - I have such test repo set up that I use before releasing -thumb updates
15:55.48sixwheeledbeastok I'll do that first then.
15:55.56sixwheeledbeastOh some questions...
15:56.05freemangordonit makes you feel confidednt you won;t gonna screw user's devices :)
15:57.15freemangordonwhat questions?
15:58.49sixwheeledbeastsome of the packages have only package version differences between master and stable like clutter for example, why
15:59.52sixwheeledbeastclutter 0.8.2-0maemo66+0m5+0cssu0 and 0.8.2-0maemo67+0m5 seem to be the same thing
16:00.00sixwheeledbeastfor example
16:00.23freemangordongoes to check
16:00.44freemangordonhttps://gitorious.org/community-ssu/clutter_0_8/commit/754de1d35bc316ce5d166785a09b8c17c9d6e95d
16:01.21freemangordonhttps://gitorious.org/community-ssu/clutter_0_8/commit/172befb5d3465313b8d6a6a9456224700345ff56
16:01.48sixwheeledbeastthins is also true for freetype
16:01.59sixwheeledbeasts/thins/this/
16:02.52freemangordonsixwheeledbeast: what version for clutter is now in -stabe?
16:02.56freemangordon*-stable
16:03.14sixwheeledbeastchecks
16:05.26freemangordonfreetype - same thing like clutter:
16:05.30freemangordonhttps://gitorious.org/community-ssu/freetype/commit/f0dcd3acbea40a48a93f74622ead1f3d995c815d
16:05.37freemangordonhttps://gitorious.org/community-ssu/freetype/commit/a2f3335caf287a73a7a32b6d90dc55a59d617693
16:06.12freemangordonversions differ because merlin1991 has "sanitized" them to fit cssu versioning scheme
16:06.21freemangordonsixwheeledbeast: ^^^
16:07.39freemangordonif you look at commit log, you'll see that there are more commits in stable than in testing https://gitorious.org/community-ssu/freetype/commits/f0dcd3acbea40a48a93f74622ead1f3d995c815d
16:07.49sixwheeledbeast0.8.2-0maemo66, so does this mean clutter is upto date on stable branch then?
16:08.55freemangordonno, because clutter on gitorious, branch stable is 0.8.2-0maemo66+0m5+0cssu0
16:10.40freemangordonsixwheeledbeast: you should get used to look at debian/changelog and commit log on gitorious, as we (the developers) try hard to not make changes without increasing the version
16:11.52freemangordonsixwheeledbeast: in general, versioning in cssu ie:
16:12.04sixwheeledbeastah it's currently 0.8.2-0maemo66+0m5+0cssu0 actually
16:12.54freemangordonif we are upstream, then we increase the "base" version, like we do for hildon-desktop
16:14.06freemangordonwell, then clutter in -stable is up-to-date
16:15.50freemangordon(versioning) if we are not upstream, we add +0cssu0 for the first time the package gets released in cssu, and increase like 0cssu1, 0cssu2 etc
16:16.10freemangordonmerlin1991 can elaborate more on that than me :)
16:16.54freemangordonsixwheeledbeast: what is the version of freetype in -stable?
16:17.38freemangordonhmm, libfreetype6 (>= 2.3.9-1osso2+0m5+0cssu1)
16:18.02freemangordonfreetype (2.3.9-2osso2+0cssu1) unstable; urgency=low
16:18.34sixwheeledbeastscratches head
16:18.36freemangordonthere is a difference
16:18.38sixwheeledbeast2.3.9-1osso2+0m5+0cssu1
16:19.06freemangordonops
16:19.08freemangordonmy bad
16:19.15freemangordonfreetype (2.3.9-1osso2+0m5+0cssu1) unstable; urgency=low
16:19.32freemangordonso freetype is uptodate too
16:20.28freemangordonbut pali's script listed it, because the version in -testing is not "sanitized)
16:20.39sixwheeledbeastoh.
16:20.54sixwheeledbeastso this is why
16:21.02freemangordonso those 2 can fall off the list imo. merlin1991 ^^^ ?
16:21.09sixwheeledbeasti think I understand a bit more now
16:21.16freemangordongood :)
16:21.48sixwheeledbeastlet me find the pirtae pad with the note I made....
16:22.02freemangordonsixwheeledbeast: did you try to merge clutter and freetype master->stable?
16:22.20freemangordonI guess it has failed. or rather said - merged nothing.
16:22.24sixwheeledbeastErr, yes
16:22.34sixwheeledbeastThat was what was confusing me
16:22.52freemangordonthat is normal, as it is already merged. and -stable branch is ahead of master
16:23.47sixwheeledbeasthttps://piratenpad.de/G4YLdvQN5k
16:24.15freemangordonsixwheeledbeast: great we make that clear. anything else you wanna ask?
16:24.45freemangordonhmm, what about that list on piratenpad?
16:25.18sixwheeledbeasterr probably, but I can't think now :D I understand a bit better now.
16:25.31freemangordongreat
16:25.43freemangordonping me if anything
16:25.59sixwheeledbeastso 0.8.2-0maemo67+0m5 is the same as 0.8.2-0maemo66+0m5+0cssu0
16:26.18freemangordonlooks like
16:26.26freemangordonjudjong by the commit log
16:26.32sixwheeledbeastand likewise for freetype, great. That really confused me.
16:26.32freemangordon*judging
16:26.41freemangordonyep, the same from freetype
16:27.04freemangordonyou may want to send an email to merlin1991, just to be 100% sure
16:27.12freemangordonthose are his commits after all :)
16:27.53sixwheeledbeastok so I don't need to update them, I'll remove them changes in the mp then
16:28.33freemangordonyou mean you'll revert the changes, right?
16:28.37freemangordonnot remove :)
16:29.09freemangordonas now -mp wants the correct versions to be installd
16:32.03sixwheeledbeastYes. Revert :) back to version S6. oh what is the normal method of building the packages clone them on git and then build them?
16:34.18freemangordongit clone; git checkout stable
16:34.37freemangordondpkg-buildpackage -rfakeroot -sa -us -uc -I.git
16:35.01freemangordonif you merge, don't forget to push back
16:35.12sixwheeledbeastI actually downloaded the tarball to scratchbox and built, Now I understand git a bit better make sense to pull them, build and push any changes to origin/stable.
16:35.31freemangordondownloaded the tarball?
16:36.01freemangordonwhere did you get it from, it is *YOU* that releases the tarballs in stable :P
16:36.14sixwheeledbeastWhat does the -I.git flag do? The tar from git on the web.
16:36.26freemangordonoh, I see
16:36.43freemangordon-I.git is to not include .git directory in the source package
16:37.09sixwheeledbeastah great I couldn't find that
16:38.10freemangordonBTW I am not sure for -us -uc, no idea who and where signs the packages in CSSU
16:38.37freemangordonbut aiui the packages are uploaded unsigned to repository.maemo.org
16:38.50freemangordonand there tham got signed
16:38.54freemangordon*them
16:38.56sixwheeledbeastcool I'll clean my files out and try everything again then try and setup a local apt, as you mention.
16:38.58sixwheeledbeast:nod:
16:39.47sixwheeledbeastOh I think I have one last question....
16:39.48freemangordonwell, you may skip that for the next update
16:40.05freemangordonyou can test the packages with dpkg -i as well
16:40.08freemangordongo on
16:40.54sixwheeledbeasthildon-application-manager 2.2.72-5 isn't tagged I want to make sure I rebase to the correct commit
16:41.54sixwheeledbeastI make it #abf64e2
16:43.37freemangordonlooks like the correct commit
16:44.15sixwheeledbeastgreat :D
16:44.36freemangordonhttps://gitorious.org/community-ssu/hildon-application-manager/commit/6bf3dfe986a13d0208b6a4aa4f1b07953622be72
16:44.55freemangordonthis is the second parent in https://gitorious.org/community-ssu/hildon-application-manager/commit/abf64e2af41a535d0b2033e479d5dd563e4c44e8
16:45.43freemangordonwonders why this is not merged with keeping the history, but anyway :)
16:46.06freemangordonoh, "Conflicts: debian/changelog"
16:46.52sixwheeledbeastok so I can merge stable to #abf64e2
16:47.01freemangordonI think so
16:47.32freemangordonyou may want to ask git to compare master/stable after that
16:48.11freemangordonyou should have only my "speedyham" patches and pali's latest changes as a difference
16:50.15sixwheeledbeast:nod: "git diff" So would I normally merge or rebase when updating the stable branch?
16:54.47freemangordonI thinks so. keep in mind I've never been the -stable maintainer ;)
16:55.04freemangordonfor -thumb I do git merge
16:55.35sixwheeledbeastok
17:27.08sixwheeledbeastgoes to check the other packages to make sure there's no more with the "sanitizing" issue
17:28.50sixwheeledbeastfacepalms and releases he can use git diff
18:04.17*** join/#maemo-ssu arcean (~arcean@aacw181.neoplus.adsl.tpnet.pl)
18:04.19*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
18:11.43*** join/#maemo-ssu arcean (~arcean@aafs193.neoplus.adsl.tpnet.pl)
18:14.17sixwheeledbeastfreemangordon: I think gtk has different version numbers but package is the same http://privatepaste.com/02332615b3
18:15.59*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
18:40.44sixwheeledbeasthmm, does git normally act weird in scratchbox.
18:46.15*** join/#maemo-ssu drathir (~kamiljk8@s51.linuxpl.com)
19:00.00sixwheeledbeastgit clone; git checkout stable doesn't work :S
19:06.27*** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
19:54.05*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
19:59.33*** join/#maemo-ssu aap (~drew@cpe-71-72-180-216.woh.res.rr.com)
20:04.14*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
20:21.16*** join/#maemo-ssu eugene_42 (~eugene@109.188.126.236)
20:41.28*** join/#maemo-ssu _rd (~rd@p57B48376.dip0.t-ipconnect.de)
21:12.04*** join/#maemo-ssu infobot (~infobot@rikers.org)
21:12.04*** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2014-01-01): 21.2011.38-1Tmaemo9.1; Stable(2013-06-18): 21.2011.38-1Smaemo6.1
21:12.04*** mode/#maemo-ssu [+v infobot] by ChanServ
21:18.59*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
22:01.53*** join/#maemo-ssu LauRoman|Alt (~LauRoman@5-14-83-50.residential.rdsnet.ro)
22:22.04freemangordonsixwheeledbeast: yes
22:22.25freemangordonyou should git clone, git checkout -b stable origin/stable
22:22.30freemangordonor similar
22:23.50sixwheeledbeastfreemangordon: I did git clone and checkout then /scratchbox/login/ in the end
22:24.03sixwheeledbeastfreemangordon: I am correct about gtk?
22:25.44freemangordonsixwheeledbeast: sorry, can't check right now. GF's calling me ;)
22:25.54freemangordonwill do it tomorrow
22:25.58sixwheeledbeasthave fun...
23:11.17*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.