=== freeflying_away is now known as freeflying [01:44] slangasek: http://bazaar.launchpad.net/~apachelogger/+junk/plymouth-stop-kdm/revision/1461 does that look sane to you? [03:19] Noskcaj: i think i was waiting on some feedback from some internal channels before merging [03:20] Noskcaj: for precise anyway, haven't done anything with trusty yet so feel free [03:57] So, uh, where's the libudev bug tracker these days? [05:06] Good morning [05:36] stokachu, I was meaning trusty, but i'm not really able to fix the ubuntu patch fot this [05:36] *for [05:46] Hello guys may I ask a question?? Does the locale of Ubuntu comes from Debian or glib [05:46] *glibc [06:11] arun: from upstream glibc, with some Debian and Ubuntu patches [06:12] pitti: that means if I upload my locale in glibc, it will be applied in Debian and Ubuntu ? [06:12] arun: yes; and we can even do that early, but we require a locale to be submitted (and if possible, reviewed) upstream before we include it [06:14] pitti: so, how can I upload the locale to Ubuntu that I have already done in glibc [06:14] pitti: should I have to again in Ubuntu if I have already done in glibc ? [06:14] arun: please open a bug against "langpack-locales" and give the URL to the upstream bug [06:15] pitti: so, when may the patch get update in distro? [06:15] arun: should be in the next couple of days then [06:15] or can I download the package of the updated one ? [06:15] arun: well, you submitted the locale upstream, I'd assume you have it actually installed to test it :) [06:15] pitti: then after that will the language packs get updated in Installer also? [06:16] arun: yes, then we'll build langpacks, as soon as we get them for trusty (they aren't enabled yet) [06:16] pitti: can't I apply or test it in my own system ? [06:17] pitti: I would I do that, I can't figure out !! [06:17] arun: how did you test it if you didn't do that? [06:17] *how [06:17] pitti: I just created the locales not tested it [06:17] please see "man localedef" [06:18] arun: you can copy it to /usr/share/i18n/locales/, add it to /usr/share/i18n/SUPPORTED, and then run "sudo locale-gen xx_YY.UTF-8" to test it like if it was shipped by the distro [06:18] with localedef you can build it without mucking around in /usr [06:22] pitti: ok wait ok , I am testing please be in touch [06:33] Pici: yes then what to do after locale-gen ? [06:36] pitti: are u there? [06:36] Pici: sorry [06:36] pitti: yes then what to do after locale-gen ? [06:36] arun: you run your program under that locale [06:37] LANG=xx_YY.UTF-8 gedit [06:37] or whatever else [06:37] or set it as system default locale to test everything [06:37] of course you won't have many translations (unless you installed a few from your translation efforts), but you can check time format and the like [06:38] pitti: yaa I wanted to check that time thing, how to ? [06:38] "date", or look in the panel [06:38] pitti: didn't work [06:41] pitti: it didn't get applied I think [06:50] pitti: hello are u there? [06:50] pitti: what should I do the next [06:51] arun: do you see your locale in "locale -a"? [06:51] pitti: no there no [06:51] so you didn't run locale-gen with your new locale name [06:53] pitti: I did [06:54] then it failed; do you get some error message ther? [06:54] pitti: no , I don't [06:54] arun: please pastebin the whole command that you ran and its output [06:54] pitti: I did this :- sudo locale-gen the_NP.UTF-8 and enter but no errr\or [06:55] pitti: and then did sudo locale -a and there is no the_NP in that list [06:55] arun: did you get the "Generating locales..." "the_NP.UTF-8... done" output? (pretty please just show me the whole output -- I can't pull every single piece of information like that) [06:56] pitti: no that thing didn't come [06:56] there is no such output , I mean no output [06:56] arun: then you didn't add it to SUPPORTED [06:56] pitti: i did it , dude [06:57] pitti: oh ya [06:57] pitti: I had missed it sorry [07:00] pitti: I had got an error in 1st try that is http://dpaste.com/1470055/ then in second attempt no errors output was without error [07:00] yeah, that's why you need to test a locale :) [07:01] so, apparently "the" needs to be added to some place I don't know [07:01] pitti: oh [07:01] pitti: but the date is not being appplied [07:02] so that localedef knows it [07:03] probably some place in libc which knows about the 2/3-letter iso codes [07:03] pitti: now its listed in locale -a [07:03] at this point this really needs a bug report [07:03] to track this between the different packages and upstreams [07:06] pitti: and when I type LC_TIME=the_NP.UTF-8 it says [07:06] bash: warning: setlocale: LC_TIME: cannot change locale (the_NP.UTF-8) [07:06] yeah, as the generation of the locale failed due to the unknown "the" [07:07] pitti: oh wait [07:12] Looking at the commit upstream, it looks like there might just be a stray "the" on the line before lang_term (or, perhaps, that was meant to be preceded with a "lang_ab") [07:13] +postal_fmt "/ [07:13] +" [07:13] +% the [07:13] +lang_term "" [07:13] +% the [07:15] Oh, wait, I'm reading that backward. [07:15] Yeah, that looks like it's right. [07:15] * infinity shouldn't try to understand new things at 7am. [07:17] infinity: ok [07:18] infinity: I think libc-bin (localedef) has some kind of compiled form from iso-codes which hardcode the available language names and 2/3 letter ISO codes [07:19] pitti: You think it's picking it out of localedata/SUPPORTED at compile time instead of runtime? That seems silly. [07:20] infinity: no, just the definition of "the"; localedef verifies that the language name is known (and what it actually expands to) [07:20] I'm not sure where that lives, though [07:21] yes guys have a look https://sourceware.org/git/?p=glibc.git;a=blob;f=locale/iso-639.def;h=56db3c81d53709194486bc579f0ec5cc4a14cc3d;hb=b46d046e7bf7e0f96e41e522da731b89177e31ab [07:22] looks like it [07:23] Ah-ha. [07:24] so, where that thing is compiled !! [07:24] So, the big question is, is Tharu/the defined by iso-639? [07:24] Oh, it's already in there. [07:24] 463 DEFINE_LANGUAGE_CODE3 ("Tharu, Chitwani", the, the) [07:24] infinity: yes, it's in /usr/share/xml/iso-codes/iso_639_3.xml [07:25] I'm just blind. [07:25] ah, but not in langpack-locale's copy of iso-639.def [07:25] so that needs to be synced [07:26] one more reason to merge them back to glibc :) [07:26] I didn't actually think it would be used/installed anywhere, though [07:26] it can probalby just go from langpack-loclaes [07:27] infinity, arun: or perhaps this has been added later than the ubuntu release arun is running this on? [07:27] It's not in the 2.18 iso-639 (and, of course, this locale isn't in 2.18 either), so if someone wants me to pull it back into 2.18, a bug filed would be nice, before I go fly for 12 hours and forget about this. [07:28] ah [07:28] arun: ^ what I said about "this needs an ubuntu bug report at this point to coordinate" [07:28] good morning [07:29] pitti: ok brother as this is a new locale , I had just added that in the glibc 2 days ago [07:30] arun: Indeed, I can see the upstream commits. But if you want it in a distro before 2.19 comes out, we need to pull some patches. If you don't care about it working until 2.19 is in the distro, you can do nothing and just wait. [07:31] (I'd do it now in my 2.18 packaging, but I'm literally 2 minutes away from closing my laptop and running to a train station) [07:31] the thing is the packing didn't worked for me that I tried [07:32] arun: So, if you want it backported, please file a bug on eglibc and assign it to "adconrad". If you're happy waiting for 2.19, wait. [07:32] infinity: when are u returning home? [07:32] arun: I'll be home in half a day or so. [07:32] * infinity runs off. [07:32] infinity: when will glibc get released [07:35] pitti: bro so whats next [07:35] pitti: what should I do [07:36] pitti: any way to test that crap ?> [07:36] arun: as I said, please file an ubuntu bug with pointing to the upstream bug where you submitted the locale (unless it's already committed), and we'll coordinate the glibc/langpack-locales uploads [07:36] arun: whoa, calling your work "crap"? [07:37] arun: you could locally build eglibc with that patch applied, but that will take a bit [07:42] pitti: oh thanks brother [07:42] pitti: thanks a lot [07:42] I will surely bug a report [07:46] pitti: when is LTS releasing? [07:46] arun: next April [07:46] pitti: oh that mean 6 months left? [07:47] arun, yep [07:47] and should I finish all the things before that to get it in it [07:48] arun, For the actual code, yes. translations can be added (i think) in LTS point releases [07:49] Noskcaj: what if the translations are not made in it, willl the work in it [07:50] Noskcaj: WILL IT BE AVAILABLE IN Language Option during installation ? [07:51] arun, If the code changes get done, and launchpad recognises the language, yep [07:51] Noskcaj: cool, yes Launchpad does [07:53] but the translations are done in another stream can we submit the po file to the maintainer later on ? === doko_ is now known as doko [08:57] @pilot in === udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.10 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: jamespage [08:57] morning folks [09:04] jamespage: hello [09:04] hey arun [09:05] jamespage: how are u ? [09:07] arun, all good here [09:07] jamespage: cool, are u in locale maintaining ? [09:08] Laney, just wondering, when do you think evolution 3.10 will be in ubuntu? [09:08] arun, not quite sure I understand the question - I'm on pilot duty this morning [09:08] so working through the sponsorship queue right now [09:08] jamespage, he's trying to add a new language to ubuntu [09:09] Noskcaj: yup like that [09:10] Noskcaj: once webkit stops being sad [09:10] ok [09:10] it keeps being oom killed on the porter box so I can't be sure if my fixes work :( [09:21] arun, can't help you with that - sorry [09:21] jamespage: ok [09:21] jamespage: thanks [09:42] is update-apt-xapian-index segfaulting in trusty for others as well? [09:45] just unity-panel-services yere. [09:48] xnox, do you have a backtrace? [09:50] seb128: whoopsie uploaded a crash & ubuntu-bug *.crash doesn't do anything to launchpad. [09:50] xnox, can you give me the error id? [09:51] xnox, you can access your list of report from gnome-control-center -> privacy iirc [09:52] xnox: the top three at https://errors.ubuntu.com/?package=unity-services&period=day is what I see. [09:53] seb128: ^ [09:53] seb128: to trigger, open oboard and wait or some such. eventually it has a fizzy fit. [09:53] xnox, is that on trusty? [09:54] xnox, but yeah, seems like a11y related, which probably explain why I don't see those, I didn't activate a11y === panda|x201 is now known as panda|w530 [09:57] xnox, it's weird, those 3 reports haven't been seen in versions > precise according to e.u.c (which is right, they got fix in quantal iirc) [09:57] seb128: you need a touch screen notebook ;-) [09:57] xnox, feel free to send me one ;-) [09:57] xnox, are you sure it's the same bug though? [09:58] no, but i have no idea how to force ubuntu-bug to upload a crash. it now says that my packages are obsolete, duh [09:58] anyway, need to do real work. [09:59] xnox, can you copy the file somewhere where I can download it? [10:02] xnox, just point ubuntu-bug at the crash file in /var/crash [10:04] you might need to retrace locally though, if you have obsolete packages [10:04] crash reports bit rot pretty fast ;( [10:25] arun: If you want a locale to be available during installation, you need to start work ASAP on getting debian-installer translated to it, and that work needs to be done in Debian. See https://web.archive.org/web/20130923213600/http://d-i.alioth.debian.org/doc/i18n/ [10:25] (alioth.d.o is down right now so you get an archive link ...) [10:26] cjwatson: yaa, its down so, I am in idle now [10:26] cjwatson: and how can I get the glibc compiled [10:26] Please don't ask me about that. [10:27] I'm just telling you that you need to start on this work in Debian as soon as possible because the translations will take some time to filter through to Ubuntu. [10:27] (And we don't enable new installer translations unless they've been done in Debian; it just doesn't scale for us.) [10:28] cjwatson: but the server is down now , isn't it .... [10:29] Yes, but that doesn't stop you getting started on some of the other parts of that. For example, have you contacted the d-i development team yet? Start from https://web.archive.org/web/20120401055952/http://d-i.alioth.debian.org/doc/i18n/ch03.html [10:31] hi doko, i saw you filed some failures about trusty complaining for not finding ac_nonexistent.h file, how did you solve it? it happens to me with couchdb [10:32] yolanda, hmm, can't remember, which ones I did file ... [10:33] http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.rtmidi_2.0.1~ds0-3_FAILEDTOBUILD.txt [10:33] so i'm seeing same errors when building couchdb for trusty [10:33] yolanda, well, I didn't fix these =) [10:37] doko, so you just left it, is there some issue with trusty then? [10:38] yolanda, most likely. but I didn't do a test rebuild for trusty yet. this was just the initial arm64 build [10:39] doko, ok, i'm adding some new features for trusty to that packages and having that problem. Not sure if just build for saucy instead [10:41] Hi there. Could somebody with the rights to do so accept the nomination of bug 1183580 for saucy? [10:41] bug 1183580 in librcc (Ubuntu) "[SRU] librcc segfaults on latest saucy" [High,Fix released] https://launchpad.net/bugs/1183580 [10:51] Ampelbein: done [10:52] pitti: Thank you. === _salem is now known as salem_ [11:16] yolanda: do you have a link to the full build-log? [11:17] xnox, just built locally, i can rebuild and pastebinit [11:17] yolanda: cause "ac_nonexistant.h" is usually a red-herring, it's used intentionally by autoconf to test non-existing headers =) [11:18] xnox, seems that cannot find any header [11:18] let me paste the log [11:18] yolanda: e.g. in http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.rtmidi_2.0.1~ds0-3_FAILEDTOBUILD.txt the actual error is: [11:18] checking build system type... Invalid configuration `aarch64-linux-gnu': machine `aarch64' not recognized [11:18] configure: error: /bin/bash config/config.sub aarch64-linux-gnu failed [11:18] after that it just does "cat" of config.log which has all internal details of what configure script did. [11:19] So, just a simple config.{sub,guess} update. [11:19] correct. [11:19] (Please use dh_autotools-dev) [11:19] infinity: snapping my answers =) [11:19] xnox: I don't board for 3 minutes, I need something to occupy my time. :) [11:19] infinity: =)))) [11:20] xnox http://paste.ubuntu.com/6436923/ [11:21] Missing build-dep. [11:22] Though, that seems hard, given that dpkg provides an install-info binary... [11:22] smoser, utlemming: are you OK with https://code.launchpad.net/~med/ubuntu-seeds/sosreport/+merge/179485 ? [11:22] inifinit, i double checked and i have that install-info package installed [11:22] infinity ^ [11:30] You may have but it's not in your build-deps [11:30] dpkg's version is in /usr/sbin/install-info so not on the default PATH for a package build; TBH trying to detect install-info in configure seems silly anyway [11:30] I guess it's using it in its "make install" [11:31] It's probably simplest to add a build-dep on install-info and move on === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === brainwash_ is now known as brainwash === MacSlow is now known as MacSlow|lunch [12:13] @pilot out === udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.10 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: === oSoMoN_ is now known as oSoMoN === psivaa is now known as psivaa-lunch === MacSlow|lunch is now known as MacSlow === chrisccoulson is now known as notchrisccoulson [13:45] seb128: hey. sorry. was on vacation last week. [13:45] dobey, hey! oh, nice, I hope you had fun ;-) [13:46] pitti: can you approve the binaries for nvidia-331 and nvidia-331-updates in NEW, please? [13:46] not as much as i wanted to, but it was ok :) [13:58] tseliot: done [13:59] pitti: great, thanks! === psivaa-lunch is now known as psivaa === bdrung_ is now known as bdrung === corvolino is now known as corvolino[work] [15:18] doko: is it ok if I re-introduce arm-linux-gnueabihf-gcc-4.6 into universe? it's still needed for ubuntu-touch development at the moment. [15:29] tseliot, hey, do you know if there is any known bug with nvidia drivers' xrandr support in 13.10? [15:29] tseliot, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254 [15:29] Ubuntu bug 1224254 in gnome-settings-daemon (Ubuntu) "xrandr Xerrors with the nvidia binary drivers" [Medium,Confirmed] [15:29] tseliot, not sure where to reassign? nvidia-drivers? [15:37] xnox, 4.6, are you joking? [15:38] doko: goldfish 3.4 kernels misscompile with 4.7 and FTBFS with 4.8. =/ [15:38] doko: $ apt-cache showsrc linux-goldfish | grep gcc-4.6 [15:41] seb128: let me check [15:42] Mirv: https://code.launchpad.net/~rsalveti/ubuntu/trusty/qtbase-opensource-src/android-emulator-workaround/+merge/195622 mind reviewing it? [15:43] Mirv: needed to get Qt working with the android emulator [15:44] tseliot, thanks [15:45] seb128: yes, that happens with hybrid graphics. It's a bug in either nvidia or in the modesettings driver [15:45] tseliot, can you reassign/add a comment? [15:46] seb128: sure [15:46] tseliot, thanks [15:54] xnox, which kernel version is this? [15:55] doko: goldfish is 3.4 but has plenty of emulator devices written by google / non-mainline [15:56] doko: grouper, manta, maguro, goldfish are all compiled with gcc-4.6. mako is the only touch kernel compiled with 4.7. [15:58] apachelogger: yep, looks sane [15:58] doko: see https://bugs.launchpad.net/ubuntu/+source/linux-goldfish/+bug/1236444 [15:58] Ubuntu bug 1236444 in linux-goldfish (Ubuntu Saucy) "kernel panic" [Undecided,Fix released] [15:58] which was "fixed" by compiling with 4.6. [16:11] xnox, just love that kinda fix [16:11] :-) [16:12] jamespage: the other day i was thinking to abuse multiple-tarballs of 3.0 formats and make an "automake-all" package which builds all automakes from 1.4 -> 1.14 [16:35] doko: please could you triage bug 1252290? I don't know why you temporarily demoted tomcat7 so not sure how to deal with this one. [16:35] bug 1252290 in tomcat7 (Ubuntu) "tomcat7 is disabled in the trusty server seeds starting from 20131115.1" [Undecided,New] https://launchpad.net/bugs/1252290 [16:37] dholbach, what's the website you use again to know what packages you sponsored for somebody? [16:38] seb128, http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi - but it's down with the rest of alioth [16:38] seb128: it's linked of qa.ubuntuwire.com (at the bottom) [16:38] dholbach, oh right, thanks anyway [16:38] xnox, thanks [16:38] seb128, here's what mitya57 suggested to do: http://paste.ubuntu.com/6416445/ [16:41] i really thought they'd have alioth back up after this weekend... [16:43] orbisvicis: i'm wathcing #alioth on OFTC, where nagios says, it's down. [16:43] dholbach, danke [16:44] if I want to revert a particular commit from an (ubuntu) source package maintained at alioth, would it be possible. Does ubuntu mirror anything? [16:45] orbisvicis: ..... all debian/ubuntu packages can be fetched with: pull-debian-source / pull-lp-source respectively and one can do anything to them.... [16:45] orbisvicis: if you know changes that you want to revert, that's easy to do. [16:45] orbisvicis: there are no mirrors. === dholbach_ is now known as dholbach [16:51] xnox: i don't know the commit in particular, but it is either fully upstream (which is maintained at git.debian.org [alioth]), or includes changes to the debian/ directory. Either case... pull-lp-source wouldn't track such commits? [16:52] ogasawara: pull-*-source download latest debian .src package. [16:52] ogasawara: unping. [16:52] You get the latest thing in the archive, but nothing from the vcs. [16:52] orbisvicis: pull-*-source download latest debian .src package. Not vcs history. [16:52] If there's history or new things there [16:53] orbisvicis: but e.g. if it's an individual patch under debian/patches, it's easy to revert. [16:53] orbisvicis: or you can look at commit-diff mailing lists if there is one for repository in question. [16:53] xnox: that's an idea, thanks. I' [16:53] ll give that a shot later === dholbach_ is now known as dholbach === notchrisccoulson is now known as chrisccoulson [17:48] barry: you seen this project yet : https://bitbucket.org/tpn/pyparallel/ [17:50] barry: http://vimeo.com/79539317 [17:57] I have a build failure I can't figure out: http://lpaste.net/3009038909163175936 [17:57] any other command in override_dh_auto_test works fine, and in the c10shell hook, I can run "xvfb-run -a dh_auto_test" without any problems [17:59] as well as make -f debian/rules override_dh_auto_test [18:01] Hello. Is there a video stream for UDS I can watch? [18:02] mathfreak_: The sessions take place in IRC and google hangouts (I think), just click the link on summit.ubuntu.com [18:03] Thanks! [18:14] think I figured it out... xvfb is automatically started once installed..? [18:37] jamesh, hey, wrt to go-dbus, how about making the trunk series point to your trunk branch? === salem_ is now known as _salem [18:40] stokachu: i haven't watched the latest video yet, but i was at trent's talk at pycon and i'm following the mlist thread. pretty cool and crazy stuff :) === _salem is now known as salem_ [18:50] barry: yea man pretty interesting === Guest79045 is now known as Vivek [19:37] Hi guys] [19:37] hi [19:38] can I talk about issues with my Ubuntu build (I used Ubuntu Builder) [19:38] hey ogra_ [19:39] yo [19:39] in the spirit of your blog post maybe there's room at UDS for a session on the update thing? [19:39] I'm having problems with my build of Ubuntu [19:39] IMO I bet the phased updates handle like 90% of what they're trying to avoid [19:41] jcastro, sounds good, think we can get clem to participate _ [19:41] ? === marcoceppi_ is now known as marcoceppi [19:41] if he's interested, sure, gotta start somewhere! [19:41] just having a session wont hellp if not the right people are in it [19:41] yeah, I mean, maybe it's something we do later or something [19:42] I just wanted to bring up that UDS is here and we've got the right people in the right virtual rooms [19:42] I'm currently running my build of Ubuntu 13.04. But instead of the XFCE Desktop Manager I wanted to see, I get Busybox. [19:46] allstarsnorks2: hi! I'm not sure, but ubuntu-builder seems to be a separate project, so maybe you'd have more luck reporting your problem to its developers... they have a bug tracker is on google code: https://code.google.com/p/ubuntu-builder/issues/list [19:46] allstarsnorks2: in fact https://code.google.com/p/ubuntu-builder/issues/detail?id=52 sounds similar to what you wrote above [19:52] Made a bug report [20:09] is unity development using this channel? [20:09] there is #ubuntu-unity i think === salem_ is now known as _salem [21:52] xnox: when testing the emulator, do you remember if it was also stuck sometimes? quite frequently it gets to a point where I cannot start any other program, like top [21:52] same kernel and emulator works fine with android, just wonder if something we might be doing or missing [21:53] * ScottK waves to ogra_. [21:53] I guess it's been a 'fun' day. [21:53] * ogra_ wavws back to ScottK [21:53] it has ! [21:54] :) [21:54] FWIW, I think Mint's default policy on updates makes it unsuitable for casual users, but that's just me. [21:55] well, they claim the updates make it unstable, if thats true there is clearly something to do on our side [21:56] (in fact they show you a scary dialog that points to "may harm your system" security updates, i think that could even be worse than suppressing them ... teaching people that security adds instability) [22:02] ogra_: well, all of the systems I manage (around 300 containers, 50 or so servers and a dozen desktops) are configured to apply any security and bugfix update automatically every hour (thanks to unattended-upgrade). I have seen breakage but nothing that we didn't fix immediately and nothing that could have really been prevented (the last in date being procps failing to upgrade in containers, requiring manual action to resolve...) [22:03] stgraber, right, i'm not really sure from when this Mint policy comes though ... we might have done worse in the past, might have burned them and now they are scared [22:03] would be good to hear a clear word about the reasons really [22:14] in the past linuxmint achieved some customizations by overwriting or editing dpkg-owned files in place without creating derived packages or even diverting... so installing updated packages from ubuntu would undo their changes [22:14] I don't have a linuxmint install handy, but glancing quickly at e.g. http://packages.linuxmint.com/pool/main/m/mintsystem/mintsystem_7.9.0.dsc it seems to still do the same sort of thing :| [22:14] anyone willing to sponsor this for me: https://bugs.launchpad.net/debian/+source/apt/+bug/1206047 [22:14] Ubuntu bug 1206047 in apt (Debian) "typo? in /etc/cron.daily/apt : MinAgeSec variable does not exist" [Undecided,New] [22:26] tarpman, oh my === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [23:03] hey can someone review my merge request: https://code.launchpad.net/~tjguthrie4600/ubuntu/trusty/apt/bug-1206047/+merge/195553 === freeflying is now known as freeflying_away