[03:35] <aaron_liuj> where i can get the whole doc of build chrome
[04:45] <persia> aaron_liuj: Could you be a bit more precise about which materials you seek?
[04:57] <aaron_liuj> i want to comiple  chrome for arm platform
[04:58] <aaron_liuj> but i find building chromium is so different from other plalform
[05:05] <aaron_liuj> but i find building chromium is so different from other build system such as autoconfig automake
[05:49] <persia> so, "chrome" and "chromium" are different, in that "chrome" contains special branding magic.
[05:50] <persia> If you download the source (`apt-get source chromium-browser`), there is a file debian/rules that contains the instructions to build the source.  Build logs are available on laiunchpad.
[05:51] <persia> If you've an armel install, building for arm is as simple as `apt-get build-dep chromium-browser; debuild -b` in the downloaded sources (although we usually recommend tools like sbuild or pbuilder(
[07:39] <cooloney> amitk: do you know the quick way to import the omap4 defconfig based on our ti-omap branch configs?
[07:39] <cooloney> amitk: i already rebased the omap4 branch from omapzoom git server
[07:40] <cooloney> amitk: need to tweak the configs
[07:41] <cooloney> how about copy over omap4 defconfig to debain.ti-omap/configs/config.commom.ubuntu
[07:41] <cooloney> and run fdr genconfigs?
[07:41] <amitk> cooloney: I'd append the omap4defconfig at the _end_ of the ubuntu config and then run updateconfigs
[07:42] <cooloney> amitk: oh, at the end of debain.ti-omap/configs/config.commom.ubuntu?
[07:42] <amitk> copying over the defconfig to our config will lose all our ubuntu-fication tweaks
[07:42] <amitk> e.g. apparmor, security settings, etc.
[07:42] <cooloney> amitk: right, i lost them,
[07:43] <amitk> cooloney: cat omap4defconfig >> debain.ti-omap/configs/config.commom.ubuntu
[07:43] <cooloney> amitk: ok, got it. thanks man, will try soon
[07:56] <zyga> good morning folks
[07:57] <cooloney> amitk: too bad, i tried that, but the new config lost all the modules.
[07:58] <cooloney> amitk: it seems like it turned off all the module configs
[07:58] <cooloney> any idea about that?
[07:58] <amitk> cooloney: I guess the omap4defconfig turns off modules?
[08:00] <cooloney> amitk: no, it enable modules as the same as our omap3 config
[08:00] <cooloney> CONFIG_MODULES=y
[08:00] <amitk> cooloney: try this, cat omap4defconfig | grep "=[ym]" > /tmp/omap4; cat /tmp/omap4 >> debain.ti-omap/configs/config.commom.ubuntu
[08:01] <cooloney> but aparently, there is no modules config in omap4defconfig
[08:03] <amitk> ok
[08:06] <cooloney> amitk: btw, i am trying with arch/arm/configs/omap_4430sdp_defconfig as omap4defconfig, since there is no other configs looks ok to me
[08:06] <cooloney> amitk: this trick works,
[08:06] <cooloney> thanks a lot
[08:07] <amitk> cool
[08:07] <alf__> good morning all!
[08:07] <amitk> alf__: morning
[08:19] <zyga> the ubuntu group photo is online :-)
[08:19] <zyga> http://www.flickr.com/photos/kwwii/4610334160/
[08:26] <hrw> morning
[08:27] <hrw> zyga: thx - I am 3rd from left in first row
[08:28] <zyga> hrw, yeah, I saw you right away
[09:20] <zyga> toolchain guys, package guys, I have a question - let's say you push a toolchain patch that affects something (be it code size or some critical bug fix) - how can I (qa guy) determine which set of packages were used to build/cross build certain package - I want to be able to tell 'ah package FOO-1.2-0 was built with old toolchain while FOO-1-2.1 was built with the new toolchain'
[09:20] <zyga> is this even possible? do we always bump package version on rebuild?
[09:21] <zyga> (or the inverse question, do we always rebuild as a consequence of an upload with version change)
[09:21] <zyga> lool, ^^ >
[09:21] <hrw> good question. I can not answer as I did not upload package in Debian
[09:22] <persia> You can check the build log in LP.
[09:22] <zyga> I have one use case that would require this and I need to check if it's even possible: tracking code size across releases
[09:22] <zyga> and, in crazy situations, across toolchain changes
[09:23] <zyga> persia, LP has a collection of build-deps for each package it built? with rich package version etc/
[09:24] <persia> Absolutely.  See https://launchpad.net/ubuntu/+source/libvirt/0.7.5-5ubuntu27/+build/1702547/+files/buildlog_ubuntu-lucid-armel.libvirt_0.7.5-5ubuntu27_FULLYBUILT.txt.gz as an example/
[09:24] <persia> Note that this is a verbose format, so you'd have to parse, but there's often other interesting things in the log if you're tracking down a regression when you don't think the source changed.
[09:25] <zyga> persia, hmm, parsing is fragile, does any other part of launchpad maintain a more declarative format for the meta information of each build>
[09:25] <persia> Every upload generates a new build, and rebuilding the same source twice without an upload is only accepted in the case where the first attempt FTBFS.
[09:26] <zyga> persia, so what would happen if we push a new toolchain? nothing - r-deps do not become invalid?
[09:26] <persia> Note that from the fragmentary bits I got from some of the UDS discussions, this may not hold true for some classes of repository, but it is how it is implemented in Soyuz today.
[09:26] <zyga> persia, (we have to upload each package again just to see it rebuilt?)
[09:26] <persia> Yep.
[09:26] <hrw> persia: what about 'binary NMU'? they have same source but 'b1' added to version
[09:26] <zyga> hrw, good question, I was about to ask for that - someone mentioned this during a session
[09:26] <persia> There's ways to arrange test-rebuilds against arbitrary toolchains with throwaway results, which the toolchain team uses.
[09:27] <persia> hrw: We don't have binNMUs in Ubuntu.
[09:27] <zyga> mmm
[09:27] <zyga> okay, some of the bits are more clear now, thanks
[09:27] <persia> heh.
[09:27] <zyga> I think my use case is not really sensible then ;-)
[09:28] <persia> What was your use case?
[09:28] <hrw> persia: ok
[09:28] <zyga> persia, tracking daily/weekly binary object sizes vs toolchain revision
[09:29] <persia> zyga: Yeah, you'd need a rebuild-repo for that, and it's a heavy load on the buildds.
[09:29] <persia> (or some other class of derivative repo)
[09:30] <zyga> persia, building a sub-main variant could make sense too - like what I did some time ago - toolchain kernel libc and some basic userspace
[09:30] <zyga> it takes 3 hours to build this on 8 way xeon inside a ramdisk
[09:31] <persia> I guess.  That's more an embedded design pattern, and we don't tend to do embedded here.
[09:31] <zyga> and the results are quite representative for the whole repository
[09:33]  * zyga has a crazy idea
[09:34] <zyga> hrw, oe could build our toolchain and some packages to check for binary size experiments
[09:34] <hrw> zyga: it can, but writing recipes for it would take time
[09:34] <zyga> hrw, yeah but if the new toolchain is such a big issue then it could be reasonable
[09:35] <persia> zyga: If you're just experimenting locally, why not just use schroot+qemu-user-arm+croco, and use the debian/rules files that already exist.
[09:35] <zyga> croco? what is that
[09:36] <persia> croco is a system that allows you to wrap various binaries in a cross-arch chroot and run native.  For example, there's no good reason to run armel bash to process a bash script during build when doing local cross-compile analysis.
[09:36] <zyga> persia, one of the things I don't want to depend on is qemu - it's currently broken and it really kills performance - OE approach has the strength of working cross compilation of selected packages
[09:36] <persia> The results are likely to vary from those build on the buildds, but that's a different issue.
[09:36] <persia> Which bit is broken?
[09:36] <persia> Note that not all debian packages *can* cross-compile.
[09:36] <zyga> persia, qemu bit - lool will tell you how it currently hangs/crashes under heavy load
[09:37] <persia> Also, using soemthing like croco makes it significantly less slow.
[09:37] <zyga> persia, I have a bunch of backtraces if you want to see
[09:37] <zyga> persia, that's true, it could be reasonable tradeoff for time-to-make-it-happen vs time-to-build-each-time
[09:37] <persia> I believe you.  It doesn't tend to crash for me, but I don't push it hard.  Was that qemu-system-arm or qemu-user-arm?
[09:38] <zyga> system
[09:38] <ogra> zyga, the chroot bit of qemu isnt broken, only qemu-system-arm is, i think croco hooks into the static builds
[09:38] <persia> Oh, yeah, I'm not advocating that for builds at all.
[09:38] <ogra> s/hooks into/can hook into/
[09:38] <persia> croco works best with qemu-user-arm
[09:38] <ogra> right
[09:38] <zyga> then it could be just right
[09:39] <persia> It does things like call the right cross-compiler instead of calling the native compiler, but it still provides the ability to run native code, which helps with stuff like test suites.
[09:39] <ogra> its a bit like OBS
[09:40] <persia> kinda sorta :)
[09:40] <zyga> OBS?
[09:40] <persia> OpenSuSE Build System
[09:40] <ogra> opensuses build system
[09:40] <ogra> bah, i'm slow today
[09:41] <persia> And following in the footsteps of e.e. cummings :)
[13:26] <neure> how is 10.04 on beagle?
[13:27] <zyga> neure, somewhat choppy, depends on which version you are talking about
[13:27] <amitk> neure: it works on the C4 beagles
[13:27] <amitk> older ones aren't yet supported
[13:29] <neure> how do i see my version?
[13:30] <neure> how about C3?
[13:30] <neure> what is different C3 -> C4?
[13:31] <amitk> http://elinux.org/BeagleBoard#Revision_A
[13:37] <neure> apparently i have C2
[13:37] <neure> so is the "Improved USB Host PHY power rails" that might affect keyboard / mouse?
[13:38] <neure> whatever that means..
[13:38] <XorA> neure: means USB actually works reliably on all C4
[13:39] <XorA> neure: USB EHCI is hit and miss on earlier beagles
[13:39] <neure> EHCI?
[13:39] <neure> ok
[13:39] <XorA> the normal looking usb port, not the mini B OTG port
[13:39] <amitk> neure: in addition to what XorA said, we have no real reason _not_ to support older beagles except lack of old HW.
[13:39] <neure> ok
[13:40] <XorA> amitk: the installer works fine on C3, just because usb is screwed you cant install
[13:40] <neure> so if i use the mini B port, it should work even on C2?
[13:41] <rcn-ee> neure, you can use the otg port using my NetInstall setup on elinux using the commuinty kernel...
[13:42] <neure> im currently running ångström on it
[13:43] <neure> i could try ubuntu
[13:43] <neure> on the other hand, i'd like to try something with rt linux kernel
[13:43] <siji> my experience, I have got better performance with ubuntu than Angstrom
[13:43] <siji> Specially with Clutter /EGL etc..
[13:44] <rcn-ee> amitk, just hit bug 563650 with 2.6.34 + dss2 -for-next with my kernel.. discussion on linux-omap... http://www.spinics.net/lists/linux-omap/msg30138.html
[13:44] <ubot2> Launchpad bug 563650 in linux-ti-omap (Ubuntu Lucid) (and 1 other project) "DSS2 oops when shutting down while DPMS is active (affects: 1) (heat: 10)" [Medium,Confirmed] https://launchpad.net/bugs/563650
[13:44] <amitk> siji: is angstrom compiled with NEON and ARMv7 ?
[13:45] <XorA> amitk: of course we do :-D
[13:45]  * XorA puts on his Angstrom maintainer hat
[13:45] <siji> :)
[13:46] <siji> amitk, with ARM v7
[13:46] <amitk> XorA: just curious why siji is seeing the difference, is all :)
[13:48] <amitk> rcn-ee: aah, any headway?
[13:48] <rcn-ee> it might just be a thumb2 thing..
[13:48] <rcn-ee> amitk, nope... just triggered the latest opps about 10 mins ago..
[14:46] <james_w> I have my beagle partially booting now, but due to having no rtc battery it won't get pass fsck, is there a way to force mounting without an interactive shell?
[14:47] <ogra> james_w, with the official image you can just set fixrtc on the cmdline
[14:47] <ogra> we have a workaround in initramfs
[16:09] <ogra> XorA, do you happen to know which DSS2 patches are missing exactly to make the zoom work in ubuntu ? (same question for touchbook)
[16:09] <ogra> i'd like to have screen support for both of them in maverick
[16:09] <ogra> (just basic stuff is enough though)
[16:10] <XorA> ogra: no, the dss2 in the TI zoom2 tree is slightly different to what entered mainline, the patches all need rejigged
[16:10] <ogra> hrm
[16:11] <XorA> ogra: ask koen about touchbook, he at least has one
[16:11] <XorA> ogra: and pandora support in maverick should happen as well
[16:11] <ogra> it boots fine here with an ubuntu install ... i just cant convince it to output to the screen ...
[16:11] <ogra> nobody on the team has a pandora
[16:11] <XorA> ogra: no-one has a pandora yet
[16:12] <XorA> ogra: I will have before maverick
[16:12] <ogra> sweet ... i'll hunt you down for testing it then
[16:12] <lool> zyga: Build information > yes, the versions are recorded in the log, but as you note it's a bit fragile and doens't cover everything; there's a dh_buildinfo which does something more extensive
[16:13] <XorA> ogra: youll have to come to #linux-omap and pester the guys there for zoom2 support
[16:13] <ogra> will do
[16:13] <ogra> we dont have a maverick kernel yet though
[16:13] <ogra> i'm just looking into the missing bits atm
[16:14] <XorA> ogra: well just getting patches against lucid would be good, DSS2 wont change that much now
[16:14] <lool> davidm: Sure, I already had chats with prpplague on the upcoming LCDs
[16:14] <lool> davidm: Thanks for the contact
[16:14] <ogra> XorA, maverick will use 2.6.35
[16:14] <XorA> ogra: there was nothing controversial in the 2.6.35 pull request for dss2
[16:14] <ogra> so we need them against that one
[16:14] <ogra> great
[16:15] <XorA> ogra: so the patches should only need slight rejig between lucid/maverick, its just finding someone with time to do them clean
[16:15] <ogra> lucid is done, all i care for wrt lucid is 10.07 which uses its completely own kernel
[16:15] <XorA> Im not on the TI display team
[16:16] <ogra> but you are owning all that knowledge :)
[16:16] <XorA> ogra: sumitsemwal I think knows the actual guys who own that part of kernel
[16:16]  * zyga is bac
[16:16] <zyga> k
[16:17] <ogra> ok, i'll first wait to see what we get with the maverick kernel
[16:17] <XorA> ogra: extend my day to 48 hours and Ill do it :-D
[16:17] <ogra> and whats still missing
[16:17] <ogra> heh
[16:17] <ogra> i assume dss2 improved between .33 and .35
[16:18] <XorA> I think bugfixes only, no architectural changes
[16:18] <ogra> hmm
[16:26] <sumitsemwal> XorA: :) .. I will ask people who're involved with the DSS2 to join.. maybe tomorrow?
[16:27] <amitk> sumitsemwal: good to see you hang out here :)
[16:27] <ogra> yeah !
[16:28] <sumitsemwal> amitk: newbie, be gentle :P
[16:30] <amitk> sumitsemwal: hehe :)
[21:58] <NCommander> sebjan: ping?
[22:00] <NCommander> robclark: ping?
[22:00] <robclark> NCommander: pong
[22:01] <NCommander> robclark: see PM
[22:02] <ogra_cmpc> robclark, how did you compile the kernel i have on the blaze ? i see a lot of segfaults using a lucid rootfs
[22:03] <ogra_cmpc> was it cross built ?
[22:04] <robclark> ogra_cmpc: y, it was cross built.. but I don't think that is the issue
[22:04] <ogra_cmpc> hmm
[22:04] <robclark> I wonder if you are just seeing the empty_zero_page issue..
[22:04] <robclark> kernel is unlikely to get pissy over glibc or runtime lib mismatch..
[22:04] <ogra_cmpc> might be i just noticed that git, dpkg and apt segfault
[22:05] <robclark> ogra_cmpc: yeah, that sounds like the issue... give me a minute and I'll post real simple test code to see if you hit that..
[22:05] <ogra_cmpc> i didnt resarch anything yet, juwst playing around with it while watching tv
[22:05] <robclark> avoid 'git clone'
[22:06] <robclark> that is really good at triggering the problem
[22:06] <ogra_cmpc> heh, noticed that
[22:06] <ogra_cmpc> yeah
[22:06] <ogra_cmpc> fatal: git fetch_pack: expected ACK/NAK, got ''
[22:06] <robclark> yup, that's the one
[22:06]  * ogra_cmpc was already worried its gits fault in out amrel build
[22:07] <ogra_cmpc> *armel
[22:07] <ogra_cmpc> until i noticed apt and dpkg suffering too
[22:07] <robclark> it is an arm arch prob in kernel.. from looking at code, I'm not really sure how it should work.. how copy_to_user() would trigger a page fault..
[22:08] <robclark> one of our baseport guys claims to not see this bug.. using a newer kernel, but unsure about what commit fixes it (if it is indeed fixed)
[22:08] <robclark> but I've been busy with other debugging since I got back, so haven't had a chance to revisit that issue
[22:09] <ogra_cmpc> we'll see, i think cooloney already works on a kernel package thats based on a checkout from today
[22:09] <robclark> ogra_cmpc: if you need a quick stop-gap solution, an older version of git (1.5.x) doesn't seem to trigger it
[22:09] <ogra_cmpc> i should be able to test it within the next days
[22:10] <ogra_cmpc> well, i usually dont even touch git :) but i can host trees on my laptop if needed and just rsync back and forth
[22:10] <ogra_cmpc> <- bzr user ...
[22:10] <robclark> ok.. let me know if you discover anything... it's on my list of interesting things to debug, but unfortunately I have some less interesting things to debug first ;-)
[22:10] <ogra_cmpc> heh, k


