Notices


Reply
Thread Tools
peterleinchen's Avatar
Posts: 3,392 | Thanked: 6,459 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#1841
Originally Posted by Ilew View Post
...
I guess this is my official offer to be cssu maintainer.
Thx. and more thanks
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following 5 Users Say Thank You to peterleinchen For This Useful Post:
Posts: 1,138 | Thanked: 1,817 times | Joined on Feb 2011 @ The Netherlands
#1842
In case you need this:
https://www.dropbox.com/s/47u8qwajb2..._Final.7z?dl=0

I will having a go at it too. To see if I can mange
__________________
N900 loaded with:
CSSU-T (Thumb)
720p recording,
Pierogi, Lanterne, Cooktimer, Frogatto
N9 16GB loaded with:
Kernel-Plus
--
[TCPdump & libpcap | ngrep]
--
donate
 

The Following 2 Users Say Thank You to mr_pingu For This Useful Post:
merlin1991's Avatar
Posts: 125 | Thanked: 1,142 times | Joined on Feb 2010 @ Austria
#1843
Originally Posted by Ilew View Post
That's easy enough.
I've already scripted the cloning and pulling from git.
I'll set up a new vm to do the building over the next couple days.
I guess this is my official offer to be cssu maintainer.
A few more things:
* update the dependencies and changelog in https://github.com/community-ssu/mp-...e-community-pr so that new packages are actually in the "release"
* which implies have an account on github so we can give you push access to the repos
* build packages with
Code:
dpkg-buildpackage -rfakeroot -I.git -us -uc
so that the entire .git repo is not included in the version tarballs
* you can get the builddepends faster in your sb with
Code:
fakeroot apt-get build-dep PACKAGE
* never trust the .deb filename for versions, ie. the 1: stuff in modest is not part of the filename -> always check in the .changes file of the package you built for the exact version to put into the mp
* use the script in https://github.com/community-ssu/cssu-state to find version differences between -devel -testing -stable and our git repos
* slap any bad developers that try to sneak in debhelper 7 funktions, cssu target build is debhelper 5 because 7 would make a requirement to extras

And probably most important show up in #maemo-ssu on freenode irc so we all can interact faster (especially when you run into the first build troubles)
__________________
"Fog is neither water nor air, it's something between." Merlin
 

The Following 8 Users Say Thank You to merlin1991 For This Useful Post:
Posts: 2,144 | Thanked: 8,407 times | Joined on May 2010
#1844
Before running dpkg-buildpackage I would suggest to clean git repository of autogenerated and unwanted files:
Code:
git clean -fdx
(read manpage git-clean what it is doing!)
 

The Following User Says Thank You to pali For This Useful Post:
merlin1991's Avatar
Posts: 125 | Thanked: 1,142 times | Joined on Feb 2010 @ Austria
#1845
Originally Posted by pali View Post
Code:
git clean -fdx
actually better: git clean -dfxe .gitignore

but since he usually will build from a fresh clone this shouldn't be required in the normal case
__________________
"Fog is neither water nor air, it's something between." Merlin
 

The Following 3 Users Say Thank You to merlin1991 For This Useful Post:
Posts: 74 | Thanked: 266 times | Joined on Aug 2012
#1846
Originally Posted by merlin1991 View Post
A few more things:
* use the script in https://github.com/community-ssu/cssu-state to find version differences between -devel -testing -stable

snip....

And probably most important show up in #maemo-ssu on freenode irc so we all can interact faster (especially when you run into the first build troubles)
That script is a lifesaver.
I was manually looking at the cssu-devel and coming up with the changelog/control files for the metapackage while scratchbox was downloading.

I do have a github account but I've never pushed anything before so I may need some help setting that up initially.
www.github.com/ileuu

Usually I lurk the irc logs but i'll make an effort to join.

Thanks for that merlin and pali. I'll save those commands and tips use them after work.

@merlin, pali, freemangordon or anyone else.
Is it okay to setup scratchbox locally and not use the vm image?
 

The Following User Says Thank You to Ilew For This Useful Post:
Posts: 3,037 | Thanked: 12,671 times | Joined on Mar 2010 @ Sofia,Bulgaria
#1847
It is, this is what I am using for cssu-thumb, however the risk of "polluting" it with packages from extras or other stuff while experimenting is higher than if you have dedicated VM just for CSSU.

BTW, hanging on #maemo-ssu is a kind of a must
__________________
Never fear. I is here.

720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900

Community SSU developer
kernel-power developer and maintainer

 

The Following 2 Users Say Thank You to freemangordon For This Useful Post:
Posts: 1,149 | Thanked: 2,784 times | Joined on Dec 2010
#1848
Originally Posted by freemangordon View Post
BTW, hanging on #maemo-ssu is a kind of a must
With my shift patterns/overtime etc that kind of rules me out unfortunately.
 

