/srv/irclogs.ubuntu.com/2016/05/18/#ubuntu-devel.txt

=== yuning-afk is now known as yuning
=== marcusto_ is now known as marcustomlinson_
=== freeflying__ is now known as freeflying
=== Logan_ is now known as Logan
=== farblue_ is now known as farblue
=== nobuto_ is now known as nobuto
=== Bluefoxicy_ is now known as Bluefoxicy
=== inaddy is now known as tinoco
=== Zic is now known as Guest59663
=== lewq_ is now known as lewq
=== marcustomlinson_ is now known as marcustomlinson
pittibdmurray: we could surely; we can't search for HookError_* attachments?05:34
pittisarnold: great to hear!05:35
sarnoldgood morning pitti :)05:36
sarnoldpitti: do you mean to find bugs like 1582992 ?05:37
pittiyes05:38
sarnolddoes that mean I get to skip reporting them when I find them? :)05:38
pittidepends, if we want to track SRUs of broken hooks, or not assume that everyone looks for this tag, we should probably continue to have proper bugs for them05:39
sarnoldthat makes sense05:40
karstensrageit takes me about 20 minutes to test out my modules, they kind of go together so you can test them both at the same time05:56
karstensrageso round to 1 hour, could i offer 4 hours of my time testing another backport request or w/e in trade for getting my backport requests looked at?05:56
karstensragemichagogo if you are micahg would that be something you would consider?05:57
karstensragethe four hours is just something to consider, like nothing like tomcat or java but something in the same ballpark as my modules in terms of effort and cognitive load and ill offer to do two or something06:00
sarnoldkarstensrage: btw, what does the backports offer that e.g. a ppa doesn't? either method requires administrator effort to install, right?06:01
karstensrageyes06:01
karstensrageeither method should be done by an administrator06:02
estanhi, sorry if this is obvious, but what's the policy of updating packages in 16.04, will only security fixes go in? because 16.04 was released, quite unfortunately, with Octave 4.0.0, which had several bugs. 4.0.2 (which is now in Debian stretch / sid) is much better. any chance of it being updated?06:02
sarnoldestan: you can SRU updates, it takes some paperwork and testing, but ought to be tolerable: https://wiki.ubuntu.com/StableReleaseUpdates06:03
estansarnold: thanks! we're basing our product on 16.04, and compiling Octave is such a chore.06:11
cpaelzergood morning06:13
michagogokarstensrage: eh? Don't know who that is06:15
estansarnold: i'm a bit new to this, do you know if the procedure for requesting SRUs is special in any way when the updated package is in stretch?07:13
estansarnold: should i just refer to the debian package and suggest they pull it, with a motivation why the bug is grave? (in this case, it's a regression with the risk of data loss).07:16
sarnoldestan: a sync from debian may indeed be useful.. the 4.0.1 changelog was -huge-.. I didn't spot a 4.0.2 changelog, is it similar?07:17
estanbut i realize now that not all changes in octave 4.0.1 and 4.0.2 are okay for SRU, so maybe just that fix should be included?07:17
estanhold on, i'll have a look.07:17
sarnoldback in the day there used to be a "MicroReleaseException" process that packages could apply for...07:18
sarnoldit's been mostly extended to anything with high-quality release processes... I hope that includes octave, but it may not.07:18
estanyea. i'm not sure. i would hope it does :)07:19
RAOFHigh quality release process or significant in-archive testing.07:19
RAOF(ie: If you've got an excellent set of DEP-8 tests you may also win)07:19
estanhm okay.07:22
estanthe changelog for 4.0.2 was smaller (had to look in the archive for it: ftp://ftp.gnu.org/gnu/octave/octave-4.0.2.tar.gz).07:22
estanbut considering the many changes, perhaps it's better to request the 4.0.0 package be patched with the fix i'm thinking of? (it's a bug in the reading of HDF5 format using Octave's open(..): http://savannah.gnu.org/bugs/?45225).07:24
estanerr, load()/save().07:25
sarnoldthat would probably be easier07:26
sarnoldbut that changelog.. heh07:26
estanyea.. i don't feel like doing an SRU for all that now :)07:26
estanthis is the fix: http://hg.savannah.gnu.org/hgweb/octave/rev/d54aa96abadf , and they added a test case for it.07:27
estani'll try to make a patched package then (never done it before). in the middle of a dist upgrade atm, so it'll have to be a little later.07:28
sarnoldyeah that patch looks way easier to sru :)07:28
estanthe existing 4.0.0 package seems to do "make check" as part of the package building, and the tests seems fairly thorough, so that's good.07:32
=== Guest59663 is now known as Zic
farblueHi all :) I think I know the reason for the problems I’m having with my fan network setup and it’s the SNAT rule added to iptables by fanctl. I need the ‘to:’ to be a different IP address. does anyone know a sensible way to configure this?08:27
TJ-cyphermox: could you tell me if bug 1582899 (live-installer / expert mode) is one of your areas of interest still?08:32
ubottubug 1582899 in live-installer (Ubuntu) "in-target: mkinitramfs: failed to determine device for /" [Undecided,New] https://launchpad.net/bugs/158289908:32
=== TJ_Remix is now known as TJ-
=== farblue_ is now known as farblue
=== ackkk is now known as ackk
=== plars_ is now known as plars
=== xnox_ is now known as xnox
=== tedg_ is now known as tedg
=== robru_ is now known as robru
=== Ursinha_ is now known as Ursinha
=== balkamos_ is now known as balkamos
=== dgadomski_ is now known as dgadomski
=== michagogo_ is now known as michagogo
estanhm, could someone help me with the bzr command to get the xenial-proposed of the octave package? i'm trying to make my first patch.09:17
caribou_estan: I don't see any octave in xenial-proposed but there is one in yakkety-proposed;09:21
caribou_estan: you can get it with pull-lp-source octave yakkety (from the ubuntu-dev-tools package)09:21
pittiestan: there are no more automatic (UDD) bzr branches for xenial, just use apt-get source or pull-lp-source ^09:22
estancaribou_ pitti: alright. my end goal is to create a bug report + SRU for http://savannah.gnu.org/bugs/?45225#attached , it's just that i've never done any Debian packaging, and never used bzr, so i'm a little lost :p09:25
estani started with the Getting Set Up guide to get a launchpad account, GPG key etc, and now working my way through http://packaging.ubuntu.com/html/fixing-a-bug.html09:26
caribou_estan: Traditional packaging might be more helpful in your case : http://packaging.ubuntu.com/html/traditional-packaging.html09:30
FourDollarshappyaron: Could you help to sponsor my patch for https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582301?09:37
ubottuLaunchpad bug 1582301 in network-manager (Ubuntu) "/usr/bin/nm-connection-editor:11:recheck_pending_activations:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit" [High,In progress]09:37
=== sil2100_ is now known as sil2100
ckingis there any reason why libjson0-dev is not in yakkety?10:19
cjwatsoncking: replaced by libjson-c-dev10:23
ckingcjwatson, ok, thanks10:23
cjwatsoncking: (it was a transitional package in xenial)10:23
ckingcjwatson, ah, I should have spotted that10:23
TJ-cjwatson: do you have anything to do with live-installer package any more?10:25
cjwatsonTJ-: no10:25
TJ-cjwatson: thought so but worth the ask :)10:25
TJ-cjwatson: 2nd (and last!) Q: Do you know if with the ubuntu-server ISO installer, it selects between base-installer and live-installer depending on whether boot-time 'expert mode' is selected?10:27
cjwatsonTJ-: err I don't think so, IIRC that's purely about how the image was built (i.e. it uses live-installer if it's present); if you need to disable live-installer then you can preseed live-installer/enable=false10:30
cjwatsonTJ-: but the ISO image won't have the debs required for base-installer to work so that probably isn't very useful :)10:31
TJ-cjwatson: OK, the reason for asking is a user reported a weird bug in expert mode that boils down to live-installer not mounting devtmpfs in the /target/ before doing update-initramfs, resulting in failing to locate the device for /10:31
TJ-cjwatson: I noticed the ISO's pool/ does have base-installer but I failed to understand if it was used in any circumstance.10:32
cjwatsonTJ-: base-installer has common code used by both the bootstrap-base and live-installer frontends10:32
TJ-cjwatson: the bug seems to be that the live-installer postinst script has the crucial "waypoint 1 setup_dev" commented out10:32
cjwatsonTJ-: so it's actually about switching between bootstrap-base and live-installer, not switching between base-installer and live-installer10:33
TJ-cjwatson: I'm failing to understand why it only fails in expert mode10:33
cjwatsonpass10:33
TJ-cjwatson: ahhh, bootstrap-base, yes, that was the code I was reading originally before I spotted live-installer running10:33
TJ-I'll bug cyphermox about it when he's around :)10:35
happyaronFourDollars: is it accepted by upstream? if so no problem11:07
FourDollarshappyaron: It is not accepted by the upstream yet, but seb128 asks me to work with you.11:17
seb128FourDollars, happyaron, it was discussed on the upstream list, but yeah we should maybe wait for them to review/ack to backport/upload11:18
=== bluesabre1 is now known as bluesabre
=== hikiko is now known as hikiko|ln
=== tai271828_ is now known as tai271828
=== \b is now known as benonsoftware
=== dobey_ is now known as dobey
=== hikiko|ln is now known as hikiko
=== Pici` is now known as Pici
=== henrix_ is now known as henrix
=== _salem is now known as salem_
=== caribou_ is now known as caribou
=== Son_Goku_ is now known as Son_Goku
rharperHi, I've a debdiff that fixes 3 bugs I've filed against bridge-utils package;  should I attach the same debdiff against each bug? Or create separate patches/debdiffs for each one individually?13:45
cyphermoxrharper: you can attach it to just one, I'll review it now?13:49
rharpercyphermox: sure13:49
rharpercyphermox: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/157685813:51
ubottuLaunchpad bug 1576858 in bridge-utils (Ubuntu) "brctl provides no way to set gc_timer value of a bridge" [Undecided,New]13:51
rharperthe other two are: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1576876 and https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/157687013:52
ubottuLaunchpad bug 1576876 in bridge-utils (Ubuntu) "bridge-utils: /etc/network/if-pre-up.d/bridge doesn't handle multiple stanzas of bridge_portprio" [Undecided,New]13:52
ubottuLaunchpad bug 1576870 in bridge-utils (Ubuntu) "bridge-utils manpage contains incorrect max for portprio" [Undecided,New]13:52
TJ-cyphermox: could you at some point look at bug 1582899  - not sure if you're still covering the package13:54
ubottubug 1582899 in live-installer (Ubuntu) "in-target: mkinitramfs: failed to determine device for /" [Undecided,New] https://launchpad.net/bugs/158289913:55
pitticjwatson: hey Colin, how are you?14:01
bdmurraypitti: Easily search LP for bugs with an attachment name? Not as far as I know.14:01
pitticjwatson: do you still remember how http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt is produced?14:02
pitticjwatson: I find a reference in britney1-ubuntu run_b1(), which calls ./update_out.py; but neither run-proposed-migration nor britney1-ubuntu actually seem to call that14:02
sinzui rbasak: is there anything I need to do regarding the backport of juju 1.25.5 to wily and trusty per bug 1556981 . Do I poke someone on the SRU team?14:02
ubottubug 1556981 in juju-core (Ubuntu Wily) "[needs-packaging] Juju 1.25.5 is not in wily and trusty" [Wishlist,In progress] https://launchpad.net/bugs/155698114:02
pitticjwatson: and I don't see another invocation of update_out.py (and it looks like update_output.txt is what this script produced)14:03
cyphermoxrharper: sorry, got distracted by half my coffee going in my cup, and the other half oozing from all sides of the machine onto the countertop14:12
cyphermoxrharper: -can have a fractional part.14:12
cyphermox+can have a fractional part.  Available on kernel versions < TBD ?14:12
rharpercyphermox: thx;  right;  I'll update with the data;14:13
cyphermoxother than that it seems alright14:15
cyphermoxit's for xenial?14:15
rharpercyphermox: it's not available on any of the supported kernels we have;  I just need to find which kernel release dropped that14:15
rharpercyphermox: yakkety and it ideally should go back to X and T and P IMO;14:15
rharperthe big issue is the per-port settings14:16
cyphermoxok. your changelog reads xenial14:16
rharperthat's where I tested it14:16
cyphermoxcool cool14:16
rharpersince I didn't have a yakkety cloud-image yet14:16
rharperalso, thoughts on whether the bridge script should be -e ?14:16
rharperset -e ;14:16
cyphermoxI'd be tempted to say no14:16
rharperwhen you apply values to things like port priority and it fails14:17
cyphermoxwould it be better to not have a bridge or to have a partial bridge with maybe missing options?14:17
rharperI suppose it depends on the configurer of the bridge14:17
rharperif you left stp on for example14:17
cyphermoxoh, yeah14:17
rharperthat might cause trouble for networks with loops14:17
cyphermoxit definitely would break in fun ways in that case14:18
rharperI'm not sure about the SRU impact14:18
rharperI would expect folks would have already complained14:18
cyphermoxfor SRU it probably should not be changed14:18
rharperbut it's a pretty clear bug that if someone on trusty did want to apply settings, they can't14:18
rharperright, the set -e; agreed;  what about the current patch for per-port settings ?14:19
cyphermoxit makes sense to me; I see not issue with it14:19
rharperok; let me clean up the manpage sentence on gc_timer/gc_int14:19
cyphermoxI'm not sure if it's a very common use-case, but this would work14:20
rharperit isn't I think14:20
rharperbut I was extending our bridge config testing in curtin14:20
rharperand wrote a testcase for validating bridge settings14:20
rharpernoticed the b0rkage and thus the bugs14:20
cjwatsonpitti: in britney1: britney:    cp $DATA_B2/output/$SERIES/output.txt $HTML/$SERIES/update_output.txt14:23
cjwatsonpitti: so then grep for just output.txt in britney2 and you'll find it14:23
cjwatsonor indeed case-insensitively for upgrade_output14:24
pitticjwatson: ah, thanks; so we don't use update_out.py at all?14:24
cjwatsonpitti: not the one in britney1, no.  I just didn't delete it to avoid making merges even harder14:24
pitticjwatson: background is, I'd like to add something like update_output_notest.txt which ignores autopkgtests, so that it's easier to untangle transitions14:24
pitticjwatson: thanks, that clarifies a lot14:25
cjwatsonpitti: Probably simplest to do a separate britney2 run with different configuration.14:27
pitticjwatson: right, that was the idea (with --dry-run or so, to not spit out the list of packages to migrate)14:27
pitti(that was HeidiResult or something similar, no?)14:28
pittiwith ADT_ENABLE=no14:28
cjwatsonsomething like that, yeah14:29
cjwatsonyou mostly just need to take care to avoid overwriting the delta from another run; britney2 doesn't do the actual copies itself14:29
cjwatsonI'd recommend generating the config dynamically in britney1, in order to avoid future problems with config drift14:30
cjwatsoni.e. sed over britney.conf14:30
pitticjwatson: *nod*; is HEIDI_OUTPUT that delta? or is it taken from output.txt?14:33
cjwatsonit's not taken from output.txt.  IIRC HEIDI_OUTPUT or something very similar is the delta14:35
cjwatsonyeah, HEIDI_OUTPUT sounds right.  (heidi is the old name for dak copy-suite, I think)14:36
cjwatsondak control-suite rather14:37
cyphermoxrharper: done?15:00
rharperyeah, lemme update the patch15:03
cyphermoxok15:04
rharperok, updated15:05
rharperfor 2.6.0 or older, you can have gc_int ; and port priority has max 255, default 128;, newer has no gc_int and a port priority of 63, defaults to 32.15:06
* rharper downloaded 2.6.0-tar.bz2 for the first time in like a decade 15:06
cyphermoxoh wow, that is kind of old15:06
rharperyeah, Linux git didn't have anything older than 2.6.1215:07
naccrharper: i think there is a historical linux tree15:24
naccrharper: but it's accuracy is ... imperfect :)15:24
naccrharper: i think it was a side-import from bk, not endorsed by Linus (I think technically he might not have been allowed to endorse it, random politics)15:25
rharpernacc: hehe15:40
karstensrageis there a better way to find a backport tester (42 members) than randomly pinging nick in irc?16:23
nacckarstensrage: i would think a 'backport tester' is anyone ... a backports team member is distinct?16:23
nacckarstensrage: meaning, if you have a backported package in a PPA, anyone could test it16:23
karstensragehttps://launchpad.net/~ubuntu-backports-testers16:24
karstensragenacc, how would i go about finding this "anyone"16:24
nacckarstensrage: well, i mean, if you're backporting something, there must be a use-case or bug or something. So you find people affected by that bug and they test it... ?16:26
karstensragenacc, this is just a new thing16:26
karstensrageit made into debian-testing, got pulled from unstable to xenial proposed and is now in xenial16:27
karstensragewould also like it in trusty and precise16:27
infinityWhat makes you think you need a third party tester?16:27
karstensragei dont know what i need, i cant get any traction on the backport, seems like the backport list is huge and no one is doing them16:27
infinityThe backports team might be a bit understaffed right now.16:28
infinityBut the testing stuff can be done entirely by you.16:28
karstensrageok done and done16:28
karstensrageso if thats the case, and since they understaffed, and its tested and working, can someone else just push the button?16:30
=== jgrimm is now known as jgrimm-afk
karstensrageinfinity, you might have been the one that pulled it into xenial16:41
infinitykarstensrage: I was, but I don't do backports stuff.16:42
karstensragei thank you for that, that was unexpectedly seamless16:42
karstensrageno freaking way16:45
karstensrageLaney, i could hug you16:45
estanhow long does it usually take between uploading a ppa package before i can see it there?16:46
karstensrageestan, usually very fast, or you get an email saying it was rejected16:46
karstensragelike 5 minutes?16:46
estankarstensrage: hm ok. weird. i uploaded quite a while ago and havent gotten a mail. the upload command was sucessful.16:47
karstensragecheck spam?16:47
karstensragethe upload can be successful but it still be rejected for all kinds of reasons esp if you dont change the version at all16:48
karstensrageLaney, if you have any questions please feel free16:49
karstensrageif you want my direct number i can provide that16:49
Laneykarstensrage: questions about what?16:49
Laneywhat's the best way to retire at 35?16:50
karstensragesell meth16:50
karstensrage:P16:50
estanyea, just thought i would have gotten a rejection by now in case somethibg was wrong. nothing in spam.16:50
estanwould it come from launchpad.net?16:50
infinityestan: You won't get an email if you forgot to sign it.16:51
karstensrageLaney, didnt you just handle one of my backports?16:51
karstensragei meant questions about the other one16:51
Laneydon't know16:51
estaninfinity: it refused to upload first since i forgot, then i signed and it succeeded.16:52
LaneyI handled some backports16:52
Laneydon't know if any of them were yours16:52
karstensrageoic16:52
Laneybut if you're happy, that's nice16:52
karstensragewell one was16:52
Laney:)16:52
karstensrageso thank you16:52
estanill look closer when im home, on the bus now.16:52
karstensrageLaney, would you consider doing the other one?16:55
karstensrageplease?16:55
LaneyIt depends on the first16:55
LaneySo I can't build it until that one is done16:55
karstensrageyes16:55
karstensrageit seems done?16:55
karstensragei see it in precise16:56
LaneyTakes a while to get to the mirrors16:56
karstensrageill check trusty16:56
karstensrageok16:56
estaninfinity: seems i signed with the wrong key. i thought i'd pick the one i set GPGKEY to in the environment, but i should have set DEBSIGN_KEYID (or passed -k).17:09
estaninfinity: meh: "Package has already been uploaded to ppa on ppa.launchpad.net". i uploaded with the wrong key. now i get that after trying to upload the debsign --re-sign'ed package. do you happen to know what i can do now?17:14
estaninfinity: ah, -f.17:15
estanworking now \o/17:15
=== wendar_ is now known as wendar
jynikI see that the releases linked from18:20
jynikhttps://wiki.ubuntu.com/Core all 404. Any chance someone could point me to the associated build scripts?18:21
rbasaksinzui: yeah it's waiting on the SRU team. See https://launchpad.net/ubuntu/trusty/+queue?queue_state=1 and equivalent for Wily.18:37
sinzuirbasak: oh, "unappoved" thank you. Looked at "new"18:38
sarnoldjynik: odd, try theseinstad http://cdimage.ubuntu.com/ubuntu-core/xenial/daily-preinstalled/18:44
jyniksarnold: Yeah, I did see those. Trying to lend someone a hand who was using the 14.04 LTS and not quite done getting ready to jump to the 16.04 LTS.18:45
jynikWas hoping I could at least find whatever build scripts/tools/etc. to rebuild the 14.04.x LTS Core image until they finish transitioning18:46
naccjynik: well, LTS -> LTS upgrades aren't offered ntil july anyways18:47
jyniknacc: I see. Even more of a reason for me to track down where the 14.04 Core images my colleague needs went then.18:48
jynikI'm hunting around the dev wiki - just having some trouble finding how these core images are built.18:49
dobeythere were 14.04 core images?18:49
ogra_yes18:50
jynikhttps://web.archive.org/web/*/http://cdimage.ubuntu.com/ubuntu-core/releases/14.04/release/18:50
ogra_they were renamed tto ubuntu-base18:50
dobeyoh18:50
jynikogra_: Ah, to avoid confusion with Snappy Core?18:51
ogra_look at http://cdimage.ubuntu.com/ubuntu-base/releases/ or some such18:51
ogra_yeah18:51
dobeythey are the pre-snappy minimal ubuntu installs?18:51
ogra_yeah18:51
dobeyah ok, that makes sense18:51
ogra_and they still get built, just under a new name18:51
jynikogra_: Thank you. While I have your attention - any chance you could point me to any docs on how these are being built?18:51
dobeyi guess someone should update the wiki page, and maybe add a "Base" wiki page and point people to it for old stuff18:52
ogra_they are built on a launchpad-buildd using live-build ... the config for it lives in the livecd-rootfs package18:52
jynikogra_: Excellent, many thanks.18:53
ogra_dobey, well, perhaps there are reasons that the page was removed completely ... slangasek would know18:55
dobeyogra_: ? https://wiki.ubuntu.com/Core is very much still there18:56
ogra_oh18:56
=== salem_ is now known as _salem
=== _salem is now known as salem_
hallynpitti: hey - i have a tiny reproducer package-set for bug 1579922 (left the code links in the last comment)20:01
ubottubug 1579922 in init-system-helpers (Ubuntu) "dh_systemd_enable fails due to 'preset' when service file is renamed" [Undecided,New] https://launchpad.net/bugs/157992220:01
hallynsolving that is the key to fixing the libvirt upgrade problem...20:01
hallynarges: bug 1583009 , is the fix you uploaded for libvirt?  (not seeing it in rmadison)20:06
ubottubug 1583009 in libvirt (Ubuntu) "Error starting domain since update" [Medium,In progress] https://launchpad.net/bugs/158300920:06
infinityhallyn: https://launchpad.net/ubuntu/+source/libvirt/1.3.4-1ubuntu220:20
infinityhallyn: You're just impatient. ;)20:20
hallyntis true.  thx20:21
hallynarges: libvirt in sid doesn't have that, i wonder if they have a reason.20:24
pittihallyn: cheers, I'll look at that20:25
patcablewhat's the usual length of time it takes from a package to go from being in -proposed to being something people will get when they apt-get upgrade?20:25
patcable(provided verification happened)20:25
infinitypatcable: About a week.20:26
patcableexciting, thanks20:27
Bluefoxicyfor point releases on Xenial, do you add new software packages to universe?20:34
infinityBluefoxicy: We sometimes add new packages, yes.20:38
Bluefoxicyinfinity:  cool.  What happens if a package is main and installed by default in a newer release, but also gets added to a prior LTS?  Does it go to universe?20:41
infinityBluefoxicy: It wouldn't be added to an older release without reason to do so, we don't just pull packages in willy-nilly.  So, "depends".20:42
Bluefoxicynod20:43
BluefoxicyI'm trying to write a zram manager and just curious what I should target as a long-term roadmap20:43
infinityA zram manager?  Does it really need management?20:44
infinityOr do you mean "enhancing zram-config to take a conffile"?20:45
BluefoxicyNo, I mean an active manager.20:45
BluefoxicyI can pull statistics on how much data is stored in zram and how much RAM it takes up; it's trivial to write a few simple rules to manage it--i.e. to determine if there's less than $Xmin or more than $Xmax available swap, if the amount of RAM consumed by zram swap is below $Y maximum, and so forth20:45
infinityYeah, that doesn't sound like a thing we'd pull back into a stable release.20:46
Bluefoxicyso you can say, "Use up to 50% of my RAM as zram", and zram will create swap space as it populates, and remove swap space as it depopulates20:46
jtaylorsounds a bit like you want to use zswap instead20:47
Bluefoxicythe problem with zram-config is it just says, "Make X amount of swap available"; if you fill it with almost-uncompressible data, it uses nearly so much RAM.  if you fill it with highly-compressible data, it uses almost no RAM.  You're rolling some dice and hoping for the best20:47
jtaylorits config is max percent of ram and doesn't reserve any ram20:47
Bluefoxicyjtaylor:  I'm not interested in writing back to disk as a cop-out to say "stop eating my RAM with this"; more importantly, I'm not interested in overprovisioning disk-based swap in an estimate of what's likely to achieve goals I can target directly.20:48
Bluefoxicylast I checked, zswap cached a disk swap partition into compressed memory20:48
Bluefoxicythat's interesting in its own right20:48
jtaylorusually your disk is much larger than ram so its not really much overprovisioning20:49
BluefoxicyI've long-abandoned disk-backed swap as any significant portion of swap space, though, because while 8MB of swap space is reasonable in a world where 16MB is a lot of RAM, 12GB of swap space is not usable in a world where you have 24GB of actual RAM20:49
sarnoldthe installer created a 120 gigabyte swap partition for me because I had 128 gigs of ram. this left about 800 megabytes for /.20:50
jtaylorhehe20:50
Bluefoxicysarnold: lol what20:50
jtaylorand then it still creats a 1gb boot which files up with like 5 kernels ;)20:51
Bluefoxicysarnold: a 5tb disk is like $110 now, goway20:51
sarnoldjtaylor: bingo :)20:51
Bluefoxicyjtaylor: RHEL6 still creates a 99MB /boot and then freaks out every time you try to upgrade if you already have 2 kernels installed20:51
sarnoldBluefoxicy: heh, I've got nine 3tb drives in this machine, plan on adding another six soon... the 120 gig SSDs are just for the OS :)20:51
Bluefoxicyinfinity:  anyway I figured it'd be useful as an available software package, but I'm trying to get away from the installer defaulting to making a swap partition--it would at least close bug #-99999Sarnold20:52
sarnoldoops. I broke Bluefoxicy :)20:53
Bluefoxicynegative overflow :)20:53
infinitySome use cases still need real swap, no matter how much we wish they didn't.  The first step to get away from swap partitions (by default) is to acknowledge that we can't create RAM out of thin air, but swap partitions suck, and switch to swap files.20:54
Bluefoxicythere's a swapd that creates swap files on-the-fly similar to what I described20:54
infinityIf you mix zram and swap files together, the fact that swap files are a bit slower and icker is made up for by zram giving you some breathing room, and everyone wins.  Ish.20:54
Bluefoxicywhy do some things need real swap?  Memory is just too tight?20:55
infinityNot everyone has gobs of RAM.20:55
infinitySuch is life.20:55
infinityNot all computers are created equal.20:55
infinityAnd, on the other end of the spectrum, some computers are HUGE, but run even more huge working sets.20:55
infinityAnd extending to disk beats not being able to compute your weird set.20:56
pittixnox: FYI, upstart autopkgtests have been looping/breaking testbeds since yesterday, I'll blacklist them now (i. e. they'll stay in progress, but they stop DoSing the workers)20:56
Bluefoxicygenerally the ones with minimal RAM are things like phones and tablets20:56
pittixnox: as the test workers are still KDE/Qt-DoSed, need to make some room20:56
infinityBluefoxicy: Or old computers that suck.20:56
Bluefoxicyon those architectures, it's traditional to not use swap because of some odd fear of destroying the nand20:56
infinityBluefoxicy: But, as I note, there's also the high end.  Some workloads just really need more RAM than it's feasible to buy, and slow beats not running.20:56
Bluefoxicyinfinity:  I think high-end HPEC and scientific computing are special cases and we shouldn't just partition out 9000 gigs of swap space because you might be building a nuclear bomb simulator :P20:57
infinityTo be fair, the installer can't really target those high end users, because we have no idea how much RAM they need.20:57
Bluefoxicyright20:57
infinityStill, "old computers suck" is a totally valid installation target.20:58
infinityJust because my laptop has 20G of RAM doesn't mean they all do.20:58
Bluefoxicyit's trivial to add functionality to create/use swap files at any path based on any rules20:58
sarnoldand it's amazing how quickly "new computer" turns into "sucky old computer".20:58
Bluefoxicyalso, in terms of old computers sucking, I don't think you can revive them by adding 2G more disk RAM to a 1G system20:58
BluefoxicyI tried that20:58
Bluefoxicywhat I got was "CHROME found another flash video that locks up my computer and requires me to unplug it"20:59
Bluefoxicythat has actually happened to me with 24GB of RAM installed and 4GB of swap, which is why I disabled disk swap entirely20:59
Bluefoxicy(it will ALSO happen with large amounts of lz4 zram, or zswap, of course)20:59
Bluefoxicy(...less bad, maybe, but it'll still happen)21:00
infinitysarnold: Yeah, I have a Nehalem i7 with 6G of RAM that may as well be a 486 for how crap it looks next to my laptop.21:00
Bluefoxicyhey man21:00
Bluefoxicythe 486 was a solid processor21:00
BluefoxicyQuake 1 had full, real-time, software-rendered 3D, but required a 486SX 33mhz with 8 megabytes of RAM21:00
Bluefoxicynot even a math coprocessor21:00
infinityIf by 486, you mean the AMD 5x86 486 clone, I agree.21:00
Bluefoxicywhich, mostly, worked because John Carmack is a freaking wizard from another dimension21:00
infinityEither way, my "beastly desktop gaming machine" is now "an old crap computer", just proving sarnold's point. :P21:01
Bluefoxicyha21:01
BluefoxicyI dispose of my machines after 10 years21:01
infinityThe Nehalem is a lot less than 10 years old. :P21:01
infinityHrm.  2008.  Well, not "a lot".21:02
infinityThat computer is a bit newer than that, though.21:02
BluefoxicyI got rid of my AMD64 X2 1.9GHz Barton core when a fan controller physically burned out from electrical wear due to being older than modern computing.21:02
BluefoxicyI then bought a Core i5 at 3GHz :)21:03
=== salem_ is now known as _salem
BluefoxicyExciting times.  The AMD64 would overheat and shut down the system at 1.9GHz, but not at 1.8GHz, so I had a CPU power management daemon throttle it to 1.8GHz if the CPU core temperature reached 78C, and unthrottle it at 75C21:04
* Bluefoxicy gets back to work21:06
JanCswap would be useful for moving leaked (and thus unused) memory out of RAM, except usually the leaked/unused memory is fragmented & mixed with used memory, meaning it get swapped in all the time  :)21:17
Bluefoxicythere are ways to fix tht21:17
Bluefoxicythat21:17
JanCin theory, yes21:18
JanCnot leaking memory would be a good start, not fragmenting memory would be good too  ;)21:18
Bluefoxicythings like Mono use compacting memory managers and physically colocate highly-used memory.  For non-managed memory allocators, it's a notably good strategy to allocate allocations from the same thread close together; allocate similar-sized allocations together; and allocate large allocations as anonymous mappings21:19
Bluefoxicysome 10 years ago I tried to write a ptmalloc replacement on Hoary, but I'm not a programmer and got myself in all kinds of trouble I didn't know how to resolve :P21:20
Bluefoxicy(I still say brk() is outdated)21:21
argeshallyn: it fixes the issue. yea wondering why they don't have it22:15
=== dx- is now known as dx
=== zequence_ is now known as zequence
dannfhallyn: do you mind if i upload this to y? https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1566564/comments/423:13
ubottuLaunchpad bug 1566564 in qemu (Ubuntu Xenial) "support query-gic-version QMP command" [Undecided,Confirmed]23:13
cjwatsons390x builders will be going down in about 25 minutes for maintenance; expected downtime about an hour23:15

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