[06:03] <quickshotdevs> New news from manualplanet: Benjamin Humphrey: Brussels, beer, Ubuntu and boys taking a leak
[08:25] <ubuntujenkins> morning
[08:33] <nisshh> ubuntujenkins: hey
[08:33] <ubuntujenkins> hello nisshh
[08:34] <nisshh> ubuntujenkins: that ooa works great
[08:34] <nisshh> ppa
[08:35] <ubuntujenkins> that was the plan :P . So far we have no bugs with it I hope it stays like that
[08:47] <ubuntujenkins> godbyk: can we add the ppa to the website?
[09:10] <ChrisWoollard_> I also agree. That ppa works a treat.
[09:40] <dutchie> problem #42 in making the bug form work: debian has bzr 1.5, launchpad requires bzr 1.16 to download branches
[10:29] <popey> dutchie: upgrade bzr?
[12:08] <dutchie> popey: yeah, going to have to
[12:12] <dutchie> stupid inferoior 2g connection
[12:36] <dutchie> bah
[12:36] <dutchie> no godbyk or daker :(
[12:39] <thorwil> dutchie: look on the bright side! i'm here and most likely totally useless regarding whatever you have on your mind or at hand ;)
[12:41] <dutchie> do you know if there is a 500/404 page used on u-m.org?
[12:41] <dutchie> that I canborow
[12:45] <thorwil> http://ubuntu-manual.org/thequeenisnotamused
[12:45] <thorwil> apparently the url is interpreted as far as possible, so you always get at least the home page :(
[14:28] <nisshh> godbyk: there is a guy asking on lp when the german version of e1 will be released, apparently its now fully translated on lp
[14:30] <nisshh> godbyk-android: ^^^
[15:27] <ChrisWoollard_> There have been a lot of bugs filed today against the manual!
[15:28] <dutchie> godbyk: CNAME bugs.ubuntu-manual.org to um-bugs.joshh.co.uk
[15:30] <ubuntujenkins> ChrisWoollard_: my inbox noticed :-)
[15:32] <ChrisWoollard_> It looks like a guy called Marc Stewart is reading the intire book and logging bugs as he goes. He is on page 36 at the moment. :)
[15:33] <ChrisWoollard_> i mean entire
[15:33] <ubuntujenkins> at least we will be very bug free
[15:34] <ubuntujenkins> dutchie: your form asks for an e-mail. Where in the bug report does that go? will it not be traceable by bots?
[15:35] <ChrisWoollard_> Some of those bugs are tricky. He is really pushing my knowledge of english grammar. So much so that I have had to get a book out to help.
[15:37] <ubuntujenkins> I thought i would try and help. but then i looked at how complex they can be and decided my english is not up to it. I am a mechnical engineer we are better at maths
[15:41] <ubuntujenkins> be back later
[15:41] <ubuntujenkins> o/
[15:41] <ChrisWoollard_> I am going to spend my evening trying to make sense of some more. At least he is explaining his reasoning behind the changes.
[15:41] <ChrisWoollard_> See you
[15:51] <dutchie> ubuntujenkins: it doesn't go anywhere yet
[15:52] <dutchie> i may remove it
[15:53] <dutchie> initially I just copied the fields from the spreadsheet
[15:53] <dutchie> now it's up, i can start to get some feeback
[15:53] <dutchie> +d
[15:54] <dutchie> just don't let humphreybc publicise it everywhere, as it's nowhere near ready
[15:55] <dutchie> right, hometime
[17:27] <ubuntujenkins>  dutchie message recived I will stop ben if i see someone tell him
[18:16] <godbyk> I'm home again.
[18:16] <godbyk> I'll take a look at the ubuntu-manual bugs in a moment.
[18:16] <godbyk> Going to have lunch first.
[18:54] <ChrisWoollard> There are lots
[18:55] <godbyk> ChrisWoollard: No problem. I can usually blow through them pretty quickly.
[18:55] <godbyk> I'm fairly good at US English grammar.
[18:55] <godbyk> (And don't mind telling people that they're wrong.) :)
[18:57] <godbyk> is anyone else editing right now that I'll interfere with?
[18:58] <ChrisWoollard> Not at the moment. After I put my children to bed. I'll mark bugs as in progress if I am working on them.
[19:03] <godbyk> okay, cool.
[19:03] <nisshh> godbyk: let me know when you go through and hunt for glossary entries, no rush but id like to get a whole bunch more in there
[19:03] <godbyk> I'm gonna eat lunch real quick and then I'll dive in.
[19:03] <godbyk> nisshh: absolutely!
[19:03] <nisshh> cool
[19:03] <godbyk> nisshh: you might post a message to the list and ask people what they think should be in the glossary and index, too.  just so we have some ideas.
[19:04] <godbyk> nisshh: oh, and you shouldn't have self-referencing glossary entries.  don't use \gls{thisword} in the 'thisword' entry. (there's not much point.)
[19:04] <nisshh> godbyk: right, and since chapter 6 is no longer going to be in the manual after 10.10 i might take over the maintenance of the index
[19:04] <nisshh> godbyk: good point ill remove those tommorrow
[19:05] <godbyk> 'kay.
[19:05] <godbyk> we'll collect ideas for the index. I'll work with you on it a bit later.
[19:05] <godbyk> (it's easy; we just need to make sure we set some rules for consistency.)
[19:05] <nisshh> right, like we are doing for the rest of the manual
[19:05] <godbyk> yep
[19:06] <nisshh> ok, ill post to the ML in the morning
[19:06] <nisshh> my brain is starting to die now that its 2am
[19:07] <godbyk> heh.. no worries.
[19:07] <nisshh> anyways, ill cya in the morning probably, gnight!
[20:00] <godbyk> Okay, time to crush some bugs.
[20:14] <godbyk> Right now I'm just going through and assigning most of the grammar-related bugs to myself.  I'll start editing them in a little bit.
[20:18] <ChrisWoollard> I have also started working on bugs
[20:19] <godbyk> ChrisWoollard: feel free to dive in. I've assigned a bunch of them to myself. (mostly the grammar and formatting bugs.)
[20:19] <godbyk> I have to send out a few emails, so I won't be stepping on your toes in bzr for a little while yet. :)
[20:20] <ChrisWoollard> As
[20:21] <ChrisWoollard> I am going to work on one thing at a time and mark in progress as I am going
[20:21] <ChrisWoollard> I am going to prop
[20:21] <ChrisWoollard> probably work on anything that isn't formatting
[20:23] <godbyk> okay.
[20:23] <godbyk> I think I stole most the formatting bugs, too.
[20:23] <godbyk> :)
[20:23] <dutchie> godbyk: did you do the CNAME?
[20:24] <godbyk> dutchie: uh, nope. where do you want me to point it?
[20:24] <dutchie> um-bugs.joshh.co.uk
[20:24] <dutchie> should be ready to go
[20:25] <godbyk> okay.
[20:25] <godbyk> setting it up now
[20:26] <dutchie> (you can observe it running at that address, too)
[20:27] <godbyk> I've added the CNAME record.
[20:27] <godbyk> It may take a moment for it to propagate to all the DNS servers, of course.
[20:28] <godbyk> But it looks like it's working here already.
[20:28] <godbyk> http://bugs.ubuntu-manual.org/
[20:28] <ubuntujenkins> works for me
[20:28] <Zeike> me too
[20:28] <godbyk> submitting a bug to test it. :)
[20:28] <godbyk> what's the story with staging.launchpad.net, anyway?
[20:29] <dutchie> testing purposes :)
[20:29] <godbyk> my bug: https://bugs.staging.launchpad.net/ubuntu-manual/+bug/580292
[20:29] <dutchie> feedback?
[20:30]  * ubuntujenkins has a go
[20:30] <godbyk> I would probably set English and Spelling.. as the defaults for the dropdown lists.
[20:30] <godbyk> (the language in the end should default to the browser language, but we only have the english edition out so far.)
[20:30] <Zeike> Does anybody want to give this a quick look through and tell me what you think? http://pastebin.ubuntu.com/439510/
[20:30] <godbyk> maybe add a note telling them where to find the revision number (bottom of the copyright page)
[20:31] <ubuntujenkins> you can type letters in the number feild
[20:31] <godbyk> Zeike: what am I looking at?
[20:31] <dutchie> ubuntujenkins: but if you click submit, it shouldn't let you
[20:31] <dutchie> godbyk: noted
[20:31] <godbyk> of course, we'll want to pretty up the formatting at some point, but I assume you're not asking about that. :)
[20:32] <dutchie> well, yeah, that too
[20:32] <Zeike> Its the file system section from the command line chapter.  Page 121
[20:32] <ubuntujenkins> dutchie: my bad had not got that far
[20:32] <godbyk> seems okay. was there anything we had on our google bug form that didn't transfer over?
[20:32] <godbyk> dutchie: ooh, could you have it do a lookup on the supplied page number to add the chapter name to the bug report, too?  makes it easier to find the bug on our end.
[20:33] <godbyk> (I realize it's variable depending on the revision, but it'll give us an idea.)
[20:33] <godbyk> (and it beats me grepping the .tex files for a phrase)
[20:33] <ubuntujenkins> also the suggestion box doesn't show in the bug report or a i mad?
[20:34] <dutchie> godbyk: that sounds, er, fun
[20:34] <dutchie> i was going to add in a dupe finder based vaguely on what we have in the DB
[20:35] <dutchie> could just add in a "chapter" ox
[20:35] <dutchie> +b
[20:35] <godbyk> true. as long as it's not too much to ask of people. :)
[20:37] <dutchie> yeah
[20:37] <dutchie> could probably collapse some of those entries down a little
[20:38] <godbyk> default the revision entry to the current released edition of the translation/language they selected.
[20:38] <dutchie> hang on
[20:38] <dutchie> need to find somewhere to make notes
[20:42] <dutchie> ubuntujenkins: i don't think i added the suggestion box to what shows up in LP, so no, you're not mad :)
[20:43] <ubuntujenkins> hehe I think i may be mad any way :P
[20:44] <dutchie> entirely possible
[20:45] <ubuntujenkins> godbyk: can we update the website with the latex ppa?
[20:45]  * dutchie shares the todo doc with other @ubuntu-manual.org folks
[20:47] <godbyk> ubuntujenkins: you mean edit the text on the site?  sure. I'll add it to my list. :)
[20:47] <ubuntujenkins> cheers godbyk :)
[20:47] <dutchie> godbyk: know if there is an easy way to make it visible to UMP folks?
[20:47] <dutchie> (via google docs)
[20:48] <godbyk> dutchie: I'm not sure. other than sending a link.
[20:48] <godbyk> lemme see if it shows up in my list.
[20:48] <dutchie> i don't think it will
[20:49] <godbyk> gah.
[20:49] <godbyk> google's captcha's are the worst!
[20:49] <ubuntujenkins> godbyk: I have sent you the instructions to save you finding them on the mailing list
[20:50] <godbyk> ubuntujenkins: thanks
[20:51] <ubuntujenkins> thanks for doing it I have not looked into how to add stuff to the website yet. I need to sort out a quickshot one
[20:51] <godbyk> dutchie: yeah, it's not in the list.
[20:52] <godbyk> if you go to the sharing dialog, I think there's a 'share with all @ubuntu-manual.org users' checkbox or something.
[20:52] <godbyk> ubuntujenkins: no problem.
[20:52] <dutchie> i can't see one
[20:52] <godbyk> ubuntujenkins: basically just edit a file and commit it. the server auto-pulls every so oftetn.
[20:52] <dutchie> i think that's because i created it with my normal @googlemail.com account
[20:52] <godbyk> ah, that's probably why.
[20:53] <dutchie> the accounts are linked together though
[20:53] <ubuntujenkins> godbyk: yea i guessed but i need to make sure i do it correctly etc. I will add it to the list of stuff to do
[20:55] <ubuntujenkins> I have set myself a deadline of 30th of june to have devloped the manual program for maverick and the quickshot ui.  Personally I think they are being picky. But i would like a 2nd / 3rd opinion.
[21:28] <dutchie> ooh, no manualbot
[21:29] <ubuntujenkins> #585484
[21:29] <godbyk> bug 545484
[21:29] <godbyk> ah, bummer.
[21:29] <godbyk> bad bots!
[21:29] <ubuntujenkins> #585484
[21:29] <ubuntujenkins> https://bugs.edge.launchpad.net/ubuntu-manual/+bug/585484
[21:29] <manualbot> Launchpad bug 585484 in ubuntu-manual "Factual problem with sudo on page 123" [Undecided,New]
[21:30] <godbyk> yay, manualbot!
[21:30] <dutchie> really should get round to making manualbot start on boot
[21:32] <ubuntujenkins> ChrisWoollard: Personally I agree with the bug reporter. If I hit alt+f2 and type sudo gedit i don't see the sudo promt. I need gksudo so that i can type in my password. It is picky but could be frustraing to a new user. just my humble opinion.
[21:32] <godbyk> ChrisWoollard: I would say that if the manual is introducing sudo, use sudo.
[21:33] <godbyk> I don't know that I run GUI apps using sudo..  I typically use it with command-line apps. But that's because I'm usually only running command-line apps.
[21:34] <dutchie> (note manualbot connects over ipv6 for extra geek points)
[21:36] <ChrisWoollard> By looking at the manual i get the impression that sudo is being run from the shell and not from Alt+F2. If it was Alt+F2 I would specify gksudo.
[21:37] <ChrisWoollard> from the shell it really doesn't matter.
[21:42] <ChrisWoollard> Ok. It has been decided. In this case it says as it is.
[21:43]  * dutchie can tell from humphreybc's experience of European steak that he has not been to Europe before
[21:43] <dutchie> "Ask for a medium steak, get a rare steak. Ask for a rare steak, get a live cow."
[21:45] <godbyk> The last time I ordered a "hamburger" in England, I got a Salisbury steak on a bun.
[21:45] <godbyk> Also, cuts of meat are different in Europe, I discovered (or at least Germany).
[21:46] <godbyk> It added an extra complication when I was trying to explain to the butcher what I wanted. (The first complication being that I don't speak German.)
[21:46] <ChrisWoollard> Where were you eating
[21:46] <godbyk> I don't recall now.
[21:46] <dutchie> what the hell is a Salisbury steak?
[21:46] <godbyk> I remember we were both reduced to pointing at body parts, though. :)
[21:47] <ChrisWoollard> A steak from Salisbury.  That's interesting.
[21:49] <godbyk> (Wikipedia teaches me so many new things each day.  It's wondrous!)
[21:49] <ChrisWoollard> To me that sounded English. BUt apparently not. That explains why I have never heard of it
[21:50] <godbyk> Yeah, I'd assumed it was named after Salisbury (the place), but knew it was likely a US thing.
[21:50] <godbyk> (It was too processed to have come from anywhere else. ;-))
[22:19] <ChrisWoollard> Godbyk: I think bug #584504 is one for you. It is an index entry appearing in the wrong place
[22:19] <manualbot> Launchpad bug 584504 in ubuntu-manual "erroneous entry at start of Index ie first entry of "CD/DVD Creator, 27"" [Undecided,New] https://launchpad.net/bugs/584504
[22:19] <godbyk> ChrisWoollard: fair enough. feel free to assign it to me.
[22:19] <ChrisWoollard> ok, will do
[22:39] <ChrisWoollard> I have a problem compiling the manual. It won't build anymore. It gets stuck half way
[22:40] <ubuntujenkins> ChrisWoollard: please paste bin your error
[22:40] <godbyk> ChrisWoollard: post the main.log file.
[22:44] <ubuntujenkins> he he I saw "later live with jools holland" and read it as "later live with josh holland"
[22:45] <ChrisWoollard> http://paste.ubuntu.com/439562
[22:45]  * dutchie is famous
[22:46] <ChrisWoollard> I don't think it was me that broke it.  I deleted my local branch and started again. It still didn't compile
[22:47] <godbyk> ChrisWoollard: are you compiling the main US English version? 'cause that log file looks okay
[22:48] <ChrisWoollard> That is weird. in the terminal it said error 1
[22:49] <ChrisWoollard> I was doing the us english
[22:49] <ubuntujenkins> I am glad you say its ok kevin cos i thought so too. I thought i was missing the obvious
[22:49] <godbyk> ChrisWoollard: paste the output around the Error 1 stuff.
[22:53]  * ubuntujenkins theres like 100 bug emails a day. We should be really bug free soon
[22:54] <ChrisWoollard> http://paste.ubuntu.com/439568
[22:54] <flan> Wishful thinking.
[22:56] <ubuntujenkins> hello flan, true it is wishfull thinking but i like to be positive about these things :)
[22:56] <ubuntujenkins> night all
[22:57] <dutchie> night ubuntujenkins
[22:57] <ubuntujenkins> night dutchie
[23:00] <godbyk> ChrisWoollard: run: makeglossaries -L english main
[23:00] <godbyk> and tell me if it gives any errors
[23:00] <ChrisWoollard> ok, will do
[23:01] <flan> G'night, ubuntujenkins.
[23:01] <godbyk> ChrisWoollard: and if that's okay, try: makeindex main
[23:02] <ChrisWoollard> no errors on either
[23:03] <godbyk> ChrisWoollard: you're compiling the lucid-e2 branch, right?  and just running 'make' with no arguments?
[23:03] <ChrisWoollard> when i run make in the ubuntu-manual directory. It pauses about half way. Then i press enter and it continues
[23:04] <ChrisWoollard> I believe it is lucid-e2
[23:04] <godbyk> ChrisWoollard:
[23:04] <godbyk> ChrisWoollard: run 'xelatex main'
[23:05] <ChrisWoollard> and just and i am running make on its own
[23:05] <ChrisWoollard> It just stops half way with a ? prompt
[23:06] <godbyk> ChrisWoollard: it should give you an error message of some sort
[23:07] <godbyk> also, type 'H' and press Enter. it'll give you more info
[23:08] <ChrisWoollard> The control sequence at the end of the top line of your error message was never \def'ed
[23:08] <godbyk> so someone misspelled a \command.
[23:09] <ChrisWoollard> i'll paste again
[23:10] <ChrisWoollard> http://paste.ubuntu.com/439582
[23:10] <godbyk> ChrisWoollard: \Button should be \button (lowercase).
[23:11] <ChrisWoollard> is that in listening to audio?
[23:12] <godbyk> ChrisWoollard: default-apps/listening-to-audio-and-music.tex line 63
[23:13] <ChrisWoollard> i found it.
[23:13] <ChrisWoollard> i'll try again
[23:14] <ChrisWoollard> now a different error. now a missing }
[23:15] <ChrisWoollard> looks like the glossary
[23:15] <godbyk> apparently people haven't been running 'make' before they commit. :)
[23:15] <godbyk> (despite my pleas for them to do so.)
[23:15] <ChrisWoollard> Well, I have to say. none of these errors were mine
[23:15] <ChrisWoollard> :)
[23:16] <godbyk> :)
[23:16] <ChrisWoollard> how do i know which line the error is on?
[23:16] <godbyk> It says l.000 (where 000 is the line number)
[23:16] <godbyk> at the beginning of the context lines (just above the ?)
[23:17] <ChrisWoollard> ok, i think 11
[23:25] <ChrisWoollard> Is this where you usually bang your head against a wall?
[23:25] <godbyk> tracking down all the typos that people make?
[23:25] <ChrisWoollard> yes
[23:25] <godbyk> it's a bit irksome sometimes, but I've gotten pretty good at it.
[23:25] <ChrisWoollard> i now have another one
[23:26] <godbyk> if you want to commit what you've fixed so far, I can try to fix the others for you real quick.
[23:26] <ChrisWoollard> i just did
[23:26] <godbyk> then maybe we'll institute a new rule that requires people to run 'make' before committing.
[23:26] <ChrisWoollard> At least I have now had a crash course on debugging
[23:27] <rickspencer3> hey guys, when I start getting content for the developer manual, what format should I get the chapters in, and where should I store them?
[23:29] <ChrisWoollard> fixed another
[23:29] <ChrisWoollard> and commited
[23:30] <ChrisWoollard> I can't find the error in the glossary though
[23:31] <godbyk> gah! damn you. :)
[23:31] <ChrisWoollard> sorry
[23:31] <godbyk> uncommitting and recommitting now. :)
[23:32] <godbyk> remaking. we'll see if they're all fixed now.
[23:32] <ChrisWoollard> Not touching anything until told to now :)
[23:33] <godbyk> looks like it compiled cleanly for me here.
[23:33] <dutchie> for a DVCS, bzr is shocking at handling parallel commits
[23:34] <dutchie> maybe we're Doing It Wrong
[23:34] <godbyk> dutchie: yeah, I don't know if I'm using it wrong or what.
[23:34] <godbyk> dutchie: but there's gotta be a better way.
[23:34] <dutchie> my answer would be "git", but...
[23:34] <godbyk> dutchie: I hate seeing the 'removed three revisions'-type messages when someone runs 'bzr 'merge'.
[23:34] <ChrisWoollard> have you pushed?
[23:35] <godbyk> nothing to push
[23:35] <godbyk> I think you got them all
[23:35] <dutchie> i mean, no offence to the guys who built bzr, but git was written in C and perl by a bunch of kernel hackers
[23:35] <dutchie> with beards
[23:35] <godbyk> heh
[23:35] <godbyk> I don't know enough to choose between the various VCSs.
[23:36] <godbyk> I just wish they'd figure it out and tell me which one I should spend time learning.
[23:36] <ChrisWoollard> Mine still doesn't build
[23:36] <godbyk> as it is, I've had to learn enough about cvs, svn, bzr, and git to check code out and in.
[23:36] <godbyk> run 'bzr status' anything listed?
[23:36] <ChrisWoollard> apparently there is an issue in the glossary line 11.
[23:36] <godbyk> ChrisWoollard: otherwise, run 'make clean', then 'make'
[23:37] <ChrisWoollard> nothing lised
[23:38] <dutchie> right, bedtime
[23:38] <ChrisWoollard> Yay
[23:38] <dutchie> night all
[23:38] <ChrisWoollard> it worked
[23:38] <godbyk> dutchie: g'night.
[23:38] <godbyk> ChrisWoollard: great!
[23:39] <ChrisWoollard> I hope people don't break it again. That scared me a bit


