[02:32] <ausxxh> in ubuntu is tgt or iscsitarget default for openstack/cinder?
[05:47] <pitti> Good morning
[06:48] <dholbach> good morning
[07:02] <stgraber> chiluk: so, for bug 1057358, I didn't upload the fix, but it sounds like someone re-uploaded the exact same broken fix as last time... I said I'd take care of this when I had time but it looks like that wasn't good enough for somebody who went ahead anyway
[07:03] <stgraber> chiluk: for bug 1069570, the "fix" is a feature addition in isc-dhcp, so I have no plan to SRU it as it's against SRU policy
[07:48] <tkamppeter_> OdyX, I have released cups-filters 1.0.34, uploaded it to Ubuntu and committed it to the Debian BZR.
[07:58] <OdyX> tkamppeter_: aye. Won't have time today unfortunately.
[07:58] <pitti> tkamppeter_: need some Debian sponsoring?
[08:00] <OdyX> pitti: ah yeah, if you could upload it to experimental, it would be great.
[08:00] <pitti> OdyX: I'll update the changelog for Debian then
[08:01] <OdyX> pitti: of course. :-) .oO(And in these cases, uploading there first, and syncing looks like a good plan to me, but I'm not enough into Ubuntu to know…)
[08:04] <pitti> sbuilding..
[09:41] <apachelogger> Laney: yes (about kdiff3 and im-config)
[09:41] <Laney> ah, because I checked the Debian BTS list for im-config and didn't see it
[09:43] <apachelogger> I wasn't particularly in the mood to file tickets in all the broken software I saw yesterday, so I sent mails to the authors
[09:44] <Laney> if you add patch headers then people can find this information out without having to check with you
[09:48] <apachelogger> good point
[10:15] <tkamppeter> OdyX, pitti, I know that getting usually synced packages to Debian first is the better way, I only quickly upload into Ubuntu as we ara in a stage close to release and so the packages should get in quickly to get more testing.
[10:27] <OdyX> tkamppeter: yeah, np, as long as the general rule stays first-to-experimental-when-reasonable, I'm happy.
[10:33] <pitti> cjwatson, Daviey: from the desktop side, seb128 proposed to turn off apport now as for raring we won't change a lot any more and we have errors.u.c.; any opinion from you from the foundations/server side?
[10:34] <pitti> (for crash reports)
[10:35] <xnox> ev: see pitti above ^
[10:36] <Daviey> pitti: It makes little difference to server TBH. So i don't object.
[10:36] <cjwatson> pitti: I'm OK with that if ev is
[10:36] <ev> pitti: to be clear, leave it running for reporting to errors.ubuntu.com? Just turning it off for reporting to Launchpad, right?
[10:36] <pitti> ev has lobbied for turning off apport LP reports all the time :)
[10:36] <pitti> ev: correct
[10:36] <ev> pitti: fine by me then
[10:37] <ev> and yeah, the sooner we can make errors.u.c a suitable replacement for using LP bugs as a crash database for seb128 and others, the better :)
[10:37] <Daviey> ev: Do you have some recent documentation how server users can add more value to errors.ubuntu.com?
[10:38] <ev> Daviey: I still need to implement an automatic non-interactive reporting toggle :-/
[10:38] <pitti> ev, seb128: oh, and we've traditionally kept "Type: Package" reports on LP
[10:38] <Daviey> (In Raring+1, I'd really like us to considering running the dev cycle with it submit-by-default, easy opt-out - and turn off at B1.
[10:38] <pitti> i. e. upgrade errors
[10:38] <seb128> pitti, is e.u.c listing those?
[10:39] <pitti> seb128: yes
[10:39] <dpm> pitti, cjwatson, if we get the language pack exports from Launchpad to be part of the new release opening process, do you think it might make sense to add the step to set up the language packs PPA for the new release on https://wiki.ubuntu.com/NewReleaseCycleProcess ?
[10:39] <cjwatson> feel free
[10:39] <ev> pitti: those things are the bane of my existence. Can we sit down at not-UDS with some dpkg/apt/aptd/software-center/ohmygodtoomanypieces people and come up with a better signature algorithm?
[10:39] <pitti> seb128, ev: I have no strong opinion about package problems on LP
[10:40] <ev> I'm not convinced the current wall of text is particularly useful for grouping them together.
[10:40] <pitti> +1
[10:40] <pitti> they are incredibly hard to process even manually
[10:40] <ev> yay
[10:41]  * ev nods
[10:41] <pitti> it often takes nontrivial smarts to figure out what the actual problem is
[10:41] <xnox> ev: pitti: so we often tell people to run `ubuntu-bug ubiquity` to collect and submit all the installation logs. Would they simply arrive to errors.u.c or whould that command just do nothing?
[10:41] <pitti> xnox: bug reports have never been disabled
[10:41] <pitti> specifically, errors.u.c. isn't well suited for manual bug reports
[10:41] <pitti> so they always go to LP, even for stables
[10:42] <xnox> pitti: ah, ok. than it's all good. So it's just apport popups for "something crashed" will stop taking people to +filebug ?!
[10:42] <pitti> right
[10:42] <Daviey> ev: Are you likely going to have capacity to add server lovin' to whoopie in raring+1?
[10:42] <xnox> pitti: awesome. +1 from me ;-)
[10:42] <ev> Daviey: I really hope so.
[10:42] <ev> But extra hands are always welcome
[10:42] <Daviey> ev: If we can help.. just let me know.
[10:43] <doko> pitti, jibel: python3.3 now ready for autopkgtest's
[10:43] <ev> Daviey: find me someone to write a bit of code to automatically process and upload an apport report.
[10:43] <pitti> doko: \o/
[10:43] <ev> It's really not that much work - I'm just buried under the day-to-day operations.
[10:43] <pitti> doko: can we disable the one test that relies on stdin existing? or was that fixed/dropped in 3.3?
[10:43] <ev> s/upload/mark for upload/g
[10:43] <pitti> seb128, ev: apport uploaded
[10:43] <ev> Daviey: basically apport-cli without the interaction and an upstart job
[10:43] <doko> pitti, please first run the test
[10:44] <ev> yay
[10:44] <pitti> doko: is it in some branch?
[10:44] <doko> pitti, it might be different, because subprocess handles file desriptors different in 3.x
[10:44] <pitti> ah, I just got a closed bug mail, apparently you uploaded already
[10:46] <cjwatson> pitti: I thought I contributed debian/script.py some time back to fix that test
[10:46] <pitti> ok, will still take a bit until jenkins hits it
[10:46] <cjwatson> does the autopkgtest not use it?
[10:47] <pitti> I'm already running a VM on my workstation right now, I have too little RAM to run a second one with py3.3; but can do in teh afternoon
[10:47] <doko> cjwatson, it doesn't help (I think), if apt-run enables the redirection
[10:47] <pitti> cjwatson: apparently not; but the failure is easy to reproduce with "python2.7 -E -Wd -3 -E -tt /usr/lib/python2.7/test/regrtest.py -w test_file2k </dev/null"
[10:47] <cjwatson> not sure I agree; debian/script.py should work regardless of the prior state of stdin
[10:48] <pitti> is debian/script.py a wrapper which the tests should be run under?
[10:48] <cjwatson> yes
[10:48] <doko> they do in the build
[10:48] <cjwatson> right, grep debian/rules for it
[10:49] <seb128> pitti, danke
[10:50] <pitti> python debian/script.py foo 'python2.7 -E -Wd -3 -E -tt /usr/lib/python2.7/test/regrtest.py -w test_file2k' < /dev/null
[10:50] <pitti> ^ works
[10:50] <pitti> foo → /dev/null works as well (we aren't actually interested in the output)
[10:51] <pitti> so that should be added to debian/tests/testsuite ?
[10:51] <pitti> jibel: ^ FYI (as you were looking at that, too)
[10:52] <cjwatson> pitti: just to check, you're testing this within adt-run and not just from a terminal?
[10:52] <pitti> I tested that particular bit in a terminal
[10:53] <pitti> I ran the full thing under run-adt-test (i. e. adt-run in a VM) and adt-run (i. e. on my workstation), and reduced the failure to above command
[10:53] <dpm> cjwatson, ok, thanks, will do (re: new release openings and translations). pitti, do you have the steps documented somewhere to set up the langpacks PPA for dev releases, or can you give me a couple of bullet points and I'll add them to the wiki page?
[10:53] <cjwatson> tests in a terminal are misleading here because in a terminal you have a useful stdin
[10:53] <pitti> adt-run redirects stdin, causing the failure of that particular test
[10:53] <cjwatson> anyway, yeah, debian/script.py is very likely the right answer
[10:54] <pitti> cjwatson: the "</dev/null" should disable that, though?
[10:54] <cjwatson> right
[10:54] <cjwatson> I wasn't sure exactly what you meant by "foo → /dev/null", that's all
[10:54] <cjwatson> → not being a redirection operator in my shell :-)
[10:54] <pitti> dpm: langpack PPA to NewReleaseCycleProcess> yes from my side; you can add me as a contact point
[10:55] <pitti> dpm: we don't actualy use the PPA for dev releases, we upload straight to raring; we just need to do a first manual build (once we have an export), and then set up the crontabs
[10:55] <pitti> dpm: but we should set up the cronjobs for the stable releases when opening a new dev release
[10:55] <dpm> pitti, yeah, I'm documenting that too
[10:56] <cjwatson> damnit, haskell-hakyll hangs on the buildds - I could've sworn I'd fixed that
[10:56] <dpm> thanks
[10:56] <pitti> cjwatson: right, sorry; I meant: python debian/script.py /dev/null 'python2.7 -E -Wd -3 -E -tt /usr/lib/python2.7/test/regrtest.py -w test_file2k' < /dev/null
[10:56] <pitti> i.e. just replacing the "foo" in my orignal call with /dev/null
[10:56] <cjwatson> ah, gotcha
[10:57] <cjwatson> I'd recommend just running the entire suite under debian/script.py and catting the logfile at the end, or similar?
[10:57] <pitti> yes, sounds good
[10:58] <pitti> cjwatson: actually, we don't need to cat the log file; output still goes to stdout AFAICS?
[10:58] <doko> pitti, and enable xvfb too, and fix the disabled tests for running in the installed location ;)
[10:58] <pitti> (hence my "/dev/null" log file proposal)
[10:59] <cjwatson> pitti: oh, yes, true
[10:59] <cjwatson> forgot my own code
[10:59] <pitti> doko: one step at a time :) but it's great to have coverage for the pythons now!
[11:26] <cjwatson> Laney: so, slightly perplexingly, this ghc change changes the libghc-ghc-dev ABI hash on i386 (although none of the others), and the debdiff shows the addition of /usr/share/man/man1/runghc.1.gz, /usr/share/man/man1/ghci-<IP_ADDRESS>.gz, and /usr/share/man/man1/ghci.1.gz
[11:26]  * Laney blinks
[11:26] <cjwatson> Laney: ghci still works fine; I wonder if some of this depends on which ghc was used to build (IOW the effective change here might simply be that I'm building ghc with ghc 7.6 rather than ghc 7.4)
[11:27] <Laney> That wouldn't surprise me
[11:27] <cjwatson> and libghc-ghc-dev changing hash isn't a problem if it's going to change on armhf anyway; it just surprised me
[11:35] <Laney> cjwatson: I just turned up http://thread.gmane.org/gmane.comp.lang.haskell.debian/3287
[11:37] <cjwatson> Ah, yes, the tail-end of that thread matches
[11:38] <cjwatson> If the armhf build also only changes the ghc hash then I think we're good enough
[11:38] <Laney> "In fact, I'm pretty impressed that we manage to get the same hashes even
[11:38] <Laney> sometimes."
[11:38] <cjwatson> heh, yeah, I liked that
[11:38] <Laney> at least he's honest!
[11:42] <cjwatson> I believe the reverse chain is (1) doctest, ghc-mtl, ghc-syb-utils, gitit, haddock (2) hint
[11:42] <cjwatson> Which seems tolerable
[11:47] <jibel> doko, pitti sorry lunch break. I'll run the testsuite in our environment with script.py
[12:24] <jibel> doko, python2.7 testsuite pass when run under script.py
[12:24] <doko> jibel, the other tests too?
[12:26] <tim`> is there a reason raring is sticking with boost 1.49 instead of moving up to 1.53?
[12:27] <tim`> errr 1.50 maybe - looks like both are packaged
[12:29] <cjwatson> tim`: regardless of reasons it's far too late now - boost transitions take time
[12:30] <cjwatson> we do them at or near the start of release cycles
[12:30] <jibel> doko, yes, the 3 tests that failed yesterday: stdin, fsync and fdatasync. For fsync I removed eatmydata. IO performance is good enough with unsafe-io enabled in dpkg.
[12:30] <tim`> just curious if there was something specific holding it up
[12:31] <tim`> or if there was just not much interest
[12:31] <doko> jibel, ok, thanks! for bonus points you may want to re-enable the tests in the test scripts, and then send patches to fix these =)
[12:31] <doko> tim`, time ... and there is no 1.50 anymore
[12:32] <pitti> doko: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python3.3/, FYI
[12:32] <tim`> when do versions for 13.10 get laid out ?
[12:32] <pitti> Invalid -u/--use option: all,-network,-urlfetch,-gui,-xpickle
[12:32] <pitti> Use --help for usage
[12:33] <pitti> it didn't get very far
[12:33] <doko> pitti, my browser tries to download these files. is there a way to show these in the browser?
[12:33] <pitti> doko: not that I know of; but you can use the "console output", that will be displayed inline
[12:33] <pitti> I just look at them in gedit
[12:34] <pitti> doko: "Konsolenausgabe" is at the left menu, leading to https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python3.3/1/ARCH=i386,label=adt/console
[12:35] <doko> apw, ogasawara: I'm preparing an upload of the final GCC 4.7.3. the current version in r already has 4.7.3 as the "upstream" version. There are no changes on x86, compared to the current version. still looking at armhf and arm64
[12:35] <cjwatson> tim`: only a handful of toolchain packages need to be decided early
[12:35] <cjwatson> tim`: so nowish or before, and AFAIK it'll be boost 1.53
[12:36] <doko> we switch to 1.53 together with GCC 4.8
[12:36] <doko> at least, that's my plan
[12:36] <doko> xnox had already set up the transition tracker
[12:38] <apachelogger> cjwatson: I forgot to remove the colors yesterday, https://code.launchpad.net/~kubuntu-members/debian-cd/kubuntu-raring-artwork/+merge/158350 should fix this
[12:40] <cjwatson> apachelogger: merged/deployed, thanks
[12:40] <tim`> oh man - gcc 4.7 breaks enough things already :)
[12:41] <apachelogger> cjwatson: thank you
[12:42] <xnox> tim`: well and gcc 4.8 fixes a lot of C++11 things that were missing in 4.7 ;-)
[12:43] <tim`> will there likely be an alt gcc-4.6 package still ?
[12:44] <xnox> tim`: raring has 1.49 as default and 1.53 available in universe. The plan for next cycle (S-something) is to have 1.53 the one and only atm. We might be switching to 1.54 or have it available in universe, all depends on upstream release timing.
[12:44] <tim`> cool
[12:44] <xnox> tim`: why do you want gcc-4.6?
[12:45] <xnox> boost-1.53 is looking very good so far: http://people.canonical.com/~xnox/boost1.53/
[12:45] <tim`> i guess the issues i've run into are with cuda and zeroc-ice - ice has sorted out thier issues by now - not sure about cuda
[12:45] <xnox> still a few things to fix, but nothing out of the ordinary.
[12:45] <cjwatson> we only remove older gcc packages once nothing in our archive requires them any more
[12:46] <cjwatson> we do generally have to keep moving forward though, otherwise the hill to climb is just that much higher later on
[12:46] <tim`> yeah - understandable
[12:46] <mitya57> we still have gcc-4.6 in raring (and even 4.4), but I wouldn't recommend anyone to use that
[12:50] <doko> 4.4 will die in the s-series, killing all the games packages implemented in Dv1
[12:50] <doko> working on getting D to 4.8, so 4.6 can die too
[12:51] <tim`> D?
[12:51] <doko> not C
[12:52] <mitya57> https://en.wikipedia.org/wiki/D_(programming_language)
[12:52] <tim`> ah yes
[12:53] <NCommander> Beside D, is there any other unusual GCC frontends hanging around? (I know GNAT is kinda special though thats fortunately mainstream ...)
[12:53] <siretart> go?
[12:54] <xnox> siretart: we have go even in precise ;-)
[12:54] <xnox> siretart: 4.8 has some support for 1.1.
[12:55] <sconklin> @pilot out
[13:09] <doko> NCommander, do you want to package the PL/1 and Cobol frontends?
[13:11] <NCommander> doko, don't we already have opencobol in archive? (and no, I don't :-P)
[13:49]  * xnox really thinks old-style cmake find modules are brain dead..... goes to file a patch to FindZlib.cmake to include /usr/include/$(MULTIARCH) in the $ZLIB_INCLUDE_DIRS
[13:49] <xnox> that looks wrong... and still doesn't solve my ftbfs... looking more.
[13:57] <jamespage> pitti, could you take a look at https://code.launchpad.net/~james-page/ubuntu/raring/apport/cloud-archive/+merge/158378 - it adds a crashdb config and handler to pickup packages from the ubuntu cloud archive
[13:57] <jamespage> I'd like to backport the same into 12.04 as well
[13:59] <pitti> jamespage: do you figure that users will have a need to change that configuration?
[13:59] <jamespage> pitti, not quite sure I understand your question
[14:00] <pitti> jamespage: I'd start with putting the actual configuration into the hook, instead of adding it to the config file
[14:00] <jamespage> pitti, ah - so add the crashdb configuration to the ubuntu_cloud.py hook itself - right - lemme give that a go
[14:01] <pitti> jamespage: right, like report['CrashDB'] = '{"impl": "launchpad", ....}'
[14:03] <jamespage> pitti, working on that now
[14:03] <pitti> jamespage: and as a style nitpick, let's drop the line break and the parens in the if
[14:04] <jamespage> pitti, ack
[14:19] <jamespage> pitti, hmm - so on 12.04 I got a origin text in the package field - how do I detect the source of the package in raring?
[14:20] <pitti> jamespage: oh, inline config doesn't work in 12.04 yet, there we'll need a file in /etc/apport/crashdb.conf.d/
[14:20] <jamespage> pitti, yeah - I just noticed that :-)
[14:20] <jamespage> OK - so for 12.04 I need a crashdb config in crashdb.conf.d
[14:20] <pitti> jamespage: you should get the origin text in raring as well, but only if it's actually from a PPA
[14:20] <pitti> jamespage: if not, then it's the ubuntu package
[14:21] <jamespage> pitti: these packages come from ubuntu-cloud.archive.canonical.com
[14:21] <pitti> jamespage: you can check explicitly with if apport.packaging.is_distro_package(report['Package'].split()[0]):
[14:21] <pitti> jamespage: you don't get an [origin: ...] field in raring?
[14:25] <jamespage> pitti, lemme check again
[14:29] <doko> Sweetshark, bug subscriptions for liblangtag missing ...
[14:30] <xnox> doko: http://paste.ubuntu.com/5698613/        isn't         /usr/include/x86_64-linux-gnu/ missing from that list?
[14:30] <doko> damn, he did smell that
[14:32] <doko> $ gcc -v -E -dM - < /dev/null 2>&1| grep '^ '
[14:32] <doko>  /usr/lib/gcc/x86_64-linux-gnu/4.7/cc1 -E -quiet -v -imultilib . -imultiarch x86_64-linux-gnu - -mtune=generic -march=x86-64 -fstack-protector -dM
[14:32] <doko>  /usr/lib/gcc/x86_64-linux-gnu/4.7/include
[14:32] <doko>  /usr/local/include
[14:32] <doko>  /usr/lib/gcc/x86_64-linux-gnu/4.7/include-fixed
[14:32] <doko>  /usr/include/x86_64-linux-gnu
[14:32] <doko>  /usr/include
[14:32] <doko> xnox, works for me. why do you call cc1 directly?
[14:35] <jamespage> pitti, it would appear not
[14:35] <doko> Sweetshark, bug subscriptions for liblangtag missing ...
[14:36] <xnox> doko: hmm.... thanks that your command also works for me.
[14:38] <xnox> doko: trying to understand https://launchpadlibrarian.net/136352236/buildlog_ubuntu-raring-armhf.sword_1.6.2%2Bdfsg-5ubuntu1_FAILEDTOBUILD.txt.gz
[14:39] <xnox> zlib.h is in non-arch qualified, zconf.h is in arch-qualified location. Yet somehow zconf.h doesn't get included from zlib.h..... probably cmake/that package silliness.
[14:39] <xnox> then.
[14:40] <jamespage> pitti, packaging.get_package_origin give me 'Canonical' - I think thats good enought for my filter
[14:42] <doko> xnox, the -I/usr/lib/arm-linux-gnueabihf looks suspcicious, but shouldn't hurt
[14:43] <doko> -- CONFIGURING SOURCE LIST
[14:43] <doko> -- ZLib: system /usr/lib/arm-linux-gnueabihf/libz.so
[14:43] <doko> -- cURL: system /usr/lib/arm-linux-gnueabihf/libcurl.so and /usr/include
[14:46] <apw> doko, thanks
[14:51] <Sweetshark> doko: thx for adding
[14:52] <doko> xnox, ^^^ so for curl it does detect the include, but not for zlib ?
[14:52] <doko> cmake madness?
[14:54] <stokachu> xnox: am i reading nmu wrong? i thought since im not the maintainer it should be filed as such (re sosreport)
[14:56] <xnox> stokachu: from the point of view of the Debian Project - the package maintainer is the person who uploads and maintains the package in debian. the upstream contact is who wrote the software and is the main committer, the upstream contact can be mentioned in ./debian/copyright
[14:57] <xnox> stokachu: NMU is when another person makes an upload of the debian package on-behalf of the regular package maintainer.
[14:57] <xnox> stokachu: for example if you upload xiphos into debian, instead of me, that would be NMU. As I'm debian maintainer for xiphos.
[14:57] <stokachu> ahh
[14:58] <xnox> stokachu: if I upload sosreport into debian instead of you, that would be NMU. As i will not be the regular maintainer of that package.
[14:58] <cjwatson> filing a bug report with "NMU" in the title is kind of a declaration of intent
[14:58] <cjwatson> assuming that's what you mean
[14:58] <xnox> cjwatson: stokachu meant to do an ITP ;-)
[14:58] <jamespage> pitti, how does that look - https://code.launchpad.net/~james-page/ubuntu/raring/apport/cloud-archive/+merge/158378
[14:59] <stokachu> ok so do i close this sponsor request
[14:59] <jamespage> seems to work OK for me (although the test on raring is a little artificial as the cloud archive is really just for 12.04
[14:59] <jamespage> )
[14:59] <xnox> stokachu: one files an ITP if you intend to upload and hence become package maintainer in debian for that new piece of software.
[15:00] <pitti> jamespage: splendid!
[15:00] <stokachu> xnox: yea thats what i need to do
[15:00] <cjwatson> stokachu: don't close the bug and open a new one - that's pointless
[15:00] <cjwatson> stokachu: mutate it into what it's supposed to be instead with control commands
[15:00] <pitti> jamespage: yeah, but it doesn't hurt to have it there, so that it will be there for the next LTS, or if we actually get a cloud archive for raring for some reason
[15:00] <stokachu> ok
[15:00] <cjwatson> http://www.debian.org/Bugs/server-control
[15:00] <jamespage> pitti, yes indeed - that's kinda what I thought
[15:01] <xnox> stokachu: well open an ITP with cc to debian-devel, and mutate the sponsorship request =)
[15:01] <jamespage> pitti, are you OK for me to upload that and push the branch?
[15:01] <stokachu> so i should have an ITP ane a sponsorship request bug
[15:01] <pitti> jamespage: I just hope that ~cloud is a sufficiently tight test
[15:01] <stokachu> and*
[15:01] <xnox> stokachu: as one should file ITP to "announce" that you are about to take-up a package.
[15:02] <jamespage> pitti: I think ~cloud with origin 'Canonical' is
[15:02] <stokachu> xnox: 698329
[15:02] <pitti> jamespage: sure, please do (and use  "dch -r" and "debcommit -r" after that)
[15:02] <jamespage> pitti, ack
[15:02] <xnox> stokachu: yeah. As ITPs are usually forwarded to debian-devel and some people can point out typpos in the descriptions, or reason for a package to be not included in debian and such like. Just google for "ITP" on debian-devel to get the sense of those bugs/descriptions.
[15:02] <xnox> stokachu: new maintainer guide should tell you all about these things.
[15:03] <stokachu> yea ive been reading through the guides but i guess i got confused on nmu versus itp
[15:05] <BenC> infinity: any reason that linux-ppc-3.8.0-8 isn't in raring proper yet?
[15:05] <xnox> stokachu: in ubuntu we do not have "strong maintainership" instead anyone can upload anything, thus the concept of NMU is non-existent in ubuntu.
[15:06] <cjwatson> BenC: it's waiting for me to upload debian-installer
[15:06] <BenC> cjwatson: Ah, ok, thanks
[15:06] <cjwatson> which in turn is waiting for somebody to approve libdebian-installer in the upload queue
[15:06] <BenC> Just making sure it doesn't fall through the cracks :)
[15:06] <stokachu> xnox: ahh
[15:06] <stokachu> xnox: its all making sense now :)
[15:23] <cyphermox> slangasek: I'd remove the duplication for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433 if you don't mind, I can definitely reproduce the / is busy even after manually stopping and killing just about everything before doing a reboot; I got lsof after the stops and all, and there's very little left around
[15:42] <slangasek> cyphermox: ok, so what is keeping the root fs busy?
[15:45] <cyphermox> slangasek: I don't know ;)
[15:46] <cyphermox> slangasek: http://paste.ubuntu.com/5698847/  <-- I think "sh", is related to sendsigs too, there are no sessions open at the time in VTs or in lightdm or anywhere
[15:47] <cyphermox> certainly running lsof like so adds one more thing to write to /, but the same issue appears even if I comment out that part
[15:47] <cyphermox> (I had lsof run as part of sendsigs)
[16:40] <pitti> stgraber, Laney: could you please accept ~ubuntu-core-dev invitation into ~network-manager?
[16:40] <pitti> with that, core devs can finally push to the NM packaging branch
[16:40] <stgraber> pitti: yep, will do
[16:41] <stgraber> done
[16:41] <pitti> stgraber: merci!
[16:41] <pitti> jamespage: http://launchpadlibrarian.net/136986347/apport_2.0.1-0ubuntu17.1_2.0.1-0ubuntu17.2.diff.gz LGTM
[17:22] <jamespage> pitti, great!
[18:01] <tkamppeter> OdyX, I have added a new USB quirk rule patch (5 printers) to CUPS and also submitted it upstream, it also contains your correction for the Stylus Photo 750. See Debian GIT, new Ubuntu CUPS package, and https://www.cups.org/str.php?L4311.
[18:23] <bryce> slangasek, does udev automatically reload all rules at boot, or do you have to deliberately run udevadm trigger?
[18:24] <bryce> (or udevadm control --reload-rules; google gives me some conflicting recommendations)
[18:46] <smoser> cjwatson, do you know how i can make debian installer not go into vga mode from the netboot iso?
[18:46] <smoser> trying to boot with 'kvm -curses'
[18:47] <smoser> kirkland, for some reason i think maybe you have known that?
[18:49] <slangasek> bryce: so, if by "reload" you mean "load from disk when started from the root filesystem"... sure?
[18:49] <slangasek> bryce: what's the root problem here?
[18:51] <bryce> slangasek, for the gpu hang apport hook, which is started by a udev rule, I wanted to disable that for the release, so commented out the line in the udev rule.  However I'm noticing we're still getting a few reports, so am wondering if something more needs done to get the rule disabled for folks.
[18:52] <slangasek> bryce: udev has an in-memory cache of the rules (naturally), but otherwise reads them from disk on every boot.
[18:54] <bryce> slangasek, ok, that's what I thought.  But I can't explain how bug #1168066 got autofiled.  I mean it's good that it got filed, it's a legit bug.  But AFAIK the rule should not be filing these bugs anymore so I'm a bit perplexed.
[18:56] <slangasek> bryce: we're talking about /lib/udev/rules.d/40-xserver-xorg-video-intel.rules, right?
[18:57] <bryce> slangasek, yes
[18:57] <slangasek> bryce: I have the version of the package from that bug installed, and I see a present and active udev rule
[18:57] <slangasek> so it doesn't seem to actually be disabled in the package?
[19:00] <bryce> slangasek, not commented out?
[19:00] <slangasek> bryce: nope
[19:00] <slangasek> # Disable freeze hook.
[19:00] <slangasek> SUBSYSTEM=="drm", ACTION=="change", ENV{ERROR}=="1", RUN+="/usr/share/apport/apport-gpu-error-intel.py"
[19:00] <slangasek> there's a nice comment /above/ it ;)
[19:00] <bryce> hum, that could be the problem.  It *is* commented out in the package
[19:00] <slangasek> define "in the package"
[19:01] <slangasek> that's the unmodified version of the file, from the binary package in the archive
[19:01] <bryce> apt-get source xdiagnose; cat xdiagnose-3.4.4/debian/xdiagnose.udev
[19:02] <slangasek> bryce: oh, but it's not shipped by xdiagnose
[19:02] <slangasek> it's shipped by xserver-xorg-video-intel!
[19:02] <bryce> o_O
[19:03] <ogra_> heh
[19:05] <bryce> ahem.  yay leftovers.
[19:46] <barry> slangasek: so, apt-ftparchive.  between mvo and i, we've uploaded for raring and sru for precise.  i *think* i've got a chroot to build for lucid-cat.  now the fun bit: lucid dpkg-source can't parse multiarch deps like gettext:any.  it's probably okay to just remove :any from the build-dep (it's the only bd with that that i can see).  agreed?
[19:47] <slangasek> barry: definitely yes
[19:47] <barry> slangasek: cool.  we'll see if that makes the package buildable :)
[19:49] <barry> slangasek: hmm, likely will have to bump down some dep version numbers as well
[20:03] <slangasek> bryce: so I guess that also explains why I was getting two apport popups for every gpu hang ;D
[20:06] <bryce> slangasek, and also why we were still getting false gpu reports after we thought we fixed it...
[20:19] <roadmr> hello! when doing a pxe installation with raring, entries in /etc/network/interfaces appear borked ;/ there's no space between the lo and eth0 stanzas. Is this known or should I file a bug?
[20:22] <sarnold> roadmr: can't go wrong with a bug report :)
[20:23] <roadmr> sarnold: ok, makes sense, let me research this a bit more and then I'll file
[20:50] <bryce> slangasek, sru's are in for that.  thanks for noticing the redundant rule.
[21:11] <dobey> barry: is bug #1071897 still relevant at all or should i just close it as invalid?
[21:12] <barry> dobey: i haven't tried recently.  let me grab it and try.
[21:13] <dobey> barry: does it even matter now? 4.2.0 is in rarning now, and this bug is from ~5 months ago when lots of deps were changing
[21:14] <barry> dobey: yeah, probably doesn't
[21:23] <barry> dobey: well, the test suite is still giving me errors on a local sbuild.  if it's not breaking on the buildd's, i'll close my eyes and pretend they aren't happening.
[21:27] <dobey> barry: it works building in 3 PPAs and the official archive, so not sure what the difference would be exactly to cause it to fail locally for you
[21:27] <barry> dobey: me neither, but if you don't care i don't either :)
[21:30] <dobey> barry: i do know i had problems with ubuntu-sso-client when trying to switch from pbuilder to sbuild for testing locally, and i think there is a config difference with the lp builders vs. local sbuild, where the issue doesn't occur on the lp builders, so maybe it's related to that. but i haven't had time to deal with fixing it, and it's a fairly complicated thing to fix
[21:34] <cjwatson> smoser: https://help.ubuntu.com/12.04/installation-guide/i386/boot-parms.html - DEBIAN_FRONTEND=text
[21:35] <cjwatson> barry: the fact that you're asking that question (gettext:any) makes me a bit concerned that you're trying to drop the whole of raring's apt into lucid-cat, rather than cherry-picking the relevant patches - is that the case or am I missing something?
[21:35] <cjwatson> (or precise-updates' apt into lucid-cat, either way)
[21:57] <slangasek> cjwatson: yep, sorry, I may have suggested to barry that a full apt backport from precise-updates /might/ possibly be easier
[21:57] <barry> cjwatson: well, i was being optimistic, but i think it's not the right way to go.  unfortunately, the apt code in question has changed significantly since lucid, so the precise/raring patch has little hope of applying to the lucid version.  i've been talking with mvo over email about it, and he'll probably take a crack at producing a lucid version of the patch instead
[21:57] <slangasek> but apparently this was me forgetting just when lucid was :-)
[21:57] <barry> slangasek: ;)
[21:58] <slangasek> (i.e.: before multiarch... and apparently also before dpkg-symbols supported c++ names!)
[21:58] <barry> slangasek, cjwatson maybe we should convince is to just upgrade to precise already :)
[21:58] <slangasek> barry: depends on how soon we want this bug fixed
[21:58] <barry> slangasek: yeah.  the bug report made it sound like a big deal for some folks
[22:00] <barry> anyway, let's see if mvo can help us out here before we worry too much
[22:17] <celso_> People,  i need something that install the updates available until last week. but i dont want to install the ones after that. how do i do that? i need this to detect a regression.
[22:19] <sarnold> celso_: there's a log of package operations in /var/log/dpkg.log -- perhaps that can help you
[22:20] <geofft> celso_: ask xnox if he's deployed our LP-Librarian-using snapshot code yet :)
[22:20] <geofft> I can probably cobble something together if you give me a timestamp
[22:23] <celso_> i will explain what is happening. until near last week, my laptop was doing fine, using vgaswitcheroo to turn off my atihd5000 series to use my intell hd3000. after the last week updates (near that time) my laptop almost 90% of the time, when booting, it stays with the black screen.
[22:24] <celso_> but it won't happen if i don't install the updates, so, something has gone wrong in some file updated.
[22:24] <celso_> and i would like to find what is.
[22:25] <celso_> but unfortunatly, i am no developer or programer.
[22:25] <celso_> so, i am kind of "stuck"
[22:25] <sarnold> celso_: If I understand what I've seen others report, plymouth fights lightdm for console during boot.. you may wish to search for bugreports with both those names
[22:27] <celso_> but it don't even show a console. it stays with completely black screen with brightness and with some disk activity each half second.
[22:28] <celso_> i think a feature to install/block updates by time would be a good feature to debug some bugs
[22:30] <celso_> the problem for dpkg.log is it will not show the time each update become available if i install all now
[22:30] <celso_> i think
[22:31] <sarnold> celso_: true enough, it only shows what happened on that one machine..
[22:32] <celso_> i will install 100 updates each time and will see what happens, and then cut another half, and again....
[22:33] <celso_> it will cost alot of bandwitch but its the only way i can see.
[22:34] <celso_> brb and by the way, thanks for the help!
[22:36] <stokachu> if there is a LICENSE file and a debian/copyright but the package is for both Debian and Fedora do I renamed the LICENSE file to like LICENSE.Fedora?
[22:36] <sarnold> celso_: apt-cacher-ng or apt-cacher can easily cache packages that you download, it can drastically save time here
[22:37] <celso_> ok. i will try.
[22:39] <celso_> thanks!
[22:45] <ion> Also see squid-deb-proxy
[22:46] <celso_> have to restart. brb
[23:18] <stokachu> so if an upstream source has a LICENSE file is it acceptable to remove it during a debian build? lintian keeps reporting an extra-license-file error
[23:18] <stokachu> i have updated debian/copyright accordingly
[23:48] <slangasek> stokachu: it doesn't make sense to remove it from the source tree during the build, but you can use any of a number of techniques to make sure it doesn't ship in the binary package, yes
[23:49] <stokachu> slangasek: any urls you can point me to? googling is failing for me :(
[23:49] <slangasek> stokachu: might be better to use a worked example
[23:49] <slangasek> stokachu: can you point me at your package?
[23:50] <stokachu> so right now im working off https://github.com/sosreport/sosreport/tree/master/debian
[23:50] <stokachu> using debhelper and the Makefile is what is forcing a install of LICENSE into /usr/share/sos/.
[23:50] <stokachu> so one thing i thought of was to let debian and rpm spec handle the actual copying of the license file and removing it out of the makefile
[23:52] <slangasek> stokachu: (the reason I suggest this is that "how do I exclude this file" is dependent on the style of packaging in use... it might be a matter of fixing debian/sos.install, or calling 'rm debian/sos/usr/share/sos/LICENSE' in debian/rules)
[23:52] <slangasek> stokachu: python-support is deprecated, please use dh_python instead (wiki link in one second)
[23:53] <stokachu> yea ive got a few changes i haven't committed yet
[23:53] <stokachu> lemme show you my branch one sec
[23:53] <slangasek> ok
[23:54] <stokachu> slangasek: https://github.com/battlemidget/sosreport/tree/debian-packaging/debian
[23:54] <stokachu> thats my latest work from after fixing all lintian errors
[23:55] <slangasek> stokachu: so I'd say the simplest approach here is:
[23:55] <slangasek> override_dh_auto_install:
[23:55] <slangasek> \tdh_auto_install
[23:55] <slangasek> \trm -f debian/tmp/usr/share/sos/LICENSE
[23:55] <stokachu> ah ok
[23:55] <stokachu> i tried override before but didnt call dh_auto_install first
[23:56]  * slangasek nods
[23:56] <stokachu> gonna try that now and test
[23:57] <stokachu> slangasek: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705192 trying to get this thing sponsored
[23:58] <stokachu> so far i think ive fixed all the warnings from message 29
[23:58] <slangasek> stokachu: you seem to still have a dep on python-support in your branch
[23:59] <stokachu> ah in my control file
[23:59] <stokachu> lemme remove that
[23:59] <stokachu> i also see this warning
[23:59] <stokachu> W: dh_python2:90: Python 2.7 should install files in /usr/lib/python2.7/dist-packages/. Did you forget "--install-layout=deb"?
[23:59] <stokachu> but when i look at the layout after it builds it is in dist-packages already


[01:03] <cprofitt> The Who is butchering their own songs...
[01:04] <cprofitt> they are not as bad as the Stones were... but perhaps the NFL should get some 'current' musicians to do the half-time show
[01:06] <pleia2> hehe
[01:31] <IdleOne> yeah, like Ricky Martin or maybe George Micheal
[01:31] <IdleOne> jump into the 80's at least
[01:41] <cjohnston> cprofitt: they dont want to have any more 'incidents'


[01:12] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Currently building (cosmic/qtbase-opensource-src). Dependency wait (cosmic/qtdeclarative-opensource-src, cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebsockets-opensource-src). Diff missing (cosmic/qttools-opensource-src, cosmic/qtwebkit-opensource-src). Failed to build (cosmic/qtxmlpatterns-opensource-src)
[01:19] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[01:20] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Preparing packages
[01:32] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qtdeclarative-opensource-src, cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebkit-opensource-src, cosmic/qtwebsockets-opensource-src, cosmic/qtxmlpatterns-opensource-src). Diff missing (cosmic/qttools-opensource-src). Successfully built (cosmic/qtbase-opensource-src)
[01:39] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Failed to build
[02:00] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Failed to build
[02:03] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Preparing packages
[02:20] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Failed to build
[02:24] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Preparing packages
[02:25] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[02:32] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qtdeclarative-opensource-src, cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebkit-opensource-src, cosmic/qtwebsockets-opensource-src). Diff missing (cosmic/qttools-opensource-src). Pending binary packages (cosmic/qtxmlpatterns-opensource-src). Successfully built (cosmic/qtbase-opensource
[02:40] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Failed to build
[02:45] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Preparing packages
[02:52] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qtdeclarative-opensource-src, cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebkit-opensource-src, cosmic/qtwebsockets-opensource-src). Diff missing (cosmic/qttools-opensource-src). Successfully built (cosmic/qtbase-opensource-src, cosmic/qtxmlpatterns-opensource-src)
[02:59] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Pending binary packages
[03:12] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebkit-opensource-src, cosmic/qtwebsockets-opensource-src). Diff missing (cosmic/qttools-opensource-src). Failed to build (cosmic/qtdeclarative-opensource-src). Successfully built (cosmic/qtbase-opensource-src, cosmic/qtxmlpatterns-opensource-src)
[03:19] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Successfully built
[03:20] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Failed to build
[04:32] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qtsensors-opensource-src, cosmic/qttools-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebkit-opensource-src, cosmic/qtwebsockets-opensource-src). Failed to build (cosmic/qtlocation-opensource-src). Successfully built (cosmic/qtbase-opensource-src, cosmic/qtxmlpatterns-opensource-src). Uploading build (cosmic/qtdeclarative-opensource-src)
[05:32] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qttools-opensource-src, cosmic/qtwebkit-opensource-src). Successfully built (cosmic/qtbase-opensource-src, cosmic/qtdeclarative-opensource-src, cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebsockets-opensource-src, cosmic/qtxmlpatterns-opensource-src)
[05:56] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3296 Needs rebuild due to higher version at destination
[09:21] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3301 Pending binary packages
[09:42] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3301 Diff missing
[12:01] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3302 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[12:43] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3302 Diff missing
[13:46] -queuebot:#ubuntu-ci-eng- jamespage, https://bileto.ubuntu.com/#/ticket/3285 Dependency wait (cosmic/networking-bgpvpn). Failed to build (cosmic/openvswitch). Needs rebuild due to higher version at destination (cosmic/networking-ovn, cosmic/networking-sfc, cosmic/neutron, cosmic/neutron-dynamic-routing, cosmic/neutron-fwaas, cosmic/neutron-lbaas, cosmic/neutron-vpnaas, cosmic/python-eventlet). Ready to build (cosmic/python-os-xenapi)
[14:31] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Preparing packages
[14:59] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[15:00] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Needs rebuild due to new commits
[15:00] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Preparing packages
[15:19] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Failed to build
[15:21] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[15:39] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Failed to build
[15:40] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3299 Successfully built
[15:48] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[16:19] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Failed to build
[16:43] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[16:59] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Failed to build
[22:16] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Preparing packages
[22:59] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3298 Successfully built
[23:12] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Dependency wait (cosmic/qtbase-opensource-src). Diff missing (cosmic/qttools-opensource-src, cosmic/qtwebkit-opensource-src). Successfully built (cosmic/qtdeclarative-opensource-src, cosmic/qtlocation-opensource-src, cosmic/qtsensors-opensource-src, cosmic/qtwebchannel-opensource-src, cosmic/qtwebsockets-opensource-src, cosmic/qtxmlpatterns-opensource-src)


[00:04] <Unit193> OvenWerks: Hrm, are you the random downloading the core ISO?  If so, we're about to do another rebuild (so you'll be able to zsync though.)
[00:05] <bluesabre> Unit193 is a creepy download stalker :)
[00:05] <krytarik> lol
[00:05] <Unit193> bluesabre: #ubuntustudio-devel, mate.
[00:07] <bluesabre> tis a silly place
[00:07] <bluesabre> that I should be in more frequently
[00:27] <ochosi> Unit193: do we have some install instructions or docs for it in place?
[00:27] <ochosi> as soon as we do, i'll sure as hell gonna socialize it :)
[00:28] <ochosi> bluesabre: you mean camelot?
[00:28] <Unit193> ochosi: mini.iso is on the tracker, and -core install instructions are the same as the desktop.
[00:28] <Unit193> Wait for the final rebuild?
[00:29] <ochosi> sure
[00:29] <ochosi> anyway tonight i'm too tired, let's finalize this tomorrow
[00:29] <ochosi> also, let's talk to elfy
[00:32] <bluesabre> :)
[02:15] <OvenWerks> Unit193: Thanks ok.
[02:16] <Unit193> It'll work fine as-is, but slight build changes.
[03:15] <Unit193> krtarik: OK I think I'm happier with it.  Slight roadbump in the fix, but all should be good.
[05:02] <OvenWerks> Unit193: zsync is not happy trying to dl core
[05:02] <Unit193> Oh?
[05:02] <OvenWerks> failed to retrieve from xubuntu-core-15.04-amd64.iso
[05:02] <OvenWerks> I am not sure if there is a trick to deal with https
[05:03] <Unit193> zsync http://unit193.net/xubuntu/xubuntu-core-15.04-amd64.iso.zsync  or you can use the same zsync-curl package.
[05:04] <OvenWerks> Ok that works.
[06:47] <elfy> morning
[06:51] <astraljava> o/
[06:51] <Unit193> Howdy.
[06:51] <Unit193> elfy: Got enough pings in scrollback?
[06:52] <elfy> yep I did
[06:52] <elfy> speed reading catches the gist of it :)
[06:52] <elfy> I'm all for -core being more official
[06:53] <elfy> as far as testing goes - that's kind of immaterial - imo we shouldn't not do THIS just because we've got few testers
[06:53] <elfy> I would have to assume the ones we DO have would test what we threw their way
[06:54] <Unit193> No, we should not do it because it'd be me directly adding more to the testing load. :P
[06:54] <elfy> I'll be doing the 'how did testing go' mail to the list soon - let's see what response we get from that
[06:54] <elfy> and as Unit193 said - I'd be cool with -core being pushed at milestones only
[06:55] <elfy> Unit193: lol
[07:16] <elfy> also - if we are going to push it then the next cycle is the one to do it during, I'd not be soSearch Results blasé during the following LTS one
[07:17] <elfy> stupid middle mouse button
[08:25] <Unit193> slickymasterWork: zsync before you use the image, btw.
[08:25] <slickymasterWork> ok Unit193
[08:30] <ochosi> elfy: that sounds pretty good to me!
[08:31] <ochosi> so maybe rather than announcing the image for 15.04 on xu.org, we could announce that there will be images throughout 15.10 and that we want ppl to do milestone testing
[08:32] <ochosi> actually i'm wondering whether smoketests would be enough for -core
[08:32] <ochosi> since most (or all?) of the rest is tested in -desktop anyway
[08:34] <elfy> ochosi: that sounds and appears logical
[08:34] <Unit193> Awwwh. :(
[08:51] <ochosi> Unit193: what would you have preferred
[08:54] <Unit193> Well, kind of kidding, but..
[09:17] <ochosi> Unit193: right, still, please finish your sentences :)
[09:17] <elfy> heh
[09:19] <Unit193> Eh, well kind of exists now, but meh.
[09:40] <ochosi> Unit193: yeah, as i said, i wouldn't mind announcing it's sort-of-readiness now when announcing plans for 15.10 for it
[09:40] <ochosi> elfy: ^ ?
[09:46] <elfy> yep - works here
[10:02] <ochosi> Unit193: would that be an ok compromise for you then?
[10:08] <ochosi> knome: re: that xfpm bug, you might have to compile yourself either way because if you can reproduce the bug, i'll need to add more debug-code so we can get the needed info
[10:08] <ochosi> bbiab
[10:08] <knome> hurgh
[10:08] <knome> :P
[10:08] <ochosi> well, that's what testing apps actually means most often ;)
[10:09] <knome> i know
[10:09] <ochosi> but the steps are really simple
[10:09] <ochosi> are you comfortable with applying git patches btw?
[10:10] <knome> somewhat
[10:10] <ochosi> ok good
[10:10] <ochosi> otherwise i would've set up a separate repo for testing/debugging it, but that seems a little over the top
[10:10] <knome> heh
[10:10] <ochosi> gotta run out for 2h, bb after that
[10:11] <knome> yep
[11:53] <knome> pleia2, RT 26480 if you are interested, but no need to worry, i'll handle it
[12:04] <elfy> thanks knome
[12:04] <elfy> could have done that myself ...
[12:06] <knome> it's fine :)
[12:18] <knome> http://cdimage.ubuntu.com/xubuntu/releases/15.04/release/
[12:18] <knome> oops.
[13:55] <ochosi> knome: any time you're ready, lemme know
[13:56] <knome> got to eat first
[13:56] <ochosi> sure, bon appetit
[13:57] <knome> if only i knew what i'm eating..
[14:51] <slickymasterWork> Unit193, zsynced and installed without a glich
[14:52] <elfy> afternoon peeps
[14:52] <slickymasterWork> if you want any specific testing on it please let me know
[14:52] <slickymasterWork> hey elfy
[14:52] <slickymasterWork> *glitch
[15:59] <ochosi> knome: soo... ready for some testing now?
[16:25] <knome> ochosi, unfortunately (for you) i'm not on my desktop now...
[16:25] <knome> will probably be postponed to some other day; unless you simply leave me the instructions and the test subject..
[16:35] <ochosi> hm, alright
[16:47] <slickymasterWork> ftr knome, there's a typo in http://xubuntu.org/news/15-04-release/
[16:47] <slickymasterWork> I'm correcting it
[16:59] <elfy> where?
[17:00] <slickymasterWork> in the known issues section
[17:00] <slickymasterWork> It was: "... To workaround this, simply readd the notes plugin to the panel....
[17:00] <slickymasterWork> removed the extra 'd' in readd
[17:00] <elfy> oh yea
[17:00] <elfy> umm
[17:01] <elfy> readd is right - read isn't :)
[17:01] <elfy> or re-add
[17:03] <slickymasterWork> god damn it elfy :P
[17:03] <knome> slickymasterWork, yeah you are wrong :P
[17:03] <knome> it's "re-add"
[17:03] <slickymasterWork> well at least you'll have to concur that it was an honest mistake
[17:04] <elfy> and work around as krytarik said elsewhere, being too scared to come here
[17:04] <krytarik> LOL - yeah yeah.
[17:04] <elfy> slickymasterWork: it was an honest mistake for sure :)
[17:04] <elfy> ohai krytarik :p
[17:05] <slickymasterWork> ok, it's re-add. now
[17:06] <knome> slickymasterWork, "To work around this, simply add the notes plugin back to the panel."
[17:06] <knome> slickymasterWork, plz
[17:07] <slickymasterWork> ok knome, I admit I read it diagonally
[17:07] <elfy> that's lost in translation here :)
[17:07] <knome> slickymasterWork, please put what i just quoted there for improved clarity
[17:08] <slickymasterWork> ?! knome
[17:08] <knome> slickymasterWork, "To work around this, simply add the notes plugin back to the panel."
[17:08] <slickymasterWork> put what? where?
[17:08] <knome> on the website
[17:08] <knome> :P
[17:08] <krytarik> Same would apply to the wiki page, btw.
[17:08] <knome> i can take care of that
[17:09] <slickymasterWork> so not, re-add?
[17:09] <slickymasterWork> without the comma
[17:09] <elfy> slickymasterWork: change it to that sentence
[17:09] <knome> slickymasterWork, well it's a different sentence altogether :P
[17:09] <elfy> To work around this, simply add the notes plugin back to the panel
[17:09] <knome> or i can do it if it's too baffling..
[17:11] <slickymasterWork> no it's not too baffling knome
[17:11] <slickymasterWork> it's done
[17:11] <knome> thanks
[17:12] <elfy> ummm
[17:12] <elfy> looks to be a different colour to me
[17:12] <knome> really?
[17:12] <krytarik> +1
[17:12] <knome> maybe
[17:13] <knome> damn that slimy master
[17:13] <elfy> definitely
[17:13] <elfy> bad timing there from me :p
[17:13] <krytarik> Also, "Release notes" → "Release Notes" as well then. :P
[17:13]  * knome goes fix
[17:14]  * knome sighs
[17:14] <knome> done
[17:14] <krytarik> \o/
[18:37] <knome> zequence, ping
[19:14] <Unit193> ochosi: Heh, of course.  In the end whatever works and is useful.  If that means wait until 15.10 for more testing, that's fine.
[19:44] <knome> zequence, (at least) two things:
[19:44] <knome> zequence, 1) how did you end up with SSL on studio's website?
[19:45] <knome> zequence, 2) did you get jetpack installed for studio WP and/or are you interested in it any more?
[21:51] <zequence> knome: Don't know about the ssl. We haven't got anything installed, no.
[21:51] <zequence> I'm satisfied myself with what we have right now.
[21:51] <knome> zequence, ok, then i'll likely as them to close that ticket


[06:16] <amansi26> Hi.. can anyone tell me what difference does it make if cloud init status returning running and cloud init status returning done?
[08:51] <meena> cloud-init is a oneshot service. so if you're asking systemd for a status while it's actively doing stuff, it'll say running, otherwise, done
[08:53] <amansi26> meena: For rhel and sles when I install cloud-init package, the status shows done (by default) but for ubuntu it is showing disabled (by-default)
[08:54] <meena> amansi26: you probably have to enable it in /etc/default/cloud*
[08:55] <meena> i say, not having used cloud-init on Linux in almost two years
[08:56] <meena> on *BSD we have /etc/rc.conf for the same purposes, but no one has even looked at my patch! https://github.com/canonical/cloud-init/pull/161
[16:42] <amansi26> When we install cloud-init on a system. What ll be the default value for cloud-init status?
[16:48] <amansi26> How to change cloud-init status from running to done?
[16:56] <blackboxsw> amansi26: status starts as 'not run'
[16:57] <amansi26> But in my case it is coming as disabled
[17:00] <blackboxsw> It expects to see all cloudinit stages completing in /run/cloud-init/satus.json
[17:00] <blackboxsw> https://github.com/canonical/cloud-init/blob/master/cloudinit/cmd/status.py#L101
[17:00] <blackboxsw> And if disabled itll report that
[17:00] <blackboxsw> https://github.com/canonical/cloud-init/blob/master/cloudinit/cmd/status.py#L73
[17:02] <blackboxsw> amansi26: running cloud-init status --long  will tell you why disabled
[17:08] <amansi26> blackboxsw: It says "Cloud-init disabled by cloud-init-generator" . But then I checked for /etc/cloud/cloud-init.disabled (it doesnot exists) and /proc/cmdline (doesnot contain cloud-init=disabled)
[17:29] <blackboxsw> amansi26: so this is a fresh pkg install, cloudinits generator hasn't run yet to create init files which will run cloudinit on next boot.
[17:29] <blackboxsw> Genet
[17:30] <blackboxsw> Generator is at /lib/systemd/system-generaties
[17:31] <blackboxsw> Oops /lib/systemd/system-generators/cloud-init-generator is what enables cloud init
[17:36] <amansi26> blackboxsw: There is no such file on the system
[17:47] <blackboxsw> amansi26: what distibution again?
[17:48] <blackboxsw> ubuntu?
[17:48] <amansi26> blackboxsw: yes
[17:50] <blackboxsw> if that ubuntu image didn't have cloud-init already installed, it is probably not a certified cloud image from ubuntu from https://cloud-images.ubuntu.com/
[17:53] <amansi26> blackboxsw: I can tell you the steps I performed. 1.Took an iso from http://old-releases.ubuntu.com/releases/16.04.4/ubuntu-16.04-server-ppc64el.iso and installed the ubuntu system. 2. I have a custom cloud-init debian package, I tried installing that. It got installed. But the status is disabled(by-default, as discussed).
[17:54] <blackboxsw> if I `lxc launch ubuntu-daily:bionic mybionic; lxc exec mybionic ls /lib/systemd/system-generators/` I can see cloud-init-generator file there
[17:54] <blackboxsw> amansi26: if you are trying to boot cloud-image with cloud-init you really should source from official cloud-image isos
[17:55] <blackboxsw> https://cloud-images.ubuntu.com/xenial/current/
[17:56] <amansi26> But there is no iso file out there
[18:23] <amansi26> blackboxsw: When will this file /lib/systemd/system-generators/cloud-init-generator get generated?
[19:08] <blackboxsw> amansi26: it should be part of the deb package built
[19:09] <blackboxsw> packages/bddeb could help with that
[19:10] <blackboxsw> it defaults to systemd init system type which s what packages the cloud-init-generator from systemd/*.tmpl
[19:11] <blackboxsw> './tools/run-container' could also perform a build of your custom cloud-init dir in an lxc container on centos/debian/ubuntu and emit a built binary package to your $CWD


[01:09] <Oderus> having an issue when updating with a certain repo that worked a couple days ago, anyone seen this error or know how to deal with it? W: gpgv:/var/lib/apt/lists/ppa.launchpad.net_fengestad_devel_ubuntu_dists_xenial_InRelease: The repository is insufficiently signed by key B0C05875FDAB46D08017FCE24A526E70416A86EB (weak digest)
[01:14] <k1l_>  https://juliank.wordpress.com/2016/03/14/dropping-sha-1-support-in-apt/  and https://juliank.wordpress.com/2016/03/15/clarifications-and-updates-on-apt-sha1/
[01:14] <k1l_> its just a warning (for now). tell the repo maintainer to use a proper key to sign the packages
[01:30] <Oderus> k1l_: thank you
[03:52] <salamanderrake> lordievader: when I did a apt-get full-upgrade ubuntu's unity interface broke, there was no bar/menu thing.
[04:51] <ChibaPet> apt-get update ; apt-get dist-upgrade ; apt-get install ubuntu-desktop
[04:51] <ChibaPet> If there are problems, that ought to identify them.
[07:04] <salamanderrake> ok thanks
[07:07] <ChibaPet> you're welcome
[09:14] <lotus|xenial> my new desktop xenial screen: http://lotuspsychje.deviantart.com/art/Ubuntu-16-04-64bit-Development-branch-598369242
[09:21] <lordievader> Good morning.
[09:31] <morgan_> lotus|xenial: nice
[09:32] <lotus|xenial> morgan_: thank you :p
[09:32] <morgan_> not seen the unity dash at the bottom of the screen before
[09:33] <morgan_> looks better I would say
[09:33] <lotus|xenial> morgan_: you can test yourself with gsettings tweak
[09:34] <morgan_> I will do when I install 16.04 - i'm running kubuntu/solus at the minute
[09:34] <morgan_> I assume there will be an option in the system-settings menu?
[09:34] <lotus|xenial> cool
[09:34] <lotus|xenial> morgan_: at this moment not yet
[09:35] <morgan_> (btw solus is very nice/snappy - lacks packagaes and has bugs though at the min)
[09:35] <lotus|xenial> morgan_: still needs the gsettings tweak from terminal, but smooth already
[09:37] <morgan_> cool - looking forward to testing Mir now also (now nvidia have a driver..)
[09:38] <lotus|xenial> morgan_: 16.04 will still have unity7 by default, and unity8 will be available for install also
[09:38] <morgan_> can you install alongside ?
[09:38] <lotus|xenial> morgan_: yes, you will be able to choose at login then
[09:39] <morgan_> good stuff !
[09:39] <lotus|xenial> morgan_: unity8 by default at 16.10 estimate
[09:39] <morgan_> make sense not to have mir, etc on an LTS..
[09:40] <lotus|xenial> who knows on 18.04 :p
[09:40] <lotus|xenial> morgan_: alot of changes comming our way mate
[09:40] <morgan_> The fact nvidia now have Vulkan/Mir/Wayland support is encouraging for the future...
[09:41] <lotus|xenial> morgan_: very
[09:52] <lotus|xenial> brb dist-upgrade reboot
[09:58] <varaindemian> when is the date of the final beta of bubuntu 16.04?
[09:58] <lotus|xenial> varaindemian: around 21 april
[09:59] <lotus|xenial> varaindemian: check the schedule in topic mate
[10:00] <varaindemian> lotus|xenial,  March 24th
[10:00] <varaindemian>
[10:00] <varaindemian> Warning /!\ Final Beta Freeze, Warning /!\ Final Beta
[10:00] <varaindemian> oh
[10:01] <varaindemian> lotus|xenial, actually tomorrow?
[10:01] <lotus|xenial> varaindemian: final beta freeze yes
[10:02] <lotus|xenial> varaindemian: but final official release 21 april
[10:03] <varaindemian> lotus|xenial, so tomorrow we can expect something new
[10:04] <lotus|xenial> varaindemian: every update xenial does, something new happens
[10:05] <varaindemian> lotus|xenial, they say its the final beta so I expect something more interesting..
[10:05] <lotus|xenial> varaindemian: are you on 16.04 right now?
[10:06] <varaindemian> nope
[10:06] <varaindemian> lotus|xenial, I am on arch and I want to change
[10:06] <lotus|xenial> varaindemian: every update xenial did, interesting things happened already
[10:06] <lotus|xenial> varaindemian: final beta freeze is just the deadline
[10:07] <lotus|xenial> new kernels, new package versions,etc
[10:07] <lotus|xenial> its already happening
[10:08] <varaindemian> I see
[10:24] <Fudge> hey guys, i installed desktop today but find that watching content over the network with totem movie player is really laggy, any ideas?
[10:25] <lotuspsychje> Fudge: upgrade or clean install?
[10:25] <Fudge> clean install mate
[10:25] <lotuspsychje> Fudge: up to date to latest?
[10:25] <Fudge> ive been running server for a while, maybe two months with some issues but desktop is a bit of a mess seemingly
[10:26] <Fudge> The following packages have been kept back: usb-modeswitch-data
[10:26] <Fudge> 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
[10:26] <Fudge> basically yeah
[10:26] <Fudge> the AU mirror is three hours behind US though
[10:26] <lotuspsychje> Fudge: uname -a ?
[10:26] <Fudge> Linux vtech 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[10:26] <lotuspsychje> good :p
[10:27] <Fudge> always wise to check m8
[10:27] <lotuspsychje> Fudge: installed ther ubuntu-restricted-extras ?
[10:27] <Fudge> I ticked the box at install but have not installed anything accept cpufreqd and espeakup, espeakup is a console screen reader
[10:28] <Fudge> i just dont get it, even pausing my show it takes 2 seconds
[10:28] <lotuspsychje> Fudge: sure you got right graphics drivers active?
[10:28] <Fudge> onboard video
[10:29] <lotuspsychje> Fudge: did you have this glitch at previous kernel also?
[10:29] <Fudge> not sure which kernel i was running on trusty, think a vivid one
[10:30] <Fudge> linux-image-4.2.0-25-generic
[10:30] <lotuspsychje> Fudge: check sudo lshw -C video if driver shows correctly also?
[10:30] <Fudge> nah that works fine on this hardware, its a core 2 duo quad core machine
[10:30] <lotuspsychje> yeah just checking all options
[10:31] <Fudge>        product: 82G33/G31 Express Integrated Graphics Controller
[10:31] <lotuspsychje> driver=
[10:31] <Fudge> VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)
[10:32] <Fudge> how else do i check the driver?
[10:32] <lotuspsychje> Fudge: should show at bottom
[10:32] <Fudge> ah k
[10:32] <lotuspsychje> Fudge: driver=i...
[10:33] <Fudge>        configuration: driver=i915 latency=0
[10:33] <lotuspsychje> ok looking good
[10:33] <lotuspsychje> Fudge: you have any problems playing 1080p over youtube or vlc?
[10:34] <Fudge> havnt even openned firefox yet, ill give it a go
[10:35] <Fudge> actually i usually only download the lower quality since i cant see the video anyway
[10:35] <Fudge> ill get back to you with that one :D
[10:36] <lotuspsychje> kk
[11:01] <Fudge> lotuspsychje:  i had to reset unity settings, see how it goes now
[11:01] <lotuspsychje> ok
[11:02] <Fudge> the 1080p youtube played fine
[11:03] <lotuspsychje> Fudge: so lets assume its a totem issue
[11:03] <lotuspsychje> Fudge: can you start totem from terminal please, try that over-network- vid?
[11:04] <lotuspsychje> Fudge: did you install ubuntu-restricted-extras ?
[11:06] <Fudge> yep sure did
[11:09] <Fudge> still laggy when copied file to desktop, might re-install tomorrow see if it happens again
[11:11] <lotuspsychje> Fudge: you mean totem plays still laggy after playing file local?
[11:11] <Fudge> it doesnt glitch, but if i hit space=pause it takes 3 seconds to resond
[11:11] <Fudge> respond
[11:15] <lotuspsychje> Fudge: try totem from terminal, might spit out some usefull errors
[11:15] <Fudge> nothing i could read mate, at all just that i ran it
[11:15] <Fudge> ill re-iunstall after work tomorrow and see if it was just somethign screwy :D
[11:16] <lotuspsychje> kk
[11:28] <pavlushka> I am getting local fonts clumsy http://i.imgur.com/ZAEd4Gy.png
[11:29] <k1l_> pavlushka: please dont crosspost. that is just annoying. if its a 16.04 system please only in here
[11:29] <pavlushka> yes its a 16.04 system
[11:30] <pavlushka> and ok.
[11:39] <alkisg> In 16.04 I cannot write an .iso by right-clicking in it from naytilus anymore... was that program dropped? which UI is used now?
[11:40] <alkisg> http://www.ubuntu.com/download/desktop/burn-a-dvd-on-ubuntu ==> I don't have that option anymore
[11:41] <alkisg> Was that part of brasero?
[12:48] <BluesKaj> hiyas all
[13:52] <genii> "Setting up udev (229-3ubuntu1) ... addgroup: The group `input` already exists as a system group. Exiting. /var/lib/dpkg/info/udev.postinst: 109: [: Illegal number: * "
[14:17] <BluesKaj> genii, yes I saw that in my upgrade as well, wonder why it's trying to add a group
[14:25] <TJ-> that needs refixing then
[14:26] <TJ-> can you guys do "getent group input" please
[14:29] <BluesKaj> TJ-, input:x:107:
[14:30] <TJ-> OK, and also "grep 'addgroup.*input' /var/lib/dpkg/info/*.postinst"
[14:30] <genii> TJ-: Let me get online with that box first, hang on
[14:31] <lotuspsychje> !info udev xenial
[14:32] <lotuspsychje> genii: how comes your version shows higher?
[14:32] <genii-testing> TJ-: input:x:106:
[14:32] <TJ-> 229-3ubuntu1 is current
[14:32] <lotuspsychje> ah bot needs sync?
[14:33] <TJ-> genii-testing: ok, the warning message about 'input' group is just that, a reminder, not fatal, but the later test failure is serious
[14:34] <BluesKaj> TJ-, on the 2nd request, /var/lib/dpkg/info/udev.postinst:    addgroup --system input
[14:34] <TJ-> could you both "pastebinit <( ls -latr /sys/class/net/eno*)" please
[14:35] <TJ-> genii-testing: can you create a bug report on this?
[14:35] <TJ-> I'm alerting pitti about it, but we ought to have a tracking bug. BluesKaj can then me-too the report
[14:35] <genii-testing> TJ-: with grep -n ... /var/lib/dpkg/info/udev.postinst:151:    addgroup --system input
[14:36] <genii-testing> Against package udev?
[14:36] <TJ-> genii-testing: thanks. that just confirms its a warning. if udev has previously added the 'input' group it lets 'addgroup' fail the 2nd time but you see the warning
[14:36] <TJ-> genii-testing: yes
[14:36] <BluesKaj> TJ-, ls -latr /sys/class/net/eno* just gives: /var/lib/dpkg/info/udev.postinst:    addgroup --system input
[14:37] <TJ-> OK, it's already fixed in the git repo... fix will come into packaging soon
[14:37] <BluesKaj> tj oops wrong line copy , this is the corrct one: ls: cannot access '/sys/class/net/eno*': No such file or directory
[14:38] <BluesKaj> TJ-,^
[14:40] <TJ-> we're sorted, the existing report is bug 1560112
[14:40] <genii> TJ-: Bug already exists, #1560112
[14:41] <genii> Marked it as "affecting me"
[14:41] <lotuspsychje> nice find
[14:42] <TJ-> BluesKaj: that explains why the test fails. if no entries exist the loop variable will be empty
[14:42] <TJ-> the code assumes there will always be entries, when they only apply to VMware guests in the main
[14:42] <BluesKaj> right
[14:44] <jaythelinuxguy> Hello everyone. I am testing MariaDB on Ubuntu 16.04 (daily image). I've set a root password. I've noticed some strange behavior with MariaDB. For one, if I'm logged in as the Linux user root, I can access the MariaDB shell as root with any password (even if I enter a wrong password, I still get in). Also, no regular Linux user can access the root MariaDB shell, even if I type the right password. Is this something specific to Ubuntu's
[14:44] <jaythelinuxguy> implementation of MariaDB? Or maybe a bug?
[14:44] <lotuspsychje> jaythelinuxguy: upgrade or clean install?
[14:45] <jaythelinuxguy> lotuspsychje clean
[14:45]  * BluesKaj wonders when plasma 5.6 is gonna hit the Xenial backports
[14:46] <lotuspsychje> BluesKaj: not sure
[14:48] <MonkeyDust> ask in #ubunt+2
[14:48] <MonkeyDust> ask in #ubuntu+2
[14:48] <MonkeyDust> (silly joke)
[14:49] <lotuspsychje> :p
[14:50] <lotuspsychje> !find mariadb-server
[14:51] <lotuspsychje> jaythelinuxguy: wich version are you on mate?
[14:51] <MonkeyDust> jaythelinuxguy  cat /etc/issue
[14:54] <TJ-> jaythelinuxguy: using mysqladmin tool?
[14:54] <MonkeyDust> !info mariadb-server
[14:58] <lotuspsychje> MonkeyDust: you skared him with your joke
[15:00] <TJ-> unless MYSQL_PWD is set in the calling environment, or there is no password set for the mariadb 'root' user, there doesn't seem to be a way in
[15:01] <jaythelinuxguy> /etc/issue: Ubuntu Xenial Xerus (development branch) \n \l
[15:02] <jaythelinuxguy> I didn't use mysqladmin, I used mysql_secure_installation
[15:03] <TJ-> jaythelinuxguy: you used that tool to try to access the DB server and got admitted without entering the DB root user's password?
[15:03] <jaythelinuxguy> I used the following as the Linux root user: mysql -u root -p (then I entered a wrong password on purpose)
[15:03] <jaythelinuxguy> I still got in
[15:04] <TJ-> jaythelinuxguy: Are you still using the same shell session you called mysql_secure_installation from?
[15:04] <jaythelinuxguy> If I run mysql -u root -p (as a normal Linux user) I can't get into MariaDB at all, even with the right password
[15:04] <jaythelinuxguy> TJ no, I've rebooted several times since
[15:04] <TJ-> jaythelinuxguy: ok, so not a leaky environment issue
[15:05] <jaythelinuxguy> I've also set up another fresh 16.04 install just to make sure, and same behavior
[15:05] <TJ-> I'm looking at the sourcecode
[15:06] <TJ-> jaythelinuxguy: did the password you used with mysql_secure_installation have any shell-special characters in?
[15:07] <jaythelinuxguy> TJ: The first time I did, but then I set the password to 'test123' and had the same issue
[15:07] <MonkeyDust> popey  in MATE i cannot disable the window animation when reducing a window... already checked 'reduced resources'
[15:09] <TJ-> jaythelinuxguy: OK, so nothing special there. It looks as if the shell script mysql_secure_installation.sh may not correctly write the root password into the temporary config file it creates, which would mean the password is empty. Have you, after accessing the DB from the system root user, checked the user and grants tables to see if a password is stored for 'root' ?
[15:10] <jaythelinuxguy> TJ: I have not, I'll check that now
[15:11] <TJ-> the shell code has this: "UPDATE mysql.user SET Password=PASSWORD('$esc_pass') WHERE User='root';"
[15:13] <jaythelinuxguy> TJ: It does show a password hash for root, for localhost, <IP_ADDRESS>, and ::1
[15:14] <jaythelinuxguy> TJ: Also, the password hash changes when I run mysql_secure_installation again
[15:15] <TJ-> jaythelinuxguy: right, and when you run the script you see "Password updated successfully!" when it sets the password?
[15:15] <jaythelinuxguy> TJ: Yes, it does say that.
[15:15] <TJ-> jaythelinuxguy: ok, so the confirms it works through its set_root_password() function
[15:16] <TJ-> so 2 things: 1) the password being hashed might not be the password you typed (resulting in a different hash)
[15:16] <TJ-> 2) why the heck can the system root user get in without a password
[15:17] <TJ-> you need to file a bug against the package
[15:18] <jaythelinuxguy> TJ: I also just created a test user, and that works perfectly as expected, I created a user, gave him grants, and then I can log in as that user. If I enter a wrong password for my test user, I can't get in, so that part works fine. This appears to be limited to the root user
[15:18] <jaythelinuxguy> I'll file a bug
[15:18] <TJ-> jaythelinuxguy: another test you can do to get more detailed info
[15:19] <lotuspsychje> maybe the #ubuntu-hardened guys need to know this aswell, as it might be security flaw?
[15:20] <TJ-> temporarily edit the mysql_secure_installation.sh script itself. Add "set -x" near the top so the script writes debug info to terminal. Secondly, locate the set_root_password function, and the line "esc_pass=..." followed by "do_query ..." and in between them add "echo "Escaped Password: $esc_pass"
[15:21] <TJ-> then run the script as "mysql_secure_installation.sh ...args... |& tee /tmp/mariadb.log"
[15:21] <TJ-> use that 'test123' as your password and see if the Escaped version is the same
[15:22] <jaythelinuxguy> Thanks TJ
[15:23] <TJ-> that call to basic_single_escape() is doing a complex 'sed': "echo "$1" | sed 's/\(['"'"'\]\)/\\\1/g' "
[15:23] <TJ-> that might be messing up
[15:32] <jaythelinuxguy> TJ: Your changes to the mysql_secure_installation script were brilliant
[15:32] <TJ-> jaythelinuxguy: did it reveal a problem?
[15:33] <jaythelinuxguy> Still looking through the output
[15:34] <TJ-> jaythelinuxguy: I'd grep for "Escape" to begin with :)
[15:34] <TJ-> that will show you the password after it was escaped
[15:34] <jaythelinuxguy> Sorry. Yes, it did show the right password
[15:34] <TJ-> Oh, that's a shame! That was the only place it could really mess up!
[15:37] <jaythelinuxguy> I filed the bug, and I checked the box that indicates it's a potential security vulnerability. Is there any harm in my making it public since 16.04 is beta anyway?
[15:38] <TJ-> jaythelinuxguy: no... what's the bug # ?
[15:39] <TJ-> I'll try to reproduce it
[15:39] <jaythelinuxguy> 1561062
[15:40] <TJ-> bug 1561062
[15:40] <TJ-> are you using amd64 architecture?
[15:46] <jaythelinuxguy> Yes, amd64
[15:46] <jaythelinuxguy> In a virtualbox vm
[15:52] <TJ-> I'm testing it in a chroot
[16:04] <lotuspsychje> !movelauncher
[16:05] <lotuspsychje> for the xenial users who wanna test :p
[16:08] <MonkeyDust> my cpu goes berserk in xenial/unity, was forced to logout and switch to mate
[16:09] <nicomachus> MonkeyDust: any idea on the culprit?
[16:09] <lotuspsychje> MonkeyDust: thats weird...running pretty lightweight on my old amd 3200+
[16:09] <nicomachus> doing fine on my Core2Duo as well
[16:10] <lotuspsychje> MonkeyDust: what cpu is that?
[16:10] <nicomachus> currently .9% while idle.
[16:10] <TJ-> jaythelinuxguy: same result here. as system UID 0 "mysql -u root" I'm in, with another UID and "mysql -u root -p" I get "ERROR 1698 (28000): Access denied for user 'root'@'localhost'"
[16:11] <MonkeyDust> unity now, again: cpu 99-100% and slow performance
[16:12] <lotuspsychje> hmmz
[16:12] <lotuspsychje> MonkeyDust: clean install?
[16:12] <TJ-> jaythelinuxguy: you need to read /usr/share/doc/mariadb-server-10.0/README.Debian.gz
[16:12] <MonkeyDust> intel here
[16:12] <TJ-> jaythelinuxguy: it's not a bug; it's by design
[16:12] <MonkeyDust> lotuspsychje  yes, always
[16:13] <TJ-> jaythelinuxguy: that is referred to in the package changelog
[16:13] <MonkeyDust> anyway, gtg, bbl
[16:13] <lotuspsychje> kk
[16:13] <jaythelinuxguy> Thanks TJ I'll read that in a bit, I'll be afk for a few but I'll check that out
[16:13] <TJ-> Instead the MariaDB root account is set to be authenticated
[16:13] <TJ-> using the unix socket, e.g. any mysqld invocation by root or via sudo will
[16:13] <TJ-> let the user see the mysqld prompt.
[16:14] <TJ-> that doesn't explain why "mysql -u root -p" fails from another user though
[16:22] <TJ-> jaythelinuxguy: looks like I've found the problem with it not setting the root password
[16:24] <jaythelinuxguy> TJ: what did you find?
[16:31] <TJ-> It *looks* as if when not the root user because mysql is run from the localhost it still uses the Unix socket, and the non-root user doesn't have privileges, regardless of the user/password on the command line. Can you try setting a grant for root from '%' host ('root'@'%') and then try connecting from the host into the VM over the net with mysql on the host?
[16:31] <TJ-> if I am correct that should work
[16:31] <TJ-> I was looking for a way to disable unix socket usage but not found an obvious cmd-line option so far
[16:32] <jaythelinuxguy> Do you mean: grant all privileges on *.* to 'root'@'%';
[16:32] <jaythelinuxguy> I did that and it still won't work, let me double-check
[16:33] <jaythelinuxguy> Yeah still can't log in
[16:34] <jaythelinuxguy> Oh sorry I didn't notice the "over the net" part
[16:34] <jaythelinuxguy> one sec
[16:34] <jaythelinuxguy> That doesn't work either
[16:36] <TJ-> tried using "--protocol TCP" locally and that doesn't either
[16:38] <TJ-> checked with tcpdump and "--protocol TCP" does have it talk over the 'lo' network interface, rather than the socket
[16:39] <TJ-> also confirmed the hashed stored password matches by doing "select password('test123'); "
[16:44] <TJ-> do you see anything in the /var/log/auth.log or /var/log/mysql/error.log ?
[17:12] <jaythelinuxguy> Nothing in those logs
[17:17] <pavlushka> I am getting local fonts clumsy http://i.imgur.com/ZAEd4Gy.png
[17:19] <TJ-> I found something weird. I removed the root@localhost unix_plugin prequirement and it still fails over TCP
[17:20] <TJ-> I then altered /etc/hosts to change 'localhost' to another name so it wouldn't reverse-lookup <IP_ADDRESS> or ::1 to that, but it still does, so it may never be trying to use the entries in mysql.user for<EMAIL_ADDRESS>or root@::1
[17:34] <TJ-> hmmm, according to the docs to use the unix_socket plugin it should have a plugin file named auth_socket.so in the plugins directory, and I don't see such
[17:38] <TJ-> debian packaging adds 3 patches to make it built-in, one of which generates the default user table with the root/localhost entries, and that unix_socket in the plugin column
[17:44] <jaythelinuxguy> TJ: Very interesting, thank you for all your help. I do agree your findings are peculiar
[17:49] <TJ-> I wonder if it being built-in is over-riding the network connection
[18:23] <TJ-> jaythelinuxguy: just done some testing with a new user. If I 'create user ...' and then 'grant all on *.* to ... with grant option;' I can log-in correctly over TCP
[18:24] <jaythelinuxguy> TJ: That's the behavior I'm seeing as well
[18:24] <TJ-> jaythelinuxguy: but as soon as I change the grant to be '...identified by unix_socket...' it no longer works. You cannot have multiple GRANT table entries for the same user@hostname
[18:25] <TJ-> so you cannot add an additional GRANT for the same user@host which doesn't use unix_socket.
[18:25] <TJ-> I'd describe that as a very bad GOTCHYA! bug - totally unexpected
[18:25] <jaythelinuxguy> Wow Ubuntu's implementation of MariaDB is getting stranger by the minute
[18:26] <TJ-> this is standard with unix_socket; these patches were added in Debian and that's why they're in Ubuntu
[18:38] <TJ-> it seems as this affects mysql 5.7 too - We've made the bug public and I've emailed the Debian maintainer
[18:54] <jaythelinuxguy> Thanks TJ for all your help, I'll watch the bug report as things develop
[19:00] <TJ-> jaythelinuxguy: I've added some notes about the failure scenario just now
[19:02] <TJ-> I thought I'd be sneaky and create another entry for root@localhost without the unix_socket, but the user table primary key is User|Host, grrr
[19:07] <TJ-> jaythelinuxguy: found a sneaky workaround :D
[21:08] <Madhumper69> after updating ubuntu it set grub to ro and not rw for my mounted swap file why is that? took a while to figure it out and fix it!
[21:12] <TJ-> huh?
[21:13] <alkisg> Madhumper69: err how is grub related to swap files?
[21:16] <Madhumper69> linux	/boot/vmlinuz-3.13.0-24-generic root=UUID=AAC884AC1F144321 loop=/ubuntu/disks/root.disk ro   quiet splash $vt_handoff                     had to change ro to rw
[21:17] <Madhumper69> in /etc/grub.d/forgetnameof file
[21:17] <alkisg> loop is not a swap file
[21:17] <Madhumper69> im running 16.04lts i copy pasted from forum
[21:18] <Madhumper69> resolved my issue anyways
[21:18] <MonkeyDust> Madhumper69  #ubuntu+1
[21:21] <TJ-> Madhumper69: the root file-system *should* be mounted 'ro' to being with; the init system will remount rw
[22:02] <Madhumper69> well by changing it to rw i can boot into gui otherwise i was getting mass errors and couldnt do anything
[22:02] <Madhumper69> lots dbus errors
[22:03] <Madhumper69> bare with me i am like 2months old to ubuntu and linux
[22:58] <genii> TJ-: BTW earlier when I did ubuntu-bug udev to report that issue, made the machine segfault. Just noticed it now as I'm shutting down for the night
[22:59] <TJ-> genii: ouch!
[23:00] <genii> Hockey watching time :)


[01:21] <bobweaver> ogra_,  Ping :)  just wondering if you know if there is a arm image for 12.04 ?
[01:23] <bobweaver> This says that it can work but where are the images ?
[01:24] <bobweaver> https://wiki.ubuntu.com/Nexus7/Installation
[04:35] <erikc> can i apt-get things like gcc and gdb on a nexus device with ubuntu touch preview and do development on the device directly?
[04:54] <cyphermox> erikc: yes you can
[04:55] <cyphermox> in the chroot, of course
[06:20] <jair> hello there team ;-)
[06:21] <jair> I am trying to clarify something about ubuntu-touch, is there a doc that explain the architectural layer of technologies that make ubuntu-touch?
[06:22] <jair> for example: 1]hardware layer 2] linux kernel 3] applications
[06:22] <jair> I know that android uses hardware-> linux kernel -> dalvic vm -> java -> apps
[06:23] <jair> is ubuntu-touch and it's apps dependant of java technologies as android?
[06:24] <wilee-nilee> butter cream frosting on a marshmallow base
[06:24] <jair> hmm can we be a little more technical?
[06:27] <jair> http://developer.android.com/about/versions/index.html
[06:27] <jair> this is an example of Android
[06:28] <wilee-nilee> pretty quiet here late at night U.S. time you might get responses during the day, weekends are a bit slower as well
[06:28] <jair> do we have something like this from ubuntu touch?
[06:28] <scarecrow_> Where can I find more information about Ubuntu Touch?
[06:29] <jair> I am checking right now the different pages in the ubuntu touch wiki
[06:29] <jair> scarecrow_: https://wiki.ubuntu.com/Touch
[06:34] <scarecrow_> If I wanted to create a tablet right now, what CPU architecture types are supported?
[06:36] <jair> scarecrow_: I will say all the architectures supported by ubuntu
[06:36] <jair> ubuntu OS
[06:36] <jair> but if you are like me and want to know the exact information: https://launchpad.net/~ubuntu-phone in that page is the technical team
[06:37] <wilee-nilee> ubuntu on top of android cm 10.1 I believe
[06:38] <jair> wilee-nilee: that mean the OS still depends of a large amount of Java?
[06:39] <jair> wilee-nilee: to run all the apps.  I will be installing the SDK and I am willing to work in app development but I hope I don't need to learn Java for it
[06:39] <jair> I just think Java is heavy
[06:39] <wilee-nilee> jair, Not sure to be honest.
[06:40] <jair> wilee-nilee: I appreciate your responses, I will send an email to the technical group
[06:40] <wilee-nilee> I'm not a developer just a regular user waiting for more development.
[06:40] <jair> understand, I am a user, wanting to become a developer ;)
[06:41] <wilee-nilee> jair, They seem to like help, so go for it. ;)
[06:41] <jair> wilee-nilee: definitely will is my passion, I prefer that that even woman LOL gives me more satisfaction
[06:42] <jair> I really need to learn a lot man
[06:42] <jair> but hey to the benefit of the people and family and personal
[06:44] <wilee-nilee> ;)
[06:53] <jair> will be back after reading a bit
[06:53] <jair> Thank you!
[07:56] <lilstevie> jair, ubuntu touch does not contain any of the dalvik vm technologies, userspace is a mix of standard native GNU tools, and a QT5 ui
[07:57] <lilstevie> jair, the android portion of ubuntu touch is purely for driver support, and the "x server" currently runs on surface flinger (at least until mir is ready)
[08:28] <Towleeeie9613> Does anyone know if there are going to be at least mostly functioning betas for ubuntu touch for non-developer use?
[10:10] <hempe> Hy everyone. I'm currenty working on a simple c++ application for ubuntu touch (to create a tutorial) and ran into one big problem. When I request a build on launchpad it only builds for amd64 and i386 but not for arm. the problem seems to be, that the build dependencies like qt5-qmake, qtdeclarative5-dev and libqt5v8-5-dev are not available for arm. does anybody know how to resolve this problem?
[10:59] <hemangpatel> Hello guys
[11:00] <hemangpatel> is ubuntu phone targeting iOS and android ?
[11:19] <snuggl> hemangpatel: ubuntu touch *is* an android dist
[11:19] <snuggl> so no iOS
[13:08] <Romario> How fast is development coming along? For example I havent seen change in Galaxy Note section in quite a while... What is the estimate from BETA to full release?
[13:32] <nik90> Romario: we haven't even reached Beta yet.  Infact the alpha 1 milestone will be on the 16th of May (atleast for the core apps like Calendar, clock, Weather etc)
[13:33] <nik90> Romario: as for  the support of other mobile devices, please note that only nexus variants are officially supported while other devices like Galaxy Note, S2, S3 etc etc..are handled by the community.
[13:33] <nik90> Romario: so if you arent seeing much progress with the Galaxy note, then it could be that the community member working on it is busy with other stuff
[14:43] <jjp_> how in ubuntu touch ... any users
[14:44] <Deihmos> Dead
[16:19] <lolprikky> installed touch on nexus 7, lost power and device died, now it wont turn back on. what do
[16:19] <lolprikky> current
[16:20] <Guest42075> Is there a version of ubuntu touch for a Anderson 2.5 tablet? Ive been searching and couldnt find
[16:21] <Guest42075> Anderson ADT 2.5 was it's name
[16:26] <lolprikky> please, anyone can halp?
[16:26] <lolprikky> i believe my device has been bricked it doesnt even wanna boot into recovery mode
[16:29] <Tassadar_> lolprikky: it doesn't do anything even if you hold the power button for 10s?
[16:31] <lolprikky> nop
[16:31] <lolprikky> o wait
[16:31] <lolprikky> now a google logo popped up
[16:31] <lolprikky> ah there we go
[16:31] <lolprikky> that was a long 10 seconds
[16:32] <lolprikky> ok
[16:32] <Tassadar_> yeah, it is like "reset" button on a PC
[16:32] <lolprikky> i have a nother question, when trying to input the wifi password there is no keyboard appearing ...
[16:33] <lolprikky> i just got this stuff installed
[16:34] <lolprikky> is there a way to enable on screen keyboard?
[16:34] <lolprikky> its kinda hard to type without one lol
[17:02] <Safa_[A_boy]> Hi all, I have a nextbook 7SE with google play, I'm trying to unlock the bootloader, this is the results from the tablet:
[17:02] <Safa_[A_boy]> http://pastebin.com/uu6RAn7R
[17:02] <Safa_[A_boy]> I I bought the device to install Ubuntu on it ^_^
[17:04] <Tassadar_> well, it's bootloader can't be unlocked then
[17:10] <Safa_[A_boy]> Why?
[17:11] <Tassadar_> the manufacturer did not enable it, or, in this case, it is not even implemented
[17:12] <Tassadar_> you should've bought some supported device
[17:14] <Safa_[A_boy]> and how could I know that?!
[17:14]  * Safa_[A_boy] bad luck!
[17:15] <Tassadar_> https://wiki.ubuntu.com/Touch/Devices
[17:16] <Tassadar_> or, you can try to port ubuntu touch to that device, if you have the knowledge needed
[17:17] <Safa_[A_boy]> I bought this one because it's cheap :p
[17:17] <Safa_[A_boy]> I don't know how to port
[17:17] <Safa_[A_boy]> anyway, thanks for your help
[18:21] <omac> good afternoon everyone
[18:21] <omac> I just installed ubuntu touch quantal-2502.zip using scanno's recipe.
[18:22] <omac> Are there more recent and more functional images available here?
[18:23] <omac> I don't have wpa_supplicant connecting to wifi yet.
[18:23] <omac> it takes about 4 minutes to boot up.
[18:24] <omac> The gui itself is barely responsive at first.   The left edge menu seems to respond.
[18:24] <omac> But the browser and the other apps don't actually seem to work on this version.
[18:25] <omac> I can adb shell, ubuntu_chroot into it.
[19:22] <omac> ERROR [ctrl_interface]: Read-only file system
[19:23] <omac> insmod /data/ubuntu/system/lib/hw/wlan/ar6000.ko      ip link set wlan0 up         wpa_supplicant -B -Dwext -i wlan0 -c /etc/wifi/wpa_supplicant.conf
[19:23] <omac> the insmod was ok.  the ip link showed wlan0 was up.
[19:23] <omac> the read only showed up after the wpa_supplicant command.
[19:23] <omac> does anybody know how to fix this?
[20:36] <techzilla> hello is anyone on online?
[20:37] <techzilla> just wanted to ask, if any unofficial/official support existed for the quad core A9 samsung chipsets?
[20:37] <techzilla> ...or even a ppa...., anything really
[20:38] <techzilla> not loving the idea of an expensive first generation A15 tablet, or an inexpensive first generation A9 tablet.
[20:39] <techzilla> top that with a lack of A15 quad core chipsets in production, and the supported A9 is the tegra....
[20:40] <techzilla> really doesn't actually matter if the A9 was sansung, could be anything quad-core A9, non-tegra, and with a workable GPU.  such as the quad-core freescale stuff
[20:43] <nik90> techzilla: u might want to ask this tomorrow during a weekday since everyone if off today :)
[23:05] <bobweaver> anyone know how to get parent node items form a xmllistmodel ?   say that I am searching api       source:""
[23:05] <bobweaver>     source:somesource     query: "/ProgramGuide/Channels/ChannelInfo/Programs/Program"    XmlRole {name: "StartTime"; query: "StartTime/string()"}          XmlRole {name: "chanchan"; query: "../../ChanId/string()"
[23:05] <bobweaver> so that chanchan returns path  of  source//ProgramGuide/Channels/ChannelInfo/ChanId
[23:06] <bobweaver> But "StartTime" would  use the path  source//ProgramGuide/Channels/ChannelInfo/Programs/Program/StartTime    so that I can test them later on


[07:53] <chelz> i'm looking over info about the Global Jam but in terms of a time or event where people are encouraged to seek out all the hardware they can, and encourage people they know to seek out all the hardware those people can, for making any necessary tweaks in default Ubuntu so it works out-of-the-box. is there a time/event one focused on hardware
[11:28] <edakiri> I would like to propose 2 changes to pre-release Ubuntus to increase reliability and aid testing:
[11:29] <edakiri> #0 : Have the default color scheme be atypical (such as light foreground and dark background) or randomly generated.  This will increase awareness and fixing of faulty color handling in applications.
[11:30] <edakiri> #1 : Everything compiled with GCC gets at least debugging symbols of level -g1, which enables a stack trace.
[13:04] <jpds> edakiri: We have -dbg package for #1.
[15:07] <persia> Well, if there is no -dbg package, there may be ddebs
[15:36] <edakiri> persia: Some times there is no -dbg package.   Some other times I have been unable to find it. Some other times, many packages debug symbols were bundled into a big debug package, which i had inadequate space to install.  Some times the error is sporadic and if you do not already have the debug information installed, you will miss the opportunity. Everyone should be considered testing if it is not a released distribution. The debug package
[15:37] <persia> edakiri: Like I said, lots of packages have ddebs, rather than -dbg packages.
[15:37] <edakiri> i don't know about ddebs. i will look into it
[15:37] <persia> Having everything with debug symbols until release freeze means a 3 month gap between when work stops on a release and when the release happens: that is too expensive.
[15:38] <edakiri> persia: why would there be a gap?
[15:39] <persia> Because we'd have to recompile everything to not have the symbols in order to fit it on a CD.
[15:39] <edakiri> It doesn't take 3 months to recompile, does it?
[15:39] <persia> At least.  Maybe longer.
[15:39] <persia> Remember that there are more than 20,000 packages.
[15:41] <edakiri> I used to run Gentoo.  It makes installing from source packages sound more efficient. --or a mix.
[15:45] <persia> That only works if you have relatively fast hardware.  At least some of my devices would be useless with that model.
[16:05] <edakiri> I don't know how it would work with a mobile phone, but compiling without optimization, it installed swiftly enough - and i installed the way that rebuild even libc.
[19:59] <flax> hello, i have this freezing 10.04 ubuntu, it happens after i press the <enter> key
[20:00] <flax> the system is still running (have an sshserver running)
[20:00] <flax> but it appears as if the system is completely frozen,...
[20:00] <flax> any clues how i can recover my system?
[20:02] <persia> flax: There's a bug about that (I forget the number), and I think it was fixed.
[20:02] <persia> Someone in #ubuntu+1 might be able to give you support on working around it.
[20:02] <flax> thanks!