19:03:49 #startmeeting 19:03:49 Meeting started Fri Jul 1 19:03:49 2011 UTC. The chair is MadameZou. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:03:49 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:04:01 #topic One day with Debian Perl Team 19:04:03 ok, hello and welcome everybody! 19:04:20 it's nice to see many new faces (well, nicknames) here and also some well-known ones 19:04:24 o/ 19:04:33 (the latter can probably help me a bit :)) 19:04:58 before I start to tell something about the group you might want to prepare a few things: 19:05:08 1) a large screen for many windows :) 19:05:26 2) if you want to try packaging we need to install at least dh-make-perl subversion devscripts quilt 19:05:49 3) if you install dh-make-perl please run dh-make-perl refresh-cache now (to save time later) 19:05:54 and an editor. 19:06:03 right, thanks 19:06:30 4) I'm termcasting one of my terminals so can just kick back and watch what I'M doing: 19:06:47 telnet termcast.org and choose the DayWithTheDebianPerlGroup channel there 19:07:17 (the termcast is done - surprise - with a perl module called App::Termcast, packaged as libapp-termcast-perl) 19:07:27 (cool!) 19:07:41 5) you may also want to join #debian-perl to see commit messages later, or just see what's going on there 19:08:04 ok, so much for the preparation 19:08:39 good. about me: you probably know that my name is gregor herrmann. I'm austrian, am a member of the debian perl group since 2006 and I'm a DD since 2008 19:09:26 I joined the group in a very typical way: I packaged a perl module, looked for a sponsor, and then gunnar wolf said "hey, why don't you join the team?" - and I'm still there :) 19:09:33 so, about this team: 19:09:52 what are we doing? we are packaging perl modules, usually from the CPAN, for debian 19:10:05 (not perl, the interpreter itself) 19:10:24 we are using alioth.debian.org for cooperation 19:10:27 some links: 19:10:38 #link http://wiki.debian.org/Teams/DebianPerlGroup - general overiew 19:10:55 #link http://wiki.debian.org/Teams/DebianPerlGroup/Welcome - why and how you would want to join 19:11:20 #link http://pkg-perl.alioth.debian.org - our homepage with docs, howtos and other stuff 19:11:29 ok, some numbers about the group: 19:11:44 at the beginning of the week the project had 179 members in alioth 19:12:03 that's alot. but there are people I've never seen in the last 5 years :) 19:12:18 during the last year 71 people made at least one commit to our svn repo 19:12:33 and in total there were 16814 in the last year 19:12:40 +commits 19:12:59 the number of packages we are maintaining is ~2000 at the moment 19:13:14 how can we manage so many packages? 19:13:47 1) they are similar, 2) most of them are simple, 3) most upstream authors are great, 4) we have nice tools 19:14:02 one especially nice tool is PET: 19:14:14 #link http://pkg-perl.alioth.debian.org/cgi-bin/pet.cgi - classical PET 19:14:36 #link http://pet.43-1.org/pkg-perl/pet.cgi - PET2 (with support for git and remote repos etc.) 19:15:07 PET(2) shows as what we need to work on: packages with bugs, with new upstream releases, ready for upload etc. 19:15:18 oh, I forget a final link to numbers: 19:15:41 #link http://pkg-perl.alioth.debian.org/docs/miniDebConf-paris2010/miniDebConf-paris2010.pdf - presentation by xoswald dodathome and me from last fall 19:16:18 alright, that was the introduction about the group. are there any questions so far before we get our hands dirty? 19:16:36 last spring for me, a am in the other hemisphere 19:16:51 raschipi: oops, sorry 19:17:26 everyone ready so far? tools installed, termcast running? 19:17:59 * pau4o is ready 19:18:13 which is size of your term, in chars? 19:18:23 * TetsuyO is ready too 19:18:32 ready 19:18:44 * MadameZou too 19:18:53 cubuanic: good question. no idea how awesome and urxvt would tell me. it's the quarter of my screen :) 19:19:10 gregoa: stty size 19:19:25 hi mxey 19:19:26 ok, I though to show how to create a package from scratch, which involves the BTS, dh-make-perl and subversion 19:19:28 echo $COLUMNS $LINES 19:19:34 mxey: thanks! 37 119 19:19:41 ok, thx 19:19:50 * cubuanic ready 19:19:55 * gregoa learns something new every day in debian :) 19:20:14 question one: which package? let's take one where there is an RFP (request for packaging) bug 19:20:38 we can get thme from http://bugs.debian.org/wnpp (slow), http://www.debian.org/devel/wnpp/ or http://pkg-perl.alioth.debian.org/qa/wnpp.html 19:20:45 * zobel looks for a hard one :) 19:20:48 the last one only lists lib.*-perl packages 19:20:55 zobel: I have already chosen one :) 19:21:18 and the one is http://bugs.debian.org/564106 Template::Plugin::Gravatar 19:21:44 as a first step I will now tell the BTS and the rest of the world them I'm going to package it 19:22:12 with the bts utility: 19:22:18 bts retitle 564106 "ITP: Template::Plugin::Gravatar - configurable TT2-based generation of Gravatar URLs from email addresses" . owner it \! 19:22:24 (from devscripts) 19:22:43 an alternative would be to send a plain mail to control@bugs.debian.org with the commands 19:22:55 and now: let's see dh-make-perl at work: 19:23:07 dh-make-perl --pkg-perl --source-format "3.0 (quilt)" --dh 8 --closes 564106 --cpan Template::Plugin::Gravatar 19:23:26 I hope it works for others too with a different machine than mine 19:23:33 will it works some info: 19:23:44 dh-make-perl will make a draft package for us. 19:23:58 --pkg-perl set the maintainer to the debian perl group and some other things 19:24:30 --source-format and --dh tell something about the way we want the package (as source formart "3.0 (quilt)" and using debhelper 8 19:24:44 the closses will add the bug number to the change log 19:25:11 and "--cpan Template::Plugin::Gravatar" says: grab the Template::Plugin::Gravatar tarball from the CPAN, unpack it and make-me-a-package 19:25:50 in my right terminal I see that dh-make-perl has finished its work. what's the status for others? 19:26:01 done 19:26:06 \o/ 19:26:14 (and it's so cool!) 19:26:20 gregoa: we have a question 19:26:26 any problems? ah yes 19:26:40 < zobel> question: is dh-make-perl is scaning for already existing RFP and/or packages in sid/NEW? 19:27:14 zobel: good question. I _think_ so but I'm not 100% sure 19:27:20 dam: ^^ do you know? 19:27:51 er, I think too. will check and answer in a minute? 19:27:59 dam: perfect, thanks! 19:28:05 in the meanwhile we have another question :) 19:28:14 (have I mentioned the advantages of teamwork? :)) 19:28:16 < zobel> question: is there a difference between /home/gregoa/.dh-make-perl/rules.dh7.tiny and the default one? 19:28:46 zobel: it's a symlink and most probably completley unnedded, and cruft from old times :) 19:29:08 ah. thx. i was just wondering about that file. 19:29:24 (a symlink to the version in svn but that's the same as the one in the package) 19:29:27 good catch :) 19:29:39 alright. shall we look at the files? 19:30:03 no more questions open 19:30:07 so now we have a Template-Plugin-Gravatar-0.05 directory with upstream code and the created debian dir 19:30:10 zobel: thanks 19:30:39 in the debian dir we have what we would expect there :) I'll quickly go through them: 19:31:08 debian/watch contains our default regexp for downloading upstream tarballs from the CPAN. no need to change 19:31:32 debian/source/format is 3.0 (quilt) as we told dh-make-perl. fine 19:32:01 debian/rules is the short-style 3-line dh variant we always use. no need to change something, at least now 19:32:26 debian/libtemplate-plugin-gravatar-perl.docs contains the README which dh-make-perl detected. 19:32:31 let's read it 19:32:57 it's almost empty, no value for users, so we rm debian/libtemplate-plugin-gravatar-perl.docs 19:33:25 debian/compat - debhelper compatibility level 8, as we told dh-make-perl. good. 19:33:39 that leaves us with debian/copyright and debian/control. let's start with copyright. 19:34:00 here we see some boilerplate at the top 19:34:16 then we have to check if the rest is accurate. 19:34:32 we can use `licensecheck' from devscripts or a simple grep: 19:35:12 "grep -ir copyright ." show info in ./lib/Template/Plugin/Gravatar.pm and inc/Module/* 19:35:39 so we inspect ./lib/Template/Plugin/Gravatar.pm closer and find "Copyright 2007, Ashley Pond V." and "same terms as perl" 19:36:08 compared to our d/copyright the year is missing but the rest is fine 19:36:18 and then we need to add info about inc/M/I 19:36:54 since Module::Install fragments are included often we can copy the relevant lines from http://pkg-perl.alioth.debian.org/copyright.html#module__install 19:36:56 gregoa: you might want to nuke that dot at the end of the first copyright line 19:37:05 (perl hackers and packagers are lazy) 19:37:09 mxey: right, thanks! 19:37:49 so this should be fine 19:38:10 http://paste.debian.net/121622/ 19:38:20 ok, on to debian/control 19:39:07 we find a section for the source and a section for the binary package, both filled with info from dh-maker-perl as we told it or as it found in the upstream source 19:39:24 again debhelper 8, correct maintainer and Uploaders, URLs, ... 19:39:39 the Standards-Version is wrong, the current one is 3.9.2 19:39:45 (we should update dh-make-perl :)) 19:40:14 how about libtemplate-perl (>= 2)? let's check with rmadison which versions we have in the archive 19:40:41 ok, even etch has 2.14-1 so we can remove the "(>= 2)" 19:41:04 in Build-Depends-Indep and in Depends 19:41:23 we can double-check in META.yml and Makefile.PL 19:41:42 should be ok :) 19:41:53 the last thing before we can build the package is the description 19:42:00 we can remove the boilerplate at the end 19:42:33 and then short and long description really need some work :) 19:42:49 gregoa: could you please go slower on the terminal? I can't follow irssi and your terminal very well :) 19:43:14 MadameZou: I have the same problem with typing in two terminals :) 19:43:17 ok i try 19:43:25 thanks :D 19:43:41 MadameZou: thanks , I was having same problem :P 19:44:38 ok, I stop typing in debian/control and wait for comments/proposals for the short and long descriptions :) 19:45:13 uhm, I think you have lost the "T" of Template 19:45:29 where? 19:45:46 bemplate::... 19:45:47 where you have the cursor, the last line first char 19:46:00 4th line under description 19:46:27 I see it here. will pastebin 19:46:33 http://paste.debian.net/121626/ 19:46:48 (btw: this nopaste is also perl: libapp-nopaste-perl :)) 19:47:13 :) 19:47:29 is there still an error I'm missing? 19:47:38 yes, you're right: you have it 19:47:39 in the pause, here's an answer to zobel's question: (1) dh-make-perl warns if the prospective package is already known to APT. (2) it adds Closes: #xxxxx if the package is found in WNPP, but it seems it doesn't warn you that you need to take the ITP and such (iow, it is just an automatic --closes option) 19:47:50 probably some refreshing problem on my terminal..? 19:47:59 true 19:48:02 dam: thanks! 19:48:07 ok, then let's keep it 19:48:12 gregoa: some questions here 19:48:19 go! 19:48:44 < pabs> question: how is the relationship between pkg-perl and upstream (CPAN/etc)? 19:49:19 pabs: "good", or do you have anything specific in mind? 19:49:40 < pabs> question: what QA tools are there for CPAN authors and Debian folks packaging and thus doing QA on Perl modules? 19:49:50 dam: thx 19:49:55 MadameZou: I have refreshing problem in my terminal too 19:50:09 gregoa: are they happy with modules being redistributed in Debian? 19:50:27 it is fantastic when CPAN authors come to #debian-perl and ask "Hey, how can I make your job easier?" 19:50:30 * pabs thinking of the Ruby situation there 19:51:07 pabs: for CPAN authors there are not many debian-specific tools, there's something on our website for them to search, there's some kwalitee test, and there are lots of ideas from improving :) 19:51:29 pabs: we also have CPAN authors joining the team, and usually the cooperation is very cordial 19:52:14 pabs: also the perl packagagers (niko and dom) also seek input from perl5porters etc. before changes and receive very considerate mails 19:52:44 the CPAN community is really one of the nice things in doing this work 19:52:53 ok, shall we go on with our package? 19:53:13 the last file is debian/changelog, and we can also leave it. 19:53:14 y 19:53:19 now, let's build it 19:53:36 nack. unstable! 19:53:43 usually I build everything in cowbuilder but that's to complicated for now 19:53:51 we don't like UNRELEASED! :) 19:53:56 zobel: the UNRELEASED is un purpose for now 19:54:02 okay 19:54:15 gregoa: pointer for cowbuilder? 19:54:21 zobel: I leave it before injecting into svn, then look again, and only set it to unstable when uploading 19:54:33 zobel: otherwise PET would show it as ready for upload 19:54:34 apt-zobel@kvasir:~% apt-cache search cowbuilder 19:54:34 cowbuilder - pbuilder running on cowdancer 19:54:40 fsfs: ^ 19:54:51 fsfs: pbuilder has a good documentation in the package and on the web 19:55:08 fsfs: and there's something in the ubuntu wiki that describes it step by step 19:55:14 (not sure about the debian wiki) 19:55:17 gregoa: can you `clear` your terminal (I see lot of mixed lines here) 19:55:24 pau4o: better? 19:55:33 yes 19:55:42 ok, so no cowubuiler but plain dpkg-buildpackage 19:55:55 hello all 19:56:05 i'm late 19:56:08 oh, what we need is a tarball. we can search it somewhere under ~/.cpan or just use uscan 19:56:20 uscan -verbose 19:56:25 not enough :) 19:56:32 uscan -verbose -force 19:56:37 now we have it in ../ 19:57:01 ok: dpkg-buildpackage -uc -us 19:57:20 termcasting is really quite cool. 19:57:25 if you get warnings about missing packages you need to install them (probably libtemplate-perl) 19:57:51 mxey: I'm glad you like it :) # never used it before 19:58:05 (sugar: telnet termcast.org and choose A day with debian perl team) 19:58:19 ok, so I have a package now in ../ 19:58:22 how about others? 19:58:45 i guess we should fix problems found by tests? :) 19:58:48 I have package too 19:58:55 I'm installing libtemplate-perl, and then I think I'll have a package,too :-) 19:59:15 zobel: we should, but I don't have any. what do you get? 19:59:43 * TetsuyO has a package 19:59:55 gregoa: i don't have any, but during the last BSP, i had a package to NMU which had quite a lot errors in tests/ 20:00:15 not maintained by the perl group 20:00:18 zobel: ah ok. 20:00:47 * gregoa just noticed to missing build dependencies for t/pod* but we keep that for later) 20:01:07 good. pabs already asked about QA - so as usual in debian we will run lintian against the .changes 20:01:25 lintian -i -I --show-overrides --pedantic --color auto ../libtemplate-plugin-gravatar-perl_0.05-1_i386.changes 20:01:36 (these are my preferred lintian options) 20:01:51 no output here! yeah! 20:02:00 \o/ 20:02:07 (maybe I should have mentioned lintian earlier *cough*) 20:02:44 good. so far the shiny new package is only on several hard disks in several hemispheres and timezones, but it belongs in our svn repository 20:03:13 here I'm using svn-inject, and I'm afraid you can only watch the termcast (and the commits in #debian-perl) 20:04:11 svn-inject is in the svn-buildpackage package, together with svn-buildpackage and svn-upgrade 20:04:32 -inject: first time, -upgrade: new upstream versions, -buildpackage: build from svn checkout 20:04:48 and done 20:04:59 now I will change into my "normal" pkg-perl repo 20:05:11 and get the package again 20:05:45 for those not having our trunk checkout it yet: don't do it now :) 20:05:52 but you can "svn co svn://svn.debian.org/pkg-perl/trunk/libtemplate-plugin-gravatar-perl/" 20:06:38 ok, looking at the clock I see that we are already a bit late. 20:06:49 actually I wanted to finish + upload this package 20:07:02 then show you how to upgrade another package and forward a patch upstream 20:07:07 and then have a discussion 20:07:26 but I guess this will last until tomorrow (CEST) :)) 20:07:43 we could easily have a second-part session :) 20:07:43 MadameZou, everybody: how's the energy, what are the interests, how shall we proceed? 20:07:52 gregoa: gogogo! 20:08:05 :) 20:08:16 I'm awake , go :) 20:08:23 * MadameZou also is for going at least for another hour 20:08:28 gregoa: go ahead 20:08:38 But what thinks people in other timezones? 20:08:41 $one_hour++ 20:08:43 * TetsuyO it's ok also for me gregoa 20:09:08 oing on for next few hours (evn to morning (CEST)) 20:09:20 * darkestkhan has no problems with g 20:09:52 ok, thanks :) 20:10:06 \o/ 20:10:15 maybe we leave this package at this state now - it's almost done anyway :) 20:10:36 * msantana +1 20:10:48 if you want to join the team that's what you do: look for an RFP bug or file an ITP bug, create a package and svn-inject it 20:11:19 of course then a final check is needed, building in a chroot, and then, as zobel noticed, setting the distribution from UNRELEASED to unstable 20:11:39 and it will show up on PET, some DD will see it in the "ready for upload" section, will review it and either upload it 20:11:56 or add TODO items into debian/changelog and set it back to UNRELEASED 20:12:09 gregoa: < fsfs> is it possible to see the termcast again later, is it logged? 20:12:18 that's our workflow, besides mail (debian-perl@lists.debian.org) and IRC, of course 20:12:50 fsfs: I have no idea, but I don't think so. I'm only using this termcast.org service, maybe ther's something on their website? 20:13:02 good 20:13:26 actually creating new packages is not so "everday work" - after all we already have enough packages :) 20:13:42 really everyday is upgrading to new upstream releases 20:13:58 I guess we have ~5 new upstream vesions per day 20:14:09 so let's take one of them: libpoe-component-client-keepalive-perl 20:14:30 if you want to follow along I suggest that you check it out from svn: 20:14:39 svn co svn://svn.debian.org/pkg-perl/trunk/libpoe-component-client-keepalive-perl/ 20:14:54 fsfs: but the IRC log will be available afterwards 20:15:01 one question: how do you look up for new upstream versions? 20:15:11 darkestkhan: PET again :) 20:15:40 darkestkhan: http://pkg-perl.alioth.debian.org/cgi-bin/pet.cgi -> "Newer upstream release vailable" 20:15:54 it uses the info from debian/watch in svn 20:16:03 but we will check manually now with uscan: 20:16:13 uscan -verbose -report 20:16:31 ok, uscan agrees with PET. 20:17:14 now I use svn-upgrade, which has a nice --uscan switch. it grabs the tarball, throws the contents into svn (/branches/upstream/package) and merges it into trunk 20:18:01 (again, KGB announces the commits in #debian-perl) 20:18:06 and finished 20:18:29 so now I have in my working copy the new version (not yet on the server) 20:18:39 and I will check the changes with svn diff 20:19:15 right at the top we see new requirements. I copy them to a "scratchpad" 20:19:57 ok, the rest of the small diff looks innocent 20:20:13 so I can commit it to trunk 20:20:37 either "svn ci -m 'some message'" or the next nice tool: debcommit (also in devscripts, so not perl specific) 20:20:53 debcommit commits and takes the diff of debian/changelog as the commit message 20:20:54 gregoa: please `clear` again 20:21:22 pau4o: done, hope it works 20:21:47 all you have checked out the package from svn before can now "svn up" and have again the same files as I have here 20:21:49 yep, I think editor that you use messes with termcasting 20:22:14 pau4o: yup, sounds reasonable. unfortunately sometimes I need to edit something despite all the tools :) 20:22:29 ok, so we can again look around in the package 20:23:20 doesn't look bad (I've chosen a package that was upgraded not long ago :)) 20:23:34 we noticed that some requirements changed, so let's look into d/control 20:24:25 and adjust them: libpoe-perl (>= 2:1.2990) -> 2:1.3110 20:24:39 and for libpoe-component-resolver-perl we need rmadison again 20:25:06 rmadison does run dak ls on ries via cgi 20:25:25 "dak ls $package-name" 20:25:27 and - bummer - upstream wants 0.912 but debian only has 0.911. so need to update this package before 20:25:36 zobel: isn't it using UDD in the meantime? 20:25:45 might be 20:25:46 ok, I change the version in d/control anyway 20:26:15 or better: I add it as (>= 0.912) 20:26:21 then the next PET trick: 20:27:04 I open d/changelog and add "WAITS-FOR: libpoe-component-resolver-perl 0.912" 20:27:17 that way PET puts into it's own section 20:27:23 and a changelog entry would also be nice 20:27:32 'debian' => "http://qa.debian.org/madison.php", 20:27:53 (I thought that was a redirect to some udd.cgi now) 20:28:47 ok, summary: versions in d/control updated, changelog entry and WAITS-FOR in d/changelog for PET 20:28:52 so: commit again 20:29:16 and those of you who have it can "svn up" again 20:29:31 and we can't finish this package now because of the dependency 20:29:42 but I chose it for another reason anyway: there's a patch! 20:29:57 in debian/patches/ we have fix-pod-whatis.patch 20:29:58 gregoa: you are right, the php redirects to a cgi, which uses UDD 20:30:12 zobel: ok, thanks for checking! 20:30:36 if we look at the patch: it fixes a problem in the POD (embedded documentation) 20:31:01 it has nice headers according to DEP3 20:31:03 #link http://dep.debian.net/deps/dep3/ 20:31:14 and what do we see there: "Forwarded: no" 20:31:27 not good. we should forward it upstream of course! 20:31:36 and that's what I wanted to show actually :) 20:32:02 CPAN modules (almost always) use the CPAN request tracker, so we can just go their. 20:32:15 we can use the URL from debian/control or debian/watcg (it#s the same) 20:32:27 http://search.cpan.org/dist/POE-Component-Client-Keepalive/ 20:32:49 and there we have a link "view/report bugs" 20:32:58 https://rt.cpan.org/Public/Dist/Display.html?Name=POE-Component-Client-Keepalive 20:33:20 check: is our patch there or a similar bug report? no 20:33:27 so we need to file one 20:33:48 we can click on "report a new bug" 20:33:53 https://rt.cpan.org/Public/Bug/Report.html?Queue=POE-Component-Client-Keepalive 20:34:04 #idea: update rmadison to use the cgi directly (zobel) 20:34:15 which explains the procedure: either log in or use email 20:34:36 I will now just write an email to Component-Client-Keepalive [at] rt.cpan.org 20:35:19 gregoa: we want to refresh the patch first? 20:35:37 carnil: just my idea when I started typing the mail :) 20:35:39 carnil: grazie! 20:35:57 ok, let's see if it applies 20:36:01 with quilt: 20:36:16 quilt push 20:36:21 WAHH it fails 20:36:31 do I have to fix a patch now? that was not planned :) 20:37:25 ok, done :) 20:37:49 (sorry this was a bit quick. quilt would also be a nice topic for a tutorial) 20:38:17 svn diff --> the patch looks the same except for the version. good. nothing broken. back to the mail. 20:38:42 eheh 20:38:54 ok, mail sent 20:38:55 LOL @ remember your attachments! 20:39:02 CPAN RT is very quick so ... 20:39:43 not today. it should show up on https://rt.cpan.org/Public/Dist/Display.html?Name=POE-Component-Client-Keepalive 20:40:28 ok, what's missing now is: update the headers in the patch 20:40:29 vorfuehreffekt?! :) 20:40:39 zobel: ganz genau :) 20:40:48 usually new reports are really there after the next refresh 20:41:27 oh, mail bounce, sec 20:42:02 hm, seems I got the address wrong 20:42:26 should have been bug-POE-Component-Client-Keepalive [at] rt.cpan.org. 20:43:04 ok, bounced again, maybe I have more luck now :) 20:43:13 (that's what you get for live action :)) 20:43:32 gregoa: it's there now 20:43:33 now it's there: https://rt.cpan.org/Public/Bug/Display.html?id=69235 20:44:24 good, patch header updated, now: changelog and commit 20:44:43 next tool: dch (debchange) for editing the changelog, again in devscripts 20:45:04 last check with svn diff 20:45:19 and debcommit again 20:45:23 Forwarded: no? 20:45:46 dam: thanks! oops. 20:46:29 that's how interesting commit messages are created :) 20:46:39 ok, I think we can leave this package now. 20:46:52 we've seen svn-upgrade, a few changes, and the forwarding of a patch 20:47:00 gregoa: question for you 20:47:03 now it waits for this other libpoe-something dependency 20:47:10 MadameZou: yes please 20:47:10 < zobel> question: gregoa, can you tell us what to take care of 20:47:10 when moving a package from single maintainer to 20:47:10 pkg-perl? 20:47:13 ooops 20:47:55 gregoa: you may answer that at the end of your lecture. 20:48:01 zobel: follow the written and unwritten rules; the first part is easy: http://pkg-perl.alioth.debian.org/policy.html 20:48:24 zobel: the second part is more "look at other packages" or "ask for a review" 20:48:52 zobel: we also have a takeover script in svn (in the scripts directory) that changes maintainer, svn-injects the package etc. 20:49:26 zobel, MadameZou: I think we can open the Q&A part; at least it's late enough and I'm starting to make too many mistakes in packaging :) 20:50:11 gregoa: feel free to hijack my -perl packages :) 20:50:24 gregoa: ok 20:50:41 zobel: :) - if you really want to get rid of them please send a short mail to debian-perl@ldo so it doesn't get lost 20:51:04 < pabs> question: in other language communities, rapidly changing APIs are the norm, does the CPAN/Perl community have a similar issue? 20:51:57 * dam was going to echo that too :) 20:52:04 pabs: I'd say no. major upgrades of perl itself cause some work, but the perl 5.12 upgrade some weeks ago went rather smooth despite ~400 binNMUs 20:52:54 pabs: sometimes an important packages changes an interface or has another incompatible change, but that's rare (and usually more an upstream issue than ours) 20:53:05 [B[B[B[B[B[B[B[B[B[B[B[B[B[D[D[D[D[D[D[D[D[D[D[D 20:53:24 oops, braindead parts here 20:53:29 gregoa: followup, are there any tools to watch for API compat issues? like abi-compliance-checker for C libraries? 20:53:34 I think he meant Foo::Bar changing itsAPI with each release 20:53:41 yup 20:54:00 no, I can't remember such nasty modules. dam? carnil? 20:54:25 gregoa: done :) 20:54:33 and I don't know a checker for that. maybe someone else? 20:54:38 zobel: danke! 20:54:48 er, there was a package I ITP-ed recently which failed to build with the current version of one of its dependencies. Both were in 0.0x versions, though 20:55:19 ack, that's not "changing in each release" :) 20:55:38 <@MadameZou> QUESTION (for the end of the session): Where are the sources of PET2? How it works? 20:55:45 yes. I was really surprised too :) 20:55:58 * MadameZou is quite intrigued by PET2 20:56:06 darkest magic :) 20:56:09 PET and PET2 sources are also on alioth, in a separate project 20:56:14 dam LOL 20:56:14 let me get some URLs 20:56:36 PET is in svn: svn+ssh://svn.debian.org/svn/pet/trunk 20:56:48 #link! 20:56:53 gregoa: are there recommended tools for packaging with GIT instead of SVN 20:56:58 PET2 is in git: git+ssh://git.debian.org/git/pet/pet2.git 20:57:09