[01:48] <minasota> bad day for windows i guess
[01:51] <Unit193> I had them closed, it's OK.  Wasn't really rainy outside though...
[01:56] <minasota> sucks that some hospitals got rained on though. that part kinda pisses me off
[02:01] <minasota> are we talking about the same thing?
[02:16] <Unit193> No, I went literal. :P
[02:21] <minasota> haha, ok
[03:22] <superfly> Yeah, NHS has always been an MS shop. They've repeatedly done with MS even though other companies have offered better contracts for a non-Windows system. Can't say I'm surprised at what happened, it's been a few years coming.


[10:14] <Tahvok> Hey guys!
[10:14] <Tahvok> I'm having some trouble with apt-get update: https://gist.github.com/Tahvok/1fa51bacde327791d24c1fe2e6383ad8
[10:15] <Tahvok> telnet to us.archive.ubuntu.com 80 works just fine
[10:15] <Tahvok> So I'm not sure why it's failing
[10:16] <tomreyn> "500 Connection failure: Network is unreachable" is remote servers' error. this remote server can be either the us.archive.ubuntu.com server or, more likely, a proxy server in between you and the apt mirror.
[10:17] <tomreyn> Tahvok: ^
[10:18] <tomreyn> put simply: my guess is that you have a boken proxy server between the system throwing this error and the (us.)archive.ubuntu.com archive mirror servers.
[10:20] <Tahvok> tomreyn: thanks for pointing me to this. I'm checking this now
[10:28] <tomreyn> Tahvok: welcome. not that you can also run apt(-get) with -o 'Debug::Acquire::http="true"'
[10:29] <Tahvok> It was indeed proxy issue. Fixed now. Thanks a lot!
[10:30] <tomreyn> welcome. :) and in case you took note of the above hint, please make it this instead: -o 'Debug::Acquire::http=true'
[10:39] <MonsieurBon> Hi
[10:39] <MonsieurBon> how do I make iptables configuration persistent over a reboot?
[10:39] <MonsieurBon> Ideally it would load the iptables rules before any network interfaces come up
[11:09] <tomreyn> MonsieurBon: look into iptables-save and iptables-restore unless you use some other software for managing iptables, since those usually provide something else for this purpose.
[18:34] <sruli> trying to install 18.04 server, cannot find a option to setup lvm for the install


