| drkokandy | I like the idea from earlier of filing bugs against the manual. I was able to patch a few bugs in ubuntu server documentation once that might have been hard for the user to change him or herself. | 00:56 |
|---|---|---|
| === aaron is now known as ahoneybun | ||
| wxl | Nairwolf: hai | 15:17 |
| Nairwolf | hi ;) | 15:17 |
| wxl | saw your email but haven't looked at the code i'm sorry to say | 15:18 |
| wxl | i'll study up on lxml and get back to you | 15:18 |
| wxl | ok? | 15:18 |
| wxl | feel fre to share it around, though | 15:18 |
| wxl | i know ianorlin and Kamilion both grok python | 15:19 |
| Nairwolf | okay, but you'll see my code isn't finished yet | 15:19 |
| ianorlin | hmm why wasn't I highligted there? | 15:19 |
| wxl | under stood | 15:19 |
| Nairwolf | I thought that information about broken links were children of node where there is the source of broken link. | 15:20 |
| Nairwolf | Not sure it's clear | 15:20 |
| wxl | that makes sense | 15:21 |
| Nairwolf | okay, as soon as, I'll have time, I will try to make more test on lxml | 15:21 |
| Nairwolf | what means "grok" ? | 15:22 |
| wxl | understand | 15:23 |
| wxl | it's from a book | 15:23 |
| wxl | https://en.wikipedia.org/wiki/Grok | 15:23 |
| Nairwolf | okay, nice ;) | 15:26 |
| Nairwolf | I hope oneday I'll grok python ;) | 15:27 |
| wxl | heheheh | 15:27 |
| gsilva | Hi guys | 17:05 |
| gsilva | brb | 17:10 |
| Kamilion | you rang? | 17:54 |
| wxl | naw, Kamilion. just telling florian he can ping off of you if he needs python help, too. | 17:55 |
| Kamilion | ah, a'right | 17:55 |
| wxl | !info qtqr | 18:33 |
| ubot93 | qtqr (source: qr-tools): Qt frontend for QR code generator and decoder. In component universe, is optional. Version 1.4~bzr21-1 (wily), package size 28 kB, installed size 188 kB | 18:33 |
| Kamilion | hm, how do I easily get a link for LP#1446767 | 19:38 |
| Kamilion | hm so it'll just pick up bug 1447654 in plaintext | 19:51 |
| ubot93 | bug 1447654 in policykit-1 (Ubuntu) "installing policykit-1 hangs under systemd" [Medium,New] https://launchpad.net/bugs/1447654 | 19:51 |
| ianorlin | I found out it is possible but manual partitioning in ubiquity is quite difficult | 22:12 |
| Nairwolf | do you know how the development of the next release will be organized ? | 23:14 |
| wxl | Nairwolf: i think, from what i can tell so far, the next two releases will continue to be bug fix releases | 23:14 |
| wxl | in the background, of course, we'll be working on lxqt | 23:15 |
| Nairwolf | okay, but for 15.10 there will have gcc 5 and maybe python 3, no ? | 23:15 |
| Nairwolf | Oh, yes, lxqt, almost forget it | 23:15 |
| wxl | yes, but that's universal for all of the ubuntu ecosystem | 23:15 |
| Nairwolf | so, there will need some guys to test that | 23:15 |
| wxl | so it will be nice to not have to worry abotu those things at the same time | 23:16 |
| Nairwolf | okay, so, for this (gcc, python, and maybe snappy), it will be the ubuntu core team which will do that ? | 23:16 |
| wxl | by that do you mean lxqt or gcc/py? | 23:16 |
| Nairwolf | for lxqt | 23:17 |
| wxl | well, they'll be involved in managing the transition for the core pieces | 23:17 |
| wxl | it may affect us but ultimately we'll probably just point the core team back at it | 23:17 |
| Nairwolf | the lubuntu-qa team will need to test that | 23:17 |
| wxl | and/or release team | 23:17 |
| wxl | yeah it's an ongoing thing | 23:17 |
| Nairwolf | okay, I see | 23:17 |
| wxl | just like with the systemd transition | 23:17 |
| wxl | which ultimately didn't affect us at all | 23:17 |
| wxl | i have high hopes honestly | 23:17 |
| wxl | also i prefer py3 so :) | 23:17 |
| Nairwolf | yes, me too | 23:18 |
| Nairwolf | and for the next release of lubuntu 14.04 ? (It's 14.04.3 I think). Any specific work ? | 23:19 |
| Nairwolf | I've read there are already daily ISO. Testing will always be "use the distrib and report any bugs" ? | 23:24 |
| Nairwolf | Because, I'm think to use 30Gb to install Lubuntu on my prod computer, and always save my Xubuntu system, in case of bugs. | 23:25 |
| Kamilion | O_o | 23:45 |
| Kamilion | 30GB? that seems a little large. | 23:45 |
| Kamilion | oh, the partition itself | 23:45 |
| Nairwolf | In fact, I've 85Go free in my computer | 23:46 |
| Kamilion | Go? | 23:47 |
| * Kamilion thinks | 23:47 | |
| Kamilion | Gigaoctets? What a strange way to describe it. | 23:47 |
| Nairwolf | why ? | 23:47 |
| Nairwolf | How do you write this ? | 23:47 |
| Kamilion | I havn't heard of anyone using Octal since the DEC Alphas running Compuserve | 23:47 |
| Nairwolf | Maybe, I use the french format... | 23:48 |
| Kamilion | Oh, I see. | 23:48 |
| Nairwolf | oh, sorry, Gparted told me it's Gio | 23:48 |
| Kamilion | Standard would probably be gibibits or gibibytes | 23:48 |
| Kamilion | Gib or GiB | 23:48 |
| Nairwolf | It's not what I've on Gparted | 23:48 |
| Kamilion | versus Gigabits or Gigabytes, which != Gibibits/Gibibytes | 23:49 |
| Nairwolf | If I right, 1 Go = 10^9 octols, right ? | 23:49 |
| Kamilion | http://en.wikipedia.org/wiki/Gibibyte | 23:49 |
| Kamilion | giga is 1000, gibi is 1024 | 23:49 |
| Nairwolf | okay, in french we always say Giga, but, I suppose it means Gibi | 23:50 |
| Kamilion | so gigaoctet is same as gibibit | 23:50 |
| Kamilion | as gigaoctet implies 1024 | 23:51 |
| Kamilion | not 1000 | 23:51 |
| Nairwolf | yes, for me, gigaocte implies 1024 and not 1000. | 23:51 |
| Kamilion | bleh. SI prefixes are so unfun. | 23:51 |
| Nairwolf | in fact, in french language we never use Gibi | 23:52 |
| Kamilion | Gigabytes (1000) are used by the hardware manufacturers | 23:52 |
| Kamilion | Gibibytes (1024) are used by the software providers | 23:52 |
| Nairwolf | And it's always bytes | 23:52 |
| Nairwolf | but we say "Gigaoctet" | 23:53 |
| Nairwolf | octet = byte | 23:53 |
| Kamilion | there's gigabit as well, divide gigabyte by 8 | 23:53 |
| Kamilion | or multiply gigabit by 8 to reach byte | 23:53 |
| Nairwolf | Yes, I know that | 23:53 |
| Kamilion | at least the french representation is mathmatically more correct than gigabyte | 23:53 |
| Kamilion | :) | 23:53 |
| Nairwolf | And sometimes bad company use the term of Gigabits in order to loose consumer. | 23:54 |
| Kamilion | well, the context is normally different | 23:54 |
| Kamilion | bytes are normally used for storage, bits are normally used for transfers | 23:54 |
| Nairwolf | I not sure because we always say Giga, you can never say if it's 1000 or 1024. You need to precise if you want to make some calculs | 23:54 |
| Kamilion | so it is normal for networking to say megabit or gigabit, where it is not normal for storage to say megabit or gigabit unless they are indicating transfer speeds | 23:55 |
| Kamilion | computer history is strange :) | 23:56 |
| Nairwolf | No, I speak about storages in USB, Ipad, or Ithings. They use Gb, and I'm sure that the average people don't know the difference. Because, of course X Go is bigger than X Gb | 23:56 |
| Kamilion | Flash memory is often specified in megabits | 23:56 |
| Nairwolf | hum, yes, it's true | 23:57 |
| Kamilion | as a result of the 4096 bit page size | 23:57 |
| Kamilion | and they will always have exact multiples | 23:57 |
| Kamilion | unlike hard discs, which have varying sectors per track and may not end up on a whole multiple | 23:57 |
| Kamilion | or allocate some space internally for firmware use (common on western digitals) | 23:58 |
| Nairwolf | oh, I understand why you didn't understand firstly. Because first time I write this wrong (Gb), and then I use the french representation (Go as octet means byte) ;) I'm too tired tonight | 23:58 |
| Kamilion | no worries, I've been on IRC for 20 years, not only can i speak typo, I'm also used to international chatters | 23:59 |
| Nairwolf | yes, it's true what you say about western digitals | 23:59 |
| Kamilion | i was around for the big "am brazil" invasion of efnet long ago | 23:59 |
| Nairwolf | I've been on IRC for less one year ;) | 23:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!