[03:18] <jono> going through http://women.debian.org/wiki/English/PackagingTutorial
[03:19] <superm1> jono out of curiosity, why following women.debian.org?
[03:19] <jono> superm1: there is the packaging tutorial there
[03:19] <jono> but dh_make seems to not generate a debian directory for me
[03:19] <superm1> we have one at our wiki too
[03:19] <superm1> !packagingguide
[03:19] <ubotu> The packaging guide is at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html - See https://wiki.ubuntu.com/MOTU/Packages/New for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/DeveloperResources - See also !backports
[03:20] <tgm4883_laptop> jono was trying to pick up chicks
[03:20] <jono> ok will start there
[03:21] <tonyyarusso> jono: whatcha packaging?
[03:21] <azeem> jono: does dh_make spew out an error, or just doesn't create debian/
[03:21] <jono> tell you what, I will look at the packaging guide first
[03:21] <jono> tonyyarusso: just want to learn how to package
[03:22] <tonyyarusso> ah
[05:08] <Hobbsee> hmmm, no life
[05:09] <Hobbsee> !uvf
[05:09] <ubotu> uvf is Upstream Version Freeze.  For an exception, see https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6
[05:51] <white> Hobbsee: bored? :)
[05:51] <Hobbsee> white: not overly.  was going to see whether the world had blown up, etc
[06:11] <ScottK> gouki: Yes, but there are easier bits you can start with.  It doesn't have to be all tricky stuff.  Start with bugs tagged packaging bitesize.
[12:30] <DarkSun88> Hi all
[12:33] <simu> looking for reviews of my package on REU
[12:33] <simu> *REVU*
[01:06] <white> simu: i am not so sure about REVU procedures, but wouldn't it help the reviewers, when you give them your package name?
[01:07] <geser> white: currently you have a 50% chance to review the right package :)
[01:07] <geser> it's rotoscope
[01:07] <simu> white: its calles rotoscope
[01:07] <simu> called
[01:08] <simu> geser: lol correct ;-
[01:10] <simu> currently I'm the guy who builds half of the packages
[01:11] <white> geser: out of curiousity, did the community decide, if they want to have the servers at canonical or not?
[01:13] <geser> white: I don't know what's planned with REVU in the future. Currently it is on one of the community machines for ubuntu-devs.
[01:15] <white> does every MOTU have an account on the normal devel machines?
[01:15] <white> or is it restricted to the core devs?
[01:15] <Fujitsu> white: Only Canonical employees have accounts on Canonical machines.
[01:16] <white> Fujitsu: weren't the compromised machines community ran?
[01:16] <Fujitsu> There are a few community systems around, with *.ubuntuwire.com accessible to all ubuntu-dev members.
[01:16] <white> so *.ubuntu.com is canonical only?
[01:16] <Fujitsu> white: They're not really Canonical machines, and they're more for LoCo teams.
[01:16] <Fujitsu> Pretty much, yes.
[01:16] <white> ah ok
[01:54] <sistpoty> hi folks
[01:57] <Fujitsu> Hi sistpoty.
[01:57] <sistpoty> hi Fujitsu
[03:24] <Lamego> anyone on gutsy right now ?
[03:25] <ScottK> Lots of people.  Yes.
[03:25] <Lamego> ok
[03:25] <Lamego> could you test the unsermake package ?
[03:25] <ScottK> Not me anymore unfortunately as my Gutsy hard drive died on Friday.
[03:25] <Lamego> before I create a bug report, I would like to be sure it is not fixed on the gutsy version
[03:25] <ScottK> Sorry.
[03:25] <Lamego> ok :(
[03:26] <Lamego> I am getting a "ImportError: No module named cPickle" on Feisty
[03:26] <nixternal> I removed unsermake so I can't test it either
[03:27] <Lamego> ok, found the issue, it depends on python-2.4, but it is not set as a depend
[03:27] <nixternal> that error looks familiar
[03:28] <geser> I tried importing the module in python2.5 and a python2.4 shell and it worked both times
[03:28] <Lamego> well, i just tried running the "unsermake" command
[03:28] <Lamego> without python2.4
[03:28] <Lamego> it fails
[03:29] <Lamego> brb
[03:31] <geser> Lamego: can you try if importing cPickle in a python shell also fails?
[03:31] <sistpoty> wohoo, I'm doing some huge data mining to rebuild revu's account database right now :)
[03:31] <geser> Lamego: according to packages.u.c it should be included in the pyhton2.5 package
[03:31] <Lamego> it does not fail, importing from the shell
[03:33] <Lamego> checking /usr/bin/unsermake
[03:33] <Lamego> exec python2.4 -c "import $mod; $mod.main()" --modules $mods "$@"
[03:34] <geser> Lamego: running unsermake in a gutsy pbuilder gives only "no file Makefile present"
[03:53] <Lamego> well, I am using a feisty dchroot
[03:53] <Lamego> geser, can you check /usr/bin/unsermake ?
[03:54] <Lamego> the feisty version script contains: mods=/usr/lib/python2.4/site-packages/unsermake
[03:55] <geser> still the same
[03:56] <geser> it still references python2.4 in the script
[04:00] <Lamego> ah found it, https://bugs.launchpad.net/ubuntu/+source/unsermake/+bug/107822
[04:00] <ubotu> Launchpad bug 107822 in unsermake "unsermake requires python2.4 which is not listed as dependency" [Medium,In progress] 
[04:05] <zorglu_> q. im trying to build a .deb for vlc 0.9, and the .diff from 0.8.9 pacakge no more apply. any suggestion on how i can fix this ? the 3500 line .diff seems hard to edit :)
[04:11] <CyberSDF> Hello all !
[04:14] <CyberSDF> I'm a Geany user (http://geany.uvena.de/) and i would like if it possible for someone in MOTU to update the version of this packages from 0.10.2 (actually in universe) to 0.11 ?
[04:14] <Lamego> Zombie, recreate it from scratch :) ?
[04:19] <norsetto> CyberSDF: geany 0.11.2 will be available in gutsy
[04:22] <tobiasschulz> Can someone check http://revu.tauware.de/details.py?upid=13 ?
[04:22] <tobiasschulz> And perhaps advocate?
[04:25] <CyberSDF> norsetto, not in feisty? Some bugs in 0.10 are tedious
[04:25] <ScottK> CyberSDF: Are any of these bugs ones that cause a crash or data loss?
[04:25] <Lamego> CyberSDF, current versions updates policy is restricted to security or serious bug fixes
[04:27] <CyberSDF> No bugs are not serious nothing impacting security or stability
[04:27] <ScottK> CyberSDF: Then you can request a feisty-backport.
[04:28] <ScottK> !backports
[04:28] <Lamego> CyberSDF, you can find geanius 0.11 at non official sources, use are your own risk :P
[04:28] <ubotu> If new updated Ubuntu packages are built for an application, then they go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[04:28] <ScottK> Doing a backport of the Gutsy package is safer than trying to install the upstream stuff yourself.
[04:30] <CyberSDF> ScottK, yes i'll do that
[04:30] <ScottK> OK.
[04:30] <CyberSDF> Thanks all :)
[04:30] <ScottK> You're welcome.
[04:30] <Lamego> CyberSDF, http://www.getdeb.net/app.php?name=Geany <- is is backported
[04:30] <tobiasschulz> May a MOTU please check my package? http://revu.tauware.de/details.py?upid=13
[04:35] <ScottK> Lamego: Please do NOT recommend people install stuff from random external sources.  That is NOT an Ubuntu backport.
[04:36] <ScottK> CyberSDF: I recommend you ignore Lamego's last suggestion.
[04:36] <CyberSDF> getdeb packages are not safe ?
[04:36] <Lamego> ScottK, have you checked the build diff ?
[04:36] <ScottK> Lamego: Just so you know, the person that runs getdeb was invited to work with us to get his packages into Ubuntu.
[04:36] <Lamego> or are just picking the usual "we are the only best and secure" source of software ?
[04:37] <ScottK> His response was that it was to much work to make his packages meet Ubuntu quality standards.
[04:37] <ScottK> No.  I haven't checked this particular package, but it was the getdeb people that said they would not make their packages meet our quality standards.
[04:37] <Lamego> ScottK, I am that person, I have created that package, and it has safe as compiling from the source, if you are not a developer and have no skills to check the source by yourself
[04:37] <ScottK> We have a backports process and it's not that har.
[04:38] <Lamego> but ok, this is motu, CyberSDF please ignore me
[04:38] <ScottK> har/hard
[04:38] <ScottK> Lamego: Then why don't you get your stuff into the Ubuntu repos rather than duplicate effort elsewhere?
[04:39] <ScottK> Backports testing also requires no packaging skills and is a part of the Ubuntu process.
[04:39] <Lamego> ScottK, I already reply that several times, I am sure you can answer that yourself from the recent mails on the MOTU ML :)
[04:39] <Lamego> anyway, lets keep on,  I will not recall getdeb urls into -motu, again
[04:40] <sistpoty> most revu accounts are back, passwords recreated. the login is whatevery your email address was in your last upload to gutsy
[04:40] <ScottK> Lamego: I would really like to see you try and work with us to get your work into the Ubuntu repos.
[04:41] <sistpoty> please don't nuke packages yet, the script to do so most probably won't work ;)
[04:42] <Lamego> ScottK, I am working for "current" users, not for "future" users, we have different goals, it is not duplicate work
[04:43] <ScottK> Lamego: Gutsy + Backports = Current users.
[04:43] <Lamego> there is a lot of users which can find getdeb, under stand it, but not backports
[04:44] <Lamego> backports are still driven by "ubuntu+1" not "current" for apps versions
[04:44] <ScottK> Well Ubuntu+1 strives to be current.  If you are packaging stuff that's not in Ubuntu yet, then you are doing work away from Ubuntu that would benifit the community more if it were done here.
[04:46] <ScottK> You've made the choice not to do that.  It's your choice.
[04:46] <Lamego> ScottK, Ubuntu is the community which I belong to, so, getdeb is ubuntu :)
[04:46] <ScottK> Lamego: From your perspective I'm sure that's true.  From mine, it's not.
[04:47] <ScottK> If your packages break systems (not saying they do), it's not an Ubuntu problem.  It's a getdeb problem.
[04:47] <Lamego> ScottK, Your comments look a lot like those Debian fans during Ubuntu's birth :)
[04:47] <zorglu_> q. im trying to build a .deb for vlc 0.9, and the .diff from 0.8.9 pacakge no more apply. any suggestion on how i can fix this ? it ends with "1 out of 1 hunk FAILED -- rejects in file modules/misc/freetype.c  Patch 020_dejavu_font.diff does not apply (enforce with -f))
[04:48] <Lamego> ScottK, sure, that is why they are tagged "~getdeb~" so that they can be pointed and fixed by us
[04:48] <ScottK> Lamego: That's a responsible approach.
[04:49] <ScottK> zorglu_: You have to look at that patch and figure out why it didn't apply.
[04:49] <zorglu_> ScottK: that patch is a 3500line diff...
[04:49] <ScottK> Lamego: From Debian's perspective I would agree BTW.  If we break something in Ubuntu, it's not Debian's problem.
[04:49] <Lamego> don't worry, the universe is big enough both for the masters and the apprentices ;)
[04:50] <zorglu_> ScottK: is there any tool for that ? or you guy really handle 3500line diff ?
[04:50] <ScottK> zorglu_: I certainly wouldn't.
[04:50] <Lamego> Zombie, most of that diif may contain patches which were already applied upstream
[04:50] <zorglu_> ScottK: good because im not enclined to either :)
[04:50] <Lamego> ops, i meant zorglu_
[04:50] <ScottK> zorglu_: There is something, I think called rediff.
[04:51] <zorglu_> ok looking for rediff
[04:52] <zorglu_> Lamego: ok.. not sure i understand what you mean tho. im not used to packaging, i got vlc svn compiled, just trying to get the .deb for feisty, based on the .deb from 0.8.9
[04:52] <zorglu_> upgrade :)
[04:52] <xhaker> Lamego, you should come by #ubuntu-pt and register on launchpad on the team
[04:53] <ScottK> Lamego: Bug #124933 is an example of what I think should be avoided.  Have you tried to get this package into Ubuntu?
[04:53] <ubotu> Launchpad bug 124933 in Ubuntu "[needs-packaging]  flock" [Wishlist,New]  https://launchpad.net/bugs/124933
[04:54] <ScottK> Bug #94896 too.
[04:54] <ubotu> Launchpad bug 94896 in Ubuntu "[needs-packaging]  BASIC-256" [Wishlist,Confirmed]  https://launchpad.net/bugs/94896
[04:54] <Lamego> ScottK, no, that was one of the few binary builds, and which may have legal issues, or not
[04:55] <Lamego> but because I am not a lawyer and don't have the time or will to research on it it will be kept until someone complains about it :)
[04:56] <ScottK> I have to run.  I do hope you will work to get more stuff into the Ubuntu repos.
[04:56] <ScottK> Lamego: Which of those two bugs are you discussing, Flock?
[04:56] <Lamego> yes, flock
[04:56] <Lamego> which I believe contains some copyrighted art
[04:57] <xhaker> How does one regenerate the control file with one control.in manually?
[05:09] <Lamego> ScottK, we will continue this chat later :P
[05:17] <Lamego> what happened to the servers ? how where they compromised ?
[05:19] <sistpoty> Lamego: look at the mail sent to the loco teams, I don't know anything more than stated there
[05:19] <Lamego> I am not on a loco team, do you have the link ?
[05:20] <sistpoty> Lamego: https://lists.ubuntu.com/archives/loco-contacts/2007-August/001510.html
[05:20] <Lamego> the last mail on REVU denotes user accounts concern, it seems to be related :P
[05:21] <Lamego> no info
[06:05] <xxxxx1> heya
[06:06] <toutouff> Hi xxxxx1
[06:07] <xxxxx1> hey toutouff
[06:09] <highvoltage> hey xxxxx1 and toutouff
[06:10] <xxxxx1> hey highvoltage
[06:12] <ScottK> sistpoty: Is there a mailing list for REVU uploads/comments yet or is that still on the TODO?
[06:13] <sistpoty> ScottK: it should use the motu-reviewers one, but s.th. (I guess with exim setup on sparky) is still wrong
[06:14] <sistpoty> ScottK: but it's on my list, but I probably won't fix it today though ;)
[06:14] <toutouff> I am a new contributor. About the bugs tagged as needs-packaging, if I want to package one, in debian/control, I set Maintainer with my name or with Ubuntu MOTU Developers ?( then it will go to REVU and maybe to universi if everithing's OK)
[06:14] <ScottK> OK.  No problem.  I really do appreciate all the effort you put into getting revu back up.
[06:15] <ScottK> toutouff: Maintainer is the Ubuntu MOTU Developers.  Set yourself as XSBC-Original-Maintainer.
[06:16] <sistpoty> ScottK: if I didn't program it that crappy in the first place, It'd have been much easier *g*
[06:16] <ScottK> Heh.
[06:17] <toutouff> ok, thank you ScottK
[06:35] <siretart> Seveas: do you have a minute regarding django use in falcon?
[06:36] <Seveas> siretart, yes
[06:36] <siretart> Seveas: I don't find a settings.py nor a manage.py in falcon's branch.
[06:37] <Seveas> siretart, that's because there isn't any :)
[06:37] <siretart> Seveas: how do you specify the sql backend, create tables and such?
[06:37] <Seveas> If you look at manage.py in a django project, you'll see it only has 3 lines. All functionality it uses can be used from code directly
[06:38] <siretart> right
[06:38] <siretart> still, I don't see a call to django.core.management.execute_manager() in falcon
[06:38] <Seveas> and settings.py isn't the only way to configure django, you can call django.conf.settings.configure(), see lib/falcon/config.py.in
[06:39] <Seveas> I don't use the functions of the manager with execute_manager -- the only functions I use is the database creation things, look for _get_sql_model_create in lib/falcon/__init__.py
[06:40] <Seveas> django/core/management.py exposes some other nice things as well
[06:41] <Seveas> you have to configure django (d.c.settings.configure() ) before being able to use the management functions this way
[06:41] <siretart> ah, I see
[06:41] <siretart> this requires quite intime knowledge of djangos internals, doesn't it?
[06:42] <Seveas> not really, I just wanted to be able to automatically create the tables and I went looking through the code to see how django does that
[06:42] <Seveas> django/core/management.py proved to be useful
[06:43] <Seveas> I found all this out while writing falcon :)
[06:43] <siretart> didn't you use the admin webapp from django for db administration/debugging tasks?
[06:44] <Seveas> no
[06:45] <Seveas> django offers the './manage.py shell' function. Falcon has a similar 'falcon shell' function, allowing you to easily play with its innards
[06:45] <Seveas> manual db administration/debugging should not be necessary for end users. I used either the falcon shell or a simple sqlite shell for that
[06:47] <siretart> for revu production, I'd prefer a postgres
[06:48] <sistpoty> huhu siretart
[06:48] <Seveas> then say so in django.conf.settings.configure() :)
[06:48] <siretart> hm. phone brb
[06:48] <siretart> hi sistpoty
[06:48] <Seveas> siretart, but revu is a web app, it should not try to avoid manage.py/settings.py
[06:56] <sistpoty> siretart: there are some weird exim errors in the log files on sparky, not quite sure what to make off these (didn't touch any exim stuff there)
[06:56] <sistpoty> siretart: e.g.: ** motu-reviewers@tauware.de R=nonlocal: Mailing to remote domains not supported
[07:22] <siretart> sistpoty: I'll look at that later today
[07:29] <sistpoty> siretart: cool, thanks!
[07:43] <Lamego> how do we flag that a package should be on the amd64 repository because it does not run on 64 bits ?
[07:44] <crimsun> err
[07:45] <crimsun> do you mean that it should /not/ be available for amd64?
[07:45] <Lamego> yes, if it does not work, why should it run ? Unless someone can provide a fix, which does not seem to be the case
[07:45] <Lamego> i mean, why should it be there
[07:46] <Lamego> https://bugs.launchpad.net/ubuntu/+source/gambas/+bug/130137
[07:46] <ubotu> Launchpad bug 130137 in gambas "gambas doesn't open" [Undecided,New] 
[07:46] <siretart> Lamego: I'd say do the same as we do with all buggy software: file a bug
[07:46] <Lamego> it does not work on feisty, and it will not work on gutsy
[07:46] <Lamego> siretart, it was filed already
[07:48] <simu> still looking for motu that advocate my package rotoscope on revu
[07:49] <Lamego> the first bug report on this was on Date: Wed May 2 12:41:39 2007
[07:50] <Lamego> still the package keeps there, leading people to spend more time on bug reports
[07:50] <siretart> sistpoty: should be working now
[07:51] <sistpoty> siretart: excellent, thanks!
[08:02] <siretart> sistpoty: sparky is now relaying mail via faui45, I need to ask michael gernoth tomorrow if he's okay with that, but I'm confident
[08:03] <mok0> Do we have to register again with REVU? My account seems to have disappeared...
[08:04] <sistpoty> siretart: great, thanks a lot... imo it would only bee needed to relay mails to the reviewers mailing list, maybe michael would like that, too ;)
[08:06] <ScottK> mok0: Not all the accounts have been recreated.
[08:06] <sistpoty> mok0: you're not a motu, are you?
[08:07] <sistpoty> mok0: if so, you're account will automatically get recreated, once you'll upload a package
[08:11] <mok0> sistpoty: No I'm not a MOTU
[08:11] <sistpoty> mok0: I've only imported motu accounts, since setting an account to be able to review packages is (the only) manual step
[08:12] <Lamego> does this new old REVU server has backups setup ?
[08:13] <sistpoty> Lamego: it doesn't. but I'll do manual backups from time to time
[08:14] <mok0> sistpoty: So I have to get my gpg public key uploaded again?
[08:15] <sistpoty> mok0: unless you've changed your key on LP today, no. I imported the keyring from LP on friday night
[08:15] <geser> mok0: no, upload to REVU again and your account will get recreated (with a new password)
[08:16] <mok0> I'll try it tomorrow
[08:16] <sistpoty> mok0: but please only upload, if you've got a package to review to keep revu clean ;)
[08:18] <siretart> sistpoty: regarding the home directories of tiber, in fact, I've done some using boxbackup
[08:18] <mok0> sistpoty: not to worry, I have several packages that have gone through several cycles of reviewing.
[08:18] <siretart> sistpoty: I would 'just' need to restore them :)
[08:19] <sistpoty> siretart: great... though I'd rather not run arbitrary cronjobs/web-pages from home directories on sparky ;)
[08:19] <mok0> ScottK, geser: my feisty -> gutsy distupgrade crashed and burned
[08:19] <sistpoty> siretart: I'll follow up on the mail regarding revu with that info
[08:19] <siretart> sistpoty: wait with that
[08:19] <sistpoty> siretart: ok
[08:19] <siretart> sistpoty: I still need to find the encrpytion key
[08:20] <sistpoty> hehe
[08:22] <siretart> ok, found it. hmm. I wonder if I should restore the backup key to tiber and restore the old homes there.. hmmm
[08:22] <siretart> oh, boxbackup not in feisty, need to backport that. grml
[08:23] <ScottK> mok0: We need bug reports then.  If you want help sorting it out before filing bugs, feel free to mail me.
[08:25] <mok0> ScottK: I am not sure what went wrong.
[08:25] <ScottK> mok0: What happened?