[09:35] <mdke> sladen: is that your akademy story? If so, please can you remember to post to the mailing list for review so that all the editors know what is going on?
[09:39] <mdke> story in the queue re: ubuntu-fr
[09:40] <mdke> feel free to spice it up
[11:43] <Burgundavia> mdke: is there a good time to finally finish that planet spec
[11:43] <Burgundavia> ?
[11:55] <sladen> mdke: riddell's
[11:56] <sladen> mdke: though I don't think he actually posted it
[11:18] <mdke> sladen: ah, I didn't realise that he had access
[11:31] <mdke> sladen: no, I was right - you posted it, and rich approved it. It's just nice to have a post to the mailing list so we're all in the loop
[11:32] <sladen> mdke: no. I. did. not.
[11:34] <mdke> sladen: well, someone using your account did, then
[11:34] <mdke> content2007-07-04 19:40story: added Kubuntu at Akademy 2007.sladenview
[11:35] <sladen> mdke: you should ask riddell about that then
[11:35] <mdke> he has your password?
[11:35] <sladen> mdke: either that or my laptop
[11:35] <mdke> right...
[11:36] <sladen> I'm quite intrigued now
[11:36] <sladen> perhaps we have the CMS CC'ed the mailing list with all updates/change notifications
[11:37] <mdke> just content messages would work


