[12:03] marcin`, ArmeBosse: 2027 is the right one to review? [12:04] sistpoty: currently yes [12:04] no it's not the right one* [12:04] marcin`: what do you mean w. currently? another upload pending? [12:04] ArmeBosse: do you really want your config.template.php ? [12:04] sistpoty: just a moment [12:05] marcin`: sure [12:05] there's probably 2 different package from 2 people if we continue === sistpoty gets a break and is out for a smoke [12:06] ArmeBosse: is there something else different than this postinst script? [12:06] oh yes, i can send you a diff [12:06] ok [12:07] there's 16 files changed from previous upload [12:07] no 13 [12:07] ? [12:07] no way... [12:07] you count these removed files that are related with 'themes' ? [12:08] morning all [12:08] just a diff and count how many files [12:08] ArmeBosse: I ask about difference between package on your website [12:08] ArmeBosse: and this one that is currently in revu [12:09] i talk about previous upload [12:09] ajmitch_: hi [12:09] ArmeBosse: I got /debian directory from your current package [12:10] svn is the real one synced [12:10] heh need to learn svn [12:10] hi ajmitch_ [12:10] can you tell me how to checkout this now? [12:10] just read the page [12:11] ajmitch_: hello [12:11] http://vtigerforge.fosslabs.com/scm/?group_id=20 [12:12] ok got it [12:12] just a sec [12:12] anyway I think that sistpoty could take a look on vtiger now [12:13] time is running [12:13] and I'm almost sure that the only thing that could be different is this postinst script [12:13] ajmitch: I was told that you have main privs? Do you have time to look at libnfsidmap? Simple task ;) [12:14] marcin`: you're wrong [12:14] tepsipakki: yes I do have upload privileges, no I don't have time [12:14] ArmeBosse: my password doesn't work [12:14] http://revu.tauware.de/diff.py?upid1=2026&upid2=2027 [12:14] ArmeBosse: need to checkout anonymous [12:15] if you don't know your pass, you can't put polish lang [12:15] ajmitch: ok, np [12:16] tepsipakki: btw.: is this a new upstream version? [12:16] marcin`: http://revu.tauware.de/diff.py?upid1=2026&upid2=2027 [12:16] ArmeBosse: I can log to polish lang as admin [12:16] ArmeBosse: and I know my password but this pass doesn;t work with svn for ubuntu package [12:16] same pass [12:17] use 3 times [12:17] sistpoty: yes [12:17] same pass [12:17] like alioth [12:17] shit... I also forgot about header in 'copyright' [12:17] tepsipakki: you'll need to request an UVF-exception as well (just in case you haven't done so yet) [12:17] UVF exception ? [12:17] sistpoty: done already [12:17] good [12:18] ArmeBosse: no 'package was debianized by..." and my credentials [12:18] ArmeBosse: I added these additional licenses but forgot to change header [12:18] ArmeBosse: UpstreamVersionFreeze was some time ago, that means new upstream version for existing packages need prior approval [12:18] k [12:19] marcin`: you don't seem to look same diff file [12:21] I look on this *2027 [12:22] we need to synchronize in 100% [12:22] I'll be ready [12:22] in 10 minutes [12:22] sistpoty: are you here? [12:23] marcin`: yes [12:23] sistpoty: short question [12:23] sistpoty: we need to synchronize some changes but I also got more general question [12:24] go ahead then ;) [12:24] sistpoty: we have some not so important differences between ArmeBosse repo and mine [12:24] sistpoty: but there is one important thing [12:24] sistpoty: in vtigercrm-mysql-local we need to create /etc/vtigercrm/config.inc.php file [12:25] sistpoty: we do this in *.postinst script but in different way [12:25] i'll bet and win ;) [12:25] sistpoty: ArmeBosse has debian/config.template.php file [12:25] sistpoty: and he want's to install this file in /etc/vtigercrm/ [12:26] sistpoty: from 'rules' script [12:26] he can look previous package [12:26] sistpoty: and then use this template to as input to generate /etc/vtigercrm/config.inc.php [12:26] http://revu.tauware.de/details.py?upid=2026 [12:26] sistpoty: hmm I'm lost now maybe previous... [12:27] ArmeBosse: right [12:27] sistpoty: so there you can take a look at ArmeBosse way [12:27] sistpoty: and in current http://revu.tauware.de/details.py?upid=2027 [12:27] sistpoty: you can take a look at my way in .postinst [12:28] phew... before I take a look... just a questions, maybe it solves the issue [12:28] sistpoty: I create config.template.php on the fly with mktmp and it goes to /tmp [12:28] sistpoty: and then I use this file as input for postinst - and remove on the end [12:28] sistpoty: question is - which solution is better === hub [n=hub@toronto-hs-216-138-231-194.s-ip.magma.ca] has joined #ubuntu-motu [12:29] marcin`, ArmeBosse: if you install that file under /etc... is creating the actual config from it repeatable (as in calling a command and get a config from it)? [12:29] sistpoty: will you complain on ArmeBosse way? === cassidy [n=cassidy@f1-pc174.ulb.ac.be] has joined #ubuntu-motu [12:29] repeatable yes via dpkg-reconfigure [12:30] only config-files should actually go to /etc/... if the template doesn't fulfill the meaning of a config-file, it shouldn't be there [12:30] rule / debian policy to refer to please ? [12:30] but in the case, that an admin has the possibility to change the template and easily create a new (actual) config-file from it, it sounds like a good solution to me [12:31] ArmeBosse: probably in fhs... or in debian-policy where it says about config-files... would need to look myself [12:31] my point of view: [12:31] for me it must be readable and maintainable [12:32] ArmeBosse: heh and I missed README.Debian... need to change my build scripts... [12:32] a postinst is postinst and not a template [12:32] marcin`: you missed many things [12:32] ArmeBosse: but user should not maintain *.template.inc [12:33] if i need to change the template i don't want to touch postinst file [12:33] from my point a view a non sense [12:33] user no, user don't touche /etc [12:33] ArmeBosse: the thing is that user shouldn't touch template.php at all [12:33] admin yes [12:34] ArmeBosse: ok - not user - admin [12:34] ArmeBosse: but if admin - then stil he should touch config.inc.php - not template.php [12:35] i want to use dbconfig facility [12:35] ArmeBosse: neither fsh nor debian-policy seem to provide exhaustive information on this [12:36] yes in general, it's to admin point of view [12:36] only thing in fhs is: /etc contains configuration files and directories that are specific to the current system. === ogra_ibook [n=ogra@ubuntu/member/ogra] has joined #ubuntu-motu [12:36] so the question is: is this used to configure s.th. or just a template, which an admin can use as *template* to write his config-file from [12:37] sistpoty: it's just template [12:37] not for me :) [12:37] hehe [12:37] sistpoty: but in fact it's not for admin - postinst uses this file as input to generate config.php [12:37] ok, ArmeBosse, with your solution I could dpkg-reconfigure and would have a new config-file, right? [12:38] anyway i'll keep it like this in debian package as we can't find consensus [12:38] yes [12:38] ok... then to marcin`'s solution [12:38] sistpoty: yes with his solution you end with two files in /etc/vtiger [12:38] sistpoty: with /etc/vtigercrm/config.inc.php and config.template.php [12:38] marcin`: you create the actual config on the fly in postinst, right? [12:39] sistpoty: right [12:39] marcin`: so you don't need another file... but what happens if the user changed the config-file himself? [12:39] in fact out solution are simmilar [12:39] marcin`: will it get overwritten? [12:40] (on upgrading for example= [12:40] hmm propably dpkg will ask if it should be overwritten or not [12:40] lol [12:40] marcin`: so you have the config-file itself *inside* the package and modify it during postinst? [12:41] sistpoty: yes because we need to put some info about database there [12:41] sistpoty: ArmeBosse solution does the same thing with the same tool [12:41] sistpoty: the only difference is that he puts his template file to /etc/vtigercrm [12:42] sistpoty: and it stays there [12:42] marcin`: that's wrong... you cannot modify a file during postinst, that's a conffile inside the package (and this is part of the policy) [12:42] sistpoty: after installation [12:42] sistpoty: while I put my file in /tmp and remove after postinst will create /etc/vtigercrm/config.php [12:43] config.inc.php [12:43] yes config.inc.php [12:43] marcin`: so /etc/vtigercrm/config.php is *not* part of the package? [12:43] no [12:43] ok [12:43] as I said - our solutions are almost identidal [12:43] of source package you mean ? [12:44] marcin`: but the issue still remains: what if an admin changes /etc/vtigercrm/config.php... will it get overwritten (e.g. on upgrade) or not? [12:44] sistpoty: it will if admin will let to do this [12:44] sistpoty: I don't understand this question [12:45] sistpoty: if you got some file in etc and you change this file then postinst will ask you what to do with config - keep/overwrite/show diff [12:45] sistpoty: right? [12:45] sistpoty: thing is you got two solutions: [12:45] marcin`: if it's a conffile (i.e. *inside* the package) dpkg will do it for you [12:46] marcin`: if it's created during postinst, you'll need to make this sure for yourself [12:47] sistpoty: 1. install debian/template.php to /etc/vtiger/template.php -> run postinst and use template.php to create /etc/vtiger/config.php [12:48] using dbconfig-common [12:48] 1 is me ;) [12:48] sistpoty: 2. create temporary template in tmp/template.php -> run postinst and use tmp/template.php to create /etc/vtiger/config.php -> clean tmp/template.php [12:49] marcin`, ArmeBosse: there is no such thing as "the right way" for it... [12:49] we both use the same script to generate config.inc.php but different sources [12:50] marcin`: with 2. you'll need to ensure that admin-changes aren't lost (for 1. as well, but it's not so bad, if the created file get's overwritten imo) [12:50] and the only one 'visible' difference is that ArmeBosse keeps his template.php in /etc and I clean it [12:50] sistpoty: i know just we're not agree between us ;) [12:50] hehe [12:50] dismissed !!! [12:50] like MTV program [12:51] imo, 1. is s.th. that's more handy for an site-admin, since he can always change the template and regenerate the config-file from it [12:51] ArmeBosse: well the thing is that it's not the problem for me how this config.php is createt [12:51] created [12:51] ArmeBosse: I like this template.php too [12:51] so wher's the problem ? [12:51] ArmeBosse: but I think that we should clean this file from /etc [12:51] so I would personally go for 1.... but as stated before, there is "right"/"wrong" way for both of it [12:52] ArmeBosse: in my opinion in /etc/ should be only 'real' config not template+config [12:53] sistpoty: an other think, i'm also upstream and debian maintainer, and keep this like that. just ubuntu package is "collaborative", so fork the solution or not [12:53] ArmeBosse: unfortunately dbconfig-common script apparently doesn't support relative paths so we need to put this template file somewhere [12:53] marcin`: exim4 does it (similar) to ArmeBosse's solution... you have /etc/exim4/update-exim4.conf.conf and /etc/exim4/exim4.conf.template, and can call a script to generate the actual configuration files from it [12:54] marcin`: imo a template from which a config-file can be created is a config-file as well [12:55] but anyways... I stated what thing I'd prefer... both seem "right" as long as they respect 10.7 from debian-policy [12:55] okidoki [12:56] it will be ArmeBosse's solution in package [12:56] an issue resolved [12:56] need to copy these differences carefully [12:56] alleluia [12:56] ArmeBosse: :) [12:56] hehe... luckily you didn't disagree on wether to use cdbs or debhelper *g* [12:56] ArmeBosse: and we are sure that sistpoty will accept this postinst ;) [12:56] must ajmitch_ turn ;) [12:57] ? [12:57] sistpoty: my original package was debhelper :) [12:57] theme issue :) [12:57] sistpoty: cdbs was my part [12:57] you don't know yet ? [12:57] d'oh *g* [12:57] :) [12:58] ajmitch_: you seems busy, don't know if we can disturb you === ajmitch_ is busy [12:58] hehe === sistpoty is out for another cigarette... brb [01:08] ArmeBosse: ok I will start to upload in 5 minutes [01:09] ok [01:09] how many diffs ? [01:09] hmm few [01:09] copyright [01:09] than svn [01:09] or 2027 [01:10] svn [01:10] copyright, rules, config.template.php - I think that's all [01:10] have you commit your changes ? [01:10] not yet [01:10] k [01:10] btw my svn doesn't work... [01:11] lang you mean ? [01:11] I mean developer svn with my password [01:11] no - ubuntu package [01:12] 3 times same password like alioth === yosch [n=yosch@lns-bzn-55-82-255-182-222.adsl.proxad.net] has joined #ubuntu-motu [01:12] ArmeBosse: lang too === ogra_ibook [n=ogra@ubuntu/member/ogra] has joined #ubuntu-motu [01:13] ArmeBosse: aaah so I need to put my password 3 times :) ? [01:13] cool - good to know ;) [01:13] yes :) [01:14] key pairs are useful for such things sometimes ;) [01:14] in order to NOT put your password, 3 times [01:14] also [01:14] or just having a non-broken setup [01:15] mhm [01:15] hey raphink [01:15] hi sistpoty [01:15] I'm just passing through [01:15] ajmitch_: ? having to put in your password 3 times is a broken setup? [01:15] about to go to bed and ready through the REVU2 spec and classes ;) [01:15] raphink: great news :) [01:15] hi LaserJock [01:15] :) [01:15] ajmitch_: gforge issue no ? [01:16] LaserJock: if it's entering the same password 3 times in a row, then something is wrong [01:16] ArmeBosse: probably [01:16] Hi Laserjock <>< [01:16] good night [01:16] gn8 dholbach [01:16] night dholbach [01:16] hi sistpoty [01:16] hi dholbach [01:16] bye dholbach [01:16] bye dholbach [01:16] night guys - you rock! [01:16] hi raphink <>< [01:16] :) [01:17] ajmitch_: well, on svn.debian.org I have to do it at least twice because of ssh and svn [01:18] huhu [01:18] I thought that was common for svn+ssh [01:18] common with gforge [01:19] 3 or 4 ;) and probably 5 [01:19] hmm, that seems a bit excessive [01:20] hi ogra [01:20] hi ogra [01:20] hey [01:21] :)= [01:21] ArmeBosse: vtigercrm goes to revu === raphink loves the #ubuntu-motu chan [01:21] it's a nice place to be :) [01:21] raphink: revu tools are available on dapper ? or i must add universe repo ? [01:21] ArmeBosse: it's available in dapper universe [01:21] hello ogra [01:22] and you probably have to edit /usr/bin/revu-build and change PBUILDERNAME to "sudo pbuilder" [01:22] raphink: have you documented revu-tools? [01:22] ajmitch_: yes, on the wiki [01:22] raphink: I mean in the package [01:22] since people can use it offline [01:22] ajmitch_: https://wiki.ubuntu.com/MOTU/Packages/REVU/REVU-Tools [01:22] ajmitch_: oooh [01:23] ajmitch_: well there are short help messages with --help [01:23] raphink: since every binary/script must have a man page, right? ;) [01:23] and manuals [01:23] :) [01:23] and it wouldn't have been advocated without them, right? [01:23] man revu-{report, build, orig} [01:23] sure ;) [01:23] so is all the info on the wiki in the package? [01:23] revu-review doesn't have a manpage yet though. I forgot to make one, I will add it in 0.6 [01:24] not all of them no [01:24] the manpages are a bit more concise [01:24] ajmitch_: well, we weren't that strict on one or two missing manpages lately ;) [01:24] but they explain how to use the commands [01:25] sistpoty: I'm usually strict on manpages ;) [01:25] so I am to be with myself, too [01:25] raphink: I'm usually as well, though I did some uploads the last days w. missing manpages (if this was the only problem) [01:25] ajmitch_: you can have a look at the man pages for revu-{build,orig,report} [01:25] sistpoty: it depends on how far we allow standards to slip :) [01:26] sistpoty: hehe [01:26] we want the best stuff in [01:26] well, I guess I'll file bugs on the packages that are passed the new-queue... then we can see if the maintainer actually cares ;) [01:26] sistpoty: sure, including some of mine ;) [01:27] I didn't upload packages from you ajmitch_ ;) [01:28] oh... gmult is ready to go (but needs another advocacy)... http://revu.tauware.de/details.py?upid=2001 [01:28] I still have to fix up a number of bugs [01:29] ajmitch_: e.g. http://raphink.net/debian/mans/revu-report.html [01:31] ajmitch_: do you think that's clear enough? [01:31] raphink: maybe [01:31] maybe ;) [01:31] lol [01:31] ok [01:33] marcin`: something strange orig.tar.gz changed [01:35] config.php typo problem [01:35] heah, can a REVU admin nuke gaussum? [01:35] config.php where? [01:36] LaserJock: sure, why? [01:36] copyright line 1 no mail [01:36] which we provide [01:36] LaserJock: why should it be nuked? [01:36] raphink: I took the ITP over and got it into Debian and it is in the sync queue right now so that upload is obsolete [01:37] vtiger-crm in comments [01:37] LaserJock: ok [01:37] dirs no / needed at the en of path [01:38] rules: find $(WEBAPPDIR) -name "*.jpg" -perm /a+x -exec chmod a-x {} \; [01:38] raphink: that's the second email you sent :-) [01:39] no lintian warning about jpg ? [01:39] dont know need to build it [01:39] LaserJock: becoming a high-flying debian maintainer now, are we? :) [01:39] ajmitch_: heck yeah ;-) [01:39] LaserJock: it pays well? [01:40] re add version comment in sql file please [01:40] ajmitch_: actually it was much easier than I thought it would be. Especially for the package that I put on REVU and got uploaded to Universe first [01:40] ajmitch_: It took a whole 2 days to get somebody to upload it to NEW [01:40] that's pretty good [01:40] depends on the sponsor, though [01:41] some of us can be pretty slack [01:41] ChrisH [01:41] right [01:41] (2006 key) in your name is not needed [01:42] but with gausssum I took over the ITP for the guy and had to do some tweaking so it took a bit longer. So now I have 2 packages in Debian which I think is pretty awesome. [01:43] LaserJock: yes... I've got only two packages in ubuntu so far ;) === jsgotangco [n=jsg@210.4.38.43] has joined #ubuntu-motu [01:44] well, for the most part I really try to aviod packaging new programs from scratch. I feel like Universe needs enough work that I shouldn't spend all my time packaging new stuff. [01:44] but I appreciate those who do [01:45] LaserJock: the second email I sent ?? [01:45] marcin`: i confirm there's a change in orig.tar.gz [01:45] what are you talking about LaserJock ? [01:45] raphink: yeah, on the 15th you had an almost identical comment on gausssum [01:46] LaserJock: really? [01:46] yeah [01:46] oh yeah right [01:46] raphink: explain this.. [01:46] * Keep only one entry in debian/changelog till this package is released officially. [01:46] well I guess that shows it's just me ;) [01:46] ajmitch_: well there's no need to talk about the new upstream version since it was never released in Ubuntu yet [01:47] ajmitch_: so only 5.3 should be listed in the changelog imo [01:47] raphink: so? it's still fine to leave in that info [01:47] 5.2 having only been produced on revu [01:47] raphink: I'm just going to have to disagree with you [01:47] ajmitch_: not what I was told by other MOTUs when I was reviewed in the past ;) [01:47] ajmitch_: sure you can disagree :) [01:47] ArmeBosse: I'm not sure if I'll be able to sign this package if I'll remove (2006 key) [01:47] and I'm fine with having your point [01:47] raphink: sure, but I can still think you're wrong :) [01:48] hmm, I can see including previous upstream releases but I think it is nice if it doesn't go in a 0ubuntu30 or something [01:48] ajmitch_: some months ago, I was explained that it was better to only keep the entries for official releases in the changelog [01:48] marcin`: don't know too [01:48] so users don't begin to search for the other versions in the archives [01:48] if they were never released [01:49] how many users would know to look in a changelog & try & hunt down other versions? [01:49] it's not exactly going to be a common activity [01:49] ajmitch_: the point being that when I see a 0ubuntu5 in Ubuntu I expect there was a 0ubuntu{1-4} released before === iiping [n=iiping@203.84.186.198] has joined #ubuntu-motu [01:49] especially as released versions get removed from the archive as well [01:49] ajmitch_: I would [01:49] s/released/uploaded/ [01:49] developers would [01:49] and it's pretty useful to have reliable versionning for this reason === ajmitch_ sighs [01:50] hehe [01:50] when I'm hunting for bugs for example [01:50] and I see ina changelog `unstable` [01:50] working in MOTU just isn't fun like it used to be [01:50] I try to find tracks of the package in Debian [01:50] which seems logical [01:50] raphink: if there were multiple versions uploaded to dapper, only 1 will still be there [01:50] so you can't search through that history [01:51] unless someone released it as part of `unstable` unofficially, and there's no way to know where [01:51] ajmitch_: sure on LP I can [01:51] raphink: I can understand your point but you sacrifice having a true change log [01:51] if someone uploaded it to unstable, then it will be removed on a newer upload [01:51] and on changelogs.ubuntu.com too [01:51] thankfully [01:51] raphink: that package is still *gone* [01:51] LaserJock: depends how you see it' [01:51] removing info just because you like a cleaner changelog is still wrong, imho [01:52] not just because I like cleaner changelog ajmitch_ [01:52] but because a prerelease change is not a real change for users [01:52] I don't know why I bother === ajmitch_ goes back to work [01:53] ajmitch_: hehe ;) [01:53] actually I second ajmitch_'s opinion... [01:53] ajmitch_: don't get me wrong I get your point [01:53] maybe we should have an Ubuntu vacation when Dapper is released :-) [01:53] :) [01:53] though I don't think we should encourage ppl. to do a new version *only* for revu [01:53] LaserJock: hehe [01:53] (or rather disencourage them) [01:53] LaserJock: I'm having a long-term ubuntu vacation at the moment [01:53] LaserJock: and I've got no real incentive to finish it [01:53] ajmitch_: how long? still in AU [01:54] LaserJock: yes I'm still in .au, and I'll probably keep away from MOTU after that as well [01:55] lo guys can u tell me what ui can use gstreamer [01:55] iiping: what ui? [01:55]