The Following 2 Users Say Thank You to Android_808 For This Useful Post:
Posts: 74 | Thanked: 266 times | Joined on Aug 2012
#1849
Originally Posted by freemangordon View Post
It is, this is what I am using for cssu-thumb, however the risk of "polluting" it with packages from extras or other stuff while experimenting is higher than if you have dedicated VM just for CSSU.

BTW, hanging on #maemo-ssu is a kind of a must
I've created a new user just for CSSU with it's own targets. So no "pollution" should happen.

Timezone may be a problem but I will try to hop on irc.

Looking at the cssu-state, it looks fairly easy to figure out what needs to be updated in testing.
A couple of question, should the deployment always go git->devel->testing->git-stable->stable?

I ask because community-ssu-enabler is:
Code:
0.8-1->0.7-3->0.7-5->0.7-5->0.7-5.
So in that case would we push 0.7-3 or 0.8-1 to test?

Here's a few more weird ones:
osso-systemui-alarm -
Code:
0.3.3+0cssu1->0.3.3+0cssu2->0.3.3+0cssu1
Seems like the devel version hasn't made it into git.
and tracker and vte -
Code:
0.6.95-35maemo1+0m5+0cssu1->0.6.95-35maemo1+0m5+0cssu0->0.6.95-35maemo1+0m5+0cssu1
Code:
1:0.16.14-0mh9.m7->1:0.16.14-0mh9.m6->1:0.16.14-0mh9.m7
For these ones the git version and test versions are higher than devel.

Sorry the formatting is not very good (Much easier to read in cssu-state).

Final question, what do we do for packages that are only in devel? Would the cssu-maintainer decide or is it the devs?

Here's the list of all the packages that are in test and have a newer version in git/devel :
Code:
package: updated to version
alarmd: 1.1.16+0m5+0cssu1
clock-ui: 0.7-0+0cssu8
community-ssu-enabler: 0.8-1
curl: 7.26.0-1maemo1+0cssu2
fmtx-middleware: 0.65.1
hildon-application-manager: 1:2.2.75-1
hildon-welcome: 0.23-4
ke-recv: 3.19-18
libpng: 1.2.49-1maemo1+0cssu3
mce: 1.8.127.5+0m5
modest: 3.90.7-13.5
openssl: 0.9.8zh-1+maemo1+0m5+0cssu0
osso-systemui-tklock: 0.3.1.1+0cssu2 or 0.3.1.1+0cssu1
profiled: 1.0.4 or none if it has to go to devel first
qt4-x11: 1:4.7.4~git20110505+cssu12
status-area-applet-battery: 1.0-11
mp-fremantle-community-pr: 21.2011.38-1Tmaemo12
Edit: I had trouble starting to build libpng because it depends on mawk and that isn't installable with the default repos.

My repo list:
Code:
[sbox-FREMANTLE_ARMEL: ~/cssu-master/libpng/debian] > cat /etc/apt/sources.list
deb http://repository.maemo.org/ fremantle/sdk free non-free
deb-src http://repository.maemo.org/ fremantle/sdk free
deb http://repository.maemo.org/ fremantle/tools free non-free
deb-src http://repository.maemo.org/ fremantle/tools free
deb http://repository.maemo.org/ fremantle/******************************** nokia-binaries
I did find it in:
http://repository.maemo.org/pool/maemo/ossw/m/mawk/

On my phone it is available to install:
Code:
mawk:
  Installed: (none)
  Candidate: 1.3.3-11.1
  Version table:
     1.3.3-11.1 0
        500 http://repository.maemo.org fremantle-1.3/free Packages
        500 http://repository.maemo.org fremantle/free Packages
Is it okay to install?

Last edited by Ilew; 2016-12-08 at 10:39.
 

The Following User Says Thank You to Ilew For This Useful Post:
Posts: 2,144 | Thanked: 8,407 times | Joined on May 2010
#1850
git repositories on github have branches which should match:

master --> cssu-devel
stable --> cssu-stable

cssu-testing currently is not branched, packages comes from cssu-devel. cssu-stable packages comes from cssu-testing repository after they are heavily tested. In some cases cssu-stable packages could be different as in cssu-testing (in case we need to patch old cssu-stable package, but do not want to use cssu-testing yet).

http://repository.maemo.org/pool/maemo/ossw is IIRC Maemo 1.0 and must not be used for Maemo 5.

You should use only Maemo 5 SDK repos (+ possible correct CSSU repo; e.g when building cssu-stable package, you can use cssu-stable repo, but not cssu-testing!), no Extras, no other repositories. If it is not possible (e.g there are missing dependences, or anything else), please ask us on IRC.

About that mawk, I do not know... merlin1991 should know it as he built those packages.
 

The Following 5 Users Say Thank You to pali For This Useful Post:
Reply

Tags
cssu testing

Thread Tools

 
Forum Jump


All times are GMT. The time now is 11:53.