[00:56] <nhandler> jrib: We can't have ubottu treat kick messages as comments. Too many people use scripts that automatically specfiy a kick comment. Having a bunch of generic "You should know better" comments would not really be helpful
[00:58] <Myrtti> er, correct me if I'm wrong, but kick messages ARE treated as comments
[00:58] <Myrtti> that's how it's been in the ban tracker since time immemorial
[01:26] <gnomefreak76> has anyone wrote a factoid about the window buttons
[01:28] <gnomefreak76> ok !buttons is not it
[01:29] <Myrtti> why would anyone have written such a factoid and what do you think it should say
[01:29] <gnomefreak> Myrtti: lucid window control buttons moved to left side
[01:29] <gnomefreak> people dont like that
[01:29] <gnomefreak> alot of them too
[01:30] <gnomefreak> its one of those "lets throw it in there and see if people like it" type things IIRC
[01:31] <nhandler> I might be useful to include a link to a page explaining how to move the buttons back to the right. I have a feeling that will be a FAQ after lucid is released
[01:31] <gnomefreak> nhandler: there are a few of them but knowing how long they will be up is not known
[01:32] <nhandler> gnomefreak: Do we have a page on the wiki explaining how to move the buttons?
[01:32] <Myrtti> feels a bit of yakshaving
[01:32]  * gnomefreak can add them but i was told that someone may have already done that
[01:32] <gnomefreak> nhandler: nope not that i know of
[01:32] <gnomefreak> http://sites.google.com/site/alucidfs/how-i-do/move-buttons-to-right-side
[01:33] <gnomefreak> that is one. most of them are on blogs
[01:33] <gnomefreak> none official
[01:33] <nhandler> Yeah, I've seen the blog posts. It might be good to get a page added to the community help wiki about this.
[01:35] <gnomefreak> nhandler: yeah i wanted to the other day but was unable to find enough time to do it. there is also at least 1 bug report with the many ways to change it
[01:36] <nhandler> gnomefreak: Maybe talk to the people in #ubuntu-doc and see if someone there has some time to prepare a page
[01:37] <Myrtti> y'all should just use Xubuntu. We fortunate people have a gui for changing the location and positioning of them.
[01:37] <Myrtti> *SNERK*
[01:37] <gnomefreak> it wont be this week for me. im just finishing up updates and ill be gone for a day or 3
[01:37] <gnomefreak> ubuntu-tweek will do it
[01:37] <gnomefreak> #ubuntu-doc
[01:37] <gnomefreak> damn
[01:40] <nhandler> Myrtti: Kubuntu has something to do that too iirc
[01:41] <gnomefreak> asked in *-doc
[03:39] <Myrtti> ohai bikcmp
[03:42] <bikcmp> uhh...
[03:42] <bikcmp> chazz?
[03:55] <mneptok> @login
[04:03] <Myrtti> !ping
[04:04] <Myrtti> @whoami
[04:04] <Myrtti> @login
[04:06] <Myrtti> bikcmp: so what brings you here?
[04:11] <bikcmp> Myrtti: Was going to say that a bad nick joined, but it's all fixed now
[04:11] <bikcmp> :)
[04:13]  * mneptok gestures at the /topic
[05:03] <bazhang> bikcmp, hi
[05:06] <bikcmp> hello bazhang
[05:06] <bikcmp> sorry, rejoined here by accident.
[05:06] <bazhang> bikcmp, did you need some assistance?
[05:06] <bazhang> aha
[05:14]  * mneptok whips bazhang
[05:14] <mneptok> FASTER, damn you!
[05:15] <bazhang> hehe
[05:22] <bazhang> !sa
[05:22] <bazhang> @sa
[05:25] <Flannel> Meh.
[05:25] <Flannel> Services are down
[05:25] <wgrant> I thought my scripts were broken when anonymous_ didn't disappear.
[05:26] <wgrant> But no, no privileges for us.,
[05:26] <bazhang> weird. there is no channel at #ubuntu-sa , even though the wiki for loco teams list it as such
[07:55] <dholbach> good morning
[14:35]  * genii makes more coffee
[14:59] <KB1JWQ> If someone gets the chance, can I get some constructive feedback on a forum post?
[15:00] <KB1JWQ> http://ubuntuforums.org/showthread.php?t=1432243 <-- My last response.  I wanted to make sure that was in the right tone for the forums.  I'm entirely too used to IRC, I just don't want to come across as "RTFM, noob!" if I can avoid it.
[15:17] <jussi01> !gq
[15:17] <Pici> KB1JWQ: I think thats fine, I'm not a fan of ESR's guide myself, but for a subject such as sendmail, you really need a real question before you cans tart troubleshooting.
[15:17] <jussi01> KB1JWQ: you might waant to use that one ^^
[15:18] <KB1JWQ> Ahh, never saw that before.
[15:18] <KB1JWQ> Thanks Pici  and jussi01.
[15:19] <KB1JWQ> I'll help if I can, but I REALLY need specific questions in most cases. :-)  "Teach me X" isn't something I accept from anyone as a problem request.
[15:20] <KB1JWQ> jussi01: Unfortunately I think that one's too IRC centric.
[15:20] <KB1JWQ> What I like about ESR's guide is that it covers almost every online medium you could hope for.
[15:43] <Myrtti> +b<EMAIL_ADDRESS>?
[15:44] <Myrtti> objections?
[15:44] <Pici> Myrtti: Was he kicked earlier?
[15:44] <Myrtti> someone from that ip, yes
[15:44] <Myrtti> and banned
[15:45] <Myrtti> different ident
[17:05] <genii> "lspci" into the channel ... :/
[17:05] <ikonia> seems fixed
[17:06] <genii> ikonia: The bot caught it and gave a pastebin warn, etc
[17:06] <ikonia> I wish kubuntu would start putting things into main rather than ppa's
[17:06] <ikonia> lead by example
[17:31] <Myrtti> [19:31] ~~~dancing-bot<EMAIL_ADDRESS>has  joined #ubuntu
[18:00] <lorenzo> #ubuntu-it-chat
[18:02] <mneptok> lorenzo: you MUST type /join first
[18:02] <mneptok> !it
[18:02] <mneptok> scrivi /join #ubuntu-it
[18:03] <mneptok> non scrivi #ubuntu-it solo
[18:15] <Mamarok> lorenzo: e poi, dommanda agli altri nel canale Italiano come adjungere il canale automaticamente, cosi non dévi scrieverlô ogni volta
[19:48] <Myrtti> !soc ~= s/2006/2010/
[19:48] <arvind_k> Hi, please change the factoid of soc
[19:48] <Myrtti> !soc
[19:48] <arvind_k> oh Myrtti just did that :)
[19:48] <arvind_k> thanks
[19:48] <Myrtti> ahead of you ;-)
[19:48] <arvind_k> hahaha :) btw do you happen to know where will the mentors be hanging around ?
[19:49] <Myrtti> no idea
[19:49] <Myrtti> "IRC: #ubuntu-gsoc or #gsoc on freenode"
[19:49] <Myrtti> as on the link in the factoid
[19:49] <arvind_k> oh ok, let me check it out , thanks anyways :)
[20:03] <Myrtti> !xampp
[20:06] <Myrtti> !pm > sascha_
[20:26]  * genii rolls his eyes
[20:38] <Myrtti> !bot > human_
[20:50] <guntbert> please have a look at<nocturnus> in #ubuntu - he seems to switch between dubious advice - off topic chatter - rudeness ...
[20:52] <ikonia> ok
[20:52] <ikonia> my eyes are open
[20:53] <guntbert> ikonia: not completely sure though  ... but thx
[20:53] <ikonia> lets wait and see
[20:53] <guntbert> exactly what I was asking for :-)
[20:53] <ikonia> looks like you're right already
[20:54] <guntbert> what a pity
[20:54] <guntbert> I'd prefer to be wrong
[20:55]  * ikonia angers at the stupidity of ubuntu including the app "wtf"
[20:55] <ikonia> inline with it's code of conduct
[20:56] <Myrtti> !info wtf
[20:56] <ikonia> oh, it's gone - good
[20:56] <Myrtti> !info wtf jaunty
[20:56] <ikonia> interesting, maybe it wasn't in the official repo's
[20:56] <Myrtti> !info wtf hardy
[20:57]  * Myrtti goes to kick the wifi access point, bash it with a mallet and pour cola on the pieces
[20:57] <ikonia> oh dear
[20:58] <Myrtti> my bloodpressure isn't doing too well when I'm using the hotel wifi
[21:01] <nocturnus> ikonia: ar eyou there?
[21:01] <nocturnus> oh hello elky
[21:01] <ikonia> yes
[21:02] <nocturnus> Are you getting my PM's ...?
[21:02] <ikonia> yes
[21:02] <nocturnus> Perhaps my IRC client is blocking them
[21:02] <ikonia> no
[21:02] <nocturnus> I mean when you reply
[21:02] <nocturnus> [ because I'm +G ]
[21:03] <ikonia> ok
[21:05] <nocturnus> Well ...?
[21:05] <ikonia> well what ?
[21:05] <nocturnus> Well I'm wondering if you read my queries or what?
[21:05] <ikonia> I read them, and explained to them I'm not unbanning you at the moment
[21:06] <nocturnus> I didn't get a PM
[21:06] <ikonia> if you didn't get them, I'll explain it again here,
[21:06] <nocturnus> You can copy/paste if you wish.
[21:06] <ikonia> I'm not unbanning you as I asked you multiple times to stop referencing sofas and you chose to play dumb and pretend you had not mentioned sofas
[21:06] <nocturnus> No ... that's not what I meant ...
[21:06] <ikonia> other users complained about your offtopic comments, I attempted to stop them and you tried to push me/be smart with me
[21:06] <nocturnus> I know I said the word sofas once, but as I said it was a pun, and not a reference
[21:07] <nocturnus> I don't really know anything about sofas.
[21:07] <ikonia> I'm sure you don't
[21:07] <nocturnus> Then what's the problem?
[21:07] <ikonia> I asked you to stop referncing it 3 times and you're last words where to mention it again
[21:07] <nocturnus> I only said it once, the other times was because you asked me
[21:07] <ikonia> yes, and I asked you to stop and you just kept referencing sofas
[21:07] <nocturnus> I think this is a communication error - not my first language you know ..
[21:08] <ikonia> I understand english may not be your first language
[21:08] <nocturnus> *sigh*
[21:08] <nocturnus> I wasn't ~referencing~ them, just replying to the replies you gave!
[21:08] <ikonia> yet I kept asking you to stop and you kept replying
[21:08] <ikonia> instead of stopping
[21:08] <nocturnus> Because I don't understanded what the problem is ..
[21:08] <nocturnus> I didn't spam "sofa sofa sofa sofa ..."
[21:09] <nocturnus> understood rather
[21:09] <ikonia> I didn't say you spammed sofa sofa sofa
[21:09] <ikonia> you where making offtopic comments, sofa was one of them, I asked you to stop and you kept pushing it
[21:09] <nocturnus> Well on several occasions - that's what I meant by 's s s s  ...'
[21:10] <nocturnus> As soon as you brought it up with me, I directed all sofa-related puns towards you for clarificatoin
[21:10] <ikonia> how about stopping all "puns" as you where told to
[21:10] <ikonia> nocturnus: how do you know elky ?
[21:11] <nocturnus> She's the head organiser in #ubuntu-women
[21:11] <nocturnus> I used to go there a year ago
[21:11] <ikonia> ahh, so you would be known to her then
[21:12] <nocturnus> Not formally.
[21:12] <nocturnus> Certainly not by this alias
[21:12] <ikonia> she'll remember you
[21:12] <ikonia> oh really
[21:12] <ikonia> what alias
[21:12] <nocturnus> webchat aliases, I don't remember
[21:13] <ikonia> ok - what country are you in ?
[21:13] <nocturnus> Canada
[21:13] <ikonia> lets see if she remebers you and will vouch for your behaviour when she wakes up
[21:13] <ikonia> as I'm not convinced by your behaviour at all
[21:13] <nocturnus> This is quite rude, I know what you're trying to imply.
[21:13] <ikonia> what am I trying to imply ?
[21:14] <nocturnus> Well ... what can I say.
[21:14] <ikonia> I've just stated what I'm doing
[21:14] <nocturnus> 17:09:23 <+ikonia> oh really
[21:14] <ikonia> ?
[21:14] <nocturnus> It doesn't sound to me like you're 'just stating'. My english isn't great but I'm not socially stupid
[21:14] <ikonia> I have just stated what I'm doing
[21:15] <ikonia> I am asking elky if she remembers you to vouch for you as I'm not convinced by your behaviour
[21:15] <nocturnus> How could she 'remember' me provided I told you I was not introduced formally and that I used web-chat
[21:17] <ikonia> ok - now I don't believe you as I've just seen you've been muted in ##linux too for problematic behaviour
[21:17] <ikonia> so I'm going to leave the ban in place for a while, you can think about your behaviour
[21:18] <nocturnus> I was muted in #linux for telling people not to offer 100$ discounts on hardware
[21:18] <ikonia> that's not the case
[21:18] <nocturnus> This is why I meant you are implying more than you are saying.
[21:18] <ikonia> again - you're behaviour
[21:18] <ikonia> I'm not implying anything, I'm stating clearly
[21:18] <nocturnus> Please be fair.
[21:18] <ikonia> I am
[21:18] <nocturnus> You just jumped to conclusions based on my #linux 'behavior'
[21:19] <ikonia> no, it is in addition to your behaviour in #ubuntu
[21:19] <nocturnus> Seeing as you're in #
[21:19] <nocturnus> whoops
[21:19] <nocturnus> in #ubuntu, you could have easily given me a second chance
[21:19] <ikonia> I gave you 3 chances to stop going on about sofa's / offtopic
[21:19] <nocturnus> It can't be 'in addition' to my behavior in #ubuntu because that's the original case in question
[21:19] <ikonia> ok - I'm not playing this game
[21:20] <nocturnus> #ubuntu is the parent case, the additional case is #linux
[21:20] <ikonia> I'll state the situation
[21:20] <nocturnus> You just use circular reasoning to convict me!
[21:20] <nocturnus> I know the situation.
[21:20] <nocturnus> I'm banned until you are convinced.
[21:20] <ikonia> nocturnus: you where asked to stop being offtopic in #ubuntu - an example was mentioning sofas
[21:20] <ikonia> nocturnus: you did not stop so you where removed
[21:20] <nocturnus> Please ...
[21:20] <nocturnus> save your breath, I have a buffer on my IRC client ...
[21:21] <ikonia> nocturnus: I suspect your beahviour with your current nickname may be an attempt to hide previous bad behaviour on other nicks - but I'm not certain
[21:21] <ikonia> you're behaviour and banning in ##linux backs up that your behaviour in #ubuntu was not an accident or missunderstanding
[21:21] <ikonia> therefore I am leaving the ban in place at this time
[21:21] <nocturnus> ikonia: If you want to bring #linux into question, I have psi-jack to vouch for me, and he's a very knowledgeful regular
[21:22] <ikonia> I'm not brining ##linux into the equasion - they can do what they wish as their channel, however the fact that you got put on mute for similar behaviour to ubuntu suggests you know what you are doing
[21:38] <nocturnus> ikonia: sorry about that, I had to reconnect
[21:38] <nocturnus> Have you taken the time to consider a response to my last questions?
[21:38] <ikonia> no need to apologise, nothing more to say
[21:39] <nocturnus> Well a response to my questions would be delightful ...
[21:39] <ikonia> I didn't see a question
[21:39] <nocturnus> Hmm ... perhaps I am mistaken.
[21:39] <nocturnus> Oh wait I remember,
[21:39] <nocturnus> how long until I can put this fiasco behind me?
[21:40] <nocturnus> ... and rejoin #ubuntu?
[21:40] <ikonia> come back in a few days and we'll review it then
[21:40] <nocturnus> I don't think I'll be comming back at all, perhaps months into the future ..
[21:40] <ikonia> then why ask ?
[21:46] <ikonia> for the record psi-jack ##linux staff wouldn't vouch for him
[21:48] <elky> ikonia, sorry, i can only vouch for his existence, not his behaviour. He spent the other day informing #ubuntu-women how he was Alpha Male and a lot of people there got quite creeped out by this
[21:49] <ikonia> elky: stinks of someone like bacta
[21:50] <ikonia> his nick was registered in jan 2010
[21:50] <ikonia> the way he singled you out
[21:50] <elky> he singled me out because i booted him for proclaiming his alpha maleness
[21:50] <ikonia> ooh right
[21:50] <ikonia> he claimed he used to be in #ubuntu-women about a year ago
[21:51] <elky> i recall a similar nick that doesn't idle there permanently any longer, but unless he confirms it's only speculation
[21:52] <ikonia> odd, the guys in ##linux-ops where shocked he's asked them to vouch for him as they had pretty negative things to say
[21:52] <ikonia> and yet he found ##club-ubuntu straight away
[21:54] <elky> ikonia, did the ##linux-ops stuff seem based on recent times?
[21:54] <ikonia> yes
[21:55] <ikonia> he's only been registered sice jan 2010
[21:55] <ikonia> they didn't have much to go on
[22:25] <ikonia> !ping
[22:25] <ikonia> ubottu's hung


[07:55] <tomasarad> hi! have anybody problem to launch sK1 graphic app ? in my xenial ubuntu-studio sK1, not start - sorry for my bad english
[14:55] <cambriel> hi, i recently installed ubuntu studio for the first time (17.04) and am having a difficult time getting jack to function. so far I have attempted killing pulseaudio (which should not be necessary with ubuntu studio) and it was not helpful, neither was disabling DBUS. This is a relatively clean install except I  have installed some icon and theme packages, some of which have updated some other gnome packages, dockbarx, and som
[14:59] <cambriel> its probably also worth noting that ardour gives a "failed to open audio device" error as well when attmpting to connect to ALSA
[15:01] <OvenWerks> cambriel: try (in a terminal) killall -9 jackd jackdbus
[15:02] <cambriel> i killed jackdbus just now and re-opened ardour and its giving me a different error: "The audio backend was shutdown because:  ALSA I/O error."
[15:03] <OvenWerks> did you also kill jackd?
[15:04] <OvenWerks> alsa IO error? what buffer size are you using?
[15:05] <cambriel> jackd wasnt running
[15:05] <cambriel> the buffer size is "1024 samples"
[15:07] <OvenWerks> that should be fine.
[15:07] <OvenWerks> which audio IF do you use?
[15:09] <cambriel> im sorry i do not know what that means
[15:10] <OvenWerks> what audio device are you using?
[15:10] <cambriel> in ardour?
[15:10] <OvenWerks> in you r computerthat you want to use for ardour
[15:12] <OvenWerks> You might try pasting the output of cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh
[15:12] <OvenWerks> to pastebin.com and posting the url here
[15:15] <cambriel> i just noticed that playing videos on my browser also no longer produces audio, whereas it used to. so something went wrong obviously since i have installed? im not sure what or how
[15:15] <cambriel> https://pastebin.com/6QXsEQFw
[15:16] <OvenWerks> jackd is running so it blocks the browser
[15:17] <OvenWerks> So you are using only internal audio it looks like
[15:19] <OvenWerks> you do need to stop jackd so "killall -9 jackd"
[15:21] <cambriel> oh weird i did that before and it said there was no such process. could starting ardour have started it again somehow?
[15:23] <OvenWerks> yes
[15:23] <OvenWerks> many jack aware apps will start jackd if it is not already running
[15:24] <cambriel> yeah because i'm still getting the same alsa i/o error when i try to start ardour
[15:24] <OvenWerks> :)
[15:24] <OvenWerks> It is best to run jackdbus from qjackctl right after boot.
[15:25] <cambriel> yeah and when i try to do that it does not work lol
[15:25] <OvenWerks> Running jackdbus will bridge pulse to jack so your browser will work too.
[15:26] <cambriel> qjackctl gives me all sorts of errors when i try to start it, even right after boot
[15:26] <cambriel> thats like, my main issue with ubuntu studio so far
[15:26] <OvenWerks> some of those errors may be harmless. The question is if t will start jackdbus correctly.
[15:27] <cambriel> it does not
[15:27] <OvenWerks> You can also use jack_control from the command line
[15:28] <OvenWerks> have you changed the jack server name in the qjackctl setup?
[15:28] <OvenWerks> (in advanced)
[15:29] <cambriel> I don't think so
[15:29] <OvenWerks> ok,
[15:31] <OvenWerks> what do you get if you do killall jackd jackdbus; jack_control start
[15:35] <cambriel> https://pastebin.com/f4mkQx0f
[15:37] <OvenWerks> ls -l /usr/bin/jackdbus
[15:37] <OvenWerks> What are the permissions?
[15:38] <cambriel> -rwxr-xr-x 1 root root 108952 Sep 17  2016 /usr/bin/jackdbus
[15:38] <OvenWerks> Looks right
[15:39] <OvenWerks> Are you logged in as the same user that installed?
[15:39] <cambriel> Yes
[15:39] <OvenWerks> have you tried to run ardour or jack as root? (with sudo)
[15:41] <OvenWerks> Hint, do not ever run jack as root
[15:41] <cambriel> killall jackd jackdbus; sudo jack_control start jackd: no process found [sudo] password for angel:  --- start DBus exception: org.jackaudio.Error.Generic: Failed to open server
[15:41] <cambriel> oh woops
[15:41] <cambriel> i never did try but i just tried
[15:42] <cambriel> I thought you were telling me to :(
[15:42] <OvenWerks> It almost seems like dbus is not working
[15:42] <OvenWerks> As happens it didn't work so it should be not problem.
[15:43] <OvenWerks> I am not sure why though
[15:44] <cambriel> I tried disabling it in qjackctl but it still didnt work
[15:44] <OvenWerks> the copy of 17.04 I tried did have a working dbus. I was able to run jackdbus with no problem.
[15:45] <cambriel> should I just reinstall?
[15:47] <OvenWerks> if you are going to do that, make sure the iso image you have is right. Check the md5sum
[15:47] <cambriel> how do I do that
[15:48] <OvenWerks> http://cdimage.ubuntu.com/ubuntustudio/releases/17.04/release/MD5SUMS should match md5sum ubuntustudio-17.04-dvd-amd64.iso
[15:48] <OvenWerks> (assuming 64bit
[15:51] <OvenWerks> md5sum run on the iso will take some time :)
[15:52] <cambriel> I once did the "check disk" option on the usb when I booted from it. Is that the same thing?
[15:52] <OvenWerks> should be
[15:53] <cambriel> okay, so I will go ahead and reinstall i suppose
[15:54] <OvenWerks> you are getting beyond my personal understanding of things :(  While I use dbus, I do not understand it well
[18:41] <fred1807> This is a famous example of an Alsa "normalizer" plugin made with compressor and limiter: https://paste.debian.net/plain/989208.  Please, how/where can I set/incrase buffer_size in here ?
[20:03] <studio-user533> why is this using irc instead of a forum
[20:42] <cambriel> hi. i was in here earlier because i was trying to get help with jack on a new install of ubuntu studio. i just did a completely fresh install of ubuntu studio and it is still not workingio
[20:46] <cambriel> here are the messages from qjackctl if that is helpful https://pastebin.com/1S6DS5B1
[20:46] <cambriel> its extremely frustrating that jack is just is not working out of the box for me in ubuntu stoudi


[02:21] -queuebot:#ubuntu-release- Packageset: Removed oem-somerville-onix-adl-meta from canonical-oem-metapackages in focal
[02:21] -queuebot:#ubuntu-release- Packageset: Removed oem-somerville-onix-adl-meta from canonical-oem-metapackages in jammy
[03:38] -queuebot:#ubuntu-release- New binary: openjdk-23 [amd64] (noble-proposed/universe) [23~4ea-1] (no packageset)
[04:21] -queuebot:#ubuntu-release- Packageset: Added oem-somerville-onix-adl-meta to canonical-oem-metapackages in focal
[04:21] -queuebot:#ubuntu-release- Packageset: Added oem-somerville-onix-adl-meta to canonical-oem-metapackages in jammy
[04:22] -queuebot:#ubuntu-release- New binary: openjdk-23 [s390x] (noble-proposed/universe) [23~4ea-1] (no packageset)
[05:11] -queuebot:#ubuntu-release- New binary: openjdk-23 [arm64] (noble-proposed/universe) [23~4ea-1] (no packageset)
[06:22] -queuebot:#ubuntu-release- New sync: oem-somerville-onix-adl-meta (focal-proposed/primary) [20.04~ubuntu2]
[06:28] -queuebot:#ubuntu-release- New: accepted openjdk-23 [amd64] (noble-proposed) [23~4ea-1]
[06:28] -queuebot:#ubuntu-release- New: accepted openjdk-23 [s390x] (noble-proposed) [23~4ea-1]
[06:28] -queuebot:#ubuntu-release- New: accepted suitesparse [arm64] (noble-proposed) [1:7.4.0+dfsg-2]
[06:28] -queuebot:#ubuntu-release- New: accepted suitesparse [ppc64el] (noble-proposed) [1:7.4.0+dfsg-2]
[06:28] -queuebot:#ubuntu-release- New: accepted openjdk-23 [arm64] (noble-proposed) [23~4ea-1]
[06:28] -queuebot:#ubuntu-release- New: accepted suitesparse [armhf] (noble-proposed) [1:7.4.0+dfsg-2]
[06:28] -queuebot:#ubuntu-release- New: accepted suitesparse [amd64] (noble-proposed) [1:7.4.0+dfsg-2]
[06:28] -queuebot:#ubuntu-release- New: accepted suitesparse [riscv64] (noble-proposed) [1:7.4.0+dfsg-2]
[06:28] -queuebot:#ubuntu-release- New: accepted suitesparse [s390x] (noble-proposed) [1:7.4.0+dfsg-2]
[08:20] -queuebot:#ubuntu-release- New sync: oem-sutton.bachman-balesego-meta (focal-proposed/primary) [20.04~ubuntu2]
[08:39] -queuebot:#ubuntu-release- New: rejected oem-sutton.bachman-balesego-meta [sync] (focal-proposed) [20.04~ubuntu1]
[08:43] -queuebot:#ubuntu-release- New: rejected oem-sutton.bachman-balesego-meta [sync] (focal-proposed) [20.04~ubuntu2]
[08:43] -queuebot:#ubuntu-release- New source: oem-sutton.bachman-balesego-meta (focal-proposed/primary) [20.04~ubuntu2]
[08:48] -queuebot:#ubuntu-release- New source: ubuntu-proxy-manager (jammy-proposed/primary) [0.1~22.04.1]
[08:55] -queuebot:#ubuntu-release- New sync: oem-sutton.bachman-baara-meta (focal-proposed/primary) [20.04~ubuntu2]
[09:24] -queuebot:#ubuntu-release- Unapproved: oem-sutton.bachman-balwina-meta (focal-proposed/main) [20.04~ubuntu1 => 20.04~ubuntu2] (canonical-oem-metapackages) (sync)
[10:02] -queuebot:#ubuntu-release- New source: python-cepces (jammy-proposed/primary) [0.3.7-0ubuntu1~22.04]
[10:03] -queuebot:#ubuntu-release- New source: python-requests-gssapi (jammy-proposed/primary) [1.2.3-0ubuntu1~22.04]
[11:19] -queuebot:#ubuntu-release- New binary: durdraw [amd64] (noble-proposed/universe) [0.24.3-2] (no packageset)
[11:24] <LocutusOfBorg> britney please come back, we forgive you!
[11:25] -queuebot:#ubuntu-release- New binary: receptor [amd64] (noble-proposed/universe) [1.4.3-4] (no packageset)
[12:10] <fossfreedom_> The ubuntu-archive reports seems to have stopped on Saturday... https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/  is this something someone can hit with a hammer please?
[13:22] <LocutusOfBorg> fossfreedom_, read my request to have britney back
[13:23] <LocutusOfBorg> also graham asked the same
[13:24] <LocutusOfBorg> Bring it back, bring it back, don't take it away from me, because you don't know, what it means to me
[14:09]  * Eickmeyer waking up to LocutusOfBorg breaking into song makes my morning
[14:19] <LocutusOfBorg> we are borg, we just assimilate Freddie Mercury. Resistance was futile
[14:23] <Eickmeyer> 🤣
[14:33]  * arraybolt3_tl wonders who's going to notice I'm the one who stole the vacuum tube that the Britney mainframe relied on for operation
[14:33]  * arraybolt3_tl gently puts vacuum tube back
[15:58] -queuebot:#ubuntu-release- New: accepted oem-sutton.bachman-balesego-meta [source] (focal-proposed) [20.04~ubuntu2]
[16:04] -queuebot:#ubuntu-release- New binary: oem-sutton.bachman-balesego-meta [amd64] (focal-proposed/none) [20.04~ubuntu2] (canonical-oem-metapackages)
[16:05] -queuebot:#ubuntu-release- New: accepted oem-sutton.bachman-balesego-meta [amd64] (focal-proposed) [20.04~ubuntu2]
[16:06] -queuebot:#ubuntu-release- New: rejected oem-sutton.bachman-baara-meta [sync] (focal-proposed) [20.04~ubuntu1]
[16:14] -queuebot:#ubuntu-release- New: rejected oem-somerville-onix-adl-meta [sync] (focal-proposed) [20.04~ubuntu2]
[16:16] -queuebot:#ubuntu-release- New source: oem-somerville-onix-adl-meta (focal-proposed/primary) [20.04~ubuntu2]
[16:22] <vorlon> fossfreedom_, LocutusOfBorg: flagging the release team is probably more effective than invoking britney by name on the channel.  I've raised the python recursion limit now, hopefully that completes
[16:37] -queuebot:#ubuntu-release- New: accepted oem-somerville-onix-adl-meta [source] (focal-proposed) [20.04~ubuntu2]
[16:39] -queuebot:#ubuntu-release- New binary: oem-somerville-onix-adl-meta [amd64] (focal-proposed/none) [20.04~ubuntu2] (canonical-oem-metapackages)
[16:41] -queuebot:#ubuntu-release- New: rejected oem-sutton.bachman-baara-meta [sync] (focal-proposed) [20.04~ubuntu2]
[16:41] -queuebot:#ubuntu-release- New source: oem-sutton.bachman-baara-meta (focal-proposed/primary) [20.04~ubuntu2]
[16:42] -queuebot:#ubuntu-release- New: accepted oem-somerville-onix-adl-meta [amd64] (focal-proposed) [20.04~ubuntu2]
[16:43] <vorlon> well, rather an exciting list of java-related packages dropping out of the i386 whitelist
[16:43] -queuebot:#ubuntu-release- New: accepted oem-sutton.bachman-baara-meta [source] (focal-proposed) [20.04~ubuntu2]
[16:43] <vorlon> hopefully that's correct
[16:45] -queuebot:#ubuntu-release- New binary: oem-sutton.bachman-baara-meta [amd64] (focal-proposed/none) [20.04~ubuntu2] (canonical-oem-metapackages)
[16:46] -queuebot:#ubuntu-release- New: accepted oem-sutton.bachman-baara-meta [amd64] (focal-proposed) [20.04~ubuntu2]
[16:54] <jbicha> vorlon: that may be a side effect of https://launchpad.net/ubuntu/+source/libphonenumber/8.12.57+ds-4build1/+latestbuild/i386
[16:55] <jbicha> evolution-data-server uses libphonenumber and libphonenumber has Build-Depends: javahelper which is arch:all but ultimately depends on binfmt-support
[16:56] <jbicha> I'm thinking we may need binfmt-support in the hardcoded i386 overrides
[16:57] <jbicha> or maybe it's unrelated to what you saw, but still needs to be looked into :)
[17:01] <tsimonq2> ^ I concur with that, just haven't had the necessary justification IMHO for the ask :)
[17:01] <vorlon> neither javahelper nor binfmt-support are part of the set that dropped out, I don't think it's related
[17:06] -queuebot:#ubuntu-release- Packageset: 123 entries have been added or removed
[17:14] <LocutusOfBorg> vorlon, isn't "britney" an highlighted key like "ubuntu-archive" is? :D
[17:14] <LocutusOfBorg> thanks for fixing it!
[17:16] <tsimonq2> (When's the last time someone highlighted Britney because it was doing something good? :P)
[17:16] <tsimonq2> (Oh, that's right, when the timeframe got cut down exponentially recently :D I guess I'm wrong!)
[17:17] <vorlon> LocutusOfBorg: it doesn't appear to be fixed though
[17:18] <vorlon> doubling the recursion limit wasn't enough? :P
[17:18] <vorlon> I'll just disable the autohinter for now
[17:18] <vorlon> (which is what we did in 2021)
[17:34] <tsimonq2> vorlon: That failure *does* look awfully similar to the notmuch autopkgtest failure I was facing the other day...
[17:35] <tsimonq2> Probably not related, but just might be.
[17:35] <LocutusOfBorg> notmuch related?
[17:35] <LocutusOfBorg> howmuch?
[17:35] <tsimonq2> *hand gestures* thismuch
[17:35] <tsimonq2> :P
[17:35] <LocutusOfBorg> thatmuch? awesome!
[17:36] <LocutusOfBorg> I was joking about britney being an highlighted word for Ubuntu-release, but maaaaaaaaaaaybe, this might be a good idea at the end?
[17:36] <tsimonq2> _1
[17:36] <tsimonq2> *+1
[17:37] <tsimonq2> Britney problems tend to be of a different class than normal Release Team queries.
[17:37] <tsimonq2> (SSH access vs pure "I'm on the Release Team" type thing.)
[17:51] <ginggs> i just got some britney emails
[17:51] <ginggs> things are migrating
[18:06] <vorlon> tsimonq2: er there's no code overlap between britney and a notmuch autopkgtest
[18:14] -queuebot:#ubuntu-release- Unapproved: cloud-init (mantic-proposed/main) [23.4-0ubuntu1~23.10.1 => 23.4.1-0ubuntu1~23.10.2] (core, ubuntu-cloud)
[18:35] -queuebot:#ubuntu-release- New binary: rust-if-watch [amd64] (noble-proposed/universe) [3.2.0-5] (no packageset)
[18:41] <vorlon> does anyone know if there's a particularly large transition going on that would explain the autohinter being angry?
[18:42] <vorlon> wondering if I should re-enable it now that we've had a successful run, or if it's just going to fail again
[19:01] -queuebot:#ubuntu-release- Unapproved: cloud-init (lunar-proposed/main) [23.4-0ubuntu1~23.04.1 => 23.4.1-0ubuntu1~23.04.2] (core, ubuntu-cloud)
[19:03] -queuebot:#ubuntu-release- Unapproved: cloud-init (jammy-proposed/main) [23.4-0ubuntu1~22.04.1 => 23.4.1-0ubuntu1~22.04.2] (core, ubuntu-cloud)
[19:04] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [23.4-0ubuntu1~20.04.1 => 23.4.1-0ubuntu1~20.04.2] (core, edubuntu, ubuntu-cloud)
[19:04] <jbicha> vorlon: I think python3 is the only big one now
[19:05] <vorlon> python3 is not a candidate so should not have impacted the autohinter
[21:23] <vorlon> tried to turn the autohinter back on and it again hit recursion limits: https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/noble/2024-01-08/20:58:21.log so it's back off again
[22:21] -queuebot:#ubuntu-release- New binary: rust-gix-commitgraph [amd64] (noble-proposed/universe) [0.22.1-1] (no packageset)
[22:22] -queuebot:#ubuntu-release- New binary: rust-gix-commitgraph [arm64] (noble-proposed/universe) [0.22.1-1] (no packageset)
[22:22] -queuebot:#ubuntu-release- New binary: rust-gix-commitgraph [ppc64el] (noble-proposed/universe) [0.22.1-1] (no packageset)
[22:22] -queuebot:#ubuntu-release- New binary: rust-gix-commitgraph [armhf] (noble-proposed/universe) [0.22.1-1] (no packageset)
[22:24] -queuebot:#ubuntu-release- New: accepted durdraw [amd64] (noble-proposed) [0.24.3-2]
[22:24] -queuebot:#ubuntu-release- New: accepted rust-gix-commitgraph [amd64] (noble-proposed) [0.22.1-1]
[22:24] -queuebot:#ubuntu-release- New: accepted rust-gix-commitgraph [armhf] (noble-proposed) [0.22.1-1]
[22:24] -queuebot:#ubuntu-release- New: accepted rust-if-watch [amd64] (noble-proposed) [3.2.0-5]
[22:24] -queuebot:#ubuntu-release- New: accepted receptor [amd64] (noble-proposed) [1.4.3-4]
[22:24] -queuebot:#ubuntu-release- New: accepted rust-gix-commitgraph [ppc64el] (noble-proposed) [0.22.1-1]
[22:24] -queuebot:#ubuntu-release- New: accepted rust-gix-commitgraph [arm64] (noble-proposed) [0.22.1-1]
[22:27] -queuebot:#ubuntu-release- New binary: rust-gix-commitgraph [s390x] (noble-proposed/universe) [0.22.1-1] (no packageset)
[22:39] -queuebot:#ubuntu-release- New: accepted rust-gix-commitgraph [s390x] (noble-proposed) [0.22.1-1]


[23:46] <mfisch> is anyone else having issues with apport?
[23:46] <penguin42> what's it doing to you?
[23:47] <mfisch> when I click "Continue" it just closes
[23:47] <mfisch> I'm trying to report these annoying gwibber crashes
[23:47] <penguin42> you're running it from the command line? does it give any diag when it disappeares?
[23:47] <mfisch> unfortunately no, nor in syslog
[23:48] <mfisch> 0 exit code too
[23:48] <penguin42> oh, that's not very nice
[23:48] <mfisch> yeah,
[23:48] <mfisch> also it's creating a 0 byte .upload file
[23:48] <mfisch> _usr_bin_gwibber.1001.upload
[23:53] <mfisch> same behavior for apport-cli
[23:56] <penguin42> I'm not sure the 0 byte file is a problem - I think that's just a flag
[23:56] <mfisch> right
[23:56] <mfisch> I assume it thinks it was able to upload the crash
[23:57] <penguin42> mfisch: I think what I'd expect it to be doing would be opening a web browser
[23:57] <mfisch> yep
[23:57] <mfisch> me too
[23:57] <mfisch> well it's python, I'll attach pdb
[23:58] <penguin42> oh please explain; I've never figured out debugging python
[23:58] <mfisch> I'm just going to walk through it


[00:28] <musclehill> Running 12.04.3. Receive errors about tmdb3.py on a regular basis. Doesn't affect recording or shutdown
[23:24] <Hydr0p0nX> is there a way I can have a kernel module auto-recompile after an upgrade?
[23:24] <Hydr0p0nX> need my tuning adapter and network card setup to


 k11:wheezy
[11:31] <k1l_> i think he did some trolling before
[19:20] <bazhang>  wN (~wN@redhat/jwaterwo)
[19:20] <k1l> yep
[19:20] <bazhang> a bit surprising someone considered "trusted" in that community would want to disrupt ours
[19:23] <LjL> at least under your concept of wanting to disrupt a community, which apparently involves being surprised that someone that you thought was perfectly valid Ubuntu support gets shunned
[19:25] <IdleOne> I think I agree but I am not sure you worded that how you intended, least is not clear to me.
[19:25] <LjL> maybe s/someone/something/ helps
[19:26] <LjL> these days after my fingers have typed about three or four characters they just tab-complete at the body layer
[19:34] <bazhang> the  constant "wat^" repeated, getting well clear of the topic , staying there, calling us bots and then quitting
[19:35] <bazhang> since the channel is the main front/edge for the community, I'm not sure how much more clarity you  need there
[19:36] <bazhang> also, reisio seems to confuse ##linux with #ubuntu
[19:37] <bazhang> user term1,term2,term3 was making some odd comments
[19:38] <LjL> maybe i'm seeing a different log from what you're seeing. i see "^ wat" repeated a grand total of two times; i see technical support, perhaps with some slightly off-topic light-heartnedness that, really, one can expect is acceptable; i see him trying to help with getting iTunes things from Ubuntu (by using VirtualBox or whatever, and i also see him helping other people with things beforehand); and i see him asking *why* that wasn't considered technical
[19:38] <LjL> support, and calling the *bot* a bot, that he felt hassled by
[19:38] <IdleOne> he was helping the user with the itunes question, his answer was probably the best solution possible (a little verbose perhaps). the !language call for the word ass was excessive, could have been handled with a simple "Please keep the language clean" instead of a bot trigger. He didn't call anyone a bot.
 Itunes is evil lol  <--- I consider continuing on and on about this to be "disruptive" and has nothing to do with iTunes support
[19:40] <bazhang> which is where it was when we asked them to get back on topic
[19:40] <k1l> i think the itunes rants should be there in the channel.
[19:40] <IdleOne> it isn't enough to just read the words, we need to also read between the lines.
[19:40] <IdleOne> I think LjL and I are talking about wN and not xanux
[19:40] <bazhang> I presume you mean shouldn't
[19:41] <k1l> the main target was not to get itunes running, but to make sure to rant about it.
[19:41] <bazhang> he got the answer on how to use iTunes right away with a winehq db link, and multiple suggestions, then it was dragged on for quite a bit
[19:42] <k1l> and to make "^ wat" after beeing asked to stay ontopic and not use family unfriendly language is not the way i think a ubuntu/member/ should have handled the situation
[19:43] <IdleOne> what ubuntu member?
[19:43] <bazhang> yes exactly. and reisio, as always has to interject: telling us it's ot is more disruptive than letting us go on for several minutes about this itunes offtopic chat
[19:43] <k1l> IdleOne: wN got a redhat cloak
[19:44] <LjL> i think some of you guys really, really have lost track. also, i'm talking about wN, not xanux or reisio or anyone else
[19:44] <IdleOne> k1l: yes, what does that have to do with ubuntu/member?
[19:44] <bazhang> LjL, or you misread what we were talking about from the start
[19:45] <k1l> IdleOne: as a cloaked member (ubuntu or redhat) you represent the community. that is my point.
[19:45] <LjL> pray tell, how is saying "[21:20:18] <bazhang>  wN (~wN@redhat/jwaterwo) [21:20:47] <bazhang> a bit surprising someone considered "trusted" in that community would want to disrupt ours" not talking about wN? if you meant something else, than you did wN a disservice for randomly pasting his cloak like that.
[19:46] <bazhang> seriously?
[19:46] <LjL> yes, seriously.
[19:46] <LjL> do i look like i'm joking at the moment?
[19:46] <IdleOne> k1l: yes, wN has a redhat cloak and that means he represents that community. My argument is that wN did nothing wrong and he felt harassed by the bot because of the use of a very mild "bad" word.
[19:46] <k1l> IdleOne: so if i join #fedora, beeing offtopic, using non-familiar language (which both is against the channel guidelines) and then make comands when beeing asked to stick to the guidelines. what would that look like?
[19:46] <bazhang> no , I mean you really want to drag this out?
[19:48] <k1l> IdleOne: i am not happy how that situation turned out. but im not fine with blaming us for that alone
[19:48] <IdleOne> I think you both misread the entire situation with wN and ended up chasing him out of the channel.
[19:48] <k1l> IdleOne: i disagree
[19:48] <bazhang> haha
[19:49] <IdleOne> I also think it is time that we stop making comments about users in this channel about how they respond to questions or how they ask questions. It makes us look like we are poking fun at them.
[19:49] <bazhang> !disunity!
[19:54] <k1l> IdleOne: just to make it clear. i was not picky at wN because he got a redhat cloak. i just think i would not have liked an ubuntu/member/ to act like that in another support channel when looking back at that situation
[20:47] <k1l> hi paulgreen35
[20:48] <paulgreen35> Hi. I am trying to find someone who will give me a hand to access the Ubuntu Forums. Would you be able to help?
[20:49] <k1l> paulgreen35: actually this is the operator channel for the irc-channel. for questions regarding the forums please ask in #ubuntuforums
[20:49] <paulgreen35> Ok, thanks.
[21:18] <genii> I get a feeling the "!livestream" deal was a ploy to get people to watch the Syria fundraiser
[22:18] <bazhang> * LLKCKfan<EMAIL_ADDRESS>[22:18] <bazhang> heads up on this user
[22:19] <bazhang> nothing ever works, will repeat question forever