/srv/irclogs.ubuntu.com/2011/10/22/#ubuntu-devel.txt

jbicha!backports | mika00:13
ubottumika: If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging00:13
ScottKYes, that's what I was about to say.00:13
blahsphemerDoes the passwd executable change the ownership of any file? cuz it's capability list seems to list: CAP_CHOWN as one of the capabilities01:34
infinityIt's entirely possible that it does so when it creates backups and copies things around.  Though why it doesn't create with the permissions it wants then, I don't know.01:38
infinity(I haven't checked, though, the CAP may be entirely unnecessary)01:38
blahsphemerinfinity, no. THe cap is necessary. I tried removing the cap and change a passwd, it says Authentication token manipulation error01:39
blahsphemerHow do I investigate this? As in how do I find out which file it's modifying?01:39
infinitystrace it.01:39
infinityOr read the source.01:39
infinityBut stracing is the simpler way to quickly find the opens/creates/renames/chowns.01:40
blahsphemerinfinity, ok01:41
blahsphemerinfinity, I unable to change passwords if I run passwd using strace. Would you know why?02:17
blahsphemerinfinity, running from the terminal normally,  am able to change the password, though.02:17
infinityAre you doing it as root?02:22
infinitystracing suid binaries doesn't work so well.02:22
blahsphemerinfinity, oh no. I completely forgot that part. I'll do it now.02:23
blahsphemerinfinity, found it. It chowns /etc/nshadow. Thank you very much02:27
=== Amaranth_ is now known as Amaranth
=== bregma_ is now known as bregma
=== Amaranth_ is now known as Amaranth
mikaScottK: thanks (and also to jbicha who isn't here anymore :))07:55
asachmm. weren't there bzr branches for ppa packages similar to UDD? whats the url scheme for those?09:12
asacjames_w: i guess you know :) ?09:15
=== tkamppeter_ is now known as tkamppeter
maxbasac: I never heard of such a thing10:26
asacmaxb: kk10:30
Davieyinfinity: Sync's don't seem to provide karma.. so there is no risk of gaining too much :)10:46
StevenKDaviey: If there isn't a bug for syncs not providing karma, please file one.10:48
DavieyStevenK: that would imply we care about karma :)10:48
StevenKWell, we as in the LP team do.10:49
erle-when will there be a fglrx update? who is in charge?11:04
erle-maybe a update fixes it11:05
erle-repos have version 8.889, amd has version 8.892 released11:05
infinityStevenK: I want karma every time I perform queue manipulation.14:38
infinityStevenK: But more seriously, I want every queue change audited.14:38
zubHi, what package is reponsible for the distro upgrade dialog - is it update-notifier?19:34
hyperairupdate-manager i should think.19:35
zubah, ok19:36
zubhttp://linux.fjfi.cvut.cz/~zub/Screenshot-Ubuntu%2011.10%20Upgrade%20Available.png19:36
zubseems it ignores http proxy, so I'm looking if there's a bug reported for this already19:36
hyperairtry setting it in /etc/apt/apt.conf.d/19:38
zubit is set, come on19:38
zubaptitude works ok19:38
hyperairah19:38
* hyperair shrugs19:38
zuband it's set in http_proxy, and even in the gnome thing, whatever that does19:38
zubhyperair: sorry :)19:38
zubin that window, it's trying to fetch a web page with some info about the upgrade - I think... so it shouldn't be using apt's proxy, but http_proxy or whatever else the gnom proxy setting changes19:40
zubbut anyway as far as I know, all that's needed was set at that box, web works, apt works19:40
slangasekzub: please file a bug against update-manager, yes19:47
penguin_03has this patch "DM-CRYPT: Scale to multiple CPUs v3" http://lkml.org/lkml/2010/10/10/44 been applied to any versions of Ubuntu?19:47
zubslangasek: ok, thanks for info19:47
zubI'm also filing/commenting on some unity bugs19:48
zubI've been using it for 1 day and found several issues I believe to be bugs :-(19:48
slangasekpenguin_03: there's no reason we would have picked such a patch unless it's included in the upstream kernel we're shipping19:49
penguin_03do the newer kernels have any parallel dm-crypt support?19:49
slangasekno idea19:50
dajhornpenguin_03: That patch is in the Oneiric kernel.19:56
penguin_03dajhorn, thanks19:56
dajhornpenguin_03: Welcome.19:57
=== yofel_ is now known as yofel
SpamapSslangasek: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/876959 ... he's right that the dbgsym packages for the version of mysql 5.1 in lucid-updates aren't on ddebs.ubuntu.com. Any ideas?20:01
ubottuLaunchpad bug 876959 in mysql-dfsg-5.1 (Ubuntu) "no mysql-server-5.1-dbgsym for security/updates repositorires" [Undecided,New]20:01
SpamapSthough they are available for the highest version in lucid-security20:01
slangasekSpamapS: ICMP redirect pitti20:01
slangasekin general the ddeb archive is a mess because there's no LP-driven reference counting; but I'm never clear on what bugs are present at any given time20:02
SpamapSpitti: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/876959 ... he's right that the dbgsym packages for the version of mysql 5.1 in lucid-updates aren't on ddbes.ubuntu.com. Any ideas?20:02
ubottuLaunchpad bug 876959 in mysql-dfsg-5.1 (Ubuntu) "no mysql-server-5.1-dbgsym for security/updates repositorires" [Undecided,New]20:02
SpamapSslangasek: I've had mostly failure when trying to make use of it. :-/20:02
SpamapSpartial success... but almost always some piece missing20:03
SpamapSslangasek: so there's no LP project that is specific to the dbgsym repo?20:03
SpamapSwas going to redirect the bug to that20:03
slangasekah, I don't know; my point was about soyuz not knowing about ddebs20:04
SpamapSoh right20:04
SpamapSslangasek: so, the PHP upstreams want us to include PHP 5.4 in 12.0420:11
SpamapSslangasek: maybe I'll make the condition that their build process stops smoking crack for 3 months before we do that. ;)20:11
slangasekheh20:11
slangasekgood luck, it's a lifelong addict20:12
SpamapSLike taking the weed from snoop20:14
SpamapSit wouldn't be PHP if it didn't have the rock20:14
luist_can anyone point me a simple .dsc to build a deb package?20:35
cjwatson.dsc files are generated by the dpkg-dev toolchain from a source tree; you won't get anywhere at all trying to write a .dsc by hand20:39
marwi'd like to assist in development of a project/application, and i know only python. any advice on where to start?20:41
luist_oh god…. i have a folder with 1 executable and 1 .desktop file. i compressed them in a tar.gz. how do i make a deb package out of it… that should be so simple but all the freaking guides i find shows the tons of useless stuff that i dont need…!20:44
cjwatsondh_make should get you most of the way there; or I'm sure if you put the .tar.gz somewhere public then somebody could give you the files you need under debian/20:45
cjwatson(I would, but need to deal with children's bedtime ...)20:46
marwluist_: there is a good video tutorial by a german guy about deb files for py projects20:46
luist_marw: link?20:46
SpamapSluist_: dh_make will indeed build you a pretty good debian/ dir20:46
marwluist_: you're in luck, i saved it. http://showmedo.com/videotutorials/video?name=linuxJensMakingDeb20:46
cjwatsonpython packaging can actually be a fairly complex case and is more than you need if it's just a single executable20:46
cjwatson(because of all the complexities around supporting multiple python versions)20:47
=== Quintasan_ is now known as Quintasan
maxbAnd the infelicitous profileration of methods of doing so20:47
maxb*proliferation20:47
cjwatsonyes, though that's getting better20:48
SpamapSluist_: you probably jus need to run that, and then list the files you want installed in debian/install  like   executable_file /usr/bin      then  exec.desktop /usr/share/applications20:48
cjwatson(it did involve the creation of a third method, but the previous two are now deprecated and their use is dropping)20:48
maxbSadly, despite my best efforts, I have yet to eliminate Debian etch at work, so I'm doomed to live with the variety for a while longer :-)20:48
cjwatsonyep, what SpamapS said20:48
cjwatson*etch*?20:49
luist_SpamapS: ok nice! but what am i doing wrong here: http://pastie.org/2742190  the dir names seems to be right20:49
maxbI know, I know20:49
* cjwatson passes maxb an archaeologist's hat20:49
cjwatsoncd hinfo-0.1; dh_make20:49
SpamapSindeed20:49
luist_oh20:49
cjwatson(actually you may need to 'mv hinfo-0.1.tar.gz hinfo_0.1.orig.tar.gz' first)20:50
* SpamapS recalls similar happy days learning to package his first real C application.. pipemeter.. some 10 years ago :)20:50
maxbThe one thing to bear in mind about dh_make is that it writes an informative *template* - it might just work even if you don't customize what it emits at all, but I'd strongly recommend deleting all the bits you don't need and ensuring you understand everything you keep20:51
luist_SpamapS: ook! whats exactly is this debian/install20:51
cjwatson'man dh_install' will tell you20:51
luist_cjwatson: ok :P20:51
maxbmany of the debian/<something> files are declarative instructions for the dh_<something> program20:52
cjwatsonbut briefly, it's just a declarative way of installing specific files to specific locations, especially useful if your project doesn't already have 'make install' or similar20:52
SpamapSif you have a Makefile that understand 'make', and DESTDIR=foo 'make install' ..  it generally works IIRC20:52
SpamapSmaxb: they're all .ex so they just sit there20:52
SpamapScruft, but thats ok, he's not trying to get included in the distro ;)20:53
maxbSpamapS: Agreed, they don't harm the functionality of building the package, but they do obfuscate the new packager's understanding if they don't take the time to delete as appropriate20:53
SpamapSthats one reason we started pkgme ... trying to be smarter about building a real package, not just a templated one20:54
* SpamapS sorely wishes he could raise contributing to pkgme on his priority list20:54
luist_i just tried this: /work/HardwareInfo/hinfo-0.1$ dh_make -f ./hinfo-0.1.tar.gz  and i have no idea what happened rofl20:54
cjwatsonjust dh_make, you shouldn't need options20:54
luist_cjwatson: well its not like i see any difference here :T20:55
luist_cjwatson: is there any default folder where packages should be built, like with rpms?20:55
cjwatsonno, that's rpm brain-damage :)20:55
luist_cjwatson: yep :(20:55
cjwatsonanywhere under your home directory is just fine20:55
luist_cjwatson: well /work/... doesnt seem like my home dir right ;)20:56
cjwatsonor anywhere you can write to20:56
luist_ok20:56
cjwatsonas I say, if you're in a rush, it's fine to put the tar.gz somewhere and it would probably take an experienced packager five minutes.  it depends whether your goal is to make a package, or to learn how to do it20:56
luist_cjwatson: today: make a package   next week: learn how to do it to provide an update :T20:57
* cjwatson nods20:57
luist_yes it would take less than 5 minutes for me to make an rpm… but im not really in the mood of working on a weekend -.-20:57
cjwatson(note, then, that dh_make is one way to create the initial files, but you don't use it to update to new versions, and if you try you'll get confused)20:57
luist_cjwatson: well as long as it have a version, i can update right?20:58
cjwatsonthe basic idea of rpm and debian packaging is much the same; install files into a temporary directory, then bundle it up into a package with some metadata attached20:58
cjwatsondebian packaging is split out into several files rather than using a single .spec file, that's all really20:58
cjwatson(and sure, lots of tools and so on, but at the basic level ...)20:59
luist_well what exaclty should i do after running dh_make… plus i dont now what im doing until now: prepare Debian packaging for an original source archive sounds a bit abstract for me21:00
cjwatsonthe bare minimum for a Debian package is (a) debian/rules (which can be a copy of /usr/share/doc/debhelper/examples/rules.tiny) (b) debian/control with some metadata about your package (c) debian/changelog with version history in a specified format (d) if you want it to be accepted into a public repository anywhere, debian/copyright21:00
cjwatsonthere are usually a few other files as well but that's the guts21:00
luist_cjwatson: do i create these inside my folder?21:01
cjwatsonthen 'debuild' builds source + binary packages21:01
cjwatsonyes21:01
cjwatsondh_make should have done that for you21:01
luist_cjwatson: no it didnt21:01
cjwatsondid it produce any output at all?21:01
luist_cjwatson: but now a lot of things make sense.. that would replace the .spec right21:01
cjwatsonindeed21:01
luist_cjwatson: nop it didnt21:01
cjwatsonblink21:02
luist_cjwatson: what about hinfo_0.1.orig.tar.gz ?21:02
luist_cjwatson: my bad it gave me output21:02
maxbluist_: Do you use Bazaar? If so, check out the trivial example package https://code.launchpad.net/~maxb/+junk/example-package21:02
cjwatsonum, introducing more tools may not be the correct response to a confused person :)21:03
cjwatsonbut you can just look at it on the web21:03
maxbor just browse it, there are only 6 files21:03
cjwatsonyep, that's a good place to start21:04
maxbIn fact, go here: http://bazaar.launchpad.net/~maxb/+junk/example-package/revision/1 then click "expand all"21:04
cjwatsonluist_: pastebin the output?21:05
luist_cjwatson: oh i just used --createorig and it worked now21:06
luist_cjwatson: :)21:06
cjwatsonI'd have renamed hinfo-0.1.tar.gz to hinfo_0.1.orig.tar.gz, but whatever works21:06
luist_cjwatson: http://pastie.org/274227721:09
luist_cjwatson: theres no debian/install :T21:09
cjwatsonthat's ok, create it21:11
luist_cjwatson: did with the line: HardwareInfo    /usr/bin21:11
luist_cjwatson: or it should be just usr/bin ?21:12
maxbI have a feeling either might work, but usr/bin definitely will21:13
cjwatsoneither will work21:15
luist_cjwatson: ok also added: hinfo.desktop     etc/xdg/autostart21:16
luist_cjwatson: now what :)21:16
cjwatsonrun 'debuild', and if it gives you any errors then fix them up.  repeat.21:17
cjwatson(until successful.)21:17
cjwatsonif it completes successfully, run 'debc' to show what the resulting package looks like.21:17
luist_cjwatson: oh god: http://pastie.org/274232821:24
cjwatsonyou'll need to edit debian/changelog then.  it should be self-explanatory; if it isn't, paste it21:25
luist_cjwatson: wasnt it generated by dh_make rofl21:25
cjwatsonwhere it apparently says " -- root", it should be something like (example from one of my packages):21:25
cjwatson -- Colin Watson <cjwatson@ubuntu.com>  Wed, 19 Oct 2011 22:53:40 +010021:25
cjwatsonplease don't use "rofl" as punctuation, it sets my teeth on edge :)21:26
cjwatsonit can't autodetect everything - it generates a template for you to edit, hopefully fairly close to usable but it probably does need a few edits to work21:26
cjwatson(it's a long time since I actually used dh_make myself, sorry, I've been in this game long enough that I just do it by hand)21:27
luist_cjwatson: ok :) btw this is not self-explanatory at all… the line thats giving me the warning has the same syntax from the example u gave me: -- Max Bowsher <_@maxb.eu>  Sat, 22 Oct 2011 21:58:42 +010021:29
cjwatsonthe error output you pasted disagrees; it says that the line reads " -- root"21:30
maxbThe format is quite strict, including the number of spaces in each place, and the date format21:30
maxbThere is a tool, called "dch" for adding new changelog entries, such that you never need to type those lines manually21:31
cjwatsonI'm surprised dh_make gets it wrong by default though :-(21:31
luist_cjwatson: well i changed to   -- SEE-MG <_@anything.com> Sat, 22 Oct 2011 19:27:23 +010021:31
luist_cjwatson: but same error21:32
maxbThe *two* spaces between the email and the date are mandatory21:32
luist_maxb: oh21:32
cjwatsonoh meep, bug 87570521:32
ubottuLaunchpad bug 875705 in dh-make (Ubuntu) "dh_make in Oneiric outpus wrong content to changelog" [High,Confirmed] https://launchpad.net/bugs/87570521:32
cjwatsonsigh21:32
maxboutpus!  irta octopus initially :-)21:33
luist_errr… hinfo-0.1/debian/control at line 5: line with unknown format (not field-colon-value)   http://pastie.org/274235821:35
Laneyhah21:35
cjwatsonyeah, same bug21:35
cjwatson'export DEBFULLNAME="Your Full Name"; export DEBEMAIL=your@email.address'21:35
cjwatsonrm -rf debian  and start again21:35
cjwatsonsorry - I'll look into getting this fixed reasonably urgently21:36
luist_o.O21:36
cjwatsonlooks like it's because LOGNAME isn't set, perhaps a desktop-level change?21:37
cjwatsonI bet this is actually a lightdm bug21:38
luist_cjwatson: ok.. going to install these now: Could not find a signing program (pgp or gpg)!21:39
luist_cjwatson: i can feel im almost there21:39
cjwatsonyou can ignore that21:39
luist_cjwatson: really?21:40
luist_http://pastie.org/274238121:40
cjwatsonit won't have cryptographically-signed the package but it will have generated one, if it got that far21:41
cjwatsonyou can use 'debuild -uc -us' to stop it trying21:41
luist_ok good21:43
luist_cjwatson: oh god i have a deb package!!21:43
luist_cjwatson: thanks a lot :)21:46
cjwatsonexcellent, sorry about that roadblock21:46
cjwatsonI think I have a fix, just will need to test it a bit and do the paperwork for a stable update21:47
luist_cjwatson: its ok… ive learnt a lot here21:47
cjwatson(http://paste.ubuntu.com/716397/)21:47
cjwatsonfix uploaded to precise, doing the writeup for oneiric-proposed now21:54
Laneyhm, I use lightdm yet have $LOGNAME set21:54
cjwatsonsomething in your shell startup scripts?21:54
Laneynot knowingly21:54
cjwatsonor even your shell21:54
Laneygnome-panel/xmonad instead of unity21:54
maxblightdm/unity here ... and no $LOGNAME21:54
cjwatsonthe bug seemed fairly clear when I looked at the lightdm source21:54
Laneyyeah, I checked on another unity laptop and it didn't have it21:55
Laneyzsh must set it21:55
cjwatsonit does21:55
cjwatson./Src/params.c:703:    setsparam("LOGNAME", ztrdup((str = getlogin()) && *str ? str : cached_username));21:56
Laneyluverly21:57
forestoHi, all.  I'm packaging a driver module that was removed from ubuntu ages ago. Someone forgot to remove the man page from the ubuntu 'manpages' package when the driver was removed from ubuntu, so my new package (which contains an updated man page) now clashes with 'manpages', and dpkg won't install it. What is the best way to avoid the conflict?22:02
cjwatsonyou could give the man page a slightly different name; perhaps append a short string to the section number22:06
cjwatson(called a "section extension" - see e.g. the "3pm" pages documenting perl modules)22:07
cjwatsonluist_: OK, I've uploaded a dh-make fix to oneiric-proposed as well now (waiting for review) and forwarded the patch to Debian22:07
forestoI'm considering that. Is there an officially blessed (by debian/ubuntu) way to handle this?22:08
cjwatsonluist_: so the next person shouldn't have the same problem, hopefully22:08
cjwatsonforesto: not that I know of, but I maintain man-db so I guess my advice is about the best approximation to that you'll get ;-)22:08
forestoThanks, cjwatson.  I've filed a bug on the dangling man page, too.22:09
cjwatsonright, and if that gets fixed then you could rename the page in your package and add Breaks/Replaces on manpages; but until then (and for <= oneiric) I'd definitely advise working around the file conflict22:10
cjwatsonare the pages basically the same between manpages and your package?  is there a problem with people getting the manpages version if they have that installed?22:10
cjwatsonoh, you said updated, hmm22:10
cjwatsonthere probably isn't an ideal short-term solution22:10
luist_cjwatson: :)22:11
cjwatsonI suppose you could dpkg-divert away manpages' version, but that feels rather heavy-handed to me22:11
forestoYeah, it's the sk98lin driver, and the one in manpages is ancient. Options have changed since then.22:12
maxbooi, what would be the downsides to having the new package declare a Replaces: manpages ?22:15
maxbOr, would that all go horribly wrong the first time manpages was updated after the custom package was installed?22:16
cjwatsonmaxb: I think we did make that work in dpkg a while back (dapper, maybe)22:28
cjwatsonmaxb: but even so, I kind of take the attitude that anything I have to look up in dpkg source to conclusively determine its behaviour may not be a good idea :-)22:28
cjwatsonI think it's best to avoid file conflicts wherever possible22:28
DoctorPepperhi guys !!!22:30
forestoI did see the note in the debian policy about using Replaces: when a package takes over a file from another package, but it looked to me like it was intended for use when a new package takes over the duties of an old one. That's not really what's going on here.22:31
DoctorPepperagateau:  are you here ?22:32
cjwatsonforesto: it is used for single files moving between packages too.  I prefer to only use it consensually though (i.e. when the file is actually moved, not just to slam something over the top of an existing package that still ships the file).22:36
cjwatsonthe definition of Replaces is a little confusing as it does double duty depending on whether the packages also Conflict or not.22:36
forestoYes, that usage was hinted as well. Thanks for making sure I didn't miss it.22:36
forestoOkay, so I have the man page in a subsection now (4opt), but of course, it doesn't show up unless the user runs "man -a sk98lin" or "man 4opt sk98lin". Anyone know if there's a subsection that would override section 4 as the default?23:13
forestoAn appropriate subsection, that is.23:13
forestoand thanks, cjwatson.23:16
penguin42the order seems to be set by /etc/manpath.config23:17
forestoThanks, penguiin42.  Hm... None of the sections preceding 4 really apply, but since it's just a temporary workaround until the ubuntu manpages bug is fixed, maybe I could put the new man page in section 8.23:22
foresto(It is a network module after all, and there are plenty of network-admin-related things in section 8.)23:23
slangasekforesto: section 8 is "system management commands"; a network module doesn't sound like it belongs.23:40
slangasek(cf. man-pages(7))23:40
forestoslangasek: Yes, note my comment two lines up:  None of the sections preceding 4 really apply.23:42
forestoIMHO, it's more important to avoid giving the user bad instructions on the use of his kernel driver than it is to adhere perfectly to the section categories, and since this is only a temporary workaround and only necessary due to a bug in the stock manpages, I think abusing section 8 a little is warranted.23:44
forestoIn other words, I'd rather annoy someone for bending the man section rules than really screw someone by leading them to render their system unbootable.23:46
infinityforesto: Why not just fix the manpage shipped in manpages?23:46
slangasekforesto: well, if you're just putting it in a section where it doesn't belong as a workaround, rationalizing which section is less bad than the others to abuse is unnecessary :)23:46
slangasekto someone who cares about the sections, it'll be in the wrong section; to someone who doesn't, any section will do23:47
forestoslangasek: heh... point taken. I'm just trying to do this as well as I can.  :)23:48
forestoinfinity: The bug is already filed. I don't have the power to alter the official manpages package, and I don't think anyone has the power to retroactively do it on packages that have already "shipped".23:49
infinityWell, we can push updates, if it matters deeply.23:49
infinityBut you could just dpkg-divert the manpages' copy out of the way too.23:50
forestoYour suggestion would make sense if my package was not going to be released until manpages is fixed. I'm releasing in a PPA though. Today.23:50
forestoWe talked about dpkg-divert a couple hours ago. cjwatson didn't like the idea.23:50
infinityHe just said "that feels heavy-handed".23:51
forestoYea.23:51
infinityIt's still more correct than throwing the manpage in the wrong section to force it to have priority. :)23:51
infinityI'm pretty sure he didn't suggest that either. :P23:51
forestoActually, he suggested using a subsection.23:52
infinityRight.23:52
forestoA subsection  to the existing section doesn't solve the problem.23:52
infinityBut then you disliked that because it won't sort the way you want.23:52
forestoNo.23:52
forestoBecause it leaves the average user with bad instructions on configuring rather delicate part of his system.23:53
infinityIt's a NIC driver, not a nuclear reactor.23:55
infinityBut yeah, having the right info is nice.23:55
infinitydpkg-divert still sounds like the right solution to me for a third-party package that wants to overwrite files without overwriting.23:55
infinityWhich is, in the end, what you're after.23:55
forestoIt's very possibly the user's only convenient connection to the net, which means a misconfiguration would leave him unable to easily find out how to fix it.23:56
forestoTo be fair, I do see your point.23:56
forestodpkg-divert seems heavy-handed to me too, but I'll consider it.23:57
infinityWell, it's the "right" solution to the problem.23:58
infinityHaving manpages in the wrong section thwarts people like me who read by section intentionally.23:58
forestoNo wonder you're pushing so hard for it. :)23:59
infinityFor instance, I'm used to typing "man 2 open", and if I ever read manpages for kernel modules, I'd probably instictively read "man 4 sk98lin".23:59
infinitySo, I'd still get the wrong info if you shove it in section 8.23:59

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