/srv/irclogs.ubuntu.com/2009/03/31/#ubuntu-motu.txt

TheMuso.c00:04
directhex.cs00:06
=== jdong_ is now known as j-dizzle
=== j-dizzle is now known as jdong
=== Snova_ is now known as Snova
xooxCan anyone tell me why the ppa repo https://launchpad.net/~rvm4000/+archive/ppa is empty? All the links are broken.02:10
=== spork is now known as Guest64965
Milyardoxoox: https://launchpad.net/~rvm4000/+archive/ppa/+build/91714802:35
MilyardoThere were build failures at launchpads last attempt to build packages02:35
=== Andre_Gondim is now known as Andre_Gondim-afk
xooxMilyardo: So *no* packages are available?03:03
xooxMilyardo: Seems only lpia failed.03:03
=== Snova_ is now known as Snova
=== TheMuso_ is now known as TheMuso
=== Andre_Gondim-afk is now known as Andre_Gondim
=== Andre_Gondim is now known as Andre_Gondim-afk
LordKowso whats going on with nautilus-actions?05:51
LordKowbug 34103505:51
ubottuLaunchpad bug 341035 in nautilus-actions "[jaunty] %d parameter returns nothing" [Undecided,New] https://launchpad.net/bugs/34103505:51
LordKowupstream cvs has had little activity over the last couple of years, mostly translation updates. all of the bug reports on gnome's bugtracker are being left alone. i don't think ubuntu should try and maintain an otherwise unmaintained package... if that is the case.05:52
LordKowit appears that nautilus scripts can pretty much do the same. and as it stands right now nautilus-actions is pretty much useless if %params are broken.05:52
LordKowi guess not all the %params are broken, but still my other points stick... i guess if there is a motu person who wants to continue to maintain it then sure.05:55
dholbachgood morning06:26
stefanlsdmorning06:28
dholbachhiya stefanlsd06:28
=== fabrice_sp__ is now known as fabrice_sp
fabrice_sp'morning stefanlsd06:34
pwnguinScottK-desktop: out of curiousity, how'd you notice #31295706:37
dholbachcan I persuade somebody to do a demo of some packaging topic on 23rd April, 0:00 UTC?07:07
dholbachI know I might be up at the wrong time to persuade people who are awake around that time ;-)07:07
dtcheni could. any suggested topics/boundaries?07:13
dholbachhey dtchen07:14
* dholbach hugs dtchen07:14
dholbachanything you like - https://wiki.ubuntu.com/Packaging/Training is what we're going to try out07:14
dholbacha 15 minute demo + some time for Q&A is compeltely fine07:14
dholbachI hope that people will step up and give short demos like "dh_install --list-missing" or "quilt" or "pbuilder hooks" or whatever07:15
macoyes plz!07:15
macodoh...i'll have to miss that one. there'll be logs, right?07:17
dtchenmaybe piuparts, though i certainly don't mind covering dh 7/quilt/git07:17
dholbachsure07:17
dtchenlet me get back to you via e-mail07:17
dholbachdtchen: thanks a lot - I'll be announcing the sessions in a bit anyway, we'll just keep the slot open until then07:18
dholbachdtchen: as I said, whatever you like - I'm sure there's going to be a lot of people who appreciate it07:18
gesergood morning08:21
dholbachhi geser08:22
geserHi dholbach08:22
stefanlsdAnyone willing to take a look at https://bugs.edge.launchpad.net/ubuntu/+source/tripod/+bug/337862 - its NBS and there is a FTBFS for lastfm. Its qt4.5 related and gentoo has a patch, i just cant work the qmake stuff out08:25
ubottuUbuntu bug 337862 in amarok "Small libgpod3 -> libgpod4 transition" [High,Fix released]08:25
=== santiago-pgsql is now known as santiago-ve
Toadstoolgood morning08:30
=== thekorn_ is now known as thekorn
=== thekorn_ is now known as thekorn
=== asac_ is now known as asac
abliHi! if I want to publish a package in my ppa for hardy, intrepid and jaunty, does that mean that I have to uploaded it three times with only the distrib being different in the changelog?11:53
geserabli: yes, changing the distro and the version (e.g. adding ~intrepid1 to the end)11:55
abliEven if nothing else is different? Shouldn't I be able to upload a single source package and say "compile this for each distrib"?11:56
pmjdebruijnnot yet11:56
abliok. thanks.11:57
geserabli: as the build debs are strored in one directory you can't have three different debs (each one for a different release) in that one dir (as the filename will be the same)11:58
abliok. Uploading the source three times is no problem. I was just trying to avoid generating extra work for the ppa system, but I guess its not much of an issue.11:59
pmjdebruijnjust always suffix ~intrepid or ~jaunty12:00
gordonsymeHello12:01
gordonsymeAny python packagers about?12:01
=== mcasadevall is now known as NCommander
=== thekorn_ is now known as thekorn
ScottKpwnguin: One of the Python teams (pythonistas) is subscribed to cwiid bugs.13:27
directhexwii!13:29
directhexi still wish someone more competent than me had done something with the ps3 bluetooth remote13:29
=== thekorn_ is now known as thekorn
goshawkhi14:11
gordonsymeHi, any python packagers around?14:17
hyperairgordonsyme: as in python apps or python itself14:17
gordonsymehyperair: python apps14:18
cody-somerville!ask14:18
ubottuPlease don't ask to ask a question, simply ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)14:18
hyperairwell i've been messing around with a python app but nobody's reviewed it/sponsored it in debian14:18
gordonsymehyperair: I've been trying to work out how to package something for a few days and I've just hit a wall. I don't know enough about the packaging process to continue14:18
hyperairyea just ask14:18
POXhyperair: not possible, did you ask on #debian-python or debian-python@l.d.o ?14:19
hyperairPOX: what?14:19
POX"but nobody's reviewed it/sponsored it in debian"14:20
hyperairPOX: i'm not satisfied yet14:20
hyperairPOX: when i'm satisfied with my own packaging i'll ask for sponsoring14:20
hyperairPOX: there's a java part which may or may not need building14:20
gordonsymeI have a bunch of modules and three scripts. I have distutils building a tarball for me. Previously I was using CDBS to package the distutils tarball into a single deb. Now I would like to package the modules in one 'common' deb and put each script into its own deb. Is this even possible without writing a massive rules file?14:20
POXoh ok, I thought nodoby in Debian replied to your RFS14:21
hyperairPOX: hahah14:21
hyperairPOX: actually i think i posted an RFS on debian-mentors14:21
hyperairPOX: then i retracted it because upstream changed something14:22
POXCc debian-python@ next time14:22
hyperairgordonsyme: look into dh_install14:22
hyperairPOX: does debian-python have some sort of Vcs?14:22
gordonsymehyperair: thanks14:23
POXdebian-python@l.d.o is a mailing list, but we have 2 teams as well14:23
hyperairgordonsyme: you might be interested in looking at remuco-server which is sitting in mentors.debian.net14:23
POXone for modules/extensions and one for applications14:23
gordonsymehyperair: cool, will have a look14:23
POXcan someone teach the ubottu about DPMT and PAPT?14:23
hyperairPOX: i see. what are their names?14:23
hyperairPOX: what's DPMT and PAPT?14:24
POXthere's a wiki page on ubuntu.com, IIRC14:24
POXlet me search14:24
POXhttps://wiki.ubuntu.com/Debian/PythonModulesTeam14:26
hyperairPOX: i see. cool14:28
hyperairPOX: only svn? =(14:29
POXbut your package will have to be perfect to be sponsored, ask savvas ;)14:29
hyperair?14:29
POXhttps://bugs.launchpad.net/ubuntu/+source/imgseek/+bug/34245014:30
ubottuUbuntu bug 342450 in imgseek "Please sync imgseek 0.8.6-3 from debian unstable" [Medium,Confirmed]14:30
POX"It was a long journey" ;)14:30
hyperair._.?14:30
* hyperair doesn't like svn =\14:32
POXit's just a tool that keeps the debian dir14:32
hyperairyes iknow14:33
hyperairi prefer git14:33
POXtell that to >100 other maintainers14:33
hyperair=(14:33
POXI like git too, but I doubt we'll use it14:34
hyperairwe could use both =D14:34
POXeven if I would be the only one to decide14:34
hyperairoh =(14:34
hyperairwell pkg-cli-* has both git and svn14:34
POXno we cannot use both14:34
hyperairwhy not14:34
POXone of the requirement is to have a command that will update all packages (including the new ones)14:35
hyperairoh14:35
POXtry to check/sponsor few packages a day when you cannnot automate as much a possible14:36
hyperairsince when is sponsoring an automated task14:36
POXupdating all packages in one comman and grepping for common mistake is14:37
POXor updating it while starting to read RFS mails14:37
POXcommand*14:37
hyperairi see14:38
POXactually right now I'm without computer at home (it died few days ago), but usually I do it this way14:38
ahasenackhey guys, got this error when trying to build a package for smart-1.2 (based on the previous jaunty one):14:40
ahasenackpycentral: pycentral debhelper: both directories site-packages and dist-packages exist.14:40
ahasenackpycentral debhelper: both directories site-packages and dist-packages exist.14:40
ahasenackit's the same rules file (1.1.1 vs 1.2), and same environment (jaunty), but for some reason it fails when using 1.214:40
ahasenackwhat's this about?14:40
* hyperair has only used python-support14:42
hyperairbut if rules fails with 1.2, then obviously upstream has changed something14:42
hyperairand rules needs to be updated14:42
hyperairor something else14:42
POXhyperair: it will be hard to be sponsored with python-central in our teams14:43
POXahasenack: check if you have new pytohn-central14:43
hyperairPOX: ?14:43
POXpython2.6 installs to dist-utils by default (or at least if the layout=deb is used)14:43
ahasenackPOX: 0.6.11ubuntu514:43
hyperairPOX: you mean python-support or python-central is preferred?14:43
POXso it's ok14:43
POXnot prefered, pysupport is the only one accepted since few week14:44
POXs14:44
ahasenackhmm, found a difference in setup.py14:44
hyperairPOX: then you shouldn't be telling me, i've only ever used python-support ;)14:44
hyperairPOX: but you should get the debian python policy page updated14:44
POXI only wanted to let you know that you're using the right one ;)14:44
hyperairPOX: ah okay =p14:44
POXhyperair: the policy for 95% of packages is 1) install to standard location 2) call dh_pysupport14:45
hyperairPOX: install to standard location meaning?14:46
POXwe'll deal with policy once all packages will not use pycentral or "currect"14:46
hyperairmy package uses python setup.py install --install-lib=/usr/share/python-support/modulename --root=debian/tmp14:46
POXhyperair: python ./setup.py --root=debian/package/14:46
hyperairPOX: is that all that's needed?14:46
POXhyperair: that's wrong14:46
POXyou should not use pysupport internal paths14:47
hyperairhm14:47
POXremove --install-lib and it will be ok14:47
hyperairPOX: the policy said to use --isntall-lib. don't you think this is even more reason to correct it?14:48
hyperairand perhaps state that "pysupport is preferred"14:48
POXhyperair: there are lots of special cases, but again for ~90%  of packages that's all what you need to know about python policy14:48
POXat least for python modules14:49
hyperairPOX: http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html#s-pysupport14:49
POX(not applications or extensions)14:49
hyperairPOX: i'm talking about this. it says use --install-lib14:49
POXcheck README file from python-support package14:49
POX(the one from experimental has a mini howto)14:50
hyperairhmm14:50
POX/usr/share/doc/python-support/README.gz14:50
POX(experimental's one is updated)14:50
hyperairi see14:51
POX(will be uploaded to unstable soon)14:51
hyperairbut seriously, what's wrong with updating the policy?14:51
POXyou have to convince doko to update it14:52
POXand since he's python-central author, it will be hard14:52
hyperairugh14:52
goshawki'm packaging a compiler which needs a library which is not packaged in ubuntu yet (both library and compiler). The compiler needs the library (which is a .a) to link binaries cuz it's a standard library. Should i package the library into the compiler package or should i create 2 packages, oner for library-dev and one for compiler?14:54
hyperairPOX: without --install-lib, it installs into /usr/share/python2.614:54
hyperairsorry14:54
hyperairdebian/tmp/usr/lib/python2.5/site-packages14:54
POXthat's ok, dh_pysupport will move the files to the right location14:54
sistpoty|workgoshawk: I'd just put it the static lib into the compiler package14:55
hyperairPOX: but it didn't14:55
POXchange "tmp" to package name and it will14:55
hyperairmeh.14:55
hyperairi see14:55
goshawksistpoty|work: uhm... well.14:55
hyperairso pysupport is after dh_install eh14:55
POXyes14:56
goshawksistpoty|work: do you know if there is a paragraph in the debian policy about it?14:56
hyperairi see14:56
sistpoty|workgoshawk: to my knowledge there isn't14:57
sistpoty|workgoshawk: does upstream release the library as separate tarball?14:57
goshawksistpoty|work: yes14:57
goshawkcompiler is a project14:57
sistpoty|workgoshawk: then I guess the -dev is better... just thought this was in the same tarball14:57
goshawkand library another one14:58
gordonsymehyperair: many thanks for your help, your remuco-server rules file showed me exactly what to do14:58
hyperairgordonsyme: np.14:58
hyperairgordonsyme: one thing. debian/rules should not have --install-lib in the setup.py call14:58
goshawksistpoty|work: but the compiler should depend on the library then14:58
goshawkas Depends:14:58
sistpoty|workgoshawk: if it otherwise can't build binaries then yes14:58
goshawkisn't it?14:59
goshawkok14:59
goshawkthx14:59
hyperairgordonsyme: also, if you don't have a Makefile as well as a setup.py at the top-level, you shouldn't need to override dh_auto_install14:59
goshawkone more think14:59
goshawkthing14:59
goshawkthe library name is tango14:59
goshawkshould i package it as libtango?14:59
gordonsymehyperair: ok, I'll give that a go. Thanks again15:00
hyperairgoshawk: see the debian library packaging guide15:00
hyperairgordonsyme: if you're using git, you can use git clone git://git.debian.org/git/collab-maint/remuco-server.git15:00
hyperairgordonsyme: i've updated the stuff there15:01
gordonsymehyperair: great, ta15:01
hyperair=)15:01
vladimir_ehi all, does anyone know why claws-mail-tools depends on claws-mail? it's a recommended package for Sylpheed and that forces Sylpheed users to install claws-mail15:08
bddebianHeya gang15:12
sistpoty|workhi bddebian15:15
bddebianHeya sistpoty|work15:15
cody-somervillevladimir_e, Probably a bug.15:16
cody-somervillevladimir_e, please file one :)15:16
vladimir_ecody-somerville, yes, wanted some insight before doing so15:16
\shet voila...google-perftools fixed15:29
zirodaycould anyone help me out with https://wiki.ubuntu.com/MOTU/GettingStarted?15:33
zirodayI'm getting a 500 error15:33
vladimir_eziroday, working for me15:33
zirodayvladimir_e: heh, appending the ? made it work, https://wiki.ubuntu.com/MOTU/GettingStarted doesn't though15:34
maxbziroday: It works for me, try refresh (or Shift+Refresh)15:45
zirodaymaxb: must just be my day :)15:45
=== rTd_fNjL is now known as LjL
LucidFoxIf I see a bug with only a patch attached rather than a debdiff, should I ask the patch's author to post a debdiff, or make my own upload and include the patch there?17:50
macomake your own17:50
maconot everyone that knows how to code knows how to make a debdiff. ive started going through and converting patches i find17:51
=== santiago-pgsql is now known as santiago-ve
* LucidFox nods17:52
=== mathiaz_ is now known as mathiaz
=== Igorot is now known as Knightlust
YokoZarQuick sponsorship question: if I'm sponsoring someone else's debdiff without further changes, I'm supposed to leave their name in the changelog and manually sign it before uploading yes?18:46
directhexafaik yes18:47
YokoZar(this isn't listed in the sponsorship workflow page): https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue18:47
directhexi.e. acknowledgement of who did the work18:47
directhexi've been in a few changelog.Debian.gz files anyway18:48
YokoZarHow does launchpad know whose signature is on it?18:48
YokoZar(eg that I uploaded it)18:48
YokoZarbecause it tracks that too I think18:48
YokoZarAlso I'm not entirely sure of the command to make this manual signature (I'll put it in the wiki on the sponsorship page)18:49
fabrice_spHi. A small question: can a package in universe depends on packages in multiverse?18:50
directhexdebuild takes a -k flag18:50
directhexfabrice_sp, no, that package is a multiverse package by definition18:50
YokoZarfabrice_sp: no, that package should then be moved to multiverse18:50
YokoZarAlthough that has to be done manually I think18:50
YokoZarfabrice_sp: It can recommend them though18:51
directhexYokoZar, recommends is okay? i thought only suggests18:52
fabrice_spdirecthex, so what kind of bug report should I open to demote it? (it's for mythtv-status, that depends on libmyth-perl)18:52
fabrice_spor YokoZar18:53
YokoZardirecthex: I thought recommends was okay...that way when someone has multiverse unchecked in sources it won't freak out like it will with depends18:53
YokoZarOnly difference between recommends and suggests is install by default -- otherwise we'd need a third category (install by default unless repo is disabled) or something, which is what recommends does currently18:54
Turlhi18:54
Turlhow can I call dh_desktop on cdbs?18:55
YokoZarfabrice_sp: file a bug against the package on launchpad and just put that in the description "should be in multiverse" or "depends on a multiverse package but is in universe"18:55
fabrice_spYokoZar, ok. Thanks!18:55
fabrice_spFor that request (move from universe to multiverse), should I subscribe u-u-s or archive admin directly?19:04
AnAntHello, I am trying to create a pbuilder environment from the Jaunty beta ISO image as follows:19:23
AnAntsudo pbuilder --create  --distribution jaunty --mirror  "deb cdrom:[Ubuntu 9.04 _Jaunty Jackalope_ - Beta i386 (20090324)]/"19:23
AnAntand I've mounted the ISO on /cdrom/19:23
AnAntyet pbuilder gives this error:19:24
=== Zic is now known as Guest12602
AnAntE: unknown location deb/dists/jaunty/Release19:24
lfaraoneAnAnt: run the command without "deb" and see what happens.19:24
AnAntE: unknown location cdrom:[Ubuntu/dists/jaunty/Release19:25
AnAntso ?19:25
lfaraoneAnAnt: did you use apt-cdrom to add the CD?19:27
AnAntlfaraone: apt-cdrom in what ?19:27
lfaraoneAnAnt: apt-cdrom is a utility.19:27
lfaraoneAnAnt: you use it to add CDs to your apt sources.19:28
AnAntlfaraone: I'm talking about pbuilder, apt-cdrom adds CD in /etc/apt/sources.list19:28
lfaraoneAnAnt: once you do that, apt should know to use it automagically.19:28
AnAntlfaraone: what has apt to do with pbuilder ?19:28
lfaraoneAnAnt: (pbuilder uses apt)19:28
lfaraoneAnAnt: *everything*19:28
AnAntlfaraone: anyways, the CD got added when I ran /cdrom/cdromupgrade19:29
AnAntlfaraone: pbuilder uses apt, but it doesn't get the mirrors from /etc/apt/sources.list19:29
AnAntlfaraone: it gets them either from command line or /etc/pbuilderrc19:29
macolfaraone: pbuilders have their own /etc/apt/sources.list though19:31
=== paul__ is now known as Elbrus
macoyou can login to pbuilders19:31
AnAntah, done it19:32
AnAnt--mirror file:/cdrom19:32
AnAntgot it from debian  bug 166665119:33
ubottuError: Could not parse data returned by Debian: HTTP Error 404: No such bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1666651;mbox=yes)19:33
AnAntgot it from debian  bug 16665119:33
ubottuDebian bug 166651 in pbuilder "pbuilder: please support CDs" [Wishlist,Open] http://bugs.debian.org/16665119:33
superm1AnAnt, add that to the wiki page if you can19:35
AnAntwell, this seems to have a problem on subsequent pbuilder update though19:36
AnAntoh, I got other errors19:36
AnAntW: Failed to fetch file:/cdrom/dists/jaunty/main/binary-i386/Packages  File not found19:38
AnAntthat causes pbuilder to abort with error19:39
AnAntI see that there is /cdrom/dists/jaunty/main/binary-i386/Packages.gz19:39
AnAntie. gzip'ed19:39
ahasenackare there people from Ubuntu QA here in this channel? I was wondering if we could get https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/309042 fixed for jaunty at least19:41
ubottuUbuntu bug 309042 in console-setup "Intrepid: no "brazil - thinkpad" keyboard layout option anymore" [Undecided,New]19:41
nxvlnixternal: ping19:48
AnAntwhy is it trying to fetch cdrom/dists/jaunty/main/binary-i386/Packages instead of cdrom/dists/jaunty/main/binary-i386/Packages.gz ?!19:50
nixternalnxvl: pongalong19:50
nxvlnixternal: whouldn't you want to run the session of 23rd April, 00:00 UTC??19:51
nixternalwhat session?19:51
nxvlnixternal: http://ubuntupackaging.wordpress.com/2009/03/31/packaging-training-kicking-off-this-week/19:51
nixternalnxvl: unsure if I can commit to that just yet, but I would be interested in some Kubuntu packaging stuff on that list19:54
nxvlnixternal: that's fine, we are going to do it every thursday19:55
nxvlnixternal: rotatin hours like it said there19:55
nxvlnixternal: i'm just trying to file the white space of the 23th19:55
nixternallet me find someone for you19:56
nxvlnixternal: \o/19:56
nxvlnixternal: even a 15 minutes session + Q&A is welcomed19:56
=== mathiaz_ is now known as mathiaz
=== foursixnine is now known as santiago-ve
AnAntheimdal-dev is a virtual package ?!20:28
AnAntwhat's wrong with pbuilder ?!20:30
cody-somervillenothing20:30
cody-somervillepbuilder uses apt20:30
DktrKranzAnAnt, it's not20:30
AnAntpbuilder is failing to build a package because it thinks that heimdal-dev, libfsplib-dev, libmozjs-dev and libtre-dev are virtual packages !20:31
jpdsAnAnt: Do you ave universe enabled in your pbuilder setup?20:33
AnAntyup20:33
AnAntand done pbuilder update20:34
fabrice_spHi DktrKranz. It seems Bug #345263 is stuck. What should be the next step?20:35
ubottuLaunchpad bug 345263 in ubuntu "Sync php-mdb2 2.4.1-1 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/34526320:35
AnAnthow does it get the notion that those packages are virtual ?20:35
fabrice_spAnAnt, try to login to pbuilder, and check what is the content of source.list20:37
AnAntfabrice_sp: I just done that, found that universe & multiverse are enabled there, so I logged using --save-after-login, and enabled them, and now running apt-get update20:39
fabrice_spok20:39
AnAntthanks20:39
fabrice_spgood luck with pbuilder :-)20:39
AnAntthanks20:40
cjwatsonahasenack: 309042> surely getting bugs fixed is a function of development, not QA21:11
ahasenackcjwatson: I was under the impression QA was the first step: they would triage it and assign it the right milestone21:12
cjwatsonahasenack: yay paperwork21:12
ahasenackcjwatson: :)21:12
cjwatsonI'll deal with it, I might actually get it right21:12
cjwatsonthe keyboard subsystem is difficult and I'm not aware that QA is deeply familiar with the ins and outs of it (I wouldn't blame them)21:13
ahasenackcjwatson: \o/ thanks!21:13
cjwatsonahasenack: but just as a basic comment, the set of layouts and variants that exists is actually under the control of xkeyboard-config, not console-setup21:14
cjwatsonahasenack: the reason it wasn't changelogged in console-setup is that console-setup just gets updated from xkeyboard-config on each rebuild21:15
ahasenackaha21:15
cjwatsonI'll make sure that it isn't getting left out for some other reason before reassigning the bug21:15
=== yofel_ is now known as yofel
=== Igorot is now known as Knightlust
macois there a way to specify to dh_make whether its gplv2 or v3?22:10
macoor does it not have to be that specific?22:11
marnoldmaco, iirc no22:12
macois that to both?22:12
=== azeem_ is now known as azeem
cjwatsonmaco: why not just edit it after dh_make has finished? it's only meant to be a first pass22:19
macocjwatson: well the second question was to ask if the control file has to say which gpl version or just "gpl"22:21
=== Snova_ is now known as Snova
cjwatsonmaco: licensing goes in debian/copyright rather than debian/control; but yes, it should say which GPL version is involved, although that might be "v2 or later" or similar22:22
macooops. ok thank you22:24
=== Snova_ is now known as Snova
=== Snova_ is now known as Snova

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!